{"Headers": "AVEVA Catalog", "Content": "By default, the AVEVA Catalog window is displayed with the General discipline and Home tab selected. The main parts of the AVEVA Catalog window are:\n\nCatalog Explorer - provides an easy-to-use, graphical method of exploring the Catalog Database.\nThe title bar of the module window, displays the quick access toolbar and the name of the current project.\nQuick Access Toolbar: options on the tabs and the project menu can be added to the Quick Access Toolbar for convenient access. Some commands are located here by default. The default location of this toolbar is above the tabs to the left of the title bar, but it can be moved below them if required. Refer to Quick Access Toolbar for further information.\nOverall Project functionality: accessed from the Project tab, the displayed fluent User Interface (UI) provides access to a number of key commands and facilities.\n3D Graphical View - displays the design model graphically as the model is built. When required the Messages window is also displayed in the 3D graphical view, refer to Messages window.\nThe title bar of the module window, displays the quick access toolbar and the name of the current project.\nThe title bar of the module window, displays the quick access toolbar and the name of the current project.\nQuick Access Toolbar: options on the tabs and the project menu can be added to the Quick Access Toolbar for convenient access. Some commands are located here by default. The default location of this toolbar is above the tabs to the left of the title bar, but it can be moved below them if required. Refer to Quick Access Toolbar for further information.\nQuick Access Toolbar: options on the tabs and the project menu can be added to the Quick Access Toolbar for convenient access. Some commands are located here by default. The default location of this toolbar is above the tabs to the left of the title bar, but it can be moved below them if required. Refer to Quick Access Toolbar for further information.\nOverall Project functionality: accessed from the Project tab, the displayed fluent User Interface (UI) provides access to a number of key commands and facilities.\nOverall Project functionality: accessed from the Project tab, the displayed fluent User Interface (UI) provides access to a number of key commands and facilities.\n3D Graphical View - displays the design model graphically as the model is built. When required the Messages window is also displayed in the 3D graphical view, refer to Messages window.\n3D Graphical View - displays the design model graphically as the model is built. When required the Messages window is also displayed in the 3D graphical view, refer to Messages window.\nMessage Log window displays user and system messages created by the application including alerts and errors.\nStatus Bar: located at the bottom right hand corner of the AVEVA Catalog window. Displays status information such as errors, warnings and information.\nCommand Window is used for executing standard commands and Programmable Macro Language (PML) functions.\nAVEVA Catalog Tabs: most commands, facilities and utilities of AVEVA Catalog are accessed from a number of tabs.\nMessage Log window displays user and system messages created by the application including alerts and errors.\nMessage Log window displays user and system messages created by the application including alerts and errors.\nStatus Bar: located at the bottom right hand corner of the AVEVA Catalog window. Displays status information such as errors, warnings and information.\nStatus Bar: located at the bottom right hand corner of the AVEVA Catalog window. Displays status information such as errors, warnings and information.\nCommand Window is used for executing standard commands and Programmable Macro Language (PML) functions.\nCommand Window is used for executing standard commands and Programmable Macro Language (PML) functions.\nAVEVA Catalog Tabs: most commands, facilities and utilities of AVEVA Catalog are accessed from a number of tabs.\nAVEVA Catalog Tabs: most commands, facilities and utilities of AVEVA Catalog are accessed from a number of tabs.\n\n\n\nQuick Access Toolbar\nGeneral\nHome\nAVEVA Catalog\nQuick Access Toolbar\nQuick Access\nQuick Access Toolbar\nProject\n3D Graphical View\nMessages\nMessages\nCatalog Explorer -\nMessage Log\nStatus Bar\nCommand Window\nAVEVA Catalog Tabs\nAVEVA Catalog"}
{"Headers": "Quick Access Toolbar", "Content": "The quick access toolbar is at the top right hand corner of the AVEVA Catalog window. The General discipline is selected by default, the toolbar contains a set of common menu short cuts.\n\nThe main work area of AVEVA Catalog includes a Catalog Explorer which is central to navigation of the Catalog and Properties databases.\n\nFor a full explanation of the Catalog Explorer and common AVEVA E3D Design user interface refer to Common Functionality.\n\n\n\nAVEVA Catalog\nGeneral\n\nCatalog Explorer\nCommon Functionality"}
{"Headers": "Project tab", "Content": "The Project tab provides access to a number of key project commands and facilities. All the displayed options are available for selection common to all products with the exception of the Options functionality. The functionality enables the editing/viewing of user preferences specific to the AVEVA E3D Design product and discipline.\n\nUnits, Explorer Settings, Show Tooltips and Coordinates are common throughout AVEVA E3D Design products, refer to Units and Coordinates for further information. Representation Rules are specific to AVEVA Catalog.\n\n\n\nProject\nOptions\nUnits\nExplorer Settings\nShow Tooltips\nCoordinates\nUnits\nCoordinates"}
{"Headers": "Drawing Representation Settings", "Content": "The Drawing Representation Settings allow a system administrator to define the appearance of a component, as displayed in a 3D graphical view depending on the following drawing representation settings:\n\nThe functionality available from the Drawing Representation Settings enables a representation types to be defined, each corresponding to a given combination of these representation settings. Reference types can then reference such a type to change the appearance of a displayed component.\nA set of sub windows show all the representation types currently defined, use the upper part of the main window to edit the lists by adding, removing or modifying individual entries.\nEntries can be cut, replaced, copied, inserted after or before the current selection.\nThe File entry near the top of the window shows where the current type set, as listed on the window, is stored.\nEach representation type is defined by the following settings:\nThe range of drawing levels to be shown\nThe obstruction level\nThe centerline flag\nThe tube flag.\nThe range of drawing levels to be shown\nThe range of drawing levels to be shown\nThe obstruction level\nThe obstruction level\nThe centerline flag\nThe centerline flag\nThe tube flag.\nThe tube flag.\nA keyword\nA description\nA drawing level range\nAn obstruction level\nThe centerline flag\nThe tube flag.\nA keyword\nA keyword\nA description\nA description\nA drawing level range\nA drawing level range\nAn obstruction level\nAn obstruction level\nThe centerline flag\nThe centerline flag\nThe tube flag.\nThe tube flag.\n\n\n\nDrawing Representation Settings\nDrawing Representation Settings"}
{"Headers": "Disciplines within AVEVA Catalog", "Content": "To facilitate working within AVEVA Catalog certain functionality becomes available depending on which discipline is active.\n\nThe disciplines available for selection are:\nThe GENERAL discipline contains common toolsets which are available throughout AVEVA Catalog. Selecting any other option expands on the available toolsets providing access to features specific to that discipline. Refer to AVEVA Catalog and Common Tools for further information.\nFor all other functionality common to all AVEVA E3D Design products, refer to Common Functionality.\nGeneral, Piping, Equipment, Electrical, Structures, Supports.\nGeneral, Piping, Equipment, Electrical, Structures, Supports.\nGeneral, Piping, Equipment, Electrical, Structures, Supports.\nNote:\nAdministrator functionality is only displayed if the user has system administrator rights.\n\n\n\nAVEVA Catalog\nCommon Tools\nGeneral\nPiping\nEquipment\nElectrical\nStructures\nSupports\nGENERAL\nAVEVA Catalog\nCommon Tools\nCommon Functionality\nNote\n:"}
{"Headers": "Multi-Purpose Windows", "Content": "AVEVA Catalog uses multi -purpose windows to carry out tasks, such as the creation of a new catalog element or the modification of an existing catalog elements, refer to the relevant functionality for further information.\n\nOr the creation of a category for any discipline from the same window by selecting the desired Purpose. Refer to Attributes of DATA Elements for further information.\n\n\n\n\nAttributes of DATA Elements"}
{"Headers": "the catalog database", "Content": "The Catalog database which is a reference database contains a catalog of the standard components where component selection is provided through specifications that dictate which catalog components can be used.\nIt may contain a single \u2018universal\u2019 catalog, but it will more commonly contain a general catalog plus one or more specialized catalogs specific to particular design functions.\n\n\n\nCatalog"}
{"Headers": "How it works", "Content": "Once a component is selected, a Specification Reference (SPREF) is identified and held in the Model database. The SPREF points to a Specification Component (SPCOM) in the specification, this in turn points to a catalog component (SCOM, SPRF and son on) in the catalog.\n\nWhen working within the Piping, Equipment, Electrical, Structures or Supports disciplines, selecting any tab provides access to features specific to that discipline.\nWhen working within a disciplines AVEVA Catalog uses multi-purpose windows. For example, it is possible create either a pipework or structures specification from the same window by selecting the desired purpose. For an explanation of common window functionality refer to Multi-Purpose Windows\n\n\n\nMulti-Purpose Windows\n, Electrical,\nStructures\nSupports\nMulti-Purpose Windows"}
{"Headers": "Hierarchy", "Content": "Catalogues are constructed as a hierarchy of elements, each element has certain attributes and some may contain further member elements, the complete catalogue hierarchy is displayed below.\n\nAll database elements are owned by other elements, therefore elements must be created in a strict order.\nThe following database elements are common to all catalog disciplines:\nSections and Categories are administrative elements which allows the segregation of particular types of catalogue data into logical parts of the hierarchy. Sections which subdivide an overall CATA are obligatory; Categories, which subdivide Sections, are optional. A CATA can contain a number of Catalogue Sections. These are of two types: Piping Sections (SECT) and Structural Sections (STSE).\nTo create a section, refer to Create Section for further information, to create a category, refer to Units for further information.\nSome database elements are only applicable to specific disciplines such as table definitions and connections. For further information on the hierarchical structure and the catalog database, refer to Catalog Database Structure.\nWORLD\nCATALOG (CATA)\nSECTIONS\nCATEGORIES (optional).\nWORLD\nWORLD\nCATALOG (CATA)\nCATALOG (CATA)\nSECTIONS\nSECTIONS\nCATEGORIES (optional).\nCATEGORIES (optional).\n\n\n\nCreate Section\nUnits\nCatalog Database Structure\nCreate Section\nUnits\nCatalog Database Structure"}
{"Headers": "Create Catalog", "Content": "Use the Create Catalog window to create a new Catalog database (DB) element (CATA) in the catalog hierarchy.\nDepending on the discipline currently selected in AVEVA Catalog a default purpose selection is made, for example, PIPE is selected by default when in the AVEVA Catalog Pipework discipline.\nSelect the Use defined Storage Area check box to add elements to a defined storage area, refer to Storage Areas for further information.\n\nNote:\nCATA is the highest level element of the Catalog hierarchy.\n\n\n\nStorage Areas\nCreate Catalog\nUse defined Storage Area\nStorage Areas\nNote\n:"}
{"Headers": "Create Section", "Content": "A Catalog Database Element (CATA) can contain a number of Catalog Sections which are administrative elements, there are two types: Piping Sections (SECT) and the Structural Sections (STSE). They are principal administrative elements by which the Catalog is divided and arranged. A SECT or STSE can only be created below a CATA element.\n\nUse the Create Section window to create a new SECT element in the catalogue hierarchy the functionality is common throughout all disciplines. Depending on the discipline currently selected in AVEVA Catalog a default purpose selection is made, for example, PIPE is selected by default when in the AVEVA Catalog Pipework discipline.\nSelect the Use defined Storage Area check box to add elements to a defined storage area, refer to Storage Areas for further information.\nNote:\nIf the PIPING discipline is selected, the Create Section window is displayed.\n\n\n\nStorage Areas\nNote\n:\nCreate Section\nCreate Section\nUse defined Storage Area\nStorage Areas"}
{"Headers": "Create Category", "Content": "Sections, which subdivide an overall catalog (CATA), are obligatory. Categories, which subdivide Sections, are optional (although their use is recommended). A Category (CATE element) is an administrative element, which can be created below a section (SECT element). Depending on the purpose of a Category the appropriate element is created in the Catalog DB (CATE for piping and Structural Category (STCA) for structures).\n\nUse the Create Category or Create Structural Section window to create a new CATE or SCTA element in the catalog hierarchy, the functionality is common throughout all disciplines.\nDepending on the discipline currently selected in AVEVA Catalog a default purpose selection is made, for example PIPE is selected by default when in the AVEVA Catalog Pipework discipline.\nSelect the Use defined Storage Area check box to add elements to a defined storage area, refer to Storage Areas for further information.\n\nThe CATE or SCTA element is displayed in the Catalog Explorer and the Model View window is displayed.\n\n\n\n\nStorage Areas\nCreate Category\nCreate Structural Section\nAVEVA Catalog\nAVEVA Catalog\nUse defined Storage Area\nStorage Areas\nCatalog Explorer\nModel View"}
{"Headers": "Model View", "Content": "The Model View window is used to define or modify the size, geometry and other characteristics of a component. These are also used in setting the attributes of the pointsets, geomsets and datasets to which the component refers.\n\nModel References\nUse the Model References part of the Model View window to create administrative elements and component parameters, define the axis system and p-points, group primitive elements and DATA elements, also referred to reference data\nOn creation of a CATE or SCTA the window is automatically populated with default parameters dependent upon the element being created.\nCategory\nAn administrative element used to separate generic elements of particular types in the hierarchy. Refer to Catalog Sections (SECT and STSEC) and Categories (CATE and STCA) for further information.\nComponent\nCatalog components which contain the parameters and the references of the component. Refer to Elements Used in Both Types of Catalog Section/Category , Elements Used in Piping Sections/Categories, Elements Used in Structural Sections/Categories and Catalog Components for further information.\n3D P-point Set (PTSET)\nUsed in the Piping discipline, a Point Set (PTSET) is a collection of p-point elements for piping components, usually abbreviated to 3D Pointset.\nTo define a point set which is a definition of the position, direction, connection type and bore of a Component\u2019s P-points, to be used by Model, Isodraft and so on. Refer to 3D Pointsets (PTSET) for further information.\nThe numbering of P-points of piping components must follow certain conventions, refer to Piping Components for further information.\n3D Pline Set (PTSSET)\nUsed in the Structures discipline, a Pline Set (PTSSET) is a collection of p-lines for structural components.\nTo define a point set which is a definition of the position, direction, connection type and bore of a Component\u2019s P-points, to be used by Model, Isodraft and so on. Refer to Structural Pointsets (PTSSET) for further information.\n3D Geometry Set (GMSET)\nA 3D Geometry Set (usually abbreviated to 3D Geomset) is a grouping of the primitive elements which make up a piping component, joint or fitting. It specifies the dimensions, orientation and obstruction geometry of each primitive. Refer to 3D Geomsets (GMSET), 3D Geomset Primitives and Constructing Structural Geomsets for further information.\nNegative 3D Geomsets (NGMSET)\nA NGMSET is a grouping of negative 3D primitive elements which are used to represent holes or end preparations for structural items. It specifies the dimensions, orientation and obstruction geometry of each negative primitive. Refer to Negative 3D Geomsets (NGMSET) and Negative Primitives for further information.\nStructural Geometry Set (GMSSET)\nA GMSSET is a grouping of 2D primitive elements used to make up structural profiles. It specifies the dimensions, orientation and obstruction geometry of each primitive. The Geomset defines the symbol that is drawn for a particular Component by AVEVA Catalog (and Model) and also defines the obstruction geometry of the Component for use when clash checking. Each symbol is built up from a combination of the following three types of primitive:. Refer to Structural Geomsets (GMSSET), Structural Geomset Primitives and Constructing 3D Geomsets for further information.\nData Set (DTSET)\nA Data Set (DTSET) element is a grouping of DATA (DATA) elements, holding any catalog data not stored more specifically elsewhere and which is required for use in Model or Draw. A Data Set can be created below a Section (SECT) element or a Category (CATE) element. A DATA element with a specified Design Parameter (DESP) purpose can own multiple Sub Data (SUBDAT) elements which contain valid values for selection in Model or Draw. Refer to Data Set (DTSET) and Sub Data (SUBDAT) for further information.\nBoltSet (BTSE)\nA Bolt Set (BTSE) element is the administrative element for catalog component bolting information. It can also be used to store information for the standard bolt holes. The standard bolt holes are numbered from 1 to NOFF. It owns Bolt Point (BLTP) elements, which store the bolting information for an individual bolt for a particular type of flange. Refer to Bolting Tables and Bolting for further information.\nJoint Weld Set (JWSET)\nUsed for structural joints and fittings and panel fittings, a Joint Weld Set (JWSET) element is a grouping of structural Joint Weld (JWELD) elements. Each JWELD contains information to define the position, path and various weld attributes, for example, type and connection references. When the joint or fitting is created in Model, the properties of any JWELD elements are copied to create an STWELD element under the fixing or panel fitting. Refer to Joint Welds for further information.\nCatalog Components\nEssentially there are four types of catalog components, Piping component, profile, joint and fitting. Refer to Catalog Components, Piping Component, Profile, Joints and Fitting for further information.\nParameter Definitions\nParameters define the size, geometry and other characteristics of a component, these are used in setting the attributes of the pointset, geomsets and datasets to which the component element refer.\nAll classes of component can use component parameters, design parameters and insulation parameters. Structural Components can also use attached and owning design parameters. Component parameters are defined in the Catalog; the other classes of parameters allow characteristics to be set during the design process.\nPiping Components, Profiles and Fittings each use one type of Pointset and one type of Geomset. Joints use both types of Pointset and one type of Geomset. The attributes of Pointsets and Geomsets may be defined in terms of parameters, set either explicitly or as real expressions.\nThe Parameter Definitions part of the Model View window is used to create, define, modify and delete the component definitions. On creation of a CATE or SCTA the window is automatically populated with default parameters dependent upon the element being created. For example, as the Piping discipline is active, the default parameter Nominal Bore is displayed in the Parameter Definitions part of the Model View window.\n\nUse the generic functionality to create, copy, import pre-defined components or export the current list.\nNew\nCreates a new component, the Reference part of the Model View window is displayed.\nCopy\nMake a duplicate of the currently selected component\nImport\nImports from an external CSV or Excel file containing a list of pre-defined components\nExport\nExport the current list of components to an external CSV or Excel file.\nNew\nCreates a new component, the Reference part of the Model View window is displayed.\nCopy\nMake a duplicate of the currently selected component\nImport\nImports from an external CSV or Excel file containing a list of pre-defined components\nExport\nExport the current list of components to an external CSV or Excel file.\n\nCategory\nComponent\n3D P-point Set (PTSET)\n3D Pline Set (PTSSET)\n3D Geometry Set (GMSET)\nNegative 3D Geomsets (NGMSET)\nStructural Geometry Set (GMSSET)\nData Set (DTSET)\nBoltSet (BTSE)\nJoint Weld Set (JWSET)\nCategory\nCategory\nComponent\nComponent\n3D P-point Set (PTSET)\n3D P-point Set (PTSET)\n3D Pline Set (PTSSET)\n3D Pline Set (PTSSET)\n3D Geometry Set (GMSET)\n3D Geometry Set (GMSET)\nNegative 3D Geomsets (NGMSET)\nNegative 3D Geomsets (NGMSET)\nStructural Geometry Set (GMSSET)\nStructural Geometry Set (GMSSET)\nData Set (DTSET)\nData Set (DTSET)\nBoltSet (BTSE)\nBoltSet (BTSE)\nJoint Weld Set (JWSET)\nJoint Weld Set (JWSET)\nNote:\nOnly the last parameter in the parameter list can be deleted. Warnings are issued because deleting a parameter definition does not change any component geometry or component property expressions that are dependent on the deleted parameter. The corresponding parameter value is removed from any component found that uses this parameter definition.\n\n\n\nCatalog Sections (SECT and STSEC) and Categories (CATE and STCA)\nElements Used in Both Types of Catalog Section/Category\nElements Used in Piping Sections/Categories\nElements Used in Structural Sections/Categories\nCatalog Components\n3D Pointsets (PTSET)\nPiping Components\nStructural Pointsets (PTSSET)\n3D Geomsets (GMSET)\n3D Geomset Primitives\nConstructing Structural Geomsets\nNegative 3D Geomsets (NGMSET) and Negative Primitives\nStructural Geomsets (GMSSET)\nStructural Geomset Primitives\nConstructing 3D Geomsets\nData Set (DTSET)\nSub Data (SUBDAT)\nBolting Tables\nBolting\nJoint Welds\nCatalog Components\nPiping Component\nProfile\nJoints\nFitting\nModel View\nModel References\nModel References\nModel View\nCategory\nComponent\n3D P-point Set (PTSET)\n3D Pline Set (PTSSET)\n3D Geometry Set (GMSET)\nNegative 3D Geomsets (NGMSET)\nStructural Geometry Set (GMSSET)\nData Set (DTSET)\nBoltSet (BTSE)\nJoint Weld Set (JWSET)\nCategory\nCatalog Sections (SECT and STSEC) and Categories (CATE and STCA)\nComponent\nElements Used in Both Types of Catalog Section/Category\nElements Used in Piping Sections/Categories\nElements Used in Structural Sections/Categories\nCatalog Components\n3D P-point Set (PTSET)\n3D Pointsets (PTSET)\nPiping Components\n3D Pline Set (PTSSET)\nStructural Pointsets (PTSSET)\n3D Geometry Set (GMSET)\n3D Geomsets (GMSET)\n3D Geomset Primitives\nConstructing Structural Geomsets\nNegative 3D Geomsets (NGMSET)\nNegative 3D Geomsets (NGMSET) and Negative Primitives\nStructural Geometry Set (GMSSET)\nStructural Geomsets (GMSSET)\nStructural Geomset Primitives\nConstructing 3D Geomsets\nData Set (DTSET)\nData Set (DTSET)\nSub Data (SUBDAT)\nBoltSet (BTSE)\nBolting Tables\nBolting\nJoint Weld Set (JWSET)\nJoint Welds\nCatalog Components\nCatalog Components\nPiping Component\nProfile\nJoints\nFitting\nParameter Definitions\ncomponent parameters\ndesign parameters\ninsulation parameters\nattached\nowning design parameters\nParameter Definitions\nModel View\nNominal Bore\nParameter Definitions\nModel View\nNote\n:\nNew\nReference\nModel View\nCopy\nImport\nExport"}
{"Headers": "Parts", "Content": "Once a component is selected in the Model, a Specification Reference (SPREF) is identified and points to a Specification Component (SPCOM) in the specification, which in turn points to a catalog component. However parts can be used in the catalog to fully describe the components without the need for defining a specification. Refer to Component Parts for further information.\n\n\n\n\nComponent Parts"}
{"Headers": "Units", "Content": "Unit types can be set up which can then be linked to relevant attributes of the various elements which appear throughout the databases.\n\nThe unit hierarchy is as follows, the UNIT element is a top level administrative element, which owns a Measurement Set element (MSET) which in turn owns a Measurement Type element (MTYPE) and finally an Attribute List Element (ATLIST). Refer to Unit Types for further information.\n\n\n\nUnit Types"}
{"Headers": "Groups", "Content": "Groups are any collection of elements in the database which the administrator can define as a group. The Group World (GPWL) is a top level administrative element. Which is turn owns a Group (GROU) element. Refer to Group World Element (GPWLD) and Group Element (GROUP) for further information.\n\n\n\n"}
{"Headers": "Text Definition", "Content": "Use the dual purpose Text Definition window to create or modify a Text Definition (TEXT elements) which can be used to store any textual data at almost any level in the database hierarchy displayed in the Catalog Explorer.\n\nThe text string is stored in the STEX attribute of the Text element, is restricted to a maximum of 120 characters. The text must not be enclosed between apostrophes unless you want to form part of the text string.\n\n\n\nText Definition\nCatalog Explorer."}
{"Headers": "Detail and Material Text", "Content": "Use the dual purpose Detail Text Definition window to define Detail Text (DTEXT elements) which hold any general text which is used to describe the corresponding component in schedules, on isometric drawings and so on.\n\nEach type of component has a two-dimensional symbol which is used to represent it on the isometric drawings. Each symbol is referred to by a text attribute, known as the symbol key (SKEY) attribute, of a DTEXT element. Refer to Symbol Keys for further information.\nAVEVA Catalog has a complete list of the standard symbols and their associated symbol keys, grouped together by generic type (ELBO, FLAN, PCOM, VALV and so on).\nDepending on the Generic Type selected, the Description: part of the Detail Text Definition window, is populated with a list of available descriptions. The Symbol Key is set automatically set once the generic type has been selected.\nFor Isodraft the fields for Detail, Interface B and Interface C must be populated. Text expressions can be specified for the Detail (Isodraft), (Interface B) and (Interface C) text fields. Text expression must be entered as valid string expressions beginning with an open parentheses \"(\" and ending with a close parentheses \")\". If the expression is not specified in this way the text fields will be treated as a simple string. Refer to Catalog Requirements for further information.\nAs Material Texts are common across component types it is normal to create them in a separate section (below a SECT element). Material Text (SMTE elements) contain descriptive text describing the material(s) from which the physical component is constructed. Refer to Material Text for further information.\n\n\n\n\nMaterial Text\nDetail Text Definition\nSymbol Keys\nDescription:\nDetail Text Definition\nDetail\nInterface B\nInterface C\nDetail (Isodraft)\n(Interface B)\n(Interface C)\nCatalog Requirements\nMaterial Text"}
{"Headers": "the general discipline", "Content": "The General discipline within AVEVA Catalog provides a standard set of tools, which are commonly available throughout. Additional options specific to other disciplines are available, refer to the relevant discipline for further information.\n\n\n\nGeneral"}
{"Headers": "Model Settings", "Content": "Design data attributes have initial defaults that can be amended; parameters must have their defaults set for the appropriate type of component.\n\nThe left hand part of the window shows the current design data attribute defaults for piping components. These have standard default settings, amend any of the displayed settings as required.\nUse the right hand part of the window to set default values for any relevant types of parameter. Use the option at the top of the window to choose the required parameter type; any current settings are shown in the scrollable list. Amend existing settings or set new parameters in either of the following ways:\nModel settings can be changed using the Category Creation window as well as by the Model Settings window. In addition to changing the catalog parameters, the Category Creation window may change other parameters based on a categories dataset.\nFor example, if the dataset includes properties that define design parameters, those design parameters in the model settings are set to the default property values from the dataset. If the Only Update Catalog Parameters check box is checked on the Model Settings window, then the Category Creation window will not update any model settings except those for catalog parameters.\nTo set parameters individually, enter a parameter number and its required default setting in the text-boxes below the list, then select Insert to transfer the new settings to the list.\nTo copy parameter settings from an existing catalog or design item, navigate to an element which has the required parameter settings and select Use CE to copy these to the current list.\nTo reset all standard defaults, click Default, all design data attributes are set to their standard settings and (CAUTION) clears all design parameter settings.\nTo set parameters individually, enter a parameter number and its required default setting in the text-boxes below the list, then select Insert to transfer the new settings to the list.\nTo set parameters individually, enter a parameter number and its required default setting in the text-boxes below the list, then select Insert to transfer the new settings to the list.\nTo copy parameter settings from an existing catalog or design item, navigate to an element which has the required parameter settings and select Use CE to copy these to the current list.\nTo copy parameter settings from an existing catalog or design item, navigate to an element which has the required parameter settings and select Use CE to copy these to the current list.\nTo reset all standard defaults, click Default, all design data attributes are set to their standard settings and (CAUTION) clears all design parameter settings.\nTo reset all standard defaults, click Default, all design data attributes are set to their standard settings and (CAUTION) clears all design parameter settings.\n\n\n\nInsert\nUse CE\nDefault\nCategory Creation\nModel Settings\nCategory Creation\nOnly Update Catalog Parameters\nModel Settings\nCategory Creation"}
{"Headers": "Copy Element and Rename", "Content": "For ease of use and as a time saving device, use the Copy element and Rename window to copy an element along with its attributes from one owner in the catalog database to another.\n\n\n\n\nCopy element and Rename"}
{"Headers": "Catalog Copy", "Content": "Use the Catalog Copy window to copy catalog items from read only databases to local write databases. The read only databases may be foreign databases or locally copied MASTER databases that you has no write access to.\nThe following restrictions should be observed:\n\nThe Catalog Copy window is divided into the following frames:\nCopy Options\nSelect either the Same Name or the Prefix option. If the Prefix option is selected, the string in the adjacent text gadget is used as the prefix to the Copy To name. The Include Reference toggle is used to include any references for any SCOM, SPRF or SFIT items that are included in the Copy From frame, as these references may or may not exist in the same part of the hierarchy.\nCatalog Explorer\nDisplays all the catalog elements in the current set of databases.\nCopy From\nDisplays all the items that are to be copied in the current sequence.\nCopy To\nDisplays the name of the database items that to be created when the Apply Copy option is applied. It also shows the database item name in the target database into which the item is to be copied.\nCopy to Location\nDisplays all the possible locations in the target databases, where the Copy From items can be copied to.\nCopy Options\nSelect either the Same Name or the Prefix option. If the Prefix option is selected, the string in the adjacent text gadget is used as the prefix to the Copy To name. The Include Reference toggle is used to include any references for any SCOM, SPRF or SFIT items that are included in the Copy From frame, as these references may or may not exist in the same part of the hierarchy.\nCatalog Explorer\nDisplays all the catalog elements in the current set of databases.\nCopy From\nDisplays all the items that are to be copied in the current sequence.\nCopy To\nDisplays the name of the database items that to be created when the Apply Copy option is applied. It also shows the database item name in the target database into which the item is to be copied.\nCopy to Location\nDisplays all the possible locations in the target databases, where the Copy From items can be copied to.\nThe Copy From frame can be populated by right clicking in the Catalog Explorer frame to display a sub-menu, Add Elements to Copy From and Add Members to Copy From or by clicking either of the two top options to the right of the Catalog Explorer frame.\n\nOr by clicking either of the two top options to the right of the Catalog Explorer frame.\n\n\nEither option adds the current element or its members to the Copy From pane.\nOnce the Copy From pane has been populated, the right click functionality on the Catalog Explorer is only active if the Catalog Explorer item's owner is the same as the one in the pane. The options are also only active based on the current catalog explorer item and the Copy From pane owner type.\nItems can be removed from the Copy From pane by using the right click functionality:\n\nOr by clicking the two lower options to the left of the Copy From pane:\n\n\nThe Copy From pane can also be populated by using the Include References toggle and Update option. These are only active if any items in the grid are of type SCOM, SPRF or SFIT and will look for any references for example: GMRE, PTRE, NGMRE, DTRE, PSTR, GSTR and BLFARRAY.\n\nAny items not already in the Copy From pane are added.\n\nIf the Include References toggle is not checked then the references are removed from the pane. The Update option allows any new items that have been added to the pane after the Include References toggle has been ticked to be added to the pane.\nWhen the Copy From pane is populated the Copy To pane is also populated.\n\nThe Copy To pane is populated with the name the item is to be given when the Apply Copy option is applied. The green tick indicates that the name does not already exist in the target databases. Any items where the specified name does exist in the target databases will be highlighted with a red dot sphere and will not be copied. The target databases are defined by any database in the current MDB that can be written to.\n\nThe Copy To column now needs to be populated with the new location in the target databases.\nSelect an owning element in the Catalog Explorer frame to copy to, making it the currently selected item.\nIf the selected item in the Catalog Explorer frame is of the correct owner type and the database can be written to then a Set copy location from Explorer right click option is available in Copy To pane.\n\nFor example, if the element members that are to be copied are of type CATA then an owning element of type CATA in the destination database from the Catalog Explorer frame must be selected then select Set copy location from Explorer.\n\nIf an owning element of the correct type is already present when the Copy From grid is populated then the Copy To Location pane is also populated with any items in the target databases where the items in the Copy From pane can be created.\nFor example, in the following figure a number of SPRF items are copied which need to be created at an Structural Category (STCA) level. Therefore the pane is populated with all STCA elements in all databases that can be written to in the Multiple Database (MDB).\n\nWhen an item is selected in the Copy to Location pane, the location of the selected items in the Copy To pane can be set by either right clicking on the Copy To Location pane.\n\nOr by clicking the options located to the right of the pane.\n\n\nOnce the Copy To grid is populated and contains any items that have a name and copy location that both contain a green tick, Apply becomes active.\nWhen Apply is clicked, all the items that can be copied (items with green ticks in both columns of the Copy To grid) are copied from the Copy From pane to the location in the Copy To pane with the applied name. All references that are included in the copy are reset to the newly created references in the target databases. The Catalog Copy window is then cleared ready for the next copy sequence.\nThe system only allows items to be copied at the same level in the hierarchy within a copy sequence.\nThe owning hierarchy must exist (or be created) in the database where the items are going to be copied to.\nOnly members of top level items (for example: SPWL, CATA and so on) can be copied, as it is not possible to specify into which database an item is to be copied without actually having an existing item in the target database.\nThe system only allows items to be copied at the same level in the hierarchy within a copy sequence.\nThe system only allows items to be copied at the same level in the hierarchy within a copy sequence.\nThe owning hierarchy must exist (or be created) in the database where the items are going to be copied to.\nThe owning hierarchy must exist (or be created) in the database where the items are going to be copied to.\nOnly members of top level items (for example: SPWL, CATA and so on) can be copied, as it is not possible to specify into which database an item is to be copied without actually having an existing item in the target database.\nOnly members of top level items (for example: SPWL, CATA and so on) can be copied, as it is not possible to specify into which database an item is to be copied without actually having an existing item in the target database.\nNote:\nIf the destination database does not have an owning element of the correct type then it must be created in the database hierarchy. For example in the case of a CATA refer to Create Catalog.\nNote:\nDifferent elements can be created in different locations in the target databases.\n\n\n\nCreate Catalog\nCatalog Copy\nCatalog Copy\nCopy Options\nSame Name\nPrefix\nPrefix\nCopy To\nInclude Reference\nCopy From\nCatalog Explorer\nCopy From\nCopy To\nApply Copy\nCopy to Location\nCopy From\nCopy From\nCatalog Explorer\nAdd Elements to Copy From\nAdd Members to Copy From\nCatalog Explorer\nCatalog Explorer\nCopy From\nCopy From\nCopy From\nCopy From\nCopy From\nCopy From\nInclude References\nUpdate\nCopy From\nInclude References\nUpdate\nInclude References\nCopy From\nCopy To\nCopy To\nApply Copy\nCopy To\nCatalog Explorer\nCatalog Explorer\nSet copy location from Explorer\nCopy To\nCatalog Explorer\nSet copy location from Explorer\nNote\n:\nCreate Catalog\nCopy From\nCopy To Location\nCopy From\nCopy to Location\nCopy To\nCopy To Location\nNote\n:\nCopy To\nApply\nApply\nCopy To\nCopy From\nCopy To\nCatalog Copy"}
{"Headers": "Storage Areas", "Content": "Storage areas are places in the catalog database where administrative and reference data for the piping, structural or equipment disciplines are held, this functionality ensures the correct storage areas are used, otherwise referred to as defined storage areas, by default the Pipework tab is selected.\nDependent upon which discipline is been used dictates how each tab is populated, such as the administrative elements and the other relevant elements (also referred to reference data) required by the Pipework, Structural or Equipment disciplines.\nThe File functionality allows the default \u2018out of box\u2019, defined user groups or company specific storage areas to be loaded.\n\n\n\nPipework\nFile"}
{"Headers": "Material Properties", "Content": "AVEVA Catalog can display the content of the data held in properties databases created in AVEVA Administration. These databases are used to hold properties of components and materials which may be needed for stress analysis or safety auditing of all or part of a design. Includes data such as the material densities needed by the Model structural applications for calculating weights and center of gravity of steelwork items. Refer to Property Database and the Catalog Database for further information.\nUse the Material Properties window to view attributes of the currently selected Material World (MATW) or Component World (CMPW) element.\n\n\n\nProperty Database\nCatalog Database\nProperty Database\nCatalog Database\nMaterial Properties"}
{"Headers": "Import data", "Content": "Use the Spreadsheet Import window to import data such as surface treatment or paint definitions from CSV and Excel files.\n\n\n\nSpreadsheet Import"}
{"Headers": "Specification List", "Content": "The currently configured specifications within the catalog database are categorized and displayed in the Specification List window, by default the highest element in the hierarchy, specification worlds are displayed.\nUse the Spec World Types drop-down to filter specifications relevant to a specific design discipline (Piping, Structural Steel, and so on).\nThe options are as follows:\n\nOnce the relevant specification world element has been selected, all the specifications which are members of that world are displayed in the window. Select a specification in the list to make it the current selection in the Catalog Explorer.\nTo view the specification, click Display Spec, the selected specification is displayed. The functionality available from the window is common throughout AVEVA applications.\n\nAll\nPiping\nHeating & Ventilation\nCable Trays\nHanger & Support\nEquipment\nStructural Steel.\nAll\nAll\nPiping\nPiping\nHeating & Ventilation\nHeating & Ventilation\nCable Trays\nCable Trays\nHanger & Support\nHanger & Support\nEquipment\nEquipment\nStructural Steel.\nStructural Steel.\nNote:\nAll applicable Spec World elements are shown in the Spec Worlds list. This facility reads the Purpose attributes of the Specification Worlds to find the required elements, so it will only work correctly if these have been set. Use the All setting to find a required specification if it is not displayed.\n\n\n\nSpecification List\nSpec World Types\nNote\n:\nSpec Worlds\nPurpose\nAll\nCatalog Explorer\nDisplay Spec"}
{"Headers": "Specification Structure", "Content": "The Specification Structure window displays a summary of the currently selected specification in the hierarchy. Use the window to quickly view the structure and content of the selected specification.\n\nTo view the structure and content of the specification, identify the specification in the Catalog Explorer as the CE, then click Specification. The Specification Structure window is then populated with the detail of the newly selected specification.\n\n\n\nSpecification Structure\nCatalog Explorer\nSpecification\nSpecification Structure"}
{"Headers": "Surface Treatment Definition", "Content": "Use the Surface Treatment definition window to define new surface treatments, the window consists of three sections:\nSurface Treatments\nwhere all the available surface treatments for a project are specified.\nPaint Definitions\nwhere the paint type, the coating thickness and the order in which the coatings are applied is specified.\nSelected Coatings\nwhen the allowable paint types and manufacturers are specified.\nSurface Treatments\nwhere all the available surface treatments for a project are specified.\nPaint Definitions\nwhere the paint type, the coating thickness and the order in which the coatings are applied is specified.\nSelected Coatings\nwhen the allowable paint types and manufacturers are specified.\n\n\n\n\nSurface Treatments\nPaint Definitions\nSelected Coatings\nSurface Treatment definition\nSurface Treatments\nPaint Definitions\nSelected Coatings"}
{"Headers": "Symbol Set", "Content": "Symbolic representation is cross-disciplinary functionality which allows design items to be represented symbolically in a 2D View in Draw when the Update Design process is executed. This depends on creating appropriate symbol and/or text templates in the Draw database and setting up appropriate data structures and references in Catalog databases before this functionality is used.\nIf the Draw administrator does not have the appropriate permissions in the Catalog, then effective co-operation between the Draw and Catalog administrators will be critical for the symbolic representation functionality.\nTo support this functionality, additional elements (DRSSET and DRSYLK) have been added to the Catalog database.\nEach catalog item references a parameterized template and provides a set of values for these parameters. To use symbolic representation with a fixed size symbol for occurrences of these catalog items in Draw View, a single design symbol set (DRRSET) is created and referenced by the GPART for each of these items. However, if a scaled design symbol is used, a DRSSET would be created for each of these items in the Catalog.\n\n\n"}
{"Headers": "Selection Tables", "Content": "Selection Tables (specifications) are general purpose tables which can be used to control the choice of components available for selection by populating the table with specific GPARTS for use in DESIGN, refer to Component Parts for further information. Selection Tables are more commonly used with Equipment and Steelwork disciplines, refer to Equipment and Structures for further information.\nThe tables can be populated in the following ways:\nSelection Criteria - uses a series of questions (column headers (TABHEA and TABHQU)) and answers (entry in table rows (TABITEM)).\nAttributes Filters - searches the catalog for GPARTS with matching attributes.\nSelection Criteria - uses a series of questions (column headers (TABHEA and TABHQU)) and answers (entry in table rows (TABITEM)).\nSelection Criteria - uses a series of questions (column headers (TABHEA and TABHQU)) and answers (entry in table rows (TABITEM)).\nAttributes Filters - searches the catalog for GPARTS with matching attributes.\nAttributes Filters - searches the catalog for GPARTS with matching attributes.\nNote:\nSelection tables cannot be used in the Piping discipline, refer to Setting Specification Attributes for further information.\n\n\n\nComponent Parts\nEquipment\nStructures\nSetting Specification Attributes\nComponent Parts\nEquipment\nStructures\nNote\n:\nSetting Specification Attributes"}
{"Headers": "Search", "Content": "A search facility is provided as an extension to several windows within AVEVA Catalog. The Search window can be invoked from a number of other windows such as the Task sub window of the Create Part World.\nUsing this search functionality is different from the common search functionality available throughout all disciplines, refer to Search for further information. The example below shows the Search window invoked from the Create Part World window.\n\nThe individual components of the search window (DB Type, Element Types, and so on) is pre populated by the displayed window, however these values can be amended.\nUse the DB Type drop-down to specify which database to search, possible values are:\nIn most cases, only the Catalog and Property databases will be relevant when using AVEVA Catalog.\nIn the Element Types field enter a space delimited list of elements types to search. Click the box to the right of this displays the Select Element Types to search for window.\n\nThe list of elements displayed in this window are dependent on the Database Type, selected in the DB Type drop-down list.\nPick from the list of Available Element Types by highlighting an entry and click Add ->> to include the element in the Selected Element Types list.\nTo remove an element from the list of Selected Element Types highlight an entry and click <<-Remove.\nClick OK to return to the search window.\nBy default the Search In field is pre-populated with an asterisk. The asterisk value is a wildcard which indicated the search will be conducted on all elements in the database hierarchy.\nIf the search is to be carried out below a certain position in the database hierarchy, specify the name of the element to search below in the Search In field (for example DRA/PRJ/TMP/PIPING/A0). Alternatively select the item in the Catalog Explorer and click Add CE.\nClick Reset to reset the Search In field to its default value.\nUse the grid part of the window to build a list of criteria to be used when conducting the search. These conditions allow the search to test certain criteria based on the values of attributes within the specified elements. There will normally be a pre-populated entry depending on the displayed window.\n\nClick in a cell in the Attribute column to expand a list of valid attributes available to the element. The list of attributes is dependant on the selection made in the Element Types field.\nClick in the cell in the operator column to expand a list of available comparison criteria, possible selections are as follows:\n=\nAttribute value is equal to\n<>\nAttribute value is more than or less than\n<\nAttribute value is less than\n<=\nAttribute value is less than or equal to\n>\nAttribute value is more than\n=>\nAttribute value is equal to or more than\nLike\nAttribute value is like (specified string).\nAttribute value is equal to\nAttribute value is more than or less than\nAttribute value is less than\nAttribute value is less than or equal to\nAttribute value is more than\nAttribute value is equal to or more than\nAttribute value is like (specified string).\nTo remove an entry from the list of search criteria click Remove Statement.\nClick Choose Result Cols to display the Search Results Presentation Settings window allowing you to alter the presentation of the search results:\n\nIn the Search Result Presentation Settings window select the required attributes to be displayed in the search results by selecting the check box beside the attribute.\nChange the order attributes are displayed by selecting Move Up or Move Down. The list of attributes is dependent on the Element Types selected.\nClick Referenced Attributes to display the Choose Referenced Attributes for xxxx window allowing the Referenced Attributes to be displayed.\n\nSelect Referenced Attributes from the hierarchical list and click Add ->> to include them in the Selected Attributes list.\nTo remove entries from the list of Selected Attributes highlight an entry and click <<-Remove.\nWhen all the fields of the search window have been populated, click Find to begin the search. The time taken to display search results is dependent on the size of the database and complexity of the search criteria.\nA search results window is displayed as follows, results are displayed in a grid list.\nClick to highlight an entry. Depending on the window that originally launched the search, it may be possible to select multiple entries by holding CTRL while making selections.\nClick Use Result to pass the selection back to the window that invoked the search window.\nNote:\nThese are the databases that are available to a standard project, additional databases may appear in the list if an administrator has customized the project.\n\n\n\nCreate Part World\nSearch\nCreate Part World\nSearch\nCreate Part World\nNote\n:\nElement Types\nSelect Element Types to search for\nDB Type\nAvailable Element Types\nAdd ->>\nSelected Element Types\n<<-Remove\nOK\nCatalog Explorer\nAdd CE\nReset\n=\n<>\n<\n<=\n>\n=>\nLike\nRemove Statement\nChoose Result Cols\nSearch Results Presentation Settings\nSearch Result Presentation Settings\nMove Up\nMove Down\nReferenced Attributes\nChoose Referenced Attributes for xxxx\nAdd ->>\nSelected Attributes\n<<-Remove\nFind\nCTRL\nUse Result"}
{"Headers": "Convert Spec", "Content": "The Convert Spec window allows older style specifications to be converted into new style GPART families or TABGRO elements types depending on the discipline which is active, such as Piping or Structures.\nThe conversion process takes all the referenced catalog data from the incoming specification and creates the new structure, it will also create a new specification with the GPART reference.\nFor non-piping specifications, the Convert Spec creates a TABGRO>CTABLE>TABITE structure to match the incoming spec, so that the new selection option can be used when in Model.The Convert Spec may not be displayed instantly, before the window is displayed a conversion list is built. While this process takes place a progress bar is displayed at the bottom of the AVEVA Catalog window.\n\nUse the Discipline drop-down list, to select the type of specification to convert, the Source specification list is populated with applicable specifications. From the Source specification list, click to highlight the specification to be converted.\nSelect an entry in the Source specification list to display possible target elements in the database hierarchy displayed in the Catalog Explorer for the converted spec to output to. These are listed in the Destination Spec Worlds/Table Groups and Destination Part Worlds.\nIf no destinations are listed new elements can be created, select Create Spec World (displays the Create Specification World) or select Create Part World (displays the Create Part World).\nClick to highlight an entry from the Destination Spec Worlds/Table Groups and Destination Part Worlds.\nClick Apply to convert the specification and create the desired database hierarchy in the Catalog Explorer.\n\n\n\nCreate Part World\nConvert Spec\nDiscipline\nSource specification\nSource specification\nSource specification\nCatalog Explorer\nDestination Spec Worlds/Table Groups\nDestination Part Worlds\nCreate Spec World\nCreate Specification World\nCreate Part World\nCreate Part World\nDestination Spec Worlds/Table Groups\nDestination Part Worlds\nApply\nCatalog Explorer."}
{"Headers": "Surface Treatment", "Content": "Use the functionality to be create table groups elements for the purpose of setting up specific Surface Treatments (refer to Surface Treatment Definition for further information) for parts prior to being applied to a model in the Model application.\nCreate a new table group element in the catalog hierarchy, the functionality is common throughout all disciplines, refer to Multi-Purpose Windows for further information. A Table Group (TABGRO element) must be created below a Specification World (SPWL).\n\nOnce the new table group administrative element is created, the TABGRO window is displayed. Refer to Selection Tables for further information.\nA TABGRO must be created for the following types of selection table:\nWhen dealing with a Surface Treatment a TABGRO will reference a PART family listing all the surface treatments that are to be available to the project (refer to Create Part Family for\nInside and outside surface treatments can be assigned based on the PSPE attributes of the PIPE or HVAC elements. In this case, the TABGRO (Table Group) and all the TABITE elements (Table Items) must have their purpose attributes set to IPSP and OPSP.\nIPSP Selection criteria for the inside surface treatment SPEC of PIPES/HVAC based in the PSPE.\nOPSP Selection criteria for the outside surface treatment SPEC of PIPES/HVAC based in the PSPE.\nFACE Selection criteria for the surface treatment SPEC based on the FACE CODE of the owning ZONE.\nGENE Generic Selection Criteria for the surface treatment SPEC.\nIPSP Selection criteria for the inside surface treatment SPEC of PIPES/HVAC based in the PSPE.\nIPSP Selection criteria for the inside surface treatment SPEC of PIPES/HVAC based in the PSPE.\nOPSP Selection criteria for the outside surface treatment SPEC of PIPES/HVAC based in the PSPE.\nOPSP Selection criteria for the outside surface treatment SPEC of PIPES/HVAC based in the PSPE.\nFACE Selection criteria for the surface treatment SPEC based on the FACE CODE of the owning ZONE.\nFACE Selection criteria for the surface treatment SPEC based on the FACE CODE of the owning ZONE.\nGENE Generic Selection Criteria for the surface treatment SPEC.\nGENE Generic Selection Criteria for the surface treatment SPEC.\n\n\n\nSurface Treatment Definition\nMulti-Purpose Windows\nSelection Tables\nCreate Part Family\nSurface Treatment Definition\nMulti-Purpose Windows\nTable Group\nSpecification World\nSelection Tables\nCreate Part Family"}
{"Headers": "Integration with AVEVA ERM", "Content": "For more detailed information about setting up AVEVA ERM integration, the notification mechanism and workflows for catalog and part list integration, refer to the AVEVA ERM-Design Integration User Guide located at: C:\\Programs(x86)\\AVEVA\\Everything3D2.10\\ERMIntegration\\AVEVAERMIntegrationUserGuide.pdf.\n\n\n"}
{"Headers": "Piping discipline", "Content": "When working within the Piping discipline of AVEVA Catalog, piping specific hierarchy can be created and additional tools specific to piping are available.\n\n\n\n"}
{"Headers": "Piping Component", "Content": "Piping Component (COMP) is an element defining a piece of pipework. It consists of a list of values (known as component parameters) and references to a 3D pointset element and a 3D geomset element. The pointset and geomset make use of the component parameter values in defining the size, geometry and connection types of the Piping Component. Refer to Piping Component (COMP; SCOM) for further information.\n\n\n\nPiping Component (COMP; SCOM)\nPiping Component (COMP; SCOM)"}
{"Headers": "Specific piping hierarchy", "Content": "The piping specific hierarchy contains information such as branch, reducer, nominal bore, bolting or connection tables which are part of the catalog database.\n\nThese tables are a collection of similar elements in the database which the administrator can group together elements to help with creation of specifications such as bore ranges, branch and reducer types, wall thickness and pipe data. Refer to Wall Thickness Table, Pipe Data Table and Create Nominal Bore World for further information. On all windows, click Apply or OK to save the changes or click Cancel to discard any inputs and close the window.\nThe Connection Compatibility Table hierarchy holds a list of all the compatible connection types for Piping Components in a set project. Refer to Coco Table for further information.\nThe Bolt Table hierarchy contains information describing the nature of the bolted connections of Piping Components in a project. Refer to Bolt Diameter and Length Tables for further information.\nTable World\nThe Table World (TABWL) is a top level administrative element, which can own one or several administrative table elements:\n\nMany multi-purpose windows provide similar functionality through the create and modify options. Refer to Multi-Purpose Windows for further information.\nNominal Bore Table\nA Nominal Bore Table (NOMTAB) element is the administrative element for a nominal bore table and must be created below a Table World (TABWLD) element.\n\nMany multi-purpose windows provide similar functionality through the create and modify options, the functionality is common throughout all disciplines. Refer to Multi-Purpose Windows for further information.\nOnce the administrative elements have been created, the Size Range window is displayed. By default, the Name fields are automatically populated, the Description is Unset and the Purpose is set to PIPE, as the currently active discipline is PIPING.\n\nClick to highlight the desired bore sizes in the Available Nominal Bores (mm) list. Multiple bores can be selected at once by left clicking and dragging the mouse pointer. To remove particular highlighted entries hold down the CTRL key and left click on a bore size.\nADD >\nAdds highlighted bore size to the Nominal Bores part of the Size Range window.\nADD ALL >>\nAdds all highlighted bore size to the Nominal Bores part of the Size Range window.\nRemove <\nRemoves the highlighted bore size to the Nominal Bores part of the Size Range window.\nRemove All <<\nRemoves all the highlighted bore size to the Nominal Bores part of the Size Range window.\nADD >\nAdds highlighted bore size to the Nominal Bores part of the Size Range window.\nADD ALL >>\nAdds all highlighted bore size to the Nominal Bores part of the Size Range window.\nRemove <\nRemoves the highlighted bore size to the Nominal Bores part of the Size Range window.\nRemove All <<\nRemoves all the highlighted bore size to the Nominal Bores part of the Size Range window.\n\nCreate Branch Tables\nBranch tables are used as a way of selecting the type of fitting used for example BW could indicate a Butt Weld Tee, SW a Socket Weld Tee, WOL a Butt Weld Outlet Boss and SOL a Socket Weld Outlet Boss. A Branch Table (BRTAB) element must be created below a Table World (TABWLD) element.\n\nMany multi-purpose windows provide similar functionality through the create and modify options, the functionality is common throughout all disciplines. Refer to Multi-Purpose Windows for further information. Once the BRTAB is created, the Branch Table window is displayed.\nBy default, the name fields are automatically populated, the description is Unset and the Purpose is set to BRAN, as the currently active discipline is PIPING.\n\nClick to highlight the desired bores in the Available Nominal Bores (mm) list by left clicking on the desired bore size. Multiple bores can be selected at once by left clicking and dragging the mouse pointer down the list.\nADD >\nAdds highlighted bore size to the Branch Size part of the Branch Table.\nADD ALL >>\nAdds all of the highlighted bore size to the Branch Size part of the Branch Table.\nRemove <\nRemoves the highlighted bore size to the Branch Size part of the Branch Table.\nRemove All <<\nRemove all of the highlighted bore size to the Branch Size part of the Branch Table.\nADD >\nAdds highlighted bore size to the Branch Size part of the Branch Table.\nADD ALL >>\nAdds all of the highlighted bore size to the Branch Size part of the Branch Table.\nRemove <\nRemoves the highlighted bore size to the Branch Size part of the Branch Table.\nRemove All <<\nRemove all of the highlighted bore size to the Branch Size part of the Branch Table.\n\nShort codes are under user control and are stored in the defaults file: PMLUI\\dflts\\cat-pipetablecodes.\nOnce the desired bores have been added to the Branch Table, short codes can be added. From the Cell Click Action part of the Branch Table, click Add.\nIn the Main Bores part of the Branch Table window, click on the required empty cells to add the short code.\n\nTo add the short code to multiple cells, select multiple cells by holding down CTRL and left clicking and dragging the mouse pointer.\nTo remove short codes, from the Cell Click Action part of the Branch Table window, select Clear and left click on the cell within the Branch Table.\nTo return the mouse pointer to normal operation, from the Cell Click Action part of the Branch Table window, select None.\nReducer Sizes\n\nThe Reducer Sizes check box is only active when used in conjunction with the Specification creation windows. When a Spec is associated with a Specification Table this check box allows the quick switching between windows allowing faster edits to be made.\nCreate Reducer Tables\nThe Reducer Table creation window behaves in exactly the same manner as the Branch Table window. To avoid repetition this section only lists the differences between the two. A Reducer Table must be created below a Table World (TABWLD) element.\n\nMany multi-purpose windows provide similar functionality through the create and modify options, the functionality is common throughout all disciplines. Refer to Multi-Purpose Windows for further information. Once the Reducer Table (BRTAB) element, the Reducer Table window is displayed.\nBy default, the name fields are automatically populated, the description is Unset and the Purpose is set to REDU, as Reducer has been selected from the Create Specification Table group.\n\nThe only difference in behaviour to the Branch Table window is the list of Short Codes available for selection, by default, these are:\nShort codes are under user control and are stored in the defaults file: PMLUI\\dflts\\cat-pipetablecodes. Populate the table as described in the previous section.\n\nCOCO Table\nThe Connection Compatibility Table (CCTA) holds a list of all the compatible connection types for Piping Components in a set project. A CCTA is an administrative element which exists at the same level as CATA in the hierarchy. A CCTA has Connection Compatibility (COCO) elements as its members, each of which has a pair of coded connection types stored as its CTYPE attribute. These connection types are those referred to in the PCON attribute of a Piping Component\u2019s P-points.\n\nMany multi-purpose windows provide similar functionality through the create and modify options, the functionality is common throughout all disciplines. Refer to Multi-Purpose Windows for further information. Once the Coco table element is created, the Connection Compatibility Table window is displayed.\n\nFrom the Connection Types part of the Connection Compatibility Table window, select the required connection types from the list of available connections. Multiply selections can be made by holding down the CTRL key and using the left click on the mouse.\nFrom the Connection Types part of the Connection Compatibility Table window, click to highlighted a connection type to the Connections grid then by click Add >.\nAdd >\nAdds the highlighted connection type to the Connections part of the Connection Compatibility Table.\nAdd All >>\nAdds all of the highlighted connection type to the Connections part of the Connection Compatibility Table.\nRemove <\nRemoves the highlighted connection type to the Connections part of the Connection Compatibility Table.\nRemove All <<\nRemove all of the highlighted connection type to the Connections part of the Connection Compatibility Table.\nAdd >\nAdds the highlighted connection type to the Connections part of the Connection Compatibility Table.\nAdd All >>\nAdds all of the highlighted connection type to the Connections part of the Connection Compatibility Table.\nRemove <\nRemoves the highlighted connection type to the Connections part of the Connection Compatibility Table.\nRemove All <<\nRemove all of the highlighted connection type to the Connections part of the Connection Compatibility Table.\n\nNominal bore size table\nBranch and reducer tables\nPipe data tables\nWall thickness tables.\nNominal bore size table\nNominal bore size table\nBranch and reducer tables\nBranch and reducer tables\nPipe data tables\nPipe data tables\nWall thickness tables.\nWall thickness tables.\nNote:\nThe Nominal Bore Table does not provide wall thickness data in the model, refer to Wall Thickness Table for further information.\nNote: For nominal bores that are not included in the standard nominal values, refer to Create Nominal Bore World for further information.\nNote:\nIf the connection compatibility table is from a read-only Master project, an error message is displayed. The table is displayed and the data in the Connections grid is readable but the table will be in read-only mode.\nNote:\nWhen a connection type is added from the Connections Types list to the Connections grid, it is removed from the Connections Types list and vice versa.\n\n\n\nWall Thickness Table\nPipe Data Table\nCreate Nominal Bore World\nBolt Diameter and Length Tables\nMulti-Purpose Windows\nWall Thickness Table\nCreate Nominal Bore World\nMulti-Purpose Windows\nMulti-Purpose Windows\nMulti-Purpose Windows\nMulti-Purpose Windows\nWall Thickness Table\nPipe Data Table\nCreate Nominal Bore World\nApply\nOK\nCancel\nCoco Table\nBolt Diameter and Length Tables\nTable World\nMulti-Purpose Windows\nNominal Bore Table\nTable World\nTABWLD\nNote\n:\nWall Thickness Table\nNote\n:\nCreate Nominal Bore World\nMulti-Purpose Windows\nSize Range window\nName\nDescription\nUnset\nPurpose\nAvailable Nominal Bores (mm)\nADD >\nNominal Bores\nSize Range\nADD ALL >>\nNominal Bores\nSize Range\nRemove <\nNominal Bores\nSize Range\nRemove All <<\nNominal Bores\nSize Range\nCreate Branch Tables\nBranch Table\nBRTAB\nTable World\nTABWLD\nMulti-Purpose Windows\nBranch Table\nUnset\nPurpose\nAvailable Nominal Bores (mm)\nADD >\nBranch Size\nBranch Table\nADD ALL >>\nBranch Size\nBranch Table\nRemove <\nBranch Size\nBranch Table\nRemove All <<\nBranch Size\nBranch Table\nBranch Table,\n.\nCell Click Action\nBranch Table\nAdd\nMain Bores\nBranch Table\nCell Click Action\nBranch Table\nClear\nBranch Table\nCell Click Action\nBranch Table\nNone\nReducer Sizes\nReducer Sizes\nSpecification creation\nCreate Reducer Tables\nReducer Table\nBranch Table\nReducer Table\na Table World (TABWLD)\nMulti-Purpose Windows\nReducer Table\nBRTAB\nReducer Table\nUnset\nPurpose\nCreate Specification Table\nBranch Table\nECC\nCONC\nSWGE\nSWGC\nCOCO Table\nMulti-Purpose Windows\nConnection Compatibility Table\nNote\n:\nConnections\nConnection Types\nConnection Compatibility Table\nConnection Types\nConnection Compatibility Table\nConnections\nAdd >\nNote\n:\nConnections Types\nConnections\nConnections Types\nAdd >\nConnections\nConnection Compatibility Table\nAdd All >>\nConnections\nConnection Compatibility Table\nRemove <\nConnections\nConnection Compatibility Table\nRemove All <<\nConnections\nConnection Compatibility Table"}
{"Headers": "Bolt Table Utilities", "Content": "Bolting tables are part of the bolt table hierarchy which contains information describing the nature of the bolted connections of piping components in a project. Although the Bolt Table is part of the Catalog database, and so must be set up using AVEVA Catalog, it has been designed for the exclusive use of Isodraft, only a summary is presented here. Refer to Bolting for further information.\nBolt Tables (BLTAB) elements are an administrative element which are used to hold Bolt Length Tables (LTAB) elements, Bolt List (BLIS) elements and Multi Bolt List (MBLI) elements. LTAB elements store Standard Bolt Lengths for specific diameters (DTAB element). BLIS elements are used to group together standard bolt elements (SBOL) and MBLI elements are used to group together multiple bolt elements (MBOL).\n\n\n\n\nBolting"}
{"Headers": "Bolt Sets (BTSE)", "Content": "The Bolt Set (BTSE) element is the administrative element for the catalog bolting information, refer to Bolting Tables for further information.\n\n\n\nBolting Tables"}
{"Headers": "Create Nominal Bore World", "Content": "For users who require bores, that are not included in the standard nominal values, functionality is available for the creation of tables that will hold the required bores in the AVEVA Catalog database.\nWhen being switched from module to module, the Catalog database is scanned for a Nominal Bore World (NBRWLD) element. Purpose on NBRWLD can be set to either BLEN or BDIA depending on whether the elements are being used to store metric/imperial equivalent Bolt Lengths or Bolt Diameters. If so, the nominal bore-checking routine is switched to the user defined nominal bores.\n\nMany multi-purpose windows provide similar functionality through the create and modify options, the functionality is common throughout all disciplines. Refer to Multi-Purpose Windows for further information. A NBRWLD administrative element is added to the database hierarchy and display in the Catalog Explorer and the Bolt Diameter/Length Table is displayed.\n\n\n\nMulti-Purpose Windows\nMulti-Purpose Windows\nCatalog Explorer\nBolt Diameter/Length Table"}
{"Headers": "Wall Thickness Table", "Content": "Wall thickness tables are a reference list of elements with a bore and a wall thickness value. The Create Wall Thickness Table window is displayed with a default name based on the current element and must be created below a TABWLD element in the catalog hierarchy. It is also an administrative element.\n\nMany multi-purpose windows provide similar functionality through the create and modify options, the functionality is common throughout all disciplines. Refer to Multi-Purpose Windows for further information. A Wall Thickness Table is added to the database hierarchy and the Wall Thickness Table window is displayed.\nThe Wall Thickness Table builds a set of wall thickness elements (WTHELE) matching the bore sizes in the specification to which it's applied. The bore sizes selected must match those in the specification from the Available Nominal Bores list.\n\nClick to highlight the desired bores in the Available Nominal Bores (mm) list by left clicking on the desired bore size. Multiple bores can be selected at once by clicking and dragging the mouse pointer down the list.\n\nClick Add > to populate the Nominal Bores column, to add the complete bore list to the Nominal Bore column, click Add All >>.\n\nAfter the addition of the required bores to the Nominal Bores column, the Remove and Remove All options become active allowing the removal of bores from the Nominal Bores list.\nAfter setting the required bores, the Wall Thickness values can be entered. For each nominal bores enter a wall thickness into the corresponding blank field.\n\nWhen all the Wall Thickness values have been entered, click Apply to create the Wall Thickness Table (WHTAB) element in the database hierarchy displayed in the catalog hierarchy.\n\n\n\n\nMulti-Purpose Windows\nCreate Wall Thickness Table\nMulti-Purpose Windows\nWall Thickness Table\nWall Thickness Table\nAvailable Nominal Bores\nAvailable Nominal Bores (mm)\nAdd >\nNominal Bores\nNominal Bore\nAdd All >>\nNominal Bores\nRemove\nRemove All\nNominal Bores\nWall Thickness\nApply\nWall Thickness Table"}
{"Headers": "Pipe Data Table", "Content": "Pipe Data Tables are designed to store bore specific data and are referenced by a specification. Each specification references its own specific pipe data table.\nEach pipe data table owns a number of pipe data elements matching the bore sizes of the specification components. Each pipe data element has attributes to identify wall thickness, corrosion allowance and flange excess allowance and these will be accessible for each component.\nThe Create Pipe Data Table window is displayed with a default name based on the current element and must be created below a TABWLD element in the catalog hierarchy. It is also an administrative element.\n\nMany multi-purpose windows provide similar functionality through the create and modify options, the functionality is common throughout all disciplines. Refer Multi-Purpose Windows to for further information. A Pipe Data Table is added to the catalog hierarchy and the Pipe Data Table window is displayed.\n\nBy default, the Name fields are automatically populated, the Description is Unset and the Purpose is set to PIPE, as the currently active discipline is Piping.\n\n\n\nMulti-Purpose Windows\nPipe Data Tables\nCreate Pipe Data Table\nMulti-Purpose Windows\nPipe Data Table\nName\nDescription\nUnset\nPurpose"}
{"Headers": "Create/Modify Permissible Specifications", "Content": "Use the functionality to restrict the pipe, insulation and tracing specifications available for selection at project level.\n\nNote:\nThis is an administrator function, use to create or modify the specifications available for selection.\n\n\n\nNote\n:"}
{"Headers": "Sloperef", "Content": "Each piping specification in the catalog has a sloperef attribute which is determined by a slope element (SLOELE). When creating a new pipe, the sloperef is set automatically from the sloperef of the specification. If a specification has a sloperef set, this will be transferred onto any new pipes using this specification in the future. Refer to Slope Element and Pipe Slope Element Editor Window for further information.\nThe sloperef can be set in the conventional way using the search tools to find suitable tables. Click Search, the Tasks > Cad Attributes > Search (Slope Element Ref) populates the lower part of the Specification window.\n\nBy default, SLOELE automatically populates the Element Types field. Click Find to search for all SLOELE elements and populates the window.\n\nTo set the sloperef, highlight the required slope table, then click Use Selected.\n\n\n\nPipe Slope Element Editor Window\nSlope Element\nPipe Slope Element Editor Window\nSearch\nTasks > Cad Attributes > Search (Slope Element Ref)\nElement Types\nFind\nUse Selected"}
{"Headers": "The pipe slope", "Content": "The Pipe Slope Element Editor window is a dual purpose window with create (default) or modify functionality.\nIn practice a SLOELE stores 4 angles, during modelling the only angle considered is the default slope angle. The other angles define a range which is checked by Data Consistency Checking Utility (DATACON):\nUse the Slope Mode drop-down to select the determine how the four slope angles are defined in the Pipe Slope Element Editor window.\nminimum slope angle to maximum slope angle is an allowable range\nminimum vertical angle defines a point where the slope is not considered.\nminimum slope angle to maximum slope angle is an allowable range\nminimum slope angle to maximum slope angle is an allowable range\nminimum vertical angle defines a point where the slope is not considered.\nminimum vertical angle defines a point where the slope is not considered.\n1 in\nAngle\nPercent\nValue in.\n1 in\n1 in\nAngle\nAngle\nPercent\nPercent\nValue in.\nValue in.\nNote:\nOfftol is an attribute which allows the direction of a ppoint to vary by a small amount. It is used on piping components where slopes are applied. They are designed to replace zero length bends which are commonly used for slopes. When pipes are sloped, it often means that the welds between the components and tubes need to be adjusted so that a slope is introduced. Offtol controls the angle of this process, in AVEVA Catalog, the Offtol attribute is set to 12 degrees to allow for a maximum possible slope of 1 in 5 (11.7 degrees).\n\n\n\nPipe Slope Element Editor\nNote\n:\nSlope Mode\nPipe Slope Element Editor"}
{"Headers": "Piping tools", "Content": "Piping Tools (utilities) Piping provides functionality to which can be used to convert an older style specification to a new one, view and modify the Isodraft CKey, produce a report detailing the SKEYs and PConns for all the elements in the selected specifications or modify the connection types on the Ppoints of elements.\n\nRefer to Symbol Key Report and Connections for further information.\n\n\n\nSymbol Key Report\nConnections\nSymbol Key Report\nConnections"}
{"Headers": "Convert Spec", "Content": "The functionality available from the Convert Spec window is identical to that from Convert Spec functionality available for selection in the General discipline, refer to Convert Spec for further information.\n\n\n\nConvert Spec\nConvert Spec\nGeneral\nConvert Spec"}
{"Headers": "Keys", "Content": "When generating spools, SPOOLER needs to know what type of connection or joint is been used, this is identified by the Isodraft Connection Key (CKEY) attribute of the COCO element. Refer to Specifying Pipe End Conditions for use by Isodraft for further information.\nTo view and edit the currently configured CKey for the Coco table identified as a CE in the Catalog hierarchy.\n\nClick CE to populate the Edit Ckeys window with the CCTA elements Ckeys (connection type).\n\nUse the part of the Set CKeys part of the Edit CKeys window to filter the CTYPE and CKey attributes displayed, refer to Filter CKey for more information. Modify the CKey attribute used, refer to Filter CKey for further information or delete selected entries in the CKeys list.\n\n\n\nFilter CKey\nFilter CKey\nSpecifying Pipe End Conditions for use by Isodraft\nCE\nEdit Ckeys\nSet CKeys\nEdit CKeys\nFilter CKey\nFilter CKey"}
{"Headers": "A catalog database", "Content": "A Catalog database may contain a single \u2018universal\u2019 catalog, but it will more commonly contain a general catalog plus one or more specialized catalogs specific to particular design functions.\nSections and Categories are administrative elements which separates particular types of catalog data into logical parts of the database hierarchy. Sections, which subdivide an overall CATA, are obligatory; Categories, which subdivide Sections, are optional (although their use is recommended).\nIn the case of using the Equipment discipline, elements are stored in the hierarchy as templates or components under template or component categories. The functionality available to create template or component categories are identical to that described in Multi -Purpose windows, refer to Multi-Purpose Windows for further information.\n\n\n\nMulti-Purpose Windows\nMulti-Purpose Windows"}
{"Headers": "Table Group", "Content": "Selection Tables (specification) are general purpose tables which can be used to control the choice of components available for selection by populating the table with specific General Parts (GPARTs) for use in the Design. Refer to Selection Tables for further information.\nUse table group functionality to create administrative elements for the purpose of selecting equipment and equipment electrical components using specifications. Refer to Selection Table Hierarchy for further information.\nThe Create Table Group window creates a new table group element which is an administrative element in the catalog hierarchy. The functionality is common throughout all disciplines, refer to Multi-Purpose Windows for further information.\n\nOnce the new table group administrative element is created, the TABGRO window is displayed. The TABGRO window acts as a task hub for all the tasks associated with the creation and modification of selection table(s) (CTABLE).\n\nTable Attributes\nUse the Table Attributes part of the table group window to define the general attributes for the selection table. It is recommended to give individual selection tables a unique description.\n\nTable Header\nUse the Add Heading part of the TABGRO window to define a description for the table header (TABHEA) element, as there can be many selection tables within one group it is recommended to give each selection table in the group an unique description.\n\nOnce the description has been defined, the window is then displayed as Edit Heading. The description previously defined is displayed along with an auto generated name. The Purpose defines in which discipline the selection table will be displayed, by default it is blank.\n\nUse the Edit Questions part of the TABGRO window to add, remove or modify TABHEAQ elements.\n\nTable Item\nTable items (TABITE) have a reference to the corresponding part and hold the selection answers for that part (TABITEM).\nUse the search criteria to find the GPART elements that will appear in the table, click Add Items (Search), the functionality available is common throughout AVEVA products. Refer to Search for further information.\nTo add the currently selected GPART items in the Catalogue Explorer to the list of TABITE elements in the table, click Add Items (from CE) or navigate to a GPART element or to a Part Hierarchy Element (PRTELE) element that owns GPARTelements and select these. For a detailed explanation of GPARTS refer to Create Part Family for more information.\n\nAdd the selection data (answers (entry in table rows)) to columns (questions (column headers)) in the table. Select one or more entries in the list of table items. Click Edit Selection to display the Edit Items part of the TABGRO window which allows answer values to be set for each of the selected table items.\nIn the answer field enter a value if desired, such as VPUMP, this will appear in the selection table presented in the Equipment discipline and can be used for filtering the selection of equipment items available to design users.\n\nNote:\nA Table Group (TABGRO element) must be created below a Specification World (SPWL).\nNote:\nThe selection criteria or filters are defined by the questions and answers in the CTABLE, the table header element holds the question (TABHEAQ) column heading) and the table items (TABITE) elements have the answers (TABITEM) entry in table row).\nNote:\nThere is a special case for a Question with Purpose TYPE. This will be used by the equipment selection application to filter automatically on User Defined Element Type. For example, if the project has a User Defined Element Type (UDET) :VPUMP, then the Equipment application user will be presented only with Table Items that have answer VPUMP to the TYPE question.\n\n\n\nSelection Tables\nMulti-Purpose Windows\nSearch\nCreate Part Family\nSelection Tables\nSelection Table Hierarchy\nCreate Table Group\nMulti-Purpose Windows\nNote\n:\nTable Group\nSpecification World\nTable Attributes\nTable Attributes\nTable Header\nAdd Heading\nEdit Heading\nEdit Questions\nNote\n:\nTable Item\nSearch\nAdd Items (from CE)\nCreate Part Family\nEdit Selection\nEdit Items\nNote\n:"}
{"Headers": "Nozzle Specification", "Content": "Use the Nozzle Specification window to build up a specification by reference to the attribute settings of existing nozzles in the catalog database. The specification simply acts as an index to allow any required nozzle to be located easily.\nTo build such a specification, navigate to the catalog element (CATA, SECT or CATE) that contains all nozzles that are to be accessed using the new specification.\n\nUse the upper part of the window to specify details of the overall SPEC element to be created; the lower part lists all nozzles below the current level in the catalog which can be used to specify which ones are to be included in the specification.\nIf required, change the default settings for Spec, Description and Standard.\nThe Spec World option lists all available SPWL elements for the appropriate generic type (as controlled by the setting of the PURP attribute). If more than one is available, select the one below that the new SPEC element is to be created.\nThe left-hand list is populated with the category (CATE) elements, while the right-hand list is populated with the nozzles in the selected category. By default, all listed nozzles are incorporated into the specification. To prevent one or more nozzles or complete categories being included in the specification, select them in the relevant list and click Remove below that list. The 'removed' entries will only be shown (marked with a * symbol) if the Hidden option above the list is set to On. To reverse the process, select a 'removed' entry and click Re-Instate.\nWhen the lists are populated with only those nozzles which can be selectable using the new specification, click OK to build the specification.\nCreate Specification\nThe Create Specification window available in the Spec Generator application is used when creating Specifications for Nozzles or Structural Steel.\nWhile within Spec Generator, in the Create group, select Specification to display the Create Specification window.\n\nIn principle, an empty Specification element can be created and then modify it by reference to any specified catalog item. In practice, you can only create Specifications for structural profiles or equipment nozzles using this method.\nTo create a Specification in this way (perhaps for later modification), check the CE is a SPWL element.\nUse a meaningful Name and Description to identify the specification amongst many others.\nThe Generic Type option currently restricts choice to Equipment (with a corresponding Spec Type of Nozzles) or Structural Steel (with a corresponding Spec Type of Steel Sections, that is Profiles). Select the required option.\nNote:\nThe functionality is only available in the Equipment discipline and at least one Specification World with its PURP attribute set to indicate its suitability for storing nozzle specifications has been created. Set the purpose for NOZZLE spec to EQUI, and the SPEC purpose set to NOZZ.\n\n\n\nNozzle Specification\nNote\n:\nSpec\nDescription\nStandard\nSpec World\nRemove\nHidden\nOn\nRe-Instate\nOK\nCreate Specification\nCreate Specification\nSpec Generator\nCreate\nSpecification\nCreate Specification\nName\nDescription\nGeneric Type\nEquipment\nSpec Type\nNozzles\nStructural Steel\nSpec Type\nSteel Sections"}
{"Headers": "Equipment Electrical Component Selection", "Content": "Equipment elements can contain electrical component (ELCONN) elements that represent electrical components within an equipment. Cables are connected to ELCONN elements. The Equipment application allows Table Groups to be created for the purpose of selecting equipment electrical components in the Model application. This is achieved by using the Table Group window described in the previous section. The only difference is in the Sub-Discipline must be set to ELEC on the Table attributes sub window. For other electrical elements, refer to Electrical for further information.\n\n\n\n\nElectrical\nTable Group\nElectrical"}
{"Headers": "features to AVEVA", "Content": "When working within AVEVA Electrical, in AVEVA Catalog, addition features are available specific to Electrical discipline.\nA Catalog database may contain a single \u2018universal\u2019 catalog, but it will more commonly contain a general catalog plus one or more specialized catalogs specific to particular design functions\nSections and Categories are administrative elements which separates particular types of catalog data into logical parts of the database hierarchy. Sections, which subdivide an overall CATA, are obligatory; Categories, which subdivide Sections, are optional (although their use is recommended). In this case, Cable Tray, Cable Cores or Cable Node Representation.\nElectrical elements are created and stored in the hierarchy as templates or components under template or component categories. Refer to Electrical Component for further information.\n\n\n\nCable Tray\nCable Cores\nCable Node Representation\nCable Tray\nCable Cores\nCable Node Representation\nElectrical Component"}
{"Headers": "Cable Tray", "Content": "Use the Create Category window to create a cable tray element (CTRAY), including types such as elbows, tees, crosses, risers, straights and so on. By default, the category name has a CATE extension and the purpose is set to TRAY, the functionality is common throughout all disciplines, refer to Multi-Purpose Windows for further information.\n\nThe definition of cable tray elements is as in other modules, is a task of building up the model data using the references and modelling techniques, refer to Model View for further information.\n\nOnce defined all elements can then be used in other catalog element structures, for example, General Parts (GPARTs), Table Groups (TABGROs) and subsequently used in Model using appropriate selection techniques.\n\n\n\nMulti-Purpose Windows\nModel View\nCreate Category\nMulti-Purpose Windows\nModel View"}
{"Headers": "Cable Cores", "Content": "Use the Create Category window to create a cable core element (CORE). By default, the category name has a CATE extension and the purpose is set to CORE, the functionality is common throughout all disciplines, refer to Multi-Purpose Windows for further information.\n\nThe definition of cable core elements is as in other modules, is a task of building up the model data using the references and modelling techniques, refer to Model View for further information. The definition of cores is slightly different to other category types, and includes the additional function shown in the category window.\n\nAn option for Cable Core Set is available in the Model References part of the category window.\nCable Core Set (CCORSET) elements are specific to the cable element, and contains Cable Core Elements (CABCOR) which contain information such as number, purpose, description, core tag and core group. Clicking on the CCORSET displays the following sub window:\n\nTo create a new cable core, click New, the Cable Core window is automatically populated with a number and type by default.\n\nThe following fields are also available:\nNumber (NUMB)\nName of element is specified or hierarchy description\nPurpose (PURP)\nDescription code word\nDescription (DESC)\nDescription of element\nCore Tag\nCable core tag\nCore Group\nCable core conductor group\nNumber (NUMB)\nName of element is specified or hierarchy description\nPurpose (PURP)\nDescription code word\nDescription (DESC)\nDescription of element\nCore Tag\nCable core tag\nCore Group\nCable core conductor group\nThe above screenshot shows a populated cable core window which would result in the following database hierarchy:\n\nThe SCOM here would typically reference a CCORSET, if more than one cable core set is required, the SCOM can be copied using the normal copy routine in the category grid.\n\nUse the normal copy functionality from main menu for the CCORSET element in the category, then use the category window to re-reference the new CCORSET element.\n\nOnce defined all elements can then be used in other catalog element structures, for example, General Parts (GPARTs), Table Groups (TABGROs) and subsequently used in Model using appropriate selection techniques.\n\n\n\nMulti-Purpose Windows\nModel View\nCreate Category\nMulti-Purpose Windows\nModel View\nCable Core Set\nModel References\nNew,\nCable Core"}
{"Headers": "Cable Node Representation", "Content": "Use the Create Category window to define the necessary representation of the cable nodes in design, which will eventually be drawn on drawings as symbols. By default, the category name has a CATE extension and the purpose is set to REPR, the functionality is common throughout all disciplines, refer to Multi-Purpose Windows for further information.\n\nOnce defined all elements can then be used in other catalog element structures, for example, General Parts (GPARTS), Table Groups (TABGROs) and subsequently used in Model using appropriate selection techniques.\nElements would be defined as in the example shows above, the geometry is defined to make the symbol as you wish to see it eventually in design.\nOnce defined as SCOM elements, it would be then required to create GPART Family, example.\n\n\n\nMulti-Purpose Windows\nCreate Category\nMulti-Purpose Windows"}
{"Headers": "Interference Class Defaults", "Content": "Use the functionality available from the Interference Class Defaults window to add, delete or reload rules.\n\nClass\nThe Classes available for selection from the drop-down list are defined by the Cable Properties Elements (CABDATA) in the MASTER/PROP world.\n\nMaterial type\nThe Material types available for selection from the drop-down list are Perforated and Unperforated.\n\nCalculation\nThe Calculations (rules for the fill level checks) are available for selection from the drop-down list.\n\nThere are three \u2018out of the box\u2019 calaculations (rules), see below, however if required, calculations can be added to the cblCalculationStore in the following location PMLLIB\\design\\objects\\cblCalculationStore.pmlobj.\n\nAll the calculations are listed in PMLLIB\\design\\objects\\cblCalculationStore.pmlobj which can be found using the window code. Each calculation is one method in the cblCalculationStore, to add a new calculation, create a method in that file following the example of the existing methods, then register it to the list of calculations inside the method .constructCalculationList().\n\nReload classes\nUse to reload the rules in the Interference Class Defaults window.\nAdd a rule\nUse to add a new rule to the Interference Class Defaults window, select a Class, Material and Calculation available for selection.\nDelete a rule\nUse to delete a rule from the Interference Class Defaults window, click to select a rule in the window then click the button. A Confirm window is displayed, click Yes to delete the rule or No to discard any changes.\n\nReload classes\nUse to reload the rules in the Interference Class Defaults window.\n\nAdd a rule\nUse to add a new rule to the Interference Class Defaults window, select a Class, Material and Calculation available for selection.\n\nDelete a rule\nUse to delete a rule from the Interference Class Defaults window, click to select a rule in the window then click the button. A Confirm window is displayed, click Yes to delete the rule or No to discard any changes.\nRefer to Cable Properties Element (CABDATA) for further information.\nNote:\nAs long as the added calculations satisfy the specified criteria the fill level calculations will be successful when selected from the Interference Class Defaults window.\n\n\n\nInterference Class Defaults\nClass\nCable Properties\nMASTER/PROP\nMaterial type\nMaterial types\nPerforated\nUnperforated\nCalculation\nCalculations\nNote\n:\nInterference Class Defaults\nReload classes\nInterference Class Defaults\nAdd a rule\nInterference Class Defaults\nClass\nMaterial\nCalculation\nDelete a rule\nInterference Class Defaults\nConfirm\nYes\nNo"}
{"Headers": "working with HVAC", "Content": "When working within the HVAC - Preview discipline of AVEVA Catalog, specific hierarchy can be created and additional tools specific to piping are available.\nAll HVAC components used in the design are selected from the Catalog database by setting the Specification Reference for the corresponding design element so that it points to the required catalog entry.\nEach catalog item is defined in terms of two subsidiary sets of data:\nTo enable the HVAC Preview functionality in Paragon, select PROJECT > Options > Discipline, then click to check the Enable check box.\n\nA Geometry Set, which defines the overall physical shape of the item in terms of a set of 3D basic shapes (known as primitives). A geometry set can include negative 3D primitives to represent holes.\nA Point Set, which defines a number of reference points and directions superimposed on the geometric shape so that individual parts of that shape can be identified and manipulated. These reference points, each of which represents a 1D point position, are called p-points.\nA range of catalog components with similar overall geometry will all reference the same geometry set and point set, so that the amount of data needed to represent all possible items is kept to a minimum. The dimensions of the items are not fixed in the catalog but are expressed in terms of Design parameters. dimensions are allocated to these parameterised dimensions when the item is used in a specific part of the design model: they may either be set explicitly or derived from associated dimensions of other design components to which the item is to be connected.\nA Geometry Set, which defines the overall physical shape of the item in terms of a set of 3D basic shapes (known as primitives). A geometry set can include negative 3D primitives to represent holes.\nA Geometry Set, which defines the overall physical shape of the item in terms of a set of 3D basic shapes (known as primitives). A geometry set can include negative 3D primitives to represent holes.\nA Point Set, which defines a number of reference points and directions superimposed on the geometric shape so that individual parts of that shape can be identified and manipulated. These reference points, each of which represents a 1D point position, are called p-points.\nA Point Set, which defines a number of reference points and directions superimposed on the geometric shape so that individual parts of that shape can be identified and manipulated. These reference points, each of which represents a 1D point position, are called p-points.\nA range of catalog components with similar overall geometry will all reference the same geometry set and point set, so that the amount of data needed to represent all possible items is kept to a minimum. The dimensions of the items are not fixed in the catalog but are expressed in terms of Design parameters. dimensions are allocated to these parameterised dimensions when the item is used in a specific part of the design model: they may either be set explicitly or derived from associated dimensions of other design components to which the item is to be connected.\nA range of catalog components with similar overall geometry will all reference the same geometry set and point set, so that the amount of data needed to represent all possible items is kept to a minimum. The dimensions of the items are not fixed in the catalog but are expressed in terms of Design parameters. dimensions are allocated to these parameterised dimensions when the item is used in a specific part of the design model: they may either be set explicitly or derived from associated dimensions of other design components to which the item is to be connected.\n\n\n\nHVAC - Preview\nHVAC Preview\nPROJECT > Options > Discipline\nEnable"}
{"Headers": "Specifications", "Content": "HVAC specifications are much like piping specifications, AVEVA provide three \u2018out of box\u2019 specifications:\n\nThe functionality available from the AVEVA Specification window is identical to that previous described, refer to Specifications for further information.\nMandatory headings in the specification table are:\nPSHA\nComponent shape - RECT, CIRC or FLAT.\nPWID\nDuct width or diameter for circular components.\nPHEI\nDuct height (for circular components set to 0).\nPSHA\nComponent shape - RECT, CIRC or FLAT.\nPWID\nDuct width or diameter for circular components.\nPHEI\nDuct height (for circular components set to 0).\n\n\nAVEVA-RECTANGULAR\nAVEVA SIMDUCT-CLASS-C\nAVEVA SIMDUCT-CLASS-F.\nAVEVA-RECTANGULAR\nAVEVA-RECTANGULAR\nAVEVA SIMDUCT-CLASS-C\nAVEVA SIMDUCT-CLASS-C\nAVEVA SIMDUCT-CLASS-F.\nAVEVA SIMDUCT-CLASS-F.\nNote:\nIn AVEVA Catalog - the POINTS for pHeight, pWidth (for circular). The PDShape must currently be set using the Attributes window (if it is not in the Catalog window).\n\n\n\nSpecifications\nAVEVA Specification\nSpecifications\nNote\n:\nAVEVA Catalog\nAttributes\nCatalog"}
{"Headers": "HVAC Standards", "Content": "HVAC standards are a collection of specifications and customer settings available for selection in the HVAC Editor window. Use the functionality from the HVAC Standards window to add company specific specifications, custom settings and to link a custom setting to a specification (for linking refer to Link Custom Settings to Specification for further information).\n\nNote:\nFor this release both a specification and a custom settings must be selected in the HVAC Standards window.\n\n\n\nHVAC Editor\nHVAC Standards\nLink Custom Settings to Specification\nNote\n:\nHVAC Standards"}
{"Headers": "HVAC Custom Setting", "Content": "HVAC custom settings is the detailing specification from the previous version of HVAC. These settings specify the maximum length (for straight HVAC ducting), material, gauge, size, joint type, sheet material and which default to use for the selected custom setting.\nUse the functionality available form the HVAC Custom Settings window to add or delete settings for Rectangular, Circular and Flat Oval components.\n\nLink Custom Settings to Specification\nUse this functionality to define which custom settings are associated with a particular specification. This means in the model application when choosing a custom component whilst working in a particular specification, the custom component can be chosen with a custom setting which is linked with the current specification, for example: has the expected material and gauge.\nNote:\nFor this release, gauge, stiffener and max spacing may be set in a custom setting but these are not used when creating custom components in the model.\n\n\n\nHVAC Custom Settings\nNote\n:\nLink Custom Settings to Specification"}
{"Headers": "Convert Custom Setting", "Content": "Use the functionality available from the HVAC Custom Setting Converter window to covert a detailing specification from the previous version of HVAC (in the previous version a text file) and transfer it to Paragon. Where each custom setting is stored under a Catalog (CATA) element as a SECT.\n\nFrom\nFile\nNavigate to location of the required detailing specification.\nSheet Material\nThe material (custom setting) associated with the detailing specification is displayed.\nFilename\nThe file name of the detailing specification is displayed.\nTo\nCurrent Cata\nUse to specify where the detailing specification will be place once converted.\nRename\nIf required rename the detailing specification.\nDescription\nEnter a description for the converted detailing specification.\nSheet Material\nIf required, select a new custom setting for the material, available material settings are:\nA material from a Material World (MATW) element must be selected for the newly converted custom setting, any materials (for example: SOLI) with purpose HVAC can be selected here.\n\nFile\nNavigate to location of the required detailing specification.\nSheet Material\nThe material (custom setting) associated with the detailing specification is displayed.\nFilename\nThe file name of the detailing specification is displayed.\n\nCurrent Cata\nUse to specify where the detailing specification will be place once converted.\nRename\nIf required rename the detailing specification.\nDescription\nEnter a description for the converted detailing specification.\nSheet Material\nIf required, select a new custom setting for the material, available material settings are:\nA material from a Material World (MATW) element must be selected for the newly converted custom setting, any materials (for example: SOLI) with purpose HVAC can be selected here.\nOn successful conversion of the previous detailing specification a message is displayed in the Messages pane of the HVAC Custom Setting Converter window.\n\n\n\n\nHVAC Custom Setting Converter\nFrom\nFile\nSheet Material\nFilename\nTo\nCurrent Cata\nRename\nDescription\nSheet Material\nMessages\nHVAC Custom Setting Converter"}
{"Headers": "HVAC Defaults", "Content": "Each custom setting has defaults associated with it, AVEVA supply two \u2018out of the box\u2019 defaults: AVEVAHVACMDFLTS (AVEVA HVAC metric defaults) and AVEVAHVACIDFLTS (AVEVA HVAC imperial defaults). These defaults hold default values for dimensions of the custom (parameterized) components.\n\n\n"}
{"Headers": "Working with structures", "Content": "When working within structures, in AVEVA Catalog, addition features are available specific to structures.\n\n\n"}
{"Headers": "Specific structures hierarchy", "Content": "The structures specific hierarchy contains information such as profiles, joints and fittings which are part of the catalog database. A profile, joint or fitting category must reside below a STSE which in turn must reside below a CATA element.\n\n\n\n"}
{"Headers": "Profile", "Content": "A structural profile is a 2D cross-sectional shape defined by a series of vertex elements placed at each change in direction of the shape.\nThe shape must have a minimum of three vertices. Each vertex is defined with the following attributes\nWhen defining the vertices the following practices should be observed to make sure the correct results are achieved:\nWhen creating an enclosed shape consider using two touching SPRO components to simplify the shape.\nProfiles require a Geometry Set, a Pline Set, a Data Set and a Specification to function correctly. The profiles are usually defined parametrically such that a single definition may be used for a wide variety of similar shaped profiles with different dimensions.\nAll structural profiles have a Generic Type set via the GTYPE attribute of the SPRF element. A Gtype is an abbreviated description (a maximum of four letters) that refers to a generic shape of a profile, for example a BEAM, TUBE, ANG and so on.\nThere are a number of reserved GTYPES as listed below:\nANGL\nEqual or Unequal Angle\nPLTG\nPlate Girder\nBFLA\nBulb Flat\nBox Girder\nRBAR\nRound Bar\nBOXG\nRTUB\nRectangular or Square Tube\nCEE\nFlanged C Profile\nTFC\nTapered Flange Channel\nCTUB\nCircular Tube\nTFI\nTapered Flange I\nFBAR\nFlat Bar\nTFT\nTapered Flange Tee\nHBAR\nHexagonal Bar\nTFTW\nTapered Flange, Tapered Web Tee\nPFC\nParallel Flange Channel\nTWT\nTapered Web Tee\nPFI\nParallel Flanged I\nZED\nZ Profile\nPFT\nParallel Flange Tee\n\n\nThe reserved Gtypes are held in the file %AVEVA_DESIGN_DFLTS%UI-GTYPE-SELEM. This is a read only file. If new Gtypes are required then the read only attribute must be removed from the file and then use the to edit the list.\nVertex numbering should maintain rotational order, either clock wise or anti-clockwise.\nLines between vertices should not self intersect or cross each other.\nVertex numbering should maintain rotational order, either clock wise or anti-clockwise.\nVertex numbering should maintain rotational order, either clock wise or anti-clockwise.\nLines between vertices should not self intersect or cross each other.\nLines between vertices should not self intersect or cross each other.\n\n\n\nGtype\nDescription\nGtype\nDescription\nANGL\nPLTG\nBFLA\nRBAR\nBOXG\nRTUB\nCEE\nTFC\nCTUB\nTFI\nFBAR\nTFT\nHBAR\nTFTW\nPFC\nTWT\nPFI\nZED\nPFT"}
{"Headers": "Joints", "Content": "Joint (JOIN) - a 3D structural Component defining a physical means of attaching one Section to another. It consists of a list of component parameters and references to a Structural Pointset element, a 3D Pointset element and a 3D Geomset element. The two Pointsets and the Geomset make use of the component parameter values in defining the size and geometry of the Component. Refer to Joint (JOIN; SJOI) for further information.\nStructural joints are catalog components that are referenced via the Spref attribute of an SJOI element and are associated with the owning and attached members of the connection.\nJoints may be complex or a simple, depending on the engineering requirement, that is the time and effort spent on their creation. Joints can consist of positive and/or negative 3D geometry components and may be any shape that can be defined by these components.\nJoints are usually defined parametrically such that a single definition may be used for different size combinations of the Owning and Attached section\u2019s Gtype.\n\n\n\nJoint (JOIN; SJOI)\nJoint (JOIN; SJOI)"}
{"Headers": "Merged Joints", "Content": "Merged joint design templates and catalog specifications are provided in the sample data, example PML callback functions for three different types of merged joint are also included.\nThe design templates, catalog data and PML callbacks are all linked and required to run the merged joint functionality. For example, the system calls a PML function when a design template is instanced, and the created MFIX element references a specification component.\n\n\n\n"}
{"Headers": "Fitting", "Content": "Fitting (FITT) - a 3D structural Component defining an object which is physically attached to a Section but is not part of the structure formed by Sections and Joints. For example, a Fitting may be used to attach a pipe hanger to a Section. The element consists of a list of component parameters and references to a 3D Pointset element and a 3D Geomset element. The Pointset and Geomset make use of the component parameter values in defining the size and geometry of the Component. Refer to Fitting (FITT; SFIT) for further information.\n\n\n\nFitting (FITT; SFIT)\nFitting (FITT; SFIT)"}
{"Headers": "Templates", "Content": "It is possible to define parameters for a template which can later be used in Model. A Template Category must reside below a STSE which in turn must reside below a CATA element. The Create Structural Category window is similar in layout to a standard , refer to Create Parts from Template Area for further information.\n\n\n\nCreate Structural Category\nCreate Parts from Template Area"}
{"Headers": "Rule Sets", "Content": "Rules can be created and used for a variety of purposes. The primary purpose of rules is to set the default value of design parameters in catalog and template items. Rules like these are useful for properties which must be aligned with a standard but cannot be derived formulaically.\nFor example, below is a table defining the number of bolt hole rows needed for a joint connecting two I-Sections:\n150mm - 200mm\n2\n200mm - 300mm\n3\n300mm - 500mm\n4\n> 500mm\n5\nThis logic could have previously been achieved using a number of IFTRUE expressions, or by manual entry of a design parameter when creating every instance of the joint. Using the rule set functionality, this logic can instead be stored in the catalog and applied to every joint as it is created, to set the default value for the number of bolt-hole rows.\nA Rule Set World (RLSWL) element can be created directly under a WORLD element to store Rule Set (RLSET) elements in a generic location.\nA RLSET element contains a collection of Rule (DRULE) elements which all have the same purpose.\n\n\n"}
{"Headers": "Understanding Parameters", "Content": "There are several different types of parameters available in Paragon. Profile geometry components normally only use those defined for the profile, however, Design Parameters may be used.\n\n\n"}
{"Headers": "attributes for 2D and 3D", "Content": "2D and 3D geometry components have a number of attributes that control the representation in the graphics window. The most important of these attributes are:\nTubeflag\nThe Tubeflag attribute may be set to TRUE or FALSE (the default) and is effectively an ON/OFF flag for component visibility. For structural geometry components it is essential that Tubeflag is set to TRUE, i.e. ON.\nLevel\nThe Level attribute contains two numbers indicating the inclusive range of the drawing levels that the component will be displayed on, e.g. if a components Level attribute is set to 4 8, the component will be visible on drawing levels 4 through 8 inclusive in the graphics window.\nFor SPRF components it is usual to create three geometry definitions with the appropriate components on different drawing levels, for example:\n\nSimplified: Level 0 \u2013 4 Obstruction value 0\nThis representation is used in Draft if an isometric view of the profile is required.\n\nActual: Level 5 \u2013 8 Obstruction value 2\nThis representation is used for most 3D and 2D graphics as it is the true representation of the profile.\n\nObstruction: Level 9 -10 Obstruction value 1\nThis representation is used for the obstruction volumes of the profile.\nObstruction\nThe Obstruction attribute informs the clash detection facility whether a geometry component should be considered as:\nHard\nObstruction value of 2\nSoft\nObstruction value of 1\nNone\nObstruction value of 0\nHard\nObstruction value of 2\nSoft\nObstruction value of 1\nNone\nObstruction value of 0\nThe SANN, SREC and SPRO creation sub forms have a Representation option that enables pre-set values for Level, Obstruction and Tubeflag to be set. The following table gives the details of the Representation available:\nDefault\n0-10\n2\nFALSE\nProfile Obstruction\n3-5\n2\nTRUE\nProfile Detail\n6-8\n0\nTRUE\nProfile Centerline\n6-8\n0\nFALSE\nPiping Obstruction\n0-10\n2\nFALSE\nPiping Reserved\n0-10\n1\nFALSE\nPiping Detail\n0-10\n2\nTRUE\nPiping Centreline\n0-10\n0\nFALSE\nDetail with No Obst\n2-10\n0\nTRUE\nDetail Volume\n2-10\n2\nTRUE\nObstruction Volume\n9-10\n2\nTRUE\nInsulation Volume\n7-10\n1\nTRUE\nReserved Volume\n8-10\n1\nTRUE\n\n\n\n\nTubeflag\nLevel\nObstruction"}
{"Headers": "SLH Tasks", "Content": "Use the SLH Catalog Tasks window to create parts and components which are used by defaults and assemblies in the SLH application.\nAll the tasks that a user would carry out that are associated with the creation or modification of parts or components are available for selection from this central window, which acts as a task hub.\n\nNote:\nCreate or navigate to the required SLH Catalog hierarchy in the Catalog Explorer.\n\n\n\nSLH Catalog Tasks\nNote\n:\nCatalog Explorer"}
{"Headers": "Components", "Content": "From the Categories part of the SLH Catalog Tasks window, select Create alongside the Treads field. The Create SLH Tread Category window is displayed.\n\nEnter the Name to be assigned to the new SLH Catalog Component and enter a Description (text description of the catalog).\nUse the Stair or Step Ladder radio buttons to create a SLH Catalog component for either a stair flight or a step ladder.\nUse the Variable or Fixed radio buttons to fix or allow you to modify the dimensions and attributes of the SLH Catalog Component.\nClick Create to create a Catalog SLH Category (SCTA element) in the database hierarchy. Refer to Catalog Sections (SECT and STSEC) and Categories (CATE and STCA) for further information. The Model View window of the SLH Catalog Component is displayed.\nOr\nClick Task List to return to the SLH Catalog Tasks window.\nThe Model View window of the SLH Catalog Component is populated with parameters which define the size, geometry and other characteristics of components. They are used in setting the attributes of the Pointsets, Geomsets and Datasets to which component elements refer.\nRefer to Catalog Sections (SECT and STSEC) and Categories (CATE and STCA), Elements Used in Both Types of Catalog Section/Category and Elements Used in Structural Sections/Categories.\n\nNote:\nThe Stair and Step Ladder radio buttons are only available for SLH Tread Catalog components.\n\n\n\nCatalog Sections (SECT and STSEC) and Categories (CATE and STCA)\nCatalog Sections (SECT and STSEC) and Categories (CATE and STCA)\nElements Used in Both Types of Catalog Section/Category\nElements Used in Structural Sections/Categories\nCategories\nSLH Catalog Tasks\nCreate\nTreads\nCreate SLH Tread Category\nName\nDescription\n.\nStair\nStep Ladder\nNote\n:\nStair\nStep Ladder\nVariable\nFixed\nCreate\nCatalog Sections (SECT and STSEC) and Categories (CATE and STCA)\nModel View\nTask List\nSLH Catalog Tasks\nModel View\nCatalog Sections (SECT and STSEC) and Categories (CATE and STCA)\nElements Used in Both Types of Catalog Section/Category\nElements Used in Structural Sections/Categories"}
{"Headers": "Component Parts", "Content": "Component Parts (GPART) elements are used in the catalog to fully describe the SLH components, the GPART elements reference SLH templates and SLH component (SFIT) elements which are used by defaults and assemblies.\nThe GPART element has the same standard attributes as a Specific Component (SPCO), including Catalog Reference (CATREF), DETREF, Material Text (MATXT), Component Properties (CMPREF) and Bolt Reference (BLTREF), along with other attributes specific to the Part.\nParts can be added to the Selection Tables for selecting Parts in the design module, and these can be used for all disciplines except piping.\nThere are many different combinations of SLH catalog component parts that can be created, because of this the Paragon application uses a common layout for the windows that are presented to you. For the same reason this document only includes a detailed description of how to create one specific type of SLH catalog component parts. The information can be applied to the same processes that are used to create all other types of SLH catalog components parts.\nNote:\nThe PURPOSE attribute determines what the GPART element is used for in SLH.\n\n\n\nNote\n:"}
{"Headers": "Structural Specifications", "Content": "Specific features are available for the creation and modification of structural specifications when working within structures.\n\n\n"}
{"Headers": "Import Automatic Joint Specification", "Content": "Use the Automatic Joint Spec window to import an automatic joint specification file. The automatic joint specification is created as a SPEC element below the currently selected SPWL element in the hierarchy. Refer to Create Specification World for further information.\n\nType a path and filename in the field or click Open File to navigate to the required location and select the automatic joint specification file.\nCreates the automatic joint specification.\nIf a SPWL element is not currently selected in the hierarchy, an error message is displayed.\n\n\n\n\nCreate Specification World\nAutomatic Joint Spec\nCreate Specification World\nOpen File"}
{"Headers": "Working with supports", "Content": "When working within supports, in AVEVA Catalog, additional features are available that are specific to supports.\n\n\n"}
{"Headers": "Administration Data", "Content": "Controls some of the design limits within which supports can be created and sets the criteria that the Supports application uses to locate support zones.\nThe default values/settings that display on the windows are those that exist when the Supports application is first installed.\nNote that the user can modify some of the defaults on the Options(1) tab using the Supports Application Defaults window (refer to Application Defaults for further information).\nThe Supports Admin Data window modifies values in /MDS/OPTION/DEFAULTS, which are the defaults that are set for the Supports Application Defaults window in Model.\nChanges made are only applied to the database when Apply is clicked. Cancel removes the window. If changes have been made, but not applied, a window displays asking if the changes are to be applied before exiting.\n\n\n\n\nOptions(1)\nSupports Application Defaults\nApplication Defaults\nSupports Admin Data\nSupports Application Defaults\nApply\nCancel"}
{"Headers": "Administration option 1", "Content": "The defaults on the Options (1) tab are grouped into three sections: Application Tolerances, Hangers and Framework Connection Details.\n\n\n\nOptions (1)\nApplication Tolerances\nHangers\nFramework Connection Details"}
{"Headers": "Administration option 2", "Content": "The Options (2) tab displays further default options.\n\n\n\n\nOptions (2)"}
{"Headers": "Zone ID", "Content": "The defaults on the Miscellaneous tab are grouped into three sections: Form Size Control, Active Icons and Zone ID.\n\nZone ID\nThe settings within the Zone ID section represent the criteria that the Supports application uses to select suitable zones for creation of support frameworks. Supports uses the attributes and values to determine the list of zones where support frameworks and hangers can be created.\n\n\n\nMiscellaneous\nForm Size Control\nActive Icons\nZone ID\nZone ID"}
{"Headers": "Active Standards", "Content": "Sets the active state of all support types in the catalog, this controls the availability of supports for use on the project by the user.\nTabs along the top of the window allow you to select the support type and the list of available supports displays the corresponding supports. The active status for each support is indicated by the colour of the first column, green indicates active and amber indicates inactive. Multiple supports can be selected in the list of available supports and you can Activate or Deactivate them respectively. If a single support is selected, the active status of individual bore sizes can also be defined using the list of available bore sizes.\nChanges made are only applied to the database when Apply is clicked. Cancel removes the window. If changes have been made, but not applied, a window displays asking if the changes are to be applied before exiting.\nIf any other windows that have similar functionality are open, for example:\nYou are asked if that window can be closed.\n\nClick Yes to close the window and open the Supports Active Standards window.\nClick No or Cancel to leave the original window open and cancel the process.\nIf you select Yes and changes on the original window are not applied, you are asked to apply changes.\n\nClick Yes to apply the changes and open the Supports Active Standards window.\nClick No to cancel the changes and open the Supports Active Standards window.\nClick Cancel to leave the original window open and cancel the process.\n\nClick Full to make all supports active, click Brief to activate a small subset of supports for demonstration purposes.\nAncillary Data\nHanger Data\nStructure Data\nTrunnion Data\nAncillary Data\nAncillary Data\nHanger Data\nHanger Data\nStructure Data\nStructure Data\nTrunnion Data\nTrunnion Data\n\n\n\nAncillary Data\nHanger Data\nStructure Data\nTrunnion Data\nActivate\nDeactivate\nApply\nCancel\nAncillary Data\nHanger Data\nStructure Data\nTrunnion Data\nYes\nSupports Active Standards\nNo\nCancel\nYes\nYes\nSupports Active Standards\nNo\nSupports Active Standards\nCancel\nFull\nBrief"}
{"Headers": "Ancillary Data", "Content": "Sets the design parameter definitions for all the ancillary support components that can be 3D modelled using design parameters in the catalog. It allows you to define the physical dimensions of all the ancillaries to match a given vendor.\nThe supplied parameters are generally based on, but not exclusively:\nCarpenter & Paterson Ltd\nPipe Suspension Equipment Catalog No. 7/94\n\nCarpenter & Paterson Ltd\n\nPipe Suspension Equipment Catalog No. 7/94\nReferences to the supplier figure numbers are provided on the relevant part of the window. The window also provides material descriptions. The window allows you to set minimum and maximum design values associated with certain attributes of the ancillary, and contains information used during Material Take Off (MTO) extraction using automatic drawing production.\nThe component descriptions can also contain rules that modify the geometry of the component in certain situations. For example, by adding stiffening webs for pipe shoes where the height of the shoe exceeds a given value.\nChanges made are only applied to the database when Apply is clicked. Cancel removes the window. If changes have been made, but not applied, a window displays asking if the changes are to be applied before exiting.\n\n\n\n\nApply\nCancel"}
{"Headers": " list of available ancillary support standards", "Content": "The left hand side of the window displays the list of available ancillary support standards. Filter criteria can be used to specify which ancillary support standards are displayed in the list. Refer to GUI Grid Data for further information.\nSelect the Show Active Ancillaries check box to display only active ancillary support standards.\nHanger and trunnion support types are explained. Refer to Hanger Data and Trunnion Data for further information.\nLighting support types are explained. Refer to Lighting Support Defaults for further information.\nStructural framework support types are explained. Refer to Structure Data for further information.\nWhen a support type is highlighted, the support standard Name, Replacement Name and Description appear at the top of the window. The information is outside of the tabbed areas and displays on all tabs.\nThe plotfile for the selected standard displays on the right hand side of the window. To zoom in to an area of the plotfile, click and drag the middle mouse button to create a zoom area. To restore the original size, right-click and select Reset Limits from the drop-down menu.\nThe information on the window is grouped into two parts. Design detail in the Standard part of the window applies to component design. The Bore Specific part of the window contains data associated with the specified size (bore) of component.\nClick Apply before selecting another standard, otherwise any changes are lost.\nSupport Standard\nThe support type selected in the list of available ancillary support standards displays, and cannot be changed. The support standard is the code used internally within the software by the Supports application.\nStandard Replacement Name\nThe Standard Replacement Name is used on all windows in the Supports application when referring to the support type defined by the support standard. It is also output in place of the support standard name on automatic drawing production drawings. The name can be modified by editing the text in the field. All characters in the replacement name must be alpha/numeric.\nDescription\nThe text in this field is configurable to suit each design project, and only displays in the Model module during the creation of Supports. The description in the field does not affect any associated Material Take Off (MTO) details output in automatic drawing production, as the details are stored in the catalog database.\nSupport Class\nThe support class drop-down list defines the classification of an ancillary. The support classification is used to define compatible ancillaries for each ancillary type.\nActive\nAllows you to specify which of the available support standards are available for use in the project by the user.\nSelect the check box to include the currently selected support standard in selection lists.\nDeselect the check box to exclude the currently selected support standard from selection lists.\nThe active setting overrides any subsequent active setting that displays on the Parameters tab. Refer to Parameters Tab for further information.\nPipe Weight\nDetermines if the ancillary is calculated as part of the pipe weight on the MTO.\nSelect the check box to include the currently selected ancillary to the pipe weight on the MTO.\nDeselect the check box to exclude the currently selected ancillary from the pipe weight on the MTO.\nIsometric MTOC Flag\nDetermines if the material for an ancillary appears in the material list on the piping isometric.\nSelect the check box to include the material in the isometric material list.\nDeselect the check box to exclude the material from the isometric material list.\nOffline\nAllows you to specify which of the available ancillaries can be created as logical offline. Setting an ancillary as logical offline allows the ancillary to be created away from the centerline of the pipe. For example, you may want to create an ancillary on a flange, a tee or on the start of a bend.\nSelect the check box to enable offline creation of the ancillary.\nDeselect the check box to disable offline creation of the ancillary.\nVendor Reference\nDetails the vendor figure number associated with the component build parameters that are detailed on the Supports Ancillary Defaults window.\nPipe Specification Material Code\nThe pipe material is specified here:\nFor example, the text value, CS, represents the setting stored at a valid PIPE specification, at the uda :MDSPipeMat, for use by the supports application. These settings are configurable and not restricted to the example display values.\nPropcon - MDS Ancillary Material\nThe ancillary component material is selected from the materials available from all Material World (MTWL) elements contained in the AVEVA Catalog (properties) database.\nSKey\nThe symbol key that is stored against the SDTE of the specification is displayed here. A symbol key specifies a symbol representation for a support type on an isometric drawing.\nSKey Override\nYou can override the symbol key that is stored against the SDTE of the specification. Input an alternative symbol key value in the field to modify the symbol representation for a support type on an isometric drawing.\nAdditional Welds\nSpecifies the number of additional welds that can be associated with the ancillary support.\nAdditional Trunnion Welds\nSpecifies the number of additional trunnion welds that can be associated with the ancillary support.\nSupport Function\nThe ancillary support function is specified here. For example, AN for an anchor support.\nYou can assign a support function to a chosen preliminary support standard so that it can be identified as a particular support type (for example, anchor) when the time comes to convert the preliminary support into a detailed support type.\nWhen coupled with similar support types on ancillaries, hangers and trunnion standards, it becomes possible to check that the support type being created when using an existing preliminary support matches that already specified during initial design.\nBy default, ancillary, hanger and trunnion standards are assigned a default support function corresponding to their standard code. For example, AT, AN, FH, VH, TT, these are fully configurable.\nTo specify a support function for an ancillary, refer to Ancillary Data for further information.\nTo specify a support function for a hanger, refer to Hanger Data for further information\nTo specify a support function for a trunnion, refer to Trunnion Data for further information.\nSupport Behaviour\nSpecifies the default behaviour for a user defined ancillary that is copied from a support ancillary. The default behaviour of the user defined ancillary is determined from the behaviour of the specified support ancillary when created in Model.\nThe example displays a GT500 that has been copied from a GT06 and has specified support behaviour of GT06.\n\nThe user defined GT500 is added as an associated ancillary to an XAT001 in Model. If the shoe height of the XAT001 is modified to 150mm, a confirm window displays asking the user to reposition the guides or lugs. This default behaviour is identical to that of a GT06.\n\nDetail Rtext\nAVEVA provides a library of Multi Discipline Supports (MDS) catalog content in the AVEVA Catalog Project (ACP), that is reissued periodically to accompany product updates.\nMuch of the MDS out-of-the-box content can be customized in local projects using the Application Defaults, and where appropriate updates to these are delivered along with product updates, enabling those local projects to take advantage of new functionality and catalog content.\nThe Detail Rtext functionality allows you to customize the MDS Detail Texts in the Application Defaults, removing the need to modify the ACP directly and maintain them when an update is received.\nInput a text expression in the Detail Rtext field that will evaluate at the hanger.\nThe following text expressions are valid:\nThe following text expression would not evaluate to a text result:\nSpecifies the geometry set for a user defined ancillary that is copied from a support ancillary. The filter type determines the range of support standard numbers that can be selected for the copied user defined ancillary. For example, if Guides For Shoes is selected from the drop-down list, the available range of support standard numbers is from GT500 to GT569. Refer to Geometry Sets for further information.\nSpecifies the support standard number for a user defined ancillary that is copied from a support ancillary.\nCopies the support data from the currently selected support ancillary to the user defined ancillary. If an existing support type is detected, a Confirm window displays asking you to confirm the copy. Click Yes to copy the support data.\n\nCS Carbon Steel\nSS Stainless Steel\nFG Fibre Glass\nGV Galvanized\nPL Plastic\nCN Cupro Nickel\nALL represents ANY material, for example, valid for all pipe specifications.\nCS Carbon Steel\nCS Carbon Steel\nSS Stainless Steel\nSS Stainless Steel\nFG Fibre Glass\nFG Fibre Glass\nGV Galvanized\nGV Galvanized\nPL Plastic\nPL Plastic\nCN Cupro Nickel\nCN Cupro Nickel\nALL represents ANY material, for example, valid for all pipe specifications.\nALL represents ANY material, for example, valid for all pipe specifications.\nNote:\nThe check box is inactive for Ancillary Components (AC), Branch Bracings (BR) and Manufacturer Hangers (MH) ancillaries because it should not be possible to create these ancillary types as logical offline.\nNote:\nIf the Detail Rtext field does not display, make sure Application Defaults updates 00087 and 00088 are installed (refer to Update Existing Client Project Application Defaults Databases for further information) together with the latest version of AVEVA E3D Design and ACP.\nImportant:\nWhen an existing support standard is copied into the user defined supports catalog, the catalog datasets, pointsets and geometry sets are copied from the source to the target databases in the MDU project. In general, the user can make changes to the geometry set of the copied item without restriction. Modifications to pointsets and datasets must only be carried out if required, modifications to existing data dkeys or p-points may destabilize the operations of the copied support against the functionality provided in the source support standard.\n\n\n\nHanger Data\nTrunnion Data\nLighting Support Defaults\nStructure Data\nParameters Tab\nAncillary Data\nHanger Data\nTrunnion Data\nUpdate Existing Client Project Application Defaults Databases\nGeometry Sets\nGUI Grid Data\nHanger Data\nTrunnion Data\nLighting Support Defaults\nStructure Data\nName\nReplacement Name\nDescription\nReset Limits\nStandard\nBore Specific\nApply\nSupport Standard\nStandard Replacement Name\nStandard Replacement Name\nDescription\nSupport Class\nActive\nParameters\nParameters Tab\nPipe Weight\nIsometric MTOC Flag\nOffline\nNote\n:\nVendor Reference\nSupports Ancillary Defaults\nPipe Specification Material Code\nPropcon - MDS Ancillary Material\nSKey\nSKey Override\nAdditional Welds\nAdditional Trunnion Welds\nSupport Function\nAncillary Data\nHanger Data\nTrunnion Data\nSupport Behaviour\nDetail Rtext\nDetail Rtext\nNote\n:\nDetail Rtext\nUpdate Existing Client Project Application Defaults Databases\nDetail Rtext\nGuides For Shoes\nGeometry Sets\nConfirm\nYes\nImportant:"}
{"Headers": "the design parameters for the selected ancillary for each bore size.", "Content": "The Parameters tab displays a table of the design parameters for the selected ancillary for each bore size. The listed parameters can be modified.\n\nClick and drag the vertical column separator lines to modify the width of table columns.\nWhen a table row is selected, the selected bore size is populated in the Size, Alt Expression and User Des Pars tabs. For example, when switching to the Size tab, the selected bore is displayed and can be modified.\nRight-click the currently selected cell to display a drop-down menu.\n\nCopy\nCopies the currently selected cell value. The value is stored on the clipboard for a later paste operation.\nPaste\nPastes the cell value that is stored on the clipboard into the currently selected cells.\nFill Down\nCopies the cell value from the top cell in a selection of cells and pastes it into all cells in the selection.\nFill Up\nCopies the cell value from the bottom cell in a selection of cells and pastes it into all cells in the selection.\nCopy\nCopies the currently selected cell value. The value is stored on the clipboard for a later paste operation.\nPaste\nPastes the cell value that is stored on the clipboard into the currently selected cells.\nFill Down\nCopies the cell value from the top cell in a selection of cells and pastes it into all cells in the selection.\nFill Up\nCopies the cell value from the bottom cell in a selection of cells and pastes it into all cells in the selection.\nNom Bore\nDefines the size (bore) of the pipe. The pipe defaults apply to the size of the pipe selected.\nActive\nThe setting determines the pipe bore sizes that the support ancillary can be attached to.\nIf the cell contains a tick symbol, the support ancillary can be attached to the pipe bore size.\nIf the cell contains a cross symbol, the support ancillary cannot be attached to the pipe bore size.\nClick on a cell to modify the Active setting.\nShop\nThe setting determines whether the material for an ancillary appears on the piping isometric material list under the FABRICATION MATERIALS (SHOP TRUE) or ERECTION MATERIALS (SHOP FALSE) heading of the MTO.\nIf the cell contains a tick symbol, the material for the ancillary appears on the piping isometric material list under the FABRICATION MATERIALS (SHOP TRUE).\nIf the cell contains a tick symbol, the material for the ancillary appears on the piping isometric material list under the ERECTION MATERIALS (SHOP FALSE).\nMaterial Code\nProvides the same information as Pipe Specification Material Code, but overrides the standard setting for the selected bore.\nAncillary Material\nProvides the same information as Propcon - MDS Ancillary Material, but overrides the standard setting for the selected bore.\n\n\n\nPipe Specification Material Code\nPropcon - MDS Ancillary Material\nParameters\nSize\nAlt Expression\nUser Des Pars\nSize\nCopy\nPaste\nFill Down\nFill Up\nNom Bore\nActive\nActive\nShop\nMaterial Code\nPipe Specification Material Code\nAncillary Material\nPropcon - MDS Ancillary Material"}
{"Headers": "The Size tab allows the design parameters for a specific bore size to be modified", "Content": "The Size tab allows the design parameters for a specific bore size to be modified. The displayed design parameters correspond to the selected table row on the Parameters tab.\n\nThe design parameter descriptions that display on the Size (and Parameter) tabs are taken from the DTREF of the SCOM. The SCOM can be located in the hierarchy. For example, for an AT01, all the SCOM are collected for /ATTA-AT01.\n\nWhere the CATE cannot be found, the design parameter descriptions display as unset, and the message Cannot collect SCOM DBREFS and get descriptions displays on the status bar. If the CATE is found, but one or more design parameter descriptions are unset, it displays as unset.\nPreview\nThe preview displays a graphical view of the selected ancillary bore. Updates to values in the list of parameters on the left hand side of the window are updated in real time in the preview.\nRight-click the Eye on the top right hand side of the preview to display a drop-down menu.\n\nDisplay Axes\nSelect the option to display the axis in the preview.\nDisplay Ppoints\nSelect the option to display Ppoints in the preview.\nDisplay Reflection\nSelect the option to display reflective lighting in the preview.\nDraw Holes\nSelect the option to display holes in the preview.\nDraw Obstruction\nSelect the option to display obstruction values in the preview.\nCapture screenshot\nSingle\nCreates a screenshot of the of the currently displayed preview.\nThe screenshot is saved as a *.png file. Use the Save screenshot window to navigate to the desired location and name the saved file.\nAll sizes\nCreates a screenshot of the preview for all nominal bore sizes.\nThe screenshots are saved as *.png files. Use the Browse For Folder window to navigate to the desired location for the saved files. The files are autonamed using a combination of the support standard and bore size.\nDisplay Axes\nSelect the option to display the axis in the preview.\n\nDisplay Ppoints\nSelect the option to display Ppoints in the preview.\n\nDisplay Reflection\nSelect the option to display reflective lighting in the preview.\n\nDraw Holes\nSelect the option to display holes in the preview.\n\nDraw Obstruction\nSelect the option to display obstruction values in the preview.\n\nCapture screenshot\n\nCreates a screenshot of the of the currently displayed preview.\nThe screenshot is saved as a *.png file. Use the Save screenshot window to navigate to the desired location and name the saved file.\nCreates a screenshot of the preview for all nominal bore sizes.\nThe screenshots are saved as *.png files. Use the Browse For Folder window to navigate to the desired location for the saved files. The files are autonamed using a combination of the support standard and bore size.\nAll modifications are reflected in the relevant table on the Parameters tab.\nOn returning to the Parameters tab, all modifications can be viewed. If the modifications are satisfactory, all the changes can be applied to the database by clicking Apply.\n\n\n\nSize\nParameters\nSize\nParameter\nCannot collect SCOM DBREFS and get descriptions\nPreview\nEye\nDisplay Axes\nDisplay Ppoints\nDisplay Reflection\nDraw Holes\nDraw Obstruction\nCapture screenshot\nSingle\nSave screenshot\nAll sizes\nBrowse For Folder\nParameters\nParameters"}
{"Headers": "The Alternate Expression tab provides for alternative expressions and alternative design parameters for a particular bore", "Content": "The feature is used to change the geometry of a component in certain situations.\n\nThe Supports application checks the alternative expression each time the component is modified. if the expression is true, the alternative design parameters to the right of the expression are used.\nThe example displays an alternative expression for an AT01 ancillary. When design parameter 5 is greater than 100mm, design parameter 7 is set to 6mm and design parameter 9 is set to 25mm. The Supports application creates stiffeners on the AT01 pipe shoe 6mm thick and located 25mm from each end of the shoe.\n\n\n\nAlternate Expression"}
{"Headers": "design parametrs", "Content": "The User Des Pars tab displays the design parameters that the user can modify during the creation or subsequent modification of a support.\n\nThe example displays component AT01 with a bore size of 20mm. The user can modify two of the design parameters for AT01:\nWhen the user modifies the values using the Supports application, the minimum and maximum values are checked and a warning message displays if any values are outside of the allowable ranges. You must make sure suitable minimum and maximum values are input for the design parameters.\nIn some situations it may be necessary to restrict a user-editable parameter to a single value. For example, for AT01 with 20mm bore, the shoe height can be fixed to 100mm to match the component available in a given supplier catalog. In this case the minimum and maximum values are both set to 100.\nDesign parameter 2 - support length, which contains minimum and maximum values of 100mm and 350mm.\nDesign parameter 5 - support height, which contains minimum and maximum values of 50mm and 180mm.\nDesign parameter 2 - support length, which contains minimum and maximum values of 100mm and 350mm.\nDesign parameter 2 - support length, which contains minimum and maximum values of 100mm and 350mm.\nDesign parameter 5 - support height, which contains minimum and maximum values of 50mm and 180mm.\nDesign parameter 5 - support height, which contains minimum and maximum values of 50mm and 180mm.\n\n\n\nUser Des Pars"}
{"Headers": "The Support Compatibility tab", "Content": "The Support Compatibility tab defines which associated ancillaries are available to the user for each particular ancillary type.\n\nThe fields at the top of the window display details for the currently selected ancillary. Refer to Standard Tab for further information.\nEach ancillary type is associated with a particular support class. For example, an AT01 is associated with a welded shoe support class. The support class of the selected ancillary displays at the top right of the Supports Ancillary Data window.\nOnly one of each compatible ancillary support class can be added to an ancillary. For example, to add both a stop and a guide to a shoe, set (on the shoe) the compatible ancillaries support classes to 'STOP FOR SHOE' and 'GUIDE FOR SHOE' and then set the support classes of the stop and the shoe.\nThe list of available support classes contains all available support classes.\nThe list of compatible support classes contains all available support classes that are compatible with the currently selected ancillary.\nTo make a support class available, select an item in the list of available support classes and click the right arrow at the side of the list. The item is transferred to the adjacent list. Click the left arrow to reverse the action.\nThe list of compatible ancillaries contains all compatible ancillaries (populated from the selections made in the list of compatible support classes).\nThe list of restricted ancillaries allows you to specify the ancillaries that are excluded during support creation.\nTo exclude an ancillary from support creation, select an item in the list of compatible ancillaries and click the right arrow at the side of the list. The item is transferred to the adjacent list. Click the left arrow to reverse the action.\nThe combination of the lists defines the ancillary types that the user can select from.\n\n\n\nStandard Tab\nSupport Compatibility\nStandard Tab\nSupports Ancillary Data"}
{"Headers": "The Selection Configuration tab ", "Content": "The Selection Configuration tab contains checks and restrictions for each ancillary.\n\nThe Common part of the Selection Configuration tab applies to all ancillaries. The Trunnion Ancillary part of the tab applies only to trunnion ancillaries and becomes active if the support class of the selected ancillary contains the word TRUNNION.\nPrimary Component\nSelect the check box to define that the ancillary can be created as a standalone ancillary, not just as an associated ancillary.\nIf the support class of the currently selected ancillary starts with the word FOR, the check box is deactivated.\nAvailable on Framework\nSelect the check box to define that the ancillary can be created on a framework.\nOnly Available on Framework\nSelect the check box to define that the ancillary is only available on a framework structure.\nMinimum Elevation\nSpecifies the elevation (height) at which an ancillary can be created at and above. For example, setting a value of 5000 means the ancillary can be created at any elevation at 5000mm and above, but not below 5000mm. If a value of -1000 is input, the support can be created at any elevation below 1000mm.\nThe default setting is *, indicating that there is no restriction on the elevation at which the ancillary can be created.\nPipe Direction\nSelect the Vertical check box to define that the ancillary can be created on a vertical pipe.\nSelect the Horizontal check box to define that the ancillary can be created on a horizontal pipe. If the ancillary is allowed on a horizontal pipe, it must pass the maximum slope check.\nSelect the Ignore Max Pipe Slope check box to define that the ancillary can be created on a pipe with a slope value greater than the defined maximum pipe slope in the Supports application defaults. Refer to Max. Pipe Slope (MDSSUPPMS) for further information.\nComponent Type\nBy default, the Supports application positions the trunnion ancillary on the head or the base of the trunnion.\nThe Head option button indicates that the trunnion ancillary is positioned on the head of the trunnion.\nThe Base option button indicates that the trunnion ancillary is positioned on the base of the trunnion.\nIf the trunnion ancillary is in the support class FOR TRUNNION BASE or PIPE REST INLINE, it is defined as a base component. If the trunnion ancillary support class contains the word BASE or BEARING, it is defined as a base component. All other trunnion ancillaries are defined as head components.\nHead Components Allowed\nThe Head Components Allowed part of the tab applies only to trunnion ancillaries and becomes active if the selected ancillary is a trunnion head component.\nSelect the Tube check box to define that the head component of the trunnion ancillary can be positioned on a pipe tube.\nSelect the Elbow check box to define that the head component of the trunnion ancillary can be positioned on an pipe elbow.\nSelect the Reducer check box to define that the head component of the trunnion ancillary can be positioned on a pipe reducer.\nSelect the Tee check box to define that the head component of the trunnion ancillary can be positioned on a pipe tee.\nTrunnion Types Allowed On\nThe list of allowed trunnions contains all trunnions that the currently selected trunnion ancillary can be created on.\nThe list of restricted trunnions allows you to specify the trunnion types that the ancillary cannot be created on.\nTo restrict an ancillary from being created on a trunnion type, select an item in the list of allowed trunnions and click the right arrow at the side of the list. The item is transferred to the adjacent list. Click the left arrow to reverse the action.\n\n\n\nMax. Pipe Slope (MDSSUPPMS)\nSelection Configuration\nCommon\nSelection Configuration\nTrunnion Ancillary\nPrimary Component\nAvailable on Framework\nOnly Available on Framework\nMinimum Elevation\nPipe Direction\nVertical\nHorizontal\nIgnore Max Pipe Slope\nMax. Pipe Slope (MDSSUPPMS)\nComponent Type\nHead\nBase\nHead Components Allowed\nHead Components Allowed\nTube\nElbow\nReducer\nTee\nTrunnion Types Allowed On"}
{"Headers": "Hanger Data", "Content": "Sets the configuration of hanger templates. Each hanger configuration can have a replacement name that is more meaningful to the user, and a description to suit a particular design project.\nThe hanger templates only apply to the Supports application when the Project Hanger Interface (MDSHANGIF) default value is set to MDS (refer to Project Hanger Interface (MDSHANGIF) for further information). Three sets of hanger templates are supplied with the application, one for each of the hanger components manufacturer/supplier. For example, Platforms Stairs and Ladders (PSL), GRINNELL (now ANVIL) and PIHASA.\nChanges made are only applied to the database when Apply is clicked. Cancel removes the window. If changes have been made, but not applied, a window displays asking if the changes are to be applied before exiting.\n\nImportant:\nThe hanger template configurations that display in the Supports Hanger Data window must represent the same hanger components included in the actual hanger templates defined in various application data worlds APPLDW/SUPPORT/HANGERS/<suffix>. The modelled hanger templates are held for each hanger component manufacturer/supplier in their respective databases. (Refer to Hanger Design Templates for further information).\n\n\n\nProject Hanger Interface (MDSHANGIF)\nImportant:\nSupports Hanger Data\nHanger Design Templates\nonly\nProject Hanger Interface (MDSHANGIF)\nApply\nCancel"}
{"Headers": "The left hand side of the window", "Content": "The left hand side of the window displays the list of available hanger template types; each type represents a hanger configuration. There are two basic hanger types: Fixed Hangers (FH) and Variable Hangers (VH). Filter criteria can be used to specify which hanger template types are displayed in the list. Refer to GUI Grid Data for further information.\nWhen a Hanger configuration is highlighted, the support standard Name, Replacement Name and Description appear at the top of the window. The information is outside of the tabbed areas and displays on all four tabs.\nThe plotfile for the selected hanger configuration displays on the right hand side of the window. To zoom in to an area of the plotfile, click and drag the middle mouse button to create a zoom area. To restore the original size, right-click and select Reset Limits from the drop-down menu.\nClick Apply before selecting another standard, otherwise any changes are lost.\nSupport Standard\nThe hanger template configuration selected in the list of available hanger template types displays, and cannot be changed. The support standard is the code used internally within the software by the Supports application.\nStandard Replacement Name\nThe Standard Replacement Name name is used on all windows in the Supports application when referring to the hanger configuration defined by the support standard. It is also output in place of the support standard name on automatic drawing production drawings. The replacement name is based on the hanger configuration. Refer to Hanger Template Configuration for further information.\nDescription\nThe text in this field is configurable to suit each design project, and only displays in the Model module during the creation of Supports. The description in the field does not affect any associated Material Take Off (MTO) details output in automatic drawing production, as the details are stored in the catalog database.\nHanger Template Configuration\nEach hanger template configuration contains its own specific design characteristics, based on these considerations:\nThe hanger template configuration is defined as a combination of three basic components, the top (T), middle (M) and bottom (B) component. For example, a T1 M2 B5 hanger is made up of a T1 type top connection, M2 type middle connection and a B5 type pipe connection.\nBased on the component combination and other attributes of the hanger template, the supports application can determine the incorporation of the hanger template into the design.\nYou can select the T, M and B components that represent the hanger from the Hanger configuration drop-down lists.\nActive\nEnables you to specify which of the available hanger template configurations are available for use on the project by the user:\nTrue\nSelect the option button to include the currently selected hanger template configuration in selection lists.\nFalse\nSelect the option button to exclude the currently selected hanger template configuration from selection lists.\nTrue\nSelect the option button to include the currently selected hanger template configuration in selection lists.\nFalse\nSelect the option button to exclude the currently selected hanger template configuration from selection lists.\nSKey\nThe symbol key that is stored against the SDTE of the specification is displayed here. A symbol key specifies a symbol representation for a support type on an isometric drawing.\nSKey Override\nYou can override the symbol key that is stored against the SDTE of the specification. Input an alternative symbol key value in the field to modify the symbol representation for a support type on an isometric drawing.\nSupport Function\nThe hanger support function is specified here. For example, FH for a Fixed Hanger.\nBy default, ancillary, hanger and trunnion standards are assigned a default support function corresponding to their standard code. For example, AT, AN, FH, VH, TT, these are fully configurable.\nTo specify a support function for an ancillary, refer to Ancillary Data for further information.\nTo specify a support function for a hanger, refer to Hanger Data for further information\nTo specify a support function for a trunnion, refer to Trunnion Data for further information.\nDetail Rtext\nAVEVA provides a library of Multi Discipline Supports (MDS) catalog content in the AVEVA Catalog Project (ACP), that is reissued periodically to accompany product updates.\nMuch of the MDS out-of-the-box content can be customized in local projects using the Application Defaults, and where appropriate updates to these are delivered along with product updates, enabling those local projects to take advantage of new functionality and catalog content.\nThe Detail Rtext functionality allows you to customize the MDS Detail Texts in the Application Defaults, removing the need to modify the ACP directly and maintain them when an update is received.\nInput a text expression in the Detail Rtext field that will evaluate at the hanger.\nThe following text expressions are valid:\nThe following text expression would not evaluate to a text result:\nIs it a single or double configuration?\nShould the hanger be connected to a vertical or to a horizontal pipe?\nShould the pipe be insulated?\nShould the steelwork connection be a double-channel connection? What type of beams can be used for the steelwork connection?\nIf it is a variable spring hanger, where is the spring located? Is it below the pipe? Is it located above the pipe but below the steelwork? Is it located on top of the steelwork?\nIs the Hanger connected to the pipe using a pipe clamp or to a welded lug?\nIs it a single or double configuration?\nIs it a single or double configuration?\nShould the hanger be connected to a vertical or to a horizontal pipe?\nShould the hanger be connected to a vertical or to a horizontal pipe?\nShould the pipe be insulated?\nShould the pipe be insulated?\nShould the steelwork connection be a double-channel connection? What type of beams can be used for the steelwork connection?\nShould the steelwork connection be a double-channel connection? What type of beams can be used for the steelwork connection?\nIf it is a variable spring hanger, where is the spring located? Is it below the pipe? Is it located above the pipe but below the steelwork? Is it located on top of the steelwork?\nIf it is a variable spring hanger, where is the spring located? Is it below the pipe? Is it located above the pipe but below the steelwork? Is it located on top of the steelwork?\nIs the Hanger connected to the pipe using a pipe clamp or to a welded lug?\nIs the Hanger connected to the pipe using a pipe clamp or to a welded lug?\nNote:\nIf the Detail Rtext field does not display, make sure Application Defaults updates 00087 and 00088 are installed (refer to Update Existing Client Project Application Defaults Databases for further information) together with the latest version of AVEVA E3D Design and ACP.\n\n\n\nAncillary Data\nHanger Data\nTrunnion Data\nUpdate Existing Client Project Application Defaults Databases\nGUI Grid Data\nName\nReplacement Name\nDescription\nReset Limits\nApply\nSupport Standard\nStandard Replacement Name\nStandard Replacement Name\nHanger Template Configuration\nDescription\nHanger Template Configuration\nT\nM\nB\nHanger configuration\nActive\nTrue\nFalse\nSKey\nSKey Override\nSupport Function\nAncillary Data\nHanger Data\nTrunnion Data\nDetail Rtext\nDetail Rtext\nNote\n:\nDetail Rtext\nUpdate Existing Client Project Application Defaults Databases\nDetail Rtext"}
{"Headers": "The SoftTypes tab allows", "Content": "The SoftTypes tab allows you to view hanger template configuration soft types. The configurations use the same template as the hanger configuration defined in the SoftTypes column, but are handled differently by the Supports application.\n\nNote: The hanger template configuration in the SoftTypes column is the master template used by the hanger standard that displays in the Standard column.\n\n\n\nSoftTypes\nSoftTypes\nNote\n:\nSoftTypes\nStandard"}
{"Headers": " hanger supports a pipe", "Content": "If a hanger supports a pipe through a lug, ancillary or trunnion, this tab allows you to view the standard supports that can be used for the support.\n\nClick a component in the Bottom Hanger Types column. The Support Standards column displays the standard types that it can be associated with.\nThe associations can only be modified using the command line interface.\n\n\n\nBottom Hanger Types\nSupport Standards"}
{"Headers": "The Allowed Rod Sizes tab", "Content": "The Allowed Rod Sizes tab allows you to view the range of available rod sizes for a given hanger configuration.\n\nClick an entry in the Nominal Pipe Size column. The available rod sizes for the selected bore and hanger configuration display in the Allowed Rod Sizes column.\nThe associations can only be modified using the command line interface.\n\n\n\nAllowed Rod Sizes\nNominal Pipe Size\nAllowed Rod Sizes"}
{"Headers": "Structure Data", "Content": "Sets the available support standards that can be used in a project, replacement support names and descriptions can also be specified.\nFramework types prefixed FT can be organized into groups, which makes selection of a framework easier for the user.\nThe window also defines which ancillaries are available to the user for a particular framework support.\nAlternative codes can be defined to replace the Supports application default codes to suit an alternative standard.\nChanges made are only applied to the database when Apply is clicked. Cancel removes the window. If changes have been made, but not applied, a window displays asking if the changes are to be applied before exiting.\n\n\n\n\nFT\nApply\nCancel"}
{"Headers": "The left hand side of the window and gui data", "Content": "The left hand side of the window displays the list of the available framework support types. Filter criteria can be used to specify which framework support types are displayed in the list. Refer to GUI Grid Data for further information.\nWhen a support type is highlighted, the support standard Name, Replacement Name and Description appear at the top of the window. The information is outside of the tabbed areas and displays on all tabs.\nThe plotfile for the selected configuration displays on the right hand side of the window. To zoom in to an area of the plotfile, click and drag the middle mouse button to create a zoom area. To restore the original size, right-click and select Reset Limits from the drop-down menu.\nClick Apply before selecting another standard, otherwise any changes are lost.\nSupport Standard\nThe support type selected in the list of available framework support types displays, and cannot be changed. The support standard is the code used internally within the software by the Supports application.\nStandard Replacement Name\nThe Standard Replacement Name is used on all windows in the Supports application when referring to the support type defined by the support standard. It is also output in place of the support standard name on automatic drawing production drawings. The name can be modified by editing the text in the field.\nDescription\nThe text in this field is configurable to suit each design project, and only displays in the Model module during the creation of Supports. The description in the field does not affect any associated Material Take Off (MTO) details output in automatic drawing production, as the details are stored in the catalog database.\nActive\nAllows you to specify which of the available support standards are available for use in the project by the user.\nSelect the check box to include the currently selected support standard in selection lists.\nDeselect the check box to exclude the currently selected support standard from selection lists.\nIsometric MTOC Flag\nDetermines if the material for a support appears in the material list on the piping isometric. The setting is applied to the MTOC attribute of the selected component (for example, the Source Reference (SREF) Attachment Point (ATTA) for the framework)\nSelect the check box to include the material in the isometric material list.\nDeselect the check box to exclude the material from the isometric material list.\nThe isometric MTOC flag overrides any subsequent shop flag settings that display on the Parameters tab. Refer to Parameters Tab for further information.\nSKey\nThe symbol key that is stored against the SDTE of the specification is displayed here. A symbol key specifies a symbol representation for a support type on an isometric drawing.\nSKey Override\nYou can override the symbol key that is stored against the SDTE of the specification. Input an alternative symbol key value in the field to modify the symbol representation for a support type on an isometric drawing.\nDetail Rtext\nAVEVA provides a library of Multi Discipline Supports (MDS) catalog content in the AVEVA Catalog Project (ACP), that is reissued periodically to accompany product updates.\nMuch of the MDS out-of-the-box content can be customized in local projects using the Application Defaults, and where appropriate updates to these are delivered along with product updates, enabling those local projects to take advantage of new functionality and catalog content.\nThe Detail Rtext functionality allows you to customize the MDS Detail Texts in the Application Defaults, removing the need to modify the ACP directly and maintain them when an update is received.\nInput a text expression in the Detail Rtext field that will evaluate at the hanger.\nThe following text expressions are valid:\nThe following text expression would not evaluate to a text result:\nNote:\nIf the Detail Rtext field does not display, make sure Application Defaults updates 00087 and 00088 are installed (refer to Update Existing Client Project Application Defaults Databases for further information) together with the latest version of AVEVA E3D Design and ACP.\n\n\n\nUpdate Existing Client Project Application Defaults Databases\nGUI Grid Data\nName\nReplacement Name\nDescription\nReset Limits\nApply\nSupport Standard\nStandard Replacement Name\nDescription\nActive\nIsometric MTOC Flag\nSKey\nSKey Override\nDetail Rtext\nDetail Rtext\nNote\n:\nDetail Rtext\nUpdate Existing Client Project Application Defaults Databases\nDetail Rtext"}
{"Headers": "The Framework Selections/Restrictions tab", "Content": "The Framework Selections/Restrictions tab allows you to specify the ancillaries that are available to the user during framework support creation.\n\nThe fields at the top of the window display details for the currently selected framework. Refer to Standard Tab for further information.\nThe list of available selections contains all available ancillaries.\nThe options below the list provide filtering for specific ancillary types.\nTo make an ancillary available, select an item in the list and click the right arrow at the side of the list. The item is transferred to the adjacent list. Click the left arrow to reverse the action. The * character represents all ancillary types.\nThe list of available restrictions allows you to specify the ancillaries that are excluded during framework support creation. The functionality of the list of available restrictions is identical to the functionality of the list of available selections.\nThe combination of the lists defines the ancillary types that the user can select from.\nIn the example, the * character is used for the list of available selections, indicating that all ancillary types are made available. The list of available restrictions indicates the exclusion of AN06, AN08 and all LT type ancillaries from the Supports application.\n\n\n\nStandard Tab\nFramework Selections/Restrictions\nStandard Tab"}
{"Headers": "The Framework Codes tab contains", "Content": "The Framework Codes tab contains alternative descriptions for the support codes used by the Supports application.\n\nFor example, some of the support codes associated with an FT09 support are:\nFT09-1-1\nFT09-2-1\nFT09-3-1\nFT09-4-1\nFT09-5-1\nFT09-6-1\nFT09-1-2\nFT09-2-2\nFT09-3-2\nFT09-4-2\nFT09-5-2\nFT09-6-2\nFT09-1-3\nFT09-2-3\nFT09-3-3\nFT09-4-3\nFT09-5-3\nFT09-6-3\nFT09-1-4\nFT09-2-4\nFT09-3-4\nFT09-4-4\nFT09-5-4\nFT09-6-4\nFT09-1-5\nFT09-2-5\nFT09-3-5\nFT09-4-5\nFT09-5-5\nFT09-6-5\nFT09-1-6\nFT09-2-6\nFT09-3-6\nFT09-4-6\nFT09-5-6\nFT09-6-6\nFT09-1-1\nFT09-2-1\nFT09-3-1\nFT09-4-1\nFT09-5-1\nFT09-6-1\nFT09-1-2\nFT09-2-2\nFT09-3-2\nFT09-4-2\nFT09-5-2\nFT09-6-2\nFT09-1-3\nFT09-2-3\nFT09-3-3\nFT09-4-3\nFT09-5-3\nFT09-6-3\nFT09-1-4\nFT09-2-4\nFT09-3-4\nFT09-4-4\nFT09-5-4\nFT09-6-4\nFT09-1-5\nFT09-2-5\nFT09-3-5\nFT09-4-5\nFT09-5-5\nFT09-6-5\nFT09-1-6\nFT09-2-6\nFT09-3-6\nFT09-4-6\nFT09-5-6\nFT09-6-6\nThe codes are dependent on the steelwork size used and the number of cross bars. In some circumstances the standard may have a different standard code for different steelwork sizes with the same configuration. The settings can be used to print the correct code in the MODEL module, on the ADP drawing and in the material list of the piping isometric if required.\nFor example, if an alternative code of M10A1 is specified for FT09-1-1, for ADP and isometric production, the code FT09-1-1 code is replaced with M10A1.\nThe list of available support codes displays the fixed support codes for the selected framework and the alternative code, if defined. The * character indicates that the fixed code is used, which is the default setting.\nEdit Selected Row\nTo modify the Alternative Code for the currently selected row in the list of available support codes, input a value in the field to replace the * character. Press Enter to populate the list of available support codes with the modified value.\nEdit Column\nAn alternative code can be specified for a range of fixed codes, by making appropriate selections in the From and To drop-down lists. Input an Alternative Code in the field to replace the stored values. Press Enter to populate the list of available support codes with the modified value.\n\n\n\nFramework Codes\nEdit Selected Row\nAlternative Code\nEnter\nEdit Column\nFrom\nTo\nAlternative Code\nEnter"}
{"Headers": "Trunnion Data", "Content": "Sets the available trunnion types that can be used on a project, and which trunnion bore sizes can be used with each pipe bore.\nThe window also allows you to specify the pipe sizes that the selected trunnion can be attached to, and if the trunnion material type appears on the piping isometric.\nYou can also select which trunnion base plate standards are available to the user.\nChanges are only applied to the database when Apply is clicked. Cancel removes the window. If changes have been made but not applied, a window displays asking if the changes are to be applied before exiting.\n\n\n\n\nApply\nCancel"}
{"Headers": "The left hand side of the window", "Content": "The left hand side of the window displays the list of available trunnion support types (TT series). Filter criteria can be used to specify which trunnion support types are displayed in the list. Refer to GUI Grid Data for further information.\nWhen a trunnion is highlighted, the support standard Name, Replacement Name and Description appear at the top of the window. The information is outside of the tabbed areas and displays on all tabs.\nThe plotfile for the selected trunnion displays on the right hand side of the window. To zoom in to an area of the plotfile, click and drag the middle mouse button to create a zoom area. To restore the original size, right-click and select Reset Limits from the drop-down menu.\nClick Apply before selecting another trunnion type, otherwise any changes are lost.\nSupport Standard\nThe trunnion name selected in the list of available trunnion support types displays, and cannot be changed. The support standard is the code used internally within the software by the Supports application\nStandard Replacement Name\nThe Standard Replacement Name is used on all windows in the supports application when referring to the support type defined by the support standard. It is also output in place of the support standard name on automatic drawing production drawings. The name can be modified by editing the text in the field.\nDescription\nThe text in this field is configurable to suit each design project, and only displays in the Model module during the creation of Supports. The description in the field does not affect any associated Material Take Off (MTO) details output in automatic drawing production, as the details are stored in the catalog database.\nActive\nAllows you to specify which of the available support standards are available for use in the project by the user.\nSelect the check box to include the currently selected support standard in selection lists.\nDeselect the check box to exclude the currently selected support standard from selection lists.\nThe Active setting overrides any subsequent active setting that displays on the Active/Shop Flag tab. Refer to Active/Shop Flag Tab for further information.\nVendor Reference\nNot available at this release.\nElevation Restriction\nSpecifies the elevation (height) at which a trunnion can be created at and above. For example, setting a value of 5000 means the trunnion can be created at any elevation at 5000mm and above. If a value of -1000 is input, the trunnion can be created at any elevation below 1000mm.\nThe default setting is *, indicating that there is no restriction on the elevation at which the trunnion can be created.\nPipe Specification Material Code\nThe pipe material is specified here:\nFor example, the text value CS represents the setting stored at a valid PIPE specification, at the uda :MDSPipeMat, for use by the Supports application. These settings are configurable and not restricted to the example display values.\nSKey\nThe symbol key that is stored against the SDTE of the specification is displayed here. A symbol key specifies a symbol representation for a support type on an isometric drawing.\nSKey Override\nYou can override the symbol key that is stored against the SDTE of the specification. Input an alternative symbol key value in the field to modify the symbol representation for a support type on an isometric drawing.\nSupport Function\nThe trunnion support function is specified here. For example, TT for a Trunnion.\nBy default, ancillary, hanger and trunnion standards are assigned a default support function corresponding to their standard code. For example, AT, AN, FH, VH, TT, these are fully configurable.\nTo specify a support function for an ancillary, refer to Ancillary Data for further information.\nTo specify a support function for a hanger, refer to Hanger Data for further information\nTo specify a support function for a trunnion, refer to Trunnion Data for further information.\nIsometric MTOC Flag\nDetermines if the material for the trunnion appears in the material list on the piping isometric.\nSelect the check box to include the material in the isometric material list.\nDeselect the check box to exclude the material from the isometric material list.\nThe isometric MTOC flag overrides any subsequent shop flag settings that display on the Active/Shop Flag tab. Refer to Active/Shop Flag Tab for further information.\nDetail Rtext\nAVEVA provides a library of Multi Discipline Supports (MDS) catalog content in the AVEVA Catalog Project (ACP), that is reissued periodically to accompany product updates.\nMuch of the MDS out-of-the-box content can be customized in local projects using the Application Defaults, and where appropriate updates to these are delivered along with product updates, enabling those local projects to take advantage of new functionality and catalog content.\nThe Detail Rtext functionality allows you to customize the MDS Detail Texts in the Application Defaults, removing the need to modify the ACP directly and maintain them when an update is received.\nInput a text expression in the Detail Rtext field that will evaluate at the hanger.\nThe following text expressions are valid:\nThe following text expression would not evaluate to a text result:\nCS Carbon Steel\nSS Stainless Steel\nFG Fibre Glass\nGV Galvanized\nPL Plastic\nCN Cupro Nickel\nALL represents ANY material, for example, valid for all pipe specifications.\nCS Carbon Steel\nCS Carbon Steel\nSS Stainless Steel\nSS Stainless Steel\nFG Fibre Glass\nFG Fibre Glass\nGV Galvanized\nGV Galvanized\nPL Plastic\nPL Plastic\nCN Cupro Nickel\nCN Cupro Nickel\nALL represents ANY material, for example, valid for all pipe specifications.\nALL represents ANY material, for example, valid for all pipe specifications.\nNote:\nIf the Detail Rtext field does not display, make sure Application Defaults updates 00087 and 00088 are installed (refer to Update Existing Client Project Application Defaults Databases for further information) together with the latest version of AVEVA E3D Design and ACP.\n\n\n\nActive/Shop Flag Tab\nAncillary Data\nHanger Data\nTrunnion Data\nActive/Shop Flag Tab\nUpdate Existing Client Project Application Defaults Databases\nGUI Grid Data\nName\nReplacement Name\nDescription\nReset Limits\nApply\nSupport Standard\nStandard Replacement Name\nStandard Replacement Name\nDescription\nActive\nActive/Shop Flag Tab\nVendor Reference\nElevation Restriction\nPipe Specification Material Code\nSKey\nSKey Override\nSupport Function\nAncillary Data\nHanger Data\nTrunnion Data\nIsometric MTOC Flag\nActive/Shop Flag\nActive/Shop Flag Tab\nDetail Rtext\nDetail Rtext\nNote\n:\nDetail Rtext\nUpdate Existing Client Project Application Defaults Databases\nDetail Rtext"}
{"Headers": " chcek boxes", "Content": "\nActive\nThe setting of the check boxes determines the pipe bore sizes that the selected trunnion type can be attached to.\nIf the Active check box is selected on the Standard tab, all check boxes are selected by default, you can deselect the required check boxes for the project.\nIf the Active check box is not selected on the Standard tab, this setting overrides all the check box settings, all bore sizes are defined as not active, even if the check box is selected.\nShop Flag\nThe setting of the check boxes determines whether the material for a trunnion appears on the piping isometric material list under the FABRICATION MATERIALS (SHOP TRUE) or ERECTION MATERIALS (SHOP FALSE) heading of the Material Take Off (MTO).\nIf the Isometric MTOC Flag check box is selected on the Standard tab, all check boxes are selected by default, you can deselect the required check boxes for the project.\nIf the Isometric MTOC Flag check box is not selected on the Standard tab, this setting overrides all the check box settings, all shop flag settings are defined as not active, even if the check box is selected.\n\n\n\nActive\nActive\nStandard\nActive\nStandard\nShop Flag\nIsometric MTOC Flag\nStandard\nIsometric MTOC Flag\nStandard"}
{"Headers": " the available trunnion types", "Content": "Sets the available trunnion types that can be used on a project, and which trunnion bore sizes and trunnion components are available to the user.\n\nTrunnion Bores List\nThe size of the pipe is specified by clicking the Bore up/down arrows. The available trunnion bores for the selected trunnion type and pipe bore display in the Trunnion Bores list.\nTo make a trunnion bore size available to the user, select an item in the Inactive list and click the right arrow at the side of the list. The item is transferred to the adjacent Active list. Click the left arrow to reverse the action.\nThe default trunnion bore displays at the top of the Active list.\nTrunnion Sizes\nThe trunnion size is the length of the trunnion from the bottom of the trunnion baseplate, (not the bearing plate) to the center of the pipe to which it is welded/clamped.\nThe minimum and maximum trunnion size for the selected trunnion type and pipe bore can be set, as well as the default trunnion size (length).\nComponents for Trunnion Bore List\nThe available ancillary components for the selected trunnion are listed. A list is available for each component type based on support class. Refer to Support Class for further information.\nThe support classes for trunnions are:\nTo make a trunnion component available to the user, select an item in the Inactive list and click the right arrow at the side of the list. The item is transferred to the adjacent Active list. Click the left arrow to reverse the action.\nThe default trunnion component displays at the top of the Active list.\nPreview\nThe preview part of the Component Selection tab allows you to view a 2D representation of the currently selected trunnion component.\nRight-Click Menu\nYou can right-click either the list of active trunnion bores or the list of active trunnion bore components to display a drop-down menu.\n\nMake default (move to top)\nSelect from the drop-down menu to define the selected trunnion bore/trunnion component as the default.\nMove up\nSelect from the drop-down menu to move the selected trunnion bore/trunnion component up one position on the list of active trunnion bores/list of active trunnion components.\nMove down\nSelect from the drop-down menu to move the selected trunnion bore/trunnion component down one position on the list of active trunnion bores/list of active trunnion components.\nMake default (move to top)\nSelect from the drop-down menu to define the selected trunnion bore/trunnion component as the default.\nMove up\nSelect from the drop-down menu to move the selected trunnion bore/trunnion component up one position on the list of active trunnion bores/list of active trunnion components.\nMove down\nSelect from the drop-down menu to move the selected trunnion bore/trunnion component down one position on the list of active trunnion bores/list of active trunnion components.\n\nTRUNNION BASE PLATE\nTRUNNION BEARING PLATE\nTRUNNION COLLAR PLATE\nTRUNNION CLAMP\nISOLATION BLOCK\nBREAK OUT PLATES\nINLINE REINFORCING PLATE\nTRUNNION BASE PLATE\nTRUNNION BASE PLATE\nTRUNNION BEARING PLATE\nTRUNNION BEARING PLATE\nTRUNNION COLLAR PLATE\nTRUNNION COLLAR PLATE\nTRUNNION CLAMP\nTRUNNION CLAMP\nISOLATION BLOCK\nISOLATION BLOCK\nBREAK OUT PLATES\nBREAK OUT PLATES\nINLINE REINFORCING PLATE\nINLINE REINFORCING PLATE\n\n\n\nTrunnion Bores List\nBore\nTrunnion Bores\nInactive\nActive\nActive\nTrunnion Sizes\nComponents for Trunnion Bore List\nSupport Class\nInactive\nActive\nActive\nPreview\nComponent Selection\nRight-Click Menu\nMake default (move to top)\nMove up\nMove down"}
{"Headers": "Lighting Support Defaults", "Content": "Sets the available defaults required to create a lighting support.\nClick Reset to revert the Lighting Support Defaults window to the default values/settings.\nChanges are only applied to the database when Apply is clicked. Cancel removes the window. If changes have been made but not applied, a window displays asking if the changes are to be applied before exiting.\n\nType\nThe text field is used to identify a lighting support type.\nCode\nThe PML (Programmable Macro Language) string expression specifies the support code of the lighting support that is used for output in DRAW or reports.\nOrigin\nDefines the support origin that is used when positioning the support. Any positional attribute or p-point reference can be specified.\nReplacement Type\nThe alternative support type to be output in DRAW or reports.\nMax. Height\nThe maximum height at which the support can be created. The value can also be set locally within the support template to provide different maximum values for different conditions (for example, a different zone or elevation).\nMin. Height\nThe minimum height at which the support can be created. The value can also be set locally within the support template to provide different minimum values for different conditions (for example, a different zone or elevation).\nBracket Limit\nIf the support height is less/greater than this value, then bracket(s) are removed from or added to the support. The bracket limit can also be specified locally within the support template.\nType\nSpecifies the item within the design database that represents the lighting equipment to be supported.\nFilter\nThe PML filter expression can be used to specify attributes that define the lighting equipment more precisely.\nOrigin\nSpecifies the origin of the lighting. When the support is created, its origin is placed at the lighting origin. Any positional attribute or p-point reference (for example, DP1, P2) can be specified. The lighting origin is normally positioned in the middle of the support when viewed from the Z (vertical) direction.\nY Direction\nUsed during lighting support creation to orientate the support so that the Y axis is aligned with the Y direction of the specified lighting. Any positional attribute, local axis of lighting (for example, Y45N) or p-point reference (for example, DP1 or P1) can be specified. Lighting is assured to be on the horizontal plane.\n\n\n\nReset\nLighting Support Defaults\nApply\nCancel\nType\nCode\nOrigin\nReplacement Type\nMax. Height\nMin. Height\nBracket Limit\nType\nFilter\nOrigin\nY Direction"}
{"Headers": "Area Based ADP Grid Data", "Content": "The Supports application contains functionality to include GRIDSY grids (available in Model) in the Area Based ADP (ABA) location plan. The use of SCTN based grid definitions is maintained. The functionality enables the use of multiple grid systems across the 3D model. Suitable grid systems are automatically selected in the ABA location plan during drawing generation.\n\nIn order to include a GRIDSY grid in AVEVA Catalog, it is first necessary to set up a grid in Model.\nYou can define the list of available grids, the pattern for tagging of gridlines (Programmable Macro Language (PML) expression) and origin of support coordinates that display on the drawing.\nThe administration data is stored in the MDSAPPDEFAULTS database below CATA MDS/ABAGRIDDATA/DEFAULTS.\nThe default values/settings indicated on the window are those that exist when the Supports application is first installed.\nChanges made are only applied to the database when Apply is clicked. To keep the changes the Save Work operation must to be performed.\nClick Cancel to close the window. If changes have been made, but not applied, a window displays asking if the changes are to be applied before exiting.\n\nGridline Tag Patterns\nThe gridline tag patterns allow you to customise the way in which grid data is tagged within the ABA location plan which is created in the Draw application. PML expressions can be input into the GRDLN Tag and SCTN Tag fields which are evaluated against the selected gridlines.\nExpressions are evaluated against the X and Y gridlines that are automatically selected when generating the support, such expressions can therefore comprise of any of the gridline attributes or any attribute from the hierarchy above (provided that STRING output is maintained).\nWhen the ABA location plan is created, the result is written into the ATEXT attribute of a SLAB. It can contain explicit sequences that have special meanings in Draw, for example '/#' which is interpreted as a newline character and splits the resulting text into two lines.\nSupport Datum Origin Coordinates\nThe support datum origin coordinates settings allow you to define the calculation process for the support datum dimensions used in the ABA location plan in the Draw application.\nThe Support Coordinates Origin drop-down list contains the following types of support datum calculation:\nList of Valid Grids\nYou can define the available grid systems for use with the ABA location plan.\nTo add a grid to the list of valid grids, select the grid (GRIDSY, Structure (STRU) or Framework (FRMW) grid element) to be added on the Catalog Explorer and click ADD CE.\nClick Remove Selected to delete the currently selected grid from the list of valid grids.\n\nMatching Grid - The origin of the selected grid is used.\nZone, Site, World - The origin of the specified element in the hierarchy above the support is used.\nNamed Item - The origin of the specified named item in the design database is used.\nMatching Grid - The origin of the selected grid is used.\nMatching Grid - The origin of the selected grid is used.\nZone, Site, World - The origin of the specified element in the hierarchy above the support is used.\nZone, Site, World - The origin of the specified element in the hierarchy above the support is used.\nNamed Item - The origin of the specified named item in the design database is used.\nNamed Item - The origin of the specified named item in the design database is used.\nNote:\nThe Supports ABA Grid Data window is not required for REFGRID grids, they take their tag format directly from the grid line data. In order to use REFGRID grids, the location plan task uses the mdsAbaLocPlanRefGrd function. An example can be seen in the AvevaPlantSample project task /mds_aba_location_plan_task.\nIf an attempt is made to include a REFGRID grid, an error message is displayed. This can be safely ignored.\n\n\n\nSupports\nNote\n:\nSupports ABA Grid Data\nSupports\nApply\nSave Work\nCancel\nGridline Tag Patterns\nGRDLN Tag\nSCTN Tag\nSupport Datum Origin Coordinates\nSupport Coordinates Origin\nMatching Grid\nZone, Site, World\nNamed Item\nList of Valid Grids\nADD CE\nRemove Selected"}
{"Headers": "Ancillary Selection Criteria", "Content": "Sets user defined ancillary selection criteria for the generation of supports. These criteria are used in addition to the standard checks that are performed on ancillaries when they are created. For example bore, temperature and material checks.\nThe administration data is stored in the MDSAPPDEFAULTS database below CATA MDS/SELECTION-CRITERIA.\nThe default values/settings that display on the windows are those are those that exist when the Supports application is first installed.\nClick Reset to revert the User Defined Ancillary Selection Criteria window to the default values/settings.\nChanges made are only applied to the database when Apply is clicked. To keep the changes the Save Work operation must be performed.\nClick Cancel to close the window. If changes are made, but not applied, a window displays asking if the changes are to be applied before exiting.\n\nTemperature Check\nYou can override the default temperature check that is performed at branch level.\nFor example, the temperature check can be modified to be carried out at pipe level by changing the expression field to temp of PIPE.\nThe validity of the PML expression is checked by AVEVA Catalog, if an error is detected an error message displays and the Expression field is highlighted.\n\nUser Defined Criteria\nYou can input customized ancillary checking expressions in the Criteria 1 to 5 fields.\nFor example, the paint code of a branch can be specified, the user is then only able to create the ancillary if the paint code matches that defined in the Programmable Macro Language (PML) expression.\n\nInput an ancillary selection criteria description in the Description field.\nInput a valid PML expression in the Expression field.\nTick the Active check box to activate the ancillary selection criteria.\nThe supports hierarchy is separate from the branch and pipe. The initial element expected in the criteria expression is the SUPPO element. The previous component on the selected branch, nearest to the SUPPO element is represented by the compref attribute on the SUPPO.\nUser Defined Functions\nIn addition to the standard expression functionality, it is also possible to create a user defined function to perform more advanced checking.\nYou can assign a user defined check function to the Criteria fields. The value in the expression field is the full function call to the user defined function. For example, the expression can be called !!checkCriteria1().\n\nUser Defined Check Function - Creation and Usage Rules\nThe following rules must be observed when assigning a function:\nUser Defined Check Function - Example Listing\nThe example user defined check function enables the user to create a support only when the paint spec of the branch is either '12345-STD-PIP-001-RAL1069' or '12345-STD-PIP-001-RAL1070'.\nThe user defined check function must be created in a standard text file. As the function name is checkCriteria1 the file should be saved as checkcriteria1.pmlfnc\nIt is recommended that check functions are saved in a separate folder to AVEVA E3D Design and that the pmllib environment variable in AVEVA E3D Design startup is modified to point to it.\nFor example:\nCreate a folder called pmllib in c:\\userpml\\\nSave checkcriteria1.pmlfnc to c:\\userpml\\pmllib\\\nModify the environment variable for pmllib to add this new search path. For example:\nEnter Model, type PML REHASH ALL into the command line and press Enter. The pml index is updated allowing the user defined file to be used.\nRefer to the Using PML in AVEVA Products for further information regarding PML customization.\nDefine function !!functionName() is BOOLEAN\nIf !!ce.compref.type.eq(\u2018BRAN\u2019) then\n !bran = !!ce.compref (if the compref is the branch itself)\nelse\n !bran = !!ce.compref.owner (if the compref is a branch component)\nendif\ndefine function !!checkCriteria1() is BOOLEAN\n --get the paint spec of the pipe branch\n var !paintSpec ptsp of bran of compref\n\n --make sure that the paint spec of the of the pipe is one of the types specified\n      below\n   \n if !paintSpec.neq('12345-STD-PIP-001-RAL1069') and\n !paintSpec.neq('12345-STD-PIP-001-RAL1070') then\n  return FALSE\n else\n  return TRUE\n endif\n\nendfunction\nThe function entered in the expression field must be in the correct format. For example, !!functionName()\nThe user defined function file must have a BOOLEAN return type. For example, the function file definition must in the following format:\nDefine function !!functionName() is BOOLEAN\nThe function cannot be called with any arguments. For example, the function brackets must be empty.\nWhen the user defined check function is run, the current element is the datum support of the pipe so all processing must be done on this basis. For example, to interrogate the branch the following commands can be used.\nIf !!ce.compref.type.eq(\u2018BRAN\u2019) then\n !bran = !!ce.compref (if the compref is the branch itself)\nelse\n !bran = !!ce.compref.owner (if the compref is a branch component)\nendif\nThe function entered in the expression field must be in the correct format. For example, !!functionName()\nThe function entered in the expression field must be in the correct format. For example, !!functionName()\nThe user defined function file must have a BOOLEAN return type. For example, the function file definition must in the following format:\nDefine function !!functionName() is BOOLEAN\nThe user defined function file must have a BOOLEAN return type. For example, the function file definition must in the following format:\nThe function cannot be called with any arguments. For example, the function brackets must be empty.\nThe function cannot be called with any arguments. For example, the function brackets must be empty.\nWhen the user defined check function is run, the current element is the datum support of the pipe so all processing must be done on this basis. For example, to interrogate the branch the following commands can be used.\nIf !!ce.compref.type.eq(\u2018BRAN\u2019) then\n !bran = !!ce.compref (if the compref is the branch itself)\nelse\n !bran = !!ce.compref.owner (if the compref is a branch component)\nendif\nWhen the user defined check function is run, the current element is the datum support of the pipe so all processing must be done on this basis. For example, to interrogate the branch the following commands can be used.\n\n\n\nReset\nUser Defined Ancillary Selection Criteria\nApply\nSave Work\nCancel\nTemperature Check\nUser Defined Criteria\nDescription\nExpression\nActive\nUser Defined Functions\nUser Defined Check Function - Creation and Usage Rules\n!!functionName()\nDefine function !!functionName() is BOOLEAN\nUser Defined Check Function - Example Listing\nEnter\nUsing PML in AVEVA Products"}
{"Headers": "Compensation Plates", "Content": "The Supports application contains functionality to enable the creation and modification of compensating plates in order to fill any gaps between frameworks and ancillaries. In order to create compensating plates within Model, it is first necessary to set up a number of administrative options.\nThe administration data is stored in the MDSAPPDEFAULTS database below CATA MDS/COMPENSATING-PLATES/DEFAULTS.\n\n\n"}
{"Headers": "the minimum and maximum gap sizes", "Content": "Sets the minimum and maximum gap sizes and the calculation process for plate thicknesses and rounding distances.\nThe default values/settings indicated on the window are those that exist when the Supports application is first installed.\nClick Reset to revert the Supports Compensation Options window to the default values/settings.\nChanges made are only applied to the database when Apply is clicked. To keep the changes the Save Work operation must be performed.\nClick Cancel to close the window. If changes have been made, but not applied, a window displays asking if the changes are to be applied before exiting.\n\nGap\nThe gap settings allow you to define when a compensation can be used and which type of compensation to use in a particular situation.\nIt is also possible to define the maximum gap for a plate to be used. If the gap is between the maximum for a plate and the maximum for a profile, then a compensating profile (FIXING) is created.\nThe dimensional value of the Minimum field defines the minimum space required for the user to create a compensating plate. If the gap is less than this value then it is not regarded as a gap and no compensation is created.\nThe dimensional value of the Maximum for Plates field defines the maximum space required for the user to create a compensating plate. If the gap is equal or less than this value (and not less than the Minimum) then plates (PANE) are created to fill the gap.\nThe dimensional value of the Maximum for Profile field defines the maximum space required for the user to create a compensating profile. If the gap is equal or less than this value but greater than the maximum value for plates, then a profile (FIXING) is placed to fill the gap.\nPlate Thickness\nThe plate thickness settings allow you to define the calculation process for the thickness of the compensating plate.\nThe Calculation Method drop-down list contains the following types of plate thickness calculation:\nThe Visually Accommodate option can be set to either On or Off using the drop-down list. If there is a gap or overlap, the actual thickness of the top plate can be accommodated so that it fits the gap. Adding an extra design parameter to the plate alters the height.\nRounding\nThe rounding settings allow you to define the calculation process for the rounding of the compensating plate.\nThe X and Y values for the compensating plate are the length and width values. In order to obtain these sizes a calculation can be performed, refer to Compensation Sizes for further information.\nAfter the X or Y size of the compensating plate is calculated, it is rounded according to the specified parameters.\nThe Calculation Method drop-down list contains the following types of rounding calculation:\nThe X-size value and Y-size value fields allow you to define the nearest value to round to. For example, an X-size value of 10mm rounds the result to the nearest 10mm.\nTo disable rounding, set the X and Y size values to 0mm.\nGreater or equal to the gap - The overall thickness of all plates must either fit the gap or overlap it. There must be no remaining gap.\nLess or equal to the gap - The overall thickness of all plates must never overlap the gap. Plates either fit the gap or some gap remains.\nClosest to the Gap - There can be either an overlap or a gap remaining, Plates of thicknesses are selected so the overall thickness is as close to the gap size as possible.\nGreater or equal to the gap - The overall thickness of all plates must either fit the gap or overlap it. There must be no remaining gap.\nGreater or equal to the gap - The overall thickness of all plates must either fit the gap or overlap it. There must be no remaining gap.\nLess or equal to the gap - The overall thickness of all plates must never overlap the gap. Plates either fit the gap or some gap remains.\nLess or equal to the gap - The overall thickness of all plates must never overlap the gap. Plates either fit the gap or some gap remains.\nClosest to the Gap - There can be either an overlap or a gap remaining, Plates of thicknesses are selected so the overall thickness is as close to the gap size as possible.\nClosest to the Gap - There can be either an overlap or a gap remaining, Plates of thicknesses are selected so the overall thickness is as close to the gap size as possible.\nAlways Up - The resulting value from the calculation is always rounded upwards. For example, if the resulting X size is 33mm and the rounding X value is set to 10mm then it is rounded up to 40mm.\nAlways Down - The resulting value from the calculation is always rounded downwards. For example, if the resulting X size is 38mm and the rounding X value is set to 10mm then it is rounded down to 30mm.\nTo Closest Value - The resulting value from the calculation is rounded to the nearest number. For example, if the resulting X size is 38mm and the rounding X value is set to 10mm then it is rounded up to 40mm.\nAlways Up - The resulting value from the calculation is always rounded upwards. For example, if the resulting X size is 33mm and the rounding X value is set to 10mm then it is rounded up to 40mm.\nAlways Up - The resulting value from the calculation is always rounded upwards. For example, if the resulting X size is 33mm and the rounding X value is set to 10mm then it is rounded up to 40mm.\nAlways Down - The resulting value from the calculation is always rounded downwards. For example, if the resulting X size is 38mm and the rounding X value is set to 10mm then it is rounded down to 30mm.\nAlways Down - The resulting value from the calculation is always rounded downwards. For example, if the resulting X size is 38mm and the rounding X value is set to 10mm then it is rounded down to 30mm.\nTo Closest Value - The resulting value from the calculation is rounded to the nearest number. For example, if the resulting X size is 38mm and the rounding X value is set to 10mm then it is rounded up to 40mm.\nTo Closest Value - The resulting value from the calculation is rounded to the nearest number. For example, if the resulting X size is 38mm and the rounding X value is set to 10mm then it is rounded up to 40mm.\n\n\n\nCompensation Sizes\nReset\nSupports Compensation Options\nApply\nSave Work\nCancel\nGap\nMinimum\nMaximum for Plates\nMaximum for Profile\nPlate Thickness\nCalculation Method\nGreater or equal to the gap\nLess or equal to the gap\nClosest to the Gap\nVisually Accommodate\nOn\nOff\nRounding\nCompensation Sizes\nCalculation Method\nAlways Up\nAlways Down\nTo Closest Value\nX-size value\nY-size value"}
{"Headers": " the rules that are used to calculate both the X and Y sizes of the compensating plate", "Content": "Sets the rules that are used to calculate both the X and Y sizes of the compensating plate.\nThe default values/settings indicated on the window are those that exist when the Supports application is first installed.\nClick Reset to revert the Supports Compensation Sizes window to the default values/settings.\nChanges made are only applied to the database when Apply is clicked. To keep the changes the Save Work operation must be performed.\nClick Cancel to close the window. If changes have been made, but not applied, a window displays asking if the changes are to be applied before exiting.\n\nThe Supports Compensation Sizes window contains two tabs for specifying separate rules to calculate the X and Y sizes of the compensating plate.\nThe General Rule is used when a rule for a given support type is not defined.\nThe Default Value field defines the default X and Y sizes of the compensating plate.\nRules can be created for specific support types, input the support codes into the support code field, separated by a space. An asterisk can be used to identify all support types. If two rules are defined for the same support type, the first rule in the list for that support type is used and the second is ignored.\nA rule must always be a Programmable Macro Language (PML) expression that returns a REAL value upon evaluation. If the expression contains references to attributes or properties, the expression is evaluated against the ANCI of the support. Therefore it can contain any attribute or property which is available on the ANCI element.\nTo access the width of the General Section (GENSEC) supporting the ANCI, the syntax 'VVAL( !WIDTH)' can be included into the expression. The profile width in this context is the width of the GENSEC face below the ANCI depending on the profile rotation and may not necessarily correspond to the catalog property WIDT.\nIf the evaluation of the rule expression fails, then the explicitly set default value is used instead.\nTo add a new rule to the list of available rules, click Add Entry to display the Add Entry window.\n\nYou can populate the Support Codes and X-Size Rule or Y-Size Rule fields with the relevant rule values.\nClick OK to add the rule to the list of available rules or Cancel to discard any changes and close the Add Entry window.\nClick Remove Entry to delete the currently selected rule.\n\n\n\nReset\nSupports Compensation Sizes\nApply\nSave Work\nCancel\nSupports Compensation Sizes\nGeneral Rule\nDefault Value\nAdd Entry\nAdd Entry\nSupport Codes\nX-Size Rule\nY-Size Rule\nOK\nCancel\nAdd Entry\nRemove Entry"}
{"Headers": "Sets the available materials for a compensating plate.", "Content": "Sets the available materials for a compensating plate.\nThe default values/settings indicated on the window are those that exist when the supports application is first installed.\nChanges made are only applied to the database when Apply is clicked. To keep the changes the Save Work operation must be performed.\nClick Cancel to close the window. If changes have been made, but not applied, a window displays asking if the changes are to be applied before exiting.\n\nThe Supports Compensation Materials window contains two lists, the first lists the different possible choices of materials and the second lists the available materials.\nTo set a material choice, select the appropriate choice from the list of available choices and then select the material for that choice from the list of available materials.\nDuplicate choices are omitted from the material selection drop-down list in Model.\nThe default choice is the material that is initially set when a compensation is created. It is not possible to remove the default choice.\nThe available materials that can be assigned to a choice are populated from the MDS/PROP database and only solid materials are available for selection.\n\n\n\nApply\nSave Work\nCancel\nSupports Compensation Materials"}
{"Headers": "Multiple Support Catalogs", "Content": "Sets the current MDU catalog. Multiple copies of the MDU catalog can be created to support the use of different catalogs in a single session.\nSelect a catalog from the MDU drop-down list.\n\nCopy MDU Catalog\nCopies an existing MDU Catalog to support the use of multiple catalogs in a single session.\n\nFrom\nSelect from the drop-down list to define the source MDU catalog to be copied.\nTo\nSelect from the drop-down list to define the target location of the created MDU catalog.\nDescription\nInput a name for the created MDU catalog.\nMessages\nDescribes what actions the application is carrying out.\nClick Cancel to discard any changes and close the MDU Catalog Copy window.\nClick Apply to copy the MDU catalog, a Confirm window displays informing you that the operation may take considerable time to complete.\n\nClick Yes to continue with the copy process.\nSupport Configuration File\nBy default, support configuration files are read from the default path which is the installation directory. The default path can be overwritten by setting the environment variable MDS_SUPPORT_CONFIG_LOCATION.\nThe standard support configuration file is named SupportConfigurationFile.xml. Multiple support configuration files are supported.\nNew support catalogs must follow a defined folder path:\nA folder named userSupportConfiguration must be added to the %MDS_SUPPORT_CONFIG_LOCATION% path.\nAll configuration information, for example, image files, the support configuration xml file and any other files specific to that support configuration must be stored in a unique configuration specific folder. This folder uses the naming convention Configuration-<MDU DB CODE>.\nPlot files must be stored in the plots folder which is located in the configuration specific folder.\nSpecific naming conventions must be used, if the internally referenced MDU DB CODE is A, the naming convention is:\nConfiguration specific folder\nConfiguration-A\nSupport configuration file\nSupportConfiguration-A.xml\nFolder for configuration specific plot files\nplots\nImage names & plot file names\nSame naming convention as existing support standards.\nConfiguration specific folder\nConfiguration-A\nSupport configuration file\nSupportConfiguration-A.xml\nFolder for configuration specific plot files\nplots\nImage names & plot file names\nSame naming convention as existing support standards.\nFor example, if the %MDS_SUPPORT_CONFIG_LOCATION% is configured to a folder other than the installation directory, the default configuration xml file (SupportConfiguration.xml) must be located alongside the userSupportConfiguration folder. In the example, the %MDS_SUPPORT_CONFIG_LOCATION% folder is D:\\localSupportConfigurations\\.\n\nThe userSupportConfiguration folder contains a folder for each specific configuration.\n\nThe configuration specific folder contains the plots folder, image files and the support configuration file.\n\nThe plots folder contains the plot files.\n\nA new support catalog that uses the key letter K may require a separate support configuration file, named SupportConfigurationFile-K.xml. The new support configuration file is stored in the configuration specific folder.\n\nThe DimensionsControlConfiguration id value, in the support configuration file, can be set to the defined key letter. For example:\n\nMapping and representation for a specific support type can be defined. For example, AT510 and AT03.\nFor mapping name \"AT510\", the image id is \"at510\". The application searches for the image named at510.png. The image is stored in the same path as the support configuration file.\nFor mapping name \"AT03\", the image id is \"at03\". An image file is not found, the application uses the support standard image.\nIf an external image or a support standard image is not found, a blank image displays.\n<DimensionControlConfiguration id=\"K\">\nNote:\nThe Multiple Support Catalogs functionality is only available when all the databases, for example, MDS/CATA(DB No.7320), MDS/MDSAPPDEFAULTS(DB No.7351) and MDU/CATA(DB No.7355) are part of the selected MDB.\nNote:\nYou are prompted to restart the session for the modifications to take effect.\n\n\n\nNote\n:\nMDU\nCopy MDU Catalog\nFrom\nTo\nDescription\nMessages\nCancel\nMDU Catalog Copy\nApply\nConfirm\nYes\nNote\n:\nSupport Configuration File\nuserSupportConfiguration\n<DimensionControlConfiguration id=\"K\">"}
{"Headers": "Modify User Defined Ancillary Geometry", "Content": "The Supports application allows you to create a set of ancillary standards with their own geometry. Configuration of standards dimensionally is covered in Ancillary Data.\nThe user defined ancillary standards comprise a number of support types. The table displays the user defined ancillary types that have been created that can be configured geometrically:\n\n\nFrom\nTo\n\nAT\nAncillary\nAT500\nAT700\n201\nLT\nLug\nLT500\nLT700\n201\nBT\nU-Bolt\nBT500\nBT700\n201\nAN\nAnchor for shoes\nAN500\nAN569\n70\nAN\nAnchor for pipes\nAN570\nAN639\n70\nAN\nAnchor for trunnions\nAN640\nGT700\n61\nGT\nGuide for shoes\nGT500\nGT569\n70\nGT\nGuide for pipes\nGT570\nGT639\n70\nGT\nGuide for trunnions\nGT640\nGT700\n61\nST\nStops for shoes\nST500\nST569\n70\nST\nStops for pipes\nST570\nST639\n70\nST\nStops for trunnions\nST640\nST700\n61\nAC\nAncillary Components for Trunnions\nAC500\nAC599\n100\nAC\nPlate Component for Trunnions\nAC600\nAC700\n101\nCA\nCable Tray Ancillaries\nCA500\nCA700\n201\nThe ability to create the user defined ancillary types is achieved by supports being configured to use a blank set of ancillaries, so that users can complete their own geometry. A user project called MDU is created; a hierarchy /MDU prefix is used instead of the /MDS prefix where applicable. The example displays how this is implemented into a supports project environment.\n\nThe MDU project has the geometry and point sets pre-created and linked into the Multi Discipline Supports (MDS) catalog and specification. The geometry sets are empty and the point sets have the minimum p-point requirements. You can then create the geometry within the MDU project and set up any design parameters required for the component. The MDU project only stores geometry, point and data sets for the types and ranges detailed earlier.\n\n\n\nAncillary Data\nAncillary Data\nFrom\nTo"}
{"Headers": "The geometry sets are created in project MDU", "Content": "The geometry sets are created in project MDU. The examples display what is added and details any properties that are used. You can add geometry using the properties if required and add additional properties as necessary.\nSimple Box Representation\n\nThe box is set to a length of 10, and uses the pipe Outside Diameter (OD) as the X and Y length.\n\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1. All other design parameters are set to 0 (zero), as indicated in the Properties window.\nNo user editable design parameters have been defined.\nAnchor for Shoes\nSimple Anchor Representation\n\n\nThese user standards ask for a pipe shoe to be identified so it can read the shoe parameters Shoe Height and Flange Width in order to size the anchor. It then asks for a section or box to be identified to read the anchor width across the section of box.\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1, 100, 102 and 133.2. All other design parameters are set to 0 (zero), as indicated in the Properties window.\nDesign parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.\nAnchor for Pipes\nSimple Box Representation\n\n\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1. All other design parameters are set to 0 (zero), as indicated in the Properties window.\nNo user editable design parameters have been defined.\nGuide for Shoes\nSimple Guide Representation\n\n\nThese user standards ask for a pipe shoe to be identified so it can read the shoe parameters Shoe Height and Flange Width in order to size the guide.\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1, 100 and 102. All other design parameters are set to 0 (zero), as indicated in the Properties window.\nDesign parameters 1, 2, 3 and 4 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.\nGuide for Pipes\nSimple Guide Representation\n\n\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1 and 0. All other design parameters are set to 0 (zero), as indicated in the Properties window.\nStop for Shoes\nSimple Stop Representation\n\n\nThese user standards ask for a pipe shoe to be identified so it can read the shoe parameters Shoe Height and Flange Width in order to size the Anchor. It then asks for a section or box to be identified to read the anchor width across the section of box.\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1, 100 102 and 133.2. All other design parameters are set to 0 (zero), as indicated in Properties window.\nDesign parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.\nStop for Pipes\nSimple Box Representation\n\n\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1. All other design parameters are set to 0 (zero) as indicated in the Properties window.\nAnchor for Trunnions\nSimple Anchor Representation\n\n\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset. The Plate Length, Plate Width and Plate Thickness are obtained from the identified Base Plate. All other design parameters are set to 0 (zero) as indicated in the Properties window.\nDesign parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.\nStop for Trunnions\nSimple Stop Representation\n\n\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset. The Plate Length, Plate Width and Plate Thickness are obtained from the identified base plate. All other design parameters are set to 0 (zero) as indicated in the Properties window.\nDesign parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.\nGuide for Trunnions\nSimple Guide Representation\n\n\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset. The Plate Length, Plate Width and Plate Thickness are obtained from the identified base plate. All other design parameters are set to 0 (zero) as indicated in the Properties window.\nDesign parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.\nAncillary Component for Trunnions\nSimple Ancillary Representation\n\n\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1. All other design parameters are set to 0 (zero), as indicated in the Properties window.\nNo user editable design parameters have been defined.\nPlate Component for Trunnions\nSimple Plate Representation\n\n\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1. All other design parameters are set to 0 (zero), as indicated in the Properties window.\nNo user editable design parameters have been defined.\nCable Tray Ancillaries\nSimple Cable Tray Ancillary Representation\n\n\nThe three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection type and 21 design parameters have been created. The design parameters are set to 0 (zero) as indicated in the Properties window. Cable ancillaries do not include Minimum/Maximum Insulation and Minimum/Maximum Temperature parameters. The Outside Diameter is always set to 0 (zero) for cable tray ancillaries.\n\n\n\nProperties\nProperties\nProperties\nProperties\nProperties\nProperties\nProperties\nProperties\nProperties\nProperties\nProperties\nProperties\nProperties"}
{"Headers": "These have been created with the minimum points required", "Content": "These have been created with the minimum points required. These are:\nP-Point\nDescription\n1\nArrive point\n2\nLeave point\n3\nBottom of Pipe (BOP) -5mm. For example, bottom of the ancillary geometry -5mm\n9\nBOP (Including geometry if required). For example, bottom of the ancillary geometry\n10\nLeft of pipe\n11\nRight of pipe\n12\nBOP\nP-Point\nDescription\n1\nArrive point\n2\nLeave point\n3\nBottom of Pipe (BOP) -5mm. For example, bottom of the ancillary geometry -5mm\n9\nBOP (Including geometry if required). For example, bottom of the ancillary geometry\n10\nLeft of pipe\n11\nRight of pipe\n12\nBOP\nThe diagram displays the position and directions of the p-points, P1 and P2 are arriving and leave points along the centerline of the pipe.\n\nNote:\nThe default p-points provided cannot be deleted or modified, but additional p-points can be created if required.\n\n\n\nNote\n:"}
{"Headers": " created with the minimum number of elements required", "Content": "These have been created with the minimum number of elements required. These are:\n/Prefix-DESC\nSupport standard\nDESC\n'AT500'\n/Prefix-RNAM\nStandard Replacement Name\nRNAM\n(BEF (AFT (ATTRIB PPRO of DATA /MDS/ATTA/DEFAULTS/AT500/GEN/CCOD , \u2018(\u2018\u2019\u2019) , \u2018\u2019\u2019 )\u2019 ) )\n/Prefix-PA1\nNominal Bore\nNB\nPARA 1\n/Prefix-PA2\nOutside Diameter\nOD\nPARA 2\n/Prefix-PA3\nConnection Type\nCONN\nPARA 3\n/Prefix-WEIG\nComponent Weight\nWEIG\n(ATTRIB DENS of 1 OF 1 of :MDSMatRef * ATTRIB NVOL / 1000 / 1000 / 1000 * VVAL !!MDSWEIUNIT)\n/Prefix-MATR\nComponent Material\nMATR\n(ATTRIB DESC of :MDSMatRef)\n/Prefix-CODE\nSupport Code\nCODE\n(TRIM ( DIST ( NOMBORE ( false , ATTRIB CPAR[1 ] ) , false , false , true , 4 , false ) ) + '-' + ATTRIB PROPRNAM)\n/Prefix-CDES\nMDS Configurable\nDescription\nCDES\n(BEF (AFT (ATTRIB PPRO of DATA /MDS/ATTA/DEFAULTS/AT500/GEN/DESC , \u2018( \u2018\u2019\u2019 ) \u2018\u2019\u2019 ) ) )\n/Prefix-DP1\nDesign Parameter 1\nUnset\nDESP[1]\nWhere /Prefix is /Standard-DATA-, for example, /AT500-DATA-DESC and the standard used is AT500\nYou can add/modify the data set as necessary.\n\n\n"}
{"Headers": "The catalog items", "Content": "The catalog items for the user defined ancillaries have been created in the ranges detailed within the MDU project. The MDU project contains all the catalog elements, For example, SCOM, 3D Geomset Elemen (GMSE), Pointset Element (PTSE), Data Set (DTSE) and SDTE, where the user modifies the GMSE to suit their requirements. The specification components for ALL the user defined ancillaries are in the /MDS specification in the Multi Discipline Supports (MDS) project, which must not be modified by users.\n\n\nFrom\nTo\nFrom\nTo\nAT\nAncillary\nAT01\nAT115\nAT500\nAT700\nLT\nLug\nLT01\nLT16\nLT500\nLT700\nBT\nU-Bolt\nBT01\nBT11\nBT500\nBT700\nAN\nAnchor\nAN01\nAN18\nAN500\nAN700\nGT\nGuide\nGT01\nGT50\nGT500\nGT700\nST\nStop\nST01\nST33\nST500\nST700\nThe MDU project catalog hierarchy has been created for a size range of 8mm (1/4\") to 1200mm (48\") in the bore sizes that display:\n8\n1/4\n13.7\n14\n15\n3/8\n21.3\n21\n20\n1/2\n26.7\n26\n25\n1\n33.4\n33\n32\n1.1/4\n42.2\n42\n40\n1.1/2\n48.3\n48\n50\n2\n60.3\n61\n65\n2.1/2\n73\n73\n80\n3\n88.9\n89\n100\n4\n114.3\n115\n125\n5\n141.3\n141\n150\n6\n168.3\n169\n200\n8\n219.1\n220\n250\n10\n273\n273\n300\n12\n323.8\n324\n350\n14\n355.6\n358\n400\n16\n406.4\n407\n450\n18\n457\n457\n500\n20\n508\n508\n550\n22\n559\n559\n600\n24\n610\n610\n650\n26\n660\n660\n700\n28\n711\n711\n750\n30\n762\n762\n800\n32\n813\n813\n850\n34\n864\n864\n900\n36\n914\n914\n950\n38\n965\n965\n1000\n40\n1016\n1016\n1050\n42\n1067\n1067\n1100\n44\n1118\n1118\n1150\n46\n1168\n1168\n1200\n48\n1219\n1219\n\n\n\n\nMDS\nMDS"}
{"Headers": "Teh standard pipework in Aveva Catalog", "Content": "You can use the standard pipework application in AVEVA Catalog to modify the required elements within the MDU catalog database. For example,\nMDU/CATA <dbnum7355,dbfile%MDU000/mdu7355>.\nWithin the MDU project, the following should not be deleted or modified (including name change):\nCATREF\n(Catalog Reference)\nPTREF\n(P-Point Set Reference)\n(refer to the Note for further information)\nGMREF\n(Geometry Set Reference)\n(refer to the Note for further information)\nDTREF\n(Data Set Reference)\n(refer to the Note for further information)\n\nCATREF\n(Catalog Reference)\n\n\nPTREF\n(P-Point Set Reference)\n(refer to the Note for further information)\n\nGMREF\n(Geometry Set Reference)\n(refer to the Note for further information)\n\nDTREF\n(Data Set Reference)\n(refer to the Note for further information)\nNote:\nAlthough the MDU default p-points provided cannot be deleted or modified, additional p-points can be created. Also, geometry can be added to the geometry sets, and additional properties included as necessary\n\n\n\nNote\n:"}
{"Headers": "Support Standards", "Content": "Various Support Standards are available.\n\n\n"}
{"Headers": "The standards are available in the Supports application", "Content": "The standards are available in the Supports application, but are automatically created when creating an ancillary standard (refer to Ancillaries for further information).\nThe standards marked with a * are not available in the Supports application. These standards are obsolete and have been replaced by other new standards.\nAC01*\nXAC01\nForged eye rod.\nAC02*\nXAC02\nFully threaded rod.\nAC03*\nXAC03\nTurnbuckle.\nAC04*\nXAC04\nClevis.\nAC05*\nXAC05\nWeldless eye nut (bow).\nAC06*\nXAC06\nBeam welding attachment.\nAC07*\nXAC07\nWelding lug.\nAC08*\nXAC08\nClevis plate.\nAC09*\nXAC09\nSpherical washer.\nAC10\nXAC10\nPipe clamp (light).\nAC11*\nXAC11\nPipe clamp (heavy).\nAC12*\nXAC12\nPipe clamp for insulated pipe (light).\nAC13*\nXAC13\nPipe clamp for insulated pipe (heavy).\nAC14*\nXAC14\nPipe clamp for Cu-Ni pipe.\nAC15*\nXAC15\nPipe clamp for insulated Cu-Ni pipe.\nAC16*\nXAC16\nRiser clamp.\nAC17\nXAC17\nVessel Support Lug\nAC18A\nXAC18A\nBase Plate\nAC18B\nXAC18B\nBase Plate\nAC19A\nXAC19A\nBearing Plate\nAC19B\nXAC19B\nBearing Plate\nAC20\nXAC20\nCollar\nAC21\nXAC21\nBase plate for RTJ Joints\nAC22\nXAC22\nBolt on base support\nAC24\nXAC24\nReinforcing Pad\nAC25\nXAC25\nDummy branch end plate\nAC27\nXAC27\nBreak Out Plates with Shim\nAC28\nXAC28\nStrap On Clamp for RTR Pipe\nAC29\nXAC29\nBolted Clamp Assembly\nAC30\nXAC30\nAdjustable Baseplate\nAC31\nXAC31\nAnchor Bolted Clamp Assembly\nAC32\nXAC32\nBreak Out Plates with Shim\nAC33\nXAC33\nEnd Plate for Rod Hanger Trunnion\nAC34\nXAC34\nReinforcing Pad\nAC35\nXAC35\nPipe Clamp\nAC36\nXAC36\nU Strap\nAC37\nXAC37\nPipe Riser Clamp\nAC38\nXAC38\nGuide Trunnions\nAC39\nXAC39\nIsolation Block Acoustic/General for Trunnion XTT23\nAC40\nXAC40\nGeneral Slide Unit for Trunnion XTT23\nAC41\nXAC41\nCold Isolation Block for Trunnion XTT23\nAC44\nXAC44\nClamp for Trunnions for Diam 2\" to 24\"\nAC45\nXAC45\nClamp for Dummy Legs for Diam 2\" to 24\"\nAC46\nXAC46\nLTCS Upper Break Out Plate for Trunnion XTT23\nAC47\nXAC47\nCS Base Plate for Trunnion XTT23\nAC48\nXAC48\nCS Lower Break Out Plate for Trunnion XTT23\nAC49\nXAC49\nBase Plate 1.1/2\" to 16\"\nAC50\nXAC50\nEnd Plate 2\" to 24\"\nAC51\nXAC51\nSupport Plate 2\" to 24\"\nAC52\nXAC52\nStiffener 2\" to 24\"\nAC53\nXAC53\nGRE Pipe Clamps for diam 1.1/2\" to 40\"\nAC54\nXAC54\nCPVC Pipe Clamps for diam 1.1/2\" to 12\"\nAC55\nXAC55\n4 Bolt Clamp for Trunnions diam 2.1/2\" to 24\"\nAC56\nXAC56\nBase Plate Circular\nAC57\nXAC57\nAdjustable Trunnion Base Plate 1.1/2\" to 24\"\nAC58\nXAC58\nPipe Clamp for Trunnions - DN 20-250\nAC59\nXAC59\nBase Plate for Trunnions - DN 20-250\n\n\n\n\nAncillaries\nAncillaries"}
{"Headers": "The standards are available in the Supports application user defined anchor standard", "Content": "The standards are available in the Supports application.\nThe standards marked with a * are not available in the Supports application. These standards are obsolete and have been replaced by other new standards.\nRefer to Modify User Defined Ancillary Geometry for further information on user defined anchor standards.\nAN01A*\nXAN01A\nPedestal Anchor Type A.\nAN01B*\nXAN01B\nPedestal Anchor Type B.\nAN02\nXAN02\nPipe Shoe Anchor.\nAN03\nXAN03\nPipe Shoe Anchor.\nAN04\nXAN04\nBolted Anchor shoe for Hot insulated pipe or temp transport NPS 2-36.\nAN05\nXAN05\nTemporary restraint NPS 2-20.\nAN06\nXAN06\nBolt on Shoe w/Directional Anchor Cold (Cryogenic) Service (50/100mm Insu) NPS 3 - 48\nAN07A\nXAN07\nAnchor U Bolt (AB) Black, NPS 2 - 20.\nAN07B\nXAN07\nAnchor U Bolt (AG) Galvanised, NPS 2 - 20.\nAN07C\nXAN07\nAnchor U Bolt (AP) Plastic Coated, NPS 2 - 20.\nAN08\nXAN08\nPipe Clamp Anchor For RTR Pipe NPS 2-24.\nAN09\nXAN09\nOverstrap Anchor (C.S./Alloy Pipes) NPS 1/2- 20\nAN10\nXAN10\nDirectional Anchor NPS 1-36.\nAN11\nXAN11\nBolt On Anchor For Galvanised Pipe NPS 6-12.\nAN12A\nXAN12A\nFlat Clamp for CS pipes NPS 1.1/2-16.\nAN12B\nXAN12B\nFlat Clamp with Neoprene Sleeve for SS pipes NPS 1.1/2-16.\nAN13\nXAN13\nHALFEN Anchor HCS RADV NPS 1\" 6\"\nAN17\nXAN17\nAnchor U Bolt for Cupro Nickel Lines, NPS 1/2- 8.\nAN18\nXAN18\nAnchor U Bolt for Carbon Steel Lines, NPS 1/2- 8.\nAN19\nXAN19\nAnchor - DN 15-1400\nAN20\nXAN20\nU-Bolt Anchor\nAN21\nXAN21\nAnchor Low\nAN22\nXAN22\nAnchor Low\nAN23\nXAN23\nAnchor Low 2-Sided\nAN24\nXAN24\nAnchor Low 2-Sided\nAN25\nXAN25\nAnchor High\nAN26\nXAN26\nAnchor High 2-Sided\nAN27\nXAN27\nAnchor High\nAN28\nXAN28\nAnchor High 2-Sided\nAN29\nXAN29\nAnchor High\nAN30\nXAN30\nAnchor High 2-Sided\nAN31\nXAN31\nAnchor Extra High\nAN32\nXAN32\nAnchor Extra High 2-Sided\nAN33\nXAN33\nAnchor Extra High\nAN34\nXAN34\nAnchor Extra High 2-Sided\nAN35\nXAN35\nAnchor Extra High\nAN36\nXAN36\nAnchor Extra High 2-sided\nAN37\nXAN37\nU-Bolt Guide\nAN38\nXAN38\nAnchor Low\nAN39\nXAN39\nAnchor Low 2-Sided\n\n\n\n\nModify User Defined Ancillary Geometry\nModify User Defined Ancillary Geometry"}
{"Headers": "The standards are available in the Supports application User Defined Ancillary Standards.", "Content": "The standards are available in the Supports application.\nThe standards marked with a * are not available in the Supports application. These standards are obsolete and have been replaced by other new standards.\nRefer to Modify User Defined Ancillary Geometry for further information on User Defined Ancillary Standards.\nPIPE-REST\nXRT01\nPipe Rest\nPIPE-REST-INLINE\nXRT02\nPipe Rest Inline for Trunnions\nAT01\nXAT001\nPipe shoe for N.B. 3/4\" to 20\"\nAT02\nXAT002\nPipe shoe for N.B. 24\" to 48\"\nAT03\nXAT003\nClamp on pipe shoe for N.B. 3/4\" to 20\"\nAT04\nXAT004\nClamp on pipe shoe for N.B. for pipe Cu-Ni 2\" to 20\"\nAT05\nXAT005\nReinforcing plate (cut from pipe)\nAT06\nXAT006\nClamp on pipe shoe for stainless or galvanised pipe\nAT07\nXAT007\nPipe shoe with reinforcing plate for N.B. 3/4\" to 20\"\nAT08\nXAT008\nPipe shoe with reinforcing plate for N.B. 24\" to 48\"\nAT09\nXAT009\nReinforcing plate (cut from plate)\nAT10A*\nXAT10A\nPedestal support for elbows (type A)\nAT10B*\nXAT10B\nPedestal support for tube (type B)\nAT11A*\nXAT11A\nAdjustable pedestal support for elbows (type A)\nAT11B*\nXAT11B\nAdjustable pedestal support for tube (type B)\nAT12\nXAT012\nShoe for C.S. Pipe. Hot Service (63mm Maximum Insu.) NPS 2\"-36\"\nAT13\nXAT013\nShoe for C.S. Pipe. Hot Service (75mm/100mm Insu.) NPS 2\"-36\"\nAT14\nXAT014\nShoe for Low Temp C.S. Pipe. Inter. Service to -46 c (75mm/100mm Insu.) NPS 2\"-36\"\nAT15\nXAT015\nShoe for Low Temp C.S. Pipe. Inter. Service to -46 c (63mm Maximum Insu.) NPS 2\"-36\"\nAT16\nXAT016\nBolt on Shoe, Heat Insulated & Uninsulated C.S. NPS 2\"-32\"\nAT17\nXAT017\nShoe for RTR Pipe, NPS 2-14\nAT18\nXAT018\nShoe for Low Temp S.S. Pipe. Inter. Service <-46 c (63mm Maximum Insu.) NPS 2\"-36\"\nAT19\nXAT019\nShoe for Low Temp S.S. Pipe. Inter. Service <-46 c (75mm/100mm Insu.) NPS 2\"-36\"\nAT20\nXAT020\nClamp on shoe for Cu-Ni NPS 2 - 24\nAT21\nXAT021\nPipe Guide for reciprocating Compressor Pipe 2\" to 24\"\nAT22\nXAT022\nTemporary Transport Anchor for NPS 6-36 Uninsulated C.S.\nAT23\nXAT023\nWelded Cradle Support for Uninsulated Pipe or Shoe, NPS 2 1/2 - 36\nAT24\nXAT024\nCradle for RTR Pipe NPS 2 - 4\nAT25\nXAT025\nBolt On Shoe Cold (Cryogenic) Service (25mm/100mm Insu.) NPS 3\" - 48\"\nAT26\nXAT026\nCradle for Cold Service (30 - 150mm Insulation), NPS 1/2 - 2.\nAT27\nXAT027\nHanger Clamp for RTR Pipe NPS 2 - 24.\nAT28\nXAT028\nU Bolt Guide for RTR pipe NPS 2 - 24.\nAT29A\nXAT029A\nReinforcing Pad for straight pipe for C.S. pipe.\nAT29B\nXAT029B\nReinforcing Pad for elbow for C.S. pipe.\nAT30\nXAT030\nSpecial Shim Assembly for Sloping Lines NPS 2-36\nAT31A\nXAT031A\nReinforcing Pad for straight pipe for High Alloy/SST pipe.\nAT31B\nXAT031B\nReinforcing Pad for elbow for High Alloy/SST pipe.\nAT32\nXAT032\nPipe Strap (Lined) for Galv. and S.S Lines NPS 1.1/2 - 8\nAT33A\nXAT033A\nTrunnion Isolation Pad(Type A - 140mm x 140mm) -Acoustic/General - NPS 1/2 - 24\nAT33B\nXAT033B\nTrunnion Isolation Pad(Type B - 140mm x 250mm) - Acoustic/General - NPS 1/2 - 24\nAT33C\nXAT033C\nTrunnion Isolation Pad(Type C - 140mm x 300mm) - Acoustic/General - NPS 1/2 - 24\nAT33D\nXAT033D\nTrunnion Isolation Pad(Type D - 200mm x 200mm) - Acoustic/General - NPS 1/2 - 24\nAT33E\nXAT033E\nTrunnion Isolation Pad(Type E - 250mm x 250mm) - Acoustic/General - NPS 1/2 - 24\nAT33F\nXAT033F\nTrunnion Isolation Pad(Type F - Variable Size) - Acoustic/General - NPS 1/2 - 24\nAT34A\nXAT034A\nTrunnion Slide Unit(Type A - 140mm x 140mm) - General - NPS 1/2 - 24\nAT34B\nXAT034B\nTrunnion Slide Unit(Type B - 140mm x 250mm) - General - NPS 1/2 - 24\nAT34C\nXAT034C\nTrunnion Slide Unit(Type C - 140mm x 300mm) - General - NPS 1/2 - 24\nAT34D\nXAT034D\nTrunnion Slide Unit(Type D - 200mm x 200mm) - General - NPS 1/2 -24\nAT34E\nXAT034E\nTrunnion Slide Unit(Type E - 250mm x 250mm) - General - NPS 1/2 - 24\nAT34F\nXAT034F\nTrunnion Slide Unit(Type F - Variable Size) - General - NPS 1/2 - 24\nAT35\nXAT035\nCold Isolation Block with CS Cage for Trunnion XTT23\nAT36\nXAT036\nTico Isolation Wrap - Temp. -40 to +100 deg.C (C.S./Alloy/Cu-Ni Pipes) - NPS 1/2 - 24.\nAT37\nXAT037\nTico Isolation Wrap - Temp. +101 to +150 deg.C (C.S./Alloy/Cu-Ni Pipes) - NPS 1/2 - 24.\nAT38\nXAT038\nBonded Neoprene Rubber Isolation Wrap - Temp. -40 to +100 deg.C (CS/Alloy/Cu-Ni Pipes) - NPS 1/2 - 24\nAT39\nXAT039\nBonded Viton Rubber Isolation Wrap - Temp. +101 to +150 deg.C (CS/Alloy/Cu-Ni Pipes) - NPS 1/2 -24\nAT40A\nXAT040A\nIsolation Pad(Type A - 140mm x 140mm) - Acoustic/General - NPS 1/2 - 24\nAT40B\nXAT040B\nIsolation Pad(Type B - 140mm x 250mm) - Acoustic/General - NPS 1/2 - 24\nAT40C\nXAT040C\nIsolation Pad(Type C - 140mm x 300mm) - Acoustic/General - NPS 1/2 - 24\nAT40D\nXAT040D\nIsolation Pad(Type D - 200mm x 200mm) - Acoustic/General - NPS 1/2 - 24\nAT40E\nXAT040E\nIsolation Pad(Type E - 250mm x 250mm) - Acoustic/General - NPS 1/2 - 24\nAT40F\nXAT040F\nIsolation Pad(Type F - Variable Size) - Acoustic/General - NPS 1/2 - 24\nAT41A\nXAT041A\nSlide Unit(Type A - 140mm x 140mm) - General - NPS 1/2 - 24\nAT41B\nXAT041B\nSlide Unit(Type B - 140mm x 250mm) - General - NPS 1/2 - 24\nAT41C\nXAT041C\nSlide Unit(Type C - 140mm x 300mm) - General - NPS 1/2 - 24\nAT41D\nXAT041D\nSlide Unit(Type D - 200mm x 200mm) - General - NPS 1/2 - 24\nAT41E\nXAT041E\nSlide Unit(Type E - 250mm x 250mm) - General - NPS 1/2 - 24\nAT41F\nXAT041F\nSlide Unit(Type F - Variable Size) - General - NPS 1/2 - 24\nAT42\nXAT042\nPTFE Isolation Pad - Bonded to Steel - NPS 1.1/2 - 24\nAT43\nXAT043\nPipe Penetration Single Seal (Packed) - Certified A0 & H0 Rating NPS 1/2 - 24\nAT44\nXAT044\nPipe Penetration Single Seal (Packed) - Certified A60 & H60 Rating - NPS 1/2 - 24\nAT45\nXAT045\nPipe Penetration Double Seal - Certified A0 & H0 Rating w/o Insulation & A60 H60 & H120 Rating with Insulation, NPS 1/2 - 24\nAT46\nXAT046\nPipe Penetration Double Seal - Certified upto J100 Jet Fire Resistance & A60 H60 & H120 Rating NPS 1/2 - 24\nAT47\nXAT047\nCold Isolation Shoe (C.S./Alloy Pipes) NPS 2 - 8\nAT48\nXAT048\nCold Isolation Shoe (C.S./Alloy Pipes) NPS 10 - 24\nAT49\nXAT049\n2 Bolt Heavy Series Pipe Clamp with Circular Cold Isolation Block (CS/Alloy Pipes) - NPS 1/2 - 24\nAT50\nXAT050\nReinforcing Pad for Horizontal and Vertical Cu-Ni Pipes - NPS 2.1/2 - 24\nAT51\nXAT051\nFull Encirclement Reinforcing Sleeve for Cu-Ni Pipes - NPS 2.1/2 - 24\nAT52A\nXAT052A\nType A Protection Shield for Diam 2\" to 24\"\nAT52B\nXAT052B\nType B Protection Shield for Diam 2\" to 24\"\nAT52C\nXAT052C\nType C Protection Shield for Diam 2\" to 24\"\nAT52D\nXAT052D\nType D Protection Shield for Diam 2\" to 24\"\nAT52E\nXAT052E\nType E Protection Shield for Diam 2\" to 24\"\nAT52F\nXAT052F\nType F Protection Shield for Diam 2\" to 24\"\nAT53A\nXAT053A\nType A 4 Point Shear Lug Bearing for Diam 2\" to 24\"\nAT53B\nXAT053B\nType B 2 Point Shear Lug Bearing for Diam 2\" to 24\"\nAT54\nXAT054\nHP Mud and Cement High Pressure Clamps for Diam 2\" to 6\"\nAT55A\nXAT055A\nBolt on Shoe type A Uninsulated C.S. NPS 2\"-6\"\nAT55B\nXAT055B\nBolt on Shoe type B Uninsulated C.S. NPS 2\"-6\"\nAT55C\nXAT055C\nBolt on Shoe type C Uninsulated C.S. NPS 8\"-24\"\nAT56\nXAT056\nClamp for Vertical support NPS 2\" to 8\"\nAT57\nXAT057\nHALFEN Pipe Shoe HRG-4 NPS 1/2\" - 6\"\nAT58\nXAT058\nHALFEN Pipe Shoe HRG - 4 with Spacer Clip HCS AHS 5/1 NPS 1/2\" - 6\"\nAT59\nXAT059\nTrunnion Cold Isolation Block with Integral Base Plate Light\nAT60\nXAT060\nFlanged Supports for FRP/RTR Lines 1\" - 32\"\nAT61\nXAT061\nPlate Attachment - Vertical Pipe (CS, LTCS, SS Pipes) - NPS 12\"-48\"\nAT62\nXAT062\nAdjustable Guide Insert Bolts Parallel NPS 2\"-48\"\nAT63\nXAT063\nPipe Strap (Lined) for FRP / RTR Lines NPS 1 - 8\nAT64\nXAT064\nPipe Strap (Lined) for CuNi Lines NPS 1.1/2 - 8\nAT65\nXAT065\nFull Encirclement Wrapper Plate (no longitudinal welding) for Pipes - NPS 2 - 48\nAT66\nXAT066\nStauff Clamp Heavy Series SPAL **,***,* xxx DPAL-AS NPS 1/2 - 6\"\nAT67\nXAT067\nStauff Clamp Heavy Series SPAL/DUB **,***,* xxx DPAL-AS NPS 1/2\" - 6\"\nAT68\nXAT068\nTrunnion Cold Isolation Block with Integral Base Plate Heavy\nAT69\nXAT069\nAdjustable Guide Insert Bolts Perpendicular - NPS 2\"-48\"\nAT70\nXAT070\nAdjustable Guide Insert Offset to Pipe Bolts Parallel - NPS 2\"-48\"\nAT71\nXAT071\nAdjustable Guide Insert Offset to Pipe Bolts Perpendicular - NPS 2\"-48\"\nAT72\nXAT072\nCPVC Pipe shoes height 100 to 200 for diam 1-1/2\" to 24\"\nAT73\nXAT073\nGRE Pipe shoes height 100 to 200 for diam 26\" to 40\"\nAT74A\nXAT074A\nCPVC Protection shield for diam 1/2\" to 16\" TYPE A\nAT74B\nXAT074B\nCPVC Protection shield for diam 1/2\" to 16\" TYPE B\nAT75A\nXAT075A\nAnti friction sliding plate for diam 1/2\" to 40\" TYPE A\nAT75B\nXAT075B\nAnti friction sliding plate for diam 1/2\" to 40\" TYPE B\nAT76\nXAT076\nPipe Shoe NPS 18\"-20\"\nAT87\nXAT087\nGRE Pipe shoes height 100 to 200 for diam 1-1/2\" to 24\"\nAT88\nXAT088\nDN8 - DN50 - Single sided Pipe Slide\nAT93\nXAT093\nGRE Pipe Clamps for diam 1.1/2\" to 40\"\nAT94\nXAT094\nCPVC Pipe Clamps for diam 1.1/2\" to 12\"\nAT95A\nXAT095A\nGRE Protection shield for diam 1/2\" to 16\" TYPE A\nAT95B\nXAT095B\nGRE Protection shield for diam 1/2\" to 16\" TYPE B\nAT96\nXAT096\nWelded Shoe for N.P.S. 1\" - 36\"\nAT97\nXAT097\nClamped Shoe (Unlined) for N.P.S. 1\" - 24\"\nAT98\nXAT098\nWelded Shoe with re-pad for N.P.S. 1\" - 36\"\nAT99\nXAT099\nClamped Shoe (Lined) for N.P.S. 1\" - 24\"\nAT100A\nXAT100A\nTrunnion Ptfe Faced Slide Unit (Suitable for Acoustic & Vibration Isolation) Type A - NPS 1/2 - 24\nAT100B\nXAT100B\nTrunnion Ptfe Faced Slide Unit (Suitable for Acoustic & Vibration Isolation) Type B - NPS 1/2 - 24\nAT101A\nXAT101A\nPtfe Faced Slide Unit (Suitable for Acoustic & Vibration Isolation) Type A - NPS 1/2 - 24\nAT101B\nXAT101B\nPtfe Faced Slide Unit (Suitable for Acoustic & Vibration Isolation) Type B - NPS 1/2 - 24\nAT102\nXAT102\nPipe Strap\nAT103A\nXAT103A\nClamped Pipe Shoe Pihasa 2134 IPE 160 NPS 1/2 - 4\nAT103B\nXAT103B\nClamped Pipe Shoe Pihasa 2134 IPE 200 NPS 1/2 - 16\nAT103C\nXAT103C\nClamped Pipe Shoe Pihasa 2134 IPE 240 NPS 3 - 16\nAT103D\nXAT103D\nClamped Pipe Shoe Pihasa 2134 IPE 270 NPS 5 - 16\nAT104A\nXAT104A\nClamped Pipe Shoe Pihasa 2136 Small NPS 1.1/2 - 30\nAT104B\nXAT104B\nClamped Pipe Shoe Pihasa 2136 Large NPS 1.1/2 - 30\nAT105A\nXAT105A\nReinforcing Pad for straight pipe/elbow for C.S. pipe.\nAT105B\nXAT105B\nReinforcing Pad for straight pipe/elbow for C.S. pipe.\nAT108A\nXAT108A\nLisega Type 49xx11 Pipe Clamp Base 0 to 350 deg.C - NPS 15 - 150\nAT108B\nXAT108B\nLisega Type 49xx12 Pipe Clamp Base - 0 to 350 deg.C - NPS 15 - 125\nAT108C\nXAT108C\nLisega Type 49xx13 Pipe Clamp Base - 0 to 350 deg.C - NPS 175 - 1000\nAT108D\nXAT108D\nLisega Type 49xx14 Pipe Clamp Base - 0 to 350 deg.C - NPS 15 - 900\nAT108E\nXAT108E\nLisega Type 49xx25 Pipe Clamp Base - 350 to 500 deg.C - NPS 15 - 900\nAT108F\nXAT108F\nLisega Type 49xx35 Pipe Clamp Base - 450 to 560 deg.C - NPS 15 - 900\nAT108G\nXAT108G\nLisega Type 49xx45 Pipe Clamp Base - 560 to 600 deg.C - NPS 15 - 900\nAT108H\nXAT108H\nLisega Type 49xx64 Pipe Clamp Base - 100 to 350 deg.C - NPS 15 - 125\nAT108AX\nXAT108AX\nLisega Type 49xx11 (Larger Pipe Outside Diameter) Pipe Clamp Base - 0 to 350 deg.C - NPS 65,100,125,150 - ONLY\nAT108BX\nXAT108BX\nLisega Type 49xx12 (Larger Pipe Outside Diameter) Pipe Clamp Base - 0 to 350 deg.C - NPS 65,100,125 - ONLY\nAT108CX\nXAT108CX\nLisega Type 49xx13 (Larger Pipe Outside Diameter) Pipe Clamp Base - 0 to 350 deg.C - NPS 250,350,400 - ONLY\nAT108DX\nXAT108DX\nLisega Type 49xx14 (Larger Pipe Outside Diameter) Pipe Clamp Base - 0 to 350 deg.C - NPS 65,100,125,150,250,350,400 - ONLY\nAT108EX\nXAT108EX\nLisega Type 49xx25 (Larger Pipe Outside Diameter) Pipe Clamp Base - 350 to 500 deg.C - NPS 65,100,125,150,250,350,400 - ONLY\nAT108FX\nXAT108FX\nLisega Type 49xx35 (Larger Pipe Outside Diameter) Pipe Clamp Base - 450 to 560 deg.C - NPS 65,100,125,150,250,350,400 - ONLY\nAT108GX\nXAT108GX\nLisega Type 49xx45 (Larger Pipe Outside Diameter) Pipe Clamp Base - 560 to 600 deg.C - NPS 65,100,125,150,250,350,400 - ONLY\nAT108HX\nXAT108HX\nLisega Type 49xx64 (Larger Pipe Outside Diameter) Pipe Clamp Base - 100 to 350 deg.C - NPS 65,100,125 - ONLY\nAT109\nXAT109\nPipe Strap\nAT111\nXAT111\nSlider Pad for diam 1/2\" to 40\"\nAT112\nXAT112\nLoose Pipe Strap 1/4\" to 36\"\nAT113\nXAT113\nPipe Strap 1/4\" to 36\"\nAT114\nXAT114\nLisega Type 49xx63SP Pipe Clamp base - 0 to 350 deg.C - NPS 175 - 700\nAT115\nXAT115\nLisega Type 49xx63G Pipe Clamp base - 0 to 350 deg.C - NPS 250,700,900,1000\nAT116\nXAT116\nDouble Heavy Vertical Pipe Clamp - DN 15-1400\nAT117\nXAT117\nDouble Light Vertical Pipe Clamp - DN 15-1400\nAT118\nXAT118\nSingle Light Vertical Pipe Clamp - DN 15-1400\nAT119\nXAT119\nVertical Pipe Clamp for Spring Cans - DN 15-1400\nAT120\nXAT120\nSingle Light Vertical Pipe Clamp - DN 15-1400\nAT121\nXAT121\nSingle Heavy Vertical Pipe Clamp - DN15-1400\nAT122\nXAT122\nDouble Heavy Vertical Pipe Clamp - DN 15-1400\nAT123\nXAT123\nSingle Light Vertical Pipe Clamp - DN 15-1400\nAT124\nXAT124\nSingle Light Vertical Pipe Clamp - DN 15-1400\nAT125\nXAT125\nDouble Heavy Vertical Pipe Clamp - DN15-1400\nAT126\nXAT126\nPipe Shoe with Clamps - DN 15-1400\nAT127\nXAT127\nPipe Shoe with Clamps Cold Insulation - DN 15-800\nAT128\nXAT128\nPipe Shoe - DN 400-600\nAT129\nXAT129\nPipe Shoe - DN 650-1000\nAT130\nXAT130\nPipe Shoe with Clamps - DN 250-450\nAT131\nXAT131\nPipe Shoe with Clamps - DN 500-1000\nAT132\nXAT132\nPipe Clamp with Double Shoes - DN 50-1400\nAT133\nXAT133\nBand for Copper Pipe NPS 2.5 - 8\nAT134\nXAT134\nPipe Strap (lined) NPS 3/8 -1\nAT135\nXAT135\nSliding Piece (Pipe Welded) NPS 1/2 - 40\nAT136\nXAT136\nLisega Type 49xx63G1SP Single-sided Pipe Slide - 0 to 350 deg. C - NPS 250,700,900,1000\nAT140\nXAT140\nClamped Pipe Shoe for S/S,6Mo & Duplex lines. - Temp -130 to 340 deg.C 4\" to 24\"\nAT141\nXAT141\nWelded Pipe Shoe for S/S,6Mo & Duplex lines - Sch10s & below. Heavy Load or Vibration 6\" to 24\"\nAT144\nXAT144\nWelded Pipe Shoe for CS & LTCS lines - 3/4\" to 24\"\nAT145\nXAT145\nClamped Pipe Shoe for CS & LTCS lines - 3/4\" to 36\"\nAT146\nXAT146\nWelded Pipe Shoe for S/S Lines - 3/4\" to 24\"\nAT147\nXAT147\nWelded Pipe Shoe for Duplex lines - 3/4\" to 24\"\nAT148\nXAT148\nWelded Pipe Shoe for 6Mo lines - 3/4\" to 24\"\nAT149\nXAT149\nClamped Pipe Shoe for Galv,S/S 6Mo & Duplex lines - 3/4\" to 36\"\nAT150\nXAT150\nWelded Pipe Shoe with Repad for S/S,6Mo and Duplex lines - 3/4\" to 24\"\nAT151\nXAT151\nWelded Pipe Shoe with Repad for CS & LTCS lines - 3/4\" to 24\"\nAT152\nXAT152\nOglaend Pipe Clamp AISI 316L 1/2\" to 2\"\nAT153\nXAT153\nOglaend Pipe Clamp AISI 316L 1/2\" to 2\"\nAT154\nXAT154\nAngle bracket for U-Bolt diam 1/2\" to 8\"\nAT155\nXAT155\nAngle bracket for U-Bolt diam 1/2\" to 8\"\nAT156\nXAT156\nOglaend Pipe Clamp HDG 1/2\" to 2\"\nAT157\nXAT157\nOglaend Pipe Clamp HDG 1/2\" to 2\"\nAT158\nXAT158\nClamped Pipe Shoe for FRP Pipe - 2\" to 36\"\nAT159\nXAT159\nClamped Pipe Shoe for FRP Pipe - 2\" to 36\"\nAT160A\nXAT160\nType A - Clamped Pipe Short Shoe Linestop for FRP Pipe - 2\" to 36\"\nAT160B\nXAT160\nType B - Clamped Pipe Long Shoe Linestop for FRP Pipe - 2\" to 36\"\nAT161\nXAT161\nDN3 - DN20 - Single-sided Pipe Slide\nAT162\nXAT162\nDN8 - DN50 - Austenitic Single-sided Pipe Slide\nAT163\nXAT163\nDN3 - DN20 - Austenitic Single-sided Pipe Slide\nAT164\nXAT164\nOglaend Single Clamp Shoe - Uninsulated pipe 1\" to 6\"\nAT165\nXAT165\nOglaend Single Clamp Shoe - Insulated pipe 1/2\" to 6\"\nAT166\nXAT166\nAngle bracket for Pipe Clamp diam 1/2\" to 2\"\nAT167\nXAT167\nAngle bracket for U-Bolt diam 1\" to 4\"\nAT168\nXAT168\nOglaend Pipe Clamp diam 1/2\" to 1.1/2\"\nAT174\nXAT174\nFull Encirclement Reinforcing pad (cut from pipe)\nAT175\nXAT175\nPart Encirclement Reinforcing pad (cut from pipe)\nAT185\nXAT185\nButterfly Valve Support F4\nAT211\nXAT211\nPipe Slide Low\nAT212\nXAT212\nPipe Slide Low 2-Sided\nAT213\nXAT213\nPipe Slide Low\nAT214\nXAT214\nPipe Slide Low 2-Sided\nAT215\nXAT215\nFoot Support A2\nAT216\nXAT216\nFoot Support A3\nAT217\nXAT217\nPipe Slide Low 3-Sided\nAT218\nXAT218\nPipe Slide Low 3-Sided\nAT219\nXAT219\nFoot Support A1\nAT220\nXAT220\nFoot Support B1\nAT221\nXAT221\nFoot Support B2\nAT222\nXAT222\nFoot Support B3\nAT223\nXAT223\nPipe Slide\nAT224\nXAT224\nPipe Slide\nAT225\nXAT225\nPipe Clamp A\nAT226\nXAT226\nPipe Slide High\nAT227\nXAT227\nPipe Slide High\nAT228\nXAT228\nPipe Slide Low\nAT229\nXAT229\nPipe Slide Low 4-Sided\nAT230\nXAT230\nPipe Slide Low 4-Sided\nAT231\nXAT231\nPipe Slide Extra High\nAT232\nXAT232\nPipe Slide Extra High\nAT233\nXAT233\nPipe Slide High\nAT234\nXAT234\nPipe Slide Extra High\nAT235\nXAT235\nPipe Slide Low 2-Sided\nAT236\nXAT236\nPipe Slide Low 3-Sided\nAT237\nXAT237\nPipe Slide Low 4-Sided\nAT238\nXAT238\nPipe Slide High 2-Sided\nAT239\nXAT239\nPipe Slide High 3-Sided\nAT240\nXAT240\nPipe Slide High 4-Sided\nAT241\nXAT241\nPipe Slide High 2-Sided\nAT242\nXAT242\nPipe Slide High 3-Sided\nAT243\nXAT243\nPipe Slide High 4-Sided\nAT244\nXAT244\nPipe Slide High 2-Sided\nAT245\nXAT245\nPipe Slide High 3-Sided\nAT246\nXAT246\nPipe Slide High 4-Sided\nAT247\nXAT247\nPipe Slide Extra High 2-Sided\nAT248\nXAT248\nPipe Slide Extra High 3-Sided\nAT249\nXAT249\nPipe Slide Extra High 4-Sided\nAT250\nXAT250\nPipe Slide Extra High 2-Sided\nAT251\nXAT251\nPipe Slide Extra High 3-Sided\nAT252\nXAT252\nPipe Slide Extra High 4-Sided\nAT253\nXAT253\nPipe Slide Extra High 2-sided\nAT254\nXAT254\nPipe Slide Extra High 3-sided\nAT255\nXAT255\nPipe Slide Extra High 4-sided\nAT256\nXAT256\nPipe Slide\nAT257\nXAT257\nPipe Slide\nAT258\nXAT258\nPipe Slide\nAT259\nXAT259\nPipe Slide\n\n\n\n\nModify User Defined Ancillary Geometry\nModify User Defined Ancillary Geometry"}
{"Headers": "The standards are available in the Supports application BRAN.", "Content": "The standards are available in the Supports application.\nBR01\nXBR01\n2 Way Brace for Open Ended Connection to Pipe.\nBR02\nXBR02\n2 Way Brace for Open Ended Connection to Flange.\nBR03\nXBR03\n2 Way Bracing for Orifice Connections.\nBR04\nXBR04\n4 Way Brace for Open Ended Connection to Pipe.\nBR05\nXBR05\n3 Way Brace for Open Ended Connection to Flange.\nBR06\nXBR06\n4 Way Brace for Open Ended Connection to Flange.\nBR07\nXBR07\n2 Way Brace for Open Ended Connection to Pipe.\nBR08\nXBR08\n2 Way Brace for Open Ended Connection to Flange.\nBR09\nXBR09\n2 Way Brace for Open Ended Connection to Flange.\n\n\n\n"}
{"Headers": "The standards are available in the Supports application. Refer to Modify User Defined Ancillary Geometry for further information on user defined U-bolt standards.", "Content": "The standards are available in the Supports application. Refer to Modify User Defined Ancillary Geometry for further information on user defined U-bolt standards.\nBT01A\nXBT01\nU Bolt gripped (type A)\nBT01B\nXBT01\nU Bolt non-gripped (type B)\nBT02\nXBT02\nU Bolt tico coated\nBT03\nXBT03\nU Bolt PTFE coated insulation\nBT04A\nXBT04\nU Bolt Guide (GB) Black, NPS 1/2 - 36.\nBT04B\nXBT04\nU Bolt Guide (GG) Galvanized, NPS 1/2 - 36.\nBT04C\nXBT04\nU Bolt Guide (GP) Plastic Coated, NPS 1/2 - 36.\nBT05\nXBT05\nU Bolt gripped with sleeve, NPS 2 - 24.\nBT06\nXBT06\nU Bolt Guide for Cupro Nickel Lines, NPS 1/2 - 8.\nBT07\nXBT07\nU Bolt Guide for Carbon Steel Lines, NPS 1/2 - 8.\nBT09\nXBT09\nLined U-Bolt guided 2\" TO 8\"\nBT10\nXBT10\nU Bolt Guide, NPS 1/2 - 36\"\nBT11\nXBT11\nLoose Type U Bolt Guide, NPS 1/2 - 36\"\nBT12\nXBT12\nU Bolt for steel pipe, NPS 1/2 - 3\"\nBT13\nXBT13\nU Bolt for steel pipe, NPS 4 - 32\"\nBT14\nXBT14\nExpansion U Bolt for steel pipe, NPS 1 - 32\"\nBT15\nXBT15\nLined U Bolt NPS 1 1/4 - 2\"\nBT16\nXBT16\nLined U Bolt NPS 2 1/2 - 36\"\nBT17\nXBT17\nU Bolt for use with slip pad NPS 1/2 - 32\"\nBT18\nXBT18\nU Bolt with Teflon Pad NPS 2 1/2 - 32\"\nBT19\nXBT19\nExpansion U Bolt with Slip Pad NPS 1 - 32\"\nBT21\nXBT21-\nU Bolt Guide for CS & LTCS Lines - 1/2\" to 6\"\nBT22\nXBT22-\nU Bolt Grip for CS & LTCS Lines - 1/2\" to 6\"\nBT23\nXBT23-\nU Bolt Guide for Galv,S/S,6Mo & Duplex lines - 1/2\" to 6\"\nBT24\nXBT24-\nU Bolt Grip for Galv,S/S,6Mo & Duplex lines - 1/2\" to 6\"\n\n\n\n\nModify User Defined Ancillary Geometry\nModify User Defined Ancillary Geometry"}
{"Headers": "The standards are available in the Supports application for Rack.", "Content": "The standards are available in the Supports application.\nRACK-REST\nXCA01\nRack Rest\nCA02A\nXCA02\nCable Clip with Angles\nCA02B\nXCA02\nCable Clip\n\n\n\n"}
{"Headers": "CT01XCT01", "Content": "The standards are available in the Supports application.\nCT01\nXCT01\n'L' Bracket up.\nCT02\nXCT02\n'L' Bracket down.\nCT03\nXCT03\n'L' Bracket Cantilever.\nCT04\nXCT04\nGoal post.\nCT05\nXCT05\nSupport frame.\nCT06\nXCT06\nCantilever bracket.\nCT07\nXCT07\n'T' Post. (Vertical down).\nCT08\nXCT08\n'T' Post. (Vertical up).\n\n\n\n"}
{"Headers": "The standards are available in the Supports application FB01XFB01.", "Content": "The standards are available in the Supports application.\nFB01\nXFB01\nFrame Bracing.\nFB02\nXFB02\nFrame Bracing.\n\n\n\n"}
{"Headers": "The standards are available in the Supports application DT01A1XSU01TICO.", "Content": "The standards are available in the Supports application.\nDT01\nXDT01\nHVAC duct support frame.\nDT02\nXDT02\nHVAC duct support frame.\nDT03\nXDT03\nHVAC duct cantilever bracket.\nDT04\nXDT04\nHVAC duct 'L' bracket.\n\n\n\n"}
{"Headers": "The standards are available in the Supports application SU01A1XSU01Tico.", "Content": "The standards are available in the Supports application.\nSU01A1\nXSU01\nTICO bondslip unit type A size 1.\nSU01A2\nXSU01\nTICO bondslip unit type A size 2.\nSU01A3\nXSU01\nTICO bondslip unit type A size 3.\nSU01A4\nXSU01\nTICO bondslip unit type A size 4.\nSU01B1\nXSU01\nTICO bondslip unit type B size 1.\nSU01B2\nXSU01\nTICO bondslip unit type B size 2.\nSU01B3\nXSU01\nTICO bondslip unit type B size 3.\nSU01B4\nXSU01\nTICO bondslip unit type B size 4.\nSU01C1\nXSU01\nTICO bondslip unit type C size 1.\nSU01C2\nXSU01\nTICO bondslip unit type C size 2.\nSU01C3\nXSU01\nTICO bondslip unit type C size 3.\nSU01C4\nXSU01\nTICO bondslip unit type C size 4.\nSU02A1\nXSU02\nPTFE. slide unit type A size 1.\nSU02A2\nXSU02\nPTFE. slide unit type A size 2.\nSU02A3\nXSU02\nPTFE. slide unit type A size 3.\nSU02A4\nXSU02\nPTFE. slide unit type A size 4.\nSU02B1\nXSU02\nPTFE. slide unit type B size 1.\nSU02B2\nXSU02\nPTFE. slide unit type B size 2.\nSU02B3\nXSU02\nPTFE. slide unit type B size 3.\nSU02B4\nXSU02\nPTFE. slide unit type B size 4.\nSU02C1\nXSU02\nPTFE. slide unit type C size 1.\nSU02C2\nXSU02\nPTFE. slide unit type C size 2.\nSU02C3\nXSU02\nPTFE. slide unit type C size 3.\nSU02C4\nXSU02\nPTFE. slide unit type C size 4.\nSU03\nXSU03\nShoe Supports, Teflon Slide Plate (Upper Element) NPS 3-36.\nSU04\nXSU04\nShoe Supports, Teflon Slide Plate NPS 2-36.\n\n\n\n"}
{"Headers": "The standards are available in the Supports application.", "Content": "The standards are available in the Supports application.\nThe standards marked with a * are not available in the Supports application. These standards are obsolete and have been replaced by other new standards.\nTT01*\nXTT01\nTrunnions for straight piping.\nTT02*\nXTT02\nTrunnions for pipe elbows.\nTT03*\nXTT03\nTrunnions for CuNi straight piping.\nTT04\nXTT04\nBase ELL and Pipe Support NPS 2-36\nTT05\nXTT05\nBase ELL and Pipe Support NPS 2-36 with Bearing Plate\nTT06\nXTT06\nBase ELL and Pipe Support Variable NPS 2-36\nTT07\nXTT07\nBase ELL and Pipe Support Variable NPS 2-36 with Bearing Plate\nTT08\nXTT08\nBase ELL and Pipe Support for RTJ Spools NPS 2-36\nTT09\nXTT09\nBase ELL and Pipe Support for RTJ Spools NPS 2-36 with Bearing Plate\nTT10\nXTT10\nBase Support for RTR Pipe NPS 2-14\nTT11\nXTT11\nBase Support for RTR Pipe NPS 2-14 with Bearing Plate\nTT12\nXTT12\nBase Support Bolt On NPS 2-36\nTT13\nXTT13\nBase Support Bolt On with Bearing Plate NPS 2-36\nTT14\nXTT14\nType A Dummy Extension for Horizontal Pipe NPS 2-36\nTT15\nXTT15\nType B Dummy Extension for Horizontal Pipe NPS 2-36\nTT16\nXTT16\nType C Dummy Extension for Horizontal Pipe NPS 2-36\nTT17\nXTT17\nDummy Extension for Vertical Pipe NPS 2-36\nTT18\nXTT18\nBase Support Adjustable Base NPS 2-24\nTT19\nXTT19\nBase Support Adjustable Base with Bearing Plate NPS 2-8\nTT20\nXTT20\nSupport for Relief Valve Discharge Pipe NPS 2-12\nTT21\nXTT21\nRod Hanger Welded Elbow Trunnion NPS 12-24\nTT22\nXTT22\nBase Support Anchor for RTR Pipe NPS 2-14\nTT23\nXTT23\nTrunnion with an Integral Cold Isolation Block for C.S./Alloy Pipes NPS 1.1/2-20\nTT24\nXTT24\nTrunnion Clamp for Vertical Pipe NPS 2-24\nTT25\nXTT25\n90 Degree Cranked Vertical Dummy Leg for 2\" - 24\"\nTT26\nXTT26\nVertical Dummy Leg for 2\" - 24\"\nTT27\nXTT27\nTrunnion With Integral Guide for 2\" - 24\"\nTT28\nXTT28\nBase Support Anchor for RTR Pipe NPS 2-14 with Bearing Plate\nTT29\nXTT29\nGRE Pipes Vertical Dummy Leg for diam 2\" - 24\"\nTT30\nXTT30\nCPVC Pipes Vertical Dummy Leg for diam 2\" - 24\"\nTT31\nXTT31\nGRE Pipes Trunnion for 2\" - 24\"\nTT32\nXTT32\nCPVC Pipes Trunnion for 2\" - 24\"\nTT33\nXTT33\nGRE Pipes Stanchion for 2\" - 24\"\nTT34\nXTT34\nCPVC Pipes Stanchion for 2\" - 24\"\nTT35\nXTT35\nVertical Dummy Leg for diam 2\" - 24\"\nTT36\nXTT36\nTrunnion NB 1.1/2\" - 30\"\nTT37\nXTT37\nAdjustable Trunnion NB 2\" - 12\"\nTT38\nXTT38\nBase Support Welded to pipe 2\" TO 24\"\nTT39\nXTT39\nBase Support Welded to elbow 2\" TO 24\"\nTT40\nXTT40\nTrunnion for uninsulated lines - NPS 20-250\nTT41\nXTT41\nTrunnion for uninsulated lines - NPS 20-250\nTT42\nXTT42-\nTrunnion for Elbow - 1\" to 36\"\nTT43\nXTT43-\nTrunnion for Straight Pipe - 1\" to 36\"\nTT44\nXTT44-\nTrunnion with Repad for Straight Pipe - 1\" to 36\"\n\n\n\n"}
{"Headers": "The standards are available in the Supports application VT01XVT01.", "Content": "The standards are available in the Supports application.\nVT01\nXVT01\nSupport from vessel for 2\" to 10\" N.B. Pipe.\nVT02\nXVT02\nSupport from vessel for 12\" to 20\" N.B. Pipe.\nVT03\nXVT03\nGuide from vessel for 8\" to 20\" N.B. Insulated Pipe.\nVT04\nXVT04\nGuide from vessel for 8\" to 24\" N.B. Pipe.\nVT05\nXVT05\nSupport from vessel for 2\" to 6\" N.B. Pipe.\nVT06\nXVT06\nGuide from vessel for 2\" to 4\" N.B. Pipe.\nVT07\nXVT07\nSupport Bracket Uninsulated Pipe NPS 2 - 10\nVT08\nXVT08\nSupport Bracket Insulated/Uninsulated Pipe NPS 6 - 18\nVT09\nXVT09\nSupport Bracket Uninsulated Pipe NPS 8 - 18\nVT10\nXVT10\nSupport Bracket Uninsulated Pipe NPS 2 - 24\nVT11\nXVT11\nSupport Bracket Uninsulated Pipe NPS 2 - 4\nVT12\nXVT12\nSupport Bracket Guide for Uninsulated Pipe NPS 16 - 24\nVT13\nXVT13\nSupport Bracket Guide for Uninsulated CS Pipe NPS 10 - 14\nVT14\nXVT14\nSupport Bracket Guide for Uninsulated CS Pipe NPS 6 - 8\nVT15\nXVT15\nSupport Bracket Guide for Uninsulated CS Pipe NPS\n1/2 - 4\nVT16\nXVT16\nSpecial Guide for Vertical Pipe in the Splash Zone NPS 3 - 12\nVT17\nXVT17\nSupport Bracket Uninsulated/Insulated Pipe NPS 1/2 - 3\nVT18\nXVT18\nSupport Bracket Insulated Pipe NPS 3 - 14\nVT19\nXVT19\nSupport Bracket Guide for insulated Pipe NPS 16 - 24\nVT20\nXVT20\nCantilever support from vertical & horizontal vessel for 2\" to 10\" N.B. Pipe.\nVT21\nXVT21\nBraced cantilever support from vertical & horizontal vessel for 2\" to 10\" N.B. Pipe.\nVT22\nXVT22\nCantilever support from vertical vessel for vertical pipes with lugs LT13 or LT15 2.1/2\" to 20\" N.B. Pipe.\nVT23\nXVT23\nCantilever support from vertical vessel for vertical pipes with Trunnions 2.1/2\" to 14\" N.B. Pipe.\nVT24\nXVT24\nCantilever braced support from vertical vessel for vertical pipes with Trunnions 2.1/2\" to 14\" N.B. Pipe.\n\n\n\n"}
{"Headers": "Catalogues", "Content": "You must use the following conventions for structural catalogues so that the Model applications can recognize them and so that the Paragon applications can use them:\nThe diagrams in the following subsection illustrate the structure of the catalogues.\nThe PURPose of the CATAlogue must be set to one of the following: STL, FITT, JOIN or PFIT. This makes sure that any specifications and applications which are built can recognized the correct catalogue element. Thus the steel Profile specification looks for the purpose STL, the Joint specification looks for the purpose JOIN, the Fitting specification looks for the purpose FITT and the Panel Fitting specification looks for the purpose PFIT. A meaningful DESCription is also beneficial.\nThe PURPose of the STSEction must be set to REF for Reference Data, PRFL for Profiles, FITT for Fittings, JOIN for Joints and PFIT for Panel Fittings.\nThe PURPose of the STCAtegory must be set to REF for Reference Data, PRFL for Profiles, FITT for Fittings, JOIN for Joints and PFIT for Panel Fittings.\nThe GTYPE of the Profile, Fitting, Joint or Panel Fitting must be set. This makes sure that specific restrictions can be applied to Joints and Fittings when building the specifications. For example: any Section with a GTYPE set to BEAM can be used with a Joint which has its GTYPE set to BEAM; any Fitting with a GTYPE set to FITT can be used with any Fitting specification.\nThe purpose of a CSTANdard is to let you define in a text string the type of standard that is being used. It is used purely for information and administration of the Catalogue. For example, the CSTANdard for British Sections is BS 5950.\nThe PURPose of the CATAlogue must be set to one of the following: STL, FITT, JOIN or PFIT. This makes sure that any specifications and applications which are built can recognized the correct catalogue element. Thus the steel Profile specification looks for the purpose STL, the Joint specification looks for the purpose JOIN, the Fitting specification looks for the purpose FITT and the Panel Fitting specification looks for the purpose PFIT. A meaningful DESCription is also beneficial.\nThe PURPose of the CATAlogue must be set to one of the following: STL, FITT, JOIN or PFIT. This makes sure that any specifications and applications which are built can recognized the correct catalogue element. Thus the steel Profile specification looks for the purpose STL, the Joint specification looks for the purpose JOIN, the Fitting specification looks for the purpose FITT and the Panel Fitting specification looks for the purpose PFIT. A meaningful DESCription is also beneficial.\nThe PURPose of the STSEction must be set to REF for Reference Data, PRFL for Profiles, FITT for Fittings, JOIN for Joints and PFIT for Panel Fittings.\nThe PURPose of the STSEction must be set to REF for Reference Data, PRFL for Profiles, FITT for Fittings, JOIN for Joints and PFIT for Panel Fittings.\nThe PURPose of the STCAtegory must be set to REF for Reference Data, PRFL for Profiles, FITT for Fittings, JOIN for Joints and PFIT for Panel Fittings.\nThe PURPose of the STCAtegory must be set to REF for Reference Data, PRFL for Profiles, FITT for Fittings, JOIN for Joints and PFIT for Panel Fittings.\nThe GTYPE of the Profile, Fitting, Joint or Panel Fitting must be set. This makes sure that specific restrictions can be applied to Joints and Fittings when building the specifications. For example: any Section with a GTYPE set to BEAM can be used with a Joint which has its GTYPE set to BEAM; any Fitting with a GTYPE set to FITT can be used with any Fitting specification.\nThe GTYPE of the Profile, Fitting, Joint or Panel Fitting must be set. This makes sure that specific restrictions can be applied to Joints and Fittings when building the specifications. For example: any Section with a GTYPE set to BEAM can be used with a Joint which has its GTYPE set to BEAM; any Fitting with a GTYPE set to FITT can be used with any Fitting specification.\nThe purpose of a CSTANdard is to let you define in a text string the type of standard that is being used. It is used purely for information and administration of the Catalogue. For example, the CSTANdard for British Sections is BS 5950.\nThe purpose of a CSTANdard is to let you define in a text string the type of standard that is being used. It is used purely for information and administration of the Catalogue. For example, the CSTANdard for British Sections is BS 5950.\n\n\n"}
{"Headers": "Piping catalogue", "Content": "As with the piping catalogue, there are many ways in which you can structure your steelwork catalogues. The same two ways of structuring both types of catalogue are preferred, the difference being the types of administrative elements used. However, whereas for piping there is only one type of catalogue (namely for piping components), the following three types of catalogue are used for steelwork:\nThe basic layout of the catalogues is the same as for piping, for example, where the reference data is stored, but the way in which the data is separated differs.\n\nPROFILES\nJOINTS\nFITTINGS (FITT and PFIT)\nPROFILES\nPROFILES\nJOINTS\nJOINTS\nFITTINGS (FITT and PFIT)\nFITTINGS (FITT and PFIT)\n\n\n\nThe basic layout of the catalogues is the same as for piping, for example, where the reference data is stored, but the way in which the data is separated differs."}
{"Headers": "Purpose Catalogue", "Content": "Purpose\nPurpose should be the same as the SPEC with which the catalogue is to be used (STL, FITT, JOIN, PFIT etc.)\nCstandard\nCatalogue standard\nSTSEction \u2011 Structural Section\nDescription\nDescription of Section\nGtype-\nGeneric type of element contained in section; this should be the same as the type of element used in MODEL, e.g.BEAM\nDescription\nDescription of Section\nGtype-\nGeneric type of element contained in section; this should be the same as the type of element used in MODEL, e.g.BEAM\nPurpose\nPurpose should equate to the STYP of the items as defined in the Spec\nFunction\nDescription\nGtype\nIdentifies the Generic element type\nSkey\nnot applicable\nPtref\nPoint set reference\nGmref\nGeometry set reference\nNgmref\nNegative geometry reference\nDataSetRef\nData set reference\nPstreference\nPline set reference\nGstreference\nProfile set reference\nCDetail\nDetail reference\nOwnconn\nOwning connection profile type\nAttconn\nAttached connection profile type\nCPlot\nPlot file for reference used in documentation\nIcon\nIcon name\nCstandard\nStandard\u00b7\nPTSE \u2011 Point Sets\nDescription\nDescription of point set\nGtype\nIdentifies the Generic element type\nSkey\nSymbol Key to which point set relates\nPurpose\nPurpose of point set\nDescription\nDescription of point set\nGtype\nIdentifies the Generic element type\nSkey\nSymbol Key to which point set relates\nPurpose\nPurpose of point set\nGtype\nIdentifies the Generic element type\nPurpose\nPurpose of geometry set\nNGMS \u2011 Negative Geometry Sets\nDescription\nDescription of geometry set\nGtype\nIdentifies the Generic element type\nPurpose\nPurpose of geometry set\nDescription\nDescription of geometry set\nGtype\nIdentifies the Generic element type\nPurpose\nPurpose of geometry set\nDTSE - Datasets\nDescription\nDescription of dataset\nGtype\nIdentifies the Generic element type\nPurpose\nPurpose of dataset\nDescription\nDescription of dataset\nGtype\nIdentifies the Generic element type\nPurpose\nPurpose of dataset\nGtype\nIdentifies the Generic element type\nPurpose\nPurpose of point set\nGtype\nIdentifies the Generic element type\nPurpose\nPurpose of geometry structural set\n\n\n\n"}
{"Headers": "Datasets", "Content": "The general purpose of Datasets is twofold:\nRefer to Catalogues and Specifications Reference Manual Section 3 for further information.\nTo let you query catalogue parameters.\nTo let you input design parameters via simple forms and menus.\nTo let you query catalogue parameters.\nTo let you query catalogue parameters.\nTo let you input design parameters via simple forms and menus.\nTo let you input design parameters via simple forms and menus.\n\n\n\nSection 3"}
{"Headers": "the profile catalogue", "Content": "The Profile catalogue should be structured so that the separation of the data is sensible, for example, all sections of the same generic profile should be under the structural section. The segregation beneath the section should be used to associate groups within the generic type; for example, in the case of British Standards, each category should contain sections with the same serial size, whereas in DIN standards the same class should be used (IPE, IPB, etc.). In most instances there will only be one profile set and one geometry set for each generic type of profile.\n\n\n\n"}
{"Headers": "the fittings catalogue", "Content": "The Fittings catalogue should be structured so that all fittings of a given generic type are stored beneath the same section, for example, lifting lugs, stiffeners, etc. Within each section the fittings should be broken down into groups relating to the profile on which the fitting can be used, for example, I, H, L, COLU, BEAM.\nThe Panel Fitting catalogue should follow the same format as the Fitting catalogue except that the panel fitting element is called a PFIT.\n\n\n\n\nexcept\nPFIT"}
{"Headers": "the joints catalogue", "Content": "The Joints catalogue should be structured so that all joints of a given generic type are stored beneath the same section, for example, cleats, endplates, baseplates. Within each section the joints should be broken down into categories relating to the types of sections to which the joint can be connected, for example, I\u2011I, I\u2011Chan, I\u2011L. The generic types of the sections should be stored against Ownconn and Attconn attributes.\n\n\n\n\n\n\n\n\n\n"}
{"Headers": "Specifications", "Content": "The following conventions for structural specifications must be followed to make sure that a correct specification is built. The application follows strict rules when building these specifications and reads the specification in a tabulated format. Description should be given at the correct level and any question of Tanswers must be input for the forms and menus to be correctly built. The steelwork specifications work in a different way to piping specifications, where there can be more than one answer. For example, a typical connection for two beams can either be a bolted or welded connection; hence there can be two answers to one question.\n\n\n"}
{"Headers": "panel thickness", "Content": "Panel thickness availability in the Model module can be controlled via the catalogue Specification mechanism. Using \u2018Ans\u2019 \u2018Maxans\u2019 attributes on the SPCO can limit the allowable minimum and maximum panel thicknesses.\n\nType\nAttribute\nData\nDescription\nSPEC\nDescription\n{ str }\ndisplay on form spec gadget\nQuestion\nTHK\nquestion for offspring\nPurpose\nPLT\nspec purpose\nTquestions\nthickness\nspecific question for offspring\nSPCO\nAns\nreal\nmin thickness\nMaxans\nreal\nmax thickness\nSPEC\nDescription\n{ str }\ndisplay on form spec gadget\nQuestion\nTHK\nquestion for offspring\nPurpose\nPLT\nspec purpose\nTquestions\nthickness\nspecific question for offspring\nSPCO\nAns\nreal\nmin thickness\nMaxans\nreal\nmax thickness\n\n\nNote:\nThe CATREF is not used as the geometry is defined in the Model module.\n\n\n\nNote\n:\nSPEC\nstr\nSPCO"}
{"Headers": "attributes for specification elements in hierachical order pupose FITT", "Content": "\nAttributes for Specification elements in hierarchical order:\nSPEC\nDescription\n{ str }\ndisplay on form spec gadget\nPurpose\nFITT\nspec purpose\nQuestion\nTYPE\nquestion for offspring\nMatref\n{ ref }\nmaterial reference in Property DB\nSELE\nDescription\n{ str }\ninformation on type of profile\nTanswer\n{ word }\ngeneric type of profile that can own the fitting. ANY will allow a fitting to be used on any profile type.\nQuestions\nSTYP\nquestion for offspring\nSELE\nDescription\n{ str }\ndisplay on form stype gadget\nTanswer\n{ word }\nsub-type of fitting, for example, LUG, HOLE.\nSPCO\nCatref\n{ ref }\npointer to HFIT in catalogue\nDetref\n{ ref }\npointer to detail text\n\n\n\n\nstr\nref\nstr\nword\nstr\nword\nref\nref"}
{"Headers": "attributes for specification elements in hierachical order pupose PFIT", "Content": "\nAttributes for Specification elements in hierarchical order:\nSPEC\nDescription\n{ str }\ndisplay on form spec gadget\nPurpose\nPFIT\nspec purpose\nQuestion\nTYPE\nquestion for offspring\nMatref\n{ ref }\nmaterial reference in Property DB\nSELE\nDescription\n{ str }\ndisplay generic type on form\nQuestion\nSTYP\nquestion for offspring\nTanswer\n{ word }\ngeneric type of fitting\nSELE\nDescription\n{ str }\ndisplay on form stype gadget\nTanswer\n{ word }\nsub-type of fitting, for example, Door, Window.\nSPCO\nCatref\n{ ref }\npointer to PFIT in catalogue\nDetref\n{ ref }\npointer to detail text\n\n\n\n\nSPEC\nstr\nref\nSELE\nSELE\nstr\nword\nSPCO\nref\nref"}
{"Headers": "attributes for specification elements in hierachical order pupose Join", "Content": "\nAttributes for Specification elements in hierarchical order:\nSPEC\nDescription\n{ str }\ndisplay on form spec gadget\n\nPurpose\nJOIN\nspec purpose\n\nQuestion\nOTYP\nquestion for offspring\n\nMatref\n{ ref }\nmaterial reference in Property DB\nSELE\nDescription\n{ str }\ndisplay on form stype gadget\n\nTanswer\n{ word }\ngeneric type of profile which joints can be owned by. ANY will allow joints to be owned by any profile, NONE will allow setting of PJOI specrefs.\n\nQuestion\nATYP\nquestion for offspring\nSELE\nDescription\n{ str }\ninformation on type of profile\nTanswer\n{ word }\ngeneric type of profile that can be attached to joint. ANY will allow any type of profile to be attached to the joint.\nQuestion\nSTYP\nquestion for offspring\nSPCO\nCatref\n{ ref }\npointer to PFIT in catalogue\nDetref\n{ ref }\npointer to detail text\nSELE\nDescription\n{ str }\ninformation on type of profile\n\nTanswer\n{ word }\ngeneric type of profile that can be attached to joint. ANY will allow any type of profile to be attached to the joint.\n\nQuestion\nSTYP\nquestion for offspring\nSPCO\nCatref\n{ ref }\npointer to PFIT in catalogue\n\nDetref\n{ ref }\npointer to detail text\n\n\n\n\nSPEC\nstr\nref\nSELE\nstr\nword\nSELE\nSPCO"}
{"Headers": "Materials in Model", "Content": "For the materials of a structural element (MATR) to be set in Model, you must be able to see a Properties Database (DB) containing the available materials.\nTo create a Material World, carry out the following steps:\nIf new material densities are required to be added to the system, DENSITY.DAT can be modified to include your new materials. The format of the file is as follows:\nAL-CAST\n\\Aluminium, cast\n\\2560\nAl-WROUGHT\n\\Aluminium, wrought\n\\2700\nDURALUMIN\n\\Aluminium, Duralumin\n\\2790\nThe hash character ( # ) signifies a comment line: any line beginning with it will be ignored.\nTo load the new/modified materials into the system, follow step 4 above. If you moved the file to some other directory, run the macro by passing the full pathname of the file, thus:\nNote:\nAll densities are in kg/cu m.\n\n\n\nedit module PARAGON mode PROP rw\n$m/%PMLUI%/DES/DATA/MLOADPROP\nNote\n:\n$m/%PMLUI%/DES/DATA/MLOADPROP\npathname"}
{"Headers": "the ,Net customization", "Content": "The .NET Customization User Guide gives software engineers, with experience of software development in C# using Visual Studio, guidance on the development of .NET customization for AVEVA products. The AVEVA .NET Customization User Guide is not intended to be used as an introduction to C#.\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"Headers": "The introduction of a customization", "Content": "The introduction of a customization capability using Microsoft .NET technology has opened up a whole new world of customization and is particularly relevant for the integration of AVEVA products with other customer systems. .NET API's provide access to various aspects of the product including Graphical User Interface, Database and Geometry.\nAs part of AVEVA's strategy of 'continual progression' the .NET customization capability has been introduced in such a way that it can be used alongside the existing PML based customization. Through the use of PML.NET, an enhancement to PML which allows the PML programmer to call .NET code, customization which utilizes the strengths of .NET compiled code and PML can be achieved.\n\nThe above diagram illustrates the two new methods of customization using .NET technology. The first is via the concept of a .NET Addin and the second using PML.NET. Both methods provide a mechanism whereby a .NET assembly (dll) can be dynamically loaded into a module at runtime.\n\n\n"}
{"Headers": "Common Application Framework Interfaces", "Content": "The Common Application Framework (CAF) is an extensible framework which provides the .NET programmer with access to various services which support both application development and customization. The foundations of the CAF are provided by the two interface assemblies:\nThese interfaces provide the following major services:\nSimple customization can be achieved by creating User Defined Attributes in Lexicon, delivering them in C# and loading them using the Aveva.ApplicationFramework.dll. Refer to for further information.\nIt may be desirable to introduce extra GUI tools with complex customizations, this can be achieved using the Aveva.ApplicationFramework.Presentation.dll.\nThe Application Framework Interfaces are documented at https://help.aveva.com/API/CAF/index.html.\nAveva.ApplicationFramework.dll\nAveva.ApplicationFramework.Presentation.dll\nAveva.ApplicationFramework.dll\nAveva.ApplicationFramework.dll\nAveva.ApplicationFramework.Presentation.dll\nAveva.ApplicationFramework.Presentation.dll\nAddinManager:\nThis class provides properties and methods for the management of ApplicationFramework Addins.\nServiceManager:\nThis class defines an interface which provides a means by which the various components of the ApplicationFramework can publish their services. The ServiceManager also acts as a service provider responding to requests for services. It can also be used by applications and application addins to publish additional services.\nSettingsManager:\nThis class provides properties and methods for the management of application settings which are stored in settings groups which are persisted between sessions.\nAddinManager:\nThis class provides properties and methods for the management of ApplicationFramework Addins.\nAddinManager:\nThis class provides properties and methods for the management of ApplicationFramework Addins.\nServiceManager:\nThis class defines an interface which provides a means by which the various components of the ApplicationFramework can publish their services. The ServiceManager also acts as a service provider responding to requests for services. It can also be used by applications and application addins to publish additional services.\nServiceManager:\nThis class defines an interface which provides a means by which the various components of the ApplicationFramework can publish their services. The ServiceManager also acts as a service provider responding to requests for services. It can also be used by applications and application addins to publish additional services.\nSettingsManager:\nThis class provides properties and methods for the management of application settings which are stored in settings groups which are persisted between sessions.\nSettingsManager:\nThis class provides properties and methods for the management of application settings which are stored in settings groups which are persisted between sessions.\nCommandBarManager:\nThis provides access to the ribbon menus and commandbars of a CAF based application. It also has methods to load the definition of menus and commandbars from User Interface customization (UIC) files.\nCommandManager:\nThis class defines an interface to provide the presentation framework client with a mechanism for the management of command objects which can be associated with Tools or other User interface objects. The action of invoking a tool, for example: clicking a ButtonTool, will cause the execution of the associated command object. It is possible to associate the same command object with a number of different user interface objects, for example: ButtonTool on a Menu and a LinkLabel, thereby allowing for the centralization of these user interface object actions within a command. Various state-like properties of a command, for example: enabled/checked, would also be reflected in all user interface objects associated with a command; disabling a command would cause all associated user interface objects to be disabled. User interface objects are associated with a command via a CommandExecutor derived class.\nResourceManager:\nThis class defines an interface to provide Addins with a simplified mechanism to access localizable resources. The ResourceManager provides a number of methods which allows an addin to then access the various types of resources (string, image, cursor, icon etc.) which resource files may contain.\nWindowManager:\nThis provides access to the main application window, the StatusBar and a collection of MDI and docked windows. It also provides the addin writer with methods to create MDI and docked windows to host user controls.\nCommandBarManager:\nThis provides access to the ribbon menus and commandbars of a CAF based application. It also has methods to load the definition of menus and commandbars from User Interface customization (UIC) files.\nCommandBarManager:\nThis provides access to the ribbon menus and commandbars of a CAF based application. It also has methods to load the definition of menus and commandbars from User Interface customization (UIC) files.\nCommandManager:\nThis class defines an interface to provide the presentation framework client with a mechanism for the management of command objects which can be associated with Tools or other User interface objects. The action of invoking a tool, for example: clicking a ButtonTool, will cause the execution of the associated command object. It is possible to associate the same command object with a number of different user interface objects, for example: ButtonTool on a Menu and a LinkLabel, thereby allowing for the centralization of these user interface object actions within a command. Various state-like properties of a command, for example: enabled/checked, would also be reflected in all user interface objects associated with a command; disabling a command would cause all associated user interface objects to be disabled. User interface objects are associated with a command via a CommandExecutor derived class.\nCommandManager:\nThis class defines an interface to provide the presentation framework client with a mechanism for the management of command objects which can be associated with Tools or other User interface objects. The action of invoking a tool, for example: clicking a ButtonTool, will cause the execution of the associated command object. It is possible to associate the same command object with a number of different user interface objects, for example: ButtonTool on a Menu and a LinkLabel, thereby allowing for the centralization of these user interface object actions within a command. Various state-like properties of a command, for example: enabled/checked, would also be reflected in all user interface objects associated with a command; disabling a command would cause all associated user interface objects to be disabled. User interface objects are associated with a command via a CommandExecutor derived class.\nResourceManager:\nThis class defines an interface to provide Addins with a simplified mechanism to access localizable resources. The ResourceManager provides a number of methods which allows an addin to then access the various types of resources (string, image, cursor, icon etc.) which resource files may contain.\nResourceManager:\nThis class defines an interface to provide Addins with a simplified mechanism to access localizable resources. The ResourceManager provides a number of methods which allows an addin to then access the various types of resources (string, image, cursor, icon etc.) which resource files may contain.\nWindowManager:\nThis provides access to the main application window, the StatusBar and a collection of MDI and docked windows. It also provides the addin writer with methods to create MDI and docked windows to host user controls.\nWindowManager:\nThis provides access to the main application window, the StatusBar and a collection of MDI and docked windows. It also provides the addin writer with methods to create MDI and docked windows to host user controls.\n\n\n\nhttps://help.aveva.com/API/CAF/index.html\n\nAddinManager\nServiceManager\nSettingsManager\nCommandBarManager\nCommandManager\nResourceManager\nWindowManager\nhttps://help.aveva.com/API/CAF/index.html"}
{"Headers": "Database Interfaces", "Content": "The database related interfaces are provided by the interface assemblies:\nInterfaces are available to allow customizations to query or write to the program database. Refer to Database Interface for further information.\nAveva.Core.Database.dll & Aveva.Core.Database.Filters.dll\nAveva.Core.Database.dll & Aveva.Core.Database.Filters.dll\nAveva.Core.Database.dll & Aveva.Core.Database.Filters.dll\n\n\n\nDatabase Interface\nDatabase Interface"}
{"Headers": "Geometry Interfaces", "Content": "The geometry related interfaces are provided by the interface assembly:\nThis interface has a number of geometry related classes. For example, position, orientation, direction, arc, line and plane.\nAveva.Core.Geometry.dll\nAveva.Core.Geometry.dll\nAveva.Core.Geometry.dll\n\n\n"}
{"Headers": "Maths Interfaces", "Content": "The maths related interfaces are provided by the interface assembly:\nThis interface has a number of two dimensional and three dimensional low level geometry related classes.\nAveva.Core.Maths.Geometry.dll\nAveva.Core.Maths.Geometry.dll\nAveva.Core.Maths.Geometry.dll\n\n\n"}
{"Headers": "Shared Interfaces", "Content": "Some general shared interfaces are provided in the interface assembly:\nThis provides current element, selection changed events and Datal listing facilities. You can use Visual Studio to find the classes and methods.\nAveva.Core.Shared.dll\nAveva.Core.Shared.dll\nAveva.Core.Shared.dll\n\n\n"}
{"Headers": "Utilities Interfaces", "Content": "Utility interfaces are provided in the interface assembly:\nThis provides messaging, string utilities, tracing, undo and units. It also provides access to the command line but this is not supported\nAveva.Core.Utilities.dll\nAveva.Core.Utilities.dll\nAveva.Core.Utilities.dll\n\n\n"}
{"Headers": "Graphics Interfaces", "Content": "Interfaces to access the drawlist and colours are provided in the interface assembly:\nThe rest of this user guide will cover in detail how to write a .NET addin and an assembly containing classes with methods which are callable from Programmable Macro Language (PML). It will describe the use of the various .NET interfaces via the use of sample code.\nAveva.Core3D.Graphics.dll\nAveva.Core3D.Graphics.dll\nAveva.Core3D.Graphics.dll\n\n\n"}
{"Headers": "Engineering Interfaces", "Content": "Interfaces to access Engineer API through the Programmable Macro Language (PML) are provided in the interface assembly:\nThis provides functionality to manage lists from macros, add and remove rows from grids, set colours and export to xlsx. All methods are PML callable and can be used with PML or C# (.NET) code.\nAveva.Engineering.Tags.Pml.dll\nAveva.Engineering.Tags.Pml.dll\nAveva.Engineering.Tags.Pml.dll\n\n\n"}
{"Headers": "Zip file sample,zip sample using core/core3D", "Content": "A zip file (Samples.zip) containing a number of samples using the Core/Core3D interfaces can be found in the installation directory. Each sample directory contains a number of C# source files and a Visual Studio project. Before opening and building a project in Visual Studio, set the environment variable %AVEVA_DESIGN_EXE% to include the product installation directory (this will make sure that all the project's assembly references are correct) and set %CAF_ADDINS_PATH% to include the directory where you want to build the sample (this will make sure that the project builds the example here). When running the product you also need to make sure that %CAF_ADDINS_PATH% is set to the same build directory to make sure that the example addin is loaded from here.\n\n\n"}
{"Headers": "AttributeBrowserAddin", "Content": "This is a C# addin containing a simple form which displays the attributes for the currently selected element. To use this within a module, copy the module's addins.xml file, for example, DesignAddins.xml, from the product directory to the directory set in CAF_ADDINS_PATH and then modify it to include AttributeBrowserAddin. To access the addin you will need to add the command to a State button on the ribbon or toolbar depending on the User Interface (UI) in the module. To do this in the application, open up the customization window and either create a new tab group/toolbar or use an existing one. Create a new State Button and in its properties specify the command to be \"Aveva.ShowAttributeBrowserCommand\", then click Apply and close the window. You should be able to open the attribute browser button by clicking on the new button.\n\n\n\nApply"}
{"Headers": "ExamplesAddin", "Content": "This is a C# addin containing a number of code examples that can be run via a command. The command Aveva.Example.Command, is loaded when the addin is started. To add the addin to a module, copy the modules Addins.xml, for example, DesignAddins.xml from the product directory to the directory set in CAF_ADDINS_PATH. Edit this file adding the ExampleAddin to it (There is an example addins file in the ExamplesAddin directory). The command can be run from a ComboBox tool added to the ribbon or toolbar depending on the User Interface (UI) in the module. To do this in the application, create a new Tab group/toolbar using the Customization utility, add a ComboBox tool to it and attach the command to that. Each example can then be run by selecting it in the ComboBox. Since these examples create and claim Model elements they need to be run in a Design multi-write database.\n\n\n"}
{"Headers": "FlexibleExplorerAddin", "Content": "This is a C# addin which contains a Flexible Explorer control on a window and can be used with any of the modules. You will need to build the Addin inside Visual Studio after updating the references and then copy the DLL (FlexibleExplorerAddin.dll) and the associated XML sample file (FlexibleExplorerSample.xml) to the executable directory.\nIn order to load the addin into the modules you will need to add a reference in the DesignAddins.XML file.\nFinally, you will need to use the Customization tool to add a state button in the module in order to display the addin.\nWith the sample Flexible Explorer definition file (FlexibleExplorerSample.xml) the addin will display all the elements in the model.\nDetailed information about the Flexible Explorer is available, refer to Use of Flexible Explorer Control for further information.\n\n\n\nUse of Flexible Explorer Control\nUse of Flexible Explorer Control"}
{"Headers": "NetGridExample", "Content": "Installation for this example is exactly the same as with previous examples (refer to AttributeBrowserAddin or ExamplesAddin for further information). After following these instructions, enter the module you want to use and, once loaded, bring up the customization window. This example differs to the Attributes browser as it doesn't create a command, so in order to load the grid you need to create a state button as before, but the command is done differently. Open the command dialog by clicking on the \"\u2026\" button to the right of the field. For the type, select Command Class and for the class select DockedWindowStateCommand, finally click OK. Next click on the \"\u2026\" button in the Arguments field and select the Void .ctor(System.String) constructor. For the window key, enter Grid Control Addin and then click OK to close the dialog.\nOnce this has been done, close the customization window and click on the new state button. The grid control window should appear just like any other form.\n\n\n\nAttributeBrowserAddin\nExamplesAddin\nAttributeBrowserAddin\nExamplesAddin\nCommand Class\nDockedWindowStateCommand\nOK\nVoid .ctor(System.String)\nGrid Control Addin\nOK"}
{"Headers": "PMLNetExample", "Content": "This example provides a simple C# class which can be called from within the Programmable Macro Language (PML).\n\n\n"}
{"Headers": "PMLGridExample", "Content": "An example of an AVEVA Grid Control hosted on a Programmable Macro Language (PML) form can be found in the Samples.zip file.\n\n\n"}
{"Headers": "Tracing and Optimization", "Content": "Suggestions to minimize the speed of start-up of addins have been made above. There are 2 built-in ways to monitor this and investigate the reasons if poor performance is suspected.\nTarget start-up time for an Addin should be no more than 1 second, if possible. To find out how long your Addin takes to start-up set the following environment variable:\nOutput similar to the following will then be displayed in the Console Window:\nThe standard facilities found in the classes of the Aveva.Core.Utilities.Tracing namespace can be used for tracing performance problems as well as for other general coding investigations.\nThe PdmsTrace class gives access to all the facilities of the Plant Design Management System (PDMS) trace system and provides a means of outputting general trace messages and values during processing. PdmsTrace functions also enable querying and setting of PDMS trace flags; give access to the current state of the call stack; and allow starting and stopping of Central Processor Unit (CPU) time tracing.\nThe TraceEntry class provides the means to trace the entry and exit of functions as processing takes place. As the nesting of function calls gets deeper and deeper the function entry messages are indented further and further. Though this output can quickly get verbose it can frequently give evidence of problems in the code - for example functions being called too frequently \u2026 or not at all!\nTo work correctly in C#, TraceEntry needs to know about entry and exit from functions in correct chronological order. There is a difficulty with this in C# because of the way that \"garbage collection\" works in that language. This means, in particular, it is necessary to make sure that the function exit event occurs at the right moment. This can be achieved by using the Dispose method explicitly:\nThere are still problems with this however as you will need to catch every \"return\" statement individually. Also the Dispose() method will never be called if an exception occurs. A simpler and more robust way is to do this job using the C# \"using\" command as follows:\nIf you are using these facilities to investigate the start-up of an addin, you will need to set the chosen trace flag from your code:\nAnd, finally, you can use the CPU time profiling options in conjunction with TraceEntry by using:\nReviewing Addin Start-up Time\nset AVEVA_CAF_TRACING=PERFORMANCE\nAVEVA Everything3D Design Mk2.1.0[10061]  (WINDOWS-NT 6.3)\nCopyright 2012 to current year.  AVEVA Solutions Limited and its subsidiaries. All\n      rights reserved.\n   \nIssued to UKCAMSPLS\nLoading addins took: 0.282 secs.\nStarting addin Explorer: 0.984 secs.\nStarting addin DrawList: 0.024 secs.\nStarting addin Collections: 1.264 secs.\nStarting addin History: 0.011 secs.\nStarting addin ReferenceList: 0.170 secs.\nStarting addin PipeCheck: 0.447 secs.\nStarting addin Find: 0.117 secs.\nStarting addin Links Addin: 0.042 secs.\nStarting addin Attributes: 0.706 secs.\nStarting addin Status Controller: 0.016 secs.\nStarting addin ModelChanges: 0.047 secs.\nStarting addin SVGCompare: 0.612 secs.\nStarting addin Aveva.Core.InstrumentationImport.Addin.DataUpdate: 0.114 secs.\nStarting addin Aveva.Core.AVEVANetExportConfigAddin: 0.237 secs.\nStarting addin Aveva.Core.ReportingAddin: 0.327 secs.\nStarting addin MessageAddin: 0.240 secs.\nStarting addin Integrator: 0.533 secs.\nTotal time starting addins: 5.905 secs.\nLoading UIC file\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\MyDataAddin.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\StatusController.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\design.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\CoreSchematicMenu.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\SVGCompare.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\AVEVA.design.cabling.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\AVEVA.design.hvac.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\AVEVA.design.MDS.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\AVEVA.design.piping.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1.customisation\\AVEVA.design.steelwork.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\MessageWindowCoreMenus.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\AVEVA.design.laser.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\Integrator.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\DiagramViewer.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1\\InstrumentationImportAddin.uic\nDefined new tools\nLoading UIC file C:\\AVEVA\\Plant\\E3D2.1.customisation\\Model.Addin.uic\nDefined new tools\nUpdating CommandBar Layout: 0.002 secs.\nLoading CommandBar layout: 0.172 secs.\nDockManager.LoadFromXML: 2.628 secs.\nLoading Window Layout: 3.227 secs.\nTraceEntry tr = TraceEntry.Enter(\"Start\", (TraceNumber)101);\n   \n// ...\n// code being traced ...\n// ...\ntr.Dispose();   // explicit call on exit\nusing (TraceEntry tr = TraceEntry.Enter(\"Start\", (TraceNumber)101))\n   \n{\n     // ...\n     // code being traced ...\n     // ...\n}    // implicit call to Dispose() on exit from the block\n     // even if there are exceptions or multiple return statements\nPdmsTrace.SetTraceFlag((TraceNumber)101, 1);\n   \nPdmsTrace.StartCPUTrace();\n   \n// ...\n// code being timed ...\n// ...\nPdmsTrace.StopCPUTrace(true);\n\n\n\nPdmsTrace\nTraceEntry\nexit\nTraceEntry\nTraceEntry\n(\n\"Start\"\n(\nTraceNumber\n)\n// ...\n// code being traced ...\n// ...\n// explicit call on exit\nusing \n(\nTraceEntry\nTraceEntry\n\"Start\"\n, (\nTraceNumber\n)\n     \n// ...\n     // code being traced ...\n     // ...\n// implicit call to Dispose() on exit from the block\n     // even if there are exceptions or multiple return statements\nPdmsTrace\n((\nTraceNumber\n)\nPdmsTrace\n// ...\n// code being timed ...\n// ...\nPdmsTrace\n(\ntrue\n);"}
{"Headers": "Exception Handling in a Common Application Framework Addin", "Content": "The code of all components of a Common Application Framework (CAF) Addin is executed within the event loop of the host AVEVA program. Any exception raised within the Addin code, or any code called by it, that is not caught by the addin code itself will have to be handled in the event loop. The AVEVA host has effective ways to handle some classes of exceptions - namely PdmsExceptions and PMLNetExceptions. In the situation where the host program is in the process of executing Programmable Macro Language (PML), then the PML first has an opportunity to handle the exception itself. If the PML does not handle the exception, or if no PML is currently being executed, the host program handles these exceptions by notifying the user of the exception text and number interactively via the Status Bar, MessageBoxes or the CommandLine display as appropriate. Event loop processing then continues normally.\nFor all other classes of exception the host event loop has no standard procedure and the outcome is that the host program terminates untidily. It is therefore very poor programming style to allow general exceptions to escape from the Addin. A relatively easy way to prevent this is to trap exceptions systematically at every entry point between the host event loop and the component interfaces - for example in every Command.Execute function:\nThis recommendation does not, of course, replace the routine practice of handling exceptions at the appropriate points within the Addin code when they are anticipated and can be dealt with effectively. It simply provides a safety net for unanticipated and otherwise unhandled exceptions.\n/// <summary>\n/// Execute\n/// </summary>\npublic override void Execute()\n   \n{\n     try\n     {\n   \n          // Do the required function.\n             DoTheJob();\n     }\n     catch (System.Exception ex)\n   \n     {\n   \n          // Pass on PdmsExceptions and PMLNetExceptions.\n          // Handle all others:\n          //   (perhaps by raising a PdmsException).\n     }\n   \n}\n\nprivate void DoTheJob()\n{\n     // Do the required function...\n}\n\n\n\n/// <summary>\n/// Execute\n/// </summary>\npublic override void\n \n{\n     \ntry\n     \n     \ncatch \nException\n     \n          \n// Pass on PdmsExceptions and PMLNetExceptions.\n          // Handle all others:\n          //   (perhaps by raising a PdmsException).\n     \nprivate void\n DoTheJob()\n   \n  // Do the required function..."}
{"Headers": "Thread safety in a Common Application Framework Addin", "Content": "C# allows code to use multiple threads and there are situations where this can be useful in an Addin. However this technique should be used with care as the host AVEVA program is not itself multiple thread safe. Thus there can be only one thread at a time which executes functions in DbLayer, Common Application Framework (CAF) or other host core code.\n\n\n"}
{"Headers": "Addins In TTY", "Content": "TeleTypewriter (TTY) addins that implement the IAddinTty interface can also be defined in the <module>Addins.xml and will be loaded when the application starts. In graphics only those addins which implement the IAddin interface will be loaded and started as before. Addins can implement both interfaces but may need refactoring so that no User Interface (UI) elements are started in TTY mode. User Defined Attributes (UDAs) implemented as pseudo attributes can now be implemented in this way; refer to example implementation of IAddinTty interface below.\nusing System;\n   \nusing System.IO;\n   \nusing System.Windows.Forms;\n   \nusing Aveva.ApplicationFramework;\n   \nusing Aveva.ApplicationFramework.Presentation;\n   \nusing Aveva.Core.Database;\n   \nusing Ps = Aveva.Core.Database.DbPseudoAttribute;\n   \nusing NOUN = Aveva.Core.Database.DbElementTypeInstance;\n   \n\nnamespace Aveva.Core.Tests.AddinTty\n   \n\n    /// <summary>\n    /// Summary description for AddinTtyTest\n    /// </summary>\n    public class AddinTty : IAddinTty, IAddin\n   \n    {\n        /// <summary>\n        /// Start the Addin\n        /// </summary>\n        /// <param name=\"serviceManager\"></param>\n        void IAddinTty.Start(ServiceManager serviceManager)\n   \n        {\n            // get uda attribute\n            DbAttribute uda = DbAttribute.GetDbAttribute(\":UDADDIN\");\n   \n\n            if (uda != null)\n            {\n   \n                // Create instance of delegate containing method to evaluate\n                // pseudo attribute\n                Ps.GetStringDelegate dele =\n   \nnew Ps.GetStringDelegate(AddinTtyValue);\n   \n                // and pass delegate instance to core.\n                Ps.AddGetStringAttribute(uda, NOUN.EQUIPMENT, dele);\n   \n            }\n        }\n\n        void IAddinTty.Stop()\n   \n        {\n   \n        }\n\n        String IAddinTty.Name\n   \n        {\n   \n            get { return \"AddinTty\"; }\n        }\n   \n\n        get { return \"AddinTty\"; }IAddinTty.Description\n   \n        {\n   \n           get { return \"AddinTty\"; }\n   \n        }\n   \n\n        // String delegate for UDA\n        static private string AddinTtyValue(DbElement ele, DbAttribute att, DbQualifier qualifier)\n   \n        {\n   \n            return \"AddinTty\";\n   \n        }\n    }\n}\n\n\n\nusing\nusing\nusing\nusing\nusing\nusing\nusing\nusing\nnamespace\n    \n/// <summary>\n    \n/// Summary description for AddinTtyTest\n    /// </summary>\n    \npublic class\n    {\n        \n/// <summary>\n        \n/// Start the Addin\n        \n/// </summary>\n        \n/// <param name=\"serviceManager\"></param>\n        \nvoid\n            \n// get uda attribute\n           \n           \nnull\n)\n           \n                \n// Create instance of delegate containing method to evaluate\n                // pseudo attribute\n              \nnew\n              \n  // and pass delegate instance to core.\n              \n        \nvoid\n        \n        \nString\n       \n            \nget \n{ \nreturn\n \n\"AddinTty\"\n; }\n       \n        \nget \n{ \nreturn\n \n\"AddinTty\"\n       \n           \nget \n{ \nreturn\n \n\"AddinTty\"\n       \n        \n// String delegate for UDA\n        \nstatic private string\n \n       \n            \nreturn\n \n\"AddinTty\""}
{"Headers": "functionality provided via an addin", "Content": "User access to functionality provided via an addin is normally provided through the use of ribbon menus and tools on a commandbar. Reference was made earlier, in the User Guide about addin commands, that the Common Application Framework (CAF) provides a mechanism to allow the use of ribbon menus and commandbars for an application to be defined in a User Interface Customization (UIC) file. This section provides details of how a CAF based application can be configured to load a UIC file, and how the UIC file can be edited using the applications interactive user interface customization tool. Newer modules, for example Model and Draw use the Ribbon commandbar, this is configured in the same way as the original toolbar (detailed below).\n\n\n"}
{"Headers": "Configuring a Module to Load a User Interface Customization File", "Content": "Each Common Application Framework (CAF) based application has an Extensible Markup Language (XML) configuration file which contains a list of User Interface Customization (UIC) files that the application should load at start-up. The default location for this file is in the same directory as the application executable. It has a filename of the form <Module Name>Customisation.xml. By default the UIC files are also expected to be in the same directory as the application executable. You can however specify the full path to the UIC file including the use of UNC pathnames. It is also possible to define a project specific UIC file. The string \"$1\" in the UIC path will be replaced with the current project name.\nIf during addin development you do not wish to modify the customization configuration file in the install directory (this is particularly likely to be the case if you are using a server based installation) then the default location of the customization configuration file can be overridden using the environment variable CAF_UIC_PATH. You can then edit a copy of the file and point this environment variable at the directory you copy it to.\nThe order of the UIC files in this configuration file is significant. They are loaded in order since it is possible for a UIC file to define a tool which is hosted in a menu or on a commandbar defined in a UIC file already loaded.\nA new UIC file can be added to a module simply by adding a new line to the corresponding customization configuration file. The actual content of the UIC file will be created using the interactive user interface customization tool described below.\nAs well as adding to the customization configuration file, an addin can also load a UIC file directly using the AddUICustomisationFile method of the CommandBarManager.\nThis UIC file will be loaded before those define in the Customization configuration file, so it must create its own menu or commandbar to host its tools.\n<?xml version=\"1.0\" encoding=\"utf-8\" ?>\n <UICustomizationSet xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">\n <DefaultIcon>AvevaSharedIcons:ID_WARNING</DefaultIcon>\n <UICustomizationFiles>\n <CustomizationFile Name=\"Module\" Path=\"design.uic\" />\n <CustomizationFile Name=\"SchematicExplorerAddin\" Path=\"CoreSchematicMenu.uic\" />\n <CustomizationFile Name=\"Project\" Path=\"$1.uic\" Optional=\"true\" />\n <CustomizationFile Name=\"SVGCompare\" Path=\"SVGCompare.uic\" />\n <CustomizationFile Name=\"Cabling\" Path=\"AVEVA.design.cabling.uic\" />\n <CustomizationFile Name=\"Hvac\" Path=\"AVEVA.design.hvac.uic\" />\n <CustomizationFile Name=\"Supports\" Path=\"AVEVA.design.MDS.uic\" />\n <CustomizationFile Name=\"Piping\" Path=\"AVEVA.design.piping.uic\" />\n <CustomizationFile Name=\"Steelwork\" Path=\"AVEVA.design.steelwork.uic\" />\n <CustomizationFile Name=\"MessageAddin\" Path=\"MessageWindowCoreMenus.uic\" />\n <CustomizationFile Name=\"Laser\" Path=\"AVEVA.design.laser.uic\" />\n <CustomizationFile Name=\"Integrator\" Path=\"Integrator.uic\" />\n <CustomizationFile Name=\"DiagramViewer\" Path=\"DiagramViewer.uic\" />\n <CustomizationFile Name=\"InstrumentationImportAddin\" Path=\"InstrumentationImportAddin.uic\"\n      />\n   \n </UICustomizationFiles>\n </UICustomizationSet>\n// Load a UIC file for the AttributeBrowser.\nICommandBarManager commandBarManager = dependencyResolver.GetImple\\-mentationOf<ICommandBarManager>();\ncommandBarManager.AddUICustomisationFile(\"AttributeBrowser.uic\", \"AttributeBrowser\");\n   \n\n\n\n// Load a UIC file for the AttributeBrowser.\n\"AttributeBrowser.uic\"\n\"AttributeBrowser\""}
{"Headers": "Environment Variables for .NET Customization", "Content": "There are 4 environment variables, with significant values, available for use with the .NET Customization capability.\nAVEVA_DESIGN_EXE\nshould be set to the product installation directory.\nCAF_ADDINS_PATH\nindicates the location of the AddIns.\nCAF_UIC_PATH\nindicates the location of files where the GUI is defined.\nAVEVA_CAF_TRACING\ncan be set to obtain information while developing.\nAVEVA_DESIGN_EXE\nshould be set to the product installation directory.\nCAF_ADDINS_PATH\nindicates the location of the AddIns.\nCAF_UIC_PATH\nindicates the location of files where the GUI is defined.\nAVEVA_CAF_TRACING\ncan be set to obtain information while developing.\nIf this environment variable is unset, the program behaves as if it has been set to the product installation directory. The value can be multiple paths, separated by ';' and the application will search all of them in sequence for AddIns.\nThe application will search for <module_name>Addins.xml in the directories until it finds a matching file. Once a <module_name>Addins.xml file is found, the application searches the directories for files with the same name. The list of addins is read from these xml files, duplicate entries within the matching files are disregarded.\nWhen customizing, users will probably want to have the product installation directory in the path list to locate standard AVEVA AddIns delivered with the product.\nThe CAF_UIC_PATH implicitly appends the installation folder.\nIf this environment variable is unset, the program behaves as if it has been set to the product installation directory. The value can be multiple paths, separated by ';' .\nThe application will search for <module_name>Customisation.xml in the directories until it finds a matching file. Once a <module_name>Customization.xml file is found, the application searches the directories for files with the same name. The list of customization files is read from these xml files, duplicate entries within the matching files are disregarded.\nEach <\u2026>Customization.xml file contains a list of .uic files. The path for which may be a filename, when the uic file is in the same directory, or a full pathname to the where the uic file exists.\nFiles can use the notation '$1.uic'. The application will substitute the current Project Code (E.G. APS) for $1 on start up. An error will be raised if the file is not found unless the Optional=\"true\" has been specified.\nFor example:\nOn start-up, the application will look for the uic files specified. An error will be raised if one is not found unless the optional=\u2019true\u2019 has been specified.\nThe uic files are processed in order. UI containers must have been defined before UI components are added to them.\nIn addition to using the CAF_UIC_PATH to look for <\u2026>Customization.xml files, the application will also use it to locate resource files.\n  <UICustomizationFiles>\n    <CustomizationFile Name=\"Module\" Path=\"admin.uic\" />\n    <CustomizationFile Name=\"Project\" Path=\"$1.uic\" Optional=\"true\"/>\n    <CustomizationFile Name=\"MessageAddin\" Path=\"MessageAddinMenu.uic\" />\n  </UICustomizationFiles>\n</UICustomizationSet>\n\n\n"}
{"Headers": "Edit an UIC File", "Content": "The content of a User Interface Customization (UIC) file is created using the CAF based applications\u2019 built-in interactive user interface customization tool available from the Customize window. Click to display the Customize window.\n\nThe customization system supports the concept of multiple configuration files. Any number of levels of customization file can be defined either using the module customization configuration file or the CommandBarManager. AddUICustomizationFile() method, and they are layered on-top of each other in the order they appear in the list.\n\nSelecting an entry in the list will update the customize explorer will show command tools with all configuration information defined in the selected file and those above it. Any items in the customize explorer or list of command tools view which are not defined in the currently active customization file are displayed with an italic font in grey.\nAny customization file which a user does not have write access to does not appear in the drop-down list, but its contents are included in the customize explorer and list of command tools view.\nThe selected customization file will become the active customization file. It will only be possible to edit customization information defined in this file.\nThe Customize Explorer is populated with a representation of the active customization. It shows CommandBars and their contents, Menubars and their entries, Context Menus and their entries and Ribbons and their contents defined in all of the configuration files above and including the currently selected file. It also contains a list of the currently loaded resource files.\nWhen a node in the customize explorer is selected, the property grid is updated with the corresponding object so that its properties can be edited. Only objects which are defined in the currently Active Customization File can have their properties modified.\nSelecting a node in the customize explorer which represents an object defined in a non-active file will update the property grid, but it will be disabled, preventing modification.\nIf the selected node represents a resource file, the Resource Editor will be displayed instead of the property grid.\nThe tools owned by a MenuTool or Ribbon can be re-ordered by dragging the tool to the new desired position.\nThe list of command tools is populated with each of the tools defined in each of the configuration files above and including the currently selected file.\nUse the functionality available to:\nThe property grid is updated with the corresponding tool object so that its properties can be edited. Only objects which are defined in the currently active customization file can have their properties modified. Selecting a tool which is defined in a non-active file updates the property grid, but it will be disabled thus preventing modification.\nTools can be dragged from the list of command tools and dropped into a MenuTool or Ribbon in the customization explorer. It is also possible to add tools to a menu or ribbon defined in a higher level customization file.\nThe functionality can be used to integrate new tools into an existing system defined menu hierarchy and extend system toolbars as well as creating new top level menus and new tabs.\nOne possible risk of adding tools to menus or ribbons defined at a higher level is that the higher level structure might at a later date be modified making these tools \u2018orphaned\u2019, or making the data which is stored to indicate their position within the host invalid. To warn of this, these tools are displayed in red within the customization explorer.\nUse the right-click menu available from the List of Command Tools pane of the Customize window to delete, create a tool or get an image from the clipboard.\n\nDelete\nDeletes the currently selected tool, if the selected tool is not editable then the delete operation is disabled. If the tool has been used then a warning message is displayed to confirm that the delete should be carried out.\n\nNew\nUses the displayed menu to create a new menu tool, create a new tool of the required type with a unique default name (Tool<N>) and add it to the list. New tools can also be created using the icons on the left side of the command tool pane.\n\nThe properties for the new menu tool are displayed in the properties grid and can be edited.\n\nUse the functionality available from the property grid to edit the various properties of the tools. The customize explorer or the list of tools is kept up to date with any property changes.\n\nThe following properties can be set for all Tools:\nThe following properties are available on some Command Tools:\nIf required, the command property can be modified, click . . . in the Command field to display the Command window. By default the command type is set to Command, other command types available for selection are Macro and Command Class, refer to Macro and Command Class for further information.\n\nHere a list of the currently loaded CAF Command objects is displayed for selection.\nThe macro functionality uses a special command class to invoke the entered single PML command. This enables the PML developer to use the interactive customization tool to create their own menus and commandbars without needing to write C# command classes.\n\nUse the functionality available from the Command window, to select a command class from populated list:\n\nThe ribbon section of the explorer enables the creation of tools; application menus, contextual tab groups and tabs, the creation, modification, deletion or group order is identical to that previously described. Refer to Edit an UIC File for further information.\n\nUse of the resource editor enables each of the currently loaded resource sets to be edited. It supports String, Icon and Bitmap resources. Each resource set can comprise a number of resource files, with an Invariant Language resource file and any number of locale specific resource files. When a resource file is selected, the Resource Editor is activated.\n\nWhen active, the resource editor command bar contains the following operations:\n\nSave\nSaves the resource file to the default location.\nCopy Resources\nCopies a resource file to the clipboard.\nPaste Resources\nPastes a resource file into another resource file.\nDelete\nDeletes a resource file.\nAdd New Resource File\nAdds a new resource file. The resource file name must be typed in the text box adjacent to the icon.\n\nSave\nSaves the resource file to the default location.\n\nCopy Resources\nCopies a resource file to the clipboard.\n\nPaste Resources\nPastes a resource file into another resource file.\n\nDelete\nDeletes a resource file.\n\nAdd New Resource File\nAdds a new resource file. The resource file name must be typed in the text box adjacent to the icon.\nNew resource files (icon or bitmaps) can be added using drag-and-drop from a windows explorer. The resource id is generated from the filename, capitalized and prefixed with \"ID_\". If there is a clash with an existing resource, a confirmation window is displayed prompting for confirmation of file replacement.\nUse the property grid to add new string resource(s), double click in the available blank entry in the grid. Once created a new blank row is automatically added to the grid.\n\nUse the Edit Formatted Text window to edit existing resource(s), right click the required string resource in the property grid, from the displayed menu select Formatted Text Editor.\n\nUse the localisable resources functionality to customize a locale specific resource file or add a new locale specific resource file to the resource file set (this can then be selected for editing). Refer to Resource Manager for further information.\n\nUse the standard functionality available for selection from the View Style menu to change how information is displayed in the resource file editor.\n\nThe icon and bitmap tabs also have a popup menu which provides access to these functions as well as a rename function. Double clicking on a resource also enters the rename mode.\n\nProperties of tools which are strings or the icon property can use resources for their value. Reference to a resource is made using the form <ResourceSet Name>:<Resource Id> as shown below:\n\nThe caption and icon properties can be set on a tool in the tool list by drag-and-drop from the resource editor onto the tool.\nThere is a standalone version of the resource editor available to enable resource files to be created and edited. This program is called \"ResourceEditor.exe\" and can be found in the installation directory.\nWhen started it displays a file selection window which enables the choice of an existing resource file or the addition a new resource file.\nSelect a Node in the List\nDrag & Drop from the List to the Customization Explorer\nList Context Menu.\nSelect a Node in the List\nSelect a Node in the List\nDrag & Drop from the List to the Customization Explorer\nDrag & Drop from the List to the Customization Explorer\nList Context Menu.\nList Context Menu.\nApplicationContext\nCurrently unused\nArguments\nList of arguments supplied to the Command\nCaption\nText to display on CommandBar\nCommand\nCommand to run (see below)\nDisplayStyle\nDetermines how the tool is displayed on the CommandBar\nDefault- The tool is displayed in a default style.\nDefaultForToolType - The tool is displayed based on the default for the tools type and its location.\nTextOnlyAlways - The tool is always displayed as text only.\nTextOnlyInMenus - The Tool is displayed as a graphic when located on a Toolbar, and displayed as text when located on a Menu.\nImageAndText - The tool is displayed using its assigned image and text. This setting is ignored when the item is on a top-level menu.\nImageOnlyOnToolbars - The Tool is displayed as a graphic when located on a Toolbar, and displayed as image and text when located on a Menu.\nIcon\nIcon to display on CommandBar\nKeyTip\nTip is shown on the ribbon when the Alt key is pressed, aids quick navigation\nName\nUnique name for this tool\nShortcut\nShortcut key to activate this tool\nTooltip\nPlain tool-tip text to display on mouse-over\nTooltipFormattedText\nFormatted tool-tip text to display on mouse-over\nTooltipTitle\nTitle for tool-tip\nApplicationContext\nCurrently unused\nApplicationContext\nArguments\nList of arguments supplied to the Command\nArguments\nCaption\nText to display on CommandBar\nCaption\nCommand\nCommand to run (see below)\nCommand\nDisplayStyle\nDetermines how the tool is displayed on the CommandBar\nDefault- The tool is displayed in a default style.\nDefaultForToolType - The tool is displayed based on the default for the tools type and its location.\nTextOnlyAlways - The tool is always displayed as text only.\nTextOnlyInMenus - The Tool is displayed as a graphic when located on a Toolbar, and displayed as text when located on a Menu.\nImageAndText - The tool is displayed using its assigned image and text. This setting is ignored when the item is on a top-level menu.\nImageOnlyOnToolbars - The Tool is displayed as a graphic when located on a Toolbar, and displayed as image and text when located on a Menu.\nDisplayStyle\nIcon\nIcon to display on CommandBar\nIcon\nKeyTip\nTip is shown on the ribbon when the Alt key is pressed, aids quick navigation\nKeyTip\nName\nUnique name for this tool\nName\nShortcut\nShortcut key to activate this tool\nShortcut\nTooltip\nPlain tool-tip text to display on mouse-over\nTooltip\nTooltipFormattedText\nFormatted tool-tip text to display on mouse-over\nTooltipFormattedText\nTooltipTitle\nTitle for tool-tip\nTooltipTitle\nAutoComplete\nSets whether the edit portion is automatically updated to match an item in the list as new characters are typed.\nControl\nControl embedded in container\nEditable\nSets if the text is editable by the user\nMaxLength\nMaximum number of characters the user is allowed to enter\nPassword\nDisplay text in password mode (hidden)\nValueList\nList of values to display\nWidth\nTool width on the CommandBar\nAutoComplete\nSets whether the edit portion is automatically updated to match an item in the list as new characters are typed.\nAutoComplete\nControl\nControl embedded in container\nControl\nEditable\nSets if the text is editable by the user\nEditable\nMaxLength\nMaximum number of characters the user is allowed to enter\nMaxLength\nPassword\nDisplay text in password mode (hidden)\nPassword\nValueList\nList of values to display\nValueList\nWidth\nTool width on the CommandBar\nWidth\nDockedWindowStateCommand\nModuleSwitchCommand\nSelectTaskPaneCommand\nCommandBarStateCommand.\nDockedWindowStateCommand\nDockedWindowStateCommand\nModuleSwitchCommand\nModuleSwitchCommand\nSelectTaskPaneCommand\nSelectTaskPaneCommand\nCommandBarStateCommand.\nCommandBarStateCommand.\nNote:\nOnly ribbons and their contents (tabs, groups and menus) are described.\nNote:\nFunctionality is available for icons and bitmaps only.\nNote:\nThe functionality available from the formatted text editor is standard.\n\n\n\nEdit an UIC File\nResource Manager\nCustomize\nCustomize\nCommandBarManager. AddUICustomizationFile()\nCustomize Explorer\nActive Customization File\nResource Editor\nNote\n:\nList of Command Tools\nCustomize\nDelete\nNew\n. . .\nCommand\nCommand\nCommand\nMacro\nCommand Class\nCommand\nEdit an UIC File\nInvariant Language\nResource Editor\nSave\nCopy Resources\nPaste Resources\nDelete\nAdd New Resource File\nNote\n:\nEdit Formatted Text\nFormatted Text Editor\nNote\n:\nResource Manager\nView Style\nresource file editor"}
{"Headers": "database related interfaces", "Content": "The database related interfaces are provided by the interface assemblies:\nThis interface has the following main classes:\nNamespace: Aveva.Core.Database\nThe class is valid for system types and User Defined Element Types (UDETs).\nAs well as the class methods there is a lot of functionality that can be accessed via pseudo attributes. The relevant pseudo attributes are listed where relevant.\nThe classes fall into the following groups:\nAveva.Core.Database.dll & Aveva.Core.Database.Filters.dll\nAveva.Core.Database.dll & Aveva.Core.Database.Filters.dll\nAveva.Core.Database.dll & Aveva.Core.Database.Filters.dll\nDatabaseService:\nThe sole purpose of this class is to open a project.\nDbAttribute:\nThe class has two purposes:\nInstances of the class are used to identify and pass around attributes\nThe methods allow the retrieval of metadata about an attribute, for example: type, size, Name, pseudo or not, etc. The class is valid for system attributes and User Defined Attributes (UDAs).\nDB:\nThis class provides information on the opened Data Bases (DBs).\nDbElement:\nInstances of DbElement are used to identify an element. This is the main class for reading and writing to the database. The methods cover\nelement creation\nelement deletion\ncopy\ngetting/setting attributes and rules\nnavigating the DB\nevaluating database expressions.\nDbElementType:\nThe class has two purposes:\nInstances of the class are used to identify and pass around Element types\nThe methods allow the retrieval of metadata about an Element type, for example: Name, description, allowed attributes and members etc.\nDatabaseService:\nThe sole purpose of this class is to open a project.\nDatabaseService:\nThe sole purpose of this class is to open a project.\nDbAttribute:\nThe class has two purposes:\nInstances of the class are used to identify and pass around attributes\nThe methods allow the retrieval of metadata about an attribute, for example: type, size, Name, pseudo or not, etc. The class is valid for system attributes and User Defined Attributes (UDAs).\nDbAttribute:\nThe class has two purposes:\nDB:\nThis class provides information on the opened Data Bases (DBs).\nDB:\nThis class provides information on the opened Data Bases (DBs).\nDbElement:\nInstances of DbElement are used to identify an element. This is the main class for reading and writing to the database. The methods cover\nelement creation\nelement deletion\ncopy\ngetting/setting attributes and rules\nnavigating the DB\nevaluating database expressions.\nDbElement:\nInstances of DbElement are used to identify an element. This is the main class for reading and writing to the database. The methods cover\nDbElementType:\nThe class has two purposes:\nInstances of the class are used to identify and pass around Element types\nThe methods allow the retrieval of metadata about an Element type, for example: Name, description, allowed attributes and members etc.\nDbElementType:\nThe class has two purposes:\nDbEvents:\nThis class contains the mechanisms for subscribing to database events. It covers savework, getwork, undo, redo, flush, refresh, drop events plus capturing general database changes.\nDbExpression:\nClass to hold a database expression. These are the same as Programmable Macro Language (PML) 1 expressions. Methods to evaluate expressions are on the DbElement class.\nDbPseudoAttribute:\nThis Class allows pseudo attribute code to be plugged in for UDAs.\nDbRule:\nClass to hold a database rule\nDbUserChanges: This is passed through by the 'database change' event. It contains a list of database changes made since the last 'database change' event was raised. Changes may be queried down to the attribute level.\nMDB:\nMethods to do operations on an Multiple DataBase (MDB), for example: savework, getwork.\nTable:\nVarious classes to access the internal Dabacon tables, for example: the name table.\nProject:\nThe main method is to open the MDB.\nDbEvents:\nThis class contains the mechanisms for subscribing to database events. It covers savework, getwork, undo, redo, flush, refresh, drop events plus capturing general database changes.\nDbEvents:\nThis class contains the mechanisms for subscribing to database events. It covers savework, getwork, undo, redo, flush, refresh, drop events plus capturing general database changes.\nDbExpression:\nClass to hold a database expression. These are the same as Programmable Macro Language (PML) 1 expressions. Methods to evaluate expressions are on the DbElement class.\nDbExpression:\nClass to hold a database expression. These are the same as Programmable Macro Language (PML) 1 expressions. Methods to evaluate expressions are on the DbElement class.\nDbPseudoAttribute:\nThis Class allows pseudo attribute code to be plugged in for UDAs.\nDbPseudoAttribute:\nThis Class allows pseudo attribute code to be plugged in for UDAs.\nDbRule:\nClass to hold a database rule\nDbRule:\nClass to hold a database rule\nDbUserChanges: This is passed through by the 'database change' event. It contains a list of database changes made since the last 'database change' event was raised. Changes may be queried down to the attribute level.\nDbUserChanges: This is passed through by the 'database change' event. It contains a list of database changes made since the last 'database change' event was raised. Changes may be queried down to the attribute level.\nMDB:\nMethods to do operations on an Multiple DataBase (MDB), for example: savework, getwork.\nMDB:\nMethods to do operations on an Multiple DataBase (MDB), for example: savework, getwork.\nTable:\nVarious classes to access the internal Dabacon tables, for example: the name table.\nTable:\nVarious classes to access the internal Dabacon tables, for example: the name table.\nProject:\nThe main method is to open the MDB.\nProject:\nThe main method is to open the MDB.\nData Model Definition Classes\nBasic database access, query and modification.\nFilters\nIterators\nDabacon Tables\nDBs, MDBs and Projects\nEvents and pseudo attribute plugins\nData Model Definition Classes\nData Model Definition Classes\nBasic database access, query and modification.\nBasic database access, query and modification.\nFilters\nFilters\nIterators\nIterators\nDabacon Tables\nDabacon Tables\nDBs, MDBs and Projects\nDBs, MDBs and Projects\nEvents and pseudo attribute plugins\nEvents and pseudo attribute plugins\n\n\n\nData Model Definition Classes\nFilters\nIterators\nDabacon Tables\nDatabaseService\nDbAttribute\nDB\nDbElement\nDbElementType\nDbEvents\nDbExpression\nDbPseudoAttribute\nDbRule\nDbUserChanges\nMDB\nTable\nProject\nData Model Definition Classes\nFilters\nIterators\nDabacon Tables\nDBs, MDBs and Projects"}
{"Headers": "Data Model Definition Classes", "Content": "Four classes are available.\n\n\n"}
{"Headers": "class external to the AVEVA module", "Content": "There is a single class for all element types.\nThe purpose of the class is to:\nExternal to the AVEVA module, the hash value can be used to uniquely identify an Element type. The hash value is a 32 bit integer.\nIn C# a DbElementType object may be obtained in one of three ways:\nThe methods allow the Element type metadata to be accessed. For example:\nPseudo attributes that provide similar information on a particular element instance (for example, on a DbElement) are:\nHLIS\nDbElementType[]\nList of all possible types in owning hierarchy\nLIST\nDbElementType[]\nList of all possible member types\nLLIS\nDbElementType[]\nList of all possible types in member hierarchy\nOLIS\nDbElementType[]\nList of all possible owner types\nREPTXT\nString\nReporter text used for element type\nATTLIST\nDbAttribute[]\nList of all visible attributes for element\nPSATTS\nDbAttribute[]\nList of pseudo attributes\nUDALIS\nDbAttribute[]\nList of UDAs\n\nDbNounManual- Manual category\nDbType - DB type\nInstances of the class identify the element type. i.e. methods on other classes take a DbElementType as an argument rather than a string to denote an Element type. The DbElementType has 'value' semantics for comparison purposes. i.e. comparing of two DbElementTypes will always return true if they refer to the same type, even if they are different objects.\nAccess the metadata associated with element types.\nInstances of the class identify the element type. i.e. methods on other classes take a DbElementType as an argument rather than a string to denote an Element type. The DbElementType has 'value' semantics for comparison purposes. i.e. comparing of two DbElementTypes will always return true if they refer to the same type, even if they are different objects.\nInstances of the class identify the element type. i.e. methods on other classes take a DbElementType as an argument rather than a string to denote an Element type. The DbElementType has 'value' semantics for comparison purposes. i.e. comparing of two DbElementTypes will always return true if they refer to the same type, even if they are different objects.\nAccess the metadata associated with element types.\nAccess the metadata associated with element types.\nName\nDescription\nBaseType (for User Defined Element Type [UDETs])\nList of attributes\nList of User Defined Attributes (UDAs)\nAllowed members\nAllowed owners\nTypes that may appear above this element type\nTypes that may appear below this element type\nElement types that may be referenced from a given attribute on this element type\nDatabase types in which it occurs\nName\nName\nDescription\nDescription\nBaseType (for User Defined Element Type [UDETs])\nBaseType (for User Defined Element Type [UDETs])\nList of attributes\nList of attributes\nList of User Defined Attributes (UDAs)\nList of User Defined Attributes (UDAs)\nAllowed members\nAllowed members\nAllowed owners\nAllowed owners\nTypes that may appear above this element type\nTypes that may appear above this element type\nTypes that may appear below this element type\nTypes that may appear below this element type\nElement types that may be referenced from a given attribute on this element type\nElement types that may be referenced from a given attribute on this element type\nDatabase types in which it occurs\nDatabase types in which it occurs\n\n\n\nDbElementType[]\nDbElementType[]\nDbElementType[]\nDbElementType[]\nString\nDbAttribute[]\nDbAttribute[]\nDbAttribute[]"}
{"Headers": "DbElement type", "Content": "This is very similar to DbElementType. There is a single class for all attributes.\nThe purpose of the class is to:\nThe class should not be confused with the attribute value. The actual Attribute value for a particular Element can only be accessed via the DbElement class. Comparing two DbAttributes just compares whether they identify the same attribute, the comparison does not look at attribute values in any way.\nExternal to the AVEVA module, the hash value can be used to uniquely identify an Attribute. The hash value is a 32 bit integer.\nIn C# a DbAttribute object may be obtained in the following ways:\nThe methods allow the following metadata to be accessed:\nAttribute Type\nUnits\nName\nDescription\nCategory\nSize\nAllowed Values\nAllowed ranges\nIs a UDA\nIs a pseudo attribute\nWhether the attribute may take a qualifier\nAttribute Type\nUnits\nName\nDescription\nCategory\nSize\nAllowed Values\nAllowed ranges\nIs a UDA\nIs a pseudo attribute\nWhether the attribute may take a qualifier\nFind the type of attribute XLEN. We use the global instance of XLEN on the DbAttributeInstance class.\nDbAttributeUnit -\nType of units, for example: distance or bore or none.\nDbAttributeType \u2013\nType of attribute. One of\nINTEGER = 1,\nDOUBLE = 2,\nBOOL = 3,\nSTRING = 4,\nELEMENT = 5,\nDIRECTION = 7,\nPOSITION = 8,\nORIENTATION = 9\nDbAttributeQualifier \u2013 used to determine what sort of qualifier an attribute has\nDbAttributeUnit -\nType of units, for example: distance or bore or none.\nDbAttributeType \u2013\nType of attribute. One of\n\nINTEGER = 1,\n\nDOUBLE = 2,\n\nBOOL = 3,\n\nSTRING = 4,\n\nELEMENT = 5,\n\nDIRECTION = 7,\n\nPOSITION = 8,\n\nORIENTATION = 9\nDbAttributeQualifier \u2013 used to determine what sort of qualifier an attribute has\n\nusing ATT=Aveva.Core.Database.DbAttributeInstance;\n   \nDbAttributeType  xlenTyp= ATT.XLEN.Type;\nAccess the metadata (i.e. data about data) associated with attributes, for example: type, name, length.\nIdentify attributes. i.e. methods on other classes should always take a DbAttribute rather than a string as an argument to denote the attribute. Any comparison of attribute identity should be done by comparing DbAttribute objects.\nAccess the metadata (i.e. data about data) associated with attributes, for example: type, name, length.\nAccess the metadata (i.e. data about data) associated with attributes, for example: type, name, length.\nIdentify attributes. i.e. methods on other classes should always take a DbAttribute rather than a string as an argument to denote the attribute. Any comparison of attribute identity should be done by comparing DbAttribute objects.\nIdentify attributes. i.e. methods on other classes should always take a DbAttribute rather than a string as an argument to denote the attribute. Any comparison of attribute identity should be done by comparing DbAttribute objects.\n\n\n\nDbElement class\nDbAttributes\nusing \nDbAttributeUnit -\nType of units, for example: distance or bore or none.\nDbAttributeType \u2013\nType of attribute. One of\nINTEGER = 1,\nDOUBLE = 2,\nBOOL = 3,\nSTRING = 4,\nELEMENT = 5,\nDIRECTION = 7,\nPOSITION = 8,\nORIENTATION = 9\nDbAttributeQualifier \u2013 used to determine what sort of qualifier an attribute has"}
{"Headers": "class contains instances of DbElement Type", "Content": "This class contains instances of DbElementType for every element type in the AVEVA module. These instances may be used wherever a DbElementType is expected, for example: if a method MyMethod() takes an DbElementType, then you could write:\nfor example:\nIt is often convenient to add a using statement for these instances, for example:\nMyMethod(Aveva.Core.Database.DbElementTypeInstance.EQUIPMENT);\nusing NOUN=Aveva.Core.Database.DbElementTypeInstance;\n   \nMyMethod(NOUN.EQUIPMENT);\n\n\n\nDbElementType\nDbElementType\nMyMethod(\n)\nDbElementType,\nusing"}
{"Headers": "class contains instances of DbAttribute", "Content": "This class contains instances of DbAttribute for every element type in the AVEVA module. These instances may be used wherever a DbAttribute is expected, for example: if a method MyMethod() takes a DbAttribute, you could write:\nFor example:\nIt is often convenient to add a using statement for these instances.\nFor example:\nMyMethod(Aveva.Core.Database.DbAttributeInstance.XLEN);\nusing ATT=Aveva.Core.Database.DbAttributeInstance;\n   \nMyMethod(ATT.XLEN);\n\n\n\nMyMethod()\nDbAttribute\nusing"}
{"Headers": "Element Access", "Content": "Functionality is available to manipulate the access to elements.\n\n\n"}
{"Headers": "section describes the DbElement class", "Content": "This section describes the DbElement class. The DbElement class is the most widely used class and it covers a large proportion of the database functionality that will be used in practise.\nThe methods fall into the following groups:\nDbElement is a generic object that represents all database elements regardless of their type.\nAn instance of a DbElement may be obtained as follows:\nfor example.\nThe DbElement object encapsulates the identity of the database object. Any comparison of database objects must be done using DbElements. The DbElement has 'value' semantics for comparison purposes. i.e. comparing of two DbElements will always return true if they refer to the same element, even if they are different objects. DbElement instances should be used in all cases where the identity of an element is being passed or stored.\nA DbElement can be identified externally to the AVEVA module by a combination of the ref number AND type. The ref number is a two long integer, for example: =123/4567.\nA DbElement need not represent a 'valid' element. There are a number of reasons why a DbElement might be invalid:\nThere is a IsValid()method to test if a DbElement is valid.\nIf the DbElement is invalid then all attribute access and database navigation will fail for that DbElement.\nThe error handling techniques used are:\nDbElement has the following basic methods:\nToString()- Returns the Name of the element. If unnamed, it returns the constructed name.\nGetElementType()- Returns the DbElementType.\nThere are a number of pseudo attributes that return slight variations on name and type, as below.\nType related:\nACTTYPE\nDbElementType\n\nType of element\nAHLIS\nDbElementType (200)\n\nList of actual types in owning hierarchy\nOSTYPE\nDbElementType\n\nShortcut for \"Type of owner\"\nTYPE\nDbElementType\n\nType of the element, ignoring UDET\nTYSEQU\nint\n\nType Sequence Number\nName Related:\nCUTNAM\nString\nint\nFull name of element, truncated to n characters\nCUTNMN\nString\nint\nFull name of element (without leading slash) truncated to n characters\nFLNM\nString\n\nFull name of the element\nFLNN\nString\n\nFull name of the element (without leading slash)\nISNAMED\nBool\n\nTrue if element is named\nNAMESQ\nString\n\nType. sequence number and name of element\nNAMETY\nString\n\nType and name of the element\nNAMN\nString\n\nName of the element (without leading slash)\nNAMTYP\nString\n\nType and full name of element\n\nDbElement vess1 = DbElement.GetElement(\"/VESS1\");\nNavigation\nQuerying of attributes\nDatabase modifications\nStorage of rules and expressions\nComparison across sessions\nNavigation\nNavigation\nQuerying of attributes\nQuerying of attributes\nDatabase modifications\nDatabase modifications\nStorage of rules and expressions\nStorage of rules and expressions\nComparison across sessions\nComparison across sessions\nThere is a static GetElement() method with no arguments to return a 'null' DbElement.\nThere is a static GetElement() method which returns a DbElement given a name. This name should include the '/'.\nThere is a static GetElement() method which returns a DbElement given a ref (two long int array) and type. This is only needed where a reference has been stored externally to the AVEVA module.\nThere are many methods on various classes which return DbElements\nThere is a static GetElement() method with no arguments to return a 'null' DbElement.\nThere is a static GetElement() method with no arguments to return a 'null' DbElement.\nThere is a static GetElement() method which returns a DbElement given a name. This name should include the '/'.\nThere is a static GetElement() method which returns a DbElement given a name. This name should include the '/'.\nThere is a static GetElement() method which returns a DbElement given a ref (two long int array) and type. This is only needed where a reference has been stored externally to the AVEVA module.\nThere is a static GetElement() method which returns a DbElement given a ref (two long int array) and type. This is only needed where a reference has been stored externally to the AVEVA module.\nThere are many methods on various classes which return DbElements\nThere are many methods on various classes which return DbElements\nThe element is in a DB not opened.\nThe element has been deleted.\nThe element is in a DB not opened.\nThe element is in a DB not opened.\nThe element has been deleted.\nThe element has been deleted.\n\n\n\nDbElement\nDbElement\nGetElement()\nDbElement\nGetElement()\nDbElement\nGetElement()\nDbElement\nDbElements\nDbElement\nDbElements\nDbElement\nDbElements\nDbElement\nDbElement\nIsValid()\nmethod\nDbElement\nDbElement\nDbElement\nDbElement\nToString()\nGetElementType()\nDbElementType\n.\nType related:\nDbElementType\nDbElementType (200)\nDbElementType\nDbElementType\nint\nName Related:\nString\nint\nString\nint\nString\nString\nBool\nString\nString\nString\nString"}
{"Headers": "methods to navigate the primary hierarchy", "Content": "There are basic methods to navigate the primary hierarchy. for example, consider the following hierarchy:\n\nIf we are sitting at Zone2, we can navigate as follows:\nScanning the database is a very common operation. For this reasons there are additional iterator and filter classes that ease this task. These are described in the section on Filters/Iterators.\nALLELE\nDbElement[])\nDbElementType\nAll elements in the MDB of a particular type\nCONNECTIONS\nDbElement[]\n\nConnections\nCONNECTIONSH\nDbElement[]\n\nConnections for all descendants\nCONNER\nString\nInt\nConnection error message\nDDEP\nInt\n\nDatabase depth within hierarchy (World is 0)\nFRSTW\nDbElement\nString\nReference of first world of given DB type in current MDB\nMAXD\nInt\n\nDB hierarchy depth of lowest level item beneath element\nMBACK\nDbElement[]\n*DbElementType\nMembers in reverse order\nMCOU\nInt\n*DbElementType\nNumber of Element Members of Given type\nMEMB\nDbElement[]\n*DbElementType\nAll members, or members of specific type\nOWNLST\nDbElement[]\n\nOwning hierarchy\nPARENT\nDbElement\n*DbElementType\nReference of ascendant element of specified type\nSEQU\nInt\n\nSequence Position in Member List\nTYSEQU\nInt\n\nType Sequence Number\n'*'- qualifier is optional\nStandard navigation methods do not work for descending a secondary hierarchy. Pseudo attribute SMEMB must be used, for example: to get the design elements below a GPSET, you must query the SMEMB attribute on the GPSET.\nPseudo attributes relating to secondary hierarchies are:\nGPPRXS\nDbElement[]\nGroup proxy items referring to element\nGROUPS\nDbElement[]\nGPSETs in which element occurs\nSEXPND\nDbElement[]\nRecursive expansion of SMEMB\nSITEM\nDbElement\nReference from secondary hierarchy\nSMEMB\nDbElement[]\nImmediate members in secondary hierarchy\nThe difference between SMEMB and SEXPND is that SEXPND allows for recursive secondary hierarchies. Where there are no recursive possibilities, SMEMB and SEXPND will be the same. The following example illustrates the difference between SMEMB and SEXPND:\n\nIn the example there are two secondary nodes S1 and S2. S1 holds element A and C, and S2 holds S1, D and G.\nFor S1,\nSMEMB returns A,C\nSEXPND returns A,C\nFor S2,\nSMEMB returns S1,D, G\nSEXPND returns A,C, D, G\nusing NOUN=Aveva.Core.Database.DbElementTypeInstance;\n   \nDbElement zone = DbElement.GetElement(\"/Zone1\")\nDbElement temp=zone2.Next(); // temp is now Zone3\ntemp=zone2->Previous(); // temp is now Zone1\ntemp=zone2->Owner(); // temp is now Site1\ntemp=zone2->FirstMember(); // temp is now Pipe1\nDbElement pipe1=temp;\ntemp=zone2->LastMember(); // temp is now Equi1\nDbElement temp=pipe1.Next(NOUN.EQUIPMENT); // temp is Equi1\nDbElement temp=pipe1.Previous(); // temp is \u2018null\u2019 as there is no previous element.\n      This can only be tested using the \u2018IsNull\u2019 method\n   \n\n\n\nusing\n \nAttribute Name\nData Type\nQualifier\nDescription\nDbElement[])\nDbElementType\nDbElement[]\nDbElement[]\nString\nInt\nInt\nDbElement\nString\nInt\nDbElement[]\n*DbElementType\nInt\n*DbElementType\nDbElement[]\n*DbElementType\nDbElement[]\nDbElement\n*DbElementType\nInt\nInt\nDbElement[]\nDbElement[]\nDbElement[]\nDbElement\nDbElement[]"}
{"Headers": "site will have different attributes to a branch", "Content": "The attributes available on for a DbElement will depend on its type, for example: a site will have different attributes to a branch. For this reason attributes are accessed through generic methods rather than specific methods. These generic methods pass in the identity of the attribute being queried (a DbAttribute object). There are separate methods for each attribute type (int, double etc), plus separate methods for single values or arrays.\nfor example:\nThis call returns the value of attribute XLEN. If 'myEle' is not a BOX then an exception will be raised.\nIf there is any doubt as to whether 'myEle' is a BOX or not, then there are a set of methods that return false if the attribute does not exists.\nfor example:\nIn addition there is a IsAttributeValid() method that can be used to test if an attribute is valid or not.\nThe basic mechanism works for all attributes including UDAs and pseudo attributes.\nThe attribute types supported are:\nint, int[]\ndouble, double[]\nbool, bool[]\nstring, string[]\nDbElement, DbElement[]\nDbElementType, DbElementType[]\nDbAttribute, DbAttribute[]\nPosition\nDirection\nOrientation\nExpression\nint, int[]\ndouble, double[]\nbool, bool[]\nstring, string[]\nDbElement, DbElement[]\nDbElementType, DbElementType[]\nDbAttribute, DbAttribute[]\nPosition\nDirection\nOrientation\nExpression\nThere are two lists of valid attributes:\nRelated pseudo attributes are:\nAttribute Name\nData Type\nDescription\nATTLIST\nDbElementType[]\nList of all visible attributes for element\nATTRAW\nDbElementType[]\nList of raw attributes\nPSATTS\nDbElementType[]\nList of pseudo attributes\nRLIS\nDbElementType[]\nList of rules set\nUDALIS\nDbElementType[]\nList of UDAs\nUDASET\nDbElementType[]\nList of UDAs set\nAttribute Name\nData Type\nDescription\nATTLIST\nDbElementType[]\nList of all visible attributes for element\nATTRAW\nDbElementType[]\nList of raw attributes\nPSATTS\nDbElementType[]\nList of pseudo attributes\nRLIS\nDbElementType[]\nList of rules set\nUDALIS\nDbElementType[]\nList of UDAs\nUDASET\nDbElementType[]\nList of UDAs set\nMany attributes take a qualifier. The qualifier is the extra information to make the query. Examples of where a qualifier is used are:\nThe definition of what pseudo attributes take what qualifier is described in the data model reference manual.\nThe DbQualifier class represents the qualifier. This can hold any type of qualifier, i.e. int, double,string, DbElementType, Attribute, position, direction, orientation. It can hold multiple qualifier values, although few current attributes require multiple valued qualifiers. There is a separate method to set the WRT element.\nThere is a set of query routines that take a qualifier as an extra argument.\nfor example: to query the bore of ppoint 1:\nIf the attribute value is to go onto a form then the value must be formatted correctly. The correct formatting is not always obvious or available. Therefore there are special methods to return any attribute as a formatted string. This will format the attribute into the form that would appear at the command line. For example if the attribute is a position and we are working in finch unit, then something like 'W 39'4.7/16 N 59'0.85/128 U 4'0.31/128' might be returned.\nThe method to do this is GetAsString().\nusing ATT=Aveva.Core.Database.DbAttributeInstance;\n   \ndouble length=myEle.GetDouble(ATT.XLEN);\nusing ATT=Aveva.Core.Database.DbAttributeInstance;\n   \ndouble length;\nif (!myEle.GetValidDouble(ATT_XLEN,length)) {\n    // handle error in some way\n}\nDbQualifier qual=new DbQualifier();\n   \nqual.Add(1);\ndouble bore=myele.GetDouble(ATT.PPBO, qual);\nNote:\nThe methods that are called GetAttribute, GetAttributeArray are the 'getattribute' methods that return DbAttributes. Similarly the GetElement, GetElementArray methods are the 'getattribute' methods that return DbElements. This is confusing since GetElement is also the name of the method to return a DbElement given a name. We may change the names of these in the future.\nNote:\nThere is no generalized method for setting an attribute from a string.\n\n\n\nDbElement\nDbAttribute\nusing \nusing \nA\nIsAttributeValid()\nNote\n:\nGetAttribute\nGetAttributeArray\nDbAttributes\nGetElement\nGetElementArray\nDbElements\nGetElement\nDbElement\nGetAttributes()\nDbElementType[]\nDbElementType[]\nDbElementType[]\nDbElementType[]\nDbElementType[]\nDbElementType[]\nDbQualifier\nnew\nW 39'4.7/16 N 59'0.85/128 U 4'0.31/128\nGetAsString()\nNote\n:"}
{"Headers": "when an element is modified", "Content": "The following modifications are allowed:\nWhen an element is modified, it is not simply the case of directly updating the database. For example, when setting an attribute the following sequence takes place:\nIt can be seen that making what appears to be a simple modification is actually quite complicated.\nIn particularly a lot of errors are possible. Errors may be generated by any of the steps 1-2 plus steps 4-8.\nIf an error occurs the code will raise a PdmsException. The calling code needs to allow for this.\nClarification of some of these errors is as follows:\nCheck that the attribute value is the right type\nFor example, if a text attribute then the new value must be text, for example: setting DESC to 99 will raise an error.\nCheck against any valid values or ranges\nThis will check the value against any user provided criteria stored in the dictionary DBs.\nCheck access control\nAn error will be raised if the modification is not allowed. An error will also be raised at this point if the attribute is not valid for the given element.\nCheck that the DB is open in write\nAn error will be raised if 'read only'.\nCheck LOCK flag\nAn error will be raised if the LOCK flag is true.\nDo claim check, and claim if needed (and implicit claim is allowed)\nAn error will be raised if:\nCall the legality checking routines to make sure that the modification is valid\nThese checks are made by the plugged in application specific code. Thus potentially any error could be raised.\nIf a DB has been set up to be 'implicit' the user will claim elements as needed without having to do explicit claims.\nThere are some methods on DbElement to claim/release individual elements or a hierarchy of elements. If working on a hierarchy of elements, and errors occur, then the system will still do what it can.\nThere are also methods on the MDB class to claim/release a list of elements. Performance is improved by claiming or releasing elements in bulk, thus in general the MDB methods should be used rather than the ones on DbElement.\nThe granularity of claim is at the level of primary element. This is described in the data management reference manual.\nPseudo Attributes Relating to Claims\nCLMID\nString\nUnique system ID of user claiming element\nCLMNUM\nint\nUser or extract number claiming element. Extract numbers are negative\nCLMTIE\nDbElement[]\nReference to elements that are automatically claimed along with this element\nNPDESC\nDbElement[]\nList of non primary offspring\nOKCLA\nbool\nTrue if element may be claimed\nOKCLH\nBool\nTrue if element and hierarchy may be claimed\nOKREL\nbool\nTrue if element may be released\nOKRLH\nBool\nTrue if element and hierarchy may be released\nPRIMTY\nBool\nTrue if element is primary\nPRMMEM\nbool\nTrue if there are any primary elements amongst descendants\nPRMOWN\nDbElement\nPrimary owning element (will be itself if primary)\nUSCLHI\nDbElement[]\nElements in descendant hierarchy claimed to this user\nUSERC\nString\nUser name of user claiming element\nUSNCLH\nDbElement[]\nElements in descendant hierarchy not claimed to this user\n\nSet Attribute\nCreate Element\nDelete Element\nCopy Element\nMove Element\nChange Type\nSet Attribute\nSet Attribute\nCreate Element\nCreate Element\nDelete Element\nDelete Element\nCopy Element\nCopy Element\nMove Element\nMove Element\nChange Type\nChange Type\nThe DB uses explicit claims and the primary element has not been claimed.\nThe primary element is claimed by another user or extract.\nThe DB uses explicit claims and the primary element has not been claimed.\nThe DB uses explicit claims and the primary element has not been claimed.\nThe primary element is claimed by another user or extract.\nThe primary element is claimed by another user or extract.\n\n\n\nSet Attribute\nCreate Element\nDelete Element\nCopy Element\nMove Element\nChange Type\nSet Attribute\nCreate Element\nDelete Element\nCopy Element\nMove Element\nChange Type\nCheck that the attribute value is the right type\nCheck against any valid values or ranges\nCheck access control\nCheck that the DB is open in write\nCheck LOCK flag\nDo claim check, and claim if needed (and implicit claim is allowed)\nCall the legality checking routines to make sure that the modification is valid\nDbElement\nDbElement\nPseudo Attributes Relating to Claims\nString\nint\nDbElement[]\nDbElement[]\nbool\nBool\nbool\nBool\nBool\nbool\nDbElement\nDbElement[]\nString\nDbElement[]"}
{"Headers": "PML database expression", "Content": "Database expressions are PML1 expressions, for example: (XLEN * 1000). Expressions are of the following type:\nDatabase expressions are stored in various places in the AVEVA module as follows:\nThere is a DbExpression class to hold an expression. An DbExpression may be obtained in one of the following ways:\nHaving got an DbExpression there are two things that can be done with it:\nThe methods to evaluate an expression against an element are on the DbElement class. There are different methods depending on the expected result of the expression. The method names start with 'Evaluate'. The method that returns a double has an argument for the units (distance/bore/none). The result will always be in millimetres (mm), for example:\nIn this case the core system can work out that it is a distance, since DIAM is a distance. Thus although we specified that it was a distance, it was not strictly needed. Thus if the distance units were inch or finch then the '+2' would be interpreted as '+2inches'.\nHowever consider:\nIn this case we do not know if \"10\" is 10mm or 10 inches. We must tell the system that it is a 'distance' unit. The system then interrogates the current distance units to return the result. If the current distance units is mm, then dval will be 10.0. If the current distance units is inch/finch then \"10\" is interpreted to mean 10 inches and is hence returned as 254.\nPML.NET rules consist of an expression and a dynamic/static flag. When constructing a rule, the expression type is also needed.\nThere are methods on DbElement to:\nNRULEE\nInt\n\nNumber of rule inconsistencies on element\nRCOU\nInt\n\nNumber of rules on element\nRULEER\nString\nint\nText of \"nth\" rule error\nRULSET\nDbAttribute[]\n\nList of rules set\n\nDbExpression expr = DbExpression.Parse(\"DIAM OF PREV + 2\");\ndouble dval;\n   \nDbAttributeUnit units = DbAttributeUnit.DIST;\ndval = nozz1.EvaluateDouble(expr4, units);\nDbExpression expr = DbExpression.Parse(\"10\");\ndouble dval;\n   \nDbAttributeUnit units = DbAttributeUnit.DIST;\ndval = nozz1.EvaluateDouble(expr4, units);\nDouble\nDbElement\nBool\nString\nPosition\nDirection\nOrientation\nDouble\nDouble\nDbElement\nDbElement\nBool\nBool\nString\nString\nPosition\nPosition\nDirection\nDirection\nOrientation\nOrientation\nAs part of a rule\nParameterization of the catalogue\nAs part of a rule\nAs part of a rule\nParameterization of the catalogue\nParameterization of the catalogue\nUse the static method internalParse() that creates a DbExpression from a string, for example: internalParse(\"XLEN * 100\")\nRetrieve an expression from a rule\nRetrieve an expression from a catalogue parameter\nUse the static method internalParse() that creates a DbExpression from a string, for example: internalParse(\"XLEN * 100\")\nUse the static method internalParse() that creates a DbExpression from a string, for example: internalParse(\"XLEN * 100\")\nRetrieve an expression from a rule\nRetrieve an expression from a rule\nRetrieve an expression from a catalogue parameter\nRetrieve an expression from a catalogue parameter\nSet a rule for any attribute.\nGet a rule for any attribute\nEvaluate a rule\nVerify that the rule result is up to date\nSet a rule for any attribute.\nSet a rule for any attribute.\nGet a rule for any attribute\nGet a rule for any attribute\nEvaluate a rule\nEvaluate a rule\nVerify that the rule result is up to date\nVerify that the rule result is up to date\nNote:\nIf the value is required to be formatted for output, then it must be converted back in all cases. A method will be added to return values in local units at a later point.\n\n\n\ninternalParse()\nDbExpression\ninternalParse(\"XLEN * 100\")\ndouble\ndouble\nNote\nInt\nInt\nString\nint\nDbAttribute[]"}
{"Headers": "comparison date in c#", "Content": "There are no explicit methods exposed in C# which cover comparison across sessions. It is not currently possible to set the comparison date in C#.\nThere are however a number of pseudo attributes that can be accessed as follows:\nATTMOD\nBool\nDbAttribute\nTrue if specified attribute has been modified this session\nATTMODC\nbool\nDbAttribute\nTrue if specified attribute has been modified since comparison date\nATTMODLIST\nDbAttribute[]\nint\nList of attributes modified since given session\nATTMODLISTC\nDbAttribute[]\n\nList of attributes modified since comparison date\nCRINFO\nstring\n\nDB creation information\nDBSESS\nint\n\nLast DB session\nELECRE\nbool\nint\nTrue if created since given session\nELECREC\nbool\n\nTrue if created since comparison date\nELEDEL\nbool\nint\nTrue if deleted since given session\nELEDELC\nbool\n\nTrue if deleted since comparison date\nELEMOD\nbool\nint\nTrue if modified since given session\nELEMODC\nbool\n\nTrue if modified since comparison date\nEXMOD\nbool\n\nTrue if element modified in this extract\nHIST\nInt[]\nDbAttribute\nHistory of sessions in which element or specified attribute were made\nLASTM\nstring\nDbAttribute\nDate of last modification\nMSESS\nint\nDbAttribute\nLast session number\nPRVSES\nint\nint\nPrevious Session to that specified\nRULEMOD\nbool\nDbAttribute\nTrue if rule modified this session\nRULEMODC\nBool\nDbAttribute\nTrue if rule modified since comparison date\nRULEMODLIST\nDbAttribute[]\nint\nList of rules modified since given session\nRULEMODLISTC\nDbAttribute[]\n\nList of rules modified since comparison date\nSESCLA\nint\n\nSession Of Claim\nSESSC\nstring\nint\nComment for specified session\nSESSCA\nInt[]\n\nList of pairs of DB number, last session number for all referenced DBs\nSESSCH\nInt[]\n\nAs for SESSCA, but searches all descendants for referenced DBs\nSESSD\nstring\nint\nDate of specified Session\nSESSM\nint\nDbAttribute\nSession Of Last Modification\nSESSNO\nint\n\nCurrent opened Session\nSESSU\nstring\nint\nUser creating specified session\nUSERM\nstring\nDbAttribute\nUser making last modification\n\n\n\n\nBool\nDbAttribute\nbool\nDbAttribute\nDbAttribute[]\nint\nDbAttribute[]\nstring\nint\nbool\nint\nbool\nbool\nint\nbool\nbool\nint\nbool\nbool\nInt[]\nDbAttribute\nstring\nDbAttribute\nint\nDbAttribute\nint\nint\nbool\nDbAttribute\nBool\nDbAttribute\nDbAttribute[]\nint\nDbAttribute[]\nint\nstring\nint\nInt[]\nInt[]\nstring\nint\nint\nDbAttribute\nint\nstring\nint\nstring\nDbAttribute"}
{"Headers": "Iterators", "Content": "The DBElementCollection class can be used to iterate through the database hierarchy. The iterator is created with a root element and an optional filter. There are then methods to step through the hierarchy and return the element at the current location.\nFor example: to look for all nozzles below a given element\nThe collection can then be iterated through using foreach\nThe iterator class has been written to avoid unnecessarily scanning parts of the database that will not match the filter, for example: if looking for all boxes then the iterator will not bother to look below pipes.\nTypeFilter filt = new TypeFilter(DbElementTypeInstance.NOZZLE);\n   \nDBElementCollection collection;\n   \ncollection = new DBElementCollection(ele, filt);\n   \nforeach (DbElement ele in collection)\n{\n\u2026. Do something\n}\n\n\n\nDBElementCollection\nTypeFilter\nnew \nTypeFilter(DbElementTypeInstance\nDBElementCollection\nnew \nDBElementCollection\nele\nforeach \n(\nDbElement\nin \ncollection)"}
{"Headers": "Filters", "Content": "There are a variety of ready built filter classes available. The main ones are:\nTypeFilter - True for given Element type(s)\nAttributeFalseFilter - True if given attribute is false\nAttributeTrueFilter - True if given attribute is true\nAttributeRefFilter - True if given attribute value matches given DbElement\nAndFilter - AND two existing filters\nOrFilter - OR two existing filters\nBelowFilter - Filter to test if element is below an element for which the given filter is true.\n\n\n\nTypeFilter\nAttributeFalseFilter\nAttributeTrueFilter\nAttributeRefFilter\nAndFilter\nOrFilter\nBelowFilter"}
{"Headers": "Dabacon Tables", "Content": "In the Dabacon schema we can define an attribute to be an indexed attribute. Indexed attributes go into a Dabacon table.\nTables consist of a list of key/value pairs. The key may be a string (ntable), integer (itable) or reference (ftable). The 'value' part of the pair is always the refno of the element having that attribute value, for example: internally a name table may look something like:\n\u2026..\nJanet = 123/456\nJohn = 321/543\nJonathon = 111/321\n\u2026\nThus for a given name, the corresponding element can rapidly be found without having to scan the entire Multiple DataBase (MDB).\nThe keys in a name table must be unique. Integer and reference tables may contain the same key many times, for example: internally a reference table may look like:\n\u2026.\n=123/456 =234/555\n=123/456 =222/333\n=123/456 =211/999\n=123/458 =203/909\nIn the above table, element =123/456 has appeared in the table three times. This means that three different elements were all referencing =123/456 for this particular attribute. This is common, for example: catalogue references are reference tables, and for these there may be hundreds of elements referencing the same catalogue component. A further point worth noting with respect to tables:\nEach Database (DB) has its own table. The entries in that table are for 'values' in that DB. Thus for the above ftable, =234/555 etc must be in this DB. However =123/456, =123/458 may be in a different DB. Indeed there may well be further references to =123/458 from other DBs. Hence to find all references to =123/456 we need to check the tables in each opened DB.\nEach Database (DB) has its own table. The entries in that table are for 'values' in that DB. Thus for the above ftable, =234/555 etc must be in this DB. However =123/456, =123/458 may be in a different DB. Indeed there may well be further references to =123/458 from other DBs. Hence to find all references to =123/456 we need to check the tables in each opened DB.\nEach Database (DB) has its own table. The entries in that table are for 'values' in that DB. Thus for the above ftable, =234/555 etc must be in this DB. However =123/456, =123/458 may be in a different DB. Indeed there may well be further references to =123/458 from other DBs. Hence to find all references to =123/456 we need to check the tables in each opened DB.\n\n\n"}
{"Headers": "C# classes to access directly to the Dabacon Tables", "Content": "There are C# classes that enable direct access to the Dabacon tables. The classes are defined as follows:\nNameTable - for iterating through name tables\nRefTable - for iterating through reference tables\nIntTable - for iterating through integer tables\nThese classes work on a single DB. In most cases, we really want to iterate through all DBs in the MDB as if it was one table. Thus for integer and name tables there are iterator classes that go across the whole MDB as follows:\nMdbNameTable - for iterating through a name table across entire MDB\nMdbIntTable - for iterating through an integer table across entire MDB\nThere is no method for iterating through a reference table since the order of references in a table is not meaningful.\nThere are also methods to return all entries for a given key. This is particularly useful for reference tables; these are methods of the MDB class.\nIn C# there is a NameTable class. An example of C# code that looks for all names starting with the letter 'B' is as follows:\nDabacon allocates search tokens when scanning tables. It has a limited number of search tokens. If you get to the end of the table then the token is freed automatically. However if you stop the search before you get to the end then you must explicitly free the token.\nThe IDispose method is used to free the underlying Dabacon token. Therefore ALWAYS scan the Dabacon table within a 'using' block to make sure that the Dispose method is called. If the underlying token is not freed then errors will be output to the AVEVA module command line of the form:\nThe error generating code does not actually free the tokens. So typically you will see the number climb as more tokens are used up and not freed. The messages will be generated until the database is closed.\nstring nam1=new string(\"/B\");\nstring nam2=new string(\"/C\");\nNameTable ntable = new MdbNameTable(db, DBAttribute.NAME, nam1, nam2);\n   \nusing (ntable)\n   \n{\n   foreach (Element ele in ntable)\n   \n   {\n   // Do something here with each element\n   }\n}\n\"xx dabacon search tokens - Expected none \"\n\n\n\nNameTable\nRefTable\nIntTable\nMdbNameTable\nMdbIntTable\nnew\nusing\n   \nforeach\nin"}
{"Headers": "Multiple DataBase Functionality", "Content": "The Miltiple DataBase (MDB) class exposes methods that act on the currently opened MDB. This is a singleton class. It contains methods to\nRelated pseudo attributes are:\nOKDROP\nbool\nTrue if element may be dropped\nOKRLEX\nbool\nTrue if element may be extract released\n\nOpen/close an MDB.\nSave work / quit work.\nQuery claims.\nClaim/release elements\nExtract operations, for example: flush, refresh, extract claim, extract release, extract drop.\nGet opened DataBases (DBs).\nReturn an element(s) of a given name.\nReturn elements with matching values in name and integer tables (as described in previous section.\nOpen/close an MDB.\nOpen/close an MDB.\nSave work / quit work.\nSave work / quit work.\nQuery claims.\nQuery claims.\nClaim/release elements\nClaim/release elements\nExtract operations, for example: flush, refresh, extract claim, extract release, extract drop.\nExtract operations, for example: flush, refresh, extract claim, extract release, extract drop.\nGet opened DataBases (DBs).\nGet opened DataBases (DBs).\nReturn an element(s) of a given name.\nReturn an element(s) of a given name.\nReturn elements with matching values in name and integer tables (as described in previous section.\nReturn elements with matching values in name and integer tables (as described in previous section.\n\n\n"}
{"Headers": "DstaBase Functionality", "Content": "When an Multiple Database (MDB) is opened, a Database (DB) class instance is created for each opened DB.\nThe functionality offered by this class falls into the following categories:\nACCEDB\nstring\n\nDB access\nCLAIM\nString\n\nImplicit or explicit claims\nCLCCNT\nint\n\nClaim list changes count\nCSESS\nString\nint\nComment entered for specified session\nDACC\nString\n\nDatabase access\nDBLC\nDbElement[]\n\nList of LOCs belonging to a DB\nDCLA\nString\n\nDatabase claim mode\nDSESS\nString\nint\nDate of specified session\nEXPIRY\nString\n\nProtected DB Expiry date\nEXTALS\nDbElement[]\n\nExtract ancestors\nEXTCLS\nDbElement[]\n\nExtract children\nEXTDES\nDbElement[]\n\nExtract descendants\nEXTFAM\nDbElement[]\n\nExtract family\nFILENAME\nString\n\nDB filename\nFOREIGN\nstring\n\nOriginating project\nHCCNT\nint\n\nHeader/Extract list changes count\nISDBFR\nbool\n\nTrue if database is foreign\nISDRDB\nBool\n\nTrue if database has drawings\nISWORK\nbool\n\nTrue if a working extract\nLINKSN\nint\n\nLinked session on parent extract\nLPROT\nbool\n\nProtected DB Flag\nMDBCLS\nDbElement[]\n\nList of MDBs in which DB is current\nMDBLS\nDbElement[]\n\nList of MDBs to which DB belongs\nNACCNT\nint\n\nNon-additive changes count\nNAMEDB\nstring\n\nDB name\nNXTDBN\nint\n\nNext DB number\nNXTEXN\nint\n\nNext DB extract number\nNXTFDB\nint\n\nNext DB file and DB number\nNXTFLN\nint\n\nNext DB file number\nPSESS\nint\nint\nPrevious session number\nSIZEDB\nint\n\nSize of DB\nSTPDBS\nDbElement[]\n\nStamps containing db\nSTPSES\nInt[]\n\nSessions used in at least one stamp\nSTYPDB\nstring\n\nDB sub type\nTYPEDB\nstring\n\nDB type\nUSESS\nstring\nint\nUser creating session\nIn addition for any DbElement in any DB, the following pseudo attributes provide information on the current DB:\nDBAC\nString\n\nDB Access, MULTIWRITE or UPDATE\nDBCL\nString\n\nDB Claim\nDBCNTL\nBool\n\nTrue if element is in a control DB\nDBEXNO\nint\n\nDB Extract Number\nDBFI\nString\n\nDB filename\nDBFN\nint\n\nDB file number\nDBNA\nString\n\nDB name\nDBNU\nint\n\nDB Number\nDBREF\nDbElement\n\nReference of DB element\nDBTY\nString\n\nDB type (DESI, CATA etc)\nDBVAR\nBool\n\nTrue if element is in a variant DB\nDBWRITE\nBool\n\nTrue if element is in a writable DB\nWDBNA\nSTRING\n\nWorking DB name\n\nQuery the properties of the DB, for example: number, MULTIWRITE or not\nReturning the world element for that DB\nSession information, for example: when was the session written and by whom. There is a DbSession object that holds details on a database session.\nReturn the DbElement in the system DB that represents this DB. This DbElement can then be used to query system attributes and additional pseudo attributes. The additional pseudo attributes available on the DbElement representing the DB are described below:\nQuery the properties of the DB, for example: number, MULTIWRITE or not\nQuery the properties of the DB, for example: number, MULTIWRITE or not\nReturning the world element for that DB\nReturning the world element for that DB\nSession information, for example: when was the session written and by whom. There is a DbSession object that holds details on a database session.\nSession information, for example: when was the session written and by whom. There is a DbSession object that holds details on a database session.\nReturn the DbElement in the system DB that represents this DB. This DbElement can then be used to query system attributes and additional pseudo attributes. The additional pseudo attributes available on the DbElement representing the DB are described below:\nReturn the DbElement in the system DB that represents this DB. This DbElement can then be used to query system attributes and additional pseudo attributes. The additional pseudo attributes available on the DbElement representing the DB are described below:\n\n\n\nstring\nString\nint\nString\nint\nString\nDbElement[]\nString\nString\nint\nString\nDbElement[]\nDbElement[]\nDbElement[]\nDbElement[]\nString\nstring\nint\nbool\nBool\nbool\nint\nbool\nDbElement[]\nDbElement[]\nint\nstring\nint\nint\nint\nint\nint\nint\nint\nDbElement[]\nInt[]\nstring\nstring\nstring\nint\nString\nString\nBool\nint\nString\nint\nString\nint\nDbElement\nString\nBool\nBool\nSTRING"}
{"Headers": "Events", "Content": "The database events fall into the following groups:\nGeneral capture of Database changes.\nWriting Pseudo attributes for User Defined Attributes (UDAs).\nDB/MDB related events.\nGeneral capture of Database changes.\nGeneral capture of Database changes.\nWriting Pseudo attributes for User Defined Attributes (UDAs).\nWriting Pseudo attributes for User Defined Attributes (UDAs).\nDB/MDB related events.\nDB/MDB related events.\n\n\n"}
{"Headers": "The generalised mechanism in C#", "Content": "The generalised mechanism in C# is as follows:\nThere is a delegate to define the event signature.\nThere is a method to add a delegate to the list of event handlers to be called.\nThere is a delegate to define the event signature.\nThere is a delegate to define the event signature.\nThere is a method to add a delegate to the list of event handlers to be called.\nThere is a method to add a delegate to the list of event handlers to be called.\n\n\n"}
{"Headers": "Dblayer maintains a change list of Database(DB)", "Content": "DBlayer maintains a change list of Database (DB) changes. Users can subscribe to this list of changes.\nThe list of changes is encapsulated in the DbUserChanges class. The DbUserChanges class has methods to determine what changes have been made, for example: elements created or deleted or modified.\nThe delegates are:\nTo add a subscriber (handler), the method is:\nThis will be in the DbEvents class.\nThe subscribers receive a DbUserChanges class instance which has a list of elements changed and what the changes are.\nThe events are fired as follows:\nThe event will only be fired if database changes have been made.\npublic delegate void ChangeEventHandler(DbUserChanges changes);\n   \npublic static void AddChangeEventHandler(ChangeDelegate plug)\n   \nAt the end of running in a Programmable Macro Language (PML) macro\nAfter the execution of an AVEVA module specific command on the command line\nWhen any action on a form has completed.\nAt the end of running in a Programmable Macro Language (PML) macro\nAt the end of running in a Programmable Macro Language (PML) macro\nAfter the execution of an AVEVA module specific command on the command line\nAfter the execution of an AVEVA module specific command on the command line\nWhen any action on a form has completed.\nWhen any action on a form has completed.\n\n\n\npublic delegate\npublic static void"}
{"Headers": "Calculate the value of pseudo attributes", "Content": "Code can be plugged in to calculate the value of pseudo attributes. The code to do this must be registered in the AVEVA module by passing in a C# delegate.\nCode can be registered in two ways:\nThe same UDA may have multiple delegates registered for different element types.\nThere is a different delegate for each attribute type, for example: for integer attributes the delegate is:\nThese are defined in the DbPseudoAttribute class.\nThe user must write a method that matches the method signature of the delegate, for example: to write pseudo attribute code for a 'double' attribute, the user must write a method that has the signature defined by 'GetDoubleDelegate'. for example, a method that takes a DbElement, a DbAttribute, int and returns a double.\nFor example: the following method would be valid:\nAn instance of the delegate containing the method must then be created and registered with the AVEVA module.\nThere are separate methods to register the different types of delegates. There are also separate methods to add a plugger for a particular element type, for example: the two methods to add a GetDoubleDelegate are:\nAn example of registering a delegate is:\nCode may be plugged by User Defined Element Type (UDET) as well as the base type. The following criteria are used to locate the right plugged code:\nfor example: you could add three delegates to calculate :WEIGHT. You could add one that calculates the :WEIGHT on a :MYELE, one that calculates the :WEIGHT of SCTN and one that calculates WEIGHT for any other element for which :WEIGHT is valid.\nA delegate only needs adding once at start up.\nThe events do not allow for errors. Thus if the value can not be calculated then the pseudo attribute code should return a sensible default.\npublic delegate double GetDoubleDelegate(DbElement ele, DbAttribute att, int qualifier);\n   \n// Double delegate for UDA\nstatic private double VolumeCalculation(DbElement ele,DbAttribute\n   \n                         att,int qualifier)\n{\n // calculate the volume by multiplying the lengths along each side\n double x=ele.GetDouble(ATT.XLEN);\n   \n double y=ele.GetDouble(ATT.YLEN);\n   \n double z=ele.GetDouble(ATT.ZLEN);\n   \n // Result of UDA must be returned\n return (x * y * z);\n   \n}\npublic static void AddGetDoubleAttribute(DbAttribute att,GetIntDelegate plug)\n   \npublic static void AddGetDoubleAttribute(DbAttribute att, DbElementType type, GetIntDelegate plug)\n   \nusing System;\n   \nusing NOUN=Aveva.Core.Database.DbElementTypeInstance;\n   \nusing Ps=Aveva.Core.Database.DbPseudoAttribute;\n   \nnamespace Aveva.Core.Shared.Tests\n   \n{\n static public void RegisterDelegate()\n   \n {\n   \n  // get uda attribute\n  DbAttribute uda=DbAttribute.GetDbAttribute(\":VOLUME\");\n   \n  // Create instance of delegate containing \"VolumeCalculation\" method\n  Ps.GetDoubleDelegate dele=new Ps.GetDoubleDelegate(VolumeCal\\-culation);\n   \n  // Pass delegate instance to core PDMS. This will be invoked later\n     // when :VOLUME is queried.\n      // In this case registry for all valid element types.\n  Ps.AddGetDoubleAttribute(uda,dele);\n   \n   }\n   \n}\n\n\n\npublic delegate\n'GetDoubleDelegate'\nDbElement\nDbAttribute\n// Double delegate for UDA\nstatic private double\n \n// calculate the volume by multiplying the lengths along each side\n \ndouble\n \ndouble\n \ndouble\n \n// Result of UDA must be returned\n \nreturn\nGetDoubleDelegate\npublic static void\npublic static void\n \n \nusing\nusing\nusing\nnamespace\n \nstatic public void\n \n  \n// get uda attribute\n  \n  \n// Create instance of delegate containing \"VolumeCalculation\" method\n  \n=new\n  \n// Pass delegate instance to core PDMS. This will be invoked later\n     // when :VOLUME is queried.\n      // In this case registry for all valid element types.\n  \n  "}
{"Headers": "pre actions and post action", "Content": "The following events can be captured:\nExcept for quit, the pre actions are really called post action but with the Database (DB) in the pre action state. The pre action is only called if the action succeeds.\nMost of the pre and post actions fall into just two categories:\nThe interested parties are different in the two cases. When changing the database file, the interested parties are 3rd party systems outside of the AVEVA module. When changing our view of the database it is the current session that needs to reflect the changes, for example: update the 3D graphics and explorer.\nThe events raised reflect this split.\nThe events are:\nCommitPending - This is called to commit any outstanding change to the database. It is called prior to setmark, undo, redo, Savework, quit, Getwork.\nClearCache() - This will be called after doing a temporary switch to a different session in a DB, or after doing a Getwork, undo, redo, quit.\nCommitPending - This is called to commit any outstanding change to the database. It is called prior to setmark, undo, redo, Savework, quit, Getwork.\nCommitPending - This is called to commit any outstanding change to the database. It is called prior to setmark, undo, redo, Savework, quit, Getwork.\nClearCache() - This will be called after doing a temporary switch to a different session in a DB, or after doing a Getwork, undo, redo, quit.\nClearCache() - This will be called after doing a temporary switch to a different session in a DB, or after doing a Getwork, undo, redo, quit.\nPre and Post events for local changes. i.e. changes affecting the current view of the data. These will be Getwork, undo, redo.\nPre and Post events for changes affecting the data on the DB. These will be Savework, refresh, drop, flush, refresh. These will pass the list of changes. For 'global' DBs, if the parent extract is at a different location, the flush event will be raised by the child extract.\nPre and Post events for local changes. i.e. changes affecting the current view of the data. These will be Getwork, undo, redo.\nPre and Post events for local changes. i.e. changes affecting the current view of the data. These will be Getwork, undo, redo.\nPre and Post events for changes affecting the data on the DB. These will be Savework, refresh, drop, flush, refresh. These will pass the list of changes. For 'global' DBs, if the parent extract is at a different location, the flush event will be raised by the child extract.\nPre and Post events for changes affecting the data on the DB. These will be Savework, refresh, drop, flush, refresh. These will pass the list of changes. For 'global' DBs, if the parent extract is at a different location, the flush event will be raised by the child extract.\nPost claim/release events\nPost failed Getwork/Savework\nPost claim/release events\nPost claim/release events\nPost failed Getwork/Savework\nPost failed Getwork/Savework\nNote:\nClearCache may be called thousands of times within a single operation. Thus any event handlers must be fast.\nNote:\nIn this case the flush could still fail at the parent. Alternatively the daemon needs to raise the flush event.\n\n\n\nCommitPending\nClearCache()\nNote\n:\n\nClearCache\nNote\n:"}
{"Headers": "Units", "Content": "Real dimensioned quantities may be created or returned as objects of type DbDouble which have a dimension, DbDoubleDimension, current units, DbDoubleUnits, and a real value which may be presented as a string using a format object, DbFormat. Standard dimensions and units are defined by the enumerated types DbDimension and DbUnits returned by DbDoubleDimension and DbDoubleUnits respectively. The DbElement Get/Set interface supports both undimensioned and dimensioned attributes which may be formatted using the DbFormat object. The following classes are available in the Aveva.Core.Database interface.\n\n\n"}
{"Headers": "Represents a standard or compound unit constructed via static constructors", "Content": "Represents a standard or compound unit constructed via static constructors. For example, construct a compound unit from an expression\nor construct a standard unit from a standard enumeration\nThere is a static method to get all the defined standard and compound units\nand properties to get the description, dimension, conversion factor etc. For example, get the dimension of given units\nDbDoubleUnits u1 = DbDoubleUnits.GetUnits(\"kg.m.s-2\");\n   \nDbDoubleUnits u1 = DbDoubleUnits.GetUnits(DbUnits.MM);\n   \nDbDoubleUnits[] units = DbDoubleUnits.AllUnits();\n   \nDbDimension d1 = DbDoubleUnits.GetUnits(DbUnits.MM).Dimension;\n   \n\n\n\nDbDoubleUnits\nDbDoubleUnits\nkg.m.s-2\nDbDoubleUnits\nDbDoubleUnits\n(\nDbUnits\nDbDoubleUnits\nDbDoubleUnits\nDbDimension\nDbDoubleUnits\n(\nDbUnits"}
{"Headers": "Enumeration fo standard units", "Content": "Enumeration of standard units. For example:\nDbUnits.KG\n   \n\n\n\nDbUnits"}
{"Headers": "Represents a standard or compound dimension constructed via static constructors", "Content": "Represents a standard or compound dimension constructed via static constructors. For example, construct a compound dimension from an expression\nor construct a standard dimension from a standard enumeration\nThere are properties to get the current units for given dimension, all units for given dimension etc. For example, get all the units of given dimension\nDbAttribute also has a property, Dimension, which returns the dimension of given attribute. For example,\nDbDoubleDimension d1 = DbDoubleDimension.GetDimension(\"volt/m\");\n   \nDbDoubleDimension d1 = DbDoubleDimension.GetDimension(DbDimension.DIST);\n   \nDbDoubleDimension mass = DbDoubleDimension.GetDimension(DbDimension.MASS);\n   \nDbDoubleUnits[] massUnits = mass.Units;\n   \nDbAttribute ud1 = DbAttribute.GetDbAttribute(\":UD1\");\n   \nDbDoubleDimension dimension = ud1.Dimension;\n   \n\n\n\nDbDoubleDimension\nDbDoubleDimension\nvolt/m\nDbDoubleDimension\nDbDoubleDimension\nDbDimension\nDbDoubleDimension\nDbDoubleDimension\nDbDimension\nDbDoubleUnits\nDbAttribute\nDbAttribute\n:UD1\nDbDoubleDimension"}
{"Headers": "Enumeration fo standard dimensions", "Content": "Enumeration of standard dimensions. For example\nDbDimension.MASS\n   \n\n\n\nDbDimension"}
{"Headers": "Represents a real dimensioned quantity", "Content": "Represents a real dimensioned quantity which can be constructed from an expression and/or a format or returned from DbElement. For example, create a DbDouble from a real value\nor create a DbDouble from a string expression\nor get a dimensioned attribute from DbElement as a DbDouble\nDbDouble's may also be used to set dimensioned attributes. For example, setting the HBOR of a branch\nQuantities of dimension BORE may be created as follows from a real value\nor a string expression and a format\nreturning the nearest nominal bore depending on the current BORE units. There are also properties to return the units, dimension etc. For example, get the units of given DbDouble\nTo return a formatted string, For example\nand to convert to different units\nDbDouble also implements the expected binary operator overloads '+', '-', '\\', '*', '==', '!=', '<', '<=', '>' and '>=' allowing arithmetic operations and comparison of dimensioned quantities. For example, adding 2 quantities of the same dimension together\nDbDouble d1 = DbDouble.Create(1.0);\n   \nDbDouble d1 = DbDouble.Create(\"1.0kg\");\n   \nDbElement bran = DbElement.GetElement(\"/100-B-1-B1\");\n   \nDbDouble hbor = bran.GetDbDouble(DbAttributeInstance.HBOR);\n   \nDbElement bran = DbElement.GetElement(\"/100-B-1-B1\");\n   \nDbDouble hbor = DbDouble.Create(\"300\", fbore)\n   \nbran.SetAttribute(DbAttributeInstance.HBOR, hbor);\n   \nDbDouble bore = DbDouble.CreateBore(300);\n   \nDbFormat fbore = DbFormat.Create();\n   \nfbore.Dimension = DbDoubleDimension.GetDimension(DbDimension.DIST);\n   \nfbore.Units = DbDoubleUnits.GetUnits(DbUnits.FINC);\nDbDouble bore = DbDouble.CreateBore(\"12\", fbore);\n   \nDbDouble d1 = DbDouble.Create(\"2m\");\n   \nDbDoubleUnits u1 = d1.Units;\n   \nDbFormat ftemp = DbFormat.Create();\n   \nftemp.Dimension = DbDoubleDimension.GetDimension(DbDimension.TEMP);\n   \nftemp.Units = DbDoubleUnits.GetUnits(\"degRankine\");\n   \nftemp.Label = \"degRan\";\n   \nDbDouble t1 = DbDouble.Create(\"3 celsius\");\n   \nString tempStr = t1.ToString(ftemp);\n   \nDbDouble d1 = DbDouble.Create(\"1kg\");\n   \nDbDouble d2 = d1.ConvertUnits(DbDoubleUnits.GetUnits(DbUnits.LB));\n   \nd1 = DbDouble.Create(\"1 kg\");\n   \nd2 = DbDouble.Create(\"2.2046 lb\");\n   \nd3 = d1 + d2;\n\n\n\nDbDouble\nDbDouble\nDbDouble\nDbDouble\n1.0kg\nDbElement\nDbElement\n/100-B-1-B1\nDbDouble\n(\nDbAttributeInstance\nDbElement\nDbElement\n/100-B-1-B1\nDbDouble\nDbDouble\n300\n(\nDbAttributeInstance\nDbDouble\nDbDouble\n300\nDbFormat\nDbFormat\nDbDoubleDimension\nDbDimension\nDbDouble\nDbDouble\n12\nDbDouble\nDbDouble\n2m\nDbDoubleUnits u1\nDbFormat\nDbFormat\nDbDoubleDimension\nDbDimension\nDbDoubleUnits\ndegRankine\ndegRan\nDbDouble\nDbDouble\n3 celsius\nString\nDbDouble\nDbDouble\nDbDouble\nDbDoubleUnits\n(\nDbUnits\nDbDouble\n1 kg\nDbDouble\n2.2046 lb"}
{"Headers": "Arithmetic errors", "Content": "Arithmetic errors or errors constructing DbDouble's will throw a PdmsException containing the error message. For example, adding 2 quantities of different dimensions together will throw a PdmsException which can be caught\nd1 = DbDouble.Create(\"1 kg\");\n   \nd2 = DbDouble.Create(\"2 mm\");\n   \ntry\n{\n   d3 = d1 + d2;\n}\ncatch (PdmsException ex)\n   \n{\n  \n}\n\n\n\nDbDouble\n1 kg\nDbDouble\n2 mm\ntry\ncatch \n(\nPdmsException\n "}
{"Headers": "formatting of DbDouble's as a string having properties", "Content": "This object allows formatting of DbDouble's as a string having properties to set the dimension, decimal points, label etc. For example, formatting a temperature\nor constructing a DbDouble from a string and given format\nA DbFormat object has a property that is a pointer to another DbFormat. This format will be used (delegated to) in toString type operations if the value produce by the current DbFormat is less than one.\nDelegation can continue along a chain formatting the quantity to ever smaller units. All these format objects must be consistent dimension and progressively smaller units.\nt1 = DbDouble.Create(\"0 celsius\");\n   \nDbFormat tempFmt = DbFormat.Create();\n   \ntempFmt.Dimension = DbDoubleDimension.GetDimension(DbDimension.TEMP);\n   \ntempFmt.Units = DbDoubleUnits.GetUnits(DbUnits.CELSIUS);\n   \ntempFmt.DecimalPoints = 1;\ntempFmt.Label = \"degC\";\nstring tempStr = t1.ToString(tempFmt);\n   \nDbFormat f1 = DbFormat.Create();\n   \nf1.Dimension = DbDoubleDimension.GetDimension(DbDimension.DIST);\n   \nf1.Units = DbDoubleUnits.GetUnits(DbUnits.INCH);\n   \nDbDouble d1 = DbDouble.Create(\"1\", f1);\n   \n\n\n\nDbDouble\n0 celsius\"\nDbFormat\nDbFormat\nDbDoubleDimension\n(\nDbDimension\nDbDoubleUnits\nDbUnits\nstring\nDbFormat\nDbFormat\nDbDoubleDimension\n.GetDimensio\nDbDimension\nDbDoubleUnits\n(\nDbUnits\nDbDouble\nDbDouble"}
{"Headers": " PML .NET allows you to instantiate and invoke methods", "Content": "Programmable Macro Language (PML) .NET allows you to instantiate and invoke methods on .NET objects from PML proxy objects. PML proxy class definitions are created from .NET class definitions at run time. These proxy classes present the same methods as the .NET class which are described using custom attributes. Proxy methods are passed arguments of known types which are marshalled to the corresponding method on to the .NET instance. The PML proxy objects behave just like any other PML object.\n\n\n"}
{"Headers": "Design Details", "Content": "Programmable Macro Language (PML) callable assemblies are loaded by the AVEVA module using the IMPORT syntax. Assemblies may be defined in potentially any .NET language, for example managed C++, C# or VB.NET. The PML.NET Engine loads a given assembly using reflection. The assembly may be located in the %AVEVA_DESIGN_EXE% directory, a subdirectory below %AVEVA_DESIGN_EXE% a mapped drive or on a UNC path. When the assembly is loaded PML class definitions are created for each PML callable class within the assembly. The PML.Net Engine only loads assemblies which are marked with the custom attribute PMLNetCallable. Only classes and methods which are marked as PMLNetCallable are considered. In order to create a valid PML Proxy class definition the .NET class and its methods must adhere to certain rules. Once an assembly has been loaded instances of PMLNetCallable classes may be created. No additional code to interface between PML and .NET is necessary. This is provided by the PMLNetEngine.\n\n\n"}
{"Headers": "Customize AVEVA modules by PML.NET", "Content": "The diagram below shows how AVEVA modules may be customized using PML.NET. A number of .NET API's are available which allow access to the current database session, drawlist, geometry and other functionality. Users are able to write their own managed code which accesses the AVEVA module via these C# API's. It is not possible to directly call PML from C#. However there is an event mechanism which allows PML to subscribe to events raised from C# (these are shown in dashed lines below). Events are also raised when the database changes and can be subscribed to from C# (also shown in dashed lines). In this example the external C# assemblies share the same database session as Design i.e. they run in the same process and therefore see the same data.\n\nFor example: the sequence:\nwill give an error.\nIn order to identify and load a particular class definition the PML proxy class is assumed to have the same name as the .NET class (PML callable classes must be case independent). This class name is passed to the PMLNetEngine which creates the .NET instance.\nFor example:\ncreates an instance of the .NET class netobject. To specify in which assembly this class is defined and resolve any name clashes the user needs to also specify the namespace in which the .NET class is defined using the following syntax:\nWhere <string> is the namespace in which the class is defined.\nFor example:\nThe namespace is considered to be case independent. This namespace will remain current until it goes out of scope, for example: at end of macro. When the user types:\nthen all namespaces in the current scope will be searched to find a match. In this example, if 'Aveva.Core. PMLNetExample' is not currently in scope, then the error:\nwill be raised.\nObject names can consist of any alpha but not numeric characters (this restriction is imposed by PML). They are treated as case-independent. However, it is no longer necessary to define them in upper case - any mixture of upper and lower case letters will have the same effect.\nThe query methods on an object have been enhanced as follows:\n(a) Querying an object will show the namespace name as well as the object name:\nFor example:\n(b) There is a new query method to list all the methods of an object (including constructors)\nFor example:\n(c) A new query:\nlists the namespaces currently in scope.\nThere is a new global method on all objects:\nwhich returns a list of the methods on the object as an array of strings.\nFor example:\nreturns:\nBefore an instance of a .NET object can be instantiated the assembly containing the class definition must be loaded. This is done using the IMPORT syntax as follows\nWhere <string> is the case-independent name of the assembly\nOnly PML variables of the following types may be passed to methods on .NET classes. In the table below the PML variable type is in the left column and the .NET equivalent variable type is in the right column. Data is marshalled in both directions between PML and .NET by the PMLNetEngine.\nREAL\ndouble\nSTRING\nstring\nBOOLEAN\nbool\nARRAY (these can be sparse and multi-dimensional)\nHashtable - The Key must be numeric (integer of double) to match the PML Array index which is always REAL. An error will be raised during execution if this is not the case.\nOBJECT Any existing PML.NET instance\nPMLNetCallable class\nArguments to PML Proxy methods are passed by reference so can be in/out parameters (in .NET output arguments must be passed by reference).\nPML Gadgets and DB elements have reference semantics when they are copied whereas all other objects have value semantics when they are copied. This is controlled by the Assign() method on the .NET class. So, for example if the Assign() method here copies the value then\nfor example, !a and !b do not point to the same object.\nIn order to perform either a shallow or deep copy of the member data inside the .NET class the Assign() method must be defined on the .NET class (see rules). This is analogous to overriding the operator \"=\" in C++.\nOverloading of methods is supported for all variable types in PML so a .NET Proxy can be created from a .NET class which has overloaded methods.\nThe custom attribute [PMLNetCallable()] is used to describe the PML interface for a .NET class. This metadata allows the PML callable assemblies to be self-describing. This clearly defines the class and allows an assembly to expose a subset of its public interface to PML. The PMLNetEngine uses this metadata to decide which .NET class definitions can be created in PML. Reflection is used to load an assembly and create PML class definitions. All classes and methods for which PML Proxy class definitions will be created must be marked as PMLNetCallable. The assembly itself must also be marked as PMLNetCallable.\nSo, a PML callable .NET class in C# looks like this:\nThis class has a default constructor and a single method. Both the constructor and method are marked as PMLNetCallable along with the class itself.\nThe assembly itself must also be marked as PMLNetCallable. This is normally done in the AssemblyInfo file as follows\nIn PML there is no concept of private members or methods - everything is public. Access to public data in .NET must be via properties or get/set accessor methods. Properties in .NET class are defined as get and set methods in PML. So, for example the following PMLNetCallable property in .NET\nwould have the following Proxy methods in PML\nPML variables are of two kinds: global and local. Global variables last for a whole session (or until you delete them). A local variable can be used only from within one PML function or macro. The lifetime of the .NET instance is controlled by the scope of the PML proxy.\nClasses can have any number of overloaded constructors but must have a default constructor which is marked as PMLNetCallable. The PML Proxy constructor instantiates an instance of the underlying .NET class. When the proxy goes out of scope the destructor destroys the underlying .NET instance.\nThe string() method is available on all PML objects. For a .NET Proxy this will call the ToString() method on the .NET instance. If the ToString() method is overridden on the .NET class then this will be called.\nPML is case independent, so it is not possible to have MyMethod() and MYMETHOD() in .NET. PML will report non-unique object/method names.\nDoubles are used in PML.NET to store reals and ints so doubles must be used in .NET (integers are not available in PML)\nEvents on PML.NET objects may be subscribed to from PML. A PML callback on a particular instance may be added to an event on another PML.NET instance. Events are defined by a .NET component by associating the delegate PMLNetEventHandler with the event. This delegate has the signature\nWhere args is an array of event arguments of any PML.NET type (see table of valid types). The following code associates this delegate with an event\nThis event can then be caught in Programmable Macro Language (PML) by adding an appropriate callback to the instance raising the event\nWhere\nAt some later time the event handler may be removed\nwhere !handle is the handle of the PML.NET delegate returned by addeventhandler().\nNetcallback is a PML object defined as\nException handling is placed around the Invoke method to handle .NET method invocation exceptions like TargetException, ArgumentException etc. The result of catching such an exception is to ultimately return a PMLError object from PMLNetProxy::Invoke() which results in a PML exception (1000,n) being thrown where 1000 is the module number for PML.NET. .NET can throw its own PML exceptions. The exception to throw is PMLNetException. For example\nThis may then be handled inside a PML macro i.e.\nAny other exception within the loaded assembly itself is caught by the global exception handler inside the AVEVA module.\nCertain rules must be adhered to when defining a .NET class which is PML callable. These are enforced by the PMLNetEngine when an assembly is imported. They are\nIf these rules are not adhered to then errors are reported to the trace log when the assembly is loaded and a PML class definition will not be created. If the class definition has not been defined then the following PML error will result\nIn order to output trace to a log file and the console window add the following lines to the exe's config file\nThis will create the file PMLNetTrace.log in C:\\temp and log all the valid class definitions as they are imported.\n USING NAMESPACE \u2018Aveva.Core\u2019\n   \n !netobj = object namespace.NETObject ( )\n!a = object netobject()\nUSING NAMESPACE <string>\n'Aveva.Core.PMLNetExample'\n!netobj = object  NetObject ( )\n (46,87)   PML: Object definition for NETOBJECT could not be found.\n q  var !x\n\n < Aveva.Core.NAMESPACE.NETOBJECT>\nAveva.Core.NAMESPACE.NETOBJECT\n Q METH/ODS\nq meth !x\n\n\n<Aveva.Core.NAMESPACE.NETOBJECT>Aveva.Core.NAMESPACE.NETOBJECT\n          NETOBJECT ( )\n          NETOBJECT (REAL)\n          ADD (REAL)\n          REMOVE(REAL)\n          ASSIGN(Aveva.Core.NAMESPACE.NETOBJECT)\n          DOSOMETHING(REAL, REAL, REAL)\nQ NAMESP/ACES\n    .methods()\n   !arr = !x.methods()\n   q var !x\n<ARRAY>\n [1] <STRING> 'NETOBJECT ( )'\n [2] <STRING> 'NETOBJECT (REAL)'\n [3] <STRING> 'ADD (REAL)'\n [4] <STRING> 'REMOVE(REAL)'\n [5] <STRING> 'ASSIGN(Aveva.Core.NAMESPACE.NETOBJECT)'\n [6] <STRING> 'DOSOMETHING(REAL, REAL, REAL)'\nIMPORT <string>\n!a = object netobject()\n!a.val(1)\n!b = !a\n!b.val(2)\nthen\nq var !a.val() returns 1\nand\nq var !b.val() returns 2\n[PMLNetCallable()]\nnamespace PMLNet\n{\n    [PMLNetCallable ()]\n    public class PMLNetExample\n    {\n        [PMLNetCallable ()]\n        public PMLNetExample()\n        {\n       \n        }\n        [PMLNetCallable ()]\n        public void DoSomething(double x, double y, double z)\n        {\n             z = x + y;\n        }\n    }\n}\nusing Aveva.Core.PMLNet;\n   \n[assembly: PMLNetCallable()]\n[PMLNetCallable()]\npublic double Val\n   \n{\n   get\n   {\n      return mval;\n   \n   }\n   set\n   {\n   \n      mval = value;\n   }\n   \n}\nREAL VAL()\nVAL(REAL)\n__delegate void PMLNetEventHandler(ArrayList __gc *args);\n   \n[PMLNetCallable()]\npublic class PMLNetExample\n   \n{\n[PMLNetCallable()]\npublic event PMLNetDelegate.PMLNetEventHandler PMLNetExampleEvent;\n   \n [PMLNetCallable()]\n public PMLNetExample ()\n   \n {\n }\n [PMLNetCallable()]\n public void Assign(PMLNetExample that)\n   \n {\n    }\n [PMLNetCallable()]\n public void RaiseExampleEvent()\n   \n {\n     ArrayList args = new ArrayList();\n   \n           args.Add(\"PMLNetExampleEvent \");\n           args.Add(\"A\");\n           if (PMLNetExampleEvent!= null)\n               PMLNetExampleEvent(args);\n   \n      }\n}\n!n = object pmlnetexample()\n!c = object netcallback()\n!handle = !n.addeventhandler('pmlnetexampleevent', !c, 'callback')\n!n.removeeventhandler('pmlnetexampleevent', !handle)\ndefine method .callback(!array is ARRAY)\n !args = 'NETCALLBACK object ' + !array[0] + !array[1]\n $P $!args\nendmethod\nthrow new PMLNetException(1000, 1, \"PMLNetExample Exception\");\n   \nhandle(1000,1)\n\u2026\nendhandle\n(46,87)   PML: Object definition for XXX could not be found.\n<system.diagnostics>\n       <switches>\n          <add name=\"PMLNetTraceSwitch\" value=\"4\" />\n       </switches>\n  </system.diagnostics>\n<appSettings>\n        <add key=\"PMLNetTraceLog\" value=\"C:\\temp\\PMLNetTrace.log\" />\n</appSettings>\nOnly .NET classes which are marked as PMLNetCallable and adhere to certain rules can be called from PML (these rules are described later)\nModule switching does not persist .NET objects. Core PML objects defined in FORTRAN or C++ are not persisted either.\nPassing other PML system/user objects to .NET, for example: DIRECTION, ORIENTATION, \u2026 is not possible. It is possible to pass database references to .NET either as an array or String. It is also possible to pass an existing instance of a PML.NET Proxy to .NET.\nIt is not possible to call directly PML objects from .NET. The only way to call PML from .NET is via events.\nIt is not possible to enter 'partial' namespaces as you might in C# and expect them to be concatenated.\nOnly .NET classes which are marked as PMLNetCallable and adhere to certain rules can be called from PML (these rules are described later)\nOnly .NET classes which are marked as PMLNetCallable and adhere to certain rules can be called from PML (these rules are described later)\nModule switching does not persist .NET objects. Core PML objects defined in FORTRAN or C++ are not persisted either.\nModule switching does not persist .NET objects. Core PML objects defined in FORTRAN or C++ are not persisted either.\nPassing other PML system/user objects to .NET, for example: DIRECTION, ORIENTATION, \u2026 is not possible. It is possible to pass database references to .NET either as an array or String. It is also possible to pass an existing instance of a PML.NET Proxy to .NET.\nPassing other PML system/user objects to .NET, for example: DIRECTION, ORIENTATION, \u2026 is not possible. It is possible to pass database references to .NET either as an array or String. It is also possible to pass an existing instance of a PML.NET Proxy to .NET.\nIt is not possible to call directly PML objects from .NET. The only way to call PML from .NET is via events.\nIt is not possible to call directly PML objects from .NET. The only way to call PML from .NET is via events.\nIt is not possible to enter 'partial' namespaces as you might in C# and expect them to be concatenated.\nIt is not possible to enter 'partial' namespaces as you might in C# and expect them to be concatenated.\n!n is the PML.NET instance on which the event will be raised\n!c is the instance of a PML object with a method callback() with the appropriate arguments\n!n is the PML.NET instance on which the event will be raised\n!n is the PML.NET instance on which the event will be raised\n!c is the instance of a PML object with a method callback() with the appropriate arguments\n!c is the instance of a PML object with a method callback() with the appropriate arguments\nPML callable assemblies must be marked as PMLNetCallable and reside in the %AVEVA_DESIGN_EXE% directory, subdirectory of the application or UNC path.\nOnly classes may be PML Callable (this excludes Structures, Interfaces, Enums, \u2026).\nA PML callable class must be marked as PMLNetCallable.\nA PML callable method must be marked as PMLNetCallable.\nA PML callable method can only pass valid argument types (see table of types).\nPML callable classes and methods must be public.\nPML callable methods with default arguments cannot be defined.\nPML callable class and method names must be case independent.\nPML callable classes must have an Assign() method.\nPML callable classes must have a public default constructor which is PMLNetCallable.\nPML callable assemblies must be marked as PMLNetCallable and reside in the %AVEVA_DESIGN_EXE% directory, subdirectory of the application or UNC path.\nPML callable assemblies must be marked as PMLNetCallable and reside in the %AVEVA_DESIGN_EXE% directory, subdirectory of the application or UNC path.\nOnly classes may be PML Callable (this excludes Structures, Interfaces, Enums, \u2026).\nOnly classes may be PML Callable (this excludes Structures, Interfaces, Enums, \u2026).\nA PML callable class must be marked as PMLNetCallable.\nA PML callable class must be marked as PMLNetCallable.\nA PML callable method must be marked as PMLNetCallable.\nA PML callable method must be marked as PMLNetCallable.\nA PML callable method can only pass valid argument types (see table of types).\nA PML callable method can only pass valid argument types (see table of types).\nPML callable classes and methods must be public.\nPML callable classes and methods must be public.\nPML callable methods with default arguments cannot be defined.\nPML callable methods with default arguments cannot be defined.\nPML callable class and method names must be case independent.\nPML callable class and method names must be case independent.\nPML callable classes must have an Assign() method.\nPML callable classes must have an Assign() method.\nPML callable classes must have a public default constructor which is PMLNetCallable.\nPML callable classes must have a public default constructor which is PMLNetCallable.\nNote:\nQuery methods will not list the methods on objects of type ANY, even though such methods are available on all objects.\n\n\n\n \nNote\n:\ndo not\nusing\n[PMLNetCallable()]\npublic double\n   get\n   {\n      return\n   set\n   \nvalue\n;\n  \nToString() Method\ndelegate void\n__gc\npublic class\npublic event\n \npublic\n \npublic void\n \npublic void\n= new\n           \nif\nnull\n)\n               \n!n\n!c\n!handle\nthrow new"}
{"Headers": ".NET controls can be hosted on a pml form", "Content": ".NET controls can be hosted on a PML form. In order to do this PML provides a container gadget which can host the control. This container gadget has attributes to set and get its size and position and may be added to any PML defined form. It has similar behaviour to a Frame gadget in terms of docking, anchoring and positioning within an owning form. An instance of the .NET control is instantiated from PML. The PML container provides a method to add an instance of a .NET control to it. The .NET control may raise events which may be handled by PML. In order to customise the context menus of the .NET control from PML the ability to define a PML menu which can be shown when the .NET control raises an event is provided.\nA container on a form that can host the .NET control can be created in the following way in the form setup\nwhich can be docked and positioned.\nThe control may be added to the container by setting the container's control to the .NET control's handle.\nEvents on the control are supported by PML delegates already described. These allow you to add popup menus to the control for example. Events may be subscribed to by adding an event handler as follows to the .NET control\nwhere the method to call when the event is fired is defined as follows\nand the menu shown by the method which is added to the container is defined as follows\ncontainer .exampleContainer PmlNetControl 'example' dock fill width 30 height 20\nusing namespace 'Aveva.Core.Presentation'\n!this.exampleControl = object PMLNetExampleControl()\n!this.exampleContainer.control = !this.exampleControl.handle()\n!this. exampleControl.addeventhandler('OnPopup', !this,\n 'rightClickGrid')\ndefine method .rightClickGrid(!data is ARRAY)\n  !this.exampleContainer.popup = !this.examplePopup\n   \n  !this.exampleContainer.showPopup(!data[0], !data[1])\nendmethod\nmenu .examplePopup popup\n   !this.examplePopup.add( 'CALLBACK', 'Add to 3D View',\n'!this.addToThreeDView()' )\n\n\n\ndefine method .rightClickGrid(!data is ARRAY)\n "}
{"Headers": "Example of a .NET grid hosted", "Content": "The following examples are available in the Samples directory -\nExample of a .NET grid hosted on a PML form\nExample of a PML Callable assembly:\nExample of how to use the new object:\nList available methods:\ncall the example method:\n\nimport |pmlnetexample|\nusing namespace |aveva.core.samples|\n!pmlobj = object pmlnetexample()\nq var !pmlobj.methods()\n!pmlobj.method()\nImport |C:\\%path-to-samples%\\PMLNetExample\\bin\\Debug\\pmlnetexample|\nNote:\nThe module can be loaded from a directory:\n\n\n\nNote\n:"}
{"Headers": "Use an instance of an AVEVA C# Grid Control on a C# form", "Content": "This section describes how to use an instance of an AVEVA C# Grid Control on a C# form. The example which is used in this documentation is supplied with the product. The Visual Studio project, NetGridExample, containing the source code is located in the samples.zip file.\nNote:\nThat you can only use the AVEVA C# Grid Control on your own Visual Studio form if you have a design time license for Infragistics.\nNote:\nThat you can run this C# Addin with the AVEVA module without having an Infragistics license.\n\n\n\nNote\n:\nNote\n:"}
{"Headers": "Create a C# Addin which Contains an AVEVA Grid Control", "Content": "The supplied C# project is an example of a C# addin for use with AVEVA Plant/AVEVA Marine. The C# addin includes an AVEVA C# Grid Control and some other Visual Studio WinForms gadgets to demonstrate how the Grid Control can be used with AVEVA Plant/AVEVA Marine.\nThe addin creates the docked window shown below when run within the AVEVA Plant/AVEVA Marine Design module.\n\nThe example C# code collects all the Equipment items within the current project and lists them inside the grid along with attribute values for Name, Type, and Owner.\nThe data in the grid can be selected, sorted and filtered.\n\nAnd the other menu is available from the header bar at the top of the grid:\n\nNote:\nThe following features of the example addin. These features make use of the published Grid Control API (see the section below entitled \"AVEVA Grid Control API\").\nNote:\nThat these menu options will only become available once you have made some modifications to the Design.uic file through menu customization. See below for instructions on how to do this.\n\n\n\nNote\n:\nNote\n:"}
{"Headers": "Provide Access to the Addin in Design", "Content": "In order to see the addin inside Design you will need to do the following:\n!menu.add('TOGGLE', 'My Data',   '',   'My Data')\n!menu.add('TOGGLE', 'Reference List', '',   'Reference List')\n!menu.add('TOGGLE', 'Attributes Utility', '',   'Attributes Utility')\n!menu.add('TOGGLE', 'Search Utility', '',   'Find Utility')\n!menu.add('TOGGLE', 'Search Results', '',   'Output Utility')\n!menu.add('TOGGLE',    'New Addin',  '',    'New Addin')\nNote:\nYou can also create your own toolbar which contained a menu item to open/close the addin.\n\n\n\nDisplay\n!menu.add('TOGGLE',    'New Addin',  '',    'New Addin')\nNote\n:"}
{"Headers": "Use the AVEVA Grid Control with Different Data Sources", "Content": "The supplied C# addin populates the grid with database items and their attribute values.\nThe following data sources are available for this method of working. Refer to the AVEVA Grid Control API section below for further information.\nThere are two other ways that an instance of the grid can be populated with data:\nMore specific control of grid columns can be made with use of the ColumnSpecifcation class. An array of ColumnSpecifcations can be used in the construction of the NetDataSource.\nExamples can be found in the PMLGridExample in the Samples directory.\nThe Type property can also be set through the ColumnDataType property as a string. It is important to do this before the data is bound to the grid as columnspecifications are read and values are output around that.\nWith a dabacon data source for the GridControl, if an expression is used (say SEQU OF OWN), the default grid data type is a string, unless defined otherwise on creation of the columnspecification and the expression returns.\nTwo new pmlnetcallable constructors have been made for columnspecifications, to correspond with the new settable property.\nAn example setup in pml would be:\nusing namespace  'Aveva.Core.Presentation'\nnameCol = object COLUMNSPECIFICATION('name', 'name')\n!paramCol = object COLUMNSPECIFICATION('despar 1', 'despar 1', 'real')\n!seqCol = object COLUMNSPECIFICATION('NUM', 'SEQU')\n!sequOwnerCol = object COLUMNSPECIFICATION('NUM OF OWN', 'NUM OF OWN', false, true\n      'integer')\n   \n\n!headingsColumnSpecified    = ARRAY()\n!headingsColumnSpecified[1] = !nameCol\n!headingsColumnSpecified[2] = !paramCol\n!headingsColumnSpecified[3] = !seqCol\n!headingsColumnSpecified[4] = !sequOwnerCol\nNetDataSource(String TableName, Array Attributes, Array Items)\nNetDataSource(String TableName, Array Attributes, Array AttributeTitles, Array Items)\nNetDataSource(String TableName, Array Attributes, Array Items, String Tooltips\nNetDataSource(String TableName, Array Attributes, Array Items)\nNetDataSource(String TableName, Array Attributes, Array Items)\nNetDataSource(String TableName, Array Attributes, Array AttributeTitles, Array Items)\nNetDataSource(String TableName, Array Attributes, Array AttributeTitles, Array Items)\nNetDataSource(String TableName, Array Attributes, Array Items, String Tooltips\nNetDataSource(String TableName, Array Attributes, Array Items, String Tooltips\nThese can be set to integer, double or string. With string being the default. Units and formats are applied on the string datatype of the column.\n\"real\" variables (in pml speak) can be either an integer or a double, however for grid specific properties (sorting, etc.), there is a difference. This is due to the Third Party library being used for grids.\nThese can be set to integer, double or string. With string being the default. Units and formats are applied on the string datatype of the column.\nThese can be set to integer, double or string. With string being the default. Units and formats are applied on the string datatype of the column.\n\"real\" variables (in pml speak) can be either an integer or a double, however for grid specific properties (sorting, etc.), there is a difference. This is due to the Third Party library being used for grids.\n\"real\" variables (in pml speak) can be either an integer or a double, however for grid specific properties (sorting, etc.), there is a difference. This is due to the Third Party library being used for grids.\n\n\n"}
{"Headers": "Add an XML Menu to the Form", "Content": "Code has been added to the supplied addin to allow two different context menus to be used with the grid: a selection menu, and a header menu.\nTo enable this to work with your session you will need to use the Menu Customization utility described earlier in this document.\n\nTo add the menus you will need to do the following in the Menu Customization utility:\nprivate void mCommandBarManager_UILoaded(object sender, EventArgs e)\n         \n  {\n   String contextMenuKey = \"NewAddin.SelectMenu\";\n         \n   if(mCommandBarManager.RootTools.Contains(contextMenuKey))\n   {\n    MenuTool menu = (MenuTool)mCommandBarManager.Root\\-Tools[contextMenuKey];\n    mAddinControl.SelectionMenu = menu;\n   }\n   contextMenuKey = \"NewAddin.HeaderMenu\";\n   if(mCommandBarManager.RootTools.Contains(contextMenuKey))\n   {\n    MenuTool menu = (MenuTool)mCommandBarManager.Root\\-Tools[contextMenuKey];\n    mAddinControl.HeaderMenu = menu;\n   }\n}\n\n\n\nprivate void\nobject\nNewAddin.SelectMenu"}
{"Headers": "Add an Event to the Addin", "Content": "There are several events which have been exposed for the AVEVA Grid Control. These are:\nRefer to for Event handling.\nCell data is passed back to the calling application as an array before a change is made in a cell of the grid (This assumes that the grid is in editable mode or bulk editable mode). The fourth argument of the array (Array[3]) can be set to false by the calling application in order to disallow the new value of the cell.\nEvent to alert the user when the value of a cell is changed.\nCopyKeyPressed (Array)\nDeleteKeyPressed (Array)\nThe position of the mousedown, and an array of selected items is passed through to the calling application when the context menu is used on the grid.\nprivate void netGridControl1_AfterSelectChange(System.Collections.ArrayLst args)\n   \n{\n //Print the number of the selected rows in textbox2\n if (args == null)\n   \n {\n  return;\n }\n   \n Hashtable al = new Hashtable();\n   \n al = (Hashtable)args[0];\n if (al == null)\n {\n  return;\n }\n this.textBox2.Text = al.Count.ToString();\n   \n}\nArray[0] is the Row Tag of the cell\nArray[1] is the Column Tag of the cell\nArray[0] is the Row Tag of the cell\nArray[0] is the Row Tag of the cell\nArray[1] is the Column Tag of the cell\nArray[1] is the Column Tag of the cell\nArray[0] is the new value the user typed in\nArray[1] is the Row Tag of the cell\nArray[2] is the Column Tag of the cell\nArray[3] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[4] is a string. If you set Array[3] to \"false\" then this value can be set to give the reason why the new value cannot be allowed. The message will be displayed in the cell tooltip.\nArray[0] is the new value the user typed in\nArray[0] is the new value the user typed in\nArray[1] is the Row Tag of the cell\nArray[1] is the Row Tag of the cell\nArray[2] is the Column Tag of the cell\nArray[2] is the Column Tag of the cell\nArray[3] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[3] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[4] is a string. If you set Array[3] to \"false\" then this value can be set to give the reason why the new value cannot be allowed. The message will be displayed in the cell tooltip.\nArray[4] is a string. If you set Array[3] to \"false\" then this value can be set to give the reason why the new value cannot be allowed. The message will be displayed in the cell tooltip.\nArray[0] the rows to be deleted\nArray[1] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[2] is a string. If you set Array[1] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] the rows to be deleted\nArray[0] the rows to be deleted\nArray[1] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[2] is a string. If you set Array[1] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[2] is a string. If you set Array[1] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is the tag of the row\nArray[1] is a tag of the column\nArray[0] is the tag of the row\nArray[0] is the tag of the row\nArray[1] is a tag of the column\nArray[1] is a tag of the column\nArray[0] is a Boolean. It is true if any columns are in the group by mode.\nArray[0] is a Boolean. It is true if any columns are in the group by mode.\nArray[0] is a Boolean. It is true if any columns are in the group by mode.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is the x coordinate of the current cursor position\nArray[1] is the y coordinate of the current cursor position\nArray[2] contains the ID of each of the selected rows\nArray[0] is the x coordinate of the current cursor position\nArray[0] is the x coordinate of the current cursor position\nArray[1] is the y coordinate of the current cursor position\nArray[1] is the y coordinate of the current cursor position\nArray[2] contains the ID of each of the selected rows\nArray[2] contains the ID of each of the selected rows\nArray[0] is the row tag of the copied row\nArray[1] is the drop index\nArray[2] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[3] is a string. If you set Array[2] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is the row tag of the copied row\nArray[0] is the row tag of the copied row\nArray[1] is the drop index\nArray[1] is the drop index\nArray[2] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[2] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[3] is a string. If you set Array[2] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[3] is a string. If you set Array[2] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is the row tag of the copied row\nArray[1] is the drop index\nArray[2] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[3] is a string. If you set Array[2] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is the row tag of the copied row\nArray[0] is the row tag of the copied row\nArray[1] is the drop index\nArray[1] is the drop index\nArray[2] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[2] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[3] is a string. If you set Array[2] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[3] is a string. If you set Array[2] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[0] is a Boolean. If you set it to \"false\" then the action is cancelled\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nArray[1] is a string. If you set Array[0] to \"false\" then this value can be set to give the reason why the action has been cancelled. The message will be displayed in the cell tooltip.\nNote:\nThis event is the opportunity for the calling code to make a synchronising change to any related data source. In the case where the related data is Dabacon element/attribute data, the BeforeCellUpdate event should arrange for the Dabacon element/attribute to be modified appropriately. A convenient way to do this is to use the NetGridControl.DoDabaconCellUpdate(Array) function to perform the modification. Simply pass the Array to this function as an argument. If the function is unable to perform the modification for any reason the Array[3] and Array[4] values will be set to indicate the problem.\n\n\n\nprivate void\n \nif\nnull\n  \nreturn\n;\n \nnew\nnull\n)\n {\n  \nreturn\n;\n }\n \nthis\n\nNote\n:"}
{"Headers": "Other Functionality Available within the Environment", "Content": "Note:\nThe following additional functionality available with the Addin:\n\n\n\nNote\n:"}
{"Headers": "Use of the C# Grid Control with PML", "Content": "The C# Grid Control can also be used on a PML form. See the PMLGridExample code in the Samples directory.\n\n\n"}
{"Headers": "Grid Control API", "Content": "The following table includes the API calls which have been made available for the Grid Control.\nName\nType\nPurpose\nBindToDataSource(NetDataSource)\n\nBind Grid to NetDataSource.\nBindToDataSource(NetDataSource(Boolean)\n\nBind Grid to NetDataSource.\nBoolean - keepColumnWidths.\nNetDataSource(String TableName, Array Attributes, Array AttributeTitles, Array Elements)\n\nData Source constructor for database Attributes and database elements. The Grid will populate itself with database attribute values. The title of each column is represented by AttributeTitles.\nNetDataSource(String TableName, Array Attributes, Array Elements)\n\nData Source constructor for database Attributes and database elements. The Grid will populate itself with database attribute values.\nNetDataSource(String TableName, Array Attributes, Array Elements, String Tooltips)\n\nData Source constructor for database Attributes and database elements. The Grid will populate itself with database attribute values.\nNetDataSource(String TableName, Array columns, Array of Array of rows)\n\nData Source constructor for column headings, and a set of row data. In this case the grid does NOT populate itself with database attribute values.\nNetDataSource(String TableName, Array columns, Array of Array of rows, String Tooltips)\n\nData Source constructor for column headings, and a set of row data. In this case the grid does NOT populate itself with database attribute values.\nNetDataSource(String TableName, string PathName)\n\nData Source constructor for import of an Excel or CSV File.\nName\nType\nPurpose\nAlignGroupHeaderVertcally(string GroupName, string Align)\n\nVertically align the group header (Bottom, Top, Middle, Default).\nallGridEvents()\n\nQuery whether grid events are on or off\nallGridEvents(Boolean)allGridEvents(Boolean)\n\nSwitch Grid Events On or Off.\nAllowDropInGrid()\n\nQuery AllowDropInGrid.\nAllowDropInGrid(Boolean)\n\nAllow drag/drop in the grid.\nBulkEditableGrid()\n\nQuery BulkEditableGrid.\nBulkEditableGrid(Boolean)\n\nAllow/disallow cells to be bulk editable. Bulk edit mode allows multiple cells to be selected, and Fill down/Fill up operations to be performed. Copy and Paste operations will also apply to multiple cells selected in the same column.\nClearGrid()\n\nRemove data & column headings.\nClearGridData()\n\nRemove all of the row data from the grid.\nColumnExcelFilter()\n\nQuery ColumnExcelFilter.\nColumnExcelFilter(Boolean)\n\nAllow/disallow Excel style filter on columns.\nExcelFilterCaseSensitivity()\n\nQuery ExcelFilterCaseSensitivity.\nExcelFilterCaseSensitivity(Boolean)\n\nSet Excel column filter to be case sensitive or not. Default is TRUE (case sensitive)\nColumnSetup()\n\nDisplay the column setup form.\nColumnSummaries()\n\nQuery columnSummaries.\nColumnSummaries(Boolean)\n\nAllow/disallow Average, Count, etc on numeric columns\ncreateValueList(String Name, Array for List)\n\nCreate a value list for the grid.\nDisplayNulrefAs()\n\nQuery DisplayNumrefAs.\nDisplayNulrefAs(String)\n\nNominate (or query) a text string to be used in grid cells that hold \"Nulref\" reference attribute data.\nDisplayUnsetAs()\n\nQuery DisplayUnsetAs.\nDisplayUnsetAs(String)\n\nNominate (or query) a text string to be used in grid cells that hold \"unset\" attribute data.\nEditableGrid()\n\nQuery EditableGrid\nEditableGrid(Boolean)\n\nAllow/disallow cells to be editable.\nErrorIcon()\n\nQuery ErrorIcon.\nErrorIcon(Boolean)\n\nAllow/disallow the display of the red icon in the cell if an attribute value or expression cannot be computed.\nFeedbackFailColor()\n\nQuery FeedbackFailColor.\nFeedbackFailColor(String)\n\nNominate (or query) the colour used to highlight cells where editing fails.\nFeedbackSuccessColor()\n\nQuery FeedbackSuccessColor\nFeedbackSuccessColor(String)\n\nNominate (or query) the colour used to highlight cells successfully edited.\nFixedHeaders()\n\nQuery FixedHeaders.\nFixedHeaders(Boolean)\n\nAllow/disallow fixed headers. (Useful when scrolling).\nFixedRows()\n\nQuery FixedRows.\nFixedRows(Boolean)\n\nAllow/disallow fixing of rows (Useful when scrolling).\ngetDataSource()\nNetDataSource\nReturns the data source that has been set in the grid.\ngetGroups\n\nReturns list of groups used in grid.\nGetGroupOrigin(string grKey)\n\nReturn the origin of the given group.\nGetGroupSpan(string grKey)\n\nReturn the span of the given group.\nGridHeight()\nReal\nQuery GridHeight.\nGridHeight(Real)\n\nSet the height of the rows in the grid.\ngetParentGroupForGroup(string groupName)\n\nReturns parent's group name for given group.\ngetParentGroupForColumn(string colName)\n\nReturns parent's group name for given column.\nGroupMoving(String)\n\nSet the moving of groups to: Default, NotAllowed, WithinBand or WithinGroup.\nHeaderSort()\n\nQuery HeaderSort.\nHeaderSort(Boolean)\n\nAllow/disallow the user to sort columns.\nHideGroupByBox()\n\nQuery HideGroupByBox.\nHideGroupByBox(Boolean)\n\nHide/show the groupBy box.\nloadFromMemoryStream(object data)\n\nLoad the grid from a stored memory stream.\nloadGridFromXML(string xmlFile)\n\nLoad the grid from an XML file.\nloadGridLayout(object gridLayout)\n\nLoad the stored layout of a grid.\nloadLayoutFromXml(String)\n\nLoad a stored grid layout into the current grid instance.\nOutlookGroupStyle\n\nQuery OutlookGroupStyle.\nOutlookGroupStyle(Boolean)\n\nAllow/disallow the Outlook Group style feature.\nprintPreview()\n\nOpens a Print Preview of the grid instance (which also allows printing).\nQuickReport()\n\nCreate a quick report from the current grid.\nReadOnlyCellColor()\n\nQuery ReadOnlyCellColor.\nReadOnlyCellColor(String)\n\nNominate (or query) the background colour used to indicate cells where editing is not permitted.\nRefreshAllFilters()\n\nRefresh all the filters in the grid.\nRefreshTable()\n\nFor a grid displaying Dabacon data this recalculates the content of every cell to refresh to the latest database state.\nRefreshVisibleRegion()\n\nFor a grid displaying Dabacon data this recalculates the content of every cell in the visible region to refresh to the latest database state.\nresetCellFeedback()\n\nReset the cell editing feedback highlight colour and tooltip text.\nResetColumnProperties()\n\nReset column layout.\nResetGridOrder()\n\nReset the order of the columns in the grid.\nsaveGridToExcel(string excelFile)\n\nSave the grid data to an Excel file.\nsaveGridToExcel(string excelFile, string worksheet)\n\nSave the grid data to a designated worksheet of an Excel file. Note that this will retain all grid groupings and layout of data.\nsaveGridToExcel(string excelFile,string worksheet, string strHeader)\n\nSave the grid data to a designated worksheet of an Excel file. Here strHeader is a user supplied string which is output to the first row in the Excel spreadsheet. The grid data is then output starting in row #2.\nSaveLayoutToXml(String)\n\nSave the grid layout (not data) to a file on the file system.\nsaveToMemoryStream(ref MemoryStream stream)\n\nSave the grid to a memory stream.\nsetAlternateRowColor(Red Num, Green Num, Blue Num)\n\nSet alternate rows of the grid to a different colour. The default is: (251, 251, 255).\nsetAlternateRowColor(String)\n\nSet alternate rows of the grid to a different colour.\nsetLabelVisibility(Boolean)\n\nShow/hide the label which indicates the number of rows in the grid.\nSingleRowSelection()\n\nQuery SingleRowSelection.\nSingleRowSelection(Boolean)\n\nSet grid to single row selection.\nsplitGrid(Boolean)\n\nAllow/disallow the user to split the grid horizontally and vertically.\nSetGroupOrigin(string grKey, Point value)\n\nSet of the {x,y} origin of the given group.\nstoreGridLayout()\n\nStore the layout of the grid.\nSetGroupSpan(string grKey, Point value)\n\nSet of the {x,y} span of the given group.\nSyntaxErrorColor()\n\nQuery SyntaxErrorColor.\nSyntaxErrorColor(String)\n\nNominate (or query) the colour used to highlight cells containing syntactically invalid data.\nWrapColumnHeaders(true)\n\nAllow word wrap in column headers.\nWrapColumnHeaders(false)\n\nDisallow word wrap in column headers.\nName\nType\nPurpose\naddRow(Array)\n\nAdd a single row of data. If the grid is based on database elements then the first element of the array is read. If not, then the Array data represents the data in each cell of the row.\nclearRowSelection()\n\nClear row selection.\ndeleteRows(Array)\n\nDelete one or more rows by row tag.\ndeleteSelectedRows()\n\nDelete selected rows.\nGetFilteredInRows()\nArray\nReturn the rows which are contained in the current filter.\nGetFilteredOutRows()\nArray\nReturn the rows which are not contained in the current filter.\ngetNumberRows()\nReal\nGet the number of rows in the grid.\ngetNumberSelectedRows\nReal\nGet the number of selected rows in the grid.\ngetRow(Real)\n\nGet the row data.\ngetRow(string row)\nArray\nGet the cells in the row with the specified row tag.\ngetRowNumFromTag(string rowTag)\n\nGet the row number from the row tag.\ngetRows()\nArray of Array (rows)\nReturns an array of all the row data.\ngetRowTag(Real)\n\nGet the row tag.\ngetRowTagByListIndex(Real)\n\nGet the row tag by list index.\nGetSelectedRows()\nArray of Array (rows)\nReturns array of selected rows.\nGetSelectedRowColumn(row, column))\n\nGet the row and column of the selected row.\ngetSelectedRowTags()\nArray of row tags\nGet the selected row tags.\ngetVisibleIndexOfRow(string strRowTag)\n\nGet the visible index of the row.\nHasFilteredRows(Boolean)\n\nSet whether the grid has filtered rows.\nisRowVisible(Real)\n\nIs the given row visible.\nMoveRowToPosition(Real, Real)\n\nMove a row to a given position in the grid.\nMoveRowToPosition(String, Real)\n\nMove a row to a given position in the grid.\nMoveSelectedRowsDown()\n\nMove the selected rows down in the grid.\nMoveSelectedRowsUp()\n\nMove the selected rows up in the grid.\nNumberedRows\n\nTrue if numbered rows, false if not.\nreturnSelectedRows(Array)\n\nReturn the selected rows.\nRowAddDeleteGrid()\n\nQuery RowAddDeleteGrid.\nRowAddDeleteGrid(Boolean)\n\nEnable/disable row addition and deletion in the grid.\nScrollSelectedRowToView()\n\nQuery ScrollSelectedRowToView.\nScrollSelectedRowToView(Boolean)\n\nScroll the selected row into view.\nselectAllRows()\n\nSelect all the rows in the grid.\nselectRow(Real)\n\nSelect the given row.\nsetEditableRow(Real, BoolenanBoolean)\n\nSet the given row as editable or not.\nsetRowColor(Real, string strColorcolour)\n\nSet the colour of the row to the named value.\nSetRowColor(string rowTag, string colour)\n\nSet the colour of the row to the named value.\nSetRowColor(string row, real red, real green, real blue)\n\nSet the colour of the row to the RGB value.\nsetRowTooltip(Real, string tooltip)\n\nSet row tooltip to the specified string.\nsetRowTooltip(string row, string tooltip)\n\nSet row tooltip to the specified string.\nsetRowVisibility(Real, Boolean)\n\nSet the visibility of the row.\nsetSelectedRows(Array)\n\nSelect the given rows.\nsetSelectedRowTags(Array)\n\nProgrammatically select the given row tags.\n\n\n\nMethods on columns in the grid\nName\nType\nPurpose\nAlignColumnHeaderVertcally(string ColumnName, string Align)\n\nAlign the given column header vertically: Default, Top, Middle or Bottom.\nassignBiCheckboxToColumn(Real)\n\nAssign a bi-checkbox to the given column.\nassignDataTypeToColumn(Real)\n\nAssign data type \"double\" to the given column.\nAssignDateTimeToColumn(double col)\n\nSet table column with date time picker.\nassignOptionSetToColumn(Real)\n\nAssign a Yes/No option set to the given column.\nassignValueListToColumn(String, Real)\n\nAssign a value list (string) to the given column.\nAutoFitColumns()\n\nResize columns to fit widest text.\nCheckFixedHeaderIndicatorOnColumn(String)\n\nQuery FixedHeaderIndicatorOn Column.\nCheckFixedHeaderOn Column(String)\n\nQuery FixedHeaderOnColumn.\nColumnsInGroupByBox()\nBoolean\nReturns true if there is at least one column in the GroupBy box.\nColumnMoving(String)\n\nAllow/disallow column moving on the given column.\nColumnDisplayedAndSortedAscending(string key)\n\nSet given column as displayed and sorted in ascending order.\nExtendLastColumn()\n\nQuery ExtendLastColumn.\nExtendLastColumn(Boolean)\n\nExtend the last column.\nFixedHeaderIndicatorOn Column(string column, Boolean)\n\nSet fixed header indicator on the given column.\nFixedHeaderOnColumn(string column, Boolean)\n\nFix the header on the column.\ngetColumn(Real)\n\nGet the cells in the column.\ngetColumn(string column)\nArray\nGet the cells in the column with a specified tag.\nGetColumnIndex(string colKey)\n\nGet the column index of the given column.\ngetColumnKey(Real)\n\nGet the key of the given column.\ngetColumnMask (Real)\n\nGet the mask of the given column.\nGetColumnOrigin(string colKey)\n\nGet the column origin of the given column.\ngetColumnPosition(string column)\nReal\nGet the position of the column with the specified tag.\nGetColumnSpan(string colKey)\n\nGet the span of the given column.\nGetColumnTitle(string column)\nString\nGet the title of the column with the specified tag.\ngetColumns()\nArray of STRING\nGet the columns in the grid.\ngetColumnsWithFilters()\nArray of STRING\nGet the columns in the grid with filters.\ngetTitles()\nArray of strings\nGet the titles for the columns in the grid.\ngetNumberColumns()\nREAL\nReturn the number of columns.\nGetSetFiltersOfGivenColumn(string col)\n\nGet filters that are set in given column name.\ngetUserColumns()\nArray\nGet the columns in the column setup window.\nGetUserColumnSpecifications\nArray\nGet the column specifications in the column setup window.\ngetUserTitles()\nArray\nGet the column titles in the column setup window.\nHashtable GetColumnsWithFilters()\n\nReturn all columns in the grid with filters.\nisColumnVisible(Real)\nBoolean\nQuery the visibility of the given column.\nisColumnVisible(string column)\nBoolean\nQuery the visibility of the specified column.\nResetColumnFilters()\n\nReset all of the column filters.\nResizeAllColumns()\n\nResize columns to fit in available width of form.\nselectCell (Real, Real, Boolean)\n\nSelect/deselect the cell (row, column).\nsetColumnColor (Real, string colour)\n\nSet the column colour to a string.\nsetColumnColor(string column, string colour)\n\nSet the column colour to a string, for example, red.\nsetColumnImage(Real, string strImageFile)\n\nSet the column image.\nsetColumnMask(Real, string strMask)\n\nSet the column mask.\nSetColumnOrigin(string colKey, Point value)\n\nSet the origin of the given column.\nsetColumnPosition(string, realPoint value)\n\nSet the position of the given column.\nSetColumnSpan(string colKey, Point value)\n\nSet the span of the given column.\nsetColumnTextAlignment(string column, string alignment)\n\nSet the alignment of text in the column to CENTRE, CENTER, LEFT or RIGHT\nsetColumnVisibility(Real, Boolean)\n\nShow/hide the specified column.\nsetColumnVisibility(String, Boolean)\n\nShow/hide the specified column.\nSetColumnWidth(Real, Real)\n\nSet the column to a designated width.\nSetColumnWidth(string column, real width)\n\nSet the column to a designated width.\nsetColumnsWithFilters(Array)\n\nSet the columns in the grid with the specified filters.\nSetColumnWithFilters(string colName, Hashtable paramValues)\n\nSet the column in the grid with specified filters and column names. This function requires to set columns and values in correct order, otherwise it won't set correctly\nSetColumnWithFilters(string colName, Hashtable paramValues)\n\nSet the column in the grid with the specified filters.\nsetEditableColumn(Real, Boolean)\n\nSet the given column to be editable/uneditable.\nsetGroupByColumn(Real, Boolean)\n\nSet the ability to group by column.\nsetNameColumnImage()\n\nDisplays standard icons in a \"NAME\" attribute column when database elements are used.\nsetNameColumnImage(boolean keepColumnWidth)\n\nDisplays standard icons in a \"NAME\" attribute column when database elements are used.\nAdditional parameter to set whether or not to maintain the column width.\nsortColumnAscending(String)\n\nSort in ascending order the specified column.\nsortColumnsAscending(Array)\n\nSort in ascending order the specified columns.\nSortedColumnCollection()\nArray\nGet the sorted columns,\nunsetNameColumnImage()\n\nRemove the standard icons in the \"NAME\" attribute column when database elements are used.\nName\nType\nPurpose\nAssignDateTimeToCell(double col, double row)\n\nSet table cell with date time picker.\nassignValueListToCell(String, Real, Real)\n\nAssign the given value list to the cell (row, column).\ncheckValueIsInCellValueList\n\nCheck if the value is in the Cells Value List\ncheckValueIsInValueList\n\nCheck if the value is in the Value List\nDoDabaconCellUpdate(Array args)\n\nThis function is provided to support user code in the BeforeCellUpdate event when the grid is displaying Dabacon element/attribute data. The array provided as argument to the BeforeCellUpdate event can be passed on to this function to modify the Dabacon element/attribute in synchroniztion with the cell data. If the function is unable to perform the modification for any reason the Array[3] and Array[4] values will be set to indicate the problem. Refer to Add an Event to the Addin for further information.\nDoDabaconElementCopy(Array args)\n\nDo a Dabacon Element copy.\nDoDabaconElementCreateAtPosition(Array args)\n\nDo a Dabacon Element create at position in the hierarchy.\nDoDabaconElementCreateFirst(Array args)\n\nDo a Dabacon Element create at the first position in the hierarchy.\nDoDabaconElementCreateLast(Array args)\n\nDo a Dabacon Element create at the last position in the hierarchy.\nDoDabaconElementDelete(Array args)\n\nDo a Dabacon Element delete.\nDoDabaconElementOrderUpdate(Array args)\n\nDo a Dabacon element order update.\ngetCell(Real, Real)\n\nGet the content of the cell in the specified row and column.\ngetCell(string rowTag, string columnTag)\nSTRING\nGet the content of the cell in the specified row and column.\ngetCellByListIndex(string rowTag, string colTag)\n\nGet the cell by list index.\nisEditableCell(string strRowTag, string strColTag)\nBoolean\nGet whether or not the cell is editable.\nremoveValueListFromCell (Real, Real)\n\nRemove the value list from the cell.\nsetCellColor(string rowTag, string columnTag, string colour)\n\nSet the colour of a cell, for example: red.\nsetCellColor(string rowTag, string columnTag, real red, real green, real blue)\n\nSet the colour of the cell to the RGB value.\nsetCellColor(Real, Real, Real, Real, Real, Real)\n\nSet the colour of the cell to the RGB value.\nsetCellColor(Real, Real, Real)\n\nSet the colour of the cell to the colour number.\nsetCellColor(Real, Real, String)\n\nSet the colour of the cell.\nsetCellImage(Real, Real, String)\n\nSet the image of the cell.\nsetCellImage(Real, Real, Image)\n\nSet the image of the cell.\nsetCellTextAlignment(string rowTag, string columnTag, string alignment), where alignment=CENTRE, CENTER, LEFT, RIGHT\n\nSet the alignment of text in the cell to CENTRE, CENTER, LEFT or RIGHT.\nsetCellTooltip(Real, Real, string strToolTip)\n\nSet the tooltip of the cell.\nsetCellValue(Real, Real, string strVal)\n\nSet the value of the cell.\nsetCellValue(string rowTag, string columnTag, string value)\n\nSet a value in the cell.\nsetCellValueByListIndex (Real, Real, string strVal)\n\nSet a value in the cell by list index.\nsetCellValueByListIndex(string rowTag, string columnTag, string value)\n\nSet a value in the cell by list index.\nsetEditableCell(Real, Real, Boolean editable)\n\nEnable/disable cell editing.\nsetEditableCell(string rowTag, string columnTag, Boolean editable)\n\nEnable/disable cell editing.\nsetSelectedCellsValue(string strVal)\n\nSet the value for all selected cells.\n\nOther methods\nName\nType\nPurpose\nUpdates()\nQuery updates.\nUpdates(Boolean)\nSet whether or not database updates should be applied to the grid.\nsetErrorIcon(Image, Image)\nSet the image of the icon to appear in a Dabacon grid when an error is generated.\nLayoutFromColumnSpecs(bool keepColumnWidths)\nRefresh layout of all columns.\nMenuTool PopupMenu\nSet the popup menu for the grid.\nMenuTool PopupMenuHeader\nSet the popup menu for the header of the grid.\nRefreshGroupSort()\nRefresh group sort (can be used when a new item is added).\nCellSort : IComparer\nThe IComparer class to sort two grid cells.\nCompare(object x, object y)\nThe compare algorithm to sort two grid cells\nSuspendUpdates(Boolean)\nSuspend updates to the grid.\nDisplayStyle CellValueListDisplayStyle\nThe cell Value List display style (Always, OnMouseEnter, OnCellActivate, OnRowActivate).\nDictionary<string, ColumnLayout> GetCurrentColumnLayout()\nGets the layout detail for each column.\nSetDateTimeDataFormat(|dd'/'MM'/'yyyy HH:mm:ss|)\nOutput/argument data[1] value if data[1] is dateTime type.\nIf the region is set to India/India English etc., the date time is normally returned as dd-MM-yyyy HH:mm:ss which will break the pre-set PML reading. This option sets the format as \"dd'/'MM'/'yyyy HH:mm:ss\" which forces the use of a slash instead of a hyphen.\nName\nType\nPurpose\nUpdates()\n\nQuery updates.\nUpdates(Boolean)\n\nSet whether or not database updates should be applied to the grid.\nsetErrorIcon(Image, Image)\n\nSet the image of the icon to appear in a Dabacon grid when an error is generated.\nLayoutFromColumnSpecs(bool keepColumnWidths)\n\nRefresh layout of all columns.\nMenuTool PopupMenu\n\nSet the popup menu for the grid.\nMenuTool PopupMenuHeader\n\nSet the popup menu for the header of the grid.\nRefreshGroupSort()\n\nRefresh group sort (can be used when a new item is added).\nCellSort : IComparer\n\nThe IComparer class to sort two grid cells.\nCompare(object x, object y)\n\nThe compare algorithm to sort two grid cells\nSuspendUpdates(Boolean)\n\nSuspend updates to the grid.\nDisplayStyle CellValueListDisplayStyle\n\nThe cell Value List display style (Always, OnMouseEnter, OnCellActivate, OnRowActivate).\nDictionary<string, ColumnLayout> GetCurrentColumnLayout()\n\nGets the layout detail for each column.\nSetDateTimeDataFormat(|dd'/'MM'/'yyyy HH:mm:ss|)\n\nOutput/argument data[1] value if data[1] is dateTime type.\nIf the region is set to India/India English etc., the date time is normally returned as dd-MM-yyyy HH:mm:ss which will break the pre-set PML reading. This option sets the format as \"dd'/'MM'/'yyyy HH:mm:ss\" which forces the use of a slash instead of a hyphen.\n\nNote:\nNot all of the API calls have been exposed for PML use.\nNote:\nYou can only use the AVEVA C# Grid Control on your own Visual Studio form if you have a design time license for Infragistics.\nNote:\nIf the user is allowed to write data to the grid, then this data does not automatically get written back to the data source (or database). The BeforeCellUpdate event of the calling code is responsible for doing this synchronisation, and is in control of whether to either allow or disallow the change (Refer to Add an Event to the Addin for further information). This does not enable the user to add/remove rows, just to edit the content of the existing cells.\nNote:\nThis will retain all grid groupings and layout of data. The String should specify the full pathname.\n\n\n\nAdd an Event to the Addin\nAdd an Event to the Addin\nNote\n:\nNote\n:\nData Source methods for populating the grid\nName\nType\nPurpose\nGeneral methods available for the grid\nName\nType\nPurpose\nNote\n:\nAdd an Event to the Addin\nNote\n:\nMethods on rows in the grid\nName\nType\nPurpose\nMethods on columns in the grid\nName\nType\nPurpose\nMethods on cells in the grid\nName\nType\nPurpose\nAdd an Event to the Addin\nOther methods\nName\nType\nPurpose"}
{"Headers": "Input Mask Characters", "Content": "Masks can be set on data within a column. The mask will restrict the format and type of the data which can be entered into cells within the column. The mask can consist of the following characters:\n#\nDigit placeholder. Character must be numeric (0-9) and entry is required.\n.\nDecimal placeholder. The actual character used is the one specified as the decimal placeholder by the system's international settings. This character is treated as a literal for masking purposes.\n,\nThousands separator. The actual character used is the one specified as the thousands separator by the system's international settings. This character is treated as a literal for masking purposes.\n:\nTime separator. The actual character used is the one specified as the time separator by the system's international settings. This character is treated as a literal for masking purposes\n/\nDate separator. The actual character used is the one specified as the date separator by the system's international settings. This character is treated as a literal for masking purposes.\n\\\nTreat the next character in the mask string as a literal. This allows you to include the '#', '&', 'A', and '?' characters in the mask. This character is treated as a literal for masking purposes.\n&\nCharacter placeholder. Valid values for this placeholder are ANSI characters in the following ranges: 32-126 and 128-255 (keyboard and foreign symbol characters).\n>\nConvert all the characters that follow to uppercase.\n<\nConvert all the characters that follow to lowercase.\nA\nAlphanumeric character placeholder. For example: a-z, A-Z, or 0-9. Character entry is required.\na\nAlphanumeric character placeholder. For example: a-z, A-Z, or 0-9. Character entry is not required.\n9\nDigit placeholder. Character must be numeric (0-9) but entry is not required.\n-\nOptional minus sign to indicate negative numbers. Must appear at the beginning of the mask string.\nC\nCharacter or space placeholder. Character entry is not required. This operates exactly like the '&' placeholder, and makes sure compatibility with Microsoft Access.\n?\nLetter placeholder. For example: a-z or A-Z. Character entry is not required.\nLiteral\nAll other symbols are displayed as literals; that is, they appear as themselves.\nn\nDigit placeholder. A group of n's can be used to create a numeric section where numbers are entered from right to left. Character must be numeric (0-9) but entry is not required.\nmm, dd, yy\nCombination of these three special strings can be used to define a date mask. mm for month, dd for day, yy for two digit year and yyyy for four digit year. Examples: mm/dd/yyyy, yyyy/mm/dd, mm/yy.\nhh, mm, ss, tt\nCombination of these three special strings can be used to define a time mask. hh for hour, mm for minute, ss for second, and tt for AP/PM. Examples: hh:mm, hh:mm tt, hh:mm:ss.\n\n\n\n\n#\n.\n,\n:\n/\n\\\n&\n>\n<\nA\na\n9\n-\nC\n?\nLiteral\nn\nmm, dd, yy\nhh, mm, ss, tt"}
{"Headers": "Data is a .NET addin", "Content": "My Data is a .NET addin that allows database elements to be collected together in collections which are persisted between modules. The API to modify My Data is also available from PML.\nMy Data assembly can be imported as follows\nIMPORT 'MyDataAddin'\nhandle any\nendhandle\nUSING NAMESPACE 'Aveva.Core.Presentation.MyDataAddin'\n!!mydata=object pmlmydata()\n\n\n"}
{"Headers": "My Data API", "Content": "The following api is then available on the My Data object.\nPMLMyData\n\nMyData constructor\nAddElement(String elename)\n\nAdds an orphaned element of given name\nAddElements(Array elements)\n\nAdds orphaned elements as array of strings\nAddCollection(String name)\n\nAdd collection of given name\nAddCollections(Array collections)\n\nAdd collections as an array of strings\nAddElementToCollection(String elementName, String collectionName)\n\nAdd element of given name to collection of given name\nAddElementsToCollection(Array elements, String collectionName)\n\nAdd elements as array of strings to collection of given name\nRemoveElement(String elename)\n\nRemove orphaned element of given name\nRemoveElements(Array elements)\n\nRemove orphaned elements as array of strings\nRemoveAllElements\n\nRemove all elements\nRemoveCollection(String name)\n\nRemove collection of given name\nRemoveCollections(Array names)\n\nRemove collections as an array of strings\nRemoveAllCollections\n\nRemove all collections\nRemoveElementFromCollection(String elementName, String collectionName)\n\nRemove given element from given collection\nRemoveElementsFromCollection(Array elements, string collectionName)\n\nRemove elements as array of strings from given collection\nRemoveAllElementsFromCollection(String collectionName)\n\nRemove all elements from given collection\nRemoveAll()\n\nRemove all orphaned elements and collections\nElements()\nArray\nReturn orphaned elements as array of strings\nElementsInCollection(String collectionName)\nArray\nReturn the elements in given collection as an array of strings\nCollections()\nArray\nReturn the collection names as an array of strings\nRenameCollection(string oldName, string newName)\n\nRename given collection with new name\n\n\n\n"}
{"Headers": "Using My Data from PML", "Content": "From PML, elements and collections can be added, removed and edited. For example:\n!!mydata.addElement('/VESS1')\n!!mydata.addElement('/VESS2')\n!!mydata.addElement('/PUMP1')\n!!mydata.addElement('/PUMP2')\n!a=object array()\n!a[1]='/VESS1'\n!a[2]='/VESS2'\n!b=object array()\n!b[1]='/PUMP1'\n!b[2]='/PUMP2'\n!!mydata.addElements(!a)\n!!mydata.addElements(!b)\n!!mydata.removeElement('/VESS1')\n!!mydata.removeAll()\n!!mydata.addElement('/VESS1')\n!!mydata.addElement('/VESS2')\n!!mydata.addElement('/PUMP1')\n!!mydata.addElement('/PUMP2')\n!!mydata.removeElements(!a)\n!!mydata.addCollection('My collection1')\n!!mydata.addCollection('My collection2')\n!collections = object array()\n!collections[1] = 'My collection3'\n!collections[2] = 'My collection4'\n!!mydata.addCollections(!collections)\n!!mydata.removeCollection('My collection1')\n!!mydata.removeCollection('My collection2')\n!collections = object array()\n!collections[1] = 'My collection3'\n!collections[2] = 'My collection4'\n!!mydata.removeCollections(!collections)\n!!mydata.addCollection('My collection1')\n!!mydata.addCollection('My collection2')\n!!mydata.addElementToCollection('/VESS1', 'My collection1')\n!!mydata.addElementToCollection('/VESS2', 'My collection2')\n!!mydata.addCollection('My collection1')\n!!mydata.addCollection('My collection2')\n!a=object array()\n!a[1]='/VESS1'\n!a[2]='/VESS2'\n!b=object array()\n!b[3]='/PUMP1'\n!b[4]='/PUMP2'\n!!mydata.addElementsToCollection(!a, 'My collection1')\n!!mydata.addElementsToCollection(!b, 'My collection2')\n!!mydata.removeElementFromCollection('/VESS1', 'My collection1')\n!!mydata.removeElementFromCollection('/VESS2', 'My collection1')\n!!mydata.removeAllElements()\n!!mydata.removeAllElementsFromCollection('My collection1')\n!!mydata.removeAllCollections()\n!!mydata.removeElementsFromCollection(!b, 'My collection2')\n!!mydata.renameCollection('collectionA', 'collectionX')\n!!mydata.renameCollection('collectionB', 'collectionY')\nq var !!mydata.elements()\nq var !!mydata.collections()\nq var !!mydata.elementsInCollection('My collection1')\n\n\n"}
{"Headers": "Open fiel browser window using pml syntax", "Content": "A standard Windows file browser window can be opened by using PML syntax.\nIf no argument is given then the object will default to Open, otherwise the user can specify the value Open or Save.\nYou can query the object and the methods on the PMLFileBrowser instance as follows:\nTo show the File Browser dialog use the following syntax:\nDirectory\nString\nDefault directory to display in File Browser.\nSeed\nString\nDefault value to be populated in the Name input box of the File Browser.\nTitle\nString\nValue to be displayed in the File Browser window title bar.\nExists\nBoolean\nCheck if the input file exists.\nFilter\nString\nThe type of files to open. Must be in the format of a description, followed by \"|\" and then the file types - for example\nWord Documents|*.DOC\nor\nText files (*.txt)|*.txt|All files (*.*)|*.*\nIndex\nInteger\nFor multiple strings, the index of the filter currently selected.\nFor example the following syntax could be entered at the command line.\nAfter entering the command the following window will be displayed.\n\nUse the following syntax to return the name of the file selected in the File Browser window.\nimport 'PMLFileBrowser'\nusing namespace 'Aveva.Core.Presentation'\n!browser = object PMLFileBrowser('OPEN')\nQ Var !browser\nQ methods !browser\n!browser.show(directory,seed,title,exists,filter,index)\n!browser.show('C:\\','abc.DOC','My Browser',true, 'Word Documents|*.DOC',1)\nq var !browser.file()\nNote:\nThe default values have been set as specified:\n\n\n\nOpen\nOpen\nSave\nNote\nFile Browser"}
{"Headers": "The configuration Manager", "Content": "The Configuration Manager is a centralized repository for all configurations that allows easy migration to a DataBase (DB) backed storage and a unified Application Programming Interface (API) of applications. A modular system allows the Configuration Manager to deal with all the myriad configuration formats to provide backwards compatibility and a clear migration path. The Configuration Manager can be used by all applications that make use of the Common Application Framework (CAF) addins.\n\n\n"}
{"Headers": "Configuration Manager Setup", "Content": "The Configuration Database must first be set up in the Admin module, set up is then required in the Lexicon module.\nThere must be at least one DataBase (DB) of type Configuration in the Multiple DataBase (MDB). By default, a Config DB already exists which is a read only type with Core configurations. It is not recommended to use the default Config DB.\nA config DB is created in the same way as any other DB and can be added to the MDB.\nOnce the Config DB is set, config sets must be created using the Command Window.\nThe example PML code can be used as a reference to create a Config Set World as well as Config Sets below it.\nThe example Programmable Macro Language (PML) code creates a Config Set World named EICONFIGWORLD and creates a Config Set named EICONFIGSET below it. Appropriate PML may be required to navigate to the right node Config DBs in the MDB or multiple Config Worlds already exist in the DB. The precedence value indicates the order in which the Config Sets must be considered, the higher the precedence value the higher the priority of the Config Set. It is not recommended to use precedence values above 3000 as some Core configurations make use of values above 3000.\nThe keys that point to the Configuration Manager values saved in the Config DB must be created in the Dictionary DB using the Lexicon module.\nValid Config Group World (CFFGGDW), Config Group (CFGGRP) and Config Key (CFGKEY) elements must be created.\nThe example can be used as a reference to create and configure a CFFGGDW element.\n\nThe example can be used as a reference to create and configure a CFGGRP element.\n\nThe CFGGRP must be populated with a Name and a valid Config key name. The Display name is an optional attribute.\nThe CFGGRP can contain multiple group elements as well as multiple key elements.\nThe example can be used as a reference to create and configure a CFGKEY element.\n\nThe CFGKEY must be populated with a Name, a Config Key name, a Config value type and a Uda type.\nTo use configuration, dbProviders must be instantiated appropriately when the module/ add-in, project is loaded.\nAn instance of IConfigurationManagerConsumer can be created. A configuration manager consumer is used to interact with the configurations and to create dbProviders.\nA dbProvider can be created in the following way:\nThe parameters are self explanatory. The dbProvider must be associated with a parent group.\nBy default, the configuration provider initialises any configurations that are saved under the parent group. The created dbProviders must then be added to the configuration manager:\nOnly providers added to the configuration manager are available for use in the project.\nSetting a value in a key requires dbProvider. For example:\nThe required dbProvider can be queried in various ways from the collection offered by the configuration manager consumer.\nThe Set method of DatabaseConfigurationProvider uses two arguments \u2013 the key name along with the group name and the value to be stored in the key. The value supplied is stored in the key passed to this method.\nA configuration value can also be set using the ConfigurationManager. The configuration instance must be registered in one of the providers under ConfigurationManager. The ConfigurationManager does not load a configuration if it has no instances or values saved in it. Setting values using ConfigurationManager requires careful assessment before use.\nTo get values stored under a key, the key along with the group name must be passed to the get method. For example:\nThe configuration manager can be used to get a value if a valid config key exists.\n goto frstw CONF\n $* Sets\n $P Creating config set world\n new CFGSTW /EICONFIGWORLD\n $P Creating config sets\n new CFGSET /EICONFIGSET\nDname 'AVEVA EI options'\nDesc 'AVEVA EI options'\n Precedence 1\nvar dbProvider = new DatabaseConfigurationProvider(providerName, displayName, parentGroup,\n      precedence, \"Startup\", setName, active, set);\n   \nconfigurationManager.AddProvider(dbProvider);\n  dbProvider = null;\n   \n    var configurationManager = EIDependencyResolver.ConfigurationManagerConsumer;\n    foreach(var provider in configurationManager.Providers)\n   \n    {\n   \n      if (provider.Name == \"EICableSpecProvider\")\n      {\n        dbProvider = provider as DatabaseConfigurationProvider;\n      }\n    }\n    //WRITE\ndbProvider.Set(@\"EICONFIGURATIONKEY/ELECCABLESPECKEY\", specData.Electrical);\nconfigurationManager.Get<string>(@\"EICONFIGURATIONKEY/ELECCABLESPECKEY\");\nNote:\nThe commands do not produce any visible results in the Admin Explorer.\nNote:\nThe Config value type must be set to 2 for strings.\n\n\n\nCommand Window\nNote\n:\nName\nConfig key name\nDisplay name\nName\nConfig Key name\nConfig value type\nUda type\nNote\n:\nConfig value type\n2\n \n   \n    "}
{"Headers": "Use the Configuration Manager", "Content": "A two phased approach can be used to implement the Configuration Manager.\n\nSettings providers are requested on start-up and register any settings that can be provided.\nApplications receive settings by requesting them by name from the ConfigurationManager\nThe Configuration Manager then asks each provider in turn, via a precedence, to provide a setting value. If the provider fails to supply a setting value, the Configuration Manager then asks the next provider. If no providers supply a value, the SystemDefault is returned.\nA cache may be required for performance. Settings files could be read only when the first setting is requested (lazy loading) and all the other settings cached at that point. This approach allows a selective supply of providers and supports legacy settings.\nStart read-only.\nExisting data is replicated by creating legacy providers (perhaps one for each file type and one for environment variables). These providers are simple to write.\nExisting applications are modified to use the Configuration Manager (it is recommended to move settings over gradually to minimize risk of error).\nAdd write capability.\nNew style providers are added to store settings in better places (for example, a database). Use the precedence to ensure these providers are preferred, with the legacy provider as a back-up.\nNew consumers are added for additional functionality:\nTo get a reference to the Configuration Manager:\nUse appropriate Get/Set methods, for example:\nProgrammable Macro Language (PML) access to the configuration values is achieved via a C# object. The following methods are defined:\nThe Integer methods return a REAL value.\nFor Get methods with a default, the default value is returned if no value exists for that name.\nThe Set methods return a flag indicating if the set succeeded.\nThe following code creates an object:\nConfigurationManager.RegisterSetting(\"DateFormat\");\nstring dateFormat = ConfigurationManager.GetSetting<string>(\"DateFormat\", SystemDefault);\n<SPAN>;</SPAN>\nconfigurationManager.GetString(key);\nstring GetString(string key, string default)\nstring GetString(string key)\nboolean GetBoolean(string key, boolean default)\nboolean GetBoolean(string key)\nreal GetInteger(string key, real default)\n\nreal GetInteger(string key)\nreal GetDouble(string key, real default)\nreal GetDouble(string key)\nstring GetAsString(string key)\narray GetEnumNames(string key)\narray GetEnumValues(string key)\n\nboolean SetString(key, value)\nboolean SetBoolean(key, boolean value)\nboolean SetInteger(key, real value)\nboolean SetDouble(key, real value)\n\nboolean SetFromString(string key, string value)\nimport 'Aveva.Core.Configuration.Implementation'\nusing namespace 'Aveva.Core.Configuration.Implementation'\n!cm = object PMLConfigurationManager()\nq var !cm.GetString('Isometrics/ALLTYPES/Text')\nq var !cm.GetInteger('Isometrics/ALLTYPES/Integer')\nq var !cm.GetDouble('Isometrics/ALLTYPES/Real')\nq var !cm.GetBoolean('Isometrics/ALLTYPES/Boolean')\n!cm.SetString('Isometrics/ALLTYPES/Text', 'Hello Aveva')\nq var !cm.GetString('Isometrics/ALLTYPES/Text')\n\n\n:\n\n\nInteger input\n\ntext .listLength |Length of recently used list | callback '!this.conMan.SetInteger\n(|Diagrams/GeneralOptions/SystemConfiguration/System/MRU_LIST_LENGTH|, !this.listLength.val.real())'\n      width 10 integer\n   \n\nOption (Drop-down)\n\noption .isometrics01 |Drawing Size | callback '!this.conMan.SetInteger(|Isometrics/SHEETLAYOUT/DrawingSize|,\n      !this.isometrics01.selection(|rtext|).real())' width 24\n   \n\n\n\n!iso01 = !this.conMan.GetInteger(|Isometrics/SHEETLAYOUT/DrawingSize|)\n\n\n!enumNames = !this.conMan.GetEnumNames(|Isometrics/SHEETLAYOUT/DrawingSize|)\n!enumValues = !this.conMan.GetEnumValues(|Isometrics/SHEETLAYOUT/DrawingSize|)  \n!this.isometrics01.dText = !enumNames\n!this.isometrics01.rText  = !enumValues\n!this.isometrics01.select('rtext','$!iso01')\n\n\n\nToggle\ntoggle .isometrics02  |Show Change Highlighting | callback '!this.conMan.SetBoolean(|Isometrics/CHANGEHIGHLIGHTING/HIGHLIGHTINDICATOR|,\n      !this.isometrics02.val)'\n   \nConfiguration UI\nImport/Export\nConfiguration UI\nConfiguration UI\nImport/Export\nImport/Export\n\n\n\nConfigurationManager.RegisterSetting(\"DateFormat\");\nstring dateFormat = ConfigurationManager.GetSetting<string>(\"DateFormat\", SystemDefault);\nExamples of Get methods\nExample of the Set method"}
{"Headers": "The AVEVA Standalone interface to build and develop customized applications", "Content": "The AVEVA Standalone interface allows you to build and develop customized applications. Functionality is available to access and modify Dabacon based data programmatically, in a secure and authorized manner, with all validity and legality checks in place, without the need for a Graphical User Interface.\nThere are two standalone assemblies available for customization:\nWhen using the AVEVA Standalone interface, developers can carry out the following procedures using a single standalone executable process:\nApplication or custom commands and macros can be called directly for execution without the need for user interaction.\nDatabase API calls along with application commands and macros can be implemented.\n   Standalone.Start((int)ModuleName.Design, envHashTable);\n   \n   //open project etc\n   PdmsMessage error;\n   \n   if (!Standalone.Open(envHashTable[\"PROJECTNAME\"].ToString(),\n   \n                        envHashTable[\"USER\"].ToString(),\n   \n                        envHashTable[\"AUTH\"].ToString(),\n   \n                        envHashTable[\"MDB\"].ToString(),\n   \n                        out error))\n   \n   {\n   \n       error.Output();\n   }\n   // Do some basic Database work (business logic)\n   CheckDatabase();\n   // close and open an invalid project\n   Project.CurrentProject.Close();\n   \n   Standalone.Finish();\n   \nAveva.Core3D.Standalone\nSupports, and is limited to, common core functionality and core command syntax graphs.\nAveva.E3D.Standalone\nSupports AVEVA E3D Design functions and command syntax graphs. For example Model or Draw.\nAveva.Core3D.Standalone\nSupports, and is limited to, common core functionality and core command syntax graphs.\nAveva.Core3D.Standalone\nAveva.E3D.Standalone\nSupports AVEVA E3D Design functions and command syntax graphs. For example Model or Draw.\nAveva.E3D.Standalone\nLaunch the custom application as a specific module (for example, Model or Draw).\nLogin and open the project(s).\nRun the business logic.\nSave work, if required.\nUnclaim all elements, if applicable.\nClose the project and finish the process.\nLaunch the custom application as a specific module (for example, Model or Draw).\nLaunch the custom application as a specific module (for example, Model or Draw).\nLogin and open the project(s).\nLogin and open the project(s).\nRun the business logic.\nRun the business logic.\nSave work, if required.\nSave work, if required.\nUnclaim all elements, if applicable.\nUnclaim all elements, if applicable.\nClose the project and finish the process.\nClose the project and finish the process.\n\n\n\n   \nStandalone\nModuleName\n   \n//open project etc\n   \nPdmsMessage\n  \nStandalone\nPROJECTNAME\nUSER\nAUTH\nMDB\nout\n   \n   \n// Do some basic Database work (business logic)\n   \n();\n  \n // close and open an invalid project\n   \nProject\n.\n   \nStandalone"}
{"Headers": "Use AVEVA Standalone", "Content": "To build and run the sample code.\nSET AVEVA_DESIGN_EXE=C:\\Program Files (x86)\\AVEVA\\\nEverything3D2.10\n\n\n\nSamples.zip\nStandaloneExample\nStandaloneExample\nVisual Studio Command Prompt\nStandaloneExample\nAVEVA_DESIGN_EXE\nAvevaStandalone.sln\napp.config\napp.config\nAvevaStandaloneE3D.exe.config\nAvevaStandaloneE3D.exe.config\nStandalone.cs"}
{"Headers": "The Pipework application", "Content": "The Pipework application is supplied as a module within the AVEVA E3D Design suite. The Pipework application enables the design and detail of complex pipework networks within a full 3D environment, with the support of tools to produce a clash-free design.\nOnce the 3D model has been produced, the Pipe Stress Interface - R2 provides a two-way exchange of information between AVEVA E3D Design and Rohr2. Piping designers and stress engineers can exchange design and stress information seamlessly, to eliminate data re-entry and duplication.\nIt is also possible to transfer stress data from Rohr2 to AVEVA E3D Design for hanger and support calculations.\nRohr2 can be acquired from:\nSigma Ingenieurgesellschaft mbH.\nBertha-von-Suttner-Allee 19\n59423 Unna Germany\n\n\n\n\n\n\n\n\n\n\n\n"}
{"Headers": "The UDA macrp file", "Content": "In order to use the interface, additional User Defined Attributes (UDAs) and catalog data is required.\nThe UDA macro file (lexicon_psi_r2_uda.mac) contains attributes for loads and forces. The catalog macro file (paragon_psi_r2_uda.mac) contains parameterized NOZZle components which are used for the geometry display of imported pipes.\nUDAs and Catalog Data are provided as Database (DB) Listings files. Both files are located in the installation path:\nC:\\Program Files (x86)\\AVEVA\\Everything3D3.1\\asso_products\\psi-r2\\data\nTwo DBs must be provided for the Database Listings files:\nDictionary DB (type \"dict\", access update)\nlexicon_psi_r2_uda.mac\nCatalog DB (type \"cata\", access multiwrite)\nparagon_psi_r2_uda.mac\nDictionary DB (type \"dict\", access update)\nDictionary DB (type \"dict\", access update)\nlexicon_psi_r2_uda.mac\nlexicon_psi_r2_uda.mac\nCatalog DB (type \"cata\", access multiwrite)\nCatalog DB (type \"cata\", access multiwrite)\nparagon_psi_r2_uda.mac\nparagon_psi_r2_uda.mac\nNote:\nMake sure that the DBs are included in every MDB.\nNote:\nUninstall PSI and PSI-R2 before installing AVEVA E3D Design 3.1.2 and any later update releases.\n\n\n\nNote\n:\nNote\n:"}
{"Headers": "AVEVA E3D communicates with Rohr2 using ASCII files", "Content": "AVEVA E3D Design communicates with Rohr2 using ASCII files. These files are stored in a directory that is declared by the environment variable %R2STRESS%. In addition, a Project-specific environment variable, %xyzR2STRESS%, can be used (\"xyz\" is the project code).\nIf both environment variables are set and both directories exist, the Project-specific directory is used.\nIt is recommended to use the Project-specific environment variable because of Project-related settings and different displacement files for each Project.\nThe following file extensions are used by the interface to transfer data:\nExtension\nDescription\nDirection\n.ntr\nFile with geometry data.\nAVEVA E3D Design to Rohr2.\n.ntrerror\nLog file for transfer of geometry.\n.r2hangprop\nFile with data for hanger points.\nRohr2 to AVEVA E3D Design.\n.r2hangerror\nLog file for hanger points.\n.r2disp\nFile for displacement data.\nExtension\nDescription\nDirection\n.ntr\nFile with geometry data.\nAVEVA E3D Design to Rohr2.\n.ntrerror\nLog file for transfer of geometry.\n.r2hangprop\nFile with data for hanger points.\nRohr2 to AVEVA E3D Design.\n.r2hangerror\nLog file for hanger points.\n.r2disp\nFile for displacement data.\nAn overview of the allowed Hanger Types is available. For further information, refer to Hanger Types.\n\n\n\nHanger Types\n%R2STRESS%\n%xyzR2STRESS%\nExtension\nDescription\nDirection\nHanger Types"}
{"Headers": "The transfer of geometry data", "Content": "The transfer of geometry data is bound to the allowed type declaration of Rohr2. For example, it is not possible to transfer tee-fittings with three different bores or reducing elbows. It is also not possible to transfer reducers or elbows with an outlet.\nBefore transferring pipe systems, pipes must be checked for geometry and bore consistency, otherwise problems during data transfer cannot be excluded.\n\n\n"}
{"Headers": "Provides a two way exchange of information between AVEVA E3D Design and the Rohr2", "Content": "Provides a two way exchange of information between AVEVA E3D Design and the Rohr2 pipe stress system.\n\nExport\nExports geometry and material to Rohr2. For further information, refer to Export Geometry from E3D to Rohr2.\nDisplacement\nCreates a 3D model for each loading case defined in the Rohr2 result file. The 3D model consists of Nozzles that indicate the displacement of the pipe system and can be displayed together with the original pipe system. For further information, refer to Thermal Displacements.\nSupport Value\nTransfers pipe support data, calculated by Rohr2, to 3D model element attributes. For further information, refer to Import Hanger Attributes.\nSettings\nDefines data transfer settings between AVEVA E3D Design and Rohr2. For further information, refer to Data Transfer Settings.\nExport\nExports geometry and material to Rohr2. For further information, refer to Export Geometry from E3D to Rohr2.\nDisplacement\nCreates a 3D model for each loading case defined in the Rohr2 result file. The 3D model consists of Nozzles that indicate the displacement of the pipe system and can be displayed together with the original pipe system. For further information, refer to Thermal Displacements.\nSupport Value\nTransfers pipe support data, calculated by Rohr2, to 3D model element attributes. For further information, refer to Import Hanger Attributes.\nSettings\nDefines data transfer settings between AVEVA E3D Design and Rohr2. For further information, refer to Data Transfer Settings.\n\n\n\n\nExport Geometry from E3D to Rohr2\nThermal Displacements\nImport Hanger Attributes\nData Transfer Settings\nExport\nExport Geometry from E3D to Rohr2\nDisplacement\nThermal Displacements\nSupport Value\nImport Hanger Attributes\nSettings\nData Transfer Settings"}
{"Headers": "Exports geometry and material from AVEVA E3D Design to Rohr2", "Content": "Exports geometry and material from AVEVA E3D Design to Rohr2.\n\nThe Export Data part of the AVEVA Pipe Stress Interface - R2 window displays the pipes/ branches for export.\nWhen collecting the pipes of a pipe system for export to Rohr2, it is mandatory that the pipes are in a network. None of the branches may be isolated by the rest of the pipe system.\nThe current export list content is displayed and highlighted in the 3D view. The content can be checked for completeness. For example, a branch may not be collected because of missing references.\nThe highlight color can be modified. For further information, refer to Data Transfer Settings.\nList Pipes / List Branches\nDisplays branches or pipes for export.\nAdd CE\nAdds all branches below the current element to the export list.\nNote: It is not checked if all elements are part of a single network or all branches are connected correctly.\nAdd Network\nAdds all branches to the export list which are connected directly or indirectly to the current element.\nRemove CE\nRemoves all branches below the current element from the export list.\nRemove Network\nRemoves all branches from the export list which are connected directly or indirectly to the current element.\nRemove Selected\nRemoves the selected elements from the export list.\nLoad Pipe List\nPopulates the export list with the content of a previously saved file.\nSave Pipe List\nSaves the content of the export list to a file.\nModify Hangers\nAssigns hanger types to single hangers. Refer to Modify Hangers for further information.\nShow Limits\nSets the limits of the 3D view to the content of the export list.\nShow Labels\nDisplays selected pipe supports in the 3D view.\nLabel Types\nDisplays selected support attributes.\nThe option becomes active when Show Labels is selected.\nApply\nExports all selected branches. After collecting all geometry and material data, the file browser is opened in order to define the name and location of the transfer file. The file extension must be .ntr.\nAdditionally, a second file with the extension .ntrerror is created in the transfer directory. The log file contains all export error information.\nCancel\nDiscards any changes and closes the AVEVA Pipe Stress Interface - R2 window.\nList Pipes / List Branches\nDisplays branches or pipes for export.\nAdd CE\nAdds all branches below the current element to the export list.\nAdd Network\nAdds all branches to the export list which are connected directly or indirectly to the current element.\nRemove CE\nRemoves all branches below the current element from the export list.\nRemove Network\nRemoves all branches from the export list which are connected directly or indirectly to the current element.\nRemove Selected\nRemoves the selected elements from the export list.\nLoad Pipe List\nPopulates the export list with the content of a previously saved file.\nSave Pipe List\nSaves the content of the export list to a file.\nModify Hangers\nAssigns hanger types to single hangers. Refer to Modify Hangers for further information.\nShow Limits\nSets the limits of the 3D view to the content of the export list.\nShow Labels\nDisplays selected pipe supports in the 3D view.\nLabel Types\nDisplays selected support attributes.\nThe option becomes active when Show Labels is selected.\nApply\nExports all selected branches. After collecting all geometry and material data, the file browser is opened in order to define the name and location of the transfer file. The file extension must be .ntr.\nAdditionally, a second file with the extension .ntrerror is created in the transfer directory. The log file contains all export error information.\nCancel\nDiscards any changes and closes the AVEVA Pipe Stress Interface - R2 window.\n\nNote: It is not checked if all elements are part of a single network or all branches are connected correctly.\n\n\n\nData Transfer Settings\nModify Hangers\nExport Data\nAVEVA Pipe Stress Interface - R2\nData Transfer Settings\nList Pipes / List Branches\nAdd CE\nNote\n:\nAdd Network\nRemove CE\nRemove Network\nRemove Selected\nLoad Pipe List\nSave Pipe List\nModify Hangers\nModify Hangers\nShow Limits\nShow Labels\nLabel Types\nShow Labels\nApply\nCancel\nAVEVA Pipe Stress Interface - R2"}
{"Headers": "Assigns hanger types to single hangers.", "Content": "Assigns hanger types to single hangers.\n\nSupport List\nDisplays all hangers associated with the pipes selected for export (ATTY unset or ATTY HANG).\nSupport Types\nDisplays all available hanger types for export.\nAccept\nModifies the hanger points (USTHTYP attribute) for selected hanger points and hanger types.\nHome\nDisplays the Export Data part of the AVEVA Pipe Stress Interface - R2 window.\nSupport List\nDisplays all hangers associated with the pipes selected for export (ATTY unset or ATTY HANG).\nSupport Types\nDisplays all available hanger types for export.\nAccept\nModifies the hanger points (USTHTYP attribute) for selected hanger points and hanger types.\nHome\nDisplays the Export Data part of the AVEVA Pipe Stress Interface - R2 window.\n\n\n\n\nSupport List\nATTY unset\nATTY HANG\nSupport Types\nAccept\nUSTHTYP\nHome\nExport Data\nAVEVA Pipe Stress Interface - R2"}
{"Headers": "the stress calculation in Rohr2", "Content": "One result of the stress calculation in Rohr2 is the displacements based on thermal influences of the whole pipe system. The displacements can be displayed in AVEVA E3D Design.\nFor each loading case, a separate 3D model containing equipment elements with nozzles is created. The created 3D models can be displayed together with the original pipe.\nIn order to read the displacement files, a design Database (DB) with write access must be selected. In this DB, a site (for example, /R2) must be created. The PURPOSE attribute of that site must contain the value DISP.\nIf there is such a site in a read/write DB, it is displayed in the window.\nIt must be taken into account that imported 3D models of loading cases cause hard clashes in AVEVA E3D Design. It is recommended to import the 3D model in a DB that is not always current, to temporarily check loading cases.\nThe loading case 3D models are based on parameterized NOZZles. The nozzles represent two adjacent calculation points and the direct line between these two points, modelled by a cylinder. The pipe can also be displayed with insulation. In order to display insulation, the Obstruction and Insulation transparency should be set to 50%. For further information, refer to Representations.\n\n\n\nPURPOSE\nDISP"}
{"Headers": "Creates a 3D model for each defined loading case in the Rohr2 result file", "Content": "Creates a 3D model for each defined loading case in the Rohr2 result file. The 3D model consists of Nozzles that indicate the displacement of the pipe system and can be displayed together with the original pipe system.\n\nFor each loading case of a calculated pipe system, Rohr2 writes one ASCII file with the extension .r2disp to the transfer directory. The files contain positions, with movement in X, Y, and Z directions, for each calculation point.\nThe files are displayed in the Import Displacements part of the AVEVA Pipe Stress Interface - R2 window and sorted by pipe systems and respective loading cases. The list can be refreshed.\nSelect the loading cases to be imported and click Load Cases to import files to the Database (DB).\nThe example below describes a created hierarchy:\nType\nName\nDescription\nSITE\n/DISP\nZONE\n/DISP_28MAW30\nThe ZONE element contains all loading cases of the 28MAW30 system.\nEQUI\n/DISP_28MAW30_DL\nThe EQUI element contains the DL loading case.\nSUBE\n\u2026/F0HAC10BR011/B1\nThe SUBE element contains the /F0HAC10BR011/B1 branch of the DL loading case.\nNOZZ\n\u2026/F0HAC10BR011/B1_260-280\nThe NOZZ element represents the connection between calculation points 260 and 280.\nType\nName\nDescription\nSITE\n/DISP\n\nZONE\n/DISP_28MAW30\nThe ZONE element contains all loading cases of the 28MAW30 system.\nEQUI\n/DISP_28MAW30_DL\nThe EQUI element contains the DL loading case.\nSUBE\n\u2026/F0HAC10BR011/B1\nThe SUBE element contains the /F0HAC10BR011/B1 branch of the DL loading case.\nNOZZ\n\u2026/F0HAC10BR011/B1_260-280\nThe NOZZ element represents the connection between calculation points 260 and 280.\nAfter importing the loading cases, the Import Displacements part of the AVEVA Pipe Stress Interface - R2 window is updated. The Representations part of the AVEVA Pipe Stress Interface - R2 window is populated with the content of the DB.\nImported files are renamed from .r2disp to .r2dispold.\nImported loading cases are displayed per pipe system. For each pipe system, a single loading case and all branches of that system are listed. The display of loading cases can be switched on and off and superimposed with the original branch. Colors can be adjusted individually.\nOnly selected branches in the branch list are displayed in the 3D view. Select a system to update the 3D view with all system branches.\nThe example displays a superimposed pipe with calculated load cases.\n\n\n\nOriginal pipe 3D model (blue).\nOriginal pipe 3D model (blue).\nOriginal pipe 3D model (blue).\nLoading case 3D model 0_DEAD_LOAD (red).\nLoading case 3D model 0_DEAD_LOAD (red).\nLoading case 3D model 0_DEAD_LOAD (red).\nOriginal pipe 3D model (blue) superimposed with loading case model 0_DEAD_LOAD (red).\nOriginal pipe 3D model (blue) superimposed with loading case model 0_DEAD_LOAD (red).\nOriginal pipe 3D model (blue) superimposed with loading case model 0_DEAD_LOAD (red).\n\n\n\nImport\nDisplacements\nAVEVA Pipe Stress Interface - R2\nLoad Cases\nType\nName\nDescription\nSITE\n/DISP\nZONE\n/DISP_28MAW30\nZONE\nEQUI\n/DISP_28MAW30_DL\nEQUI\nSUBE\n\u2026/F0HAC10BR011/B1\nSUBE\nNOZZ\n\u2026/F0HAC10BR011/B1_260-280\nNOZZ\nImport\nDisplacements\nAVEVA Pipe Stress Interface - R2\nRepresentations\nAVEVA Pipe Stress Interface - R2\n0_DEAD_LOAD\n0_DEAD_LOAD"}
{"Headers": "the UST-UDAs are not available", "Content": "If the UST-UDAs are not available, a message is displayed asking to contact the system administrator. Without the UDAs, the interface does not work.\n\nThe error can be caused by:\nThe respective DICT Database (DB) is not created in the Admin module.\nThe respective DICT DB is not included in the current MDB or is deferred.\nThe required UDAs are not included in the DICT DB. For further information, refer to Prerequisites.\nThe DICT DB is not compiled.\nThe respective DICT Database (DB) is not created in the Admin module.\nThe respective DICT Database (DB) is not created in the Admin module.\nThe respective DICT DB is not included in the current MDB or is deferred.\nThe respective DICT DB is not included in the current MDB or is deferred.\nThe required UDAs are not included in the DICT DB. For further information, refer to Prerequisites.\nThe required UDAs are not included in the DICT DB. For further information, refer to Prerequisites.\nThe DICT DB is not compiled.\nThe DICT DB is not compiled.\n\n\n\nPrerequisites\nPrerequisites"}
{"Headers": "Rohr2 delivers design data for the design and construction of pipe hangers and supports", "Content": "The design data for the hanger points of all pipe systems are stored in ASCII files with the extension .r2hangprop in the communication directory %R2STRESS% or %xyzR2STRESS% respectively. The values are transferred to the attributes of the corresponding support points.\n\n\n"}
{"Headers": "Transfers pipe support data, calculated by Rohr2, to 3D model element attributes.", "Content": "\n\nIf an r2hangprop file is not present in the communication directory, a message is displayed indicating that no files with hanger point data are available.\n\nThe .r2hangprop file contains all hanger point design data for a calculated pipe system. If the hanger point design data can be transferred without errors, the files are renamed from .r2hangprop to .r2hangpropold.\nIf write access is not available for at least one of the hanger points, or if the hanger point is in a read-only Database (DB), a window is displayed containing a list of hanger points that cannot be updated. Detailed error information is written to a file with the extension r2hangerror. The error file is created in the %xyzR2STRESS% directory or %R2STRESS% directory, respectively.\n\n\n"}
{"Headers": "The support point attributes", "Content": "The following support point attributes are set:\nUDA name\nExample\nDescription\n:USTDYNLOAD\n1.8 2.6 3.8\nDynamic load in X, Y, Z direction [kN].\n:USTEREPORT\n|Rep No 124711|\nElasticity report [text: max. 120 characters].\n:USTFORCE\n10 5.6 7.8\nForces in X, Y, Z direction [kN].\n:USTHCOMP\n|507845|\nSpring or constant hanger part number.\n:USTMAXTRAVEL\n3.6\nMaximum movement [mm].\n:USTMOVEMENT\n2.1 3.5 0.7 3.4 4.3\nvalue: movement in y direction [mm].\nvalue: movement in x direction [mm].\nvalue: movement in z direction [mm].\nvalue: positive dynamic movement [mm].\nvalue: negative dynamic movement [mm].\n:USTNODENUMB\n1023\nHanger point node number.\n:USTSRATE\n4.5\nSpring rate [N/mm].\n:USTSTATLOAD\n7.8\nStatic load [kN].\n:USTTESTLOAD\n4.3\nWater test load [kN].\nUDA name\nExample\nDescription\n:USTDYNLOAD\n1.8 2.6 3.8\nDynamic load in X, Y, Z direction [kN].\n:USTEREPORT\n|Rep No 124711|\nElasticity report [text: max. 120 characters].\n:USTFORCE\n10 5.6 7.8\nForces in X, Y, Z direction [kN].\n:USTHCOMP\n|507845|\nSpring or constant hanger part number.\n:USTMAXTRAVEL\n3.6\nMaximum movement [mm].\n:USTMOVEMENT\n2.1 3.5 0.7 3.4 4.3\n:USTNODENUMB\n1023\nHanger point node number.\n:USTSRATE\n4.5\nSpring rate [N/mm].\n:USTSTATLOAD\n7.8\nStatic load [kN].\n:USTTESTLOAD\n4.3\nWater test load [kN].\n\n\n\n\nUDA name\nExample\nDescription\n:USTDYNLOAD\n:USTEREPORT\n:USTFORCE\n:USTHCOMP\n:USTMAXTRAVEL\n:USTMOVEMENT\n:USTNODENUMB\n:USTSRATE\n:USTSTATLOAD\n:USTTESTLOAD"}
{"Headers": "The UDAs USTHTYP and USTSCHTYP", "Content": "The UDAs USTHTYP and USTSCHTYP contain hanger construction description abbreviations. The UDA USTHTYP describes the design-engineering. The UDA USTSCHTYP describes the calculated mode of operation at the hanger point.\nThe UDA USTHTYP is used to define a pre-selection for hanger design. The pre-selection is used in the Cascade software, owned by Witzenmann GmbH, Pforzheim (Germany). For example, the UDA value KH defines a constant hanger.\nThe following table displays Rohr2 definitions with no corresponding Witzenmann hanger type (none). In such cases, the definition must be produced in the Cascade software.\nThe table provides an overview of the most common hanger types.\nDescription\nWitzenmann\nRohr2\nUDA\n:USTHTYP\n:USTSCHTYP\nGeneral clamp\nAC\nNone\nRigid support\nGS\nGS\nRigid hanger\nSH\nSH\nSpring hanger\nFH\nFH\nConstant hanger\nKH\nKH\nGeneral rigid support\nGS\nST\nFix point\nFP\nFP\nFriction bearing vertical\nNone\nGL\nLateral thrust bearing vertical\nNone\nFL\nAxial stop\nNone\nAX\nLateral stop horizontal\nNone\nQS\nStauff-clamp\nSC\nNone\nFriction bearing + Axial stop vertical, axial\nNone\nGLAX\nThrust bearing + Axial stop all movements\nNone\nFLAX\nLateral stop + Axial stop horizontal lateral, axial\nNone\nQSAX\nThrust bearing vertical, guiding in the global X axis\nNone\nFLVX\nThrust bearing vertical, guiding in the global Y axis\nNone\nFLVY\nThrust bearing vertical, guiding in the global Z axis\nNone\nFLVZ\nThrust bearing vertical, guiding in the global X and Y axis\nNone\nFLVXY\nThrust bearing vertical, guiding in the global X and Z axis\nNone\nFLVXZ\nThrust bearing vertical, guiding in the global Y and Z axis\nNone\nFLVYZ\nLateral stop in vertical pipe\nNone\nQSV\nLateral stop in vertical pipe in the global X axis\nNone\nQSVX\nLateral stop in vertical pipe in the global Y axis\nNone\nQSVY\nLateral stop in vertical pipe in the global Z axis\nNone\nQSVZ\nGeneral spring support\nNone\nFS\nSpring support\nFS\nFGL\nSpring support + guidance\nNone\nFFL\nSpring support + axial stop\nFS\nFGLAX\nSpring support + guidance + axial stop\nFS\nFFLAX\nSpring support + guidance in vertical and global X direction\nFS\nFFLVX\nSpring support + guidance in vertical and global Y direction\nFS\nFFLVY\nSpring support + guidance in vertical and global Z direction\nFS\nFFLVZ\nSpring support + guidance in vertical and global X and Y direction\nFS\nFFLVXY\nSpring support + guidance in vertical and global X and Z direction\nFS\nFFLVXZ\nSpring support + guidance in vertical and global Y and Z direction\nFS\nFFLVYZ\nConstant support\nKS\nKGL\nConstant support + guidance\nKS\nKFL\nConstant support + axial stop\nKS\nKGLAX\nConstant support + guidance + axial stop\nKS\nKFLAX\nConstant support + guidance in vertical and global X direction\nKS\nKFLVX\nConstant support + guidance in vertical and global Y direction\nKS\nKFLVY\nConstant support + guidance in vertical and global Z direction\nKS\nKFLVZ\nConstant support + guidance in vertical and global X and Y direction\nKS\nKFLVXY\nConstant support + guidance in vertical and global X and Z direction\nKS\nKFLVXZ\nConstant support + guidance in vertical and global Y and Z direction\nKS\nKFLVYZ\nGeneral pivot support\nGS\nGS\nRigid pivot support vertical\nGS\nGSV\nRigid pivot support lateral\nGS\nGSQ\nRigid pivot support axial\nGS\nGSAX\nRigid pivot support in vertical pipe lateral in global X direction\nGS\nGSQVX\nRigid pivot support in vertical pipe lateral in global Y direction\nGS\nGSQVY\nRigid pivot support in vertical pipe lateral in global Z direction\nGS\nGSQVZ\nElastic pivot support vertical\nFS\nFGSV\nElastic pivot support lateral\nFS\nFGSQ\nElastic pivot support axial\nFS\nFGSAX\nElastic pivot support in vertical pipe lateral in global X direction\nFS\nFGSQVX\nElastic pivot support in vertical pipe lateral in global Y direction\nFS\nFGSQVY\nElastic pivot support in vertical pipe lateral in global Z direction\nFS\nFGSQVZ\nConstant pivot support vertical\nKS\nKGSV\nConstant pivot support lateral\nKS\nKGSQ\nConstant pivot support axial\nKS\nKGSAX\nConstant pivot support in vertical pipe lateral in global X direction\nKS\nKGSQVX\nConstant pivot support in vertical pipe lateral in global Y direction\nKS\nKGSQVY\nConstant pivot support in vertical pipe lateral in global Z direction\nKS\nKGSQVZ\nDescription\nWitzenmann\nRohr2\nUDA\n:USTHTYP\n:USTSCHTYP\nGeneral clamp\nAC\nNone\nRigid support\nGS\nGS\nRigid hanger\nSH\nSH\nSpring hanger\nFH\nFH\nConstant hanger\nKH\nKH\nGeneral rigid support\nGS\nST\nFix point\nFP\nFP\nFriction bearing vertical\nNone\nGL\nLateral thrust bearing vertical\nNone\nFL\nAxial stop\nNone\nAX\nLateral stop horizontal\nNone\nQS\nStauff-clamp\nSC\nNone\nFriction bearing + Axial stop vertical, axial\nNone\nGLAX\nThrust bearing + Axial stop all movements\nNone\nFLAX\nLateral stop + Axial stop horizontal lateral, axial\nNone\nQSAX\nThrust bearing vertical, guiding in the global X axis\nNone\nFLVX\nThrust bearing vertical, guiding in the global Y axis\nNone\nFLVY\nThrust bearing vertical, guiding in the global Z axis\nNone\nFLVZ\nThrust bearing vertical, guiding in the global X and Y axis\nNone\nFLVXY\nThrust bearing vertical, guiding in the global X and Z axis\nNone\nFLVXZ\nThrust bearing vertical, guiding in the global Y and Z axis\nNone\nFLVYZ\nLateral stop in vertical pipe\nNone\nQSV\nLateral stop in vertical pipe in the global X axis\nNone\nQSVX\nLateral stop in vertical pipe in the global Y axis\nNone\nQSVY\nLateral stop in vertical pipe in the global Z axis\nNone\nQSVZ\nGeneral spring support\nNone\nFS\nSpring support\nFS\nFGL\nSpring support + guidance\nNone\nFFL\nSpring support + axial stop\nFS\nFGLAX\nSpring support + guidance + axial stop\nFS\nFFLAX\nSpring support + guidance in vertical and global X direction\nFS\nFFLVX\nSpring support + guidance in vertical and global Y direction\nFS\nFFLVY\nSpring support + guidance in vertical and global Z direction\nFS\nFFLVZ\nSpring support + guidance in vertical and global X and Y direction\nFS\nFFLVXY\nSpring support + guidance in vertical and global X and Z direction\nFS\nFFLVXZ\nSpring support + guidance in vertical and global Y and Z direction\nFS\nFFLVYZ\nConstant support\nKS\nKGL\nConstant support + guidance\nKS\nKFL\nConstant support + axial stop\nKS\nKGLAX\nConstant support + guidance + axial stop\nKS\nKFLAX\nConstant support + guidance in vertical and global X direction\nKS\nKFLVX\nConstant support + guidance in vertical and global Y direction\nKS\nKFLVY\nConstant support + guidance in vertical and global Z direction\nKS\nKFLVZ\nConstant support + guidance in vertical and global X and Y direction\nKS\nKFLVXY\nConstant support + guidance in vertical and global X and Z direction\nKS\nKFLVXZ\nConstant support + guidance in vertical and global Y and Z direction\nKS\nKFLVYZ\nGeneral pivot support\nGS\nGS\nRigid pivot support vertical\nGS\nGSV\nRigid pivot support lateral\nGS\nGSQ\nRigid pivot support axial\nGS\nGSAX\nRigid pivot support in vertical pipe lateral in global X direction\nGS\nGSQVX\nRigid pivot support in vertical pipe lateral in global Y direction\nGS\nGSQVY\nRigid pivot support in vertical pipe lateral in global Z direction\nGS\nGSQVZ\nElastic pivot support vertical\nFS\nFGSV\nElastic pivot support lateral\nFS\nFGSQ\nElastic pivot support axial\nFS\nFGSAX\nElastic pivot support in vertical pipe lateral in global X direction\nFS\nFGSQVX\nElastic pivot support in vertical pipe lateral in global Y direction\nFS\nFGSQVY\nElastic pivot support in vertical pipe lateral in global Z direction\nFS\nFGSQVZ\nConstant pivot support vertical\nKS\nKGSV\nConstant pivot support lateral\nKS\nKGSQ\nConstant pivot support axial\nKS\nKGSAX\nConstant pivot support in vertical pipe lateral in global X direction\nKS\nKGSQVX\nConstant pivot support in vertical pipe lateral in global Y direction\nKS\nKGSQVY\nConstant pivot support in vertical pipe lateral in global Z direction\nKS\nKGSQVZ\n*none = undefined\nA particular hanger construction can be chosen for calculation in Rohr2.\n\n\n\nUSTHTYP\nUSTSCHTYP\nUSTHTYP\nUSTSCHTYP\nUSTHTYP\nKH\nDescription\nWitzenmann\nRohr2\n:USTHTYP\n:USTSCHTYP"}
{"Headers": "If a hanger is calculated with Rohr2, the UDA :USTSCHTYP contains the calculated data", "Content": "If a hanger is calculated with Rohr2, the UDA :USTSCHTYP contains the calculated data. If the hanger point is transferred to Rohr2 again this data is used.\nIf the UDA is empty or contains invalid data, the UDA :USTHTYP is transferred to Rohr2 if it is valid.\nIf both UDAs contain invalid data, the default standard hanger type is transferred.\n\n\n\n:USTSCHTYP\n:USTHTYP"}
{"Headers": " the transfer procedure of Rohr2 data", "Content": "During the transfer procedure of Rohr2 data, the calculated hanger type is written to the UDA :USTSCHTYP. Additionally, the Witzenmann hanger type is determined and written to the UDA :USTHTYP.\n\n\n\n:USTSCHTYP\n:USTHTYP"}
{"Headers": "the UST-UDAs are not available", "Content": "If the UST-UDAs are not available, a message is displayed asking to contact the system administrator. Without the UDAs, the interface does not work.\n\nThe error can be caused by:\nIt is possible that write access to some support elements is not available due to claims, locks or general read-only access.\nIn addition to the error messages, all support elements that cannot be transferred are listed in an Error window. Error descriptions are listed in an r2hangerror file.\nThe respective DICT Database (DB) is not created in the Admin module.\nThe respective DICT DB is not included in the current MDB or is deferred.\nThe required UDAs are not included in the DICT DB. For further information, refer to Prerequisites.\nThe DICT DB is not compiled.\nThe respective DICT Database (DB) is not created in the Admin module.\nThe respective DICT Database (DB) is not created in the Admin module.\nThe respective DICT DB is not included in the current MDB or is deferred.\nThe respective DICT DB is not included in the current MDB or is deferred.\nThe required UDAs are not included in the DICT DB. For further information, refer to Prerequisites.\nThe required UDAs are not included in the DICT DB. For further information, refer to Prerequisites.\nThe DICT DB is not compiled.\nThe DICT DB is not compiled.\n\n\n\nPrerequisites\nPrerequisites\nError"}
{"Headers": "Defines data transfer settings between AVEVA E3D Design and Rohr2.", "Content": "Defines data transfer settings between AVEVA E3D Design and Rohr2.\n\nThe AVEVA Pipe Stress Interface - R2: Settings window is opened with default values. Modified settings can be saved in a central .INI file (%R2STRESS%\\rtwoexportoption.ini) or in a project specific .INI file (%xyzR2STRESS%\\rtwoexportoption.ini). The window is then opened with saved values.\nOrder Description\nDefines the order using description text. For further information, refer to Order Description.\nGeneral\nDefines the environmental temperature and direction of gravity. For further information, refer to General.\nPipe/Pipe Components\nDefines Pipe/Component data transfer settings. For further information, refer to Pipe/Pipe Components.\nExpansion Joints\nDefines expansion joint data transfer settings. For further information, refer to Expansion Joints.\nHangers and Supports\nDefines hanger and support data transfer settings. For further information, refer to Hangers and Supports.\nLoad Settings File\nOpens the file browser to load settings from a file.\nSave Settings File\nOpens the file browser to save the current settings to a file.\nApply\nApplies the data transfer settings.\nCancel\nDiscards any changes and closes the AVEVA Pipe Stress Interface - R2: Settings window.\nOrder Description\nDefines the order using description text. For further information, refer to Order Description.\nGeneral\nDefines the environmental temperature and direction of gravity. For further information, refer to General.\nPipe/Pipe Components\nDefines Pipe/Component data transfer settings. For further information, refer to Pipe/Pipe Components.\nExpansion Joints\nDefines expansion joint data transfer settings. For further information, refer to Expansion Joints.\nHangers and Supports\nDefines hanger and support data transfer settings. For further information, refer to Hangers and Supports.\nLoad Settings File\nOpens the file browser to load settings from a file.\nSave Settings File\nOpens the file browser to save the current settings to a file.\nApply\nApplies the data transfer settings.\nCancel\nDiscards any changes and closes the AVEVA Pipe Stress Interface - R2: Settings window.\n\n\n\n\nOrder Description\nGeneral\nPipe/Pipe Components\nExpansion Joints\nHangers and Supports\nAVEVA Pipe Stress Interface - R2: Settings\nOrder Description\nOrder Description\nGeneral\nGeneral\nPipe/Pipe Components\nPipe/Pipe Components\nExpansion Joints\nExpansion Joints\nHangers and Supports\nHangers and Supports\nLoad Settings File\nSave Settings File\nApply\nCancel"}
{"Headers": "Defines the order using description text.", "Content": "Defines the order using description text.\n\nThe order information is displayed in report headings or drawings in Rohr2. Alternatively, AVEVA E3D Design commands or any standard text can be used. For example, CURRENT PROJECT.\nAVEVA E3D Design commands must be entered directly, while standard text requires vertical bars as boundaries \" | \".\n\n\n\nCURRENT PROJECT"}
{"Headers": "Defines the environmental temperature and direction of gravity.", "Content": "Defines the environmental temperature and direction of gravity.\n\nEnvironment Temperature\nInput a value to define the environment temperature.\nDirection of Gravity\nAvailable values are +X, - X, +Y, -Y, +Z, or -Z. The default value is -Z.\nColors\nModifies the export list colors. For further information, refer to Export Geometry from E3D to Rohr2.\nSite\nDefines the site name that the displacement model is read into.\nEnvironment Temperature\nInput a value to define the environment temperature.\nDirection of Gravity\nAvailable values are +X, - X, +Y, -Y, +Z, or -Z. The default value is -Z.\nColors\nModifies the export list colors. For further information, refer to Export Geometry from E3D to Rohr2.\nSite\nDefines the site name that the displacement model is read into.\n\n\n\n\nExport Geometry from E3D to Rohr2\nExport Geometry from E3D to Rohr2"}
{"Headers": "Defines pipe/component data transfer settings.", "Content": "Defines pipe/component data transfer settings.\nSettings must be specified so that values can be determined by attributes or UDAs of PIPE, BRAN or BRAN MEM elements or associated elements, for example SPEC, SPCO or COMPREF.\n\n\n\n\nPIPE\nBRAN\nBRAN MEM\nSPEC\nSPCO\nCOMPREF"}
{"Headers": "Defines expansion joint data transfer settings.", "Content": "Defines expansion joint data transfer settings.\n\n\n\n"}
{"Headers": "Defines hanger and support data transfer settings.", "Content": "Defines hanger and support data transfer settings.\n\nThe AVEVA E3D Design elements ATTA, SHU, and SUPPO can be used for hanger or support points. The default value is the attachment point.\nAttachment and support points are only transferred to Rohr2 if the value of the ATT type attribute is set to HANG, NULL, or is empty and the value of the FStatus attribute is not set to INSULATION.\nBoth elements are provided with the UDAs :USTHTYP (hanger type) and :USTSCHTYP (stress calculated hanger type).\nThe UDA :USTHTYP can be used to define a hanger type before stress calculation.\nThe selection is limited by the Witzenmann hanger types.\nThe UDA :USTSCHTYP is set by Rohr2 and contains the hanger type after stress calculation by Rohr2. If there is an equivalent Witzenmann hanger type, the UDA :USTHTYP is overwritten during import of Rohr2 data.\nWhen transferring geometry to Rohr2, the UDA :USTSCHTYP is checked for a hanger type that has already been transferred from Rohr2. In that case, it would be transferred to Rohr2 again. If the UDA does not contain a valid value, the UDA :USTHTYP is analysed and transferred if necessary. If this UDA also does not contain a valid value, the standard hanger type is used.\nThe advantage of the procedure is that hanger types do not have to be defined AVEVA E3D Design. The stress calculator defines a default hanger type for the first stress calculation in Rohr2. For example, it is possible to define a constant hanger for steam pipes or a friction-type bearing for water pipes as a default.\nThe following alternatives can be selected:\nConstant hanger <Standard>\nRigid hanger\nFriction-type bearing\nSpring hanger\nConstant hanger <Standard>\nConstant hanger <Standard>\nRigid hanger\nRigid hanger\nFriction-type bearing\nFriction-type bearing\nSpring hanger\nSpring hanger\n\n\n\nATTA\nSHU\nSUPPO\nATT\nHANG\nNULL\nFStatus\nINSULATION\n:USTHTYP\n:USTSCHTYP\n:USTHTYP\n:USTSCHTYP\n:USTHTYP\n:USTSCHTYP\n:USTHTYP"}
{"Headers": "Implements complex structure in the R2 interface.", "Content": "Implements complex structure in the R2 interface.\nATTA name !!attaname() and PCOM classification !!pcomClasses() are displayed in the AVEVA Pipe Stress Interface - R2: Settings window.\nBoth are provided as an example and placed in the PMLLIB path below userfunction. The !!attaname() as an example:\n\n\n\nATTA\n!!attaname()\nPCOM\n!!pcomClasses()\nAVEVA Pipe Stress Interface - R2: Settings\nPMLLIB\nuserfunction\n!!attaname()\n-------------------------------------------------------\ndefine function !!attaName() is string\nif (!!ce.type inset('ATTA','ANCI','LUANCI')) then\nreturn !!ce.stext & '-' & !!ce.:mdssuppfunc\nelse\nreturn !!ce.name\nendif\nendfunction\n-------------------------------------------------------"}
{"Headers": "Functionality is available to support the transfer of Lap Joint Stub End (LJSE) elements to Rohr2.", "Content": "Functionality is available to support the transfer of Lap Joint Stub End (LJSE) elements to Rohr2.\nThe LJSE and the associated flange are combined into a single FLA component to be transferred to Rohr2.\nThe example displays a set of LJSE with associated lapped flanges.\n\nWhen the LJSE is transferred to Rohr2, instead of being transferred as two separate components, the LJSE and FLAN are transferred as a single FLA entry in the Rohr2 neutral file. For example:\n\nBecause the two components from AVEVA E3D Design are combined into a single component, some of the transferred data is derived from the LJSE and some of the data is derived from the FLAN.\nThe table indicates how the data is transferred to the single FLA entry in the neutral file and what element the data is derived from.\nAttribute\nExpression\nE3D Element\nMore Info\nComponent Description\nNAME\nLJSE\nMaterial Description\nMTXX\nLJSE\nWeight of elements (kg)\nGWEI\nFLAN + LJSE\nWeight is the LJSE weight and FLAN weight added together.\nWall Thickness ppoint\n1 (mm)\npwallt(1)\nLJSE\nWall Thickness ppoint\n2 (mm)\npwallt(2)\nLJSE\nWall Thickness ppoint\n3 (mm)\npwallt(3)\nLJSE\nWall Thickness ppoint\n4 (mm)\npwallt(4)\nLJSE\nWall Thickness Outside Tolerance (%)\nLJSE\nWall Thickness Inside Tolerance (%)\nLJSE\nNorm / Standard\nFLAN\nNORM obtained from the flange.\nBTK\nFLAN\nThe bolt thickness is taken from the flange.\nAttribute\nExpression\nE3D Element\nMore Info\nComponent Description\nNAME\nLJSE\n\nMaterial Description\nMTXX\nLJSE\n\nWeight of elements (kg)\nGWEI\nFLAN + LJSE\nWeight is the LJSE weight and FLAN weight added together.\nWall Thickness ppoint\n1 (mm)\npwallt(1)\nLJSE\n\nWall Thickness ppoint\n2 (mm)\npwallt(2)\nLJSE\n\nWall Thickness ppoint\n3 (mm)\npwallt(3)\nLJSE\n\nWall Thickness ppoint\n4 (mm)\npwallt(4)\nLJSE\n\nWall Thickness Outside Tolerance (%)\n\nLJSE\n\nWall Thickness Inside Tolerance (%)\n\nLJSE\n\nNorm / Standard\n\nFLAN\nNORM obtained from the flange.\nBTK\n\nFLAN\nThe bolt thickness is taken from the flange.\nMuch like creating a set or weld neck flanges, the gasket is ignored completely and any geometry length of the gasket is added onto the length of one of the flanges in the flange set.\n\n\n\nAttribute\nExpression\nE3D Element\nMore Info"}
{"Headers": "Database Concepts", "Content": "This reference manual describes in detail the structure and methods of the internal databases used within AVEVA E3D Design. It is written for System Administrators who may be involved in maintaining projects, and the databases from which they are created.\n\n\n"}
{"Headers": "Information is provided on project organization", "Content": "Information is provided on project organization, the definition of teams and multiple database and the splitting of data across multiple databases.\n\n\n"}
{"Headers": "create a Project", "Content": "In order to create data, you must first create a Project.\nA Project consists of:\nA project starts with just the System, Comms and Misc DBs.\nYou will then have to create other DBs for users to work on. The various visible DB types are:\nSystem\nContains details on DBs, Multiple Databases (MDBs), teams etc in the project\nDictionary\nContains User Defined Attribute (UDA) and User Defined Element Type (UDET) definitions\nProperty\nContains units for different properties\nCatalog\nContains Catalog and specification information\nModel\nContains Plant design information\nDraw\nContains drawing information\nSPOOL\nContains spool information\nMaterials\nContains hull material information\nDiagrams\nContains Schematic information\nTransaction\nUsed by Global to record transactions\nSCHEMATIC\nContains PI&D (Schematic) information\nMANU\nContains detailed manufacturing data\nNSEQ\nStores name sequences\nSystem\nContains details on DBs, Multiple Databases (MDBs), teams etc in the project\nDictionary\nContains User Defined Attribute (UDA) and User Defined Element Type (UDET) definitions\nProperty\nContains units for different properties\nCatalog\nContains Catalog and specification information\nModel\nContains Plant design information\nDraw\nContains drawing information\nSPOOL\nContains spool information\nMaterials\nContains hull material information\nDiagrams\nContains Schematic information\nTransaction\nUsed by Global to record transactions\nSCHEMATIC\nContains PI&D (Schematic) information\nMANU\nContains detailed manufacturing data\nNSEQ\nStores name sequences\nTypically there will be many DBs of each type within a project.\nAn example of a simple project is as follows:\n\nDBs may be included from other projects.\nEach DB has a unique DB number. User DBs have numbers in the range 1-7000. The range 7000-8000 is reserved for AVEVA supplied databases. The range 8000-8192 is reserved for system databases.\nThe DB number is assigned to the DB on creation. You may specify the DB number. If not specified by you then the next available DB number is used.\nThere may never be two DBs with the same DB number in a single project. Thus to include a DB from another project, that DB number must be unused in the target project.\nOne each of System, Comms, and Misc Databases (DBs)\nMultiple Design, Catalog, Drawing, and Dictionary DBs\nVarious picture files\nOne each of System, Comms, and Misc Databases (DBs)\nOne each of System, Comms, and Misc Databases (DBs)\nMultiple Design, Catalog, Drawing, and Dictionary DBs\nMultiple Design, Catalog, Drawing, and Dictionary DBs\nVarious picture files\nVarious picture files\n\n\n\nSystem\nDictionary\nProperty\nCatalog\nSPOOL\nMaterials\nDiagrams\nTransaction"}
{"Headers": "A Database (DB) belongs to one team", "Content": "For ease of working DBs are grouped into Teams and Multiple Databases (MDBs). A Database (DB) belongs to one team, but may be in many MDBs. You must specify the MDB to work on when entering AVEVA E3D Design.\nDetails of DBs, teams, and MDBs are stored in the system database.\nIt can be seen that DB /A is only in MDB /X, whereas DB /B is in both MDB /X and /Y.\nTeam access controls fundamental write access. Members of Team1 will always have write access to DBs /A and /B, and read access to the remainder. For members of Team2 it will be the opposite way around.\nIf a DB is included from another project then it is always read only regardless of team membership.\nThese concepts are discussed in detail in the Administrator User Guide.\n\n\n\nAdministrator User Guide\nAdministrator User Guide"}
{"Headers": "Theoretically there need only be one Database (DB) of each DB type. ", "Content": "Theoretically there need only be one Database (DB) of each DB type. The main reasons for there being more are:\nDBs are used as a fundamental means of access control. DBs are allocated to Teams, and only team members can modify a DB.\nWhilst the multiwrite facilities allow many writers per DB, it eases contention if the writers are not all accessing the same DB.\nThe easiest way to run a Global project is to have different DBs writable at different locations.\nThe granularity of propagation and distribution in Global is per DB\nIt allows different permutations of Multiple Databases (MDBs).\nIt allows specific DBs to be hidden from sub contractors\nInclusion in other projects is done on a DB basis.\nDBs are used as a fundamental means of access control. DBs are allocated to Teams, and only team members can modify a DB.\nDBs are used as a fundamental means of access control. DBs are allocated to Teams, and only team members can modify a DB.\nWhilst the multiwrite facilities allow many writers per DB, it eases contention if the writers are not all accessing the same DB.\nWhilst the multiwrite facilities allow many writers per DB, it eases contention if the writers are not all accessing the same DB.\nThe easiest way to run a Global project is to have different DBs writable at different locations.\nThe easiest way to run a Global project is to have different DBs writable at different locations.\nThe granularity of propagation and distribution in Global is per DB\nThe granularity of propagation and distribution in Global is per DB\nIt allows different permutations of Multiple Databases (MDBs).\nIt allows different permutations of Multiple Databases (MDBs).\nIt allows specific DBs to be hidden from sub contractors\nIt allows specific DBs to be hidden from sub contractors\nInclusion in other projects is done on a DB basis.\nInclusion in other projects is done on a DB basis.\n\n\n"}
{"Headers": "All data in a Dabacon database is stored in elements", "Content": "All data in a Dabacon database is stored in elements. Every element has a type, for example BOX. The type of element determines the attributes available on the element.\nEach DB type allows a different set of element types.\nDatabase attributes are described in Database Attributes\nThe elements are organized in a primary hierarchy. This is described in Database hierarchy.\n\n\n\nBOX\nBOX"}
{"Headers": "Every element has a reference number,", "Content": "Every element has a reference number, which is assigned when the element is created, and is unique to that element within the project. The reference number comprises two 32 bit integers. This is displayed in the form:\nThe first integer encodes the database number. This can be queried on the command line using Q DBNUMBER.\nThe second integer is a sequence number, starting at 0, and incrementing each time an element is created.\nThus, for example, the element with a reference number of =8193/0 will be the WORLD element (since this is always created first) created in Database (DB) 1.\nThe reference number is never changed once an element has been created.\n\n\n"}
{"Headers": "In AVEVA E3D Design any element may be given a name", "Content": "In AVEVA E3D Design any element may be given a name. The name always starts with a '/'. At the user level, it is this name that is typically used to identify an element. Names may of course be changed, thus there is no guarantee that the element named '/FRED' today is the same as the element named '/FRED' yesterday.\nAn element need not have a name. For these elements AVEVA E3D Design creates a constructed name, consisting of the relative position in the hierarchy up to the first named element.\nfor example, BOX 2 OF SUBEQUIPMENT 1 OF /VESS1\nWhilst the constructed name can be used to identify elements, its use is even more volatile than named elements, since the order of an element in a member's list may change.\nYou can duplicate the name of an element in a Design (DESI), Production (MANU), Schematic (SCHE) or Engineering (ENGI) databases in the current MDB. For example an element can be named `/FRED\u00b4 in the DESI database and a different element can be named \u00b4/FRED\u00b4 in the MANU database.\nAVEVA E3D Design is case sensitive and AVEVA recommends you stick to UPPERCASE characters. If you create an element named /FRED and at some later time you try to find it by typing /fred or /FreD, it will not be found.\n\n\n"}
{"Headers": "Current element", "Content": "At the user level there is a concept of current element.\nMost AVEVA E3D Design commands act on the current element. This is often referred to as the CE. There is an extensive set of commands to navigate around the database changing the CE.\n\n\n"}
{"Headers": "Element type", "Content": "For most elements, the element type may never be changed after creation. For example, once created, an element of type SITE will always be of type SITE until deleted.\nThere are a few exceptions to this rule where it makes sense. For example, BENDs may be changed to ELBOs and vice versa.\n\n\n"}
{"Headers": "hierarchical data model", "Content": "Information is provided on the hierarchical data model, the user defined hierarchies, the element instances and the use case of primary hierarchy.\n\n\n"}
{"Headers": "The database schemas in AVEVA E3D Design are fixed by AVEVA.", "Content": "The database schemas in AVEVA E3D Design are fixed by AVEVA.\nYou may, however, customize the allowed hierarchy using User Defined Element Types (UDETs).\nA UDET must be based on an existing system type. For example, you may define a UDET :PUMP which is based on an Equipment. By default, a UDET will have the same allowed members and allowed owners as a base type. This can be customised to be a subset of that allowed on the base type, for example, you might decide that SUBE are not allowed under a :PUMP even though they are allowed under an Equipment (EQUI).\nUDETs based on zones may own other UDETs based on zones. This allows very flexible data models to be built.\n\n\n"}
{"Headers": "A new database (DB) starts", "Content": "A new database (DB) starts with a single world element with name '/*'. Users will then create instances of other element types. For example, a system user might create an initial hierarchy of sites and zones in a Model DB, leaving it to other users to create the actual Plant items.\nAn element instance will always be created within the primary hierarchy. For example, a new ZONE element must be created under an existing SITE. It cannot be created as a 'freestanding' element outside the existing hierarchy.\nThe actual element hierarchy can be viewed with the AVEVA E3D Design explorer.\nAll element instances within a multiple Database (MDB) are accessible at all times.\n\n\n"}
{"Headers": "The primary hierarchy", "Content": "The primary hierarchy is used as follows:\nIt is used to create the 'constructed' name for unnamed elements.\nWhen an element is deleted, all descendants in the primary hierarchy are deleted.\nThe COPY command will copy an element and all its primary descendants.\nClaiming elements relies on the primary hierarchy.\nCollections work on the primary hierarchy.\nMost commands assume that the action is to be performed on the given element and its descendants in its primary hierarchy, for example,. adding a ZONE to a 3D view will add everything below that ZONE.\nIn the Design Database (DB), world positions and orientations are concatenated according to the primary hierarchy.\nIt is used to create the 'constructed' name for unnamed elements.\nIt is used to create the 'constructed' name for unnamed elements.\nWhen an element is deleted, all descendants in the primary hierarchy are deleted.\nWhen an element is deleted, all descendants in the primary hierarchy are deleted.\nThe COPY command will copy an element and all its primary descendants.\nThe COPY command will copy an element and all its primary descendants.\nClaiming elements relies on the primary hierarchy.\nClaiming elements relies on the primary hierarchy.\nCollections work on the primary hierarchy.\nCollections work on the primary hierarchy.\nMost commands assume that the action is to be performed on the given element and its descendants in its primary hierarchy, for example,. adding a ZONE to a 3D view will add everything below that ZONE.\nMost commands assume that the action is to be performed on the given element and its descendants in its primary hierarchy, for example,. adding a ZONE to a 3D view will add everything below that ZONE.\nIn the Design Database (DB), world positions and orientations are concatenated according to the primary hierarchy.\nIn the Design Database (DB), world positions and orientations are concatenated according to the primary hierarchy.\n\n\n"}
{"Headers": "An element can only exist", "Content": "An element can only exist once in the primary data hierarchy. Secondary hierarchies, such as Group Sets (GPSETs), allow elements to appear more than once in the overall hierarchy. For example a PIPE will appear below a ZONE in the primary hierarchy. The same PIPE may also be added to a GPSET element. This is useful for collecting elements according to different criteria.\nThe diagram below shows a typical multi hierarchy where the secondary links are dotted.\n\nMost commands will work on secondary hierarchies. For example, if /GPSET1 is added to a 3D view then this is equivalent to adding both /VESS1 and /PUMP2 to the 3D view. However, there are exceptions to this. In particular deleting a GROUP will not delete the GROUP members; thus deleting /GPSET1 will not delete /VESS1 and /PUMP2.\nUnlike the Primary hierarchy, secondary hierarchies may span different databases (DBs).\n\n\n"}
{"Headers": "Every element may have a number of attributes", "Content": "Every element may have a number of attributes. All elements have the following attributes:\nNAME\nthe element's name\nTYPE\nthe element's type\nLOCK\nif set, then the element may not be modified\nOWNER\nthe element's owner\nMEMBERS\nthe current members of the element\nNAME\nthe element's name\nTYPE\nthe element's type\nLOCK\nif set, then the element may not be modified\nOWNER\nthe element's owner\nMEMBERS\nthe current members of the element\nThe remaining attributes vary depending on the element type. The Database Schema defines which attributes are available on an element type. The allowed attributes for an element type may be ascertained using Programmable Macro Language (PML) objects and other command queries.\nAttributes may be one of the following types:\nRef\nRef Array\nPosition\nDirection\nOrientation\nAttribute\nElementType (or Noun)\nA 'Ref' type is a pointer to another element. For example, on a BRANCH element the Connection Reference (CREF) attribute points to the connected NOZZLE. The use of Ref attributes enables AVEVA E3D Design to model networks and other cross relationships.\nThe attribute type dictates how the attribute can be set with PML or specific syntax.\n\n\n\nNAME\nTYPE\nLOCK\nOWNER\nMEMBERS"}
{"Headers": "You can extend the allowed attributes for any element type", "Content": "You can extend the allowed attributes for any element type, including a /ser Defined Element Type (UDET), by defining User Defined Attributes (UDAs). For example, you could define a UDA called :SUPPLIER of type string on all piping components. The newly defined UDA will then exist on all applicable elements, existing and new. If the definition of a UDA is changed then this will also apply to all existing instances.\nHaving defined a UDA, it is accessed in the same way as any other attribute.\n\n\n"}
{"Headers": "In addition to the attributes stored on the database", "Content": "In addition to the attributes stored on the database, there are a large number of pseudo attributes. The value of pseudo attributes is calculated at the time of making the query.\nFor example, the CUTLENGTH attribute on SCTN elements is a pseudo attribute calculated at the point of doing the query.\nThere is a lot of functionality presented via pseudo attributes. Currently there are over 1200 pseudo attributes.\nSince the value of a pseudo attribute is calculated from other attributes, it is not generally possible to set their value directly.\n\n\n"}
{"Headers": "Attributes and element types have a global name space", "Content": "Attributes and element types have a global name space. This means that an attribute such as XLEN will have an identical meaning wherever it exists.\nSimilarly if an element type is valid in more than one database type, the definition of the element type will be identical in each.\n\n\n"}
{"Headers": "introduction attributes", "Content": "Some real attributes are simply numbers, counts, quantities etc. Others represent real physical quantities such as distances, areas, densities, angles etc. The type of physical quantity is called its physical dimension, often shortened in unambiguous contexts to its dimension. Real attributes (stored, derived, user defined etc.) can all be assigned a physical dimension and this determines the type of data stored in these attributes wherever and whenever they occur in the database. The most common dimensions of attributes are of length (internally set to either DIST or BORE). There are many others supported including density, mass, pressure, temperature, area, volume and angle.\nThe dimension of an attribute is held in the database in its (ambiguously named) UNIT field. It may be queried directly using the VAR ATTDEF attributeName UNIT syntax, and the !attribute.units() PML ATTRIBUTE object method, refer to PML ElementType Class.\n\n\n\nPML ElementType Class\nPML ElementType Class"}
{"Headers": "Information a database", "Content": "Information is provided on database expressions and rules to define a database.\n\n\n"}
{"Headers": "Database expression may be defined as a rule", "Content": "Database expressions can be of the following types:\nThe contents of an expression may contain the standard operator and mathematical functions along with the names of attributes and element identification.\nThis expression simply multiplies the three attributes XLEN, YLEN, ZLEN together and then multiplies by two.\nThe attributes refer to the current element. If attributes of other elements are required then the OF syntax is used.\nThe 'OF' keyword makes sure that the AREA attribute is obtained from the owner of the current element rather than the current element itself.\nThe main uses of expressions are:\nDatabase expressions are very similar to Programmable Macro Language (PML) expressions. The major difference is that database expressions may not contain other PML variables or functions. For example, (XLEN * !MYVAR) is not a valid database expression.\n(XLEN * YLEN * ZLEN * 2)\n(PURP EQ 'HS' AND AREA OF OWNER EQ 1)\nalgebraic\nboolean (or logical)\ntext\nElement ID\nposition\ndirection\norientation\nalgebraic\nalgebraic\nboolean (or logical)\nboolean (or logical)\ntext\ntext\nElement ID\nElement ID\nposition\nposition\ndirection\ndirection\norientation\norientation\nCatalog parameterization\nTemplate parameterization\nRules\nDrafting line styles\nUser level collections and report\nCatalog parameterization\nCatalog parameterization\nTemplate parameterization\nTemplate parameterization\nRules\nRules\nDrafting line styles\nDrafting line styles\nUser level collections and report\nUser level collections and report\n\n\n"}
{"Headers": "An attribute may be defined as a rule", "Content": "An attribute may be defined as a rule. For example, the attribute XLEN may be defined as a rule by the expression (YLEN * 2).\nThe OF syntax is often used in Rule expressions to refer to other elements, for example, (YLEN OF /FRED * 2)\nThe result of the rule is stored against the attribute as for other attributes.\nThere are commands to recalculate the rule.\nRules may be either static or dynamic. If static, then the rule result will only be recalculated on demand. If dynamic, then the result will be recalculated every time an attribute within the expression changes, for example, for the above rule, if YLEN is modified, then XLEN will be recalculated automatically. The dynamic linkage of rules may be across elements and across Databases (DBs).\n\n\n"}
{"Headers": "Database using data listings", "Content": "Information is provided on the possibilities to dump out the database using data listings and the Reconfigurer.\n\n\n"}
{"Headers": "Data listings DATALs", "Content": "Data listings (DATALs) capture the state of the database in the form of AVEVA E3D Design commands. All element data including all attributes, User Defined Attributes (UDAs) and rules will be captured. They are similar in concept to Extensible Markup Language (XML) output. These files can then be read back in via the command line.\nData listings are used as follows:\nLong term archiving\nCopying parts of a Database (DB) between projects\nFor general information.\nLong term archiving\nLong term archiving\nCopying parts of a Database (DB) between projects\nCopying parts of a Database (DB) between projects\nFor general information.\nFor general information.\n\n\n"}
{"Headers": "Reconfiguration DATAL Data listing", "Content": "Reconfigurer is similar to Data Listing (DATAL) in that it dumps out the state of the data.\nThe data can be dumped to either binary or text file. Using binary files is quickest.\nReconfigurer is faster than DATAL and is recommended if whole DBs or world level elements are to be transferred. DATAL or the copy facilities is recommended if lower level elements are to be transferred.\n\n\n"}
{"Headers": "Data Access Control", "Content": "Data Access Control (DAC) is the mechanism that protects information handled by the system from accidental or unauthorised manipulation.\nThe basic access control available is known as 'Team Owning Databases'. It implements access control on database level by simply giving the members of the team owning the database full access and others read-only to data held in particular databases.\nA more sophisticated access control is implemented in the form of Access Control Rights (ACRs). ACR allows the administrator of the system to apply a more fine grained access control over the model. The following figure illustrates the DAC database hierarchy.\n\nAn ACR is defined through two entities:\nA PEROP defines the access rights given for a number of pre-defined operations for one or more elements.\nOne or more ACRs may be assigned to a user granting and denying access to the model.\nFor a user to gain update access to a particular element two rules apply:\nManagement tools are available for DAC through the Admin module. Control of DAC is also available through Programmable Macro Language (PML).\nA PEROP consists of three parts:\nThe PEROP may further restrict the elements it applies to by a qualifying condition. The qualifying conditions is an AVEVA E3D Design statement that should evaluate to true to qualify the PEROP.\nThe following operations are available through PEROPs\nEach of these operations may be set to\nAllow\nThe operation is permitted\nDisallow\nThe operation is not permitted\nIgnore\nThe PEROP does not define whether this operation is permitted or not\nAllow\nThe operation is permitted\nDisallow\nThe operation is not permitted\nIgnore\nThe PEROP does not define whether this operation is permitted or not\nOptionally the PEROP may further restrict which attributes it allows modification to by specifying a list of attributes that it either includes or excludes from allowing modification to.\nThe PEROP also holds the message that the system will issue if the PEROP denies attempted operation.\nA ROLE, which is a collection of rules called Permissible Operations (PEROPs).\nA SCOPE, which defines to what part of the model the ROLE applies. The SCOPE may be an expression, for example, all ZONE WHERE (FUNC eq 'TEAMA')\nA ROLE, which is a collection of rules called Permissible Operations (PEROPs).\nA ROLE, which is a collection of rules called Permissible Operations (PEROPs).\nA SCOPE, which defines to what part of the model the ROLE applies. The SCOPE may be an expression, for example, all ZONE WHERE (FUNC eq 'TEAMA')\nA SCOPE, which defines to what part of the model the ROLE applies. The SCOPE may be an expression, for example, all ZONE WHERE (FUNC eq 'TEAMA')\nAt least one PEROP in a ROLE assigned to a USER must grant the update operation.\nNo one PEROP must explicitly deny the operation.\nAt least one PEROP in a ROLE assigned to a USER must grant the update operation.\nAt least one PEROP in a ROLE assigned to a USER must grant the update operation.\nNo one PEROP must explicitly deny the operation.\nNo one PEROP must explicitly deny the operation.\nThe Element it applies to\nThe operations which can be performed on those elements\nOptionally the Attributes that may be modified.\nThe Element it applies to\nThe Element it applies to\nThe operations which can be performed on those elements\nThe operations which can be performed on those elements\nOptionally the Attributes that may be modified.\nOptionally the Attributes that may be modified.\nCreate\nModify\nDelete\nClaim\nIssue\nDrop\nOutput\nExport\nCopy\nCreate\nCreate\nModify\nModify\nDelete\nDelete\nClaim\nClaim\nIssue\nIssue\nDrop\nDrop\nOutput\nOutput\nExport\nExport\nCopy\nCopy\n\n\n\nAllow\nDisallow\nIgnore"}
{"Headers": "Apply modifications", "Content": "The following checks are applied to all modifications:\nThe claiming process is described in Claiming Elements.\nCheck access control\nCheck that the DB is open in write\nCheck that the element's LOCK flag is false\nIf a multiwrite Database (DB) then do a claim check, and claim if needed\nCheck access control\nCheck access control\nCheck that the DB is open in write\nCheck that the DB is open in write\nCheck that the element's LOCK flag is false\nCheck that the element's LOCK flag is false\nIf a multiwrite Database (DB) then do a claim check, and claim if needed\nIf a multiwrite Database (DB) then do a claim check, and claim if needed\n\n\n"}
{"Headers": "The engineering integrity", "Content": "The engineering integrity is always maintained for any database modification.\nThe integrity checks are applied below the database interface. Thus modifying the database is always safe whether done via PML commands or C#.\nThe checks are applied to individual attributes and element types. For example the OBST attribute can only ever be set to 0,1 or 2. AVEVA E3D Design will always check that this is the case prior to allowing the modification.\n\n\n"}
{"Headers": "Elements may be created", "Content": "Elements may be created. They are always created one at a time, and may only be created at a legitimate point in the primary hierarchy.\nOn creation, a unique reference number will be assigned. The method by which the default reference number is generated is described in User Defined Hierarchies.\nIt is possible to create an element with a specified reference number, provided it is unused and valid for the Database (DB). This functionality is provided for certain specialized situations (such as recreating an exact copy of a DB, so that all references to elements from other DBs remain valid), and is not recommended for general use.\nThe attributes will be set to their default values. In some cases the default attribute values are cascaded down from the owning element.\n\n\n\nUser Defined Hierarchies\nUser Defined Hierarchies"}
{"Headers": "Elements may be deleted", "Content": "Elements may be deleted. All elements below the deleted element in the primary hierarchy will also be deleted.\nReference numbers of deleted elements are never reused.\n\n\n"}
{"Headers": "Elements may be copied", "Content": "Elements may be copied. There are options to copy a single element or an element and all its descendants. Elements may be copied between Databases (DBs). Any cross references entirely within the copied structure will be updated to point to the newly created elements.\nElements are always copied on top of an existing element of the same type.\nThere are various options on the copy command to allow:\nAdditional potential errors at create are:\nThe copied elements to be renamed according to a given criteria\nWhether any attribute rules are to be rerun on the copied element. (Rules are described in Reconfigurer)\nThe copied elements to be renamed according to a given criteria\nThe copied elements to be renamed according to a given criteria\nWhether any attribute rules are to be rerun on the copied element. (Rules are described in Reconfigurer)\nWhether any attribute rules are to be rerun on the copied element. (Rules are described in Reconfigurer)\nThe element may not be copied to an element of a different type\nThe element may not be copied to an element of a different type\nThe element may not be copied to an element of a different type\n\n\n\nReconfigurer\nReconfigurer"}
{"Headers": "Elements may be moved", "Content": "Elements may be moved to a different point in the Database (DB) or to a different DB.\nThe Element and all its descendants will be moved.\nIf the element is moved to a different DB, then its reference number is changed. All reference attributes pointing to the moved structure will be updated.\nAdditional potential errors at move are:\nThe element is not allowed in the members list of the new owner\nThe element is not allowed in the members list of the new owner\nThe element is not allowed in the members list of the new owner\n\n\n"}
{"Headers": "Modifying Atrributes", "Content": "The following checks are applied when modifying attributes:\nSometimes modifying one attribute will actually cause a number of attributes to change. There are two main cases where this might happen:\nThe integrity of cross referenced attributes is maintained when one end of the connection is changed. Changing one end of a connection will also change the following:\nIn essence, changing one value may result in four elements being updated.\nFor example, consider the following:\n\nAfter setting the CREF on /N1 to /B1, the end result is:\n\n\n\n"}
{"Headers": "A dynamic rule", "Content": "A dynamic rule will automatically respond to changes which affect the attributes referred to in the rule.\nFor example, we set a rule on YLEN of /MYBOX to be (YLEN OF /FRED * 2). Thus if YLEN on /FRED changes then YLEN on /MYBOX will be updated automatically. However there are reasons why the automatic propagation of dynamic rules may fail, as follows:\nNote also that only static rules are not automatically updated. For these reasons there are commands to verify that rule results are up to date.\n\n\n"}
{"Headers": "defining a session by saving or getting the work", "Content": "Information is provided on the handling of a session, for example, defining a session by saving or getting the work, creating a stamp, displaying the session history, setting a comparison date and merging changes.\n\n\n"}
{"Headers": "flush operation", "Content": "A new session is created for every flush operation. Thus it is much better to flush a large number of elements in one go rather than flush them individually.\n\n\n"}
{"Headers": "Global allows Databases to be spread across different locations", "Content": "Global allows Databases (DBs) to be spread across different locations. Global propagates changes from one location to another. The Global daemon does the propagation.\nWith global, there may be copies of a database or extract at multiple locations, but only one copy may be writeable. A database is said to be primary at a given location if it is writeable there, and secondary if it is not. A DB may be made primary at any location.\nDifferent extracts from the same extract family may be primary at different locations. This allows multiple different locations to modify the same DB.\n\n\n"}
{"Headers": "Change primary database (DB)", "Content": "Changes made to a primary database (DB) are propagated to the read only secondary DBs. The propagation algorithm just sends the new sessions. For example:\n\nIf this case the propagation algorithm will send the sessions 20 to 39 to the secondary location.\n\n\n"}
{"Headers": "Programmable Macro Language (PML) attribute ", "Content": "A Programmable Macro Language (PML) attribute instance may be created for a system attribute or a User defined Attribute (UDA).\nThe class should not be confused with the attribute value. The actual Attribute value for a particular Element can only be accessed via the DBREF class or via the QUERY command. Comparing two Attributes just compares whether they identify the same attribute, the comparison does not look at attribute values in any way.\n\n\n"}
{"Headers": " Attribute", "Content": "The Attribute instance can then be used for querying the \u2018meta data\u2019, that means, data about data. The methods of the class allow the following to be queried.\nString Type()\nAttribute type\nString Name()\nAttribute name\nString Description()\nAttribute description\nInt Hash()\nAttribute hash value\nint Length()\nAttribute length\nbool IsPseudo()\nWhether pseudo or not\nbool IsUda()\nWhether a User defined Attributes (UDA) or not\nstring querytext()\nAs output at the command line when querying attribute\nstring units\nEither BORE, DISTANCE or NONE\nReturns the unit field of the attribute which is the string of the hash code of the dimension of the attribute (BORE, DIST, MASS, ANGL, or for numbers of no physical quantity NONE). For UDAs it is the value of the UDA Type (UTYP) attribute.\nbool Noclaim()\nWhether attribute can be changed without doing a claim\nElementType array\nElementTypes\nList of Elements for which the attribute is valid. This only works for UDAs\nReal array limits\nMin/Max values for real/int types\nString array\nValidValues(ElementType)\nList of valid for text attributes. The list may vary with element type\nstring DefaultValue\n(ElementType)\nAttribute default. This only works for UDAs\nstring Category()\nDetermines the grouping of attributes on the \u2018Attribute Utility\u2019 form\nbool hyperlink()\nif true then the attribute value refers to an external file\nbool connection()\nif true then the attribute value will appear on the reference list form\nbool hidden()\nIf true then attribute will not appear on the Attribute utility form or after \u2018Q ATT\u2019\nbool protected()\nif true then attribute is not visible if a protected Databases (DB).\nString Type()\nAttribute type\nString Name()\nAttribute name\nString Description()\nAttribute description\nInt Hash()\nAttribute hash value\nint Length()\nAttribute length\nbool IsPseudo()\nWhether pseudo or not\nbool IsUda()\nWhether a User defined Attributes (UDA) or not\nstring querytext()\nAs output at the command line when querying attribute\nstring units\nEither BORE, DISTANCE or NONE\nReturns the unit field of the attribute which is the string of the hash code of the dimension of the attribute (BORE, DIST, MASS, ANGL, or for numbers of no physical quantity NONE). For UDAs it is the value of the UDA Type (UTYP) attribute.\nbool Noclaim()\nWhether attribute can be changed without doing a claim\nElementType array\nElementTypes\nList of Elements for which the attribute is valid. This only works for UDAs\nReal array limits\nMin/Max values for real/int types\nString array\nValidValues(ElementType)\nList of valid for text attributes. The list may vary with element type\nstring DefaultValue\n(ElementType)\nAttribute default. This only works for UDAs\nstring Category()\nDetermines the grouping of attributes on the \u2018Attribute Utility\u2019 form\nbool hyperlink()\nif true then the attribute value refers to an external file\nbool connection()\nif true then the attribute value will appear on the reference list form\nbool hidden()\nIf true then attribute will not appear on the Attribute utility form or after \u2018Q ATT\u2019\nbool protected()\nif true then attribute is not visible if a protected Databases (DB).\nString Type()\nAttribute type\nString Name()\nAttribute name\nString Description()\nAttribute description\nInt Hash()\nAttribute hash value\nint Length()\nAttribute length\nbool IsPseudo()\nWhether pseudo or not\nbool IsUda()\nWhether a User defined Attributes (UDA) or not\nstring querytext()\nAs output at the command line when querying attribute\nstring units\nEither BORE, DISTANCE or NONE\nReturns the unit field of the attribute which is the string of the hash code of the dimension of the attribute (BORE, DIST, MASS, ANGL, or for numbers of no physical quantity NONE). For UDAs it is the value of the UDA Type (UTYP) attribute.\nbool Noclaim()\nWhether attribute can be changed without doing a claim\nElementType array\nElementTypes\nList of Elements for which the attribute is valid. This only works for UDAs\nReal array limits\nMin/Max values for real/int types\nString array\nValidValues(ElementType)\nList of valid for text attributes. The list may vary with element type\nstring DefaultValue\n(ElementType)\nAttribute default. This only works for UDAs\nstring Category()\nDetermines the grouping of attributes on the \u2018Attribute Utility\u2019 form\nbool hyperlink()\nif true then the attribute value refers to an external file\nbool connection()\nif true then the attribute value will appear on the reference list form\nbool hidden()\nIf true then attribute will not appear on the Attribute utility form or after \u2018Q ATT\u2019\nbool protected()\nif true then attribute is not visible if a protected Databases (DB).\nNote:\nWe do yet not support direct usage of this class in other syntax.\n\n\n\nString Type()\nString Name()\nString Description()\nInt Hash()\nint Length()\nbool IsPseudo()\nbool IsUda()\nstring querytext()\nstring units\nbool Noclaim()\nElementType array\nElementTypes\nReal array limits\nString array\nValidValues(ElementType)\nstring DefaultValue\n(ElementType)\nstring Category()\nbool hyperlink()\nbool connection()\nbool hidden()\nbool protected()\nNote\n:"}
{"Headers": "ElementType", "Content": "An ElementType instance may be created for a system Element type or a User Defined Element Type (UDET).\nThe ElementType instance can then be used for querying the \u2018meta data\u2019. which means,. data about data. The methods of the class allow the following to be queried.\n\n\n"}
{"Headers": "The available methods", "Content": "The available methods are:\nstring Name()\nName of element type\nstring Description()\nDescription of element type\nint Hash()\nHash value\nbool IsUdet()\nWhether a User Defined Element Type (UDET) or not\nAttribute array\nsystemAttributes()\nList of system attributes (excludes User defined Attributes (UDAs))\nstring array DbType()s\nList of valid Database (DB) types\nstring ChangeType()\nIndicates if an element of this type may have it\u2019s type changed\nElementType SystemType()\nfor UDETs this is the base type\nElementType array\nUDETs derived from this type\nbool Primary()\nWhether the element is primary or not\nElementType array\nMemberTypes()\nValid members, including UDETs\nElementType array\nParentTypes()\nValid parents, including UDETs\nstring Name()\nName of element type\nstring Description()\nDescription of element type\nint Hash()\nHash value\nbool IsUdet()\nWhether a User Defined Element Type (UDET) or not\nAttribute array\nsystemAttributes()\nList of system attributes (excludes User defined Attributes (UDAs))\nstring array DbType()s\nList of valid Database (DB) types\nstring ChangeType()\nIndicates if an element of this type may have it\u2019s type changed\nElementType SystemType()\nfor UDETs this is the base type\nElementType array\nUDETs derived from this type\nbool Primary()\nWhether the element is primary or not\nElementType array\nMemberTypes()\nValid members, including UDETs\nElementType array\nParentTypes()\nValid parents, including UDETs\nstring Name()\nName of element type\nstring Description()\nDescription of element type\nint Hash()\nHash value\nbool IsUdet()\nWhether a User Defined Element Type (UDET) or not\nAttribute array\nsystemAttributes()\nList of system attributes (excludes User defined Attributes (UDAs))\nstring array DbType()s\nList of valid Database (DB) types\nstring ChangeType()\nIndicates if an element of this type may have it\u2019s type changed\nElementType SystemType()\nfor UDETs this is the base type\nElementType array\nUDETs derived from this type\nbool Primary()\nWhether the element is primary or not\nElementType array\nMemberTypes()\nValid members, including UDETs\nElementType array\nParentTypes()\nValid parents, including UDETs\nNote:\nWe do yet not support direct usage of this class in other syntax.\n\n\n\nstring Name()\nstring Description()\nint Hash()\nbool IsUdet()\nAttribute array\nsystemAttributes()\nstring array DbType()s\nstring ChangeType()\nElementType SystemType()\nElementType array\nbool Primary()\nElementType array\nMemberTypes()\nElementType array\nParentTypes()\nNote\n:"}
{"Headers": "Pseudo attributes", "Content": "There are a number of pseudo attributes that return values according to the element type, as follows:\nHLIS\nWORD(2000)\n\nList of all possible types in owning hierarchy\nLIST\nWORD(2000)\n\nList of all possible member types\nLLIS\nWORD(2000)\n\nList of all possible types in member hierarchy\nOLIS\nWORD(2000)\n\nList of all possible owner types\nREPTXT\nSTRING\n\nReporter text used for element type\n\n\nAttribute Name\nData Type\nQualifier\nDescription\nHLIS\nWORD(2000)\nList of all possible types in owning hierarchy\nLIST\nWORD(2000)\nList of all possible member types\nLLIS\nWORD(2000)\nList of all possible types in member hierarchy\nOLIS\nWORD(2000)\nList of all possible owner types\nREPTXT\nSTRING\nReporter text used for element type\n\n\n"}
{"Headers": "Database Modification", "Content": "This chapter describes the commands to create, copy and modify database elements.\n\n\n"}
{"Headers": "Database Modification", "Content": "As well as accessing the current content of a Database (DB), you may also (if you have Read/Write access rights) modify a DB in any of the following ways:\nCreate a new element at an appropriate level of the DB hierarchy; refer to Create a New Element.\nDelete an element from the DB hierarchy; refer to Delete an Element.\nReorganize the hierarchy, refer to Reorganize the DB Hierarchy:\nby rearranging members of an element into a different list order.\nby moving an element from one part of the hierarchy to another;\nDefine the attributes and offspring of a new element by copying the corresponding attribute, settings and member lists from another element; refer to Copy Attributes from One Element to Another.\nCreate a new element at an appropriate level of the DB hierarchy; refer to Create a New Element.\nCreate a new element at an appropriate level of the DB hierarchy; refer to Create a New Element.\nDelete an element from the DB hierarchy; refer to Delete an Element.\nDelete an element from the DB hierarchy; refer to Delete an Element.\nReorganize the hierarchy, refer to Reorganize the DB Hierarchy:\nby rearranging members of an element into a different list order.\nby moving an element from one part of the hierarchy to another;\nReorganize the hierarchy, refer to Reorganize the DB Hierarchy:\nDefine the attributes and offspring of a new element by copying the corresponding attribute, settings and member lists from another element; refer to Copy Attributes from One Element to Another.\nDefine the attributes and offspring of a new element by copying the corresponding attribute, settings and member lists from another element; refer to Copy Attributes from One Element to Another.\n\n\n\nCreate a New Element\nDelete an Element\nReorganize the DB Hierarchy\nCopy Attributes from One Element to Another\nCreate a New Element\nDelete an Element\nReorganize the DB Hierarchy\nCopy Attributes from One Element to Another"}
{"Headers": "Creation of a new element", "Content": "To create a new element within an existing Database (DB), you must first make sure that the Current Element (CE) is at a level within the hierarchy which can legally own the element to be created. For example, a Site can own a Zone, but it cannot own a Valve. To create a new Valve, you must be at Branch level. You must therefore navigate to the correct level by using one of the command options described in Database Navigation and Query Syntax.\nYou can then create a new element, set its attributes and, if required, create further elements as its members.\nIf you create an element without explicitly identifying its position in the Member List of the Current Element, the new element is inserted immediately after the Current List Position. To use this option, enter the command\nNEW element_type element_name\n(element_name is optional)\nNEW element_type element_name\n(element_name is optional)\nFor example, if the Current List Position is at member 4 (/VALV1) of the Member List.\n\nThe command\nadds a new Tee at list position 5 (between /VALV1 and /ELBO2) and names it /TEE2. The Member List of /BRAN1 thus becomes\n\nTo insert the new Tee as the first or last component in the Member List, access the Branch Head or Tail, respectively, before giving the NEW TEE command.\nTo create a new element at a specified list position, identify a list position adjacent to the required position and state which side of it the newly-created element is to go. The command syntax is one of the following:\nwhere element_name is again optional and where list_position may be specified in any of the ways described in Database Navigation and Query Syntax.\nConsider the following examples. Starting from the configuration shown, any of these commands creates a new Tee between /ELBO3 (list position 7) and /FLAN2 (list position 8):\nNEW TEE AFTER /ELBO3\nSpecify name or refno\nNEW TEE BEFORE 8\nSpecify list position number\nNEW TEE BEFORE FLAN 2\nSpecify member type and number (second Flange in the list)\nNEW TEE AFTER LAST ELBO\nSpecify first or last member of a given type (last Elbow in the list)\nNEW TEE AFTER NEXT 3\nSpecify position relative to Current List Position\nNEW TEE BEFORE LAST FLAN\nSpecify first or last member of a given type\nNEW TEE AFTER /ELBO3\nSpecify name or refno\nNEW TEE BEFORE 8\nSpecify list position number\nNEW TEE BEFORE FLAN 2\nSpecify member type and number (second Flange in the list)\nNEW TEE AFTER LAST ELBO\nSpecify first or last member of a given type (last Elbow in the list)\nNEW TEE AFTER NEXT 3\nSpecify position relative to Current List Position\nNEW TEE BEFORE LAST FLAN\nSpecify first or last member of a given type\nThe new Tee, which is unnamed, becomes list member 7, /ELBO3 becomes list member 8, /FLAN2 becomes list member 9, and so on.\nTo create a new top level element in a specific database there is a DB keyword available in the syntax of the \u2018NEW\u2019 command as follows:\nNEW element_type element_name DB database_name\nwhere element_name is again optional and where the database_name is expressed as a fully qualified database name,for example, team/database.\nThe following command will create a new SITE named /MYSITE in the MYTEAM/MYDB database.\nNEW element_type element_name\n(element_name is optional)\nNEW TEE AFTER /ELBO3\nSpecify name or refno\nNEW TEE BEFORE 8\nSpecify list position number\nNEW TEE BEFORE FLAN 2\nSpecify member type and number (second Flange in the list)\nNEW TEE AFTER LAST ELBO\nSpecify first or last member of a given type (last Elbow in the list)\nNEW TEE AFTER NEXT 3\nSpecify position relative to Current List Position\nNEW TEE BEFORE LAST FLAN\nSpecify first or last member of a given type\nNEW TEE /TEE2\nNEW    element_type element_name BEFore list_position\nNEW    element_type element_name AFTer list_position\nNEW SITE /MYSITE DB MYTEAM/MYDB\nNote:\nThe Q LIST query will tell you which element types you can create as members of the Current Element.\n\n\n\nDatabase Navigation and Query Syntax\nDatabase Navigation and Query Syntax\nDatabase Navigation and Query Syntax\nNote\n:\nNEW element_type element_name\nDatabase Navigation and Query Syntax\nNEW TEE AFTER /ELBO3\nNEW TEE BEFORE 8\nNEW TEE BEFORE FLAN 2\nNEW TEE AFTER LAST ELBO\nNEW TEE AFTER NEXT 3\nNEW TEE BEFORE LAST FLAN\nNEW\nelement_type element_name\nDB\ndatabase_name\nelement_name\ndatabase_name\nteam/database"}
{"Headers": "Delete GPSET", "Content": "You can delete either the entire Current Element or some or all of its offspring. When you delete the Current Element, you also delete all of its offspring (that is, its members, their members, etc.) from the hierarchy. The command must therefore be used with care. When an element has been deleted, its Owner becomes the new Current Element.\nAs a safeguard against accidental deletion of parts of a DB, the deletion function operates only on the Current Element. As further safeguards, the DELETE command word must be entered in full and the command syntax requires that you confirm the generic type of the Current Element. Furthermore, access to the required element and its subsequent deletion must be specified in two separate command lines.\nTo delete the Current Element and all its offspring, enter\nFor example, to delete a Nozzle, make the Nozzle the Current Element and then enter\nThe Equipment which owned the Nozzle becomes the Current Element.\nTo delete a complete Zone, including all Equipment, Piping, Structures etc. owned by it, make the Zone the Current Element and then enter\nThe Site which owned the deleted Zone becomes the Current Element.\nTo delete only specified members of the Current Element, use one of the following forms of the command syntax:\nDELETE element_type MEMbers\n(deletes all members)\nDELETE element_type MEMbers integer\n(deletes one member)\nDELETE element_type MEMbers integer TO integer\n(deletes a range of members)\n(deletes all members)\n(deletes one member)\n(deletes a range of members)\nConsider the following examples, where the Current Element is /BRAN1 with the Member List illustrated in Figure 10-2:\nDELETE BRAN MEMBERS\nDeletes all components from the Branch, leaving only the Branch Head and Tail\nDELETE BRAN MEMBER 6\nDeletes only /TEE1\nDELETE BRAN MEMBERS 5 TO 7\nDeletes /ELBO2, /TEE1 and /ELBO3\nDeletes all components from the Branch, leaving only the Branch Head and Tail\nDeletes only /TEE1\nDeletes /ELBO2, /TEE1 and /ELBO3\n\nDELETE element_type MEMbers\n(deletes all members)\nDELETE element_type MEMbers integer\n(deletes one member)\nDELETE element_type MEMbers integer TO integer\n(deletes a range of members)\nDELETE BRAN MEMBERS\nDeletes all components from the Branch, leaving only the Branch Head and Tail\nDELETE BRAN MEMBER 6\nDeletes only /TEE1\nDELETE BRAN MEMBERS 5 TO 7\nDeletes /ELBO2, /TEE1 and /ELBO3\nDELETE NOZZ\nDELETE ZONE\n\n\n\nDELETE\nDELETE element_type MEMbers\nDELETE element_type MEMbers integer\nDELETE element_type MEMbers integer TO integer\nDELETE BRAN MEMBERS\nDELETE BRAN MEMBER 6\nDELETE BRAN MEMBERS 5 TO 7"}
{"Headers": "Structure of the Database hierarchy", "Content": "You can reorganize the structure of the Database (DB) hierarchy, without elements being added to or removed from its contents, in either of two ways:\nIn both cases elements and their offspring are transferred to new positions in the hierarchy. In the first case the element's owner remains unchanged, while in the second case the element's owner changes.\nTo rearrange the Member List of the Current Element (CE), use one of the commands:\nwhere element_id specifies an element which is to be moved (which must be a member of the Current Element) and where list_position may be specified in any of the ways described in Database Navigation and Query Syntax.\nIf list_position is omitted, the intended position is assumed to be immediately after the Current List Position.\nFor example, starting with the previous Member List:\n\nThe command\nmoves /ELBO3 to position 5, immediately following the Current List Position, giving the new Member List\n\nStarting from either of the above configurations, the command\nmoves /ELBO3 to position 3, immediately before /ELBO1, thus\n\nTo insert an existing element into the Member List of the Current Element, when it is not already a member of that list, use one of the commands\nwhere element_id specifies an element which is to be moved (which may be anywhere within the DB hierarchy as long as it is at an appropriate level) and where list_position may be specified in any of the ways described in Database Navigation and Query Syntax.\nIf list_position is omitted, the intended position is assumed to be immediately after the Current List Position.\nFor example, starting with the simple hierarchy\n\nthe command\nmoves /PIPE2 (and all its offspring) to the position immediately following the Current List Position. Ownership of /PIPE2 passes from /ZONE2 to /ZONE1, resulting in the new hierarchy\n\nREOrder element_id\nREOrder element_id  BEFore list_position\nREOrder element_id  AFTer  list_position\nREORDER /ELBO3\nREORDER    /ELBO3   BEFORE   FIRST   ELBO\nINCLude element_id\nINCLude element_id  BEFore list_position\nINCLude element_id  AFTer  list_position\nINCLUDE /PIPE2\nBy rearranging the order of the Member List of a single element\nBy relocating an element to a different part of the hierarchy\nBy rearranging the order of the Member List of a single element\nBy rearranging the order of the Member List of a single element\nBy relocating an element to a different part of the hierarchy\nBy relocating an element to a different part of the hierarchy\n\n\n\nDatabase Navigation and Query Syntax\nDatabase Navigation and Query Syntax\nDatabase Navigation and Query Syntax\nLude element_id\nINCLude element_id  BEFore list_position\nINCLude element_id  AFTer  list_position\nDatabase Navigation and Query Syntax"}
{"Headers": "Creation of a new element as a copy", "Content": "It is often convenient to create a new element as a copy of an existing element which has the same, or similar, attribute settings or members to those required. You do this in two stages:\nWhen an element is 'cloned' in this way, all attributes are copied from the source element to the target element except NAME (which must be unique) and LOCK (which is always unlocked in the target element). Additionally, and this is what makes the facility so powerful, all offspring of the source element are copied as offspring of the target element.\nYou may specify automatic renaming of the Current Element and its offspring as part of the copying process. Without this the new elements will be unnamed, since AVEVA E3D Design does not permit two elements in the same Database (DB) hierarchy to have identical names. You may also choose to copy only the members (and their offspring) of the source element, leaving the attributes of the Current Element itself unchanged.\nTo copy a complete element and all of its offspring, after creating a new Current Element of an appropriate type, enter\nwhere element_id identifies the source element to be copied.\nFor example, to create a new item of Equipment which is an exact replica of a previously-defined Equipment, you might use the command sequence (at Zone level)\nThis creates /EQUIPB as the Current Element and then turns it into an exact copy of /EQUIPA. All attributes and members of /EQUIPB now have the same settings as those of /EQUIPA, including its position, orientation etc., and so you will probably now want to move one of the Equipments to a different location.\nTo copy all offspring of an element, so that they create duplicate offspring for the Current Element, enter\nThe position, orientation, etc., of the Current Element now remain unchanged, but it acquires new members which are derived from the specified source element and which are correctly positioned relative to the Current Element.\nTo copy selected offspring of an element, so that they create duplicate offspring for the Current Element, enter\nFor example, the command sequence\ncreates a new Branch named /SIDEARM whose components replicate that part of the existing Branch /MAINLINE between the specified list positions. The attributes of the Branch /SIDEARM itself are unaffected by the COPY command, so that its position, orientation, etc. (as defined by its Head and Tail settings) remain unchanged by the addition of its new members.\nTo copy attributes from an identified element into the current element, type\nThis causes all attributes (except for references to elements in DESI databases and OWNER) to be copied to the current element. Or:\nThis is similar to the ATTRIBUTES option, except that as well as DESI references not being copied, neither are any position, direction, orientation or angle attributes.\nIn both cases, the Specification Reference (SPREF) and Catalog Reference (CATREF) are also not copied between elements of different types.\nTo copy elements alongside their original positions, type\nThis option causes a list of elements, defined by the selection criterion select, to be copied alongside their original positions in the database. So if the list includes a SCTN and a PNOD (for example) then each of these items would be copied so that the new SCTN shares the same owner as the old SCTN and the new PNOD shares the same owner as the old PNOD. As this option copies elements, rather than just attributes, other COPY options, such as RENAME, are valid.\nTo copy all or part of an element and rename the copies, append the command\nto the corresponding COPY command line.\nFor example, the command\ncopies all attributes and offspring of /FRACT1/PIPE into the Current Element. Where /FRACT1 occurs as the name or part of the name, it is changed to /FRACT2 in the Current Element and its offspring. Thus the Current Element itself is now named /FRACT2/PIPE, and so on.\nDACCOH\nBOOL\n\nTrue if DAC allows element hierarchy to be copied to another DB\nDACCOP\nBOOL\n\nTrue if DAC allows element to be copied to another DB\nDACCRE\nBOOL\nNOUN\nTrue if DAC allows element to be created\nDACDEL\nBOOL\n\nTrue if DAC allows element to be deleted\nDACERR\nSTRING(120)\nATTR\nReturns the DAC error\nMODATT\nBOOL\nATTR\nTrue if attribute of element can be modified\nMODDEL\nBOOL\nATTR\nTrue if element can be deleted\n\nAttribute Name\nData Type\nQualifier\nDescription\nDACCOH\nBOOL\nTrue if DAC allows element hierarchy to be copied to another DB\nDACCOP\nBOOL\nTrue if DAC allows element to be copied to another DB\nDACCRE\nBOOL\nNOUN\nTrue if DAC allows element to be created\nDACDEL\nBOOL\nTrue if DAC allows element to be deleted\nDACERR\nSTRING(120)\nATTR\nReturns the DAC error\nMODATT\nBOOL\nATTR\nTrue if attribute of element can be modified\nMODDEL\nBOOL\nATTR\nTrue if element can be deleted\nCOPY element_id\nNEW EQUI /EQUIPB\nCOPY /EQUIPA\nCOPY MEMbers OF element_id\nCOPY MEMbers integer TO integer OF element_id\nNEW BRAN /SIDEARM\nCOPY MEMBERS 12 TO 20 OF /MAINLINE\nCOPY ATTributes OF element_id\nCOPY LIKE element_id\nCOPY ADJ/ACENT select\n... REName    old_name   new_name\nCOPY  /FRACT1/PIPE  RENAME  /FRACT1  /FRACT2\nNote:\nIf the Current Element already has members, it is not possible to make it a copy of another element in this way.\n\n\n\nCreate a New Element\nCreate a New Element\nNote\n:"}
{"Headers": "Save Work and Get Work", "Content": "SAVEWORK saves the current Model changes without leaving Model. It is good practice to use this command on a regular basis during a long session to make sure maximum data security.\nAs well as a comment, an optional number n can be used to specify a particular database for the command. The number is the number of the database in the order output by the STATUS command (refer to Project). If no number is given, the SAVEWORK applies to the whole Multiple Database (MDB). An example of Savework syntax is SAVEWORK \u2018comment\u2019 1.\nGETWORK refreshes the view of all READ databases to pick up any changes that other users may have made since you first opened them. The optional n works in the same way as for SAVEWORK. You would normally only use GETWORK if you know of specific changes you wish to pick up and use. Please note that GETWORK slows up subsequent database access, as the information has to be re-read from disk. Therefore, you should use this command sparingly.\n\n\n\nProject\nn\nProject\nn"}
{"Headers": "New session", "Content": "Each time you enter Model or save your design changes, a new session is created for each database changed. You can then query when specific items of design data were modified by reference to the corresponding session number(s). Sessions can be used by the System Administrator to backtrack changes to a given date or session if necessary.\n\n\n"}
{"Headers": "SAVEWORK", "Content": "You can add a comment for each session, which can help identify the work done in each session.\nLets you associate comment text with the current Model session. You can query this text later to help you identify a particular session in which modifications were made to elements and/or attribute settings. You can enter the session comment before you issue a SAVEWORK command, or as part of a SAVEWORK command for example SAVEWORK \u2018MY COMMENTS\u2019.\nSESSION COMMENT \u2019Addition of upper platform\u2019\nwhere integer is the session number.\nEach time you enter Model or save your design changes, a new session is created for each database changed. You can then query when specific items of design data were modified by reference to the corresponding session number(s). Sessions can be used by the System Administrator to backtrack changes to a given date or session if necessary.\nExample\nSESSION COMMENT \u2019Addition of upper platform\u2019\n>-- SESSION COMMENT -- text -->\n   \nQ SESSComment integer\nNote:\nSessions 1 and 2 are created in ADMIN (when the MODEL DB and its World element, respectively, are created), so the first true session will be Session 3.\nExample\nSESSION COMMENT \u2019Addition of upper platform\u2019\n\n\n\nbefore\nNote\n:\nSession 3\nSESSION COMMENT \u2019Addition of upper platform\u2019\ntext\ninteger\ninteger"}
{"Headers": "Multiwrite Databases Claims and Extracts", "Content": "If a Model or Draw Database (DB) has been created as a multiwrite database, several users can write to it simultaneously, although they cannot change the same element.\nMultiwrite databases can either be Standard multiwrite databases, or Extract databases. In both types, an element must be claimed before it can be modified. Claiming an element prevents other users claiming (and modifying) the element; the element must be released before another user can change it.\nClaiming can be either explicit, where you must use the CLAIM command before attempting to modify the element, or implicit, where the claim is made automatically when you try to modify the element. The claim mode is set when the DB is created. Refer to Administrator Command Reference Manual for further information.\n\n\n\nmultiwrite\nStandard\nExtract\nclaimed\nreleased\nexplicit\nimplicit\nAdministrator Command Reference Manual\nAdministrator Command Reference Manual\n."}
{"Headers": "CLAIM command", "Content": "In a Standard multiwrite database, you must claim an element before changing it. This is known as a user claim. If the claim mode is explicit (see below for details of how to check this), you must first claim each element that you want to modify using the CLAIM command. If the claim mode is implicit, the claim will be made automatically (although you can still give explicit CLAIM commands if you want to prevent other users claiming specific elements).\nOnly primary elements can be claimed, these are listed in the Data Model Reference Manual.\nYou can claim a specified element only, or a specified element plus all of the significant elements below it in the hierarchy. If the claimed element is not a significant element, the significant element above it in the hierarchy will be claimed.\nAn element must be unclaimed before another user can claim it and change it. User claims are always unclaimed when you change modules or leaves AVEVA E3D Design, and you can also unclaim elements at any time during an AVEVA E3D Design session using the UNCLAIM command.\nCLAIM /ZoneA /EQUIP100 /PIPE-100-A\n\nClaims named elements\nCLAIM /ZoneA HIERARCHY\n\nClaims named element and all of its owned hierarchy\nCLAIM /ELBOW-33\n\n\nClaims Branch which owns named component, since ELBO is not a significant element\nUNCLAIM /PIPE-100 /PIPE-200\n\nUnclaims named elements\nUNCLAIM ALL\nUnclaims all elements currently claimed\nExamples\nCLAIM /ZoneA /EQUIP100 /PIPE-100-A\nClaims named elements\nCLAIM /ZoneA HIERARCHY\nClaims named element and all of its owned hierarchy\nCLAIM /ELBOW-33\nClaims Branch which owns named component, since ELBO is not a significant element\nUNCLAIM /PIPE-100 /PIPE-200\nUnclaims named elements\nUNCLAIM ALL\nUnclaims all elements currently claimed\n                .---------------.\n               /                |\n>-- CLAIM ----*-- elementname --+-- HIERARCHY ---.\n                                |                |\n                                \u2018----------------+-->\n                 .---------------.\n                /                |\n>-- UNCLAIM ---*-- elementname --+-- HIERARCHY ---.\n               |                 |                |\n               \u2018-- ALL ----------+----------------+-->\n\n\n\n\nData Model Reference Manual\nuser claim\nprimary\nData Model Reference Manual\nunclaimed\nCLAIM /ZoneA /EQUIP100 /PIPE-100-A\nCLAIM /ZoneA HIERARCHY\nCLAIM /ELBOW-33\nUNCLAIM /PIPE-100 /PIPE-200\nUNCLAIM ALL"}
{"Headers": "GETWORK", "Content": "Elements cannot be claimed if recent changes have been made to them by other users. You must issue a GETWORK command first.\nElements cannot be unclaimed if there are updates outstanding. You must issue a SAVEWORK command first.\nYou can insert/remove primary elements in a members list without claiming the owner. For example, you can add a Branch to a Pipe without claiming the Pipe. Thus two users can add different Branches to the same Pipe: any discrepancies will be resolved when a SAVEWORK is attempted.\nBefore an element can be deleted, that element and all of its sub-hierarchy must be claimed.\nThe following potential problems may not be revealed until you try to save changes:\nElements cannot be claimed if recent changes have been made to them by other users. You must issue a GETWORK command first.\nElements cannot be claimed if recent changes have been made to them by other users. You must issue a GETWORK command first.\nElements cannot be unclaimed if there are updates outstanding. You must issue a SAVEWORK command first.\nElements cannot be unclaimed if there are updates outstanding. You must issue a SAVEWORK command first.\nYou can insert/remove primary elements in a members list without claiming the owner. For example, you can add a Branch to a Pipe without claiming the Pipe. Thus two users can add different Branches to the same Pipe: any discrepancies will be resolved when a SAVEWORK is attempted.\nYou can insert/remove primary elements in a members list without claiming the owner. For example, you can add a Branch to a Pipe without claiming the Pipe. Thus two users can add different Branches to the same Pipe: any discrepancies will be resolved when a SAVEWORK is attempted.\nBefore an element can be deleted, that element and all of its sub-hierarchy must be claimed.\nBefore an element can be deleted, that element and all of its sub-hierarchy must be claimed.\nThe following potential problems may not be revealed until you try to save changes:\nThe following potential problems may not be revealed until you try to save changes:\n\n\n"}
{"Headers": "Data Access Control", "Content": "Unlike standard multiwrite databases, extracts allow users to keep elements claimed when they exit from AVEVA E3D Design or change to another module. They can also be used, together with Data Access Control (DAC), to manage workflow. Refer to Administrator User Guide for more information.\nAn Extract is created from an existing Database. When an Extract is created, it will be empty, with pointers back to the owing or master database . Extracts can only be created from Multiwrite databases. An extract can be worked on by one User at the same time as another user is working on the master or another extract.\nWhen a user works on the extract, an extract claim is made as well as a user claim.\nIf the claim mode is explicit, the extract claim will be made automatically when you make a user claim using the CLAIM command. You can also claim to the extract only using the EXTRACT CLAIM command.\nIf an element is claimed to an extract, only users with write access to the extract will be able to make a user claim and start work on the element:\nWhen an extract user does a SAVEWORK, the changed data will be saved to the Extract. The unchanged data will still be read via pointers back to the master Database (DB). The changes made to the extract can be written back to the master, or dropped. Also, the extract can be refreshed with changes made to the master.\nEXTRACT CLAIM /STRU1 /STRU2 /STRU3\n\nClaims named elements to the extract\nEXTRACT CLAIM /STRU1 /STRU2 /ZONE-A HIERARCHY\n\nClaims the named elements, and all the elements in the hierarchy to the extract\nThe HIERARCHY keyword must be the last on the command line. It will attempt to claim to the extract all members of the elements listed in the command which are not already claimed to the extract.\nEXTRACT FLUSH DB PIPE/PIPE \u2018Description of flush\u2019\n\nWrites all changes to the database back to the owing extract. The Extract claim is maintained.\nEXTRACT FLUSH /STRU1 /STRU2 /STRU3 \u2018Flushing three  structures\u2019\n\nWrites the changes to the named elements back to the owing extract. The Extract claim is maintained.\nEXTRACT ISSUE DB PIPE/PIPE \u2018Issuing /pipe\u2019\n\nWrites all the changes to the database back to the owning extract and releases the extract claim\nEXTRACT ISSUE /ZONE-A HIERARCHY \u2018Issuing /zone\u2019\n\nWrites all the changes to the named element and all elements under it in the hierarchy back to the owning extract and releases the extract claim\nEXTRACT ISSUE /STRU1 /STRU2 /STRU3 \u2018Issuing three structures\u2019\n\nWrites the changes to the named elements back to the owning extract and releases the extract claim\nEXTRACT RELEASE DB PIPE/PIPE\n\nReleases the extract claim: this command can only be given to release changes that have already been flushed.\nEXTRACT RELEASE /STRU1 /STRU2 /STRU3\n\nReleases the extract claim: this command can only be given to release changes that have already been flushed.\nEXTRACT RELEASE /ZONE-A HIERARCHY\n\nReleases the extract claim to the named element and all: elements under it in the hierarchy.\nEXTRACT DROP DB PIPE/PIPE \u2018Dropping /Pipe\u2019\n\nDrops changes that have not been flushed or issued. Your claim must have been unclaimed before this command can be given.\nEXTRACT REFRESH DB MYTEAMPIPING\n\nThis will refresh the extract MYTEAMPIPING with changes made on the parent extract,\nThe elements required can be specified by selection criteria, using a Programmable Macro Language (PML) expression. For example:\nExamples\nEXTRACT CLAIM /STRU1 /STRU2 /STRU3\nClaims named elements to the extract\nEXTRACT CLAIM /STRU1 /STRU2 /ZONE-A HIERARCHY\nClaims the named elements, and all the elements in the hierarchy to the extract\nThe HIERARCHY keyword must be the last on the command line. It will attempt to claim to the extract all members of the elements listed in the command which are not already claimed to the extract.\nEXTRACT FLUSH DB PIPE/PIPE \u2018Description of flush\u2019\nWrites all changes to the database back to the owing extract. The Extract claim is maintained.\nEXTRACT FLUSH /STRU1 /STRU2 /STRU3 \u2018Flushing three  structures\u2019\nWrites the changes to the named elements back to the owing extract. The Extract claim is maintained.\nEXTRACT ISSUE DB PIPE/PIPE \u2018Issuing /pipe\u2019\nWrites all the changes to the database back to the owning extract and releases the extract claim\nEXTRACT ISSUE /ZONE-A HIERARCHY \u2018Issuing /zone\u2019\nWrites all the changes to the named element and all elements under it in the hierarchy back to the owning extract and releases the extract claim\nEXTRACT ISSUE /STRU1 /STRU2 /STRU3 \u2018Issuing three structures\u2019\nWrites the changes to the named elements back to the owning extract and releases the extract claim\nEXTRACT RELEASE DB PIPE/PIPE\nReleases the extract claim: this command can only be given to release changes that have already been flushed.\nEXTRACT RELEASE /STRU1 /STRU2 /STRU3\nReleases the extract claim: this command can only be given to release changes that have already been flushed.\nEXTRACT RELEASE /ZONE-A HIERARCHY\nReleases the extract claim to the named element and all: elements under it in the hierarchy.\nEXTRACT DROP DB PIPE/PIPE \u2018Dropping /Pipe\u2019\nDrops changes that have not been flushed or issued. Your claim must have been unclaimed before this command can be given.\nEXTRACT REFRESH DB MYTEAMPIPING\nThis will refresh the extract MYTEAMPIPING with changes made on the parent extract,\nEXTRACT CLAIM ALL STRU WHERE (:OWNER EQ 'USERA') HIERARCHY\n>- EXTRACT -+- FLUSH ---------------.\n            |                       |\n            |- FLUSHWithoutrefresh -|\n            |                       |\n            |- RELEASE -------------|\n            |                       |\n            |- ISSUE ---------------|\n            |                       |\n            |- DROP ----------------|    .-------<-------.\n            |                       |   /                |\n            \u2018- REFRESH -------------+--*-- elementname --+- HIERARCHY -.\n                                    |                                  |\n                                    |                                  |\n                                    |                                  |\n                                    \u2018-- DB dbname ---------------------+->\nIf the databases are set up with implicit claim, when you modify the element, the element will be claimed both to the extract and then to you. If the element is already claimed to the extract, then the claim will only be made to you.\nIf the databases are set up with explicit claim, then you will need to use the CLAIM command before modifying the element.\nOnce you have made a user claim, no other users will be able to work on the elements claimed, as in a normal multiwrite database.\nIf you unclaim an element, it will remain claimed to the extract until the extract claim is released or issued.\nIf the databases are set up with implicit claim, when you modify the element, the element will be claimed both to the extract and then to you. If the element is already claimed to the extract, then the claim will only be made to you.\nIf the databases are set up with implicit claim, when you modify the element, the element will be claimed both to the extract and then to you. If the element is already claimed to the extract, then the claim will only be made to you.\nIf the databases are set up with explicit claim, then you will need to use the CLAIM command before modifying the element.\nIf the databases are set up with explicit claim, then you will need to use the CLAIM command before modifying the element.\nOnce you have made a user claim, no other users will be able to work on the elements claimed, as in a normal multiwrite database.\nOnce you have made a user claim, no other users will be able to work on the elements claimed, as in a normal multiwrite database.\nIf you unclaim an element, it will remain claimed to the extract until the extract claim is released or issued.\nIf you unclaim an element, it will remain claimed to the extract until the extract claim is released or issued.\n\n\n\nAdministrator User Guide\nmaster\nreleased\nissued\nEXTRACT CLAIM /STRU1 /STRU2 /STRU3\nEXTRACT CLAIM /STRU1 /STRU2 /ZONE-A HIERARCHY\nHIERARCHY\nEXTRACT FLUSH DB PIPE/PIPE \u2018Description of flush\u2019\nEXTRACT FLUSH /STRU1 /STRU2 /STRU3 \u2018Flushing three  structures\u2019\nEXTRACT ISSUE DB PIPE/PIPE \u2018Issuing /pipe\u2019\nEXTRACT ISSUE /ZONE-A HIERARCHY \u2018Issuing /zone\u2019\nEXTRACT ISSUE /STRU1 /STRU2 /STRU3 \u2018Issuing three structures\u2019\nEXTRACT RELEASE DB PIPE/PIPE\nEXTRACT RELEASE /STRU1 /STRU2 /STRU3\nEXTRACT RELEASE /ZONE-A HIERARCHY\nEXTRACT DROP DB PIPE/PIPE \u2018Dropping /Pipe\u2019\nEXTRACT REFRESH DB MYTEAMPIPING"}
{"Headers": "NAmeData", "Content": "Attribute Name\nData Type\nQualifier\nDescription\nDACCLA\nBOOL\nTrue if DAC allows element to be claimed\nDACERR\nSTRING(120)\nATTR\nReturns the DAC error\nDACISS\nBOOL\nTrue if DAC allows element to be issued\nAttribute Name\nData Type\nQualifier\nDescription\nDACCLA\nBOOL\n\nTrue if DAC allows element to be claimed\nDACERR\nSTRING(120)\nATTR\nReturns the DAC error\nDACISS\nBOOL\n\nTrue if DAC allows element to be issued\nCLMID\nSTRING(120)\n\nUnique system ID of user claiming element\nCLMNUM\nINTEGER\n\nUser or extract number claiming element. Extract num\\-bers are negative\nCLMTIE\nELEMENT(4)\n\nReference to elements that are automatically claimed along with this element\nEXCLFR\nBOOL\n\nTrue if element claimed from this extract. Only True for Primary elements\nEXCLHI\nELEMENT(5000)\n\nPrimary elements in descendant hierarchy claimed to this extract (includes this element)\nEXCLTO\nBOOL\n\nTrue if element claimed to this extract. Only True for Pri\\-mary elements\nEXNCLH\nELEMENT(5000)\n\nPrimary elements in descendant hierarchy not claimed to this extract\nEXTRC\nSTRING(120)\n\nName of extract claiming element\nNPDESC\nELEMENT(5000)\n\nList of non primary offspring\nOKCLA\nBOOL\n\nTrue if element may be claimed\nOKCLH\nBOOL\n\nTrue if element and hierarchy may be claimed\nOKREL\nBOOL\n\nTrue if element may be released\nOKRLH\nBOOL\n\nTrue if element and hierarchy may be released\nPRIMTY\nBOOL\n\nTrue if element is primary\nPRMMEM\nBOOL\n\nTrue if there are any primary elements amongst descendants\nPRMOWN\nELEMENT\n\nPrimary owning element (will be itself if primary)\nUSCLHI\nELEMENT(5000)\n\nElements in descendant hierarchy claimed to this user\nUSERC\nSTRING(120)\n\nUser name of user claiming element\nUSNCLH\nELEMENT(5000)\n\nElements in descendant hierarchy not claimed to this user\nEXHCNC\nELEMENT(5000)\n\nAs EXTCNC, but repeat test for all descendants\nEXHCNN\nELEMENT(5000)\n\nAs EXTCNN, but repeat test for all descendants\nEXHCON\nELEMENT(5000)\n\nAs EXTCON, but repeat test for all descendants\nEXHRCN\nELEMENT(5000)\n\nAs EXRCN, but repeat test for all descendants\nEXHRCO\nELEMENT(5000)\n\nAs EXTRCO, but repeat test for all descendants\nEXMOC\nBOOL\n\nAs EXMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOC\nBOOL\n\nAs EXPMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOD\nBOOL\n\nTrue if primary and element or non-primary descendants have been modified in this extract\nEXTCNC\nELEMENT(5000)\n\nAs EXTCON but excluding non modified elements\nEXTCNN\nELEMENT(5000)\n\nAs EXTCON but excluding modified elements\nEXTCON\nELEMENT(5000)\n\nPrimary elements connected/disconnected from ele\\-ment or non primary descendants in extract\nEXTRCN\nELEMENT(5000)\n\nAs EXTCNN, but applied recursively to each connection\nEXTRCO\nELEMENT(5000)\n\nAs EXTCON, but applied recursively to each connection\nOKDROP\nBOOL\n\nTrue if element may be dropped\nOKDRPH\nELEMENT(5000)\n\nPrimary elements preventing hierarchy drop\nOKRLEH\nELEMENT(5000)\n\nPrimary elements preventing hierarchy release\nOKRLEX\nBOOL\n\nTrue if element may be extract released\n\n\nAttribute Name\nData Type\nQualifier\nDescription\nDACCLA\nBOOL\nTrue if DAC allows element to be claimed\nDACERR\nSTRING(120)\nATTR\nReturns the DAC error\nDACISS\nBOOL\nTrue if DAC allows element to be issued\nAttribute Name\nData Type\nQualifier\nDescription\nCLMID\nSTRING(120)\nUnique system ID of user claiming element\nCLMNUM\nINTEGER\nUser or extract number claiming element. Extract num\\-bers are negative\nCLMTIE\nELEMENT(4)\nReference to elements that are automatically claimed along with this element\nEXCLFR\nBOOL\nTrue if element claimed from this extract. Only True for Primary elements\nEXCLHI\nELEMENT(5000)\nPrimary elements in descendant hierarchy claimed to this extract (includes this element)\nEXCLTO\nBOOL\nTrue if element claimed to this extract. Only True for Pri\\-mary elements\nEXNCLH\nELEMENT(5000)\nPrimary elements in descendant hierarchy not claimed to this extract\nEXTRC\nSTRING(120)\nName of extract claiming element\nNPDESC\nELEMENT(5000)\nList of non primary offspring\nOKCLA\nBOOL\nTrue if element may be claimed\nOKCLH\nBOOL\nTrue if element and hierarchy may be claimed\nOKREL\nBOOL\nTrue if element may be released\nOKRLH\nBOOL\nTrue if element and hierarchy may be released\nPRIMTY\nBOOL\nTrue if element is primary\nPRMMEM\nBOOL\nTrue if there are any primary elements amongst descendants\nPRMOWN\nELEMENT\nPrimary owning element (will be itself if primary)\nUSCLHI\nELEMENT(5000)\nElements in descendant hierarchy claimed to this user\nUSERC\nSTRING(120)\nUser name of user claiming element\nUSNCLH\nELEMENT(5000)\nElements in descendant hierarchy not claimed to this user\nAttribute Name\nData Type\nQualifier\nDescription\nEXHCNC\nELEMENT(5000)\nAs EXTCNC, but repeat test for all descendants\nEXHCNN\nELEMENT(5000)\nAs EXTCNN, but repeat test for all descendants\nEXHCON\nELEMENT(5000)\nAs EXTCON, but repeat test for all descendants\nEXHRCN\nELEMENT(5000)\nAs EXRCN, but repeat test for all descendants\nEXHRCO\nELEMENT(5000)\nAs EXTRCO, but repeat test for all descendants\nEXMOC\nBOOL\nAs EXMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOC\nBOOL\nAs EXPMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOD\nBOOL\nTrue if primary and element or non-primary descendants have been modified in this extract\nEXTCNC\nELEMENT(5000)\nAs EXTCON but excluding non modified elements\nEXTCNN\nELEMENT(5000)\nAs EXTCON but excluding modified elements\nEXTCON\nELEMENT(5000)\nPrimary elements connected/disconnected from ele\\-ment or non primary descendants in extract\nEXTRCN\nELEMENT(5000)\nAs EXTCNN, but applied recursively to each connection\nEXTRCO\nELEMENT(5000)\nAs EXTCON, but applied recursively to each connection\nOKDROP\nBOOL\nTrue if element may be dropped\nOKDRPH\nELEMENT(5000)\nPrimary elements preventing hierarchy drop\nOKRLEH\nELEMENT(5000)\nPrimary elements preventing hierarchy release\nOKRLEX\nBOOL\nTrue if element may be extract released\n\n\n"}
{"Headers": "Undo and Redo", "Content": "It is possible to undo and redo many operations. The undo mechanism is managed by AVEVA E3D Design using a stack of transaction objects.\nEach transaction object records the change in the state across the transaction.\nThe new descriptions are then:\nMARKDB \u2018comment\u2019 - Complete the current transaction and starts a new transaction.\nUNDODB - Undo the last transaction. If there is a current transaction then this is completed. Multiple Undos are allowed.\nREDODB - Redo to next mark. Multiple Redos are allowed. A redo is only valid after an UNDO. Any database change after an UNDO invalidates a REDO.\n\n\n"}
{"Headers": "Undo and Redo", "Content": "Every time you select an undo operation an entry is taken off the undo stack. The state saved in this transaction is restored, and the transaction object is placed on the redo stack.\nWhen the undo stack is empty, then the Undo button and the Undo menu option will be greyed out indicating that there are no operations remaining that can be undone.\nIf the operation of undo involves moving into or out of model editing mode, then the switch into that mode will happen automatically, and the model editor button and menu option will reflect the change.\nThe selection set and handle appropriate to the editing operation that was being used will also be restored.\nThere are also a number of ways that you can perform an undo:\nThe undo stack is automatically cleared after a SAVEWORK or GETWORK.\nA similar process to the one described above occurs for redo.\nWhen a transaction is taken off the redo stack, it is put back onto the undo stack.\nIf you perform any operation that changes the database after doing an undo, then the redo stack will be cleared.\nRefer to for controlling the undo stack from user defined Programmable Macro Language (PML).\nMARKDB 'comment'\nSet a Database mark. Multiple marks may be set.\nUNDODB\nUndo database to last mark. Multiple undos are allowed.\nREDODB\nRedo to next mark. Multiple Redos are allowed. A redo is only valid after an UNDO. Any database change after an UNDO invalidates a REDO.\nMARKDB 'comment'\nSet a Database mark. Multiple marks may be set.\nUNDODB\nUndo database to last mark. Multiple undos are allowed.\nREDODB\nRedo to next mark. Multiple Redos are allowed. A redo is only valid after an UNDO. Any database change after an UNDO invalidates a REDO.\nThe list of marks can be obtained from PML function MARKDB.\nThe system will always create an initial mark the first time the database is changed.\nMARKDB 'comment'\nSet a Database mark. Multiple marks may be set.\nUNDODB\nUndo database to last mark. Multiple undos are allowed.\nREDODB\nRedo to next mark. Multiple Redos are allowed. A redo is only valid after an UNDO. Any database change after an UNDO invalidates a REDO.\nAREA 0\nMARKDB 'First Mark'\nAREA 100\nMARKDB 'Second Mark'\nAREA 200\nMARKDB 'Third Mark'\nAREA 300\n!MARKS = MARKDB\nQ VAR !MARKS\nUNDODB\nQ AREA - value will be 200\nUNDODB\nQ AREA - value will be 100\nUNDODB\nQ AREA - value will be 0\nREDODB\nQ AREA - value will be 100\nREDODB\nQ AREA - value will be 200\nAREA 99\nUNDODB\nQ AREA - value will be 200\nREDODB\nQ AREA - value will be 99\nBy clicking on the Undo button on the appropriate toolbar.\nBy selecting the Undo option on the Edit pulldown menu on the main toolbar.\nBy entering the command UNDODB n where n indicates how many steps are to be undone.\nBy clicking on the Undo button on the appropriate toolbar.\nBy clicking on the Undo button on the appropriate toolbar.\nBy selecting the Undo option on the Edit pulldown menu on the main toolbar.\nBy selecting the Undo option on the Edit pulldown menu on the main toolbar.\nBy entering the command UNDODB n where n indicates how many steps are to be undone.\nBy entering the command UNDODB n where n indicates how many steps are to be undone.\n\n\n\nUndo\nUndo\nUndo\nUndo\nEdit\nUNDODB n\nn\n\nExample"}
{"Headers": "Shared Collections (Groups) and Secondary Hierarchies", "Content": "A shared collection can hold in its members list a number of design elements from any combination of hierarchic levels, they may also span Multiple Databases (MDBs). You can use any appropriate design operation to act upon all of these individual elements simply by carrying out the operation on the shared collection.\nShared collections are particularly useful when there is a need to create a secondary hierarchy of elements. For example a set of elements for a project may span more that one site, if this is the case it is difficulty to identify where in the hierarchy these elements occur. With a shared collection you can easily query its members and see the hierarchy of elements contained within it.\nA shared collection is a Model database element in its own right, and is therefore stored automatically for use in later sessions when you save database changes.\nThe Elements which make up a shared collection within the Model database are shown below:\n\nGPWL (Group World) Is a top level administrative element. A GPWL may hold multiple GPSET (Group Set) elements.\nGPSET contains groups of items (GPITEM). A GPSET element has Name, DESC, and FUNCTION attributes.\nGPITEM These are elements within a database which are to be grouped under a Group Set (GPSET). Elements from different databases can all be grouped into the same Group Set. A GPITEM has the following attributes Name, DESC and SITEM.\nIt is possible to nest Group Sets within other Group Sets. To achieve this structure a GPSET can own another GPSET or a GPITEM can point back onto a GPSET. The following figure illustrates this:\n\n\n\n\nGPWL\nGPSET\nGPITEM"}
{"Headers": "Shared Collections (Groups) and Secondary Hierarchies", "Content": "The contents of a shared collection are defined by adding or removing references to or from the list part of the shared collection.\nIn order to use the commands described in this section, the current element must be the shared collection whose member list you wish to modify. Specified elements are then added to the list part of the current element starting from the current list position or are removed from the list part of the current element such that the current list position becomes the Head position.\nThe elements to be added to, or removed from, the shared collection\u2019s member list may be specified in any of the following ways:\nGADD /ZONE1 /VALVE2\n\nAdds /ZONE1 and /VALVE2 to the current shared collection, starting from the current list position\nGREMOVE /ZONE1 /BOX3\n\nRemoves /ZONE1 and /BOX3 from the current shared collection and moves the current list position pointer to the Head position\nGADD MEM OF /BRANCH1 /BRANCH2\n\nAdds all the pipe Components in Branches /BRANCH1 and /BRANCH2 to the current shared collection, starting from the current list position\nGREM MEM OF /PIPE100 MEM OF /EQUI-B\n\nRemoves all Branches of the Pipe /PIPE100 and all members of Equipment /EQUI-B from the current shared collection\nGREM ITEMS OF /ZONE2\n\nRemoves from the current shared collection all occurrences of those offspring of /ZONE2 which are items\nGADD ALL EQU BRAN OF /ZONE1 /ZONE2\n\nAdds all offspring of /ZONE1 and /ZONE2 which are of types Equip or Branch to the current shared collection, starting from the current list position\nExamples\nGADD /ZONE1 /VALVE2\nAdds /ZONE1 and /VALVE2 to the current shared collection, starting from the current list position\nGREMOVE /ZONE1 /BOX3\nRemoves /ZONE1 and /BOX3 from the current shared collection and moves the current list position pointer to the Head position\nGADD MEM OF /BRANCH1 /BRANCH2\nAdds all the pipe Components in Branches /BRANCH1 and /BRANCH2 to the current shared collection, starting from the current list position\nGREM MEM OF /PIPE100 MEM OF /EQUI-B\nRemoves all Branches of the Pipe /PIPE100 and all members of Equipment /EQUI-B from the current shared collection\nGREM ITEMS OF /ZONE2\nRemoves from the current shared collection all occurrences of those offspring of /ZONE2 which are items\nGADD ALL EQU BRAN OF /ZONE1 /ZONE2\nAdds all offspring of /ZONE1 and /ZONE2 which are of types Equip or Branch to the current shared collection, starting from the current list position\n>--+-- GADD -----.     .-------------.\n   |             |    /              |\n   \u2018-- GREMove --+---*-- <selatt> ---+--->\nExplicitly, by name or (system-assigned) reference number.\nAs members of specified elements, where a member of an element is defined as any element immediately below it in the DB hierarchy\nAs items of specified elements, where an item of an element is any element anywhere below it in the hierarchy which has no list part (such as a Valve, Point, Box, etc.)\nBy type (such as Equipment, Branch, Pipe, etc.)\nExplicitly, by name or (system-assigned) reference number.\nExplicitly, by name or (system-assigned) reference number.\nAs members of specified elements, where a member of an element is defined as any element immediately below it in the DB hierarchy\nAs members of specified elements, where a member of an element is defined as any element immediately below it in the DB hierarchy\nAs items of specified elements, where an item of an element is any element anywhere below it in the hierarchy which has no list part (such as a Valve, Point, Box, etc.)\nAs items of specified elements, where an item of an element is any element anywhere below it in the hierarchy which has no list part (such as a Valve, Point, Box, etc.)\nBy type (such as Equipment, Branch, Pipe, etc.)\nBy type (such as Equipment, Branch, Pipe, etc.)\n\n\n\n\nor\nmember\nimmediately\nitem\nno\nGADD /ZONE1 /VALVE2\nGREMOVE /ZONE1 /BOX3\nGADD MEM OF /BRANCH1 /BRANCH2\nGREM MEM OF /PIPE100 MEM OF /EQUI-B\nGREM ITEMS OF /ZONE2\nGADD ALL EQU BRAN OF /ZONE1 /ZONE2"}
{"Headers": "Delete GPSET", "Content": "The action of this command differs from normal behaviour if the current element is a shared collection.\nDELETE GPSET\n\nOnly the current element and any Offspring that are GPSETs will be deleted.\nDELETE GPWLD\n\nOnly the current element and any Offspring that are GPSETs will be deleted.\n\nExamples\nDELETE GPSET\nOnly the current element and any Offspring that are GPSETs will be deleted.\nDELETE GPWLD\nOnly the current element and any Offspring that are GPSETs will be deleted.\n\n\n\nDELETE GPSET\nDELETE GPWLD"}
{"Headers": "Copy a shared collection", "Content": "Shared collections can be copied with a slightly different effect to normal elements.\nCOPY /GROUP21 (At a Group)\n\nThe Current shared collection will contain exactly the same Members as /GROUP21. No new elements have been created.\n\nExamples\nCOPY /GROUP21 (At a Group)\nThe Current shared collection will contain exactly the same Members as /GROUP21. No new elements have been created.\n\n\n\nCOPY /GROUP21 (At a Group)"}
{"Headers": "Selection for GPSET", "Content": "You may specify a dynamic selection for a GPSET. The dynamic selection consists of a PML1 collection expression.\nFor example:\nThe selection must be set against the SCOSEL attribute.\nFor example:\nThe selection is evaluated dynamically whenever the shared collection is used. Depending on the selection used there is a performance overhead in evaluating the selection.\nALL PIPE WHERE (BORE GT 80)\nALL BRAN MEMBERS WHERE (SPREF EQ /MYSPEC ) for SITE /SITE1\n   \nSCOSEL ALL EQUI FROM CLAIMLIST\n\n\n\nRE (BORE GT 80)\nALL BRAN MEMBERS WHERE (SPREF EQ /MYSPEC \n."}
{"Headers": "Expressions", "Content": "This section explains the PML 1 expressions package. These facilities are needed within AVEVA products, for example, to define report templates in AVEVA E3D Design.\nExpressions have types. For example, you can have numeric expressions, text expressions and logical expressions. All the elements in an expression must be of the correct type. For example, if you have a two numbers, x and y, and two text strings text1 and text2, the following expression is meaningless:\nx + text1\n$\nx + text1\n$\nHowever, both of the following expressions are valid:\nx + y\n$ adds the values of the numeric variables.\nText1 + text2\n$ concatenates the two text strings.\nx + y\n$ adds the values of the numeric variables.\nText1 + text2\n$ concatenates the two text strings.\nReal expressions also have a physical dimension. This may be NONE when all values in the expression are purely numerical, but if any value has a physical dimension (such as being a length or mass) then all other values must be compatible with it and the result of the expression may have a physical dimension, or it may evaluate to a pure numerical value (1inch / 1mm = 25.4).\nThe following types of expressions are available:\nx + text1\n$\nx + y\n$ adds the values of the numeric variables.\nText1 + text2\n$ concatenates the two text strings.\nLogical Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nNumeric (Real) Functions\nText Expressions\nLogical Expressions\nLogical Expressions\nLogical Array Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nNumeric (Real) Expressions\nNumeric (Real) Functions\nNumeric (Real) Functions\nText Expressions\nText Expressions\nNote:\nGenerally, all these facilities are compatible with PML 2.\n\n\n\nLogical Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nNumeric (Real) Functions\nText Expressions\nNote\n:\nx + text1\nx + y\nText1 + text2\nLogical Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nNumeric (Real) Functions\nText Expressions"}
{"Headers": "Expressions", "Content": "The format of an expression, for example the use of brackets, spaces and quotes, is important. If you do not follow the rules given below you will get error messages:\nText must be enclosed in quotes.\nThere must be a space between each operator and operand. For example:\nUse round brackets to control the order of evaluation of expressions and to enclose the argument of a function.\nIn general, you do not need spaces before or after brackets, except when an AVEVA E3D Design name is followed by a bracket. If there is no space, the bracket will be read as part of the name.\n'This is text\u2019\nx + y\nSIN(30)\n(NAME EQ /VESS1 )\n\n\n"}
{"Headers": "Operators", "Content": "Operators are evaluated in the order of the following list: the ones at the top of the list are evaluated first.\nBRACKETS\nBrackets can be used to control the order in which operators are evaluated, in the same way as in normal arithmetic\nFUNCTIONS\n\n* /\n\n+ -\n\nEQ, NEQ, LT, LE, GE, GT\n\nNOT\n\nAND\n\nOR\n\n\nOperator\nComments\nBRACKETS\nBrackets can be used to control the order in which operators are evaluated, in the same way as in normal arithmetic\nFUNCTIONS\n* /\n+ -\nEQ, NEQ, LT, LE, GE, GT\nNOT\nAND\nOR\n\n\n"}
{"Headers": "Expressions", "Content": "Expressions can be nested using brackets.\n( (SIN(!angleA) * 2)  /  SIN(!angleB) )\n\n\n\n( (SIN(!angleA) * 2)  /  SIN(!angleB) )"}
{"Headers": "Logical expressions", "Content": "Logical expressions can contain:\nAVEVA E3D Design attributes of type logical e.g. BUILT.\nLogical constants. The constants available are: TRUE, ON, YES for true, and FALSE, OFF, NO for false.\nLogical operators.\nLogical functions.\nAVEVA E3D Design attributes of type logical e.g. BUILT.\nAVEVA E3D Design attributes of type logical e.g. BUILT.\nLogical constants. The constants available are: TRUE, ON, YES for true, and FALSE, OFF, NO for false.\nLogical constants. The constants available are: TRUE, ON, YES for true, and FALSE, OFF, NO for false.\nLogical operators.\nLogical operators.\nLogical functions.\nLogical functions.\n\n\n"}
{"Headers": "Logical expressions", "Content": "Logical expressions involving physical quantities.\nIf the expression contains unit qualified values, or attributes with a physical dimension then these values are converted to consistent units before comparison\nIf a value is not unit qualified it is assumed to be in current units of the quantity defined by the other value (i.e. the context of the expression). For example if current units of mass (colloquially weight) are oz then\nBut if current units of mass are kg then expression will return FALSE as 2lb is not equal to 2kg.\nIf the units are not units of the same physical quantity FALSE will always be returned as the two values are completely incompatible (as are apples and pears) and a warning issued (for example, (2lb equal 32mm).\nThe logical operators available are:\nAND\n\nEQ, NE\nThe operators EQ and NE may be applied to any pair of values of the same type.\nGT, GE, LE, LT\nThe operators GE, LE, GT and LT may only be used with numbers and positions. For more information, see Positions, Directions and Orientations in Expressions.\nNOT\n\nOR\n\nlog1 AND log2\n-> logical\nPerform the logical AND between two logical values. Treats unset values as FALSE.\nIf one of the values is undefined and the other one is FALSE, the result is FALSE.\nTRUE and FALSE -> FALSE\nCompare two values. A special feature is used for the positions, only the coordinates specified are compared. Refer to Compare Positions for more information. Unset values result in FALSE across EQ, TRUE across NE.\nIf two positions have no common coordinate, for example, \u2019N 10 ne U 10\u2019, the result is undefined. Units are consolidated across comparisons.\n( 1.0 eq 2.0) -> FALSE\nNone.\n( number1 GT number2 )\n> logical\n( pos1 GT pos2 )\n> logical\n( number1 GE number2 )\n> logical\n( pos1 GE pos2 )\n> logical\n( number1 LE number2 )\n> logical\n( pos1 LE pos2 )\n> logical\n( number1 LT number2 )\n> logical\n( pos1 LT pos2 )\n> logical\nCompare two values. A special feature is used for positions: only the coordinates specified are compared. See Compare Positions for more information. For positions, since comparisons may be performed on more than one value, LT (GT) is not the inverse of GE (LE). Unset values result in false\nIf two positions have no common coordinate, the result is undefined. For example, \u2019N 10 gt U 10\u2019.\nUnits are consolidated across comparisons.\n( 1.0 LT 2.0) -> TRUE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\n( N 0 E 10 GT N 10 E 0 ) -FALSE\nNone.\nNOT log1\n-> logical\nPerform the logical NOT on a logical value.\nNone.\nnot TRUE -> FALSE\nNone.\nOR log2\n-> logical\nPerform the logical inclusive OR between two logical values. (The exclusive OR is defined by using NE.)\nAllows numbers instead of logical values.\nIf one of the values is undefined and the other one is TRUE, the result is TRUE.\nTRUE or FALSE -> TRUE\nNone.\n\nOperator\nComments\nAND\nEQ, NE\nThe operators EQ and NE may be applied to any pair of values of the same type.\nGT, GE, LE, LT\nThe operators GE, LE, GT and LT may only be used with numbers and positions. For more information, see Positions, Directions and Orientations in Expressions.\nNOT\nOR\nSynopsis\nlog1 AND log2\n-> logical\nDescription\nPerform the logical AND between two logical values. Treats unset values as FALSE.\nSide Effects\nIf one of the values is undefined and the other one is FALSE, the result is FALSE.\nExample\nTRUE and FALSE -> FALSE\nSynopsis\n( number1 EQual number2)\n-> logical\n( text1 EQual text2 )\n-> logical\n( log1 EQual log2 )\n-> logical\n( id1 EQual id2 )\n-> logical\n( pos1 EQual pos2 )\n-> logical\n( dir1 EQual dir2 )\n-> logical\n( ori1 EQual ori2 )\n-> logical\n( pp1 EQual pp2 )\n-> logical\n( number1 NEqual number2 )\n-> logical\n( text1 NEqual text2 )\n-> logical\n( log1 NEqual log2 )\n-> logical\n( id1 NEqual id2 )\n-> logical\n( pos1 NEqual pos2 )\n-> logical\n( dir1 NEqual dir2 )\n-> logical\n( ori1 NEqual ori2 )\n-> logical\n( pp1 NEqual pp2 )\n-> logical\nDescription\nCompare two values. A special feature is used for the positions, only the coordinates specified are compared. Refer to Compare Positions for more information. Unset values result in FALSE across EQ, TRUE across NE.\nSide Effects\nIf two positions have no common coordinate, for example, \u2019N 10 ne U 10\u2019, the result is undefined. Units are consolidated across comparisons.\nExample\n( 1.0 eq 2.0) -> FALSE\nErrors\nNone.\nSynopsis\n( number1 GT number2 )\n> logical\n( pos1 GT pos2 )\n> logical\n( number1 GE number2 )\n> logical\n( pos1 GE pos2 )\n> logical\n( number1 LE number2 )\n> logical\n( pos1 LE pos2 )\n> logical\n( number1 LT number2 )\n> logical\n( pos1 LT pos2 )\n> logical\nDescription\nCompare two values. A special feature is used for positions: only the coordinates specified are compared. See Compare Positions for more information. For positions, since comparisons may be performed on more than one value, LT (GT) is not the inverse of GE (LE). Unset values result in false\nSide Effects\nIf two positions have no common coordinate, the result is undefined. For example, \u2019N 10 gt U 10\u2019.\nUnits are consolidated across comparisons.\nExample\n( 1.0 LT 2.0) -> TRUE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\n( N 0 E 10 GT N 10 E 0 ) -FALSE\nErrors\nNone.\nSynopsis\nNOT log1\n-> logical\nDescription\nPerform the logical NOT on a logical value.\nSide Effects\nNone.\nExample\nnot TRUE -> FALSE\nErrors\nNone.\nSynopsis\nOR log2\n-> logical\nDescription\nPerform the logical inclusive OR between two logical values. (The exclusive OR is defined by using NE.)\nAllows numbers instead of logical values.\nSide Effects\nIf one of the values is undefined and the other one is TRUE, the result is TRUE.\nExample\nTRUE or FALSE -> TRUE\nErrors\nNone.\n( number1 EQual number2)\n-> logical\n( text1 EQual text2 )\n-> logical\n( log1 EQual log2 )\n-> logical\n( id1 EQual id2 )\n-> logical\n( pos1 EQual pos2 )\n-> logical\n( dir1 EQual dir2 )\n-> logical\n( ori1 EQual ori2 )\n-> logical\n( pp1 EQual pp2 )\n-> logical\n( number1 NEqual number2 )\n-> logical\n( text1 NEqual text2 )\n-> logical\n( log1 NEqual log2 )\n-> logical\n( id1 NEqual id2 )\n-> logical\n( pos1 NEqual pos2 )\n-> logical\n( dir1 NEqual dir2 )\n-> logical\n( ori1 NEqual ori2 )\n-> logical\n( pp1 NEqual pp2 )\n-> logical\nNote:\nThe operators EQ, NE, LT, GT, LE and GE are sometimes referred to as comparator or relational operators; NOT, AND and OR are sometimes referred to as Boolean operators. Refer to Precision of Comparisons for tolerances in comparing numbers.\n\n\n\nPositions, Directions and Orientations in Expressions\nPrecision of Comparisons\nCompare Positions\nCompare Positions\nPositions, Directions and Orientations in Expressions\nNote\n:\ncomparator\nrelational\nBoolean\nPrecision of Comparisons\nSynopsis\nlog1 AND log2\n-> logical\nDescription\nSide Effects\nExample\nTRUE and FALSE -> FALSE\nEQ and NE\nSynopsis\nDescription\nCompare Positions\nSide Effects\n\u2019N 10 ne U 10\u2019\nExample\n( 1.0 eq 2.0) -> FALSE\nErrors\nSynopsis\n( number1 GT number2 )\n> logical\n( pos1 GT pos2 )\n> logical\n( number1 GE number2 )\n> logical\n( pos1 GE pos2 )\n> logical\n( number1 LE number2 )\n> logical\n( pos1 LE pos2 )\n> logical\n( number1 LT number2 )\n> logical\n( pos1 LT pos2 )\n> logical\nDescription\nCompare Positions\nSide Effects\n\u2019N 10 gt U 10\nExample\n( 1.0 LT 2.0) -> TRUE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\n( N 0 E 10 GT N 10 E 0 ) -FALSE\nErrors\nSynopsis\nNOT log1\n-> logical\nDescription\nSide Effects\nExample\nnot TRUE -> FALSE\nErrors\nSynopsis\nOR log2\n-> logical\nDescription\nSide Effects\nExample\nTRUE or FALSE -> TRUE\nErrors"}
{"Headers": "Logical functions", "Content": "The logical functions available are:\nBADREF\nDEFINED,UNDEFINED\nCREATED\nDELETED\nEMPTY\nIFTRUE\nMATCHWILD\nMODIFIED\nUNSET\nVLOGICAL\nBADREF\n\nDEFINED,UNDEFINED\n\nCREATED\n\nDELETED\n\nEMPTY\n\nIFTRUE\n\nMATCHWILD\n\nMODIFIED\n\nUNSET\n\nVLOGICAL\n\nBADREF (id)\n-> logical\nTRUE if id is invalid, else FALSE.\nNone\nBADREF(TREF) -> \u2019true\u2019 if TREF=nulref\nNone.\nDEFined (variable_name)\n-> logical\nDEFined (variable_name,number)\n-> logical\nUNDEFined (variable_name)\n-> logical\nUNDEFined (variable_name , number)\n-> logical\nWith one argument, DEFINED is true only if the scalar variable, the array variable or the array variable element exists.\nWith two arguments, DEFINED is true only if the first argument is an array variable which has a value for the index denoted by the second argument.\nUNDEFINED( !foo ) is equivalent to NOT DEFINED( !foo ).\nNone.\nDEFINED ( !var ) -> TRUE\nDEFINED ( !array ) -> TRUE\nDEFINED ( !array[1] )) -> TRUE\nDEFINED ( !array , 1 ) -> TRUE\nDEFINED ( !var) -> FALSE\nUNDEFINED ( !array) -> TRUE\nDEFINED ( !array , 3 ) -> FALSE\nNone.\nCREATED\n-> logical\nReturns TRUE if the element has been created since the set date.\nNone.\nCREATED -> TRUE\nNone.\nDELETED\n-> logical\nReturns TRUE if the element has been deleted since the set date.\nNone.\nDELETED -> TRUE\nNone.\nEMPTY(text)\n-> logical\nReturns TRUE if text is a zero length string, else FALSE\nNone.\nEMPTY(\u2018\u2019) -> TRUE\nEMPTY(\u2018not empty\u2019) -> FALSE\nNone.\nIFTrue(logical, anyA, anyB)\n-> logical\nThe first argument is a logical value or expression.\nThe second and third arguments may be of any type BUT THEY MUST BE OF THE SAME TYPE.\nReturns a value that is the SAME TYPE as the second and third arguments.\nReturns anyA if logical evaluates to TRUE, anyB if logical evaluates to FALSE.\nanyA and anyB can be IFTRUE functions themselves (as long as they return consistent types) so IF constructs can be nested.ds.\nNone.\nIFT (SPREF EQ /A3B/GC50, 'BLUE', 'RED'\niftrue (gwei gt 1tonne, /INSUL/THICK, /INSUL/THIN)\n-> BLUE\n->INSUL/THICK\nNormal number of argument errors and Mismatched second and third arguments:\n(2,497) TYPE MISMATCH: unmatched or illegal argument type for IFTRUE function.\nMATCHW/ILD( text1, text2)\n-> logical\nMATCHW/ILD( text1, text2, text3)\n-> logical\nMATCHW/ILD( text1, text2, text3, text4)\n-> logical\nMatches string text2 to string text1. If they are the same then returns TRUE, else FALSE. text2 may contain wildcard characters.\nThe defaults for wildcards are \u2018*\u2019 for any number of characters, and \u2018?\u2019 for a single character.\nWith three arguments, the multiple wildcard character \u2018*\u2019 may be redefined by text3.\nWith four arguments the single wildcard character \u2018?\u2019 may be redefined by text4.\nNone\nMATCHW/ILD(\u2019** text\u2019,\u2019**!\u2019,\u2019!\u2019) -> TRUE\nNone.\n\n                                   .-----------------------------------.\n                                 /                                    |\n>- MODIFIED-(-+- attname -------*- DESCENDANTS \u2011-+-+-comma +-attname \u2011\u2019\n              |                 |                | |\n              |- DESCENDANTS -. |- SIGNIFICANT --| |\n              |               | |                | |\n              |- SIGNIFICANT--| |- PRIMARY ----- | |\n              |               | |                | |\n              |- PRIMARY -----| |- OFFSPRING-----| |\n              |               | |                | |\n              |- OFFSPRING ---| \u2018----------------\u2019 |\n              |               |                    |\n              |               |                    |\n              |               |                    |\n              \u2018---------------+--------------------+--+-- ) - OF \u2011 id \u00c6\n                                                  |\n                                                   \u2018-\u00c6\n\nFor sophisticated queries relating to modifications. Returns TRUE if a modification has taken place.\nEach attribute name may be followed by the following qualifying keywords:\nOFFSPRING, to check this element and members\nSIGNIF, to check all elements for which this element represents the significant one;\nPRIMARY, check all elements for which this element represents the primary one;\nDESCENDANTS, this element and everything below (descendants).\nThe \u2018OF\u2019 syntax may be used as for attributes.\nThe MODIFIED function or the GEOM, CATTEXT and CATMOD pseudo-attributes.\nThe MODIFIED, DELETED and CREATED functions may go anywhere within an AVEVA E3D\u2122 PML1 expression. i.e. after Q/VAR and within collections\nNone\nQ (MODIFIED())\nReturns TRUE if element has changed at all since the comparison date.\nIt will also return TRUE if the element has been created since the comparison date.\nQ MODIFIED(POS,ORI)\nReturns TRUE if POS or ORI modified since the comparison date.\nQ MODIFIED(P1 POS)\nReturns TRUE if the position of P1 has changed.\nQ MODIFIED(GEOM DESCENDANTS\nReturns TRUE if any geometry for item or any descendants has changed\nQ MODIFIED(PRIMARY)\nReturns TRUE if any element for which this element is primary, has changed.\nQ MODIFIED() OF /PIPE1\nReturns TRUE if /PIPE1 has been modified since the comparison date.\nQ (BUIL OR MODIFIED()OR ELECREC OF NEXT )\n\nNone.\nThe MODIFIED, DELETED and CREATED functions are not implemented within PML2 expressions.\nUNSET(value)\n-> logical\nReturns TRUE if value is unset, else FALSE. The value can be of any data type including ARRAYS. Normally it will be an AVEVA E3D\u2122 attribute.\nNone.\nUNSET( DESC )\nTRUE where DESC is an unset text attribute\nUNSET(CRFA)\nFALSE where CRFA contains unset reference attributes\nNone.\nVLOGICAL is used for the late evaluation of variables.\nVLOGICAL ( variable_name ))\n-> logical\nVLOGICAL ( variable_name , number)\n-> logical\nWith one argument, return the value of the scalar variable or the value of the array variable element as a logical.\nWith two arguments, return the value of the element corresponding to the index number as a logical.\nThe rules of conversion are:\nTRUE for the strings \u2019T\u2019, \u2019TR\u2019, \u2019TRU\u2019 or \u2019TRUE\u2019 (case insensitive) or any numeric value not equal to zero;\nFALSE for the strings \u2019F\u2019, \u2019FA\u2019, \u2019FAL\u2019, \u2019FALS\u2019 or \u2019FALSE\u2019 (case insensitive) or a numeric value equal to zero.\nScalar variables may not be indexed. For example, VTEXT(!var[1]) will return an error.\nArray variables must have an index. For example, VTEXT (!array) will return an error.\nThe value cannot be translated into a logical.\nSee also VTEXT, used for late evaluation when a text result is required; and VVALUE, used for late evaluation when a numeric result is required.\nIf the scalar variable, the array variable, or the array variable element does not exist, the result is undefined.\nVLOG ( !array[1] ) -> TRUE\nVLOG ( !array , 2 ) -> FALSE\nNone.\n\nBADREF\nDEFINED,UNDEFINED\nCREATED\nDELETED\nEMPTY\nIFTRUE\nMATCHWILD\nMODIFIED\nUNSET\nVLOGICAL\nSynopsis\nBADREF (id)\n-> logical\nDescription\nTRUE if id is invalid, else FALSE.\nSide Effects\nNone\nExample\nBADREF(TREF) -> \u2019true\u2019 if TREF=nulref\nErrors\nNone.\nSynopsis\nDEFined (variable_name)\n-> logical\nDEFined (variable_name,number)\n-> logical\nUNDEFined (variable_name)\n-> logical\nUNDEFined (variable_name , number)\n-> logical\nDescription\nWith one argument, DEFINED is true only if the scalar variable, the array variable or the array variable element exists.\nWith two arguments, DEFINED is true only if the first argument is an array variable which has a value for the index denoted by the second argument.\nUNDEFINED( !foo ) is equivalent to NOT DEFINED( !foo ).\nSide Effects\nNone.\nExample\nDEFINED ( !var ) -> TRUE\nDEFINED ( !array ) -> TRUE\nDEFINED ( !array[1] )) -> TRUE\nDEFINED ( !array , 1 ) -> TRUE\nDEFINED ( !var) -> FALSE\nUNDEFINED ( !array) -> TRUE\nDEFINED ( !array , 3 ) -> FALSE\nErrors\nNone.\nSynopsis\nCREATED\n-> logical\nDescription\nReturns TRUE if the element has been created since the set date.\nSide Effects\nNone.\nExample\nCREATED -> TRUE\nErrors\nNone.\nSynopsis\nDELETED\n-> logical\nDescription\nReturns TRUE if the element has been deleted since the set date.\nSide Effects\nNone.\nExample\nDELETED -> TRUE\nErrors\nNone.\nSynopsis\nEMPTY(text)\n-> logical\nDescription\nReturns TRUE if text is a zero length string, else FALSE\nSide Effects\nNone.\nExample\nEMPTY(\u2018\u2019) -> TRUE\nEMPTY(\u2018not empty\u2019) -> FALSE\nErrors\nNone.\nSynopsis\nIFTrue(logical, anyA, anyB)\n-> logical\nThe first argument is a logical value or expression.\nThe second and third arguments may be of any type BUT THEY MUST BE OF THE SAME TYPE.\nReturns a value that is the SAME TYPE as the second and third arguments.\nDescription\nReturns anyA if logical evaluates to TRUE, anyB if logical evaluates to FALSE.\nanyA and anyB can be IFTRUE functions themselves (as long as they return consistent types) so IF constructs can be nested.ds.\nSide Effects\nNone.\nExample\nIFT (SPREF EQ /A3B/GC50, 'BLUE', 'RED'\niftrue (gwei gt 1tonne, /INSUL/THICK, /INSUL/THIN)\n-> BLUE\n->INSUL/THICK\nErrors\nNormal number of argument errors and Mismatched second and third arguments:\n(2,497) TYPE MISMATCH: unmatched or illegal argument type for IFTRUE function.\nSynopsis\nMATCHW/ILD( text1, text2)\n-> logical\nMATCHW/ILD( text1, text2, text3)\n-> logical\nMATCHW/ILD( text1, text2, text3, text4)\n-> logical\nDescription\nMatches string text2 to string text1. If they are the same then returns TRUE, else FALSE. text2 may contain wildcard characters.\nThe defaults for wildcards are \u2018*\u2019 for any number of characters, and \u2018?\u2019 for a single character.\nWith three arguments, the multiple wildcard character \u2018*\u2019 may be redefined by text3.\nWith four arguments the single wildcard character \u2018?\u2019 may be redefined by text4.\nSide Effects\nNone\nExample\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019??big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019???*big*\u2019) -> FALSE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*beer\u2019) -> TRUE\nMATCHW/ILD(\u2019** text\u2019,\u2019**!\u2019,\u2019!\u2019) -> TRUE\nErrors\nNone.\nSynopsis\n                                   .-----------------------------------.\n                                 /                                    |\n>- MODIFIED-(-+- attname -------*- DESCENDANTS \u2011-+-+-comma +-attname \u2011\u2019\n              |                 |                | |\n              |- DESCENDANTS -. |- SIGNIFICANT --| |\n              |               | |                | |\n              |- SIGNIFICANT--| |- PRIMARY ----- | |\n              |               | |                | |\n              |- PRIMARY -----| |- OFFSPRING-----| |\n              |               | |                | |\n              |- OFFSPRING ---| \u2018----------------\u2019 |\n              |               |                    |\n              |               |                    |\n              |               |                    |\n              \u2018---------------+--------------------+--+-- ) - OF \u2011 id \u00c6\n                                                  |\n                                                   \u2018-\u00c6\nDescription\nFor sophisticated queries relating to modifications. Returns TRUE if a modification has taken place.\nEach attribute name may be followed by the following qualifying keywords:\nOFFSPRING, to check this element and members\nSIGNIF, to check all elements for which this element represents the significant one;\nPRIMARY, check all elements for which this element represents the primary one;\nDESCENDANTS, this element and everything below (descendants).\nThe \u2018OF\u2019 syntax may be used as for attributes.\nThe MODIFIED function or the GEOM, CATTEXT and CATMOD pseudo-attributes.\nThe MODIFIED, DELETED and CREATED functions may go anywhere within an AVEVA E3D\u2122 PML1 expression. i.e. after Q/VAR and within collections\nSide Effects\nNone\nExample\nQ (MODIFIED())\nReturns TRUE if element has changed at all since the comparison date.\nIt will also return TRUE if the element has been created since the comparison date.\nQ MODIFIED(POS,ORI)\nReturns TRUE if POS or ORI modified since the comparison date.\nQ MODIFIED(P1 POS)\nReturns TRUE if the position of P1 has changed.\nQ MODIFIED(GEOM DESCENDANTS\nReturns TRUE if any geometry for item or any descendants has changed\nQ MODIFIED(PRIMARY)\nReturns TRUE if any element for which this element is primary, has changed.\nQ MODIFIED() OF /PIPE1\nReturns TRUE if /PIPE1 has been modified since the comparison date.\nQ (BUIL OR MODIFIED()OR ELECREC OF NEXT )\nErrors\nNone.\nSynopsis\nUNSET(value)\n-> logical\nDescription\nReturns TRUE if value is unset, else FALSE. The value can be of any data type including ARRAYS. Normally it will be an AVEVA E3D\u2122 attribute.\nSide Effects\nNone.\nExample\nUNSET( DESC )\nTRUE where DESC is an unset text attribute\nUNSET(CRFA)\nFALSE where CRFA contains unset reference attributes\nErrors\nNone.\nSynopsis\nVLOGICAL ( variable_name ))\n-> logical\nVLOGICAL ( variable_name , number)\n-> logical\nDescription\nWith one argument, return the value of the scalar variable or the value of the array variable element as a logical.\nWith two arguments, return the value of the element corresponding to the index number as a logical.\nThe rules of conversion are:\nTRUE for the strings \u2019T\u2019, \u2019TR\u2019, \u2019TRU\u2019 or \u2019TRUE\u2019 (case insensitive) or any numeric value not equal to zero;\nFALSE for the strings \u2019F\u2019, \u2019FA\u2019, \u2019FAL\u2019, \u2019FALS\u2019 or \u2019FALSE\u2019 (case insensitive) or a numeric value equal to zero.\nScalar variables may not be indexed. For example, VTEXT(!var[1]) will return an error.\nArray variables must have an index. For example, VTEXT (!array) will return an error.\nThe value cannot be translated into a logical.\nSee also VTEXT, used for late evaluation when a text result is required; and VVALUE, used for late evaluation when a numeric result is required.\nSide Effects\nIf the scalar variable, the array variable, or the array variable element does not exist, the result is undefined.\nExample\nVLOG ( !array[1] ) -> TRUE\nVLOG ( !array , 2 ) -> FALSE\nErrors\nNone.\n\n\n\nSynopsis\nBADREF (id)\n-> logical\nDescription\nid\nSide Effects\nExample\nBADREF(TREF) -> \u2019true\u2019 if TREF=nulref\nErrors\nSynopsis\nDEFined (variable_name)\n-> logical\nDEFined (variable_name,number)\n-> logical\nUNDEFined (variable_name)\n-> logical\nUNDEFined (variable_name , number)\n-> logical\nDescription\nSide Effects\nExample\nDEFINED ( !var ) -> TRUE\nDEFINED ( !array ) -> TRUE\nDEFINED ( !array[1] )) -> TRUE\nDEFINED ( !array , 1 ) -> TRUE\nDEFINED ( !var) -> FALSE\nUNDEFINED ( !array) -> TRUE\nDEFINED ( !array , 3 ) -> FALSE\nErrors\nSynopsis\nCREATED\n-> logical\nDescription\nSide Effects\nExample\nCREATED -> TRUE\nErrors\nSynopsis\nDELETED\n-> logical\nDescription\nSide Effects\nExample\nDELETED -> TRUE\nErrors\nSynopsis\nEMPTY(text)\n-> logical\nDescription\nSide Effects\nExample\nEMPTY(\u2018\u2019) -> TRUE\nEMPTY(\u2018not empty\u2019) -> FALSE\nErrors\nSynopsis\nIFTrue(logical, anyA, anyB)\n-> logical\nDescription\nSide Effects\nExample\nIFT (SPREF EQ /A3B/GC50, 'BLUE', 'RED'\niftrue (gwei gt 1tonne, /INSUL/THICK, /INSUL/THIN)\n-> BLUE\n->INSUL/THICK\nErrors\nSynopsis\nMATCHW/ILD( text1, text2)\n-> logical\nMATCHW/ILD( text1, text2, text3)\n-> logical\nMATCHW/ILD( text1, text2, text3, text4)\n-> logical\nDescription\ntext2\ntext1\ntext2\ntext3\ntext4\nSide Effects\nExample\nMATCHW/ILD(\u2019** text\u2019,\u2019**!\u2019,\u2019!\u2019) -> TRUE\nErrors\nSynopsis\n                                 .-----------------------------------.\n                                 /                                    |\n>- MODIFIED-(-+- attname -------*- DESCENDANTS \u2011-+-+-comma +-attname \u2011\u2019\n              |                 |                | |\n              |- DESCENDANTS -. |- SIGNIFICANT --| |\n              |               | |                | |\n              |- SIGNIFICANT--| |- PRIMARY ----- | |\n              |               | |                | |\n              |- PRIMARY -----| |- OFFSPRING-----| |\n              |               | |                | |\n              |- OFFSPRING ---| \u2018----------------\u2019 |\n              |               |                    |\n              |               |                    |\n              |               |                    |\n              \u2018---------------+--------------------+--+-- ) - OF \u2011 id \u00c6\n                                                  |\n                                                   \u2018-\u00c6\nDescription\nSide Effects\nExample\nQ (MODIFIED())\nQ MODIFIED(POS,ORI)\nQ MODIFIED(P1 POS)\nQ MODIFIED(GEOM DESCENDANTS\nQ MODIFIED(PRIMARY)\nQ MODIFIED() OF /PIPE1\nQ (BUIL OR MODIFIED()OR ELECREC OF NEXT )\nErrors\nSynopsis\nUNSET(value)\n-> logical\nDescription\nvalue\nSide Effects\nNone.\nExample\nUNSET( DESC )\nTRUE where DESC is an unset text attribute\nUNSET(CRFA)\nFALSE where CRFA contains unset reference attributes\nErrors\nSynopsis\nVLOGICAL ( variable_name ))\n-> logical\nVLOGICAL ( variable_name , number)\n-> logical\nDescription\nVTEXT(!var[1])\nVTEXT (!array)\nSide Effects\nExample\nVLOG ( !array[1] ) -> TRUE\nVLOG ( !array , 2 ) -> FALSE\nErrors"}
{"Headers": "Logical array", "Content": "Logical array expressions can contain:\nAVEVA E3D Design attributes of type logical array. For example, LOGARR where LOGARR is a User Dfined Attribute (UDA) of type logical.\nLogical constants. The constants available are: TRUE, ON, YES for true; and FALSE, OFF, NO for false.\nLogical operators. Refer to Logical Operators.\nLogical functions. Refer to Logical Functions.\nAVEVA E3D Design attributes of type logical array. For example, LOGARR where LOGARR is a User Dfined Attribute (UDA) of type logical.\nAVEVA E3D Design attributes of type logical array. For example, LOGARR where LOGARR is a User Dfined Attribute (UDA) of type logical.\nLogical constants. The constants available are: TRUE, ON, YES for true; and FALSE, OFF, NO for false.\nLogical constants. The constants available are: TRUE, ON, YES for true; and FALSE, OFF, NO for false.\nLogical operators. Refer to Logical Operators.\nLogical operators. Refer to Logical Operators.\nLogical functions. Refer to Logical Functions.\nLogical functions. Refer to Logical Functions.\n\n\n\nLogical Operators\nLogical Functions\nLogical Operators\n.\nLogical Functions\n."}
{"Headers": "Design expressions", "Content": "In AVEVA E3D Design expressions, integers are treated as reals; they are fully interchangeable. Numeric expressions can contain:\nNumbers, for example: 32, 10.1.\nNumbers can be given as integer exponents, for example: 10 exp 5, and 5 E 6.\nValues (numbers) can be qualified by units. This introduces dimensional analysis into the expression. The valid units are any standard appropriate unit qualifiers for example MM, M/etres, IN/ches, FT, FEET, kg, lb, kgf/m3, pascal. These may be preceded by SQU/are, CUBIC, CUB/e to denote non-linear Values, or alternatively they can have power indices appended. For example: 100 mm, 10 exp 5 cubic feet, 10m3, 20newton.m-2. Feet and inches can be shown as, for example, 10'6.\nAVEVA E3D Design attributes of type number, for example: XLEN.\nPosition, direction and orientation attributes which have a subscript to indicate which part of the array is required. For example, POS[2] means the second element of the POSITION attribute; that is, the northing.\nNote:\nPosition, direction and orientation attributes without subscripts can only be used in number array expressions.\nThe keyword PI (3.142).\nNumeric operators.\nNumeric functions.\nNumbers, for example: 32, 10.1.\nNumbers, for example: 32, 10.1.\nNumbers can be given as integer exponents, for example: 10 exp 5, and 5 E 6.\nNumbers can be given as integer exponents, for example: 10 exp 5, and 5 E 6.\nValues (numbers) can be qualified by units. This introduces dimensional analysis into the expression. The valid units are any standard appropriate unit qualifiers for example MM, M/etres, IN/ches, FT, FEET, kg, lb, kgf/m3, pascal. These may be preceded by SQU/are, CUBIC, CUB/e to denote non-linear Values, or alternatively they can have power indices appended. For example: 100 mm, 10 exp 5 cubic feet, 10m3, 20newton.m-2. Feet and inches can be shown as, for example, 10'6.\nValues (numbers) can be qualified by units. This introduces dimensional analysis into the expression. The valid units are any standard appropriate unit qualifiers for example MM, M/etres, IN/ches, FT, FEET, kg, lb, kgf/m3, pascal. These may be preceded by SQU/are, CUBIC, CUB/e to denote non-linear Values, or alternatively they can have power indices appended. For example: 100 mm, 10 exp 5 cubic feet, 10m3, 20newton.m-2. Feet and inches can be shown as, for example, 10'6.\nAVEVA E3D Design attributes of type number, for example: XLEN.\nAVEVA E3D Design attributes of type number, for example: XLEN.\nPosition, direction and orientation attributes which have a subscript to indicate which part of the array is required. For example, POS[2] means the second element of the POSITION attribute; that is, the northing.\nNote:\nPosition, direction and orientation attributes without subscripts can only be used in number array expressions.\nPosition, direction and orientation attributes which have a subscript to indicate which part of the array is required. For example, POS[2] means the second element of the POSITION attribute; that is, the northing.\nThe keyword PI (3.142).\nThe keyword PI (3.142).\nNumeric operators.\nNumeric operators.\nNumeric functions.\nNumeric functions.\n\n\n\nPOS[2]\nNote"}
{"Headers": "Numeric operators", "Content": "The numeric operators available are:\n+\nAddition.\n-\nSubtraction.\n*\nMultiplication.\n/\nDivision.\n\nOperator\nComments\n+\nAddition.\n-\nSubtraction.\n*\nMultiplication.\n/\nDivision.\n\n\n"}
{"Headers": "Addition", "Content": "The add and subtract functions available are\nnumber + number\n-> number\nnumber \u2011 number\n-> number\n+ number\n-> number\n- number\n-> number\nAdd or subtract two numbers. They can also be used as unary operators at the beginning of a parenthesized sub-expression.\nUnits are consolidated across add and subtract and the result is returned in current units of the physical quantity, for example when current distance units are inches\nIf only one value has a unit qualifier the other is assumed to be in current units of that physical quantity for example:\nIf the two values have conflicting units a warning is issued and a value is returned with no units assuming both values are in the database units of their respective quantities which is mm and Kg in the example:\nq (1ft + 1kg ) will return 305.8\n1 + 2 -> 3.0\n1 \u2011 2 -> 1.0\n+ 1 -> 1.0\n- 1 -> -1.0\nFloating point underflow.\n\nSynopsis\nnumber + number\n-> number\nnumber \u2011 number\n-> number\n+ number\n-> number\n- number\n-> number\nDescription\nAdd or subtract two numbers. They can also be used as unary operators at the beginning of a parenthesized sub-expression.\nSide Effects\nUnits are consolidated across add and subtract and the result is returned in current units of the physical quantity, for example when current distance units are inches\nq (1ft + 100mm) will return 15.9in\nIf only one value has a unit qualifier the other is assumed to be in current units of that physical quantity for example:\nq (1ft + 100 ) will return 112in\nIf the two values have conflicting units a warning is issued and a value is returned with no units assuming both values are in the database units of their respective quantities which is mm and Kg in the example:\nq (1ft + 1kg ) will return 305.8\nExample\n1 + 2 -> 3.0\n1 \u2011 2 -> 1.0\n+ 1 -> 1.0\n- 1 -> -1.0\nErrors\nFloating point underflow.\n\n\n\nSynopsis\nnumber + number\n-> number\nnumber \u2011 number\n-> number\n+ number\n-> number\n- number\n-> number\nDescription\nSide Effects\nExample\n1 + 2 -> 3.0\n1 \u2011 2 -> 1.0\n+ 1 -> 1.0\n- 1 -> -1.0\nErrors"}
{"Headers": "Miltiply and divide", "Content": "The multiply and divide functions available are\nnumber * number\n-> number\nnumber / number\n-> number\nMultiply or divide two numbers. They can also be used as unary operators at the beginning of a parenthesized sub-expression. Numeric underflow is not considered to be an error and neither is it flagged as a warning. The result returned is zero.\nUnits are consolidated across Multiply and Divide. The result is returned in the current units of the physical quantity of the result for example when current units of pressure are psi then:\nIf one value has no unit it is assumed to be a scaling factor. This also applies to reciprocal physical quantities. For example:\nfor (10 / XLEN) will return 2mm-1 when XLEN is 5mm\n2 * 3 -> 6.0\n2 / 3 -> 0.666666666\nDivide by zero.\n\nSynopsis\nnumber * number\n-> number\nnumber / number\n-> number\nDescription\nMultiply or divide two numbers. They can also be used as unary operators at the beginning of a parenthesized sub-expression. Numeric underflow is not considered to be an error and neither is it flagged as a warning. The result returned is zero.\nSide Effects\nUnits are consolidated across Multiply and Divide. The result is returned in the current units of the physical quantity of the result for example when current units of pressure are psi then:\nq (20kgf/ 1 cm2 ) will return 284.47PSI\nIf one value has no unit it is assumed to be a scaling factor. This also applies to reciprocal physical quantities. For example:\nfor (10 / XLEN) will return 2mm-1 when XLEN is 5mm\nExample\n2 * 3 -> 6.0\n2 / 3 -> 0.666666666\nErrors\nDivide by zero.\n\n\n\nSynopsis\nnumber * number\n-> number\nnumber / number\n-> number\nDescription\nSide Effects\n(10 / XLEN)\nExample\n2 * 3 -> 6.0\n2 / 3 -> 0.666666666\nErrors"}
{"Headers": "Numeric function", "Content": "All referenced units are current units. The numeric functions available are:\nABS ( number1 )\nGives the absolute value of a number\nACOS ( number1 )\nGives the arc cosine of a number, in degrees.\nASIN ( number1 )\nGives the arc sine of a number, in degrees.\nATAN ( number1 )\nGives the arc tangent of a number, in degrees.\nATANT ( number1, number2 )\n\nGives the arc tangent of number1/number2, in degrees, with the appropriate sign.\nALOG ( number1 )\nGives the exponential function (natural anti-log) of a number.\nARRAY(pos or dir or ori)\n\nConverts a position, direction or orientation value or attribute into three numbers.\nARRAYSIZE ( variable-name )\n\nGives the size of an array variable.\nARRAYWIDTH( variable-name )\n\nGives the largest display width of any string in array variable-name.\nCOMPONENT dir OF pos2\nGives the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nINT ( number1 )\nGives the truncated integer value of a number.\nSIN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nCOS ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nTAN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nLENGTH ( text1 )\nGives the length of text1.\nLOG ( number1 )\nGives the natural logarithm of a number.\nMATCH ( text1, text2 )\nGives the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nMAX ( number1, number2[ , number3 [. . .]]) )\n\nGives the maximum value of the arguments.\nMIN ( number1, number2[ , number3 [. . .]]) )\n\nGives the minimum value of the arguments.\nNEGATE\nMultiply a number by -1.0.\nNINT ( number1 )\nGives the nearest integer to a real. NINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nOCCUR ( text1, text2 )\nGives the number of times string text2 occurs in string text1.\nREAL ( text1 )\nTry to read a number at the beginning of text1.\nPOWER ( number1, number2 )\n\nGives the value of number1 raised to the power number2.\nSQRT ( number1 )\nGives the square root of a number.\nVVALUE ( variable-name )\n\nUsed for late evaluation of variables. Gives a real value.\nABS ( number1 )\n-> number\nReturns the absolute value of a real.\nNone.\nABS ( -3.2 ) -> 3.2\nNone.\nAll these will return values in current angle units.\nASIN ( number1 )\n-> number\nACOS ( number1 )\n-> number\nATAN ( number1 )\n-> number\nATANT ( number1, number2 )\n-> number\nReturn the arc-cosine, arc-sine or arc-tangent of a number, in degrees.\nATANT returns the arc-tangent of number1/number2 with the appropriate sign. ATANT is useful where the second value is near or equal to zero.\nFor example, (6 0 ATANT) will give the correct result of 90 degrees, but (6 0 D ATAN) will indicate an error when trying to divide by zero.\nNone.\nACOS ( 0.8660254 ) -> 30degrees\nArgument of ACOS or ASIN out of range [-1.0,+1.0]\nATANT (0.0,0.0) is undefined.\nALOG ( number1 )\n-> number\nReturn the exponential function (natural anti-log) of a number.\nNumeric underflow causes the result to be set to zero.\nALOG( -0.7 ) -> 0.4965853\nFloating point overflow.\nARRAY(pos or dir or ori)\n-> number\nConverts a position, direction or orientation value or attribute into three numbers.\nNone\nARRAY(e100 ) -> 100 0 0\nNone.\nARRAYSize ( variable-name )\n-> number\nGive the size of an array variable.\nIf the array variable does not exist, the result is undefined.\nARRAYSIZE(!array) -> 2.0\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nARRAYWIDTH ( variable-name )\n-> number\nGive the largest display with of any string in array variable_name.\nNone.\nIf an array contains the following values:\n!ARRAY[1] \u2019Bread\u2019\n!ARRAY[2] \u2019is\u2019\n!ARRAY[3] \u2019for\u2019\n!ARRAY[4] \u2019life,\u2019\n!ARRAY[5] \u2019not\u2019\n!ARRAY[6] \u2019just\u2019\n!ARRAY[7] \u2019for\u2019\n!ARRAY[8] \u2019breakfast\u2019\nThen\nARRAYWIDTH(!ARRAY -> 9\ndefines the length of \u2019breakfast\u2019.\n\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nCOMPonent dir1 OF pos2\n-> text\nReturns the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nNone.\nCOMP E 45 N of N 0 E 100 U 50 -> 70.710\nNone.\nDISTConvert ( number )\n-> number\nReturns a distance value cast from the input number.\nThe input value is converted to its database units (if it is a physical quantity) and then cast to database units of distance (i.e. mm) and presented in current units of distance.\nNone.\nWhen current distance units are mm\ndistc(1000)\ndistc(10metre)\ndistc( 5pascal)\ndistc (5atm)\n\n-> 1000mm\n-> 10000mm\n-> 5mm\n-> 506625mm\nWhen current distance units are inch\ndistc(1000)\ndistc(10metre)\ndistc( 5pascal)\ndistc (5atm)\n\n-> 39.4in\n-> 393.7in\n-> 0.2in\n-> 19945.9in\nNone.\nAll these will accept values qualified by angle units. If no unit is supplied the value is assumed to be in current angle units (usually degrees).\nSINe ( number1 )\n-> number\nCOSine ( number1 )\n-> number\nTANgent ( number1 )\n-> number\nReturn the sine, cosine or tangent value of a number (considered to be in degrees).\nNone.\nCOS ( 0.0 ) returns 1.0\nTAN ( 45.0 degrees ) returns 1.0\nTAN (0.785 radians) ) returns 0.9992\nDivision by zero for TAN if the sine is (nearly) equal to zero.\nINT ( number1 )\n-> number\nReturn the truncated integer value of a number.\nNone.\nINT ( -23.7 ) -> -23.0\nInteger overflow.\nLENgth ( text1 )\n-> number\nReturn the length of text1.\nNone.\nLENGTH ( \u2019abcdef\u2019 ) -> 6.0\nLENGTH ( \u2019\u2019 ) -> 0.0\nNone.\nLOG ( number1 )\n-> number\nReturn the natural logarithm of a number.\nNone.\nLOG( 3 ) -> 1 0986123\nNegative arguments.\nMATch ( text1 , text2)\n-> number\nReturn the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nNone.\nMATCH ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> 3.0\nMATCH ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> 0.0\nMATCH ( \u2019abcdef\u2019 , \u2019\u2019 ) -> 1.0\nNone.\nMAX ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nMIN ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nReturn the maximum or minimum value of the arguments.\nValues being evaluated are assumed to of a common physical quantity.\nIf no unit qualifiers are supplied they are simply numbers.\nIf a physical quantity is defined the result will be in current units of that quantity.\nIf unqualified numbers are mixed with unit values they are assumed to be in the current units of that physical quantity.\nIf quantities are in mixed units they are all compared in comparison to a standard unit.\nIf quantities are of different types of physical quantities a warning is issued and the numeric result compares the values in their database units.\nMin and Max return a value with the same dimension as that of their arguments.\nMAX ( 1 , 3.4 ) -> 3.4\nMIN ( 7.6 , -12.33 , 2.3 ) -> -12.33\nMIN (7.6ft, 12.33inch, 1000mm ) -> 12.3 in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1000 ) -> 1000in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1kg ) -> 2316.5 (database mm equivalent of 7.6ft)\nNone.\nNEGate ( number1 )\n-> number\nMultiply a real by -1.0.\nNone.\nNEG ( 1 ) -> -1.0\nNone.\nNINT ( number1 )\n-> number\nReturn the nearest integer to a real. NINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nNone.\nNINT ( 1.1 ) -> 1.0\nNINT ( -23.7 ) -> -24.0\nNINT ( 1.5 ) -> 2.0\nNINT ( -11.5 ) -> -12.0\nInteger overflow.\nOCCUR(text1, text2)\n-> integer\nCounts the number of times string text2 occurs in string text1\nNone.\nOCCUR (\u2019ABBACCBBBBBAB\u2019, \u2019BB\u2019) -> 3\nOCCUR(\u2019ZZZZZZZZZZZ\u2019, \u2019A\u2019) -> 0\nNone.\nREAL ( text1 )\n-> number\nTry to read a real number at the beginning of text1.\nNote that if text is in the form of an exponent, (-12E-1 in the third example), there must be no spaces in it.\nNote: this function was formerly called NUMBER.\nNumeric underflow causes the result to be set to zero.\nIf the text string contains units they are ignored and the value only is returned.\nIf the test string contains text that is NOT a valid unit it will generate an error.\nIf the text string is space separated from the number it is completely ignored.\nREAL ( \u201912.34\u2019) -> 12.34\nREAL ( \u2019 7.23 E 3 meters\u2019 ) -> 7.23\nREAL ( \u2019 -12E-1 meters \u2019 ) -> -1.2\nREAL (' 1200 fred ' ) -> 1200\nREAL (' 1200fred ' ) -> returns an error\nThis will return the value of the number in the string IGNORING any unit qualifier. The unit qualifier must still be a valid unit qualifier. This is done so that output from $! And VAR ! commands can still be accepted by the REAL function.\nUnable to convert the text into a real number.\nPOWer ( number1 , number2 )\n-> real\nReturn the value of number1 raised to the power number2.\nIf the value being raised to a power is that of a physical quantity the result is also of a physical quantity.(in relevant current units).\nIf the resultant quantity is non physical (for example, by raising to a fractional power, or an extreme power, a warning is given and only the value of quantity is raised to the power.\nIf the power is a physical quantity this also gives a warning.\nPOWER ( -2 , 3 ) -> -8\nPOWER ( -2inch , 2 ) -> 4in2\nPOWER ( 2inch, 3.5 ) -> returns 11.314 with an error (i.e. 2**3.5)\nFloating point overflow.\nZero first argument and non-positive second argument (effectively divide by zero).\nNegative first argument and non-integer second argument.\nSQrt ( number1 )\n-> number\nReturn the square root of a real.\nUnits are consolidated across SQRT. The resultant value will be in current units of that quantity.\nIf the resultant quantity has no recognized physical dimension a warning is given and the value return will be a number relating to the input value in database units.\nSQRT ( 4 ) -> 2.0\nSQRT ( 4inch2 ) -> 2.0inch\nsqrt ( 4inch3 ) -> a warning and 256.02 which is sqrt (4*25.4mm)\nNegative argument.\nVVALUE is used for the late evaluation of PML variables.\nVVALue( variable_name )\n-> number\nVVALue( variable_name , number )\n-> number\nWith one argument, returns value of the scalar variable or value of the array variable element as a number.\nWith two arguments, returns value of the element corresponding to the index number as a number.\nThe value of the variable will be returned, irrespective of its units.\nThis will return the value of the number in the string IGNORING any unit qualifier. The unit qualifier must still be a valid unit qualifier. This is done so that output from $! And VAR ! commands can still be accepted by the VVAL function.\nIf the scalar variable, the array variable or the array variable element does not exist, the result is undefined.\nVVAL ( !array[1] ) -> 1.0\nVVAL ( !array , 2 ) -> 0.0\nScalar variable may not be indexed. For example, VTEXT (!var[1]) ) will return an error.\nArray variable must have an index. For example, VTEXT ( !array ) ) will return an error.\nThe string can not be converted to a number.\n\nFunction\nComments\nABS ( number1 )\nGives the absolute value of a number\nACOS ( number1 )\nGives the arc cosine of a number, in degrees.\nASIN ( number1 )\nGives the arc sine of a number, in degrees.\nATAN ( number1 )\nGives the arc tangent of a number, in degrees.\nATANT ( number1, number2 )\nGives the arc tangent of number1/number2, in degrees, with the appropriate sign.\nALOG ( number1 )\nGives the exponential function (natural anti-log) of a number.\nARRAY(pos or dir or ori)\nConverts a position, direction or orientation value or attribute into three numbers.\nARRAYSIZE ( variable-name )\nGives the size of an array variable.\nARRAYWIDTH( variable-name )\nGives the largest display width of any string in array variable-name.\nCOMPONENT dir OF pos2\nGives the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nINT ( number1 )\nGives the truncated integer value of a number.\nSIN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nCOS ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nTAN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nLENGTH ( text1 )\nGives the length of text1.\nLOG ( number1 )\nGives the natural logarithm of a number.\nMATCH ( text1, text2 )\nGives the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nMAX ( number1, number2[ , number3 [. . .]]) )\nGives the maximum value of the arguments.\nMIN ( number1, number2[ , number3 [. . .]]) )\nGives the minimum value of the arguments.\nNEGATE\nMultiply a number by -1.0.\nNINT ( number1 )\nGives the nearest integer to a real. NINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nOCCUR ( text1, text2 )\nGives the number of times string text2 occurs in string text1.\nREAL ( text1 )\nTry to read a number at the beginning of text1.\nPOWER ( number1, number2 )\nGives the value of number1 raised to the power number2.\nSQRT ( number1 )\nGives the square root of a number.\nVVALUE ( variable-name )\nUsed for late evaluation of variables. Gives a real value.\nSynopsis\nABS ( number1 )\n-> number\nDescription\nReturns the absolute value of a real.\nSide Effects\nNone.\nExample\nABS ( -3.2 ) -> 3.2\nErrors\nNone.\nSynopsis\nASIN ( number1 )\n-> number\nACOS ( number1 )\n-> number\nATAN ( number1 )\n-> number\nATANT ( number1, number2 )\n-> number\nDescription\nReturn the arc-cosine, arc-sine or arc-tangent of a number, in degrees.\nATANT returns the arc-tangent of number1/number2 with the appropriate sign. ATANT is useful where the second value is near or equal to zero.\nFor example, (6 0 ATANT) will give the correct result of 90 degrees, but (6 0 D ATAN) will indicate an error when trying to divide by zero.\nSide Effects\nNone.\nExample\nACOS ( 0.8660254 ) -> 30degrees\nErrors\nArgument of ACOS or ASIN out of range [-1.0,+1.0]\nATANT (0.0,0.0) is undefined.\nSynopsis\nALOG ( number1 )\n-> number\nDescription\nReturn the exponential function (natural anti-log) of a number.\nSide Effects\nNumeric underflow causes the result to be set to zero.\nExample\nALOG( -0.7 ) -> 0.4965853\nErrors\nFloating point overflow.\nSynopsis\nARRAY(pos or dir or ori)\n-> number\nDescription\nConverts a position, direction or orientation value or attribute into three numbers.\nSide Effects\nNone\nExample\nARRAY(e100 ) -> 100 0 0\nErrors\nNone.\nSynopsis\nARRAYSize ( variable-name )\n-> number\nDescription\nGive the size of an array variable.\nSide Effects\nIf the array variable does not exist, the result is undefined.\nExample\nARRAYSIZE(!array) -> 2.0\nErrors\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nSynopsis\nARRAYWIDTH ( variable-name )\n-> number\nDescription\nGive the largest display with of any string in array variable_name.\nSide Effects\nNone.\nExample\nIf an array contains the following values:\n!ARRAY[1] \u2019Bread\u2019\n!ARRAY[2] \u2019is\u2019\n!ARRAY[3] \u2019for\u2019\n!ARRAY[4] \u2019life,\u2019\n!ARRAY[5] \u2019not\u2019\n!ARRAY[6] \u2019just\u2019\n!ARRAY[7] \u2019for\u2019\n!ARRAY[8] \u2019breakfast\u2019\nThen\nARRAYWIDTH(!ARRAY -> 9\ndefines the length of \u2019breakfast\u2019.\nErrors\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nSynopsis\nCOMPonent dir1 OF pos2\n-> text\nDescription\nReturns the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nSide Effects\nNone.\nExample\nCOMP E 45 N of N 0 E 100 U 50 -> 70.710\nErrors\nNone.\nSynopsis\nDISTConvert ( number )\n-> number\nDescription\nReturns a distance value cast from the input number.\nThe input value is converted to its database units (if it is a physical quantity) and then cast to database units of distance (i.e. mm) and presented in current units of distance.\nSide Effects\nNone.\nExample\nWhen current distance units are mm\ndistc(1000)\ndistc(10metre)\ndistc( 5pascal)\ndistc (5atm)\n-> 1000mm\n-> 10000mm\n-> 5mm\n-> 506625mm\nWhen current distance units are inch\ndistc(1000)\ndistc(10metre)\ndistc( 5pascal)\ndistc (5atm)\n-> 39.4in\n-> 393.7in\n-> 0.2in\n-> 19945.9in\nErrors\nNone.\nSynopsis\nSINe ( number1 )\n-> number\nCOSine ( number1 )\n-> number\nTANgent ( number1 )\n-> number\nDescription\nReturn the sine, cosine or tangent value of a number (considered to be in degrees).\nSide Effects\nNone.\nExample\nCOS ( 0.0 ) returns 1.0\nTAN ( 45.0 degrees ) returns 1.0\nTAN (0.785 radians) ) returns 0.9992\nErrors\nDivision by zero for TAN if the sine is (nearly) equal to zero.\nSynopsis\nINT ( number1 )\n-> number\nDescription\nReturn the truncated integer value of a number.\nSide Effects\nNone.\nExample\nINT ( 1.6 )    -> 1.0\nINT ( -23.7 ) -> -23.0\nErrors\nInteger overflow.\nSynopsis\nLENgth ( text1 )\n-> number\nDescription\nReturn the length of text1.\nSide Effects\nNone.\nExample\nLENGTH ( \u2019abcdef\u2019 ) -> 6.0\nLENGTH ( \u2019\u2019 ) -> 0.0\nErrors\nNone.\nSynopsis\nLOG ( number1 )\n-> number\nDescription\nReturn the natural logarithm of a number.\nSide Effects\nNone.\nExample\nLOG( 3 ) -> 1 0986123\nErrors\nNegative arguments.\nSynopsis\nMATch ( text1 , text2)\n-> number\nDescription\nReturn the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nSide Effects\nNone.\nExample\nMATCH ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> 3.0\nMATCH ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> 0.0\nMATCH ( \u2019abcdef\u2019 , \u2019\u2019 ) -> 1.0\nErrors\nNone.\nSynopsis\nMAX ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nMIN ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nDescription\nReturn the maximum or minimum value of the arguments.\nSide Effects\nValues being evaluated are assumed to of a common physical quantity.\nIf no unit qualifiers are supplied they are simply numbers.\nIf a physical quantity is defined the result will be in current units of that quantity.\nIf unqualified numbers are mixed with unit values they are assumed to be in the current units of that physical quantity.\nIf quantities are in mixed units they are all compared in comparison to a standard unit.\nIf quantities are of different types of physical quantities a warning is issued and the numeric result compares the values in their database units.\nMin and Max return a value with the same dimension as that of their arguments.\nExample\nMAX ( 1 , 3.4 ) -> 3.4\nMIN ( 7.6 , -12.33 , 2.3 ) -> -12.33\nMIN (7.6ft, 12.33inch, 1000mm ) -> 12.3 in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1000 ) -> 1000in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1kg ) -> 2316.5 (database mm equivalent of 7.6ft)\nErrors\nNone.\nSynopsis\nNEGate ( number1 )\n-> number\nDescription\nMultiply a real by -1.0.\nSide Effects\nNone.\nExample\nNEG ( 1 ) -> -1.0\nErrors\nNone.\nSynopsis\nNINT ( number1 )\n-> number\nDescription\nReturn the nearest integer to a real. NINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nSide Effects\nNone.\nExample\nNINT ( 1.1 ) -> 1.0\nNINT ( -23.7 ) -> -24.0\nNINT ( 1.5 ) -> 2.0\nNINT ( -11.5 ) -> -12.0\nErrors\nInteger overflow.\nSynopsis\nOCCUR(text1, text2)\n-> integer\nDescription\nCounts the number of times string text2 occurs in string text1\nSide Effects\nNone.\nExample\nOCCUR (\u2019ABBACCBBBBBAB\u2019, \u2019BB\u2019) -> 3\nOCCUR(\u2019ZZZZZZZZZZZ\u2019, \u2019A\u2019) -> 0\nErrors\nNone.\nSynopsis\nREAL ( text1 )\n-> number\nDescription\nTry to read a real number at the beginning of text1.\nNote that if text is in the form of an exponent, (-12E-1 in the third example), there must be no spaces in it.\nNote: this function was formerly called NUMBER.\nSide Effects\nNumeric underflow causes the result to be set to zero.\nIf the text string contains units they are ignored and the value only is returned.\nIf the test string contains text that is NOT a valid unit it will generate an error.\nIf the text string is space separated from the number it is completely ignored.\nExample\nREAL ( \u201912.34\u2019) -> 12.34\nREAL ( \u2019 7.23 E 3 meters\u2019 ) -> 7.23\nREAL ( \u2019 -12E-1 meters \u2019 ) -> -1.2\nREAL (' 1200 fred ' ) -> 1200\nREAL (' 1200fred ' ) -> returns an error\nThis will return the value of the number in the string IGNORING any unit qualifier. The unit qualifier must still be a valid unit qualifier. This is done so that output from $! And VAR ! commands can still be accepted by the REAL function.\nNote:\nThe extension of these functions are NOT supported in DARS as they require PML functionality.\nErrors\nUnable to convert the text into a real number.\nSynopsis\nPOWer ( number1 , number2 )\n-> real\nDescription\nReturn the value of number1 raised to the power number2.\nSide Effects\nIf the value being raised to a power is that of a physical quantity the result is also of a physical quantity.(in relevant current units).\nIf the resultant quantity is non physical (for example, by raising to a fractional power, or an extreme power, a warning is given and only the value of quantity is raised to the power.\nIf the power is a physical quantity this also gives a warning.\nExample\nPOWER ( -2 , 3 ) -> -8\nPOWER ( -2inch , 2 ) -> 4in2\nPOWER ( 2inch, 3.5 ) -> returns 11.314 with an error (i.e. 2**3.5)\nErrors\nFloating point overflow.\nZero first argument and non-positive second argument (effectively divide by zero).\nNegative first argument and non-integer second argument.\nSynopsis\nSQrt ( number1 )\n-> number\nDescription\nReturn the square root of a real.\nSide Effects\nUnits are consolidated across SQRT. The resultant value will be in current units of that quantity.\nIf the resultant quantity has no recognized physical dimension a warning is given and the value return will be a number relating to the input value in database units.\nExample\nSQRT ( 4 ) -> 2.0\nSQRT ( 4inch2 ) -> 2.0inch\nsqrt ( 4inch3 ) -> a warning and 256.02 which is sqrt (4*25.4mm)\nErrors\nNegative argument.\nSynopsis\nVVALue( variable_name )\n-> number\nVVALue( variable_name , number )\n-> number\nDescription\nWith one argument, returns value of the scalar variable or value of the array variable element as a number.\nWith two arguments, returns value of the element corresponding to the index number as a number.\nThe value of the variable will be returned, irrespective of its units.\nThis will return the value of the number in the string IGNORING any unit qualifier. The unit qualifier must still be a valid unit qualifier. This is done so that output from $! And VAR ! commands can still be accepted by the VVAL function.\nNote:\nThe extension of these functions are NOT supported in DARS as they require PML functionality.\nSide Effects\nIf the scalar variable, the array variable or the array variable element does not exist, the result is undefined.\nExample\nVVAL ( !array[1] ) -> 1.0\nVVAL ( !array , 2 ) -> 0.0\nErrors\nScalar variable may not be indexed. For example, VTEXT (!var[1]) ) will return an error.\nArray variable must have an index. For example, VTEXT ( !array ) ) will return an error.\nThe string can not be converted to a number.\nNote:\nThe extension of these functions are NOT supported in DARS as they require PML functionality.\nNote:\nThe extension of these functions are NOT supported in DARS as they require PML functionality.\n\n\n\nFunction\nComments\nABS ( number1 )\nACOS ( number1 )\nASIN ( number1 )\nATAN ( number1 )\nATANT ( number1, number2 )\nnumber1\nnumber2\nALOG ( number1 )\nARRAY(pos or dir or ori)\nARRAYSIZE ( variable-name )\nARRAYWIDTH( variable-name )\nCOMPONENT dir OF pos2\npos2\ndir1\nINT ( number1 )\nSIN ( number1 )\nCOS ( number1 )\nTAN ( number1 )\nLENGTH ( text1 )\nLOG ( number1 )\nMATCH ( text1, text2 )\ntext2\ntext1\ntext2\ntext1\nMAX ( number1, number2[ , number3 [. . .]]) )\nMIN ( number1, number2[ , number3 [. . .]]) )\nNEGATE\nNINT ( number1 )\nOCCUR ( text1, text2 )\ntext2\ntext1\nREAL ( text1 )\ntext1\nPOWER ( number1, number2 )\nnumber1\nnumber2\nSQRT ( number1 )\nVVALUE ( variable-name )\nSynopsis\nABS ( number1 )\n-> number\nDescription\nSide Effects\nExample\nABS ( -3.2 ) -> 3.2\nErrors\nSynopsis\nASIN ( number1 )\n-> number\nACOS ( number1 )\n-> number\nATAN ( number1 )\n-> number\nATANT ( number1, number2 )\n-> number\nDescription\nnumber1/number2\nSide Effects\nExample\nACOS ( 0.8660254 ) -> 30degrees\nErrors\nATANT (0.0,0.0)\nSynopsis\nALOG ( number1 )\n-> number\nDescription\nSide Effects\nExample\nALOG( -0.7 ) -> 0.4965853\nErrors\nSynopsis\nARRAY(pos or dir or ori)\n-> number\nDescription\nSide Effects\nExample\nARRAY(e100 ) -> 100 0 0\nErrors\nSynopsis\nARRAYSize ( variable-name )\n-> number\nDescription\nSide Effects\nExample\nErrors\nSynopsis\nARRAYWIDTH ( variable-name )\n-> number\nDescription\nvariable_name\nSide Effects\nExample\nIf an array contains the following values:\n!ARRAY[1] \u2019Bread\u2019\n!ARRAY[2] \u2019is\u2019\n!ARRAY[3] \u2019for\u2019\n!ARRAY[4] \u2019life,\u2019\n!ARRAY[5] \u2019not\u2019\n!ARRAY[6] \u2019just\u2019\n!ARRAY[7] \u2019for\u2019\n!ARRAY[8] \u2019breakfast\u2019\nARRAYWIDTH(!ARRAY -> 9\nErrors\nSynopsis\nCOMPonent dir1 OF pos2\n-> text\nDescription\npos2\ndir1.\nSide Effects\nExample\nCOMP E 45 N of N 0 E 100 U 50 -> 70.710\nErrors\nSynopsis\nDISTConvert ( number )\n-> number\nDescription\nSide Effects\nExample\n-> 1000mm\n-> 10000mm\n-> 5mm\n-> 506625mm\ndistc(1000)\ndistc(10metre)\ndistc( 5pascal)\ndistc (5atm)\n-> 39.4in\n-> 393.7in\n-> 0.2in\n-> 19945.9in\nErrors\nSynopsis\nSINe ( number1 )\n-> number\nCOSine ( number1 )\n-> number\nTANgent ( number1 )\n-> number\nDescription\nSide Effects\nExample\nCOS ( 0.0 ) returns 1.0\nTAN ( 45.0 degrees ) returns 1.0\nTAN (0.785 radians) ) returns 0.9992\nErrors\nSynopsis\nINT ( number1 )\n-> number\nDescription\nSide Effects\nExample\nErrors\nSynopsis\nLENgth ( text1 )\n-> number\nDescription\ntext1\nSide Effects\nExample\nLENGTH ( \u2019abcdef\u2019 ) -> 6.0\nLENGTH ( \u2019\u2019 ) -> 0.0\nErrors\nSynopsis\nLOG ( number1 )\n-> number\nDescription\nSide Effects\nExample\nLOG( 3 ) -> 1 0986123\nErrors\nSynopsis\nMATch ( text1 , text2)\n-> number\nDescription\ntext2\ntext1\ntext2\ntext1\nSide Effects\nExample\nMATCH ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> 3.0\nMATCH ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> 0.0\nMATCH ( \u2019abcdef\u2019 , \u2019\u2019 ) -> 1.0\nErrors\nSynopsis\nMAX ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nMIN ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nDescription\nSide Effects\nExample\nMAX ( 1 , 3.4 ) -> 3.4\nMIN ( 7.6 , -12.33 , 2.3 ) -> -12.33\nMIN (7.6ft, 12.33inch, 1000mm ) -> 12.3 in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1000 ) -> 1000in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1kg ) -> 2316.5 (database mm equivalent of 7.6ft)\nSynopsis\nNEGate ( number1 )\n-> number\nDescription\nSide Effects\nExample\nNEG ( 1 ) -> -1.0\nErrors\nSynopsis\nDescription\nNINT(N+0.5)\nN+1\nN\nN\nN\nSide Effects\nExample\nNINT ( 1.1 ) -> 1.0\nNINT ( -23.7 ) -> -24.0\nNINT ( 1.5 ) -> 2.0\nNINT ( -11.5 ) -> -12.0\nErrors\nSynopsis\nOCCUR(text1, text2)\n-> integer\nDescription\ntext2\ntext1\nSide Effects\nExample\nOCCUR (\u2019ABBACCBBBBBAB\u2019, \u2019BB\u2019) -> 3\nOCCUR(\u2019ZZZZZZZZZZZ\u2019, \u2019A\u2019) -> 0\nErrors\nSynopsis\nREAL ( text1 )\n-> number\nDescription\ntext1\nSide Effects\nExample\nREAL ( \u201912.34\u2019) -> 12.34\nREAL ( \u2019 7.23 E 3 meters\u2019 ) -> 7.23\nREAL ( \u2019 -12E-1 meters \u2019 ) -> -1.2\nREAL (' 1200 fred ' ) -> 1200\nREAL (' 1200fred ' ) -> returns a\nNote\n:\nErrors\nSynopsis\nPOWer ( number1 , number2 )\n-> real\nDescription\nnumber1\nnumber2\nSide Effects\nExample\nPOWER ( -2 , 3 ) -> -8\nPOWER ( -2inch , 2 ) -> 4in2\nPOWER ( 2inch, 3.5 ) -> returns 11.314 with an error (i.e. 2**3.5)\nErrors\nSynopsis\nSQrt ( number1 )\n-> number\nDescription\nSide Effects\nExample\nSQRT ( 4 ) -> 2.0\nSQRT ( 4inch2 ) -> 2.0inch\nsqrt ( 4inch3 ) -> a warning and 256.02 which is sqrt (4*25.4mm)\nErrors\nSynopsis\nVVALue( variable_name )\n-> number\nVVALue( variable_name , number )\n-> number\nDescription\nNote\n:\nSide Effects\nExample\nVVAL ( !array[1] ) -> 1.0\nVVAL ( !array , 2 ) -> 0.0\nErrors\nVTEXT (!var[1]) )\nVTEXT ( !array ) )"}
{"Headers": "Real array expressions", "Content": "Real array expressions can contain attributes of type real array, for example: DESP.\n\n\n"}
{"Headers": "Real array expressions", "Content": "In real expressions the dimension of the result is tracked using:\nIf at any time a value with no dimension occurs where a value with a specific dimension is needed then the value is taken to be one of that dimension in the current working units of that dimension (for example, mm for distances, degrees for angles). This will occur in addition and subtraction operations, and arguments for typed functions (for example,. trigonometric).\nWhenever a clash of physical quantity occurs then either a warning or an error will be raised (for example, SIN(25inch).\nIn all expressions and functions physical quantities are tracked and the result, wherever possible is returned in the current units of the resultant physical quantity (dimension). If the system cannot do this (for example, the expression is not dimensionally sound, or the dimension exceeds the scope which the system can track) then a warning is issued and a simple numeric result is returned.\nWhen a user enters a literal value then the type of physical quantity is not known and the decision as to what it is determined to make it consistent with the context with respect to other values in the expression. When it is finally determined the value is then taken to be in the current units of that quantity. The method of this determination is normally straightforward and is described in specific sections above.\nThe units for PML variables are also unknown. Where units are known and handled similarly in expression.\nTo cope with \u2019unknown\u2019 units each value remembers its original units internally. An attempt is then made to allow for \u2019unknown\u2019 units across operators and within functions. In general the physical quantity of the result of a function, or expressions, is tracked by the system and the resulting value is one of the resultant physical quantities. For example multiplying 3 distances together gives a result of a volume which will have units such as gallons, litres or cubic ft.\nOn comparison, addition or subtraction of two values then if one has units and the other has none (i.e. not a physical quantity) it is assumed to be the same sort of quantity as the other, and in the current units of that quantity.\nFor example:\nIf we are working in distance units of inches, it is known that XLEN is a distance value. Internally the value is held in mm, but the units are held as INCH. The units for \u201910\u2019 are held as unknown. On doing the comparison, the \u201910\u2019 is assumed to be inches and thus multiplied by 25.4 to make sure that the comparison works as expected.\nSpecial action is also taken to preserve the correct units across multiplication, division, POWER and SQRT, as described in the sections above.\n(XLEN GT 10).\nThe dimension of any attribute values used (for example, XLEN, BANG, DENS, GVOL)\nThe unit qualifiers of any values supplied\nThe known result of any function (for example, ASIN returns an angle, POW, SQRT return a computed dimension, MIN/MAX that of their arguments etc.)\nThe computed result of multiplication and division operation. (for example, GWEI/GVOL is a density)\nThe need for consistency for addition and subtraction operations\nThe dimension of any attribute values used (for example, XLEN, BANG, DENS, GVOL)\nThe dimension of any attribute values used (for example, XLEN, BANG, DENS, GVOL)\nThe unit qualifiers of any values supplied\nThe unit qualifiers of any values supplied\nThe known result of any function (for example, ASIN returns an angle, POW, SQRT return a computed dimension, MIN/MAX that of their arguments etc.)\nThe known result of any function (for example, ASIN returns an angle, POW, SQRT return a computed dimension, MIN/MAX that of their arguments etc.)\nThe computed result of multiplication and division operation. (for example, GWEI/GVOL is a density)\nThe computed result of multiplication and division operation. (for example, GWEI/GVOL is a density)\nThe need for consistency for addition and subtraction operations\nThe need for consistency for addition and subtraction operations\n\n\n"}
{"Headers": "Ids", "Content": "IDs can be used in expressions. IDs can be any of the following:\nSPEC OF SPREF OF FLAN 1 OF NEXT BRAN.\nHEAD TUBE OF /BRAN1.\nElement name, for example: /VESS1.\nRefno, for example: =23/456.\nElement type further up the hierarchy, for example: SITE.\nNumber within member list, for example: 3.\nType and number within member list, for example: BOX 3.\nNEXT, PREV for next, previous within current list. Optionally with a count and/or element type, for example: NEXT 2 BOX, LAST CYL.\nNEXT, PREV MEMBER for next, previous within member list. Optionally with a count and/or element type.\nIf the element type given is only valid as a member then MEMBER is assumed. For example, NEXT BOX at an EQUIPMENT will assume MEMBER.\nFIRST, LAST for first and last in current list. Optionally with a count and/or element type.\nFIRST, LAST MEMBER for first and last in member list. If the element type given is only valid as a member then MEMBER is assumed.\nEND to navigate up from current list.\nEND is similar to owner but not quite the same. For example, if the current element is a GROUP MEMBER, and it has been reached from the GROUP then END will return to the group but OWNE will go to the true owner.\nAttribute of type ref, for example: CREF\nSAME to mean last current element\nNULREF to mean =0/0\nCE for the current element\n\u2019OF\u2019 may be used to nest the options indefinitely. For example:\nSPEC OF SPREF OF FLAN 1 OF NEXT BRAN.\nThis denotes the SPEC element owing the SELE element pointed to by the SPREF attribute on the first FLANGE of the next BRANCH. ILEAVE TUBE, IARRIV TUBE, HEAD TUBE, TAIL TUBE can be added to denote tube. For example:\nHEAD TUBE OF /BRAN1.\nAn error will occur if there is no implied tube for the element concerned.\nID arrays can also be used in expressions. For example, CRFA.\nElement name, for example: /VESS1.\nElement name, for example: /VESS1.\nRefno, for example: =23/456.\nRefno, for example: =23/456.\nElement type further up the hierarchy, for example: SITE.\nElement type further up the hierarchy, for example: SITE.\nNumber within member list, for example: 3.\nNumber within member list, for example: 3.\nType and number within member list, for example: BOX 3.\nType and number within member list, for example: BOX 3.\nNEXT, PREV for next, previous within current list. Optionally with a count and/or element type, for example: NEXT 2 BOX, LAST CYL.\nNEXT, PREV for next, previous within current list. Optionally with a count and/or element type, for example: NEXT 2 BOX, LAST CYL.\nNEXT, PREV MEMBER for next, previous within member list. Optionally with a count and/or element type.\nNEXT, PREV MEMBER for next, previous within member list. Optionally with a count and/or element type.\nIf the element type given is only valid as a member then MEMBER is assumed. For example, NEXT BOX at an EQUIPMENT will assume MEMBER.\nIf the element type given is only valid as a member then MEMBER is assumed. For example, NEXT BOX at an EQUIPMENT will assume MEMBER.\nFIRST, LAST for first and last in current list. Optionally with a count and/or element type.\nFIRST, LAST for first and last in current list. Optionally with a count and/or element type.\nFIRST, LAST MEMBER for first and last in member list. If the element type given is only valid as a member then MEMBER is assumed.\nFIRST, LAST MEMBER for first and last in member list. If the element type given is only valid as a member then MEMBER is assumed.\nEND to navigate up from current list.\nEND to navigate up from current list.\nEND is similar to owner but not quite the same. For example, if the current element is a GROUP MEMBER, and it has been reached from the GROUP then END will return to the group but OWNE will go to the true owner.\nEND is similar to owner but not quite the same. For example, if the current element is a GROUP MEMBER, and it has been reached from the GROUP then END will return to the group but OWNE will go to the true owner.\nAttribute of type ref, for example: CREF\nAttribute of type ref, for example: CREF\nSAME to mean last current element\nSAME to mean last current element\nNULREF to mean =0/0\nNULREF to mean =0/0\nCE for the current element\nCE for the current element\n\u2019OF\u2019 may be used to nest the options indefinitely. For example:\nSPEC OF SPREF OF FLAN 1 OF NEXT BRAN.\n\u2019OF\u2019 may be used to nest the options indefinitely. For example:\nThis denotes the SPEC element owing the SELE element pointed to by the SPREF attribute on the first FLANGE of the next BRANCH. ILEAVE TUBE, IARRIV TUBE, HEAD TUBE, TAIL TUBE can be added to denote tube. For example:\nHEAD TUBE OF /BRAN1.\nThis denotes the SPEC element owing the SELE element pointed to by the SPREF attribute on the first FLANGE of the next BRANCH. ILEAVE TUBE, IARRIV TUBE, HEAD TUBE, TAIL TUBE can be added to denote tube. For example:\nAn error will occur if there is no implied tube for the element concerned.\nID arrays can also be used in expressions. For example, CRFA.\nAn error will occur if there is no implied tube for the element concerned.\nNote:\nSome of the ID syntax clashes with other types. To allow for this, an id expression may always be preceded with the keyword ID. For example, ID 3 will mean the third member of the current list rather than a number of value 3.\n\n\n\nNote\n:"}
{"Headers": "Defining position", "Content": "The basic ways of defining a position are:\nThe Cartesian position may optionally be followed by WRT to specify the axis system. Refer to WRT.\nPOS OF /VESS1 WRT /* or P1 POS OF /CYL2\nN 45 W 20000 U 1000\nN 1000 FROM /ATEST.\nN 1000 FROM P1 OF /BOX2.\nN 1000 FROM POSS OF /SCTN1\nN (DESP[1] + 10) E\nPosition attribute plus optional WRT. For example:\nPOS OF /VESS1 WRT /* or P1 POS OF /CYL2\nCartesian position. For example:\nN 45 W 20000 U 1000\nCartesian position from an element. For example:\nN 1000 FROM /ATEST.\nCartesian position from a ppoint. For example:\nN 1000 FROM P1 OF /BOX2.\nCartesian position from an attribute. For example:\nN 1000 FROM POSS OF /SCTN1\nAny numeric value within a position may itself be an expression. For example: the following is a valid position expression\nN (DESP[1] + 10) E\nPosition attribute plus optional WRT. For example:\nPOS OF /VESS1 WRT /* or P1 POS OF /CYL2\nPosition attribute plus optional WRT. For example:\nCartesian position. For example:\nN 45 W 20000 U 1000\nCartesian position. For example:\nCartesian position from an element. For example:\nN 1000 FROM /ATEST.\nCartesian position from an element. For example:\nCartesian position from a ppoint. For example:\nN 1000 FROM P1 OF /BOX2.\nCartesian position from a ppoint. For example:\nCartesian position from an attribute. For example:\nN 1000 FROM POSS OF /SCTN1\nCartesian position from an attribute. For example:\nAny numeric value within a position may itself be an expression. For example: the following is a valid position expression\nN (DESP[1] + 10) E\nAny numeric value within a position may itself be an expression. For example: the following is a valid position expression\n\n\n\nWRT\nWRT"}
{"Headers": "WRT keyword", "Content": "The WRT keyword is used to toggle between absolute and relative units.\nWhen we specify an element (or attribute of an element) we are specifying an absolute point in world space. The point can be given in world space or some other axis. Normally the answer is required relative to the owner axis system and this is taken as the default. For example:\nQ POS\n$ will return the position of the current element\n$ relatively to its owner.\nQ POS OF /EQUIP1\n$ will return the position of EQUIP1 relative to its\n$ owner.\nQ POS\n$ will return the position of the current element\n$ relatively to its owner.\nQ POS OF /EQUIP1\n$ will return the position of EQUIP1 relative to its\n$ owner.\nIf we require the result in some other axis system then the WRT keyword is used. For example:\nQ POS WRT /*\n$.for the position in world coordinates.\nQ POS WRT /*\n$.for the position in world coordinates.\nWhen we specify a Cartesian coordinate we are dealing with a relative position.\nFor example, \u2019N 10\u2019 is meaningless until we specify the axis system, or default to an axis system.\nAgain we use WRT to do this, although it is important to note that in this case we are going from a relative position to an absolute position (in the previous example WRT was used to go from an absolute position to a relative one).\nFor example:\nN 100 WRT /BOX1\n$ specifies an absolute position in world space\n$ which is N100 of /BOX1.\nN 100 WRT /BOX1\n$ specifies an absolute position in world space\n$ which is N100 of /BOX1.\nThe default is that Cartesian coordinates are in the owning element\u2019s axis system. This absolute position can be expressed in different coordinate systems: the default is again the owner\u2019s axis system.\nA SITE at (0,0,0)\nWith default (World) orientation\nA ZONE at (100,0,0)\nWith default (World) orientation\nAn EQUIPMENT at (100,0,0)\nWith orientation \u2019N IS E\nA BOX at (-100,0,0)\nWith default (World) orientation\nThe result of Q (N 100 WRT /BOX1), will depend on the current element.\nWorld\n(300,100,0), in World coordinates.\nSite\n(300,100,0) in World coordinates because the World is the owner of the current element.\nZone\n(300,100,0) in World coordinates, because the Site is the owner of the current element, and the Site coordinates are the same as the World coordinates.\nEquipment\n(200,100,0), which is the position relative to its owner, the Zone.\nBox\n(100,100,0) which is the position relative to its owner, the Equipment.\nWRT can be further qualified by FROM.\nQ POS\n$ will return the position of the current element\n$ relatively to its owner.\nQ POS OF /EQUIP1\n$ will return the position of EQUIP1 relative to its\n$ owner.\nQ POS WRT /*\n$.for the position in world coordinates.\nN 100 WRT /BOX1\n$ specifies an absolute position in world space\n$ which is N100 of /BOX1.\nItem\nComments\nA SITE at (0,0,0)\nWith default (World) orientation\nA ZONE at (100,0,0)\nWith default (World) orientation\nAn EQUIPMENT at (100,0,0)\nWith orientation \u2019N IS E\nA BOX at (-100,0,0)\nWith default (World) orientation\nLocation\nResult\nWorld\n(300,100,0), in World coordinates.\nSite\n(300,100,0) in World coordinates because the World is the owner of the current element.\nZone\n(300,100,0) in World coordinates, because the Site is the owner of the current element, and the Site coordinates are the same as the World coordinates.\nEquipment\n(200,100,0), which is the position relative to its owner, the Zone.\nBox\n(100,100,0) which is the position relative to its owner, the Equipment.\nNote:\nThe CONSTRUCT syntax uses the world as the default axis.\n\n\n\nQ POS\nQ POS OF /EQUIP1\nQ POS WRT /*\nN 100 WRT /BOX1\nNote\n:\nQ (N 100 WRT /BOX1)"}
{"Headers": "WRT keyword", "Content": "Two positions can be compared with EQ, NE, GT, LT, GE or LE. The pairs of coordinates are only compared in the coordinate axes for which the two positions are defined. A position attribute always has all three coordinates defined.\nFor positions entered by you, only those coordinates which are given by you are defined. For example:\n\u2019N10U3\u2019\n$ only the Y and Z coordinates are defined,\n$ while the X coordinate remains undefined\n\u2019N10U3\u2019\n$ only the Y and Z coordinates are defined,\n$ while the X coordinate remains undefined\nFor the EQ operator, all the pairs of defined coordinates should be equal. For NE, only one pair of defined coordinates need be different. For GT (LT,GE,LE), all the defined coordinates of the first position should be greater than (less than, greater than or equal to, less than or equal to) the defined coordinates of the second position. This means that GE is not the opposite of LT and LE is not the opposite of GT.\nIf no coordinate of the two positions are defined for a common axis (e.g. \u2019N10\u2019 and \u2019W4D7\u2019), the result of the comparison is undefined.\n\u2019POS EQ W1S2D3\u2019\n$ This evaluates to true only if POS of the current $ element is (-1,-2,-3).\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\n$ Only the second coordinate of POS is compared;\n$ if it is greater than 10, then the result is true.\n\u2019E10N10 GT E0N0\u2019\n$ Is true because the inequality is verified for the X\n$ and Y axis (both coordinates are undefined for\n$ the Z axis, so it is ignored).\n\u2019E10N0 GT E0N0\u2019\n$ Is false because the Y components are different $ axes.\n\u2019E10N0 GT E0U100\u2019\n$ Is true. Although no comparison can be\n$ performed n either the Y or the Z axis, because\n$ the components are not present in both position\n$ constants, the comparison is true in the X\n$ component.\n\u2019N10 EQ W4D7\u2019\n$ Is undefined (no comparison is possible).\n\u2019POS EQ W1S2D3\u2019\n$ This evaluates to true only if POS of the current $ element is (-1,-2,-3).\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\n\n$ Only the second coordinate of POS is compared;\n$ if it is greater than 10, then the result is true.\n\u2019E10N10 GT E0N0\u2019\n$ Is true because the inequality is verified for the X\n$ and Y axis (both coordinates are undefined for\n$ the Z axis, so it is ignored).\n\u2019E10N0 GT E0N0\u2019\n$ Is false because the Y components are different $ axes.\n\u2019E10N0 GT E0U100\u2019\n$ Is true. Although no comparison can be\n$ performed n either the Y or the Z axis, because\n$ the components are not present in both position\n$ constants, the comparison is true in the X\n$ component.\n\u2019N10 EQ W4D7\u2019\n$ Is undefined (no comparison is possible).\nRefer to Precision of Comparisons, for tolerances in comparing numbers.\n\u2019N10U3\u2019\n$ only the Y and Z coordinates are defined,\n$ while the X coordinate remains undefined\n\u2019POS EQ W1S2D3\u2019\n$ This evaluates to true only if POS of the current $ element is (-1,-2,-3).\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\n$ Only the second coordinate of POS is compared;\n$ if it is greater than 10, then the result is true.\n\u2019E10N10 GT E0N0\u2019\n$ Is true because the inequality is verified for the X\n$ and Y axis (both coordinates are undefined for\n$ the Z axis, so it is ignored).\n\u2019E10N0 GT E0N0\u2019\n$ Is false because the Y components are different $ axes.\n\u2019E10N0 GT E0U100\u2019\n$ Is true. Although no comparison can be\n$ performed n either the Y or the Z axis, because\n$ the components are not present in both position\n$ constants, the comparison is true in the X\n$ component.\n\u2019N10 EQ W4D7\u2019\n$ Is undefined (no comparison is possible).\n\n\n\nPrecision of Comparisons\n\u2019N10U3\u2019\n\u2019POS EQ W1S2D3\u2019\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\n\u2019E10N10 GT E0N0\u2019\n\u2019E10N0 GT E0N0\u2019\n\u2019E10N0 GT E0U100\u2019\n\u2019N10 EQ W4D7\u2019\nPrecision of Comparisons\n,"}
{"Headers": "POLAR keyword", "Content": "The POLAR keyword allows positions to be defined in terms of a distance in a particular direction from a point.\nIf FROM is not specified the default is the origin of the owner.\nPOLAR N 45 E DIST 20M FROM U 10 M\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V\nPOLAR N 45 E DIST 20M FROM U 10 M\n\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V\n\n\n\nPOLAR N 45 E DIST 20M FROM U 10 M\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V\nPOLAR dir DISTance expr -+- FROM -+- pos -----.\n                         |        |           |\n                         |        \u2018- point ---|\n                         |                    |\n                         \u2018--------------------+--->\n\n\n\nPOLAR dir DISTance expr -+- FROM -+- pos -----.\n                         |        |           |\n                         |        \u2018- point ---|\n                         |                    |\n                         \u2018--------------------+--->\nPOLAR N 45 E DIST 20M FROM U 10 M\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V"}
{"Headers": "Database Concepts", "Content": "This reference manual describes in detail the structure and methods of the internal databases used within AVEVA E3D Design. It is written for System Administrators who may be involved in maintaining projects, and the databases from which they are created.\n\n\n"}
{"Headers": "Project", "Content": "Information is provided on project organization, the definition of teams and multiple database and the splitting of data across multiple databases.\n\n\n"}
{"Headers": "Project Organization", "Content": "In order to create data, you must first create a Project.\nA Project consists of:\nA project starts with just the System, Comms and Misc DBs.\nYou will then have to create other DBs for users to work on. The various visible DB types are:\nSystem\nContains details on DBs, Multiple Databases (MDBs), teams etc in the project\nDictionary\nContains User Defined Attribute (UDA) and User Defined Element Type (UDET) definitions\nProperty\nContains units for different properties\nCatalog\nContains Catalog and specification information\nModel\nContains Plant design information\nDraw\nContains drawing information\nSPOOL\nContains spool information\nMaterials\nContains hull material information\nDiagrams\nContains Schematic information\nTransaction\nUsed by Global to record transactions\nSCHEMATIC\nContains PI&D (Schematic) information\nMANU\nContains detailed manufacturing data\nNSEQ\nStores name sequences\nSystem\nContains details on DBs, Multiple Databases (MDBs), teams etc in the project\nDictionary\nContains User Defined Attribute (UDA) and User Defined Element Type (UDET) definitions\nProperty\nContains units for different properties\nCatalog\nContains Catalog and specification information\nModel\nContains Plant design information\nDraw\nContains drawing information\nSPOOL\nContains spool information\nMaterials\nContains hull material information\nDiagrams\nContains Schematic information\nTransaction\nUsed by Global to record transactions\nSCHEMATIC\nContains PI&D (Schematic) information\nMANU\nContains detailed manufacturing data\nNSEQ\nStores name sequences\nTypically there will be many DBs of each type within a project.\nAn example of a simple project is as follows:\n\nDBs may be included from other projects.\nEach DB has a unique DB number. User DBs have numbers in the range 1-7000. The range 7000-8000 is reserved for AVEVA supplied databases. The range 8000-8192 is reserved for system databases.\nThe DB number is assigned to the DB on creation. You may specify the DB number. If not specified by you then the next available DB number is used.\nThere may never be two DBs with the same DB number in a single project. Thus to include a DB from another project, that DB number must be unused in the target project.\nSystem\nContains details on DBs, Multiple Databases (MDBs), teams etc in the project\nDictionary\nContains User Defined Attribute (UDA) and User Defined Element Type (UDET) definitions\nProperty\nContains units for different properties\nCatalog\nContains Catalog and specification information\nModel\nContains Plant design information\nDraw\nContains drawing information\nSPOOL\nContains spool information\nMaterials\nContains hull material information\nDiagrams\nContains Schematic information\nTransaction\nUsed by Global to record transactions\nSCHEMATIC\nContains PI&D (Schematic) information\nMANU\nContains detailed manufacturing data\nNSEQ\nStores name sequences\nOne each of System, Comms, and Misc Databases (DBs)\nMultiple Design, Catalog, Drawing, and Dictionary DBs\nVarious picture files\nOne each of System, Comms, and Misc Databases (DBs)\nOne each of System, Comms, and Misc Databases (DBs)\nMultiple Design, Catalog, Drawing, and Dictionary DBs\nMultiple Design, Catalog, Drawing, and Dictionary DBs\nVarious picture files\nVarious picture files\n\n\n\nSystem\nDictionary\nProperty\nCatalog\nSPOOL\nMaterials\nDiagrams\nTransaction"}
{"Headers": "Teams and MDBs", "Content": "For ease of working DBs are grouped into Teams and Multiple Databases (MDBs). A Database (DB) belongs to one team, but may be in many MDBs. You must specify the MDB to work on when entering AVEVA E3D Design.\nDetails of DBs, teams, and MDBs are stored in the system database.\nAn example is shown below.\n\nIt can be seen that DB /A is only in MDB /X, whereas DB /B is in both MDB /X and /Y.\nTeam access controls fundamental write access. Members of Team1 will always have write access to DBs /A and /B, and read access to the remainder. For members of Team2 it will be the opposite way around.\nIf a DB is included from another project then it is always read only regardless of team membership.\nThese concepts are discussed in detail in the Administrator User Guide.\n\n\n\nAdministrator User Guide\nAdministrator User Guide"}
{"Headers": "Splitting Data Across Multiple Databases", "Content": "Theoretically there need only be one Database (DB) of each DB type. The main reasons for there being more are:\nDBs are used as a fundamental means of access control. DBs are allocated to Teams, and only team members can modify a DB.\nWhilst the multiwrite facilities allow many writers per DB, it eases contention if the writers are not all accessing the same DB.\nThe easiest way to run a Global project is to have different DBs writable at different locations.\nThe granularity of propagation and distribution in Global is per DB\nIt allows different permutations of Multiple Databases (MDBs).\nIt allows specific DBs to be hidden from sub contractors\nInclusion in other projects is done on a DB basis.\nDBs are used as a fundamental means of access control. DBs are allocated to Teams, and only team members can modify a DB.\nDBs are used as a fundamental means of access control. DBs are allocated to Teams, and only team members can modify a DB.\nWhilst the multiwrite facilities allow many writers per DB, it eases contention if the writers are not all accessing the same DB.\nWhilst the multiwrite facilities allow many writers per DB, it eases contention if the writers are not all accessing the same DB.\nThe easiest way to run a Global project is to have different DBs writable at different locations.\nThe easiest way to run a Global project is to have different DBs writable at different locations.\nThe granularity of propagation and distribution in Global is per DB\nThe granularity of propagation and distribution in Global is per DB\nIt allows different permutations of Multiple Databases (MDBs).\nIt allows different permutations of Multiple Databases (MDBs).\nIt allows specific DBs to be hidden from sub contractors\nIt allows specific DBs to be hidden from sub contractors\nInclusion in other projects is done on a DB basis.\nInclusion in other projects is done on a DB basis.\n\n\n"}
{"Headers": "Database Elements", "Content": "All data in a Dabacon database is stored in elements. Every element has a type, for example BOX. The type of element determines the attributes available on the element.\nEach DB type allows a different set of element types.\nDatabase attributes are described in Database Attributes\nThe elements are organized in a primary hierarchy. This is described in Database hierarchy.\n\n\n\nBOX\nBOX"}
{"Headers": "Reference Number", "Content": "Every element has a reference number, which is assigned when the element is created, and is unique to that element within the project. The reference number comprises two 32 bit integers. This is displayed in the form:\nThe first integer encodes the database number. This can be queried on the command line using Q DBNUMBER.\nThe second integer is a sequence number, starting at 0, and incrementing each time an element is created.\nThus, for example, the element with a reference number of =8193/0 will be the WORLD element (since this is always created first) created in Database (DB) 1.\nThe reference number is never changed once an element has been created.\n\n\n"}
{"Headers": "Name", "Content": "In AVEVA E3D Design any element may be given a name. The name always starts with a '/'. At the user level, it is this name that is typically used to identify an element. Names may of course be changed, thus there is no guarantee that the element named '/FRED' today is the same as the element named '/FRED' yesterday.\nAn element need not have a name. For these elements AVEVA E3D Design creates a constructed name, consisting of the relative position in the hierarchy up to the first named element.\nfor example, BOX 2 OF SUBEQUIPMENT 1 OF /VESS1\nWhilst the constructed name can be used to identify elements, its use is even more volatile than named elements, since the order of an element in a member's list may change.\nYou can duplicate the name of an element in a Design (DESI), Production (MANU), Schematic (SCHE) or Engineering (ENGI) databases in the current MDB. For example an element can be named `/FRED\u00b4 in the DESI database and a different element can be named \u00b4/FRED\u00b4 in the MANU database.\nAVEVA E3D Design is case sensitive and AVEVA recommends you stick to UPPERCASE characters. If you create an element named /FRED and at some later time you try to find it by typing /fred or /FreD, it will not be found.\n\n\n"}
{"Headers": "Current Element", "Content": "At the user level there is a concept of current element.\nMost AVEVA E3D Design commands act on the current element. This is often referred to as the CE. There is an extensive set of commands to navigate around the database changing the CE.\n\n\n"}
{"Headers": "Change Element Types", "Content": "For most elements, the element type may never be changed after creation. For example, once created, an element of type SITE will always be of type SITE until deleted.\nThere are a few exceptions to this rule where it makes sense. For example, BENDs may be changed to ELBOs and vice versa.\n\n\n"}
{"Headers": "Primary Database Hierarchy", "Content": "Information is provided on the hierarchical data model, the user defined hierarchies, the element instances and the use case of primary hierarchy.\n\n\n"}
{"Headers": "Hierarchical Data Model", "Content": "Each database consists of a hierarchy of elements. The allowed hierarchy is defined in a Database Schema. The database schema is the 'meta data', i.e. it is data about data. Database Schemas cannot be modified by users. The Database Schema for each database type is listed in the data model reference manual. An example of part of the Database Schema for Model databases is shown below:\n\nThis schema shows which elements are allowed where. For example, a WORLD may own a SITE, or GROUPWORLD, whereas a SITE may own a ZONE, BOUNDARY, DRAWING or GROUND model.\nThe same element type may occur in more than one place in the schema. In the above example it can be seen that a BOUNDARY element may occur below a SITE or a ZONE.\nAll database schemas have a WORLD element at the root.\n\n\n"}
{"Headers": "User Defined Hierarchies", "Content": "The database schemas in AVEVA E3D Design are fixed by AVEVA.\nYou may, however, customize the allowed hierarchy using User Defined Element Types (UDETs).\nA UDET must be based on an existing system type. For example, you may define a UDET :PUMP which is based on an Equipment. By default, a UDET will have the same allowed members and allowed owners as a base type. This can be customised to be a subset of that allowed on the base type, for example, you might decide that SUBE are not allowed under a :PUMP even though they are allowed under an Equipment (EQUI).\nUDETs based on zones may own other UDETs based on zones. This allows very flexible data models to be built.\n\n\n"}
{"Headers": "Element Instances", "Content": "A new database (DB) starts with a single world element with name '/*'. Users will then create instances of other element types. For example, a system user might create an initial hierarchy of sites and zones in a Model DB, leaving it to other users to create the actual Plant items.\nAn element instance will always be created within the primary hierarchy. For example, a new ZONE element must be created under an existing SITE. It cannot be created as a 'freestanding' element outside the existing hierarchy.\nThe actual element hierarchy can be viewed with the AVEVA E3D Design explorer.\nAll element instances within a multiple Database (MDB) are accessible at all times.\n\n\n"}
{"Headers": "Where the Primary Hierarchy is Used", "Content": "The primary hierarchy is used as follows:\nIt is used to create the 'constructed' name for unnamed elements.\nWhen an element is deleted, all descendants in the primary hierarchy are deleted.\nThe COPY command will copy an element and all its primary descendants.\nClaiming elements relies on the primary hierarchy.\nCollections work on the primary hierarchy.\nMost commands assume that the action is to be performed on the given element and its descendants in its primary hierarchy, for example,. adding a ZONE to a 3D view will add everything below that ZONE.\nIn the Design Database (DB), world positions and orientations are concatenated according to the primary hierarchy.\nIt is used to create the 'constructed' name for unnamed elements.\nIt is used to create the 'constructed' name for unnamed elements.\nWhen an element is deleted, all descendants in the primary hierarchy are deleted.\nWhen an element is deleted, all descendants in the primary hierarchy are deleted.\nThe COPY command will copy an element and all its primary descendants.\nThe COPY command will copy an element and all its primary descendants.\nClaiming elements relies on the primary hierarchy.\nClaiming elements relies on the primary hierarchy.\nCollections work on the primary hierarchy.\nCollections work on the primary hierarchy.\nMost commands assume that the action is to be performed on the given element and its descendants in its primary hierarchy, for example,. adding a ZONE to a 3D view will add everything below that ZONE.\nMost commands assume that the action is to be performed on the given element and its descendants in its primary hierarchy, for example,. adding a ZONE to a 3D view will add everything below that ZONE.\nIn the Design Database (DB), world positions and orientations are concatenated according to the primary hierarchy.\nIn the Design Database (DB), world positions and orientations are concatenated according to the primary hierarchy.\n\n\n"}
{"Headers": "Secondary Hierarchies", "Content": "An element can only exist once in the primary data hierarchy. Secondary hierarchies, such as Group Sets (GPSETs), allow elements to appear more than once in the overall hierarchy. For example a PIPE will appear below a ZONE in the primary hierarchy. The same PIPE may also be added to a GPSET element. This is useful for collecting elements according to different criteria.\nThe diagram below shows a typical multi hierarchy where the secondary links are dotted.\n\nMost commands will work on secondary hierarchies. For example, if /GPSET1 is added to a 3D view then this is equivalent to adding both /VESS1 and /PUMP2 to the 3D view. However, there are exceptions to this. In particular deleting a GROUP will not delete the GROUP members; thus deleting /GPSET1 will not delete /VESS1 and /PUMP2.\nUnlike the Primary hierarchy, secondary hierarchies may span different databases (DBs).\n\n\n"}
{"Headers": "Database Attributes", "Content": "Every element may have a number of attributes. All elements have the following attributes:\nNAME\nthe element's name\nTYPE\nthe element's type\nLOCK\nif set, then the element may not be modified\nOWNER\nthe element's owner\nMEMBERS\nthe current members of the element\nNAME\nthe element's name\nTYPE\nthe element's type\nLOCK\nif set, then the element may not be modified\nOWNER\nthe element's owner\nMEMBERS\nthe current members of the element\nThe remaining attributes vary depending on the element type. The Database Schema defines which attributes are available on an element type. The allowed attributes for an element type may be ascertained using Programmable Macro Language (PML) objects and other command queries.\nAttributes may be one of the following types:\nRef\nRef Array\nPosition\nDirection\nOrientation\nAttribute\nElementType (or Noun)\nA 'Ref' type is a pointer to another element. For example, on a BRANCH element the Connection Reference (CREF) attribute points to the connected NOZZLE. The use of Ref attributes enables AVEVA E3D Design to model networks and other cross relationships.\nThe attribute type dictates how the attribute can be set with PML or specific syntax.\nNAME\nthe element's name\nTYPE\nthe element's type\nLOCK\nif set, then the element may not be modified\nOWNER\nthe element's owner\nMEMBERS\nthe current members of the element\nInteger\nRef\nInteger Array\nRef Array\nReal\nPosition\nReal Array\nDirection\nBool (or Logical)\nOrientation\nBool (or Logical) Array\nAttribute\nString (or Text)\nElementType (or Noun)\n\n\n\nNAME\nTYPE\nLOCK\nOWNER\nMEMBERS"}
{"Headers": "User Defined Attributes", "Content": "You can extend the allowed attributes for any element type, including a /ser Defined Element Type (UDET), by defining User Defined Attributes (UDAs). For example, you could define a UDA called :SUPPLIER of type string on all piping components. The newly defined UDA will then exist on all applicable elements, existing and new. If the definition of a UDA is changed then this will also apply to all existing instances.\nHaving defined a UDA, it is accessed in the same way as any other attribute.\n\n\n"}
{"Headers": "Pseudo Attributes", "Content": "In addition to the attributes stored on the database, there are a large number of pseudo attributes. The value of pseudo attributes is calculated at the time of making the query.\nFor example, the CUTLENGTH attribute on SCTN elements is a pseudo attribute calculated at the point of doing the query.\nThere is a lot of functionality presented via pseudo attributes. Currently there are over 1200 pseudo attributes.\nSince the value of a pseudo attribute is calculated from other attributes, it is not generally possible to set their value directly.\n\n\n"}
{"Headers": "Global Namespace for Attribute and Element Type Names", "Content": "Attributes and element types have a global name space. This means that an attribute such as XLEN will have an identical meaning wherever it exists.\nSimilarly if an element type is valid in more than one database type, the definition of the element type will be identical in each.\n\n\n"}
{"Headers": "Attributes of Physical Quantities", "Content": "Some real attributes are simply numbers, counts, quantities etc. Others represent real physical quantities such as distances, areas, densities, angles etc. The type of physical quantity is called its physical dimension, often shortened in unambiguous contexts to its dimension. Real attributes (stored, derived, user defined etc.) can all be assigned a physical dimension and this determines the type of data stored in these attributes wherever and whenever they occur in the database. The most common dimensions of attributes are of length (internally set to either DIST or BORE). There are many others supported including density, mass, pressure, temperature, area, volume and angle.\nThe dimension of an attribute is held in the database in its (ambiguously named) UNIT field. It may be queried directly using the VAR ATTDEF attributeName UNIT syntax, and the !attribute.units() PML ATTRIBUTE object method, refer to PML ElementType Class.\n\n\n\nPML ElementType Class\nPML ElementType Class"}
{"Headers": "Database Expressions and Rules", "Content": "Information is provided on database expressions and rules to define a database.\n\n\n"}
{"Headers": "Expressions", "Content": "Database expressions can be of the following types:\nThe contents of an expression may contain the standard operator and mathematical functions along with the names of attributes and element identification.\nThis expression simply multiplies the three attributes XLEN, YLEN, ZLEN together and then multiplies by two.\nThe attributes refer to the current element. If attributes of other elements are required then the OF syntax is used.\nThe 'OF' keyword makes sure that the AREA attribute is obtained from the owner of the current element rather than the current element itself.\nThe main uses of expressions are:\nDatabase expressions are very similar to Programmable Macro Language (PML) expressions. The major difference is that database expressions may not contain other PML variables or functions. For example, (XLEN * !MYVAR) is not a valid database expression.\n(XLEN * YLEN * ZLEN * 2)\n(PURP EQ 'HS' AND AREA OF OWNER EQ 1)\nalgebraic\nboolean (or logical)\ntext\nElement ID\nposition\ndirection\norientation\nalgebraic\nalgebraic\nboolean (or logical)\nboolean (or logical)\ntext\ntext\nElement ID\nElement ID\nposition\nposition\ndirection\ndirection\norientation\norientation\nCatalog parameterization\nTemplate parameterization\nRules\nDrafting line styles\nUser level collections and report\nCatalog parameterization\nCatalog parameterization\nTemplate parameterization\nTemplate parameterization\nRules\nRules\nDrafting line styles\nDrafting line styles\nUser level collections and report\nUser level collections and report\n\n\n"}
{"Headers": "Rules", "Content": "An attribute may be defined as a rule. For example, the attribute XLEN may be defined as a rule by the expression (YLEN * 2).\nThe OF syntax is often used in Rule expressions to refer to other elements, for example, (YLEN OF /FRED * 2)\nThe result of the rule is stored against the attribute as for other attributes.\nThere are commands to recalculate the rule.\nRules may be either static or dynamic. If static, then the rule result will only be recalculated on demand. If dynamic, then the result will be recalculated every time an attribute within the expression changes, for example, for the above rule, if YLEN is modified, then XLEN will be recalculated automatically. The dynamic linkage of rules may be across elements and across Databases (DBs).\n\n\n"}
{"Headers": "Dumping out the Database", "Content": "Information is provided on the possibilities to dump out the database using data listings and the Reconfigurer.\n\n\n"}
{"Headers": "Data Listings", "Content": "Data listings (DATALs) capture the state of the database in the form of AVEVA E3D Design commands. All element data including all attributes, User Defined Attributes (UDAs) and rules will be captured. They are similar in concept to Extensible Markup Language (XML) output. These files can then be read back in via the command line.\nData listings are used as follows:\nLong term archiving\nCopying parts of a Database (DB) between projects\nFor general information.\nLong term archiving\nLong term archiving\nCopying parts of a Database (DB) between projects\nCopying parts of a Database (DB) between projects\nFor general information.\nFor general information.\n\n\n"}
{"Headers": "Reconfigurer", "Content": "Reconfigurer is similar to Data Listing (DATAL) in that it dumps out the state of the data.\nThe data can be dumped to either binary or text file. Using binary files is quickest.\nReconfigurer is faster than DATAL and is recommended if whole DBs or world level elements are to be transferred. DATAL or the copy facilities is recommended if lower level elements are to be transferred.\n\n\n"}
{"Headers": "Database Modifications", "Content": "The fundamental modifications allowed are:\nElement creation\nElement deletion\nElement copy\nElement move\nAttribute modification\nElement creation\nElement creation\nElement deletion\nElement deletion\nElement copy\nElement copy\nElement move\nElement move\nAttribute modification\nAttribute modification\n\n\n"}
{"Headers": "Data Access Control (DACs)", "Content": "Data Access Control (DAC) is the mechanism that protects information handled by the system from accidental or unauthorised manipulation.\nThe basic access control available is known as 'Team Owning Databases'. It implements access control on database level by simply giving the members of the team owning the database full access and others read-only to data held in particular databases.\nA more sophisticated access control is implemented in the form of Access Control Rights (ACRs). ACR allows the administrator of the system to apply a more fine grained access control over the model. The following figure illustrates the DAC database hierarchy.\n\nAn ACR is defined through two entities:\nA PEROP defines the access rights given for a number of pre-defined operations for one or more elements.\nOne or more ACRs may be assigned to a user granting and denying access to the model.\nFor a user to gain update access to a particular element two rules apply:\nManagement tools are available for DAC through the Admin module. Control of DAC is also available through Programmable Macro Language (PML).\nA PEROP consists of three parts:\nThe PEROP may further restrict the elements it applies to by a qualifying condition. The qualifying conditions is an AVEVA E3D Design statement that should evaluate to true to qualify the PEROP.\nThe following operations are available through PEROPs\nEach of these operations may be set to\nAllow\nThe operation is permitted\nDisallow\nThe operation is not permitted\nIgnore\nThe PEROP does not define whether this operation is permitted or not\nAllow\nThe operation is permitted\nDisallow\nThe operation is not permitted\nIgnore\nThe PEROP does not define whether this operation is permitted or not\nOptionally the PEROP may further restrict which attributes it allows modification to by specifying a list of attributes that it either includes or excludes from allowing modification to.\nThe PEROP also holds the message that the system will issue if the PEROP denies attempted operation.\nAllow\nThe operation is permitted\nDisallow\nThe operation is not permitted\nIgnore\nThe PEROP does not define whether this operation is permitted or not\nA ROLE, which is a collection of rules called Permissible Operations (PEROPs).\nA SCOPE, which defines to what part of the model the ROLE applies. The SCOPE may be an expression, for example, all ZONE WHERE (FUNC eq 'TEAMA')\nA ROLE, which is a collection of rules called Permissible Operations (PEROPs).\nA ROLE, which is a collection of rules called Permissible Operations (PEROPs).\nA SCOPE, which defines to what part of the model the ROLE applies. The SCOPE may be an expression, for example, all ZONE WHERE (FUNC eq 'TEAMA')\nA SCOPE, which defines to what part of the model the ROLE applies. The SCOPE may be an expression, for example, all ZONE WHERE (FUNC eq 'TEAMA')\nAt least one PEROP in a ROLE assigned to a USER must grant the update operation.\nNo one PEROP must explicitly deny the operation.\nAt least one PEROP in a ROLE assigned to a USER must grant the update operation.\nAt least one PEROP in a ROLE assigned to a USER must grant the update operation.\nNo one PEROP must explicitly deny the operation.\nNo one PEROP must explicitly deny the operation.\nThe Element it applies to\nThe operations which can be performed on those elements\nOptionally the Attributes that may be modified.\nThe Element it applies to\nThe Element it applies to\nThe operations which can be performed on those elements\nThe operations which can be performed on those elements\nOptionally the Attributes that may be modified.\nOptionally the Attributes that may be modified.\nCreate\nModify\nDelete\nClaim\nIssue\nDrop\nOutput\nExport\nCopy\nCreate\nCreate\nModify\nModify\nDelete\nDelete\nClaim\nClaim\nIssue\nIssue\nDrop\nDrop\nOutput\nOutput\nExport\nExport\nCopy\nCopy\n\n\n\nAllow\nDisallow\nIgnore"}
{"Headers": "Errors Applicable to all Modifications", "Content": "The following checks are applied to all modifications:\nThe claiming process is described in Claiming Elements.\nCheck access control\nCheck that the DB is open in write\nCheck that the element's LOCK flag is false\nIf a multiwrite Database (DB) then do a claim check, and claim if needed\nCheck access control\nCheck access control\nCheck that the DB is open in write\nCheck that the DB is open in write\nCheck that the element's LOCK flag is false\nCheck that the element's LOCK flag is false\nIf a multiwrite Database (DB) then do a claim check, and claim if needed\nIf a multiwrite Database (DB) then do a claim check, and claim if needed\n\n\n"}
{"Headers": "Integrity of Modifications", "Content": "The engineering integrity is always maintained for any database modification.\nThe integrity checks are applied below the database interface. Thus modifying the database is always safe whether done via PML commands or C#.\nThe checks are applied to individual attributes and element types. For example the OBST attribute can only ever be set to 0,1 or 2. AVEVA E3D Design will always check that this is the case prior to allowing the modification.\n\n\n"}
{"Headers": "Element Creation", "Content": "Elements may be created. They are always created one at a time, and may only be created at a legitimate point in the primary hierarchy.\nOn creation, a unique reference number will be assigned. The method by which the default reference number is generated is described in User Defined Hierarchies.\nIt is possible to create an element with a specified reference number, provided it is unused and valid for the Database (DB). This functionality is provided for certain specialized situations (such as recreating an exact copy of a DB, so that all references to elements from other DBs remain valid), and is not recommended for general use.\nThe attributes will be set to their default values. In some cases the default attribute values are cascaded down from the owning element.\n\n\n\nUser Defined Hierarchies\nUser Defined Hierarchies"}
{"Headers": "Element Deletion", "Content": "Elements may be deleted. All elements below the deleted element in the primary hierarchy will also be deleted.\nReference numbers of deleted elements are never reused.\n\n\n"}
{"Headers": "Element Copy", "Content": "Elements may be copied. There are options to copy a single element or an element and all its descendants. Elements may be copied between Databases (DBs). Any cross references entirely within the copied structure will be updated to point to the newly created elements.\nElements are always copied on top of an existing element of the same type.\nThere are various options on the copy command to allow:\nAdditional potential errors at create are:\nThe copied elements to be renamed according to a given criteria\nWhether any attribute rules are to be rerun on the copied element. (Rules are described in Reconfigurer)\nThe copied elements to be renamed according to a given criteria\nThe copied elements to be renamed according to a given criteria\nWhether any attribute rules are to be rerun on the copied element. (Rules are described in Reconfigurer)\nWhether any attribute rules are to be rerun on the copied element. (Rules are described in Reconfigurer)\nThe element may not be copied to an element of a different type\nThe element may not be copied to an element of a different type\nThe element may not be copied to an element of a different type\n\n\n\nReconfigurer\nReconfigurer"}
{"Headers": "Element Move", "Content": "Elements may be moved to a different point in the Database (DB) or to a different DB.\nThe Element and all its descendants will be moved.\nIf the element is moved to a different DB, then its reference number is changed. All reference attributes pointing to the moved structure will be updated.\nAdditional potential errors at move are:\nThe element is not allowed in the members list of the new owner\nThe element is not allowed in the members list of the new owner\nThe element is not allowed in the members list of the new owner\n\n\n"}
{"Headers": "Attribute Modification", "Content": "The following checks are applied when modifying attributes:\nSometimes modifying one attribute will actually cause a number of attributes to change. There are two main cases where this might happen:\nThe integrity of cross referenced attributes is maintained when one end of the connection is changed. Changing one end of a connection will also change the following:\nIn essence, changing one value may result in four elements being updated.\nFor example, consider the following:\n\nAfter setting the CREF on /N1 to /B1, the end result is:\n\n\n\n"}
{"Headers": "Effect of Modifications on Dynamic Rules", "Content": "A dynamic rule will automatically respond to changes which affect the attributes referred to in the rule.\nFor example, we set a rule on YLEN of /MYBOX to be (YLEN OF /FRED * 2). Thus if YLEN on /FRED changes then YLEN on /MYBOX will be updated automatically. However there are reasons why the automatic propagation of dynamic rules may fail, as follows:\nNote also that only static rules are not automatically updated. For these reasons there are commands to verify that rule results are up to date.\n\n\n"}
{"Headers": "Database Sessions", "Content": "Information is provided on the handling of a session, for example, defining a session by saving or getting the work, creating a stamp, displaying the session history, setting a comparison date and merging changes.\n\n\n"}
{"Headers": "Savework/Getwork", "Content": "Data is only saved to the database on demand. Similarly you will only see changes made by others on demand. In order to make changes visible to other users two steps must occur:\nFor most applications, the save-work/get-work actions are totally in the hands of the user.\n\n\n\nSave work\nGet work"}
{"Headers": "Sessions", "Content": "When a savework is made a new session will be created on the database. The changed data will always be written to the end of the file. This represents the 'delta' from the previous session. Details such as date, user, session description are stored as part of the session data. There is always a pointer from the database header to the last session on the database.\n\nInternally there is a linked list between sessions. It is worth reiterating that once a session is written, it will never be changed. Thus if a user is looking at session 19, then his view of the data will never change in any way regardless of any sessions created by other users. If you do want to see the changes made by others then you must do a 'Getwork'. 'Getwork' will always reposition you to view the latest session. Thus in the above example if a user originally looking at session 19 did a Getwork then he would now be looking at session 39.\n\n\n"}
{"Headers": "Session History", "Content": "The Database will preserve the full session history. Thus at any point it is possible to find out what was changed when and by whom. The system can report on changes down to the attribute level.\nThe list of facilities include:\nThe DIFF command can be used to report on changes. For example, if you were to modify a couple of attributes on an equipment, and add a new primitive, then the DIFF command could be used to report on the changes. The output from the command might be:\nBy default, the DIFF command will report the changes made by you in the current working session, that is to say, since the last savework. It is also possible to specify a given session number, a date and time, or a stamp (refer to Create a Stamp) in order to see the differences since then.\nThe OUTPUT command may be used to record changes since a given session. The Data Listing (DATAL) file will then contain the commands that reproduce the updates made since the given session. The file can then be read back in to reproduce the changes. This is convenient where bits of data have been copied between projects, and the copied data needs to be updated with changes made to the original.\nReverse changes can also be output. The DATAL file will then contain the commands that remove the updates made since the given session. This is a convenient way for restoring part of a model back to how it was at an earlier point.\n /VESS1\n/VESS1 [=15752/201] has been modified\nList member /EXTRACYL created\nComparing elements to an old session\nDataling out changes since a given session\nSetting a comparison session\nCreating a stamp\nVarious pseudo attributes\nComparing elements to an old session\nComparing elements to an old session\nDataling out changes since a given session\nDataling out changes since a given session\nSetting a comparison session\nSetting a comparison session\nCreating a stamp\nCreating a stamp\nVarious pseudo attributes\nVarious pseudo attributes\nLocal comparison for Database items\n /VESS1\n/VESS1 [=15752/201] has been modified\nMember list has changed\nList member /EXTRACYL created\nDescription has changed\nOld value= my description\nNew value= my new description\nArea has changed\nOld value= 999\nNew value= 100\n/EXTRACYL [=15752/1326] has been created\n2 changed elements found\nLocal comparison for Database items\n /VESS1\n/VESS1 [=15752/201] has been modified\nLocal comparison for Database items\nMember list has changed\nList member /EXTRACYL created\nMember list has changed\nDescription has changed\nOld value= my description\nNew value= my new description\nDescription has changed\nArea has changed\nOld value= 999\nNew value= 100\nArea has changed\n/EXTRACYL [=15752/1326] has been created\n2 changed elements found\n/EXTRACYL [=15752/1326] has been created\n\n\n\nCreate a Stamp\nCreate a Stamp"}
{"Headers": "Create a Stamp", "Content": "It is often convenient to mark a set of Databases (DBs) at particular milestones in the project. The 'Stamp' functionality allows this. It is then straight forward to find out what has changed since the stamp, or to view the data as it was at that time.\nStamps can only be created within Admin.\n\n\n"}
{"Headers": "Set a Comparison Date", "Content": "Within AVEVA E3D Design a comparison date can be set. A convenient way of doing this is to use a stamp. However the comparison date may also be set to an explicit session on a particular extract. If the comparison session is on a different extract then the extract must be an ascendant of the current extract.\nAny query may then be done at the old session using the 'OLD' keyword. for example:\nThis would return the value of XLEN at the comparison session.\nThere are a number of pseudo attributes that can be used to do comparisons. These are listed in the database reference manual.\nQ OLD XLEN\n\n\n"}
{"Headers": "Merge Changes", "Content": "As a result of storing all changes, AVEVA E3D Design databases will grow relatively quickly. You may compress a Database (DB) to reduce its size by merging multiple sessions together using the MERGE CHANGES command in Admin. You may compress all sessions, or a range of sessions.\nAny sessions used in stamps will always be preserved. Thus before compressing a DB you should create stamps to preserve any comparison points that might be needed. Sessions 1,2 and the last session are also always preserved. Thus for the previous example, if you decide to do a MERGE CHANGES on a database having set a stamp on session 10, the resultant DB will look like:\n\nIt can be seen that as well as sessions 10, sessions 1,2 and 39 are kept. The changes in session 10 now hold the accumulated changes for sessions 3-10, and Session 39 actually holds the accumulated changes for sessions 11 to 39.\nThe MERGE CHANGES command is discussed in the ADMIN manual.\n\n\n\nMERGE CHANGES"}
{"Headers": "Multiwrite Working", "Content": "Database Constructor (Dabacon) DBs may be either 'UPDATE' or 'MULTIWRITE.\nUPDATE DBs allow only one user to have write access at any given time, although multiple users may still have simultaneous read access.\nMULTIWRITE DBs allow multiple simultaneous users with write and read access.\n\n\n"}
{"Headers": "Multiwrite Strategy", "Content": "The Database employs two techniques to allow multiple writers.\nA claiming mechanism - User must claim an element at the point of making a modification. This will lock the element preventing other users making modifications.\nA Last Back Wins strategy- For some changes a 'last back win' strategy is used rather than claim locks. With this strategy two users may change the same element. Any changes are merged back in. The merging is done at the attribute level. If two users change the same attribute then the last save wins. Places where this strategy is used are:\nSome connection attributes. for example, changing a TREF attribute on a branch does not require the BRANCH to be claimed.\nMember lists containing primary elements are always merged back. For example, creating a ZONE below a SITE doe NOT require the SITE to be claimed,\nChanges issued from variant extracts are always merged back in.\nDynamic rule linkage\nSpatial map values\nSome connection attributes. for example, changing a TREF attribute on a branch does not require the BRANCH to be claimed.\nSome connection attributes. for example, changing a TREF attribute on a branch does not require the BRANCH to be claimed.\nMember lists containing primary elements are always merged back. For example, creating a ZONE below a SITE doe NOT require the SITE to be claimed,\nMember lists containing primary elements are always merged back. For example, creating a ZONE below a SITE doe NOT require the SITE to be claimed,\nChanges issued from variant extracts are always merged back in.\nChanges issued from variant extracts are always merged back in.\nDynamic rule linkage\nDynamic rule linkage\nSpatial map values\nSpatial map values\n\n\n"}
{"Headers": "Claim Elements", "Content": "The level of claiming is at the 'primary' element level. Examples of primary element types are SITE, ZONE, EQUI, SUBE. Examples of non primary elements are primitives such as BOX. When you need to modify a non primary element then the first primary element up the hierarchy must be claimed out. For example, to modify a BOX, then the owning EQUI or SUBE must be claimed.\nWhen working on multiwrite Databases (DBs), users may either explicitly claim elements to work on, or let the system implicitly claim elements for them. The implicit claim will occur at the point of making a modification.\nThere are a number of reasons why an element may not be claimed:\nIf a list of elements is claimed, and some in the list fail, then the remaining elements will still be claimed.\n\n\n"}
{"Headers": "Release Elements", "Content": "Having claimed an element, a user may release it, thus allowing others to change it.\nAn element may not be released if changes are outstanding. You must do a SAVEWORK first.\nOn leaving a module all elements will be released for that user.\nIf a list of elements is released, and some in the list fail, then the remaining elements will still be released.\n\n\n"}
{"Headers": "Performance Considerations", "Content": "Every time a claim/release is made the underlying Database (DB) is accessed. To minimize such access, as many elements as possible should be done in one go.\n\n\n"}
{"Headers": "Potential Conflicts at SAVEWORK/GETWORK in a Multiwrite Environment", "Content": "There are a number of potential problems which are not discovered until SAVEWORK or GETWORK.\nIf any error occurs at SAVEWORK or GETWORK then the entire operation is aborted.\n\n\n"}
{"Headers": "Extracts", "Content": "Extracts are an extension of the multiwrite facilities.\nThe extra functionality offered by extracts is:\nThey allow long term claims, that means, elements are not released on module switch.\nThe issuing of data is separated from SAVEWORK.\nA partial set of changes may be issued, rather than the whole lot.\nA partial set of changes may be dropped, hence losing the changes.\nAllows variants to be tried and maintained.\nAllows a 'last back wins' when issuing from variants\nUsers may have their own private work space.\nUsers can use extracts to implement an approval/work cycle, so that. the issuing of data from one extract to another could correspond to given criteria being met. Other users could then read the approved data rather than the working data.\nThey allow long term claims, that means, elements are not released on module switch.\nThey allow long term claims, that means, elements are not released on module switch.\nThe issuing of data is separated from SAVEWORK.\nThe issuing of data is separated from SAVEWORK.\nA partial set of changes may be issued, rather than the whole lot.\nA partial set of changes may be issued, rather than the whole lot.\nA partial set of changes may be dropped, hence losing the changes.\nA partial set of changes may be dropped, hence losing the changes.\nAllows variants to be tried and maintained.\nAllows variants to be tried and maintained.\nAllows a 'last back wins' when issuing from variants\nAllows a 'last back wins' when issuing from variants\nUsers may have their own private work space.\nUsers may have their own private work space.\nUsers can use extracts to implement an approval/work cycle, so that. the issuing of data from one extract to another could correspond to given criteria being met. Other users could then read the approved data rather than the working data.\nUsers can use extracts to implement an approval/work cycle, so that. the issuing of data from one extract to another could correspond to given criteria being met. Other users could then read the approved data rather than the working data.\n\n\n"}
{"Headers": "Create Extracts", "Content": "Extracts are created from existing multiwrite Databases (DBs). The existing DB then becomes the Master DB. Many extracts may be created off the same Master DBs. Extracts may also be created from other extracts. The term extract family is used to refer to all extracts created directly or indirectly off a Master DB. Example of an extract family:\n\nIn this extract family, three extracts were created below the Master DB. Two further extracts were then created below Extract1.\nThere may be up to 8000 extracts in an extract family.\nExtracts may be included in an Multiple Database (MDB) as for any other DB. Two extracts from the same extract family cannot be included in the same MDB.\n\n\n"}
{"Headers": "Restrictions on Extracts", "Content": "It is not be possible to:\nCOPY an extract\nINCLUDE an extract from a foreign project without its parent extract being included first.\nEXCLUDE an extract/DB unless all child extracts have been excluded.\nCOPY an extract\nCOPY an extract\nINCLUDE an extract from a foreign project without its parent extract being included first.\nINCLUDE an extract from a foreign project without its parent extract being included first.\nEXCLUDE an extract/DB unless all child extracts have been excluded.\nEXCLUDE an extract/DB unless all child extracts have been excluded.\n\n\n"}
{"Headers": "Extract Sessions", "Content": "An extract will have its own set of sessions. This is illustrated below:\n\nIn this example the extract Database (DB) was created when the Master DB had 19 sessions. The extract thus represents a branching of the model from session 19. Changes were then made to the Master and to the Extract. The Extract has had nine more sessions created (sessions 2-10). The Master has had 20 more sessions added (sessions 20 - 39).\nChanges made to an extract can be flushed back to the Master DB. Similarly the extract may be refreshed with changes made to the Master.\n\n\n"}
{"Headers": "MERGE CHANGES on Extracts", "Content": "When a 'MERGE CHANGE' operation is performed on a DB with extracts, all the lower extracts have to be changed to take account of this. Thus doing a 'MERGE CHANGE' on a DB with extracts should not be undertaken lightly. The opposite is not needed, i.e. MERGE CHANGES on a child does not require the parent extract to be merged.\nThe following restrictions apply to MERGE CHANGES:\nTo minimize the sessions preserved in (1) it is suggested that a bottom up approach is followed when doing 'MERGE CHANGES'.\n\n\n"}
{"Headers": "Extract Claims/Releases", "Content": "In order to modify an element in an extract, the element must be claimed to the extract. The principals of extract claiming are exactly the same as standard claiming, i.e, the granularity of extract claims is at the level of primary elements.\nExtract claims will work up through the extract levels, extract claiming as necessary, i.e, you need not do a separate claim for each level of extract.\nFor example, consider a three level extract as follows:\n\nIf a user does an extract claim to the Working Extract the following logic will be used:\nIs element claimed out to WORKING already?\n-if YES\ndo nothing\n-if NO\nIs element claimed to APPROVED extract?\n-if NO\nClaim from ASBUILT to APPROVED\nThen claim from APPROVED to WORKING\n-if YES-\nClaim from APPROVED to WORKING\nIs element claimed out to WORKING already?\n\n-if YES\n\n\n\ndo nothing\n\n-if NO\n\n\n\nIs element claimed to APPROVED extract?\n\n-if NO\n\n\nClaim from ASBUILT to APPROVED\n\n\nThen claim from APPROVED to WORKING\n\n-if YES-\n\n\nClaim from APPROVED to WORKING\nThe extract claim may fail for the same reasons that a user claim may fail, i.e.:\nUnlike user claims, extract claims stay with the extract across SAVEWORKs.\nIf a list of elements is extract claimed, and some in the list fail, then the remaining elements will still be extract claimed.\nIs element claimed out to WORKING already?\n-if YES\ndo nothing\n-if NO\nIs element claimed to APPROVED extract?\n-if NO\nClaim from ASBUILT to APPROVED\nThen claim from APPROVED to WORKING\n-if YES-\nClaim from APPROVED to WORKING\nAnother user/extract has the item claimed\nThe element is modified in a later version, hence a refresh is needed first.\nAnother user/extract has the item claimed\nAnother user/extract has the item claimed\nThe element is modified in a later version, hence a refresh is needed first.\nThe element is modified in a later version, hence a refresh is needed first.\n\n\n"}
{"Headers": "Extract Release", "Content": "Extract claims may be released in the same way as user claims.\nAn extract release will not be permitted if:\nIf a list of elements is extract released, and some in the list fail, then the remaining elements will still be extract released.\n\n\n"}
{"Headers": "User Claims/Releases on an Extract", "Content": "An extract is itself a multiuser Database (DB), thus more than one user may work on an extract. Standard user claims and releases are thus also applicable to extracts\n\n\n"}
{"Headers": "Variants", "Content": "Variants are like standard extracts except that there is no extract claiming of elements between the variant and its parent extract. Any elements may thus be modified. This has the advantage that many users can potentially change the same element at the same time in a different variant. The disadvantage is that conflicts are not discovered until the time of flush.\nThere are no restrictions on where variants are located in the extract tree, for example, variants may own other normal extracts or other variant extracts. If a variants owns standard extracts, then the variant acts as a root for subsequent extract claims.\n\n\n"}
{"Headers": "Extract Operations", "Content": "The following operations are allowed:\nDrop\nThis is the process of losing modifications done locally on an extract combined with the transfer of write extract back to the parent extract.\nPartial Drop\nThis is the process of losing modifications done locally on a subset of elements, combined with the transfer of write extract back to the parent extract.\nIssue\nThe local changes are copied to the parent extract, and the elements are released.\nFlush\nThis term is used for issuing without doing a release.\nPartial Issue\nThe Issuing of a subset of the modifications made in the current extract to the parent extract.\nRefresh\nThe mechanism by which an extract is updated with changes made in the parent Database (DB).\nDrop\nThis is the process of losing modifications done locally on an extract combined with the transfer of write extract back to the parent extract.\nPartial Drop\nThis is the process of losing modifications done locally on a subset of elements, combined with the transfer of write extract back to the parent extract.\nIssue\nThe local changes are copied to the parent extract, and the elements are released.\nFlush\nThis term is used for issuing without doing a release.\nPartial Issue\nThe Issuing of a subset of the modifications made in the current extract to the parent extract.\nRefresh\nThe mechanism by which an extract is updated with changes made in the parent Database (DB).\nThe refresh functionality is needed since users work on a constant view of the parent extract DB. Thus they will not see other users' issues until they do a REFRESH. It is akin to the GETWORK functionality in a single multiwrite DB.\nAll flushing, issuing, releasing and dropping operations work on one level of extract only. A Refresh can be done all the way up the tree using just one command.\nIf an extract operation fails, then the entire operation is aborted.\nDrop\nThis is the process of losing modifications done locally on an extract combined with the transfer of write extract back to the parent extract.\nPartial Drop\nThis is the process of losing modifications done locally on a subset of elements, combined with the transfer of write extract back to the parent extract.\nIssue\nThe local changes are copied to the parent extract, and the elements are released.\nFlush\nThis term is used for issuing without doing a release.\nPartial Issue\nThe Issuing of a subset of the modifications made in the current extract to the parent extract.\nRefresh\nThe mechanism by which an extract is updated with changes made in the parent Database (DB).\n\n\n\nDrop\nPartial Drop\nIssue\nFlush\nPartial Issue\nRefresh"}
{"Headers": "Merge Algorithm", "Content": "On issue or flush, changes made in an extract will be merged back to the parent extract.\nThe basic approach is that any changes made to the extract are applied to the parent extract, as shown below:\n\nThe granularity of this merge is at the attribute level, which means, two users can change different attributes on the same element and merge their changes together. If they modify the same attribute then a 'last back win' strategy is used.\nAVEVA E3D Design makes sure that all merges are valid at the raw database level, so that, the data will be Database Integrity Checker (DICE) clean. However it is not possible to make sure that the data is consistent in engineering terms. Thus it is highly recommended that when variant data is flushed back, Data Consistency Checking Utility (DATACON) checks and Clasher checks are run on the resulting version.\nThe definition of the different sessions for issue and flush are:\nSession on parent when Refresh was last done\nFrom session on child extract\nNew session on parent\nThe definition of the different sessions for refresh are:\nSession on parent when Refresh was last done\nFrom session on child extract\nNew session on parent\nThe definition of the different sessions for drop are:\nSession on parent when Refresh was last done\nFrom session on child extract\nNew session on child\nThe drop command compares the elements that are NOT to be dropped and applies the changes to create a new session.\nThe same algorithm is used for SAVEWORK and GETWORK.\nThere are two exceptions to the merge criteria as follows:\nBase Session\nSession on parent when Refresh was last done\nFrom Session\nFrom session on child extract\nTo Session\nNew session on parent\nBase Session\nSession on parent when Refresh was last done\nFrom Session\nFrom session on child extract\nTo Session\nNew session on parent\nBase Session\nSession on parent when Refresh was last done\nFrom Session\nFrom session on child extract\nTo Session\nNew session on child\nNote:\nThe standard flush and issue commands also do a refresh. This makes sure that there is a suitable base session for the next extract operation.\n\n\n\nBase Session\nFrom Session\nTo Session\nBase Session\nFrom Session\nTo Session\nBase Session\nFrom Session\nTo Session\nNote\n:"}
{"Headers": "Dealing with Deleted Elements", "Content": "There are three ways of denoting deleted items for a partial operation.\n\n\n"}
{"Headers": "Flushing Connected Items", "Content": "For two way connections, it is often desirable to flush both ends of the connection in order to preserve engineering consistency. There are addition options that allow the connected items to be flushed.\n\n\n"}
{"Headers": "Errors for Extract Operations", "Content": "Potential problems at issue and refresh are the same as for SAVEWORK and GETWORK on multiwrite DBs, i.e. there could be a name clash, or an owning element could be deleted. Such problems will need to resolved in the extract prior to issuing being allowed.\nIf doing a partial issue or flush or if issuing from an extract, then extra checks are applied as follows:\nWhere an element has not been claimed, then Drop can still be used to lose the local changes.\nWhere a non primary element has changed owner, then the old primary owner and the new primary owner must both be issued back at the same time.\nIf an element has been unnamed, and the name reused, then both elements must be flushed back together.\nIf an element and its owner have been created then:\n1. if it is included in a partial flushback, then so must its owner.\nif the owner is include in a partial drop, then so must the element itself\nif an element and its owner have been deleted then:\n1. if it is included in a partial drop, then so must it's owner.\nif the owner is included in a partial flush, then so must it.\nWhere a non primary element has changed owner, then the old primary owner and the new primary owner must both be issued back at the same time.\nWhere a non primary element has changed owner, then the old primary owner and the new primary owner must both be issued back at the same time.\nIf an element has been unnamed, and the name reused, then both elements must be flushed back together.\nIf an element has been unnamed, and the name reused, then both elements must be flushed back together.\nIf an element and its owner have been created then:\nIf an element and its owner have been created then:\n1. if it is included in a partial flushback, then so must its owner.\nif the owner is include in a partial drop, then so must the element itself\n1. if it is included in a partial flushback, then so must its owner.\nif an element and its owner have been deleted then:\nif an element and its owner have been deleted then:\n1. if it is included in a partial drop, then so must it's owner.\nif the owner is included in a partial flush, then so must it.\n1. if it is included in a partial drop, then so must it's owner.\nNote:\nWhen a partial issue or drop is made there is no guarantee that the data is 'Engineering correct'. Users are advised to run Clasher and/or Datacon on the resultant version.\n\n\n\nNote\n:"}
{"Headers": "Performance Considerations", "Content": "A new session is created for every flush operation. Thus it is much better to flush a large number of elements in one go rather than flush them individually.\n\n\n"}
{"Headers": "Global Working", "Content": "Global allows Databases (DBs) to be spread across different locations. Global propagates changes from one location to another. The Global daemon does the propagation.\nWith global, there may be copies of a database or extract at multiple locations, but only one copy may be writeable. A database is said to be primary at a given location if it is writeable there, and secondary if it is not. A DB may be made primary at any location.\nDifferent extracts from the same extract family may be primary at different locations. This allows multiple different locations to modify the same DB.\n\n\n"}
{"Headers": "Global Propagation", "Content": "Changes made to a primary database (DB) are propagated to the read only secondary DBs. The propagation algorithm just sends the new sessions. For example:\n\nIf this case the propagation algorithm will send the sessions 20 to 39 to the secondary location.\n\n\n"}
{"Headers": "Extract Claim/Release with Global", "Content": "If the two extracts are primary at the same location, then the extract claim/release operations are the same as for non global projects. If the two extracts are primary at different locations then the claim/release goes via the daemon. For example:\n\nThe extract claim operation is thus asynchronous. You have to wait to discover if the claim succeeded or not.\n\n\n"}
{"Headers": "Flush with Global", "Content": "If the two extracts are primary at the same location, then the flush operation is the same as for non global projects. If the two extracts are primary at different locations then the steps are as follows:\n\nThe steps are:\nStep 2 could fail for normal reasons, e.g. a name clash. If so the primary child extract needs to be informed so that next time it uses the correct base session for comparison purposes. At the command level this is the 'EXTRACT FLUSH RESET' command.\n\n\n"}
{"Headers": "Merge Changes for Global Extracts", "Content": "In the Global environment MERGE CHANGES will only be allowed where all lower extracts are also primary on this location.\n\n\n"}
{"Headers": "Undo Capabilities", "Content": "Information is provided on the undo/redo and Backtrack/rewind behavior within the session.\n\n\n"}
{"Headers": "Undo/Redo within a Session", "Content": "The AVEVA E3D Design database has a built in undo/redo capability. Applications may define a start/end transaction and wind back to the start of that transaction.\nInternally this is implemented using 'micro' sessions. Each micro session represents the start of each transaction.\nAn undo can not be done across a SAVEWORK.\n\n\n"}
{"Headers": "Backtrack/Rewind", "Content": "The system administrator may remove the last one or many sessions from the Database (DB).\n\n\n"}
{"Headers": "Database Navigation and Query Syntax", "Content": "This section covers aspects of database navigation. Many examples are given during a Model\u00b4session but are also relevant to the Draw module.\n\n\n"}
{"Headers": "Current Element", "Content": "The database has a concept of current element. This is often referred to as the Current Element (CE). The current element is highlighted in the explorer. In the 3D view the current element is shown in a different colour.\nMany Programmable Macro Language (PML) commands work on the current element.\nThe current element can be changed in the following ways:\nBy picking an element in the explorer\nBy picking an element in the 3D view\nBy typing an element name into the name box\nBy typing a navigation command at the command line\nBy picking an element in the explorer\nBy picking an element in the explorer\nBy picking an element in the 3D view\nBy picking an element in the 3D view\nBy typing an element name into the name box\nBy typing an element name into the name box\nBy typing a navigation command at the command line\nBy typing a navigation command at the command line\n\n\n"}
{"Headers": "Current Position", "Content": "There is also a concept of a current position. The concept of current position is only used when creating elements or when navigating down to the next level.\nBy default the current position is before the first member.\nThis is described further in Climb Up.\n\n\n\nClimb Up\nClimb Up"}
{"Headers": "PML DBRef Object", "Content": "Programmable Macro Language (PML) supports a Database Reference (DBREF) object. A DBREF object identifies an element in the AVEVA E3D Design database. There are various methods available on the DBREF object. The methods for a DBREF are described in the software customization manual.\n\n\n"}
{"Headers": "PML !!CE Variable", "Content": "There is a global Programmable Macro Language (PML) Database Reference (DBREF) variable called !!CE that tracks the database current element. This object may be used/queried at any time.\n\n\n"}
{"Headers": "Specify the Standard Name", "Content": "This is the simplest way of navigating around the database. Just enter the name of the element at the command line. A name is always preceded by a slash.\nFor example:\n/PUMP99\n/BRANCH2\n/BRANCH2 will now be the CE.\n\n\n"}
{"Headers": "Specify the Constructed Name", "Content": "Unnamed elements always have a constructed name. The constructed name consists of:\nIf the constructed name is given, that element will become the CE.\nFor example:\nIf the element is a UDET then the UDET name must be used instead of the system type.\nFor example:\nthe type and relative position in its owners list.\nthe OF keyword\nthe constructed name of its parent\nthe type and relative position in its owners list.\nthe type and relative position in its owners list.\nthe OF keyword\nthe OF keyword\nthe constructed name of its parent\nthe constructed name of its parent\n\n\n"}
{"Headers": "Specify the World", "Content": "The following syntax accesses the world element by name, type:\n\n\n"}
{"Headers": "Specify the Refno", "Content": "The reference number can always be used to navigate to an element.\n\n\n"}
{"Headers": "Use the BACKREf attribute", "Content": "The BACKREf attribute brings the back pointer reference for Reference Table Attributes and answer the question \"what references me (ce)\". The syntax is:\nFor example, standing on a Specific Component (SPCO) and querying for BACKREf (attname SPREF ) will return all elements referencing that SPCO.\nExcluding the argument will list all Reference Table Attributes referencing Current Element (CE).\nFor example:\nQ BACKREF [(ATTNAME att1 [, ATTNAME att2] )]\nQ BACKREF( attname SPCO)\nQ BACKREF\n\n\n"}
{"Headers": "Specify a Relative Position in the Hierarchy", "Content": "Relative navigation can be done using a number of commands as follows:\nClimb up\nMove within current level\nMove to next lower level\nClimb up\nClimb up\nMove within current level\nMove within current level\nMove to next lower level\nMove to next lower level\n\n\n"}
{"Headers": "Climb Up", "Content": "The following syntax is valid:\nOWNER\nclimb to owning element. The owning element becomes the Current Element (CE). The current position is then before the first member\nEND\nclimbs to owning element. The owning element becomes the CE. The current position is at the previous element\n<Element type>\nclimb to element of that type. This element becomes the new CE. This leaves the current position at the immediate member element that was climbed through.\nOWNER\nclimb to owning element. The owning element becomes the Current Element (CE). The current position is then before the first member\nEND\nclimbs to owning element. The owning element becomes the CE. The current position is at the previous element\n<Element type>\nclimb to element of that type. This element becomes the new CE. This leaves the current position at the immediate member element that was climbed through.\nFor example, consider the following hierarchy:\nIf the CE is /MYBOX, then:\nOWNER\nThe CE becomes /MYEQUI. The current position is now before the first member.\nEND\nAlso climbs to /MYEQUI, but leaves the current position at /MYBOX\nEQUI\nAlso climbs to /MYEQUI, and leaves the current position at /MYBOX\nSITE\nClimbs to /MYSITE, and leaves the current position at /MYZONE\nOWNER\nThe CE becomes /MYEQUI. The current position is now before the first member.\nEND\nAlso climbs to /MYEQUI, but leaves the current position at /MYBOX\nEQUI\nAlso climbs to /MYEQUI, and leaves the current position at /MYBOX\nSITE\nClimbs to /MYSITE, and leaves the current position at /MYZONE\n\nOWNER\nclimb to owning element. The owning element becomes the Current Element (CE). The current position is then before the first member\nEND\nclimbs to owning element. The owning element becomes the CE. The current position is at the previous element\n<Element type>\nclimb to element of that type. This element becomes the new CE. This leaves the current position at the immediate member element that was climbed through.\nOWNER\nThe CE becomes /MYEQUI. The current position is now before the first member.\nEND\nAlso climbs to /MYEQUI, but leaves the current position at /MYBOX\nEQUI\nAlso climbs to /MYEQUI, and leaves the current position at /MYBOX\nSITE\nClimbs to /MYSITE, and leaves the current position at /MYZONE\n\n\n\nOWNER\nEND\n<Element type>\nOWNER\nEND\nEQUI\nSITE"}
{"Headers": "Move within the Current Level", "Content": "Next\nGoes to next element in at current level\nNext int\nGoes to next nth element at current level\nNext <element type>\nGoes to next element of given type at current level\nNext int <element type>\nGoes to next nth element of given type at current level\nPrev\nGoes to prev element at current level\nPrev int\nGoes to prev nth element at current level\nPrev <element type>\nto previous element of given type at current level\nPrev int<element type>\nto previous nth element of given type at current level\nFirst\nGoes to first element at current level\nFirst int\nGoes to nth element at current level\nFirst <element type>\nGo to first element of given type\nFirst int <element type>\nGo to nth element of given type\nLast\nGo to last element at current level\nLast int\nGo to nth from last element at current level\nLast <element type>\nGo to last element of given type\nLast int <element type>\nGo to nth last element of given type\n<element type> int\nThis is the same as \u2018First int <element type>\u2019\nNext\nGoes to next element in at current level\nNext int\nGoes to next nth element at current level\nNext <element type>\nGoes to next element of given type at current level\nNext int <element type>\nGoes to next nth element of given type at current level\nPrev\nGoes to prev element at current level\nPrev int\nGoes to prev nth element at current level\nPrev <element type>\nto previous element of given type at current level\nPrev int<element type>\nto previous nth element of given type at current level\nFirst\nGoes to first element at current level\nFirst int\nGoes to nth element at current level\nFirst <element type>\nGo to first element of given type\nFirst int <element type>\nGo to nth element of given type\nLast\nGo to last element at current level\nLast int\nGo to nth from last element at current level\nLast <element type>\nGo to last element of given type\nLast int <element type>\nGo to nth last element of given type\n<element type> int\nThis is the same as \u2018First int <element type>\u2019\nIf a UDET, then the UDET type must be given.\nThe Current element is /MyCylC, as highlighted.\nMoves CE to /MyBoxB\nMoves CE to /MyCylD\nMoves CE to /MyCylD\nMoves CE to /MyBoxD\n\nMoves CE to /MyRtorA\nMoves CE to /MyCylB\nMoves CE to /MyBoxA\nMoves CE to /MyCylA\n\nMoves CE to /MyBoxA\nMoves CE to /MyCylA\nMoves CE to /MyCylA\nMoves CE to /MyCylC\nThis is the same as FIRST 2 BOX. Moves CE to /MyBoxB.\n\nMoves CE to /MyBoxD\nMoves CE to /MyCylD\nMoves CE to /MyCylD\nMoves CE to /MyCylB\n\nNext\nGoes to next element in at current level\nNext int\nGoes to next nth element at current level\nNext <element type>\nGoes to next element of given type at current level\nNext int <element type>\nGoes to next nth element of given type at current level\nPrev\nGoes to prev element at current level\nPrev int\nGoes to prev nth element at current level\nPrev <element type>\nto previous element of given type at current level\nPrev int<element type>\nto previous nth element of given type at current level\nFirst\nGoes to first element at current level\nFirst int\nGoes to nth element at current level\nFirst <element type>\nGo to first element of given type\nFirst int <element type>\nGo to nth element of given type\nLast\nGo to last element at current level\nLast int\nGo to nth from last element at current level\nLast <element type>\nGo to last element of given type\nLast int <element type>\nGo to nth last element of given type\n<element type> int\nThis is the same as \u2018First int <element type>\u2019\nNEXT\nMoves CE to /MyBoxB\nNEXT 3\nMoves CE to /MyCylD\nNEXT CYL\nMoves CE to /MyCylD\nNEXT 3 BOX\nMoves CE to /MyBoxD\nPREV\nMoves CE to /MyRtorA\nPREV 2\nMoves CE to /MyCylB\nPREV BOX\nMoves CE to /MyBoxA\nPREV 2 CYL\nMoves CE to /MyCylA\nFIRST\nMoves CE to /MyBoxA\nFIRST 2\nMoves CE to /MyCylA\nFIRST CYL\nMoves CE to /MyCylA\nFIRST 3 CYL\nMoves CE to /MyCylC\nBOX 2\nThis is the same as FIRST 2 BOX. Moves CE to /MyBoxB.\nLAST\nMoves CE to /MyBoxD\nLAST 2\nMoves CE to /MyCylD\nLAST CYL\nMoves CE to /MyCylD\nLAST 3 CYL\nMoves CE to /MyCylB\n\n\n\nNext\nNext int\nNext <element type>\nNext int <element type>\nPrev\nPrev int\nPrev <element type>\nPrev int<element type>\nFirst\nFirst int\nFirst <element type>\nFirst int <element type>\nLast\nLast int\nLast <element type>\nLast int <element type>\n<element type> int\n5 CYL /MyCylC\nNEXT\nNEXT 3\nNEXT CYL\nNEXT 3 BOX\nPREV\nPREV 2\nPREV BOX\nPREV 2 CYL\nFIRST\nFIRST 2\nFIRST CYL\nFIRST 3 CYL\nBOX 2\nLAST\nLAST 2\nLAST CYL\nLAST 3 CYL"}
{"Headers": "Move to Next Lower Level", "Content": "The syntax for moving down a level shares much of the syntax for moving within the level.\nInt\ndescend to nth child\nFirst Member\nGoes to 1st member\nLast Member\nGoes to last member\nFirst <element type>,\nFirstMember<element type>\nGoes to first member of given type\nFirst int <element type>\nGo to nth element of given type in members list\nLast <element type>,\nLastMember<element type>\nGoes to last member of given type\nLast int <element type>\nGo to nth last element of given type in members list\nNext <element type>\nGoes to next element in member list from current position\nNext int <element type>\nGoes to next nth element in member list of given type from current position\nPrev <element type>\nGoes to next element in member list from current position\nPrev int <element type>\nGoes to previous nth element in member list of given type from current position\n<element type> int\ndescend to nth child of given type\nInt\ndescend to nth child\nFirst Member\nGoes to 1st member\nLast Member\nGoes to last member\nFirst <element type>,\nFirstMember<element type>\nGoes to first member of given type\nFirst int <element type>\nGo to nth element of given type in members list\nLast <element type>,\nLastMember<element type>\nGoes to last member of given type\nLast int <element type>\nGo to nth last element of given type in members list\nNext <element type>\nGoes to next element in member list from current position\nNext int <element type>\nGoes to next nth element in member list of given type from current position\nPrev <element type>\nGoes to next element in member list from current position\nPrev int <element type>\nGoes to previous nth element in member list of given type from current position\n<element type> int\ndescend to nth child of given type\nWe can use the same example as before but in this case we are positioned at the owning equipment, say /MYEQUI. The current position is defaulted to the start of the list. The member list being:\nMoves CE to /MyCylC (5th member)\nMoves CE to /MyBoxA\nMoves CE to /MyBoxD\nMoves CE to /MyCylA\nMoves CE to /MyCylC\nMoves CE to /MyCylD\nMoves CE to /MyCylC\nMoves CE to /MyCylA (same as FIRST CYL)\nMoves CE to /MyCylB (same as FIRST 2 CYL)\nInvalid as there are no cylinders before the current position\nMoves CE to /MYBoxD\nIn the above examples, the use of NEXT had the same result as using FIRST. The use of PREV was invalid. This is because the current position was off the start. We can change the current position using the END syntax to give more meaningful examples\nFor example:\nThe CE is /MyEqui as before, but with the current position at /MyCylB\nMoves CE to /MyCylC\nMoves CE to /MyCylD\nMoves CE to /MyCylA\n\nInt\ndescend to nth child\nFirst Member\nGoes to 1st member\nLast Member\nGoes to last member\nFirst <element type>,\nFirstMember<element type>\nGoes to first member of given type\nFirst int <element type>\nGo to nth element of given type in members list\nLast <element type>,\nLastMember<element type>\nGoes to last member of given type\nLast int <element type>\nGo to nth last element of given type in members list\nNext <element type>\nGoes to next element in member list from current position\nNext int <element type>\nGoes to next nth element in member list of given type from current position\nPrev <element type>\nGoes to next element in member list from current position\nPrev int <element type>\nGoes to previous nth element in member list of given type from current position\n<element type> int\ndescend to nth child of given type\n5\nMoves CE to /MyCylC (5th member)\nFIRST MEMBER\nMoves CE to /MyBoxA\nLAST MEMBER\nMoves CE to /MyBoxD\nFIRST CYL\nMoves CE to /MyCylA\nFIRST 3 CYL\nMoves CE to /MyCylC\nLAST CYL\nMoves CE to /MyCylD\nLAST 2 CYL\nMoves CE to /MyCylC\nNEXT CYL\nMoves CE to /MyCylA (same as FIRST CYL)\nNEXT 2 CYL\nMoves CE to /MyCylB (same as FIRST 2 CYL)\nPREV CYL\nInvalid as there are no cylinders before the current position\nBOX 4\nMoves CE to /MYBoxD\nNEXT CYL\nMoves CE to /MyCylC\nNEXT 2 CYL\nMoves CE to /MyCylD\nPREV CYL\nMoves CE to /MyCylA\n/MyCylB\nEND\n\n\n\nInt\nFirst Member\nLast Member\nFirst <element type>,\nFirstMember<element type>\nFirst int <element type>\nLast <element type>,\nLastMember<element type>\nLast int <element type>\nNext <element type>\nNext int <element type>\nPrev <element type>\nPrev int <element type>\n<element type> int\n5\nFIRST MEMBER\nLAST MEMBER\nFIRST CYL\nFIRST 3 CYL\nLAST CYL\nLAST 2 CYL\nNEXT CYL\nNEXT 2 CYL\nPREV CYL\nBOX 4\nNEXT CYL\nNEXT 2 CYL\nPREV CYL"}
{"Headers": "Syntax Ambiguity Between Moving Across and Down", "Content": "In most cases there is no ambiguity with having some of the same syntax for moving down and moving across. This is because it is rare to have the same element type as a sibling and a member. However there are some situations where this does occur. In these cases, the default is to move down rather than across.\nFor example.\n\nIf the CE is /SUBE1, then\nBOX 1\nMoves CE to /BoxX (NOT /BoxA)\nNEXT BOX\nMoves CE to /BoxX (NOT /BoxB)\nLAST BOX\nMoves CE to /BoxY (NOT /BoxB)\nBOX 1\nMoves CE to /BoxX (NOT /BoxA)\nNEXT BOX\nMoves CE to /BoxX (NOT /BoxB)\nLAST BOX\nMoves CE to /BoxY (NOT /BoxB)\n\nBOX 1\nMoves CE to /BoxX (NOT /BoxA)\nNEXT BOX\nMoves CE to /BoxX (NOT /BoxB)\nLAST BOX\nMoves CE to /BoxY (NOT /BoxB)\n\n\n\nBOX 1\nNEXT BOX\nLAST BOX"}
{"Headers": "Climb up by Default", "Content": "The commands to move to an element at the same level, may also be used for elements at any higher level. which means, if the command is invalid at the CE, AVEVA E3D Design will keep on climbing until the command becomes valid.\nFor example, for the previous example, with the Current element (CE) at /BoxY:\nSUBE 2\nMoves CE to /SUBE2\nLAST SUBE\nMoves CE to /SUBE2\nFIRST ZONE\nMoves CE to /Zone1 (assuming that this is the first zone)\nSUBE 2\nMoves CE to /SUBE2\nLAST SUBE\nMoves CE to /SUBE2\nFIRST ZONE\nMoves CE to /Zone1 (assuming that this is the first zone)\n\nSUBE 2\nMoves CE to /SUBE2\nLAST SUBE\nMoves CE to /SUBE2\nFIRST ZONE\nMoves CE to /Zone1 (assuming that this is the first zone)\n\n\n\nSUBE 2\nLAST SUBE\nFIRST ZONE"}
{"Headers": "Use the \u2018OF\u2019 Syntax", "Content": "The commands described so far all work on the Current Element (CE). It is allow able to do a navigation relative to any element by using the \u2018OF\u2019 syntax.\nFor example:\nThe \u2018constructed\u2019 name is actually an example of the use of the \u2018OF\u2019 syntax.\nThe \u2018OF\u2019 syntax can be nested as much as required.\nFor example:\nFIRST MEMBER OF /ZONE1\n FIRST MEMBER OF FIRST BOX OF NEXT EQUI\n\n\n"}
{"Headers": "Other Syntax", "Content": "Information provided on the GOTO Syntax and how to return to the previous current element..\n\n\n"}
{"Headers": "Use the GOTO Syntax", "Content": "The GOTO command can be used to go to any reference attribute.\nFor example:\nThis will go to the element pointed to by the CREF of the Current Element (CE).\nAs with other navigation commands, the \u2018OF\u2019 syntax may be used to go to reference on a different element.\nFor example:\nPseudo attributes can be specified after GOTO. A particularly useful pseudo attribute is FRSTW. This goes to first world of a given type.\nFor example:\nThis will go to the first catalog world.\nGOTO CREF \nGOTO HREF OF /BRANCH88\nGOTO FRSTW CATA\n\n\n"}
{"Headers": "Return to the Previous Current Element", "Content": "The SAME command will always return to the previous current element.\nFor example:\nThe current element will now be /VESS1.\n/VESS1\n/SECTION99\nSAME\n\n\n"}
{"Headers": "ID Expressions", "Content": "The above commands are all examples of an identification (ID) expression. The one exception is the \u2018GOTO\u2019 syntax. This keyword is omitted within an ID expression. ID expressions should be enclosed in brackets, although in most cases, they will work without the brackets. An ID expression may itself be queried or assigned to a Programmable Macro Language (PML) variable.\nQuerying an expression or assigning it to a PML variable dos NOT change the CE.\nAssigning an ID expression to a PML variable is a common way to write PML.\nQ ( NEXT BOX)\n!MyEle = ( next box )\n!MyEle = ( next box of /VESS1 )\n!MyEle = (SPRE )\n\n\n"}
{"Headers": "Special Cases", "Content": "Information provided on the User Defined Element Type (UDET) and the TRACE command.\n\n\n"}
{"Headers": "UDETs", "Content": "A User Defined Element Type (UDET) may be used wherever an element type is valid.\nFor example:\nThe following exception applies:\nWhen climbing, either the UDET or the base type may be specified.\nFor example:\n(:MYBOX 1 OF /VESS1 )\nNEXT :MYBOX\nFIRST 2 :MYBOX\n:MYEQUIP - will climb to /VESSEL\nEQUIP - will also climb to /VESSEL\n\n\n"}
{"Headers": "Trace Command", "Content": "If in TeleTypewriter (TTY) mode, the TRACE ON/OFF command can be turned on track changes in current element. The default is on.\n\n\n"}
{"Headers": "Pseudo Attributes Relating to Navigation", "Content": "The following pseudo attributes relate to the database hierarchy. These can be queried directly or via a Programmable Macro Language (PML) variable.\nALLELE\nDBREF\nElementType\nAll elements in the MDB of a particular type\nCONNECTIONS\nDBREF array\n\nConnections\nCONNECTIONSH\nDBREF array\n\nConnections for all descendants\nCONNER\nString\nInt\nConnection error message\nDDEP\nInt\n\nDatabase depth within hierarchy (World is 0)\nFRSTW\nDBREF\nString\nReference of first world of given DB type in current MDB\nMAXD\nInt\n\nDB hierarchy depth of lowest level item beneath element\nMBACK\nDBREF array\n*ElementType\nMembers in reverse order\nMCOU\nInt\n*ElementType\nNumber of Element Members of Given type\nMEMB\nDBREF array\n*ElementType\nAll members, or members of specific type\nOWNLST\nDBREF array\n\nOwning hierarchy\nPARENT\nDBREF\n*ElementType\nReference of ascendant element of specified type\nSEQU\nInt\n\nSequence Position in Member List\nTYSEQU\nInt\n\nType Sequence Number\n\u2018*\u2019- qualifier is optional\nAttribute Name\nData Type\nQualifier\nDescription\nALLELE\nDBREF\nElementType\nAll elements in the MDB of a particular type\nCONNECTIONS\nDBREF array\nConnections\nCONNECTIONSH\nDBREF array\nConnections for all descendants\nCONNER\nString\nInt\nConnection error message\nDDEP\nInt\nDatabase depth within hierarchy (World is 0)\nFRSTW\nDBREF\nString\nReference of first world of given DB type in current MDB\nMAXD\nInt\nDB hierarchy depth of lowest level item beneath element\nMBACK\nDBREF array\n*ElementType\nMembers in reverse order\nMCOU\nInt\n*ElementType\nNumber of Element Members of Given type\nMEMB\nDBREF array\n*ElementType\nAll members, or members of specific type\nOWNLST\nDBREF array\nOwning hierarchy\nPARENT\nDBREF\n*ElementType\nReference of ascendant element of specified type\nSEQU\nInt\nSequence Position in Member List\nTYSEQU\nInt\nType Sequence Number\n\n\n"}
{"Headers": "Attributes", "Content": "Information is provided on attribute types, real attributes, physical quantities, setting and querying attributes, PML attribute classes and PML element type classes.\n\n\n"}
{"Headers": "Attribute Types", "Content": "Attributes can be the following types:\nAttributes may also be arrays of simple attributes Those supported are:\nInteger\nReal\nBool (or Logical)\nString (or Text)\nDatetime\nRef\nThis is a pointer to another element by storing its internal database reference (as Integer(2) array)\nPosition\nThis is a special form of Real(3) array containing 3 distances\nDirection\nThis is a special form of a Real(3) array\nOrientation\nThis is a special form of a Real(3) array\nWord\nThis a character string of up to either 4 or 6 American Standard Code for Information Interchange (ASCI)I upper case character string stored as an integer which is often interpreted either as an enumerated value or as a user readable name. Words are used for the simple names and for many enumerated integer values. They are often called hash codes.\nIf more than 4 (or 6) characters are entered only the first ones will be used, but without generating an error. Lower case characters will be converted to uppercase, and non ASCII unicode characters will be ignored. The word cannot contain a space. The space is one of the characters that will automatically delimit the string.\nDifferent attributes are limited to either 4 or 6 characters, although attribute and element type names do have up to 6. Whether 4 or 6 are allowed is an implementation issue and the older attributes existing in originally introduced in earlier databases tend to be limited to 4 characters.\nExamples of their use are TYPE of elements and attributes.\nModifier attributes (JUST = TOP, BOT)\nPline names\nUnit field of real attributes and dimension setting attributes (PTYPE = DIST, BORE, NONE etc)\nInteger\nInteger\nReal\nReal\nBool (or Logical)\nBool (or Logical)\nString (or Text)\nString (or Text)\nDatetime\nDatetime\nRef\nThis is a pointer to another element by storing its internal database reference (as Integer(2) array)\nRef\nPosition\nThis is a special form of Real(3) array containing 3 distances\nPosition\nDirection\nThis is a special form of a Real(3) array\nDirection\nOrientation\nThis is a special form of a Real(3) array\nOrientation\nWord\nThis a character string of up to either 4 or 6 American Standard Code for Information Interchange (ASCI)I upper case character string stored as an integer which is often interpreted either as an enumerated value or as a user readable name. Words are used for the simple names and for many enumerated integer values. They are often called hash codes.\nIf more than 4 (or 6) characters are entered only the first ones will be used, but without generating an error. Lower case characters will be converted to uppercase, and non ASCII unicode characters will be ignored. The word cannot contain a space. The space is one of the characters that will automatically delimit the string.\nDifferent attributes are limited to either 4 or 6 characters, although attribute and element type names do have up to 6. Whether 4 or 6 are allowed is an implementation issue and the older attributes existing in originally introduced in earlier databases tend to be limited to 4 characters.\nExamples of their use are TYPE of elements and attributes.\nModifier attributes (JUST = TOP, BOT)\nPline names\nUnit field of real attributes and dimension setting attributes (PTYPE = DIST, BORE, NONE etc)\nWord\nInteger Array\nReal Array\nBool (or Logical) Array\nText Array\nRef Array\nInteger Array\nInteger Array\nReal Array\nReal Array\nBool (or Logical) Array\nBool (or Logical) Array\nText Array\nText Array\nRef Array\nRef Array\n\n\n"}
{"Headers": "Real Attributes of Physical Quantities", "Content": "Real attributes can be purely numeric, but often they may be representing physical quantities. The type of a physical quantity is its (physical) dimension.\nAttributes of physical quantities are consistently stored in the database in defined database units, irrespective of the current working units, or of the units of any value entered by you. The whole system operates on the expectation that all stored values of physically dimensioned quantities are in their relevant standard database units.\nThe following table lists the dimensions understood by the system giving:\nFor example attributes of length have a hash code of DIST are stored in mm and other standard units include inch, cm, ft, metre:\nAbsPressure\nABSP\npascal\nbar atm PSI torr mmHg inHg\npressure may be absolute or gauge\nAcceleration\nACCL\nm/s2\n\n\nActualPower\nACTPOW\nV.A\n\n\nAngle\nANGL\ndegree\ngrade arcmin arcsec\n\nAngularAcceleration\nANGCCE\nrad/s2\n\n\nAngularFrequency\nANGF\ndeg/s\nrpm rps rph angFreqHertz\n\nAngularMomentum\nANGM\nN.m.s\n\n\nArea\nSQDI\nmm2\nacre hectare\n\nAreaPerLength\nAREALE\nm2/m\nAreaPerLength\n\nBore\nBORE\nmm\nin\nRange of bore units limited to mm and inch (and Finch)\nCableSize\nCABL\nkcmil\ncirmil circmms\n\nCalorificValueMole\nCALVQ\nJ/Mol\n\n\nCalorificValueVolume\nCALVV\nJ/m3\n\n\nCapacitance\nCAPA\nfarad\n\n\nCharge\nCHAR\ncoulomb\n\n\nConductance\nCOND\nsiemens\nmho\n\nContent\nPCUD\nmm-3\n\n\nConvertiblePressure\nPRESC\ncpascala\ncpascalg cbarg catmg cpsig ctorrg cmmHgg cinHgg cbara catma cpsia ctorra cmmHga cinHga osia inHgaAtSixtyDegF mmHgaAtSixtyDegF inWateraAtSixtyDegF inWateraAtFourDegC ftWateraAtSixtyDegF ftWateraAtFourDegC ata\n\nCurrency\nCURY\nUSD\nGBP EUR\n\nCurrent\nCURR\nampere\n\n\nCurrentDensity\nCURITY\nA/m2\n\n\nDensity\nDENS\nkg/m3\n\n\nDensityMANDB\nMAND\nkg/mm3\n\ndensities stored in MANU database\nEffectiveHeatCapacity\nEFFCAP\nJ/m/K\n\n\nElectricChargeDensity\nELECSI\nC/m3\n\n\nElectricConductivity\nCNDT\nS/m\n\n\nElectricField\nEFLD\nV/m\n\n\nElectricFluxDensity\nELEFSI\nC/m2\n\n\nEMF\nEMF\nvolt\n\n\nEnergy\nENER\nkWh\njoule BTU calorie calorieit BTUit chu chuAtFifteenDegC\n\nEnergyDensity\nEDEN\nJ/kg\n\n\nEntropy\nENTR\nJ/K\n\n\nEquivalence\nEQUIVA\nequivalent\n\n\nEquivalenceFlow\nEQULOW\nequiv/s\n\n\nEquivalencePerVolume\nEQPRME\nequiv/m3\n\n\nFlowRateMolePerLength\nSQPTD\nMol/s/m\n\n\nFlowRateVolPerRpm\nFRVPR\n\n\n\nForce\nFORC\nnewton\npdl dyne kgf lbf\n\nFoulingFactor\nFFAC\nm2.K/W\n\n\nFrequency\nFREQ\nhertz\nfreqRpm freqRps freqRph\n\nGaugePressure\nGAGE\npascal\nbar atm PSI torr mmHg inHg\npressure may be absolute or gauge\nHeatCoefficientArea\nHEAREA\nW/K\n\n\nHeatFluxLinear\nHEAEAR\nW/m\n\n\nHeatingValue\nHVAL\nJ/m3\n\n\nHeatOfReaction\nHEAION\nJ/m3/h\n\n\nHeatTransferCoeff\nHTRA\nW/m2/K\n\n\nIlluminance\nILLUMI\nlux\n\n\nImpedance\nIMPE\nohm\n\n\nInductance\nINDU\nhenry\n\n\nInertia\nINER\nkg/m2\n\n\nInversePressure\nINVURE\npascal-1\n\n\nInverseTemperature\nINVRAT\nkelvin-1\n\n\nKinematicViscosity\nKVIS\nm2/s\nStoke\n\nLength\nDIST\nmm\nm in ft cm km mile yard micron thou angstrom\n\nLinearDensity\nPDIS\nmm-1\n\n\nLuminance\nLUMNCE\ncd/m2\n\n\nLuminousFlux\nLUMLUX\nlumen\n\n\nLuminousIntensity\nLUMI\nCandela\n\n\nMagFieldIntensity\nMFIN\nA/m\n\n\nMagFluxDensity\nMFXD\ntesla\n\n\nMagneticFlux\nMGFX\nweber\n\n\nMass\nMASS\nkg\ngram tonne lb oz longTon shortTon cwt longCwt shortCwt ozt grain stone\n\nMassFlow\nMFLO\nkg/s\n\n\nMassFlux\nMASLUX\nkg/s/m2\n\n\nMassPerArea\nMAPEA\nkg/m2\n\n\nMassPerEnergy\nMAPGY\nkg/J\n\n\nMassReactionRate\nMARETE\nkg/s/m3\n\n\nMolarConcentration\nMOLONC\nMol/m3\n\n\nMolarEntropy\nMOLOPY\nJ/Mol/K\n\n\nMolarFlow\nMOLLOW\nMol/s\n\n\nMolarMass\nMOLASS\nkg/Mol\n\n\nMolarPermeability\nMOLITY\n\n\n\nMolarReactionRate\nMOLATV\nMol/m3/s\n\n\nMolarReactionRateMass\nMOLATM\nMol/kg/s\n\n\nMolarVolume\nMOLUME\nm3/Mol\n\n\nMoleFluxDensity\nMOLATA\nMol/m2/s\n\n\nMolePerMass\nMOLALY\nMol/kg\n\n\nMomentum\nMOME\nN.s\n\n\nNoise\nNOIS\nDecibelA\n\n\nPermeability\nPMBT\nH/m\n\n\nPermittivity\nPMTT\nF/m\n\n\npH\nPH\npH\n\n\nPower\nPOWE\nkW\nhp watt\n\nPowerPerArea\nPOPEA\nW/m2\n\n\nPowerPerVolume\nPOWUME\nW/m3\n\n\nPressure\nPRES\npascal\nbar atm psi torr mmHg inHg osi inHgAtSixtyDegF mmHgAtSixtyDegF inWaterAtSixtyDegF inWaterAtFourDegC ftWaterAtSixtyDegF ftWaterAtFourDegC mmWaterAtSixtyDegF mmWaterAtFourDegC at\n\nPressurePerDistance\nPRPEST\nPa/m\n\n\nPressurePerTemperature\nPRPEMP\nPa/K\n\n\nPressureRate\nPREATE\nPa/s\n\n\nRadiance\nRADNCE\n\n\n\nRadiantIntensity\nRADITY\nW/sr\n\n\nRadiationDose\nRDOS\nsievert\nrem gray raddose\n\nRadioactivity\nRADY\nBq\ncurie\n\nRadioactivityConc\nRADONC\nBq/m3\n\n\nRatio\nRATIO\nRatio\npc ppm ppb\n\nReactivePower\nREAC\nVAreac\n\n\nResistivity\nREST\nohm/m\n\n\nRotationalStiffness\nSTFR\nN.m/rad\n\n\nSecondMomentOfArea\nSMOFA\nmetre4\n\n\nSolidAngle\nSANGL\nsteradian\n\n\nSolventPermeability\nSOPETY\nkg/m2/s/Pa\n\n\nSpecFuelelConsumptionVol\nSPFUNS\nm3/J\n\n\nSpecHeatCapacity\nSHCP\nJ/kg/K\n\n\nSpecificRadioactivity\nSPVITY\nBq/g\n\n\nSpecificSurfaceMass\nSPEASS\nm2/kg\n\n\nSpeed\nSPEE\nm/s\nknot\n\nStiffness\nSTIF\nN/m\n\n\nSubstanceQuantity\nSUBQ\nMole\nlbMole stdcubicfoot stdcubicmeters\n\nSurfaceDensity\nPSQD\nmm-2\n\n\nTemperature\nTEMP\ndegC\ndegF kelvin degRan\n\nTemperatureGradient\nTPDI\ndegC/mm\n\n\nTemperatureRate\nTEMATE\nK/s\n\n\nTemperatureVolumePerMole\nVOLPTQ\n\n\n\nThermalConductivity\nTCON\nW/m/K\n\n\nThermalExpansionCoeff\nTHENCO\ndegC-1\n\n\nThermalResistance\nTRES\nK/W\n\n\nTime\nTIME\nsecond\nmin hr day month week year\n\nTorque\nTORQ\nN.m\n\n\nUnitMass\nUMAS\nkg/mm\n\n\nViscosityDynamic\nVISC\nPa.s\npoise\n\nVolHeatTransferCoeff\nVOLEFF\nW/m3/K\n\n\nVolume\nCUDI\nmm3\nlitre ImpGal USGal bbl Mbbl MMbbl grt ImpQrt USQrt USDryQrt ImpPint USPint USDryPint ImpFloz USFloz USDryGal\n\nVolumetricFlow\nVFLO\nm3/s\nMSCubicFeetDay\n\nNone\nNONE\n\n\nnumerical real attribute\nWORD\nWORD\n\n\nused in assigning parameter dimensions etc.\nParameter\nUNIPAR\n\n\nused for parameter attributes\n\nName of Dimension\nHashCode/Word\nDatabase Units\nOther Specific Units\nComments\nAbsPressure\nABSP\npascal\nbar atm PSI torr mmHg inHg\npressure may be absolute or gauge\nAcceleration\nACCL\nm/s2\nActualPower\nACTPOW\nV.A\nAngle\nANGL\ndegree\ngrade arcmin arcsec\nAngularAcceleration\nANGCCE\nrad/s2\nAngularFrequency\nANGF\ndeg/s\nrpm rps rph angFreqHertz\nAngularMomentum\nANGM\nN.m.s\nArea\nSQDI\nmm2\nacre hectare\nAreaPerLength\nAREALE\nm2/m\nAreaPerLength\nBore\nBORE\nmm\nin\nRange of bore units limited to mm and inch (and Finch)\nCableSize\nCABL\nkcmil\ncirmil circmms\nCalorificValueMole\nCALVQ\nJ/Mol\nCalorificValueVolume\nCALVV\nJ/m3\nCapacitance\nCAPA\nfarad\nCharge\nCHAR\ncoulomb\nConductance\nCOND\nsiemens\nmho\nContent\nPCUD\nmm-3\nConvertiblePressure\nPRESC\ncpascala\ncpascalg cbarg catmg cpsig ctorrg cmmHgg cinHgg cbara catma cpsia ctorra cmmHga cinHga osia inHgaAtSixtyDegF mmHgaAtSixtyDegF inWateraAtSixtyDegF inWateraAtFourDegC ftWateraAtSixtyDegF ftWateraAtFourDegC ata\nCurrency\nCURY\nUSD\nGBP EUR\nCurrent\nCURR\nampere\nCurrentDensity\nCURITY\nA/m2\nDensity\nDENS\nkg/m3\nDensityMANDB\nMAND\nkg/mm3\ndensities stored in MANU database\nEffectiveHeatCapacity\nEFFCAP\nJ/m/K\nElectricChargeDensity\nELECSI\nC/m3\nElectricConductivity\nCNDT\nS/m\nElectricField\nEFLD\nV/m\nElectricFluxDensity\nELEFSI\nC/m2\nEMF\nEMF\nvolt\nEnergy\nENER\nkWh\njoule BTU calorie calorieit BTUit chu chuAtFifteenDegC\nEnergyDensity\nEDEN\nJ/kg\nEntropy\nENTR\nJ/K\nEquivalence\nEQUIVA\nequivalent\nEquivalenceFlow\nEQULOW\nequiv/s\nEquivalencePerVolume\nEQPRME\nequiv/m3\nFlowRateMolePerLength\nSQPTD\nMol/s/m\nFlowRateVolPerRpm\nFRVPR\nForce\nFORC\nnewton\npdl dyne kgf lbf\nFoulingFactor\nFFAC\nm2.K/W\nFrequency\nFREQ\nhertz\nfreqRpm freqRps freqRph\nGaugePressure\nGAGE\npascal\nbar atm PSI torr mmHg inHg\npressure may be absolute or gauge\nHeatCoefficientArea\nHEAREA\nW/K\nHeatFluxLinear\nHEAEAR\nW/m\nHeatingValue\nHVAL\nJ/m3\nHeatOfReaction\nHEAION\nJ/m3/h\nHeatTransferCoeff\nHTRA\nW/m2/K\nIlluminance\nILLUMI\nlux\nImpedance\nIMPE\nohm\nInductance\nINDU\nhenry\nInertia\nINER\nkg/m2\nInversePressure\nINVURE\npascal-1\nInverseTemperature\nINVRAT\nkelvin-1\nKinematicViscosity\nKVIS\nm2/s\nStoke\nLength\nDIST\nmm\nm in ft cm km mile yard micron thou angstrom\nLinearDensity\nPDIS\nmm-1\nLuminance\nLUMNCE\ncd/m2\nLuminousFlux\nLUMLUX\nlumen\nLuminousIntensity\nLUMI\nCandela\nMagFieldIntensity\nMFIN\nA/m\nMagFluxDensity\nMFXD\ntesla\nMagneticFlux\nMGFX\nweber\nMass\nMASS\nkg\ngram tonne lb oz longTon shortTon cwt longCwt shortCwt ozt grain stone\nMassFlow\nMFLO\nkg/s\nMassFlux\nMASLUX\nkg/s/m2\nMassPerArea\nMAPEA\nkg/m2\nMassPerEnergy\nMAPGY\nkg/J\nMassReactionRate\nMARETE\nkg/s/m3\nMolarConcentration\nMOLONC\nMol/m3\nMolarEntropy\nMOLOPY\nJ/Mol/K\nMolarFlow\nMOLLOW\nMol/s\nMolarMass\nMOLASS\nkg/Mol\nMolarPermeability\nMOLITY\nMolarReactionRate\nMOLATV\nMol/m3/s\nMolarReactionRateMass\nMOLATM\nMol/kg/s\nMolarVolume\nMOLUME\nm3/Mol\nMoleFluxDensity\nMOLATA\nMol/m2/s\nMolePerMass\nMOLALY\nMol/kg\nMomentum\nMOME\nN.s\nNoise\nNOIS\nDecibelA\nPermeability\nPMBT\nH/m\nPermittivity\nPMTT\nF/m\npH\nPH\npH\nPower\nPOWE\nkW\nhp watt\nPowerPerArea\nPOPEA\nW/m2\nPowerPerVolume\nPOWUME\nW/m3\nPressure\nPRES\npascal\nbar atm psi torr mmHg inHg osi inHgAtSixtyDegF mmHgAtSixtyDegF inWaterAtSixtyDegF inWaterAtFourDegC ftWaterAtSixtyDegF ftWaterAtFourDegC mmWaterAtSixtyDegF mmWaterAtFourDegC at\nPressurePerDistance\nPRPEST\nPa/m\nPressurePerTemperature\nPRPEMP\nPa/K\nPressureRate\nPREATE\nPa/s\nRadiance\nRADNCE\nRadiantIntensity\nRADITY\nW/sr\nRadiationDose\nRDOS\nsievert\nrem gray raddose\nRadioactivity\nRADY\nBq\ncurie\nRadioactivityConc\nRADONC\nBq/m3\nRatio\nRATIO\nRatio\npc ppm ppb\nReactivePower\nREAC\nVAreac\nResistivity\nREST\nohm/m\nRotationalStiffness\nSTFR\nN.m/rad\nSecondMomentOfArea\nSMOFA\nmetre4\nSolidAngle\nSANGL\nsteradian\nSolventPermeability\nSOPETY\nkg/m2/s/Pa\nSpecFuelelConsumptionVol\nSPFUNS\nm3/J\nSpecHeatCapacity\nSHCP\nJ/kg/K\nSpecificRadioactivity\nSPVITY\nBq/g\nSpecificSurfaceMass\nSPEASS\nm2/kg\nSpeed\nSPEE\nm/s\nknot\nStiffness\nSTIF\nN/m\nSubstanceQuantity\nSUBQ\nMole\nlbMole stdcubicfoot stdcubicmeters\nSurfaceDensity\nPSQD\nmm-2\nTemperature\nTEMP\ndegC\ndegF kelvin degRan\nTemperatureGradient\nTPDI\ndegC/mm\nTemperatureRate\nTEMATE\nK/s\nTemperatureVolumePerMole\nVOLPTQ\nThermalConductivity\nTCON\nW/m/K\nThermalExpansionCoeff\nTHENCO\ndegC-1\nThermalResistance\nTRES\nK/W\nTime\nTIME\nsecond\nmin hr day month week year\nTorque\nTORQ\nN.m\nUnitMass\nUMAS\nkg/mm\nViscosityDynamic\nVISC\nPa.s\npoise\nVolHeatTransferCoeff\nVOLEFF\nW/m3/K\nVolume\nCUDI\nmm3\nlitre ImpGal USGal bbl Mbbl MMbbl grt ImpQrt USQrt USDryQrt ImpPint USPint USDryPint ImpFloz USFloz USDryGal\nVolumetricFlow\nVFLO\nm3/s\nMSCubicFeetDay\nNone\nNONE\nnumerical real attribute\nWORD\nWORD\nused in assigning parameter dimensions etc.\nParameter\nUNIPAR\nused for parameter attributes\n\n\n"}
{"Headers": "Real Attributes of Physical Quantities", "Content": "Real attributes can be purely numeric, but often they may be representing physical quantities. The type of a physical quantity is its (physical) dimension.\nAttributes of physical quantities are consistently stored in the database in defined database units, irrespective of the current working units, or of the units of any value entered by you. The whole system operates on the expectation that all stored values of physically dimensioned quantities are in their relevant standard database units.\nThe following table lists the dimensions understood by the system giving:\nFor example attributes of length have a hash code of DIST are stored in mm and other standard units include inch, cm, ft, metre:\nAbsPressure\nABSP\npascal\nbar atm PSI torr mmHg inHg\npressure may be absolute or gauge\nAcceleration\nACCL\nm/s2\n\n\nActualPower\nACTPOW\nV.A\n\n\nAngle\nANGL\ndegree\ngrade arcmin arcsec\n\nAngularAcceleration\nANGCCE\nrad/s2\n\n\nAngularFrequency\nANGF\ndeg/s\nrpm rps rph angFreqHertz\n\nAngularMomentum\nANGM\nN.m.s\n\n\nArea\nSQDI\nmm2\nacre hectare\n\nAreaPerLength\nAREALE\nm2/m\nAreaPerLength\n\nBore\nBORE\nmm\nin\nRange of bore units limited to mm and inch (and Finch)\nCableSize\nCABL\nkcmil\ncirmil circmms\n\nCalorificValueMole\nCALVQ\nJ/Mol\n\n\nCalorificValueVolume\nCALVV\nJ/m3\n\n\nCapacitance\nCAPA\nfarad\n\n\nCharge\nCHAR\ncoulomb\n\n\nConductance\nCOND\nsiemens\nmho\n\nContent\nPCUD\nmm-3\n\n\nConvertiblePressure\nPRESC\ncpascala\ncpascalg cbarg catmg cpsig ctorrg cmmHgg cinHgg cbara catma cpsia ctorra cmmHga cinHga osia inHgaAtSixtyDegF mmHgaAtSixtyDegF inWateraAtSixtyDegF inWateraAtFourDegC ftWateraAtSixtyDegF ftWateraAtFourDegC ata\n\nCurrency\nCURY\nUSD\nGBP EUR\n\nCurrent\nCURR\nampere\n\n\nCurrentDensity\nCURITY\nA/m2\n\n\nDensity\nDENS\nkg/m3\n\n\nDensityMANDB\nMAND\nkg/mm3\n\ndensities stored in MANU database\nEffectiveHeatCapacity\nEFFCAP\nJ/m/K\n\n\nElectricChargeDensity\nELECSI\nC/m3\n\n\nElectricConductivity\nCNDT\nS/m\n\n\nElectricField\nEFLD\nV/m\n\n\nElectricFluxDensity\nELEFSI\nC/m2\n\n\nEMF\nEMF\nvolt\n\n\nEnergy\nENER\nkWh\njoule BTU calorie calorieit BTUit chu chuAtFifteenDegC\n\nEnergyDensity\nEDEN\nJ/kg\n\n\nEntropy\nENTR\nJ/K\n\n\nEquivalence\nEQUIVA\nequivalent\n\n\nEquivalenceFlow\nEQULOW\nequiv/s\n\n\nEquivalencePerVolume\nEQPRME\nequiv/m3\n\n\nFlowRateMolePerLength\nSQPTD\nMol/s/m\n\n\nFlowRateVolPerRpm\nFRVPR\n\n\n\nForce\nFORC\nnewton\npdl dyne kgf lbf\n\nFoulingFactor\nFFAC\nm2.K/W\n\n\nFrequency\nFREQ\nhertz\nfreqRpm freqRps freqRph\n\nGaugePressure\nGAGE\npascal\nbar atm PSI torr mmHg inHg\npressure may be absolute or gauge\nHeatCoefficientArea\nHEAREA\nW/K\n\n\nHeatFluxLinear\nHEAEAR\nW/m\n\n\nHeatingValue\nHVAL\nJ/m3\n\n\nHeatOfReaction\nHEAION\nJ/m3/h\n\n\nHeatTransferCoeff\nHTRA\nW/m2/K\n\n\nIlluminance\nILLUMI\nlux\n\n\nImpedance\nIMPE\nohm\n\n\nInductance\nINDU\nhenry\n\n\nInertia\nINER\nkg/m2\n\n\nInversePressure\nINVURE\npascal-1\n\n\nInverseTemperature\nINVRAT\nkelvin-1\n\n\nKinematicViscosity\nKVIS\nm2/s\nStoke\n\nLength\nDIST\nmm\nm in ft cm km mile yard micron thou angstrom\n\nLinearDensity\nPDIS\nmm-1\n\n\nLuminance\nLUMNCE\ncd/m2\n\n\nLuminousFlux\nLUMLUX\nlumen\n\n\nLuminousIntensity\nLUMI\nCandela\n\n\nMagFieldIntensity\nMFIN\nA/m\n\n\nMagFluxDensity\nMFXD\ntesla\n\n\nMagneticFlux\nMGFX\nweber\n\n\nMass\nMASS\nkg\ngram tonne lb oz longTon shortTon cwt longCwt shortCwt ozt grain stone\n\nMassFlow\nMFLO\nkg/s\n\n\nMassFlux\nMASLUX\nkg/s/m2\n\n\nMassPerArea\nMAPEA\nkg/m2\n\n\nMassPerEnergy\nMAPGY\nkg/J\n\n\nMassReactionRate\nMARETE\nkg/s/m3\n\n\nMolarConcentration\nMOLONC\nMol/m3\n\n\nMolarEntropy\nMOLOPY\nJ/Mol/K\n\n\nMolarFlow\nMOLLOW\nMol/s\n\n\nMolarMass\nMOLASS\nkg/Mol\n\n\nMolarPermeability\nMOLITY\n\n\n\nMolarReactionRate\nMOLATV\nMol/m3/s\n\n\nMolarReactionRateMass\nMOLATM\nMol/kg/s\n\n\nMolarVolume\nMOLUME\nm3/Mol\n\n\nMoleFluxDensity\nMOLATA\nMol/m2/s\n\n\nMolePerMass\nMOLALY\nMol/kg\n\n\nMomentum\nMOME\nN.s\n\n\nNoise\nNOIS\nDecibelA\n\n\nPermeability\nPMBT\nH/m\n\n\nPermittivity\nPMTT\nF/m\n\n\npH\nPH\npH\n\n\nPower\nPOWE\nkW\nhp watt\n\nPowerPerArea\nPOPEA\nW/m2\n\n\nPowerPerVolume\nPOWUME\nW/m3\n\n\nPressure\nPRES\npascal\nbar atm psi torr mmHg inHg osi inHgAtSixtyDegF mmHgAtSixtyDegF inWaterAtSixtyDegF inWaterAtFourDegC ftWaterAtSixtyDegF ftWaterAtFourDegC mmWaterAtSixtyDegF mmWaterAtFourDegC at\n\nPressurePerDistance\nPRPEST\nPa/m\n\n\nPressurePerTemperature\nPRPEMP\nPa/K\n\n\nPressureRate\nPREATE\nPa/s\n\n\nRadiance\nRADNCE\n\n\n\nRadiantIntensity\nRADITY\nW/sr\n\n\nRadiationDose\nRDOS\nsievert\nrem gray raddose\n\nRadioactivity\nRADY\nBq\ncurie\n\nRadioactivityConc\nRADONC\nBq/m3\n\n\nRatio\nRATIO\nRatio\npc ppm ppb\n\nReactivePower\nREAC\nVAreac\n\n\nResistivity\nREST\nohm/m\n\n\nRotationalStiffness\nSTFR\nN.m/rad\n\n\nSecondMomentOfArea\nSMOFA\nmetre4\n\n\nSolidAngle\nSANGL\nsteradian\n\n\nSolventPermeability\nSOPETY\nkg/m2/s/Pa\n\n\nSpecFuelelConsumptionVol\nSPFUNS\nm3/J\n\n\nSpecHeatCapacity\nSHCP\nJ/kg/K\n\n\nSpecificRadioactivity\nSPVITY\nBq/g\n\n\nSpecificSurfaceMass\nSPEASS\nm2/kg\n\n\nSpeed\nSPEE\nm/s\nknot\n\nStiffness\nSTIF\nN/m\n\n\nSubstanceQuantity\nSUBQ\nMole\nlbMole stdcubicfoot stdcubicmeters\n\nSurfaceDensity\nPSQD\nmm-2\n\n\nTemperature\nTEMP\ndegC\ndegF kelvin degRan\n\nTemperatureGradient\nTPDI\ndegC/mm\n\n\nTemperatureRate\nTEMATE\nK/s\n\n\nTemperatureVolumePerMole\nVOLPTQ\n\n\n\nThermalConductivity\nTCON\nW/m/K\n\n\nThermalExpansionCoeff\nTHENCO\ndegC-1\n\n\nThermalResistance\nTRES\nK/W\n\n\nTime\nTIME\nsecond\nmin hr day month week year\n\nTorque\nTORQ\nN.m\n\n\nUnitMass\nUMAS\nkg/mm\n\n\nViscosityDynamic\nVISC\nPa.s\npoise\n\nVolHeatTransferCoeff\nVOLEFF\nW/m3/K\n\n\nVolume\nCUDI\nmm3\nlitre ImpGal USGal bbl Mbbl MMbbl grt ImpQrt USQrt USDryQrt ImpPint USPint USDryPint ImpFloz USFloz USDryGal\n\nVolumetricFlow\nVFLO\nm3/s\nMSCubicFeetDay\n\nNone\nNONE\n\n\nnumerical real attribute\nWORD\nWORD\n\n\nused in assigning parameter dimensions etc.\nParameter\nUNIPAR\n\n\nused for parameter attributes\n\nName of Dimension\nHashCode/Word\nDatabase Units\nOther Specific Units\nComments\nAbsPressure\nABSP\npascal\nbar atm PSI torr mmHg inHg\npressure may be absolute or gauge\nAcceleration\nACCL\nm/s2\nActualPower\nACTPOW\nV.A\nAngle\nANGL\ndegree\ngrade arcmin arcsec\nAngularAcceleration\nANGCCE\nrad/s2\nAngularFrequency\nANGF\ndeg/s\nrpm rps rph angFreqHertz\nAngularMomentum\nANGM\nN.m.s\nArea\nSQDI\nmm2\nacre hectare\nAreaPerLength\nAREALE\nm2/m\nAreaPerLength\nBore\nBORE\nmm\nin\nRange of bore units limited to mm and inch (and Finch)\nCableSize\nCABL\nkcmil\ncirmil circmms\nCalorificValueMole\nCALVQ\nJ/Mol\nCalorificValueVolume\nCALVV\nJ/m3\nCapacitance\nCAPA\nfarad\nCharge\nCHAR\ncoulomb\nConductance\nCOND\nsiemens\nmho\nContent\nPCUD\nmm-3\nConvertiblePressure\nPRESC\ncpascala\ncpascalg cbarg catmg cpsig ctorrg cmmHgg cinHgg cbara catma cpsia ctorra cmmHga cinHga osia inHgaAtSixtyDegF mmHgaAtSixtyDegF inWateraAtSixtyDegF inWateraAtFourDegC ftWateraAtSixtyDegF ftWateraAtFourDegC ata\nCurrency\nCURY\nUSD\nGBP EUR\nCurrent\nCURR\nampere\nCurrentDensity\nCURITY\nA/m2\nDensity\nDENS\nkg/m3\nDensityMANDB\nMAND\nkg/mm3\ndensities stored in MANU database\nEffectiveHeatCapacity\nEFFCAP\nJ/m/K\nElectricChargeDensity\nELECSI\nC/m3\nElectricConductivity\nCNDT\nS/m\nElectricField\nEFLD\nV/m\nElectricFluxDensity\nELEFSI\nC/m2\nEMF\nEMF\nvolt\nEnergy\nENER\nkWh\njoule BTU calorie calorieit BTUit chu chuAtFifteenDegC\nEnergyDensity\nEDEN\nJ/kg\nEntropy\nENTR\nJ/K\nEquivalence\nEQUIVA\nequivalent\nEquivalenceFlow\nEQULOW\nequiv/s\nEquivalencePerVolume\nEQPRME\nequiv/m3\nFlowRateMolePerLength\nSQPTD\nMol/s/m\nFlowRateVolPerRpm\nFRVPR\nForce\nFORC\nnewton\npdl dyne kgf lbf\nFoulingFactor\nFFAC\nm2.K/W\nFrequency\nFREQ\nhertz\nfreqRpm freqRps freqRph\nGaugePressure\nGAGE\npascal\nbar atm PSI torr mmHg inHg\npressure may be absolute or gauge\nHeatCoefficientArea\nHEAREA\nW/K\nHeatFluxLinear\nHEAEAR\nW/m\nHeatingValue\nHVAL\nJ/m3\nHeatOfReaction\nHEAION\nJ/m3/h\nHeatTransferCoeff\nHTRA\nW/m2/K\nIlluminance\nILLUMI\nlux\nImpedance\nIMPE\nohm\nInductance\nINDU\nhenry\nInertia\nINER\nkg/m2\nInversePressure\nINVURE\npascal-1\nInverseTemperature\nINVRAT\nkelvin-1\nKinematicViscosity\nKVIS\nm2/s\nStoke\nLength\nDIST\nmm\nm in ft cm km mile yard micron thou angstrom\nLinearDensity\nPDIS\nmm-1\nLuminance\nLUMNCE\ncd/m2\nLuminousFlux\nLUMLUX\nlumen\nLuminousIntensity\nLUMI\nCandela\nMagFieldIntensity\nMFIN\nA/m\nMagFluxDensity\nMFXD\ntesla\nMagneticFlux\nMGFX\nweber\nMass\nMASS\nkg\ngram tonne lb oz longTon shortTon cwt longCwt shortCwt ozt grain stone\nMassFlow\nMFLO\nkg/s\nMassFlux\nMASLUX\nkg/s/m2\nMassPerArea\nMAPEA\nkg/m2\nMassPerEnergy\nMAPGY\nkg/J\nMassReactionRate\nMARETE\nkg/s/m3\nMolarConcentration\nMOLONC\nMol/m3\nMolarEntropy\nMOLOPY\nJ/Mol/K\nMolarFlow\nMOLLOW\nMol/s\nMolarMass\nMOLASS\nkg/Mol\nMolarPermeability\nMOLITY\nMolarReactionRate\nMOLATV\nMol/m3/s\nMolarReactionRateMass\nMOLATM\nMol/kg/s\nMolarVolume\nMOLUME\nm3/Mol\nMoleFluxDensity\nMOLATA\nMol/m2/s\nMolePerMass\nMOLALY\nMol/kg\nMomentum\nMOME\nN.s\nNoise\nNOIS\nDecibelA\nPermeability\nPMBT\nH/m\nPermittivity\nPMTT\nF/m\npH\nPH\npH\nPower\nPOWE\nkW\nhp watt\nPowerPerArea\nPOPEA\nW/m2\nPowerPerVolume\nPOWUME\nW/m3\nPressure\nPRES\npascal\nbar atm psi torr mmHg inHg osi inHgAtSixtyDegF mmHgAtSixtyDegF inWaterAtSixtyDegF inWaterAtFourDegC ftWaterAtSixtyDegF ftWaterAtFourDegC mmWaterAtSixtyDegF mmWaterAtFourDegC at\nPressurePerDistance\nPRPEST\nPa/m\nPressurePerTemperature\nPRPEMP\nPa/K\nPressureRate\nPREATE\nPa/s\nRadiance\nRADNCE\nRadiantIntensity\nRADITY\nW/sr\nRadiationDose\nRDOS\nsievert\nrem gray raddose\nRadioactivity\nRADY\nBq\ncurie\nRadioactivityConc\nRADONC\nBq/m3\nRatio\nRATIO\nRatio\npc ppm ppb\nReactivePower\nREAC\nVAreac\nResistivity\nREST\nohm/m\nRotationalStiffness\nSTFR\nN.m/rad\nSecondMomentOfArea\nSMOFA\nmetre4\nSolidAngle\nSANGL\nsteradian\nSolventPermeability\nSOPETY\nkg/m2/s/Pa\nSpecFuelelConsumptionVol\nSPFUNS\nm3/J\nSpecHeatCapacity\nSHCP\nJ/kg/K\nSpecificRadioactivity\nSPVITY\nBq/g\nSpecificSurfaceMass\nSPEASS\nm2/kg\nSpeed\nSPEE\nm/s\nknot\nStiffness\nSTIF\nN/m\nSubstanceQuantity\nSUBQ\nMole\nlbMole stdcubicfoot stdcubicmeters\nSurfaceDensity\nPSQD\nmm-2\nTemperature\nTEMP\ndegC\ndegF kelvin degRan\nTemperatureGradient\nTPDI\ndegC/mm\nTemperatureRate\nTEMATE\nK/s\nTemperatureVolumePerMole\nVOLPTQ\nThermalConductivity\nTCON\nW/m/K\nThermalExpansionCoeff\nTHENCO\ndegC-1\nThermalResistance\nTRES\nK/W\nTime\nTIME\nsecond\nmin hr day month week year\nTorque\nTORQ\nN.m\nUnitMass\nUMAS\nkg/mm\nViscosityDynamic\nVISC\nPa.s\npoise\nVolHeatTransferCoeff\nVOLEFF\nW/m3/K\nVolume\nCUDI\nmm3\nlitre ImpGal USGal bbl Mbbl MMbbl grt ImpQrt USQrt USDryQrt ImpPint USPint USDryPint ImpFloz USFloz USDryGal\nVolumetricFlow\nVFLO\nm3/s\nMSCubicFeetDay\nNone\nNONE\nnumerical real attribute\nWORD\nWORD\nused in assigning parameter dimensions etc.\nParameter\nUNIPAR\nused for parameter attributes\n\n\n"}
{"Headers": "Values of Physical Quantities", "Content": "A value of a real physical quantity has a numerical value (the number) and defines units of measure which are the units in which the quantity is measured. For example a distance can be 25.4mm or 1inch but regardless of the number it is the same distance because there is a known conversion factor between millimetres and inches.\nValue may be entered into the system with a unit qualifier which determines the dimension of the physical quantity and sets its value in those units.\nThe system will automatically convert from the input unit to the database unit, and from database unit to a presentation unit (for example the 'current' unit) using internally defined conversion factors. For compound units (for example,. from 'pound per square inch' to 'pascal') the conversion factors of the component units are combined together.\nThe internal conversion units used are sourced as accurately as possible. Some conversions are arithmetically exact for example, inches:mm, and SI conversions as listed by Bureau International des Poids et Mesures:\nSome conversions are experimentally determined (for example, conversion from Kg force to Newton) and precise published values are used.\nAll the values are consistent with those published, for example, by US National Institute of Standards and Technology and listed at\nWhen more accurate values greater than 7 significant figures are obtainable from other sources such as\nand elsewhere these have been used in preference.\nThere is one exception to this rule. The British Thermal Unit (BTU) which is defined by AVEVA E3D Design to be a 'typical' value of 1055.16kJ and not that defined by Fifth International Conference value of 1055.05585262kJ.\n\n\n\nhttp://physics.nist.gov/Pubs/SP811/appenB8.html\nhttp://en.wikipedia.org/wiki/Template:Convert\nhttp://physics.nist.gov/Pubs/SP811/appenB8.html\nhttp://en.wikipedia.org/wiki/Template:Convert"}
{"Headers": "Standard Units", "Content": "There are a set of standard specific units that the system will understand. Ideally the unit qualifier should be appended to the value (for example, 6.5inch) but often it can be recognized if separated from its value (for example, 6.5 inch); but not always.\nFor each unit there is an abbreviated form, a long form, and a full form (which are often identical) (for example, mm and millimeter). All can be understood including curtailed versions of the long form (for example, metre and met) always providing there are no other ambiguities. However in general, the long form will be necessary if the unit is solitary (which means. not part of a compound unit) and especially if the unit qualifier is space separated from its value.\nThe set of standard units are:\narcmin\narcmin\narcmin\nARCM\nAngle\narcsec\narcsec\narcsec\nARCS\nAngle\ndeg\ndegree\ndegree\nDEG\nAngle\ngrad\ngrad\ngrade\nGRAD\nAngle\nrad\nradian\nradian\nRAD\nAngle\nacre\nacre\nacre\nACRE\nArea\nha\nhectare\nhectare\nHECT\nArea\nF\nfarad\nfarad\nFARA\nCapacitance\nC\ncoulomb\ncoulomb\nCOUL\nCharge\nmho\nmho\nmho\nMHO\nConductance\nSi\nsiemens\nsiemens\nSIEM\nConductance\nEUR\nEUR\neuro\nEURO\nCurrency\nGBP\nGBP\nGBPound\nUKPD\nCurrency\nUSD\nUSD\nUSDollar\nUSDO\nCurrency\nA\nampere\nampere\nAMP\nCurrent\nV\nvolt\nvolt\nVOLT\nEMF\nBTU\nBTU\nBTU\nBTU\nEnergy\ncal\ncalorie\ncalorie\nCALO\nEnergy\nJ\njoule\njoule\nJOUL\nEnergy\nkWh\nkWh\nkiloWatthour\nKWH\nEnergy\ndyn\ndyne\ndyne\nFORC\nForce\nkgf\nkgf\nkgForce\nKGF\nForce\nlbf\nlbf\npoundForce\nLBF\nForce\nN\nnewton\nnewton\nNEWT\nForce\npdl\npdl\npoundal\nPDL\nForce\nHz\nhertz\nhertz\nHERZ\nFrequency\nrpm\nrpm\nrpm\nRPM\nFrequency\nohm\nohm\nohm\nOHM\nImpedance\nH\nhenry\nhenry\nHENR\nInductance\nAngst\nangstrom\nangstrom\nANGS\nLength\ncm\ncm\ncentimetre\nCM\nLength\nft\nft\nfoot\nFOOT\nLength\nin\nin\ninch\nINCH\nLength\nin\ninch\ninch\nFINC\nLength\nkm\nkm\nkilometre\nKM\nLength\nm\nmetre\nmetre\nMETR\nLength\nmicron\nmicron\nmicron\nMICR\nLength\nmile\nmile\nmile\nMILE\nLength\nmm\nmm\nmillimetre\nMM\nLength\nthou\nthou\nthou\nTHOU\nLength\nyd\nyd\nyard\nYARD\nLength\nT\ntesla\ntesla\nTESL\nMagFluxDensity\nWb\nweber\nweber\nWEBE\nMagneticFlux\ncwt\ncwt\nhundredweight\nCWT\nMass\ng\ngram\ngram\nGRAM\nMass\nkg\nkg\nkilogram\nKG\nMass\nlb\nlb\npound\nPOUN\nMass\noz\noz\nounce\nOZ\nMass\nshortTon\nshortTon\nshortTon\nSTON\nMass\nton\nlongTon\nlongTon\nTON\nMass\ntonne\ntonne\ntonne\nTONN\nMass\nhp\nhp\nhorsePower\nHP\nPower\nkW\nkW\nkiloWatt\nKWAT\nPower\nW\nwatt\nwatt\nWATT\nPower\natm\natm\natmosphere\nATM\nPressure\nbar\nbar\nbar\nBAR\nPressure\ninHg\ninHg\ninHg\nINHG\nPressure\nmmHg\nmmHg\nmmHg\nMMHG\nPressure\nPa\npascal\npascal\nPASC\nPressure\nPSI\nPSI\nPSI\nPSI\nPressure\ntorr\ntorr\ntorr\nTORR\nPressure\nGy\ngray\ngray\nGRAY\nRadiationDose\nradD\nraddose\nradDose\nRADD\nRadiationDose\nrem\nrem\nrem\nREM\nRadiationDose\nSv\nsievert\nsievert\nSIEV\nRadiationDose\nBq\nbequerel\nbequerel\nBEQU\nRadioactivity\nCi\ncurie\ncurie\nCURI\nRadioactivity\nknot\nknot\nknot\nKNOT\nSpeed\ndegC\ndegC\ndegCelsius\nCELS\nTemperature\ndegF\ndegF\ndegFahrenheit\nFAHR\nTemperature\ndegRan\ndegRan\ndegRankine\nRANK\nTemperature\nK\nkelvin\nkelvin\nKELV\nTemperature\nday\nday\nday\nDAY\nTime\nhr\nhour\nhour\nHOUR\nTime\nmin\nminute\nminute\nMINU\nTime\nmth\nmonth\nmonth\nMONT\nTime\ns\nsecond\nsecond\nSECO\nTime\nwk\nweek\nweek\nWEEK\nTime\nyr\nyear\nyear\nYEAR\nTime\nP\npoise\npoise\nPOIS\nViscosityDynamic\nImpGal\nImpGal\nImpGallon\nGALI\nVolume\nl\nlitre\nlitre\nLITR\nVolume\nUSGal\nUSGal\nUSGallon\nGALU\nVolume\nWhere there are US and SI spelling alternatives BOTH versions are supported for example litre and liter, millimetre and millimeter etc.\nThere is a significant extension of input in feet and inches (so-called FINCH format).\nA double quote (\") may be used as a unit qualifier for inch in any context (decimal inch input, or finch input).\nIn FINCH format a single quote (') is accepted as an abbreviation for feet and must be used for non format controlled input) and a double quote for inches.\nThe feet and inch value is entered using both feet and inch unit qualifiers, and the fractional part of inches can either be entered as a decimal, 5'2.125\" or as a fraction 5'2.1/8\". The inch qualifier can be any inch qualifier or none (as it is syntactically redundant).\nIf the input is controlled by a format object the foot qualifier can be any foot qualifier (ft, foot, blip) and the inch qualifier can be placed after the integer inch value OR at the end of the inch value, or omitted.\nAbbreviation\nLong Name\nFullname\nHash Code\nPhysical Dimension\narcmin\narcmin\narcmin\nARCM\nAngle\narcsec\narcsec\narcsec\nARCS\nAngle\ndeg\ndegree\ndegree\nDEG\nAngle\ngrad\ngrad\ngrade\nGRAD\nAngle\nrad\nradian\nradian\nRAD\nAngle\nacre\nacre\nacre\nACRE\nArea\nha\nhectare\nhectare\nHECT\nArea\nF\nfarad\nfarad\nFARA\nCapacitance\nC\ncoulomb\ncoulomb\nCOUL\nCharge\nmho\nmho\nmho\nMHO\nConductance\nSi\nsiemens\nsiemens\nSIEM\nConductance\nEUR\nEUR\neuro\nEURO\nCurrency\nGBP\nGBP\nGBPound\nUKPD\nCurrency\nUSD\nUSD\nUSDollar\nUSDO\nCurrency\nA\nampere\nampere\nAMP\nCurrent\nV\nvolt\nvolt\nVOLT\nEMF\nBTU\nBTU\nBTU\nBTU\nEnergy\ncal\ncalorie\ncalorie\nCALO\nEnergy\nJ\njoule\njoule\nJOUL\nEnergy\nkWh\nkWh\nkiloWatthour\nKWH\nEnergy\ndyn\ndyne\ndyne\nFORC\nForce\nkgf\nkgf\nkgForce\nKGF\nForce\nlbf\nlbf\npoundForce\nLBF\nForce\nN\nnewton\nnewton\nNEWT\nForce\npdl\npdl\npoundal\nPDL\nForce\nHz\nhertz\nhertz\nHERZ\nFrequency\nrpm\nrpm\nrpm\nRPM\nFrequency\nohm\nohm\nohm\nOHM\nImpedance\nH\nhenry\nhenry\nHENR\nInductance\nAngst\nangstrom\nangstrom\nANGS\nLength\ncm\ncm\ncentimetre\nCM\nLength\nft\nft\nfoot\nFOOT\nLength\nin\nin\ninch\nINCH\nLength\nin\ninch\ninch\nFINC\nLength\nkm\nkm\nkilometre\nKM\nLength\nm\nmetre\nmetre\nMETR\nLength\nmicron\nmicron\nmicron\nMICR\nLength\nmile\nmile\nmile\nMILE\nLength\nmm\nmm\nmillimetre\nMM\nLength\nthou\nthou\nthou\nTHOU\nLength\nyd\nyd\nyard\nYARD\nLength\nT\ntesla\ntesla\nTESL\nMagFluxDensity\nWb\nweber\nweber\nWEBE\nMagneticFlux\ncwt\ncwt\nhundredweight\nCWT\nMass\ng\ngram\ngram\nGRAM\nMass\nkg\nkg\nkilogram\nKG\nMass\nlb\nlb\npound\nPOUN\nMass\noz\noz\nounce\nOZ\nMass\nshortTon\nshortTon\nshortTon\nSTON\nMass\nton\nlongTon\nlongTon\nTON\nMass\ntonne\ntonne\ntonne\nTONN\nMass\nhp\nhp\nhorsePower\nHP\nPower\nkW\nkW\nkiloWatt\nKWAT\nPower\nW\nwatt\nwatt\nWATT\nPower\natm\natm\natmosphere\nATM\nPressure\nbar\nbar\nbar\nBAR\nPressure\ninHg\ninHg\ninHg\nINHG\nPressure\nmmHg\nmmHg\nmmHg\nMMHG\nPressure\nPa\npascal\npascal\nPASC\nPressure\nPSI\nPSI\nPSI\nPSI\nPressure\ntorr\ntorr\ntorr\nTORR\nPressure\nGy\ngray\ngray\nGRAY\nRadiationDose\nradD\nraddose\nradDose\nRADD\nRadiationDose\nrem\nrem\nrem\nREM\nRadiationDose\nSv\nsievert\nsievert\nSIEV\nRadiationDose\nBq\nbequerel\nbequerel\nBEQU\nRadioactivity\nCi\ncurie\ncurie\nCURI\nRadioactivity\nknot\nknot\nknot\nKNOT\nSpeed\ndegC\ndegC\ndegCelsius\nCELS\nTemperature\ndegF\ndegF\ndegFahrenheit\nFAHR\nTemperature\ndegRan\ndegRan\ndegRankine\nRANK\nTemperature\nK\nkelvin\nkelvin\nKELV\nTemperature\nday\nday\nday\nDAY\nTime\nhr\nhour\nhour\nHOUR\nTime\nmin\nminute\nminute\nMINU\nTime\nmth\nmonth\nmonth\nMONT\nTime\ns\nsecond\nsecond\nSECO\nTime\nwk\nweek\nweek\nWEEK\nTime\nyr\nyear\nyear\nYEAR\nTime\nP\npoise\npoise\nPOIS\nViscosityDynamic\nImpGal\nImpGal\nImpGallon\nGALI\nVolume\nl\nlitre\nlitre\nLITR\nVolume\nUSGal\nUSGal\nUSGallon\nGALU\nVolume\nNote:\n\" and ' qualifiers are NOT accepted for minutes and seconds or arc units.\n\n\n\nNote\n:"}
{"Headers": "SI Unit Prefixes", "Content": "Any unit may have an SI unit prefix preceding it which can be applied either directly (as in hectogramme) or with an intervening underscore (hecto_gramme).\nUnlike the units themselves the SI prefix cannot be abbreviated as it would introduce too much syntax ambiguity.\nMany standard units actually incorporate the SI prefix in them (mm, cm, kg) these are still standard units so it is actually (although misleadingly) possible to duplicate this as in millikg (which is, equivalent to a gram).\nThe system does not forbid use of SI prefixes with imperial units, although, this is not to be encouraged.\nThe set of prefixes supported are:\nExa\n1E+18\nPeta\n1E+15\nTera\n1E+12\nGiga\n1E+09\nMega\n1000000\nkilo\n1000\nhecto\n100\ndeca\n10\ndeci\n0.1\ncenti\n0.01\nmilli\n0.001\nmicro\n0.000001\nnano\n1E-09\npico\n1E-12\nfemto\n1E-15\n\nPrefix\nMultiplier\nExa\n1E+18\nPeta\n1E+15\nTera\n1E+12\nGiga\n1E+09\nMega\n1000000\nkilo\n1000\nhecto\n100\ndeca\n10\ndeci\n0.1\ncenti\n0.01\nmilli\n0.001\nmicro\n0.000001\nnano\n1E-09\npico\n1E-12\nfemto\n1E-15\n\n\n"}
{"Headers": "Compound Units", "Content": "Units may have powers applied by immediately appending an integer power. This is often the only way of inputting the units of some values. Limited alternative verbose forms are supported using additional words square and cubic (which can be abbreviated down to SQU and CUB). For example:\nHowever the verbose syntax will not work with all abbreviations of standard units.\nFor compound units requiring more than one unit these should be appended either using a dot (.) or a slash (/) which inverts the following power. Density, Speed and Moments can be input using forms such as:\nAgain limited verbose forms are also supported using either concentrated units or the additional word 'per' as in\nHowever whenever values are reported back the verbose forms are generally NOT used.\nIn general there is no serious limit to the complexity of compound units that may be entered.\nHowever when compound units are stored by the system, in particular when setting current working units or setting Programmable Macro Language (PML) variables, there are limitations to the complexity of compound units that can be maintained.\nNo more than 4 component units can be used.\nEach component unit can have:\nWhen there is only one component it can be one of:\nIf there are two components these are defined with:\nIf there are three components these are defined with:\nIf there are four components these are defined with:\nWhen the choice of units, powers or prefixes are restricted, the order of components may be adjusted to match a compound unit in range.\nThe named unit itself\nAn optional power of the unit (multiple and/or reciprocal)\nAn optional SI Prefix\nThe named unit itself\nThe named unit itself\nAn optional power of the unit (multiple and/or reciprocal)\nAn optional power of the unit (multiple and/or reciprocal)\nAn optional SI Prefix\nAn optional SI Prefix\nAny standard unit\n-8>power>+8\nSI Prefixes femto to Exa\nAny standard unit\nAny standard unit\n-8>power>+8\n-8>power>+8\nSI Prefixes femto to Exa\nSI Prefixes femto to Exa\nAny standard unit\n-8>power>+8\nSI Prefixes femto to Exa for first component, and milli to Mega for second\nAny standard unit\nAny standard unit\n-8>power>+8\n-8>power>+8\nSI Prefixes femto to Exa for first component, and milli to Mega for second\nSI Prefixes femto to Exa for first component, and milli to Mega for second\nAny standard unit for first components, limited to 64 common units for last\n-8>power>+8\nNO SI Prefixes\nAny standard unit for first components, limited to 64 common units for last\nAny standard unit for first components, limited to 64 common units for last\n-8>power>+8\n-8>power>+8\nNO SI Prefixes\nNO SI Prefixes\nLimited to a set of 32 common units\n-2>power>+2 except the last unit which has power range of +/-4\nNO SI Prefixes\nLimited to a set of 32 common units\nLimited to a set of 32 common units\n-2>power>+2 except the last unit which has power range of +/-4\n-2>power>+2 except the last unit which has power range of +/-4\nNO SI Prefixes\nNO SI Prefixes\nNote:\nThe limitation below is not applicable to AVEVA Administration 1.8, AVEVA Engineering 15.3 and higher.\n\n\n\nNote\n:"}
{"Headers": "Units of Absolute and Gauge (gage) Pressures", "Content": "A trailing qualifier of .abs or .gauge or .gage when added to any pressure unit will be accepted on input and in string conversion.\nA trailing \"a\" or \"g\" will be accepted on standard units (and their abbreviations) on input, and on string conversion.\nWhen gauge and absolute pressures are used in expressions they will always revert back to generic pressures. In particular there is no conversion factor applied between gauge and absolute pressures and so absolute is considered the same as generic pressures.\nThe two additional pressure dimensions are supported for absolute and gauge pressures (ABS_PRESSURE and GAUGE_PRESSURE)\nThe trailing qualifier will create a quantity with dimension of either absolute or gauge pressure.\nThis trailing component can be added to both standard units such as pascal, bar, psi, atmosphere (bar.abs) and compound units (N/m2.abs, lbf/in2.gauge).\nThe trailing qualifier will create a quantity with dimension of either absolute or gauge pressure.\nThe trailing qualifier will create a quantity with dimension of either absolute or gauge pressure.\nThis trailing component can be added to both standard units such as pascal, bar, psi, atmosphere (bar.abs) and compound units (N/m2.abs, lbf/in2.gauge).\nThis trailing component can be added to both standard units such as pascal, bar, psi, atmosphere (bar.abs) and compound units (N/m2.abs, lbf/in2.gauge).\nThe .gauge or .abs will be appended to compound units when quantities are formatted as gauge or absolute pressures.\nThe .gauge or .abs will be appended to compound units when quantities are formatted as gauge or absolute pressures.\nThe .gauge or .abs will be appended to compound units when quantities are formatted as gauge or absolute pressures.\nThe trailing g or a will create an object with dimension of either gauge or absolute pressure, for example pascala, barg, psig, Paa, Pag\nIt will be appended to standard units when quantities are formatted as gauge of absolute pressures\nThe trailing g or a will create an object with dimension of either gauge or absolute pressure, for example pascala, barg, psig, Paa, Pag\nThe trailing g or a will create an object with dimension of either gauge or absolute pressure, for example pascala, barg, psig, Paa, Pag\nIt will be appended to standard units when quantities are formatted as gauge of absolute pressures\nIt will be appended to standard units when quantities are formatted as gauge of absolute pressures\nThese can be set in format objects (both Programmable Macro Language (PML) and .Net) and used to format generic pressure quantities.\nThey can be set for User Defined Attributes (UDAs) or Properties to define values of these will always be output as gauge or absolute quantities\nThey will be able to have their own current units, distinct from generic pressure units. (similarly to DIST and BORE)\nThese can be set in format objects (both Programmable Macro Language (PML) and .Net) and used to format generic pressure quantities.\nThese can be set in format objects (both Programmable Macro Language (PML) and .Net) and used to format generic pressure quantities.\nThey can be set for User Defined Attributes (UDAs) or Properties to define values of these will always be output as gauge or absolute quantities\nThey can be set for User Defined Attributes (UDAs) or Properties to define values of these will always be output as gauge or absolute quantities\nThey will be able to have their own current units, distinct from generic pressure units. (similarly to DIST and BORE)\nThey will be able to have their own current units, distinct from generic pressure units. (similarly to DIST and BORE)\nNote:\nYou cannot apply a single \"a\" or \"g\" as this means ampere or gram!\n\n\n\nNote\n:"}
{"Headers": "Database Units", "Content": "For efficiency and consistency all attributes, whether real or pseudo, are handled by the same code within product whenever possible. Dimensioned attribute whose values are stored in the Engineering Database are always returned in Database Units, and this fact is utilized within the attribute handling code. It is therefore essential that dimensioned pseudo attributes are returned in Database units. This can be achieved simply by having:\nas the last two lines of any Programmable Macro Language (PML) function which is calculating the dimensioned pseudo attribute value.\n!result = !value.dbunits()\nreturn !result\n\n\n\n!result = !value.dbunits()\nreturn !result"}
{"Headers": "Query Attributes", "Content": "Information is provided on querying attributes and arrays, on dot notation in Programmable Macro Language (PML), on qualifiers, on relative positions, directions and orientations and on pseudo attributes.\n\n\n"}
{"Headers": "Query the List of Attributes", "Content": "The attributes available for an element will depend on its type, for example, a site will have different attributes to a branch. The lists of valid attributes can be obtained as follows:\n\n\n\nNote"}
{"Headers": "Standard Attribute Query", "Content": "An attribute value may be obtained as follows:\nSpecify the attribute name after QUERY or on the RHS of a Programmable Macro Language (PML) assignment. This will return the attribute value, if valid, for the Current Element (CE).\nVia a DBREF object using the attribute name as a method, or using the \u2018Attribute\u2019 method.\nThe querying is the same for UDAs or pseudo attributes.\nThe type of the PML variable will depend on the type of the attribute and whether it is an array or not. Attributes of INTEGER type will be assigned to a PML variable of type REAL. Attributes of type WORD are assigned to PML variable of type TEXT.\nIf the attribute is a DISTANCE attribute and current DISTANCE units are inch or finch, then the value will be converted to inches. If the attribute is a BORE attribute and current BORE units are inch or finch, then the value will be converted to inches.\nIf the attribute is a REAL attribute and it is defined to be one a physical quantity (distance, angle, mass, whose metal data UNIT is set to a dimensions such as DIST, ANGL, or MASS etc.) then the attribute is returned in the current units of that quantity.\nIf it is an attribute of volume capacity (CUDI) and the current units are derived from current distance units of INCH or FINCH the value will be reported in cubic inches.\nPML1 syntax allows an attribute to be passed to a PML variable without the \u2018=\u2019 operator. If this is done then the value will always be formatted to a TEXT using the current units if applicable.\nThe VAR command has many forms but in all cases it creates PML STRING variables, not Numbers. If the contents are values and numbers then where these are physical quantities they will be appended with the units of the values as stored in the system.\nWill store the text equivalent of the value of the XLEN attribute in current distance units.\nWill return the text string form of !!CE.XLEN. It does this by using the STRING (actually queryString) method of the (temporary) real variable created by !!CE.XLEN. The real variable will be created in current units and the STRING method will append the unit qualifier to the value output\nAttributes my be queried on other elements by using the \u2018OF\u2019 syntax.\nThe syntax following the OF may be any ID expression.\n\n\n"}
{"Headers": "Query Arrays", "Content": "If the attribute is an array, the query will return a list of values. Individual elements can be queried by passing in the index number.\nAlternatively, the NUM keyword can be used for PML 1 syntax. A range of values can be returned using the TO keyword.\nAn error will occur if attempting to query off the end of the array.\nWithin a PML1 expression, a position attribute may be queried as an array in order to access the individual coordinates.\n\n\n"}
{"Headers": "dot Notation in PML", "Content": "For reference attributes, the Programmable Macro Language (PML) dot notation can be used to achieve a similar result.\nThis will return the description of the element pointed to by the CREF attribute on the Current Element (CE).\n\n\n"}
{"Headers": "Qualifier", "Content": "Many pseudo attributes take a qualifier. The qualifier is the extra information required to make the query. Examples of where a qualifier is used are:\nThe definition of what pseudo attributes take what qualifier is described in the data model reference manual.\nThe qualifier follows the attribute name in brackets. Attribute qualifiers must be preceded by the keyword ATTNAME and element types must be preceded by the keyword TYPENAME.\nFor Programmable Macro LAnguage (PML) variables, the qualifier should be assigned to a PML array object and passed to the \u2018Attribute\u2019 method as the second argument:\nto query PPOS 1\nto query list of nominal bores:\nto query Equipment members:\n\n\n"}
{"Headers": "Relative Positions, Directions, Orientations", "Content": "Positions, Orientations, directions can be queried relative to another element using the WRT syntax.\nThe use of WRT is described more fully in the Expressions.\n\n\n\nExpressions\nExpressions"}
{"Headers": "Summary of Related Pseudo Attributes", "Content": "Pseudo attributes relating to the list of attributes.\nATTLIST\nWORD(300)\n\nList of all visible attributes for element\nPSATTS\nWORD(500)\n\nList of pseudo attributes\nUDALIS\nWORD(300)\n\nList of UDAs\nUDASET\nWORD(300)\n\nList of UDAs set\nPseudo attributes relating to the name.\nCUTNAM\nSTRING(700)\nNUMBER\nFull name of element, truncated to n characters\nCUTNMN\nSTRING(700)\nNUMBER\nFull name of element (without leading slash) truncated to n characters\nFLNM\nSTRING(700)\n\nFull name of the element\nFLNN\nSTRING(700)\n\nFull name of the element (without leading slash)\nISNAMED\nBOOL\n\nTrue if element is named\nNAMESQ\nSTRING(700)\n\nType. sequence number and name of element\nNAMETY\nSTRING(700)\n\nType and name of the element\nNAMN\nSTRING(500)\n\nName of the element (without leading slash)\nNAMTYP\nSTRING(700)\n\nType and full name of element\nPseudo attributes relating to the type.\nACTTYPE\nWORD\n\nType of the element, ignoring UDET, truncated to 4 or 6 characters.\nAHLIS\nWORD(200)\n\nList of actual types in owning hierarchy\nOSTYPE\nWORD\n\nShort cut for \"Type of owner\"\nTYPE\nWORD\n\nType of the element, ignoring UDET, truncated to 4 or 6 characters\n\nAttribute Name\nData Type\nQualifier\nDescription\nATTLIST\nWORD(300)\nList of all visible attributes for element\nPSATTS\nWORD(500)\nList of pseudo attributes\nUDALIS\nWORD(300)\nList of UDAs\nUDASET\nWORD(300)\nList of UDAs set\nAttribute Name\nData Type\nQualifier\nDescription\nCUTNAM\nSTRING(700)\nNUMBER\nFull name of element, truncated to n characters\nCUTNMN\nSTRING(700)\nNUMBER\nFull name of element (without leading slash) truncated to n characters\nFLNM\nSTRING(700)\nFull name of the element\nFLNN\nSTRING(700)\nFull name of the element (without leading slash)\nISNAMED\nBOOL\nTrue if element is named\nNAMESQ\nSTRING(700)\nType. sequence number and name of element\nNAMETY\nSTRING(700)\nType and name of the element\nNAMN\nSTRING(500)\nName of the element (without leading slash)\nNAMTYP\nSTRING(700)\nType and full name of element\nAttribute Name\nData Type\nQualifier\nDescription\nACTTYPE\nWORD\nType of the element, ignoring UDET, truncated to 4 or 6 characters.\nAHLIS\nWORD(200)\nList of actual types in owning hierarchy\nOSTYPE\nWORD\nShort cut for \"Type of owner\"\nTYPE\nWORD\nType of the element, ignoring UDET, truncated to 4 or 6 characters\n\n\n"}
{"Headers": "Set Attributes", "Content": "Information is provided on the standard and special syntax, resetting user defined attributes (UDAs) to default, setting arrays, values of arrays and related pseudo attributes.\n\n\n"}
{"Headers": "Standard Syntax", "Content": "Attribute values can be set in two ways:\nThe following general rules must be followed:\nThe behaviour for each attribute type is described below:\nREAL attribute - allows an int, real or real expression\nINTEGER attribute - allows an int, a real or real expression. The result will be rounded to the nearest integer.\nTEXT attribute - allows a text value, a text expression, or UNSET. Assigning UNSET will result in a zero length string.\nLOGICAL attribute - allows FALSE, TRUE or logical expression.\nREF attribute - allows a name, refno, ID expression, or UNSET, NULREF keywords. The UNSET and NULREF keywords both result in a null reference (=0/0) being assigned.\nWORD attribute - If assigning to a PML variable, then allows a text value or text expression.\nIf assigning via the attribute name, then it must be a word.\nPOSITION attribute - allows a position or position expression.\nDIRECTION attribute - Allows a direction or direction expression\nORIENTATION attribute - Allows an orientation or an orientation expression\nThe value being assigned to an attribute must either be dimensionally equivalent to the attribute, or else a numerical value (which is taken to be in current working units of the dimension). If there is a clash of physical quantity an error will occur. The following will all generate errors.\nThe value assigned must be the correct type for the attribute type (see examples below)\nPML variables can not be directly used if using method (2). The PML variable must be expanded using the late evaluation syntax, i.e. \u2018XLEN !A\u2019 is invalid but \u2018XLEN $!A\u2019 is OK. This also applies to any PML variables within expressions.\nThe value assigned must be the correct type for the attribute type (see examples below)\nThe value assigned must be the correct type for the attribute type (see examples below)\nPML variables can not be directly used if using method (2). The PML variable must be expanded using the late evaluation syntax, i.e. \u2018XLEN !A\u2019 is invalid but \u2018XLEN $!A\u2019 is OK. This also applies to any PML variables within expressions.\nPML variables can not be directly used if using method (2). The PML variable must be expanded using the late evaluation syntax, i.e. \u2018XLEN !A\u2019 is invalid but \u2018XLEN $!A\u2019 is OK. This also applies to any PML variables within expressions.\nNote:\nThere must be a space between the name and the \u2018)\u2019\nNote:\nThe POS attribute can not be set by name, use AT syntax instead.\nDo not use brackets if setting by attribute name.\nNote:\nDo not use brackets if setting by attribute name.\nNote:\nDo not use brackets if setting by attribute name.\n\n\n\nNote\n:\nNote\n:\nNote\n:\nNote\n:\nNote\n:"}
{"Headers": "Set a UDA Back to a Default", "Content": "A UDA may be set back to it\u2019s default by using the DEFAULT keyword.\n\n\n"}
{"Headers": "Set an Array", "Content": "If assigning via a Programmable Macro Language (PML) variable, an array attribute must be assigned from a PML array object.\nIf assigning via the attribute name, then a list of values must be given.\n\n\n"}
{"Headers": "Single Value of an Array", "Content": "If assigning via a PML variable, an index number may be specified in square brackets.\nIf assigning via the attribute name, a single value of an array may be set using the NUMB keyword. The NUMB keyword follows the attribute name, and is followed by the index number.\nThis sets the 2nd value of the array to 99.\nThe NUMB command actually specifies the start point for a list of values.\nThis would set the 3rd value to 99, the 4th to 100 and the 5th to 101.\nThe new values may go off the end of the existing array, but the start point must not be more than one beyond the existing end point.\n\n\n"}
{"Headers": "Special Syntax for Names", "Content": "All elements except the WORLD can be named. Although Design elements are often given suitable names while being created, later name changes can be made by giving a new name or by removing the old name. The name of any element must be unique; that is, not already used for another currently accessible element.\nNAME /ZONE5D\nThe current element is given the specified name provided it has not been used elsewhere.\nUNN\nThe current element loses its name (it is still identifiable by its automatically allocated reference number).\nThe name of the current element and offspring can be modified where a standard name part occurs.\nREN ALL /Z1 /Z2\nAll occurrences of /Z1 in the names of the current element and its offspring will be changed to /Z2.\nExamples\nNAME /ZONE5D\nThe current element is given the specified name provided it has not been used elsewhere.\nUNN\nThe current element loses its name (it is still identifiable by its automatically allocated reference number).\nExample\nREN ALL /Z1 /Z2\nAll occurrences of /Z1 in the names of the current element and its offspring will be changed to /Z2.\n>-- NAMe --+-- ALL name name --.\n           |                   |\n           \u2018-- name -----------+-->\n>-- UNName -->\n   \n>-- REName --+-- ALL name name --.\n             |                   |\n             \u2018-- name -----------+-->\n\n\n\nNAME /ZONE5D\nUNN\nREN ALL /Z1 /Z2\nname name\nname"}
{"Headers": "Special Syntax for LOCK", "Content": "Locking a design element prevents it from being modified or deleted. The LOCK command allows either a single element to be controlled, or all its offspring too. (A complete Site can be locked if required.) This provides you with personal security control over your area of work. (General security restrictions affecting the whole Project are established in the Admin module of AVEVA E3D Design.)\nLOCK ALL\nThe current element and all its offspring are locked.\nUNLOCK\nThe current element is unlocked.\nExamples\nLOCK ALL\nThe current element and all its offspring are locked.\nUNLOCK\nThe current element is unlocked.\n>--+-- LOCK ----.\n   |            |\n   \u2018-- UNLOck --+-- ALL --.\n                |         |\n                \u2018---------+-- <snoun> --.\n                          |             |\n                          \u2018-------------+-->\n\n\n\nLOCK ALL\nUNLOCK"}
{"Headers": "Related Pseudo Attributes", "Content": "DACMOD\nBOOL\nATTR\nTrue if DAC allows attribute of element to be modified\nMODATT\nBOOL\nATTR\nTrue if attribute of element can be modified\nMODERR\nSTRING(120)\nATTR\nReturns the error text that would occur if attribute was modified\n\nAttribute Name\nData Type\nQualifier\nDescription\nDACMOD\nBOOL\nATTR\nTrue if DAC allows attribute of element to be modified\nMODATT\nBOOL\nATTR\nTrue if attribute of element can be modified\nMODERR\nSTRING(120)\nATTR\nReturns the error text that would occur if attribute was modified\n\n\n"}
{"Headers": "PML Attribute Class", "Content": "Information is provided on the creation of attribute classes and the creation methods.\n\n\n"}
{"Headers": "Creation", "Content": "A Programmable Macro Language (PML) attribute instance may be created for a system attribute or a User defined Attribute (UDA).\nThe class should not be confused with the attribute value. The actual Attribute value for a particular Element can only be accessed via the DBREF class or via the QUERY command. Comparing two Attributes just compares whether they identify the same attribute, the comparison does not look at attribute values in any way.\n\n\n"}
{"Headers": "Methods", "Content": "The Attribute instance can then be used for querying the \u2018meta data\u2019, that means, data about data. The methods of the class allow the following to be queried.\nString Type()\nAttribute type\nString Name()\nAttribute name\nString Description()\nAttribute description\nInt Hash()\nAttribute hash value\nint Length()\nAttribute length\nbool IsPseudo()\nWhether pseudo or not\nbool IsUda()\nWhether a User defined Attributes (UDA) or not\nstring querytext()\nAs output at the command line when querying attribute\nstring units\nEither BORE, DISTANCE or NONE\nReturns the unit field of the attribute which is the string of the hash code of the dimension of the attribute (BORE, DIST, MASS, ANGL, or for numbers of no physical quantity NONE). For UDAs it is the value of the UDA Type (UTYP) attribute.\nbool Noclaim()\nWhether attribute can be changed without doing a claim\nElementType array\nElementTypes\nList of Elements for which the attribute is valid. This only works for UDAs\nReal array limits\nMin/Max values for real/int types\nString array\nValidValues(ElementType)\nList of valid for text attributes. The list may vary with element type\nstring DefaultValue\n(ElementType)\nAttribute default. This only works for UDAs\nstring Category()\nDetermines the grouping of attributes on the \u2018Attribute Utility\u2019 form\nbool hyperlink()\nif true then the attribute value refers to an external file\nbool connection()\nif true then the attribute value will appear on the reference list form\nbool hidden()\nIf true then attribute will not appear on the Attribute utility form or after \u2018Q ATT\u2019\nbool protected()\nif true then attribute is not visible if a protected Databases (DB).\nString Type()\nAttribute type\nString Name()\nAttribute name\nString Description()\nAttribute description\nInt Hash()\nAttribute hash value\nint Length()\nAttribute length\nbool IsPseudo()\nWhether pseudo or not\nbool IsUda()\nWhether a User defined Attributes (UDA) or not\nstring querytext()\nAs output at the command line when querying attribute\nstring units\nEither BORE, DISTANCE or NONE\nReturns the unit field of the attribute which is the string of the hash code of the dimension of the attribute (BORE, DIST, MASS, ANGL, or for numbers of no physical quantity NONE). For UDAs it is the value of the UDA Type (UTYP) attribute.\nbool Noclaim()\nWhether attribute can be changed without doing a claim\nElementType array\nElementTypes\nList of Elements for which the attribute is valid. This only works for UDAs\nReal array limits\nMin/Max values for real/int types\nString array\nValidValues(ElementType)\nList of valid for text attributes. The list may vary with element type\nstring DefaultValue\n(ElementType)\nAttribute default. This only works for UDAs\nstring Category()\nDetermines the grouping of attributes on the \u2018Attribute Utility\u2019 form\nbool hyperlink()\nif true then the attribute value refers to an external file\nbool connection()\nif true then the attribute value will appear on the reference list form\nbool hidden()\nIf true then attribute will not appear on the Attribute utility form or after \u2018Q ATT\u2019\nbool protected()\nif true then attribute is not visible if a protected Databases (DB).\nString Type()\nAttribute type\nString Name()\nAttribute name\nString Description()\nAttribute description\nInt Hash()\nAttribute hash value\nint Length()\nAttribute length\nbool IsPseudo()\nWhether pseudo or not\nbool IsUda()\nWhether a User defined Attributes (UDA) or not\nstring querytext()\nAs output at the command line when querying attribute\nstring units\nEither BORE, DISTANCE or NONE\nReturns the unit field of the attribute which is the string of the hash code of the dimension of the attribute (BORE, DIST, MASS, ANGL, or for numbers of no physical quantity NONE). For UDAs it is the value of the UDA Type (UTYP) attribute.\nbool Noclaim()\nWhether attribute can be changed without doing a claim\nElementType array\nElementTypes\nList of Elements for which the attribute is valid. This only works for UDAs\nReal array limits\nMin/Max values for real/int types\nString array\nValidValues(ElementType)\nList of valid for text attributes. The list may vary with element type\nstring DefaultValue\n(ElementType)\nAttribute default. This only works for UDAs\nstring Category()\nDetermines the grouping of attributes on the \u2018Attribute Utility\u2019 form\nbool hyperlink()\nif true then the attribute value refers to an external file\nbool connection()\nif true then the attribute value will appear on the reference list form\nbool hidden()\nIf true then attribute will not appear on the Attribute utility form or after \u2018Q ATT\u2019\nbool protected()\nif true then attribute is not visible if a protected Databases (DB).\nNote:\nWe do yet not support direct usage of this class in other syntax.\n\n\n\nString Type()\nString Name()\nString Description()\nInt Hash()\nint Length()\nbool IsPseudo()\nbool IsUda()\nstring querytext()\nstring units\nbool Noclaim()\nElementType array\nElementTypes\nReal array limits\nString array\nValidValues(ElementType)\nstring DefaultValue\n(ElementType)\nstring Category()\nbool hyperlink()\nbool connection()\nbool hidden()\nbool protected()\nNote\n:"}
{"Headers": "PML ElementType Class", "Content": "Information is provided on creating element type classes using PML, on the methods and on the related pseudo attributes.\n\n\n"}
{"Headers": "Creation", "Content": "An ElementType instance may be created for a system Element type or a User Defined Element Type (UDET).\nThe ElementType instance can then be used for querying the \u2018meta data\u2019. which means,. data about data. The methods of the class allow the following to be queried.\n\n\n"}
{"Headers": "Methods", "Content": "The available methods are:\nstring Name()\nName of element type\nstring Description()\nDescription of element type\nint Hash()\nHash value\nbool IsUdet()\nWhether a User Defined Element Type (UDET) or not\nAttribute array\nsystemAttributes()\nList of system attributes (excludes User defined Attributes (UDAs))\nstring array DbType()s\nList of valid Database (DB) types\nstring ChangeType()\nIndicates if an element of this type may have it\u2019s type changed\nElementType SystemType()\nfor UDETs this is the base type\nElementType array\nUDETs derived from this type\nbool Primary()\nWhether the element is primary or not\nElementType array\nMemberTypes()\nValid members, including UDETs\nElementType array\nParentTypes()\nValid parents, including UDETs\nstring Name()\nName of element type\nstring Description()\nDescription of element type\nint Hash()\nHash value\nbool IsUdet()\nWhether a User Defined Element Type (UDET) or not\nAttribute array\nsystemAttributes()\nList of system attributes (excludes User defined Attributes (UDAs))\nstring array DbType()s\nList of valid Database (DB) types\nstring ChangeType()\nIndicates if an element of this type may have it\u2019s type changed\nElementType SystemType()\nfor UDETs this is the base type\nElementType array\nUDETs derived from this type\nbool Primary()\nWhether the element is primary or not\nElementType array\nMemberTypes()\nValid members, including UDETs\nElementType array\nParentTypes()\nValid parents, including UDETs\nstring Name()\nName of element type\nstring Description()\nDescription of element type\nint Hash()\nHash value\nbool IsUdet()\nWhether a User Defined Element Type (UDET) or not\nAttribute array\nsystemAttributes()\nList of system attributes (excludes User defined Attributes (UDAs))\nstring array DbType()s\nList of valid Database (DB) types\nstring ChangeType()\nIndicates if an element of this type may have it\u2019s type changed\nElementType SystemType()\nfor UDETs this is the base type\nElementType array\nUDETs derived from this type\nbool Primary()\nWhether the element is primary or not\nElementType array\nMemberTypes()\nValid members, including UDETs\nElementType array\nParentTypes()\nValid parents, including UDETs\nNote:\nWe do yet not support direct usage of this class in other syntax.\n\n\n\nstring Name()\nstring Description()\nint Hash()\nbool IsUdet()\nAttribute array\nsystemAttributes()\nstring array DbType()s\nstring ChangeType()\nElementType SystemType()\nElementType array\nbool Primary()\nElementType array\nMemberTypes()\nElementType array\nParentTypes()\nNote\n:"}
{"Headers": "Related Pseudo Attributes", "Content": "There are a number of pseudo attributes that return values according to the element type, as follows:\nHLIS\nWORD(2000)\n\nList of all possible types in owning hierarchy\nLIST\nWORD(2000)\n\nList of all possible member types\nLLIS\nWORD(2000)\n\nList of all possible types in member hierarchy\nOLIS\nWORD(2000)\n\nList of all possible owner types\nREPTXT\nSTRING\n\nReporter text used for element type\n\n\nAttribute Name\nData Type\nQualifier\nDescription\nHLIS\nWORD(2000)\nList of all possible types in owning hierarchy\nLIST\nWORD(2000)\nList of all possible member types\nLLIS\nWORD(2000)\nList of all possible types in member hierarchy\nOLIS\nWORD(2000)\nList of all possible owner types\nREPTXT\nSTRING\nReporter text used for element type\n\n\n"}
{"Headers": "Database Modification", "Content": "This chapter describes the commands to create, copy and modify database elements.\n\n\n"}
{"Headers": "Modify the Content of a DB", "Content": "As well as accessing the current content of a Database (DB), you may also (if you have Read/Write access rights) modify a DB in any of the following ways:\nCreate a new element at an appropriate level of the DB hierarchy; refer to Create a New Element.\nDelete an element from the DB hierarchy; refer to Delete an Element.\nReorganize the hierarchy, refer to Reorganize the DB Hierarchy:\nby rearranging members of an element into a different list order.\nby moving an element from one part of the hierarchy to another;\nDefine the attributes and offspring of a new element by copying the corresponding attribute, settings and member lists from another element; refer to Copy Attributes from One Element to Another.\nCreate a new element at an appropriate level of the DB hierarchy; refer to Create a New Element.\nCreate a new element at an appropriate level of the DB hierarchy; refer to Create a New Element.\nDelete an element from the DB hierarchy; refer to Delete an Element.\nDelete an element from the DB hierarchy; refer to Delete an Element.\nReorganize the hierarchy, refer to Reorganize the DB Hierarchy:\nby rearranging members of an element into a different list order.\nby moving an element from one part of the hierarchy to another;\nReorganize the hierarchy, refer to Reorganize the DB Hierarchy:\nDefine the attributes and offspring of a new element by copying the corresponding attribute, settings and member lists from another element; refer to Copy Attributes from One Element to Another.\nDefine the attributes and offspring of a new element by copying the corresponding attribute, settings and member lists from another element; refer to Copy Attributes from One Element to Another.\n\n\n\nCreate a New Element\nDelete an Element\nReorganize the DB Hierarchy\nCopy Attributes from One Element to Another\nCreate a New Element\nDelete an Element\nReorganize the DB Hierarchy\nCopy Attributes from One Element to Another"}
{"Headers": "Create a New Element", "Content": "To create a new element within an existing Database (DB), you must first make sure that the Current Element (CE) is at a level within the hierarchy which can legally own the element to be created. For example, a Site can own a Zone, but it cannot own a Valve. To create a new Valve, you must be at Branch level. You must therefore navigate to the correct level by using one of the command options described in Database Navigation and Query Syntax.\nYou can then create a new element, set its attributes and, if required, create further elements as its members.\nIf you create an element without explicitly identifying its position in the Member List of the Current Element, the new element is inserted immediately after the Current List Position. To use this option, enter the command\nNEW element_type element_name\n(element_name is optional)\nNEW element_type element_name\n(element_name is optional)\nFor example, if the Current List Position is at member 4 (/VALV1) of the Member List.\n\nThe command\nadds a new Tee at list position 5 (between /VALV1 and /ELBO2) and names it /TEE2. The Member List of /BRAN1 thus becomes\n\nTo insert the new Tee as the first or last component in the Member List, access the Branch Head or Tail, respectively, before giving the NEW TEE command.\nTo create a new element at a specified list position, identify a list position adjacent to the required position and state which side of it the newly-created element is to go. The command syntax is one of the following:\nwhere element_name is again optional and where list_position may be specified in any of the ways described in Database Navigation and Query Syntax.\nConsider the following examples. Starting from the configuration shown, any of these commands creates a new Tee between /ELBO3 (list position 7) and /FLAN2 (list position 8):\nNEW TEE AFTER /ELBO3\nSpecify name or refno\nNEW TEE BEFORE 8\nSpecify list position number\nNEW TEE BEFORE FLAN 2\nSpecify member type and number (second Flange in the list)\nNEW TEE AFTER LAST ELBO\nSpecify first or last member of a given type (last Elbow in the list)\nNEW TEE AFTER NEXT 3\nSpecify position relative to Current List Position\nNEW TEE BEFORE LAST FLAN\nSpecify first or last member of a given type\nNEW TEE AFTER /ELBO3\nSpecify name or refno\nNEW TEE BEFORE 8\nSpecify list position number\nNEW TEE BEFORE FLAN 2\nSpecify member type and number (second Flange in the list)\nNEW TEE AFTER LAST ELBO\nSpecify first or last member of a given type (last Elbow in the list)\nNEW TEE AFTER NEXT 3\nSpecify position relative to Current List Position\nNEW TEE BEFORE LAST FLAN\nSpecify first or last member of a given type\nThe new Tee, which is unnamed, becomes list member 7, /ELBO3 becomes list member 8, /FLAN2 becomes list member 9, and so on.\nTo create a new top level element in a specific database there is a DB keyword available in the syntax of the \u2018NEW\u2019 command as follows:\nNEW element_type element_name DB database_name\nwhere element_name is again optional and where the database_name is expressed as a fully qualified database name,for example, team/database.\nThe following command will create a new SITE named /MYSITE in the MYTEAM/MYDB database.\nNEW element_type element_name\n(element_name is optional)\nNEW TEE AFTER /ELBO3\nSpecify name or refno\nNEW TEE BEFORE 8\nSpecify list position number\nNEW TEE BEFORE FLAN 2\nSpecify member type and number (second Flange in the list)\nNEW TEE AFTER LAST ELBO\nSpecify first or last member of a given type (last Elbow in the list)\nNEW TEE AFTER NEXT 3\nSpecify position relative to Current List Position\nNEW TEE BEFORE LAST FLAN\nSpecify first or last member of a given type\nNEW TEE /TEE2\nNEW    element_type element_name BEFore list_position\nNEW    element_type element_name AFTer list_position\nNEW SITE /MYSITE DB MYTEAM/MYDB\nNote:\nThe Q LIST query will tell you which element types you can create as members of the Current Element.\n\n\n\nDatabase Navigation and Query Syntax\nDatabase Navigation and Query Syntax\nDatabase Navigation and Query Syntax\nNote\n:\nNEW element_type element_name\nDatabase Navigation and Query Syntax\nNEW TEE AFTER /ELBO3\nNEW TEE BEFORE 8\nNEW TEE BEFORE FLAN 2\nNEW TEE AFTER LAST ELBO\nNEW TEE AFTER NEXT 3\nNEW TEE BEFORE LAST FLAN\nNEW\nelement_type element_name\nDB\ndatabase_name\nelement_name\ndatabase_name\nteam/database"}
{"Headers": "Delete an Element", "Content": "You can delete either the entire Current Element or some or all of its offspring. When you delete the Current Element, you also delete all of its offspring (that is, its members, their members, etc.) from the hierarchy. The command must therefore be used with care. When an element has been deleted, its Owner becomes the new Current Element.\nAs a safeguard against accidental deletion of parts of a DB, the deletion function operates only on the Current Element. As further safeguards, the DELETE command word must be entered in full and the command syntax requires that you confirm the generic type of the Current Element. Furthermore, access to the required element and its subsequent deletion must be specified in two separate command lines.\nTo delete the Current Element and all its offspring, enter\nFor example, to delete a Nozzle, make the Nozzle the Current Element and then enter\nThe Equipment which owned the Nozzle becomes the Current Element.\nTo delete a complete Zone, including all Equipment, Piping, Structures etc. owned by it, make the Zone the Current Element and then enter\nThe Site which owned the deleted Zone becomes the Current Element.\nTo delete only specified members of the Current Element, use one of the following forms of the command syntax:\nDELETE element_type MEMbers\n(deletes all members)\nDELETE element_type MEMbers integer\n(deletes one member)\nDELETE element_type MEMbers integer TO integer\n(deletes a range of members)\n(deletes all members)\n(deletes one member)\n(deletes a range of members)\nConsider the following examples, where the Current Element is /BRAN1 with the Member List illustrated in Figure 10-2:\nDELETE BRAN MEMBERS\nDeletes all components from the Branch, leaving only the Branch Head and Tail\nDELETE BRAN MEMBER 6\nDeletes only /TEE1\nDELETE BRAN MEMBERS 5 TO 7\nDeletes /ELBO2, /TEE1 and /ELBO3\nDeletes all components from the Branch, leaving only the Branch Head and Tail\nDeletes only /TEE1\nDeletes /ELBO2, /TEE1 and /ELBO3\n\nDELETE element_type MEMbers\n(deletes all members)\nDELETE element_type MEMbers integer\n(deletes one member)\nDELETE element_type MEMbers integer TO integer\n(deletes a range of members)\nDELETE BRAN MEMBERS\nDeletes all components from the Branch, leaving only the Branch Head and Tail\nDELETE BRAN MEMBER 6\nDeletes only /TEE1\nDELETE BRAN MEMBERS 5 TO 7\nDeletes /ELBO2, /TEE1 and /ELBO3\nDELETE NOZZ\nDELETE ZONE\n\n\n\nDELETE\nDELETE element_type MEMbers\nDELETE element_type MEMbers integer\nDELETE element_type MEMbers integer TO integer\nDELETE BRAN MEMBERS\nDELETE BRAN MEMBER 6\nDELETE BRAN MEMBERS 5 TO 7"}
{"Headers": "Reorganize the DB Hierarchy", "Content": "You can reorganize the structure of the Database (DB) hierarchy, without elements being added to or removed from its contents, in either of two ways:\nIn both cases elements and their offspring are transferred to new positions in the hierarchy. In the first case the element's owner remains unchanged, while in the second case the element's owner changes.\nTo rearrange the Member List of the Current Element (CE), use one of the commands:\nwhere element_id specifies an element which is to be moved (which must be a member of the Current Element) and where list_position may be specified in any of the ways described in Database Navigation and Query Syntax.\nIf list_position is omitted, the intended position is assumed to be immediately after the Current List Position.\nFor example, starting with the previous Member List:\n\nThe command\nmoves /ELBO3 to position 5, immediately following the Current List Position, giving the new Member List\n\nStarting from either of the above configurations, the command\nmoves /ELBO3 to position 3, immediately before /ELBO1, thus\n\nTo insert an existing element into the Member List of the Current Element, when it is not already a member of that list, use one of the commands\nwhere element_id specifies an element which is to be moved (which may be anywhere within the DB hierarchy as long as it is at an appropriate level) and where list_position may be specified in any of the ways described in Database Navigation and Query Syntax.\nIf list_position is omitted, the intended position is assumed to be immediately after the Current List Position.\nFor example, starting with the simple hierarchy\n\nthe command\nmoves /PIPE2 (and all its offspring) to the position immediately following the Current List Position. Ownership of /PIPE2 passes from /ZONE2 to /ZONE1, resulting in the new hierarchy\n\nREOrder element_id\nREOrder element_id  BEFore list_position\nREOrder element_id  AFTer  list_position\nREORDER /ELBO3\nREORDER    /ELBO3   BEFORE   FIRST   ELBO\nINCLude element_id\nINCLude element_id  BEFore list_position\nINCLude element_id  AFTer  list_position\nINCLUDE /PIPE2\nBy rearranging the order of the Member List of a single element\nBy relocating an element to a different part of the hierarchy\nBy rearranging the order of the Member List of a single element\nBy rearranging the order of the Member List of a single element\nBy relocating an element to a different part of the hierarchy\nBy relocating an element to a different part of the hierarchy\n\n\n\nDatabase Navigation and Query Syntax\nDatabase Navigation and Query Syntax\nDatabase Navigation and Query Syntax\nLude element_id\nINCLude element_id  BEFore list_position\nINCLude element_id  AFTer  list_position\nDatabase Navigation and Query Syntax"}
{"Headers": "Copy Attributes from One Element to Another", "Content": "It is often convenient to create a new element as a copy of an existing element which has the same, or similar, attribute settings or members to those required. You do this in two stages:\nWhen an element is 'cloned' in this way, all attributes are copied from the source element to the target element except NAME (which must be unique) and LOCK (which is always unlocked in the target element). Additionally, and this is what makes the facility so powerful, all offspring of the source element are copied as offspring of the target element.\nYou may specify automatic renaming of the Current Element and its offspring as part of the copying process. Without this the new elements will be unnamed, since AVEVA E3D Design does not permit two elements in the same Database (DB) hierarchy to have identical names. You may also choose to copy only the members (and their offspring) of the source element, leaving the attributes of the Current Element itself unchanged.\nTo copy a complete element and all of its offspring, after creating a new Current Element of an appropriate type, enter\nwhere element_id identifies the source element to be copied.\nFor example, to create a new item of Equipment which is an exact replica of a previously-defined Equipment, you might use the command sequence (at Zone level)\nThis creates /EQUIPB as the Current Element and then turns it into an exact copy of /EQUIPA. All attributes and members of /EQUIPB now have the same settings as those of /EQUIPA, including its position, orientation etc., and so you will probably now want to move one of the Equipments to a different location.\nTo copy all offspring of an element, so that they create duplicate offspring for the Current Element, enter\nThe position, orientation, etc., of the Current Element now remain unchanged, but it acquires new members which are derived from the specified source element and which are correctly positioned relative to the Current Element.\nTo copy selected offspring of an element, so that they create duplicate offspring for the Current Element, enter\nFor example, the command sequence\ncreates a new Branch named /SIDEARM whose components replicate that part of the existing Branch /MAINLINE between the specified list positions. The attributes of the Branch /SIDEARM itself are unaffected by the COPY command, so that its position, orientation, etc. (as defined by its Head and Tail settings) remain unchanged by the addition of its new members.\nTo copy attributes from an identified element into the current element, type\nThis causes all attributes (except for references to elements in DESI databases and OWNER) to be copied to the current element. Or:\nThis is similar to the ATTRIBUTES option, except that as well as DESI references not being copied, neither are any position, direction, orientation or angle attributes.\nIn both cases, the Specification Reference (SPREF) and Catalog Reference (CATREF) are also not copied between elements of different types.\nTo copy elements alongside their original positions, type\nThis option causes a list of elements, defined by the selection criterion select, to be copied alongside their original positions in the database. So if the list includes a SCTN and a PNOD (for example) then each of these items would be copied so that the new SCTN shares the same owner as the old SCTN and the new PNOD shares the same owner as the old PNOD. As this option copies elements, rather than just attributes, other COPY options, such as RENAME, are valid.\nTo copy all or part of an element and rename the copies, append the command\nto the corresponding COPY command line.\nFor example, the command\ncopies all attributes and offspring of /FRACT1/PIPE into the Current Element. Where /FRACT1 occurs as the name or part of the name, it is changed to /FRACT2 in the Current Element and its offspring. Thus the Current Element itself is now named /FRACT2/PIPE, and so on.\nDACCOH\nBOOL\n\nTrue if DAC allows element hierarchy to be copied to another DB\nDACCOP\nBOOL\n\nTrue if DAC allows element to be copied to another DB\nDACCRE\nBOOL\nNOUN\nTrue if DAC allows element to be created\nDACDEL\nBOOL\n\nTrue if DAC allows element to be deleted\nDACERR\nSTRING(120)\nATTR\nReturns the DAC error\nMODATT\nBOOL\nATTR\nTrue if attribute of element can be modified\nMODDEL\nBOOL\nATTR\nTrue if element can be deleted\n\nAttribute Name\nData Type\nQualifier\nDescription\nDACCOH\nBOOL\nTrue if DAC allows element hierarchy to be copied to another DB\nDACCOP\nBOOL\nTrue if DAC allows element to be copied to another DB\nDACCRE\nBOOL\nNOUN\nTrue if DAC allows element to be created\nDACDEL\nBOOL\nTrue if DAC allows element to be deleted\nDACERR\nSTRING(120)\nATTR\nReturns the DAC error\nMODATT\nBOOL\nATTR\nTrue if attribute of element can be modified\nMODDEL\nBOOL\nATTR\nTrue if element can be deleted\nCOPY element_id\nNEW EQUI /EQUIPB\nCOPY /EQUIPA\nCOPY MEMbers OF element_id\nCOPY MEMbers integer TO integer OF element_id\nNEW BRAN /SIDEARM\nCOPY MEMBERS 12 TO 20 OF /MAINLINE\nCOPY ATTributes OF element_id\nCOPY LIKE element_id\nCOPY ADJ/ACENT select\n... REName    old_name   new_name\nCOPY  /FRACT1/PIPE  RENAME  /FRACT1  /FRACT2\nNote:\nIf the Current Element already has members, it is not possible to make it a copy of another element in this way.\n\n\n\nCreate a New Element\nCreate a New Element\nNote\n:"}
{"Headers": "Save Work and Get Work", "Content": "SAVEWORK saves the current Model changes without leaving Model. It is good practice to use this command on a regular basis during a long session to make sure maximum data security.\nAs well as a comment, an optional number n can be used to specify a particular database for the command. The number is the number of the database in the order output by the STATUS command (refer to Project). If no number is given, the SAVEWORK applies to the whole Multiple Database (MDB). An example of Savework syntax is SAVEWORK \u2018comment\u2019 1.\nGETWORK refreshes the view of all READ databases to pick up any changes that other users may have made since you first opened them. The optional n works in the same way as for SAVEWORK. You would normally only use GETWORK if you know of specific changes you wish to pick up and use. Please note that GETWORK slows up subsequent database access, as the information has to be re-read from disk. Therefore, you should use this command sparingly.\n\n\n\nProject\nn\nProject\nn"}
{"Headers": "Sessions", "Content": "Each time you enter Model or save your design changes, a new session is created for each database changed. You can then query when specific items of design data were modified by reference to the corresponding session number(s). Sessions can be used by the System Administrator to backtrack changes to a given date or session if necessary.\n\n\n"}
{"Headers": "Session Comments", "Content": "You can add a comment for each session, which can help identify the work done in each session.\nLets you associate comment text with the current Model session. You can query this text later to help you identify a particular session in which modifications were made to elements and/or attribute settings. You can enter the session comment before you issue a SAVEWORK command, or as part of a SAVEWORK command for example SAVEWORK \u2018MY COMMENTS\u2019.\nSESSION COMMENT \u2019Addition of upper platform\u2019\nwhere integer is the session number.\nEach time you enter Model or save your design changes, a new session is created for each database changed. You can then query when specific items of design data were modified by reference to the corresponding session number(s). Sessions can be used by the System Administrator to backtrack changes to a given date or session if necessary.\nExample\nSESSION COMMENT \u2019Addition of upper platform\u2019\n>-- SESSION COMMENT -- text -->\n   \nQ SESSComment integer\nNote:\nSessions 1 and 2 are created in ADMIN (when the MODEL DB and its World element, respectively, are created), so the first true session will be Session 3.\nExample\nSESSION COMMENT \u2019Addition of upper platform\u2019\n\n\n\nbefore\nNote\n:\nSession 3\nSESSION COMMENT \u2019Addition of upper platform\u2019\ntext\ninteger\ninteger"}
{"Headers": "Multiwrite Databases Claims and Extracts", "Content": "If a Model or Draw Database (DB) has been created as a multiwrite database, several users can write to it simultaneously, although they cannot change the same element.\nMultiwrite databases can either be Standard multiwrite databases, or Extract databases. In both types, an element must be claimed before it can be modified. Claiming an element prevents other users claiming (and modifying) the element; the element must be released before another user can change it.\nClaiming can be either explicit, where you must use the CLAIM command before attempting to modify the element, or implicit, where the claim is made automatically when you try to modify the element. The claim mode is set when the DB is created. Refer to Administrator Command Reference Manual for further information.\n\n\n\nmultiwrite\nStandard\nExtract\nclaimed\nreleased\nexplicit\nimplicit\nAdministrator Command Reference Manual\nAdministrator Command Reference Manual\n."}
{"Headers": "User Claims", "Content": "In a Standard multiwrite database, you must claim an element before changing it. This is known as a user claim. If the claim mode is explicit (see below for details of how to check this), you must first claim each element that you want to modify using the CLAIM command. If the claim mode is implicit, the claim will be made automatically (although you can still give explicit CLAIM commands if you want to prevent other users claiming specific elements).\nOnly primary elements can be claimed, these are listed in the Data Model Reference Manual.\nYou can claim a specified element only, or a specified element plus all of the significant elements below it in the hierarchy. If the claimed element is not a significant element, the significant element above it in the hierarchy will be claimed.\nAn element must be unclaimed before another user can claim it and change it. User claims are always unclaimed when you change modules or leaves AVEVA E3D Design, and you can also unclaim elements at any time during an AVEVA E3D Design session using the UNCLAIM command.\nCLAIM /ZoneA /EQUIP100 /PIPE-100-A\n\nClaims named elements\nCLAIM /ZoneA HIERARCHY\n\nClaims named element and all of its owned hierarchy\nCLAIM /ELBOW-33\n\n\nClaims Branch which owns named component, since ELBO is not a significant element\nUNCLAIM /PIPE-100 /PIPE-200\n\nUnclaims named elements\nUNCLAIM ALL\nUnclaims all elements currently claimed\nExamples\nCLAIM /ZoneA /EQUIP100 /PIPE-100-A\nClaims named elements\nCLAIM /ZoneA HIERARCHY\nClaims named element and all of its owned hierarchy\nCLAIM /ELBOW-33\nClaims Branch which owns named component, since ELBO is not a significant element\nUNCLAIM /PIPE-100 /PIPE-200\nUnclaims named elements\nUNCLAIM ALL\nUnclaims all elements currently claimed\n                .---------------.\n               /                |\n>-- CLAIM ----*-- elementname --+-- HIERARCHY ---.\n                                |                |\n                                \u2018----------------+-->\n                 .---------------.\n                /                |\n>-- UNCLAIM ---*-- elementname --+-- HIERARCHY ---.\n               |                 |                |\n               \u2018-- ALL ----------+----------------+-->\n\n\n\n\nData Model Reference Manual\nuser claim\nprimary\nData Model Reference Manual\nunclaimed\nCLAIM /ZoneA /EQUIP100 /PIPE-100-A\nCLAIM /ZoneA HIERARCHY\nCLAIM /ELBOW-33\nUNCLAIM /PIPE-100 /PIPE-200\nUNCLAIM ALL"}
{"Headers": "Notes on Standard Multiwrite DBs", "Content": "Elements cannot be claimed if recent changes have been made to them by other users. You must issue a GETWORK command first.\nElements cannot be unclaimed if there are updates outstanding. You must issue a SAVEWORK command first.\nYou can insert/remove primary elements in a members list without claiming the owner. For example, you can add a Branch to a Pipe without claiming the Pipe. Thus two users can add different Branches to the same Pipe: any discrepancies will be resolved when a SAVEWORK is attempted.\nBefore an element can be deleted, that element and all of its sub-hierarchy must be claimed.\nThe following potential problems may not be revealed until you try to save changes:\nElements cannot be claimed if recent changes have been made to them by other users. You must issue a GETWORK command first.\nElements cannot be claimed if recent changes have been made to them by other users. You must issue a GETWORK command first.\nElements cannot be unclaimed if there are updates outstanding. You must issue a SAVEWORK command first.\nElements cannot be unclaimed if there are updates outstanding. You must issue a SAVEWORK command first.\nYou can insert/remove primary elements in a members list without claiming the owner. For example, you can add a Branch to a Pipe without claiming the Pipe. Thus two users can add different Branches to the same Pipe: any discrepancies will be resolved when a SAVEWORK is attempted.\nYou can insert/remove primary elements in a members list without claiming the owner. For example, you can add a Branch to a Pipe without claiming the Pipe. Thus two users can add different Branches to the same Pipe: any discrepancies will be resolved when a SAVEWORK is attempted.\nBefore an element can be deleted, that element and all of its sub-hierarchy must be claimed.\nBefore an element can be deleted, that element and all of its sub-hierarchy must be claimed.\nThe following potential problems may not be revealed until you try to save changes:\nThe following potential problems may not be revealed until you try to save changes:\n\n\n"}
{"Headers": "Extract Databases", "Content": "Unlike standard multiwrite databases, extracts allow users to keep elements claimed when they exit from AVEVA E3D Design or change to another module. They can also be used, together with Data Access Control (DAC), to manage workflow. Refer to Administrator User Guide for more information.\nAn Extract is created from an existing Database. When an Extract is created, it will be empty, with pointers back to the owing or master database . Extracts can only be created from Multiwrite databases. An extract can be worked on by one User at the same time as another user is working on the master or another extract.\nWhen a user works on the extract, an extract claim is made as well as a user claim.\nIf the claim mode is explicit, the extract claim will be made automatically when you make a user claim using the CLAIM command. You can also claim to the extract only using the EXTRACT CLAIM command.\nIf an element is claimed to an extract, only users with write access to the extract will be able to make a user claim and start work on the element:\nWhen an extract user does a SAVEWORK, the changed data will be saved to the Extract. The unchanged data will still be read via pointers back to the master Database (DB). The changes made to the extract can be written back to the master, or dropped. Also, the extract can be refreshed with changes made to the master.\nEXTRACT CLAIM /STRU1 /STRU2 /STRU3\n\nClaims named elements to the extract\nEXTRACT CLAIM /STRU1 /STRU2 /ZONE-A HIERARCHY\n\nClaims the named elements, and all the elements in the hierarchy to the extract\nThe HIERARCHY keyword must be the last on the command line. It will attempt to claim to the extract all members of the elements listed in the command which are not already claimed to the extract.\nEXTRACT FLUSH DB PIPE/PIPE \u2018Description of flush\u2019\n\nWrites all changes to the database back to the owing extract. The Extract claim is maintained.\nEXTRACT FLUSH /STRU1 /STRU2 /STRU3 \u2018Flushing three  structures\u2019\n\nWrites the changes to the named elements back to the owing extract. The Extract claim is maintained.\nEXTRACT ISSUE DB PIPE/PIPE \u2018Issuing /pipe\u2019\n\nWrites all the changes to the database back to the owning extract and releases the extract claim\nEXTRACT ISSUE /ZONE-A HIERARCHY \u2018Issuing /zone\u2019\n\nWrites all the changes to the named element and all elements under it in the hierarchy back to the owning extract and releases the extract claim\nEXTRACT ISSUE /STRU1 /STRU2 /STRU3 \u2018Issuing three structures\u2019\n\nWrites the changes to the named elements back to the owning extract and releases the extract claim\nEXTRACT RELEASE DB PIPE/PIPE\n\nReleases the extract claim: this command can only be given to release changes that have already been flushed.\nEXTRACT RELEASE /STRU1 /STRU2 /STRU3\n\nReleases the extract claim: this command can only be given to release changes that have already been flushed.\nEXTRACT RELEASE /ZONE-A HIERARCHY\n\nReleases the extract claim to the named element and all: elements under it in the hierarchy.\nEXTRACT DROP DB PIPE/PIPE \u2018Dropping /Pipe\u2019\n\nDrops changes that have not been flushed or issued. Your claim must have been unclaimed before this command can be given.\nEXTRACT REFRESH DB MYTEAMPIPING\n\nThis will refresh the extract MYTEAMPIPING with changes made on the parent extract,\nThe elements required can be specified by selection criteria, using a Programmable Macro Language (PML) expression. For example:\nExamples\nEXTRACT CLAIM /STRU1 /STRU2 /STRU3\nClaims named elements to the extract\nEXTRACT CLAIM /STRU1 /STRU2 /ZONE-A HIERARCHY\nClaims the named elements, and all the elements in the hierarchy to the extract\nThe HIERARCHY keyword must be the last on the command line. It will attempt to claim to the extract all members of the elements listed in the command which are not already claimed to the extract.\nEXTRACT FLUSH DB PIPE/PIPE \u2018Description of flush\u2019\nWrites all changes to the database back to the owing extract. The Extract claim is maintained.\nEXTRACT FLUSH /STRU1 /STRU2 /STRU3 \u2018Flushing three  structures\u2019\nWrites the changes to the named elements back to the owing extract. The Extract claim is maintained.\nEXTRACT ISSUE DB PIPE/PIPE \u2018Issuing /pipe\u2019\nWrites all the changes to the database back to the owning extract and releases the extract claim\nEXTRACT ISSUE /ZONE-A HIERARCHY \u2018Issuing /zone\u2019\nWrites all the changes to the named element and all elements under it in the hierarchy back to the owning extract and releases the extract claim\nEXTRACT ISSUE /STRU1 /STRU2 /STRU3 \u2018Issuing three structures\u2019\nWrites the changes to the named elements back to the owning extract and releases the extract claim\nEXTRACT RELEASE DB PIPE/PIPE\nReleases the extract claim: this command can only be given to release changes that have already been flushed.\nEXTRACT RELEASE /STRU1 /STRU2 /STRU3\nReleases the extract claim: this command can only be given to release changes that have already been flushed.\nEXTRACT RELEASE /ZONE-A HIERARCHY\nReleases the extract claim to the named element and all: elements under it in the hierarchy.\nEXTRACT DROP DB PIPE/PIPE \u2018Dropping /Pipe\u2019\nDrops changes that have not been flushed or issued. Your claim must have been unclaimed before this command can be given.\nEXTRACT REFRESH DB MYTEAMPIPING\nThis will refresh the extract MYTEAMPIPING with changes made on the parent extract,\nEXTRACT CLAIM ALL STRU WHERE (:OWNER EQ 'USERA') HIERARCHY\n>- EXTRACT -+- FLUSH ---------------.\n            |                       |\n            |- FLUSHWithoutrefresh -|\n            |                       |\n            |- RELEASE -------------|\n            |                       |\n            |- ISSUE ---------------|\n            |                       |\n            |- DROP ----------------|    .-------<-------.\n            |                       |   /                |\n            \u2018- REFRESH -------------+--*-- elementname --+- HIERARCHY -.\n                                    |                                  |\n                                    |                                  |\n                                    |                                  |\n                                    \u2018-- DB dbname ---------------------+->\nIf the databases are set up with implicit claim, when you modify the element, the element will be claimed both to the extract and then to you. If the element is already claimed to the extract, then the claim will only be made to you.\nIf the databases are set up with explicit claim, then you will need to use the CLAIM command before modifying the element.\nOnce you have made a user claim, no other users will be able to work on the elements claimed, as in a normal multiwrite database.\nIf you unclaim an element, it will remain claimed to the extract until the extract claim is released or issued.\nIf the databases are set up with implicit claim, when you modify the element, the element will be claimed both to the extract and then to you. If the element is already claimed to the extract, then the claim will only be made to you.\nIf the databases are set up with implicit claim, when you modify the element, the element will be claimed both to the extract and then to you. If the element is already claimed to the extract, then the claim will only be made to you.\nIf the databases are set up with explicit claim, then you will need to use the CLAIM command before modifying the element.\nIf the databases are set up with explicit claim, then you will need to use the CLAIM command before modifying the element.\nOnce you have made a user claim, no other users will be able to work on the elements claimed, as in a normal multiwrite database.\nOnce you have made a user claim, no other users will be able to work on the elements claimed, as in a normal multiwrite database.\nIf you unclaim an element, it will remain claimed to the extract until the extract claim is released or issued.\nIf you unclaim an element, it will remain claimed to the extract until the extract claim is released or issued.\n\n\n\nAdministrator User Guide\nmaster\nreleased\nissued\nEXTRACT CLAIM /STRU1 /STRU2 /STRU3\nEXTRACT CLAIM /STRU1 /STRU2 /ZONE-A HIERARCHY\nHIERARCHY\nEXTRACT FLUSH DB PIPE/PIPE \u2018Description of flush\u2019\nEXTRACT FLUSH /STRU1 /STRU2 /STRU3 \u2018Flushing three  structures\u2019\nEXTRACT ISSUE DB PIPE/PIPE \u2018Issuing /pipe\u2019\nEXTRACT ISSUE /ZONE-A HIERARCHY \u2018Issuing /zone\u2019\nEXTRACT ISSUE /STRU1 /STRU2 /STRU3 \u2018Issuing three structures\u2019\nEXTRACT RELEASE DB PIPE/PIPE\nEXTRACT RELEASE /STRU1 /STRU2 /STRU3\nEXTRACT RELEASE /ZONE-A HIERARCHY\nEXTRACT DROP DB PIPE/PIPE \u2018Dropping /Pipe\u2019\nEXTRACT REFRESH DB MYTEAMPIPING"}
{"Headers": "How to Find Out What You Can Claim", "Content": "This section explains what different users will see as a result of Q CLAIMLIST commands.\n\nFor this example, take the case of a database PIPE/PIPE, accessed by USERA, with two extracts. Users USERX1 and USERX2 are working on the extracts.\nUSERA creates a Pipe and flushes the database back to the owning database, PIPE/PIPE. The results of various Q CLAIMLIST commands by the three Users, together with the extract control commands which they have to give to make the new data available, are shown in the the image.\n\nWhen you create an element, AVEVA E3D Design only sees it as a user claim, not an extract claim, until the element is flushed. It will then be reported as an extract claim (as well as a user claim, if it has not been unclaimed).\nNote that a change in the claim status of an existing element will be shown by the appropriate Q CLAIMLIST command as soon as appropriate updates take place, but a user will have to GETWORK as usual to see the changes to the Model model data.\nWe recommend that:\nQ DBNAME\nReturns the name of the database which you are actually writing to.\nQ CLAIMLIST\nOutputs a list of all elements currently claimed by yourself:\nQ CLAIMLIST OTHE\nOutputs a list of all elements currently claimed by other users who are accessing the same DB:\nQ CLAIMLIST EXTRACT\nShows the extract claimlist for all the writable extracts in the MDB.\nQ CLAIMLIST EXTRACT DB dbname\nShows the extract claimlist for the named extract DB.\nQ CLAIMLIST EXTRACT FREE DB dbname\nShows the elements claimed to the current extract and not claimed to another extract or user. That is, the elements which can be released.\nQ CLAIMLIST EXTRACT OTHER DB dbname\nShows the elements claimed to the current extract and claimed to another extract or user.\nQ CLAIMLIST CONTROL DB dbname\nShows the extract claimlist for a CONTROLLED named extract DB.\nQ DBAC\nQueries the access mode of the database. DBAC can have the text settings CONTROL, UPDATE or MULTIWRITE.\nQ DBCL\nQueries the claim mode of the database. DBCL can have the text settings EXPLICIT or IMPLICIT.\nQ LCLM\nQueries whether or not the current element is claimed by another user. Returns TRUE or FALSE.\nQ DBNAME\nReturns the name of the database which you are actually writing to.\nQ CLAIMLIST\nOutputs a list of all elements currently claimed by yourself:\nQ CLAIMLIST OTHE\nOutputs a list of all elements currently claimed by other users who are accessing the same DB:\nQ CLAIMLIST EXTRACT\nShows the extract claimlist for all the writable extracts in the MDB.\nQ CLAIMLIST EXTRACT DB dbname\nShows the extract claimlist for the named extract DB.\nQ CLAIMLIST EXTRACT FREE DB dbname\nShows the elements claimed to the current extract and not claimed to another extract or user. That is, the elements which can be released.\nQ CLAIMLIST EXTRACT OTHER DB dbname\nShows the elements claimed to the current extract and claimed to another extract or user.\nQ CLAIMLIST CONTROL DB dbname\nShows the extract claimlist for a CONTROLLED named extract DB.\nQ DBAC\nQueries the access mode of the database. DBAC can have the text settings CONTROL, UPDATE or MULTIWRITE.\nQ DBCL\nQueries the claim mode of the database. DBCL can have the text settings EXPLICIT or IMPLICIT.\nQ LCLM\nQueries whether or not the current element is claimed by another user. Returns TRUE or FALSE.\nQ DBNAME\nReturns the name of the database which you are actually writing to.\nQ CLAIMLIST\nOutputs a list of all elements currently claimed by yourself:\nQ CLAIMLIST OTHE\nOutputs a list of all elements currently claimed by other users who are accessing the same DB:\nQ CLAIMLIST EXTRACT\nShows the extract claimlist for all the writable extracts in the MDB.\nQ CLAIMLIST EXTRACT DB dbname\nShows the extract claimlist for the named extract DB.\nQ CLAIMLIST EXTRACT FREE DB dbname\nShows the elements claimed to the current extract and not claimed to another extract or user. That is, the elements which can be released.\nQ CLAIMLIST EXTRACT OTHER DB dbname\nShows the elements claimed to the current extract and claimed to another extract or user.\nQ CLAIMLIST CONTROL DB dbname\nShows the extract claimlist for a CONTROLLED named extract DB.\nQ DBAC\nQueries the access mode of the database. DBAC can have the text settings CONTROL, UPDATE or MULTIWRITE.\nQ DBCL\nQueries the claim mode of the database. DBCL can have the text settings EXPLICIT or IMPLICIT.\nQ LCLM\nQueries whether or not the current element is claimed by another user. Returns TRUE or FALSE.\nEXTRACT CLAIM ALL FROM !COLL\n>-- Q CLAIMLIST --+- OTHER -----.\n                  |             |\n                  |- EXTRACT ---+- OTHER --.\n                  |             |          |\n                  |             |- FREE ---|\n                  |             |          |\n                  |             \u2018----------|\n                  |                        |\n                  |------------------------+-- DB dbname --.\n                  |                                        |\n                  \u2018----------------------------------------+-->\nBefore you make a user or extract claim, you should do an EXTRACT REFRESH and GETWORK.\nIf you need to claim many elements to an extract, it improves performance if the elements are claimed in a single command, for example, by using a collection:\nEXTRACT CLAIM ALL FROM !COLL\nBefore you make a user or extract claim, you should do an EXTRACT REFRESH and GETWORK.\nBefore you make a user or extract claim, you should do an EXTRACT REFRESH and GETWORK.\nIf you need to claim many elements to an extract, it improves performance if the elements are claimed in a single command, for example, by using a collection:\nEXTRACT CLAIM ALL FROM !COLL\nIf you need to claim many elements to an extract, it improves performance if the elements are claimed in a single command, for example, by using a collection:\nNote:\nQ CLAIMLIST EXTRACT\ntells you what you can flush\nQ CLAIMLIST OTHERS\ntells you want you can't claim\n\n\n\n\nNote\n:\nQ CLAIMLIST EXTRACT\nQ CLAIMLIST OTHERS\nQ DBNAME\nQ CLAIMLIST\nQ CLAIMLIST OTHE\nQ CLAIMLIST EXTRACT\nQ CLAIMLIST EXTRACT DB dbname\nQ CLAIMLIST EXTRACT FREE DB dbname\nQ CLAIMLIST EXTRACT OTHER DB dbname\nQ CLAIMLIST CONTROL DB dbname\nQ DBAC\nQ DBCL\nQ LCLM"}
{"Headers": "Related Attributes", "Content": "Attribute Name\nData Type\nQualifier\nDescription\nDACCLA\nBOOL\nTrue if DAC allows element to be claimed\nDACERR\nSTRING(120)\nATTR\nReturns the DAC error\nDACISS\nBOOL\nTrue if DAC allows element to be issued\nAttribute Name\nData Type\nQualifier\nDescription\nDACCLA\nBOOL\n\nTrue if DAC allows element to be claimed\nDACERR\nSTRING(120)\nATTR\nReturns the DAC error\nDACISS\nBOOL\n\nTrue if DAC allows element to be issued\nCLMID\nSTRING(120)\n\nUnique system ID of user claiming element\nCLMNUM\nINTEGER\n\nUser or extract number claiming element. Extract num\\-bers are negative\nCLMTIE\nELEMENT(4)\n\nReference to elements that are automatically claimed along with this element\nEXCLFR\nBOOL\n\nTrue if element claimed from this extract. Only True for Primary elements\nEXCLHI\nELEMENT(5000)\n\nPrimary elements in descendant hierarchy claimed to this extract (includes this element)\nEXCLTO\nBOOL\n\nTrue if element claimed to this extract. Only True for Pri\\-mary elements\nEXNCLH\nELEMENT(5000)\n\nPrimary elements in descendant hierarchy not claimed to this extract\nEXTRC\nSTRING(120)\n\nName of extract claiming element\nNPDESC\nELEMENT(5000)\n\nList of non primary offspring\nOKCLA\nBOOL\n\nTrue if element may be claimed\nOKCLH\nBOOL\n\nTrue if element and hierarchy may be claimed\nOKREL\nBOOL\n\nTrue if element may be released\nOKRLH\nBOOL\n\nTrue if element and hierarchy may be released\nPRIMTY\nBOOL\n\nTrue if element is primary\nPRMMEM\nBOOL\n\nTrue if there are any primary elements amongst descendants\nPRMOWN\nELEMENT\n\nPrimary owning element (will be itself if primary)\nUSCLHI\nELEMENT(5000)\n\nElements in descendant hierarchy claimed to this user\nUSERC\nSTRING(120)\n\nUser name of user claiming element\nUSNCLH\nELEMENT(5000)\n\nElements in descendant hierarchy not claimed to this user\nEXHCNC\nELEMENT(5000)\n\nAs EXTCNC, but repeat test for all descendants\nEXHCNN\nELEMENT(5000)\n\nAs EXTCNN, but repeat test for all descendants\nEXHCON\nELEMENT(5000)\n\nAs EXTCON, but repeat test for all descendants\nEXHRCN\nELEMENT(5000)\n\nAs EXRCN, but repeat test for all descendants\nEXHRCO\nELEMENT(5000)\n\nAs EXTRCO, but repeat test for all descendants\nEXMOC\nBOOL\n\nAs EXMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOC\nBOOL\n\nAs EXPMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOD\nBOOL\n\nTrue if primary and element or non-primary descendants have been modified in this extract\nEXTCNC\nELEMENT(5000)\n\nAs EXTCON but excluding non modified elements\nEXTCNN\nELEMENT(5000)\n\nAs EXTCON but excluding modified elements\nEXTCON\nELEMENT(5000)\n\nPrimary elements connected/disconnected from ele\\-ment or non primary descendants in extract\nEXTRCN\nELEMENT(5000)\n\nAs EXTCNN, but applied recursively to each connection\nEXTRCO\nELEMENT(5000)\n\nAs EXTCON, but applied recursively to each connection\nOKDROP\nBOOL\n\nTrue if element may be dropped\nOKDRPH\nELEMENT(5000)\n\nPrimary elements preventing hierarchy drop\nOKRLEH\nELEMENT(5000)\n\nPrimary elements preventing hierarchy release\nOKRLEX\nBOOL\n\nTrue if element may be extract released\n\n\nAttribute Name\nData Type\nQualifier\nDescription\nDACCLA\nBOOL\nTrue if DAC allows element to be claimed\nDACERR\nSTRING(120)\nATTR\nReturns the DAC error\nDACISS\nBOOL\nTrue if DAC allows element to be issued\nAttribute Name\nData Type\nQualifier\nDescription\nCLMID\nSTRING(120)\nUnique system ID of user claiming element\nCLMNUM\nINTEGER\nUser or extract number claiming element. Extract num\\-bers are negative\nCLMTIE\nELEMENT(4)\nReference to elements that are automatically claimed along with this element\nEXCLFR\nBOOL\nTrue if element claimed from this extract. Only True for Primary elements\nEXCLHI\nELEMENT(5000)\nPrimary elements in descendant hierarchy claimed to this extract (includes this element)\nEXCLTO\nBOOL\nTrue if element claimed to this extract. Only True for Pri\\-mary elements\nEXNCLH\nELEMENT(5000)\nPrimary elements in descendant hierarchy not claimed to this extract\nEXTRC\nSTRING(120)\nName of extract claiming element\nNPDESC\nELEMENT(5000)\nList of non primary offspring\nOKCLA\nBOOL\nTrue if element may be claimed\nOKCLH\nBOOL\nTrue if element and hierarchy may be claimed\nOKREL\nBOOL\nTrue if element may be released\nOKRLH\nBOOL\nTrue if element and hierarchy may be released\nPRIMTY\nBOOL\nTrue if element is primary\nPRMMEM\nBOOL\nTrue if there are any primary elements amongst descendants\nPRMOWN\nELEMENT\nPrimary owning element (will be itself if primary)\nUSCLHI\nELEMENT(5000)\nElements in descendant hierarchy claimed to this user\nUSERC\nSTRING(120)\nUser name of user claiming element\nUSNCLH\nELEMENT(5000)\nElements in descendant hierarchy not claimed to this user\nAttribute Name\nData Type\nQualifier\nDescription\nEXHCNC\nELEMENT(5000)\nAs EXTCNC, but repeat test for all descendants\nEXHCNN\nELEMENT(5000)\nAs EXTCNN, but repeat test for all descendants\nEXHCON\nELEMENT(5000)\nAs EXTCON, but repeat test for all descendants\nEXHRCN\nELEMENT(5000)\nAs EXRCN, but repeat test for all descendants\nEXHRCO\nELEMENT(5000)\nAs EXTRCO, but repeat test for all descendants\nEXMOC\nBOOL\nAs EXMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOC\nBOOL\nAs EXPMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOD\nBOOL\nTrue if primary and element or non-primary descendants have been modified in this extract\nEXTCNC\nELEMENT(5000)\nAs EXTCON but excluding non modified elements\nEXTCNN\nELEMENT(5000)\nAs EXTCON but excluding modified elements\nEXTCON\nELEMENT(5000)\nPrimary elements connected/disconnected from ele\\-ment or non primary descendants in extract\nEXTRCN\nELEMENT(5000)\nAs EXTCNN, but applied recursively to each connection\nEXTRCO\nELEMENT(5000)\nAs EXTCON, but applied recursively to each connection\nOKDROP\nBOOL\nTrue if element may be dropped\nOKDRPH\nELEMENT(5000)\nPrimary elements preventing hierarchy drop\nOKRLEH\nELEMENT(5000)\nPrimary elements preventing hierarchy release\nOKRLEX\nBOOL\nTrue if element may be extract released\n\n\n"}
{"Headers": "Undo and Redo", "Content": "It is possible to undo and redo many operations. The undo mechanism is managed by AVEVA E3D Design using a stack of transaction objects.\nEach transaction object records the change in the state across the transaction.\nThe new descriptions are then:\nMARKDB \u2018comment\u2019 - Complete the current transaction and starts a new transaction.\nUNDODB - Undo the last transaction. If there is a current transaction then this is completed. Multiple Undos are allowed.\nREDODB - Redo to next mark. Multiple Redos are allowed. A redo is only valid after an UNDO. Any database change after an UNDO invalidates a REDO.\n\n\n"}
{"Headers": "How Undo Works", "Content": "Every time you select an undo operation an entry is taken off the undo stack. The state saved in this transaction is restored, and the transaction object is placed on the redo stack.\nWhen the undo stack is empty, then the Undo button and the Undo menu option will be greyed out indicating that there are no operations remaining that can be undone.\nIf the operation of undo involves moving into or out of model editing mode, then the switch into that mode will happen automatically, and the model editor button and menu option will reflect the change.\nThe selection set and handle appropriate to the editing operation that was being used will also be restored.\nThere are also a number of ways that you can perform an undo:\nThe undo stack is automatically cleared after a SAVEWORK or GETWORK.\nA similar process to the one described above occurs for redo.\nWhen a transaction is taken off the redo stack, it is put back onto the undo stack.\nIf you perform any operation that changes the database after doing an undo, then the redo stack will be cleared.\nRefer to for controlling the undo stack from user defined Programmable Macro Language (PML).\nMARKDB 'comment'\nSet a Database mark. Multiple marks may be set.\nUNDODB\nUndo database to last mark. Multiple undos are allowed.\nREDODB\nRedo to next mark. Multiple Redos are allowed. A redo is only valid after an UNDO. Any database change after an UNDO invalidates a REDO.\nMARKDB 'comment'\nSet a Database mark. Multiple marks may be set.\nUNDODB\nUndo database to last mark. Multiple undos are allowed.\nREDODB\nRedo to next mark. Multiple Redos are allowed. A redo is only valid after an UNDO. Any database change after an UNDO invalidates a REDO.\nThe list of marks can be obtained from PML function MARKDB.\nThe system will always create an initial mark the first time the database is changed.\nMARKDB 'comment'\nSet a Database mark. Multiple marks may be set.\nUNDODB\nUndo database to last mark. Multiple undos are allowed.\nREDODB\nRedo to next mark. Multiple Redos are allowed. A redo is only valid after an UNDO. Any database change after an UNDO invalidates a REDO.\nAREA 0\nMARKDB 'First Mark'\nAREA 100\nMARKDB 'Second Mark'\nAREA 200\nMARKDB 'Third Mark'\nAREA 300\n!MARKS = MARKDB\nQ VAR !MARKS\nUNDODB\nQ AREA - value will be 200\nUNDODB\nQ AREA - value will be 100\nUNDODB\nQ AREA - value will be 0\nREDODB\nQ AREA - value will be 100\nREDODB\nQ AREA - value will be 200\nAREA 99\nUNDODB\nQ AREA - value will be 200\nREDODB\nQ AREA - value will be 99\nBy clicking on the Undo button on the appropriate toolbar.\nBy selecting the Undo option on the Edit pulldown menu on the main toolbar.\nBy entering the command UNDODB n where n indicates how many steps are to be undone.\nBy clicking on the Undo button on the appropriate toolbar.\nBy clicking on the Undo button on the appropriate toolbar.\nBy selecting the Undo option on the Edit pulldown menu on the main toolbar.\nBy selecting the Undo option on the Edit pulldown menu on the main toolbar.\nBy entering the command UNDODB n where n indicates how many steps are to be undone.\nBy entering the command UNDODB n where n indicates how many steps are to be undone.\n\n\n\nUndo\nUndo\nUndo\nUndo\nEdit\nUNDODB n\nn\n\nExample"}
{"Headers": "Shared Collections (Groups) and Secondary Hierarchies", "Content": "A shared collection can hold in its members list a number of design elements from any combination of hierarchic levels, they may also span Multiple Databases (MDBs). You can use any appropriate design operation to act upon all of these individual elements simply by carrying out the operation on the shared collection.\nShared collections are particularly useful when there is a need to create a secondary hierarchy of elements. For example a set of elements for a project may span more that one site, if this is the case it is difficulty to identify where in the hierarchy these elements occur. With a shared collection you can easily query its members and see the hierarchy of elements contained within it.\nA shared collection is a Model database element in its own right, and is therefore stored automatically for use in later sessions when you save database changes.\nThe Elements which make up a shared collection within the Model database are shown below:\n\nGPWL (Group World) Is a top level administrative element. A GPWL may hold multiple GPSET (Group Set) elements.\nGPSET contains groups of items (GPITEM). A GPSET element has Name, DESC, and FUNCTION attributes.\nGPITEM These are elements within a database which are to be grouped under a Group Set (GPSET). Elements from different databases can all be grouped into the same Group Set. A GPITEM has the following attributes Name, DESC and SITEM.\nIt is possible to nest Group Sets within other Group Sets. To achieve this structure a GPSET can own another GPSET or a GPITEM can point back onto a GPSET. The following figure illustrates this:\n\n\n\n\nGPWL\nGPSET\nGPITEM"}
{"Headers": "Define Contents", "Content": "The contents of a shared collection are defined by adding or removing references to or from the list part of the shared collection.\nIn order to use the commands described in this section, the current element must be the shared collection whose member list you wish to modify. Specified elements are then added to the list part of the current element starting from the current list position or are removed from the list part of the current element such that the current list position becomes the Head position.\nThe elements to be added to, or removed from, the shared collection\u2019s member list may be specified in any of the following ways:\nGADD /ZONE1 /VALVE2\n\nAdds /ZONE1 and /VALVE2 to the current shared collection, starting from the current list position\nGREMOVE /ZONE1 /BOX3\n\nRemoves /ZONE1 and /BOX3 from the current shared collection and moves the current list position pointer to the Head position\nGADD MEM OF /BRANCH1 /BRANCH2\n\nAdds all the pipe Components in Branches /BRANCH1 and /BRANCH2 to the current shared collection, starting from the current list position\nGREM MEM OF /PIPE100 MEM OF /EQUI-B\n\nRemoves all Branches of the Pipe /PIPE100 and all members of Equipment /EQUI-B from the current shared collection\nGREM ITEMS OF /ZONE2\n\nRemoves from the current shared collection all occurrences of those offspring of /ZONE2 which are items\nGADD ALL EQU BRAN OF /ZONE1 /ZONE2\n\nAdds all offspring of /ZONE1 and /ZONE2 which are of types Equip or Branch to the current shared collection, starting from the current list position\nExamples\nGADD /ZONE1 /VALVE2\nAdds /ZONE1 and /VALVE2 to the current shared collection, starting from the current list position\nGREMOVE /ZONE1 /BOX3\nRemoves /ZONE1 and /BOX3 from the current shared collection and moves the current list position pointer to the Head position\nGADD MEM OF /BRANCH1 /BRANCH2\nAdds all the pipe Components in Branches /BRANCH1 and /BRANCH2 to the current shared collection, starting from the current list position\nGREM MEM OF /PIPE100 MEM OF /EQUI-B\nRemoves all Branches of the Pipe /PIPE100 and all members of Equipment /EQUI-B from the current shared collection\nGREM ITEMS OF /ZONE2\nRemoves from the current shared collection all occurrences of those offspring of /ZONE2 which are items\nGADD ALL EQU BRAN OF /ZONE1 /ZONE2\nAdds all offspring of /ZONE1 and /ZONE2 which are of types Equip or Branch to the current shared collection, starting from the current list position\n>--+-- GADD -----.     .-------------.\n   |             |    /              |\n   \u2018-- GREMove --+---*-- <selatt> ---+--->\nExplicitly, by name or (system-assigned) reference number.\nAs members of specified elements, where a member of an element is defined as any element immediately below it in the DB hierarchy\nAs items of specified elements, where an item of an element is any element anywhere below it in the hierarchy which has no list part (such as a Valve, Point, Box, etc.)\nBy type (such as Equipment, Branch, Pipe, etc.)\nExplicitly, by name or (system-assigned) reference number.\nExplicitly, by name or (system-assigned) reference number.\nAs members of specified elements, where a member of an element is defined as any element immediately below it in the DB hierarchy\nAs members of specified elements, where a member of an element is defined as any element immediately below it in the DB hierarchy\nAs items of specified elements, where an item of an element is any element anywhere below it in the hierarchy which has no list part (such as a Valve, Point, Box, etc.)\nAs items of specified elements, where an item of an element is any element anywhere below it in the hierarchy which has no list part (such as a Valve, Point, Box, etc.)\nBy type (such as Equipment, Branch, Pipe, etc.)\nBy type (such as Equipment, Branch, Pipe, etc.)\n\n\n\n\nor\nmember\nimmediately\nitem\nno\nGADD /ZONE1 /VALVE2\nGREMOVE /ZONE1 /BOX3\nGADD MEM OF /BRANCH1 /BRANCH2\nGREM MEM OF /PIPE100 MEM OF /EQUI-B\nGREM ITEMS OF /ZONE2\nGADD ALL EQU BRAN OF /ZONE1 /ZONE2"}
{"Headers": "Delete Shared Collection", "Content": "The action of this command differs from normal behaviour if the current element is a shared collection.\nDELETE GPSET\n\nOnly the current element and any Offspring that are GPSETs will be deleted.\nDELETE GPWLD\n\nOnly the current element and any Offspring that are GPSETs will be deleted.\n\nExamples\nDELETE GPSET\nOnly the current element and any Offspring that are GPSETs will be deleted.\nDELETE GPWLD\nOnly the current element and any Offspring that are GPSETs will be deleted.\n\n\n\nDELETE GPSET\nDELETE GPWLD"}
{"Headers": "Copy a Shared Collection", "Content": "Shared collections can be copied with a slightly different effect to normal elements.\nCOPY /GROUP21 (At a Group)\n\nThe Current shared collection will contain exactly the same Members as /GROUP21. No new elements have been created.\n\nExamples\nCOPY /GROUP21 (At a Group)\nThe Current shared collection will contain exactly the same Members as /GROUP21. No new elements have been created.\n\n\n\nCOPY /GROUP21 (At a Group)"}
{"Headers": "Define Dynamic Shared Collections", "Content": "You may specify a dynamic selection for a GPSET. The dynamic selection consists of a PML1 collection expression.\nFor example:\nThe selection must be set against the SCOSEL attribute.\nFor example:\nThe selection is evaluated dynamically whenever the shared collection is used. Depending on the selection used there is a performance overhead in evaluating the selection.\nALL PIPE WHERE (BORE GT 80)\nALL BRAN MEMBERS WHERE (SPREF EQ /MYSPEC ) for SITE /SITE1\n   \nSCOSEL ALL EQUI FROM CLAIMLIST\n\n\n\nRE (BORE GT 80)\nALL BRAN MEMBERS WHERE (SPREF EQ /MYSPEC \n."}
{"Headers": "Expressions", "Content": "This section explains the PML 1 expressions package. These facilities are needed within AVEVA products, for example, to define report templates in AVEVA E3D Design.\nExpressions have types. For example, you can have numeric expressions, text expressions and logical expressions. All the elements in an expression must be of the correct type. For example, if you have a two numbers, x and y, and two text strings text1 and text2, the following expression is meaningless:\nx + text1\n$\nx + text1\n$\nHowever, both of the following expressions are valid:\nx + y\n$ adds the values of the numeric variables.\nText1 + text2\n$ concatenates the two text strings.\nx + y\n$ adds the values of the numeric variables.\nText1 + text2\n$ concatenates the two text strings.\nReal expressions also have a physical dimension. This may be NONE when all values in the expression are purely numerical, but if any value has a physical dimension (such as being a length or mass) then all other values must be compatible with it and the result of the expression may have a physical dimension, or it may evaluate to a pure numerical value (1inch / 1mm = 25.4).\nThe following types of expressions are available:\nx + text1\n$\nx + y\n$ adds the values of the numeric variables.\nText1 + text2\n$ concatenates the two text strings.\nLogical Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nNumeric (Real) Functions\nText Expressions\nLogical Expressions\nLogical Expressions\nLogical Array Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nNumeric (Real) Expressions\nNumeric (Real) Functions\nNumeric (Real) Functions\nText Expressions\nText Expressions\nNote:\nGenerally, all these facilities are compatible with PML 2.\n\n\n\nLogical Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nNumeric (Real) Functions\nText Expressions\nNote\n:\nx + text1\nx + y\nText1 + text2\nLogical Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nNumeric (Real) Functions\nText Expressions"}
{"Headers": "Format of Expressions", "Content": "The format of an expression, for example the use of brackets, spaces and quotes, is important. If you do not follow the rules given below you will get error messages:\nText must be enclosed in quotes.\nThere must be a space between each operator and operand. For example:\nUse round brackets to control the order of evaluation of expressions and to enclose the argument of a function.\nIn general, you do not need spaces before or after brackets, except when an AVEVA E3D Design name is followed by a bracket. If there is no space, the bracket will be read as part of the name.\n'This is text\u2019\nx + y\nSIN(30)\n(NAME EQ /VESS1 )\n\n\n"}
{"Headers": "Operator Precedence", "Content": "Operators are evaluated in the order of the following list: the ones at the top of the list are evaluated first.\nBRACKETS\nBrackets can be used to control the order in which operators are evaluated, in the same way as in normal arithmetic\nFUNCTIONS\n\n* /\n\n+ -\n\nEQ, NEQ, LT, LE, GE, GT\n\nNOT\n\nAND\n\nOR\n\n\nOperator\nComments\nBRACKETS\nBrackets can be used to control the order in which operators are evaluated, in the same way as in normal arithmetic\nFUNCTIONS\n* /\n+ -\nEQ, NEQ, LT, LE, GE, GT\nNOT\nAND\nOR\n\n\n"}
{"Headers": "Nesting Expressions", "Content": "Expressions can be nested using brackets.\n( (SIN(!angleA) * 2)  /  SIN(!angleB) )\n\n\n\n( (SIN(!angleA) * 2)  /  SIN(!angleB) )"}
{"Headers": "Logical Expressions", "Content": "Logical expressions can contain:\nAVEVA E3D Design attributes of type logical e.g. BUILT.\nLogical constants. The constants available are: TRUE, ON, YES for true, and FALSE, OFF, NO for false.\nLogical operators.\nLogical functions.\nAVEVA E3D Design attributes of type logical e.g. BUILT.\nAVEVA E3D Design attributes of type logical e.g. BUILT.\nLogical constants. The constants available are: TRUE, ON, YES for true, and FALSE, OFF, NO for false.\nLogical constants. The constants available are: TRUE, ON, YES for true, and FALSE, OFF, NO for false.\nLogical operators.\nLogical operators.\nLogical functions.\nLogical functions.\n\n\n"}
{"Headers": "Logical Operators", "Content": "Logical expressions involving physical quantities.\nIf the expression contains unit qualified values, or attributes with a physical dimension then these values are converted to consistent units before comparison\nIf a value is not unit qualified it is assumed to be in current units of the quantity defined by the other value (i.e. the context of the expression). For example if current units of mass (colloquially weight) are oz then\nBut if current units of mass are kg then expression will return FALSE as 2lb is not equal to 2kg.\nIf the units are not units of the same physical quantity FALSE will always be returned as the two values are completely incompatible (as are apples and pears) and a warning issued (for example, (2lb equal 32mm).\nThe logical operators available are:\nAND\n\nEQ, NE\nThe operators EQ and NE may be applied to any pair of values of the same type.\nGT, GE, LE, LT\nThe operators GE, LE, GT and LT may only be used with numbers and positions. For more information, see Positions, Directions and Orientations in Expressions.\nNOT\n\nOR\n\nlog1 AND log2\n-> logical\nPerform the logical AND between two logical values. Treats unset values as FALSE.\nIf one of the values is undefined and the other one is FALSE, the result is FALSE.\nTRUE and FALSE -> FALSE\nCompare two values. A special feature is used for the positions, only the coordinates specified are compared. Refer to Compare Positions for more information. Unset values result in FALSE across EQ, TRUE across NE.\nIf two positions have no common coordinate, for example, \u2019N 10 ne U 10\u2019, the result is undefined. Units are consolidated across comparisons.\n( 1.0 eq 2.0) -> FALSE\nNone.\n( number1 GT number2 )\n> logical\n( pos1 GT pos2 )\n> logical\n( number1 GE number2 )\n> logical\n( pos1 GE pos2 )\n> logical\n( number1 LE number2 )\n> logical\n( pos1 LE pos2 )\n> logical\n( number1 LT number2 )\n> logical\n( pos1 LT pos2 )\n> logical\nCompare two values. A special feature is used for positions: only the coordinates specified are compared. See Compare Positions for more information. For positions, since comparisons may be performed on more than one value, LT (GT) is not the inverse of GE (LE). Unset values result in false\nIf two positions have no common coordinate, the result is undefined. For example, \u2019N 10 gt U 10\u2019.\nUnits are consolidated across comparisons.\n( 1.0 LT 2.0) -> TRUE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\n( N 0 E 10 GT N 10 E 0 ) -FALSE\nNone.\nNOT log1\n-> logical\nPerform the logical NOT on a logical value.\nNone.\nnot TRUE -> FALSE\nNone.\nOR log2\n-> logical\nPerform the logical inclusive OR between two logical values. (The exclusive OR is defined by using NE.)\nAllows numbers instead of logical values.\nIf one of the values is undefined and the other one is TRUE, the result is TRUE.\nTRUE or FALSE -> TRUE\nNone.\n\nOperator\nComments\nAND\nEQ, NE\nThe operators EQ and NE may be applied to any pair of values of the same type.\nGT, GE, LE, LT\nThe operators GE, LE, GT and LT may only be used with numbers and positions. For more information, see Positions, Directions and Orientations in Expressions.\nNOT\nOR\nSynopsis\nlog1 AND log2\n-> logical\nDescription\nPerform the logical AND between two logical values. Treats unset values as FALSE.\nSide Effects\nIf one of the values is undefined and the other one is FALSE, the result is FALSE.\nExample\nTRUE and FALSE -> FALSE\nSynopsis\n( number1 EQual number2)\n-> logical\n( text1 EQual text2 )\n-> logical\n( log1 EQual log2 )\n-> logical\n( id1 EQual id2 )\n-> logical\n( pos1 EQual pos2 )\n-> logical\n( dir1 EQual dir2 )\n-> logical\n( ori1 EQual ori2 )\n-> logical\n( pp1 EQual pp2 )\n-> logical\n( number1 NEqual number2 )\n-> logical\n( text1 NEqual text2 )\n-> logical\n( log1 NEqual log2 )\n-> logical\n( id1 NEqual id2 )\n-> logical\n( pos1 NEqual pos2 )\n-> logical\n( dir1 NEqual dir2 )\n-> logical\n( ori1 NEqual ori2 )\n-> logical\n( pp1 NEqual pp2 )\n-> logical\nDescription\nCompare two values. A special feature is used for the positions, only the coordinates specified are compared. Refer to Compare Positions for more information. Unset values result in FALSE across EQ, TRUE across NE.\nSide Effects\nIf two positions have no common coordinate, for example, \u2019N 10 ne U 10\u2019, the result is undefined. Units are consolidated across comparisons.\nExample\n( 1.0 eq 2.0) -> FALSE\nErrors\nNone.\nSynopsis\n( number1 GT number2 )\n> logical\n( pos1 GT pos2 )\n> logical\n( number1 GE number2 )\n> logical\n( pos1 GE pos2 )\n> logical\n( number1 LE number2 )\n> logical\n( pos1 LE pos2 )\n> logical\n( number1 LT number2 )\n> logical\n( pos1 LT pos2 )\n> logical\nDescription\nCompare two values. A special feature is used for positions: only the coordinates specified are compared. See Compare Positions for more information. For positions, since comparisons may be performed on more than one value, LT (GT) is not the inverse of GE (LE). Unset values result in false\nSide Effects\nIf two positions have no common coordinate, the result is undefined. For example, \u2019N 10 gt U 10\u2019.\nUnits are consolidated across comparisons.\nExample\n( 1.0 LT 2.0) -> TRUE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\n( N 0 E 10 GT N 10 E 0 ) -FALSE\nErrors\nNone.\nSynopsis\nNOT log1\n-> logical\nDescription\nPerform the logical NOT on a logical value.\nSide Effects\nNone.\nExample\nnot TRUE -> FALSE\nErrors\nNone.\nSynopsis\nOR log2\n-> logical\nDescription\nPerform the logical inclusive OR between two logical values. (The exclusive OR is defined by using NE.)\nAllows numbers instead of logical values.\nSide Effects\nIf one of the values is undefined and the other one is TRUE, the result is TRUE.\nExample\nTRUE or FALSE -> TRUE\nErrors\nNone.\n( number1 EQual number2)\n-> logical\n( text1 EQual text2 )\n-> logical\n( log1 EQual log2 )\n-> logical\n( id1 EQual id2 )\n-> logical\n( pos1 EQual pos2 )\n-> logical\n( dir1 EQual dir2 )\n-> logical\n( ori1 EQual ori2 )\n-> logical\n( pp1 EQual pp2 )\n-> logical\n( number1 NEqual number2 )\n-> logical\n( text1 NEqual text2 )\n-> logical\n( log1 NEqual log2 )\n-> logical\n( id1 NEqual id2 )\n-> logical\n( pos1 NEqual pos2 )\n-> logical\n( dir1 NEqual dir2 )\n-> logical\n( ori1 NEqual ori2 )\n-> logical\n( pp1 NEqual pp2 )\n-> logical\nNote:\nThe operators EQ, NE, LT, GT, LE and GE are sometimes referred to as comparator or relational operators; NOT, AND and OR are sometimes referred to as Boolean operators. Refer to Precision of Comparisons for tolerances in comparing numbers.\n\n\n\nPositions, Directions and Orientations in Expressions\nPrecision of Comparisons\nCompare Positions\nCompare Positions\nPositions, Directions and Orientations in Expressions\nNote\n:\ncomparator\nrelational\nBoolean\nPrecision of Comparisons\nSynopsis\nlog1 AND log2\n-> logical\nDescription\nSide Effects\nExample\nTRUE and FALSE -> FALSE\nEQ and NE\nSynopsis\nDescription\nCompare Positions\nSide Effects\n\u2019N 10 ne U 10\u2019\nExample\n( 1.0 eq 2.0) -> FALSE\nErrors\nSynopsis\n( number1 GT number2 )\n> logical\n( pos1 GT pos2 )\n> logical\n( number1 GE number2 )\n> logical\n( pos1 GE pos2 )\n> logical\n( number1 LE number2 )\n> logical\n( pos1 LE pos2 )\n> logical\n( number1 LT number2 )\n> logical\n( pos1 LT pos2 )\n> logical\nDescription\nCompare Positions\nSide Effects\n\u2019N 10 gt U 10\nExample\n( 1.0 LT 2.0) -> TRUE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\n( N 0 E 10 GT N 10 E 0 ) -FALSE\nErrors\nSynopsis\nNOT log1\n-> logical\nDescription\nSide Effects\nExample\nnot TRUE -> FALSE\nErrors\nSynopsis\nOR log2\n-> logical\nDescription\nSide Effects\nExample\nTRUE or FALSE -> TRUE\nErrors"}
{"Headers": "Logical Functions", "Content": "The logical functions available are:\nBADREF\nDEFINED,UNDEFINED\nCREATED\nDELETED\nEMPTY\nIFTRUE\nMATCHWILD\nMODIFIED\nUNSET\nVLOGICAL\nBADREF\n\nDEFINED,UNDEFINED\n\nCREATED\n\nDELETED\n\nEMPTY\n\nIFTRUE\n\nMATCHWILD\n\nMODIFIED\n\nUNSET\n\nVLOGICAL\n\nBADREF (id)\n-> logical\nTRUE if id is invalid, else FALSE.\nNone\nBADREF(TREF) -> \u2019true\u2019 if TREF=nulref\nNone.\nDEFined (variable_name)\n-> logical\nDEFined (variable_name,number)\n-> logical\nUNDEFined (variable_name)\n-> logical\nUNDEFined (variable_name , number)\n-> logical\nWith one argument, DEFINED is true only if the scalar variable, the array variable or the array variable element exists.\nWith two arguments, DEFINED is true only if the first argument is an array variable which has a value for the index denoted by the second argument.\nUNDEFINED( !foo ) is equivalent to NOT DEFINED( !foo ).\nNone.\nDEFINED ( !var ) -> TRUE\nDEFINED ( !array ) -> TRUE\nDEFINED ( !array[1] )) -> TRUE\nDEFINED ( !array , 1 ) -> TRUE\nDEFINED ( !var) -> FALSE\nUNDEFINED ( !array) -> TRUE\nDEFINED ( !array , 3 ) -> FALSE\nNone.\nCREATED\n-> logical\nReturns TRUE if the element has been created since the set date.\nNone.\nCREATED -> TRUE\nNone.\nDELETED\n-> logical\nReturns TRUE if the element has been deleted since the set date.\nNone.\nDELETED -> TRUE\nNone.\nEMPTY(text)\n-> logical\nReturns TRUE if text is a zero length string, else FALSE\nNone.\nEMPTY(\u2018\u2019) -> TRUE\nEMPTY(\u2018not empty\u2019) -> FALSE\nNone.\nIFTrue(logical, anyA, anyB)\n-> logical\nThe first argument is a logical value or expression.\nThe second and third arguments may be of any type BUT THEY MUST BE OF THE SAME TYPE.\nReturns a value that is the SAME TYPE as the second and third arguments.\nReturns anyA if logical evaluates to TRUE, anyB if logical evaluates to FALSE.\nanyA and anyB can be IFTRUE functions themselves (as long as they return consistent types) so IF constructs can be nested.ds.\nNone.\nIFT (SPREF EQ /A3B/GC50, 'BLUE', 'RED'\niftrue (gwei gt 1tonne, /INSUL/THICK, /INSUL/THIN)\n-> BLUE\n->INSUL/THICK\nNormal number of argument errors and Mismatched second and third arguments:\n(2,497) TYPE MISMATCH: unmatched or illegal argument type for IFTRUE function.\nMATCHW/ILD( text1, text2)\n-> logical\nMATCHW/ILD( text1, text2, text3)\n-> logical\nMATCHW/ILD( text1, text2, text3, text4)\n-> logical\nMatches string text2 to string text1. If they are the same then returns TRUE, else FALSE. text2 may contain wildcard characters.\nThe defaults for wildcards are \u2018*\u2019 for any number of characters, and \u2018?\u2019 for a single character.\nWith three arguments, the multiple wildcard character \u2018*\u2019 may be redefined by text3.\nWith four arguments the single wildcard character \u2018?\u2019 may be redefined by text4.\nNone\nMATCHW/ILD(\u2019** text\u2019,\u2019**!\u2019,\u2019!\u2019) -> TRUE\nNone.\n\n                                   .-----------------------------------.\n                                 /                                    |\n>- MODIFIED-(-+- attname -------*- DESCENDANTS \u2011-+-+-comma +-attname \u2011\u2019\n              |                 |                | |\n              |- DESCENDANTS -. |- SIGNIFICANT --| |\n              |               | |                | |\n              |- SIGNIFICANT--| |- PRIMARY ----- | |\n              |               | |                | |\n              |- PRIMARY -----| |- OFFSPRING-----| |\n              |               | |                | |\n              |- OFFSPRING ---| \u2018----------------\u2019 |\n              |               |                    |\n              |               |                    |\n              |               |                    |\n              \u2018---------------+--------------------+--+-- ) - OF \u2011 id \u00c6\n                                                  |\n                                                   \u2018-\u00c6\n\nFor sophisticated queries relating to modifications. Returns TRUE if a modification has taken place.\nEach attribute name may be followed by the following qualifying keywords:\nOFFSPRING, to check this element and members\nSIGNIF, to check all elements for which this element represents the significant one;\nPRIMARY, check all elements for which this element represents the primary one;\nDESCENDANTS, this element and everything below (descendants).\nThe \u2018OF\u2019 syntax may be used as for attributes.\nThe MODIFIED function or the GEOM, CATTEXT and CATMOD pseudo-attributes.\nThe MODIFIED, DELETED and CREATED functions may go anywhere within an AVEVA E3D\u2122 PML1 expression. i.e. after Q/VAR and within collections\nNone\nQ (MODIFIED())\nReturns TRUE if element has changed at all since the comparison date.\nIt will also return TRUE if the element has been created since the comparison date.\nQ MODIFIED(POS,ORI)\nReturns TRUE if POS or ORI modified since the comparison date.\nQ MODIFIED(P1 POS)\nReturns TRUE if the position of P1 has changed.\nQ MODIFIED(GEOM DESCENDANTS\nReturns TRUE if any geometry for item or any descendants has changed\nQ MODIFIED(PRIMARY)\nReturns TRUE if any element for which this element is primary, has changed.\nQ MODIFIED() OF /PIPE1\nReturns TRUE if /PIPE1 has been modified since the comparison date.\nQ (BUIL OR MODIFIED()OR ELECREC OF NEXT )\n\nNone.\nThe MODIFIED, DELETED and CREATED functions are not implemented within PML2 expressions.\nUNSET(value)\n-> logical\nReturns TRUE if value is unset, else FALSE. The value can be of any data type including ARRAYS. Normally it will be an AVEVA E3D\u2122 attribute.\nNone.\nUNSET( DESC )\nTRUE where DESC is an unset text attribute\nUNSET(CRFA)\nFALSE where CRFA contains unset reference attributes\nNone.\nVLOGICAL is used for the late evaluation of variables.\nVLOGICAL ( variable_name ))\n-> logical\nVLOGICAL ( variable_name , number)\n-> logical\nWith one argument, return the value of the scalar variable or the value of the array variable element as a logical.\nWith two arguments, return the value of the element corresponding to the index number as a logical.\nThe rules of conversion are:\nTRUE for the strings \u2019T\u2019, \u2019TR\u2019, \u2019TRU\u2019 or \u2019TRUE\u2019 (case insensitive) or any numeric value not equal to zero;\nFALSE for the strings \u2019F\u2019, \u2019FA\u2019, \u2019FAL\u2019, \u2019FALS\u2019 or \u2019FALSE\u2019 (case insensitive) or a numeric value equal to zero.\nScalar variables may not be indexed. For example, VTEXT(!var[1]) will return an error.\nArray variables must have an index. For example, VTEXT (!array) will return an error.\nThe value cannot be translated into a logical.\nSee also VTEXT, used for late evaluation when a text result is required; and VVALUE, used for late evaluation when a numeric result is required.\nIf the scalar variable, the array variable, or the array variable element does not exist, the result is undefined.\nVLOG ( !array[1] ) -> TRUE\nVLOG ( !array , 2 ) -> FALSE\nNone.\n\nBADREF\nDEFINED,UNDEFINED\nCREATED\nDELETED\nEMPTY\nIFTRUE\nMATCHWILD\nMODIFIED\nUNSET\nVLOGICAL\nSynopsis\nBADREF (id)\n-> logical\nDescription\nTRUE if id is invalid, else FALSE.\nSide Effects\nNone\nExample\nBADREF(TREF) -> \u2019true\u2019 if TREF=nulref\nErrors\nNone.\nSynopsis\nDEFined (variable_name)\n-> logical\nDEFined (variable_name,number)\n-> logical\nUNDEFined (variable_name)\n-> logical\nUNDEFined (variable_name , number)\n-> logical\nDescription\nWith one argument, DEFINED is true only if the scalar variable, the array variable or the array variable element exists.\nWith two arguments, DEFINED is true only if the first argument is an array variable which has a value for the index denoted by the second argument.\nUNDEFINED( !foo ) is equivalent to NOT DEFINED( !foo ).\nSide Effects\nNone.\nExample\nDEFINED ( !var ) -> TRUE\nDEFINED ( !array ) -> TRUE\nDEFINED ( !array[1] )) -> TRUE\nDEFINED ( !array , 1 ) -> TRUE\nDEFINED ( !var) -> FALSE\nUNDEFINED ( !array) -> TRUE\nDEFINED ( !array , 3 ) -> FALSE\nErrors\nNone.\nSynopsis\nCREATED\n-> logical\nDescription\nReturns TRUE if the element has been created since the set date.\nSide Effects\nNone.\nExample\nCREATED -> TRUE\nErrors\nNone.\nSynopsis\nDELETED\n-> logical\nDescription\nReturns TRUE if the element has been deleted since the set date.\nSide Effects\nNone.\nExample\nDELETED -> TRUE\nErrors\nNone.\nSynopsis\nEMPTY(text)\n-> logical\nDescription\nReturns TRUE if text is a zero length string, else FALSE\nSide Effects\nNone.\nExample\nEMPTY(\u2018\u2019) -> TRUE\nEMPTY(\u2018not empty\u2019) -> FALSE\nErrors\nNone.\nSynopsis\nIFTrue(logical, anyA, anyB)\n-> logical\nThe first argument is a logical value or expression.\nThe second and third arguments may be of any type BUT THEY MUST BE OF THE SAME TYPE.\nReturns a value that is the SAME TYPE as the second and third arguments.\nDescription\nReturns anyA if logical evaluates to TRUE, anyB if logical evaluates to FALSE.\nanyA and anyB can be IFTRUE functions themselves (as long as they return consistent types) so IF constructs can be nested.ds.\nSide Effects\nNone.\nExample\nIFT (SPREF EQ /A3B/GC50, 'BLUE', 'RED'\niftrue (gwei gt 1tonne, /INSUL/THICK, /INSUL/THIN)\n-> BLUE\n->INSUL/THICK\nErrors\nNormal number of argument errors and Mismatched second and third arguments:\n(2,497) TYPE MISMATCH: unmatched or illegal argument type for IFTRUE function.\nSynopsis\nMATCHW/ILD( text1, text2)\n-> logical\nMATCHW/ILD( text1, text2, text3)\n-> logical\nMATCHW/ILD( text1, text2, text3, text4)\n-> logical\nDescription\nMatches string text2 to string text1. If they are the same then returns TRUE, else FALSE. text2 may contain wildcard characters.\nThe defaults for wildcards are \u2018*\u2019 for any number of characters, and \u2018?\u2019 for a single character.\nWith three arguments, the multiple wildcard character \u2018*\u2019 may be redefined by text3.\nWith four arguments the single wildcard character \u2018?\u2019 may be redefined by text4.\nSide Effects\nNone\nExample\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019??big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019???*big*\u2019) -> FALSE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*beer\u2019) -> TRUE\nMATCHW/ILD(\u2019** text\u2019,\u2019**!\u2019,\u2019!\u2019) -> TRUE\nErrors\nNone.\nSynopsis\n                                   .-----------------------------------.\n                                 /                                    |\n>- MODIFIED-(-+- attname -------*- DESCENDANTS \u2011-+-+-comma +-attname \u2011\u2019\n              |                 |                | |\n              |- DESCENDANTS -. |- SIGNIFICANT --| |\n              |               | |                | |\n              |- SIGNIFICANT--| |- PRIMARY ----- | |\n              |               | |                | |\n              |- PRIMARY -----| |- OFFSPRING-----| |\n              |               | |                | |\n              |- OFFSPRING ---| \u2018----------------\u2019 |\n              |               |                    |\n              |               |                    |\n              |               |                    |\n              \u2018---------------+--------------------+--+-- ) - OF \u2011 id \u00c6\n                                                  |\n                                                   \u2018-\u00c6\nDescription\nFor sophisticated queries relating to modifications. Returns TRUE if a modification has taken place.\nEach attribute name may be followed by the following qualifying keywords:\nOFFSPRING, to check this element and members\nSIGNIF, to check all elements for which this element represents the significant one;\nPRIMARY, check all elements for which this element represents the primary one;\nDESCENDANTS, this element and everything below (descendants).\nThe \u2018OF\u2019 syntax may be used as for attributes.\nThe MODIFIED function or the GEOM, CATTEXT and CATMOD pseudo-attributes.\nThe MODIFIED, DELETED and CREATED functions may go anywhere within an AVEVA E3D\u2122 PML1 expression. i.e. after Q/VAR and within collections\nSide Effects\nNone\nExample\nQ (MODIFIED())\nReturns TRUE if element has changed at all since the comparison date.\nIt will also return TRUE if the element has been created since the comparison date.\nQ MODIFIED(POS,ORI)\nReturns TRUE if POS or ORI modified since the comparison date.\nQ MODIFIED(P1 POS)\nReturns TRUE if the position of P1 has changed.\nQ MODIFIED(GEOM DESCENDANTS\nReturns TRUE if any geometry for item or any descendants has changed\nQ MODIFIED(PRIMARY)\nReturns TRUE if any element for which this element is primary, has changed.\nQ MODIFIED() OF /PIPE1\nReturns TRUE if /PIPE1 has been modified since the comparison date.\nQ (BUIL OR MODIFIED()OR ELECREC OF NEXT )\nErrors\nNone.\nSynopsis\nUNSET(value)\n-> logical\nDescription\nReturns TRUE if value is unset, else FALSE. The value can be of any data type including ARRAYS. Normally it will be an AVEVA E3D\u2122 attribute.\nSide Effects\nNone.\nExample\nUNSET( DESC )\nTRUE where DESC is an unset text attribute\nUNSET(CRFA)\nFALSE where CRFA contains unset reference attributes\nErrors\nNone.\nSynopsis\nVLOGICAL ( variable_name ))\n-> logical\nVLOGICAL ( variable_name , number)\n-> logical\nDescription\nWith one argument, return the value of the scalar variable or the value of the array variable element as a logical.\nWith two arguments, return the value of the element corresponding to the index number as a logical.\nThe rules of conversion are:\nTRUE for the strings \u2019T\u2019, \u2019TR\u2019, \u2019TRU\u2019 or \u2019TRUE\u2019 (case insensitive) or any numeric value not equal to zero;\nFALSE for the strings \u2019F\u2019, \u2019FA\u2019, \u2019FAL\u2019, \u2019FALS\u2019 or \u2019FALSE\u2019 (case insensitive) or a numeric value equal to zero.\nScalar variables may not be indexed. For example, VTEXT(!var[1]) will return an error.\nArray variables must have an index. For example, VTEXT (!array) will return an error.\nThe value cannot be translated into a logical.\nSee also VTEXT, used for late evaluation when a text result is required; and VVALUE, used for late evaluation when a numeric result is required.\nSide Effects\nIf the scalar variable, the array variable, or the array variable element does not exist, the result is undefined.\nExample\nVLOG ( !array[1] ) -> TRUE\nVLOG ( !array , 2 ) -> FALSE\nErrors\nNone.\n\n\n\nSynopsis\nBADREF (id)\n-> logical\nDescription\nid\nSide Effects\nExample\nBADREF(TREF) -> \u2019true\u2019 if TREF=nulref\nErrors\nSynopsis\nDEFined (variable_name)\n-> logical\nDEFined (variable_name,number)\n-> logical\nUNDEFined (variable_name)\n-> logical\nUNDEFined (variable_name , number)\n-> logical\nDescription\nSide Effects\nExample\nDEFINED ( !var ) -> TRUE\nDEFINED ( !array ) -> TRUE\nDEFINED ( !array[1] )) -> TRUE\nDEFINED ( !array , 1 ) -> TRUE\nDEFINED ( !var) -> FALSE\nUNDEFINED ( !array) -> TRUE\nDEFINED ( !array , 3 ) -> FALSE\nErrors\nSynopsis\nCREATED\n-> logical\nDescription\nSide Effects\nExample\nCREATED -> TRUE\nErrors\nSynopsis\nDELETED\n-> logical\nDescription\nSide Effects\nExample\nDELETED -> TRUE\nErrors\nSynopsis\nEMPTY(text)\n-> logical\nDescription\nSide Effects\nExample\nEMPTY(\u2018\u2019) -> TRUE\nEMPTY(\u2018not empty\u2019) -> FALSE\nErrors\nSynopsis\nIFTrue(logical, anyA, anyB)\n-> logical\nDescription\nSide Effects\nExample\nIFT (SPREF EQ /A3B/GC50, 'BLUE', 'RED'\niftrue (gwei gt 1tonne, /INSUL/THICK, /INSUL/THIN)\n-> BLUE\n->INSUL/THICK\nErrors\nSynopsis\nMATCHW/ILD( text1, text2)\n-> logical\nMATCHW/ILD( text1, text2, text3)\n-> logical\nMATCHW/ILD( text1, text2, text3, text4)\n-> logical\nDescription\ntext2\ntext1\ntext2\ntext3\ntext4\nSide Effects\nExample\nMATCHW/ILD(\u2019** text\u2019,\u2019**!\u2019,\u2019!\u2019) -> TRUE\nErrors\nSynopsis\n                                 .-----------------------------------.\n                                 /                                    |\n>- MODIFIED-(-+- attname -------*- DESCENDANTS \u2011-+-+-comma +-attname \u2011\u2019\n              |                 |                | |\n              |- DESCENDANTS -. |- SIGNIFICANT --| |\n              |               | |                | |\n              |- SIGNIFICANT--| |- PRIMARY ----- | |\n              |               | |                | |\n              |- PRIMARY -----| |- OFFSPRING-----| |\n              |               | |                | |\n              |- OFFSPRING ---| \u2018----------------\u2019 |\n              |               |                    |\n              |               |                    |\n              |               |                    |\n              \u2018---------------+--------------------+--+-- ) - OF \u2011 id \u00c6\n                                                  |\n                                                   \u2018-\u00c6\nDescription\nSide Effects\nExample\nQ (MODIFIED())\nQ MODIFIED(POS,ORI)\nQ MODIFIED(P1 POS)\nQ MODIFIED(GEOM DESCENDANTS\nQ MODIFIED(PRIMARY)\nQ MODIFIED() OF /PIPE1\nQ (BUIL OR MODIFIED()OR ELECREC OF NEXT )\nErrors\nSynopsis\nUNSET(value)\n-> logical\nDescription\nvalue\nSide Effects\nNone.\nExample\nUNSET( DESC )\nTRUE where DESC is an unset text attribute\nUNSET(CRFA)\nFALSE where CRFA contains unset reference attributes\nErrors\nSynopsis\nVLOGICAL ( variable_name ))\n-> logical\nVLOGICAL ( variable_name , number)\n-> logical\nDescription\nVTEXT(!var[1])\nVTEXT (!array)\nSide Effects\nExample\nVLOG ( !array[1] ) -> TRUE\nVLOG ( !array , 2 ) -> FALSE\nErrors"}
{"Headers": "Logical Array Expressions", "Content": "Logical array expressions can contain:\nAVEVA E3D Design attributes of type logical array. For example, LOGARR where LOGARR is a User Dfined Attribute (UDA) of type logical.\nLogical constants. The constants available are: TRUE, ON, YES for true; and FALSE, OFF, NO for false.\nLogical operators. Refer to Logical Operators.\nLogical functions. Refer to Logical Functions.\nAVEVA E3D Design attributes of type logical array. For example, LOGARR where LOGARR is a User Dfined Attribute (UDA) of type logical.\nAVEVA E3D Design attributes of type logical array. For example, LOGARR where LOGARR is a User Dfined Attribute (UDA) of type logical.\nLogical constants. The constants available are: TRUE, ON, YES for true; and FALSE, OFF, NO for false.\nLogical constants. The constants available are: TRUE, ON, YES for true; and FALSE, OFF, NO for false.\nLogical operators. Refer to Logical Operators.\nLogical operators. Refer to Logical Operators.\nLogical functions. Refer to Logical Functions.\nLogical functions. Refer to Logical Functions.\n\n\n\nLogical Operators\nLogical Functions\nLogical Operators\n.\nLogical Functions\n."}
{"Headers": "Numeric (Real) Expressions", "Content": "In AVEVA E3D Design expressions, integers are treated as reals; they are fully interchangeable. Numeric expressions can contain:\nNumbers, for example: 32, 10.1.\nNumbers can be given as integer exponents, for example: 10 exp 5, and 5 E 6.\nValues (numbers) can be qualified by units. This introduces dimensional analysis into the expression. The valid units are any standard appropriate unit qualifiers for example MM, M/etres, IN/ches, FT, FEET, kg, lb, kgf/m3, pascal. These may be preceded by SQU/are, CUBIC, CUB/e to denote non-linear Values, or alternatively they can have power indices appended. For example: 100 mm, 10 exp 5 cubic feet, 10m3, 20newton.m-2. Feet and inches can be shown as, for example, 10'6.\nAVEVA E3D Design attributes of type number, for example: XLEN.\nPosition, direction and orientation attributes which have a subscript to indicate which part of the array is required. For example, POS[2] means the second element of the POSITION attribute; that is, the northing.\nNote:\nPosition, direction and orientation attributes without subscripts can only be used in number array expressions.\nThe keyword PI (3.142).\nNumeric operators.\nNumeric functions.\nNumbers, for example: 32, 10.1.\nNumbers, for example: 32, 10.1.\nNumbers can be given as integer exponents, for example: 10 exp 5, and 5 E 6.\nNumbers can be given as integer exponents, for example: 10 exp 5, and 5 E 6.\nValues (numbers) can be qualified by units. This introduces dimensional analysis into the expression. The valid units are any standard appropriate unit qualifiers for example MM, M/etres, IN/ches, FT, FEET, kg, lb, kgf/m3, pascal. These may be preceded by SQU/are, CUBIC, CUB/e to denote non-linear Values, or alternatively they can have power indices appended. For example: 100 mm, 10 exp 5 cubic feet, 10m3, 20newton.m-2. Feet and inches can be shown as, for example, 10'6.\nValues (numbers) can be qualified by units. This introduces dimensional analysis into the expression. The valid units are any standard appropriate unit qualifiers for example MM, M/etres, IN/ches, FT, FEET, kg, lb, kgf/m3, pascal. These may be preceded by SQU/are, CUBIC, CUB/e to denote non-linear Values, or alternatively they can have power indices appended. For example: 100 mm, 10 exp 5 cubic feet, 10m3, 20newton.m-2. Feet and inches can be shown as, for example, 10'6.\nAVEVA E3D Design attributes of type number, for example: XLEN.\nAVEVA E3D Design attributes of type number, for example: XLEN.\nPosition, direction and orientation attributes which have a subscript to indicate which part of the array is required. For example, POS[2] means the second element of the POSITION attribute; that is, the northing.\nNote:\nPosition, direction and orientation attributes without subscripts can only be used in number array expressions.\nPosition, direction and orientation attributes which have a subscript to indicate which part of the array is required. For example, POS[2] means the second element of the POSITION attribute; that is, the northing.\nThe keyword PI (3.142).\nThe keyword PI (3.142).\nNumeric operators.\nNumeric operators.\nNumeric functions.\nNumeric functions.\n\n\n\nPOS[2]\nNote"}
{"Headers": "Numeric (Real) Operators", "Content": "The numeric operators available are:\n+\nAddition.\n-\nSubtraction.\n*\nMultiplication.\n/\nDivision.\n\nOperator\nComments\n+\nAddition.\n-\nSubtraction.\n*\nMultiplication.\n/\nDivision.\n\n\n"}
{"Headers": "ADD and SUBTRACT (+ and -)", "Content": "The add and subtract functions available are\nnumber + number\n-> number\nnumber \u2011 number\n-> number\n+ number\n-> number\n- number\n-> number\nAdd or subtract two numbers. They can also be used as unary operators at the beginning of a parenthesized sub-expression.\nUnits are consolidated across add and subtract and the result is returned in current units of the physical quantity, for example when current distance units are inches\nIf only one value has a unit qualifier the other is assumed to be in current units of that physical quantity for example:\nIf the two values have conflicting units a warning is issued and a value is returned with no units assuming both values are in the database units of their respective quantities which is mm and Kg in the example:\nq (1ft + 1kg ) will return 305.8\n1 + 2 -> 3.0\n1 \u2011 2 -> 1.0\n+ 1 -> 1.0\n- 1 -> -1.0\nFloating point underflow.\n\nSynopsis\nnumber + number\n-> number\nnumber \u2011 number\n-> number\n+ number\n-> number\n- number\n-> number\nDescription\nAdd or subtract two numbers. They can also be used as unary operators at the beginning of a parenthesized sub-expression.\nSide Effects\nUnits are consolidated across add and subtract and the result is returned in current units of the physical quantity, for example when current distance units are inches\nq (1ft + 100mm) will return 15.9in\nIf only one value has a unit qualifier the other is assumed to be in current units of that physical quantity for example:\nq (1ft + 100 ) will return 112in\nIf the two values have conflicting units a warning is issued and a value is returned with no units assuming both values are in the database units of their respective quantities which is mm and Kg in the example:\nq (1ft + 1kg ) will return 305.8\nExample\n1 + 2 -> 3.0\n1 \u2011 2 -> 1.0\n+ 1 -> 1.0\n- 1 -> -1.0\nErrors\nFloating point underflow.\n\n\n\nSynopsis\nnumber + number\n-> number\nnumber \u2011 number\n-> number\n+ number\n-> number\n- number\n-> number\nDescription\nSide Effects\nExample\n1 + 2 -> 3.0\n1 \u2011 2 -> 1.0\n+ 1 -> 1.0\n- 1 -> -1.0\nErrors"}
{"Headers": "MULTIPLY and DIVIDE (* and /)", "Content": "The multiply and divide functions available are\nnumber * number\n-> number\nnumber / number\n-> number\nMultiply or divide two numbers. They can also be used as unary operators at the beginning of a parenthesized sub-expression. Numeric underflow is not considered to be an error and neither is it flagged as a warning. The result returned is zero.\nUnits are consolidated across Multiply and Divide. The result is returned in the current units of the physical quantity of the result for example when current units of pressure are psi then:\nIf one value has no unit it is assumed to be a scaling factor. This also applies to reciprocal physical quantities. For example:\nfor (10 / XLEN) will return 2mm-1 when XLEN is 5mm\n2 * 3 -> 6.0\n2 / 3 -> 0.666666666\nDivide by zero.\n\nSynopsis\nnumber * number\n-> number\nnumber / number\n-> number\nDescription\nMultiply or divide two numbers. They can also be used as unary operators at the beginning of a parenthesized sub-expression. Numeric underflow is not considered to be an error and neither is it flagged as a warning. The result returned is zero.\nSide Effects\nUnits are consolidated across Multiply and Divide. The result is returned in the current units of the physical quantity of the result for example when current units of pressure are psi then:\nq (20kgf/ 1 cm2 ) will return 284.47PSI\nIf one value has no unit it is assumed to be a scaling factor. This also applies to reciprocal physical quantities. For example:\nfor (10 / XLEN) will return 2mm-1 when XLEN is 5mm\nExample\n2 * 3 -> 6.0\n2 / 3 -> 0.666666666\nErrors\nDivide by zero.\n\n\n\nSynopsis\nnumber * number\n-> number\nnumber / number\n-> number\nDescription\nSide Effects\n(10 / XLEN)\nExample\n2 * 3 -> 6.0\n2 / 3 -> 0.666666666\nErrors"}
{"Headers": "Numeric (Real) Functions", "Content": "All referenced units are current units. The numeric functions available are:\nABS ( number1 )\nGives the absolute value of a number\nACOS ( number1 )\nGives the arc cosine of a number, in degrees.\nASIN ( number1 )\nGives the arc sine of a number, in degrees.\nATAN ( number1 )\nGives the arc tangent of a number, in degrees.\nATANT ( number1, number2 )\n\nGives the arc tangent of number1/number2, in degrees, with the appropriate sign.\nALOG ( number1 )\nGives the exponential function (natural anti-log) of a number.\nARRAY(pos or dir or ori)\n\nConverts a position, direction or orientation value or attribute into three numbers.\nARRAYSIZE ( variable-name )\n\nGives the size of an array variable.\nARRAYWIDTH( variable-name )\n\nGives the largest display width of any string in array variable-name.\nCOMPONENT dir OF pos2\nGives the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nINT ( number1 )\nGives the truncated integer value of a number.\nSIN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nCOS ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nTAN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nLENGTH ( text1 )\nGives the length of text1.\nLOG ( number1 )\nGives the natural logarithm of a number.\nMATCH ( text1, text2 )\nGives the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nMAX ( number1, number2[ , number3 [. . .]]) )\n\nGives the maximum value of the arguments.\nMIN ( number1, number2[ , number3 [. . .]]) )\n\nGives the minimum value of the arguments.\nNEGATE\nMultiply a number by -1.0.\nNINT ( number1 )\nGives the nearest integer to a real. NINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nOCCUR ( text1, text2 )\nGives the number of times string text2 occurs in string text1.\nREAL ( text1 )\nTry to read a number at the beginning of text1.\nPOWER ( number1, number2 )\n\nGives the value of number1 raised to the power number2.\nSQRT ( number1 )\nGives the square root of a number.\nVVALUE ( variable-name )\n\nUsed for late evaluation of variables. Gives a real value.\nABS ( number1 )\n-> number\nReturns the absolute value of a real.\nNone.\nABS ( -3.2 ) -> 3.2\nNone.\nAll these will return values in current angle units.\nASIN ( number1 )\n-> number\nACOS ( number1 )\n-> number\nATAN ( number1 )\n-> number\nATANT ( number1, number2 )\n-> number\nReturn the arc-cosine, arc-sine or arc-tangent of a number, in degrees.\nATANT returns the arc-tangent of number1/number2 with the appropriate sign. ATANT is useful where the second value is near or equal to zero.\nFor example, (6 0 ATANT) will give the correct result of 90 degrees, but (6 0 D ATAN) will indicate an error when trying to divide by zero.\nNone.\nACOS ( 0.8660254 ) -> 30degrees\nArgument of ACOS or ASIN out of range [-1.0,+1.0]\nATANT (0.0,0.0) is undefined.\nALOG ( number1 )\n-> number\nReturn the exponential function (natural anti-log) of a number.\nNumeric underflow causes the result to be set to zero.\nALOG( -0.7 ) -> 0.4965853\nFloating point overflow.\nARRAY(pos or dir or ori)\n-> number\nConverts a position, direction or orientation value or attribute into three numbers.\nNone\nARRAY(e100 ) -> 100 0 0\nNone.\nARRAYSize ( variable-name )\n-> number\nGive the size of an array variable.\nIf the array variable does not exist, the result is undefined.\nARRAYSIZE(!array) -> 2.0\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nARRAYWIDTH ( variable-name )\n-> number\nGive the largest display with of any string in array variable_name.\nNone.\nIf an array contains the following values:\n!ARRAY[1] \u2019Bread\u2019\n!ARRAY[2] \u2019is\u2019\n!ARRAY[3] \u2019for\u2019\n!ARRAY[4] \u2019life,\u2019\n!ARRAY[5] \u2019not\u2019\n!ARRAY[6] \u2019just\u2019\n!ARRAY[7] \u2019for\u2019\n!ARRAY[8] \u2019breakfast\u2019\nThen\nARRAYWIDTH(!ARRAY -> 9\ndefines the length of \u2019breakfast\u2019.\n\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nCOMPonent dir1 OF pos2\n-> text\nReturns the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nNone.\nCOMP E 45 N of N 0 E 100 U 50 -> 70.710\nNone.\nDISTConvert ( number )\n-> number\nReturns a distance value cast from the input number.\nThe input value is converted to its database units (if it is a physical quantity) and then cast to database units of distance (i.e. mm) and presented in current units of distance.\nNone.\nWhen current distance units are mm\ndistc(1000)\ndistc(10metre)\ndistc( 5pascal)\ndistc (5atm)\n\n-> 1000mm\n-> 10000mm\n-> 5mm\n-> 506625mm\nWhen current distance units are inch\ndistc(1000)\ndistc(10metre)\ndistc( 5pascal)\ndistc (5atm)\n\n-> 39.4in\n-> 393.7in\n-> 0.2in\n-> 19945.9in\nNone.\nAll these will accept values qualified by angle units. If no unit is supplied the value is assumed to be in current angle units (usually degrees).\nSINe ( number1 )\n-> number\nCOSine ( number1 )\n-> number\nTANgent ( number1 )\n-> number\nReturn the sine, cosine or tangent value of a number (considered to be in degrees).\nNone.\nCOS ( 0.0 ) returns 1.0\nTAN ( 45.0 degrees ) returns 1.0\nTAN (0.785 radians) ) returns 0.9992\nDivision by zero for TAN if the sine is (nearly) equal to zero.\nINT ( number1 )\n-> number\nReturn the truncated integer value of a number.\nNone.\nINT ( -23.7 ) -> -23.0\nInteger overflow.\nLENgth ( text1 )\n-> number\nReturn the length of text1.\nNone.\nLENGTH ( \u2019abcdef\u2019 ) -> 6.0\nLENGTH ( \u2019\u2019 ) -> 0.0\nNone.\nLOG ( number1 )\n-> number\nReturn the natural logarithm of a number.\nNone.\nLOG( 3 ) -> 1 0986123\nNegative arguments.\nMATch ( text1 , text2)\n-> number\nReturn the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nNone.\nMATCH ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> 3.0\nMATCH ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> 0.0\nMATCH ( \u2019abcdef\u2019 , \u2019\u2019 ) -> 1.0\nNone.\nMAX ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nMIN ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nReturn the maximum or minimum value of the arguments.\nValues being evaluated are assumed to of a common physical quantity.\nIf no unit qualifiers are supplied they are simply numbers.\nIf a physical quantity is defined the result will be in current units of that quantity.\nIf unqualified numbers are mixed with unit values they are assumed to be in the current units of that physical quantity.\nIf quantities are in mixed units they are all compared in comparison to a standard unit.\nIf quantities are of different types of physical quantities a warning is issued and the numeric result compares the values in their database units.\nMin and Max return a value with the same dimension as that of their arguments.\nMAX ( 1 , 3.4 ) -> 3.4\nMIN ( 7.6 , -12.33 , 2.3 ) -> -12.33\nMIN (7.6ft, 12.33inch, 1000mm ) -> 12.3 in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1000 ) -> 1000in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1kg ) -> 2316.5 (database mm equivalent of 7.6ft)\nNone.\nNEGate ( number1 )\n-> number\nMultiply a real by -1.0.\nNone.\nNEG ( 1 ) -> -1.0\nNone.\nNINT ( number1 )\n-> number\nReturn the nearest integer to a real. NINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nNone.\nNINT ( 1.1 ) -> 1.0\nNINT ( -23.7 ) -> -24.0\nNINT ( 1.5 ) -> 2.0\nNINT ( -11.5 ) -> -12.0\nInteger overflow.\nOCCUR(text1, text2)\n-> integer\nCounts the number of times string text2 occurs in string text1\nNone.\nOCCUR (\u2019ABBACCBBBBBAB\u2019, \u2019BB\u2019) -> 3\nOCCUR(\u2019ZZZZZZZZZZZ\u2019, \u2019A\u2019) -> 0\nNone.\nREAL ( text1 )\n-> number\nTry to read a real number at the beginning of text1.\nNote that if text is in the form of an exponent, (-12E-1 in the third example), there must be no spaces in it.\nNote: this function was formerly called NUMBER.\nNumeric underflow causes the result to be set to zero.\nIf the text string contains units they are ignored and the value only is returned.\nIf the test string contains text that is NOT a valid unit it will generate an error.\nIf the text string is space separated from the number it is completely ignored.\nREAL ( \u201912.34\u2019) -> 12.34\nREAL ( \u2019 7.23 E 3 meters\u2019 ) -> 7.23\nREAL ( \u2019 -12E-1 meters \u2019 ) -> -1.2\nREAL (' 1200 fred ' ) -> 1200\nREAL (' 1200fred ' ) -> returns an error\nThis will return the value of the number in the string IGNORING any unit qualifier. The unit qualifier must still be a valid unit qualifier. This is done so that output from $! And VAR ! commands can still be accepted by the REAL function.\nUnable to convert the text into a real number.\nPOWer ( number1 , number2 )\n-> real\nReturn the value of number1 raised to the power number2.\nIf the value being raised to a power is that of a physical quantity the result is also of a physical quantity.(in relevant current units).\nIf the resultant quantity is non physical (for example, by raising to a fractional power, or an extreme power, a warning is given and only the value of quantity is raised to the power.\nIf the power is a physical quantity this also gives a warning.\nPOWER ( -2 , 3 ) -> -8\nPOWER ( -2inch , 2 ) -> 4in2\nPOWER ( 2inch, 3.5 ) -> returns 11.314 with an error (i.e. 2**3.5)\nFloating point overflow.\nZero first argument and non-positive second argument (effectively divide by zero).\nNegative first argument and non-integer second argument.\nSQrt ( number1 )\n-> number\nReturn the square root of a real.\nUnits are consolidated across SQRT. The resultant value will be in current units of that quantity.\nIf the resultant quantity has no recognized physical dimension a warning is given and the value return will be a number relating to the input value in database units.\nSQRT ( 4 ) -> 2.0\nSQRT ( 4inch2 ) -> 2.0inch\nsqrt ( 4inch3 ) -> a warning and 256.02 which is sqrt (4*25.4mm)\nNegative argument.\nVVALUE is used for the late evaluation of PML variables.\nVVALue( variable_name )\n-> number\nVVALue( variable_name , number )\n-> number\nWith one argument, returns value of the scalar variable or value of the array variable element as a number.\nWith two arguments, returns value of the element corresponding to the index number as a number.\nThe value of the variable will be returned, irrespective of its units.\nThis will return the value of the number in the string IGNORING any unit qualifier. The unit qualifier must still be a valid unit qualifier. This is done so that output from $! And VAR ! commands can still be accepted by the VVAL function.\nIf the scalar variable, the array variable or the array variable element does not exist, the result is undefined.\nVVAL ( !array[1] ) -> 1.0\nVVAL ( !array , 2 ) -> 0.0\nScalar variable may not be indexed. For example, VTEXT (!var[1]) ) will return an error.\nArray variable must have an index. For example, VTEXT ( !array ) ) will return an error.\nThe string can not be converted to a number.\n\nFunction\nComments\nABS ( number1 )\nGives the absolute value of a number\nACOS ( number1 )\nGives the arc cosine of a number, in degrees.\nASIN ( number1 )\nGives the arc sine of a number, in degrees.\nATAN ( number1 )\nGives the arc tangent of a number, in degrees.\nATANT ( number1, number2 )\nGives the arc tangent of number1/number2, in degrees, with the appropriate sign.\nALOG ( number1 )\nGives the exponential function (natural anti-log) of a number.\nARRAY(pos or dir or ori)\nConverts a position, direction or orientation value or attribute into three numbers.\nARRAYSIZE ( variable-name )\nGives the size of an array variable.\nARRAYWIDTH( variable-name )\nGives the largest display width of any string in array variable-name.\nCOMPONENT dir OF pos2\nGives the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nINT ( number1 )\nGives the truncated integer value of a number.\nSIN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nCOS ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nTAN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in current units of angle (degrees) if value is unqualified).\nLENGTH ( text1 )\nGives the length of text1.\nLOG ( number1 )\nGives the natural logarithm of a number.\nMATCH ( text1, text2 )\nGives the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nMAX ( number1, number2[ , number3 [. . .]]) )\nGives the maximum value of the arguments.\nMIN ( number1, number2[ , number3 [. . .]]) )\nGives the minimum value of the arguments.\nNEGATE\nMultiply a number by -1.0.\nNINT ( number1 )\nGives the nearest integer to a real. NINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nOCCUR ( text1, text2 )\nGives the number of times string text2 occurs in string text1.\nREAL ( text1 )\nTry to read a number at the beginning of text1.\nPOWER ( number1, number2 )\nGives the value of number1 raised to the power number2.\nSQRT ( number1 )\nGives the square root of a number.\nVVALUE ( variable-name )\nUsed for late evaluation of variables. Gives a real value.\nSynopsis\nABS ( number1 )\n-> number\nDescription\nReturns the absolute value of a real.\nSide Effects\nNone.\nExample\nABS ( -3.2 ) -> 3.2\nErrors\nNone.\nSynopsis\nASIN ( number1 )\n-> number\nACOS ( number1 )\n-> number\nATAN ( number1 )\n-> number\nATANT ( number1, number2 )\n-> number\nDescription\nReturn the arc-cosine, arc-sine or arc-tangent of a number, in degrees.\nATANT returns the arc-tangent of number1/number2 with the appropriate sign. ATANT is useful where the second value is near or equal to zero.\nFor example, (6 0 ATANT) will give the correct result of 90 degrees, but (6 0 D ATAN) will indicate an error when trying to divide by zero.\nSide Effects\nNone.\nExample\nACOS ( 0.8660254 ) -> 30degrees\nErrors\nArgument of ACOS or ASIN out of range [-1.0,+1.0]\nATANT (0.0,0.0) is undefined.\nSynopsis\nALOG ( number1 )\n-> number\nDescription\nReturn the exponential function (natural anti-log) of a number.\nSide Effects\nNumeric underflow causes the result to be set to zero.\nExample\nALOG( -0.7 ) -> 0.4965853\nErrors\nFloating point overflow.\nSynopsis\nARRAY(pos or dir or ori)\n-> number\nDescription\nConverts a position, direction or orientation value or attribute into three numbers.\nSide Effects\nNone\nExample\nARRAY(e100 ) -> 100 0 0\nErrors\nNone.\nSynopsis\nARRAYSize ( variable-name )\n-> number\nDescription\nGive the size of an array variable.\nSide Effects\nIf the array variable does not exist, the result is undefined.\nExample\nARRAYSIZE(!array) -> 2.0\nErrors\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nSynopsis\nARRAYWIDTH ( variable-name )\n-> number\nDescription\nGive the largest display with of any string in array variable_name.\nSide Effects\nNone.\nExample\nIf an array contains the following values:\n!ARRAY[1] \u2019Bread\u2019\n!ARRAY[2] \u2019is\u2019\n!ARRAY[3] \u2019for\u2019\n!ARRAY[4] \u2019life,\u2019\n!ARRAY[5] \u2019not\u2019\n!ARRAY[6] \u2019just\u2019\n!ARRAY[7] \u2019for\u2019\n!ARRAY[8] \u2019breakfast\u2019\nThen\nARRAYWIDTH(!ARRAY -> 9\ndefines the length of \u2019breakfast\u2019.\nErrors\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nSynopsis\nCOMPonent dir1 OF pos2\n-> text\nDescription\nReturns the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nSide Effects\nNone.\nExample\nCOMP E 45 N of N 0 E 100 U 50 -> 70.710\nErrors\nNone.\nSynopsis\nDISTConvert ( number )\n-> number\nDescription\nReturns a distance value cast from the input number.\nThe input value is converted to its database units (if it is a physical quantity) and then cast to database units of distance (i.e. mm) and presented in current units of distance.\nSide Effects\nNone.\nExample\nWhen current distance units are mm\ndistc(1000)\ndistc(10metre)\ndistc( 5pascal)\ndistc (5atm)\n-> 1000mm\n-> 10000mm\n-> 5mm\n-> 506625mm\nWhen current distance units are inch\ndistc(1000)\ndistc(10metre)\ndistc( 5pascal)\ndistc (5atm)\n-> 39.4in\n-> 393.7in\n-> 0.2in\n-> 19945.9in\nErrors\nNone.\nSynopsis\nSINe ( number1 )\n-> number\nCOSine ( number1 )\n-> number\nTANgent ( number1 )\n-> number\nDescription\nReturn the sine, cosine or tangent value of a number (considered to be in degrees).\nSide Effects\nNone.\nExample\nCOS ( 0.0 ) returns 1.0\nTAN ( 45.0 degrees ) returns 1.0\nTAN (0.785 radians) ) returns 0.9992\nErrors\nDivision by zero for TAN if the sine is (nearly) equal to zero.\nSynopsis\nINT ( number1 )\n-> number\nDescription\nReturn the truncated integer value of a number.\nSide Effects\nNone.\nExample\nINT ( 1.6 )    -> 1.0\nINT ( -23.7 ) -> -23.0\nErrors\nInteger overflow.\nSynopsis\nLENgth ( text1 )\n-> number\nDescription\nReturn the length of text1.\nSide Effects\nNone.\nExample\nLENGTH ( \u2019abcdef\u2019 ) -> 6.0\nLENGTH ( \u2019\u2019 ) -> 0.0\nErrors\nNone.\nSynopsis\nLOG ( number1 )\n-> number\nDescription\nReturn the natural logarithm of a number.\nSide Effects\nNone.\nExample\nLOG( 3 ) -> 1 0986123\nErrors\nNegative arguments.\nSynopsis\nMATch ( text1 , text2)\n-> number\nDescription\nReturn the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nSide Effects\nNone.\nExample\nMATCH ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> 3.0\nMATCH ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> 0.0\nMATCH ( \u2019abcdef\u2019 , \u2019\u2019 ) -> 1.0\nErrors\nNone.\nSynopsis\nMAX ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nMIN ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nDescription\nReturn the maximum or minimum value of the arguments.\nSide Effects\nValues being evaluated are assumed to of a common physical quantity.\nIf no unit qualifiers are supplied they are simply numbers.\nIf a physical quantity is defined the result will be in current units of that quantity.\nIf unqualified numbers are mixed with unit values they are assumed to be in the current units of that physical quantity.\nIf quantities are in mixed units they are all compared in comparison to a standard unit.\nIf quantities are of different types of physical quantities a warning is issued and the numeric result compares the values in their database units.\nMin and Max return a value with the same dimension as that of their arguments.\nExample\nMAX ( 1 , 3.4 ) -> 3.4\nMIN ( 7.6 , -12.33 , 2.3 ) -> -12.33\nMIN (7.6ft, 12.33inch, 1000mm ) -> 12.3 in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1000 ) -> 1000in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1kg ) -> 2316.5 (database mm equivalent of 7.6ft)\nErrors\nNone.\nSynopsis\nNEGate ( number1 )\n-> number\nDescription\nMultiply a real by -1.0.\nSide Effects\nNone.\nExample\nNEG ( 1 ) -> -1.0\nErrors\nNone.\nSynopsis\nNINT ( number1 )\n-> number\nDescription\nReturn the nearest integer to a real. NINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nSide Effects\nNone.\nExample\nNINT ( 1.1 ) -> 1.0\nNINT ( -23.7 ) -> -24.0\nNINT ( 1.5 ) -> 2.0\nNINT ( -11.5 ) -> -12.0\nErrors\nInteger overflow.\nSynopsis\nOCCUR(text1, text2)\n-> integer\nDescription\nCounts the number of times string text2 occurs in string text1\nSide Effects\nNone.\nExample\nOCCUR (\u2019ABBACCBBBBBAB\u2019, \u2019BB\u2019) -> 3\nOCCUR(\u2019ZZZZZZZZZZZ\u2019, \u2019A\u2019) -> 0\nErrors\nNone.\nSynopsis\nREAL ( text1 )\n-> number\nDescription\nTry to read a real number at the beginning of text1.\nNote that if text is in the form of an exponent, (-12E-1 in the third example), there must be no spaces in it.\nNote: this function was formerly called NUMBER.\nSide Effects\nNumeric underflow causes the result to be set to zero.\nIf the text string contains units they are ignored and the value only is returned.\nIf the test string contains text that is NOT a valid unit it will generate an error.\nIf the text string is space separated from the number it is completely ignored.\nExample\nREAL ( \u201912.34\u2019) -> 12.34\nREAL ( \u2019 7.23 E 3 meters\u2019 ) -> 7.23\nREAL ( \u2019 -12E-1 meters \u2019 ) -> -1.2\nREAL (' 1200 fred ' ) -> 1200\nREAL (' 1200fred ' ) -> returns an error\nThis will return the value of the number in the string IGNORING any unit qualifier. The unit qualifier must still be a valid unit qualifier. This is done so that output from $! And VAR ! commands can still be accepted by the REAL function.\nNote:\nThe extension of these functions are NOT supported in DARS as they require PML functionality.\nErrors\nUnable to convert the text into a real number.\nSynopsis\nPOWer ( number1 , number2 )\n-> real\nDescription\nReturn the value of number1 raised to the power number2.\nSide Effects\nIf the value being raised to a power is that of a physical quantity the result is also of a physical quantity.(in relevant current units).\nIf the resultant quantity is non physical (for example, by raising to a fractional power, or an extreme power, a warning is given and only the value of quantity is raised to the power.\nIf the power is a physical quantity this also gives a warning.\nExample\nPOWER ( -2 , 3 ) -> -8\nPOWER ( -2inch , 2 ) -> 4in2\nPOWER ( 2inch, 3.5 ) -> returns 11.314 with an error (i.e. 2**3.5)\nErrors\nFloating point overflow.\nZero first argument and non-positive second argument (effectively divide by zero).\nNegative first argument and non-integer second argument.\nSynopsis\nSQrt ( number1 )\n-> number\nDescription\nReturn the square root of a real.\nSide Effects\nUnits are consolidated across SQRT. The resultant value will be in current units of that quantity.\nIf the resultant quantity has no recognized physical dimension a warning is given and the value return will be a number relating to the input value in database units.\nExample\nSQRT ( 4 ) -> 2.0\nSQRT ( 4inch2 ) -> 2.0inch\nsqrt ( 4inch3 ) -> a warning and 256.02 which is sqrt (4*25.4mm)\nErrors\nNegative argument.\nSynopsis\nVVALue( variable_name )\n-> number\nVVALue( variable_name , number )\n-> number\nDescription\nWith one argument, returns value of the scalar variable or value of the array variable element as a number.\nWith two arguments, returns value of the element corresponding to the index number as a number.\nThe value of the variable will be returned, irrespective of its units.\nThis will return the value of the number in the string IGNORING any unit qualifier. The unit qualifier must still be a valid unit qualifier. This is done so that output from $! And VAR ! commands can still be accepted by the VVAL function.\nNote:\nThe extension of these functions are NOT supported in DARS as they require PML functionality.\nSide Effects\nIf the scalar variable, the array variable or the array variable element does not exist, the result is undefined.\nExample\nVVAL ( !array[1] ) -> 1.0\nVVAL ( !array , 2 ) -> 0.0\nErrors\nScalar variable may not be indexed. For example, VTEXT (!var[1]) ) will return an error.\nArray variable must have an index. For example, VTEXT ( !array ) ) will return an error.\nThe string can not be converted to a number.\nNote:\nThe extension of these functions are NOT supported in DARS as they require PML functionality.\nNote:\nThe extension of these functions are NOT supported in DARS as they require PML functionality.\n\n\n\nFunction\nComments\nABS ( number1 )\nACOS ( number1 )\nASIN ( number1 )\nATAN ( number1 )\nATANT ( number1, number2 )\nnumber1\nnumber2\nALOG ( number1 )\nARRAY(pos or dir or ori)\nARRAYSIZE ( variable-name )\nARRAYWIDTH( variable-name )\nCOMPONENT dir OF pos2\npos2\ndir1\nINT ( number1 )\nSIN ( number1 )\nCOS ( number1 )\nTAN ( number1 )\nLENGTH ( text1 )\nLOG ( number1 )\nMATCH ( text1, text2 )\ntext2\ntext1\ntext2\ntext1\nMAX ( number1, number2[ , number3 [. . .]]) )\nMIN ( number1, number2[ , number3 [. . .]]) )\nNEGATE\nNINT ( number1 )\nOCCUR ( text1, text2 )\ntext2\ntext1\nREAL ( text1 )\ntext1\nPOWER ( number1, number2 )\nnumber1\nnumber2\nSQRT ( number1 )\nVVALUE ( variable-name )\nSynopsis\nABS ( number1 )\n-> number\nDescription\nSide Effects\nExample\nABS ( -3.2 ) -> 3.2\nErrors\nSynopsis\nASIN ( number1 )\n-> number\nACOS ( number1 )\n-> number\nATAN ( number1 )\n-> number\nATANT ( number1, number2 )\n-> number\nDescription\nnumber1/number2\nSide Effects\nExample\nACOS ( 0.8660254 ) -> 30degrees\nErrors\nATANT (0.0,0.0)\nSynopsis\nALOG ( number1 )\n-> number\nDescription\nSide Effects\nExample\nALOG( -0.7 ) -> 0.4965853\nErrors\nSynopsis\nARRAY(pos or dir or ori)\n-> number\nDescription\nSide Effects\nExample\nARRAY(e100 ) -> 100 0 0\nErrors\nSynopsis\nARRAYSize ( variable-name )\n-> number\nDescription\nSide Effects\nExample\nErrors\nSynopsis\nARRAYWIDTH ( variable-name )\n-> number\nDescription\nvariable_name\nSide Effects\nExample\nIf an array contains the following values:\n!ARRAY[1] \u2019Bread\u2019\n!ARRAY[2] \u2019is\u2019\n!ARRAY[3] \u2019for\u2019\n!ARRAY[4] \u2019life,\u2019\n!ARRAY[5] \u2019not\u2019\n!ARRAY[6] \u2019just\u2019\n!ARRAY[7] \u2019for\u2019\n!ARRAY[8] \u2019breakfast\u2019\nARRAYWIDTH(!ARRAY -> 9\nErrors\nSynopsis\nCOMPonent dir1 OF pos2\n-> text\nDescription\npos2\ndir1.\nSide Effects\nExample\nCOMP E 45 N of N 0 E 100 U 50 -> 70.710\nErrors\nSynopsis\nDISTConvert ( number )\n-> number\nDescription\nSide Effects\nExample\n-> 1000mm\n-> 10000mm\n-> 5mm\n-> 506625mm\ndistc(1000)\ndistc(10metre)\ndistc( 5pascal)\ndistc (5atm)\n-> 39.4in\n-> 393.7in\n-> 0.2in\n-> 19945.9in\nErrors\nSynopsis\nSINe ( number1 )\n-> number\nCOSine ( number1 )\n-> number\nTANgent ( number1 )\n-> number\nDescription\nSide Effects\nExample\nCOS ( 0.0 ) returns 1.0\nTAN ( 45.0 degrees ) returns 1.0\nTAN (0.785 radians) ) returns 0.9992\nErrors\nSynopsis\nINT ( number1 )\n-> number\nDescription\nSide Effects\nExample\nErrors\nSynopsis\nLENgth ( text1 )\n-> number\nDescription\ntext1\nSide Effects\nExample\nLENGTH ( \u2019abcdef\u2019 ) -> 6.0\nLENGTH ( \u2019\u2019 ) -> 0.0\nErrors\nSynopsis\nLOG ( number1 )\n-> number\nDescription\nSide Effects\nExample\nLOG( 3 ) -> 1 0986123\nErrors\nSynopsis\nMATch ( text1 , text2)\n-> number\nDescription\ntext2\ntext1\ntext2\ntext1\nSide Effects\nExample\nMATCH ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> 3.0\nMATCH ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> 0.0\nMATCH ( \u2019abcdef\u2019 , \u2019\u2019 ) -> 1.0\nErrors\nSynopsis\nMAX ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nMIN ( number1 , number2 [ , number3 [ ... ] ] )\n-> number\nDescription\nSide Effects\nExample\nMAX ( 1 , 3.4 ) -> 3.4\nMIN ( 7.6 , -12.33 , 2.3 ) -> -12.33\nMIN (7.6ft, 12.33inch, 1000mm ) -> 12.3 in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1000 ) -> 1000in (current distance units are inch)\nMAX (7.6ft, 12.33inch, 1kg ) -> 2316.5 (database mm equivalent of 7.6ft)\nSynopsis\nNEGate ( number1 )\n-> number\nDescription\nSide Effects\nExample\nNEG ( 1 ) -> -1.0\nErrors\nSynopsis\nDescription\nNINT(N+0.5)\nN+1\nN\nN\nN\nSide Effects\nExample\nNINT ( 1.1 ) -> 1.0\nNINT ( -23.7 ) -> -24.0\nNINT ( 1.5 ) -> 2.0\nNINT ( -11.5 ) -> -12.0\nErrors\nSynopsis\nOCCUR(text1, text2)\n-> integer\nDescription\ntext2\ntext1\nSide Effects\nExample\nOCCUR (\u2019ABBACCBBBBBAB\u2019, \u2019BB\u2019) -> 3\nOCCUR(\u2019ZZZZZZZZZZZ\u2019, \u2019A\u2019) -> 0\nErrors\nSynopsis\nREAL ( text1 )\n-> number\nDescription\ntext1\nSide Effects\nExample\nREAL ( \u201912.34\u2019) -> 12.34\nREAL ( \u2019 7.23 E 3 meters\u2019 ) -> 7.23\nREAL ( \u2019 -12E-1 meters \u2019 ) -> -1.2\nREAL (' 1200 fred ' ) -> 1200\nREAL (' 1200fred ' ) -> returns a\nNote\n:\nErrors\nSynopsis\nPOWer ( number1 , number2 )\n-> real\nDescription\nnumber1\nnumber2\nSide Effects\nExample\nPOWER ( -2 , 3 ) -> -8\nPOWER ( -2inch , 2 ) -> 4in2\nPOWER ( 2inch, 3.5 ) -> returns 11.314 with an error (i.e. 2**3.5)\nErrors\nSynopsis\nSQrt ( number1 )\n-> number\nDescription\nSide Effects\nExample\nSQRT ( 4 ) -> 2.0\nSQRT ( 4inch2 ) -> 2.0inch\nsqrt ( 4inch3 ) -> a warning and 256.02 which is sqrt (4*25.4mm)\nErrors\nSynopsis\nVVALue( variable_name )\n-> number\nVVALue( variable_name , number )\n-> number\nDescription\nNote\n:\nSide Effects\nExample\nVVAL ( !array[1] ) -> 1.0\nVVAL ( !array , 2 ) -> 0.0\nErrors\nVTEXT (!var[1]) )\nVTEXT ( !array ) )"}
{"Headers": "Real Arrays", "Content": "Real array expressions can contain attributes of type real array, for example: DESP.\n\n\n"}
{"Headers": "Units and Physical Quantity Attributes in Expressions", "Content": "In real expressions the dimension of the result is tracked using:\nIf at any time a value with no dimension occurs where a value with a specific dimension is needed then the value is taken to be one of that dimension in the current working units of that dimension (for example, mm for distances, degrees for angles). This will occur in addition and subtraction operations, and arguments for typed functions (for example,. trigonometric).\nWhenever a clash of physical quantity occurs then either a warning or an error will be raised (for example, SIN(25inch).\nIn all expressions and functions physical quantities are tracked and the result, wherever possible is returned in the current units of the resultant physical quantity (dimension). If the system cannot do this (for example, the expression is not dimensionally sound, or the dimension exceeds the scope which the system can track) then a warning is issued and a simple numeric result is returned.\nWhen a user enters a literal value then the type of physical quantity is not known and the decision as to what it is determined to make it consistent with the context with respect to other values in the expression. When it is finally determined the value is then taken to be in the current units of that quantity. The method of this determination is normally straightforward and is described in specific sections above.\nThe units for PML variables are also unknown. Where units are known and handled similarly in expression.\nTo cope with \u2019unknown\u2019 units each value remembers its original units internally. An attempt is then made to allow for \u2019unknown\u2019 units across operators and within functions. In general the physical quantity of the result of a function, or expressions, is tracked by the system and the resulting value is one of the resultant physical quantities. For example multiplying 3 distances together gives a result of a volume which will have units such as gallons, litres or cubic ft.\nOn comparison, addition or subtraction of two values then if one has units and the other has none (i.e. not a physical quantity) it is assumed to be the same sort of quantity as the other, and in the current units of that quantity.\nFor example:\nIf we are working in distance units of inches, it is known that XLEN is a distance value. Internally the value is held in mm, but the units are held as INCH. The units for \u201910\u2019 are held as unknown. On doing the comparison, the \u201910\u2019 is assumed to be inches and thus multiplied by 25.4 to make sure that the comparison works as expected.\nSpecial action is also taken to preserve the correct units across multiplication, division, POWER and SQRT, as described in the sections above.\n(XLEN GT 10).\nThe dimension of any attribute values used (for example, XLEN, BANG, DENS, GVOL)\nThe unit qualifiers of any values supplied\nThe known result of any function (for example, ASIN returns an angle, POW, SQRT return a computed dimension, MIN/MAX that of their arguments etc.)\nThe computed result of multiplication and division operation. (for example, GWEI/GVOL is a density)\nThe need for consistency for addition and subtraction operations\nThe dimension of any attribute values used (for example, XLEN, BANG, DENS, GVOL)\nThe dimension of any attribute values used (for example, XLEN, BANG, DENS, GVOL)\nThe unit qualifiers of any values supplied\nThe unit qualifiers of any values supplied\nThe known result of any function (for example, ASIN returns an angle, POW, SQRT return a computed dimension, MIN/MAX that of their arguments etc.)\nThe known result of any function (for example, ASIN returns an angle, POW, SQRT return a computed dimension, MIN/MAX that of their arguments etc.)\nThe computed result of multiplication and division operation. (for example, GWEI/GVOL is a density)\nThe computed result of multiplication and division operation. (for example, GWEI/GVOL is a density)\nThe need for consistency for addition and subtraction operations\nThe need for consistency for addition and subtraction operations\n\n\n"}
{"Headers": "Using IDs in Expressions", "Content": "IDs can be used in expressions. IDs can be any of the following:\nSPEC OF SPREF OF FLAN 1 OF NEXT BRAN.\nHEAD TUBE OF /BRAN1.\nElement name, for example: /VESS1.\nRefno, for example: =23/456.\nElement type further up the hierarchy, for example: SITE.\nNumber within member list, for example: 3.\nType and number within member list, for example: BOX 3.\nNEXT, PREV for next, previous within current list. Optionally with a count and/or element type, for example: NEXT 2 BOX, LAST CYL.\nNEXT, PREV MEMBER for next, previous within member list. Optionally with a count and/or element type.\nIf the element type given is only valid as a member then MEMBER is assumed. For example, NEXT BOX at an EQUIPMENT will assume MEMBER.\nFIRST, LAST for first and last in current list. Optionally with a count and/or element type.\nFIRST, LAST MEMBER for first and last in member list. If the element type given is only valid as a member then MEMBER is assumed.\nEND to navigate up from current list.\nEND is similar to owner but not quite the same. For example, if the current element is a GROUP MEMBER, and it has been reached from the GROUP then END will return to the group but OWNE will go to the true owner.\nAttribute of type ref, for example: CREF\nSAME to mean last current element\nNULREF to mean =0/0\nCE for the current element\n\u2019OF\u2019 may be used to nest the options indefinitely. For example:\nSPEC OF SPREF OF FLAN 1 OF NEXT BRAN.\nThis denotes the SPEC element owing the SELE element pointed to by the SPREF attribute on the first FLANGE of the next BRANCH. ILEAVE TUBE, IARRIV TUBE, HEAD TUBE, TAIL TUBE can be added to denote tube. For example:\nHEAD TUBE OF /BRAN1.\nAn error will occur if there is no implied tube for the element concerned.\nID arrays can also be used in expressions. For example, CRFA.\nElement name, for example: /VESS1.\nElement name, for example: /VESS1.\nRefno, for example: =23/456.\nRefno, for example: =23/456.\nElement type further up the hierarchy, for example: SITE.\nElement type further up the hierarchy, for example: SITE.\nNumber within member list, for example: 3.\nNumber within member list, for example: 3.\nType and number within member list, for example: BOX 3.\nType and number within member list, for example: BOX 3.\nNEXT, PREV for next, previous within current list. Optionally with a count and/or element type, for example: NEXT 2 BOX, LAST CYL.\nNEXT, PREV for next, previous within current list. Optionally with a count and/or element type, for example: NEXT 2 BOX, LAST CYL.\nNEXT, PREV MEMBER for next, previous within member list. Optionally with a count and/or element type.\nNEXT, PREV MEMBER for next, previous within member list. Optionally with a count and/or element type.\nIf the element type given is only valid as a member then MEMBER is assumed. For example, NEXT BOX at an EQUIPMENT will assume MEMBER.\nIf the element type given is only valid as a member then MEMBER is assumed. For example, NEXT BOX at an EQUIPMENT will assume MEMBER.\nFIRST, LAST for first and last in current list. Optionally with a count and/or element type.\nFIRST, LAST for first and last in current list. Optionally with a count and/or element type.\nFIRST, LAST MEMBER for first and last in member list. If the element type given is only valid as a member then MEMBER is assumed.\nFIRST, LAST MEMBER for first and last in member list. If the element type given is only valid as a member then MEMBER is assumed.\nEND to navigate up from current list.\nEND to navigate up from current list.\nEND is similar to owner but not quite the same. For example, if the current element is a GROUP MEMBER, and it has been reached from the GROUP then END will return to the group but OWNE will go to the true owner.\nEND is similar to owner but not quite the same. For example, if the current element is a GROUP MEMBER, and it has been reached from the GROUP then END will return to the group but OWNE will go to the true owner.\nAttribute of type ref, for example: CREF\nAttribute of type ref, for example: CREF\nSAME to mean last current element\nSAME to mean last current element\nNULREF to mean =0/0\nNULREF to mean =0/0\nCE for the current element\nCE for the current element\n\u2019OF\u2019 may be used to nest the options indefinitely. For example:\nSPEC OF SPREF OF FLAN 1 OF NEXT BRAN.\n\u2019OF\u2019 may be used to nest the options indefinitely. For example:\nThis denotes the SPEC element owing the SELE element pointed to by the SPREF attribute on the first FLANGE of the next BRANCH. ILEAVE TUBE, IARRIV TUBE, HEAD TUBE, TAIL TUBE can be added to denote tube. For example:\nHEAD TUBE OF /BRAN1.\nThis denotes the SPEC element owing the SELE element pointed to by the SPREF attribute on the first FLANGE of the next BRANCH. ILEAVE TUBE, IARRIV TUBE, HEAD TUBE, TAIL TUBE can be added to denote tube. For example:\nAn error will occur if there is no implied tube for the element concerned.\nID arrays can also be used in expressions. For example, CRFA.\nAn error will occur if there is no implied tube for the element concerned.\nNote:\nSome of the ID syntax clashes with other types. To allow for this, an id expression may always be preceded with the keyword ID. For example, ID 3 will mean the third member of the current list rather than a number of value 3.\n\n\n\nNote\n:"}
{"Headers": "Positions, Directions and Orientations in Expressions", "Content": "Information is provided on how to use and compare positions and on how to define units, an offset from a fixed point, the direction and orientation in expressions.\n\n\n"}
{"Headers": "Use Positions in Expressions", "Content": "The basic ways of defining a position are:\nThe Cartesian position may optionally be followed by WRT to specify the axis system. Refer to WRT.\nPOS OF /VESS1 WRT /* or P1 POS OF /CYL2\nN 45 W 20000 U 1000\nN 1000 FROM /ATEST.\nN 1000 FROM P1 OF /BOX2.\nN 1000 FROM POSS OF /SCTN1\nN (DESP[1] + 10) E\nPosition attribute plus optional WRT. For example:\nPOS OF /VESS1 WRT /* or P1 POS OF /CYL2\nCartesian position. For example:\nN 45 W 20000 U 1000\nCartesian position from an element. For example:\nN 1000 FROM /ATEST.\nCartesian position from a ppoint. For example:\nN 1000 FROM P1 OF /BOX2.\nCartesian position from an attribute. For example:\nN 1000 FROM POSS OF /SCTN1\nAny numeric value within a position may itself be an expression. For example: the following is a valid position expression\nN (DESP[1] + 10) E\nPosition attribute plus optional WRT. For example:\nPOS OF /VESS1 WRT /* or P1 POS OF /CYL2\nPosition attribute plus optional WRT. For example:\nCartesian position. For example:\nN 45 W 20000 U 1000\nCartesian position. For example:\nCartesian position from an element. For example:\nN 1000 FROM /ATEST.\nCartesian position from an element. For example:\nCartesian position from a ppoint. For example:\nN 1000 FROM P1 OF /BOX2.\nCartesian position from a ppoint. For example:\nCartesian position from an attribute. For example:\nN 1000 FROM POSS OF /SCTN1\nCartesian position from an attribute. For example:\nAny numeric value within a position may itself be an expression. For example: the following is a valid position expression\nN (DESP[1] + 10) E\nAny numeric value within a position may itself be an expression. For example: the following is a valid position expression\n\n\n\nWRT\nWRT"}
{"Headers": "WRT", "Content": "The WRT keyword is used to toggle between absolute and relative units.\nWhen we specify an element (or attribute of an element) we are specifying an absolute point in world space. The point can be given in world space or some other axis. Normally the answer is required relative to the owner axis system and this is taken as the default. For example:\nQ POS\n$ will return the position of the current element\n$ relatively to its owner.\nQ POS OF /EQUIP1\n$ will return the position of EQUIP1 relative to its\n$ owner.\nQ POS\n$ will return the position of the current element\n$ relatively to its owner.\nQ POS OF /EQUIP1\n$ will return the position of EQUIP1 relative to its\n$ owner.\nIf we require the result in some other axis system then the WRT keyword is used. For example:\nQ POS WRT /*\n$.for the position in world coordinates.\nQ POS WRT /*\n$.for the position in world coordinates.\nWhen we specify a Cartesian coordinate we are dealing with a relative position.\nFor example, \u2019N 10\u2019 is meaningless until we specify the axis system, or default to an axis system.\nAgain we use WRT to do this, although it is important to note that in this case we are going from a relative position to an absolute position (in the previous example WRT was used to go from an absolute position to a relative one).\nFor example:\nN 100 WRT /BOX1\n$ specifies an absolute position in world space\n$ which is N100 of /BOX1.\nN 100 WRT /BOX1\n$ specifies an absolute position in world space\n$ which is N100 of /BOX1.\nThe default is that Cartesian coordinates are in the owning element\u2019s axis system. This absolute position can be expressed in different coordinate systems: the default is again the owner\u2019s axis system.\nA SITE at (0,0,0)\nWith default (World) orientation\nA ZONE at (100,0,0)\nWith default (World) orientation\nAn EQUIPMENT at (100,0,0)\nWith orientation \u2019N IS E\nA BOX at (-100,0,0)\nWith default (World) orientation\nThe result of Q (N 100 WRT /BOX1), will depend on the current element.\nWorld\n(300,100,0), in World coordinates.\nSite\n(300,100,0) in World coordinates because the World is the owner of the current element.\nZone\n(300,100,0) in World coordinates, because the Site is the owner of the current element, and the Site coordinates are the same as the World coordinates.\nEquipment\n(200,100,0), which is the position relative to its owner, the Zone.\nBox\n(100,100,0) which is the position relative to its owner, the Equipment.\nWRT can be further qualified by FROM.\nQ POS\n$ will return the position of the current element\n$ relatively to its owner.\nQ POS OF /EQUIP1\n$ will return the position of EQUIP1 relative to its\n$ owner.\nQ POS WRT /*\n$.for the position in world coordinates.\nN 100 WRT /BOX1\n$ specifies an absolute position in world space\n$ which is N100 of /BOX1.\nItem\nComments\nA SITE at (0,0,0)\nWith default (World) orientation\nA ZONE at (100,0,0)\nWith default (World) orientation\nAn EQUIPMENT at (100,0,0)\nWith orientation \u2019N IS E\nA BOX at (-100,0,0)\nWith default (World) orientation\nLocation\nResult\nWorld\n(300,100,0), in World coordinates.\nSite\n(300,100,0) in World coordinates because the World is the owner of the current element.\nZone\n(300,100,0) in World coordinates, because the Site is the owner of the current element, and the Site coordinates are the same as the World coordinates.\nEquipment\n(200,100,0), which is the position relative to its owner, the Zone.\nBox\n(100,100,0) which is the position relative to its owner, the Equipment.\nNote:\nThe CONSTRUCT syntax uses the world as the default axis.\n\n\n\nQ POS\nQ POS OF /EQUIP1\nQ POS WRT /*\nN 100 WRT /BOX1\nNote\n:\nQ (N 100 WRT /BOX1)"}
{"Headers": "FROM", "Content": "In some cases we require an offset from a fixed point, other than the position of an item. For example, a point or attribute.\nThe FROM syntax is used for this. We may still use WRT in combination with FROM, but in this case the WRT is only used to determine the axis direction and not the offset, since the offset is specified by the FROM part.\nConsider the following:\nA SITE at (0,0,0)\nWith default (World) orientation\nA ZONE at (100,0,0)\nWith default (World) orientation\nAn EQUIPMENT at (100,0,0)\nWith orientation \u2019N IS E\nA BOX at (-100,0,0)\nWith default (World) orientation\nThe result of Q (N 100 WRT /* FROM /BOX1), shown as \u00c4 in , will depend on the current element.\nWorld, Site, and Zone\n(200,200,0) since the offset of N100 is applied in world axis rather than /BOX1 axis.\nEquipment\n(100,200,0). Note: the default axis for the result is the Zone.\nBox\n(200,0,0), because the default axis for the result is the Equipment.\nThe result of \u2019Q (N 100 WRT /BOX1 FROM /* ) is different:\nSite and Zone\n(100,0,0)\nEquipment\n(0,0,0)\nBox\n(0, -100, 0), because the axis for the result is the Equipment.\nThe result of \u2019Q (N 100 FROM /* )\u2019 is different yet again.\nFor this we cannot mark an absolute point on the diagram since the default WRT will vary with the current element. In fact for the SITE, ZONE, EQUI the point \u00c4 is marked in , and for the BOX the point coincides with the ZONE.\nSite and Zone\n(0,100,0)\nEquipment\n(-100,100,0), because the default result axis is the Zone.\nBox\n(0, -100, 0), because the axis for the result is the Equipment.\n\nItem\nComments\nA SITE at (0,0,0)\nWith default (World) orientation\nA ZONE at (100,0,0)\nWith default (World) orientation\nAn EQUIPMENT at (100,0,0)\nWith orientation \u2019N IS E\nA BOX at (-100,0,0)\nWith default (World) orientation\nLocation\nResult\nWorld, Site, and Zone\n(200,200,0) since the offset of N100 is applied in world axis rather than /BOX1 axis.\nEquipment\n(100,200,0). Note: the default axis for the result is the Zone.\nBox\n(200,0,0), because the default axis for the result is the Equipment.\nLocation\nResult\nSite and Zone\n(100,0,0)\nEquipment\n(0,0,0)\nBox\n(0, -100, 0), because the axis for the result is the Equipment.\nLocation\nResult\nSite and Zone\n(0,100,0)\nEquipment\n(-100,100,0), because the default result axis is the Zone.\nBox\n(0, -100, 0), because the axis for the result is the Equipment.\n\n\n\nQ (N 100 WRT /* FROM /BOX1),\n\u00c4\n\u2019Q (N 100 WRT /BOX1 FROM /* )\n\u2019Q (N 100 FROM /* )\u2019\n\u00c4"}
{"Headers": "Compare Positions", "Content": "Two positions can be compared with EQ, NE, GT, LT, GE or LE. The pairs of coordinates are only compared in the coordinate axes for which the two positions are defined. A position attribute always has all three coordinates defined.\nFor positions entered by you, only those coordinates which are given by you are defined. For example:\n\u2019N10U3\u2019\n$ only the Y and Z coordinates are defined,\n$ while the X coordinate remains undefined\n\u2019N10U3\u2019\n$ only the Y and Z coordinates are defined,\n$ while the X coordinate remains undefined\nFor the EQ operator, all the pairs of defined coordinates should be equal. For NE, only one pair of defined coordinates need be different. For GT (LT,GE,LE), all the defined coordinates of the first position should be greater than (less than, greater than or equal to, less than or equal to) the defined coordinates of the second position. This means that GE is not the opposite of LT and LE is not the opposite of GT.\nIf no coordinate of the two positions are defined for a common axis (e.g. \u2019N10\u2019 and \u2019W4D7\u2019), the result of the comparison is undefined.\n\u2019POS EQ W1S2D3\u2019\n$ This evaluates to true only if POS of the current $ element is (-1,-2,-3).\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\n$ Only the second coordinate of POS is compared;\n$ if it is greater than 10, then the result is true.\n\u2019E10N10 GT E0N0\u2019\n$ Is true because the inequality is verified for the X\n$ and Y axis (both coordinates are undefined for\n$ the Z axis, so it is ignored).\n\u2019E10N0 GT E0N0\u2019\n$ Is false because the Y components are different $ axes.\n\u2019E10N0 GT E0U100\u2019\n$ Is true. Although no comparison can be\n$ performed n either the Y or the Z axis, because\n$ the components are not present in both position\n$ constants, the comparison is true in the X\n$ component.\n\u2019N10 EQ W4D7\u2019\n$ Is undefined (no comparison is possible).\n\u2019POS EQ W1S2D3\u2019\n$ This evaluates to true only if POS of the current $ element is (-1,-2,-3).\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\n\n$ Only the second coordinate of POS is compared;\n$ if it is greater than 10, then the result is true.\n\u2019E10N10 GT E0N0\u2019\n$ Is true because the inequality is verified for the X\n$ and Y axis (both coordinates are undefined for\n$ the Z axis, so it is ignored).\n\u2019E10N0 GT E0N0\u2019\n$ Is false because the Y components are different $ axes.\n\u2019E10N0 GT E0U100\u2019\n$ Is true. Although no comparison can be\n$ performed n either the Y or the Z axis, because\n$ the components are not present in both position\n$ constants, the comparison is true in the X\n$ component.\n\u2019N10 EQ W4D7\u2019\n$ Is undefined (no comparison is possible).\nRefer to Precision of Comparisons, for tolerances in comparing numbers.\n\u2019N10U3\u2019\n$ only the Y and Z coordinates are defined,\n$ while the X coordinate remains undefined\n\u2019POS EQ W1S2D3\u2019\n$ This evaluates to true only if POS of the current $ element is (-1,-2,-3).\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\n$ Only the second coordinate of POS is compared;\n$ if it is greater than 10, then the result is true.\n\u2019E10N10 GT E0N0\u2019\n$ Is true because the inequality is verified for the X\n$ and Y axis (both coordinates are undefined for\n$ the Z axis, so it is ignored).\n\u2019E10N0 GT E0N0\u2019\n$ Is false because the Y components are different $ axes.\n\u2019E10N0 GT E0U100\u2019\n$ Is true. Although no comparison can be\n$ performed n either the Y or the Z axis, because\n$ the components are not present in both position\n$ constants, the comparison is true in the X\n$ component.\n\u2019N10 EQ W4D7\u2019\n$ Is undefined (no comparison is possible).\n\n\n\nPrecision of Comparisons\n\u2019N10U3\u2019\n\u2019POS EQ W1S2D3\u2019\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\n\u2019E10N10 GT E0N0\u2019\n\u2019E10N0 GT E0N0\u2019\n\u2019E10N0 GT E0U100\u2019\n\u2019N10 EQ W4D7\u2019\nPrecision of Comparisons\n,"}
{"Headers": "POLAR", "Content": "The POLAR keyword allows positions to be defined in terms of a distance in a particular direction from a point.\nIf FROM is not specified the default is the origin of the owner.\nPOLAR N 45 E DIST 20M FROM U 10 M\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V\nPOLAR N 45 E DIST 20M FROM U 10 M\n\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V\n\n\n\nPOLAR N 45 E DIST 20M FROM U 10 M\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V\nPOLAR dir DISTance expr -+- FROM -+- pos -----.\n                         |        |           |\n                         |        \u2018- point ---|\n                         |                    |\n                         \u2018--------------------+--->\n\n\n\nPOLAR dir DISTance expr -+- FROM -+- pos -----.\n                         |        |           |\n                         |        \u2018- point ---|\n                         |                    |\n                         \u2018--------------------+--->\nPOLAR N 45 E DIST 20M FROM U 10 M\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V"}
{"Headers": "Direction", "Content": "The basic ways of defining a direction are:\nHDIR OF /PIPE1 WRT /*\nN 45 W\n(U WRT CE )\nQ ( Z WRT /SCTN )\nFROM N 50 WRT CE TO N 100\n>- CLOSEST type -+- WITH exp -.\n                 |            |\n                 \u2018------------+- DIRECTION dir -+- EXTENT val -.\n                                                |              |\n                                                \u2018--------------+--> cont\n                                                    \n         continued >-+- AFTER val -.\n                     |             |\n                     \u2018-------------+- FROM ? -.\n                                   |          |\n                                   \u2018----------+-->\nCLOSEST DIR E\nCLOSEST BOX WITH ( PURP EQ \u2019FLOO\u2019 ) DIR D WRT /* EXTENT 20M\nCLOSEST VALVE DIR N 45 U FROM E100 N200 U300\nCLOSEST BRAN HANG AFTER 2M\nDirection attribute plus optional WRT. For example,\nHDIR OF /PIPE1 WRT /*\nCartesian direction. For example,\nN 45 W\nCartesian direction WRT to an element.\nAll Cartesian directions are returned in the axis of the owner of the current element. For example:\n(U WRT CE )\nwill return the Z axis of the current element relative to its owner.\nQ ( Z WRT /SCTN )\nwill return the Z axis direction of /SCTN relative to the owner of the current element. For example, if the result is required in world coordinates the current element must be the World or a Site.\nFROM pos2 TO pos2. For example\nFROM N 50 WRT CE TO N 100\nKeyword AXES followed by a p-point or pline.\nThe CLOSEST keyword, which will find the closest element in a particular direction.\nDirection attribute plus optional WRT. For example,\nHDIR OF /PIPE1 WRT /*\nDirection attribute plus optional WRT. For example,\nCartesian direction. For example,\nN 45 W\nCartesian direction. For example,\nCartesian direction WRT to an element.\nCartesian direction WRT to an element.\nAll Cartesian directions are returned in the axis of the owner of the current element. For example:\n(U WRT CE )\nAll Cartesian directions are returned in the axis of the owner of the current element. For example:\nwill return the Z axis of the current element relative to its owner.\nQ ( Z WRT /SCTN )\nwill return the Z axis of the current element relative to its owner.\nwill return the Z axis direction of /SCTN relative to the owner of the current element. For example, if the result is required in world coordinates the current element must be the World or a Site.\nwill return the Z axis direction of /SCTN relative to the owner of the current element. For example, if the result is required in world coordinates the current element must be the World or a Site.\nFROM pos2 TO pos2. For example\nFROM N 50 WRT CE TO N 100\nFROM pos2 TO pos2. For example\nKeyword AXES followed by a p-point or pline.\nKeyword AXES followed by a p-point or pline.\nThe CLOSEST keyword, which will find the closest element in a particular direction.\nThe CLOSEST keyword, which will find the closest element in a particular direction.\nIn the above graph the keywords are:\nEXTENT, which is how far to search in the direction specified, default 10M\nAFTER, or the distance along vector after which to start search, default 0M\nFROM, which specifies an alternative start point other than current element. This is of particular use for a branch where you might want to specify the HPOS or TPOS.\nIn the above graph the keywords are:\nIn the above graph the keywords are:\nEXTENT, which is how far to search in the direction specified, default 10M\nEXTENT, which is how far to search in the direction specified, default 10M\nAFTER, or the distance along vector after which to start search, default 0M\nAFTER, or the distance along vector after which to start search, default 0M\nFROM, which specifies an alternative start point other than current element. This is of particular use for a branch where you might want to specify the HPOS or TPOS.\nFROM, which specifies an alternative start point other than current element. This is of particular use for a branch where you might want to specify the HPOS or TPOS.\n\n\n"}
{"Headers": "Orientations", "Content": "The basic ways of defining an orientation are:\nORI OF /BOX1 WRT /*\ndir IS dir AND dir IS dir\n(E IS U WRT /SCTN1 AND N IS E WRT /SCTN1)\n            ----<---------.\n             /              |\n >-- AXES --*--- PArrive ---|\n            |               |\n            |--- PLeave ----|\n            |               |\n            |--- PTail -----|\n            |               |\n            |--- HHead -----|\n            |               |\n            |--- HTail -----|\n            |               |\n            \u2018--- PPOINT n --+-- OF - <gid> ---->\n( AXES PLEAVE IS AXES PLEAVE OF PREV AND AXES P3 IS UP )\nOrientation attribute plus optional WRT. For example:\nORI OF /BOX1 WRT /*\nCartesian orientation. For example:\ndir IS dir AND dir IS dir\nFor example to set an orientation of an element to that of a section, rotated by 90 degrees use:\n(E IS U WRT /SCTN1 AND N IS E WRT /SCTN1)\nThe AXES keyword, which will allow you to use P-points to specify orientations.\nOrientation attribute plus optional WRT. For example:\nORI OF /BOX1 WRT /*\nOrientation attribute plus optional WRT. For example:\nCartesian orientation. For example:\ndir IS dir AND dir IS dir\nCartesian orientation. For example:\nFor example to set an orientation of an element to that of a section, rotated by 90 degrees use:\n(E IS U WRT /SCTN1 AND N IS E WRT /SCTN1)\nFor example to set an orientation of an element to that of a section, rotated by 90 degrees use:\nThe AXES keyword, which will allow you to use P-points to specify orientations.\nThe AXES keyword, which will allow you to use P-points to specify orientations.\nThis will orient a branch component, such as a valve, so that it is aligned with the previous component and its P3 is up.\nRefer to also Compare Positions.\nThis will orient a branch component, such as a valve, so that it is aligned with the previous component and its P3 is up.\nRefer to also Compare Positions.\nThis will orient a branch component, such as a valve, so that it is aligned with the previous component and its P3 is up.\n\n\n\nCompare Positions\n            ----<---------.\n             /              |\n >-- AXES --*--- PArrive ---|\n            |               |\n            |--- PLeave ----|\n            |               |\n            |--- PTail -----|\n            |               |\n            |--- HHead -----|\n            |               |\n            |--- HTail -----|\n            |               |\n            \u2018--- PPOINT n --+-- OF - <gid> ---->\nCompare Positions"}
{"Headers": "Text Expressions", "Content": "Text expressions can contain the following:\nA text string, which must be enclosed in quotes. For example: \u2019FRED\u2019.\nAn AVEVA E3D Design attribute of type text or word. For example: FUNC\nA single element of a word array attribute. For example: ELEL[2].\nText operators\nText functions\nA text string, which must be enclosed in quotes. For example: \u2019FRED\u2019.\nA text string, which must be enclosed in quotes. For example: \u2019FRED\u2019.\nAn AVEVA E3D Design attribute of type text or word. For example: FUNC\nAn AVEVA E3D Design attribute of type text or word. For example: FUNC\nA single element of a word array attribute. For example: ELEL[2].\nA single element of a word array attribute. For example: ELEL[2].\nText operators\nText operators\nText functions\nText functions\n\n\n"}
{"Headers": "Text Operator", "Content": "The text operator available is +, used for concatenation.\ntext1 + text2 -> text\n-> text\nReturn the concatenation of two text strings.\nNone.\n\u2019no\u2019 + \u2019space\u2019 -> \u2019nospace\u2019\nText result too long.\n\nSynopsis\ntext1 + text2 -> text\n-> text\nDescription\nReturn the concatenation of two text strings.\nSide Effects\nNone.\nExample\n\u2019no\u2019 + \u2019space\u2019 -> \u2019nospace\u2019\nErrors\nText result too long.\n\n\n\nSynopsis\ntext1 + text2 -> text\n-> text\nDescription\nSide Effects\nExample\nErrors"}
{"Headers": "Text Functions", "Content": "The text functions available are:\nAFTER\nBEFORE\nDIMENSIONOF, DIMOF\nDIMWOOD\nDISTANCE\nLOWCASE, UPCASE\nPART\nREPLACE\nSTRING\nSUBS, DSUBS\nTRIM\nUNITSOF\nVTEXT\nAFTER\n\nBEFORE\n\nDIMENSIONOF, DIMOF\n\nDIMWOOD\n\nDISTANCE\n\nLOWCASE, UPCASE\n\nPART\n\nREPLACE\n\nSTRING\n\nSUBS, DSUBS\n\nTRIM\n\nUNITSOF\n\nVTEXT\n\nAFTER ( text1 , text2 )\n-> text\nReturn the substring of text1 which is after the leftmost occurrence of text2 in text1.\nIf text2 does not occur in text1, the null string is returned.\nNone.\nAFTER ( \u2019abcdef\u2019 , \u2019cd\u2019 ) ->\u2019ef\u2019\nAFTER ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> \u2019\u2019\nAFTER ( \u2019abcdef\u2019 , \u2019\u2019 ) -> \u2019abcdef\u2019\nNone.\nBEFORE ( text1 , text2 )\n-> text\nReturn the substring of text1 which is before the leftmost occurrence of text2 in text1. If text2 does not occur in text1, text1 is returned.\nNone.\nBEFORE ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> \u2019ab\u2019\nBEFORE ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> \u2019\u2019\nBEFORE ( \u2019abcdef\u2019 , \u2019\u2019 ) -> \u2018\u2019\nNone.\nDIMensionof or DIMOF\n(any real variable or expression)\n-> text\nEvaluates the real expression and returns its physical dimension as a text string. This is name of the dimension in the table in Standard Units.\nThe argument can be a single real value (with or without unit qualifier) or any real expression.\nNone.\nDim (1)\ndim(1kg)\ndimof(1kg/m3)\ndimensionof (1 curie)\ndim (1joule / 1 day / sqrt (1 m4))\ndim (1 newton / sqrt ( 1 m4)\n-> NONE\n-> Mass\n-> Density\n-> Radioactivity\n-> GENERIC\n-> Pressure\n\n\nDIMWORD\n(any real variable or expression)\n-> text\nEvaluates the real expression and returns its physical dimension as a word string. This is HASH name of the dimension in the table in Standard Units.\nThe argument can be a single real value (with or without unit qualifier) or any real expression.\nNone.\nDimword (1)\ndimword (1curie)\nDimword (1kg/5litre)\ndimword (1curie)\ndimword (1kg/5litre)\ndimword (1joule / 1 day / sqrt (1 m4))\ndimword (1 newton / sqrt (1 m4)\ndim(1kg)\n-> NONE\n-> RADY\n-> DENS\n-> RADY\n-> DENS\n-> GENERIC\n-> PRESS\n-> Mass\n\n\nDISTance ( number1 )\n-> text\nDISTance( number1, logical1, logical2, logical3, number2, logical4)\n-> text\nFor the one-argument form, if the current distance units are FINCH, text is the conversion of the decimal inches value number1 into the format \u2019aa\u2019bb.cc/dd\u2019. Otherwise, text is the STRING conversion of number1.\nThe six-argument form is more complex. The format is:\nDIST/ANCE (distance, feet, usformat, fraction, denom_or_dp, zeros)\nwhere:\nAVEVA E3D Design\nFor both US and AVEVA E3D Design formats the following rules are observed:\nThe inches and fraction of inches are followed by a double quote(\").\nNone.\nIf the current distance units are FINCH:\nDISTANCE ( 17.5 ) -> \u20191\u20195.1/2\u2019\nSome examples, where the current distance units are feet and inches:\nDIST(34.5,TRUE,TRUE,TRUE,100,TRUE) -> 2\u2019-10.1/2.\nDIST(34.5,FALSE,TRUE,FALSE,1,TRUE) -> 34.5\"\nDIST(34.5,FALSE,TRUE,TRUE,4,FALSE) -> 34 1/2\"\nDIST(128.5,TRUE,FALSE,TRUE,2,TRUE) -> 10\u201908.1/2\"\n\nThe following table shows sets of options that could have been chosen and the format of the output produced for different numbers. Blanks output by the system are represented by underscores(_).\n\nThe value is too big to be converted.\nUPCase ( text1 )\n-> text\nLOWCase ( text1 )\n-> text\nReturn an upper or lower case version of text1.\nNone.\nUPCASE ( \u2019False\u2019) -> \u2019FALSE\u2019\nLOWCASE ( \u2019False\u2019) -> \u2019false\u2019\nNone.\nPART(text1, number1)\n-> text\nPART(text1, number1 , text2)\n-> text\nWith two arguments, returns the number1 component of text1 assuming that text1 is split on any whitespace characters. If number1 is negative, counting of components starts from the right.\nWith three arguments, as above, but use text2 as the separator on which splitting takes place.\nIf you give a part number higher than the number of components in the string, the function returns an empty string.\nNone.\nPART (\u2019x-y-z\u2019, 1, \u2019-\u2019 -> \u2019x\u2019\nPART (\u2019a b c d e\u2019, 4-> \u2019d\u2019\nPART (\u2019/PIPE45/B9\u2019, -1, \u2019/\u2019) -> \u2019B9\u2019\nPART(\u2019aa bb cc\u2019, 2) -> \u2019bb\u2019\nPART(\u2019aa-bb-cc\u2019,3,\u2019-\u2019) -> \u2019cc\u2019\nNone.\nREPLace (text1,text2,text3)\n-> text\nREPLace(text1,text2,text3,int1)\n-> text\nREPLace(text1,text2,text2,int1,int2)\n-> text\nReplace search string text2 in input string text1 with replacement string text3.\nIf int1 is given this specifies the first occurrence of text2 at which to start replacement.\nIf int2 is given this specifies the number of replacements to make. int1 and/or int2 may be negative to indicate that the direction is backwards.\nNone.\nThree arguments:\nREPLACE (\u2019cat dog cat cat dog \u2019, \u2019cat\u2019, \u2019dog\u2019 ) -> \u2019dog dog dog dog dog\u2019\nAll occurrences of \u2019cat\u2019 are replaced with \u2019dog\u2019.\n\nFour arguments: start occurrence given:\nREPLACE (\u2019cat dog cat cat cat dog\u2019, \u2019cat\u2019, \u2019dog\u2019, 2) -> \u2019cat dog dog dog dog dog\nAll occurrence of \u2019cat\u2019 from the second occurrence onwards are replaced with \u2019dog\u2019\n\nREPLACE(\u2019cat dog cat cat dog\u2019 ,\u2019cat\u2019, dog\u2019, -2 -> \u2019dog dog dog cat dog\u2019\nAll occurrences starting at the second occurrence from the end of the string and moving backwards are replaced Note that a negative fourth argument without a fifth argument implies backwards mode.\n\nFive arguments: start occurrence and number of replacements given. Replace two occurrences of \u2019cat\u2019 starting at second occurrence:\nREPLACE (\u2019cat dog cat cat cat, \u2019cat\u2019, \u2019dog\u2019, 2,2) -> \u2019cat dog dog dog cat\u2019\nReplace two occurrences in backwards direction starting at the second occurrence:\nREPLACE (\u2019cat dog cat cat cat\u2019, ,\u2019cat\u2019, \u2019dog\u2019, 2, -2) -> \u2019dog dog dog cat cat \u2019\n\nReplace two occurrences in forwards direction starting at second occurrence from the end of the string:\nREPLACE (\u2019cat cat cat cat dog\u2019, \u2019cat\u2019, \u2019dog\u2019,-2,2) -> \u2019cat cat dog dog dog\u2019\nReplace two occurrences in backwards direction starting at second occurrence from the end of the string.\nREPLACE (\u2019cat cat cat cat dog\u2019,\u2019cat\u2019, \u2019dog\u2019, -2, -2) -> \u2019cat dog dog cat dog\u2019\n\nThe following examples all give the same result:\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, 4, 2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, 5, -2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019,-6, -2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, -7, 2)\n\nIn each case, the output string is\n\u2019cat1 cat2 cat3 dog4 dog5 cat6 cat7 cat8 cat9 cat10\u2019\n\nIf the replacement string text3 is a null string the required number of occurrences of the search string text2 are removed. For example:\nREPLACE (\u2019AAABBABZ\u2019, \u2019B\u2019, \u2019\u2019) -> \u2019AAAAZ\u2019\nREPLACE (\u2019AAABBABZ\u2019, \u2019B\u2019, \u2019\u2019, -1, -1) -> \u2019AAABBAZ\u2019\nIf the input string text1 is a null string or an unset text attribute, the input string text1 is returned unchanged. For example:\nREPLACE (\u2019\u2019, \u2019A\u2019,\u2019B\u2019) -> \u2019\u2019\nIf the search string text2 is longer than the input string text1, the input string text1 is returned unchanged. For example:\nREPLACE(\u2019AA\u2019, \u2019AAAAA\u2019 , \u2019B\u2019) -> \u2019AA\u2019\n\nIf no occurrence of the search string text2 is found, the input string text1 is returned unchanged. For example:\nIf required occurrence int1 is not found the input string text1 is returned unchanged. For example:\nREPLACE(\u2019AAAAAA\u2019, \u2019A\u2019, \u2019B\u2019, 10 )   -> \u2019AAAAAA\u2019\n\nIf the number of replacements required int2 is greater than the actual number of occurrence from the specified start occurrence, replacements are made up to the end of the string ( or beginning in backwards mode). For example:\nREPLACE (\u2019AAAAAA\u2019, \u2019A\u2019, \u2019B\u2019, -3, 8) -> \u2019BBBBAA\u2019\nSTRing ( any scalar type )\n-> text\nSTRing ( number , text1 )\n-> text\nSTRing ( pos , text1 )\n-> text\nTurns a value into a text string.\nWith a single argument the STRING function can be applied to the following scalar data types:\n\nWith only one argument, decimal places are output to give a maximum of six significant figures. Trailing zeros are always removed in this case.\n\nWith two arguments the data type may be either numeric (scalar) or position or direction. With two arguments, convert a number or position into a text string using the format described by text1, which may take any of the values between \u2019D0\u2019 and \u2019D6\u2019 (or \u2019d0\u2019 and \u2019d6\u2019), where the number indicates the number of decimal places.\n\nFor numbers, STRING always outputs values as millimetres. If unit conversion is needed then the DIST function should be used. For positions, the current distance units are used.\nNone.\nSTRING ( 1 ) -> \u20191\u2019\nSTRING ( 1 , \u2019D3\u2019 ) -> \u20191.000\u2019\nSTRING ( 1.23456789 ) -> \u20191.23457\u2019\nSTRING(1.1230000) ->\u20191.123\u2019\nSTRING ( 1.23456789 , \u2019D3\u2019 ) -> \u20191.235\u2019\nSTRING (9*9 LT 100) -> \u2019TRUE\u2019\nSTRING (OWN OF CE) -> \u2019/PIPE1\u2019\nSTRING(POS) -> \u2019W1000 N20000 U18000\u2019\nSTRING(POS, \u2019D4\u2019 ) -> \u2019W10000.1234 N20000.1234 U18000.1234\u2019\nSTRING(HDIR OF /PIPE1-1) -> \u2019D\u2019\nSTRING(E 22.0125 N, \u2019D2\u2019) -> \u2019E 22.01 N\u2019\nSTRING (ORI OF NEXT) -> \u2019Y IS D AND Z IS U\u2019\n\nSUBString ( text1 , number1 )\n-> text\nSUBString ( text1 , number1 , number2 )\n-> text\nWith two arguments, return the substring of text1 beginning at the position number1 to the end of text1.\nWith three arguments, return the substring of text1 beginning at the position number1 and of length number2. If number1 is negative, then counting of characters starts from the RHS of the input string. If number2 is negative, then characters up to and including the start position are returned.\nNone.\nSUBSTRING ( \u2019abcdef\u2019 , 3 ) -> \u2019cdef\u2019\nSUBSTRING ( \u2019abcdef\u2019 ,-3 ) -> \u2019abcd\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 3 , 2 ) -> \u2019cd\u2019\nSUBSTRING ( \u2019abcdef\u2019 , -3, 2 ) -> \u2019de\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 3 , -2 ) -> \u2019bc\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 10 ) -> \u2019\u2019\nSUBSTRING ( \u2019abcdef\u2019 , -10 , 2 ) -> \u2019ab\u2019\nNone.\nTRIM ( text1 )\n-> text\nTRIM ( text1, text2 )\n-> text\nTRIM ( text1, text2, text3 )\n-> text\nWhen only one argument is supplied, TRIM removes all spaces to the left (leading) and right (trailing) of text1 and returns the answer in text.\nWhen two arguments are supplied, text2 specifies where the spaces should be removed from: either \u2019L\u2019 or \u2019l\u2019 for left, \u2019R\u2019 or \u2019r\u2019 for right, and \u2019M\u2019 or \u2019m\u2019 for multiple (where multiple occurrences of blanks are squeezed to a single spaces) or any combination of the three key letters. So the default is \u2019LR\u2019 when this field is omitted.\nWhen the third argument text3 is also supplied, this should only be a single character which overrides the space character as the character being trimmed.\nNone.\nTRIM ( \u2019 How now, brown cow \u2019, \u2019LRM\u2019 ) -> \u2019How now, brown cow\u2019\nTRIM ( \u201910.3000\u2019, \u2019R\u2019, \u20190\u2019 ) -> \u201910.3\u2019\nNone.\nUNITSOF or UNIT\n(any real variable or expression)\n-> text\nEvaluates the real expression and returns its current units a text string. This is standard unit qualifier that would be output with the value when queried.\nThe argument can be a single real value (with or without unit qualifier) or any real expression.\nNone.\nNote these are only possible results, depending on current units\nUNITOF (1)\nUNITOF (1kg)\nUNITOF (1kg/m3)\nUNITOF (1 curie)\nUNITOF (1joule / 1 day / sqrt (1 m4))\nUNITOF (1 newton / sqrt (1 m4))\n-> \u2018\u2019\n-> lb\n-> lb/ft3\n-> curie\n-> j/s/mm2\n-> bar\nNone.\nVTEXT is used for the late evaluation of variables.\nVTEXT ( variable-name )\n-> text\nVTEXT ( variable-name , number )\n-> text\nWith one argument, it gets the value of the scalar variable or the value of the array variable element.\nWith two arguments, it gets the value of the element corresponding to the index number.\nThe value is returned as a text string.\nSee also VLOGICAL used for late evaluation when a logical result is required, and VVALUE used for late evaluation when a numeric result is required.\nIf the scalar variable, the array variable or the array variable element does not exist, the result is undefined.\nVTEXT ( !var ) -> \u2019hello\u2019\nVTEXT ( !array[1] ) -> \u20191.00\u2019\nVTEXT ( !array , 2 ) -> \u20190.00\u2019\nErrors Scalar variable may not be indexed (for example, VTEXT (!var[1]) ).\nArray variable must have an index (for example, VTEXT ( !array ) ).\n\nAFTER\nBEFORE\nDIMENSIONOF, DIMOF\nDIMWOOD\nDISTANCE\nLOWCASE, UPCASE\nPART\nREPLACE\nSTRING\nSUBS, DSUBS\nTRIM\nUNITSOF\nVTEXT\nSynopsis\nAFTER ( text1 , text2 )\n-> text\nDescription\nReturn the substring of text1 which is after the leftmost occurrence of text2 in text1.\nIf text2 does not occur in text1, the null string is returned.\nSide Effects\nNone.\nExample\nAFTER ( \u2019abcdef\u2019 , \u2019cd\u2019 ) ->\u2019ef\u2019\nAFTER ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> \u2019\u2019\nAFTER ( \u2019abcdef\u2019 , \u2019\u2019 ) -> \u2019abcdef\u2019\nErrors\nNone.\nSynopsis\nBEFORE ( text1 , text2 )\n-> text\nDescription\nReturn the substring of text1 which is before the leftmost occurrence of text2 in text1. If text2 does not occur in text1, text1 is returned.\nSide Effects\nNone.\nExample\nBEFORE ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> \u2019ab\u2019\nBEFORE ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> \u2019\u2019\nBEFORE ( \u2019abcdef\u2019 , \u2019\u2019 ) -> \u2018\u2019\nErrors\nNone.\nSynopsis\nDIMensionof or DIMOF\n(any real variable or expression)\n-> text\nDescription\nEvaluates the real expression and returns its physical dimension as a text string. This is name of the dimension in the table in Standard Units.\nThe argument can be a single real value (with or without unit qualifier) or any real expression.\nSide Effects\nNone.\nExample\nDim (1)\ndim(1kg)\ndimof(1kg/m3)\ndimensionof (1 curie)\ndim (1joule / 1 day / sqrt (1 m4))\ndim (1 newton / sqrt ( 1 m4)\n-> NONE\n-> Mass\n-> Density\n-> Radioactivity\n-> GENERIC\n-> Pressure\nErrors\nSynopsis\nDIMWORD\n(any real variable or expression)\n-> text\nDescription\nEvaluates the real expression and returns its physical dimension as a word string. This is HASH name of the dimension in the table in Standard Units.\nThe argument can be a single real value (with or without unit qualifier) or any real expression.\nSide Effects\nNone.\nExample\nDimword (1)\ndimword (1curie)\nDimword (1kg/5litre)\ndimword (1curie)\ndimword (1kg/5litre)\ndimword (1joule / 1 day / sqrt (1 m4))\ndimword (1 newton / sqrt (1 m4)\ndim(1kg)\n-> NONE\n-> RADY\n-> DENS\n-> RADY\n-> DENS\n-> GENERIC\n-> PRESS\n-> Mass\nErrors\nSynopsis\nDISTance ( number1 )\n-> text\nDISTance( number1, logical1, logical2, logical3, number2, logical4)\n-> text\nDescription\nFor the one-argument form, if the current distance units are FINCH, text is the conversion of the decimal inches value number1 into the format \u2019aa\u2019bb.cc/dd\u2019. Otherwise, text is the STRING conversion of number1.\nThe six-argument form is more complex. The format is:\nDIST/ANCE (distance, feet, usformat, fraction, denom_or_dp, zeros)\nwhere:\ndistance is the numeric distance in inches that is to be formatted.\nfeet is a logical flag set to true if output is to be in feet and inches and to false if output is to be in inches.\nusformat is a logical set to true if US format is to be used or false if AVEVA E3D Design format is to be used.\nfraction is a logical set to true if the fractional component is to be output as a fraction or false if to be output as a decimal denom_or_dp is a number representing the largest denominator if fraction is TRUE or representing the number of decimal places if it is FALSE.\nzeros is a logical set to true if zeros are to be shown when that component of the output has no value. .\nAVEVA E3D Design\nFor both US and AVEVA E3D Design formats the following rules are observed:\nIf distance is negative, the first symbol is a minus sign.\nIf feet is true and the distance is at least a foot, then the number of feet is output next, followed by a single quote (\u2019). Only if zeros is true will the number of feet be output as 0 for distances less than a foot. Otherwise the feet will be omitted.\nIf feet have been output, the inches will be at least two characters wide. Numbers less than ten will be preceded by a space if US format is being used or a zero if AVEVA E3D Design format is used. A zero will be output if there are no whole inches.\nIf no feet have been output and the distance is at least an inch, then the number of inches is displayed but without any preceding spaces. Only if zeros is true will a 0 be output for distances of less than an inch.\nIf inches have been output and fraction is true, these will be followed by a decimal point (.).\nIf fraction is TRUE and the number has a fractional component, then the numerator and the denominator are shown separated by a slash (/). This is then blank padded up to the width that the largest numerator and denominator would take.\nIf fraction is FALSE and the number of decimal places is greater than zero, then the decimal point (.) is displayed followed by the remainder up to the appropriate number of decimal places. If the number of decimal places is 0 then the decimal point is not shown either.\nIf US format has been selected then the following additional rules are observed on output:\nThe (\u2019) after the number of feet is followed by a dash\n(-).\nThe decimal point separating the inches from the fraction is replaced by a space.\nThe inches and fraction of inches are followed by a double quote(\").\nSide Effects\nNone.\nExample\nIf the current distance units are FINCH:\nDISTANCE ( 17.5 ) -> \u20191\u20195.1/2\u2019\nSome examples, where the current distance units are feet and inches:\nDIST(34.5,TRUE,TRUE,TRUE,100,TRUE) -> 2\u2019-10.1/2.\nDIST(34.5,FALSE,TRUE,FALSE,1,TRUE) -> 34.5\"\nDIST(34.5,FALSE,TRUE,TRUE,4,FALSE) -> 34 1/2\"\nDIST(128.5,TRUE,FALSE,TRUE,2,TRUE) -> 10\u201908.1/2\"\nThe following table shows sets of options that could have been chosen and the format of the output produced for different numbers. Blanks output by the system are represented by underscores(_).\nErrors\nThe value is too big to be converted.\nSynopsis\nUPCase ( text1 )\n-> text\nLOWCase ( text1 )\n-> text\nDescription\nReturn an upper or lower case version of text1.\nSide Effects\nNone.\nExample\nUPCASE ( \u2019False\u2019) -> \u2019FALSE\u2019\nLOWCASE ( \u2019False\u2019) -> \u2019false\u2019\nErrors\nNone.\nSynopsis\nPART(text1, number1)\n-> text\nPART(text1, number1 , text2)\n-> text\nDescription\nWith two arguments, returns the number1 component of text1 assuming that text1 is split on any whitespace characters. If number1 is negative, counting of components starts from the right.\nWith three arguments, as above, but use text2 as the separator on which splitting takes place.\nIf you give a part number higher than the number of components in the string, the function returns an empty string.\nSide Effects\nNone.\nExample\nPART (\u2019x-y-z\u2019, 1, \u2019-\u2019 -> \u2019x\u2019\nPART (\u2019a b c d e\u2019, 4-> \u2019d\u2019\nPART (\u2019/PIPE45/B9\u2019, -1, \u2019/\u2019) -> \u2019B9\u2019\nPART(\u2019aa bb cc\u2019, 2) -> \u2019bb\u2019\nPART(\u2019aa-bb-cc\u2019,3,\u2019-\u2019) -> \u2019cc\u2019\nErrors\nNone.\nSynopsis\nREPLace (text1,text2,text3)\n-> text\nREPLace(text1,text2,text3,int1)\n-> text\nREPLace(text1,text2,text2,int1,int2)\n-> text\nDescription\nReplace search string text2 in input string text1 with replacement string text3.\nIf int1 is given this specifies the first occurrence of text2 at which to start replacement.\nIf int2 is given this specifies the number of replacements to make. int1 and/or int2 may be negative to indicate that the direction is backwards.\nSide Effects\nNone.\nExample\nThree arguments:\nREPLACE (\u2019cat dog cat cat dog \u2019, \u2019cat\u2019, \u2019dog\u2019 ) -> \u2019dog dog dog dog dog\u2019\nAll occurrences of \u2019cat\u2019 are replaced with \u2019dog\u2019.\nFour arguments: start occurrence given:\nREPLACE (\u2019cat dog cat cat cat dog\u2019, \u2019cat\u2019, \u2019dog\u2019, 2) -> \u2019cat dog dog dog dog dog\nAll occurrence of \u2019cat\u2019 from the second occurrence onwards are replaced with \u2019dog\u2019\nREPLACE(\u2019cat dog cat cat dog\u2019 ,\u2019cat\u2019, dog\u2019, -2 -> \u2019dog dog dog cat dog\u2019\nAll occurrences starting at the second occurrence from the end of the string and moving backwards are replaced Note that a negative fourth argument without a fifth argument implies backwards mode.\nFive arguments: start occurrence and number of replacements given. Replace two occurrences of \u2019cat\u2019 starting at second occurrence:\nREPLACE (\u2019cat dog cat cat cat, \u2019cat\u2019, \u2019dog\u2019, 2,2) -> \u2019cat dog dog dog cat\u2019\nReplace two occurrences in backwards direction starting at the second occurrence:\nREPLACE (\u2019cat dog cat cat cat\u2019, ,\u2019cat\u2019, \u2019dog\u2019, 2, -2) -> \u2019dog dog dog cat cat \u2019\nReplace two occurrences in forwards direction starting at second occurrence from the end of the string:\nREPLACE (\u2019cat cat cat cat dog\u2019, \u2019cat\u2019, \u2019dog\u2019,-2,2) -> \u2019cat cat dog dog dog\u2019\nReplace two occurrences in backwards direction starting at second occurrence from the end of the string.\nREPLACE (\u2019cat cat cat cat dog\u2019,\u2019cat\u2019, \u2019dog\u2019, -2, -2) -> \u2019cat dog dog cat dog\u2019\nThe following examples all give the same result:\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, 4, 2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, 5, -2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019,-6, -2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, -7, 2)\nIn each case, the output string is\n\u2019cat1 cat2 cat3 dog4 dog5 cat6 cat7 cat8 cat9 cat10\u2019\nIf the replacement string text3 is a null string the required number of occurrences of the search string text2 are removed. For example:\nREPLACE (\u2019AAABBABZ\u2019, \u2019B\u2019, \u2019\u2019) -> \u2019AAAAZ\u2019\nREPLACE (\u2019AAABBABZ\u2019, \u2019B\u2019, \u2019\u2019, -1, -1) -> \u2019AAABBAZ\u2019\nErrors\nIf the input string text1 is a null string or an unset text attribute, the input string text1 is returned unchanged. For example:\nREPLACE (\u2019\u2019, \u2019A\u2019,\u2019B\u2019) -> \u2019\u2019\nIf the search string text2 is longer than the input string text1, the input string text1 is returned unchanged. For example:\nREPLACE(\u2019AA\u2019, \u2019AAAAA\u2019 , \u2019B\u2019) -> \u2019AA\u2019\nIf no occurrence of the search string text2 is found, the input string text1 is returned unchanged. For example:\nREPLACE( \u2019AAAAAA\u2019,\u2019B\u2019,\u2019C\u2019)  -> \u2019AAAAAA\nIf required occurrence int1 is not found the input string text1 is returned unchanged. For example:\nREPLACE(\u2019AAAAAA\u2019, \u2019A\u2019, \u2019B\u2019, 10 )   -> \u2019AAAAAA\u2019\nIf the number of replacements required int2 is greater than the actual number of occurrence from the specified start occurrence, replacements are made up to the end of the string ( or beginning in backwards mode). For example:\nREPLACE(\u2019AAAAAA\u2019, \u2019A\u2019, \u2019B\u2019, 2, 8) ->   \u2019ABBBBB\u2019\nREPLACE (\u2019AAAAAA\u2019, \u2019A\u2019, \u2019B\u2019, -3, 8) -> \u2019BBBBAA\u2019\nSynopsis\nSTRing ( any scalar type )\n-> text\nSTRing ( number , text1 )\n-> text\nSTRing ( pos , text1 )\n-> text\nDescription\nTurns a value into a text string.\nWith a single argument the STRING function can be applied to the following scalar data types:\nNumeric\nLogical\nId\nPosition\nDirection\nOrientation\nWith only one argument, decimal places are output to give a maximum of six significant figures. Trailing zeros are always removed in this case.\nWith two arguments the data type may be either numeric (scalar) or position or direction. With two arguments, convert a number or position into a text string using the format described by text1, which may take any of the values between \u2019D0\u2019 and \u2019D6\u2019 (or \u2019d0\u2019 and \u2019d6\u2019), where the number indicates the number of decimal places.\nFor numbers, STRING always outputs values as millimetres. If unit conversion is needed then the DIST function should be used. For positions, the current distance units are used.\nSide Effects\nNone.\nExample\nSTRING ( 1 ) -> \u20191\u2019\nSTRING ( 1 , \u2019D3\u2019 ) -> \u20191.000\u2019\nSTRING ( 1.23456789 ) -> \u20191.23457\u2019\nSTRING(1.1230000) ->\u20191.123\u2019\nSTRING ( 1.23456789 , \u2019D3\u2019 ) -> \u20191.235\u2019\nSTRING (9*9 LT 100) -> \u2019TRUE\u2019\nSTRING (OWN OF CE) -> \u2019/PIPE1\u2019\nSTRING(POS) -> \u2019W1000 N20000 U18000\u2019\nSTRING(POS, \u2019D4\u2019 ) -> \u2019W10000.1234 N20000.1234 U18000.1234\u2019\nSTRING(HDIR OF /PIPE1-1) -> \u2019D\u2019\nSTRING(E 22.0125 N, \u2019D2\u2019) -> \u2019E 22.01 N\u2019\nSTRING (ORI OF NEXT) -> \u2019Y IS D AND Z IS U\u2019\nErrors\nSynopsis\nSUBString ( text1 , number1 )\n-> text\nSUBString ( text1 , number1 , number2 )\n-> text\nDescription\nWith two arguments, return the substring of text1 beginning at the position number1 to the end of text1.\nWith three arguments, return the substring of text1 beginning at the position number1 and of length number2. If number1 is negative, then counting of characters starts from the RHS of the input string. If number2 is negative, then characters up to and including the start position are returned.\nSide Effects\nNone.\nExample\nSUBSTRING ( \u2019abcdef\u2019 , 3 ) -> \u2019cdef\u2019\nSUBSTRING ( \u2019abcdef\u2019 ,-3 ) -> \u2019abcd\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 3 , 2 ) -> \u2019cd\u2019\nSUBSTRING ( \u2019abcdef\u2019 , -3, 2 ) -> \u2019de\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 3 , -2 ) -> \u2019bc\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 10 ) -> \u2019\u2019\nSUBSTRING ( \u2019abcdef\u2019 , -10 , 2 ) -> \u2019ab\u2019\nErrors\nNone.\nSynopsis\nTRIM ( text1 )\n-> text\nTRIM ( text1, text2 )\n-> text\nTRIM ( text1, text2, text3 )\n-> text\nDescription\nWhen only one argument is supplied, TRIM removes all spaces to the left (leading) and right (trailing) of text1 and returns the answer in text.\nWhen two arguments are supplied, text2 specifies where the spaces should be removed from: either \u2019L\u2019 or \u2019l\u2019 for left, \u2019R\u2019 or \u2019r\u2019 for right, and \u2019M\u2019 or \u2019m\u2019 for multiple (where multiple occurrences of blanks are squeezed to a single spaces) or any combination of the three key letters. So the default is \u2019LR\u2019 when this field is omitted.\nWhen the third argument text3 is also supplied, this should only be a single character which overrides the space character as the character being trimmed.\nSide Effects\nNone.\nExample\nTRIM ( \u2019 How now, brown cow \u2019, \u2019LRM\u2019 ) -> \u2019How now, brown cow\u2019\nTRIM ( \u201910.3000\u2019, \u2019R\u2019, \u20190\u2019 ) -> \u201910.3\u2019\nErrors\nNone.\nSynopsis\nUNITSOF or UNIT\n(any real variable or expression)\n-> text\nDescription\nEvaluates the real expression and returns its current units a text string. This is standard unit qualifier that would be output with the value when queried.\nThe argument can be a single real value (with or without unit qualifier) or any real expression.\nSide Effects\nNone.\nExample\nNote these are only possible results, depending on current units\nUNITOF (1)\nUNITOF (1kg)\nUNITOF (1kg/m3)\nUNITOF (1 curie)\nUNITOF (1joule / 1 day / sqrt (1 m4))\nUNITOF (1 newton / sqrt (1 m4))\n-> \u2018\u2019\n-> lb\n-> lb/ft3\n-> curie\n-> j/s/mm2\n-> bar\nErrors\nNone.\nSynopsis\nVTEXT ( variable-name )\n-> text\nVTEXT ( variable-name , number )\n-> text\nDescription\nWith one argument, it gets the value of the scalar variable or the value of the array variable element.\nWith two arguments, it gets the value of the element corresponding to the index number.\nThe value is returned as a text string.\nSee also VLOGICAL used for late evaluation when a logical result is required, and VVALUE used for late evaluation when a numeric result is required.\nSide Effects\nIf the scalar variable, the array variable or the array variable element does not exist, the result is undefined.\nExample\nVTEXT ( !var ) -> \u2019hello\u2019\nVTEXT ( !array[1] ) -> \u20191.00\u2019\nVTEXT ( !array , 2 ) -> \u20190.00\u2019\nErrors\nErrors Scalar variable may not be indexed (for example, VTEXT (!var[1]) ).\nArray variable must have an index (for example, VTEXT ( !array ) ).\ndistance is the numeric distance in inches that is to be formatted.\nfeet is a logical flag set to true if output is to be in feet and inches and to false if output is to be in inches.\nusformat is a logical set to true if US format is to be used or false if AVEVA E3D Design format is to be used.\ndistance is the numeric distance in inches that is to be formatted.\ndistance is the numeric distance in inches that is to be formatted.\nfeet is a logical flag set to true if output is to be in feet and inches and to false if output is to be in inches.\nfeet is a logical flag set to true if output is to be in feet and inches and to false if output is to be in inches.\nusformat is a logical set to true if US format is to be used or false if AVEVA E3D Design format is to be used.\nusformat is a logical set to true if US format is to be used or false if AVEVA E3D Design format is to be used.\nfraction is a logical set to true if the fractional component is to be output as a fraction or false if to be output as a decimal denom_or_dp is a number representing the largest denominator if fraction is TRUE or representing the number of decimal places if it is FALSE.\nzeros is a logical set to true if zeros are to be shown when that component of the output has no value. .\nfraction is a logical set to true if the fractional component is to be output as a fraction or false if to be output as a decimal denom_or_dp is a number representing the largest denominator if fraction is TRUE or representing the number of decimal places if it is FALSE.\nfraction is a logical set to true if the fractional component is to be output as a fraction or false if to be output as a decimal denom_or_dp is a number representing the largest denominator if fraction is TRUE or representing the number of decimal places if it is FALSE.\nzeros is a logical set to true if zeros are to be shown when that component of the output has no value. .\nzeros is a logical set to true if zeros are to be shown when that component of the output has no value. .\nIf distance is negative, the first symbol is a minus sign.\nIf feet is true and the distance is at least a foot, then the number of feet is output next, followed by a single quote (\u2019). Only if zeros is true will the number of feet be output as 0 for distances less than a foot. Otherwise the feet will be omitted.\nIf distance is negative, the first symbol is a minus sign.\nIf distance is negative, the first symbol is a minus sign.\nIf feet is true and the distance is at least a foot, then the number of feet is output next, followed by a single quote (\u2019). Only if zeros is true will the number of feet be output as 0 for distances less than a foot. Otherwise the feet will be omitted.\nIf feet is true and the distance is at least a foot, then the number of feet is output next, followed by a single quote (\u2019). Only if zeros is true will the number of feet be output as 0 for distances less than a foot. Otherwise the feet will be omitted.\nIf feet have been output, the inches will be at least two characters wide. Numbers less than ten will be preceded by a space if US format is being used or a zero if AVEVA E3D Design format is used. A zero will be output if there are no whole inches.\nIf feet have been output, the inches will be at least two characters wide. Numbers less than ten will be preceded by a space if US format is being used or a zero if AVEVA E3D Design format is used. A zero will be output if there are no whole inches.\nIf feet have been output, the inches will be at least two characters wide. Numbers less than ten will be preceded by a space if US format is being used or a zero if AVEVA E3D Design format is used. A zero will be output if there are no whole inches.\nIf no feet have been output and the distance is at least an inch, then the number of inches is displayed but without any preceding spaces. Only if zeros is true will a 0 be output for distances of less than an inch.\nIf inches have been output and fraction is true, these will be followed by a decimal point (.).\nIf no feet have been output and the distance is at least an inch, then the number of inches is displayed but without any preceding spaces. Only if zeros is true will a 0 be output for distances of less than an inch.\nIf no feet have been output and the distance is at least an inch, then the number of inches is displayed but without any preceding spaces. Only if zeros is true will a 0 be output for distances of less than an inch.\nIf inches have been output and fraction is true, these will be followed by a decimal point (.).\nIf inches have been output and fraction is true, these will be followed by a decimal point (.).\nIf fraction is TRUE and the number has a fractional component, then the numerator and the denominator are shown separated by a slash (/). This is then blank padded up to the width that the largest numerator and denominator would take.\nIf fraction is TRUE and the number has a fractional component, then the numerator and the denominator are shown separated by a slash (/). This is then blank padded up to the width that the largest numerator and denominator would take.\nIf fraction is TRUE and the number has a fractional component, then the numerator and the denominator are shown separated by a slash (/). This is then blank padded up to the width that the largest numerator and denominator would take.\nIf fraction is FALSE and the number of decimal places is greater than zero, then the decimal point (.) is displayed followed by the remainder up to the appropriate number of decimal places. If the number of decimal places is 0 then the decimal point is not shown either.\nIf US format has been selected then the following additional rules are observed on output:\nIf fraction is FALSE and the number of decimal places is greater than zero, then the decimal point (.) is displayed followed by the remainder up to the appropriate number of decimal places. If the number of decimal places is 0 then the decimal point is not shown either.\nIf fraction is FALSE and the number of decimal places is greater than zero, then the decimal point (.) is displayed followed by the remainder up to the appropriate number of decimal places. If the number of decimal places is 0 then the decimal point is not shown either.\nIf US format has been selected then the following additional rules are observed on output:\nIf US format has been selected then the following additional rules are observed on output:\nThe (\u2019) after the number of feet is followed by a dash\n(-).\nThe decimal point separating the inches from the fraction is replaced by a space.\nThe (\u2019) after the number of feet is followed by a dash\nThe (\u2019) after the number of feet is followed by a dash\n(-).\n(-).\nThe decimal point separating the inches from the fraction is replaced by a space.\nThe decimal point separating the inches from"}
{"Headers": "Late Evaluation of Variables in Expressions", "Content": "The functions Valid Value elements (VVALUE), VLOGICAL and VTEXT are used for late evaluation of Programmable Macro Language (PML) variables, that is, they enable you to specify PML variables in expressions which will not be evaluated until the expression is evaluated. For example, when you are creating a report template, you are actually creating a macro which will run when a report is generated. All variables in a report template must therefore be preceded by a suitable late evaluation operator; otherwise the system will try to substitute a value for the variable when it is entered on the form. The difference between the operators is the type of output. VVALUE is used to output a numeric value, VLOGICAL to output a logical variable and VTEXT to output a text variable.\n\n\n"}
{"Headers": "Attributes in Expressions", "Content": "All attributes and pseudo-attributes may be recognised within expressions. Optionally they may be followed by \u2019OF\u2019 to denote a different element to the current one; for example, POS OF /VESS1. Brackets may be used to denote an element of an array, for example DESP[8 + 1] for the ninth value of DESP. Since syntax clashes are possible, the keyword ATTRIB may be used to denote that an attribute follows. For example, ATTRIB E will denote the pseudo-attribute EAST as opposed to the start of a position or direction. Attributes are described in the Data Model Reference Manual.\n\n\n\nData Model Reference Manual\nDESP[8 + 1]\nData Model Reference Manual"}
{"Headers": "Query Expressions", "Content": "All expressions may be queried. Arrays are always concatenated into a single variable. Imperial values are always output as inch to variables. This preserves maximum accuracy. To output in FINCH, then the DISTANCE function must be used. In general expression do not have to be enclosed in brackets, but to be sure that other queries are not picked up by mistake then it is advisable to do so.\nParticular queries that could lead to confusion are those available both outside and inside expressions. These are:\nThe functionality may vary between outside and inside expression queries. For example, \u2019Q N 100 FROM /POSS\u2019 is not valid. It must be entered as Q N 100 FROM /POSS ).\nQ PPOINT n\nQ POS or cartesian position\nQ ORI or cartesian orientation\nQ PPOINT n\nQ PPOINT n\nQ POS or cartesian position\nQ POS or cartesian position\nQ ORI or cartesian orientation\nQ ORI or cartesian orientation\n\n\n\nQ PPOINT n\nQ POS or cartesian position\nQ ORI or cartesian orientation\n\u2019Q N 100 FROM /POSS\u2019\nQ N 100 FROM /POSS"}
{"Headers": "Precision of Comparisons", "Content": "To allow for small losses of accuracy, the following tolerances are used.\nNumber\nTolerance factor of 0.000001.\nIn other words, if the difference between two reals is not greater than 0.000001* (maximum of the two values) then the values are considered to be equal. For example,\nPosition\nConsidered to be equal if within 0.5 mm of one another.\nDirection or Orientation\nConsidered to be equal if values are within 0.005.\n\nObject\nTolerance\nNumber\nTolerance factor of 0.000001.\nIn other words, if the difference between two reals is not greater than 0.000001* (maximum of the two values) then the values are considered to be equal. For example,\n(1.000001 GT 1) is FALSE as it considers 1.000001; and 1 to be equal;\n(1.000002 GT 1) is TRUE.\nPosition\nConsidered to be equal if within 0.5 mm of one another.\nDirection or Orientation\nConsidered to be equal if values are within 0.005.\n(1.000001 GT 1) is FALSE as it considers 1.000001; and 1 to be equal;\n(1.000002 GT 1) is TRUE.\n(1.000001 GT 1) is FALSE as it considers 1.000001; and 1 to be equal;\n(1.000001 GT 1) is FALSE as it considers 1.000001; and 1 to be equal;\n(1.000002 GT 1) is TRUE.\n(1.000002 GT 1) is TRUE.\n\n\n"}
{"Headers": "Undefined Values", "Content": "In order to permit expressions like ((DIAM GT 200.0) OR (TYPE EQ \u2019BOX\u2019)), expressions must be able to cope with undefined values. Generally, applying an operator to one or more undefined arguments has an undefined result.\nTwo exceptions are: the use of the AND operator with a false argument, will result in FALSE, regardless of whether or not the remainder of the arguments are defined; and OR which returns TRUE if any of its arguments is TRUE. For example, consider applying the above expression when the current element is a box. DIAM is undefined; therefore (DIAM GT 200.0) is also undefined. However, (TYPE EQ \u2019BOX\u2019) is certainly true and so the final result of the whole expression evaluates to TRUE.\nAn undefined result occurs when:\nOne of the operands or arguments of a function (except some cases of AND and OR) is undefined.\nAn attribute is unavailable for the corresponding element (for example, \u2019DIAM OF OWNER\u2019 when the current element is a box).\nAn element is undefined (for example, \u2019OWNER\u2019 when the current element is the WORLD).\nAn attribute is unset (for example, text attribute or User defined Atrtribute (UDA) of length 0).\nA variable is undefined (for example, \u2019VVAL(!ARC6)\u2019 where !ARC6 has never been initialized).\nTwo position constants are compared with GT, GE, LT or LE and they have no common coordinates (for example, \u2019N10 EQ E5\u2019).\nIf the result of the whole expression is undefined, an error occurs.\nOne of the operands or arguments of a function (except some cases of AND and OR) is undefined.\nOne of the operands or arguments of a function (except some cases of AND and OR) is undefined.\nAn attribute is unavailable for the corresponding element (for example, \u2019DIAM OF OWNER\u2019 when the current element is a box).\nAn attribute is unavailable for the corresponding element (for example, \u2019DIAM OF OWNER\u2019 when the current element is a box).\nAn element is undefined (for example, \u2019OWNER\u2019 when the current element is the WORLD).\nAn element is undefined (for example, \u2019OWNER\u2019 when the current element is the WORLD).\nAn attribute is unset (for example, text attribute or User defined Atrtribute (UDA) of length 0).\nAn attribute is unset (for example, text attribute or User defined Atrtribute (UDA) of length 0).\nA variable is undefined (for example, \u2019VVAL(!ARC6)\u2019 where !ARC6 has never been initialized).\nA variable is undefined (for example, \u2019VVAL(!ARC6)\u2019 where !ARC6 has never been initialized).\nTwo position constants are compared with GT, GE, LT or LE and they have no common coordinates (for example, \u2019N10 EQ E5\u2019).\nTwo position constants are compared with GT, GE, LT or LE and they have no common coordinates (for example, \u2019N10 EQ E5\u2019).\nIf the result of the whole expression is undefined, an error occurs.\nIf the result of the whole expression is undefined, an error occurs.\n\n\n\n((DIAM GT 200.0) OR (TYPE EQ \u2019BOX\u2019))\n(DIAM GT 200.0)\n(TYPE EQ \u2019BOX\u2019)\n\u2019DIAM OF OWNER\u2019\n\u2019OWNER\u2019\n\u2019VVAL(!ARC6)\u2019\n!ARC6\n\u2019N10 EQ E5\u2019"}
{"Headers": "Unset Values", "Content": "A particular class of undefined values are unset values. The concept exists for attributes which are valid for a given element, but for which no value has been assigned. Typically these may be elements of an array, or \u2019word\u2019 attributes. References of value =0/0 are also treated as unset.\nUnset values are propagated as for undefined values (except for Boolean operations- see below). Undefined values take precedence over unset. There is a specific logical function UNSET to test if a values is unset.\nAcross comparisons, unset values are not propagated, but are treated as follows:\nEQ, GT, GE, LT, LE\nResults in FALSE.\nNE\nResults in TRUE.\nOR , AND\nValues are treated as FALSE.\nFor example, if DESP(2) and LVAL(3) are unset then:\nOperator\nWhen Applied to an UNSET\nEQ, GT, GE, LT, LE\nResults in FALSE.\nNE\nResults in TRUE.\nOR , AND\nValues are treated as FALSE.\n(DESP(2) GT 99) -> False\n(DESP(2) NE 33) -> True\n(:LVAL(3) AND TRUE) -> False\n\n\n\nDESP(2)\nLVAL(3)"}
{"Headers": "Rules to Define Attribute Settings", "Content": "Rather than being set explicitly, the values of some types of attribute can be specified in terms of rules; that is, expressions from which the attribute values can be evaluated. Rules can be set only for attributes of the following types (including user-defined attributes): text, scalar (integer, real or logical), position, orientation, direction; they cannot be set for reference attributes. A static rule will change the attribute setting only when verified or executed explicitly, whereas a dynamic rule will update the attribute setting whenever any part of the expression changes (the default type is static).\n\n\n\nstatic\ndynamic"}
{"Headers": "Set Attribute Rules", "Content": "Lets you set a rule for the value of a single named attribute. The rule may contain any valid expression of the type applicable to the attribute setting.\nRULE SET ZLEN (XLEN + YLEN)\n\nSets rule that ZLEN of the current element is the sum of its XLEN and YLEN values. The ZLEN will be updated to reflect changes to XLEN or YLEN only when the rule is verified or executed (i.e. it is a static rule).\nRULE SET XLEN DYNAM (YLEN + 2)\n\nXLEN will be updated automatically whenever YLEN is changed.\nRULE SET POS (N300 E400 U500) ON ALL BOX FOR /PUMP1\n\nSets rule for position attribute for all boxes in /PUMP1\nRULE SET POS DYNAM (N100 FROM /BOX2 )\n\nIf BOX2 moves, the element with this attribute rule will move with it automatically. (Note space between last character of element name and closing parenthesis.)\nQ ATT\nDisplays all attribute values and all rules for the current element.\nQ RULES\nDisplays all rules for current element.\nQ RUL OF XLEN\nDisplays rule for XLEN attribute of current element.\nQ ATT\nDisplays all attribute values and all rules for the current element.\nQ RULES\nDisplays all rules for current element.\nQ RUL OF XLEN\nDisplays rule for XLEN attribute of current element.\n\nExamples\nRULE SET ZLEN (XLEN + YLEN)\nSets rule that ZLEN of the current element is the sum of its XLEN and YLEN values. The ZLEN will be updated to reflect changes to XLEN or YLEN only when the rule is verified or executed (i.e. it is a static rule).\nRULE SET XLEN DYNAM (YLEN + 2)\nXLEN will be updated automatically whenever YLEN is changed.\nRULE SET POS (N300 E400 U500) ON ALL BOX FOR /PUMP1\nSets rule for position attribute for all boxes in /PUMP1\nRULE SET POS DYNAM (N100 FROM /BOX2 )\nIf BOX2 moves, the element with this attribute rule will move with it automatically. (Note space between last character of element name and closing parenthesis.)\nQ ATT\nDisplays all attribute values and all rules for the current element.\nQ RULES\nDisplays all rules for current element.\nQ RUL OF XLEN\nDisplays rule for XLEN attribute of current element.\n>- RULE SET - attribute_name -+- STAtic --.\n                              |           |\n                              |- DYNamic -|\n                              |           |\n                              \u2018-----------+- <expre> -+- ON -.\n                                                      |      |\n                                                      \u2018------+-.\n                                                               |\n                                                        .------\u2019\n                                                        |\n                                                        \u2018-+- <selatt> -.\n                                                          |            |\n                                                          \u2018------------+->\n   \n\n\n\nRULE SET ZLEN (XLEN + YLEN)\nRULE SET XLEN DYNAM (YLEN + 2)\nRULE SET POS (N300 E400 U500) ON ALL BOX FOR /PUMP1\nRULE SET POS DYNAM (N100 FROM /BOX2 )\nQ ATT\nQ RULES\nQ RUL OF XLEN"}
{"Headers": "Verify Attribute Rules", "Content": "When a rule is verified, the expression held in the rule is evaluated and both the result of the evaluation and the current value of the attribute are displayed.\nRULE VERIFY ALL\n\nVerifies all rules for the current element.\nRULE VER HEIG ON CYLI 1 FOR /PUMP1\n\nVerifies rule for height attribute on first cylinder of /PUMP1.\nExamples\nRULE VERIFY ALL\nVerifies all rules for the current element.\nRULE VER HEIG ON CYLI 1 FOR /PUMP1\nVerifies rule for height attribute on first cylinder of /PUMP1.\n>-- RULE VERify --+-- attribute_name --.\n                  |                    |\n                  \u2018-- ALL -------------+-- ON --.\n                                       |        |\n                                       \u2018--------+-- <selatt> --.\n                                                |              |\n                                                \u2018--------------+-->\n   \n\n\n\nRULE VERIFY ALL\nRULE VER HEIG ON CYLI 1 FOR /PUMP1"}
{"Headers": "Execute Attribute Rules", "Content": "When a rule is executed, the expression held in the rule is evaluated and the value of the attribute is replaced by the result of the evaluation.\nRULE EXECUTE :TEMP1\n\nExecutes rule for uda :TEMP1 for the current element.\nRULE EXE ALL ON ALL BOX FOR /PUMP1\n\nExecutes all rules for all boxes owned by /PUMP1.\nExamples\nRULE EXECUTE :TEMP1\nExecutes rule for uda :TEMP1 for the current element.\nRULE EXE ALL ON ALL BOX FOR /PUMP1\nExecutes all rules for all boxes owned by /PUMP1.\n>-- RULE EXEcute --+-- attribute_name --.\n                   |                    |\n                   \u2018-- ALL -------------+-- ON --.\n                                        |        |\n                                        \u2018--------+-- <selatt> --.\n                                                 |              |\n                                                 \u2018--------------+->\n   \n\n\n\nRULE EXECUTE :TEMP1\nRULE EXE ALL ON ALL BOX FOR /PUMP1"}
{"Headers": "Delete Attribute Rules", "Content": "Lets you delete one or more rules for the current element or for specified elements.\nRULE DELETE ALL\n\nDeletes all rules for the current element.\nRULE DEL ALL ON ALL FOR /PUMP1\n\nDeletes all rules for all primitives owned by /PUMP1.\nExamples\nRULE DELETE ALL\nDeletes all rules for the current element.\nRULE DEL ALL ON ALL FOR /PUMP1\nDeletes all rules for all primitives owned by /PUMP1.\n>-- RULE DELete --+-- attribute_name --.\n                  |                    |\n                  \u2018-- ALL -------------+-- ON --.\n                                       |        |\n                                       \u2018--------+-- <selatt> --.\n                                                |              |\n                                                \u2018--------------+-->\n   \n\n\n\nRULE DELETE ALL\nRULE DEL ALL ON ALL FOR /PUMP1"}
{"Headers": "Rules for Arrays", "Content": "Rules can be set for array attributes by using the NUM syntax, for example, the following sets rules for the first 3 design parameters.\nRUL SET DESP NUM 1 ( DESP(1) OF /RULE-SCTN )\nRUL SET DESP NUM 2 ( DESP(4) OF /RULE-SCTN )\nRUL SET DESP NUM 3 ( 100 + DESP(2) OF PREV )\n\n\n"}
{"Headers": "Collections", "Content": "You can create an array which includes a number of elements which all satisfy specific selection criteria, as defined by yourself. This is a useful way of collecting information on particular elements. You use the syntax:\n!Array is the name of the array that will be created to contain the elements selected.\nThe following general criteria can be used to define the selection:\nIt is possible to limit the number of items collected using the MAX number option. Starting for example: MAX 50, will collect only the first 50 items that matches the criteria given.\nClass is essentially a list of element types (or possibly of actual elements). This list can be optionally qualified to indicate whether members should be included, or whether only \u2018items\u2019 (that is, the lowest level components in the hierarchy below a given element) should be included.\nFor example:\nALL\nSelects all elements\nALL FRMW\nSelects all framework elements\nALL BRANCH MEMBERS\nSelects all piping components\nITEMS OF EQUI /VESS1\nSelects all primitives below /VESS1\n( /PIPE1 /PIPE2 )\nSelects only /PIPE1 and /PIPE2.\nThe command:\nWould create the array !PIPECOMPS and set it to contain the reference numbers of every piping component in the MDB.\nLogical expressions, which return TRUE or FALSE, can be used. They are most likely to be used to check the value of an attribute for collection. The WITH or WHERE options introduce the expression. For example:\nwould collect all elements for which the attributes XLEN, YLEN and ZLEN match the criteria in the array !LENGTHS.\nA volume is defined by the WITHIN keyword. You can define the volume either in terms of two diagonally opposite points of an enclosing box, or as a volume around an element (with an optional clearance around the box which contains the element). For example:\ncollects all elements in the defined volume into the array !VOLUME.\ncollects all piping components within the volume defined by a box \u2018drawn\u2019 1500 mm around /PUMP1 and puts them into the array !P. The EXCLUSIVE keyword indicates that only the chosen elements exclusively within the given volume are to be selected.\nIn Plant there are structural design data, termed MODEL, and detailed design data, termed PRODUCTION. These two sets of data represent the same model and occupy the same 3D space. For a volumetric query you only want one of the sets of data returned.\nThese two options allow you to choose which set of data will be returned by the volumetric query.\nQ VOLUMEOPTION HULL DESIGN\nReturns DESIGN data\nQ VOLUMEOPTION HULL PRODUCTION\nReturns PRODUCTION data\nQ VOLUMEOPTION HULL DESIGN\nReturns DESIGN data\nQ VOLUMEOPTION HULL PRODUCTION\nReturns PRODUCTION data\nHierarchy criteria can be defined by the FOR keyword. It identifies a list of elements below which all selected elements must occur. You can also include an exclusion list. For example:\nYou can append the results of such a collection to an existing array using the APPEND keyword. For example:\nWould add the references for all elbows to the array !BENDS.\nYou can also overwrite elements in the array by specifying the first index in the array which you want to be overwritten. The specified index, and the indexes following it, will be overwritten by the results. For example:\nWould place the reference for the first ELBOW selected at position 99 in the array !BENDS, overwriting any existing data, and subsequent selections in the array elements that follow.\nIf you specify more than one criteria, the specifications must be in the above order Some more examples:\nALL\nSelects all elements\nALL FRMW\nSelects all framework elements\nALL BRANCH MEMBERS\nSelects all piping components\nITEMS OF EQUI /VESS1\nSelects all primitives below /VESS1\n( /PIPE1 /PIPE2 )\nSelects just /PIPE1 and /PIPE2\nALL WITH (XLEN GT 1000 )\nSelects all elements where XLEN is greater than 1000mm\nALL WITHIN W8000N17000U1000 TO W1400N13500U1200\nSelects all elements within the defined volume\nALL PIPE WITHIN VOLUME /PIPE1 1500\nSelects all piping elements within a volume defined as a box drawn around /PIPE1, with a clearance of 1500mm between the edges of /PIPE1 and the volume box.\nALL\nSelects all elements\nALL FRMW\nSelects all framework elements\nALL BRANCH MEMBERS\nSelects all piping components\nITEMS OF EQUI /VESS1\nSelects all primitives below /VESS1\n( /PIPE1 /PIPE2 )\nSelects just /PIPE1 and /PIPE2\nALL WITH (XLEN GT 1000 )\n\nSelects all elements where XLEN is greater than 1000mm\nALL WITHIN W8000N17000U1000 TO W1400N13500U1200\n\nSelects all elements within the defined volume\nALL PIPE WITHIN VOLUME /PIPE1 1500\n\nSelects all piping elements within a volume defined as a box drawn around /PIPE1, with a clearance of 1500mm between the edges of /PIPE1 and the volume box.\nTypically, the expression is the slowest condition to evaluate, so it is important to limit the selection as much as possible. For instance, take the example which appeared above:\nSince only BOXes (and NBOXes) meet this criterion it would be sensible to limit the search by specifying an appropriate class:\nThis cuts the time to execute the selection. This is because the selection system knows that BOXes only occur in DESI databases. Therefore it does not search other types of database. It also knows where boxes are in the hierarchy, and so does not search unnecessary elements.\nEven greater performance savings can be gained by explicitly limiting the elements which have to be visited by the search:\nBy default, the entire MDB is searched. But by specifying a hierarchy criterion, the selection time can be cut considerably.\nLimiting the volume of the search also cuts the number of elements which have to be checked. However, it should be noted that this criterion is applied by determining whether element limit boxes fall within the specified volume, using the spatial map. This is a fast approach, but is not meant to provide the same accuracy as is used in on line clashing.\nwill set up the array IPIPECOMPS to contain the reference numbers of every piping component in the MDB, e.g.\nEvery flange could then be extracted as follows:\nand then enhanced (highlighted):\nThis could alternatively be performed in one step:\nCollections may be joined or concatenated by preceding the COLLECT keyword by APPEND:\nAlternatively, the following:\nwould place the reference of the first SLCY at position 99 in !LIST overwriting any data that already exists at that and subsequent elements of the array.\nIf a selection contains elements of type TUBIng, then the collection describes it as the Leave Tube of an existing database element:\nThen !TUBING would contain something like the following:\n!TUBING[1]\n'IL TUB OF =20/302'\n!TUBING[2]\n'IL TUB OF =20/303'\n!TUBING[1]\n'IL TUB OF =20/302'\n!TUBING[2]\n'IL TUB OF =20/303'\nThe evaluate command allows an expression to be evaluation for all members of a collection.\nThe syntax is:\nVAR !variable EVALUATE expression For selection e.g. to get the description of all equipment you can do:\nThe PML collection object can also be used as an alternative to the COLLECTION syntax. This object is described in the Software Customisation Reference Manual.\nThe name of a given prefix may be collected using the 'FROM TABLE NAME PREFIX' option.\nFor example:\nThis will find all names starting with 'B'.\nThe syntax may be used in conjunction with the standard options. E.g.\nSome reference attributes index the attribute values. For these the indexed values can be accessed directly using FROM TABLE XXXX VALUE YYYY, where XXX is the attribute name and YYYY is the attribute match.\nFor example:\nThis will return all elements with SPRE set to /RF300/100G.\nThe syntax may be used in conjunction with the standard options. For example:\nSearching using indexes directly will be considerably faster than the standard searches.for example:\nThe referenced attributes that are indexed are:\nCATR\nCatalog reference\nPTRE\nPoint set reference\nGMRE\ngeometry set reference\nDTRE\nData set reference\nPSTR\nStructural Pline set reference\nGSTR\nStructural geometry set reference\nNGMR\nNegative geometry set reference\nPAIREF\nReference to a PAINT element\nSRFTRE\nReference to a SRFTRT element\nSLOREF\nPipe slope reference\nINSURE\nReference to a INSCMP element\nDOCREF\nCross reference DOCU elements\nCATR\nCatalog reference\nSPRE\nSprec reference\nLSTU\nTube spec\nISPE\nInsulation ref\nHSTU\nHead tube spec\nINRE\nInsulation reference\nHCREF\nReferences to head connected branches\nTCREF\nReferences to tail connected branches\nGOBREF\nHull Generating OBject REFerence\nCONNRE\nConnections on nodes\nPOSREF\nReference to point\nMDSYSF\nmodel reference\nACCREF\nAccess element reference\nHDBREF\nHull generic references\nHTPREF\nHull topological object model reference\nSCHLNK\nConnectivity link to schematic item references\nDESLNK\nConnectivity link to design model item references\nENGLNK\nConnectivity link to design model item references\nPRODRF\nreference from outfitting element to hull element\nSPBREF\nSpace boundary element reference\nSPINRE\nSpace inventory element reference\nINPRTR\nInside Paint Reference\nOUPRTR\nOutside Paint Reference\nASSTAR\nAssociation target reference\nMARKRF\nCable Mark points\nASSTMP\nAssembly template reference\nROUTND\nCable Preliminary route point\nSLOREF\nPipe slope reference\nTo benefit from indexing you must use the 'FROM TABLE' syntax in collections. This syntax is similar the same as for system attributes.\nFor Text Userd Defined Attributes (UDAS):\nwill find all elements in current Database (DB) with :MYTEXTATT set to 'fred'\nwill find all elements in current DB with :MYTEXTATT starting with 'fred'\nFor Integer UDAS:\nThis will find all elements with a :MYATT of 100\nThis will find all elements where :MYATT is between 100 and 110.\nFor Ref Attributes:\nwill find all elements in current DB with :MYREFATT set to /PIPE1\nThe new syntax may be combined with existing collection syntax. E.g.\nCurrently a collection can be restricted to a specific DB by navigating to a specific DB and setting the scope of /*. For example:\nAt 12.1 the DB name may be specified as part of the collection.\nFor example:\nOr\nOr\nCommand\nEffect\nALL\nSelects all elements\nALL FRMW\nSelects all framework elements\nALL BRANCH MEMBERS\nSelects all piping components\nITEMS OF EQUI /VESS1\nSelects all primitives below /VESS1\n( /PIPE1 /PIPE2 )\nSelects only /PIPE1 and /PIPE2.\nQ VOLUMEOPTION HULL DESIGN\nReturns DESIGN data\nQ VOLUMEOPTION HULL PRODUCTION\nReturns PRODUCTION data\nALL\nSelects all elements\nALL FRMW\nSelects all framework elements\nALL BRANCH MEMBERS\nSelects all piping components\nITEMS OF EQUI /VESS1\nSelects all primitives below /VESS1\n( /PIPE1 /PIPE2 )\nSelects just /PIPE1 and /PIPE2\nALL WITH (XLEN GT 1000 )\nSelects all elements where XLEN is greater than 1000mm\nALL WITHIN W8000N17000U1000 TO W1400N13500U1200\nSelects all elements within the defined volume\nALL PIPE WITHIN VOLUME /PIPE1 1500\nSelects all piping elements within a volume defined as a box drawn around /PIPE1, with a clearance of 1500mm between the edges of /PIPE1 and the volume box.\n!TUBING[1]\n'IL TUB OF =20/302'\n!TUBING[2]\n'IL TUB OF =20/303'\nCatalog DB\nCATR\nCatalog reference\nPTRE\nPoint set reference\nGMRE\ngeometry set reference\nDTRE\nData set reference\nPSTR\nStructural Pline set reference\nGSTR\nStructural geometry set reference\nNGMR\nNegative geometry set reference\nPAIREF\nReference to a PAINT element\nSRFTRE\nReference to a SRFTRT element\nSLOREF\nPipe slope reference\nINSURE\nReference to a INSCMP element\nDesign DB\nDOCREF\nCross reference DOCU elements\nCATR\nCatalog reference\nSPRE\nSprec reference\nLSTU\nTube spec\nISPE\nInsulation ref\nHSTU\nHead tube spec\nINRE\nInsulation reference\nHCREF\nReferences to head connected branches\nTCREF\nReferences to tail connected branches\nGOBREF\nHull Generating OBject REFerence\nCONNRE\nConnections on nodes\nPOSREF\nReference to point\nMDSYSF\nmodel reference\nACCREF\nAccess element reference\nHDBREF\nHull generic references\nHTPREF\nHull topological object model reference\nSCHLNK\nConnectivity link to schematic item references\nDESLNK\nConnectivity link to design model item references\nENGLNK\nConnectivity link to design model item references\nPRODRF\nreference from outfitting element to hull element\nSPBREF\nSpace boundary element reference\nSPINRE\nSpace inventory element reference\nINPRTR\nInside Paint Reference\nOUPRTR\nOutside Paint Reference\nASSTAR\nAssociation target reference\nMARKRF\nCable Mark points\nASSTMP\nAssembly template reference\nROUTND\nCable Preliminary route point\nSLOREF\nPipe slope reference\nVAR !Array COLLECT selection criteria MAX number\n   \nVAR !PIPECOMPS COLLECT ALL BRANCH MEMBERS\nVAR !LENGTHS COLLECT ALL WITH ( XLEN * YLEN 8 ZLEN GT 1000 )\nVAR !VOLUME COLLECT ALL WITHIN W800N17000U0 TO W1400N13500U1200\nVAR !P COLLECT ALL PIPE EXCLUSIVE WITHIN VOLUME /PUMP1 1500\n>--- VOLUMEOPTION ---+--- HULL DESIGN ---.\n                     |                   |\n                     |                   |\n                     \u2018- HULL PRODUCTION -+--- ON  ---.\n                                         |           |\n                                         |           |\n                                         \u2018--- OFF ---+--->\nVAR !BRANCH COLLECT ALL BRANCH MEMBERS FOR /PIPE1 /PIPE2\nEXCLUDE BRAN 1 OF /PIPE2\nVAR !BENDS APPEND COLLECT ALL ELBOWS\nVAR !BENDS[99] COLLECT ALL ELBOWS\nENHANCE ALL WITH ( XLEN * YLEN * ZLEN GT 100 0 )\nENHANCE ALL BOX WITH ( XLEN * YLEN * ZLEN GT 100 0 )\nENHANCE ALL BOX WITH ( XLEN * YLEN * ZLEN GT 1000 ) FOR /*\nVAR IPIPECOMPS COLLECT ALL BRANCH MEMBERS\nIPIPECOMPS [1]  = '=20/302'\nIPIPECOMPS [2]  = '=20/303'\nIPIPECOMPS [3]  = '=20/304'\n       .\n       .\n       .\nIPIPECOMPS [354] = '=25/510'\nVAR !FLANGES COLLECT (ALL FLANGES) FROM IPIPECOMPS\nENHANCE ALL FROM !FLANGES\nENHANCE ALL FLANGES FROM IPIPECOMPS\nVAR !BENDS APPEND COLLECT ALL ELBOWS\nVAR !LIST[99] COLLECT ALL SLCY\nVAR !TUBING COLLECT (ALL TUBI) FOR /*\nvar !cln collect all EQUI\nvar !name evaluate (description) for all from !cln\nvar !name evaluate (description) for all EQUI\nCOLLECT ALL FROM TABLE NAME PREFIX '/B'\nCOLLECT ALL NOZZ WHERE (HEIGHT GT 100) FROM TABLE NAME PREFIX '/B'\nVAR !COLL COLLECT ALL FROM TABLE SPRE VALUE /RF300/100G\nVAR !COLL COLLECT ALL FLAN FROM TABLE SPRE VALUE /RF300/100G\nVAR !COLL COLLECT ALL WHERE (SPRE EQ /RF300/100G)\nVAR !COLL COLLECT ALL for /* FROM TABLE :MYTEXTATT VALUE  'fred'\nVAR !COLL COLLECT ALL for /* FROM TABLE :MYTEXTATT PREFIX  'fred'\nVAR !COLL COLLECT ALL FROM TABLE :MYATT VALUE 100\nVAR !COLL COLLECT ALL FROM TABLE :MYATT VALUE 100 TO 110\nVAR !COLL COLLECT ALL for /* FROM TABLE :MYREFATT VALUE /PIPE1\nVAR !COLL COLLECT ALL for /* FROM TABLE :MYREFATT VALUE /PIPE1\nQ ALL \u2026 for /*\nVAR !COLL COLLECT ALL BOX FOR DB CTBATEST/DESI\nVAR !COLL COLLECT ALL WHERE (SITE EQ /ATEST) FOR DB CTBATEST/DESI FROM TABLE SPRE\n      VALUE /RF300/100G\n   \nVAR !COLL COLLECT ALL FOR DB CTBATEST/DESI FROM TABLE NAME PREFIX '/B'\nA class of elements or element types.\nA logical expression to be satisfied at all selected elements.\nA physical volume in which all selected elements must lie.\nA point in the hierarchy below which all selected elements must lie.\nAll criteria (except for class) are optional.\nA class of elements or element types.\nA class of elements or element types.\nA logical expression to be satisfied at all selected elements.\nA logical expression to be satisfied at all selected elements.\nA physical volume in which all selected elements must lie.\nA physical volume in which all selected elements must lie.\nA point in the hierarchy below which all selected elements must lie.\nAll criteria (except for class) are optional.\nA point in the hierarchy below which all selected elements must lie.\nNote: This selection mechanism is a very powerful tool for searching whole databases and MDBs. However, if you're not careful the selection process could be very time consuming and tie up a lot of computer resource. Therefore, it is important that selection is performed as efficiently as possible. Plant tries to apply the above criteria so that the fastest condition is applied first and the most expensive is left to last.\n\n\n\n \n!Array\nClass\nALL\nALL FRMW\nALL BRANCH MEMBERS\nITEMS OF EQUI /VESS1\n/VESS1\n( /PIPE1 /PIPE2 )\n/PIPE1\n/PIPE2\n!PIPECOMPS\nMDB\nTRUE\nFALSE\nWITH\nWHERE\nVAR !LENGTHS COLLECT ALL WITH ( XLEN * YLEN 8 ZLEN GT 1000 )\nXLEN\nYLEN\nZLEN\n!LENGTHS\nvolume\nWITHIN\nVAR !VOLUME COLLECT ALL WITHIN W800N17000U0 TO W1400N13500U1200\n!VOLUME\nVAR !P COLLECT ALL PIPE EXCLUSIVE WITHIN VOLUME /PUMP1 1500\n/PUMP1\n!P\nEXCLUSIVE\nQ VOLUMEOPTION HULL DESIGN\nQ VOLUMEOPTION HULL PRODUCTION\nCommand Syntax\n>--- VOLUMEOPTION ---+--- HULL DESIGN ---.\n                     |                   |\n                     |                   |\n                     \u2018- HULL PRODUCTION -+--- ON  ---.\n                                         |           |\n                                         |           |\n                                         \u2018--- OFF ---+--->\nHierarchy\nFOR\nappend\nAPPEND\n!BENDS\noverwrite\nELBOW\n!BENDS\nALL\nALL FRMW\nALL BRANCH MEMBERS\nITEMS OF EQUI /VESS1\n( /PIPE1 /PIPE2 )\nALL WITH (XLEN GT 1000 )\nALL WITHIN W8000N17000U1000 TO W1400N13500U1200\nALL PIPE WITHIN VOLUME /PIPE1 1500\nNote\n:\n!TUBING[1]\n'IL TUB OF =20/302'\n!TUBING[2]\n'IL TUB OF =20/303'\nCATR\nCatalog reference\nPTRE\nPoint set reference\nGMRE\ngeometry set reference\nDTRE\nData set reference\nPSTR\nStructural Pline set reference\nGSTR\nStructural geometry set reference\nNGMR\nNegative geometry set reference\nPAIREF\nReference to a PAINT element\nSRFTRE\nReference to a SRFTRT element\nSLOREF\nPipe slope reference\nINSURE\nReference to a INSCMP element\nDOCREF\nCross reference DOCU elements\nCATR\nCatalog reference\nSPRE\nSprec reference\nLSTU\nTube spec\nISPE\nInsulation ref\nHSTU\nHead tube spec\nINRE\nInsulation reference\nHCREF\nReferences to head connected branches\nTCREF\nReferences to tail connected branches\nGOBREF\nHull Generating OBject REFerence\nCONNRE\nConnections on nodes\nPOSREF\nReference to point\nMDSYSF\nmodel reference\nACCREF\nAccess element reference\nHDBREF\nHull generic references\nHTPREF\nHull topological object model reference\nSCHLNK\nConnectivity link to schematic item references\nDESLNK\nConnectivity link to design model item references\nENGLNK\nConnectivity link to design model item references\nPRODRF\nreference from outfitting element to hull element\nSPBREF\nSpace boundary element reference\nSPINRE\nSpace inventory element reference\nINPRTR\nInside Paint Reference\nOUPRTR\nOutside Paint Reference\nASSTAR\nAssociation target reference\nMARKRF\nCable Mark points\nASSTMP\nAssembly template reference\nROUTND\nCable Preliminary route point\nSLOREF\nPipe slope reference"}
{"Headers": "Comparisons Across Sessions and Stamps", "Content": "Information is provided on changing the management, defining the comparison data, comparing the database changes and reverting elements.\n\n\n"}
{"Headers": "Change Management", "Content": "You can query the following aspects of the history of modifications to the current database:\nWhen and by whom an element or attribute was last modified.\nA complete history of the sessions in which an element or attribute has been modified.\nDetails of a given session.\nThe session number for a given date.\nWhen and by whom an element or attribute was last modified.\nWhen and by whom an element or attribute was last modified.\nA complete history of the sessions in which an element or attribute has been modified.\nA complete history of the sessions in which an element or attribute has been modified.\nDetails of a given session.\nDetails of a given session.\nThe session number for a given date.\nThe session number for a given date.\n\n\n"}
{"Headers": "Query the Last Modification to an Element or Attribute", "Content": "Lets you query details of the most recent change to a given element or attribute.\nQ LASTMOD\nGives date for last modification to current element.\nQ SESSMOD\nGives session number for last modification to current element.\nQ USERMOD\nGives name of user who last modified current element.\nQ LASTMOD HIER\nGives dates for last modifications to current element and its members.\nQ LASTMOD XLEN\nGives date for last modification to XLEN attribute of current element.\nExamples\nQ LASTMOD\nGives date for last modification to current element.\nQ SESSMOD\nGives session number for last modification to current element.\nQ USERMOD\nGives name of user who last modified current element.\nQ LASTMOD HIER\nGives dates for last modifications to current element and its members.\nQ LASTMOD XLEN\nGives date for last modification to XLEN attribute of current element.\nQ --+-- LASTMod --.\n    |             |\n    |-- SESSMod --|\n    |             |\n    \u2018-- USERMod --+--+-- <selatt> --.\n                  |  |              |\n                  |  \u2018--------------+-- HIERarchy --.\n                  |                 |               |\n                  |                 \u2018---------------+-->\n                  |\n                  \u2018-- attribute_name -->\n\n\n\nQ LASTMOD\nQ SESSMOD\nQ USERMOD\nQ LASTMOD HIER\nQ LASTMOD XLEN"}
{"Headers": "Query the Session History for an Element or Attribute", "Content": "Lets you query modification history for a given attribute; i.e. session numbers during which the attribute was modified.\nQ HISTORY DIAM\nGives all sessions in which DIAM attribute was modified.\nExamples\nQ HISTORY DIAM\nGives all sessions in which DIAM attribute was modified.\nQ HISTORY attribute_name\nNote:\nHISTORY is an array type pseudo-attribute, so that qualifying positions may be appended to query specific occurrences in the modification history. For example:\nQ HISTORY[2] DIAM\ngives second most recent session in which DIAM attribute was modified.\nNote:\nHistory records are restricted to a maximum of 120 sessions.\n\n\n\nQ HISTORY DIAM\nNote\n:\nQ HISTORY[2] DIAM\nNote\n:\nattribute_name"}
{"Headers": "Query Details of a Specific Session", "Content": "Lets you query details of any specific session. This is particularly useful to get details of sessions listed by a HISTORY command.\nQ SESSCOMM 58\nGives comment text associated with session 58\nQ SESSUSER 58\nGives name of user responsible for session 58.\nQ SESSDATE 58\nGives date and time at which session 58 was created.\nExamples\nQ SESSCOMM 58\nGives comment text associated with session 58\nQ SESSUSER 58\nGives name of user responsible for session 58.\nQ SESSDATE 58\nGives date and time at which session 58 was created.\nQ --+-- SESSComment --.\n    |                 |\n    |-- SESSUser -----|\n    |                 |\n    \u2018-- SESSDate -----+-- integer -->\nNote:\nAll session queries are for the current DB.\n\n\n\nQ SESSCOMM 58\nQ SESSUSER 58\nQ SESSDATE 58\nNote\n:"}
{"Headers": "Query Session Number for a Given Time", "Content": "Lets you query which session was current at a given time. (This is the inverse of the Q SESSDATE option described in Query Details of a Specific Session.)\nQ SESSION ON 12:00 22 August 1995 Q SESSION ON 9 /9 /96\n\nTime defaults to 23:59, so returns last session number on given date.\nwhere <date> is a standard syntax graph. Remember that <date> actually specifies a time (to the nearest minute), so take care if you use any defaults here.\nExamples\nQ SESSION ON 12:00 22 August 1995 Q SESSION ON 9 /9 /96\nTime defaults to 23:59, so returns last session number on given date.\nQ SESSION ON <date>\n\n\n\nQuery Details of a Specific Session\nQuery Details of a Specific Session"}
{"Headers": "Comparison Date", "Content": "It is only by comparing a drawing at two states or sessions that it is possible to determine what has changed. Using the current state of the drawing as one state we must then reference an earlier state in order to make the comparison. We do this by specifying a Comparison Date (COMPDATE), that is, the drawing state at a time that we wish to use as a baseline or datum.\n\n\n"}
{"Headers": "et the Comparison Date", "Content": "You can enter a comparison date, either for the entire Multiple Database (MDB) or an individual Database (DB). For individual DBs, you can also enter a specific session number and extract number.\nSETCOMPDATE 31 March 2002\nSETCOMPDATE STAMP /STAMP1\nSETCOMPDATE NOW\n\nCompares against the start values\nSETCOMPDATE FOR CTBATEST/DESI to session 99\nSETCOMPDATE FOR CTBATEST/DESI to EXTRACT\n\nCompares against the parent.\nSETCOMPDATE FOR CTBATEST/DESI to CTBATEST/MASTER\n\nCTBATEST/MASTER must be up the extract hierarchy.\nThe \u2018date\u2019 subgraph takes the keyword NOW This in effect sets the comparison date to the start of the session. This can be useful for querying the original value of an attribute.\nThe EXTRACT keyword sets the comparison to an extract DB. This extract DB must be one further up the extract hierarchy. If the EXTRACT keyword is used by itself, the comparison is set to the parent extract. Thus this enables you to find out what has been changed in this extract.\nExamples\nSETCOMPDATE 31 March 2002\nSETCOMPDATE STAMP /STAMP1\nSETCOMPDATE NOW\nCompares against the start values\nSETCOMPDATE FOR CTBATEST/DESI to session 99\nSETCOMPDATE FOR CTBATEST/DESI to EXTRACT\nCompares against the parent.\nSETCOMPDATE FOR CTBATEST/DESI to CTBATEST/MASTER\nCTBATEST/MASTER must be up the extract hierarchy.\n-SETCOMPDATE--|---date->\n              | --STAMP------name->\n              \u2018-FOR--DB--dbname--TO--|--date-->\n                                     |--Session -int-|--|-EXTRACT--|\u2014- int---->\n                                     \u2018---------------\u2018  \u2018-->       |-- Dbname->\n                                                                   \u2018---------->\n   \n\n\n\nSETCOMPDATE 31 March 2002\nSETCOMPDATE STAMP /STAMP1\nSETCOMPDATE NOW\nSETCOMPDATE FOR CTBATEST/DESI \nSETCOMPDATE FOR CTBATEST/DESI to EXTRACT\nSETCOMPDATE FOR CTBATEST/DESI to CTBATEST/MASTER"}
{"Headers": "Query the Comparison Date", "Content": "The query will return the comparison session number or extract number for a Database (DB).\nQ COMPDATE  EXTRACT FOR DB CTBATEST/DESI\nto get extract\nQ COMPDATE COMPDATE SESSION FOR DB CTBATEST/DESI\nto get session\nQ COMPDATE DATE\nto get date\nQ COMPDATE STAMP\nto get stamp\nThe query for the comparison date will only return a value if the COMPDATE was set using a single date. Otherwise it will return \u2018unset\u2019. Similarly querying a stamp is only valid if the COMPDATE was set using a stamp.\nExamples\nQ COMPDATE  EXTRACT FOR DB CTBATEST/DESI\nto get extract\nQ COMPDATE COMPDATE SESSION FOR DB CTBATEST/DESI\nto get session\nQ COMPDATE DATE\nto get date\nQ COMPDATE STAMP\nto get stamp\nQ ----------|-COMPDATE-|--SESSION--|--FOR---dbname--->\nVAR \u2011vname--\u2018          |\u2014EXTRACT---\u00b4\n                       |----DATE--------->\n                       \u2018----STAMP-------->\nNote:\nNote that if a stamp is used to set the comparison date, this will set the comparison session for each database within the stamp. It will also reset any comparison dates set previously.\n\n\n\nQ COMPDATE  EXTRACT FOR DB CTBATEST/DESI\nQ COMPDATE COMPDATE SESSION FOR DB CTBATEST/DESI\nQ COMPDATE DATE\nQ COMPDATE STAMP\nNote\n:"}
{"Headers": "MODIFIED Function", "Content": "For the more sophisticated queries relating to modifications, the MODIFIED function tells you if the given element has changed since the comparison date. This function is not implemented within PML2 expressions.\nTo return true if element has changed at all since the comparison date use:\nQ MODIFIED()\n\nIt will also return true if the element has been created since the comparison date.\nTo return true if POS or ORI have been modified since the comparison date use:\n\nQ MODIFIED(POS,ORI)\nTo return true if the position of P1 has changed use.\n\nQ MODIFIED(P1 POS)\n\n\nYou may follow each attribute name with the qualifying keywords below.\nTo check this element and members use:\n\nOFFSPRING\nTo check all elements for which this element represents the significant one use:\n\nSIGNIF\nTo check all elements for which this element represents the primary one use:\n\nPRIMARY\nTo check this element and everything below (descendants):\n\nDESCENDANTS\nYou can use the keywords below on their own to test for any attribute change. For example, to return true if any geometry for item or any descendants have changed use:\n\nQ MODIFIED(GEOM DESCENDANTS)\nTo return true if any element for which this element is primary, has changed use:\n\nQ MODIFIED(PRIMARY)\nYou may use the \u2018OF\u2019 syntax as for attributes. for example, to return true if /PIPE1 has been modified since the comparison date use:\n\nQ MODIFIED() OF /PIPE1\nYou may put the new functions anywhere within an AVEVA E3D Design PML1 expression. that means. after Q/Var and within collections. For example,\n\nQ (BUIL OR MODIFIED() OR ELECREC OF NEXT )\n                                              \u2018-->\nExamples\nTo return true if element has changed at all since the comparison date use:\n   Q MODIFIED()\n   It will also return true if the element has been created since the comparison date.\nTo return true if POS or ORI have been modified since the comparison date use:\nQ MODIFIED(POS,ORI)\nTo return true if the position of P1 has changed use.\nQ MODIFIED(P1 POS)\nYou may follow each attribute name with the qualifying keywords below.\nTo check this element and members use:\nOFFSPRING\nTo check all elements for which this element represents the significant one use:\nSIGNIF\nTo check all elements for which this element represents the primary one use:\nPRIMARY\nTo check this element and everything below (descendants):\nDESCENDANTS\nYou can use the keywords below on their own to test for any attribute change. For example, to return true if any geometry for item or any descendants have changed use:\nQ MODIFIED(GEOM DESCENDANTS)\nTo return true if any element for which this element is primary, has changed use:\nQ MODIFIED(PRIMARY)\nYou may use the \u2018OF\u2019 syntax as for attributes. for example, to return true if /PIPE1 has been modified since the comparison date use:\nQ MODIFIED() OF /PIPE1\nYou may put the new functions anywhere within an AVEVA E3D Design PML1 expression. that means. after Q/Var and within collections. For example,\nQ (BUIL OR MODIFIED() OR ELECREC OF NEXT )\n\n\n\nQ MODIFIED()\nQ MODIFIED(POS,ORI)\nQ MODIFIED(P1 POS)\nOFFSPRING\nSIGNIF\nPRIMARY\nDESCENDANTS\nQ MODIFIED(GEOM DESCENDANTS)\nQ MODIFIED(PRIMARY)\nQ MODIFIED() OF /PIPE1\nQ (BUIL OR MODIFIED() OR ELECREC OF NEXT )\n                                   .------------------------------------.\n                                  /                                      |\n>-MODIFIED-(-+--attname-------|--*--DESCENDANTS--+--+-comma--+--attname--\u00b4\n             |                   |               |  |\n             |--DESCENDANTS--.   |-- SIGNIFICANT-|  |\n             |               |   |               |  |\n             |--SIGNIFICANT--|   |--PRIMARY----- |  |\n             |               |   |               |  |\n             |--PRIMARY------|   |--MEMBERS------|  |\n             |               |   |               |  |\n             |--MEMBERS------|   \u2018---------------\u2018  |\n             |               |                      |\n             |               |                      |\n             |               |                      |\n             \u2018---------------+----------------------+--+--) ---OF --id-->\n                                                    |\n                                              \u2018-->"}
{"Headers": "CREATED Function", "Content": "Determine if an element has changed since the Comparison Date. The functionality of CREATED() is identical to using the pseudo attribute ELECREC.\nQ ( CREATED() )\n\n\n"}
{"Headers": "DELETED Function", "Content": "Determine if an element has been deleted since the Comparison Date. The functionality of DELETED() is identical to using the pseudo attribute ELEDELC.\nQ ( DELETED() )-\nreturns deleted since comparison date\nHowever if the element has been deleted then you cannot have navigated to it in the first place, hence DELETED() by itself will always be true. There are two ways around this.\nEither include the element\u2019s reference number, for example:\nQ (DELETED() of =15752/234 )\nOr use it as part of the 'old' syntax. e.g.:\nQ OLD (DELETED() of /VESS2)\n\nExamples\nQ ( DELETED() )-\nreturns deleted since comparison date\nHowever if the element has been deleted then you cannot have navigated to it in the first place, hence DELETED() by itself will always be true. There are two ways around this.\nEither include the element\u2019s reference number, for example:\nQ (DELETED() of =15752/234 )\nOr use it as part of the 'old' syntax. e.g.:\nQ OLD (DELETED() of /VESS2)\n\n\n\nQ ( DELETED() )-\nQ (DELETED() of =15752/234 )\nQ OLD (DELETED() of /VESS2)"}
{"Headers": "GEOM, CATTEXT, and CATMOD Special Attributes", "Content": "There are three new special attributes \u2018GEOM\u2019, \u2018CATTEXT\u2019, and CATMOD (previously called \u2018CATA\u2019).\nThe GEOM attribute returns true if any aspect of the evaluated geometry has changed.\nThe definition of evaluated geometry change includes:\nThis will return true if any part of the evaluated detail or material text has changed.\nSpecial attribute CATMOD will return true if any value in the catalog has changed, for example,\nThus it is possible that the geometry element has changed but the GEOM keyword returns false, for example, a User Defined Attributes (UDA) value may have changed, but this has no effect on the evaluated geometry.\nThe CATMOD keyword on the other hand will return true for any change.\nYou can use the CATMOD keyword on any element. It will return \u2018false\u2019 if the element does not have a SPREF or CATREF reference pointing into the catalog database. It will return \u2018true\u2019 if the element has a SPREF or CATREF attribute and either (a) this reference attribute has itself changed in value or (b) the catalog element pointed at, or any catalog element owned by or pointed at by this element, either directly or indirectly, has changed in any way.\nThe exception is that elements pointed at by UDA\u2019s are not compared, although the value of the UDA itself is checked. Thus if a reference valued UDA has been changed then this will count as a change, but if only the element pointed at has changed, then this will not count.\nAny dimension of a primitive has changed\nAny ppoint changes\nPos/ori change\nThe level information used to determine the geometry is set by the \u2018REPRE MASS\u2019 command. The \u2018REPRE MASS\u2019 command is also available in Isodraft.\nAny dimension of a primitive has changed\nAny dimension of a primitive has changed\nAny ppoint changes\nAny ppoint changes\nPos/ori change\nThe level information used to determine the geometry is set by the \u2018REPRE MASS\u2019 command. The \u2018REPRE MASS\u2019 command is also available in Isodraft.\nPos/ori change\nSpecification Reference (SPREF)\nChanges to a Specific Component (SPCO) element\nChanges to a Piping Component (COMP) element\nChanges to any Pointset Element (PTSE), 3D Geomset Element (GMSE)\nChanges to any dataset elements\nChanges in DTEXT, Material Text elements (MTEXT) elements\nNote that there is a subtle difference between CATMOD and the other two: the CATTEXT and GEOM keywords work on the evaluated values.\nSpecification Reference (SPREF)\nSpecification Reference (SPREF)\nChanges to a Specific Component (SPCO) element\nChanges to a Specific Component (SPCO) element\nChanges to a Piping Component (COMP) element\nChanges to a Piping Component (COMP) element\nChanges to any Pointset Element (PTSE), 3D Geomset Element (GMSE)\nChanges to any Pointset Element (PTSE), 3D Geomset Element (GMSE)\nChanges to any dataset elements\nChanges to any dataset elements\nChanges in DTEXT, Material Text elements (MTEXT) elements\nNote that there is a subtle difference between CATMOD and the other two: the CATTEXT and GEOM keywords work on the evaluated values.\nChanges in DTEXT, Material Text elements (MTEXT) elements\n\n\n\npointed at"}
{"Headers": "Query Any Attribute at the Comparison Date", "Content": "The \u2018OLD\u2019 syntax enables you to query any attribute at the comparison date.\nYou can use the syntax in front of any expression or attribute. The whole expression will then be evaluated at the comparison date. For example:\nIf a name is given, the name will be for the item at the comparison date, not now. Thus values of deleted items may be accessed. For example:\nWhere /OLDPIPE no longer exists.\nThe \u2018OLD\u2019 syntax may also be used after \u2018VAR\u2019. This includes collections. For example:\nThis would return a collection of all PIPES at the old version.\nIf the functions MODIFIED, CREATED, DELETED are used on the old version then the comparison is made with the current version.\nFor example to get a list of deleted pipes between the comparison date and now, then the following collection could be used. For example:\nThere is also a pseudo attribute, DSESS. that returns the session number when an element was deleted.That means having got the deleted PIPES from the previous query, we can now find out when they were deleted.\nQ OLD XLEN\nQ OLD REF OF /OLDPIPE\nVAR !PIPES OLD COLLECT ALL PIPES\nVAR !PIPES OLD COLLECT ALL PIPES WITH ( DELETED() )\n\n\n"}
{"Headers": "Compare Database Changes", "Content": "Information is provided on comparing database stats at different times and on model changes.\n\n\n"}
{"Headers": "Compare Database States at Different Times", "Content": "You can compare details of your current database settings with the corresponding settings at a specified earlier time and generate a report listing all differences. The types of change reported include:\nDIFFERENCE SINCE\nLets you report all changes to one or more specified database elements since an earlier version of that database. The output is in the form of a report listing all elements and attributes which have changed, with their old and new values. The report can be sent to a file by using the ALPHA FILE or ALPHA LOG commands.\nDIFFERENCE ALL BRANCH FOR /ATEST SINCE 21 JANUARY\nDIFF CE SINCE 10:00\nAssumes current day.\nDIFF /ZONE\nCompares current settings with those at your last SAVEWORK command.\nDIFF SITE SINCE SESSION 66\nCompares current settings with those at the end of session 66 of the current database.\nExamples\nDIFFERENCE ALL BRANCH FOR /ATEST SINCE 21 JANUARY\nDIFF CE SINCE 10:00\nAssumes current day.\nDIFF /ZONE\nCompares current settings with those at your last SAVEWORK command.\nDIFF SITE SINCE SESSION 66\nCompares current settings with those at the end of session 66 of the current database.\n>- DIFFerence <selele> SINCE -+- <date/time> -+-----------------------.\n                              |               |                       |\n                              |- LATEST ------|                       | \n                              |               |                       |\n                              |--SESSION nn --|                       |\n                              |               |                       |\n                              \u2018---------------+- EXTRACT -+- extname -|\n                                                          |           |\n                                                          \u2018- extno ---+->\n   \nCreation and deletion of elements.\nChanges to the attribute settings of elements.\nChanges in the list order for BRANCH, POGON, DRAWI and BOUND elements.\nCreation and deletion of elements.\nCreation and deletion of elements.\nChanges to the attribute settings of elements.\nChanges to the attribute settings of elements.\nChanges in the list order for BRANCH, POGON, DRAWI and BOUND elements.\nChanges in the list order for BRANCH, POGON, DRAWI and BOUND elements.\nNote:\nThe database states are compared between SAVEWORK operations. For example, if you last saved your design changes at 9:30 and ask for a comparison since 10:00, the current settings will be compared with those at 9:30.\n\n\n\nNote\n:\nDIFFERENCE ALL BRANCH FOR /ATEST SINCE 21 JANUARY\nDIFF CE SINCE 10:00\nDIFF /ZONE\nDIFF SITE SINCE SESSION 66"}
{"Headers": "Model Changes", "Content": "Model Changes provides a mechanism for exploring change and highlighting changed elements in the 3D Graphical View. On the Manage tab, in the History group, click Model Changes to display the Model Changes window.\n\nThe Model Changes window has two vertically split panes. The top pane contains a Model Explorer while the lower split contains the following tabs.\nThe Element History and Key panes are for information only while the Model Timeline and Stamps panes allow the selection of a session or stamp upon which to base the display of changes in the explorer pane, and optional highlighting of changed elements in the 3D graphical view. Once a session or stamp is selected changes can be highlighted by Refresh.\nModel Timeline\nClicking Model Timeline displays every session for every Design database in the current MDB, ordered chronologically.\n\nStamps\nClicking Stamps lists details of every stamp that records session numbers for all of the Design databases in the Multiple Database (MDB).\n\nElement History\nClicking Element History lists the details of every database session in which the selected Current Element (CE) has changed.\n\nKey\nClicking Key displays a static tree control with images, colour and text explaining explorer annotations used to display changes in the explorer control.\n\nEither of two modes of change reporting can be selected from the drop-down menu according to the current selection.\n\nAll Changes Since displays only changes that have been made in all databases in the MDB between, but not including, the selected session or stamp, and the current state of the model but does include any unsaved changes.\nOnly Changes At displays only the changes that were made when the highlighted session was created which, may have been a savework or as the result of an extract operation, such as a flush or refresh, as indicated by the Reason column in the Model Timeline table.\nNote Highlighting in the explorer pane and in the 3D graphical view is always with reference to the current state of the model; it is possible that no changes from a previous session will be visible, for example if all changes were made to elements that have since been deleted.\nWhen Refresh is clicked and the change analysis operation is complete the explorer tree is updated with annotations which highlight the changed elements in detail.\nClicking Highlight has an immediate effect on all 3D graphical views if changes are currently displayed in the explorer tree. Any changed elements that have graphical representation and are in the drawlist for any active view are highlighted in colour. This uses the same customizable colour used by the Highlight element function available via right-click menu in the standard Model Explorer. Unchecking Highlight returns the graphical display to normal coloring.\nAll panes of the Model Changes are updated and explorer annotations and 3D graphical highlighting are reset in the following circumstances:\nFollowing any of these operations Refresh must be clicked again in order to update the change highlighting.\n.\n\n\n\n\n\n\n.\n.\nfurther element changes\nsavework, getwork, and refresh\nuser or MDB switch\nfurther element changes\nfurther element changes\nsavework, getwork, and refresh\nsavework, getwork, and refresh\nuser or MDB switch\nuser or MDB switch\nNote: T\nhe previous DB Changes appware is now available on the Manage tab, in the History group, clicking DB Listing.\nNote:\nFor large models this change analysis can take some time.\n\n\n\nModel Changes\nManage\nHistory\nModel Changes\nModel Changes\nNote\n:\nDB Changes\nManage\nHistory\nDB Listing\nModel Changes\n\n\n\n\nElement History\nKey\nModel Timeline\nStamps\nRefresh\nModel Timeline\nModel Timeline\nStamps\nStamps\nElement History\nElement History\nKey\nKey\nAll Changes Since\nNote\n:\nOnly Changes At\nRefresh\nHighlight\nHighlight element\nHighlight\nModel Changes\nRefresh"}
{"Headers": "Revert Elements", "Content": "Revert allows you to directly Revert an element or hierarchy of elements to a previous state.\nWhere the <comparison> syntax is similar to that following the SINCE keyword in both of the existing DIFFERENCE and OUTPUT CHANGES commands.\nIf the BEFORE clause is used the elements will be reverted to the state they had before the session that is selected by the historical specification.\nExamples of the Revert Command:\nThe revert command makes sure that every element creation, include, reorder and deletion, and every attribute change is allowed before proceeding. If any of these tests fail, for example due to legality checks, read-only databases or Data Access Controls (DACs), then the entire revert operation is cancelled and the following error is generated.\nIn this case a series of warning messages is written to the console indicating the causes of the error, for example:\nElement locks do not prevent a revert operation if those elements were unlocked in the previous state.\n>- REVert -+- ELEment ---.\n           |             |\n           `- HIERarchy -+- <selele> -+- AT -----.\n                                      |          |\n                                      `- BEFore -+- <comparison> ->\n-->-+- <date/time> -+-----------------------.\n    |               |                       |\n    |- LATEST ------|                       |\n    |               |                       |\n    |---------------+- EXTRACT -+-----------|\n    |                           |           |\n    |                           |- extno ---+\n    |                           |           |\n    |                           '- extname -+\n    |                                       |\n     `- STAMP - <name> ---------------------+->\nREVERT HIER /EQUIP AT LATEST\nREVERT HIER /EQUIP BEFORE LATEST\nREVERT ELE /E1301 AT 20:16 26 / 3 / 2010\nREVERT HIER /PIPES AT STAMP /StampMilestone7\nREVERT HIER CE AT EXTRACT\n(43,615) Cannot Revert elements. No changes have been made.\nDAC prevents deletion of element /DELETE_UDET_B\nDAC prevents creation of element =15752/1363\nDAC prevents modification of attribute Built on element /MODIFY_B_VESS1\nNote:\nThis command is not directly related to the REVERT <database name> command available in the Admin module. This command allows an entire database to be reverted to the state it had at a previous session.\n\n\n\n>- REVert -+- ELEment ---.\n           |             |\n           `- HIERarchy -+- <selele> -+- AT -----.\n                                      |          |\n                                      `- BEFore -+- <comparison> ->\n<comparison>\nSINCE\nDIFFERENCE\nOUTPUT CHANGES\n-->-+- <date/time> -+-----------------------.\n    |               |                       |\n    |- LATEST ------|                       |\n    |               |                       |\n    |---------------+- EXTRACT -+-----------|\n    |                           |           |\n    |                           |- extno ---+\n    |                           |           |\n    |                           '- extname -+\n    |                                       |\n     `- STAMP - <name> ---------------------+->\nBEFORE\n/EQUIP\n/EQUIP\n/E1301\n/PIPES\n(43,615) Cannot Revert elements. No changes have been made.\nDAC prevents deletion of element /DELETE_UDET_B\nDAC prevents creation of element =15752/1363\nDAC prevents modification of attribute Built on element /MODIFY_B_VESS1\nNote\n:\nREVERT <database name>"}
{"Headers": "Project Queries", "Content": "Information is provided on the multiple database mode, on how to check current user status and system status and on how to list project information and how query multiple database.\n\n\n"}
{"Headers": "MDB Mode", "Content": "The MDB command puts you into MDB Mode, where you can use a limited number of Monitor commands. This lets you change the current multiple database during a session without having to leave the Module and enter Monitor.\nWhen you enter MDB mode, you can either update the current Multiple Database (MDB) to save your design changes, or ignore any changes made since your last SAVEWORK command, by specifying UPDATE or NOUPDATE.\nWhen you are in MDB mode, you can give the following commands, which are the same as the corresponding Monitor commands. Refer to for further information.\nMDB UPDATE\nSave design changes and enter MDB Mode.\nMDB NOUPDATE\nEnter MDB Mode without saving design changes.\nEXCHANGE\nDEFER\nCURRENT\nAlter the databases in the current list of the current MDB\nPROTECT\nTemporarily alters your access rights to specified databases.\nUSER username\nChanges the current user\nPROJECT code\nChanges the current project\nLIST\nAllows you to query:\nUsers, including the number of active users,\nTeams including the set (current) Team,\nDatabases, including copied Databases,\nMDBs, Macros and Variables\n/PIPING\nChange to MDB /PIPING.\n/PIPING READONLY\nChange to MDB /PIPING in read-only mode.\nEXIT\nReturn to MODEL Mode.\nExamples\nMDB UPDATE\nSave design changes and enter MDB Mode.\nMDB NOUPDATE\nEnter MDB Mode without saving design changes.\nEXCHANGE\nDEFER\nCURRENT\nAlter the databases in the current list of the current MDB\nPROTECT\nTemporarily alters your access rights to specified databases.\nUSER username\nChanges the current user\nPROJECT code\nChanges the current project\nLIST\nAllows you to query:\nUsers, including the number of active users,\nTeams including the set (current) Team,\nDatabases, including copied Databases,\nMDBs, Macros and Variables\n/PIPING\nChange to MDB /PIPING.\n/PIPING READONLY\nChange to MDB /PIPING in read-only mode.\nEXIT\nReturn to MODEL Mode.\n>-- MDB --+-- UPdate ----.\n          |              |\n          \u2018-- NOUPdate --+-->\n\n\n\nMDB Mode\n\n\nMDB UPDATE\nMDB NOUPDATE\nEXCHANGE\nDEFER\nCURRENT\nPROTECT\nUSER username\nPROJECT code\nLIST\n/PIPING\n/PIPING READONLY\nEXIT"}
{"Headers": "Check the Current User Status", "Content": "Gives you information about your current status as a user and about the Databases (DBs) to which you have access.\nA typical response to the STATUS command could be:\nProject: XYZ\nUser:    CSI (758)\nTeams:   B\nMDB:     /DESIGN\nCurrent DBS:\n  1  PIPING/SITE                       RW\n  2  MASTER/CATLOG                     R\nDeferred DBS:\n  3  STRUCT/STEEL\nThis indicates that the designer has identified himself as being AVEVA E3D Design user CSI, that he is logged in to the computer as user 758, that he is a member of team B, that he is accessing Project XYZ, and that he has selected an Multiple Database (MDB) called /MODEL.\nIf INFO is specified then a line of text explains the reason for the database access mode differing from expectation. For example:\nExample\nA typical response to the STATUS command could be:\nProject: XYZ\nUser:    CSI (758)\nTeams:   B\nMDB:     /DESIGN\nCurrent DBS:\n  1  PIPING/SITE                       RW\n  2  MASTER/CATLOG                     R\nDeferred DBS:\n  3  STRUCT/STEEL\n>-- STATus -+---------------->\n            |\n            \u2018- INFOrmation -->\n   \nnot integrated\ncurrent product has limited access\ndatabase not allocated to this location\nnot integrated\nnot integrated\ncurrent product has limited access\ncurrent product has limited access\ndatabase not allocated to this location\ndatabase not allocated to this location\n\n\n\nProject: XYZ\nUser:    CSI (758)\nTeams:   B\nMDB:     /DESIGN\nCurrent DBS:\n  1  PIPING/SITE                       RW\n  2  MASTER/CATLOG                     R\nDeferred DBS:\n  3  STRUCT/STEEL"}
{"Headers": "Check the Current System Status", "Content": "The SYstem STATus command gives you information about the current active status of the project in which you are working. It lists all users who are currently accessing the project, the modules and databases which they are using, and whether they are examining (Read-only status) or modifying (Read/Write status) the database. It also gives the workstation identifier for each user.\nA typical response to the SYSTAT command could be:\nPROJECT  XYZ\n==============\n\nUSER SYSTEM (57b)\nMODULE ADMIN\nMDB ** UNSET **\n\nUSER HHJ (752)\nMODULE DESIGN\nMDB /STEEL\n\nDB              MODE\nMASTER/AREA-A   R\nMASTER/AREA-B   R\nSTRUC/AREA-C    RW\nThis shows that two users are currently logged in and are using AVEVA E3D Design for work on Project XYZ. The Project Coordinator is using Admin but is not accessing any databases. User 752 is using Model. He is accessing the Multiple Database (MDB) named /STEEL, whose constituent Databases (DBs) are as listed. He has Read-only status for the DBs owned by the MASTER (System) team and Read/Write access to the DB STRUC/AREA-C.\nExample\nA typical response to the SYSTAT command could be:\nPROJECT  XYZ\n==============\n\nUSER SYSTEM (57b)\nMODULE ADMIN\nMDB ** UNSET **\n\nUSER HHJ (752)\nMODULE DESIGN\nMDB /STEEL\n\nDB              MODE\nMASTER/AREA-A   R\nMASTER/AREA-B   R\nSTRUC/AREA-C    RW\n>-- SYStat -->\n\n\n\nSY\nSTAT\nPROJECT  XYZ\n==============\nUSER SYSTEM (57b)\nMODULE ADMIN\nMDB ** UNSET **\nUSER HHJ (752)\nMODULE DESIGN\nMDB /STEEL\nDB              MODE\nMASTER/AREA-A   R\nMASTER/AREA-B   R\nSTRUC/AREA-C    RW"}
{"Headers": "List Project Information", "Content": "Lets you list most of the project information held in the System Database, with the exception of confidential details such as other users\u2019 passwords, which can only be listed by the System Administrator in AVEVA E3D Design Admin.\nA typical response to the LIST MDB command could be:\n List of MDBS for project XXX\n==============================\nMDB:     /DESIGN\nCurrent DBS:\n  1  PIPING/AREA-A                     DESI Exclusive\n  2  PIPING/AREA-C                     DESI Update\n  3  MASTER/AREA-D                     DESI Exclusive\n Deferred DBS:\n  4  PIPING/AREA-B                     DESI Exclusive\n  5  MASTER/AREA-E                     DESI Update\n\nMDB:/STEEL\nCurrent DBS:\n  1  MASTER/AREA-A                     DESI Exclusive\n  2  MASTER/AREA-B                     DESI Exclusive\n  3  STRUCT/AREA-C                     DESI Exclusive\nDeferred DBS:\n**NONE**\n\nMDB:     /ANSI\nCurrent DBS:\n  1  CATAL/AREA-E                      CATA Update\nDeferred DBS:\n**NONE**\nA typical response to the LIST USERS command could be:\n List of USERS for project ZZZ\n===============================\nSYSTEM   (FREE)\nTEAMS :MASTER   STAB\n\nZ        (FREE)\nTEAMS :***NONE**\n\nGEN      (GENERAL)\nTEAMS :TEST\nThe information generated by the LIST command can either be displayed on screen or sent to a file.\nExamples\nA typical response to the LIST MDB command could be:\n List of MDBS for project XXX\n==============================\nMDB:     /DESIGN\nCurrent DBS:\n  1  PIPING/AREA-A                     DESI Exclusive\n  2  PIPING/AREA-C                     DESI Update\n  3  MASTER/AREA-D                     DESI Exclusive\n Deferred DBS:\n  4  PIPING/AREA-B                     DESI Exclusive\n  5  MASTER/AREA-E                     DESI Update\n\nMDB:/STEEL\nCurrent DBS:\n  1  MASTER/AREA-A                     DESI Exclusive\n  2  MASTER/AREA-B                     DESI Exclusive\n  3  STRUCT/AREA-C                     DESI Exclusive\nDeferred DBS:\n**NONE**\n\nMDB:     /ANSI\nCurrent DBS:\n  1  CATAL/AREA-E                      CATA Update\nDeferred DBS:\n**NONE**\nA typical response to the LIST USERS command could be:\n List of USERS for project ZZZ\n===============================\nSYSTEM   (FREE)\nTEAMS :MASTER   STAB\n\nZ        (FREE)\nTEAMS :***NONE**\n\nGEN      (GENERAL)\nTEAMS :TEST\n             .----<----.\n            /          |\n>-- LIst --*-- USers --|\n           |           |\n           |-- MDBs ---|\n           |           |\n           |-- DBs ----|\n           |           |\n           |-- TEams --\u2019\n           |\n           \u2018-------------->\n\n\n\n List of MDBS for project XXX\n==============================\nMDB:     /DESIGN\nCurrent DBS:\n  1  PIPING/AREA-A                     DESI Exclusive\n  2  PIPING/AREA-C                     DESI Update\n  3  MASTER/AREA-D                     DESI Exclusive\n Deferred DBS:\n  4  PIPING/AREA-B                     DESI Exclusive\n  5  MASTER/AREA-E                     DESI Update\n\nMDB:/STEEL\nCurrent DBS:\n  1  MASTER/AREA-A                     DESI Exclusive\n  2  MASTER/AREA-B                     DESI Exclusive\n  3  STRUCT/AREA-C                     DESI Exclusive\nDeferred DBS:\n**NONE**\n\nMDB:     /ANSI\nCurrent DBS:\n  1  CATAL/AREA-E                      CATA Update\nDeferred DBS:\n**NONE**\n List of USERS for project ZZZ\n===============================\nSYSTEM   (FREE)\nTEAMS :MASTER   STAB\n\nZ        (FREE)\nTEAMS :***NONE**\n\nGEN      (GENERAL)\nTEAMS :TEST"}
{"Headers": "Query MDB Information", "Content": "Lets you query details of the current Multiple Database (MDB). This is a supplementary querying facility to the LIST command (List Project Information). It allows specific information about features of the project configuration to be interrogated.\n>-- Query --+-- USer      ---.\n            |                |\n            |-- USer word ---|\n            |                |\n            |-- TEam word ---|\n            |                |\n            |-- DB dbname ---|\n            |                |\n            \u2018-- MDB name ----+-->\n   \n\n\n\nList Project Information\nList Project Information"}
{"Headers": "Query Individual Database Information", "Content": "Lets you query details of the current DB for a given element.\nQ DBNAME\nGives name of current DB\nQ DBTYPE\nGives type of current DB\nQ DBFNUMBER\nGives file number for current DB\nQ DBFILE\nGives pathname for current DB file\nExamples\nQ DBNAME\nGives name of current DB\nQ DBTYPE\nGives type of current DB\nQ DBFNUMBER\nGives file number for current DB\nQ DBFILE\nGives pathname for current DB file\n>-- Query --+-- DBNAme -----.\n            |               |\n            |-- DBTYpe -----|\n            |               |\n            |-- DBFNumber --|\n            |               |\n            \u2018-- DBFIle -----+-->\n\n\n\nQ DBNAME\nQ DBTYPE\nQ DBFNUMBER\nQ DBFILE"}
{"Headers": "Link Documents", "Content": "The link documents mechanisms provide the ability to link external and internal documents to database objects. Every element in the database can be associated with a resource that is either another database element for example a drawing, or an external document such as a file, or a web page. External documents are not stored in the Dabacon database.\n\n\n"}
{"Headers": "Overview", "Content": "Each document or other resource, either external or internal, that can be linked to a database element is represented in the database as Link Descriptor. The Link Descriptor's main role is to carry information about the document it describes and a Uniform Resource Locator (URL).\nIt is possible for any other elements in the database to reference these Link Descriptors through a two-way mechanism enabling users to find all elements that reference a particular Link Descriptor and the opposite, find all documents referenced by an element.\nIt is also possible to assign classification information to each Link Descriptor. The classification information provides the facility of assigning multiple class information to a Link Descriptor so that a search for all elements that have references to documents with specific classification assigned can be made. For example, a search can be made for all Link Descriptors classified as \"Installation\"-class document or all pumps that do not reference any \"Certificate\" and \"Security\"-class documents.\nThe following figure shows a schematic overview of the possible linkage to external documents and internal drawings.\n\n\n\n"}
{"Headers": "Data Structures", "Content": "There are several element types used for organizing links and storing link information. All kinds of elements may be created using standard AVEVA E3D Design command syntax.\n\n\n"}
{"Headers": "Link World (LINKWL)", "Content": "All elements related to links are stored under Link World elements. To use links you have to create at least one Link World. It can store Link Folders, Link Classes and Link Descriptors which are covered in the following sections.\nIt is possible to assign Link Descriptors to elements in other databases. It is therefore recommended that LINKWL elements are created in a MODEL database of its own to which all relevant teams have read and write access.\n\n\n"}
{"Headers": "Link Folder (LNFOLD)", "Content": "Under Link Worlds it is possible to organize all elements into a tree structure. You can create Link Folders that can contain more Link Folders or Link Classes and Link Descriptors. This way it is possible to freely configure the hierarchy.\n\n\n"}
{"Headers": "Link Descriptor (LNDESC)", "Content": "A Link Descriptor (LNDESC) element holds a link to documents and external resources. Both external documents and draft drawing elements can be referenced using a LNDESC.\nA Link Descriptor has the following attributes:\nThe following pseudo attributes may be queried:\nNAME - user-defined name of the LNDESC element.\nDESC - description of the element.\nLNKURL - a string storing raw Uniform Resource Locator of the linked document.\nNAME - user-defined name of the LNDESC element.\nNAME - user-defined name of the LNDESC element.\nDESC - description of the element.\nDESC - description of the element.\nLNKURL - a string storing raw Uniform Resource Locator of the linked document.\nLNKURL - a string storing raw Uniform Resource Locator of the linked document.\nLNKREF - if the Link Descriptor holds a reference to an internal database element,that means,. the LNKURL stores a \"dabref://\u2026\" link, this attribute returns a reference to a database element linked through this descriptor. Otherwise, LNKREF returns a null reference. It is also possible to store an internal reference through this attribute.\nURL - this attribute returns merely the value of LNKURL but its main purpose is that you can assign either an external URL or a string with reference number of a Dabacon element, which is automatically recognised and stored as an internal link.\nLNKCLS - list of Link Class elements that classify this Link Descriptor.\nLNKELE - list of elements that have this Link Descriptor assigned.\nLNKREF - if the Link Descriptor holds a reference to an internal database element,that means,. the LNKURL stores a \"dabref://\u2026\" link, this attribute returns a reference to a database element linked through this descriptor. Otherwise, LNKREF returns a null reference. It is also possible to store an internal reference through this attribute.\nLNKREF - if the Link Descriptor holds a reference to an internal database element,that means,. the LNKURL stores a \"dabref://\u2026\" link, this attribute returns a reference to a database element linked through this descriptor. Otherwise, LNKREF returns a null reference. It is also possible to store an internal reference through this attribute.\nURL - this attribute returns merely the value of LNKURL but its main purpose is that you can assign either an external URL or a string with reference number of a Dabacon element, which is automatically recognised and stored as an internal link.\nURL - this attribute returns merely the value of LNKURL but its main purpose is that you can assign either an external URL or a string with reference number of a Dabacon element, which is automatically recognised and stored as an internal link.\nLNKCLS - list of Link Class elements that classify this Link Descriptor.\nLNKCLS - list of Link Class elements that classify this Link Descriptor.\nLNKELE - list of elements that have this Link Descriptor assigned.\nLNKELE - list of elements that have this Link Descriptor assigned.\n\n\n"}
{"Headers": "Link Class (LNCLAS)", "Content": "Classification of documents is possible through use of Link Classes (LNCLAS). Each Link Descriptor (LNDESC) may be classified by multiple classes; in the diagram below see how each LNDESC is associated with more than one LNCLAS. A single Link Class may classify multiple Link Descriptors; in the diagram LNCLASI is associated with all three LNDESC.\n\nA Link Class has the following attributes:\nThere is also a pseudo attribute available named LNKDOC that returns a list of LNDESC elements that are classified by this LNCLAS.\nNAME - user-defined name of the LNCLAS element.\nDESC - description of the element.\nNAME - user-defined name of the LNCLAS element.\nNAME - user-defined name of the LNCLAS element.\nDESC - description of the element.\nDESC - description of the element.\n\n\n"}
{"Headers": "Command Window", "Content": "Link Documents functionality is available through the command line. Standard AVEVA E3D Design command syntax can be used to create, delete or modify database elements and to query and set their attributes including pseudo attributes.\nThe following sections describe the typical scenarios connected with links including examples.\n\n\n"}
{"Headers": "Configuring Links Hierarchy", "Content": "Before it is possible to link documents to database elements it is necessary to create at least one Link World (LINKWL). You can organize Link Descriptors and Link Classes into a hierarchy of folders. An example hierarchy is shown below.\n\n\n\n"}
{"Headers": "Link a Document to a Database Element", "Content": "To add a link between an element and a document (or an external resource):\nYou can also link a document to an element using an existing Link Descriptor, because many database element can be linked to the same document:\nThe DLADD command can be used to add links from a document to one or more other elements. The command syntax is:\nIt is possible to create an association both by adding a link from a Link Descriptor to a database element and by adding a link from a database element to a Link Descriptor. Examples are given below.\nIf current element is a Hull Panel Element (HPAN) named /PANEL1 the following command assigns Link Descriptors /MYDOC1 and /MYDOC2 to /PANEL1:\nIf current element is a Link Descriptor (LNDESC) named /MYDOC1 the following command assigns this Link Descriptor to /PANEL1 and /PUMP1:\nThe whole process of linking a document to /PUMP1 might look like this:\n>--- DLADD -------*-- <selatt> -----+------>\n> DLADD /MYDOC1 /MYDOC2\n> DLADD /PANEL1 /PUMP1\n> NEW LNDESC /MYDOC\n> URL 'http://aveva.com/all_about_vm12_link_documents.pdf'\n> DLADD /PUMP1\n\n\n"}
{"Headers": "Unlinking a Document from a Database Element", "Content": "Once there is an association between an element and a Link Descriptor you can break the assignment by using the DLREMOVE command. The command syntax is:\nIt is possible to remove an association both by removing a link from a Link Descriptor to a database element or by removing a link from a database element to a Link Descriptor. For example:\nIf current element is a Hull Panel Element (HPAN) named /PANEL1 the following command removes link to document described by /MYDOC1 from /PANEL1:\nIf current element is a Link Descriptor (LNDESC) named /MYDOC1 the following command removes link to document described by this Link Descriptor to /PUMP1:\nThe following command removes all Link Descriptor associations from the current element:\nThe following command removes the first five Link Descriptor associations from the current element:\nIf the current element is a Link Descriptor you can retrieve or set the URL stored in this descriptor. To link to an external resource you should directly set the URL:\nThe Link Descriptor has a pseudo attribute LNKREF that returns a database reference if the descriptor links internally to Dabacon. If you set the URL to an external resource LNKREF returns a null reference:\nYou can use the LNKREF to set link to an internal database reference for example, a drawing:\n                    ----------------+\n                   /                |\n>--- DLREMove ----*-- <selatt> -----+------>\n> DLREM /MYDOC1\n> DLREM /PUMP1\n> DLREM LINks\n> DLREM LIN 1 TO 5\n> URL 'file:///Docsys/MyDocument.doc'\n> QUERY LNKREF\n> LNKREF /DRAWING1\n> QUERY LNKREF\nUrl DBRef / DRAWING1\n\n\n"}
{"Headers": "Classify a Link", "Content": "Each Link Descriptor can have a number of Link Classes assigned. To classify a link:\nIf current element is a Link Descriptor (LNDESC) named /MYDOC1 the following command classifies this Link Descriptor as a /MYCLASS1 and /MYCLASS2 document:\nIf current element is a Link Class (LNCLAS) named /MYCLASS1 the following command classifies a Link Descriptor named /MYDOC1 as a /MYCLASS1 document:\n> DLADD /MYCLASS1 /MYCLASS2\n> DLADD /MYDOC1\n\n\n"}
{"Headers": "Unclassify a Link", "Content": "To remove classification information from a Link Descriptor you can use the DLREMOVE command.\nIf current element is a Link Descriptor (LNDESC) named /MYDOC1 the following command removes /MYCLASS1 classification from the /MYDOC1 Link Descriptor:\nIf current element is a Link Class (LNCLAS) named /MYCLASS1 the following command removes /MYCLASS1 classification from the /MYDOC1 Link Descriptor:\nThe following command removes all Link Descriptor associations from the current Link Class:\nThe following command removes all classification information from the current Link Descriptor:\n> DLREM /MYCLASS1\n> DLREM /MYDOC1\n> DLREM LINks\n> DLREM CLAsses\n\n\n"}
{"Headers": "Related Pseudo Attributes", "Content": "A number of pseudo attributes allow retrieval of information on the relation between Link Descriptors (LNDESC), Link Classes (LNCLAS) and model elements:\n\n\n"}
{"Headers": "Links Addin", "Content": "The Link Addin is a customizable user form which simplifies much of the process of creating links.\nThe Links Addin uses the notion of link categories to treat different types of links differently.\nBy default the Links Addin comes with predefined link categories for: E-mail address, Web page, Existing file and Drawing. However, it gives the possibility to extend this set of link types and to create additional categories. For example, one could add a category that would accumulate links to documents or links to FTP resources if needed.\nWhen creating a link the Links Addin gives the possibility to choose a link category and set options for the new link. An example link creation dialog is shown below.\n\nEach link category has a name and an icon. The dialog provides the possibility to input the Name and Description for the link, depending on the type of link being created the form will prompt for an appropriate resource to link to. For example when created a link to a web page you are prompted to enter a valid Address such as http://www.aveva.com.\nClicking OK will open a new window prompting for a container for the new link.\n\nOn its first use, the \u2018Select destination container\u2019 window will appear empty. This is because a Link World and Link Folder hierarchy has not been created.\nAs discussed in the section \u2018Configuring Link Hierarchy\u2019 at least one Link World should be created.\nIn the \u2018Select destination container\u2019 window right click to create a \u2018New world\u2019. A \u2018New folder\u2019 must also be created below a world.\n\nClick OK for the link to be created in the database hierarchy.\nOnce a link has been created it is possible to view the link attributes using the link list sub form, launched from the \u2018Show Link\u2019 button from the toolbar. This form displays the element the Link has been assigned to, the Link Name, Category, Description and Link URL.\n\nThe Link Addin can be customized through a set of API\u2019s, refer to for further information.\n\n\n\nOK\nOK\n"}
{"Headers": "Inter-DB Connection Macros", "Content": "Access to a DB is usually controlled in such a way that only one user can modify the content of that Database (DB) at any one time; that is, only one user can have Write access to the DB. Other users may have simultaneous Read access, depending how access rights have been set up in the Admin module.\nIn a multi-disciplinary project, in which different teams of users work on different aspects of the design, an individual user will usually have Read/Write access to the DBs controlled by their own team and Read-only access to DBs controlled by other teams. This works well until a user needs to connect an item in their team\u2019s DB to an item in another team\u2019s DB; for example, a member of the Piping team may wish to connect a Branch in a Piping DB to a Nozzle in an Equipment DB (to which they have Read-only access). In such a case, the design changes needed in the Equipment DB are stored in a \u2018buffer\u2019 file known as an inter-DB connection macro. Only when this macro is run by a member of the Equipment team, with Write access to the Equipment DB, are the changes implemented.\nThe sequence of events which would occur is illustrated in the following example.\nAssume that Project ABC has separate Piping and Equipment design teams. Assume that User P has Read/Write access to a Piping DB and Read-only access to an Equipment DB, while User E has Read/Write access to the Equipment DB and Read-only access to the Piping DB.\nUser P wishes to connect a Branch Tail in their Piping DB to a Nozzle in User E\u2019s Equipment DB; that is, they wish to set the Branch\u2019s TREF in their Piping DB to point to the CREF of the Nozzle (which they can do) and to set the CREF of the Nozzle to point to the Tail Reference (TREF) of their Branch (which they can not do), thus:\n\n$M /%ABCMAC%/abc001.mac\nDELETE MACRO 1\nUser P sets the TREF of their Branch to point to the CREF of the Nozzle in the Equipment DB.\nWhen User P tries to set the Nozzle\u2019s CREF, they receive a message telling them that they are trying to connect to a read-only DB and that an inter-DB connection macro is being created automatically. This macro, which stores the commands needed to set the CREF, is given a name with the format abc001.mac (where the macro number, 001 here, is allocated sequentially), and is held in the directory ABCMAC (or as defined by the project\u2019s environmental variables).\nWhen User E next enters MONITOR, they receive a message asking them to run the inter-DB connection macro abc001.mac and to delete it when they have done so.\nUser E enters MODEL and runs the inter-DB connection macro by giving the command\n$M /%ABCMAC%/abc001.mac\nThis sets the CREF for the Nozzle to point to the TREF of the Branch and completes the link between the two DBs.\nUser E enters MONITOR (or ADMIN if they have sufficient access rights) and deletes the redundant macro by giving the command\nDELETE MACRO 1\nwhere 1 is the macro number. This command is valid in Model, Monitor and Admin.\nUser P sets the TREF of their Branch to point to the CREF of the Nozzle in the Equipment DB.\nUser P sets the TREF of their Branch to point to the CREF of the Nozzle in the Equipment DB.\nWhen User P tries to set the Nozzle\u2019s CREF, they receive a message telling them that they are trying to connect to a read-only DB and that an inter-DB connection macro is being created automatically. This macro, which stores the commands needed to set the CREF, is given a name with the format abc001.mac (where the macro number, 001 here, is allocated sequentially), and is held in the directory ABCMAC (or as defined by the project\u2019s environmental variables).\nWhen User P tries to set the Nozzle\u2019s CREF, they receive a message telling them that they are trying to connect to a read-only DB and that an inter-DB connection macro is being created automatically. This macro, which stores the commands needed to set the CREF, is given a name with the format abc001.mac (where the macro number, 001 here, is allocated sequentially), and is held in the directory ABCMAC (or as defined by the project\u2019s environmental variables).\nWhen User E next enters MONITOR, they receive a message asking them to run the inter-DB connection macro abc001.mac and to delete it when they have done so.\nWhen User E next enters MONITOR, they receive a message asking them to run the inter-DB connection macro abc001.mac and to delete it when they have done so.\nUser E enters MODEL and runs the inter-DB connection macro by giving the command\n$M /%ABCMAC%/abc001.mac\nThis sets the CREF for the Nozzle to point to the TREF of the Branch and completes the link between the two DBs.\nUser E enters MODEL and runs the inter-DB connection macro by giving the command\nUser E enters MONITOR (or ADMIN if they have sufficient access rights) and deletes the redundant macro by giving the command\nDELETE MACRO 1\nwhere 1 is the macro number. This command is valid in Model, Monitor and Admin.\nUser E enters MONITOR (or ADMIN if they have sufficient access rights) and deletes the redundant macro by giving the command\nNote:\nIf User P checks their DB for data consistency errors between Stages 2 and 4, when the macro has been created but not yet run, they will get an \u2018incompatible connection reference\u2019 message. They cannot finalize their design until User E has run the macro. Thus, the successful use of inter-DB connection macros relies on good co-operation between the teams involved.\nNote:\nInter-DB connection macros are also created in multiwrite DBs if an attachment is claimed by another user.\n\n\n\none\nWrite\nRead\ninter-DB connection macro\nProject ABC\nUser P\nUser E\nnot\nabc001.mac\nABCMAC\nNote\n:\nNote\n:"}
{"Headers": "Sequence Number Generator", "Content": "The Sequence Number Generator is useful to derive unique names in a concurrent application environment. The functionality is based on a set of methods that operates towards a separate overwrite type of database. This is storing the uniquely named sequences and also details about the respective sequence. Name sequence elements and their attributes are protected from being handled manually. One way to operate with name sequences is through PML NameSeq objects.\nA unique item in a sequence is made up by the name of the sequence followed by a running number, for example, TEST123, where TEST is the name of the sequence and 123 is the running number.\n\n\n"}
{"Headers": "Create a Name Sequence Database", "Content": "A name sequence database, of the type NSEQ, is created by the Admin utility and selected to an Multiple Database (MDB) as any other ordinary type of database. The options given while creating this type of database is limited as the NSEQ type of the database is predestined to be of an overwrite type.\n\n\n"}
{"Headers": "Enable Usage of Name Sequences from PML", "Content": "import 'aveva.model.nameseq'\nusing namespace 'aveva.model.nameseq'\n\n\n\naveva.model.nameseq\naveva.model.nameseq"}
{"Headers": "NameSeq Object", "Content": "NameSeq(string)\nBool\nIf not existing, creates a sequence of given name, otherwise brings back the name sequence available.\nNext()\nString\nGet next composed name in sequence.\nRemove()\nBool\nDelete sequence.\nSetStart(real)\nBool\nSet first running number of sequence (default 0).\nSetMax(real)\nBool\nSet last running number of sequence.\nSetStep(real)\nBool\nSet increment (default 1).\nSetWraparound()\nBool\nAllow wraparound when maximum value is reached.\nSetNoWraparound()\nBool\nDisallow wraparound (error returned when maximum is reached).\nGetMax()\nReal\nGet last running number of sequence (default 2147483647).\nGetStep()\nReal\nGet increment.\nGetCurrent()\nReal\nGet current running number.\nGetName()\nString\nGet name of sequence.\nIsWraparound()\nBool\nGet wraparound status.\nReStart\nBool\nRestarts a sequence from its first running number.\nGetStart\nReal\nGet first running number\n\nName\nResult\nDescription\nNameSeq(string)\nBool\nIf not existing, creates a sequence of given name, otherwise brings back the name sequence available.\nNext()\nString\nGet next composed name in sequence.\nRemove()\nBool\nDelete sequence.\nSetStart(real)\nBool\nSet first running number of sequence (default 0).\nSetMax(real)\nBool\nSet last running number of sequence.\nSetStep(real)\nBool\nSet increment (default 1).\nSetWraparound()\nBool\nAllow wraparound when maximum value is reached.\nSetNoWraparound()\nBool\nDisallow wraparound (error returned when maximum is reached).\nGetMax()\nReal\nGet last running number of sequence (default 2147483647).\nGetStep()\nReal\nGet increment.\nGetCurrent()\nReal\nGet current running number.\nGetName()\nString\nGet name of sequence.\nIsWraparound()\nBool\nGet wraparound status.\nReStart\nBool\nRestarts a sequence from its first running number.\nGetStart\nReal\nGet first running number\n\n\n"}
{"Headers": "Typical Usage of Name Sequences", "Content": "Following is an example showing how to define a sequence named TEST and let the sequence start from 1000. The method Next increments the running number and returns a name composed by the name of the sequence followed by the running number, for example,. TEST1001, TEST1002. Whenever needed it is possible to make a break-in in the sequence and change for example the increment to e.g. 20 instead of 1 as default. This will then generate composed names as TEST1022, TEST1042.\n\n\n\n\nNext"}
{"Headers": "Name Sequences in Global Projects", "Content": "Name sequence databases are local for each site and are not replicated among the different sites. However names generated by the name sequence mechanism can be used for naming of items included in the Global synchronisation. To maintain unique naming of items in a Global environment, the setup of name sequences must be considered. A proper method is to let each site have different starting numbers of their name sequences, for example,. SetStart() to a number different for each site.\n\n\n"}
{"Headers": "Distributed Attributes", "Content": "New functionality feature called Distributed attributes has been introduced to the database system. The fundamental concept of distributed attributes is about enabling objects to have groups of attributes distributed across hierarchies and potentially databases. As a result, a number of improvements can be used in the database system.\nImproved Concurrency\nPossibility to Distribute an Objects Attributes across Hierarchies and Databases\nSimplified Access Control\nData Inclusion/Exclusion\nUser Extendibility on New and Existing Data\nAutomatic Attribute Management\n\nUsers may work on different sets of data of an object in parallel.\nSupport simultaneous multi-discipline update on same object.\nClaim granularity, only claim relevant portions of an object.\nUsers may work on different sets of data of an object in parallel.\nUsers may work on different sets of data of an object in parallel.\nSupport simultaneous multi-discipline update on same object.\nSupport simultaneous multi-discipline update on same object.\nClaim granularity, only claim relevant portions of an object.\nClaim granularity, only claim relevant portions of an object.\nEasy distribution over Global dividing distributed attribute over different primary locations.\nEasy distribution over Global dividing distributed attribute over different primary locations.\nEasy distribution over Global dividing distributed attribute over different primary locations.\nTeam owning databases provides both read/write and read-only levels of access within the same object.\nTeam owning databases provides both read/write and read-only levels of access within the same object.\nTeam owning databases provides both read/write and read-only levels of access within the same object.\nPossible to hide select portions of an object.\nPossible to hide select portions of an object.\nPossible to hide select portions of an object.\nIn cases where it is hard to define User Defined Element Types (UDETs) this is an alternative way to extend existing objects with distributed attribute data.\nIn cases where it is hard to define User Defined Element Types (UDETs) this is an alternative way to extend existing objects with distributed attribute data.\nIn cases where it is hard to define User Defined Element Types (UDETs) this is an alternative way to extend existing objects with distributed attribute data.\nThe management (create/delete/referencing) of the distributed attributes.\nWhile the concept itself is rather straightforward, it introduces new possibilities to applications.\nAn pictoral representation of how the concept might be used in an application, follows:\nThe management (create/delete/referencing) of the distributed attributes.\nThe management (create/delete/referencing) of the distributed attributes.\nWhile the concept itself is rather straightforward, it introduces new possibilities to applications.\nWhile the concept itself is rather straightforward, it introduces new possibilities to applications.\nAn pictoral representation of how the concept might be used in an application, follows:\nAn pictoral representation of how the concept might be used in an application, follows:\n\n\n\nImproved Concurrency\nPossibility to Distribute an Objects Attributes across Hierarchies and Databases\nSimplified Access Control\nData Inclusion/Exclusion\nUser Extendibility on New and Existing Data\nAutomatic Attribute Management"}
{"Headers": "Terminology and Data", "Content": "Distributed attributes are built on top of the well established functions and concepts of AVEVA E3D Design technology. The functionality of distributed attributes User Defined Attributes (UDAs) and User Defined Element Type (UDETs) behave as an integral part of the system.\nA distributed attribute group is a UDET based on the XPITEM element type. The UDET itself works like any other UDET and may carry any number of attributes, whereas UDAs, which are defined by you.\nAn pictoral representation of how the components relate to each other is displayed below:\n\nTerm\nDescription\nBinding element\nThe owner of distributed attributes groups.\nDistributed element / attribute group\nThe container for distributed attributes these can be thought of as attribute groups. The distributed element is always a UDET based on the XPITEM element type.\nDistributed attribute\nThe attributes, UDAs that a defined for an attribute group.\nDefault home\nThe location where the distributed elements are stored and managed.\nBinding element\nThe owner of distributed attributes groups.\nDistributed element / attribute group\nThe container for distributed attributes these can be thought of as attribute groups. The distributed element is always a UDET based on the XPITEM element type.\nDistributed attribute\nThe attributes, UDAs that a defined for an attribute group.\nDefault home\nThe location where the distributed elements are stored and managed.\nAll definitions of Distributed Attributes are stored in dictionary databases and maintained by the Lexicon module.\nTerm\nDescription\nBinding element\nThe owner of distributed attributes groups.\nDistributed element / attribute group\nThe container for distributed attributes these can be thought of as attribute groups. The distributed element is always a UDET based on the XPITEM element type.\nDistributed attribute\nThe attributes, UDAs that a defined for an attribute group.\nDefault home\nThe location where the distributed elements are stored and managed.\n\n\n\nUDA\nUDET\nUDET\nXPITEM\nUDET\nUDET\nUDA\nBinding element\nDistributed element / attribute group\nDistributed attribute\nDefault home"}
{"Headers": "Configuration", "Content": "Distributed attributes are made up of User Defined Element Type (UDETs) which are associated with the binding element that they add attributes to. To configure distributed attributes:\nCreate UDETs to be used as distributed attribute groups.\nCreate the attributes to be included in the attribute groups.\nCreate distributed attribute schema associating elements with the distributed attribute group.\nCreate the default home definition the location where distributed attributes are to be created and managed.\nCreate actual default home top level elements where distributed attribute groups are created.\nCreate UDETs to be used as distributed attribute groups.\nCreate UDETs to be used as distributed attribute groups.\nCreate the attributes to be included in the attribute groups.\nCreate the attributes to be included in the attribute groups.\nCreate distributed attribute schema associating elements with the distributed attribute group.\nCreate distributed attribute schema associating elements with the distributed attribute group.\nCreate the default home definition the location where distributed attributes are to be created and managed.\nCreate the default home definition the location where distributed attributes are to be created and managed.\nCreate actual default home top level elements where distributed attribute groups are created.\nCreate actual default home top level elements where distributed attribute groups are created.\n\n\n"}
{"Headers": "Create Distributed Attribute Group, the UDET", "Content": "The task only differ from creating a regular User Defined Element Type (UDET) in one aspect, and that is that the UDET intended for use as a distributed attribute group must be based on the XPITEM element type.\nYou must create the UDETs to be used as distributed attribute groups, these UDETs needs to be defined with XPITEM as their basetype, then the attributes must be created.\n\n\n"}
{"Headers": "Create the Attributes, as UDAs", "Content": "The attributes can be defined as any regular User Defined Attribute (UDA), no special considerations need to be taken.\nFor example: the UDAs, to be included in the attribute groups.\n\n\n"}
{"Headers": "Create Distributed Attributes Schema", "Content": "The distributed attribute schema, associating elements with the distributed attribute group must then be created.\nThere are two administrative levels, Distributed Attribute Definition World (DSXWLD) and Distributed Attribute Group (DSXGRP) that is left without any specific explanation. They serve the same purpose of grouping things, that is schemas, UDAs together. Distributed attributes schemas are configured using the Distributed Attribute Schema (DSXSCH), Distributed Attribute Owner (DSXOWN) and Distributed Attribute Member (DSXMBR) objects in the lexicon application.\n\nA distributed attribute schema is represented by the DSXSCH element, and consists of a name and an optional default home reference. The default home reference may be overridden at lower levels in the schema. At present, all schemas are treated as one unified schema; this functionality is subject to change.\n\nYou can define the element types that may be extended by distributed attributes. The definition contains an Element List (ELEL) which designates the element types. It also contains a default home reference that, if set override default home defined on schema level.\n\nThe last part of the distributed attributes schema definition is to associate the UDETs that form the distributed attributes for the owning elements specified in DSXOWN. The definition specifies which XPITEM based UDETs that can be used as distributed attributes for the specified owner. There is a cardinality definition available that defines the minimum and maximum number of each of the distributed attributes that may be created. A -1 in the maximum definition represents an infinite number. It also contains an allocation reference that might override anything defined at schema or owner level.\n\n\n\n"}
{"Headers": "Default Home Definition", "Content": "The location where distributed attributes are created and managed must now be defined, create the default and home definition.\nDefault home definition is a structure that is used by distributed attributes to figure out where to create and store the distributed part of the attributes. The DEFHOM (\"Allocate\" in the GUI) reference points to the allocation rule to use.\nEach Default home definition is represented by a Distributed Attribute Default Home (DSXHOM) element the element must be referenced from distributed attributes, for example: Distributed Attribute Schema (DSXSCH) (where to store elements).\n\n\nYou must then create the actual default home. For example: create the top-level elements where the distributed attribute groups are created.\nThe default home destination contains a string or ID expression that evaluates the name or ID of the default home to be used. When used together with distributed attributes, the name must result in a XPIWLD element. The destination definition also evaluates a logical test that must yield true in order for it to be used.\n\nEnables more elaborate tests, logical expressions can be defined and inserted between the Distributed Attribute Default Home (DSXHOM) and the final destination.\n\nNote:\nThat the tests on the logical expressions has not yet implemented.\n\n\n\nNote\n:\nDefault Home"}
{"Headers": "Create the XPIWLD Home Elements", "Content": "For each unique destination Distributed Attribute Destination (DSXDST) defined, the corresponding actual XPIWLD home\u2011element must be created. For example:\nNEW XPIWLD /MyLineLists\n\n\n\nXPIWLD"}
{"Headers": "Distributed Attributes, Configuration and Usage Details", "Content": "The information that defines the available distributed attributes is defined in two separate hierarchies:\nthe structure of the attributes\nwhere to physically create and store the data.\nthe structure of the attributes\nthe structure of the attributes\nwhere to physically create and store the data.\nwhere to physically create and store the data.\n\n\n"}
{"Headers": "Distributed Attributes and Default Home Configuration", "Content": "The distributed attributes definition is created in the Lexicon module and stored in a Dictionary (DICT) database. The detail information of each attribute relies on the existing definitions of User Defined Attributes (UDAs) and User Defined Element Type (UDETs). The definition of distributed attributes is to define what type of attribute groups (for example: UDETs) are allowed as distributed attributes to which element types, and their cardinality (further constrains definitions may follow).\n\n\n"}
{"Headers": "DSX Hierarchy, Top Elements", "Content": "The hierarchy where this information is stored is organized the following way:\n\nThe common DSX data structure that contains both distributed attributes and default home definition.\nThe Distributed Attribute Definition World (DSXWLD) is the top level element for storing distributed attribute schemas and default home selectors. It does not contain any attributes of particular interest to distributed attributes configuration. It can have Distributed Attribute Group (DSXGRP) as members.\nNAME\nText\nStandard\nDESC\nText\nStandard\nThe DSXGRP is a purely administrative level that aids in organizing distributed attribute schemas and default home selectors. It does not contain any attributes of particular interest to distributed attributes configuration. The DSXGRP element may have DSXSCH and DSXHOM members.\nNAME\nText\nStandard\nDESC\nText\nStandard\n\nAttribute Name\nType\nUsage\nNAME\nText\nStandard\nDESC\nText\nStandard\nAttribute Name\nType\nUsage\nNAME\nText\nStandard\nDESC\nText\nStandard\n\n\n\nDSXWLD\nDSXGRP\nDSXGRP\nDSXGRP\nDSXSCH\nDSXHOM"}
{"Headers": "Distributed Attributes Schema", "Content": "A distributed attribute schema is headed with a Distributed Attribute Schema (DSXSCH) element. Currently there is no particular support or use of multiple schemas but to organize distributed attributes in groups of definitions.\nThe DSXSCH defines a distributed attribute schema the vital attribute is the Default Home (DEFHOM) that may contain a reference to a schema default Distributed Attribute Default Home (DSXHOM) element. The DSXSCH element can have DSXOWN as members.\nNAME\nText\nStandard\nDESC\nText\nStandard\nDEFHOM\nRef to DSXHOM\nIdentifies the default home selector for this schema\nThe Distributed Attribute Owner (DSXOWN) defines the element types that may have the defined set of distributed attributes. One DSXOWN may define one or more element types as defined by the Element List (ELEL) attribute. It also contains an optional reference to a binder default DSXHOM element, that DSXHOM overrides any DSXHOM definition on the DSXSCH level. The DSXOWN element can have Distributed Attribute Member (DSXMBR) as members.\nNAME\nText\nStandard\nDESC\nText\nStandard\nDEFHOM\nReference to DSXHOM\nIdentifies the default home selector for the binder. Overrides any definition on schema level.\nELEL\nElement types list\nDefines the element types that may have distributed attribute types bound to them\nThe DSXMBR defines the element types to be used as distributed attributes. One DSXMBR may define one or more element types as defined by the ELEL attribute. The element types must be User Defined Element Types (UDETs) based on the XPITEM element type. It also contains an optional reference to a distributed attribute default home DSXHOM element, that DSXHOM overrides any definition on the DSXOWN level.\nNAME\nText\nStandard\nDESC\nText\nStandard\nDEFHOM\nReference to DSXHOM\nIdentifies the default home selector for the distributed element types defined in this definition\nAUTCRE\nLogical\nAuto-create. The distributed element is automatically created if it doesn't exist at a modification operation.\nELEL\nElement types list\nDefines the element types that represents the distributed attribute types\nCARD\nInteger array [2]\nMin and Max cardinality of the distributed attributes. (Note, only the Max Cardinality is currently effective)\n\nAttribute Name\nType\nUsage\nNAME\nText\nStandard\nDESC\nText\nStandard\nDEFHOM\nRef to DSXHOM\nIdentifies the default home selector for this schema\nAttribute Name\nType\nUsage\nNAME\nText\nStandard\nDESC\nText\nStandard\nDEFHOM\nReference to DSXHOM\nIdentifies the default home selector for the binder. Overrides any definition on schema level.\nELEL\nElement types list\nDefines the element types that may have distributed attribute types bound to them\nAttribute Name\nType\nUsage\nNAME\nText\nStandard\nDESC\nText\nStandard\nDEFHOM\nReference to DSXHOM\nIdentifies the default home selector for the distributed element types defined in this definition\nAUTCRE\nLogical\nAuto-create. The distributed element is automatically created if it doesn't exist at a modification operation.\nELEL\nElement types list\nDefines the element types that represents the distributed attribute types\nCARD\nInteger array [2]\nMin and Max cardinality of the distributed attributes. (Note, only the Max Cardinality is currently effective)\n\n\n\nDSXSCH\nDSXSCH\nDEFHOM\nDSXHOM\nDSXSCH\nDSXOWN\nDSXOWN\nDSXOWN\nELEL)\nDSXHOM\nDSXHOM\nDSXHOM\nDSXSCH\nDSXOWN\nDSXMBR\nDSXMBR\nDSXMBR\nELEL\nXPITEM\nDSXHOM\nDSXHOM\nDSXOWN"}
{"Headers": "Default Home Selector", "Content": "The default home is defined by a Distributed Attribute Default Home (DSXHOM) hierarchy, it is expected that a number of default home definitions are in use for distributed attributes.\nThe DSXHOM defines a default home selector, it contains no information vital to the Default home configuration and may have Distributed Attribute Test (DSXTST) and Distributed Attribute Destination (DSXDST) members.\nNAME\nText\nStandard\nDESC\nText\nStandard\nThe DSXTST defines a test that needs to yield true upon evaluation for considering using this default home, it contains a test expression defined in PML1. The expression operates on the current binding element.\nNAME\nText\nStandard\nDESC\nText\nStandard\nDHTEST\nPML1 expression\nThe test to evaluate to examine if this represents the requested default home.\nThe DSXDST denotes the default home value as a text string. It also contains a test that needs to yield true upon evaluation for considering this default home being valid.\nNAME\nText\nStandard\nDESC\nText\nStandard\nDHTEST\nPML1 expression\nThe test to evaluate to examine if this represents the requested default home.\nDHTEXT\nPML1 expression\nAn expression of string or ID type that should evaluate to an existing element at runtime. (For distributed attributes, this must resolve to a XPIWLD element).\n\nAttribute Name\nType\nUsage\nNAME\nText\nStandard\nDESC\nText\nStandard\nAttribute Name\nType\nUsage\nNAME\nText\nStandard\nDESC\nText\nStandard\nDHTEST\nPML1 expression\nThe test to evaluate to examine if this represents the requested default home.\nAttribute Name\nType\nUsage\nNAME\nText\nStandard\nDESC\nText\nStandard\nDHTEST\nPML1 expression\nThe test to evaluate to examine if this represents the requested default home.\nDHTEXT\nPML1 expression\nAn expression of string or ID type that should evaluate to an existing element at runtime. (For distributed attributes, this must resolve to a XPIWLD element).\n\n\n\nDSXHOM\nDSXHOM\nDSXTST\nDSXDST\nDSXTST"}
{"Headers": "New Syntaxes", "Content": "There are new syntaxes available to work with distributed attributes.\nThe creation/deletion of the distributed attributes member(s)\nThe manipulating of the individual values on the distributed attributes members.\nThe creation/deletion of the distributed attributes member(s)\nThe creation/deletion of the distributed attributes member(s)\nThe manipulating of the individual values on the distributed attributes members.\nThe manipulating of the individual values on the distributed attributes members.\n\n\n"}
{"Headers": "New and Updated Syntax", "Content": "There are also a small number of pseudo attributes available on elements that are associated with distributed attributes.\nThe NEW command creates a new distributed attribute and associates the CE/on element with it.\nThe example creates a new distributed attribute of type :PRESSURE and associates it with Current Element (CE).\nDATT NEW\nDATT NEW <type> [on <element>]\nDATT NEW :PRESSURE\n\n\n\nSyntax\nExample"}
{"Headers": "DATT DELete", "Content": "The DELete command removes distributed attributes from Current Element (CE)/from element\nThe example deletes the last distributed attribute member of type :PROCESS from /MyEquipment.\nDATT DELete ALL [<type>] [from < element>]\nDATT DELete [FIRST | LAST | <int>] <type> [from < element>]\n   \nDATT DEL LAST :PROCESS FROM /MyEquipment\n\n\n\nSyntax\nFIRST\nExample"}
{"Headers": "Q ATT", "Content": "The existing Q ATT have been extended to allow for querying distributed attributes.\nThe command displays all the values of the :PROCESS type associated with Current Element (CE).\nQ ATT [AS ANY | <type>]\nQ ATT AS :PROCESS\n\n\n\nSyntax\nExample"}
{"Headers": "Distributed Attributes and Attribute Syntax", "Content": "Since more than one instance of a distributed element is handled [n] is used to qualify which instance you are interested in.\nThe syntax is used on both queries and manipulations of attributes, as well as in PML1 expressions.\n-- Query the value of the :local\\:process distributed attribute on Current Element (CE)\n-- Set the value of distributed attribute :local\\:process to false\n-- Query all LNLIST elements where distributed attribute :local\\:process equals true\n-- Query the value of the second instance of distributed attribute :local\\:process\n-- Set the value of the second instance of distributed attribute :local\\:process to false\n-- Query all LNLIST elements where second instance of distributed attribute :local\\:process equals true\n:UDANAME\\:UDETNAME\nQ :LOCAL\\:PROCESS\n:local\\process true\n:LOCAL\\:PROCESS false\nQ ALL LNLIST WITH (:LOCAL\\PROCESS EQ true)\nQ :LOCAL\\:PROCESS[2]\n:local\\process[2] true\n:LOCAL\\:PROCESS[2] false\nQ ALL LNLIST WITH (:LOCAL\\PROCESS[2] EQ true)\n\n\n\nSyntax\nExample"}
{"Headers": "PML2 Support", "Content": "There is full PML2 support for distributed attributes. Constructs such as; !!ce.:local\\:process = false works as could be expected. Also more complex things involving both arrays and multiple instances of distributed attributes work with the syntax that would be expected.\n-- Set the third array element in the second instance of distributed attribute :myArray\\:MyList to 12.345\n!!ce.:myArray[3]\\:myList[2] = 12.345\n\n\n\n!!ce.:local\\:process = false\nExample\n:myArray\\:MyList to 12.345"}
{"Headers": "Pseudo Attributes Associated with Distributed Attributes", "Content": "There are a few number of pseudo attributes available to all elements that may have distributed attributes associated with them.\n\n\n"}
{"Headers": "DLIST - Eligible Distributed Attributes Members", "Content": "The attribute returns a list of all eligible distributed attribute types that may be associated with Current Element (CE). The list does not consider any constraints defined in the schema.\nQ DLIST\nDLIST :PROCESS :PRESSURE\n\n\n\nExample"}
{"Headers": "XRLSTT - List Distributed Attributes Member Types Associated", "Content": "This attribute returns a list of all distributed attribute types associated with current element.\nQ XRLSTT\nXRLSTT :PROCESS :PRESSURE\n\n\n\nExample"}
{"Headers": "XRLIST - List Distributed Attributes Member Associated", "Content": "The attribute returns a list of all distributed attribute members (elements) associated with current element. The attribute may take an optional qualifier on typename.\nQ XRLIST\nXRLIST\nQ XRLIST (TYPENAME :PROCESS )\n\n\n\nExample\nQ XRLIST\nQ XRLIST (TYPENAME :PROCESS )"}
{"Headers": "XRQCNT - Count of Distributed Attributes Member Associated", "Content": "The attribute returns the number of distributed attribute members (elements) associated with current element. The attribute may take an optional qualifier on typename.\nQ XRQCNT\nXRQCNT 2\nQ XRQCNT (TYPENAME :PROCESS )\nXRQCNT 1\n\n\n\nExample\nQ XRQCNT\nQ XRQCNT (TYPENAME :PROCESS )"}
{"Headers": "XRQELE - Return a Single Distributed Attribute Member", "Content": "The attribute returns a selected distributed attributes member of distributed attribute members (elements) associated with current element. The attribute may take an optional qualifier of typename.and relative position.\nQ XRQELE\nXRQELE 1 :PROCESS 1 of XPIFLD 2 of XPIFLD 1 of /THEPROCWLD\nQ XRQELE ( 1 )\nXRQELE 1 :PRESSURE 1 of XPIFLD 2 of XPIFLD 1 of /THEPROCWLD\n\n\n\nExample\nQ XRQELE\nQ XRQELE ( 1 )"}
{"Headers": "ATTDST - List of Attributes to Show", "Content": "The attribute is available on the distributed attribute member and returns a list of attributes that should be shown by default as attributes. The attribute fulfils the same purpose as ATTLIS for normal attributes.\nQ ATTDST\nATTDST :TEMP :VISCOCITY\n\n\n\nExample"}
{"Headers": "DFHOME - The Evaluated Default Home", "Content": "The attribute is available on the any element, in addition to be used for distributed attributes, it may be used in a generic way.\nIt takes the typename of a bindable noun/udet as qualifier. It evaluates the actual home element using current element as when evaluating the test expressions and returns a nulref or a ref to an XPIWLD element.\nThe DSXHOM reference passed as a qualifier is used to evaluate the expressions defined in the DSXTST/DSXDST of that DSXHOM. It returns a nulref of the ref of the ID value held in the DHTEXT attribute of the resulting DSXDST. The Current Element (CE) is passed to the expression for evaluation.\n-- distributed attributes, get the location to store distributed attributes of type process for CE.\n-- Generic example, get the reference that results of evaluation the DSXHOM /MyHomeSelector for /TESTTHIS.\nQ DFHOME ( TYPENAME :PROCESS )\nDFHOME /THEPROCESSWORLD\nQ DFHOME ( /MyHomeSelector ) OF /TESTTHIS\nDFHOME /STOREITHERE\nNote:\nThe evaluation finds the associated Distributed Attribute Default Home (DSXHOM) from the typename qualifier, after that processing is the same as for the generic case.\n\n\n\nWhen used specifically for distributed attributes evaluation\nNote\n:\nUsing it for generic \"find a default home\" purposes\nExample\nQ DFHOME ( TYPENAME :PROCESS )\nQ DFHOME ( /MyHomeSelector ) OF /TESTTHIS"}
{"Headers": "DATAL", "Content": "As a complement to normal Data Listing (DATAL) processing of distributed attributes, there is a specialized support that generates datals with the distributed attributes syntax.\nFor example: getting everything under the ZONE /MyZone including any distributed attributes would be done by executing the following output command:\nPart of the output would resemble the following, with the distributed attributes statements included:\nOUTPUT INCLUDE Distributed/ATTRIBUTES ... <SELELE> and other options\nOUTPUT INCLUDE DistributedA /MyZone\nNEW EQUI\nDATT NEW :Process\n:Local\\:Process false\nEND\n\n\n\nSyntax"}
{"Headers": "Element Selection, Claim, Flush", "Content": "The element selection syntax is extended so that the distributed attribute group, in previous examples the :Process is addressable using the AS keyword. Allows you to extract operations such as claim, flush and Status Control operations on the distributed attribute granularity level.\n\n\n\n:Process"}
{"Headers": "Status Control Example", "Content": "-- Assign /MyStatus to distributed attribute group :Process of /MyEquip\n-- Query the list of assigned statuses of the distributed attribute group :Process of /MyEquip\nStvLst\\:Process /MyStatus\n-- Query the status value for /MyStatus of the distributed attribute group :Process of /MyEquip\nSTM ASS /MyStatus to /MyEquip as :Process\nQ STVLST OF /MyEquip AS :Process\nQ STVVAL(/MyStatus) OF /MyEquip AS :Process\nStvLst\\:Process /NotStarted\n\n\n\nSTM ASS /MyStatus to /MyEquip as :Process\nQ STVLST OF /MyEquip AS :Process\nQ STVVAL(/MyStatus) OF /MyEquip AS :Process"}
{"Headers": "Copying Data between Projects", "Content": "The Copying Data between Projects facility is not available in AVEVA Plant.\n\n\n"}
{"Headers": "Cleanup and the CLEANUp Command", "Content": "The command CLEANUp cleans up unwanted references in the database. It is possible to remove null references and unresolved/invalid references.\nThe logical attributes NULLREf, INVREF and UNRESOlved is used to sort out whether a reference attribute points to something valid or not. The syntax is the same for all three:\nAnswers the question is the attribute att null (=0/0)?\nIs the attribute att pointing to an element whose existence we cannot find and verify? It could be that the database is missing or that the reference is truly invalid.\nIs the attribute pointing to an element that is non-existent? This differs from unresolved in that the database that should accommodate the missing element is present in the active mdb.\n\nQ NULLRE (ATTNAME att )\nQ UNRESO (ATTNAME att )\nQ INVREF (ATTNAME att )\nCLEANU/P NULL/REF | INVALID | UNRES/OLVED attribute [ON noun] [FOR ele] [SETNULL | DELETE]\nCLEANU NULL STLREF ON EQUI DELETE\nCLEANU UNRES CATREF FOR /PIPES SETNULL\nCLEANU INVALID CATREF\n\n\n\nQ NULLRE (ATTNAME \natt\n )\nQ UNRESO (ATTNAME \natt\n )\nQ INVREF (ATTNAME \natt\n )\nCLEANU/P NULL/REF | INVALID | UNRES/OLVED \nattribute\n [ON noun] [FOR ele] [SETNULL | DELETE]\nCLEANU NULL STLREF ON EQUI DELETE\nCLEANU UNRES CATREF FOR /PIPES SETNULL\nCLEANU INVALID CATREF"}
{"Headers": "Catalog Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the Catalogue database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "Catalogue Database Elements", "Content": "All data in the Catalogue database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Communications Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the Communications database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "Communications Database Elements", "Content": "All data in the Communications database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts,\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Communication Element (COMM)", "Content": "Status\nLocrf\nLocation reference\nUcurd\nUCURD\n\nStatus\nLocrf\nLocation reference\nUcurd\nUCURD\nCommunication World Element (COMW)\nNone\nStatus\nLocrf\nLocation reference\nUcurd\nUCURD\n\n\n\nCommunication World Element (COMW)\nLocrf\nUcurd\nCommunication World Element (COMW)"}
{"Headers": "Communication World Element (COMW)", "Content": "Name\nName of the element\nPrjlock\nProject lock\nIsolt\nLocation isolation flag\nCOMUST\nUpgrade flag\nName\nName of the element\nPrjlock\nProject lock\nIsolt\nLocation isolation flag\nCOMUST\nUpgrade flag\nWorld Element (WORLD)\nCommunication Element (COMM)\nName\nName of the element\nPrjlock\nProject lock\nIsolt\nLocation isolation flag\nCOMUST\nUpgrade flag\n\n\n\nWorld Element (WORLD)\nCommunication Element (COMM)\nName\nPrjlock\nIsolt\nCOMUST\nWorld Element (WORLD)\nCommunication Element (COMM)"}
{"Headers": "World Element (WORLD) - Communication", "Content": "Administrative Element\nPrimary Element\nThe WORLD is the topmost level of the database hierarchy within which all other elements exist. It cannot be deleted or copied in the same way that applies to say, a ZONE or a DRWG. Its existence is controlled by the ADMINISTRATION module.\nName\nName of the element\nName\nName of the element\nNone\nCommunication World Element (COMW)\nName\nName of the element\n\n\n\nCommunication World Element (COMW)\nName\nCommunication World Element (COMW)"}
{"Headers": "Elements in Accommodation Category", "Content": "All data in the Design database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\nCategories are administrative elements which allow you to segregate particular types of design data into logical parts of the hierarchy. For more information on Categories and associated administrative elements, refer to Catalogues and Specifications Reference Manual.\n\n\n"}
{"Headers": "Access Point Element (ACCPNT)", "Content": "Accommodation Element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nAccType\nAccess type\nRefLevel\nReference Level\nOpnSize\nOpening size\nPosition\nPosition\nOrientation\nOrientation\nAccRef\nReference to Access element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nAccType\nAccess type\nRefLevel\nReference Level\nOpnSize\nOpening size\nPosition\nPosition\nOrientation\nOrientation\nAccRef\nReference to Access element\nAccess Point Set Element (ACCSET)\nNone\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nAccType\nAccess type\nRefLevel\nReference Level\nOpnSize\nOpening size\nPosition\nPosition\nOrientation\nOrientation\nAccRef\nReference to Access element\n\n\n\nAccess Point Set Element (ACCSET)\nName\nPurpose\nFunction\nAccType\nRefLevel\nOpnSize\nPosition\nOrientation\nAccRef\nAccess Point Set Element (ACCSET)"}
{"Headers": "Access Point Set Element (ACCSET)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStair Tower Element (STRTWR)\nStairwell Element (STRWELL)\nAccess Point Element (ACCPNT)\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\n\n\n\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStair Tower Element (STRTWR)\nStairwell Element (STRWELL)\nAccess Point Element (ACCPNT)\nName\nPurpose\nFunction\nDescription\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStair Tower Element (STRTWR)\nStairwell Element (STRWELL)\nAccess Point Element (ACCPNT)"}
{"Headers": "Building Block Element (BBLOCK)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nPurpose\nDescription code word\nDescription\nDescription of the element\nNAngle\nNorth angle\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nAreaReference\nArea reference\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nPurpose\nDescription code word\nDescription\nDescription of the element\nNAngle\nNorth angle\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nAreaReference\nArea reference\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\nWorld Element (WORLD)\nArea Definition Element (AREADEF)\nBuilding Level Element (BLEVEL)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nOpen Space Element (OPENSPACE)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nStairwell Element (STRWELL)\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nPurpose\nDescription code word\nDescription\nDescription of the element\nNAngle\nNorth angle\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nAreaReference\nArea reference\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\n\n\n\nWorld Element (WORLD)\nArea Definition Element (AREADEF)\nBuilding Level Element (BLEVEL)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nOpen Space Element (OPENSPACE)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nStairwell Element (STRWELL)\nName\nArea\nNumber\nFunction\nPurpose\nDescription\nNAngle\nPosition\nOrientation\nHeidefault\nAreaReference\nLabOffset\nUuidia\nWorld Element (WORLD)\nArea Definition Element (AREADEF)\nBuilding Level Element (BLEVEL)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nOpen Space Element (OPENSPACE)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nStairwell Element (STRWELL)"}
{"Headers": "Building Level Element (BLEVEL)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nPurpose\nDescription code word\nDescription\nDescription of the element\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nNAngle\nNorth angle\nElevation\nElevation\nAreaReference\nArea reference\nDFlRHeight\nDefault Floor Height\nDClnHeight\nDefault Ceiling Height\nXYOffset\nXY offset\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nPurpose\nDescription code word\nDescription\nDescription of the element\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nNAngle\nNorth angle\nElevation\nElevation\nAreaReference\nArea reference\nDFlRHeight\nDefault Floor Height\nDClnHeight\nDefault Ceiling Height\nXYOffset\nXY offset\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\nBuilding Block Element (BBLOCK)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nInventory List Element (INVLST)\nOpen Space Element (OPENSPACE)\nRef Data Group Element (REFDAT)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nBoundary Element Set Element (SPBSET)\nStairwell Element (STRWELL)\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nPurpose\nDescription code word\nDescription\nDescription of the element\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nNAngle\nNorth angle\nElevation\nElevation\nAreaReference\nArea reference\nDFlRHeight\nDefault Floor Height\nDClnHeight\nDefault Ceiling Height\nXYOffset\nXY offset\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\n\n\n\nBuilding Block Element (BBLOCK)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nInventory List Element (INVLST)\nOpen Space Element (OPENSPACE)\nRef Data Group Element (REFDAT)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nBoundary Element Set Element (SPBSET)\nStairwell Element (STRWELL)\nName\nArea\nNumber\nFunction\nPurpose\nDescription\nPosition\nOrientation\nHeidefault\nNAngle\nElevation\nAreaReference\nDFlRHeight\nDClnHeight\nXYOffset\nLabOffset\nUuidia\nBuilding Block Element (BBLOCK)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nInventory List Element (INVLST)\nOpen Space Element (OPENSPACE)\nRef Data Group Element (REFDAT)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nBoundary Element Set Element (SPBSET)\nStairwell Element (STRWELL)"}
{"Headers": "Boundary Line Element (BNDLIN)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nDescription\nDescription of the element\nLevel\nDrawing level\nPosition\nPosition\nOrientation\nOrientation\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nDescription\nDescription of the element\nLevel\nDrawing level\nPosition\nPosition\nOrientation\nOrientation\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nCeiling Element (CEILIN)\nPlaner Ceiling Grid Element (CLNPNGRID)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStairwell Element (STRWELL)\nLoop Element (LOOP)\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nDescription\nDescription of the element\nLevel\nDrawing level\nPosition\nPosition\nOrientation\nOrientation\n\n\n\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nCeiling Element (CEILIN)\nPlaner Ceiling Grid Element (CLNPNGRID)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStairwell Element (STRWELL)\nLoop Element (LOOP)\nName\nArea\nNumber\nFunction\nDescription\nLevel\nPosition\nOrientation\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nCeiling Element (CEILIN)\nPlaner Ceiling Grid Element (CLNPNGRID)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStairwell Element (STRWELL)\nLoop Element (LOOP)"}
{"Headers": "Ceiling Element (CEILIN)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nMatref\nMaterial reference\nPosition\nPosition\nOrientation\nOrientation\nClnType\nCeiling Type\nClnCode\nCeiling Code\nClnHeight\nCeiling Height\nXYOffset\nXY offset\nAreaReference\nArea reference\nClnVoid\nCeiling Void Height\nFireRating\nFire rating\nFiresistance\nFire resistance\nColSchema\nColor Schema\nKnuckl\nTrue if knuckled\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nMatref\nMaterial reference\nPosition\nPosition\nOrientation\nOrientation\nClnType\nCeiling Type\nClnCode\nCeiling Code\nClnHeight\nCeiling Height\nXYOffset\nXY offset\nAreaReference\nArea reference\nClnVoid\nCeiling Void Height\nFireRating\nFire rating\nFiresistance\nFire resistance\nColSchema\nColor Schema\nKnuckl\nTrue if knuckled\nLabOffset\nLabel offset\nDetail Group Element (DETGRP)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nBent Plate Element (BPANEL)\nPlaner Ceiling Grid Element (CLNPNGRID)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nPanel Element (PANEL)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nMatref\nMaterial reference\nPosition\nPosition\nOrientation\nOrientation\nClnType\nCeiling Type\nClnCode\nCeiling Code\nClnHeight\nCeiling Height\nXYOffset\nXY offset\nAreaReference\nArea reference\nClnVoid\nCeiling Void Height\nFireRating\nFire rating\nFiresistance\nFire resistance\nColSchema\nColor Schema\nKnuckl\nTrue if knuckled\nLabOffset\nLabel offset\n\n\n\nDetail Group Element (DETGRP)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nBent Plate Element (BPANEL)\nPlaner Ceiling Grid Element (CLNPNGRID)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nPanel Element (PANEL)\nName\nDescription\nFunction\nPurpose\nNumber\nArea\nMatref\nPosition\nOrientation\nClnType\nClnCode\nClnHeight\nXYOffset\nAreaReference\nClnVoid\nFireRating\nFiresistance\nColSchema\nKnuckl\nLabOffset\nDetail Group Element (DETGRP)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nBent Plate Element (BPANEL)\nPlaner Ceiling Grid Element (CLNPNGRID)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nPanel Element (PANEL)"}
{"Headers": "Grid Cell Positioning Element (CGRDCP)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\ncellid\nCell Identifier\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\ncellid\nCell Identifier\nCeiling Grid Components Element (CLNCGR)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\ncellid\nCell Identifier\n\n\n\nCeiling Grid Components Element (CLNCGR)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nName\nDescription\nFunction\nPurpose\nNumber\ncellid\nCeiling Grid Components Element (CLNCGR)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)"}
{"Headers": "Gridline Positioning Element (CGRDLP)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nGrdLID\nGridline Identifier\nGrdLXPR\nProportion along X gridline from Gridline ID\nGrdLYPR\nProportion along Y gridline from Gridline ID\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nGrdLID\nGridline Identifier\nGrdLXPR\nProportion along X gridline from Gridline ID\nGrdLYPR\nProportion along Y gridline from Gridline ID\nCeiling Grid Components Element (CLNCGR)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nGrdLID\nGridline Identifier\nGrdLXPR\nProportion along X gridline from Gridline ID\nGrdLYPR\nProportion along Y gridline from Gridline ID\n\n\n\nCeiling Grid Components Element (CLNCGR)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nName\nDescription\nFunction\nPurpose\nNumber\nGrdLID\nGrdLXPR\nGrdLYPR\nCeiling Grid Components Element (CLNCGR)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)"}
{"Headers": "Ceiling Grid Components Element (CLNCGR)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPlaner Ceiling Grid Element (CLNPNGRID)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Tile Element (CLNTIL)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\n\n\n\nPlaner Ceiling Grid Element (CLNPNGRID)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Tile Element (CLNTIL)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nName\nDescription\nFunction\nPurpose\nNumber\nPlaner Ceiling Grid Element (CLNPNGRID)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Tile Element (CLNTIL)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)"}
{"Headers": "Ceiling Lattice Element (CLNLATTICE)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPlaner Ceiling Grid Element (CLNPNGRID)\nStructural Generic Section Element (GENSEC)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\n\n\n\nPlaner Ceiling Grid Element (CLNPNGRID)\nStructural Generic Section Element (GENSEC)\nName\nDescription\nFunction\nPurpose\nNumber\nPlaner Ceiling Grid Element (CLNPNGRID)\nStructural Generic Section Element (GENSEC)"}
{"Headers": "Planer Ceiling Grid Element (CLNPNGRID)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nGAngle\nGeneral Angle\nGXYOffset\nGrid XY Offset\nGrdXSpacing\nGrid X Spacing\nGrdYSpacing\nGrid Y Spacing\nColSchema\nColor Schema\nFireRating\nFire rating\nFiresistance\nFire resistance\nKnuckl\nTrue if knuckled\nDCTilThk\nDefault Ceiling Tile Thickness\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nGAngle\nGeneral Angle\nGXYOffset\nGrid XY Offset\nGrdXSpacing\nGrid X Spacing\nGrdYSpacing\nGrid Y Spacing\nColSchema\nColor Schema\nFireRating\nFire rating\nFiresistance\nFire resistance\nKnuckl\nTrue if knuckled\nDCTilThk\nDefault Ceiling Tile Thickness\nLabOffset\nLabel offset\nCeiling Element (CEILIN)\nBoundary Line Element (BNDLIN)\nCeiling Grid Components Element (CLNCGR)\nCeiling Lattice Element (CLNLATTICE)\nRestraint Element (RESTRAINT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nGAngle\nGeneral Angle\nGXYOffset\nGrid XY Offset\nGrdXSpacing\nGrid X Spacing\nGrdYSpacing\nGrid Y Spacing\nColSchema\nColor Schema\nFireRating\nFire rating\nFiresistance\nFire resistance\nKnuckl\nTrue if knuckled\nDCTilThk\nDefault Ceiling Tile Thickness\nLabOffset\nLabel offset\n\n\n\nCeiling Element (CEILIN)\nBoundary Line Element (BNDLIN)\nCeiling Grid Components Element (CLNCGR)\nCeiling Lattice Element (CLNLATTICE)\nRestraint Element (RESTRAINT)\nName\nDescription\nFunction\nPurpose\nNumber\nPosition\nOrientation\nGAngle\nGXYOffset\nGrdXSpacing\nGrdYSpacing\nColSchema\nFireRating\nFiresistance\nKnuckl\nDCTilThk\nLabOffset\nCeiling Element (CEILIN)\nBoundary Line Element (BNDLIN)\nCeiling Grid Components Element (CLNCGR)\nCeiling Lattice Element (CLNLATTICE)\nRestraint Element (RESTRAINT)"}
{"Headers": "Ceiling Tile Element (CLNTIL)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\ncellid\nCell Identifier\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nTAngle\nTile Angle\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\ncellid\nCell Identifier\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nTAngle\nTile Angle\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nLabOffset\nLabel offset\nCeiling Grid Components Element (CLNCGR)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\ncellid\nCell Identifier\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nTAngle\nTile Angle\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nLabOffset\nLabel offset\n\n\n\nCeiling Grid Components Element (CLNCGR)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\ncellid\nSpref\nDesparam\nTAngle\nMatref\nFireRating\nFiresistance\nLabOffset\nCeiling Grid Components Element (CLNCGR)\nElectrical Fitting Element (ELFITTING)\nFire Protection Fitting Element (FPFITTING)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nTemplate Element (TMPLATE)"}
{"Headers": "Constant Thickness Wall Element (CTWALL)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nObstruction\nObstruction level\nHeight\nHeight\nWThickness\nWall thickness\nWJusLine\nWall Justification Line\nVAngle\nAngle from vertical\nBRadius\nBend radius\nRoutReference\nRoute reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nColSchema\nColor Schema\nFireRating\nFire rating\nFiresistance\nFire resistance\nHCRef\nHead connections\nTCRef\nTail connections\nCloseFlag\nTrue if branch is closed\nUuidia\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nObstruction\nObstruction level\nHeight\nHeight\nWThickness\nWall thickness\nWJusLine\nWall Justification Line\nVAngle\nAngle from vertical\nBRadius\nBend radius\nRoutReference\nRoute reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nColSchema\nColor Schema\nFireRating\nFire rating\nFiresistance\nFire resistance\nHCRef\nHead connections\nTCRef\nTail connections\nCloseFlag\nTrue if branch is closed\nUuidia\nUniversally unique identifier\nDetail Group Element (DETGRP)\nStructure Element (STRUCTURE)\nHead Attachment Point Element (HATTA)\nRoute Path Element (RPATH)\nTail Attachment Point Element (TATTA)\nWall Components Element (WLCOMPONENTS)\nWall Features Element (WLFEAT)\nWall Joints Element (WLJNTS)\nWall Profile Set Element (WLPRSE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nObstruction\nObstruction level\nHeight\nHeight\nWThickness\nWall thickness\nWJusLine\nWall Justification Line\nVAngle\nAngle from vertical\nBRadius\nBend radius\nRoutReference\nRoute reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nColSchema\nColor Schema\nFireRating\nFire rating\nFiresistance\nFire resistance\nHCRef\nHead connections\nTCRef\nTail connections\nCloseFlag\nTrue if branch is closed\nUuidia\nUniversally unique identifier\n\n\n\nDetail Group Element (DETGRP)\nStructure Element (STRUCTURE)\nHead Attachment Point Element (HATTA)\nRoute Path Element (RPATH)\nTail Attachment Point Element (TATTA)\nWall Components Element (WLCOMPONENTS)\nWall Features Element (WLFEAT)\nWall Joints Element (WLJNTS)\nWall Profile Set Element (WLPRSE)\nName\nDescription\nFunction\nPurpose\nNumber\nArea\nPosition\nOrientation\nLevel\nObstruction\nHeight\nWThickness\nWJusLine\nVAngle\nBRadius\nRoutReference\nDesparam\nMatref\nColSchema\nFireRating\nFiresistance\nHCRef\nTCRef\nCloseFlag\nUuidia\nDetail Group Element (DETGRP)\nStructure Element (STRUCTURE)\nHead Attachment Point Element (HATTA)\nRoute Path Element (RPATH)\nTail Attachment Point Element (TATTA)\nWall Components Element (WLCOMPONENTS)\nWall Features Element (WLFEAT)\nWall Joints Element (WLJNTS)\nWall Profile Set Element (WLPRSE)"}
{"Headers": "Detail Group Element (DETGRP)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nNumber\nNumber\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\nDUnion\nDRAFT element union detail flag\nName\nName of the element\nNumber\nNumber\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\nDUnion\nDRAFT element union detail flag\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nStairwell Element (STRWELL)\nCeiling Element (CEILIN)\nConstant Thickness Wall Element (CTWALL)\nDoor Element (DOOR)\nElectrical Fitting Element (ELFITTING)\nFixture Element (FIXTUR)\nFloor Covering Element (FLRCOV)\nFire Protection Fitting Element (FPFITTING)\nFurniture Element (FURNIT)\nHandrail Element (HANDRA)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nInsulation Requirements Element (INSURQ)\nLadder Element (LADDER)\nWindow Element (WINDOW)\nName\nName of the element\nNumber\nNumber\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\nDUnion\nDRAFT element union detail flag\n\n\n\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nStairwell Element (STRWELL)\nCeiling Element (CEILIN)\nConstant Thickness Wall Element (CTWALL)\nDoor Element (DOOR)\nElectrical Fitting Element (ELFITTING)\nFixture Element (FIXTUR)\nFloor Covering Element (FLRCOV)\nFire Protection Fitting Element (FPFITTING)\nFurniture Element (FURNIT)\nHandrail Element (HANDRA)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nInsulation Requirements Element (INSURQ)\nLadder Element (LADDER)\nWindow Element (WINDOW)\nName\nNumber\nPurpose\nFunction\nDescription\nDUnion\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nStairwell Element (STRWELL)\nCeiling Element (CEILIN)\nConstant Thickness Wall Element (CTWALL)\nDoor Element (DOOR)\nElectrical Fitting Element (ELFITTING)\nFixture Element (FIXTUR)\nFloor Covering Element (FLRCOV)\nFire Protection Fitting Element (FPFITTING)\nFurniture Element (FURNIT)\nHandrail Element (HANDRA)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nInsulation Requirements Element (INSURQ)\nLadder Element (LADDER)\nWindow Element (WINDOW)"}
{"Headers": "Door Element (DOOR)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpnSize\nOpening size\nWThickness\nWall thickness\nClrSize\nClearance size\nWidth\nWidth\nHeight\nHeight\nHgSide\nHinge side\nSwing\nSwing\nLeafs\nNumber of door leafs\nLThickness\nDoor leaf thickness\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpnSize\nOpening size\nWThickness\nWall thickness\nClrSize\nClearance size\nWidth\nWidth\nHeight\nHeight\nHgSide\nHinge side\nSwing\nSwing\nLeafs\nNumber of door leafs\nLThickness\nDoor leaf thickness\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\nDetail Group Element (DETGRP)\nWall Openings Element (WLOPEN)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpnSize\nOpening size\nWThickness\nWall thickness\nClrSize\nClearance size\nWidth\nWidth\nHeight\nHeight\nHgSide\nHinge side\nSwing\nSwing\nLeafs\nNumber of door leafs\nLThickness\nDoor leaf thickness\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\n\n\n\nDetail Group Element (DETGRP)\nWall Openings Element (WLOPEN)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\nSpref\nDesparam\nMatref\nOpnSize\nWThickness\nClrSize\nWidth\nHeight\nHgSide\nSwing\nLeafs\nLThickness\nFireRating\nFiresistance\nWaterTight\nGasTight\nPosition\nOrientation\nLabOffset\nUuidia\nDetail Group Element (DETGRP)\nWall Openings Element (WLOPEN)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)"}
{"Headers": "Electrical Fitting Element (ELFITTING)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nPosition\nPosition\nOrientation\nOrientation\nMatref\nMaterial reference\nElRating\nElectrical Rating\nOpTemperature\nOperational temperature\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nPosition\nPosition\nOrientation\nOrientation\nMatref\nMaterial reference\nElRating\nElectrical Rating\nOpTemperature\nOperational temperature\nLabOffset\nLabel offset\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nPosition\nPosition\nOrientation\nOrientation\nMatref\nMaterial reference\nElRating\nElectrical Rating\nOpTemperature\nOperational temperature\nLabOffset\nLabel offset\n\n\n\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\nSpref\nMdsysf\nDesparam\nPosition\nOrientation\nMatref\nElRating\nOpTemperature\nLabOffset\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)"}
{"Headers": "External Framework Element (EXTFRM)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nAssTmpReference\nAssembly Template Reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nAssTmpReference\nAssembly Template Reference\nPlatform Element (PLTFRM)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nBent Plate Element (BPANEL)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nAssTmpReference\nAssembly Template Reference\n\n\n\nPlatform Element (PLTFRM)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nBent Plate Element (BPANEL)\nName\nDescription\nFunction\nMatref\nFireRating\nFiresistance\nAssTmpReference\nPlatform Element (PLTFRM)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nBent Plate Element (BPANEL)"}
{"Headers": "Floor Cover Cut Plane Element (FCUTPLANE)", "Content": "Accommodation Element\nName\nName of the element\nNumber\nNumber\nPurpose\nDescription code word\nDescription\nDescription of the element\nFunction\nFunction\nPosition\nPosition\nCutplane\nCutting plane normal\nName\nName of the element\nNumber\nNumber\nPurpose\nDescription code word\nDescription\nDescription of the element\nFunction\nFunction\nPosition\nPosition\nCutplane\nCutting plane normal\nFloor Covering Element (FLRCOV)\nNone\nName\nName of the element\nNumber\nNumber\nPurpose\nDescription code word\nDescription\nDescription of the element\nFunction\nFunction\nPosition\nPosition\nCutplane\nCutting plane normal\n\n\n\nFloor Covering Element (FLRCOV)\nName\nNumber\nPurpose\nDescription\nFunction\nPosition\nCutplane\nFloor Covering Element (FLRCOV)"}
{"Headers": "Fixture Element (FIXTUR)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\n\n\n\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\nSpref\nMdsysf\nDesparam\nMatref\nPosition\nOrientation\nLabOffset\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)"}
{"Headers": "Floor Covering Element (FLRCOV)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nDescription\nDescription of the element\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nObstruction\nObstruction level\nFlrType\nFloor Type\nFlrCode\nFloor Code\nColSchema\nColor Schema\nFireRating\nFire rating\nFiresistance\nFire resistance\nLabOffset\nLabel offset\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nDescription\nDescription of the element\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nObstruction\nObstruction level\nFlrType\nFloor Type\nFlrCode\nFloor Code\nColSchema\nColor Schema\nFireRating\nFire rating\nFiresistance\nFire resistance\nLabOffset\nLabel offset\nDetail Group Element (DETGRP)\nFloor Cover Cut Plane Element (FCUTPLANE)\nFloor Covering Layer Element (FLRLAY)\nLoop Element (LOOP)\nName\nName of the element\nArea\nArea\nNumber\nNumber\nFunction\nFunction\nDescription\nDescription of the element\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nObstruction\nObstruction level\nFlrType\nFloor Type\nFlrCode\nFloor Code\nColSchema\nColor Schema\nFireRating\nFire rating\nFiresistance\nFire resistance\nLabOffset\nLabel offset\n\n\n\nDetail Group Element (DETGRP)\nFloor Cover Cut Plane Element (FCUTPLANE)\nFloor Covering Layer Element (FLRLAY)\nLoop Element (LOOP)\nName\nArea\nNumber\nFunction\nDescription\nPosition\nOrientation\nLevel\nObstruction\nFlrType\nFlrCode\nColSchema\nFireRating\nFiresistance\nLabOffset\nDetail Group Element (DETGRP)\nFloor Cover Cut Plane Element (FCUTPLANE)\nFloor Covering Layer Element (FLRLAY)\nLoop Element (LOOP)"}
{"Headers": "Floor Covering Layer Element (FLRLAY)", "Content": "Accommodation Element\nName\nName of the element\nNumber\nNumber\nPurpose\nDescription code word\nDescription\nDescription of the element\nFunction\nFunction\nMatAngle\nMaterial Lay Angle\nMatref\nMaterial reference\nFllThk\nFloor layer thickness\nFflext\nEdge Extension Around Floor layer\nMatWidth\nMaterial Width\nMatLength\nMaterial Length\nMatover\nMaterial Overlap\nName\nName of the element\nNumber\nNumber\nPurpose\nDescription code word\nDescription\nDescription of the element\nFunction\nFunction\nMatAngle\nMaterial Lay Angle\nMatref\nMaterial reference\nFllThk\nFloor layer thickness\nFflext\nEdge Extension Around Floor layer\nMatWidth\nMaterial Width\nMatLength\nMaterial Length\nMatover\nMaterial Overlap\nFloor Covering Element (FLRCOV)\nNone\nName\nName of the element\nNumber\nNumber\nPurpose\nDescription code word\nDescription\nDescription of the element\nFunction\nFunction\nMatAngle\nMaterial Lay Angle\nMatref\nMaterial reference\nFllThk\nFloor layer thickness\nFflext\nEdge Extension Around Floor layer\nMatWidth\nMaterial Width\nMatLength\nMaterial Length\nMatover\nMaterial Overlap\n\n\n\nFloor Covering Element (FLRCOV)\nName\nNumber\nPurpose\nDescription\nFunction\nMatAngle\nMatref\nFllThk\nFflext\nMatWidth\nMatLength\nMatover\nFloor Covering Element (FLRCOV)"}
{"Headers": "Fire Protection Fitting Element (FPFITTING)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nHazard\nHazard\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nHazard\nHazard\nLabOffset\nLabel offset\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nFixing Element (FIXING)\nDesign Ppoint/Pline Set Element (DPSET)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nHazard\nHazard\nLabOffset\nLabel offset\n\n\n\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nFixing Element (FIXING)\nDesign Ppoint/Pline Set Element (DPSET)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\nPosition\nOrientation\nSpref\nMdsysf\nDesparam\nMatref\nHazard\nLabOffset\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nFixing Element (FIXING)\nDesign Ppoint/Pline Set Element (DPSET)\nTemplate Element (TMPLATE)"}
{"Headers": "Furniture Element (FURNIT)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\n\n\n\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\nSpref\nDesparam\nMatref\nPosition\nOrientation\nLabOffset\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)"}
{"Headers": "Grid Plane Element (GRIDCY)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nRadius\nRadius\nLevel\nDrawing level\nLvisibility\nVisibility flag\nIDPlane\nID Plane\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nRadius\nRadius\nLevel\nDrawing level\nLvisibility\nVisibility flag\nIDPlane\nID Plane\nUuid\nUniversally unique identifier\nGrid Faces Element (GRIDFACES)\nReference Grid Arc Element (REFGAR)\nReference Grid Line Element (REFGLN)\nName\nName of the element\nDescription\nDescription of the element\nRadius\nRadius\nLevel\nDrawing level\nLvisibility\nVisibility flag\nIDPlane\nID Plane\nUuid\nUniversally unique identifier\n\n\n\nGrid Faces Element (GRIDFACES)\nReference Grid Arc Element (REFGAR)\nReference Grid Line Element (REFGLN)\nName\nDescription\nRadius\nLevel\nLvisibility\nIDPlane\nUuid\nGrid Faces Element (GRIDFACES)\nReference Grid Arc Element (REFGAR)\nReference Grid Line Element (REFGLN)"}
{"Headers": "Grid Plane Element (GRIDPL)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nRadiPlane\nRadial plane flag\nLvisibility\nVisibility flag\nIDPlane\nID Plane\nPLLIM\nlimited plane\nXYSIZE\nsize array for grids\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nRadiPlane\nRadial plane flag\nLvisibility\nVisibility flag\nIDPlane\nID Plane\nPLLIM\nlimited plane\nXYSIZE\nsize array for grids\nUuid\nUniversally unique identifier\nGrid Elevations Element (GRIDELEVATION)\nGrid Faces Element (GRIDFACES)\nReference Grid Arc Element (REFGAR)\nReference Grid Line Element (REFGLN)\nName\nName of the element\nDescription\nDescription of the element\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nRadiPlane\nRadial plane flag\nLvisibility\nVisibility flag\nIDPlane\nID Plane\nPLLIM\nlimited plane\nXYSIZE\nsize array for grids\nUuid\nUniversally unique identifier\n\n\n\nGrid Elevations Element (GRIDELEVATION)\nGrid Faces Element (GRIDFACES)\nReference Grid Arc Element (REFGAR)\nReference Grid Line Element (REFGLN)\nName\nDescription\nPosition\nOrientation\nLevel\nRadiPlane\nLvisibility\nIDPlane\nPLLIM\nXYSIZE\nUuid\nGrid Elevations Element (GRIDELEVATION)\nGrid Faces Element (GRIDFACES)\nReference Grid Arc Element (REFGAR)\nReference Grid Line Element (REFGLN)"}
{"Headers": "Handrail Element (HANDRA)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nRailHeight\nHeights of rails measured from path\nPostSpacing\nDefault post spacing\nTangOffset\nTangent offset\nEPostOffset\nEnd post tangent offset\nPostOffset\nVertical post offset from the routing path\nShowKPlate\nShow kickplate in default representation\nBRadius\nBend radius\nRoutReference\nRoute reference\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nHCRef\nHead connections\nTCRef\nTail connections\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nASLStandard\nASL Standard Reference\nASLSbStandard\nASL Substandard Reference\nCloseFlag\nTrue if branch is closed\nAssTmpReference\nAssembly Template Reference\nBuilt\nBuilt/Unbuilt flag\nShop\nShop/Site flag\nUuidia\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nRailHeight\nHeights of rails measured from path\nPostSpacing\nDefault post spacing\nTangOffset\nTangent offset\nEPostOffset\nEnd post tangent offset\nPostOffset\nVertical post offset from the routing path\nShowKPlate\nShow kickplate in default representation\nBRadius\nBend radius\nRoutReference\nRoute reference\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nHCRef\nHead connections\nTCRef\nTail connections\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nASLStandard\nASL Standard Reference\nASLSbStandard\nASL Substandard Reference\nCloseFlag\nTrue if branch is closed\nAssTmpReference\nAssembly Template Reference\nBuilt\nBuilt/Unbuilt flag\nShop\nShop/Site flag\nUuidia\nUniversally unique identifier\nDetail Group Element (DETGRP)\nFramework Element (FRMWORK)\nLadder Element (LADDER)\nPlatform Element (PLTFRM)\nStair Flight Element (STRFLT)\nStair Landing Element (STRLNG)\nStructure Element (STRUCTURE)\nSubframework Element (SBFRAMEWORK)\nDesign Dataset Element (DDSE)\nHead Attachment Point Element (HATTA)\nHandrail Features Element (HRFEAT)\nKickplate Set Element (HRKPSE)\nHandrail Panel Set Element (HRPNSE)\nPost Set Element (POSTSE)\nRail Set Element (RAILSET)\nRoute Path Element (RPATH)\nTail Attachment Point Element (TATTA)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nRailHeight\nHeights of rails measured from path\nPostSpacing\nDefault post spacing\nTangOffset\nTangent offset\nEPostOffset\nEnd post tangent offset\nPostOffset\nVertical post offset from the routing path\nShowKPlate\nShow kickplate in default representation\nBRadius\nBend radius\nRoutReference\nRoute reference\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nHCRef\nHead connections\nTCRef\nTail connections\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nASLStandard\nASL Standard Reference\nASLSbStandard\nASL Substandard Reference\nCloseFlag\nTrue if branch is closed\nAssTmpReference\nAssembly Template Reference\nBuilt\nBuilt/Unbuilt flag\nShop\nShop/Site flag\nUuidia\nUniversally unique identifier\n\n\n\nDetail Group Element (DETGRP)\nFramework Element (FRMWORK)\nLadder Element (LADDER)\nPlatform Element (PLTFRM)\nStair Flight Element (STRFLT)\nStair Landing Element (STRLNG)\nStructure Element (STRUCTURE)\nSubframework Element (SBFRAMEWORK)\nDesign Dataset Element (DDSE)\nHead Attachment Point Element (HATTA)\nHandrail Features Element (HRFEAT)\nKickplate Set Element (HRKPSE)\nHandrail Panel Set Element (HRPNSE)\nPost Set Element (POSTSE)\nRail Set Element (RAILSET)\nRoute Path Element (RPATH)\nTail Attachment Point Element (TATTA)\nName\nDescription\nFunction\nPurpose\nNumber\nArea\nPosition\nOrientation\nLevel\nRailHeight\nPostSpacing\nTangOffset\nEPostOffset\nPostOffset\nShowKPlate\nBRadius\nRoutReference\nMatref\nFireRating\nFiresistance\nHCRef\nTCRef\nDcrfarray\nASLStandard\nASLSbStandard\nCloseFlag\nAssTmpReference\nBuilt\nShop\nUuidia\nDetail Group Element (DETGRP)\nFramework Element (FRMWORK)\nLadder Element (LADDER)\nPlatform Element (PLTFRM)\nStair Flight Element (STRFLT)\nStair Landing Element (STRLNG)\nStructure Element (STRUCTURE)\nSubframework Element (SBFRAMEWORK)\nDesign Dataset Element (DDSE)\nHead Attachment Point Element (HATTA)\nHandrail Features Element (HRFEAT)\nKickplate Set Element (HRKPSE)\nHandrail Panel Set Element (HRPNSE)\nPost Set Element (POSTSE)\nRail Set Element (RAILSET)\nRoute Path Element (RPATH)\nTail Attachment Point Element (TATTA)"}
{"Headers": "Height Change Node Element (HNODE)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nConnReference\nReferences to other element\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nHeight\nHeight\nSLOPEFlag\nSLOPEF (True if its a sloping wall else step change)\nTRIMTYPE\nCTWALL TRIM TYPE\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nConnReference\nReferences to other element\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nHeight\nHeight\nSLOPEFlag\nSLOPEF (True if its a sloping wall else step change)\nTRIMTYPE\nCTWALL TRIM TYPE\nHeight Change Feature Element (HTFEAT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nConnReference\nReferences to other element\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nHeight\nHeight\nSLOPEFlag\nSLOPEF (True if its a sloping wall else step change)\nTRIMTYPE\nCTWALL TRIM TYPE\n\n\n\nHeight Change Feature Element (HTFEAT)\nName\nDescription\nFunction\nSpref\nPurpose\nNumber\nArea\nConnReference\nPosRef\nZdistance\nPkdistance\nHeight\nSLOPEFlag\nTRIMTYPE\nHeight Change Feature Element (HTFEAT)"}
{"Headers": "Handrail Features Element (HRFEAT)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Gate Element (HRGATE)\nRoute Attachment Point Element (RATTA)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\n\n\n\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Gate Element (HRGATE)\nRoute Attachment Point Element (RATTA)\nName\nDescription\nFunction\nMatref\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Gate Element (HRGATE)\nRoute Attachment Point Element (RATTA)"}
{"Headers": "Handrail Gate Element (HRGATE)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpnSize\nOpening size\nClrSize\nClearance size\nWidth\nWidth\nHeight\nHeight\nHgSide\nHinge side\nSwing\nSwing\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nHRJusLine\nHandrail Justification Line\nAssTmpReference\nAssembly Template Reference\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpnSize\nOpening size\nClrSize\nClearance size\nWidth\nWidth\nHeight\nHeight\nHgSide\nHinge side\nSwing\nSwing\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nHRJusLine\nHandrail Justification Line\nAssTmpReference\nAssembly Template Reference\nLabOffset\nLabel offset\nHandrail Features Element (HRFEAT)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nStructural Generic Section Element (GENSEC)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpnSize\nOpening size\nClrSize\nClearance size\nWidth\nWidth\nHeight\nHeight\nHgSide\nHinge side\nSwing\nSwing\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nHRJusLine\nHandrail Justification Line\nAssTmpReference\nAssembly Template Reference\nLabOffset\nLabel offset\n\n\n\nHandrail Features Element (HRFEAT)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nStructural Generic Section Element (GENSEC)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\nSpref\nDesparam\nMatref\nOpnSize\nClrSize\nWidth\nHeight\nHgSide\nSwing\nPosRef\nZdistance\nPkdistance\nHRJusLine\nAssTmpReference\nLabOffset\nHandrail Features Element (HRFEAT)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nStructural Generic Section Element (GENSEC)\nTemplate Element (TMPLATE)"}
{"Headers": "Kickplate Set Element (HRKPSE)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nKickplate Element (KICKPL)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\n\n\n\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nKickplate Element (KICKPL)\nName\nDescription\nFunction\nMatref\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nKickplate Element (KICKPL)"}
{"Headers": "Handrail Panel Element (HRPANE)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nEndPosition\nEnd Position\nXoffset\nX-offset\nZoffset\nZ-offset\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nHRJusLine\nHandrail Justification Line\nPaneSize\nPanel Size\nLabOffset\nLabel offset\nBangle\nBeta angle\nRise\nTread Rise\nAssTmpReference\nAssembly Template Reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nEndPosition\nEnd Position\nXoffset\nX-offset\nZoffset\nZ-offset\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nHRJusLine\nHandrail Justification Line\nPaneSize\nPanel Size\nLabOffset\nLabel offset\nBangle\nBeta angle\nRise\nTread Rise\nAssTmpReference\nAssembly Template Reference\nHandrail Panel Set Element (HRPNSE)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nEndPosition\nEnd Position\nXoffset\nX-offset\nZoffset\nZ-offset\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nHRJusLine\nHandrail Justification Line\nPaneSize\nPanel Size\nLabOffset\nLabel offset\nBangle\nBeta angle\nRise\nTread Rise\nAssTmpReference\nAssembly Template Reference\n\n\n\nHandrail Panel Set Element (HRPNSE)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\nSpref\nDesparam\nMatref\nEndPosition\nXoffset\nZoffset\nPosRef\nZdistance\nPkdistance\nHRJusLine\nPaneSize\nLabOffset\nBangle\nRise\nAssTmpReference\nHandrail Panel Set Element (HRPNSE)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)"}
{"Headers": "Handrail Panel Set Element (HRPNSE)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Panel Element (HRPANE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\n\n\n\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Panel Element (HRPANE)\nName\nDescription\nFunction\nMatref\nFireRating\nFiresistance\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Panel Element (HRPANE)"}
{"Headers": "Handrail Post Element (HRPOST)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nZoffset\nZ-offset\nHeight\nHeight\nPosRef\nReference to point\nPkdistance\nProportional distance along Pline\nZdistance\nPosition in section\nXoffset\nX-offset\nVertDirection\nVERTDI (true if Z axe is vertical)\nHRJusLine\nHandrail Justification Line\nBangle\nBeta angle\nLength\nLength\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nAssTmpReference\nAssembly Template Reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nZoffset\nZ-offset\nHeight\nHeight\nPosRef\nReference to point\nPkdistance\nProportional distance along Pline\nZdistance\nPosition in section\nXoffset\nX-offset\nVertDirection\nVERTDI (true if Z axe is vertical)\nHRJusLine\nHandrail Justification Line\nBangle\nBeta angle\nLength\nLength\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nAssTmpReference\nAssembly Template Reference\nPost Set Element (POSTSE)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nZoffset\nZ-offset\nHeight\nHeight\nPosRef\nReference to point\nPkdistance\nProportional distance along Pline\nZdistance\nPosition in section\nXoffset\nX-offset\nVertDirection\nVERTDI (true if Z axe is vertical)\nHRJusLine\nHandrail Justification Line\nBangle\nBeta angle\nLength\nLength\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nAssTmpReference\nAssembly Template Reference\n\n\n\nPost Set Element (POSTSE)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\nSpref\nDesparam\nMatref\nZoffset\nHeight\nPosRef\nPkdistance\nZdistance\nXoffset\nVertDirection\nHRJusLine\nBangle\nLength\nDrnstart\nDrnend\nAssTmpReference\nPost Set Element (POSTSE)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)"}
{"Headers": "Handrail Termination Element (HRTERM)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nZoffset\nZ-offset\nHeight\nHeight\nPosRef\nReference to point\nPkdistance\nProportional distance along Pline\nZdistance\nPosition in section\nXoffset\nX-offset\nVertDirection\nVERTDI (true if Z axe is vertical)\nHRJusLine\nHandrail Justification Line\nBangle\nBeta angle\nLength\nLength\nAssTmpReference\nAssembly Template Reference\nAngle\nAngle\nRAILTRim\nRail Trim\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nZoffset\nZ-offset\nHeight\nHeight\nPosRef\nReference to point\nPkdistance\nProportional distance along Pline\nZdistance\nPosition in section\nXoffset\nX-offset\nVertDirection\nVERTDI (true if Z axe is vertical)\nHRJusLine\nHandrail Justification Line\nBangle\nBeta angle\nLength\nLength\nAssTmpReference\nAssembly Template Reference\nAngle\nAngle\nRAILTRim\nRail Trim\nRail Set Element (RAILSET)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nZoffset\nZ-offset\nHeight\nHeight\nPosRef\nReference to point\nPkdistance\nProportional distance along Pline\nZdistance\nPosition in section\nXoffset\nX-offset\nVertDirection\nVERTDI (true if Z axe is vertical)\nHRJusLine\nHandrail Justification Line\nBangle\nBeta angle\nLength\nLength\nAssTmpReference\nAssembly Template Reference\nAngle\nAngle\nRAILTRim\nRail Trim\n\n\n\nRail Set Element (RAILSET)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\nSpref\nDesparam\nMatref\nZoffset\nHeight\nPosRef\nPkdistance\nZdistance\nXoffset\nVertDirection\nHRJusLine\nBangle\nLength\nAssTmpReference\nAngle\nRAILTRim\nRail Set Element (RAILSET)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)"}
{"Headers": "Height Change Feature Element (HTFEAT)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nNone\nHeight Change Node Element (HNODE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nHeight Change Node Element (HNODE)\nName\nDescription\nFunction\nHeight Change Node Element (HNODE)"}
{"Headers": "HVAC Fitting Element (HVACFITTING)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nCref\nConnection reference\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpTemperature\nOperational temperature\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nCref\nConnection reference\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpTemperature\nOperational temperature\nLabOffset\nLabel offset\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nCref\nConnection reference\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpTemperature\nOperational temperature\nLabOffset\nLabel offset\n\n\n\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nAttributes\nName\nDescription\nFunction\nPurpose\nNumber\nPosition\nOrientation\nCref\nSpref\nMdsysf\nDesparam\nMatref\nOpTemperature\nLabOffset\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)"}
{"Headers": "Information Fitting Element (INFITTING)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nInfotext\nInfotext\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nInfotext\nInfotext\nLabOffset\nLabel offset\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nSpref\nComponent spec reference\nMdsysf\nReference Array of Model and Design Elements\nDesparam\nDesign parameters\nMatref\nMaterial reference\nInfotext\nInfotext\nLabOffset\nLabel offset\n\n\n\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\nPosition\nOrientation\nSpref\nMdsysf\nDesparam\nMatref\nInfotext\nLabOffset\nCeiling Element (CEILIN)\nGrid Cell Positioning Element (CGRDCP)\nGridline Positioning Element (CGRDLP)\nCeiling Grid Components Element (CLNCGR)\nCeiling Tile Element (CLNTIL)\nDetail Group Element (DETGRP)\nWall Fittings Element (WLFITTING)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)"}
{"Headers": "Insulation Requirements Element (INSURQ)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nNumber\nNumber\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nInsuType\nInsulation type\nDINThickness\nDefault insulation thickness\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nObstruction\nObstruction level\nHeidefault\nDefault Height value\nFireRating\nFire rating\nFiresistance\nFire resistance\nPinDensity\nPin Density\nMatref\nMaterial reference\nIspec\nInsulation spec reference\nLabOffset\nLabel offset\nName\nName of the element\nNumber\nNumber\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nInsuType\nInsulation type\nDINThickness\nDefault insulation thickness\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nObstruction\nObstruction level\nHeidefault\nDefault Height value\nFireRating\nFire rating\nFiresistance\nFire resistance\nPinDensity\nPin Density\nMatref\nMaterial reference\nIspec\nInsulation spec reference\nLabOffset\nLabel offset\nDetail Group Element (DETGRP)\nLoop Element (LOOP)\nName\nName of the element\nNumber\nNumber\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nInsuType\nInsulation type\nDINThickness\nDefault insulation thickness\nPosition\nPosition\nOrientation\nOrientation\nLevel\nDrawing level\nObstruction\nObstruction level\nHeidefault\nDefault Height value\nFireRating\nFire rating\nFiresistance\nFire resistance\nPinDensity\nPin Density\nMatref\nMaterial reference\nIspec\nInsulation spec reference\nLabOffset\nLabel offset\n\n\n\nDetail Group Element (DETGRP)\nLoop Element (LOOP)\nName\nNumber\nDescription\nFunction\nPurpose\nInsuType\nDINThickness\nPosition\nOrientation\nLevel\nObstruction\nHeidefault\nFireRating\nFiresistance\nPinDensity\nMatref\nIspec\nLabOffset\nDetail Group Element (DETGRP)\nLoop Element (LOOP)"}
{"Headers": "Platform Internal Framework Element (INTFRM)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nGAngle\nGeneral Angle\nGXYOffset\nGrid XY Offset\nMatref\nMaterial reference\nGrdXSpacing\nGrid X Spacing\nGrdYSpacing\nGrid Y Spacing\nFireRating\nFire rating\nFiresistance\nFire resistance\nGrdPosition\nGrid Position\nGrdDirection\nGrid direction\nAssTmpReference\nAssembly Template Reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nGAngle\nGeneral Angle\nGXYOffset\nGrid XY Offset\nMatref\nMaterial reference\nGrdXSpacing\nGrid X Spacing\nGrdYSpacing\nGrid Y Spacing\nFireRating\nFire rating\nFiresistance\nFire resistance\nGrdPosition\nGrid Position\nGrdDirection\nGrid direction\nAssTmpReference\nAssembly Template Reference\nPlatform Element (PLTFRM)\nBent Plate Element (BPANEL)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nGAngle\nGeneral Angle\nGXYOffset\nGrid XY Offset\nMatref\nMaterial reference\nGrdXSpacing\nGrid X Spacing\nGrdYSpacing\nGrid Y Spacing\nFireRating\nFire rating\nFiresistance\nFire resistance\nGrdPosition\nGrid Position\nGrdDirection\nGrid direction\nAssTmpReference\nAssembly Template Reference\n\n\n\nPlatform Element (PLTFRM)\nBent Plate Element (BPANEL)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nName\nDescription\nFunction\nPurpose\nNumber\nPosition\nOrientation\nGAngle\nGXYOffset\nMatref\nGrdXSpacing\nGrdYSpacing\nFireRating\nFiresistance\nGrdPosition\nGrdDirection\nAssTmpReference\nPlatform Element (PLTFRM)\nBent Plate Element (BPANEL)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)"}
{"Headers": "Inventory Element (INVELEMENT)", "Content": "Accommodation Element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nSpInRef\nReference to external inventory element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nSpInRef\nReference to external inventory element\nInventory List Element (INVLST)\nNone\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nSpInRef\nReference to external inventory element\n\n\n\nInventory List Element (INVLST)\nName\nPurpose\nFunction\nSpInRef\nInventory List Element (INVLST)"}
{"Headers": "Inventory List Element (INVLST)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStairwell Element (STRWELL)\nInventory Element (INVELEMENT)\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\n\n\n\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStairwell Element (STRWELL)\nInventory Element (INVELEMENT)\nAttributes\nName\nPurpose\nFunction\nDescription\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStairwell Element (STRWELL)\nInventory Element (INVELEMENT)"}
{"Headers": "Kickplate Element (KICKPL)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nBangle\nBeta angle\nXoffset\nX-offset\nZoffset\nZ-offset\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nBendCorners\nBend corners - true if fillet should be applied to the corners of kickplate\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nSPkdistance\nProportional distance of start point along Pline\nSzdistance\nStart load point in section\nEndRef\nCable End reference\nEPkdistance\nProportional distance of end point along Pline\nEzdistance\nEnd load point in section\nAssTmpReference\nAssembly Template Reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nBangle\nBeta angle\nXoffset\nX-offset\nZoffset\nZ-offset\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nBendCorners\nBend corners - true if fillet should be applied to the corners of kickplate\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nSPkdistance\nProportional distance of start point along Pline\nSzdistance\nStart load point in section\nEndRef\nCable End reference\nEPkdistance\nProportional distance of end point along Pline\nEzdistance\nEnd load point in section\nAssTmpReference\nAssembly Template Reference\nKickplate Set Element (HRKPSE)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nBangle\nBeta angle\nXoffset\nX-offset\nZoffset\nZ-offset\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nBendCorners\nBend corners - true if fillet should be applied to the corners of kickplate\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nSPkdistance\nProportional distance of start point along Pline\nSzdistance\nStart load point in section\nEndRef\nCable End reference\nEPkdistance\nProportional distance of end point along Pline\nEzdistance\nEnd load point in section\nAssTmpReference\nAssembly Template Reference\n\n\n\nKickplate Set Element (HRKPSE)\nAttributes\nName\nDescription\nFunction\nSpref\nDesparam\nMatref\nLevel\nBangle\nXoffset\nZoffset\nLMirror\nJusline\nBendCorners\nYdirection\nDrnstart\nDrnend\nStaRef\nSPkdistance\nSzdistance\nEndRef\nEPkdistance\nEzdistance\nAssTmpReference\nKickplate Set Element (HRKPSE)"}
{"Headers": "Open Features Element (OPENFE)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPlatform Opening Element (PLOPEN)\nRoute Attachment Point Element (RATTA)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nPlatform Opening Element (PLOPEN)\nRoute Attachment Point Element (RATTA)\nName\nDescription\nFunction\nPlatform Opening Element (PLOPEN)\nRoute Attachment Point Element (RATTA)"}
{"Headers": "Open Space Element (OPENSPACE)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nArea\nArea\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nNAngle\nNorth angle\nFlrHeight\nFloor Height\nXYOffset\nXY offset\nAreaReference\nArea reference\nTemperature\nTemperature\nMaxTemperature\nMaximum Temperature\nMinTemperature\nMinimum Temperature\nHumidity\nDesign Humidity\nMaxHumidity\nMaximum Humidity\nMinHumidity\nMinimum Humidity\nMaxWater\nMaximum Water Level\nAirChangeRate\nAir Change Rate\nOccupancy\nOccupancy\nLighting\nLighting requirements\nFireRating\nFire rating\nFiresistance\nFire resistance\nMaxArea\nMaximum area\nMinArea\nMinimum area\nMaxVolume\nMaximum Volume\nMinVolume\nMinimum Volume\nColSchema\nColor Schema\nDFlrType\nDefault Floor Type\nDFlrCode\nDefault Floor Code\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nArea\nArea\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nNAngle\nNorth angle\nFlrHeight\nFloor Height\nXYOffset\nXY offset\nAreaReference\nArea reference\nTemperature\nTemperature\nMaxTemperature\nMaximum Temperature\nMinTemperature\nMinimum Temperature\nHumidity\nDesign Humidity\nMaxHumidity\nMaximum Humidity\nMinHumidity\nMinimum Humidity\nMaxWater\nMaximum Water Level\nAirChangeRate\nAir Change Rate\nOccupancy\nOccupancy\nLighting\nLighting requirements\nFireRating\nFire rating\nFiresistance\nFire resistance\nMaxArea\nMaximum area\nMinArea\nMinimum area\nMaxVolume\nMaximum Volume\nMinVolume\nMinimum Volume\nColSchema\nColor Schema\nDFlrType\nDefault Floor Type\nDFlrCode\nDefault Floor Code\nLabOffset\nLabel offset\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nRoom Element (ROOM)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nInventory List Element (INVLST)\nRef Data Group Element (REFDAT)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nBoundary Element Set Element (SPBSET)\nStairwell Element (STRWELL)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nArea\nArea\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nNAngle\nNorth angle\nFlrHeight\nFloor Height\nXYOffset\nXY offset\nAreaReference\nArea reference\nTemperature\nTemperature\nMaxTemperature\nMaximum Temperature\nMinTemperature\nMinimum Temperature\nHumidity\nDesign Humidity\nMaxHumidity\nMaximum Humidity\nMinHumidity\nMinimum Humidity\nMaxWater\nMaximum Water Level\nAirChangeRate\nAir Change Rate\nOccupancy\nOccupancy\nLighting\nLighting requirements\nFireRating\nFire rating\nFiresistance\nFire resistance\nMaxArea\nMaximum area\nMinArea\nMinimum area\nMaxVolume\nMaximum Volume\nMinVolume\nMinimum Volume\nColSchema\nColor Schema\nDFlrType\nDefault Floor Type\nDFlrCode\nDefault Floor Code\nLabOffset\nLabel offset\n\n\n\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nRoom Element (ROOM)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nInventory List Element (INVLST)\nRef Data Group Element (REFDAT)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nBoundary Element Set Element (SPBSET)\nStairwell Element (STRWELL)\nAttributes\nName\nDescription\nFunction\nPurpose\nArea\nNumber\nPosition\nOrientation\nHeidefault\nNAngle\nFlrHeight\nXYOffset\nAreaReference\nTemperature\nMaxTemperature\nMinTemperature\nHumidity\nMaxHumidity\nMinHumidity\nMaxWater\nAirChangeRate\nOccupancy\nLighting\nFireRating\nFiresistance\nMaxArea\nMinArea\nMaxVolume\nMinVolume\nColSchema\nDFlrType\nDFlrCode\nLabOffset\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nRoom Element (ROOM)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nInventory List Element (INVLST)\nRef Data Group Element (REFDAT)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nBoundary Element Set Element (SPBSET)\nStairwell Element (STRWELL)"}
{"Headers": "Platform Features Element (PLFEAT)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPlatform Element (PLTFRM)\nFixing Element (FIXING)\nPlatform Opening Element (PLOPEN)\nRoute Attachment Point Element (RATTA)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nPlatform Element (PLTFRM)\nFixing Element (FIXING)\nPlatform Opening Element (PLOPEN)\nRoute Attachment Point Element (RATTA)\nName\nDescription\nFunction\nPlatform Element (PLTFRM)\nFixing Element (FIXING)\nPlatform Opening Element (PLOPEN)\nRoute Attachment Point Element (RATTA)"}
{"Headers": "Platform Opening Element (PLOPEN)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nPlatform Features Element (PLFEAT)\nOpen Features Element (OPENFE)\nRoute Path Element (RPATH)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\n\n\n\nPlatform Features Element (PLFEAT)\nOpen Features Element (OPENFE)\nRoute Path Element (RPATH)\nName\nDescription\nFunction\nWJusLine\nPurpose\nNumber\nArea\nPosition\nOrientation\nPosRef\nZdistance\nPkdistance\nPlatform Features Element (PLFEAT)\nOpen Features Element (OPENFE)\nRoute Path Element (RPATH)"}
{"Headers": "Platform Element (PLTFRM)", "Content": "Accommodation Element\nPrimary Element\nAttributes\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nLevel\nDrawing level\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nPosition\nPosition\nOrientation\nOrientation\nThickn\nThickness\nHeadroom\nHeadroom\nBRadius\nBend radius\nRoutReference\nRoute reference\nDesparam\nDesign parameters\nCloseFlag\nTrue if branch is closed\nASLStandard\nASL Standard Reference\nASLSbStandard\nASL Substandard Reference\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nAssTmpReference\nAssembly Template Reference\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nLevel\nDrawing level\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nPosition\nPosition\nOrientation\nOrientation\nThickn\nThickness\nHeadroom\nHeadroom\nBRadius\nBend radius\nRoutReference\nRoute reference\nDesparam\nDesign parameters\nCloseFlag\nTrue if branch is closed\nASLStandard\nASL Standard Reference\nASLSbStandard\nASL Substandard Reference\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nAssTmpReference\nAssembly Template Reference\nLabOffset\nLabel offset\nStructure Element (STRUCTURE)\nDesign Dataset Element (DDSE)\nExternal Framework Element (EXTFRM)\nHandrail Element (HANDRA)\nPlatform Internal Framework Element (INTFRM)\nPlatform Features Element (PLFEAT)\nPlating Grid Element (PLTGRD)\nRoute Path Element (RPATH)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nLevel\nDrawing level\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nPosition\nPosition\nOrientation\nOrientation\nThickn\nThickness\nHeadroom\nHeadroom\nBRadius\nBend radius\nRoutReference\nRoute reference\nDesparam\nDesign parameters\nCloseFlag\nTrue if branch is closed\nASLStandard\nASL Standard Reference\nASLSbStandard\nASL Substandard Reference\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nAssTmpReference\nAssembly Template Reference\nLabOffset\nLabel offset\n\n\n\nStructure Element (STRUCTURE)\nDesign Dataset Element (DDSE)\nExternal Framework Element (EXTFRM)\nHandrail Element (HANDRA)\nPlatform Internal Framework Element (INTFRM)\nPlatform Features Element (PLFEAT)\nPlating Grid Element (PLTGRD)\nRoute Path Element (RPATH)\nAttributes\nName\nDescription\nFunction\nPurpose\nNumber\nArea\nLevel\nMatref\nFireRating\nFiresistance\nPosition\nOrientation\nThickn\nHeadroom\nBRadius\nRoutReference\nDesparam\nCloseFlag\nASLStandard\nASLSbStandard\nDcrfarray\nAssTmpReference\nLabOffset\nStructure Element (STRUCTURE)\nDesign Dataset Element (DDSE)\nExternal Framework Element (EXTFRM)\nHandrail Element (HANDRA)\nPlatform Internal Framework Element (INTFRM)\nPlatform Features Element (PLFEAT)\nPlating Grid Element (PLTGRD)\nRoute Path Element (RPATH)"}
{"Headers": "Plating Grid Element (PLTGRD)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nGAngle\nGeneral Angle\nGXYOffset\nGrid XY Offset\nMatref\nMaterial reference\nXoffset\nX-offset\nGrdXSpacing\nGrid X Spacing\nGrdYSpacing\nGrid Y Spacing\nRadiSpacing\nRadius Spacing\nAnglSpacing\nANGLE Spacing\nBNDOFF\nOffset from boundary\nFireRating\nFire rating\nFiresistance\nFire resistance\nLabOffset\nLabel offset\nGrdPosition\nGrid Position\nGrdDirection\nGrid direction\nAssTmpReference\nAssembly Template Reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nGAngle\nGeneral Angle\nGXYOffset\nGrid XY Offset\nMatref\nMaterial reference\nXoffset\nX-offset\nGrdXSpacing\nGrid X Spacing\nGrdYSpacing\nGrid Y Spacing\nRadiSpacing\nRadius Spacing\nAnglSpacing\nANGLE Spacing\nBNDOFF\nOffset from boundary\nFireRating\nFire rating\nFiresistance\nFire resistance\nLabOffset\nLabel offset\nGrdPosition\nGrid Position\nGrdDirection\nGrid direction\nAssTmpReference\nAssembly Template Reference\nPlatform Element (PLTFRM)\nBent Plate Element (BPANEL)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nGAngle\nGeneral Angle\nGXYOffset\nGrid XY Offset\nMatref\nMaterial reference\nXoffset\nX-offset\nGrdXSpacing\nGrid X Spacing\nGrdYSpacing\nGrid Y Spacing\nRadiSpacing\nRadius Spacing\nAnglSpacing\nANGLE Spacing\nBNDOFF\nOffset from boundary\nFireRating\nFire rating\nFiresistance\nFire resistance\nLabOffset\nLabel offset\nGrdPosition\nGrid Position\nGrdDirection\nGrid direction\nAssTmpReference\nAssembly Template Reference\n\n\n\nPlatform Element (PLTFRM)\nBent Plate Element (BPANEL)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nName\nDescription\nFunction\nPurpose\nNumber\nPosition\nOrientation\nGAngle\nGXYOffset\nMatref\nXoffset\nGrdXSpacing\nGrdYSpacing\nRadiSpacing\nAnglSpacing\nBNDOFF\nFireRating\nFiresistance\nLabOffset\nGrdPosition\nGrdDirection\nAssTmpReference\nPlatform Element (PLTFRM)\nBent Plate Element (BPANEL)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)"}
{"Headers": "Post Set Element (POSTSE)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Post Element (HRPOST)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\n\n\n\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Post Element (HRPOST)\nName\nDescription\nFunction\nMatref\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Post Element (HRPOST)"}
{"Headers": "Rail Element (RAIL)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nBangle\nBeta angle\nXoffset\nX-offset\nZoffset\nZ-offset\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nSPkdistance\nProportional distance of start point along Pline\nSzdistance\nStart load point in section\nEndRef\nCable End reference\nEPkdistance\nProportional distance of end point along Pline\nEzdistance\nEnd load point in section\nRadsetflag\nRadius set flag - ignore Radius values if FALSE\nAssTmpReference\nAssembly Template Reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nBangle\nBeta angle\nXoffset\nX-offset\nZoffset\nZ-offset\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nSPkdistance\nProportional distance of start point along Pline\nSzdistance\nStart load point in section\nEndRef\nCable End reference\nEPkdistance\nProportional distance of end point along Pline\nEzdistance\nEnd load point in section\nRadsetflag\nRadius set flag - ignore Radius values if FALSE\nAssTmpReference\nAssembly Template Reference\nRail Set Element (RAILSET)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nBangle\nBeta angle\nXoffset\nX-offset\nZoffset\nZ-offset\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nSPkdistance\nProportional distance of start point along Pline\nSzdistance\nStart load point in section\nEndRef\nCable End reference\nEPkdistance\nProportional distance of end point along Pline\nEzdistance\nEnd load point in section\nRadsetflag\nRadius set flag - ignore Radius values if FALSE\nAssTmpReference\nAssembly Template Reference\n\n\n\nRail Set Element (RAILSET)\nName\nDescription\nFunction\nSpref\nDesparam\nMatref\nLevel\nBangle\nXoffset\nZoffset\nLMirror\nJusline\nYdirection\nDrnstart\nDrnend\nStaRef\nSPkdistance\nSzdistance\nEndRef\nEPkdistance\nEzdistance\nRadsetflag\nAssTmpReference\nRail Set Element (RAILSET)"}
{"Headers": "Rail Set Element (RAILSET)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Termination Element (HRTERM)\nRail Element (RAIL)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatref\nMaterial reference\n\n\n\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Termination Element (HRTERM)\nRail Element (RAIL)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nMatref\nHandrail Element (HANDRA)\nRouting Volume Element (RUTVOLUME)\nHandrail Termination Element (HRTERM)\nRail Element (RAIL)\nTemplate Element (TMPLATE)"}
{"Headers": "Route Attachment Point Element (RATTA)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nConnReference\nReferences to other element\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nLevel\nDrawing level\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nConnReference\nReferences to other element\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nLevel\nDrawing level\n\nHandrail Features Element (HRFEAT)\nOpen Features Element (OPENFE)\nPlatform Features Element (PLFEAT)\nWall Features Element (WLFEAT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nConnReference\nReferences to other element\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nLevel\nDrawing level\n\n\n\nHandrail Features Element (HRFEAT)\nOpen Features Element (OPENFE)\nPlatform Features Element (PLFEAT)\nWall Features Element (WLFEAT)\nName\nDescription\nFunction\nPurpose\nNumber\nArea\nConnReference\nPosRef\nZdistance\nPkdistance\nLevel\n\nHandrail Features Element (HRFEAT)\nOpen Features Element (OPENFE)\nPlatform Features Element (PLFEAT)\nWall Features Element (WLFEAT)"}
{"Headers": "Ref Data Group Element (REFDAT)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRef Data Group Element (REFDAT)\nRoom Element (ROOM)\nDrawn Line Element (DRAWING)\nRef Data Group Element (REFDAT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nPosition\nPosition\nOrientation\nOrientation\n\n\n\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRef Data Group Element (REFDAT)\nRoom Element (ROOM)\nDrawn Line Element (DRAWING)\nRef Data Group Element (REFDAT)\nName\nDescription\nFunction\nPurpose\nNumber\nPosition\nOrientation\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRef Data Group Element (REFDAT)\nRoom Element (ROOM)\nDrawn Line Element (DRAWING)\nRef Data Group Element (REFDAT)"}
{"Headers": "Reference Grid Arc Element (REFGAR)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nLvisibility\nVisibility flag\nGrdRef\nGrid reference\nName\nName of the element\nDescription\nDescription of the element\nLvisibility\nVisibility flag\nGrdRef\nGrid reference\nGrid Plane Element (GRIDCY)\nGrid Plane Element (GRIDPL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nLvisibility\nVisibility flag\nGrdRef\nGrid reference\n\n\n\nGrid Plane Element (GRIDCY)\nGrid Plane Element (GRIDPL)\nName\nDescription\nLvisibility\nGrdRef\nGrid Plane Element (GRIDCY)\nGrid Plane Element (GRIDPL)"}
{"Headers": "Reference Grid Line Element (REFGLN)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nLvisibility\nVisibility flag\nGrdRef\nGrid reference\nName\nName of the element\nDescription\nDescription of the element\nLvisibility\nVisibility flag\nGrdRef\nGrid reference\nGrid Plane Element (GRIDCY)\nGrid Plane Element (GRIDPL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nLvisibility\nVisibility flag\nGrdRef\nGrid reference\n\n\n\nGrid Plane Element (GRIDCY)\nGrid Plane Element (GRIDPL)\nName\nDescription\nLvisibility\nGrdRef\nGrid Plane Element (GRIDCY)\nGrid Plane Element (GRIDPL)"}
{"Headers": "Rung Ladder Gate Element (RLGATE)", "Content": "Accommodation Element\nName\nName of the element\nFunction\nFunction\nDescription\nDescription of the element\nPurpose\nDescription code word\nNumber\nNumber\nMatref\nMaterial reference\nLabOffset\nLabel offset\nHgSide\nHinge side\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nAssTmpReference\nAssembly Template Reference\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nName\nName of the element\nFunction\nFunction\nDescription\nDescription of the element\nPurpose\nDescription code word\nNumber\nNumber\nMatref\nMaterial reference\nLabOffset\nLabel offset\nHgSide\nHinge side\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nAssTmpReference\nAssembly Template Reference\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nRung Ladder Cage Element (RLCAGE)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)\nName\nName of the element\nFunction\nFunction\nDescription\nDescription of the element\nPurpose\nDescription code word\nNumber\nNumber\nMatref\nMaterial reference\nLabOffset\nLabel offset\nHgSide\nHinge side\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nAssTmpReference\nAssembly Template Reference\nSpref\nComponent spec reference\nDesparam\nDesign parameters\n\n\n\nRung Ladder Cage Element (RLCAGE)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)\nAttributes\nName\nFunction\nDescription\nPurpose\nNumber\nMatref\nLabOffset\nHgSide\nDcrfarray\nAssTmpReference\nSpref\nDesparam\nRung Ladder Cage Element (RLCAGE)\nBent Plate Element (BPANEL)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nStructural Generic Section Element (GENSEC)\nPanel Element (PANEL)\nTemplate Element (TMPLATE)"}
{"Headers": "Room Element (ROOM)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nNAngle\nNorth angle\nFlrHeight\nFloor Height\nClnHeight\nCeiling Height\nXYOffset\nXY offset\nOccType\nOccupancy Type\nAreaReference\nArea reference\nColSchema\nColor Schema\nTemperature\nTemperature\nMaxTemperature\nMaximum Temperature\nMinTemperature\nMinimum Temperature\nHumidity\nDesign Humidity\nMaxHumidity\nMaximum Humidity\nMinHumidity\nMinimum Humidity\nPressure\nPressure\nMaxPressure\nMaximum Pressure\nMinPressure\nMinimum Pressure\nMaxWater\nMaximum Water Level\nAirChangeRate\nAir Change Rate\nOccupancy\nOccupancy\nLighting\nLighting requirements\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nMaxArea\nMaximum area\nMinArea\nMinimum area\nMaxVolume\nMaximum Volume\nMinVolume\nMinimum Volume\nDDoorSill\nDefault Door Sill\nDWinSill\nDefault Window Sill\nDClnType\nDefault Ceiling Type\nDClnCode\nDefault Ceiling Code\nDFlrType\nDefault Floor Type\nDFlrCode\nDefault Floor Code\nRoomType\nRoom Type\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\nAccident\nAccident level radiation\nProduction\nProduction level radiation\nMaintenance\nMaintenance level radiation\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nNAngle\nNorth angle\nFlrHeight\nFloor Height\nClnHeight\nCeiling Height\nXYOffset\nXY offset\nOccType\nOccupancy Type\nAreaReference\nArea reference\nColSchema\nColor Schema\nTemperature\nTemperature\nMaxTemperature\nMaximum Temperature\nMinTemperature\nMinimum Temperature\nHumidity\nDesign Humidity\nMaxHumidity\nMaximum Humidity\nMinHumidity\nMinimum Humidity\nPressure\nPressure\nMaxPressure\nMaximum Pressure\nMinPressure\nMinimum Pressure\nMaxWater\nMaximum Water Level\nAirChangeRate\nAir Change Rate\nOccupancy\nOccupancy\nLighting\nLighting requirements\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nMaxArea\nMaximum area\nMinArea\nMinimum area\nMaxVolume\nMaximum Volume\nMinVolume\nMinimum Volume\nDDoorSill\nDefault Door Sill\nDWinSill\nDefault Window Sill\nDClnType\nDefault Ceiling Type\nDClnCode\nDefault Ceiling Code\nDFlrType\nDefault Floor Type\nDFlrCode\nDefault Floor Code\nRoomType\nRoom Type\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\nAccident\nAccident level radiation\nProduction\nProduction level radiation\nMaintenance\nMaintenance level radiation\nApplication Data Element (APPLDATA)\nBuilding Level Element (BLEVEL)\nStructure Element (STRUCTURE)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nInventory List Element (INVLST)\nOpen Space Element (OPENSPACE)\nRef Data Group Element (REFDAT)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nBoundary Element Set Element (SPBSET)\nStairwell Element (STRWELL)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nNAngle\nNorth angle\nFlrHeight\nFloor Height\nClnHeight\nCeiling Height\nXYOffset\nXY offset\nOccType\nOccupancy Type\nAreaReference\nArea reference\nColSchema\nColor Schema\nTemperature\nTemperature\nMaxTemperature\nMaximum Temperature\nMinTemperature\nMinimum Temperature\nHumidity\nDesign Humidity\nMaxHumidity\nMaximum Humidity\nMinHumidity\nMinimum Humidity\nPressure\nPressure\nMaxPressure\nMaximum Pressure\nMinPressure\nMinimum Pressure\nMaxWater\nMaximum Water Level\nAirChangeRate\nAir Change Rate\nOccupancy\nOccupancy\nLighting\nLighting requirements\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nMaxArea\nMaximum area\nMinArea\nMinimum area\nMaxVolume\nMaximum Volume\nMinVolume\nMinimum Volume\nDDoorSill\nDefault Door Sill\nDWinSill\nDefault Window Sill\nDClnType\nDefault Ceiling Type\nDClnCode\nDefault Ceiling Code\nDFlrType\nDefault Floor Type\nDFlrCode\nDefault Floor Code\nRoomType\nRoom Type\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\nAccident\nAccident level radiation\nProduction\nProduction level radiation\nMaintenance\nMaintenance level radiation\n\n\n\nApplication Data Element (APPLDATA)\nBuilding Level Element (BLEVEL)\nStructure Element (STRUCTURE)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nInventory List Element (INVLST)\nOpen Space Element (OPENSPACE)\nRef Data Group Element (REFDAT)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nBoundary Element Set Element (SPBSET)\nStairwell Element (STRWELL)\nName\nDescription\nFunction\nPurpose\nNumber\nArea\nPosition\nOrientation\nHeidefault\nNAngle\nFlrHeight\nClnHeight\nXYOffset\nOccType\nAreaReference\nColSchema\nTemperature\nMaxTemperature\nMinTemperature\nHumidity\nMaxHumidity\nMinHumidity\nPressure\nMaxPressure\nMinPressure\nMaxWater\nAirChangeRate\nOccupancy\nLighting\nFireRating\nFiresistance\nWaterTight\nGasTight\nMaxArea\nMinArea\nMaxVolume\nMinVolume\nDDoorSill\nDWinSill\nDClnType\nDClnCode\nDFlrType\nDFlrCode\nRoomType\nLabOffset\nUuidia\nAccident\nProduction\nMaintenance\nApplication Data Element (APPLDATA)\nBuilding Level Element (BLEVEL)\nStructure Element (STRUCTURE)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nInventory List Element (INVLST)\nOpen Space Element (OPENSPACE)\nRef Data Group Element (REFDAT)\nRestricted Area Element (RSTAREA)\nRouting Volume Element (RUTVOLUME)\nBoundary Element Set Element (SPBSET)\nStairwell Element (STRWELL)"}
{"Headers": "Routing Segment Element (RSEG)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nBangle\nBeta angle\nLMirror\nTrue if Mirroring required\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nEndRef\nCable End reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nBangle\nBeta angle\nLMirror\nTrue if Mirroring required\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nEndRef\nCable End reference\nSequence of Segments Element (SEGSEQ)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nBangle\nBeta angle\nLMirror\nTrue if Mirroring required\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nEndRef\nCable End reference\n\n\n\nSequence of Segments Element (SEGSEQ)\nName\nDescription\nFunction\nSpref\nDesparam\nBangle\nLMirror\nYdirection\nDrnstart\nDrnend\nStaRef\nEndRef\nSequence of Segments Element (SEGSEQ)"}
{"Headers": "Restricted Area Element (RSTAREA)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nHazType\nHazard Description\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nAreaReference\nArea reference\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nHazType\nHazard Description\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nAreaReference\nArea reference\nLabOffset\nLabel offset\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nInventory List Element (INVLST)\nBoundary Element Set Element (SPBSET)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nHazType\nHazard Description\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nAreaReference\nArea reference\nLabOffset\nLabel offset\n\n\n\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nInventory List Element (INVLST)\nBoundary Element Set Element (SPBSET)\nAttributes\nName\nDescription\nFunction\nPurpose\nNumber\nArea\nHazType\nPosition\nOrientation\nHeidefault\nAreaReference\nLabOffset\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nInventory List Element (INVLST)\nBoundary Element Set Element (SPBSET)"}
{"Headers": "Routing Volume Element (RUTVOLUME)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nLabOffset\nLabel offset\nMatref\nMaterial reference\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nLabOffset\nLabel offset\nMatref\nMaterial reference\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nHead Attachment Point Element (HATTA)\nHandrail Features Element (HRFEAT)\nKickplate Set Element (HRKPSE)\nHandrail Panel Set Element (HRPNSE)\nPost Set Element (POSTSE)\nRail Set Element (RAILSET)\nRoute Path Element (RPATH)\nTail Attachment Point Element (TATTA)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nLabOffset\nLabel offset\nMatref\nMaterial reference\n\n\n\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nHead Attachment Point Element (HATTA)\nHandrail Features Element (HRFEAT)\nKickplate Set Element (HRKPSE)\nHandrail Panel Set Element (HRPNSE)\nPost Set Element (POSTSE)\nRail Set Element (RAILSET)\nRoute Path Element (RPATH)\nTail Attachment Point Element (TATTA)\nName\nDescription\nFunction\nPurpose\nNumber\nArea\nLabOffset\nMatref\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nHead Attachment Point Element (HATTA)\nHandrail Features Element (HRFEAT)\nKickplate Set Element (HRKPSE)\nHandrail Panel Set Element (HRPNSE)\nPost Set Element (POSTSE)\nRail Set Element (RAILSET)\nRoute Path Element (RPATH)\nTail Attachment Point Element (TATTA)"}
{"Headers": "Sequence of Segments Element (SEGSEQ)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nCable Branch Element (CABLE)\nCable Way Branch Element (CWBRAN)\n\nRouting Segment Element (RSEG)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nCable Branch Element (CABLE)\nCable Way Branch Element (CWBRAN)\nRouting Segment Element (RSEG)\nName\nDescription\nFunction\nCable Branch Element (CABLE)\nCable Way Branch Element (CWBRAN)\n\nRouting Segment Element (RSEG)"}
{"Headers": "Boundary Reference Element (SPBOU)", "Content": "Accommodation Element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nSpBRef\nReference to boundary element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nSpBRef\nReference to boundary element\nNone\nNone\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nSpBRef\nReference to boundary element\n\n\n\nName\nPurpose\nFunction\nSpBRef"}
{"Headers": "Boundary Element Set Element (SPBSET)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStairwell Element (STRWELL)\nNone\nName\nName of the element\nPurpose\nDescription code word\nFunction\nFunction\nDescription\nDescription of the element\n\n\n\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStairwell Element (STRWELL)\nName\nPurpose\nFunction\nDescription\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nRestricted Area Element (RSTAREA)\nStairwell Element (STRWELL)"}
{"Headers": "Stairwell Element (STRWELL)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nStrCon\nStair Configuration\nAreaReference\nArea reference\nColSchema\nColor Schema\nCWidth\nClearance Width\nHeadroom\nHeadroom\nHeadClearance\nHead Clearance\nFThickness\nStair Flight Thickness\nOpHeight\nOperational Height\nOpWidth\nOperational Width\nOpLength\nOperational Length\nAccLevels\nAccess Heights for Stairwell\nLndLevels\nLanding levels from owning element\nLevRfA\nReferences to levels serviced by stairwell\nTemperature\nTemperature\nMaxTemperature\nMaximum Temperature\nMinTemperature\nMinimum Temperature\nHumidity\nDesign Humidity\nMaxHumidity\nMaximum Humidity\nMinHumidity\nMinimum Humidity\nPressure\nPressure\nMaxPressure\nMaximum Pressure\nMinPressure\nMinimum Pressure\nMaxWater\nMaximum Water Level\nAirChangeRate\nAir Change Rate\nOccupancy\nOccupancy\nLighting\nLighting requirements\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nDClnType\nDefault Ceiling Type\nDClnCode\nDefault Ceiling Code\nDFlrType\nDefault Floor Type\nDFlrCode\nDefault Floor Code\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nLabOffset\nLabel offset\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nStrCon\nStair Configuration\nAreaReference\nArea reference\nColSchema\nColor Schema\nCWidth\nClearance Width\nHeadroom\nHeadroom\nHeadClearance\nHead Clearance\nFThickness\nStair Flight Thickness\nOpHeight\nOperational Height\nOpWidth\nOperational Width\nOpLength\nOperational Length\nAccLevels\nAccess Heights for Stairwell\nLndLevels\nLanding levels from owning element\nLevRfA\nReferences to levels serviced by stairwell\nTemperature\nTemperature\nMaxTemperature\nMaximum Temperature\nMinTemperature\nMinimum Temperature\nHumidity\nDesign Humidity\nMaxHumidity\nMaximum Humidity\nMinHumidity\nMinimum Humidity\nPressure\nPressure\nMaxPressure\nMaximum Pressure\nMinPressure\nMinimum Pressure\nMaxWater\nMaximum Water Level\nAirChangeRate\nAir Change Rate\nOccupancy\nOccupancy\nLighting\nLighting requirements\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nDClnType\nDefault Ceiling Type\nDClnCode\nDefault Ceiling Code\nDFlrType\nDefault Floor Type\nDFlrCode\nDefault Floor Code\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nLabOffset\nLabel offset\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nLegal Members\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nDesign Dataset Element (DDSE)\nInventory List Element (INVLST)\nBoundary Element Set Element (SPBSET)\nStair Landing Element (STRLNG)\nStair Tower Element (STRTWR)\nStair Flight Element (STRFLT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nPosition\nPosition\nOrientation\nOrientation\nHeidefault\nDefault Height value\nStrCon\nStair Configuration\nAreaReference\nArea reference\nColSchema\nColor Schema\nCWidth\nClearance Width\nHeadroom\nHeadroom\nHeadClearance\nHead Clearance\nFThickness\nStair Flight Thickness\nOpHeight\nOperational Height\nOpWidth\nOperational Width\nOpLength\nOperational Length\nAccLevels\nAccess Heights for Stairwell\nLndLevels\nLanding levels from owning element\nLevRfA\nReferences to levels serviced by stairwell\nTemperature\nTemperature\nMaxTemperature\nMaximum Temperature\nMinTemperature\nMinimum Temperature\nHumidity\nDesign Humidity\nMaxHumidity\nMaximum Humidity\nMinHumidity\nMinimum Humidity\nPressure\nPressure\nMaxPressure\nMaximum Pressure\nMinPressure\nMinimum Pressure\nMaxWater\nMaximum Water Level\nAirChangeRate\nAir Change Rate\nOccupancy\nOccupancy\nLighting\nLighting requirements\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nDClnType\nDefault Ceiling Type\nDClnCode\nDefault Ceiling Code\nDFlrType\nDefault Floor Type\nDFlrCode\nDefault Floor Code\nDcrfarray\nArray of Design datasets for Design Code/Criteria\nLabOffset\nLabel offset\n\n\n\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nDesign Dataset Element (DDSE)\nInventory List Element (INVLST)\nBoundary Element Set Element (SPBSET)\nStair Landing Element (STRLNG)\nStair Tower Element (STRTWR)\nStair Flight Element (STRFLT)\nName\nDescription\nFunction\nPurpose\nNumber\nArea\nPosition\nOrientation\nHeidefault\nStrCon\nAreaReference\nColSchema\nCWidth\nHeadroom\nHeadClearance\nFThickness\nOpHeight\nOpWidth\nOpLength\nAccLevels\nLndLevels\nLevRfA\nTemperature\nMaxTemperature\nMinTemperature\nHumidity\nMaxHumidity\nMinHumidity\nPressure\nMaxPressure\nMinPressure\nMaxWater\nAirChangeRate\nOccupancy\nLighting\nFireRating\nFiresistance\nWaterTight\nGasTight\nDClnType\nDClnCode\nDFlrType\nDFlrCode\nDcrfarray\nLabOffset\nBuilding Block Element (BBLOCK)\nBuilding Level Element (BLEVEL)\nOpen Space Element (OPENSPACE)\nRoom Element (ROOM)\nAccess Point Set Element (ACCSET)\nArea Definition Element (AREADEF)\nBoundary Line Element (BNDLIN)\nDetail Group Element (DETGRP)\nDesign Dataset Element (DDSE)\nInventory List Element (INVLST)\nBoundary Element Set Element (SPBSET)\nStair Landing Element (STRLNG)\nStair Tower Element (STRTWR)\nStair Flight Element (STRFLT)"}
{"Headers": "Use Material Element (ERIAL)", "Content": "Material Element\nName\nName of the element\nDescription\nIs TRUE for the cableway branch that is meant to be dressed. If value is FALSE, then CTMRTRL cannot be created under CWBRAN element.\nReturn value\nBOOLEAN\nRules and Assumptions\nUser is prohibited to create CTMTRL under CWBRAN element which has the attribute set to FALSE.\nName\nName of the element\nDescription\nIs TRUE for the cableway branch that is meant to be dressed. If value is FALSE, then CTMRTRL cannot be created under CWBRAN element.\nReturn value\nBOOLEAN\nRules and Assumptions\nUser is prohibited to create CTMTRL under CWBRAN element which has the attribute set to FALSE.\n\nName\nName of the element\nDescription\nIs TRUE for the cableway branch that is meant to be dressed. If value is FALSE, then CTMRTRL cannot be created under CWBRAN element.\nReturn value\nBOOLEAN\nRules and Assumptions\nUser is prohibited to create CTMTRL under CWBRAN element which has the attribute set to FALSE.\n\n\n\nName\nDescription\nReturn value\nRules and Assumptions"}
{"Headers": "Window Element (WINDOW)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpnSize\nOpening size\nWThickness\nWall thickness\nClrSize\nClearance size\nWidth\nWidth\nHeight\nHeight\nHgSide\nHinge side\nSwing\nSwing\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpnSize\nOpening size\nWThickness\nWall thickness\nClrSize\nClearance size\nWidth\nWidth\nHeight\nHeight\nHgSide\nHinge side\nSwing\nSwing\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\nDetail Group Element (DETGRP)\nWall Openings Element (WLOPEN)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nOpnSize\nOpening size\nWThickness\nWall thickness\nClrSize\nClearance size\nWidth\nWidth\nHeight\nHeight\nHgSide\nHinge side\nSwing\nSwing\nFireRating\nFire rating\nFiresistance\nFire resistance\nWaterTight\nWater Tight\nGasTight\nGas Tight\nPosition\nPosition\nOrientation\nOrientation\nLabOffset\nLabel offset\nUuidia\nUniversally unique identifier\n\n\n\nDetail Group Element (DETGRP)\nWall Openings Element (WLOPEN)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nPurpose\nNumber\nSpref\nDesparam\nMatref\nOpnSize\nWThickness\nClrSize\nWidth\nHeight\nHgSide\nSwing\nFireRating\nFiresistance\nWaterTight\nGasTight\nPosition\nOrientation\nLabOffset\nUuidia\nDetail Group Element (DETGRP)\nWall Openings Element (WLOPEN)\nDesign Dataset Element (DDSE)\nDesign Ppoint/Pline Set Element (DPSET)\nFixing Element (FIXING)\nTemplate Element (TMPLATE)"}
{"Headers": "Wall Components Element (WLCOMPONENTS)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nConstant Thickness Wall Element (CTWALL)\nWall Panel Element (WLPANEL)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nConstant Thickness Wall Element (CTWALL)\nWall Panel Element (WLPANEL)\nName\nDescription\nFunction\nConstant Thickness Wall Element (CTWALL)\nWall Panel Element (WLPANEL)"}
{"Headers": "Wall Features Element (WLFEAT)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nConstant Thickness Wall Element (CTWALL)\nRoute Attachment Point Element (RATTA)\nWall Fittings Element (WLFITTING)\nWall Openings Element (WLOPEN)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nConstant Thickness Wall Element (CTWALL)\nRoute Attachment Point Element (RATTA)\nWall Fittings Element (WLFITTING)\nWall Openings Element (WLOPEN)\nAttributes\nName\nDescription\nFunction\nConstant Thickness Wall Element (CTWALL)\nRoute Attachment Point Element (RATTA)\nWall Fittings Element (WLFITTING)\nWall Openings Element (WLOPEN)"}
{"Headers": "Wall Fittings Element (WLFITTING)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nVDistance\nVertical Distance\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nVDistance\nVertical Distance\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nWall Features Element (WLFEAT)\nElectrical Fitting Element (ELFITTING)\nFixture Element (FIXTUR)\nFire Protection Fitting Element (FPFITTING)\nFurniture Element (FURNIT)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nVDistance\nVertical Distance\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\n\n\n\nWall Features Element (WLFEAT)\nElectrical Fitting Element (ELFITTING)\nFixture Element (FIXTUR)\nFire Protection Fitting Element (FPFITTING)\nFurniture Element (FURNIT)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)\nName\nDescription\nFunction\nWJusLine\nPurpose\nNumber\nArea\nVDistance\nPosRef\nZdistance\nPkdistance\nWall Features Element (WLFEAT)\nElectrical Fitting Element (ELFITTING)\nFixture Element (FIXTUR)\nFire Protection Fitting Element (FPFITTING)\nFurniture Element (FURNIT)\nHVAC Fitting Element (HVACFITTING)\nInformation Fitting Element (INFITTING)"}
{"Headers": "Wall Joints Element (WLJNTS)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nConstant Thickness Wall Element (CTWALL)\nWall Joint Element (WLJOIN)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nConstant Thickness Wall Element (CTWALL)\nWall Joint Element (WLJOIN)\nAttributes\nName\nDescription\nFunction\nConstant Thickness Wall Element (CTWALL)\nWall Joint Element (WLJOIN)"}
{"Headers": "Wall Joint Element (WLJOIN)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nWJusLine\nWall Justification Line\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nBangle\nBeta angle\nPosRef\nReference to point\nPkdistance\nProportional distance along Pline\nZdistance\nPosition in section\nSDistance\nVertical Distance of Start\nEDistance\nVertical Distance of End\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nWJusLine\nWall Justification Line\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nBangle\nBeta angle\nPosRef\nReference to point\nPkdistance\nProportional distance along Pline\nZdistance\nPosition in section\nSDistance\nVertical Distance of Start\nEDistance\nVertical Distance of End\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nWall Joints Element (WLJNTS)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nWJusLine\nWall Justification Line\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nBangle\nBeta angle\nPosRef\nReference to point\nPkdistance\nProportional distance along Pline\nZdistance\nPosition in section\nSDistance\nVertical Distance of Start\nEDistance\nVertical Distance of End\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\n\n\n\nWall Joints Element (WLJNTS)\nName\nDescription\nFunction\nSpref\nDesparam\nMatref\nLevel\nWJusLine\nLMirror\nJusline\nBangle\nPosRef\nPkdistance\nZdistance\nSDistance\nEDistance\nDrnstart\nDrnend\nWall Joints Element (WLJNTS)"}
{"Headers": "Wall Openings Element (WLOPEN)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nVDistance\nVertical Distance\nVertDirection\nVERTDI (true if Z axe is vertical)\nOpnSize\nOpening size\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nVDistance\nVertical Distance\nVertDirection\nVERTDI (true if Z axe is vertical)\nOpnSize\nOpening size\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nWall Features Element (WLFEAT)\nDoor Element (DOOR)\nRoute Path Element (RPATH)\nWindow Element (WINDOW)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nArea\nArea\nVDistance\nVertical Distance\nVertDirection\nVERTDI (true if Z axe is vertical)\nOpnSize\nOpening size\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\n\n\n\nWall Features Element (WLFEAT)\nDoor Element (DOOR)\nRoute Path Element (RPATH)\nWindow Element (WINDOW)\nAttributes\nName\nDescription\nFunction\nWJusLine\nPurpose\nNumber\nArea\nVDistance\nVertDirection\nOpnSize\nPosRef\nZdistance\nPkdistance\nWall Features Element (WLFEAT)\nDoor Element (DOOR)\nRoute Path Element (RPATH)\nWindow Element (WINDOW)"}
{"Headers": "Wall Panel Element (WLPANEL)", "Content": "Accommodation Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nVDistance\nVertical Distance\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nVDistance\nVertical Distance\nWall Components Element (WLCOMPONENTS)\nTemplate Element (TMPLATE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWJusLine\nWall Justification Line\nPurpose\nDescription code word\nNumber\nNumber\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nFireRating\nFire rating\nFiresistance\nFire resistance\nPosRef\nReference to point\nZdistance\nPosition in section\nPkdistance\nProportional distance along Pline\nVDistance\nVertical Distance\n\n\n\nWall Components Element (WLCOMPONENTS)\nTemplate Element (TMPLATE)\nName\nDescription\nFunction\nWJusLine\nPurpose\nNumber\nSpref\nDesparam\nMatref\nFireRating\nFiresistance\nPosRef\nZdistance\nPkdistance\nVDistance\nWall Components Element (WLCOMPONENTS)\nTemplate Element (TMPLATE)"}
{"Headers": "Wall Profile Element (WLPROF)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nBangle\nBeta angle\nXoffset\nX-offset\nZoffset\nZ-offset\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nWJusLine\nWall Justification Line\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nPkdistance\nProportional distance along Pline\nSzdistance\nStart load point in section\nEndRef\nCable End reference\nEPkdistance\nProportional distance of end point along Pline\nEzdistance\nEnd load point in section\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nBangle\nBeta angle\nXoffset\nX-offset\nZoffset\nZ-offset\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nWJusLine\nWall Justification Line\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nPkdistance\nProportional distance along Pline\nSzdistance\nStart load point in section\nEndRef\nCable End reference\nEPkdistance\nProportional distance of end point along Pline\nEzdistance\nEnd load point in section\nWall Profile Set Element (WLPRSE)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpref\nComponent spec reference\nDesparam\nDesign parameters\nMatref\nMaterial reference\nLevel\nDrawing level\nBangle\nBeta angle\nXoffset\nX-offset\nZoffset\nZ-offset\nLMirror\nTrue if Mirroring required\nJusline\nJustification Pline\nWJusLine\nWall Justification Line\nYdirection\nPreferred Y axis direction\nDrnstart\nPlane normal at start of SCTN/GENSEC\nDrnend\nPlane normal at end of SCTN/GENSEC\nStaRef\nCable Start reference\nPkdistance\nProportional distance along Pline\nSzdistance\nStart load point in section\nEndRef\nCable End reference\nEPkdistance\nProportional distance of end point along Pline\nEzdistance\nEnd load point in section\n\n\n\nWall Profile Set Element (WLPRSE)\nName\nDescription\nFunction\nSpref\nDesparam\nMatref\nLevel\nBangle\nXoffset\nZoffset\nLMirror\nJusline\nWJusLine\nYdirection\nDrnstart\nDrnend\nStaRef\nPkdistance\nSzdistance\nEndRef\nEPkdistance\nEzdistance\nWall Profile Set Element (WLPRSE)"}
{"Headers": "Wall Profile Set Element (WLPRSE)", "Content": "Accommodation Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nZdistance\nPosition in section\nVDistance\nVertical Distance\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nZdistance\nPosition in section\nVDistance\nVertical Distance\nConstant Thickness Wall Element (CTWALL)\nWall Profile Element (WLPROF)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nZdistance\nPosition in section\nVDistance\nVertical Distance\n\n\n\nConstant Thickness Wall Element (CTWALL)\nWall Profile Element (WLPROF)\nName\nDescription\nFunction\nZdistance\nVDistance\nConstant Thickness Wall Element (CTWALL)\nWall Profile Element (WLPROF)"}
{"Headers": "Dictionary Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the Dictionary database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "Dictionary Database Elements", "Content": "All data in the Dictionary database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Attribute Column Element (ATTCOLUMN)", "Content": "A column definition that uses a database element attribute as the columns data source.\nName\nName of the element\nDescription\nDescription of the element\nDbAttribute\nDatabase attribute\nAtQualifier\nAttribute qualifier\nUdname\nUser defined name\nReadOnly\nRead only\nName\nName of the element\nDescription\nDescription of the element\nDbAttribute\nDatabase attribute\nAtQualifier\nAttribute qualifier\nUdname\nUser defined name\nReadOnly\nRead only\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDbAttribute\nDatabase attribute\nAtQualifier\nAttribute qualifier\nUdname\nUser defined name\nReadOnly\nRead only\n\n\n\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)\nName\nDescription\nDbAttribute\nAtQualifier\nUdname\nReadOnly\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)"}
{"Headers": "Attribute Filter Element (ATTFILTER)", "Content": "A filter definition that defines an attribute test to filter a set of elements. The tests are performed using one of a fixed set of operators and a user defined value.\nName\nName of the element\nDbAttribute\nDatabase attribute\nFiltOperator\nFilter operator\nFiltValue\nFilter value\nName\nName of the element\nDbAttribute\nDatabase attribute\nFiltOperator\nFilter operator\nFiltValue\nFilter value\nDatabase View Element (DBVW)\nNone\nName\nName of the element\nDbAttribute\nDatabase attribute\nFiltOperator\nFilter operator\nFiltValue\nFilter value\n\n\n\nDatabase View Element (DBVW)\nName\nDbAttribute\nFiltOperator\nFiltValue\nDatabase View Element (DBVW)"}
{"Headers": "Calculation Template Group Element (CALGRP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nCalculation Template Group Element (CALGRP)\nCalculation Template World Element (CALWLD)\nCalculation Template Group Element (CALGRP)\nCalculation Template Element (CALTMP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nCalculation Template Group Element (CALGRP)\nCalculation Template World Element (CALWLD)\nCalculation Template Group Element (CALGRP)\nCalculation Template Element (CALTMP)\nName\nDescription\nCalculation Template Group Element (CALGRP)\nCalculation Template World Element (CALWLD)\nCalculation Template Group Element (CALGRP)\nCalculation Template Element (CALTMP)"}
{"Headers": "Calculation Template Element (CALTMP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDpName\nDisplay Name\nCUAlwd\nIndicates compare update window is allowed\nName\nName of the element\nDescription\nDescription of the element\nDpName\nDisplay Name\nCUAlwd\nIndicates compare update window is allowed\nCalculation Template Group Element (CALGRP)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDpName\nDisplay Name\nCUAlwd\nIndicates compare update window is allowed\n\n\n\nCalculation Template Group Element (CALGRP)\nName\nDescription\nDpName\nCUAlwd\nCalculation Template Group Element (CALGRP)"}
{"Headers": "Calculation Template World Element (CALWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nCalculation Template Group Element (CALGRP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nCalculation Template Group Element (CALGRP)\nName\nDescription\nWorld Element (WORLD)\nCalculation Template Group Element (CALGRP)"}
{"Headers": "Config Group World Element (CFGGPW)", "Content": "102 Element\nPrimary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nConfig Group Element (CFGGRP)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nConfig Group Element (CFGGRP)\nName\nWorld Element (WORLD)\nConfig Group Element (CFGGRP)"}
{"Headers": "Config Group Element (CFGGRP)", "Content": "102 Element\nPrimary Element\nName\nName of the element\nDname\nDisplay Name\nDescription\nDescription of the element\nCfgName\nConfiguration key name\nName\nName of the element\nDname\nDisplay Name\nDescription\nDescription of the element\nCfgName\nConfiguration key name\nConfig Group World Element (CFGGPW)\nConfig Group Element (CFGGRP)\nConfig Key Element (CFGKEY)\nConfig Group Element (CFGGRP)\nName\nName of the element\nDname\nDisplay Name\nDescription\nDescription of the element\nCfgName\nConfiguration key name\n\n\n\nConfig Group World Element (CFGGPW)\nConfig Group Element (CFGGRP)\nConfig Key Element (CFGKEY)\nConfig Group Element (CFGGRP)\nName\nDname\nDescription\nCfgName\nConfig Group World Element (CFGGPW)\nConfig Group Element (CFGGRP)\nConfig Key Element (CFGKEY)\nConfig Group Element (CFGGRP)"}
{"Headers": "Config Key Element (CFGKEY)", "Content": "102 Element\nPrimary Element\nName\nName of the element\nDname\nDisplay Name\nDescription\nDescription of the element\nCfgName\nConfiguration key name\nCfgType\nConfiguration value type\nCfgCtx\nConfiguration key context\nUunits\nFor Real Attributes, the dimension of the attribute (if applicable. (Examples bore, length, angle, mass)\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR\nUlength\nLength of data or text, arrays and Text Arrays. The maximum value is 214783647.\nULVOpt\nDetermines if UDA valid values or range limit is optional\nName\nName of the element\nDname\nDisplay Name\nDescription\nDescription of the element\nCfgName\nConfiguration key name\nCfgType\nConfiguration value type\nCfgCtx\nConfiguration key context\nUunits\nFor Real Attributes, the dimension of the attribute (if applicable. (Examples bore, length, angle, mass)\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR\nUlength\nLength of data or text, arrays and Text Arrays. The maximum value is 214783647.\nULVOpt\nDetermines if UDA valid values or range limit is optional\nConfig Group Element\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)\nName\nName of the element\nDname\nDisplay Name\nDescription\nDescription of the element\nCfgName\nConfiguration key name\nCfgType\nConfiguration value type\nCfgCtx\nConfiguration key context\nUunits\nFor Real Attributes, the dimension of the attribute (if applicable. (Examples bore, length, angle, mass)\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR\nUlength\nLength of data or text, arrays and Text Arrays. The maximum value is 214783647.\nULVOpt\nDetermines if UDA valid values or range limit is optional\n\n\n\nConfig Group Element\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)\nName\nDname\nDescription\nCfgName\nCfgType\nCfgCtx\nUunits\nUtype\nUlength\nULVOpt\nConfig Group Element\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)"}
{"Headers": "Column Relation Element (COLRELATION)", "Content": "Primary Element\nA parent child relationship between two columns. The values in the child column identified must be a sub-set of the values in the parent column identified.\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nParColumn\nParent column\nChdColumn\nChild column\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nParColumn\nParent column\nChdColumn\nChild column\nDatabase View Group Element (DBVWGROUP)\nDatabase View Set Element (DBVWSET)\nDatabase View World Element (DBVWWLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nParColumn\nParent column\nChdColumn\nChild column\n\n\n\nDatabase View Group Element (DBVWGROUP)\nDatabase View Set Element (DBVWSET)\nDatabase View World Element (DBVWWLD)\nName\nDescription\nUdname\nParColumn\nChdColumn\nDatabase View Group Element (DBVWGROUP)\nDatabase View Set Element (DBVWSET)\nDatabase View World Element (DBVWWLD)"}
{"Headers": "Create Rules Element (CRERULES)", "Content": "Primary Element\nCreate rules for creating row elements and column elements within a database view.\nName\nName of the element\nDescription\nDescription of the element\nOwnExpression\nOwner expression\nOwnExType\nOwner expression type\nTypExpression\nType Expression\ntypExType\nType expression type\nCreanc\nCreate ancestors\nName\nName of the element\nDescription\nDescription of the element\nOwnExpression\nOwner expression\nOwnExType\nOwner expression type\nTypExpression\nType Expression\ntypExType\nType expression type\nCreanc\nCreate ancestors\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)\nSet Attribute Rule Element (SETATTRIBUTE)\nSet Parameter Element (SETPARAMETER)\nSet Status Rule Element (SETSTATUS)\nName\nName of the element\nDescription\nDescription of the element\nOwnExpression\nOwner expression\nOwnExType\nOwner expression type\nTypExpression\nType Expression\ntypExType\nType expression type\nCreanc\nCreate ancestors\n\n\n\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)\nSet Attribute Rule Element (SETATTRIBUTE)\nSet Parameter Element (SETPARAMETER)\nSet Status Rule Element (SETSTATUS)\nName\nDescription\nOwnExpression\nOwnExType\nTypExpression\ntypExType\nCreanc\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)\nSet Attribute Rule Element (SETATTRIBUTE)\nSet Parameter Element (SETPARAMETER)\nSet Status Rule Element (SETSTATUS)"}
{"Headers": "Database View Element (DBVW)", "Content": "Primary Element\nA database view definition that defines a table constructed from the database hierarchy.\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nElelist\nTypes of elements (including UDETs) to which this applies\nDbVwStRef\nDatabase View Set reference array\nAutCre\nSet true to automatically create the element.\nAlwDel\nTo allow the admin user to determine if tags can be deleted\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nElelist\nTypes of elements (including UDETs) to which this applies\nDbVwStRef\nDatabase View Set reference array\nAutCre\nSet true to automatically create the element.\nAlwDel\nTo allow the admin user to determine if tags can be deleted\nDatabase View Group Element (DBVWGROUP)\nDatabase View Set Element (DBVWSET)\nDatabase View World Element (DBVWWLD)\nAttribute Column Element (ATTCOLUMN)\nAttribute Filter Element (ATTFILTER)\nCreate Rules Element (CRERULES)\nExpression Column Element (EXPCOLUMN)\nExpression Filter Element (EXPFILTER)\nSource Element Element (SRCELEMENT)\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nElelist\nTypes of elements (including UDETs) to which this applies\nDbVwStRef\nDatabase View Set reference array\nAutCre\nSet true to automatically create the element.\nAlwDel\nTo allow the admin user to determine if tags can be deleted\n\n\n\nDatabase View Group Element (DBVWGROUP)\nDatabase View Set Element (DBVWSET)\nDatabase View World Element (DBVWWLD)\nAttribute Column Element (ATTCOLUMN)\nAttribute Filter Element (ATTFILTER)\nCreate Rules Element (CRERULES)\nExpression Column Element (EXPCOLUMN)\nExpression Filter Element (EXPFILTER)\nSource Element Element (SRCELEMENT)\nName\nDescription\nUdname\nElelist\nDbVwStRef\nAutCre\nAlwDel\nDatabase View Group Element (DBVWGROUP)\nDatabase View Set Element (DBVWSET)\nDatabase View World Element (DBVWWLD)\nAttribute Column Element (ATTCOLUMN)\nAttribute Filter Element (ATTFILTER)\nCreate Rules Element (CRERULES)\nExpression Column Element (EXPCOLUMN)\nExpression Filter Element (EXPFILTER)\nSource Element Element (SRCELEMENT)"}
{"Headers": "Database View Group Element (DBVWGROUP)", "Content": "Primary Element\nA group element for managing database view definition elements.\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nDatabase View World Element (DBVWWLD)\nColumn Relation Element (COLRELATION)\nDatabase View Element (DBVW)\nDatabase View Set Element (DBVWSET)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nDatabase View World Element (DBVWWLD)\nColumn Relation Element (COLRELATION)\nDatabase View Element (DBVW)\nDatabase View Set Element (DBVWSET)\nName\nDescription\nDatabase View World Element (DBVWWLD)\nColumn Relation Element (COLRELATION)\nDatabase View Element (DBVW)\nDatabase View Set Element (DBVWSET)"}
{"Headers": "Database View Set Element (DBVWSET)", "Content": "Primary Element\nA set of database view definitions which may be related.\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nPridbv\nPrimary Database View\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nPridbv\nPrimary Database View\nDatabase View Group Element (DBVWGROUP)\nDatabase View World Element (DBVWWLD)\nColumn Relation Element (COLRELATION)\nDatabase View Element (DBVW)\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nPridbv\nPrimary Database View\n\n\n\nDatabase View Group Element (DBVWGROUP)\nDatabase View World Element (DBVWWLD)\nColumn Relation Element (COLRELATION)\nDatabase View Element (DBVW)\nName\nDescription\nUdname\nPridbv\nDatabase View Group Element (DBVWGROUP)\nDatabase View World Element (DBVWWLD)\nColumn Relation Element (COLRELATION)\nDatabase View Element (DBVW)"}
{"Headers": "Database View World Element (DBVWWLD)", "Content": "Primary Element\nA world of definition elements for defining database views.\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nColumn Relation Element (COLRELATION)\nDatabase View Element (DBVW)\nDatabase View Group Element (DBVWGROUP)\nDatabase View Set Element (DBVWSET)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nColumn Relation Element (COLRELATION)\nDatabase View Element (DBVW)\nDatabase View Group Element (DBVWGROUP)\nDatabase View Set Element (DBVWSET)\nName\nDescription\nWorld Element (WORLD)\nColumn Relation Element (COLRELATION)\nDatabase View Element (DBVW)\nDatabase View Group Element (DBVWGROUP)\nDatabase View Set Element (DBVWSET)"}
{"Headers": "Discipline Related Types Element (DISUDT)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDiscif\nReference of DISCIPLINE Element\nElelist\nTypes of elements, including UDETs, to which this applies\nName\nName of the element\nDescription\nDescription of the element\nDiscif\nReference of DISCIPLINE Element\nElelist\nTypes of elements, including UDETs, to which this applies\nEngineering Types Classification Element (UDTCLA)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDiscif\nReference of DISCIPLINE Element\nElelist\nTypes of elements, including UDETs, to which this applies\n\n\n\nEngineering Types Classification Element (UDTCLA)\nName\nDescription\nDiscif\nElelist\nEngineering Types Classification Element (UDTCLA)"}
{"Headers": "Datasheet Template Group Element (DSTGRO)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nDatasheet Template Group Element (DSTGRO)\nDatasheet Template World Element (DSTWLD)\nDatasheet Template Group Element (DSTGRO)\nDatasheet Template Element (DSTMPL)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nDatasheet Template Group Element (DSTGRO)\nDatasheet Template World Element (DSTWLD)\nDatasheet Template Group Element (DSTGRO)\nDatasheet Template Element (DSTMPL)\nName\nDescription\nDatasheet Template Group Element (DSTGRO)\nDatasheet Template World Element (DSTWLD)\nDatasheet Template Group Element (DSTGRO)\nDatasheet Template Element (DSTMPL)"}
{"Headers": "Datasheet Template Element (DSTMPL)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nExfile\nExtract file number\nPvno\nPicture version number\nDatasource\nDBView or DBViewSet reference array for Datasheet Template\nDiscis\nAssociated disciplines\nDSNO\nDatasheet number\nLstdst\nLogical Value For List Datasheet\nDSTYPE\nDatasheet type\nDBBLOB\nDatabase Binary Large Object\nName\nName of the element\nDescription\nDescription of the element\nExfile\nExtract file number\nPvno\nPicture version number\nDatasource\nDBView or DBViewSet reference array for Datasheet Template\nDiscis\nAssociated disciplines\nDSNO\nDatasheet number\nLstdst\nLogical Value For List Datasheet\nDSTYPE\nDatasheet type\nDBBLOB\nDatabase Binary Large Object\nDatasheet Template Group Element (DSTGRO)\nNone\nName\nName of the element\nDescription\nDescription of the element\nExfile\nExtract file number\nPvno\nPicture version number\nDatasource\nDBView or DBViewSet reference array for Datasheet Template\nDiscis\nAssociated disciplines\nDSNO\nDatasheet number\nLstdst\nLogical Value For List Datasheet\nDSTYPE\nDatasheet type\nDBBLOB\nDatabase Binary Large Object\n\n\n\nDatasheet Template Group Element (DSTGRO)\nName\nDescription\nExfile\nPvno\nDatasource\nDiscis\nDSNO\nLstdst\nDSTYPE\nDBBLOB\nDatasheet Template Group Element (DSTGRO)"}
{"Headers": "Datasheet Template World Element (DSTWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nDatasheet Template Group Element (DSTGRO)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nDatasheet Template Group Element (DSTGRO)\nName\nDescription\nWorld Element (WORLD)\nDatasheet Template Group Element (DSTGRO)"}
{"Headers": "Default Home Destination Definition Element (DSXDST)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nDHTest\nTest locator expression\nDHText\nDefault home identifier expression\nName\nName of the element\nDescription\nDescription of the element\nDHTest\nTest locator expression\nDHText\nDefault home identifier expression\nDefault Home Definition Element (DSXHOM)\nDefault Home Test Definition Element (DSXTST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDHTest\nTest locator expression\nDHText\nDefault home identifier expression\n\n\n\nDefault Home Definition Element (DSXHOM)\nDefault Home Test Definition Element (DSXTST)\nName\nDescription\nDHTest\nDHText\nDefault Home Definition Element (DSXHOM)\nDefault Home Test Definition Element (DSXTST)"}
{"Headers": "Group for Distributed Definitions Element (DSXGRP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nDistributed Attribute Definition World Element (DSXWLD)\nDefault Home Definition Element (DSXHOM)\nDistributed Attributes Schema Element (DSXSCH)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nDistributed Attribute Definition World Element (DSXWLD)\nDefault Home Definition Element (DSXHOM)\nDistributed Attributes Schema Element (DSXSCH)\nName\nDescription\nDistributed Attribute Definition World Element (DSXWLD)\nDefault Home Definition Element (DSXHOM)\nDistributed Attributes Schema Element (DSXSCH)"}
{"Headers": "Default Home Definition Element (DSXHOM)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nGroup for Distributed Definitions Element (DSXGRP)\nDefault Home Destination Definition Element (DSXDST)\nDefault Home Test Definition Element (DSXTST)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nGroup for Distributed Definitions Element (DSXGRP)\nDefault Home Destination Definition Element (DSXDST)\nDefault Home Test Definition Element (DSXTST)\nName\nDescription\nGroup for Distributed Definitions Element (DSXGRP)\nDefault Home Destination Definition Element (DSXDST)\nDefault Home Test Definition Element (DSXTST)"}
{"Headers": "Bound Elements Definition Element (DSXMBR)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nAutCre\nSet true to automatically create the element.\nElelist\nTypes of elements (including UDETs) to which this applies\nCardinality\nCardinality definition\nDefHome\nDefault allocation home\nName\nName of the element\nDescription\nDescription of the element\nAutCre\nSet true to automatically create the element.\nElelist\nTypes of elements (including UDETs) to which this applies\nCardinality\nCardinality definition\nDefHome\nDefault allocation home\nBinding Elements Definition Element (DSXOWN)\nNone\nName\nName of the element\nDescription\nDescription of the element\nAutCre\nSet true to automatically create the element.\nElelist\nTypes of elements (including UDETs) to which this applies\nCardinality\nCardinality definition\nDefHome\nDefault allocation home\n\n\n\nBinding Elements Definition Element (DSXOWN)\nName\nDescription\nAutCre\nElelist\nCardinality\nDefHome\nBinding Elements Definition Element (DSXOWN)"}
{"Headers": "Binding Elements Definition Element (DSXOWN)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nElelist\nTypes of elements (including UDETs) to which this applies\nDefHome\nDefault allocation home\nName\nName of the element\nDescription\nDescription of the element\nElelist\nTypes of elements (including UDETs) to which this applies\nDefHome\nDefault allocation home\nDistributed Attributes Schema Element (DSXSCH)\nBound Elements Definition Element (DSXMBR)\nName\nName of the element\nDescription\nDescription of the element\nElelist\nTypes of elements (including UDETs) to which this applies\nDefHome\nDefault allocation home\n\n\n\nDistributed Attributes Schema Element (DSXSCH)\nBound Elements Definition Element (DSXMBR)\nName\nDescription\nElelist\nDefHome\nDistributed Attributes Schema Element (DSXSCH)\nBound Elements Definition Element (DSXMBR)"}
{"Headers": "Distributed Attributes Schema Element (DSXSCH)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDefHome\nDefault allocation home\nName\nName of the element\nDescription\nDescription of the element\nDefHome\nDefault allocation home\nGroup for Distributed Definitions Element (DSXGRP)\nBinding Elements Definition Element (DSXOWN)\nName\nName of the element\nDescription\nDescription of the element\nDefHome\nDefault allocation home\n\n\n\nGroup for Distributed Definitions Element (DSXGRP)\nBinding Elements Definition Element (DSXOWN)\nName\nDescription\nDefHome\nGroup for Distributed Definitions Element (DSXGRP)\nBinding Elements Definition Element (DSXOWN)"}
{"Headers": "Default Home Test Definition Element (DSXTST)", "Content": "Attributes\nName\nName of the element\nDescription\nDescription of the element\nDHTest\nTest locator expression\nName\nName of the element\nDescription\nDescription of the element\nDHTest\nTest locator expression\nDefault Home Definition Element (DSXHOM)\nDefault Home Destination Definition Element (DSXDST)\nDefault Home Test Definition Element (DSXTST)\nName\nName of the element\nDescription\nDescription of the element\nDHTest\nTest locator expression\n\n\n\nDefault Home Definition Element (DSXHOM)\nDefault Home Destination Definition Element (DSXDST)\nDefault Home Test Definition Element (DSXTST)\nName\nDescription\nDHTest\nDefault Home Definition Element (DSXHOM)\nDefault Home Destination Definition Element (DSXDST)\nDefault Home Test Definition Element (DSXTST)"}
{"Headers": "Distributed Attribute Definition World Element (DSXWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nGroup for Distributed Definitions Element (DSXGRP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nGroup for Distributed Definitions Element (DSXGRP)\nName\nDescription\nWorld Element (WORLD)\nGroup for Distributed Definitions Element (DSXGRP)"}
{"Headers": "Engineering Configuration World Element (ENGCWL)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nCorcon\nCOR Configurations\nName\nName of the element\nDescription\nDescription of the element\nCorcon\nCOR Configurations\nWorld Element (WORLD)\nEngineering Interface Definition Element (INTDEF)\nTMS Configuration Element (TMSCFG)\nEngineering Types Classification Element (UDTCLA)\nName\nName of the element\nDescription\nDescription of the element\nCorcon\nCOR Configurations\n\n\n\nWorld Element (WORLD)\nEngineering Interface Definition Element (INTDEF)\nTMS Configuration Element (TMSCFG)\nEngineering Types Classification Element (UDTCLA)\nName\nDescription\nCorcon\nWorld Element (WORLD)\nEngineering Interface Definition Element (INTDEF)\nTMS Configuration Element (TMSCFG)\nEngineering Types Classification Element (UDTCLA)"}
{"Headers": "Expression Column Element (EXPCOLUMN)", "Content": "A column definition that has an expression as its data source. The expression may be a PML 1 or XPath expression.\nName\nName of the element\nDescription\nDescription of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nUdname\nUser defined name\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR)\nName\nName of the element\nDescription\nDescription of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nUdname\nUser defined name\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR)\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nUdname\nUser defined name\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR)\n\n\n\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)\nName\nDescription\nExpression\nExpType\nUdname\nUtype\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)"}
{"Headers": "Expression Filter Element (EXPFILTER)", "Content": "A filter definition that defines a boolean expression to filter an element set. The expression may be a PML 1 expression or an XPath 1.0 expression.\nName\nName of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nName\nName of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nDatabase View Element (DBVW)\nNone\nName\nName of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\n\n\n\nDatabase View Element (DBVW)\nName\nExpression\nExpType\nDatabase View Element (DBVW)"}
{"Headers": "Engineering Interface Attribute Element (INTATT)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDbAttribute\nDatabase attribute\nName\nName of the element\nDescription\nDescription of the element\nDbAttribute\nDatabase attribute\nEngineering Type Interface Element (UDTINT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDbAttribute\nDatabase attribute\n\n\n\nEngineering Type Interface Element (UDTINT)\nName\nDescription\nDbAttribute\nEngineering Type Interface Element (UDTINT)"}
{"Headers": "Engineering Interface Definition Element (INTDEF)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nEngineering Configuration World Element (ENGCWL)\nEngineering Type Interface Element (UDTINT)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nEngineering Configuration World Element (ENGCWL)\nEngineering Type Interface Element (UDTINT)\nName\nDescription\nEngineering Configuration World Element (ENGCWL)\nEngineering Type Interface Element (UDTINT)"}
{"Headers": "Naming Rule Element (NAMRUL)", "Content": "Primary Element\nName\nName of the element\nDistag\nDisplay tag\nDescription\nDescription of the element\nActive\nActive\nNamatt\nNaming attribute\nRefcls\nReferenced conceptual model class\nClstyp\nClass Type\nName\nName of the element\nDistag\nDisplay tag\nDescription\nDescription of the element\nActive\nActive\nNamatt\nNaming attribute\nRefcls\nReferenced conceptual model class\nClstyp\nClass Type\nNaming Rules Group Element (RULGRP)\nNaming Part Element (NRULPT)\nName\nName of the element\nDistag\nDisplay tag\nDescription\nDescription of the element\nActive\nActive\nNamatt\nNaming attribute\nRefcls\nReferenced conceptual model class\nClstyp\nClass Type\n\n\n\nNaming Rules Group Element (RULGRP)\nNaming Part Element (NRULPT)\nName\nDistag\nDescription\nActive\nNamatt\nRefcls\nClstyp\nNaming Rules Group Element (RULGRP)\nNaming Part Element (NRULPT)"}
{"Headers": "Naming Part Element (NRULPT)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nConatt\nReferenced conceptual model attribute\nInuniq\nFlag to notify if attribute is used in uniqueness\nRequired\nAction is not optional\nValType\nType of the value. INT, REAL or TEXT\nTexlength\nLength of text\nFixlen\nFlag to notify if length of the attribute is fixed\nNulval\nString to be used if the attribute is blank\nSepar\nSeparator String\nPrefix\nPrefix\nSuffix\nSuffix\nPtordr\nOrder of part in rule\nPartyp\nType of part\nLvisibility\nVisibility flag\nName\nName of the element\nDescription\nDescription of the element\nConatt\nReferenced conceptual model attribute\nInuniq\nFlag to notify if attribute is used in uniqueness\nRequired\nAction is not optional\nValType\nType of the value. INT, REAL or TEXT\nTexlength\nLength of text\nFixlen\nFlag to notify if length of the attribute is fixed\nNulval\nString to be used if the attribute is blank\nSepar\nSeparator String\nPrefix\nPrefix\nSuffix\nSuffix\nPtordr\nOrder of part in rule\nPartyp\nType of part\nLvisibility\nVisibility flag\nNaming Rule Element (NAMRUL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nConatt\nReferenced conceptual model attribute\nInuniq\nFlag to notify if attribute is used in uniqueness\nRequired\nAction is not optional\nValType\nType of the value. INT, REAL or TEXT\nTexlength\nLength of text\nFixlen\nFlag to notify if length of the attribute is fixed\nNulval\nString to be used if the attribute is blank\nSepar\nSeparator String\nPrefix\nPrefix\nSuffix\nSuffix\nPtordr\nOrder of part in rule\nPartyp\nType of part\nLvisibility\nVisibility flag\n\n\n\nNaming Rule Element (NAMRUL)\nName\nDescription\nConatt\nInuniq\nRequired\nValType\nTexlength\nFixlen\nNulval\nSepar\nPrefix\nSuffix\nPtordr\nPartyp\nLvisibility\nNaming Rule Element (NAMRUL)"}
{"Headers": "Flexible Explorer Criteria Element (PBSCRT)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nPBSFty\nFlexible Explorer formula type\nPBSFml\nFlexible Explorer formula\nPBSSrt\nFlexible Explorer sorting\nPBSQno\nFlexible Explorer query node\nName\nName of the element\nDescription\nDescription of the element\nPBSFty\nFlexible Explorer formula type\nPBSFml\nFlexible Explorer formula\nPBSSrt\nFlexible Explorer sorting\nPBSQno\nFlexible Explorer query node\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)\nNone\nName\nName of the element\nDescription\nDescription of the element\nPBSFty\nFlexible Explorer formula type\nPBSFml\nFlexible Explorer formula\nPBSSrt\nFlexible Explorer sorting\nPBSQno\nFlexible Explorer query node\n\n\n\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)\nName\nDescription\nPBSFty\nPBSFml\nPBSSrt\nPBSQno\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)"}
{"Headers": "Flexible Explorer Object Node Element (PBSOBN)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nPBSFty\nFlexible Explorer formula type\nPBSFml\nFlexible Explorer formula\nPBSTxt\nFlexible Explorer text\nPBSIco\nFlexible Explorer icon\nPBSVal\nFlexible Explorer value\nPBSGrb\nFlexible Explorer grouping formula\nPBSCmu\nFlexible Explorer context menu\nPBSSrt\nFlexible Explorer sorting\nPBSHde\nFlexible Explorer Hide empty child nodes\nPBSPar\nFlexible Explorer parameter nodes\nPBSRcr\nFlexible Explorer recurrent node\nName\nName of the element\nDescription\nDescription of the element\nPBSFty\nFlexible Explorer formula type\nPBSFml\nFlexible Explorer formula\nPBSTxt\nFlexible Explorer text\nPBSIco\nFlexible Explorer icon\nPBSVal\nFlexible Explorer value\nPBSGrb\nFlexible Explorer grouping formula\nPBSCmu\nFlexible Explorer context menu\nPBSSrt\nFlexible Explorer sorting\nPBSHde\nFlexible Explorer Hide empty child nodes\nPBSPar\nFlexible Explorer parameter nodes\nPBSRcr\nFlexible Explorer recurrent node\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Template Definition Element (PBSTPL)\nFlexible Explorer Text Node Element (PBSTXN)\nFlexible Explorer Criteria Element (PBSCRT)\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)\nName\nName of the element\nDescription\nDescription of the element\nPBSFty\nFlexible Explorer formula type\nPBSFml\nFlexible Explorer formula\nPBSTxt\nFlexible Explorer text\nPBSIco\nFlexible Explorer icon\nPBSVal\nFlexible Explorer value\nPBSGrb\nFlexible Explorer grouping formula\nPBSCmu\nFlexible Explorer context menu\nPBSSrt\nFlexible Explorer sorting\nPBSHde\nFlexible Explorer Hide empty child nodes\nPBSPar\nFlexible Explorer parameter nodes\nPBSRcr\nFlexible Explorer recurrent node\n\n\n\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Template Definition Element (PBSTPL)\nFlexible Explorer Text Node Element (PBSTXN)\nFlexible Explorer Criteria Element (PBSCRT)\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)\nName\nDescription\nPBSFty\nPBSFml\nPBSTxt\nPBSIco\nPBSVal\nPBSGrb\nPBSCmu\nPBSSrt\nPBSHde\nPBSPar\nPBSRcr\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Template Definition Element (PBSTPL)\nFlexible Explorer Text Node Element (PBSTXN)\nFlexible Explorer Criteria Element (PBSCRT)\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)"}
{"Headers": "Flexible Explorer Template Definition Element (PBSTPL)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nPBSTxt\nFlexible Explorer Text\nPBSIco\nFlexible Explorer icon\nPBSCmu\nFlexible Explorer context menu\nPBSSrt\nFlexible Explorer sorting\nPBSHde\nFlexible Explorer Hide empty child nodes\nDiscis\nAssociated disciplines\nName\nName of the element\nDescription\nDescription of the element\nPBSTxt\nFlexible Explorer Text\nPBSIco\nFlexible Explorer icon\nPBSCmu\nFlexible Explorer context menu\nPBSSrt\nFlexible Explorer sorting\nPBSHde\nFlexible Explorer Hide empty child nodes\nDiscis\nAssociated disciplines\nFlexible Explorer Templates World Element (PBSWLD)\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)\nName\nName of the element\nDescription\nDescription of the element\nPBSTxt\nFlexible Explorer Text\nPBSIco\nFlexible Explorer icon\nPBSCmu\nFlexible Explorer context menu\nPBSSrt\nFlexible Explorer sorting\nPBSHde\nFlexible Explorer Hide empty child nodes\nDiscis\nAssociated disciplines\n\n\n\nFlexible Explorer Templates World Element (PBSWLD)\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)\nName\nDescription\nPBSTxt\nPBSIco\nPBSCmu\nPBSSrt\nPBSHde\nDiscis\nFlexible Explorer Templates World Element (PBSWLD)\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)"}
{"Headers": "Flexible Explorer Text Node Element (PBSTXN)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nPBSFty\nFlexible Explorer formula type\nPBSFml\nFlexible Explorer formula\nPBSIco\nFlexible Explorer icon\nPBSCmu\nFlexible Explorer context menu\nPBSSrt\nFlexible Explorer sorting\nPBSHde\nFlexible Explorer Hide empty child nodes\nPBSPar\nFlexible Explorer parameter nodes\nPBSRcr\nFlexible Explorer recurrent node\nName\nName of the element\nDescription\nDescription of the element\nPBSFty\nFlexible Explorer formula type\nPBSFml\nFlexible Explorer formula\nPBSIco\nFlexible Explorer icon\nPBSCmu\nFlexible Explorer context menu\nPBSSrt\nFlexible Explorer sorting\nPBSHde\nFlexible Explorer Hide empty child nodes\nPBSPar\nFlexible Explorer parameter nodes\nPBSRcr\nFlexible Explorer recurrent node\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Template Definition Element (PBSTPL)\nFlexible Explorer Text Node Element (PBSTXN)\nFlexible Explorer Criteria Element (PBSCRT)\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)\nName\nName of the element\nDescription\nDescription of the element\nPBSFty\nFlexible Explorer formula type\nPBSFml\nFlexible Explorer formula\nPBSIco\nFlexible Explorer icon\nPBSCmu\nFlexible Explorer context menu\nPBSSrt\nFlexible Explorer sorting\nPBSHde\nFlexible Explorer Hide empty child nodes\nPBSPar\nFlexible Explorer parameter nodes\nPBSRcr\nFlexible Explorer recurrent node\n\n\n\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Template Definition Element (PBSTPL)\nFlexible Explorer Text Node Element (PBSTXN)\nFlexible Explorer Criteria Element (PBSCRT)\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)\nName\nDescription\nPBSFty\nPBSFml\nPBSIco\nPBSCmu\nPBSSrt\nPBSHde\nPBSPar\nPBSRcr\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Template Definition Element (PBSTPL)\nFlexible Explorer Text Node Element (PBSTXN)\nFlexible Explorer Criteria Element (PBSCRT)\nFlexible Explorer Object Node Element (PBSOBN)\nFlexible Explorer Text Node Element (PBSTXN)"}
{"Headers": "Flexible Explorer Templates World Element (PBSWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nFlexible Explorer Template Definition Element (PBSTPL)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nFlexible Explorer Template Definition Element (PBSTPL)\nName\nDescription\nWorld Element (WORLD)\nFlexible Explorer Template Definition Element (PBSTPL)"}
{"Headers": "Revision Block Definition Element (REVBLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\nFordat\nDate Format Definition\nSTDEFREF\nStatus definition\nRevision Count\nDirection Coding\nUsehdr\nHeader Usage Indicator\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\nFordat\nDate Format Definition\nSTDEFREF\nStatus definition\n\nRevision Count\n\nDirection Coding\nUsehdr\nHeader Usage Indicator\nRevision Configuration Group Element (REVCGP)\nRevision History Block Data Item Element (REVSTD)\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\nFordat\nDate Format Definition\nSTDEFREF\nStatus definition\nRevision Count\nDirection Coding\nUsehdr\nHeader Usage Indicator\n\n\n\nRevision Configuration Group Element (REVCGP)\nRevision History Block Data Item Element (REVSTD)\nName\nDescription\nDistag\nFordat\nSTDEFREF\nUsehdr\nRevision Configuration Group Element (REVCGP)\nRevision History Block Data Item Element (REVSTD)"}
{"Headers": "Revision Configuration Group Element (REVCGP)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nRevision Configuration Group Element (REVCGP)\nRevision Configuration World Element (REVCWL)\nRevision Configuration Group Element (REVCGP)\nRevision Block Definition Element (REVBLD)\nRevision Number Definition Element (REVNOD)\nRevision Configuration Element (REVCON)\nVersion Control Configuration Element (VERCON)\nName\nName of the element\n\n\n\nRevision Configuration Group Element (REVCGP)\nRevision Configuration World Element (REVCWL)\nRevision Configuration Group Element (REVCGP)\nRevision Block Definition Element (REVBLD)\nRevision Number Definition Element (REVNOD)\nRevision Configuration Element (REVCON)\nVersion Control Configuration Element (VERCON)\nName\nRevision Configuration Group Element (REVCGP)\nRevision Configuration World Element (REVCWL)\nRevision Configuration Group Element (REVCGP)\nRevision Block Definition Element (REVBLD)\nRevision Number Definition Element (REVNOD)\nRevision Configuration Element (REVCON)\nVersion Control Configuration Element (VERCON)"}
{"Headers": "Revision Configuration Element (REVCON)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\nElelist\nTypes of elements, including UDETs, to which this applies\nRvcrwr\nWorking Revision Creation Statuses\nRvcris\nRevision Controlled Element Issue Statuses\nSTDEFREF\nStatus definition\nNodref\nRevision Number Definition\nBldref\nRevision Block Array\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\nElelist\nTypes of elements, including UDETs, to which this applies\nRvcrwr\nWorking Revision Creation Statuses\nRvcris\nRevision Controlled Element Issue Statuses\nSTDEFREF\nStatus definition\nNodref\nRevision Number Definition\nBldref\nRevision Block Array\nRevision Configuration Group Element (REVCGP)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\nElelist\nTypes of elements, including UDETs, to which this applies\nRvcrwr\nWorking Revision Creation Statuses\nRvcris\nRevision Controlled Element Issue Statuses\nSTDEFREF\nStatus definition\nNodref\nRevision Number Definition\nBldref\nRevision Block Array\n\n\n\nRevision Configuration Group Element (REVCGP)\nName\nDescription\nDistag\nElelist\nRvcrwr\nRvcris\nSTDEFREF\nNodref\nBldref\nRevision Configuration Group Element (REVCGP)"}
{"Headers": "Revision Configuration World Element (REVCWL)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nRevision Configuration Group Element (REVCGP)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nRevision Configuration Group Element (REVCGP)\nName\nWorld Element (WORLD)\nRevision Configuration Group Element (REVCGP)"}
{"Headers": "Revision Number Definition Element (REVNOD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\nWrkmrk\nWorking Revision Indicator String\nIncWrk\nIncrement at working revision\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\nWrkmrk\nWorking Revision Indicator String\nIncWrk\nIncrement at working revision\nRevision Configuration Group Element (REVCGP)\nRevision Number Part Element (REVNOP)\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\nWrkmrk\nWorking Revision Indicator String\nIncWrk\nIncrement at working revision\n\n\n\nRevision Configuration Group Element (REVCGP)\nRevision Number Part Element (REVNOP)\nName\nDescription\nDistag\nWrkmrk\nIncWrk\nRevision Configuration Group Element (REVCGP)\nRevision Number Part Element (REVNOP)"}
{"Headers": "Revision Number Part Element (REVNOP)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nNopknd\nNumber Part Type: 1=alpha,2=number,3=custom\nTexlength\nLength of text\nDistag\nDisplay tag\nPrefix\nPrefix\nSepar\nSeparator String\nCusval\nDelimited Custom Value List\nUsecap\nCapital Letter Usage Indicator\nExclch\nExclusion Character List\nSeqres\nSequence Reset Indicator\nSeqbls\nSequence Blank Start Indicator\nStartZero\nStart from zero\nClrIssue\nClear lower parts on issue\nName\nName of the element\nDescription\nDescription of the element\nNopknd\nNumber Part Type: 1=alpha,2=number,3=custom\nTexlength\nLength of text\nDistag\nDisplay tag\nPrefix\nPrefix\nSepar\nSeparator String\nCusval\nDelimited Custom Value List\nUsecap\nCapital Letter Usage Indicator\nExclch\nExclusion Character List\nSeqres\nSequence Reset Indicator\nSeqbls\nSequence Blank Start Indicator\nStartZero\nStart from zero\nClrIssue\nClear lower parts on issue\nRevision Number Definition Element (REVNOD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nNopknd\nNumber Part Type: 1=alpha,2=number,3=custom\nTexlength\nLength of text\nDistag\nDisplay tag\nPrefix\nPrefix\nSepar\nSeparator String\nCusval\nDelimited Custom Value List\nUsecap\nCapital Letter Usage Indicator\nExclch\nExclusion Character List\nSeqres\nSequence Reset Indicator\nSeqbls\nSequence Blank Start Indicator\nStartZero\nStart from zero\nClrIssue\nClear lower parts on issue\n\n\n\nRevision Number Definition Element (REVNOD)\nName\nDescription\nNopknd\nTexlength\nDistag\nPrefix\nSepar\nCusval\nUsecap\nExclch\nSeqres\nSeqbls\nStartZero\nClrIssue\nRevision Number Definition Element (REVNOD)"}
{"Headers": "Revision History Block Data Item Element (REVSTD)", "Content": "Name\nName of the element\nDistag\nDisplay tag\nValref\nStatus Value reference\nRbctyp\nRevision History Column Type: 1=RevNo,2=Date,3=User,4=Comment\nName\nName of the element\nDistag\nDisplay tag\nValref\nStatus Value reference\nRbctyp\nRevision History Column Type: 1=RevNo,2=Date,3=User,4=Comment\nRevision Block Definition Element (REVBLD)\nNone\nName\nName of the element\nDistag\nDisplay tag\nValref\nStatus Value reference\nRbctyp\nRevision History Column Type: 1=RevNo,2=Date,3=User,4=Comment\n\n\n\nRevision Block Definition Element (REVBLD)\nName\nDistag\nValref\nRbctyp\nRevision Block Definition Element (REVBLD)"}
{"Headers": "Naming Rules Group Element (RULGRP)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nNaming Rules World Element (RULWLD)\nNaming Rules Group Element (RULGRP)\nNaming Rules Group Element (RULGRP)\nNaming Rule Element (NAMRUL)\nName\nName of the element\n\n\n\nNaming Rules World Element (RULWLD)\nNaming Rules Group Element (RULGRP)\nNaming Rules Group Element (RULGRP)\nNaming Rule Element (NAMRUL)\nName\nNaming Rules World Element (RULWLD)\nNaming Rules Group Element (RULGRP)\nNaming Rules Group Element (RULGRP)\nNaming Rule Element (NAMRUL)"}
{"Headers": "Naming Rules World Element (RULWLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nNaming Rules Group Element (RULGRP)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nNaming Rules Group Element (RULGRP)\nName\nWorld Element (WORLD)\nNaming Rules Group Element (RULGRP)"}
{"Headers": "Set Attribute Rule Element (SETATTRIBUTE)", "Content": "A rule used to set an attribute when an element is created. If the value expression is left unset then the application or user are prompted for input.\nName\nName of the element\nDbAttribute\nDatabase attribute\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nUPrompt\nTextual prompt to display to the user\nRequired\nAction is not optional\nName\nName of the element\nDbAttribute\nDatabase attribute\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nUPrompt\nTextual prompt to display to the user\nRequired\nAction is not optional\nCreate Rules Element (CRERULES)\nTest Expression Element (TESTEXPRESSION)\nName\nName of the element\nDbAttribute\nDatabase attribute\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nUPrompt\nTextual prompt to display to the user\nRequired\nAction is not optional\n\n\n\nCreate Rules Element (CRERULES)\nTest Expression Element (TESTEXPRESSION)\nName\nDbAttribute\nExpression\nExpType\nUPrompt\nRequired\nCreate Rules Element (CRERULES)\nTest Expression Element (TESTEXPRESSION)"}
{"Headers": "Set Parameter Element (SETPARAMETER)", "Content": "A parameter for use when executing rules to element creation within database views.\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nUPrompt\nTextual prompt to display to the user\nRequired\nAction is not optional\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nUPrompt\nTextual prompt to display to the user\nRequired\nAction is not optional\nCreate Rules Element (CRERULES)\nNone\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nUPrompt\nTextual prompt to display to the user\nRequired\nAction is not optional\n\n\n\nCreate Rules Element (CRERULES)\nName\nDescription\nUdname\nUtype\nExpression\nExpType\nUPrompt\nRequired\nCreate Rules Element (CRERULES)"}
{"Headers": "Set Status Rule Element (SETSTATUS)", "Content": "Set the status definition to apply to an element when created.\nName\nName of the element\nSTDEFREF\nStatus definition\nUPrompt\nTextual prompt to display to the user\nRequired\nAction is not optional\nName\nName of the element\nSTDEFREF\nStatus definition\nUPrompt\nTextual prompt to display to the user\nRequired\nAction is not optional\nCreate Rules Element (CRERULES)\nTest Expression Element (TESTEXPRESSION)\nName\nName of the element\nSTDEFREF\nStatus definition\nUPrompt\nTextual prompt to display to the user\nRequired\nAction is not optional\n\n\n\nCreate Rules Element (CRERULES)\nTest Expression Element (TESTEXPRESSION)\nName\nSTDEFREF\nUPrompt\nRequired\nCreate Rules Element (CRERULES)\nTest Expression Element (TESTEXPRESSION)"}
{"Headers": "Source Element Element (SRCELEMENT)", "Content": "Primary Element\nDefines the navigation from the current element context to another element so that attributes and expressions can be used from the identified element.\nName\nName of the element\nDescription\nDescription of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nAutCre\nSet true to automatically create the element.\nName\nName of the element\nDescription\nDescription of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nAutCre\nSet true to automatically create the element.\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)\nAttribute Column Element (ATTCOLUMN)\nCreate Rules Element (CRERULES)\nExpression Column Element (EXPCOLUMN)\nSource Element Element (SRCELEMENT)\nName\nName of the element\nDescription\nDescription of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nAutCre\nSet true to automatically create the element.\n\n\n\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)\nAttribute Column Element (ATTCOLUMN)\nCreate Rules Element (CRERULES)\nExpression Column Element (EXPCOLUMN)\nSource Element Element (SRCELEMENT)\nName\nDescription\nExpression\nExpType\nAutCre\nDatabase View Element (DBVW)\nSource Element Element (SRCELEMENT)\nAttribute Column Element (ATTCOLUMN)\nCreate Rules Element (CRERULES)\nExpression Column Element (EXPCOLUMN)\nSource Element Element (SRCELEMENT)"}
{"Headers": "Status Definition Element (STADEF)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nIniVal\nInitial Value\nElelist\nTypes of elements, including UDETs, to which this applies\nIconL\nICONL\nIconS\nICONS\nName\nName of the element\nDescription\nDescription of the element\nIniVal\nInitial Value\nElelist\nTypes of elements, including UDETs, to which this applies\nIconL\nICONL\nIconS\nICONS\nStatus Definitions Group Element (STAGRP)\nStatus Configuration World Element (STAWLD)\nStatus Value Element (STAVAL)\nName\nName of the element\nDescription\nDescription of the element\nIniVal\nInitial Value\nElelist\nTypes of elements, including UDETs, to which this applies\nIconL\nICONL\nIconS\nICONS\n\n\n\nStatus Definitions Group Element (STAGRP)\nStatus Configuration World Element (STAWLD)\nStatus Value Element (STAVAL)\nName\nDescription\nIniVal\nElelist\nIconL\nIconS\nStatus Definitions Group Element (STAGRP)\nStatus Configuration World Element (STAWLD)\nStatus Value Element (STAVAL)"}
{"Headers": "Status Definitions Group Element (STAGRP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nStatus Configuration World Element (STAWLD)\nStatus Definition Element (STADEF)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nStatus Configuration World Element (STAWLD)\nStatus Definition Element (STADEF)\nName\nDescription\nStatus Configuration World Element (STAWLD)\nStatus Definition Element (STADEF)"}
{"Headers": "Status Link (STALNK)", "Content": "\nName\nName of the element\nType\nBoolean\nAbbreviation\nAllow delegation\nName\nName of the element\nType\nBoolean\nAbbreviation\nAllow delegation\n\nName\nName of the element\nType\nBoolean\nAbbreviation\nAllow delegation\n\n\n\nName\nType\nAbbreviation"}
{"Headers": "Status Value Element (STAVAL)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nValName\nLocal Name of a Status Value\nValNumber\nNumerical representation of a Status Value\nDemIx\nIndex of Demote Status Value\nPromIx\nIndex of Promote Status Value\nValArray\nValid Status Values\nIconL\nICONL\nIconS\nICONS\nReaLov\nList of Values for Status Reason\nName\nName of the element\nDescription\nDescription of the element\nValName\nLocal Name of a Status Value\nValNumber\nNumerical representation of a Status Value\nDemIx\nIndex of Demote Status Value\nPromIx\nIndex of Promote Status Value\nValArray\nValid Status Values\nIconL\nICONL\nIconS\nICONS\nReaLov\nList of Values for Status Reason\nStatus Definition Element (STADEF)\nNone\nName\nName of the element\nDescription\nDescription of the element\nValName\nLocal Name of a Status Value\nValNumber\nNumerical representation of a Status Value\nDemIx\nIndex of Demote Status Value\nPromIx\nIndex of Promote Status Value\nValArray\nValid Status Values\nIconL\nICONL\nIconS\nICONS\nReaLov\nList of Values for Status Reason\n\n\n\nStatus Definition Element (STADEF)\nName\nDescription\nValName\nValNumber\nDemIx\nPromIx\nValArray\nIconL\nIconS\nReaLov\nStatus Definition Element (STADEF)"}
{"Headers": "Status Configuration World Element (STAWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nStatus Definition Element (STADEF)\nStatus Definitions Group Element (STAGRP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nStatus Definition Element (STADEF)\nStatus Definitions Group Element (STAGRP)\nName\nDescription\nWorld Element (WORLD)\nStatus Definition Element (STADEF)\nStatus Definitions Group Element (STAGRP)"}
{"Headers": "Test Expression Element (TESTEXPRESSION)", "Content": "An expression used to return a boolean result for conditional processing.\nName\nName of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nName\nName of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\nSet Attribute Rule Element (SETATTRIBUTE)\nSet Status Rule Element (SETSTATUS)\nNone\nName\nName of the element\nExpression\nPML or XPath Expression to be executed\nExpType\nExpression syntax. Either PML or XPath\n\n\n\nSet Attribute Rule Element (SETATTRIBUTE)\nSet Status Rule Element (SETSTATUS)\nName\nExpression\nExpType\nSet Attribute Rule Element (SETATTRIBUTE)\nSet Status Rule Element (SETSTATUS)"}
{"Headers": "TMS Configuration Element (TMSCFG)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nTmsadp\nAutomatic Discipline Pulldown\nTmsaaa\nAutomatic Admin Approval\nAlwRename\nAllow Rename\nName\nName of the element\nDescription\nDescription of the element\nTmsadp\nAutomatic Discipline Pulldown\nTmsaaa\nAutomatic Admin Approval\nAlwRename\nAllow Rename\nEngineering Configuration World Element (ENGCWL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nTmsadp\nAutomatic Discipline Pulldown\nTmsaaa\nAutomatic Admin Approval\nAlwRename\nAllow Rename\n\n\n\nEngineering Configuration World Element (ENGCWL)\nName\nDescription\nTmsadp\nTmsaaa\nAlwRename\nEngineering Configuration World Element (ENGCWL)"}
{"Headers": "User Defined Attribute Element (UDA)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nUkey\nUDA key - internal unique system identifier\nAblength\nMinimum abbreviation length for a UDA/UDET user defined name\nLock\nLogical flag which determines if the UDAs attribute values are locked\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR\nUlength\nLength of data or text, arrays and Text Arrays. The maximum value is 214783647.\nDefaultLocation\nAttribute to follow to get default location\nDefaultAtt\nAttribute on default location to use for default\nDefaultExpression\nExpression used to calculate default\nUunits\nFor Real Attributes, the dimension of the attribute if applicable. (Examples, bore, length, angle, mass)\nTUNIt\nDefault unit of value (falls back to dimension default if not set) for Real Attributes with Uunitsset.\nOldkey\nOld key\nUdacpy\nUDA copy\nRptxt\nText used when presenting the attribute to the user\nElelist\nTypes of elements, including UDETs, to which this applies\nReflist\nTypes of elements (including UDETs) that can be pointed to by a reference attribute\nDflt\nDefault value for the attribute\nUcat\nCategory on forms\nUpseud\nSet true to calculate attribute value rather than store it in a database. User code must be provided\nUprote\nSet true to disallow viewing the attribute in a protected database\nUhide\nSet true to hide attribute on forms\nUNODUPLICATES\nSet false to dissallow duplicate values in the array\nUteams\nTeams that will see a hidden attribute\nUhyper\nSet true to treat attribute value as a named link to an external resource\nUconn\nTrue if the element referenced by UDA value should appear as a connection\nUdpend\nlist of attributes that this attribute depends on\nUdpsfg\nName of PML function used for value calculation. Function should take single parameter of DBREF type.\nUdpsfs\nName of PML function used for SET value. Function should take parameters of DBREF type and a value.\nUdtabl\nDetermines if UDA is to be indexed in a table for fast access\nULVOpt\nDetermines if UDA valid values or range limit is optional\nULVType\nDefines the use of list of value for a UDA, as Single select or Multiple select\nUdname\nUser defined name\nPrEdit\nEditor for property, not for use by end user\nPrConv\nConvertor for property, not for use by end user.\nPrEdit\nEditor for property\nPrConv\nConvertor for property\nUcases\nSet true to allow Engineering cases\nUclone\nPropagate to linked elements\nUVVFER\nAttribute to follow to get UDA valid values filtering element\nUMinlength\nMinimum length for text or word\nUSHVV\nUDA shared valid value\nLngVariant\nLanguage Variant, is attribute language variant. Applies to text attributes only\nCancopy\nControl of UDA copy through .NET Db API\nLock\nLogical flag which determines if the UDAs attribute values are locked\nName\nName of the element\nDescription\nDescription of the element\nUkey\nUDA key - internal unique system identifier\nAblength\nMinimum abbreviation length for a UDA/UDET user defined name\nLock\nLogical flag which determines if the UDAs attribute values are locked\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR\nUlength\nLength of data or text, arrays and Text Arrays. The maximum value is 214783647.\nDefaultLocation\nAttribute to follow to get default location\nDefaultAtt\nAttribute on default location to use for default\nDefaultExpression\nExpression used to calculate default\nUunits\nFor Real Attributes, the dimension of the attribute if applicable. (Examples, bore, length, angle, mass)\nTUNIt\nDefault unit of value (falls back to dimension default if not set) for Real Attributes with Uunitsset.\nOldkey\nOld key\nUdacpy\nUDA copy\nRptxt\nText used when presenting the attribute to the user\nElelist\nTypes of elements, including UDETs, to which this applies\nReflist\nTypes of elements (including UDETs) that can be pointed to by a reference attribute\nDflt\nDefault value for the attribute\nUcat\nCategory on forms\nUpseud\nSet true to calculate attribute value rather than store it in a database. User code must be provided\nUprote\nSet true to disallow viewing the attribute in a protected database\nUhide\nSet true to hide attribute on forms\nUNODUPLICATES\nSet false to dissallow duplicate values in the array\nUteams\nTeams that will see a hidden attribute\nUhyper\nSet true to treat attribute value as a named link to an external resource\nUconn\nTrue if the element referenced by UDA value should appear as a connection\nUdpend\nlist of attributes that this attribute depends on\nUdpsfg\nName of PML function used for value calculation. Function should take single parameter of DBREF type.\nUdpsfs\nName of PML function used for SET value. Function should take parameters of DBREF type and a value.\nUdtabl\nDetermines if UDA is to be indexed in a table for fast access\nULVOpt\nDetermines if UDA valid values or range limit is optional\nULVType\nDefines the use of list of value for a UDA, as Single select or Multiple select\nUdname\nUser defined name\nPrEdit\nEditor for property, not for use by end user\nPrConv\nConvertor for property, not for use by end user.\nPrEdit\nEditor for property\nPrConv\nConvertor for property\nUcases\nSet true to allow Engineering cases\nUclone\nPropagate to linked elements\nUVVFER\nAttribute to follow to get UDA valid values filtering element\nUMinlength\nMinimum length for text or word\nUSHVV\nUDA shared valid value\nLngVariant\nLanguage Variant, is attribute language variant. Applies to text attributes only\nCancopy\nControl of UDA copy through .NET Db API\nLock\nLogical flag which determines if the UDAs attribute values are locked\nUser Defined Attribute Group Element (UGROUP)\nUser Defined Attribute World Element (UWRLD)\nUser Defined Dynamic Limit Element (UDYLIM)\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)\nName\nName of the element\nDescription\nDescription of the element\nUkey\nUDA key - internal unique system identifier\nAblength\nMinimum abbreviation length for a UDA/UDET user defined name\nLock\nLogical flag which determines if the UDAs attribute values are locked\nUtype\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR\nUlength\nLength of data or text, arrays and Text Arrays. The maximum value is 214783647.\nDefaultLocation\nAttribute to follow to get default location\nDefaultAtt\nAttribute on default location to use for default\nDefaultExpression\nExpression used to calculate default\nUunits\nFor Real Attributes, the dimension of the attribute if applicable. (Examples, bore, length, angle, mass)\nTUNIt\nDefault unit of value (falls back to dimension default if not set) for Real Attributes with Uunitsset.\nOldkey\nOld key\nUdacpy\nUDA copy\nRptxt\nText used when presenting the attribute to the user\nElelist\nTypes of elements, including UDETs, to which this applies\nReflist\nTypes of elements (including UDETs) that can be pointed to by a reference attribute\nDflt\nDefault value for the attribute\nUcat\nCategory on forms\nUpseud\nSet true to calculate attribute value rather than store it in a database. User code must be provided\nUprote\nSet true to disallow viewing the attribute in a protected database\nUhide\nSet true to hide attribute on forms\nUNODUPLICATES\nSet false to dissallow duplicate values in the array\nUteams\nTeams that will see a hidden attribute\nUhyper\nSet true to treat attribute value as a named link to an external resource\nUconn\nTrue if the element referenced by UDA value should appear as a connection\nUdpend\nlist of attributes that this attribute depends on\nUdpsfg\nName of PML function used for value calculation. Function should take single parameter of DBREF type.\nUdpsfs\nName of PML function used for SET value. Function should take parameters of DBREF type and a value.\nUdtabl\nDetermines if UDA is to be indexed in a table for fast access\nULVOpt\nDetermines if UDA valid values or range limit is optional\nULVType\nDefines the use of list of value for a UDA, as Single select or Multiple select\nUdname\nUser defined name\nPrEdit\nEditor for property, not for use by end user\nPrConv\nConvertor for property, not for use by end user.\nPrEdit\nEditor for property\nPrConv\nConvertor for property\nUcases\nSet true to allow Engineering cases\nUclone\nPropagate to linked elements\nUVVFER\nAttribute to follow to get UDA valid values filtering element\nUMinlength\nMinimum length for text or word\nUSHVV\nUDA shared valid value\nLngVariant\nLanguage Variant, is attribute language variant. Applies to text attributes only\nCancopy\nControl of UDA copy through .NET Db API\nLock\nLogical flag which determines if the UDAs attribute values are locked\n\n\n\nUser Defined Attribute Group Element (UGROUP)\nUser Defined Attribute World Element (UWRLD)\nUser Defined Dynamic Limit Element (UDYLIM)\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)\nName\nDescription\nUkey\nAblength\nLock\nUtype\nUlength\nDefaultLocation\nDefaultAtt\nDefaultExpression\nUunits\nTUNIt\nOldkey\nUdacpy\nRptxt\nElelist\nReflist\nDflt\nUcat\nUpseud\nUprote\nUhide\nUNODUPLICATES\nUteams\nUhyper\nUconn\nUdpend\nUdpsfg\nUdpsfs\nUdtabl\nULVOpt\nULVType\nUdname\nPrEdit\nPrConv\nPrEdit\nPrConv\nUcases\nUclone\nUVVFER\nUMinlength\nUSHVV\nLngVariant\nCancopy\nLock\nUser Defined Attribute Group Element (UGROUP)\nUser Defined Attribute World Element (UWRLD)\nUser Defined Dynamic Limit Element (UDYLIM)\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)"}
{"Headers": "User Defined Element Element (UDET)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nUkey\nUDA key - internal unique system identifier\nBaseTy\nBase type for the user-defined element type\nUDMList\nList of allowed member types\nUDOList\nList of allowed owner types\nUDHLIS\nAttributes hidden on elements of this user-defined element type\nUdname\nUser defined name\nOldkey\nOld key\nName\nName of the element\nDescription\nDescription of the element\nUkey\nUDA key - internal unique system identifier\nBaseTy\nBase type for the user-defined element type\nUDMList\nList of allowed member types\nUDOList\nList of allowed owner types\nUDHLIS\nAttributes hidden on elements of this user-defined element type\nUdname\nUser defined name\nOldkey\nOld key\nUser Defined Element Group Element (UDETGR)\nUser Defined Element World Element (UDETWL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nUkey\nUDA key - internal unique system identifier\nBaseTy\nBase type for the user-defined element type\nUDMList\nList of allowed member types\nUDOList\nList of allowed owner types\nUDHLIS\nAttributes hidden on elements of this user-defined element type\nUdname\nUser defined name\nOldkey\nOld key\n\n\n\nUser Defined Element Group Element (UDETGR)\nUser Defined Element World Element (UDETWL)\nName\nDescription\nUkey\nBaseTy\nUDMList\nUDOList\nUDHLIS\nUdname\nOldkey\nUser Defined Element Group Element (UDETGR)\nUser Defined Element World Element (UDETWL)"}
{"Headers": "User Defined Element Group Element (UDETGR)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nUser Defined Element World Element (UDETWL)\nUser Defined Element Element (UDET)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nUser Defined Element World Element (UDETWL)\nUser Defined Element Element (UDET)\nName\nDescription\nUser Defined Element World Element (UDETWL)\nUser Defined Element Element (UDET)"}
{"Headers": "User Defined Element World Element (UDETWL)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nUser Defined Element Element (UDET)\nUser Defined Element Group Element (UDETGR)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nUser Defined Element Element (UDET)\nUser Defined Element Group Element (UDETGR)\nName\nDescription\nWorld Element (WORLD)\nUser Defined Element Element (UDET)\nUser Defined Element Group Element (UDETGR)"}
{"Headers": "User Defined List Of Values Element (UDLOV)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nUsysty\nName of the system attribute\nValType\nType of the value. INT, REAL or TEXT\nName\nName of the element\nDescription\nDescription of the element\nUsysty\nName of the system attribute\nValType\nType of the value. INT, REAL or TEXT\nUser Defined Attribute Group Element (UGROUP)\nUser Defined Dynamic Limit Element (UDYLIM)\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)\nName\nName of the element\nDescription\nDescription of the element\nUsysty\nName of the system attribute\nValType\nType of the value. INT, REAL or TEXT\n\n\n\nUser Defined Attribute Group Element (UGROUP)\nUser Defined Dynamic Limit Element (UDYLIM)\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)\nName\nDescription\nUsysty\nValType\nUser Defined Attribute Group Element (UGROUP)\nUser Defined Dynamic Limit Element (UDYLIM)\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)"}
{"Headers": "Engineering Types Classification Element (UDTCLA)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nEngineering Configuration World Element (ENGCWL)\nDiscipline Related Types Element (DISUDT)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nEngineering Configuration World Element (ENGCWL)\nDiscipline Related Types Element (DISUDT)\nName\nDescription\nEngineering Configuration World Element (ENGCWL)\nDiscipline Related Types Element (DISUDT)"}
{"Headers": "User Defined Type Group Filter Element Element (UDTELE)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nElelist\nTypes of elements, including UDETs, to which this applies\nUdtExpression\nuser Defined Type Group Expression\nName\nName of the element\nDescription\nDescription of the element\nElelist\nTypes of elements, including UDETs, to which this applies\nUdtExpression\nuser Defined Type Group Expression\nUser Defined Type Group Element (UDTG)\nNone\nName\nName of the element\nDescription\nDescription of the element\nElelist\nTypes of elements, including UDETs, to which this applies\nUdtExpression\nuser Defined Type Group Expression\n\n\n\nUser Defined Type Group Element (UDTG)\nName\nDescription\nElelist\nUdtExpression\nUser Defined Type Group Element (UDTG)"}
{"Headers": "User Defined Type Group Element (UDTG)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nUkey\nUDA key - internal unique system identifier\nUdname\nUser defined name\nIconS\nICONS\nName\nName of the element\nDescription\nDescription of the element\nUkey\nUDA key - internal unique system identifier\nUdname\nUser defined name\nIconS\nICONS\nUser Defined Type Group World Element (UDTW)\nUser Defined Type Group Filter Element Element (UDTELE)\nName\nName of the element\nDescription\nDescription of the element\nUkey\nUDA key - internal unique system identifier\nUdname\nUser defined name\nIconS\nICONS\n\n\n\nUser Defined Type Group World Element (UDTW)\nUser Defined Type Group Filter Element Element (UDTELE)\nName\nDescription\nUkey\nUdname\nIconS\nUser Defined Type Group World Element (UDTW)\nUser Defined Type Group Filter Element Element (UDTELE)"}
{"Headers": "Engineering Type Interface Element (UDTINT)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDbeletype\nElement type\nName\nName of the element\nDescription\nDescription of the element\nDbeletype\nElement type\nEngineering Interface Definition Element (INTDEF)\nEngineering Interface Attribute Element (INTATT)\nName\nName of the element\nDescription\nDescription of the element\nDbeletype\nElement type\n\n\n\nEngineering Interface Definition Element (INTDEF)\nEngineering Interface Attribute Element (INTATT)\nName\nDescription\nDbeletype\nEngineering Interface Definition Element (INTDEF)\nEngineering Interface Attribute Element (INTATT)"}
{"Headers": "User Defined Type Group World Element (UDTW)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nUser Defined Type Group Element (UDTG)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nUser Defined Type Group Element (UDTG)\nName\nDescription\nWorld Element (WORLD)\nUser Defined Type Group Element (UDTG)"}
{"Headers": "User Defined Dynamic Limit Element (UDYLIM)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nUexmin\nExpression defining the minimum value\nUexmax\nExpression defining the maximum value\nName\nName of the element\nDescription\nDescription of the element\nUexmin\nExpression defining the minimum value\nUexmax\nExpression defining the maximum value\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)\nNone\nName\nName of the element\nDescription\nDescription of the element\nUexmin\nExpression defining the minimum value\nUexmax\nExpression defining the maximum value\n\n\n\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)\nName\nDescription\nUexmin\nUexmax\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)"}
{"Headers": "User Defined Attribute Group Element (UGROUP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nUser Defined Attribute World Element (UWRLD)\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nUser Defined Attribute World Element (UWRLD)\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)\nName\nDescription\nUser Defined Attribute World Element (UWRLD)\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)"}
{"Headers": "User Defined Limit Element (ULIMIT)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nUmin\nMinimum value\nUmax\nMaximum value\nName\nName of the element\nDescription\nDescription of the element\nUmin\nMinimum value\nUmax\nMaximum value\nConfig Key Element (CFGKEY)\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)\nNone\nName\nName of the element\nDescription\nDescription of the element\nUmin\nMinimum value\nUmax\nMaximum value\n\n\n\nConfig Key Element (CFGKEY)\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)\nName\nDescription\nUmin\nUmax\nConfig Key Element (CFGKEY)\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)"}
{"Headers": "Unit Set Element (UNTST)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nUntstDimension\nUnit set dimension\nUntstSystem\nUnit set system\nDecsep\nDecimal separator\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nUntstDimension\nUnit set dimension\nUntstSystem\nUnit set system\nDecsep\nDecimal separator\nUnit Sets Group Element (UNTSTGROUP)\nUnit Sets World Element (UNTSTWORLD)\nUnit Set Unit Element (UNTSTUNIT)\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nUntstDimension\nUnit set dimension\nUntstSystem\nUnit set system\nDecsep\nDecimal separator\n\n\n\nUnit Sets Group Element (UNTSTGROUP)\nUnit Sets World Element (UNTSTWORLD)\nUnit Set Unit Element (UNTSTUNIT)\nName\nDescription\nUdname\nUntstDimension\nUntstSystem\nDecsep\nUnit Sets Group Element (UNTSTGROUP)\nUnit Sets World Element (UNTSTWORLD)\nUnit Set Unit Element (UNTSTUNIT)"}
{"Headers": "Unit Sets Group Element (UNTSTGROUP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nUnit Sets World Element (UNTSTWORLD)\nUnit Set Element (UNTST)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nUnit Sets World Element (UNTSTWORLD)\nUnit Set Element (UNTST)\nName\nDescription\nUnit Sets World Element (UNTSTWORLD)\nUnit Set Element (UNTST)"}
{"Headers": "Unit Set Unit Element (UNTSTUNIT)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nUsuval\nUnit for Unit Set\nUntord\nUnit order\nDecprc\nDecimal precision\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nUsuval\nUnit for Unit Set\nUntord\nUnit order\nDecprc\nDecimal precision\nUnit Set Element (UNTST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nUdname\nUser defined name\nUsuval\nUnit for Unit Set\nUntord\nUnit order\nDecprc\nDecimal precision\n\n\n\nUnit Set Element (UNTST)\nName\nDescription\nUdname\nUsuval\nUntord\nDecprc\nUnit Set Element (UNTST)"}
{"Headers": "Unit Sets World Element (UNTSTWORLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nUnit Sets Group Element (UNTSTGROUP)\nUnit Set Element (UNTST)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nUnit Sets Group Element (UNTSTGROUP)\nUnit Set Element (UNTST)\nName\nDescription\nWorld Element (WORLD)\nUnit Sets Group Element (UNTSTGROUP)\nUnit Set Element (UNTST)"}
{"Headers": "User System Defined Attribute Element (USDA)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nUsysty\nName of the system attribute\nUall\nUALL\nElelist\nTypes of elements (including UDETs) to which this attribute applies\nUcat\nCategory on forms\nUhide\nSet true to hide attribute on forms\nULVOpt\nDetermines if UDA valid values or range limit is optional\nUteams\nTeams that will see a hidden attribute\nName\nName of the element\nDescription\nDescription of the element\nUsysty\nName of the system attribute\nUall\nUALL\nElelist\nTypes of elements (including UDETs) to which this attribute applies\nUcat\nCategory on forms\nUhide\nSet true to hide attribute on forms\nULVOpt\nDetermines if UDA valid values or range limit is optional\nUteams\nTeams that will see a hidden attribute\nUser Defined Attribute Group Element (UGROUP)\nUser Defined Dynamic Limit Element (UDYLIM)\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)\nName\nName of the element\nDescription\nDescription of the element\nUsysty\nName of the system attribute\nUall\nUALL\nElelist\nTypes of elements (including UDETs) to which this attribute applies\nUcat\nCategory on forms\nUhide\nSet true to hide attribute on forms\nULVOpt\nDetermines if UDA valid values or range limit is optional\nUteams\nTeams that will see a hidden attribute\n\n\n\nUser Defined Attribute Group Element (UGROUP)\nUser Defined Dynamic Limit Element (UDYLIM)\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)\nName\nDescription\nUsysty\nUall\nElelist\nUcat\nUhide\nULVOpt\nUteams\nUser Defined Attribute Group Element (UGROUP)\nUser Defined Dynamic Limit Element (UDYLIM)\nUser Defined Limit Element (ULIMIT)\nUser Defined Valid Value Element (UVALID)"}
{"Headers": "User Defined Valid Value Element (UVALID)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nUvval\nValid value for UDA\nUcval\nreferenced to controlling UVALID\nUDescription\nFull description of the element\nName\nName of the element\nDescription\nDescription of the element\nUvval\nValid value for UDA\nUcval\nreferenced to controlling UVALID\nUDescription\nFull description of the element\nConfig Key Element (CFGKEY)\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)\nNone\nName\nName of the element\nDescription\nDescription of the element\nUvval\nValid value for UDA\nUcval\nreferenced to controlling UVALID\nUDescription\nFull description of the element\n\n\n\nConfig Key Element (CFGKEY)\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)\nName\nDescription\nUvval\nUcval\nUDescription\nConfig Key Element (CFGKEY)\nUser Defined Attribute Element (UDA)\nUser Defined List Of Values Element (UDLOV)\nUser System Defined Attribute Element (USDA)"}
{"Headers": "User Defined Attribute World Element (UWRLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nUser Defined Attribute Element (UDA)\nUser Defined Attribute Group Element (UGROUP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nUser Defined Attribute Element (UDA)\nUser Defined Attribute Group Element (UGROUP)\nName\nDescription\nWorld Element (WORLD)\nUser Defined Attribute Element (UDA)\nUser Defined Attribute Group Element (UGROUP)"}
{"Headers": "Version Control Configuration Element (VERCON)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nRvcon\nRevision Configuration\nIssExt\nStates to issue extracts\nNotify\nNotification states\nGrrel\nGoverning revision relationship type\nName\nName of the element\nDescription\nDescription of the element\nRvcon\nRevision Configuration\nIssExt\nStates to issue extracts\nNotify\nNotification states\nGrrel\nGoverning revision relationship type\nRevision Configuration Group Element (REVCGP)\nNone\nName\nName of the element\nDescription\nDescription of the element\nRvcon\nRevision Configuration\nIssExt\nStates to issue extracts\nNotify\nNotification states\nGrrel\nGoverning revision relationship type\n\n\n\nRevision Configuration Group Element (REVCGP)\nName\nDescription\nRvcon\nIssExt\nNotify\nGrrel\nRevision Configuration Group Element (REVCGP)"}
{"Headers": "World Element (WORLD) - Dictionairy", "Content": "Administrative Element\nPrimary Element\nThe WORLD is the topmost level of the database hierarchy within which all other elements exist. It cannot be deleted or copied in the same way that applies to say, a ZONE or a DRWG. Its existence is controlled by the ADMINISTRATION module.\nName\nName of the element\nName\nName of the element\nNone\nCalculation Template World Element (CALWLD)\nConfig Group World Element (CFGGPW)\nDatabase View World Element (DBVWWLD)\nDatasheet Template World Element (DSTWLD)\nDistributed Attribute Definition World Element (DSXWLD)\nEngineering Configuration World Element (ENGCWL)\nFlexible Explorer Templates World Element (PBSWLD)\nRevision Configuration World Element (REVCWL)\nNaming Rules World Element (RULWLD)\nStatus Configuration World Element (STAWLD)\nUser Defined Element World Element (UDETWL)\nUser Defined Type Group World Element (UDTW)\nUnit Sets World Element (UNTSTWORLD)\nUser Defined Attribute World Element (UWRLD)\nName\nName of the element\n\n\n\nCalculation Template World Element (CALWLD)\nConfig Group World Element (CFGGPW)\nDatabase View World Element (DBVWWLD)\nDatasheet Template World Element (DSTWLD)\nDistributed Attribute Definition World Element (DSXWLD)\nEngineering Configuration World Element (ENGCWL)\nFlexible Explorer Templates World Element (PBSWLD)\nRevision Configuration World Element (REVCWL)\nNaming Rules World Element (RULWLD)\nStatus Configuration World Element (STAWLD)\nUser Defined Element World Element (UDETWL)\nUser Defined Type Group World Element (UDTW)\nUnit Sets World Element (UNTSTWORLD)\nUser Defined Attribute World Element (UWRLD)\nName\nCalculation Template World Element (CALWLD)\nConfig Group World Element (CFGGPW)\nDatabase View World Element (DBVWWLD)\nDatasheet Template World Element (DSTWLD)\nDistributed Attribute Definition World Element (DSXWLD)\nEngineering Configuration World Element (ENGCWL)\nFlexible Explorer Templates World Element (PBSWLD)\nRevision Configuration World Element (REVCWL)\nNaming Rules World Element (RULWLD)\nStatus Configuration World Element (STAWLD)\nUser Defined Element World Element (UDETWL)\nUser Defined Type Group World Element (UDTW)\nUnit Sets World Element (UNTSTWORLD)\nUser Defined Attribute World Element (UWRLD)"}
{"Headers": "Draft Database Elements", "Content": "All data in the Draft database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n"}
{"Headers": "Annotation Change Style Element (ACSTYLE)", "Content": "Draft Representation Definition Element\nName\nName of the element\nTpen\nText pen\nNlpen\nNote/framing pen\nFpen\nFill pen\nFont\nText font\nBrackets\nBrackets code\nUnderline\nUnderling flag\nTxcolour\nText colour\nTxtrgb\nRGB text colour\nNLStyle\nNote linestyle\nNLColour\nNote colour\nColrgb\nRGB colour\nFStyle\nFill style\nFColour\nFill colour\nFilrgb\nRGB fill colour\nName\nName of the element\nTpen\nText pen\nNlpen\nNote/framing pen\nFpen\nFill pen\nFont\nText font\nBrackets\nBrackets code\nUnderline\nUnderling flag\nTxcolour\nText colour\nTxtrgb\nRGB text colour\nNLStyle\nNote linestyle\nNLColour\nNote colour\nColrgb\nRGB colour\nFStyle\nFill style\nFColour\nFill colour\nFilrgb\nRGB fill colour\nRepresentation Rules and Styles Library Element (RPLB)\nNone\nName\nName of the element\nTpen\nText pen\nNlpen\nNote/framing pen\nFpen\nFill pen\nFont\nText font\nBrackets\nBrackets code\nUnderline\nUnderling flag\nTxcolour\nText colour\nTxtrgb\nRGB text colour\nNLStyle\nNote linestyle\nNLColour\nNote colour\nColrgb\nRGB colour\nFStyle\nFill style\nFColour\nFill colour\nFilrgb\nRGB fill colour\n\n\n\nRepresentation Rules and Styles Library Element (RPLB)\nName\nTpen\nNlpen\nFpen\nFont\nBrackets\nUnderline\nTxcolour\nTxtrgb\nNLStyle\nNLColour\nColrgb\nFStyle\nFColour\nFilrgb\nRepresentation Rules and Styles Library Element (RPLB)"}
{"Headers": "Add Entry Element (ADDENTRY)", "Content": "Draft IDList Definition Element\nName\nName of the element\nIdname\nDesign data or catalogue component\nIdnx\nDesign data or catalogue component (as text)\nCriteria\nSelection criteria (used to define tag & rep. rules)\nName\nName of the element\nIdname\nDesign data or catalogue component\nIdnx\nDesign data or catalogue component (as text)\nCriteria\nSelection criteria (used to define tag & rep. rules)\nID List Element (IDLIST)\nNone\nName\nName of the element\nIdname\nDesign data or catalogue component\nIdnx\nDesign data or catalogue component (as text)\nCriteria\nSelection criteria (used to define tag & rep. rules)\n\n\n\nID List Element (IDLIST)\nName\nIdname\nIdnx\nCriteria\nID List Element (IDLIST)"}
{"Headers": "Global Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the Global database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "Global Database Elements", "Content": "All data in the Global database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Baseline Element (BASLIN) - Global", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\nGlobal Baseline World Element (GBASEWORLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\n\n\n\nGlobal Baseline World Element (GBASEWORLD)\nName\nDescription\nDname\nPrcode\nWRKSHR\nGlobal Baseline World Element (GBASEWORLD)"}
{"Headers": "Database Element (DB) - Global", "Content": "Primary Element\nNumbdb\nDB number\nStype\nSPECON type question\nFino\nFile number\nArea\nArea\nAccessdb\nDB access\nClaimdb\nImplicit or explicit claims\nDescription\nDescription of the element\nTpArea\nTemplated Project Area Name\nTpDiscipline\nTemplated Project Discipline Name\nProjid\nPROJID - on the DB element\nFcpyref\nForward copy reference\nBcpyref\nBackward copy reference\nExtNo\nExtract number\nExtOwner\nExtract owner\nLVariant\nVariant Flag\nLCtrolled\nControlled DB Flag\nName\nName of the element\nLRefOnly\nDatabase holds Reference data only flag\nLConsumer\nConsumer Extract database flag, can be refreshed when read-only\nLSvHistory\nDatabase save history from compaction flag\nNumbdb\nDB number\nStype\nSPECON type question\nFino\nFile number\nArea\nArea\nAccessdb\nDB access\nClaimdb\nImplicit or explicit claims\nDescription\nDescription of the element\nTpArea\nTemplated Project Area Name\nTpDiscipline\nTemplated Project Discipline Name\nProjid\nPROJID - on the DB element\nFcpyref\nForward copy reference\nBcpyref\nBackward copy reference\nExtNo\nExtract number\nExtOwner\nExtract owner\nLVariant\nVariant Flag\nLCtrolled\nControlled DB Flag\nName\nName of the element\nLRefOnly\nDatabase holds Reference data only flag\nLConsumer\nConsumer Extract database flag, can be refreshed when read-only\nLSvHistory\nDatabase save history from compaction flag\nDatabase List Element (DBLI)\nDatabase Location Information Element (DBLOC)\nNumbdb\nDB number\nStype\nSPECON type question\nFino\nFile number\nArea\nArea\nAccessdb\nDB access\nClaimdb\nImplicit or explicit claims\nDescription\nDescription of the element\nTpArea\nTemplated Project Area Name\nTpDiscipline\nTemplated Project Discipline Name\nProjid\nPROJID - on the DB element\nFcpyref\nForward copy reference\nBcpyref\nBackward copy reference\nExtNo\nExtract number\nExtOwner\nExtract owner\nLVariant\nVariant Flag\nLCtrolled\nControlled DB Flag\nName\nName of the element\nLRefOnly\nDatabase holds Reference data only flag\nLConsumer\nConsumer Extract database flag, can be refreshed when read-only\nLSvHistory\nDatabase save history from compaction flag\n\n\n\nDatabase List Element (DBLI)\nDatabase Location Information Element (DBLOC)\nNumbdb\nStype\nFino\nArea\nAccessdb\nClaimdb\nDescription\nTpArea\nTpDiscipline\nProjid\nFcpyref\nBcpyref\nExtNo\nExtOwner\nLVariant\nLCtrolled\nName\nLRefOnly\nLConsumer\nLSvHistory\nDatabase List Element (DBLI)\nDatabase Location Information Element (DBLOC)"}
{"Headers": "Global List of DBs Allocated to Location Element (DBALL)", "Content": "DeAlAll\nTrue if location locked due to deallocation of dbs\nDeAlAll\nTrue if location locked due to deallocation of dbs\nGlobal Location Element (LOC)\nDatabase Element (DB)\nDeAlAll\nTrue if location locked due to deallocation of dbs\n\n\n\nGlobal Location Element (LOC)\nDatabase Element (DB)\nDeAlAll\nGlobal Location Element (LOC)\nDatabase Element (DB)"}
{"Headers": "Database List Element (DBLI) - Global", "Content": "Primary Element\n\n\n\nTeam Element (TEAM)\nDatabase Element (DB)\n\n\n\n\nTeam Element (TEAM)\nDatabase Element (DB)\nTeam Element (TEAM)\nDatabase Element (DB)"}
{"Headers": "Database Location Information Element (DBLOC)", "Content": "Primary Element\nLocrf\nLocation reference\nPrvrf\nReference to previous owner of DB\nPropg\nDB propagation flag\nPicfd\nPicture file distribution flag\nNoLnkPropagation\nLinked Documents distribution disabled\nDeAlDB\nReference array for locations where DB id being deallocated\nLocrf\nLocation reference\nPrvrf\nReference to previous owner of DB\nPropg\nDB propagation flag\nPicfd\nPicture file distribution flag\nNoLnkPropagation\nLinked Documents distribution disabled\nDeAlDB\nReference array for locations where DB id being deallocated\nDatabase Element (DB)\nNone\nLocrf\nLocation reference\nPrvrf\nReference to previous owner of DB\nPropg\nDB propagation flag\nPicfd\nPicture file distribution flag\nNoLnkPropagation\nLinked Documents distribution disabled\nDeAlDB\nReference array for locations where DB id being deallocated\n\n\n\nDatabase Element (DB)\nLocrf\nPrvrf\nPropg\nPicfd\nNoLnkPropagation\nDeAlDB\nDatabase Element (DB)"}
{"Headers": "DB Range Element (DBRANG) - Global", "Content": "Primary Element\nName\nName of the element\nDBRBEG\nDB range start\nDBREND\nDB range end\nName\nName of the element\nDBRBEG\nDB range start\nDBREND\nDB range end\nGlobal Status World Element (GSTAT)\nNone\nName\nName of the element\nDBRBEG\nDB range start\nDBREND\nDB range end\n\n\n\nGlobal Status World Element (GSTAT)\nName\nDBRBEG\nDBREND\nGlobal Status World Element (GSTAT)"}
{"Headers": "Discipline Element (DISCIPLINE)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\nPRDBSN\nStart DB Number\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\nPRDBSN\nStart DB Number\nGlobal Discipline World Element (GDISCWORLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\nPRDBSN\nStart DB Number\n\n\n\nGlobal Discipline World Element (GDISCWORLD)\nName\nDescription\nDname\nPrcode\nWRKSHR\nPRDBSN\nGlobal Discipline World Element (GDISCWORLD)"}
{"Headers": "Global Baseline World Element (GBASEWORLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nBaseline Element (BASLIN)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nBaseline Element (BASLIN)\nName\nWorld Element (WORLD)\nBaseline Element (BASLIN)"}
{"Headers": "Global Discipline World Element (GDISCWORLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nDiscipline Element (DISCIPLINE)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nDiscipline Element (DISCIPLINE)\nName\nWorld Element (WORLD)\nDiscipline Element (DISCIPLINE)"}
{"Headers": "Global Location World Element (GLOCWL)", "Content": "Primary Element\nName\nName of the element\nAduuid\nUUID to ensure Project uniqueness\nGlbVersion\nGlobal version string\nHubrf\nReference to the hub location\nPrvrf\nReference to previous owner of DB\nNxtHb\nReference to next (future) hub\nGLinkPropagation\nProject has Linked Documents distribution enabled\nName\nName of the element\nAduuid\nUUID to ensure Project uniqueness\nGlbVersion\nGlobal version string\nHubrf\nReference to the hub location\nPrvrf\nReference to previous owner of DB\nNxtHb\nReference to next (future) hub\nGLinkPropagation\nProject has Linked Documents distribution enabled\nWorld Element (WORLD)\nGlobal Group List Element (GRPLI)\nGlobal Link List Element (LNKLI)\nGlobal Location List Element (LOCLI)\nName\nName of the element\nAduuid\nUUID to ensure Project uniqueness\nGlbVersion\nGlobal version string\nHubrf\nReference to the hub location\nPrvrf\nReference to previous owner of DB\nNxtHb\nReference to next (future) hub\nGLinkPropagation\nProject has Linked Documents distribution enabled\n\n\n\nWorld Element (WORLD)\nGlobal Group List Element (GRPLI)\nGlobal Link List Element (LNKLI)\nGlobal Location List Element (LOCLI)\nName\nAduuid\nGlbVersion\nHubrf\nPrvrf\nNxtHb\nGLinkPropagation\nWorld Element (WORLD)\nGlobal Group List Element (GRPLI)\nGlobal Link List Element (LNKLI)\nGlobal Location List Element (LOCLI)"}
{"Headers": "Global Maturity World Element (GMATUWORLD)", "Content": "Primary Element\nName\nName of the element\nMlvref\nReference to the Shared Maturity Level\nName\nName of the element\nMlvref\nReference to the Shared Maturity Level\nWorld Element (WORLD)\nMaturity Level Element (MATURITY)\nName\nName of the element\nMlvref\nReference to the Shared Maturity Level\n\n\n\nWorld Element (WORLD)\nMaturity Level Element (MATURITY)\nName\nMlvref\nWorld Element (WORLD)\nMaturity Level Element (MATURITY)"}
{"Headers": "Global Project Definition World Element (GPRDEWORLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nProject Definition Element (PRDEFDB)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nProject Definition Element (PRDEFDB)\nName\nWorld Element (WORLD)\nProject Definition Element (PRDEFDB)"}
{"Headers": "Global Role World Element (GROLWL)", "Content": "Primary Element\nName\nName of the element\nLACR\nAccess Control on/off switch\nName\nName of the element\nLACR\nAccess Control on/off switch\nWorld Element (WORLD)\nRole Element (ROLE)\nName\nName of the element\nLACR\nAccess Control on/off switch\n\n\n\nWorld Element (WORLD)\nRole Element (ROLE)\nName\nLACR\nWorld Element (WORLD)\nRole Element (ROLE)"}
{"Headers": "Global Group Element (GRP)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nGlobal Group List Element (GRPLI)\nNone\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nGlobal Group List Element (GRPLI)\nName\nDescription\nGlobal Group List Element (GRPLI)"}
{"Headers": "Global Group List Element (GRPLI)", "Content": "Primary Element\n\n\n\nGlobal Location World Element (GLOCWL)\nGlobal Group Element (GRP)\n\n\n\n\nGlobal Location World Element (GLOCWL)\nGlobal Group Element (GRP)\nGlobal Location World Element (GLOCWL)\nGlobal Group Element (GRP)"}
{"Headers": "Global Status World Element (GSTAT)", "Content": "Primary Element\nName\nName of the element\nPrjnumber\nProject number\nMaxusers\nMaximum number of user\nPrjdesc\nProject description\nInfa\nClient info - Project Name\nCharset\nCharacter set\nPrjstatus\nAccess Control project status\nAduuid\nUUID to ensure Project uniqueness\nUTCSWT\nTrue if System outputs UTC based Session Date Times\nName\nName of the element\nPrjnumber\nProject number\nMaxusers\nMaximum number of user\nPrjdesc\nProject description\nInfa\nClient info - Project Name\nCharset\nCharacter set\nPrjstatus\nAccess Control project status\nAduuid\nUUID to ensure Project uniqueness\nUTCSWT\nTrue if System outputs UTC based Session Date Times\nWorld Element (WORLD)\nDB Range Element (DBRANG)\nName\nName of the element\nPrjnumber\nProject number\nMaxusers\nMaximum number of user\nPrjdesc\nProject description\nInfa\nClient info - Project Name\nCharset\nCharacter set\nPrjstatus\nAccess Control project status\nAduuid\nUUID to ensure Project uniqueness\nUTCSWT\nTrue if System outputs UTC based Session Date Times\n\n\n\nWorld Element (WORLD)\nDB Range Element (DBRANG)\nName\nPrjnumber\nMaxusers\nPrjdesc\nInfa\nCharset\nPrjstatus\nAduuid\nUTCSWT\nWorld Element (WORLD)\nDB Range Element (DBRANG)"}
{"Headers": "Global Stamp World Element (GSTWLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nStamp Element (STAMP)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nStamp Element (STAMP)\nName\nWorld Element (WORLD)\nStamp Element (STAMP)"}
{"Headers": "Global Team World Element (GTMWL)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nTeam Element (TEAM)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nTeam Element (TEAM)\nName\nWorld Element (WORLD)\nTeam Element (TEAM)"}
{"Headers": "Global Link Element (LNK)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nLnkrx\nReference to first location of a link\nLnkry\nReference to second location of a link\nLnkwv\nLink weighting value\nName\nName of the element\nDescription\nDescription of the element\nLnkrx\nReference to first location of a link\nLnkry\nReference to second location of a link\nLnkwv\nLink weighting value\nGlobal Link List Element (LNKLI)\nNone\nName\nName of the element\nDescription\nDescription of the element\nLnkrx\nReference to first location of a link\nLnkry\nReference to second location of a link\nLnkwv\nLink weighting value\n\n\n\nGlobal Link List Element (LNKLI)\nName\nDescription\nLnkrx\nLnkry\nLnkwv\nGlobal Link List Element (LNKLI)"}
{"Headers": "Global Link List Element (LNKLI)", "Content": "Primary Element\n\n\n\nGlobal Location World Element (GLOCWL)\nGlobal Link Element (LNK)\n\n\n\n\nGlobal Location World Element (GLOCWL)\nGlobal Link Element (LNK)\nGlobal Location World Element (GLOCWL)\nGlobal Link Element (LNK)"}
{"Headers": "Global Location Element (LOC)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nLocid\nLocation identifier\nRhost\nHost computer name or IP address of remote machine\nIconn\nCOMMS connection type (0/1 = on/off-line)\nLinit\nLocation initialisation flag\nGrprf\nReference to group (owner of location)\nLocrf\nLocation reference\nPrmrf\nPrimary Location Element\nPrvrf\nReference to previous owner of DB\nExtlow\nLocation extract number range, low limit\nExthigh\nLocation extract number range, high limit\nLCpOvWrite\nLocation Overwrite DB Users policy flag\nNoExtCreation\nLocation extract create suppression flag\nNumbdb\nDB number\nName\nName of the element\nDescription\nDescription of the element\nLocid\nLocation identifier\nRhost\nHost computer name or IP address of remote machine\nIconn\nCOMMS connection type (0/1 = on/off-line)\nLinit\nLocation initialisation flag\nGrprf\nReference to group (owner of location)\nLocrf\nLocation reference\nPrmrf\nPrimary Location Element\nPrvrf\nReference to previous owner of DB\nExtlow\nLocation extract number range, low limit\nExthigh\nLocation extract number range, high limit\nLCpOvWrite\nLocation Overwrite DB Users policy flag\nNoExtCreation\nLocation extract create suppression flag\nNumbdb\nDB number\nGlobal Location List Element (LOCLI)\nGlobal List of DBs Allocated to Location Element (DBALL)\nName\nName of the element\nDescription\nDescription of the element\nLocid\nLocation identifier\nRhost\nHost computer name or IP address of remote machine\nIconn\nCOMMS connection type (0/1 = on/off-line)\nLinit\nLocation initialisation flag\nGrprf\nReference to group (owner of location)\nLocrf\nLocation reference\nPrmrf\nPrimary Location Element\nPrvrf\nReference to previous owner of DB\nExtlow\nLocation extract number range, low limit\nExthigh\nLocation extract number range, high limit\nLCpOvWrite\nLocation Overwrite DB Users policy flag\nNoExtCreation\nLocation extract create suppression flag\nNumbdb\nDB number\n\n\n\nGlobal Location List Element (LOCLI)\nGlobal List of DBs Allocated to Location Element (DBALL)\nName\nDescription\nLocid\nRhost\nIconn\nLinit\nGrprf\nLocrf\nPrmrf\nPrvrf\nExtlow\nExthigh\nLCpOvWrite\nNoExtCreation\nNumbdb\nGlobal Location List Element (LOCLI)\nGlobal List of DBs Allocated to Location Element (DBALL)"}
{"Headers": "Global Location List Element (LOCLI)", "Content": "Primary Element\nExtlow\nLocation extract number range, low limit\nExthigh\nLocation extract number range, high limit\nExtlow\nLocation extract number range, low limit\nExthigh\nLocation extract number range, high limit\nGlobal Location World Element (GLOCWL)\nGlobal Location Element (LOC)\nExtlow\nLocation extract number range, low limit\nExthigh\nLocation extract number range, high limit\n\n\n\nGlobal Location World Element (GLOCWL)\nGlobal Location Element (LOC)\nExtlow\nExthigh\nGlobal Location World Element (GLOCWL)\nGlobal Location Element (LOC)"}
{"Headers": "Maturity Level Element (MATURITY) - Global", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nMatowner\nMaturity Owning Element\nDiscif\nReference of DISCIPLINE Element\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nMatowner\nMaturity Owning Element\nDiscif\nReference of DISCIPLINE Element\nGlobal Maturity World Element (GMATUWORLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nMatowner\nMaturity Owning Element\nDiscif\nReference of DISCIPLINE Element\n\n\n\nGlobal Maturity World Element (GMATUWORLD)\nName\nDescription\nDname\nPrcode\nMatowner\nDiscif\nGlobal Maturity World Element (GMATUWORLD)"}
{"Headers": "Permissible Operations Element (PEROP) - Global", "Content": "Name\nName of the element\nOpcreate\nCreate Access Control Operation\nOpmodify\nModify Access Control Operation\nOpdelete\nDelete Access Control Operation\nOpclaim\nClaim Access Control Operation\nOpissue\nIssue Access Control Operation\nOpdrop\nDrop Access Control Operation\nOpoutput\nOutput (DATAL) Access Control Operation\nOpexport\nExport Access Control Operation\nOpcopyfrom\nCopy-From Access Control Operation\nEclass\nAccess Control Element class\nAclass\nAccess Control Attribute class\nCondition\nAccess Control Logical condition\nAcrmessage\nAccess Control User defined message\nName\nName of the element\nOpcreate\nCreate Access Control Operation\nOpmodify\nModify Access Control Operation\nOpdelete\nDelete Access Control Operation\nOpclaim\nClaim Access Control Operation\nOpissue\nIssue Access Control Operation\nOpdrop\nDrop Access Control Operation\nOpoutput\nOutput (DATAL) Access Control Operation\nOpexport\nExport Access Control Operation\nOpcopyfrom\nCopy-From Access Control Operation\nEclass\nAccess Control Element class\nAclass\nAccess Control Attribute class\nCondition\nAccess Control Logical condition\nAcrmessage\nAccess Control User defined message\nRole Element (ROLE)\nNone\nName\nName of the element\nOpcreate\nCreate Access Control Operation\nOpmodify\nModify Access Control Operation\nOpdelete\nDelete Access Control Operation\nOpclaim\nClaim Access Control Operation\nOpissue\nIssue Access Control Operation\nOpdrop\nDrop Access Control Operation\nOpoutput\nOutput (DATAL) Access Control Operation\nOpexport\nExport Access Control Operation\nOpcopyfrom\nCopy-From Access Control Operation\nEclass\nAccess Control Element class\nAclass\nAccess Control Attribute class\nCondition\nAccess Control Logical condition\nAcrmessage\nAccess Control User defined message\n\n\n\nRole Element (ROLE)\nName\nOpcreate\nOpmodify\nOpdelete\nOpclaim\nOpissue\nOpdrop\nOpoutput\nOpexport\nOpcopyfrom\nEclass\nAclass\nCondition\nAcrmessage\nRole Element (ROLE)"}
{"Headers": "Associated Discipline Element (PRADIS) - Global", "Content": "Name\nName of the element\nPdislf\nDiscipline Location Container Reference\nPconxf\nConsumer Extract Database Reference\nName\nName of the element\nPdislf\nDiscipline Location Container Reference\nPconxf\nConsumer Extract Database Reference\nProject Discipline List Element (PRDISL)\nNone\nName\nName of the element\nPdislf\nDiscipline Location Container Reference\nPconxf\nConsumer Extract Database Reference\n\n\n\nProject Discipline List Element (PRDISL)\nName\nPdislf\nPconxf\nProject Discipline List Element (PRDISL)"}
{"Headers": "Associated Baseline Element (PRBASL) - Global", "Content": "Primary Element\nName\nName of the element\nLprcre\nDiscipline Created\nBaself\nReference of Baseline Element\nLocrf\nLocation reference\nName\nName of the element\nLprcre\nDiscipline Created\nBaself\nReference of Baseline Element\nLocrf\nLocation reference\nProject Definition Element (PRDEFDB)\nNone\nName\nName of the element\nLprcre\nDiscipline Created\nBaself\nReference of Baseline Element\nLocrf\nLocation reference\n\n\n\nProject Definition Element (PRDEFDB)\nName\nLprcre\nBaself\nLocrf\nProject Definition Element (PRDEFDB)"}
{"Headers": "Project Definition Element (PRDEFDB) - Global", "Content": "Primary Element\nName\nName of the element\nBasname\nBase Name for the Project Definition\nDescription\nDescription of the element\nMaturf\nReference of Maturity Level Element\nTmsdif\nTMS Discipline\nName\nName of the element\nBasname\nBase Name for the Project Definition\nDescription\nDescription of the element\nMaturf\nReference of Maturity Level Element\nTmsdif\nTMS Discipline\nGlobal Project Definition World Element (GPRDEWORLD)\nAssociated Baseline Element (PRBASL)\nProject Discipline List Element (PRDISL)\nName\nName of the element\nBasname\nBase Name for the Project Definition\nDescription\nDescription of the element\nMaturf\nReference of Maturity Level Element\nTmsdif\nTMS Discipline\n\n\n\nGlobal Project Definition World Element (GPRDEWORLD)\nAssociated Baseline Element (PRBASL)\nProject Discipline List Element (PRDISL)\nName\nBasname\nDescription\nMaturf\nTmsdif\nGlobal Project Definition World Element (GPRDEWORLD)\nAssociated Baseline Element (PRBASL)\nProject Discipline List Element (PRDISL)"}
{"Headers": "Project Discipline List Element (PRDISL) - Global", "Content": "Primary Element\nName\nName of the element\nDiscif\nReference of DISCIPLINE Element\nLocrf\nLocation reference\nLprcre\nDiscipline Created\nPrddbf\nReference to the Master DB\nName\nName of the element\nDiscif\nReference of DISCIPLINE Element\nLocrf\nLocation reference\nLprcre\nDiscipline Created\nPrddbf\nReference to the Master DB\nProject Definition Element (PRDEFDB)\nAssociated Discipline Element (PRADIS)\nName\nName of the element\nDiscif\nReference of DISCIPLINE Element\nLocrf\nLocation reference\nLprcre\nDiscipline Created\nPrddbf\nReference to the Master DB\n\n\n\nProject Definition Element (PRDEFDB)\nAssociated Discipline Element (PRADIS)\nName\nDiscif\nLocrf\nLprcre\nPrddbf\nProject Definition Element (PRDEFDB)\nAssociated Discipline Element (PRADIS)"}
{"Headers": "Role Element (ROLE) - Global", "Content": "Name\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nGlobal Role World Element (GROLWL)\nPermissible Operations Element (PEROP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nGlobal Role World Element (GROLWL)\nPermissible Operations Element (PEROP)\nName\nDescription\nGlobal Role World Element (GROLWL)\nPermissible Operations Element (PEROP)"}
{"Headers": "Stamp Element (STAMP) - Global", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nSetDate\nSet Date\nSETUTC\nSet UTC Date\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nSetDate\nSet Date\nSETUTC\nSet UTC Date\nGlobal Stamp World Element (GSTWLD)\nStamp List Element (STLST)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nSetDate\nSet Date\nSETUTC\nSet UTC Date\n\n\n\nGlobal Stamp World Element (GSTWLD)\nStamp List Element (STLST)\nName\nDescription\nFunction\nPurpose\nSetDate\nSETUTC\nGlobal Stamp World Element (GSTWLD)\nStamp List Element (STLST)"}
{"Headers": "Stamp List Element (STLST) - Global", "Content": "Name\nName of the element\nStlsf\nDatabase reference\nStsess\nDatabase session number\nName\nName of the element\nStlsf\nDatabase reference\nStsess\nDatabase session number\nStamp Element (STAMP)\nNone\nName\nName of the element\nStlsf\nDatabase reference\nStsess\nDatabase session number\n\n\n\nStamp Element (STAMP)\nName\nStlsf\nStsess\nStamp Element (STAMP)"}
{"Headers": "Team Element (TEAM) - Global", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nTeamstatus\nAccess Control team status\nDiscis\nAssociated disciplines\nName\nName of the element\nDescription\nDescription of the element\nTeamstatus\nAccess Control team status\nDiscis\nAssociated disciplines\nGlobal Team World Element (GTMWL)\nDatabase List Element (DBLI)\nName\nName of the element\nDescription\nDescription of the element\nTeamstatus\nAccess Control team status\nDiscis\nAssociated disciplines\n\n\n\nGlobal Team World Element (GTMWL)\nDatabase List Element (DBLI)\nName\nDescription\nTeamstatus\nDiscis\nGlobal Team World Element (GTMWL)\nDatabase List Element (DBLI)"}
{"Headers": "World Element (WORLD)- Global", "Content": "Administrative Element\nPrimary Element\nThe WORLD is the topmost level of the database hierarchy within which all other elements exist. It cannot be deleted or copied in the same way that applies to say, a ZONE or a DRWG. Its existence is controlled by the ADMINISTRATION module.\nName\nName of the element\nName\nName of the element\nNone\nGlobal Baseline World Element (GBASEWORLD)\nGlobal Discipline World Element (GDISCWORLD)\nGlobal Location World Element (GLOCWL)\nGlobal Maturity World Element (GMATUWORLD)\nGlobal Project Definition World Element (GPRDEWORLD)\nGlobal Role World Element (GROLWL)\nGlobal Status World Element (GSTAT)\nGlobal Stamp World Element (GSTWLD)\nGlobal Team World Element (GTMWL)\nName\nName of the element\n\n\n\nGlobal Baseline World Element (GBASEWORLD)\nGlobal Discipline World Element (GDISCWORLD)\nGlobal Location World Element (GLOCWL)\nGlobal Maturity World Element (GMATUWORLD)\nGlobal Project Definition World Element (GPRDEWORLD)\nGlobal Role World Element (GROLWL)\nGlobal Status World Element (GSTAT)\nGlobal Stamp World Element (GSTWLD)\nGlobal Team World Element (GTMWL)\nName\nGlobal Baseline World Element (GBASEWORLD)\nGlobal Discipline World Element (GDISCWORLD)\nGlobal Location World Element (GLOCWL)\nGlobal Maturity World Element (GMATUWORLD)\nGlobal Project Definition World Element (GPRDEWORLD)\nGlobal Role World Element (GROLWL)\nGlobal Status World Element (GSTAT)\nGlobal Stamp World Element (GSTWLD)\nGlobal Team World Element (GTMWL)"}
{"Headers": "Manu Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the Manu database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "Manu Database Elements", "Content": "All data in the Manu database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "ARCHIV Element (ARCHIV) - Manu", "Content": "Structural Detailing Element\nName\nName of the element\nDescription\nDescription of the element\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nUuid\nUniversally unique identifier\nNone\nNone\nName\nName of the element\nDescription\nDescription of the element\nUuid\nUniversally unique identifier\n\n\n\nName\nDescription\nUuid"}
{"Headers": "Nesting Auxiliary Function Element (AUXFN)", "Content": "Hull Manufacturing Element\n\nNone\nNone\n\n\n"}
{"Headers": "Nesting Auxiliary Function Parameters Element (AUXPR)", "Content": "Hull Manufacturing Element\n\nNone\nNone\n\n\n"}
{"Headers": "Nesting Bridge Element (BRIDGE)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nBrTyp\nBridge type\nBrRefA\nNested part reference\nBrRefB\nNested part reference\nBWidth\nBridge width\nBriRad\nBridge radius\nBrPosA\nFirst bridge definition point\nBrPosB\nSecond bridge definition point\nBrPosS\nBridge definition side point\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nBrTyp\nBridge type\nBrRefA\nNested part reference\nBrRefB\nNested part reference\nBWidth\nBridge width\nBriRad\nBridge radius\nBrPosA\nFirst bridge definition point\nBrPosB\nSecond bridge definition point\nBrPosS\nBridge definition side point\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\nPlate Nest Element (PLNEST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nBrTyp\nBridge type\nBrRefA\nNested part reference\nBrRefB\nNested part reference\nBWidth\nBridge width\nBriRad\nBridge radius\nBrPosA\nFirst bridge definition point\nBrPosB\nSecond bridge definition point\nBrPosS\nBridge definition side point\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\n\n\n\nPlate Nest Element (PLNEST)\nName\nDescription\nBrTyp\nBrRefA\nBrRefB\nBWidth\nBriRad\nBrPosA\nBrPosB\nBrPosS\nFtVals\nUuid\nPlate Nest Element (PLNEST)"}
{"Headers": "Burning Gap Element (BRNGAP)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nGapPos\nGap definition points\nGWidth\nGate Width\nFRefId\nReference information\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nGapPos\nGap definition points\nGWidth\nGate Width\nFRefId\nReference information\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\nNested Part Element (NSTPLA)\nCut Free Geometry Element (CUTFR)\nName\nName of the element\nDescription\nDescription of the element\nGapPos\nGap definition points\nGWidth\nGate Width\nFRefId\nReference information\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\n\n\n\nNested Part Element (NSTPLA)\nCut Free Geometry Element (CUTFR)\nName\nDescription\nGapPos\nGWidth\nFRefId\nFtVals\nUuid\nNested Part Element (NSTPLA)\nCut Free Geometry Element (CUTFR)"}
{"Headers": "Nesting Corner Loop Element (CORNLP)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCLPOS\nCorner loop definition point\nCLLENA\nFirst corner loop length\nCLLENB\nSecond corner loop length\nCLRAD\nCorner loop radius\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nCLPOS\nCorner loop definition point\nCLLENA\nFirst corner loop length\nCLLENB\nSecond corner loop length\nCLRAD\nCorner loop radius\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\nNested Part Element (NSTPLA)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCLPOS\nCorner loop definition point\nCLLENA\nFirst corner loop length\nCLLENB\nSecond corner loop length\nCLRAD\nCorner loop radius\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\n\n\n\nNested Part Element (NSTPLA)\nName\nDescription\nCLPOS\nCLLENA\nCLLENB\nCLRAD\nFtVals\nUuid\nNested Part Element (NSTPLA)"}
{"Headers": "Pin Element (CPIN)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nColNum\nPin column number\nHght\nHeight\nPntUv\nPoint2D\nRowNum\nPin row number\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nColNum\nPin column number\nHght\nHeight\nPntUv\nPoint2D\nRowNum\nPin row number\nPin Jig Row Element (CPINRW)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nColNum\nPin column number\nHght\nHeight\nPntUv\nPoint2D\nRowNum\nPin row number\n\n\n\nPin Jig Row Element (CPINRW)\nAttributes\nName\nDescription\nCHNGD\nTBID\nColNum\nHght\nPntUv\nRowNum\nPin Jig Row Element (CPINRW)"}
{"Headers": "Pin Jig Corner Point Element (CPINCR)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nCorNum\nCorner number\nCornUv\nCorner point\nHght\nHeight\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nCorNum\nCorner number\nCornUv\nCorner point\nHght\nHeight\nPin Jig Element (CPINJG)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nCorNum\nCorner number\nCornUv\nCorner point\nHght\nHeight\n\n\n\nPin Jig Element (CPINJG)\nName\nDescription\nCHNGD\nTBID\nCorNum\nCornUv\nHght\nPin Jig Element (CPINJG)"}
{"Headers": "Pin Jig Element (CPINJG)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nAngFr\nAngle between assembly and frame plane\nAngWl\nAngle between assembly and water-line plane\nNpill\nNumber of jig pillars\nLowPos\nPoint nearest workshop floor\nNoCol\nNumber of pin jig columns\nNoRow\nNumber of pin jig rows\nManTra\nTransformation from local coordinate system\nName\nName of the element\nDescription\nDescription of the element\nAngFr\nAngle between assembly and frame plane\nAngWl\nAngle between assembly and water-line plane\nNpill\nNumber of jig pillars\nLowPos\nPoint nearest workshop floor\nNoCol\nNumber of pin jig columns\nNoRow\nNumber of pin jig rows\nManTra\nTransformation from local coordinate system\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)\nPin Jig Corner Point Element (CPINCR)\nPin Jig Row Element (CPINRW)\nName\nName of the element\nDescription\nDescription of the element\nAngFr\nAngle between assembly and frame plane\nAngWl\nAngle between assembly and water-line plane\nNpill\nNumber of jig pillars\nLowPos\nPoint nearest workshop floor\nNoCol\nNumber of pin jig columns\nNoRow\nNumber of pin jig rows\nManTra\nTransformation from local coordinate system\n\n\n\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)\nPin Jig Corner Point Element (CPINCR)\nPin Jig Row Element (CPINRW)\nName\nDescription\nAngFr\nAngWl\nNpill\nLowPos\nNoCol\nNoRow\nManTra\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)\nPin Jig Corner Point Element (CPINCR)\nPin Jig Row Element (CPINRW)"}
{"Headers": "Pin Jig Row Element (CPINRW)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nRowNum\nPin row number\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nRowNum\nPin row number\nPin Jig Element (CPINJG)\nPin Element (CPIN)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nRowNum\nPin row number\n\n\n\nPin Jig Element (CPINJG)\nPin Element (CPIN)\nName\nDescription\nCHNGD\nTBID\nRowNum\nPin Jig Element (CPINJG)\nPin Element (CPIN)"}
{"Headers": "Nesting Cutout Bridge Element (CUTBR)", "Content": "Hull Manufacturing Element\n\nLegal Owners\nNone\nNone\n\n\n"}
{"Headers": "Cut Free Geometry Element (CUTFR)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nResRef\nRest plate reference\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nResRef\nRest plate reference\nUuid\nUniversally unique identifier\nBurning Gap Element (BRNGAP)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nPoint 2D Element (POINUV)\nName\nName of the element\nDescription\nDescription of the element\nResRef\nRest plate reference\nUuid\nUniversally unique identifier\n\n\n\nBurning Gap Element (BRNGAP)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nPoint 2D Element (POINUV)\nName\nDescription\nResRef\nUuid\nBurning Gap Element (BRNGAP)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nPoint 2D Element (POINUV)"}
{"Headers": "Fabrication Assembly Element (FABASS)", "Content": "Assembly Element\nPrimary Element\nDescription\nDescription of the element\nFunction\nFunction\nAsBuil\nAssembly build strategy\nAsDest\nAssembly destination\nAsECoG\nAssembly estimated centre of gravity\nAsEWei\nAssembly estimated weight\nAsName\nLocal assembly name\nAsOri\nPredefined assembly orientation\nAsWLoc\nAssembly working location\nDelDat\nDelivery Date\nOrientation\nOrientation\nPosition\nPosition\nOrdRef\nOrder reference\nUuid\nUniversally unique identifier\nDescription\nDescription of the element\nFunction\nFunction\nAsBuil\nAssembly build strategy\nAsDest\nAssembly destination\nAsECoG\nAssembly estimated centre of gravity\nAsEWei\nAssembly estimated weight\nAsName\nLocal assembly name\nAsOri\nPredefined assembly orientation\nAsWLoc\nAssembly working location\nDelDat\nDelivery Date\nOrientation\nOrientation\nPosition\nPosition\nOrdRef\nOrder reference\nUuid\nUniversally unique identifier\nFabrication Assembly Element (FABASS)\nFabrication Assembly World Element (FAWLD)\nFabrication Assembly Element (FABASS)\nConnection Between Two Parts Element (FACONN)\nFabrication Assembly Item Element (FAITEM)\nDescription\nDescription of the element\nFunction\nFunction\nAsBuil\nAssembly build strategy\nAsDest\nAssembly destination\nAsECoG\nAssembly estimated centre of gravity\nAsEWei\nAssembly estimated weight\nAsName\nLocal assembly name\nAsOri\nPredefined assembly orientation\nAsWLoc\nAssembly working location\nDelDat\nDelivery Date\nOrientation\nOrientation\nPosition\nPosition\nOrdRef\nOrder reference\nUuid\nUniversally unique identifier\n\n\n\nFabrication Assembly Element (FABASS)\nFabrication Assembly World Element (FAWLD)\nFabrication Assembly Element (FABASS)\nConnection Between Two Parts Element (FACONN)\nFabrication Assembly Item Element (FAITEM)\nDescription\nFunction\nAsBuil\nAsDest\nAsECoG\nAsEWei\nAsName\nAsOri\nAsWLoc\nDelDat\nOrientation\nPosition\nOrdRef\nUuid\nFabrication Assembly Element (FABASS)\nFabrication Assembly World Element (FAWLD)\nFabrication Assembly Element (FABASS)\nConnection Between Two Parts Element (FACONN)\nFabrication Assembly Item Element (FAITEM)"}
{"Headers": "Connection Between Two Parts Element (FACONN)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nCParts\nConnection parts\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nCParts\nConnection parts\nUuid\nUniversally unique identifier\nFabrication Assembly Element (FABASS)\nFastener Set Element (FAFSET)\nConnection Weld Element (FAWELD)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nCParts\nConnection parts\nUuid\nUniversally unique identifier\n\n\n\nFabrication Assembly Element (FABASS)\nFastener Set Element (FAFSET)\nConnection Weld Element (FAWELD)\nName\nDescription\nFunction\nCParts\nUuid\nFabrication Assembly Element (FABASS)\nFastener Set Element (FAFSET)\nConnection Weld Element (FAWELD)"}
{"Headers": "Fastener Element (FAFAST)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nFWeight\nFastener Weight\nFLength\nFastener length\nFasType\nFastener Type\nFabLocation\nFabrication location\nFCoat\nCoating\nFGrade\nFastener material grade\nFStandard\nFastener Standard\nFDesignation\nFastener Designation\nPosition\nPosition\nOrientation\nOrientation\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nFWeight\nFastener Weight\nFLength\nFastener length\nFasType\nFastener Type\nFabLocation\nFabrication location\nFCoat\nCoating\nFGrade\nFastener material grade\nFStandard\nFastener Standard\nFDesignation\nFastener Designation\nPosition\nPosition\nOrientation\nOrientation\nUuid\nUniversally unique identifier\nFastener Set Element (FAFSET)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nFWeight\nFastener Weight\nFLength\nFastener length\nFasType\nFastener Type\nFabLocation\nFabrication location\nFCoat\nCoating\nFGrade\nFastener material grade\nFStandard\nFastener Standard\nFDesignation\nFastener Designation\nPosition\nPosition\nOrientation\nOrientation\nUuid\nUniversally unique identifier\n\n\n\nFastener Set Element (FAFSET)\nName\nDescription\nFunction\nFWeight\nFLength\nFasType\nFabLocation\nFCoat\nFGrade\nFStandard\nFDesignation\nPosition\nOrientation\nUuid\nFastener Set Element (FAFSET)"}
{"Headers": "Fastener Set Element (FAFSET)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nFDesignation\nFastener Designation\nFSetWeight\nFastener Set Weight\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nFDesignation\nFastener Designation\nFSetWeight\nFastener Set Weight\nUuid\nUniversally unique identifier\nConnection Between Two Parts Element (FACONN)\nFastener Element (FAFAST)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nFDesignation\nFastener Designation\nFSetWeight\nFastener Set Weight\nUuid\nUniversally unique identifier\n\n\n\nConnection Between Two Parts Element (FACONN)\nFastener Element (FAFAST)\nName\nDescription\nFunction\nFDesignation\nFSetWeight\nUuid\nConnection Between Two Parts Element (FACONN)\nFastener Element (FAFAST)"}
{"Headers": "Fabrication Assembly Item Element (FAITEM)", "Content": "Assembly Element\nName\nName of the element\nAsiQua\nAssembly item quantity\nName\nName of the element\nAsiQua\nAssembly item quantity\nFabrication Assembly Element (FABASS)\nNone\nName\nName of the element\nAsiQua\nAssembly item quantity\n\n\n\nFabrication Assembly Element (FABASS)\nName\nAsiQua\nFabrication Assembly Element (FABASS)"}
{"Headers": "Connection Weld Element (FAWELD)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nFabLocation\nFabrication location\ntVals\nt Values\nWBacking\nTrue if backing bar is to be used\nWeCom\nWeld comment\nWeGold\nTrue if golden weld\nWeName\nWeld name\nWeProc\nWelding process\nWeSusp\nWeld end suspension\nWfin\nWeld finish\nWgAng\nWeld groove angle\nWGap\nWeld Gap\nWIntermittent\nTrue if intermittent weld\nWIntPitch\nIntermittent weld pitch\nWIntLength\nIntermittent weld length\nWlddia\nDiameter (width) for plug/slot welds\nWLLen\nLeg length of the weld\nWLngth\nWeld Length\nWndt\nNo destructive test for the weld\nWSLen\nLength for slot weld\nWSpacer\nTrue if spacer is to be used\nWsSusp\nWeld start suspension\nWStandard\nWeld standard\nWStdv\nWeld standard version\nWTest\nTest procedure for the weld\nWtorch\nWeld torch vector\nWType\nWeld type\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nFabLocation\nFabrication location\ntVals\nt Values\nWBacking\nTrue if backing bar is to be used\nWeCom\nWeld comment\nWeGold\nTrue if golden weld\nWeName\nWeld name\nWeProc\nWelding process\nWeSusp\nWeld end suspension\nWfin\nWeld finish\nWgAng\nWeld groove angle\nWGap\nWeld Gap\nWIntermittent\nTrue if intermittent weld\nWIntPitch\nIntermittent weld pitch\nWIntLength\nIntermittent weld length\nWlddia\nDiameter (width) for plug/slot welds\nWLLen\nLeg length of the weld\nWLngth\nWeld Length\nWndt\nNo destructive test for the weld\nWSLen\nLength for slot weld\nWSpacer\nTrue if spacer is to be used\nWsSusp\nWeld start suspension\nWStandard\nWeld standard\nWStdv\nWeld standard version\nWTest\nTest procedure for the weld\nWtorch\nWeld torch vector\nWType\nWeld type\nUuid\nUniversally unique identifier\nConnection Between Two Parts Element (FACONN)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nFabLocation\nFabrication location\ntVals\nt Values\nWBacking\nTrue if backing bar is to be used\nWeCom\nWeld comment\nWeGold\nTrue if golden weld\nWeName\nWeld name\nWeProc\nWelding process\nWeSusp\nWeld end suspension\nWfin\nWeld finish\nWgAng\nWeld groove angle\nWGap\nWeld Gap\nWIntermittent\nTrue if intermittent weld\nWIntPitch\nIntermittent weld pitch\nWIntLength\nIntermittent weld length\nWlddia\nDiameter (width) for plug/slot welds\nWLLen\nLeg length of the weld\nWLngth\nWeld Length\nWndt\nNo destructive test for the weld\nWSLen\nLength for slot weld\nWSpacer\nTrue if spacer is to be used\nWsSusp\nWeld start suspension\nWStandard\nWeld standard\nWStdv\nWeld standard version\nWTest\nTest procedure for the weld\nWtorch\nWeld torch vector\nWType\nWeld type\nUuid\nUniversally unique identifier\n\n\n\nConnection Between Two Parts Element (FACONN)\nName\nDescription\nFunction\nFabLocation\ntVals\nWBacking\nWeCom\nWeGold\nWeName\nWeProc\nWeSusp\nWfin\nWgAng\nWGap\nWIntermittent\nWIntPitch\nWIntLength\nWlddia\nWLLen\nWLngth\nWndt\nWSLen\nWSpacer\nWsSusp\nWStandard\nWStdv\nWTest\nWtorch\nWType\nUuid\nConnection Between Two Parts Element (FACONN)"}
{"Headers": "Fabrication Assembly World Element (FAWLD)", "Content": "Assembly Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWorld Element (WORLD)\nFabrication Assembly Element (FABASS)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nWorld Element (WORLD)\nFabrication Assembly Element (FABASS)\nName\nDescription\nFunction\nWorld Element (WORLD)\nFabrication Assembly Element (FABASS)"}
{"Headers": "Fabrication Material Pool Element (FMTRPO)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nMPkgRf\nManufacturing Package Reference\nName\nName of the element\nDescription\nDescription of the element\nMPkgRf\nManufacturing Package Reference\nWorld Element (WORLD)\nManufacturing Package Folder Element (MPKGFL)\nName\nName of the element\nDescription\nDescription of the element\nMPkgRf\nManufacturing Package Reference\n\n\n\nWorld Element (WORLD)\nManufacturing Package Folder Element (MPKGFL)\nName\nDescription\nMPkgRf\nWorld Element (WORLD)\nManufacturing Package Folder Element (MPKGFL)"}
{"Headers": "Fabrication Material Instance Element (FPRJIN)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nAvbity\nAvailability of material instance\nMidErm\nMaterial id in the ERM system\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nAvbity\nAvailability of material instance\nMidErm\nMaterial id in the ERM system\nFabrication Plate Material Element (FPRJPL)\nFabrication Profile Material Element (FPRJPR)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nAvbity\nAvailability of material instance\nMidErm\nMaterial id in the ERM system\n\n\n\nFabrication Plate Material Element (FPRJPL)\nFabrication Profile Material Element (FPRJPR)\nName\nDescription\nFunction\nAvbity\nMidErm\nFabrication Plate Material Element (FPRJPL)\nFabrication Profile Material Element (FPRJPR)"}
{"Headers": "Fabrication Plate Material Element (FPRJPL)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatLength\nMaterial Length\nMatWidth\nMaterial Width\nThickn\nThickness\nMatref\nMaterial reference\nRmtrl\nRest material\nRplRef\nRaw plate reference\nFPhase\nFabrication unit/phase\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatLength\nMaterial Length\nMatWidth\nMaterial Width\nThickn\nThickness\nMatref\nMaterial reference\nRmtrl\nRest material\nRplRef\nRaw plate reference\nFPhase\nFabrication unit/phase\nManufacturing Package Folder Element (MPKGFL)\nFabrication Material Instance Element (FPRJIN)\nPoint 2D Element (POINUV)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nMatLength\nMaterial Length\nMatWidth\nMaterial Width\nThickn\nThickness\nMatref\nMaterial reference\nRmtrl\nRest material\nRplRef\nRaw plate reference\nFPhase\nFabrication unit/phase\n\n\n\nManufacturing Package Folder Element (MPKGFL)\nFabrication Material Instance Element (FPRJIN)\nPoint 2D Element (POINUV)\nName\nDescription\nFunction\nMatLength\nMatWidth\nThickn\nMatref\nRmtrl\nRplRef\nFPhase\nManufacturing Package Folder Element (MPKGFL)\nFabrication Material Instance Element (FPRJIN)\nPoint 2D Element (POINUV)"}
{"Headers": "Fabrication Profile Material Element (FPRJPR)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSfcode\nStiffener Code\nPrBTyp\nBasic Profile Type\nPShape\nProfile shape symbol text\nPParm\nProfile parameters\nMatLength\nMaterial Length\nMatref\nMaterial reference\nRmtrl\nRest material\nRprRef\nRaw profile reference\nFPhase\nFabrication unit/phase\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSfcode\nStiffener Code\nPrBTyp\nBasic Profile Type\nPShape\nProfile shape symbol text\nPParm\nProfile parameters\nMatLength\nMaterial Length\nMatref\nMaterial reference\nRmtrl\nRest material\nRprRef\nRaw profile reference\nFPhase\nFabrication unit/phase\nManufacturing Package Folder Element (MPKGFL)\nFabrication Material Instance Element (FPRJIN)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSfcode\nStiffener Code\nPrBTyp\nBasic Profile Type\nPShape\nProfile shape symbol text\nPParm\nProfile parameters\nMatLength\nMaterial Length\nMatref\nMaterial reference\nRmtrl\nRest material\nRprRef\nRaw profile reference\nFPhase\nFabrication unit/phase\n\n\n\nManufacturing Package Folder Element (MPKGFL)\nFabrication Material Instance Element (FPRJIN)\nName\nDescription\nFunction\nSfcode\nPrBTyp\nPShape\nPParm\nMatLength\nMatref\nRmtrl\nRprRef\nFPhase\nManufacturing Package Folder Element (MPKGFL)\nFabrication Material Instance Element (FPRJIN)"}
{"Headers": "Group Set Element (GPSET) - Manu", "Content": "Group Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nScosel\nAccess Control scope\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nScosel\nAccess Control scope\nGroup Set Element (GPSET)\nGroup World Element (GPWLD)\nGroup Set Element (GPSET)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nScosel\nAccess Control scope\n\n\n\nGroup Set Element (GPSET)\nGroup World Element (GPWLD)\nGroup Set Element (GPSET)\nName\nDescription\nFunction\nScosel\nGroup Set Element (GPSET)\nGroup World Element (GPWLD)\nGroup Set Element (GPSET)"}
{"Headers": "Group World Element (GPWLD) - Manu", "Content": "Group Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nWorld Element (WORLD)\nGroup Set Element (GPSET)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\n\n\n\nWorld Element (WORLD)\nGroup Set Element (GPSET)\nName\nDescription\nFunction\nPurpose\nWorld Element (WORLD)\nGroup Set Element (GPSET)"}
{"Headers": "Nesting Hook Element (HOOK)", "Content": "Hull Manufacturing Element\n\nNone\nNone\n\n\n"}
{"Headers": "Generic Hull Reference Element (HRDREF)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nHDBREF\nGeneric Hull DB Ref\nName\nName of the element\nHDBREF\nGeneric Hull DB Ref\nNone\nNone\nName\nName of the element\nHDBREF\nGeneric Hull DB Ref\n\n\n\nName\nHDBREF"}
{"Headers": "Labelled Entity Element (LABETY)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nLBType\nReference information for labelling\nLactyp\nLabelled action\nLblSid\nLabelling side of part\nLblPos\nLabelling definition point\nLblAng\nLabelling angle\nLbRinf\nReference information for labelling\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nLBType\nReference information for labelling\nLactyp\nLabelled action\nLblSid\nLabelling side of part\nLblPos\nLabelling definition point\nLblAng\nLabelling angle\nLbRinf\nReference information for labelling\nUuid\nUniversally unique identifier\nNested Part Element (NSTPLA)\nNested Profile Part Element (NSTPRO)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nName\nName of the element\nDescription\nDescription of the element\nLBType\nReference information for labelling\nLactyp\nLabelled action\nLblSid\nLabelling side of part\nLblPos\nLabelling definition point\nLblAng\nLabelling angle\nLbRinf\nReference information for labelling\nUuid\nUniversally unique identifier\n\n\n\nNested Part Element (NSTPLA)\nNested Profile Part Element (NSTPRO)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nName\nDescription\nLBType\nLactyp\nLblSid\nLblPos\nLblAng\nLbRinf\nUuid\nNested Part Element (NSTPLA)\nNested Profile Part Element (NSTPRO)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)"}
{"Headers": "Labelled Symbol Element (LABSYM)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nLBType\nReference information for labelling\nLactyp\nLabelled action type\nLblSid\nLabelling side of part\nSymFnt\nLabelling symbol font\nSymNum\nLabelling symbol number\nLblPos\nLabelling definition point\nLbsPos\nLabelled symbol text position\nLblAng\nLabelling angle\nLBLHGT\nLabelling height\nLblMir\nLabelling reflection code\nLbRinf\nReference information for labelling\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nLBType\nReference information for labelling\nLactyp\nLabelled action type\nLblSid\nLabelling side of part\nSymFnt\nLabelling symbol font\nSymNum\nLabelling symbol number\nLblPos\nLabelling definition point\nLbsPos\nLabelled symbol text position\nLblAng\nLabelling angle\nLBLHGT\nLabelling height\nLblMir\nLabelling reflection code\nLbRinf\nReference information for labelling\nUuid\nUniversally unique identifier\nLabelled Entity Element (LABETY)\nNested Part Element (NSTPLA)\nNested Profile Part Element (NSTPRO)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nLabelled Text Element (LABTXT)\nName\nName of the element\nDescription\nDescription of the element\nLBType\nReference information for labelling\nLactyp\nLabelled action type\nLblSid\nLabelling side of part\nSymFnt\nLabelling symbol font\nSymNum\nLabelling symbol number\nLblPos\nLabelling definition point\nLbsPos\nLabelled symbol text position\nLblAng\nLabelling angle\nLBLHGT\nLabelling height\nLblMir\nLabelling reflection code\nLbRinf\nReference information for labelling\nUuid\nUniversally unique identifier\n\n\n\nLabelled Entity Element (LABETY)\nNested Part Element (NSTPLA)\nNested Profile Part Element (NSTPRO)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nLabelled Text Element (LABTXT)\nName\nDescription\nLBType\nLactyp\nLblSid\nSymFnt\nSymNum\nLblPos\nLbsPos\nLblAng\nLBLHGT\nLblMir\nLbRinf\nUuid\nLabelled Entity Element (LABETY)\nNested Part Element (NSTPLA)\nNested Profile Part Element (NSTPRO)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nLabelled Text Element (LABTXT)"}
{"Headers": "Labelled Text Element (LABTXT)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nLBType\nReference information for labelling\nLactyp\nLabelled action\nLblSid\nLabelling side of part\nTxtFnt\nLabelling text font\nLblPos\nLabelling definition point\nLbsPos\nLabelled symbol text position\nLblAng\nLabelling angle\nLBLHGT\nLabelling height\nLblDir\nLabelling direction\nLblTxt\nLabelled text\nLbRinf\nReference information for labelling\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nLBType\nReference information for labelling\nLactyp\nLabelled action\nLblSid\nLabelling side of part\nTxtFnt\nLabelling text font\nLblPos\nLabelling definition point\nLbsPos\nLabelled symbol text position\nLblAng\nLabelling angle\nLBLHGT\nLabelling height\nLblDir\nLabelling direction\nLblTxt\nLabelled text\nLbRinf\nReference information for labelling\nUuid\nUniversally unique identifier\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nNested Part Element (NSTPLA)\nNested Profile Part Element (NSTPRO)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nLBType\nReference information for labelling\nLactyp\nLabelled action\nLblSid\nLabelling side of part\nTxtFnt\nLabelling text font\nLblPos\nLabelling definition point\nLbsPos\nLabelled symbol text position\nLblAng\nLabelling angle\nLBLHGT\nLabelling height\nLblDir\nLabelling direction\nLblTxt\nLabelled text\nLbRinf\nReference information for labelling\nUuid\nUniversally unique identifier\n\n\n\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nNested Part Element (NSTPLA)\nNested Profile Part Element (NSTPRO)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nName\nDescription\nLBType\nLactyp\nLblSid\nTxtFnt\nLblPos\nLbsPos\nLblAng\nLBLHGT\nLblDir\nLblTxt\nLbRinf\nUuid\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nNested Part Element (NSTPLA)\nNested Profile Part Element (NSTPRO)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)"}
{"Headers": "Manufacturing Package Element (MANPKG)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nMPkgRf\nManufacturing Package Reference.\nName\nName of the element\nDescription\nDescription of the element\nMPkgRf\nManufacturing Package Reference.\nWorld Element (WORLD)\nManufacturing Package Folder Element (MPKGFL)\nManufacturing Package Filter Element (MPKGFT)\nName\nName of the element\nDescription\nDescription of the element\nMPkgRf\nManufacturing Package Reference.\n\n\n\nWorld Element (WORLD)\nManufacturing Package Folder Element (MPKGFL)\nManufacturing Package Filter Element (MPKGFT)\nName\nDescription\nMPkgRf\nWorld Element (WORLD)\nManufacturing Package Folder Element (MPKGFL)\nManufacturing Package Filter Element (MPKGFT)"}
{"Headers": "Nested Assembly Plate Element (MAPLNS)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCharge\nCharge\nDrawNo\nDrawing number\nFrmScl\nForm scale\nNdtInt\nNC tape date\nNdtTxt\nNC tape date text\nNplDfa\nNesting default file 1\nNplDfb\nNesting default file 2\nNplMir\nQuantity mirrored nested plates\nNplNor\nQuantity normal nested plates\nNplTot\nTotal quantity nested plates\nOperat\nOperator\nPdtInt\nProduction date\nPdtTxt\nProduction date text\nPurch\nPurchase information\nShipNo\nShip number\nStpUv\nStart point\nVdtInt\nVerification date\nVdtTxt\nVerification date text\nTypeCd\nType code\nTypeCe\nType code\nName\nName of the element\nDescription\nDescription of the element\nCharge\nCharge\nDrawNo\nDrawing number\nFrmScl\nForm scale\nNdtInt\nNC tape date\nNdtTxt\nNC tape date text\nNplDfa\nNesting default file 1\nNplDfb\nNesting default file 2\nNplMir\nQuantity mirrored nested plates\nNplNor\nQuantity normal nested plates\nNplTot\nTotal quantity nested plates\nOperat\nOperator\nPdtInt\nProduction date\nPdtTxt\nProduction date text\nPurch\nPurchase information\nShipNo\nShip number\nStpUv\nStart point\nVdtInt\nVerification date\nVdtTxt\nVerification date text\nTypeCd\nType code\nTypeCe\nType code\nNested Plate Thickness Element (MNSTTH)\nManufacturing Package Folder Element (MPKGFL)\nBurner Data Element (MBURN)\nNesting Machine Path Time Element (MNPATH)\nNested Plate Part Element (MNPLA)\nNesting Rest Plates Normal Steel Quality Element (MNRNSQ)\nNesting Rest Plates Work Element (MNRWRK)\nNesting Tool Path Element (MNTOOL)\nNesting Raw Plate Instances Element (MPLRWI)\nName\nName of the element\nDescription\nDescription of the element\nCharge\nCharge\nDrawNo\nDrawing number\nFrmScl\nForm scale\nNdtInt\nNC tape date\nNdtTxt\nNC tape date text\nNplDfa\nNesting default file 1\nNplDfb\nNesting default file 2\nNplMir\nQuantity mirrored nested plates\nNplNor\nQuantity normal nested plates\nNplTot\nTotal quantity nested plates\nOperat\nOperator\nPdtInt\nProduction date\nPdtTxt\nProduction date text\nPurch\nPurchase information\nShipNo\nShip number\nStpUv\nStart point\nVdtInt\nVerification date\nVdtTxt\nVerification date text\nTypeCd\nType code\nTypeCe\nType code\n\n\n\nNested Plate Thickness Element (MNSTTH)\nManufacturing Package Folder Element (MPKGFL)\nBurner Data Element (MBURN)\nNesting Machine Path Time Element (MNPATH)\nNested Plate Part Element (MNPLA)\nNesting Rest Plates Normal Steel Quality Element (MNRNSQ)\nNesting Rest Plates Work Element (MNRWRK)\nNesting Tool Path Element (MNTOOL)\nNesting Raw Plate Instances Element (MPLRWI)\nName\nDescription\nCharge\nDrawNo\nFrmScl\nNdtInt\nNdtTxt\nNplDfa\nNplDfb\nNplMir\nNplNor\nNplTot\nOperat\nPdtInt\nPdtTxt\nPurch\nShipNo\nStpUv\nVdtInt\nVdtTxt\nTypeCd\nTypeCe\nNested Plate Thickness Element (MNSTTH)\nManufacturing Package Folder Element (MPKGFL)\nBurner Data Element (MBURN)\nNesting Machine Path Time Element (MNPATH)\nNested Plate Part Element (MNPLA)\nNesting Rest Plates Normal Steel Quality Element (MNRNSQ)\nNesting Rest Plates Work Element (MNRWRK)\nNesting Tool Path Element (MNTOOL)\nNesting Raw Plate Instances Element (MPLRWI)"}
{"Headers": "Production Parts Block Element (MBLOCK)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nWorld Element (WORLD)\nProduction Parts Panel Element (MPANEL)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\n\n\n\nWorld Element (WORLD)\nProduction Parts Panel Element (MPANEL)\nName\nDescription\nCHNGD\nTBID\nWorld Element (WORLD)\nProduction Parts Panel Element (MPANEL)"}
{"Headers": "Built Profile Part Element (MBPRO)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)\nPlate Part Element (MPLATE)\nProfile Part Element (MPROF)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\n\n\n\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)\nPlate Part Element (MPLATE)\nProfile Part Element (MPROF)\nName\nDescription\nCHNGD\nTBID\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)\nPlate Part Element (MPLATE)\nProfile Part Element (MPROF)"}
{"Headers": "Burner Data Element (MBURN)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBrnNam\nBurner name\nBrnNum\nBurner number\nBrnPrc\nBurner process name\nBrnRef\nBurner reference id\nBrnToo\nBurner tool\nBrnTyp\nBurner type\nBurnId\nBurner id\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBrnNam\nBurner name\nBrnNum\nBurner number\nBrnPrc\nBurner process name\nBrnRef\nBurner reference id\nBrnToo\nBurner tool\nBrnTyp\nBurner type\nBurnId\nBurner id\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBrnNam\nBurner name\nBrnNum\nBurner number\nBrnPrc\nBurner process name\nBrnRef\nBurner reference id\nBrnToo\nBurner tool\nBrnTyp\nBurner type\nBurnId\nBurner id\n\n\n\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nAttributes\nName\nDescription\nCHNGD\nTBID\nBrnNam\nBrnNum\nBrnPrc\nBrnRef\nBrnToo\nBrnTyp\nBurnId\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)"}
{"Headers": "Nesting Machine Path Time Element (MNPATH)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nPunchT\nPunching time\nTotalt\nTotal machine time for a nested plate\nWatTim\nWater cleaning time\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nPunchT\nPunching time\nTotalt\nTotal machine time for a nested plate\nWatTim\nWater cleaning time\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nNesting Pathtime Blast Element (MPTBLS)\nNesting Pathtime Burn Element (MPTBRN)\nNesting Pathtime Factors Element (MPTFAC)\nNesting Pathtime GSD Element (MPTGSD)\nNesting Pathtime Label Element (MPTLAB)\nNesting Pathtime Mark Element (MPTMRK)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nPunchT\nPunching time\nTotalt\nTotal machine time for a nested plate\nWatTim\nWater cleaning time\n\n\n\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nNesting Pathtime Blast Element (MPTBLS)\nNesting Pathtime Burn Element (MPTBRN)\nNesting Pathtime Factors Element (MPTFAC)\nNesting Pathtime GSD Element (MPTGSD)\nNesting Pathtime Label Element (MPTLAB)\nNesting Pathtime Mark Element (MPTMRK)\nName\nDescription\nCHNGD\nTBID\nPunchT\nTotalt\nWatTim\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nNesting Pathtime Blast Element (MPTBLS)\nNesting Pathtime Burn Element (MPTBRN)\nNesting Pathtime Factors Element (MPTFAC)\nNesting Pathtime GSD Element (MPTGSD)\nNesting Pathtime Label Element (MPTLAB)\nNesting Pathtime Mark Element (MPTMRK)"}
{"Headers": "Nested Plate Part Element (MNPLA)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nParNam\nPart name\nCircR\nCircumscribed rectangle\nManCog\nCenter of gravity\nLcircr\nLeast circumscribed rectangle\nHuMirror\nTrue if mirrored in local v-axis\nPlArea\nArea\nManWgh\nWeight\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nParNam\nPart name\nCircR\nCircumscribed rectangle\nManCog\nCenter of gravity\nLcircr\nLeast circumscribed rectangle\nHuMirror\nTrue if mirrored in local v-axis\nPlArea\nArea\nManWgh\nWeight\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nParNam\nPart name\nCircR\nCircumscribed rectangle\nManCog\nCenter of gravity\nLcircr\nLeast circumscribed rectangle\nHuMirror\nTrue if mirrored in local v-axis\nPlArea\nArea\nManWgh\nWeight\n\n\n\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nAttributes\nName\nDescription\nCHNGD\nTBID\nParNam\nCircR\nManCog\nLcircr\nHuMirror\nPlArea\nManWgh\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)"}
{"Headers": "Nested Profile Part Element (MNPROF)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nParNam\nPart name\nNprSid\nSide of nested profile\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nParNam\nPart name\nNprSid\nSide of nested profile\nNested Profile Element (MPRNST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nParNam\nPart name\nNprSid\nSide of nested profile\n\n\n\nNested Profile Element (MPRNST)\nName\nDescription\nCHNGD\nTBID\nParNam\nNprSid\nNested Profile Element (MPRNST)"}
{"Headers": "Nesting Created Rest Plates Element (MNRCRE)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNrParm\nNumber of rest plate parameters\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nRparm\nRest plate parameters\nRplNam\nRest plate name\nRplTyp\nRest plate type\nManWgh\nWeight\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNrParm\nNumber of rest plate parameters\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nRparm\nRest plate parameters\nRplNam\nRest plate name\nRplTyp\nRest plate type\nManWgh\nWeight\nNested Plate Element (MPLNST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNrParm\nNumber of rest plate parameters\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nRparm\nRest plate parameters\nRplNam\nRest plate name\nRplTyp\nRest plate type\nManWgh\nWeight\n\n\n\nNested Plate Element (MPLNST)\nAttributes\nName\nDescription\nCHNGD\nTBID\nNrParm\nPlaLen\nPlArea\nPlaWdt\nRparm\nRplNam\nRplTyp\nManWgh\nNested Plate Element (MPLNST)"}
{"Headers": "Nesting Rest Plates Normal Steel Quality Element (MNRNSQ)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nRplCod\nRest plate code\nRplNam\nRest plate name\nThickn\nThickness\nManWgh\nWeight\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nRplCod\nRest plate code\nRplNam\nRest plate name\nThickn\nThickness\nManWgh\nWeight\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nRplCod\nRest plate code\nRplNam\nRest plate name\nThickn\nThickness\nManWgh\nWeight\n\n\n\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nName\nDescription\nCHNGD\nTBID\nPlaLen\nPlArea\nPlaWdt\nRplCod\nRplNam\nThickn\nManWgh\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)"}
{"Headers": "Nesting Rest Plates Work Element (MNRWRK)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nThickn\nThickness\nManWgh\nWeight\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nThickn\nThickness\nManWgh\nWeight\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nThickn\nThickness\nManWgh\nWeight\n\n\n\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nName\nDescription\nCHNGD\nTBID\nPlaLen\nPlArea\nPlaWdt\nThickn\nManWgh\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)"}
{"Headers": "Nested Plate Quality Element (MNSTQU)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nWorld Element (WORLD)\nNested Plate Thickness Element (MNSTTH)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\n\n\n\nWorld Element (WORLD)\nNested Plate Thickness Element (MNSTTH)\nName\nDescription\nCHNGD\nTBID\nWorld Element (WORLD)\nNested Plate Thickness Element (MNSTTH)"}
{"Headers": "Nested Plate Thickness Element (MNSTTH)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNested Plate Quality Element (MNSTQU)\nNested Assembly Plate Element (MAPLNS)\n\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\n\n\n\nNested Plate Quality Element (MNSTQU)\nNested Assembly Plate Element (MAPLNS)\nName\nDescription\nCHNGD\nTBID\nNested Plate Quality Element (MNSTQU)\nNested Assembly Plate Element (MAPLNS)"}
{"Headers": "Nesting Tool Path Element (MNTOOL)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nNesting Toolpath Blast Element (MTPBLS)\nNesting Toolpath Burn Element (MTPBRN)\nNesting Toolpath GSD Element (MTPGSD)\nNesting Toolpath Label Element (MTPLAB)\nNesting Toolpath Mark Element (MTPMRK)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\n\n\n\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nNesting Toolpath Blast Element (MTPBLS)\nNesting Toolpath Burn Element (MTPBRN)\nNesting Toolpath GSD Element (MTPGSD)\nNesting Toolpath Label Element (MTPLAB)\nNesting Toolpath Mark Element (MTPMRK)\nName\nDescription\nCHNGD\nTBID\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nNesting Toolpath Blast Element (MTPBLS)\nNesting Toolpath Burn Element (MTPBRN)\nNesting Toolpath GSD Element (MTPGSD)\nNesting Toolpath Label Element (MTPLAB)\nNesting Toolpath Mark Element (MTPMRK)"}
{"Headers": "Mog World Element (MOGWLD) - Manu", "Content": "Hull General Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nName\nDescription\nWorld Element (WORLD)"}
{"Headers": "Production Parts Panel Element (MPANEL)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nProduction Parts Block Element (MBLOCK)\nPin Jig Element (CPINJG)\nBuilt Profile Part Element (MBPRO)\nPlate Part Element (MPLATE)\nProfile Part Element (MPROF)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\n\n\n\nProduction Parts Block Element (MBLOCK)\nPin Jig Element (CPINJG)\nBuilt Profile Part Element (MBPRO)\nPlate Part Element (MPLATE)\nProfile Part Element (MPROF)\nName\nDescription\nCHNGD\nTBID\nProduction Parts Block Element (MBLOCK)\nPin Jig Element (CPINJG)\nBuilt Profile Part Element (MBPRO)\nPlate Part Element (MPLATE)\nProfile Part Element (MPROF)"}
{"Headers": "Manufacturing Package Folder Element (MPKGFL)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nMPkgFilter\nManufacturing Package Filter Expression\nName\nName of the element\nDescription\nDescription of the element\nMPkgFilter\nManufacturing Package Filter Expression\nFabrication Material Pool Element (FMTRPO)\nManufacturing Package Element (MANPKG)\nManufacturing Package Folder Element (MPKGFL)\nPin Jig Element (CPINJG)\nFabrication Plate Material Element (FPRJPL)\nFabrication Profile Material Element (FPRJPR)\nNested Assembly Plate Element (MAPLNS)\nBuilt Profile Part Element (MBPRO)\nManufacturing Package Folder Element (MPKGFL)\nPlate Part Element (MPLATE)\nNested Plate Element (MPLNST)\nRaw Plate Element (MPLRAW)\nNested Profile Element (MPRNST)\nProfile Part Element (MPROF)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nName\nName of the element\nDescription\nDescription of the element\nMPkgFilter\nManufacturing Package Filter Expression\n\n\n\nFabrication Material Pool Element (FMTRPO)\nManufacturing Package Element (MANPKG)\nManufacturing Package Folder Element (MPKGFL)\nPin Jig Element (CPINJG)\nFabrication Plate Material Element (FPRJPL)\nFabrication Profile Material Element (FPRJPR)\nNested Assembly Plate Element (MAPLNS)\nBuilt Profile Part Element (MBPRO)\nManufacturing Package Folder Element (MPKGFL)\nPlate Part Element (MPLATE)\nNested Plate Element (MPLNST)\nRaw Plate Element (MPLRAW)\nNested Profile Element (MPRNST)\nProfile Part Element (MPROF)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)\nName\nDescription\nMPkgFilter\nFabrication Material Pool Element (FMTRPO)\nManufacturing Package Element (MANPKG)\nManufacturing Package Folder Element (MPKGFL)\nPin Jig Element (CPINJG)\nFabrication Plate Material Element (FPRJPL)\nFabrication Profile Material Element (FPRJPR)\nNested Assembly Plate Element (MAPLNS)\nBuilt Profile Part Element (MBPRO)\nManufacturing Package Folder Element (MPKGFL)\nPlate Part Element (MPLATE)\nNested Plate Element (MPLNST)\nRaw Plate Element (MPLRAW)\nNested Profile Element (MPRNST)\nProfile Part Element (MPROF)\nPlate Nest Element (PLNEST)\nProfile Nest Element (PRNEST)"}
{"Headers": "Manufacturing Package Filter Element (MPKGFT)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nMPkgFilter\nManufacturing Package Filter Expression\nName\nName of the element\nDescription\nDescription of the element\nMPkgFilter\nManufacturing Package Filter Expression\nManufacturing Package Element (MANPKG)\nNone\nName\nName of the element\nDescription\nDescription of the element\nMPkgFilter\nManufacturing Package Filter Expression\n\n\n\nManufacturing Package Element (MANPKG)\nName\nDescription\nMPkgFilter\nManufacturing Package Element (MANPKG)"}
{"Headers": "Plate Part Element (MPLATE)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nAnyCha\nTrue if chamfer is defined on any edge\nAsPart\nTrue if assembly part.\nAsPlno\nNumber of assembly plate parts\nAsPrno\nNumber of profiles on assembly part\nAsPwle\nTotal length of weld in assembly part\nBent\nBent flag\nBlsLen\nLength of blasting contours\nBrnLen\nLength of burning contours\nManCog\nCenter of gravity\nCorrug\nTrue if corrugation is defined on the plate part\nCrcAng\nTurning angle for least circumscribed rectangle\nCrcLw\nLength and width of least circumscribed rectangle\nCurved\nTrue if curved plate part.\nDatInt\nDate\nDatTxt\nDate\nDest\nDestination\nFncCd\nFunctional description code\nFncTxt\nFunctional description\nFolded\nTrue if folded\nHolGrd\nTrue if any hole in the plate should be grinded\nKnuckl\nTrue if knuckled\nManTyp\nManufactured type for example. Plane, Curved,...\nMrkLen\nTotal marking length\nPanSid\nSide of panel\nPlArea\nArea\nPlaTyp\nType of plate for example. Plate, Bracket, Clip,...\nPosNo\nPosition number\nProSid\nPlate side with most profile markings\nPrtIdl\nLong part id\nPrtIds\nShort part id\nPrtLst\nParts list name\nQuaCd\nQuality code\nQuaTxt\nQuality\nSdtTxt\nSplitting date\nStreat\nSurface treatment\nThickn\nThickness\nTypeCd\nType code\nTypeCe\nType code\nManWgh\nWeight\nUuid\nUniversally unique identifier\nOrdRef\nOrder reference\nEdgGrd\nTrue if any edge should be grinded\nMidrho\nMinimum diameter of drilled holes\nMieang\nMinimum angle for edge preparation\nMxdrho\nMaximum diameter of drilled holes\nMxeang\nMaximum angle for edge preparation\nPlcuho\nTrue if plate has holes to be cut\nPldrho\nTrue if plate has holes to be drilled\nPllbl\nTrue if plate has labels defined\nPlsiho\nTrue if plate has sink holes\nPlslho\nTrue if plate has slotted holes\nPlthho\nTrue if plate has holes to be threaded\nEPREPV\nTrue if V-bevel\nEPREPY\nTrue if Y-bevel\nEPREPX\nTrue if X-bevel\nPlnot\nTrue if plate has notches\nPlcuto\nTrue if plate has cutouts\nNMark\nNumber of markings\nNgsd\nNumber of GSDs\nNLbl\nNumber of labels\nNCHole\nNumber of cut holes\nNMkHol\nNumber of marked holes\nNDHole\nNumber of drilled holes\nNSlHol\nNumber of slot holes\nNTHole\nNumber of threaded holes\nNSiHol\nNumber of sink holes\nNNotch\nNumber of notches\nNCutou\nNumber of cutouts\nNDDrHo\nNumber of different diameters of drilled holes\nNSSlHo\nNumber of different sizes of slot holes\nCLHole\nCutting length holes\nCLNotc\nCutting length notches\nCLCuto\nCutting length cutouts\nCLEib\nCutting length end, no bevel or butt\nCLEvb\nCutting length end, V bevel\nCLEyb\nCutting length end, Y bevel\nCLExb\nCutting length end, X bevel\nCLGrnd\nTotal grinding length\nPlmkho\nTrue if plate has holes to be marked\nMichoa\nMinimum area of cut holes\nPlmrk\nTrue if plate has marking\nEprepC\nTrue if Varying bevel\nName\nName of the element\nDescription\nDescription of the element\nAnyCha\nTrue if chamfer is defined on any edge\nAsPart\nTrue if assembly part.\nAsPlno\nNumber of assembly plate parts\nAsPrno\nNumber of profiles on assembly part\nAsPwle\nTotal length of weld in assembly part\nBent\nBent flag\nBlsLen\nLength of blasting contours\nBrnLen\nLength of burning contours\nManCog\nCenter of gravity\nCorrug\nTrue if corrugation is defined on the plate part\nCrcAng\nTurning angle for least circumscribed rectangle\nCrcLw\nLength and width of least circumscribed rectangle\nCurved\nTrue if curved plate part.\nDatInt\nDate\nDatTxt\nDate\nDest\nDestination\nFncCd\nFunctional description code\nFncTxt\nFunctional description\nFolded\nTrue if folded\nHolGrd\nTrue if any hole in the plate should be grinded\nKnuckl\nTrue if knuckled\nManTyp\nManufactured type for example. Plane, Curved,...\nMrkLen\nTotal marking length\nPanSid\nSide of panel\nPlArea\nArea\nPlaTyp\nType of plate for example. Plate, Bracket, Clip,...\nPosNo\nPosition number\nProSid\nPlate side with most profile markings\nPrtIdl\nLong part id\nPrtIds\nShort part id\nPrtLst\nParts list name\nQuaCd\nQuality code\nQuaTxt\nQuality\nSdtTxt\nSplitting date\nStreat\nSurface treatment\nThickn\nThickness\nTypeCd\nType code\nTypeCe\nType code\nManWgh\nWeight\nUuid\nUniversally unique identifier\nOrdRef\nOrder reference\nEdgGrd\nTrue if any edge should be grinded\nMidrho\nMinimum diameter of drilled holes\nMieang\nMinimum angle for edge preparation\nMxdrho\nMaximum diameter of drilled holes\nMxeang\nMaximum angle for edge preparation\nPlcuho\nTrue if plate has holes to be cut\nPldrho\nTrue if plate has holes to be drilled\nPllbl\nTrue if plate has labels defined\nPlsiho\nTrue if plate has sink holes\nPlslho\nTrue if plate has slotted holes\nPlthho\nTrue if plate has holes to be threaded\nEPREPV\nTrue if V-bevel\nEPREPY\nTrue if Y-bevel\nEPREPX\nTrue if X-bevel\nPlnot\nTrue if plate has notches\nPlcuto\nTrue if plate has cutouts\nNMark\nNumber of markings\nNgsd\nNumber of GSDs\nNLbl\nNumber of labels\nNCHole\nNumber of cut holes\nNMkHol\nNumber of marked holes\nNDHole\nNumber of drilled holes\nNSlHol\nNumber of slot holes\nNTHole\nNumber of threaded holes\nNSiHol\nNumber of sink holes\nNNotch\nNumber of notches\nNCutou\nNumber of cutouts\nNDDrHo\nNumber of different diameters of drilled holes\nNSSlHo\nNumber of different sizes of slot holes\nCLHole\nCutting length holes\nCLNotc\nCutting length notches\nCLCuto\nCutting length cutouts\nCLEib\nCutting length end, no bevel or butt\nCLEvb\nCutting length end, V bevel\nCLEyb\nCutting length end, Y bevel\nCLExb\nCutting length end, X bevel\nCLGrnd\nTotal grinding length\nPlmkho\nTrue if plate has holes to be marked\nMichoa\nMinimum area of cut holes\nPlmrk\nTrue if plate has marking\nEprepC\nTrue if Varying bevel\nBuilt Profile Part Element (MBPRO)\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nAnyCha\nTrue if chamfer is defined on any edge\nAsPart\nTrue if assembly part.\nAsPlno\nNumber of assembly plate parts\nAsPrno\nNumber of profiles on assembly part\nAsPwle\nTotal length of weld in assembly part\nBent\nBent flag\nBlsLen\nLength of blasting contours\nBrnLen\nLength of burning contours\nManCog\nCenter of gravity\nCorrug\nTrue if corrugation is defined on the plate part\nCrcAng\nTurning angle for least circumscribed rectangle\nCrcLw\nLength and width of least circumscribed rectangle\nCurved\nTrue if curved plate part.\nDatInt\nDate\nDatTxt\nDate\nDest\nDestination\nFncCd\nFunctional description code\nFncTxt\nFunctional description\nFolded\nTrue if folded\nHolGrd\nTrue if any hole in the plate should be grinded\nKnuckl\nTrue if knuckled\nManTyp\nManufactured type for example. Plane, Curved,...\nMrkLen\nTotal marking length\nPanSid\nSide of panel\nPlArea\nArea\nPlaTyp\nType of plate for example. Plate, Bracket, Clip,...\nPosNo\nPosition number\nProSid\nPlate side with most profile markings\nPrtIdl\nLong part id\nPrtIds\nShort part id\nPrtLst\nParts list name\nQuaCd\nQuality code\nQuaTxt\nQuality\nSdtTxt\nSplitting date\nStreat\nSurface treatment\nThickn\nThickness\nTypeCd\nType code\nTypeCe\nType code\nManWgh\nWeight\nUuid\nUniversally unique identifier\nOrdRef\nOrder reference\nEdgGrd\nTrue if any edge should be grinded\nMidrho\nMinimum diameter of drilled holes\nMieang\nMinimum angle for edge preparation\nMxdrho\nMaximum diameter of drilled holes\nMxeang\nMaximum angle for edge preparation\nPlcuho\nTrue if plate has holes to be cut\nPldrho\nTrue if plate has holes to be drilled\nPllbl\nTrue if plate has labels defined\nPlsiho\nTrue if plate has sink holes\nPlslho\nTrue if plate has slotted holes\nPlthho\nTrue if plate has holes to be threaded\nEPREPV\nTrue if V-bevel\nEPREPY\nTrue if Y-bevel\nEPREPX\nTrue if X-bevel\nPlnot\nTrue if plate has notches\nPlcuto\nTrue if plate has cutouts\nNMark\nNumber of markings\nNgsd\nNumber of GSDs\nNLbl\nNumber of labels\nNCHole\nNumber of cut holes\nNMkHol\nNumber of marked holes\nNDHole\nNumber of drilled holes\nNSlHol\nNumber of slot holes\nNTHole\nNumber of threaded holes\nNSiHol\nNumber of sink holes\nNNotch\nNumber of notches\nNCutou\nNumber of cutouts\nNDDrHo\nNumber of different diameters of drilled holes\nNSSlHo\nNumber of different sizes of slot holes\nCLHole\nCutting length holes\nCLNotc\nCutting length notches\nCLCuto\nCutting length cutouts\nCLEib\nCutting length end, no bevel or butt\nCLEvb\nCutting length end, V bevel\nCLEyb\nCutting length end, Y bevel\nCLExb\nCutting length end, X bevel\nCLGrnd\nTotal grinding length\nPlmkho\nTrue if plate has holes to be marked\nMichoa\nMinimum area of cut holes\nPlmrk\nTrue if plate has marking\nEprepC\nTrue if Varying bevel\n\n\n\nBuilt Profile Part Element (MBPRO)\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)\nName\nDescription\nAnyCha\nAsPart\nAsPlno\nAsPrno\nAsPwle\nBent\nBlsLen\nBrnLen\nManCog\nCorrug\nCrcAng\nCrcLw\nCurved\nDatInt\nDatTxt\nDest\nFncCd\nFncTxt\nFolded\nHolGrd\nKnuckl\nManTyp\nMrkLen\nPanSid\nPlArea\nPlaTyp\nPosNo\nProSid\nPrtIdl\nPrtIds\nPrtLst\nQuaCd\nQuaTxt\nSdtTxt\nStreat\nThickn\nTypeCd\nTypeCe\nManWgh\nUuid\nOrdRef\nEdgGrd\nMidrho\nMieang\nMxdrho\nMxeang\nPlcuho\nPldrho\nPllbl\nPlsiho\nPlslho\nPlthho\nEPREPV\nEPREPY\nEPREPX\nPlnot\nPlcuto\nNMark\nNgsd\nNLbl\nNCHole\nNMkHol\nNDHole\nNSlHol\nNTHole\nNSiHol\nNNotch\nNCutou\nNDDrHo\nNSSlHo\nCLHole\nCLNotc\nCLCuto\nCLEib\nCLEvb\nCLEyb\nCLExb\nCLGrnd\nPlmkho\nMichoa\nPlmrk\nEprepC\nBuilt Profile Part Element (MBPRO)\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)"}
{"Headers": "Nested Plate Element (MPLNST)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCharge\nCharge\nDrawNo\nDrawing number\nFrmScl\nForm scale\nMinPos\nSmallest position number of nested plate parts\nNdtInt\nNC tape date\nNdtTxt\nNC tape date text\nNplDfa\nNesting default file 1\nNplDfb\nNesting default file 2\nNplMir\nQuantity mirrored nested plates\nNplNor\nQuantity normal nested plates\nNplTot\nTotal quantity nested plates\nOperat\nOperator\nPdtInt\nProduction date\nPdtTxt\nProduction date text\nPurch\nPurchase information\nShipNo\nShip number\nStpUv\nStart point\nVdtInt\nVerification date\nVdtTxt\nVerification date text\nTypeCd\nType code\nTypeCe\nType code\nInsRef\nRaw material instance reference\nName\nName of the element\nDescription\nDescription of the element\nCharge\nCharge\nDrawNo\nDrawing number\nFrmScl\nForm scale\nMinPos\nSmallest position number of nested plate parts\nNdtInt\nNC tape date\nNdtTxt\nNC tape date text\nNplDfa\nNesting default file 1\nNplDfb\nNesting default file 2\nNplMir\nQuantity mirrored nested plates\nNplNor\nQuantity normal nested plates\nNplTot\nTotal quantity nested plates\nOperat\nOperator\nPdtInt\nProduction date\nPdtTxt\nProduction date text\nPurch\nPurchase information\nShipNo\nShip number\nStpUv\nStart point\nVdtInt\nVerification date\nVdtTxt\nVerification date text\nTypeCd\nType code\nTypeCe\nType code\nInsRef\nRaw material instance reference\nNested Plate Thickness Element (MNSTTH)\nManufacturing Package Folder Element (MPKGFL)\nBurner Data Element (MBURN)\nNesting Machine Path Time Element (MNPATH)\nNested Plate Part Element (MNPLA)\nNesting Created Rest Plates Element (MNRCRE)\nNesting Rest Plates Normal Steel Quality Element (MNRNSQ)\nNesting Rest Plates Work Element (MNRWRK)\nNesting Tool Path Element (MNTOOL)\nNesting Raw Plate Instances Element (MPLRWI)\nName\nName of the element\nDescription\nDescription of the element\nCharge\nCharge\nDrawNo\nDrawing number\nFrmScl\nForm scale\nMinPos\nSmallest position number of nested plate parts\nNdtInt\nNC tape date\nNdtTxt\nNC tape date text\nNplDfa\nNesting default file 1\nNplDfb\nNesting default file 2\nNplMir\nQuantity mirrored nested plates\nNplNor\nQuantity normal nested plates\nNplTot\nTotal quantity nested plates\nOperat\nOperator\nPdtInt\nProduction date\nPdtTxt\nProduction date text\nPurch\nPurchase information\nShipNo\nShip number\nStpUv\nStart point\nVdtInt\nVerification date\nVdtTxt\nVerification date text\nTypeCd\nType code\nTypeCe\nType code\nInsRef\nRaw material instance reference\n\n\n\nNested Plate Thickness Element (MNSTTH)\nManufacturing Package Folder Element (MPKGFL)\nBurner Data Element (MBURN)\nNesting Machine Path Time Element (MNPATH)\nNested Plate Part Element (MNPLA)\nNesting Created Rest Plates Element (MNRCRE)\nNesting Rest Plates Normal Steel Quality Element (MNRNSQ)\nNesting Rest Plates Work Element (MNRWRK)\nNesting Tool Path Element (MNTOOL)\nNesting Raw Plate Instances Element (MPLRWI)\nName\nDescription\nCharge\nDrawNo\nFrmScl\nMinPos\nNdtInt\nNdtTxt\nNplDfa\nNplDfb\nNplMir\nNplNor\nNplTot\nOperat\nPdtInt\nPdtTxt\nPurch\nShipNo\nStpUv\nVdtInt\nVdtTxt\nTypeCd\nTypeCe\nInsRef\nNested Plate Thickness Element (MNSTTH)\nManufacturing Package Folder Element (MPKGFL)\nBurner Data Element (MBURN)\nNesting Machine Path Time Element (MNPATH)\nNested Plate Part Element (MNPLA)\nNesting Created Rest Plates Element (MNRCRE)\nNesting Rest Plates Normal Steel Quality Element (MNRNSQ)\nNesting Rest Plates Work Element (MNRWRK)\nNesting Tool Path Element (MNTOOL)\nNesting Raw Plate Instances Element (MPLRWI)"}
{"Headers": "Raw Plate Element (MPLRAW)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nMatDen\nMaterial density\nNused\nNumber of used raw plates\nPaintO\nPainting other side\nPaintT\nPainting this side\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nQuaCd\nQuality code\nQuaTxt\nQuality\nThickn\nThickness\nManWgh\nWeight\nName\nName of the element\nDescription\nDescription of the element\nMatDen\nMaterial density\nNused\nNumber of used raw plates\nPaintO\nPainting other side\nPaintT\nPainting this side\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nQuaCd\nQuality code\nQuaTxt\nQuality\nThickn\nThickness\nManWgh\nWeight\nManufacturing Package Folder Element (MPKGFL)\nProduction Raw Plate Thickness Element (MRAWTH)\nNone\nName\nName of the element\nDescription\nDescription of the element\nMatDen\nMaterial density\nNused\nNumber of used raw plates\nPaintO\nPainting other side\nPaintT\nPainting this side\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nQuaCd\nQuality code\nQuaTxt\nQuality\nThickn\nThickness\nManWgh\nWeight\n\n\n\nManufacturing Package Folder Element (MPKGFL)\nProduction Raw Plate Thickness Element (MRAWTH)\nName\nDescription\nMatDen\nNused\nPaintO\nPaintT\nPlaLen\nPlArea\nPlaWdt\nQuaCd\nQuaTxt\nThickn\nManWgh\nManufacturing Package Folder Element (MPKGFL)\nProduction Raw Plate Thickness Element (MRAWTH)"}
{"Headers": "Nesting Raw Plate Instances Element (MPLRWI)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nMatDen\nMaterial density\nPaintO\nPainting other side\nPaintT\nPainting this side\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nQuaTxt\nQuality\nScrapT\nTotal scrap of raw plate area\nScrapU\nTotal scrap of used raw plate area\nThickn\nThickness\nUarea\nUsed area\nUplLen\nUsed raw plate length\nUwght\nUsed weight\nUwidth\nUsed width\nManWgh\nWeight\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nMatDen\nMaterial density\nPaintO\nPainting other side\nPaintT\nPainting this side\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nQuaTxt\nQuality\nScrapT\nTotal scrap of raw plate area\nScrapU\nTotal scrap of used raw plate area\nThickn\nThickness\nUarea\nUsed area\nUplLen\nUsed raw plate length\nUwght\nUsed weight\nUwidth\nUsed width\nManWgh\nWeight\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nMatDen\nMaterial density\nPaintO\nPainting other side\nPaintT\nPainting this side\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nQuaTxt\nQuality\nScrapT\nTotal scrap of raw plate area\nScrapU\nTotal scrap of used raw plate area\nThickn\nThickness\nUarea\nUsed area\nUplLen\nUsed raw plate length\nUwght\nUsed weight\nUwidth\nUsed width\nManWgh\nWeight\n\n\n\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)\nName\nDescription\nCHNGD\nTBID\nMatDen\nPaintO\nPaintT\nPlaLen\nPlArea\nPlaWdt\nQuaTxt\nScrapT\nScrapU\nThickn\nUarea\nUplLen\nUwght\nUwidth\nManWgh\nNested Assembly Plate Element (MAPLNS)\nNested Plate Element (MPLNST)"}
{"Headers": "Nested Profile Element (MPRNST)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nBrnLen\nLength of burning contours\nBrnSt\nNumber of starts for burning\nDatInt\nDate\nDatTxt\nDate\nDimTxt\nDimensions text\nLabSt\nNumber of starts for label signing\nMrkLen\nTotal marking length\nMrkSt\nNumber of starts for marking\nNcutnt\nNumber of cutouts and notches\nNgsd\nNumber of GSDs\nNhole\nNumber of holes\nParm\nParameters\nPathTm\nPath time for selected burning machine\nPdtTxt\nProduction date text\nProLen\nRaw profile length\nQuaCd\nQuality code\nQuaPai\nPaint specification\nQuaTxt\nQuality\nRawPro\nName of raw profile\nShpSym\nShape symbol text\nTypeCd\nType code\nTypeCe\nType code\nUprLen\nUsed profile length\nInsRef\nRaw material instance reference\nName\nName of the element\nDescription\nDescription of the element\nBrnLen\nLength of burning contours\nBrnSt\nNumber of starts for burning\nDatInt\nDate\nDatTxt\nDate\nDimTxt\nDimensions text\nLabSt\nNumber of starts for label signing\nMrkLen\nTotal marking length\nMrkSt\nNumber of starts for marking\nNcutnt\nNumber of cutouts and notches\nNgsd\nNumber of GSDs\nNhole\nNumber of holes\nParm\nParameters\nPathTm\nPath time for selected burning machine\nPdtTxt\nProduction date text\nProLen\nRaw profile length\nQuaCd\nQuality code\nQuaPai\nPaint specification\nQuaTxt\nQuality\nRawPro\nName of raw profile\nShpSym\nShape symbol text\nTypeCd\nType code\nTypeCe\nType code\nUprLen\nUsed profile length\nInsRef\nRaw material instance reference\nManufacturing Package Folder Element (MPKGFL)\nWorld Element (WORLD)\nNested Profile Part Element (MNPROF)\nName\nName of the element\nDescription\nDescription of the element\nBrnLen\nLength of burning contours\nBrnSt\nNumber of starts for burning\nDatInt\nDate\nDatTxt\nDate\nDimTxt\nDimensions text\nLabSt\nNumber of starts for label signing\nMrkLen\nTotal marking length\nMrkSt\nNumber of starts for marking\nNcutnt\nNumber of cutouts and notches\nNgsd\nNumber of GSDs\nNhole\nNumber of holes\nParm\nParameters\nPathTm\nPath time for selected burning machine\nPdtTxt\nProduction date text\nProLen\nRaw profile length\nQuaCd\nQuality code\nQuaPai\nPaint specification\nQuaTxt\nQuality\nRawPro\nName of raw profile\nShpSym\nShape symbol text\nTypeCd\nType code\nTypeCe\nType code\nUprLen\nUsed profile length\nInsRef\nRaw material instance reference\n\n\n\nManufacturing Package Folder Element (MPKGFL)\nWorld Element (WORLD)\nNested Profile Part Element (MNPROF)\nName\nDescription\nBrnLen\nBrnSt\nDatInt\nDatTxt\nDimTxt\nLabSt\nMrkLen\nMrkSt\nNcutnt\nNgsd\nNhole\nParm\nPathTm\nPdtTxt\nProLen\nQuaCd\nQuaPai\nQuaTxt\nRawPro\nShpSym\nTypeCd\nTypeCe\nUprLen\nInsRef\nManufacturing Package Folder Element (MPKGFL)\nWorld Element (WORLD)\nNested Profile Part Element (MNPROF)"}
{"Headers": "Profile Part Element (MPROF)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nManCog\nCenter of gravity\nDimTxt\nDimensions text\nFncCd\nFunctional description code\nFncTxt\nFunctional description\nManTyp\nManufactured type for example. Plane, Curved,...\nMouLen\nMould length\nPanSid\nSide of panel\nParm\nParameters\nPosNo\nPosition number\nPrtIdl\nLong part id\nPrtIds\nShort part id\nPrtLst\nParts list name\nPtpTxt\nProfile type. for example. Stiffener, Flange,...\nQuaCd\nQuality code\nQuaTxt\nQuality\nShpSym\nShape symbol text\nTotLen\nTotal Length\nTypeCd\nType code\nTypeCe\nType code\nManWgh\nWeight\nUuid\nUniversally unique identifier\nOrdRef\nOrder reference\nAnyCha\nTrue if chamfer is defined on any edge\nBent\nBent flag\nBPType\nBasic Profile Type\nCurved\nTrue if curved plate part.\nEdgGrd\nTrue if any edge should be grinded\nHolGrd\nTrue if any hole in the part should be grinded\nMidrho\nMinimum diameter of drilled holes\nMieang\nMinimum angle for edge preparation\nMifang\nMinimum end cut angle flanges\nMiwang\nMinimum end cut angle web\nMxdrho\nMaximum diameter of drilled holes\nMxeang\nMaximum angle for edge preparation\nMxfang\nMaximum end cut angle flanges\nMxwang\nMaximum end cut angle web\nPrcuho\nTrue if profile has holes to be cut in this surface\nPrcuto\nTrue if profile has cutouts in this surface\nPrdrho\nTrue if profile has drill holes in this surface\nPrlbl\nTrue if profile has labels defined in this surface\nPrmrk\nTrue if profile has marking defined in this surface\nPrnot\nTrue if profile has notches in this surface\nPrsiho\nTrue if profile has sink holes in this surface\nPrslho\nTrue if profile has slotted holes in this surface\nPrthho\nTrue if profile has threaded holes in this surface\nTotLen\nTotal manual length\nEPREPV\nTrue if V-bevel\nEPREPY\nTrue if Y-bevel\nEPREPX\nTrue if X-bevel\nFulLen\nTotal length of manufactured profile\nNMark\nNumber of markings\nNgsd\nNumber of GSDs\nNLbl\nNumber of labels\nNCHole\nNumber of cut holes\nNMkHol\nNumber of marked holes\nNDHole\nNumber of drilled holes\nNSlHol\nNumber of slot holes\nNTHole\nNumber of threaded holes\nNSiHol\nNumber of sink holes\nNNotch\nNumber of notches\nNCutou\nNumber of cutouts\nNDDrHo\nNumber of different diameters of drilled holes\nNSSlHo\nNumber of different sizes of slot holes\nBrnLen\nLength of burning contours\nCLHole\nCutting length holes\nCLNotc\nCutting length notches\nCLCuto\nCutting length cutouts\nCLEib\nCutting length end, no bevel or butt\nCLEvb\nCutting length end, V bevel\nCLEyb\nCutting length end, Y bevel\nCLExb\nCutting length end, X bevel\nCLGrnd\nTotal grinding length\nTLVBev\nProfile trace length, V bevel\nTLYBev\nProfile trace length, Y bevel\nTLXBev\nProfile trace length, X bevel\nMrkLen\nTotal marking length\nPrmkho\nTrue if profile has holes to be marked in surfaces\nMichoa\nMinimum area of cut holes\nEprepC\nTrue if Varying bevel\nName\nName of the element\nDescription\nDescription of the element\nManCog\nCenter of gravity\nDimTxt\nDimensions text\nFncCd\nFunctional description code\nFncTxt\nFunctional description\nManTyp\nManufactured type for example. Plane, Curved,...\nMouLen\nMould length\nPanSid\nSide of panel\nParm\nParameters\nPosNo\nPosition number\nPrtIdl\nLong part id\nPrtIds\nShort part id\nPrtLst\nParts list name\nPtpTxt\nProfile type. for example. Stiffener, Flange,...\nQuaCd\nQuality code\nQuaTxt\nQuality\nShpSym\nShape symbol text\nTotLen\nTotal Length\nTypeCd\nType code\nTypeCe\nType code\nManWgh\nWeight\nUuid\nUniversally unique identifier\nOrdRef\nOrder reference\nAnyCha\nTrue if chamfer is defined on any edge\nBent\nBent flag\nBPType\nBasic Profile Type\nCurved\nTrue if curved plate part.\nEdgGrd\nTrue if any edge should be grinded\nHolGrd\nTrue if any hole in the part should be grinded\nMidrho\nMinimum diameter of drilled holes\nMieang\nMinimum angle for edge preparation\nMifang\nMinimum end cut angle flanges\nMiwang\nMinimum end cut angle web\nMxdrho\nMaximum diameter of drilled holes\nMxeang\nMaximum angle for edge preparation\nMxfang\nMaximum end cut angle flanges\nMxwang\nMaximum end cut angle web\nPrcuho\nTrue if profile has holes to be cut in this surface\nPrcuto\nTrue if profile has cutouts in this surface\nPrdrho\nTrue if profile has drill holes in this surface\nPrlbl\nTrue if profile has labels defined in this surface\nPrmrk\nTrue if profile has marking defined in this surface\nPrnot\nTrue if profile has notches in this surface\nPrsiho\nTrue if profile has sink holes in this surface\nPrslho\nTrue if profile has slotted holes in this surface\nPrthho\nTrue if profile has threaded holes in this surface\nTotLen\nTotal manual length\nEPREPV\nTrue if V-bevel\nEPREPY\nTrue if Y-bevel\nEPREPX\nTrue if X-bevel\nFulLen\nTotal length of manufactured profile\nNMark\nNumber of markings\nNgsd\nNumber of GSDs\nNLbl\nNumber of labels\nNCHole\nNumber of cut holes\nNMkHol\nNumber of marked holes\nNDHole\nNumber of drilled holes\nNSlHol\nNumber of slot holes\nNTHole\nNumber of threaded holes\nNSiHol\nNumber of sink holes\nNNotch\nNumber of notches\nNCutou\nNumber of cutouts\nNDDrHo\nNumber of different diameters of drilled holes\nNSSlHo\nNumber of different sizes of slot holes\nBrnLen\nLength of burning contours\nCLHole\nCutting length holes\nCLNotc\nCutting length notches\nCLCuto\nCutting length cutouts\nCLEib\nCutting length end, no bevel or butt\nCLEvb\nCutting length end, V bevel\nCLEyb\nCutting length end, Y bevel\nCLExb\nCutting length end, X bevel\nCLGrnd\nTotal grinding length\nTLVBev\nProfile trace length, V bevel\nTLYBev\nProfile trace length, Y bevel\nTLXBev\nProfile trace length, X bevel\nMrkLen\nTotal marking length\nPrmkho\nTrue if profile has holes to be marked in surfaces\nMichoa\nMinimum area of cut holes\nEprepC\nTrue if Varying bevel\nBuilt Profile Part Element (MBPRO)\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nManCog\nCenter of gravity\nDimTxt\nDimensions text\nFncCd\nFunctional description code\nFncTxt\nFunctional description\nManTyp\nManufactured type for example. Plane, Curved,...\nMouLen\nMould length\nPanSid\nSide of panel\nParm\nParameters\nPosNo\nPosition number\nPrtIdl\nLong part id\nPrtIds\nShort part id\nPrtLst\nParts list name\nPtpTxt\nProfile type. for example. Stiffener, Flange,...\nQuaCd\nQuality code\nQuaTxt\nQuality\nShpSym\nShape symbol text\nTotLen\nTotal Length\nTypeCd\nType code\nTypeCe\nType code\nManWgh\nWeight\nUuid\nUniversally unique identifier\nOrdRef\nOrder reference\nAnyCha\nTrue if chamfer is defined on any edge\nBent\nBent flag\nBPType\nBasic Profile Type\nCurved\nTrue if curved plate part.\nEdgGrd\nTrue if any edge should be grinded\nHolGrd\nTrue if any hole in the part should be grinded\nMidrho\nMinimum diameter of drilled holes\nMieang\nMinimum angle for edge preparation\nMifang\nMinimum end cut angle flanges\nMiwang\nMinimum end cut angle web\nMxdrho\nMaximum diameter of drilled holes\nMxeang\nMaximum angle for edge preparation\nMxfang\nMaximum end cut angle flanges\nMxwang\nMaximum end cut angle web\nPrcuho\nTrue if profile has holes to be cut in this surface\nPrcuto\nTrue if profile has cutouts in this surface\nPrdrho\nTrue if profile has drill holes in this surface\nPrlbl\nTrue if profile has labels defined in this surface\nPrmrk\nTrue if profile has marking defined in this surface\nPrnot\nTrue if profile has notches in this surface\nPrsiho\nTrue if profile has sink holes in this surface\nPrslho\nTrue if profile has slotted holes in this surface\nPrthho\nTrue if profile has threaded holes in this surface\nTotLen\nTotal manual length\nEPREPV\nTrue if V-bevel\nEPREPY\nTrue if Y-bevel\nEPREPX\nTrue if X-bevel\nFulLen\nTotal length of manufactured profile\nNMark\nNumber of markings\nNgsd\nNumber of GSDs\nNLbl\nNumber of labels\nNCHole\nNumber of cut holes\nNMkHol\nNumber of marked holes\nNDHole\nNumber of drilled holes\nNSlHol\nNumber of slot holes\nNTHole\nNumber of threaded holes\nNSiHol\nNumber of sink holes\nNNotch\nNumber of notches\nNCutou\nNumber of cutouts\nNDDrHo\nNumber of different diameters of drilled holes\nNSSlHo\nNumber of different sizes of slot holes\nBrnLen\nLength of burning contours\nCLHole\nCutting length holes\nCLNotc\nCutting length notches\nCLCuto\nCutting length cutouts\nCLEib\nCutting length end, no bevel or butt\nCLEvb\nCutting length end, V bevel\nCLEyb\nCutting length end, Y bevel\nCLExb\nCutting length end, X bevel\nCLGrnd\nTotal grinding length\nTLVBev\nProfile trace length, V bevel\nTLYBev\nProfile trace length, Y bevel\nTLXBev\nProfile trace length, X bevel\nMrkLen\nTotal marking length\nPrmkho\nTrue if profile has holes to be marked in surfaces\nMichoa\nMinimum area of cut holes\nEprepC\nTrue if Varying bevel\n\n\n\nBuilt Profile Part Element (MBPRO)\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)\nName\nDescription\nManCog\nDimTxt\nFncCd\nFncTxt\nManTyp\nMouLen\nPanSid\nParm\nPosNo\nPrtIdl\nPrtIds\nPrtLst\nPtpTxt\nQuaCd\nQuaTxt\nShpSym\nTotLen\nTypeCd\nTypeCe\nManWgh\nUuid\nOrdRef\nAnyCha\nBent\nBPType\nCurved\nEdgGrd\nHolGrd\nMidrho\nMieang\nMifang\nMiwang\nMxdrho\nMxeang\nMxfang\nMxwang\nPrcuho\nPrcuto\nPrdrho\nPrlbl\nPrmrk\nPrnot\nPrsiho\nPrslho\nPrthho\nTotLen\nEPREPV\nEPREPY\nEPREPX\nFulLen\nNMark\nNgsd\nNLbl\nNCHole\nNMkHol\nNDHole\nNSlHol\nNTHole\nNSiHol\nNNotch\nNCutou\nNDDrHo\nNSSlHo\nBrnLen\nCLHole\nCLNotc\nCLCuto\nCLEib\nCLEvb\nCLEyb\nCLExb\nCLGrnd\nTLVBev\nTLYBev\nTLXBev\nMrkLen\nPrmkho\nMichoa\nEprepC\nBuilt Profile Part Element (MBPRO)\nProduction Parts Panel Element (MPANEL)\nManufacturing Package Folder Element (MPKGFL)"}
{"Headers": "Nesting Pathtime Blast Element (MPTBLS)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidlt\nPathtime except idle time\nTott\nTotal pathtime\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidlt\nPathtime except idle time\nTott\nTotal pathtime\nNesting Machine Path Time Element (MNPATH)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidlt\nPathtime except idle time\nTott\nTotal pathtime\n\n\n\nNesting Machine Path Time Element (MNPATH)\nName\nDescription\nCHNGD\nTBID\nNidlt\nTott\nNesting Machine Path Time Element (MNPATH)"}
{"Headers": "Nesting Pathtime Burn Element (MPTBRN)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNbevIt\nPathtime except starts, I-bevel\nNbevXt\nPathtime except starts, X-bevel\nNbevYt\nPathtime except starts, Y-bevel\nTotti\nTotal pathtime, I-bevel\nTottx\nTotal pathtime, X-bevel\nTotty\nTotal pathtime, Y-bevel\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNbevIt\nPathtime except starts, I-bevel\nNbevXt\nPathtime except starts, X-bevel\nNbevYt\nPathtime except starts, Y-bevel\nTotti\nTotal pathtime, I-bevel\nTottx\nTotal pathtime, X-bevel\nTotty\nTotal pathtime, Y-bevel\nNesting Machine Path Time Element (MNPATH)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNbevIt\nPathtime except starts, I-bevel\nNbevXt\nPathtime except starts, X-bevel\nNbevYt\nPathtime except starts, Y-bevel\nTotti\nTotal pathtime, I-bevel\nTottx\nTotal pathtime, X-bevel\nTotty\nTotal pathtime, Y-bevel\n\n\n\nNesting Machine Path Time Element (MNPATH)\nName\nDescription\nCHNGD\nTBID\nNbevIt\nNbevXt\nNbevYt\nTotti\nTottx\nTotty\nNesting Machine Path Time Element (MNPATH)"}
{"Headers": "Nesting Pathtime Factors Element (MPTFAC)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBrnFac\nBurning factor\nClnFac\nCleaning factor\nIdlFac\nIdle movement factor\nNstFac\nNumber of starts - factor\nPowFac\nPowder point factor\nPrept\nPreparation time\nPwwFac\nPowder way factor\nRatFac\nRationalisation factor\nRatPot\nRationalisation post text\nRatPre\nRationalisation pre text\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBrnFac\nBurning factor\nClnFac\nCleaning factor\nIdlFac\nIdle movement factor\nNstFac\nNumber of starts - factor\nPowFac\nPowder point factor\nPrept\nPreparation time\nPwwFac\nPowder way factor\nRatFac\nRationalisation factor\nRatPot\nRationalisation post text\nRatPre\nRationalisation pre text\nNesting Machine Path Time Element (MNPATH)\nNesting Pathtime Time Factors Element (MPTFCI)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBrnFac\nBurning factor\nClnFac\nCleaning factor\nIdlFac\nIdle movement factor\nNstFac\nNumber of starts - factor\nPowFac\nPowder point factor\nPrept\nPreparation time\nPwwFac\nPowder way factor\nRatFac\nRationalisation factor\nRatPot\nRationalisation post text\nRatPre\nRationalisation pre text\n\n\n\nNesting Machine Path Time Element (MNPATH)\nNesting Pathtime Time Factors Element (MPTFCI)\nName\nDescription\nCHNGD\nTBID\nBrnFac\nClnFac\nIdlFac\nNstFac\nPowFac\nPrept\nPwwFac\nRatFac\nRatPot\nRatPre\nNesting Machine Path Time Element (MNPATH)\nNesting Pathtime Time Factors Element (MPTFCI)"}
{"Headers": "Nesting Pathtime Time Factors Element (MPTFCI)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nTimFac\nPathtime time factor\nTimPet\nTime factor pre text\nTimPot\nTime factor post text\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nTimFac\nPathtime time factor\nTimPet\nTime factor pre text\nTimPot\nTime factor post text\nNesting Pathtime Factors Element (MPTFAC)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nTimFac\nPathtime time factor\nTimPet\nTime factor pre text\nTimPot\nTime factor post text\n\n\n\nNesting Pathtime Factors Element (MPTFAC)\nName\nDescription\nCHNGD\nTBID\nTimFac\nTimPet\nTimPot\nNesting Pathtime Factors Element (MPTFAC)"}
{"Headers": "Nesting Pathtime GSD Element (MPTGSD)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidlt\nPathtime except idle time\nTott\nTotal pathtime\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidlt\nPathtime except idle time\nTott\nTotal pathtime\nNesting Machine Path Time Element (MNPATH)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidlt\nPathtime except idle time\nTott\nTotal pathtime\n\n\n\nNesting Machine Path Time Element (MNPATH)\nName\nDescription\nCHNGD\nTBID\nNidlt\nTott\nNesting Machine Path Time Element (MNPATH)"}
{"Headers": "Nesting Pathtime Label Element (MPTLAB)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidLab\nPathtime except idle time for label\nTotLab\nTotal label pathtime\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidLab\nPathtime except idle time for label\nTotLab\nTotal label pathtime\nNesting Machine Path Time Element (MNPATH)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidLab\nPathtime except idle time for label\nTotLab\nTotal label pathtime\n\n\n\nNesting Machine Path Time Element (MNPATH)\nName\nDescription\nCHNGD\nTBID\nNidLab\nTotLab\nNesting Machine Path Time Element (MNPATH)"}
{"Headers": "Nesting Pathtime Mark Element (MPTMRK)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidlt\nPathtime except idle time\nTott\nTotal pathtime\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidlt\nPathtime except idle time\nTott\nTotal pathtime\nNesting Machine Path Time Element (MNPATH)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNidlt\nPathtime except idle time\nTott\nTotal pathtime\n\n\n\nNesting Machine Path Time Element (MNPATH)\nName\nDescription\nCHNGD\nTBID\nNidlt\nTott\nNesting Machine Path Time Element (MNPATH)"}
{"Headers": "Production Raw Plate Quality Element (MRAWQU)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nWorld Element (WORLD)\nProduction Raw Plate Thickness Element (MRAWTH)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\n\n\n\nWorld Element (WORLD)\nProduction Raw Plate Thickness Element (MRAWTH)\nName\nDescription\nCHNGD\nTBID\nWorld Element (WORLD)\nProduction Raw Plate Thickness Element (MRAWTH)"}
{"Headers": "Production Raw Plate Thickness Element (MRAWTH)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nProduction Raw Plate Quality Element (MRAWQU)\nRaw Plate Element (MPLRAW)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\n\n\n\nProduction Raw Plate Quality Element (MRAWQU)\nRaw Plate Element (MPLRAW)\nName\nDescription\nCHNGD\nTBID\nProduction Raw Plate Quality Element (MRAWQU)\nRaw Plate Element (MPLRAW)"}
{"Headers": "Production Rest Plate Thickness Element (MRESTH)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nProduction Rest Plate Quality Element (MRESTQ)\nRest Plate Element (MRPLA)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\n\n\n\nProduction Rest Plate Quality Element (MRESTQ)\nRest Plate Element (MRPLA)\nName\nDescription\nCHNGD\nTBID\nProduction Rest Plate Quality Element (MRESTQ)\nRest Plate Element (MRPLA)"}
{"Headers": "Production Rest Plate Quality Element (MRESTQ)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nWorld Element (WORLD)\nProduction Rest Plate Thickness Element (MRESTH)\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\n\n\n\nWorld Element (WORLD)\nProduction Rest Plate Thickness Element (MRESTH)\nName\nDescription\nCHNGD\nTBID\nWorld Element (WORLD)\nProduction Rest Plate Thickness Element (MRESTH)"}
{"Headers": "Rest Plate Element (MRPLA)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nNrParm\nNumber of rest plate parameters\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nRparm\nRest plate parameters\nRplNum\nNumber of rest plates\nRplPos\nRest plate position\nRplTyp\nRest plate type\nRplSet\nRest plate set\nThickn\nThickness\nQuaCd\nQuality code\nQuaTxt\nQuality\nManWgh\nWeight\nRplCre\nRest plates created\nRplUsd\nRest plates used\nName\nName of the element\nDescription\nDescription of the element\nNrParm\nNumber of rest plate parameters\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nRparm\nRest plate parameters\nRplNum\nNumber of rest plates\nRplPos\nRest plate position\nRplTyp\nRest plate type\nRplSet\nRest plate set\nThickn\nThickness\nQuaCd\nQuality code\nQuaTxt\nQuality\nManWgh\nWeight\nRplCre\nRest plates created\nRplUsd\nRest plates used\nProduction Rest Plate Thickness Element (MRESTH)\nNone\nName\nName of the element\nDescription\nDescription of the element\nNrParm\nNumber of rest plate parameters\nPlaLen\nRaw plate length\nPlArea\nArea\nPlaWdt\nRaw plate width\nRparm\nRest plate parameters\nRplNum\nNumber of rest plates\nRplPos\nRest plate position\nRplTyp\nRest plate type\nRplSet\nRest plate set\nThickn\nThickness\nQuaCd\nQuality code\nQuaTxt\nQuality\nManWgh\nWeight\nRplCre\nRest plates created\nRplUsd\nRest plates used\n\n\n\nProduction Rest Plate Thickness Element (MRESTH)\nName\nDescription\nNrParm\nPlaLen\nPlArea\nPlaWdt\nRparm\nRplNum\nRplPos\nRplTyp\nRplSet\nThickn\nQuaCd\nQuaTxt\nManWgh\nRplCre\nRplUsd\nProduction Rest Plate Thickness Element (MRESTH)"}
{"Headers": "Nesting Toolpath Blast Element (MTPBLS)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBevLen\nLengths of bevel\nIdlLen\nNon-burning idle length\nNstart\nNumber of non-burning starts\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBevLen\nLengths of bevel\nIdlLen\nNon-burning idle length\nNstart\nNumber of non-burning starts\nNesting Tool Path Element (MNTOOL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBevLen\nLengths of bevel\nIdlLen\nNon-burning idle length\nNstart\nNumber of non-burning starts\n\n\n\nNesting Tool Path Element (MNTOOL)\nName\nDescription\nCHNGD\nTBID\nBevLen\nIdlLen\nNstart\nNesting Tool Path Element (MNTOOL)"}
{"Headers": "Nesting Toolpath Burn Element (MTPBRN)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBevLi\nLengths of I-bevel\nBevLv\nLength of vertical bevel\nBevLx\nLengths of X-bevel\nBevLy\nLengths of Y-bevel\nBrnSeq\nBurning sequence number\nIdlL\nBurning idle length\nNstrt\nNumber of burning starts\nNstrtI\nNumber of burning starts I-bevel\nNstrtX\nNumber of burning starts X-bevel\nNstrtY\nNumber of burning starts Y-bevel\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBevLi\nLengths of I-bevel\nBevLv\nLength of vertical bevel\nBevLx\nLengths of X-bevel\nBevLy\nLengths of Y-bevel\nBrnSeq\nBurning sequence number\nIdlL\nBurning idle length\nNstrt\nNumber of burning starts\nNstrtI\nNumber of burning starts I-bevel\nNstrtX\nNumber of burning starts X-bevel\nNstrtY\nNumber of burning starts Y-bevel\nNesting Tool Path Element (MNTOOL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBevLi\nLengths of I-bevel\nBevLv\nLength of vertical bevel\nBevLx\nLengths of X-bevel\nBevLy\nLengths of Y-bevel\nBrnSeq\nBurning sequence number\nIdlL\nBurning idle length\nNstrt\nNumber of burning starts\nNstrtI\nNumber of burning starts I-bevel\nNstrtX\nNumber of burning starts X-bevel\nNstrtY\nNumber of burning starts Y-bevel\n\n\n\nNesting Tool Path Element (MNTOOL)\nName\nDescription\nCHNGD\nTBID\nBevLi\nBevLv\nBevLx\nBevLy\nBrnSeq\nIdlL\nNstrt\nNstrtI\nNstrtX\nNstrtY\nNesting Tool Path Element (MNTOOL)"}
{"Headers": "Nesting Toolpath GSD Element (MTPGSD)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNstart\nNumber of non-burning starts\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNstart\nNumber of non-burning starts\nNesting Tool Path Element (MNTOOL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nNstart\nNumber of non-burning starts\n\n\n\nNesting Tool Path Element (MNTOOL)\nName\nDescription\nCHNGD\nTBID\nNstart\nNesting Tool Path Element (MNTOOL)"}
{"Headers": "Nesting Toolpath Label Element (MTPLAB)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nIdLabl\nLength of label idle movement\nNchar\nNumber of label characters\nNlStrt\nNumber of label starts\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nIdLabl\nLength of label idle movement\nNchar\nNumber of label characters\nNlStrt\nNumber of label starts\nNesting Tool Path Element (MNTOOL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nIdLabl\nLength of label idle movement\nNchar\nNumber of label characters\nNlStrt\nNumber of label starts\n\n\n\nNesting Tool Path Element (MNTOOL)\nName\nDescription\nCHNGD\nTBID\nIdLabl\nNchar\nNlStrt\nNesting Tool Path Element (MNTOOL)"}
{"Headers": "Nesting Toolpath Mark Element (MTPMRK)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBevLen\nLengths of bevel\nIdlLen\nNon-burning idle length\nNstart\nNumber of non-burning starts\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBevLen\nLengths of bevel\nIdlLen\nNon-burning idle length\nNstart\nNumber of non-burning starts\nNesting Tool Path Element (MNTOOL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nCHNGD\nChanged counter\nTBID\nTribon ID\nBevLen\nLengths of bevel\nIdlLen\nNon-burning idle length\nNstart\nNumber of non-burning starts\n\n\n\nNesting Tool Path Element (MNTOOL)\nName\nDescription\nCHNGD\nTBID\nBevLen\nIdlLen\nNstart\nNesting Tool Path Element (MNTOOL)"}
{"Headers": "Nested Part Element (NSTPLA)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nManWgh\nWeight\nPartrf\nManufacturing part references\nMirrCd\nNested part reflection\nRotAng\nNested part rotation\nNPlaOr\nNested part origin\nUuid\nUniversally unique identifier\nSqNumb\nPart Sequence on Nest\nAwQEx\nAllow Quality Exchange\nAwThEx\nAllow Thickness Exchange\nName\nName of the element\nDescription\nDescription of the element\nManWgh\nWeight\nPartrf\nManufacturing part references\nMirrCd\nNested part reflection\nRotAng\nNested part rotation\nNPlaOr\nNested part origin\nUuid\nUniversally unique identifier\nSqNumb\nPart Sequence on Nest\nAwQEx\nAllow Quality Exchange\nAwThEx\nAllow Thickness Exchange\nPlate Nest Element (PLNEST)\nBurning Gap Element (BRNGAP)\nNesting Corner Loop Element (CORNLP)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nSmart Geometry Element (SMGEO)\nName\nName of the element\nDescription\nDescription of the element\nManWgh\nWeight\nPartrf\nManufacturing part references\nMirrCd\nNested part reflection\nRotAng\nNested part rotation\nNPlaOr\nNested part origin\nUuid\nUniversally unique identifier\nSqNumb\nPart Sequence on Nest\nAwQEx\nAllow Quality Exchange\nAwThEx\nAllow Thickness Exchange\n\n\n\nPlate Nest Element (PLNEST)\nBurning Gap Element (BRNGAP)\nNesting Corner Loop Element (CORNLP)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nSmart Geometry Element (SMGEO)\nName\nDescription\nManWgh\nPartrf\nMirrCd\nRotAng\nNPlaOr\nUuid\nSqNumb\nAwQEx\nAwThEx\nPlate Nest Element (PLNEST)\nBurning Gap Element (BRNGAP)\nNesting Corner Loop Element (CORNLP)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nSmart Geometry Element (SMGEO)"}
{"Headers": "Nested Profile Part Element (NSTPRO)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nManWgh\nWeight\nPartrf\nManufacturing part references\nMirrCd\nNested part reflection\nRotAng\nNested part rotation\nNPRSTP\nNested profile starting position\nNprlen\nNested profile length\nUuid\nUniversally unique identifier\nSqNumb\nPart Sequence on Nest\nAwQEx\nAllow Quality Exchange\nAwThEx\nAllow Thickness Exchange\nName\nName of the element\nDescription\nDescription of the element\nManWgh\nWeight\nPartrf\nManufacturing part references\nMirrCd\nNested part reflection\nRotAng\nNested part rotation\nNPRSTP\nNested profile starting position\nNprlen\nNested profile length\nUuid\nUniversally unique identifier\nSqNumb\nPart Sequence on Nest\nAwQEx\nAllow Quality Exchange\nAwThEx\nAllow Thickness Exchange\nProfile Nest Element (PRNEST)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nName\nName of the element\nDescription\nDescription of the element\nManWgh\nWeight\nPartrf\nManufacturing part references\nMirrCd\nNested part reflection\nRotAng\nNested part rotation\nNPRSTP\nNested profile starting position\nNprlen\nNested profile length\nUuid\nUniversally unique identifier\nSqNumb\nPart Sequence on Nest\nAwQEx\nAllow Quality Exchange\nAwThEx\nAllow Thickness Exchange\n\n\n\nProfile Nest Element (PRNEST)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nName\nDescription\nManWgh\nPartrf\nMirrCd\nRotAng\nNPRSTP\nNprlen\nUuid\nSqNumb\nAwQEx\nAwThEx\nProfile Nest Element (PRNEST)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)"}
{"Headers": "Manufacturing Order Element (ORDER)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nOrdare\nSurface Area\nOrdwei\nOrder Weight\nPospp\nPosition number per phase\nComStA\nComment string 1\nDescal\nDescaling\nElegal\nElectrogalvanise\nFFCoat\nFirst finish coating\nSFCoat\nSecond finish coating\nFBCoat\nFirst base coating\nSBCoat\nSecond base coating\nDraftM\nDraftsman\nPrjMan\nProject manager\nCostEs\nCost estimator\nSiteMa\nSite manager\nCstmer\nCustomer\nCstmrN\nCustomer number\nSiteAd\nSite address\nStrtDt\nStart Date\nDelDat\nDelivery Date\nName\nName of the element\nDescription\nDescription of the element\nOrdare\nSurface Area\nOrdwei\nOrder Weight\nPospp\nPosition number per phase\nComStA\nComment string 1\nDescal\nDescaling\nElegal\nElectrogalvanise\nFFCoat\nFirst finish coating\nSFCoat\nSecond finish coating\nFBCoat\nFirst base coating\nSBCoat\nSecond base coating\nDraftM\nDraftsman\nPrjMan\nProject manager\nCostEs\nCost estimator\nSiteMa\nSite manager\nCstmer\nCustomer\nCstmrN\nCustomer number\nSiteAd\nSite address\nStrtDt\nStart Date\nDelDat\nDelivery Date\nManufacturing Order World Element (ORDWLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nOrdare\nSurface Area\nOrdwei\nOrder Weight\nPospp\nPosition number per phase\nComStA\nComment string 1\nDescal\nDescaling\nElegal\nElectrogalvanise\nFFCoat\nFirst finish coating\nSFCoat\nSecond finish coating\nFBCoat\nFirst base coating\nSBCoat\nSecond base coating\nDraftM\nDraftsman\nPrjMan\nProject manager\nCostEs\nCost estimator\nSiteMa\nSite manager\nCstmer\nCustomer\nCstmrN\nCustomer number\nSiteAd\nSite address\nStrtDt\nStart Date\nDelDat\nDelivery Date\n\n\n\nManufacturing Order World Element (ORDWLD)\nName\nDescription\nOrdare\nOrdwei\nPospp\nComStA\nDescal\nElegal\nFFCoat\nSFCoat\nFBCoat\nSBCoat\nDraftM\nPrjMan\nCostEs\nSiteMa\nCstmer\nCstmrN\nSiteAd\nStrtDt\nDelDat\nManufacturing Order World Element (ORDWLD)"}
{"Headers": "Manufacturing Order World Element (ORDWLD)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWorld Element (WORLD)\nManufacturing Order Element (ORDER)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nWorld Element (WORLD)\nManufacturing Order Element (ORDER)\nName\nDescription\nFunction\nWorld Element (WORLD)\nManufacturing Order Element (ORDER)"}
{"Headers": "Plate Nest Element (PLNEST)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nMachine\nMachine reference\nBurnId\nBurner id\nNcDate\nNC tape date\nNplMir\nQuantity mirrored nested plates\nNplNor\nQuantity normal nested plates\nNplTot\nTotal quantity nested plates\nNcreat\nCreator of the nest\nPrdDate\nProduction date\nStpUv\nStart point\nNstTyp\nNesting Type\nRawref\nRaw material reference\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nMachine\nMachine reference\nBurnId\nBurner id\nNcDate\nNC tape date\nNplMir\nQuantity mirrored nested plates\nNplNor\nQuantity normal nested plates\nNplTot\nTotal quantity nested plates\nNcreat\nCreator of the nest\nPrdDate\nProduction date\nStpUv\nStart point\nNstTyp\nNesting Type\nRawref\nRaw material reference\nUuid\nUniversally unique identifier\nManufacturing Package Folder Element (MPKGFL)\nNesting Bridge Element (BRIDGE)\nCut Free Geometry Element (CUTFR)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nNested Part Element (NSTPLA)\nNesting Raw Plate Element (RAWPL)\nNesting Starts World Element (TOOSTS)\nPlanning Data for Plate Nest Element (PLPLDA)\nName\nName of the element\nDescription\nDescription of the element\nMachine\nMachine reference\nBurnId\nBurner id\nNcDate\nNC tape date\nNplMir\nQuantity mirrored nested plates\nNplNor\nQuantity normal nested plates\nNplTot\nTotal quantity nested plates\nNcreat\nCreator of the nest\nPrdDate\nProduction date\nStpUv\nStart point\nNstTyp\nNesting Type\nRawref\nRaw material reference\nUuid\nUniversally unique identifier\n\n\n\nManufacturing Package Folder Element (MPKGFL)\nNesting Bridge Element (BRIDGE)\nCut Free Geometry Element (CUTFR)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nNested Part Element (NSTPLA)\nNesting Raw Plate Element (RAWPL)\nNesting Starts World Element (TOOSTS)\nPlanning Data for Plate Nest Element (PLPLDA)\nName\nDescription\nMachine\nBurnId\nNcDate\nNplMir\nNplNor\nNplTot\nNcreat\nPrdDate\nStpUv\nNstTyp\nRawref\nUuid\nManufacturing Package Folder Element (MPKGFL)\nNesting Bridge Element (BRIDGE)\nCut Free Geometry Element (CUTFR)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nNested Part Element (NSTPLA)\nNesting Raw Plate Element (RAWPL)\nNesting Starts World Element (TOOSTS)\nPlanning Data for Plate Nest Element (PLPLDA)"}
{"Headers": "Planning Data for Plate Nest Element (PLPLDA)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nNbrns\nNumber of burning starts\nNgsd\nNumber of GSDs\nNhole\nNumber of holes\nNMark\nNumber of markings\nNLabel\nNumber of labels\nNbls\nNumber of blastings\nNmbls\nNumber of markblastings\nPrcTim\nProcessing time in seconds\nBrnLen\nLength of burning contours\nIdleln\nLength of idle movement\nMrkLen\nTotal marking length\nBlsLen\nLength of blasting contours\nMblLen\nLength of markblasting\nBnLenI\nLength of vertical bevel\nBnLenV\nLength of V-Bevel\nBnLenX\nLength of X-Bevel\nBnLenY\nLength of Y-Bevel\nName\nName of the element\nDescription\nDescription of the element\nNbrns\nNumber of burning starts\nNgsd\nNumber of GSDs\nNhole\nNumber of holes\nNMark\nNumber of markings\nNLabel\nNumber of labels\nNbls\nNumber of blastings\nNmbls\nNumber of markblastings\nPrcTim\nProcessing time in seconds\nBrnLen\nLength of burning contours\nIdleln\nLength of idle movement\nMrkLen\nTotal marking length\nBlsLen\nLength of blasting contours\nMblLen\nLength of markblasting\nBnLenI\nLength of vertical bevel\nBnLenV\nLength of V-Bevel\nBnLenX\nLength of X-Bevel\nBnLenY\nLength of Y-Bevel\nPlate Nest Element (PLNEST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nNbrns\nNumber of burning starts\nNgsd\nNumber of GSDs\nNhole\nNumber of holes\nNMark\nNumber of markings\nNLabel\nNumber of labels\nNbls\nNumber of blastings\nNmbls\nNumber of markblastings\nPrcTim\nProcessing time in seconds\nBrnLen\nLength of burning contours\nIdleln\nLength of idle movement\nMrkLen\nTotal marking length\nBlsLen\nLength of blasting contours\nMblLen\nLength of markblasting\nBnLenI\nLength of vertical bevel\nBnLenV\nLength of V-Bevel\nBnLenX\nLength of X-Bevel\nBnLenY\nLength of Y-Bevel\n\n\n\nPlate Nest Element (PLNEST)\nName\nDescription\nNbrns\nNgsd\nNhole\nNMark\nNLabel\nNbls\nNmbls\nPrcTim\nBrnLen\nIdleln\nMrkLen\nBlsLen\nMblLen\nBnLenI\nBnLenV\nBnLenX\nBnLenY\nPlate Nest Element (PLNEST)"}
{"Headers": "Point 2D Element (POINUV)", "Content": "Hull Manufacturing Element\nName\nName of the element\nPosUV\nRest plate position\nName\nName of the element\nPosUV\nRest plate position\nCut Free Geometry Element (CUTFR)\nFabrication Plate Material Element (FPRJPL)\nNone\nName\nName of the element\nPosUV\nRest plate position\n\n\n\nCut Free Geometry Element (CUTFR)\nFabrication Plate Material Element (FPRJPL)\nName\nPosUV\nCut Free Geometry Element (CUTFR)\nFabrication Plate Material Element (FPRJPL)"}
{"Headers": "Profile Nest Element (PRNEST)", "Content": "Hull Manufacturing Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nMachine\nMachine reference\nBurnId\nBurner id\nNcDate\nNC tape date\nNcreat\nCreator of the nest\nPrdDate\nProduction date\nRawref\nRaw material reference\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nMachine\nMachine reference\nBurnId\nBurner id\nNcDate\nNC tape date\nNcreat\nCreator of the nest\nPrdDate\nProduction date\nRawref\nRaw material reference\nUuid\nUniversally unique identifier\nManufacturing Package Folder Element (MPKGFL)\nCut Free Geometry Element (CUTFR)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nNested Profile Part Element (NSTPRO)\nPlanning Data for Profile Nest Element (PRPLDA)\nRaw Bar/Profile for Nesting Element (RAWPR)\nName\nName of the element\nDescription\nDescription of the element\nMachine\nMachine reference\nBurnId\nBurner id\nNcDate\nNC tape date\nNcreat\nCreator of the nest\nPrdDate\nProduction date\nRawref\nRaw material reference\nUuid\nUniversally unique identifier\n\n\n\nManufacturing Package Folder Element (MPKGFL)\nCut Free Geometry Element (CUTFR)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nNested Profile Part Element (NSTPRO)\nPlanning Data for Profile Nest Element (PRPLDA)\nRaw Bar/Profile for Nesting Element (RAWPR)\nName\nDescription\nMachine\nBurnId\nNcDate\nNcreat\nPrdDate\nRawref\nUuid\nManufacturing Package Folder Element (MPKGFL)\nCut Free Geometry Element (CUTFR)\nLabelled Entity Element (LABETY)\nLabelled Symbol Element (LABSYM)\nLabelled Text Element (LABTXT)\nNested Profile Part Element (NSTPRO)\nPlanning Data for Profile Nest Element (PRPLDA)\nRaw Bar/Profile for Nesting Element (RAWPR)"}
{"Headers": "Planning Data for Profile Nest Element (PRPLDA)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nNgsd\nNumber of GSDs\nNhole\nNumber of holes\nNcutnt\nNumber of cutouts and notches\nNEndCt\nNumber of cutouts and notches\nNMark\nNumber of markings\nNLabel\nNumber of labels\nPrcTim\nProcessing time in seconds\nBrnLen\nLength of burning contours\nMrkLen\nTotal marking length\nBnLenI\nLength of vertical bevel\nBnLenV\nLength of V-Bevel\nBnLenX\nLength of X-Bevel\nBnLenY\nLength of Y-Bevel\nName\nName of the element\nDescription\nDescription of the element\nNgsd\nNumber of GSDs\nNhole\nNumber of holes\nNcutnt\nNumber of cutouts and notches\nNEndCt\nNumber of cutouts and notches\nNMark\nNumber of markings\nNLabel\nNumber of labels\nPrcTim\nProcessing time in seconds\nBrnLen\nLength of burning contours\nMrkLen\nTotal marking length\nBnLenI\nLength of vertical bevel\nBnLenV\nLength of V-Bevel\nBnLenX\nLength of X-Bevel\nBnLenY\nLength of Y-Bevel\nProfile Nest Element (PRNEST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nNgsd\nNumber of GSDs\nNhole\nNumber of holes\nNcutnt\nNumber of cutouts and notches\nNEndCt\nNumber of cutouts and notches\nNMark\nNumber of markings\nNLabel\nNumber of labels\nPrcTim\nProcessing time in seconds\nBrnLen\nLength of burning contours\nMrkLen\nTotal marking length\nBnLenI\nLength of vertical bevel\nBnLenV\nLength of V-Bevel\nBnLenX\nLength of X-Bevel\nBnLenY\nLength of Y-Bevel\n\n\n\nProfile Nest Element (PRNEST)\nName\nDescription\nNgsd\nNhole\nNcutnt\nNEndCt\nNMark\nNLabel\nPrcTim\nBrnLen\nMrkLen\nBnLenI\nBnLenV\nBnLenX\nBnLenY\nProfile Nest Element (PRNEST)"}
{"Headers": "Nesting Raw Plate Element (RAWPL)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nPlaLen\nRaw plate length\nPlaWdt\nRaw plate width\nThickn\nThickness\nMatref\nMaterial reference\nName\nName of the element\nDescription\nDescription of the element\nPlaLen\nRaw plate length\nPlaWdt\nRaw plate width\nThickn\nThickness\nMatref\nMaterial reference\nPlate Nest Element (PLNEST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nPlaLen\nRaw plate length\nPlaWdt\nRaw plate width\nThickn\nThickness\nMatref\nMaterial reference\n\n\n\nPlate Nest Element (PLNEST)\nName\nDescription\nPlaLen\nPlaWdt\nThickn\nMatref\nPlate Nest Element (PLNEST)"}
{"Headers": "Raw Bar/Profile for Nesting Element (RAWPR)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nMatref\nMaterial reference\nPParm\nProfile parameters\nProTyp\nProfile type\nBPType\nBasic Profile Type\nProLen\nRaw profile length\nName\nName of the element\nDescription\nDescription of the element\nMatref\nMaterial reference\nPParm\nProfile parameters\nProTyp\nProfile type\nBPType\nBasic Profile Type\nProLen\nRaw profile length\nProfile Nest Element (PRNEST)\nNone\nName\nName of the element\nDescription\nDescription of the element\nMatref\nMaterial reference\nPParm\nProfile parameters\nProTyp\nProfile type\nBPType\nBasic Profile Type\nProLen\nRaw profile length\n\n\n\nProfile Nest Element (PRNEST)\nName\nDescription\nMatref\nPParm\nProTyp\nBPType\nProLen\nProfile Nest Element (PRNEST)"}
{"Headers": "Smart Geometry Element (SMGEO)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nSmSide\nSmart geo side\nSMType\nSmart geo type\nSmIden\nSmart geo identifier\nSmScle\nSmart geo scale\nSmOPos\nSmart geo position\nSmORot\nSmart geo rotation\nUuid\nUniversally unique identifier\nFRefId\nReference information\nName\nName of the element\nDescription\nDescription of the element\nSmSide\nSmart geo side\nSMType\nSmart geo type\nSmIden\nSmart geo identifier\nSmScle\nSmart geo scale\nSmOPos\nSmart geo position\nSmORot\nSmart geo rotation\nUuid\nUniversally unique identifier\nFRefId\nReference information\nNested Part Element (NSTPLA)\nNone\nName\nName of the element\nDescription\nDescription of the element\nSmSide\nSmart geo side\nSMType\nSmart geo type\nSmIden\nSmart geo identifier\nSmScle\nSmart geo scale\nSmOPos\nSmart geo position\nSmORot\nSmart geo rotation\nUuid\nUniversally unique identifier\nFRefId\nReference information\n\n\n\nNested Part Element (NSTPLA)\nName\nDescription\nSmSide\nSMType\nSmIden\nSmScle\nSmOPos\nSmORot\nUuid\nFRefId\nNested Part Element (NSTPLA)"}
{"Headers": "Status Link World Element (STLNKW) - Manu", "Content": "Administrative Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\nWorld Element (WORLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\n\n\n\nWorld Element (WORLD)\nName\nDescription\nStlPos\nWorld Element (WORLD)"}
{"Headers": "Task Namespace Element (TNASPE) - Manu", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nWorld Element (WORLD)\nTask Group Element (TTSKGP)\nWorkflow Group Element (TWFLGP)\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nTask Group Element (TTSKGP)\nWorkflow Group Element (TWFLGP)\nName\nTaname\nDescription\nWorld Element (WORLD)\nTask Group Element (TTSKGP)\nWorkflow Group Element (TWFLGP)"}
{"Headers": "Nesting Start Element (TOOSTR)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nSTTYP\nStart type\nStTycd\nType code for beginning of start\nEnTyCd\nType code for end of start\nTooDir\nTool path direction\nSTPOSS\nStarting point start\nSTPOSE\nEnding point start\nSthook\nStart hook reference\nEnhook\nEnd hook reference\nFRefId\nReference information\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\nStRefs\nStart order references\nName\nName of the element\nDescription\nDescription of the element\nSTTYP\nStart type\nStTycd\nType code for beginning of start\nEnTyCd\nType code for end of start\nTooDir\nTool path direction\nSTPOSS\nStarting point start\nSTPOSE\nEnding point start\nSthook\nStart hook reference\nEnhook\nEnd hook reference\nFRefId\nReference information\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\nStRefs\nStart order references\nNesting Starts World Element (TOOSTS)\nNone\nName\nName of the element\nDescription\nDescription of the element\nSTTYP\nStart type\nStTycd\nType code for beginning of start\nEnTyCd\nType code for end of start\nTooDir\nTool path direction\nSTPOSS\nStarting point start\nSTPOSE\nEnding point start\nSthook\nStart hook reference\nEnhook\nEnd hook reference\nFRefId\nReference information\nFtVals\nt Values for nesting components\nUuid\nUniversally unique identifier\nStRefs\nStart order references\n\n\n\nNesting Starts World Element (TOOSTS)\nName\nDescription\nSTTYP\nStTycd\nEnTyCd\nTooDir\nSTPOSS\nSTPOSE\nSthook\nEnhook\nFRefId\nFtVals\nUuid\nStRefs\nNesting Starts World Element (TOOSTS)"}
{"Headers": "Nesting Starts World Element (TOOSTS)", "Content": "Hull Manufacturing Element\nName\nName of the element\nDescription\nDescription of the element\nWrkseq\nWorking sequence\nName\nName of the element\nDescription\nDescription of the element\nWrkseq\nWorking sequence\nPlate Nest Element (PLNEST)\nNesting Start Element (TOOSTR)\nName\nName of the element\nDescription\nDescription of the element\nWrkseq\nWorking sequence\n\n\n\nPlate Nest Element (PLNEST)\nNesting Start Element (TOOSTR)\nName\nDescription\nWrkseq\nPlate Nest Element (PLNEST)\nNesting Start Element (TOOSTR)"}
{"Headers": "Task Element Element (TTSKEL) - Manu", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTskdef\nReference to the task definition\nWflelm\nReference to Workflow Element\nTsknam\nTask Definition Name\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTskdef\nReference to the task definition\nWflelm\nReference to Workflow Element\nTsknam\nTask Definition Name\nTask Group Element (TTSKGP)\nNone\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTskdef\nReference to the task definition\nWflelm\nReference to Workflow Element\nTsknam\nTask Definition Name\n\n\n\nTask Group Element (TTSKGP)\nName\nTaname\nDescription\nTskdef\nWflelm\nTsknam\nTask Group Element (TTSKGP)"}
{"Headers": "Task Group Element (TTSKGP) - Manu", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTask Namespace Element (TNASPE)\nTask Element Element (TTSKEL)\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\n\n\n\nTask Namespace Element (TNASPE)\nTask Element Element (TTSKEL)\nName\nTaname\nDescription\nTask Namespace Element (TNASPE)\nTask Element Element (TTSKEL)"}
{"Headers": "Workflow Element Element (TWFLEL) - Manu", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nOrgelm\nReference to Original Element\nTskref\nAssigned tasks list\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nOrgelm\nReference to Original Element\nTskref\nAssigned tasks list\nWorkflow Group Element (TWFLGP)\nNone\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nOrgelm\nReference to Original Element\nTskref\nAssigned tasks list\n\n\n\nWorkflow Group Element (TWFLGP)\nName\nTaname\nDescription\nOrgelm\nTskref\nWorkflow Group Element (TWFLGP)"}
{"Headers": "Workflow Group Element (TWFLGP) - Manu", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTask Namespace Element (TNASPE)\nWorkflow Element Element (TWFLEL)\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\n\n\n\nTask Namespace Element (TNASPE)\nWorkflow Element Element (TWFLEL)\nName\nTaname\nDescription\nTask Namespace Element (TNASPE)\nWorkflow Element Element (TWFLEL)"}
{"Headers": "World Element (WORLD) - Manu", "Content": "Administrative Element\nPrimary Element\nThe WORLD is the topmost level of the database hierarchy within which all other elements exist. It cannot be deleted or copied in the same way that applies to say, a ZONE or a DRWG. Its existence is controlled by the ADMINISTRATION module.\nName\nName of the element\nName\nName of the element\nNone\nFabrication Assembly World Element (FAWLD)\nFabrication Material Pool Element (FMTRPO)\nGroup World Element (GPWLD)\nManufacturing Package Element (MANPKG)\nProduction Parts Block Element (MBLOCK)\nNested Plate Quality Element (MNSTQU)\nMog World Element (MOGWLD)\nNested Profile Element (MPRNST)\nProduction Raw Plate Quality Element (MRAWQU)\nProduction Rest Plate Quality Element (MRESTQ)\nManufacturing Order World Element (ORDWLD)\nTask Namespace Element (TNASPE)\nStatus Link World Element (STLNKW)\nName\nName of the element\n\n\n\nFabrication Assembly World Element (FAWLD)\nFabrication Material Pool Element (FMTRPO)\nGroup World Element (GPWLD)\nManufacturing Package Element (MANPKG)\nProduction Parts Block Element (MBLOCK)\nNested Plate Quality Element (MNSTQU)\nMog World Element (MOGWLD)\nNested Profile Element (MPRNST)\nProduction Raw Plate Quality Element (MRAWQU)\nProduction Rest Plate Quality Element (MRESTQ)\nManufacturing Order World Element (ORDWLD)\nTask Namespace Element (TNASPE)\nStatus Link World Element (STLNKW)\nName\nFabrication Assembly World Element (FAWLD)\nFabrication Material Pool Element (FMTRPO)\nGroup World Element (GPWLD)\nManufacturing Package Element (MANPKG)\nProduction Parts Block Element (MBLOCK)\nNested Plate Quality Element (MNSTQU)\nMog World Element (MOGWLD)\nNested Profile Element (MPRNST)\nProduction Raw Plate Quality Element (MRAWQU)\nProduction Rest Plate Quality Element (MRESTQ)\nManufacturing Order World Element (ORDWLD)\nTask Namespace Element (TNASPE)\nStatus Link World Element (STLNKW)"}
{"Headers": "Property Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the Property database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "Property Database Elements", "Content": "All data in the property database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Cable Properties Element (CABDATA)", "Content": "Name\nName of the element\nOutdiameter\nOutside diameter\nOutsdiameter\nOutside shield diameter\nUweight\nUnit pipe weight\nResistance\nResistance\nReactance\nReactance\nImpedance\nImpedance\nMinBend\nMinimum Bend Radius\nCondGroup\nNo of Conductor Groups\nDinterference\nDefault Interference class\nVoltAC\nVoltage AC\nVoltDC\nVoltage DC\nCurrent\nCurrent\nGapAllowance\nGap Allowance\nXArea\nCross sectional area\nNogrps\nNumber of groups\nGrptyp\nText storing group type for cable\nOascr\nIndicates screened or shielded\nGrpscr\nIndicates screened or shielded group\nArmred\nIndicating whether CABD is armoured\nEcorsz\nSize of the earth core\nIntemp\nInsulation temperature\nAmTemp\nAmpacity Temperature\nNoecor\nNumber of earth cores\nNoncor\nNumber of neutral cores\nUsecde\nText storing user code for cable\nCataNo\nText storing unique display name for Cable\nAlwUse\nIndicates whether or not catalogue can be used in the project\nMinVlt\nMinimum voltage\nMaxVlt\nMaximum voltage\nDescription\nDescription of the element\nVltrng\nVoltage Range\nCorsz\nSize of the core\nNcorsz\nSize of the neutral core\nCandrm\nCan drum\nCutalw\nCutting allowance\nCutmin\nCutting allowance minimum length\nDrumln\nDrum length\nInnshd\nInner sheath diameter\nManufr\nManufacturer\nOutshd\nOuter sheath diameter\nMinrad\nMinimum bend radius\nPultsn\nPulling tension\nRemrks\nRemarks\nCabcol\nCable colour\nOshmtl\nOuter sheath material\nIshmtl\nInner sheath material\nArmmtl\nArmour material\nInslev\nInsulation level\nConmtl\nConductor material\nCresis\nConductor resistance\nCreact\nConductor reactance\nCimped\nConductor impedance\nEresis\nEarth resistance\nEreact\nEarth reactance\nEimped\nEarth impedance\nMasspl\nMass per unit Length\nCorcod\nCore code\nCcoref\nCable core set reference\nTabcln\nTabite Class Name\nName\nName of the element\nOutdiameter\nOutside diameter\nOutsdiameter\nOutside shield diameter\nUweight\nUnit pipe weight\nResistance\nResistance\nReactance\nReactance\nImpedance\nImpedance\nMinBend\nMinimum Bend Radius\nCondGroup\nNo of Conductor Groups\nDinterference\nDefault Interference class\nVoltAC\nVoltage AC\nVoltDC\nVoltage DC\nCurrent\nCurrent\nGapAllowance\nGap Allowance\nXArea\nCross sectional area\nNogrps\nNumber of groups\nGrptyp\nText storing group type for cable\nOascr\nIndicates screened or shielded\nGrpscr\nIndicates screened or shielded group\nArmred\nIndicating whether CABD is armoured\nEcorsz\nSize of the earth core\nIntemp\nInsulation temperature\nAmTemp\nAmpacity Temperature\nNoecor\nNumber of earth cores\nNoncor\nNumber of neutral cores\nUsecde\nText storing user code for cable\nCataNo\nText storing unique display name for Cable\nAlwUse\nIndicates whether or not catalogue can be used in the project\nMinVlt\nMinimum voltage\nMaxVlt\nMaximum voltage\nDescription\nDescription of the element\nVltrng\nVoltage Range\nCorsz\nSize of the core\nNcorsz\nSize of the neutral core\nCandrm\nCan drum\nCutalw\nCutting allowance\nCutmin\nCutting allowance minimum length\nDrumln\nDrum length\nInnshd\nInner sheath diameter\nManufr\nManufacturer\nOutshd\nOuter sheath diameter\nMinrad\nMinimum bend radius\nPultsn\nPulling tension\nRemrks\nRemarks\nCabcol\nCable colour\nOshmtl\nOuter sheath material\nIshmtl\nInner sheath material\nArmmtl\nArmour material\nInslev\nInsulation level\nConmtl\nConductor material\nCresis\nConductor resistance\nCreact\nConductor reactance\nCimped\nConductor impedance\nEresis\nEarth resistance\nEreact\nEarth reactance\nEimped\nEarth impedance\nMasspl\nMass per unit Length\nCorcod\nCore code\nCcoref\nCable core set reference\nTabcln\nTabite Class Name\nSorting Category Element (CMPTYPE)\nNone\nName\nName of the element\nOutdiameter\nOutside diameter\nOutsdiameter\nOutside shield diameter\nUweight\nUnit pipe weight\nResistance\nResistance\nReactance\nReactance\nImpedance\nImpedance\nMinBend\nMinimum Bend Radius\nCondGroup\nNo of Conductor Groups\nDinterference\nDefault Interference class\nVoltAC\nVoltage AC\nVoltDC\nVoltage DC\nCurrent\nCurrent\nGapAllowance\nGap Allowance\nXArea\nCross sectional area\nNogrps\nNumber of groups\nGrptyp\nText storing group type for cable\nOascr\nIndicates screened or shielded\nGrpscr\nIndicates screened or shielded group\nArmred\nIndicating whether CABD is armoured\nEcorsz\nSize of the earth core\nIntemp\nInsulation temperature\nAmTemp\nAmpacity Temperature\nNoecor\nNumber of earth cores\nNoncor\nNumber of neutral cores\nUsecde\nText storing user code for cable\nCataNo\nText storing unique display name for Cable\nAlwUse\nIndicates whether or not catalogue can be used in the project\nMinVlt\nMinimum voltage\nMaxVlt\nMaximum voltage\nDescription\nDescription of the element\nVltrng\nVoltage Range\nCorsz\nSize of the core\nNcorsz\nSize of the neutral core\nCandrm\nCan drum\nCutalw\nCutting allowance\nCutmin\nCutting allowance minimum length\nDrumln\nDrum length\nInnshd\nInner sheath diameter\nManufr\nManufacturer\nOutshd\nOuter sheath diameter\nMinrad\nMinimum bend radius\nPultsn\nPulling tension\nRemrks\nRemarks\nCabcol\nCable colour\nOshmtl\nOuter sheath material\nIshmtl\nInner sheath material\nArmmtl\nArmour material\nInslev\nInsulation level\nConmtl\nConductor material\nCresis\nConductor resistance\nCreact\nConductor reactance\nCimped\nConductor impedance\nEresis\nEarth resistance\nEreact\nEarth reactance\nEimped\nEarth impedance\nMasspl\nMass per unit Length\nCorcod\nCore code\nCcoref\nCable core set reference\nTabcln\nTabite Class Name\n\n\n\nSorting Category Element (CMPTYPE)\nName\nOutdiameter\nOutsdiameter\nUweight\nResistance\nReactance\nImpedance\nMinBend\nCondGroup\nDinterference\nVoltAC\nVoltDC\nCurrent\nGapAllowance\nXArea\nNogrps\nGrptyp\nOascr\nGrpscr\nArmred\nEcorsz\nIntemp\nAmTemp\nNoecor\nNoncor\nUsecde\nCataNo\nAlwUse\nMinVlt\nMaxVlt\nDescription\nVltrng\nCorsz\nNcorsz\nCandrm\nCutalw\nCutmin\nDrumln\nInnshd\nManufr\nOutshd\nMinrad\nPultsn\nRemrks\nCabcol\nOshmtl\nIshmtl\nArmmtl\nInslev\nConmtl\nCresis\nCreact\nCimped\nEresis\nEreact\nEimped\nMasspl\nCorcod\nCcoref\nTabcln\nSorting Category Element (CMPTYPE)"}
{"Headers": "Card Data Element (CARD)", "Content": "Name\nName of the element\nCatype\nCard type\nCtxt\nCard text\nName\nName of the element\nCatype\nCard type\nCtxt\nCard text\nRundeck Element (RUNDECK)\nNone\nName\nName of the element\nCatype\nCard type\nCtxt\nCard text\n\n\n\nRundeck Element (RUNDECK)\nName\nCatype\nCtxt\nRundeck Element (RUNDECK)"}
{"Headers": "Case Element (CASE)", "Content": "Name\nName of the element\nWefactor\nWeight multiplier\nWpressure\nWind pressure\nWifactor\nWind multiplier\nIpressure\nInternal pressure\nRpressure\nReference pressure\nPtemperature\nPipework temperature\nRtemperature\nReference temperature\nTgradient\nPipework temperature gradient\nShockload\nShock load vector\nApplication\nApplication\nName\nName of the element\nWefactor\nWeight multiplier\nWpressure\nWind pressure\nWifactor\nWind multiplier\nIpressure\nInternal pressure\nRpressure\nReference pressure\nPtemperature\nPipework temperature\nRtemperature\nReference temperature\nTgradient\nPipework temperature gradient\nShockload\nShock load vector\nApplication\nApplication\nCase World Element (CASWORLD)\nNone\nName\nName of the element\nWefactor\nWeight multiplier\nWpressure\nWind pressure\nWifactor\nWind multiplier\nIpressure\nInternal pressure\nRpressure\nReference pressure\nPtemperature\nPipework temperature\nRtemperature\nReference temperature\nTgradient\nPipework temperature gradient\nShockload\nShock load vector\nApplication\nApplication\n\n\n\nCase World Element (CASWORLD)\nName\nWefactor\nWpressure\nWifactor\nIpressure\nRpressure\nPtemperature\nRtemperature\nTgradient\nShockload\nApplication\nCase World Element (CASWORLD)"}
{"Headers": "Case Type Element (CASTYPE)", "Content": "Name\nName of the element\nName\nName of the element\nCase World Element (CASWORLD)\nCase Element (CASE)\nName\nName of the element\n\n\n\nCase World Element (CASWORLD)\nCase Element (CASE)\nName\nCase World Element (CASWORLD)\nCase Element (CASE)"}
{"Headers": "Case World Element (CASWORLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nCase Element (CASE)\nCase Type Element (CASTYPE)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nCase Element (CASE)\nCase Type Element (CASTYPE)\nName\nWorld Element (WORLD)\nCase Element (CASE)\nCase Type Element (CASTYPE)"}
{"Headers": "Component Properties Element (CMPDATA)", "Content": "Name\nName of the element\nOutdiameter\nOutside diameter\nAcbore\nActual bore\nBtolerance\nBore tolerance\nWtolerance\nWall thickness tolerance / Weight tolerance\nCweight\nTotal component weight\nCiweight\nTotal insulation weight\nWdiameter\nWind diameter modulus\nShapemodulus\nShape modulus\nRinertia\nRotational inertia vector\nSifactor\nStress intensification factor\nPrfactor\nPressure factor\nSdthickness\nSaddle thickness\nCorallowance\nCorrosion thickness\nEfactor\nE-factor\nPwastage\nPercentage wastage factor\nBflex\nOut of plane flexibility factor for bends\nDfflex\nDisplacement force flexibility\nDmflex\nDisplacement moment flexibility\nRmflex\nRotational moment flexibility\nMrkr\n3 way component marker\nName\nName of the element\nOutdiameter\nOutside diameter\nAcbore\nActual bore\nBtolerance\nBore tolerance\nWtolerance\nWall thickness tolerance / Weight tolerance\nCweight\nTotal component weight\nCiweight\nTotal insulation weight\nWdiameter\nWind diameter modulus\nShapemodulus\nShape modulus\nRinertia\nRotational inertia vector\nSifactor\nStress intensification factor\nPrfactor\nPressure factor\nSdthickness\nSaddle thickness\nCorallowance\nCorrosion thickness\nEfactor\nE-factor\nPwastage\nPercentage wastage factor\nBflex\nOut of plane flexibility factor for bends\nDfflex\nDisplacement force flexibility\nDmflex\nDisplacement moment flexibility\nRmflex\nRotational moment flexibility\nMrkr\n3 way component marker\nSorting Category Element (CMPTYPE)\nNone\nName\nName of the element\nOutdiameter\nOutside diameter\nAcbore\nActual bore\nBtolerance\nBore tolerance\nWtolerance\nWall thickness tolerance / Weight tolerance\nCweight\nTotal component weight\nCiweight\nTotal insulation weight\nWdiameter\nWind diameter modulus\nShapemodulus\nShape modulus\nRinertia\nRotational inertia vector\nSifactor\nStress intensification factor\nPrfactor\nPressure factor\nSdthickness\nSaddle thickness\nCorallowance\nCorrosion thickness\nEfactor\nE-factor\nPwastage\nPercentage wastage factor\nBflex\nOut of plane flexibility factor for bends\nDfflex\nDisplacement force flexibility\nDmflex\nDisplacement moment flexibility\nRmflex\nRotational moment flexibility\nMrkr\n3 way component marker\n\n\n\nSorting Category Element (CMPTYPE)\nName\nOutdiameter\nAcbore\nBtolerance\nWtolerance\nCweight\nCiweight\nWdiameter\nShapemodulus\nRinertia\nSifactor\nPrfactor\nSdthickness\nCorallowance\nEfactor\nPwastage\nBflex\nDfflex\nDmflex\nRmflex\nMrkr\nSorting Category Element (CMPTYPE)"}
{"Headers": "Sorting Category Element (CMPTYPE)", "Content": "Name\nName of the element\nName\nName of the element\nProperty Component World Element (CMPWORLD)\nCable Properties Element (CABDATA)\nComponent Properties Element (CMPDATA)\nTube Properties Element (TUBDATA)\nName\nName of the element\n\n\n\nProperty Component World Element (CMPWORLD)\nCable Properties Element (CABDATA)\nComponent Properties Element (CMPDATA)\nTube Properties Element (TUBDATA)\nName\nProperty Component World Element (CMPWORLD)\nCable Properties Element (CABDATA)\nComponent Properties Element (CMPDATA)\nTube Properties Element (TUBDATA)"}
{"Headers": "Property Component World Element (CMPWORLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nSorting Category Element (CMPTYPE)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nSorting Category Element (CMPTYPE)\nName\nWorld Element (WORLD)\nSorting Category Element (CMPTYPE)"}
{"Headers": "Constraint Element (CONSTRAINT)", "Content": "Name\nName of the element\nForce\nForce vector\nMoment\nMoment\nDisplacement\nTranslation displacements\nRotn\nRotation\nDlimit\nDisplacement limit\nRlimit\nRotation limits\nFlimit\nForce limit\nMlimit\nMoment limits\nDflfactors\nTranslational spring values\nRflfactors\nRotational spring values\nFcoeff\nFriction coefficient\nCpull\nCold pull - translational\nCputwist\nCold pull - twist\nApplication\nApplication\nName\nName of the element\nForce\nForce vector\nMoment\nMoment\nDisplacement\nTranslation displacements\nRotn\nRotation\nDlimit\nDisplacement limit\nRlimit\nRotation limits\nFlimit\nForce limit\nMlimit\nMoment limits\nDflfactors\nTranslational spring values\nRflfactors\nRotational spring values\nFcoeff\nFriction coefficient\nCpull\nCold pull - translational\nCputwist\nCold pull - twist\nApplication\nApplication\nConstraint Type Element (CONTYPE)\nConstraint Data World Element (CONWORLD)\nCase Table Element (TCASE)\nName\nName of the element\nForce\nForce vector\nMoment\nMoment\nDisplacement\nTranslation displacements\nRotn\nRotation\nDlimit\nDisplacement limit\nRlimit\nRotation limits\nFlimit\nForce limit\nMlimit\nMoment limits\nDflfactors\nTranslational spring values\nRflfactors\nRotational spring values\nFcoeff\nFriction coefficient\nCpull\nCold pull - translational\nCputwist\nCold pull - twist\nApplication\nApplication\n\n\n\nConstraint Type Element (CONTYPE)\nConstraint Data World Element (CONWORLD)\nCase Table Element (TCASE)\nName\nForce\nMoment\nDisplacement\nRotn\nDlimit\nRlimit\nFlimit\nMlimit\nDflfactors\nRflfactors\nFcoeff\nCpull\nCputwist\nApplication\nConstraint Type Element (CONTYPE)\nConstraint Data World Element (CONWORLD)\nCase Table Element (TCASE)"}
{"Headers": "Constraint Type Element (CONTYPE)", "Content": "Name\nName of the element\nRtype\nRestraint type\nName\nName of the element\nRtype\nRestraint type\nConstraint Data World Element (CONWORLD)\nConstraint Element (CONSTRAINT)\nName\nName of the element\nRtype\nRestraint type\n\n\n\nConstraint Data World Element (CONWORLD)\nConstraint Element (CONSTRAINT)\nName\nRtype\nConstraint Data World Element (CONWORLD)\nConstraint Element (CONSTRAINT)"}
{"Headers": "Constraint Data World Element (CONWORLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nConstraint Element (CONSTRAINT)\nConstraint Type Element (CONTYPE)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nConstraint Element (CONSTRAINT)\nConstraint Type Element (CONTYPE)\nName\nWorld Element (WORLD)\nConstraint Element (CONSTRAINT)\nConstraint Type Element (CONTYPE)"}
{"Headers": "Fluid Material Element (FLUID)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nMaterial World Element (MATWORLD)\nProperty Table - A Element (TAPROPERTY)\nProperty Table - B Element (TBPROPERTY)\nProperty Table - C Element (TCPROPERTY)\nMaterial Density Table Element (TDENSITY)\nExpansion Coefficient Table Element (TEXPANSION)\nText Element (TEXT)\nYoungs Modulus Table Element (TYOUNG)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nMaterial World Element (MATWORLD)\nProperty Table - A Element (TAPROPERTY)\nProperty Table - B Element (TBPROPERTY)\nProperty Table - C Element (TCPROPERTY)\nMaterial Density Table Element (TDENSITY)\nExpansion Coefficient Table Element (TEXPANSION)\nText Element (TEXT)\nYoungs Modulus Table Element (TYOUNG)\nName\nDescription\nMaterial World Element (MATWORLD)\nProperty Table - A Element (TAPROPERTY)\nProperty Table - B Element (TBPROPERTY)\nProperty Table - C Element (TCPROPERTY)\nMaterial Density Table Element (TDENSITY)\nExpansion Coefficient Table Element (TEXPANSION)\nText Element (TEXT)\nYoungs Modulus Table Element (TYOUNG)"}
{"Headers": "Group World Element (GPWLD) - Property", "Content": "Group Element\nPrimary Element\nThe element is a subsidiary World that contains only GROUPs and is owned by the main WORLD element.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nWorld Element (WORLD)\nGroup Element (GROUP)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\n\n\n\nWorld Element (WORLD)\nGroup Element (GROUP)\nName\nDescription\nFunction\nPurpose\nWorld Element (WORLD)\nGroup Element (GROUP)"}
{"Headers": "Group Element (GROUP) - Property", "Content": "Group Element\nYou may define as a GROUP any collection of elements in the database, assembling these elements as a single GROUP unit.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nOrrf\nOrigin reference (for templates)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nOrrf\nOrigin reference (for templates)\nGroup World Element (GPWLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nOrrf\nOrigin reference (for templates)\n\n\n\nGroup World Element (GPWLD)\nName\nDescription\nFunction\nPurpose\nOrrf\nGroup World Element (GPWLD)"}
{"Headers": "Material World Element (MATWORLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nName\nWorld Element (WORLD)\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)"}
{"Headers": "Rundeck Element (RUNDECK)", "Content": "Name\nName of the element\nDate\nDate\nUname\nName of user\nName\nName of the element\nDate\nDate\nUname\nName of user\nRun World Element (RUNWORLD)\nCard Data Element (CARD)\nName\nName of the element\nDate\nDate\nUname\nName of user\n\n\n\nRun World Element (RUNWORLD)\nCard Data Element (CARD)\nName\nDate\nUname\nRun World Element (RUNWORLD)\nCard Data Element (CARD)"}
{"Headers": "Run World Element (RUNWORLD)", "Content": "Name\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nRundeck Element (RUNDECK)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nRundeck Element (RUNDECK)\nName\nWorld Element (WORLD)\nRundeck Element (RUNDECK)"}
{"Headers": "Spot Property A Temperature and Pressure Element (SAPROPERTY)", "Content": "Name\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nAproperty\nSpot value of property A\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nAproperty\nSpot value of property A\nProperty Table - A Element (TAPROPERTY)\nNone\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nAproperty\nSpot value of property A\n\n\n\nProperty Table - A Element (TAPROPERTY)\nName\nTemperature\nPressure\nAproperty\nProperty Table - A Element (TAPROPERTY)"}
{"Headers": "Spot Property B Temperature and Pressure Element (SBPROPERTY)", "Content": "Name\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nBproperty\nSpot value of property B\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nBproperty\nSpot value of property B\nProperty Table - B Element (TBPROPERTY)\nNone\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nBproperty\nSpot value of property B\n\n\n\nProperty Table - B Element (TBPROPERTY)\nName\nTemperature\nPressure\nBproperty\nProperty Table - B Element (TBPROPERTY)"}
{"Headers": "Spot Property C Temperature and Pressure Element (SCPROPERTY)", "Content": "Name\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nCproperty\nSpot value of property C\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nCproperty\nSpot value of property C\nProperty Table - C Element (TCPROPERTY)\nNone\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nCproperty\nSpot value of property C\n\n\n\nProperty Table - C Element (TCPROPERTY)\nName\nTemperature\nPressure\nCproperty\nProperty Table - C Element (TCPROPERTY)"}
{"Headers": "Spot Density Temperature and Pressure Element (SDENSITY)", "Content": "Name\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nDensity\nSpot value of density\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nDensity\nSpot value of density\nMaterial Density Table Element (TDENSITY)\nNone\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nDensity\nSpot value of density\n\n\n\nMaterial Density Table Element (TDENSITY)\nName\nTemperature\nPressure\nDensity\nMaterial Density Table Element (TDENSITY)"}
{"Headers": "Spot Expansion Coefficient Temperature and Pressure Element (SEXPANSION)", "Content": "Name\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nExpansion\nSpot value of expansion coefficient\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nExpansion\nSpot value of expansion coefficient\nExpansion Coefficient Table Element (TEXPANSION)\nNone\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nExpansion\nSpot value of expansion coefficient\n\n\n\nExpansion Coefficient Table Element (TEXPANSION)\nName\nTemperature\nPressure\nExpansion\nExpansion Coefficient Table Element (TEXPANSION)"}
{"Headers": "Solids Extended Info Element (SOLEXT)", "Content": "Name\nName of the element\nQuaCd\nQuality code\nPreppr\nPreparation information\nName\nName of the element\nQuaCd\nQuality code\nPreppr\nPreparation information\nSolid Material Element (SOLID)\nNone\nName\nName of the element\nQuaCd\nQuality code\nPreppr\nPreparation information\n\n\n\nSolid Material Element (SOLID)\nName\nQuaCd\nPreppr\nSolid Material Element (SOLID)"}
{"Headers": "Solid Material Element (SOLID)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nPurpose\nDescription code word\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nPurpose\nDescription code word\nUuid\nUniversally unique identifier\nMaterial World Element (MATWORLD)\nSolids Extended Info Element (SOLEXT)\nProperty Table - A Element (TAPROPERTY)\nProperty Table - B Element (TBPROPERTY)\nProperty Table - C Element (TCPROPERTY)\nMaterial Density Table Element (TDENSITY)\nExpansion Coefficient Table Element (TEXPANSION)\nText Element (TEXT)\nPoissons Ratio Table Element (TPOISSON)\nAllowable Stress Table Element (TSTRESS)\nYoungs Modulus Table Element (TYOUNG)\nName\nName of the element\nDescription\nDescription of the element\nPurpose\nDescription code word\nUuid\nUniversally unique identifier\n\n\n\nMaterial World Element (MATWORLD)\nSolids Extended Info Element (SOLEXT)\nProperty Table - A Element (TAPROPERTY)\nProperty Table - B Element (TBPROPERTY)\nProperty Table - C Element (TCPROPERTY)\nMaterial Density Table Element (TDENSITY)\nExpansion Coefficient Table Element (TEXPANSION)\nText Element (TEXT)\nPoissons Ratio Table Element (TPOISSON)\nAllowable Stress Table Element (TSTRESS)\nYoungs Modulus Table Element (TYOUNG)\nName\nDescription\nPurpose\nUuid\nMaterial World Element (MATWORLD)\nSolids Extended Info Element (SOLEXT)\nProperty Table - A Element (TAPROPERTY)\nProperty Table - B Element (TBPROPERTY)\nProperty Table - C Element (TCPROPERTY)\nMaterial Density Table Element (TDENSITY)\nExpansion Coefficient Table Element (TEXPANSION)\nText Element (TEXT)\nPoissons Ratio Table Element (TPOISSON)\nAllowable Stress Table Element (TSTRESS)\nYoungs Modulus Table Element (TYOUNG)"}
{"Headers": "Spot Poissons Ratio Temperature and Pressure Element (SPOISSON)", "Content": "Name\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nPoissons\nSpot value of Poissons ratio\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nPoissons\nSpot value of Poissons ratio\nPoissons Ratio Table Element (TPOISSON)\nNone\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nPoissons\nSpot value of Poissons ratio\n\n\n\nPoissons Ratio Table Element (TPOISSON)\nName\nTemperature\nPressure\nPoissons\nPoissons Ratio Table Element (TPOISSON)"}
{"Headers": "Spot Stress Temperature and Pressure Element (SSTRESS)", "Content": "Name\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nStress\nSpot value of stress\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nStress\nSpot value of stress\nAllowable Stress Table Element (TSTRESS)\nNone\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nStress\nSpot value of stress\n\n\n\nAllowable Stress Table Element (TSTRESS)\nName\nTemperature\nPressure\nStress\nAllowable Stress Table Element (TSTRESS)"}
{"Headers": "Spot Youngs Modulus Temperature and Pressure Element (SYOUNG)", "Content": "Name\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nYoungs\nSpot value of Youngs modulus\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nYoungs\nSpot value of Youngs modulus\nYoungs Modulus Table Element (TYOUNG)\nNone\nName\nName of the element\nTemperature\nTemperature\nPressure\nPressure\nYoungs\nSpot value of Youngs modulus\n\n\n\nYoungs Modulus Table Element (TYOUNG)\nName\nTemperature\nPressure\nYoungs\nYoungs Modulus Table Element (TYOUNG)"}
{"Headers": "Property Table - A Element (TAPROPERTY)", "Content": "Name\nName of the element\nPqualifier\nProperty qualifier\nPname\nProperty description\nSref\nSource reference\nName\nName of the element\nPqualifier\nProperty qualifier\nPname\nProperty description\nSref\nSource reference\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Property A Temperature and Pressure Element (SAPROPERTY)\nName\nName of the element\nPqualifier\nProperty qualifier\nPname\nProperty description\nSref\nSource reference\n\n\n\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Property A Temperature and Pressure Element (SAPROPERTY)\nName\nPqualifier\nPname\nSref\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Property A Temperature and Pressure Element (SAPROPERTY)"}
{"Headers": "Property Table - B Element (TBPROPERTY)", "Content": "Name\nName of the element\nPqualifier\nProperty qualifier\nPname\nProperty description\nSref\nSource reference\nName\nName of the element\nPqualifier\nProperty qualifier\nPname\nProperty description\nSref\nSource reference\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Property B Temperature and Pressure Element (SBPROPERTY)\nName\nName of the element\nPqualifier\nProperty qualifier\nPname\nProperty description\nSref\nSource reference\n\n\n\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Property B Temperature and Pressure Element (SBPROPERTY)\nName\nPqualifier\nPname\nSref\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Property B Temperature and Pressure Element (SBPROPERTY)"}
{"Headers": "Case Table Element (TCASE)", "Content": "Name\nName of the element\nCasref\nCase reference\nName\nName of the element\nCasref\nCase reference\nConstraint Element (CONSTRAINT)\nNone\nName\nName of the element\nCasref\nCase reference\n\n\n\nConstraint Element (CONSTRAINT)\nName\nCasref\nConstraint Element (CONSTRAINT)"}
{"Headers": "Property Table - C Element (TCPROPERTY)", "Content": "Name\nName of the element\nPqualifier\nProperty qualifier\nPname\nProperty description\nSref\nSource reference\nName\nName of the element\nPqualifier\nProperty qualifier\nPname\nProperty description\nSref\nSource reference\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Property C Temperature and Pressure Element (SCPROPERTY)\nName\nName of the element\nPqualifier\nProperty qualifier\nPname\nProperty description\nSref\nSource reference\n\n\n\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Property C Temperature and Pressure Element (SCPROPERTY)\nName\nPqualifier\nPname\nSref\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Property C Temperature and Pressure Element (SCPROPERTY)"}
{"Headers": "Material Density Table Element (TDENSITY)", "Content": "Name\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\nName\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Density Temperature and Pressure Element (SDENSITY)\nName\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\n\n\n\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Density Temperature and Pressure Element (SDENSITY)\nName\nPqualifier\nSref\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Density Temperature and Pressure Element (SDENSITY)"}
{"Headers": "Expansion Coefficient Table Element (TEXPANSION)", "Content": "Name\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\nName\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Expansion Coefficient Temperature and Pressure Element (SEXPANSION)\nName\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\n\n\n\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Expansion Coefficient Temperature and Pressure Element (SEXPANSION)\nName\nPqualifier\nSref\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Expansion Coefficient Temperature and Pressure Element (SEXPANSION)"}
{"Headers": "Text Element (TEXT) - Property", "Content": "Administrative Element\nTEXT is a general element that can occupy most positions in the hierarchy. It can be used to store additional information about an owning or adjacent element.\nName\nName of the element\nPurpose\nDescription code word\nStext\nS Text string\nOrrf\nOrigin reference (for templates)\nName\nName of the element\nPurpose\nDescription code word\nStext\nS Text string\nOrrf\nOrigin reference (for templates)\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nNone\nName\nName of the element\nPurpose\nDescription code word\nStext\nS Text string\nOrrf\nOrigin reference (for templates)\n\n\n\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nName\nPurpose\nStext\nOrrf\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)"}
{"Headers": "Poissons Ratio Table Element (TPOISSON)", "Content": "Name\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\nName\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\nSolid Material Element (SOLID)\nSpot Poissons Ratio Temperature and Pressure Element (SPOISSON)\nName\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\n\n\n\nSolid Material Element (SOLID)\nSpot Poissons Ratio Temperature and Pressure Element (SPOISSON)\nName\nPqualifier\nSref\nSolid Material Element (SOLID)\nSpot Poissons Ratio Temperature and Pressure Element (SPOISSON)"}
{"Headers": "Allowable Stress Table Element (TSTRESS)", "Content": "Name\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\nName\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\nSolid Material Element (SOLID)\nSpot Stress Temperature and Pressure Element (SSTRESS)\nName\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\n\n\n\nSolid Material Element (SOLID)\nSpot Stress Temperature and Pressure Element (SSTRESS)\nName\nPqualifier\nSref\nSolid Material Element (SOLID)\nSpot Stress Temperature and Pressure Element (SSTRESS)"}
{"Headers": "Tube Properties Element (TUBDATA)", "Content": "Name\nName of the element\nOutdiameter\nOutside diameter\nAcbore\nActual bore\nBtolerance\nBore tolerance\nWtolerance\nWall thickness tolerance / Weight tolerance\nUweight\nUnit pipe weight\nUiweight\nUnit insulation weight\nWdiameter\nWind diameter modulus\nShapemodulus\nShape modulus\nRinertia\nRotational inertia vector\nSifactor\nStress intensification factor\nPrfactor\nPressure factor\nSdthickness\nSaddle thickness\nCorallowance\nCorrosion thickness\nEfactor\nE-factor\nPwastage\nPercentage wastage factor\nBflex\nOut of plane flexibility factor for bends\nMrkr\n3 way component marker\nName\nName of the element\nOutdiameter\nOutside diameter\nAcbore\nActual bore\nBtolerance\nBore tolerance\nWtolerance\nWall thickness tolerance / Weight tolerance\nUweight\nUnit pipe weight\nUiweight\nUnit insulation weight\nWdiameter\nWind diameter modulus\nShapemodulus\nShape modulus\nRinertia\nRotational inertia vector\nSifactor\nStress intensification factor\nPrfactor\nPressure factor\nSdthickness\nSaddle thickness\nCorallowance\nCorrosion thickness\nEfactor\nE-factor\nPwastage\nPercentage wastage factor\nBflex\nOut of plane flexibility factor for bends\nMrkr\n3 way component marker\nSorting Category Element (CMPTYPE)\nNone\nName\nName of the element\nOutdiameter\nOutside diameter\nAcbore\nActual bore\nBtolerance\nBore tolerance\nWtolerance\nWall thickness tolerance / Weight tolerance\nUweight\nUnit pipe weight\nUiweight\nUnit insulation weight\nWdiameter\nWind diameter modulus\nShapemodulus\nShape modulus\nRinertia\nRotational inertia vector\nSifactor\nStress intensification factor\nPrfactor\nPressure factor\nSdthickness\nSaddle thickness\nCorallowance\nCorrosion thickness\nEfactor\nE-factor\nPwastage\nPercentage wastage factor\nBflex\nOut of plane flexibility factor for bends\nMrkr\n3 way component marker\n\n\n\nSorting Category Element (CMPTYPE)\nName\nOutdiameter\nAcbore\nBtolerance\nWtolerance\nUweight\nUiweight\nWdiameter\nShapemodulus\nRinertia\nSifactor\nPrfactor\nSdthickness\nCorallowance\nEfactor\nPwastage\nBflex\nMrkr\nSorting Category Element (CMPTYPE)"}
{"Headers": "Youngs Modulus Table Element (TYOUNG)", "Content": "Name\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\nName\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Youngs Modulus Temperature and Pressure Element (SYOUNG)\nName\nName of the element\nPqualifier\nProperty qualifier\nSref\nSource reference\n\n\n\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Youngs Modulus Temperature and Pressure Element (SYOUNG)\nName\nPqualifier\nSref\nFluid Material Element (FLUID)\nSolid Material Element (SOLID)\nSpot Youngs Modulus Temperature and Pressure Element (SYOUNG)"}
{"Headers": "World Element (WORLD) - Property", "Content": "Administrative Element\nPrimary Element\nThe WORLD is the topmost level of the database hierarchy within which all other elements exist. It cannot be deleted or copied in the same way that applies to say, a ZONE or a DRWG. Its existence is controlled by the ADMINISTRATION module.\nName\nName of the element\nName\nName of the element\nNone\nCase World Element (CASWORLD)\nProperty Component World Element (CMPWORLD)\nConstraint Data World Element (CONWORLD)\nGroup World Element (GPWLD)\nMaterial World Element (MATWORLD)\nRun World Element (RUNWORLD)\nName\nName of the element\n\n\n\nCase World Element (CASWORLD)\nProperty Component World Element (CMPWORLD)\nConstraint Data World Element (CONWORLD)\nGroup World Element (GPWLD)\nMaterial World Element (MATWORLD)\nRun World Element (RUNWORLD)\nName\nCase World Element (CASWORLD)\nProperty Component World Element (CMPWORLD)\nConstraint Data World Element (CONWORLD)\nGroup World Element (GPWLD)\nMaterial World Element (MATWORLD)\nRun World Element (RUNWORLD)"}
{"Headers": "Schematic Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the Schematic database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "Schematic Database Elements", "Content": "All data in the Schematic database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Datasheet Instance Group Element (DSIGRO) - Engineering", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nDatasheet Instance World Element (DSIWLD)\nDatasheet Instance Element (DSINST)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nDatasheet Instance World Element (DSIWLD)\nDatasheet Instance Element (DSINST)\nName\nDescription\nDatasheet Instance World Element (DSIWLD)\nDatasheet Instance Element (DSINST)"}
{"Headers": "Datasheet Instance Element (DSINST) - Engineering", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDSTITL\nDatasheet title\nDSSUBT\nDatasheet sub title\nDocNum\nDocument Number\nSHTOT\nTotal Sheets\nDSTREF\nDatasheet Template reference for Datasheet Instance\nDSIAST\nDatasheet Instance assigned tags reference array for Datasheet Instance\nPrmtag\nAssociated Primary Element\nExfile\nExtract file number\nPvno\nPicture version number\nDSNO\nDatasheet number\nName\nName of the element\nDescription\nDescription of the element\nDSTITL\nDatasheet title\nDSSUBT\nDatasheet sub title\nDocNum\nDocument Number\nSHTOT\nTotal Sheets\nDSTREF\nDatasheet Template reference for Datasheet Instance\nDSIAST\nDatasheet Instance assigned tags reference array for Datasheet Instance\nPrmtag\nAssociated Primary Element\nExfile\nExtract file number\nPvno\nPicture version number\nDSNO\nDatasheet number\nDatasheet Instance Group Element (DSIGRO)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDSTITL\nDatasheet title\nDSSUBT\nDatasheet sub title\nDocNum\nDocument Number\nSHTOT\nTotal Sheets\nDSTREF\nDatasheet Template reference for Datasheet Instance\nDSIAST\nDatasheet Instance assigned tags reference array for Datasheet Instance\nPrmtag\nAssociated Primary Element\nExfile\nExtract file number\nPvno\nPicture version number\nDSNO\nDatasheet number\n\n\n\nDatasheet Instance Group Element (DSIGRO)\nName\nDescription\nDSTITL\nDSSUBT\nDocNum\nSHTOT\nDSTREF\nDSIAST\nPrmtag\nExfile\nPvno\nDSNO\nDatasheet Instance Group Element (DSIGRO)"}
{"Headers": "Datasheet Instance World Element (DSIWLD) - Schematic", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nDatasheet Instance Group Element (DSIGRO)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nDatasheet Instance Group Element (DSIGRO)\nName\nDescription\nWorld Element (WORLD)\nDatasheet Instance Group Element (DSIGRO)"}
{"Headers": "Revision and Issue Element (REVISS) - Schematic", "Content": "Primary Element\nName\nName of the element\nRvnum\nRevision number\nRvnpts\nRevision number value parts\nRviss\nIssued\nRvcanc\nCancelled\nRVURI\nIssued object location\nExfile\nExtract file number\nPvno\nPicture version number\nNumber\nNumber\nRVFTYP\nRevision file type\nStahrf\nStatus History Reference\nDBBLOB\nDatabase Binary Large Object\nRelrev\nRelated revisions\nDSTYPE\nDatasheet type\nName\nName of the element\nRvnum\nRevision number\nRvnpts\nRevision number value parts\nRviss\nIssued\nRvcanc\nCancelled\nRVURI\nIssued object location\nExfile\nExtract file number\nPvno\nPicture version number\nNumber\nNumber\nRVFTYP\nRevision file type\nStahrf\nStatus History Reference\nDBBLOB\nDatabase Binary Large Object\nRelrev\nRelated revisions\nDSTYPE\nDatasheet type\nRevision Link Element Element (REVLNK)\nNone\nName\nName of the element\nRvnum\nRevision number\nRvnpts\nRevision number value parts\nRviss\nIssued\nRvcanc\nCancelled\nRVURI\nIssued object location\nExfile\nExtract file number\nPvno\nPicture version number\nNumber\nNumber\nRVFTYP\nRevision file type\nStahrf\nStatus History Reference\nDBBLOB\nDatabase Binary Large Object\nRelrev\nRelated revisions\nDSTYPE\nDatasheet type\n\n\n\nRevision Link Element Element (REVLNK)\nName\nRvnum\nRvnpts\nRviss\nRvcanc\nRVURI\nExfile\nPvno\nNumber\nRVFTYP\nStahrf\nDBBLOB\nRelrev\nDSTYPE\nRevision Link Element Element (REVLNK)"}
{"Headers": "Revision Link Elements Element (REVLKS) - Schematic", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nRevision Link Elements Element (REVLKS)\nRevision Links World Element (REVLWL)\nRevision Link Elements Element (REVLKS)\nRevision Link Element Element (REVLNK)\nName\nName of the element\n\n\n\nRevision Link Elements Element (REVLKS)\nRevision Links World Element (REVLWL)\nRevision Link Elements Element (REVLKS)\nRevision Link Element Element (REVLNK)\nName\nRevision Link Elements Element (REVLKS)\nRevision Links World Element (REVLWL)\nRevision Link Elements Element (REVLKS)\nRevision Link Element Element (REVLNK)"}
{"Headers": "Revision Link Element Element (REVLNK) - Schematic", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nCelref\nStatus Element reference\nRvcon\nRevision Configuration\nName\nName of the element\nDescription\nDescription of the element\nCelref\nStatus Element reference\nRvcon\nRevision Configuration\nRevision Link Elements Element (REVLKS)\nRevision and Issue Element (REVISS)\nName\nName of the element\nDescription\nDescription of the element\nCelref\nStatus Element reference\nRvcon\nRevision Configuration\n\n\n\nRevision Link Elements Element (REVLKS)\nRevision and Issue Element (REVISS)\nName\nDescription\nCelref\nRvcon\nRevision Link Elements Element (REVLKS)\nRevision and Issue Element (REVISS)"}
{"Headers": "Revision Links World Element (REVLWL) - Schematic", "Content": "Primary Element\nName\nName of the element\nRvlpos\nRevision links reference\nName\nName of the element\nRvlpos\nRevision links reference\nWorld Element (WORLD)\nRevision Link Elements Element (REVLKS)\nName\nName of the element\nRvlpos\nRevision links reference\n\n\n\nWorld Element (WORLD)\nRevision Link Elements Element (REVLKS)\nName\nRvlpos\nWorld Element (WORLD)\nRevision Link Elements Element (REVLKS)"}
{"Headers": "Schematic Actuator Element (SCACTUATOR)", "Content": "709 Element\nPrimary Element\nThe SCACTU represents actuator element which can refer to inline elements such as SCVALV, SCFITT and SCINST.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nAlcode\nAlarm code array\nSpref\nComponent spec reference\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nSciref\nInstrument reference\nScirty\nInstrument reference type\nEcrfarray\nEquipment connection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nAlcode\nAlarm code array\nSpref\nComponent spec reference\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nSciref\nInstrument reference\nScirty\nInstrument reference type\nEcrfarray\nEquipment connection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Group Element (SCGROUP)\nText Element (TEXT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nAlcode\nAlarm code array\nSpref\nComponent spec reference\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nSciref\nInstrument reference\nScirty\nInstrument reference type\nEcrfarray\nEquipment connection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Group Element (SCGROUP)\nText Element (TEXT)\nName\nDescription\nFunction\nLocation\nDistag\nPrefix\nLetter\nNumber\nSuffix\nAlcode\nSpref\nIspec\nTspec\nPtspec\nArea\nArrive\nLeave\nPosition\nDiagxpos\nDiagypos\nSciref\nScirty\nEcrfarray\nScsysf\nSclore\nInprtref\nOuprtref\nDiarefarray\nPagearray\nRestatus\nReuser\nRecomment\nREDATE\nScaref\nDesref\nUclone\nClnref\nSchematic Group Element (SCGROUP)\nText Element (TEXT)"}
{"Headers": "Schematic Area Shape Element (SCAREA)", "Content": "Schematic Piping and HVAC Element\nPrimary Element\nRepresents schematic area shape. SCAREA can be referenced by any schematic element which can be represented on drawing. The elements referencing SCAREA are shown in its secondary hierarchy in explorer tree.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Group Element (SCGROUP)\nText Element (TEXT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Group Element (SCGROUP)\nText Element (TEXT)\nName\nDescription\nFunction\nPurpose\nDiarefarray\nPagearray\nDiagxpos\nDiagypos\nScaref\nUclone\nClnref\nSchematic Group Element (SCGROUP)\nText Element (TEXT)"}
{"Headers": "Schematic Branch Element (SCBRANCH)", "Content": "Schematic Piping and HVAC Element\nPrimary Element\nThe SCBRAN is the owner of the SCSEGments. A SCBRAN has a head (HREF) and tail (TREF) which refer to the SCBRANch origin and destination.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nHref\nHead reference\nTref\nTail reference\nTemperature\nTemperature\nPressure\nPressure\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nHstube\nHead tube specification\nHconnect\nHead connection type\nTconnect\nTail connection type\nArea\nArea\nBore\nBore\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nHref\nHead reference\nTref\nTail reference\nTemperature\nTemperature\nPressure\nPressure\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nHstube\nHead tube specification\nHconnect\nHead connection type\nTconnect\nTail connection type\nArea\nArea\nBore\nBore\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic HVAC Element (SCHVAC)\nSchematic Instrumentation Line Element (SCILINE)\nSchematic Pipeline Element (SCPLINE)\nSchematic Segment Element (SCSEGMENT)\nText Element (TEXT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nHref\nHead reference\nTref\nTail reference\nTemperature\nTemperature\nPressure\nPressure\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nHstube\nHead tube specification\nHconnect\nHead connection type\nTconnect\nTail connection type\nArea\nArea\nBore\nBore\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic HVAC Element (SCHVAC)\nSchematic Instrumentation Line Element (SCILINE)\nSchematic Pipeline Element (SCPLINE)\nSchematic Segment Element (SCSEGMENT)\nText Element (TEXT)\nName\nDescription\nFunction\nHref\nTref\nTemperature\nPressure\nPspec\nIspec\nTspec\nFluref\nPtspec\nHstube\nHconnect\nTconnect\nArea\nBore\nInprtref\nOuprtref\nUclone\nClnref\nSchematic HVAC Element (SCHVAC)\nSchematic Instrumentation Line Element (SCILINE)\nSchematic Pipeline Element (SCPLINE)\nSchematic Segment Element (SCSEGMENT)\nText Element (TEXT)"}
{"Headers": "Schematic Cable Element (SCCABLE)", "Content": "Schematic Electrical Element\nPrimary Element\nSCCABle represent a Cable in the schematics. It can connect to SCEQUIpment/SCSUBEquipment or SCELCOnnections.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nFEQDES\nFrom Equipment Description\nTEQDES\nTo Equipment Description\nSpref\nComponent spec reference\nCExes\nCable excesses\nStaRef\nCable Start reference\nStaPoint\nCable Start connection point\nEndRef\nCable End reference\nEndPoint\nCable End connection point\nScsysf\nSystem reference array for schematic elements\nIClass\nInterference class\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nFEQDES\nFrom Equipment Description\nTEQDES\nTo Equipment Description\nSpref\nComponent spec reference\nCExes\nCable excesses\nStaRef\nCable Start reference\nStaPoint\nCable Start connection point\nEndRef\nCable End reference\nEndPoint\nCable End connection point\nScsysf\nSystem reference array for schematic elements\nIClass\nInterference class\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Group Element (SCGROUP)\nSchematic Multi Cable Element (SCMCABLE)\nSchematic Core Element (SCCORE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nFEQDES\nFrom Equipment Description\nTEQDES\nTo Equipment Description\nSpref\nComponent spec reference\nCExes\nCable excesses\nStaRef\nCable Start reference\nStaPoint\nCable Start connection point\nEndRef\nCable End reference\nEndPoint\nCable End connection point\nScsysf\nSystem reference array for schematic elements\nIClass\nInterference class\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Group Element (SCGROUP)\nSchematic Multi Cable Element (SCMCABLE)\nSchematic Core Element (SCCORE)\nName\nDescription\nFunction\nPurpose\nFEQDES\nTEQDES\nSpref\nCExes\nStaRef\nStaPoint\nEndRef\nEndPoint\nScsysf\nIClass\nDiarefarray\nPagearray\nRestatus\nReuser\nRecomment\nREDATE\nScaref\nDesref\nUclone\nClnref\nSchematic Group Element (SCGROUP)\nSchematic Multi Cable Element (SCMCABLE)\nSchematic Core Element (SCCORE)"}
{"Headers": "Schematic Core Element (SCCORE)", "Content": "Schematic Electrical Element\nSCCORE represent a Cable core in the schematics. It can connect to SCELCOnnections.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nStaRef\nCable Start reference\nStaPoint\nCable Start connection point\nEndRef\nCable End reference\nEndPoint\nCable End connection point\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nStaRef\nCable Start reference\nStaPoint\nCable Start connection point\nEndRef\nCable End reference\nEndPoint\nCable End connection point\nSchematic Cable Element (SCCABLE)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nStaRef\nCable Start reference\nStaPoint\nCable Start connection point\nEndRef\nCable End reference\nEndPoint\nCable End connection point\n\n\n\nSchematic Cable Element (SCCABLE)\nName\nDescription\nFunction\nPurpose\nStaRef\nStaPoint\nEndRef\nEndPoint\nSchematic Cable Element (SCCABLE)"}
{"Headers": "Schematic Drawing Element (SCDIAGRAM)", "Content": "Schematic Piping and HVAC Element\nPrimary Element\nSCDIAGram is a proxy element providing a link to a file (such as a Visio file) and a neutral viewer file (svg).\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUrl\nURL\nExfile\nExtract file number\nPvno\nPicture version number\nArno\nPicture directory area number\nNumber\nNumber\nSchtype\nSchematic type\nSchfformat\nSchematic file format\nScsysd\nSystem reference array for schematic diagrams\nSterefarray\nStencil reference array for schematic elements\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUrl\nURL\nExfile\nExtract file number\nPvno\nPicture version number\nArno\nPicture directory area number\nNumber\nNumber\nSchtype\nSchematic type\nSchfformat\nSchematic file format\nScsysd\nSystem reference array for schematic diagrams\nSterefarray\nStencil reference array for schematic elements\nSchematic Group Element (SCGROUP)\nSchematic Document Page Element (SCPAGE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUrl\nURL\nExfile\nExtract file number\nPvno\nPicture version number\nArno\nPicture directory area number\nNumber\nNumber\nSchtype\nSchematic type\nSchfformat\nSchematic file format\nScsysd\nSystem reference array for schematic diagrams\nSterefarray\nStencil reference array for schematic elements\n\n\n\nSchematic Group Element (SCGROUP)\nSchematic Document Page Element (SCPAGE)\nName\nDescription\nFunction\nUrl\nExfile\nPvno\nArno\nNumber\nSchtype\nSchfformat\nScsysd\nSterefarray\nSchematic Group Element (SCGROUP)\nSchematic Document Page Element (SCPAGE)"}
{"Headers": "Schematic Duct Element (SCDUCT)", "Content": "Schematic HVAC Element\nThe SCDUCTs are inline member of SCSEGment in HVAC, representing the ductwork.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nCrfarray\nConnection reference array\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nWidarray\nWidth array\nHeiarray\nHeight array\nConarray\nConnection array\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nCrfarray\nConnection reference array\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nWidarray\nWidth array\nHeiarray\nHeight array\nConarray\nConnection array\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Segment Element (SCSEGMENT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nCrfarray\nConnection reference array\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nWidarray\nWidth array\nHeiarray\nHeight array\nConarray\nConnection array\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Segment Element (SCSEGMENT)\nName\nDescription\nFunction\nDistag\nGtype\nScstype\nSpref\nPspec\nIspec\nTspec\nPtspec\nArea\nArrive\nLeave\nCrfarray\nInprtref\nOuprtref\nWidarray\nHeiarray\nConarray\nScaref\nDesref\nUclone\nClnref\nSchematic Segment Element (SCSEGMENT)"}
{"Headers": "Schematic Electrical Connection Element (SCELCONNECTION)", "Content": "Schematic Equipment Element\nSCELCOnnections provide the link between an SCEQUIpment (which owns them) and a SCCABle which is connected to each one.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nCatref\nCatalogue reference\nIspec\nInsulation spec reference\nDuty\nDuty\nOrrf\nOrigin reference (for templates)\nStmf\nTemplate selection pointer\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nCatref\nCatalogue reference\nIspec\nInsulation spec reference\nDuty\nDuty\nOrrf\nOrigin reference (for templates)\nStmf\nTemplate selection pointer\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Subequipment Element (SCSUBEQUIPMENT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nCatref\nCatalogue reference\nIspec\nInsulation spec reference\nDuty\nDuty\nOrrf\nOrigin reference (for templates)\nStmf\nTemplate selection pointer\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Subequipment Element (SCSUBEQUIPMENT)\nName\nDescription\nFunction\nPurpose\nCatref\nIspec\nDuty\nOrrf\nStmf\nDiarefarray\nPagearray\nDiagxpos\nDiagypos\nScaref\nDesref\nUclone\nClnref\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Subequipment Element (SCSUBEQUIPMENT)"}
{"Headers": "Schematic Equipment Element (SCEQUIPMENT)", "Content": "Schematic Equipment Element\nPrimary Element\nThe SCEQUIpment element represents process vessels, storage vessels, heat exchangers, pumps and any other predefined item that is part of the schematics. It may own SCNOZZless and SCSUBEquipment.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nPurpose\nDescription code word\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nEqclass\nEquipment class\nEqtype\nEquipment class\nNumber\nNumber\nSuffix\nSuffix\nArea\nArea\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nIspec\nInsulation spec reference\nSpref\nComponent spec reference\nEcrfarray\nEquipment connection reference array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nPurpose\nDescription code word\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nEqclass\nEquipment class\nEqtype\nEquipment class\nNumber\nNumber\nSuffix\nSuffix\nArea\nArea\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nIspec\nInsulation spec reference\nSpref\nComponent spec reference\nEcrfarray\nEquipment connection reference array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Group Element (SCGROUP)\nSchematic Electrical Connection Element (SCELCONNECTION)\nSchematic Nozzles Element (SCNOZZLE)\nSchematic Subequipment Element (SCSUBEQUIPMENT)\nText Element (TEXT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nPurpose\nDescription code word\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nEqclass\nEquipment class\nEqtype\nEquipment class\nNumber\nNumber\nSuffix\nSuffix\nArea\nArea\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nIspec\nInsulation spec reference\nSpref\nComponent spec reference\nEcrfarray\nEquipment connection reference array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Group Element (SCGROUP)\nSchematic Electrical Connection Element (SCELCONNECTION)\nSchematic Nozzles Element (SCNOZZLE)\nSchematic Subequipment Element (SCSUBEQUIPMENT)\nText Element (TEXT)\nName\nDescription\nFunction\nLocation\nPurpose\nDistag\nPrefix\nLetter\nEqclass\nEqtype\nNumber\nSuffix\nArea\nScsysf\nSclore\nDiarefarray\nPagearray\nIspec\nSpref\nEcrfarray\nPosition\nDiagxpos\nDiagypos\nRestatus\nReuser\nRecomment\nREDATE\nInprtref\nOuprtref\nScaref\nDesref\nUclone\nClnref\nSchematic Group Element (SCGROUP)\nSchematic Electrical Connection Element (SCELCONNECTION)\nSchematic Nozzles Element (SCNOZZLE)\nSchematic Subequipment Element (SCSUBEQUIPMENT)\nText Element (TEXT)"}
{"Headers": "Schematic Fitting Element (SCFITTING)", "Content": "Schematic Piping Element\nThe SCFITTings are inline member of SCSEGment. A SCFITTing can have up to ten (10) connections.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nBorearray\nBore array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCrfarray\nConnection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nBorearray\nBore array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCrfarray\nConnection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Segment Element (SCSEGMENT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nBorearray\nBore array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCrfarray\nConnection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Segment Element (SCSEGMENT)\nName\nDescription\nFunction\nDistag\nPrefix\nLetter\nNumber\nSuffix\nGtype\nScstype\nSpref\nPspec\nIspec\nTspec\nPtspec\nArea\nFailcond\nArrive\nLeave\nBorearray\nPosition\nDiagxpos\nDiagypos\nCrfarray\nScsysf\nSclore\nInprtref\nOuprtref\nScaref\nDesref\nUclone\nClnref\nSchematic Segment Element (SCSEGMENT)"}
{"Headers": "Schematic Group Element (SCGROUP)", "Content": "Schematic Piping and HVAC Element\nPrimary Element\nThe SCGROUp is an administrative owner of schematic elements such as SCPLIN, SCHVAC, SCEQUI, SCCAB etc. A SCGROUp can own other SCGROUps.\nName\nName of the element\nName\nName of the element\nSchematic Group Element (SCGROUP)\nWorld Element (WORLD)\nSchematic Actuator Element (SCACTUATOR)\nSchematic Area Shape Element (SCAREA)\nSchematic Cable Element (SCCABLE)\nSchematic Drawing Element (SCDIAGRAM)\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Group Element (SCGROUP)\nSchematic HVAC Element (SCHVAC)\nSchematic Instrumentation Line Element (SCILINE)\nSchematic Instrumentation Loop Element (SCLOOP)\nSchematic Multi Cable Element (SCMCABLE)\nSchematic Offline Instrument Element (SCOINSTRUMENT)\nSchematic Pipeline Element (SCPLINE)\nSchematic Stencil Element (SCSTENCIL)\nSchematic Template Element (SCTEMPLATE)\nName\nName of the element\n\n\n\nSchematic Group Element (SCGROUP)\nWorld Element (WORLD)\nSchematic Actuator Element (SCACTUATOR)\nSchematic Area Shape Element (SCAREA)\nSchematic Cable Element (SCCABLE)\nSchematic Drawing Element (SCDIAGRAM)\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Group Element (SCGROUP)\nSchematic HVAC Element (SCHVAC)\nSchematic Instrumentation Line Element (SCILINE)\nSchematic Instrumentation Loop Element (SCLOOP)\nSchematic Multi Cable Element (SCMCABLE)\nSchematic Offline Instrument Element (SCOINSTRUMENT)\nSchematic Pipeline Element (SCPLINE)\nSchematic Stencil Element (SCSTENCIL)\nSchematic Template Element (SCTEMPLATE)\nName\nSchematic Group Element (SCGROUP)\nWorld Element (WORLD)\nSchematic Actuator Element (SCACTUATOR)\nSchematic Area Shape Element (SCAREA)\nSchematic Cable Element (SCCABLE)\nSchematic Drawing Element (SCDIAGRAM)\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Group Element (SCGROUP)\nSchematic HVAC Element (SCHVAC)\nSchematic Instrumentation Line Element (SCILINE)\nSchematic Instrumentation Loop Element (SCLOOP)\nSchematic Multi Cable Element (SCMCABLE)\nSchematic Offline Instrument Element (SCOINSTRUMENT)\nSchematic Pipeline Element (SCPLINE)\nSchematic Stencil Element (SCSTENCIL)\nSchematic Template Element (SCTEMPLATE)"}
{"Headers": "Schematic HVAC Element (SCHVAC)", "Content": "Schematic HVAC Element\nPrimary Element\nThe SCHVAC is an administrative owner of one or more two-ended SCBRANches. Usually a SCHVAC will include a principle SCBRANch routed between two SCNOZZles.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLinetype\nLine type\nNumber\nNumber\nBore\nBore\nTemperature\nTemperature\nPressure\nPressure\nDtmpmax\nDesign temp. max\nDtmpmin\nDesign temp. min\nOtmpmax\nOperating temp. max\nOtmpmin\nOperating temp. min\nDpremax\nDesign pres. max\nDpremin\nDesign pres. min\nOpremax\nOperating pres. max\nOpremin\nOperating pres. min\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nDuctwidth\nDefault duct width\nDuctheight\nDefault duct height\nDuctshape\nDefault duct shape\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLinetype\nLine type\nNumber\nNumber\nBore\nBore\nTemperature\nTemperature\nPressure\nPressure\nDtmpmax\nDesign temp. max\nDtmpmin\nDesign temp. min\nOtmpmax\nOperating temp. max\nOtmpmin\nOperating temp. min\nDpremax\nDesign pres. max\nDpremin\nDesign pres. min\nOpremax\nOperating pres. max\nOpremin\nOperating pres. min\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nDuctwidth\nDefault duct width\nDuctheight\nDefault duct height\nDuctshape\nDefault duct shape\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Group Element (SCGROUP)\nSchematic Branch Element (SCBRANCH)\nText Element (TEXT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLinetype\nLine type\nNumber\nNumber\nBore\nBore\nTemperature\nTemperature\nPressure\nPressure\nDtmpmax\nDesign temp. max\nDtmpmin\nDesign temp. min\nOtmpmax\nOperating temp. max\nOtmpmin\nOperating temp. min\nDpremax\nDesign pres. max\nDpremin\nDesign pres. min\nOpremax\nOperating pres. max\nOpremin\nOperating pres. min\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nDuctwidth\nDefault duct width\nDuctheight\nDefault duct height\nDuctshape\nDefault duct shape\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Group Element (SCGROUP)\nSchematic Branch Element (SCBRANCH)\nText Element (TEXT)\nName\nDescription\nFunction\nPurpose\nLinetype\nNumber\nBore\nTemperature\nPressure\nDtmpmax\nDtmpmin\nOtmpmax\nOtmpmin\nDpremax\nDpremin\nOpremax\nOpremin\nPspec\nIspec\nTspec\nFluref\nPtspec\nDuctwidth\nDuctheight\nDuctshape\nInprtref\nOuprtref\nScsysf\nUclone\nClnref\nSchematic Group Element (SCGROUP)\nSchematic Branch Element (SCBRANCH)\nText Element (TEXT)"}
{"Headers": "Schematic HVAC Fitting Element (SCHVFITTING)", "Content": "Schematic HVAC Element\nThe SCHVFIttings are inline member of SCSEGment in HVAC. A SCHVFItting can have up to ten (10) connections.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCrfarray\nConnection reference array\nScsysf\nSystem reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nWidarray\nWidth array\nHeiarray\nHeight array\nConarray\nConnection array\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCrfarray\nConnection reference array\nScsysf\nSystem reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nWidarray\nWidth array\nHeiarray\nHeight array\nConarray\nConnection array\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Segment Element (SCSEGMENT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCrfarray\nConnection reference array\nScsysf\nSystem reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nWidarray\nWidth array\nHeiarray\nHeight array\nConarray\nConnection array\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Segment Element (SCSEGMENT)\nName\nDescription\nFunction\nDistag\nPrefix\nLetter\nNumber\nSuffix\nGtype\nScstype\nSpref\nPspec\nIspec\nTspec\nPtspec\nArea\nFailcond\nArrive\nLeave\nPosition\nDiagxpos\nDiagypos\nCrfarray\nScsysf\nInprtref\nOuprtref\nWidarray\nHeiarray\nConarray\nScaref\nDesref\nUclone\nClnref\nSchematic Segment Element (SCSEGMENT)"}
{"Headers": "Schematic Instrumentation Line Element (SCILINE)", "Content": "709 Element\nPrimary Element\nThe SCILIN is an administrative owner of one or more two-ended SCBRANches. Usually a SCILIN will be used for creating detailed instrument lines.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLinetype\nLine type\nNumber\nNumber\nBore\nBore\nTemperature\nTemperature\nPressure\nPressure\nDtmpmax\nDesign temp. max\nDtmpmin\nDesign temp. min\nOtmpmax\nOperating temp. max\nOtmpmin\nOperating temp. min\nDpremax\nDesign pres. max\nDpremin\nDesign pres. min\nOpremax\nOperating pres. max\nOpremin\nOperating pres. min\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLinetype\nLine type\nNumber\nNumber\nBore\nBore\nTemperature\nTemperature\nPressure\nPressure\nDtmpmax\nDesign temp. max\nDtmpmin\nDesign temp. min\nOtmpmax\nOperating temp. max\nOtmpmin\nOperating temp. min\nDpremax\nDesign pres. max\nDpremin\nDesign pres. min\nOpremax\nOperating pres. max\nOpremin\nOperating pres. min\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Group Element (SCGROUP)\nSchematic Branch Element (SCBRANCH)\nText Element (TEXT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLinetype\nLine type\nNumber\nNumber\nBore\nBore\nTemperature\nTemperature\nPressure\nPressure\nDtmpmax\nDesign temp. max\nDtmpmin\nDesign temp. min\nOtmpmax\nOperating temp. max\nOtmpmin\nOperating temp. min\nDpremax\nDesign pres. max\nDpremin\nDesign pres. min\nOpremax\nOperating pres. max\nOpremin\nOperating pres. min\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Group Element (SCGROUP)\nSchematic Branch Element (SCBRANCH)\nText Element (TEXT)\nName\nDescription\nFunction\nPurpose\nLinetype\nNumber\nBore\nTemperature\nPressure\nDtmpmax\nDtmpmin\nOtmpmax\nOtmpmin\nDpremax\nDpremin\nOpremax\nOpremin\nPspec\nIspec\nTspec\nFluref\nPtspec\nInprtref\nOuprtref\nScsysf\nSclore\nUclone\nClnref\nSchematic Group Element (SCGROUP)\nSchematic Branch Element (SCBRANCH)\nText Element (TEXT)"}
{"Headers": "Schematic Element Index Element (SCIND)", "Content": "SCIND represents an element index in the schematics.\nUuid\nUniversally unique identifier\nSCReference\nSchematic element reference\nUuid\nUniversally unique identifier\nSCReference\nSchematic element reference\nSchematic Document Page Element (SCPAGE)\nNone\nUuid\nUniversally unique identifier\nSCReference\nSchematic element reference\n\n\n\nSchematic Document Page Element (SCPAGE)\nUuid\nSCReference\nSchematic Document Page Element (SCPAGE)"}
{"Headers": "Schematic Instrument Element (SCINSTRUMENT)", "Content": "Schematic Piping Element\nThe SCINSTrument is a inline instrument, meaning it will be a member of a SCSEGment, similar to SCFITTings and SCVALVes. A SCINSTrument can have up to ten (10) connections.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nAlcode\nAlarm code array\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nBorearray\nBore array\nCrfarray\nConnection reference array\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nAlcode\nAlarm code array\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nBorearray\nBore array\nCrfarray\nConnection reference array\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Segment Element (SCSEGMENT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nAlcode\nAlarm code array\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nBorearray\nBore array\nCrfarray\nConnection reference array\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Segment Element (SCSEGMENT)\nName\nDescription\nFunction\nLocation\nDistag\nPrefix\nLetter\nNumber\nSuffix\nAlcode\nGtype\nScstype\nSpref\nPspec\nIspec\nTspec\nPtspec\nArea\nFailcond\nArrive\nLeave\nPosition\nDiagxpos\nDiagypos\nBorearray\nCrfarray\nInprtref\nOuprtref\nScsysf\nSclore\nScaref\nDesref\nUclone\nClnref\nSchematic Segment Element (SCSEGMENT)"}
{"Headers": "Schematic Instrumentation Loop Element (SCLOOP)", "Content": "709 Element\nPrimary Element\nRepresents schematic instrumentation loop. SCLOOP can be referenced by inline components, equipments. The elements referencing SCLOIOP are shown in its secondary hierarchy in explorer tree.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Group Element (SCGROUP)\nText Element (TEXT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Group Element (SCGROUP)\nText Element (TEXT)\nName\nDescription\nFunction\nUclone\nClnref\nSchematic Group Element (SCGROUP)\nText Element (TEXT)"}
{"Headers": "Schematic Multi Cable Element (SCMCABLE)", "Content": "Schematic Electrical Element\nPrimary Element\nSCMCABle represent a Multi Cable in the schematics. It can connect to SCEQUIpment/SCSUBEquipment or SCELCOnnections.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nScquantity\nQuantity\nScdigits\nDigits\nScdelimiter\nDelimiter\nScalpha\nALPHA/NOALPHA flag\nFEQDES\nFrom Equipment Description\nTEQDES\nTo Equipment Description\nSpref\nComponent spec reference\nCExes\nCable excesses\nStaRef\nCable Start reference\nStaPoint\nCable Start connection point\nEndRef\nCable End reference\nEndPoint\nCable End connection point\nScsysf\nSystem reference array for schematic elements\nIClass\nInterference class\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nScquantity\nQuantity\nScdigits\nDigits\nScdelimiter\nDelimiter\nScalpha\nALPHA/NOALPHA flag\nFEQDES\nFrom Equipment Description\nTEQDES\nTo Equipment Description\nSpref\nComponent spec reference\nCExes\nCable excesses\nStaRef\nCable Start reference\nStaPoint\nCable Start connection point\nEndRef\nCable End reference\nEndPoint\nCable End connection point\nScsysf\nSystem reference array for schematic elements\nIClass\nInterference class\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Group Element (SCGROUP)\nSchematic Cable Element (SCCABLE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nScquantity\nQuantity\nScdigits\nDigits\nScdelimiter\nDelimiter\nScalpha\nALPHA/NOALPHA flag\nFEQDES\nFrom Equipment Description\nTEQDES\nTo Equipment Description\nSpref\nComponent spec reference\nCExes\nCable excesses\nStaRef\nCable Start reference\nStaPoint\nCable Start connection point\nEndRef\nCable End reference\nEndPoint\nCable End connection point\nScsysf\nSystem reference array for schematic elements\nIClass\nInterference class\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Group Element (SCGROUP)\nSchematic Cable Element (SCCABLE)\nName\nDescription\nFunction\nPurpose\nScquantity\nScdigits\nScdelimiter\nScalpha\nFEQDES\nTEQDES\nSpref\nCExes\nStaRef\nStaPoint\nEndRef\nEndPoint\nScsysf\nIClass\nDiarefarray\nPagearray\nScaref\nDesref\nUclone\nClnref\nSchematic Group Element (SCGROUP)\nSchematic Cable Element (SCCABLE)"}
{"Headers": "Schematic Nozzles Element (SCNOZZLE)", "Content": "Schematic Equipment Element\nSCNOZZles provide the link between an SCEQUIpment (which owns them) and a SCPLIN (SCBRANCH) which is connected to each one.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nTemperature\nTemperature\nPressure\nPressure\nBore\nBore\nCref\nConnection reference\nCatref\nCatalogue reference\nIspec\nInsulation spec reference\nNspec\nSpecification for NOZZLE\nScgtype\nSchematic nozzle gtype\nDuty\nDuty\nDuctwidth\nDefault duct width\nDuctheight\nDefault duct height\nDuctshape\nDefault duct shape\nDiarefarray\nDiagram reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nPagearray\nPage in diagram\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nTemperature\nTemperature\nPressure\nPressure\nBore\nBore\nCref\nConnection reference\nCatref\nCatalogue reference\nIspec\nInsulation spec reference\nNspec\nSpecification for NOZZLE\nScgtype\nSchematic nozzle gtype\nDuty\nDuty\nDuctwidth\nDefault duct width\nDuctheight\nDefault duct height\nDuctshape\nDefault duct shape\nDiarefarray\nDiagram reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nPagearray\nPage in diagram\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Subequipment Element (SCSUBEQUIPMENT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nTemperature\nTemperature\nPressure\nPressure\nBore\nBore\nCref\nConnection reference\nCatref\nCatalogue reference\nIspec\nInsulation spec reference\nNspec\nSpecification for NOZZLE\nScgtype\nSchematic nozzle gtype\nDuty\nDuty\nDuctwidth\nDefault duct width\nDuctheight\nDefault duct height\nDuctshape\nDefault duct shape\nDiarefarray\nDiagram reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nPagearray\nPage in diagram\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Subequipment Element (SCSUBEQUIPMENT)\nName\nDescription\nFunction\nPurpose\nTemperature\nPressure\nBore\nCref\nCatref\nIspec\nNspec\nScgtype\nDuty\nDuctwidth\nDuctheight\nDuctshape\nDiarefarray\nInprtref\nOuprtref\nPagearray\nDiagxpos\nDiagypos\nScaref\nDesref\nUclone\nClnref\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Subequipment Element (SCSUBEQUIPMENT)"}
{"Headers": "Schematic Offline Instrument Element (SCOINSTRUMENT)", "Content": "Schematic Piping and HVAC Element\nPrimary Element\nThe SCOINStrument is an off-line instrument which can refer to other elements, such as SCTUB, SCVALV, SCFITT, SCINST, SCDUCT and SCHVFI. Typically, it might be an actuator referring to a SCVALVe.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nAlcode\nAlarm code array\nSpref\nComponent spec reference\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCref\nConnection reference\nSciref\nInstrument reference\nScirty\nInstrument reference type\nEcrfarray\nEquipment connection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nAlcode\nAlarm code array\nSpref\nComponent spec reference\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCref\nConnection reference\nSciref\nInstrument reference\nScirty\nInstrument reference type\nEcrfarray\nEquipment connection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Group Element (SCGROUP)\nText Element (TEXT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nAlcode\nAlarm code array\nSpref\nComponent spec reference\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCref\nConnection reference\nSciref\nInstrument reference\nScirty\nInstrument reference type\nEcrfarray\nEquipment connection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Group Element (SCGROUP)\nText Element (TEXT)\nName\nDescription\nFunction\nLocation\nDistag\nPrefix\nLetter\nNumber\nSuffix\nAlcode\nSpref\nIspec\nTspec\nPtspec\nArea\nArrive\nLeave\nPosition\nDiagxpos\nDiagypos\nCref\nSciref\nScirty\nEcrfarray\nScsysf\nSclore\nInprtref\nOuprtref\nDiarefarray\nPagearray\nRestatus\nReuser\nRecomment\nREDATE\nScaref\nDesref\nUclone\nClnref\nSchematic Group Element (SCGROUP)\nText Element (TEXT)"}
{"Headers": "Schematic Off-page Connection Input Element (SCOPCI)", "Content": "Schematic Piping and HVAC Element\nThe SCOPCI are incoming off-page connector used to build up chains of SCSEGments in a SCBRANch via its OPCREF attribute.\nName\nName of the element\nOpcref\nOffpage connector reference\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nOpcref\nOffpage connector reference\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Segment Element (SCSEGMENT)\nNone\nName\nName of the element\nOpcref\nOffpage connector reference\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Segment Element (SCSEGMENT)\nName\nOpcref\nArrive\nLeave\nDiagxpos\nDiagypos\nScaref\nDesref\nUclone\nClnref\nSchematic Segment Element (SCSEGMENT)"}
{"Headers": "Schematic Off-page Connection Output Element (SCOPCO)", "Content": "Schematic Piping and HVAC Element\nThe SCOPCO are outgoing off-page connector used to build up chains of SCSEGments in a SCBRANch via its OPCREF attribute.\nName\nName of the element\nOpcref\nOffpage connector reference\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nOpcref\nOffpage connector reference\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Segment Element (SCSEGMENT)\nNone\nName\nName of the element\nOpcref\nOffpage connector reference\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Segment Element (SCSEGMENT)\nName\nOpcref\nArrive\nLeave\nDiagxpos\nDiagypos\nScaref\nDesref\nUclone\nClnref\nSchematic Segment Element (SCSEGMENT)"}
{"Headers": "Schematic Document Page Element (SCPAGE)", "Content": "SCPAGE represents a document page in the schematics.\nUuid\nUniversally unique identifier\nSCPaname\nSchematic page name\nSCPatype\nSchematic page type\nUuid\nUniversally unique identifier\nSCPaname\nSchematic page name\nSCPatype\nSchematic page type\nSchematic Drawing Element (SCDIAGRAM)\nSchematic Template Element (SCTEMPLATE)\nSchematic Element Index Element (SCIND)\nUuid\nUniversally unique identifier\nSCPaname\nSchematic page name\nSCPatype\nSchematic page type\n\n\n\nSchematic Drawing Element (SCDIAGRAM)\nSchematic Template Element (SCTEMPLATE)\nSchematic Element Index Element (SCIND)\nUuid\nSCPaname\nSCPatype\nSchematic Drawing Element (SCDIAGRAM)\nSchematic Template Element (SCTEMPLATE)\nSchematic Element Index Element (SCIND)"}
{"Headers": "Schematic Pipe Destination Element (SCPDESTINATION)", "Content": "Schematic Piping Element\nThe SCPDEStination is a schematic element representing a pipeline destination to avoid having unconnected ends.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLocation\nLocation\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLocation\nLocation\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Segment Element (SCSEGMENT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLocation\nLocation\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Segment Element (SCSEGMENT)\nName\nDescription\nFunction\nPurpose\nLocation\nArrive\nLeave\nPosition\nDiagxpos\nDiagypos\nScaref\nDesref\nUclone\nClnref\nSchematic Segment Element (SCSEGMENT)"}
{"Headers": "Schematic Pipeline Element (SCPLINE)", "Content": "Schematic Piping Element\nPrimary Element\nThe SCPLIN is an administrative owner of one or more two-ended SCBRANches. Usually a SCPLIN will include a principle SCBRANch routed between two SCNOZZles, with subsidiary SCBRANches for control loops, bypasses to spare pumps etc.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLinetype\nLine type\nNumber\nNumber\nBore\nBore\nTemperature\nTemperature\nPressure\nPressure\nDtmpmax\nDesign temp. max\nDtmpmin\nDesign temp. min\nOtmpmax\nOperating temp. max\nOtmpmin\nOperating temp. min\nDpremax\nDesign pres. max\nDpremin\nDesign pres. min\nOpremax\nOperating pres. max\nOpremin\nOperating pres. min\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLinetype\nLine type\nNumber\nNumber\nBore\nBore\nTemperature\nTemperature\nPressure\nPressure\nDtmpmax\nDesign temp. max\nDtmpmin\nDesign temp. min\nOtmpmax\nOperating temp. max\nOtmpmin\nOperating temp. min\nDpremax\nDesign pres. max\nDpremin\nDesign pres. min\nOpremax\nOperating pres. max\nOpremin\nOperating pres. min\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Group Element (SCGROUP)\nSchematic Branch Element (SCBRANCH)\nText Element (TEXT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nLinetype\nLine type\nNumber\nNumber\nBore\nBore\nTemperature\nTemperature\nPressure\nPressure\nDtmpmax\nDesign temp. max\nDtmpmin\nDesign temp. min\nOtmpmax\nOperating temp. max\nOtmpmin\nOperating temp. min\nDpremax\nDesign pres. max\nDpremin\nDesign pres. min\nOpremax\nOperating pres. max\nOpremin\nOperating pres. min\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nFluref\nFluid reference\nPtspec\nPaint specification\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScsysf\nSystem reference array for schematic elements\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Group Element (SCGROUP)\nSchematic Branch Element (SCBRANCH)\nText Element (TEXT)\nName\nDescription\nFunction\nPurpose\nLinetype\nNumber\nBore\nTemperature\nPressure\nDtmpmax\nDtmpmin\nOtmpmax\nOtmpmin\nDpremax\nDpremin\nOpremax\nOpremin\nPspec\nIspec\nTspec\nFluref\nPtspec\nInprtref\nOuprtref\nScsysf\nUclone\nClnref\nSchematic Group Element (SCGROUP)\nSchematic Branch Element (SCBRANCH)\nText Element (TEXT)"}
{"Headers": "Schematic Segment Element (SCSEGMENT)", "Content": "Schematic Piping and HVAC Element\nPrimary Element\nThe SCSEGment is the owner of the actual SCFITTings and SCVALVes (or SCHVFIttings for HVAC). The components are in sequential order in the SCSEGment. The head (HREF) and tail (TREF) refer to the owning SCBRANch if it is a start/end SCSEGment of a SCBRANch. SCSEGments are concatenated by using SCOPCI/SCOPCO elements in the start/end of a SCSEGment. A SCOPCI can refer to a SCOPCO and vice versa to build up a chain of SCSEGments.\nName\nName of the element\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nHref\nHead reference\nTref\nTail reference\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nHref\nHead reference\nTref\nTail reference\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Branch Element (SCBRANCH)\nSchematic Duct Element (SCDUCT)\nSchematic Fitting Element (SCFITTING)\nSchematic HVAC Fitting Element (SCHVFITTING)\nSchematic Instrument Element (SCINSTRUMENT)\nSchematic Off-page Connection Input Element (SCOPCI)\nSchematic Off-page Connection Output Element (SCOPCO)\nSchematic Pipe Destination Element (SCPDESTINATION)\nSchematic Tubing Element (SCTUBING)\nSchematic Valve Element (SCVALV)\nName\nName of the element\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nHref\nHead reference\nTref\nTail reference\nRestatus\nRelease to 3D status\nReuser\nRelease to 3D user\nRecomment\nRelease to 3D comment\nREDATE\nRelease to 3D date\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Branch Element (SCBRANCH)\nSchematic Duct Element (SCDUCT)\nSchematic Fitting Element (SCFITTING)\nSchematic HVAC Fitting Element (SCHVFITTING)\nSchematic Instrument Element (SCINSTRUMENT)\nSchematic Off-page Connection Input Element (SCOPCI)\nSchematic Off-page Connection Output Element (SCOPCO)\nSchematic Pipe Destination Element (SCPDESTINATION)\nSchematic Tubing Element (SCTUBING)\nSchematic Valve Element (SCVALV)\nName\nDiarefarray\nPagearray\nHref\nTref\nRestatus\nReuser\nRecomment\nREDATE\nUclone\nClnref\nSchematic Branch Element (SCBRANCH)\nSchematic Duct Element (SCDUCT)\nSchematic Fitting Element (SCFITTING)\nSchematic HVAC Fitting Element (SCHVFITTING)\nSchematic Instrument Element (SCINSTRUMENT)\nSchematic Off-page Connection Input Element (SCOPCI)\nSchematic Off-page Connection Output Element (SCOPCO)\nSchematic Pipe Destination Element (SCPDESTINATION)\nSchematic Tubing Element (SCTUBING)\nSchematic Valve Element (SCVALV)"}
{"Headers": "Schematic Stencil Element (SCSTENCIL)", "Content": "Schematic Piping and HVAC Element\nPrimary Element\nSCSTENcil is a proxy element providing a link to a stencil file (such as a Visio stencil file).\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUrl\nURL\nExfile\nExtract file number\nPvno\nPicture version number\nArno\nPicture directory area number\nSchfformat\nSchematic file format\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUrl\nURL\nExfile\nExtract file number\nPvno\nPicture version number\nArno\nPicture directory area number\nSchfformat\nSchematic file format\nSchematic Group Element (SCGROUP)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUrl\nURL\nExfile\nExtract file number\nPvno\nPicture version number\nArno\nPicture directory area number\nSchfformat\nSchematic file format\n\n\n\nSchematic Group Element (SCGROUP)\nName\nDescription\nFunction\nUrl\nExfile\nPvno\nArno\nSchfformat\nSchematic Group Element (SCGROUP)"}
{"Headers": "Schematic Subequipment Element (SCSUBEQUIPMENT)", "Content": "Schematic Equipment Element\nPrimary Element\nThe SCSUBEquipment element is similar to the SCEQUIpment element, except that it is owned by an SCEQUIpment element and cannot itself own SCSUBEquipment elements.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nPurpose\nDescription code word\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nEqclass\nEquipment class\nEqtype\nEquipment class\nNumber\nNumber\nSuffix\nSuffix\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nIspec\nInsulation spec reference\nSpref\nComponent spec reference\nEcrfarray\nEquipment connection reference array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nPurpose\nDescription code word\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nEqclass\nEquipment class\nEqtype\nEquipment class\nNumber\nNumber\nSuffix\nSuffix\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nIspec\nInsulation spec reference\nSpref\nComponent spec reference\nEcrfarray\nEquipment connection reference array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Electrical Connection Element (SCELCONNECTION)\nSchematic Nozzles Element (SCNOZZLE)\nText Element (TEXT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nPurpose\nDescription code word\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nEqclass\nEquipment class\nEqtype\nEquipment class\nNumber\nNumber\nSuffix\nSuffix\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nDiarefarray\nDiagram reference array for schematic elements\nPagearray\nPage in diagram\nIspec\nInsulation spec reference\nSpref\nComponent spec reference\nEcrfarray\nEquipment connection reference array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Electrical Connection Element (SCELCONNECTION)\nSchematic Nozzles Element (SCNOZZLE)\nText Element (TEXT)\nName\nDescription\nFunction\nLocation\nPurpose\nDistag\nPrefix\nLetter\nEqclass\nEqtype\nNumber\nSuffix\nScsysf\nSclore\nDiarefarray\nPagearray\nIspec\nSpref\nEcrfarray\nPosition\nDiagxpos\nDiagypos\nScaref\nDesref\nUclone\nClnref\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic Electrical Connection Element (SCELCONNECTION)\nSchematic Nozzles Element (SCNOZZLE)\nText Element (TEXT)"}
{"Headers": "Schematic Template Element (SCTEMPLATE)", "Content": "Schematic Piping and HVAC Element\nPrimary Element\nSCTEMPlate is a proxy element providing a link to a template file (such as a Visio template file).\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUrl\nURL\nExfile\nExtract file number\nPvno\nPicture version number\nArno\nPicture directory area number\nSchfformat\nSchematic file format\nSterefarray\nStencil reference array for schematic elements\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUrl\nURL\nExfile\nExtract file number\nPvno\nPicture version number\nArno\nPicture directory area number\nSchfformat\nSchematic file format\nSterefarray\nStencil reference array for schematic elements\nSchematic Group Element (SCGROUP)\nSchematic Document Page Element (SCPAGE)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nUrl\nURL\nExfile\nExtract file number\nPvno\nPicture version number\nArno\nPicture directory area number\nSchfformat\nSchematic file format\nSterefarray\nStencil reference array for schematic elements\n\n\n\nSchematic Group Element (SCGROUP)\nSchematic Document Page Element (SCPAGE)\nName\nDescription\nFunction\nUrl\nExfile\nPvno\nArno\nSchfformat\nSterefarray\nSchematic Group Element (SCGROUP)\nSchematic Document Page Element (SCPAGE)"}
{"Headers": "Schematic Tubing Element (SCTUBING)", "Content": "Schematic Piping Element\nThe SCTUBe are inline member of SCSEGment representing the tubing.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nBorearray\nBore array\nCrfarray\nConnection reference array\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nBorearray\nBore array\nCrfarray\nConnection reference array\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Segment Element (SCSEGMENT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nDistag\nDisplay tag\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nBorearray\nBore array\nCrfarray\nConnection reference array\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Segment Element (SCSEGMENT)\nName\nDescription\nFunction\nDistag\nGtype\nScstype\nSpref\nPspec\nIspec\nTspec\nPtspec\nArea\nArrive\nLeave\nBorearray\nCrfarray\nSclore\nInprtref\nOuprtref\nScaref\nDesref\nUclone\nClnref\nSchematic Segment Element (SCSEGMENT)"}
{"Headers": "Schematic Valve Element (SCVALV)", "Content": "Schematic Piping Element\nThe SCVALVes are inline member of SCSEGment. A SCVALVe can have up to ten (10) connections.\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nBorearray\nBore array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCrfarray\nConnection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nBorearray\nBore array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCrfarray\nConnection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\nSchematic Segment Element (SCSEGMENT)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLocation\nLocation\nDistag\nDisplay tag\nPrefix\nPrefix\nLetter\nLetter\nNumber\nNumber\nSuffix\nSuffix\nGtype\nGeneric type\nScstype\nSchematic stype\nSpref\nComponent spec reference\nPspec\nPipe specification\nIspec\nInsulation spec reference\nTspec\nTracing spec reference\nPtspec\nPaint specification\nArea\nArea\nFailcond\nFailCond\nArrive\nArrive Ppoint\nLeave\nLeave Ppoint\nBorearray\nBore array\nPosition\nPosition\nDiagxpos\nX position of the symbol on Visio drawing in mm\nDiagypos\nY position of the symbol on Visio drawing in mm\nCrfarray\nConnection reference array\nScsysf\nSystem reference array for schematic elements\nSclore\nInstrumentation loop reference array for schematic elements\nInprtref\nInside paint reference\nOuprtref\nOutside paint reference\nScaref\nArea shape reference\nDesref\nDesign reference\nUclone\nPropagate to linked elements\nClnref\nReferences to clones of this element\n\n\n\nSchematic Segment Element (SCSEGMENT)\nName\nDescription\nFunction\nLocation\nDistag\nPrefix\nLetter\nNumber\nSuffix\nGtype\nScstype\nSpref\nPspec\nIspec\nTspec\nPtspec\nArea\nFailcond\nArrive\nLeave\nBorearray\nPosition\nDiagxpos\nDiagypos\nCrfarray\nScsysf\nSclore\nInprtref\nOuprtref\nScaref\nDesref\nUclone\nClnref\nSchematic Segment Element (SCSEGMENT)"}
{"Headers": "Status Link World Element (STLNKW) - Schematic", "Content": "Administrative Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\nWorld Element (WORLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\n\n\n\nWorld Element (WORLD)\nName\nDescription\nStlPos\nWorld Element (WORLD)"}
{"Headers": "Text Element (TEXT) - Schematic", "Content": "Administrative Element\nTEXT is a general element that can occupy most positions in the hierarchy. It can be used to store additional information about an owning or adjacent element.\nName\nName of the element\nPurpose\nDescription code word\nStext\nS Text string\nOrrf\nOrigin reference (for templates)\nName\nName of the element\nPurpose\nDescription code word\nStext\nS Text string\nOrrf\nOrigin reference (for templates)\nSchematic Actuator Element (SCACTUATOR)\nSchematic Area Shape Element (SCAREA)\nSchematic Branch Element (SCBRANCH)\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic HVAC Element (SCHVAC)\nSchematic Instrumentation Line Element (SCILINE)\nSchematic Instrumentation Loop Element (SCLOOP)\nSchematic Offline Instrument Element (SCOINSTRUMENT)\nSchematic Pipeline Element (SCPLINE)\nSchematic Subequipment Element (SCSUBEQUIPMENT)\nNone\nName\nName of the element\nPurpose\nDescription code word\nStext\nS Text string\nOrrf\nOrigin reference (for templates)\n\n\n\nSchematic Actuator Element (SCACTUATOR)\nSchematic Area Shape Element (SCAREA)\nSchematic Branch Element (SCBRANCH)\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic HVAC Element (SCHVAC)\nSchematic Instrumentation Line Element (SCILINE)\nSchematic Instrumentation Loop Element (SCLOOP)\nSchematic Offline Instrument Element (SCOINSTRUMENT)\nSchematic Pipeline Element (SCPLINE)\nSchematic Subequipment Element (SCSUBEQUIPMENT)\nName\nPurpose\nStext\nOrrf\nSchematic Actuator Element (SCACTUATOR)\nSchematic Area Shape Element (SCAREA)\nSchematic Branch Element (SCBRANCH)\nSchematic Equipment Element (SCEQUIPMENT)\nSchematic HVAC Element (SCHVAC)\nSchematic Instrumentation Line Element (SCILINE)\nSchematic Instrumentation Loop Element (SCLOOP)\nSchematic Offline Instrument Element (SCOINSTRUMENT)\nSchematic Pipeline Element (SCPLINE)\nSchematic Subequipment Element (SCSUBEQUIPMENT)"}
{"Headers": "World Element (WORLD) - Schematic", "Content": "Administrative Element\nPrimary Element\nThe WORLD is the topmost level of the database hierarchy within which all other elements exist. It cannot be deleted or copied in the same way that applies to say, a ZONE or a DRWG. Its existence is controlled by the ADMINISTRATION module of AVEVA E3D\u2122.\nName\nName of the element\nName\nName of the element\nNone\nDatasheet Instance World Element (DSIWLD)\nRevision Links World Element (REVLWL)\nSchematic Group Element (SCGROUP)\nStatus Link World Element (STLNKW)\nName\nName of the element\n\n\n\nDatasheet Instance World Element (DSIWLD)\nRevision Links World Element (REVLWL)\nSchematic Group Element (SCGROUP)\nStatus Link World Element (STLNKW)\nName\nDatasheet Instance World Element (DSIWLD)\nRevision Links World Element (REVLWL)\nSchematic Group Element (SCGROUP)\nStatus Link World Element (STLNKW)"}
{"Headers": "Spooler Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the Spooler database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "Spooler Database Elements", "Content": "All data in the Spooler database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Additional Items Element (AITEMS)", "Content": "Name\nName of the element\nItmtbl\nTable linking AITEMS elements to piping components\nName\nName of the element\nItmtbl\nTable linking AITEMS elements to piping components\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nNone\nName\nName of the element\nItmtbl\nTable linking AITEMS elements to piping components\n\n\n\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nName\nItmtbl\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)"}
{"Headers": "Attached Weld Element (AWELD)", "Content": "Name\nName of the element\nSpref\nComponent spec reference\nShop\nShop/Site flag\nAllowance\nAllowance\nWldprefix\nWeld number prefix\nWldnumber\nWeld number\nAwdowner\nTable linking AWELD elements to piping components\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\nName\nName of the element\nSpref\nComponent spec reference\nShop\nShop/Site flag\nAllowance\nAllowance\nWldprefix\nWeld number prefix\nWldnumber\nWeld number\nAwdowner\nTable linking AWELD elements to piping components\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\nWeld Group Element (WLDGRP)\nNone\nName\nName of the element\nSpref\nComponent spec reference\nShop\nShop/Site flag\nAllowance\nAllowance\nWldprefix\nWeld number prefix\nWldnumber\nWeld number\nAwdowner\nTable linking AWELD elements to piping components\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\n\n\n\nWeld Group Element (WLDGRP)\nName\nSpref\nShop\nAllowance\nWldprefix\nWldnumber\nAwdowner\nWldxrf\nWeld Group Element (WLDGRP)"}
{"Headers": "Field Element (FIELD)", "Content": "Name\nName of the element\nIssued\nTrue if drawing has been issued\nSpltbl\nTable linking SPOOL & FIELD elements to piping components\nOldspl\nUSED INTERNALLY TO HELP WITH UPDATE\nSplchg\nUSED INTERNALLY TO HELP WITH UPDATE\nName\nName of the element\nIssued\nTrue if drawing has been issued\nSpltbl\nTable linking SPOOL & FIELD elements to piping components\nOldspl\nUSED INTERNALLY TO HELP WITH UPDATE\nSplchg\nUSED INTERNALLY TO HELP WITH UPDATE\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nNone\nName\nName of the element\nIssued\nTrue if drawing has been issued\nSpltbl\nTable linking SPOOL & FIELD elements to piping components\nOldspl\nUSED INTERNALLY TO HELP WITH UPDATE\nSplchg\nUSED INTERNALLY TO HELP WITH UPDATE\n\n\n\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nName\nIssued\nSpltbl\nOldspl\nSplchg\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)"}
{"Headers": "Implied Joint Element (IJOINT)", "Content": "Name\nName of the element\nJntnumber\nJoint number\nJNTowners\nTable linking IJOINT elements to piping components\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\nCkey\nISODRAFT end condition key\nName\nName of the element\nJntnumber\nJoint number\nJNTowners\nTable linking IJOINT elements to piping components\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\nCkey\nISODRAFT end condition key\nJoint Group Element (JNTGRP)\nNone\nName\nName of the element\nJntnumber\nJoint number\nJNTowners\nTable linking IJOINT elements to piping components\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\nCkey\nISODRAFT end condition key\n\n\n\nJoint Group Element (JNTGRP)\nName\nJntnumber\nJNTowners\nWldxrf\nCkey\nJoint Group Element (JNTGRP)"}
{"Headers": "Isometrics Department Element (ISODEPT)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSplprefix\nSpool number prefix\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSplprefix\nSpool number prefix\nWorld Element (WORLD)\nIsometrics Registry Element (ISOREGI)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSplprefix\nSpool number prefix\n\n\n\nWorld Element (WORLD)\nIsometrics Registry Element (ISOREGI)\nName\nDescription\nFunction\nSplprefix\nWorld Element (WORLD)\nIsometrics Registry Element (ISOREGI)"}
{"Headers": "Isometrics Registry Element (ISOREGI)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSplprefix\nSpool number prefix\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSplprefix\nSpool number prefix\nIsometrics Department Element (ISODEPT)\nSpool Drawing Element (SPLDRG)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSplprefix\nSpool number prefix\n\n\n\nIsometrics Department Element (ISODEPT)\nSpool Drawing Element (SPLDRG)\nName\nDescription\nFunction\nSplprefix\nIsometrics Department Element (ISODEPT)\nSpool Drawing Element (SPLDRG)"}
{"Headers": "Implied Weld Element (IWELD)", "Content": "Name\nName of the element\nSpref\nComponent spec reference\nAllowance\nAllowance\nWldprefix\nWeld number prefix\nWldnumber\nWeld number\nIWDowners\nTable linking IWELD elements to piping components\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\nCkey\nISODRAFT end condition key\nName\nName of the element\nSpref\nComponent spec reference\nAllowance\nAllowance\nWldprefix\nWeld number prefix\nWldnumber\nWeld number\nIWDowners\nTable linking IWELD elements to piping components\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\nCkey\nISODRAFT end condition key\nWeld Group Element (WLDGRP)\nNone\nName\nName of the element\nSpref\nComponent spec reference\nAllowance\nAllowance\nWldprefix\nWeld number prefix\nWldnumber\nWeld number\nIWDowners\nTable linking IWELD elements to piping components\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\nCkey\nISODRAFT end condition key\n\n\n\nWeld Group Element (WLDGRP)\nName\nSpref\nAllowance\nWldprefix\nWldnumber\nIWDowners\nWldxrf\nCkey\nWeld Group Element (WLDGRP)"}
{"Headers": "Joint Group Element (JNTGRP)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nImplied Joint Element (IJOINT)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nImplied Joint Element (IJOINT)\nName\nDescription\nFunction\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nImplied Joint Element (IJOINT)"}
{"Headers": "Real Weld Element (RWELD)", "Content": "Name\nName of the element\nWldprefix\nWeld number prefix\nWldnumber\nWeld number\nRWDowner\nTable linking RWELD elements to design WELD elements\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\nName\nName of the element\nWldprefix\nWeld number prefix\nWldnumber\nWeld number\nRWDowner\nTable linking RWELD elements to design WELD elements\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\nWeld Group Element (WLDGRP)\nNone\nName\nName of the element\nWldprefix\nWeld number prefix\nWldnumber\nWeld number\nRWDowner\nTable linking RWELD elements to design WELD elements\nWldxrf\nUSED INTERNALLY TO HELP WITH UPDATE\n\n\n\nWeld Group Element (WLDGRP)\nName\nWldprefix\nWldnumber\nRWDowner\nWldxrf\nWeld Group Element (WLDGRP)"}
{"Headers": "Spool Drawing Element (SPLDRG)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nIssued\nTrue if drawing has been issued\nSFLimit\nSpooling limits\nSmaximum\nMaximum spool number in current spool drawing\nWmaximum\nMaximum weld number in current spool drawing\nJmaximum\nMaximum joint number in current spool drawing\nPmaximum\nMaximum part number in current spool drawing\nBmaximum\nMaximum bend number in current spool drawing\nSplprefix\nSpool number prefix\nWldprefix\nWeld number prefix\nFarea\nConstruction area\nFpline\nProcess line number\nFdrawing\nIsometric drawing number\nFrevision\nIsometric drawing revision\nFrdrawing\nReference drawings\nFstatus\nFstatus\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nIssued\nTrue if drawing has been issued\nSFLimit\nSpooling limits\nSmaximum\nMaximum spool number in current spool drawing\nWmaximum\nMaximum weld number in current spool drawing\nJmaximum\nMaximum joint number in current spool drawing\nPmaximum\nMaximum part number in current spool drawing\nBmaximum\nMaximum bend number in current spool drawing\nSplprefix\nSpool number prefix\nWldprefix\nWeld number prefix\nFarea\nConstruction area\nFpline\nProcess line number\nFdrawing\nIsometric drawing number\nFrevision\nIsometric drawing revision\nFrdrawing\nReference drawings\nFstatus\nFstatus\nIsometrics Registry Element (ISOREGI)\nAdditional Items Element (AITEMS)\nField Element (FIELD)\nJoint Group Element (JNTGRP)\nSpool Temporary Element (SPLTMP)\nSpool Element (SPOOL)\nWeld Group Element (WLDGRP)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nIssued\nTrue if drawing has been issued\nSFLimit\nSpooling limits\nSmaximum\nMaximum spool number in current spool drawing\nWmaximum\nMaximum weld number in current spool drawing\nJmaximum\nMaximum joint number in current spool drawing\nPmaximum\nMaximum part number in current spool drawing\nBmaximum\nMaximum bend number in current spool drawing\nSplprefix\nSpool number prefix\nWldprefix\nWeld number prefix\nFarea\nConstruction area\nFpline\nProcess line number\nFdrawing\nIsometric drawing number\nFrevision\nIsometric drawing revision\nFrdrawing\nReference drawings\nFstatus\nFstatus\n\n\n\nIsometrics Registry Element (ISOREGI)\nAdditional Items Element (AITEMS)\nField Element (FIELD)\nJoint Group Element (JNTGRP)\nSpool Temporary Element (SPLTMP)\nSpool Element (SPOOL)\nWeld Group Element (WLDGRP)\nName\nDescription\nFunction\nIssued\nSFLimit\nSmaximum\nWmaximum\nJmaximum\nPmaximum\nBmaximum\nSplprefix\nWldprefix\nFarea\nFpline\nFdrawing\nFrevision\nFrdrawing\nFstatus\nIsometrics Registry Element (ISOREGI)\nAdditional Items Element (AITEMS)\nField Element (FIELD)\nJoint Group Element (JNTGRP)\nSpool Temporary Element (SPLTMP)\nSpool Element (SPOOL)\nWeld Group Element (WLDGRP)"}
{"Headers": "Spool Temporary Element (SPLTMP)", "Content": "Name\nName of the element\nDspldg\nUSED INTERNALLY TO HELP WITH UPDATE\nName\nName of the element\nDspldg\nUSED INTERNALLY TO HELP WITH UPDATE\nSpool Drawing Element (SPLDRG)\nAdditional Items Element (AITEMS)\nField Element (FIELD)\nJoint Group Element (JNTGRP)\nSpool Element (SPOOL)\nWeld Group Element\nName\nName of the element\nDspldg\nUSED INTERNALLY TO HELP WITH UPDATE\n\n\n\nSpool Drawing Element (SPLDRG)\nAdditional Items Element (AITEMS)\nField Element (FIELD)\nJoint Group Element (JNTGRP)\nSpool Element (SPOOL)\nWeld Group Element\nName\nDspldg\nSpool Drawing Element (SPLDRG)\nAdditional Items Element (AITEMS)\nField Element (FIELD)\nJoint Group Element (JNTGRP)\nSpool Element (SPOOL)\nWeld Group Element"}
{"Headers": "Spool Element (SPOOL)", "Content": "Name\nName of the element\nIssued\nTrue if drawing has been issued\nSplprefix\nSpool number prefix\nSplnumber\nSpool number\nSpltbl\nTable linking SPOOL & FIELD elements to piping components\nOldspl\nUSED INTERNALLY TO HELP WITH UPDATE\nSplchg\nUSED INTERNALLY TO HELP WITH UPDATE\nName\nName of the element\nIssued\nTrue if drawing has been issued\nSplprefix\nSpool number prefix\nSplnumber\nSpool number\nSpltbl\nTable linking SPOOL & FIELD elements to piping components\nOldspl\nUSED INTERNALLY TO HELP WITH UPDATE\nSplchg\nUSED INTERNALLY TO HELP WITH UPDATE\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nNone\nName\nName of the element\nIssued\nTrue if drawing has been issued\nSplprefix\nSpool number prefix\nSplnumber\nSpool number\nSpltbl\nTable linking SPOOL & FIELD elements to piping components\nOldspl\nUSED INTERNALLY TO HELP WITH UPDATE\nSplchg\nUSED INTERNALLY TO HELP WITH UPDATE\n\n\n\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nName\nIssued\nSplprefix\nSplnumber\nSpltbl\nOldspl\nSplchg\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)"}
{"Headers": "Status Link World Element (STLNKW) - Spooler", "Content": "Administrative Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\nWorld Element (WORLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\n\n\n\nWorld Element (WORLD)\nName\nDescription\nStlPos\nWorld Element (WORLD)"}
{"Headers": "Weld Group Element (WLDGRP)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nAttached Weld Element (AWELD)\nImplied Weld Element (IWELD)\nReal Weld Element (RWELD)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nAttached Weld Element (AWELD)\nImplied Weld Element (IWELD)\nReal Weld Element (RWELD)\nName\nDescription\nFunction\nSpool Drawing Element (SPLDRG)\nSpool Temporary Element (SPLTMP)\nAttached Weld Element (AWELD)\nImplied Weld Element (IWELD)\nReal Weld Element (RWELD)"}
{"Headers": "World Element (WORLD) - Spooler", "Content": "Administrative Element\nPrimary Element\nThe WORLD is the topmost level of the database hierarchy within which all other elements exist. It cannot be deleted or copied in the same way that applies to say, a ZONE or a DRWG. Its existence is controlled by the ADMINISTRATION module.\nName\nName of the element\nName\nName of the element\nNone\nIsometrics Department Element (ISODEPT)\nStatus Link World Element (STLNKW)\nName\nName of the element\n\n\n\nIsometrics Department Element (ISODEPT)\nStatus Link World Element (STLNKW)\nName\nIsometrics Department Element (ISODEPT)\nStatus Link World Element (STLNKW)"}
{"Headers": "System Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the System database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "System Database Elements", "Content": "All data in the System database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Access Control Rights Element (ACR)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nRoleref\nAccess Control role references from ACR\nScoperef\nAccess Control scope references from ACR\nName\nName of the element\nDescription\nDescription of the element\nRoleref\nAccess Control role references from ACR\nScoperef\nAccess Control scope references from ACR\nAccess Control Rights World Element (ACRW)\nNone\nName\nName of the element\nDescription\nDescription of the element\nRoleref\nAccess Control role references from ACR\nScoperef\nAccess Control scope references from ACR\n\n\n\nAccess Control Rights World Element (ACRW)\nName\nDescription\nRoleref\nScoperef\nAccess Control Rights World Element (ACRW)"}
{"Headers": "Access Control Rights Reference Element (ACRL)", "Content": "Acrf\nACR reference attribute\nAcrf\nACR reference attribute\nAccess Control Rights Group Element (ACRST)\nNone\nAcrf\nACR reference attribute\n\n\n\nAccess Control Rights Group Element (ACRST)\nAcrf\nAccess Control Rights Group Element (ACRST)"}
{"Headers": "Access Control Rights Group Element (ACRST)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nAccess Control Rights World Element (ACRW)\nAccess Control Rights Reference Element (ACRL)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nAccess Control Rights World Element (ACRW)\nAccess Control Rights Reference Element (ACRL)\nName\nDescription\nAccess Control Rights World Element (ACRW)\nAccess Control Rights Reference Element (ACRL)"}
{"Headers": "Access Control Rights World Element (ACRW)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nAccess Control Rights Element (ACR)\nAccess Control Rights Group Element (ACRST)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nAccess Control Rights Element (ACR)\nAccess Control Rights Group Element (ACRST)\nName\nWorld Element (WORLD)\nAccess Control Rights Element (ACR)\nAccess Control Rights Group Element (ACRST)"}
{"Headers": "Baseline World Element (BASEWLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nBaseline Element (BASLIN)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nBaseline Element (BASLIN)\nName\nWorld Element (WORLD)\nBaseline Element (BASLIN)"}
{"Headers": "Baseline Element (BASLIN) - System", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\nBaseline World Element (BASEWLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\n\n\n\nBaseline World Element (BASEWLD)\nName\nDescription\nDname\nPrcode\nWRKSHR\nBaseline World Element (BASEWLD)"}
{"Headers": "Buffer Command Element (CMBU)", "Content": "Bufsize\nPreferred buffer size\nMbufsize\nPreferred buffer size in MBytes\nBufsize\nPreferred buffer size\nMbufsize\nPreferred buffer size in MBytes\nRunfile Element (RUNFILE)\nNone\nBufsize\nPreferred buffer size\nMbufsize\nPreferred buffer size in MBytes\n\n\n\nRunfile Element (RUNFILE)\nBufsize\nMbufsize\nRunfile Element (RUNFILE)"}
{"Headers": "Initial Macro for Execution Element (CMMA)", "Content": "Fname\nFilename\nFname\nFilename\nRunfile Element (RUNFILE)\nNone\nFname\nFilename\n\n\n\nRunfile Element (RUNFILE)\nFname\nRunfile Element (RUNFILE)"}
{"Headers": "Set RW Mode Command Element (CMMO)", "Content": "Tynumber\nNumber type\nModedb\nDatabase mode\nTynumber\nNumber type\nModedb\nDatabase mode\nRunfile Element (RUNFILE)\nNone\nTynumber\nNumber type\nModedb\nDatabase mode\n\n\n\nRunfile Element (RUNFILE)\nTynumber\nModedb\nRunfile Element (RUNFILE)"}
{"Headers": "Open Command Element (CMOP)", "Content": "Funit\nFUNIT\nModedb\nDatabase mode\nFname\nFilename\nFunit\nFUNIT\nModedb\nDatabase mode\nFname\nFilename\nRunfile Element (RUNFILE)\nNone\nFunit\nFUNIT\nModedb\nDatabase mode\nFname\nFilename\n\n\n\nRunfile Element (RUNFILE)\nFunit\nModedb\nFname\nRunfile Element (RUNFILE)"}
{"Headers": "Resume Command Element (CMRE)", "Content": "Fname\nFilename\nFname\nFilename\nRunfile Element (RUNFILE)\nNone\nFname\nFilename\n\n\n\nRunfile Element (RUNFILE)\nFname\nRunfile Element (RUNFILE)"}
{"Headers": "Database Element (DB) - System", "Content": "Primary Element\nNumbdb\nDB number\nStype\nSPECON type question\nFino\nFile number\nArea\nArea\nAccessdb\nDB access\nClaimdb\nImplicit or explicit claims\nDescription\nDescription of the element\nTpArea\nTemplated Project Area Name\nTpDiscipline\nTemplated Project Discipline Name\nProjid\nPROJID - on the DB element\nFcpyref\nForward copy reference\nBcpyref\nBackward copy reference\nExtNo\nExtract number\nExtOwner\nExtract owner\nLVariant\nVariant Flag\nLCtrolled\nControlled DB Flag\nName\nName of the element\nLRefOnly\nDatabase holds Reference data only flag\nLConsumer\nConsumer Extract database flag, can be refreshed when read-only\nLSvHistory\nDatabase save history from compaction flag\nNumbdb\nDB number\nStype\nSPECON type question\nFino\nFile number\nArea\nArea\nAccessdb\nDB access\nClaimdb\nImplicit or explicit claims\nDescription\nDescription of the element\nTpArea\nTemplated Project Area Name\nTpDiscipline\nTemplated Project Discipline Name\nProjid\nPROJID - on the DB element\nFcpyref\nForward copy reference\nBcpyref\nBackward copy reference\nExtNo\nExtract number\nExtOwner\nExtract owner\nLVariant\nVariant Flag\nLCtrolled\nControlled DB Flag\nName\nName of the element\nLRefOnly\nDatabase holds Reference data only flag\nLConsumer\nConsumer Extract database flag, can be refreshed when read-only\nLSvHistory\nDatabase save history from compaction flag\nDatabase List Element (DBLI)\nExtracts List Element (EXTLI)\nNone\nNumbdb\nDB number\nStype\nSPECON type question\nFino\nFile number\nArea\nArea\nAccessdb\nDB access\nClaimdb\nImplicit or explicit claims\nDescription\nDescription of the element\nTpArea\nTemplated Project Area Name\nTpDiscipline\nTemplated Project Discipline Name\nProjid\nPROJID - on the DB element\nFcpyref\nForward copy reference\nBcpyref\nBackward copy reference\nExtNo\nExtract number\nExtOwner\nExtract owner\nLVariant\nVariant Flag\nLCtrolled\nControlled DB Flag\nName\nName of the element\nLRefOnly\nDatabase holds Reference data only flag\nLConsumer\nConsumer Extract database flag, can be refreshed when read-only\nLSvHistory\nDatabase save history from compaction flag\n\n\n\nDatabase List Element (DBLI)\nExtracts List Element (EXTLI)\nNumbdb\nStype\nFino\nArea\nAccessdb\nClaimdb\nDescription\nTpArea\nTpDiscipline\nProjid\nFcpyref\nBcpyref\nExtNo\nExtOwner\nLVariant\nLCtrolled\nName\nLRefOnly\nLConsumer\nLSvHistory\nDatabase List Element (DBLI)\nExtracts List Element (EXTLI)"}
{"Headers": "Database Set Element to Reference DB Element (DBL)", "Content": "Dbf\nDatabase reference attribute\nDbf\nDatabase reference attribute\nDatabase Set Element (DBSET)\nNone\nDbf\nDatabase reference attribute\n\n\n\nDatabase Set Element (DBSET)\nDbf\nDatabase Set Element (DBSET)"}
{"Headers": "Database List Element (DBLI) - System", "Content": "Primary Element\n\n\n\nTeam Element (TEAM)\nDatabase Element (DB)\n\n\n\n\nTeam Element (TEAM)\nDatabase Element (DB)\nTeam Element (TEAM)\nDatabase Element (DB)"}
{"Headers": "DB Range Element (DBRANG) - System", "Content": "Primary Element\nName\nName of the element\nDBRBEG\nDB range start\nDBREND\nDB range end\nName\nName of the element\nDBRBEG\nDB range start\nDBREND\nDB range end\nStatus Element (STATUS)\nNone\nName\nName of the element\nDBRBEG\nDB range start\nDBREND\nDB range end\n\n\n\nStatus Element (STATUS)\nName\nDBRBEG\nDBREND\nStatus Element (STATUS)"}
{"Headers": "Database Set Element (DBSET)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nDbCriteria\nCriteria (expression) for DBs in the DBset\nDbsorder\nOrder dbs in dynamic DBSET by name, type or number\nName\nName of the element\nDescription\nDescription of the element\nDbCriteria\nCriteria (expression) for DBs in the DBset\nDbsorder\nOrder dbs in dynamic DBSET by name, type or number\nDatabase Set World Element (DBSTWL)\nDatabase Set Element to Reference DB Element (DBL)\nDatabase Set List Element (DBSTL)\nName\nName of the element\nDescription\nDescription of the element\nDbCriteria\nCriteria (expression) for DBs in the DBset\nDbsorder\nOrder dbs in dynamic DBSET by name, type or number\n\n\n\nDatabase Set World Element (DBSTWL)\nDatabase Set Element to Reference DB Element (DBL)\nDatabase Set List Element (DBSTL)\nName\nDescription\nDbCriteria\nDbsorder\nDatabase Set World Element (DBSTWL)\nDatabase Set Element to Reference DB Element (DBL)\nDatabase Set List Element (DBSTL)"}
{"Headers": "Database Set List Element (DBSTL)", "Content": "Dbstf\nDatabase set reference attribute\nDbstf\nDatabase set reference attribute\nDatabase Set Element (DBSET)\nNone\nDbstf\nDatabase set reference attribute\n\n\n\nDatabase Set Element (DBSET)\nDbstf\nDatabase Set Element (DBSET)"}
{"Headers": "Database Set World Element (DBSTWL)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nDatabase Set Element (DBSET)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nDatabase Set Element (DBSET)\nName\nWorld Element (WORLD)\nDatabase Set Element (DBSET)"}
{"Headers": "Discipline Element (DISCIPLINE)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\nPRDBSN\nStart DB Number\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\nPRDBSN\nStart DB Number\nDiscipline World Element (DISCWLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nWRKSHR\nWork Share\nPRDBSN\nStart DB Number\n\n\n\nDiscipline World Element (DISCWLD)\nName\nDescription\nDname\nPrcode\nWRKSHR\nPRDBSN\nDiscipline World Element (DISCWLD)"}
{"Headers": "Discipline World Element (DISCWLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nDiscipline Element (DISCIPLINE)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nDiscipline Element (DISCIPLINE)\nName\nWorld Element (WORLD)\nDiscipline Element (DISCIPLINE)"}
{"Headers": "Extracts List Element (EXTLI)", "Content": "\n\n\nUser Element (USER)\nDatabase Element (DB)\n\n\n\n\nUser Element (USER)\nDatabase Element (DB)\nUser Element (USER)\nDatabase Element (DB)"}
{"Headers": "Font File Details Element (FONTFILE)", "Content": "Primary Element\nIrno\nISO-IR number\nStno\nStyle number\nFnma\nStandard font file name\nFnmb\nBold font file name\nFaangle\nSkew angle for font file\nIrno\nISO-IR number\nStno\nStyle number\nFnma\nStandard font file name\nFnmb\nBold font file name\nFaangle\nSkew angle for font file\nFont World Element (FONTWORLD)\nNone\nIrno\nISO-IR number\nStno\nStyle number\nFnma\nStandard font file name\nFnmb\nBold font file name\nFaangle\nSkew angle for font file\n\n\n\nFont World Element (FONTWORLD)\nIrno\nStno\nFnma\nFnmb\nFaangle\nFont World Element (FONTWORLD)"}
{"Headers": "Font World Element (FONTWORLD)", "Content": "Primary Element\nName\nName of the element\nFntdirectory\nFont directory\nName\nName of the element\nFntdirectory\nFont directory\nStatus Element (STATUS)\nFont File Details Element (FONTFILE)\nTruetype Font File Details Element (TTFONT)\nName\nName of the element\nFntdirectory\nFont directory\n\n\n\nStatus Element (STATUS)\nFont File Details Element (FONTFILE)\nTruetype Font File Details Element (TTFONT)\nName\nFntdirectory\nStatus Element (STATUS)\nFont File Details Element (FONTFILE)\nTruetype Font File Details Element (TTFONT)"}
{"Headers": "Windows Authentication User Group Element (GLOGID)", "Content": "Primary Element\nName\nName of the element\nUsef\nUser reference\nUsrli\nValid users for given user login\nGlogNm\nWindows authentication user group name\nName\nName of the element\nUsef\nUser reference\nUsrli\nValid users for given user login\nGlogNm\nWindows authentication user group name\nUser World Element (USERWORLD)\nNone\nName\nName of the element\nUsef\nUser reference\nUsrli\nValid users for given user login\nGlogNm\nWindows authentication user group name\n\n\n\nUser World Element (USERWORLD)\nName\nUsef\nUsrli\nGlogNm\nUser World Element (USERWORLD)"}
{"Headers": "Global Location Daemon Configuration Element (LCOMC)", "Content": "Logfn\nCOMMS log file name\nLogms\nCOMMS log file active/inactive flag\nLoglv\nCOMMS log file level of detail\nLogfn\nCOMMS log file name\nLogms\nCOMMS log file active/inactive flag\nLoglv\nCOMMS log file level of detail\nGlobal Location Comms World Element (LCOMW)\nNone\nLogfn\nCOMMS log file name\nLogms\nCOMMS log file active/inactive flag\nLoglv\nCOMMS log file level of detail\n\n\n\nGlobal Location Comms World Element (LCOMW)\nLogfn\nLogms\nLoglv\nGlobal Location Comms World Element (LCOMW)"}
{"Headers": "Global Location Comms Link Details Element (LCOMD)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nLocrf\nLocation reference\nTimer\nFrequency of DB propagation\nTimeStart\nStart time of COMMS window\nTimeEnd\nEnd time of COMMS window\nTimeInterval\nCOMMS retry time interval\nTimeOutNumber\nCOMMS max retry count\nExecBefore\nExec file before DB propagation\nExecAfter\nExec file after DB propagation\nLNoUpdate\nDB propagation suppressed flag\nName\nName of the element\nDescription\nDescription of the element\nLocrf\nLocation reference\nTimer\nFrequency of DB propagation\nTimeStart\nStart time of COMMS window\nTimeEnd\nEnd time of COMMS window\nTimeInterval\nCOMMS retry time interval\nTimeOutNumber\nCOMMS max retry count\nExecBefore\nExec file before DB propagation\nExecAfter\nExec file after DB propagation\nLNoUpdate\nDB propagation suppressed flag\nGlobal Location Comms Link List Element (LCOML)\nNone\nName\nName of the element\nDescription\nDescription of the element\nLocrf\nLocation reference\nTimer\nFrequency of DB propagation\nTimeStart\nStart time of COMMS window\nTimeEnd\nEnd time of COMMS window\nTimeInterval\nCOMMS retry time interval\nTimeOutNumber\nCOMMS max retry count\nExecBefore\nExec file before DB propagation\nExecAfter\nExec file after DB propagation\nLNoUpdate\nDB propagation suppressed flag\n\n\n\nGlobal Location Comms Link List Element (LCOML)\nName\nDescription\nLocrf\nTimer\nTimeStart\nTimeEnd\nTimeInterval\nTimeOutNumber\nExecBefore\nExecAfter\nLNoUpdate\nGlobal Location Comms Link List Element (LCOML)"}
{"Headers": "Global Location Comms Link List Element (LCOML)", "Content": "\n\n\nGlobal Location Comms World Element (LCOMW)\nGlobal Location Comms Link Details Element (LCOMD)\n\n\n\n\nGlobal Location Comms World Element (LCOMW)\nGlobal Location Comms Link Details Element (LCOMD)\nGlobal Location Comms World Element (LCOMW)\nGlobal Location Comms Link Details Element (LCOMD)"}
{"Headers": "Global Location Comms World Element (LCOMW)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nGlobal Location Daemon Configuration Element (LCOMC)\nGlobal Location Comms Link List Element (LCOML)\nEvent Timer Information List Element (LCTIML)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nGlobal Location Daemon Configuration Element (LCOMC)\nGlobal Location Comms Link List Element (LCOML)\nEvent Timer Information List Element (LCTIML)\nName\nWorld Element (WORLD)\nGlobal Location Daemon Configuration Element (LCOMC)\nGlobal Location Comms Link List Element (LCOML)\nEvent Timer Information List Element (LCTIML)"}
{"Headers": "Event Timer Information Details Element (LCTIMD)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nLocrf\nLocation reference\nLEndTi\nTime out period for commands\nLMaxTry\nMaximum number of retries for command\nLTimeInterval\nTime Interval between retries\nLWaitD\nTime interval between re-sending commands\nSecSetting\nSecurity Setting for the Location connection\nName\nName of the element\nDescription\nDescription of the element\nLocrf\nLocation reference\nLEndTi\nTime out period for commands\nLMaxTry\nMaximum number of retries for command\nLTimeInterval\nTime Interval between retries\nLWaitD\nTime interval between re-sending commands\nSecSetting\nSecurity Setting for the Location connection\nEvent Timer Information List Element (LCTIML)\nNone\nName\nName of the element\nDescription\nDescription of the element\nLocrf\nLocation reference\nLEndTi\nTime out period for commands\nLMaxTry\nMaximum number of retries for command\nLTimeInterval\nTime Interval between retries\nLWaitD\nTime interval between re-sending commands\nSecSetting\nSecurity Setting for the Location connection\n\n\n\nEvent Timer Information List Element (LCTIML)\nName\nDescription\nLocrf\nLEndTi\nLMaxTry\nLTimeInterval\nLWaitD\nSecSetting\nEvent Timer Information List Element (LCTIML)"}
{"Headers": "Event Timer Information List Element (LCTIML)", "Content": "LEvenL\nTime interval for Event Loop\nLMerTimer\nFrequency of Auto Merge of Transaction DB\nLMerSuccess\nNumber of days Successful commands persist in Trans dB\nLMerFailure\nNumber of days Failed commands persist in Trans dB\nLMerDl\nEnable automatic merge of transaction db\nSecSetting\nSecurity Setting for the Location connection\nLEvenL\nTime interval for Event Loop\nLMerTimer\nFrequency of Auto Merge of Transaction DB\nLMerSuccess\nNumber of days Successful commands persist in Trans dB\nLMerFailure\nNumber of days Failed commands persist in Trans dB\nLMerDl\nEnable automatic merge of transaction db\nSecSetting\nSecurity Setting for the Location connection\nGlobal Location Comms World Element (LCOMW)\nEvent Timer Information Details Element (LCTIMD)\nLEvenL\nTime interval for Event Loop\nLMerTimer\nFrequency of Auto Merge of Transaction DB\nLMerSuccess\nNumber of days Successful commands persist in Trans dB\nLMerFailure\nNumber of days Failed commands persist in Trans dB\nLMerDl\nEnable automatic merge of transaction db\nSecSetting\nSecurity Setting for the Location connection\n\n\n\nGlobal Location Comms World Element (LCOMW)\nEvent Timer Information Details Element (LCTIMD)\nLEvenL\nLMerTimer\nLMerSuccess\nLMerFailure\nLMerDl\nSecSetting\nGlobal Location Comms World Element (LCOMW)\nEvent Timer Information Details Element (LCTIMD)"}
{"Headers": "Linestyle World Element (LINESTYLEWORLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nStatus Element (STATUS)\nLinestyle Width Definition Element (LSWIDD)\nName\nName of the element\n\n\n\nStatus Element (STATUS)\nLinestyle Width Definition Element (LSWIDD)\nName\nStatus Element (STATUS)\nLinestyle Width Definition Element (LSWIDD)"}
{"Headers": "Linestyle Width Definition Element (LSWIDD)", "Content": "Primary Element\nName\nName of the element\nLSWKey\nLine Style Width Key\nLSWidth\nLine Style Width\nName\nName of the element\nLSWKey\nLine Style Width Key\nLSWidth\nLine Style Width\nLinestyle World Element (LINESTYLEWORLD)\nNone\nName\nName of the element\nLSWKey\nLine Style Width Key\nLSWidth\nLine Style Width\n\n\n\nLinestyle World Element (LINESTYLEWORLD)\nName\nLSWKey\nLSWidth\nLinestyle World Element (LINESTYLEWORLD)"}
{"Headers": "MDB Project Definition Element (MATMDB)", "Content": "Primary Element\nName\nName of the element\nMaturf\nReference of Maturity Level Element\nDiscif\nReference of DISCIPLINE Element\nPrmdbf\nReference of MDB Element\nBaself\nReference of Baseline Element\nName\nName of the element\nMaturf\nReference of Maturity Level Element\nDiscif\nReference of DISCIPLINE Element\nPrmdbf\nReference of MDB Element\nBaself\nReference of Baseline Element\nProject Definition for MDBs Element (PRDEFMDB)\nNone\nName\nName of the element\nMaturf\nReference of Maturity Level Element\nDiscif\nReference of DISCIPLINE Element\nPrmdbf\nReference of MDB Element\nBaself\nReference of Baseline Element\n\n\n\nProject Definition for MDBs Element (PRDEFMDB)\nName\nMaturf\nDiscif\nPrmdbf\nBaself\nProject Definition for MDBs Element (PRDEFMDB)"}
{"Headers": "Maturity Level Element (MATURITY) - System", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nMatowner\nMaturity Owning Element\nDiscif\nReference of DISCIPLINE Element\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nMatowner\nMaturity Owning Element\nDiscif\nReference of DISCIPLINE Element\nMaturity-level World Element (MATUWLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDname\nDisplay Name\nPrcode\nShort code\nMatowner\nMaturity Owning Element\nDiscif\nReference of DISCIPLINE Element\n\n\n\nMaturity-level World Element (MATUWLD)\nName\nDescription\nDname\nPrcode\nMatowner\nDiscif\nMaturity-level World Element (MATUWLD)"}
{"Headers": "Maturity-level World Element (MATUWLD)", "Content": "Primary Element\nName\nName of the element\nMlvref\nReference to the Shared Maturity Level\nName\nName of the element\nMlvref\nReference to the Shared Maturity Level\nWorld Element (WORLD)\nMaturity Level Element (MATURITY)\nName\nName of the element\nMlvref\nReference to the Shared Maturity Level\n\n\n\nWorld Element (WORLD)\nMaturity Level Element (MATURITY)\nName\nMlvref\nWorld Element (WORLD)\nMaturity Level Element (MATURITY)"}
{"Headers": "Multiple Database Element (MDB)", "Content": "Primary Element\nName\nName of the element\nDbls\nList of DBs belonging to MDB\nCurdbs\nCurrent DBs\nDescription\nDescription of the element\nName\nName of the element\nDbls\nList of DBs belonging to MDB\nCurdbs\nCurrent DBs\nDescription\nDescription of the element\nMultiple Database World Element (MDBW)\nDatabase Element (DB)\nDatabase Set Element (DBSET)\nName\nName of the element\nDbls\nList of DBs belonging to MDB\nCurdbs\nCurrent DBs\nDescription\nDescription of the element\n\n\n\nMultiple Database World Element (MDBW)\nDatabase Element (DB)\nDatabase Set Element (DBSET)\nName\nDbls\nCurdbs\nDescription\nMultiple Database World Element (MDBW)\nDatabase Element (DB)\nDatabase Set Element (DBSET)"}
{"Headers": "Multiple Database World Element (MDBW)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nMultiple Database Element (MDB)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nMultiple Database Element (MDB)\nName\nWorld Element (WORLD)\nMultiple Database Element (MDB)"}
{"Headers": "Permissible Operations Element (PEROP) - System", "Content": "Name\nName of the element\nOpcreate\nCreate Access Control Operation\nOpmodify\nModify Access Control Operation\nOpdelete\nDelete Access Control Operation\nOpclaim\nClaim Access Control Operation\nOpissue\nIssue Access Control Operation\nOpdrop\nDrop Access Control Operation\nOpoutput\nOutput (DATAL) Access Control Operation\nOpexport\nExport Access Control Operation\nOpcopyfrom\nCopy-From Access Control Operation\nEclass\nAccess Control Element class\nAclass\nAccess Control Attribute class\nCondition\nAccess Control Logical condition\nAcrmessage\nAccess Control User defined message\nName\nName of the element\nOpcreate\nCreate Access Control Operation\nOpmodify\nModify Access Control Operation\nOpdelete\nDelete Access Control Operation\nOpclaim\nClaim Access Control Operation\nOpissue\nIssue Access Control Operation\nOpdrop\nDrop Access Control Operation\nOpoutput\nOutput (DATAL) Access Control Operation\nOpexport\nExport Access Control Operation\nOpcopyfrom\nCopy-From Access Control Operation\nEclass\nAccess Control Element class\nAclass\nAccess Control Attribute class\nCondition\nAccess Control Logical condition\nAcrmessage\nAccess Control User defined message\nRole Element (ROLE)\nNone\nName\nName of the element\nOpcreate\nCreate Access Control Operation\nOpmodify\nModify Access Control Operation\nOpdelete\nDelete Access Control Operation\nOpclaim\nClaim Access Control Operation\nOpissue\nIssue Access Control Operation\nOpdrop\nDrop Access Control Operation\nOpoutput\nOutput (DATAL) Access Control Operation\nOpexport\nExport Access Control Operation\nOpcopyfrom\nCopy-From Access Control Operation\nEclass\nAccess Control Element class\nAclass\nAccess Control Attribute class\nCondition\nAccess Control Logical condition\nAcrmessage\nAccess Control User defined message\n\n\n\nRole Element (ROLE)\nName\nOpcreate\nOpmodify\nOpdelete\nOpclaim\nOpissue\nOpdrop\nOpoutput\nOpexport\nOpcopyfrom\nEclass\nAclass\nCondition\nAcrmessage\nRole Element (ROLE)"}
{"Headers": "Associated Discipline Element (PRADIS) - System", "Content": "Name\nName of the element\nPdislf\nDiscipline Location Container Reference\nPconxf\nConsumer Extract Database Reference\nName\nName of the element\nPdislf\nDiscipline Location Container Reference\nPconxf\nConsumer Extract Database Reference\nProject Discipline List Element (PRDISL)\nNone\nName\nName of the element\nPdislf\nDiscipline Location Container Reference\nPconxf\nConsumer Extract Database Reference\n\n\n\nProject Discipline List Element (PRDISL)\nName\nPdislf\nPconxf\nProject Discipline List Element (PRDISL)"}
{"Headers": "Associated Baseline Element (PRBASL) - System", "Content": "Primary Element\nName\nName of the element\nLprcre\nDiscipline Created\nBaself\nReference of Baseline Element\nLocrf\nLocation reference\nName\nName of the element\nLprcre\nDiscipline Created\nBaself\nReference of Baseline Element\nLocrf\nLocation reference\nProject Definition Element (PRDEFDB)\nNone\nName\nName of the element\nLprcre\nDiscipline Created\nBaself\nReference of Baseline Element\nLocrf\nLocation reference\n\n\n\nProject Definition Element (PRDEFDB)\nName\nLprcre\nBaself\nLocrf\nProject Definition Element (PRDEFDB)"}
{"Headers": "Project Definition Element (PRDEFDB) - System", "Content": "Primary Element\nName\nName of the element\nBasname\nBase Name for the Project Definition\nDescription\nDescription of the element\nMaturf\nReference of Maturity Level Element\nTmsdif\nTMS Discipline\nName\nName of the element\nBasname\nBase Name for the Project Definition\nDescription\nDescription of the element\nMaturf\nReference of Maturity Level Element\nTmsdif\nTMS Discipline\nProject Definition World Element (PRDEWL)\nAssociated Baseline Element (PRBASL)\nProject Discipline List Element (PRDISL)\nName\nName of the element\nBasname\nBase Name for the Project Definition\nDescription\nDescription of the element\nMaturf\nReference of Maturity Level Element\nTmsdif\nTMS Discipline\n\n\n\nProject Definition World Element (PRDEWL)\nAssociated Baseline Element (PRBASL)\nProject Discipline List Element (PRDISL)\nName\nBasname\nDescription\nMaturf\nTmsdif\nProject Definition World Element (PRDEWL)\nAssociated Baseline Element (PRBASL)\nProject Discipline List Element (PRDISL)"}
{"Headers": "Project Definition for MDBs Element (PRDEFMDB)", "Content": "Primary Element\nName\nName of the element\nPrgldf\nReference to Project Definition element\nDbstf\nDatabase set reference attribute\nName\nName of the element\nPrgldf\nReference to Project Definition element\nDbstf\nDatabase set reference attribute\nProject Definition World for MDBs Element (SPRDEWORLD)\nMDB Project Definition Element (MATMDB)\nName\nName of the element\nPrgldf\nReference to Project Definition element\nDbstf\nDatabase set reference attribute\n\n\n\nProject Definition World for MDBs Element (SPRDEWORLD)\nMDB Project Definition Element (MATMDB)\nName\nPrgldf\nDbstf\nProject Definition World for MDBs Element (SPRDEWORLD)\nMDB Project Definition Element (MATMDB)"}
{"Headers": "Project Definition World Element (PRDEWL)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nProject Definition Element (PRDEFDB)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nProject Definition Element (PRDEFDB)\nName\nWorld Element (WORLD)\nProject Definition Element (PRDEFDB)"}
{"Headers": "Project Discipline List Element (PRDISL) - System", "Content": "Primary Element\nName\nName of the element\nDiscif\nReference of DISCIPLINE Element\nLocrf\nLocation reference\nLprcre\nDiscipline Created\nPrddbf\nReference to the Master DB\nName\nName of the element\nDiscif\nReference of DISCIPLINE Element\nLocrf\nLocation reference\nLprcre\nDiscipline Created\nPrddbf\nReference to the Master DB\nProject Definition Element (PRDEFDB)\nAssociated Discipline Element (PRADIS)\nName\nName of the element\nDiscif\nReference of DISCIPLINE Element\nLocrf\nLocation reference\nLprcre\nDiscipline Created\nPrddbf\nReference to the Master DB\n\n\n\nProject Definition Element (PRDEFDB)\nAssociated Discipline Element (PRADIS)\nName\nDiscif\nLocrf\nLprcre\nPrddbf\nProject Definition Element (PRDEFDB)\nAssociated Discipline Element (PRADIS)"}
{"Headers": "Runfile World Element (RFWL)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nStatus Element (STATUS)\nRunfile Element (RUNFILE)\nName\nName of the element\n\n\n\nStatus Element (STATUS)\nRunfile Element (RUNFILE)\nName\nStatus Element (STATUS)\nRunfile Element (RUNFILE)"}
{"Headers": "Role Element (ROLE) - System", "Content": "Name\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nRole World Element (ROLWL)\nPermissible Operations Element (PEROP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nRole World Element (ROLWL)\nPermissible Operations Element (PEROP)\nName\nDescription\nRole World Element (ROLWL)\nPermissible Operations Element (PEROP)"}
{"Headers": "Role World Element (ROLWL)", "Content": "Primary Element\nName\nName of the element\nLACR\nAccess Control on/off switch\nName\nName of the element\nLACR\nAccess Control on/off switch\nWorld Element (WORLD)\nRole Element (ROLE)\nName\nName of the element\nLACR\nAccess Control on/off switch\n\n\n\nWorld Element (WORLD)\nRole Element (ROLE)\nName\nLACR\nWorld Element (WORLD)\nRole Element (ROLE)"}
{"Headers": "Runfile Element (RUNFILE)", "Content": "Primary Element\nAttributes\nName\nName of the element\nSmno\nSMODU number\nSecurity\nUser security\nName\nName of the element\nSmno\nSMODU number\nSecurity\nUser security\nRunfile World Element (RFWL)\nBuffer Command Element (CMBU)\nInitial Macro for Execution Element (CMMA)\nSet RW Mode Command Element (CMMO)\nOpen Command Element (CMOP)\nResume Command Element (CMRE)\nName\nName of the element\nSmno\nSMODU number\nSecurity\nUser security\n\n\n\nRunfile World Element (RFWL)\nBuffer Command Element (CMBU)\nInitial Macro for Execution Element (CMMA)\nSet RW Mode Command Element (CMMO)\nOpen Command Element (CMOP)\nResume Command Element (CMRE)\nName\nSmno\nSecurity\nRunfile World Element (RFWL)\nBuffer Command Element (CMBU)\nInitial Macro for Execution Element (CMMA)\nSet RW Mode Command Element (CMMO)\nOpen Command Element (CMOP)\nResume Command Element (CMRE)"}
{"Headers": "Scope Element (SCOPE)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nScosel\nAccess Control scope\nName\nName of the element\nDescription\nDescription of the element\nScosel\nAccess Control scope\nScope World Element (SCOWL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nScosel\nAccess Control scope\n\n\n\nScope World Element (SCOWL)\nName\nDescription\nScosel\nScope World Element (SCOWL)"}
{"Headers": "Scope World Element (SCOWL)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nScope Element (SCOPE)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nScope Element (SCOPE)\nName\nWorld Element (WORLD)\nScope Element (SCOPE)"}
{"Headers": "Project Definition World for MDBs Element (SPRDEWORLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nProject Definition for MDBs Element (PRDEFMDB)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nProject Definition for MDBs Element (PRDEFMDB)\nName\nWorld Element (WORLD)\nProject Definition for MDBs Element (PRDEFMDB)"}
{"Headers": "Stamp Element (STAMP) - System", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nSetDate\nSet Date\nSETUTC\nSet UTC Date\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nSetDate\nSet Date\nSETUTC\nSet UTC Date\nStamp World Element (STWLD)\nStamp List Element (STLST)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nPurpose\nDescription code word\nSetDate\nSet Date\nSETUTC\nSet UTC Date\n\n\n\nStamp World Element (STWLD)\nStamp List Element (STLST)\nName\nDescription\nFunction\nPurpose\nSetDate\nSETUTC\nStamp World Element (STWLD)\nStamp List Element (STLST)"}
{"Headers": "Status Element (STATUS)", "Content": "Primary Element\nName\nName of the element\nPrjnumber\nProject number\nMaxusers\nMaximum number of user\nPrjlock\nProject lock\nPrjdesc\nProject description\nInfa\nClient info - Project Name\nInfb\nComment - Project Message\nCharset\nCharacter set\nLocrf\nLocation reference\nPrjstatus\nAccess Control project status\nAduuid\nUUID to ensure Project uniqueness\nUTCSWT\nTrue if System outputs UTC based Session Date Times\nConnectserviceID\nConnect service ID of the uploaded project in cloud\nName\nName of the element\nPrjnumber\nProject number\nMaxusers\nMaximum number of user\nPrjlock\nProject lock\nPrjdesc\nProject description\nInfa\nClient info - Project Name\nInfb\nComment - Project Message\nCharset\nCharacter set\nLocrf\nLocation reference\nPrjstatus\nAccess Control project status\nAduuid\nUUID to ensure Project uniqueness\nUTCSWT\nTrue if System outputs UTC based Session Date Times\nConnectserviceID\nConnect service ID of the uploaded project in cloud\nWorld Element (WORLD)\nDB Range Element (DBRANG)\nFont World Element (FONTWORLD)\nLinestyle World Element (LINESTYLEWORLD)\nRunfile World Element (RFWL)\nName\nName of the element\nPrjnumber\nProject number\nMaxusers\nMaximum number of user\nPrjlock\nProject lock\nPrjdesc\nProject description\nInfa\nClient info - Project Name\nInfb\nComment - Project Message\nCharset\nCharacter set\nLocrf\nLocation reference\nPrjstatus\nAccess Control project status\nAduuid\nUUID to ensure Project uniqueness\nUTCSWT\nTrue if System outputs UTC based Session Date Times\nConnectserviceID\nConnect service ID of the uploaded project in cloud\n\n\n\nWorld Element (WORLD)\nDB Range Element (DBRANG)\nFont World Element (FONTWORLD)\nLinestyle World Element (LINESTYLEWORLD)\nRunfile World Element (RFWL)\nName\nPrjnumber\nMaxusers\nPrjlock\nPrjdesc\nInfa\nInfb\nCharset\nLocrf\nPrjstatus\nAduuid\nUTCSWT\nConnectserviceID\nWorld Element (WORLD)\nDB Range Element (DBRANG)\nFont World Element (FONTWORLD)\nLinestyle World Element (LINESTYLEWORLD)\nRunfile World Element (RFWL)"}
{"Headers": "Stamp List Element (STLST) - System", "Content": "Name\nName of the element\nStlsf\nDatabase reference\nStsess\nDatabase session number\nName\nName of the element\nStlsf\nDatabase reference\nStsess\nDatabase session number\nStamp Element (STAMP)\nNone\nName\nName of the element\nStlsf\nDatabase reference\nStsess\nDatabase session number\n\n\n\nStamp Element (STAMP)\nName\nStlsf\nStsess\nStamp Element (STAMP)"}
{"Headers": "Stamp World Element (STWLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nStamp Element (STAMP)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nStamp Element (STAMP)\nName\nWorld Element (WORLD)\nStamp Element (STAMP)"}
{"Headers": "Team Element (TEAM) - System", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nTeamStatus\nAccess Control team status\nDiscis\nAssociated disciplines\nName\nName of the element\nDescription\nDescription of the element\nTeamStatus\nAccess Control team status\nDiscis\nAssociated disciplines\nTeam World Element (TEAMWORLD)\nDatabase List Element (DBLI)\nName\nName of the element\nDescription\nDescription of the element\nTeamStatus\nAccess Control team status\nDiscis\nAssociated disciplines\n\n\n\nTeam World Element (TEAMWORLD)\nDatabase List Element (DBLI)\nName\nDescription\nTeamStatus\nDiscis\nTeam World Element (TEAMWORLD)\nDatabase List Element (DBLI)"}
{"Headers": "Team World Element (TEAMWORLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nTeam Element (TEAM)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nTeam Element (TEAM)\nName\nWorld Element (WORLD)\nTeam Element (TEAM)"}
{"Headers": "Team List Element (TMLI)", "Content": "\n\n\nUser Element (USER)\nNone\n\n\n\n\nUser Element (USER)\nUser Element (USER)"}
{"Headers": "Truetype Font File Details Element (TTFONT)", "Content": "Primary Element\nTTFindex\nTrueType font index\nTTfacename\nTrueType font face name\nTTFdescription\nTrueType font description\nTTFindex\nTrueType font index\nTTfacename\nTrueType font face name\nTTFdescription\nTrueType font description\nFont World Element (FONTWORLD)\nNone\nTTFindex\nTrueType font index\nTTfacename\nTrueType font face name\nTTFdescription\nTrueType font description\n\n\n\nFont World Element (FONTWORLD)\nTTFindex\nTTfacename\nTTFdescription\nFont World Element (FONTWORLD)"}
{"Headers": "User Login ID Element (ULOGID)", "Content": "Primary Element\nName\nName of the element\nUsef\nUser reference\nUsrli\nValid users for given user login\nName\nName of the element\nUsef\nUser reference\nUsrli\nValid users for given user login\nUser World Element (USERWORLD)\nNone\nName\nName of the element\nUsef\nUser reference\nUsrli\nValid users for given user login\n\n\n\nUser World Element (USERWORLD)\nName\nUsef\nUsrli\nUser World Element (USERWORLD)"}
{"Headers": "User Element (USER)", "Content": "Primary Element\nPassword\nPassword\nSecurity\nUser security\nName\nName of the element\nDescription\nDescription of the element\nAcrli\nAccess Control User assigned ACRs\nUsrmdb\nMDBs that a user may select from. If unset, then there is no restriction.\nUMDBRe\nWhen \u2018true\u2019 restricts the user to selecting from those MDBs defined in USRMDB\nUalias\nAlias of the standard user\nPassword\nPassword\nSecurity\nUser security\nName\nName of the element\nDescription\nDescription of the element\nAcrli\nAccess Control User assigned ACRs\nUsrmdb\nMDBs that a user may select from. If unset, then there is no restriction.\nUMDBRe\nWhen \u2018true\u2019 restricts the user to selecting from those MDBs defined in USRMDB\nUalias\nAlias of the standard user\nUser World Element (USERWORLD)\nExtracts List Element (EXTLI)\nTeam List Element (TMLI)\nPassword\nPassword\nSecurity\nUser security\nName\nName of the element\nDescription\nDescription of the element\nAcrli\nAccess Control User assigned ACRs\nUsrmdb\nMDBs that a user may select from. If unset, then there is no restriction.\nUMDBRe\nWhen \u2018true\u2019 restricts the user to selecting from those MDBs defined in USRMDB\nUalias\nAlias of the standard user\n\n\n\nUser World Element (USERWORLD)\nExtracts List Element (EXTLI)\nTeam List Element (TMLI)\nPassword\nSecurity\nName\nDescription\nAcrli\nUsrmdb\nUMDBRe\nUalias\nUser World Element (USERWORLD)\nExtracts List Element (EXTLI)\nTeam List Element (TMLI)"}
{"Headers": "User World Element (USERWORLD)", "Content": "Primary Element\nName\nName of the element\nLauthu\nLogin Authentication on/off switch\nLckPsw\nLock passwords for general users\nName\nName of the element\nLauthu\nLogin Authentication on/off switch\nLckPsw\nLock passwords for general users\nWorld Element (WORLD)\nWindows Authentication User Group Element (GLOGID)\nUser Login ID Element (ULOGID)\nUser Element (USER)\nName\nName of the element\nLauthu\nLogin Authentication on/off switch\nLckPsw\nLock passwords for general users\n\n\n\nWorld Element (WORLD)\nWindows Authentication User Group Element (GLOGID)\nUser Login ID Element (ULOGID)\nUser Element (USER)\nName\nLauthu\nLckPsw\nWorld Element (WORLD)\nWindows Authentication User Group Element (GLOGID)\nUser Login ID Element (ULOGID)\nUser Element (USER)"}
{"Headers": "World Element (WORLD) - System", "Content": "Administrative Element\nPrimary Element\nThe WORLD is the topmost level of the database hierarchy within which all other elements exist. It cannot be deleted or copied in the same way that applies to say, a ZONE or a DRWG. Its existence is controlled by the ADMINISTRATION module.\nName\nName of the element\nName\nName of the element\nNone\nAccess Control Rights World Element (ACRW)\nBaseline World Element (BASEWLD)\nDatabase Set World Element (DBSTWL)\nDiscipline World Element (DISCWLD)\nGlobal Location Comms World Element (LCOMW)\nMaturity-level World Element (MATUWLD)\nMultiple Database World Element (MDBW)\nProject Definition World Element (PRDEWL)\nRole World Element (ROLWL)\nScope World Element (SCOWL)\nProject Definition World for MDBs Element (SPRDEWORLD)\nStatus Element (STATUS)\nStamp World Element (STWLD)\nTeam World Element (TEAMWORLD)\nUser World Element (USERWORLD)\nName\nName of the element\n\n\n\nAccess Control Rights World Element (ACRW)\nBaseline World Element (BASEWLD)\nDatabase Set World Element (DBSTWL)\nDiscipline World Element (DISCWLD)\nGlobal Location Comms World Element (LCOMW)\nMaturity-level World Element (MATUWLD)\nMultiple Database World Element (MDBW)\nProject Definition World Element (PRDEWL)\nRole World Element (ROLWL)\nScope World Element (SCOWL)\nProject Definition World for MDBs Element (SPRDEWORLD)\nStatus Element (STATUS)\nStamp World Element (STWLD)\nTeam World Element (TEAMWORLD)\nUser World Element (USERWORLD)\nName\nAccess Control Rights World Element (ACRW)\nBaseline World Element (BASEWLD)\nDatabase Set World Element (DBSTWL)\nDiscipline World Element (DISCWLD)\nGlobal Location Comms World Element (LCOMW)\nMaturity-level World Element (MATUWLD)\nMultiple Database World Element (MDBW)\nProject Definition World Element (PRDEWL)\nRole World Element (ROLWL)\nScope World Element (SCOWL)\nProject Definition World for MDBs Element (SPRDEWORLD)\nStatus Element (STATUS)\nStamp World Element (STWLD)\nTeam World Element (TEAMWORLD)\nUser World Element (USERWORLD)"}
{"Headers": "Transaction Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the Transaction database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "Transaction Database Elements", "Content": "All data in the transaction database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Transaction Day Element (TRDAY)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nTransaction Month Element (TRMONTH)\nTransaction User Element (TRUSER)\nName\nName of the element\n\n\n\nTransaction Month Element (TRMONTH)\nTransaction User Element (TRUSER)\nName\nTransaction Month Element (TRMONTH)\nTransaction User Element (TRUSER)"}
{"Headers": "Transaction Failure Element (TRFAILURE)", "Content": "Primary Element\nMesNumber\nMessage Number\nMsText\nMessage text\nDateMs\nDate message created\nCommType\nCommand Type\nOpType\nOperation Type\nMsType\nReference of TROUCO/TROPER creating this POSTOP\nMesReference\nMessage data reference\nMesQualifier\nMessage Qualifier Number\nMsDTxt\nMessage Data text\nMsLocation\nLocation Origin of Message\nMesNumber\nMessage Number\nMsText\nMessage text\nDateMs\nDate message created\nCommType\nCommand Type\nOpType\nOperation Type\nMsType\nReference of TROUCO/TROPER creating this POSTOP\nMesReference\nMessage data reference\nMesQualifier\nMessage Qualifier Number\nMsDTxt\nMessage Data text\nMsLocation\nLocation Origin of Message\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)\nNone\nMesNumber\nMessage Number\nMsText\nMessage text\nDateMs\nDate message created\nCommType\nCommand Type\nOpType\nOperation Type\nMsType\nReference of TROUCO/TROPER creating this POSTOP\nMesReference\nMessage data reference\nMesQualifier\nMessage Qualifier Number\nMsDTxt\nMessage Data text\nMsLocation\nLocation Origin of Message\n\n\n\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)\nMesNumber\nMsText\nDateMs\nCommType\nOpType\nMsType\nMesReference\nMesQualifier\nMsDTxt\nMsLocation\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)"}
{"Headers": "Transaction Failure List Element (TRFLST)", "Content": "Primary Element\n\n\n\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Failure Element (TRFAILURE)\n\n\n\n\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Failure Element (TRFAILURE)\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Failure Element (TRFAILURE)"}
{"Headers": "Transaction Input Command Element (TRINCOMMAND)", "Content": "Primary Element\nName\nName of the element\nOriLocation\nOriginal Location\nDesLocation\nDestination Location for the command\nPrvLocation\nPrevious Location of Command\nCommType\nCommand Type\nTrDbRf\nDB for transaction\nTrFino\nTran. File number\nTrExtNo\nExtract number\nTrArea\nArea\nTrStype\nDatabase type\nTrDbNo\nDB number\nAuxLocation\nPrevious Location of Command\nExTime\nTime of Execution for Command\nSysLocation\nSystem Location for Remote Access\nTrCarguments\nArgument Qualifiers\nInArCount\nNumber of integers in Argument list\nIntArguments\nArguments for command\nTrDaccess\nDatabase access\nComuid\nTROUCO Reference at relevant Site\nDepcount\nNumber of dependencies\nDepend\nCommands on which this is dependent\nDeptype\nCommands on which this is dependent\nIncState\nInput Command Status\nDateCreated\nDate command Created\nDateAk\nDate command Acknowledged\nNAcknowledged\nNo. of times Acknowledged\nDateRd\nDate command ready\nDateCm\nDate command Completed\nDateRp\nDate command Replied\nNReply\nNo. of times Replied\nTrPassed\nSuccessful Result Flag\nMsText\nMessage text\nDatEnded\nDate command Stopped\nNRepAk\nNo. of times Reply Acknowledged\nTrVisi\nWhether the command is visible\nDescription\nDescription of the element\nUserStopped\nUser who cancelled command\nComString\nUser Command String\nTrModu\nModule\nTrLocl\nLocal command or not\nName\nName of the element\nOriLocation\nOriginal Location\nDesLocation\nDestination Location for the command\nPrvLocation\nPrevious Location of Command\nCommType\nCommand Type\nTrDbRf\nDB for transaction\nTrFino\nTran. File number\nTrExtNo\nExtract number\nTrArea\nArea\nTrStype\nDatabase type\nTrDbNo\nDB number\nAuxLocation\nPrevious Location of Command\nExTime\nTime of Execution for Command\nSysLocation\nSystem Location for Remote Access\nTrCarguments\nArgument Qualifiers\nInArCount\nNumber of integers in Argument list\nIntArguments\nArguments for command\nTrDaccess\nDatabase access\nComuid\nTROUCO Reference at relevant Site\nDepcount\nNumber of dependencies\nDepend\nCommands on which this is dependent\nDeptype\nCommands on which this is dependent\nIncState\nInput Command Status\nDateCreated\nDate command Created\nDateAk\nDate command Acknowledged\nNAcknowledged\nNo. of times Acknowledged\nDateRd\nDate command ready\nDateCm\nDate command Completed\nDateRp\nDate command Replied\nNReply\nNo. of times Replied\nTrPassed\nSuccessful Result Flag\nMsText\nMessage text\nDatEnded\nDate command Stopped\nNRepAk\nNo. of times Reply Acknowledged\nTrVisi\nWhether the command is visible\nDescription\nDescription of the element\nUserStopped\nUser who cancelled command\nComString\nUser Command String\nTrModu\nModule\nTrLocl\nLocal command or not\nTransaction Location Element (TRLOCATION)\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Success List Element (TRSLST)\nName\nName of the element\nOriLocation\nOriginal Location\nDesLocation\nDestination Location for the command\nPrvLocation\nPrevious Location of Command\nCommType\nCommand Type\nTrDbRf\nDB for transaction\nTrFino\nTran. File number\nTrExtNo\nExtract number\nTrArea\nArea\nTrStype\nDatabase type\nTrDbNo\nDB number\nAuxLocation\nPrevious Location of Command\nExTime\nTime of Execution for Command\nSysLocation\nSystem Location for Remote Access\nTrCarguments\nArgument Qualifiers\nInArCount\nNumber of integers in Argument list\nIntArguments\nArguments for command\nTrDaccess\nDatabase access\nComuid\nTROUCO Reference at relevant Site\nDepcount\nNumber of dependencies\nDepend\nCommands on which this is dependent\nDeptype\nCommands on which this is dependent\nIncState\nInput Command Status\nDateCreated\nDate command Created\nDateAk\nDate command Acknowledged\nNAcknowledged\nNo. of times Acknowledged\nDateRd\nDate command ready\nDateCm\nDate command Completed\nDateRp\nDate command Replied\nNReply\nNo. of times Replied\nTrPassed\nSuccessful Result Flag\nMsText\nMessage text\nDatEnded\nDate command Stopped\nNRepAk\nNo. of times Reply Acknowledged\nTrVisi\nWhether the command is visible\nDescription\nDescription of the element\nUserStopped\nUser who cancelled command\nComString\nUser Command String\nTrModu\nModule\nTrLocl\nLocal command or not\n\n\n\nTransaction Location Element (TRLOCATION)\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Success List Element (TRSLST)\nName\nOriLocation\nDesLocation\nPrvLocation\nCommType\nTrDbRf\nTrFino\nTrExtNo\nTrArea\nTrStype\nTrDbNo\nAuxLocation\nExTime\nSysLocation\nTrCarguments\nInArCount\nIntArguments\nTrDaccess\nComuid\nDepcount\nDepend\nDeptype\nIncState\nDateCreated\nDateAk\nNAcknowledged\nDateRd\nDateCm\nDateRp\nNReply\nTrPassed\nMsText\nDatEnded\nNRepAk\nTrVisi\nDescription\nUserStopped\nComString\nTrModu\nTrLocl\nTransaction Location Element (TRLOCATION)\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Success List Element (TRSLST)"}
{"Headers": "Transaction Location Element (TRLOCATION)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nTransaction User Element (TRUSER)\nTransaction Input Command Element (TRINCOMMAND)\nName\nName of the element\n\n\n\nTransaction User Element (TRUSER)\nTransaction Input Command Element (TRINCOMMAND)\nName\nTransaction User Element (TRUSER)\nTransaction Input Command Element (TRINCOMMAND)"}
{"Headers": "Transaction Message Element (TRMESSAGE)", "Content": "Primary Element\nMesNumber\nMessage Number\nMsText\nMessage text\nDateMs\nDate message created\nCommType\nCommand Type\nOpType\nOperation Type\nMsLocation\nLocation Origin of Message\nMsSent\nMessage Sent to relevant site\nMesNumber\nMessage Number\nMsText\nMessage text\nDateMs\nDate message created\nCommType\nCommand Type\nOpType\nOperation Type\nMsLocation\nLocation Origin of Message\nMsSent\nMessage Sent to relevant site\nTransaction Message List Element (TRMLST)\nNone\nMesNumber\nMessage Number\nMsText\nMessage text\nDateMs\nDate message created\nCommType\nCommand Type\nOpType\nOperation Type\nMsLocation\nLocation Origin of Message\nMsSent\nMessage Sent to relevant site\n\n\n\nTransaction Message List Element (TRMLST)\nMesNumber\nMsText\nDateMs\nCommType\nOpType\nMsLocation\nMsSent\nTransaction Message List Element (TRMLST)"}
{"Headers": "Transaction Message List Element (TRMLST)", "Content": "Primary Element\n\n\n\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Failure Element (TRFAILURE)\nTransaction Message Element (TRMESSAGE)\nTransaction Success Element (TRSUCCESS)\n\n\n\n\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Failure Element (TRFAILURE)\nTransaction Message Element (TRMESSAGE)\nTransaction Success Element (TRSUCCESS)\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Failure Element (TRFAILURE)\nTransaction Message Element (TRMESSAGE)\nTransaction Success Element (TRSUCCESS)"}
{"Headers": "Transaction Month Element (TRMONTH)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nTransaction Year Element (TRYEAR)\nTransaction Day Element (TRDAY)\nName\nName of the element\n\n\n\nTransaction Year Element (TRYEAR)\nTransaction Day Element (TRDAY)\nName\nTransaction Year Element (TRYEAR)\nTransaction Day Element (TRDAY)"}
{"Headers": "Transaction Message World Element (TRMSGW)", "Content": "Primary Element\nName\nName of the element\nTrsetl\nLocal commands are to be stored\nName\nName of the element\nTrsetl\nLocal commands are to be stored\nWorld Element (WORLD)\nTransaction Year Element (TRYEAR)\nName\nName of the element\nTrsetl\nLocal commands are to be stored\n\n\n\nWorld Element (WORLD)\nTransaction Year Element (TRYEAR)\nName\nTrsetl\nWorld Element (WORLD)\nTransaction Year Element (TRYEAR)"}
{"Headers": "Transaction Operations Element (TROPERATION)", "Content": "Primary Element\nName\nName of the element\nOpType\nOperation Type\nOpState\nOperation Status\nDateCreated\nDate command Created\nDateRd\nDate command ready\nDateRn\nDate command running\nDateSl\nDate command last Stalled\nNRetry\nNumber of Retries\nMaxTry\nMaximum Number of Retries\nEndTimeTrying\nDate command Stopped\nWaitime\nTime interval between Retries\nDateCm\nDate command Completed\nTrPassed\nSuccessful Result Flag\nMsText\nMessage text\nDatEnded\nDate command Stopped\nUserStopped\nUser who cancelled command\nDepcount\nNumber of dependencies\nDepend\nCommands on which this is dependent\nDeptype\nCommands on which this is dependent\nPreOperation\nReference of TROUCO/TROPER creating this POSTOP\nPOpCode\nPost Operation Code\nName\nName of the element\nOpType\nOperation Type\nOpState\nOperation Status\nDateCreated\nDate command Created\nDateRd\nDate command ready\nDateRn\nDate command running\nDateSl\nDate command last Stalled\nNRetry\nNumber of Retries\nMaxTry\nMaximum Number of Retries\nEndTimeTrying\nDate command Stopped\nWaitime\nTime interval between Retries\nDateCm\nDate command Completed\nTrPassed\nSuccessful Result Flag\nMsText\nMessage text\nDatEnded\nDate command Stopped\nUserStopped\nUser who cancelled command\nDepcount\nNumber of dependencies\nDepend\nCommands on which this is dependent\nDeptype\nCommands on which this is dependent\nPreOperation\nReference of TROUCO/TROPER creating this POSTOP\nPOpCode\nPost Operation Code\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)\nTransaction Success List Element (TRSLST)\nName\nName of the element\nOpType\nOperation Type\nOpState\nOperation Status\nDateCreated\nDate command Created\nDateRd\nDate command ready\nDateRn\nDate command running\nDateSl\nDate command last Stalled\nNRetry\nNumber of Retries\nMaxTry\nMaximum Number of Retries\nEndTimeTrying\nDate command Stopped\nWaitime\nTime interval between Retries\nDateCm\nDate command Completed\nTrPassed\nSuccessful Result Flag\nMsText\nMessage text\nDatEnded\nDate command Stopped\nUserStopped\nUser who cancelled command\nDepcount\nNumber of dependencies\nDepend\nCommands on which this is dependent\nDeptype\nCommands on which this is dependent\nPreOperation\nReference of TROUCO/TROPER creating this POSTOP\nPOpCode\nPost Operation Code\n\n\n\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)\nTransaction Success List Element (TRSLST)\nName\nOpType\nOpState\nDateCreated\nDateRd\nDateRn\nDateSl\nNRetry\nMaxTry\nEndTimeTrying\nWaitime\nDateCm\nTrPassed\nMsText\nDatEnded\nUserStopped\nDepcount\nDepend\nDeptype\nPreOperation\nPOpCode\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)\nTransaction Success List Element (TRSLST)"}
{"Headers": "Transaction Foreign Command Element (TROUCOMMAND)", "Content": "Primary Element\nName\nName of the element\nOriLocation\nOriginal Location\nDesLocation\nDestination Location for the command\nPrvLocation\nPrevious Location of Command\nCommType\nCommand Type\nTrDbRf\nDB for transaction\nTrFino\nTran. File number\nTrExtNo\nExtract number\nTrArea\nArea\nTrStype\nDatabase type\nTrDbNo\nDB number\nAuxLocation\nPrevious Location of Command\nExTime\nTime of Execution for Command\nSysLocation\nSystem Location for Remote Access\nTrCarguments\nArgument Qualifiers\nInArCount\nNumber of integers in Argument list\nIntArguments\nArguments for command\nTrDaccess\nDatabase access\nDepcount\nNumber of dependencies\nDepend\nCommands on which this is dependent\nDeptype\nCommands on which this is dependent\nOutState\nOutput Command Status\nNxTarLocation\nNext Target Location for the command\nDateCreated\nDate command Created\nDateRd\nDate command ready\nDateSnt\nDate command Sent\nNRetry\nNumber of Retries\nMaxTry\nMaximum Number of Retries\nEndTimeTrying\nDate command Stopped\nWaitime\nTime interval between Retries\nDateAk\nDate command Acknowledged\nNAcknowledged\nNo. of times Acknowledged\nCmReference\nReference of TRINCO element at relevant site\nDateRp\nDate command Replied\nNReply\nNo. of times Replied\nTrPassed\nSuccessful Result Flag\nMsText\nMessage text\nDateRk\nDate command Reply Acknowledged\nNRepAk\nNo. of times Reply Acknowledged\nDatEnded\nDate command Stopped\nUserStopped\nUser who cancelled command\nPreOperation\nReference of TROUCO/TROPER creating this POSTOP\nPOpCode\nPost Operation Code\nName\nName of the element\nOriLocation\nOriginal Location\nDesLocation\nDestination Location for the command\nPrvLocation\nPrevious Location of Command\nCommType\nCommand Type\nTrDbRf\nDB for transaction\nTrFino\nTran. File number\nTrExtNo\nExtract number\nTrArea\nArea\nTrStype\nDatabase type\nTrDbNo\nDB number\nAuxLocation\nPrevious Location of Command\nExTime\nTime of Execution for Command\nSysLocation\nSystem Location for Remote Access\nTrCarguments\nArgument Qualifiers\nInArCount\nNumber of integers in Argument list\nIntArguments\nArguments for command\nTrDaccess\nDatabase access\nDepcount\nNumber of dependencies\nDepend\nCommands on which this is dependent\nDeptype\nCommands on which this is dependent\nOutState\nOutput Command Status\nNxTarLocation\nNext Target Location for the command\nDateCreated\nDate command Created\nDateRd\nDate command ready\nDateSnt\nDate command Sent\nNRetry\nNumber of Retries\nMaxTry\nMaximum Number of Retries\nEndTimeTrying\nDate command Stopped\nWaitime\nTime interval between Retries\nDateAk\nDate command Acknowledged\nNAcknowledged\nNo. of times Acknowledged\nCmReference\nReference of TRINCO element at relevant site\nDateRp\nDate command Replied\nNReply\nNo. of times Replied\nTrPassed\nSuccessful Result Flag\nMsText\nMessage text\nDateRk\nDate command Reply Acknowledged\nNRepAk\nNo. of times Reply Acknowledged\nDatEnded\nDate command Stopped\nUserStopped\nUser who cancelled command\nPreOperation\nReference of TROUCO/TROPER creating this POSTOP\nPOpCode\nPost Operation Code\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)\nTransaction Success List Element (TRSLST)\nName\nName of the element\nOriLocation\nOriginal Location\nDesLocation\nDestination Location for the command\nPrvLocation\nPrevious Location of Command\nCommType\nCommand Type\nTrDbRf\nDB for transaction\nTrFino\nTran. File number\nTrExtNo\nExtract number\nTrArea\nArea\nTrStype\nDatabase type\nTrDbNo\nDB number\nAuxLocation\nPrevious Location of Command\nExTime\nTime of Execution for Command\nSysLocation\nSystem Location for Remote Access\nTrCarguments\nArgument Qualifiers\nInArCount\nNumber of integers in Argument list\nIntArguments\nArguments for command\nTrDaccess\nDatabase access\nDepcount\nNumber of dependencies\nDepend\nCommands on which this is dependent\nDeptype\nCommands on which this is dependent\nOutState\nOutput Command Status\nNxTarLocation\nNext Target Location for the command\nDateCreated\nDate command Created\nDateRd\nDate command ready\nDateSnt\nDate command Sent\nNRetry\nNumber of Retries\nMaxTry\nMaximum Number of Retries\nEndTimeTrying\nDate command Stopped\nWaitime\nTime interval between Retries\nDateAk\nDate command Acknowledged\nNAcknowledged\nNo. of times Acknowledged\nCmReference\nReference of TRINCO element at relevant site\nDateRp\nDate command Replied\nNReply\nNo. of times Replied\nTrPassed\nSuccessful Result Flag\nMsText\nMessage text\nDateRk\nDate command Reply Acknowledged\nNRepAk\nNo. of times Reply Acknowledged\nDatEnded\nDate command Stopped\nUserStopped\nUser who cancelled command\nPreOperation\nReference of TROUCO/TROPER creating this POSTOP\nPOpCode\nPost Operation Code\n\n\n\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)\nTransaction Success List Element (TRSLST)\nName\nOriLocation\nDesLocation\nPrvLocation\nCommType\nTrDbRf\nTrFino\nTrExtNo\nTrArea\nTrStype\nTrDbNo\nAuxLocation\nExTime\nSysLocation\nTrCarguments\nInArCount\nIntArguments\nTrDaccess\nDepcount\nDepend\nDeptype\nOutState\nNxTarLocation\nDateCreated\nDateRd\nDateSnt\nNRetry\nMaxTry\nEndTimeTrying\nWaitime\nDateAk\nNAcknowledged\nCmReference\nDateRp\nNReply\nTrPassed\nMsText\nDateRk\nNRepAk\nDatEnded\nUserStopped\nPreOperation\nPOpCode\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Failure List Element (TRFLST)\nTransaction Message List Element (TRMLST)\nTransaction Success List Element (TRSLST)"}
{"Headers": "Transaction Success List Element (TRSLST)", "Content": "Primary Element\n\n\n\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Success Element (TRSUCCESS)\n\n\n\n\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Success Element (TRSUCCESS)\nTransaction Input Command Element (TRINCOMMAND)\nTransaction Operations Element (TROPERATION)\nTransaction Foreign Command Element (TROUCOMMAND)\nTransaction Success Element (TRSUCCESS)"}
{"Headers": "Transaction Success Element (TRSUCCESS)", "Content": "Primary Element\nMesNumber\nMessage Number\nMsText\nMessage text\nDateMs\nDate message created\nCommType\nCommand Type\nOpType\nOperation Type\nMsType\nReference of TROUCO/TROPER creating this POSTOP\nMesReference\nMessage data reference\nMesQualifier\nMessage Qualifier Number\nMsDTxt\nMessage Data text\nMsLocation\nLocation Origin of Message\nMesNumber\nMessage Number\nMsText\nMessage text\nDateMs\nDate message created\nCommType\nCommand Type\nOpType\nOperation Type\nMsType\nReference of TROUCO/TROPER creating this POSTOP\nMesReference\nMessage data reference\nMesQualifier\nMessage Qualifier Number\nMsDTxt\nMessage Data text\nMsLocation\nLocation Origin of Message\nTransaction Message List Element (TRMLST)\nTransaction Success List Element (TRSLST)\nNone\nMesNumber\nMessage Number\nMsText\nMessage text\nDateMs\nDate message created\nCommType\nCommand Type\nOpType\nOperation Type\nMsType\nReference of TROUCO/TROPER creating this POSTOP\nMesReference\nMessage data reference\nMesQualifier\nMessage Qualifier Number\nMsDTxt\nMessage Data text\nMsLocation\nLocation Origin of Message\n\n\n\nTransaction Message List Element (TRMLST)\nTransaction Success List Element (TRSLST)\nMesNumber\nMsText\nDateMs\nCommType\nOpType\nMsType\nMesReference\nMesQualifier\nMsDTxt\nMsLocation\nTransaction Message List Element (TRMLST)\nTransaction Success List Element (TRSLST)"}
{"Headers": "Transaction User Element (TRUSER)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nTransaction Day Element (TRDAY)\nTransaction Location Element (TRLOCATION)\nName\nName of the element\n\n\n\nTransaction Day Element (TRDAY)\nTransaction Location Element (TRLOCATION)\nName\nTransaction Day Element (TRDAY)\nTransaction Location Element (TRLOCATION)"}
{"Headers": "Transaction Year Element (TRYEAR)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nTransaction Message World Element (TRMSGW)\nTransaction Month Element (TRMONTH)\nName\nName of the element\n\n\n\nTransaction Message World Element (TRMSGW)\nTransaction Month Element (TRMONTH)\nName\nTransaction Message World Element (TRMSGW)\nTransaction Month Element (TRMONTH)"}
{"Headers": "World Element (WORLD) - Transaction", "Content": "Administrative Element\nPrimary Element\nThe WORLD is the topmost level of the database hierarchy within which all other elements exist. It cannot be deleted or copied in the same way that applies to say, a ZONE or a DRWG. Its existence is controlled by the ADMINISTRATION module.\nName\nName of the element\nName\nName of the element\nNone\nTransaction Message World Element (TRMSGW)\nName\nName of the element\n\n\n\nTransaction Message World Element (TRMSGW)\nName\nTransaction Message World Element (TRMSGW)"}
{"Headers": "Configuration Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the Configuration database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "Configuration Database Elements", "Content": "All data in the Configuration database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Config Set Element (CFGSET)", "Content": "102 Element\nPrimary Element\nName\nName of the element\nDname\nDisplay Name\nDescription\nDescription of the element\nPrecedence\nPrecedence\nName\nName of the element\nDname\nDisplay Name\nDescription\nDescription of the element\nPrecedence\nPrecedence\nConfig Set Element (CFGSET)\nConfig Set World Element (CFGSTW)\nConfig Set Element (CFGSET)\nConfig Value Instance Element (CFGVAL)\nName\nName of the element\nDname\nDisplay Name\nDescription\nDescription of the element\nPrecedence\nPrecedence\n\n\n\nConfig Set Element (CFGSET)\nConfig Set World Element (CFGSTW)\nConfig Set Element (CFGSET)\nConfig Value Instance Element (CFGVAL)\nName\nDname\nDescription\nPrecedence\nConfig Set Element (CFGSET)\nConfig Set World Element (CFGSTW)\nConfig Set Element (CFGSET)\nConfig Value Instance Element (CFGVAL)"}
{"Headers": "Config Set World Element (CFGSTW)", "Content": "102 Element\nPrimary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WRLD)\nConfig Set Element (CFGSET)\nName\nName of the element\n\n\n\nWorld Element (WRLD)\nConfig Set Element (CFGSET)\nName\nWorld Element (WRLD)\nConfig Set Element (CFGSET)"}
{"Headers": "Config Value Instance Element (CFGVAL)", "Content": "102 Element\nPrimary Element\nCfgOvride\nConfiguration Override Flag\nCfgTValue\nConfiguration text value\nCfgLValue\nConfiguration logical value\nCfgLAValue\nConfiguration logical array value\nCfgIValue\nConfiguration integer value\nCfgIAValue\nConfiguration integer array value\nCfgRValue\nConfiguration real value\nCfgRAValue\nConfiguration real array value\nCfgTAValue\nConfiguration text array value\nCfgKReference\nConfiguration key reference\nCfgOvride\nConfiguration Override Flag\nCfgTValue\nConfiguration text value\nCfgLValue\nConfiguration logical value\nCfgLAValue\nConfiguration logical array value\nCfgIValue\nConfiguration integer value\nCfgIAValue\nConfiguration integer array value\nCfgRValue\nConfiguration real value\nCfgRAValue\nConfiguration real array value\nCfgTAValue\nConfiguration text array value\nCfgKReference\nConfiguration key reference\nConfig Set Element (CFGSET)\nNone\nCfgOvride\nConfiguration Override Flag\nCfgTValue\nConfiguration text value\nCfgLValue\nConfiguration logical value\nCfgLAValue\nConfiguration logical array value\nCfgIValue\nConfiguration integer value\nCfgIAValue\nConfiguration integer array value\nCfgRValue\nConfiguration real value\nCfgRAValue\nConfiguration real array value\nCfgTAValue\nConfiguration text array value\nCfgKReference\nConfiguration key reference\n\n\n\nConfig Set Element (CFGSET)\nCfgOvride\nCfgTValue\nCfgLValue\nCfgLAValue\nCfgIValue\nCfgIAValue\nCfgRValue\nCfgRAValue\nCfgTAValue\nCfgKReference\nConfig Set Element (CFGSET)"}
{"Headers": "World Element (WORLD) - Configuration", "Content": "Administrative Element\nPrimary Element\nName\nName of the element\nName\nName of the element\nNone\nConfig Set World Element (CFGSTW)\nName\nName of the element\n\n\n\nConfig Set World Element (CFGSTW)\nName\nConfig Set World Element (CFGSTW)"}
{"Headers": "Attribute Category: Accommodation", "Content": "ACCDIR\ndir\n\nAccess Direction\nACCELE\nreal(500)\n\nElevations of Referenced Levels\nALIST\nelement(500)\n\n\nBNDARE\nreal\n\nBoundary line area\nCELLTO\nreal\n\nTotal Number of Cell\nCELLTR\nreal\n\nTotal Number of Trimmed Cells\nCELLWH\nreal\n\nTotal Number of Untrimmed Cells\nCLNELE\nreal\n\nCeiling Elevation\nEDGELE\nreal\n\nEdge Length\nFLCARE\nreal\n\nFloor cover area\nFLCSTHICKNESS\nreal\n\nFloor cover thickness\nFLCVOL\nreal\n\nFloor cover volume\nFLLARE\nreal\n\nFloor layer area\nFLLVOL\nreal\n\nFloor layer volume\nFLRELE\nreal\n\nFloor Elevation\nFLRELV\nreal\n\nFloor elevation\nFLTDIR\ndir\n\nStairflight Direction\nGAREA\nreal\n\nCeiling Grid Area\nHNODEL\nelement(500)\n\nHnode list\nINSARE\nreal\n\nInsulation requirement area\nLABPOS\npos\n\nLabel position\nLGOING\nreal(10)\n\nLower Tread Going\nLWP\npos\n\nLower Working Point\nMATDIR\ndir\n\nMaterial direction\nPITCH\nreal(10)\n\nPitch of stair flight\nPRMDIR\ndir\n\nPrimary Direction\nSLHNAP\nelement(500)\n\nSorted list of HNODE after POINTR\nSLHNBP\nelement(500)\n\nSorted list of HNODE before POINTR\nTRIMCE\ninteger(10000)\n\nArray of Trimmed Cells\nTRIMTY\nword\n\nCTWALL TRIM TYPE\nUGOING\nreal(10)\n\nUpper Tread Going\nURISE\nreal(10)\n\nUpper Tread Rise\nUWP\npos\n\nUpper Working Point\nWHOLEC\nreal\n\nArray of Whole Cells\nWJUSL\nword\n\nWall Justification Line\n\nAttribute Name\nData Type\nQualifier\nDescription\nACCDIR\ndir\nAccess Direction\nACCELE\nreal(500)\nElevations of Referenced Levels\nALIST\nelement(500)\nBNDARE\nreal\nBoundary line area\nCELLTO\nreal\nTotal Number of Cell\nCELLTR\nreal\nTotal Number of Trimmed Cells\nCELLWH\nreal\nTotal Number of Untrimmed Cells\nCLNELE\nreal\nCeiling Elevation\nEDGELE\nreal\nEdge Length\nFLCARE\nreal\nFloor cover area\nFLCSTHICKNESS\nreal\nFloor cover thickness\nFLCVOL\nreal\nFloor cover volume\nFLLARE\nreal\nFloor layer area\nFLLVOL\nreal\nFloor layer volume\nFLRELE\nreal\nFloor Elevation\nFLRELV\nreal\nFloor elevation\nFLTDIR\ndir\nStairflight Direction\nGAREA\nreal\nCeiling Grid Area\nHNODEL\nelement(500)\nHnode list\nINSARE\nreal\nInsulation requirement area\nLABPOS\npos\nLabel position\nLGOING\nreal(10)\nLower Tread Going\nLWP\npos\nLower Working Point\nMATDIR\ndir\nMaterial direction\nPITCH\nreal(10)\nPitch of stair flight\nPRMDIR\ndir\nPrimary Direction\nSLHNAP\nelement(500)\nSorted list of HNODE after POINTR\nSLHNBP\nelement(500)\nSorted list of HNODE before POINTR\nTRIMCE\ninteger(10000)\nArray of Trimmed Cells\nTRIMTY\nword\nCTWALL TRIM TYPE\nUGOING\nreal(10)\nUpper Tread Going\nURISE\nreal(10)\nUpper Tread Rise\nUWP\npos\nUpper Working Point\nWHOLEC\nreal\nArray of Whole Cells\nWJUSL\nword\nWall Justification Line\n\n\n"}
{"Headers": "Attribute Category: Admin DB", "Content": "ACRGRP\nelement(5000)\n\nList of ACRs within a ACRSET\nCURRFULL\nelement(5000)\n\nList of current DBs in MDB, expanding DBsets\nDBLS\nelement(5000)\n\nList of DBs belonging to MDB\nDBLSFULL\nelement(5000)\n\nList of DBs belonging to MDB, expanding DBsets\nDBPRODUCTAVAILABLE\nstringarray(50)\nword\nProducts available for databases\nDBSETLS\nelement(5000)\n\nList of DbSets in MDB\nDBSHIE\nelement(5000)\n\nDatabase hierarchy within a DBSET\nDBSLEV\nelement(5000)\n\nDatabases at a level within a DBSET\nDBSLIS\nelement(5000)\n\nDatabases within a DBSET\nDBSSTP\nelement(8000)\n\nDBs in a stamp\nDEFERD\nelement(10000)\n\nDeferred DBs in MDB\nLVAR\nlogical\n\nVariant Flag\nPRJID\nstring(17)\n\nProject id. Available on STAT or GSTAT element\nPROJIDTEXT\nstring(100)\nword\nProject id\nSTMPLS\nelement(10000)\n\nList of STAMPs related to an MDB\nTEAMLS\nelement(1000)\n\nList of TEAMs to which USER belongs\nUSERLS\nelement(2000)\n\nList of USERs belonging to TEAM\n\nAttribute Name\nData Type\nQualifier\nDescription\nACRGRP\nelement(5000)\nList of ACRs within a ACRSET\nCURRFULL\nelement(5000)\nList of current DBs in MDB, expanding DBsets\nDBLS\nelement(5000)\nList of DBs belonging to MDB\nDBLSFULL\nelement(5000)\nList of DBs belonging to MDB, expanding DBsets\nDBPRODUCTAVAILABLE\nstringarray(50)\nword\nProducts available for databases\nDBSETLS\nelement(5000)\nList of DbSets in MDB\nDBSHIE\nelement(5000)\nDatabase hierarchy within a DBSET\nDBSLEV\nelement(5000)\nDatabases at a level within a DBSET\nDBSLIS\nelement(5000)\nDatabases within a DBSET\nDBSSTP\nelement(8000)\nDBs in a stamp\nDEFERD\nelement(10000)\nDeferred DBs in MDB\nLVAR\nlogical\nVariant Flag\nPRJID\nstring(17)\nProject id. Available on STAT or GSTAT element\nPROJIDTEXT\nstring(100)\nword\nProject id\nSTMPLS\nelement(10000)\nList of STAMPs related to an MDB\nTEAMLS\nelement(1000)\nList of TEAMs to which USER belongs\nUSERLS\nelement(2000)\nList of USERs belonging to TEAM\n\n\n"}
{"Headers": "Attribute Category: Admin DB, Database Element", "Content": "ACCESSDB\nstring(10)\n\nDB access\nAREAEX\nlogical\n\nTrue if area exists for DB\nCLAIMDB\nstring(10)\n\nImplicit or explicit claims\nCLCCNT\ninteger\n\nClaim list changes count\nCOPYDB\nelement(8191)\n\nCopies of this database\nCSESS\nstring(640)\ninteger\nComment entered for specified session\nDACC\nstring\n\nDatabase access\nDBHASPRODUCT\nlogical\n\nHas a product been associated with this DB?\nDBLC\nelement(1000)\n\nList of LOCs belonging to a DB\nDBPRODUCTTEXT\nstring(1024)\n\nProduct associated with this DB\nDBPRODUCTWRITE\nlogical\nword\nFlag determining whether product can write to DB\nDBUsers\nelement(10000)\n\nCurrent Users in the system using this DB\nDBUSRX\nelement(10000)\n\nCurrent Users in the system using this DB or any extract descendants\nDCLA\nstring\n\nDatabase claim mode\nDSESS\nstring(640)\ninteger\nDate of specified session\nENCODB\nstring\n\nDB Encoding\nEXPIRY\nstring(50)\n\nProtected DB Expiry date\nEXTALS\nelement(8191)\n\nExtract ancestors\nEXTCLS\nelement(8191)\n\nExtract children\nEXTDES\nelement(8191)\n\nExtract descendants\nEXTFAM\nelement(8191)\n\nExtract family\nEXTMAS\nelement\n\nExtract master\nFILEEX\nlogical\n\nTrue if DB file exists and is valid\nFILENAME\nstring\n\nDB filename\nFOREIGN\nstring\n\nDB foreign/local\nHCCNT\ninteger\n\nHeader/Extract list changes count\nISCOPY\nlogical\n\nTrue if a copy DB\nISDBFR\nlogical\n\nTrue if database is foreign\nISDBPR\nlogical\n\nTrue if database is primary for global working\nISDRDB\nlogical\n\nTrue if database has drawings\nISEXTR\nlogical\n\nTrue if an extract\nISFOR\nlogical\n\nTrue if database is foreign\nISLNKD\nlogical\n\nTrue if database may have Linked documents\nISMAST\nlogical\n\nTrue if a Master DB, i.e. top level extract\nISUPGD\nlogical\n\nTrue if Upgrade is required for DB\nISWORK\nlogical\n\nTrue if a working extract\nLINKSN\ninteger\n\nLinked session on parent extract\nLPASS\nlogical\n\nDB Password Flag\nLPROT\nlogical\n\nProtected DB Flag\nMDBCLS\nelement(1000)\n\nList of MDBs in which DB is current\nMDBLS\nelement(1000)\n\nList of MDBs to which DB belongs\nNACCNT\ninteger\n\nNon-additive changes count\nNAMEDB\nstring\n\nDB name\nNSESS\ninteger\n\nNumber of extant sessions\nNXTDBN\ninteger\n\nNext DB number\nNXTDBU\ninteger\n\nNext Unique DB number\nNXTEXN\ninteger\n\nNext DB extract number\nNXTFDB\ninteger\n\nNext DB file and DB number\nNXTFLN\ninteger\n\nNext DB file number\nOKUPGD\nlogical\n\nTrue if a Master DB that can be upgraded here\nPSESS\ninteger\ninteger\nPrevious session number\nRSESS\nstring(640)\ninteger\nReason for creation of session\nSIZEDB\ninteger\n\nSize of DB\nSTPDAT\nstring\n\nCalculated or Persisted Stamp Date\nSTPDBS\nelement(5000)\n\nStamps containing db\nSTPSES\ninteger(5000)\n\nSessions used in at least one stamp\nSTYPDB\nstring\n\nDB sub type\nTSESS\nstring(640)\ninteger\nIdentifier of Transaction containing session\nTYPEDB\nstring(6)\n\nDB type\nUPGDDB\ninteger\n\nUpgrade number for DB\nUSESS\nstring(640)\ninteger\nUser creating session\nUTCSES\nlogical\ninteger\nTrue if the session date is a calculated local date\nUTCSTP\nlogical\n\nTrue if the stamp date is a calculated local date\n\nAttribute Name\nData Type\nQualifier\nDescription\nACCESSDB\nstring(10)\nDB access\nAREAEX\nlogical\nTrue if area exists for DB\nCLAIMDB\nstring(10)\nImplicit or explicit claims\nCLCCNT\ninteger\nClaim list changes count\nCOPYDB\nelement(8191)\nCopies of this database\nCSESS\nstring(640)\ninteger\nComment entered for specified session\nDACC\nstring\nDatabase access\nDBHASPRODUCT\nlogical\nHas a product been associated with this DB?\nDBLC\nelement(1000)\nList of LOCs belonging to a DB\nDBPRODUCTTEXT\nstring(1024)\nProduct associated with this DB\nDBPRODUCTWRITE\nlogical\nword\nFlag determining whether product can write to DB\nDBUsers\nelement(10000)\nCurrent Users in the system using this DB\nDBUSRX\nelement(10000)\nCurrent Users in the system using this DB or any extract descendants\nDCLA\nstring\nDatabase claim mode\nDSESS\nstring(640)\ninteger\nDate of specified session\nENCODB\nstring\nDB Encoding\nEXPIRY\nstring(50)\nProtected DB Expiry date\nEXTALS\nelement(8191)\nExtract ancestors\nEXTCLS\nelement(8191)\nExtract children\nEXTDES\nelement(8191)\nExtract descendants\nEXTFAM\nelement(8191)\nExtract family\nEXTMAS\nelement\nExtract master\nFILEEX\nlogical\nTrue if DB file exists and is valid\nFILENAME\nstring\nDB filename\nFOREIGN\nstring\nDB foreign/local\nHCCNT\ninteger\nHeader/Extract list changes count\nISCOPY\nlogical\nTrue if a copy DB\nISDBFR\nlogical\nTrue if database is foreign\nISDBPR\nlogical\nTrue if database is primary for global working\nISDRDB\nlogical\nTrue if database has drawings\nISEXTR\nlogical\nTrue if an extract\nISFOR\nlogical\nTrue if database is foreign\nISLNKD\nlogical\nTrue if database may have Linked documents\nISMAST\nlogical\nTrue if a Master DB, i.e. top level extract\nISUPGD\nlogical\nTrue if Upgrade is required for DB\nISWORK\nlogical\nTrue if a working extract\nLINKSN\ninteger\nLinked session on parent extract\nLPASS\nlogical\nDB Password Flag\nLPROT\nlogical\nProtected DB Flag\nMDBCLS\nelement(1000)\nList of MDBs in which DB is current\nMDBLS\nelement(1000)\nList of MDBs to which DB belongs\nNACCNT\ninteger\nNon-additive changes count\nNAMEDB\nstring\nDB name\nNSESS\ninteger\nNumber of extant sessions\nNXTDBN\ninteger\nNext DB number\nNXTDBU\ninteger\nNext Unique DB number\nNXTEXN\ninteger\nNext DB extract number\nNXTFDB\ninteger\nNext DB file and DB number\nNXTFLN\ninteger\nNext DB file number\nOKUPGD\nlogical\nTrue if a Master DB that can be upgraded here\nPSESS\ninteger\ninteger\nPrevious session number\nRSESS\nstring(640)\ninteger\nReason for creation of session\nSIZEDB\ninteger\nSize of DB\nSTPDAT\nstring\nCalculated or Persisted Stamp Date\nSTPDBS\nelement(5000)\nStamps containing db\nSTPSES\ninteger(5000)\nSessions used in at least one stamp\nSTYPDB\nstring\nDB sub type\nTSESS\nstring(640)\ninteger\nIdentifier of Transaction containing session\nTYPEDB\nstring(6)\nDB type\nUPGDDB\ninteger\nUpgrade number for DB\nUSESS\nstring(640)\ninteger\nUser creating session\nUTCSES\nlogical\ninteger\nTrue if the session date is a calculated local date\nUTCSTP\nlogical\nTrue if the stamp date is a calculated local date\n\n\n"}
{"Headers": "Attribute Category: Admin DB, Database Elements", "Content": "SCOSLX\ninteger(500)\n\nAccess Control scope\n\nAttribute Name\nData Type\nQualifier\nDescription\nSCOSLX\ninteger(500)\nAccess Control scope\n\n\n"}
{"Headers": "Attribute Category: Admin DB, Interdisciplinary Project element", "Content": "LPRDEL\nlogical\n\nInterdisciplinary Project Element is deletable Flag\nLPRMOD\nlogical\n\nInterdisciplinary Project Element is modifiable Flag\n\nAttribute Name\nData Type\nQualifier\nDescription\nLPRDEL\nlogical\nInterdisciplinary Project Element is deletable Flag\nLPRMOD\nlogical\nInterdisciplinary Project Element is modifiable Flag\n\n\n"}
{"Headers": "Attribute Category: Admin DB, TMS Project element", "Content": "TMSPRJ\nlogical\n\nFlag to notify if this is a TMS Project\n\nAttribute Name\nData Type\nQualifier\nDescription\nTMSPRJ\nlogical\nFlag to notify if this is a TMS Project\n\n\n"}
{"Headers": "Attribute Category: Allowed Operation", "Content": "DACCLA\nlogical\n\nTrue if DAC allows element to be claimed\nDACCOH\nlogical\n\nTrue if DAC allows element hierarchy to be copied to another DB\nDACCOP\nlogical\n\nTrue if DAC allows element to be copied to another DB\nDACCRE\nlogical\nelemtype\nTrue if DAC allows element to be created\nDACDEL\nlogical\n\nTrue if DAC allows element to be deleted\nDACDRO\nlogical\n\nTrue if DAC allows element to be dropped\nDACERR\nstring(120)\nattr\nReturns the DAC error\nDACEXH\nlogical\n\nTrue if DAC allows element hierarchy to be exported\nDACEXP\nlogical\n\nTrue if DAC allows element to be exported\nDACISS\nlogical\n\nTrue if DAC allows element to be issued\nDACMOD\nlogical\nattr\nTrue if DAC allows attribute of element to be modified\nDACOUH\nlogical\n\nTrue if DAC allows element hierarchy to be output\nDACOUT\nlogical\n\nTrue if DAC allows element to be output\nMODATT\nlogical\nattr\nTrue if attribute of element can be modified\nMODDEL\nlogical\nattr\nTrue if element can be deleted\nMODERR\nstring(240)\nattr\nReturns the error text that would occur if attribute was modified\nOKDRPH\nelement(5000)\n\nPrimary elements preventing hierarchy drop\nOKRLEH\nelement(5000)\n\nPrimary elements preventing hierarchy release\n\nAttribute Name\nData Type\nQualifier\nDescription\nDACCLA\nlogical\nTrue if DAC allows element to be claimed\nDACCOH\nlogical\nTrue if DAC allows element hierarchy to be copied to another DB\nDACCOP\nlogical\nTrue if DAC allows element to be copied to another DB\nDACCRE\nlogical\nelemtype\nTrue if DAC allows element to be created\nDACDEL\nlogical\nTrue if DAC allows element to be deleted\nDACDRO\nlogical\nTrue if DAC allows element to be dropped\nDACERR\nstring(120)\nattr\nReturns the DAC error\nDACEXH\nlogical\nTrue if DAC allows element hierarchy to be exported\nDACEXP\nlogical\nTrue if DAC allows element to be exported\nDACISS\nlogical\nTrue if DAC allows element to be issued\nDACMOD\nlogical\nattr\nTrue if DAC allows attribute of element to be modified\nDACOUH\nlogical\nTrue if DAC allows element hierarchy to be output\nDACOUT\nlogical\nTrue if DAC allows element to be output\nMODATT\nlogical\nattr\nTrue if attribute of element can be modified\nMODDEL\nlogical\nattr\nTrue if element can be deleted\nMODERR\nstring(240)\nattr\nReturns the error text that would occur if attribute was modified\nOKDRPH\nelement(5000)\nPrimary elements preventing hierarchy drop\nOKRLEH\nelement(5000)\nPrimary elements preventing hierarchy release\n\n\n"}
{"Headers": "Attribute Category: Assembly Related", "Content": "ASIOWN\nelement(500)\n\nAssembly item referring to element\nASMBLB\nlogical\n\nTrue if element is possible to assemble\nASMBLD\nlogical\n\nTrue if element is assembled\nASMBLS\nstring\n\nA for assembled elements, NA for not assembled elements\nASMOWN\nelement(500)\n\nAssembly referring to element\nASNORM\ndir\n\nAssembly normal\nASORIS\nstring(20)\n\nPredefined assembly orientation string\nASSEQ\ninteger\n\nAssembly sequence\nASVDIR\ndir\n\nAssembly view direction\n\nAttribute Name\nData Type\nQualifier\nDescription\nASIOWN\nelement(500)\nAssembly item referring to element\nASMBLB\nlogical\nTrue if element is possible to assemble\nASMBLD\nlogical\nTrue if element is assembled\nASMBLS\nstring\nA for assembled elements, NA for not assembled elements\nASMOWN\nelement(500)\nAssembly referring to element\nASNORM\ndir\nAssembly normal\nASORIS\nstring(20)\nPredefined assembly orientation string\nASSEQ\ninteger\nAssembly sequence\nASVDIR\ndir\nAssembly view direction\n\n\n"}
{"Headers": "Attribute Category: Association Related", "Content": "AOBJS\nelement(500)\n\nReference Array of all Model currently participating in ASSOCs\nASMBS\nelement(500)\n\nReference Array of all association members using element\nASSCIA\nelement(500)\n\nReference Array of all associate elements used with constraints\nASSDFS\nelement(500)\n\nReference Array of all ASSDEFs\nASSOS\nelement(500)\n\nReference Array of all associations with constraints\nASTMBS\nelement(500)\n\nReference Array of all association members targeting element\nDASSCI\nelement(500)\n\nReference Array of all direct associates with constraints\nDASSOS\nelement(500)\n\nReference Array of all associations with constraints\nDIREV\ndir\n\nDirection evaluation\nLOGEV\nlogical\n\nLogical value evaluation\nPOSEV\npos\n\nPosition evaluation\nREALEV\nreal\n\nReal evaluation\nSTREV\nstring(120)\n\nString value evaluation\nTESTEV\nlogical\n\nResult of constraint test evaluation\n\nAttribute Name\nData Type\nQualifier\nDescription\nAOBJS\nelement(500)\nReference Array of all Model currently participating in ASSOCs\nASMBS\nelement(500)\nReference Array of all association members using element\nASSCIA\nelement(500)\nReference Array of all associate elements used with constraints\nASSDFS\nelement(500)\nReference Array of all ASSDEFs\nASSOS\nelement(500)\nReference Array of all associations with constraints\nASTMBS\nelement(500)\nReference Array of all association members targeting element\nDASSCI\nelement(500)\nReference Array of all direct associates with constraints\nDASSOS\nelement(500)\nReference Array of all associations with constraints\nDIREV\ndir\nDirection evaluation\nLOGEV\nlogical\nLogical value evaluation\nPOSEV\npos\nPosition evaluation\nREALEV\nreal\nReal evaluation\nSTREV\nstring(120)\nString value evaluation\nTESTEV\nlogical\nResult of constraint test evaluation\n\n\n"}
{"Headers": "Attribute Category: Attribute Related", "Content": "ATTDST\nword(2000)\n\nList the distributed attributes, default gives all udas\nATTLIST\nword(2000)\n\nList of all attributes for element\nATTOUT\nword(2000)\n\nList of all attributes excluding hidden ones, i.e as output in \"Q ATT\"\nATTRAW\nword(2000)\n\nList of raw attributes\nCASELIST\nstringarray(100)\nattr\nList of cases set for a UDA\nINHSRC\nelement\nattr\nInherited source att\nINVREF\nlogical\nattr\nT/F on attributes that are invalid references\nNULLRE\nlogical\nattr\nT/F on attributes that are null value references\nPRDLS\nword(2000)\n\nList of all design properties\nPROUT\nword(2000)\n\nList of all properties excluding hidden ones, i.e as output in \"Q ATT\"\nPRREF\nelement\n\nDataset reference\nPSATTS\nword(500)\n\nList of pseudo attributes\nRLIS\nword(200)\n\nList of rules set\nUDALIS\nword(2000)\n\nList of UDAs\nUDASET\nword(2000)\n\nList of UDAs set\nUNRESO\nlogical\nattr\nT/F on attributes that are unresolved references\n\nAttribute Name\nData Type\nQualifier\nDescription\nATTDST\nword(2000)\nList the distributed attributes, default gives all udas\nATTLIST\nword(2000)\nList of all attributes for element\nATTOUT\nword(2000)\nList of all attributes excluding hidden ones, i.e as output in \"Q ATT\"\nATTRAW\nword(2000)\nList of raw attributes\nCASELIST\nstringarray(100)\nattr\nList of cases set for a UDA\nINHSRC\nelement\nattr\nInherited source att\nINVREF\nlogical\nattr\nT/F on attributes that are invalid references\nNULLRE\nlogical\nattr\nT/F on attributes that are null value references\nPRDLS\nword(2000)\nList of all design properties\nPROUT\nword(2000)\nList of all properties excluding hidden ones, i.e as output in \"Q ATT\"\nPRREF\nelement\nDataset reference\nPSATTS\nword(500)\nList of pseudo attributes\nRLIS\nword(200)\nList of rules set\nUDALIS\nword(2000)\nList of UDAs\nUDASET\nword(2000)\nList of UDAs set\nUNRESO\nlogical\nattr\nT/F on attributes that are unresolved references\n\n\n"}
{"Headers": "Attribute Category: AutoCAD Related", "Content": "ACBTEX\nstring(500)\n\nAutoCAD annotation text\nACBTYP\nstring(180)\n\nAutoCAD annotation type\nACDMTX\nstring(500)\n\nAutoCAD dimension text\nACDTYP\nstring(180)\n\nAutoCAD dimension type\nACPLTX\nstring(500)\n\nAutoCAD projection line text\nACPTYP\nstring(180)\n\nAutoCAD projection line type\nDWGF\nstring(73)\n\nDWG filename (No suffix)\nODWGF\nstring(73)\n\nOpen DWG filename (No suffix)\nPDWGF\nstring(73)\n\nDWG filename (with suffix)\n\nAttribute Name\nData Type\nQualifier\nDescription\nACBTEX\nstring(500)\nAutoCAD annotation text\nACBTYP\nstring(180)\nAutoCAD annotation type\nACDMTX\nstring(500)\nAutoCAD dimension text\nACDTYP\nstring(180)\nAutoCAD dimension type\nACPLTX\nstring(500)\nAutoCAD projection line text\nACPTYP\nstring(180)\nAutoCAD projection line type\nDWGF\nstring(73)\nDWG filename (No suffix)\nODWGF\nstring(73)\nOpen DWG filename (No suffix)\nPDWGF\nstring(73)\nDWG filename (with suffix)\n\n\n"}
{"Headers": "Attribute Category: Aveva Only", "Content": "LOCK\nlogical\n\nLogical flag which determines if the UDAs attribute values are locked\n\nAttribute Name\nData Type\nQualifier\nDescription\nLOCK\nlogical\nLogical flag which determines if the UDAs attribute values are locked\n\n\n"}
{"Headers": "Attribute Category: Branch Specific", "Content": "BRCOG\npos\n\nBranch centre of gravity\nBRCONNECT\nelement(5000)\n\nBranch member connections\nBREARE\nreal\n\nBranch external surface area\nBRIARE\nreal\n\nBranch internal surface area\nBRICOG\npos\n\nBranch insulated centre of gravity\nBRIWEI\nreal\n\nBranch insulated weight\nBRLEG\nelement(5000)\n\nBranch members on the same leg\nBRWCOG\npos\n\nBranch wet centre of gravity\nBRWEIG\nreal\n\nBranch weight\nBRWICOG\npos\n\nBranch wet insulated centre of gravity\nBRWIWEI\nreal\n\nBranch insulated wet weight\nBRWWEI\nreal\n\nBranch wet weight\nCLLE\nreal\n\nBranch centreline length\nHEADH\nreal\n\nHead duct height\nHEADW\nreal\n\nHead duct width\nHEND\nstring\n\nConnection at other end of HREF (HEAD or TAIL)\nHPOSE\nreal\n\nEasting of head position\nHPOSN\nreal\n\nNorthing of head position\nHPOSU\nreal\n\nUpping of head position\nTAILH\nreal\n\nTail duct height\nTAILW\nreal\n\nTail duct width\nTEND\nstring\n\nConnection at other end of TREF (HEAD or TAIL)\nTPOSE\nreal\n\nEasting of tail position\nTPOSN\nreal\n\nNorthing of tail position\nTPOSU\nreal\n\nUpping of tail position\nTUCL\nreal\n\nTube centreline length of branch\nTULE\nreal\n\nTube length of branch\n\nAttribute Name\nData Type\nQualifier\nDescription\nBRCOG\npos\nBranch centre of gravity\nBRCONNECT\nelement(5000)\nBranch member connections\nBREARE\nreal\nBranch external surface area\nBRIARE\nreal\nBranch internal surface area\nBRICOG\npos\nBranch insulated centre of gravity\nBRIWEI\nreal\nBranch insulated weight\nBRLEG\nelement(5000)\nBranch members on the same leg\nBRWCOG\npos\nBranch wet centre of gravity\nBRWEIG\nreal\nBranch weight\nBRWICOG\npos\nBranch wet insulated centre of gravity\nBRWIWEI\nreal\nBranch insulated wet weight\nBRWWEI\nreal\nBranch wet weight\nCLLE\nreal\nBranch centreline length\nHEADH\nreal\nHead duct height\nHEADW\nreal\nHead duct width\nHEND\nstring\nConnection at other end of HREF (HEAD or TAIL)\nHPOSE\nreal\nEasting of head position\nHPOSN\nreal\nNorthing of head position\nHPOSU\nreal\nUpping of head position\nTAILH\nreal\nTail duct height\nTAILW\nreal\nTail duct width\nTEND\nstring\nConnection at other end of TREF (HEAD or TAIL)\nTPOSE\nreal\nEasting of tail position\nTPOSN\nreal\nNorthing of tail position\nTPOSU\nreal\nUpping of tail position\nTUCL\nreal\nTube centreline length of branch\nTULE\nreal\nTube length of branch\n\n\n"}
{"Headers": "Attribute Category: Cable", "Content": "CBSTAT\nstring(700)\ninteger\nCable routing status text\nCCOREF\nelement\n\nCable core set reference\nFILCAL\nstring(80)\n\nFILCAL (name of cable fill level calculation used)\n\nAttribute Name\nData Type\nQualifier\nDescription\nCBSTAT\nstring(700)\ninteger\nCable routing status text\nCCOREF\nelement\nCable core set reference\nFILCAL\nstring(80)\nFILCAL (name of cable fill level calculation used)\n\n\n"}
{"Headers": "Attribute Category: Cabling", "Content": "ACLIST\nelement(500)\n\nArriving cables to attached point\nATCONN\nelement(500)\n\nList of elements connected to attachment\nAYDIR\ndir\n\nArrive Y axis direction\nBRLIST\nreal(500)\n\nBend radii of a cable\nCABBOX\nreal(6)\n\nCalculated box volume in world coordinates\nCABGAP\nreal\n\ncable gap on cabletray as multiple of OUTD\nCABINT\nstring(120)\n\ncable interference class\nCABLAY(OUT)\nreal\n\nDefines laying method for cables inside the branch. Attribute on %CWAY has no effect on functionality \u2013 it's used only to cascading down to CWBRAN during creation of new CWBRAN.\nCBACXR\nreal\ninteger\nAccumulated cables xarea at route node\nCBCOG\npos\n\nCable centre of gravity\nCBCULE\nreal\n\nCut Length of cable\nCBFRLE\nreal(20)\n\nFree Length of cable\nCBGELE\nreal\n\nGeometric Length of cable\nCBNUCW\nelement(500)\n\nCables at a point on a cableway\nCBPREF\nelement(500)\n\nReferences to POINTR forming route of a cable\nCBRNLS\nelement(500)\n\nList of route nodes that cable passes\nCBRRLS\nelement(500)\n\nList of route nodes and rattas that cable passes\nCBRWGL\nreal\n\nRaw Geometric Length of cable\nCBSTT\nstring(10)\n\nCable status text\nCBTOLE\nreal\n\nTotal Length of Cable\nCBWEIG\nreal\n\nCable weight\nCENRAD\n\n\nReturns the centre radius of CWBRAN volume at this particular point\nCENRADIUS\nreal\n\nCentreline Radius\nCFCHE\nlogical\n\nFill level check\nCFILL\nreal\n\nFill level at route node\nCLIST\nelement(500)\ninteger\nAll cables attached to route node\nCMAXF\nreal\n\nCalculate maximum fill level on cway\nCMINF\nreal\n\nCalculate minimum fill level on cway\nCONATS\nelement(500)\n\nList of attachment connected to attachment\nCONBRA\nelement(500)\n\nList of branches connected to branch\nCONNE\nlogical\n\nSegment end connection flag\nCONNS\nlogical\n\nSegment start connection flag\nCONSIS\nlogical\n\nPosition consistency\nCONTRA\nelement(500)\n\nList of trays connected to branch\nCWJBLS\nelement(500)\n\nCableway branches and junction boxes list\nCWJUSL\nword\n\nCable Way Justification Line\nCWLIST\nelement(500)\n\nAll cableways attached to route node\nCWPPJB\nelement(500)\n\nCableway branches and pull pits and junction boxes list\nCWPPLS\nelement(500)\n\nCableway branches and pull pits list\nDEPREF\nelement(500)\n\nList of elements connected to branch tail\nDFBRAD(IUS)\nreal\n\nReturn value of radius at POINTR used to select correct specification component:\nAlways inside radius at bends\nInside or outside radius at risers *(depending whether riser is Inside/Outside)\nELCXRF\nelement(500)\n\nReturn reference from CABLE element to ELCONN element\nENBINF\npos\ninteger\nEnd bend information\nFCENTRE\npos\n\nCentre of fillet arc\nFEND\npos\n\nFillet arc position\nFILREF\nelement(500)\n\nSorted references to attachment points with ascending order of fill level greater then 0\nFLEVEL\nreal\ninteger\nFill level at route node\nFMID\npos\n\nMiddle point of fillet arc\nFSTART\npos\n\nFillet start position\nHDCONN\nelement(500)\n\nList of elements connected to branch head\nHDREF\nelement(500)\n\nList of attachment connected to attachment\nINSLEN\nreal(200)\n\nInstallation length\nINSMETHOD\nstring(240)\n\nGetting installation method lengths. The output is a textual array describing length of installation method along the cable. Size of the array depends on how many different installation methods are applied along the cable route.\nINSRAD\n\n\nReturns the smallest radius of CWBRAN at this particular point\nINSRADIUS\nreal\n\nInside Radius\nINSTLV(EL)\nstring(240)\n\nGetting installation level and dressing. The output is a textual array of 5 elements as follows:\nFree Route, <length>\nlength of the part of the cable that is routed outside branch\nUnderground Dressed, <length>\n\u2026 inside *underground dressed branch\nUnderground Not Dressed, <length>\n...inside underground undressed branch\nAbove Ground Dressed, <length>\n...inside above ground dressed branch\nAbove Ground Not Dressed\n...inside above ground dressed branch\n*underground \u2013 is determined by attribute UNDERG queried on the branch\nINVRAD(IUS)\nlogical\n\nReturns true if cable uses a radius smaller than minimum radius for it's specification (see property MINBEN)\nJBLIST\nelement(500)\n\nJunction boxes list\nLALCAB\nelement(500)\n\nList arriving leaving cables on attached point\nLAYMOT\nstring(100)\ninteger\nLayout mode text\nLYDIR\ndir\n\nLeave Y axis direction on point\nMINFIL\nreal\n\nMin Fill level on Cableway and Cabletray components\nNPLIST\nelement(500)\n\nAll NATPs attached to route node\nNUMCOR\ninteger\n\nNumber of cores in a cable\nOUTRAD\n\n\nReturns the biggest radius of CWBRAN at this particular point\nOUTRADIUS\nreal\n\nOutside Radius\nOVCWIDTH\nreal\n\nOverall cables width\nPRFELE\nelement\n\nCableway profile element\nPRFOBS\ninteger\n\nCableway profile obstructions\nPULLLS\nelement(500)\n\nPull pit list\nRADI\nreal\n\nObtains the radius of a cable at this particular point\nRCONAT\nelement(500)\nelement\nList of valid connected route attachments\nRILIST\nelement(500)\n\nRoute information list\nRMINIMUM\nreal\n\nScans all the routing points the cable is routed through and returns the minimal radius of the cable\nRNODEL\nelement(500)\nword\nRnode list\nROUHEIGHT\nreal\n\nRouting Height\nROUWIDTH\nreal\n\nRouting Width\nSTBINF\npos\ninteger\nStart bend information\nSTRJUS\nword\n\nCable Way Justification Line\nTLCONN\nelement(500)\n\nList of elements connected to branch tail\nTLREF\nelement(500)\n\nList of attachment connected to attachment\nTXAREA\nreal\n\nTotal Cableway X-area\nVRADI\nreal\n\nCableway radius\n\nAttribute Name\nData Type\nQualifier\nDescription\nACLIST\nelement(500)\nArriving cables to attached point\nATCONN\nelement(500)\nList of elements connected to attachment\nAYDIR\ndir\nArrive Y axis direction\nBRLIST\nreal(500)\nBend radii of a cable\nCABBOX\nreal(6)\nCalculated box volume in world coordinates\nCABGAP\nreal\ncable gap on cabletray as multiple of OUTD\nCABINT\nstring(120)\ncable interference class\nCABLAY(OUT)\nreal\nDefines laying method for cables inside the branch. Attribute on %CWAY has no effect on functionality \u2013 it's used only to cascading down to CWBRAN during creation of new CWBRAN.\nCBACXR\nreal\ninteger\nAccumulated cables xarea at route node\nCBCOG\npos\nCable centre of gravity\nCBCULE\nreal\nCut Length of cable\nCBFRLE\nreal(20)\nFree Length of cable\nCBGELE\nreal\nGeometric Length of cable\nCBNUCW\nelement(500)\nCables at a point on a cableway\nCBPREF\nelement(500)\nReferences to POINTR forming route of a cable\nCBRNLS\nelement(500)\nList of route nodes that cable passes\nCBRRLS\nelement(500)\nList of route nodes and rattas that cable passes\nCBRWGL\nreal\nRaw Geometric Length of cable\nCBSTT\nstring(10)\nCable status text\nCBTOLE\nreal\nTotal Length of Cable\nCBWEIG\nreal\nCable weight\nCENRAD\nReturns the centre radius of CWBRAN volume at this particular point\nCENRADIUS\nreal\nCentreline Radius\nCFCHE\nlogical\nFill level check\nCFILL\nreal\nFill level at route node\nCLIST\nelement(500)\ninteger\nAll cables attached to route node\nCMAXF\nreal\nCalculate maximum fill level on cway\nCMINF\nreal\nCalculate minimum fill level on cway\nCONATS\nelement(500)\nList of attachment connected to attachment\nCONBRA\nelement(500)\nList of branches connected to branch\nCONNE\nlogical\nSegment end connection flag\nCONNS\nlogical\nSegment start connection flag\nCONSIS\nlogical\nPosition consistency\nCONTRA\nelement(500)\nList of trays connected to branch\nCWJBLS\nelement(500)\nCableway branches and junction boxes list\nCWJUSL\nword\nCable Way Justification Line\nCWLIST\nelement(500)\nAll cableways attached to route node\nCWPPJB\nelement(500)\nCableway branches and pull pits and junction boxes list\nCWPPLS\nelement(500)\nCableway branches and pull pits list\nDEPREF\nelement(500)\nList of elements connected to branch tail\nDFBRAD(IUS)\nreal\nReturn value of radius at POINTR used to select correct specification component:\nAlways inside radius at bends\nInside or outside radius at risers *(depending whether riser is Inside/Outside)\nELCXRF\nelement(500)\nReturn reference from CABLE element to ELCONN element\nENBINF\npos\ninteger\nEnd bend information\nFCENTRE\npos\nCentre of fillet arc\nFEND\npos\nFillet arc position\nFILREF\nelement(500)\nSorted references to attachment points with ascending order of fill level greater then 0\nFLEVEL\nreal\ninteger\nFill level at route node\nFMID\npos\nMiddle point of fillet arc\nFSTART\npos\nFillet start position\nHDCONN\nelement(500)\nList of elements connected to branch head\nHDREF\nelement(500)\nList of attachment connected to attachment\nINSLEN\nreal(200)\nInstallation length\nINSMETHOD\nstring(240)\nGetting installation method lengths. The output is a textual array describing length of installation method along the cable. Size of the array depends on how many different installation methods are applied along the cable route.\nINSRAD\nReturns the smallest radius of CWBRAN at this particular point\nINSRADIUS\nreal\nInside Radius\nINSTLV(EL)\nstring(240)\nGetting installation level and dressing. The output is a textual array of 5 elements as follows:\nFree Route, <length>\nlength of the part of the cable that is routed outside branch\nUnderground Dressed, <length>\n\u2026 inside *underground dressed branch\nUnderground Not Dressed, <length>\n...inside underground undressed branch\nAbove Ground Dressed, <length>\n...inside above ground dressed branch\nAbove Ground Not Dressed\n...inside above ground dressed branch\n*underground \u2013 is determined by attribute UNDERG queried on the branch\nINVRAD(IUS)\nlogical\nReturns true if cable uses a radius smaller than minimum radius for it's specification (see property MINBEN)\nJBLIST\nelement(500)\nJunction boxes list\nLALCAB\nelement(500)\nList arriving leaving cables on attached point\nLAYMOT\nstring(100)\ninteger\nLayout mode text\nLYDIR\ndir\nLeave Y axis direction on point\nMINFIL\nreal\nMin Fill level on Cableway and Cabletray components\nNPLIST\nelement(500)\nAll NATPs attached to route node\nNUMCOR\ninteger\nNumber of cores in a cable\nOUTRAD\nReturns the biggest radius of CWBRAN at this particular point\nOUTRADIUS\nreal\nOutside Radius\nOVCWIDTH\nreal\nOverall cables width\nPRFELE\nelement\nCableway profile element\nPRFOBS\ninteger\nCableway profile obstructions\nPULLLS\nelement(500)\nPull pit list\nRADI\nreal\nObtains the radius of a cable at this particular point\nRCONAT\nelement(500)\nelement\nList of valid connected route attachments\nRILIST\nelement(500)\nRoute information list\nRMINIMUM\nreal\nScans all the routing points the cable is routed through and returns the minimal radius of the cable\nRNODEL\nelement(500)\nword\nRnode list\nROUHEIGHT\nreal\nRouting Height\nROUWIDTH\nreal\nRouting Width\nSTBINF\npos\ninteger\nStart bend information\nSTRJUS\nword\nCable Way Justification Line\nTLCONN\nelement(500)\nList of elements connected to branch tail\nTLREF\nelement(500)\nList of attachment connected to attachment\nTXAREA\nreal\nTotal Cableway X-area\nVRADI\nreal\nCableway radius\n\n\n"}
{"Headers": "Attribute Category: Catalog", "Content": "BRTXRF\nelement(500)\n\nReturn reference from Branch Table element to SPECs\nBTHK\nstring(1000)\n\nParameterised bolt thickness\nBTYP\nstring(1000)\n\nBolt type\nCCORXR\nelement(500)\n\nReturn reference from CCORSET element to SCOMs\nCOCDRE\nelement(500)\nword\nCOCDESS with same COCONN value as qualifier\nCOCOXR\nelement(500)\n\nCOCO description return reference\nCOCSAM\nelement(500)\n\nCOCOS with same CTYP value as COCDES\nCTYPLI\nword(5000)\n\nList of COCO Ctypes\nDESGEO\nelement(5000)\n\nDesign geometrical dependencies\nDUPLIC\nelement(10000)\ninteger\nDuplicates of the current element with the same attribute values\nGAPALL\nstring(1000)\n\nGap Allowance\nGEODEP\nelement(5000)\n\nDirect geometrical dependencies\nHDUPLI\nelement(10000)\ninteger\nDuplicates of the current element (checking members)\nLBBORE\nlogical\n\nTRUE if Minor/Branch bore is in nominal bore table\nLHBORE\nlogical\n\nTRUE if Major/Header bore is in nominal bore table\nLRBORE\nlogical\n\nTRUE if bores is in reducer table\nLTBORE\nlogical\n\nTRUE if bores is in branch (tee) table\nNOMXRF\nelement(500)\n\nReturn reference from NOMTAB element to SPECs\nPAAX\nstring(30)\n\nDirection of axis\nPAXI\nstring(30)\n\nAxial direction\nPBAX\nstring(30)\n\nDirection\nPCAX\nstring(30)\n\nDirection of C offset\nPRTRTX\nstring(1000)\nword\nPart element R text\nPRTSTX\nstring(1000)\nword\nPart element S text\nPRTTTX\nstring(1000)\nword\nPart element T text\nPRTXRF\nelement(500)\n\nReturn reference from PART element to SPCOs\nPZAXI\nstring(30)\n\nAlignment axial direction\nREDXRF\nelement(500)\n\nReturn reference from Reducer Table element to SPECs\nSCHED\nstring(10)\n\nPiping Schedule\n\nAttribute Name\nData Type\nQualifier\nDescription\nBRTXRF\nelement(500)\nReturn reference from Branch Table element to SPECs\nBTHK\nstring(1000)\nParameterised bolt thickness\nBTYP\nstring(1000)\nBolt type\nCCORXR\nelement(500)\nReturn reference from CCORSET element to SCOMs\nCOCDRE\nelement(500)\nword\nCOCDESS with same COCONN value as qualifier\nCOCOXR\nelement(500)\nCOCO description return reference\nCOCSAM\nelement(500)\nCOCOS with same CTYP value as COCDES\nCTYPLI\nword(5000)\nList of COCO Ctypes\nDESGEO\nelement(5000)\nDesign geometrical dependencies\nDUPLIC\nelement(10000)\ninteger\nDuplicates of the current element with the same attribute values\nGAPALL\nstring(1000)\nGap Allowance\nGEODEP\nelement(5000)\nDirect geometrical dependencies\nHDUPLI\nelement(10000)\ninteger\nDuplicates of the current element (checking members)\nLBBORE\nlogical\nTRUE if Minor/Branch bore is in nominal bore table\nLHBORE\nlogical\nTRUE if Major/Header bore is in nominal bore table\nLRBORE\nlogical\nTRUE if bores is in reducer table\nLTBORE\nlogical\nTRUE if bores is in branch (tee) table\nNOMXRF\nelement(500)\nReturn reference from NOMTAB element to SPECs\nPAAX\nstring(30)\nDirection of axis\nPAXI\nstring(30)\nAxial direction\nPBAX\nstring(30)\nDirection\nPCAX\nstring(30)\nDirection of C offset\nPRTRTX\nstring(1000)\nword\nPart element R text\nPRTSTX\nstring(1000)\nword\nPart element S text\nPRTTTX\nstring(1000)\nword\nPart element T text\nPRTXRF\nelement(500)\nReturn reference from PART element to SPCOs\nPZAXI\nstring(30)\nAlignment axial direction\nREDXRF\nelement(500)\nReturn reference from Reducer Table element to SPECs\nSCHED\nstring(10)\nPiping Schedule\n\n\n"}
{"Headers": "Attribute Category: Catalogue", "Content": "COMPTYPE\nword\n\nType of component\n\nAttribute Name\nData Type\nQualifier\nDescription\nCOMPTYPE\nword\nType of component\n\n\n"}
{"Headers": "Attribute Category: Catalog Value for Design Item", "Content": "PTYP\nword\n\nProperty type\n\nAttribute Name\nData Type\nQualifier\nDescription\nPTYP\nword\nProperty type\n\n\n"}
{"Headers": "Attribute Category: Catalog Values for Design Item", "Content": "APAR\nreal(100)\n\nAttached catalogue parameters\nCATR\nelement\n\nCatalogue reference\nCATTEX\nstring(725)\n\nConcatenation of Detailing and Material Texts\nCPAR\nreal(100)\n\nCatalogue parameters\nDEFSPK\nelement\n\nDefault Reference of SPEC for branch members\nDETR\nelement\n\nDetailing text reference\nDTXR\nstring(2000)\n\nRTEXT of detailing text\nDTXS\nstring(2000)\n\nSTEXT of detailing text\nDTXT\nstring(2000)\n\nTTEXT of detailing text\nGMRE\nelement\n\nGeometry set reference\nGSTR\nelement\n\nStructural geometry set reference\nGTYP\nword\n\nGeneric type\nIPAR\nreal(30)\n\nParameters of the insulation catalogue component\nMATR\nelement\n\nMaterial reference\nMTXR\nelement\n\nMaterial text reference\nMTXX\nstring(2000)\n\nXTEXT of material text\nMTXY\nstring(2000)\n\nYTEXT of material text\nMTXZ\nstring(2000)\n\nZTEXT of material text\nNGMR\nelement\n\nNegative geometry set reference\nOPAR\nreal(100)\n\nOwning parameters - catalogue component\nPARA\nreal(100)\n\nParameters\nPSTR\nelement\n\nStructural Pline set reference\nPTRE\nelement\n\nPoint set reference\nSKEYSCALE\ninteger\n\nUniversal SKEY scale factor\nSPMA\nreal\nword\nSpec angle maximum answer\nSPOW\nelement\n\nReference of SPEC owning SPCO of branch members\nSPRA\nreal\nword\nSpec angle answer\nSPRB\nreal\nword\nSpec bore answer\nSPWD\nstring\nword\nSpec text answer\nSTYP\nstring\n\nSPECON type question\nTPAR\nreal(30)\n\nTrace catalogue component parameters\nWPAR\nword(100)\n\nParameters as a word\n\nAttribute Name\nData Type\nQualifier\nDescription\nAPAR\nreal(100)\nAttached catalogue parameters\nCATR\nelement\nCatalogue reference\nCATTEX\nstring(725)\nConcatenation of Detailing and Material Texts\nCPAR\nreal(100)\nCatalogue parameters\nDEFSPK\nelement\nDefault Reference of SPEC for branch members\nDETR\nelement\nDetailing text reference\nDTXR\nstring(2000)\nRTEXT of detailing text\nDTXS\nstring(2000)\nSTEXT of detailing text\nDTXT\nstring(2000)\nTTEXT of detailing text\nGMRE\nelement\nGeometry set reference\nGSTR\nelement\nStructural geometry set reference\nGTYP\nword\nGeneric type\nIPAR\nreal(30)\nParameters of the insulation catalogue component\nMATR\nelement\nMaterial reference\nMTXR\nelement\nMaterial text reference\nMTXX\nstring(2000)\nXTEXT of material text\nMTXY\nstring(2000)\nYTEXT of material text\nMTXZ\nstring(2000)\nZTEXT of material text\nNGMR\nelement\nNegative geometry set reference\nOPAR\nreal(100)\nOwning parameters - catalogue component\nPARA\nreal(100)\nParameters\nPSTR\nelement\nStructural Pline set reference\nPTRE\nelement\nPoint set reference\nSKEYSCALE\ninteger\nUniversal SKEY scale factor\nSPMA\nreal\nword\nSpec angle maximum answer\nSPOW\nelement\nReference of SPEC owning SPCO of branch members\nSPRA\nreal\nword\nSpec angle answer\nSPRB\nreal\nword\nSpec bore answer\nSPWD\nstring\nword\nSpec text answer\nSTYP\nstring\nSPECON type question\nTPAR\nreal(30)\nTrace catalogue component parameters\nWPAR\nword(100)\nParameters as a word\n\n\n"}
{"Headers": "Attribute Category: Catalog Values for Ducting Item", "Content": "ARRHEI\nreal\n\nArrive height\nARRWID\nreal\n\nArrive width\nLEAHEI\nreal\n\nLeave height\nLEAWID\nreal\n\nLeave width\nPPHEI\nreal\ninteger\nPpoint height\nPPWID\nreal\ninteger\nPpoint width\n\nAttribute Name\nData Type\nQualifier\nDescription\nARRHEI\nreal\nArrive height\nARRWID\nreal\nArrive width\nLEAHEI\nreal\nLeave height\nLEAWID\nreal\nLeave width\nPPHEI\nreal\ninteger\nPpoint height\nPPWID\nreal\ninteger\nPpoint width\n\n\n"}
{"Headers": "Attribute Category: Catalog Values for Hanger Item", "Content": "HHBO\nreal\n\nHanger head bore\nHHBP\npos\n\nBottom of hanger head\nHHCO\nword\n\nHanger head connection type\nHHDR\ndir\n\nHanger head direction\nHHGR\nreal\n\nHanger head gradient\nHHOD\nreal\n\nHanger head outside diameter\nHHPO\npos\n\nHanger head position\nHHTP\npos\n\nTop of hanger head\nHTBO\nreal\n\nHanger tail bore\nHTBP\npos\n\nBottom of hanger tail\nHTCO\nword\n\nHanger tail connection type\nHTDR\ndir\n\nHanger tail direction\nHTGR\nreal\n\nHanger tail gradient\nHTOD\nreal\n\nHanger tail outside diameter\nHTPO\npos\n\nHanger tail position\nHTTP\npos\n\nTop of hanger tail\n\nAttribute Name\nData Type\nQualifier\nDescription\nHHBO\nreal\nHanger head bore\nHHBP\npos\nBottom of hanger head\nHHCO\nword\nHanger head connection type\nHHDR\ndir\nHanger head direction\nHHGR\nreal\nHanger head gradient\nHHOD\nreal\nHanger head outside diameter\nHHPO\npos\nHanger head position\nHHTP\npos\nTop of hanger head\nHTBO\nreal\nHanger tail bore\nHTBP\npos\nBottom of hanger tail\nHTCO\nword\nHanger tail connection type\nHTDR\ndir\nHanger tail direction\nHTGR\nreal\nHanger tail gradient\nHTOD\nreal\nHanger tail outside diameter\nHTPO\npos\nHanger tail position\nHTTP\npos\nTop of hanger tail\n\n\n"}
{"Headers": "Attribute Category: Catalog Values for Piping Item", "Content": "AALLAN\nreal\n\nArrive Ppoint allowed angle\nABOP\npos\n\nBottom of arrive pipe\nABOR\nreal\n\nArrive bore\nACON\nword\n\nArrive connection type\nACORRO\nreal\n\nArrive corrosion allowance\nADIR\ndir\n\nArrive direction\nAGRD\nreal\n\nArrive Ppoint gradient\nAOD\nreal\n\nArrive Ppoint outside diameter\nAPOS\npos\n\nArrive position\nAPOSE\nreal\n\nEasting of arrive position\nAPOSN\nreal\n\nNorthing of arrive position\nAPOSU\nreal\n\nUpping of arrive position\nAQAANG\nreal\n\nAngle between alignment direction of arrive pp and previous\nAQANG\nreal\n\nAngle between arrive Ppoint and previous component\nAQBORE\nlogical\n\nTRUE if arrive Ppoint has same bore as previous\nAQCON\nlogical\n\nTRUE if arrive Ppoint has Correct connection type\nAQOFF\nreal\n\nOffset between arrive Ppoint and previous component\nATCORR\nreal\n\nArrive tube corrosion allowance\nATOP\npos\n\nTop of arrive pipe\nATSTLEN\nreal\n\nArrive Tube Stock Length\nATWALL\nreal\n\nArrive tube wall thickness\nAWALLT\nreal\n\nArrive wall thickness\nAZDIR\ndir\n\nArrive alignment direction\nBJOINT\nstring\n\nBolt joint\nBTOTAL\ninteger\n\nBolt joint total\nBTOTWE\nreal\n\nBolt total weight\nDCORRO\nreal\n\nDerived corrosion\nDFBRADIUS\nreal\nelement\nDefault bend radius\nDWALLT\nreal\n\nDerive wall thickness\nFLALLO\nreal\n\nFlange allowance\nFLOFFS\nreal\n\nFlange offset\nHCORRO\nreal\n\nHead Corrosion\nHWALLT\nreal\n\nHead wall thickness\nLALLAN\nreal\n\nLeave Ppoint allowed angle\nLBOP\npos\n\nBottom of leave pipe\nLBOR\nreal\n\nLeave bore\nLCON\nword\n\nLeave connection type\nLCORRO\nreal\n\nLeave corrosion allowance\nLDI\ndir\n\nLeave direction\nLGRD\nreal\n\nLeave Ppoint gradient\nLOD\nreal\n\nLeave Ppoint outside diameter\nLPOS\npos\n\nLeave position\nLPOSE\nreal\n\nEasting of leave position\nLPOSN\nreal\n\nNorthing of leave position\nLPOSU\nreal\n\nUpping of leave position\nLQAANG\nreal\n\nAngle between alignment direction of leave Ppoint and next\nLQANG\nreal\n\nAngle between leave Ppoint and next component\nLQBORE\nlogical\n\nTRUE if leave Ppoint has same bore as next\nLQCON\nlogical\n\nTRUE if leave Ppoint has Correct connection type\nLQOFF\nreal\n\nOffset between leave Ppoint and next component\nLTCORR\nreal\n\nLeave tube corrosion allowance\nLTOP\npos\n\nTop of leave pipe\nLTSTLEN\nreal\n\nLeave Tube Stock Length\nLTWALL\nreal\n\nLeave tube wall thickness\nLWALLT\nreal\n\nLeave wall thickness\nLZDIR\ndir\n\nLeave alignment direction\nMAXB\nreal\n\nMaximum bore\nNOMBIN\nreal(200)\nword\nList of valid Nominal bores in Inches\nNOMBMM\nreal(200)\nword\nList of valid Nominal bores in MM\nPALLAN\nreal\ninteger\nPpoint allowed angle\nPBOP\npos\ninteger\nBottom of pipe\nPCORRO\nreal\ninteger\nP Tube corrosion\nPCWALL\nreal\ninteger\nPpoint connect wall thickness\nPFLALL\nstring(1000)\n\nFlange allowance parameter\nPFLOFF\nstring(1000)\n\nFlange offset parameter\nPHBO\nreal\n\nPipe head bore\nPHBP\npos\n\nBottom of pipe head\nPHCO\nword\n\nPipe head connection type\nPHDR\ndir\n\nPipe head direction\nPHGR\nreal\n\nPipe head gradient\nPHOD\nreal\n\nPipe head outside diameter\nPHPO\npos\n\nPipe head position\nPHTP\npos\n\nTop of pipe head\nPQAANG\nreal\ninteger\nAngle between alignment direction of specified pp and adjacent component\nPQANG\nreal\ninteger\nAngle between specified Ppoint and adjacent component\nPQBORE\nlogical\ninteger\nTRUE if specified Ppoint has same bore as adjacent\nPQCON\nlogical\ninteger\nTRUE if leave Ppoint has Correct connection type\nPQOFF\nreal\ninteger\nOffset between specified Ppoint and adjacent component\nPTBO\nreal\n\nPipe tail bore\nPTBP\npos\n\nBottom of pipe tail\nPTCO\nword\n\nPipe tail connection type\nPTDR\ndir\n\nPipe tail direction\nPTGR\nreal\n\nPipe tail gradient\nPTOD\nreal\n\nPipe tail outside diameter\nPTOP\npos\ninteger\nTop of pipe\nPTPO\npos\n\nPipe tail position\nPTTP\npos\n\nTop of pipe tail\nPWALLT\nreal\ninteger\nPpoint wall thickness\nRANANG\nreal(32)\nelemtype\nRange of available angles for bends and elbows\nRANRAD\nreal(32)\nelemtype\nRange of available radii\nTCORRO\nreal\n\nTail Corrosion\nTWALLT\nreal\n\nTail wall thickness\nWALLTH\nreal\n\nTube wall thickness\nWTHICK\nreal\n\nWall thickness\n\nAttribute Name\nData Type\nQualifier\nDescription\nAALLAN\nreal\nArrive Ppoint allowed angle\nABOP\npos\nBottom of arrive pipe\nABOR\nreal\nArrive bore\nACON\nword\nArrive connection type\nACORRO\nreal\nArrive corrosion allowance\nADIR\ndir\nArrive direction\nAGRD\nreal\nArrive Ppoint gradient\nAOD\nreal\nArrive Ppoint outside diameter\nAPOS\npos\nArrive position\nAPOSE\nreal\nEasting of arrive position\nAPOSN\nreal\nNorthing of arrive position\nAPOSU\nreal\nUpping of arrive position\nAQAANG\nreal\nAngle between alignment direction of arrive pp and previous\nAQANG\nreal\nAngle between arrive Ppoint and previous component\nAQBORE\nlogical\nTRUE if arrive Ppoint has same bore as previous\nAQCON\nlogical\nTRUE if arrive Ppoint has Correct connection type\nAQOFF\nreal\nOffset between arrive Ppoint and previous component\nATCORR\nreal\nArrive tube corrosion allowance\nATOP\npos\nTop of arrive pipe\nATSTLEN\nreal\nArrive Tube Stock Length\nATWALL\nreal\nArrive tube wall thickness\nAWALLT\nreal\nArrive wall thickness\nAZDIR\ndir\nArrive alignment direction\nBJOINT\nstring\nBolt joint\nBTOTAL\ninteger\nBolt joint total\nBTOTWE\nreal\nBolt total weight\nDCORRO\nreal\nDerived corrosion\nDFBRADIUS\nreal\nelement\nDefault bend radius\nDWALLT\nreal\nDerive wall thickness\nFLALLO\nreal\nFlange allowance\nFLOFFS\nreal\nFlange offset\nHCORRO\nreal\nHead Corrosion\nHWALLT\nreal\nHead wall thickness\nLALLAN\nreal\nLeave Ppoint allowed angle\nLBOP\npos\nBottom of leave pipe\nLBOR\nreal\nLeave bore\nLCON\nword\nLeave connection type\nLCORRO\nreal\nLeave corrosion allowance\nLDI\ndir\nLeave direction\nLGRD\nreal\nLeave Ppoint gradient\nLOD\nreal\nLeave Ppoint outside diameter\nLPOS\npos\nLeave position\nLPOSE\nreal\nEasting of leave position\nLPOSN\nreal\nNorthing of leave position\nLPOSU\nreal\nUpping of leave position\nLQAANG\nreal\nAngle between alignment direction of leave Ppoint and next\nLQANG\nreal\nAngle between leave Ppoint and next component\nLQBORE\nlogical\nTRUE if leave Ppoint has same bore as next\nLQCON\nlogical\nTRUE if leave Ppoint has Correct connection type\nLQOFF\nreal\nOffset between leave Ppoint and next component\nLTCORR\nreal\nLeave tube corrosion allowance\nLTOP\npos\nTop of leave pipe\nLTSTLEN\nreal\nLeave Tube Stock Length\nLTWALL\nreal\nLeave tube wall thickness\nLWALLT\nreal\nLeave wall thickness\nLZDIR\ndir\nLeave alignment direction\nMAXB\nreal\nMaximum bore\nNOMBIN\nreal(200)\nword\nList of valid Nominal bores in Inches\nNOMBMM\nreal(200)\nword\nList of valid Nominal bores in MM\nPALLAN\nreal\ninteger\nPpoint allowed angle\nPBOP\npos\ninteger\nBottom of pipe\nPCORRO\nreal\ninteger\nP Tube corrosion\nPCWALL\nreal\ninteger\nPpoint connect wall thickness\nPFLALL\nstring(1000)\nFlange allowance parameter\nPFLOFF\nstring(1000)\nFlange offset parameter\nPHBO\nreal\nPipe head bore\nPHBP\npos\nBottom of pipe head\nPHCO\nword\nPipe head connection type\nPHDR\ndir\nPipe head direction\nPHGR\nreal\nPipe head gradient\nPHOD\nreal\nPipe head outside diameter\nPHPO\npos\nPipe head position\nPHTP\npos\nTop of pipe head\nPQAANG\nreal\ninteger\nAngle between alignment direction of specified pp and adjacent component\nPQANG\nreal\ninteger\nAngle between specified Ppoint and adjacent component\nPQBORE\nlogical\ninteger\nTRUE if specified Ppoint has same bore as adjacent\nPQCON\nlogical\ninteger\nTRUE if leave Ppoint has Correct connection type\nPQOFF\nreal\ninteger\nOffset between specified Ppoint and adjacent component\nPTBO\nreal\nPipe tail bore\nPTBP\npos\nBottom of pipe tail\nPTCO\nword\nPipe tail connection type\nPTDR\ndir\nPipe tail direction\nPTGR\nreal\nPipe tail gradient\nPTOD\nreal\nPipe tail outside diameter\nPTOP\npos\ninteger\nTop of pipe\nPTPO\npos\nPipe tail position\nPTTP\npos\nTop of pipe tail\nPWALLT\nreal\ninteger\nPpoint wall thickness\nRANANG\nreal(32)\nelemtype\nRange of available angles for bends and elbows\nRANRAD\nreal(32)\nelemtype\nRange of available radii\nTCORRO\nreal\nTail Corrosion\nTWALLT\nreal\nTail wall thickness\nWALLTH\nreal\nTube wall thickness\nWTHICK\nreal\nWall thickness\n\n\n"}
{"Headers": "Attribute Category: Catalog Values for Sloping Lines", "Content": "DEFSLO\nreal\n\nDefault pipe slope\nMAXSLO\nreal\n\nMaximum pipe slope\nMINSLO\nreal\n\nMinimum pipe slope\nMINVER\nreal\n\nMinimum vertical pipe slope\nOFFTOL\nstring(1000)\n\nPPoint offset tolerance\nPPOFFT\nreal\ninteger\nPpoint offset\nSLOREF\nelement\n\nPipe slope reference\n\nAttribute Name\nData Type\nQualifier\nDescription\nDEFSLO\nreal\nDefault pipe slope\nMAXSLO\nreal\nMaximum pipe slope\nMINSLO\nreal\nMinimum pipe slope\nMINVER\nreal\nMinimum vertical pipe slope\nOFFTOL\nstring(1000)\nPPoint offset tolerance\nPPOFFT\nreal\ninteger\nPpoint offset\nSLOREF\nelement\nPipe slope reference\n\n\n"}
{"Headers": "Attribute Category: Catalog Values for SUPCOMP Item", "Content": "SHBO\nreal\n\nSUPCOMP head bore\nSTBO\nreal\n\nSUPCOMP tail bore\n\nAttribute Name\nData Type\nQualifier\nDescription\nSHBO\nreal\nSUPCOMP head bore\nSTBO\nreal\nSUPCOMP tail bore\n\n\n"}
{"Headers": "Attribute Category: Change History", "Content": "ATTMOD\nlogical\nattr\nTrue if specified attribute has been modified this session\nATTMODC\nlogical\nattr\nTrue if specified attribute has been modified since comparison date\nATTMODLIST\nword(500)\ninteger\nList of attributes modified since given session\nATTMODLISTC\nword(500)\n\nList of attributes modified since comparison date\nCATMOD\ninteger\n\nCatalogue Geometry Modified- Not directly query able\nCRDATE\nstring(120)\nattr\nDate element created in current DB or if extract in ascendant\nCREXTR\ninteger\nattr\nExtract element created in current DB or if extract in ascendant\nCRINFO\nstring(200)\n\nDB creation information\nCRSESS\ninteger\nattr\nSession element created in current DB or if extract in ascendant\nCRUSER\nstring(120)\nattr\nUser created element in current DB or if extract in ascendant\nDBSESS\ninteger\n\nLast DB session\nELECRE\nlogical\ninteger\nTrue if created since given session\nELECREC\nlogical\n\nTrue if created since comparison date\nELEDEL\nlogical\ninteger\nTrue if deleted since given session\nELEDELC\nlogical\n\nTrue if deleted since comparison date\nELEMOD\nlogical\ninteger\nTrue if modified since given session\nELEMODC\nlogical\n\nTrue if modified since comparison date\nEXMOD\nlogical\n\nTrue if element modified in this extract\nGEOM\ninteger\n\nGeometry Modified- Not directly queryable\nHIST\ninteger(120)\nattr\nHistory of sessions in which element or specified attribute were made\nLASTM\nstring(120)\nattr\nDate of last modification\nMSESS\ninteger\nattr\nLast session number\nPRVSES\ninteger\ninteger\nPrevious Session to that specified\nRULEMOD\nlogical\nattr\nTrue if rule modified this session\nRULEMODC\nlogical\nattr\nTrue if rule modified since comparison date\nRULEMODLIST\nword(500)\ninteger\nList of rules modified since given session\nRULEMODLISTC\nword(500)\n\nList of rules modified since comparison date\nSESCLA\ninteger\n\nSession Of Claim\nSESSC\nstring(120)\ninteger\nComment for specified session\nSESSCA\ninteger(10000)\n\nList of pairs of DB number, last session number for all referenced DBs\nSESSCH\ninteger(10000)\n\nAs for SESSCA, but searches all descendants for referenced DBs\nSESSD\nstring(120)\ninteger\nDate of specified Session\nSESSM\ninteger\nattr\nSession Of Last Modification\nSESSNO\ninteger\n\nCurrent opened Session\nSESSU\nstring(120)\ninteger\nUser creating specified session\nUSERM\nstring(120)\nattr\nUser making last modification\n\nAttribute Name\nData Type\nQualifier\nDescription\nATTMOD\nlogical\nattr\nTrue if specified attribute has been modified this session\nATTMODC\nlogical\nattr\nTrue if specified attribute has been modified since comparison date\nATTMODLIST\nword(500)\ninteger\nList of attributes modified since given session\nATTMODLISTC\nword(500)\nList of attributes modified since comparison date\nCATMOD\ninteger\nCatalogue Geometry Modified- Not directly query able\nCRDATE\nstring(120)\nattr\nDate element created in current DB or if extract in ascendant\nCREXTR\ninteger\nattr\nExtract element created in current DB or if extract in ascendant\nCRINFO\nstring(200)\nDB creation information\nCRSESS\ninteger\nattr\nSession element created in current DB or if extract in ascendant\nCRUSER\nstring(120)\nattr\nUser created element in current DB or if extract in ascendant\nDBSESS\ninteger\nLast DB session\nELECRE\nlogical\ninteger\nTrue if created since given session\nELECREC\nlogical\nTrue if created since comparison date\nELEDEL\nlogical\ninteger\nTrue if deleted since given session\nELEDELC\nlogical\nTrue if deleted since comparison date\nELEMOD\nlogical\ninteger\nTrue if modified since given session\nELEMODC\nlogical\nTrue if modified since comparison date\nEXMOD\nlogical\nTrue if element modified in this extract\nGEOM\ninteger\nGeometry Modified- Not directly queryable\nHIST\ninteger(120)\nattr\nHistory of sessions in which element or specified attribute were made\nLASTM\nstring(120)\nattr\nDate of last modification\nMSESS\ninteger\nattr\nLast session number\nPRVSES\ninteger\ninteger\nPrevious Session to that specified\nRULEMOD\nlogical\nattr\nTrue if rule modified this session\nRULEMODC\nlogical\nattr\nTrue if rule modified since comparison date\nRULEMODLIST\nword(500)\ninteger\nList of rules modified since given session\nRULEMODLISTC\nword(500)\nList of rules modified since comparison date\nSESCLA\ninteger\nSession Of Claim\nSESSC\nstring(120)\ninteger\nComment for specified session\nSESSCA\ninteger(10000)\nList of pairs of DB number, last session number for all referenced DBs\nSESSCH\ninteger(10000)\nAs for SESSCA, but searches all descendants for referenced DBs\nSESSD\nstring(120)\ninteger\nDate of specified Session\nSESSM\ninteger\nattr\nSession Of Last Modification\nSESSNO\ninteger\nCurrent opened Session\nSESSU\nstring(120)\ninteger\nUser creating specified session\nUSERM\nstring(120)\nattr\nUser making last modification\n\n\n"}
{"Headers": "Attribute Category: Claim Related", "Content": "CLMID\nstring(120)\n\nUnique system ID of user claiming element\nCLMIDL\nstring(256)\n\nUnique system ID of user claiming element (long)\nCLMNUM\ninteger\n\nUser or extract number claiming element. Extract numbers are negative\nCLMTIE\nelement(4)\n\nReference to elements that are automatically claimed along with this element\nEXCLFR\nlogical\n\nTrue if element claimed from this extract. Only True for Primary elements\nEXCLHI\nelement(5000)\n\nPrimary elements in descendant hierarchy claimed to this extract(includes this element)\nEXCLPA\nlogical\n\nTrue if element claimed to Parent extract. Only True for Primary elements\nEXCLTO\nlogical\n\nTrue if element claimed to this extract. Only True for Primary elements\nEXNCLH\nelement(5000)\n\nPrimary elements in descendant hierarchy not claimed to this extract\nEXTRC\nstring(120)\n\nName of extract claiming element\nLCLM\nlogical\n\nTrue if element is claimed\nLCLMH\nlogical\n\nTrue if element and hierarchy claimed\nNPDESC\nelement(5000)\n\nList of non primary offspring\nOKCLA\nlogical\n\nTrue if element may be claimed\nOKCLH\nlogical\n\nTrue if element and hierarchy may be claimed\nOKREL\nlogical\n\nTrue if element may be released\nOKRLH\nlogical\n\nTrue if element and hierarchy may be released\nPRIMTY\nlogical\n\nTrue if element is primary\nPRMMEM\nlogical\n\nTrue if there are any primary elements amongst descendants\nPRMOWN\nelement\n\nPrimary owning element (will be itself if primary)\nUSCLHI\nelement(5000)\n\nElements in descendant hierarchy claimed to this user\nUSERC\nstring(120)\n\nUser name of user claiming element\nUSNCLH\nelement(5000)\n\nElements in descendant hierarchy not claimed to this user\n\nAttribute Name\nData Type\nQualifier\nDescription\nCLMID\nstring(120)\nUnique system ID of user claiming element\nCLMIDL\nstring(256)\nUnique system ID of user claiming element (long)\nCLMNUM\ninteger\nUser or extract number claiming element. Extract numbers are negative\nCLMTIE\nelement(4)\nReference to elements that are automatically claimed along with this element\nEXCLFR\nlogical\nTrue if element claimed from this extract. Only True for Primary elements\nEXCLHI\nelement(5000)\nPrimary elements in descendant hierarchy claimed to this extract(includes this element)\nEXCLPA\nlogical\nTrue if element claimed to Parent extract. Only True for Primary elements\nEXCLTO\nlogical\nTrue if element claimed to this extract. Only True for Primary elements\nEXNCLH\nelement(5000)\nPrimary elements in descendant hierarchy not claimed to this extract\nEXTRC\nstring(120)\nName of extract claiming element\nLCLM\nlogical\nTrue if element is claimed\nLCLMH\nlogical\nTrue if element and hierarchy claimed\nNPDESC\nelement(5000)\nList of non primary offspring\nOKCLA\nlogical\nTrue if element may be claimed\nOKCLH\nlogical\nTrue if element and hierarchy may be claimed\nOKREL\nlogical\nTrue if element may be released\nOKRLH\nlogical\nTrue if element and hierarchy may be released\nPRIMTY\nlogical\nTrue if element is primary\nPRMMEM\nlogical\nTrue if there are any primary elements amongst descendants\nPRMOWN\nelement\nPrimary owning element (will be itself if primary)\nUSCLHI\nelement(5000)\nElements in descendant hierarchy claimed to this user\nUSERC\nstring(120)\nUser name of user claiming element\nUSNCLH\nelement(5000)\nElements in descendant hierarchy not claimed to this user\n\n\n"}
{"Headers": "Attribute Category: Clasher", "Content": "CLCONN\nelement(5000)\ninteger\nElements that Clasher considers to be connected (and hence no clashes)\nHULLDE\nlogical\n\nTrue if element is a hull design item\nHULLPR\nlogical\n\nTrue if element is a hull production item\n\nAttribute Name\nData Type\nQualifier\nDescription\nCLCONN\nelement(5000)\ninteger\nElements that Clasher considers to be connected (and hence no clashes)\nHULLDE\nlogical\nTrue if element is a hull design item\nHULLPR\nlogical\nTrue if element is a hull production item\n\n\n"}
{"Headers": "Attribute Category: Commenting", "Content": "CTHLIS\nelement(500)\n\nList of attached comment threads\nCTHTOL\nelement(500)\n\nList elements assigned to a comment threads\n\nAttribute Name\nData Type\nQualifier\nDescription\nCTHLIS\nelement(500)\nList of attached comment threads\nCTHTOL\nelement(500)\nList elements assigned to a comment threads\n\n\n"}
{"Headers": "Attribute Category: Configuration", "Content": "CFKEYP\nstring(2000)\n\nConfiguration key path\n\nAttribute Name\nData Type\nQualifier\nDescription\nCFKEYP\nstring(2000)\nConfiguration key path\n\n\n"}
{"Headers": "Attribute Category: Core Code", "Content": "CORCOD\nstring(120)\n\nCore code\n\nAttribute Name\nData Type\nQualifier\nDescription\nCORCOD\nstring(120)\nCore code\n\n\n"}
{"Headers": "Attribute Category: Cross Section", "Content": "XAMANG\nreal\nword\nCross section along mounting angle\nXFTPT\npos\nword\nCross section foot point\nXINCL\nreal\nword\nCross section inclination angle\nXTHK\nreal\nword\nCross section thickness\nXTPPT\npos\nword\nCross section top point\nXXMANG\nreal\nword\nCross section cross mounting angle\n\nAttribute Name\nData Type\nQualifier\nDescription\nXAMANG\nreal\nword\nCross section along mounting angle\nXFTPT\npos\nword\nCross section foot point\nXINCL\nreal\nword\nCross section inclination angle\nXTHK\nreal\nword\nCross section thickness\nXTPPT\npos\nword\nCross section top point\nXXMANG\nreal\nword\nCross section cross mounting angle\n\n\n"}
{"Headers": "Attribute Category: Database", "Content": "ATTSIZE\ninteger\nattr\nActual size of attribute\nDBAC\nstring\n\nDB Access, MULTIWRITE or UPDATE\nDBCL\nstring\n\nDB Claim\nDBCNTL\nlogical\n\nTrue if element is in a control DB\nDBEXNO\ninteger\n\nDB Extract Number\nDBFI\nstring\n\nDB filename\nDBFN\ninteger\n\nDB file number\nDBNA\nstring\n\nDB name\nDBNU\ninteger\n\nDB Number\nDBREF\nelement\n\nDB reference\nDBTE\nstring\n\nDB Text Encoding\nDBTY\nword\n\nDB type (DESI, CATA etc)\nDBVAR\nlogical\n\nTrue if element is in a variant DB\nDBWRITE\nlogical\n\nTrue if element is in a writable DB\nDOUPGR\nlogical\n\nTrue if element is recommended to be upgraded in current db\nLCTROL\nlogical\n\nControlled DB Flag\nWDBNA\nstring\n\nWorking DB name\n\nAttribute Name\nData Type\nQualifier\nDescription\nATTSIZE\ninteger\nattr\nActual size of attribute\nDBAC\nstring\nDB Access, MULTIWRITE or UPDATE\nDBCL\nstring\nDB Claim\nDBCNTL\nlogical\nTrue if element is in a control DB\nDBEXNO\ninteger\nDB Extract Number\nDBFI\nstring\nDB filename\nDBFN\ninteger\nDB file number\nDBNA\nstring\nDB name\nDBNU\ninteger\nDB Number\nDBREF\nelement\nDB reference\nDBTE\nstring\nDB Text Encoding\nDBTY\nword\nDB type (DESI, CATA etc)\nDBVAR\nlogical\nTrue if element is in a variant DB\nDBWRITE\nlogical\nTrue if element is in a writable DB\nDOUPGR\nlogical\nTrue if element is recommended to be upgraded in current db\nLCTROL\nlogical\nControlled DB Flag\nWDBNA\nstring\nWorking DB name\n\n\n"}
{"Headers": "Attribute Category: Database Integrity", "Content": "UDETCHECK\nstring(120)\n\nReport from UDET check on element\n\nAttribute Name\nData Type\nQualifier\nDescription\nUDETCHECK\nstring(120)\nReport from UDET check on element\n\n\n"}
{"Headers": "Attribute Category: Data Model", "Content": "DLIST\nword(2000)\n\nList of all possible dist att types\nHLIS\nword(2000)\n\nList of all possible types in owning hierarchy\nLIST\nword(5000)\n\nList of all possible member types\nLLIS\nword(2000)\n\nList of all possible types in member hierarchy\nOLIS\nword(2000)\n\nList of all possible owner types\nREPTXT\nstring\n\nReporter text used for element type\n\nAttribute Name\nData Type\nQualifier\nDescription\nDLIST\nword(2000)\nList of all possible dist att types\nHLIS\nword(2000)\nList of all possible types in owning hierarchy\nLIST\nword(5000)\nList of all possible member types\nLLIS\nword(2000)\nList of all possible types in member hierarchy\nOLIS\nword(2000)\nList of all possible owner types\nREPTXT\nstring\nReporter text used for element type\n\n\n"}
{"Headers": "Attribute Category: Database Structure", "Content": "BACKRE\nelement(1000)\nattr\nList reftable back references\nCONNECTIONS\nelement(5000)\n\nConnections\nCONNECTIONSH\nelement(5000)\n\nConnections for all descendants\nCONNER\nstring(300)\ninteger\nConnection error message\nDDEP\ninteger\n\nDatabase depth within hierarchy (World is 0)\nDISPNN\nstring(120)\n\nDisplay Name\nFRSTW\nelement\nword\nReference of first world of given DB type in current MDB\nGPPRXS\nelement(500)\n\nGroup proxy items referring to element\nGROUPS\nelement(500)\nelemtype, logical\nGPSETs in which element occurs\nLEVE\ninteger(2)\n\nDrawing level\nMAXD\ninteger\n\nDB hierarchy depth of lowest level item beneath element\nMBACK\nelement(10000)\nelemtype\nMembers in reverse order\nMCOU\ninteger\nelemtype\nNumber of Element Members of Given type\nMEMB\nelement(10000)\nelemtype\nAll members, or members of specific type\nMEMDAB\nelement(10000)\n\nDabacon members\nMHCOUNT\ninteger\nelemtype\nNumber of Elements of Given type\nMSGUID\nstring(160)\n\nUniversally unique identifier from external sources (in MS format)\nOWNER\nelement\n\nElement owner in database hierarchy\nOWNLST\nelement(100)\n\nOwning hierarchy\nPARENT\nelement\nelemtype\nReference of ascendant element of specified type\nQUAN\ninteger\n\nQuantity (always one!)\nSEQU\ninteger\n\nSequence Position in Member List\nSEXPND\nelement(10000)\n\nAll descendent elements in secondary hierarchy\nSITEM\nelement\n\nReference from secondary hierarchy\nSMEMB\nelement(10000)\n\nImmediate members in secondary hierarchy\n\nAttribute Name\nData Type\nQualifier\nDescription\nBACKRE\nelement(1000)\nattr\nList reftable back references\nCONNECTIONS\nelement(5000)\nConnections\nCONNECTIONSH\nelement(5000)\nConnections for all descendants\nCONNER\nstring(300)\ninteger\nConnection error message\nDDEP\ninteger\nDatabase depth within hierarchy (World is 0)\nDISPNN\nstring(120)\nDisplay Name\nFRSTW\nelement\nword\nReference of first world of given DB type in current MDB\nGPPRXS\nelement(500)\nGroup proxy items referring to element\nGROUPS\nelement(500)\nelemtype, logical\nGPSETs in which element occurs\nLEVE\ninteger(2)\nDrawing level\nMAXD\ninteger\nDB hierarchy depth of lowest level item beneath element\nMBACK\nelement(10000)\nelemtype\nMembers in reverse order\nMCOU\ninteger\nelemtype\nNumber of Element Members of Given type\nMEMB\nelement(10000)\nelemtype\nAll members, or members of specific type\nMEMDAB\nelement(10000)\nDabacon members\nMHCOUNT\ninteger\nelemtype\nNumber of Elements of Given type\nMSGUID\nstring(160)\nUniversally unique identifier from external sources (in MS format)\nOWNER\nelement\nElement owner in database hierarchy\nOWNLST\nelement(100)\nOwning hierarchy\nPARENT\nelement\nelemtype\nReference of ascendant element of specified type\nQUAN\ninteger\nQuantity (always one!)\nSEQU\ninteger\nSequence Position in Member List\nSEXPND\nelement(10000)\nAll descendent elements in secondary hierarchy\nSITEM\nelement\nReference from secondary hierarchy\nSMEMB\nelement(10000)\nImmediate members in secondary hierarchy\n\n\n"}
{"Headers": "Attribute Category: Datal Related", "Content": "DTLELE\nelement(5000)\n\nDatal Elements list\nDTLLIST\nword(2000)\n\nDatal Attributes List\n\nAttribute Name\nData Type\nQualifier\nDescription\nDTLELE\nelement(5000)\nDatal Elements list\nDTLLIST\nword(2000)\nDatal Attributes List\n\n\n"}
{"Headers": "Attribute Category: Dataset Related", "Content": "CDPL\nword(100)\n\nList of valid current design properties\nCDPR\nreal\nword\nCurrent design dataset property\nCFDP\nelement\nword\nCurrent design dataset property\nDEPD\nstring(250)\nword\nDefault value of local design property\nDEPL\nword(100)\n\nList of local design properties\nDEPR\nstring(250)\nword\nLocal design property value\nFDEPD\nstring(250)\nword\nFormatted Local Design Property Default Value\nFDEPR\nstring(250)\nword\nFormatted Local Design Property Value\nFPRDE\nstring(250)\nword\nFormatted property default\nFPROP\nstring(250)\nword\nFormatted property value from dataset\nFTCDD\nstring(250)\nword\nFormatted Current Design Property Default Value\nFTCDP\nstring(250)\nword\nFormatted Current Design Property Value\nLDPR\nreal\nword\nLocal design dataset property\nLFDP\nelement\nword\nLocal design dataset property\nPRDE\nstring(250)\nword\nProperty default\nPRDES\nstring(250)\nword\nProperty value from design\nPRLS\nword(200)\n\nList of valid properties - catalogue or design\nPROP\nstring(250)\nword\nProperty value from catalogue or design dataset\nPROPTYPE\nword\nword\nProperty Dimension from catalogue or design dataset\nPRPU\nword\nword\nProperty purpose\nPRTI\nstring(120)\nword\nProperty title\nRPRO\nreal\nword\nCatalogue dataset property\nTCDD\nstring(250)\nword\nCurrent design property default value\nTCDP\nstring(250)\nword\nCurrent design property value\nTDPR\nreal\nword\nTemplate design dataset property\nTFDP\nelement\nword\nTemplate design dataset property\n\nAttribute Name\nData Type\nQualifier\nDescription\nCDPL\nword(100)\nList of valid current design properties\nCDPR\nreal\nword\nCurrent design dataset property\nCFDP\nelement\nword\nCurrent design dataset property\nDEPD\nstring(250)\nword\nDefault value of local design property\nDEPL\nword(100)\nList of local design properties\nDEPR\nstring(250)\nword\nLocal design property value\nFDEPD\nstring(250)\nword\nFormatted Local Design Property Default Value\nFDEPR\nstring(250)\nword\nFormatted Local Design Property Value\nFPRDE\nstring(250)\nword\nFormatted property default\nFPROP\nstring(250)\nword\nFormatted property value from dataset\nFTCDD\nstring(250)\nword\nFormatted Current Design Property Default Value\nFTCDP\nstring(250)\nword\nFormatted Current Design Property Value\nLDPR\nreal\nword\nLocal design dataset property\nLFDP\nelement\nword\nLocal design dataset property\nPRDE\nstring(250)\nword\nProperty default\nPRDES\nstring(250)\nword\nProperty value from design\nPRLS\nword(200)\nList of valid properties - catalogue or design\nPROP\nstring(250)\nword\nProperty value from catalogue or design dataset\nPROPTYPE\nword\nword\nProperty Dimension from catalogue or design dataset\nPRPU\nword\nword\nProperty purpose\nPRTI\nstring(120)\nword\nProperty title\nRPRO\nreal\nword\nCatalogue dataset property\nTCDD\nstring(250)\nword\nCurrent design property default value\nTCDP\nstring(250)\nword\nCurrent design property value\nTDPR\nreal\nword\nTemplate design dataset property\nTFDP\nelement\nword\nTemplate design dataset property\n\n\n"}
{"Headers": "Attribute Category: Design Parameters", "Content": "ADESP\nreal(100)\n\nDesign parameters of attached element\nDDESP\nreal(100)\n\nDesign parameters as distance\nODESP\nreal(100)\n\nOwning design parameters\nWDESP\nword(100)\n\nDesign parameters as words\n\nAttribute Name\nData Type\nQualifier\nDescription\nADESP\nreal(100)\nDesign parameters of attached element\nDDESP\nreal(100)\nDesign parameters as distance\nODESP\nreal(100)\nOwning design parameters\nWDESP\nword(100)\nDesign parameters as words\n\n\n"}
{"Headers": "Attribute Category: Design Point Related", "Content": "DDIR\ndir\n\nDesign PPoint spherical direction\nDPBO\nreal\ninteger\nDesign point bore\nDPCO\nword\ninteger\nDesign point connection type\nDPCOU\ninteger\n\nNumber of valid design points\nDPDI\ndir\ninteger\nDesign point direction\nDPGR\nreal\ninteger\nDesign Point Gradient\nDPLS\ninteger(200)\n\nList of valid design points\nDPPS\npos\ninteger\nDesign point position\nDPVI\ninteger(200)\n\nList of visible design points\n\nAttribute Name\nData Type\nQualifier\nDescription\nDDIR\ndir\nDesign PPoint spherical direction\nDPBO\nreal\ninteger\nDesign point bore\nDPCO\nword\ninteger\nDesign point connection type\nDPCOU\ninteger\nNumber of valid design points\nDPDI\ndir\ninteger\nDesign point direction\nDPGR\nreal\ninteger\nDesign Point Gradient\nDPLS\ninteger(200)\nList of valid design points\nDPPS\npos\ninteger\nDesign point position\nDPVI\ninteger(200)\nList of visible design points\n\n\n"}
{"Headers": "Attribute Category: Detailing", "Content": "DGABRE\ninteger\n\nDetailing Graphic Measure Line Absolute relativ flag\nDGARLT\ninteger\n\nDetailing Graphic Arc Length Dimension type\nDGBAST\nreal\n\nTriangle Base Line\nDGCRAD\nreal\n\nDetailing Graphic Circle Radius\nDGDARK\ninteger\n\nDetailing Graphic Display Criteria\nDGDBED\nreal\n\nDrawback End Diameter\nDGDBGN\ninteger\n\nDetailing Graphic Group number\nDGDBSD\nreal\n\nDrawback Start Diameter\nDGELVT\nreal\n\nElevation Value\nDGEXB\nreal\n\nDetailing Graphic Distance to extension line begin\nDGEXE\nreal\n\nDetailing Graphic Distance to extension line end\nDGFCOL\ninteger\n\nDetailing Graphic Fill Color\nDGFILL\ninteger\n\nDetailing Graphic Fill flag\nDGFLTV\ninteger\n\nDetailing Graphic Line Pattern Number\nDGFONT\ninteger\n\nDetailing Graphic Font Number\nDGFPAD\nreal\n\nPattern Repeat Factor\nDGFPTY\ninteger\n\nPattern Type\nDGFRME\ninteger\n\nDetailing Graphic Text frame\nDGFSHA\nreal\n\nDetailing Graphic Shading Opacity\nDGGAD\nreal\n\nDetailing Graphic global angle direction\nDGISEA\ninteger\n\nAutomatic Placement\nDGITAL\nlogical\n\nDetailing Graphic Text Attribute Italics\nDGLAYN\ninteger\n\nDetailing Graphic Layer Number\nDGLCLO\ninteger\n\nClose Polyline\nDGLFIL\ninteger\n\nFill Polyline\nDGLLEN\ninteger(3)\n\nText Line Lengths\nDGLLIN\ninteger\n\nDetailing Graphic Multi-line Text Length\nDGLPFL\nreal\n\nDetailing Graphic Line pitch first line\nDGLPIA\nreal\n\nDetailing Graphic Line pitch absolute\nDGLSPA\nreal\n\nLine Spacing\nDGLTA\nreal\n\nDetailing Graphic Line termination angle\nDGLTIV\ninteger\n\nDetailing Graphic Line Type invisible\nDGLTL\nreal\n\nDetailing Graphic Line termination length\nDGLTSB\ninteger\n\nDetailing Graphic Line termination begin\nDGLTSE\ninteger\n\nDetailing Graphic Line termination end\nDGLTVI\ninteger\n\nDetailing Graphic Visible Line Type number\nDGLVSD\ninteger\n\nLevel Symbol Docking\nDGLVST\ninteger\n\nLevel Symbol Type\nDGMALI\nlogical\n\nDetailing Graphic mark line flag\nDGMATT\ninteger\n\nDetailing Graphic Measure Line Text type\nDGMLAT\ninteger\n\nDetailing Graphic Angle Measure Line type\nDGMLL\nreal\n\nDetailing Graphic Marker Line Length\nDGMTRL\nreal\n\nDetailing Graphic Triangle Measure Line length\nDGMTRT\ninteger\n\nDetailing Graphic Triangle Measure Line type\nDGNLIN\ninteger\n\nNumber of Lines\nDGOLIN\ninteger\n\nNumber of Lines above Marker\nDGORAN\nreal\n\nOrientation Angle\nDGPAAN\nreal\n\nPattern Angle\nDGPACK\ninteger\n\nDetailing Graphic Packed Word\nDGPATT\ninteger\n\nDetailing Graphic Line Pattern repeat factor\nDGPDDR\nelement(100)\n\nReference to DGPDD Element\nDGPEN\ninteger\n\nDetailing Graphic Dimension Pen\nDGPIV\ninteger\n\nDetailing Graphic Pen invisible\nDGPVI\ninteger\n\nDetailing Graphic Pen visible\nDGRADI\nreal(32)\n\nList of radius\nDGRDP\ninteger\n\nDetailing Graphic Radius dimension position\nDGRDT\ninteger\n\nDetailing Graphic Radius dimension type\nDGSCAL\nreal\n\nScaling Factor\nDGSEGT\ninteger\n\nDetailing Graphic Segment Type\nDGSHAD\ninteger\n\nShading\nDGSMH\nreal\n\nDetailing Graphic Sm_Sysm height\nDGSMW\nreal\n\nDetailing Graphic Sm_Sysm width\nDGTALI\ninteger\n\nDetailing Graphic text alignment\nDGTANG\nreal\n\nDetailing Graphic text angle\nDGTATB\ninteger\n\nDetailing Graphic Text Attribute\nDGTCOL\ninteger\n\nDetailing Graphic Text Color\nDGTPLP\ninteger\n\nText Position on Level Point\nDGTPOS\ninteger\n\nDetailing Graphic Text position\nDGTTOM\ninteger\n\nDetailing Graphic text position related to mark out point\nDGTXAN\ninteger\n\nDetailing Graphic Text Anchor\nDGTXB\nreal\n\nDetailing Graphic Distance to text begin\nDGTXE\nreal\n\nDetailing Graphic Distance to text end\nDGTXLI\ninteger\n\nDetailing Graphic Flag for the lift of the last decimal number\nDGTXRF\nelement(100)\n\nReference to DTTXTS Element\nDGTXST\ninteger\n\nDetailing Graphic Text Attribute style\nDGTXT\nstring(80)\n\nDisplay Text\nDGTYPE\ninteger\n\nDetailing Graphic Type\nDGUSOF\nreal\n\nDetailing Graphic underscore offset\nDGWCIR\ninteger\n\nGirth Weld Flag\nDGWFLG\ninteger\n\nShop Weld Flag\nDGWNTX\ninteger\n\nNumber of Weld Spec Texts\nDGWNUM\ninteger\n\nNumber of Waves\nDGWSCA\nreal\n\nZ3 Window Scale\nDGWSLS\ninteger\n\nDetailing Graphic Welding Symbol Left side flag\nDGWSOS\ninteger\n\nDetailing Graphic Welding Symbol Other side flag\nDGWSSN\ninteger\n\nDetailing Graphic Welding Symbol Number\nDGZART\ninteger\n\nDetailing Graphic Drawing Type\nDTADHO\ninteger\n\nBolting: Additional hole type\nDTADPU\ninteger\n\nBolting Centre Punch Type\nDTAREA\nreal\n\nArea\nDTAUTW\ninteger\n\nClamping Length Balancing Mode\nDTBCKD\ndatetime(2)\n\nDetailing Job Backup Date\nDTBNAM\nstring(32)\n\nDetailing Model Bolt Name\nDTBNDB\nstring(32)\n\nDetailing Model Bolt Name for Database\nDTBNDR\nstring(32)\n\nDetailing Model Bolt Name for Drawings\nDTCATR\nstring(10)\n\nBolt Set Component Catalogue Numbers\nDTCDAT\ndatetime(2)\n\nDetailing Drawing Creation Date\nDTCITY\nstring(80)\n\nDetailing Address City\nDTCLMA\nreal\n\nBolt Clamping Length (maximum)\nDTCLMI\nreal\n\nBolt Clamping Length (minimum)\nDTCLML\nreal\n\nBolt Clamping Length (calculated)\nDTCLWA\nreal\n\nBolting Washer Clearance\nDTCNTY\nstring(80)\n\nDetailing Address Country\nDTCOGC\nreal(3)\n\nCentre of Gravity\nDTCSAG\nreal\n\nSink Hole Angle\nDTCSDA\nreal\n\nSink Hole Diameter 1\nDTCSDB\nreal\n\nSink Hole Diameter 2\nDTCSDC\nreal\n\nSink Hole Diameter 3\nDTCSHD\nreal\n\nSink Hole Dimension Head\nDTCSIV\nlogical\n\nCountersunk Bolt\nDTCSNU\nreal\n\nSink Hole Dimension Nut\nDTCTLN\nreal\n\nDetailing Item Cut Length\nDTDLIM\nlogical\n\nBlind Hole Bolt\nDTDMAT\nlogical\n\nClamp Length Calculation Flag\nDTENVA\nreal\n\nEnveloping Area\nDTFTHK\nreal\n\nDetailing Element Flange Thickness\nDTGATT\nreal(10)\n\nDetailing Model Attributes Real part\nDTGCOG\nreal(3)\n\nGross Centre of Gravity\nDTGNIF\ninteger\n\nBolt Hole Orientation Mode\nDTGRADE\nstring(32)\n\nDetailing Material Grade\nDTHDHE\nreal\n\nBolt Header Height\nDTHEIG\nreal\n\nDetailing Element Height\nDTHOTY\ninteger\n\nBolting Hole Type\nDTLNAM\nreal\n\nDetailing Item Length after Marking\nDTLNGE\nreal\n\nDetailing Item generated Length\nDTMDFD\nstring(19)\n\nModified Date/Time\nDTMDST\ndatetime(2)\n\nModification Date\nDTMFST\ndatetime(2)\n\nManufacturing Status Date\nDTMIND\ninteger\n\nBolt Connection Processing Mode\nDTMKST\nstring(80)\n\nMarking Status\nDTMTYP\ninteger\n\nM3 Connection Type\nDTNUMB\ninteger\n\nDetailing Model Element ident number\nDTOHDD\nreal\n\nOutside Bolt Header Diameter\nDTOPOS\ninteger\n\nDetailing Element Order Item Number\nDTPARE\nreal\n\nPlane Area\nDTPROT\nreal\n\nBolt Protrusion\nDTPTAR\nreal(1000)\n\nPoints: [0]=x ; [1]=y ; means max 500 points\nDTPUNI\ninteger\n\nBolt Packing Unit\nDTRADA\nreal\n\nDetailing Element Fillet Radius 1\nDTRADB\nreal\n\nDetailing Element Fillet Radius 2\nDTRADC\nreal\n\nDetailing Element Fillet Radius 3\nDTRDAT\nreal(100)\n\nDetailing Model Attributes Real part\nDTROOA\nreal\n\nDetailing Element Root Dimension 1\nDTROOB\nreal\n\nDetailing Element Root Dimension 2\nDTROOC\nreal\n\nDetailing Element Root Dimension 3\nDTRSUF\nreal\n\nReal Surface\nDTRUSF\nreal\n\nRough Surface\nDTRUWG\nreal\n\nRough Weight\nDTRWGH\nreal\n\nREALWeight\nDTRWHG\nreal\n\nDetailing Element Remaining Webbing Height\nDTSAAS\nreal\n\nDetailing weld throat depth (arrow side)\nDTSAOS\nreal\n\nDetailing weld throat depth other side\nDTSCAN\nlogical\n\nBolt Hole Investigation Flag\nDTSEFL\ninteger(100)\n\nDetailing Model Relation Secondaries Flags\nDTSKEY\nstring(32)\n\nBolt Standard Key\nDTSMAT\nlogical\n\nInclude Bolt Mounting Material\nDTSNUM\ninteger\n\nSection number (cladding)\nDTSPOS\ninteger\n\nStart number for marking\nDTSTAT\ninteger\n\nDetailing Element Status\nDTSTYP\ninteger\n\nDetailing Element Shape Type Code\nDTSURF\nstring(32)\n\nDetailing Surface Treatment\nDTTAPE\ninteger\n\nTapered Washer Mode\nDTTCNT\ninteger\n\nDetailing Element Total Count\nDTTLNU\ninteger\n\nNumber of truck load\nDTTOTL\nreal\n\nTotal Bolt Length\nDTTSNR\ninteger\n\nDetailing Element Phase Number\nDTTXNX\ninteger\n\nFabrication model element text sequence number\nDTTXRF\nelement(100)\n\nBocad Detailing Text Reference\nDTUARE\nreal\n\nRubber Band Area\nDTUKST\ndatetime(2)\n\nDocumentation ID Date\nDTUNIT\ninteger\n\nBolt Dimension Units\nDTVBKY\nstring(32)\n\nBolt Fastener Table Key\nDTVIDD\nlogical\n\nBolt always as 3D body\nDTVOLF\nreal\n\nVolume3D M\nDTVOLR\nreal\n\nVolume3D R\nDTWGHT\nreal\n\nWeight\nDTWIDT\nreal\n\nDetailing Element Width\nDTWSIZ\nreal\n\nBolt Header Wrench Size\nDTWTHK\nreal\n\nDetailing Element Webbing Thickness\nDTXVEC\ndir\n\nDetailing View Volume X-Axis\nDTYVEC\ndir\n\nDetailing View Volume Y-Axis\nDTZGRD\nelement\n\nDetailing Zone Primary Grid\nDTZNUM\ninteger\n\nBocad Detailing Zone Number\nDTZPLN\nelement\n\nDetailing Zone View Volume\nDTZPOS\nreal\n\nZ Offset of the view plane\nDTZVEC\ndir\n\nDetailing View Volume Z-Axis\nFSPMNU\ninteger\n\nFactory Standard Part Mark Number\n\nAttribute Name\nData Type\nQualifier\nDescription\nDGABRE\ninteger\nDetailing Graphic Measure Line Absolute relativ flag\nDGARLT\ninteger\nDetailing Graphic Arc Length Dimension type\nDGBAST\nreal\nTriangle Base Line\nDGCRAD\nreal\nDetailing Graphic Circle Radius\nDGDARK\ninteger\nDetailing Graphic Display Criteria\nDGDBED\nreal\nDrawback End Diameter\nDGDBGN\ninteger\nDetailing Graphic Group number\nDGDBSD\nreal\nDrawback Start Diameter\nDGELVT\nreal\nElevation Value\nDGEXB\nreal\nDetailing Graphic Distance to extension line begin\nDGEXE\nreal\nDetailing Graphic Distance to extension line end\nDGFCOL\ninteger\nDetailing Graphic Fill Color\nDGFILL\ninteger\nDetailing Graphic Fill flag\nDGFLTV\ninteger\nDetailing Graphic Line Pattern Number\nDGFONT\ninteger\nDetailing Graphic Font Number\nDGFPAD\nreal\nPattern Repeat Factor\nDGFPTY\ninteger\nPattern Type\nDGFRME\ninteger\nDetailing Graphic Text frame\nDGFSHA\nreal\nDetailing Graphic Shading Opacity\nDGGAD\nreal\nDetailing Graphic global angle direction\nDGISEA\ninteger\nAutomatic Placement\nDGITAL\nlogical\nDetailing Graphic Text Attribute Italics\nDGLAYN\ninteger\nDetailing Graphic Layer Number\nDGLCLO\ninteger\nClose Polyline\nDGLFIL\ninteger\nFill Polyline\nDGLLEN\ninteger(3)\nText Line Lengths\nDGLLIN\ninteger\nDetailing Graphic Multi-line Text Length\nDGLPFL\nreal\nDetailing Graphic Line pitch first line\nDGLPIA\nreal\nDetailing Graphic Line pitch absolute\nDGLSPA\nreal\nLine Spacing\nDGLTA\nreal\nDetailing Graphic Line termination angle\nDGLTIV\ninteger\nDetailing Graphic Line Type invisible\nDGLTL\nreal\nDetailing Graphic Line termination length\nDGLTSB\ninteger\nDetailing Graphic Line termination begin\nDGLTSE\ninteger\nDetailing Graphic Line termination end\nDGLTVI\ninteger\nDetailing Graphic Visible Line Type number\nDGLVSD\ninteger\nLevel Symbol Docking\nDGLVST\ninteger\nLevel Symbol Type\nDGMALI\nlogical\nDetailing Graphic mark line flag\nDGMATT\ninteger\nDetailing Graphic Measure Line Text type\nDGMLAT\ninteger\nDetailing Graphic Angle Measure Line type\nDGMLL\nreal\nDetailing Graphic Marker Line Length\nDGMTRL\nreal\nDetailing Graphic Triangle Measure Line length\nDGMTRT\ninteger\nDetailing Graphic Triangle Measure Line type\nDGNLIN\ninteger\nNumber of Lines\nDGOLIN\ninteger\nNumber of Lines above Marker\nDGORAN\nreal\nOrientation Angle\nDGPAAN\nreal\nPattern Angle\nDGPACK\ninteger\nDetailing Graphic Packed Word\nDGPATT\ninteger\nDetailing Graphic Line Pattern repeat factor\nDGPDDR\nelement(100)\nReference to DGPDD Element\nDGPEN\ninteger\nDetailing Graphic Dimension Pen\nDGPIV\ninteger\nDetailing Graphic Pen invisible\nDGPVI\ninteger\nDetailing Graphic Pen visible\nDGRADI\nreal(32)\nList of radius\nDGRDP\ninteger\nDetailing Graphic Radius dimension position\nDGRDT\ninteger\nDetailing Graphic Radius dimension type\nDGSCAL\nreal\nScaling Factor\nDGSEGT\ninteger\nDetailing Graphic Segment Type\nDGSHAD\ninteger\nShading\nDGSMH\nreal\nDetailing Graphic Sm_Sysm height\nDGSMW\nreal\nDetailing Graphic Sm_Sysm width\nDGTALI\ninteger\nDetailing Graphic text alignment\nDGTANG\nreal\nDetailing Graphic text angle\nDGTATB\ninteger\nDetailing Graphic Text Attribute\nDGTCOL\ninteger\nDetailing Graphic Text Color\nDGTPLP\ninteger\nText Position on Level Point\nDGTPOS\ninteger\nDetailing Graphic Text position\nDGTTOM\ninteger\nDetailing Graphic text position related to mark out point\nDGTXAN\ninteger\nDetailing Graphic Text Anchor\nDGTXB\nreal\nDetailing Graphic Distance to text begin\nDGTXE\nreal\nDetailing Graphic Distance to text end\nDGTXLI\ninteger\nDetailing Graphic Flag for the lift of the last decimal number\nDGTXRF\nelement(100)\nReference to DTTXTS Element\nDGTXST\ninteger\nDetailing Graphic Text Attribute style\nDGTXT\nstring(80)\nDisplay Text\nDGTYPE\ninteger\nDetailing Graphic Type\nDGUSOF\nreal\nDetailing Graphic underscore offset\nDGWCIR\ninteger\nGirth Weld Flag\nDGWFLG\ninteger\nShop Weld Flag\nDGWNTX\ninteger\nNumber of Weld Spec Texts\nDGWNUM\ninteger\nNumber of Waves\nDGWSCA\nreal\nZ3 Window Scale\nDGWSLS\ninteger\nDetailing Graphic Welding Symbol Left side flag\nDGWSOS\ninteger\nDetailing Graphic Welding Symbol Other side flag\nDGWSSN\ninteger\nDetailing Graphic Welding Symbol Number\nDGZART\ninteger\nDetailing Graphic Drawing Type\nDTADHO\ninteger\nBolting: Additional hole type\nDTADPU\ninteger\nBolting Centre Punch Type\nDTAREA\nreal\nArea\nDTAUTW\ninteger\nClamping Length Balancing Mode\nDTBCKD\ndatetime(2)\nDetailing Job Backup Date\nDTBNAM\nstring(32)\nDetailing Model Bolt Name\nDTBNDB\nstring(32)\nDetailing Model Bolt Name for Database\nDTBNDR\nstring(32)\nDetailing Model Bolt Name for Drawings\nDTCATR\nstring(10)\nBolt Set Component Catalogue Numbers\nDTCDAT\ndatetime(2)\nDetailing Drawing Creation Date\nDTCITY\nstring(80)\nDetailing Address City\nDTCLMA\nreal\nBolt Clamping Length (maximum)\nDTCLMI\nreal\nBolt Clamping Length (minimum)\nDTCLML\nreal\nBolt Clamping Length (calculated)\nDTCLWA\nreal\nBolting Washer Clearance\nDTCNTY\nstring(80)\nDetailing Address Country\nDTCOGC\nreal(3)\nCentre of Gravity\nDTCSAG\nreal\nSink Hole Angle\nDTCSDA\nreal\nSink Hole Diameter 1\nDTCSDB\nreal\nSink Hole Diameter 2\nDTCSDC\nreal\nSink Hole Diameter 3\nDTCSHD\nreal\nSink Hole Dimension Head\nDTCSIV\nlogical\nCountersunk Bolt\nDTCSNU\nreal\nSink Hole Dimension Nut\nDTCTLN\nreal\nDetailing Item Cut Length\nDTDLIM\nlogical\nBlind Hole Bolt\nDTDMAT\nlogical\nClamp Length Calculation Flag\nDTENVA\nreal\nEnveloping Area\nDTFTHK\nreal\nDetailing Element Flange Thickness\nDTGATT\nreal(10)\nDetailing Model Attributes Real part\nDTGCOG\nreal(3)\nGross Centre of Gravity\nDTGNIF\ninteger\nBolt Hole Orientation Mode\nDTGRADE\nstring(32)\nDetailing Material Grade\nDTHDHE\nreal\nBolt Header Height\nDTHEIG\nreal\nDetailing Element Height\nDTHOTY\ninteger\nBolting Hole Type\nDTLNAM\nreal\nDetailing Item Length after Marking\nDTLNGE\nreal\nDetailing Item generated Length\nDTMDFD\nstring(19)\nModified Date/Time\nDTMDST\ndatetime(2)\nModification Date\nDTMFST\ndatetime(2)\nManufacturing Status Date\nDTMIND\ninteger\nBolt Connection Processing Mode\nDTMKST\nstring(80)\nMarking Status\nDTMTYP\ninteger\nM3 Connection Type\nDTNUMB\ninteger\nDetailing Model Element ident number\nDTOHDD\nreal\nOutside Bolt Header Diameter\nDTOPOS\ninteger\nDetailing Element Order Item Number\nDTPARE\nreal\nPlane Area\nDTPROT\nreal\nBolt Protrusion\nDTPTAR\nreal(1000)\nPoints: [0]=x ; [1]=y ; means max 500 points\nDTPUNI\ninteger\nBolt Packing Unit\nDTRADA\nreal\nDetailing Element Fillet Radius 1\nDTRADB\nreal\nDetailing Element Fillet Radius 2\nDTRADC\nreal\nDetailing Element Fillet Radius 3\nDTRDAT\nreal(100)\nDetailing Model Attributes Real part\nDTROOA\nreal\nDetailing Element Root Dimension 1\nDTROOB\nreal\nDetailing Element Root Dimension 2\nDTROOC\nreal\nDetailing Element Root Dimension 3\nDTRSUF\nreal\nReal Surface\nDTRUSF\nreal\nRough Surface\nDTRUWG\nreal\nRough Weight\nDTRWGH\nreal\nREALWeight\nDTRWHG\nreal\nDetailing Element Remaining Webbing Height\nDTSAAS\nreal\nDetailing weld throat depth (arrow side)\nDTSAOS\nreal\nDetailing weld throat depth other side\nDTSCAN\nlogical\nBolt Hole Investigation Flag\nDTSEFL\ninteger(100)\nDetailing Model Relation Secondaries Flags\nDTSKEY\nstring(32)\nBolt Standard Key\nDTSMAT\nlogical\nInclude Bolt Mounting Material\nDTSNUM\ninteger\nSection number (cladding)\nDTSPOS\ninteger\nStart number for marking\nDTSTAT\ninteger\nDetailing Element Status\nDTSTYP\ninteger\nDetailing Element Shape Type Code\nDTSURF\nstring(32)\nDetailing Surface Treatment\nDTTAPE\ninteger\nTapered Washer Mode\nDTTCNT\ninteger\nDetailing Element Total Count\nDTTLNU\ninteger\nNumber of truck load\nDTTOTL\nreal\nTotal Bolt Length\nDTTSNR\ninteger\nDetailing Element Phase Number\nDTTXNX\ninteger\nFabrication model element text sequence number\nDTTXRF\nelement(100)\nBocad Detailing Text Reference\nDTUARE\nreal\nRubber Band Area\nDTUKST\ndatetime(2)\nDocumentation ID Date\nDTUNIT\ninteger\nBolt Dimension Units\nDTVBKY\nstring(32)\nBolt Fastener Table Key\nDTVIDD\nlogical\nBolt always as 3D body\nDTVOLF\nreal\nVolume3D M\nDTVOLR\nreal\nVolume3D R\nDTWGHT\nreal\nWeight\nDTWIDT\nreal\nDetailing Element Width\nDTWSIZ\nreal\nBolt Header Wrench Size\nDTWTHK\nreal\nDetailing Element Webbing Thickness\nDTXVEC\ndir\nDetailing View Volume X-Axis\nDTYVEC\ndir\nDetailing View Volume Y-Axis\nDTZGRD\nelement\nDetailing Zone Primary Grid\nDTZNUM\ninteger\nBocad Detailing Zone Number\nDTZPLN\nelement\nDetailing Zone View Volume\nDTZPOS\nreal\nZ Offset of the view plane\nDTZVEC\ndir\nDetailing View Volume Z-Axis\nFSPMNU\ninteger\nFactory Standard Part Mark Number\n\n\n"}
{"Headers": "Attribute Category: Dictionary", "Content": "DFLT\nstring(500)\n\nDefault value for the attribute\nLDFLT\nlogical\n\nlogical default value for a UDA\nNDFLT\nreal\n\nNumeric default value for a UDA\nUDNA\nstring(120)\n\nUser defined name\nUKEYFR\ninteger\n\nNumber of free UKey values available\n\nAttribute Name\nData Type\nQualifier\nDescription\nDFLT\nstring(500)\nDefault value for the attribute\nLDFLT\nlogical\nlogical default value for a UDA\nNDFLT\nreal\nNumeric default value for a UDA\nUDNA\nstring(120)\nUser defined name\nUKEYFR\ninteger\nNumber of free UKey values available\n\n\n"}
{"Headers": "Attribute Category: Distributed Attributes Related", "Content": "DFHOME\nelement\nelement, elemtype\nGet default home element\nXRLIST\nelement(10000)\nelemtype\nList distributed attributes\nXRLSTT\nword(2000)\nelemtype\nList distributed attributes\nXRQCNT\ninteger\nelemtype\nGet distributed attributes element count\nXRQELE\nelement\nelemtype, integer\nGet distributed attributes element\n\nAttribute Name\nData Type\nQualifier\nDescription\nDFHOME\nelement\nelement, elemtype\nGet default home element\nXRLIST\nelement(10000)\nelemtype\nList distributed attributes\nXRLSTT\nword(2000)\nelemtype\nList distributed attributes\nXRQCNT\ninteger\nelemtype\nGet distributed attributes element count\nXRQELE\nelement\nelemtype, integer\nGet distributed attributes element\n\n\n"}
{"Headers": "Attribute Category: Draft & Schematic Drawing-File Related", "Content": "DOFIL\nstring(73)\n\nDrawing Object filename\nDRFILE\nstring(73)\n\nDrawing File Name\nDRFNUM\ninteger(21)\n\nDrawing File Numbers\nDRFTYP\ninteger(21)\n\nDrawing File Types\nISLOADED\nlogical\n\nTrue if Sheet is loaded\nISPICF\nlogical\n\nPicture has File\nPICF\nstring(73)\n\nPicture filename\nPICHTY\nword\n\nHard type of picture\nPICSTY\nword\n\nSoft type of picture\n\nAttribute Name\nData Type\nQualifier\nDescription\nDOFIL\nstring(73)\nDrawing Object filename\nDRFILE\nstring(73)\nDrawing File Name\nDRFNUM\ninteger(21)\nDrawing File Numbers\nDRFTYP\ninteger(21)\nDrawing File Types\nISLOADED\nlogical\nTrue if Sheet is loaded\nISPICF\nlogical\nPicture has File\nPICF\nstring(73)\nPicture filename\nPICHTY\nword\nHard type of picture\nPICSTY\nword\nSoft type of picture\n\n\n"}
{"Headers": "Attribute Category: Draft Colour Related", "Content": "BFCONU\ninteger\n\nBackface colour number\nBOCONU\ninteger\n\nObscured Backface colour number\nCHCONU\ninteger\n\nCrosshairs colour number\nCLCONU\ninteger\n\nCentreline colour number\nCLMRGB\ninteger(4)\n\nRGB column colour\nCLNRGB\ninteger(4)\n\nRGB centreline colour\nCOLCON\ninteger\n\nColumn colour number\nCOLRGB\ninteger(4)\n\nRGB colour\nDLCONU\ninteger\n\nDimension line colour number\nDTCONU\ninteger\n\nDimension text colour number\nFCONUM\ninteger\n\nFill colour number\nFFCONU\ninteger\n\nFront-face colour number\nFFCRGB\ninteger(4)\n\nRGB front face colour\nFILRGB\ninteger(4)\n\nRGB fill colour\nLFCONU\ninteger\n\nLabel frame colour number\nLLCONU\ninteger\n\nLabel leader colour number\nMCONUM\ninteger\n\nMarker colour number\nMLNCON\ninteger\n\nMember-line colour number\nNLCONU\ninteger\n\nNote colour number\nOBCONU\ninteger\n\nObscured face colour number\nOCCONU\ninteger\n\nObscured Centreline colour number\nOLCONU\ninteger\n\nOutline colour number\nPAFRGB\ninteger(4)\n\nRGB plot action from colour\nPATRGB\ninteger(4)\n\nRGB plot action to colour\nPICRGB\ninteger(4)\n\nRGB picture current colour\nPINRGB\ninteger(4)\n\nRGB pipe insulation colour\nPINSCN\ninteger\n\nPipe Insulation colour number\nPLCONU\ninteger\n\nProjection line colour number\nPLNCON\ninteger\n\nPline colour number\nPTCONU\ninteger\n\nProjection text colour number\nROWCON\ninteger\n\nRow colour number\nTXCONU\ninteger\n\nText colour number\n\nAttribute Name\nData Type\nQualifier\nDescription\nBFCONU\ninteger\nBackface colour number\nBOCONU\ninteger\nObscured Backface colour number\nCHCONU\ninteger\nCrosshairs colour number\nCLCONU\ninteger\nCentreline colour number\nCLMRGB\ninteger(4)\nRGB column colour\nCLNRGB\ninteger(4)\nRGB centreline colour\nCOLCON\ninteger\nColumn colour number\nCOLRGB\ninteger(4)\nRGB colour\nDLCONU\ninteger\nDimension line colour number\nDTCONU\ninteger\nDimension text colour number\nFCONUM\ninteger\nFill colour number\nFFCONU\ninteger\nFront-face colour number\nFFCRGB\ninteger(4)\nRGB front face colour\nFILRGB\ninteger(4)\nRGB fill colour\nLFCONU\ninteger\nLabel frame colour number\nLLCONU\ninteger\nLabel leader colour number\nMCONUM\ninteger\nMarker colour number\nMLNCON\ninteger\nMember-line colour number\nNLCONU\ninteger\nNote colour number\nOBCONU\ninteger\nObscured face colour number\nOCCONU\ninteger\nObscured Centreline colour number\nOLCONU\ninteger\nOutline colour number\nPAFRGB\ninteger(4)\nRGB plot action from colour\nPATRGB\ninteger(4)\nRGB plot action to colour\nPICRGB\ninteger(4)\nRGB picture current colour\nPINRGB\ninteger(4)\nRGB pipe insulation colour\nPINSCN\ninteger\nPipe Insulation colour number\nPLCONU\ninteger\nProjection line colour number\nPLNCON\ninteger\nPline colour number\nPTCONU\ninteger\nProjection text colour number\nROWCON\ninteger\nRow colour number\nTXCONU\ninteger\nText colour number\n\n\n"}
{"Headers": "Attribute Category: Draft Dimension and Annotation", "Content": "AGATYPE\nstring(120)\n\nAuto Grid Annotation Type (as text)\nAGDCLOSED\nstring(120)\n\nAuto Grid Annotation Closed Dimensions (as text)\nAGDOFFSET\nstring(80)\n\nAuto Grid Annotation Dimension Offset\nAGDOOFFSET\nstring(80)\n\nAuto Grid Annotation Overall Dimension Offset\nAGDOVR\nstring(120)\n\nAuto Grid Annotation Overall Dimensions (as text)\nAGDVRT\nstring(120)\n\nAuto Grid Annotation Vertical Dimensions (as text)\nAGLOFFSET\nstring(80)\n\nAuto Grid Annotation Label offset\nAGMODE\nstring(120)\n\nAuto Grid Annotation Mode (as text)\nAGSIDE\nstring(120)\n\nAuto Grid Annotation Sides\nAPOFTX\nstring(80)\n\nLeaderline attachment point text\nBPOFTX\nstring(80)\n\nLeader bend point offset text\nCHCRGB\ninteger(4)\n\nRGB dimension crosshairs colour\nCHEITX\nstring(80)\n\nCharacter height text\nCHOSTX\nstring(80)\n\nCrosshairs overshoot text\nCONERF\nelement\n\nConnection End Ref\nCONSRF\nelement\n\nConnection Start Ref\nCPOFTX\nstring(80)\n\nLeaderline connection point text\nCSPATX\nstring(80)\n\nCharacter spacing factor (as text)\nCTXTPS\nstring(120)\n\nConnector Text Position (as text)\nDDEGTX\nstring(80)\n\nRadial dimension angle text\nDLCNTMODE\nstring(20)\n\nDimension line continuous mode (as text)\nDLNRGB\ninteger(4)\n\nRGB dimension line colour\nDMSPTX\nstring(80)\n\nDimension spacing text\nDPOFF\nreal\n\nDimension point offset\nDTCHTX\nstring(80)\n\nDim text char height text\nDTERID\ninteger\n\nDimension terminator ID\nDTLHTX\nstring(80)\n\nDimension text letter height text\nDTOFTX\nstring(80)\n\nDimension text offset text\nDTRATX\nstring(80)\n\nDimension text radius text\nDTXRGB\ninteger(4)\n\nRGB dimension text colour\nELEVAT\nreal\n\nElevation\nFTERID\ninteger\n\nFirst terminator ID\nGBOXTX\nstring(80)\n\nBox gap text\nLFGRGB\ninteger(4)\n\nRGB glabel style frame colour\nLFRRGB\ninteger(4)\n\nRGB label frame colour\nLHEITX\nstring(80)\n\nLetter height text\nLLCLTX\nstring(80)\n\nLeader line clearance text\nLLGRGB\ninteger(4)\n\nRGB glabel style leader colour\nLLNRGB\ninteger(4)\n\nRGB leader line colour\nLOCRGB\ninteger(4)\n\nLoop RGB colour\nLSPATX\nstring(80)\n\nText line spacing factor (as text)\nLTERID\ninteger\n\nLabel terminator ID\nMLNRGB\ninteger(4)\n\nRGB member line colour\nMRKRGB\ninteger(4)\n\nRGB marker colour\nMTLCHE\nstring(80)\n\nMatchline text character height as text\nMTLLST\ninteger\n\nMatchline linestyle\nMTLRGB\ninteger(4)\n\nRGB matchline colour\nMTTRGB\ninteger(4)\n\nRGB matchline text colour\nNPPT\ninteger\n\nPpoint number\nOBFRGB\ninteger(4)\n\nRGB obscured face colour\nOCCOLO\ninteger\n\nCentreline and Obscured face colour\nOCCRGB\ninteger(4)\n\nObscured Centreline RGB colour\nOCSTYL\ninteger\n\nCentreline and Obscured face Style\nOLNRGB\ninteger(4)\n\nRGB outline colour\nOSHTTX\nstring(80)\n\nOvershoot text\nPKDI\nreal\n\nProportional distance along Pline\nPLCLTX\nstring(80)\n\nProjection line clearance text\nPLCRGB\ninteger(4)\n\nRGB projection line colour\nPLNRGB\ninteger(4)\n\nRGB pline colour\nPLSPTX\nstring(80)\n\nProj line text line-spacing text\nPRBMAR\nreal\n\nPrimitive blanking margin\nPRBMTX\nstring(80)\n\nPrimitive blanking margin text\nPTCHTX\nstring(80)\n\nProj text char height text\nPTLHTX\nstring(80)\n\nProjection text letter height text\nPTOFTX\nstring(80)\n\nProjection line text offset text\nPTXRGB\ninteger(4)\n\nRGB projection text colour\nRLTRGB\ninteger(4)\n\nRGB ruler long tick colour\nRMTRGB\ninteger(4)\n\nRGB ruler medium tick colour\nROWRGB\ninteger(4)\n\nRGB row colour\nRSTRGB\ninteger(4)\n\nRGB ruler short tick colour\nSCALAX\nstring(120)\n\nSymbol Scale Axis (as text)\nSMBFLG\nstring(120)\n\nSymbol extensible flag (as text)\nSYMCNA\nelement(1000)\n\nSymbol Connection Array\nTRUNTX\nstring(80)\n\nTruncation value (+ve) or percentage (-ve) text\nTSIZTX\nstring(80)\n\nTerminator size text\nTXGRGB\ninteger(4)\n\nRGB glabel style text colour\nTXTRGB\ninteger(4)\n\nRGB text colour\nVFRLST\ninteger\n\nView frame linestyle\nVFRRGB\ninteger(4)\n\nRGB view frame colour\nVSIRGB\ninteger(4)\n\nRGB view Section Indicator colour\n\nAttribute Name\nData Type\nQualifier\nDescription\nAGATYPE\nstring(120)\nAuto Grid Annotation Type (as text)\nAGDCLOSED\nstring(120)\nAuto Grid Annotation Closed Dimensions (as text)\nAGDOFFSET\nstring(80)\nAuto Grid Annotation Dimension Offset\nAGDOOFFSET\nstring(80)\nAuto Grid Annotation Overall Dimension Offset\nAGDOVR\nstring(120)\nAuto Grid Annotation Overall Dimensions (as text)\nAGDVRT\nstring(120)\nAuto Grid Annotation Vertical Dimensions (as text)\nAGLOFFSET\nstring(80)\nAuto Grid Annotation Label offset\nAGMODE\nstring(120)\nAuto Grid Annotation Mode (as text)\nAGSIDE\nstring(120)\nAuto Grid Annotation Sides\nAPOFTX\nstring(80)\nLeaderline attachment point text\nBPOFTX\nstring(80)\nLeader bend point offset text\nCHCRGB\ninteger(4)\nRGB dimension crosshairs colour\nCHEITX\nstring(80)\nCharacter height text\nCHOSTX\nstring(80)\nCrosshairs overshoot text\nCONERF\nelement\nConnection End Ref\nCONSRF\nelement\nConnection Start Ref\nCPOFTX\nstring(80)\nLeaderline connection point text\nCSPATX\nstring(80)\nCharacter spacing factor (as text)\nCTXTPS\nstring(120)\nConnector Text Position (as text)\nDDEGTX\nstring(80)\nRadial dimension angle text\nDLCNTMODE\nstring(20)\nDimension line continuous mode (as text)\nDLNRGB\ninteger(4)\nRGB dimension line colour\nDMSPTX\nstring(80)\nDimension spacing text\nDPOFF\nreal\nDimension point offset\nDTCHTX\nstring(80)\nDim text char height text\nDTERID\ninteger\nDimension terminator ID\nDTLHTX\nstring(80)\nDimension text letter height text\nDTOFTX\nstring(80)\nDimension text offset text\nDTRATX\nstring(80)\nDimension text radius text\nDTXRGB\ninteger(4)\nRGB dimension text colour\nELEVAT\nreal\nElevation\nFTERID\ninteger\nFirst terminator ID\nGBOXTX\nstring(80)\nBox gap text\nLFGRGB\ninteger(4)\nRGB glabel style frame colour\nLFRRGB\ninteger(4)\nRGB label frame colour\nLHEITX\nstring(80)\nLetter height text\nLLCLTX\nstring(80)\nLeader line clearance text\nLLGRGB\ninteger(4)\nRGB glabel style leader colour\nLLNRGB\ninteger(4)\nRGB leader line colour\nLOCRGB\ninteger(4)\nLoop RGB colour\nLSPATX\nstring(80)\nText line spacing factor (as text)\nLTERID\ninteger\nLabel terminator ID\nMLNRGB\ninteger(4)\nRGB member line colour\nMRKRGB\ninteger(4)\nRGB marker colour\nMTLCHE\nstring(80)\nMatchline text character height as text\nMTLLST\ninteger\nMatchline linestyle\nMTLRGB\ninteger(4)\nRGB matchline colour\nMTTRGB\ninteger(4)\nRGB matchline text colour\nNPPT\ninteger\nPpoint number\nOBFRGB\ninteger(4)\nRGB obscured face colour\nOCCOLO\ninteger\nCentreline and Obscured face colour\nOCCRGB\ninteger(4)\nObscured Centreline RGB colour\nOCSTYL\ninteger\nCentreline and Obscured face Style\nOLNRGB\ninteger(4)\nRGB outline colour\nOSHTTX\nstring(80)\nOvershoot text\nPKDI\nreal\nProportional distance along Pline\nPLCLTX\nstring(80)\nProjection line clearance text\nPLCRGB\ninteger(4)\nRGB projection line colour\nPLNRGB\ninteger(4)\nRGB pline colour\nPLSPTX\nstring(80)\nProj line text line-spacing text\nPRBMAR\nreal\nPrimitive blanking margin\nPRBMTX\nstring(80)\nPrimitive blanking margin text\nPTCHTX\nstring(80)\nProj text char height text\nPTLHTX\nstring(80)\nProjection text letter height text\nPTOFTX\nstring(80)\nProjection line text offset text\nPTXRGB\ninteger(4)\nRGB projection text colour\nRLTRGB\ninteger(4)\nRGB ruler long tick colour\nRMTRGB\ninteger(4)\nRGB ruler medium tick colour\nROWRGB\ninteger(4)\nRGB row colour\nRSTRGB\ninteger(4)\nRGB ruler short tick colour\nSCALAX\nstring(120)\nSymbol Scale Axis (as text)\nSMBFLG\nstring(120)\nSymbol extensible flag (as text)\nSYMCNA\nelement(1000)\nSymbol Connection Array\nTRUNTX\nstring(80)\nTruncation value (+ve) or percentage (-ve) text\nTSIZTX\nstring(80)\nTerminator size text\nTXGRGB\ninteger(4)\nRGB glabel style text colour\nTXTRGB\ninteger(4)\nRGB text colour\nVFRLST\ninteger\nView frame linestyle\nVFRRGB\ninteger(4)\nRGB view frame colour\nVSIRGB\ninteger(4)\nRGB view Section Indicator colour\n\n\n"}
{"Headers": "Attribute Category: Draft Dimensions and Annotation", "Content": "AKEYL\nword(20)\n\nAttribute-keylist (for Radial dimensions)\nDDNMX\nreal\n\nDDNM X position\nDDNMXY\nreal(2)\n\nDDNM XY position\nDDNMY\nreal\n\nDDNM Y position\nDFONTN\nstring(80)\n\nDimension text font name\nDIMPOS\npos\n\nDerived 3D dimension position\nDTLH\nreal\n\nDimension text letter height\nEVITXP\nstring(1500)\n\nEvaluated intelligent text for projection line\nEVITXT\nstring(1500)\n\nEvaluated intelligent text\nEXBTEX\nstring(1500)\n\nExpanded annotation text\nEXDMTX\nstring(1500)\n\nExpanded dimension text\nEXPLTX\nstring(1500)\n\nExpanded projection line text\nFONTN\nstring(80)\n\nFont name\nLHEI\nreal\n\nLetter height\nPDEFI\nstring\n\nPrimitive Definition\nPFONTN\nstring(80)\n\nProjection line text font name\nPRMVI\nlogical\n\nDraughting primitive visibility\nPTLH\nreal\n\nProjection text letter height\nRULAXE\nstring\n\nRuler axis (as text)\nRULTCP\nstring(120)\n\nRuler tick side (as text)\nRULTXP\nstring(120)\n\nRuler text side (as text)\nSHDPOS\nreal(2)\n\nDimension line/arc sheet position\nSHXYPS\nreal(2)\n\n2D Sheet Position\nSYSZ\nreal\n\nSymbol size (uniform scaling)\nVDPOS\npos\n\nDimension line/arc position\n\nAttribute Name\nData Type\nQualifier\nDescription\nAKEYL\nword(20)\nAttribute-keylist (for Radial dimensions)\nDDNMX\nreal\nDDNM X position\nDDNMXY\nreal(2)\nDDNM XY position\nDDNMY\nreal\nDDNM Y position\nDFONTN\nstring(80)\nDimension text font name\nDIMPOS\npos\nDerived 3D dimension position\nDTLH\nreal\nDimension text letter height\nEVITXP\nstring(1500)\nEvaluated intelligent text for projection line\nEVITXT\nstring(1500)\nEvaluated intelligent text\nEXBTEX\nstring(1500)\nExpanded annotation text\nEXDMTX\nstring(1500)\nExpanded dimension text\nEXPLTX\nstring(1500)\nExpanded projection line text\nFONTN\nstring(80)\nFont name\nLHEI\nreal\nLetter height\nPDEFI\nstring\nPrimitive Definition\nPFONTN\nstring(80)\nProjection line text font name\nPRMVI\nlogical\nDraughting primitive visibility\nPTLH\nreal\nProjection text letter height\nRULAXE\nstring\nRuler axis (as text)\nRULTCP\nstring(120)\nRuler tick side (as text)\nRULTXP\nstring(120)\nRuler text side (as text)\nSHDPOS\nreal(2)\nDimension line/arc sheet position\nSHXYPS\nreal(2)\n2D Sheet Position\nSYSZ\nreal\nSymbol size (uniform scaling)\nVDPOS\npos\nDimension line/arc position\n\n\n"}
{"Headers": "Attribute Category: Draft Drawing and Sheet", "Content": "DREVAY\nelement(50)\n\nDRWG revisions array\nDRSTYP\nstring(120)\n\nDrawing subtype\nDRTITL\nstring(1000)\n\nDrawing title\nDRTYPE\nstring(120)\n\nDrawing type\nNUMOFF\ninteger\n\nNumber of Sheets in Drawing\nSHTNUM\ninteger\n\nSheet Number\nSREVAY\nelement(50)\n\nSheet revisions array\nSTITL\nstring(1000)\n\nSheet title\n\nAttribute Name\nData Type\nQualifier\nDescription\nDREVAY\nelement(50)\nDRWG revisions array\nDRSTYP\nstring(120)\nDrawing subtype\nDRTITL\nstring(1000)\nDrawing title\nDRTYPE\nstring(120)\nDrawing type\nNUMOFF\ninteger\nNumber of Sheets in Drawing\nSHTNUM\ninteger\nSheet Number\nSREVAY\nelement(50)\nSheet revisions array\nSTITL\nstring(1000)\nSheet title\n\n\n"}
{"Headers": "Attribute Category: Draft Drawing and sheet", "Content": "BFCRGB\ninteger(4)\n\nRGB backface colour\nBOCOLO\ninteger\n\nBackface and Obscured face colour\nBOCRGB\ninteger(4)\n\nBackfaceObscured RGB colour\nBOSTYL\ninteger\n\nBackface and Obscured face Style\nDRMXTL\ninteger\n\nDraft general max text length\nDSHPOS\npos\n\nDraft sheet position derived from 3d\nLSCSLS\nlogical\n\nLogical sheet changed since last save\nLZERGB\ninteger(4)\n\nRGB layer 0 colour\nLZLSTY\ninteger\n\nLayer 0 linestyle\nLZPRIN\nlogical\n\nLayer 0 printability flag\nLZVIS\nlogical\n\nLayer 0 visibility flag\nMSTYID\ninteger\n\nMarker style\nMSTYSZ\nreal\n\nMarker size\nVLOCDI\ndir\ninteger\nView location plane direction\nVLOCPO\npos\ninteger\nView location plane position\n\nAttribute Name\nData Type\nQualifier\nDescription\nBFCRGB\ninteger(4)\nRGB backface colour\nBOCOLO\ninteger\nBackface and Obscured face colour\nBOCRGB\ninteger(4)\nBackfaceObscured RGB colour\nBOSTYL\ninteger\nBackface and Obscured face Style\nDRMXTL\ninteger\nDraft general max text length\nDSHPOS\npos\nDraft sheet position derived from 3d\nLSCSLS\nlogical\nLogical sheet changed since last save\nLZERGB\ninteger(4)\nRGB layer 0 colour\nLZLSTY\ninteger\nLayer 0 linestyle\nLZPRIN\nlogical\nLayer 0 printability flag\nLZVIS\nlogical\nLayer 0 visibility flag\nMSTYID\ninteger\nMarker style\nMSTYSZ\nreal\nMarker size\nVLOCDI\ndir\ninteger\nView location plane direction\nVLOCPO\npos\ninteger\nView location plane position\n\n\n"}
{"Headers": "Attribute Category: Draft Drawing View", "Content": "DAENABLED\nstring(10)\n\nEnable Autolabels for view (as text)\nDSHANG\nreal\n\nDraft absolute sheet angle\nELEVV\nlogical\n\nIs Elevation View\nIDLIEV\nelement(10000)\n\nEvaluated list of idlist elements\nLADRGB\ninteger(4)\n\nRGB laser drawing colour\nPLANV\nlogical\n\nIs Plan View\nPSTAT\ninteger\n\nPlane status\nSVWAY\nelement(50)\n\nSheet Views array\nVLIM\nreal(6)\n\nView limits\nVREG\nreal(4)\n\nView region\nVTITL\nstring(1000)\n\nView title\nVVOL\nreal(6)\n\nView volume\n\nAttribute Name\nData Type\nQualifier\nDescription\nDAENABLED\nstring(10)\nEnable Autolabels for view (as text)\nDSHANG\nreal\nDraft absolute sheet angle\nELEVV\nlogical\nIs Elevation View\nIDLIEV\nelement(10000)\nEvaluated list of idlist elements\nLADRGB\ninteger(4)\nRGB laser drawing colour\nPLANV\nlogical\nIs Plan View\nPSTAT\ninteger\nPlane status\nSVWAY\nelement(50)\nSheet Views array\nVLIM\nreal(6)\nView limits\nVREG\nreal(4)\nView region\nVTITL\nstring(1000)\nView title\nVVOL\nreal(6)\nView volume\n\n\n"}
{"Headers": "Attribute Category: Draft Intelligent Text Related", "Content": "PCODA\ninteger\n\nPrecision code angles\nPCODF\ninteger\n\nPrecision code fractions\nPCODI\ninteger\n\nPrecision code imperial\nPCODM\ninteger\n\nPrecision code metric\nUCODB\ninteger\n\nUnits code bore\nUCODD\ninteger\n\nUnits code distance\n\nAttribute Name\nData Type\nQualifier\nDescription\nPCODA\ninteger\nPrecision code angles\nPCODF\ninteger\nPrecision code fractions\nPCODI\ninteger\nPrecision code imperial\nPCODM\ninteger\nPrecision code metric\nUCODB\ninteger\nUnits code bore\nUCODD\ninteger\nUnits code distance\n\n\n"}
{"Headers": "Attribute Category: Draft Style Related - Line/Fill/Marker", "Content": "BFSTREF\nelement\n\nBackface linestyle Reference\nCHSTREF\nelement\n\nCrosshairs linestyle Reference\nCLSTREF\nelement\n\nCentreline linestyle Reference\nCOLSTREF\nelement\n\nColumn linestyle Reference\nDLSTREF\nelement\n\nDimension linestyle Reference\nFFSTREF\nelement\n\nFront-face linestyle Reference\nFSTNUM\ninteger\n\nFill style number\nFSTREF\nelement\n\nFill style Reference\nHLSTREF\nelement\n\nHatching linestyle Reference\nLFSTREF\nelement\n\nLabel frame linestyle Reference\nLLSTREF\nelement\n\nLabel leader linestyle Reference\nMLNSTREF\nelement\n\nMember-line linestyle Reference\nMSTREF\nelement\n\nMarker style Reference\nNLSTREF\nelement\n\nNote linestyle Reference\nOBSTREF\nelement\n\nObscured face linestyle Reference\nOLSTREF\nelement\n\nOutline linestyle Reference\nPLNSTREF\nelement\n\nPline linestyle Reference\nPLSTREF\nelement\n\nProjection linestyle Reference\nROWSTREF\nelement\n\nRow linestyle Reference\n\nAttribute Name\nData Type\nQualifier\nDescription\nBFSTREF\nelement\nBackface linestyle Reference\nCHSTREF\nelement\nCrosshairs linestyle Reference\nCLSTREF\nelement\nCentreline linestyle Reference\nCOLSTREF\nelement\nColumn linestyle Reference\nDLSTREF\nelement\nDimension linestyle Reference\nFFSTREF\nelement\nFront-face linestyle Reference\nFSTNUM\ninteger\nFill style number\nFSTREF\nelement\nFill style Reference\nHLSTREF\nelement\nHatching linestyle Reference\nLFSTREF\nelement\nLabel frame linestyle Reference\nLLSTREF\nelement\nLabel leader linestyle Reference\nMLNSTREF\nelement\nMember-line linestyle Reference\nMSTREF\nelement\nMarker style Reference\nNLSTREF\nelement\nNote linestyle Reference\nOBSTREF\nelement\nObscured face linestyle Reference\nOLSTREF\nelement\nOutline linestyle Reference\nPLNSTREF\nelement\nPline linestyle Reference\nPLSTREF\nelement\nProjection linestyle Reference\nROWSTREF\nelement\nRow linestyle Reference\n\n\n"}
{"Headers": "Attribute Category: Drafting", "Content": "DNOTCP\nelement\n\nDraw Note Current Command Line Point\n\nAttribute Name\nData Type\nQualifier\nDescription\nDNOTCP\nelement\nDraw Note Current Command Line Point\n\n\n"}
{"Headers": "Attribute Category: Element Type Related", "Content": "ACTTYPE\nword\n\nType of element, truncating non UDETs to 4 or 6 characters\nAHLIS\nword(200)\n\nList of actual types in owning hierarchy\nFULLT\nstring\n\ntype of the element\nFULSYS\nstring\n\nType of the element, ignoring UDET, not truncated\nOSTYPE\nword\n\nShort cut for \"Type of owner\"\nTYPE\nword\n\nType of the element, ignoring UDET, truncated to 4 or 6 characters\nTYSEQU\ninteger\n\nType Sequence Number\n\nAttribute Name\nData Type\nQualifier\nDescription\nACTTYPE\nword\nType of element, truncating non UDETs to 4 or 6 characters\nAHLIS\nword(200)\nList of actual types in owning hierarchy\nFULLT\nstring\ntype of the element\nFULSYS\nstring\nType of the element, ignoring UDET, not truncated\nOSTYPE\nword\nShort cut for \"Type of owner\"\nTYPE\nword\nType of the element, ignoring UDET, truncated to 4 or 6 characters\nTYSEQU\ninteger\nType Sequence Number\n\n\n"}
{"Headers": "Attribute Category: Element type related", "Content": "GENTYP\nword\n\nType of geometry\n\nAttribute Name\nData Type\nQualifier\nDescription\nGENTYP\nword\nType of geometry\n\n\n"}
{"Headers": "Attribute Category: Engineering", "Content": "CLANAM\nstringarray(10)\n\nClass Name\nCLSNAM\nstring(120)\n\nClass Name\nCLSURI\nstring(200)\n\nClass URI Pseudo\nDOCCHG\nelement(2147483647)\n\nReference to changed related documents\nDSIFIL\nstring(2000)\n\nDatasheet Instance filename\nENGCHG\nlogical\n\nChanged since Issue\nENGDOC\nelement(2147483647)\n\nReference to related documents\nTABCLN\nstringarray(10)\n\nTabite Class Name\nTABREF\nelement(100)\n\nTabite reference\n\nAttribute Name\nData Type\nQualifier\nDescription\nCLANAM\nstringarray(10)\nClass Name\nCLSNAM\nstring(120)\nClass Name\nCLSURI\nstring(200)\nClass URI Pseudo\nDOCCHG\nelement(2147483647)\nReference to changed related documents\nDSIFIL\nstring(2000)\nDatasheet Instance filename\nENGCHG\nlogical\nChanged since Issue\nENGDOC\nelement(2147483647)\nReference to related documents\nTABCLN\nstringarray(10)\nTabite Class Name\nTABREF\nelement(100)\nTabite reference\n\n\n"}
{"Headers": "Attribute Category: Extract Related", "Content": "EXHCNC\nelement(5000)\n\nAs EXTCNC, but repeat test for all descendants\nEXHCNN\nelement(5000)\n\nAs EXTCNN, but repeat test for all descendants\nEXHCON\nelement(5000)\n\nAs EXTCON, but repeat test for all descendants\nEXHRCN\nelement(5000)\n\nAs EXRCN, but repeat test for all descendants\nEXHRCO\nelement(5000)\n\nAs EXTRCO, but repeat test for all descendants\nEXMOC\nlogical\n\nAs EXMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOC\nlogical\n\nAs EXPMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOD\nlogical\n\nTrue if primary and element or non-primary descendants have been modified in this extract\nEXTCNC\nelement(5000)\n\nAs EXTCON but excluding non modified elements\nEXTCNN\nelement(5000)\n\nAs EXTCON but excluding modified elements\nEXTCON\nelement(5000)\n\nPrimary elements connected/disconnected from element or non primary descendants in extract\nEXTRCN\nelement(5000)\n\nAs EXTCNN, but applied recursively to each connection\nEXTRCO\nelement(5000)\n\nAs EXTCON, but applied recursively to each connection\nINCFLU\nelement(500)\n\nAdditional elements to include for flush\nINCPRO\nelement(500)\n\nAdditional elements to include for data propagation\nOKDROP\nlogical\n\nTrue if element may be dropped\nOKRLEX\nlogical\n\nTrue if element may be extract released\n\nAttribute Name\nData Type\nQualifier\nDescription\nEXHCNC\nelement(5000)\nAs EXTCNC, but repeat test for all descendants\nEXHCNN\nelement(5000)\nAs EXTCNN, but repeat test for all descendants\nEXHCON\nelement(5000)\nAs EXTCON, but repeat test for all descendants\nEXHRCN\nelement(5000)\nAs EXRCN, but repeat test for all descendants\nEXHRCO\nelement(5000)\nAs EXTRCO, but repeat test for all descendants\nEXMOC\nlogical\nAs EXMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOC\nlogical\nAs EXPMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOD\nlogical\nTrue if primary and element or non-primary descendants have been modified in this extract\nEXTCNC\nelement(5000)\nAs EXTCON but excluding non modified elements\nEXTCNN\nelement(5000)\nAs EXTCON but excluding modified elements\nEXTCON\nelement(5000)\nPrimary elements connected/disconnected from element or non primary descendants in extract\nEXTRCN\nelement(5000)\nAs EXTCNN, but applied recursively to each connection\nEXTRCO\nelement(5000)\nAs EXTCON, but applied recursively to each connection\nINCFLU\nelement(500)\nAdditional elements to include for flush\nINCPRO\nelement(500)\nAdditional elements to include for data propagation\nOKDROP\nlogical\nTrue if element may be dropped\nOKRLEX\nlogical\nTrue if element may be extract released\n\n\n"}
{"Headers": "Attribute Category: Fabrication", "Content": "RELELS\nelement(500000)\nword\nRelated Elements, Fabrication\nRELELT\nelement\nword\nRelated Element, Fabrication\nRELINF\nstring(200)\nword\nRelated Element Information, Fabrication\n\nAttribute Name\nData Type\nQualifier\nDescription\nRELELS\nelement(500000)\nword\nRelated Elements, Fabrication\nRELELT\nelement\nword\nRelated Element, Fabrication\nRELINF\nstring(200)\nword\nRelated Element Information, Fabrication\n\n\n"}
{"Headers": "Attribute Category: Fabrication Assembly", "Content": "FASIOW\nelement(500)\n\nFabrication assembly item referring to element\nFASOWN\nelement(500)\n\nFabrication assembly referring to element\nFASSEQ\ninteger\n\nFabrication assembly sequence\n\nAttribute Name\nData Type\nQualifier\nDescription\nFASIOW\nelement(500)\nFabrication assembly item referring to element\nFASOWN\nelement(500)\nFabrication assembly referring to element\nFASSEQ\ninteger\nFabrication assembly sequence\n\n\n"}
{"Headers": "Attribute Category: Global", "Content": "ADMLOC\nelement\n\nCurrently administered location\nCURLOC\nelement\n\nTrue current location\nDBALL\nelement(8000)\n\nList of DBs allocated to location\nDBPR\nelement(8000)\n\nList of DBs Primary at location\nEXCPRM\nelement(8191)\n\nPrimary locations of extract children\nEXOPRM\nelement\n\nPrimary location of extract owner\nGLBSTR\nlogical\n\nTrue if Project has Global structure\nISALLO\nlogical\n\nTrue if database is allocated at this location\nISEXAP\nlogical\n\nTrue if extract ancestry is primary here\nISEXCP\nlogical\n\nTrue if all extract children are primary here\nISEXFP\nlogical\n\nTrue if extract family is primary here\nISEXMP\nlogical\n\nTrue if extract master is primary here\nISEXOP\nlogical\n\nTrue if extract owner is primary here\nISPRIM\nlogical\n\nTrue if database is primary at this location\nLOCPR\nelement(1000)\n\nList of LOCs Primary at location\nNXTLOCATIONS\nelement(200)\n\nList of online neighbour LOCs for a LOC\nPRIMDB\nstring\n\nGlobal status of DB, primary or secondary\nPRMLOC\nelement\n\nPrimary location\n\nAttribute Name\nData Type\nQualifier\nDescription\nADMLOC\nelement\nCurrently administered location\nCURLOC\nelement\nTrue current location\nDBALL\nelement(8000)\nList of DBs allocated to location\nDBPR\nelement(8000)\nList of DBs Primary at location\nEXCPRM\nelement(8191)\nPrimary locations of extract children\nEXOPRM\nelement\nPrimary location of extract owner\nGLBSTR\nlogical\nTrue if Project has Global structure\nISALLO\nlogical\nTrue if database is allocated at this location\nISEXAP\nlogical\nTrue if extract ancestry is primary here\nISEXCP\nlogical\nTrue if all extract children are primary here\nISEXFP\nlogical\nTrue if extract family is primary here\nISEXMP\nlogical\nTrue if extract master is primary here\nISEXOP\nlogical\nTrue if extract owner is primary here\nISPRIM\nlogical\nTrue if database is primary at this location\nLOCPR\nelement(1000)\nList of LOCs Primary at location\nNXTLOCATIONS\nelement(200)\nList of online neighbour LOCs for a LOC\nPRIMDB\nstring\nGlobal status of DB, primary or secondary\nPRMLOC\nelement\nPrimary location\n\n\n"}
{"Headers": "Attribute Category: Hull", "Content": "APARMS\nreal(9)\n\nAll parameters\nASDIM\nreal(3)\n\nAssembly dimension\nASREF\nelement\n\nAssembly reference\nASSNST\nelement\n\nAssembly Nest\nATWLEN\nreal\n\nAssembly total weld length\nBEALAM\nstring(12)\n\nName of the bead laminate code\nBEAPOS\ninteger\n\nBead posno\nBEAQUA\nstring(26)\n\nBead quality\nBEAWTH\nreal\n\nBead width\nBENT\nlogical\n\nBent flag\nBEVEL\nreal\n\nBevel\nBEVFLA\nreal\n\nBevel code, flange\nBEVLFT\nreal\n\nBevel code on left side of seam\nBEVM\nreal(2)\n\nBevel codes along M1 and M2 curves\nBEVRGT\nreal\n\nBevel code on right side of seam\nBEVTXT\nstring\n\nBevel text\nBEVWEB\nreal\n\nBevel code, web\nBLCKLM\nlogical\n\nTrue if block limit seam\nBRARLT\nreal(10)\n\nBracket arm lengths\nBURNID\nstring(80)\n\nBurner id\nBUYMRK\nstring(26)\n\nBuying mark\nCAXISE\nstring\n\nCoordinate axis enumerated\nCHALEN\nreal\n\nLength of chamfer intervals\nCHANUM\ninteger\n\nNumber of chamfer intervals\nCLIPCD\ninteger\n\nClip code\nCLMPLN\nreal\n\nClamping length of manufactured profile\nCLNELS\nelement(100)\n\nReferences to panels or components in the same clone chain\nCLOSED\nlogical\n\nTrue if plate covering entire referenced component\nCMALL\nreal\n\nStructure allowance\nCMBOUA\nelement\n\nAft boundary\nCMBOUF\nelement\n\nFwd boundary\nCMBOUL\nelement\n\nLower boundary\nCMBOUP\nelement\n\nPs boundary\nCMBOUS\nelement\n\nStbd boundary\nCMBOUU\nelement\n\nUpper boundary\nCMBOX\nreal(6)\n\nBounding box\nCMCAT\nstring(256)\n\nCompartment category\nCMCDE\nreal\n\nContent density\nCMCTID\nstring(256)\n\nContent type ID\nCMDESC\nstring(256)\n\nCompartment description\nCMFLW\nreal\n\nFull Load Weight\nCMLCV\nreal\n\nLongitudinal centre of total volume\nCMMGE\ninteger\n\nMerged compartment indicator\nCMPER\nreal\n\nCompartment permeability\nCMPERD\nreal\n\nPermeability for use in damage\nCMPURP\nstring(256)\n\nPurpose\nCMTCV\nreal\n\nTransverse centre of total volume\nCMTYP\ninteger\n\nType of compartment\nCMVCV\nreal\n\nVertical centre of total volume\nCMVOL\nreal\n\nTotal volume\nCNTNUM\ninteger\n\nContour number\nCOMNT\nstring\n\nComment\nCONAM\nstring\n\nCutout name\nCONCD\ninteger\n\nConnection code\nCONDES\nstring\n\nConnection string\nCONTYP\nstring\n\nConnection type\nCORNUM\ninteger\n\nCorner number\nDATINT\ninteger(2)\n\nDate\nDEST\nstring(26)\n\nDestination\nDIST\nreal(2)\n\nDistances\nDISTM\nreal(2)\n\nDistances to M1 and M2 curves\nDSGNTN\nstring\n\nDesignation\nDSTNCE\nreal\n\nDistance\nDTWTCL\nstring\n\nDate of weight/cog calculation\nEDPUV\npos\n\nEnd point\nEPARAM\nreal(6)\n\nEvaluated parameters\nEXCESS\nreal\n\nExcess\nEXCLEN\nreal(3)\n\nLength of excess intervals\nEXCLFT\nreal\n\nExcess on left side of seam\nEXCNUM\ninteger(3)\n\nNumber of excess intervals\nEXCRGT\nreal\n\nExcess on right side of seam\nEXCTLF\ninteger\n\nExcess type on left side of seam\nEXCTRG\ninteger\n\nExcess type on right side of seam\nEXTBOX\nreal(6)\n\nExtended block box\nEXTNSN\nreal\n\nExtension\nFABLOC\nword\n\nFabrication location\nFASTYP\nword\n\nFastener Type\nFEMCOL\ninteger\n\nFEM image object colour\nFLATYP\ninteger\n\nFlange type\nFNCCD\ninteger\n\nFunctional description code\nFNCTXT\nstring(80)\n\nFunctional description\nFOLDED\nlogical\n\nTrue if folded\nFULLEN\nreal\n\nTotal length of manufactured profile\nGENSTR\nstring\ninteger\nGeneral strings\nGPSTR\nstring(26)\ninteger\nGeneral purpose strings\nGRILEN\nreal\n\nLength of grinding intervals\nGRIND\nreal\n\nGrinding info\nGRINUM\ninteger\n\nNumber of grinding intervals\nHASCLN\nlogical\n\nHas clones flag\nHGHT\nreal\n\nHeight\nHLCOLO\nstring\n\nHull Colour\nHULCNT\ninteger\n\nSize of hull array/collection\nHULLOB\nelement\n\nHull object reference\nHULOC\nstring\n\nLocation\nHUMVW\nstring\n\nModel View\nHUREFL\nlogical\n\nReflected\nHUREPL\nelement\n\nReplica\nHUSYMM\nlogical\n\nSymmetrical\nHYWTSU\nreal\n\nWetted surface\nIBLNAM\nstring\n\nName of idealised block\nIDENT\nstring\n\nPanel identification string\nINCL\nreal\n\nInclination angle\nINSTNC\nstring\n\nBracket instance name\nISECPT\npos\nword, integer\nIntersection point\nKNUANG\nreal\n\nKnuckle angle\nKNUCKL\nlogical\n\nTrue if knuckled\nLAMDIS\nlogical\n\nTrue if Lam Displ\nLAMINA\nstring(12)\n\nName of first laminate code\nLAMINB\nstring(12)\n\nName of second laminate code\nLAMWTH\nreal\n\nWidth of laminate\nLIMNUM\ninteger\n\nOrder number of limit\nMACRID\nstring\n\nClip macro ID\nMANBLK\nstring\n\nName of owner block\nMANLEN\nreal\n\nLength of manual intervals\nMANNUM\ninteger\n\nNumber of manual intervals\nMANPAN\nstring\n\nName of owner panel\nMANTRA\nreal(16)\n\nTransformation from local coordinate system\nMAXARE\nreal\n\nMaximum area\nMFFIND\nelement\n\nFind Manufacturingpackage folder\nMGRADE\nstring(25)\n\nMaterial grade\nMIBSHP\nword\n\nBurning shape\nMIRROR\nlogical\n\nTrue if mirrored in local v-axis\nMICOMP\nword\n\nMovement instruction valid for\nMIPSID\nword\n\nProfile end\nMISIDE\nword\n\nMovement instruction side\nMNDIRE\nstring(9)\n\nMain direction enumerated\nMNSIDE\nstring(9)\n\nMain side enumerated\nMODREF\nelement(100)\n\nModel references\nMOULEN\nreal\n\nMould length\nMPFIND\nelement\n\nFind Manufacturingpackage\nMPKGFD\nelement\n\nFind Manufacturingpackage\nMTHICK\nreal\n\nMaterial thickness\nNOMARK\nlogical\n\nTrue if unmarked\nNOPGS\ninteger\n\nNumber of openings\nNPRVEC\nreal(2)\n\nLocal rotation vector of part\nNPSIDE\nstring(80)\n\nSide of nested part\nNPXYP\nreal(2)\n\nPosition of part(x,y)\nNTRLEN\nreal\n\nNeutral length\nOBJCD\ninteger(2)\n\nObject codes\nOFFSET\nreal\n\nOffset\nOGDSTS\nreal(25)\n\nDistances to openings\nOTHLEN\nreal\n\nLength of other intervals\nOTHNUM\ninteger\n\nNumber of other intervals\nOUAREA\nreal\n\nOuter area\nOUTFRF\nelement\n\nReference of matching outfit object\nOVRSH\nreal\n\nOvershoot (d-measure) for unsymmetrical flange\nPANOTL\nelement(100)\n\nReferences to limiting panels\nPANREF\nelement\n\nPanel reference\nPANSID\ninteger\n\nSide of panel\nPARAL\nlogical\n\nTrue if tap parallel to referred seam\nPARM\nreal(6)\n\nParameters\nPARNAM\nstring(256)\n\nPart name\nPARREF\nelement(10)\n\nPart reference\nPDELE\nelement\n\nReference of matching hull object\nPECPAR\nstring\nword\nEndcut parameters\nPLAREA\nreal\n\nArea\nPNTUV\npos\n\nPoint2D\nPNTXYZ\npos\n\nPoint3D\nPOINUM\ninteger\n\nPoint Num\nPOSNO\ninteger\n\nPosition number\nPRTIDL\nstring(132)\n\nLong part id\nPRTIDM\nstring(132)\nword\nModule part id\nPRTIDS\nstring(132)\n\nShort part id\nPRTLST\nstring(26)\n\nParts list name\nQUACD\ninteger\n\nQuality code\nQUATXT\nstring(26)\n\nQuality\nRAWPLA\nelement\n\nRaw Plate\nREFLCL\nlogical\n\nTrue if reflected in CL\nRSBOX\nreal(6)\n\nBounding box of RSO\nRSFFD\ninteger\n\nFunctional description on face\nRSFMC\ninteger\n\nMaterial code on face\nRSFMS\nstring(256)\n\nMaterial side on face\nRSFMT\nreal\n\nMaterial thickness on face\nRSFSA\nlogical\n\nAuto stiffening on face\nRSFSD\nstring(256)\n\nProfile dim on face\nRSFSS\nstring(256)\n\nStiffener side on face\nRSFST\ninteger\n\nProfile type on face\nRSFWT\nlogical\n\nWatertight\nRSLBRA\nstring(256)\n\nBracket instance at limit\nRSLELE\nelement\n\nLimiting element\nRSLPRE\ninteger\n\nProfile end definition at limit\nRSPAN\nelement(1000)\n\nPanel(s) defined on RSO\nRSPLN\ninteger\n\nPrincipal plane of RSO\nRSTYP\ninteger\n\nType of RSO\nSCHEME\nstring\n\nScheme name\nSCRAPT\nreal\n\nTotal scrap of raw plate area\nSCRAPU\nreal\n\nTotal scrap of used raw plate area\nSDTINT\ninteger(2)\n\nSplitting date\nSDTTXT\nstring(22)\n\nSplitting date\nSHFALG\nreal\n\nShrinkage factor along main direction\nSHFPRP\nreal\n\nShrinkage factor perpendicular to main direction\nSHFSEA\nreal\n\nShrinkage factor for seams perp. to main direction\nSHPUV\npos\n\nPoint defining shrinkage\nSHVUV\ndir\n\nVector defining shrinkage\nSPECIF\nlogical\n\nTrue if outer panel contour on PS/SB are different\nSPLA\nstring\n\nName of spigot plate\nSPPOSN\ninteger\n\nPosition number of spigot plate\nSTPUV\npos\n\nStart point\nSTREAT\nstring(26)\n\nSurface treatment\nSTRXPL\nlogical\n\nTrue if surface treatment explicitly defined\nSYMELE\nelement\n\nSymmetric element\nSYMLNS\ninteger\n\nSide of direction vector\nSYMM\ninteger\n\nSymmetry code\nSYMXYZ\ndir\n\nVector along symmetry line\nTAGCD\ninteger\n\nTag code\nTAGCDS\ninteger(25)\n\nTag codes\nTAGNMS\ninteger(25)\n\nTag numbers\nTAGNUM\ninteger\n\nTag number\nTGHETP\nstring(20)\n\nType of Tightness code\nTOTLEN\nreal\n\nTotal manual length\nTPLFRR\nelement(10000)\ninteger\nTopology references - from\nTPLFRT\ninteger(10000)\nelement\nTopology reference types - from\nTPLPAR\nreal(50)\n\nTemplate parameters\nTPLTOR\nelement(10000)\ninteger\nTopology references - to\nTPLTOT\ninteger(10000)\nelement\nTopology reference types - to\nTPLTYP\nstring(25)\n\nTemplate type\nTVALS\nreal(1000)\n\nt Values\nTWIST\nlogical\n\nTrue if twisted\nTWSTAN\nreal\n\nTwist angle\nTYPECD\ninteger\n\nType code\nTYPECE\ninteger\n\nType code\nUPRLEN\nreal\n\nUsed profile length\nUUID\nstring(36)\n\nUniversally unique identifier\nUUIDREF\nelement(500)\nword\nUniversally unique identifier references\nVBEVEL\nlogical\n\nTrue if V-bevel\nWELDDP\nreal\n\nWelding depth\nWGAP\nreal\n\nWeld Gap\nWLNGTH\nreal\n\nWeld Length\nWTYPE\nword\n\nWeld type\nXBEVEL\nlogical\n\nTrue if X-bevel\nYBEVEL\nlogical\n\nTrue if Y-bevel\n\nAttribute Name\nData Type\nQualifier\nDescription\nAPARMS\nreal(9)\nAll parameters\nASDIM\nreal(3)\nAssembly dimension\nASREF\nelement\nAssembly reference\nASSNST\nelement\nAssembly Nest\nATWLEN\nreal\nAssembly total weld length\nBEALAM\nstring(12)\nName of the bead laminate code\nBEAPOS\ninteger\nBead posno\nBEAQUA\nstring(26)\nBead quality\nBEAWTH\nreal\nBead width\nBENT\nlogical\nBent flag\nBEVEL\nreal\nBevel\nBEVFLA\nreal\nBevel code, flange\nBEVLFT\nreal\nBevel code on left side of seam\nBEVM\nreal(2)\nBevel codes along M1 and M2 curves\nBEVRGT\nreal\nBevel code on right side of seam\nBEVTXT\nstring\nBevel text\nBEVWEB\nreal\nBevel code, web\nBLCKLM\nlogical\nTrue if block limit seam\nBRARLT\nreal(10)\nBracket arm lengths\nBURNID\nstring(80)\nBurner id\nBUYMRK\nstring(26)\nBuying mark\nCAXISE\nstring\nCoordinate axis enumerated\nCHALEN\nreal\nLength of chamfer intervals\nCHANUM\ninteger\nNumber of chamfer intervals\nCLIPCD\ninteger\nClip code\nCLMPLN\nreal\nClamping length of manufactured profile\nCLNELS\nelement(100)\nReferences to panels or components in the same clone chain\nCLOSED\nlogical\nTrue if plate covering entire referenced component\nCMALL\nreal\nStructure allowance\nCMBOUA\nelement\nAft boundary\nCMBOUF\nelement\nFwd boundary\nCMBOUL\nelement\nLower boundary\nCMBOUP\nelement\nPs boundary\nCMBOUS\nelement\nStbd boundary\nCMBOUU\nelement\nUpper boundary\nCMBOX\nreal(6)\nBounding box\nCMCAT\nstring(256)\nCompartment category\nCMCDE\nreal\nContent density\nCMCTID\nstring(256)\nContent type ID\nCMDESC\nstring(256)\nCompartment description\nCMFLW\nreal\nFull Load Weight\nCMLCV\nreal\nLongitudinal centre of total volume\nCMMGE\ninteger\nMerged compartment indicator\nCMPER\nreal\nCompartment permeability\nCMPERD\nreal\nPermeability for use in damage\nCMPURP\nstring(256)\nPurpose\nCMTCV\nreal\nTransverse centre of total volume\nCMTYP\ninteger\nType of compartment\nCMVCV\nreal\nVertical centre of total volume\nCMVOL\nreal\nTotal volume\nCNTNUM\ninteger\nContour number\nCOMNT\nstring\nComment\nCONAM\nstring\nCutout name\nCONCD\ninteger\nConnection code\nCONDES\nstring\nConnection string\nCONTYP\nstring\nConnection type\nCORNUM\ninteger\nCorner number\nDATINT\ninteger(2)\nDate\nDEST\nstring(26)\nDestination\nDIST\nreal(2)\nDistances\nDISTM\nreal(2)\nDistances to M1 and M2 curves\nDSGNTN\nstring\nDesignation\nDSTNCE\nreal\nDistance\nDTWTCL\nstring\nDate of weight/cog calculation\nEDPUV\npos\nEnd point\nEPARAM\nreal(6)\nEvaluated parameters\nEXCESS\nreal\nExcess\nEXCLEN\nreal(3)\nLength of excess intervals\nEXCLFT\nreal\nExcess on left side of seam\nEXCNUM\ninteger(3)\nNumber of excess intervals\nEXCRGT\nreal\nExcess on right side of seam\nEXCTLF\ninteger\nExcess type on left side of seam\nEXCTRG\ninteger\nExcess type on right side of seam\nEXTBOX\nreal(6)\nExtended block box\nEXTNSN\nreal\nExtension\nFABLOC\nword\nFabrication location\nFASTYP\nword\nFastener Type\nFEMCOL\ninteger\nFEM image object colour\nFLATYP\ninteger\nFlange type\nFNCCD\ninteger\nFunctional description code\nFNCTXT\nstring(80)\nFunctional description\nFOLDED\nlogical\nTrue if folded\nFULLEN\nreal\nTotal length of manufactured profile\nGENSTR\nstring\ninteger\nGeneral strings\nGPSTR\nstring(26)\ninteger\nGeneral purpose strings\nGRILEN\nreal\nLength of grinding intervals\nGRIND\nreal\nGrinding info\nGRINUM\ninteger\nNumber of grinding intervals\nHASCLN\nlogical\nHas clones flag\nHGHT\nreal\nHeight\nHLCOLO\nstring\nHull Colour\nHULCNT\ninteger\nSize of hull array/collection\nHULLOB\nelement\nHull object reference\nHULOC\nstring\nLocation\nHUMVW\nstring\nModel View\nHUREFL\nlogical\nReflected\nHUREPL\nelement\nReplica\nHUSYMM\nlogical\nSymmetrical\nHYWTSU\nreal\nWetted surface\nIBLNAM\nstring\nName of idealised block\nIDENT\nstring\nPanel identification string\nINCL\nreal\nInclination angle\nINSTNC\nstring\nBracket instance name\nISECPT\npos\nword, integer\nIntersection point\nKNUANG\nreal\nKnuckle angle\nKNUCKL\nlogical\nTrue if knuckled\nLAMDIS\nlogical\nTrue if Lam Displ\nLAMINA\nstring(12)\nName of first laminate code\nLAMINB\nstring(12)\nName of second laminate code\nLAMWTH\nreal\nWidth of laminate\nLIMNUM\ninteger\nOrder number of limit\nMACRID\nstring\nClip macro ID\nMANBLK\nstring\nName of owner block\nMANLEN\nreal\nLength of manual intervals\nMANNUM\ninteger\nNumber of manual intervals\nMANPAN\nstring\nName of owner panel\nMANTRA\nreal(16)\nTransformation from local coordinate system\nMAXARE\nreal\nMaximum area\nMFFIND\nelement\nFind Manufacturingpackage folder\nMGRADE\nstring(25)\nMaterial grade\nMIBSHP\nword\nBurning shape\nMIRROR\nlogical\nTrue if mirrored in local v-axis\nMICOMP\nword\nMovement instruction valid for\nMIPSID\nword\nProfile end\nMISIDE\nword\nMovement instruction side\nMNDIRE\nstring(9)\nMain direction enumerated\nMNSIDE\nstring(9)\nMain side enumerated\nMODREF\nelement(100)\nModel references\nMOULEN\nreal\nMould length\nMPFIND\nelement\nFind Manufacturingpackage\nMPKGFD\nelement\nFind Manufacturingpackage\nMTHICK\nreal\nMaterial thickness\nNOMARK\nlogical\nTrue if unmarked\nNOPGS\ninteger\nNumber of openings\nNPRVEC\nreal(2)\nLocal rotation vector of part\nNPSIDE\nstring(80)\nSide of nested part\nNPXYP\nreal(2)\nPosition of part(x,y)\nNTRLEN\nreal\nNeutral length\nOBJCD\ninteger(2)\nObject codes\nOFFSET\nreal\nOffset\nOGDSTS\nreal(25)\nDistances to openings\nOTHLEN\nreal\nLength of other intervals\nOTHNUM\ninteger\nNumber of other intervals\nOUAREA\nreal\nOuter area\nOUTFRF\nelement\nReference of matching outfit object\nOVRSH\nreal\nOvershoot (d-measure) for unsymmetrical flange\nPANOTL\nelement(100)\nReferences to limiting panels\nPANREF\nelement\nPanel reference\nPANSID\ninteger\nSide of panel\nPARAL\nlogical\nTrue if tap parallel to referred seam\nPARM\nreal(6)\nParameters\nPARNAM\nstring(256)\nPart name\nPARREF\nelement(10)\nPart reference\nPDELE\nelement\nReference of matching hull object\nPECPAR\nstring\nword\nEndcut parameters\nPLAREA\nreal\nArea\nPNTUV\npos\nPoint2D\nPNTXYZ\npos\nPoint3D\nPOINUM\ninteger\nPoint Num\nPOSNO\ninteger\nPosition number\nPRTIDL\nstring(132)\nLong part id\nPRTIDM\nstring(132)\nword\nModule part id\nPRTIDS\nstring(132)\nShort part id\nPRTLST\nstring(26)\nParts list name\nQUACD\ninteger\nQuality code\nQUATXT\nstring(26)\nQuality\nRAWPLA\nelement\nRaw Plate\nREFLCL\nlogical\nTrue if reflected in CL\nRSBOX\nreal(6)\nBounding box of RSO\nRSFFD\ninteger\nFunctional description on face\nRSFMC\ninteger\nMaterial code on face\nRSFMS\nstring(256)\nMaterial side on face\nRSFMT\nreal\nMaterial thickness on face\nRSFSA\nlogical\nAuto stiffening on face\nRSFSD\nstring(256)\nProfile dim on face\nRSFSS\nstring(256)\nStiffener side on face\nRSFST\ninteger\nProfile type on face\nRSFWT\nlogical\nWatertight\nRSLBRA\nstring(256)\nBracket instance at limit\nRSLELE\nelement\nLimiting element\nRSLPRE\ninteger\nProfile end definition at limit\nRSPAN\nelement(1000)\nPanel(s) defined on RSO\nRSPLN\ninteger\nPrincipal plane of RSO\nRSTYP\ninteger\nType of RSO\nSCHEME\nstring\nScheme name\nSCRAPT\nreal\nTotal scrap of raw plate area\nSCRAPU\nreal\nTotal scrap of used raw plate area\nSDTINT\ninteger(2)\nSplitting date\nSDTTXT\nstring(22)\nSplitting date\nSHFALG\nreal\nShrinkage factor along main direction\nSHFPRP\nreal\nShrinkage factor perpendicular to main direction\nSHFSEA\nreal\nShrinkage factor for seams perp. to main direction\nSHPUV\npos\nPoint defining shrinkage\nSHVUV\ndir\nVector defining shrinkage\nSPECIF\nlogical\nTrue if outer panel contour on PS/SB are different\nSPLA\nstring\nName of spigot plate\nSPPOSN\ninteger\nPosition number of spigot plate\nSTPUV\npos\nStart point\nSTREAT\nstring(26)\nSurface treatment\nSTRXPL\nlogical\nTrue if surface treatment explicitly defined\nSYMELE\nelement\nSymmetric element\nSYMLNS\ninteger\nSide of direction vector\nSYMM\ninteger\nSymmetry code\nSYMXYZ\ndir\nVector along symmetry line\nTAGCD\ninteger\nTag code\nTAGCDS\ninteger(25)\nTag codes\nTAGNMS\ninteger(25)\nTag numbers\nTAGNUM\ninteger\nTag number\nTGHETP\nstring(20)\nType of Tightness code\nTOTLEN\nreal\nTotal manual length\nTPLFRR\nelement(10000)\ninteger\nTopology references - from\nTPLFRT\ninteger(10000)\nelement\nTopology reference types - from\nTPLPAR\nreal(50)\nTemplate parameters\nTPLTOR\nelement(10000)\ninteger\nTopology references - to\nTPLTOT\ninteger(10000)\nelement\nTopology reference types - to\nTPLTYP\nstring(25)\nTemplate type\nTVALS\nreal(1000)\nt Values\nTWIST\nlogical\nTrue if twisted\nTWSTAN\nreal\nTwist angle\nTYPECD\ninteger\nType code\nTYPECE\ninteger\nType code\nUPRLEN\nreal\nUsed profile length\nUUID\nstring(36)\nUniversally unique identifier\nUUIDREF\nelement(500)\nword\nUniversally unique identifier references\nVBEVEL\nlogical\nTrue if V-bevel\nWELDDP\nreal\nWelding depth\nWGAP\nreal\nWeld Gap\nWLNGTH\nreal\nWeld Length\nWTYPE\nword\nWeld type\nXBEVEL\nlogical\nTrue if X-bevel\nYBEVEL\nlogical\nTrue if Y-bevel\n\n\n"}
{"Headers": "Attribute Category: HVAC", "Content": "ARRSHA\nword\n\nArrive PPoint Connection shape\nLEASHA\nword\n\nLeave PPoint Connection shape\nPDSHAP\nstring(1000)\n\nDuct PPOINT shape\nPPSHAP\nword\ninteger\nPPoint Connection shape\n\nAttribute Name\nData Type\nQualifier\nDescription\nARRSHA\nword\nArrive PPoint Connection shape\nLEASHA\nword\nLeave PPoint Connection shape\nPDSHAP\nstring(1000)\nDuct PPOINT shape\nPPSHAP\nword\ninteger\nPPoint Connection shape\n\n\n"}
{"Headers": "Attribute Category: Ladder", "Content": "BRNGSP\nreal\n\nBottom Rung Spacing\nCUTLAR\nreal(50)\n\nCut Length Array\nEXEXTN\nreal\n\nExit Extension\nEXTOFF\nreal\n\nExit Offset\nGATEHEIGHT\nreal\n\nGate Height\nGATEWD\nreal\n\nGate Width\nHDIST\nreal\n\nHorizontal Distance\nHRSDIS\nreal\n\nHandrail Start Distance\nLDRDIR\ndir\n\nLadder Direction\nLPITCH\nreal\n\nLadder Pitch\nRUNGS\ninteger\ninteger\nNumber of rungs\nSTILEN\nreal\ninteger\nStail length\nTREADO\nreal\n\nTread Overlap\n\nAttribute Name\nData Type\nQualifier\nDescription\nBRNGSP\nreal\nBottom Rung Spacing\nCUTLAR\nreal(50)\nCut Length Array\nEXEXTN\nreal\nExit Extension\nEXTOFF\nreal\nExit Offset\nGATEHEIGHT\nreal\nGate Height\nGATEWD\nreal\nGate Width\nHDIST\nreal\nHorizontal Distance\nHRSDIS\nreal\nHandrail Start Distance\nLDRDIR\ndir\nLadder Direction\nLPITCH\nreal\nLadder Pitch\nRUNGS\ninteger\ninteger\nNumber of rungs\nSTILEN\nreal\ninteger\nStail length\nTREADO\nreal\nTread Overlap\n\n\n"}
{"Headers": "Attribute Category: Laser", "Content": "LMDREF\nelement(20)\n\nBack reference to demolition packages referencing laser survey\nLMDSES\ninteger(10)\n\nSession number of back reference to demolition packages referencing laser survey\nLMDSYN\nstring(700)\n\nSynchronisation state of AVEVA and laser survey databases\nMODID\nstring(2000)\n\nUsed by laser driver to identify external laser data\nVENID\nstring(120)\n\nDriver definition used to access external laser survey\n\nAttribute Name\nData Type\nQualifier\nDescription\nLMDREF\nelement(20)\nBack reference to demolition packages referencing laser survey\nLMDSES\ninteger(10)\nSession number of back reference to demolition packages referencing laser survey\nLMDSYN\nstring(700)\nSynchronisation state of AVEVA and laser survey databases\nMODID\nstring(2000)\nUsed by laser driver to identify external laser data\nVENID\nstring(120)\nDriver definition used to access external laser survey\n\n\n"}
{"Headers": "Attribute Category: LEXICON", "Content": "ISKEYDB\nlogical\n\nDoes ukey incorporate DB number\nTMPLTF\nstring(2000)\n\nDatasheet Template filename\nUDATLS\nword(200)\n\nList of attributes for UDET\nUDPMEM\nword(500)\n\nPossible type members for a UDET\nUDPOWN\nword(500)\n\nPossible owners for a UDET\n\nAttribute Name\nData Type\nQualifier\nDescription\nISKEYDB\nlogical\nDoes ukey incorporate DB number\nTMPLTF\nstring(2000)\nDatasheet Template filename\nUDATLS\nword(200)\nList of attributes for UDET\nUDPMEM\nword(500)\nPossible type members for a UDET\nUDPOWN\nword(500)\nPossible owners for a UDET\n\n\n"}
{"Headers": "Attribute Category: Link Related", "Content": "DBLNKP\nlogical\n\nLinked Documents (DB) distribution flag\nLNKCLS\nelement(500)\n\nClasses referencing a DocLink\nLNKDOC\nelement(500)\n\nDocLinks referring to element\nLNKELE\nelement(500)\n\nElements referencing a DocLink\nLNKREF\nelement\n\nReference internal document (drawing/sheet)\nLNPRXS\nelement(500)\n\nProxy items referring to element\nURL\nstring(1024)\n\nURL\n\nAttribute Name\nData Type\nQualifier\nDescription\nDBLNKP\nlogical\nLinked Documents (DB) distribution flag\nLNKCLS\nelement(500)\nClasses referencing a DocLink\nLNKDOC\nelement(500)\nDocLinks referring to element\nLNKELE\nelement(500)\nElements referencing a DocLink\nLNKREF\nelement\nReference internal document (drawing/sheet)\nLNPRXS\nelement(500)\nProxy items referring to element\nURL\nstring(1024)\nURL\n\n\n"}
{"Headers": "Attribute Category: Local Name Related", "Content": "LNAME\nstring(21)\n\nLocal name as stored on template\nLNLST\nstring(2000)\n\nList of local names for current template\nRSEQFA\nelement(500)\n\nRule sequence ref array for local names\nRSEQN\ninteger\n\nSequence number for rule execution\n\nAttribute Name\nData Type\nQualifier\nDescription\nLNAME\nstring(21)\nLocal name as stored on template\nLNLST\nstring(2000)\nList of local names for current template\nRSEQFA\nelement(500)\nRule sequence ref array for local names\nRSEQN\ninteger\nSequence number for rule execution\n\n\n"}
{"Headers": "Attribute Category: Manufacturing", "Content": "FSETWE\nreal\n\nFastener Set Weight\nORDARE\nreal\n\nSurface Area\nORDWEI\nreal\n\nOrder Weight\n\nAttribute Name\nData Type\nQualifier\nDescription\nFSETWE\nreal\nFastener Set Weight\nORDARE\nreal\nSurface Area\nORDWEI\nreal\nOrder Weight\n\n\n"}
{"Headers": "Attribute Category: Mass Properties", "Content": "DNST\nreal\n\nDensity\nFNCTAR\nreal\n\nTotal area\nGCOF\npos\n\nGross centre of gravity\nGMOF\nreal(9)\n\nGross moments of inertia\nGSRF\nreal\n\nGross surface area\nGVOL\nreal\n\nGross volume\nGWEI\nreal\n\nGross weight\nHCOFG\npos\n\ncomputed hull item centre of gravity\nHSRFA\nreal\n\nComputed Hull item surface area\nHVOLU\nreal\n\nComputed Hull Item volume\nMOFI\npos\n\nMoment of Inertia\nNCOF\npos\n\nNett centre of gravity\nNMOF\nreal(9)\n\nNett moments of inertia\nNSRF\nreal\n\nNett surface area\nNVOL\nreal\n\nNett volume\nNWEI\nreal\n\nNett weight\nRCOF\npos\n\nRough centre of gravity\nRMOF\nreal(9)\n\nRough moments of inertia\nRSRF\nreal\n\nRough surface area\nRVOL\nreal\n\nRough gross volume\nRWEI\nreal\n\nRough weight\nSUWGAL\nreal\n\nSupport + Supported ALL Gross Weight ALL\nSUWGSA\nreal\n\nSupported ALL Gross weight\nSUWGST\nreal\n\nSupported Gross weight\nSUWNAL\nreal\n\nSupport + Supported Nett weight ALL\nSUWNSA\nreal\n\nSupported ALL Nett weight\nSUWNST\nreal\n\nSupported Nett weight\nSUWRAL\nreal\n\nSupport + Supported Rough Weight ALL\nSUWRSA\nreal\n\nSupported ALL Rough weight\nSUWRST\nreal\n\nSupported Rough weight\nUSCCOG\npos\n\nUser derived centre of gravity position\nUSCWCO\npos\n\nUser derived wet centre of gravity position\nUSCWEI\nreal\n\nDerived value for user weight\nUSCWWE\nreal\n\nDerived value for user wet weight\n\nAttribute Name\nData Type\nQualifier\nDescription\nDNST\nreal\nDensity\nFNCTAR\nreal\nTotal area\nGCOF\npos\nGross centre of gravity\nGMOF\nreal(9)\nGross moments of inertia\nGSRF\nreal\nGross surface area\nGVOL\nreal\nGross volume\nGWEI\nreal\nGross weight\nHCOFG\npos\ncomputed hull item centre of gravity\nHSRFA\nreal\nComputed Hull item surface area\nHVOLU\nreal\nComputed Hull Item volume\nMOFI\npos\nMoment of Inertia\nNCOF\npos\nNett centre of gravity\nNMOF\nreal(9)\nNett moments of inertia\nNSRF\nreal\nNett surface area\nNVOL\nreal\nNett volume\nNWEI\nreal\nNett weight\nRCOF\npos\nRough centre of gravity\nRMOF\nreal(9)\nRough moments of inertia\nRSRF\nreal\nRough surface area\nRVOL\nreal\nRough gross volume\nRWEI\nreal\nRough weight\nSUWGAL\nreal\nSupport + Supported ALL Gross Weight ALL\nSUWGSA\nreal\nSupported ALL Gross weight\nSUWGST\nreal\nSupported Gross weight\nSUWNAL\nreal\nSupport + Supported Nett weight ALL\nSUWNSA\nreal\nSupported ALL Nett weight\nSUWNST\nreal\nSupported Nett weight\nSUWRAL\nreal\nSupport + Supported Rough Weight ALL\nSUWRSA\nreal\nSupported ALL Rough weight\nSUWRST\nreal\nSupported Rough weight\nUSCCOG\npos\nUser derived centre of gravity position\nUSCWCO\npos\nUser derived wet centre of gravity position\nUSCWEI\nreal\nDerived value for user weight\nUSCWWE\nreal\nDerived value for user wet weight\n\n\n"}
{"Headers": "Attribute Category: Mitred Bend", "Content": "ACTANG\nreal\n\nActual angle of a bend\nACTNCU\ninteger\n\nActual number of cuts of a bend\nACTRAD\nreal\n\nActual radius of a bend\nBSCANG\nreal\n\nBend Segment Cut Angle\nBSCLL\nreal\n\nCentre-Line Length of a mitred Bend Segment\nBSMNIL\nreal\n\nMinimum Length of Insulation of a mitred Bend Segment\nBSMNL\nreal\n\nMinimum Length of a mitred Bend Segment\nBSMXIL\nreal\n\nMaximum Length of Insulation of a mitred Bend Segment\nBSMXL\nreal\n\nMaximum Length of a mitred Bend Segment\nBVSCLL\nreal\n\nCentre-Line Length of a mitred Bend Segment\nBVSMNI\nreal\n\nMinimum Length of Insulation of a Virtual mitred Bend end-Segment\nBVSMNL\nreal\n\nMinimum Length of a virtual mitred Bend end-Segment\nBVSMXI\nreal\n\nMaximum Length of Insulation of a Virtual mitred Bend end-Segment\nBVSMXL\nreal\n\nMaximum Length of a virtual mitred Bend end-Segment\n\nAttribute Name\nData Type\nQualifier\nDescription\nACTANG\nreal\nActual angle of a bend\nACTNCU\ninteger\nActual number of cuts of a bend\nACTRAD\nreal\nActual radius of a bend\nBSCANG\nreal\nBend Segment Cut Angle\nBSCLL\nreal\nCentre-Line Length of a mitred Bend Segment\nBSMNIL\nreal\nMinimum Length of Insulation of a mitred Bend Segment\nBSMNL\nreal\nMinimum Length of a mitred Bend Segment\nBSMXIL\nreal\nMaximum Length of Insulation of a mitred Bend Segment\nBSMXL\nreal\nMaximum Length of a mitred Bend Segment\nBVSCLL\nreal\nCentre-Line Length of a mitred Bend Segment\nBVSMNI\nreal\nMinimum Length of Insulation of a Virtual mitred Bend end-Segment\nBVSMNL\nreal\nMinimum Length of a virtual mitred Bend end-Segment\nBVSMXI\nreal\nMaximum Length of Insulation of a Virtual mitred Bend end-Segment\nBVSMXL\nreal\nMaximum Length of a virtual mitred Bend end-Segment\n\n\n"}
{"Headers": "Attribute Category: Name Related", "Content": "CUTNAM\nstring(700)\ninteger\nFull name of element, truncated to n characters\nCUTNMN\nstring(700)\ninteger\nFull name of element (without leading slash) truncated to n characters\nFLNM\nstring(700)\n\nFull name of the element\nFLNN\nstring(700)\n\nName of the element\nIDSPU\ninteger\n\nSpecified unique identifier\nISNAMED\nlogical\n\nTrue if element is named\nNAMESQ\nstring(700)\n\nType. sequence number and name of element\nNAMETY\nstring(700)\n\nType and name of the element\nNAMN\nstring(500)\n\nName of the element (without leading slash)\nNAMTYP\nstring(700)\n\nType and full name of element\nRAWNAM\nstring(500)\n\nName only\n\nAttribute Name\nData Type\nQualifier\nDescription\nCUTNAM\nstring(700)\ninteger\nFull name of element, truncated to n characters\nCUTNMN\nstring(700)\ninteger\nFull name of element (without leading slash) truncated to n characters\nFLNM\nstring(700)\nFull name of the element\nFLNN\nstring(700)\nName of the element\nIDSPU\ninteger\nSpecified unique identifier\nISNAMED\nlogical\nTrue if element is named\nNAMESQ\nstring(700)\nType. sequence number and name of element\nNAMETY\nstring(700)\nType and name of the element\nNAMN\nstring(500)\nName of the element (without leading slash)\nNAMTYP\nstring(700)\nType and full name of element\nRAWNAM\nstring(500)\nName only\n\n\n"}
{"Headers": "Attribute Category: NoOfPosts", "Content": "NPOST\ninteger\n\nNumber of Posts\n\nAttribute Name\nData Type\nQualifier\nDescription\nNPOST\ninteger\nNumber of Posts\n\n\n"}
{"Headers": "Attribute Category: Nuclear Applications", "Content": "MATPURPOSE\nword\n\nMaterial purpose\nNUCDNA\nreal\n\nDistance to nearest anchor\nNUCDNE\nreal\n\nDistance to the Nearest Edge\nNUCDNR\nelement(2)\n\nNearest Adjacent Anchor\n\nAttribute Name\nData Type\nQualifier\nDescription\nMATPURPOSE\nword\nMaterial purpose\nNUCDNA\nreal\nDistance to nearest anchor\nNUCDNE\nreal\nDistance to the Nearest Edge\nNUCDNR\nelement(2)\nNearest Adjacent Anchor\n\n\n"}
{"Headers": "Attribute Category: Other Design", "Content": "AUTCOL\nreal(3)\n\nDesign rgb autocolour\nAVRAD\nreal\n\nAverage radius for a CTOR or RTOR\nDOCREF\nelement\n\nDocument reference\nDOCXRF\nelement(500)\n\nReturn reference from Design element to DOCITM element\nFULLID\nstring(20)\n\nFull ID Plane\nGRDID\nstring(20)\n\nGrid plane index\nGRDLBL\nstring(120)\n\nPlanes Label\nIDPREF\nstring(20)\n\nID Prefix\nIFCUID\nstring(160)\n\nUniversally unique identifier from external sources (in IFC format)\nMODSTA\nstring(20)\n\nCreation Status of Models as enumerated\nNCONNE\ninteger\n\nMismatched connections. i.e. no valid backpointer\n\nAttribute Name\nData Type\nQualifier\nDescription\nAUTCOL\nreal(3)\nDesign rgb autocolour\nAVRAD\nreal\nAverage radius for a CTOR or RTOR\nDOCREF\nelement\nDocument reference\nDOCXRF\nelement(500)\nReturn reference from Design element to DOCITM element\nFULLID\nstring(20)\nFull ID Plane\nGRDID\nstring(20)\nGrid plane index\nGRDLBL\nstring(120)\nPlanes Label\nIDPREF\nstring(20)\nID Prefix\nIFCUID\nstring(160)\nUniversally unique identifier from external sources (in IFC format)\nMODSTA\nstring(20)\nCreation Status of Models as enumerated\nNCONNE\ninteger\nMismatched connections. i.e. no valid backpointer\n\n\n"}
{"Headers": "Attribute Category: Piping", "Content": "ARRI\ninteger\n\nArrive Ppoint\nATCLL\nreal\n\nCentre-line length of arrive implied tube\nATLE\nreal\n\nLength of arrive implied tube\nCEND\nstring\n\nConnection at other end of CREF (HEAD or TAIL)\nFITLEN\nreal\n\nLength of branch fitting\nGRDE\nreal\n\nGradient of implied tube. Gradient is the vertical rise(fall) divided by the horizontal distance.\nHDIR\ndir\n\nHead direction\nINLEN\nreal\n\nInsulation length\nINTHK\nreal\n\nInsulation thickness\nITLE\nreal\n\nLength of implied tube\nITPS\npos\n\nPosition of implied tube\nLEAV\ninteger\n\nLeave Ppoint\nLTCLL\nreal\n\nCentre-line length of leave implied tube\nLTLE\nreal\n\nLength of leave implied tube\nMTBE\nelement\n\nMaterial tube start. The first component, excluding ATTSs, for whom the LOFF is invalid or false\nMTCL\nreal\n\nMaterial tube centreline length.\nMTEN\nelement\n\nMaterial tube end. The first component, excluding ATTSs, for whom the LOFF is invalid or false\nMTLE\nreal\n\nMaterial tube length for TUBI. Includes preceding bend length if bend is offline.\nMTOL\nstring(1000)\n\nMaterial List Length\nMTOQ\nstring(1000)\n\nMaterial take off quantity\nPCREF\ninteger(4)\ninteger\nPpoint and ref of connected piping component\nPOCK\nword\n\nIs a branch component in a pocket\nROBRRU\nelement(500)\n\nRouter Rules applying to a piping element or members\nSTAP\nreal\n\nLength of arrive straight tube\nSTLE\nreal\n\nLength of leave straight tube\nTDIR\ndir\n\nTail direction\nTEXIST\nlogical\n\nTrue if component has TUBI. Always true for offline bends.\nTGEOM\nlogical\n\nTrue if component has TUBI geometry\nTRLEN\nreal\n\nTracing length\n\nAttribute Name\nData Type\nQualifier\nDescription\nARRI\ninteger\nArrive Ppoint\nATCLL\nreal\nCentre-line length of arrive implied tube\nATLE\nreal\nLength of arrive implied tube\nCEND\nstring\nConnection at other end of CREF (HEAD or TAIL)\nFITLEN\nreal\nLength of branch fitting\nGRDE\nreal\nGradient of implied tube. Gradient is the vertical rise(fall) divided by the horizontal distance.\nHDIR\ndir\nHead direction\nINLEN\nreal\nInsulation length\nINTHK\nreal\nInsulation thickness\nITLE\nreal\nLength of implied tube\nITPS\npos\nPosition of implied tube\nLEAV\ninteger\nLeave Ppoint\nLTCLL\nreal\nCentre-line length of leave implied tube\nLTLE\nreal\nLength of leave implied tube\nMTBE\nelement\nMaterial tube start. The first component, excluding ATTSs, for whom the LOFF is invalid or false\nMTCL\nreal\nMaterial tube centreline length.\nMTEN\nelement\nMaterial tube end. The first component, excluding ATTSs, for whom the LOFF is invalid or false\nMTLE\nreal\nMaterial tube length for TUBI. Includes preceding bend length if bend is offline.\nMTOL\nstring(1000)\nMaterial List Length\nMTOQ\nstring(1000)\nMaterial take off quantity\nPCREF\ninteger(4)\ninteger\nPpoint and ref of connected piping component\nPOCK\nword\nIs a branch component in a pocket\nROBRRU\nelement(500)\nRouter Rules applying to a piping element or members\nSTAP\nreal\nLength of arrive straight tube\nSTLE\nreal\nLength of leave straight tube\nTDIR\ndir\nTail direction\nTEXIST\nlogical\nTrue if component has TUBI. Always true for offline bends.\nTGEOM\nlogical\nTrue if component has TUBI geometry\nTRLEN\nreal\nTracing length\n\n\n"}
{"Headers": "Attribute Category: Pipe Piece", "Content": "AELRFA\nelement(500)\n\nBoundary components for the PipePiece\nBELRFA\nelement(500)\n\nAll components in the PipePiece\nBELTYP\ninteger(500)\n\nAll component types in the PipeSpool\nCMPRFA\nelement(500)\n\nAll components for the PipePiece\nHSVLD\nlogical\n\nHVACspool valid\nMELRFA\nelement(500)\n\nAll components (non-tube) in the PipePiece\nPCRFA\nelement(500)\n\nAll spools that contain this element\nPPANFL\nreal\n\nPipe Piece Angle between flanges\nPPAREF\nelement\n\nPipe Piece Arrive Reference\nPPBRAD\nreal(500)\n\nPipe piece bend radii\nPPBRAT\nreal(500)\n\nPipe piece bend ratio\nPPCUTL\nreal\n\nCut Length\nPPEFR\nlogical\n\nLeave flange required\nPPFINL\nreal\n\nFinished Length\nPPFMCV\nlogical\n\nPipe piece fabrication machines verified\nPPLREF\nelement\n\nPipe Piece Leave Reference\nPPRFA\nelement(500)\n\nAll components in the PipePiece\nPPSFR\nlogical\n\nArrive flange required\nPPSTU\nelement\n\nPipe Piece Specification\nPPVBMC\nelement\n\nReturn the bending machine IF the pipe piece is verified\nPPVERI\nword\n\nPipe piece verified\nPPVWMC\nelement\n\nReturn the welding machine IF the pipe piece is verified\nPSVLD\nlogical\n\nPipespool valid\n\nAttribute Name\nData Type\nQualifier\nDescription\nAELRFA\nelement(500)\nBoundary components for the PipePiece\nBELRFA\nelement(500)\nAll components in the PipePiece\nBELTYP\ninteger(500)\nAll component types in the PipeSpool\nCMPRFA\nelement(500)\nAll components for the PipePiece\nHSVLD\nlogical\nHVACspool valid\nMELRFA\nelement(500)\nAll components (non-tube) in the PipePiece\nPCRFA\nelement(500)\nAll spools that contain this element\nPPANFL\nreal\nPipe Piece Angle between flanges\nPPAREF\nelement\nPipe Piece Arrive Reference\nPPBRAD\nreal(500)\nPipe piece bend radii\nPPBRAT\nreal(500)\nPipe piece bend ratio\nPPCUTL\nreal\nCut Length\nPPEFR\nlogical\nLeave flange required\nPPFINL\nreal\nFinished Length\nPPFMCV\nlogical\nPipe piece fabrication machines verified\nPPLREF\nelement\nPipe Piece Leave Reference\nPPRFA\nelement(500)\nAll components in the PipePiece\nPPSFR\nlogical\nArrive flange required\nPPSTU\nelement\nPipe Piece Specification\nPPVBMC\nelement\nReturn the bending machine IF the pipe piece is verified\nPPVERI\nword\nPipe piece verified\nPPVWMC\nelement\nReturn the welding machine IF the pipe piece is verified\nPSVLD\nlogical\nPipespool valid\n\n\n"}
{"Headers": "Attribute Category: Piping Specification", "Content": "ICAT\nelement\n\nInsulation catalogue reference\nIDET\nelement\n\nInsulation detail text reference\nIDRT\nstring(2000)\n\nInsulation detail RTEXT\nIDST\nstring(2000)\n\nInsulation detail STEXT\nIDTT\nstring(2000)\n\nInsulation detail TTEXT\nIMAT\nelement\n\nInsulation material text reference\nIMXT\nstring(2000)\n\nInsulation material XTEXT\nIMYT\nstring(2000)\n\nInsulation material YTEXT\nIMZT\nstring(2000)\n\nInsulation material ZTEXT\nISPR\nelement\n\nInsulation specification component reference\nTCAT\nelement\n\nTrace catalogue reference\nTDET\nelement\n\nTrace detail text reference\nTDRT\nstring(2000)\n\nTrace detail RTEXT\nTDST\nstring(2000)\n\nTrace detail STEXT\nTDTT\nstring(2000)\n\nTrace detail TTEXT\nTMAT\nelement\n\nTrace material text reference\nTMXT\nstring(2000)\n\nTrace material XTEXT\nTMYT\nstring(2000)\n\nTrace material YTEXT\nTMZT\nstring(2000)\n\nTrace material ZTEXT\nTSPR\nelement\n\nTrace specification component reference\n\nAttribute Name\nData Type\nQualifier\nDescription\nICAT\nelement\nInsulation catalogue reference\nIDET\nelement\nInsulation detail text reference\nIDRT\nstring(2000)\nInsulation detail RTEXT\nIDST\nstring(2000)\nInsulation detail STEXT\nIDTT\nstring(2000)\nInsulation detail TTEXT\nIMAT\nelement\nInsulation material text reference\nIMXT\nstring(2000)\nInsulation material XTEXT\nIMYT\nstring(2000)\nInsulation material YTEXT\nIMZT\nstring(2000)\nInsulation material ZTEXT\nISPR\nelement\nInsulation specification component reference\nTCAT\nelement\nTrace catalogue reference\nTDET\nelement\nTrace detail text reference\nTDRT\nstring(2000)\nTrace detail RTEXT\nTDST\nstring(2000)\nTrace detail STEXT\nTDTT\nstring(2000)\nTrace detail TTEXT\nTMAT\nelement\nTrace material text reference\nTMXT\nstring(2000)\nTrace material XTEXT\nTMYT\nstring(2000)\nTrace material YTEXT\nTMZT\nstring(2000)\nTrace material ZTEXT\nTSPR\nelement\nTrace specification component reference\n\n\n"}
{"Headers": "Attribute Category: Pline Related", "Content": "DPKEY\nword\n\nDraft derived Pline identifier key\nPKEY\nword\n\nPline identifier key\nPLCN\nlogical\nword\nPline centreline flag\nPLCO\nword\nword\nPline connection\nPLDE\nstring(120)\nword\nPline description\nPLEN\npos\nword\nPline end\nPLENCU\npos\nword\nPline end, allowing for cutback\nPLLE\ninteger(2)\nword\nPline level\nPLLS\nword(100)\n\nList of valid Plines\nPLNA\nword(100)\n\nList of available Pline names\nPLOR\nori\nword\nPline orientation\nPLPU\nword\nword\nPline purpose\nPLREFS\nelement(5000)\n\nPline references\nPLST\npos\nword\nPline start\nPLSTCU\npos\nword\nPline start, allowing for cutback\nPLTU\nlogical\nword\nPline tube flag\nPLVI\nword(200)\n\nList of visible Plines\nPLVIF\ninteger\nword\nPline visibility flag\n\nAttribute Name\nData Type\nQualifier\nDescription\nDPKEY\nword\nDraft derived Pline identifier key\nPKEY\nword\nPline identifier key\nPLCN\nlogical\nword\nPline centreline flag\nPLCO\nword\nword\nPline connection\nPLDE\nstring(120)\nword\nPline description\nPLEN\npos\nword\nPline end\nPLENCU\npos\nword\nPline end, allowing for cutback\nPLLE\ninteger(2)\nword\nPline level\nPLLS\nword(100)\nList of valid Plines\nPLNA\nword(100)\nList of available Pline names\nPLOR\nori\nword\nPline orientation\nPLPU\nword\nword\nPline purpose\nPLREFS\nelement(5000)\nPline references\nPLST\npos\nword\nPline start\nPLSTCU\npos\nword\nPline start, allowing for cutback\nPLTU\nlogical\nword\nPline tube flag\nPLVI\nword(200)\nList of visible Plines\nPLVIF\ninteger\nword\nPline visibility flag\n\n\n"}
{"Headers": "Attribute Category: Positional", "Content": "D\nreal\n\nPosition downing\nDRPS\npos\n\nDerived position for steelwork\nE\nreal\n\nPosition easting\nEASTING\npos\n\nEasting part expressed as a position\nEVOL\nreal(6)\n\nEnclosing box volume in given coordinates\nFNCCOA\npos\n\nCentre of Area\nGRDAXE\nstring\n\nGrid axes\nGRDDIR\ndir\n\nGrid direction\nGRDPOS\npos\n\nGrid Position\nGRIDX\nstring(20)\n\nGrid X position\nGRIDY\nstring(20)\n\nGrid Y position\nGRIDZ\nstring(20)\n\nGrid Z position\nN\nreal\n\nPosition northing\nNORTHING\npos\n\nNorthing part expressed as a position\nNPOSE\nreal\n\nEasting of position wrt owner\nNPOSN\nreal\n\nNorthing of position wrt owner\nNPOSU\nreal\n\nUpping of position wrt owner\nORI\nori\n\nOrientation\nORIA\nreal(3)\n\nOrientation as angles\nPACTDI\ndir\ninteger\nPpoint actual direction\nPOS\npos\n\nPosition\nPOSN\nreal\n\nNorthing of position\nPOSU\nreal\n\nUpping of position\nPOSX\nreal\n\nEasting (X coordinate) of position\nS\nreal\n\nPosition southing\nSHIPX\nstring(20)\n\nShip X position\nSHIPY\nstring(20)\n\nShip Y position\nSHIPZ\nstring(20)\n\nShip Z position\nTRANS\nreal(12)\n\nLocal transformation matrix\nU\nreal\n\nPosition upping\nUPPING\npos\n\nUpping part expressed as a position\nW\nreal\n\nPosition westing\nWORI\nori\n\nWorld orientation\nWORPOS\npos\n\nWorld position\nWTRANS\nreal(12)\n\nTransformation matrix to world\n\nAttribute Name\nData Type\nQualifier\nDescription\nD\nreal\nPosition downing\nDRPS\npos\nDerived position for steelwork\nE\nreal\nPosition easting\nEASTING\npos\nEasting part expressed as a position\nEVOL\nreal(6)\nEnclosing box volume in given coordinates\nFNCCOA\npos\nCentre of Area\nGRDAXE\nstring\nGrid axes\nGRDDIR\ndir\nGrid direction\nGRDPOS\npos\nGrid Position\nGRIDX\nstring(20)\nGrid X position\nGRIDY\nstring(20)\nGrid Y position\nGRIDZ\nstring(20)\nGrid Z position\nN\nreal\nPosition northing\nNORTHING\npos\nNorthing part expressed as a position\nNPOSE\nreal\nEasting of position wrt owner\nNPOSN\nreal\nNorthing of position wrt owner\nNPOSU\nreal\nUpping of position wrt owner\nORI\nori\nOrientation\nORIA\nreal(3)\nOrientation as angles\nPACTDI\ndir\ninteger\nPpoint actual direction\nPOS\npos\nPosition\nPOSN\nreal\nNorthing of position\nPOSU\nreal\nUpping of position\nPOSX\nreal\nEasting (X coordinate) of position\nS\nreal\nPosition southing\nSHIPX\nstring(20)\nShip X position\nSHIPY\nstring(20)\nShip Y position\nSHIPZ\nstring(20)\nShip Z position\nTRANS\nreal(12)\nLocal transformation matrix\nU\nreal\nPosition upping\nUPPING\npos\nUpping part expressed as a position\nW\nreal\nPosition westing\nWORI\nori\nWorld orientation\nWORPOS\npos\nWorld position\nWTRANS\nreal(12)\nTransformation matrix to world\n\n\n"}
{"Headers": "Attribute Category: PPoint Related", "Content": "BRANBO\nreal(200)\n\nArray of branch bore excluding arrive and leave\nBRANDI\nstringarray(200)\n\nArray of branch bore direction excluding the arrive and leave\nDWDIR\ndir\n\nDraft world direction for pline or ppoint\nDWPOS\npos\n\nDraft world position for pline or ppoint\nLVDWPO\nlogical\n\nTRUE if valid Draft pline point or ppoint\nPCONDE\nstring(120)\ninteger\nPpoint connection description\nPDIR\ndir\ninteger\nPpoint direction\nPGRD\nreal\ninteger\nPpoint gradient\nPOD\nreal\ninteger\nPpoint outside diameter\nPPBO\nreal\ninteger\nPpoint bore\nPPCO\nword\ninteger\nPpoint connection type\nPPCOU\ninteger\n\nNumber of valid Ppoints\nPPDE\nstring(120)\ninteger\nPpoint description\nPPEXST\nlogical\ninteger\nTrue if Ppoint exists\nPPLS\ninteger(200)\n\nList of valid Ppoints\nPPOS\npos\ninteger\nPpoint position\nPPSK\nword\ninteger\nPpoint pskey\nPPUR\nword\ninteger\nPpoint purpose\nPPVI\ninteger(200)\n\nList of visible Ppoints\nPPVIF\ninteger\ninteger\nPpoint visibility flag\nPSLDIR\ndir\ninteger\nPpoint slope direction\nPSPIN\ninteger\n\nPpoint number showing position of spindle\nPZDIR\ndir\ninteger\nPpoint alignment direction\n\nAttribute Name\nData Type\nQualifier\nDescription\nBRANBO\nreal(200)\nArray of branch bore excluding arrive and leave\nBRANDI\nstringarray(200)\nArray of branch bore direction excluding the arrive and leave\nDWDIR\ndir\nDraft world direction for pline or ppoint\nDWPOS\npos\nDraft world position for pline or ppoint\nLVDWPO\nlogical\nTRUE if valid Draft pline point or ppoint\nPCONDE\nstring(120)\ninteger\nPpoint connection description\nPDIR\ndir\ninteger\nPpoint direction\nPGRD\nreal\ninteger\nPpoint gradient\nPOD\nreal\ninteger\nPpoint outside diameter\nPPBO\nreal\ninteger\nPpoint bore\nPPCO\nword\ninteger\nPpoint connection type\nPPCOU\ninteger\nNumber of valid Ppoints\nPPDE\nstring(120)\ninteger\nPpoint description\nPPEXST\nlogical\ninteger\nTrue if Ppoint exists\nPPLS\ninteger(200)\nList of valid Ppoints\nPPOS\npos\ninteger\nPpoint position\nPPSK\nword\ninteger\nPpoint pskey\nPPUR\nword\ninteger\nPpoint purpose\nPPVI\ninteger(200)\nList of visible Ppoints\nPPVIF\ninteger\ninteger\nPpoint visibility flag\nPSLDIR\ndir\ninteger\nPpoint slope direction\nPSPIN\ninteger\nPpoint number showing position of spindle\nPZDIR\ndir\ninteger\nPpoint alignment direction\n\n\n"}
{"Headers": "Attribute Category: Presentation Related", "Content": "ICOTYP\nstring(300)\n\nIcon used for element\n\nAttribute Name\nData Type\nQualifier\nDescription\nICOTYP\nstring(300)\nIcon used for element\n\n\n"}
{"Headers": "Attribute Category: Project Copy", "Content": "PCPIDV\nelement(10000)\n\nEnabled for project copy\nPCPSET\nelement(10000)\n\nEnabled for project copy\n\nAttribute Name\nData Type\nQualifier\nDescription\nPCPIDV\nelement(10000)\nEnabled for project copy\nPCPSET\nelement(10000)\nEnabled for project copy\n\n\n"}
{"Headers": "Attribute Category: Properties", "Content": "GPRTRE\nelement(100)\n\nGpart reference\n\nAttribute Name\nData Type\nQualifier\nDescription\nGPRTRE\nelement(100)\nGpart reference\n\n\n"}
{"Headers": "Attribute Category: Repeats Related", "Content": "REPSEQ\ninteger\n\nSequence no. for template repeat element\nTMRXREF\nelement(500)\n\nReturn reference from TMRREL element to repeat elements\n\nAttribute Name\nData Type\nQualifier\nDescription\nREPSEQ\ninteger\nSequence no. for template repeat element\nTMRXREF\nelement(500)\nReturn reference from TMRREL element to repeat elements\n\n\n"}
{"Headers": "Attribute Category: Rules Related", "Content": "DEPATT\nword(2000)\n\nAttributes that a rule or catalogue parameterised expression is dependent upon\nNRULEE\ninteger\n\nNumber of rule inconsistencies on element\nRCOU\ninteger\n\nNumber of rules on element\nRULEER\nstring(300)\ninteger\nText of \"nth\" rule error\nRULSET\nword(2000)\n\nList of rules set\nSUBRUL\ninteger(200)\nattr\nList of subrule indexes for given rule\n\nAttribute Name\nData Type\nQualifier\nDescription\nDEPATT\nword(2000)\nAttributes that a rule or catalogue parameterised expression is dependent upon\nNRULEE\ninteger\nNumber of rule inconsistencies on element\nRCOU\ninteger\nNumber of rules on element\nRULEER\nstring(300)\ninteger\nText of \"nth\" rule error\nRULSET\nword(2000)\nList of rules set\nSUBRUL\ninteger(200)\nattr\nList of subrule indexes for given rule\n\n\n"}
{"Headers": "Attribute Category: Schematics", "Content": "BRALNK\nelement(20)\n\nConnectivity SCBRAN-BRANCH Link\nCMPLNK\nelement\n\nReturn reference from schematic or design element to CYMLNK element\nCMPSTS\nstring(120)\n\nConnectivity comparison status description\nDESLNK\nelement(20)\n\nConnectivity Design Model Link\nDIAREF\nelement(500)\n\nDiagram reference array for schematic elements\nENGLNK\nelement\n\nEngineering Element Link\nGRIDXPOS\nstring\n\nX position of the symbol according to the gridding definition\nGRIDYPOS\nstring\n\nY position of the symbol according to the gridding definition\nILPBUA\nstring(120)\n\nReturn Integrator Build Area derived from Area Limit Point Labels\nLLDIAGRAMS\nstring(2000)\n\nLine list diagrams\nLLENTRY\nlogical\n\nIs a line list entry - true or false\nLLFROM\nstring(2000)\n\nFrom column text for a line list\nLLTBRANCH\nelement\n\nLine list tail branch\nLLTO\nstring(2000)\n\nTo column text for a line list\nMANLNK\nelement\n\nManufacturing Element Link\nNVIEWF\nstring(73)\ninteger\nNeutral viewer filename\nPAGE\ninteger(500)\n\nPage in diagram\nRECOMM\nstring(256)\n\nRelease to 3D comment\nREDATE\nstring(12)\n\nRelease to 3D date\nRESTAT\ninteger\n\nRelease to 3D status\nREUSER\nstring(12)\n\nRelease to 3D user\nSCBREF\nelement(50)\n\nSchematic element back reference\nSCEIRE\nelement(60)\n\nEnhanced instrument relationship\nSCELOR\nelement(20)\n\nEnhanced instrumentation loop reference array for schematic elements\nSCHELE\nelement\n\nSchematic head element\nSCHLNK\nelement\n\nConnectivity Schematic Link\nSCIERTYPE\nword(60)\n\nInstrument enhanced reference type\nSCIIRE\nelement(50)\n\nInstrument to instrument reference\nSCIIRTYPE\nword(50)\n\nInstrument to instrument reference type\nSCIPRE\nelement(50)\n\nInstrument process reference\nSCIPRTYPE\nword(50)\n\nInstrument process reference type\nSCIREL\nelement(50)\n\nInstrument relationship\nSCIRLTYPE\nword(50)\n\nInstrument relationship type\nSCTELE\nelement\n\nSchematic tail element\nSPLLNK\nelement\n\nSpooler Element Link\nSTEREF\nelement(500)\n\nStencil reference array for schematic elements\nVISF\nstring(73)\n\nVisio filename\n\nAttribute Name\nData Type\nQualifier\nDescription\nBRALNK\nelement(20)\nConnectivity SCBRAN-BRANCH Link\nCMPLNK\nelement\nReturn reference from schematic or design element to CYMLNK element\nCMPSTS\nstring(120)\nConnectivity comparison status description\nDESLNK\nelement(20)\nConnectivity Design Model Link\nDIAREF\nelement(500)\nDiagram reference array for schematic elements\nENGLNK\nelement\nEngineering Element Link\nGRIDXPOS\nstring\nX position of the symbol according to the gridding definition\nGRIDYPOS\nstring\nY position of the symbol according to the gridding definition\nILPBUA\nstring(120)\nReturn Integrator Build Area derived from Area Limit Point Labels\nLLDIAGRAMS\nstring(2000)\nLine list diagrams\nLLENTRY\nlogical\nIs a line list entry - true or false\nLLFROM\nstring(2000)\nFrom column text for a line list\nLLTBRANCH\nelement\nLine list tail branch\nLLTO\nstring(2000)\nTo column text for a line list\nMANLNK\nelement\nManufacturing Element Link\nNVIEWF\nstring(73)\ninteger\nNeutral viewer filename\nPAGE\ninteger(500)\nPage in diagram\nRECOMM\nstring(256)\nRelease to 3D comment\nREDATE\nstring(12)\nRelease to 3D date\nRESTAT\ninteger\nRelease to 3D status\nREUSER\nstring(12)\nRelease to 3D user\nSCBREF\nelement(50)\nSchematic element back reference\nSCEIRE\nelement(60)\nEnhanced instrument relationship\nSCELOR\nelement(20)\nEnhanced instrumentation loop reference array for schematic elements\nSCHELE\nelement\nSchematic head element\nSCHLNK\nelement\nConnectivity Schematic Link\nSCIERTYPE\nword(60)\nInstrument enhanced reference type\nSCIIRE\nelement(50)\nInstrument to instrument reference\nSCIIRTYPE\nword(50)\nInstrument to instrument reference type\nSCIPRE\nelement(50)\nInstrument process reference\nSCIPRTYPE\nword(50)\nInstrument process reference type\nSCIREL\nelement(50)\nInstrument relationship\nSCIRLTYPE\nword(50)\nInstrument relationship type\nSCTELE\nelement\nSchematic tail element\nSPLLNK\nelement\nSpooler Element Link\nSTEREF\nelement(500)\nStencil reference array for schematic elements\nVISF\nstring(73)\nVisio filename\n\n\n"}
{"Headers": "Attribute Category: Space Management", "Content": "FAATYP\nstring(20)\n\nType of area world as enumerated\nFCATYP\nstring(20)\n\nType of curve world as enumerated\nFNCAA\nelement\npos, dir, integer\nReturns an adjoining area given a point and location vector.\nFNCAFP\nelement\npos, dir, integer\nReturns the functional area that contains the given point\nFNCCL\nelement\npos, dir, integer\nReturns the closest limit to a point within an area.\nFNCLCB\nreal\n\nLength of curve branch\nFNCLOB\nreal\n\nLength of boundary\nPTFA\nelement(3)\n\nPoint references\nPTRF\nelement\n\nPoint reference\nREFSUR\nelement\n\nReference to surface instance\nRSOPP\nelement\npos\nReturns the planar panel given an RSO and a point.\nRSOPPT\nreal\npos\nReturns the thickness of the selected planar panel.\nSPMAAS\nelement(500)\npos\nFinds all adjoining spaces of a given space and point.\nSPMARA\nreal\n\nArea of face\nSPMAS\nelement\npos\nReturns an adjoining space given a point and location vector.\nSPMBOX\nreal(6)\n\nBounding box\nSPMCF\nelement\npos\nReturns the closest face to a point within a space.\nSPMCFA\nreal\n\nFloor area\nSPMCLI\nword(2000)\n\nList of customer attributes for space\nSPMCOV\npos\n\nCentre of Volume\nSPMFAR\nreal\n\nFace area\nSPMFLW\nreal\n\nFull load weight\nSPMFRM\nelement\npos, dir, integer\nReturns the first reference model a ray intersects\nSPMMVO\nreal\n\nTotal (moulded) volume\nSPMNVO\nreal\n\nNet volume\nSPMOTP\nstring(20)\n\nType of space management operation as enumerated\nSPMRSO\nelement\n\nReturns the RSO of the face.\nSPMSFP\nelement\n\nReturns the space that contains the given point\nSPMTYP\nstring(20)\n\nType of space world as enumerated\nSPMVOI\ninteger\n\nSpace void marker\n\nAttribute\nData Type\nQualifier\nDescription\nFAATYP\nstring(20)\nType of area world as enumerated\nFCATYP\nstring(20)\nType of curve world as enumerated\nFNCAA\nelement\npos, dir, integer\nReturns an adjoining area given a point and location vector.\nFNCAFP\nelement\npos, dir, integer\nReturns the functional area that contains the given point\nFNCCL\nelement\npos, dir, integer\nReturns the closest limit to a point within an area.\nFNCLCB\nreal\nLength of curve branch\nFNCLOB\nreal\nLength of boundary\nPTFA\nelement(3)\nPoint references\nPTRF\nelement\nPoint reference\nREFSUR\nelement\nReference to surface instance\nRSOPP\nelement\npos\nReturns the planar panel given an RSO and a point.\nRSOPPT\nreal\npos\nReturns the thickness of the selected planar panel.\nSPMAAS\nelement(500)\npos\nFinds all adjoining spaces of a given space and point.\nSPMARA\nreal\nArea of face\nSPMAS\nelement\npos\nReturns an adjoining space given a point and location vector.\nSPMBOX\nreal(6)\nBounding box\nSPMCF\nelement\npos\nReturns the closest face to a point within a space.\nSPMCFA\nreal\nFloor area\nSPMCLI\nword(2000)\nList of customer attributes for space\nSPMCOV\npos\nCentre of Volume\nSPMFAR\nreal\nFace area\nSPMFLW\nreal\nFull load weight\nSPMFRM\nelement\npos, dir, integer\nReturns the first reference model a ray intersects\nSPMMVO\nreal\nTotal (moulded) volume\nSPMNVO\nreal\nNet volume\nSPMOTP\nstring(20)\nType of space management operation as enumerated\nSPMRSO\nelement\nReturns the RSO of the face.\nSPMSFP\nelement\nReturns the space that contains the given point\nSPMTYP\nstring(20)\nType of space world as enumerated\nSPMVOI\ninteger\nSpace void marker\n\n\n"}
{"Headers": "Attribute Category: Spatial", "Content": "CSGBOX\nreal(6)\n\nCSG-Calculated box volume in world coordinates\nGTAREAS\nelement(5000)\n\nAll areas whose bounding box fully or partially enclose element\nGTEXAREAS\nelement(5000)\n\nAll areas that fully or partially enclose element\nGTGROUPS\nelement(5000)\n\nAll groups that fully enclose element\nGTHARD\nelement(5000)\n\nAll rooms with hard obstruction that fully enclose element\nGTROOM\nelement(5000)\n\nAll rooms that fully enclose element\nGTSOFT\nelement(5000)\n\nAll rooms with soft obstruction that fully enclose element\nINROOM\nelement(5000)\n\nAll rooms that include element in their inventory\nLVOL\nreal(6)\n\nEnclosing box volume in local coordinates\nWVOL\nreal(6)\n\nEnclosing box volume in world coordinates\n\nAttribute Name\nData Type\nQualifier\nDescription\nCSGBOX\nreal(6)\nCSG-Calculated box volume in world coordinates\nGTAREAS\nelement(5000)\nAll areas whose bounding box fully or partially enclose element\nGTEXAREAS\nelement(5000)\nAll areas that fully or partially enclose element\nGTGROUPS\nelement(5000)\nAll groups that fully enclose element\nGTHARD\nelement(5000)\nAll rooms with hard obstruction that fully enclose element\nGTROOM\nelement(5000)\nAll rooms that fully enclose element\nGTSOFT\nelement(5000)\nAll rooms with soft obstruction that fully enclose element\nINROOM\nelement(5000)\nAll rooms that include element in their inventory\nLVOL\nreal(6)\nEnclosing box volume in local coordinates\nWVOL\nreal(6)\nEnclosing box volume in world coordinates\n\n\n"}
{"Headers": "Attribute Category: Spooler", "Content": "AWDORF\nelement(1500)\n\nWeld owners attribute on AWELD elements\nAWDOWN\ninteger(3)\n\nTable linking AWELD elements to piping components\nAWDREF\nelement(20)\n\nReturn reference to AWELD element\nAWDORF\nelement\n\nReturn the name of the Support owning the additional weld.\nAWELDS\ninteger(20)\n\nWeld numbers of attached welds\nBOLTPARTNUMBERS\ninteger(20)\n\nSpooling bolt part numbers\nITMTBL\ninteger(2000)\n\nTable linking AITEMS elements to piping components\nIWDORF\nelement(1500)\n\nWeld owners attribute on IWELD elements\nIWDOWN\ninteger(8)\n\nTable linking IWELD elements to piping components\nJNTORF\nelement(1500)\n\nJoint owners attribute on IJOINT elements\nJNTOWN\ninteger(8)\n\nTable linking IJOINT elements to piping components\nJNTREF\nelement\ninteger\nReturn reference from Ppoint to ijoint element\nMTOPARTNUMBERS\ninteger(20)\n\nAdditional spooling item part numbers\nPARTNUMBER\ninteger\n\nPart number of a spooled component or leave tube\nPBENDNUMBER\ninteger\n\nSpooling pulled bend number\nRWDOWN\nelement\n\nReference of associated WELD of RWELD element\nRWDOWN\ninteger(2)\n\nTable linking RWELD elements to design WELD elements\nSFREF\nelement\n\nReturn reference from piping component or leave tube to spool or field element\nSPLMEM\nelement(1500)\n\nSpooling table attribute on SPOOL or FIELD elements\nSPLPARENT\nelement(500)\nelemtype\nBranches referenced by a SPLDRG, SPOOL or FIELD\nSPLTBL\ninteger(2000)\n\nTable linking SPOOL & FIELD elements to piping components\nSPLVOLUME\nreal(3)\n\nVolume of a SPOOL element\nSPOONUMBER\nstring(120)\n\nSpool number including spool prefix\nWBORE\nreal\n\nBore on IWELD/RWELD\nWJPOS\npos\n\nImplied weld position\nWLDREF\nelement\ninteger\nReturn reference from Ppoint or WELD to IWELD or RWELD element\nWSHOP\nlogical\n\nWeld shop/site flag on IWELD/RWELD\nWSPEC\nelement\n\nWeld specification on IWELD/RWELD\n\nAttribute Name\nData Type\nQualifier\nDescription\nAWDORF\nelement(1500)\nWeld owners attribute on AWELD elements\nAWDOWN\ninteger(3)\nTable linking AWELD elements to piping components\nAWDREF\nelement(20)\nReturn reference to AWELD element\nAWDORF\nelement\nReturn the name of the Support owning the additional weld.\nAWELDS\ninteger(20)\nWeld numbers of attached welds\nBOLTPARTNUMBERS\ninteger(20)\nSpooling bolt part numbers\nITMTBL\ninteger(2000)\nTable linking AITEMS elements to piping components\nIWDORF\nelement(1500)\nWeld owners attribute on IWELD elements\nIWDOWN\ninteger(8)\nTable linking IWELD elements to piping components\nJNTORF\nelement(1500)\nJoint owners attribute on IJOINT elements\nJNTOWN\ninteger(8)\nTable linking IJOINT elements to piping components\nJNTREF\nelement\ninteger\nReturn reference from Ppoint to ijoint element\nMTOPARTNUMBERS\ninteger(20)\nAdditional spooling item part numbers\nPARTNUMBER\ninteger\nPart number of a spooled component or leave tube\nPBENDNUMBER\ninteger\nSpooling pulled bend number\nRWDOWN\nelement\nReference of associated WELD of RWELD element\nRWDOWN\ninteger(2)\nTable linking RWELD elements to design WELD elements\nSFREF\nelement\nReturn reference from piping component or leave tube to spool or field element\nSPLMEM\nelement(1500)\nSpooling table attribute on SPOOL or FIELD elements\nSPLPARENT\nelement(500)\nelemtype\nBranches referenced by a SPLDRG, SPOOL or FIELD\nSPLTBL\ninteger(2000)\nTable linking SPOOL & FIELD elements to piping components\nSPLVOLUME\nreal(3)\nVolume of a SPOOL element\nSPOONUMBER\nstring(120)\nSpool number including spool prefix\nWBORE\nreal\nBore on IWELD/RWELD\nWJPOS\npos\nImplied weld position\nWLDREF\nelement\ninteger\nReturn reference from Ppoint or WELD to IWELD or RWELD element\nWSHOP\nlogical\nWeld shop/site flag on IWELD/RWELD\nWSPEC\nelement\nWeld specification on IWELD/RWELD\n\n\n"}
{"Headers": "Attribute Category: Stairs", "Content": "GOING\nreal(10)\n\nTread Going\nLAYOUT\nlogical\n\nTRUE if element is layout mode\nNOTREAD\ninteger\n\nNumber of treads\nTREADD\nreal\n\nTread Depth\nTWIDTH\nreal\n\nTread Width\n\nAttribute Name\nData Type\nQualifier\nDescription\nGOING\nreal(10)\nTread Going\nLAYOUT\nlogical\nTRUE if element is layout mode\nNOTREAD\ninteger\nNumber of treads\nTREADD\nreal\nTread Depth\nTWIDTH\nreal\nTread Width\n\n\n"}
{"Headers": "Attribute Category: Status Related", "Content": "RVCURR\nstring(50)\n\nCurrent revision\nSTVALI\nstring(10)\nelement\nAlias of user making last status modification\nSTVASD\nelement(500)\n\nStatus types eligible\nSTVCOM\nstring\nelement\nStatus comment\nSTVDAT\ndatetime(2)\nelement\nStatus Modification Date\nSTVDEMOTE\nelement\n\nDemote Status Value\nSTVDSC\nstring\nelement\nStatus description\nSTVLNK\nelement\nelement\nStatus value Reference\nSTVLST\nelement(500)\n\nStatuses assigned\nSTVMOD\nstring(120)\nelement\nDate of last status modification\nSTVNAM\nstring\nelement\nStatus value name\nSTVNUM\ninteger\nelement\nStatus value\nSTVPROMOTE\nelement\n\nPromote Status Value\nSTVREA\nstring\nelement\nStatus reason\nSTVREF\nelement\n\nValue Ref\nSTVSUS\nlogical\nelement\nCurrent status held\nSTVTRV\nelement(500)\n\nValid Transitions\nSTVUNR\nelement(500)\n\nUnresolved Status refs\nSTVUSD\nelement(10000)\n\nElements having this status value\nSTVUSE\nstring(120)\nelement\nUser making last status modification\nSTVVAL\nelement\nelement\nStatus value Reference\nSTVVLD\nlogical\nelement\nTrue if Status valid to be controlled\n\nAttribute Name\nData Type\nQualifier\nDescription\nRVCURR\nstring(50)\nCurrent revision\nSTVALI\nstring(10)\nelement\nAlias of user making last status modification\nSTVASD\nelement(500)\nStatus types eligible\nSTVCOM\nstring\nelement\nStatus comment\nSTVDAT\ndatetime(2)\nelement\nStatus Modification Date\nSTVDEMOTE\nelement\nDemote Status Value\nSTVDSC\nstring\nelement\nStatus description\nSTVLNK\nelement\nelement\nStatus value Reference\nSTVLST\nelement(500)\nStatuses assigned\nSTVMOD\nstring(120)\nelement\nDate of last status modification\nSTVNAM\nstring\nelement\nStatus value name\nSTVNUM\ninteger\nelement\nStatus value\nSTVPROMOTE\nelement\nPromote Status Value\nSTVREA\nstring\nelement\nStatus reason\nSTVREF\nelement\nValue Ref\nSTVSUS\nlogical\nelement\nCurrent status held\nSTVTRV\nelement(500)\nValid Transitions\nSTVUNR\nelement(500)\nUnresolved Status refs\nSTVUSD\nelement(10000)\nElements having this status value\nSTVUSE\nstring(120)\nelement\nUser making last status modification\nSTVVAL\nelement\nelement\nStatus value Reference\nSTVVLD\nlogical\nelement\nTrue if Status valid to be controlled\n\n\n"}
{"Headers": "Attribute Category: Structural", "Content": "AANGXZ\nreal\n\nAngle of attached SCTN in XZ plane of joint\nAANGYZ\nreal\n\nAngle of attached SCTN in YZ plane of joint\nACTL\nreal\n\nActual length\nADDMHE\nstring(32)\n\nDetailing Bolt Set Head-Side Addtl. Material\nADDMNU\nstring(32)\n\nDetailing Bolt Set Nut-Side Addtl. Material\nANPJ\npos\n\nAttached neutral point of joint (steelwork)\nANPS\npos\n\nAttached neutral point of section (steelwork)\nBOLTYP\ninteger\n\nBolt Type Number\nBPANNR\ndir\n\nCurved base panel normal\nBPANOR\nori\n\nCurved base panel orientation\nBPANRE\nelement\n\nBase panel reference\nCLALEN\nreal\n\nclamping length\nCLHO\nreal\n\nclearance hole\nCUTL\nreal\n\nCut length\nDELPE\nreal\n\nEasting of D-Position in STRUC\nDELPN\nreal\n\nNorthing of D-position in STRUC\nDELPU\nreal\n\nUpping of D-position in STRUC\nDIRX\nreal(3)\n\ngrid limit in x direction\nDIRY\nreal(3)\n\ngrid limit in x direction\nDISTFH\nreal\ninteger\nDistance from head\nDISTFN\nreal\n\nDistance from next point\nDISTFP\nreal\n\nDistance from previous point\nDRNE\ndir\n\nPlane normal at end of SCTN/GENSEC\nDRNS\ndir\n\nPlane normal at start of SCTN/GENSEC\nDTCLHO\nreal\n\nBolt Hole Clearance\nECCE\npos\n\nEccentricity (steelwork)\nECCJ\npos\n\nEccentricity of joint (steelwork)\nGENIX\nstring(125)\n\ngeneration information for x direction\nGENIY\nstring(125)\n\ngeneration information for y direction\nGENIZ\nstring(125)\n\ngeneration information for z direction\nGPENH\ninteger\n\npen for hidden lines\nGPENV\ninteger\n\npen for visible lines\nGRDNUM\ninteger\n\ngrid number\nGRDTYP\ninteger\n\ngrid type\nHIERARCHY\nelement(5000)\n\nStructural connections\nHRJUSL\nword\n\nHandrail Justification Line\nISSTENDATUM\nlogical\n\nIs start ENDATUM; order depending on owned FIXING\nJSPOSE\npos\n\nJustifications End point position\nJSPOSS\npos\n\nJustifications Start point position\nJUSL\nword\n\nJustification Pline\nLCKNUT\nstring(32)\n\nDetailing Bolt Set Lock Nut\nLENG\nreal\n\nLength\nLENSEG\nreal\n\nLength of segment\nLINKS\nelement(5000)\n\nLinked elements\nLOHE\nreal\n\nPLOOP height - from first PLOOP in owning panel\nLTAPER\nlogical\n\nTrue if Gensec can be tapered\nMIDP\npos\n\nSection midpoint (steelwork)\nNOMDIA\nreal\n\nNominal Bolt Shank Diameter\nNOMLEN\nreal\n\nNominal Bolt Shank Length\nONPJ\npos\n\nOwning neutral point of joint (steelwork)\nONPS\npos\n\nOwning neutral point of section (steelwork)\nPALIG\nreal\n\nPanel alignment\nPLTYPE\ninteger\n\nType of Grid Plane Definition\nPOSE\npos\n\nEnd point position\nPOSEE\nreal\n\nEasting of end point position\nPOSEU\nreal\n\nUpping of end point position\nPOSEY\nreal\n\nNorthing (Y coordinate) of end point position\nPOSL\nword\n\nPositioning line\nPOSS\npos\n\nStart point position\nPOSSE\nreal\n\nEasting of start point position\nPOSSN\nreal\n\nNorthing of start point position\nPOSSU\nreal\n\nUpping of start point position\nPREFSP\nlogical\n\nPreferred Specification\nPSIZE\nreal(2)\n\nPanel size\nRATTAL\nelement(500)\nword\nRatta list\nSLRAP\nelement(500)\n\nSorted list of RATTA after POINTR\nSLRBP\nelement(500)\n\nSorted list of RATTA before POINTR\nSPRLCK\nstring(32)\n\nDetailing Bolt Set Springlock Washer\nSTDNUM\ninteger\n\nStandard Number\nSTDTXT\nstring(32)\n\nStandard\nTCTL\nreal\n\nTrue cut length\nTWSHRH\nstring(32)\n\nDetailing Bolt Set Head-Side Tapered Washer\nTWSHRN\nstring(32)\n\nDetailing Bolt Set Nut-Side Tapered Washer\nUBULG\nreal\n\nUsed bulge factor for curve geometry\nUCURTYP\nword\n\nUsed curve type\nURADI\nreal\n\nUsed radius for curve geometry\nWASHRH\nstring(32)\n\nDetailing Bolt Set Head-Side Washer\nWASHRN\nstring(32)\n\nDetailing Bolt Set Nut-Side Washer\nWCCAS\ninteger\n\nWelding constant contour (arrow side)\nWCCOS\ninteger\n\nWelding constant contour (other side)\nWCHAR\ninteger\n\nDetailing Weld Characteristic\nWCLOS\nlogical\n\nClosure weld\nWGNAS\ninteger\n\nWelding symbol ID (arrow side)\nWGNOS\ninteger\n\nWelding symbol ID (other side)\nWGOLD\nlogical\n\nGolden Weld\nWGROUP\ninteger\n\nWeld Grouping Option\nWIMAS\nlogical\n\nIntermittent weld (arrow side)\nWIMOS\nlogical\n\nIntermittent weld (other side)\nWINDAS\nstring(32)\n\nWelding Index (Arrow Side)\nWINDOS\nstring(32)\n\nWelding Index (Other Side)\nWISYM\ninteger\n\nWelding Process symbol number\nWLDAAS\nreal\n\nWeld chamfer angle arrow side\nWLDAOS\nreal\n\nWeld chamfer angle (other side)\nWLDBAS\ninteger\n\nWeld Backing (arrow side)\nWLDBOS\ninteger\n\nWeld Backing (other side)\nWLDCAS\nreal\n\nWeld width (arrow side)\nWLDCOS\nreal\n\nWeld width (other side)\nWLDDAS\nreal\n\nWeld Diameter (arrow side)\nWLDDOS\nreal\n\nWeld diameter (other side)\nWLDEAS\nreal\n\nWeld thickness (arrow side)\nWLDEOS\nreal\n\nWeld thickness (other side)\nWLDFAS\ninteger\n\nWelding Finish (arrow side)\nWLDFOS\ninteger\n\nWelding Finish (other side)\nWLDHAS\ninteger\n\nWelding Spacer (arrow side)\nWLDHOS\ninteger\n\nWelding Spacer (other side)\nWLDINF\ninteger\n\nWelding information\nWLDLAS\nreal\n\nWeld segment length (arrow side)\nWLDLOS\nreal\n\nWeld segment length (other side)\nWLDNAS\ninteger\n\nNumber of weld segments (arrow side)\nWLDNOS\ninteger\n\nNumber of weld segments (other side)\nWLDRAS\nreal\n\nWeld chamfer Gap (arrow side)\nWLDRND\nlogical\n\nFlag weld all round\nWLDROS\nreal\n\nWeld chamfer Gap (other side)\nWLDSAS\nreal\n\nWeld chamfer depth (arrow side)\nWLDSOS\nreal\n\nWeld chamfer depth (other side)\nWLDTAS\ninteger\n\nWeld process number (arrow side)\nWLDTHY\nreal\n\nWeld material thickness (Y direction)\nWLDTHZ\nreal\n\nWeld material thickness (Z direction)\nWLDTOS\ninteger\n\nWeld process number (other side)\nWLDTYP\ninteger\n\nWelding Element Type Number\nWLDVAS\nreal\n\nWeld segment offset (arrow side)\nWLDVOS\nreal\n\nWeld segment Offset (other side)\nWLDZAS\nreal\n\nWeld leg length (arrow side)\nWLDZOS\nreal\n\nWeld leg length (other side)\nWLEGTX\nstring(32)\n\nWelding legend text\nWNAMAS\nstring(32)\n\nWeld Name (arrow side)\nWNAMOS\nstring(32)\n\nWeld Name (other side)\nWNDTN\nstring(32)\n\nWelding NDT type name\nWNTHK\nstring(32)\n\nWeld Name Thickness\nWPDAS\nreal\n\nWeld segment distance (arrow side)\nWPDOS\nreal\n\nWeld segment distance (other side)\nWPOST\nstring(32)\n\nWeld mark text\nWSSAS\nreal\n\nWeld penetration depth (arrow side)\nWSSOS\nreal\n\nWeld penetration depth (other side)\nWUNIQ\nlogical\n\nWelding Element Unique Flag\nWVTAS\ninteger\n\nWeld type (arrow side)\nWVTOS\ninteger\n\nWeld type (other side)\nXYSIZE\nreal(2)\n\nsize array for grids\nYDIR\ndir\n\nPreferred Y axis direction\nZDIR\ndir\n\nAdditional axis direction\nZDIS\nreal\n\nPosition in section\n\nAttribute Name\nData Type\nQualifier\nDescription\nAANGXZ\nreal\nAngle of attached SCTN in XZ plane of joint\nAANGYZ\nreal\nAngle of attached SCTN in YZ plane of joint\nACTL\nreal\nActual length\nADDMHE\nstring(32)\nDetailing Bolt Set Head-Side Addtl. Material\nADDMNU\nstring(32)\nDetailing Bolt Set Nut-Side Addtl. Material\nANPJ\npos\nAttached neutral point of joint (steelwork)\nANPS\npos\nAttached neutral point of section (steelwork)\nBOLTYP\ninteger\nBolt Type Number\nBPANNR\ndir\nCurved base panel normal\nBPANOR\nori\nCurved base panel orientation\nBPANRE\nelement\nBase panel reference\nCLALEN\nreal\nclamping length\nCLHO\nreal\nclearance hole\nCUTL\nreal\nCut length\nDELPE\nreal\nEasting of D-Position in STRUC\nDELPN\nreal\nNorthing of D-position in STRUC\nDELPU\nreal\nUpping of D-position in STRUC\nDIRX\nreal(3)\ngrid limit in x direction\nDIRY\nreal(3)\ngrid limit in x direction\nDISTFH\nreal\ninteger\nDistance from head\nDISTFN\nreal\nDistance from next point\nDISTFP\nreal\nDistance from previous point\nDRNE\ndir\nPlane normal at end of SCTN/GENSEC\nDRNS\ndir\nPlane normal at start of SCTN/GENSEC\nDTCLHO\nreal\nBolt Hole Clearance\nECCE\npos\nEccentricity (steelwork)\nECCJ\npos\nEccentricity of joint (steelwork)\nGENIX\nstring(125)\ngeneration information for x direction\nGENIY\nstring(125)\ngeneration information for y direction\nGENIZ\nstring(125)\ngeneration information for z direction\nGPENH\ninteger\npen for hidden lines\nGPENV\ninteger\npen for visible lines\nGRDNUM\ninteger\ngrid number\nGRDTYP\ninteger\ngrid type\nHIERARCHY\nelement(5000)\nStructural connections\nHRJUSL\nword\nHandrail Justification Line\nISSTENDATUM\nlogical\nIs start ENDATUM; order depending on owned FIXING\nJSPOSE\npos\nJustifications End point position\nJSPOSS\npos\nJustifications Start point position\nJUSL\nword\nJustification Pline\nLCKNUT\nstring(32)\nDetailing Bolt Set Lock Nut\nLENG\nreal\nLength\nLENSEG\nreal\nLength of segment\nLINKS\nelement(5000)\nLinked elements\nLOHE\nreal\nPLOOP height - from first PLOOP in owning panel\nLTAPER\nlogical\nTrue if Gensec can be tapered\nMIDP\npos\nSection midpoint (steelwork)\nNOMDIA\nreal\nNominal Bolt Shank Diameter\nNOMLEN\nreal\nNominal Bolt Shank Length\nONPJ\npos\nOwning neutral point of joint (steelwork)\nONPS\npos\nOwning neutral point of section (steelwork)\nPALIG\nreal\nPanel alignment\nPLTYPE\ninteger\nType of Grid Plane Definition\nPOSE\npos\nEnd point position\nPOSEE\nreal\nEasting of end point position\nPOSEU\nreal\nUpping of end point position\nPOSEY\nreal\nNorthing (Y coordinate) of end point position\nPOSL\nword\nPositioning line\nPOSS\npos\nStart point position\nPOSSE\nreal\nEasting of start point position\nPOSSN\nreal\nNorthing of start point position\nPOSSU\nreal\nUpping of start point position\nPREFSP\nlogical\nPreferred Specification\nPSIZE\nreal(2)\nPanel size\nRATTAL\nelement(500)\nword\nRatta list\nSLRAP\nelement(500)\nSorted list of RATTA after POINTR\nSLRBP\nelement(500)\nSorted list of RATTA before POINTR\nSPRLCK\nstring(32)\nDetailing Bolt Set Springlock Washer\nSTDNUM\ninteger\nStandard Number\nSTDTXT\nstring(32)\nStandard\nTCTL\nreal\nTrue cut length\nTWSHRH\nstring(32)\nDetailing Bolt Set Head-Side Tapered Washer\nTWSHRN\nstring(32)\nDetailing Bolt Set Nut-Side Tapered Washer\nUBULG\nreal\nUsed bulge factor for curve geometry\nUCURTYP\nword\nUsed curve type\nURADI\nreal\nUsed radius for curve geometry\nWASHRH\nstring(32)\nDetailing Bolt Set Head-Side Washer\nWASHRN\nstring(32)\nDetailing Bolt Set Nut-Side Washer\nWCCAS\ninteger\nWelding constant contour (arrow side)\nWCCOS\ninteger\nWelding constant contour (other side)\nWCHAR\ninteger\nDetailing Weld Characteristic\nWCLOS\nlogical\nClosure weld\nWGNAS\ninteger\nWelding symbol ID (arrow side)\nWGNOS\ninteger\nWelding symbol ID (other side)\nWGOLD\nlogical\nGolden Weld\nWGROUP\ninteger\nWeld Grouping Option\nWIMAS\nlogical\nIntermittent weld (arrow side)\nWIMOS\nlogical\nIntermittent weld (other side)\nWINDAS\nstring(32)\nWelding Index (Arrow Side)\nWINDOS\nstring(32)\nWelding Index (Other Side)\nWISYM\ninteger\nWelding Process symbol number\nWLDAAS\nreal\nWeld chamfer angle arrow side\nWLDAOS\nreal\nWeld chamfer angle (other side)\nWLDBAS\ninteger\nWeld Backing (arrow side)\nWLDBOS\ninteger\nWeld Backing (other side)\nWLDCAS\nreal\nWeld width (arrow side)\nWLDCOS\nreal\nWeld width (other side)\nWLDDAS\nreal\nWeld Diameter (arrow side)\nWLDDOS\nreal\nWeld diameter (other side)\nWLDEAS\nreal\nWeld thickness (arrow side)\nWLDEOS\nreal\nWeld thickness (other side)\nWLDFAS\ninteger\nWelding Finish (arrow side)\nWLDFOS\ninteger\nWelding Finish (other side)\nWLDHAS\ninteger\nWelding Spacer (arrow side)\nWLDHOS\ninteger\nWelding Spacer (other side)\nWLDINF\ninteger\nWelding information\nWLDLAS\nreal\nWeld segment length (arrow side)\nWLDLOS\nreal\nWeld segment length (other side)\nWLDNAS\ninteger\nNumber of weld segments (arrow side)\nWLDNOS\ninteger\nNumber of weld segments (other side)\nWLDRAS\nreal\nWeld chamfer Gap (arrow side)\nWLDRND\nlogical\nFlag weld all round\nWLDROS\nreal\nWeld chamfer Gap (other side)\nWLDSAS\nreal\nWeld chamfer depth (arrow side)\nWLDSOS\nreal\nWeld chamfer depth (other side)\nWLDTAS\ninteger\nWeld process number (arrow side)\nWLDTHY\nreal\nWeld material thickness (Y direction)\nWLDTHZ\nreal\nWeld material thickness (Z direction)\nWLDTOS\ninteger\nWeld process number (other side)\nWLDTYP\ninteger\nWelding Element Type Number\nWLDVAS\nreal\nWeld segment offset (arrow side)\nWLDVOS\nreal\nWeld segment Offset (other side)\nWLDZAS\nreal\nWeld leg length (arrow side)\nWLDZOS\nreal\nWeld leg length (other side)\nWLEGTX\nstring(32)\nWelding legend text\nWNAMAS\nstring(32)\nWeld Name (arrow side)\nWNAMOS\nstring(32)\nWeld Name (other side)\nWNDTN\nstring(32)\nWelding NDT type name\nWNTHK\nstring(32)\nWeld Name Thickness\nWPDAS\nreal\nWeld segment distance (arrow side)\nWPDOS\nreal\nWeld segment distance (other side)\nWPOST\nstring(32)\nWeld mark text\nWSSAS\nreal\nWeld penetration depth (arrow side)\nWSSOS\nreal\nWeld penetration depth (other side)\nWUNIQ\nlogical\nWelding Element Unique Flag\nWVTAS\ninteger\nWeld type (arrow side)\nWVTOS\ninteger\nWeld type (other side)\nXYSIZE\nreal(2)\nsize array for grids\nYDIR\ndir\nPreferred Y axis direction\nZDIR\ndir\nAdditional axis direction\nZDIS\nreal\nPosition in section\n\n\n"}
{"Headers": "Attribute Category: Supports", "Content": "CONSUPPORTS\nelement(500)\n\nAll connected supports to the element tree under an element\nHANEXP\npos\n\nHANCI expected position wrt the start of the COMPRE\nHANOFFSET\npos\n\nHANCI cached position offset\nHANPOSITION\npos\n\nSupport cached position\nLNKALINVALID\nelement(100)\n\nAll invalid HANCI refs\nLNKALLARRAY\nelement(100)\n\nAll HANCI refs\nLNKIRARRAY\nelement(100)\n\nInvalid HANCI reference array attribute\nLNKRFARRAY\nelement(100)\n\nHANCI reference array attribute\nLNKVFARRAY\nlogical(10)\n\nIndividual support valid flags array attribute\nSUPALINVALID\nelement(100)\n\nAll invalid ANCI REFS on a SITE, ZONE, PIPE, BRAN\nSUPALLANCIS\nelement(100)\n\nAll ANCI REFs on a SITE, ZONE, PIPE, BRAN\nSUPFRARRAY\nelement(100)\n\nSupport FIXINGs reference array\nSUPIRARRAY\nelement(100)\n\nInvalid ANCILLARY support reference attribute\nSUPLST\nelement(100)\nword\nAll supports connected to a section or a panel\nSUPRFARRAY\nelement(100)\n\nANCILLARY reference array attribute\nSUPVFARRAY\nlogical(10)\n\nIndividual ANCI valid flags array attribute\n\nAttribute Name\nData Type\nQualifier\nDescription\nCONSUPPORTS\nelement(500)\nAll connected supports to the element tree under an element\nHANEXP\npos\nHANCI expected position wrt the start of the COMPRE\nHANOFFSET\npos\nHANCI cached position offset\nHANPOSITION\npos\nSupport cached position\nLNKALINVALID\nelement(100)\nAll invalid HANCI refs\nLNKALLARRAY\nelement(100)\nAll HANCI refs\nLNKIRARRAY\nelement(100)\nInvalid HANCI reference array attribute\nLNKRFARRAY\nelement(100)\nHANCI reference array attribute\nLNKVFARRAY\nlogical(10)\nIndividual support valid flags array attribute\nSUPALINVALID\nelement(100)\nAll invalid ANCI REFS on a SITE, ZONE, PIPE, BRAN\nSUPALLANCIS\nelement(100)\nAll ANCI REFs on a SITE, ZONE, PIPE, BRAN\nSUPFRARRAY\nelement(100)\nSupport FIXINGs reference array\nSUPIRARRAY\nelement(100)\nInvalid ANCILLARY support reference attribute\nSUPLST\nelement(100)\nword\nAll supports connected to a section or a panel\nSUPRFARRAY\nelement(100)\nANCILLARY reference array attribute\nSUPVFARRAY\nlogical(10)\nIndividual ANCI valid flags array attribute\n\n\n"}
{"Headers": "Attribute Category: Surface", "Content": "SURNOR\ndir\npos, dir\nSurface Normal\nSURPNT\npos\npos, dir\nSurface Point\n\nAttribute Name\nData Type\nQualifier\nDescription\nSURNOR\ndir\npos, dir\nSurface Normal\nSURPNT\npos\npos, dir\nSurface Point\n\n\n"}
{"Headers": "Attribute Category: Surface Treatment", "Content": "MYINSF\nelement\n\nSurface Treatment Reference\nMYOUSF\nelement\n\nSurface Treatment Reference\nMYSRFT\nelement\nword\nSurface Treatment Reference\nPUINCD\nstring(120)\n\nInside punch code\nPUOUCD\nstring(120)\n\nOutside punch code\nSTINCD\nstring(120)\n\nInside surface treatment symbol code\nSTINRF\nelement\n\nInside surface treatment reference\nSTOUCD\nstring(120)\n\nOutside Surface treatment symbol code\nSTOURF\nelement\n\nOutside surface treatment reference\n\nAttribute Name\nData Type\nQualifier\nDescription\nMYINSF\nelement\nSurface Treatment Reference\nMYOUSF\nelement\nSurface Treatment Reference\nMYSRFT\nelement\nword\nSurface Treatment Reference\nPUINCD\nstring(120)\nInside punch code\nPUOUCD\nstring(120)\nOutside punch code\nSTINCD\nstring(120)\nInside surface treatment symbol code\nSTINRF\nelement\nInside surface treatment reference\nSTOUCD\nstring(120)\nOutside Surface treatment symbol code\nSTOURF\nelement\nOutside surface treatment reference\n\n\n"}
{"Headers": "Attribute Category: System Related", "Content": "DATE\nstring(12)\n\nDate\nEXTNO\ninteger\n\nExtract number\nINSYST\nelement(500)\n\nReference Array of all SYSGRPs Elements\nPRIMSY\nelement\n\nReference of the primary system elements\n\nAttribute Name\nData Type\nQualifier\nDescription\nDATE\nstring(12)\nDate\nEXTNO\ninteger\nExtract number\nINSYST\nelement(500)\nReference Array of all SYSGRPs Elements\nPRIMSY\nelement\nReference of the primary system elements\n\n\n"}
{"Headers": "Attribute Category: Task Related", "Content": "TAASTA\nelement\nword, integer\nAssigned Task Reference\nTAATCT\ninteger\nword\nAssigned Tasks Count\nTAATDS\nstring\nword, integer\nAssigned Task Description\nTAATKS\nelement(500)\nword\nAssigned Tasks\nTAATNA\nstring(200)\nword\nAssigned Task Name\nTAATNB\ninteger\nword, integer\nAssigned Task Number\nTAATNS\nstring\nword\nAssigned Task Names\nTAATSN\nstring\nword, integer\nAssigned Task Status Name\nTAISAS\nlogical\nword\nTrue if element is assigned to a task\nTANSCT\ninteger\n\nTask Name Space Count\nTANSNA\nstring(200)\ninteger\nTask Name Space Name\nTANSNS\nstring\nword\nTask Name Space Names\nTASTDS\nstring\nword\nTask Status Description\nTASTNA\nstring\nword\nTask Status Name\nTASTNB\ninteger\nword\nTask Status Number\nTASTVA\nelement\nword\nTask Status Value Reference\n\nAttribute Name\nData Type\nQualifier\nDescription\nTAASTA\nelement\nword, integer\nAssigned Task Reference\nTAATCT\ninteger\nword\nAssigned Tasks Count\nTAATDS\nstring\nword, integer\nAssigned Task Description\nTAATKS\nelement(500)\nword\nAssigned Tasks\nTAATNA\nstring(200)\nword\nAssigned Task Name\nTAATNB\ninteger\nword, integer\nAssigned Task Number\nTAATNS\nstring\nword\nAssigned Task Names\nTAATSN\nstring\nword, integer\nAssigned Task Status Name\nTAISAS\nlogical\nword\nTrue if element is assigned to a task\nTANSCT\ninteger\nTask Name Space Count\nTANSNA\nstring(200)\ninteger\nTask Name Space Name\nTANSNS\nstring\nword\nTask Name Space Names\nTASTDS\nstring\nword\nTask Status Description\nTASTNA\nstring\nword\nTask Status Name\nTASTNB\ninteger\nword\nTask Status Number\nTASTVA\nelement\nword\nTask Status Value Reference\n\n\n"}
{"Headers": "Attribute Category: Terrain", "Content": "SEALEV\nreal\n\nSea level height\n\nAttribute Name\nData Type\nQualifier\nDescription\nSEALEV\nreal\nSea level height\n\n\n"}
{"Headers": "Attribute Category: User Defined Type Group Related", "Content": "INUDTG\nlogical\nelemtype\nIs in Udtg\nUDTGS\nword(500)\n\nUser Defined Group Types\n\nAttribute Name\nData Type\nQualifier\nDescription\nINUDTG\nlogical\nelemtype\nIs in Udtg\nUDTGS\nword(500)\nUser Defined Group Types\n\n\n"}
{"Headers": "Attribute Category: Voltage Range", "Content": "VLTRNG\nstring(120)\n\nVoltage Range\n\nAttribute Name\nData Type\nQualifier\nDescription\nVLTRNG\nstring(120)\nVoltage Range\n\n\n"}
{"Headers": "Introduction to Attributes", "Content": "All attributes can be queried and set by you. However, many are automatically set as a result of commands. Only the attributes that you would normally set explicitly are described in full. The ones that are set automatically are of interest because you can report on them.\nNote that some attributes are used exclusively by AVEVA E3D\u2122 modules. These are not described here.\nAttributes can be divided into two categories:\nThe special attributes are either self-explanatory or are explained in the context of the element under which they appear in this chapter.\nIn addition to their standard attributes, elements may have one or more user-defined attributes (UDAs). These are set and used in the same way as standard attributes, except that the UDA names are distinguished by being prefixed with a colon (:) character.\nNote:\nSome special attributes are only used for drawing control within ISODRAFT or DRAFT. How the settings of these attributes are applied is described in the ISODRAFT or DRAFT Reference Manual.\n\n\n\nGeneral attributes\nSpecial Attributes\nNote\nuser-defined attributes"}
{"Headers": "Attribute Types", "Content": "The following is a list of attribute types.\nAll names start with a slash / and consist of any number of name parts separated by further slashes. The maximum length is 50 characters (including the slash \u2018/\u2019). A name part consists of any string of characters, letters, or digits, with the exception of $ or @. If the STAR command (qv) has been used, the * character has special significance.\nThe names given to elements are purely for your convenience and have no meaning in the system.\nExamples: \u2003/HX42\u2003/HX42/NOZ1\u2003/16/23/NH4/H21/N4\u2003/AREA3\nA real attribute holds a single real number (for example 25.5, -0.057, 25683.5, etc.). Real attributes are generally used to store dimensions (for example. DIAM, XLEN, etc.).\nAn integer attribute holds a single integer or whole number (for example. 1, -2, 4000, etc.). Integer attributes are used in Piping Components to identify connection points (ARRIV, LEAVE); in Equipment Primitives to identify obstruction levels for clash detection (OBSTR); etc.\nA reference attribute holds a reference to another element. The attribute holds the internal system reference number, for example. =12/106, and not the name of the element. Reference attributes are used to forge logical links between elements. For example, the SPREF attribute is used to link a Piping Component element in the Design to a Specification Component in a Specification. Note that a reference attribute may be restricted to storing the references of particular types of element (for example. the SPREF reference of a Piping Component may only contain the reference to a Specification Component element, that is an element of type SPCOM). The restrictions on individual reference attributes are shown in brackets with each attribute.\nA logical attribute is either TRUE or FALSE. An example of its use is the BUILT attribute in a Pipe which is needed to indicate whether the Pipe has been constructed on site or not.\nWord Attribute\nA word attribute holds a string of up to four characters. Word attributes are used, for example, to indicate the direction of flow in a branch (FORW, BACK) etc.\nA text attribute holds a string of up to 120 alphanumeric characters. The length of each text attribute is specified in the database schema. Most text attributes can hold up to 120 characters (for example. \u2018HP STEAM\u2019). The text must be input between closing single quotes or, optionally, between vertical bars (useful for entering imperial units, for example. |4\u20196|).\nA real array attribute holds more than one real number. For example, the position attribute (POS) consists of three real numbers and represents the X, Y and Z coordinates which define the position of an element.\nInteger Array Attribute\nAn integer array attribute holds more than one integer. For example, the LEVEL attribute consists of two integers and is used to control the level range of drawing detail.\nA reference array attribute holds more than one reference to another element. For example, a connection reference array (CRFA) is used to hold the connection links of a four-way valve (VFWA) or a CROSS.\nA text array attribute holds more than one text string. The strings of a text array can be of different lengths, and some can be empty strings.\nIf an attribute is set to 'noclaim' it means that the attribute can be modified without having to claim the element. Thus reducing contention in specific area such as connecting branches to equipment where a number of piping engineers can connect their branches to the same equipment. Note that there would be no warning if two branches were connected to the same nozzle with the last user to do a savework \"winning\".\n\n\n\nqv"}
{"Headers": "List of All Attributes", "Content": "The attributes are listed in Alphabetical order:\n\n\n"}
{"Headers": "Attribute A", "Content": "AALLAN\nreal\n\nArrive Ppoint allowed angle\nAANGXZ\nreal\n\nAngle of attached SCTN in XZ plane of joint\nAANGYZ\nreal\n\nAngle of attached SCTN in YZ plane of joint\nABLE\ninteger\n\nMinimum abbreviation length for a UDA/UDET user defined name\nABOP\npos\n\nBottom of arrive pipe\nABOR\nreal\n\nArrive bore\nABRE\nstring(8)\n\nAbbreviation\nACBO\nstring(1000)\n\nActual bore\nACBTEX\nstring(500)\n\nAutoCAD annotation text\nACBTYP\nstring(180)\n\nAutoCAD annotation type\nACCDIR\ndir\n\nAccess Direction\nACCELE\nreal(500)\n\nElevations of Referenced Levels\nACCESSDB\nstring(10)\n\nDB access\nACCIDENT\nreal\n\nAccident level radiation\nACCLEV\nreal(100)\n\nAccess Heights for Stairwell\nACCREF\nelement\n\nReference to Access element\nACCTYP\nword\n\nAccess type\nACDATE\nstring(50)\n\nDate last modified in AutoCAD\nACDMTX\nstring(500)\n\nAutoCAD dimension text\nACDSTY\nstring(120)\n\nAutoCAD Dimension style\nACDTYP\nstring(180)\n\nAutoCAD dimension type\nACDWT\nstring(120)\n\nAutoCAD drawing template name\nACEXPO\nstring\n\nAutoCAD export flag\nACLASS\nword(100)\n\nAccess Control Attribute class\nACLAYE\nstring(120)\n\nAutoCAD layer name\nACLIST\nelement(500)\n\nArriving cables to attached point\nACLOCK\nstring\n\nAutoCAD picture lock\nACNAME\nstring(120)\n\nAutoCAD name\nACON\nword\n\nArrive connection type\nACORRO\nreal\n\nArrive corrosion allowance\nACPICT\nstring\n\nEverything3D DRAW picture\nACPLTX\nstring(500)\n\nAutoCAD projection line text\nACPO\nelement\n\nAccess port reference\nACPTYP\nstring(180)\n\nAutoCAD projection line type\nACRF\nelement\n\nACR reference attribute\nACRGRP\nelement(5000)\n\nList of ACRs within a ACRSET\nACRLI\nelement(300)\n\nAccess Control User assigned ACRs\nACRMESSAGE\nstring(120)\n\nAccess Control User defined message\nACSCAL\nreal\n\nAutoCAD picture scale factor\nACSTYF\nelement\n\nAnnotation change style reference\nACTANG\nreal\n\nActual angle of a bend\nACTIV\nlogical\n\nActive\nACTL\nreal\n\nActual length\nACTNCU\ninteger\n\nActual number of cuts of a bend\nACTRAD\nreal\n\nActual radius of a bend\nACTTYPE\nword\n\nType of element, truncating non UDETs to 4 or 6 characters\nACTXRF\nelement\n\nAnnotation Context Reference\nADDMHE\nstring(32)\n\nDetailing Bolt Set Head-Side Addtl. Material\nADDMNU\nstring(32)\n\nDetailing Bolt Set Nut-Side Addtl. Material\nADDSEGMENTS\nlogical\n\nAuto creating segments flag\nADEFRF\nelement\n\nReference to master ASSDEF\nADEG\nreal\n\nOrientation\nADEN\nreal\n\nAddition factor (unit definition)\nADESP\nreal(100)\n\nDesign parameters of attached element\nADIR\ndir\n\nArrive direction\nADMLOC\nelement\n\nCurrently administered location\nADPRFA\nelement(500)\n\nADP reference array\nADUUID\nstring(40)\n\nUUID to ensure Project uniqueness\nAELRFA\nelement(500)\n\nBoundary components for the PipePiece\nAEXCES\nreal\n\nArrive excess for leave tube\nAFPARA\nreal(100)\n\nAuxiliary function parameters\nAFTEXT\nstring(400)\n\nAuxiliary function\nAGATYINT\ninteger\n\nAuto Grid Annotation Type (ByVStyle, ViewFrame, Local)\nAGATYPE\nstring(120)\n\nAuto Grid Annotation Type (as text)\nAGDCLINT\ninteger\n\nAuto Grid Annotation Closed Dimensions (ByVStyle, Off, On)\nAGDCLOSED\nstring(120)\n\nAuto Grid Annotation Closed Dimensions (as text)\nAGDMSTYLE\nelement\n\nAuto Grid Annotation Dimension style reference\nAGDOFFSET\nstring(80)\n\nAuto Grid Annotation Dimension Offset\nAGDOFREAL\nreal\n\nAuto Grid Annotation Dimension Offset real\nAGDOOFFSET\nstring(80)\n\nAuto Grid Annotation Overall Dimension Offset\nAGDOOREAL\nreal\n\nAuto Grid Annotation Overall Dimension Offset real\nAGDOVINT\ninteger\n\nAuto Grid Annotation Overall Dimensions (ByVStyle, Off, On)\nAGDOVR\nstring(120)\n\nAuto Grid Annotation Overall Dimensions (as text)\nAGDVRT\nstring(120)\n\nAuto Grid Annotation Vertical Dimensions (as text)\nAGDVTINT\ninteger\n\nAuto Grid Annotation Vertical Dimensions Integer (ByVStyle, Off, On)\nAGLESTYLE\nelement\n\nAuto Grid Annotation Elevation Label style reference\nAGLETM\nelement\n\nAuto Grid Annotation Elevation Label Template Reference\nAGLFSTYLE\nelement\n\nAuto Grid Annotation Face Label style reference\nAGLFTM\nelement\n\nAuto Grid Annotation Face Label Template Reference\nAGLOFFSET\nstring(80)\n\nAuto Grid Annotation Label offset\nAGLOFREAL\nreal\n\nAuto Grid Annotation Label offset real\nAGMODE\nstring(120)\n\nAuto Grid Annotation Mode (as text)\nAGMODINT\ninteger\n\nAuto Grid Annotation Mode (ByVStyle, Off, Labels, Dimensions, All)\nAGRD\nreal\n\nArrive Ppoint gradient\nAGSIDE\nstring(120)\n\nAuto Grid Annotation Sides\nAGSIDINT\ninteger\n\nAuto Grid Annotation Sides Integer\nAHEIGHT\nreal\n\nAccess height\nAHLIS\nword(200)\n\nList of actual types in owning hierarchy\nAIRCHA\nreal\n\nAir Change Rate\nAIRT\nstring(120)\n\nAir tight control method\nAKEY\nword\n\nAttribute key\nAKEYL\nword(20)\n\nAttribute-keylist (for Radial dimensions)\nALCODE\ninteger(10)\n\nAlarm code array\nALENGTH\nreal\n\nArrive length\nALIGN\nstring\n\nVertical alignment\nALIST\nelement(500)\n\n\nALLANG\nstring(1000)\n\nConnection allowable rotational angle\nALLELE\nelement(10000)\nelemtype\nAll elements in the MDB of a particular type\nALLO\nreal\n\nAllowance\nALTDEF\nelement\n\nAlternative Def\nALWDEL\nlogical\n\nTo allow the admin user to determine if tags can be deleted\nALWDLG\nboolean\n\nAllow delegation\nALWREN\nlogical\n\nAllow Rename\nALWUSE\nlogical\n\nIndicates whether or not catalogue can be used in the project\nAMAPNM\nstring(120)\n\nLocal Name of Proxy actual member\nAMEMRF\nelement\n\nReference to a design model object\nAMPMPN\nstring(120)\n\nLocal Name of Proxy in Association\nAMTEMP\nreal\n\nAmpacity Temperature\nANGFR\nreal\n\nAngle between assembly and frame plane\nANGL\nreal\n\nAngle\nANGLSP\nreal(10000)\n\nANGLE Spacing\nANGSEG\nreal(2)\n\nAngle segment (start,end)\nANGSPA\nreal\n\nSpringback angle at 20 degrees\nANGSPB\nreal\n\nSpringback angle at 120 degrees\nANGWL\nreal\n\nAngle between assembly and water-line plane\nANPJ\npos\n\nAttached neutral point of joint (steelwork)\nANPS\npos\n\nAttached neutral point of section (steelwork)\nANSTYP\nword\n\nType of answer NONE, REAL, WORD, TEXT or BOOL\nANSW\nreal\n\nAnswer, when a real is expected\nANTY\nstring(120)\n\nAnalysis type\nANYCHA\nlogical\n\nTrue if chamfer is defined on any edge\nAOBJS\nelement(500)\n\nReference Array of all Model currently participating in ASSOCs\nAOD\nreal\n\nArrive Ppoint outside diameter\nAOFCEL\ninteger\n\nNumber of connected elements\nAPAR\nreal(100)\n\nAttached catalogue parameters\nAPARMS\nreal(9)\n\nAll parameters\nAPDT\nstring(12)\n\nDate of approval\nAPOF\nreal(2)\n\nLeaderline attachment point\nAPOFTX\nstring(80)\n\nLeaderline attachment point text\nAPOS\npos\n\nArrive position\nAPOSE\nreal\n\nEasting of arrive position\nAPOSN\nreal\n\nNorthing of arrive position\nAPOSU\nreal\n\nUpping of arrive position\nAPPL\nstring(20)\n\nApplication\nAPPR\nstring(1000)\n\nApprover\nAPRO\nreal\n\nSpot value of property A\nAPTDAT\nreal(5)\n\nAnnotation Point 2D Data\nAQAANG\nreal\n\nAngle between alignment direction of arrive pp and previous\nAQANG\nreal\n\nAngle between arrive Ppoint and previous component\nAQBORE\nlogical\n\nTRUE if arrive Ppoint has same bore as previous\nAQCON\nlogical\n\nTRUE if arrive Ppoint has Correct connection type\nAQOFF\nreal\n\nOffset between arrive Ppoint and previous component\nARCDAT\nblob(2147483647)\n\nArchive Binary Data\nAREA\ninteger\n\nArea\nAREAEX\nlogical\n\nTrue if area exists for DB\nAREARE\nelement\n\nArea reference\nARMMTL\nelement\n\nArmour material\nARMRED\nlogical\n\nIndicating whether CABD is armoured\nARNO\ninteger\n\nPicture directory area number\nARRHEI\nreal\n\nArrive height\nARRI\ninteger\n\nArrive Ppoint\nARRSHA\nword\n\nArrive PPoint Connection shape\nARRWID\nreal\n\nArrive width\nASBPAN\nelement\n\nAssembly base panel reference\nASBUIL\nstring(1000)\n\nAssembly build strategy\nASCODE\nstring\n\nAnno selection code\nASDEST\nstring(120)\n\nAssembly destination\nASDIM\nreal(3)\n\nAssembly dimension\nASECOG\nreal(3)\n\nAssembly estimated centre of gravity\nASEWEI\nreal\n\nAssembly estimated weight\nASFBR\nlogical\n\nSpooling marker for arrive tube\nASIOWN\nelement(500)\n\nAssembly item referring to element\nASIQUA\ninteger\n\nAssembly item quantity\nASLSBSTANDARD\nelement\n\nASL Substandard Reference\nASLSTANDARD\nelement\n\nASL Standard Reference\nASMBLB\nlogical\n\nTrue if element is possible to assemble\nASMBLD\nlogical\n\nTrue if element is assembled\nASMBLR\nelement\n\nAssembly reference\nASMBLS\nstring\n\nA for assembled elements, NA for not assembled elements\nASMBLX\nstring(120)\n\nAssembly reference as text\nASMBS\nelement(500)\n\nReference Array of all association members using element\nASMOWN\nelement(500)\n\nAssembly referring to element\nASNAME\nstring(50)\n\nLocal assembly name\nASNORM\ndir\n\nAssembly normal\nASORI\ninteger\n\nPredefined assembly orientation\nASORIS\nstring(20)\n\nPredefined assembly orientation string\nASPART\nlogical\n\nTrue if assembly part.\nASPLNO\ninteger\n\nNumber of assembly plate parts\nASPRNO\ninteger\n\nNumber of profiles on assembly part\nASPWLE\nreal\n\nTotal length of weld in assembly part\nASREF\nelement\n\nAssembly reference\nASRF\nelement\n\nADP annotation symbol library ref\nASSCIA\nelement(500)\n\nReference Array of all associate elements used with constraints\nASSDFS\nelement(500)\n\nReference Array of all ASSDEFs\nASSEQ\ninteger\n\nAssembly sequence\nASSNST\nelement\n\nAssembly Nest\nASSOS\nelement(500)\n\nReference Array of all associations with constraints\nASSTAR\nelement\n\nAssociation Target Reference\nASSTMPREFERENCE\nelement\n\nAssembly Template Reference\nASTAB\nword(15)\n\nADP association table\nASTEXT\nstring(500)\nattr\nAttribute value as text\nASTMBS\nelement(500)\n\nReference Array of all association members targeting element\nASUB\nreal\n\nAngle subtended\nASVDIR\ndir\n\nAssembly view direction\nASWLOC\nstring(120)\n\nAssembly working location\nATCLL\nreal\n\nCentre-line length of arrive implied tube\nATCONN\nelement(500)\n\nList of elements connected to attachment\nATCORR\nreal\n\nArrive tube corrosion allowance\nATEX\nstring(1000)\n\nLabel Text\nATLE\nreal\n\nLength of arrive implied tube\nATLS\nword(50)\n\nAccess type list\nATNA\nword\n\nAttribute name\nATOL\ninteger\n\nArc tolerance\nATOP\npos\n\nTop of arrive pipe\nATQUALIFIER\nstring(1000)\n\nAttribute qualifier\nATSTLEN\nreal\n\nArrive Tube Stock Length\nATTC\nword\n\nAttached connection type\nATTDST\nword(2000)\n\nList the distributed attributes, default gives all udas\nATTLIST\nword(2000)\n\nList of all attributes for element\nATTMOD\nlogical\nattr\nTrue if specified attribute has been modified this session\nATTMODC\nlogical\nattr\nTrue if specified attribute has been modified since comparison date\nATTMODLIST\nword(500)\ninteger\nList of attributes modified since given session\nATTMODLISTC\nword(500)\n\nList of attributes modified since comparison date\nATTNAM\nstring(32)\n\nAttribute Name expression for ATTRRL elements\nATTOUT\nword(2000)\n\nList of all attributes excluding hidden ones, i.e as output in \"Q ATT\"\nATTRAW\nword(2000)\n\nList of raw attributes\nATTRUL\nstring(1000)\n\nAttribute Rule expression for ATTRRL elements\nATTSET\nword\n\nSet attribute with result\nATTSIZE\ninteger\nattr\nActual size of attribute\nATTY\nword\n\nAttachment type\nATWALL\nreal\n\nArrive tube wall thickness\nATWLEN\nreal\n\nAssembly total weld length\nATWREF\nelement\n\nArrive tube wall thickness reference\nAUTCOL\nreal(3)\n\nDesign rgb autocolour\nAUTCRE\nlogical\n\nSet true to automatically create the element.\nAUTH\nstring(1000)\n\nAuthor\nAUXPOS\nreal(2)\n\nAuxiliary function definition point\nAVBITY\nstring(25)\n\nAvailablity of material instance\nAVRAD\nreal\n\nAverage radius for a CTOR or RTOR\nAWALLT\nreal\n\nArrive wall thickness\nAWDARR\nlogical\n\nAuto weld arrive flange\nAWDFLN\nlogical\n\nBending machine accepts autowelded flanges\nAWDLEV\nlogical\n\nAuto weld leave flange\nAWDORF\nelement(1500)\n\nWeld owners attribute on AWELD elements\nAWDOWN\ninteger(3)\n\nTable linking AWELD elements to piping components\nAWDREF\nelement(20)\n\nReturn reference to AWELD element\nAWELDS\ninteger(20)\n\nWeld numbers of attached welds\nAWQEX\nlogical\n\nAllow Quality Exchange\nAWTHEX\nlogical\n\nAllow Thickness Exchange\nAXIDIR\ndir\n\nAxis direction applied to repeat\nAXIPOS\npos\n\nAxis position applied to repeat\nAXISID\nstring(20)\n\nAxis ID\nAXISLA\nstring(20)\n\nAxis Label\nAXSPRI\nlogical\n\nIs principle Axes Symbol\nAXSSIZ\nreal\n\nAXESYM nominal size\nAXSTYP\nword\n\nAxes Symbol type\nAYDIR\ndir\n\nArrive Y axis direction\nAZDIR\ndir\n\nArrive alignment direction\nAZID\nreal\n\nDefault Azimuth value\nAZIF\nreal\n\nAzimuth attractor factor\nAZIL\nreal(2)\n\nAzimuth limits (Min/Max)\nAZIS\nlogical\n\nAzimuth set flag - ignore Azimuth values if FALSE\n\nAttribute Name\nData Type\nQualifier\nDescription\nAALLAN\nreal\nArrive Ppoint allowed angle\nAANGXZ\nreal\nAngle of attached SCTN in XZ plane of joint\nAANGYZ\nreal\nAngle of attached SCTN in YZ plane of joint\nABLE\ninteger\nMinimum abbreviation length for a UDA/UDET user defined name\nABOP\npos\nBottom of arrive pipe\nABOR\nreal\nArrive bore\nABRE\nstring(8)\nAbbreviation\nACBO\nstring(1000)\nActual bore\nACBTEX\nstring(500)\nAutoCAD annotation text\nACBTYP\nstring(180)\nAutoCAD annotation type\nACCDIR\ndir\nAccess Direction\nACCELE\nreal(500)\nElevations of Referenced Levels\nACCESSDB\nstring(10)\nDB access\nACCIDENT\nreal\nAccident level radiation\nACCLEV\nreal(100)\nAccess Heights for Stairwell\nACCREF\nelement\nReference to Access element\nACCTYP\nword\nAccess type\nACDATE\nstring(50)\nDate last modified in AutoCAD\nACDMTX\nstring(500)\nAutoCAD dimension text\nACDSTY\nstring(120)\nAutoCAD Dimension style\nACDTYP\nstring(180)\nAutoCAD dimension type\nACDWT\nstring(120)\nAutoCAD drawing template name\nACEXPO\nstring\nAutoCAD export flag\nACLASS\nword(100)\nAccess Control Attribute class\nACLAYE\nstring(120)\nAutoCAD layer name\nACLIST\nelement(500)\nArriving cables to attached point\nACLOCK\nstring\nAutoCAD picture lock\nACNAME\nstring(120)\nAutoCAD name\nACON\nword\nArrive connection type\nACORRO\nreal\nArrive corrosion allowance\nACPICT\nstring\nEverything3D DRAW picture\nACPLTX\nstring(500)\nAutoCAD projection line text\nACPO\nelement\nAccess port reference\nACPTYP\nstring(180)\nAutoCAD projection line type\nACRF\nelement\nACR reference attribute\nACRGRP\nelement(5000)\nList of ACRs within a ACRSET\nACRLI\nelement(300)\nAccess Control User assigned ACRs\nACRMESSAGE\nstring(120)\nAccess Control User defined message\nACSCAL\nreal\nAutoCAD picture scale factor\nACSTYF\nelement\nAnnotation change style reference\nACTANG\nreal\nActual angle of a bend\nACTIV\nlogical\nActive\nACTL\nreal\nActual length\nACTNCU\ninteger\nActual number of cuts of a bend\nACTRAD\nreal\nActual radius of a bend\nACTTYPE\nword\nType of element, truncating non UDETs to 4 or 6 characters\nACTXRF\nelement\nAnnotation Context Reference\nADDMHE\nstring(32)\nDetailing Bolt Set Head-Side Addtl. Material\nADDMNU\nstring(32)\nDetailing Bolt Set Nut-Side Addtl. Material\nADDSEGMENTS\nlogical\nAuto creating segments flag\nADEFRF\nelement\nReference to master ASSDEF\nADEG\nreal\nOrientation\nADEN\nreal\nAddition factor (unit definition)\nADESP\nreal(100)\nDesign parameters of attached element\nADIR\ndir\nArrive direction\nADMLOC\nelement\nCurrently administered location\nADPRFA\nelement(500)\nADP reference array\nADUUID\nstring(40)\nUUID to ensure Project uniqueness\nAELRFA\nelement(500)\nBoundary components for the PipePiece\nAEXCES\nreal\nArrive excess for leave tube\nAFPARA\nreal(100)\nAuxiliary function parameters\nAFTEXT\nstring(400)\nAuxiliary function\nAGATYINT\ninteger\nAuto Grid Annotation Type (ByVStyle, ViewFrame, Local)\nAGATYPE\nstring(120)\nAuto Grid Annotation Type (as text)\nAGDCLINT\ninteger\nAuto Grid Annotation Closed Dimensions (ByVStyle, Off, On)\nAGDCLOSED\nstring(120)\nAuto Grid Annotation Closed Dimensions (as text)\nAGDMSTYLE\nelement\nAuto Grid Annotation Dimension style reference\nAGDOFFSET\nstring(80)\nAuto Grid Annotation Dimension Offset\nAGDOFREAL\nreal\nAuto Grid Annotation Dimension Offset real\nAGDOOFFSET\nstring(80)\nAuto Grid Annotation Overall Dimension Offset\nAGDOOREAL\nreal\nAuto Grid Annotation Overall Dimension Offset real\nAGDOVINT\ninteger\nAuto Grid Annotation Overall Dimensions (ByVStyle, Off, On)\nAGDOVR\nstring(120)\nAuto Grid Annotation Overall Dimensions (as text)\nAGDVRT\nstring(120)\nAuto Grid Annotation Vertical Dimensions (as text)\nAGDVTINT\ninteger\nAuto Grid Annotation Vertical Dimensions Integer (ByVStyle, Off, On)\nAGLESTYLE\nelement\nAuto Grid Annotation Elevation Label style reference\nAGLETM\nelement\nAuto Grid Annotation Elevation Label Template Reference\nAGLFSTYLE\nelement\nAuto Grid Annotation Face Label style reference\nAGLFTM\nelement\nAuto Grid Annotation Face Label Template Reference\nAGLOFFSET\nstring(80)\nAuto Grid Annotation Label offset\nAGLOFREAL\nreal\nAuto Grid Annotation Label offset real\nAGMODE\nstring(120)\nAuto Grid Annotation Mode (as text)\nAGMODINT\ninteger\nAuto Grid Annotation Mode (ByVStyle, Off, Labels, Dimensions, All)\nAGRD\nreal\nArrive Ppoint gradient\nAGSIDE\nstring(120)\nAuto Grid Annotation Sides\nAGSIDINT\ninteger\nAuto Grid Annotation Sides Integer\nAHEIGHT\nreal\nAccess height\nAHLIS\nword(200)\nList of actual types in owning hierarchy\nAIRCHA\nreal\nAir Change Rate\nAIRT\nstring(120)\nAir tight control method\nAKEY\nword\nAttribute key\nAKEYL\nword(20)\nAttribute-keylist (for Radial dimensions)\nALCODE\ninteger(10)\nAlarm code array\nALENGTH\nreal\nArrive length\nALIGN\nstring\nVertical alignment\nALIST\nelement(500)\nALLANG\nstring(1000)\nConnection allowable rotational angle\nALLELE\nelement(10000)\nelemtype\nAll elements in the MDB of a particular type\nALLO\nreal\nAllowance\nALTDEF\nelement\nAlternative Def\nALWDEL\nlogical\nTo allow the admin user to determine if tags can be deleted\nALWDLG\nboolean\nAllow delegation\nALWREN\nlogical\nAllow Rename\nALWUSE\nlogical\nIndicates whether or not catalogue can be used in the project\nAMAPNM\nstring(120)\nLocal Name of Proxy actual member\nAMEMRF\nelement\nReference to a design model object\nAMPMPN\nstring(120)\nLocal Name of Proxy in Association\nAMTEMP\nreal\nAmpacity Temperature\nANGFR\nreal\nAngle between assembly and frame plane\nANGL\nreal\nAngle\nANGLSP\nreal(10000)\nANGLE Spacing\nANGSEG\nreal(2)\nAngle segment (start,end)\nANGSPA\nreal\nSpringback angle at 20 degrees\nANGSPB\nreal\nSpringback angle at 120 degrees\nANGWL\nreal\nAngle between assembly and water-line plane\nANPJ\npos\nAttached neutral point of joint (steelwork)\nANPS\npos\nAttached neutral point of section (steelwork)\nANSTYP\nword\nType of answer NONE, REAL, WORD, TEXT or BOOL\nANSW\nreal\nAnswer, when a real is expected\nANTY\nstring(120)\nAnalysis type\nANYCHA\nlogical\nTrue if chamfer is defined on any edge\nAOBJS\nelement(500)\nReference Array of all Model currently participating in ASSOCs\nAOD\nreal\nArrive Ppoint outside diameter\nAOFCEL\ninteger\nNumber of connected elements\nAPAR\nreal(100)\nAttached catalogue parameters\nAPARMS\nreal(9)\nAll parameters\nAPDT\nstring(12)\nDate of approval\nAPOF\nreal(2)\nLeaderline attachment point\nAPOFTX\nstring(80)\nLeaderline attachment point text\nAPOS\npos\nArrive position\nAPOSE\nreal\nEasting of arrive position\nAPOSN\nreal\nNorthing of arrive position\nAPOSU\nreal\nUpping of arrive position\nAPPL\nstring(20)\nApplication\nAPPR\nstring(1000)\nApprover\nAPRO\nreal\nSpot value of property A\nAPTDAT\nreal(5)\nAnnotation Point 2D Data\nAQAANG\nreal\nAngle between alignment direction of arrive pp and previous\nAQANG\nreal\nAngle between arrive Ppoint and previous component\nAQBORE\nlogical\nTRUE if arrive Ppoint has same bore as previous\nAQCON\nlogical\nTRUE if arrive Ppoint has Correct connection type\nAQOFF\nreal\nOffset between arrive Ppoint and previous component\nARCDAT\nblob(2147483647)\nArchive Binary Data\nAREA\ninteger\nArea\nAREAEX\nlogical\nTrue if area exists for DB\nAREARE\nelement\nArea reference\nARMMTL\nelement\nArmour material\nARMRED\nlogical\nIndicating whether CABD is armoured\nARNO\ninteger\nPicture directory area number\nARRHEI\nreal\nArrive height\nARRI\ninteger\nArrive Ppoint\nARRSHA\nword\nArrive PPoint Connection shape\nARRWID\nreal\nArrive width\nASBPAN\nelement\nAssembly base panel reference\nASBUIL\nstring(1000)\nAssembly build strategy\nASCODE\nstring\nAnno selection code\nASDEST\nstring(120)\nAssembly destination\nASDIM\nreal(3)\nAssembly dimension\nASECOG\nreal(3)\nAssembly estimated centre of gravity\nASEWEI\nreal\nAssembly estimated weight\nASFBR\nlogical\nSpooling marker for arrive tube\nASIOWN\nelement(500)\nAssembly item referring to element\nASIQUA\ninteger\nAssembly item quantity\nASLSBSTANDARD\nelement\nASL Substandard Reference\nASLSTANDARD\nelement\nASL Standard Reference\nASMBLB\nlogical\nTrue if element is possible to assemble\nASMBLD\nlogical\nTrue if element is assembled\nASMBLR\nelement\nAssembly reference\nASMBLS\nstring\nA for assembled elements, NA for not assembled elements\nASMBLX\nstring(120)\nAssembly reference as text\nASMBS\nelement(500)\nReference Array of all association members using element\nASMOWN\nelement(500)\nAssembly referring to element\nASNAME\nstring(50)\nLocal assembly name\nASNORM\ndir\nAssembly normal\nASORI\ninteger\nPredefined assembly orientation\nASORIS\nstring(20)\nPredefined assembly orientation string\nASPART\nlogical\nTrue if assembly part.\nASPLNO\ninteger\nNumber of assembly plate parts\nASPRNO\ninteger\nNumber of profiles on assembly part\nASPWLE\nreal\nTotal length of weld in assembly part\nASREF\nelement\nAssembly reference\nASRF\nelement\nADP annotation symbol library ref\nASSCIA\nelement(500)\nReference Array of all associate elements used with constraints\nASSDFS\nelement(500)\nReference Array of all ASSDEFs\nASSEQ\ninteger\nAssembly sequence\nASSNST\nelement\nAssembly Nest\nASSOS\nelement(500)\nReference Array of all associations with constraints\nASSTAR\nelement\nAssociation Target Reference\nASSTMPREFERENCE\nelement\nAssembly Template Reference\nASTAB\nword(15)\nADP association table\nASTEXT\nstring(500)\nattr\nAttribute value as text\nASTMBS\nelement(500)\nReference Array of all association members targeting element\nASUB\nreal\nAngle subtended\nASVDIR\ndir\nAssembly view direction\nASWLOC\nstring(120)\nAssembly working location\nATCLL\nreal\nCentre-line length of arrive implied tube\nATCONN\nelement(500)\nList of elements connected to attachment\nATCORR\nreal\nArrive tube corrosion allowance\nATEX\nstring(1000)\nLabel Text\nATLE\nreal\nLength of arrive implied tube\nATLS\nword(50)\nAccess type list\nATNA\nword\nAttribute name\nATOL\ninteger\nArc tolerance\nATOP\npos\nTop of arrive pipe\nATQUALIFIER\nstring(1000)\nAttribute qualifier\nATSTLEN\nreal\nArrive Tube Stock Length\nATTC\nword\nAttached connection type\nATTDST\nword(2000)\nList the distributed attributes, default gives all udas\nATTLIST\nword(2000)\nList of all attributes for element\nATTMOD\nlogical\nattr\nTrue if specified attribute has been modified this session\nATTMODC\nlogical\nattr\nTrue if specified attribute has been modified since comparison date\nATTMODLIST\nword(500)\ninteger\nList of attributes modified since given session\nATTMODLISTC\nword(500)\nList of attributes modified since comparison date\nATTNAM\nstring(32)\nAttribute Name expression for ATTRRL elements\nATTOUT\nword(2000)\nList of all attributes excluding hidden ones, i.e as output in \"Q ATT\"\nATTRAW\nword(2000)\nList of raw attributes\nATTRUL\nstring(1000)\nAttribute Rule expression for ATTRRL elements\nATTSET\nword\nSet attribute with result\nATTSIZE\ninteger\nattr\nActual size of attribute\nATTY\nword\nAttachment type\nATWALL\nreal\nArrive tube wall thickness\nATWLEN\nreal\nAssembly total weld length\nATWREF\nelement\nArrive tube wall thickness reference\nAUTCOL\nreal(3)\nDesign rgb autocolour\nAUTCRE\nlogical\nSet true to automatically create the element.\nAUTH\nstring(1000)\nAuthor\nAUXPOS\nreal(2)\nAuxiliary function definition point\nAVBITY\nstring(25)\nAvailablity of material instance\nAVRAD\nreal\nAverage radius for a CTOR or RTOR\nAWALLT\nreal\nArrive wall thickness\nAWDARR\nlogical\nAuto weld arrive flange\nAWDFLN\nlogical\nBending machine accepts autowelded flanges\nAWDLEV\nlogical\nAuto weld leave flange\nAWDORF\nelement(1500)\nWeld owners attribute on AWELD elements\nAWDOWN\ninteger(3)\nTable linking AWELD elements to piping components\nAWDREF\nelement(20)\nReturn reference to AWELD element\nAWELDS\ninteger(20)\nWeld numbers of attached welds\nAWQEX\nlogical\nAllow Quality Exchange\nAWTHEX\nlogical\nAllow Thickness Exchange\nAXIDIR\ndir\nAxis direction applied to repeat\nAXIPOS\npos\nAxis position applied to repeat\nAXISID\nstring(20)\nAxis ID\nAXISLA\nstring(20)\nAxis Label\nAXSPRI\nlogical\nIs principle Axes Symbol\nAXSSIZ\nreal\nAXESYM nominal size\nAXSTYP\nword\nAxes Symbol type\nAYDIR\ndir\nArrive Y axis direction\nAZDIR\ndir\nArrive alignment direction\nAZID\nreal\nDefault Azimuth value\nAZIF\nreal\nAzimuth attractor factor\nAZIL\nreal(2)\nAzimuth limits (Min/Max)\nAZIS\nlogical\nAzimuth set flag - ignore Azimuth values if FALSE\n\n\n"}
{"Headers": "Attribute B", "Content": "BACKRE\nelement(1000)\nattr\nList reftable back references\nBAEXSS\nreal\n\nBending Excess Arrive\nBAIN\nstring\n\nBefore/After indicator\nBANG\nreal\n\nBeta angle\nBASELF\nelement\n\nReference of Baseline Element\nBASETYPE\nword\n\nBase type for the user-defined element type\nBASNAME\nstring(50)\n\nBase Name for the Project Definition\nBBFF\nelement(500)\n\nArray of bounding Boundary Formers\nBCPY\nelement\n\nBackward copy reference\nBDIA\nstring(1000)\n\nBolt diameter\nBDTUL\nlogical\n\nBoolean dimension text underlining flag\nBEAD\nreal\n\nDefault Bearing value\nBEAF\nreal\n\nBearing attractor factor\nBEAL\nreal(2)\n\nBearing limits (Min/Max)\nBEALAM\nstring(12)\n\nName of the bead laminate code\nBEAPOS\ninteger\n\nBead posno\nBEAQUA\nstring(26)\n\nBead quality\nBEAS\nlogical\n\nBearing set flag - ignore Bearing values if FALSE\nBEAWTH\nreal\n\nBead width\nBELRFA\nelement(500)\n\nAll components in the PipePiece\nBELTYP\ninteger(500)\n\nAll component types in the PipeSpool\nBENANG\nreal\n\nBending angle\nBENDCORNERS\nlogical\n\nBend corners - true if fillet should be applied to the corners of kickplate\nBENDIR\nword\n\nBending machine direction\nBENDMACREFERENCE\nelement\n\nBending Machine reference\nBENDMC\nelement\n\nBending Machine Reference\nBENMLF\nreal\n\nMinimum length for the first straight tube\nBENMLL\nreal\n\nMinimum length for the last straight tube\nBENPIF\nreal\n\nMaximum tube insertion length (with pre-welded flange)\nBENPIL\nreal\n\nMaximum tube insertion length (with pre-welded collar)\nBENPIP\nreal\n\nMaximum tube insertion length (Plane end)\nBENPIR\nreal\n\nBend radius (not ratio)\nBENROT\nword\n\nBending machine rotation\nBENT\nlogical\n\nBent flag\nBEVCOD\nreal(10)\n\nBevel codes for edges\nBEVDFR\nelement\n\nReference to Bevel Definition\nBEVEL\nreal\n\nBevel\nBEVFLA\nreal\n\nBevel code, flange\nBEVLEN\nreal(2)\n\nLengths of bevel\nBEVLFT\nreal\n\nBevel code on left side of seam\nBEVLI\nreal(3)\n\nLengths of I-bevel\nBEVLV\nreal\n\nLength of vertical bevel\nBEVLX\nreal(3)\n\nLengths of X-bevel\nBEVLY\nreal(3)\n\nLengths of Y-bevel\nBEVM\nreal(2)\n\nBevel codes along M1 and M2 curves\nBEVPAR\nreal(50)\n\nBevelling Parameters\nBEVPAT\nreal(10)\n\nBevelling Tool Parameters\nBEVRGT\nreal\n\nBevel code on right side of seam\nBEVROF\nlogical\n\nBevel Root Face\nBEVTAP\nlogical\n\nBevel Tapering\nBEVTXT\nstring\n\nBevel text\nBEVTYP\ninteger\n\nBevel Type Number\nBEVWEB\nreal\n\nBevel code, web\nBFCOLO\ninteger\n\nBackface colour\nBFCONU\ninteger\n\nBackface colour number\nBFCRGB\ninteger(4)\n\nRGB backface colour\nBFCRGP\ninteger(4)\n\nRGB backface colour physical\nBFLE\nstring(1000)\n\nOut of plane flexibility factor for bends\nBFOBCO\ninteger\n\nBackface and Obscured face color\nBFOBST\ninteger\n\nBackface and Obscured face linestyle\nBFORI\nori\n\nBent Feature Orientation\nBFPN\ninteger\n\nBackface pen\nBFRF\nelement\n\nReference to real Boundary Former\nBFSTREF\nelement\n\nBackface linestyle Reference\nBFSTYL\ninteger\n\nBackface linestyle\nBGTDIA\nreal\ninteger\nBolt diameter\nBGTLEN\nreal\ninteger\nBolt length\nBGTNOF\ninteger\ninteger\nNumber of Bolts\nBGTSPC\nelement\ninteger\nGet SPCO of the the bolt\nBGTTXT\nstring(256)\ninteger\nGet TEXT of the bolt\nBGTWEI\nreal\ninteger\nBolt weight\nBITE\nword(25)\n\nBolt items\nBITL\nreal(25)\n\nBolt item lengths\nBJOINT\nstring\n\nBolt joint\nBKEY\nstring(4)\n\nDRAFT user defined base symbol/skey name\nBLCKLM\nlogical\n\nTrue if block limit seam\nBLDREF\nelement(100)\n\nRevision Block Array\nBLEN\nreal(200)\n\nBolt length\nBLEXSS\nreal\n\nBending Leave Excess\nBLNK\nlogical\n\nAuto-blanking flag\nBLRF\nelement(10)\n\nBolt reference array\nBLSLEN\nreal\n\nLength of blasting contours\nBLTM\nstring(3)\n\nBolt method\nBLTR\nelement\n\nBolt reference\nBLTW\nreal\n\nStandard Bolt weight\nBMAR\nreal\n\nAuto-blanking margin\nBMAX\ninteger\n\nMaximum bend number in current spool drawing\nBMCLOC\nlogical\n\nTrue if bending machine bends clockwise\nBMLEVE\nreal(100)\n\nBeam levels from owning element\nBNDARE\nreal\n\nBoundary line area\nBNDOFF\nreal\n\nOffset from boundary\nBNLENI\nreal\n\nLength of vertical bevel\nBNLENV\nreal\n\nLength of V-Bevel\nBNLENX\nreal\n\nLength of X-Bevel\nBNLENY\nreal\n\nLength of Y-Bevel\nBOCOLO\ninteger\n\nBackface and Obscured face colour\nBOCONU\ninteger\n\nObscured Backface colour number\nBOCRGB\ninteger(4)\n\nBackfaceObscured RGB colour\nBOCRGP\ninteger(4)\n\nBackfaceObscured RGB colour physical\nBOLTPARTNUMBERS\ninteger(20)\n\nSpooling bolt part numbers\nBOLTYP\ninteger\n\nBolt Type Number\nBORE\nreal\n\nBore\nBOREAR\nreal(10)\n\nBore array\nBOSTYL\ninteger\n\nBackface and Obscured face Style\nBOTCUT\nreal\n\nBottom Stile Cut Distance\nBOTHEI\nreal\n\nBottom height\nBOTSTR\nreal\n\nBOTT Stringer Gap\nBPANNR\ndir\n\nCurved base panel normal\nBPANOR\nori\n\nCurved base panel orientation\nBPANRE\nelement\n\nBase panel reference\nBPOF\nreal(4)\n\nLeader bend point offset\nBPOFTX\nstring(80)\n\nLeader bend point offset text\nBPRO\nreal\n\nSpot value of property B\nBPTYPE\ninteger\n\nBasic Profile Type\nBRACKE\nstring\n\nBrackets code\nBRAD\nreal\n\nBend radius\nBRALNK\nelement(20)\n\nConnectivity SCBRAN-BRANCH Link\nBRANBO\nreal(200)\n\nArray of branch bore excluding arrive and leave\nBRANDI\nstringarray(200)\n\nArray of branch bore direction excluding the arrive and leave\nBRARLN\nreal\n\nBracket arm length\nBRARLT\nreal(10)\n\nBracket arm lengths\nBRCOG\npos\n\nBranch centre of gravity\nBRCONNECT\nelement(5000)\n\nBranch member connections\nBREARE\nreal\n\nBranch external surface area\nBREF\nelement\n\nBranch Reference\nBRIARE\nreal\n\nBranch internal surface area\nBRICOG\npos\n\nBranch insulated centre of gravity\nBRIRAD\nreal\n\nBridge radius\nBRIWEI\nreal\n\nBranch insulated weight\nBRLEG\nelement(5000)\n\nBranch members on the same leg\nBRLIST\nreal(500)\n\nBend radii of a cable\nBRLO\ninteger\n\nBranch Positioning Status code (Router)\nBRNCOM\nstring(320)\n\nBurner comment\nBRNFAC\nreal\n\nBurning factor\nBRNGSP\nreal\n\nBottom Rung Spacing\nBRNLEN\nreal\n\nLength of burning contours\nBRNNAM\nstring(26)\n\nBurner name\nBRNNUM\ninteger\n\nBurner number\nBRNPRC\nstring(26)\n\nBurner process name\nBRNREF\nstring(26)\n\nBurner reference id\nBRNSEQ\nstring(26)\n\nBurning sequence number\nBRNST\ninteger\n\nNumber of starts for burning\nBRNTOO\ninteger\n\nBurner tool\nBRNTYP\nstring(26)\n\nBurner type\nBRPOSA\nreal(2)\n\nFirst bridge definition point\nBRPOSB\nreal(2)\n\nSecond bridge definition point\nBRPOSS\nreal(2)\n\nBridge definition side point\nBRREF\nelement\n\nBranch table reference\nBRREFA\nelement\n\nNested part reference\nBRREFB\nelement\n\nNested part reference\nBRTXRF\nelement(500)\n\nReturn reference from Branch Table element to SPECs\nBRTYP\ninteger\n\nBridge type\nBRWCOG\npos\n\nBranch wet centre of gravity\nBRWEIG\nreal\n\nBranch weight\nBRWICOG\npos\n\nBranch wet insulated centre of gravity\nBRWIWEI\nreal\n\nBranch insulated wet weight\nBRWWEI\nreal\n\nBranch wet weight\nBSCANG\nreal\n\nBend Segment Cut Angle\nBSCLL\nreal\n\nCentre-Line Length of a mitred Bend Segment\nBSDWG\nstring(120)\n\nAutoCAD backing sheet name\nBSEL\nstring(3)\n\nBolt Selector\nBSFN\nstring(1024)\n\nBacking sheet filename\nBSLAYE\nstring(120)\n\nAutoCAD backing sheet layer\nBSMNIL\nreal\n\nMinimum Length of Insulation of a mitred Bend Segment\nBSMNL\nreal\n\nMinimum Length of a mitred Bend Segment\nBSMXIL\nreal\n\nMaximum Length of Insulation of a mitred Bend Segment\nBSMXL\nreal\n\nMaximum Length of a mitred Bend Segment\nBSPE\nelement\n\nBolt specification\nBSRF\nelement\n\nBacking sheet reference\nBSRFA\nelement(500)\n\nADP backing sheet list\nBSTA\ninteger\n\nBranch Status code (Router)\nBTEX\nstring(1000)\n\nAnnotation text string\nBTHK\nstring(1000)\n\nParameterised bolt thickness\nBTLS\nword(50)\n\nBoundary Former type list\nBTOL\nstring(1000)\n\nBore tolerance\nBTOTAL\ninteger\n\nBolt joint total\nBTOTWE\nreal\n\nBolt total weight\nBTYP\nstring(1000)\n\nBolt type\nBUFS\ninteger\n\nPreferred buffer size\nBUIL\nlogical\n\nBuilt/Unbuilt flag\nBULG\nreal\n\nBulge factor\nBUNI\nword\n\nBore units\nBUNREF\nelement\n\nCable bundle reference\nBURF\nelement\n\nReference to real Building Element\nBURNID\nstring(80)\n\nBurner id\nBUYMRK\nstring(26)\n\nBuying mark\nBVCODN\ninteger\n\nBevelled Code number\nBVIS\nlogical\n\nBottom visibility flag\nBVSCLL\nreal\n\nCentre-Line Length of a mitred Bend Segment\nBVSEGN\ninteger\n\nBevelled segment number\nBVSMNI\nreal\n\nMinimum Length of Insulation of a Virtual mitred Bend end-Segment\nBVSMNL\nreal\n\nMinimum Length of a virtual mitred Bend end-Segment\nBVSMXI\nreal\n\nMaximum Length of Insulation of a Virtual mitred Bend end-Segment\nBVSMXL\nreal\n\nMaximum Length of a virtual mitred Bend end-Segment\nBWEI\nreal(200)\n\nBolt weight\nBWIDTH\nreal\n\nBridge width\nBWITHF\nlogical\n\nBend with flow\n\nAttribute Name\nData Type\nQualifier\nDescription\nBACKRE\nelement(1000)\nattr\nList reftable back references\nBAEXSS\nreal\nBending Excess Arrive\nBAIN\nstring\nBefore/After indicator\nBANG\nreal\nBeta angle\nBASELF\nelement\nReference of Baseline Element\nBASETYPE\nword\nBase type for the user-defined element type\nBASNAME\nstring(50)\nBase Name for the Project Definition\nBBFF\nelement(500)\nArray of bounding Boundary Formers\nBCPY\nelement\nBackward copy reference\nBDIA\nstring(1000)\nBolt diameter\nBDTUL\nlogical\nBoolean dimension text underlining flag\nBEAD\nreal\nDefault Bearing value\nBEAF\nreal\nBearing attractor factor\nBEAL\nreal(2)\nBearing limits (Min/Max)\nBEALAM\nstring(12)\nName of the bead laminate code\nBEAPOS\ninteger\nBead posno\nBEAQUA\nstring(26)\nBead quality\nBEAS\nlogical\nBearing set flag - ignore Bearing values if FALSE\nBEAWTH\nreal\nBead width\nBELRFA\nelement(500)\nAll components in the PipePiece\nBELTYP\ninteger(500)\nAll component types in the PipeSpool\nBENANG\nreal\nBending angle\nBENDCORNERS\nlogical\nBend corners - true if fillet should be applied to the corners of kickplate\nBENDIR\nword\nBending machine direction\nBENDMACREFERENCE\nelement\nBending Machine reference\nBENDMC\nelement\nBending Machine Reference\nBENMLF\nreal\nMinimum length for the first straight tube\nBENMLL\nreal\nMinimum length for the last straight tube\nBENPIF\nreal\nMaximum tube insertion length (with pre-welded flange)\nBENPIL\nreal\nMaximum tube insertion length (with pre-welded collar)\nBENPIP\nreal\nMaximum tube insertion length (Plane end)\nBENPIR\nreal\nBend radius (not ratio)\nBENROT\nword\nBending machine rotation\nBENT\nlogical\nBent flag\nBEVCOD\nreal(10)\nBevel codes for edges\nBEVDFR\nelement\nReference to Bevel Definition\nBEVEL\nreal\nBevel\nBEVFLA\nreal\nBevel code, flange\nBEVLEN\nreal(2)\nLengths of bevel\nBEVLFT\nreal\nBevel code on left side of seam\nBEVLI\nreal(3)\nLengths of I-bevel\nBEVLV\nreal\nLength of vertical bevel\nBEVLX\nreal(3)\nLengths of X-bevel\nBEVLY\nreal(3)\nLengths of Y-bevel\nBEVM\nreal(2)\nBevel codes along M1 and M2 curves\nBEVPAR\nreal(50)\nBevelling Parameters\nBEVPAT\nreal(10)\nBevelling Tool Parameters\nBEVRGT\nreal\nBevel code on right side of seam\nBEVROF\nlogical\nBevel Root Face\nBEVTAP\nlogical\nBevel Tapering\nBEVTXT\nstring\nBevel text\nBEVTYP\ninteger\nBevel Type Number\nBEVWEB\nreal\nBevel code, web\nBFCOLO\ninteger\nBackface colour\nBFCONU\ninteger\nBackface colour number\nBFCRGB\ninteger(4)\nRGB backface colour\nBFCRGP\ninteger(4)\nRGB backface colour physical\nBFLE\nstring(1000)\nOut of plane flexibility factor for bends\nBFOBCO\ninteger\nBackface and Obscured face color\nBFOBST\ninteger\nBackface and Obscured face linestyle\nBFORI\nori\nBent Feature Orientation\nBFPN\ninteger\nBackface pen\nBFRF\nelement\nReference to real Boundary Former\nBFSTREF\nelement\nBackface linestyle Reference\nBFSTYL\ninteger\nBackface linestyle\nBGTDIA\nreal\ninteger\nBolt diameter\nBGTLEN\nreal\ninteger\nBolt length\nBGTNOF\ninteger\ninteger\nNumber of Bolts\nBGTSPC\nelement\ninteger\nGet SPCO of the the bolt\nBGTTXT\nstring(256)\ninteger\nGet TEXT of the bolt\nBGTWEI\nreal\ninteger\nBolt weight\nBITE\nword(25)\nBolt items\nBITL\nreal(25)\nBolt item lengths\nBJOINT\nstring\nBolt joint\nBKEY\nstring(4)\nDRAFT user defined base symbol/skey name\nBLCKLM\nlogical\nTrue if block limit seam\nBLDREF\nelement(100)\nRevision Block Array\nBLEN\nreal(200)\nBolt length\nBLEXSS\nreal\nBending Leave Excess\nBLNK\nlogical\nAuto-blanking flag\nBLRF\nelement(10)\nBolt reference array\nBLSLEN\nreal\nLength of blasting contours\nBLTM\nstring(3)\nBolt method\nBLTR\nelement\nBolt reference\nBLTW\nreal\nStandard Bolt weight\nBMAR\nreal\nAuto-blanking margin\nBMAX\ninteger\nMaximum bend number in current spool drawing\nBMCLOC\nlogical\nTrue if bending machine bends clockwise\nBMLEVE\nreal(100)\nBeam levels from owning element\nBNDARE\nreal\nBoundary line area\nBNDOFF\nreal\nOffset from boundary\nBNLENI\nreal\nLength of vertical bevel\nBNLENV\nreal\nLength of V-Bevel\nBNLENX\nreal\nLength of X-Bevel\nBNLENY\nreal\nLength of Y-Bevel\nBOCOLO\ninteger\nBackface and Obscured face colour\nBOCONU\ninteger\nObscured Backface colour number\nBOCRGB\ninteger(4)\nBackfaceObscured RGB colour\nBOCRGP\ninteger(4)\nBackfaceObscured RGB colour physical\nBOLTPARTNUMBERS\ninteger(20)\nSpooling bolt part numbers\nBOLTYP\ninteger\nBolt Type Number\nBORE\nreal\nBore\nBOREAR\nreal(10)\nBore array\nBOSTYL\ninteger\nBackface and Obscured face Style\nBOTCUT\nreal\nBottom Stile Cut Distance\nBOTHEI\nreal\nBottom height\nBOTSTR\nreal\nBOTT Stringer Gap\nBPANNR\ndir\nCurved base panel normal\nBPANOR\nori\nCurved base panel orientation\nBPANRE\nelement\nBase panel reference\nBPOF\nreal(4)\nLeader bend point offset\nBPOFTX\nstring(80)\nLeader bend point offset text\nBPRO\nreal\nSpot value of property B\nBPTYPE\ninteger\nBasic Profile Type\nBRACKE\nstring\nBrackets code\nBRAD\nreal\nBend radius\nBRALNK\nelement(20)\nConnectivity SCBRAN-BRANCH Link\nBRANBO\nreal(200)\nArray of branch bore excluding arrive and leave\nBRANDI\nstringarray(200)\nArray of branch bore direction excluding the arrive and leave\nBRARLN\nreal\nBracket arm length\nBRARLT\nreal(10)\nBracket arm lengths\nBRCOG\npos\nBranch centre of gravity\nBRCONNECT\nelement(5000)\nBranch member connections\nBREARE\nreal\nBranch external surface area\nBREF\nelement\nBranch Reference\nBRIARE\nreal\nBranch internal surface area\nBRICOG\npos\nBranch insulated centre of gravity\nBRIRAD\nreal\nBridge radius\nBRIWEI\nreal\nBranch insulated weight\nBRLEG\nelement(5000)\nBranch members on the same leg\nBRLIST\nreal(500)\nBend radii of a cable\nBRLO\ninteger\nBranch Positioning Status code (Router)\nBRNCOM\nstring(320)\nBurner comment\nBRNFAC\nreal\nBurning factor\nBRNGSP\nreal\nBottom Rung Spacing\nBRNLEN\nreal\nLength of burning contours\nBRNNAM\nstring(26)\nBurner name\nBRNNUM\ninteger\nBurner number\nBRNPRC\nstring(26)\nBurner process name\nBRNREF\nstring(26)\nBurner reference id\nBRNSEQ\nstring(26)\nBurning sequence number\nBRNST\ninteger\nNumber of starts for burning\nBRNTOO\ninteger\nBurner tool\nBRNTYP\nstring(26)\nBurner type\nBRPOSA\nreal(2)\nFirst bridge definition point\nBRPOSB\nreal(2)\nSecond bridge definition point\nBRPOSS\nreal(2)\nBridge definition side point\nBRREF\nelement\nBranch table reference\nBRREFA\nelement\nNested part reference\nBRREFB\nelement\nNested part reference\nBRTXRF\nelement(500)\nReturn reference from Branch Table element to SPECs\nBRTYP\ninteger\nBridge type\nBRWCOG\npos\nBranch wet centre of gravity\nBRWEIG\nreal\nBranch weight\nBRWICOG\npos\nBranch wet insulated centre of gravity\nBRWIWEI\nreal\nBranch insulated wet weight\nBRWWEI\nreal\nBranch wet weight\nBSCANG\nreal\nBend Segment Cut Angle\nBSCLL\nreal\nCentre-Line Length of a mitred Bend Segment\nBSDWG\nstring(120)\nAutoCAD backing sheet name\nBSEL\nstring(3)\nBolt Selector\nBSFN\nstring(1024)\nBacking sheet filename\nBSLAYE\nstring(120)\nAutoCAD backing sheet layer\nBSMNIL\nreal\nMinimum Length of Insulation of a mitred Bend Segment\nBSMNL\nreal\nMinimum Length of a mitred Bend Segment\nBSMXIL\nreal\nMaximum Length of Insulation of a mitred Bend Segment\nBSMXL\nreal\nMaximum Length of a mitred Bend Segment\nBSPE\nelement\nBolt specification\nBSRF\nelement\nBacking sheet reference\nBSRFA\nelement(500)\nADP backing sheet list\nBSTA\ninteger\nBranch Status code (Router)\nBTEX\nstring(1000)\nAnnotation text string\nBTHK\nstring(1000)\nParameterised bolt thickness\nBTLS\nword(50)\nBoundary Former type list\nBTOL\nstring(1000)\nBore tolerance\nBTOTAL\ninteger\nBolt joint total\nBTOTWE\nreal\nBolt total weight\nBTYP\nstring(1000)\nBolt type\nBUFS\ninteger\nPreferred buffer size\nBUIL\nlogical\nBuilt/Unbuilt flag\nBULG\nreal\nBulge factor\nBUNI\nword\nBore units\nBUNREF\nelement\nCable bundle reference\nBURF\nelement\nReference to real Building Element\nBURNID\nstring(80)\nBurner id\nBUYMRK\nstring(26)\nBuying mark\nBVCODN\ninteger\nBevelled Code number\nBVIS\nlogical\nBottom visibility flag\nBVSCLL\nreal\nCentre-Line Length of a mitred Bend Segment\nBVSEGN\ninteger\nBevelled segment number\nBVSMNI\nreal\nMinimum Length of Insulation of a Virtual mitred Bend end-Segment\nBVSMNL\nreal\nMinimum Length of a virtual mitred Bend end-Segment\nBVSMXI\nreal\nMaximum Length of Insulation of a Virtual mitred Bend end-Segment\nBVSMXL\nreal\nMaximum Length of a virtual mitred Bend end-Segment\nBWEI\nreal(200)\nBolt weight\nBWIDTH\nreal\nBridge width\nBWITHF\nlogical\nBend with flow\n\n\n"}
{"Headers": "Attribute C", "Content": "CABBOX\nreal(6)\n\nCalculated box volume in world coordinates\nCABCOL\nstring(120)\n\nCable colour\nCABGAP\nreal\n\ncable gap on cabletray as multiple of OUTD\nCABINT\nstring(120)\n\ncable interference class\nCAGOFF\nreal\n\nCage Offset\nCAGSIZ\nreal\n\nCage Size\nCANCOP\nlogical\n\nControl of UDA copy through .NET Db API\nCANDRM\nlogical\n\nCan drum\nCAPTIO\nstring(120)\n\nCaption\nCARD\ninteger(2)\n\nCardinality definition\nCARE\nstring(12)\n\nIsodraft Compipe: Area\nCASELIST\nstringarray(100)\nattr\nList of cases set for a UDA\nCASENAME\nstring(120)\n\nCase Name\nCASENM\nstring(120)\n\nCase Name\nCASR\nelement\n\nCase reference\nCATANO\nstring(120)\n\nText storing unique display name for Cable\nCATMOD\ninteger\n\nCatalogue Geometry Modified- Not directly query able\nCATR\nelement\n\nCatalogue reference\nCATTEX\nstring(725)\n\nConcatenation of Detailing and Material Texts\nCATUSR\nelement\n\nCategory owner\nCATY\ninteger\n\nCard type\nCAXISE\nstring\n\nCoordinate axis enumerated\nCAXISI\ninteger\n\nCoordinate axis\nCBACXR\nreal\ninteger\nAccumulated cables xarea at route node\nCBCOG\npos\n\nCable centre of gravity\nCBCULE\nreal\n\nCut Length of cable\nCBFRLE\nreal(20)\n\nFree Length of cable\nCBGELE\nreal\n\nGeometric Length of cable\nCBNUCW\nelement(500)\n\nCables at a point on a cableway\nCBPOSA\nreal(2)\n\nFirst cut bridge definition point\nCBPOSB\nreal(2)\n\nSecond cut bridge definition point\nCBPREF\nelement(500)\n\nReferences to POINTR forming route of a cable\nCBRNLS\nelement(500)\n\nList of route nodes that cable passes\nCBRRLS\nelement(500)\n\nList of route nodes and rattas that cable passes\nCBRWGL\nreal\n\nRaw Geometric Length of cable\nCBSTA\ninteger\n\nCable routing status\nCBSTAT\nstring(700)\ninteger\nCable routing status text\nCBSTT\nstring(10)\n\nCable status text\nCBTOLE\nreal\n\nTotal Length of Cable\nCBWEIG\nreal\n\nCable weight\nCCEN\ninteger\n\nCost centre\nCCLA\ninteger\n\nCost class\nCCOL\ninteger\n\nColour (in catalogue)\nCCON\nword\n\nConnection type\nCCOREF\nelement\n\nCable core set reference\nCCORRE\nelement\n\nCable Core set reference\nCCORXR\nelement(500)\n\nReturn reference from CCORSET element to SCOMs\nCDET\nelement\n\nCatalogue detail\nCDIST\nreal\n\nCurveDistance\nCDPL\nword(100)\n\nList of valid current design properties\nCDPR\nreal\nword\nCurrent design dataset property\nCDRG\nstring(24)\n\nIsodraft Compipe: Drawing number\nCELLID\ninteger(2)\n\nCell Identifier\nCELLTO\nreal\n\nTotal Number of Cell\nCELLTR\nreal\n\nTotal Number of Trimmed Cells\nCELLWH\nreal\n\nTotal Number of Untrimmed Cells\nCELREF\nelement\n\nStatus Element reference\nCEND\nstring\n\nConnection at other end of CREF (HEAD or TAIL)\nCENGRA\npos\n\nFactory Standard Part Centre of Gravity\nCENRADIUS\nreal\n\nCentreline Radius\nCERF\nelement(500)\n\nArray of Faces generated by this\nCEXES\nreal(4)\n\nCable excesses\nCEXS\nreal\n\nPercentage excess for passing cables\nCFCHE\nlogical\n\nFill level check\nCFDP\nelement\nword\nCurrent design dataset property\nCFFA\nelement(500)\n\nArray of Faces generated by this\nCFGCTX\nstring(120)\n\nConfiguration key context\nCFGEO\nreal(8)\n\nCut free definition curve\nCFGIAV\ninteger(2147483647)\n\nConfiguration integer array value\nCFGIV\ninteger\n\nConfiguration integer value\nCFGKRE\nelement\n\nConfiguration key reference\nCFGLAV\nlogical(2147483647)\n\nConfiguration logical array value\nCFGLV\nlogical\n\nConfiguration logical value\nCFGNAM\nstring(50)\n\nConfiguration key name\nCFGOVR\nlogical\n\nConfiguration Override Flag\nCFGRAV\nreal(2147483647)\n\nConfiguration real array value\nCFGRV\nreal\n\nConfiguration real value\nCFGTAV\nstringarray(2147483647)\n\nConfiguration text array value\nCFGTV\nstring(2048)\n\nConfiguration text value\nCFGTYP\nstring(120)\n\nConfiguration value type\nCFILL\nreal\n\nFill level at route node\nCFKEYP\nstring(2000)\n\nConfiguration key path\nCFRA\nelement(10)\n\nCofitting reference array for Pfittings\nCGROFF\nreal\n\nGrid position offset\nCGrPos\ninteger(100)\n\nCoordinate grid positions\nCHALEN\nreal\n\nLength of chamfer intervals\nCHAM\nreal(2)\n\nChamfer lengths\nCHANUM\ninteger\n\nNumber of chamfer intervals\nCHAR\ninteger\n\nCharacter set\nCHARGE\nstring(75)\n\nCharge\nCHCOLO\ninteger\n\nDimension crosshairs colour\nCHCONU\ninteger\n\nCrosshairs colour number\nCHCRGB\ninteger(4)\n\nRGB dimension crosshairs colour\nCHCRGP\ninteger(4)\n\nRGB dimension crosshairs colour physical\nCHDCOLUMN\nelement\n\nChild column\nCHECKE\nstring(1000)\n\nChecker\nCHEI\nreal\n\nCharacter height\nCHEIGL\nreal\n\nGLabel style character height\nCHEITX\nstring(80)\n\nCharacter height text\nCHKDAT\nstring(120)\n\nDate checked\nCHKSUM\nstring(32)\n\nMD5 checksum\nCHNGD\ninteger\n\nChanged counter\nCHOS\nreal\n\nCrosshairs overshoot\nCHOSTX\nstring(80)\n\nCrosshairs overshoot text\nCHPN\ninteger\n\nCrosshairs pen\nCHSTREF\nelement\n\nCrosshairs linestyle Reference\nCHSTYL\ninteger\n\nCrosshairs linestyle\nCIMPED\nreal\n\nConductor impedance\nCIRCR\nreal(4)\n\nCircumscribed rectangle\nCIWE\nstring(1000)\n\nTotal insulation weight\nCKEY\nword\n\nISODRAFT end condition key\nCLADNO\nstring(120)\n\nAdditional notations\nCLAI\ninteger\n\nClaim mode\nCLAIMDB\nstring(10)\n\nImplicit or explicit claims\nCLALEN\nreal\n\nclamping length\nCLANAM\nstringarray(10)\n\nClass Name\nCLBASE\nreal\n\nColumn base offset\nCLCCNT\ninteger\n\nClaim list changes count\nCLCOLO\ninteger\n\nCentreline colour\nCLCONN\nelement(5000)\ninteger\nElements that Clasher considers to be connected (and hence no clashes)\nCLCONU\ninteger\n\nCentreline colour number\nCLCUTO\nreal\n\nCutting length cutouts\nCLEIB\nreal\n\nCutting length end, no bevel or butt\nCLEVB\nreal\n\nCutting length end, V bevel\nCLEXB\nreal\n\nCutting length end, X bevel\nCLEYB\nreal\n\nCutting length end, Y bevel\nCLFG\nlogical\n\nCentreline flag\nCLFL\nlogical\n\nCentreline flag\nCLGRND\nreal\n\nTotal grinding length\nCLHO\nreal\n\nclearance hole\nCLHOLE\nreal\n\nCutting length holes\nCLHULL\nstring(120)\n\nHull\nCLICEC\nstring(120)\n\nIce class\nCLIPCD\ninteger\n\nClip code\nCLIST\nelement(500)\ninteger\nAll cables attached to route node\nCLLE\nreal\n\nBranch centreline length\nCLLENA\nreal\n\nFirst corner loop length\nCLLENB\nreal\n\nSecond corner loop length\nCLMACH\nstring(120)\n\nMachinery\nCLMID\nstring(120)\n\nUnique system ID of user claiming element\nCLMIDL\nstring(256)\n\nUnique system ID of user claiming element (long)\nCLMNUM\ninteger\n\nUser or extract number claiming element. Extract numbers are negative\nCLMO\nstring\n\nCentreline mode: 1=CL OFF, 2=CL ON\nCLMPLN\nreal\n\nClamping length of manufactured profile\nCLMRGB\ninteger(4)\n\nRGB column colour\nCLMRGP\ninteger(4)\n\nRGB column colour physical\nCLMTIE\nelement(4)\n\nReference to elements that are automatically claimed along with this element\nCLNCOD\nstring(120)\n\nCeiling Code\nCLNELE\nreal\n\nCeiling Elevation\nCLNELS\nelement(100)\n\nReferences to panels or components in the same clone chain\nCLNFAC\nreal\n\nCleaning factor\nCLNHEI\nreal\n\nCeiling Height\nCLNOTC\nreal\n\nCutting length notches\nCLNREF\nelement(100)\n\nReferences to clones of this element\nCLNRGB\ninteger(4)\n\nRGB centreline colour\nCLNRGP\ninteger(4)\n\nRGB centreline colour physical\nCLNTYP\nstring(120)\n\nCeiling Type\nCLNVOI\nreal\n\nCeiling Void Height\nCLOSED\nlogical\n\nTrue if plate covering entire referenced component\nCLOSEFLAG\nlogical\n\nTrue if branch is closed\nCLPN\ninteger\n\nCentreline pen\nCLPOS\nreal(2)\n\nCorner loop definition point\nCLRAD\nreal\n\nCorner loop radius\nCLRF\nelement\n\nActual circulation list reference\nCLRISS\nlogical\n\nClear lower parts on issue\nCLRSIZ\nreal(2)\n\nClearance size\nCLSARE\nstring(120)\n\nService area\nCLSNAM\nstring(120)\n\nClass Name\nCLSTREF\nelement\n\nCentreline linestyle Reference\nCLSTYL\ninteger\n\nCentreline linestyle\nCLSTYP\ninteger\n\nClass Type\nCLSURI\nstring(200)\n\nClass URI Pseudo\nCLTOT\nreal\n\nTotal cutting length\nCLTRID\ninteger\n\nCloning transformation composition index\nCLUTCH\nword\n\nBending machine insertion direction\nCMALL\nreal\n\nStructure allowance\nCMAXF\nreal\n\nCalculate maximum fill level on cway\nCMBOUA\nelement\n\nAft boundary\nCMBOUF\nelement\n\nFwd boundary\nCMBOUL\nelement\n\nLower boundary\nCMBOUP\nelement\n\nPs boundary\nCMBOUS\nelement\n\nStbd boundary\nCMBOUU\nelement\n\nUpper boundary\nCMBOX\nreal(6)\n\nBounding box\nCMCAT\nstring(256)\n\nCompartment category\nCMCDE\nreal\n\nContent density\nCMCTID\nstring(256)\n\nContent type ID\nCMDESC\nstring(256)\n\nCompartment description\nCMFLW\nreal\n\nFull Load Weight\nCMINF\nreal\n\nCalculate minimum fill level on cway\nCMLCV\nreal\n\nLongitudinal centre of total volume\nCMMGE\ninteger\n\nMerged compartment indicator\nCMNTID\nstring(32)\n\nDetailing Comment ID\nCMPER\nreal\n\nCompartment permeability\nCMPERD\nreal\n\nPermeability for use in damage\nCMPLNK\nelement\n\nReturn reference from schematic or design element to CYMLNK element\nCMPR\nelement\n\nComponent reference\nCMPRFA\nelement(500)\n\nAll components for the PipePiece\nCMPSTATUS\nword\n\nConnectivity comparison status\nCMPSTS\nstring(120)\n\nConnectivity comparison status description\nCMPURP\nstring(256)\n\nPurpose\nCMTCV\nreal\n\nTransverse centre of total volume\nCMTYP\ninteger\n\nType of compartment\nCMVCV\nreal\n\nVertical centre of total volume\nCMVOL\nreal\n\nTotal volume\nCNSTRF\nelement\n\nConnector style reference\nCNTNUM\ninteger\n\nContour number\nCNTYPE\ninteger\n\nContour Type Number\nCNUM\nstring(22)\n\nIsodraft Compipe: Line number\nCOCDRE\nelement(500)\nword\nCOCDESS with same COCONN value as qualifier\nCOCONN\nword\n\nCOCO Connection type\nCOCORE\nelement(2)\n\nCOCO description reference\nCOCOXR\nelement(500)\n\nCOCO description return reference\nCOCSAM\nelement(500)\n\nCOCOS with same CTYP value as COCDES\nCOFF\nreal\n\nOffset\nCOFVEC\nreal(3)\n\nCurve Vector\nCOLCOL\ninteger\n\nColumn colour\nCOLCON\ninteger\n\nColumn colour number\nCOLNUM\ninteger\n\nPin column number\nCOLRGB\ninteger(4)\n\nRGB colour\nCOLRGP\ninteger(4)\n\nRGB colour physical\nCOLSCH\nstring(120)\n\nColor Schema\nCOLSTREF\nelement\n\nColumn linestyle Reference\nCOLSTY\ninteger\n\nColumn linestyle\nCOLXSP\nreal(100)\n\nSpacing between columns in the X direction of the tower\nCOLYSP\nreal(100)\n\nSpacing between columns in the Y direction of the tower\nCOMBOO\nword\n\nBoolean Combination\nCOMM\nstring(120)\n\nComment\nCOMMST\nstring(500)\n\nComment string\nCOMNT\nstring\n\nComment\nCOMPEN\nlogical\n\nCompensate bending activities for springback\nCOMPID\ninteger(100)\n\nComponent identity\nCOMPRE\nelement\n\nSupported component reference\nCOMPTYPE\nword\n\nType of component\nCOMSTA\nstring(256)\n\nComment string 1\nCONAM\nstring\n\nCutout name\nCONARR\nword(10)\n\nConnection array\nCONATS\nelement(500)\n\nList of attachment connected to attachment\nCONATT\nstring(5000)\n\nReferenced conceptual model attribute\nCONBRA\nelement(500)\n\nList of branches connected to branch\nCONCD\ninteger\n\nConnection code\nCOND\ninteger(500)\n\nAccess Control Logical condition\nCONDES\nstring\n\nConnection string\nCONDGR\ninteger\n\nNo of Conductor Groups\nCONERF\nelement\n\nConnection End Ref\nCONMTL\nelement\n\nConductor material\nCONNE\nlogical\n\nSegment end connection flag\nCONNECTIONS\nelement(5000)\n\nConnections\nCONNECTIONSH\nelement(5000)\n\nConnections for all descendants\nCONNECTSERVICEID\nstring(120)\n\nConnect service ID of the uploaded project in cloud\nCONNER\nstring(300)\ninteger\nConnection error message\nCONNRE\nelement(10)\n\nReferences to other element\nCONNS\nlogical\n\nSegment start connection flag\nCONREF\nelement\n\nReferences to other connected element\nCONRF\nelement\n\nConnector reference\nCONSIS\nlogical\n\nPosition consistency\nCONSRF\nelement\n\nConnection Start Ref\nCONSUPPORTS\nelement(500)\n\nAll connected supports to the element tree under an element\nCONTRA\nelement(500)\n\nList of trays connected to branch\nCONTYP\nstring\n\nConnection type\nCOPI\ninteger\n\nNumber of copies\nCOPYDB\nelement(8191)\n\nCopies of this database\nCORA\nstring(1000)\n\nCorrosion thickness\nCORCGR\nstring(120)\ninteger\ncable core conductor group\nCORCOD\nstring(120)\n\nCore code\nCORCOM\nstring(120)\n\nCore composition\nCORCON\nelement(50)\n\nCOR Configurations\nCORGRP\ninteger\n\nCore Group\nCORNUM\ninteger\n\nCorner number\nCORNUV\npos\n\nCorner point\nCORROS\nreal\n\nTube corrosion\nCORRUG\nlogical\n\nTrue if corrugation is defined on the plate part\nCORSZ\nreal\n\nSize of the core\nCORTAG\nstring(120)\ninteger\ncable core tag\nCORTYP\nstring(120)\n\nCore type\nCOSTES\nstring(256)\n\nCost estimator\nCOUN\ninteger\n\nCounter\nCOVHOL\nlogical\n\nCover hole\nCPAR\nreal(100)\n\nCatalogue parameters\nCPARTS\nelement(4)\n\nConnection parts\nCPEN\ninteger\n\nPen for internal columns\nCPFA\nelement(500)\n\nArray of Ports this points to\nCPHASE\nelement\n\nReference to Construction Phase\nCPLO\nstring(120)\n\nPlot (in catalogue)\nCPOF\nreal(2)\n\nLeaderline connection point wrt. text origin\nCPOFTX\nstring(80)\n\nLeaderline connection point text\nCPOS\npos\n\nconditioning position for curve geometry\nCPRIND\nword(2)\n\nConnection point instance repeat index\nCPRIO\ninteger\n\nConnector priority flag\nCPRO\nreal\n\nSpot value of property C\nCPSDAT\nblob(2147483647)\n\nCPS Data\nCPSRCR\nelement\n\nConnection point instance source reference\nCPUL\nreal(3)\n\nCold pull - translational\nCPUT\nreal(3)\n\nCold pull - twist\nCRCANG\nreal\n\nTurning angle for least circumscribed rectangle\nCRCLW\nreal(2)\n\nLength and width of least circumscribed rectangle\nCRDATE\nstring(120)\nattr\nDate element created in current DB or if extract in ascendant\nCREACT\nreal\n\nConductor reactance\nCREANCESTORS\nlogical\n\nCreate ancestors\nCREF\nelement\n\nConnection reference\nCRESIS\nreal\n\nConductor resistance\nCREXTR\ninteger\nattr\nExtract element created in current DB or if extract in ascendant\nCRFA\nelement(10)\n\nConnection reference array\nCRINFO\nstring(200)\n\nDB creation information\nCRIT\ninteger(1000)\n\nSelection criteria (used to define tag & rep. rules)\nCRSAOS\nelement\n\nSymbolic cross section abut other side style reference\nCRSATS\nelement\n\nSymbolic cross section abut this side style reference\nCRSESS\ninteger\nattr\nSession element created in current DB or if extract in ascendant\nCRSNR\nelement\n\nSymbolic cross section style reference\nCRSOS\nelement\n\nSymbolic cross section other side style reference\nCrspn\nelement\n\nSymbolic cross section penetration style reference\nCRSTHS\nelement\n\nSymbolic cross section this side style reference\nCRUSER\nstring(120)\nattr\nUser created element in current DB or if extract in ascendant\nCSESS\nstring(640)\ninteger\nComment entered for specified session\nCSFBR\nlogical\n\nSpooling marker for components\nCSGBOX\nreal(6)\n\nCSG-Calculated box volume in world coordinates\nCSPA\nreal\n\nCharacter spacing factor\nCSPATX\nstring(80)\n\nCharacter spacing factor (as text)\nCSPC\nstring(6)\n\nIsodraft Compipe: Specification\nCSTA\nstring(120)\n\nCatalogue Standard\nCSTMER\nstring(256)\n\nCustomer\nCSTMRN\nstring(256)\n\nCustomer number\nCSTR\nelement\n\nConstraint reference\nCTCREF\nelement\ninteger\nCable tray component ref\nCTHATP\ninteger\n\nCommenting attachment purpose\nCTHCFC\nelement\n\nClosed LOV reference\nCTHCFO\nelement\n\nOpen LOV reference\nCTHCTP\nstring(120)\n\nCommenting content type\nCTHICK\nreal\n\nCoating thickness\nCTHID\nelement\n\nThread Id\nCTHLIS\nelement(500)\n\nList of attached comment threads\nCTHMAS\nelement\n\nCommenting world Master reference\nCTHREF\nelement\n\nComment Element reference\nCTHSEL\ninteger(500)\n\nSelection expression\nCTHSTA\ninteger\n\nCommenting thread state (Open/Close)\nCTHSTT\nstring(20)\n\nThread state text\nCTHTEX\nstring(1000)\n\nCommenting text\nCTHTOL\nelement(500)\n\nList elements assigned to a comment threads\nCTHWLI\nelement(20)\n\nList of Commenting worlds\nCTSPE\nelement\n\nCable tray specification\nCTTYP\nword\n\nCable tray typ\nCTXPSP\ninteger\n\nConnector Text Position (ByVStyle, Centre, Start, End)\nCTXT\nstring(120)\n\nCard text\nCTXTPS\nstring(120)\n\nConnector Text Position (as text)\nCTYA\nword\n\nAttached connection type\nCTYE\nword\n\nEnd connection type\nCTYO\nword\n\nOwning connection type\nCTYP\nword(2)\n\nConnection type\nCTYPLI\nword(5000)\n\nList of COCO Ctypes\nCTYS\nword\n\nStart connection type\nCUALWD\nlogical\n\nIndicates compare update window is allowed\nCURD\nelement(5000)\n\nCurrent DBs\nCURF\nstring\n\nCurve fitting code: 1 default, 2 cubicfit\nCURLOC\nelement\n\nTrue current location\nCURNAM\nstring(120)\n\nCurve Name\nCURREN\nstring(1000)\n\nCurrent\nCURRFULL\nelement(5000)\n\nList of current DBs in MDB, expanding DBsets\nCURTYP\nword\n\nCurve type\nCURVED\nlogical\n\nTrue if curved plate part.\nCUSDIR\nlogical\n\nCurve Segment Direction Start to End\nCUSOFF\nreal\n\nCurve Segment Offset\nCUSRAD\nreal\n\nCurve Segment Radius\nCUSVAL\nstring(4000)\n\nDelimited Custom Value List\nCUTALW\nreal\n\nCutting allowance\nCUTB\nreal\n\nCutback\nCUTL\nreal\n\nCut length\nCUTLAR\nreal(50)\n\nCut Length Array\nCUTMIN\nreal\n\nCutting allowance minimum length\nCUTNAM\nstring(700)\ninteger\nFull name of element, truncated to n characters\nCUTNMN\nstring(700)\ninteger\nFull name of element (without leading slash) truncated to n characters\nCUTP\ndir\n\nCutting plane normal\nCUTVEC\ndir\n\nCut plane normal\nCVALS\nreal(100)\n\nCoordinate values\nCWBMAT\nstring(700)\n\nCableway branch material type\nCWEI\nstring(1000)\n\nTotal component weight\nCWHEAD\nelement(500)\n\nCableway Head\nCWHPOS\npos\n\nCableway path head point position\nCWIDTH\nreal\n\nClearance Width\nCWJBLS\nelement(500)\n\nCableway branches and junction boxes list\nCWJUSL\nword\n\nCable Way Justification Line\nCWLIST\nelement(500)\n\nAll cableways attached to route node\nCWPPJB\nelement(500)\n\nCableway branches and pull pits and junction boxes list\nCWPPLS\nelement(500)\n\nCableway branches and pull pits list\nCWTAIL\nelement(500)\n\nCableway Tail\nCWTPOS\npos\n\nCableway path tail point position\n\nAttribute Name\nData Type\nQualifier\nDescription\nCABBOX\nreal(6)\nCalculated box volume in world coordinates\nCABCOL\nstring(120)\nCable colour\nCABGAP\nreal\ncable gap on cabletray as multiple of OUTD\nCABINT\nstring(120)\ncable interference class\nCAGOFF\nreal\nCage Offset\nCAGSIZ\nreal\nCage Size\nCANCOP\nlogical\nControl of UDA copy through .NET Db API\nCANDRM\nlogical\nCan drum\nCAPTIO\nstring(120)\nCaption\nCARD\ninteger(2)\nCardinality definition\nCARE\nstring(12)\nIsodraft Compipe: Area\nCASELIST\nstringarray(100)\nattr\nList of cases set for a UDA\nCASENAME\nstring(120)\nCase Name\nCASENM\nstring(120)\nCase Name\nCASR\nelement\nCase reference\nCATANO\nstring(120)\nText storing unique display name for Cable\nCATMOD\ninteger\nCatalogue Geometry Modified- Not directly query able\nCATR\nelement\nCatalogue reference\nCATTEX\nstring(725)\nConcatenation of Detailing and Material Texts\nCATUSR\nelement\nCategory owner\nCATY\ninteger\nCard type\nCAXISE\nstring\nCoordinate axis enumerated\nCAXISI\ninteger\nCoordinate axis\nCBACXR\nreal\ninteger\nAccumulated cables xarea at route node\nCBCOG\npos\nCable centre of gravity\nCBCULE\nreal\nCut Length of cable\nCBFRLE\nreal(20)\nFree Length of cable\nCBGELE\nreal\nGeometric Length of cable\nCBNUCW\nelement(500)\nCables at a point on a cableway\nCBPOSA\nreal(2)\nFirst cut bridge definition point\nCBPOSB\nreal(2)\nSecond cut bridge definition point\nCBPREF\nelement(500)\nReferences to POINTR forming route of a cable\nCBRNLS\nelement(500)\nList of route nodes that cable passes\nCBRRLS\nelement(500)\nList of route nodes and rattas that cable passes\nCBRWGL\nreal\nRaw Geometric Length of cable\nCBSTA\ninteger\nCable routing status\nCBSTAT\nstring(700)\ninteger\nCable routing status text\nCBSTT\nstring(10)\nCable status text\nCBTOLE\nreal\nTotal Length of Cable\nCBWEIG\nreal\nCable weight\nCCEN\ninteger\nCost centre\nCCLA\ninteger\nCost class\nCCOL\ninteger\nColour (in catalogue)\nCCON\nword\nConnection type\nCCOREF\nelement\nCable core set reference\nCCORRE\nelement\nCable Core set reference\nCCORXR\nelement(500)\nReturn reference from CCORSET element to SCOMs\nCDET\nelement\nCatalogue detail\nCDIST\nreal\nCurveDistance\nCDPL\nword(100)\nList of valid current design properties\nCDPR\nreal\nword\nCurrent design dataset property\nCDRG\nstring(24)\nIsodraft Compipe: Drawing number\nCELLID\ninteger(2)\nCell Identifier\nCELLTO\nreal\nTotal Number of Cell\nCELLTR\nreal\nTotal Number of Trimmed Cells\nCELLWH\nreal\nTotal Number of Untrimmed Cells\nCELREF\nelement\nStatus Element reference\nCEND\nstring\nConnection at other end of CREF (HEAD or TAIL)\nCENGRA\npos\nFactory Standard Part Centre of Gravity\nCENRADIUS\nreal\nCentreline Radius\nCERF\nelement(500)\nArray of Faces generated by this\nCEXES\nreal(4)\nCable excesses\nCEXS\nreal\nPercentage excess for passing cables\nCFCHE\nlogical\nFill level check\nCFDP\nelement\nword\nCurrent design dataset property\nCFFA\nelement(500)\nArray of Faces generated by this\nCFGCTX\nstring(120)\nConfiguration key context\nCFGEO\nreal(8)\nCut free definition curve\nCFGIAV\ninteger(2147483647)\nConfiguration integer array value\nCFGIV\ninteger\nConfiguration integer value\nCFGKRE\nelement\nConfiguration key reference\nCFGLAV\nlogical(2147483647)\nConfiguration logical array value\nCFGLV\nlogical\nConfiguration logical value\nCFGNAM\nstring(50)\nConfiguration key name\nCFGOVR\nlogical\nConfiguration Override Flag\nCFGRAV\nreal(2147483647)\nConfiguration real array value\nCFGRV\nreal\nConfiguration real value\nCFGTAV\nstringarray(2147483647)\nConfiguration text array value\nCFGTV\nstring(2048)\nConfiguration text value\nCFGTYP\nstring(120)\nConfiguration value type\nCFILL\nreal\nFill level at route node\nCFKEYP\nstring(2000)\nConfiguration key path\nCFRA\nelement(10)\nCofitting reference array for Pfittings\nCGROFF\nreal\nGrid position offset\nCGrPos\ninteger(100)\nCoordinate grid positions\nCHALEN\nreal\nLength of chamfer intervals\nCHAM\nreal(2)\nChamfer lengths\nCHANUM\ninteger\nNumber of chamfer intervals\nCHAR\ninteger\nCharacter set\nCHARGE\nstring(75)\nCharge\nCHCOLO\ninteger\nDimension crosshairs colour\nCHCONU\ninteger\nCrosshairs colour number\nCHCRGB\ninteger(4)\nRGB dimension crosshairs colour\nCHCRGP\ninteger(4)\nRGB dimension crosshairs colour physical\nCHDCOLUMN\nelement\nChild column\nCHECKE\nstring(1000)\nChecker\nCHEI\nreal\nCharacter height\nCHEIGL\nreal\nGLabel style character height\nCHEITX\nstring(80)\nCharacter height text\nCHKDAT\nstring(120)\nDate checked\nCHKSUM\nstring(32)\nMD5 checksum\nCHNGD\ninteger\nChanged counter\nCHOS\nreal\nCrosshairs overshoot\nCHOSTX\nstring(80)\nCrosshairs overshoot text\nCHPN\ninteger\nCrosshairs pen\nCHSTREF\nelement\nCrosshairs linestyle Reference\nCHSTYL\ninteger\nCrosshairs linestyle\nCIMPED\nreal\nConductor impedance\nCIRCR\nreal(4)\nCircumscribed rectangle\nCIWE\nstring(1000)\nTotal insulation weight\nCKEY\nword\nISODRAFT end condition key\nCLADNO\nstring(120)\nAdditional notations\nCLAI\ninteger\nClaim mode\nCLAIMDB\nstring(10)\nImplicit or explicit claims\nCLALEN\nreal\nclamping length\nCLANAM\nstringarray(10)\nClass Name\nCLBASE\nreal\nColumn base offset\nCLCCNT\ninteger\nClaim list changes count\nCLCOLO\ninteger\nCentreline colour\nCLCONN\nelement(5000)\ninteger\nElements that Clasher considers to be connected (and hence no clashes)\nCLCONU\ninteger\nCentreline colour number\nCLCUTO\nreal\nCutting length cutouts\nCLEIB\nreal\nCutting length end, no bevel or butt\nCLEVB\nreal\nCutting length end, V bevel\nCLEXB\nreal\nCutting length end, X bevel\nCLEYB\nreal\nCutting length end, Y bevel\nCLFG\nlogical\nCentreline flag\nCLFL\nlogical\nCentreline flag\nCLGRND\nreal\nTotal grinding length\nCLHO\nreal\nclearance hole\nCLHOLE\nreal\nCutting length holes\nCLHULL\nstring(120)\nHull\nCLICEC\nstring(120)\nIce class\nCLIPCD\ninteger\nClip code\nCLIST\nelement(500)\ninteger\nAll cables attached to route node\nCLLE\nreal\nBranch centreline length\nCLLENA\nreal\nFirst corner loop length\nCLLENB\nreal\nSecond corner loop length\nCLMACH\nstring(120)\nMachinery\nCLMID\nstring(120)\nUnique system ID of user claiming element\nCLMIDL\nstring(256)\nUnique system ID of user claiming element (long)\nCLMNUM\ninteger\nUser or extract number claiming element. Extract numbers are negative\nCLMO\nstring\nCentreline mode: 1=CL OFF, 2=CL ON\nCLMPLN\nreal\nClamping length of manufactured profile\nCLMRGB\ninteger(4)\nRGB column colour\nCLMRGP\ninteger(4)\nRGB column colour physical\nCLMTIE\nelement(4)\nReference to elements that are automatically claimed along with this element\nCLNCOD\nstring(120)\nCeiling Code\nCLNELE\nreal\nCeiling Elevation\nCLNELS\nelement(100)\nReferences to panels or components in the same clone chain\nCLNFAC\nreal\nCleaning factor\nCLNHEI\nreal\nCeiling Height\nCLNOTC\nreal\nCutting length notches\nCLNREF\nelement(100)\nReferences to clones of this element\nCLNRGB\ninteger(4)\nRGB centreline colour\nCLNRGP\ninteger(4)\nRGB centreline colour physical\nCLNTYP\nstring(120)\nCeiling Type\nCLNVOI\nreal\nCeiling Void Height\nCLOSED\nlogical\nTrue if plate covering entire referenced component\nCLOSEFLAG\nlogical\nTrue if branch is closed\nCLPN\ninteger\nCentreline pen\nCLPOS\nreal(2)\nCorner loop definition point\nCLRAD\nreal\nCorner loop radius\nCLRF\nelement\nActual circulation list reference\nCLRISS\nlogical\nClear lower parts on issue\nCLRSIZ\nreal(2)\nClearance size\nCLSARE\nstring(120)\nService area\nCLSNAM\nstring(120)\nClass Name\nCLSTREF\nelement\nCentreline linestyle Reference\nCLSTYL\ninteger\nCentreline linestyle\nCLSTYP\ninteger\nClass Type\nCLSURI\nstring(200)\nClass URI Pseudo\nCLTOT\nreal\nTotal cutting length\nCLTRID\ninteger\nCloning transformation composition index\nCLUTCH\nword\nBending machine insertion direction\nCMALL\nreal\nStructure allowance\nCMAXF\nreal\nCalculate maximum fill level on cway\nCMBOUA\nelement\nAft boundary\nCMBOUF\nelement\nFwd boundary\nCMBOUL\nelement\nLower boundary\nCMBOUP\nelement\nPs boundary\nCMBOUS\nelement\nStbd boundary\nCMBOUU\nelement\nUpper boundary\nCMBOX\nreal(6)\nBounding box\nCMCAT\nstring(256)\nCompartment category\nCMCDE\nreal\nContent density\nCMCTID\nstring(256)\nContent type ID\nCMDESC\nstring(256)\nCompartment description\nCMFLW\nreal\nFull Load Weight\nCMINF\nreal\nCalculate minimum fill level on cway\nCMLCV\nreal\nLongitudinal centre of total volume\nCMMGE\ninteger\nMerged compartment indicator\nCMNTID\nstring(32)\nDetailing Comment ID\nCMPER\nreal\nCompartment permeability\nCMPERD\nreal\nPermeability for use in damage\nCMPLNK\nelement\nReturn reference from schematic or design element to CYMLNK element\nCMPR\nelement\nComponent reference\nCMPRFA\nelement(500)\nAll components for the PipePiece\nCMPSTATUS\nword\nConnectivity comparison status\nCMPSTS\nstring(120)\nConnectivity comparison status description\nCMPURP\nstring(256)\nPurpose\nCMTCV\nreal\nTransverse centre of total volume\nCMTYP\ninteger\nType of compartment\nCMVCV\nreal\nVertical centre of total volume\nCMVOL\nreal\nTotal volume\nCNSTRF\nelement\nConnector style reference\nCNTNUM\ninteger\nContour number\nCNTYPE\ninteger\nContour Type Number\nCNUM\nstring(22)\nIsodraft Compipe: Line number\nCOCDRE\nelement(500)\nword\nCOCDESS with same COCONN value as qualifier\nCOCONN\nword\nCOCO Connection type\nCOCORE\nelement(2)\nCOCO description reference\nCOCOXR\nelement(500)\nCOCO description return reference\nCOCSAM\nelement(500)\nCOCOS with same CTYP value as COCDES\nCOFF\nreal\nOffset\nCOFVEC\nreal(3)\nCurve Vector\nCOLCOL\ninteger\nColumn colour\nCOLCON\ninteger\nColumn colour number\nCOLNUM\ninteger\nPin column number\nCOLRGB\ninteger(4)\nRGB colour\nCOLRGP\ninteger(4)\nRGB colour physical\nCOLSCH\nstring(120)\nColor Schema\nCOLSTREF\nelement\nColumn linestyle Reference\nCOLSTY\ninteger\nColumn linestyle\nCOLXSP\nreal(100)\nSpacing between columns in the X direction of the tower\nCOLYSP\nreal(100)\nSpacing between columns in the Y direction of the tower\nCOMBOO\nword\nBoolean Combination\nCOMM\nstring(120)\nComment\nCOMMST\nstring(500)\nComment string\nCOMNT\nstring\nComment\nCOMPEN\nlogical\nCompensate bending activities for springback\nCOMPID\ninteger(100)\nComponent identity\nCOMPRE\nelement\nSupported component reference\nCOMPTYPE\nword\nType of component\nCOMSTA\nstring(256)\nComment string 1\nCONAM\nstring\nCutout name\nCONARR\nword(10)\nConnection array\nCONATS\nelement(500)\nList of attachment connected to attachment\nCONATT\nstring(5000)\nReferenced conceptual model attribute\nCONBRA\nelement(500)\nList of branches connected to branch\nCONCD\ninteger\nConnection code\nCOND\ninteger(500)\nAccess Control Logical condition\nCONDES\nstring\nConnection string\nCONDGR\ninteger\nNo of Conductor Groups\nCONERF\nelement\nConnection End Ref\nCONMTL\nelement\nConductor material\nCONNE\nlogical\nSegment end connection flag\nCONNECTIONS\nelement(5000)\nConnections\nCONNECTIONSH\nelement(5000)\nConnections for all descendants\nCONNECTSERVICEID\nstring(120)\nConnect service ID of the uploaded project in cloud\nCONNER\nstring(300)\ninteger\nConnection error message\nCONNRE\nelement(10)\nReferences to other element\nCONNS\nlogical\nSegment start connection flag\nCONREF\nelement\nReferences to other connected element\nCONRF\nelement\nConnector reference\nCONSIS\nlogical\nPosition consistency\nCONSRF\nelement\nConnection Start Ref\nCONSUPPORTS\nelement(500)\nAll connected supports to the element tree under an element\nCONTRA\nelement(500)\nList of trays connected to branch\nCONTYP\nstring\nConnection type\nCOPI\ninteger\nNumber of copies\nCOPYDB\nelement(8191)\nCopies of this database\nCORA\nstring(1000)\nCorrosion thickness\nCORCGR\nstring(120)\ninteger\ncable core conductor group\nCORCOD\nstring(120)\nCore code\nCORCOM\nstring(120)\nCore composition\nCORCON\nelement(50)\nCOR Configurations\nCORGRP\ninteger\nCore Group\nCORNUM\ninteger\nCorner number\nCORNUV\npos\nCorner point\nCORROS\nreal\nTube corrosion\nCORRUG\nlogical\nTrue if corrugation is defined on the plate part\nCORSZ\nreal\nSize of the core\nCORTAG\nstring(120)\ninteger\ncable core tag\nCORTYP\nstring(120)\nCore type\nCOSTES\nstring(256)\nCost estimator\nCOUN\ninteger\nCounter\nCOVHOL\nlogical\nCover hole\nCPAR\nreal(100)\nCatalogue parameters\nCPARTS\nelement(4)\nConnection parts\nCPEN\ninteger\nPen for internal columns\nCPFA\nelement(500)\nArray of Ports this points to\nCPHASE\nelement\nReference to Construction Phase\nCPLO\nstring(120)\nPlot (in catalogue)\nCPOF\nreal(2)\nLeaderline connection point wrt. text origin\nCPOFTX\nstring(80)\nLeaderline connection point text\nCPOS\npos\nconditioning position for curve geometry\nCPRIND\nword(2)\nConnection point instance repeat index\nCPRIO\ninteger\nConnector priority flag\nCPRO\nreal\nSpot value of property C\nCPSDAT\nblob(2147483647)\nCPS Data\nCPSRCR\nelement\nConnection point instance source reference\nCPUL\nreal(3)\nCold pull - translational\nCPUT\nreal(3)\nCold pull - twist\nCRCANG\nreal\nTurning angle for least circumscribed rectangle\nCRCLW\nreal(2)\nLength and width of least circumscribed rectangle\nCRDATE\nstring(120)\nattr\nDate element created in current DB or if extract in ascendant\nCREACT\nreal\nConductor reactance\nCREANCESTORS\nlogical\nCreate ancestors\nCREF\nelement\nConnection reference\nCRESIS\nreal\nConductor resistance\nCREXTR\ninteger\nattr\nExtract element created in current DB or if extract in ascendant\nCRFA\nelement(10)\nConnection reference array\nCRINFO\nstring(200)\nDB creation information\nCRIT\ninteger(1000)\nSelection criteria (used to define tag & rep. rules)\nCRSAOS\nelement\nSymbolic cross section abut other side style reference\nCRSATS\nelement\nSymbolic cross section abut this side style reference\nCRSESS\ninteger\nattr\nSession element created in current DB or if extract in ascendant\nCRSNR\nelement\nSymbolic cross section style reference\nCRSOS\nelement\nSymbolic cross section other side style reference\nCrspn\nelement\nSymbolic cross section penetration style reference\nCRSTHS\nelement\nSymbolic cross section this side style reference\nCRUSER\nstring(120)\nattr\nUser created element in current DB or if extract in ascendant\nCSESS\nstring(640)\ninteger\nComment entered for specified session\nCSFBR\nlogical\nSpooling marker for components\nCSGBOX\nreal(6)\nCSG-Calculated box volume in world coordinates\nCSPA\nreal\nCharacter spacing factor\nCSPATX\nstring(80)\nCharacter spacing factor (as text)\nCSPC\nstring(6)\nIsodraft Compipe: Specification\nCSTA\nstring(120)\nCatalogue Standard\nCSTMER\nstring(256)\nCustomer\nCSTMRN\nstring(256)\nCustomer number\nCSTR\nelement\nConstraint reference\nCTCREF\nelement\ninteger\nCable tray component ref\nCTHATP\ninteger\nCommenting attachment purpose\nCTHCFC\nelement\nClosed LOV reference\nCTHCFO\nelement\nOpen LOV reference\nCTHCTP\nstring(120)\nCommenting content type\nCTHICK\nreal\nCoating thickness\nCTHID\nelement\nThread Id\nCTHLIS\nelement(500)\nList of attached comment threads\nCTHMAS\nelement\nCommenting world Master reference\nCTHREF\nelement\nComment Element reference\nCTHSEL\ninteger(500)\nSelection expression\nCTHSTA\ninteger\nCommenting thread state (Open/Close)\nCTHSTT\nstring(20)\nThread state text\nCTHTEX\nstring(1000)\nCommenting text\nCTHTOL\nelement(500)\nList elements assigned to a comment threads\nCTHWLI\nelement(20)\nList of Commenting worlds\nCTSPE\nelement\nCable tray specification\nCTTYP\nword\nCable tray typ\nCTXPSP\ninteger\nConnector Text Position (ByVStyle, Centre, Start, End)\nCTXT\nstring(120)\nCard text\nCTXTPS\nstring(120)\nConnector Text Position (as text)\nCTYA\nword\nAttached connection type\nCTYE\nword\nEnd connection type\nCTYO\nword\nOwning connection type\nCTYP\nword(2)\nConnection type\nCTYPLI\nword(5000)\nList of COCO Ctypes\nCTYS\nword\nStart connection type\nCUALWD\nlogical\nIndicates compare update window is allowed\nCURD\nelement(5000)\nCurrent DBs\nCURF\nstring\nCurve fitting code: 1 default, 2 cubicfit\nCURLOC\nelement\nTrue current location\nCURNAM\nstring(120)\nCurve Name\nCURREN\nstring(1000)\nCurrent\nCURRFULL\nelement(5000)\nList of current DBs in MDB, expanding DBsets\nCURTYP\nword\nCurve type\nCURVED\nlogical\nTrue if curved plate part.\nCUSDIR\nlogical\nCurve Segment Direction Start to End\nCUSOFF\nreal\nCurve Segment Offset\nCUSRAD\nreal\nCurve Segment Radius\nCUSVAL\nstring(4000)\nDelimited Custom Value List\nCUTALW\nreal\nCutting allowance\nCUTB\nreal\nCutback\nCUTL\nreal\nCut length\nCUTLAR\nreal(50)\nCut Length Array\nCUTMIN\nreal\nCutting allowance minimum length\nCUTNAM\nstring(700)\ninteger\nFull name of element, truncated to n characters\nCUTNMN\nstring(700)\ninteger\nFull name of element (without leading slash) truncated to n characters\nCUTP\ndir\nCutting plane normal\nCUTVEC\ndir\nCut plane normal\nCVALS\nreal(100)\nCoordinate values\nCWBMAT\nstring(700)\nCableway branch material type\nCWEI\nstring(1000)\nTotal component weight\nCWHEAD\nelement(500)\nCableway Head\nCWHPOS\npos\nCableway path head point position\nCWIDTH\nreal\nClearance Width\nCWJBLS\nelement(500)\nCableway branches and junction boxes list\nCWJUSL\nword\nCable Way Justification Line\nCWLIST\nelement(500)\nAll cableways attached to route node\nCWPPJB\nelement(500)\nCableway branches and pull pits and junction boxes list\nCWPPLS\nelement(500)\nCableway branches and pull pits l"}
{"Headers": "Attribute D", "Content": "D\nreal\n\nPosition downing\nDACC\nstring\n\nDatabase access\nDACCLA\nlogical\n\nTrue if DAC allows element to be claimed\nDACCOH\nlogical\n\nTrue if DAC allows element hierarchy to be copied to another DB\nDACCOP\nlogical\n\nTrue if DAC allows element to be copied to another DB\nDACCRE\nlogical\nelemtype\nTrue if DAC allows element to be created\nDACDEL\nlogical\n\nTrue if DAC allows element to be deleted\nDACDRO\nlogical\n\nTrue if DAC allows element to be dropped\nDACERR\nstring(120)\nattr\nReturns the DAC error\nDACEXH\nlogical\n\nTrue if DAC allows element hierarchy to be exported\nDACEXP\nlogical\n\nTrue if DAC allows element to be exported\nDACISS\nlogical\n\nTrue if DAC allows element to be issued\nDACMOD\nlogical\nattr\nTrue if DAC allows attribute of element to be modified\nDACOUH\nlogical\n\nTrue if DAC allows element hierarchy to be output\nDACOUT\nlogical\n\nTrue if DAC allows element to be output\nDAENABLED\nstring(10)\n\nEnable Autolabels for view (as text)\nDAENI\ninteger\n\nEnable Design Element Auto Labelling for view (Off, On)\nDAEXLL\nlogical\n\nDimension auto external line length\nDAREF\nelement\n\nReference of associated dataset area\nDARREF\nelement\n\nDesign area reference\nDARSF\nelement\n\nDesign Element Auto Labelling rule set reference\nDASSCI\nelement(500)\n\nReference Array of all direct associates with constraints\nDASSOS\nelement(500)\n\nReference Array of all associations with constraints\nDATASO\nelement(10)\n\nDBView or DBViewSet reference array for Datasheet Template\nDATE\nstring(12)\n\nDate\nDATEFO\nstring\n\nDate format\nDATIM\nstring(19)\n\nLMI Date/time\nDATINT\ninteger(2)\n\nDate\nDATONE\ninteger\n\nDate 1\nDATTWO\ninteger\n\nDate 2\nDATTXT\nstring(22)\n\nDate\nDBAC\nstring\n\nDB Access, MULTIWRITE or UPDATE\nDBALL\nelement(8000)\n\nList of DBs allocated to location\nDBATTRIBUTE\nword\n\nDatabase attribute\nDBBLOB\nblob(2147483647)\n\nDatabase Binary Large Object\nDBCL\nstring\n\nDB Claim\nDBCNTL\nlogical\n\nTrue if element is in a control DB\nDBCRITERIA\ninteger(2000)\n\nCrteria(expression) for DBs in the DBset\nDBELET\nword\n\nElement type\nDBEXNO\ninteger\n\nDB Extract Number\nDBF\nelement\n\nDatabase reference attribute\nDBFI\nstring\n\nDB filename\nDBFN\ninteger\n\nDB file number\nDBHASPRODUCT\nlogical\n\nHas a product been associated with this DB?\nDBLC\nelement(1000)\n\nList of LOCs belonging to a DB\nDBLNKP\nlogical\n\nLinked Documents (DB) distribution flag\nDBLS\nelement(5000)\n\nList of DBs belonging to MDB\nDBLSFULL\nelement(5000)\n\nList of DBs belonging to MDB, expanding DBsets\nDBNA\nstring\n\nDB name\nDBNU\ninteger\n\nDB Number\nDBOT\nreal\n\nBottom diameter\nDBPR\nelement(8000)\n\nList of DBs Primary at location\nDBPRODUCTAVAILABLE\nstringarray(50)\nword\nProducts available for databases\nDBPRODUCTTEXT\nstring(1024)\n\nProduct associated with this DB\nDBPRODUCTWRITE\nlogical\nword\nFlag determining whether product can write to DB\nDBRBEG\ninteger\n\nDB range start\nDBREF\nelement\n\nDB reference\nDBREND\ninteger\n\nDB range end\nDBSESS\ninteger\n\nLast DB session\nDBSETLS\nelement(5000)\n\nList of DbSets in MDB\nDBSHIE\nelement(5000)\n\nDatabase hierarchy within a DBSET\nDBSLEV\nelement(5000)\n\nDatabases at a level within a DBSET\nDBSLIS\nelement(5000)\n\nDatabases within a DBSET\nDBSORD\nstring(120)\n\nOrder dbs in dynamic DBSET by name, type or number\nDBSSTP\nelement(8000)\n\nDBs in a stamp\nDBSTF\nelement\n\nDatabase set reference attribute\nDBTE\nstring\n\nDB Text Encoding\nDBTY\nword\n\nDB type (DESI, CATA etc)\nDBUsers\nelement(10000)\n\nCurrent Users in the system using this DB\nDBUSRX\nelement(10000)\n\nCurrent Users in the system using this DB or any extract descendants\nDBVAR\nlogical\n\nTrue if element is in a variant DB\nDBVWSTREF\nelement(50)\n\nDatabase View Set reference array\nDBWRITE\nlogical\n\nTrue if element is in a writable DB\nDCLA\nstring\n\nDatabase claim mode\nDCLNCO\nstring(120)\n\nDefault Ceiling Code\nDCLNHE\nreal\n\nDefault Ceiling Height\nDCLNTY\nstring(120)\n\nDefault Ceiling Type\nDCMPID\ninteger\n\nDefinition component identity\nDCODE\nstring\n\nDirection code\nDCON\nword\n\nDesign PPoint connection type\nDCONFINT\ninteger\n\nDraw Connector Flags Integer\nDCONFLAGS\nstring(120)\n\nDraw Connector Flags\nDCORRO\nreal\n\nDerived corrosion\nDCRFA\nelement(10)\n\nArray of Design datasets for Design Code/Criteria\nDCSTYF\nelement\n\nDesign change style reference\nDCTILT\nreal\n\nDefault Ceiling Tile Thickness\nDDDF\nstring(1000)\n\nDefault Design data value\nDDEF\nreal(3)\n\nPort distance flexibility defaults\nDDEG\nreal\n\nDimension line angle\nDDEGTX\nstring(80)\n\nRadial dimension angle text\nDDEP\ninteger\n\nDatabase depth within hierarchy (World is 0)\nDDESP\nreal(100)\n\nDesign parameters as distance\nDDIR\ndir\n\nDesign PPoint spherical direction\nDDNM\nelement\n\nDesign element reference\nDDNMX\nreal\n\nDDNM X position\nDDNMXY\nreal(2)\n\nDDNM XY position\nDDNMY\nreal\n\nDDNM Y position\nDDNX\nstring(120)\n\nDesign element as text\nDDOORS\nreal\n\nDefault Door Sill\nDDPR\nstring(1000)\n\nDesign data property value\nDDRFA\nelement(10)\n\nArray of default design datasets (for template)\nDEALAL\nlogical\n\nTrue if location locked due to deallocation of dbs\nDEALDB\nelement(300)\n\nReference array for locations where DB id being deallocated\nDECGAP\nreal\n\nDecoration Gap\nDECMOD\ninteger\n\nDecoration Mode\nDECOFF\nreal(2)\n\nDecoration offset\nDECP\ninteger\n\nDecimal places\nDECPRC\ninteger\n\nDecimal precision\nDECREP\nreal\n\nDecoration Repeat\nDECSEP\nstring\n\nDecimal separator\nDECSIZ\nreal\n\nDecoration Size\nDEFA\nreal\n\nDefault\nDEFATT\nword(2000)\n\nDefault List of all attributes for element\nDEFAULTATT\nword\n\nAttribute on default location to use for default\nDEFAULTEXP\ninteger(2000)\n\nExpression used to calculate default\nDEFAULTLOCATION\nword\n\nAttribute to follow to get default location\nDEFERD\nelement(10000)\n\nDeferred DBs in MDB\nDEFHOM\nelement\n\nDefault allocation home\nDEFLEN\nreal\n\nFixed length of the weld\nDEFLNK\nelement\n\nLink to terrain definition\nDEFREF\nelement\n\nReference to a definition element.\nDEFSLO\nreal\n\nDefault pipe slope\nDEFSPK\nelement\n\nDefault Reference of SPEC for branch members\nDELANG\nreal\n\nAngle applied to repeat elements\nDELDAT\ndatetime(2)\n\nDelivery Date\nDELDSG\nword\n\nDelivery Designation flag\nDELP\npos\n\nD-position in structure\nDELPE\nreal\n\nEasting of D-Position in STRUC\nDELPN\nreal\n\nNorthing of D-position in STRUC\nDELPU\nreal\n\nUpping of D-position in STRUC\nDELTAE\nreal\n\nEasterly Offset applied to repeat elements\nDELTAN\nreal\n\nNortherly Offset applied to repeat elements\nDELTAU\nreal\n\nVertical Offset applied to repeat elements\nDEMIX\ninteger\n\nIndex of Demote Status Value\nDEMRDY\nlogical\n\nFlag to signify the completion of demolition definition\nDEMVOL\nelement(20)\n\nReferences to Volumes to be demolished referenced laser survey\nDENS\nreal\n\nSpot value of density\nDEPATT\nword(2000)\n\nAttributes that a rule or catalogue parameterised expression is dependent upon\nDEPD\nstring(250)\nword\nDefault value of local design property\nDEPL\nword(100)\n\nList of local design properties\nDEPR\nstring(250)\nword\nLocal design property value\nDEPREF\nelement(500)\n\nList of elements connected to branch tail\nDEPTH\nreal\n\nDepth\nDESC\nstring(120)\n\nDescription of the element\nDESCAL\nstring(256)\n\nDescaling\nDESELE\nelement\n\nReference to Design Object\nDESELM\nelement(50)\n\nReferences to Design Elements\nDESGEO\nelement(5000)\n\nDesign geometrical dependencies\nDESLNK\nelement(20)\n\nConnectivity Design Model Link\nDESMOD\ninteger\n\nDesign Mode\nDESP\nreal(100)\n\nDesign parameters\nDESREF\nelement(10)\n\nDesign reference\nDESSTR\nelement\n\nDesign Structure Reference\nDEST\nstring(26)\n\nDestination\nDESXCL\nlogical\n\nDesign Outfitting excluded Geometry\nDETA\nlogical\n\nDetail flag\nDETR\nelement\n\nDetailing text reference\nDETYPE\ninteger\n\nType of Element In Detailing Node Creation\nDEXREF\nelement\n\nExternal element reference\nDFBRADIUS\nreal\nelement\nDefault bend radius\nDFFL\nreal(6)\n\nDisplacement force flexibility\nDFHOME\nelement\nelement, elemtype\nGet default home element\nDFLA\nstring\n\nRadial dimension type flag\nDFLF\nreal(3)\n\nTranslational spring values\nDFLRCO\nstring(120)\n\nDefault Floor Code\nDFLRHE\nreal\n\nDefault Floor Height\nDFLRTY\nstring(120)\n\nDefault Floor Type\nDFLT\nstring(500)\n\nDefault value for the attribute\nDFLTA\nstring(1000)\n\nDefaults for Type 1 annotation - special attribute for use by ADP\nDFLTB\nstring(1000)\n\nDefaults for Type 2 annotation - special attribute for use by ADP\nDFLTC\nstring(1000)\n\nDefaults for Type 3 annotation - special attribute for use by ADP\nDFLTD\nstring(1000)\n\nDefaults for Type 4 annotation - special attribute for use by ADP\nDFNM\nstring(120)\n\nDocument filename\nDFON\ninteger\n\nDimension text font\nDFONTN\nstring(80)\n\nDimension text font name\nDFUN\nelement\n\nDefault unit\nDGABMA\nreal\n\nHelper Line Distance Start\nDGABME\nreal\n\nHelper Line Distance End\nDGABPA\nreal\n\nDetailing Dimensioning Start Distance\nDGABPE\nreal\n\nDetailing Dimensioning End Distance\nDGABRE\ninteger\n\nDetailing Graphic Measure Line Absolute relativ flag\nDGACCU\ninteger\n\nDetailing Graphic Units Accuracy\nDGADDM\nlogical\n\nDetailing Graphic Additional Measure\nDGADDT\nlogical(3)\n\nDetailing Graphic Additional Measure Type Options\nDGALPO\nstring(32)\n\nDeatiling Graphics Arc Length Postfix\nDGALPR\nstring(32)\n\nDeatiling Graphics Arc Length Prefix\nDGALTI\nstring(32)\n\nDeatiling Graphics Arc Length Title\nDGANCH\ninteger\n\nDetailing Graphic Anchor Point Option\nDGANPT\nreal(2)\n\nDetailing Graphic Anchor Point Dx / Dy\nDGARLT\ninteger\n\nDetailing Graphic Arc Length Dimension type\nDGBAST\nreal\n\nTriangle Base Line\nDGBOLD\nlogical\n\nDetailing Graphic Text Attribute Bold\nDGCENT\nlogical\n\nDetailing Graphic Flag Text centred\nDGCPOP\ninteger\n\nDetailing Graphics Arc Length Center Point Option\nDGCRAD\nreal\n\nDetailing Graphic Circle Radius\nDGCRST\ninteger\n\nDetailing Graphic Polyline Attribute Creation sub type\nDGCRTY\ninteger\n\nDetailing Graphic Attribute Creation Type\nDGDARK\ninteger\n\nDetailing Graphic Display Criteria\nDGDBEA\nreal\n\nDetailing Graphic Polyline Attribute Drawback end angle\nDGDBED\nreal\n\nDrawback End Diameter\nDGDBEL\nreal\n\nDetailing Graphic Polyline Attribute Drawback end length\nDGDBET\ninteger\n\nDetailing Graphic Symbol Attribute Drawback end type\nDGDBGN\ninteger\n\nDetailing Graphic Group number\nDGDBSA\nreal\n\nDetailing Graphic Polyline Attribute Drawback start angle\nDGDBSD\nreal\n\nDrawback Start Diameter\nDGDBSL\nreal\n\nDetailing Graphic Polyline Attribute Drawback start length\nDGDBST\ninteger\n\nDetailing Graphic Symbol Attribute Drawback start type\nDGDISL\nreal\n\nDetailing Graphic Distance to Dimension Line (longitudinal)\nDGDIST\nreal\n\nDetailing Graphic Distance to Dimension Line\nDGDLOL\nreal\n\nDetailing Graphic Distance Line Overlength\nDGDLPO\ninteger\n\nDetailing Graphic Radius Dimension Position on Dimension Line\nDGDLTR\nelement\n\nReference to DGDLT Element\nDGDLTX\nreal\n\nDetailing Graphic Polyline Attribute Delta X\nDGDLTY\nreal\n\nDetailing Graphic Polyline Attribute Delta Y\nDGDOLF\nreal\n\nDetailing Graphic Dimension Line Overlength (Front)\nDGDOLR\nreal\n\nDetailing Graphic Dimension Line Overlength (Rear)\nDGDTDP\nreal\n\nDetailing Graphic Elevation Attribute Distance to dimension point\nDGDTES\nreal\n\nDetailing Graphic Elevation Attribute Distance to elevation symbol\nDGEBPA\nlogical\n\nDetailing Graphic Flag Parallel Planes Only\nDGELVT\nreal\n\nElevation Value\nDGEXB\nreal\n\nDetailing Graphic Distance to extension line begin\nDGEXE\nreal\n\nDetailing Graphic Distance to extension line end\nDGEXET\ninteger\n\nDetailing Graphic Polyline Attribute Type of execution\nDGFANG\ninteger\n\nFill Angle Index\nDGFCOL\ninteger\n\nDetailing Graphic Fill Color\nDGFDIS\ninteger\n\nFill Distance Index\nDGFILL\ninteger\n\nDetailing Graphic Fill flag\nDGFLTV\ninteger\n\nDetailing Graphic Line Pattern Number\nDGFONT\ninteger\n\nDetailing Graphic Font Number\nDGFORM\ninteger\n\nDetailing Graphic Value Format\nDGFPAD\nreal\n\nPattern Repeat Factor\nDGFPAN\nreal\n\nFill Pattern Angle\nDGFPFA\nreal\n\nFill Pattern Factor\nDGFPTY\ninteger\n\nPattern Type\nDGFRME\ninteger\n\nDetailing Graphic Text frame\nDGFSHA\nreal\n\nDetailing Graphic Shading Opacity\nDGGAD\nreal\n\nDetailing Graphic global angle direction\nDGGONP\nstring(32)\n\nDeatiling Graphics Gon Postfix\nDGHASL\nlogical\n\nDetailing Graphic Elevation Attribute Has second line\nDGHGTH\ninteger\n\nDetailing Graphic Text Height\nDGHLDI\nreal\n\nDetailing Graphic Distance to Help Line\nDGHLLE\nreal\n\nDetailing Graphic Symbol Attribute Helpline Length\nDGHLLO\ninteger\n\nDetailing Graphic Help Line Length Option\nDGHLLV\nreal\n\nDetailing Graphic Help Line Length\nDGHLOL\nreal\n\nDetailing Graphic Help Line Overlength\nDGHLPO\ninteger\n\nDetailing Graphic Radius Dimension Position on Help Line\nDGHWR\ninteger\n\nDetailing Graphic Text Height-to-Width ratio\nDGISCL\nlogical\n\nDetailing Graphic Symbol Attribute Is Closed\nDGISEA\ninteger\n\nAutomatic Placement\nDGITAL\nlogical\n\nDetailing Graphic Text Attribute Italics\nDGJOIN\nelement\n\nDetailing parent element reference\nDGJOIS\nelement\n\nDetailing child element reference\nDGLAYN\ninteger\n\nDetailing Graphic Layer Number\nDGLCLO\ninteger\n\nClose Polyline\nDGLDAN\nreal\n\nDetailing Graphic Leader Angle\nDGLDFA\nreal\n\nDetailing Graphic Elevation Attribute Factor for line distance\nDGLDLE\nreal\n\nDetailing Graphic Leader Length\nDGLDOP\ninteger\n\nDetailing Graphics Leader Line Option\nDGLDTY\ninteger\n\nDetailing Graphic Leader Type\nDGLEN\nreal\n\nDetailing Graphic Polyline Attribute Length\nDGLFIL\ninteger\n\nFill Polyline\nDGLLEN\ninteger(3)\n\nText Line Lengths\nDGLLIN\ninteger\n\nDetailing Graphic Multi-line Text Length\nDGLLTY\ninteger\n\nDetailing Graphic Elevation Attribute Type of leader line values\nDGLPFL\nreal\n\nDetailing Graphic Line pitch first line\nDGLPIA\nreal\n\nDetailing Graphic Line pitch absolute\nDGLSPA\nreal\n\nLine Spacing\nDGLTA\nreal\n\nDetailing Graphic Line termination angle\nDGLTIV\ninteger\n\nDetailing Graphic Line Type invisible\nDGLTL\nreal\n\nDetailing Graphic Line termination length\nDGLTR\nelement\n\nReference to DGLTYP Element\nDGLTSB\ninteger\n\nDetailing Graphic Line termination begin\nDGLTSE\ninteger\n\nDetailing Graphic Line termination end\nDGLTVI\ninteger\n\nDetailing Graphic Visible Line Type number\nDGLVSD\ninteger\n\nLevel Symbol Docking\nDGLVST\ninteger\n\nLevel Symbol Type\nDGMALI\nlogical\n\nDetailing Graphic mark line flag\nDGMATT\ninteger\n\nDetailing Graphic Measure Line Text type\nDGMBAS\nreal(2)\n\nDetailing Dimensioning Base Point\nDGMBEG\nreal(2)\n\nDetailing Dimensioning Origin\nDGMDIS\nreal\n\nDetailing Graphic Distance to Dimension Point\nDGMFMT\ninteger\n\nDetailing Graphic Value Formatting Option\nDGMKDX\nreal\n\nDelta X\nDGMKDY\nreal\n\nDelta Y\nDGMLAT\ninteger\n\nDetailing Graphic Angle Measure Line type\nDGMLEG\nreal(2)\n\nDetailing Dimensioning Leg End Point\nDGMLL\nreal\n\nDetailing Graphic Marker Line Length\nDGMODE\ninteger\n\nDetailing Graphic Polyline Attribute Mode\nDGMORA\nreal(2)\n\nDetailing Dimensioning Start Orientation\nDGMORB\nreal(2)\n\nDetailing Dimensioning End Orientation\nDGMPTD\nreal\n\nDetailing Graphic Minimum Point Distance\nDGMTRL\nreal\n\nDetailing Graphic Triangle Measure Line length\nDGMTRT\ninteger\n\nDetailing Graphic Triangle Measure Line type\nDGMTXT\nstring(80)\n\nDeatiling Graphics Measure Option Text\nDGMTYP\ninteger\n\nDetailing Graphic Angle Measure Type\nDGNINV\ninteger\n\nDetailing Graphic Number of invisible characters\nDGNLIN\ninteger\n\nNumber of Lines\nDGNOSI\ninteger\n\nDetailing Graphic Symbol Attribute Number of sides\nDGOLIN\ninteger\n\nNumber of Lines above Marker\nDGONEC\nstring(100)\n\nDetailing Graphic Symbol Attribute Text 1 Content\nDGONES\nlogical\n\nDetailing Graphic Symbol Attribute Text 1 selected\nDGORAN\nreal\n\nOrientation Angle\nDGORIE\ninteger\n\nDetailing Graphic Text Orientation\nDGORTY\ninteger\n\nDetailing Graphic Radius Dimension Orientation Type\nDGPAAN\nreal\n\nPattern Angle\nDGPACK\ninteger\n\nDetailing Graphic Packed Word\nDGPATT\ninteger\n\nDetailing Graphic Line Pattern repeat factor\nDGPDDR\nelement(100)\n\nReference to DGPDD Element\nDGPEN\ninteger\n\nDetailing Graphic Dimension Pen\nDGPICK\ninteger\n\nDetailing Graphic Pick Element\nDGPIV\ninteger\n\nDetailing Graphic Pen invisible\nDGPTYP\ninteger\n\nDetailing Graphic Polyline Attribute Polyline Type\nDGPVI\ninteger\n\nDetailing Graphic Pen visible\nDGPXY\nreal(200)\n\nDetailing Graphic 2D Points\nDGPXYZ\nreal(300)\n\nDetailing Graphic 3D Points\nDGRADI\nreal(32)\n\nList of radius\nDGRDP\ninteger\n\nDetailing Graphic Radius dimension position\nDGRDT\ninteger\n\nDetailing Graphic Radius dimension type\nDGREPR\ninteger\n\nDetailing Graphic Symbol Attribute Representation Rule\nDGSCAL\nreal\n\nScaling Factor\nDGSEGT\ninteger\n\nDetailing Graphic Segment Type\nDGSHAD\ninteger\n\nShading\nDGSIDI\nreal\n\nDetailing Graphic Polyline Attribute Side displacement\nDGSLBA\nreal\n\nDetailing Graphic Slope Base Value\nDGSLCO\nstring(32)\n\nDetailing Graphic Elevation Attribute Content of second line\nDGSMH\nreal\n\nDetailing Graphic Sm_Sysm height\nDGSMW\nreal\n\nDetailing Graphic Sm_Sysm width\nDGTALI\ninteger\n\nDetailing Graphic text alignment\nDGTANG\nreal\n\nDetailing Graphic text angle\nDGTAR\nelement\n\nReference to DGTXAT Element\nDGTARC\ninteger\n\nDetailing Graphic Arc Attribute Type of arc\nDGTATB\ninteger\n\nDetailing Graphic Text Attribute\nDGTCOL\ninteger\n\nDetailing Graphic Text Color\nDGTPLP\ninteger\n\nText Position on Level Point\nDGTPOS\ninteger\n\nDetailing Graphic Text position\nDGTRDY\nreal\n\nDetailing Graphic Slope Triangle DY\nDGTTOM\ninteger\n\nDetailing Graphic text position related to mark out point\nDGTWOC\nstring(100)\n\nProduction Phase\nDGTWOS\nlogical\n\nDetailing Graphic Symbol Attribute Text 2 selected\nDGTXAD\ninteger\n\nDetailing Graphic Symbol Attribute Text Adjustment\nDGTXAN\ninteger\n\nDetailing Graphic Text Anchor\nDGTXB\nreal\n\nDetailing Graphic Distance to text begin\nDGTXE\nreal\n\nDetailing Graphic Distance to text end\nDGTXLI\ninteger\n\nDetailing Graphic Flag for the lift of the last decimal number\nDGTXRF\nelement(100)\n\nReference to DTTXTS Element\nDGTXST\ninteger\n\nDetailing Graphic Text Attribute style\nDGTXT\nstring(80)\n\nDisplay Text\nDGTXTL\nstringarray(20)\n\nDetailing Graphics Text\nDGTYPE\ninteger\n\nDetailing Graphic Type\nDGUNIT\ninteger\n\nDetailing Graphics Units system\nDGUSOF\nreal\n\nDetailing Graphic underscore offset\nDGVIEW\ninteger\n\nDetailing Graphic View Number\nDGWASI\nreal\n\nWave Size\nDGWCIR\ninteger\n\nGirth Weld Flag\nDGWFLG\ninteger\n\nShop Weld Flag\nDGWFRM\nlogical\n\nDetailing Graphic Symbol Attribute Draw with frame\nDGWNTX\ninteger\n\nNumber of Weld Spec Texts\nDGWNUM\ninteger\n\nNumber of Waves\nDGWSCA\nreal\n\nZ3 Window Scale\nDGWSLS\ninteger\n\nDetailing Graphic Welding Symbol Left side flag\nDGWSOS\ninteger\n\nDetailing Graphic Welding Symbol Other side flag\nDGWSSN\ninteger\n\nDetailing Graphic Welding Symbol Number\nDGZART\ninteger\n\nDetailing Graphic Drawing Type\nDHTEST\ninteger(500)\n\nTest locator expression\nDHTEXT\ninteger(500)\n\nDefault home identifier expression\nDIAGXPOS\nreal\n\nX position of the symbol on Visio drawing in mm\nDIAGYPOS\nreal\n\nY position of the symbol on Visio drawing in mm\nDIAM\nreal\n\nDiameter\nDIAREF\nelement(500)\n\nDiagram reference array for schematic elements\nDICMID\ninteger(100)\n\nPredefined instance component identities\nDIME\nlogical\n\nDRAFT user defined symbol dimension flag\nDIMPAT\nstring(1024)\n\nImported attribute\nDIMPOS\npos\n\nDerived 3D dimension position\nDIMTXT\nstring(40)\n\nDimensions text\nDINTER\nstring(257)\n\nDefault Interference class\nDINTHK\nreal\n\nDefault insulation thickness\nDIR\ndir\n\nDirection\nDIRATT\nstring(120)\n\nName of attribute (or pseudo) to be used to set direction for automatic label placement\nDIRCOD\ninteger\n\nDirection Coding\nDIREV\ndir\n\nDirection evaluation\nDIRMOI\ninteger\n\nAuto labelling direction setting (Horizontal, Vertical, Pline, Attribute)\nDIRX\nreal(3)\n\ngrid limit in x direction\nDIRXP\ninteger(500)\n\nDirection expression\nDIRY\nreal(3)\n\ngrid limit in x direction\nDISCIF\nelement\n\nReference of DISCIPLINE Element\nDISCIS\nelement(50)\n\nAssociated disciplines\nDISP\nreal(3)\n\nTranslation displacements\nDISPNM\nstring(120)\n\nDisplay Name\nDISPNN\nstring(120)\n\nDisplay Name\nDIST\nreal(2)\n\nDistances\nDISTAG\nstring(50)\n\nDisplay tag\nDISTFH\nreal\ninteger\nDistance from head\nDISTFN\nreal\n\nDistance from next point\nDISTFP\nreal\n\nDistance from previous point\nDISTM\nreal(2)\n\nDistances to M1 and M2 curves\nDKEY\nword\n\nData Key\nDLCNMINT\ninteger\n\nDimension line continuous mode (Default, ByVStyle, Off, On)\nDLCNTMODE\nstring(20)\n\nDimension line continuous mode (as text)\nDLCOLO\ninteger\n\nDimension line colour\nDLCONU\ninteger\n\nDimension line colour number\nDLEV\ninteger\n\nDrawing level\nDLGDAT\nInt array\n\nDelegation date\nDLGOF\ntext\n\nDelegate of\nDLFG\nstring\n\nLinear/Angular dimension line flag\nDLIM\nreal(6)\n\nDisplacement limit\nDLIST\nword(2000)\n\nList of all possible dist att types\nDLNRGB\ninteger(4)\n\nRGB dimension line colour\nDLNRGP\ninteger(4)\n\nRGB dimension line colour physical\nDLPN\ninteger\n\nDimension line pen\nDLSTREF\nelement\n\nDimension linestyle Reference\nDLSTYL\ninteger\n\nDimension linestyle\nDMFA\nelement(2)\n\nISODRAFT Reference Dimension attribute\nDMFL\nreal(9)\n\nDisplacement moment flexibility\nDMSP\nreal\n\nLower limit to spacing between parallel dimensions\nDMSPTX\nstring(80)\n\nDimension spacing text\nDMSTRF\nelement\n\nDimension style reference\nDMTX\nstring(1000)\n\nDimension text\nDMTY\nword(2)\n\nISODRAFT Reference Dimension attribute\nDNAME\nstring(50)\n\nDisplay Name\nDNOTCP\nelement\n\nDraw Note Current Command Line Point\nDNST\nreal\n\nDensity\nDOCCHG\nelement(2147483647)\n\nReference to changed related documents\nDOCNUM\nstring(40)\n\nDocument Number\nDOCREF\nelement\n\nDocument reference\nDOCXRF\nelement(500)\n\nReturn reference from Design element to DOCITM element\nDOFF\nreal\n\nDimension line offset\nDOFIL\nstring(73)\n\nDrawing Object filename\nDOUHOL\nlogical\n\nDoubling hole\nDOUPGR\nlogical\n\nTrue if element is recommended to be upgraded in current db\nDPBO\nreal\ninteger\nDesign point bore\nDPCO\nword\ninteger\nDesign point connection type\nDPCOU\ninteger\n\nNumber of valid design points\nDPDI\ndir\ninteger\nDesign point direction\nDPDIST\nreal\n\nDraw proportional distance\nDPFN\nstring(1024)\n\nISODRAFT dynamic detail plotfile name\nDPGR\nreal\ninteger\nDesign Point Gradient\nDPGRID\ninteger\n\nISODRAFT dynamic detail grid reference attribute\nDPKEY\nword\n\nDraft derived Pline identifier key\nDPLS\ninteger(200)\n\nList of valid design points\nDPNAME\nstring(120)\n\nDisplay Name\nDPOFF\nreal\n\nDimension point offset\nDPOINX\nstring(480)\n\nDesign point information\nDPOS\npos\n\nDimension line/arc position\nDPPS\npos\ninteger\nDesign point position\nDPREMA\nreal\n\nDesign pres. max\nDPREMI\nreal\n\nDesign pres. min\nDPRO\nstring(1000)\n\nParameterised Property Expression (Default)\nDPSF\nelement\n\nDesign PPointset reference\nDPVI\ninteger(200)\n\nList of visible design points\nDRAD\nstring(1000)\n\nRadial offset\nDRAFTM\nstring(256)\n\nDraftsman\nDRAWNO\nstring(26)\n\nDrawing number\nDREVAY\nelement(50)\n\nDRWG revisions array\nDRFILE\nstring(73)\n\nDrawing File Name\nDRFLOINT\ninteger\n\nDraw Flow (ByVStyle, None, Forward, Back)\nDRFLOW\nstring(20)\n\nDraw Flow (as text)\nDRFNUM\ninteger(21)\n\nDrawing File Numbers\nDRFTYP\ninteger(21)\n\nDrawing File Types\nDRGP\ninteger\n\nDrawing priority (used to determine how to draw SCTN)\nDRMXTL\ninteger\n\nDraft general max text length\nDRNE\ndir\n\nPlane normal at end of SCTN/GENSEC\nDRNS\ndir\n\nPlane normal at start of SCTN/GENSEC\nDRPS\npos\n\nDerived position for steelwork\nDRRF\nelement\n\nOld spooler drawing reference\nDRSSRE\nelement\n\nDraft Symbol set reference\nDRSTYP\nstring(120)\n\nDrawing subtype\nDRSTYTABLE\nstring(120)\n\nDrawing subtype table\nDRTITL\nstring(1000)\n\nDrawing title\nDRTMPR\nelement\n\nDraft template reference\nDRTYPE\nstring(120)\n\nDrawing type\nDRTYPTABLE\nstring(120)\n\nDrawing type Table\nDRUMLN\nreal\n\nDrum length\nDRWGN\nstring(1000)\n\nDrawing number\nDSCO\nstring(120)\n\nDesign code\nDSESS\nstring(640)\ninteger\nDate of specified session\nDSET\nlogical(3)\n\nDisplacement limits set flag - ignore values if FALSE\nDSGNTN\nstring\n\nDesignation\nDSHANG\nreal\n\nDraft absolute sheet angle\nDSHPOS\npos\n\nDraft sheet position derived from 3d\nDSIAST\nelement(500)\n\nDatasheet Instance assigned tags reference array for Datasheet Instance\nDSIFIL\nstring(2000)\n\nDatasheet Instance filename\nDSNO\ninteger\n\nDatasheet number\nDSSUBT\nstring(2000)\n\nDatasheet sub title\nDSTAPN\nstring(120)\n\nDatasheet Additional Page Name\nDSTAPT\nstring(120)\n\nDatasheet Additional Page Type\nDSTITL\nstring(2000)\n\nDatasheet title\nDSTNCE\nreal\n\nDistance\nDSTREF\nelement\n\nDatasheet Template reference for Datasheet Instance\nDSTY\nstring\n\nRadial dimension style flag\nDSTYPE\ninteger\n\nDatasheet type\nDSUPCA\nlogical\n\nDrawing Engine suppress caching\nDSXLNK\nelement(200)\n\nConnectivity Extended Design Model Link\nDTADDR\nelement\n\nDetailing Job Address\nDTADDT\nstring(80)\n\nAdditional Text Data\nDTADEG\nreal\n\nDimension Text Angle Degrees\nDTADGP\nreal\n\nDimension Text Angle Degrees\nDTADHO\ninteger\n\nBolting: Additional hole type\nDTADPU\ninteger\n\nBolting Centre Punch Type\nDTAN\nstring\n\nDimension text angle flag\nDTANFL\nreal\n\nDetailing Fabrication Item / Angle of cut - Flange/Left\nDTANFR\nreal\n\nDetailing Fabrication Item / Angle of cut - Flange/Right\nDTANGZ\nreal\n\nAngle to Zero Line\nDTANSA\nstring\n\nDimension text angle flag style angular DTANSA\nDTANSL\nstring\n\nDimension text angle flag style linear DTANSL\nDTANSR\nstring\n\nDimension text angle flag style radiant DTANSR\nDTANWL\nreal\n\nDetailing Fabrication Item / Angle of cut - Web/Left\nDTANWR\nreal\n\nDetailing Fabrication Item / Angle of cut - Web/Right\nDTAOBV\ninteger\n\nNumber of bolting vectors\nDTAREA\nreal\n\nArea\nDTAUTW\ninteger\n\nClamping Length Balancing Mode\nDTBCKD\ndatetime(2)\n\nDetailing Job Backup Date\nDTBCOA\nstring(80)\n\nDetailing Base Coating\nDTBDIA\nreal\n\nDetailing Element Border Diameter\nDTBDR\nelement\n\nReference to a bolt definition element\nDTBNAM\nstring(32)\n\nDetailing Model Bolt Name\nDTBNDB\nstring(32)\n\nDetailing Model Bolt Name for Database\nDTBNDR\nstring(32)\n\nDetailing Model Bolt Name for Drawings\nDTBREV\nelement\n\nReference to Revision\nDTBSET\ninteger(10)\n\nBolt Set Composition\nDTBSR\nelement\n\nReference to a bolt set definition element\nDTCATR\nstring(10)\n\nBolt Set Component Catalogue Numbers\nDTCDAT\ndatetime(2)\n\nDetailing Drawing Creation Date\nDTCEXL\nreal\n\nLength of the extrusion cut length\nDTCH\nreal\n\nDimension text character height\nDTCHTX\nstring(80)\n\nDim text char height text\nDTCITY\nstring(80)\n\nDetailing Address City\nDTCKEY\ninteger\n\nBocad Detailing Comment Key\nDTCLAS\ninteger\n\nBocad Detailing Element Class\nDTCLHO\nreal\n\nBolt Hole Clearance\nDTCLIP\ninteger\n\nClamping Length Calculation Mode\nDTCLMA\nreal\n\nBolt Clamping Length (maximum)\nDTCLMI\nreal\n\nBolt Clamping Length (minimum)\nDTCLML\nreal\n\nBolt Clamping Length (calculated)\nDTCLWA\nreal\n\nBolting Washer Clearance\nDTCNST\nelement\n\nDetailing Zone/Phase Designer\nDTCNTC\nelement\n\nDetailing Job Customer Contact Person\nDTCNTY\nstring(80)\n\nDetailing Address Country\nDTCNUM\ninteger(100)\n\nBocad Detailing Comment Number\nDTCOGC\nreal(3)\n\nCentre of Gravity\nDTCOLA\nstring(80)\n\nPrimary Color\nDTCOLB\nstring(80)\n\nExternal Color\nDTCOLN\nelement\n\nNested Drawing Reference\nDTCOLO\ninteger\n\nDimension text colour\nDTCONU\ninteger\n\nDimension text colour number\nDTCORF\nelement(100)\n\nReference to Bocad Detailing Comment Container\nDTCSAG\nreal\n\nSink Hole Angle\nDTCSDA\nreal\n\nSink Hole Diameter 1\nDTCSDB\nreal\n\nSink Hole Diameter 2\nDTCSDC\nreal\n\nSink Hole Diameter 3\nDTCSHD\nreal\n\nSink Hole Dimension Head\nDTCSIV\nlogical\n\nCountersunk Bolt\nDTCSNU\nreal\n\nSink Hole Dimension Nut\nDTCTLN\nreal\n\nDetailing Item Cut Length\nDTCUST\nelement\n\nDetailing Job Customer\nDTCUTY\ninteger\n\nDetailing Fabrication Item / Type of cut, 0 = no, 1 = standard cuts, 2 = cutouts-notch\nDTDBST\nstring(80)\n\nDetailing Job Database State\nDTDDTE\ndatetime(2)\n\nDetailing Job Delivery Date\nDTDESI\nstring(80)\n\nDesignation\nDTDESR\nelement\n\nReference to Bolt Set Designation Container\nDTDINN\ninteger\n\nDetailing Element DIN Number\nDTDISA\nreal\n\nSection Distance 1\nDTDISB\nreal\n\nSection Distance 2\nDTDLIM\nlogical\n\nBlind Hole Bolt\nDTDMAT\nlogical\n\nClamp Length Calculation Flag\nDTDRST\ninteger\n\nDetailing Drawing Status\nDTDRTY\ninteger\n\nDetailing Drawing Type\nDTDTEN\nstring(80)\n\nDetailing End Date\nDTDTST\nstring(80)\n\nDetailing Start Date\nDTDVIS\nlogical\n\nVisible in base dimetry\nDTEDAT\ninteger(90)\n\nDetailing Model Element Attributes\nDTELEM\nelement\n\nReference to an element modified or created during Macro execution\nDTEMAL\nstring(80)\n\nDetailing Person eMail Address\nDTENVA\nreal\n\nEnveloping Area\nDTER\nstring\n\nDimension terminator code\nDTERID\ninteger\n\nDimension terminator ID\nDTERSA\ninteger\n\nDimension term. code style angular DTERSA\nDTERSL\ninteger\n\nDimension term. code style linear DTERSL\nDTERSR\ninteger\n\nDimension term. code style radiant DTERSR\nDTETYP\ninteger\n\nDetailing Element External Type Code\nDTFCOA\nstring(80)\n\nDetailing Final Coating\nDTFEAG\nelement\n\nReference to a Feature Group/Set\nDTFEAR\nelement\n\nReference to a Feature\nDTFEAS\nelement(100)\n\nReferences to Feature Values\nDTFL\nstring\n\nDimension text radius flag\nDTFLTY\ninteger\n\nBMF Folder Type\nDTFLWB\nreal\n\nDetailing Fabrication Item / Partial cut/cutout - angle Flange/Left/bottom\nDTFLWT\nreal\n\nDetailing Fabrication Item / Partial cut/cutout - angle Flange/Left/top\nDTFLXB\nreal\n\nDetailing Fabrication Item / Partial cut/cutout - x value Flange/Left/bottom\nDTFLXT\nreal\n\nDetailing Fabrication Item / Partial cut/cutout - x value Flange/Left/top\nDTFPHN\nstring(80)\n\nDetailing Person FAX Phone number\nDTFPO\nstring(100)\n\nFinal painting 1\nDTFPT\nstring(100)\n\nFinal painting 2\nDTFRAM\ninteger\n\nDim Text Frame Sides (ByVStyle, ByOwner, Off, All, Combination of Top/Left/Right/Bottom)\nDTFREA\nstring(80)\n\nBocad Detailing Free Attribute 1\nDTFREB\nstring(80)\n\nBocad Detailing Free Attribute 2\nDTFREC\nstring(80)\n\nBocad Detailing Free Attribute 3\nDTFRED\nstring(80)\n\nBocad Detailing Free Attribute 4\nDTFREE\nstring(80)\n\nBocad Detailing Free Attribute 5\nDTFRWB\nreal\n\nDetailing Fabrication Item / Partial cut/cutout - angle Flange/Right/bottom\nDTFRWT\nreal\n\nDetailing Fabrication Item / Partial cut/cutout - angle Flange/Right/top\nDTFRXB\nreal\n\nDetailing Fabrication Item / Partial cut/cutout - x value Flange/Right/bottom\nDTFRXT\nreal\n\nDetailing Fabrication Item / Partial cut/cutout - x value Flange/Right/top\nDTFSIZ\ninteger(2)\n\nDetailing Model Folder Sizes\nDTFTHK\nreal\n\nDetailing Element Flange Thickness\nDTFUNC\ninteger\n\nDetailing Element Function Code\nDTGALV\nstring(80)\n\nDetailing Galvanisation Type\nDTGATT\nreal(10)\n\nDetailing Model Attributes Real part\nDTGCNT\ninteger\n\nDetailing Element Generated Count\nDTGCOG\nreal(3)\n\nGross Centre of Gravity\nDTGEND\ninteger\n\nDetailing Element Generation Date\nDTGID\ninteger\n\nDetailing Model geoemetry ident number\nDTGLEN\ninteger\n\nDetailing Element Generation Length\nDTGNIF\ninteger\n\nBolt Hole Orientation Mode\nDTGRADE\nstring(32)\n\nDetailing Material Grade\nDTGRDS\nelement(99)\n\nReferences to Detailing Job Grid Definitions\nDTGTRI\nreal(12)\n\nDetailing Creation Tripod\nDTGTYP\ninteger\n\nDetailing Element Geometry Type Code\nDTHDHE\nreal\n\nBolt Header Height\nDTHEIG\nreal\n\nDetailing Element Height\nDTHGTH\nreal\n\nHeight\nDTHOTY\ninteger\n\nBolting Hole Type\nDTIDAT\ninteger(120)\n\nDetailing Model Attributes Integer part\nDTINAX\nlogical\n\nSeamline in Axis Direction\nDTIT\nstring(32)\n\nData Title\nDTITYP\ninteger\n\nDetailing Element Internal Type Code\nDTJDSC\nstring(80)\n\nDetailing Job Description\nDTJLOC\nelement\n\nDetailing Job Location\nDTJNUM\nstring(80)\n\nBocad Detailing Job Number / Name\nDTJREV\nstring(80)\n\nDetailing Job Revision\nDTLEAD\nelement\n\nReference to Lead Part\nDTLELE\nelement(5000)\n\nDatal Elements list\nDTLEN\ninteger\n\nDetailing Element Length\nDTLGTH\nreal\n\nDetailing Fabrication Element Length\nDTLH\nreal\n\nDimension text letter height\nDTLHTX\nstring(80)\n\nDimension text letter height text\nDTLLIST\nword(2000)\n\nDatal Attributes List\nDTLNAM\nreal\n\nDetailing Item Length after Marking\nDTLNGE\nreal\n\nDetailing Item generated Length\nDTLPDO\nelement\n\nReference to Original main part\nDTLPDZ\nelement\n\nReferences to Additional Part\nDTLPHN\nstring(80)\n\nDetailing Person Landline Phone number\nDTLTST\ninteger(8192)\n\nDatal Test attribute\nDTMANA\nstring(120)\n\nMacro Name\nDTMAT\nstring(80)\n\nFabrication Material\nDTMDFD\nstring(19)\n\nModified Date/Time\nDTMDST\ndatetime(2)\n\nModification Date\nDTMFKE\ninteger\n\nDetailing Element Manufacturing ID\nDTMFST\ndatetime(2)\n\nManufacturing Status Date\nDTMIND\ninteger\n\nBolt Connection Processing Mode\nDTMKIN\nstring(80)\n\nInitial Mark Number\nDTMKPR\nstring(80)\n\nPrevious Mark Number\nDTMKST\nstring(80)\n\nMarking Status\nDTMKTX\nstring(80)\n\nMark Text\nDTMMDE\ninteger\n\nDetailing Element Marking Status / Mode\nDTMODD\ninteger\n\nDetailing Element Modification Date\nDTMODF\nstring(80)\n\nModfied by\nDTMPAR\nelement\n\nReference to original mirror element\nDTMPHN\nstring(80)\n\nDetailing Person Mobile Phone number\nDTMPMA\nreal\n\nDesign temp. max\nDTMPMI\nreal\n\nDesign temp. min\nDTMTYP\ninteger\n\nM3 Connection Type\nDTNAME\nstring(80)\n\nDetailing Item Name\nDTNBEN\ninteger\n\nDetailing Fabrication Item / Quantity of bends\nDTNCHA\ninteger\n\nDetailing Fabrication Item / Quantity of chamfers\nDTNHOL\ninteger\n\nDetailing Fabrication Item / Quantity of holes\nDTNICO\ninteger\n\nDetailing Fabrication Item / Quantity of inner contours\nDTNMOD\ninteger\n\nDetailing Fabrication Item / Quantity of modification on the geometry. Notches, Cuts, Cutoffs...\nDTNMPO\ninteger\n\nDetailing Fabrication Item / Quantity of marking points\nDTNNOT\ninteger\n\nDetailing Fabrication Item / Quantity of notches\nDTNSEA\ninteger\n\nNumber of Seam Angles\nDTNSEC\ninteger\n\nNumber of Seamline Sections\nDTNSEL\ninteger\n\nDetailing Fabrication Item / Quantity of superelevation\nDTNSHO\ninteger\n\nDetailing Fabrication Item / Quantity of slotted holes\nDTNSWE\ninteger\n\nDetailing Fabrication Item / Quantity of welds, site\nDTNTYP\ninteger\n\nType Of Detailing Node\nDTNUMB\ninteger\n\nDetailing Model Element ident number\nDTNWWE\ninteger\n\nDetailing Fabrication Item / Quantity of welds, workshop\nDTOF\nreal(2)"}
{"Headers": "Attribute E", "Content": "E\nreal\n\nPosition easting\nEASTING\npos\n\nEasting part expressed as a position\nECADAV\nstring(500)\n\nAttribute Driven Symbol - Attribute Value\nECADST\nelement(500)\n\nEngineering Canvas Symbol Templates\nECBSRE\nelement\n\nEngineering canvas backing sheet reference\nECCE\npos\n\nEccentricity (steelwork)\nECCFR\nelement\n\nEngineering canvas connection from\nECCJ\npos\n\nEccentricity of joint (steelwork)\nECCPDR\nelement\n\nEngineering canvas connection point type definition reference\nECCPRE\nelement\n\nEngineering canvas connection point graphics reference\nECCPTR\nelement\n\nEngineering canvas connection point template reference\nECCTO\nelement\n\nEngineering canvas connection to\nECDCTY\ninteger\n\nEngineering Canvas drawing content type\nECDER\nelement(1000)\n\nEngineering canvas draw entity reference\nECDFLR\nelement\n\nEngineering Canvas Default Label reference\nECDNAM\nstring(120)\n\nEngineering Canvas display name\nECGHPA\nreal(3)\n\nEngineering Canvas Grid Horizontal Parameters\nECGHST\nstring(25)\n\nEngineering Canvas Grid Horizontal Start Text\nECGHTA\nlogical\n\nEngineering Canvas Grid Horizontal Text Ascending\nECGHTF\ninteger\n\nEngineering Canvas Grid Horizontal Text Format\nECGOFF\nreal(2)\n\nEngineering Canvas Grid Offset\nECGPOS\nreal(2)\n\nEngineering Canvas Grid 2D Position\nECGREF\nelement\n\nEngineering Canvas Grid Reference\nECGSIZ\nreal(2)\n\nEngineering Canvas Grid Size\nECGTXH\nreal\n\nEngineering Canvas Grid Text Height\nECGTYP\nstring(120)\n\nEngineering Canvas Glyphtype\nECGUAR\ninteger\n\nEngineering Canvas Guard Level\nECGVPA\nreal(3)\n\nEngineering Canvas Grid Vertical Parameters\nECGVST\nstring(25)\n\nEngineering Canvas Grid Vertical Start Text\nECGVTA\nlogical\n\nEngineering Canvas Grid Vertical Text Ascending\nECGVTF\ninteger\n\nEngineering Canvas Grid Vertical Text Format\nECIREF\nelement\n\nEngineering Canvas template index reference\nECLASS\nword(100)\n\nAccess Control Element class\nECLCLR\nstring(120)\n\nEngineering Canvas Line Colour\nECLNKF\nelement\n\nEngineering source item reference\nECLNKT\nelement\n\nEngineering target item reference\nECLOFF\nreal(2)\n\nEngineering Canvas Label Offset\nECLTYP\nstring(120)\n\nEngineering Canvas Linetype\nECMDEF\nlogical\n\nMapping Default flag\nECMTDR\nelement(200)\n\nEngineering Canvas Metadata Reference\nECNUMB\nstring(50)\n\nEngineering Canvas number\nECOPCR\nelement(500)\n\nEngineering Canvas OPC References\nECORSZ\nreal\n\nSize of the earth core\nECPGRP\nstring(120)\n\nEngineering Canvas Palette Group\nECPIREF\nelement\n\nEngineering Canvas palette item reference\nECPREF\nelement(1000)\n\nEngineering Canvas page reference\nECPURP\nstringarray(50)\n\nDrawing Purpose\nECREF\nelement\n\nEngineering Canvas reference\nECRFA\nelement(500)\n\nEquipment connection reference array\nECRMSU\nstringarray(200)\n\nEngineering Canvas Revision Mark Subject\nECSHLL\nlogical\n\nShow Leader Line\nECSHRE\nelement\n\nEngineering canvas sheet reference\nECSREF\nelement\n\nEngineering canvas symbol reference\nECSTD\nstring(120)\n\nEngineering Canvas Standard\nECSTR\nelement\n\nEngineering canvas symbol template reference\nECSTTY\nstring(120)\n\nSymbol template type\nECSTVR\nelement\n\nEngineering canvas symbol template variant reference\nECTARR\nelement(500)\n\nEngineering Canvas Types\nECTCL\nelement(1000)\n\nEngineering table cell link reference\nECTCR\nelement(1000)\n\nEngineering table cell reference\nECTFML\nstring(120)\n\nEngineering canvas text formula\nECTPLO\nlogical\n\nTemplate only flag\nECTREF\nelement\n\nEngineering Canvas Type Reference\nECTREG\nreal(4)\n\nEngineering canvas template region\nEDEREF\nelement\n\nEnd reference\nEDGELE\nreal\n\nEdge Length\nEDGGRD\nlogical\n\nTrue if any edge should be grinded\nEDGLST\nelement(1000)\n\nEdge list\nEDISTA\nreal\n\nVertical Distance of End\nEDOCOR\ninteger\n\nStores Document order values\nEDOCRF\nelement\n\nEngineering Referenced Document\nEDOCRV\nstring(120)\n\nEngineering Document Revision\nEDPUV\npos\n\nEnd point\nEDSREF\nelement\n\nStart reference\nEFAC\nstring(1000)\n\nE-factor\nEFMDM\nstring(240)\n\nEngineering Feed Mapping Dimension\nEFMFR\nstring(2000)\n\nEngineering Feed Mapping From\nEFMFUN\nstring(120)\n\nEngineering Feed Mapping Functional Type\nEFMINC\nlogical\n\nEngineering Feed Mapping Include\nEFMTO\nstring(2000)\n\nEngineering Feed Mapping To\nEFOR\nreal(3)\n\nEnd force vector components\nEIMPED\nreal\n\nEarth impedance\nELCXRF\nelement(500)\n\nReturn reference from CABLE element to ELCONN element\nELDATA\ninteger(8192)\n\ndata\nELDSZ\ninteger\n\nDataSize\nELECRE\nlogical\ninteger\nTrue if created since given session\nELECREC\nlogical\n\nTrue if created since comparison date\nELEDEL\nlogical\ninteger\nTrue if deleted since given session\nELEDELC\nlogical\n\nTrue if deleted since comparison date\nELEGAL\nstring(256)\n\nElectrogalvanise\nELEL\nword(2147483647)\n\nTypes of elements, including UDETs, to which this applies\nELEMOD\nlogical\ninteger\nTrue if modified since given session\nELEMODC\nlogical\n\nTrue if modified since comparison date\nELEPTR\ninteger\n\nElemp\nELESZ\ninteger\n\nSize\nELEVAT\nreal\n\nElevation\nELEVID\nstring(20)\n\nElevation starting index\nELEVLA\nstring(20)\n\nLabel for Elevation grid planes\nELEVV\nlogical\n\nIs Elevation View\nELRATI\nreal\n\nElectrical Rating\nELTYPC\nword\n\nElement type\nELVRSN\ninteger\n\nElement version\nEMOM\nreal(3)\n\nEnd moment components\nENBINF\npos\ninteger\nEnd bend information\nENCODB\nstring\n\nDB Encoding\nENDA\nreal\n\nEnd angle\nENDELE\nreal\n\nEnd Elevation\nENDOFF\nreal\n\nOffset of the end of section\nENDPOINT\ninteger\n\nCable End connection point\nENDPOS\npos\n\nEnd Position\nENDREF\nelement\n\nCable End reference\nENDRFARRAY\nelement(100)\n\nENDATUM reference array\nENGCHG\nlogical\n\nChanged since Issue\nENGDOC\nelement(2147483647)\n\nReference to related documents\nENGLNK\nelement\n\nEngineering Element Link\nENGTYP\nstring(2000)\n\nDatasheet engineering type\nENHOOK\nstring(256)\n\nEnd hook reference\nENSEQU\ninteger\n\nEnd Sequence Position of last work before Macro execution in FCSG list\nENTYCD\ninteger\n\nType code for end of start\nENVBMA\nreal(3)\n\nSpecified project envelope box max extent\nENVBMI\nreal(3)\n\nSpecified project envelope box min extent\nEPARAM\nreal(6)\n\nEvaluated parameters\nEPKDI\nreal\n\nProportional distance of end point along Pline\nEPOSTO\nreal\n\nEnd post tangent offset\nEPREPC\nlogical\n\nTrue if Varying bevel\nEPREPV\nlogical\n\nTrue if V-bevel\nEPREPX\nlogical\n\nTrue if X-bevel\nEPREPY\nlogical\n\nTrue if Y-bevel\nEQCLASS\nstring(50)\n\nEquipment class\nEQTYPE\nstring(100)\n\nEquipment class\nEREACT\nreal\n\nEarth reactance\nEREC\ninteger\n\nErection class\nEREL\ninteger\n\nEnd releases (packed)\nERESIS\nreal\n\nEarth resistance\nETEX\nstring(1000)\n\nExample text\nETMTTL\nstring(120)\n\nEngineering 3D Model Title\nEVITXP\nstring(1500)\n\nEvaluated intelligent text for projection line\nEVITXT\nstring(1500)\n\nEvaluated intelligent text\nEVOL\nreal(6)\n\nEnclosing box volume in given coordinates\nEXBTEX\nstring(1500)\n\nExpanded annotation text\nEXCESS\nreal\n\nExcess\nEXCLCH\nstring(50)\n\nExclusion Character List\nEXCLEL\nlogical\n\nLogically deleted from the project\nEXCLEN\nreal(3)\n\nLength of excess intervals\nEXCLFR\nlogical\n\nTrue if element claimed from this extract. Only True for Primary elements\nEXCLFT\nreal\n\nExcess on left side of seam\nEXCLHI\nelement(5000)\n\nPrimary elements in descendant hierarchy claimed to this extract(includes this element)\nEXCLPA\nlogical\n\nTrue if element claimed to Parent extract. Only True for Primary elements\nEXCLTO\nlogical\n\nTrue if element claimed to this extract. Only True for Primary elements\nEXCNUM\ninteger(3)\n\nNumber of excess intervals\nEXCPRM\nelement(8191)\n\nPrimary locations of extract children\nEXCRGT\nreal\n\nExcess on right side of seam\nEXCTLF\ninteger\n\nExcess type on left side of seam\nEXCTRG\ninteger\n\nExcess type on right side of seam\nEXDIST\nreal\n\nExit Top Distance\nEXDMTX\nstring(1500)\n\nExpanded dimension text\nEXECAFTER\nstring(512)\n\nExec file after DB propagation\nEXECBEFORE\nstring(512)\n\nExec file before DB propagation\nEXEXTE\nreal\n\nExit Extension\nEXEXTN\nreal\n\nExit Extension\nEXFI\ninteger\n\nExtract file number\nEXHCNC\nelement(5000)\n\nAs EXTCNC, but repeat test for all descendants\nEXHCNN\nelement(5000)\n\nAs EXTCNN, but repeat test for all descendants\nEXHCON\nelement(5000)\n\nAs EXTCON, but repeat test for all descendants\nEXHEIG\nreal\n\nExit Height\nEXHRCN\nelement(5000)\n\nAs EXRCN, but repeat test for all descendants\nEXHRCO\nelement(5000)\n\nAs EXTRCO, but repeat test for all descendants\nEXMOC\nlogical\n\nAs EXMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXMOD\nlogical\n\nTrue if element modified in this extract\nEXNCLH\nelement(5000)\n\nPrimary elements in descendant hierarchy not claimed to this extract\nEXOPRM\nelement\n\nPrimary location of extract owner\nEXPA\nreal\n\nSpot value of expansion coefficient\nEXPIRY\nstring(50)\n\nProtected DB Expiry date\nEXPLTX\nstring(1500)\n\nExpanded projection line text\nEXPMOC\nlogical\n\nAs EXPMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOD\nlogical\n\nTrue if primary and element or non-primary descendants have been modified in this extract\nEXPRESSION\nstring(1000)\n\nPML or XPath Expression to be executed\nEXPTYPE\nstring(15)\n\nExpression syntax. Either PML or XPath\nEXTALS\nelement(8191)\n\nExtract ancestors\nEXTANT\nreal\n\nTolerance angle\nEXTBOA\nreal\n\nExtrusion branch OD A\nEXTBOB\nreal\n\nExtrusion branch OD B\nEXTBOD\nreal\n\nExtrusion branch outside diameter\nEXTBOX\nreal(6)\n\nExtended block box\nEXTCLS\nelement(8191)\n\nExtract children\nEXTCNC\nelement(5000)\n\nAs EXTCON but excluding non modified elements\nEXTCNN\nelement(5000)\n\nAs EXTCON but excluding modified elements\nEXTCON\nelement(5000)\n\nPrimary elements connected/disconnected from element or non primary descendants in extract\nEXTDES\nelement(8191)\n\nExtract descendants\nEXTDIR\nstring(10)\n\nDirection of ladder exit\nEXTEAA\nreal\n\nMinimum distance from an extrusion to the next extrusion\nEXTEAB\nreal\n\nMinimum distance from centre of an extrusion to next bend\nEXTEAH\nreal\n\nExtrusion collar height (from the top of tube to the end of collar)\nEXTEAK\nreal\n\nMinimum distance from an extrusion to the pipe end\nEXTEHE\nreal\n\nHeight of extrusion machine\nEXTFAM\nelement(8191)\n\nExtract family\nEXTHI\ninteger\n\nLocation extract number range, high limit\nEXTLO\ninteger\n\nLocation extract number range, low limit\nEXTMAS\nelement\n\nExtract master\nEXTMRE\nelement\n\nExtrusion machine reference.\nEXTNO\ninteger\n\nExtract number\nEXTNSN\nreal\n\nExtension\nEXTOFF\nreal\n\nExit Offset\nEXTOWN\nelement\n\nExtract owner\nEXTRC\nstring(120)\n\nName of extract claiming element\nEXTRCN\nelement(5000)\n\nAs EXTCNN, but applied recursively to each connection\nEXTRCO\nelement(5000)\n\nAs EXTCON, but applied recursively to each connection\nEXTREF\nelement\n\nReferences to exit level\nEXTVOLUME\nreal\n\nVolume for material\nEXWIDTH\nreal\n\nExit Width\nEZDI\nreal\n\nEnd load point in section\n\nAttribute Name\nData Type\nQualifier\nDescription\nE\nreal\nPosition easting\nEASTING\npos\nEasting part expressed as a position\nECADAV\nstring(500)\nAttribute Driven Symbol - Attribute Value\nECADST\nelement(500)\nEngineering Canvas Symbol Templates\nECBSRE\nelement\nEngineering canvas backing sheet reference\nECCE\npos\nEccentricity (steelwork)\nECCFR\nelement\nEngineering canvas connection from\nECCJ\npos\nEccentricity of joint (steelwork)\nECCPDR\nelement\nEngineering canvas connection point type definition reference\nECCPRE\nelement\nEngineering canvas connection point graphics reference\nECCPTR\nelement\nEngineering canvas connection point template reference\nECCTO\nelement\nEngineering canvas connection to\nECDCTY\ninteger\nEngineering Canvas drawing content type\nECDER\nelement(1000)\nEngineering canvas draw entity reference\nECDFLR\nelement\nEngineering Canvas Default Label reference\nECDNAM\nstring(120)\nEngineering Canvas display name\nECGHPA\nreal(3)\nEngineering Canvas Grid Horizontal Parameters\nECGHST\nstring(25)\nEngineering Canvas Grid Horizontal Start Text\nECGHTA\nlogical\nEngineering Canvas Grid Horizontal Text Ascending\nECGHTF\ninteger\nEngineering Canvas Grid Horizontal Text Format\nECGOFF\nreal(2)\nEngineering Canvas Grid Offset\nECGPOS\nreal(2)\nEngineering Canvas Grid 2D Position\nECGREF\nelement\nEngineering Canvas Grid Reference\nECGSIZ\nreal(2)\nEngineering Canvas Grid Size\nECGTXH\nreal\nEngineering Canvas Grid Text Height\nECGTYP\nstring(120)\nEngineering Canvas Glyphtype\nECGUAR\ninteger\nEngineering Canvas Guard Level\nECGVPA\nreal(3)\nEngineering Canvas Grid Vertical Parameters\nECGVST\nstring(25)\nEngineering Canvas Grid Vertical Start Text\nECGVTA\nlogical\nEngineering Canvas Grid Vertical Text Ascending\nECGVTF\ninteger\nEngineering Canvas Grid Vertical Text Format\nECIREF\nelement\nEngineering Canvas template index reference\nECLASS\nword(100)\nAccess Control Element class\nECLCLR\nstring(120)\nEngineering Canvas Line Colour\nECLNKF\nelement\nEngineering source item reference\nECLNKT\nelement\nEngineering target item reference\nECLOFF\nreal(2)\nEngineering Canvas Label Offset\nECLTYP\nstring(120)\nEngineering Canvas Linetype\nECMDEF\nlogical\nMapping Default flag\nECMTDR\nelement(200)\nEngineering Canvas Metadata Reference\nECNUMB\nstring(50)\nEngineering Canvas number\nECOPCR\nelement(500)\nEngineering Canvas OPC References\nECORSZ\nreal\nSize of the earth core\nECPGRP\nstring(120)\nEngineering Canvas Palette Group\nECPIREF\nelement\nEngineering Canvas palette item reference\nECPREF\nelement(1000)\nEngineering Canvas page reference\nECPURP\nstringarray(50)\nDrawing Purpose\nECREF\nelement\nEngineering Canvas reference\nECRFA\nelement(500)\nEquipment connection reference array\nECRMSU\nstringarray(200)\nEngineering Canvas Revision Mark Subject\nECSHLL\nlogical\nShow Leader Line\nECSHRE\nelement\nEngineering canvas sheet reference\nECSREF\nelement\nEngineering canvas symbol reference\nECSTD\nstring(120)\nEngineering Canvas Standard\nECSTR\nelement\nEngineering canvas symbol template reference\nECSTTY\nstring(120)\nSymbol template type\nECSTVR\nelement\nEngineering canvas symbol template variant reference\nECTARR\nelement(500)\nEngineering Canvas Types\nECTCL\nelement(1000)\nEngineering table cell link reference\nECTCR\nelement(1000)\nEngineering table cell reference\nECTFML\nstring(120)\nEngineering canvas text formula\nECTPLO\nlogical\nTemplate only flag\nECTREF\nelement\nEngineering Canvas Type Reference\nECTREG\nreal(4)\nEngineering canvas template region\nEDEREF\nelement\nEnd reference\nEDGELE\nreal\nEdge Length\nEDGGRD\nlogical\nTrue if any edge should be grinded\nEDGLST\nelement(1000)\nEdge list\nEDISTA\nreal\nVertical Distance of End\nEDOCOR\ninteger\nStores Document order values\nEDOCRF\nelement\nEngineering Referenced Document\nEDOCRV\nstring(120)\nEngineering Document Revision\nEDPUV\npos\nEnd point\nEDSREF\nelement\nStart reference\nEFAC\nstring(1000)\nE-factor\nEFMDM\nstring(240)\nEngineering Feed Mapping Dimension\nEFMFR\nstring(2000)\nEngineering Feed Mapping From\nEFMFUN\nstring(120)\nEngineering Feed Mapping Functional Type\nEFMINC\nlogical\nEngineering Feed Mapping Include\nEFMTO\nstring(2000)\nEngineering Feed Mapping To\nEFOR\nreal(3)\nEnd force vector components\nEIMPED\nreal\nEarth impedance\nELCXRF\nelement(500)\nReturn reference from CABLE element to ELCONN element\nELDATA\ninteger(8192)\ndata\nELDSZ\ninteger\nDataSize\nELECRE\nlogical\ninteger\nTrue if created since given session\nELECREC\nlogical\nTrue if created since comparison date\nELEDEL\nlogical\ninteger\nTrue if deleted since given session\nELEDELC\nlogical\nTrue if deleted since comparison date\nELEGAL\nstring(256)\nElectrogalvanise\nELEL\nword(2147483647)\nTypes of elements, including UDETs, to which this applies\nELEMOD\nlogical\ninteger\nTrue if modified since given session\nELEMODC\nlogical\nTrue if modified since comparison date\nELEPTR\ninteger\nElemp\nELESZ\ninteger\nSize\nELEVAT\nreal\nElevation\nELEVID\nstring(20)\nElevation starting index\nELEVLA\nstring(20)\nLabel for Elevation grid planes\nELEVV\nlogical\nIs Elevation View\nELRATI\nreal\nElectrical Rating\nELTYPC\nword\nElement type\nELVRSN\ninteger\nElement version\nEMOM\nreal(3)\nEnd moment components\nENBINF\npos\ninteger\nEnd bend information\nENCODB\nstring\nDB Encoding\nENDA\nreal\nEnd angle\nENDELE\nreal\nEnd Elevation\nENDOFF\nreal\nOffset of the end of section\nENDPOINT\ninteger\nCable End connection point\nENDPOS\npos\nEnd Position\nENDREF\nelement\nCable End reference\nENDRFARRAY\nelement(100)\nENDATUM reference array\nENGCHG\nlogical\nChanged since Issue\nENGDOC\nelement(2147483647)\nReference to related documents\nENGLNK\nelement\nEngineering Element Link\nENGTYP\nstring(2000)\nDatasheet engineering type\nENHOOK\nstring(256)\nEnd hook reference\nENSEQU\ninteger\nEnd Sequence Position of last work before Macro execution in FCSG list\nENTYCD\ninteger\nType code for end of start\nENVBMA\nreal(3)\nSpecified project envelope box max extent\nENVBMI\nreal(3)\nSpecified project envelope box min extent\nEPARAM\nreal(6)\nEvaluated parameters\nEPKDI\nreal\nProportional distance of end point along Pline\nEPOSTO\nreal\nEnd post tangent offset\nEPREPC\nlogical\nTrue if Varying bevel\nEPREPV\nlogical\nTrue if V-bevel\nEPREPX\nlogical\nTrue if X-bevel\nEPREPY\nlogical\nTrue if Y-bevel\nEQCLASS\nstring(50)\nEquipment class\nEQTYPE\nstring(100)\nEquipment class\nEREACT\nreal\nEarth reactance\nEREC\ninteger\nErection class\nEREL\ninteger\nEnd releases (packed)\nERESIS\nreal\nEarth resistance\nETEX\nstring(1000)\nExample text\nETMTTL\nstring(120)\nEngineering 3D Model Title\nEVITXP\nstring(1500)\nEvaluated intelligent text for projection line\nEVITXT\nstring(1500)\nEvaluated intelligent text\nEVOL\nreal(6)\nEnclosing box volume in given coordinates\nEXBTEX\nstring(1500)\nExpanded annotation text\nEXCESS\nreal\nExcess\nEXCLCH\nstring(50)\nExclusion Character List\nEXCLEL\nlogical\nLogically deleted from the project\nEXCLEN\nreal(3)\nLength of excess intervals\nEXCLFR\nlogical\nTrue if element claimed from this extract. Only True for Primary elements\nEXCLFT\nreal\nExcess on left side of seam\nEXCLHI\nelement(5000)\nPrimary elements in descendant hierarchy claimed to this extract(includes this element)\nEXCLPA\nlogical\nTrue if element claimed to Parent extract. Only True for Primary elements\nEXCLTO\nlogical\nTrue if element claimed to this extract. Only True for Primary elements\nEXCNUM\ninteger(3)\nNumber of excess intervals\nEXCPRM\nelement(8191)\nPrimary locations of extract children\nEXCRGT\nreal\nExcess on right side of seam\nEXCTLF\ninteger\nExcess type on left side of seam\nEXCTRG\ninteger\nExcess type on right side of seam\nEXDIST\nreal\nExit Top Distance\nEXDMTX\nstring(1500)\nExpanded dimension text\nEXECAFTER\nstring(512)\nExec file after DB propagation\nEXECBEFORE\nstring(512)\nExec file before DB propagation\nEXEXTE\nreal\nExit Extension\nEXEXTN\nreal\nExit Extension\nEXFI\ninteger\nExtract file number\nEXHCNC\nelement(5000)\nAs EXTCNC, but repeat test for all descendants\nEXHCNN\nelement(5000)\nAs EXTCNN, but repeat test for all descendants\nEXHCON\nelement(5000)\nAs EXTCON, but repeat test for all descendants\nEXHEIG\nreal\nExit Height\nEXHRCN\nelement(5000)\nAs EXRCN, but repeat test for all descendants\nEXHRCO\nelement(5000)\nAs EXTRCO, but repeat test for all descendants\nEXMOC\nlogical\nAs EXMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXMOD\nlogical\nTrue if element modified in this extract\nEXNCLH\nelement(5000)\nPrimary elements in descendant hierarchy not claimed to this extract\nEXOPRM\nelement\nPrimary location of extract owner\nEXPA\nreal\nSpot value of expansion coefficient\nEXPIRY\nstring(50)\nProtected DB Expiry date\nEXPLTX\nstring(1500)\nExpanded projection line text\nEXPMOC\nlogical\nAs EXPMOD but ignoring changes to \"noclaim\" attributes and member lists\nEXPMOD\nlogical\nTrue if primary and element or non-primary descendants have been modified in this extract\nEXPRESSION\nstring(1000)\nPML or XPath Expression to be executed\nEXPTYPE\nstring(15)\nExpression syntax. Either PML or XPath\nEXTALS\nelement(8191)\nExtract ancestors\nEXTANT\nreal\nTolerance angle\nEXTBOA\nreal\nExtrusion branch OD A\nEXTBOB\nreal\nExtrusion branch OD B\nEXTBOD\nreal\nExtrusion branch outside diameter\nEXTBOX\nreal(6)\nExtended block box\nEXTCLS\nelement(8191)\nExtract children\nEXTCNC\nelement(5000)\nAs EXTCON but excluding non modified elements\nEXTCNN\nelement(5000)\nAs EXTCON but excluding modified elements\nEXTCON\nelement(5000)\nPrimary elements connected/disconnected from element or non primary descendants in extract\nEXTDES\nelement(8191)\nExtract descendants\nEXTDIR\nstring(10)\nDirection of ladder exit\nEXTEAA\nreal\nMinimum distance from an extrusion to the next extrusion\nEXTEAB\nreal\nMinimum distance from centre of an extrusion to next bend\nEXTEAH\nreal\nExtrusion collar height (from the top of tube to the end of collar)\nEXTEAK\nreal\nMinimum distance from an extrusion to the pipe end\nEXTEHE\nreal\nHeight of extrusion machine\nEXTFAM\nelement(8191)\nExtract family\nEXTHI\ninteger\nLocation extract number range, high limit\nEXTLO\ninteger\nLocation extract number range, low limit\nEXTMAS\nelement\nExtract master\nEXTMRE\nelement\nExtrusion machine reference.\nEXTNO\ninteger\nExtract number\nEXTNSN\nreal\nExtension\nEXTOFF\nreal\nExit Offset\nEXTOWN\nelement\nExtract owner\nEXTRC\nstring(120)\nName of extract claiming element\nEXTRCN\nelement(5000)\nAs EXTCNN, but applied recursively to each connection\nEXTRCO\nelement(5000)\nAs EXTCON, but applied recursively to each connection\nEXTREF\nelement\nReferences to exit level\nEXTVOLUME\nreal\nVolume for material\nEXWIDTH\nreal\nExit Width\nEZDI\nreal\nEnd load point in section\n\n\n"}
{"Headers": "Attribute F", "Content": "FAAAWT\ninteger\n\nType of area world\nFAAN\ninteger\n\nSkew angle for font file\nFAATYP\nstring(20)\n\nType of area world as enumerated\nFABLOC\nword\n\nFabrication location\nFABRIC\ninteger\n\nShop or Site fabrication status\nFACODE\nstring(100)\n\nFacode\nFAILCO\ninteger\n\nFailCond\nFAREA\nstring(5)\n\nConstruction area\nFASIOW\nelement(500)\n\nFabrication assembly item referring to element\nFASOWN\nelement(500)\n\nFabrication assembly referring to element\nFASSEQ\ninteger\n\nFabrication assembly sequence\nFASTYP\nword\n\nFastener Type\nFBCOAT\nstring(256)\n\nFirst base coating\nFCACWT\ninteger\n\nType of curve world\nFCATYP\nstring(20)\n\nType of curve world as enumerated\nFCDATE\ninteger(2)\n\nFile creation date\nFCENTRE\npos\n\nCentre of fillet arc\nFCLXSP\nreal(100)\n\nSpacing between stair flights in the X direction of the tower\nFCLYSP\nreal(100)\n\nSpacing between stair flights in the Y direction of the tower\nFCMEAS\nreal\n\nFlange correction measure\nFCOAT\nstring(256)\n\nCoating\nFCODE\nstring\n\nFace code\nFCOE\nreal(3)\n\nFriction coefficient\nFCOLOUR\ninteger\n\nFill colour\nFCONUM\ninteger\n\nFill colour number\nFCPY\nelement\n\nForward copy reference\nFDEPD\nstring(250)\nword\nFormatted Local Design Property Default Value\nFDEPR\nstring(250)\nword\nFormatted Local Design Property Value\nFDESIG\nstring(256)\n\nFastener Designation\nFDRA\nstring(32)\n\nIsometric drawing number\nFEANAM\nstring(80)\n\nDetailing Feature Name\nFEASNM\nstring(80)\n\nDetailing Feature Set Name\nFEDEXS\nreal(500)\n\nFeed excess values\nFEMCOL\ninteger\n\nFEM image object colour\nFEND\npos\n\nFillet arc position\nFEQDES\nstring(120)\n\nFrom Equipment Description\nFFCOAT\nstring(256)\n\nFirst finish coating\nFFCOLO\ninteger\n\nFront-face colour\nFFCONU\ninteger\n\nFront-face colour number\nFFCRGB\ninteger(4)\n\nRGB front face colour\nFFCRGP\ninteger(4)\n\nRGB front face colour physical\nFFLEXT\nreal\n\nEdge Extension Around Floor layer\nFFPN\ninteger\n\nFront-face pen\nFFSTREF\nelement\n\nFront-face linestyle Reference\nFFSTYL\ninteger\n\nFront-face linestyle\nFGAP\nreal\n\nFirst offset distance\nFGRADE\nstring(256)\n\nFastener material grade\nFGRF\nelement\n\nReference to boundary faces\nFHIER\nelement\n\nReferences to functional model hierarchy\nFICHOL\nlogical\n\nFictitious hole\nFILCAL\nstring(80)\n\nFILCAL (name of cable fill level calculation used)\nFILCHK\nlogical\n\nFILCHK (true if fill level check is enabled )\nFILEEX\nlogical\n\nTrue if DB file exists and is valid\nFILENAME\nstring\n\nDB filename\nFILL\nlogical\n\nDRAFT user defined symbol fill flag\nFILLDI\nword\n\nFill direction\nFILREF\nelement(500)\n\nSorted references to attachment points with ascending order of fill level greater then 0\nFILRGB\ninteger(4)\n\nRGB fill colour\nFILRGP\ninteger(4)\n\nRGB fill colour physical\nFILTOPERATOR\nstring(25)\n\nFilter operator\nFILTVALUE\nstring(1000)\n\nFilter value\nFINO\ninteger\n\nFile number\nFINPUT\nstring(120)\n\nInput by\nFIRE\nreal\n\nFire resistance\nFIRERATING\nstring(120)\n\nFire rating\nFISSUE\nstring(12)\n\nCurrent pipe spec issue\nFITLEN\nreal\n\nLength of branch fitting\nFIXEDB\nlogical\n\nFIXEDB (true if bends are fixed)\nFIXLEN\nlogical\n\nFlag to notify if length of the attribute is fixed\nFIXT\nstring(12)\n\nStructural fixity\nFLALLO\nreal\n\nFlange allowance\nFLATYP\ninteger\n\nFlange type\nFLCARE\nreal\n\nFloor cover area\nFLCSTHICKNESS\nreal\n\nFloor cover thickness\nFLCVOL\nreal\n\nFloor cover volume\nFLEN\nstring(1024)\n\nExternal file name\nFLENG\nreal\n\nFastener length\nFLEVEL\nreal\ninteger\nFill level at route node\nFLIM\nreal(3)\n\nForce limit\nFLLARE\nreal\n\nFloor layer area\nFLLTHK\nreal\n\nFloor layer thickness\nFLLVOL\nreal\n\nFloor layer volume\nFLNM\nstring(700)\n\nFull name of the element\nFLNN\nstring(700)\n\nName of the element\nFLOFFS\nreal\n\nFlare Offset\nFLRTYP\nstring(120)\n\nFloor Type\nFLTDIR\ndir\n\nStairflight Direction\nFLTYPE\nstring(120)\n\nFile Type\nFLUR\nelement\n\nFluid reference\nFLWA\nlogical\n\nDRAFT user defined symbol flow arrow\nFMID\npos\n\nMiddle point of fillet arc\nFNAM\nstring(1024)\n\nFilename\nFNCAA\nelement\npos, dir, integer\nReturns an adjoining area given a point and location vector.\nFNCAFP\nelement\npos, dir, integer\nReturns the functional area that contains the given point\nFNCCD\ninteger\n\nFunctional description code\nFNCCL\nelement\npos, dir, integer\nReturns the closest limit to a point within an area.\nFNCCOA\npos\n\nCentre of Area\nFNCLCB\nreal\n\nLength of curve branch\nFNCLOB\nreal\n\nLength of boundary\nFNCTAR\nreal\n\nTotal area\nFNCTXT\nstring(80)\n\nFunctional description\nFNMA\nstring(32)\n\nStandard font file name\nFNMB\nstring(32)\n\nBold font file name\nFNTD\nstring(32)\n\nFont directory\nFOLDED\nlogical\n\nTrue if folded\nFONT\ninteger\n\nText font\nFONTG\ninteger\n\nGLabel style text font\nFONTN\nstring(80)\n\nFont name\nFOOTRO\nreal\n\nFoot Room\nFORC\nreal(3)\n\nForce vector\nFORDAT\nstring(20)\n\nDate Format Definition\nFOREIGN\nstring\n\nDB foreign/local\nFPATH\nstring(256)\n\nFile path\nFPEN\ninteger\n\nFill pen\nFPHASE\nstring(50)\n\nFabrication unit/phase\nFPLINE\nstring(32)\n\nProcess line number\nFPON\ninteger\n\nFROM port number\nFPRDE\nstring(250)\nword\nFormatted property default\nFPROP\nstring(250)\nword\nFormatted property value from dataset\nFRAD\nreal\n\nFillet radius\nFRDR\nstring(32)\n\nReference drawings\nFREF\nelement\n\nFitting reference\nFREFID\ninteger\n\nReference information\nFREV\nstring(4)\n\nIsometric drawing revision\nFRMSCL\nreal\n\nForm scale\nFRPO\npos\n\nEye point\nFRSTW\nelement\nword\nReference of first world of given DB type in current MDB\nFRTXTA\nstring(80)\n\nFree Text Attribute 1\nFRTXTB\nstring(80)\n\nFree Text Attribute 2\nFRTXTC\nstring(80)\n\nFree Text Attribute 3\nFRTXTD\nstring(80)\n\nFree Text Attribute 4\nFRTXTE\nstring(80)\n\nFree Text Attribute 5\nFRTXTF\nstring(80)\n\nFree Text Attribute 6\nFRTXTG\nstring(80)\n\nFree Text Attribute 7\nFRTXTH\nstring(80)\n\nFree Text Attribute 8\nFSETWE\nreal\n\nFastener Set Weight\nFSPMNU\ninteger\n\nFactory Standard Part Mark Number\nFSPOST\nreal\n\nDistance to the first post\nFSPREF\nelement\n\nReference to Factory Standard Part element\nFSPTXT\nstring(120)\n\nFactory Standard Part Text\nFSTAND\nstring(256)\n\nFastener Standard\nFSTART\npos\n\nFillet start position\nFSTAT\nstring(15)\n\nFstatus\nFSTNUM\ninteger\n\nFill style number\nFSTREF\nelement\n\nFill style Reference\nFSTYLE\ninteger\n\nFill style\nFSTYNO\ninteger\n\nFill Style Number\nFTCDD\nstring(250)\nword\nFormatted Current Design Property Default Value\nFTCDP\nstring(250)\nword\nFormatted Current Design Property Value\nFTER\nstring\n\nFirst dimension terminator code\nFTERID\ninteger\n\nFirst terminator ID\nFTERSA\ninteger\n\nDimension first term. code style angular FTERSA\nFTERSL\ninteger\n\nDimension first term. code style linear FTERSL\nFTHICKNESS\nreal\n\nStair Flight Thickness\nFTVALS\nreal(1000)\n\nt Values for nesting components\nFULLEN\nreal\n\nTotal length of manufactured profile\nFULLID\nstring(20)\n\nFull ID Plane\nFULLT\nstring\n\ntype of the element\nFULSYS\nstring\n\nType of the element, ignoring UDET, not truncated\nFUNC\nstring(120)\n\nFunction\nFUNI\ninteger\n\nFUNIT\nFURNRF\nelement\n\nFurniture Reference\nFWEI\nreal\n\nFastener Weight\n\nAttribute Name\nData Type\nQualifier\nDescription\nFAAAWT\ninteger\nType of area world\nFAAN\ninteger\nSkew angle for font file\nFAATYP\nstring(20)\nType of area world as enumerated\nFABLOC\nword\nFabrication location\nFABRIC\ninteger\nShop or Site fabrication status\nFACODE\nstring(100)\nFacode\nFAILCO\ninteger\nFailCond\nFAREA\nstring(5)\nConstruction area\nFASIOW\nelement(500)\nFabrication assembly item referring to element\nFASOWN\nelement(500)\nFabrication assembly referring to element\nFASSEQ\ninteger\nFabrication assembly sequence\nFASTYP\nword\nFastener Type\nFBCOAT\nstring(256)\nFirst base coating\nFCACWT\ninteger\nType of curve world\nFCATYP\nstring(20)\nType of curve world as enumerated\nFCDATE\ninteger(2)\nFile creation date\nFCENTRE\npos\nCentre of fillet arc\nFCLXSP\nreal(100)\nSpacing between stair flights in the X direction of the tower\nFCLYSP\nreal(100)\nSpacing between stair flights in the Y direction of the tower\nFCMEAS\nreal\nFlange correction measure\nFCOAT\nstring(256)\nCoating\nFCODE\nstring\nFace code\nFCOE\nreal(3)\nFriction coefficient\nFCOLOUR\ninteger\nFill colour\nFCONUM\ninteger\nFill colour number\nFCPY\nelement\nForward copy reference\nFDEPD\nstring(250)\nword\nFormatted Local Design Property Default Value\nFDEPR\nstring(250)\nword\nFormatted Local Design Property Value\nFDESIG\nstring(256)\nFastener Designation\nFDRA\nstring(32)\nIsometric drawing number\nFEANAM\nstring(80)\nDetailing Feature Name\nFEASNM\nstring(80)\nDetailing Feature Set Name\nFEDEXS\nreal(500)\nFeed excess values\nFEMCOL\ninteger\nFEM image object colour\nFEND\npos\nFillet arc position\nFEQDES\nstring(120)\nFrom Equipment Description\nFFCOAT\nstring(256)\nFirst finish coating\nFFCOLO\ninteger\nFront-face colour\nFFCONU\ninteger\nFront-face colour number\nFFCRGB\ninteger(4)\nRGB front face colour\nFFCRGP\ninteger(4)\nRGB front face colour physical\nFFLEXT\nreal\nEdge Extension Around Floor layer\nFFPN\ninteger\nFront-face pen\nFFSTREF\nelement\nFront-face linestyle Reference\nFFSTYL\ninteger\nFront-face linestyle\nFGAP\nreal\nFirst offset distance\nFGRADE\nstring(256)\nFastener material grade\nFGRF\nelement\nReference to boundary faces\nFHIER\nelement\nReferences to functional model hierarchy\nFICHOL\nlogical\nFictitious hole\nFILCAL\nstring(80)\nFILCAL (name of cable fill level calculation used)\nFILCHK\nlogical\nFILCHK (true if fill level check is enabled )\nFILEEX\nlogical\nTrue if DB file exists and is valid\nFILENAME\nstring\nDB filename\nFILL\nlogical\nDRAFT user defined symbol fill flag\nFILLDI\nword\nFill direction\nFILREF\nelement(500)\nSorted references to attachment points with ascending order of fill level greater then 0\nFILRGB\ninteger(4)\nRGB fill colour\nFILRGP\ninteger(4)\nRGB fill colour physical\nFILTOPERATOR\nstring(25)\nFilter operator\nFILTVALUE\nstring(1000)\nFilter value\nFINO\ninteger\nFile number\nFINPUT\nstring(120)\nInput by\nFIRE\nreal\nFire resistance\nFIRERATING\nstring(120)\nFire rating\nFISSUE\nstring(12)\nCurrent pipe spec issue\nFITLEN\nreal\nLength of branch fitting\nFIXEDB\nlogical\nFIXEDB (true if bends are fixed)\nFIXLEN\nlogical\nFlag to notify if length of the attribute is fixed\nFIXT\nstring(12)\nStructural fixity\nFLALLO\nreal\nFlange allowance\nFLATYP\ninteger\nFlange type\nFLCARE\nreal\nFloor cover area\nFLCSTHICKNESS\nreal\nFloor cover thickness\nFLCVOL\nreal\nFloor cover volume\nFLEN\nstring(1024)\nExternal file name\nFLENG\nreal\nFastener length\nFLEVEL\nreal\ninteger\nFill level at route node\nFLIM\nreal(3)\nForce limit\nFLLARE\nreal\nFloor layer area\nFLLTHK\nreal\nFloor layer thickness\nFLLVOL\nreal\nFloor layer volume\nFLNM\nstring(700)\nFull name of the element\nFLNN\nstring(700)\nName of the element\nFLOFFS\nreal\nFlare Offset\nFLRTYP\nstring(120)\nFloor Type\nFLTDIR\ndir\nStairflight Direction\nFLTYPE\nstring(120)\nFile Type\nFLUR\nelement\nFluid reference\nFLWA\nlogical\nDRAFT user defined symbol flow arrow\nFMID\npos\nMiddle point of fillet arc\nFNAM\nstring(1024)\nFilename\nFNCAA\nelement\npos, dir, integer\nReturns an adjoining area given a point and location vector.\nFNCAFP\nelement\npos, dir, integer\nReturns the functional area that contains the given point\nFNCCD\ninteger\nFunctional description code\nFNCCL\nelement\npos, dir, integer\nReturns the closest limit to a point within an area.\nFNCCOA\npos\nCentre of Area\nFNCLCB\nreal\nLength of curve branch\nFNCLOB\nreal\nLength of boundary\nFNCTAR\nreal\nTotal area\nFNCTXT\nstring(80)\nFunctional description\nFNMA\nstring(32)\nStandard font file name\nFNMB\nstring(32)\nBold font file name\nFNTD\nstring(32)\nFont directory\nFOLDED\nlogical\nTrue if folded\nFONT\ninteger\nText font\nFONTG\ninteger\nGLabel style text font\nFONTN\nstring(80)\nFont name\nFOOTRO\nreal\nFoot Room\nFORC\nreal(3)\nForce vector\nFORDAT\nstring(20)\nDate Format Definition\nFOREIGN\nstring\nDB foreign/local\nFPATH\nstring(256)\nFile path\nFPEN\ninteger\nFill pen\nFPHASE\nstring(50)\nFabrication unit/phase\nFPLINE\nstring(32)\nProcess line number\nFPON\ninteger\nFROM port number\nFPRDE\nstring(250)\nword\nFormatted property default\nFPROP\nstring(250)\nword\nFormatted property value from dataset\nFRAD\nreal\nFillet radius\nFRDR\nstring(32)\nReference drawings\nFREF\nelement\nFitting reference\nFREFID\ninteger\nReference information\nFREV\nstring(4)\nIsometric drawing revision\nFRMSCL\nreal\nForm scale\nFRPO\npos\nEye point\nFRSTW\nelement\nword\nReference of first world of given DB type in current MDB\nFRTXTA\nstring(80)\nFree Text Attribute 1\nFRTXTB\nstring(80)\nFree Text Attribute 2\nFRTXTC\nstring(80)\nFree Text Attribute 3\nFRTXTD\nstring(80)\nFree Text Attribute 4\nFRTXTE\nstring(80)\nFree Text Attribute 5\nFRTXTF\nstring(80)\nFree Text Attribute 6\nFRTXTG\nstring(80)\nFree Text Attribute 7\nFRTXTH\nstring(80)\nFree Text Attribute 8\nFSETWE\nreal\nFastener Set Weight\nFSPMNU\ninteger\nFactory Standard Part Mark Number\nFSPOST\nreal\nDistance to the first post\nFSPREF\nelement\nReference to Factory Standard Part element\nFSPTXT\nstring(120)\nFactory Standard Part Text\nFSTAND\nstring(256)\nFastener Standard\nFSTART\npos\nFillet start position\nFSTAT\nstring(15)\nFstatus\nFSTNUM\ninteger\nFill style number\nFSTREF\nelement\nFill style Reference\nFSTYLE\ninteger\nFill style\nFSTYNO\ninteger\nFill Style Number\nFTCDD\nstring(250)\nword\nFormatted Current Design Property Default Value\nFTCDP\nstring(250)\nword\nFormatted Current Design Property Value\nFTER\nstring\nFirst dimension terminator code\nFTERID\ninteger\nFirst terminator ID\nFTERSA\ninteger\nDimension first term. code style angular FTERSA\nFTERSL\ninteger\nDimension first term. code style linear FTERSL\nFTHICKNESS\nreal\nStair Flight Thickness\nFTVALS\nreal(1000)\nt Values for nesting components\nFULLEN\nreal\nTotal length of manufactured profile\nFULLID\nstring(20)\nFull ID Plane\nFULLT\nstring\ntype of the element\nFULSYS\nstring\nType of the element, ignoring UDET, not truncated\nFUNC\nstring(120)\nFunction\nFUNI\ninteger\nFUNIT\nFURNRF\nelement\nFurniture Reference\nFWEI\nreal\nFastener Weight\n\n\n"}
{"Headers": "Attribute G", "Content": "GANGLE\nreal\n\nGeneral Angle\nGAP\ninteger\n\nEnd cut gap\nGAPALL\nstring(1000)\n\nGap Allowance\nGAPF\nreal\n\nFirst offset distance\nGAPI\nreal\n\nIntermediate offset distance\nGAPLEN\nreal\n\nGap length\nGAPPOS\nreal(2)\n\nGap definition points\nGAPS\nreal(150)\n\nProjection line gap array\nGAPWID\nreal\n\nGap width\nGAREA\nreal\n\nCeiling Grid Area\nGASTIG\nlogical\n\nGas Tight\nGATECO\nstring(120)\n\nGate Configuration\nGATEHEIGHT\nreal\n\nGate Height\nGATESI\nreal(2)\n\nGate Size\nGATEWD\nreal\n\nGate Width\nGBOX\nreal\n\nBox gap\nGBOXTX\nstring(80)\n\nBox gap text\nGCOF\npos\n\nGross centre of gravity\nGDEFIN\ninteger(100)\n\nGlyph Outline Definition\nGDIAM\ninteger\n\nGlyph Circle Diameter\nGENGT\nword\n\nGeometry type\nGENIX\nstring(125)\n\ngeneration information for x direction\nGENIY\nstring(125)\n\ngeneration information for y direction\nGENIZ\nstring(125)\n\ngeneration information for z direction\nGENSTR\nstring\ninteger\nGeneral strings\nGENTYP\nword\n\nType of geometry\nGEODEP\nelement(5000)\n\nDirect geometrical dependencies\nGEOHEIGHT\nreal\n\nElevation\nGEOM\ninteger\n\nGeometry Modified- Not directly queryable\nGFILLD\nlogical\n\nGlyph Primitive Filled Flag\nGHEIGH\nreal\n\nGate Height\nGLBSTR\nlogical\n\nTrue if Project has Global structure\nGLBVER\nstring(120)\n\nGlobal version string\nGLINKP\nlogical\n\nProject has Linked Documents distribution enabled\nGLOGNM\nstring(256)\n\nWindows authentication user group name\nGLYNO\ninteger\n\nGlyph Number\nGLYNUM\ninteger\n\nGlyph Number\nGLYREF\nelement\n\nGlyph Reference\nGMOF\nreal(9)\n\nGross moments of inertia\nGMRE\nelement\n\nGeometry set reference\nGOBREF\nelement\n\nGenerating reference\nGOFFS\ninteger(2)\n\nGlyph Primitive offset\nGOING\nreal(10)\n\nTread Going\nGOVCOM\nelement\n\nBaseline governing component reference\nGPENH\ninteger\n\npen for hidden lines\nGPENV\ninteger\n\npen for visible lines\nGPKGFI\ninteger(500)\n\nGeneric Package Filter Expression\nGPKGRF\nelement\n\nGeneric Package Reference\nGPPRXS\nelement(500)\n\nGroup proxy items referring to element\nGPRTRE\nelement(100)\n\nGpart reference\nGPSTR\nstring(26)\ninteger\nGeneral purpose strings\nGRADE\nreal\n\nSteel grade\nGRAXE\ninteger\n\nGrid axes (internal)\nGRDAC\ninteger\n\nDetailing Model Grid Access Mode\nGRDAXE\nstring\n\nGrid axes\nGRDDIR\ndir\n\nGrid direction\nGRDE\nreal\n\nGradient of implied tube. Gradient is the vertical rise(fall) divided by the horizontal distance.\nGRDID\nstring(20)\n\nGrid plane index\nGRDLBL\nstring(120)\n\nPlanes Label\nGRDLID\ninteger(2)\n\nGridline Identifier\nGRDLXP\nreal\n\nProportion along X gridline from Gridline ID\nGRDLYP\nreal\n\nProportion along Y gridline from Gridline ID\nGRDNUM\ninteger\n\ngrid number\nGRDOFF\nreal\n\nGrid offset\nGRDPOS\npos\n\nGrid Position\nGRDREF\nelement\n\nGrid reference\nGRDTYP\ninteger\n\ngrid type\nGRDVIS\nlogical\n\nvisibility of the grid\nGRDXSP\nreal(10000)\n\nGrid X Spacing\nGRDYSP\nreal(10000)\n\nGrid Y Spacing\nGRIDNM\nelement\n\nDesign grid reference\nGRIDNX\nstring(120)\n\nDesign element as text\nGRIDX\nstring(20)\n\nGrid X position\nGRIDXPOS\nstring\n\nX position of the symbol according to the gridding definition\nGRIDY\nstring(20)\n\nGrid Y position\nGRIDYPOS\nstring\n\nY position of the symbol according to the gridding definition\nGRIDZ\nstring(20)\n\nGrid Z position\nGRILEN\nreal\n\nLength of grinding intervals\nGRIND\nreal\n\nGrinding info\nGRINUM\ninteger\n\nNumber of grinding intervals\nGRIP\nreal\n\nMinimum distance between bends\nGROUPS\nelement(500)\nelemtype, logical\nGPSETs in which element occurs\nGRPRF\nelement\n\nReference to group (owner of location)\nGRPSCR\nlogical\n\nIndicates screened or shielded group\nGRPSEQ\ninteger\n\nCore group sequence\nGRPTYP\nstring(120)\n\nText storing group type for cable\nGRREL\ninteger\n\nGoverning revision relationship type\nGRSYS\nelement\n\nGrid system reference\nGSRF\nreal\n\nGross surface area\nGSTR\nelement\n\nStructural geometry set reference\nGTAREAS\nelement(5000)\n\nAll areas whose bounding box fully or partially enclose element\nGTEXAREAS\nelement(5000)\n\nAll areas that fully or partially enclose element\nGTGROUPS\nelement(5000)\n\nAll groups that fully enclose element\nGTHARD\nelement(5000)\n\nAll rooms with hard obstruction that fully enclose element\nGTROOM\nelement(5000)\n\nAll rooms that fully enclose element\nGTSOFT\nelement(5000)\n\nAll rooms with soft obstruction that fully enclose element\nGTXT\nstring(120)\n\nText storing rule to generate Inventory List\nGTYP\nword\n\nGeneric type\nGVOL\nreal\n\nGross volume\nGWEI\nreal\n\nGross weight\nGWIDTH\nreal\n\nGate Width\nGXLEN\ninteger\n\nGlyph Rectangle XLength\nGXYOFF\nreal(2)\n\nGrid XY Offset\nGYLEN\ninteger\n\nGlyph Rectangle YLength\n\nAttribute Name\nData Type\nQualifier\nDescription\nGANGLE\nreal\nGeneral Angle\nGAP\ninteger\nEnd cut gap\nGAPALL\nstring(1000)\nGap Allowance\nGAPF\nreal\nFirst offset distance\nGAPI\nreal\nIntermediate offset distance\nGAPLEN\nreal\nGap length\nGAPPOS\nreal(2)\nGap definition points\nGAPS\nreal(150)\nProjection line gap array\nGAPWID\nreal\nGap width\nGAREA\nreal\nCeiling Grid Area\nGASTIG\nlogical\nGas Tight\nGATECO\nstring(120)\nGate Configuration\nGATEHEIGHT\nreal\nGate Height\nGATESI\nreal(2)\nGate Size\nGATEWD\nreal\nGate Width\nGBOX\nreal\nBox gap\nGBOXTX\nstring(80)\nBox gap text\nGCOF\npos\nGross centre of gravity\nGDEFIN\ninteger(100)\nGlyph Outline Definition\nGDIAM\ninteger\nGlyph Circle Diameter\nGENGT\nword\nGeometry type\nGENIX\nstring(125)\ngeneration information for x direction\nGENIY\nstring(125)\ngeneration information for y direction\nGENIZ\nstring(125)\ngeneration information for z direction\nGENSTR\nstring\ninteger\nGeneral strings\nGENTYP\nword\nType of geometry\nGEODEP\nelement(5000)\nDirect geometrical dependencies\nGEOHEIGHT\nreal\nElevation\nGEOM\ninteger\nGeometry Modified- Not directly queryable\nGFILLD\nlogical\nGlyph Primitive Filled Flag\nGHEIGH\nreal\nGate Height\nGLBSTR\nlogical\nTrue if Project has Global structure\nGLBVER\nstring(120)\nGlobal version string\nGLINKP\nlogical\nProject has Linked Documents distribution enabled\nGLOGNM\nstring(256)\nWindows authentication user group name\nGLYNO\ninteger\nGlyph Number\nGLYNUM\ninteger\nGlyph Number\nGLYREF\nelement\nGlyph Reference\nGMOF\nreal(9)\nGross moments of inertia\nGMRE\nelement\nGeometry set reference\nGOBREF\nelement\nGenerating reference\nGOFFS\ninteger(2)\nGlyph Primitive offset\nGOING\nreal(10)\nTread Going\nGOVCOM\nelement\nBaseline governing component reference\nGPENH\ninteger\npen for hidden lines\nGPENV\ninteger\npen for visible lines\nGPKGFI\ninteger(500)\nGeneric Package Filter Expression\nGPKGRF\nelement\nGeneric Package Reference\nGPPRXS\nelement(500)\nGroup proxy items referring to element\nGPRTRE\nelement(100)\nGpart reference\nGPSTR\nstring(26)\ninteger\nGeneral purpose strings\nGRADE\nreal\nSteel grade\nGRAXE\ninteger\nGrid axes (internal)\nGRDAC\ninteger\nDetailing Model Grid Access Mode\nGRDAXE\nstring\nGrid axes\nGRDDIR\ndir\nGrid direction\nGRDE\nreal\nGradient of implied tube. Gradient is the vertical rise(fall) divided by the horizontal distance.\nGRDID\nstring(20)\nGrid plane index\nGRDLBL\nstring(120)\nPlanes Label\nGRDLID\ninteger(2)\nGridline Identifier\nGRDLXP\nreal\nProportion along X gridline from Gridline ID\nGRDLYP\nreal\nProportion along Y gridline from Gridline ID\nGRDNUM\ninteger\ngrid number\nGRDOFF\nreal\nGrid offset\nGRDPOS\npos\nGrid Position\nGRDREF\nelement\nGrid reference\nGRDTYP\ninteger\ngrid type\nGRDVIS\nlogical\nvisibility of the grid\nGRDXSP\nreal(10000)\nGrid X Spacing\nGRDYSP\nreal(10000)\nGrid Y Spacing\nGRIDNM\nelement\nDesign grid reference\nGRIDNX\nstring(120)\nDesign element as text\nGRIDX\nstring(20)\nGrid X position\nGRIDXPOS\nstring\nX position of the symbol according to the gridding definition\nGRIDY\nstring(20)\nGrid Y position\nGRIDYPOS\nstring\nY position of the symbol according to the gridding definition\nGRIDZ\nstring(20)\nGrid Z position\nGRILEN\nreal\nLength of grinding intervals\nGRIND\nreal\nGrinding info\nGRINUM\ninteger\nNumber of grinding intervals\nGRIP\nreal\nMinimum distance between bends\nGROUPS\nelement(500)\nelemtype, logical\nGPSETs in which element occurs\nGRPRF\nelement\nReference to group (owner of location)\nGRPSCR\nlogical\nIndicates screened or shielded group\nGRPSEQ\ninteger\nCore group sequence\nGRPTYP\nstring(120)\nText storing group type for cable\nGRREL\ninteger\nGoverning revision relationship type\nGRSYS\nelement\nGrid system reference\nGSRF\nreal\nGross surface area\nGSTR\nelement\nStructural geometry set reference\nGTAREAS\nelement(5000)\nAll areas whose bounding box fully or partially enclose element\nGTEXAREAS\nelement(5000)\nAll areas that fully or partially enclose element\nGTGROUPS\nelement(5000)\nAll groups that fully enclose element\nGTHARD\nelement(5000)\nAll rooms with hard obstruction that fully enclose element\nGTROOM\nelement(5000)\nAll rooms that fully enclose element\nGTSOFT\nelement(5000)\nAll rooms with soft obstruction that fully enclose element\nGTXT\nstring(120)\nText storing rule to generate Inventory List\nGTYP\nword\nGeneric type\nGVOL\nreal\nGross volume\nGWEI\nreal\nGross weight\nGWIDTH\nreal\nGate Width\nGXLEN\ninteger\nGlyph Rectangle XLength\nGXYOFF\nreal(2)\nGrid XY Offset\nGYLEN\ninteger\nGlyph Rectangle YLength\n\n\n"}
{"Headers": "Attribute H", "Content": "HANEXP\npos\n\nHANCI expected position wrt the start of the COMPRE\nHANGLE\nreal\n\nHatching Angle\nHANICOFFSET\nreal(3)\n\nHANCI INTERNAL CACHED OFFSET\nHANICPOSITION\nreal(3)\n\nINTERNAL HANCI cached position\nHANOFFSET\npos\n\nHANCI cached position offset\nHANPOSITION\npos\n\nSupport cached position\nHASCLN\nlogical\n\nHas clones flag\nHAZARD\nstring(120)\n\nHazard\nHAZTYP\nstring(120)\n\nHazard Description\nHBLBOX\nreal(6)\n\nBlock box\nHBOR\nreal\n\nHead bore\nHCCNT\ninteger\n\nHeader/Extract list changes count\nHCNREF\nelement\n\nHullConnection reference\nHCOFG\npos\n\ncomputed hull item centre of gravity\nHCON\nword\n\nHead connection type\nHCORRO\nreal\n\nHead Corrosion\nHCREF\nelement(100)\n\nHead connections\nHDBREF\nelement\n\nGeneric Hull DB Ref\nHDCONN\nelement(500)\n\nList of elements connected to branch head\nHDIR\ndir\n\nHead direction\nHDIST\nreal\n\nHorizontal Distance\nHDMF\nelement(2)\n\nISODRAFT Reference Dimension attribute\nHDMT\nword(2)\n\nISODRAFT Reference Dimension attribute\nHDREF\nelement(500)\n\nList of attachment connected to attachment\nHDSHAP\nword\n\nBranch head duct shape\nHDUPLI\nelement(10000)\ninteger\nDuplicates of the current element (checking members)\nHEADCL\nreal\n\nHead Clearance\nHEADH\nreal\n\nHead duct height\nHEADRO\nreal\n\nHeadroom\nHEADW\nreal\n\nHead duct width\nHEATT\ninteger\n\nHeat Treatment\nHEIARR\nreal(10)\n\nHeight array\nHEID\nreal\n\nDefault Height value\nHEIF\nreal\n\nHeight attractor factor\nHEIG\nreal\n\nHeight\nHEIL\nreal(2)\n\nHeight limits (Min/Max)\nHEIS\nlogical\n\nHeight set flag - ignore Height values if FALSE\nHEND\nstring\n\nConnection at other end of HREF (HEAD or TAIL)\nHGHT\nreal\n\nHeight\nHGSIDE\nword\n\nHinge side\nHHBO\nreal\n\nHanger head bore\nHHBP\npos\n\nBottom of hanger head\nHHCO\nword\n\nHanger head connection type\nHHDR\ndir\n\nHanger head direction\nHHGR\nreal\n\nHanger head gradient\nHHOD\nreal\n\nHanger head outside diameter\nHHPO\npos\n\nHanger head position\nHHTP\npos\n\nTop of hanger head\nHIERARCHY\nelement(5000)\n\nStructural connections\nHIST\ninteger(120)\nattr\nHistory of sessions in which element or specified attribute were made\nHLCOLO\nstring\n\nHull Colour\nHLIS\nword(2000)\n\nList of all possible types in owning hierarchy\nHLSTREF\nelement\n\nHatching linestyle Reference\nHLSTYLE\ninteger\n\nHatching linestyle\nHMAV\nreal\n\nAverage humidity\nHMMA\nreal\n\nMaximum humidity\nHMMI\nreal\n\nMinimum humidity\nHNCKEY\ninteger\n\nHole Notch Cutout Key\nHNODEL\nelement(500)\n\nHnode list\nHOFFSE\nreal\n\nHatching Line Offset\nHOLDES\nstring(120)\n\nHole Designation\nHOLGRD\nlogical\n\nTrue if any hole in the part should be grinded\nHOLTYP\ninteger\n\nDetailing Model Hole Type\nHOOGEO\nreal(8)\n\nHook definition curve\nHOOPSP\nreal\n\nHoop Spacing\nHOOTYP\ninteger\n\nHook type\nHPATNO\ninteger\n\nHatch Pattern Number\nHPOS\npos\n\nHead position\nHPOSE\nreal\n\nEasting of head position\nHPOSN\nreal\n\nNorthing of head position\nHPOSU\nreal\n\nUpping of head position\nHPREF\nelement\n\nHead point reference\nHRCLE\nreal\n\nHANDRAIL CLEAR WIDTH\nHREF\nelement\n\nHead reference\nHREL\nlogical\n\nBranch Member Head relative flag (Router)\nHRJUSL\nword\n\nHandrail Justification Line\nHROBS\nreal\n\nHandrail Obstruction\nHROFF\nreal\n\nHandrail Offset\nHRSDIS\nreal\n\nHandrail Start Distance\nHRSF\nelement\n\nHatch ruleset reference\nHRSTAR\nreal\n\nHandrail Start Height\nHSARFA\nelement(500)\n\nHVACSpool arrive references\nHSEPAR\nreal\n\nHatching Line Separation\nHSLRFA\nelement(500)\n\nHVACSpool leave references\nHSPE\nelement\n\nHanger specification\nHSRFA\nreal\n\nComputed Hull item surface area\nHSRO\nelement\n\nHeadrod specification\nHSTU\nelement\n\nHead tube specification\nHSTYF\nelement\n\nHatch style reference\nHSVLD\nlogical\n\nHVACspool valid\nHTBO\nreal\n\nHanger tail bore\nHTBP\npos\n\nBottom of hanger tail\nHTCO\nword\n\nHanger tail connection type\nHTDR\ndir\n\nHanger tail direction\nHTGR\nreal\n\nHanger tail gradient\nHTOD\nreal\n\nHanger tail outside diameter\nHTPO\npos\n\nHanger tail position\nHTPREF\nelement\n\nTopology reference\nHTTP\npos\n\nTop of hanger tail\nHTYP\nword\n\nHanger type\nHUBRF\nelement\n\nReference to the hub location\nHULAPP\nlogical\n\nHull applicable Geometry\nHULCNT\ninteger\n\nSize of hull array/collection\nHULLDE\nlogical\n\nTrue if element is a hull design item\nHULLOB\nelement\n\nHull object reference\nHULLPR\nlogical\n\nTrue if element is a hull production item\nHULOC\nstring\n\nLocation\nHUMIDI\nreal\n\nDesign Humidity\nHUMIRR\nlogical\n\nTrue if mirrored in local v-axis\nHUMVW\nstring\n\nModel View\nHUREFL\nlogical\n\nReflected\nHUREPL\nelement\n\nReplica\nHUSYMM\nlogical\n\nSymmetrical\nHVOLU\nreal\n\nComputed Hull Item volume\nHWALLT\nreal\n\nHead wall thickness\nHWRF\nelement\n\nHead Working Point (Router)\nHYACTV\nreal\n\nActual value\nHYAEAP\nreal\n\nAft end of Ls aft of AP\nHYAIDX\nreal\n\nAttained index\nHYALKT\nreal\n\nAbove water line KG2\nHYAOPS\nstring(120)\n\nActive opening states\nHYARAT\nreal\n\nArea ratio\nHYASSE\ninteger\n\nAssessment\nHYAWLA\nreal\n\nAbove water line area\nHYBDAE\nreal\n\nAft extent of bay\nHYBDFE\nreal\n\nFwd extent of bay\nHYBEMO\nreal\n\nBending moment\nHYBHAT\nreal\n\nBreadth of hatch\nHYBHFC\nreal\n\nBulkhead factor\nHYBML\nreal\n\nBMl\nHYBMT\nreal\n\nBMt\nHYBPPM\nreal\n\n% of max allowed\nHYBRAD\nreal\n\nBilge radius\nHYBUIL\nstring(120)\n\nBuilder\nHYBVAL\nreal\n\nb value\nHYBWL\nreal\n\nBreadth in water line\nHYCAST\nstring(120)\n\nDamage case + state\nHYCB\nreal\n\nBlock coefficient\nHYCBWL\nreal\n\nBlock coefficient calc in water line\nHYCBX\nreal\n\nCB including volume for shell\nHYCLAN\nstring(120)\n\nClass Number\nHYCLET\nstring(120)\n\nCall letters\nHYCM\nreal\n\nMidship area coefficient\nHYCMWL\nreal\n\nMidship area coefficient calc in water line\nHYCOLR\ninteger\n\nColour\nHYCOMP\nelement\n\nCompartment\nHYCONA\nstring(120)\n\nCondition\nHYCONB\nstring(120)\n\nCondition\nHYCOND\nelement\n\nLoading condition\nHYCP\nreal\n\nPrismatic coefficient\nHYCPCA\nelement(125)\n\nCompartment category\nHYCPER\nreal\n\nProbabilistic permeability values\nHYCPID\nstring(120)\n\nCompartment ID\nHYCPNA\nstring(120)\n\nCompartment name\nHYCPWL\nreal\n\nPrismatic coefficient calc in water line\nHYCRCA\nstring(120)\n\nCritical case\nHYCRDA\nstring(120)\n\nDamage stability criteria\nHYCRIT\nstring(120)\n\nCriterion\nHYCRIV\nreal\n\nCritical value\nHYCRKG\nreal\n\nCritical KGf\nHYCROW\nreal\n\nCrowding lever\nHYCRPR\nstring(120)\n\nProbabilistic damage stability criteria\nHYCSTM\nstring(120)\n\nCustomer\nHYCTBT\nstring(120)\n\nBay Title\nHYCTCT\nelement\n\nContainer type\nHYCTNA\nstring(120)\n\nDescription\nHYCTNO\ninteger\n\nNumber of containers\nHYCTRM\nreal\n\nTrim\nHYCTTI\nstring\n\nLoading set title\nHYCTTR\nstring(120)\n\nTier\nHYCTTY\nstring(50)\n\nType\nHYCTYP\nstring(120)\n\nIntact/Damaged\nHYCVCG\nreal\n\nCritical VCG\nHYCVOL\nreal\n\nCargo volume\nHYCW\nreal\n\nWater plane area coefficient\nHYCWWL\nreal\n\nWater plane area coefficient calc in water line\nHYDAP\nreal\n\nDraft at AP\nHYDATP\nstring(120)\n\nDamage type\nHYDCID\nstring(120)\n\nDamage case\nHYDCMP\nelement\n\nDamaged compartments\nHYDECK\nreal\n\nDeck\nHYDEFW\nreal\n\nDeadweight Fresh water\nHYDEIM\nreal\n\nDeck edge immersion\nHYDENS\nreal\n\nDensity\nHYDESC\nstring(120)\n\nDescription\nHYDESD\nreal\n\nDesign draft moulded\nHYDESW\nreal\n\nDeadweight Salt water\nHYDFP\nreal\n\nDraft at FP\nHYDHGT\nreal\n\nHeight (H)\nHYDHMX\nreal\n\nHmax\nHYDIFW\nreal\n\nDisplacement Fresh water\nHYDISP\nreal\n\nDisplacement\nHYDISW\nreal\n\nDisplacement Salt water\nHYDLCF\nreal\n\nDraft at LCF\nHYDLOA\nstring(120)\n\nLoading condition\nHYDLOD\nreal\n\nDisplacement at load draft\nHYDMAX\nreal\n\nDraft marks aft x\nHYDMAZ\nreal\n\nDraft marks aft z\nHYDMCA\nelement\n\nDamage cases compartment is part of\nHYDMFX\nreal\n\nDraft marks fwd x\nHYDMFZ\nreal\n\nDraft marks fwd z\nHYDNAM\nstring(120)\n\nDescriptive name\nHYDOBU\nstring(120)\n\nDate of build\nHYDORI\nreal\n\nDistance from origin\nHYDOWN\nreal\n\nDownflood\nHYDPCA\nreal\n\nDepth of cargo\nHYDPTH\nreal\n\nDepth moulded\nHYDRAF\nreal\n\nDraft\nHYDRAM\nreal\n\nDraft aft at marks\nHYDRAP\nreal\n\nDraft AP\nHYDREF\nelement\n\nDamage case ref\nHYDRFM\nreal\n\nDraft fwd at marks\nHYDRFP\nreal\n\nDraft FP\nHYDS\nreal\n\nDS\nHYDTOL\nreal\n\nDraft tolerance\nHYDWTM\nreal\n\nDeadweight moment\nHYEFUL\nreal\n\nWeight full\nHYEVCG\nreal\n\nVCG Empty\nHYEXTR\nstring(120)\n\nHydrostatics calculated to extreme/moulded drafts\nHYFAGL\nstring(120)\n\nFlood angle\nHYFANG\nreal\n\nFlood angle\nHYFBDP\nreal\n\nFreeboard depth\nHYFBRD\nreal\n\nFreeboard\nHYFLAG\nstring(120)\n\nFlag\nHYFLKE\nreal\n\nFlat of keel\nHYFRAM\nelement\n\nFrames\nHYFRFR\ninteger\n\nFrom frame\nHYFRLE\nreal\n\nFreeboard length\nHYFRSP\nreal\n\nFrame spacing\nHYFRTY\nstring(120)\n\nFreeboard type\nHYFSC\nreal\n\nFSC\nHYFSM\nreal\n\nFree surface moment\nHYFVCG\nreal\n\nVCG Full\nHYGCMP\nelement\n\nCompartment\nHYGHGT\nreal\n\nHeight of water above grounding point\nHYGHIN\nreal\n\nStability calculations heel increment\nHYGHMO\nreal\n\nAllowable Grain Heeling Moment\nHYGIRD\nreal\n\nGirder depth\nHYGM\nreal\n\nGM\nHYGMT\nreal\n\nGMt\nHYGRAN\nreal\n\nGrain angle\nHYGTON\nreal\n\nGross tonnage\nHYGZ\nreal\n\nGZ\nHYGZAR\nreal\n\nArea\nHYGZMA\nreal\n\nMax GZ\nHYGZMD\nreal\n\nMax GZ at degrees\nHYGZRA\nreal\n\nGZ-range\nHYHABV\nreal\n\nHeight above\nHYHAFR\nreal\n\nHeel angle from\nHYHAMD\nreal\n\nHatch height over moulded depth\nHYHATO\nreal\n\nHeel angle to\nHYHBDR\nreal\n\nHeavy ballast draught\nHYHEEL\nreal\n\nHeel\nHYHEEM\nreal\n\nCritical Heel moment\nHYHGHT\nreal\n\nHeight KG2 - KG1\nHYHGTH\nreal\n\nHeight\nHYHINC\nreal\n\nBalancing tolerance heel increment\nHYHMOM\nreal\n\nHorizontal Moment\nHYHOBM\nreal\n\nHog bending moment\nHYHOSA\nreal\n\nHog(+ve)/Sag(-ve)\nHYHWLE\nreal\n\nHeavy weights lever\nHYICGM\nreal\n\nInt Cr. GMf\nHYICKG\nreal\n\nInt Cr. KGf\nHYIL\nreal\n\nIL\nHYIMO\ninteger\n\nIMO Number\nHYIMST\nstring(120)\n\nImmersion status\nHYISCR\nstring(120)\n\nIntact stability criteria\nHYISTP\nstring(120)\n\nInner structure type\nHYIT\nreal\n\nIT\nHYKG\nreal\n\nKG\nHYKGF\nreal\n\nKGf\nHYKML\nreal\n\nKML\nHYKMT\nreal\n\nKMT\nHYKN\nreal\n\nKN\nHYKTHK\nreal\n\nKeel plate thickness\nHYLBHS\nstring(120)\n\nLongitudinal bulkhead(s)\nHYLBP\nreal\n\nLength between perpendiculars\nHYLCB\nreal\n\nLCB\nHYLCF\nreal\n\nLCF\nHYLCG\nreal\n\nLCG\nHYLGTH\nreal\n\nLength\nHYLISD\nreal\n\nLightest service draft (d0)\nHYLLID\nstring(120)\n\nID\nHYLOA\nreal\n\nLength over all\nHYLOAL\nstring(120)\n\nLoadline\nHYLSEP\nreal\n\nLongitudinal separation\nHYLSKG\nreal\n\nLightship KG\nHYLSW\nreal\n\nLightship weight\nHYLWAE\nreal\n\nAft extent\nHYLWFE\nreal\n\nFwd extent\nHYLWGT\nreal\n\nLightship weight\nHYLWIT\nstring(120)\n\nItem\nHYLWL\nreal\n\nLength in water line\nHYLWWA\nreal\n\nWeight aft\nHYLWWF\nreal\n\nWeight fwd\nHYMAXX\nreal\n\nMax X\nHYMAXY\nreal\n\nMax Y\nHYMAXZ\nreal\n\nMax Z\nHYMDMI\nreal\n\nMean draft at midships\nHYMINX\nreal\n\nMin X\nHYMINY\nreal\n\nMin Y\nHYMINZ\nreal\n\nMin Z\nHYMITR\ninteger\n\nMax number of iterations\nHYMNGR\nstring(120)\n\nManager\nHYMTC\nreal\n\nMTC\nHYMVCG\nreal\n\nMinimum VCG\nHYMVOL\nreal\n\nMoulded volume\nHYNBDR\nreal\n\nNormal ballast draught\nHYNTON\nreal\n\nNet tonnage\nHYNVSF\nreal\n\nneg ve shear force\nHYOFAP\nreal\n\nOrigin from AP\nHYOFNR\nstring(120)\n\nOfficial number\nHYOPHG\nreal\n\nOpening height\nHYOPNS\nstring(120)\n\nOpenings\nHYPASS\nstring(120)\n\nPass?\nHYPAWT\nreal\n\nA * wt\nHYPCTF\nreal\n\nPercentage full\nHYPDCK\nstring(120)\n\nDeck(s)\nHYPDIA\nreal\n\nPropeller diameter\nHYPERM\nreal\n\nPermeability\nHYPODC\nstring\n\nDownflood compartment\nHYPOID\nstring\n\nPosition ID\nHYPOLO\nstring(120)\n\nLocation\nHYPORE\nstring(120)\n\nPort of registry\nHYPOSA\nreal\n\nPosition 1\nHYPOSB\nreal\n\nPosition 2\nHYPOSI\nreal\n\nPosition\nHYPOSX\nreal\n\nPosition x\nHYPOSY\nreal\n\nPosition y\nHYPOSZ\nreal\n\nPosition z\nHYPOTP\ninteger\n\nPosition type\nHYPOXD\ninteger\n\nPositive x-direction\nHYPOYD\ninteger\n\nPositive y-direction\nHYPPSA\nreal\n\nPivot point swing angle\nHYPPTX\nreal\n\nPivot point x-pos\nHYPPTY\nreal\n\nPivot point y-pos\nHYPPTZ\nreal\n\nPivot point z-pos\nHYPRIM\nreal\n\nPropeller required immersion\nHYPRLA\nreal\n\nPropeller location fwd of AP\nHYPRP\nreal\n\np\nHYPRR\nreal\n\nr\nHYPRS\nreal\n\ns\nHYPRV\nreal\n\nv\nHYPRVW\nreal\n\np*r*v*wt\nHYPRWT\nreal\n\nwt\nHYPSHH\nreal\n\nPropeller shaft height\nHYPTHK\nreal\n\nShell plate thickness\nHYPVSF\nreal\n\npos ve shear force\nHYRAKE\nreal\n\nRake of keel\nHYRARE\nreal\n\nRequired Area\nHYREGI\nstring(120)\n\nRegion\nHYRFLR\nreal\n\nRise of floor\nHYRIDX\nreal\n\nRequired index\nHYRULE\nreal\n\nRule length\nHYSABM\nreal\n\nSag bending moment\nHYSARE\nreal\n\nShifted Area\nHYSBDL\nreal\n\nSubdivision Length (Ls)\nHYSBDR\nreal\n\nSlamming Draught Full Ballast at FP\nHYSCOR\nreal\n\nCorrection\nHYSDLE\nreal\n\nSubdivision length (Ls)\nHYSDLL\nreal\n\nSubdivision Load line (ds)\nHYSEDR\nreal\n\nSlamming draught empty ballast at FP\nHYSEPD\nreal\n\nDesign speed\nHYSFBD\nreal\n\nSummer Freeboard\nHYSHFO\nreal\n\nShearing force\nHYSHNA\nstring(120)\n\nShip Name\nHYSHTP\nstring(120)\n\nShip Type\nHYSLCG\nreal\n\nShifted LCG\nHYSLOP\nreal\n\nSlope\nHYSNOT\nstring(10)\n\nNote on setting and content\nHYSOUN\nreal\n\nSounding\nHYSPER\nreal\n\nPermeability\nHYSPPM\nreal\n\n% of max allowed\nHYSTAP\ninteger\n\nAP is at station\nHYSTAT\nreal\n\nStations\nHYSTCG\nreal\n\nShifted TCG\nHYSTFP\ninteger\n\nFP is at station\nHYSTGZ\ninteger\n\nStepped GZ curve\nHYSTOH\nreal\n\nStern overhang\nHYSULD\nreal\n\nSummer load draft\nHYSUZO\nstring(120)\n\nSub Zone\nHYSVAL\nreal(10)\n\ns-value\nHYSVCG\nreal\n\nShifted VCG\nHYTBHA\nstring(120)\n\nTransverse bulkhead aft\nHYTBHF\nstring(120)\n\nTransverse bulkhead fwd\nHYTCB\nreal\n\nTCB\nHYTCF\nreal\n\nTCF\nHYTCG\nreal\n\nTCG\nHYTEMP\nreal\n\nTemperature\nHYTFSM\nreal\n\nTotal free surface\nHYTHMO\nreal\n\nTrimmed Horizontal Moment\nHYTLIQ\nreal\n\nTotal hatch length inside L/4\nHYTMOM\nreal\n\nTransverse moment\nHYTORS\nreal\n\nTorsion moment\nHYTOWL\nreal\n\nTowing lever\nHYTPC\nreal\n\nTPC\nHYTRIM\nreal\n\nTrim\nHYTSEP\nreal\n\nTransverse separation\nHYTTOL\nreal\n\nTrim tolerance\nHYTURN\nreal\n\nTurning lever\nHYTVMO\nreal\n\nTrimmed Vertical Moment\nHYTYPE\nstring(120)\n\nType\nHYUHMO\nreal\n\nUntrimmed Horizontal Moment\nHYULKO\nreal\n\nUnder water line KG1\nHYULLA\nreal\n\nUllage\nHYUVMO\nreal\n\nUntrimmed Vertical Moment\nHYUWLA\nreal\n\nUnder water line area\nHYVARM\nreal\n\nVertical Area Moment\nHYVCB\nreal\n\nVCB\nHYVCG\nreal\n\nVCG\nHYVMOM\nreal\n\nVertical Moment\nHYVOID\nreal\n\nVoid depth\nHYVOLU\nreal\n\nVolume\nHYVSEP\nreal\n\nVertical separation\nHYVVAL\nreal\n\nv value\nHYWADE\nreal\n\nSea water density\nHYWDTH\nreal\n\nWidth\nHYWEIT\nreal\n\nWeight\nHYWEMP\nreal\n\nWeight empty\nHYWGHT\nreal\n\nWeight\nHYWIND\nreal\n\nWind lever\nHYWLHG\nreal\n\nWater line heights\nHYWLLE\nreal\n\nWaterline length\nHYWLRA\nreal\n\nWL Radius\nHYWODH\nreal\n\nWater on deck height\nHYWODS\nreal\n\nWater on deck significant wave height\nHYWPA\nreal\n\nWPA\nHYWSA\nreal\n\nWSA\nHYWTSU\nreal\n\nWetted surface\nHYYAFT\nreal\n\ny-aft\nHYYANO\ninteger\n\nYard number\nHYYFWD\nreal\n\ny-fwd\nHYZONE\nstring(120)\n\nZone\nHZAXI\ndir\n\nhead Z axis\n\nAttribute Name\nData Type\nQualifier\nDescription\nHANEXP\npos\nHANCI expected position wrt the start of the COMPRE\nHANGLE\nreal\nHatching Angle\nHANICOFFSET\nreal(3)\nHANCI INTERNAL CACHED OFFSET\nHANICPOSITION\nreal(3)\nINTERNAL HANCI cached position\nHANOFFSET\npos\nHANCI cached position offset\nHANPOSITION\npos\nSupport cached position\nHASCLN\nlogical\nHas clones flag\nHAZARD\nstring(120)\nHazard\nHAZTYP\nstring(120)\nHazard Description\nHBLBOX\nreal(6)\nBlock box\nHBOR\nreal\nHead bore\nHCCNT\ninteger\nHeader/Extract list changes count\nHCNREF\nelement\nHullConnection reference\nHCOFG\npos\ncomputed hull item centre of gravity\nHCON\nword\nHead connection type\nHCORRO\nreal\nHead Corrosion\nHCREF\nelement(100)\nHead connections\nHDBREF\nelement\nGeneric Hull DB Ref\nHDCONN\nelement(500)\nList of elements connected to branch head\nHDIR\ndir\nHead direction\nHDIST\nreal\nHorizontal Distance\nHDMF\nelement(2)\nISODRAFT Reference Dimension attribute\nHDMT\nword(2)\nISODRAFT Reference Dimension attribute\nHDREF\nelement(500)\nList of attachment connected to attachment\nHDSHAP\nword\nBranch head duct shape\nHDUPLI\nelement(10000)\ninteger\nDuplicates of the current element (checking members)\nHEADCL\nreal\nHead Clearance\nHEADH\nreal\nHead duct height\nHEADRO\nreal\nHeadroom\nHEADW\nreal\nHead duct width\nHEATT\ninteger\nHeat Treatment\nHEIARR\nreal(10)\nHeight array\nHEID\nreal\nDefault Height value\nHEIF\nreal\nHeight attractor factor\nHEIG\nreal\nHeight\nHEIL\nreal(2)\nHeight limits (Min/Max)\nHEIS\nlogical\nHeight set flag - ignore Height values if FALSE\nHEND\nstring\nConnection at other end of HREF (HEAD or TAIL)\nHGHT\nreal\nHeight\nHGSIDE\nword\nHinge side\nHHBO\nreal\nHanger head bore\nHHBP\npos\nBottom of hanger head\nHHCO\nword\nHanger head connection type\nHHDR\ndir\nHanger head direction\nHHGR\nreal\nHanger head gradient\nHHOD\nreal\nHanger head outside diameter\nHHPO\npos\nHanger head position\nHHTP\npos\nTop of hanger head\nHIERARCHY\nelement(5000)\nStructural connections\nHIST\ninteger(120)\nattr\nHistory of sessions in which element or specified attribute were made\nHLCOLO\nstring\nHull Colour\nHLIS\nword(2000)\nList of all possible types in owning hierarchy\nHLSTREF\nelement\nHatching linestyle Reference\nHLSTYLE\ninteger\nHatching linestyle\nHMAV\nreal\nAverage humidity\nHMMA\nreal\nMaximum humidity\nHMMI\nreal\nMinimum humidity\nHNCKEY\ninteger\nHole Notch Cutout Key\nHNODEL\nelement(500)\nHnode list\nHOFFSE\nreal\nHatching Line Offset\nHOLDES\nstring(120)\nHole Designation\nHOLGRD\nlogical\nTrue if any hole in the part should be grinded\nHOLTYP\ninteger\nDetailing Model Hole Type\nHOOGEO\nreal(8)\nHook definition curve\nHOOPSP\nreal\nHoop Spacing\nHOOTYP\ninteger\nHook type\nHPATNO\ninteger\nHatch Pattern Number\nHPOS\npos\nHead position\nHPOSE\nreal\nEasting of head position\nHPOSN\nreal\nNorthing of head position\nHPOSU\nreal\nUpping of head position\nHPREF\nelement\nHead point reference\nHRCLE\nreal\nHANDRAIL CLEAR WIDTH\nHREF\nelement\nHead reference\nHREL\nlogical\nBranch Member Head relative flag (Router)\nHRJUSL\nword\nHandrail Justification Line\nHROBS\nreal\nHandrail Obstruction\nHROFF\nreal\nHandrail Offset\nHRSDIS\nreal\nHandrail Start Distance\nHRSF\nelement\nHatch ruleset reference\nHRSTAR\nreal\nHandrail Start Height\nHSARFA\nelement(500)\nHVACSpool arrive references\nHSEPAR\nreal\nHatching Line Separation\nHSLRFA\nelement(500)\nHVACSpool leave references\nHSPE\nelement\nHanger specification\nHSRFA\nreal\nComputed Hull item surface area\nHSRO\nelement\nHeadrod specification\nHSTU\nelement\nHead tube specification\nHSTYF\nelement\nHatch style reference\nHSVLD\nlogical\nHVACspool valid\nHTBO\nreal\nHanger tail bore\nHTBP\npos\nBottom of hanger tail\nHTCO\nword\nHanger tail connection type\nHTDR\ndir\nHanger tail direction\nHTGR\nreal\nHanger tail gradient\nHTOD\nreal\nHanger tail outside diameter\nHTPO\npos\nHanger tail position\nHTPREF\nelement\nTopology reference\nHTTP\npos\nTop of hanger tail\nHTYP\nword\nHanger type\nHUBRF\nelement\nReference to the hub location\nHULAPP\nlogical\nHull applicable Geometry\nHULCNT\ninteger\nSize of hull array/collection\nHULLDE\nlogical\nTrue if element is a hull design item\nHULLOB\nelement\nHull object reference\nHULLPR\nlogical\nTrue if element is a hull production item\nHULOC\nstring\nLocation\nHUMIDI\nreal\nDesign Humidity\nHUMIRR\nlogical\nTrue if mirrored in local v-axis\nHUMVW\nstring\nModel View\nHUREFL\nlogical\nReflected\nHUREPL\nelement\nReplica\nHUSYMM\nlogical\nSymmetrical\nHVOLU\nreal\nComputed Hull Item volume\nHWALLT\nreal\nHead wall thickness\nHWRF\nelement\nHead Working Point (Router)\nHYACTV\nreal\nActual value\nHYAEAP\nreal\nAft end of Ls aft of AP\nHYAIDX\nreal\nAttained index\nHYALKT\nreal\nAbove water line KG2\nHYAOPS\nstring(120)\nActive opening states\nHYARAT\nreal\nArea ratio\nHYASSE\ninteger\nAssessment\nHYAWLA\nreal\nAbove water line area\nHYBDAE\nreal\nAft extent of bay\nHYBDFE\nreal\nFwd extent of bay\nHYBEMO\nreal\nBending moment\nHYBHAT\nreal\nBreadth of hatch\nHYBHFC\nreal\nBulkhead factor\nHYBML\nreal\nBMl\nHYBMT\nreal\nBMt\nHYBPPM\nreal\n% of max allowed\nHYBRAD\nreal\nBilge radius\nHYBUIL\nstring(120)\nBuilder\nHYBVAL\nreal\nb value\nHYBWL\nreal\nBreadth in water line\nHYCAST\nstring(120)\nDamage case + state\nHYCB\nreal\nBlock coefficient\nHYCBWL\nreal\nBlock coefficient calc in water line\nHYCBX\nreal\nCB including volume for shell\nHYCLAN\nstring(120)\nClass Number\nHYCLET\nstring(120)\nCall letters\nHYCM\nreal\nMidship area coefficient\nHYCMWL\nreal\nMidship area coefficient calc in water line\nHYCOLR\ninteger\nColour\nHYCOMP\nelement\nCompartment\nHYCONA\nstring(120)\nCondition\nHYCONB\nstring(120)\nCondition\nHYCOND\nelement\nLoading condition\nHYCP\nreal\nPrismatic coefficient\nHYCPCA\nelement(125)\nCompartment category\nHYCPER\nreal\nProbabilistic permeability values\nHYCPID\nstring(120)\nCompartment ID\nHYCPNA\nstring(120)\nCompartment name\nHYCPWL\nreal\nPrismatic coefficient calc in water line\nHYCRCA\nstring(120)\nCritical case\nHYCRDA\nstring(120)\nDamage stability criteria\nHYCRIT\nstring(120)\nCriterion\nHYCRIV\nreal\nCritical value\nHYCRKG\nreal\nCritical KGf\nHYCROW\nreal\nCrowding lever\nHYCRPR\nstring(120)\nProbabilistic damage stability criteria\nHYCSTM\nstring(120)\nCustomer\nHYCTBT\nstring(120)\nBay Title\nHYCTCT\nelement\nContainer type\nHYCTNA\nstring(120)\nDescription\nHYCTNO\ninteger\nNumber of containers\nHYCTRM\nreal\nTrim\nHYCTTI\nstring\nLoading set title\nHYCTTR\nstring(120)\nTier\nHYCTTY\nstring(50)\nType\nHYCTYP\nstring(120)\nIntact/Damaged\nHYCVCG\nreal\nCritical VCG\nHYCVOL\nreal\nCargo volume\nHYCW\nreal\nWater plane area coefficient\nHYCWWL\nreal\nWater plane area coefficient calc in water line\nHYDAP\nreal\nDraft at AP\nHYDATP\nstring(120)\nDamage type\nHYDCID\nstring(120)\nDamage case\nHYDCMP\nelement\nDamaged compartments\nHYDECK\nreal\nDeck\nHYDEFW\nreal\nDeadweight Fresh water\nHYDEIM\nreal\nDeck edge immersion\nHYDENS\nreal\nDensity\nHYDESC\nstring(120)\nDescription\nHYDESD\nreal\nDesign draft moulded\nHYDESW\nreal\nDeadweight Salt water\nHYDFP\nreal\nDraft at FP\nHYDHGT\nreal\nHeight (H)\nHYDHMX\nreal\nHmax\nHYDIFW\nreal\nDisplacement Fresh water\nHYDISP\nreal\nDisplacement\nHYDISW\nreal\nDisplacement Salt water\nHYDLCF\nreal\nDraft at LCF\nHYDLOA\nstring(120)\nLoading condition\nHYDLOD\nreal\nDisplacement at load draft\nHYDMAX\nreal\nDraft marks aft x\nHYDMAZ\nreal\nDraft marks aft z\nHYDMCA\nelement\nDamage cases compartment is part of\nHYDMFX\nreal\nDraft marks fwd x\nHYDMFZ\nreal\nDraft marks fwd z\nHYDNAM\nstring(120)\nDescriptive name\nHYDOBU\nstring(120)\nDate of build\nHYDORI\nreal\nDistance from origin\nHYDOWN\nreal\nDownflood\nHYDPCA\nreal\nDepth of cargo\nHYDPTH\nreal\nDepth moulded\nHYDRAF\nreal\nDraft\nHYDRAM\nreal\nDraft aft at marks\nHYDRAP\nreal\nDraft AP\nHYDREF\nelement\nDamage case ref\nHYDRFM\nreal\nDraft fwd at marks\nHYDRFP\nreal\nDraft FP\nHYDS\nreal\nDS\nHYDTOL\nreal\nDraft tolerance\nHYDWTM\nreal\nDeadweight moment\nHYEFUL\nreal\nWeight full\nHYEVCG\nreal\nVCG Empty\nHYEXTR\nstring(120)\nHydrostatics calculated to extreme/moulded drafts\nHYFAGL\nstring(120)\nFlood angle\nHYFANG\nreal\nFlood angle\nHYFBDP\nreal\nFreeboard depth\nHYFBRD\nreal\nFreeboard\nHYFLAG\nstring(120)\nFlag\nHYFLKE\nreal\nFlat of keel\nHYFRAM\nelement\nFrames\nHYFRFR\ninteger\nFrom frame\nHYFRLE\nreal\nFreeboard length\nHYFRSP\nreal\nFrame spacing\nHYFRTY\nstring(120)\nFreeboard type\nHYFSC\nreal\nFSC\nHYFSM\nreal\nFree surface moment\nHYFVCG\nreal\nVCG Full\nHYGCMP\nelement\nCompartment\nHYGHGT\nreal\nHeight of water above grounding point\nHYGHIN\nreal\nStability calculations heel increment\nHYGHMO\nreal\nAllowable Grain Heeling Moment\nHYGIRD\nreal\nGirder depth\nHYGM\nreal\nGM\nHYGMT\nreal\nGMt\nHYGRAN\nreal\nGrain angle\nHYGTON\nreal\nGross tonnage\nHYGZ\nreal\nGZ\nHYGZAR\nreal\nArea\nHYGZMA\nreal\nMax GZ\nHYGZMD\nreal\nMax GZ at degrees\nHYGZRA\nreal\nGZ-range\nHYHABV\nreal\nHeight above\nHYHAFR\nreal\nHeel angle from\nHYHAMD\nreal\nHatch height over moulded depth\nHYHATO\nreal\nHeel angle to\nHYHBDR\nreal\nHeavy ballast draught\nHYHEEL\nreal\nHeel\nHYHEEM\nreal\nCritical Heel moment\nHYHGHT\nreal\nHeight KG2 - KG1\nHYHGTH\nreal\nHeight\nHYHINC\nreal\nBalancing tolerance heel increment\nHYHMOM\nreal\nHorizontal Moment\nHYHOBM\nreal\nHog bending moment\nHYHOSA\nreal\nHog(+ve)/Sag(-ve)\nHYHWLE\nreal\nHeavy weights lever\nHYICGM\nreal\nInt Cr. GMf\nHYICKG\nreal\nInt Cr. KGf\nHYIL\nreal\nIL\nHYIMO\ninteger\nIMO Number\nHYIMST\nstring(120)\nImmersion status\nHYISCR\nstring(120)\nIntact stability criteria\nHYISTP\nstring(120)\nInner structure type\nHYIT\nreal\nIT\nHYKG\nreal\nKG\nHYKGF\nreal\nKGf\nHYKML\nreal\nKML\nHYKMT\nreal\nKMT\nHYKN\nreal\nKN\nHYKTHK\nreal\nKeel plate thickness\nHYLBHS\nstring(120)\nLongitudinal bulkhead(s)\nHYLBP\nreal\nLength between perpendiculars\nHYLCB\nreal\nLCB\nHYLCF\nreal\nLCF\nHYLCG\nreal\nLCG\nHYLGTH\nreal\nLength\nHYLISD\nreal\nLightest service draft (d0)\nHYLLID\nstring(120)\nID\nHYLOA\nreal\nLength over all\nHYLOAL\nstring(120)\nLoadline\nHYLSEP\nreal\nLongitudinal separation\nHYLSKG\nreal\nLightship KG\nHYLSW\nreal\nLightship weight\nHYLWAE\nreal\nAft extent\nHYLWFE\nreal\nFwd extent\nHYLWGT\nreal\nLightship weight\nHYLWIT\nstring(120)\nItem\nHYLWL\nreal\nLength in water line\nHYLWWA\nreal\nWeight aft\nHYLWWF\nreal\nWeight fwd\nHYMAXX\nreal\nMax X\nHYMAXY\nreal\nMax Y\nHYMAXZ\nreal\nMax Z\nHYMDMI\nreal\nMean draft at midships\nHYMINX\nreal\nMin X\nHYMINY\nreal\nMin Y\nHYMINZ\nreal\nMin Z\nHYMITR\ninteger\nMax number of iterations\nHYMNGR\nstring(120)\nManager\nHYMTC\nreal\nMTC\nHYMVCG\nreal\nMinimum VCG\nHYMVOL\nreal\nMoulded volume\nHYNBDR\nreal\nNormal ballast draught\nHYNTON\nreal\nNet tonnage\nHYNVSF\nreal\nneg ve shear force\nHYOFAP\nreal\nOrigin from AP\nHYOFNR\nstring(120)\nOfficial number\nHYOPHG\nreal\nOpening height\nHYOPNS\nstring(120)\nOpenings\nHYPASS\nstring(120)\nPass?\nHYPAWT\nreal\nA * wt\nHYPCTF\nreal\nPercentage full\nHYPDCK\nstring(120)\nDeck(s)\nHYPDIA\nreal\nPropeller diameter\nHYPERM\nreal\nPermeability\nHYPODC\nstring\nDownflood compartment\nHYPOID\nstring\nPosition ID\nHYPOLO\nstring(120)\nLocation\nHYPORE\nstring(120)\nPort of registry\nHYPOSA\nreal\nPosition 1\nHYPOSB\nreal\nPosition 2\nHYPOSI\nreal\nPosition\nHYPOSX\nreal\nPosition x\nHYPOSY\nreal\nPosition y\nHYPOSZ\nreal\nPosition z\nHYPOTP\ninteger\nPosition type\nHYPOXD\ninteger\nPositive x-direction\nHYPOYD\ninteger\nPositive y-direction\nHYPPSA\nreal\nPivot point swing angle\nHYPPTX\nreal\nPivot point x-pos\nHYPPTY\nreal\nPivot point y-pos\nHYPPTZ\nreal\nPivot point z-pos\nHYPRIM\nreal\nPropeller required immersion\nHYPRLA\nreal\nPropeller location fwd of AP\nHYPRP\nreal\np\nHYPRR\nreal\nr\nHYPRS\nreal\ns\nHYPRV\nreal\nv\nHYPRVW\nreal\np*r*v*wt\nHYPRWT\nreal\nwt\nHYPSHH\nreal\nPropeller shaft height\nHYPTHK\nreal\nShell plate thickness\nHYPVSF\nreal\npos ve shear force\nHYRAKE\nreal\nRake of keel\nHYRARE\nreal\nRequired Area\nHYREGI\nstring(120)\nRegion\nHYRFLR\nreal\nRise of floor\nHYRIDX\nreal\nRequired index\nHYRULE\nreal\nRule length\nHYSABM\nreal\nSag bending moment\nHYSARE\nreal\nShifted Area\nHYSBDL\nreal\nSubdivision Length (Ls)\nHYSBDR\nreal\nSlamming Draught Full Ballast at FP\nHYSCOR\nreal\nCorrection\nHYSDLE\nreal\nSubdivision length (Ls)\nHYSDLL\nreal\nSubdivision Load line (ds)\nHYSEDR\nreal\nSlamming draught empty ballast at FP\nHYSEPD\nreal\nDesign speed\nHYSFBD\nreal\nSummer Freeboard\nHYSHFO\nreal\nShearing force\nHYSHNA\nstring(120)\nShip Name\nHYSHTP\nstring(120)\nShip Type\nHYSLCG\nreal\nShifted LCG\nHYSLOP\nreal\nSlope\nHYSNOT\nstring(10)\nNote on setting and content\nHYSOUN\nreal\nSounding\nHYSPER\nreal\nPermeability\nHYSPPM\nreal\n% of max allowed\nHYSTAP\ninteger\nAP is at station\nHYSTAT\nreal\nStations\nHYSTCG\nreal\nShifted TCG\nHYSTFP\ninteger\nFP is at station\nHYSTGZ\ninteger\nStepped GZ curve\nHYSTOH\nreal\nStern overhang\nHYSULD\nreal\nSummer load draft\nHYSUZO\nstring(120)\nSub Zone\nHYSVAL\nreal(10)\ns-value\nHYSVCG\nreal\nShifted VCG\nHYTBHA\nstring(120)\nTransverse bulkhead aft\nHYTBHF\nstring(120)\nTransverse bulkhead fwd\nHYTCB\nreal\nTCB\nHYTCF\nreal\nTCF\nHYTCG\nreal\nTCG\nHYTEMP\nreal\nTemperature\nHYTFSM\nreal\nTotal free surface\nHYTHMO\nreal\nTrimmed Horizontal Moment\nHYTLIQ\nreal\nTotal hatch length inside L/4\nHYTMOM\nreal\nTransverse moment\nHYTORS\nreal\nTorsion moment\nHYTOWL\nreal\nTowing lever\nHYTPC\nreal\nTPC\nHYTRIM\nreal\nTrim\nHYTSEP\nreal\nTransverse separation\nHYTTOL\nreal\nTrim tolerance\nHYTURN\nreal\nTurning lever\nHYTVMO\nreal\nTrimmed Vertical Moment\nHYTYPE\nstring(120)\nType\nHYUHMO\nreal\nUntrimmed Horizontal Moment\nHYULKO\nreal\nUnder water line KG1\nHYULLA\nreal\nUllage\nHYUVMO\nreal\nUntrimmed Vertical Moment\nHYUWLA\nreal\nUnder water line area\nHYVARM\nreal\nVertical Area Moment\nHYVCB\nreal\nVCB\nHYVCG\nreal\nVCG\nHYVMOM\nreal\nVertical Moment\nHYVOID\nreal\nVoid depth\nHYVOLU\nreal\nVolume\nHYVSEP\nreal\nVertical separation\nHYVVAL\nreal\nv value\nHYWADE\nreal\nSea water density\nHYWDTH\nreal\nWidth\nHYWEIT\nreal\nWeight\nHYWEMP\nreal\nWeight empty\nHYWGHT\nreal\nWeight\nHYWIND\nreal\nWind lever\nHYWLHG\nreal\nWater line heights\nHYWLLE\nreal\nWaterline length\nHYWLRA\nreal\nWL Radius\nHYWODH\nreal\nWater on deck height\nHYWODS\nreal\nWater on deck significant wave height\nHYWPA\nreal\nWPA\nHYWSA\nreal\nWSA\nHYWTSU\nreal\nWetted surface\nHYYAFT\nreal\ny-aft\nHYYANO\ninteger\nYard number\nHYYFWD\nreal\ny-fwd\nHYZONE\nstring(120)\nZone\nHZAXI\ndir\nhead Z axis\n\n\n"}
{"Headers": "Attribute I", "Content": "IAKEY\ninteger\n\nInteger attribute key\nIALIGN\ninteger\n\nInteger vertical alignment\nIBLNAM\nstring\n\nName of idealised block\nICAT\nelement\n\nInsulation catalogue reference\nICLASS\nstring(120)\n\nInterference class\nICLMO\ninteger\n\nCentreline mode as integer\nICMPID\ninteger\n\nInstance component identity\nICON\nstring(120)\n\nICON\nICONL\nstring(120)\n\nICONL\nICONN\ninteger\n\nCOMMS connection type (0/1 = on/off-line)\nICONS\nstring(120)\n\nICONS\nICOTYP\nstring(300)\n\nIcon used for element\nICURF\ninteger\n\nInteger curve fitting code: 1 default, 2 cubicfit\nIDENT\nstring\n\nPanel identification string\nIDET\nelement\n\nInsulation detail text reference\nIDFLA\ninteger\n\nInteger radial dimension type flag\nIDLABL\nreal\n\nLength of label idle movement\nIDLELN\nreal\n\nLength of idle movement\nIDLFAC\nreal\n\nIdle movement factor\nIDLFG\ninteger\n\nInteger linear/angular dimension line flag\nIDLIEV\nelement(10000)\n\nEvaluated list of idlist elements\nIDLL\nreal(3)\n\nBurning idle length\nIDLLEN\nreal(2)\n\nNon-burning idle length\nIDLN\nelement\n\nDrawlist name reference\nIDLX\nstring(120)\n\nDrawlist name (as text)\nIDNM\nelement\n\nDesign data or catalogue component\nIDNX\nstring(120)\n\nDesign data or catalogue component (as text)\nIDPLAN\nstring(20)\n\nID Plane\nIDPREF\nstring(20)\n\nID Prefix\nIDRT\nstring(2000)\n\nInsulation detail RTEXT\nIDSPU\ninteger\n\nSpecified unique identifier\nIDST\nstring(2000)\n\nInsulation detail STEXT\nIDSTY\ninteger\n\nInteger radial dimension style flag\nIDTAN\ninteger\n\nInteger dimension text angle flag\nIDTANA\ninteger\n\nInteger dim. text angle flag style angular\nIDTANL\ninteger\n\nInteger dim. text angle flag style linear\nIDTANR\ninteger\n\nInteger dim. text angle flag style radiant\nIDTER\ninteger\n\nInteger dimension terminator code\nIDTFL\ninteger\n\nInteger dimension text radius flag\nIDTT\nstring(2000)\n\nInsulation detail TTEXT\nIDTUL\ninteger\n\nInteger dimension text underlining flag\nIFCUID\nstring(160)\n\nUniversally unique identifier from external sources (in IFC format)\nIFTER\ninteger\n\nInteger first dimension terminator code\nIGAP\nreal\n\nIntermediate offset distance\nIGNBRK\nlogical\n\nIgnore isometric spec break\nIGNDUN\nlogical\n\nIgnore DUnion flag\nIJUST\ninteger\n\nInteger justification\nILPBUA\nstring(120)\n\nReturn Integrator Build Area derived from Area Limit Point Labels\nILPDLB\nstring(50)\n\nIntegrator Area Limit Point downstream label\nILPOFF\nreal\n\nIntegrator Area Limit Point offset\nILPPOI\ninteger\n\nIntegrator Area Limit Point position\nILPSCH\nelement\n\nIntegrator Area Limit Point schematic element\nILPULB\nstring(50)\n\nIntegrator Area Limit Point upstream label\nILSHA\ninteger\n\nLeader shape code\nILTER\ninteger\n\nInteger label terminator code\nIMAT\nelement\n\nInsulation material text reference\nIMGDAT\ninteger(8192)\n\nImage data\nIMGSCA\nreal\n\nImage scale\nIMPED\nstring(1000)\n\nImpedance\nIMXT\nstring(2000)\n\nInsulation material XTEXT\nIMYT\nstring(2000)\n\nInsulation material YTEXT\nIMZT\nstring(2000)\n\nInsulation material ZTEXT\nINCANG\nreal(100)\n\nInclination angles\nINCBOR\nreal\n\nInch Nominal Bore\nINCFLU\nelement(500)\n\nAdditional elements to include for flush\nINCL\nreal\n\nInclination angle\nINCPRO\nelement(500)\n\nAdditional elements to include for data propagation\nINCWRK\nlogical\n\nIncrement at working revision\nINFA\nstring(120)\n\nClient info - Project Name\nINFB\nstring(120)\n\nComment - Project Message\nINFG\nlogical\n\nInsulation flag\nINFOTE\nstring(120)\n\nInfotext\nINHSRC\nelement\nattr\nInherited source att\nINIVAL\nelement\n\nInitial Value\nINLEN\nreal\n\nInsulation length\nINMTRF\nelement\n\nINSMAT Reference\nINNSHD\nreal\n\nInner sheath diameter\nINPINDEN\nreal\n\nInsulation pin density (Area)\nINPINLEN\nreal\n\nPin length\nINPINT\nstring(120)\n\nInsulation pin type\nINPREF\nelement(100)\n\nInstallation point reference\nINPRTR\nelement\n\nInside paint reference\nINRE\nelement\n\nInsulation reference\nINRF\nelement\n\nArray of Inventory Items\nINSARE\nreal\n\nInsulation requirement area\nINSC\nstring(120)\n\nInspection schedule\nINSCOL\nstring(120)\n\nInsulation colour\nINSHOL\nlogical\n\nInsert hole\nINSL\nlogical\n\nDRAFT user defined symbol insulation flag\nINSLEN\nreal(200)\n\nInstallation length\nINSLEV\nreal\n\nInsulation level\nINSMETHOD\nstring(240)\n\nInstallation method of cable\nINSMTL\nelement\n\nInsulation material\nINSRADIUS\nreal\n\nInside Radius\nINSREF\nelement\n\nRaw material instance reference\nINSTLVEL\nstring(240)\n\nInstallation level of cable\nINSTNC\nstring\n\nBracket instance name\nINSTOPTIONS\nstring(2000)\n\nInstallation Options\nINSURE\nelement\n\nReference to a INSCMP element\nINSUTY\nstring(120)\n\nInsulation type\nINSYST\nelement(500)\n\nReference Array of all SYSGRPs Elements\nINTEMP\nreal\n\nInsulation temperature\nINTHK\nreal\n\nInsulation thickness\nINTSEN\nlogical\n\nInstallation Sense - true if clockwise\nINTY\nword\n\nInventory item type\nINUDTG\nlogical\nelemtype\nIs in Udtg\nINUNIQ\nlogical\n\nFlag to notify if attribute is used in uniqueness\nINVF\nelement(500)\n\nArray of Inventory Items\nINVI\nlogical(500)\n\nVisibility state\nINVRADIUS\nlogical\n\nInvalid Radius\nINVREF\nlogical\nattr\nT/F on attributes that are invalid references\nIOCOD\ninteger\n\nHashed origin code\nIPAR\nreal(30)\n\nParameters of the insulation catalogue component\nIPATNAM\ninteger\n\nInteger pattern Name\nIPJUST\ninteger\n\nInteger pjustification\nIPMOD\ninteger\n\nPlane mode as integer\nIPRBLN\ninteger\n\nInteger primitive blanking flag\nIPRE\nreal\n\nInternal pressure\nIPTAN\ninteger\n\nInteger projection line text angle flag\nIRCOD\ninteger\n\nInteger direction of region vertical on sheet\nIRNO\nstring\n\nISO-IR number\nISALLO\nlogical\n\nTrue if database is allocated at this location\nISCHGD\nlogical\n\nTrue if hull model is modified/changed\nISCOPY\nlogical\n\nTrue if a copy DB\nISDBFR\nlogical\n\nTrue if database is foreign\nISDBPR\nlogical\n\nTrue if database is primary for global working\nISDRDB\nlogical\n\nTrue if database has drawings\nISECPT\npos\nword, integer\nIntersection point\nISENS\ninteger\n\nInteger sense\nISEXAP\nlogical\n\nTrue if extract ancestry is primary here\nISEXCP\nlogical\n\nTrue if all extract children are primary here\nISEXFP\nlogical\n\nTrue if extract family is primary here\nISEXMP\nlogical\n\nTrue if extract master is primary here\nISEXOP\nlogical\n\nTrue if extract owner is primary here\nISEXTR\nlogical\n\nTrue if an extract\nISFOR\nlogical\n\nTrue if database is foreign\nISHMTL\nelement\n\nInner sheath material\nISIDES\ninteger\n\nFrame side visibility\nISKEYDB\nlogical\n\nDoes ukey incorporate DB number\nISLNKD\nlogical\n\nTrue if database may have Linked documents\nISLOADED\nlogical\n\nTrue if Sheet is loaded\nISMAST\nlogical\n\nTrue if a Master DB, i.e. top level extract\nISNAMED\nlogical\n\nTrue if element is named\nISOHIDDEN\nlogical\n\nIsohidden flag\nISOLTD\nlogical\n\nA flag determining whether an element is to be isolated from cloning updates.\nISPE\nelement\n\nInsulation spec reference\nISPICF\nlogical\n\nPicture has File\nISPR\nelement\n\nInsulation specification component reference\nISPRIM\nlogical\n\nTrue if database is primary at this location\nISSEXT\nelement(20)\n\nStates to issue extracts\nISSTENDATUM\nlogical\n\nIs start ENDATUM; order depending on owned FIXING\nISSUE\nlogical\n\nTrue if drawing has been issued\nISUPGD\nlogical\n\nTrue if Upgrade is required for DB\nISWORK\nlogical\n\nTrue if a working extract\nITCOD\ninteger\n\nHashed origin code\nITLE\nreal\n\nLength of implied tube\nITMTBL\ninteger(2000)\n\nTable linking AITEMS elements to piping components\nITPS\npos\n\nPosition of implied tube\nITXALIGN\ninteger\n\nInteger text vertical alignment\nIVTYP\ninteger\n\nInteger type of design view\nIWDORF\nelement(1500)\n\nWeld owners attribute on IWELD elements\nIWDOWN\ninteger(8)\n\nTable linking IWELD elements to piping components\n\nAttribute Name\nData Type\nQualifier\nDescription\nIAKEY\ninteger\nInteger attribute key\nIALIGN\ninteger\nInteger vertical alignment\nIBLNAM\nstring\nName of idealised block\nICAT\nelement\nInsulation catalogue reference\nICLASS\nstring(120)\nInterference class\nICLMO\ninteger\nCentreline mode as integer\nICMPID\ninteger\nInstance component identity\nICON\nstring(120)\nICON\nICONL\nstring(120)\nICONL\nICONN\ninteger\nCOMMS connection type (0/1 = on/off-line)\nICONS\nstring(120)\nICONS\nICOTYP\nstring(300)\nIcon used for element\nICURF\ninteger\nInteger curve fitting code: 1 default, 2 cubicfit\nIDENT\nstring\nPanel identification string\nIDET\nelement\nInsulation detail text reference\nIDFLA\ninteger\nInteger radial dimension type flag\nIDLABL\nreal\nLength of label idle movement\nIDLELN\nreal\nLength of idle movement\nIDLFAC\nreal\nIdle movement factor\nIDLFG\ninteger\nInteger linear/angular dimension line flag\nIDLIEV\nelement(10000)\nEvaluated list of idlist elements\nIDLL\nreal(3)\nBurning idle length\nIDLLEN\nreal(2)\nNon-burning idle length\nIDLN\nelement\nDrawlist name reference\nIDLX\nstring(120)\nDrawlist name (as text)\nIDNM\nelement\nDesign data or catalogue component\nIDNX\nstring(120)\nDesign data or catalogue component (as text)\nIDPLAN\nstring(20)\nID Plane\nIDPREF\nstring(20)\nID Prefix\nIDRT\nstring(2000)\nInsulation detail RTEXT\nIDSPU\ninteger\nSpecified unique identifier\nIDST\nstring(2000)\nInsulation detail STEXT\nIDSTY\ninteger\nInteger radial dimension style flag\nIDTAN\ninteger\nInteger dimension text angle flag\nIDTANA\ninteger\nInteger dim. text angle flag style angular\nIDTANL\ninteger\nInteger dim. text angle flag style linear\nIDTANR\ninteger\nInteger dim. text angle flag style radiant\nIDTER\ninteger\nInteger dimension terminator code\nIDTFL\ninteger\nInteger dimension text radius flag\nIDTT\nstring(2000)\nInsulation detail TTEXT\nIDTUL\ninteger\nInteger dimension text underlining flag\nIFCUID\nstring(160)\nUniversally unique identifier from external sources (in IFC format)\nIFTER\ninteger\nInteger first dimension terminator code\nIGAP\nreal\nIntermediate offset distance\nIGNBRK\nlogical\nIgnore isometric spec break\nIGNDUN\nlogical\nIgnore DUnion flag\nIJUST\ninteger\nInteger justification\nILPBUA\nstring(120)\nReturn Integrator Build Area derived from Area Limit Point Labels\nILPDLB\nstring(50)\nIntegrator Area Limit Point downstream label\nILPOFF\nreal\nIntegrator Area Limit Point offset\nILPPOI\ninteger\nIntegrator Area Limit Point position\nILPSCH\nelement\nIntegrator Area Limit Point schematic element\nILPULB\nstring(50)\nIntegrator Area Limit Point upstream label\nILSHA\ninteger\nLeader shape code\nILTER\ninteger\nInteger label terminator code\nIMAT\nelement\nInsulation material text reference\nIMGDAT\ninteger(8192)\nImage data\nIMGSCA\nreal\nImage scale\nIMPED\nstring(1000)\nImpedance\nIMXT\nstring(2000)\nInsulation material XTEXT\nIMYT\nstring(2000)\nInsulation material YTEXT\nIMZT\nstring(2000)\nInsulation material ZTEXT\nINCANG\nreal(100)\nInclination angles\nINCBOR\nreal\nInch Nominal Bore\nINCFLU\nelement(500)\nAdditional elements to include for flush\nINCL\nreal\nInclination angle\nINCPRO\nelement(500)\nAdditional elements to include for data propagation\nINCWRK\nlogical\nIncrement at working revision\nINFA\nstring(120)\nClient info - Project Name\nINFB\nstring(120)\nComment - Project Message\nINFG\nlogical\nInsulation flag\nINFOTE\nstring(120)\nInfotext\nINHSRC\nelement\nattr\nInherited source att\nINIVAL\nelement\nInitial Value\nINLEN\nreal\nInsulation length\nINMTRF\nelement\nINSMAT Reference\nINNSHD\nreal\nInner sheath diameter\nINPINDEN\nreal\nInsulation pin density (Area)\nINPINLEN\nreal\nPin length\nINPINT\nstring(120)\nInsulation pin type\nINPREF\nelement(100)\nInstallation point reference\nINPRTR\nelement\nInside paint reference\nINRE\nelement\nInsulation reference\nINRF\nelement\nArray of Inventory Items\nINSARE\nreal\nInsulation requirement area\nINSC\nstring(120)\nInspection schedule\nINSCOL\nstring(120)\nInsulation colour\nINSHOL\nlogical\nInsert hole\nINSL\nlogical\nDRAFT user defined symbol insulation flag\nINSLEN\nreal(200)\nInstallation length\nINSLEV\nreal\nInsulation level\nINSMETHOD\nstring(240)\nInstallation method of cable\nINSMTL\nelement\nInsulation material\nINSRADIUS\nreal\nInside Radius\nINSREF\nelement\nRaw material instance reference\nINSTLVEL\nstring(240)\nInstallation level of cable\nINSTNC\nstring\nBracket instance name\nINSTOPTIONS\nstring(2000)\nInstallation Options\nINSURE\nelement\nReference to a INSCMP element\nINSUTY\nstring(120)\nInsulation type\nINSYST\nelement(500)\nReference Array of all SYSGRPs Elements\nINTEMP\nreal\nInsulation temperature\nINTHK\nreal\nInsulation thickness\nINTSEN\nlogical\nInstallation Sense - true if clockwise\nINTY\nword\nInventory item type\nINUDTG\nlogical\nelemtype\nIs in Udtg\nINUNIQ\nlogical\nFlag to notify if attribute is used in uniqueness\nINVF\nelement(500)\nArray of Inventory Items\nINVI\nlogical(500)\nVisibility state\nINVRADIUS\nlogical\nInvalid Radius\nINVREF\nlogical\nattr\nT/F on attributes that are invalid references\nIOCOD\ninteger\nHashed origin code\nIPAR\nreal(30)\nParameters of the insulation catalogue component\nIPATNAM\ninteger\nInteger pattern Name\nIPJUST\ninteger\nInteger pjustification\nIPMOD\ninteger\nPlane mode as integer\nIPRBLN\ninteger\nInteger primitive blanking flag\nIPRE\nreal\nInternal pressure\nIPTAN\ninteger\nInteger projection line text angle flag\nIRCOD\ninteger\nInteger direction of region vertical on sheet\nIRNO\nstring\nISO-IR number\nISALLO\nlogical\nTrue if database is allocated at this location\nISCHGD\nlogical\nTrue if hull model is modified/changed\nISCOPY\nlogical\nTrue if a copy DB\nISDBFR\nlogical\nTrue if database is foreign\nISDBPR\nlogical\nTrue if database is primary for global working\nISDRDB\nlogical\nTrue if database has drawings\nISECPT\npos\nword, integer\nIntersection point\nISENS\ninteger\nInteger sense\nISEXAP\nlogical\nTrue if extract ancestry is primary here\nISEXCP\nlogical\nTrue if all extract children are primary here\nISEXFP\nlogical\nTrue if extract family is primary here\nISEXMP\nlogical\nTrue if extract master is primary here\nISEXOP\nlogical\nTrue if extract owner is primary here\nISEXTR\nlogical\nTrue if an extract\nISFOR\nlogical\nTrue if database is foreign\nISHMTL\nelement\nInner sheath material\nISIDES\ninteger\nFrame side visibility\nISKEYDB\nlogical\nDoes ukey incorporate DB number\nISLNKD\nlogical\nTrue if database may have Linked documents\nISLOADED\nlogical\nTrue if Sheet is loaded\nISMAST\nlogical\nTrue if a Master DB, i.e. top level extract\nISNAMED\nlogical\nTrue if element is named\nISOHIDDEN\nlogical\nIsohidden flag\nISOLTD\nlogical\nA flag determining whether an element is to be isolated from cloning updates.\nISPE\nelement\nInsulation spec reference\nISPICF\nlogical\nPicture has File\nISPR\nelement\nInsulation specification component reference\nISPRIM\nlogical\nTrue if database is primary at this location\nISSEXT\nelement(20)\nStates to issue extracts\nISSTENDATUM\nlogical\nIs start ENDATUM; order depending on owned FIXING\nISSUE\nlogical\nTrue if drawing has been issued\nISUPGD\nlogical\nTrue if Upgrade is required for DB\nISWORK\nlogical\nTrue if a working extract\nITCOD\ninteger\nHashed origin code\nITLE\nreal\nLength of implied tube\nITMTBL\ninteger(2000)\nTable linking AITEMS elements to piping components\nITPS\npos\nPosition of implied tube\nITXALIGN\ninteger\nInteger text vertical alignment\nIVTYP\ninteger\nInteger type of design view\nIWDORF\nelement(1500)\nWeld owners attribute on IWELD elements\nIWDOWN\ninteger(8)\nTable linking IWELD elements to piping components\n\n\n"}
{"Headers": "Attribute J", "Content": "JBLIST\nelement(500)\n\nJunction boxes list\nJDIST\nreal\n\nConnector jumping distance\nJFRE\nlogical\n\nIf YES attached section alignment may change\nJLIN\nword\n\nJoining line\nJLNE\nword\n\nJoining line end\nJLNS\nword\n\nJoining line start\nJMAX\ninteger\n\nMaximum joint number in current spool drawing\nJNTBEV\nreal(2)\n\nJoint part bevel code\nJNTC\ninteger\n\nJoint Code\nJNTCOM\nstring(300)\n\nWelded joint comment\nJNTNAM\nstring(26)\n\nWelded joint name\nJNTNUMBER\ninteger\n\nJoint number\nJNTORF\nelement(1500)\n\nJoint owners attribute on IJOINT elements\nJNTOWN\ninteger(8)\n\nTable linking IJOINT elements to piping components\nJNTREF\nelement\ninteger\nReturn reference from Ppoint to ijoint element\nJNTTHK\nreal(2)\n\nJoint part thickness\nJNTTSL\nreal\n\nTotal welded joint suspension length\nJNTTWL\nreal\n\nTotal welded joint length\nJNTTYP\nstring(26)\n\nWelded joint type\nJNUM\ninteger(2)\n\nOld spooler joint number\nJOIE\nelement\n\nEnd joint\nJOIP\nword(2)\n\nOld spooler joint number prefix\nJOIS\nelement\n\nStart joint\nJSONSERVICEID\nstring(120)\n\nJSON service ID of the uploaded project in Dabacon\nJSPOSE\npos\n\nJustifications End point position\nJSPOSS\npos\n\nJustifications Start point position\nJUMGLY\ninteger\n\nJumping Glyph\nJUSL\nword\n\nJustification Pline\nJUST\nstring\n\nJustification\n\nAttribute Name\nData Type\nQualifier\nDescription\nJBLIST\nelement(500)\nJunction boxes list\nJDIST\nreal\nConnector jumping distance\nJFRE\nlogical\nIf YES attached section alignment may change\nJLIN\nword\nJoining line\nJLNE\nword\nJoining line end\nJLNS\nword\nJoining line start\nJMAX\ninteger\nMaximum joint number in current spool drawing\nJNTBEV\nreal(2)\nJoint part bevel code\nJNTC\ninteger\nJoint Code\nJNTCOM\nstring(300)\nWelded joint comment\nJNTNAM\nstring(26)\nWelded joint name\nJNTNUMBER\ninteger\nJoint number\nJNTORF\nelement(1500)\nJoint owners attribute on IJOINT elements\nJNTOWN\ninteger(8)\nTable linking IJOINT elements to piping components\nJNTREF\nelement\ninteger\nReturn reference from Ppoint to ijoint element\nJNTTHK\nreal(2)\nJoint part thickness\nJNTTSL\nreal\nTotal welded joint suspension length\nJNTTWL\nreal\nTotal welded joint length\nJNTTYP\nstring(26)\nWelded joint type\nJNUM\ninteger(2)\nOld spooler joint number\nJOIE\nelement\nEnd joint\nJOIP\nword(2)\nOld spooler joint number prefix\nJOIS\nelement\nStart joint\nJSONSERVICEID\nstring(120)\nJSON service ID of the uploaded project in Dabacon\nJSPOSE\npos\nJustifications End point position\nJSPOSS\npos\nJustifications Start point position\nJUMGLY\ninteger\nJumping Glyph\nJUSL\nword\nJustification Pline\nJUST\nstring\nJustification\n\n\n"}
{"Headers": "Attribute K", "Content": "KNCKL\nelement\n\nSymbolic kuckle line style reference\nKNUANG\nreal\n\nKnuckle angle\nKNUCKL\nlogical\n\nTrue if knuckled\n\nAttribute Name\nData Type\nQualifier\nDescription\nKNCKL\nelement\nSymbolic kuckle line style reference\nKNUANG\nreal\nKnuckle angle\nKNUCKL\nlogical\nTrue if knuckled\n\n\n"}
{"Headers": "Attribute L", "Content": "LAAREF\nelement\n\nLaser Area reference\nLABDIR\nstring(120)\n\nName of attribute (or pseudo) to be used for label along direction\nLABOFFS\nreal(3)\n\nLabel offset\nLABPOS\npos\n\nLabel position\nLABSID\nstring(120)\n\nName of attribute (or pseudo) to be used for label side direction\nLABST\ninteger\n\nNumber of starts for label signing\nLACR\nlogical\n\nAccess Control on/off switch\nLACTIV\nlogical\n\nTrue if selectable : false = limbospec\nLACTYP\nstring(32)\n\nLabelled action\nLADCOL\ninteger\n\nLaser Drawing colour\nLADRES\ninteger\n\nLaser Drawing Resolution (dpi)\nLADRGB\ninteger(4)\n\nRGB laser drawing colour\nLADRGP\ninteger(4)\n\nRGB laser drawing colour physical\nLADSTY\ninteger\n\nLaser Drawing Style\nLALCAB\nelement(500)\n\nList arriving leaving cables on attached point\nLALLAN\nreal\n\nLeave Ppoint allowed angle\nLAMDIS\nlogical\n\nTrue if Lam Displ\nLAMINA\nstring(12)\n\nName of first laminate code\nLAMINB\nstring(12)\n\nName of second laminate code\nLAMWTH\nreal\n\nWidth of laminate\nLANGUAGE\nstring(35)\n\nLanguage tag as described in BCP 47 - Tags for Identifying Languages(http://tools.ietf.org/html/bcp47)\nLANREF\nelement\n\nLinked annotation element reference\nLASTM\nstring(120)\nattr\nDate of last modification\nLAUTHU\nlogical\n\nLogin Authentication on/off switch\nLAVORF\nelement\n\nReference to laser volume set, containing the complete definition of the laser representation\nLAXE\nori\n\nLocal axes\nLAYARF\nelement\n\nAnnotation Layer ruleset reference\nLAYDRF\nelement\n\nDesign Layer ruleset reference\nLAYMOD\ninteger\n\nBundle layout mode\nLAYMOT\nstring(100)\ninteger\nLayout mode text\nLAYOUT\nlogical\n\nTRUE if element is layout mode\nLAYTBF\nelement\n\nLayer Table reference\nLBBORE\nlogical\n\nTRUE if Minor/Branch bore is in nominal bore table\nLBFACT\nreal\n\nLabelling along factor\nLBGIMG\nlogical\n\nBackground image flag\nLBLANG\nreal\n\nLabelling angle\nLBLDIR\ninteger\n\nLabelling direction\nLBLHGT\nreal\n\nLabelling height\nLBLID\ninteger\n\nLabelling reference id\nLBLIND\nlogical\n\nBlind hole flag\nLBLMIR\ninteger\n\nLabelling reflection code\nLBLPOS\nreal(2)\n\nLabelling definition point\nLBLSID\ninteger\n\nLabelling side of part\nLBLTXT\nstring(300)\n\nLabelled text\nLBOP\npos\n\nBottom of leave pipe\nLBOR\nreal\n\nLeave bore\nLBPOME\nstring(32)\n\nLabelling position method\nLBRINF\ninteger\n\nReference information for labelling\nLBRPOS\nreal(2)\n\nLabelling reference point\nLBSPOS\ninteger\n\nLabelled symbol text position\nLBSTRF\nelement\n\nLabel style reference\nLBTRAN\nlogical(3)\n\nTrue if rotation, translation and reflection is allowed\nLBTVAL\nreal(2)\n\nLabelling at intervals\nLBTYPE\nstring(32)\n\nReference information for labelling\nLCAS\ninteger\n\nLoad case number\nLCHA\nlogical\n\nChain flag\nLCHKDA\ndatetime(2)\n\nDate of last pipe fabrication consistency check\nLCIRCR\nreal(8)\n\nLeast circumscribed rectangle\nLCKNUT\nstring(32)\n\nDetailing Bolt Set Lock Nut\nLCKPSW\nlogical\n\nLock passwords for general users\nLCLAIM\nlogical\n\nAccess Control Claim flag\nLCLM\nlogical\n\nTrue if element is claimed\nLCLMH\nlogical\n\nTrue if element and hierarchy claimed\nLCLOSE\nlogical\n\nIs this entity closed?\nLCNFA\nelement(500)\n\nArray of elements with local names\nLCON\nword\n\nLeave connection type\nLCONFL\nlogical\n\nLocal Connection Point Flag\nLCONSU\nlogical\n\nConsumer Extract database flag, can be refreshed when read-only\nLCORRO\nreal\n\nLeave corrosion allowance\nLCPOVWRITE\nlogical\n\nLocation Overwrite DB Users policy flag\nLCPREF\nelement\n\nLinked connection point reference\nLCTROL\nlogical\n\nControlled DB Flag\nLCUTDI\ndir\n\nLower Extension Cutting Direction\nLDFLT\nlogical\n\nlogical default value for a UDA\nLDI\ndir\n\nLeave direction\nLDIAM\nreal\n\nLoop diameter\nLDIMPD\nreal(3)\n\nLinear Dimension Projected Direction Pseudo\nLDISP\nlogical\n\nDisplay property flag for design datasets: True if property is shown on form\nLDPR\nreal\nword\nLocal design dataset property\nLDRDIR\ndir\n\nLadder Direction\nLEAFS\nreal\n\nNumber of door leafs\nLEAHEI\nreal\n\nLeave height\nLEASHA\nword\n\nLeave PPoint Connection shape\nLEAV\ninteger\n\nLeave Ppoint\nLEAWID\nreal\n\nLeave width\nLEND\nlogical\n\nLine end\nLENDTI\ninteger\n\nTime out period for commands\nLENG\nreal\n\nLength\nLENINS\nreal\n\nInitial tube length inside bending machine.\nLENOUT\nreal\n\nInitial tube length outside bending machine\nLENSEG\nreal\n\nLength of segment\nLETTER\nstring(50)\n\nLetter\nLEVE\ninteger(2)\n\nDrawing level\nLEVENL\ninteger\n\nTime interval for Event Loop\nLEVRFA\nelement(100)\n\nReferences to levels serviced by stairwell\nLEXCES\nreal\n\nLeave excess for leave tube\nLEXREF\nelement\n\nDraw Linked External Reference\nLEXTNS\nreal\n\nLower Extension Length\nLFADIR\ndir\n\nFlight A Direction\nLFAOFFSET\nreal\n\nLanding Flight A Offset\nLFBDIR\ndir\n\nLanding Flight B Direction\nLFBOFFSET\nreal\n\nLanding Flight B Offset\nLFCOLG\ninteger\n\nGlabel style frame colour\nLFCOLO\ninteger\n\nLabel frame colour\nLFCONU\ninteger\n\nLabel frame colour number\nLFDP\nelement\nword\nLocal design dataset property\nLFGRGB\ninteger(4)\n\nRGB glabel style frame colour\nLFGRGP\ninteger(4)\n\nRGB glabel style frame colour physical\nLFPN\ninteger\n\nLabel frame pen\nLFRA\nlogical\n\nFrame flag\nLFRRGB\ninteger(4)\n\nRGB label frame colour\nLFRRGP\ninteger(4)\n\nRGB label frame colour physical\nLFSTREF\nelement\n\nLabel frame linestyle Reference\nLFSTYG\ninteger\n\nGLabel style frame line type\nLFSTYL\ninteger\n\nLabel frame linestyle\nLGAP\nreal\n\nLast offset distance\nLGOING\nreal(10)\n\nLower Tread Going\nLGRD\nreal\n\nLeave Ppoint gradient\nLGTYPC\nlogical\n\nGeneric type is closed flag\nLHBORE\nlogical\n\nTRUE if Major/Header bore is in nominal bore table\nLHEA\nlogical\n\nLogical head flag\nLHEI\nreal\n\nLetter height\nLHEITX\nstring(80)\n\nLetter height text\nLHIDE\nlogical\n\nHide flag for catalogue datasets: True if property is not shown on form\nLIGHTI\nreal\n\nLighting requirements\nLIMI\nreal(6)\n\nVolume of interest\nLIMNMS\nstringarray(1000)\n\nLimit names\nLIMNUM\ninteger\n\nOrder number of limit\nLIMREF\nelement(10)\n\nReference limit\nLINIT\nlogical\n\nLocation initialisation flag\nLINKRE\nelement\n\nLink reference\nLINKS\nelement(5000)\n\nLinked elements\nLINKSN\ninteger\n\nLinked session on parent extract\nLINKXR\nelement(1000)\n\nReferencing elements\nLISS\nlogical\n\nTrue if drawing has been issued\nLIST\nword(5000)\n\nList of all possible member types\nLISTD\nstringarray(2147483647)\n\nGeneric Text List Data Storage\nLLCL\nreal\n\nLeader line clearance\nLLCLTX\nstring(80)\n\nLeader line clearance text\nLLCOLG\ninteger\n\nGLabel style leader colour\nLLCOLO\ninteger\n\nLeader line colour\nLLCONU\ninteger\n\nLabel leader colour number\nLLDIAGRAMS\nstring(2000)\n\nLine list diagrams\nLLDMODE\ninteger\n\nLeader line dimension mode (Default, ByVStyle, Off, On)\nLLEA\nlogical\n\nLeader line flag\nLLENG\nreal\n\nLeave length\nLLENTRY\nlogical\n\nIs a line list entry - true or false\nLLFROM\nstring(2000)\n\nFrom column text for a line list\nLLGRGB\ninteger(4)\n\nRGB glabel style leader colour\nLLGRGP\ninteger(4)\n\nRGB glabel style leader colour physical\nLLIS\nword(2000)\n\nList of all possible types in member hierarchy\nLLNRGB\ninteger(4)\n\nRGB leader line colour\nLLNRGP\ninteger(4)\n\nRGB leader line colour physical\nLLPN\ninteger\n\nLabel leader pen\nLLSTREF\nelement\n\nLabel leader linestyle Reference\nLLSTYG\ninteger\n\nGLabel style leader line type\nLLSTYL\ninteger\n\nLeader line linestyle\nLLTBRANCH\nelement\n\nLine list tail branch\nLLTO\nstring(2000)\n\nTo column text for a line list\nLMAXTR\ninteger\n\nMaximum number of retries for command\nLMDREF\nelement(20)\n\nBack reference to demolition packages referencing laser survey\nLMDSES\ninteger(10)\n\nSession number of back reference to demolition packages referencing laser survey\nLMDSYN\nstring(700)\n\nSynchronisation state of AVEVA and laser survey databases\nLMERDL\nlogical\n\nEnable automatic merge of transaction db\nLMERFAILURE\ninteger\n\nNumber of days Failed commands persist in Trans dB\nLMERSUCCESS\ninteger\n\nNumber of days Successful commands persist in Trans dB\nLMERTI\nstring(120)\n\nFrequency of Auto Merge of Transaction DB\nLMIRR\nlogical\n\nTrue if Mirroring required\nLNAME\nstring(21)\n\nLocal name as stored on template\nLNDLEV\nreal(100)\n\nLanding levels from owning element\nLNFA\nelement(480)\n\nHidden Reference Array for linked Vertices\nLNGVAR\nlogical\n\nLanguage Variant, is attribute language variant. Applies to text attributes only.\nLNKALINVALID\nelement(100)\n\nAll invalid HANCI refs\nLNKALLARRAY\nelement(100)\n\nAll HANCI refs\nLNKCLS\nelement(500)\n\nClasses referencing a DocLink\nLNKDOC\nelement(500)\n\nDocLinks referring to element\nLNKELE\nelement(500)\n\nElements referencing a DocLink\nLNKIRARRAY\nelement(100)\n\nInvalid HANCI reference array attribute\nLNKPRP\nword\n\nTRUE if item pointed to by descriptor should be propagated by Global\nLNKREF\nelement\n\nReference internal document (drawing/sheet)\nLNKRFARRAY\nelement(100)\n\nHANCI reference array attribute\nLNKRX\nelement\n\nReference to first location of a link\nLNKRY\nelement\n\nReference to second location of a link\nLNKUSE\nword\n\nLink Descriptor Usage\nLNKVFARRAY\nlogical(10)\n\nIndividual support valid flags array attribute\nLNKWV\ninteger\n\nLink weighting value\nLNLST\nstring(2000)\n\nList of local names for current template\nLNOUPDATE\nlogical\n\nDB propagation suppressed flag\nLNPRXS\nelement(500)\n\nProxy items referring to element\nLNTP\nword\n\nLine type\nLOCA\nstring(120)\n\nLocation\nLOCDBR\nelement\n\nLocation Db Ref\nLOCID\nstring(3)\n\nLocation identifier\nLOCK\nlogical\n\nLogical flag which determines if the UDAs attribute values are locked\nLOCKID\nlogical\n\nLock Id\nLOCOLO\ninteger\n\nLoop line colour\nLOCPR\nelement(1000)\n\nList of LOCs Primary at location\nLOCRF\nelement\n\nLocation reference\nLOCRGB\ninteger(4)\n\nLoop RGB colour\nLOCRGP\ninteger(4)\n\nLoop RGB colour physical\nLOCTRC\nelement\n\nSymbolic local trace style reference\nLOCTYP\ninteger\n\nLocation\nLOD\nreal\n\nLeave Ppoint outside diameter\nLODIMG\nlogical\n\nOriginal image data flag\nLOEXTN\nreal\n\nLoop extension\nLOFF\nlogical\n\nOffline flag\nLOGEV\nlogical\n\nLogical value evaluation\nLOGFN\nstring(1024)\n\nCOMMS log file name\nLOGLV\ninteger\n\nCOMMS log file level of detail\nLOGMS\nlogical\n\nCOMMS log file active/inactive flag\nLOGXP\ninteger(500)\n\nLogical expression\nLOHE\nreal\n\nPLOOP height - from first PLOOP in owning panel\nLOOS\nlogical\n\nLoose\nLORIEN\ninteger\n\nLoop orientation\nLOSTYL\ninteger\n\nLoop linestyle\nLOWGAP\nreal\n\nLower Gap\nLOWPOS\npos\n\nPoint nearest workshop floor\nLOWREF\nelement\n\nReferences to lower exit level\nLPASS\nlogical\n\nDB Password Flag\nLPITCH\nreal\n\nLadder Pitch\nLPOS\npos\n\nLeave position\nLPOSE\nreal\n\nEasting of leave position\nLPOSN\nreal\n\nNorthing of leave position\nLPOSU\nreal\n\nUpping of leave position\nLPRCRE\nlogical\n\nDiscipline Created\nLPRDEL\nlogical\n\nInterdisciplinary Project Element is deletable Flag\nLPRINT\nlogical\n\nPrintability flag\nLPRMOD\nlogical\n\nInterdisciplinary Project Element is modifiable Flag\nLPROT\nlogical\n\nProtected DB Flag\nLQAANG\nreal\n\nAngle between alignment direction of leave Ppoint and next\nLQANG\nreal\n\nAngle between leave Ppoint and next component\nLQBORE\nlogical\n\nTRUE if leave Ppoint has same bore as next\nLQCON\nlogical\n\nTRUE if leave Ppoint has Correct connection type\nLQOFF\nreal\n\nOffset between leave Ppoint and next component\nLRBORE\nlogical\n\nTRUE if bores is in reducer table\nLREF\nelement\n\nLink reference\nLREFO\nlogical\n\nDatabase holds Reference data only flag\nLRFLSY\nlogical\n\nReflectable Symbol\nLRISE\nreal\n\nLower Tread Rise\nLROTSY\nlogical\n\nRotatable Symbol\nLRUNG\nlogical\n\nLast rung flag\nLSCSLS\nlogical\n\nLogical sheet changed since last save\nLSCSYM\nlogical\n\nScale With Symbol\nLSELEC\nlogical\n\nTrue if can be set Directly in Design\nLSFBR\nlogical\n\nSpooling marker for leave tube\nLSHA\nstring\n\nLeader shape code\nLSPA\nreal\n\nText line spacing factor\nLSPATX\nstring(80)\n\nText line spacing factor (as text)\nLSRO\nelement\n\nLeave rod specification\nLSTCFL\nlogical\n\nColumn filtering\nLSTCSM\nlogical\n\nColumn summaries\nLSTCSR\nlogical\n\nColumn items can be sorted\nLSTDST\ninteger\n\nLogical Value For List Datasheet\nLSTGP\nlogical\n\nShow the grouping panel\nLSTLS\nlogical\n\nShow leading slash for names\nLSTMSF\nlogical\n\nMulti-select filter style\nLSTPIN\nlogical\n\nShow column pins in column headers\nLSTPUB\nlogical\n\nCan be published to AVEVA NET\nLSTR\nlogical\n\nStress flag\nLSTU\nelement\n\nLeave tube reference\nLSTUIH\nlogical\n\nShow units in headers\nLSTUN\nlogical\n\nShow Unset Nulref values\nLSTUPD\ndatetime(2)\n\nLast updated from\nLSTVIS\nlogical\n\nVisible in list dropdown\nLSTWTC\nlogical\n\nWrap text in cells of a grid\nLSTWTH\nlogical\n\nWrap text in column headers\nLSTYNO\ninteger\n\nLine Style Number\nLSTZF\ninteger\n\nZoom factor\nLSVHIS\nlogical\n\nDatabase save history from compaction flag\nLSWID\nreal\n\nLine Style Width\nLSWKEY\nstring(120)\n\nLine Style Width Key\nLTAI\nlogical\n\nLogical tail flag\nLTAPER\nlogical\n\nTrue if Gensec can be tapered\nLTBORE\nlogical\n\nTRUE if bores is in branch (tee) table\nLTCLL\nreal\n\nCentre-line length of leave implied tube\nLTCORR\nreal\n\nLeave tube corrosion allowance\nLTER\nstring\n\nLabel terminator code\nLTERID\ninteger\n\nLabel terminator ID\nLTHICK\nreal\n\nDoor leaf thickness\nLTIMEI\ninteger\n\nTime Interval between retries\nLTITL\nstring(120)\n\nRepresentation layer title\nLTLE\nreal\n\nLength of leave implied tube\nLTOP\npos\n\nTop of leave pipe\nLTSTLEN\nreal\n\nLeave Tube Stock Length\nLTWALL\nreal\n\nLeave tube wall thickness\nLTWREF\nelement\n\nLeave tube wall thickness reference\nLVAR\nlogical\n\nVariant Flag\nLVDWPO\nlogical\n\nTRUE if valid Draft pline point or ppoint\nLVIS\nlogical\n\nVisibility flag\nLVOL\nreal(6)\n\nEnclosing box volume in local coordinates\nLVQUAL\ninteger\n\nLaser Volume Quality\nLWAITD\ninteger\n\nTime interval between re-sending commands\nLWALLT\nreal\n\nLeave wall thickness\nLWIDTH\nreal\n\nLine Width\nLWP\npos\n\nLower Working Point\nLYCOL\ninteger\n\nAutoCAD Layer Colour\nLYCVFR\nlogical\n\nAutoCAD Layer Current Viewport Freeze\nLYDIR\ndir\n\nLeave Y axis direction on point\nLYFRZE\nlogical\n\nAutoCAD Layer Freeze flag\nLYLOCK\nlogical\n\nAutoCAD Layer Lock flag\nLYLTYP\nstring(120)\n\nAutoCAD Layer LineType\nLYLWT\nreal\n\nAutoCAD Layer LineWeight\nLYNVFR\nlogical\n\nAutoCAD Layer New Viewport Freeze\nLYPFG\nlogical\n\nAutoCAD Layer Plotting flag\nLYPSTY\nstring(120)\n\nAutoCAD Layer Plotter Style\nLYVIS\nlogical\n\nAutoCAD Layer Visibility Flag\nLZCOLO\ninteger\n\nLayer 0 colour\nLZDIR\ndir\n\nLeave alignment direction\nLZERGB\ninteger(4)\n\nRGB layer 0 colour\nLZERGP\ninteger(4)\n\nRGB layer 0 colour physical\nLZLSTY\ninteger\n\nLayer 0 linestyle\nLZLSTZ\ninteger\n\nLayer 0 linestyle zero is solid\nLZNPRI\nlogical\n\nLayer 0 no printability flag\nLZNVIS\nlogical\n\nLayer 0 no visibility flag\nLZPRIN\nlogical\n\nLayer 0 printability flag\nLZVIS\nlogical\n\nLayer 0 visibility flag\n\nAttribute Name\nData Type\nQualifier\nDescription\nLAAREF\nelement\nLaser Area reference\nLABDIR\nstring(120)\nName of attribute (or pseudo) to be used for label along direction\nLABOFFS\nreal(3)\nLabel offset\nLABPOS\npos\nLabel position\nLABSID\nstring(120)\nName of attribute (or pseudo) to be used for label side direction\nLABST\ninteger\nNumber of starts for label signing\nLACR\nlogical\nAccess Control on/off switch\nLACTIV\nlogical\nTrue if selectable : false = limbospec\nLACTYP\nstring(32)\nLabelled action\nLADCOL\ninteger\nLaser Drawing colour\nLADRES\ninteger\nLaser Drawing Resolution (dpi)\nLADRGB\ninteger(4)\nRGB laser drawing colour\nLADRGP\ninteger(4)\nRGB laser drawing colour physical\nLADSTY\ninteger\nLaser Drawing Style\nLALCAB\nelement(500)\nList arriving leaving cables on attached point\nLALLAN\nreal\nLeave Ppoint allowed angle\nLAMDIS\nlogical\nTrue if Lam Displ\nLAMINA\nstring(12)\nName of first laminate code\nLAMINB\nstring(12)\nName of second laminate code\nLAMWTH\nreal\nWidth of laminate\nLANGUAGE\nstring(35)\nLanguage tag as described in BCP 47 - Tags for Identifying Languages(http://tools.ietf.org/html/bcp47)\nLANREF\nelement\nLinked annotation element reference\nLASTM\nstring(120)\nattr\nDate of last modification\nLAUTHU\nlogical\nLogin Authentication on/off switch\nLAVORF\nelement\nReference to laser volume set, containing the complete definition of the laser representation\nLAXE\nori\nLocal axes\nLAYARF\nelement\nAnnotation Layer ruleset reference\nLAYDRF\nelement\nDesign Layer ruleset reference\nLAYMOD\ninteger\nBundle layout mode\nLAYMOT\nstring(100)\ninteger\nLayout mode text\nLAYOUT\nlogical\nTRUE if element is layout mode\nLAYTBF\nelement\nLayer Table reference\nLBBORE\nlogical\nTRUE if Minor/Branch bore is in nominal bore table\nLBFACT\nreal\nLabelling along factor\nLBGIMG\nlogical\nBackground image flag\nLBLANG\nreal\nLabelling angle\nLBLDIR\ninteger\nLabelling direction\nLBLHGT\nreal\nLabelling height\nLBLID\ninteger\nLabelling reference id\nLBLIND\nlogical\nBlind hole flag\nLBLMIR\ninteger\nLabelling reflection code\nLBLPOS\nreal(2)\nLabelling definition point\nLBLSID\ninteger\nLabelling side of part\nLBLTXT\nstring(300)\nLabelled text\nLBOP\npos\nBottom of leave pipe\nLBOR\nreal\nLeave bore\nLBPOME\nstring(32)\nLabelling position method\nLBRINF\ninteger\nReference information for labelling\nLBRPOS\nreal(2)\nLabelling reference point\nLBSPOS\ninteger\nLabelled symbol text position\nLBSTRF\nelement\nLabel style reference\nLBTRAN\nlogical(3)\nTrue if rotation, translation and reflection is allowed\nLBTVAL\nreal(2)\nLabelling at intervals\nLBTYPE\nstring(32)\nReference information for labelling\nLCAS\ninteger\nLoad case number\nLCHA\nlogical\nChain flag\nLCHKDA\ndatetime(2)\nDate of last pipe fabrication consistency check\nLCIRCR\nreal(8)\nLeast circumscribed rectangle\nLCKNUT\nstring(32)\nDetailing Bolt Set Lock Nut\nLCKPSW\nlogical\nLock passwords for general users\nLCLAIM\nlogical\nAccess Control Claim flag\nLCLM\nlogical\nTrue if element is claimed\nLCLMH\nlogical\nTrue if element and hierarchy claimed\nLCLOSE\nlogical\nIs this entity closed?\nLCNFA\nelement(500)\nArray of elements with local names\nLCON\nword\nLeave connection type\nLCONFL\nlogical\nLocal Connection Point Flag\nLCONSU\nlogical\nConsumer Extract database flag, can be refreshed when read-only\nLCORRO\nreal\nLeave corrosion allowance\nLCPOVWRITE\nlogical\nLocation Overwrite DB Users policy flag\nLCPREF\nelement\nLinked connection point reference\nLCTROL\nlogical\nControlled DB Flag\nLCUTDI\ndir\nLower Extension Cutting Direction\nLDFLT\nlogical\nlogical default value for a UDA\nLDI\ndir\nLeave direction\nLDIAM\nreal\nLoop diameter\nLDIMPD\nreal(3)\nLinear Dimension Projected Direction Pseudo\nLDISP\nlogical\nDisplay property flag for design datasets: True if property is shown on form\nLDPR\nreal\nword\nLocal design dataset property\nLDRDIR\ndir\nLadder Direction\nLEAFS\nreal\nNumber of door leafs\nLEAHEI\nreal\nLeave height\nLEASHA\nword\nLeave PPoint Connection shape\nLEAV\ninteger\nLeave Ppoint\nLEAWID\nreal\nLeave width\nLEND\nlogical\nLine end\nLENDTI\ninteger\nTime out period for commands\nLENG\nreal\nLength\nLENINS\nreal\nInitial tube length inside bending machine.\nLENOUT\nreal\nInitial tube length outside bending machine\nLENSEG\nreal\nLength of segment\nLETTER\nstring(50)\nLetter\nLEVE\ninteger(2)\nDrawing level\nLEVENL\ninteger\nTime interval for Event Loop\nLEVRFA\nelement(100)\nReferences to levels serviced by stairwell\nLEXCES\nreal\nLeave excess for leave tube\nLEXREF\nelement\nDraw Linked External Reference\nLEXTNS\nreal\nLower Extension Length\nLFADIR\ndir\nFlight A Direction\nLFAOFFSET\nreal\nLanding Flight A Offset\nLFBDIR\ndir\nLanding Flight B Direction\nLFBOFFSET\nreal\nLanding Flight B Offset\nLFCOLG\ninteger\nGlabel style frame colour\nLFCOLO\ninteger\nLabel frame colour\nLFCONU\ninteger\nLabel frame colour number\nLFDP\nelement\nword\nLocal design dataset property\nLFGRGB\ninteger(4)\nRGB glabel style frame colour\nLFGRGP\ninteger(4)\nRGB glabel style frame colour physical\nLFPN\ninteger\nLabel frame pen\nLFRA\nlogical\nFrame flag\nLFRRGB\ninteger(4)\nRGB label frame colour\nLFRRGP\ninteger(4)\nRGB label frame colour physical\nLFSTREF\nelement\nLabel frame linestyle Reference\nLFSTYG\ninteger\nGLabel style frame line type\nLFSTYL\ninteger\nLabel frame linestyle\nLGAP\nreal\nLast offset distance\nLGOING\nreal(10)\nLower Tread Going\nLGRD\nreal\nLeave Ppoint gradient\nLGTYPC\nlogical\nGeneric type is closed flag\nLHBORE\nlogical\nTRUE if Major/Header bore is in nominal bore table\nLHEA\nlogical\nLogical head flag\nLHEI\nreal\nLetter height\nLHEITX\nstring(80)\nLetter height text\nLHIDE\nlogical\nHide flag for catalogue datasets: True if property is not shown on form\nLIGHTI\nreal\nLighting requirements\nLIMI\nreal(6)\nVolume of interest\nLIMNMS\nstringarray(1000)\nLimit names\nLIMNUM\ninteger\nOrder number of limit\nLIMREF\nelement(10)\nReference limit\nLINIT\nlogical\nLocation initialisation flag\nLINKRE\nelement\nLink reference\nLINKS\nelement(5000)\nLinked elements\nLINKSN\ninteger\nLinked session on parent extract\nLINKXR\nelement(1000)\nReferencing elements\nLISS\nlogical\nTrue if drawing has been issued\nLIST\nword(5000)\nList of all possible member types\nLISTD\nstringarray(2147483647)\nGeneric Text List Data Storage\nLLCL\nreal\nLeader line clearance\nLLCLTX\nstring(80)\nLeader line clearance text\nLLCOLG\ninteger\nGLabel style leader colour\nLLCOLO\ninteger\nLeader line colour\nLLCONU\ninteger\nLabel leader colour number\nLLDIAGRAMS\nstring(2000)\nLine list diagrams\nLLDMODE\ninteger\nLeader line dimension mode (Default, ByVStyle, Off, On)\nLLEA\nlogical\nLeader line flag\nLLENG\nreal\nLeave length\nLLENTRY\nlogical\nIs a line list entry - true or false\nLLFROM\nstring(2000)\nFrom column text for a line list\nLLGRGB\ninteger(4)\nRGB glabel style leader colour\nLLGRGP\ninteger(4)\nRGB glabel style leader colour physical\nLLIS\nword(2000)\nList of all possible types in member hierarchy\nLLNRGB\ninteger(4)\nRGB leader line colour\nLLNRGP\ninteger(4)\nRGB leader line colour physical\nLLPN\ninteger\nLabel leader pen\nLLSTREF\nelement\nLabel leader linestyle Reference\nLLSTYG\ninteger\nGLabel style leader line type\nLLSTYL\ninteger\nLeader line linestyle\nLLTBRANCH\nelement\nLine list tail branch\nLLTO\nstring(2000)\nTo column text for a line list\nLMAXTR\ninteger\nMaximum number of retries for command\nLMDREF\nelement(20)\nBack reference to demolition packages referencing laser survey\nLMDSES\ninteger(10)\nSession number of back reference to demolition packages referencing laser survey\nLMDSYN\nstring(700)\nSynchronisation state of AVEVA and laser survey databases\nLMERDL\nlogical\nEnable automatic merge of transaction db\nLMERFAILURE\ninteger\nNumber of days Failed commands persist in Trans dB\nLMERSUCCESS\ninteger\nNumber of days Successful commands persist in Trans dB\nLMERTI\nstring(120)\nFrequency of Auto Merge of Transaction DB\nLMIRR\nlogical\nTrue if Mirroring required\nLNAME\nstring(21)\nLocal name as stored on template\nLNDLEV\nreal(100)\nLanding levels from owning element\nLNFA\nelement(480)\nHidden Reference Array for linked Vertices\nLNGVAR\nlogical\nLanguage Variant, is attribute language variant. Applies to text attributes only.\nLNKALINVALID\nelement(100)\nAll invalid HANCI refs\nLNKALLARRAY\nelement(100)\nAll HANCI refs\nLNKCLS\nelement(500)\nClasses referencing a DocLink\nLNKDOC\nelement(500)\nDocLinks referring to element\nLNKELE\nelement(500)\nElements referencing a DocLink\nLNKIRARRAY\nelement(100)\nInvalid HANCI reference array attribute\nLNKPRP\nword\nTRUE if item pointed to by descriptor should be propagated by Global\nLNKREF\nelement\nReference internal document (drawing/sheet)\nLNKRFARRAY\nelement(100)\nHANCI reference array attribute\nLNKRX\nelement\nReference to first location of a link\nLNKRY\nelement\nReference to second location of a link\nLNKUSE\nword\nLink Descriptor Usage\nLNKVFARRAY\nlogical(10)\nIndividual support valid flags array attribute\nLNKWV\ninteger\nLink weighting value\nLNLST\nstring(2000)\nList of local names for current template\nLNOUPDATE\nlogical\nDB propagation suppressed flag\nLNPRXS\nelement(500)\nProxy items referring to element\nLNTP\nword\nLine type\nLOCA\nstring(120)\nLocation\nLOCDBR\nelement\nLocation Db Ref\nLOCID\nstring(3)\nLocation identifier\nLOCK\nlogical\nLogical flag which determines if the UDAs attribute values are locked\nLOCKID\nlogical\nLock Id\nLOCOLO\ninteger\nLoop line colour\nLOCPR\nelement(1000)\nList of LOCs Primary at location\nLOCRF\nelement\nLocation reference\nLOCRGB\ninteger(4)\nLoop RGB colour\nLOCRGP\ninteger(4)\nLoop RGB colour physical\nLOCTRC\nelement\nSymbolic local trace style reference\nLOCTYP\ninteger\nLocation\nLOD\nreal\nLeave Ppoint outside diameter\nLODIMG\nlogical\nOriginal image data flag\nLOEXTN\nreal\nLoop extension\nLOFF\nlogical\nOffline flag\nLOGEV\nlogical\nLogical value evaluation\nLOGFN\nstring(1024)\nCOMMS log file name\nLOGLV\ninteger\nCOMMS log file level of detail\nLOGMS\nlogical\nCOMMS log file active/inactive flag\nLOGXP\ninteger(500)\nLogical expression\nLOHE\nreal\nPLOOP height - from first PLOOP in owning panel\nLOOS\nlogical\nLoose\nLORIEN\ninteger\nLoop orientation\nLOSTYL\ninteger\nLoop linestyle\nLOWGAP\nreal\nLower Gap\nLOWPOS\npos\nPoint nearest workshop floor\nLOWREF\nelement\nReferences to lower exit level\nLPASS\nlogical\nDB Password Flag\nLPITCH\nreal\nLadder Pitch\nLPOS\npos\nLeave position\nLPOSE\nreal\nEasting of leave position\nLPOSN\nreal\nNorthing of leave position\nLPOSU\nreal\nUpping of leave position\nLPRCRE\nlogical\nDiscipline Created\nLPRDEL\nlogical\nInterdisciplinary Project Element is deletable Flag\nLPRINT\nlogical\nPrintability flag\nLPRMOD\nlogical\nInterdisciplinary Project Element is modifiable Flag\nLPROT\nlogical\nProtected DB Flag\nLQAANG\nreal\nAngle between alignment direction of leave Ppoint and next\nLQANG\nreal\nAngle between leave Ppoint and next component\nLQBORE\nlogical\nTRUE if leave Ppoint has same bore as next\nLQCON\nlogical\nTRUE if leave Ppoint has Correct connection type\nLQOFF\nreal\nOffset between leave Ppoint and next component\nLRBORE\nlogical\nTRUE if bores is in reducer table\nLREF\nelement\nLink reference\nLREFO\nlogical\nDatabase holds Reference data only flag\nLRFLSY\nlogical\nReflectable Symbol\nLRISE\nreal\nLower Tread Rise\nLROTSY\nlogical\nRotatable Symbol\nLRUNG\nlogical\nLast rung flag\nLSCSLS\nlogical\nLogical sheet changed since last save\nLSCSYM\nlogical\nScale With Symbol\nLSELEC\nlogical\nTrue if can be set Directly in Design\nLSFBR\nlogical\nSpooling marker for leave tube\nLSHA\nstring\nLeader shape code\nLSPA\nreal\nText line spacing factor\nLSPATX\nstring(80)\nText line spacing factor (as text)\nLSRO\nelement\nLeave rod specification\nLSTCFL\nlogical\nColumn filtering\nLSTCSM\nlogical\nColumn summaries\nLSTCSR\nlogical\nColumn items can be sorted\nLSTDST\ninteger\nLogical Value For List Datasheet\nLSTGP\nlogical\nShow the grouping panel\nLSTLS\nlogical\nShow leading slash for names\nLSTMSF\nlogical\nMulti-select filter style\nLSTPIN\nlogical\nShow column pins in column headers\nLSTPUB\nlogical\nCan be published to AVEVA NET\nLSTR\nlogical\nStress flag\nLSTU\nelement\nLeave tube reference\nLSTUIH\nlogical\nShow units in headers\nLSTUN\nlogical\nShow Unset Nulref values\nLSTUPD\ndatetime(2)\nLast updated from\nLSTVIS\nlogical\nVisible in list dropdown\nLSTWTC\nlogical\nWrap text in cells of a grid\nLSTWTH\nlogical\nWrap text in column headers\nLSTYNO\ninteger\nLine Style Number\nLSTZF\ninteger\nZoom factor\nLSVHIS\nlogical\nDatabase save history from compaction flag\nLSWID\nreal\nLine Style Width\nLSWKEY\nstring(120)\nLine Style Width Key\nLTAI\nlogical\nLogical tail flag\nLTAPER\nlogical\nTrue if Gensec can be tapered\nLTBORE\nlogical\nTRUE if bores is in branch (tee) table\nLTCLL\nreal\nCentre-line length of leave implied tube\nLTCORR\nreal\nLeave tube corrosion allowance\nLTER\nstring\nLabel terminator code\nLTERID\ninteger\nLabel terminator ID\nLTHICK\nreal\nDoor leaf thickness\nLTIMEI\ninteger\nTime Interval between retries\nLTITL\nstring(120)\nRepresentation layer title\nLTLE\nreal\nLength of leave implied tube\nLTOP\npos\nTop of leave pipe\nLTSTLEN\nreal\nLeave Tube Stock Length\nLTWALL\nreal\nLeave tube wall thickness\nLTWREF\nelement\nLeave tube wall thickness reference\nLVAR\nlogical\nVariant Flag\nLVDWPO\nlogical\nTRUE if valid Draft pline point or ppoint\nLVIS\nlogical\nVisibility flag\nLVOL\nreal(6)\nEnclosing box volume in local coordinates\nLVQUAL\ninteger\nLaser Volume Quality\nLWAITD\ninteger\nTime interval between re-sending commands\nLWALLT\nreal\nLeave wall thickness\nLWIDTH\nreal\nLine Width\nLWP\npos\nLower Working Point\nLYCOL\ninteger\nAutoCAD Layer Colour\nLYCVFR\nlogical\nAutoCAD Layer Current Viewport Freeze\nLYDIR\ndir\nLeave Y axis direction on point\nLYFRZE\nlogical\nAutoCAD Layer Freeze flag\nLYLOCK\nlogical\nAutoCAD Layer Lock flag\nLYLTYP\nstring(120)\nAutoCAD Layer LineType\nLYLWT\nreal\nAutoCAD Layer LineWeight\nLYNVFR\nlogical\nAutoCAD Layer New Viewport Freeze\nLYPFG\nlogical\nAutoCAD Layer Plotting flag\nLYPSTY\nstring(120)\nAutoCAD Layer Plotter Style\nLYVIS\nlogical\nAutoCAD Layer Visibility Flag\nLZCOLO\ninteger\nLayer 0 colour\nLZDIR\ndir\nLeave alignment direction\nLZERGB\ninteger(4)\nRGB layer 0 colour\nLZERGP\ninteger(4)\nRGB layer 0 colour physical\nLZLSTY\ninteger\nLayer 0 linestyle\nLZLSTZ\ninteger\nLayer 0 linestyle zero is solid\nLZNPRI\nlogical\nLayer 0 no printability flag\nLZNVIS\nlogical\nLayer 0 no visibility flag\nLZPRIN\nlogical\nLayer 0 printability flag\nLZVIS\nlogical\nLayer 0 visibility flag\n\n\n"}
{"Headers": "Attribute M", "Content": "MACHIN\nelement\n\nMachine reference\nMACRID\nstring\n\nClip macro ID\nMAINTENANCE\nreal\n\nMaintenance level radiation\nMAKER\nstring(100)\n\nMaker\nMANBLK\nstring\n\nName of owner block\nMANCOG\npos\n\nCenter of gravity\nMANLEN\nreal\n\nLength of manual intervals\nMANLNK\nelement\n\nManufacturing Element Link\nMANNUM\ninteger\n\nNumber of manual intervals\nMANPAN\nstring\n\nName of owner panel\nMANTRA\nreal(16)\n\nTransformation from local coordinate system\nMANTYP\nstring(26)\n\nManufactured type e.g. Plane, Curved,...\nMANU\nstring(120)\n\nManufacturer Name\nMANUFR\nstring(120)\n\nManufacturer\nMANWGH\nreal\n\nWeight\nMARKNG\nstring(120)\n\nText storing marking for cable core\nMARKRF\nelement(100)\n\nCable Mark points\nMARPTY\ninteger\n\nMarine picture type\nMASSPL\nreal\n\nMass per unit Length\nMATANG\nreal\n\nMaterial Lay Angle\nMATDEN\nreal\n\nMaterial density\nMATDIR\ndir\n\nMaterial direction\nMATID\ninteger\n\nMaterial ID\nMATLEN\nreal\n\nMaterial Length\nMATN\nstring(1000)\n\nMaterial Note\nMATOVE\nreal\n\nMaterial Overlap\nMATOWNER\nelement\n\nMaturity Owning Element\nMATPURPOSE\nword\n\nMaterial purpose\nMATR\nelement\n\nMaterial reference\nMATTYPE\nstring(100)\n\nMaterial type\nMATURF\nelement\n\nReference of Maturity Level Element\nMATWID\nreal\n\nMaterial Width\nMATX\nelement\n\nMaterial text\nMAXA\nreal\n\nMaximum answer\nMAXARE\nreal\n\nMaximum area\nMAXB\nreal\n\nMaximum bore\nMAXCAB\ninteger\n\nMaximum Number of cables\nMAXD\ninteger\n\nDB hierarchy depth of lowest level item beneath element\nMAXFIL\nreal\n\nMaximum percentage fill level\nMAXHUM\nreal\n\nMaximum Humidity\nMAXLAY\ninteger\n\nMaximum Layers\nMAXLP\nreal\n\nMaximum length of pipe\nMAXMIN\nreal(2)\n\nMaximum and minimum values of design property\nMAXOD\nreal\n\nMaximum Outer Diameter\nMAXPLN\npos\n\nMaximum Plane Position\nMAXPRE\nreal\n\nMaximum Pressure\nMAXREP\ninteger\n\nMaximum number of Repeat items created\nMAXSLO\nreal\n\nMaximum pipe slope\nMAXTEM\nreal\n\nMaximum Temperature\nMAXU\ninteger\n\nMaximum number of user\nMAXVLT\nreal\n\nMaximum voltage\nMAXVOL\nreal\n\nMaximum Volume\nMAXWAT\nreal\n\nMaximum Water Level\nMBACK\nelement(10000)\nelemtype\nMembers in reverse order\nMBLLEN\nreal\n\nLength of markblasting\nMBUFS\ninteger\n\nPreferred buffer size in MBytes\nMCBENT\nlogical\n\nMachine bent\nMCOLOUR\ninteger\n\nMarker colour\nMCONUM\ninteger\n\nMarker colour number\nMCOU\ninteger\nelemtype\nNumber of Element Members of Given type\nMDBCLS\nelement(1000)\n\nList of MDBs in which DB is current\nMDBLS\nelement(1000)\n\nList of MDBs to which DB belongs\nMDSYSF\nelement(10)\n\nReference Array of Model and Design Elements\nMELRFA\nelement(500)\n\nAll components (non-tube) in the PipePiece\nMEMB\nelement(10000)\nelemtype\nAll members, or members of specific type\nMEMDAB\nelement(10000)\n\nDabacon members\nMEML\nword\n\nMember line\nMEMNAM\nstring(120)\n\nMember name\nMEMTYP\nstring(256)\n\nMember type array\nMFAR\nword(50)\n\nModel Function Word array\nMFFIND\nelement\n\nFind Manufacturingpackage folder\nMFIXREF\nelement\n\nMerged Fixing Reference\nMFLG\nlogical\n\nMaster link flag - SLAVE if FALSE\nMFREF\nelement\n\nMerged Fixing Reference Element\nMGRADE\nstring(25)\n\nMaterial grade\nMHCOUNT\ninteger\nelemtype\nNumber of Elements of Given type\nMIALPF\nreal\n\nFirst alpha angle\nMIALPS\nreal\n\nSecond alpha angle\nMIAUXF\ninteger\n\nAuxiliary function\nMIBAOS\nreal\n\nBevel angle other side\nMIBATO\nreal\n\nBevel angle two other side\nMIBATS\nreal\n\nBevel angle this side\nMIBATT\nreal\n\nBevel angle two this side\nMIBAWO\nreal\n\nBevel angle w other side\nMIBAWT\nreal\n\nBevel angle w this side\nMIBBDE\ninteger\n\nBevel is defined\nMIBCHO\nreal\n\nBevel chamfer height other side\nMIBCHT\nreal\n\nBevel chamfer height this side\nMIBCOD\nreal\n\nBevel code\nMIBCWO\nreal\n\nBevel chamfer width other side\nMIBCWT\nreal\n\nBevel chamfer width this side\nMIBDOS\nreal\n\nBevel depth other side\nMIBDTS\nreal\n\nBevel depth this side\nMIBECT\nlogical\n\nTrue if burning end cut\nMIBEM\nreal\n\nBevel E measure\nMIBETF\nreal\n\nFirst beta angle\nMIBETS\nreal\n\nSecond beta angle\nMIBGAP\nreal\n\nEdge preparation gap\nMIBSEG\ninteger\n\nBurn start end in gap\nMIBSHP\nword\n\nBurning shape\nMIBSPT\nreal(2)\n\nPoint on edge prep. segment\nMIBTYP\ninteger\n\nBevel type\nMIBVAR\ninteger\n\nBevel variant\nMICHAM\nreal\n\nChamfer angle\nMICHOA\nreal\n\nMinimum area of cut holes\nMICOMM\nstring(256)\n\nMovement instruction comment\nMICOMP\nword\n\nMovement instruction valid for\nMICONA\nreal\n\nConnection angle\nMICPWB\nreal\n\nDistance closest point to web\nMIDATE\ndatetime(2)\n\nCration date for movement instruction\nMIDERM\nstring(80)\n\nMaterial id in the ERM system\nMIDESG\nstring(256)\n\nDesignation\nMIDESN\nstring(256)\n\nMovement instruction designation\nMIDGSD\nreal\n\nDistance used for special marking\nMIDIMS\nstring(256)\n\nDimention string\nMIDIR\ninteger\n\nMovement direction\nMIDLFT\nreal\n\nDistance from the left to origin\nMIDORI\nreal\n\nDistance origin of feature\nMIDORV\nreal\n\nDistance to origin from base line\nMIDOZP\nreal\n\nDistance to origin from endcut\nMIDP\npos\n\nSection midpoint (steelwork)\nMIDRHO\nreal\n\nMinimum diameter of drilled holes\nMIDYAY\nreal\n\nDistance Y1 and Y2\nMIEANG\nreal\n\nMinimum angle for edge preparation\nMIECOD\ninteger\n\nEnd cut code\nMIEMSK\ninteger\n\nEnd cut param mask\nMIEPRM\nreal(9)\n\nEnd cut parameters\nMIETYP\ninteger\n\nEnd cut type\nMIEUDD\nstringarray(20)\n\nUser defined end cut data\nMIEUDN\nstring(256)\n\nName of user defined end cut\nMIEUDP\nreal(20)\n\nUser defined end cut parameters\nMIEXCE\nreal\n\nExcess on profile end\nMIFANG\nreal\n\nMinimum end cut angle flanges\nMIFEXC\nreal\n\nFabrication excess\nMIFONT\ninteger\n\nLabeling symbol font\nMIFPWB\nreal\n\nDistance farthest point to web\nMIFROT\nreal\n\nRotation of the feature\nMIFTYP\ninteger\n\nType code of feature\nMIGEVF\ninteger\n\nGeometry valid for\nMIHFAC\nreal\n\nPosition of the nose as a factor\nMIHFAD\nreal\n\nAdjust factor for the nose\nMIHMEA\nreal\n\nPosition of the nose\nMIINCA\nreal\n\nInclination angle\nMIINTA\nreal\n\nIntersecting angle\nMILCPT\nreal\n\nDistance closest point\nMILFPT\nreal\n\nDistance farthest point\nMILFTV\nreal\n\nDistance to v1\nMILORI\nreal\n\nDistance origin\nMILTYP\ninteger\n\nLabel type\nMIMASL\nstring(256)\n\nAssembly name\nMIMATT\nstring(256)\n\nMarking attribute\nMIMGSD\nlogical\n\nMarking of gsd\nMIMHDR\nstringarray(10)\n\nEngineering 3D Model File MIME Header\nMIMIRR\nlogical\n\nMirrored feature\nMIMPSD\ninteger\n\nPenetrating material side\nMIMPTH\nreal\n\nProfile thickness\nMIMSID\nreal(2)\n\nMaterial side\nMIMTYP\nstring(256)\n\nMarking type\nMIMUTP\nstring(256)\n\nMarking user type\nMIMWLD\nreal\n\nMarking of weld\nMINAME\nstring(256)\n\nMovement instruction name\nMINANG\nreal\n\nNose angle\nMINARE\nreal\n\nMinimum area\nMINBEN\nstring(1000)\n\nMinimum Bend Radius\nMINFED\nreal(500)\n\nMinimum feed values\nMINFIL\nreal\n\nMin Fill level on Cableway and Cabletray components\nMINHUM\nreal\n\nMinimum Humidity\nMINLNA\nreal\n\nFirst nose length\nMINLNB\nreal\n\nSecond nose length\nMINLP\nreal\n\nMinimum length of pipe\nMINOD\nreal\n\nMinimum Outer Diameter\nMINOSE\nreal\n\nLength of the nose\nMINPLN\npos\n\nMinimum Plane Position\nMINPOS\ninteger\n\nSmallest position number of nested plate parts\nMINPRE\nreal\n\nMinimum Pressure\nMINRAD\nreal\n\nMinimum bend radius\nMINSLO\nreal\n\nMinimum pipe slope\nMINTEM\nreal\n\nMinimum Temperature\nMINUMH\ninteger\n\nNumber of heads\nMINVER\nreal\n\nMinimum vertical pipe slope\nMINVLT\nreal\n\nMinimum voltage\nMINVOL\nreal\n\nMinimum Volume\nMIOPEN\ninteger\n\nInstruction contour type\nMIPLTH\nreal\n\nPlate thickness\nMIPMSD\nstring(256)\n\nMarking side\nMIPNAM\nstring(256)\n\nPart name reference\nMIPSID\nword\n\nProfile end\nMIPTID\ninteger\n\nInternal part id\nMIRADA\nreal\n\nRadius of arc part\nMIRADB\nreal\n\nRadius of arc part\nMIRRCD\ninteger\n\nNested part reflection\nMIRROR\nlogical\n\nTrue if mirrored in local v-axis\nMISHAP\nstring(256)\n\nInstruction shape\nMISIDE\nword\n\nMovement instruction side\nMISTSS\nreal\n\nStoss\nMISYMN\ninteger\n\nLabeling symbol number\nMITEXT\nstring(256)\n\nLabel text\nMITHEI\nreal\n\nLabel text height\nMITPOS\nreal(2)\n\nLabel text position\nMITROT\nreal\n\nLabel text rotation\nMITTYP\ninteger\n\nLabel text type\nMIWANG\nreal\n\nMinimum end cut angle web\nMIWORK\nstring(256)\n\nMovement instruction work type\nMLEF\nreal\n\nMinimum length excluding flange\nMLIF\nreal\n\nMinimum length including flange\nMLIM\nreal(3)\n\nMoment limits\nMLLIN\nlogical\n\nMll Include\nMLNCOL\ninteger\n\nMember-line colour\nMLNCON\ninteger\n\nMember-line colour number\nMLNP\ninteger\n\nMember line pen\nMLNRGB\ninteger(4)\n\nRGB member line colour\nMLNRGP\ninteger(4)\n\nRGB member line colour physical\nMLNSTREF\nelement\n\nMember-line linestyle Reference\nMLNSTY\ninteger\n\nMember-line linestyle\nMLVREF\nelement\n\nReference to the Shared Maturity Level\nMMBOR\nreal\n\nMM Nominal Bore\nMNDIRE\nstring(9)\n\nMain direction enumerated\nMNDIRI\ninteger\n\nMain direction\nMNSIDE\nstring(9)\n\nMain side enumerated\nMNSIDI\ninteger\n\nMai side\nMODATT\nlogical\nattr\nTrue if attribute of element can be modified\nMODDBR\nelement\n\nModel Db Ref\nMODDEL\nlogical\nattr\nTrue if element can be deleted\nMODERR\nstring(240)\nattr\nReturns the error text that would occur if attribute was modified\nMODID\nstring(2000)\n\nUsed by laser driver to identify external laser data\nMODNME\nstring(100)\n\nModel name\nMODREF\nelement(100)\n\nModel references\nMODSTA\nstring(20)\n\nCreation Status of Models as enumerated\nMODSTY\ninteger\n\nModel Creation Style\nMODTYP\nstring(50)\n\nModel type\nMODU\nstring(120)\n\nModule\nMOFI\npos\n\nMoment of Inertia\nMOME\nreal(3)\n\nMoment\nMOULEN\nreal\n\nMould length\nMPARE\nreal\n\nArea\nMPDAT\ndatetime(2)\n\nMass Calculation performed date\nMPEN\ninteger\n\nMarker pen\nMPFIND\nelement\n\nFind Manufacturingpackage\nMPKGFD\nelement\n\nFind Manufacturingpackage\nMPKGFI\ninteger(500)\n\nManufacturing Package Filter Expression\nMPKGRF\nelement\n\nManufacturing Package Reference\nMPREF\nelement\n\nMass Properties Element\nMPVOL\nreal\n\nVolume\nMPWEI\nreal\n\nWeight\nMRGF\nlogical\n\nADP merge flag\nMRGL\nword\n\nADP merge level\nMRKLEN\nreal\n\nTotal marking length\nMRKR\nword\n\n3 way component marker\nMRKRGB\ninteger(4)\n\nRGB marker colour\nMRKRGP\ninteger(4)\n\nRGB marker colour physical\nMRKST\ninteger\n\nNumber of starts for marking\nMSESS\ninteger\nattr\nLast session number\nMSGUID\nstring(160)\n\nUniversally unique identifier from external sources (in MS format)\nMSTREF\nelement\n\nMarker style Reference\nMSTYID\ninteger\n\nMarker style\nMSTYLE\ninteger\n\nMarker style\nMSTYSZ\nreal\n\nMarker size\nMTBE\nelement\n\nMaterial tube start. The first component, excluding ATTSs, for whom the LOFF is invalid or false\nMTCL\nreal\n\nMaterial tube centreline length.\nMTEN\nelement\n\nMaterial tube end. The first component, excluding ATTSs, for whom the LOFF is invalid or false\nMTHICK\nreal\n\nMaterial thickness\nMTLCHE\nstring(80)\n\nMatchline text character height as text\nMTLCOL\ninteger\n\nMatchline colour\nMTLE\nreal\n\nMaterial tube length for TUBI. Includes preceding bend length if bend is offline.\nMTLFON\ninteger\n\nMatchline text font\nMTLLST\ninteger\n\nMatchline linestyle\nMTLRGB\ninteger(4)\n\nRGB matchline colour\nMTLRGP\ninteger(4)\n\nRGB matchline colour physical\nMTLSTZ\ninteger\n\nMatchline line type zero is ByStyle\nMTLTCH\nreal\n\nMatchline text character height\nMTLTCO\ninteger\n\nMatchline text colour\nMTLVIS\nlogical\n\nMatchline visibility flag\nMTOC\nword\n\nMaterial list control for components\nMTOFF\nreal\n\nMaterial offset\nMTOH\nword\n\nMaterial list control for head tube\nMTOL\nstring(1000)\n\nMaterial List Length\nMTOPARTNUMBERS\ninteger(20)\n\nAdditional spooling item part numbers\nMTOQ\nstring(1000)\n\nMaterial take off quantity\nMTOR\nelement(20)\n\nExtra material list spec references\nMTOT\nword\n\nMaterial list control for components leave tube\nMTOX\ninteger(20)\n\nOld spooler addition items\nMTTRGB\ninteger(4)\n\nRGB matchline text colour\nMTTRGP\ninteger(4)\n\nRGB matchline text colour physical\nMTXR\nelement\n\nMaterial text reference\nMTXX\nstring(2000)\n\nXTEXT of material text\nMTXY\nstring(2000)\n\nYTEXT of material text\nMTXZ\nstring(2000)\n\nZTEXT of material text\nMULT\nreal\n\nMultiplier factor (unit definition)\nMVCEXP\ninteger(500)\n\nModel View content expression\nMVER\nelement\n\nReference to Master Vertex\nMVMDRF\nelement\n\nModel view definition reference\nMVVANG\nreal\n\nViewing angle\nMVVBEA\nreal\n\nViewing bearing\nMVVCAO\nlogical\n\nClip plane all off status\nMVVCAS\nlogical\n\nCap status\nMVVCCO\ninteger\n\nCap colour\nMVVCLS\nlogical\n\nClip status\nMVVCOR\nori\n\nClipbox direction\nMVVCPO\npos\n\nClipbox position\nMVVCTP\ninteger\n\nCamera type\nMVVCTR\npos\n\nViewing centre\nMVVDIR\nori\n\nViewing direction\nMVVDTO\nreal\n\nDistance to observer\nMVVELV\nreal\n\nViewing elevation\nMVVLIM\nreal(6)\n\nView limits\nMVVRAD\nreal\n\nViewing radius\nMXDRHO\nreal\n\nMaximum diameter of drilled holes\nMXEANG\nreal\n\nMaximum angle for edge preparation\nMXFANG\nreal\n\nMaximum end cut angle flanges\nMXWANG\nreal\n\nMaximum end cut angle web\nMYINSF\nelement\n\nSurface Treatment Reference\nMYOUSF\nelement\n\nSurface Treatment Reference\nMYSRFT\nelement\nword\nSurface Treatment Reference\n\nAttribute Name\nData Type\nQualifier\nDescription\nMACHIN\nelement\nMachine reference\nMACRID\nstring\nClip macro ID\nMAINTENANCE\nreal\nMaintenance level radiation\nMAKER\nstring(100)\nMaker\nMANBLK\nstring\nName of owner block\nMANCOG\npos\nCenter of gravity\nMANLEN\nreal\nLength of manual intervals\nMANLNK\nelement\nManufacturing Element Link\nMANNUM\ninteger\nNumber of manual intervals\nMANPAN\nstring\nName of owner panel\nMANTRA\nreal(16)\nTransformation from local coordinate system\nMANTYP\nstring(26)\nManufactured type e.g. Plane, Curved,...\nMANU\nstring(120)\nManufacturer Name\nMANUFR\nstring(120)\nManufacturer\nMANWGH\nreal\nWeight\nMARKNG\nstring(120)\nText storing marking for cable core\nMARKRF\nelement(100)\nCable Mark points\nMARPTY\ninteger\nMarine picture type\nMASSPL\nreal\nMass per unit Length\nMATANG\nreal\nMaterial Lay Angle\nMATDEN\nreal\nMaterial density\nMATDIR\ndir\nMaterial direction\nMATID\ninteger\nMaterial ID\nMATLEN\nreal\nMaterial Length\nMATN\nstring(1000)\nMaterial Note\nMATOVE\nreal\nMaterial Overlap\nMATOWNER\nelement\nMaturity Owning Element\nMATPURPOSE\nword\nMaterial purpose\nMATR\nelement\nMaterial reference\nMATTYPE\nstring(100)\nMaterial type\nMATURF\nelement\nReference of Maturity Level Element\nMATWID\nreal\nMaterial Width\nMATX\nelement\nMaterial text\nMAXA\nreal\nMaximum answer\nMAXARE\nreal\nMaximum area\nMAXB\nreal\nMaximum bore\nMAXCAB\ninteger\nMaximum Number of cables\nMAXD\ninteger\nDB hierarchy depth of lowest level item beneath element\nMAXFIL\nreal\nMaximum percentage fill level\nMAXHUM\nreal\nMaximum Humidity\nMAXLAY\ninteger\nMaximum Layers\nMAXLP\nreal\nMaximum length of pipe\nMAXMIN\nreal(2)\nMaximum and minimum values of design property\nMAXOD\nreal\nMaximum Outer Diameter\nMAXPLN\npos\nMaximum Plane Position\nMAXPRE\nreal\nMaximum Pressure\nMAXREP\ninteger\nMaximum number of Repeat items created\nMAXSLO\nreal\nMaximum pipe slope\nMAXTEM\nreal\nMaximum Temperature\nMAXU\ninteger\nMaximum number of user\nMAXVLT\nreal\nMaximum voltage\nMAXVOL\nreal\nMaximum Volume\nMAXWAT\nreal\nMaximum Water Level\nMBACK\nelement(10000)\nelemtype\nMembers in reverse order\nMBLLEN\nreal\nLength of markblasting\nMBUFS\ninteger\nPreferred buffer size in MBytes\nMCBENT\nlogical\nMachine bent\nMCOLOUR\ninteger\nMarker colour\nMCONUM\ninteger\nMarker colour number\nMCOU\ninteger\nelemtype\nNumber of Element Members of Given type\nMDBCLS\nelement(1000)\nList of MDBs in which DB is current\nMDBLS\nelement(1000)\nList of MDBs to which DB belongs\nMDSYSF\nelement(10)\nReference Array of Model and Design Elements\nMELRFA\nelement(500)\nAll components (non-tube) in the PipePiece\nMEMB\nelement(10000)\nelemtype\nAll members, or members of specific type\nMEMDAB\nelement(10000)\nDabacon members\nMEML\nword\nMember line\nMEMNAM\nstring(120)\nMember name\nMEMTYP\nstring(256)\nMember type array\nMFAR\nword(50)\nModel Function Word array\nMFFIND\nelement\nFind Manufacturingpackage folder\nMFIXREF\nelement\nMerged Fixing Reference\nMFLG\nlogical\nMaster link flag - SLAVE if FALSE\nMFREF\nelement\nMerged Fixing Reference Element\nMGRADE\nstring(25)\nMaterial grade\nMHCOUNT\ninteger\nelemtype\nNumber of Elements of Given type\nMIALPF\nreal\nFirst alpha angle\nMIALPS\nreal\nSecond alpha angle\nMIAUXF\ninteger\nAuxiliary function\nMIBAOS\nreal\nBevel angle other side\nMIBATO\nreal\nBevel angle two other side\nMIBATS\nreal\nBevel angle this side\nMIBATT\nreal\nBevel angle two this side\nMIBAWO\nreal\nBevel angle w other side\nMIBAWT\nreal\nBevel angle w this side\nMIBBDE\ninteger\nBevel is defined\nMIBCHO\nreal\nBevel chamfer height other side\nMIBCHT\nreal\nBevel chamfer height this side\nMIBCOD\nreal\nBevel code\nMIBCWO\nreal\nBevel chamfer width other side\nMIBCWT\nreal\nBevel chamfer width this side\nMIBDOS\nreal\nBevel depth other side\nMIBDTS\nreal\nBevel depth this side\nMIBECT\nlogical\nTrue if burning end cut\nMIBEM\nreal\nBevel E measure\nMIBETF\nreal\nFirst beta angle\nMIBETS\nreal\nSecond beta angle\nMIBGAP\nreal\nEdge preparation gap\nMIBSEG\ninteger\nBurn start end in gap\nMIBSHP\nword\nBurning shape\nMIBSPT\nreal(2)\nPoint on edge prep. segment\nMIBTYP\ninteger\nBevel type\nMIBVAR\ninteger\nBevel variant\nMICHAM\nreal\nChamfer angle\nMICHOA\nreal\nMinimum area of cut holes\nMICOMM\nstring(256)\nMovement instruction comment\nMICOMP\nword\nMovement instruction valid for\nMICONA\nreal\nConnection angle\nMICPWB\nreal\nDistance closest point to web\nMIDATE\ndatetime(2)\nCration date for movement instruction\nMIDERM\nstring(80)\nMaterial id in the ERM system\nMIDESG\nstring(256)\nDesignation\nMIDESN\nstring(256)\nMovement instruction designation\nMIDGSD\nreal\nDistance used for special marking\nMIDIMS\nstring(256)\nDimention string\nMIDIR\ninteger\nMovement direction\nMIDLFT\nreal\nDistance from the left to origin\nMIDORI\nreal\nDistance origin of feature\nMIDORV\nreal\nDistance to origin from base line\nMIDOZP\nreal\nDistance to origin from endcut\nMIDP\npos\nSection midpoint (steelwork)\nMIDRHO\nreal\nMinimum diameter of drilled holes\nMIDYAY\nreal\nDistance Y1 and Y2\nMIEANG\nreal\nMinimum angle for edge preparation\nMIECOD\ninteger\nEnd cut code\nMIEMSK\ninteger\nEnd cut param mask\nMIEPRM\nreal(9)\nEnd cut parameters\nMIETYP\ninteger\nEnd cut type\nMIEUDD\nstringarray(20)\nUser defined end cut data\nMIEUDN\nstring(256)\nName of user defined end cut\nMIEUDP\nreal(20)\nUser defined end cut parameters\nMIEXCE\nreal\nExcess on profile end\nMIFANG\nreal\nMinimum end cut angle flanges\nMIFEXC\nreal\nFabrication excess\nMIFONT\ninteger\nLabeling symbol font\nMIFPWB\nreal\nDistance farthest point to web\nMIFROT\nreal\nRotation of the feature\nMIFTYP\ninteger\nType code of feature\nMIGEVF\ninteger\nGeometry valid for\nMIHFAC\nreal\nPosition of the nose as a factor\nMIHFAD\nreal\nAdjust factor for the nose\nMIHMEA\nreal\nPosition of the nose\nMIINCA\nreal\nInclination angle\nMIINTA\nreal\nIntersecting angle\nMILCPT\nreal\nDistance closest point\nMILFPT\nreal\nDistance farthest point\nMILFTV\nreal\nDistance to v1\nMILORI\nreal\nDistance origin\nMILTYP\ninteger\nLabel type\nMIMASL\nstring(256)\nAssembly name\nMIMATT\nstring(256)\nMarking attribute\nMIMGSD\nlogical\nMarking of gsd\nMIMHDR\nstringarray(10)\nEngineering 3D Model File MIME Header\nMIMIRR\nlogical\nMirrored feature\nMIMPSD\ninteger\nPenetrating material side\nMIMPTH\nreal\nProfile thickness\nMIMSID\nreal(2)\nMaterial side\nMIMTYP\nstring(256)\nMarking type\nMIMUTP\nstring(256)\nMarking user type\nMIMWLD\nreal\nMarking of weld\nMINAME\nstring(256)\nMovement instruction name\nMINANG\nreal\nNose angle\nMINARE\nreal\nMinimum area\nMINBEN\nstring(1000)\nMinimum Bend Radius\nMINFED\nreal(500)\nMinimum feed values\nMINFIL\nreal\nMin Fill level on Cableway and Cabletray components\nMINHUM\nreal\nMinimum Humidity\nMINLNA\nreal\nFirst nose length\nMINLNB\nreal\nSecond nose length\nMINLP\nreal\nMinimum length of pipe\nMINOD\nreal\nMinimum Outer Diameter\nMINOSE\nreal\nLength of the nose\nMINPLN\npos\nMinimum Plane Position\nMINPOS\ninteger\nSmallest position number of nested plate parts\nMINPRE\nreal\nMinimum Pressure\nMINRAD\nreal\nMinimum bend radius\nMINSLO\nreal\nMinimum pipe slope\nMINTEM\nreal\nMinimum Temperature\nMINUMH\ninteger\nNumber of heads\nMINVER\nreal\nMinimum vertical pipe slope\nMINVLT\nreal\nMinimum voltage\nMINVOL\nreal\nMinimum Volume\nMIOPEN\ninteger\nInstruction contour type\nMIPLTH\nreal\nPlate thickness\nMIPMSD\nstring(256)\nMarking side\nMIPNAM\nstring(256)\nPart name reference\nMIPSID\nword\nProfile end\nMIPTID\ninteger\nInternal part id\nMIRADA\nreal\nRadius of arc part\nMIRADB\nreal\nRadius of arc part\nMIRRCD\ninteger\nNested part reflection\nMIRROR\nlogical\nTrue if mirrored in local v-axis\nMISHAP\nstring(256)\nInstruction shape\nMISIDE\nword\nMovement instruction side\nMISTSS\nreal\nStoss\nMISYMN\ninteger\nLabeling symbol number\nMITEXT\nstring(256)\nLabel text\nMITHEI\nreal\nLabel text height\nMITPOS\nreal(2)\nLabel text position\nMITROT\nreal\nLabel text rotation\nMITTYP\ninteger\nLabel text type\nMIWANG\nreal\nMinimum end cut angle web\nMIWORK\nstring(256)\nMovement instruction work type\nMLEF\nreal\nMinimum length excluding flange\nMLIF\nreal\nMinimum length including flange\nMLIM\nreal(3)\nMoment limits\nMLLIN\nlogical\nMll Include\nMLNCOL\ninteger\nMember-line colour\nMLNCON\ninteger\nMember-line colour number\nMLNP\ninteger\nMember line pen\nMLNRGB\ninteger(4)\nRGB member line colour\nMLNRGP\ninteger(4)\nRGB member line colour physical\nMLNSTREF\nelement\nMember-line linestyle Reference\nMLNSTY\ninteger\nMember-line linestyle\nMLVREF\nelement\nReference to the Shared Maturity Level\nMMBOR\nreal\nMM Nominal Bore\nMNDIRE\nstring(9)\nMain direction enumerated\nMNDIRI\ninteger\nMain direction\nMNSIDE\nstring(9)\nMain side enumerated\nMNSIDI\ninteger\nMai side\nMODATT\nlogical\nattr\nTrue if attribute of element can be modified\nMODDBR\nelement\nModel Db Ref\nMODDEL\nlogical\nattr\nTrue if element can be deleted\nMODERR\nstring(240)\nattr\nReturns the error text that would occur if attribute was modified\nMODID\nstring(2000)\nUsed by laser driver to identify external laser data\nMODNME\nstring(100)\nModel name\nMODREF\nelement(100)\nModel references\nMODSTA\nstring(20)\nCreation Status of Models as enumerated\nMODSTY\ninteger\nModel Creation Style\nMODTYP\nstring(50)\nModel type\nMODU\nstring(120)\nModule\nMOFI\npos\nMoment of Inertia\nMOME\nreal(3)\nMoment\nMOULEN\nreal\nMould length\nMPARE\nreal\nArea\nMPDAT\ndatetime(2)\nMass Calculation performed date\nMPEN\ninteger\nMarker pen\nMPFIND\nelement\nFind Manufacturingpackage\nMPKGFD\nelement\nFind Manufacturingpackage\nMPKGFI\ninteger(500)\nManufacturing Package Filter Expression\nMPKGRF\nelement\nManufacturing Package Reference\nMPREF\nelement\nMass Properties Element\nMPVOL\nreal\nVolume\nMPWEI\nreal\nWeight\nMRGF\nlogical\nADP merge flag\nMRGL\nword\nADP merge level\nMRKLEN\nreal\nTotal marking length\nMRKR\nword\n3 way component marker\nMRKRGB\ninteger(4)\nRGB marker colour\nMRKRGP\ninteger(4)\nRGB marker colour physical\nMRKST\ninteger\nNumber of starts for marking\nMSESS\ninteger\nattr\nLast session number\nMSGUID\nstring(160)\nUniversally unique identifier from external sources (in MS format)\nMSTREF\nelement\nMarker style Reference\nMSTYID\ninteger\nMarker style\nMSTYLE\ninteger\nMarker style\nMSTYSZ\nreal\nMarker size\nMTBE\nelement\nMaterial tube start. The first component, excluding ATTSs, for whom the LOFF is invalid or false\nMTCL\nreal\nMaterial tube centreline length.\nMTEN\nelement\nMaterial tube end. The first component, excluding ATTSs, for whom the LOFF is invalid or false\nMTHICK\nreal\nMaterial thickness\nMTLCHE\nstring(80)\nMatchline text character height as text\nMTLCOL\ninteger\nMatchline colour\nMTLE\nreal\nMaterial tube length for TUBI. Includes preceding bend length if bend is offline.\nMTLFON\ninteger\nMatchline text font\nMTLLST\ninteger\nMatchline linestyle\nMTLRGB\ninteger(4)\nRGB matchline colour\nMTLRGP\ninteger(4)\nRGB matchline colour physical\nMTLSTZ\ninteger\nMatchline line type zero is ByStyle\nMTLTCH\nreal\nMatchline text character height\nMTLTCO\ninteger\nMatchline text colour\nMTLVIS\nlogical\nMatchline visibility flag\nMTOC\nword\nMaterial list control for components\nMTOFF\nreal\nMaterial offset\nMTOH\nword\nMaterial list control for head tube\nMTOL\nstring(1000)\nMaterial List Length\nMTOPARTNUMBERS\ninteger(20)\nAdditional spooling item part numbers\nMTOQ\nstring(1000)\nMaterial take off quantity\nMTOR\nelement(20)\nExtra material list spec references\nMTOT\nword\nMaterial list control for components leave tube\nMTOX\ninteger(20)\nOld spooler addition items\nMTTRGB\ninteger(4)\nRGB matchline text colour\nMTTRGP\ninteger(4)\nRGB matchline text colour physical\nMTXR\nelement\nMaterial text reference\nMTXX\nstring(2000)\nXTEXT of material text\nMTXY\nstring(2000)\nYTEXT of material text\nMTXZ\nstring(2000)\nZTEXT of material text\nMULT\nreal\nMultiplier factor (unit definition)\nMVCEXP\ninteger(500)\nModel View content expression\nMVER\nelement\nReference to Master Vertex\nMVMDRF\nelement\nModel view definition reference\nMVVANG\nreal\nViewing angle\nMVVBEA\nreal\nViewing bearing\nMVVCAO\nlogical\nClip plane all off status\nMVVCAS\nlogical\nCap status\nMVVCCO\ninteger\nCap colour\nMVVCLS\nlogical\nClip status\nMVVCOR\nori\nClipbox direction\nMVVCPO\npos\nClipbox position\nMVVCTP\ninteger\nCamera type\nMVVCTR\npos\nViewing centre\nMVVDIR\nori\nViewing direction\nMVVDTO\nreal\nDistance to observer\nMVVELV\nreal\nViewing elevation\nMVVLIM\nreal(6)\nView limits\nMVVRAD\nreal\nViewing radius\nMXDRHO\nreal\nMaximum diameter of drilled holes\nMXEANG\nreal\nMaximum angle for edge preparation\nMXFANG\nreal\nMaximum end cut angle flanges\nMXWANG\nreal\nMaximum end cut angle web\nMYINSF\nelement\nSurface Treatment Reference\nMYOUSF\nelement\nSurface Treatment Reference\nMYSRFT\nelement\nword\nSurface Treatment Reference\n\n\n"}
{"Headers": "Attribute N", "Content": "N\nreal\n\nPosition northing\nNACCNT\ninteger\n\nNon-additive changes count\nNAMATT\nstring(200)\n\nNaming attribute\nNAME\nstring(500)\n\nName of the element\nNAMEDB\nstring\n\nDB name\nNAMESQ\nstring(700)\n\nType. sequence number and name of element\nNAMETY\nstring(700)\n\nType and name of the element\nNAMN\nstring(500)\n\nName of the element (without leading slash)\nNAMTOL\nlogical\n\nTrue if name is too long\nNAMTYP\nstring(700)\n\nType and full name of element\nNANGLE\nreal\n\nNorth angle\nNANPT\ninteger\n\nAnopoint number\nNARE\nelement\n\nReference to neutral axis\nNBEVIT\nreal(2)\n\nPathtime except starts, I-bevel\nNBEVXT\nreal(2)\n\nPathtime except starts, X-bevel\nNBEVYT\nreal(2)\n\nPathtime except starts, Y-bevel\nNBLS\ninteger\n\nNumber of blastings\nNBORE\nreal\n\nAllowable Nominal Bore\nNBRNS\ninteger\n\nNumber of burning starts\nNCDATE\ndatetime(2)\n\nNC tape date\nNCHAR\ninteger\n\nNumber of label characters\nNCHOLE\ninteger\n\nNumber of cut holes\nNCOF\npos\n\nNett centre of gravity\nNCOL\ninteger\n\nNumber of columns\nNCONNE\ninteger\n\nMismatched connections. i.e. no valid backpointer\nNCORSZ\nreal\n\nSize of the neutral core\nNCREAT\nstring(256)\n\nCreator of the nest\nNCTGAP\nreal\n\nEnd cut gap or overlap\nNCTTYP\ninteger\n\nType of end cut (Undefined, Sniped, Tight)\nNCUTNT\ninteger\n\nNumber of cutouts and notches\nNCUTOU\ninteger\n\nNumber of cutouts\nNCUTS\ninteger\n\nNumber of cuts in a mitred bend\nNDDRHO\ninteger\n\nNumber of different diameters of drilled holes\nNDFLT\nreal\n\nNumeric default value for a UDA\nNDHOLE\ninteger\n\nNumber of drilled holes\nNDTINT\ninteger(2)\n\nNC tape date\nNDTTXT\nstring(22)\n\nNC tape date text\nNENDCT\ninteger\n\nNumber of cutouts and notches\nNGMR\nelement\n\nNegative geometry set reference\nNGSD\ninteger\n\nNumber of GSDs\nNHOLE\ninteger\n\nNumber of holes\nNIDLAB\nreal\n\nPathtime except idle time for label\nNIDLT\nreal(2)\n\nPathtime except idle time\nNLABEL\ninteger\n\nNumber of labels\nNLBL\ninteger\n\nNumber of labels\nNLCOLO\ninteger\n\nNote colour\nNLCONU\ninteger\n\nNote colour number\nNLOA\nreal\n\nNominal load\nNLOFF\nreal\n\nNosing Line Offset\nNLPN\ninteger\n\nNote/framing pen\nNLSTREF\nelement\n\nNote linestyle Reference\nNLSTRT\ninteger\n\nNumber of label starts\nNLSTYL\ninteger\n\nNote linestyle\nNMARK\ninteger\n\nNumber of markings\nNMBLS\ninteger\n\nNumber of markblastings\nNMKHOL\ninteger\n\nNumber of marked holes\nNMOF\nreal(9)\n\nNett moments of inertia\nNNOTCH\ninteger\n\nNumber of notches\nNOCLIP\nlogical\n\nView no clipping flag\nNOCOL\ninteger\n\nNumber of pin jig columns\nNOCOPY\nlogical\n\nDetailing Feature Copy Flag\nNODIMS\nlogical\n\nNo Dims Flag\nNODREF\nelement\n\nRevision Number Definition\nNOECOR\ninteger\n\nNumber of earth cores\nNOEXTCREATION\nlogical\n\nLocation extract create suppression flag\nNOFF\ninteger\n\nNumber off\nNOFG\nlogical\n\nLink constraint inversion flag\nNOGRPS\ninteger\n\nNumber of groups\nNOHLRF\nlogical\n\nNoHLRFlag\nNOISEC\nstring(26)\n\nNoise category\nNOLNKP\nlogical\n\nLinked Documents distribution disabled\nNOMARK\nlogical\n\nTrue if unmarked\nNOMBIN\nreal(200)\nword\nList of valid Nominal bores in Inches\nNOMBMM\nreal(200)\nword\nList of valid Nominal bores in MM\nNOMDIA\nreal\n\nNominal Bolt Shank Diameter\nNOMDIR\ndir\n\nNominal slope direction\nNOMLEN\nreal\n\nNominal Bolt Shank Length\nNOMREF\nelement\n\nNominal bore table reference\nNOMXRF\nelement(500)\n\nReturn reference from NOMTAB element to SPECs\nNONCOR\ninteger\n\nNumber of neutral cores\nNOPGS\ninteger\n\nNumber of openings\nNOPKND\ninteger\n\nNumber Part Type: 1=alpha,2=number,3=custom\nNORM\ndir\n\nPlane normal\nNOROW\ninteger\n\nNumber of pin jig rows\nNORTHING\npos\n\nNorthing part expressed as a position\nNOSOFF\nreal\n\nNosing Offset\nNOTF\nelement\n\nCross-reference to NOTE/VNOT/SYTM\nNOTIFY\nelement(20)\n\nNotification states\nNOTREAD\ninteger\n\nNumber of treads\nNPDESC\nelement(5000)\n\nList of non primary offspring\nNPILL\ninteger\n\nNumber of jig pillars\nNPLAOR\nreal(2)\n\nNested part origin\nNPLDFA\nstring(80)\n\nNesting default file 1\nNPLDFB\nstring(80)\n\nNesting default file 2\nNPLIST\nelement(500)\n\nAll NATPs attached to route node\nNPLMIR\ninteger\n\nQuantity mirrored nested plates\nNPLNOR\ninteger\n\nQuantity normal nested plates\nNPLTOT\ninteger\n\nTotal quantity nested plates\nNPOS\npos\n\nPosition in owner\nNPOSE\nreal\n\nEasting of position wrt owner\nNPOSN\nreal\n\nNorthing of position wrt owner\nNPOST\ninteger\n\nNumber of Posts\nNPOSU\nreal\n\nUpping of position wrt owner\nNPPT\ninteger\n\nPpoint number\nNPRLEN\nreal\n\nNested profile length\nNPRSID\nstring(26)\n\nSide of nested profile\nNPRSTP\nreal(2)\n\nNested profile starting position\nNPRVEC\nreal(2)\n\nLocal rotation vector of part\nNPSIDE\nstring(80)\n\nSide of nested part\nNPXYP\nreal(2)\n\nPosition of part(x,y)\nNREL\ninteger\n\nNodal releases\nNRGRPS\ninteger\n\nNumber of groups\nNROW\ninteger\n\nNumber of rows\nNRPARM\ninteger\n\nNumber of rest plate parameters\nNRULEE\ninteger\n\nNumber of rule inconsistencies on element\nNSESS\ninteger\n\nNumber of extant sessions\nNSIHOL\ninteger\n\nNumber of sink holes\nNSIZ\nreal\n\nNominal size\nNSLHOL\ninteger\n\nNumber of slot holes\nNSPE\nelement\n\nSpecification for NOZZLE\nNSRF\nreal\n\nNett surface area\nNSSLHO\ninteger\n\nNumber of different sizes of slot holes\nNSTART\ninteger(2)\n\nNumber of non-burning starts\nNSTD\nelement\n\nNon-standard bolt length (reference to DTAB)\nNSTFAC\nreal\n\nNumber of starts - factor\nNSTRT\ninteger(3)\n\nNumber of burning starts\nNSTRTI\ninteger(2)\n\nNumber of burning starts I-bevel\nNSTRTX\ninteger(2)\n\nNumber of burning starts X-bevel\nNSTRTY\ninteger(2)\n\nNumber of burning starts Y-bevel\nNSTTYP\ninteger\n\nNesting Type\nNTEXT\nstring(13)\n\nNull text\nNTHOLE\ninteger\n\nNumber of threaded holes\nNTRLEN\nreal\n\nNeutral length\nNUCDNA\nreal\n\nDistance to nearest anchor\nNUCDNE\nreal\n\nDistance to the Nearest Edge\nNUCDNR\nelement(2)\n\nNearest Adjacent Anchor\nNULLRE\nlogical\nattr\nT/F on attributes that are null value references\nNULVAL\nstring(40)\n\nString to be used if the attribute is blank\nNUMB\ninteger\n\nNumber\nNUMBDB\ninteger\n\nDB number\nNUMCOR\ninteger\n\nNumber of cores in a cable\nNUMD\nreal\n\nGeneric Number Data Storage\nNUMOFF\ninteger\n\nNumber of Sheets in Drawing\nNUSED\ninteger\n\nNumber of used raw plates\nNVIEWF\nstring(73)\ninteger\nNeutral viewer filename\nNVOL\nreal\n\nNett volume\nNWEI\nreal\n\nNett weight\nNWELDS\ninteger\n\nNumber of attached welds on a piping component\nNXTDBN\ninteger\n\nNext DB number\nNXTDBU\ninteger\n\nNext Unique DB number\nNXTEXN\ninteger\n\nNext DB extract number\nNXTFDB\ninteger\n\nNext DB file and DB number\nNXTFLN\ninteger\n\nNext DB file number\nNXTHB\nelement\n\nReference to next (future) hub\nNXTKEY\ninteger\n\nnext UDA/UDET key\nNXTLOCATIONS\nelement(200)\n\nList of online neighbour LOCs for a LOC\n\nAttribute Name\nData Type\nQualifier\nDescription\nN\nreal\nPosition northing\nNACCNT\ninteger\nNon-additive changes count\nNAMATT\nstring(200)\nNaming attribute\nNAME\nstring(500)\nName of the element\nNAMEDB\nstring\nDB name\nNAMESQ\nstring(700)\nType. sequence number and name of element\nNAMETY\nstring(700)\nType and name of the element\nNAMN\nstring(500)\nName of the element (without leading slash)\nNAMTOL\nlogical\nTrue if name is too long\nNAMTYP\nstring(700)\nType and full name of element\nNANGLE\nreal\nNorth angle\nNANPT\ninteger\nAnopoint number\nNARE\nelement\nReference to neutral axis\nNBEVIT\nreal(2)\nPathtime except starts, I-bevel\nNBEVXT\nreal(2)\nPathtime except starts, X-bevel\nNBEVYT\nreal(2)\nPathtime except starts, Y-bevel\nNBLS\ninteger\nNumber of blastings\nNBORE\nreal\nAllowable Nominal Bore\nNBRNS\ninteger\nNumber of burning starts\nNCDATE\ndatetime(2)\nNC tape date\nNCHAR\ninteger\nNumber of label characters\nNCHOLE\ninteger\nNumber of cut holes\nNCOF\npos\nNett centre of gravity\nNCOL\ninteger\nNumber of columns\nNCONNE\ninteger\nMismatched connections. i.e. no valid backpointer\nNCORSZ\nreal\nSize of the neutral core\nNCREAT\nstring(256)\nCreator of the nest\nNCTGAP\nreal\nEnd cut gap or overlap\nNCTTYP\ninteger\nType of end cut (Undefined, Sniped, Tight)\nNCUTNT\ninteger\nNumber of cutouts and notches\nNCUTOU\ninteger\nNumber of cutouts\nNCUTS\ninteger\nNumber of cuts in a mitred bend\nNDDRHO\ninteger\nNumber of different diameters of drilled holes\nNDFLT\nreal\nNumeric default value for a UDA\nNDHOLE\ninteger\nNumber of drilled holes\nNDTINT\ninteger(2)\nNC tape date\nNDTTXT\nstring(22)\nNC tape date text\nNENDCT\ninteger\nNumber of cutouts and notches\nNGMR\nelement\nNegative geometry set reference\nNGSD\ninteger\nNumber of GSDs\nNHOLE\ninteger\nNumber of holes\nNIDLAB\nreal\nPathtime except idle time for label\nNIDLT\nreal(2)\nPathtime except idle time\nNLABEL\ninteger\nNumber of labels\nNLBL\ninteger\nNumber of labels\nNLCOLO\ninteger\nNote colour\nNLCONU\ninteger\nNote colour number\nNLOA\nreal\nNominal load\nNLOFF\nreal\nNosing Line Offset\nNLPN\ninteger\nNote/framing pen\nNLSTREF\nelement\nNote linestyle Reference\nNLSTRT\ninteger\nNumber of label starts\nNLSTYL\ninteger\nNote linestyle\nNMARK\ninteger\nNumber of markings\nNMBLS\ninteger\nNumber of markblastings\nNMKHOL\ninteger\nNumber of marked holes\nNMOF\nreal(9)\nNett moments of inertia\nNNOTCH\ninteger\nNumber of notches\nNOCLIP\nlogical\nView no clipping flag\nNOCOL\ninteger\nNumber of pin jig columns\nNOCOPY\nlogical\nDetailing Feature Copy Flag\nNODIMS\nlogical\nNo Dims Flag\nNODREF\nelement\nRevision Number Definition\nNOECOR\ninteger\nNumber of earth cores\nNOEXTCREATION\nlogical\nLocation extract create suppression flag\nNOFF\ninteger\nNumber off\nNOFG\nlogical\nLink constraint inversion flag\nNOGRPS\ninteger\nNumber of groups\nNOHLRF\nlogical\nNoHLRFlag\nNOISEC\nstring(26)\nNoise category\nNOLNKP\nlogical\nLinked Documents distribution disabled\nNOMARK\nlogical\nTrue if unmarked\nNOMBIN\nreal(200)\nword\nList of valid Nominal bores in Inches\nNOMBMM\nreal(200)\nword\nList of valid Nominal bores in MM\nNOMDIA\nreal\nNominal Bolt Shank Diameter\nNOMDIR\ndir\nNominal slope direction\nNOMLEN\nreal\nNominal Bolt Shank Length\nNOMREF\nelement\nNominal bore table reference\nNOMXRF\nelement(500)\nReturn reference from NOMTAB element to SPECs\nNONCOR\ninteger\nNumber of neutral cores\nNOPGS\ninteger\nNumber of openings\nNOPKND\ninteger\nNumber Part Type: 1=alpha,2=number,3=custom\nNORM\ndir\nPlane normal\nNOROW\ninteger\nNumber of pin jig rows\nNORTHING\npos\nNorthing part expressed as a position\nNOSOFF\nreal\nNosing Offset\nNOTF\nelement\nCross-reference to NOTE/VNOT/SYTM\nNOTIFY\nelement(20)\nNotification states\nNOTREAD\ninteger\nNumber of treads\nNPDESC\nelement(5000)\nList of non primary offspring\nNPILL\ninteger\nNumber of jig pillars\nNPLAOR\nreal(2)\nNested part origin\nNPLDFA\nstring(80)\nNesting default file 1\nNPLDFB\nstring(80)\nNesting default file 2\nNPLIST\nelement(500)\nAll NATPs attached to route node\nNPLMIR\ninteger\nQuantity mirrored nested plates\nNPLNOR\ninteger\nQuantity normal nested plates\nNPLTOT\ninteger\nTotal quantity nested plates\nNPOS\npos\nPosition in owner\nNPOSE\nreal\nEasting of position wrt owner\nNPOSN\nreal\nNorthing of position wrt owner\nNPOST\ninteger\nNumber of Posts\nNPOSU\nreal\nUpping of position wrt owner\nNPPT\ninteger\nPpoint number\nNPRLEN\nreal\nNested profile length\nNPRSID\nstring(26)\nSide of nested profile\nNPRSTP\nreal(2)\nNested profile starting position\nNPRVEC\nreal(2)\nLocal rotation vector of part\nNPSIDE\nstring(80)\nSide of nested part\nNPXYP\nreal(2)\nPosition of part(x,y)\nNREL\ninteger\nNodal releases\nNRGRPS\ninteger\nNumber of groups\nNROW\ninteger\nNumber of rows\nNRPARM\ninteger\nNumber of rest plate parameters\nNRULEE\ninteger\nNumber of rule inconsistencies on element\nNSESS\ninteger\nNumber of extant sessions\nNSIHOL\ninteger\nNumber of sink holes\nNSIZ\nreal\nNominal size\nNSLHOL\ninteger\nNumber of slot holes\nNSPE\nelement\nSpecification for NOZZLE\nNSRF\nreal\nNett surface area\nNSSLHO\ninteger\nNumber of different sizes of slot holes\nNSTART\ninteger(2)\nNumber of non-burning starts\nNSTD\nelement\nNon-standard bolt length (reference to DTAB)\nNSTFAC\nreal\nNumber of starts - factor\nNSTRT\ninteger(3)\nNumber of burning starts\nNSTRTI\ninteger(2)\nNumber of burning starts I-bevel\nNSTRTX\ninteger(2)\nNumber of burning starts X-bevel\nNSTRTY\ninteger(2)\nNumber of burning starts Y-bevel\nNSTTYP\ninteger\nNesting Type\nNTEXT\nstring(13)\nNull text\nNTHOLE\ninteger\nNumber of threaded holes\nNTRLEN\nreal\nNeutral length\nNUCDNA\nreal\nDistance to nearest anchor\nNUCDNE\nreal\nDistance to the Nearest Edge\nNUCDNR\nelement(2)\nNearest Adjacent Anchor\nNULLRE\nlogical\nattr\nT/F on attributes that are null value references\nNULVAL\nstring(40)\nString to be used if the attribute is blank\nNUMB\ninteger\nNumber\nNUMBDB\ninteger\nDB number\nNUMCOR\ninteger\nNumber of cores in a cable\nNUMD\nreal\nGeneric Number Data Storage\nNUMOFF\ninteger\nNumber of Sheets in Drawing\nNUSED\ninteger\nNumber of used raw plates\nNVIEWF\nstring(73)\ninteger\nNeutral viewer filename\nNVOL\nreal\nNett volume\nNWEI\nreal\nNett weight\nNWELDS\ninteger\nNumber of attached welds on a piping component\nNXTDBN\ninteger\nNext DB number\nNXTDBU\ninteger\nNext Unique DB number\nNXTEXN\ninteger\nNext DB extract number\nNXTFDB\ninteger\nNext DB file and DB number\nNXTFLN\ninteger\nNext DB file number\nNXTHB\nelement\nReference to next (future) hub\nNXTKEY\ninteger\nnext UDA/UDET key\nNXTLOCATIONS\nelement(200)\nList of online neighbour LOCs for a LOC\n\n\n"}
{"Headers": "Attribute O", "Content": "OANG\nreal\n\nOverlay sheet angle\nOASCR\nlogical\n\nIndicates screened or shielded\nOBCLCO\ninteger\n\nCentreline and Obscured face color\nOBCLST\ninteger\n\nCentreline and Obscured face linestyle\nOBCOLO\ninteger\n\nObscured face colour\nOBCONU\ninteger\n\nObscured face colour number\nOBFG\nlogical\n\nObstruction flag\nOBFRGB\ninteger(4)\n\nRGB obscured face colour\nOBFRGP\ninteger(4)\n\nRGB obscured face colour physical\nOBJBOOLEAN\nlogical\n\nAn RDF Statment Object representing a boolean\nOBJCD\ninteger(2)\n\nObject codes\nOBJDOUBLE\nreal\n\nAn RDF Statment Object representing a double\nOBJINTEGER\ninteger\n\nAn RDF Statment Object representing an integer\nOBJREFERENCE\nelement\n\nReference to an RDF Statement Object element\nOBPN\ninteger\n\nObscured face pen\nOBSDEP\nreal\n\nObstruction Depth\nOBST\ninteger\n\nObstruction level\nOBSTREF\nelement\n\nObscured face linestyle Reference\nOBSTYL\ninteger\n\nObscured face linestyle\nOBSWID\nreal\n\nObstruction Width\nOCCOLO\ninteger\n\nCentreline and Obscured face colour\nOCCONU\ninteger\n\nObscured Centreline colour number\nOCCRGB\ninteger(4)\n\nObscured Centreline RGB colour\nOCCRGP\ninteger(4)\n\nObscured Centreline RGB colour physical\nOCCTYP\nstring(50)\n\nOccupancy Type\nOCCUPA\nreal\n\nOccupancy\nOCOD\nstring\n\nHashed origin code\nOCONE\ninteger\n\nObjectcode 1\nOCSTYL\ninteger\n\nCentreline and Obscured face Style\nOCTWO\ninteger\n\nObjectcode 2\nOD\nreal\n\nOuter Diameter\nODESP\nreal(100)\n\nOwning design parameters\nODWGF\nstring(73)\n\nOpen DWG filename (No suffix)\nOFFDIR\ndir\n\nOffset direction applied to repeat\nOFFDIS\nreal\n\nOffset distance applied to repeat elements\nOFFSET\nreal\n\nOffset\nOFFSRF\nelement\n\nModel offset datum\nOFFTOL\nstring(1000)\n\nPPoint offset tolerance\nOFFTYP\nword\n\nOffset type: DELTA, LINEAR, RADIAL\nOGDSTS\nreal(25)\n\nDistances to openings\nOGOING\nreal\n\nOverall Going\nOKCLA\nlogical\n\nTrue if element may be claimed\nOKCLH\nlogical\n\nTrue if element and hierarchy may be claimed\nOKDROP\nlogical\n\nTrue if element may be dropped\nOKDRPH\nelement(5000)\n\nPrimary elements preventing hierarchy drop\nOKREL\nlogical\n\nTrue if element may be released\nOKRLEH\nelement(5000)\n\nPrimary elements preventing hierarchy release\nOKRLEX\nlogical\n\nTrue if element may be extract released\nOKRLH\nlogical\n\nTrue if element and hierarchy may be released\nOKUPGD\nlogical\n\nTrue if a Master DB that can be upgraded here\nOLCOLO\ninteger\n\nOutline colour\nOLCONU\ninteger\n\nOutline colour number\nOLDKEY\ninteger\n\nOld key\nOLENGTH\nreal\n\nOverall length\nOLIS\nword(2000)\n\nList of all possible owner types\nOLNRGB\ninteger(4)\n\nRGB outline colour\nOLNRGP\ninteger(4)\n\nRGB outline colour physical\nOLOFF\nreal\n\nOffsetLine offset from baseline\nOLPEN\ninteger\n\nOutline pen\nOLSTREF\nelement\n\nOutline linestyle Reference\nOLSTYL\ninteger\n\nOutline linestyle\nOMITFG\nlogical\n\nOmission flag\nONPJ\npos\n\nOwning neutral point of joint (steelwork)\nONPO\nreal(2)\n\nONTO Point, position of view in the region\nONPS\npos\n\nOwning neutral point of section (steelwork)\nOPAR\nreal(100)\n\nOwning parameters - catalogue component\nOPCLA\nword\n\nClaim Access Control Operation\nOPCOP\nword\n\nCopy-From Access Control Operation\nOPCRE\nword\n\nCreate Access Control Operation\nOPCREF\nelement\n\nOffpage connector reference\nOPDEL\nword\n\nDelete Access Control Operation\nOPDI\ndir\n\nOrigin plane direction\nOPDRO\nword\n\nDrop Access Control Operation\nOPERAT\nstring(26)\n\nOperator\nOPEXP\nword\n\nExport Access Control Operation\nOPHEIG\nreal\n\nOperational Height\nOPISS\nword\n\nIssue Access Control Operation\nOPLENG\nreal\n\nOperational Length\nOPMOD\nword\n\nModify Access Control Operation\nOPNSIZE\nreal(2)\n\nOpening size\nOPOS\npos\n\nOverlay sheet position\nOPOUT\nword\n\nOutput (DATAL) Access Control Operation\nOPREMA\nreal\n\nOperating pres. max\nOPREMI\nreal\n\nOperating pres. min\nOPTBLO\nelement\n\nOptional block name\nOPTEMP\nreal\n\nOperational temperature\nOPWIDT\nreal\n\nOperational Width\nORDARE\nreal\n\nSurface Area\nORDLIM\nlogical\n\nOrdered limits\nORDREF\nelement\n\nOrder reference\nORDWEI\nreal\n\nOrder Weight\nORGELM\nelement\n\nReference to Original Element\nORI\nori\n\nOrientation\nORIA\nreal(3)\n\nOrientation as angles\nORIF\nlogical\n\nOrientation flag\nORIGRF\nelement\n\nA reference to the element this one is cloned from\nORIN\nword\n\nDRAFT user defined symbol orientation\nORISE\nreal\n\nOverall Rising\nORNA\nstring(1000)\n\nOriginator text\nORRF\nelement\n\nOrigin reference (for templates)\nOSDWG\nstring(120)\n\nAutoCAD overlay name\nOSET\nlogical\n\nOffset/VIEW position flag\nOSFN\nstring(1024)\n\nOverlay sheet file\nOSHMTL\nelement\n\nOuter sheath material\nOSHT\nreal\n\nOvershoot\nOSHTTX\nstring(80)\n\nOvershoot text\nOSLV\nreal(12)\n\nOverlay sheet view layers visible\nOSRF\nelement\n\nOverlay sheet ref\nOSTYPE\nword\n\nShort cut for \"Type of owner\"\nOTHLEN\nreal\n\nLength of other intervals\nOTHNUM\ninteger\n\nNumber of other intervals\nOTMPMA\nreal\n\nOperating temp. max\nOTMPMI\nreal\n\nOperating temp. min\nOTRUNG\nlogical\n\nOmit Top Rung\nOUAREA\nreal\n\nOuter area\nOUPRTR\nelement\n\nOutside paint reference\nOUTD\nstring(1000)\n\nOutside diameter\nOUTFRF\nelement\n\nReference of matching outfit object\nOUTLNR\nelement\n\nSymbolic outline style reference\nOUTLOS\nelement\n\nSymbolic outline_other_side style reference\nOUTLTS\nelement\n\nSymbolic outline_this_side style reference\nOUTRADIUS\nreal\n\nOutside Radius\nOUTSD\nstring(1000)\n\nOutside shield diameter\nOUTSHD\nreal\n\nOuter sheath diameter\nOVCWIDTH\nreal\n\nOverall cables width\nOVRSH\nreal\n\nOvershoot (d-measure) for unsymmetrical flange\nOWNC\nword\n\nOwning connection type\nOWNER\nelement\n\nElement owner in database hierarchy\nOWNEXPRESSION\nstring(1000)\n\nOwner expression\nOWNEXTYPE\nstring(15)\n\nOwner expression type\nOWNLST\nelement(100)\n\nOwning hierarchy\nOWNREFERENCE\nelement\n\nENDATUM owner reference\n\nAttribute Name\nData Type\nQualifier\nDescription\nOANG\nreal\nOverlay sheet angle\nOASCR\nlogical\nIndicates screened or shielded\nOBCLCO\ninteger\nCentreline and Obscured face color\nOBCLST\ninteger\nCentreline and Obscured face linestyle\nOBCOLO\ninteger\nObscured face colour\nOBCONU\ninteger\nObscured face colour number\nOBFG\nlogical\nObstruction flag\nOBFRGB\ninteger(4)\nRGB obscured face colour\nOBFRGP\ninteger(4)\nRGB obscured face colour physical\nOBJBOOLEAN\nlogical\nAn RDF Statment Object representing a boolean\nOBJCD\ninteger(2)\nObject codes\nOBJDOUBLE\nreal\nAn RDF Statment Object representing a double\nOBJINTEGER\ninteger\nAn RDF Statment Object representing an integer\nOBJREFERENCE\nelement\nReference to an RDF Statement Object element\nOBPN\ninteger\nObscured face pen\nOBSDEP\nreal\nObstruction Depth\nOBST\ninteger\nObstruction level\nOBSTREF\nelement\nObscured face linestyle Reference\nOBSTYL\ninteger\nObscured face linestyle\nOBSWID\nreal\nObstruction Width\nOCCOLO\ninteger\nCentreline and Obscured face colour\nOCCONU\ninteger\nObscured Centreline colour number\nOCCRGB\ninteger(4)\nObscured Centreline RGB colour\nOCCRGP\ninteger(4)\nObscured Centreline RGB colour physical\nOCCTYP\nstring(50)\nOccupancy Type\nOCCUPA\nreal\nOccupancy\nOCOD\nstring\nHashed origin code\nOCONE\ninteger\nObjectcode 1\nOCSTYL\ninteger\nCentreline and Obscured face Style\nOCTWO\ninteger\nObjectcode 2\nOD\nreal\nOuter Diameter\nODESP\nreal(100)\nOwning design parameters\nODWGF\nstring(73)\nOpen DWG filename (No suffix)\nOFFDIR\ndir\nOffset direction applied to repeat\nOFFDIS\nreal\nOffset distance applied to repeat elements\nOFFSET\nreal\nOffset\nOFFSRF\nelement\nModel offset datum\nOFFTOL\nstring(1000)\nPPoint offset tolerance\nOFFTYP\nword\nOffset type: DELTA, LINEAR, RADIAL\nOGDSTS\nreal(25)\nDistances to openings\nOGOING\nreal\nOverall Going\nOKCLA\nlogical\nTrue if element may be claimed\nOKCLH\nlogical\nTrue if element and hierarchy may be claimed\nOKDROP\nlogical\nTrue if element may be dropped\nOKDRPH\nelement(5000)\nPrimary elements preventing hierarchy drop\nOKREL\nlogical\nTrue if element may be released\nOKRLEH\nelement(5000)\nPrimary elements preventing hierarchy release\nOKRLEX\nlogical\nTrue if element may be extract released\nOKRLH\nlogical\nTrue if element and hierarchy may be released\nOKUPGD\nlogical\nTrue if a Master DB that can be upgraded here\nOLCOLO\ninteger\nOutline colour\nOLCONU\ninteger\nOutline colour number\nOLDKEY\ninteger\nOld key\nOLENGTH\nreal\nOverall length\nOLIS\nword(2000)\nList of all possible owner types\nOLNRGB\ninteger(4)\nRGB outline colour\nOLNRGP\ninteger(4)\nRGB outline colour physical\nOLOFF\nreal\nOffsetLine offset from baseline\nOLPEN\ninteger\nOutline pen\nOLSTREF\nelement\nOutline linestyle Reference\nOLSTYL\ninteger\nOutline linestyle\nOMITFG\nlogical\nOmission flag\nONPJ\npos\nOwning neutral point of joint (steelwork)\nONPO\nreal(2)\nONTO Point, position of view in the region\nONPS\npos\nOwning neutral point of section (steelwork)\nOPAR\nreal(100)\nOwning parameters - catalogue component\nOPCLA\nword\nClaim Access Control Operation\nOPCOP\nword\nCopy-From Access Control Operation\nOPCRE\nword\nCreate Access Control Operation\nOPCREF\nelement\nOffpage connector reference\nOPDEL\nword\nDelete Access Control Operation\nOPDI\ndir\nOrigin plane direction\nOPDRO\nword\nDrop Access Control Operation\nOPERAT\nstring(26)\nOperator\nOPEXP\nword\nExport Access Control Operation\nOPHEIG\nreal\nOperational Height\nOPISS\nword\nIssue Access Control Operation\nOPLENG\nreal\nOperational Length\nOPMOD\nword\nModify Access Control Operation\nOPNSIZE\nreal(2)\nOpening size\nOPOS\npos\nOverlay sheet position\nOPOUT\nword\nOutput (DATAL) Access Control Operation\nOPREMA\nreal\nOperating pres. max\nOPREMI\nreal\nOperating pres. min\nOPTBLO\nelement\nOptional block name\nOPTEMP\nreal\nOperational temperature\nOPWIDT\nreal\nOperational Width\nORDARE\nreal\nSurface Area\nORDLIM\nlogical\nOrdered limits\nORDREF\nelement\nOrder reference\nORDWEI\nreal\nOrder Weight\nORGELM\nelement\nReference to Original Element\nORI\nori\nOrientation\nORIA\nreal(3)\nOrientation as angles\nORIF\nlogical\nOrientation flag\nORIGRF\nelement\nA reference to the element this one is cloned from\nORIN\nword\nDRAFT user defined symbol orientation\nORISE\nreal\nOverall Rising\nORNA\nstring(1000)\nOriginator text\nORRF\nelement\nOrigin reference (for templates)\nOSDWG\nstring(120)\nAutoCAD overlay name\nOSET\nlogical\nOffset/VIEW position flag\nOSFN\nstring(1024)\nOverlay sheet file\nOSHMTL\nelement\nOuter sheath material\nOSHT\nreal\nOvershoot\nOSHTTX\nstring(80)\nOvershoot text\nOSLV\nreal(12)\nOverlay sheet view layers visible\nOSRF\nelement\nOverlay sheet ref\nOSTYPE\nword\nShort cut for \"Type of owner\"\nOTHLEN\nreal\nLength of other intervals\nOTHNUM\ninteger\nNumber of other intervals\nOTMPMA\nreal\nOperating temp. max\nOTMPMI\nreal\nOperating temp. min\nOTRUNG\nlogical\nOmit Top Rung\nOUAREA\nreal\nOuter area\nOUPRTR\nelement\nOutside paint reference\nOUTD\nstring(1000)\nOutside diameter\nOUTFRF\nelement\nReference of matching outfit object\nOUTLNR\nelement\nSymbolic outline style reference\nOUTLOS\nelement\nSymbolic outline_other_side style reference\nOUTLTS\nelement\nSymbolic outline_this_side style reference\nOUTRADIUS\nreal\nOutside Radius\nOUTSD\nstring(1000)\nOutside shield diameter\nOUTSHD\nreal\nOuter sheath diameter\nOVCWIDTH\nreal\nOverall cables width\nOVRSH\nreal\nOvershoot (d-measure) for unsymmetrical flange\nOWNC\nword\nOwning connection type\nOWNER\nelement\nElement owner in database hierarchy\nOWNEXPRESSION\nstring(1000)\nOwner expression\nOWNEXTYPE\nstring(15)\nOwner expression type\nOWNLST\nelement(100)\nOwning hierarchy\nOWNREFERENCE\nelement\nENDATUM owner reference\n\n\n"}
{"Headers": "Attribute P", "Content": "PAAX\nstring(30)\n\nDirection of axis\nPACTDI\ndir\ninteger\nPpoint actual direction\nPAFRCO\ninteger\n\nPlot action from colour\nPAFRFT\ninteger\n\nPlot action from fillstyle\nPAFRGB\ninteger(4)\n\nRGB plot action from colour\nPAFRGP\ninteger(4)\n\nRGB plot action from colour physical\nPAFRLT\ninteger\n\nPlot action from linestyle\nPAGE\ninteger(500)\n\nPage in diagram\nPAINTO\nstring(26)\n\nPainting other side\nPAINTT\nstring(26)\n\nPainting this side\nPAIREF\nelement\n\nReference to a PAINT element\nPALIG\nreal\n\nPanel alignment\nPALLAN\nreal\ninteger\nPpoint allowed angle\nPANESI\nreal(2)\n\nPanel Size\nPANG\nstring(1000)\n\nAngle subtended\nPANOTL\nelement(100)\n\nReferences to limiting panels\nPANREF\nelement\n\nPanel reference\nPANSCD\ninteger\n\nPanel storing code\nPANSID\ninteger\n\nSide of panel\nPANSTC\ninteger\n\nPanel storing code\nPARA\nreal(100)\n\nParameters\nPARAL\nlogical\n\nTrue if tap parallel to referred seam\nPARCOLUMN\nelement\n\nParent column\nPARENT\nelement\nelemtype\nReference of ascendant element of specified type\nPARM\nreal(6)\n\nParameters\nPARNAM\nstring(256)\n\nPart name\nPARREF\nelement(10)\n\nPart reference\nPARTNUMBER\ninteger\n\nPart number of a spooled component or leave tube\nPartrf\nelement(2)\n\nManufacturing part references\nPARTYP\ninteger\n\nType of part\nPASS\nstring(7)\n\nPassword\nPASSQ\ninteger\n\nPassword Quality\nPATADV\nreal\n\nLine Pattern Advance value\nPATDEF\ninteger(20)\n\nPattern Definition\nPATH\nelement(500)\n\nPath\nPATHTM\nreal\n\nPath time for selected burning machine\nPATNAM\nstring\n\nPattern Name\nPATOCO\ninteger\n\nPlot action to colour\nPATOFF\nreal\n\nLine Pattern Offset\nPATOFT\ninteger\n\nPlot action to fillstyle\nPATOLT\ninteger\n\nPlot action to linestyle\nPATREP\nreal\n\nPattern Repeat\nPATRGB\ninteger(4)\n\nRGB plot action to colour\nPATRGP\ninteger(4)\n\nRGB plot action to colour physical\nPATYPE\nword\n\nPlot action type\nPAXI\nstring(30)\n\nAxial direction\nPBAX\nstring(30)\n\nDirection\nPBBT\nstring(1000)\n\nBottom B length\nPBDI\nstring(1000)\n\nDistance to bottom surface\nPBDM\nstring(1000)\n\nSnout bottom diameter\nPBENDNUMBER\ninteger\n\nSpooling pulled bend number\nPBOF\nstring(1000)\n\nB offset\nPBOP\npos\ninteger\nBottom of pipe\nPBOR\nstring(1000)\n\nBore\nPBSCMU\nstring(2000)\n\nFlexible Explorer Context Menu\nPBSFML\nstring(500)\n\nFlexible Explorer Formula\nPBSFTY\ninteger\n\nFlexible Explorer Formula Type\nPBSGRB\nstring(500)\n\nFlexible Explorer Grouping Formula\nPBSHDE\nlogical\n\nFlexible Explorer Hide Empty Child Nodes\nPBSICO\nstring(500)\n\nFlexible Explorer Icon\nPBSPAR\nelement(100)\n\nFlexible Explorer Parameter Nodes\nPBSQNO\nelement\n\nFlexible Explorer Query Node\nPBSRCR\nelement\n\nFlexible Explorer Recurrent Node\nPBSSRT\ninteger\n\nFlexible Explorer Sorting\nPBSTXT\nstring(500)\n\nFlexible Explorer Text\nPBSVAL\nstring(500)\n\nFlexible Explorer Value\nPBTP\nstring(1000)\n\nTop B length\nPCAX\nstring(30)\n\nDirection of C offset\nPCBT\nstring(1000)\n\nBottom C length\nPCODA\ninteger\n\nPrecision code angles\nPCODE\ninteger\n\nPrecision code\nPCODF\ninteger\n\nPrecision code fractions\nPCODI\ninteger\n\nPrecision code imperial\nPCODM\ninteger\n\nPrecision code metric\nPCOF\nstring(1000)\n\nC offset\nPCON\nstring(1000)\n\nConnection type\nPCONDE\nstring(120)\ninteger\nPpoint connection description\nPCONXF\nelement\n\nConsumer Extract Database Reference\nPCORRO\nreal\ninteger\nP Tube corrosion\nPCPIDV\nelement(10000)\n\nEnabled for project copy\nPCPSET\nelement(10000)\n\nEnabled for project copy\nPCREF\ninteger(4)\ninteger\nPpoint and ref of connected piping component\nPCRFA\nelement(500)\n\nAll spools that contain this element\nPCTP\nstring(1000)\n\nTop C length\nPCWALL\nreal\ninteger\nPpoint connect wall thickness\nPDAREF\nelement\n\nPipe data table reference\nPDEFI\nstring\n\nPrimitive Definition\nPDELE\nelement\n\nReference of matching hull object\nPDEREF\nelement\ninteger\nPipe data element reference\nPDIA\nstring(1000)\n\nDiameter parameter\nPDIR\ndir\ninteger\nPpoint direction\nPDIS\nstring(1000)\n\nDistance parameter\nPDISLF\nelement\n\nDiscipline Location Container Reference\nPDNAME\nstring(17)\n\nProduction name\nPDSHAP\nstring(1000)\n\nDuct PPOINT shape\nPDTINT\ninteger(2)\n\nProduction date\nPDTTXT\nstring(22)\n\nProduction date text\nPDWGF\nstring(73)\n\nDWG filename (with suffix)\nPECPAR\nstring\nword\nEndcut parameters\nPERS\nreal\n\nPerspective angle\nPFHIDE\nlogical\n\nPicture frame hide flag\nPFLALL\nstring(1000)\n\nFlange allowance parameter\nPFLOFF\nstring(1000)\n\nFlange offset parameter\nPFON\ninteger\n\nProjection line text font\nPFONTN\nstring(80)\n\nProjection line text font name\nPFPPOS\nreal(3)\n\nPolyface pt pos\nPFRE\nelement\n\nPfitting reference for Cofittings\nPFREQ\nlogical\n\nPicture file required flag\nPGRD\nreal\ninteger\nPpoint gradient\nPHBO\nreal\n\nPipe head bore\nPHBP\npos\n\nBottom of pipe head\nPHCO\nword\n\nPipe head connection type\nPHDR\ndir\n\nPipe head direction\nPHEI\nstring(1000)\n\nHeight\nPHGR\nreal\n\nPipe head gradient\nPHOD\nreal\n\nPipe head outside diameter\nPHPO\npos\n\nPipe head position\nPHTP\npos\n\nTop of pipe head\nPHTYP\nstring(120)\n\nPhase type of the component\nPICCNS\nelement\n\nPicture current connector style reference\nPICCOL\ninteger\n\nPicture current colour\nPICDMS\nelement\n\nPicture current dimension style reference\nPICF\nstring(73)\n\nPicture filename\nPICFD\nlogical\n\nPicture file distribution flag\nPICGBS\nelement\n\nPicture current base line ruler style reference\nPICGCS\nelement\n\nPicture current centre line ruler style reference\nPICGRS\nelement\n\nPicture current grid ruler style reference\nPICHTY\nword\n\nHard type of picture\nPICLBS\nelement\n\nPicture current label style reference\nPICLRF\nelement\n\nPicture current layer reference\nPICLST\ninteger\n\nPicture current linestyle\nPICORF\nelement\n\nPicture current owner reference\nPICRGB\ninteger(4)\n\nRGB picture current colour\nPICRGP\ninteger(4)\n\nRGB picture current colour physical\nPICSTY\nword\n\nSoft type of picture\nPICTXS\nelement\n\nPicture current text style reference\nPICVWS\nelement\n\nPicture current view style reference\nPINDEN\nreal\n\nPin Density\nPINRGB\ninteger(4)\n\nRGB pipe insulation colour\nPINRGP\ninteger(4)\n\nRGB pipe insulation colour physical\nPINSCN\ninteger\n\nPipe Insulation colour number\nPINSCO\ninteger\n\nPipe Insulation colour\nPINSST\ninteger\n\nPipe Insulation linestyle\nPIPSYM\nlogical\n\nPipe-end symbol flag\nPITCH\nreal(10)\n\nPitch of stair flight\nPITCHO\nreal\n\nAngular offset from ladder pitch\nPJUS\nstring\n\nProjection line text justification\nPKDI\nreal\n\nProportional distance along Pline\nPKEY\nword\n\nPline identifier key\nPLADEF\nlogical\n\nPanel has plates\nPLALEN\nreal\n\nRaw plate length\nPLANU\nstring(1000)\n\nPlanning Unit\nPLANV\nlogical\n\nIs Plan View\nPLAREA\nreal\n\nArea\nPLAREF\nelement\n\nManufacturing plate reference\nPLATYP\nstring(26)\n\nType of plate e.g. Plate, Bracket, Clip,...\nPLAWDT\nreal\n\nRaw plate width\nPLAX\nstring(120)\n\n2D direction angle\nPLCL\nreal\n\nProjection line clearance\nPLCLFL\nlogical\n\nProj. line clearance flag\nPLCLTX\nstring(80)\n\nProjection line clearance text\nPLCN\nlogical\nword\nPline centreline flag\nPLCO\nword\nword\nPline connection\nPLCOLO\ninteger\n\nProjection line colour\nPLCONU\ninteger\n\nProjection line colour number\nPLCRGB\ninteger(4)\n\nRGB projection line colour\nPLCRGP\ninteger(4)\n\nRGB projection line colour physical\nPLCUHO\nlogical\n\nTrue if plate has holes to be cut\nPLCUTO\nlogical\n\nTrue if plate has cutouts\nPLDE\nstring(120)\nword\nPline description\nPLDI\nreal(3)\n\nProjection line direction\nPLDRHO\nlogical\n\nTrue if plate has holes to be drilled\nPLED\ndir\n\nPlane entry direction\nPLEN\npos\nword\nPline end\nPLENCU\npos\nword\nPline end, allowing for cutback\nPLFG\nlogical\n\nPlines flag\nPLINON\nlogical\n\nPline-required flag\nPLLBL\nlogical\n\nTrue if plate has labels defined\nPLLE\ninteger(2)\nword\nPline level\nPLLIM\nlogical\n\nlimited plane\nPLLS\nword(100)\n\nList of valid Plines\nPLMKHO\nlogical\n\nTrue if plate has holes to be marked\nPLMRK\nlogical\n\nTrue if plate has marking\nPLNA\nword(100)\n\nList of available Pline names\nPLNCOL\ninteger\n\nPline colour\nPLNCON\ninteger\n\nPline colour number\nPLNOT\nlogical\n\nTrue if plate has notches\nPLNP\ninteger\n\nPline pen\nPLNRGB\ninteger(4)\n\nRGB pline colour\nPLNRGP\ninteger(4)\n\nRGB pline colour physical\nPLNSTREF\nelement\n\nPline linestyle Reference\nPLNSTY\ninteger\n\nPline linestyle\nPLOCK\nlogical\n\nTrue if element pos line is locked\nPLOR\nori\nword\nPline orientation\nPLPM\nword\n\nPlane pipe packing method - nearest or weighted\nPLPN\ninteger\n\nProjection line pen\nPLPP\nword\n\nPlane pipe positioning code word used by Router\nPLPU\nword\nword\nPline purpose\nPLRD\ndir\n\nPlane routine direction\nPLREFS\nelement(5000)\n\nPline references\nPLRF\nelement\n\nPlane reference\nPLSIHO\nlogical\n\nTrue if plate has sink holes\nPLSLHO\nlogical\n\nTrue if plate has slotted holes\nPLSP\nreal\n\nProjection line text line spacing\nPLSPTX\nstring(80)\n\nProj line text line-spacing text\nPLST\npos\nword\nPline start\nPLSTAT\ninteger\n\nPlanning status\nPLSTCU\npos\nword\nPline start, allowing for cutback\nPLSTREF\nelement\n\nProjection linestyle Reference\nPLSTYL\ninteger\n\nProjection linestyle\nPLTARE\nstring(150)\n\nPlant area\nPLTHHO\nlogical\n\nTrue if plate has holes to be threaded\nPLTU\nlogical\nword\nPline tube flag\nPLTX\nstring(1000)\n\nProjection line text\nPLTYPE\ninteger\n\nType of Grid Plane Definition\nPLVI\nword(200)\n\nList of visible Plines\nPLVIF\ninteger\nword\nPline visibility flag\nPLWW\nword\n\nPlane wall to wall positioning code used by Router\nPMAX\ninteger\n\nMaximum part number in current spool drawing\nPMLFUN\nstring(120)\n\nPML Function name\nPMLNAM\nstring(120)\n\nName of Pmlobject\nPMOD\nstring\n\nPlane mode\nPNAM\nstring(12)\n\nProperty description\nPNTOFF\nreal\n\nPoint Offset\nPNTUV\npos\n\nPoint2D\nPNTXY\nreal(2)\n\nDetailing Graphics 2D Position\nPNTXYZ\npos\n\nPoint3D\nPOCK\nword\n\nIs a branch component in a pocket\nPOD\nreal\ninteger\nPpoint outside diameter\nPOEF\nlogical\n\nPost-evaluation flag\nPOFF\nstring(1000)\n\nOffset\nPOINUM\ninteger\n\nPoint Num\nPOIS\nreal\n\nSpot value of Poissons ratio\nPOITYP\nstring(10)\n\nPoint type\nPOS\npos\n\nPosition\nPOSATT\nstring(120)\n\nName of attribute (or pseudo) to be used for label position\nPOSC\npos\n\nCorrugation Start position\nPOSCOD\ninteger\n\nPosition code for auxiliary function\nPOSE\npos\n\nEnd point position\nPOSEE\nreal\n\nEasting of end point position\nPOSEU\nreal\n\nUpping of end point position\nPOSEV\npos\n\nPosition evaluation\nPOSEY\nreal\n\nNorthing (Y coordinate) of end point position\nPOSF\nlogical\n\nPositioning flag\nPOSFOR\nstring\n\nIntelligent Text positional code word expansion style\nPOSL\nword\n\nPositioning line\nPOSMOINT\ninteger\n\nAuto labelling positioning setting (PPoint, PLine, Attribute)\nPOSN\nreal\n\nNorthing of position\nPOSNO\ninteger\n\nPosition number\nPOSPP\nlogical\n\nPosition number per phase\nPOSREF\nelement\n\nReference to point\nPOSS\npos\n\nStart point position\nPOSSE\nreal\n\nEasting of start point position\nPOSSN\nreal\n\nNorthing of start point position\nPOSSU\nreal\n\nUpping of start point position\nPOSTAN\ndir\n\nPost Tangent On a Point\nPOSTEX\nreal\n\nPost Extension\nPOSTOF\nreal\n\nVertical post offset from the routing path\nPOSTSP\nreal\n\nDefault post spacing\nPOSU\nreal\n\nUpping of position\nPOSUV\nreal(2)\n\nRest plate position\nPOSX\nreal\n\nEasting (X coordinate) of position\nPOSXP\ninteger(500)\n\nPosition expression\nPOWFAC\nreal\n\nPowder point factor\nPPANFL\nreal\n\nPipe Piece Angle between flanges\nPPAREF\nelement\n\nPipe Piece Arrive Reference\nPPARM\nreal(6)\n\nProfile parameters\nPPBO\nreal\ninteger\nPpoint bore\nPPBRAD\nreal(500)\n\nPipe piece bend radii\nPPBRAT\nreal(500)\n\nPipe piece bend ratio\nPPCNBD\nlogical\n\nPipe piece contains bends\nPPCO\nword\ninteger\nPpoint connection type\nPPCOU\ninteger\n\nNumber of valid Ppoints\nPPCUTL\nreal\n\nCut Length\nPPDE\nstring(120)\ninteger\nPpoint description\nPPDI\ninteger\n\nPpoint number for direction\nPPEFR\nlogical\n\nLeave flange required\nPPER\nelement\n\nPipe piece end reference\nPPEXST\nlogical\ninteger\nTrue if Ppoint exists\nPPFINL\nreal\n\nFinished Length\nPPFMCV\nlogical\n\nPipe piece fabrication machines verified\nPPHEI\nreal\ninteger\nPpoint height\nPPLREF\nelement\n\nPipe Piece Leave Reference\nPPLS\ninteger(200)\n\nList of valid Ppoints\nPPMODI\nlogical\n\nPipe piece modified\nPPNU\ninteger\n\nDesign PPoint/Port number\nPPOFFT\nreal\ninteger\nPpoint offset\nPPOINX\nstring(480)\n\nPpoint information\nPPOS\npos\ninteger\nPpoint position\nPPRFA\nelement(500)\n\nAll components in the PipePiece\nPPRO\nstring(1000)\n\nParameterised Property Expression\nPPSFR\nlogical\n\nArrive flange required\nPPSHAP\nword\ninteger\nPPoint Connection shape\nPPSK\nword\ninteger\nPpoint pskey\nPPSR\nelement\n\nPipe piece start reference\nPPSTU\nelement\n\nPipe Piece Specification\nPPUR\nword\ninteger\nPpoint purpose\nPPVBMC\nelement\n\nReturn the bending machine IF the pipe piece is verified\nPPVERI\nword\n\nPipe piece verified\nPPVI\ninteger(200)\n\nList of visible Ppoints\nPPVIF\ninteger\ninteger\nPpoint visibility flag\nPPVWMC\nelement\n\nReturn the welding machine IF the pipe piece is verified\nPPWID\nreal\ninteger\nPpoint width\nPQAANG\nreal\ninteger\nAngle between alignment direction of specified pp and adjacent component\nPQANG\nreal\ninteger\nAngle between specified Ppoint and adjacent component\nPQBORE\nlogical\ninteger\nTRUE if specified Ppoint has same bore as adjacent\nPQCON\nlogical\ninteger\nTRUE if leave Ppoint has Correct connection type\nPQOFF\nreal\ninteger\nOffset between specified Ppoint and adjacent component\nPQUA\nword\n\nProperty qualifier\nPRAD\nstring(1000)\n\nRadius\nPRAV\nreal\n\nAverage pressure\nPRBCD\ninteger\n\nBasic profile type code\nPRBLNK\nstring\n\nPrimitive blanking flag\nPRBMAR\nreal\n\nPrimitive blanking margin\nPRBMPH\nreal\n\nPrimitive blanking margin physical\nPRBMTX\nstring(80)\n\nPrimitive blanking margin text\nPRBTYP\ninteger\n\nBasic Profile Type\nPRCODE\nstring(16)\n\nShort code\nPRCONV\nstring(120)\n\nConvertor for property, not for use by end user.\nPRCTIM\ninteger\n\nProcessing time in seconds\nPRCUHO\nlogical(6)\n\nTrue if profile has holes to be cut in this surface\nPRCUTO\nlogical(6)\n\nTrue if profile has cutouts in this surface\nPRDBSN\ninteger\n\nStart DB Number\nPRDDATE\ndatetime(2)\n\nProduction date\nPRDDBF\nelement\n\nReference to the Master DB\nPRDE\nstring(250)\nword\nProperty default\nPRDES\nstring(250)\nword\nProperty value from design\nPRDLS\nword(2000)\n\nList of all design properties\nPRDREFERENCE\nelement\n\nReference to an RDF Statement Predicate element\nPRDRHO\nlogical(6)\n\nTrue if profile has drill holes in this surface\nPRECED\ninteger\n\nPrecedence\nPREDIT\nstring(120)\n\nEditor for property, not for use by end user\nPREF\nlogical\n\nPre-evaluation flag\nPREFIX\nstring(50)\n\nPrefix\nPREFSP\nlogical\n\nPreferred Specification\nPREPPR\nstring(26)\n\nPreparation information\nPREPT\nreal\n\nPreparation time\nPRES\nreal\n\nPressure\nPRESTR\nlogical\n\nPlane restricted\nPRETAN\ndir\n\nPre Tangent On a Point\nPRFC\nstring(1000)\n\nPressure factor\nPRFELE\nelement\n\nCableway profile element\nPRFG\nlogical\n\nProfile flag\nPRFL\nstring(120)\n\nProfile\nPRFMAT\nstring(80)\n\nDetailing Item Profile Material\nPRFOBS\ninteger\n\nCableway profile obstructions\nPRGLDF\nelement\n\nReference to Project Definition element\nPRICEE\nreal\n\nPrice estimate\nPRIDBV\nelement\n\nPrimary Database View\nPRIMDB\nstring\n\nGlobal status of DB, primary or secondary\nPRIMEM\nlogical\n\nPrimary member\nPRIMSY\nelement\n\nReference of the primary system elements\nPRIMTY\nlogical\n\nTrue if element is primary\nPRITYP\nstring(120)\n\nGpart Primary type\nPRJD\nstring(120)\n\nProject description\nPRJID\nstring(17)\n\nProject id. Available on STAT or GSTAT element\nPRJL\nlogical\n\nProject lock\nPRJMAN\nstring(256)\n\nProject manager\nPRJN\nstring(17)\n\nProject number\nPRJSTA\nword\n\nAccess Control project status\nPRLBL\nlogical(6)\n\nTrue if profile has labels defined in this surface\nPRLS\nword(200)\n\nList of valid properties - catalogue or design\nPRMA\nreal\n\nMaximum pressure\nPRMDBF\nelement\n\nReference of MDB Element\nPRMDIR\ndir\n\nPrimary Direction\nPRMI\nreal\n\nMinimum pressure\nPRMKHO\nlogical(6)\n\nTrue if profile has holes to be marked in surfaces\nPRMLOC\nelement\n\nPrimary location\nPRMMEM\nlogical\n\nTrue if there are any primary elements amongst descendants\nPRMOWN\nelement\n\nPrimary owning element (will be itself if primary)\nPRMRF\nelement\n\nPrimary Location Element\nPRMRK\nlogical(6)\n\nTrue if profile has marking defined in this surface\nPRMTAG\nelement\n\nAssociated Primary Element\nPRMVI\nlogical\n\nDraughting primitive visibility\nPRNOT\nlogical(6)\n\nTrue if profile has notches in this surface\nPROCDE\nstring(600)\n\nPROCess DEscription\nPRODID\nstring(26)\n\nProduct id\nPRODRF\nelement\n\nReference to Production Object\nPRODUCTION\nreal\n\nProduction level radiation\nPROJID\ninteger(3)\n\nPROJID - on the DB element\nPROJIDTEXT\nstring(100)\nword\nProject id\nPROLEN\nreal\n\nRaw profile length\nPROMIX\ninteger\n\nIndex of Promote Status Value\nPROP\nstring(250)\nword\nProperty value from catalogue or design dataset\nPROPG\nlogical\n\nDB propagation flag\nPROPRE\nreal\nattr\nCalculated Property Real Attribute\nPROPST\nelement(500)\n\nProperty set reference array\nPROPTYPE\nword\nword\nProperty Dimension from catalogue or design dataset\nPROSID\ninteger\n\nPlate side with most profile markings\nProTyp\ninteger\n\nProfile type\nPROUT\nword(2000)\n\nList of all properties excluding hidden ones, i.e as output in \"Q ATT\"\nPRPDIR\ninteger\n\nPerpendicular to location direction\nPRPNDC\nlogical\n\nTrue if the profile is mounted perpendicularly along its entire trace\nPRPU\nword\nword\nProperty purpose\nPRREF\nelement\n\nDataset reference\nPRSIHO\nlogical(6)\n\nTrue if profile has sink holes in this surface\nPRSLHO\nlogical(6)\n\nTrue if profile has slotted holes in this surface\nPRSTAT\ninteger\n\nWelding Element Production Status\nPRTHHO\nlogical(6)\n\nTrue if profile has threaded holes in this surface\nPRTI\nstring(120)\nword\nProperty title\nPRTIDL\nstring(132)\n\nLong part id\nPRTIDM\nstring(132)\nword\nModule part id\nPRTIDS\nstring(132)\n\nShort part id\nPRTLST\nstring(26)\n\nParts list name\nPRTREF\nelement\n\nPart reference\nPRTRTX\nstring(1000)\nword\nPart element R text\nPRTSTX\nstring(1000)\nword\nPart element S text\nPRTTTX\nstring(1000)\nword\nPart element T text\nPRTXRF\nelement(500)\n\nReturn reference from PART element to SPCOs\nPRVRF\nelement\n\nReference to previous owner of DB\nPRVSES\ninteger\ninteger\nPrevious Session to that specified\nPSARFA\nelement(500)\n\nPipespool arrive references\nPSATTS\nword(500)\n\nList of pseudo attributes\nPSESS\ninteger\ninteger\nPrevious session number\nPSFG\nlogical\n\nPiping component symbol flag\nPSHAPE\nstring(25)\n\nProfile shape symbol text\nPSIZE\nreal(2)\n\nPanel size\nPSKE\nword\n\nKey for ISODRAFT\nPSLDIR\ndir\ninteger\nPpoint slope direction\nPSLRFA\nelement(500)\n\nPipespool leave references\nPSPE\nelement\n\nPipe specification\nPSPIN\ninteger\n\nPpoint number showing position of spindle\nPSPR\nlogical\n\nPipe Spool Previously Released\nPSPREFERENCE\nelement\n\nAssociated POINSP Reference\nPSTAT\ninteger\n\nPlane status\nPSTF\nelement\n\nPointset reference\nPSTLENGTH\nreal\n\nPipe stock length\nPSTR\nelement\n\nStructural Pline set reference\nPSTYP\nword\n\nSpool Type\nPSVLD\nlogical\n\nPipespool valid\nPTADEG\nreal\n\nProjection Text Angle Degrees\nPTADGP\nreal\n\nProjection Text Angle Degrees\nPTAN\nstring\n\nProjection line text angle flag\nPTBO\nreal\n\nPipe tail bore\nPTBP\npos\n\nBottom of pipe tail\nPTCDI\nstring(1000)\n\nParameterised direction\nPTCH\nreal\n\nProjection text character height\nPTCHTX\nstring(80)\n\nProj text char height text\nPTCO\nword\n\nPipe tail connection type\nPTCOLO\ninteger\n\nProjection text colour\nPTCONU\ninteger\n\nProjection text colour number\nPTCPOS\nstring(250)\n\nParameterised position\nPTDI\nstring(1000)\n\nDistance to top surface\nPTDM\nstring(1000)\n\nSnout top diameter\nPTDR\ndir\n\nPipe tail direction\nPTDTRE\nelement\n\nPart Data set reference\nPTEM\nreal\n\nPipework temperature\nPTEPOS\nstring(250)\n\nParameterised end position\nPTFA\nelement(3)\n\nPoint references\nPTGR\nreal\n\nPipe tail gradient\nPTLH\nreal\n\nProjection text letter height\nPTLHTX\nstring(80)\n\nProjection text letter height text\nPTNB\ninteger(20)\n\nOld spooler bolt part number\nPTNH\ninteger\n\nOld spooler head tube part number\nPTNO\ninteger\n\nOld spooler component part number\nPTNT\ninteger\n\nOld spooler tube part number\nPTOD\nreal\n\nPipe tail outside diameter\nPTOF\nreal(2)\n\nProjection line text offset\nPTOFTX\nstring(80)\n\nProjection line text offset text\nPTOLER\nreal\n\nTolerance on a design property\nPTOP\npos\ninteger\nTop of pipe\nPTORDR\ninteger\n\nOrder of part in rule\nPTPN\ninteger\n\nProjection text pen\nPTPO\npos\n\nPipe tail position\nPTPTXT\nstring(26)\n\nProfile type. e.g. Stiffener, Flange,...\nPTRE\nelement\n\nPoint set reference\nPTRF\nelement\n\nPoint reference\nPTS\ninteger(6)\n\nLine definition points\nPTSP\nstring(120)\n\nPaint specification\nPTSPOS\nstring(250)\n\nParameterised start position\nPTTP\npos\n\nTop of pipe tail\nPTXRGB\ninteger(4)\n\nRGB projection text colour\nPTXRGP\ninteger(4)\n\nRGB projection text colour physical\nPTYP\nword\n\nProperty type\nPUCD\nstring(120)\n\nPaint Code\nPUINCD\nstring(120)\n\nInside punch code\nPULLLS\nelement(500)\n\nPull pit list\nPULTSN\nreal\n\nPulling tension\nPUNCHT\nreal\n\nPunching time\nPUNI\nstring(32)\n\nData Property Units\nPUOUCD\nstring(120)\n\nOutside punch code\nPURCH\nstring(26)\n\nPurchase information\nPURP\nword\n\nDescription code word\nPVIF\ninteger\n\nPPoint/Pline visibility filter\nPVNO\ninteger\n\nPicture version number\nPWALLT\nreal\ninteger\nPpoint wall thickness\nPWAS\nstring(1000)\n\nPercentage wastage factor\nPWID\nstring(1000)\n\nWidth / Wall thickness\nPWWFAC\nreal\n\nPowder way factor\nPX\nstring(1000)\n\nCartesian X position\nPXBS\nstring(1000)\n\nInclination of bottom surface to local X axis\nPXLE\nstring(1000)\n\nX length\nPXTS\nstring(1000)\n\nInclination of top surface to local X axis\nPY\nstring(1000)\n\nCartesian Y position\nPYBS\nstring(1000)\n\nInclination of bottom surface to local Y axis\nPYLE\nstring(1000)\n\nY length\nPYTS\nstring(1000)\n\nInclination of top surface to local Y axis\nPZ\nstring(1000)\n\nCartesian Z position\nPZAXI\nstring(30)\n\nAlignment axial direction\nPZDIR\ndir\ninteger\nPpoint alignment direction\nPZLE\nstring(1000)\n\nZ length\n\nAttribute Name\nData Type\nQualifier\nDescription\nPAAX\nstring(30)\nDirection of axis\nPACTDI\ndir\ninteger\nPpoint actual direction\nPAFRCO\ninteger\nPlot action from colour\nPAFRFT\ninteger\nPlot action from fillstyle\nPAFRGB\ninteger(4)\nRGB plot action from colour\nPAFRGP\ninteger(4)\nRGB plot action from colour physical\nPAFRLT\ninteger\nPlot action from linestyle\nPAGE\ninteger(500)\nPage in diagram\nPAINTO\nstring(26)\nPainting other side\nPAINTT\nstring(26)\nPainting this side\nPAIREF\nelement\nReference to a PAINT element\nPALIG\nreal\nPanel alignment\nPALLAN\nreal\ninteger\nPpoint allowed angle\nPANESI\nreal(2)\nPanel Size\nPANG\nstring(1000)\nAngle subtended\nPANOTL\nelement(100)\nReferences to limiting panels\nPANREF\nelement\nPanel reference\nPANSCD\ninteger\nPanel storing code\nPANSID\ninteger\nSide of panel\nPANSTC\ninteger\nPanel storing code\nPARA\nreal(100)\nParameters\nPARAL\nlogical\nTrue if tap parallel to referred seam\nPARCOLUMN\nelement\nParent column\nPARENT\nelement\nelemtype\nReference of ascendant element of specified type\nPARM\nreal(6)\nParameters\nPARNAM\nstring(256)\nPart name\nPARREF\nelement(10)\nPart reference\nPARTNUMBER\ninteger\nPart number of a spooled component or leave tube\nPartrf\nelement(2)\nManufacturing part references\nPARTYP\ninteger\nType of part\nPASS\nstring(7)\nPassword\nPASSQ\ninteger\nPassword Quality\nPATADV\nreal\nLine Pattern Advance value\nPATDEF\ninteger(20)\nPattern Definition\nPATH\nelement(500)\nPath\nPATHTM\nreal\nPath time for selected burning machine\nPATNAM\nstring\nPattern Name\nPATOCO\ninteger\nPlot action to colour\nPATOFF\nreal\nLine Pattern Offset\nPATOFT\ninteger\nPlot action to fillstyle\nPATOLT\ninteger\nPlot action to linestyle\nPATREP\nreal\nPattern Repeat\nPATRGB\ninteger(4)\nRGB plot action to colour\nPATRGP\ninteger(4)\nRGB plot action to colour physical\nPATYPE\nword\nPlot action type\nPAXI\nstring(30)\nAxial direction\nPBAX\nstring(30)\nDirection\nPBBT\nstring(1000)\nBottom B length\nPBDI\nstring(1000)\nDistance to bottom surface\nPBDM\nstring(1000)\nSnout bottom diameter\nPBENDNUMBER\ninteger\nSpooling pulled bend number\nPBOF\nstring(1000)\nB offset\nPBOP\npos\ninteger\nBottom of pipe\nPBOR\nstring(1000)\nBore\nPBSCMU\nstring(2000)\nFlexible Explorer Context Menu\nPBSFML\nstring(500)\nFlexible Explorer Formula\nPBSFTY\ninteger\nFlexible Explorer Formula Type\nPBSGRB\nstring(500)\nFlexible Explorer Grouping Formula\nPBSHDE\nlogical\nFlexible Explorer Hide Empty Child Nodes\nPBSICO\nstring(500)\nFlexible Explorer Icon\nPBSPAR\nelement(100)\nFlexible Explorer Parameter Nodes\nPBSQNO\nelement\nFlexible Explorer Query Node\nPBSRCR\nelement\nFlexible Explorer Recurrent Node\nPBSSRT\ninteger\nFlexible Explorer Sorting\nPBSTXT\nstring(500)\nFlexible Explorer Text\nPBSVAL\nstring(500)\nFlexible Explorer Value\nPBTP\nstring(1000)\nTop B length\nPCAX\nstring(30)\nDirection of C offset\nPCBT\nstring(1000)\nBottom C length\nPCODA\ninteger\nPrecision code angles\nPCODE\ninteger\nPrecision code\nPCODF\ninteger\nPrecision code fractions\nPCODI\ninteger\nPrecision code imperial\nPCODM\ninteger\nPrecision code metric\nPCOF\nstring(1000)\nC offset\nPCON\nstring(1000)\nConnection type\nPCONDE\nstring(120)\ninteger\nPpoint connection description\nPCONXF\nelement\nConsumer Extract Database Reference\nPCORRO\nreal\ninteger\nP Tube corrosion\nPCPIDV\nelement(10000)\nEnabled for project copy\nPCPSET\nelement(10000)\nEnabled for project copy\nPCREF\ninteger(4)\ninteger\nPpoint and ref of connected piping component\nPCRFA\nelement(500)\nAll spools that contain this element\nPCTP\nstring(1000)\nTop C length\nPCWALL\nreal\ninteger\nPpoint connect wall thickness\nPDAREF\nelement\nPipe data table reference\nPDEFI\nstring\nPrimitive Definition\nPDELE\nelement\nReference of matching hull object\nPDEREF\nelement\ninteger\nPipe data element reference\nPDIA\nstring(1000)\nDiameter parameter\nPDIR\ndir\ninteger\nPpoint direction\nPDIS\nstring(1000)\nDistance parameter\nPDISLF\nelement\nDiscipline Location Container Reference\nPDNAME\nstring(17)\nProduction name\nPDSHAP\nstring(1000)\nDuct PPOINT shape\nPDTINT\ninteger(2)\nProduction date\nPDTTXT\nstring(22)\nProduction date text\nPDWGF\nstring(73)\nDWG filename (with suffix)\nPECPAR\nstring\nword\nEndcut parameters\nPERS\nreal\nPerspective angle\nPFHIDE\nlogical\nPicture frame hide flag\nPFLALL\nstring(1000)\nFlange allowance parameter\nPFLOFF\nstring(1000)\nFlange offset parameter\nPFON\ninteger\nProjection line text font\nPFONTN\nstring(80)\nProjection line text font name\nPFPPOS\nreal(3)\nPolyface pt pos\nPFRE\nelement\nPfitting reference for Cofittings\nPFREQ\nlogical\nPicture file required flag\nPGRD\nreal\ninteger\nPpoint gradient\nPHBO\nreal\nPipe head bore\nPHBP\npos\nBottom of pipe head\nPHCO\nword\nPipe head connection type\nPHDR\ndir\nPipe head direction\nPHEI\nstring(1000)\nHeight\nPHGR\nreal\nPipe head gradient\nPHOD\nreal\nPipe head outside diameter\nPHPO\npos\nPipe head position\nPHTP\npos\nTop of pipe head\nPHTYP\nstring(120)\nPhase type of the component\nPICCNS\nelement\nPicture current connector style reference\nPICCOL\ninteger\nPicture current colour\nPICDMS\nelement\nPicture current dimension style reference\nPICF\nstring(73)\nPicture filename\nPICFD\nlogical\nPicture file distribution flag\nPICGBS\nelement\nPicture current base line ruler style reference\nPICGCS\nelement\nPicture current centre line ruler style reference\nPICGRS\nelement\nPicture current grid ruler style reference\nPICHTY\nword\nHard type of picture\nPICLBS\nelement\nPicture current label style reference\nPICLRF\nelement\nPicture current layer reference\nPICLST\ninteger\nPicture current linestyle\nPICORF\nelement\nPicture current owner reference\nPICRGB\ninteger(4)\nRGB picture current colour\nPICRGP\ninteger(4)\nRGB picture current colour physical\nPICSTY\nword\nSoft type of picture\nPICTXS\nelement\nPicture current text style reference\nPICVWS\nelement\nPicture current view style reference\nPINDEN\nreal\nPin Density\nPINRGB\ninteger(4)\nRGB pipe insulation colour\nPINRGP\ninteger(4)\nRGB pipe insulation colour physical\nPINSCN\ninteger\nPipe Insulation colour number\nPINSCO\ninteger\nPipe Insulation colour\nPINSST\ninteger\nPipe Insulation linestyle\nPIPSYM\nlogical\nPipe-end symbol flag\nPITCH\nreal(10)\nPitch of stair flight\nPITCHO\nreal\nAngular offset from ladder pitch\nPJUS\nstring\nProjection line text justification\nPKDI\nreal\nProportional distance along Pline\nPKEY\nword\nPline identifier key\nPLADEF\nlogical\nPanel has plates\nPLALEN\nreal\nRaw plate length\nPLANU\nstring(1000)\nPlanning Unit\nPLANV\nlogical\nIs Plan View\nPLAREA\nreal\nArea\nPLAREF\nelement\nManufacturing plate reference\nPLATYP\nstring(26)\nType of plate e.g. Plate, Bracket, Clip,...\nPLAWDT\nreal\nRaw plate width\nPLAX\nstring(120)\n2D direction angle\nPLCL\nreal\nProjection line clearance\nPLCLFL\nlogical\nProj. line clearance flag\nPLCLTX\nstring(80)\nProjection line clearance text\nPLCN\nlogical\nword\nPline centreline flag\nPLCO\nword\nword\nPline connection\nPLCOLO\ninteger\nProjection line colour\nPLCONU\ninteger\nProjection line colour number\nPLCRGB\ninteger(4)\nRGB projection line colour\nPLCRGP\ninteger(4)\nRGB projection line colour physical\nPLCUHO\nlogical\nTrue if plate has holes to be cut\nPLCUTO\nlogical\nTrue if plate has cutouts\nPLDE\nstring(120)\nword\nPline description\nPLDI\nreal(3)\nProjection line direction\nPLDRHO\nlogical\nTrue if plate has holes to be drilled\nPLED\ndir\nPlane entry direction\nPLEN\npos\nword\nPline end\nPLENCU\npos\nword\nPline end, allowing for cutback\nPLFG\nlogical\nPlines flag\nPLINON\nlogical\nPline-required flag\nPLLBL\nlogical\nTrue if plate has labels defined\nPLLE\ninteger(2)\nword\nPline level\nPLLIM\nlogical\nlimited plane\nPLLS\nword(100)\nList of valid Plines\nPLMKHO\nlogical\nTrue if plate has holes to be marked\nPLMRK\nlogical\nTrue if plate has marking\nPLNA\nword(100)\nList of available Pline names\nPLNCOL\ninteger\nPline colour\nPLNCON\ninteger\nPline colour number\nPLNOT\nlogical\nTrue if plate has notches\nPLNP\ninteger\nPline pen\nPLNRGB\ninteger(4)\nRGB pline colour\nPLNRGP\ninteger(4)\nRGB pline colour physical\nPLNSTREF\nelement\nPline linestyle Reference\nPLNSTY\ninteger\nPline linestyle\nPLOCK\nlogical\nTrue if element pos line is locked\nPLOR\nori\nword\nPline orientation\nPLPM\nword\nPlane pipe packing method - nearest or weighted\nPLPN\ninteger\nProjection line pen\nPLPP\nword\nPlane pipe positioning code word used by Router\nPLPU\nword\nword\nPline purpose\nPLRD\ndir\nPlane routine direction\nPLREFS\nelement(5000)\nPline references\nPLRF\nelement\nPlane reference\nPLSIHO\nlogical\nTrue if plate has sink holes\nPLSLHO\nlogical\nTrue if plate has slotted holes\nPLSP\nreal\nProjection line text line spacing\nPLSPTX\nstring(80)\nProj line text line-spacing text\nPLST\npos\nword\nPline start\nPLSTAT\ninteger\nPlanning status\nPLSTCU\npos\nword\nPline start, allowing for cutback\nPLSTREF\nelement\nProjection linestyle Reference\nPLSTYL\ninteger\nProjection linestyle\nPLTARE\nstring(150)\nPlant area\nPLTHHO\nlogical\nTrue if plate has holes to be threaded\nPLTU\nlogical\nword\nPline tube flag\nPLTX\nstring(1000)\nProjection line text\nPLTYPE\ninteger\nType of Grid Plane Definition\nPLVI\nword(200)\nList of visible Plines\nPLVIF\ninteger\nword\nPline visibility flag\nPLWW\nword\nPlane wall to wall positioning code used by Router\nPMAX\ninteger\nMaximum part number in current spool drawing\nPMLFUN\nstring(120)\nPML Function name\nPMLNAM\nstring(120)\nName of Pmlobject\nPMOD\nstring\nPlane mode\nPNAM\nstring(12)\nProperty description\nPNTOFF\nreal\nPoint Offset\nPNTUV\npos\nPoint2D\nPNTXY\nreal(2)\nDetailing Graphics 2D Position\nPNTXYZ\npos\nPoint3D\nPOCK\nword\nIs a branch component in a pocket\nPOD\nreal\ninteger\nPpoint outside diameter\nPOEF\nlogical\nPost-evaluation flag\nPOFF\nstring(1000)\nOffset\nPOINUM\ninteger\nPoint Num\nPOIS\nreal\nSpot value of Poissons ratio\nPOITYP\nstring(10)\nPoint type\nPOS\npos\nPosition\nPOSATT\nstring(120)\nName of attribute (or pseudo) to be used for label position\nPOSC\npos\nCorrugation Start position\nPOSCOD\ninteger\nPosition code for auxiliary function\nPOSE\npos\nEnd point position\nPOSEE\nreal\nEasting of end point position\nPOSEU\nreal\nUpping of end point position\nPOSEV\npos\nPosition evaluation\nPOSEY\nreal\nNorthing (Y coordinate) of end point position\nPOSF\nlogical\nPositioning flag\nPOSFOR\nstring\nIntelligent Text positional code word expansion style\nPOSL\nword\nPositioning line\nPOSMOINT\ninteger\nAuto labelling positioning setting (PPoint, PLine, Attribute)\nPOSN\nreal\nNorthing of position\nPOSNO\ninteger\nPosition number\nPOSPP\nlogical\nPosition number per phase\nPOSREF\nelement\nReference to point\nPOSS\npos\nStart point position\nPOSSE\nreal\nEasting of start point position\nPOSSN\nreal\nNorthing of start point position\nPOSSU\nreal\nUpping of start point position\nPOSTAN\ndir\nPost Tangent On a Point\nPOSTEX\nreal\nPost Extension\nPOSTOF\nreal\nVertical post offset from the routing path\nPOSTSP\nreal\nDefault post spacing\nPOSU\nreal\nUpping of position\nPOSUV\nreal(2)\nRest plate position\nPOSX\nreal\nEasting (X coordinate) of position\nPOSXP\ninteger(500)\nPosition expression\nPOWFAC\nreal\nPowder point factor\nPPANFL\nreal\nPipe Piece Angle between flanges\nPPAREF\nelement\nPipe Piece Arrive Reference\nPPARM\nreal(6)\nProfile parameters\nPPBO\nreal\ninteger\nPpoint bore\nPPBRAD\nreal(500)\nPipe piece bend radii\nPPBRAT\nreal(500)\nPipe piece bend ratio\nPPCNBD\nlogical\nPipe piece contains bends\nPPCO\nword\ninteger\nPpoint connection type\nPPCOU\ninteger\nNumber of valid Ppoints\nPPCUTL\nreal\nCut Length\nPPDE\nstring(120)\ninteger\nPpoint description\nPPDI\ninteger\nPpoint number for direction\nPPEFR\nlogical\nLeave flange required\nPPER\nelement\nPipe piece end reference\nPPEXST\nlogical\ninteger\nTrue if Ppoint exists\nPPFINL\nreal\nFinished Length\nPPFMCV\nlogical\nPipe piece fabrication machines verified\nPPHEI\nreal\ninteger\nPpoint height\nPPLREF\nelement\nPipe Piece Leave Reference\nPPLS\ninteger(200)\nList of valid Ppoints\nPPMODI\nlogical\nPipe piece modified\nPPNU\ninteger\nDesign PPoint/Port number\nPPOFFT\nreal\ninteger\nPpoint offset\nPPOINX\nstring(480)\nPpoint information\nPPOS\npos\ninteger\nPpoint position\nPPRFA\nelement(500)\nAll components in the PipePiece\nPPRO\nstring(1000)\nParameterised Property Expression\nPPSFR\nlogical\nArrive flange required\nPPSHAP\nword\ninteger\nPPoint Connection shape\nPPSK\nword\ninteger\nPpoint pskey\nPPSR\nelement\nPipe piece start reference\nPPSTU\nelement\nPipe Piece Specification\nPPUR\nword\ninteger\nPpoint purpose\nPPVBMC\neleme"}
{"Headers": "Attribute Q", "Content": "QALLSI\ninteger\n\nAllocSize\nQMXUPT\ninteger\n\nMaxUserPtr\nQNELEM\ninteger\n\nQNoElem\nQOBJSI\ninteger\n\nObjectSize\nQTYPE\nword\n\nType of question\nQUACD\ninteger\n\nQuality code\nQUAL\ninteger\n\nQualifier\nQUAN\ninteger\n\nQuantity (always one!)\nQUAPAI\nstring(26)\n\nPaint specification\nQUATXT\nstring(26)\n\nQuality\nQUES\nword\n\nQuestion\nQUSEXP\ninteger(250)\n\nquestion expression\n\nAttribute Name\nData Type\nQualifier\nDescription\nQALLSI\ninteger\nAllocSize\nQMXUPT\ninteger\nMaxUserPtr\nQNELEM\ninteger\nQNoElem\nQOBJSI\ninteger\nObjectSize\nQTYPE\nword\nType of question\nQUACD\ninteger\nQuality code\nQUAL\ninteger\nQualifier\nQUAN\ninteger\nQuantity (always one!)\nQUAPAI\nstring(26)\nPaint specification\nQUATXT\nstring(26)\nQuality\nQUES\nword\nQuestion\nQUSEXP\ninteger(250)\nquestion expression\n\n\n"}
{"Headers": "Attribute R", "Content": "RADD\nreal\n\nDefault Radius value\nRADF\nreal\n\nRadius attractor factor\nRADI\nreal\n\nRadius\nRADIPLANE\nlogical\n\nRadial plane flag\nRADISP\nreal(10000)\n\nRadius Spacing\nRADL\nreal(2)\n\nRadius limits (Min/Max)\nRADS\nlogical\n\nRadius set flag - ignore Radius values if FALSE\nRAILHE\nreal(15)\n\nHeights of rails measured from path\nRAILTR\nreal(100)\n\nRail Trim\nRANANG\nreal(32)\nelemtype\nRange of available angles for bends and elbows\nRANEQUIP\nreal\n\nRange of the nearest equipment\nRANRAD\nreal(32)\nelemtype\nRange of available radii\nRATFAC\nreal\n\nRationalisation factor\nRATI\nreal\n\nPressure rating\nRATPOT\nstring(15)\n\nRationalisation post text\nRATPRE\nstring(15)\n\nRationalisation pre text\nRATTAL\nelement(500)\nword\nRatta list\nRAWNAM\nstring(500)\n\nName only\nRAWPLA\nelement\n\nRaw Plate\nRAWPRO\nstring(26)\n\nName of raw profile\nRAWREF\nelement(100)\n\nRaw material reference\nRBCTYP\ninteger\n\nRevision History Column Type: 1=RevNo,2=Date,3=User,4=Comment\nRCOD\nstring\n\nDirection of region vertical on sheet\nRCOF\npos\n\nRough centre of gravity\nRCONAT\nelement(500)\nelement\nList of valid connected route attachments\nRCOU\ninteger\n\nNumber of rules on element\nRDEF\nreal(3)\n\nPort rotation flexibility defaults\nRDFIRI\nstring(2000)\n\nInternational Resource Identifier used to identify an RDF Resource\nRDFOBJECT\nstring(2000)\n\nAn RDF statement object string\nRDFPREFIX\nstring(30)\n\nA prefix (short-hand) for an RDF namespace\nREACT\nstring(1000)\n\nReactance\nREADONLY\nlogical\n\nRead only\nREALEV\nreal\n\nReal evaluation\nREALOV\nelement\n\nList of Values for Status Reason\nREALXP\ninteger(500)\n\nReal expression\nRECOMM\nstring(256)\n\nRelease to 3D comment\nREDATE\nstring(12)\n\nRelease to 3D date\nREDREF\nelement\n\nReducer table reference\nREDTYPE\ninteger\n\nReducer Type\nREDXRF\nelement(500)\n\nReturn reference from Reducer Table element to SPECs\nREF\nelement\n\nReference of the element\nREFA\nword\n\nReference attribute used in ports\nREFCLS\nstring(200)\n\nReferenced conceptual model class\nREFI\ninteger\n\nReference array index\nREFL\nword(2147483647)\n\nTypes of elements (including UDETs) that can be pointed to by a reference attribute\nREFLCL\nlogical\n\nTrue if reflected in CL\nREFLEVEL\ninteger\n\nReference Level\nREFLIM\nelement(10)\n\nReference limit\nREFMOD\ninteger\n\nReflection Mode\nREFRAW\nelement\n\nRaw surface reference\nREFSIZ\ninteger\n\nReference size\nREFSPA\nelement\n\nReference to space arrangement\nREFSUR\nelement\n\nReference to surface instance\nRELELS\nelement(500000)\nword\nRelated Elements, Fabrication\nRELELT\nelement\nword\nRelated Element, Fabrication\nRELINF\nstring(200)\nword\nRelated Element Information, Fabrication\nRELREF\nelement\n\nReference to DTRELA Element\nRELREV\nelement(100)\n\nRelated revisions\nRELRFS\nelement(1000)\n\nReferences to DTRELA Elements\nREMRKS\nstring(120)\n\nRemarks\nREPCOU\ninteger\n\nRule Repeat Counter\nREPSEQ\ninteger\n\nSequence no. for template repeat element\nREPSTL\ninteger\n\nSymbolic representation flag(SymbolicSingleLoc, SymbolicMultiLoc, Expansion)\nREPTXT\nstring\n\nReporter text used for element type\nREQUIRED\nlogical\n\nAction is not optional\nRESIS\nstring(1000)\n\nResistance\nRESO\nreal\n\nModel Resolution (distance)\nRESREF\nelement\n\nRest plate reference\nRESTAT\ninteger\n\nRelease to 3D status\nRESTRI\nlogical\n\nRestrict unused SPECs in Design\nRESVOLUME\nreal(4)\n\nReserved volume\nREUSER\nstring(12)\n\nRelease to 3D user\nREV\ninteger\n\nPipe Revision number\nREVDIR\nlogical\n\nReverse Direction flag\nREWIDTH\nreal\n\nReduced width\nRFLAG\nword\n\nType of real answer NONE, SINGle, RANGe or MULTi\nRFLF\nreal(3)\n\nRotational spring values\nRGBCOL\nreal(3)\n\nRGB colour vector\nRGBMAP\ninteger\n\nRGB colour mapping strategy (None, Nearest, Interpolate)\nRHOST\nstring(120)\n\nHost computer name or IP address of remote machine\nRILIST\nelement(500)\n\nRoute information list\nRINE\nreal(3)\n\nRotational inertia vector\nRINS\nreal\n\nInside radius\nRISE\nreal\n\nTread Rise\nRLAC\ninteger(500)\n\nRule action array\nRLEX\nelement(20)\n\nArray of references of special rules to exclude\nRLIM\nreal(6)\n\nRotation limits\nRLIN\nelement(20)\n\nArray of references of special rules to include\nRLIS\nword(200)\n\nList of rules set\nRLLO\ninteger(500)\n\nRule logical array\nRLOC\ninteger\n\nBranch Member Creation Status code (Router)\nRLSE\ninteger(500)\n\nRule selection array\nRLSTRF\nelement\n\nRuler style reference\nRLTRGB\ninteger(4)\n\nRGB ruler long tick colour\nRLTRGP\ninteger(4)\n\nRGB ruler long tick colour physical\nRMFL\nreal(6)\n\nRotational moment flexibility\nRMINIMUM\nreal\n\nMinimum radius\nRMOF\nreal(9)\n\nRough moments of inertia\nRMTRGB\ninteger(4)\n\nRGB ruler medium tick colour\nRMTRGP\ninteger(4)\n\nRGB ruler medium tick colour physical\nRMTRL\nlogical\n\nRest material\nRNAM\nstring(120)\n\nRecipient name\nRNGCON\nelement\n\nRung Connection\nRNGOFF\nreal\n\nRung Offset\nRNODEL\nelement(500)\nword\nRnode list\nRNREF\nelement\n\nRoute Node reference\nRNRIDF\nreal\n\nRung Rising Default\nRNRIMA\nreal\n\nRung Rising Minimum\nRNRIMI\nreal\n\nRung Rising Minimum\nRNTYPE\nword\n\nRNode Type\nROBRRU\nelement(500)\n\nRouter Rules applying to a piping element or members\nROLEREF\nelement\n\nAccess Control role references from ACR\nROOMTY\nstring(120)\n\nRoom Type\nRORIEN\nlogical\n\nTrue if repeat item is re-orientated upon rotation\nROTANG\nreal\n\nNested part rotation\nROTN\nreal(3)\n\nRotation\nROUHEIGHT\nreal\n\nRouting Height\nROUT\nreal\n\nOutside radius\nROUTND\nelement(100)\n\nCable Preliminary route point\nROUTRE\nelement\n\nRoute reference\nROUWIDTH\nreal\n\nRouting Width\nROWCOL\ninteger\n\nRow colour\nROWCON\ninteger\n\nRow colour number\nROWID\nstring(20)\n\nRow Id\nROWLAB\nstring(20)\n\nRow Label\nROWNUM\ninteger\n\nPin row number\nROWRGB\ninteger(4)\n\nRGB row colour\nROWRGP\ninteger(4)\n\nRGB row colour physical\nROWSTREF\nelement\n\nRow linestyle Reference\nROWSTY\ninteger\n\nRow linestyle\nRPARM\nreal(4)\n\nRest plate parameters\nRPEN\ninteger\n\nPen for internal rows\nRPLCOD\ninteger\n\nRest plate code\nRPLCRE\nlogical\n\nRest plates created\nRPLNAM\nstring(26)\n\nRest plate name\nRPLNUM\ninteger\n\nNumber of rest plates\nRPLPOS\nreal(4)\n\nRest plate position\nRPLREF\nelement\n\nRaw plate reference\nRPLSET\ninteger\n\nRest plate set\nRPLTYP\ninteger\n\nRest plate type\nRPLUSD\ninteger\n\nRest plates used\nRPRE\nreal\n\nReference pressure\nRPRO\nreal\nword\nCatalogue dataset property\nRPRREF\nelement\n\nRaw profile reference\nRPTCNT\ninteger(4)\n\nSymbol repeats count\nRPTDAT\nreal(4)\n\nRadial Dim Point 2D Data\nRPTX\nstring(120)\n\nText used when presenting the attribute to the user\nRRSF\nelement\n\nRep ruleset reference\nRSBOX\nreal(6)\n\nBounding box of RSO\nRSEQA\ninteger(500)\n\nSequence numbers for rule execution\nRSEQFA\nelement(500)\n\nRule sequence ref array for local names\nRSEQN\ninteger\n\nSequence number for rule execution\nRSESS\nstring(640)\ninteger\nReason for creation of session\nRSET\nlogical(3)\n\nRotation limits set flag - ignore values if FALSE\nRSFFD\ninteger\n\nFunctional description on face\nRSFMC\ninteger\n\nMaterial code on face\nRSFMS\nstring(256)\n\nMaterial side on face\nRSFMT\nreal\n\nMaterial thickness on face\nRSFSA\nlogical\n\nAuto stiffening on face\nRSFSD\nstring(256)\n\nProfile dim on face\nRSFSS\nstring(256)\n\nStiffener side on face\nRSFST\ninteger\n\nProfile type on face\nRSFWT\nlogical\n\nWatertight\nRSLBRA\nstring(256)\n\nBracket instance at limit\nRSLELE\nelement\n\nLimiting element\nRSLPRE\ninteger\n\nProfile end definition at limit\nRSOPP\nelement\npos\nReturns the planar panel given an RSO and a point.\nRSOPPT\nreal\npos\nReturns the thickness of the selected planar panel.\nRSPAN\nelement(1000)\n\nPanel(s) defined on RSO\nRSPLN\ninteger\n\nPrincipal plane of RSO\nRSRF\nreal\n\nRough surface area\nRSTBY\nstring(100)\n\nStatus set by\nRSTCOM\nstring(100)\n\nStatus comment\nRSTDAT\nstring(100)\n\nStatus date\nRSTNAM\nstring(100)\n\nStatus\nRSTRGB\ninteger(4)\n\nRGB ruler short tick colour\nRSTRGP\ninteger(4)\n\nRGB ruler short tick colour physical\nRSTYP\ninteger\n\nType of RSO\nRTEM\nreal\n\nReference temperature\nRTEX\nstring(2000)\n\nR Text string\nRTYP\nstring(12)\n\nRestraint type\nRUAXE\ninteger\n\nRuler axis direction (X, Y, Z)\nRULAOF\nreal\n\nRuler start offset\nRULAXE\nstring\n\nRuler axis (as text)\nRULBOF\nreal\n\nRuler end offset\nRULCDI\nlogical\n\nCustom direction\nRULEER\nstring(300)\ninteger\nText of \"nth\" rule error\nRULEMOD\nlogical\nattr\nTrue if rule modified this session\nRULEMODC\nlogical\nattr\nTrue if rule modified since comparison date\nRULEMODLIST\nword(500)\ninteger\nList of rules modified since given session\nRULEMODLISTC\nword(500)\n\nList of rules modified since comparison date\nRULLIM\nreal(6)\n\nRuler limits\nRULLOF\nreal\n\nRuler label offset\nRULLTC\ninteger\n\nRuler long tick colour\nRULLTL\nreal\n\nRuler long tick length\nRULMTC\ninteger\n\nRuler medium tick colour\nRULMTL\nreal\n\nRuler medium tick length\nRULRCO\ninteger\n\nRuler type code\nRULSET\nword(2000)\n\nList of rules set\nRULSTC\ninteger\n\nRuler short tick colour\nRULSTL\nreal\n\nRuler short tick length\nRULTCK\ninteger\n\nNumber of ticks between labelled ticks\nRULTCP\nstring(120)\n\nRuler tick side (as text)\nRULTXP\nstring(120)\n\nRuler text side (as text)\nRUNGS\ninteger\ninteger\nNumber of rungs\nRUNGSP\nreal\n\nRung Spacing\nRUSE\ninteger\n\nTrue if PPROP/DPROP to be used as an RPROP in geomset/pointset attribute expression\nRUTCP\ninteger\n\nRuler tick side (ByVstyle, Outside, Inside, Both)\nRUTXP\ninteger\n\nRuler text side (ByVstyle, Outside, Inside)\nRVAU\nstring(1000)\n\nRevision author\nRVCANC\nlogical\n\nCancelled\nRVCNT\ninteger\n\nRevision Count\nRVCON\nelement\n\nRevision Configuration\nRVCRIS\nelement(20)\n\nRevision Controlled Element Issue Statuses\nRVCRWR\nelement(20)\n\nWorking Revision Creation Statuses\nRVCURR\nstring(50)\n\nCurrent revision\nRVDT\nstring(12)\n\nDate of revision\nRVFTYP\ninteger\n\nRevision file type\nRVISS\nlogical\n\nIssued\nRVLPOS\nelement\n\nRevision links reference\nRVNPTS\nstring(50)\n\nRevision number value parts\nRVNUM\nstring(50)\n\nRevision number\nRVOL\nreal\n\nRough gross volume\nRVSN\nstring(1000)\n\nRevision number\nRVTM\nstring(120)\n\nTime of revision\nRVURI\nstring(1000)\n\nIssued object location\nRWDOWN\ninteger(2)\n\nTable linking RWELD elements to design WELD elements\nRWDOWN\nelement\n\nReference of associated WELD of RWELD element\nRWEI\nreal\n\nRough weight\nRWIDTH\nreal\n\nRung Width\nRWSREF\nelement\n\nRaw surface reference\n\nAttribute Name\nData Type\nQualifier\nDescription\nRADD\nreal\nDefault Radius value\nRADF\nreal\nRadius attractor factor\nRADI\nreal\nRadius\nRADIPLANE\nlogical\nRadial plane flag\nRADISP\nreal(10000)\nRadius Spacing\nRADL\nreal(2)\nRadius limits (Min/Max)\nRADS\nlogical\nRadius set flag - ignore Radius values if FALSE\nRAILHE\nreal(15)\nHeights of rails measured from path\nRAILTR\nreal(100)\nRail Trim\nRANANG\nreal(32)\nelemtype\nRange of available angles for bends and elbows\nRANEQUIP\nreal\nRange of the nearest equipment\nRANRAD\nreal(32)\nelemtype\nRange of available radii\nRATFAC\nreal\nRationalisation factor\nRATI\nreal\nPressure rating\nRATPOT\nstring(15)\nRationalisation post text\nRATPRE\nstring(15)\nRationalisation pre text\nRATTAL\nelement(500)\nword\nRatta list\nRAWNAM\nstring(500)\nName only\nRAWPLA\nelement\nRaw Plate\nRAWPRO\nstring(26)\nName of raw profile\nRAWREF\nelement(100)\nRaw material reference\nRBCTYP\ninteger\nRevision History Column Type: 1=RevNo,2=Date,3=User,4=Comment\nRCOD\nstring\nDirection of region vertical on sheet\nRCOF\npos\nRough centre of gravity\nRCONAT\nelement(500)\nelement\nList of valid connected route attachments\nRCOU\ninteger\nNumber of rules on element\nRDEF\nreal(3)\nPort rotation flexibility defaults\nRDFIRI\nstring(2000)\nInternational Resource Identifier used to identify an RDF Resource\nRDFOBJECT\nstring(2000)\nAn RDF statement object string\nRDFPREFIX\nstring(30)\nA prefix (short-hand) for an RDF namespace\nREACT\nstring(1000)\nReactance\nREADONLY\nlogical\nRead only\nREALEV\nreal\nReal evaluation\nREALOV\nelement\nList of Values for Status Reason\nREALXP\ninteger(500)\nReal expression\nRECOMM\nstring(256)\nRelease to 3D comment\nREDATE\nstring(12)\nRelease to 3D date\nREDREF\nelement\nReducer table reference\nREDTYPE\ninteger\nReducer Type\nREDXRF\nelement(500)\nReturn reference from Reducer Table element to SPECs\nREF\nelement\nReference of the element\nREFA\nword\nReference attribute used in ports\nREFCLS\nstring(200)\nReferenced conceptual model class\nREFI\ninteger\nReference array index\nREFL\nword(2147483647)\nTypes of elements (including UDETs) that can be pointed to by a reference attribute\nREFLCL\nlogical\nTrue if reflected in CL\nREFLEVEL\ninteger\nReference Level\nREFLIM\nelement(10)\nReference limit\nREFMOD\ninteger\nReflection Mode\nREFRAW\nelement\nRaw surface reference\nREFSIZ\ninteger\nReference size\nREFSPA\nelement\nReference to space arrangement\nREFSUR\nelement\nReference to surface instance\nRELELS\nelement(500000)\nword\nRelated Elements, Fabrication\nRELELT\nelement\nword\nRelated Element, Fabrication\nRELINF\nstring(200)\nword\nRelated Element Information, Fabrication\nRELREF\nelement\nReference to DTRELA Element\nRELREV\nelement(100)\nRelated revisions\nRELRFS\nelement(1000)\nReferences to DTRELA Elements\nREMRKS\nstring(120)\nRemarks\nREPCOU\ninteger\nRule Repeat Counter\nREPSEQ\ninteger\nSequence no. for template repeat element\nREPSTL\ninteger\nSymbolic representation flag(SymbolicSingleLoc, SymbolicMultiLoc, Expansion)\nREPTXT\nstring\nReporter text used for element type\nREQUIRED\nlogical\nAction is not optional\nRESIS\nstring(1000)\nResistance\nRESO\nreal\nModel Resolution (distance)\nRESREF\nelement\nRest plate reference\nRESTAT\ninteger\nRelease to 3D status\nRESTRI\nlogical\nRestrict unused SPECs in Design\nRESVOLUME\nreal(4)\nReserved volume\nREUSER\nstring(12)\nRelease to 3D user\nREV\ninteger\nPipe Revision number\nREVDIR\nlogical\nReverse Direction flag\nREWIDTH\nreal\nReduced width\nRFLAG\nword\nType of real answer NONE, SINGle, RANGe or MULTi\nRFLF\nreal(3)\nRotational spring values\nRGBCOL\nreal(3)\nRGB colour vector\nRGBMAP\ninteger\nRGB colour mapping strategy (None, Nearest, Interpolate)\nRHOST\nstring(120)\nHost computer name or IP address of remote machine\nRILIST\nelement(500)\nRoute information list\nRINE\nreal(3)\nRotational inertia vector\nRINS\nreal\nInside radius\nRISE\nreal\nTread Rise\nRLAC\ninteger(500)\nRule action array\nRLEX\nelement(20)\nArray of references of special rules to exclude\nRLIM\nreal(6)\nRotation limits\nRLIN\nelement(20)\nArray of references of special rules to include\nRLIS\nword(200)\nList of rules set\nRLLO\ninteger(500)\nRule logical array\nRLOC\ninteger\nBranch Member Creation Status code (Router)\nRLSE\ninteger(500)\nRule selection array\nRLSTRF\nelement\nRuler style reference\nRLTRGB\ninteger(4)\nRGB ruler long tick colour\nRLTRGP\ninteger(4)\nRGB ruler long tick colour physical\nRMFL\nreal(6)\nRotational moment flexibility\nRMINIMUM\nreal\nMinimum radius\nRMOF\nreal(9)\nRough moments of inertia\nRMTRGB\ninteger(4)\nRGB ruler medium tick colour\nRMTRGP\ninteger(4)\nRGB ruler medium tick colour physical\nRMTRL\nlogical\nRest material\nRNAM\nstring(120)\nRecipient name\nRNGCON\nelement\nRung Connection\nRNGOFF\nreal\nRung Offset\nRNODEL\nelement(500)\nword\nRnode list\nRNREF\nelement\nRoute Node reference\nRNRIDF\nreal\nRung Rising Default\nRNRIMA\nreal\nRung Rising Minimum\nRNRIMI\nreal\nRung Rising Minimum\nRNTYPE\nword\nRNode Type\nROBRRU\nelement(500)\nRouter Rules applying to a piping element or members\nROLEREF\nelement\nAccess Control role references from ACR\nROOMTY\nstring(120)\nRoom Type\nRORIEN\nlogical\nTrue if repeat item is re-orientated upon rotation\nROTANG\nreal\nNested part rotation\nROTN\nreal(3)\nRotation\nROUHEIGHT\nreal\nRouting Height\nROUT\nreal\nOutside radius\nROUTND\nelement(100)\nCable Preliminary route point\nROUTRE\nelement\nRoute reference\nROUWIDTH\nreal\nRouting Width\nROWCOL\ninteger\nRow colour\nROWCON\ninteger\nRow colour number\nROWID\nstring(20)\nRow Id\nROWLAB\nstring(20)\nRow Label\nROWNUM\ninteger\nPin row number\nROWRGB\ninteger(4)\nRGB row colour\nROWRGP\ninteger(4)\nRGB row colour physical\nROWSTREF\nelement\nRow linestyle Reference\nROWSTY\ninteger\nRow linestyle\nRPARM\nreal(4)\nRest plate parameters\nRPEN\ninteger\nPen for internal rows\nRPLCOD\ninteger\nRest plate code\nRPLCRE\nlogical\nRest plates created\nRPLNAM\nstring(26)\nRest plate name\nRPLNUM\ninteger\nNumber of rest plates\nRPLPOS\nreal(4)\nRest plate position\nRPLREF\nelement\nRaw plate reference\nRPLSET\ninteger\nRest plate set\nRPLTYP\ninteger\nRest plate type\nRPLUSD\ninteger\nRest plates used\nRPRE\nreal\nReference pressure\nRPRO\nreal\nword\nCatalogue dataset property\nRPRREF\nelement\nRaw profile reference\nRPTCNT\ninteger(4)\nSymbol repeats count\nRPTDAT\nreal(4)\nRadial Dim Point 2D Data\nRPTX\nstring(120)\nText used when presenting the attribute to the user\nRRSF\nelement\nRep ruleset reference\nRSBOX\nreal(6)\nBounding box of RSO\nRSEQA\ninteger(500)\nSequence numbers for rule execution\nRSEQFA\nelement(500)\nRule sequence ref array for local names\nRSEQN\ninteger\nSequence number for rule execution\nRSESS\nstring(640)\ninteger\nReason for creation of session\nRSET\nlogical(3)\nRotation limits set flag - ignore values if FALSE\nRSFFD\ninteger\nFunctional description on face\nRSFMC\ninteger\nMaterial code on face\nRSFMS\nstring(256)\nMaterial side on face\nRSFMT\nreal\nMaterial thickness on face\nRSFSA\nlogical\nAuto stiffening on face\nRSFSD\nstring(256)\nProfile dim on face\nRSFSS\nstring(256)\nStiffener side on face\nRSFST\ninteger\nProfile type on face\nRSFWT\nlogical\nWatertight\nRSLBRA\nstring(256)\nBracket instance at limit\nRSLELE\nelement\nLimiting element\nRSLPRE\ninteger\nProfile end definition at limit\nRSOPP\nelement\npos\nReturns the planar panel given an RSO and a point.\nRSOPPT\nreal\npos\nReturns the thickness of the selected planar panel.\nRSPAN\nelement(1000)\nPanel(s) defined on RSO\nRSPLN\ninteger\nPrincipal plane of RSO\nRSRF\nreal\nRough surface area\nRSTBY\nstring(100)\nStatus set by\nRSTCOM\nstring(100)\nStatus comment\nRSTDAT\nstring(100)\nStatus date\nRSTNAM\nstring(100)\nStatus\nRSTRGB\ninteger(4)\nRGB ruler short tick colour\nRSTRGP\ninteger(4)\nRGB ruler short tick colour physical\nRSTYP\ninteger\nType of RSO\nRTEM\nreal\nReference temperature\nRTEX\nstring(2000)\nR Text string\nRTYP\nstring(12)\nRestraint type\nRUAXE\ninteger\nRuler axis direction (X, Y, Z)\nRULAOF\nreal\nRuler start offset\nRULAXE\nstring\nRuler axis (as text)\nRULBOF\nreal\nRuler end offset\nRULCDI\nlogical\nCustom direction\nRULEER\nstring(300)\ninteger\nText of \"nth\" rule error\nRULEMOD\nlogical\nattr\nTrue if rule modified this session\nRULEMODC\nlogical\nattr\nTrue if rule modified since comparison date\nRULEMODLIST\nword(500)\ninteger\nList of rules modified since given session\nRULEMODLISTC\nword(500)\nList of rules modified since comparison date\nRULLIM\nreal(6)\nRuler limits\nRULLOF\nreal\nRuler label offset\nRULLTC\ninteger\nRuler long tick colour\nRULLTL\nreal\nRuler long tick length\nRULMTC\ninteger\nRuler medium tick colour\nRULMTL\nreal\nRuler medium tick length\nRULRCO\ninteger\nRuler type code\nRULSET\nword(2000)\nList of rules set\nRULSTC\ninteger\nRuler short tick colour\nRULSTL\nreal\nRuler short tick length\nRULTCK\ninteger\nNumber of ticks between labelled ticks\nRULTCP\nstring(120)\nRuler tick side (as text)\nRULTXP\nstring(120)\nRuler text side (as text)\nRUNGS\ninteger\ninteger\nNumber of rungs\nRUNGSP\nreal\nRung Spacing\nRUSE\ninteger\nTrue if PPROP/DPROP to be used as an RPROP in geomset/pointset attribute expression\nRUTCP\ninteger\nRuler tick side (ByVstyle, Outside, Inside, Both)\nRUTXP\ninteger\nRuler text side (ByVstyle, Outside, Inside)\nRVAU\nstring(1000)\nRevision author\nRVCANC\nlogical\nCancelled\nRVCNT\ninteger\nRevision Count\nRVCON\nelement\nRevision Configuration\nRVCRIS\nelement(20)\nRevision Controlled Element Issue Statuses\nRVCRWR\nelement(20)\nWorking Revision Creation Statuses\nRVCURR\nstring(50)\nCurrent revision\nRVDT\nstring(12)\nDate of revision\nRVFTYP\ninteger\nRevision file type\nRVISS\nlogical\nIssued\nRVLPOS\nelement\nRevision links reference\nRVNPTS\nstring(50)\nRevision number value parts\nRVNUM\nstring(50)\nRevision number\nRVOL\nreal\nRough gross volume\nRVSN\nstring(1000)\nRevision number\nRVTM\nstring(120)\nTime of revision\nRVURI\nstring(1000)\nIssued object location\nRWDOWN\ninteger(2)\nTable linking RWELD elements to design WELD elements\nRWDOWN\nelement\nReference of associated WELD of RWELD element\nRWEI\nreal\nRough weight\nRWIDTH\nreal\nRung Width\nRWSREF\nelement\nRaw surface reference\n\n\n"}
{"Headers": "Attribute S", "Content": "S\nreal\n\nPosition southing\nSAFC\ninteger\n\nSafety class\nSAVDIR\ndir\n\nCached direction\nSAVPOS\npos\n\nCached position\nSBCOAT\nstring(256)\n\nSecond base coating\nSBRA\nelement(10)\n\nSBOLT references\nSBRP\nelement\n\nSBFR to RPLA reference link (Router)\nSCAL\ninteger\n\nDRAFT user defined symbol scale factor\nSCALAP\ninteger\n\nSymbol Scale Axis (None, X, Y, Both)\nSCALAX\nstring(120)\n\nSymbol Scale Axis (as text)\nSCALI\nreal(500)\n\nADP main view allowable scale list\nSCALIN\nlogical\n\nDrafting symbol link scaling flag\nSCALPH\nlogical\n\nALPHA/NOALPHA flag\nSCAREF\nelement(10)\n\nArea shape reference\nSCBREF\nelement(50)\n\nSchematic element back reference\nSCDELI\nstring(50)\n\nDelimiter\nSCDIGIT\ninteger\n\nDigits\nSCEIRE\nelement(60)\n\nEnhanced instrument relationship\nSCELOR\nelement(20)\n\nEnhanced instrumentation loop reference array for schematic elements\nSCGTYP\nstring(50)\n\nSchematic nozzle gtype\nSCHED\nstring(10)\n\nPiping Schedule\nSCHELE\nelement\n\nSchematic head element\nSCHEME\nstring\n\nScheme name\nSCHFF\ninteger\n\nSchematic file format\nSCHLNK\nelement\n\nConnectivity Schematic Link\nSCHTYP\ninteger\n\nSchematic type\nSCIERTYPE\nword(60)\n\nInstrument enhanced reference type\nSCIIRE\nelement(50)\n\nInstrument to instrument reference\nSCIIRTYPE\nword(50)\n\nInstrument to instrument reference type\nSCIPRE\nelement(50)\n\nInstrument process reference\nSCIPRTYPE\nword(50)\n\nInstrument process reference type\nSCIREF\nelement(100)\n\nInstrument reference\nSCIREL\nelement(50)\n\nInstrument relationship\nSCIRLTYPE\nword(50)\n\nInstrument relationship type\nSCIRTY\nword(100)\n\nInstrument reference type\nSCLORE\nelement(10)\n\nInstrumentation loop reference array for schematic elements\nSCOD\nstring(3)\n\nIsodraft Compipe: Short code\nSCOPEREF\nelement\n\nAccess Control scope references from ACR\nSCOSEL\ninteger(500)\n\nAccess Control scope\nSCOSLX\ninteger(500)\n\nAccess Control scope\nSCPANA\nstring(120)\n\nSchematic page name\nSCPATY\nword\n\nSchematic page type\nSCQUAN\ninteger\n\nQuantity\nSCRAPT\nreal\n\nTotal scrap of raw plate area\nSCRAPU\nreal\n\nTotal scrap of used raw plate area\nSCREF\nelement\n\nSchematic element reference\nSCSTYP\nstring(257)\n\nSchematic stype\nSCSYSD\nelement(500)\n\nSystem reference array for schematic diagrams\nSCSYSF\nelement(10)\n\nSystem reference array for schematic elements\nSCTDIR\ndir\n\nSection Direction\nSCTELE\nelement\n\nSchematic tail element\nSDISTA\nreal\n\nVertical Distance of Start\nSDTH\nreal(3)\n\nSaddle thickness\nSDTINT\ninteger(2)\n\nSplitting date\nSDTTXT\nstring(22)\n\nSplitting date\nSEALEV\nreal\n\nSea level height\nSEAMPY\ninteger\n\nWeld Seam Y Orientation\nSEAMPZ\ninteger\n\nWeld Seam Z Orientation\nSECSETTING\nstring(120)\n\nSecurity Setting for the Location connection\nSECTYP\nstring(120)\n\nGpart Secondary type\nSEGAMP\nreal(2)\n\nSegment amplitude\nSEGAMV\nreal(3)\n\nSegment amplitude vector 3d\nSEGE\npos\n\nSegment end point position\nSEGEPT\nreal(3)\n\nSegment ending point 3d\nSEGEUV\nreal(2)\n\nSegment ending point\nSEGOPT\nreal(3)\n\nSegment origin point 3d\nSEGORI\nreal(2)\n\nSegment origin point\nSEGS\npos\n\nSegment start point position\nSEGSPT\nreal(3)\n\nSegment starting point 3d\nSEGSUV\nreal(2)\n\nSegment starting point\nSENS\nstring\n\nRotational sense\nSEPAR\nstring(40)\n\nSeparator String\nSEQBLS\nlogical\n\nSequence Blank Start Indicator\nSEQRES\nlogical\n\nSequence Reset Indicator\nSEQU\ninteger\n\nSequence Position in Member List\nSESCLA\ninteger\n\nSession Of Claim\nSESSC\nstring(120)\ninteger\nComment for specified session\nSESSCA\ninteger(10000)\n\nList of pairs of DB number, last session number for all referenced DBs\nSESSCH\ninteger(10000)\n\nAs for SESSCA, but searches all descendants for referenced DBs\nSESSD\nstring(120)\ninteger\nDate of specified Session\nSESSM\ninteger\nattr\nSession Of Last Modification\nSESSNO\ninteger\n\nCurrent opened Session\nSESSU\nstring(120)\ninteger\nUser creating specified session\nSETDATE\nstring(120)\n\nSet Date\nSETUTC\nstring(120)\n\nSet UTC Date\nSEXPND\nelement(10000)\n\nAll descendent elements in secondary hierarchy\nSFCOAT\nstring(256)\n\nSecond finish coating\nSFCODE\ninteger\n\nStiffener Code\nSFLIMI\nword\n\nSpooling limits\nSFOR\nreal(3)\n\nStart force vector component\nSFREF\nelement\n\nReturn reference from piping component or leave tube to spool or field element\nSHAP\nstring(1000)\n\nShape modulus\nSHBO\nreal\n\nSUPCOMP head bore\nSHDPOS\nreal(2)\n\nDimension line/arc sheet position\nSHFALG\nreal\n\nShrinkage factor along main direction\nSHFPRP\nreal\n\nShrinkage factor perpendicular to main direction\nSHFSEA\nreal\n\nShrinkage factor for seams perp. to main direction\nSHIPNO\nstring(80)\n\nShip number\nSHIPX\nstring(20)\n\nShip X position\nSHIPY\nstring(20)\n\nShip Y position\nSHIPZ\nstring(20)\n\nShip Z position\nSHOC\nreal(3)\n\nShock load vector\nSHOP\nlogical\n\nShop/Site flag\nSHOPRI\nlogical\n\nShop Primer\nSHOWKP\nlogical\n\nShow kickplate in default representation\nSHPSYM\nstring(40)\n\nShape symbol text\nSHPUV\npos\n\nPoint defining shrinkage\nSHRF\nelement\n\nReference to associated sheet or library\nSHTNUM\ninteger\n\nSheet Number\nSHTOT\ninteger\n\nTotal Sheets\nSHVUV\ndir\n\nVector defining shrinkage\nSHXYPS\nreal(2)\n\n2D Sheet Position\nSIDATT\nstring(120)\n\nName of attribute (or pseudo) to be used to select side for automatic label placement\nSIDES\nstring\n\nFrame side visibility\nSIDMOI\ninteger\n\nAuto Labelling side setting (Above, Below, Attribute)\nSIDPOS\nreal(2)\n\nSide definition point\nSIF\nreal(3)\n\nStress intensification factor\nSIGF\ninteger\n\nSignificant figures\nSIGREF\nelement\n\nSignificant point reference\nSIMINF\nelement\n\nSimulation information reference\nSIMITF\nelement(2147483647)\n\nSimulation item reference\nSIMNM\nstring(150)\n\nSimulation name\nSIMSRF\nelement\n\nSimulation source reference\nSITEAD\nstring(256)\n\nSite address\nSITEM\nelement\n\nReference from secondary hierarchy\nSITEMA\nstring(256)\n\nSite manager\nSIZE\nreal(2)\n\nSheet/region size\nSIZEDB\ninteger\n\nSize of DB\nSJUS\nword\n\nSurface justification of Panel\nSKAPOS\nreal(2)\n\nActual position of symbol or text\nSKEY\nstring(4)\n\nSymbol key\nSKEYSCALE\ninteger\n\nUniversal SKEY scale factor\nSKHEIG\nreal\n\nHeight of symbol or text\nSKIPID\nlogical\n\nSkip ID\nSKREFL\nlogical\n\nTrue if reflected\nSKROT\nreal\n\nRotation of symbol or text\nSKRPOS\nreal(2)\n\nReference position of symbol or text\nSKSYMN\ninteger\n\nSymbol number for given font\nSKTXTT\ninteger\n\nType of sketch text\nSKTYPE\ninteger\n\nType of sketch information\nSLENGTH\nreal\n\nSide length\nSLHNAP\nelement(500)\n\nSorted list of HNODE after POINTR\nSLHNBP\nelement(500)\n\nSorted list of HNODE before POINTR\nSLODIR\nreal(30)\n\nSlope direction array\nSLOPEF\nlogical\n\nSLOPEF (True if its a sloping wall else step change)\nSLOREF\nelement\n\nPipe slope reference\nSLRAP\nelement(500)\n\nSorted list of RATTA after POINTR\nSLRBP\nelement(500)\n\nSorted list of RATTA before POINTR\nSMAX\ninteger\n\nMaximum spool number in current spool drawing\nSMBFLG\nstring(120)\n\nSymbol extensible flag (as text)\nSMBFLI\ninteger\n\nSymbol extensible mode (None, Top, Bottom, Left, Right, Repeatable)\nSMEMB\nelement(10000)\n\nImmediate members in secondary hierarchy\nSMIDEN\nstring(128)\n\nSmart geo identifier\nSMNO\ninteger\n\nSMODU number\nSMOD\nstring\n\nSectioning mode\nSMOM\nreal(3)\n\nStart moment component\nSMOPOS\nreal(2)\n\nSmart geo position\nSMOROT\nreal\n\nSmart geo rotation\nSMSCLE\nreal\n\nSmart geo scale\nSMSIDE\ninteger\n\nSmart geo side\nSMTYPE\nstring(128)\n\nSmart geo type\nSOLFILLED\nlogical\n\nSolid Filled Flag\nSORF\nelement\n\nSource reference (for automatic application)\nSOUR\nstring(1000)\n\nSource macro\nSPACING\nreal\n\nSpacing gap\nSPBREF\nelement\n\nReference to boundary element\nSPCREF\nelement\n\nReference to a space element\nSPECIF\nlogical\n\nTrue if outer panel contour on PS/SB are different\nSPIN\nstring(4)\n\nDRAFT user defined spindle symbol/skey name\nSPINRE\nelement\n\nReference to external inventory element\nSPKBRK\nlogical\n\nATTA flag to treat as a real element\nSPKCHG\nelement\n\nflag to show where a spec change occurs in a branch\nSPKDI\nreal\n\nProportional distance of start point along Pline\nSPLA\nstring\n\nName of spigot plate\nSPLATE\nword\n\nSection plate\nSPLH\nstring(120)\n\nOld spooler head tube spool number\nSPLLNK\nelement\n\nSpooler Element Link\nSPLMEM\nelement(1500)\n\nSpooling table attribute on SPOOL or FIELD elements\nSPLN\nstring(120)\n\nOld spooler component spool number\nSPLNUM\ninteger\n\nSpool number\nSPLP\nstring(120)\n\nSpool number prefix\nSPLPARENT\nelement(500)\nelemtype\nBranches referenced by a SPLDRG, SPOOL or FIELD\nSPLT\nstring(120)\n\nOld spooler tube spool number\nSPLTBL\ninteger(2000)\n\nTable linking SPOOL & FIELD elements to piping components\nSPLVOLUME\nreal(3)\n\nVolume of a SPOOL element\nSPMA\nreal\nword\nSpec angle maximum answer\nSPMAAS\nelement(500)\npos\nFinds all adjoining spaces of a given space and point.\nSPMACC\nstring(25)\n\nAccess authorization code\nSPMACD\nstring(75)\n\nAccess authorization description\nSPMALL\nreal\n\nStructural Allowance\nSPMAOF\nreal\n\nOffset AFT\nSPMARA\nreal\n\nArea of face\nSPMARE\nreal\n\nArea of face\nSPMAS\nelement\npos\nReturns an adjoining space given a point and location vector.\nSPMATP\ninteger\n\nType of space arrangement\nSPMBB\nreal(6)\n\nBounding box\nSPMBIN\ninteger\n\nBoundary identification number\nSPMBNA\nstring(80)\n\nBoundary name\nSPMBOF\nreal\n\nOffset BOT\nSPMBOX\nreal(6)\n\nBounding box\nSPMBR\nelement\n\nBounding reference\nSPMCAS\nreal\n\nCalculated steel paint area of space contents\nSPMCDE\nstring(75)\n\nContent description\nSPMCF\nelement\npos\nReturns the closest face to a point within a space.\nSPMCFA\nreal\n\nFloor area\nSPMCLI\nword(2000)\n\nList of customer attributes for space\nSPMCOL\ninteger\n\nColour\nSPMCOS\nreal(3)\n\nCalculated centre of steel structure\nSPMCOV\npos\n\nCentre of Volume\nSPMCTY\nstring(25)\n\nContent type code\nSPMCWB\nreal\n\nCalculated length of butt weld\nSPMCWC\nreal\n\nCalculated Weight of space Contents\nSPMCWL\nreal\n\nCalculated length of fillet weld\nSPMCWS\nreal\n\nCalculated Weight of steel structure\nSPMDE\nreal\n\nDensity\nSPMEAS\nreal\n\nEstimated steel paint area of space contents\nSPMEHC\nreal\n\nEstimated HVAC Capacity\nSPMEN\nstring(26)\n\nEnvelop name\nSPMEPC\nreal\n\nEstimated Power Consumption\nSPMEWB\nreal\n\nEstimated length of butt weld\nSPMEWC\nreal\n\nEstimated Weight of space Contents\nSPMEWL\nreal\n\nEstimated length of fillet weld\nSPMEWS\nreal\n\nEstimated weight of steel structure\nSPMFAR\nreal\n\nFace area\nSPMFCL\nstring(20)\n\nFire class\nSPMFLW\nreal\n\nFull load weight\nSPMFOF\nreal\n\nOffset FWD\nSPMFRM\nelement\npos, dir, integer\nReturns the first reference model a ray intersects\nSPMFST\ninteger\n\nFace state\nSPMHSN\nstring(50)\n\nHull surface name\nSPMLSC\nstring(25)\n\nSpace Category\nSPMMVO\nreal\n\nTotal (moulded) volume\nSPMNBI\ninteger\n\nNext boundary identification number\nSPMNOC\nstring(25)\n\nNoise category code\nSPMNOD\nstring(75)\n\nNoise category description\nSPMNVO\nreal\n\nNet volume\nSPMOPT\ninteger\n\nType of space management operation\nSPMOTP\nstring(20)\n\nType of space management operation as enumerated\nSPMPED\nreal\n\nPermeability Damage\nSPMPER\nreal\n\nPermeability\nSPMPFN\nstring(50)\n\nPolyface name\nSPMPOF\nreal\n\nOffset PS\nSPMPP\nreal(5)\n\nPrecise properties\nSPMPU\nstring(25)\n\nPurpose code\nSPMRDH\nreal\n\nRequired deck height\nSPMRFA\nreal\n\nRequired floor area\nSPMRSE\nstring(25)\n\nRequired service code\nSPMRSN\nstring(50)\n\nReference surface name\nSPMRSO\nelement\n\nReturns the RSO of the face.\nSPMRTE\nelement\n\nReference to envelop space\nSPMSAC\nstring(25)\n\nSafety category code\nSPMSAD\nstring(75)\n\nSafety category description\nSPMSAN\nstring(80)\n\nSpace arrangement name\nSPMSBD\nelement(500)\n\nSpace boundary definitions\nSPMSEC\nstring(25)\n\nSecurity classification code\nSPMSED\nstring(75)\n\nSecurity classification description\nSPMSFI\ninteger\n\nSubface identification number\nSPMSFP\nelement\n\nReturns the space that contains the given point\nSPMSOF\nreal\n\nOffset SB\nSPMSS\ninteger\n\nSpace state\nSPMSTP\ninteger\n\nUser defined subtype\nSPMSWT\ninteger\n\nType of space world\nSPMTHC\nstring(25)\n\nThermal insulation code\nSPMTHD\nstring(75)\n\nThermal insulation description\nSPMTIC\nstring(25)\n\nCompartment tightness code\nSPMTID\nstring(75)\n\nCompartment tightness description\nSPMTOF\nreal\n\nOffset TOP\nSPMTOL\ninteger\n\nType of limits\nSPMTYP\nstring(20)\n\nType of space world as enumerated\nSPMVOI\ninteger\n\nSpace void marker\nSPOONUMBER\nstring(120)\n\nSpool number including spool prefix\nSPOW\nelement\n\nReference of SPEC owning SPCO of branch members\nSPPOSN\ninteger\n\nPosition number of spigot plate\nSPPURP\nword\n\nSpecial purpose table attribute\nSPRA\nreal\nword\nSpec angle answer\nSPRANG\nreal\n\nSpringback angle\nSPRB\nreal\nword\nSpec bore answer\nSPRE\nelement\n\nComponent spec reference\nSPRLCK\nstring(32)\n\nDetailing Bolt Set Springlock Washer\nSPSF\nelement\n\nSheet pointset reference\nSPSP\nstring(2)\n\nOld spooler spool prefix\nSPTYPE\nword\n\nType of element to be selected\nSPWD\nstring\nword\nSpec text answer\nSQNUMB\ninteger\n\nPart Sequence on Nest\nSRCNM\nstring(120)\n\nSimulation Source Name\nSREF\nstring(12)\n\nSource reference\nSREL\ninteger\n\nStart releases (packed)\nSREVAY\nelement(50)\n\nSheet revisions array\nSRFPNT\npos\n\nSurface orientation point\nSRFSID\ninteger(1000)\n\nSide of surface\nSRFTRE\nelement\n\nReference to a SRFTRT element\nSRFVEC\ndir\n\nVector\nSRTP\ninteger\n\nSorting priority for dimensions\nSSLENGTH\nreal\n\nSecond side length\nSSPLIT\nlogical\n\nSpool Split\nSTACOM\nstring(1000)\n\nComment to the current status set\nSTADATE\ndatetime(2)\n\nStandard Date\nSTAELE\nreal\n\nStart Elevation\nSTAHIS\nInt array\n\nSTADAT is also a date attribute on STALNK and its type defined in DDL is int array. Existing code has conversions between system datetime to db_datatime via frombinary and tobinary methods\nSTAHRF\nelement\n\nStatus History Reference\nSTALNK\nInt array\n\nSame attributes have to be added on status history as well so that whenever the STALNK is created, the entire data on STALNK needs to be pushed in STAHIS too. The status History grid is bound to all the STAHIS elements directly by passing STALNK elements.\nSTAN\nreal\n\nStart angle\nSTAP\nreal\n\nLength of arrive straight tube\nSTAPOINT\ninteger\n\nCable Start connection point\nSTAREA\nstring(120)\n\nReason for the current status set\nSTAREF\nelement\n\nCable Start reference\nSTARTI\nstring(120)\n\nStart ID\nSTARTZ\nlogical\n\nStart from zero\nSTASUS\nlogical\n\nCurrent status suspended\nSTAUSE\nstring(120)\n\nStandard User\nSTBINF\npos\ninteger\nStart bend information\nSTBO\nreal\n\nSUPCOMP tail bore\nSTCALN\nword\n\nStructural connection alignment\nSTCBND\ninteger\n\nStructural connection boundary condition\nSTCD\nstring(120)\n\nSymbol Code\nSTCOFF\nreal\n\nStructural connection offset\nSTCREF\nelement\n\nStructural connection reference\nSTDC\nstring(120)\n\nStandard code\nSTDEFREF\nelement\n\nStatus definition\nSTDNUM\ninteger\n\nStandard Number\nSTDTXT\nstring(32)\n\nStandard\nSTEPID\ninteger\n\nStep ID\nSTEPSP\nlogical\n\nStepwise springback\nSTEREF\nelement(500)\n\nStencil reference array for schematic elements\nSTEX\nstring(2000)\n\nS Text string\nSTFC\nreal\n\nConstant stretch factor\nSTFP\nreal\n\nProportional stretch factor\nSTHOOK\nstring(256)\n\nStart hook reference\nSTILEN\nreal\ninteger\nStail length\nSTILEX\nreal\n\nStile Exit Width\nSTINCD\nstring(120)\n\nInside surface treatment symbol code\nSTINRF\nelement\n\nInside surface treatment reference\nSTITL\nstring(1000)\n\nSheet title\nSTLE\nreal\n\nLength of leave straight tube\nSTLPOS\nelement\n\nStatus Element reference\nSTLR\nelement\n\nSteel Reference\nSTLSF\nelement\n\nDatabase reference\nSTMF\nelement\n\nTemplate selection pointer\nSTMPLS\nelement(10000)\n\nList of STAMPs related to an MDB\nSTOCKL\nreal\n\nStock Length\nSTOUCD\nstring(120)\n\nOutside Surface treatment symbol code\nSTOURF\nelement\n\nOutside surface treatment reference\nSTPDAT\nstring\n\nCalculated or Persisted Stamp Date\nSTPDBS\nelement(5000)\n\nStamps containing db\nSTPOSE\nreal(2)\n\nEnding point start\nSTPOSS\nreal(2)\n\nStarting point start\nSTPSES\ninteger(5000)\n\nSessions used in at least one stamp\nSTPUV\npos\n\nStart point\nSTRCD\ninteger\n\nSTRCD\nSTRCON\nstring(120)\n\nStair Configuration\nSTRE\nreal\n\nSpot value of stress\nSTREAT\nstring(26)\n\nSurface treatment\nSTREF\nelement\n\nStart reference\nSTREFS\nelement\n\nStart order references\nSTREV\nstring(120)\n\nString value evaluation\nSTRFNC\nstring(75)\n\nStructural Function description\nSTRJUS\nword\n\nCable Way Justification Line\nSTRLIM\ninteger\n\nStructure limit\nSTRREF\nelement(100)\n\nStructure references\nSTRSN\nreal\n\nStringer Snipe\nSTRSTD\nstring(120)\n\nStair Standard\nSTRTDT\ndatetime(2)\n\nStart Date\nSTRXP\ninteger(500)\n\nString expression\nSTRXPL\nlogical\n\nTrue if surface treatment explicitly defined\nSTSEQU\ninteger\n\nStart Sequence Position of last work before Macro execution in FCSG list\nSTSESS\ninteger\n\nDatabase session number\nSTSP\nelement\n\nStructural specification\nSTTYCD\ninteger\n\nType code for beginning of start\nSTTYP\ninteger\n\nStart type\nSTVALI\nstring(10)\nelement\nAlias of user making last status modification\nSTVASD\nelement(500)\n\nStatus types eligible\nSTVCOM\nstring\nelement\nStatus comment\nSTVDAT\ndatetime(2)\nelement\nStatus Modification Date\nSTVDEMOTE\nelement\n\nDemote Status Value\nSTVDSC\nstring\nelement\nStatus description\nSTVLNK\nelement\nelement\nStatus value Reference\nSTVLST\nelement(500)\n\nStatuses assigned\nSTVMOD\nstring(120)\nelement\nDate of last status modification\nSTVNAM\nstring\nelement\nStatus value name\nSTVNUM\ninteger\nelement\nStatus value\nSTVPROMOTE\nelement\n\nPromote Status Value\nSTVREA\nstring\nelement\nStatus reason\nSTVREF\nelement\n\nValue Ref\nSTVSUS\nlogical\nelement\nCurrent status held\nSTVTRV\nelement(500)\n\nValid Transitions\nSTVUNR\nelement(500)\n\nUnresolved Status refs\nSTVUSD\nelement(10000)\n\nElements having this status value\nSTVUSE\nstring(120)\nelement\nUser making last status modification\nSTVVAL\nelement\nelement\nStatus value Reference\nSTVVLD\nlogical\nelement\nTrue if Status valid to be controlled\nSTYF\nelement\n\nRep style reference\nSTYP\nstring\n\nSPECON type question\nSTYPDB\nstring\n\nDB sub type\nSUBRUL\ninteger(200)\nattr\nList of subrule indexes for given rule\nSUFFIX\nstring(50)\n\nSuffix\nSUPALINVALID\nelement(100)\n\nAll invalid ANCI REFS on a SITE, ZONE, PIPE, BRAN\nSUPALLANCIS\nelement(100)\n\nAll ANCI REFs on a SITE, ZONE, PIPE, BRAN\nSUPFRARRAY\nelement(100)\n\nSupport FIXINGs reference array\nSUPIRARRAY\nelement(100)\n\nInvalid ANCILLARY support reference attribute\nSUPLST\nelement(100)\nword\nAll supports connected to a section or a panel\nSUPP\nstring(120)\n\nSupplier Name\nSUPR\nelement\n\nSUPREF\nSUPRFARRAY\nelement(100)\n\nANCILLARY reference array attribute\nSUPVFARRAY\nlogical(10)\n\nIndividual ANCI valid flags array attribute\nSURECO\ninteger\n\nSurface exposure code\nSURF\nstring(120)\n\nSurface Preparation\nSURLNK\nelement\n\nReference to a terrain surface.\nSURMAT\nstring(100)\n\nSurface Material\nSURNOR\ndir\npos, dir\nSurface Normal\nSURPNT\npos\npos, dir\nSurface Point\nSURPRE\nstring(100)\n\nSurface Preparation\nSUWGAL\nreal\n\nSupport + Supported ALL Gross Weight ALL\nSUWGSA\nreal\n\nSupported ALL Gross weight\nSUWGST\nreal\n\nSupported Gross weight\nSUWNAL\nreal\n\nSupport + Supported Nett weight ALL\nSUWNSA\nreal\n\nSupported ALL Nett weight\nSUWNST\nreal\n\nSupported Nett weight\nSUWRAL\nreal\n\nSupport + Supported Rough Weight ALL\nSUWRSA\nreal\n\nSupported ALL Rough weight\nSUWRST\nreal\n\nSupported Rough weight\nSVASPLANE\nlogical\n\nHull symbolic view as plane Y/N\nSVASSEMBLIES\nelement(100)\n\nHull symbolic view assembly elements\nSVAUTO\nlogical\n\nHull symbolic view auto Y/N\nSVBLEXCLUDE\nlogical\n\nHull symbolic view exclude blocks Y/N\nSVBLOCKS\nelement(100)\n\nHull symbolic view block elements\nSVCAX\nlogical\n\nHull symbolic view coord axis Y/N\nSVCOMNO\ninteger\n\nHull symbolic view component number\nSVCOMTYPE\ninteger\n\nHull symbolic view component type\nSVCROSSSYM\nlogical\n\nHull symbolic view cross sect symbol Y/N\nSVCURTYPE\ninteger\n\nHull symbolic view curve type\nSVCURVES\nelement(100)\n\nHull symbolic view curve elements\nSVDBEFORE\nstring(20)\n\nHull symbolic view depth before\nSVDBEHIND\nstring(20)\n\nHull symbolic view depth behind\nSVDRACCOM\nlogical\n\nHull symbolic view draw accommodation Y/N\nSVDRAINTERS\nlogical\n\nHull symbolic view draw inters Y/N\nSVDRAP\nlogical\n\nHull symbolic view draw plane V\nSVDRCWAY\nlogical\n\nHull symbolic view draw cableway Y/N\nSVDREQUIP\nlogical\n\nHull symbolic view draw equip Y/N\nSVDRPIPE\nlogical\n\nHull symbolic view draw pipe Y/N\nSVDRPVOL\nlogical\n\nHull symbolic view draw pvol Y/N\nSVDRSTRUCT\nlogical\n\nHull symbolic view draw structure Y/N\nSVDRVENT\nlogical\n\nHull symbolic view draw ventilation Y/N\nSVLOOKING\ninteger\n\nHull symbolic view looking direction\nSVLXMAX\nstring(20)\n\nHull symbolic view xmax\nSVLXMIN\nstring(20)\n\nHull symbolic view xmin\nSVLYMAX\nstring(20)\n\nHull symbolic view ymax\nSVLYMIN\nstring(20)\n\nHull symbolic view ymin\nSVLZMAX\nstring(20)\n\nHull symbolic view zmax\nSVLZMIN\nstring(20)\n\nHull symbolic view zmin\nSVNAME\nstring(1000)\n\nHull symbolic view name\nSVPANELS\nelement(100)\n\nHull symbolic view panel elements\nSVPLEXCLUDE\nlogical\n\nHull symbolic view exclude panels Y/N\nSVPLTYPE\ninteger\n\nHull symbolic view plane type\nSVPLXORIGIN\nstring(20)\n\nHull symbolic view x1\nSVPLXUAXIS\nstring(20)\n\nHull symbolic view x2\nSVPLXVAXIS\nstring(20)\n\nHull symbolic view x3\nSVPLYORIGIN\nstring(20)\n\nHull symbolic view y1\nSVPLYUAXIS\nstring(20)\n\nHull symbolic view y2\nSVPLYVAXIS\nstring(20)\n\nHull symbolic view y3\nSVPLZORIGIN\nstring(20)\n\nHull symbolic view z1\nSVPLZUAXIS\nstring(20)\n\nHull symbolic view z2\nSVPLZVAXIS\nstring(20)\n\nHull symbolic view z3\nSVPNAM\nstring(1000)\n\nHull symbolic view pan name\nSVPONLY\nlogical\n\nHull symbolic view pan only\nSVPOSCOAXIS\nstring(20)\n\nHull symbolic view coord axis pos\nSVREFLECT\nlogical\n\nHull symbolic view reflect Y/N\nSVRSO\nlogical\n\nHull symbolic view RSO Y/N\nSVSCALE\nreal\n\nHull symbolic view scale\nSVSHPROFILE\nlogical\n\nHull symbolic view profile Y/N\nSVSHSEAM\nlogical\n\nHull symbolic view shell seam Y/N\nSVSHTHICK\nlogical\n\nHull symbolic view shell thickness Y/N\nSVTYPE\ninteger\n\nHull symbolic view type\nSVWAY\nelement(50)\n\nSheet Views array\nSWEEP\nreal\n\nSweep angle\nSWING\nword\n\nSwing\nSYLBTA\nword\n\nSYLBTAble attribute\nSYMBFG\nlogical\n\nSymbol flag\nSYMCNA\nelement(1000)\n\nSymbol Connection Array\nSYMELE\nelement\n\nSymmetric element\nSYMFNT\ninteger\n\nLabelling symbol font\nSYMGRO\nstring(120)\n\nSymbol Group\nSYMLNS\ninteger\n\nSide of direction vector\nSYMM\ninteger\n\nSymmetry code\nSYMNAM\nstring(120)\n\nSymbol Name\nSYMNUM\ninteger\n\nLabelling symbol number\nSYMRFG\nlogical\n\nSymbolic representation flag\nSYMTYP\ninteger\n\nLabelled symbol type\nSYMXYZ\ndir\n\nVector along symmetry line\nSYSZ\nreal\n\nSymbol size (uniform scaling)\nSYTBOK\nlogical\n\nSYLBTA attribute updated flag\nSZDI\nreal\n\nStart load point in section\n\nAttribute Name\nData Type\nQualifier\nDescription\nS\nreal\nPosition southing\nSAFC\ninteger\nSafety class\nSAVDIR\ndir\nCached direction\nSAVPOS\npos\nCached position\nSBCOAT\nstring(256)\nSecond base coating\nSBRA\nelement(10)\nSBOLT references\nSBRP\nelement\nSBFR to RPLA reference link (Router)\nSCAL\ninteger\nDRAFT user defined symbol scale factor\nSCALAP\ninteger\nSymbol Scale Axis (None, X, Y, Both)\nSCALAX\nstring(120)\nSymbol Scale Axis (as text)\nSCALI\nreal(500)\nADP main view allowable scale list\nSCALIN\nlogical\nDrafting symbol link scaling flag\nSCALPH\nlogical\nALPHA/NOALPHA flag\nSCAREF\nelement(10)\nArea shape reference\nSCBREF\nelement(50)\nSchematic element back reference\nSCDELI\nstring(50)\nDelimiter\nSCDIGIT\ninteger\nDigits\nSCEIRE\nelement(60)\nEnhanced instrument relationship\nSCELOR\nelement(20)\nEnhanced instrumentation loop reference array for schematic elements\nSCGTYP\nstring(50)\nSchematic nozzle gtype\nSCHED\nstring(10)\nPiping Schedule\nSCHELE\nelement\nSchematic head element\nSCHEME\nstring\nScheme name\nSCHFF\ninteger\nSchematic file format\nSCHLNK\nelement\nConnectivity Schematic Link\nSCHTYP\ninteger\nSchematic type\nSCIERTYPE\nword(60)\nInstrument enhanced reference type\nSCIIRE\nelement(50)\nInstrument to instrument reference\nSCIIRTYPE\nword(50)\nInstrument to instrument reference type\nSCIPRE\nelement(50)\nInstrument process reference\nSCIPRTYPE\nword(50)\nInstrument process reference type\nSCIREF\nelement(100)\nInstrument reference\nSCIREL\nelement(50)\nInstrument relationship\nSCIRLTYPE\nword(50)\nInstrument relationship type\nSCIRTY\nword(100)\nInstrument reference type\nSCLORE\nelement(10)\nInstrumentation loop reference array for schematic elements\nSCOD\nstring(3)\nIsodraft Compipe: Short code\nSCOPEREF\nelement\nAccess Control scope references from ACR\nSCOSEL\ninteger(500)\nAccess Control scope\nSCOSLX\ninteger(500)\nAccess Control scope\nSCPANA\nstring(120)\nSchematic page name\nSCPATY\nword\nSchematic page type\nSCQUAN\ninteger\nQuantity\nSCRAPT\nreal\nTotal scrap of raw plate area\nSCRAPU\nreal\nTotal scrap of used raw plate area\nSCREF\nelement\nSchematic element reference\nSCSTYP\nstring(257)\nSchematic stype\nSCSYSD\nelement(500)\nSystem reference array for schematic diagrams\nSCSYSF\nelement(10)\nSystem reference array for schematic elements\nSCTDIR\ndir\nSection Direction\nSCTELE\nelement\nSchematic tail element\nSDISTA\nreal\nVertical Distance of Start\nSDTH\nreal(3)\nSaddle thickness\nSDTINT\ninteger(2)\nSplitting date\nSDTTXT\nstring(22)\nSplitting date\nSEALEV\nreal\nSea level height\nSEAMPY\ninteger\nWeld Seam Y Orientation\nSEAMPZ\ninteger\nWeld Seam Z Orientation\nSECSETTING\nstring(120)\nSecurity Setting for the Location connection\nSECTYP\nstring(120)\nGpart Secondary type\nSEGAMP\nreal(2)\nSegment amplitude\nSEGAMV\nreal(3)\nSegment amplitude vector 3d\nSEGE\npos\nSegment end point position\nSEGEPT\nreal(3)\nSegment ending point 3d\nSEGEUV\nreal(2)\nSegment ending point\nSEGOPT\nreal(3)\nSegment origin point 3d\nSEGORI\nreal(2)\nSegment origin point\nSEGS\npos\nSegment start point position\nSEGSPT\nreal(3)\nSegment starting point 3d\nSEGSUV\nreal(2)\nSegment starting point\nSENS\nstring\nRotational sense\nSEPAR\nstring(40)\nSeparator String\nSEQBLS\nlogical\nSequence Blank Start Indicator\nSEQRES\nlogical\nSequence Reset Indicator\nSEQU\ninteger\nSequence Position in Member List\nSESCLA\ninteger\nSession Of Claim\nSESSC\nstring(120)\ninteger\nComment for specified session\nSESSCA\ninteger(10000)\nList of pairs of DB number, last session number for all referenced DBs\nSESSCH\ninteger(10000)\nAs for SESSCA, but searches all descendants for referenced DBs\nSESSD\nstring(120)\ninteger\nDate of specified Session\nSESSM\ninteger\nattr\nSession Of Last Modification\nSESSNO\ninteger\nCurrent opened Session\nSESSU\nstring(120)\ninteger\nUser creating specified session\nSETDATE\nstring(120)\nSet Date\nSETUTC\nstring(120)\nSet UTC Date\nSEXPND\nelement(10000)\nAll descendent elements in secondary hierarchy\nSFCOAT\nstring(256)\nSecond finish coating\nSFCODE\ninteger\nStiffener Code\nSFLIMI\nword\nSpooling limits\nSFOR\nreal(3)\nStart force vector component\nSFREF\nelement\nReturn reference from piping component or leave tube to spool or field element\nSHAP\nstring(1000)\nShape modulus\nSHBO\nreal\nSUPCOMP head bore\nSHDPOS\nreal(2)\nDimension line/arc sheet position\nSHFALG\nreal\nShrinkage factor along main direction\nSHFPRP\nreal\nShrinkage factor perpendicular to main direction\nSHFSEA\nreal\nShrinkage factor for seams perp. to main direction\nSHIPNO\nstring(80)\nShip number\nSHIPX\nstring(20)\nShip X position\nSHIPY\nstring(20)\nShip Y position\nSHIPZ\nstring(20)\nShip Z position\nSHOC\nreal(3)\nShock load vector\nSHOP\nlogical\nShop/Site flag\nSHOPRI\nlogical\nShop Primer\nSHOWKP\nlogical\nShow kickplate in default representation\nSHPSYM\nstring(40)\nShape symbol text\nSHPUV\npos\nPoint defining shrinkage\nSHRF\nelement\nReference to associated sheet or library\nSHTNUM\ninteger\nSheet Number\nSHTOT\ninteger\nTotal Sheets\nSHVUV\ndir\nVector defining shrinkage\nSHXYPS\nreal(2)\n2D Sheet Position\nSIDATT\nstring(120)\nName of attribute (or pseudo) to be used to select side for automatic label placement\nSIDES\nstring\nFrame side visibility\nSIDMOI\ninteger\nAuto Labelling side setting (Above, Below, Attribute)\nSIDPOS\nreal(2)\nSide definition point\nSIF\nreal(3)\nStress intensification factor\nSIGF\ninteger\nSignificant figures\nSIGREF\nelement\nSignificant point reference\nSIMINF\nelement\nSimulation information reference\nSIMITF\nelement(2147483647)\nSimulation item reference\nSIMNM\nstring(150)\nSimulation name\nSIMSRF\nelement\nSimulation source reference\nSITEAD\nstring(256)\nSite address\nSITEM\nelement\nReference from secondary hierarchy\nSITEMA\nstring(256)\nSite manager\nSIZE\nreal(2)\nSheet/region size\nSIZEDB\ninteger\nSize of DB\nSJUS\nword\nSurface justification of Panel\nSKAPOS\nreal(2)\nActual position of symbol or text\nSKEY\nstring(4)\nSymbol key\nSKEYSCALE\ninteger\nUniversal SKEY scale factor\nSKHEIG\nreal\nHeight of symbol or text\nSKIPID\nlogical\nSkip ID\nSKREFL\nlogical\nTrue if reflected\nSKROT\nreal\nRotation of symbol or text\nSKRPOS\nreal(2)\nReference position of symbol or text\nSKSYMN\ninteger\nSymbol number for given font\nSKTXTT\ninteger\nType of sketch text\nSKTYPE\ninteger\nType of sketch information\nSLENGTH\nreal\nSide length\nSLHNAP\nelement(500)\nSorted list of HNODE after POINTR\nSLHNBP\nelement(500)\nSorted list of HNODE before POINTR\nSLODIR\nreal(30)\nSlope direction array\nSLOPEF\nlogical\nSLOPEF (True if its a sloping wall else step change)\nSLOREF\nelement\nPipe slope reference\nSLRAP\nelement(500)\nSorted list of RATTA after POINTR\nSLRBP\nelement(500)\nSorted list of RATTA before POINTR\nSMAX\ninteger\nMaximum spool number in current spool drawing\nSMBFLG\nstring(120)\nSymbol extensible flag (as text)\nSMBFLI\ninteger\nSymbol extensible mode (None, Top, Bottom, Left, Right, Repeatable)\nSMEMB\nelement(10000)\nImmediate members in secondary hierarchy\nSMIDEN\nstring(128)\nSmart geo identifier\nSMNO\ninteger\nSMODU number\nSMOD\nstring\nSectioning mode\nSMOM\nreal(3)\nStart moment component\nSMOPOS\nreal(2)\nSmart geo position\nSMOROT\nreal\nSmart geo rotation\nSMSCLE\nreal\nSmart geo scale\nSMSIDE\ninteger\nSmart geo side\nSMTYPE\nstring(128)\nSmart geo type\nSOLFILLED\nlogical\nSolid Filled Flag\nSORF\nelement\nSource reference (for automatic application)\nSOUR\nstring(1000)\nSource macro\nSPACING\nreal\nSpacing gap\nSPBREF\nelement\nReference to boundary element\nSPCREF\nelement\nReference to a space element\nSPECIF\nlogical\nTrue if outer panel contour on PS/SB are different\nSPIN\nstring(4)\nDRAFT user defined spindle symbol/skey name\nSPINRE\nelement\nReference to external inventory element\nSPKBRK\nlogical\nATTA flag to treat as a real element\nSPKCHG\nelement\nflag to show where a spec change occurs in a branch\nSPKDI\nreal\nProportional distance of start point along Pline\nSPLA\nstring\nName of spigot plate\nSPLATE\nword\nSection plate\nSPLH\nstring(120)\nOld spooler head tube spool number\nSPLLNK\nelement\nSpooler Element Link\nSPLMEM\nelement(1500)\nSpooling table attribute on SPOOL or FIELD elements\nSPLN\nstring(120)\nOld spooler component spool number\nSPLNUM\ninteger\nSpool number\nSPLP\nstring(120)\nSpool number prefix\nSPLPARENT\nelement(500)\nelemtype\nBranches referenced by a SPLDRG, SPOOL or FIELD\nSPLT\nstring(120)\nOld spooler tube spool number\nSPLTBL\ninteger(2000)\nTable linking SPOOL & FIELD elements to piping components\nSPLVOLUME\nreal(3)\nVolume of a SPOOL element\nSPMA\nreal\nword\nSpec angle maximum answer\nSPMAAS\nelement(500)\npos\nFinds all adjoining spaces of a given space and point.\nSPMACC\nstring(25)\nAccess authorization code\nSPMACD\nstring(75)\nAccess authorization description\nSPMALL\nreal\nStructural Allowance\nSPMAOF\nreal\nOffset AFT\nSPMARA\nreal\nArea of face\nSPMARE\nreal\nArea of face\nSPMAS\nelement\npos\nReturns an adjoining space given a point and location vector.\nSPMATP\ninteger\nType of space arrangement\nSPMBB\nreal(6)\nBounding box\nSPMBIN\ninteger\nBoundary identification number\nSPMBNA\nstring(80)\nBoundary name\nSPMBOF\nreal\nOffset BOT\nSPMBOX\nreal(6)\nBounding box\nSPMBR\nelement\nBounding reference\nSPMCAS\nreal\nCalculated steel paint area of space contents\nSPMCDE\nstring(75)\nContent description\nSPMCF\nelement\npos\nReturns the closest face to a point within a space.\nSPMCFA\nreal\nFloor area\nSPMCLI\nword(2000)\nList of customer attributes for space\nSPMCOL\ninteger\nColour\nSPMCOS\nreal(3)\nCalculated centre of steel structure\nSPMCOV\npos\nCentre of Volume\nSPMCTY\nstring(25)\nContent type code\nSPMCWB\nreal\nCalculated length of butt weld\nSPMCWC\nreal\nCalculated Weight of space Contents\nSPMCWL\nreal\nCalculated length of fillet weld\nSPMCWS\nreal\nCalculated Weight of steel structure\nSPMDE\nreal\nDensity\nSPMEAS\nreal\nEstimated steel paint area of space contents\nSPMEHC\nreal\nEstimated HVAC Capacity\nSPMEN\nstring(26)\nEnvelop name\nSPMEPC\nreal\nEstimated Power Consumption\nSPMEWB\nreal\nEstimated length of butt weld\nSPMEWC\nreal\nEstimated Weight of space Contents\nSPMEWL\nreal\nEstimated length of fillet weld\nSPMEWS\nreal\nEstimated weight of steel structure\nSPMFAR\nreal\nFace area\nSPMFCL\nstring(20)\nFire class\nSPMFLW\nreal\nFull load weight\nSPMFOF\nreal\nOffset FWD\nSPMFRM\nelement\npos, dir, integer\nReturns the first reference model a ray intersects\nSPMFST\ninteger\nFace state\nSPMHSN\nstring(50)\nHull surface name\nSPMLSC\nstring(25)\nSpace Category\nSPMMVO\nreal\nTotal (moulded) volume\nSPMNBI\ninteger\nNext boundary identification number\nSPMNOC\nstring(25)\nNoise category code\nSPMNOD\nstring(75)\nNoise category description\nSPMNVO\nreal\nNet volume\nSPMOPT\ninteger\nType of space management operation\nSPMOTP\nstring(20)\nType of space management operation as enumerated\nSPMPED\nreal\nPermeability Damage\nSPMPER\nreal\nPermeability\nSPMPFN\nstring(50)\nPolyface name\nSPMPOF\nreal\nOffset PS\nSPMPP\nreal(5)\nPrecise properties\nSPMPU\nstring(25)\nPurpose code\nSPMRDH\nreal\nRequired deck height\nSPMRFA\nreal\nRequired floor area\nSPMRSE\nstring(25)\nRequired service code\nSPMRSN\nstring(50)\nReference surface name\nSPMRSO\nelement\nReturns the RSO of the face.\nSPMRTE\nelement\nReference to envelop space\nSPMSAC\nstring(25)\nSafety category code\nSPMSAD\nstring(75)\nSafety category description\nSPMSAN\nstring(80)\nSpace arrangement name\nSPMSBD\nelement(500)\nSpace boundary definitions\nSPMSEC\nstring(25)\nSecurity classification code\nSPMSED\nstring(75)\nSecurity classification description\nSPMSFI\ninteger\nSubface identification number\nSPMSFP\nelement\nReturns the space that contains the given point\nSPMSOF\nreal\nOffset SB\nSPMSS\ninteger\nSpace state\nSPMST"}
{"Headers": "Attribute T", "Content": "TAACTI\nlogical\n\nTask Active\nTAASTA\nelement\nword, integer\nAssigned Task Reference\nTAATCT\ninteger\nword\nAssigned Tasks Count\nTAATDS\nstring\nword, integer\nAssigned Task Description\nTAATKS\nelement(500)\nword\nAssigned Tasks\nTAATNA\nstring(200)\nword\nAssigned Task Name\nTAATNB\ninteger\nword, integer\nAssigned Task Number\nTAATNS\nstring\nword\nAssigned Task Names\nTAATSN\nstring\nword, integer\nAssigned Task Status Name\nTABANS\nreal(10)\n\nTabular answers\nTABCLN\nstringarray(10)\n\nTabite Class Name\nTABREF\nelement(100)\n\nTabite reference\nTACOL\nstring(120)\n\nTask Colour\nTACORO\nreal(50)\n\nTask Connection Route\nTAFILT\nstring(120)\n\nTask Filter\nTAFONT\nstring(120)\n\nTask Font\nTAGCD\ninteger\n\nTag code\nTAGCDS\ninteger(25)\n\nTag codes\nTAGNMS\ninteger(25)\n\nTag numbers\nTAGNUM\ninteger\n\nTag number\nTAHEIG\nreal\n\nTask Height\nTAILH\nreal\n\nTail duct height\nTAILW\nreal\n\nTail duct width\nTAISAS\nlogical\nword\nTrue if element is assigned to a task\nTALOSE\nstring(32)\n\nTask Logic Selection\nTANAME\nstring(80)\n\nTask Item Name\nTANGLE\nreal\n\nTile Angle\nTANGOF\nreal\n\nTangent offset\nTANS\nstring(257)\n\nText answer for text styp in spec\nTANSCT\ninteger\n\nTask Name Space Count\nTANSNA\nstring(200)\ninteger\nTask Name Space Name\nTANSNS\nstring\nword\nTask Name Space Names\nTAPOS\nreal(2)\n\nTask Position\nTAPREF\nelement\n\nTapping table reference\nTARF\nelement\n\nTarget reference\nTASKID\nstring(50)\n\nTask ID\nTASKTY\nstring(32)\n\nTask Type\nTASTDS\nstring\nword\nTask Status Description\nTASTNA\nstring\nword\nTask Status Name\nTASTNB\ninteger\nword\nTask Status Number\nTASTVA\nelement\nword\nTask Status Value Reference\nTATCOL\nstring(120)\n\nTask Text Colour\nTATYIN\nstring(500)\n\nTask Input Type\nTATYOU\nstring(500)\n\nTask Output Type\nTATYPE\nstring(10)\n\nText answer type\nTATYTR\nstring(32)\n\nTask Treated Type\nTAWID\nreal\n\nTask Width\nTBID\ninteger\n\nTribon ID\nTBNAME\nstring(25)\n\nTbName\nTBOR\nreal\n\nTail bore\nTCAT\nelement\n\nTrace catalogue reference\nTCDD\nstring(250)\nword\nCurrent design property default value\nTCDP\nstring(250)\nword\nCurrent design property value\nTCOD\nstring\n\nHashed origin code\nTCON\nword\n\nTail connection type\nTCORRO\nreal\n\nTail Corrosion\nTCREF\nelement(100)\n\nTail connections\nTCTL\nreal\n\nTrue cut length\nTDATUM\npos\n\nDefinition of a specific point on earth\nTDEF\nstring(257)\n\nText default for text styp in spec\nTDET\nelement\n\nTrace detail text reference\nTDIR\ndir\n\nTail direction\nTDMF\nelement(2)\n\nISODRAFT Reference Dimension attribute\nTDMT\nword(2)\n\nISODRAFT Reference Dimension attribute\nTDPR\nreal\nword\nTemplate design dataset property\nTDRT\nstring(2000)\n\nTrace detail RTEXT\nTDSHAP\nword\n\nBranch tail duct shape\nTDST\nstring(2000)\n\nTrace detail STEXT\nTDTT\nstring(2000)\n\nTrace detail TTEXT\nTEAMLS\nelement(1000)\n\nList of TEAMs to which USER belongs\nTEAMSTATUS\nword\n\nAccess Control team status\nTEMF\nelement\n\nTeam reference\nTEMP\nreal\n\nTemperature\nTEND\nstring\n\nConnection at other end of TREF (HEAD or TAIL)\nTEQDES\nstring(120)\n\nTo Equipment Description\nTESTEV\nlogical\n\nResult of constraint test evaluation\nTESTXP\ninteger(500)\n\nLogical Expression\nTEXIST\nlogical\n\nTrue if component has TUBI. Always true for offline bends.\nTEXLEN\ninteger\n\nLength of text\nTEXTD\nstring(120)\n\nGeneric Text Data Storage\nTFDP\nelement\nword\nTemplate design dataset property\nTGEOM\nlogical\n\nTrue if component has TUBI geometry\nTGHETP\nstring(20)\n\nType of Tightness code\nTGHTYP\ninteger\n\nType of Tightness\nTGRA\nreal\n\nPipework temperature gradient\nTHERMA\nstring(26)\n\nThermal category\nTHICKNESS\nreal\n\nThickness\nTHPO\npos\n\nPoint through which viewing\nTHSIZE\nreal(4)\n\nThumbnail size\nTIERHE\nreal(15)\n\nHeights of trays measured from path\nTIGHOL\nlogical\n\nTight hole\nTIMEEND\ninteger\n\nEnd time of COMMS window\nTIMEINTERVAL\ninteger\n\nCOMMS retry time interval\nTIMEOUTNUMBER\ninteger\n\nCOMMS max retry count\nTIMER\nstring(120)\n\nFrequency of DB propagation\nTIMESTART\ninteger\n\nStart time of COMMS window\nTIMFAC\nreal\n\nPathtime time factor\nTIMPET\nstring(15)\n\nTime factor pre text\nTIMPOT\nstring(15)\n\nTime factor post text\nTITL\nstring(1000)\n\nTitle\nTLCONN\nelement(500)\n\nList of elements connected to branch tail\nTLIN\nlogical\n\nTrue length indicator\nTLREF\nelement(500)\n\nList of attachment connected to attachment\nTLVBEV\nreal\n\nProfile trace length, V bevel\nTLXBEV\nreal\n\nProfile trace length, X bevel\nTLYBEV\nreal\n\nProfile trace length, Y bevel\nTMAT\nelement\n\nTrace material text reference\nTMAV\nreal\n\nAverage temperature\nTMDWG\nstring(120)\n\nAutoCAD template name\nTMMA\nreal\n\nMaximum temperature\nTMMI\nreal\n\nMinimum temperature\nTMPLTF\nstring(2000)\n\nDatasheet Template filename\nTMPR\nelement\n\nTemplate reference from SPCO\nTMRF\nelement\n\nTemplate reference\nTMRFSE\nelement\n\nSecondary template reference\nTMRMASTER\nelement\n\nTemplate Repeat Master Duplicate Element\nTMROWNER\nelement\n\nTemplate Repeat Owning Element\nTMRREF\nelement\n\nTemplate Repeat Element Reference\nTMRRULE\ninteger(500)\n\nTemplate Repeat Rule\nTMRXREF\nelement(500)\n\nReturn reference from TMRREL element to repeat elements\nTMSAAA\nlogical\n\nAutomatic Admin Approval\nTMSADP\nlogical\n\nAutomatic Discipline Pulldown\nTMSDIF\nelement\n\nTMS Discipline\nTMSPRJ\nlogical\n\nFlag to notify if this is a TMS Project\nTMSUSR\nstring(120)\n\nTMS user\nTMXT\nstring(2000)\n\nTrace material XTEXT\nTMYT\nstring(2000)\n\nTrace material YTEXT\nTMZT\nstring(2000)\n\nTrace material ZTEXT\nTNVOL\nreal\n\nTerrain net volume\nTODATA\nstring(120)\n\nTo check the mode of creation for to references\nTOODIR\ninteger\n\nTool path direction\nTOPCUT\nreal\n\nTop Stile Cut Distance\nTOPOLOGY\nstring(120)\n\nBranch topology\nTOPSTR\nreal\n\nTOP Stringer Gap\nTOTALT\nreal\n\nTotal machine time for a nested plate\nTOTLAB\nreal\n\nTotal label pathtime\nTOTLEN\nreal\n\nTotal manual length\nTOTT\nreal(2)\n\nTotal pathtime\nTOTTI\nreal(2)\n\nTotal pathtime, I-bevel\nTOTTX\nreal(2)\n\nTotal pathtime, X-bevel\nTOTTY\nreal(2)\n\nTotal pathtime, Y-bevel\nTPAR\nreal(30)\n\nTrace catalogue component parameters\nTPAREA\nstring(120)\n\nTemplated Project Area Name\nTPDISC\nstring(120)\n\nTemplated Project Discipline Name\nTPEN\ninteger\n\nText pen\nTPLFRR\nelement(10000)\ninteger\nTopology references - from\nTPLFRT\ninteger(10000)\nelement\nTopology reference types - from\nTPLPAR\nreal(50)\n\nTemplate parameters\nTPLTOR\nelement(10000)\ninteger\nTopology references - to\nTPLTOT\ninteger(10000)\nelement\nTopology reference types - to\nTPLTYP\nstring(25)\n\nTemplate type\nTPON\ninteger\n\nTO port number\nTPOS\npos\n\nTail position\nTPOSE\nreal\n\nEasting of tail position\nTPOSN\nreal\n\nNorthing of tail position\nTPOSTO\nreal\n\nTop post offset\nTPOSU\nreal\n\nUpping of tail position\nTPREF\nelement\n\nTail point reference\nTPRESS\nreal\n\nTestPressure\nTPVAL\nstring(1000)\n\nTask parameter name\nTQUAL\nstring(257)\n\nText qualifier in spec or sele\nTQUES\nstring(257)\n\nText question in spec or sele\nTRANS\nreal(12)\n\nLocal transformation matrix\nTRAYH\nreal\n\nTray height\nTRAYOW\nreal\n\nTray other width\nTRAYRW\nreal\n\nTray Reduce Width\nTRAYSW\nreal\n\nTray side width\nTRAYW\nreal\n\nTray Width\nTRCG\nlogical\n\nDRAFT user defined symbol trace flag\nTRCLIN\nword\n\nTrace line\nTRCOS\nelement\n\nSymbolic trace other side style reference\nTRCTS\nelement\n\nSymbolic trace this side style reference\nTREADD\nreal\n\nTread Depth\nTREADO\nreal\n\nTread Overlap\nTREATP\nelement\n\nTread type\nTREF\nelement\n\nTail reference\nTRGENA\nlogical\n\nInitial Value\nTRIMCE\ninteger(10000)\n\nArray of Trimmed Cells\nTRIMTY\nword\n\nCTWALL TRIM TYPE\nTRLEN\nreal\n\nTracing length\nTRSF\nelement\n\nTag ruleset reference\nTRUN\nreal\n\nTruncation value (+ve) or percentage (-ve)\nTRUNTX\nstring(80)\n\nTruncation value (+ve) or percentage (-ve) text\nTSESS\nstring(640)\ninteger\nIdentifier of Transaction containing session\nTSFBR\nlogical\n\nSpooling marker for leave tube\nTSIZ\nreal\n\nTerminator size\nTSIZTX\nstring(80)\n\nTerminator size text\nTSKDEF\nelement\n\nReference to the task definition\nTSKFCE\nelement\n\nReference to the flow chart element\nTSKNAM\nstring(80)\n\nTask Definiton Name\nTSKREF\nelement(500)\n\nAssigned tasks list\nTSLEN\nreal\n\nTotal suspension length\nTSPE\nelement\n\nTracing spec reference\nTSPR\nelement\n\nTrace specification component reference\nTTEX\nstring(2000)\n\nT Text string\nTTFACE\nstring(128)\n\nTrueType font face name\nTTFDES\nstring(128)\n\nTrueType font description\nTTFENA\nlogical\n\nTrueType fonts enabled flag\nTTFIND\ninteger\n\nTrueType font index\nTTHOFF\nreal\n\nTop Tube Hoop Offset\nTTYP\nword\n\nTemplate type\nTUCL\nreal\n\nTube centreline length of branch\nTUFG\nlogical\n\nTubing flag\nTUFL\nlogical\n\nTube flag\nTULE\nreal\n\nTube length of branch\nTUNI\nstring(20)\n\nDefault unit of value (falls back to dimension default if not set). for Real Attributes with Uunitsset.\nTVALS\nreal(1000)\n\nt Values\nTVIS\nlogical\n\nTop visibility flag\nTVOL\nreal\n\nTerrain volume\nTWALLT\nreal\n\nTail wall thickness\nTWIDIS\nreal(2147483647)\n\nProfile twist distance\nTWIDTH\nreal\n\nTread Width\nTWIST\nlogical\n\nTrue if twisted\nTWIVEC\nreal(2147483647)\n\nProfile twist orientation vector\nTWLEN\nreal\n\nTotal weld length\nTWRF\nelement\n\nTail Working Point (Router)\nTWSHRH\nstring(32)\n\nDetailing Bolt Set Head-Side Tapered Washer\nTWSHRN\nstring(32)\n\nDetailing Bolt Set Nut-Side Tapered Washer\nTWSTAN\nreal\n\nTwist angle\nTXALIGN\nstring\n\nText alignment\nTXAREA\nreal\n\nTotal Cableway X-area\nTXCOLG\ninteger\n\nGLabel style text colour\nTXCOLO\ninteger\n\nText colour\nTXCONU\ninteger\n\nText colour number\nTXDIR\ninteger\n\nText direction pline number\nTXGRGB\ninteger(4)\n\nRGB glabel style text colour\nTXGRGP\ninteger(4)\n\nRGB glabel style text colour physical\nTXHINT\nword\n\nText height interpretation mode flag\nTXSPLI\nlogical\n\nText splitting flag\nTXSTRF\nelement\n\nText style reference\nTXSTRI\nstring(1000)\n\nText String for enhanced LineStyles\nTXTFNT\ninteger\n\nLabelling text font\nTXTRGB\ninteger(4)\n\nRGB text colour\nTXTRGP\ninteger(4)\n\nRGB text colour physical\nTXTTYP\ninteger\n\nLabelled text type\nTXTVAL\nstring(80)\n\nDetailing Element Text Value\nTYNU\ninteger\n\nNumber type\nTYPE\nword\n\nType of the element, ignoring UDET, truncated to 4 or 6 characters\nTYPEA\nstring(10)\n\nTYPEA\nTYPEB\nstring(10)\n\nTYPEB\nTYPECD\ninteger\n\nType code\nTYPECE\ninteger\n\nType code\nTYPEDB\nstring(6)\n\nDB type\nTYPEXPRESSION\nstring(1000)\n\nType Expression\nTYPEXTYPE\nstring(15)\n\nType expression type\nTYPINC\nlogical\n\nType is inclusive\nTYPREFERENCE\nelement\n\nReference to a datatype element for an RDF Statement Object\nTYSEQU\ninteger\n\nType Sequence Number\nTZAXI\ndir\n\ntail Z axis\n\nAttribute Name\nData Type\nQualifier\nDescription\nTAACTI\nlogical\nTask Active\nTAASTA\nelement\nword, integer\nAssigned Task Reference\nTAATCT\ninteger\nword\nAssigned Tasks Count\nTAATDS\nstring\nword, integer\nAssigned Task Description\nTAATKS\nelement(500)\nword\nAssigned Tasks\nTAATNA\nstring(200)\nword\nAssigned Task Name\nTAATNB\ninteger\nword, integer\nAssigned Task Number\nTAATNS\nstring\nword\nAssigned Task Names\nTAATSN\nstring\nword, integer\nAssigned Task Status Name\nTABANS\nreal(10)\nTabular answers\nTABCLN\nstringarray(10)\nTabite Class Name\nTABREF\nelement(100)\nTabite reference\nTACOL\nstring(120)\nTask Colour\nTACORO\nreal(50)\nTask Connection Route\nTAFILT\nstring(120)\nTask Filter\nTAFONT\nstring(120)\nTask Font\nTAGCD\ninteger\nTag code\nTAGCDS\ninteger(25)\nTag codes\nTAGNMS\ninteger(25)\nTag numbers\nTAGNUM\ninteger\nTag number\nTAHEIG\nreal\nTask Height\nTAILH\nreal\nTail duct height\nTAILW\nreal\nTail duct width\nTAISAS\nlogical\nword\nTrue if element is assigned to a task\nTALOSE\nstring(32)\nTask Logic Selection\nTANAME\nstring(80)\nTask Item Name\nTANGLE\nreal\nTile Angle\nTANGOF\nreal\nTangent offset\nTANS\nstring(257)\nText answer for text styp in spec\nTANSCT\ninteger\nTask Name Space Count\nTANSNA\nstring(200)\ninteger\nTask Name Space Name\nTANSNS\nstring\nword\nTask Name Space Names\nTAPOS\nreal(2)\nTask Position\nTAPREF\nelement\nTapping table reference\nTARF\nelement\nTarget reference\nTASKID\nstring(50)\nTask ID\nTASKTY\nstring(32)\nTask Type\nTASTDS\nstring\nword\nTask Status Description\nTASTNA\nstring\nword\nTask Status Name\nTASTNB\ninteger\nword\nTask Status Number\nTASTVA\nelement\nword\nTask Status Value Reference\nTATCOL\nstring(120)\nTask Text Colour\nTATYIN\nstring(500)\nTask Input Type\nTATYOU\nstring(500)\nTask Output Type\nTATYPE\nstring(10)\nText answer type\nTATYTR\nstring(32)\nTask Treated Type\nTAWID\nreal\nTask Width\nTBID\ninteger\nTribon ID\nTBNAME\nstring(25)\nTbName\nTBOR\nreal\nTail bore\nTCAT\nelement\nTrace catalogue reference\nTCDD\nstring(250)\nword\nCurrent design property default value\nTCDP\nstring(250)\nword\nCurrent design property value\nTCOD\nstring\nHashed origin code\nTCON\nword\nTail connection type\nTCORRO\nreal\nTail Corrosion\nTCREF\nelement(100)\nTail connections\nTCTL\nreal\nTrue cut length\nTDATUM\npos\nDefinition of a specific point on earth\nTDEF\nstring(257)\nText default for text styp in spec\nTDET\nelement\nTrace detail text reference\nTDIR\ndir\nTail direction\nTDMF\nelement(2)\nISODRAFT Reference Dimension attribute\nTDMT\nword(2)\nISODRAFT Reference Dimension attribute\nTDPR\nreal\nword\nTemplate design dataset property\nTDRT\nstring(2000)\nTrace detail RTEXT\nTDSHAP\nword\nBranch tail duct shape\nTDST\nstring(2000)\nTrace detail STEXT\nTDTT\nstring(2000)\nTrace detail TTEXT\nTEAMLS\nelement(1000)\nList of TEAMs to which USER belongs\nTEAMSTATUS\nword\nAccess Control team status\nTEMF\nelement\nTeam reference\nTEMP\nreal\nTemperature\nTEND\nstring\nConnection at other end of TREF (HEAD or TAIL)\nTEQDES\nstring(120)\nTo Equipment Description\nTESTEV\nlogical\nResult of constraint test evaluation\nTESTXP\ninteger(500)\nLogical Expression\nTEXIST\nlogical\nTrue if component has TUBI. Always true for offline bends.\nTEXLEN\ninteger\nLength of text\nTEXTD\nstring(120)\nGeneric Text Data Storage\nTFDP\nelement\nword\nTemplate design dataset property\nTGEOM\nlogical\nTrue if component has TUBI geometry\nTGHETP\nstring(20)\nType of Tightness code\nTGHTYP\ninteger\nType of Tightness\nTGRA\nreal\nPipework temperature gradient\nTHERMA\nstring(26)\nThermal category\nTHICKNESS\nreal\nThickness\nTHPO\npos\nPoint through which viewing\nTHSIZE\nreal(4)\nThumbnail size\nTIERHE\nreal(15)\nHeights of trays measured from path\nTIGHOL\nlogical\nTight hole\nTIMEEND\ninteger\nEnd time of COMMS window\nTIMEINTERVAL\ninteger\nCOMMS retry time interval\nTIMEOUTNUMBER\ninteger\nCOMMS max retry count\nTIMER\nstring(120)\nFrequency of DB propagation\nTIMESTART\ninteger\nStart time of COMMS window\nTIMFAC\nreal\nPathtime time factor\nTIMPET\nstring(15)\nTime factor pre text\nTIMPOT\nstring(15)\nTime factor post text\nTITL\nstring(1000)\nTitle\nTLCONN\nelement(500)\nList of elements connected to branch tail\nTLIN\nlogical\nTrue length indicator\nTLREF\nelement(500)\nList of attachment connected to attachment\nTLVBEV\nreal\nProfile trace length, V bevel\nTLXBEV\nreal\nProfile trace length, X bevel\nTLYBEV\nreal\nProfile trace length, Y bevel\nTMAT\nelement\nTrace material text reference\nTMAV\nreal\nAverage temperature\nTMDWG\nstring(120)\nAutoCAD template name\nTMMA\nreal\nMaximum temperature\nTMMI\nreal\nMinimum temperature\nTMPLTF\nstring(2000)\nDatasheet Template filename\nTMPR\nelement\nTemplate reference from SPCO\nTMRF\nelement\nTemplate reference\nTMRFSE\nelement\nSecondary template reference\nTMRMASTER\nelement\nTemplate Repeat Master Duplicate Element\nTMROWNER\nelement\nTemplate Repeat Owning Element\nTMRREF\nelement\nTemplate Repeat Element Reference\nTMRRULE\ninteger(500)\nTemplate Repeat Rule\nTMRXREF\nelement(500)\nReturn reference from TMRREL element to repeat elements\nTMSAAA\nlogical\nAutomatic Admin Approval\nTMSADP\nlogical\nAutomatic Discipline Pulldown\nTMSDIF\nelement\nTMS Discipline\nTMSPRJ\nlogical\nFlag to notify if this is a TMS Project\nTMSUSR\nstring(120)\nTMS user\nTMXT\nstring(2000)\nTrace material XTEXT\nTMYT\nstring(2000)\nTrace material YTEXT\nTMZT\nstring(2000)\nTrace material ZTEXT\nTNVOL\nreal\nTerrain net volume\nTODATA\nstring(120)\nTo check the mode of creation for to references\nTOODIR\ninteger\nTool path direction\nTOPCUT\nreal\nTop Stile Cut Distance\nTOPOLOGY\nstring(120)\nBranch topology\nTOPSTR\nreal\nTOP Stringer Gap\nTOTALT\nreal\nTotal machine time for a nested plate\nTOTLAB\nreal\nTotal label pathtime\nTOTLEN\nreal\nTotal manual length\nTOTT\nreal(2)\nTotal pathtime\nTOTTI\nreal(2)\nTotal pathtime, I-bevel\nTOTTX\nreal(2)\nTotal pathtime, X-bevel\nTOTTY\nreal(2)\nTotal pathtime, Y-bevel\nTPAR\nreal(30)\nTrace catalogue component parameters\nTPAREA\nstring(120)\nTemplated Project Area Name\nTPDISC\nstring(120)\nTemplated Project Discipline Name\nTPEN\ninteger\nText pen\nTPLFRR\nelement(10000)\ninteger\nTopology references - from\nTPLFRT\ninteger(10000)\nelement\nTopology reference types - from\nTPLPAR\nreal(50)\nTemplate parameters\nTPLTOR\nelement(10000)\ninteger\nTopology references - to\nTPLTOT\ninteger(10000)\nelement\nTopology reference types - to\nTPLTYP\nstring(25)\nTemplate type\nTPON\ninteger\nTO port number\nTPOS\npos\nTail position\nTPOSE\nreal\nEasting of tail position\nTPOSN\nreal\nNorthing of tail position\nTPOSTO\nreal\nTop post offset\nTPOSU\nreal\nUpping of tail position\nTPREF\nelement\nTail point reference\nTPRESS\nreal\nTestPressure\nTPVAL\nstring(1000)\nTask parameter name\nTQUAL\nstring(257)\nText qualifier in spec or sele\nTQUES\nstring(257)\nText question in spec or sele\nTRANS\nreal(12)\nLocal transformation matrix\nTRAYH\nreal\nTray height\nTRAYOW\nreal\nTray other width\nTRAYRW\nreal\nTray Reduce Width\nTRAYSW\nreal\nTray side width\nTRAYW\nreal\nTray Width\nTRCG\nlogical\nDRAFT user defined symbol trace flag\nTRCLIN\nword\nTrace line\nTRCOS\nelement\nSymbolic trace other side style reference\nTRCTS\nelement\nSymbolic trace this side style reference\nTREADD\nreal\nTread Depth\nTREADO\nreal\nTread Overlap\nTREATP\nelement\nTread type\nTREF\nelement\nTail reference\nTRGENA\nlogical\nInitial Value\nTRIMCE\ninteger(10000)\nArray of Trimmed Cells\nTRIMTY\nword\nCTWALL TRIM TYPE\nTRLEN\nreal\nTracing length\nTRSF\nelement\nTag ruleset reference\nTRUN\nreal\nTruncation value (+ve) or percentage (-ve)\nTRUNTX\nstring(80)\nTruncation value (+ve) or percentage (-ve) text\nTSESS\nstring(640)\ninteger\nIdentifier of Transaction containing session\nTSFBR\nlogical\nSpooling marker for leave tube\nTSIZ\nreal\nTerminator size\nTSIZTX\nstring(80)\nTerminator size text\nTSKDEF\nelement\nReference to the task definition\nTSKFCE\nelement\nReference to the flow chart element\nTSKNAM\nstring(80)\nTask Definiton Name\nTSKREF\nelement(500)\nAssigned tasks list\nTSLEN\nreal\nTotal suspension length\nTSPE\nelement\nTracing spec reference\nTSPR\nelement\nTrace specification component reference\nTTEX\nstring(2000)\nT Text string\nTTFACE\nstring(128)\nTrueType font face name\nTTFDES\nstring(128)\nTrueType font description\nTTFENA\nlogical\nTrueType fonts enabled flag\nTTFIND\ninteger\nTrueType font index\nTTHOFF\nreal\nTop Tube Hoop Offset\nTTYP\nword\nTemplate type\nTUCL\nreal\nTube centreline length of branch\nTUFG\nlogical\nTubing flag\nTUFL\nlogical\nTube flag\nTULE\nreal\nTube length of branch\nTUNI\nstring(20)\nDefault unit of value (falls back to dimension default if not set). for Real Attributes with Uunitsset.\nTVALS\nreal(1000)\nt Values\nTVIS\nlogical\nTop visibility flag\nTVOL\nreal\nTerrain volume\nTWALLT\nreal\nTail wall thickness\nTWIDIS\nreal(2147483647)\nProfile twist distance\nTWIDTH\nreal\nTread Width\nTWIST\nlogical\nTrue if twisted\nTWIVEC\nreal(2147483647)\nProfile twist orientation vector\nTWLEN\nreal\nTotal weld length\nTWRF\nelement\nTail Working Point (Router)\nTWSHRH\nstring(32)\nDetailing Bolt Set Head-Side Tapered Washer\nTWSHRN\nstring(32)\nDetailing Bolt Set Nut-Side Tapered Washer\nTWSTAN\nreal\nTwist angle\nTXALIGN\nstring\nText alignment\nTXAREA\nreal\nTotal Cableway X-area\nTXCOLG\ninteger\nGLabel style text colour\nTXCOLO\ninteger\nText colour\nTXCONU\ninteger\nText colour number\nTXDIR\ninteger\nText direction pline number\nTXGRGB\ninteger(4)\nRGB glabel style text colour\nTXGRGP\ninteger(4)\nRGB glabel style text colour physical\nTXHINT\nword\nText height interpretation mode flag\nTXSPLI\nlogical\nText splitting flag\nTXSTRF\nelement\nText style reference\nTXSTRI\nstring(1000)\nText String for enhanced LineStyles\nTXTFNT\ninteger\nLabelling text font\nTXTRGB\ninteger(4)\nRGB text colour\nTXTRGP\ninteger(4)\nRGB text colour physical\nTXTTYP\ninteger\nLabelled text type\nTXTVAL\nstring(80)\nDetailing Element Text Value\nTYNU\ninteger\nNumber type\nTYPE\nword\nType of the element, ignoring UDET, truncated to 4 or 6 characters\nTYPEA\nstring(10)\nTYPEA\nTYPEB\nstring(10)\nTYPEB\nTYPECD\ninteger\nType code\nTYPECE\ninteger\nType code\nTYPEDB\nstring(6)\nDB type\nTYPEXPRESSION\nstring(1000)\nType Expression\nTYPEXTYPE\nstring(15)\nType expression type\nTYPINC\nlogical\nType is inclusive\nTYPREFERENCE\nelement\nReference to a datatype element for an RDF Statement Object\nTYSEQU\ninteger\nType Sequence Number\nTZAXI\ndir\ntail Z axis\n\n\n"}
{"Headers": "Attribute U", "Content": "U\nreal\n\nPosition upping\nUAEXSS\nreal\n\nUser Excess Arrive\nUALIAS\nstring(10)\n\nAlias of the standard user\nUALL\nlogical\n\nUALL\nUAREA\nreal\n\nUsed area\nUAXIS\ndir\n\nuAxis\nUBULG\nreal\n\nUsed bulge factor for curve geometry\nUCASES\nlogical\n\nSet true to allow Engineering cases\nUCAT\nstring(120)\n\nCategory on forms\nUCLONE\nlogical\n\nPropagate to linked elements\nUCOD\ninteger\n\nUnits code\nUCODB\ninteger\n\nUnits code bore\nUCODD\ninteger\n\nUnits code distance\nUCONN\nlogical\n\nTrue if the element referenced by UDA value should appear as a connection\nUCURTYP\nword\n\nUsed curve type\nUCUTDI\ndir\n\nUpper Extension Cutting Direction\nUCVAL\nelement(500)\n\nreferenced to controlling UVALID\nUDACPY\nelement\n\nUDA copy\nUDALIS\nword(2000)\n\nList of UDAs\nUDASET\nword(2000)\n\nList of UDAs set\nUDATLS\nword(200)\n\nList of attributes for UDET\nUDESC\nstring(4800)\n\nFull description of the element\nUDETCHECK\nstring(120)\n\nReport from UDET check on element\nUDHLIST\nword(120)\n\nAttributes hidden on elements of this user-defined element type\nUDIRECTION\ndir\n\nUp axis direction\nUDMLIST\nword(2147483647)\n\nList of allowed member types\nUDNA\nstring(120)\n\nUser defined name\nUDOLIST\nword(2147483647)\n\nList of allowed owner types\nUDPEND\nword(100)\n\nlist of attributes that this attribute depends on\nUDPMEM\nword(500)\n\nPossible type members for a UDET\nUDPOWN\nword(500)\n\nPossible owners for a UDET\nUDPSFG\nstring(100)\n\nName of PML function used for value calculation. Function should take single parameter of DBREF type.\nUDPSFS\nstring(100)\n\nName of PML function used for SET value. Function should take parameters of DBREF type and a value.\nUDTABL\nlogical\n\nDetermines if UDA is to be indexed in a table for fast access\nUDTEX\ninteger(500)\n\nuser Defined Type Group Expression\nUDTGS\nword(500)\n\nUser Defined Group Types\nUEEXSS\nreal\n\nUser End Excess\nUEXMAX\ninteger(500)\n\nExpression defining the maximum value\nUEXMIN\ninteger(500)\n\nExpression defining the minimum value\nUEXTNS\nreal\n\nUpper Extension Length\nUGOING\nreal(10)\n\nUpper Tread Going\nUHIDE\nlogical\n\nSet true to hide attribute on forms\nUHYPER\nlogical\n\nSet true to treat attribute value as a named link to an external resource\nUIWE\nstring(1000)\n\nUnit insulation weight\nUKEY\ninteger\n\nUDA key - internal unique system identifier\nUKEYFR\ninteger\n\nNumber of free UKey values available\nULEN\ninteger\n\nLength of data or text, arrays and Text Arrays. The maximum value is 214783647.\nULVOPT\nlogical\n\nDetermines if UDA valid values or range limit is optional\nUMAX\nreal\n\nMaximum value\nUMDBRE\nlogical\n\nDetermines if User-MDB association is restrictive\nUMIN\nreal\n\nMinimum value\nUMINLE\ninteger\n\nMinimum length for text or word\nUNAM\nstring(12)\n\nName of user\nUNDERL\nlogical\n\nUnderling flag\nUNIQID\nstring(256)\n\nUnique Identifier\nUNODUP\nlogical\n\nSet false to dissallow duplicate values in the array\nUNRESO\nlogical\nattr\nT/F on attributes that are unresolved references\nUNTORD\ninteger\n\nUnit order\nUNTSTDIMENSION\nstring(100)\n\nUnit set dimension\nUNTSTSYSTEM\nstring(20)\n\nUnit set system\nUPDCB\nstring(500)\n\nADP update callback\nUPGDDB\ninteger\n\nUpgrade number for DB\nUPLLEN\nreal\n\nUsed raw plate length\nUPPING\npos\n\nUpping part expressed as a position\nUPPREF\nelement\n\nReferences to upper exit level\nUPRLEN\nreal\n\nUsed profile length\nUPROMPT\nstring(40)\n\nTextual prompt to display to the user\nUPROTE\nlogical\n\nSet true to disallow viewing the attribute in a protected database\nUPSEUD\nlogical\n\nSet true to calculate attribute value rather than store it in a database. User code must be provided\nURADI\nreal\n\nUsed radius for curve geometry\nUREF\nelement\n\nUnits reference\nURISE\nreal(10)\n\nUpper Tread Rise\nURL\nstring(1024)\n\nURL\nUSCCOG\npos\n\nUser derived centre of gravity position\nUSCLHI\nelement(5000)\n\nElements in descendant hierarchy claimed to this user\nUSCWCO\npos\n\nUser derived wet centre of gravity position\nUSCWEI\nreal\n\nDerived value for user weight\nUSCWWE\nreal\n\nDerived value for user wet weight\nUSECAP\nlogical\n\nCapital Letter Usage Indicator\nUSECDE\nstring(120)\n\nText storing user code for cable\nUSEF\nelement\n\nUser reference\nUSEFED\nreal\n\nUser defined feed excess\nUSEHDR\nlogical\n\nHeader Usage Indicator\nUSERC\nstring(120)\n\nUser name of user claiming element\nUSEREQ\nstring(50)\n\nRequesting user\nUSERLS\nelement(2000)\n\nList of USERs belonging to TEAM\nUSERM\nstring(120)\nattr\nUser making last modification\nUSESS\nstring(640)\ninteger\nUser creating session\nUSHVV\nelement\n\nUDA shared valid value\nUSNCLH\nelement(5000)\n\nElements in descendant hierarchy not claimed to this user\nUSRCOG\ninteger(500)\n\nUser centre of gravity position\nUSRLI\nelement(50)\n\nValid users for given user login\nUSRMDB\nelement(100)\n\nMDBs that a user may select from. If unset, then there is no restriction.\nUSRWCO\ninteger(500)\n\nUser wet centre of gravity position\nUSRWEI\ninteger(500)\n\nUser entered weight value\nUSRWWE\ninteger(500)\n\nUser entered wet weight value\nUSUVAL\nstring(50)\n\nUnit for Unit Set\nUSYSTY\nword\n\nName of the system attribute\nUTCSES\nlogical\ninteger\nTrue if the session date is a calculated local date\nUTCSTP\nlogical\n\nTrue if the stamp date is a calculated local date\nUTCSWT\nlogical\n\nTrue if System outputs UTC based Session Date Times\nUTEAMS\nelement(500)\n\nTeams that will see a hidden attribute\nUTYP\nword\n\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR\nUUID\nstring(36)\n\nUniversally unique identifier\nUUIDAR\ninteger(4)\n\nUniversally unique identifier, stored array\nUUIDIA\ninteger(4)\n\nUniversally unique identifier\nUUIDREF\nelement(500)\nword\nUniversally unique identifier references\nUUNI\nstring(80)\n\nFor Real Attributes, the dimension of the attribute if applicable.(Examples bore, length, angle, mass)\nUVVAL\nstring(500)\n\nValid value for UDA\nUVVFER\nword\n\nAttribute to follow to get UDA valid values filtering element\nUWEI\nstring(1000)\n\nUnit pipe weight\nUWGHT\nreal\n\nUsed weight\nUWIDTH\nreal\n\nUsed width\nUWMTXT\nstring(120)\n\nUser weight Manager text\nUWP\npos\n\nUpper Working Point\n\nAttribute Name\nData Type\nQualifier\nDescription\nU\nreal\nPosition upping\nUAEXSS\nreal\nUser Excess Arrive\nUALIAS\nstring(10)\nAlias of the standard user\nUALL\nlogical\nUALL\nUAREA\nreal\nUsed area\nUAXIS\ndir\nuAxis\nUBULG\nreal\nUsed bulge factor for curve geometry\nUCASES\nlogical\nSet true to allow Engineering cases\nUCAT\nstring(120)\nCategory on forms\nUCLONE\nlogical\nPropagate to linked elements\nUCOD\ninteger\nUnits code\nUCODB\ninteger\nUnits code bore\nUCODD\ninteger\nUnits code distance\nUCONN\nlogical\nTrue if the element referenced by UDA value should appear as a connection\nUCURTYP\nword\nUsed curve type\nUCUTDI\ndir\nUpper Extension Cutting Direction\nUCVAL\nelement(500)\nreferenced to controlling UVALID\nUDACPY\nelement\nUDA copy\nUDALIS\nword(2000)\nList of UDAs\nUDASET\nword(2000)\nList of UDAs set\nUDATLS\nword(200)\nList of attributes for UDET\nUDESC\nstring(4800)\nFull description of the element\nUDETCHECK\nstring(120)\nReport from UDET check on element\nUDHLIST\nword(120)\nAttributes hidden on elements of this user-defined element type\nUDIRECTION\ndir\nUp axis direction\nUDMLIST\nword(2147483647)\nList of allowed member types\nUDNA\nstring(120)\nUser defined name\nUDOLIST\nword(2147483647)\nList of allowed owner types\nUDPEND\nword(100)\nlist of attributes that this attribute depends on\nUDPMEM\nword(500)\nPossible type members for a UDET\nUDPOWN\nword(500)\nPossible owners for a UDET\nUDPSFG\nstring(100)\nName of PML function used for value calculation. Function should take single parameter of DBREF type.\nUDPSFS\nstring(100)\nName of PML function used for SET value. Function should take parameters of DBREF type and a value.\nUDTABL\nlogical\nDetermines if UDA is to be indexed in a table for fast access\nUDTEX\ninteger(500)\nuser Defined Type Group Expression\nUDTGS\nword(500)\nUser Defined Group Types\nUEEXSS\nreal\nUser End Excess\nUEXMAX\ninteger(500)\nExpression defining the maximum value\nUEXMIN\ninteger(500)\nExpression defining the minimum value\nUEXTNS\nreal\nUpper Extension Length\nUGOING\nreal(10)\nUpper Tread Going\nUHIDE\nlogical\nSet true to hide attribute on forms\nUHYPER\nlogical\nSet true to treat attribute value as a named link to an external resource\nUIWE\nstring(1000)\nUnit insulation weight\nUKEY\ninteger\nUDA key - internal unique system identifier\nUKEYFR\ninteger\nNumber of free UKey values available\nULEN\ninteger\nLength of data or text, arrays and Text Arrays. The maximum value is 214783647.\nULVOPT\nlogical\nDetermines if UDA valid values or range limit is optional\nUMAX\nreal\nMaximum value\nUMDBRE\nlogical\nDetermines if User-MDB association is restrictive\nUMIN\nreal\nMinimum value\nUMINLE\ninteger\nMinimum length for text or word\nUNAM\nstring(12)\nName of user\nUNDERL\nlogical\nUnderling flag\nUNIQID\nstring(256)\nUnique Identifier\nUNODUP\nlogical\nSet false to dissallow duplicate values in the array\nUNRESO\nlogical\nattr\nT/F on attributes that are unresolved references\nUNTORD\ninteger\nUnit order\nUNTSTDIMENSION\nstring(100)\nUnit set dimension\nUNTSTSYSTEM\nstring(20)\nUnit set system\nUPDCB\nstring(500)\nADP update callback\nUPGDDB\ninteger\nUpgrade number for DB\nUPLLEN\nreal\nUsed raw plate length\nUPPING\npos\nUpping part expressed as a position\nUPPREF\nelement\nReferences to upper exit level\nUPRLEN\nreal\nUsed profile length\nUPROMPT\nstring(40)\nTextual prompt to display to the user\nUPROTE\nlogical\nSet true to disallow viewing the attribute in a protected database\nUPSEUD\nlogical\nSet true to calculate attribute value rather than store it in a database. User code must be provided\nURADI\nreal\nUsed radius for curve geometry\nUREF\nelement\nUnits reference\nURISE\nreal(10)\nUpper Tread Rise\nURL\nstring(1024)\nURL\nUSCCOG\npos\nUser derived centre of gravity position\nUSCLHI\nelement(5000)\nElements in descendant hierarchy claimed to this user\nUSCWCO\npos\nUser derived wet centre of gravity position\nUSCWEI\nreal\nDerived value for user weight\nUSCWWE\nreal\nDerived value for user wet weight\nUSECAP\nlogical\nCapital Letter Usage Indicator\nUSECDE\nstring(120)\nText storing user code for cable\nUSEF\nelement\nUser reference\nUSEFED\nreal\nUser defined feed excess\nUSEHDR\nlogical\nHeader Usage Indicator\nUSERC\nstring(120)\nUser name of user claiming element\nUSEREQ\nstring(50)\nRequesting user\nUSERLS\nelement(2000)\nList of USERs belonging to TEAM\nUSERM\nstring(120)\nattr\nUser making last modification\nUSESS\nstring(640)\ninteger\nUser creating session\nUSHVV\nelement\nUDA shared valid value\nUSNCLH\nelement(5000)\nElements in descendant hierarchy not claimed to this user\nUSRCOG\ninteger(500)\nUser centre of gravity position\nUSRLI\nelement(50)\nValid users for given user login\nUSRMDB\nelement(100)\nMDBs that a user may select from. If unset, then there is no restriction.\nUSRWCO\ninteger(500)\nUser wet centre of gravity position\nUSRWEI\ninteger(500)\nUser entered weight value\nUSRWWE\ninteger(500)\nUser entered wet weight value\nUSUVAL\nstring(50)\nUnit for Unit Set\nUSYSTY\nword\nName of the system attribute\nUTCSES\nlogical\ninteger\nTrue if the session date is a calculated local date\nUTCSTP\nlogical\nTrue if the stamp date is a calculated local date\nUTCSWT\nlogical\nTrue if System outputs UTC based Session Date Times\nUTEAMS\nelement(500)\nTeams that will see a hidden attribute\nUTYP\nword\nType of the value. INT, REAL, TEXT, REF, LOG, WORD, POS, DIR, ORI, DATE or TEXTAR\nUUID\nstring(36)\nUniversally unique identifier\nUUIDAR\ninteger(4)\nUniversally unique identifier, stored array\nUUIDIA\ninteger(4)\nUniversally unique identifier\nUUIDREF\nelement(500)\nword\nUniversally unique identifier references\nUUNI\nstring(80)\nFor Real Attributes, the dimension of the attribute if applicable.(Examples bore, length, angle, mass)\nUVVAL\nstring(500)\nValid value for UDA\nUVVFER\nword\nAttribute to follow to get UDA valid values filtering element\nUWEI\nstring(1000)\nUnit pipe weight\nUWGHT\nreal\nUsed weight\nUWIDTH\nreal\nUsed width\nUWMTXT\nstring(120)\nUser weight Manager text\nUWP\npos\nUpper Working Point\n\n\n"}
{"Headers": "Attribute V", "Content": "VADVCE\nreal(3)\n\nExpansion Direction of Expansion Coordinate System\nVADVCM\nreal(3)\n\nMain Direction of Expansion Coordinate System\nVADVCO\npos\n\nOrigin of Expansion Coordinate System\nVADVSU\nelement\n\nSurface\nVADVTY\ninteger\n\nAdvanced view Type(LocationDefined, MultiLocation, Expansion)\nVALARR\nelement(100)\n\nValid Status Values\nVALHRF\nelement\n\nStatus Value History reference\nVALIDV\nstring(1000)\n\nValid value expression for VVALUE elements\nVALNAM\nstring(50)\n\nLocal Name of a Status Value\nVALNUM\ninteger\n\nNumerical representation of a Status Value\nVALREF\nelement\n\nStatus Value reference\nVALRUL\nstring(1000)\n\nValid rule expression to test VALIDV attributes of VVALUE elements\nVALTEX\nstring(120)\n\nTextual representation of a Status Value\nVALTYP\nword\n\nType of the value. INT, REAL or TEXT\nVANGLE\nreal\n\nAngle from vertical\nVAXIS\ndir\n\nvAxis\nVBEVEL\nlogical\n\nTrue if V-bevel\nVCKS\nstring(120)\n\nPipe Spool Volume Check Status\nVCKWT\nelement\n\nPipe Spool Volume Checked With Tank\nVCOMPD\nstring(50)\n\nView Comparison Date\nVCOMPS\nelement\n\nView Comparison Stamp\nVDISTA\nreal\n\nVertical Distance\nVDPOS\npos\n\nDimension line/arc position\nVDTINT\ninteger(2)\n\nVerification date\nVDTTXT\nstring(22)\n\nVerification date text\nVENID\nstring(120)\n\nDriver definition used to access external laser survey\nVERDATE\ndatetime(2)\n\nVerification date\nVERTDI\nlogical\n\nVERTDI (true if Z axe is vertical )\nVFLIIND\nlogical\n\nView Frame Limits Independent\nVFLSTZ\ninteger\n\nView frame line type zero is ByStyle\nVFRCOL\ninteger\n\nView frame colour\nVFRLST\ninteger\n\nView frame linestyle\nVFRRGB\ninteger(4)\n\nRGB view frame colour\nVFRRGP\ninteger(4)\n\nRGB view frame colour physical\nVGAP\nreal\n\nView gap length\nVHEIGHT\nreal\n\nVolume height\nVIRF\nlogical\n\nVirtual Flag\nVISF\nstring(73)\n\nVisio filename\nVLAYRF\nelement\n\nVisual layer reference\nVLIM\nreal(6)\n\nView limits\nVLOCDE\nstringarray(2147483647)\n\nView location plane definition\nVLOCDI\ndir\ninteger\nView location plane direction\nVLOCDM\nlogical\n\nView location direction opposite to normal\nVLOCDT\nreal(2)\n\nView location depth, before & behind\nVLOCPO\npos\ninteger\nView location plane position\nVLTRNG\nstring(120)\n\nVoltage Range\nVMAR\nreal\n\nADP view margins\nVMCIAR\ninteger(10)\n\nVM Component Int Array\nVMCRAR\nreal(10)\n\nVM Component Real Array\nVMDRPDMS\nlogical\n\nVM Draw anno using pdms engine Y/N\nVMFCFB\nlogical\n\nVM Fill Colour From Border Y/N\nVMFLAY\ninteger\n\nVM Fillstyle Layer\nVMGLAY\ninteger\n\nVM Geometry Layer\nVMTASP\nreal\n\nVM text aspect\nVMTSLA\nreal\n\nVM text slant (degrees)\nVMUSYS\ninteger\n\nVM Fillstyle Unit System\nVNREF\nelement\n\nVNOTE reference - special attribute for use by ADP\nVOLTAC\nstring(1000)\n\nVoltage AC\nVOLTDC\nstring(1000)\n\nVoltage DC\nVRADI\nreal\n\nCableway radius\nVRAT\nreal(2)\n\nView ratio\nVREG\nreal(4)\n\nView region\nVSCA\nreal\n\nViewing scale - scales projected view\nVSHAPE\ninteger\n\nVolume shape\nVSICHS\nstring(1000)\n\nView Section Indicator Characters\nVSILCOLOUR\ninteger\n\nView Section Indicator line colour\nVSILSTYLE\ninteger\n\nView Section Indicator line style\nVSINRF\nelement\n\nView Section Indicator reference\nVSIRGB\ninteger(4)\n\nRGB view Section Indicator colour\nVSIRGP\ninteger(4)\n\nRGB view section indicator colour physical\nVSITIT\nstring(1000)\n\nView Section Indicator Title\nVSITSR\nelement\n\nView Section Indicator Title text style reference\nVTITL\nstring(1000)\n\nView title\nVTYP\nstring\n\nType of design view\nVVOL\nreal(6)\n\nView volume\nVWIDT\nreal\n\nVolume width\nVWLIMI\nreal(6)\n\nView Limits\nVWREFA\nelement(20)\n\nView reference array - special attribute for use by ADP\nVWSTRF\nelement\n\nView style reference\nVXREF\nelement(500)\n\nVertex reference array\n\nAttribute Name\nData Type\nQualifier\nDescription\nVADVCE\nreal(3)\nExpansion Direction of Expansion Coordinate System\nVADVCM\nreal(3)\nMain Direction of Expansion Coordinate System\nVADVCO\npos\nOrigin of Expansion Coordinate System\nVADVSU\nelement\nSurface\nVADVTY\ninteger\nAdvanced view Type(LocationDefined, MultiLocation, Expansion)\nVALARR\nelement(100)\nValid Status Values\nVALHRF\nelement\nStatus Value History reference\nVALIDV\nstring(1000)\nValid value expression for VVALUE elements\nVALNAM\nstring(50)\nLocal Name of a Status Value\nVALNUM\ninteger\nNumerical representation of a Status Value\nVALREF\nelement\nStatus Value reference\nVALRUL\nstring(1000)\nValid rule expression to test VALIDV attributes of VVALUE elements\nVALTEX\nstring(120)\nTextual representation of a Status Value\nVALTYP\nword\nType of the value. INT, REAL or TEXT\nVANGLE\nreal\nAngle from vertical\nVAXIS\ndir\nvAxis\nVBEVEL\nlogical\nTrue if V-bevel\nVCKS\nstring(120)\nPipe Spool Volume Check Status\nVCKWT\nelement\nPipe Spool Volume Checked With Tank\nVCOMPD\nstring(50)\nView Comparison Date\nVCOMPS\nelement\nView Comparison Stamp\nVDISTA\nreal\nVertical Distance\nVDPOS\npos\nDimension line/arc position\nVDTINT\ninteger(2)\nVerification date\nVDTTXT\nstring(22)\nVerification date text\nVENID\nstring(120)\nDriver definition used to access external laser survey\nVERDATE\ndatetime(2)\nVerification date\nVERTDI\nlogical\nVERTDI (true if Z axe is vertical )\nVFLIIND\nlogical\nView Frame Limits Independent\nVFLSTZ\ninteger\nView frame line type zero is ByStyle\nVFRCOL\ninteger\nView frame colour\nVFRLST\ninteger\nView frame linestyle\nVFRRGB\ninteger(4)\nRGB view frame colour\nVFRRGP\ninteger(4)\nRGB view frame colour physical\nVGAP\nreal\nView gap length\nVHEIGHT\nreal\nVolume height\nVIRF\nlogical\nVirtual Flag\nVISF\nstring(73)\nVisio filename\nVLAYRF\nelement\nVisual layer reference\nVLIM\nreal(6)\nView limits\nVLOCDE\nstringarray(2147483647)\nView location plane definition\nVLOCDI\ndir\ninteger\nView location plane direction\nVLOCDM\nlogical\nView location direction opposite to normal\nVLOCDT\nreal(2)\nView location depth, before & behind\nVLOCPO\npos\ninteger\nView location plane position\nVLTRNG\nstring(120)\nVoltage Range\nVMAR\nreal\nADP view margins\nVMCIAR\ninteger(10)\nVM Component Int Array\nVMCRAR\nreal(10)\nVM Component Real Array\nVMDRPDMS\nlogical\nVM Draw anno using pdms engine Y/N\nVMFCFB\nlogical\nVM Fill Colour From Border Y/N\nVMFLAY\ninteger\nVM Fillstyle Layer\nVMGLAY\ninteger\nVM Geometry Layer\nVMTASP\nreal\nVM text aspect\nVMTSLA\nreal\nVM text slant (degrees)\nVMUSYS\ninteger\nVM Fillstyle Unit System\nVNREF\nelement\nVNOTE reference - special attribute for use by ADP\nVOLTAC\nstring(1000)\nVoltage AC\nVOLTDC\nstring(1000)\nVoltage DC\nVRADI\nreal\nCableway radius\nVRAT\nreal(2)\nView ratio\nVREG\nreal(4)\nView region\nVSCA\nreal\nViewing scale - scales projected view\nVSHAPE\ninteger\nVolume shape\nVSICHS\nstring(1000)\nView Section Indicator Characters\nVSILCOLOUR\ninteger\nView Section Indicator line colour\nVSILSTYLE\ninteger\nView Section Indicator line style\nVSINRF\nelement\nView Section Indicator reference\nVSIRGB\ninteger(4)\nRGB view Section Indicator colour\nVSIRGP\ninteger(4)\nRGB view section indicator colour physical\nVSITIT\nstring(1000)\nView Section Indicator Title\nVSITSR\nelement\nView Section Indicator Title text style reference\nVTITL\nstring(1000)\nView title\nVTYP\nstring\nType of design view\nVVOL\nreal(6)\nView volume\nVWIDT\nreal\nVolume width\nVWLIMI\nreal(6)\nView Limits\nVWREFA\nelement(20)\nView reference array - special attribute for use by ADP\nVWSTRF\nelement\nView style reference\nVXREF\nelement(500)\nVertex reference array\n\n\n"}
{"Headers": "Attribute W", "Content": "W\nreal\n\nPosition westing\nWALLTH\nreal\n\nTube wall thickness\nWAMA\nreal\n\nMaximum water level\nWANS\nword(100)\n\nWord answers\nWASHRH\nstring(32)\n\nDetailing Bolt Set Head-Side Washer\nWASHRN\nstring(32)\n\nDetailing Bolt Set Nut-Side Washer\nWATERT\nlogical\n\nWater Tight\nWATTIM\nreal\n\nWater cleaning time\nWBACK\nlogical\n\nTrue if backing bar is to be used\nWBORE\nreal\n\nBore on IWELD/RWELD\nWCANG\nreal\n\nWeld connection angle\nWCCAS\ninteger\n\nWelding constant contour (arrow side)\nWCCOS\ninteger\n\nWelding constant contour (other side)\nWCHAR\ninteger\n\nDetailing Weld Characteristic\nWCLOS\nlogical\n\nClosure weld\nWCMNT\nstring(32)\n\nWeld Comment\nWCOM\nstring(26)\n\nWeld comment\nWDBNA\nstring\n\nWorking DB name\nWDESP\nword(100)\n\nDesign parameters as words\nWDIA\nstring(1000)\n\nWind diameter modulus\nWECOM\nstring(256)\n\nWeld comment\nWEFA\nreal\n\nWeight multiplier\nWEGOLD\nlogical\n\nTrue if golden weld\nWEIG\nreal(3)\n\nWeighting value\nWELCON\nword\n\nWelding machine connection type\nWELDDP\nreal\n\nWelding depth\nWELDMC\nelement\n\nWelding Machine Reference\nWELDTY\nword\n\nWeld Type\nWELMAC\nreal\n\nMinimum tube length for machine welding\nWELMAN\nreal\n\nMinimum tube length for manual welding\nWELORB\nreal\n\nMinimum tube length for orbital welding\nWENAM\nstring(256)\n\nWeld name\nWEPROC\nstring(256)\n\nWelding process\nWESTRF\nelement\n\nWhitespace Entity Style reference\nWESUSP\nreal\n\nWeld end suspension\nWEXPTX\nstring(32)\n\nWelding Fish Tail: Explanation text\nWFIN\nstring(256)\n\nWeld finish\nWFISTA\nstring(32)\n\nWelding Fish tail: Additional Text 1\nWFISTB\nstring(32)\n\nWelding Fish tail: Additional Text 2\nWFISTC\nstring(32)\n\nWelding Fish tail: Additional Text 3\nWFLELM\nelement\n\nReference to Workflow Element\nWFRDBL\nreal(5)\n\nDetailing Weld Free Doubles\nWFTXA\nstring(32)\n\nWelding Free text 1\nWFTXB\nstring(32)\n\nWelding Free text 2\nWFTXC\nstring(32)\n\nWelding Free text 3\nWFTXD\nstring(32)\n\nWelding Free text 4\nWGANG\nreal\n\nWeld groove angle\nWGAP\nreal\n\nWeld Gap\nWGNAS\ninteger\n\nWelding symbol ID (arrow side)\nWGNOS\ninteger\n\nWelding symbol ID (other side)\nWGOLD\nlogical\n\nGolden Weld\nWGROUP\ninteger\n\nWeld Grouping Option\nWGSTRF\nelement\n\nWhitespace Generic Style reference\nWHOLEC\nreal\n\nArray of Whole Cells\nWIANG\nreal\n\nWeld inclination angle\nWIDARR\nreal(10)\n\nWidth array\nWIDT\nreal\n\nWidth\nWIFA\nreal\n\nWind multiplier\nWIMAS\nlogical\n\nIntermittent weld (arrow side)\nWIMOS\nlogical\n\nIntermittent weld (other side)\nWINDAS\nstring(32)\n\nWelding Index (Arrow Side)\nWINDOS\nstring(32)\n\nWelding Index (Other Side)\nWINT\nlogical\n\nTrue if intermittent weld\nWINTL\nreal\n\nIntermittent weld length\nWINTP\nreal\n\nIntermittent weld pitch\nWIRESZ\nstring(120)\n\nWire size\nWISYM\ninteger\n\nWelding Process symbol number\nWJPOS\npos\n\nImplied weld position\nWJUSL\nword\n\nWall Justification Line\nWLDAAS\nreal\n\nWeld chamfer angle arrow side\nWLDAOS\nreal\n\nWeld chamfer angle (other side)\nWLDBAS\ninteger\n\nWeld Backing (arrow side)\nWLDBOS\ninteger\n\nWeld Backing (other side)\nWLDC\ninteger\n\nWeld Code\nWLDCAS\nreal\n\nWeld width (arrow side)\nWLDCOS\nreal\n\nWeld width (other side)\nWLDDAS\nreal\n\nWeld Diameter (arrow side)\nWLDDIA\nreal\n\nDiameter(width) for plug/slot welds\nWLDDOS\nreal\n\nWeld diameter (other side)\nWLDEAS\nreal\n\nWeld thickness (arrow side)\nWLDEOS\nreal\n\nWeld thickness (other side)\nWLDFAS\ninteger\n\nWelding Finish (arrow side)\nWLDFOS\ninteger\n\nWelding Finish (other side)\nWLDHAS\ninteger\n\nWelding Spacer (arrow side)\nWLDHOS\ninteger\n\nWelding Spacer (other side)\nWLDINF\ninteger\n\nWelding information\nWLDLAS\nreal\n\nWeld segment length (arrow side)\nWLDLOS\nreal\n\nWeld segment length (other side)\nWLDN\ninteger\n\nWeld number\nWLDNAS\ninteger\n\nNumber of weld segments (arrow side)\nWLDNDT\nlogical\n\nWelding NDT (Non-Destructive Testing)\nWLDNOS\ninteger\n\nNumber of weld segments (other side)\nWLDP\nstring(4)\n\nWeld number prefix\nWLDPOS\nstring(26)\n\nWelding position\nWLDRAS\nreal\n\nWeld chamfer Gap (arrow side)\nWLDREF\nelement\ninteger\nReturn reference from Ppoint or WELD to IWELD or RWELD element\nWLDRND\nlogical\n\nFlag weld all round\nWLDROS\nreal\n\nWeld chamfer Gap (other side)\nWLDSAS\nreal\n\nWeld chamfer depth (arrow side)\nWLDSOS\nreal\n\nWeld chamfer depth (other side)\nWLDTAS\ninteger\n\nWeld process number (arrow side)\nWLDTHY\nreal\n\nWeld material thickness (Y direction)\nWLDTHZ\nreal\n\nWeld material thickness (Z direction)\nWLDTOS\ninteger\n\nWeld process number (other side)\nWLDTYP\ninteger\n\nWelding Element Type Number\nWLDVAS\nreal\n\nWeld segment offset (arrow side)\nWLDVOS\nreal\n\nWeld segment Offset (other side)\nWLDZAS\nreal\n\nWeld leg length (arrow side)\nWLDZOS\nreal\n\nWeld leg length (other side)\nWLEGL\nreal\n\nWeld leg length\nWLEGTX\nstring(32)\n\nWelding legend text\nWLEN\nreal\n\nWeld length\nWLLEN\nreal\n\nLeg length of the weld\nWLNGTH\nreal\n\nWeld Length\nWMAX\ninteger\n\nMaximum weld number in current spool drawing\nWMDREF\nelement\n\nReference to weld master data\nWNAM\nstring(26)\n\nWeld name\nWNAMAS\nstring(32)\n\nWeld Name (arrow side)\nWNAMOS\nstring(32)\n\nWeld Name (other side)\nWNCAT\nstring(32)\n\nWelding NDT Category name\nWNDT\nstring(256)\n\nNo destructive test for the weld\nWNDTN\nstring(32)\n\nWelding NDT type name\nWNDTP\nreal\n\nWelding NDT percentage\nWNLAY\ninteger\n\nNumber of weld layers\nWNPROC\nstring(32)\n\nWelding NDT process name\nWNTHK\nstring(32)\n\nWeld Name Thickness\nWORI\nori\n\nWorld orientation\nWORPOS\npos\n\nWorld position\nWOSTRF\nelement\n\nWhitespace Objective Preference Style reference\nWPAR\nword(100)\n\nParameters as a word\nWPDAS\nreal\n\nWeld segment distance (arrow side)\nWPDOS\nreal\n\nWeld segment distance (other side)\nWPLEN\nreal\n\nWeight per length\nWPOST\nstring(32)\n\nWeld mark text\nWPRE\nreal\n\nWind pressure\nWPROC\nstring(26)\n\nWelding process\nWRANG\nreal\n\nWeld rotation angle\nWRKMRK\nstring(30)\n\nWorking Revision Indicator String\nWRKSEQ\nstring(256)\n\nWorking sequence\nWRKSHR\ninteger\n\nWork Share\nWSADER\nreal\n\nWhitespace alignment deviation\nWSADET\nstring(80)\n\nWhitespace alignment deviation\nWSAIAT\ninteger\n\nWhitespace annotation intersections allowed (Unset, ByStyle, ByTemp, Off/False, CONLOnly, On/True)\nWSAPPR\nreal\n\nWhitespace placement priority\nWSAPPT\nstring(80)\n\nWhitespace placement priority\nWSDCAT\ninteger\n\nWhitespace dog leg creation allowed (Unset ByStyle ByTemp Off/False On/True)\nWSDRAT\ninteger\n\nWhitespace dog leg removal allowed (Unset ByStyle ByTemp Off/False On/True)\nWSERSF\nelement\n\nWhitespace Entity Rule Set reference\nWSHOP\nlogical\n\nWeld shop/site flag on IWELD/RWELD\nWSLEN\nreal\n\nLength for slot weld\nWSLLRT\ninteger\n\nWhitespace leader line restriction (-5 ByStyle -2 UseGen 0 Off/False 1 On/True)\nWSMADR\nreal\n\nWhitespace minimum attachment point distance\nWSMADT\nstring(80)\n\nWhitespace minimum attachment point distance\nWSMASR\nreal\n\nWhitespace minimum annotation spacing\nWSMAST\nstring(80)\n\nWhitespace minimum annotation spacing\nWSOAGR\nreal\n\nWhitespace Objective Preference - A-GS overlap\nWSOAGT\nstring(80)\n\nWhitespace Objective Preference - A-GS overlap\nWSOALR\nreal\n\nWhitespace Objective Preference - alignment violation\nWSOALT\nstring(80)\n\nWhitespace Objective Preference - alignment violation\nWSOARR\nreal\n\nWhitespace Objective Preference - A-RS overlap\nWSOART\nstring(80)\n\nWhitespace Objective Preference - A-RS overlap\nWSODSR\nreal\n\nWhitespace Objective Preference - insertion distance deviation\nWSODST\nstring(80)\n\nWhitespace Objective Preference - insertion distance deviation\nWSOOVR\nreal\n\nWhitespace Objective Preference - outside of view violation\nWSOOVT\nstring(80)\n\nWhitespace Objective Preference - outside of view violation\nWSOPDR\nreal\n\nWhitespace optimal distance\nWSOPDT\nstring(80)\n\nWhitespace optimal distance\nWSOVMT\ninteger\n\nWhitespace Out-of-View mode (ByStyle UseGlob Off InsidePref InsideOnly OutsidePref OutsideOnly)\nWSOVSD\nstring(80)\n\nWhitespace Out-of-View preferred sides (ByStyle UseGeneric or comma-sep. comb. of Top Right Bottom Left)\nWSOVSI\ninteger\n\nWhitespace Out-of-View preferred sides (-5 ByStyle -2 UseGen, or bit-coded 1 Top 2 Right 4 Bottom 8 Left)\nWSOXAR\nreal\n\nWhitespace Objective Preference - X-Angs violation\nWSOXAT\nstring(80)\n\nWhitespace Objective Preference - X-Angs violation\nWSPACE\nlogical\n\nTrue if spacer is to be used\nWSPDAN\nreal\n\nWhitespace Placement Direction angle\nWSPDDG\nstring(80)\n\nWhitespace Placement Direction angle\nWSPDIN\nreal(2)\n\nWhitespace Placement Direction intervals\nWSPDIT\nstring(80)\n\nWhitespace Placement Direction intervals\nWSPEC\nelement\n\nWeld specification on IWELD/RWELD\nWSPLMT\ninteger\n\nWhitespace placement mode (Unset ByStyle ByTemp DontMove PreferOrig OptimiseDist Free)\nWSPORF\nelement\n\nWhitespace Picture Owner reference\nWSPOST\ninteger\n\nWhitespace pic. owner result state (ReviewPending, Accepted, Rejected)\nWSPROC\nstring(26)\n\nWelding standard process\nWSSAS\nreal\n\nWeld penetration depth (arrow side)\nWSSOS\nreal\n\nWeld penetration depth (other side)\nWSSTQI\ninteger\n\nWhitespace quadrants (bit-coded 1 TopRight 2 TopLeft 4 BottomLeft 8 BottomRight)\nWSSTQS\nstring(80)\n\nWhitespace quadrants (comma-sep. comb. of TopRight TopLeft BottomLeft BottomRight)\nWSSUSP\nreal\n\nWeld start suspension\nWSTAND\nstring(256)\n\nWeld standard\nWSTDV\nstring(256)\n\nWeld standard vesrion\nWSXANG\nreal(60)\n\nWhitespace Expected Angles\nWSXANT\nstring(2000)\n\nWhitespace Expected Angles\nWTCOM\nstring(300)\n\nWeld table comment\nWTEREF\nelement\ninteger\nWall thickness element reference\nWTEST\nstring(256)\n\nTest procedure for the weld\nWTHICK\nreal\n\nWall thickness\nWTHREF\nelement\n\nWall thickness table reference\nWTOL\nstring(1000)\n\nWall thickness tolerance / Weight tolerance\nWTORCH\ndir\n\nWeld torch vector\nWTPROC\nstring(26)\n\nWelding test procedure\nWTRANS\nreal(12)\n\nTransformation matrix to world\nWTSTAT\nstring(26)\n\nWeld table status\nWTYPE\nword\n\nWeld type\nWUNIQ\nlogical\n\nWelding Element Unique Flag\nWVOL\nreal(6)\n\nEnclosing box volume in world coordinates\nWVTAS\ninteger\n\nWeld type (arrow side)\nWVTOS\ninteger\n\nWeld type (other side)\n\nAttribute Name\nData Type\nQualifier\nDescription\nW\nreal\nPosition westing\nWALLTH\nreal\nTube wall thickness\nWAMA\nreal\nMaximum water level\nWANS\nword(100)\nWord answers\nWASHRH\nstring(32)\nDetailing Bolt Set Head-Side Washer\nWASHRN\nstring(32)\nDetailing Bolt Set Nut-Side Washer\nWATERT\nlogical\nWater Tight\nWATTIM\nreal\nWater cleaning time\nWBACK\nlogical\nTrue if backing bar is to be used\nWBORE\nreal\nBore on IWELD/RWELD\nWCANG\nreal\nWeld connection angle\nWCCAS\ninteger\nWelding constant contour (arrow side)\nWCCOS\ninteger\nWelding constant contour (other side)\nWCHAR\ninteger\nDetailing Weld Characteristic\nWCLOS\nlogical\nClosure weld\nWCMNT\nstring(32)\nWeld Comment\nWCOM\nstring(26)\nWeld comment\nWDBNA\nstring\nWorking DB name\nWDESP\nword(100)\nDesign parameters as words\nWDIA\nstring(1000)\nWind diameter modulus\nWECOM\nstring(256)\nWeld comment\nWEFA\nreal\nWeight multiplier\nWEGOLD\nlogical\nTrue if golden weld\nWEIG\nreal(3)\nWeighting value\nWELCON\nword\nWelding machine connection type\nWELDDP\nreal\nWelding depth\nWELDMC\nelement\nWelding Machine Reference\nWELDTY\nword\nWeld Type\nWELMAC\nreal\nMinimum tube length for machine welding\nWELMAN\nreal\nMinimum tube length for manual welding\nWELORB\nreal\nMinimum tube length for orbital welding\nWENAM\nstring(256)\nWeld name\nWEPROC\nstring(256)\nWelding process\nWESTRF\nelement\nWhitespace Entity Style reference\nWESUSP\nreal\nWeld end suspension\nWEXPTX\nstring(32)\nWelding Fish Tail: Explanation text\nWFIN\nstring(256)\nWeld finish\nWFISTA\nstring(32)\nWelding Fish tail: Additional Text 1\nWFISTB\nstring(32)\nWelding Fish tail: Additional Text 2\nWFISTC\nstring(32)\nWelding Fish tail: Additional Text 3\nWFLELM\nelement\nReference to Workflow Element\nWFRDBL\nreal(5)\nDetailing Weld Free Doubles\nWFTXA\nstring(32)\nWelding Free text 1\nWFTXB\nstring(32)\nWelding Free text 2\nWFTXC\nstring(32)\nWelding Free text 3\nWFTXD\nstring(32)\nWelding Free text 4\nWGANG\nreal\nWeld groove angle\nWGAP\nreal\nWeld Gap\nWGNAS\ninteger\nWelding symbol ID (arrow side)\nWGNOS\ninteger\nWelding symbol ID (other side)\nWGOLD\nlogical\nGolden Weld\nWGROUP\ninteger\nWeld Grouping Option\nWGSTRF\nelement\nWhitespace Generic Style reference\nWHOLEC\nreal\nArray of Whole Cells\nWIANG\nreal\nWeld inclination angle\nWIDARR\nreal(10)\nWidth array\nWIDT\nreal\nWidth\nWIFA\nreal\nWind multiplier\nWIMAS\nlogical\nIntermittent weld (arrow side)\nWIMOS\nlogical\nIntermittent weld (other side)\nWINDAS\nstring(32)\nWelding Index (Arrow Side)\nWINDOS\nstring(32)\nWelding Index (Other Side)\nWINT\nlogical\nTrue if intermittent weld\nWINTL\nreal\nIntermittent weld length\nWINTP\nreal\nIntermittent weld pitch\nWIRESZ\nstring(120)\nWire size\nWISYM\ninteger\nWelding Process symbol number\nWJPOS\npos\nImplied weld position\nWJUSL\nword\nWall Justification Line\nWLDAAS\nreal\nWeld chamfer angle arrow side\nWLDAOS\nreal\nWeld chamfer angle (other side)\nWLDBAS\ninteger\nWeld Backing (arrow side)\nWLDBOS\ninteger\nWeld Backing (other side)\nWLDC\ninteger\nWeld Code\nWLDCAS\nreal\nWeld width (arrow side)\nWLDCOS\nreal\nWeld width (other side)\nWLDDAS\nreal\nWeld Diameter (arrow side)\nWLDDIA\nreal\nDiameter(width) for plug/slot welds\nWLDDOS\nreal\nWeld diameter (other side)\nWLDEAS\nreal\nWeld thickness (arrow side)\nWLDEOS\nreal\nWeld thickness (other side)\nWLDFAS\ninteger\nWelding Finish (arrow side)\nWLDFOS\ninteger\nWelding Finish (other side)\nWLDHAS\ninteger\nWelding Spacer (arrow side)\nWLDHOS\ninteger\nWelding Spacer (other side)\nWLDINF\ninteger\nWelding information\nWLDLAS\nreal\nWeld segment length (arrow side)\nWLDLOS\nreal\nWeld segment length (other side)\nWLDN\ninteger\nWeld number\nWLDNAS\ninteger\nNumber of weld segments (arrow side)\nWLDNDT\nlogical\nWelding NDT (Non-Destructive Testing)\nWLDNOS\ninteger\nNumber of weld segments (other side)\nWLDP\nstring(4)\nWeld number prefix\nWLDPOS\nstring(26)\nWelding position\nWLDRAS\nreal\nWeld chamfer Gap (arrow side)\nWLDREF\nelement\ninteger\nReturn reference from Ppoint or WELD to IWELD or RWELD element\nWLDRND\nlogical\nFlag weld all round\nWLDROS\nreal\nWeld chamfer Gap (other side)\nWLDSAS\nreal\nWeld chamfer depth (arrow side)\nWLDSOS\nreal\nWeld chamfer depth (other side)\nWLDTAS\ninteger\nWeld process number (arrow side)\nWLDTHY\nreal\nWeld material thickness (Y direction)\nWLDTHZ\nreal\nWeld material thickness (Z direction)\nWLDTOS\ninteger\nWeld process number (other side)\nWLDTYP\ninteger\nWelding Element Type Number\nWLDVAS\nreal\nWeld segment offset (arrow side)\nWLDVOS\nreal\nWeld segment Offset (other side)\nWLDZAS\nreal\nWeld leg length (arrow side)\nWLDZOS\nreal\nWeld leg length (other side)\nWLEGL\nreal\nWeld leg length\nWLEGTX\nstring(32)\nWelding legend text\nWLEN\nreal\nWeld length\nWLLEN\nreal\nLeg length of the weld\nWLNGTH\nreal\nWeld Length\nWMAX\ninteger\nMaximum weld number in current spool drawing\nWMDREF\nelement\nReference to weld master data\nWNAM\nstring(26)\nWeld name\nWNAMAS\nstring(32)\nWeld Name (arrow side)\nWNAMOS\nstring(32)\nWeld Name (other side)\nWNCAT\nstring(32)\nWelding NDT Category name\nWNDT\nstring(256)\nNo destructive test for the weld\nWNDTN\nstring(32)\nWelding NDT type name\nWNDTP\nreal\nWelding NDT percentage\nWNLAY\ninteger\nNumber of weld layers\nWNPROC\nstring(32)\nWelding NDT process name\nWNTHK\nstring(32)\nWeld Name Thickness\nWORI\nori\nWorld orientation\nWORPOS\npos\nWorld position\nWOSTRF\nelement\nWhitespace Objective Preference Style reference\nWPAR\nword(100)\nParameters as a word\nWPDAS\nreal\nWeld segment distance (arrow side)\nWPDOS\nreal\nWeld segment distance (other side)\nWPLEN\nreal\nWeight per length\nWPOST\nstring(32)\nWeld mark text\nWPRE\nreal\nWind pressure\nWPROC\nstring(26)\nWelding process\nWRANG\nreal\nWeld rotation angle\nWRKMRK\nstring(30)\nWorking Revision Indicator String\nWRKSEQ\nstring(256)\nWorking sequence\nWRKSHR\ninteger\nWork Share\nWSADER\nreal\nWhitespace alignment deviation\nWSADET\nstring(80)\nWhitespace alignment deviation\nWSAIAT\ninteger\nWhitespace annotation intersections allowed (Unset, ByStyle, ByTemp, Off/False, CONLOnly, On/True)\nWSAPPR\nreal\nWhitespace placement priority\nWSAPPT\nstring(80)\nWhitespace placement priority\nWSDCAT\ninteger\nWhitespace dog leg creation allowed (Unset ByStyle ByTemp Off/False On/True)\nWSDRAT\ninteger\nWhitespace dog leg removal allowed (Unset ByStyle ByTemp Off/False On/True)\nWSERSF\nelement\nWhitespace Entity Rule Set reference\nWSHOP\nlogical\nWeld shop/site flag on IWELD/RWELD\nWSLEN\nreal\nLength for slot weld\nWSLLRT\ninteger\nWhitespace leader line restriction (-5 ByStyle -2 UseGen 0 Off/False 1 On/True)\nWSMADR\nreal\nWhitespace minimum attachment point distance\nWSMADT\nstring(80)\nWhitespace minimum attachment point distance\nWSMASR\nreal\nWhitespace minimum annotation spacing\nWSMAST\nstring(80)\nWhitespace minimum annotation spacing\nWSOAGR\nreal\nWhitespace Objective Preference - A-GS overlap\nWSOAGT\nstring(80)\nWhitespace Objective Preference - A-GS overlap\nWSOALR\nreal\nWhitespace Objective Preference - alignment violation\nWSOALT\nstring(80)\nWhitespace Objective Preference - alignment violation\nWSOARR\nreal\nWhitespace Objective Preference - A-RS overlap\nWSOART\nstring(80)\nWhitespace Objective Preference - A-RS overlap\nWSODSR\nreal\nWhitespace Objective Preference - insertion distance deviation\nWSODST\nstring(80)\nWhitespace Objective Preference - insertion distance deviation\nWSOOVR\nreal\nWhitespace Objective Preference - outside of view violation\nWSOOVT\nstring(80)\nWhitespace Objective Preference - outside of view violation\nWSOPDR\nreal\nWhitespace optimal distance\nWSOPDT\nstring(80)\nWhitespace optimal distance\nWSOVMT\ninteger\nWhitespace Out-of-View mode (ByStyle UseGlob Off InsidePref InsideOnly OutsidePref OutsideOnly)\nWSOVSD\nstring(80)\nWhitespace Out-of-View preferred sides (ByStyle UseGeneric or comma-sep. comb. of Top Right Bottom Left)\nWSOVSI\ninteger\nWhitespace Out-of-View preferred sides (-5 ByStyle -2 UseGen, or bit-coded 1 Top 2 Right 4 Bottom 8 Left)\nWSOXAR\nreal\nWhitespace Objective Preference - X-Angs violation\nWSOXAT\nstring(80)\nWhitespace Objective Preference - X-Angs violation\nWSPACE\nlogical\nTrue if spacer is to be used\nWSPDAN\nreal\nWhitespace Placement Direction angle\nWSPDDG\nstring(80)\nWhitespace Placement Direction angle\nWSPDIN\nreal(2)\nWhitespace Placement Direction intervals\nWSPDIT\nstring(80)\nWhitespace Placement Direction intervals\nWSPEC\nelement\nWeld specification on IWELD/RWELD\nWSPLMT\ninteger\nWhitespace placement mode (Unset ByStyle ByTemp DontMove PreferOrig OptimiseDist Free)\nWSPORF\nelement\nWhitespace Picture Owner reference\nWSPOST\ninteger\nWhitespace pic. owner result state (ReviewPending, Accepted, Rejected)\nWSPROC\nstring(26)\nWelding standard process\nWSSAS\nreal\nWeld penetration depth (arrow side)\nWSSOS\nreal\nWeld penetration depth (other side)\nWSSTQI\ninteger\nWhitespace quadrants (bit-coded 1 TopRight 2 TopLeft 4 BottomLeft 8 BottomRight)\nWSSTQS\nstring(80)\nWhitespace quadrants (comma-sep. comb. of TopRight TopLeft BottomLeft BottomRight)\nWSSUSP\nreal\nWeld start suspension\nWSTAND\nstring(256)\nWeld standard\nWSTDV\nstring(256)\nWeld standard vesrion\nWSXANG\nreal(60)\nWhitespace Expected Angles\nWSXANT\nstring(2000)\nWhitespace Expected Angles\nWTCOM\nstring(300)\nWeld table comment\nWTEREF\nelement\ninteger\nWall thickness element reference\nWTEST\nstring(256)\nTest procedure for the weld\nWTHICK\nreal\nWall thickness\nWTHREF\nelement\nWall thickness table reference\nWTOL\nstring(1000)\nWall thickness tolerance / Weight tolerance\nWTORCH\ndir\nWeld torch vector\nWTPROC\nstring(26)\nWelding test procedure\nWTRANS\nreal(12)\nTransformation matrix to world\nWTSTAT\nstring(26)\nWeld table status\nWTYPE\nword\nWeld type\nWUNIQ\nlogical\nWelding Element Unique Flag\nWVOL\nreal(6)\nEnclosing box volume in world coordinates\nWVTAS\ninteger\nWeld type (arrow side)\nWVTOS\ninteger\nWeld type (other side)\n\n\n"}
{"Headers": "Attribute X", "Content": "XAMANG\nreal\nword\nCross section along mounting angle\nXAREA\nstring(1000)\n\nCross sectional area\nXAXIS\ndir\n\nxAxis\nXBEVEL\nlogical\n\nTrue if X-bevel\nXBOT\nreal\n\nBottom X length\nXBSH\nreal\n\nX bottom shear: inclination of bottom face to local X axis\nXFTPT\npos\nword\nCross section foot point\nXGMREF\nelement\n\nReference to laser survey in which volumes will be demolished\nXINCL\nreal\nword\nCross section inclination angle\nXINDEX\ninteger\n\nLaser Image Storage X index\nXLEN\nreal\n\nX length\nXOFF\nreal\n\nX-offset\nXRLIST\nelement(10000)\nelemtype\nList distributed attributes\nXRLSTT\nword(2000)\nelemtype\nList distributed attributes\nXRPNTR\nelement\n\nDistributed Attribute reference\nXRQCNT\ninteger\nelemtype\nGet distributed attributes element count\nXRQELE\nelement\nelemtype, integer\nGet distributed attributes element\nXRSTRT\nelement\n\nDistributed Attributes reference\nXTEX\nstring(2000)\n\nX text\nXTHK\nreal\nword\nCross section thickness\nXTOP\nreal\n\nTop X length\nXTPPT\npos\nword\nCross section top point\nXTRA\nreal\n\nExtra length requirement for BOLTS\nXTSH\nreal\n\nX top shear: inclination of top face to local X axis\nXXMANG\nreal\nword\nCross section cross mounting angle\nXYOFFS\nreal(2)\n\nXY offset\nXYPS\npos\n\n2D Position or Offset for Labels\nXYSC\nreal(2)\n\nLabel XY size\nXYSIZE\nreal(2)\n\nsize array for grids\n\nAttribute Name\nData Type\nQualifier\nDescription\nXAMANG\nreal\nword\nCross section along mounting angle\nXAREA\nstring(1000)\nCross sectional area\nXAXIS\ndir\nxAxis\nXBEVEL\nlogical\nTrue if X-bevel\nXBOT\nreal\nBottom X length\nXBSH\nreal\nX bottom shear: inclination of bottom face to local X axis\nXFTPT\npos\nword\nCross section foot point\nXGMREF\nelement\nReference to laser survey in which volumes will be demolished\nXINCL\nreal\nword\nCross section inclination angle\nXINDEX\ninteger\nLaser Image Storage X index\nXLEN\nreal\nX length\nXOFF\nreal\nX-offset\nXRLIST\nelement(10000)\nelemtype\nList distributed attributes\nXRLSTT\nword(2000)\nelemtype\nList distributed attributes\nXRPNTR\nelement\nDistributed Attribute reference\nXRQCNT\ninteger\nelemtype\nGet distributed attributes element count\nXRQELE\nelement\nelemtype, integer\nGet distributed attributes element\nXRSTRT\nelement\nDistributed Attributes reference\nXTEX\nstring(2000)\nX text\nXTHK\nreal\nword\nCross section thickness\nXTOP\nreal\nTop X length\nXTPPT\npos\nword\nCross section top point\nXTRA\nreal\nExtra length requirement for BOLTS\nXTSH\nreal\nX top shear: inclination of top face to local X axis\nXXMANG\nreal\nword\nCross section cross mounting angle\nXYOFFS\nreal(2)\nXY offset\nXYPS\npos\n2D Position or Offset for Labels\nXYSC\nreal(2)\nLabel XY size\nXYSIZE\nreal(2)\nsize array for grids\n\n\n"}
{"Headers": "Attribute Y", "Content": "YBEVEL\nlogical\n\nTrue if Y-bevel\nYBOT\nreal\n\nBottom Y length\nYBSH\nreal\n\nY bottom shear: inclination of bottom face to local Y axis\nYDIR\ndir\n\nPreferred Y axis direction\nYGAP\nreal\n\nY-Gap\nYINDEX\ninteger\n\nLaser Image Storage Y index\nYLEN\nreal\n\nY length\nYOFF\nreal\n\nY-offset\nYOUN\nreal\n\nSpot value of Youngs modulus\nYTEX\nstring(2000)\n\nY text\nYTOP\nreal\n\nTop Y length\nYTSH\nreal\n\nY top shear: inclination of top face to local Y axis\n\nAttribute Name\nData Type\nQualifier\nDescription\nYBEVEL\nlogical\nTrue if Y-bevel\nYBOT\nreal\nBottom Y length\nYBSH\nreal\nY bottom shear: inclination of bottom face to local Y axis\nYDIR\ndir\nPreferred Y axis direction\nYGAP\nreal\nY-Gap\nYINDEX\ninteger\nLaser Image Storage Y index\nYLEN\nreal\nY length\nYOFF\nreal\nY-offset\nYOUN\nreal\nSpot value of Youngs modulus\nYTEX\nstring(2000)\nY text\nYTOP\nreal\nTop Y length\nYTSH\nreal\nY top shear: inclination of top face to local Y axis\n\n\n"}
{"Headers": "Engineering Case World Element (ECASWL)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\n\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nName\nDescription\nWorld Element (WORLD)\n"}
{"Headers": "Engineering Canvas Drawing Border Element (ECBORD)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nEcstd\nEngineering Canvas Standard\nECBSReference\nEngineering canvas backing sheet reference\nEctarr\nEngineering Canvas Types\nEcgreference\nEngineering Canvas Grid Reference\nEcder\nEngineering canvas draw entity reference\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nEcstd\nEngineering Canvas Standard\nECBSReference\nEngineering canvas backing sheet reference\nEctarr\nEngineering Canvas Types\nEcgreference\nEngineering Canvas Grid Reference\nEcder\nEngineering canvas draw entity reference\nEngineering Canvas Configuration Group Element (ECCFGR)\nNone\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nEcstd\nEngineering Canvas Standard\nECBSReference\nEngineering canvas backing sheet reference\nEctarr\nEngineering Canvas Types\nEcgreference\nEngineering Canvas Grid Reference\nEcder\nEngineering canvas draw entity reference\n\n\n\nEngineering Canvas Configuration Group Element (ECCFGR)\nName\nEcdnam\nEcstd\nECBSReference\nEctarr\nEcgreference\nEcder\nEngineering Canvas Configuration Group Element (ECCFGR)"}
{"Headers": "Engineering Canvas Configuration Group Element (ECCFGR)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEngineering Canvas Configuration World Element (ECCFWL)\nEngineering Canvas Drawing Border Element (ECBORD)\nEngineering Canvas Connection Point Definition Element (ECCNPDEF)\nEngineering Canvas Grid Definition Element (ECGRID)\nEngineering Canvas Symbol Template Variant Element (ECSTVARIANT)\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Template Sheet Element (ECTSHE)\nEngineering Canvas Drawing Type Element (ECTYPE)\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\n\n\n\nEngineering Canvas Configuration World Element (ECCFWL)\nEngineering Canvas Drawing Border Element (ECBORD)\nEngineering Canvas Symbol Template Variant Element (ECSTVARIANT)\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Template Sheet Element (ECTSHE)\nEngineering Canvas Drawing Type Element (ECTYPE)\nName\nEcdnam\nDescription\nEngineering Canvas Configuration World Element (ECCFWL)\nEngineering Canvas Drawing Border Element (ECBORD)\nEngineering Canvas Connection Point Definition Element (ECCNPDEF)\nEngineering Canvas Grid Definition Element (ECGRID)\nEngineering Canvas Symbol Template Variant Element (ECSTVARIANT)\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Template Sheet Element (ECTSHE)\nEngineering Canvas Drawing Type Element (ECTYPE)"}
{"Headers": "Engineering Canvas Configuration World Element (ECCFWL)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nEngineering Canvas Configuration Group Element (ECCFGR)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nEngineering Canvas Configuration Group Element (ECCFGR)\nName\nDescription\nWorld Element (WORLD)\nEngineering Canvas Configuration Group Element (ECCFGR)"}
{"Headers": "Engineering Canvas Connection Point Template Element (ECCNPT)", "Content": "Primary Element\nName\nName of the element\nEccpre\nEngineering canvas connection point graphics reference\nEccpdr\nEngineering canvas connection point type definition reference\nEcmdat\nSequence Number\nName\nName of the element\nEccpre\nEngineering canvas connection point graphics reference\nEccpdr\nEngineering canvas connection point type definition reference\nEcmdat\nSequence Number\nEngineering Canvas Functional Symbol Template Element (ECFUNC)\nEngineering Canvas Symbol Template Element (ECSYMT)\nNone\nName\nName of the element\nEccpre\nEngineering canvas connection point graphics reference\nEccpdr\nEngineering canvas connection point type definition reference\nEcmdat\nSequence Number\n\n\n\nEngineering Canvas Functional Symbol Template Element (ECFUNC)\nEngineering Canvas Symbol Template Element (ECSYMT)\nName\nEccpre\nEccpdr\nEcmdat\nEngineering Canvas Functional Symbol Template Element (ECFUNC)\nEngineering Canvas Symbol Template Element (ECSYMT)"}
{"Headers": "Engineering Canvas Connection Element (ECCONNECT)", "Content": "Primary Element\nEccfrom\nEngineering canvas connection from\nEccto\nEngineering canvas connection to\nEccfrom\nEngineering canvas connection from\nEccto\nEngineering canvas connection to\nEngineering Canvas Steel Element (ECSHEE)\nEngineering Canvas Template Sheet Element (ECTSHE)\nNone\nEccfrom\nEngineering canvas connection from\nEccto\nEngineering canvas connection to\n\n\n\nEngineering Canvas Steel Element (ECSHEE)\nEngineering Canvas Template Sheet Element (ECTSHE)\nEccfrom\nEccto\nEngineering Canvas Steel Element (ECSHEE)\nEngineering Canvas Template Sheet Element (ECTSHE)"}
{"Headers": "Engineering Canvas Connector Template Element (ECCONT)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nEctfml\nEngineering canvas text formula\nClaNam\nClass Name\nECSReference\nEngineering canvas symbol reference\nEcltyp\nEngineering Canvas Linetype\nEcgtyp\nEngineering Canvas Glyphtype\nEclclr\nEngineering Canvas Line Colour\nECTPLO\nTemplate only flag\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nEctfml\nEngineering canvas text formula\nClaNam\nClass Name\nECSReference\nEngineering canvas symbol reference\nEcltyp\nEngineering Canvas Linetype\nEcgtyp\nEngineering Canvas Glyphtype\nEclclr\nEngineering Canvas Line Colour\nECTPLO\nTemplate only flag\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Default Label Element (ECDFLA)\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nEctfml\nEngineering canvas text formula\nClaNam\nClass Name\nECSReference\nEngineering canvas symbol reference\nEcltyp\nEngineering Canvas Linetype\nEcgtyp\nEngineering Canvas Glyphtype\nEclclr\nEngineering Canvas Line Colour\nECTPLO\nTemplate only flag\n\n\n\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Default Label Element (ECDFLA)\nName\nEcdnam\nDescription\nEcstd\nEctfml\nClaNam\nECSReference\nEcltyp\nEcgtyp\nEclclr\nECTPLO\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Default Label Element (ECDFLA)"}
{"Headers": "Engineering Canvas Default Label Element (ECDFLA)", "Content": "Primary Element\nECPIReference\nEngineering Canvas palette item reference\nEcloffset\nEngineering Canvas Label Offset\nECPIReference\nEngineering Canvas palette item reference\nEcloffset\nEngineering Canvas Label Offset\nEngineering Canvas Connector Template Element (ECCONT)\nEngineering Canvas Symbol Template Element (ECSYMT)\nNone\nECPIReference\nEngineering Canvas palette item reference\nEcloffset\nEngineering Canvas Label Offset\n\n\n\nEngineering Canvas Connector Template Element (ECCONT)\nEngineering Canvas Symbol Template Element (ECSYMT)\nECPIReference\nEcloffset\nEngineering Canvas Connector Template Element (ECCONT)\nEngineering Canvas Symbol Template Element (ECSYMT)"}
{"Headers": "Engineering Canvas Drawing Element (ECDRAW)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nEcnumb\nEngineering Canvas number\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECPReference\nEngineering Canvas page reference\nPrmtag\nAssociated Primary Element\nECMTDR\nEngineering Canvas Metadata Reference\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nEcnumb\nEngineering Canvas number\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECPReference\nEngineering Canvas page reference\nPrmtag\nAssociated Primary Element\nECMTDR\nEngineering Canvas Metadata Reference\n\nNone\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nEcnumb\nEngineering Canvas number\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECPReference\nEngineering Canvas page reference\nPrmtag\nAssociated Primary Element\nECMTDR\nEngineering Canvas Metadata Reference\n\n\n\nName\nEcdnam\nEcnumb\nDescription\nEcstd\nECPReference\nPrmtag\nECMTDR\n\nLegal Members"}
{"Headers": "Engineering Canvas Functional Symbol Template Element (ECFUNC)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcstty\nSymbol template type\nECTPLO\nTemplate only flag\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcstty\nSymbol template type\nECTPLO\nTemplate only flag\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Connection Point Template Element (ECCNPT)\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcstty\nSymbol template type\nECTPLO\nTemplate only flag\n\n\n\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Connection Point Template Element (ECCNPT)\nName\nEcdnam\nDescription\nEcstd\nECSReference\nEcstty\nECTPLO\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Connection Point Template Element (ECCNPT)"}
{"Headers": "Engineering Canvas Connection Point Definition Element (ECCNPDEF)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEngineering Canvas Configuration Group Element (ECCFGR)\nNone\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\n\n\n\nEngineering Canvas Configuration Group Element (ECCFGR)\nName\nEcdnam\nDescription\nEngineering Canvas Configuration Group Element (ECCFGR)"}
{"Headers": "Engineering Canvas Connection Point Instance Element (ECCNPI)", "Content": "Primary Element\nName\nName of the element\nEccpre\nEngineering canvas connection point graphics reference\nEccptr\nEngineering canvas connection point template reference\nEccpdr\nEngineering canvas connection point type definition reference\nEcmdat\nSequence Number\nECMTDR\nEngineering Canvas Metadata Reference\nName\nName of the element\nEccpre\nEngineering canvas connection point graphics reference\nEccptr\nEngineering canvas connection point template reference\nEccpdr\nEngineering canvas connection point type definition reference\nEcmdat\nSequence Number\nECMTDR\nEngineering Canvas Metadata Reference\n\nEngineering Canvas OPC Element (ECOPC)\nEngineering Canvas Template Index Element (ECTIND)\nNone\nName\nName of the element\nEccpre\nEngineering canvas connection point graphics reference\nEccptr\nEngineering canvas connection point template reference\nEccpdr\nEngineering canvas connection point type definition reference\nEcmdat\nSequence Number\nECMTDR\nEngineering Canvas Metadata Reference\n\n\n\nEngineering Canvas OPC Element (ECOPC)\nEngineering Canvas Template Index Element (ECTIND)\nName\nEccpre\nEccptr\nEccpdr\nEcmdat\nECMTDR\n\nEngineering Canvas OPC Element (ECOPC)\nEngineering Canvas Template Index Element (ECTIND)"}
{"Headers": "Engineering Canvas Mapping Repository Element (ECMREP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nEngineering Canvas Drawing Type Element (ECTYPE)\nEngineering Canvas Symbol Mapping Element (ECSMAP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nEngineering Canvas Drawing Type Element (ECTYPE)\nEngineering Canvas Symbol Mapping Element (ECSMAP)\nName\nDescription\nEngineering Canvas Drawing Type Element (ECTYPE)\nEngineering Canvas Symbol Mapping Element (ECSMAP)"}
{"Headers": "Engineering Canvas OPC Element (ECOPC)", "Content": "Primary Element\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nECPIReference\nEngineering Canvas palette item reference\nEcopcr\nEngineering Canvas OPC References\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nECPIReference\nEngineering Canvas palette item reference\nEcopcr\nEngineering Canvas OPC References\nEngineering Canvas Steel Element (ECSHEE)\nEngineering Canvas Template Sheet Element (ECTSHE)\nEngineering Canvas Connection Point Instance Element (ECCNPI)\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nECPIReference\nEngineering Canvas palette item reference\nEcopcr\nEngineering Canvas OPC References\n\n\n\nEngineering Canvas Steel Element (ECSHEE)\nEngineering Canvas Template Sheet Element (ECTSHE)\nEcstd\nECSReference\nECPIReference\nEcopcr\nEngineering Canvas Steel Element (ECSHEE)\nEngineering Canvas Template Sheet Element (ECTSHE)\nEngineering Canvas Connection Point Instance Element (ECCNPI)"}
{"Headers": "Engineering Canvas Revision Cloud Element (ECREVC)", "Content": "Primary Element\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcrmsu\nEngineering Canvas Revision Mark Subject\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcrmsu\nEngineering Canvas Revision Mark Subject\nEngineering Canvas Steel Element (ECSHEE)\nNone\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcrmsu\nEngineering Canvas Revision Mark Subject\n\n\n\nEngineering Canvas Steel Element (ECSHEE)\nEcstd\nECSReference\nEcrmsu\nEngineering Canvas Steel Element (ECSHEE)"}
{"Headers": "Engineering Canvas Revision Mark Element (ECREVM)", "Content": "Primary Element\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcrmsu\nEngineering Canvas Revision Mark Subject\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcrmsu\nEngineering Canvas Revision Mark Subject\nEngineering Canvas Steel Element (ECSHEE)\nNone\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcrmsu\nEngineering Canvas Revision Mark Subject\n\n\n\nEngineering Canvas Steel Element (ECSHEE)\nEcstd\nECSReference\nEcrmsu\nEngineering Canvas Steel Element (ECSHEE)"}
{"Headers": "Engineering Canvas Steel Element (ECSHEE)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nEcnumb\nEngineering Canvas number\nAuthor\nAuthor\nSheet Title\nSheet title\nRvauthor\nRevision author\nChkdate\nDate checked\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSHReference\nEngineering canvas sheet reference\nEctref\nEngineering Canvas Type Reference\nEcguard\nEngineering Canvas Guard Level\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nEcnumb\nEngineering Canvas number\nAuthor\nAuthor\nSheet Title\nSheet title\nRvauthor\nRevision author\nChkdate\nDate checked\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSHReference\nEngineering canvas sheet reference\nEctref\nEngineering Canvas Type Reference\nEcguard\nEngineering Canvas Guard Level\n\nEngineering Canvas Connection Element (ECCONNECT)\n\n\nEngineering Canvas OPC Element (ECOPC)\nEngineering Canvas Revision Cloud Element (ECREVC)\nEngineering Canvas Revision Mark Element (ECREVM)\nEngineering Canvas Table Element (ECTABL)\nEngineering Canvas Text Element (ECTEXT)\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nEcnumb\nEngineering Canvas number\nAuthor\nAuthor\nSheet Title\nSheet title\nRvauthor\nRevision author\nChkdate\nDate checked\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSHReference\nEngineering canvas sheet reference\nEctref\nEngineering Canvas Type Reference\nEcguard\nEngineering Canvas Guard Level\n\n\n\nEngineering Canvas Connection Element (ECCONNECT)\nEngineering Canvas OPC Element (ECOPC)\nEngineering Canvas Revision Cloud Element (ECREVC)\nEngineering Canvas Revision Mark Element (ECREVM)\nEngineering Canvas Table Element (ECTABL)\nEngineering Canvas Text Element (ECTEXT)\nName\nEcdnam\nEcnumb\nAuthor\nSheet Title\nRvauthor\nChkdate\nDescription\nEcstd\nECSHReference\nEctref\nEcguard\n\nEngineering Canvas Connection Element (ECCONNECT)\n\n\nEngineering Canvas OPC Element (ECOPC)\nEngineering Canvas Revision Cloud Element (ECREVC)\nEngineering Canvas Revision Mark Element (ECREVM)\nEngineering Canvas Table Element (ECTABL)\nEngineering Canvas Text Element (ECTEXT)"}
{"Headers": "Engineering Canvas Symbol Mapping Element (ECSMAP)", "Content": "Name\nName of the element\nDescription\nDescription of the element\nECPIReference\nEngineering Canvas palette item reference\nECMDEF\nMapping Default flag\nName\nName of the element\nDescription\nDescription of the element\nECPIReference\nEngineering Canvas palette item reference\nECMDEF\nMapping Default flag\nEngineering Canvas Mapping Repository Element (ECMREP)\nNone\nName\nName of the element\nDescription\nDescription of the element\nECPIReference\nEngineering Canvas palette item reference\nECMDEF\nMapping Default flag\n\n\n\nEngineering Canvas Mapping Repository Element (ECMREP)\nName\nDescription\nECPIReference\nECMDEF\nEngineering Canvas Mapping Repository Element (ECMREP)"}
{"Headers": "Engineering Canvas Symbol Template Variant Element (ECSTVARIANT)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nEngineering Canvas Configuration Group Element (ECCFGR)\nNone\nName\nName of the element\nEcdnam\nEngineering Canvas display name\n\n\n\nEngineering Canvas Configuration Group Element (ECCFGR)\nName\nEcdnam\nEngineering Canvas Configuration Group Element (ECCFGR)"}
{"Headers": "Engineering Canvas Symbol Palette Element (ECSYMP)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcpgrp\nEngineering Canvas Palette Group\nEcstd\nEngineering Canvas Standard\nEctarr\nEngineering Canvas Types\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcpgrp\nEngineering Canvas Palette Group\nEcstd\nEngineering Canvas Standard\nEctarr\nEngineering Canvas Types\nEngineering Canvas Configuration Group Element (ECCFGR)\n\nEngineering Canvas Connector Template Element (ECCONT)\nEngineering Canvas Functional Symbol Template Element (ECFUNC)\nEngineering Canvas Symbol Template Element (ECSYMT)\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcpgrp\nEngineering Canvas Palette Group\nEcstd\nEngineering Canvas Standard\nEctarr\nEngineering Canvas Types\n\n\n\nEngineering Canvas Configuration Group Element (ECCFGR)\nEngineering Canvas Connector Template Element (ECCONT)\nEngineering Canvas Functional Symbol Template Element (ECFUNC)\nEngineering Canvas Symbol Template Element (ECSYMT)\nName\nEcdnam\nDescription\nEcpgrp\nEcstd\nEctarr\nEngineering Canvas Configuration Group Element (ECCFGR)\n\nEngineering Canvas Connector Template Element (ECCONT)\nEngineering Canvas Functional Symbol Template Element (ECFUNC)\nEngineering Canvas Symbol Template Element (ECSYMT)"}
{"Headers": "Engineering Canvas Symbol Template Element (ECSYMT)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nECTPLO\nTemplate only flag\nEcstvr\nEngineering canvas symbol template variant reference\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nECTPLO\nTemplate only flag\nEcstvr\nEngineering canvas symbol template variant reference\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Connection Point Template Element (ECCNPT)\nEngineering Canvas Default Label Element (ECDFLA)\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nECTPLO\nTemplate only flag\nEcstvr\nEngineering canvas symbol template variant reference\n\n\n\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Connection Point Template Element (ECCNPT)\nEngineering Canvas Default Label Element (ECDFLA)\nName\nEcdnam\nDescription\nEcstd\nECSReference\nECTPLO\nEcstvr\nEngineering Canvas Symbol Palette Element (ECSYMP)\nEngineering Canvas Connection Point Template Element (ECCNPT)\nEngineering Canvas Default Label Element (ECDFLA)"}
{"Headers": "Engineering Canvas Table Element (ECTABL)", "Content": "Primary Element\nEcstd\nEngineering Canvas Standard\nEcmdat\nSequence Number\nECSReference\nEngineering canvas symbol reference\nEcstr\nEngineering canvas symbol template reference\nEctcr\nEngineering table cell reference\nECTCL\nEngineering table cell link reference\nEcstd\nEngineering Canvas Standard\nEcmdat\nSequence Number\nECSReference\nEngineering canvas symbol reference\nEcstr\nEngineering canvas symbol template reference\nEctcr\nEngineering table cell reference\nECTCL\nEngineering table cell link reference\nEngineering Canvas Steel Element (ECSHEE)\nNone\nEcstd\nEngineering Canvas Standard\nEcmdat\nSequence Number\nECSReference\nEngineering canvas symbol reference\nEcstr\nEngineering canvas symbol template reference\nEctcr\nEngineering table cell reference\nECTCL\nEngineering table cell link reference\n\n\n\nEngineering Canvas Steel Element (ECSHEE)\nEcstd\nEcmdat\nECSReference\nEcstr\nEctcr\nECTCL\nEngineering Canvas Steel Element (ECSHEE)"}
{"Headers": "Engineering Canvas Text Element (ECTEXT)", "Content": "Primary Element\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEngineering Canvas Steel Element (ECSHEE)\nNone\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\n\n\n\nEngineering Canvas Steel Element (ECSHEE)\nEcstd\nECSReference\nEngineering Canvas Steel Element (ECSHEE)"}
{"Headers": "Engineering Canvas Template Index Element (ECTIND)", "Content": "Primary Element\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcmdat\nSequence Number\nECPIReference\nEngineering Canvas palette item reference\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcmdat\nSequence Number\nECPIReference\nEngineering Canvas palette item reference\nEngineering Canvas Template Sheet Element (ECTSHE)\nEngineering Canvas Connection Point Instance Element (ECCNPI)\nEcstd\nEngineering Canvas Standard\nECSReference\nEngineering canvas symbol reference\nEcmdat\nSequence Number\nECPIReference\nEngineering Canvas palette item reference\n\n\n\nEngineering Canvas Template Sheet Element (ECTSHE)\nEcstd\nECSReference\nEcmdat\nECPIReference\nEngineering Canvas Template Sheet Element (ECTSHE)\nEngineering Canvas Connection Point Instance Element (ECCNPI)"}
{"Headers": "Engineering Canvas Template Sheet Element (ECTSHE)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSHReference\nEngineering canvas sheet reference\nEctref\nEngineering Canvas Type Reference\nECTRegion\nEngineering canvas template region\nEcguard\nEngineering Canvas Guard Level\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSHReference\nEngineering canvas sheet reference\nEctref\nEngineering Canvas Type Reference\nECTRegion\nEngineering canvas template region\nEcguard\nEngineering Canvas Guard Level\nEngineering Canvas Configuration Group Element (ECCFGR)\nEngineering Canvas Connection Element (ECCONNECT)\n\nEngineering Canvas OPC Element (ECOPC)\nEngineering Canvas Template Index Element (ECTIND)\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nEcstd\nEngineering Canvas Standard\nECSHReference\nEngineering canvas sheet reference\nEctref\nEngineering Canvas Type Reference\nECTRegion\nEngineering canvas template region\nEcguard\nEngineering Canvas Guard Level\n\n\n\nEngineering Canvas Configuration Group Element (ECCFGR)\nEngineering Canvas Connection Element (ECCONNECT)\nEngineering Canvas OPC Element (ECOPC)\nEngineering Canvas Template Index Element (ECTIND)\nName\nEcdnam\nDescription\nEcstd\nECSHReference\nEctref\nECTRegion\nEcguard\nEngineering Canvas Configuration Group Element (ECCFGR)\nLegal Members\nEngineering Canvas Connection Element (ECCONNECT)\n\nEngineering Canvas OPC Element (ECOPC)\nEngineering Canvas Template Index Element (ECTIND)"}
{"Headers": "Engineering Canvas Drawing Type Element (ECTYPE)", "Content": "Primary Element\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nDiscis\nAssociated disciplines\nEcdctype\nEngineering Canvas drawing content type\nEcpurpose\nDrawing Purpose\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nDiscis\nAssociated disciplines\nEcdctype\nEngineering Canvas drawing content type\nEcpurpose\nDrawing Purpose\nEngineering Canvas Configuration Group Element (ECCFGR)\nEngineering Canvas Mapping Repository Element (ECMREP)\nName\nName of the element\nEcdnam\nEngineering Canvas display name\nDescription\nDescription of the element\nDiscis\nAssociated disciplines\nEcdctype\nEngineering Canvas drawing content type\nEcpurpose\nDrawing Purpose\n\n\n\nEngineering Canvas Configuration Group Element (ECCFGR)\nEngineering Canvas Mapping Repository Element (ECMREP)\nName\nEcdnam\nDescription\nDiscis\nEcdctype\nEcpurpose\nEngineering Canvas Configuration Group Element (ECCFGR)\nEngineering Canvas Mapping Repository Element (ECMREP)"}
{"Headers": "World for Engineering Canvas Data Element (ECWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\n\n\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nName\nDescription\nWorld Element (WORLD)\n\n"}
{"Headers": "Engineering Document Element (EDOCMT)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nEDocRf\nEngineering Referenced Document\nEDocRv\nEngineering Document Revision\nEdocor\nStores Document order values\nName\nName of the element\nDescription\nDescription of the element\nEDocRf\nEngineering Referenced Document\nEDocRv\nEngineering Document Revision\nEdocor\nStores Document order values\nEngineering Document Pack Element (EDOCPK)\nNone\nName\nName of the element\nDescription\nDescription of the element\nEDocRf\nEngineering Referenced Document\nEDocRv\nEngineering Document Revision\nEdocor\nStores Document order values\n\n\n\nEngineering Document Pack Element (EDOCPK)\nName\nDescription\nEDocRf\nEDocRv\nEdocor\nEngineering Document Pack Element (EDOCPK)"}
{"Headers": "Engineering Document Pack Element (EDOCPK)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\nEngineering Document Pack World Element (EDOCWL)\nEngineering Document Element (EDOCMT)\nName\nName of the element\nDescription\nDescription of the element\nDistag\nDisplay tag\n\n\n\nEngineering Document Pack World Element (EDOCWL)\nEngineering Document Element (EDOCMT)\nName\nDescription\nDistag\nEngineering Document Pack World Element (EDOCWL)\nEngineering Document Element (EDOCMT)"}
{"Headers": "Engineering Document Pack World Element (EDOCWL)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nEngineering Document Pack Element (EDOCPK)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nEngineering Document Pack Element (EDOCPK)\nName\nDescription\nWorld Element (WORLD)\nEngineering Document Pack Element (EDOCPK)"}
{"Headers": "Engineering Feed Group Element (EFGRP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nEcdnam\nEngineering Canvas display name\nName\nName of the element\nDescription\nDescription of the element\nEcdnam\nEngineering Canvas display name\nWorld for Engineering Data Element (ENGWLD)\nEngineering Feed Mapping Repository Element (EFMREP)\nName\nName of the element\nDescription\nDescription of the element\nEcdnam\nEngineering Canvas display name\n\n\n\nWorld for Engineering Data Element (ENGWLD)\nEngineering Feed Mapping Repository Element (EFMREP)\nName\nDescription\nEcdnam\nWorld for Engineering Data Element (ENGWLD)\nEngineering Feed Mapping Repository Element (EFMREP)"}
{"Headers": "Engineering Feed Mapping Instance Element (EFMINS)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nEcdnam\nEngineering Canvas display name\nEfmfr\nEngineering Feed Mapping From\nEfmto\nEngineering Feed Mapping To\nEfmfun\nEngineering Feed Mapping Functional Type\nEfmdm\nEngineering Feed Mapping Dimension\nEfminc\nEngineering Feed Mapping Include\nName\nName of the element\nDescription\nDescription of the element\nEcdnam\nEngineering Canvas display name\nEfmfr\nEngineering Feed Mapping From\nEfmto\nEngineering Feed Mapping To\nEfmfun\nEngineering Feed Mapping Functional Type\nEfmdm\nEngineering Feed Mapping Dimension\nEfminc\nEngineering Feed Mapping Include\nEngineering Feed Mapping Instance Element (EFMINS)\nEngineering Feed Mapping Repository Element (EFMREP)\nEngineering Feed Mapping Instance Element (EFMINS)\nName\nName of the element\nDescription\nDescription of the element\nEcdnam\nEngineering Canvas display name\nEfmfr\nEngineering Feed Mapping From\nEfmto\nEngineering Feed Mapping To\nEfmfun\nEngineering Feed Mapping Functional Type\nEfmdm\nEngineering Feed Mapping Dimension\nEfminc\nEngineering Feed Mapping Include\n\n\n\nEngineering Feed Mapping Instance Element (EFMINS)\nEngineering Feed Mapping Repository Element (EFMREP)\nEngineering Feed Mapping Instance Element (EFMINS)\nName\nDescription\nEcdnam\nEfmfr\nEfmto\nEfmfun\nEfmdm\nEfminc\nEngineering Feed Mapping Instance Element (EFMINS)\nEngineering Feed Mapping Repository Element (EFMREP)\nEngineering Feed Mapping Instance Element (EFMINS)"}
{"Headers": "Engineering Feed Mapping Repository Element (EFMREP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nEcdnam\nEngineering Canvas display name\nEfmfr\nEngineering Feed Mapping From\nEfmto\nEngineering Feed Mapping To\nEfmfun\nEngineering Feed Mapping Functional Type\nName\nName of the element\nDescription\nDescription of the element\nEcdnam\nEngineering Canvas display name\nEfmfr\nEngineering Feed Mapping From\nEfmto\nEngineering Feed Mapping To\nEfmfun\nEngineering Feed Mapping Functional Type\nEngineering Feed Group Element (EFGRP)\nEngineering Feed Mapping Instance Element (EFMINS)\nName\nName of the element\nDescription\nDescription of the element\nEcdnam\nEngineering Canvas display name\nEfmfr\nEngineering Feed Mapping From\nEfmto\nEngineering Feed Mapping To\nEfmfun\nEngineering Feed Mapping Functional Type\n\n\n\nEngineering Feed Group Element (EFGRP)\nEngineering Feed Mapping Instance Element (EFMINS)\nName\nDescription\nEcdnam\nEfmfr\nEfmto\nEfmfun\nEngineering Feed Group Element (EFGRP)\nEngineering Feed Mapping Instance Element (EFMINS)"}
{"Headers": "Engineering Group Level Element (ENGGRP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nEngineering Group Level Element (ENGGRP)\nWorld for Engineering Data Element (ENGWLD)\nEngineering Group Level Element (ENGGRP)\nEngineering Item Element (ENGITE)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nEngineering Group Level Element (ENGGRP)\nWorld for Engineering Data Element (ENGWLD)\nEngineering Group Level Element (ENGGRP)\nEngineering Item Element (ENGITE)\nName\nDescription\nEngineering Group Level Element (ENGGRP)\nWorld for Engineering Data Element (ENGWLD)\nEngineering Group Level Element (ENGGRP)\nEngineering Item Element (ENGITE)"}
{"Headers": "Engineering Item Element (ENGITE)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nScsysf\nSystem reference array for schematic elements\nExclel\nLogically deleted from the project\nGovcom\nBaseline governing component reference\nClnref\nReferences to clones of this element\nGrrel\nGoverning revision relationship type\nName\nName of the element\nDescription\nDescription of the element\nScsysf\nSystem reference array for schematic elements\nExclel\nLogically deleted from the project\nGovcom\nBaseline governing component reference\nClnref\nReferences to clones of this element\nGrrel\nGoverning revision relationship type\nEngineering Group Level Element (ENGGRP)\nEngineering Item Element (ENGITE)\nEngineering Item Element (ENGITE)\nName\nName of the element\nDescription\nDescription of the element\nScsysf\nSystem reference array for schematic elements\nExclel\nLogically deleted from the project\nGovcom\nBaseline governing component reference\nClnref\nReferences to clones of this element\nGrrel\nGoverning revision relationship type\n\n\n\nEngineering Group Level Element (ENGGRP)\nEngineering Item Element (ENGITE)\nEngineering Item Element (ENGITE)\nName\nDescription\nScsysf\nExclel\nGovcom\nClnref\nGrrel\nEngineering Group Level Element (ENGGRP)\nEngineering Item Element (ENGITE)\nEngineering Item Element (ENGITE)"}
{"Headers": "World for Engineering Data Element (ENGWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nEngineering Feed Group Element (EFGRP)\nEngineering Group Level Element (ENGGRP)\nTMS Information Element (ENTMSI)\nEngineering Simulation Group Element (ESIMGR)\nLibrary Engineering Group Level Element (LIBGRP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nEngineering Feed Group Element (EFGRP)\nEngineering Group Level Element (ENGGRP)\nTMS Information Element (ENTMSI)\nEngineering Simulation Group Element (ESIMGR)\nLibrary Engineering Group Level Element (LIBGRP)\nName\nDescription\nWorld Element (WORLD)\nEngineering Feed Group Element (EFGRP)\nEngineering Group Level Element (ENGGRP)\nTMS Information Element (ENTMSI)\nEngineering Simulation Group Element (ESIMGR)\nLibrary Engineering Group Level Element (LIBGRP)"}
{"Headers": "TMS Information Element (ENTMSI)", "Content": "Primary Element\nName\nName of the element\nUsereq\nRequesting user\nTMSUSR\nTMS user\nName\nName of the element\nUsereq\nRequesting user\nTMSUSR\nTMS user\nWorld for Engineering Data Element (ENGWLD)\nNone\nName\nName of the element\nUsereq\nRequesting user\nTMSUSR\nTMS user\n\n\n\nWorld for Engineering Data Element (ENGWLD)\nName\nUsereq\nTMSUSR\nWorld for Engineering Data Element (ENGWLD)"}
{"Headers": "Engineering Simulation Group Element (ESIMGR)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld for Engineering Data Element (ENGWLD)\nWorld for Simulation Eng Data Element (SIMWLD)\nEngineering Simulation Information Element (ESIMIN)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld for Engineering Data Element (ENGWLD)\nWorld for Simulation Eng Data Element (SIMWLD)\nEngineering Simulation Information Element (ESIMIN)\nName\nDescription\nWorld for Engineering Data Element (ENGWLD)\nWorld for Simulation Eng Data Element (SIMWLD)\nEngineering Simulation Information Element (ESIMIN)"}
{"Headers": "Engineering Simulation Information Element (ESIMIN)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDBBLOB\nDatabase Binary Large Object\nCASENAME\nCase Name\nSIMNM\nSimulation name\nSrcnm\nSimulation Source Name\nPltare\nPlant area\nSimsrf\nSimulation source reference\nSimitf\nSimulation item reference\nName\nName of the element\nDescription\nDescription of the element\nDBBLOB\nDatabase Binary Large Object\nCASENAME\nCase Name\nSIMNM\nSimulation name\nSrcnm\nSimulation Source Name\nPltare\nPlant area\nSimsrf\nSimulation source reference\nSimitf\nSimulation item reference\nEngineering Simulation Group Element (ESIMGR)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDBBLOB\nDatabase Binary Large Object\nCASENAME\nCase Name\nSIMNM\nSimulation name\nSrcnm\nSimulation Source Name\nPltare\nPlant area\nSimsrf\nSimulation source reference\nSimitf\nSimulation item reference\n\n\n\nEngineering Simulation Group Element (ESIMGR)\nName\nDescription\nDBBLOB\nCASENAME\nSIMNM\nSrcnm\nPltare\nSimsrf\nSimitf\nEngineering Simulation Group Element (ESIMGR)"}
{"Headers": "Engineering 3D Model Group Element (ETMGRO)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nEngineering 3D Model World Element (ETMWLD)\nEngineering 3D Model Element (ETMODL)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nEngineering 3D Model World Element (ETMWLD)\nEngineering 3D Model Element (ETMODL)\nName\nDescription\nEngineering 3D Model World Element (ETMWLD)\nEngineering 3D Model Element (ETMODL)"}
{"Headers": "Engineering 3D Model Element (ETMODL)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nETMTTL\nEngineering 3D Model Title\nMIMHDR\nEngineering 3D Model File MIME Header\nName\nName of the element\nDescription\nDescription of the element\nETMTTL\nEngineering 3D Model Title\nMIMHDR\nEngineering 3D Model File MIME Header\nEngineering 3D Model Group Element (ETMGRO)\nNone\nName\nName of the element\nDescription\nDescription of the element\nETMTTL\nEngineering 3D Model Title\nMIMHDR\nEngineering 3D Model File MIME Header\n\n\n\nEngineering 3D Model Group Element (ETMGRO)\nName\nDescription\nETMTTL\nMIMHDR\nEngineering 3D Model Group Element (ETMGRO)"}
{"Headers": "Engineering 3D Model World Element (ETMWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nEngineering 3D Model Group Element (ETMGRO)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nEngineering 3D Model Group Element (ETMGRO)\nName\nDescription\nWorld Element (WORLD)\nEngineering 3D Model Group Element (ETMGRO)"}
{"Headers": "Functional Group level Element (FUNGRP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nFunctional Group level Element (FUNGRP)\nWorld for Functional Eng Data Element (FUNWLD)\nFunctional Group level Element (FUNGRP)\nEngineering Functional Item Element (FUNITE)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nFunctional Group level Element (FUNGRP)\nWorld for Functional Eng Data Element (FUNWLD)\nFunctional Group level Element (FUNGRP)\nEngineering Functional Item Element (FUNITE)\nName\nDescription\nFunctional Group level Element (FUNGRP)\nWorld for Functional Eng Data Element (FUNWLD)\nFunctional Group level Element (FUNGRP)\nEngineering Functional Item Element (FUNITE)"}
{"Headers": "Engineering Functional Item Element (FUNITE)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nExclel\nLogically deleted from the project\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nExclel\nLogically deleted from the project\nClnref\nReferences to clones of this element\nFunctional Group level Element (FUNGRP)\nEngineering Functional Item Element (FUNITE)\nEngineering Functional Item Element (FUNITE)\nName\nName of the element\nDescription\nDescription of the element\nExclel\nLogically deleted from the project\nClnref\nReferences to clones of this element\n\n\n\nFunctional Group level Element (FUNGRP)\nEngineering Functional Item Element (FUNITE)\nEngineering Functional Item Element (FUNITE)\nName\nDescription\nExclel\nClnref\nFunctional Group level Element (FUNGRP)\nEngineering Functional Item Element (FUNITE)\nEngineering Functional Item Element (FUNITE)"}
{"Headers": "World for Functional Eng Data Element (FUNWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nFunctional Group level Element (FUNGRP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nFunctional Group level Element (FUNGRP)\nName\nDescription\nWorld Element (WORLD)\nFunctional Group level Element (FUNGRP)"}
{"Headers": "Library Engineering Group Level Element (LIBGRP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld for Engineering Data Element (ENGWLD)\nLibrary Engineering Group Level Element (LIBGRP)\nLibrary Engineering Group Level Element (LIBGRP)\nLibrary Engineering Item Element (LIBITE)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld for Engineering Data Element (ENGWLD)\nLibrary Engineering Group Level Element (LIBGRP)\nLibrary Engineering Group Level Element (LIBGRP)\nLibrary Engineering Item Element (LIBITE)\nName\nDescription\nWorld for Engineering Data Element (ENGWLD)\nLibrary Engineering Group Level Element (LIBGRP)\nLibrary Engineering Group Level Element (LIBGRP)\nLibrary Engineering Item Element (LIBITE)"}
{"Headers": "Library Engineering Item Element (LIBITE)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nNrGrps\nNumber of groups\nDispnm\nDisplay Name\nName\nName of the element\nDescription\nDescription of the element\nNrGrps\nNumber of groups\nDispnm\nDisplay Name\nLibrary Engineering Item Element (LIBITE)\nEngineering Typical Item Element (TYPITE)\nName\nName of the element\nDescription\nDescription of the element\nNrGrps\nNumber of groups\nDispnm\nDisplay Name\n\n\n\nLibrary Engineering Item Element (LIBITE)\nEngineering Typical Item Element (TYPITE)\nName\nDescription\nNrGrps\nDispnm\nLibrary Engineering Item Element (LIBITE)\nEngineering Typical Item Element (TYPITE)"}
{"Headers": "Engineering List Element (LSTDEF)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nLstNam\nList name\nLstDsc\nList description\nLstDbv\nDatabase view associated with list\nLstDfs\nDefinition set name\nLstRid\nColumn Row ID\nUuid\nUniversally unique identifier\nLstPub\nCan be published to AVEVA NET\nLstUn\nShow Unset Nulref values\nLstLs\nShow leading slash for names\nLstUih\nShow units in headers\nLstWth\nWrap text in column headers\nLstWtc\nWrap text in cells of a grid\nLstPin\nShow column pins in column headers\nLstMsf\nMulti-select filter style\nLstVis\nVisible in list dropdown\nLstCfl\nColumn filtering\nLstGp\nShow the grouping panel\nLstCsr\nColumn items can be sorted\nLstCsm\nColumn summaries\nLstZf\nZoom factor\nDiscif\nReference of DISCIPLINE Element\nDiscis\nAssociated disciplines\nLstFlt\nList filter\nName\nName of the element\nDescription\nDescription of the element\nLstNam\nList name\nLstDsc\nList description\nLstDbv\nDatabase view associated with list\nLstDfs\nDefinition set name\nLstRid\nColumn Row ID\nUuid\nUniversally unique identifier\nLstPub\nCan be published to AVEVA NET\nLstUn\nShow Unset Nulref values\nLstLs\nShow leading slash for names\nLstUih\nShow units in headers\nLstWth\nWrap text in column headers\nLstWtc\nWrap text in cells of a grid\nLstPin\nShow column pins in column headers\nLstMsf\nMulti-select filter style\nLstVis\nVisible in list dropdown\nLstCfl\nColumn filtering\nLstGp\nShow the grouping panel\nLstCsr\nColumn items can be sorted\nLstCsm\nColumn summaries\nLstZf\nZoom factor\nDiscif\nReference of DISCIPLINE Element\nDiscis\nAssociated disciplines\nLstFlt\nList filter\nList Group Level Element (LSTGRP)\nNone\nName\nName of the element\nDescription\nDescription of the element\nLstNam\nList name\nLstDsc\nList description\nLstDbv\nDatabase view associated with list\nLstDfs\nDefinition set name\nLstRid\nColumn Row ID\nUuid\nUniversally unique identifier\nLstPub\nCan be published to AVEVA NET\nLstUn\nShow Unset Nulref values\nLstLs\nShow leading slash for names\nLstUih\nShow units in headers\nLstWth\nWrap text in column headers\nLstWtc\nWrap text in cells of a grid\nLstPin\nShow column pins in column headers\nLstMsf\nMulti-select filter style\nLstVis\nVisible in list dropdown\nLstCfl\nColumn filtering\nLstGp\nShow the grouping panel\nLstCsr\nColumn items can be sorted\nLstCsm\nColumn summaries\nLstZf\nZoom factor\nDiscif\nReference of DISCIPLINE Element\nDiscis\nAssociated disciplines\nLstFlt\nList filter\n\n\n\nList Group Level Element (LSTGRP)\nName\nDescription\nLstNam\nLstDsc\nLstDbv\nLstDfs\nLstRid\nUuid\nLstPub\nLstUn\nLstLs\nLstUih\nLstWth\nLstWtc\nLstPin\nLstMsf\nLstVis\nLstCfl\nLstGp\nLstCsr\nLstCsm\nLstZf\nDiscif\nDiscis\nLstFlt\nList Group Level Element (LSTGRP)"}
{"Headers": "List Group Level Element (LSTGRP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nCatNam\nCategory name\nUuid\nUniversally unique identifier\nCatUsr\nCategory owner\nName\nName of the element\nDescription\nDescription of the element\nCatNam\nCategory name\nUuid\nUniversally unique identifier\nCatUsr\nCategory owner\nList Group Level Element (LSTGRP)\nWorld for Engineering List Element (LSTWLD)\nEngineering List Element (LSTDEF)\nList Group Level Element (LSTGRP)\nName\nName of the element\nDescription\nDescription of the element\nCatNam\nCategory name\nUuid\nUniversally unique identifier\nCatUsr\nCategory owner\n\n\n\nList Group Level Element (LSTGRP)\nWorld for Engineering List Element (LSTWLD)\nEngineering List Element (LSTDEF)\nList Group Level Element (LSTGRP)\nName\nDescription\nCatNam\nUuid\nCatUsr\nList Group Level Element (LSTGRP)\nWorld for Engineering List Element (LSTWLD)\nEngineering List Element (LSTDEF)\nList Group Level Element (LSTGRP)"}
{"Headers": "World for Engineering List Element (LSTWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nList Group Level Element (LSTGRP)\nList Group Level Element (SLTGRP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nList Group Level Element (LSTGRP)\nList Group Level Element (SLTGRP)\nName\nDescription\nWorld Element (WORLD)\nList Group Level Element (LSTGRP)\nList Group Level Element (SLTGRP)"}
{"Headers": "Revision and Issue Element (REVISS) - Engineering", "Content": "Primary Element\nName\nName of the element\nRvnum\nRevision number\nRvnpts\nRevision number value parts\nRviss\nIssued\nRvcanc\nCancelled\nRVURI\nIssued object location\nExfile\nExtract file number\nPvno\nPicture version number\nNumber\nNumber\nRVFTYP\nRevision file type\nStahrf\nStatus History Reference\nDBBLOB\nDatabase Binary Large Object\nRelrev\nRelated revisions\nDSTYPE\nDatasheet type\nName\nName of the element\nRvnum\nRevision number\nRvnpts\nRevision number value parts\nRviss\nIssued\nRvcanc\nCancelled\nRVURI\nIssued object location\nExfile\nExtract file number\nPvno\nPicture version number\nNumber\nNumber\nRVFTYP\nRevision file type\nStahrf\nStatus History Reference\nDBBLOB\nDatabase Binary Large Object\nRelrev\nRelated revisions\nDSTYPE\nDatasheet type\nRevision Link Element Element (REVLNK)\nNone\nName\nName of the element\nRvnum\nRevision number\nRvnpts\nRevision number value parts\nRviss\nIssued\nRvcanc\nCancelled\nRVURI\nIssued object location\nExfile\nExtract file number\nPvno\nPicture version number\nNumber\nNumber\nRVFTYP\nRevision file type\nStahrf\nStatus History Reference\nDBBLOB\nDatabase Binary Large Object\nRelrev\nRelated revisions\nDSTYPE\nDatasheet type\n\n\n\nRevision Link Element Element (REVLNK)\nName\nRvnum\nRvnpts\nRviss\nRvcanc\nRVURI\nExfile\nPvno\nNumber\nRVFTYP\nStahrf\nDBBLOB\nRelrev\nDSTYPE\nRevision Link Element Element (REVLNK)"}
{"Headers": "Revision Link Elements Element (REVLKS) - Engineering", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nRevision Link Elements Element (REVLKS)\nRevision Links World Element (REVLWL)\nRevision Link Elements Element (REVLKS)\nRevision Link Element Element (REVLNK)\nName\nName of the element\n\n\n\nRevision Link Elements Element (REVLKS)\nRevision Links World Element (REVLWL)\nRevision Link Elements Element (REVLKS)\nRevision Link Element Element (REVLNK)\nName\nRevision Link Elements Element (REVLKS)\nRevision Links World Element (REVLWL)\nRevision Link Elements Element (REVLKS)\nRevision Link Element Element (REVLNK)"}
{"Headers": "Revision Link Element Element (REVLNK) - Engineering", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nCelref\nStatus Element reference\nRvcon\nRevision Configuration\nName\nName of the element\nDescription\nDescription of the element\nCelref\nStatus Element reference\nRvcon\nRevision Configuration\nRevision Link Elements Element (REVLKS)\nRevision and Issue Element (REVISS)\nName\nName of the element\nDescription\nDescription of the element\nCelref\nStatus Element reference\nRvcon\nRevision Configuration\n\n\n\nRevision Link Elements Element (REVLKS)\nRevision and Issue Element (REVISS)\nName\nDescription\nCelref\nRvcon\nRevision Link Elements Element (REVLKS)\nRevision and Issue Element (REVISS)"}
{"Headers": "Revision Links World Element (REVLWL) - Engineering", "Content": "Primary Element\nName\nName of the element\nRvlpos\nRevision links reference\nName\nName of the element\nRvlpos\nRevision links reference\nWorld Element (WORLD)\nRevision Link Elements Element (REVLKS)\nName\nName of the element\nRvlpos\nRevision links reference\n\n\n\nWorld Element (WORLD)\nRevision Link Elements Element (REVLKS)\nName\nRvlpos\nWorld Element (WORLD)\nRevision Link Elements Element (REVLKS)"}
{"Headers": "Range Configuration World (RNGWLD)", "Content": "Primary Element\nName\nDescription\n\n\n\nName\nDescription"}
{"Headers": "Counter Range Config (CNTRNG)", "Content": "Primary Element\nName\nDescription\n\n\n\nName\nDescription"}
{"Headers": "Attributes and Class (ATTCLS)", "Content": "Primary Element\nAttributes\nName\nDescription\n\n\n\nName\nDescription"}
{"Headers": "Range Rule (RNGRUL)", "Content": "Primary Elements\nName\nDescription\n\n\n\nName\nDescription"}
{"Headers": "Rule Condition (RULCND)", "Content": "Primary Element\nName\nDescription\n\n\n\nName\nDescription"}
{"Headers": "Simulation Group Level Element (SIMGRP)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nSimulation Group Level Element (SIMGRP)\nWorld for Simulation Eng Data Element (SIMWLD)\nSimulation Group Level Element (SIMGRP)\nEng Sim Item Element (SIMITE)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nSimulation Group Level Element (SIMGRP)\nWorld for Simulation Eng Data Element (SIMWLD)\nSimulation Group Level Element (SIMGRP)\nEng Sim Item Element (SIMITE)\nName\nDescription\nSimulation Group Level Element (SIMGRP)\nWorld for Simulation Eng Data Element (SIMWLD)\nSimulation Group Level Element (SIMGRP)\nEng Sim Item Element (SIMITE)"}
{"Headers": "Eng Sim Item Element (SIMITE)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nExclel\nLogically deleted from the project\nDispnm\nDisplay Name\nUniqid\nUnique Identifier\nLstupd\nLast updated from\nSiminf\nSimulation information reference\nClnref\nReferences to clones of this element\nName\nName of the element\nDescription\nDescription of the element\nExclel\nLogically deleted from the project\nDispnm\nDisplay Name\nUniqid\nUnique Identifier\nLstupd\nLast updated from\nSiminf\nSimulation information reference\nClnref\nReferences to clones of this element\nSimulation Group Level Element (SIMGRP)\nEng Sim Item Element (SIMITE)\nEng Sim Item Element (SIMITE)\nName\nName of the element\nDescription\nDescription of the element\nExclel\nLogically deleted from the project\nDispnm\nDisplay Name\nUniqid\nUnique Identifier\nLstupd\nLast updated from\nSiminf\nSimulation information reference\nClnref\nReferences to clones of this element\n\n\n\nSimulation Group Level Element (SIMGRP)\nEng Sim Item Element (SIMITE)\nEng Sim Item Element (SIMITE)\nName\nDescription\nExclel\nDispnm\nUniqid\nLstupd\nSiminf\nClnref\nSimulation Group Level Element (SIMGRP)\nEng Sim Item Element (SIMITE)\nEng Sim Item Element (SIMITE)"}
{"Headers": "Simulation Source Element (SIMSRC)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nDispnm\nDisplay Name\nName\nName of the element\nDescription\nDescription of the element\nDispnm\nDisplay Name\nWorld for Simulation Eng Data Element (SIMWLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nDispnm\nDisplay Name\n\n\n\nWorld for Simulation Eng Data Element (SIMWLD)\nName\nDescription\nDispnm\nWorld for Simulation Eng Data Element (SIMWLD)"}
{"Headers": "World for Simulation Eng Data Element (SIMWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nWorld Element (WORLD)\nEngineering Simulation Group Element (ESIMGR)\nSimulation Source Element (SIMSRC)\nSimulation Group Level Element (SIMGRP)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nEngineering Simulation Group Element (ESIMGR)\nSimulation Source Element (SIMSRC)\nSimulation Group Level Element (SIMGRP)\nName\nDescription\nWorld Element (WORLD)\nEngineering Simulation Group Element (ESIMGR)\nSimulation Source Element (SIMSRC)\nSimulation Group Level Element (SIMGRP)"}
{"Headers": "Engineering Stream List Element (SLTDEF)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nLstNam\nList name\nLstDsc\nList description\nLstDbv\nDatabase view associated with list\nLstDfs\nDefinition set name\nUuid\nUniversally unique identifier\nLstZf\nZoom factor\nLstUih\nShow units in headers\nLstVis\nVisible in list dropdown\nLstPin\nShow column pins in column headers\nLstMsf\nMulti-select filter style\nLstCfl\nColumn filtering\nName\nName of the element\nDescription\nDescription of the element\nLstNam\nList name\nLstDsc\nList description\nLstDbv\nDatabase view associated with list\nLstDfs\nDefinition set name\nUuid\nUniversally unique identifier\nLstZf\nZoom factor\nLstUih\nShow units in headers\nLstVis\nVisible in list dropdown\nLstPin\nShow column pins in column headers\nLstMsf\nMulti-select filter style\nLstCfl\nColumn filtering\nList Group Level Element (SLTGRP)\nStream Phase Element (SLTPHA)\nName\nName of the element\nDescription\nDescription of the element\nLstNam\nList name\nLstDsc\nList description\nLstDbv\nDatabase view associated with list\nLstDfs\nDefinition set name\nUuid\nUniversally unique identifier\nLstZf\nZoom factor\nLstUih\nShow units in headers\nLstVis\nVisible in list dropdown\nLstPin\nShow column pins in column headers\nLstMsf\nMulti-select filter style\nLstCfl\nColumn filtering\n\n\n\nList Group Level Element (SLTGRP)\nStream Phase Element (SLTPHA)\nName\nDescription\nLstNam\nLstDsc\nLstDbv\nLstDfs\nUuid\nLstZf\nLstUih\nLstVis\nLstPin\nLstMsf\nLstCfl\nList Group Level Element (SLTGRP)\nStream Phase Element (SLTPHA)"}
{"Headers": "List Group Level Element (SLTGRP) - Engineering", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nCatNam\nCategory name\nUuid\nUniversally unique identifier\nCatUsr\nCategory owner\nName\nName of the element\nDescription\nDescription of the element\nCatNam\nCategory name\nUuid\nUniversally unique identifier\nCatUsr\nCategory owner\nWorld for Engineering List Element (LSTWLD)\nEngineering Stream List Element (SLTDEF)\nName\nName of the element\nDescription\nDescription of the element\nCatNam\nCategory name\nUuid\nUniversally unique identifier\nCatUsr\nCategory owner\n\n\n\nWorld for Engineering List Element (LSTWLD)\nEngineering Stream List Element (SLTDEF)\nName\nDescription\nCatNam\nUuid\nCatUsr\nWorld for Engineering List Element (LSTWLD)\nEngineering Stream List Element (SLTDEF)"}
{"Headers": "Stream Phase Element (SLTPHA)", "Content": "Primary Element\nName\nName of the element\nPhtyp\nPhase type of the component\nName\nName of the element\nPhtyp\nPhase type of the component\nEngineering Stream List Element (SLTDEF)\nNone\nName\nName of the element\nPhtyp\nPhase type of the component\n\n\n\nEngineering Stream List Element (SLTDEF)\nName\nPhtyp\nEngineering Stream List Element (SLTDEF)"}
{"Headers": "Status Link World Element (STLNKW) - Engineering", "Content": "Administrative Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\nWorld Element (WORLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\n\n\n\nWorld Element (WORLD)\nName\nDescription\nStlPos\nWorld Element (WORLD)"}
{"Headers": "Engineering Typical Item Element (TYPITE)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nScsysf\nSystem reference array for schematic elements\nDispnm\nDisplay Name\nName\nName of the element\nDescription\nDescription of the element\nScsysf\nSystem reference array for schematic elements\nDispnm\nDisplay Name\nLibrary Engineering Item Element (LIBITE)\nEngineering Typical Item Element (TYPITE)\nEngineering Typical Item Element (TYPITE)\nName\nName of the element\nDescription\nDescription of the element\nScsysf\nSystem reference array for schematic elements\nDispnm\nDisplay Name\n\n\n\nLibrary Engineering Item Element (LIBITE)\nEngineering Typical Item Element (TYPITE)\nEngineering Typical Item Element (TYPITE)\nName\nDescription\nScsysf\nDispnm\nLibrary Engineering Item Element (LIBITE)\nEngineering Typical Item Element (TYPITE)\nEngineering Typical Item Element (TYPITE)"}
{"Headers": "World Element (WORLD) - Engineering", "Content": "Administrative Element\nPrimary Element\nName\nName of the element\nName\nName of the element\nNone\n\nEngineering Case World Element (ECASWL)\nEngineering Canvas Configuration World Element (ECCFWL)\n\nWorld for Engineering Canvas Data Element (ECWLD)\nEngineering Document Pack World Element (EDOCWL)\nWorld for Engineering Data Element (ENGWLD)\nEngineering 3D Model World Element (ETMWLD)\nWorld for Functional Eng Data Element (FUNWLD)\nWorld for Engineering List Element (LSTWLD)\nRevision Links World Element (REVLWL)\nWorld for Simulation Eng Data Element (SIMWLD)\nStatus Link World Element (STLNKW)\nDistributed Attributes World Element (XPIWLD)\nName\nName of the element\n\n\n\nEngineering Case World Element (ECASWL)\nEngineering Canvas Configuration World Element (ECCFWL)\nWorld for Engineering Canvas Data Element (ECWLD)\nEngineering Document Pack World Element (EDOCWL)\nWorld for Engineering Data Element (ENGWLD)\nEngineering 3D Model World Element (ETMWLD)\nWorld for Functional Eng Data Element (FUNWLD)\nWorld for Engineering List Element (LSTWLD)\nRevision Links World Element (REVLWL)\nWorld for Simulation Eng Data Element (SIMWLD)\nStatus Link World Element (STLNKW)\nDistributed Attributes World Element (XPIWLD)\nName\n\nEngineering Case World Element (ECASWL)\nEngineering Canvas Configuration World Element (ECCFWL)\n\nWorld for Engineering Canvas Data Element (ECWLD)\nEngineering Document Pack World Element (EDOCWL)\nWorld for Engineering Data Element (ENGWLD)\nEngineering 3D Model World Element (ETMWLD)\nWorld for Functional Eng Data Element (FUNWLD)\nWorld for Engineering List Element (LSTWLD)\nRevision Links World Element (REVLWL)\nWorld for Simulation Eng Data Element (SIMWLD)\nStatus Link World Element (STLNKW)\nDistributed Attributes World Element (XPIWLD)"}
{"Headers": "Distributed Attribute Group Element (XPIFLD) - Engineering", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nDistributed Attribute Group Element (XPIFLD)\nDistributed Attributes World Element (XPIWLD)\nDistributed Attribute Group Element (XPIFLD)\nDistributed Attribute Base Element Element (XPITEM)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nDistributed Attribute Group Element (XPIFLD)\nDistributed Attributes World Element (XPIWLD)\nDistributed Attribute Group Element (XPIFLD)\nDistributed Attribute Base Element Element (XPITEM)\nName\nDescription\nDistributed Attribute Group Element (XPIFLD)\nDistributed Attributes World Element (XPIWLD)\nDistributed Attribute Group Element (XPIFLD)\nDistributed Attribute Base Element Element (XPITEM)"}
{"Headers": "Distributed Attribute Base Element Element (XPITEM) - Global", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nXRPNTR\nDistributed Attribute reference\nName\nName of the element\nDescription\nDescription of the element\nXRPNTR\nDistributed Attribute reference\nDistributed Attribute Group Element (XPIFLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nXRPNTR\nDistributed Attribute reference\n\n\n\nDistributed Attribute Group Element (XPIFLD)\nName\nDescription\nXRPNTR\nDistributed Attribute Group Element (XPIFLD)"}
{"Headers": "Distributed Attributes World Element (XPIWLD) - Engineering", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nXRSTRT\nDistributed Attributes reference\nName\nName of the element\nDescription\nDescription of the element\nXRSTRT\nDistributed Attributes reference\nWorld Element (WORLD)\nDistributed Attribute Group Element (XPIFLD)\nName\nName of the element\nDescription\nDescription of the element\nXRSTRT\nDistributed Attributes reference\n\n\n\nWorld Element (WORLD)\nDistributed Attribute Group Element (XPIFLD)\nName\nDescription\nXRSTRT\nWorld Element (WORLD)\nDistributed Attribute Group Element (XPIFLD)"}
{"Headers": "CrossProduct Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the CrossProduct database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "CrossProduct Database Elements", "Content": "All data in the CrossProduct database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "ARCHIV Element (ARCHIV) - CrossProduct", "Content": "Structural Detailing Element\nName\nName of the element\nDescription\nDescription of the element\nUuid\nUniversally unique identifier\nName\nName of the element\nDescription\nDescription of the element\nUuid\nUniversally unique identifier\nCommenting Attachment Element (CMTATT)\nCommenting Capture Element (CMTCAP)\nCommenting Attachment Preview Element (CMTPRE)\nNone\nName\nName of the element\nDescription\nDescription of the element\nUuid\nUniversally unique identifier\n\n\n\nCommenting Attachment Element (CMTATT)\nCommenting Capture Element (CMTCAP)\nCommenting Attachment Preview Element (CMTPRE)\nName\nDescription\nUuid\nCommenting Attachment Element (CMTATT)\nCommenting Capture Element (CMTCAP)\nCommenting Attachment Preview Element (CMTPRE)"}
{"Headers": "Commenting Attachment Element (CMTATT) - CrossProdruct", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nCTHCTP\nCommenting content type\nCthAtp\nCommenting attachment purpose\nName\nName of the element\nDescription\nDescription of the element\nCTHCTP\nCommenting content type\nCthAtp\nCommenting attachment purpose\nCommenting Post Element (CMTPOS)\nARCHIV Element (ARCHIV)\nName\nName of the element\nDescription\nDescription of the element\nCTHCTP\nCommenting content type\nCthAtp\nCommenting attachment purpose\n\n\n\nCommenting Post Element (CMTPOS)\nARCHIV Element (ARCHIV)\nName\nDescription\nCTHCTP\nCthAtp\nCommenting Post Element (CMTPOS)\nARCHIV Element (ARCHIV)"}
{"Headers": "Commenting Capture Element (CMTCAP) - CrossProduct", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nCTHCTP\nCommenting content type\nCthAtp\nCommenting attachment purpose\nMvmdrf\nModel view definition reference\nName\nName of the element\nDescription\nDescription of the element\nCTHCTP\nCommenting content type\nCthAtp\nCommenting attachment purpose\nMvmdrf\nModel view definition reference\nCommenting Post Element (CMTPOS)\nARCHIV Element (ARCHIV)\nCommenting Attachment Preview Element (CMTPRE)\nName\nName of the element\nDescription\nDescription of the element\nCTHCTP\nCommenting content type\nCthAtp\nCommenting attachment purpose\nMvmdrf\nModel view definition reference\n\n\n\nCommenting Post Element (CMTPOS)\nARCHIV Element (ARCHIV)\nCommenting Attachment Preview Element (CMTPRE)\nName\nDescription\nCTHCTP\nCthAtp\nMvmdrf\nCommenting Post Element (CMTPOS)\nARCHIV Element (ARCHIV)\nCommenting Attachment Preview Element (CMTPRE)"}
{"Headers": "Commenting Folder Element (CMTFLD) - CrossProduct", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nCommenting Folder Element (CMTFLD)\nCommenting World Element (CMTWLD)\nCommenting Folder Element (CMTFLD)\nCommenting Thread Element (CMTTHR)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nCommenting World Element (CMTWLD)\nCommenting Thread Element (CMTTHR)\nName\nDescription\nCommenting World Element (CMTWLD)\nCommenting Thread Element (CMTTHR)"}
{"Headers": "Commenting Post Element (CMTPOS) - CrossProduct", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nCthText\nCommenting text\nStaUser\nStandard User\nStaDate\nStandard Date\nName\nName of the element\nDescription\nDescription of the element\nCthText\nCommenting text\nStaUser\nStandard User\nStaDate\nStandard Date\nCommenting Thread Element (CMTTHR)\nCommenting Attachment Element (CMTATT)\nCommenting Capture Element (CMTCAP)\nName\nName of the element\nDescription\nDescription of the element\nCthText\nCommenting text\nStaUser\nStandard User\nStaDate\nStandard Date\n\n\n\nCommenting Thread Element (CMTTHR)\nCommenting Attachment Element (CMTATT)\nCommenting Capture Element (CMTCAP)\nName\nDescription\nCthText\nStaUser\nStaDate\nCommenting Thread Element (CMTTHR)\nCommenting Attachment Element (CMTATT)\nCommenting Capture Element (CMTCAP)"}
{"Headers": "Commenting Attachment Preview Element (CMTPRE) - CrossProduct", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nCTHCTP\nCommenting content type\nCthAtp\nCommenting attachment purpose\nName\nName of the element\nDescription\nDescription of the element\nCTHCTP\nCommenting content type\nCthAtp\nCommenting attachment purpose\nCommenting Capture Element (CMTCAP)\nARCHIV Element (ARCHIV)\nName\nName of the element\nDescription\nDescription of the element\nCTHCTP\nCommenting content type\nCthAtp\nCommenting attachment purpose\n\n\n\nCommenting Capture Element (CMTCAP)\nARCHIV Element (ARCHIV)\nName\nDescription\nCTHCTP\nCthAtp\nCommenting Capture Element (CMTCAP)\nARCHIV Element (ARCHIV)"}
{"Headers": "Distributed Commenting Thread Element (CMTSTH)", "Content": "Primary Element\nName\nName of the element\nCthID\nThread Id\nName\nName of the element\nCthID\nThread Id\nCommenting Folder Element (CMTFLD)\nCommenting Post Element (CMTPOS)\nName\nName of the element\nCthID\nThread Id\n\n\n\nCommenting Post Element (CMTPOS)\nName\nCthID\nCommenting Folder Element (CMTFLD)\nCommenting Post Element (CMTPOS)"}
{"Headers": "Commenting Thread Element (CMTTHR) - CrossProduct", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nStaUser\nStandard User\nStaDate\nStandard Date\nCthAtp\nCommenting attachment purpose\nCthState\nCommenting thread state (Open/Close)\nName\nName of the element\nDescription\nDescription of the element\nStaUser\nStandard User\nStaDate\nStandard Date\nCthAtp\nCommenting attachment purpose\nCthState\nCommenting thread state (Open/Close)\nCommenting Folder Element (CMTFLD)\nCommenting Post Element (CMTPOS)\nName\nName of the element\nDescription\nDescription of the element\nStaUser\nStandard User\nStaDate\nStandard Date\nCthAtp\nCommenting attachment purpose\nCthState\nCommenting thread state (Open/Close)\n\n\n\nCommenting Post Element (CMTPOS)\nName\nDescription\nStaUser\nStaDate\nCthAtp\nCthState\nCommenting Folder Element (CMTFLD)\nCommenting Post Element (CMTPOS)"}
{"Headers": "Commenting World Element (CMTWLD) - CrossProduct", "Content": "Primary Element\nName\nName of the element\nXRSTRT\nDistributed Attributes reference\nDescription\nDescription of the element\nName\nName of the element\nXRSTRT\nDistributed Attributes reference\nDescription\nDescription of the element\nWorld Element (WORLD)\nCommenting Folder Element (CMTFLD)\nName\nName of the element\nXRSTRT\nDistributed Attributes reference\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nName\nXRSTRT\nDescription\nWorld Element (WORLD)\nCommenting Folder Element (CMTFLD)"}
{"Headers": "Link Document Element (LINKWLD) - CrossProduct", "Content": "Link Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nWorld Element (WORLD)\nLink Class Element (LNCLAS)\nLink Descriptor Element (LNDESC)\nLink Folder Element (LNFOLD)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nWorld Element (WORLD)\nLink Class Element (LNCLAS)\nLink Descriptor Element (LNDESC)\nLink Folder Element (LNFOLD)\nName\nDescription\nFunction\nWorld Element (WORLD)\nLink Class Element (LNCLAS)\nLink Descriptor Element (LNDESC)\nLink Folder Element (LNFOLD)"}
{"Headers": "Link Class Element (LNCLAS) - CrossProduct", "Content": "Link Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLink Folder Element (LNFOLD)\nLink Document Element (LINKWLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nLink Folder Element (LNFOLD)\nLink Document Element (LINKWLD)\nName\nDescription\nFunction\nLink Folder Element (LNFOLD)\nLink Document Element (LINKWLD)"}
{"Headers": "Link Descriptor Element (LNDESC) - CrossProduct", "Content": "Link Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLnkPrp\nTRUE if item pointed to by descriptor should be propagated by Global\nLnkUse\nLink Descriptor Usage\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLnkPrp\nTRUE if item pointed to by descriptor should be propagated by Global\nLnkUse\nLink Descriptor Usage\nLink Folder Element (LNFOLD)\nLink Document Element (LINKWLD)\nLink Link Element (LNLINK)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLnkPrp\nTRUE if item pointed to by descriptor should be propagated by Global\nLnkUse\nLink Descriptor Usage\n\n\n\nLink Folder Element (LNFOLD)\nLink Document Element (LINKWLD)\nLink Link Element (LNLINK)\nName\nDescription\nFunction\nLnkPrp\nLnkUse\nLink Folder Element (LNFOLD)\nLink Document Element (LINKWLD)\nLink Link Element (LNLINK)"}
{"Headers": "Link Folder Element (LNFOLD) - CrossProduct", "Content": "Link Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\nLink Folder Element (LNFOLD)\nLink Document Element (LINKWLD)\nLink Class Element (LNCLAS)\nLink Descriptor Element (LNDESC)\nLink Folder Element (LNFOLD)\nName\nName of the element\nDescription\nDescription of the element\nFunction\nFunction\n\n\n\nLink Folder Element (LNFOLD)\nLink Document Element (LINKWLD)\nLink Class Element (LNCLAS)\nLink Descriptor Element (LNDESC)\nLink Folder Element (LNFOLD)\nName\nDescription\nFunction\nLink Folder Element (LNFOLD)\nLink Document Element (LINKWLD)\nLink Class Element (LNCLAS)\nLink Descriptor Element (LNDESC)\nLink Folder Element (LNFOLD)"}
{"Headers": "Link Link Element (LNLINK) - CrossProduct", "Content": "Link Element\nPrimary Element\n\n\n\nLink Descriptor Element (LNDESC)\nNone\n\n\n\n\nLink Descriptor Element (LNDESC)\nLink Descriptor Element (LNDESC)"}
{"Headers": "Model View Clipbox Element (MVICBX)", "Content": "Mvvcls\nClip status\nMvvcas\nCap status\nMvvcco\nCap colour\nXlength\nX length\nYlength\nY length\nZlength\nLine length\nMvvcpo\nClipbox position\nMvvcor\nClipbox direction\nMvvcls\nClip status\nMvvcas\nCap status\nMvvcco\nCap colour\nXlength\nX length\nYlength\nY length\nZlength\nLine length\nMvvcpo\nClipbox position\nMvvcor\nClipbox direction\nModel Viewing Position Element (MVIPOS)\nModel View Clipplane Element (MVICPL)\nMvvcls\nClip status\nMvvcas\nCap status\nMvvcco\nCap colour\nXlength\nX length\nYlength\nY length\nZlength\nLine length\nMvvcpo\nClipbox position\nMvvcor\nClipbox direction\n\n\n\nModel Viewing Position Element (MVIPOS)\nModel View Clipplane Element (MVICPL)\nMvvcls\nMvvcas\nMvvcco\nXlength\nYlength\nZlength\nMvvcpo\nMvvcor\nModel Viewing Position Element (MVIPOS)\nModel View Clipplane Element (MVICPL)"}
{"Headers": "Model View Clipplane Element (MVICPL)", "Content": "Mvvcas\nCap status\nMvvcco\nCap colour\nMvvcas\nCap status\nMvvcco\nCap colour\nModel View Clipbox Element\nNone\nMvvcas\nCap status\nMvvcco\nCap colour\n\n\n\nModel View Clipbox Element\nMvvcas\nMvvcco\nModel View Clipbox Element"}
{"Headers": "Model Viewing Definition Element (MVIDEF)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nPurpose\nDescription code word\nName\nName of the element\nDescription\nDescription of the element\nPurpose\nDescription code word\nModel Viewing Information Elements Element (MVIFLD)\nModel Viewing Model Content Element (MVIMCT)\nModel Viewing Position Element (MVIPOS)\nName\nName of the element\nDescription\nDescription of the element\nPurpose\nDescription code word\n\n\n\nModel Viewing Information Elements Element (MVIFLD)\nModel Viewing Model Content Element (MVIMCT)\nModel Viewing Position Element (MVIPOS)\nName\nDescription\nPurpose\nModel Viewing Information Elements Element (MVIFLD)\nModel Viewing Model Content Element (MVIMCT)\nModel Viewing Position Element (MVIPOS)"}
{"Headers": "Model Viewing Drawlist Information Element (MVIDWL)", "Content": "Primary Element\nMvvdlr\nDrawlist references\nMvvdlv\nDrawlist visibility\nMvvdle\nDrawlist edges\nMvvdlc\nDrawlist color\nMvvdlt\nDrawlist translucency\nMvvdlr\nDrawlist references\nMvvdlv\nDrawlist visibility\nMvvdle\nDrawlist edges\nMvvdlc\nDrawlist color\nMvvdlt\nDrawlist translucency\nModel Viewing Drawlist Setting Information Element (MVIDWS)\nNone\nMvvdlr\nDrawlist references\nMvvdlv\nDrawlist visibility\nMvvdle\nDrawlist edges\nMvvdlc\nDrawlist color\nMvvdlt\nDrawlist translucency\n\n\n\nModel Viewing Drawlist Setting Information Element (MVIDWS)\nMvvdlr\nMvvdlv\nMvvdle\nMvvdlc\nMvvdlt\nModel Viewing Drawlist Setting Information Element (MVIDWS)"}
{"Headers": "Model Viewing Drawlist Setting Information Element (MVIDWS)", "Content": "Primary Element\nMvvdsi\nDrawlist integer settings\nMvvdsr\nDrawlist real settings\nMvvdsi\nDrawlist integer settings\nMvvdsr\nDrawlist real settings\nModel Viewing Model Content Element (MVIMCT)\nModel Viewing Drawlist Information Element (MVIDWL)\nMvvdsi\nDrawlist integer settings\nMvvdsr\nDrawlist real settings\n\n\n\nModel Viewing Model Content Element (MVIMCT)\nModel Viewing Drawlist Information Element (MVIDWL)\nMvvdsi\nMvvdsr\nModel Viewing Model Content Element (MVIMCT)\nModel Viewing Drawlist Information Element (MVIDWL)"}
{"Headers": "Model Viewing Information Elements Element (MVIFLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nModel Viewing Information Elements Element (MVIFLD)\nModel Viewing Info World Element (MVIWLD)\nModel Viewing Definition Element (MVIDEF)\nModel Viewing Information Elements Element (MVIFLD)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nModel Viewing Information Elements Element (MVIFLD)\nModel Viewing Info World Element (MVIWLD)\nModel Viewing Definition Element (MVIDEF)\nModel Viewing Information Elements Element (MVIFLD)\nName\nDescription\nModel Viewing Information Elements Element (MVIFLD)\nModel Viewing Info World Element (MVIWLD)\nModel Viewing Definition Element (MVIDEF)\nModel Viewing Information Elements Element (MVIFLD)"}
{"Headers": "Model Viewing Model Content Element (MVIMCT)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nName\nName of the element\nDescription\nDescription of the element\nModel Viewing Definition Element (MVIDEF)\nModel Viewing Model Selection Element (MVISEL)\nModel Viewing Drawlist Setting Information Element (MVIDWS)\nName\nName of the element\nDescription\nDescription of the element\n\n\n\nModel Viewing Definition Element (MVIDEF)\nModel Viewing Model Selection Element (MVISEL)\nModel Viewing Drawlist Setting Information Element (MVIDWS)\nName\nDescription\nModel Viewing Definition Element (MVIDEF)\nModel Viewing Model Selection Element (MVISEL)\nModel Viewing Drawlist Setting Information Element (MVIDWS)"}
{"Headers": "Model Viewing Position Element (MVIPOS)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nPurpose\nDescription code word\nMvvctr\nViewing centre\nMvvdir\nViewing direction\nMvvdto\nDistance to observer\nMvvrad\nViewing radius\nMvvang\nViewing angle\nMvvctp\nCamera type\nMvvelv\nViewing elevation\nMvvbea\nViewing bearing\nMvvlim\nView limits\nMvvcls\nClip status\nMvvcao\nClip plane all off status\nName\nName of the element\nDescription\nDescription of the element\nPurpose\nDescription code word\nMvvctr\nViewing centre\nMvvdir\nViewing direction\nMvvdto\nDistance to observer\nMvvrad\nViewing radius\nMvvang\nViewing angle\nMvvctp\nCamera type\nMvvelv\nViewing elevation\nMvvbea\nViewing bearing\nMvvlim\nView limits\nMvvcls\nClip status\nMvvcao\nClip plane all off status\nModel Viewing Definition Element (MVIDEF)\nModel View Clipbox Element (MVICBX)\nName\nName of the element\nDescription\nDescription of the element\nPurpose\nDescription code word\nMvvctr\nViewing centre\nMvvdir\nViewing direction\nMvvdto\nDistance to observer\nMvvrad\nViewing radius\nMvvang\nViewing angle\nMvvctp\nCamera type\nMvvelv\nViewing elevation\nMvvbea\nViewing bearing\nMvvlim\nView limits\nMvvcls\nClip status\nMvvcao\nClip plane all off status\n\n\n\nModel Viewing Definition Element (MVIDEF)\nModel View Clipbox Element (MVICBX)\nName\nDescription\nPurpose\nMvvctr\nMvvdir\nMvvdto\nMvvrad\nMvvang\nMvvctp\nMvvelv\nMvvbea\nMvvlim\nMvvcls\nMvvcao\nModel Viewing Definition Element (MVIDEF)\nModel View Clipbox Element (MVICBX)"}
{"Headers": "Model Viewing Model Selection Element (MVISEL)", "Content": "Primary Element\nMvcexp\nModel View content expression\nMvcexp\nModel View content expression\nModel Viewing Model Content Element (MVIMCT)\nNone\nMvcexp\nModel View content expression\n\n\n\nModel Viewing Model Content Element (MVIMCT)\nMvcexp\nModel Viewing Model Content Element (MVIMCT)"}
{"Headers": "Model Viewing Info World Element (MVIWLD)", "Content": "Primary Element\nName\nName of the element\nDescription\nDescription of the element\nXRSTRT\nDistributed Attributes reference\nName\nName of the element\nDescription\nDescription of the element\nXRSTRT\nDistributed Attributes reference\nWorld Element (WORLD)\nModel Viewing Information Elements Element (MVIFLD)\nName\nName of the element\nDescription\nDescription of the element\nXRSTRT\nDistributed Attributes reference\n\n\n\nWorld Element (WORLD)\nModel Viewing Information Elements Element (MVIFLD)\nName\nDescription\nXRSTRT\nWorld Element (WORLD)\nModel Viewing Information Elements Element (MVIFLD)"}
{"Headers": "World Element (WORLD) - CrossProduct", "Content": "Administrative Element\nPrimary Element\nName\nName of the element\nName\nName of the element\nNone\nCommenting World Element (CMTWLD)\nLink Document Element (LINKWLD)\nModel Viewing Info World Element (MVIWLD)\nName\nName of the element\n\n\n\nCommenting World Element (CMTWLD)\nLink Document Element (LINKWLD)\nModel Viewing Info World Element (MVIWLD)\nName\nCommenting World Element (CMTWLD)\nLink Document Element (LINKWLD)\nModel Viewing Info World Element (MVIWLD)"}
{"Headers": "ConceptualModel Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the ConceptualModel database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "ConceptualModel Database Elements", "Content": "All data in the ConceptualModel database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "An RDF DataSet, used to store RDF Graphs Element (RDFDATASET)", "Content": "Primary Element\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\nTop Level RDF World, used to store RDF DataSets Element (RDFWLD)\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\n\n\n\nTop Level RDF World, used to store RDF DataSets Element (RDFWLD)\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)\nName\nRDFIRI\nTop Level RDF World, used to store RDF DataSets Element (RDFWLD)\nLegal Members\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)"}
{"Headers": "An RDF Graph, used to store RDF Resources Element (RDFGRAPH)", "Content": "Primary Element\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\nAn RDF DataSet, used to store RDF Graphs Element (RDFDATASET)\nAn RDF Namespace Definition; used to store a Namespace and its Prefix Element (RDFNSDEFINITION)\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Resource Elements Element (RESGROUP)\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\n\n\n\nAn RDF DataSet, used to store RDF Graphs Element (RDFDATASET)\nAn RDF Namespace Definition; used to store a Namespace and its Prefix Element (RDFNSDEFINITION)\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Resource Elements Element (RESGROUP)\nName\nRDFIRI\nAn RDF DataSet, used to store RDF Graphs Element (RDFDATASET)\nAn RDF Namespace Definition; used to store a Namespace and its Prefix Element (RDFNSDEFINITION)\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Resource Elements Element (RESGROUP)"}
{"Headers": "An RDF Namespace Definition; used to store a Namespace and its Prefix Element (RDFNSDEFINITION)", "Content": "Primary Element\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\nRDFPRE\nA prefix (short-hand) for an RDF namespace\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\nRDFPRE\nA prefix (short-hand) for an RDF namespace\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)\nNone\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\nRDFPRE\nA prefix (short-hand) for an RDF namespace\n\n\n\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)\nName\nRDFIRI\nRDFPRE\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)\nLegal Members"}
{"Headers": "An RDF Resource Element (RDFRESOURCE)", "Content": "Primary Element\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)\nGroup Element for RDF Resource Elements Element (RESGROUP)\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with a Boolean Object Element (STBOOLEAN)\nAn RDF Statement with a Double Object Element (STDOUBLE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with an Integer Object Element (STINTEGER)\nAn RDF Statement with a Language Qualified String Object Element (STLSTRING)\nAn RDF Statement with a Reference Object Element (STREFERENCE)\nAn RDF Statement with a String Object Element (STSTRING)\nName\nName of the element\nRDFIRI\nInternational Resource Identifier used to identify an RDF Resource\n\n\n\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)\nGroup Element for RDF Resource Elements Element (RESGROUP)\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with a Boolean Object Element (STBOOLEAN)\nAn RDF Statement with a Double Object Element (STDOUBLE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with an Integer Object Element (STINTEGER)\nAn RDF Statement with a Language Qualified String Object Element (STLSTRING)\nAn RDF Statement with a Reference Object Element (STREFERENCE)\nAn RDF Statement with a String Object Element (STSTRING)\nName\nRDFIRI\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)\nGroup Element for RDF Resource Elements Element (RESGROUP)\nLegal Members\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with a Boolean Object Element (STBOOLEAN)\nAn RDF Statement with a Double Object Element (STDOUBLE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with an Integer Object Element (STINTEGER)\nAn RDF Statement with a Language Qualified String Object Element (STLSTRING)\nAn RDF Statement with a Reference Object Element (STREFERENCE)\nAn RDF Statement with a String Object Element (STSTRING)"}
{"Headers": "Top Level RDF World, used to store RDF DataSets Element (RDFWLD)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nWorld Element (WORLD)\nAn RDF DataSet, used to store RDF Graphs Element (RDFDATASET)\nName\nName of the element\n\n\n\nWorld Element (WORLD)\nAn RDF DataSet, used to store RDF Graphs Element (RDFDATASET)\nName\nWorld Element (WORLD)\nAn RDF DataSet, used to store RDF Graphs Element (RDFDATASET)"}
{"Headers": "Group Element for RDF Resource Elements Element (RESGROUP)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)\nGroup Element for RDF Resource Elements Element (RESGROUP)\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Resource Elements Element (RESGROUP)\nName\nName of the element\n\n\n\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)\nGroup Element for RDF Resource Elements Element (RESGROUP)\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Resource Elements Element (RESGROUP)\nName\nAn RDF Graph, used to store RDF Resources Element (RDFGRAPH)\nGroup Element for RDF Resource Elements Element (RESGROUP)\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Resource Elements Element (RESGROUP)"}
{"Headers": "An RDF Statement with an Object which is not of an Inbuilt Type Element (STBASE)", "Content": "Primary Element\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nRDFOBJ\nAn RDF statement object string\nTYPREF\nReference to a datatype element for an RDF Statement Object\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nRDFOBJ\nAn RDF statement object string\nTYPREF\nReference to a datatype element for an RDF Statement Object\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nNone\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nRDFOBJ\nAn RDF statement object string\nTYPREF\nReference to a datatype element for an RDF Statement Object\n\n\n\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nName\nPRDREF\nRDFOBJ\nTYPREF\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nLegal Members"}
{"Headers": "An RDF Statement with a Boolean Object Element (STBOOLEAN)", "Content": "Primary Element\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJBOOLEAN\nAn RDF Statement Object representing a boolean\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJBOOLEAN\nAn RDF Statement Object representing a boolean\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nNone\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJBOOLEAN\nAn RDF Statement Object representing a boolean\n\n\n\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nName\nPRDREF\nOBJBOOLEAN\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nLegal Members"}
{"Headers": "An RDF Statement with a Double Object Element (STDOUBLE)", "Content": "Primary Element\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJDOUBLE\nAn RDF Statement Object representing a double\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJDOUBLE\nAn RDF Statement Object representing a double\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nNone\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJDOUBLE\nAn RDF Statement Object representing a double\n\n\n\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nName\nPRDREF\nOBJDOUBLE\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nLegal Members"}
{"Headers": "Group Element for RDF Statement Elements Element (STGROUP)", "Content": "Primary Element\nName\nName of the element\nName\nName of the element\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with an Object which is not of an Inbuilt Type Element (STBASE)\nAn RDF Statement with a Boolean Object Element (STBOOLEAN)\nAn RDF Statement with a Double Object Element (STDOUBLE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with an Integer Object Element (STINTEGER)\nAn RDF Statement with a Language Qualified String Object Element (STLSTRING)\nAn RDF Statement with a Reference Object Element (STREFERENCE)\nAn RDF Statement with a String Object Element (STSTRING)\nName\nName of the element\n\n\n\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with an Object which is not of an Inbuilt Type Element (STBASE)\nAn RDF Statement with a Boolean Object Element (STBOOLEAN)\nAn RDF Statement with a Double Object Element (STDOUBLE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with an Integer Object Element (STINTEGER)\nAn RDF Statement with a Language Qualified String Object Element (STLSTRING)\nAn RDF Statement with a Reference Object Element (STREFERENCE)\nAn RDF Statement with a String Object Element (STSTRING)\nName\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with an Object which is not of an Inbuilt Type Element (STBASE)\nAn RDF Statement with a Boolean Object Element (STBOOLEAN)\nAn RDF Statement with a Double Object Element (STDOUBLE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nAn RDF Statement with an Integer Object Element (STINTEGER)\nAn RDF Statement with a Language Qualified String Object Element (STLSTRING)\nAn RDF Statement with a Reference Object Element (STREFERENCE)\nAn RDF Statement with a String Object Element (STSTRING)"}
{"Headers": "An RDF Statement with an Integer Object Element (STINTEGER)", "Content": "Primary Element\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJINTEGER\nAn RDF Statement Object representing an integer\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJINTEGER\nAn RDF Statement Object representing an integer\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nNone\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJINTEGER\nAn RDF Statement Object representing an integer\n\n\n\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nName\nPRDREF\nOBJINTEGER\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nLegal Members"}
{"Headers": "An RDF Statement with a Language Qualified String Object Element (STLSTRING)", "Content": "Primary Element\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nRDFOBJ\nAn RDF statement object string\nLANG\nLanguage tag as described in BCP 47 - Tags for Identifying Languages(http://tools.ietf.org/html/bcp47)\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nRDFOBJ\nAn RDF statement object string\nLANG\nLanguage tag as described in BCP 47 - Tags for Identifying Languages(http://tools.ietf.org/html/bcp47)\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nNone\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nRDFOBJ\nAn RDF statement object string\nLANG\nLanguage tag as described in BCP 47 - Tags for Identifying Languages(http://tools.ietf.org/html/bcp47)\n\n\n\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nName\nPRDREF\nRDFOBJ\nLANG\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nLegal Members"}
{"Headers": "An RDF Statement with a Reference Object Element (STREFERENCE)", "Content": "Primary Element\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJREF\nReference to an RDF Statement Object element\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJREF\nReference to an RDF Statement Object element\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nNone\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nOBJREF\nReference to an RDF Statement Object element\n\n\n\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nName\nPRDREF\nOBJREF\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nLegal Members"}
{"Headers": "An RDF Statement with a String Object Element (STSTRING)", "Content": "Primary Element\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nRDFOBJ\nAn RDF statement object string\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nRDFOBJ\nAn RDF statement object string\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nNone\nName\nName of the element\nPRDREF\nReference to an RDF Statement Predicate element\nRDFOBJ\nAn RDF statement object string\n\n\n\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nName\nPRDREF\nRDFOBJ\nAn RDF Resource Element (RDFRESOURCE)\nGroup Element for RDF Statement Elements Element (STGROUP)\nLegal Members"}
{"Headers": "World Element (WORLD) - ConceptualModel", "Content": "Administrative Element\nPrimary Element\nName\nName of the element\nName\nName of the element\nNone\nTop Level RDF World, used to store RDF DataSets Element (RDFWLD)\nName\nName of the element\n\n\n\nTop Level RDF World, used to store RDF DataSets Element (RDFWLD)\nName\nTop Level RDF World, used to store RDF DataSets Element (RDFWLD)"}
{"Headers": "Task Database", "Content": "The Data Model Reference manual contains details of all the elements which can be created in the Task database, their position in the database hierarchy and their attributes.\n\n\n"}
{"Headers": "Task Database Elements", "Content": "All data in the Task database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Status Link World Element (STLNKW) - Task", "Content": "Administrative Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\nWorld Element (WORLD)\nNone\nName\nName of the element\nDescription\nDescription of the element\nStlPos\nStatus Element reference\n\n\n\nWorld Element (WORLD)\nName\nDescription\nStlPos\nWorld Element (WORLD)"}
{"Headers": "Task Flow Chart Connection Element (TAFCCO)", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nTskfce\nReference to the flow chart element\nTaActive\nTask Active\nTaCoRo\nTask Connection Route\nName\nName of the element\nDescription\nDescription of the element\nTskfce\nReference to the flow chart element\nTaActive\nTask Active\nTaCoRo\nTask Connection Route\nTask Flow Chart Element Element (TAFCEL)\nNone\nName\nName of the element\nDescription\nDescription of the element\nTskfce\nReference to the flow chart element\nTaActive\nTask Active\nTaCoRo\nTask Connection Route\n\n\n\nTask Flow Chart Element Element (TAFCEL)\nName\nDescription\nTskfce\nTaActive\nTaCoRo\nTask Flow Chart Element Element (TAFCEL)"}
{"Headers": "Task Flow Chart Element Element (TAFCEL)", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTaskType\nTask Type\nTskdef\nReference to the task definition\nTaPos\nTask Position\nTaWidth\nTask Width\nTaHeight\nTask Height\nTaCol\nTask Colour\nTaTCol\nTask Text Colour\nTaFont\nTask Font\nTaActive\nTask Active\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTaskType\nTask Type\nTskdef\nReference to the task definition\nTaPos\nTask Position\nTaWidth\nTask Width\nTaHeight\nTask Height\nTaCol\nTask Colour\nTaTCol\nTask Text Colour\nTaFont\nTask Font\nTaActive\nTask Active\nTask Flow Chart Element (TAFLCH)\nTask Flow Chart Connection Element (TAFCCO)\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTaskType\nTask Type\nTskdef\nReference to the task definition\nTaPos\nTask Position\nTaWidth\nTask Width\nTaHeight\nTask Height\nTaCol\nTask Colour\nTaTCol\nTask Text Colour\nTaFont\nTask Font\nTaActive\nTask Active\n\n\n\nTask Flow Chart Element (TAFLCH)\nTask Flow Chart Connection Element (TAFCCO)\nName\nTaname\nDescription\nTaskType\nTskdef\nTaPos\nTaWidth\nTaHeight\nTaCol\nTaTCol\nTaFont\nTaActive\nTask Flow Chart Element (TAFLCH)\nTask Flow Chart Connection Element (TAFCCO)"}
{"Headers": "Task Flow Chart Element (TAFLCH)", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTaActive\nTask Active\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTaActive\nTask Active\nWorld Element (WORLD)\nTask Flow Chart Element Element (TAFCEL)\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTaActive\nTask Active\n\n\n\nWorld Element (WORLD)\nTask Flow Chart Element Element (TAFCEL)\nName\nTaname\nDescription\nTaActive\nWorld Element (WORLD)\nTask Flow Chart Element Element (TAFCEL)"}
{"Headers": "Task Definition Element (TASDEF)", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTaskId\nTask ID\nTaskType\nTask Type\nTaLoSe\nTask Logic Selection\nTaActive\nTask Active\nTATYTR\nTask Treated Type\nTaTyIn\nTask Input Type\nTaTyOu\nTask Output Type\nTaFilter\nTask Filter\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTaskId\nTask ID\nTaskType\nTask Type\nTaLoSe\nTask Logic Selection\nTaActive\nTask Active\nTATYTR\nTask Treated Type\nTaTyIn\nTask Input Type\nTaTyOu\nTask Output Type\nTaFilter\nTask Filter\nWorld Element (WORLD)\nNone\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTaskId\nTask ID\nTaskType\nTask Type\nTaLoSe\nTask Logic Selection\nTaActive\nTask Active\nTATYTR\nTask Treated Type\nTaTyIn\nTask Input Type\nTaTyOu\nTask Output Type\nTaFilter\nTask Filter\n\n\n\nWorld Element (WORLD)\nName\nTaname\nDescription\nTaskId\nTaskType\nTaLoSe\nTaActive\nTATYTR\nTaTyIn\nTaTyOu\nTaFilter\nWorld Element (WORLD)"}
{"Headers": "Task Namespace Element (TNASPE) - Task", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nWorld Element (WORLD)\nTask Group Element (TTSKGP)\nWorkflow Group Element (TWFLGP)\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\n\n\n\nWorld Element (WORLD)\nTask Group Element (TTSKGP)\nWorkflow Group Element (TWFLGP)\nName\nTaname\nDescription\nWorld Element (WORLD)\nTask Group Element (TTSKGP)\nWorkflow Group Element (TWFLGP)"}
{"Headers": "Task Element Element (TTSKEL) - Task", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTskdef\nReference to the task definition\nWflelm\nReference to Workflow Element\nTsknam\nTask Definiton Name\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTskdef\nReference to the task definition\nWflelm\nReference to Workflow Element\nTsknam\nTask Definiton Name\nTask Group Element (TTSKGP)\nNone\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTskdef\nReference to the task definition\nWflelm\nReference to Workflow Element\nTsknam\nTask Definiton Name\n\n\n\nTask Group Element (TTSKGP)\nName\nTaname\nDescription\nTskdef\nWflelm\nTsknam\nTask Group Element (TTSKGP)"}
{"Headers": "Task Group Element (TTSKGP) - Task", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTask Namespace Element (TNASPE)\nTask Element Element (TTSKEL)\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\n\n\n\nTask Namespace Element (TNASPE)\nTask Element Element (TTSKEL)\nName\nTaname\nDescription\nTask Namespace Element (TNASPE)\nTask Element Element (TTSKEL)"}
{"Headers": "Workflow Element Element (TWFLEL) - Task", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nOrgelm\nReference to Original Element\nTskref\nAssigned tasks list\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nOrgelm\nReference to Original Element\nTskref\nAssigned tasks list\nWorkflow Group Element (TWFLGP)\nNone\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nOrgelm\nReference to Original Element\nTskref\nAssigned tasks list\n\n\n\nWorkflow Group Element (TWFLGP)\nName\nTaname\nDescription\nOrgelm\nTskref\nWorkflow Group Element (TWFLGP)"}
{"Headers": "Workflow Group Element (TWFLGP) - Task", "Content": "Steel Fabricator Task Element\nPrimary Element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\nTask Namespace Element (TNASPE)\nWorkflow Element Element (TWFLEL)\nName\nName of the element\nTaname\nTask Item Name\nDescription\nDescription of the element\n\n\n\nTask Namespace Element (TNASPE)\nWorkflow Element Element (TWFLEL)\nName\nTaname\nDescription\nTask Namespace Element (TNASPE)\nWorkflow Element Element (TWFLEL)"}
{"Headers": "World Element (WORLD) - Task", "Content": "Administrative Element\nPrimary Element\nName\nName of the element\nName\nName of the element\nNone\nStatus Link World Element (STLNKW)\nTask Flow Chart Element (TAFLCH)\nTask Definition Element (TASDEF)\nTask Namespace Element (TNASPE)\nName\nName of the element\n\n\n\nStatus Link World Element (STLNKW)\nTask Flow Chart Element (TAFLCH)\nTask Definition Element (TASDEF)\nTask Namespace Element (TNASPE)\nName\nStatus Link World Element (STLNKW)\nTask Flow Chart Element (TAFLCH)\nTask Definition Element (TASDEF)\nTask Namespace Element (TNASPE)"}
{"Headers": "Analysis Database Elements", "Content": "All data in the Analysis database is stored in elements in a strict hierarchy. Every element has a type and each type determines the attributes available on the element. Refer to Database Navigation and Query Syntax for further information on database concepts.\n\n\n\nDatabase Navigation and Query Syntax"}
{"Headers": "Generic Grouping Package Element (GENPKG)", "Content": "Functional Model Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nGPKGRF\nGeneric Package Reference\nName\nName of the element\nDescription\nDescription of the element\nGPKGRF\nGeneric Package Reference\nWorld Element (WORLD)\nGeneric Package Folder Element (GPKGFL)\nGeneric Package Filter Element (GPKGFT)\nName\nName of the element\nDescription\nDescription of the element\nGPKGRF\nGeneric Package Reference\n\n\n\nWorld Element (WORLD)\nGeneric Package Folder Element (GPKGFL)\nGeneric Package Filter Element (GPKGFT)\nName\nDescription\nGPKGRF\nWorld Element (WORLD)\nGeneric Package Folder Element (GPKGFL)\nGeneric Package Filter Element (GPKGFT)"}
{"Headers": "Generic Package Folder Element (GPKGFL)", "Content": "Functional Model Element\nPrimary Element\nName\nName of the element\nDescription\nDescription of the element\nGPkgFilter\nGeneric Package Filter Expression\nName\nName of the element\nDescription\nDescription of the element\nGPkgFilter\nGeneric Package Filter Expression\nGeneric Grouping Package Element (GENPKG)\nNone\nName\nName of the element\nDescription\nDescription of the element\nGPkgFilter\nGeneric Package Filter Expression\n\n\n\nGeneric Grouping Package Element (GENPKG)\nName\nDescription\nGPkgFilter\nGeneric Grouping Package Element (GENPKG)"}
{"Headers": "Generic Package Filter Element (GPKGFT)", "Content": "Functional Model Element\nName\nName of the element\nDescription\nDescription of the element\nGPkgFilter\nGeneric Package Filter Expression\nName\nName of the element\nDescription\nDescription of the element\nGPkgFilter\nGeneric Package Filter Expression\nGeneric Grouping Package Element (GENPKG)\nNone\nName\nName of the element\nDescription\nDescription of the element\nGPkgFilter\nGeneric Package Filter Expression\n\n\n\nGeneric Grouping Package Element (GENPKG)\nName\nDescription\nGPkgFilter\nGeneric Grouping Package Element (GENPKG)"}
{"Headers": "World Element (WORLD) - Analysis", "Content": "Administrative Element\nPrimary Element\nName\nName of the element\nName\nName of the element\nNone\nGeneric Grouping Package Element (GENPKG)\nName\nName of the element\n\n\n\nGeneric Grouping Package Element (GENPKG)\nName\nGeneric Grouping Package Element (GENPKG)"}
{"Headers": "Status Control", "Content": "Status Control is the ability to control and report on the status of individual model objects as they progress through their life cycles. It can be applied to any model objects, for example tagged items, catalog components, drawings, and so on. It can be expressed in a variety of ways, for example Approved for Construction, 80% Complete, Clash Free, and so on.\nThe desired project configuration is created by administrators as Status Definitions in Lexicon. It is applied to model objects by End-Users in any of the constructor modules - AVEVA E3D Design Model, Design, Outfitting, Paragon, AVEVA Spooler, AVEVA Diagrams, AVEVA Hull Design, Draft and Marine Drafting - using the Status Controller.\nStatus Control can be tightly coupled with Data Access Control (DAC). For example, it can be configured so that only certain Users may approve an object. It can also be configured to prevent changes to an object once it has achieved a particular status.\nA core concept for Status Control is that of a Controlled Object. A Controlled Object is defined as any model object that has one or more Status Values assigned to it. A Controlled Object may be controlled for multiple statuses to suit processes for design, manufacturing, fabrication, construction, and so on.\n\n\n"}
{"Headers": "Assumptions", "Content": "End-Users have a basic knowledge of AVEVA E3D Design/AVEVA Marine.\nAdministrators have a reasonable knowledge of Lexicon, and if required, can use the Access Control Assistant in Admin.\nDevelopers have a reasonable knowledge of PML and/or C# (.NET).\nEnd-Users have a basic knowledge of AVEVA E3D Design/AVEVA Marine.\nEnd-Users have a basic knowledge of AVEVA E3D Design/AVEVA Marine.\nAdministrators have a reasonable knowledge of Lexicon, and if required, can use the Access Control Assistant in Admin.\nAdministrators have a reasonable knowledge of Lexicon, and if required, can use the Access Control Assistant in Admin.\nDevelopers have a reasonable knowledge of PML and/or C# (.NET).\nDevelopers have a reasonable knowledge of PML and/or C# (.NET).\n\n\n"}
{"Headers": "Quick Access Tool bars", "Content": "Options are displayed on the Quick Access Tool bars of the Status Controller window for quick and convenient access.\nStatus Layout\nUse the Status Layout tool bar to create a status layout, selecting a existing status layouts and save status layouts.\n\nStatus Layout drop-down list\nAllows the User to select an existing status layout or create a new one.\nSet Layout Scope\nDisplays the Set Layout Scope window, to define the scope selection.\nSave Status Layout\nSaves the current Status Layout to the default location.\nStatus Layout drop-down list\nAllows the User to select an existing status layout or create a new one.\nSet Layout Scope\nDisplays the Set Layout Scope window, to define the scope selection.\nSave Status Layout\nSaves the current Status Layout to the default location.\nFocus Status\nUse the Focus Status tool bar to promote/demote, edit, delete status values, view history and run reports.\n\nPromote\nPromote the currently selected (CE) to the next status value.\nDemote\nDemotes the CE to the previous status value.\nEdit Status\nDisplays the Edit Status window, allows the status value to be promoted or demoted.\nDelete\nDeletes the CE model object.\nStatus History\nDisplay the Status History window, populated with the session history for the CE.\nStatistical Report\nDisplay the Statistical Report window, populated with the data and charts for the focus status of the CE.\nSelect CE in grid\nFrom the Model Explorer, highlights the CE in the grid.\nSelect CE Members in grid\nFrom the Model Explorer, highlights the members of the CE in the grid.\nSelect Graphical Selection in grid\nFrom the Graphical Selection, highlights the CE in the grid.\nPromote\nPromote the currently selected (CE) to the next status value.\nDemote\nDemotes the CE to the previous status value.\nEdit Status\nDisplays the Edit Status window, allows the status value to be promoted or demoted.\nDelete\nDeletes the CE model object.\nStatus History\nDisplay the Status History window, populated with the session history for the CE.\nStatistical Report\nDisplay the Statistical Report window, populated with the data and charts for the focus status of the CE.\nSelect CE in grid\nFrom the Model Explorer, highlights the CE in the grid.\nSelect CE Members in grid\nFrom the Model Explorer, highlights the members of the CE in the grid.\nSelect Graphical Selection in grid\nFrom the Graphical Selection, highlights the CE in the grid.\n\nStatus Layout drop-down list\nAllows the User to select an existing status layout or create a new one.\nSet Layout Scope\nDisplays the Set Layout Scope window, to define the scope selection.\nSave Status Layout\nSaves the current Status Layout to the default location.\nPromote\nPromote the currently selected (CE) to the next status value.\nDemote\nDemotes the CE to the previous status value.\nEdit Status\nDisplays the Edit Status window, allows the status value to be promoted or demoted.\nDelete\nDeletes the CE model object.\nStatus History\nDisplay the Status History window, populated with the session history for the CE.\nStatistical Report\nDisplay the Statistical Report window, populated with the data and charts for the focus status of the CE.\nSelect CE in grid\nFrom the Model Explorer, highlights the CE in the grid.\nSelect CE Members in grid\nFrom the Model Explorer, highlights the members of the CE in the grid.\nSelect Graphical Selection in grid\nFrom the Graphical Selection, highlights the CE in the grid.\nStatus Layout\nFocus Status\nStatus Layout\nStatus Layout\nFocus Status\nFocus Status\n\n\n\nStatus Controller\nStatus Layout\nStatus Layout\nStatus Layout drop-down list\nSet Layout Scope\nSave Status Layout\nFocus Status\nFocus Status\nPromote\nDemote\nEdit Status\nEdit Status\nDelete\nStatus History\nStatus History\nStatistical Report\nStatistical Report\nSelect CE in grid\nModel Explorer\nSelect CE Members in grid\nModel Explorer\nSelect Graphical Selection in grid\nGraphical Selection"}
{"Headers": "Example Workflow", "Content": "Consider the following simple workflow for a Design Status Definition which will be used as a worked example.\n\nThis example has a primary route from starting work through to releasing, with stages for checking and approving, and options at various stages to put back for rework.\n\n\n"}
{"Headers": "Status Control Data Model", "Content": "The Status Control data model defines an Example Workflow as a Status Definition (STADEF) object owning a set of Status Value (STAVAL) objects. Individual model objects reference the Status Values via Status Link (STALNK) objects, as illustrated below.\n\nStatus Link objects reside in the same Database (DB) as the model objects they reference, so that they are globally distributed with those model objects. The Status Link holds references to the model object and to the Status Value, along with attribute data for comments and history. So status data is not stored directly on the model object and the User does not need Write access to the model object in order to set its status.\nThe Status Link objects are not visible to the End-User, but the status data is available on the model object as pseudo-attributes. Administrators need to know of their existence for purposes of Data Access Control (DAC).\n\n\n\nExample Workflow\nExample Workflow"}
{"Headers": "Configuring Status Definitions in Lexicon", "Content": "Lexicon uses a hierarchy of Status Configuration World, Status Definition Group, Status Definition, and Status Value data types to define an Example Workflow.\n\n\n\nExample Workflow\nExample Workflow"}
{"Headers": "Create a Status Configuration World", "Content": "In the Lexicon Dictionary Explorer, right-click on the Dictionary World and select STAWLD: Status Configuration world, then enter a name in the Current Element Editor.\n\n\n\n\nDictionary Explorer\nSTAWLD: Status Configuration world\nCurrent Element Editor"}
{"Headers": "Create a Status Definition", "Content": "Right-click on the new STAWLD element in the Dictionary Explorer and select STADEF: Status Definition. The User can also create Status Definition Groups to contain Status Definitions). Enter a Name and Description in the Current Element Editor.\n\nIn the Current Element Editor, the User can define the Initial status for the selected Status Definition.\n\nFrom the displayed drop-list in the Initial status field, select the initial status value for the Status Definition.\nIn the Current Element Editor, the User can define the Controllable element type for the selected Status Definition.\n\nIn the Controllable element type field, click the selection button. The Select element types window is displayed.\n\nFrom the Available element types part of the Select element types window, select an element type, then click Add to list, and then OK. Other types can be applied if the definition is to apply to multiple types of elements.\nOr select Show Type Selections to define the status definition to a subset of types.\nRight-click the Status Definition in the Dictionary Explorer and select STAVAL: Status Value. Enter a Name, Description and Numerical value in the Current Element Editor.\n\nEach Status Value can have Valid transitions, in the Valid transitions field, click the selection button.\n\nThe Select valid status transitions window is displayed populated with status values that are valid transitions.\n\nSelect the status values that will be valid transitions from this value and click OK.\nOr click Cancel to discard any inputs and close the Select valid status transitions window.\nEach status value can have a value to promote or demote to, the Promote/Demote fields, click the selection button. From the drop-down list, select the appropriate values.\n\nSelect the Status Definition again in the Explorer and note its Initial status.\nIf required, a status definition can have a reason value (for example: Release, Approve, and so on) associated with it, from the Current Element Editor, in the Reason values field, click the selection button.\n\nFrom the drop-down list, select the appropriate reason, by default it is unset. The Status Definition is now complete and ready for use.\nRight click the Status Definition in the Dictionary Explorer and select Graphical View to see a workflow diagram as shown below. Click on any status value in the graphical view to make it current in the Dictionary Explorer.\n\nSave the work and exit Lexicon.\nNote:\nThese will typically be similar but the description can include spaces and will be used in the Status Controller if it is set.\nNote:\nIt will be set to the first status value by default, but the User can change this if required.\nNote:\nUDTGs can also be added as part of the controllable element types.\nNote:\nNumerical values are optional and may be used as a percentage or a simple value.\nNote:\nStatus Value name uniqueness applies only within the owning Status Definition. So names can be repeated, for example Preliminary and Released in different definitions.\nNote:\nPromote and demote are optional and simply denote a main route through the workflow - any valid transitions not marked as promote or demote will still be available in the Status Controller.\n\n\n\nSTAWLD\nDictionary Explorer\nSTADEF: Status Definition\nName\nDescription\nCurrent Element Editor\nNote\n:\nCurrent Element Editor\nInitial status\nNote\n:\nCurrent Element Editor\nControllable element type\nControllable element type\nSelect element types\nAvailable element types\nSelect element types\nAdd to list\nOK\nNote\n:\nShow Type Selections\nDictionary Explorer\nSTAVAL: Status Value\nName\nDescription\nNumerical value\nCurrent Element Editor\nNote\n:\nNote\n:\nPreliminary\nReleased\nValid transitions\nValid transitions\nSelect valid status transitions\nOK\nCancel\nSelect valid status transitions\nPromote/Demote\nNote\n:\nmain\nStatus Definition\nInitial status\nCurrent Element Editor\nReason values\nDictionary Explorer\nGraphical View\nDictionary Explorer."}
{"Headers": "Constructor Modules and Status Control", "Content": "The constructor modules such as AVEVA E3D Design Model, Paragon, Design and Outfitting, use the Status Controller to interact with Controlled Objects (any model object that has one or more status values assigned to it).\nOn the Manage tab, in the Status Control group, select Status Controller to display the Status Controller window.\n\nThe Status Controller window is initially blank unless status layouts have been previously created.\n\n\n\nManage\nStatus Control\nStatus Controller\nStatus Controller\nStatus Controller"}
{"Headers": "Status Layout", "Content": "If status layouts have been created, once selected from the Status Layout drop-down list, the window is renamed and columns are displayed to reflect this and populated with all the model objects which have the same element type specified for the selected status definition in Lexicon, for example, PIPE.\n\nThroughout this guide, the Status Controller window will continue to be referred to as the Status Controller window.\n\n\n\nStatus Layout\nStatus Controller\nStatus Controller"}
{"Headers": "Create a Status Layout", "Content": "To create a Status Layout, from the Status Controller window, select New Layout from the Status Layout drop-down list.\nOr\nRight-click on the header and select Status Layout from the displayed menu.\n\nThe Select Status Columns window is displayed, populated with all the status definitions and values created by the administrator in Lexicon.\n\nSelect the checkbox alongside the required status definition, for example, select the checkbox alongside Pipe Design Status then click OK.\nThe Set Layout Scope Elements window is then displayed to allow for scope selection. Refer to Set Layout Scope Elements for further information.\n\nClick Add to display the Reference Browser. Use the Explorer and Search tabs to select the required owning elements, then click OK. Refer to Reference Browser for further information.\n\nIf cancelled, the Status Controller window is populated with those model objects that are or could be controlled by the selected status definitions.\nA selected scope reduces the number of rows populated, which can mean a much faster display of the Status Controller window. If more than one Status Definition has been selected, one can be selected as the Focus Status in the drop-down list, and this will be used for Edit Status operations.\n\nTo modify the currently selected scope to display particular status data, select Set Layout Scope from the Status Layout quick access tool bar.\nIn the grid area, select Column Setup from the right-click menu.\n\nThe Column Setup window is displayed, populated with the pseudo-attribute expressions for the status columns already added.\n\nThe chosen column layout can be saved, in the grid area of the Status Controller window, right click one of the column titles and from the displayed menu, select Save Status Layout.\n\nThe Status Layout is automatically saved to the default location. To save the Status Layout with a different name, in the grid of the Default Status Profile window, right-click one of the column titles and from the displayed menu, select Save Status Layout As. The Save Layout As window is displayed.\n\nThis name then appears in the Status Layout drop-down list on the Status Controller window.\nSTVDSC( /DesignStatus ) of Deslnk numb 1\nNote:\nThis can take several minutes, if unsure what to include, select an element such as a zone that has few offspring; the scope can always be changed later.\nNote:\nThe User can show the status of a related object in its own column. For example, if the User is managing status of schematic equipment (SCEQUI), they can show the status of a linked EQUI using an expression like. Refer to Status Control Pseudo-Attributes for further information.\nNote:\nSetting up a column to display the Reason attribute - attributes expression is \"STVREA (/StatusName)\", for example STVREA (/CORStatus).\nNote:\nThe other options available on the right-click menu from the column titles, including Settings and Export to Excel. Refer to Getting Started for further information.\n\n\n\nSet Layout Scope Elements\nReference Browser\nStatus Control Pseudo-Attributes\nGetting Started\nStatus Controller\nNew Layout\nStatus Layout\nStatus Layout\nSelect Status Columns\nPipe Design Status\nOK\nSet Layout Scope Elements\nSet Layout Scope Elements\nAdd\nReference Browser\nExplorer\nSearch\nOK\nReference Browser\nStatus Controller\nStatus Controller\nNote\n:\nSet Layout Scope\nStatus Layout\nColumn Setup\nColumn Setup\nNote\n:\nStatus Control Pseudo-Attributes\nSTVDSC( /DesignStatus ) of Deslnk numb 1\nNote\n:\nSTVREA (/StatusName)\nSTVREA (/CORStatus)\nStatus Controller\nSave Status Layout\nDefault Status Profile\nSave Status Layout As\nSave Layout As\nStatus Layout\nStatus Controller\nNote\n:\nSettings\nExport to Excel\nGetting Started"}
{"Headers": "Edit Status Operations", "Content": "In the Status Controller window, select the rows for the model objects to be controlled, right-click in the selected area, and then from the displayed menu, select Edit Status.\n\nThe Edit Status window is displayed, to edit status values for the selected model objects. Initially the objects are Not Controlled, that is they have not been assigned a status value.\n\nSelect from the status value drop-down list, select for example, Assign to the initial value, the available status values reflects the valid transitions in the status definition set in Lexicon. Enter a relevant Comment (optional).\nIf the status definition has any states where a list of reasons values are defined then the Reason drop down list is displayed on the Edit Status window (this attribute is mandatory).\n\nUse the status control to change the status on a selected element. If the transition is to a state with a list of reason values defined then the Reason drop down list is populated, if the state does not have values defined then the drop down list is not displayed.\nClick Apply, then click OK.\nOr\nClick Cancel to discard any inputs and close the Status window.\nIf Promote and Demote transitions have been defined, these can be selected directly.\n\nIn the grid area, select the model object to be promoted or demoted, right-click and from the displayed menu, select for example Promote, a variant of the Edit Status window is displayed.\nFor multiple select elements on Promote and Demote, if all elements are at the same state then the behaviour is the same as for a single element; if some elements are at different states then the following error window is displayed.\n\nOnce the session is saved the reason is displayed in the Status History for an element. If an element has a status assignment and transition in the same session then any reason set on the transition is also displayed on the assignment.\n\nIf a status value has a reference to a list of values of the wrong type (for example integers) then the Reason drop down list will be empty and disabled.\nIf a status value has a reference to a list of values where the referenced UDLOV has been deleted or is in a Database (DB) that is not available then a window is displayed.\n\n\nRemove Status deletes the status data for the selected model objects, (which means the model objects are no longer be controlled).\n\nNavigate To allows a single row to be selected in the grid area and highlighted in the Model Explorer. In the grid area, right click the required row, then from the displayed menu, select Navigate To.\n\nNote:\nThe content of the drop down list changes appropriately for the status selected.\nNote:\nActual values are shown if all selected model objects share the same values, otherwise are displayed as mixed.\n\n\n\nStatus Controller\nEdit Status\nEdit Status\nAssign\nComment\nReason\nEdit Status\nReason\nNote\n:\nApply\nOK\nCancel\nStatus\nPromote\nDemote\nPromote\nEdit Status\nNote\n:\nmixed\nRemove Status\nNavigate To\nModel Explorer\nNavigate To"}
{"Headers": "Status History", "Content": "Status History displays the Status History window for the selected model objects which lists the status transitions along with other session history.\n\nTo export the data from the Status History window into an Excel document, in the grid area, right-click and select from the displayed menu Export to Excel. This functionality is common to all modules. Refer to Common Functionality for further information.\n\n\n\nCommon Functionality\nStatus History\nStatus History\nExport to Excel\nCommon Functionality"}
{"Headers": "Statistical Reports", "Content": "Statistical Report displays the Statistical Report window to display the data and charts for the Focus Status on the selected model objects. In the grid area, right-click the selected model objects and from the displayed menu, select Statistical Report. The Statistical Report window is displayed.\n\nHovering the cursor over one of the regions on the chart gives some figures for the model objects it represents.\n\nRight-click while the cursor is over a region on the chart, from the displayed menu, when an option is selected, the functionality is applied to the objects represented by that region.\n\nFor example, when List Elements is selected, a list of the elements for that region is displayed.\n\nRight-click in the background of the window, the displayed menu offers various options, including a range of Chart Types, for example here is a Bar Chart 3D.\n\n\n\n\nStatistical Report\nStatistical Report\nStatistical Report\nStatistical Report\nList Elements\nChart Types"}
{"Headers": "Status Pseudo-Attributes and Commands", "Content": "A number of pseudo-attributes are available on controlled objects to return their current status data, and a set of commands are provided to set status data. These provide an alternative to using the object methods described above.\n\n\n"}
{"Headers": "Status Control Pseudo-Attributes", "Content": "The following pseudo attributes are available on any controlled object.\nAttribute\nQualifier\nReturns\nRemark\nSTVPRO\nSTADEF\nSTAVAL\nGet the promote STAVAL element for the assigned STADEF.\nSTVDEM\nSTADEF\nSTAVAL\nGet the demote STAVAL element for the assigned STADEF.\nSTVLST\nSTADEF array\nGet all assigned STADEFs.\nSTVNUM\nSTADEF\ninteger\nGet the numerical value for the assigned STAVAL.\nSTVDSC\nSTADEF\nstring\nThe description of assigned STAVAL.\nSTVCOM\nSTADEF\nstring\nThe current comment from the latest status command.\nSTVREA\nSTADER\nstring\nThe reason for the last status change.\nSTVNAM\nSTADEF\nstring\nThe name of the assigned STAVAL.\nSTVVAL\nSTADEF\nSTAVAL\nThe current STAVAL for the STADEF.\nSTVLNK\nSTADEF\nSTALNK\nRef to the STALNK element (internal).\nSTVASD\nSTADEF array\nGet all eligible STADEFs, may include currently assigned.\nSTVTRV\nSTADEF array\nGet valid transitions from current STVVAL.\nSTVUNR\nREF array\nGet a list of unresolved STAVAL references from associated STALNKs.\nSTVMOD\nSTADEF\nString\nStatus last modification date.\nSTVUSE\nSTADEF\nString\nStatus last modified by User.\nAttribute\nQualifier\nReturns\nRemark\nSTVPRO\nSTADEF\nSTAVAL\nGet the promote STAVAL element for the assigned STADEF.\nSTVDEM\nSTADEF\nSTAVAL\nGet the demote STAVAL element for the assigned STADEF.\nSTVLST\n\nSTADEF array\nGet all assigned STADEFs.\nSTVNUM\nSTADEF\ninteger\nGet the numerical value for the assigned STAVAL.\nSTVDSC\nSTADEF\nstring\nThe description of assigned STAVAL.\nSTVCOM\nSTADEF\nstring\nThe current comment from the latest status command.\nSTVREA\nSTADER\nstring\nThe reason for the last status change.\nSTVNAM\nSTADEF\nstring\nThe name of the assigned STAVAL.\nSTVVAL\nSTADEF\nSTAVAL\nThe current STAVAL for the STADEF.\nSTVLNK\nSTADEF\nSTALNK\nRef to the STALNK element (internal).\nSTVASD\n\nSTADEF array\nGet all eligible STADEFs, may include currently assigned.\nSTVTRV\n\nSTADEF array\nGet valid transitions from current STVVAL.\nSTVUNR\n\nREF array\nGet a list of unresolved STAVAL references from associated STALNKs.\nSTVMOD\nSTADEF\nString\nStatus last modification date.\nSTVUSE\nSTADEF\nString\nStatus last modified by User.\nThe following pseudo-attributes are available on Status Definitions (STADEF).\nAttribute\nQualifier\nReturns\nRemark\nSTVREF\nstring/number\nSTAVAL\nGet the STAVAL with the given name or number (NUMVAL).\nSTVUSD\nREF array\nAll elements controlled by this STADEF.\nAttribute\nQualifier\nReturns\nRemark\nSTVREF\nstring/number\nSTAVAL\nGet the STAVAL with the given name or number (NUMVAL).\nSTVUSD\n\nREF array\nAll elements controlled by this STADEF.\nThe following pseudo attributes are available on Status Values (STAVAL).\nAttribute\nQualifier\nReturns\nRemark\nSTVDDT\nSTADEF\nDatetime\nStatus Delegation date.\nSTVDEM\nSTAVAL\nGet the demote STAVAL element from this STAVAL.\nSTVDOF\nSTADDEF\nString\nStatus Delegate of.\nSTVPRO\nSTAVAL\nGet the promote STAVAL element from this STAVAL.\nSTVUSD\nREF array\nAll elements controlled by this STADEF and with this STAVAL current.\nAttribute\nQualifier\nReturns\nRemark\nSTVDDT\nSTADEF\nDatetime\nStatus Delegation date.\nSTVDEM\n\nSTAVAL\nGet the demote STAVAL element from this STAVAL.\nSTVDOF\nSTADDEF\nString\nStatus Delegate of.\nSTVPRO\n\nSTAVAL\nGet the promote STAVAL element from this STAVAL.\nSTVUSD\n\nREF array\nAll elements controlled by this STADEF and with this STAVAL current.\nTo query a qualified pseudo attribute on the command line, enter the qualifier in brackets noting the space required in front of the closing bracket, e.g.\nThis will return the name of the status value, e.g. /WorkPending.\nTo obtain this information in PML2, add the required status definitions into an array and use the qualified attribute method as illustrated below.\nIn this example the first element of the status values array will now be set to the status value object, e.g.\nThis will return the string 'Work Pending'.\nWhen using status value as a condition in a collection, a command like the following will not return the expected objects:\nThis is because the name of the status value is local to the definition (so that the same name can be used in multiple definitions). Instead use one of these:\nAttribute\nQualifier\nReturns\nRemark\nSTVPRO\nSTADEF\nSTAVAL\nGet the promote STAVAL element for the assigned STADEF.\nSTVDEM\nSTADEF\nSTAVAL\nGet the demote STAVAL element for the assigned STADEF.\nSTVLST\nSTADEF array\nGet all assigned STADEFs.\nSTVNUM\nSTADEF\ninteger\nGet the numerical value for the assigned STAVAL.\nSTVDSC\nSTADEF\nstring\nThe description of assigned STAVAL.\nSTVCOM\nSTADEF\nstring\nThe current comment from the latest status command.\nSTVREA\nSTADER\nstring\nThe reason for the last status change.\nSTVNAM\nSTADEF\nstring\nThe name of the assigned STAVAL.\nSTVVAL\nSTADEF\nSTAVAL\nThe current STAVAL for the STADEF.\nSTVLNK\nSTADEF\nSTALNK\nRef to the STALNK element (internal).\nSTVASD\nSTADEF array\nGet all eligible STADEFs, may include currently assigned.\nSTVTRV\nSTADEF array\nGet valid transitions from current STVVAL.\nSTVUNR\nREF array\nGet a list of unresolved STAVAL references from associated STALNKs.\nSTVMOD\nSTADEF\nString\nStatus last modification date.\nSTVUSE\nSTADEF\nString\nStatus last modified by User.\nAttribute\nQualifier\nReturns\nRemark\nSTVREF\nstring/number\nSTAVAL\nGet the STAVAL with the given name or number (NUMVAL).\nSTVUSD\nREF array\nAll elements controlled by this STADEF.\nAttribute\nQualifier\nReturns\nRemark\nSTVDDT\nSTADEF\nDatetime\nStatus Delegation date.\nSTVDEM\nSTAVAL\nGet the demote STAVAL element from this STAVAL.\nSTVDOF\nSTADDEF\nString\nStatus Delegate of.\nSTVPRO\nSTAVAL\nGet the promote STAVAL element from this STAVAL.\nSTVUSD\nREF array\nAll elements controlled by this STADEF and with this STAVAL current.\nQ STVVAL(/DesignStatus )\n!statusDefinitions[1] = /DesignStatus\n!statusValues = !!ce.attribute('STVVAL', !statusDefinitions)\nQ var !statusValues[1].desc\nvar !myItems collect all equi with (stvval( /EquipmentDesignStatus )\neq /Approved )\nvar !myItems collect all equi with (stvnam( /EquipmentDesignStatus )\neq '/ Approved')\nvar !myItems collect all equi with (stvnum( /EquipmentDesignStatus ) gt 75)\n\n\n\nAttribute\nQualifier\nReturns\nRemark\nAttribute\nQualifier\nReturns\nRemark\nAttribute\nQualifier\nReturns\nRemark\nQ STVVAL(/DesignStatus )\n/WorkPending\n!statusDefinitions[1] = /DesignStatus\n!statusValues = !!ce.attribute('STVVAL', !statusDefinitions)\nQ var !statusValues[1].desc\nvar !myItems collect all equi with (stvval( /EquipmentDesignStatus )\neq /Approved )\nvar !myItems collect all equi with (stvnam( /EquipmentDesignStatus )\neq '/ Approved')\nvar !myItems collect all equi with (stvnum( /EquipmentDesignStatus ) gt 75)"}
{"Headers": "Status Control Commands", "Content": "The following section details the commands for Status Control.\n\n\n\n\n\n\n\nSTM ASS[ign] /Definition [to SELELE] ['comment']\nSTM REM[ove] /Definition [from SELELE]\nSTM RESET /Definition [on SELELE] ['comment']\nSTM DE[mote] /Definition [on SELELE] ['comment']\nSTM PRO[mote] /Definition [on SELELE] ['comment']\nSTM SET /Definition [/Value] [on SELELE] ['comment']\nSTM CO/mment /Definition [on SELELE] 'comment'\n\n\n\nSTM ASS[ign] /Definition [to SELELE] ['comment']\nSTM REM[ove] /Definition [from SELELE]\nSTM RESET /Definition [on SELELE] ['comment']\nSTM DE[mote] /Definition [on SELELE] ['comment']\nSTM PRO[mote] /Definition [on SELELE] ['comment']\nSTM SET /Definition [/Value] [on SELELE] ['comment']\nSTM CO/mment /Definition [on SELELE] 'comment'"}
{"Headers": "Clean Up Orphan Status Links", "Content": "Deleting status controlled elements leaves orphan STALNK elements behind, with their attribute CELREF reported as BADREF by Dice. A new PML function has been added to fix this problem.\nExecute \"!!stmcleanup()\" on the command line to clean up all STALNKs with an invalid CELREF.\nExample:\n!!stmcleanup()\n\n\n\n!!stmcleanup()\n!!stmcleanup()"}
{"Headers": "Using Status Control with Data Access Control", "Content": "Status Control can be tightly coupled with Data Access Control (DAC) to preserve data integrity. Below are some examples of what can be achieved. They have been created on the basis of Roles where the first PEROP grants all rights on all element and attribute classes, and then successive PEROPs deny some rights under specific conditions.\n\n\n"}
{"Headers": "Examples for Using Status Control with Data Access Control", "Content": "The following section lists examples for using Status Control with Data Access Control (DAC).\nExample to Prevent Modification of an Object of a Certain Status\nThis is to prevent changes to an object once it has reached a level of completion.\nCreate a PEROP that denies modify and delete operations on equipment for all attributes once the Design Status is greater than or equal to 50%. Here is the condition to use.\nA suitable error message would be: \"DAC: You may not modify object that has status Work Completed\".\nExample to Catch When the Dictionary Database Has Been Deferred\nThis traps the situation where a User has tried to defeat the access control by deferring the dictionary Database (DB) containing the status definitions.\nCreate a PEROP that denies modify and delete operations on equipment for all attributes if the Design Status is not a valid reference. Here is the condition.\nA suitable error message would be: \"DAC: You may not modify an object with an unresolved status\".\nExample to Prevent Change of Status After a Certain Level\nThis is to allow a User to move an object into a For Check state but prevent them from moving it out. A more privileged User will have the task of promoting it to Checked.\nCreate a PEROP that denies modify and delete operations on STALNK (status link) elements for attribute VALREF (status value reference) if the current value of Design Status is For Check. Here is the condition.\nA suitable error message would be: \"DAC: You may not change the Design Status of this object as it is awaiting Check\".\nExample to Prevent Removal of Status from an Object\nThis is to prevent a User from removing status from a controlled object.\nCreate a PEROP that denies delete operations on STALNK (status link) elements if they are controlled by Design Status. Here is the condition.\nA suitable error message would be: \"DAC: You may not remove Design Status from this object\".\nExample Where a User May Only Amend Status\nThis example illustrates how to prevent a User from making any changes, other than those related directly to status assignment and transition.\nCreate a PEROP that grants all operations to the status hierarchy. The PEROP should be applied to the following element type:\nThis will apply the PEROP to all objects in the status hierarchy. Assign this PEROP (and only this PEROP) to the User.\nThis is a positive Data Access Control. It grants access rights to objects. It is therefore not possible to define a specific DAC error message which will be shown if the User tries to carry out a forbidden action (for example an attempt to create an element). A generic DAC error message will be shown in these cases.\nExample to Prevent Issue of an Object That Does Not Have Sufficient Status\nThis is to prevent a User from issuing an object that has not been assigned a status or the status has not reached a sufficient level.\nCreate a PEROP that denies issue operations on equipment when the Design Status is not assigned or is less than 100. Here is the condition:\nA suitable error message would be: \"DAC: You may not issue this object until it has been Approved\".\nCOND ( ATTRIB STVNUM(ID /DesignStatus ) GE 50 )\nCOND ( NOT UNSET ( ATTRIB STVUNR ) )\nCOND ( ATTRIB OWNER OF VALREF  EQ ID /DesignStatus  AND ATTRIB DESC OF VALREF  EQ\n         'For Check'  )\nCOND ( ATTRIB OWNER OF VALREF  EQ ID /DesignStatus  )\nSTLNKW HIERARCHY\nCOND ( UNSET( STVLSK ) OR ATTRIB STVNUM(ID / DesignStatus ) LT 100 )\n\n\n\nExample to Prevent Modification of an Object of a Certain Status\nCOND ( ATTRIB STVNUM(ID /DesignStatus ) GE 50 )\nExample to Catch When the Dictionary Database Has Been Deferred\nCOND ( NOT UNSET ( ATTRIB STVUNR ) )\nExample to Prevent Change of Status After a Certain Level\nCOND ( ATTRIB OWNER OF VALREF  EQ ID /DesignStatus  AND ATTRIB DESC OF VALREF  EQ\n         'For Check'  )\nExample to Prevent Removal of Status from an Object\nCOND ( ATTRIB OWNER OF VALREF  EQ ID /DesignStatus  )\nExample Where a User May Only Amend Status\nSTLNKW HIERARCHY\nExample to Prevent Issue of an Object That Does Not Have Sufficient Status\nCOND ( UNSET( STVLSK ) OR ATTRIB STVNUM(ID / DesignStatus ) LT 100 )"}
{"Headers": "Using Status Control with Auto Colors", "Content": "Status values can be used in the Element Rules for Auto Colors.\n\n\n"}
{"Headers": "Examples for Using Status Control with Auto Colors", "Content": "The following section lists examples for using Status Control with Auto Colors.\nExample Rule for Equipment with Design Status Pending\nRule Name: Equipment Pending\nTypes: EQUI\nRule: attrib stvnum( /DesignStatus ) eq 0\nExample Rule for Equipment with Design Work Completed or Higher\nRule Name: Equipment Completed\nTypes: EQUI\nRule: attrib stvnum( /DesignStatus ) ge 50\nExample Rule for Equipment with Design Status Not Controlled\nRule Name: Equipment Not Controlled\nTypes: EQUI\nRule: badref ( attrib stvval( /DesignStatus ) )\nIf these Element Rules are defined, then Auto Color rules can be added. For example: to show completed equipment in green, pending equipment in yellow, and uncontrolled equipment in red.\n\n\n\n\nExample Rule for Equipment with Design Status Pending\nattrib stvnum( /DesignStatus ) eq 0\nExample Rule for Equipment with Design Work Completed or Higher\nattrib stvnum( /DesignStatus ) ge 50\nExample Rule for Equipment with Design Status Not Controlled\nbadref ( attrib stvval( /DesignStatus ) )"}
{"Headers": "Customizing Status Control using PML", "Content": "Status Control operations can be carried out using Programmable Macro Language (PML). All the operations that can be carried out using the Status Controller can also be done using the appropriate objects and syntax.\nSpecific company and project requirements can be implemented using Status Events and a framework is provided for this purpose.\n\n\n"}
{"Headers": "Status Events in PML", "Content": "Status Control provides an event mechanism that can be customized for individual company and project requirements. User methods can be added as event handlers and will be called with a single array argument. The following events are supported.\nStatus Change Events\nBeforeStatusAssign\nBefore a status is assigned to an object.\nAfterStatusAssign\nAfter a status is assigned to an object.\nBeforeStatusRemove\nBefore a status is removed from an object.\nAfterStatusRemove\nAfter a status is removed from an object.\nBeforeStatusChange\nBefore a status is changed/promoted/demoted on an object.\nAfterStatusChange\nAfter a status is changed/promoted/demoted on an object.\nBeforeControlledElementDelete\nBefore a controlled object is deleted.\n1\nARRAY\nString reference numbers of controlled objects.\n2\nSTRING\nReference number of status definition.\n3\nSTRING\nReference number of to status value (may be =0/0).\n4\nSTRING\nReturn message aborts operation if set but only on Before \u2026 operations.\nDatabase Change Events\nBeforeSavework\nBefore savework when there are changes to status data.\nAfterSavework\nAfter savework when there are changes to status data.\nBeforeFlush\nBefore flush when there are changes to status data.\nAfterFlush\nAfter flush when there are changes to status data.\n1\nSTRING\nReference number of status definition.\n2\nARRAY\nString reference numbers of objects that had status assigned.\n3\nARRAY\nString reference numbers of objects that had status changed.\n4\nARRAY\nString reference numbers of objects that had status removed.\n5\nSTRING\nReturn message aborts operation if set but only on Before \u2026 operations.\n\nEvent\nDescription\nBeforeStatusAssign\nBefore a status is assigned to an object.\nAfterStatusAssign\nAfter a status is assigned to an object.\nBeforeStatusRemove\nBefore a status is removed from an object.\nAfterStatusRemove\nAfter a status is removed from an object.\nBeforeStatusChange\nBefore a status is changed/promoted/demoted on an object.\nAfterStatusChange\nAfter a status is changed/promoted/demoted on an object.\nBeforeControlledElementDelete\nBefore a controlled object is deleted.\nArg No\nType\nDescription\n1\nARRAY\nString reference numbers of controlled objects.\n2\nSTRING\nReference number of status definition.\n3\nSTRING\nReference number of to status value (may be =0/0).\n4\nSTRING\nReturn message aborts operation if set but only on Before \u2026 operations.\nEvent\nDescription\nBeforeSavework\nBefore savework when there are changes to status data.\nAfterSavework\nAfter savework when there are changes to status data.\nBeforeFlush\nBefore flush when there are changes to status data.\nAfterFlush\nAfter flush when there are changes to status data.\nArg No\nType\nDescription\n1\nSTRING\nReference number of status definition.\n2\nARRAY\nString reference numbers of objects that had status assigned.\n3\nARRAY\nString reference numbers of objects that had status changed.\n4\nARRAY\nString reference numbers of objects that had status removed.\n5\nSTRING\nReturn message aborts operation if set but only on Before \u2026 operations.\n\n\n\nStatus Change Events\nDatabase Change Events"}
{"Headers": "Customizing the StatusProjectHandler PML Object", "Content": "A framework for customizing events is provided in the PML object statusProjectHandler.pmlobj in the pmllib\\common\\objects folder. A Global instance of this object is created on entry to the constructor module. It adds the event handlers and has methods for each event.\nDebug Mode\nThe User can switch ON or OFF a debug mode with the following commands.\nIn debug mode, a line of text is output to the command line for each event. For example, here is the output for object P1501A when promoted from Work Suspended to Work Started.\nWhere to Add Code\nEach event method processes its arguments and creates some variables that may be of use to the developer.\nEach place where customized code can be added is delimited as follows.\nA number of examples are provided (commented out). These make use of the statusData PML object documented below.\nMethods to Add Checks and Abort Changes\nAll of the Before \u2026 methods can be used to make additional checks and can abort the operation by returning an error message, such as to prevent a status change if a particular condition is not met. A variable has been provided for this purpose, e.g.\nBy default, the only check made in the statusProjectHandler is to prevent a general User from deleting a controlled object.\nMethods to Make Dependent Changes\nThe methods AfterStatusAssign, AfterStatusRemove, and AfterStatusChange can be used to make dependent changes when one of these operations is completed, e.g. to cascade a change of status on an assembly to its offspring in the assembly hierarchy.\nMethods to Synchronize External Systems\nThe methods AfterSavework and AfterFlush can be used to synchronize data in external systems once the changes to status data have been committed in the DataBase CONtrol Program (DABACON) Databases (DBs).\n!!statusProjectHandler.debugOn()\n!!statusProjectHandler.debugOff()\nstatusProjectHandler.beforeStatusChange(/P1501A,\n    /DesignStatus, /WorkSuspended, /WorkStarted)\nstatusProjectHandler.afterStatusChange(/P1501A,\n    /DesignStatus, /WorkStarted, /WorkStarted)\n  --==========================================================\n  -- Start of customisation\n  -- End of customisation\n  --==========================================================\n!returnMessage =\n    |Status error: You may not delete a controlled object|\nImportant:\nOther parts of the statusProjectHandler PML object should not be modified.\n\n\n\nDebug Mode\n!!statusProjectHandler.debugOn()\n!!statusProjectHandler.debugOff()\nstatusProjectHandler.beforeStatusChange(/P1501A,\n    /DesignStatus, /WorkSuspended, /WorkStarted)\nstatusProjectHandler.afterStatusChange(/P1501A,\n    /DesignStatus, /WorkStarted, /WorkStarted)\nWhere to Add Code\n  --==========================================================\n  -- Start of customisation\n  -- End of customisation\n  --==========================================================\nImportant\n:\nMethods to Add Checks and Abort Changes\n!returnMessage =\n    |Status error: You may not delete a controlled object|\nMethods to Make Dependent Changes\nAfterStatusAssign\nAfterStatusRemove\nAfterStatusChange\nMethods to Synchronize External Systems"}
{"Headers": "Using the StatusData PML Object", "Content": "The PML object statusData.pmlobj is provided in the pmllib\\common\\objects folder to allow easy manipulation of status data from PML. It encapsulates a number of core objects that are documented below and that can be used directly if preferred.\nNote:\nThe statusData object can hold status data for a single object and status definition combination, or it can hold an array of statusData objects for multiple objects and status definition combinations (refer to Constructor Methods).\n\n\n\nNote\n:"}
{"Headers": "Using the Core Status Objects from PML", "Content": "Access to status data is provided via a set of core objects as described below. These require the appropriate import and using namespace commands:\nimport 'Aveva.Pdms.DataManagement.PML'\nhandle any\n  -- ignore if already loaded\nendhandle\nusing namespace 'Aveva.Pdms.DataManagement.PML'\n\n\n\nimport 'Aveva.Pdms.DataManagement.PML'\nhandle any\n  -- ignore if already loaded\nendhandle\nusing namespace 'Aveva.Pdms.DataManagement.PML'"}
{"Headers": "Customizing Status Control using C# (.NET)", "Content": "As an alternative to (or in combination with) PML customization, customization can also be undertaken in .NET applications. Examples below are given in the C# language.\n\n\n"}
{"Headers": "Namespaces and Assemblies", "Content": "The .NET status objects described below are defined in the Aveva.Pdms.DataManagement.dll assembly, which is found in the standard AVEVA E3D Design install directory (AVEVA_DESIGN_EXE). To use these status objects, programmers need reference to the Aveva.Pdms.Database.dll assembly also found in AVEVA_DESIGN_EXE. To reference other AVEVA NET assemblies, refer to AVEVA NET documentation.)\nTo access this software from Visual Studio, add the assemblies to the project references and declare interest in the namespaces at the top of the client C# files:\nusing Aveva.Pdms.DataManagement;\nusing Aveva.Pdms.Database;\n\n\n\nAVEVA NET\nAVEVA NET\nusing Aveva.Pdms.DataManagement;\nusing Aveva.Pdms.Database;"}
{"Headers": "Classes in .NET", "Content": "The following classes are available in C#. These correspond to and have similar functionality to the PML objects described above.\nThis static class gives access to all the status definition elements in the current MDB. As a static class no instances of the class are created. The class has a single property, Statuses, which returns an array of Status objects (described below), used as follows:\nStatus[] statuses = StatusManagement.Statuses;\n\n\n\nStatus[] statuses = StatusManagement.Statuses;"}
{"Headers": "Class Status", "Content": "This class gives access to a named status definition determined in the constructor either by name or as a DbElement:\nThe screenshot below of the Visual Studio Object Browser details the public interface of the Status class:\n\nClass StatusValue\nThis class gives access to the data relating to a Status Value (STAVAL element). This represents one of the legal states that an element controlled for a given status definition may have. The status definition and value can be determined via the class constructors:\nOr:\nAlternatively, the array of all StatusValues for a given status definition can be obtained directly from a Status object:\nThe remaining functions of the StatusValue class are displayed in the Visual Studio Object Browser below:\n\nClass StatusCommand\nThis static class gives access to all the status functionality. As a static class no instances of the class are created. This class effectively duplicates the functionality otherwise available through instances of the Status class. The Visual Studio Object Browser display is as follows:\n\nClass StatusEvents\nThis class gives access to all the status change events. An instance of the class cannot be instantiated directly by constructor. Instead an instance can be created from the Status.Events property, or from the static functions StatusEvent.GetStatusEventObject(Status s) or StatusEvent.GetStatusEventObject(). The following example shows the registration of an event handler for the BeforeStatusChange event together with a sample implementation of the registered event handler:\nThe list of available status events is displayed in the Visual Studio Object Browser display as follows:\n\nStatus Change Events\nThe Before \u2026 event methods can cancel the operation.\nEvent\nArguments\nBeforeStatusAssign\nobject sender, CancelStatusEventArgs e\nAfterStatusAssign\nobject sender, StatusEventArgs e\nBeforeStatusRemove\nobject sender, CancelStatusEventArgs e\nAfterStatusRemove\nobject sender, StatusEventArgs e\nBeforeStatusChange\nobject sender, CancelStatusEventArgs e\nAfterStatusChange\nobject sender, StatusEventArgs e\nBeforeControlledElementDelete\nobject sender, CancelStatusEventArgs e\nEvent\nArguments\nBeforeStatusAssign\nobject sender, CancelStatusEventArgs e\nAfterStatusAssign\nobject sender, StatusEventArgs e\nBeforeStatusRemove\nobject sender, CancelStatusEventArgs e\nAfterStatusRemove\nobject sender, StatusEventArgs e\nBeforeStatusChange\nobject sender, CancelStatusEventArgs e\nAfterStatusChange\nobject sender, StatusEventArgs e\nBeforeControlledElementDelete\nobject sender, CancelStatusEventArgs e\nStatusEventArgs\nName\nType\nDescription\nModel\nDbElement[]\nArray of elements that is/to be controlled.\nStatus\nStatus\nThe Status object.\nTo\nStatusValue\nThe to StatusValue object.\nName\nType\nDescription\nModel\nDbElement[]\nArray of elements that is/to be controlled.\nStatus\nStatus\nThe Status object.\nTo\nStatusValue\nThe to StatusValue object.\nCancelStatusEventArgs\nName\nType\nDescription\nModel\nDbElement[]\nArray of elements that is/to be controlled.\nStatus\nStatus\nThe Status object.\nTo\nStatusValue\nThe to StatusValue object.\nCancel\nBool\nCancel the ongoing operation.\nMessage\nString\nWith this as the message.\nName\nType\nDescription\nModel\nDbElement[]\nArray of elements that is/to be controlled.\nStatus\nStatus\nThe Status object.\nTo\nStatusValue\nThe to StatusValue object.\nCancel\nBool\nCancel the ongoing operation.\nMessage\nString\nWith this as the message.\nDatabase Change Events\nThe Before \u2026 event methods can cancel the operation.\nEvent\nArguments\nBeforeSavework\nobject sender, CancelDBChangeEventArgs e\nAfterSavework\nobject sender, DBChangeEventArgs e\nBeforeFlush\nobject sender, CancelDBChangeEventArgs e\nAfterFlush\nobject sender, DBChangeEventArgs e\nEvent\nArguments\nBeforeSavework\nobject sender, CancelDBChangeEventArgs e\nAfterSavework\nobject sender, DBChangeEventArgs e\nBeforeFlush\nobject sender, CancelDBChangeEventArgs e\nAfterFlush\nobject sender, DBChangeEventArgs e\nDBChangeEventArgs\nName\nType\nDescription\nStatus\nStatus\nThe Status object.\nAssigned\nDbElement[]\nArray of DbElements that had Status assigned.\nChanged\nDbElement[]\nArray of DbElements that had Status changed.\nRemoved\nDbElement[]\nArray of DbElements that had Status removed.\nName\nType\nDescription\nStatus\nStatus\nThe Status object.\nAssigned\nDbElement[]\nArray of DbElements that had Status assigned.\nChanged\nDbElement[]\nArray of DbElements that had Status changed.\nRemoved\nDbElement[]\nArray of DbElements that had Status removed.\nCancelDBChangeEventArgs\nName\nType\nDescription\nStatus\nStatus\nThe Status object.\nAssigned\nDbElement[]\nArray of DbElements that had Status assigned.\nChanged\nDbElement[]\nArray of DbElements that had Status changed.\nRemoved\nDbElement[]\nArray of DbElements that had Status removed.\nCancel\nBool\nCancel the ongoing operation.\nMessage\nString\nWith this as the message.\nName\nType\nDescription\nStatus\nStatus\nThe Status object.\nAssigned\nDbElement[]\nArray of DbElements that had Status assigned.\nChanged\nDbElement[]\nArray of DbElements that had Status changed.\nRemoved\nDbElement[]\nArray of DbElements that had Status removed.\nCancel\nBool\nCancel the ongoing operation.\nMessage\nString\nWith this as the message.\n\nEvent\nArguments\nBeforeStatusAssign\nobject sender, CancelStatusEventArgs e\nAfterStatusAssign\nobject sender, StatusEventArgs e\nBeforeStatusRemove\nobject sender, CancelStatusEventArgs e\nAfterStatusRemove\nobject sender, StatusEventArgs e\nBeforeStatusChange\nobject sender, CancelStatusEventArgs e\nAfterStatusChange\nobject sender, StatusEventArgs e\nBeforeControlledElementDelete\nobject sender, CancelStatusEventArgs e\nName\nType\nDescription\nModel\nDbElement[]\nArray of elements that is/to be controlled.\nStatus\nStatus\nThe Status object.\nTo\nStatusValue\nThe to StatusValue object.\nName\nType\nDescription\nModel\nDbElement[]\nArray of elements that is/to be controlled.\nStatus\nStatus\nThe Status object.\nTo\nStatusValue\nThe to StatusValue object.\nCancel\nBool\nCancel the ongoing operation.\nMessage\nString\nWith this as the message.\nEvent\nArguments\nBeforeSavework\nobject sender, CancelDBChangeEventArgs e\nAfterSavework\nobject sender, DBChangeEventArgs e\nBeforeFlush\nobject sender, CancelDBChangeEventArgs e\nAfterFlush\nobject sender, DBChangeEventArgs e\nName\nType\nDescription\nStatus\nStatus\nThe Status object.\nAssigned\nDbElement[]\nArray of DbElements that had Status assigned.\nChanged\nDbElement[]\nArray of DbElements that had Status changed.\nRemoved\nDbElement[]\nArray of DbElements that had Status removed.\nName\nType\nDescription\nStatus\nStatus\nThe Status object.\nAssigned\nDbElement[]\nArray of DbElements that had Status assigned.\nChanged\nDbElement[]\nArray of DbElements that had Status changed.\nRemoved\nDbElement[]\nArray of DbElements that had Status removed.\nCancel\nBool\nCancel the ongoing operation.\nMessage\nString\nWith this as the message.\nStatus status = Status(\"/DesignStatus\");\nDbElement statusDefinitionElement;\n// ...\nStatus status = Status(statusDefinitionElement);\nStatus status = Status(\"/DesignStatus\");\nStatusValue statusValue = StatusValue(status, \"/Approved\");\nDbElement statusValueElement;\n// ...\nStatusValue statusValue = StatusValue(statusValueElement);\nStatus status = Status(\"/DesignStatus\");\nStatusValue[] statusValues = status.Values;\nStatus status = Status(\"/DesignStatus\");\nStatusEvent statusEvent = status.Event;\nstatusEvent.BeforeStatusChange += new\n   StatusEvent.BeforeStatusChangeEventHandler(My_BeforeStatusChange);\n// ...\n// Event handler\nprivate void My_BeforeStatusChange (object sender,\n                                    CancelStatusEventArgs e)\n{\n}\n\n\n\nStatus status = Status(\"/DesignStatus\");\nDbElement statusDefinitionElement;\n// ...\nStatus status = Status(statusDefinitionElement);\nVisual Studio Object Browser\nClass StatusValue\nStatus status = Status(\"/DesignStatus\");\nStatusValue statusValue = StatusValue(status, \"/Approved\");\nDbElement statusValueElement;\n// ...\nStatusValue statusValue = StatusValue(statusValueElement);\nStatus status = Status(\"/DesignStatus\");\nStatusValue[] statusValues = status.Values;\nClass StatusCommand\nClass StatusEvents\nStatus status = Status(\"/DesignStatus\");\nStatusEvent statusEvent = status.Event;\nstatusEvent.BeforeStatusChange += new\n   StatusEvent.BeforeStatusChangeEventHandler(My_BeforeStatusChange);\n// ...\n// Event handler\nprivate void My_BeforeStatusChange (object sender,\n                                    CancelStatusEventArgs e)\n{\n// Do any extra actions and check status change is allowed\nif ( /* abort status change required */ )\n{\ne.Cancel = true;\ne.Message = \"reason not to proceed\";\n}\n}\nStatus Change Events\nEvent\nArguments\nStatusEventArgs\nName\nType\nDescription\nCancelStatusEventArgs\nName\nType\nDescription\nDatabase Change Events\nEvent\nArguments\nDBChangeEventArgs\nName\nType\nDescription\nCancelDBChangeEventArgs\nName\nType\nDescription"}
{"Headers": "Distributing Customized Status Layouts", "Content": "Individual Users can customize and save their own status layouts. This process is described in Status Layout in Status Controller in Design and other Constructor Modules. As an administrator you may decide to create a set of project standard status layouts for all Users on the project.\nStatus layouts are stored in files in the User\u2019s Local Settings Application Data folder, for example, for the project BAS the folder will be:\nAn administrator who has created a set of status layouts in their own folder can copy these files and distribute them to other Users to include in their own equivalent folders. There is no need to copy the LastSelectedStatusGridProfile or WindowsLayout files in this folder as these will be created automatically.\nC:\\Users\\john.smith\\AppData\\Local\\Aveva\\AVEVA Everything3D\\1.1\\BASStatusGridProfiles\n\n\n\nStatus Layout\nStatus Layout\nC:\\Users\\john.smith\\AppData\\Local\\Aveva\\AVEVA Everything3D\\1.1\\BASStatusGridProfiles"}
{"Headers": "Upgrading Model Manager Status Data", "Content": "This section suggests an approach to upgrading status data created by AVEVA Model Manager.\nFor Model Manager, the equivalent to a Status Definition is a list of values for a particular controlled object type and is defined in VPE. Individual controlled objects then hold one of these values in a specified attribute, e.g. :mmstatus.\nA Status Definition could be created for each list of values, applied to the particular controlled object type. Where the controlled object type is qualified by a filter, e.g. PIPE with PURP 'Civils', this could be implemented as a UDET, e.g. :CivilsPipe.\nAn allowable transition should be set from the initial value to each other value in the definition, to support the next stage (some of these transitions could be removed later).\nA macro would then be written, to loop through each controlled object, assign its appropriate status definition then set it to the equivalent status value for its Model Manager status data.\n\n\n"}
{"Headers": "Approved Delegate and Date", "Content": "Status control provides an mechanism that can be customized for individual company and project requirements to delegate the approval of datasheet(s), drawing(s) and tag(s) and display the information in the revision block of the respective element and tag.\nNote:\nIn Lexicon and/or the Configuration modules, the system administrator has created the Allow delegation value and it is displayed in the Status value details fields of the Current Element Editor window.\nNote:\nFor the purposes of this example, the workflow is completed using the Configuration module.\n\n\n\nNote\n:\n\nAllow delegation\nStatus value details\nCurrent Element Editor\nNote\n:\nConfiguration\nConfiguration\nWorkflow\nAPPROVED STVAL\nSTADEF\nWorkflow Explorer\nNote\n:\n\n\nWorkflow\nAPPROVED STVAL\nDictionary Explorer\nAllow Delegate\nStatus value details\nTrue\nFalse\nNote\n:\nDelegate\nDelegate date\nAPPROVED STVAL\nNote\n:\nAllow Delegate\nFalse\nREVISION BLOCK\nWorkflow Explorer\nEdit Revision Block Definition\nRevision Block Definition - Revision Block\nAdd attributes\nApproved Delegate of\nApproved Delegation date\nHeader\nApp\u2019ed Delegate of\nApp\u2019ed Delegation date\nOK\nNote\n:\nOK\nLibraries\nView\nDatasheet\nDatasheet\nExplorer\nEdit Datasheet Template\nDatasheet Template Editor\nDatasheet Template\nData Sources\nRevision Block\nEngineer\nManage\nStatus Actions\nEdit.\nStatus - Engineering Status Definition\nStatus\nStatus - Engineering Status Definition\nNote\n:\nPending Approval\nValue\nStatus\nStatus - Engineering Status Definition\nApproved\nDelegate Of\nDelegation Date\nOK\nPromote Status\nNote\n:\nRevision Issue\nManage\nStatus Actions\nHistory\nStatus History"}
{"Headers": "Assumptions", "Content": "The Building Application Administration Guide has been written to give AVEVA E3D Design administrators the knowledge necessary to set up and configure the AVEVA Building Applications utilities. It introduces AVEVA E3D Design concepts specific to AVEVA Building Applications and explains the significance of parameter files pertinent to AVEVA Building Applications. It is also intended to enable the AVEVA E3D Design Administrators to install, configure and setup AVEVA Building Applications.\nIt is assumed that:\nThe administrator has a valid license and the software has been installed.\nThe administrator has a working knowledge of AVEVA E3D Design Systems Administration and is familiar with AVEVA Building Applications design utilities.\nThe administrator has a valid license and the software has been installed.\nThe administrator has a valid license and the software has been installed.\nThe administrator has a working knowledge of AVEVA E3D Design Systems Administration and is familiar with AVEVA Building Applications design utilities.\nThe administrator has a working knowledge of AVEVA E3D Design Systems Administration and is familiar with AVEVA Building Applications design utilities.\n\n\n"}
{"Headers": "Guide Structure", "Content": "The Building Applications Administration Guide is divided into the following sections:\nBuilding Applications\nintroduces the guide and summarizes it scope.\nInstallation\nhow to customise the installation.\nBuilding Applications Configuration\nhow to configure and update the .bat files\nParameter Files\ncontain information that Building Applications uses while in operation.\nCatalogs and Specifications\nhave several conditions or rules which must be followed.\nBuilding Applications\nintroduces the guide and summarizes it scope.\nInstallation\nhow to customise the installation.\nBuilding Applications Configuration\nhow to configure and update the .bat files\nParameter Files\ncontain information that Building Applications uses while in operation.\nCatalogs and Specifications\nhave several conditions or rules which must be followed.\n\nBuilding Applications\nintroduces the guide and summarizes it scope.\nInstallation\nhow to customise the installation.\nBuilding Applications Configuration\nhow to configure and update the .bat files\nParameter Files\ncontain information that Building Applications uses while in operation.\nCatalogs and Specifications\nhave several conditions or rules which must be followed.\n\n\n\nBuilding Applications\nInstallation\nBuilding Applications Configuration\nParameter Files\nCatalogs and Specifications\nBuilding Applications\nInstallation\nBuilding Applications Configuration\nParameter Files\nCatalogs and Specifications"}
{"Headers": "Installation", "Content": "AVEVA Building Applications are separately licensed products:\nRoom Manager\nConcrete Building Design\nConcrete Quantities.\nRoom Manager\nRoom Manager\nConcrete Building Design\nConcrete Building Design\nConcrete Quantities.\nConcrete Quantities.\n\n\n"}
{"Headers": "Building Applications Configuration", "Content": "To configure the Building Application the AVEVA E3D\u2122 administrator must update the .bat file and add the required databases. Refer to Update the .bat File, Addition of Required Databases and Installation Test for further information.\n\n\n\nUpdate the .bat File\nAddition of Required Databases\nInstallation Test\nUpdate the .bat File\nAddition of Required Databases\nInstallation Test"}
{"Headers": "Update the .bat File", "Content": "To make Building Applications available in existing projects, the logic from the .bat files supplied with product can be modified or incorporated with existing .bat files.\nBuilding Applications uses parameter files to define such items as Angle Display Format, Distance Display Format and Auto-Naming Functions. It is typical for these to be stored with a project and edited to be project specific.\nFor example, in a project called SAM the parameter files should be copied into the folder referred to as SAMDFLTS. It can be any folder, but would typically be called samdflts and stored in the project folder.\nThe evars.bat file could be updated with the following to setup the environment variable %SAMDFLTS%:\nThe following environment variables are used by the Building Applications:-\n\n\n\nSAMDFLTS\nif not \"%SAMDFLTS%\"==\"\" goto samdfltsok\nset SAMDFLTS=%1\\project\\samdflts\necho SAMDFLTS=%SAMDFLTS%\n:samdfltsok\n  Building_design normally set to %pmllib%Building_Design\\\n  common_tools normally set to %pmllib%Common_Tools\\\n  aveva_language supported languages are English and French but other languages can\n         be used as follows:-\n%pmllib%\\Building_Design\\language\n%pmllib%\\Common_Tools\\language"}
{"Headers": "Addition of Required Databases", "Content": "To make the most of Building Applications suitable catalogues are required. Sample data is available in the sample project (APS) supplied with AVEVA E3D Design, or can be recreated through the provided macros.\nFor the Catalog and Specification data, two CATA databases are supplied:\n\n\n\n\n"}
{"Headers": "Installation Test", "Content": "The AVEVA E3D Design administrator may test the installation of the Building Applications. To do this, log into AVEVA E3D Design and enter the MODEL module, select the STRUCTURES application, then the BUILDING tab (if the BUILDING tab is visible, then it has been successfully installed).\n\n\n\n\nMODEL\nSTRUCTURES\nBUILDING\nBUILDING"}
{"Headers": "Parameter Files", "Content": "Parameter files contain information that Building Applications uses while in operation. Building Applications is supplied with a number of example parameter files. Metric and imperial versions of the standard parameter files are available. In addition, a set of metric parameter files reflecting the KKS naming system are also supplied.\nEach product has minimum requirements for the parameter files used. These requirements along with a description of significant parameter files are described in the sections that follow.\nParameter files need to be placed in a separate project defaults folder and are used exclusively for Building Applications, for example. SAMDFLTS. The files are contained within three sub-folders, one for each product:\n\nParameter files are read when the Building Applications are loaded and stored in global variables. If required the AVEVA administrator can investigate these files. The administrator must find the parameters files (dflts) supplied with the product.\nconcrete_design\nconcrete_quantities\nroom_manager\nconcrete_design\nconcrete_design\nconcrete_quantities\nconcrete_quantities\nroom_manager\nroom_manager\n\n\n"}
{"Headers": "Concrete Building Design Parameter Files", "Content": "The supplied example parameter files are:\nACCURACY\nANGLES\nAREAS\nCALCULATE\nCORRESPONDENCE\nCSV\nDBSCATALOGUE\nDENSITY\nDES-PURPOSE\nDISTANCEDIRECTION\nDISTANCES\nEDITOR\nELEVATION\nESCALIER\nEXCLUSIONS\nGALETTE\nGTYPES\nHIDECONNECTED\nLEVELS\nNOMMER\nPASCATALOGUE\nSEPARATESTRUCTURE\nSLOPES\nVOLUMES\nACCURACY\nACCURACY\nANGLES\nANGLES\nAREAS\nAREAS\nCALCULATE\nCALCULATE\nCORRESPONDENCE\nCORRESPONDENCE\nCSV\nCSV\nDBSCATALOGUE\nDBSCATALOGUE\nDENSITY\nDENSITY\nDES-PURPOSE\nDES-PURPOSE\nDISTANCEDIRECTION\nDISTANCEDIRECTION\nDISTANCES\nDISTANCES\nEDITOR\nEDITOR\nELEVATION\nELEVATION\nESCALIER\nESCALIER\nEXCLUSIONS\nEXCLUSIONS\nGALETTE\nGALETTE\nGTYPES\nGTYPES\nHIDECONNECTED\nHIDECONNECTED\nLEVELS\nLEVELS\nNOMMER\nNOMMER\nPASCATALOGUE\nPASCATALOGUE\nSEPARATESTRUCTURE\nSEPARATESTRUCTURE\nSLOPES\nSLOPES\nVOLUMES\nVOLUMES\n\n\n\nACCURACY\nANGLES\nAREAS\nCALCULATE\nCORRESPONDENCE\nCSV\nDBSCATALOGUE\nDENSITY\nDES-PURPOSE\nDISTANCEDIRECTION\nDISTANCES\nEDITOR\nELEVATION\nESCALIER\nEXCLUSIONS\nGALETTE\nGTYPES\nHIDECONNECTED\nLEVELS\nNOMMER\nPASCATALOGUE\nSEPARATESTRUCTURE\nSLOPES\nVOLUMES\nACCURACY\nANGLES\nAREAS\nCALCULATE\nCORRESPONDENCE\nCSV\nDBSCATALOGUE\nDENSITY\nDES-PURPOSE\nDISTANCEDIRECTION\nDISTANCES\nEDITOR\nELEVATION\nESCALIER\nEXCLUSIONS\nGALETTE\nGTYPES\nHIDECONNECTED\nLEVELS\nNOMMER\nPASCATALOGUE\nSEPARATESTRUCTURE\nSLOPES\nVOLUMES"}
{"Headers": "ACCURACY", "Content": "The ACCURACY parameter file defines what percentages of the ratio between net volume and gross volume elements are coded yellow or red in the room volume calculations.\nThe keyword WARNING must be followed by a percentage, elements with a net to gross ratio smaller than this percentage are displayed in orange.\nThe keyword ERROR must be followed by a percentage, elements with a net to gross ratio smaller than this percentage are displayed in red.\nAll other elements are displayed in green.\n# Colour Coding for ratio net to gross volume in room volume calculations\nWARNING 80\nERROR 70\n\n\n\nACCURACY\n# Colour Coding for ratio net to gross volume in room volume calculations\nWARNING 80\nERROR 70"}
{"Headers": "ANGLES", "Content": "The ANGLES parameter file defines default format for angles (degrees, degrees/minutes/seconds or grades). If this file cannot be found, the system defaults to decimal degrees.\n# Angle Display Format\n# DD 2 = Decimal Degrees to two decimal places eg. 23.45\n# DMS = Degrees minutes and seconds eg. 23\u00b045'30\"\n# G 2 = Grades to two decimal places ex. 18.63 DMS\n\n\n\nANGLES\n# Angle Display Format\n# DD 2 = Decimal Degrees to two decimal places eg. 23.45\n# DMS = Degrees minutes and seconds eg. 23\u00b045'30\"\n# G 2 = Grades to two decimal places ex. 18.63 DMS"}
{"Headers": "AREAS", "Content": "The AREAS parameter file defines the units to be used for surface areas such as formwork areas. If this file cannot be found then project units is used.\n# Format of areas\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label e.g. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension AREA\nDP 0\nENU true\nFraction false\nLabel UNITS\nUnits FOOT\nZeros true\n\n\n\nAREAS\n# Format of areas\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label e.g. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension AREA\nDP 0\nENU true\nFraction false\nLabel UNITS\nUnits FOOT\nZeros true"}
{"Headers": "CALCULATE", "Content": "The CALCULATE parameter file defines the units to be used for stair flight parameters. If this file cannot be found then project units is used.\n# Format Calculation\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label for example. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension L\nDP 2\nENU true\nFraction false\nFtLabel '\nInchSeparator .\nLabel \"\nUnits FINCH\nZeros true\n\n\n\nCALCULATE\n# Format Calculation\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label for example. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension L\nDP 2\nENU true\nFraction false\nFtLabel '\nInchSeparator .\nLabel \"\nUnits FINCH\nZeros true"}
{"Headers": "CORRESPONDENCE", "Content": "The CORRESPONDENCE parameter file is used for translating between two different catalogues. When the specification translate button is pressed in the diagnostic wizard form, this file is used to change the spref attribute of the sub-components found that currently reference catalogues from other projects.\n\nIf the current spref attribute of the sub-component (SBFI or FIXING) is found in the first column of the file, it is changed to the corresponding value in second column. A suitable file with the first column completed can be generated by pressing the Create File button. The translation function is useful for bulk modifications, copying existing projects and advancing design from feasibility to detailed stages. The relationship between the project and the databases is defined in the DBSCATALOGUE file.\n\n\n\nCORRESPONDENCE"}
{"Headers": "CSV", "Content": "The CSV parameter file defines what characters are to be used in csv file format exports. This currently only used for reports generated by anchor spacing checked but it may be used for other csv format reports in the future.\n#\n# CSV file format\n#\n# separator\n,\n# Text\n\"\n\n\n\nCSV\n#\n# CSV file format\n#\n# separator\n,\n# Text\n\""}
{"Headers": "DBSCATALOGUE", "Content": "The DBSCATALOGUE parameter file lists the names of catalogue databases used in the diagnostic wizard to associate a catalogue with a project. The first word on each line indicates the title of the project that appears as an option on the form. Any word can be used but normally the keywords AVEVA and POWER are reserved for the supplied sample catalogues. The second word can either be SPEC or PROP. If SPEC any element that references these components will be counted in the specification part of the form. If PROP any element that references these materials will be counted in the material part of the form. The third part of the line is the name of the PDMS database.\n# Catalogue databases\n# Format  Project % Type % Name of database\n# Project = AVEVA, POWER ...\n# Type = SPEC/PROP\n# Name =\nAVEVA % PROP % MASTER/PROP\nAVEVA % SPEC % MASTER/STLCATA\nPOWER % SPEC % MASTER/POWERSPEC\n\n\n\nDBSCATALOGUE"}
{"Headers": "DENSITY", "Content": "The DENSITY parameter file\u2026.\n# Format of densities\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label e.g. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension DENS\nDP 0\nENU true\nFraction false\nFtLabel '\nInchSeparator .\nLabel Units\nUnits lb/ft3\nZeros true\n\n\n\nDENSITY\n# Format of densities\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label e.g. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension DENS\nDP 0\nENU true\nFraction false\nFtLabel '\nInchSeparator .\nLabel Units\nUnits lb/ft3\nZeros true"}
{"Headers": "DES-PURPOSE", "Content": "The DES-PURPOSE parameter file is an essential file that is used to describe different elements in chosen language. Each line has the following format:\nCode Type\\Purpose\\Description where\nCode is\na) 0000 for elements only available under concrete zone elements (dunion of 0)\nb) 0002 for elements only available under steel zone elements (dunion of 2)\nc) 0001 for elements available under all zones irrespective of dunion value\nType is the type of the element\nPurpose is the value of the attribute purpose\nDescription is a text which is used in the list of available types for creation on the main Concrete Building Design form.\n#Identifier DEFPURP\n# Purposes\n0001 SITE\\CIV\\Building\n0001 SITE\\SYS\\System\n0001 ZONE\\CIV\\Material\n0001 ZONE\\EQUI\\Equipment\n0001 ZONE\\HS\\Hangers & Supports\n0001 REST\\HS\\Hangers & Supports\n0001 STRU\\LEVL\\Level\n0001 STRU\\HS\\Hangers & Supports\n0001 SUBS\\HS\\Hangers & Supports\n0001 SUBS\\STRU\\Support Structures\n0001 FRMW\\WALL\\All walls\n0002 FRMW\\RETA\\All retaining walls\n0002 FRMW\\SLAB\\All floors\n0002 FRMW\\FOOT\\All Foundations\n0002 FRMW\\BASE\\All Bases\n0002 FRMW\\SHEL\\All Crash Protection\n0002 FRMW\\PASS\\All Nibs\n0001 FRMW\\COLU\\All Columns\n0001 FRMW\\BEAM\\All Beams\n0002 FRMW\\STAI\\All Stairs\n0000 FRMW\\CASE\\All Stairs\n0000 FRMW\\GRAT\\All Grating\n0000 FRMW\\RAIL\\All Handrails\n0000 FRMW\\META\\All Frameworks\n0000 FRMW\\LADD\\All Ladders\n0000 FRMW\\BRAC\\All stability bracing\n0000 FRMW\\TRIM\\All trimmers\n0001 GPWL\\FIRE\\Fire Sectors\n0001 GPWL\\CONS\\Construction Zones\n0001 GPWL\\TEST\\Test\ncontinues .......\nNote:\nFor sub-components, the description is defined in the files beginning with GTYPE.\nNote:\nFor groups of rooms, the type is defined with GPWL\n\n\n\nDES-PURPOSE\nNote\n:\nNote\n:\n#Identifier DEFPURP\n# Purposes\n0001 SITE\\CIV\\Building\n0001 SITE\\SYS\\System\n0001 ZONE\\CIV\\Material\n0001 ZONE\\EQUI\\Equipment\n0001 ZONE\\HS\\Hangers & Supports\n0001 REST\\HS\\Hangers & Supports\n0001 STRU\\LEVL\\Level\n0001 STRU\\HS\\Hangers & Supports\n0001 SUBS\\HS\\Hangers & Supports\n0001 SUBS\\STRU\\Support Structures\n0001 FRMW\\WALL\\All walls\n0002 FRMW\\RETA\\All retaining walls\n0002 FRMW\\SLAB\\All floors\n0002 FRMW\\FOOT\\All Foundations\n0002 FRMW\\BASE\\All Bases\n0002 FRMW\\SHEL\\All Crash Protection\n0002 FRMW\\PASS\\All Nibs\n0001 FRMW\\COLU\\All Columns\n0001 FRMW\\BEAM\\All Beams\n0002 FRMW\\STAI\\All Stairs\n0000 FRMW\\CASE\\All Stairs\n0000 FRMW\\GRAT\\All Grating\n0000 FRMW\\RAIL\\All Handrails\n0000 FRMW\\META\\All Frameworks\n0000 FRMW\\LADD\\All Ladders\n0000 FRMW\\BRAC\\All stability bracing\n0000 FRMW\\TRIM\\All trimmers\ncontinues ......."}
{"Headers": "DISTANCEDIRECTION", "Content": "The DISTANCEDIRECTION parameter file is an optional file used to describe sub-components that are specified by a distance and a direction. This file is not currently supported by the application.\n#\n# Show form for two positions for following gtypes\n#\nHAND\n\n\n\nDISTANCEDIRECTION\n#\n# Show form for two positions for following gtypes\n#\nHAND"}
{"Headers": "DISTANCES", "Content": "The DISTANCES parameter file defines the units to be used for distance/level gadgets. If this file cannot be found then project units is used.\n# Format of distances\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label for example. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension L\nDP 0\nENU true\nFraction true\nFtLabel '\nInchSeparator .\nLabel \"\nUnits FINCH\nZeros FALSE\n\n\n\nDISTANCES\n# Format of distances\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label for example. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension L\nDP 0\nENU true\nFraction true\nFtLabel '\nInchSeparator .\nLabel \"\nUnits FINCH\nZeros FALSE"}
{"Headers": "EDITOR", "Content": "The EDITOR parameter file defines the units to be used for the contour editor. If this file cannot be found then project units is used.\n# Format Editor\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label for example. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension L\nDP 0\nENU true\nFraction true\nFtLabel '\nInchSeparator .\nLabel \"\nUnits FINCH\nZeros false\n\n\n\nEDITOR\n# Format Editor\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label for example. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension L\nDP 0\nENU true\nFraction true\nFtLabel '\nInchSeparator .\nLabel \"\nUnits FINCH\nZeros false"}
{"Headers": "ELEVATION", "Content": "The ELEVATION parameter file defines the units to be used for elevations. If this file cannot be found then project units is used.\n# Format Elevation\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label for example. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension L\nDP 0\nENU true\nFraction true\nFtLabel '\nInchSeparator .\nLabel \"\nUnits FINCH\nZeros false\n\n\n\nELEVATION\n# Format Elevation\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label for example. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension L\nDP 0\nENU true\nFraction true\nFtLabel '\nInchSeparator .\nLabel \"\nUnits FINCH\nZeros false"}
{"Headers": "ESCALIER", "Content": "The ESCALIER parameter file defines default size/formula for steps in staircase. It must be in inches for imperial projects and millimetres for metric projects.\n# Definition of stair parameters\nG+2H = 25\nOptimum step height 7\nMaximum number of steps 20\n\n\n\nESCALIER\n# Definition of stair parameters\nG+2H = 25\nOptimum step height 7\nMaximum number of steps 20"}
{"Headers": "EXCLUSIONS", "Content": "The EXCLUSIONS parameter file defines the excluded elements from room inventory calculations. There are three available methods:\n#\n# To exclude a type of element from inventory lists uncomment the line for this type\n         of element\n#\n# SBFI\n# FIXING\n# FLAN\n# NOZZ\nGENSEC\n#\n# Exclude elements or owning hierarchy that have the given attribute values\nELEMENT Purpose EXCL\nOWNING SITE Name /TEST\nOWNING ZONE Name /TEST_ZONE\n# Using these attribute options may significantly reduce performance\nNote:\nComments can be added to the file using # at the start of the line.\n\n\n\nEXCLUSIONS\nNote\n#\n# To exclude a type of element from inventory lists uncomment the line for this type\n         of element\n#\n# SBFI\n# FIXING\n# FLAN\n# NOZZ\nGENSEC\n#\n# Exclude elements or owning hierarchy that have the given attribute values\nELEMENT Purpose EXCL\nOWNING SITE Name /TEST\nOWNING ZONE Name /TEST_ZONE\n# Using these attribute options may significantly reduce performance"}
{"Headers": "GALETTE", "Content": "The GALETTE parameter file describes the how to name screeds. It is used when creating either slabs with screeds or bases with screeds. If a suitable CSCREED is not available, Concrete Building Design creates one and uses the name calculated from the code supplied in this file.\nCSCREED SLAB /*/S\nCSCREED BASE /*/S\n\n\n\nGALETTE\nCSCREED SLAB /*/S\nCSCREED BASE /*/S"}
{"Headers": "GTYPES", "Content": "The GTYPES parameter file defines the description of cataloged sub-components. These are used in Concrete Building Design to associate the gtype of the sub-component with a description. The first part of each line is the gtype, the second part the description and the third part the default material for this type of sub-component. The material is no longer used as material types (steel, concrete, screed etc) and specific material can now be associated with individual specification components.\nSimilar parameter files exist with \"GTYPES\" prefix that define the description of catalogued sub-components for those element types; for example. GTYPESBEAMS, GTYPESFLOOR, GTYPESGRATING, GTYPESRAIL, GTYPESSTAIR, GTYPESWALL.\nPLAT\\Plate\\HMFS235J2G3\nTUBE\\Sleeve\nCHAN\\Channel\nDRAI\\Floor Drain\\HMFS235J2G3\nDRT\\Topo Point\\HMFS235J2G3\nHOLE\\Hole\nANCH\\Anchorage\\HMFS235J2G3\nRESE\\Reservation\nOPEN\\Opening\\HMFS235J2G3\nDOOR\\Door\\HMFS235J2G3\nFIRE\\Fire Protection\nGATE\\Gate\nPOST\\Post\n\n\n\nGTYPES\nPLAT\\Plate\\HMFS235J2G3\nTUBE\\Sleeve\nCHAN\\Channel\nDRAI\\Floor Drain\\HMFS235J2G3\nDRT\\Topo Point\\HMFS235J2G3\nHOLE\\Hole\nANCH\\Anchorage\\HMFS235J2G3\nRESE\\Reservation\nOPEN\\Opening\\HMFS235J2G3\nDOOR\\Door\\HMFS235J2G3\nFIRE\\Fire Protection\nGATE\\Gate\nPOST\\Post"}
{"Headers": "HIDECONNECTED", "Content": "The HIDECONNECTED parameter file defines the default option when users enter a project. If this file exists the list of connected elements is not shown. This is advisable if there are problems of performance on navigation in the project.\n\n\n\nHIDECONNECTED"}
{"Headers": "LASTUNUSEDNAME", "Content": "If this parameter file exists, Concrete Building Design chooses the last unused name when auto-naming an element.\nThis will often avoid the reuse of the names of deleted elements.\nThe expressions in the file will allow reuse of names if they evaluate to true for the owner\ne.g. :MMSSTATUS lt 50\n\n\n\ne.g. :MMSSTATUS lt 50"}
{"Headers": "LEVELS", "Content": "The LEVELS parameter file defines level attribute for FLOOR/SCREED elements. When a new floor or screed element is created the level attribute is set using this file. The majority of elements in Concrete Building Design are cataloged so their level values are set in the catalogue.\nFLOOR 1 20\nSCREED 6 10\n\n\n\nLEVELS\nFLOOR 1 20\nSCREED 6 10"}
{"Headers": "NOMMER", "Content": "The NOMMER parameter file is critical file to define naming convention for elements. The file must be present for application to propose a name in the creation forms.\nThe first column defines the type, the second column defines the purpose or gtype and the third column gives the naming mask. The following convention is applied to the third column:\nSITE CIV /BUILDING#\nZONE /*-{CS}\nSTRU LEVL /*-LEV%%\nFRMW WALL /*/WALLS\nFRMW RETA /*/RETAINING\nFRMW SLAB /*/FLOORS\nFRMW FOOT /*/FOUNDATIONS\nFRMW BASE /*/BASES\nFRMW BEAM /*/BEAMS\nFRMW COLU /*/COLUMNS\nFRMW STAI /*/STAIRS\nFRMW CASE /*/STAIRS\nFRMW RAIL /*/HANDRAILS\nFRMW TOUS /*/FRMW%%\nFRMW LADD /*/LADDERS\nFRMW GRAT /*/GRATINGS\nFRMW META /*/ASSEMBLY%%\nCFLOOR FOOT /*/%%\nCFLOOR SLAB /*/1F%%\nCFLOOR BASE /*/1B%%\nCSCREED SLAB /*/2F/%%\nCSCREED BASE /*/2B/%%\nCWALL RETA /*/%%\nCWALL WALL /*/%%\nSBFR BEAM /*/%%\nSBFR COLU /*/%%\ncontinues .......\nThe character \"#\" is replaced by a letter between A and Z\nThe character \"%\" is replaced by an integer between 0 and 9\nThe character \"!\" is replaced by the STEXT attribute for a TEXT element, or the empty string for another type of element.\nCharacters \"?\" is replaced by the characters of the owner elements name\n{XXX} indicates a character chosen among the proposed characters.\nSITE CIV /BUILDING#\nZONE /*-{CS}\nSTRU LEVL /*-LEV%%\nFRMW WALL /*/WALLS\nFRMW RETA /*/RETAINING\nFRMW SLAB /*/FLOORS\nFRMW FOOT /*/FOUNDATIONS\nFRMW BASE /*/BASES\nFRMW BEAM /*/BEAMS\nFRMW COLU /*/COLUMNS\nFRMW STAI /*/STAIRS\nFRMW CASE /*/STAIRS\nFRMW RAIL /*/HANDRAILS\nFRMW TOUS /*/FRMW%%\nFRMW LADD /*/LADDERS\nFRMW GRAT /*/GRATINGS\nFRMW META /*/ASSEMBLY%%\nCFLOOR FOOT /*/%%\nCFLOOR SLAB /*/1F%%\nCFLOOR BASE /*/1B%%\nCSCREED SLAB /*/2F/%%\nCSCREED BASE /*/2B/%%\nCWALL RETA /*/%%\nCWALL WALL /*/%%\nSBFR BEAM /*/%%\nSBFR COLU /*/%%\ncontinues .......\nThe character \"#\" is replaced by a letter between A and Z\nThe character \"#\" is replaced by a letter between A and Z\nThe character \"%\" is replaced by an integer between 0 and 9\nThe character \"%\" is replaced by an integer between 0 and 9\nThe character \"!\" is replaced by the STEXT attribute for a TEXT element, or the empty string for another type of element.\nThe character \"!\" is replaced by the STEXT attribute for a TEXT element, or the empty string for another type of element.\nCharacters \"?\" is replaced by the characters of the owner elements name\nCharacters \"?\" is replaced by the characters of the owner elements name\n{XXX} indicates a character chosen among the proposed characters.\nSITE CIV /BUILDING#\nZONE /*-{CS}\nSTRU LEVL /*-LEV%%\nFRMW WALL /*/WALLS\nFRMW RETA /*/RETAINING\nFRMW SLAB /*/FLOORS\nFRMW FOOT /*/FOUNDATIONS\nFRMW BASE /*/BASES\nFRMW BEAM /*/BEAMS\nFRMW COLU /*/COLUMNS\nFRMW STAI /*/STAIRS\nFRMW CASE /*/STAIRS\nFRMW RAIL /*/HANDRAILS\nFRMW TOUS /*/FRMW%%\nFRMW LADD /*/LADDERS\nFRMW GRAT /*/GRATINGS\nFRMW META /*/ASSEMBLY%%\nCFLOOR FOOT /*/%%\nCFLOOR SLAB /*/1F%%\nCFLOOR BASE /*/1B%%\nCSCREED SLAB /*/2F/%%\nCSCREED BASE /*/2B/%%\nCWALL RETA /*/%%\nCWALL WALL /*/%%\nSBFR BEAM /*/%%\nSBFR COLU /*/%%\ncontinues .......\n{XXX} indicates a character chosen among the proposed characters.\n\n\n\nNOMMER\nSITE CIV /BUILDING#\nZONE /*-{CS}\nSTRU LEVL /*-LEV%%\nFRMW WALL /*/WALLS\nFRMW RETA /*/RETAINING\nFRMW SLAB /*/FLOORS\nFRMW FOOT /*/FOUNDATIONS\nFRMW BASE /*/BASES\nFRMW BEAM /*/BEAMS\nFRMW COLU /*/COLUMNS\nFRMW STAI /*/STAIRS\nFRMW CASE /*/STAIRS\nFRMW RAIL /*/HANDRAILS\nFRMW TOUS /*/FRMW%%\nFRMW LADD /*/LADDERS\nFRMW GRAT /*/GRATINGS\nFRMW META /*/ASSEMBLY%%\nCFLOOR FOOT /*/%%\nCFLOOR SLAB /*/1F%%\nCFLOOR BASE /*/1B%%\nCSCREED SLAB /*/2F/%%\nCSCREED BASE /*/2B/%%\nCWALL RETA /*/%%\nCWALL WALL /*/%%\nSBFR BEAM /*/%%\nSBFR COLU /*/%%\ncontinues ......."}
{"Headers": "PASCATALOGUE", "Content": "The PASCATALOGUE parameter file lists the elements that do not to use the catalog. This file should not be modified. The two elements present are ladders, and spiral stairs.\nGENSEC LADD\nGENSEC SPIR\n\n\n\nPASCATALOGUE\nGENSEC LADD\nGENSEC SPIR"}
{"Headers": "SEPARATESTRUCTURE", "Content": "If the SEPARATESTRUCTURE parameter file exists, structural elements that are owned by sites, other than the site that owns a room, are considered in structural volume and surface area calculations. This increases the time required to perform the calculations so should not be used unless required by the project.\n\n\n\nSEPARATESTRUCTURE"}
{"Headers": "SLOPES", "Content": "The SLOPES parameter file defines how slopes are shown as angles.\n# How slopes are shown\n# # DD 2 = Decimal degrees with 2 figures after decimal point for example. 23.45\n# DMS = Degrees, minutes and seconds for example. 23\u00b045'30\"\n# G 2 = Grades with 2 figures after decimal point for example. 18.63\n# F 1 = mm per metre with 1 figure after decimal point for example. 5.5mm/m\n# P 2 = Percentage with 2 figures after decimal point for example. 18.63%\nP 2\n\n\n\nSLOPES\n# How slopes are shown\n# # DD 2 = Decimal degrees with 2 figures after decimal point for example. 23.45\n# DMS = Degrees, minutes and seconds for example. 23\u00b045'30\"\n# G 2 = Grades with 2 figures after decimal point for example. 18.63\n# F 1 = mm per metre with 1 figure after decimal point for example. 5.5mm/m\n# P 2 = Percentage with 2 figures after decimal point for example. 18.63%\nP 2"}
{"Headers": "VOLUMES", "Content": "The VOLUMES parameter file defines the units to be used for volumes such as concrete or room volumes. If this file cannot be found then project units is used.\n# Format of volumes\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label e.g. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension VOLUME\nDP 0\nENU true\nFraction false\nLabel UNITS\nUnits FOOT\nZeros true\n\n\n\nVOLUMES\n# Format of volumes\n# Denominator Largest denominator for Imperial fractions\n# DP 2 = Number of decimal places for decimal fractions\n# ENU TRUE = Use ENU format when outputting POSITIONS\n# Fraction FALSE = Fractional part output as decimal\n# FtLabel |'| = Label used for feet\n# InchSeparator |.| = Separator between inches and fractions\n# Label General distance label e.g. mm or \"\n# Units MM = Output number in millimetres\n# Zeros TRUE = Leading zeroes are displayed for Imperial units\n#-------------------------------------------------------------\nDenominator 32\nDimension VOLUME\nDP 0\nENU true\nFraction false\nLabel UNITS\nUnits FOOT\nZeros true"}
{"Headers": "Room Manager Parameter Files", "Content": "This is to set radiation levels and this is only applicable to nuclear projects. This optional feature is the only part of the Building Applications that is specific to nuclear.\n\n\n"}
{"Headers": "CLASSIFICATION", "Content": "The classification definition file defines the content of the secondary attributes window, which serves to enter the radio-protection classification. Significant lines start with the # character.\nThe two first lines give the names of the User Defined Attribute (UDA) parameters which store values. These UDAs are no longer used. Following lines give the choice list of proposed values to the user.\n\n----------------------------------------\n-- UDA names for Shut Down values\n----------------------------------------\n#:nrmdddcla_s#:nrmindbio_s#:nrmddcoul_s\n----------------------------------------\n-- UDA names for production values\n----------------------------------------\n#:nrmdddcla_p#:nrmindbio_p#:nrmddcoul_p\n----------------------------------------\n-- Class\nValue\nColour\n----------------------------------------\n#\n0.02A\n#\n0.0002 mSv/h\n# GREEN\n#\n0.25A\n#\n0.0025 mSv/h\n# GREEN\n#\n0.5A\n#\n0.005 mSv/h\n# GREEN\n#\n0.75A\n#\n0.0075 mSv/h\n# GREEN\n#\n1A\n#\n0.01 mSv/h\n# GREEN\n#\n2.5A\n#\n0.025 mSv/h\n# GREEN\n#\n4A\n#\n0.04 mSv/h\n# YELLOW\n#\nB\n#\n0.1 mSv/h\n# YELLOW\n#\n2B\n#\n0.2 mSv/h\n# YELLOW\n#\nC\n#\n1 mSv/h\n# YELLOW\n#\n2C\n#\n2 mSv/h\n# YELLOW\n#\nD\n#\n10 mSv/h\n# ORANGE\n#\n3D\n#\n30 mSv/h\n# ORANGE\n#\nE\n#\n100 mSv/h\n# ORANGE\n#\n3E\n#\n300 mSv/h\n# RED\n#\nF\n#\n1 Sv/h\n# RED\n#\n3F\n#\n3 Sv/h\n# RED\n#\nG\n#\n10 Sv/h\n# RED\n#\n3G\n#\n30 Sv/h\n# RED\n#\nH\n#\n100 Sv/h\n# RED\n#\n3H\n#\n300 Sv/h\n# RED\n#\nI\n#\n1000 Sv/h\n# RED\n#\n3I\n#\n3000 Sv/h\n# RED\n#\nK\n#\n10000 Sv/h\n# RED\n\n\n\n----------------------------------------\n-- UDA names for Shut Down values\n----------------------------------------\n#:nrmdddcla_s#:nrmindbio_s#:nrmddcoul_s\n----------------------------------------\n-- UDA names for production values\n----------------------------------------\n#:nrmdddcla_p#:nrmindbio_p#:nrmddcoul_p\n----------------------------------------\n-- Class\nValue\nColour\n----------------------------------------\n#\n0.02A\n#\n0.0002 mSv/h\n# GREEN\n#\n0.25A\n#\n0.0025 mSv/h\n# GREEN\n#\n0.5A\n#\n0.005 mSv/h\n# GREEN\n#\n0.75A\n#\n0.0075 mSv/h\n# GREEN\n#\n1A\n#\n0.01 mSv/h\n# GREEN\n#\n2.5A\n#\n0.025 mSv/h\n# GREEN\n#\n4A\n#\n0.04 mSv/h\n# YELLOW\n#\nB\n#\n0.1 mSv/h\n# YELLOW\n#\n2B\n#\n0.2 mSv/h\n# YELLOW\n#\nC\n#\n1 mSv/h\n# YELLOW\n#\n2C\n#\n2 mSv/h\n# YELLOW\n#\nD\n#\n10 mSv/h\n# ORANGE\n#\n3D\n#\n30 mSv/h\n# ORANGE\n#\nE\n#\n100 mSv/h\n# ORANGE\n#\n3E\n#\n300 mSv/h\n# RED\n#\nF\n#\n1 Sv/h\n# RED\n#\n3F\n#\n3 Sv/h\n# RED\n#\nG\n#\n10 Sv/h\n# RED\n#\n3G\n#\n30 Sv/h\n# RED\n#\nH\n#\n100 Sv/h\n# RED\n#\n3H\n#\n300 Sv/h\n# RED\n#\nI\n#\n1000 Sv/h\n# RED\n#\n3I\n#\n3000 Sv/h\n# RED\n#\nK\n#\n10000 Sv/h\n# RED"}
{"Headers": "Concrete Quantities Parameter Files", "Content": "The Concrete Quantities Application requires only one parameter file, GENERALITIES which is described below.\n\n\n"}
{"Headers": "GENERALITIES", "Content": "The GENERALITIES parameter file defines conditions of the concrete quantities calculations.\nConditions of the concrete quantities calculation\n# =================================================\n# Definition :\n# >>> Purpose of the concrete site\n# >>> Types of the objects to calculating\n# >>> Material\n# >>> All type of the walls\n# >>> All type of the floors\n# >>> All type of the foots\n# >>> All type of the columns\n# >>> All type of the beams\n# >>> All type of the bases\n# >>> All type of the stairs\n# >>> Volume tolerance of the collection\n# >>> General clause for the opening collection\n# >>> Opening type # >>> Detailed clause for the opening collection\n# ---------------------------------------------------\n#\n# (1) Purpose of the concrete site\n#\n# ---------------------------------------------------\nSITE # purpose eq 'CIV'\n# ---------------------------------------------------\n#\n# (2) Types of the objects to calculating\n# - All object type to calculating\n# - All object type to collecting\n#\n# ---------------------------------------------------\nSITE ZONE STRU FRMW SBFR CFLOOR CSCREE CWALL EXTRU FLOOR SCREED WALL STWALL GWALL\n         GENSEC PANE SCTN EXTRU FLOOR WALL STWALL GWALL GENSEC PANE SCTN\n# ---------------------------------------------------\n#\n# (3) Material\n# Object type + Collection clause\n#\n# ---------------------------------------------------\nSDEN with (SREF of OWNER eq |STD| and PRES eq -100000 and TEMP eq -100000)\n# ---------------------------------------------------\n#\n# (4) All type of the walls\n#\n# ---------------------------------------------------\nSTWALL WALL GWALL\n# ---------------------------------------------------\n#\n# (5) All type of the floors\n#\n# ---------------------------------------------------\nFLOOR # purp of owner eq 'SLAB'\n# ---------------------------------------------------\n#\n# (6) All type of the foots\n#\n# ---------------------------------------------------\nFLOOR # purp of owner eq 'FOOT'\n# ---------------------------------------------------\n# continues \u2026\u2026\u2026\u2026\n\n\n\nGENERALITIES\n# =================================================\n# Definition :\n# >>> Purpose of the concrete site\n# >>> Types of the objects to calculating\n# >>> Material\n# >>> All type of the walls\n# >>> All type of the floors\n# >>> All type of the foots\n# >>> All type of the columns\n# >>> All type of the beams\n# >>> All type of the bases\n# >>> All type of the stairs\n# >>> Volume tolerance of the collection\n# >>> General clause for the opening collection\n# >>> Opening type # >>> Detailed clause for the opening collection\n# ---------------------------------------------------\n#\n# (1) Purpose of the concrete site\n#\n# ---------------------------------------------------\nSITE # purpose eq 'CIV'\n# ---------------------------------------------------\n#\n# (2) Types of the objects to calculating\n# - All object type to calculating\n# - All object type to collecting\n#\n# ---------------------------------------------------\nSITE ZONE STRU FRMW SBFR CFLOOR CSCREE CWALL EXTRU FLOOR SCREED WALL STWALL GWALL\n         GENSEC PANE SCTN EXTRU FLOOR WALL STWALL GWALL GENSEC PANE SCTN\n# ---------------------------------------------------\n#\n# (3) Material\n# Object type + Collection clause\n#\n# ---------------------------------------------------\nSDEN with (SREF of OWNER eq |STD| and PRES eq -100000 and TEMP eq -100000)\n# ---------------------------------------------------\n#\n# (4) All type of the walls\n#\n# ---------------------------------------------------\nSTWALL WALL GWALL\n# ---------------------------------------------------\n#\n# (5) All type of the floors\n#\n# ---------------------------------------------------\nFLOOR # purp of owner eq 'SLAB'\n# ---------------------------------------------------\n#\n# (6) All type of the foots\n#\n# ---------------------------------------------------\nFLOOR # purp of owner eq 'FOOT'\n# ---------------------------------------------------\n# continues \u2026\u2026\u2026\u2026"}
{"Headers": "Catalogs and Specifications", "Content": "When creating catalogues and specifications for Building Applications, several conditions or rules must be followed. These conditions are described here and should be considered when configuring Building Applications.\n\n\n"}
{"Headers": "Positioning of Sub-components", "Content": "To facilitate the positioning of sub-components on the faces of cataloged elements additional P-lines are required on profiles for beams, columns and walls. One P-line is required to define each face of the element.\nThe followings attributes should be set:\n\n\nCCON attribute set to FACE or FACD - depending on whether the face is clockwise or anticlockwise from the edge.\nPURP attribute should be the DKEY of the DATA element that represents the dimension perpendicular to the direction of the pline.\nThe LEVEL of these plines should be 10 to 11.\nIf the PKEY begins with an F the user can easily distinguish it from other p-lines.\nThe PLAXIS of the p-line should be perpendicular to the face.\nCCON attribute set to FACE or FACD - depending on whether the face is clockwise or anticlockwise from the edge.\nCCON attribute set to FACE or FACD - depending on whether the face is clockwise or anticlockwise from the edge.\nPURP attribute should be the DKEY of the DATA element that represents the dimension perpendicular to the direction of the pline.\nPURP attribute should be the DKEY of the DATA element that represents the dimension perpendicular to the direction of the pline.\nThe LEVEL of these plines should be 10 to 11.\nThe LEVEL of these plines should be 10 to 11.\nIf the PKEY begins with an F the user can easily distinguish it from other p-lines.\nIf the PKEY begins with an F the user can easily distinguish it from other p-lines.\nThe PLAXIS of the p-line should be perpendicular to the face.\nThe PLAXIS of the p-line should be perpendicular to the face.\n\n\n\nCCON\nFACE\nFACD\nPURP\nDKEY\nDATA\nLEVEL\n10 to 11\nPKEY\nPLAXIS"}
{"Headers": "Representation Levels for Catalogue Elements", "Content": "Component geometry (cataloged walls, cataloged floors, beams and columns) should be at levels 0 to 20 for anchor spacing checks. Positive and negative geometry for sub-components should be at levels between 0 and 10; only the negatives for representing anchor spacing should be used in the range 10 to 20.\n\n\n"}
{"Headers": "Properties of Wall Profiles", "Content": "Wall elements must have a property (DATA) with a DKEY attribute of HEIG. This property should also be a design parameter. This enables Concrete building Design to adjust the height of walls.\nIf a wall element has a property with a DKEY attribute of HAUT, this is used to taper the wall height.\nThe thickness of a variable thickness wall should be given by the first design parameter, which makes it much easier to determine the wall thickness from embedded parts and holes.\nFor example the parameters for a simple rectangular wall are shown in the following table:\nParameters\nDKEY\nPurpose\nNumber\nUse\nPLOT\nPLOT\nFree\nPlot file\nTHK\nDESP\n1\nThickness\nHEIG\nDESP\nFree\nHeight\nLONG\nDATA\nFree\nLength\nSURF\nDATA\nFree\nFormwork Area (m\u00b2)\nPAIN\nDATA\nFree\nPaint Area (m\u00b2)\nPERI\nDATA\nFree\nPerimeter (m)\nAREA\nDATA\nFree\nCross Sectional Area (m\u00b2)\nDKEY\nPurpose\nNumber\nUse\nPLOT\nPLOT\nFree\nPlot file\nTHK\nDESP\n1\nThickness\nHEIG\nDESP\nFree\nHeight\nLONG\nDATA\nFree\nLength\nSURF\nDATA\nFree\nFormwork Area (m\u00b2)\nPAIN\nDATA\nFree\nPaint Area (m\u00b2)\nPERI\nDATA\nFree\nPerimeter (m)\nAREA\nDATA\nFree\nCross Sectional Area (m\u00b2)\n\nDKEY\nPurpose\nNumber\nUse\nPLOT\nPLOT\nFree\nPlot file\nTHK\nDESP\n1\nThickness\nHEIG\nDESP\nFree\nHeight\nLONG\nDATA\nFree\nLength\nSURF\nDATA\nFree\nFormwork Area (m\u00b2)\nPAIN\nDATA\nFree\nPaint Area (m\u00b2)\nPERI\nDATA\nFree\nPerimeter (m)\nAREA\nDATA\nFree\nCross Sectional Area (m\u00b2)\n\n\n\nParameters"}
{"Headers": "Sub-components", "Content": "To allow the same sub-component across Building Applications, consideration must be given the types of elements that could own the sub-components. The element types are:\nTo make sure the correct rotation of the subcomponent, use 3 PTPOS for each SFIT element. Use P100, P101, and P102 for 3 axes and make sure all geometry positioned relative to these points:\nFor holes, add p-points around the contour with a purpose of HOLE, PBOR for the radius (for curved shapes) and Pdistance equal to the thickness of the component, for example:\nThey are used by the kicker function when tracing a hole with a kicker.\nPdistance ( ATTRIB RPRO PROF )\nPbore (ATTRIB RPRO RADI )\nPurpose HOLE\n\n\n"}
{"Headers": "Specification Components", "Content": "There is a potential requirement for five SPCO elements to point to the same SFIT elements. The component is available for different owner types:\nNormally the concrete sub-components will not be used in Gratings.\n\n\n"}
{"Headers": "Handrailing", "Content": "For the SPRF elements used to model handrail elements, the following DATA elements are required:\nIt is recommended to use the handrailing available in the Everything3D product for a more accurate representation of handrails.\ndkey ANGL purpose DESP for the angle of pitch (Calculated by Concrete Building design)\ndkey POST purpose SPEC Pproperty with SPCO of post e.g.\ndkey ANGL purpose DESP for the angle of pitch (Calculated by Concrete Building design)\ndkey ANGL purpose DESP for the angle of pitch (Calculated by Concrete Building design)\ndkey POST purpose SPEC Pproperty with SPCO of post e.g.\ndkey POST purpose SPEC Pproperty with SPCO of post e.g.\ndkey ESPA Pproperty with post spacing value\ndkey DEGA Pproperty with the distance between ends or direction changes and the first post.\ndkey ESPA Pproperty with post spacing value\ndkey ESPA Pproperty with post spacing value\ndkey DEGA Pproperty with the distance between ends or direction changes and the first post.\ndkey DEGA Pproperty with the distance between ends or direction changes and the first post.\n\n\n"}
{"Headers": "Steel Staircases", "Content": "Additional specifications are required to allow the user to select the profiles for the steel stairs as follows:\nThese SPEC elements can own one or more SPCO elements that point to the available profiles.\nIt is recommended to use the steel stairs available in the Everything3D for a more accurate representation of steel staircases.\nSPEC (with purpose of TRIM) for the profiles available for stair trimmers/stringers\nSPEC (with purpose STEP) for the profiles available for stair treads.\nSPEC (with purpose of TRIM) for the profiles available for stair trimmers/stringers\nSPEC (with purpose of TRIM) for the profiles available for stair trimmers/stringers\nSPEC (with purpose STEP) for the profiles available for stair treads.\nSPEC (with purpose STEP) for the profiles available for stair treads.\n\n\n"}
{"Headers": "Materials", "Content": "SOLI elements should have their purpose attribute set as follows:\nIf the project requires sub-components to have a limited choice of materials then this can be done by setting the MATpurpose of the SPCO element to one of the above purposes. For example if the MATPurpose is set to STEE then only materials with a purpose of STEE will be available.\nTo restrict the material of the sub-component further, create separate SPCO elements for each material and set the matref to be the required material.\nCONC for concrete\nSTEE for steel\nSCRE for screeds\n\n\n"}
{"Headers": "Concrete Building Design", "Content": "The design of the concrete structure for a plant is a highly specialized activity which significantly affects project costs and schedules. It also has a major impact on all other engineering disciplines for the project, which all have to interface with the structure.\nAVEVA Concrete Building Design is a highly productive, specialized product for the design and modification of these complex concrete structures.\nConcrete Building Design operates as an add-on application within AVEVA E3D Design. It provides designers with a highly specialized design environment for their work, whilst giving them access to all of the features and functions of AVEVA E3D Design. The data that the designers create for walls, floors, bases, screeds, drainage channels, penetrations, doorways, anchor plates etc, is stored and managed within the AVEVA E3D Design environment which allows the designers to integrate their work with all the other design disciplines on the project.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAVEVA E3D Design\nAVEVA E3D Design\nAVEVA E3D Design"}
{"Headers": "Assumptions", "Content": "The Concrete Building Design User Guide has been written for users familiar with civil engineering concrete design practices and have prior knowledge of AVEVA E3D Design.\nIt is assumed that:\nUsers have a valid AVEVA E3D Design license and the software has been installed.\nUsers know how to launch the Model module\nThe user is familiar with the basic Graphical User Interface (GUI) features as described in the AVEVA document Getting Started with AVEVA E3D Design.\nUsers are familiar with concrete building design practices.\nUsers have a valid AVEVA E3D Design license and the software has been installed.\nUsers have a valid AVEVA E3D Design license and the software has been installed.\nUsers know how to launch the Model module\nUsers know how to launch the Model module\nThe user is familiar with the basic Graphical User Interface (GUI) features as described in the AVEVA document Getting Started with AVEVA E3D Design.\nThe user is familiar with the basic Graphical User Interface (GUI) features as described in the AVEVA document Getting Started with AVEVA E3D Design.\nUsers are familiar with concrete building design practices.\nUsers are familiar with concrete building design practices.\n\n\n\nConcrete Building Design User Guide\nAVEVA E3D Design\nAVEVA E3D Design\nModel\nAVEVA E3D Design"}
{"Headers": "Hierarchy", "Content": "As with all AVEVA E3D Design applications, all database elements are owned by other elements and must be created in a strict order.\n\n\n\n\nAVEVA E3D Design"}
{"Headers": "Walls", "Content": "Modelling of concrete wall elements follows principles similar to those used to create beams in Building Design. Sub components are supported in wall elements. In addition Building Design supports limited connectivity between wall elements. Subject to the wall type created, walls can be connected to each other, columns, beams, and floor elements.\nIn Building Design a Wall element is owned by a Group element. The wall element is administrative, further dividing the design element data structure. The physical geometry of a wall is provided by:\n\nStraight Wall (STWALL) \u2013 soft type of section.\nCurved Wall (WALL) \u2013 soft type of general section.\nGeneral Wall (GWALL) \u2013 soft type of panel.\nStraight Wall (STWALL) \u2013 soft type of section.\nStraight Wall (STWALL) \u2013 soft type of section.\nCurved Wall (WALL) \u2013 soft type of general section.\nCurved Wall (WALL) \u2013 soft type of general section.\nGeneral Wall (GWALL) \u2013 soft type of panel.\nGeneral Wall (GWALL) \u2013 soft type of panel.\n\n\n"}
{"Headers": "Floors", "Content": "Floor elements in the Building application are created and modified in similar ways to those used in the other AVEVA E3D Design applications such as Plates and Walls and Floors.\nThe Building application supports limited connectivity between floor elements. Floor Slabs can connect to Straight Walls, Columns, and Beams; while Floor Screeds can connect to Floor Slabs.\nReferring to the hierarchy for Floors, the user must create a Floor element (both slab and screed) below an existing Group element. In he hierarchy the Floor Slab elements are a soft type of a Compound Floor (CFLOOR), while Floor Screed elements are a soft type of a Compound Screed (CSCREE).\nBoth Floor Slabs and Floor Screeds are administrative elements, further dividing the data structure used in Building Design.\n\n\n\nFloor\nAVEVA E3D Design\nPlates and Walls and Floors\nBuilding\nsupports limited connectivity between floor elements. Floor Slabs can connect to Straight Walls, Columns, and Beams; while Floor Screeds can connect to Floor Slabs.\nFloor\nGroup\nBuilding Design"}
{"Headers": "Bases", "Content": "Although considered a separate element, concrete bases share many similarities with floors. They can be created with or without screeds and also support the use of sub-components. The hierarchical relationships for bases are shown below:\n\nThe relationships are identical to those of floors; however an additional relationship exists between the base and the supporting floor. Again, the application uses attributes of the compound fitting (COFI) to manage the relationship between the base and the slab.\n\n\n"}
{"Headers": "Columns", "Content": "In Concrete Building Design a Column element is a SBFR.\n\nThe component of a column is a GENSEC.\nThe sub-component of a column is an SBFI.\nA column can be connected to a floor slab using a FITT (1).\n\n\n\nSBFR\nGENSEC\nSBFI"}
{"Headers": "Beams", "Content": "In Concrete Building Design a Beam element is a SBFR.\n\nThe component of a beam is a GENSEC.\nThe sub-component of a beam is an SBFI.\nA beam can be connected to a floor slab using a FITT (1).\n\n\n\nSBFR\nGENSEC\nSBFI"}
{"Headers": "Stairs", "Content": "In Concrete Building Design a Staircase element is a SBFR.\n\nThere are three types of stair component:\nThe two types of flight are never mixed in Concrete Building Design.\nThe concrete flight is a PANE.\nThe landing is a FLOOR. The sub-component of a landing is an SBFI.\nThe steel flight is a STRFLT. Refer to Stair Flight for further information\nThe concrete flight is a PANE.\nThe concrete flight is a PANE.\nThe landing is a FLOOR. The sub-component of a landing is an SBFI.\nThe landing is a FLOOR. The sub-component of a landing is an SBFI.\nThe steel flight is a STRFLT. Refer to Stair Flight for further information\nThe steel flight is a STRFLT. Refer to Stair Flight for further information\n\n\n\nStair Flight\nSBFR\nPANE\nFLOOR\nSBFI\nSTRFLT\nStair Flight"}
{"Headers": "Ladders", "Content": "In Concrete Building Design a Ladder element is a SBFR.\n\nThe component of a ladder is a GENSEC.\n\n\n\nSBFR\nGENSEC"}
{"Headers": "Handrails", "Content": "In Concrete Building Design a Handrail element is a SBFR.\nA HANDRA element represents the handrail within the sub-framework. Refer to Handrails for further information.\n\n\n\nHandrails\nSBFR\nHandrails"}
{"Headers": "Kickers", "Content": "In Concrete Building Design a Kicker element is a WALL.\n\nThe WALL is a sub-component of a floor screed or a floor slab if there is no screed.\n\n\n\nWALL"}
{"Headers": "Floor Gratings", "Content": "In Concrete Building Design a Floor Grating element is a SBFR.\n\nThe grating component is a PANE.\nThe grating sub-component is an SBFI.\n\n\n\nSBFR\nPANE\nSBFI"}
{"Headers": "Create/Modify Element Window", "Content": "All of the tasks that a user would carry out that are associated with the creation or modification of the building elements for the Concrete Building Design application are initiated from the Create Element or Modify Element windows. For example, the Create Building window or the Modify Building window.\nTo open the Create Element or Modify Element windows, on the Building tab, in the Display group, click Properties.\n\nThe Create Element or Modify Element windows allows the user to create, modify and position building elements.\n\n\n\nConcrete Building Design\n\nCreate Building\nModify Building\n\nBuilding\nDisplay\nProperties\n"}
{"Headers": "Default Specification", "Content": "The constructional details of components available from the Concrete Building Design catalogue are determined by the current detailing specification.\n\nAll of the tasks that a user would carry out that are associated with the default specification are initiated from the Section Specification (Default) window.\n\n\n\nSection Specification (Default)"}
{"Headers": "Specification Data", "Content": "Use the Specification Data part of the Section Specification (Default) window to select any of the specifications from the catalogue.\nClick Specification to identify the current specification as the section specification (default).\nFrom the Generic Type drop-down list, select a standard from the list of available standards, once the selection has been carried out the Generic Type part of the window is automatically populated with the generic types from the catalogue.\n\n\n\nSpecification Data\nSection Specification (Default)\nSpecification\nGeneric Type\nGeneric Type"}
{"Headers": "Pline Settings", "Content": "Use the Pline Settings part of the Section Specification (Default) window to modify the Pline Settings, by default the settings are set as NA (neutral axis) (normal choice of justification setting in practice is NA).\nFrom the Justification drop-down list, select the justification from the available list, (justification determines the \u2018Setting out\u2019 position of the Section, that is the axis about which the geometry is offset).\nFrom the Member line drop-down list, select the member line from the available list (determines how sections are shown in wireline views and drawings).\nFrom the Joint Line drop-down list, select the Joint Line from the available list (determines the position of a joint relative to an attached section).\n\n\n\nPline Settings\nSection Specification (Default)\nJustification\nMember line\nJoint Line"}
{"Headers": "Options", "Content": "Use the checkboxes in the Options part of the Section Specification (Default) window to re-trim all attached sections or use as the default profile.\nClick Properties to display the properties of the profile.\nClick Plotfile to display a graphical representation of the profile.\nClick Apply to use these settings as the new default, the current specification is updated.\nClick Cancel to discard any information and close the Section Specification (Default) window.\n\n\n\nOptions\nSection Specification (Default)\nProperties\nPlotfile\nApply\nCancel\nSection Specification (Default)"}
{"Headers": "Building Applications Window", "Content": "All of the tasks that a user would carry out that are associated with the creation or modification of the hierarchy for the Concrete Building Design application are initiated from the Building Applications window.\nDepending on the selection made in the Building Applications window the user will be presented with further windows prompting the user for input. During this time, the Building Applications window is constantly displayed.\nTo open the Building Applications window, on the Building tab, in the Display group, click Browser.\n\nThe Building Applications window is a dual purpose window which allows the user to view the hierarchy and navigate to connected elements.\n\n\n\nConcrete Building Design\nBuilding Applications\nBuilding Applications\nBuilding Applications\nBuilding Applications\nBuilding\nDisplay\nBrowser\nBuilding Applications"}
{"Headers": "Building Element", "Content": "The first task the user should perform using the Building Applications window is to create a Building element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the World element is the CE.\n\nOn the Building tab, in the Create group, by default Building is displayed in the Create Element drop-down list. The user can select the other option available from the drop-down list. Refer to Building by Group of Rooms for further information on the other available option Building by Groups of Rooms.\n\nClick Create Element to display the Create Building window.\n\nBy default in the Naming pane of the Create Building window the application automatically populates the Name field with a name based on the project or company autonaming rules. Refer to Naming for further information on autonaming rules.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which autoname is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this type a new name into the Name field. If this name already exists, the following error window is displayed:\n\nfirst available name, click Use first available name.\nprevious available name, click Use previous available name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nfirst available name, click Use first available name.\nfirst available name, click Use first available name.\nprevious available name, click Use previous available name.\nprevious available name, click Use previous available name.\nnext available name, click Use next available name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nlast available name, click Use last available name.\n\n\n\nBuilding by Group of Rooms\nNaming\nBuilding Applications\nBuilding\nSelect Structural Element\nBuilding Applications\nWorld\nCE\nBuilding\nCreate\nBuilding\nCreate Element\nBuilding by Group of Rooms\nBuilding by Groups of Rooms.\nCreate Element\nCreate Building\nNaming\nCreate Building\nName\nNaming\nUse gaps in naming sequence\nUse first available name\nUse previous available name\nUse next available name\nUse last available name\nName"}
{"Headers": "Position", "Content": "The Position pane of the Create Building window specifies the position of the building element explicitly. Select the directions from the drop-down list, valid directions are East, West, North, South, Up or Down. By default, the position has a direction of Up. Input the coordinates for the building element.\n\nIf required, select one or all of the locks to fix the one or all of the coordinates.\nIf required, the axes to which all co-ordinates are interpreted with respect to must now be set.\nif required, in the wrt field, input the name of the element to which all coordinates are interpreted with respect to. The default is /*, if this is not the case, input the name of the required element.\n\n\n\nPosition\nCreate Building\nEast\nWest\nNorth\nSouth\nUp\nDown\nUp\nwrt\n/*"}
{"Headers": "Orientation", "Content": "The Orientation pane of the Create Building window, allows the user to explicitly orientate the axes (fixed reference lines) of an building element. By default, the Direction is U WRT/* and no Rotation is applied.\n\nUsing the Orientation pane of the Create Building window, the user can choose to orientate the building element with the use of coordinates or by the selection of surfaces or edges in the 3D view.\n\n\n\nOrientation\nCreate Building\nDirection\nU WRT/*\nRotation\nOrientation\nCreate Building"}
{"Headers": "Coordinate Option", "Content": "If required, the axes to which all co-ordinates are interpreted with respect to must now be set.\nif required, in the wrt field, input the name of the element to which all coordinates are interpreted with respect to. The default is U WRT /*, if this is not the case, input the name of the required element.\nIn the Rotation field, input the rotation of the axes of the building element in one of the formats that follow:\n123.25\ndecimal degrees.\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds.\n130G12\ndecimal grades.\n123.25\ndecimal degrees.\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds.\n130G12\ndecimal grades.\n\n123.25\ndecimal degrees.\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds.\n130G12\ndecimal grades.\n\n\n\nwrt\nU WRT /*\nRotation"}
{"Headers": "Selection in 3D View", "Content": "To select an existing edge or surface in the 3D view, from the Orientation pane of the Create Building window, click Pick surface or edge to define direction.\n\nThe user is prompted to \u2018Pick Face or Edge\u2019 in the 3D view, when a surface is selected the direction is set perpendicular to it or when an edge is selected the direction is aligned with the edge.\nTo define the rotation from points picked in the 3D view, from the Orientation pane of the Create Building window, click Rotate angle using two picks.\n\nThe user must select two points in the 3D View to change the rotation via the angle between the two positions and the position of the building.\n\nThe user is prompted to Pick first point to define rotation (Snap) snap: in the 3D view, once the first point has been picked, another prompt is displayed Pick second point to define rotation (Snap) snap:. The angle of rotation is displayed in the Rotation field and a graphical aid line displaying the angle of rotation is shown in the 3D view.\nClick Apply to create the building element. The Modify Building window is displayed and the Building element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Building for further information.\nClick Dismiss to discard any inputs and close the Create Building window.\n\n\n\nModify Building\nOrientation\nCreate Building\nPick surface or edge to define direction\n\u2018Pick Face or Edge\u2019\nOrientation\nCreate Building\nRotate angle using two picks\nPick first point to define rotation (Snap) snap:\nPick second point to define rotation (Snap) snap:\nRotation\nApply\nModify\nBuilding\nBuilding Applications\nModify Building\nDismiss\nCreate Building"}
{"Headers": "Modify Building", "Content": "All the tasks associated with the modification of the building element can be performed from the Modify Building window.\n\nThe user can modify, copy or refresh the Building element.\nClick Apply to create the Building element with modification, Repeat to copy the Building element, Refresh to discard any modifications and display the original attributes or Dismiss to discard any inputs and close the Modify Building window.\n\n\n\nModify Building\nBuilding\nApply\nBuilding\nRepeat\nBuilding\nRefresh\nDismiss\nModify Building"}
{"Headers": "Material Element", "Content": "Referring to the hierarchy, the user must create a Material element below an existing Building element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Building element is the CE.\n\nOn the Building tab, in the Create group, by default Material is displayed in the Create Element drop-down list. Refer to Building by Room for further information on the other available option Building by Room.\n\nClick Create Element to display the Create Material window.\n\nThe application automatically populates the Name field with a name based on the project or company autonaming rules, refer to Naming for further information.\nBy default, the Use gaps in naming sequence checkbox is selected, the user can select which name is to be used. To select the:\nThe user can change the name, to do this, type a new name in the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nFrom the How it is drawn in DRAFT pane of the Create Material window, the user can control the edge representation of physical model elements in the DRAFT module.\nBy default Lines not drawn between touching elements for example, concrete is selected.\nClick Apply to create the Material element. The Modify Material window is displayed and the Material element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Material for further information.\nClick Dismiss to discard any inputs and close the Create Material window.\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nfirst available name, click Use first available name.\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nlast available name, click Use last available name.\nNote:\nThe selection of the edge representation sets the value of the Dunion attribute.\n\n\n\nBuilding by Room\nNaming\nModify Material\nMaterial\nBuilding\nSelect Structural Element\nBuilding Applications\nBuilding\nCE\nBuilding\nCreate\nMaterial\nCreate Element\nBuilding by Room\nBuilding by Room.\nCreate Element\nCreate Material\nName\nNaming\nUse gaps in naming sequence\nUse first available name\nUse previous name\nUse next available name\nUse last available name\nName\nError\nApply\nHow it is drawn in DRAFT\nCreate Material\nDRAFT\nNote:\nLines not drawn between touching elements\nconcrete\nApply\nMaterial\nModify\nMaterial\nMaterial\nBuilding Applications\nModify Material\nDismiss to\nCreate Material"}
{"Headers": "Modify Material", "Content": "All the tasks associated with the modification of the material element can be performed from the Modify Material window.\n\nThe user can modify, copy or refresh the Material element.\nClick Apply to create the Material element with modification, Repeat to copy the Material element, Refresh to discard any modifications and display the original attributes or Dismiss to discard any inputs and close the Modify Material window.\n\n\n\nModify Material\nMaterial\nApply\nMaterial\nRepeat\nMaterial\nRefresh\nDismiss\nModify Material"}
{"Headers": "Level Element", "Content": "The user must create a Level element below an existing Material element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Material element is the CE.\n\nOn the Building tab, in the Create group, by default Level is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Level window.\n\nThe application automatically populates the Name field with a name based on the project or company autonaming rules.\nBy default, the Use gaps in naming sequence checkbox is selected, the user can select which name is to be used. To select the:\nThe user can change the name, to do this, type in a new name in the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nIn Elevation enter the height of the level (default value is zero wrt World). The level proposed is indicated by a cone in the 3D graphical view.\nClick Apply to create the Level element. The Modify Level window is displayed and the Level element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Level Element for further information.\nClick Dismiss to discard any inputs and close the Create Level window.\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nfirst available name, click Use first available name.\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nlast available name, click Use last available name.\n\n\n\nModify Level Element\nLevel\nMaterial\nSelect Structural Element\nBuilding Applications\nMaterial\nCE\nBuilding\nCreate\nLevel\nCreate Element\nCreate Element\nCreate Level\nName\nUse gaps in naming sequence\nUse first available name\nUse previous name\nUse next available name\nUse last available name\nName\nError\nApply\nElevation\nwrt\nApply\nLevel\nModify\nLevel\nLevel\nBuilding Applications\nModify Level Element\nDismiss to\nCreate Level"}
{"Headers": "Modify Level Element", "Content": "All the tasks associated with the modification of the level element can be performed from the Modify Level window.\n\nThe user can modify, copy or refresh the Level element.\nClick Apply to create the Level element with modification, Repeat to copy the Level element, Refresh to discard any modifications and display the original attributes or Dismiss to discard any inputs and close the Modify Level window.\n\n\n\nModify Level\nLevel\nApply\nLevel\nRepeat\nLevel\nRefresh\nDismiss\nModify Level"}
{"Headers": "Group Element", "Content": "The user must create a Group element below an existing Level element.\nThe user can specify from a selection of elements which are in effect the Concrete Building representation of the structural framework elements in the hierarchy.\nWhile the Concrete Design application has a selection of framework elements available for selection, the Group element is most often used as significant structural elements such as columns, beams, floors and walls are usually allocated in their own group.\nThe use of group elements allow the user to limit what elements are used and the location of these elements in the design database.\nRefer to Create Special Structure or Create Assembly Element for further information on a special structure element or assembly element.\n\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Level element is the CE.\n\nOn the Building tab, in the Create group, by default Group is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Group window.\n\nThe application automatically populates the Name field with a name based on the project or company autonaming rules, for further information on the autonaming rules, refer to Naming for further information.\nBy default, the Use gaps in naming sequence checkbox is selected, the user can select which name is to be used. To select the:\nThe user can change the name, to do this, type in a new name in the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nAfter the Group element has been named, the user can specify a default material and purpose for the Group Element.\nThe user can specify from a selection of industry standard materials, from the Default Material drop-down list.\n\nThe selection of a default material is used to calculate the weight and centre of gravity of the element enabling accurate reports to be generated.\nAfter the default material has been selected, the user can specify a purpose for the Group element.\nThe user can specify from a selection of available structural elements, from the Purpose drop-down list.\n\nThe purpose is used to control what types of elements can be created under a Group element.\nClick Apply to create the Group element. The Modify Group window is displayed and the Group element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Group Element for further information.\nClick Dismiss to discard any inputs and close the Create Group window.\nGroup\nSpecial Structure\nAssembly.\nGroup\nGroup\nSpecial Structure\nSpecial Structure\nAssembly.\nAssembly.\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nfirst available name, click Use first available name.\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nlast available name, click Use last available name.\n\n\n\nCreate Special Structure\nCreate Assembly Element\nNaming\nModify Group Element\nGroup\nLevel\nConcrete Design\nGroup\nCreate Special Structure\nCreate Assembly Element\nSelect Structural Element\nBuilding Applications\nLevel\nCE\nBuilding\nCreate\nGroup\nCreate Element\nCreate Element\nCreate Group\nName\nNaming\nUse gaps in naming sequence\nUse first available name\nUse previous name\nUse next available name\nUse last available name\nName\nError\nApply\nGroup\nGroup\nDefault Material\nGroup\nPurpose\nGroup\nApply\nGroup\nModify\nGroup\nGroup\nBuilding Applications\nModify Group Element\nDismiss to\nCreate Group"}
{"Headers": "Modify Group Element", "Content": "All the tasks associated with the modification of the Group element can be performed from the Modify Group window.\n\nThe user can modify, copy or refresh the Group element.\nClick Apply to create the Group element with modification, Repeat to copy the Group element, Refresh to discard any modifications and display the original attributes or Dismiss to discard any inputs and close the Modify Group window.\n\n\n\nGroup\nModify Group\nGroup\nApply\nGroup\nRepeat\nGroup\nRefresh\nDismiss\nModify Group"}
{"Headers": "Create Special Structure", "Content": "All the tasks associated with the creation of an Special Structure element can be performed from the Create Special Structure window.\n\nClick Apply to create the Special Structure element. The Modify Special Structure window is displayed and the Group element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Special Structure for further information.\nClick Dismiss to discard any inputs and close the Create Special Structure window.\n\n\n\nModify Special Structure\nSpecial Structure\nCreate Special Structure\nApply\nSpecial Structure\nModify Special Structure\nGroup\nBuilding Applications\nModify Special Structure\nDismiss to\nCreate Special Structure"}
{"Headers": "Modify Special Structure", "Content": "All the tasks associated with the modification of the special structure element can be performed from the Modify Special Structure window.\n\nThe user can modify, copy or refresh the Special Structure element.\nClick Apply to create the Special Structure element with modification, Repeat to copy the Special Structure element, Refresh to discard any modifications and display the original attributes or Dismiss to discard any inputs and close the Modify Structure window.\n\n\n\nModify Special Structure\nSpecial Structure\nApply\nSpecial Structure\nRepeat\nSpecial Structure\nRefresh\nDismiss\nModify Structure"}
{"Headers": "Create Assembly Element", "Content": "All the tasks associated with the creation of an Assembly element can be performed from the Create Assembly window.\n\nThe user can choose an assembly from a list of assemblies available for selection from the Assembly pane of the Create Assembly window. When the assembly has been selected the Name field is populated.\nClick Apply to create an assembly element or Dismiss to discard any inputs and close the Create Assembly window.\n\n\n\nAssembly\nCreate Assembly\nAssembly\nCreate Assembly\nName\nApply\n\nDismiss\nCreate Assembly"}
{"Headers": "Beams and Columns", "Content": "Beams and Columns elements in the Building application are created and modified in similar ways to those used in the other AVEVA E3D Design applications such as Sections, Plates, Walls and Floors and Stairs Ladders and Handrails.\nThe user must create a Beam or Column element below an existing Group element. In the hierarchy, a beam or column element is a soft type element (building representation) of the structural element called Sub-Frame (SBFR). Refer to Beams and Columns for further information on the Concrete Design hierarchy.\n\nThere are many different beams and columns that can be created, because of this the Building application uses a common layout for the windows that are presented to the user. For the same reason this chapter only includes a detailed description of how to create and modify one specific type of beam and column.\n\n\n\nBeams\nColumns\nBeams\nColumns\nAVEVA E3D Design\nSections\nPlates\nWalls and Floors and Stairs Ladders and Handrails\nBeam\nColumn\nGroup\nSub-Frame (SBFR)\nBeams\nColumns\nConcrete Design\nBuilding"}
{"Headers": "Create Beam", "Content": "Referring to the hierarchy, a beam element must reside below an existing group element with a purpose set to All Beams.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Group element is the CE.\n\nOn the Building tab, in the Create group, by default Beam is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Beam window.\n\nBy default in the Naming pane of the Create Beam window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Default Material drop-down list by default is set to Pyrocrete, the default material can be changed to another suitable material. From the Default Material drop-down list, the user can select from a list of suitable materials.\nIn the Assembly pane of the Create Beam window, by default None is displayed. The user can add the beam to a selected assembly if required. Refer to Create Assemblies for further information.\nClick Apply to create the Beam element. The Modify Beam window is displayed and the Beam element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Beam Element for further information.\nClick Dismiss to discard any inputs and close the Modify Beam window.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nCreate Assemblies\nModify Beam Element\nSelect Structural Element\nBuilding Applications\nGroup\nCE\nBuilding\nCreate\nBeam\nCreate Element\nCreate Element\nCreate Beam\nNaming\nCreate Beam\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nDefault Material\nPyrocrete\nDefault Material\nAssembly\nCreate Beam\nNone\nCreate Assemblies\nApply\nBeam\nModify\nBeam\nBeam\nBuilding Applications\nModify Beam Element\nDismiss to\nModify Beam"}
{"Headers": "Modify Beam Element", "Content": "All the tasks associated with the modification of the beam element can be performed from the Modify Beam window.\n\nThe user can modify, copy or refresh the Beam element with the exception of renaming the beam element. Refer to Create Beam for further information.\nClick Apply to create the Beam element with modification, Repeat to copy the Beam element, Refresh to discard any modifications and display the original attributes or Dismiss to discard any inputs and close the Modify Beam window.\n\n\n\nCreate Beam\nModify Beam\nBeam\nCreate Beam\nApply\nBeam\nRepeat\nBeam\nRefresh\nDismiss\nModify Beam"}
{"Headers": "Straight or Curved Beam Element", "Content": "Referring to the hierarchy for the Beam and Columns, the user must create a component below an existing Beam element, which in this case is a Straight Beam or Curved Beam element.\nIn Concrete Design hierarchy a straight beam or curved beam element are soft type elements (building representations) of structural elements:\n\nStraight Beam - GENSEC\nCurved Beam - GENSEC.\nStraight Beam - GENSEC\nStraight Beam - GENSEC\nCurved Beam - GENSEC.\nCurved Beam - GENSEC.\n\n\n\nBeam\nStraight\nBeam\nCurved Beam\nConcrete Design"}
{"Headers": "Create Straight Beam", "Content": "From the Select Structural Element pane of the Building Applications window, make sure that the Beam element is the CE.\n\nOn the Building tab, in the Create group, by default Straight Beam is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Beam window.\nIn certain projects, it is possible to create non-cataloged beams, for further information, refer to the System Administrator for further information.\nAll the tasks associated with the creation of the straight beam element can be performed from the Create Beam window.\n\nIn the Naming part of the Create Beam window, the application automatically populates the Name field with a name based on the project or company autonaming rules.\nBy default, the Use gaps in naming sequence checkbox is selected, the user can select which name is to be used. To select the:\nThe user can change the name, to do this, type in a new name in the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Material drop-down list by default is set to Pyrocrete, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nTo make sure design consistency and conformity with company standards, the basic definitions of all profiles which the user can use are held in a Catalogue database. The catalogue database is used in other Design applications with other materials and can be used in the Building application. The profiles available from the Catalogue are determined by the Section Specification.\nClick Catalogue, the Section Specification (Default) window is displayed:\n\nBy default the specification select as the Default Profile Specification is used but the user can select an alternative specification from the beam element. for further information on the Default Profile Specification, refer to Default Specification for further information.\nClick Apply to confirm the specification or Cancel to discard any inputs and close the Section Specification (Default) window.\nThe user can also modify the width and height properties of the beam element, from the Create Beam window, click Properties the Modify Properties window is displayed.\n\nThe width and height of the beam element can be input directly in to the Width and Height fields or click Measure Width, the user is prompted to Measure property dimension start (Snap) Snap: and the selection of the start dimension the user is prompted to Measure property dimension end (Snap) Snap:. After the selection in the 3D graphical view the Width measurement field is automatically populated. The height can be automatically populated in the same way, with the exception of the user clicking Measure Height. Click OK to save the properties and close the Modify Properties.\nTo return the width and height back to the default, click Default.\nTo discard any inputs, click Reset.\nTo close the Modify Properties window, click Cancel.\nBy default the Length of new beam element is 5000, but the user can change the Length, input the required length into the Length field.\nMeasure Length, the user is prompted to Measure Length: Pick Start (Snap) Snap: in the 3D graphical view, after the selection has been made the Length field is automatically populated.\nFlip start and end position, the user can reverse the start and end positions of the column.\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nfirst available name, click Use first available name.\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nlast available name, click Use last available name.\n\n\n\nDefault Specification\nSelect Structural Element\nBuilding Applications\nBeam\nCE\nBuilding\nCreate\nStraight Beam\nCreate Element\nCreate Element\nCreate Beam\nCreate Beam\nNaming\nCreate Beam\nName\nUse gaps in naming sequence\nUse first available name\nUse previous name\nUse next available name\nUse last available name\nName\nError\nApply\nMaterial\nPyrocrete\nMaterial\nCatalogue\nBuilding\nCatalogue\nCatalogue\nSection Specification (Default)\nDefault Profile Specification\nDefault Profile Specification\nDefault Specification\nApply\nCancel\nSection Specification (Default)\nCreate Beam\nProperties\nModify Properties\nWidth\nHeight\nMeasure Width\nMeasure property dimension start (Snap) Snap:\nMeasure property dimension end (Snap) Snap:\nWidth measurement\nMeasure Height\nOK\nModify Properties\nDefault\nReset\nModify Properties\nCancel\nLength\nMeasure Length\nMeasure Length: Pick Start (Snap) Snap:\nLength\nFlip start and end position,"}
{"Headers": "Use End Position for Start", "Content": "Once the graphical picks have been made the length between the two selections the Length field and Direction field of the Create Beam window are automatically populated.\n\nTo avoid changing a desired value in a field, select Coordinate unlocked. If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. The length is always calculated between both positions.\n\n\n\nLength\nDirection\nCreate Beam\nCoordinate unlocked"}
{"Headers": "Graphical Pick Start/End", "Content": "By selection of points in the 3D graphical view, the user can determine the start and end positions, orientation and miter direction of an new beam element. The drop-down list by default is set to Graphical Pick Start/End, the user is prompted to Pick Start (Snap) Snap:\nOnce the selection has been made the Start Position pane of the Create Beam window is automatically populated with starting coordinates of the new beam element and the user is prompted to Pick End (Snap) Snap: The End Position pane of the Create Beam window is again automatically populated with ending co-ordinates of the new beam element.\n\n\n\nGraphical Pick Start/End\nPick Start (Snap) Snap:\nStart Position\nCreate Beam\nPick End (Snap) Snap:\nEnd Position\nCreate Beam"}
{"Headers": "Elevation", "Content": "If required, after the selection of the start and end position, the user must pick a position at the required elevation in the 3D graphical view. Select Pick Elevation from the Start Position pane of the Create Beam window, the user is prompted to Pick Start (Snap) Snap: If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. The length is always calculated between both positions. The same process is required for the elevation of the end position of the beam element.\nClick Measure Length to measure the length, the user is prompted to Measure Length:Pick Start (Snap) Snap: once the selection has been made, the user is prompted again Measure Length:Pick End (Snap) Snap:. The Length field is automatically populated, the end position is adjusted to suit the new length.\nIn the Orientation pane of the Create Beam window, the Direction field is automatically populated but the user can input another direction. The end position is adjusted to suit the new direction and the existing length.\nTo pick an edge or surface in the 3D graphical view to define a direction. Click Pick surface or edge to define direction, the user is prompted to Pick Face or Edge: Once the selection has been made, the Direction field is automatically populated.\nTo reverse the direction, click Reverse Direction.\nBy default, the Section Rotation is 0\u00b00\u20190\" but the user can input the Section Rotation in one of the following formats:\ndecimal degrees\ndegrees, minutes and seconds\ndecimal grades.\nThe miter Direction pane of the Create Beam window can be used to establish the miter direction of the Start and Stop positions by default, the miters are perpendicular of the beam and are always shown with respect to the level. The miter is calculated automatically when the direction of the beam is modified. The user can modify each miter.\nInput a direction in the Start field, the direction is always shown with respect to the level or click Pick edge or surface to define direction, the user is prompted to Pick Face or Edge:\nInput a direction in the End field, the direction is always shown with respect to the level or click Pick edge or surface to define direction, the user is prompted to Pick Face or Edge:\n123.25\ndecimal degrees\n123\u00b015\u201905\" or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades.\n123.25\n123.25\n123.25\n123\u00b015\u201905\" or 123d15m05s\n123\u00b015\u201905\" or 123d15m05s\n123\u00b015\u201905\" or 123d15m05s\n130G12\n130G12\n130G12\n\n\n\nPick Elevation\nStart Position\nCreate Beam\nPick Start (Snap) Snap:\nMeasure Length\nMeasure Length:Pick Start (Snap) Snap:\nMeasure Length:Pick End (Snap) Snap:\nLength\nOrientation\nCreate Beam\nDirection\nPick surface or edge to define direction\nPick Face or Edge:\nDirection\nReverse Direction\nSection Rotation\nSection Rotation\nDirection\nCreate Beam\nStart\nPick edge or surface to define direction\nPick Face or Edge:\nEnd\nPick edge or surface to define direction\nPick Face or Edge:"}
{"Headers": "Activating the Connectivity", "Content": "The Building application always attempts to connect elements to other elements. If the user has selected a position on a straight wall, a column or a straight beam with a graphical pick, the beam is automatically connected to the selected element.\nThe name of the connected element is shown with a green background if the connect element is a floor. It is shown with a yellow background if it is a straight wall, column or straight beam.\n\nIf the connectivity is activated, the position and the miter of this end are adjusted.\n\n\n\nBuilding"}
{"Headers": "Validating the Creation of a Straight Beam", "Content": "Click Apply to create the straight beam. The Straight Beam Modification window automatically replaces the Creation window or click Dismiss to discard any inputs and close the Create Beam window.\nOnce the CE is changed, the Create Beam window closes.\n\n\n\nApply\nStraight Beam Modification\nCreation\nDismiss\nCreate Beam\nCreate Beam"}
{"Headers": "Modify Straight Beam", "Content": "All the tasks associated with the modification of the straight beam element can be performed from the Modify Beam window.\n\nThe functionality of this window is identical to the Create Beam window. Refer to Create Beam for further information.\n\n\n\nCreate Beam\nModify Beam\nCreate Beam\nCreate Beam"}
{"Headers": "Create Curved Beam", "Content": "From the Select Structural Element pane of the Building Applications window, make sure that the Beam element is the CE.\n\nOn the Building tab, in the Create group, select Curved Beam in the Create Element drop-down list.\nClick Create Element to display the Create Curved Beam window.\n\nThe functionality of this window is virtually identical to the Create Beam window, with the following exceptions:\nMirror Profile\nSection Rotation\nShape\nRadius\nArc Angle.\nMirror Profile\nMirror Profile\nSection Rotation\nSection Rotation\nShape\nShape\nRadius\nRadius\nArc Angle.\nArc Angle.\n\n\n\nSelect Structural Element\nBuilding Applications\nBeam\nCE\nBuilding\nCreate\nCurved Beam\nCreate Element\nCreate Element\nCreate Curved Beam\nCreate Beam"}
{"Headers": "Mirror Profile", "Content": "The section profile that is applied to the curved beam can be mirrored. By default, the Mirror Profile checkbox is clear, to mirror the section profile select the Mirror Profile checkbox.\n\n\n\nMirror Profile\nMirror Profile"}
{"Headers": "Section Rotation", "Content": "The Section Rotation specifies the rotation angle of the section profile about its justification pline.\n\nBy default the section rotation is 0\u00b00\u20190\u2019\u2019, in Section Rotation enter the rotation angle in one of the following formats:\nDecimal degrees\n123.25\nDegrees, minutes and seconds\n123\u00b015\u201905\u2019\u2019 or 123d15m05s\nDecimal grades\n130G12\nDecimal degrees\n123.25\nDegrees, minutes and seconds\n123\u00b015\u201905\u2019\u2019 or 123d15m05s\nDecimal grades\n130G12\n\nDecimal degrees\n123.25\nDegrees, minutes and seconds\n123\u00b015\u201905\u2019\u2019 or 123d15m05s\nDecimal grades\n130G12\n\n\n\nSection Rotation"}
{"Headers": "Shape", "Content": "Two types of curved beam elements are available for selection by the user:\nSimple Arc\nComplex.\nSimple Arc\nSimple Arc\nComplex.\nComplex.\n\n\n"}
{"Headers": "Single Arc", "Content": "In the Shape drop-down list select from either Single Arc, the single arc option allows the user to create a single-arched shaped beam in an angle range of 0\u00b0 and 360\u00b0.\n\nThe user can pick the position of curves, start points and end points of curved beam elements in the 3D graphical view. From the Create Curved Beam window, from the Shape drop-down list, select:\nGraphical Pick Centre\nPositions the centre of the single arc on an existing element in the design, the user is prompted to Graphical Pick Centre (Snap) WP Snap:\nGraphical Pick Start\nPicks the start of the single arc on an existing element in the design, the user is prompted to Pick Start (Snap) WP Snap: Once the selection has been made the rotation and angle are adjusted for the new start of the curve. If the radius is locked, the start position is adjusted to use the current radius. Otherwise, the end position is adjusted to use the new radius.\nGraphical Pick End\nPicks the end of the single arc on an existing element in the design, the user is prompted to Pick End (Snap) WP Snap: Once the selection has been made the rotation and angle are adjusted for the new end of the curve. If the radius is locked, the end position is adjusted to use the current radius. Otherwise, the start position is adjusted to use the new radius.\nGraphical Pick Arc\nPicks an existing panel vertex (PAVE) to establish the geometry (centre, start, end) of a single arc beam. The user is prompted to Pick PAVE:\nNote:\nThe Graphically Pick Arc requires the PAVE to have a radius greater than or equal to half the profile width for the geometry to display. If the radius is smaller, then the geometry is rendered invalid and is not displayed.\n\n\n\nShape\nSingle Arc\nCreate Curved Beam\nShape\nGraphical Pick Centre\nGraphical Pick Centre (Snap) WP Snap:\nGraphical Pick Start\nPick Start (Snap) WP Snap:\nGraphical Pick End\nPick End (Snap) WP Snap:\nGraphical Pick Arc\nPick PAVE:\nNote:\nGraphically Pick Arc"}
{"Headers": "Radius", "Content": "If graphical pick functionality is not required, for example: precise dimensions have to be entered. The user can enter the dimensions into the Radius and Arc Angle fields from the Create Curved Beam window.\nThe Radius textbox displays the radius of single-arced shaped beam. To lock or unlock the radius value click Radius locked.\nThe radius value can be set by:\nThe Arc Angle textbox displays the arc angle of a single arc shaped beam ranging from 0\u2011360 degrees. To populate it, type a value for the arc angle then press Enter. Arc angles can be entered in any of the following formats:\n123.25\n123\u00b015\u201905\u2019\u2019 or 123d15m05s\n130G12\nAlternatively, click Pick Arc Angle to invoke the Positioning Control window, allowing the user to make graphical selections of existing elements to establish the arc angle.\nThe Position section of the window is used to establish the centre position of a single-arced shaped beam. It can be populated several ways:\nThe wrt (with respect to) textbox displays the element name to which the start position co\u2011ordinates are positioned to.\nThe Orientation section of the window is used to establish the Direction and Rotation angle of the beam.\nThe Direction textbox displays the direction of the beam (defined from the start to the end positions).\nThe direction may be changed using a number of methods. The direction can be re\u2011established by typing a new direction (for example: U, N, N45E, S30W15D) then click Enter.\nTwo other methods can be used to set the direction of the beam.\nThe Pick surface or edge to define direction allows the user to graphically pick the face or edge of an existing element.\nThe Rotation textbox displays the rotation angle of the curved beam. To populate it type a value for the Rotation angle then click Enter. Rotation angles can be entered in the same formats as Arc Angles.\nAlternatively, click Rotate angle using two picks to invoke the Positioning Control window, allowing the user to make graphical selections of existing elements to establish the rotation angle.\nDecimal degrees\n123.25\nDegrees, minutes and seconds\n123\u00b015\u201905\u2019\u2019 or 123d15m05s\nDecimal grades\n130G12\nTyping a radius and clicking Enter.\nClicking Measure Length and graphically selecting existing elements to establish the radius.\nTyping a radius and clicking Enter.\nTyping a radius and clicking Enter.\nClicking Measure Length and graphically selecting existing elements to establish the radius.\nClicking Measure Length and graphically selecting existing elements to establish the radius.\nDecimal degrees\nDecimal degrees\nDecimal degrees\nDegrees, minutes and seconds\nDegrees, minutes and seconds\nDegrees, minutes and seconds\nDecimal grades\nDecimal grades\nDecimal grades\nEstablish the correct direction from the option lists and type the co-ordinates.\nClick Graphical Pick Start to invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nClick Pick Elevation to invoke the Positioning Control window to graphically pick an existing element to establish the up/down co-ordinate.\nEstablish the correct direction from the option lists and type the co-ordinates.\nEstablish the correct direction from the option lists and type the co-ordinates.\nClick Graphical Pick Start to invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nClick Graphical Pick Start to invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nClick Pick Elevation to invoke the Positioning Control window to graphically pick an existing element to establish the up/down co-ordinate.\nClick Pick Elevation to invoke the Positioning Control window to graphically pick an existing element to establish the up/down co-ordinate.\nNote:\nThe start of the arc remains stationary while the picked point projects an invisible line to the centre of the arc and the end of the arc snaps to this line thus creating the arc angle.\n\n\n\nRadius\nArc Angle\nCreate Curved Beam\nNote:"}
{"Headers": "Complex Curve", "Content": "To define a complex curve, the 2D Editor must be run using the Shape drop-down list. The curved beam is created and the Modification window replaces the Creation window.\n\n\n\n\n2D Editor\nShape\nModification\nCreation"}
{"Headers": "Confirm the Creation of the Curved Beam", "Content": "Click Apply to create the curved beam. The curved beam Modification window replaces the Creation window. If the option is greyed out, enter a valid name in the Name field to activate it.\nTo cancel the creation of the curved beam, click Dismiss. If the user navigates to another element, the window closes automatically.\nNote:\nIt is also possible to create a curved beam with AVEVA E3D Design using the Sections application. On the Sections tab, in the Create group, click Curved.\n\n\n\nApply\ncurved beam Modification\nCreation\nName\nDismiss\nNote:\nAVEVA E3D Design\nSections\nSections\nCreate\nCurved"}
{"Headers": "Activate the Connectivity", "Content": "If the end of the beam proposed is in the same position as another end and the connectivity is activated, the miter of both ends is adjusted.\n\n\n\n"}
{"Headers": "Modify Curved Beam", "Content": "All the tasks associated with the modification of the curved beam element can be performed from the Modify Curved Beam window.\n\nThe material, section, position, orientation and miters can be modified in the same way as these options were selected in the Create Curved Beam window. The section can be modified the same way as for a straight beam.\nIf the connectivity is activated, the position and miters of the ends are adjusted.\nTo confirm the modification, click Apply.\nTo create a new curved beam component with the same parameters, click Repeat.\nTo close the window, click Dismiss.\nClick Refresh to discard any modifications and display the original attributes.\n\n\n\nModify Curved Beam\nCreate Curved Beam\nApply\nRepeat\nDismiss\nRefresh"}
{"Headers": "Create Column", "Content": "Referring to the hierarchy, a column element must reside below an existing group element with a purpose set to All Columns.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Group element is the CE.\n\nOn the Building tab, in the Create group, by default Column is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Column window.\n\nBy default in the Naming pane of the Create Column window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Default Material drop-down list by default is set to Pyrocrete, the default material can be changed to another suitable material. From the Default Material drop-down list, the user can select from a list of suitable materials.\nIn the Assembly pane of the Create Column window, by default None is displayed. The user can add the column to a selected assembly if required. Refer to Create Assemblies for further information.\nClick Apply to create the Column element. The Modify Column window is displayed and the Column element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Column Element for further information.\nClick Dismiss to discard any inputs and close the Create Column window.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nCreate Assemblies\nModify Column Element\nSelect Structural Element\nBuilding Applications\nGroup\nCE\nBuilding\nCreate\nColumn\nCreate Element\nCreate Element\nCreate Column\nNaming\nCreate Column\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nDefault Material\nPyrocrete\nDefault Material\nAssembly\nCreate Column\nNone\nCreate Assemblies\nApply\nColumn\nModify\nColumn\nColumn\nBuilding Applications\nModify Column Element\nDismiss to\nCreate Column"}
{"Headers": "Modify Column Element", "Content": "All the tasks associated with the modification of the column element can be performed from the Modify Column window.\n\nThe user can modify, copy or refresh the Column element with the exception of renaming the column element. Refer to Create Column for further information.\nClick Apply to create the Column element with modification, Repeat to create a new curved beam component with the same parameters, Refresh to discard any modifications and display the original attributes or Dismiss to discard any inputs and close the Modify Column window.\n\n\n\nCreate Column\nModify Column\nColumn\nCreate Column\nApply\nColumn\nRepeat\nRefresh\nDismiss\nModify Column"}
{"Headers": "Create Column Component", "Content": "Referring to the hierarchy for the Beam and Columns, the user must create a Component.\nThe physical geometry of a column is provided by a Component element which is a soft type of a Section (GENSEC). Component elements are owned by the Column element.\n\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Column element is the CE.\n\nOn the Building tab, in the Create group, by default Component is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Column window.\nIn certain projects, it is possible to create non-catalogued columns, for further information, refer to the System Administrator for further information.\n\nIn the Naming part of the Create Column window, the application automatically populates the Name field with a name based on the project or company autonaming rules.\nBy default, the Use gaps in naming sequence checkbox is selected, the user can select which name is to be used. To select the:\nThe user can change the name, to do this, type in a new name in the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Material drop-down list by default is set to Pyrocrete, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nTo make sure design consistency and conformity with company standards, the basic definitions of all profiles which the user can use are held in a Catalogue database. The catalogue database is used in other Design applications with other materials and can be used in the Building application. The profiles available from the Catalogue are determined by the Section Specification.\nClick Catalogue, the Section Specification (Default) window is displayed:\n\nBy default the default profile specification is selected but the user can select an alternative specification for the column element. for further information on the Default Profile Specification, refer to Default Specification for further information.\nClick Apply to confirm the specification or Cancel to discard any inputs and close the Section Specification (Default) window.\nThe user can also modify the width and height properties of the column element, from the Create Column window, click Properties and the Modify Properties window is displayed.\n\nThe width and height of the column element can be input directly in to the Width and Height fields or click Measure Width, the user is prompted to Measure property dimension start (Snap) Snap: and the selection of the start dimension the user is prompted to Measure property dimension end (Snap) Snap:. After the selection in the 3D graphical view the Width measurement field is automatically populated. The height can be automatically populated in the same way, with the exception of the user clicking Measure Height. Click OK to save the properties and close the Modify Properties.\nTo return the width and height back to the default, click Default.\nTo discard any inputs, click Reset.\nTo close the Modify Properties window, click Cancel.\nBy default the Height of new column element is 5000, but the user can change the Height, input the required height into the Height field.\nMeasure Height, the user is prompted to Measure Height: Pick Start (Snap) Snap: in the 3D graphical view, after the selection has been made the Height field is automatically populated.\nClick Flip start and end position to reverse the start and end positions of the column.\nClick Use end position for start to set the end position of the previously created column as the start position of the current column.\n\nSelect Move Graphically from the option list to invoke the Positioning Control window and allows the user to graphically select an existing element to move the column\u2019s start position to.\nSelect Graphical Pick Start/End from the option list to invoke the Positioning Control window and allows the user to make two graphical selections to establish the start and end of the column.\nThe Start Position section of the window is used to establish the start position of the column. It can be populated several ways:\nThe wrt textbox displays the element name that the start position co-ordinates are positioned with respect to.\nThe End Position section of the window is used to establish the end position of the column. It can be populated using any of the methods used to establish the start position of the column.\nThe Orientation section of the window is used to establish the Direction and Section Rotation angle of the column. The Direction textbox displays the direction of the column (defined from the start to the end positions) and considering columns are vertical in nature, the default direction is set to U WRT /Level_name. By default, the direction is locked and is indicated by the lock.\nThe direction may be changed using a number of methods. If text entry is to be used, the Direction field must first be unlocked, click to unlock. The direction can be re-established by typing a new direction (for example: U, N, N45E, S30W15D) then clicking Enter.\nTwo other methods can be used to set the direction of the column. Click Pick surface or edge to define direction to graphically pick the face or edge of an existing element. It is not necessary to unlock the Direction field using this method.\nAlternatively, select Reverse Direction which changes the column direction by 180 degrees. The method can also be used whether the direction is locked or unlocked.\nThe Section Rotation textbox displays the rotation angle of the section and may be populated by typing the appropriate angle and clicking Enter. Rotation angles can be entered in any of the following formats:\ndecimal degrees\ndegrees, minutes and seconds\ndecimal grades\nThe miter Direction pane of the Create Column window can be used to establish the miter direction of the Start and Stop positions by default, the miters are perpendicular to the column and are always shown with respect to the level. The miter is calculated automatically when the direction of the column is modified. The user can modify each miter:\nInput a direction in the Start field, the direction is always shown with respect to the level or click Pick edge or surface to define direction, the user is prompted to Pick Face or Edge in the 3D graphical view.\nInput a direction in the End field, the direction is always shown with respect to the level or click Pick edge or surface to define direction, the user is prompted to Pick Face or Edge in the 3D graphical view.\n123.25\ndecimal degrees\n123\u00b015\u201905\" or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nfirst available name, click Use first available name.\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nlast available name, click Use last available name.\nEstablish the correct direction from the option lists and type the coordinates.\nClick Graphical Pick Start invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nClick Pick Elevation to invoke the Positioning Control window to graphically pick an existing element to establish the up/down co-ordinate.\nEstablish the correct direction from the option lists and type the coordinates.\nEstablish the correct direction from the option lists and type the coordinates.\nClick Graphical Pick Start invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nClick Graphical Pick Start invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nClick Pick Elevation to invoke the Positioning Control window to graphically pick an existing element to establish the up/down co-ordinate.\nClick Pick Elevation to invoke the Positioning Control window to graphically pick an existing element to establish the up/down co-ordinate.\n123.25\n123.25\n123.25\n123\u00b015\u201905\" or 123d15m05s\n123\u00b015\u201905\" or 123d15m05s\n123\u00b015\u201905\" or 123d15m05s\n130G12\n130G12\n130G12\n\n\n\nDefault Specification\nSelect Structural Element\nBuilding Applications\nColumn\nCE\nBuilding\nCreate\nComponent\nCreate Element\nCreate Element\nCreate Column\nNaming\nCreate Column\nName\nUse gaps in naming sequence\nUse first available name\nUse previous name\nUse next available name\nUse last available name\nName\nError\nApply\nMaterial\nPyrocrete\nMaterial\nCatalogue\nBuilding\nCatalogue\nCatalogue\nSection Specification (Default)\nDefault Profile Specification\nDefault Specification\nApply\nCancel\nSection Specification (Default)\nCreate Column\nProperties and\nModify Properties\nWidth\nHeight\nMeasure Width\nMeasure property dimension start (Snap) Snap:\nMeasure property dimension end (Snap) Snap:\nWidth measurement\nMeasure Height\nOK\nModify Properties\nDefault\nReset\nModify Properties\nCancel\nHeight\nMeasure Height\nMeasure Height: Pick Start (Snap) Snap:\nHeight\nDirection\nDirection\nDirection\nCreate Column\nStart\nPick edge or surface to define direction\nPick Face or Edge\nEnd\nPick edge or surface to define direction\nPick Face or Edge"}
{"Headers": "Activating the Connectivity", "Content": "The Building application always attempts to connect elements to other elements. If the user has selected a position on a floor or a straight beam with a graphical pick, the column is automatically connected to the selected element.\nThe name of the connected element is shown with a green background if the connect element is a floor. It is shown with a yellow background if it is a straight wall, column or straight beam.\n\nIf the connectivity is activated, the position and the miter of this end are adjusted.\n\n\n\nBuilding"}
{"Headers": "Validating the Creation of a Column", "Content": "Click Apply to create the column. The Modify Column window automatically replaces the Creation window or click Dismiss to discard any inputs and close the Create Column window.\nOnce the CE is changed, the Create Column window automatically closes.\n\n\n\nApply\nModify Column\nCreation\nDismiss\nCreate Column\nCreate Column"}
{"Headers": "Modify Column Component", "Content": "All the tasks associated with the modification of the column component element can be performed from the Modify Column window.\n\nThe functionality of this window is identical to the Create Column window and is used in the same way as for the modification of a straight beam. Refer to Create Column for further information.\n\n\n\nCreate Column\nModify Column\nCreate Column\nCreate Column"}
{"Headers": "Modify the Properties of a Beam or Column", "Content": "To modify the properties of a beam or column, navigate to the element which is to be modified and display the Properties window. Refer to Properties for further information.\n\n\n\n\nProperties\nProperties\nProperties"}
{"Headers": "Splitting Beams and Columns", "Content": "To split a beam into two beams or a column into two columns, refer to the Split Section, Panel or Bounded Plate for further information.\n\n\n\nSplit Section, Panel or Bounded Plate\nSplit Section, Panel or Bounded Plate"}
{"Headers": "Connectivity Menu", "Content": "To use the options available for selection from the Connectivity menu, refer to the Connect Sections or Disconnect Sections for further information.\n\n\n\nConnect Sections\nDisconnect Sections\nConnectivity\nConnect Sections\nDisconnect Sections"}
{"Headers": "Copy Connected Beams with Regular Spacings", "Content": "Connected beams can be copied along a specified axis using a specified number of copies and a spacing value between each copy. Refer to the Multiple Copy and Paste for further information.\n\n\n\nMultiple Copy and Paste\nMultiple Copy and Paste"}
{"Headers": "Create Floor Slab", "Content": "Referring to the hierarchy, a floor slab element must reside below an existing group element with a purpose set to All Floors.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Group element is the CE.\n\nOn the Building tab, in the Create group, by default Floor Slab is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Floor Slab window.\n\nBy default in the Naming pane of the Create Floor Slab window, the application automatically populates the Name field with a name based on the project or company autonaming rules. Refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Default Material drop-down list by default is set to Pyrocrete, the default material can be changed to another suitable material. From the Default Material drop-down list, the user can select from a list of suitable materials.\nIn the Assembly pane of the Create Floor Slab window, by default None is displayed. The user can add the floor slab to a selected assembly if required. Refer to Create Assemblies for further information.\nClick Apply to create the Floor Slab element. The Modify Floor Slab window is displayed and the Floor Slab element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Floor Slab Element for further information.\nClick Dismiss to discard any inputs and close the Modify Floor Slab window.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nCreate Assemblies\nModify Floor Slab Element\nSelect Structural Element\nBuilding Applications\nGroup\nCE\nBuilding\nCreate\nFloor Slab\nCreate Element\nCreate Element\nCreate Floor Slab\nNaming\nCreate Floor Slab\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nDefault Material\nPyrocrete\nDefault Material\nAssembly\nCreate Floor Slab\nNone\nCreate Assemblies\nApply\nFloor Slab\nModify\nFloor Slab\nFloor Slab\nBuilding Applications\nModify Floor Slab Element\nDismiss\n\nModify Floor Slab"}
{"Headers": "Modify Floor Slab Element", "Content": "All the tasks associated with the modification of the floor slab element can be performed from the Modify Floor Slab window.\n\nThe user can modify, copy or refresh the Floor Slab element with the exception of renaming the floor slab element. Refer to Create Floor Slab for further information.\nClick Apply to create the Floor Slab element with modification, Repeat to create a new floor slab element with the same parameters, Refresh to discard any modifications and display the original attributes or Dismiss to discard any inputs and close the Modify Floor Slab window.\n\n\n\nCreate Floor Slab\nModify Floor Slab\nFloor Slab\nCreate Floor Slab\nApply\nFloor Slab\nRepeat\nRefresh\nDismiss\nModify Floor Slab"}
{"Headers": "Create Floor Screed", "Content": "Referring to the hierarchy, a floor screed element must reside below an existing group element with a purpose set to All Floors.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Group element is the CE.\n\nOn the Building tab, in the Create group, select Floor Screed in the Create Element drop-down list.\nClick Create Element to display the Create Floor Screed window.\n\nBy default in the Naming pane of the Create Floor Screed window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Default Material drop-down list by default is set to C20/25 Screed, the default material can be changed to another suitable material. From the Default Material drop-down list, the user can select from a list of suitable materials.\nIn the Assembly pane of the Create Floor Screed window, by default None is displayed. The user can add the floor slab to a selected assembly if required. Refer to Create Assemblies for further information.\nClick Apply to create the Floor Screed element. The Modify Floor Screed window is displayed and the Floor Screed element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Floor Screed Element for further information.\nClick Dismiss to discard any inputs and close the Modify Floor Screed window.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nCreate Assemblies\nModify Floor Screed Element\nSelect Structural Element\nBuilding Applications\nGroup\nCE\nBuilding\nCreate\nFloor Screed\nCreate Element\nCreate Element\nCreate Floor Screed\nNaming\nCreate Floor Screed\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nDefault Material\nC20/25 Screed\nDefault Material\nAssembly\nCreate Floor Screed\nNone\nCreate Assemblies\nApply\nFloor Screed\nModify\nFloor Screed\nFloor Screed\nBuilding Applications\nModify Floor Screed Element\nDismiss to\nModify Floor Screed"}
{"Headers": "Modify Floor Screed Element", "Content": "All the tasks associated with the modification of the floor screed element can be performed from the Modify Floor Screed window.\n\nThe user can modify, copy or refresh the Floor Screed element with the exception of renaming the floor screed element. Refer to Create Floor Screed for further information.\nClick Apply to create the Floor Screed element with modification, Repeat to create a new floor screed element with the same parameters, Refresh to discard any modifications and display the original attributes or Dismiss to discard any inputs and close the Modify Floor Screed window.\n\n\n\nCreate Floor Screed\nModify Floor Screed\nFloor Screed\nCreate Floor Screed\nApply\nFloor Screed\nRepeat\nRefresh\nDismiss\nModify Floor Screed"}
{"Headers": "Create Floor Slab + Screed Component", "Content": "Referring to the hierarchy, a slab + screed element must reside below an existing floor slab element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Floor Slab element is the CE.\n\nOn the Building tab, in the Create group, by default Slab + Screed is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Slab + Screed window.\n\nIn the Naming part of the Create Slab + Screed window, the application automatically populates the Name field with a name based on the project or company autonaming rules.\nBy default, the Use gaps in naming sequence checkbox is selected, the user can select which name is to be used. To select the:\nThe user can change the name, to do this, type in a new name in the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Screed Material drop-down list by default is set to None, the screed material can be changed to another suitable material. From the Screed Material drop-down list, the user can select from a list of suitable materials.\nThe Slab Material drop-down list by default is set to Pyrocrete, the material can be changed to another suitable material. From the Slab Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight. The density of the material selected is shown in a tooltip.\nThe Screed Thickness and Slab Thickness can be populated in several ways:\nThe Position section of the window is used to establish the centre position of the slab. It can be populated several ways:\nThe default position is at the origin of the level. By default, the position is the origin of the slab. For rectangular and circular shapes, the origin is at the centre. To select a reference point to position the slab click the Reference drop-down list.\nThe Orientation section of the window is used to establish the Direction and Rotation angle of the slab.\nThe Direction textbox displays the direction of the slab (defined from the start to the end positions).\nThe direction may be changed using a number of methods.\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nfirst available name, click Use first available name.\nfirst available name, click Use first available name.\nprevious available name, click Use previous name.\nprevious available name, click Use previous name.\nnext available name, click Use next available name.\nnext available name, click Use next available name.\nlast available name, click Use last available name.\nlast available name, click Use last available name.\nEnter the absolute finished level (wrt World) in the Top Level field.\nSelect the top level, click Pick Screed Level. The Positioning Control window is displayed. Follow the prompt Pick Top Level (Snap) Snap: and select the top level in the graphical view.\nEnter the finished thickness in the Screed Thickness field. If the thickness is locked, click Other level changes to suit thickness to unlock it.\nClick Measure Height to measure the screed thickness. The user is prompted to Height:Pick Start (Snap) Snap:, Height:Pick Start (Snap) Snap: and select two graphical picks.\nEnter the absolute slab level (with respect to the world) in the Slab Level field.\nSelect the slab level using a position in the graphical view and click Pick Slab Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the slab level in the graphical view.\nEnter the slab thickness in the Slab Thickness field. If the thickness is locked, click Other level changes to suit thickness to unlock it.\nClick Measure Height to measure the slab thickness. The user is prompted to Height:Pick Start (Snap)Snap:, Height:Pick Start (Snap) Snap: and select two graphical picks.\nEnter the absolute bottom level (wrt World) in the Bottom Level field.\nSelect the bottom level, click Pick Bottom Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the bottom level in the graphical view.\nIf the user does not want the thickness to adapt to level changes, click Thickness changes to suit levels to lock the thickness.\nThe default finished level is zero with respect to the level. The default screed thickness is zero. The default slab thickness is 300.\nEnter the absolute finished level (wrt World) in the Top Level field.\nEnter the absolute finished level (wrt World) in the Top Level field.\nSelect the top level, click Pick Screed Level. The Positioning Control window is displayed. Follow the prompt Pick Top Level (Snap) Snap: and select the top level in the graphical view.\nSelect the top level, click Pick Screed Level. The Positioning Control window is displayed. Follow the prompt Pick Top Level (Snap) Snap: and select the top level in the graphical view.\nEnter the finished thickness in the Screed Thickness field. If the thickness is locked, click Other level changes to suit thickness to unlock it.\nEnter the finished thickness in the Screed Thickness field. If the thickness is locked, click Other level changes to suit thickness to unlock it.\nClick Measure Height to measure the screed thickness. The user is prompted to Height:Pick Start (Snap) Snap:, Height:Pick Start (Snap) Snap: and select two graphical picks.\nClick Measure Height to measure the screed thickness. The user is prompted to Height:Pick Start (Snap) Snap:, Height:Pick Start (Snap) Snap: and select two graphical picks.\nEnter the absolute slab level (with respect to the world) in the Slab Level field.\nEnter the absolute slab level (with respect to the world) in the Slab Level field.\nSelect the slab level using a position in the graphical view and click Pick Slab Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the slab level in the graphical view.\nSelect the slab level using a position in the graphical view and click Pick Slab Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the slab level in the graphical view.\nEnter the slab thickness in the Slab Thickness field. If the thickness is locked, click Other level changes to suit thickness to unlock it.\nEnter the slab thickness in the Slab Thickness field. If the thickness is locked, click Other level changes to suit thickness to unlock it.\nClick Measure Height to measure the slab thickness. The user is prompted to Height:Pick Start (Snap)Snap:, Height:Pick Start (Snap) Snap: and select two graphical picks.\nClick Measure Height to measure the slab thickness. The user is prompted to Height:Pick Start (Snap)Snap:, Height:Pick Start (Snap) Snap: and select two graphical picks.\nEnter the absolute bottom level (wrt World) in the Bottom Level field.\nEnter the absolute bottom level (wrt World) in the Bottom Level field.\nSelect the bottom level, click Pick Bottom Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the bottom level in the graphical view.\nSelect the bottom level, click Pick Bottom Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the bottom level in the graphical view.\nIf the user does not want the thickness to adapt to level changes, click Thickness changes to suit levels to lock the thickness.\nIf the user does not want the thickness to adapt to level changes, click Thickness changes to suit levels to lock the thickness.\nThe default finished level is zero with respect to the level. The default screed thickness is zero. The default slab thickness is 300.\nThe default finished level is zero with respect to the level. The default screed thickness is zero. The default slab thickness is 300.\nEnter the values in the fields for east, north and up in the Position frame. The reference can be changed by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it.\nSelect the position in the graphical view using Select Structural Element in the Position frame. To avoid changing a desired value in a field, click Coordinates unlocked to lock it.\nEnter the values in the fields for east, north and up in the Position frame. The reference can be changed by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it.\nEnter the values in the fields for east, north and up in the Position frame. The reference can be changed by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it.\nSelect the position in the graphical view using Select Structural Element in the Position frame. To avoid changing a desired value in a field, click Coordinates unlocked to lock it.\nSelect the position in the graphical view using Select Structural Element in the Position frame. To avoid changing a desired value in a field, click Coordinates unlocked to lock it.\nThe direction can be re-established by typing a new direction (for example: U, N, N45E, S30W15D) then click Enter.\nClicking Pick surface or edge to define direction allows the user to select an existing edge or surface in the model. Where a surface is selected then direction is set perpendicular to it. Where an edge is selected the direction is aligned with the edge.\nClick Rotate angle using two picks the user is prompted to Pick first point to define rotation, Pick second point to define rotation to graphically pick the rotation angle using the Positioning Control window. Two graphical picks are required. A graphical aid line is displayed showing the angle of rotation created by the picks. Alternatively the user can type in an angle using a format of degrees, minutes, and seconds.\nThe direction can be re-established by typing a new direction (for example: U, N, N45E, S30W15D) then click Enter.\nThe direction can be re-established by typing a new direction (for example: U, N, N45E, S30W15D) then click Enter.\nClicking Pick surface or edge to define direction allows the user to select an existing edge or surface in the model. Where a surface is selected then direction is set perpendicular to it. Where an edge is selected the direction is aligned with the edge.\nClicking Pick surface or edge to define direction allows the user to select an existing edge or surface in the model. Where a surface is selected then direction is set perpendicular to it. Where an edge is selected the direction is aligned with the edge.\nClick Rotate angle using two picks the user is prompted to Pick first point to define rotation, Pick second point to define rotation to graphically pick the rotation angle using the Positioning Control window. Two graphical picks are required. A graphical aid line is displayed showing the angle of rotation created by the picks. Alternatively the user can type in an angle using a format of degrees, minutes, and seconds.\nClick Rotate angle using two picks the user is prompted to Pick first point to define rotation, Pick second point to define rotation to graphically pick the rotation angle using the Positioning Control window. Two graphical picks are required. A graphical aid line is displayed showing the angle of rotation created by the picks. Alternatively the user can type in an angle using a format of degrees, minutes, and seconds.\n\n\n\nSelect Structural Element\nBuilding Applications\nFloor Slab\nCE\nBuilding\nCreate\nSlab + Screed\nCreate Element\nCreate Element\nCreate Slab + Screed\nNaming\nCreate Slab + Screed\nName\nUse gaps in naming sequence\nUse first available name\nUse previous name\nUse next available name.\nUse last available name\nName\nError\nApply\nScreed Material\nNone\nScreed Material\nSlab Material\nPyrocrete\nSlab Material\nwrt\nPositioning Control\nScreed Thickness\nSlab Level\nPositioning Control\nSlab Thickness\nwrt\nPositioning Control\nThe Position section of the window is used to establish the centre position of the slab. It can be populated several ways:\nPosition\nWrt\nPosition\nReference drop-down\nThe Orientation section of the window is used to establish the Direction and Rotation angle of the slab.\nThe Direction textbox displays the direction of the slab (defined from the start to the end positions).\nThe direction may be changed using a number of methods.\nThe direction can be re-established by typing a new direction (for example: U, N, N45E, S30W15D) then click Enter.\nPick surface or edge to define direction\nClick Rotate angle using two picks"}
{"Headers": "Select the Shape", "Content": "Select the shape using the Shape drop-down list.\nTo specify a rectangular shape, select the Rectangular option. To define the length and width:\nTo specify a circular shape, select the Circular option. To define the diameter:\nTo define a complex shape, initiate the 2D editor using the Complex option.\n\nThe 2D Contour Editor window allows the user to define a series of points, in a single plane, that are used to define the footprint of the landing.\nClick Apply to create the slab. The floor slab component is created under the floor slab element. The floor screed component is created under the floor screed element. If the floor screed element does not exist, the floor screed element is created automatically. The Modify Slab + Screed window replaces the Create Slab + Screed window.\nTo cancel the creation of the slab, click Dismiss. If the user navigates to another element, the Floor Slab + Screed Modification window closes automatically.\nEnter the values in the Length and Width fields.\nMeasure the length. Click Measure Length and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nMeasure the width. Click Measure Width and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nClick Pick corners to pick two opposite corners. The Positioning Control window is displayed. The user is prompted to Pick first corner (Snap) Snap: and Pick second corner (Snap) Snap:.\nDefine the length, click Pick Length by Position The Positioning Control window is displayed. The user is prompted to Pick length by position (Snap) Snap:.\nDefine the width, click Pick Width by Position The Positioning Control window is displayed. The user is prompted to Pick width by position (Snap) Snap:.\nEnter the values in the Length and Width fields.\nEnter the values in the Length and Width fields.\nMeasure the length. Click Measure Length and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nMeasure the length. Click Measure Length and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nMeasure the width. Click Measure Width and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nMeasure the width. Click Measure Width and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nClick Pick corners to pick two opposite corners. The Positioning Control window is displayed. The user is prompted to Pick first corner (Snap) Snap: and Pick second corner (Snap) Snap:.\nClick Pick corners to pick two opposite corners. The Positioning Control window is displayed. The user is prompted to Pick first corner (Snap) Snap: and Pick second corner (Snap) Snap:.\nDefine the length, click Pick Length by Position The Positioning Control window is displayed. The user is prompted to Pick length by position (Snap) Snap:.\nDefine the length, click Pick Length by Position The Positioning Control window is displayed. The user is prompted to Pick length by position (Snap) Snap:.\nDefine the width, click Pick Width by Position The Positioning Control window is displayed. The user is prompted to Pick width by position (Snap) Snap:.\nDefine the width, click Pick Width by Position The Positioning Control window is displayed. The user is prompted to Pick width by position (Snap) Snap:.\nEnter the value in the Diameter field.\nMeasure the Diameter. Click Measure Diameter and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nClick Pick position on radius to define the diameter and the Positioning Control window is displayed. Follow the prompt Pick position on radius (Snap) Snap:\nEnter the value in the Diameter field.\nEnter the value in the Diameter field.\nMeasure the Diameter. Click Measure Diameter and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nMeasure the Diameter. Click Measure Diameter and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nClick Pick position on radius to define the diameter and the Positioning Control window is displayed. Follow the prompt Pick position on radius (Snap) Snap:\nClick Pick position on radius to define the diameter and the Positioning Control window is displayed. Follow the prompt Pick position on radius (Snap) Snap:\n\n\n\nShape\nRectangular\nLength\nWidth\nPositioning Control\nPositioning Control\nPositioning Control\nPositioning Control\nPositioning Control\nCircular\nDiameter\nPositioning Control\nPositioning Control\nComplex\n2D Contour Editor\nApply\nModify Slab + Screed\nCreate Slab + Screed window\nDismiss\nFloor Slab + Screed Modification"}
{"Headers": "Create Floor Slab Component", "Content": "Referring to the hierarchy, a floor slab component element must reside below an existing floor slab element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Floor Slab element is the CE.\n\nOn the Building tab, in the Create group, select Slab Component in the Create Element drop-down list.\nClick Create Element to display the Create Floor Slab window.\n\nBy default in the Naming pane of the Create Floor Slab window, the application automatically populates the Name field with a name based on the project or company autonaming rules. Refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nRefer to Create Floor Slab + Screed Component for further information on Floor Slab Component creation.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nCreate Floor Slab + Screed Component\nSelect Structural Element\nBuilding Applications\nFloor Slab\nCE\nBuilding\nCreate\nSlab Component\nCreate Element\nCreate Element\nCreate Floor Slab\nNaming\nCreate Floor Slab\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nCreate Floor Slab + Screed Component\nFloor Slab\nComponent"}
{"Headers": "Create Floor Screed Component", "Content": "Referring to the hierarchy, a floor screed component element must reside below an existing floor screed element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Floor Screed element is the CE.\n\nOn the Building tab, in the Create group, select Screed Component in the Create Element drop-down list.\nClick Create Element to display the Create Floor Screed window.\n\nBy default in the Naming pane of the Create Floor Screed window, the application automatically populates the Name field with a name based on the project or company autonaming rules. Refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nRefer to Create Floor Slab + Screed Component for further information on Floor Screed Component creation.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nCreate Floor Slab + Screed Component\nSelect Structural Element\nBuilding Applications\nFloor Screed\nCE\nBuilding\nCreate\nScreed Component\nCreate Element\nCreate Element\nCreate Floor Screed\nNaming\nCreate Floor Screed\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nCreate Floor Slab + Screed Component"}
{"Headers": "Modify Floor Slab + Screed Components", "Content": "All the tasks associated with the modification of the slab component element can be performed from the Modify Slab + Screed window.\n\nThe materials, thickness, shape, position and orientation can be changed the same way they are selected in the Creation window.\nTo modify the floor slab without modifying the Floor screed, select the Floor Slab in the connections drop-down list at the bottom of the Building Applications window. The Floor Slab Modification window is displayed.\n\nTo modify the floor screed without modifying the floor slab, select the Floor Screed option in the connections drop-down list at the bottom of the Building Applications window The user is navigated to the floor screed and the Floor Screed Modification window is displayed.\n\n\n\nModify Slab + Screed\nCreation\nFloor Slab\nconnections\nBuilding Applications\nFloor Slab\nModification\nFloor Screed\nconnections\nBuilding Applications\nFloor Screed Modification"}
{"Headers": "Modify Floor Slab Component", "Content": "To modify a floor slab component, navigate to the slab component. If the Floor Slab + Screed window is displayed, select the slab element connections drop-down list at the bottom of the Building Applications window.\n\nThe material, thickness, shape, position and orientation can be change the same way they are selected in the Creation window.\nTo change the floor slab and floor screed, select the Slab & Screed option in the connections drop-down list at the bottom of the Building Applications window. The Floor Slab + Screed Modification window is displayed.\nTo modify the floor screed without modifying the floor slab, select the floor screed option in the connections drop-down list at the bottom of the Building Applications window. The user is navigated to the floor screed and the Floor Screed Modification window is displayed.\nTo confirm the change, click Apply. The elevation of any connected components is adjusted accordingly. The contour of connected screed components is not changed.\nTo create a new floor slab with the same parameters, click Repeat.\nClick Dismiss to discard any inputs and close the Modify Floor Slab window.\nIf you use AVEVA E3D Design to change the slab, click Refresh to display the current attributes.\n\n\n\nFloor Slab + Screed\nslab element connections\nBuilding Applications\nCreation\nSlab & Screed\nconnections\nBuilding Applications\nFloor Slab + Screed\nModification\nfloor screed\nconnections\nBuilding Applications\nFloor Screed\nModification\nApply\nRepeat\nDismiss\nModify Floor Slab\nAVEVA E3D Design\nRefresh"}
{"Headers": "Modify Floor Screed Component", "Content": "All the tasks associated with the modification of the floor screed element can be performed from the Modify Floor Screed window.\n\nThe material, thickness, shape, position and orientation can be modified the same way they are selected in the Creation window.\nTo modify the floor slab and floor screed together, select the Slab & Screed option in the connections drop-down list at the bottom of the Building Applications window. The user is navigated to the floor slab and the Floor Slab and Screed Modification window is displayed.\nTo change the floor slab without changing the floor screed, select the Floor Slab option in the connections drop-down list at the bottom of the Building Applications window. You are navigated to the floor slab and the Floor Slab Modification window is displayed.\nTo confirm the change, click Apply.\nTo create a new floor screed with the same parameters, click Repeat. The Create Floor Screed window is then displayed.\nClick Dismiss to discard any inputs and close the Modify Floor Screed window.\nIf you use AVEVA E3D Design to change the screed, click Refresh to display the current attributes.\n\n\n\nModify Floor Screed\nCreation\nSlab & Screed\nconnections\nBuilding Applications\nFloor Slab and Screed Modification\nFloor Slab\nconnections\nBuilding Applications\nFloor Slab\nModification\nApply\nRepeat\nCreate Floor\n\nDismiss\nModify Floor Screed\nAVEVA E3D Design\nRefresh"}
{"Headers": "Create Sloping Floor Element", "Content": "Referring to the hierarchy, a sloping floor element must reside below an existing floor slab element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Floor Slab element is the CE.\n\nOn the Building tab, in the Create group, select Sloping Floor in the Create Element drop-down list.\nClick Create Element to display the Create Floor Slab window.\n\nThe Create Floor Slab window supports functionality for naming, material selection, and defining the slab thickness. The functionality is similar to that previously explained for Slab + Screed components. Refer to Create Floor Slab for further information.\nSloping floors are created in a manner that is closer to straight beam creation than other floor types. A catalogue element is used as a profile between two points defined by the user. As such the creation window reflects the requirements for catalogue selection, positioning, orientation, and mitring.\nClick Catalogue to display the Section Specification window. Here the user can select appropriate settings relating to the profile that is used to model the floor.\n\nClick Properties to display the Modify Properties window.\n\nHere the user can select appropriate settings relating to the profile that is used to model the floor.\nClick Apply in the Section Specification window to set the properties.\nClick Cancel to discard any inputs and close the Section Specification window.\nClick Pick profile to copy to copy the properties of an existing sloped floor.\nThe Properties on the Create Floor Slab window mimics the Properties on the Section Specification window.\nIt allows users to adjust the default width and depth parameters that is used for the slab profile.\nThe Length textbox displays the proposed length of the slab. It can be populated in two ways:\nClick Flip start and end position reverses the start and end positions of the slab.\nClick the Use end position for start sets the end position of a previously created slab as the start position of the current slab for continuous end-to-start creation.\nSelect Graphical Pick Start/End from the option list to invoke the Positioning Control window to make two graphical selections to establish the start and end of the slab.\nSelect Move Graphically from the option list invokes the Positioning Control window allowing the user to graphically select an existing element to move the slabs start position to.\nThe Start Position section of the window is used to establish the start position of the slab. It can be populated in several ways:\nThe wrt (with respect to) textbox displays the element name that the start position co\u2011ordinates are positioned with respect to.\nThe End Position section of the window is used to establish the end position of the slab. It uses the same functionality as the Start Position section.\nThe Section Rotation textbox displays the rotation angle of the section To populate it, type in the appropriate angle and press Enter. Rotation angles can be entered in any of the following formats:\ndecimal degrees\ndegrees, minutes and seconds\ndecimal grades.\nThe miter Direction section of the window is used to establish the miter directions of the Start and End. The miter directions are manipulated as the start and end positions of the slab are established and/or connected to adjacent elements. By default, the miters are perpendicular to the direction of the slab and are always shown with respect to the level. However, if needed, the miters can be manually changed. Two methods can be used to select each miter:\nThe Connectivity Activated checkbox is selected by default. The Building Design utility always attempts to connect elements to other elements. For example, if the start position of a slab has been established by selecting a wall using a graphical pick, the slab is automatically connected to the wall element. The name of the connected element is shown with a green background.\nClick Apply to create the slab. The Modify Floor Slab window replaces the Create Floor Slab window.\n123.25\ndecimal degrees\n123\u00b015\u201905\" or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades.\nType a value in the length textbox.\nClick Measure Length to invoke the Positioning Control window to graphically pick existing elements to measure the length.\nType a value in the length textbox.\nType a value in the length textbox.\nClick Measure Length to invoke the Positioning Control window to graphically pick existing elements to measure the length.\nClick Measure Length to invoke the Positioning Control window to graphically pick existing elements to measure the length.\nEstablish the correct direction from the option lists and type the co-ordinates.\nClick Graphical Pick Start to invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nEstablish the correct direction from the option lists and type the co-ordinates.\nEstablish the correct direction from the option lists and type the co-ordinates.\nClick Graphical Pick Start to invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nClick Graphical Pick Start to invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\n123.25\n123.25\n123.25\n123\u00b015\u201905\" or 123d15m05s\n123\u00b015\u201905\" or 123d15m05s\n123\u00b015\u201905\" or 123d15m05s\n130G12\n130G12\n130G12\nClick End direction always perpendicular to unlock the textbox. A new direction can be entered by typing a direction or, by clicking Pick surface or edge to define direction, graphically select a face or edge of an existing element.\nClick End direction free to lock the textbox and force the miter direction to be perpendicular to the slab direction. The miter is calculated automatically when the direction of the slab is modified.\nClick End direction always perpendicular to unlock the textbox. A new direction can be entered by typing a direction or, by clicking Pick surface or edge to define direction, graphically select a face or edge of an existing element.\nClick End direction always perpendicular to unlock the textbox. A new direction can be entered by typing a direction or, by clicking Pick surface or edge to define direction, graphically select a face or edge of an existing element.\nClick End direction free to lock the textbox and force the miter direction to be perpendicular to the slab direction. The miter is calculated automatically when the direction of the slab is modified.\nClick End direction free to lock the textbox and force the miter direction to be perpendicular to the slab direction. The miter is calculated automatically when the direction of the slab is modified.\n\n\n\nCreate Floor Slab\nSelect Structural Element\nBuilding Applications\nFloor Slab\nCE\nBuilding\nCreate\nSloping Floor\nCreate Element\nCreate Element\nCreate Floor Slab\nCreate Floor Slab\nProperties\nCancel\n\nProperties\nProperties"}
{"Headers": "Create Floor Grating", "Content": "Where steel materials have been selected, flooring options are filtered to allow the creation of grating. Grating uses catalogue components to specify the plate, but the grating itself is defined and positioned in a similar manner to other floor elements.\nReferring to the hierarchy, a grating element must reside below an existing group element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Group element is the CE.\n\nOn the Building tab, in the Create group, select Grating in the Create Element drop-down list.\nClick Create Element to display the Create Grating window.\n\nBy default in the Naming pane of the Create Grating window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nSelect the desired material using the Default material drop-down list.\nThe material is used to calculate the weight. The density of the material selected is shown in a tooltip.\nIf an Assembly has been defined, the user can add the Grating element to it by selecting it from the grid. If an assembly is not required the default setting of None should be selected.\nClick Apply to create the grating. The Modify Grating window replaces the Create Grating window.\nThe functionality of the Modify Grating window is identical to the functionality available from Modify Floor Slab window. Refer to Modify Floor Slab Element for further information.\n\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\nNote:\nThat only steel materials are proposed sub-component, that is SOLI elements with a purpose of STEE.\nNote:\nThe application recognizes Grating created using other AVEVA E3D Design applications. To make sure the consistency of the Purpose of those elements must be set to GRAT.\n\n\n\nNaming\nModify Floor Slab Element\nSelect Structural Element\nBuilding Applications\nGroup\nCE\nBuilding\nCreate\nGrating\nCreate Element\nCreate Element\n\nNaming\nCreate Grating\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nDefault material\nNote:\nNote\n:\nAVEVA E3D Design\nModify Grating\nModify Floor Slab\nModify Floor Slab Element"}
{"Headers": "Create Floor Grating Component", "Content": "Referring to the hierarchy, a grating component element must reside below an existing grating element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Grating element is the CE.\n\nOn the Building tab, in the Create group, by default Component is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Grating window.\n\nBy default in the Naming pane of the Create Grating window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Material drop-down list by default is set to Pyrocrete, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight. The density of the material selected is shown in a tooltip.\nThe Grating Thickness can be populated in several ways:\nClick Catalogue to copy the default specification values from the Plates tab. Refer to Default Panel Specification for further information.\nClick Pick profile to copy copies the properties of an existing grating.\nThe Position section of the window is used to establish the centre position of the grating. It can be populated several ways:\nThe default position is at the origin of the level. By default, the position is the origin of the grating. For rectangular and circular shapes, the origin is at the center. To select a reference point to position the grating click the Reference drop-down list.\nThe Orientation section of the window is used to establish the Direction and Rotation angle of the grating.\nThe Direction textbox displays the direction of the grating (defined from the start to the end positions).\nThe direction may be changed using a number of methods. The direction can be re\u2011established by typing a new direction (for example: U, N, N45E, S30W15D) then click Enter.\nClicking Pick surface or edge to define direction allows the user to select an existing edge or surface in the model. Where a surface is selected then direction is set perpendicular to it. Where an edge is selected the direction is aligned with the edge.\nClicking Rotate angle using two picks allows the user to graphically pick the rotation angle by using the Positioning Control window. The user is prompted to Pick first point to define rotation (Snap) Snap:, Pick second point to define rotation (Snap) Snap: to pick two points in the graphical view. A graphical aid line displays the angle of rotation created by the picks. Alternatively the user can type in an angle using a format of degrees, minutes, and seconds.\nThe Shape of the grating element is also required. The option list in the Shape section of the window has three configurations; Rectangular, Circular, and Complex.\nDimensional information can be entered directly or using graphical picks. The content of the Shape section of the window, particularly the functionality of the graphical pick and dimensional textboxes, changes to suit the configuration selected.\nWhere complicated geometry is required the user can select the Complex configuration. The 2D Contour Editor window is displayed.\n\nClick Apply to create the grating. The Modify Grating window replaces the Create Grating window.\nTo cancel the creation of the grating, click Dismiss. If the user navigates to another element, the Modify Grating window closes automatically.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\nEnter the absolute finished level (wrt World) in the Top Level field.\nClick Pick Top Level. The Positioning Control window is displayed. Follow the prompt Pick Top Level (Snap) Snap: and select the top level in the graphical view.\nEnter the finished thickness in the Thickness field. If the thickness is locked, click Padlock to unlock it.\nClick Measure Height the user is prompted to Height:Pick Start (Snap) Snap:, Height:Pick Start (Snap) Snap: and select two graphical picks.\nEnter the absolute bottom level (wrt World) in the Bottom Level field.\nClick Pick Bottom Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the bottom level in the graphical view.\nIf the user does not want the thickness to adapt to level changes, click Padlock to lock the thickness.\nThe default finished level is zero with respect to the level. The default grating thickness is 0.100 meter.\nEnter the absolute finished level (wrt World) in the Top Level field.\nEnter the absolute finished level (wrt World) in the Top Level field.\nClick Pick Top Level. The Positioning Control window is displayed. Follow the prompt Pick Top Level (Snap) Snap: and select the top level in the graphical view.\nClick Pick Top Level. The Positioning Control window is displayed. Follow the prompt Pick Top Level (Snap) Snap: and select the top level in the graphical view.\nEnter the finished thickness in the Thickness field. If the thickness is locked, click Padlock to unlock it.\nEnter the finished thickness in the Thickness field. If the thickness is locked, click Padlock to unlock it.\nClick Measure Height the user is prompted to Height:Pick Start (Snap) Snap:, Height:Pick Start (Snap) Snap: and select two graphical picks.\nClick Measure Height the user is prompted to Height:Pick Start (Snap) Snap:, Height:Pick Start (Snap) Snap: and select two graphical picks.\nEnter the absolute bottom level (wrt World) in the Bottom Level field.\nEnter the absolute bottom level (wrt World) in the Bottom Level field.\nClick Pick Bottom Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the bottom level in the graphical view.\nClick Pick Bottom Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the bottom level in the graphical view.\nIf the user does not want the thickness to adapt to level changes, click Padlock to lock the thickness.\nIf the user does not want the thickness to adapt to level changes, click Padlock to lock the thickness.\nThe default finished level is zero with respect to the level. The default grating thickness is 0.100 meter.\nThe default finished level is zero with respect to the level. The default grating thickness is 0.100 meter.\nEnter the values in the fields for East, North and Up in the Position frame. The reference can be changed by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it.\nSelect the position in the graphical view using Select Structural Element in the Position frame. To avoid changing a desired value in a field, click Coordinates unlocked to lock it.\nEnter the values in the fields for East, North and Up in the Position frame. The reference can be changed by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it.\nEnter the values in the fields for East, North and Up in the Position frame. The reference can be changed by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it.\nSelect the position in the graphical view using Select Structural Element in the Position frame. To avoid changing a desired value in a field, click Coordinates unlocked to lock it.\nSelect the position in the graphical view using Select Structural Element in the Position frame. To avoid changing a desired value in a field, click Coordinates unlocked to lock it.\nNote:\nIt is also possible to create a grating with AVEVA E3D Design using the Plates application. On the Plates tab, in the Create group, click Panels.\n\n\n\nNaming\nDefault Panel Specification\nSelect Structural Element\nBuilding Applications\nGrating\nCE\nBuilding\nCreate\nComponent\n\nCreate Element\nCreate Element\n\nNaming\nCreate Grating\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nMaterial\nPyrocrete\nMaterial\nwrt\nPositioning Control\nThickness\nwrt\nPositioning Control\nDefault Panel Specification\nPosition\nWrt\nPosition\nReference drop-down\nPick surface or edge to define direction\nClicking Rotate angle using two picks\nApply\nModify Grating\nCreate Grating\nDismiss\nModify Grating\nNote:\nAVEVA E3D Design\nPlates\nPlates\nCreate\nPanels"}
{"Headers": "Modify Floor Grating Component", "Content": "All the tasks associated with the modification of the floor grating element can be performed from the Modify Grating window.\n\nThe material, thickness, shape, position and orientation can be modified the same way they were selected in the Create Grating window.\nTo confirm the change, click Apply.\nTo create a new grating with the same parameters, click Repeat. The Create Grating window is then displayed.\nClick Dismiss to discard any input and close the Modify Grating window.\nClick Refresh to discard any modifications and display the original attributes.\n\n\n\n\nCreate Grating\nApply\nRepeat\nCreate Grating\nRefresh"}
{"Headers": "Create Wall", "Content": "Referring to the hierarchy, a wall element must reside below an existing group element with a purpose set to All Walls.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Group element is the CE.\n\nOn the Building tab, in the Create group, by default Wall is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Wall window.\n\nBy default in the Naming pane of the Create Wall window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Default Material drop-down list by default is set to Pyrocrete, the default material can be changed to another suitable material. From the Default Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight, the density of the material selected is shown in a tooltip.\nIn the Assembly pane of the Create Wall window, by default None is displayed. The user can add the window to a selected assembly if required. Refer to Create Assemblies for further information.\nClick Apply to create the Wall element. The Modify Wall window is displayed and the Wall element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Wall Element for further information.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\nNote:\nIt is also possible to create a wall with AVEVA E3D Design using the Walls & Floors application. On the Walls & Floors tab, in the Create group, select Compound Wall from the Walls drop-down menu.\n\n\n\nNaming\nCreate Assemblies\nModify Wall Element\nSelect Structural Element\nBuilding Applications\nGroup\nCE\nBuilding\nCreate\nWall\nCreate Element\nCreate Element\nCreate Wall\nNaming\nCreate Wall\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nDefault Material\nPyrocrete\nDefault Material\nAssembly\nCreate Wall\nNone\nCreate Assemblies\nApply\nWall\nModify\nWall\nWall\nBuilding Applications\nModify Wall Element\nNote:\nAVEVA E3D Design\nWalls & Floors\nWalls & Floors\nCreate\nCompound Wall\nWalls"}
{"Headers": "Modify Wall Element", "Content": "All the tasks associated with the modification of the wall element can be performed from the Modify Wall window.\n\nThe material can be modified the same way it was selected in the Creation window.\nTo confirm the change, click Apply.\nTo create a new wall with the same parameters, click Repeat. The Create Wall window is then displayed.\nClick Dismiss to discard any input and close the Modify Wall window.\nClick Refresh to discard any modifications and display the original attributes.\n\n\n\nModify Wall\nCreation\nApply\nRepeat\nCreate Wall\nDismiss to discard any input and close the Modify Wall window\nRefresh"}
{"Headers": "Create Straight Wall", "Content": "Referring to the hierarchy, a straight wall element must reside below an existing wall element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Wall element is the CE.\n\nOn the Building tab, in the Create group, by default Straight Wall is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Straight Wall window.\n\nBy default in the Naming pane of the Create Straight Wall window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Material drop-down list by default is set to Pyrocrete, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nTo make sure design consistency and conformity with company standards, the basic definitions of all profiles which the user can use are held in a Catalogue database. The catalogue database is used in other Design applications with other materials and can be used in the Building application. The profiles available from the Catalogue are determined by the Section Specification.\nClick Catalogue, the Wall Specification (Default) window is displayed:\n\nBy default the default profile specification is selected but the user can select an alternative specification from the column element. for further information on the Default Profile Specification, refer to Create/Modify Element Window for further information.\nClick Apply to confirm the specification or Cancel to discard any inputs and close the Wall Specification (Default) window.\nTo copy the section of another wall, click Pick Profile to Copy and select the other wall.\nThe user can also modify the width and height properties of the column element, from the Create Straight Wall window, click Properties and the Modify Properties window is displayed.\n\nThe thickness and height of the wall element can be input directly in to the Thickness and Height fields or click Measure Thickness, the user is prompted to \u2018Measure property dimension start (Snap) Snap:\u2019 and the selection of the start dimension the user is prompted to \u2018Measure property dimension end (Snap) Snap:\u2019. After the selection in the 3D graphical view the Thickness measurement field is automatically populated. The height can be automatically populated in the same way, with the exception of the user clicking Measure Height. Click OK to save the properties and close the Modify Properties.\nTo return the width and height back to the default, click Default.\nTo discard any inputs, click Reset.\nTo close the Modify Properties, click Cancel.\nBy default the Height of new column element is 3000, but the user can change the Height, input the required height into the Height field.\nClick Measure Height and the user is prompted to Measure Height: Pick Start (Snap) Snap: in the 3D graphical view, after the selection has been made the Height field is automatically populated.\n\nThere are several methods to determine the top and bottom levels of the wall:\nEnter the absolute top level (wrt World) in the Top Level field. If the height is locked or the value is less than the bottom level, the bottom level adapts. If the height is not locked, the height adapts.\nSelect the top level using a position in the graphical view and click Pick Top Level. The view's mode changes and the Positioning Control window is displayed. If the height is locked or the value is less than the bottom level, the bottom level adapts. If the height is not locked, the height adapts. If a suitable element is selected the background colour of Top Level is changed to green and the tooltip indicates the connected element.\nEnter the height in the Height field. If the height is locked, click Padlock to unlock it. The top level adapts.\nClick Measure Height and the user is prompted to Measure Height: Pick Start (Snap) Snap: in the graphical view, after the selection has been made the Height field is automatically populated. The bottom level adapts.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the height is locked or if the value is greater than the top level, the top level adapts. If the height is not locked, the height adapts.\nSelect the bottom level using a position in the graphical view and click Select Structural Element. The view's mode changes and the Positioning Control window is displayed. If the height is locked or the value is greater than the top level, the top level adapts. If the height is not locked, the height adapts. If a suitable element is selected the background colour of Bottom Level is changed to green and the tooltip indicates the connected element.\nTo prevent the height adapting to level modifications, click Padlock to lock the height.\nThe default bottom level is zero with respect to the level. A cone shows the top level of the wall in the graphical view.\nBy default the Length of new wall element is 5000, but the user can change the Length. Input the required length into the Length field.\nMeasure Length, the user is prompted to Measure Length: Pick Start (Snap) Snap: in the graphical view, after the selection has been made the Length field is automatically populated.\nClick Flip start and end position to reverse the start and end positions of the wall.\nClick Use end position for start to set the end position of the previously created wall as the start position of the current wall.\n\nSelect Move Graphically from the option list to invoke the Positioning Control window and allows the user to graphically select an existing element to move the walls\u2019s start or end position to.\nSelect Graphical Pick Start/End from the option list to invoke the Positioning Control window and allows the user to make two graphical selections to establish the start and end of the wall.\nThe Start Position section of the window is used to establish the start position of the wall. It can be populated several ways:\nEstablish the correct direction from the option lists and type the coordinates.\nClick Graphical Pick Start invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nClick Pick to invoke the Positioning Control window to graphically pick an existing element to establish the start point. To avoid modifying a desired value in a field, click Padlock to lock. If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. Its length is always calculated between both positions.\nThe End Position section of the window is used to establish the end position of the wall. It can be populated several ways:\nEstablish the correct direction from the option lists and type the coordinates.\nClick Graphical Pick End invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nClick Pick to invoke the Positioning Control window to graphically pick an existing element to establish the end point. To avoid modifying a desired value in a field, click Padlock to lock. If the direction is locked, the start position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. Its length is always calculated between both positions.\nThe direction is always shown with respect to the level. If the direction is locked, click Padlock to unlock it. The end position is adjusted to suit the new direction and the existing length. To avoid changing the desired direction, click Padlock to lock it.\nAlternatively, to select the direction in the graphical view click Pick surface or edge to define direction. Select an object in the graphical view and slide the cursor to the desired face. The direction is perpendicular to the selected face. The end position is adjusted to suit the new direction and the existing length. To reverse the direction, click Reverse Direction. To avoid changing the desired direction, click Padlock to lock it.\nThe miter Direction pane of the Create Beam window can be used to establish the miter direction of the Start and Stop positions by default, the miters are perpendicular of the beam and are always shown with respect to the level. The miter is calculated automatically when the direction of the beam is modified. The user can modify each miter.\nInput a direction in the Start field, the direction is always shown with respect to the level or click Pick edge or surface to define direction, the user is prompted to Pick Face or Edge in the 3D graphical view.\nInput a direction in the End field, the direction is always shown with respect to the level or click Pick edge or surface to define direction, the user is prompted to Pick Face or Edge in the 3D graphical view.\nActivating the Connectivity\nThe Building application always attempts to connect elements to other elements. If the user has selected a position on a straight wall, a column or a straight beam with a graphical pick, the wall is automatically connected to the selected element.\nThe name of the connected element is shown with a yellow background.\n\nIf the connectivity is activated, the position and the miter of this end are adjusted.\nIf the user does not select a straight wall, nor a column or straight beam, but the end is in the same position as the end of a wall, column or beam, a second form of connectivity can be used. If the connectivity is activated, the miter of both ends is adjusted.\n\nClick Apply to create the straight wall. the Modify Straight Wall window replaces the Creation window. Enter a valid name in the Name field to activate it.\nTo cancel the creation of the straight wall click Dismiss to discard any inputs and close the Create Straight Wall window.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\nNote:\nUse Pick Top Level and Select Structural Element for the top and bottom levels to establish a connection with the floors above and below the straight wall.\nNote:\nTo use the second type of connectivity, select a p-point on the slab instead of the end of the other wall/beam/column.\nNote:\nTo avoid the modification of wall justification, create the wall in the same direction around a slab.\n\n\n\nNaming\nCreate/Modify Element Window\nSelect Structural Element\nBuilding Applications\nWall\nCE\nBuilding\nCreate\nStraight Wall\nCreate Element\nCreate Element\nCreate Straight Wall\nNaming\nCreate Straight Wall\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nMaterial\nPyrocrete\nMaterial\nCatalogue\nBuilding\nCatalogue\nCatalogue\nWall Specification (Default)\nDefault Profile Specification\nCreate/Modify Element Window\nApply\nCancel\nWall Specification (Default)\nCreate Straight Wall\nProperties and\nModify Properties\nThickness\nHeight\nMeasure Thickness\n\u2018Measure property dimension start (Snap) Snap:\u2019\n\u2018Measure property dimension end (Snap) Snap:\u2019\nMeasure Height\nOK\nModify Properties\nDefault\nReset\nCancel\nHeight\nClick Measure Height\nMeasure Height: Pick Start (Snap) Snap:\nwrt\nTop Level\nPositioning Control\nHeight\nClick Measure Height\nMeasure Height: Pick Start (Snap) Snap:\nwrt\nBottom Level\nPositioning Control\nBottom Level\nNote:\nLength\nMeasure Length\nMeasure Length: Pick Start (Snap) Snap:\nDirection\nCreate Beam\nStart\nPick edge or surface to define direction\nPick Face or Edge\nEnd\nPick edge or surface to define direction\nPick Face or Edge\nActivating the Connectivity\nBuilding\nNote:\nApply\nModify Straight Wall\nCreation\nName\nDismiss\nCreate Straight Wall\nNote:"}
{"Headers": "Modify Straight Wall", "Content": "All the tasks associated with the modification of the straight wall element can be performed from the Modify Straight Wall window.\n\nThe functionality of this window is identical to the Create Straight Wall window. Refer to Create Straight Wall for further information.\nTo copy the section of another wall, click Pick profile to copy and select the other wall. To modify the section, click Catalogue. The Wall Specification window is displayed with the selected wall as the CE.\n\nSelect the specification using the Specification drop-down list.\nSelect the section using the Generic Type drop-down list.\nChoose the alignment of the wall using the Justification, Member Line, and Joint Line drop-down lists.\nEnter the properties of the section using the Modify Properties window displayed when you click Properties.\nTo adjust the ends of the straight walls and beams and the columns connected to the wall, select the Re-trim all attached sections option.\n\nClick Apply to change the wall section, then Cancel to delete any input and close the Wall Specification window.\nThe properties can be altered using Properties.\nText in red indicates that the wall is connected to the end of the named wall or beam.\nText in yellow indicates that the wall is connected along the named wall or beam.\nText in green indicates that the wall is connected to the named floor.\nIf the connectivity is activated, the position and miters of the ends are adjusted.\nTo confirm the change, click Apply.\nNote:\nThe modification is made immediately; before the Straight Wall Modification window is confirmed.\nNote:\nIf the connectivity hinders you in making the desired change, you can disconnect the end using Disconnect Walls.\n\n\n\nCreate Straight Wall\nModify Straight Wall\nCreate Straight Wall\nCatalogue\nSpecification\nGeneric Type\nMember Line\nJoint Line\n\nModify Properties\nProperties\nRe-trim all attached sections\nApply\nCancel\nNote:\nStraight Wall Modification\nProperties\nNote:\nDisconnect Walls\nApply"}
{"Headers": "Split Walls", "Content": "Functionality is available to split walls within the structural model. To do this, on the Building tab, in the Modify group, select Split to display the Split vertically window.\n\nWhen the wall is split, two wall sections are displayed in the model. One section maintains the name and database reference number of the original wall element.\nThe other section now has a new database reference and therefore requires a unique name. A suitable name for the new wall element can be entered in the Split vertically window.\nThe Position section of the window allows the user to define the split point.\nThe user can specify a distance from either the start or end of the wall, based on the original walls length. Alternatively, the user can click Graphical select make a graphical selection. The Positioning Control window then becomes active.\nOnce a suitable Name has been provided and a split point defined, click Apply to split the wall element.\nClick Dismiss to cancel the action and close the window.\nWalls can also be split horizontally, from the Split vertically window, click Split horizontally to display the Split horizontally window.\n\nLike splitting vertically, two wall sections are displayed in the model.\nThe original wall element is maintained and a new wall element requiring a unique name is now created.\nTop and bottom level information for the original wall is also displayed on the window. The level at which the split is required can be entered directly into the Split Level textbox.\nThe user can make a graphical selection of the split level by clicking Pick split level. The Positioning Control window then becomes active.\nOnce a suitable Name has been provided and a split level defined, click Apply to split the wall element.\n\n\n\nBuilding\nModify\nSplit"}
{"Headers": "Connectivity", "Content": "To use the procedures given in the Connectivity group, refer to Wall Connectivity for further information.\n\n\n\nWall Connectivity\nWall Connectivity"}
{"Headers": "Create Curved Wall", "Content": "Referring to the hierarchy, a curved wall element must reside below an existing wall element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Wall element is the CE.\n\nOn the Building tab, in the Create group, select Curved Wall in the Create Element drop-down list.\nClick Create Element to display the Create Curved Wall window.\n\nThe functionality of this window is virtually identical to the Create Straight Wall window, with the following exceptions:\nMirror Profile\nSection Rotation\nShape\nRadius\nArc Angle.\nMirror Profile\nMirror Profile\nSection Rotation\nSection Rotation\nShape\nShape\nRadius\nRadius\nArc Angle.\nArc Angle.\n\n\n\nSelect Structural Element\nBuilding Applications\nWall\nCE\nBuilding\nCreate\nCurved Wall\nCreate Element\nCreate Element\nCreate Curved Wall\nCreate Straight Wall"}
{"Headers": "Mirror Profile", "Content": "The section profile that applies to the curved wall can be mirrored. By default, the Mirror Profile checkbox is clear, to mirror the section profile select the Mirror Profile checkbox.\n\n\n\nMirror Profile\nMirror Profile"}
{"Headers": "Section Rotation", "Content": "The Section Rotation specifies the rotation angle of the section profile about its justification pline.\n\nBy default the section rotation is 0\u00b00\u20190\u2019\u2019, in Section Rotation enter the rotation angle in one of the following formats:\nDecimal degrees\n123.25\nDegrees, minutes and seconds\n123\u00b015\u201905\u2019\u2019 or 123d15m05s\nDecimal grades\n130G12\nDecimal degrees\n123.25\nDegrees, minutes and seconds\n123\u00b015\u201905\u2019\u2019 or 123d15m05s\nDecimal grades\n130G12\n\nDecimal degrees\n123.25\nDegrees, minutes and seconds\n123\u00b015\u201905\u2019\u2019 or 123d15m05s\nDecimal grades\n130G12\n\n\n\nSection Rotation"}
{"Headers": "Shape", "Content": "Two types of curved wall elements are available for selection by the user:\nIn the Shape drop-down list select Single Arc, the single arc option allows the user to create a single-arched shaped wall in an angle range of 0\u00b0 and 360\u00b0.\n\nThe user can pick the position of curves, start points and end points of curved beam elements in the 3D graphical view. From the Create Curved Wall window, from the Shape drop-down list, select:\nGraphical Pick Centre\nPositions the centre of the single arc on an existing element in the design, the user is prompted to Graphical Pick Centre (Snap) WP Snap: in the status bar of the 3D graphical view.\nGraphical Pick Start\nPicks the start of the single arc on an existing element in the design, the user is prompted to Pick Start (Snap) WP Snap: in the status bar of the 3D graphical view. Once the selection has been made the rotation and angle are adjusted for the new start of the curve. If the radius is locked, the start position is adjusted to use the current radius. Otherwise, the end position is adjusted to use the new radius.\nGraphical Pick End\nPicks the end of the single arc on an existing element in the design, the user is prompted to Pick End (Snap) WP Snap: in the status bar of the 3D graphical view. Once the selection has been made the rotation and angle are adjusted for the new end of the curve. If the radius is locked, the end position is adjusted to use the current radius. Otherwise, the start position is adjusted to use the new radius.\nGraphical Pick Arc\nPicks an existing panel vertex (PAVE) to establish the geometry (centre, start, end) of a single arc wall. The user is prompted to Pick PAVE: in the status bar of the 3D graphical view.\nSimple Arc\nComplex.\nSimple Arc\nSimple Arc\nComplex.\nComplex.\nNote:\nThe Graphically Pick Arc requires the PAVE to have a radius greater then or equal to half the profile width for the geometry to display. If the radius is smaller, the geometry is rendered invalid and is not displayed.\n\n\n\nShape\nSingle Arc\nCreate Curved Wall\nShape\nGraphical Pick Centre\nGraphical Pick Centre (Snap) WP Snap\nGraphical Pick Start\nPick Start (Snap) WP Snap:\nGraphical Pick End\nPick End (Snap) WP Snap:\nGraphical Pick Arc\nPick PAVE:\nNote:\nGraphically Pick Arc"}
{"Headers": "Radius", "Content": "If graphical pick functionality is not required, for example: precise dimensions have to be entered. The user can enter the dimensions into the Radius and Arc Angle fields from the Create Curved Wall window.\nThe Radius textbox displays the radius of single-arced shaped wall. To lock or unlock the radius value click Radius locked.\nThe radius value can be set by:\nThe Arc Angle textbox displays the arc angle of a single arc shaped wall ranging from 0\u2011360 degrees. To populate it type a value for the arc angle then press Enter. Arc angles can be entered in any of the following formats:\nDecimal degrees\n123.25\nDegrees, minutes and seconds\n123\u00b015\u201905\u2019\u2019 or 123d15m05s\nDecimal grades\n130G12\nDecimal degrees\n123.25\nDegrees, minutes and seconds\n123\u00b015\u201905\u2019\u2019 or 123d15m05s\nDecimal grades\n130G12\nAlternatively, click Pick Arc Angle to invoke the Positioning Control window allowing the user to make graphically selections of existing elements to establish the arc angle.\nThe Position section of the window is used to establish the centre position of a single-arced shaped wall. It can be populated several ways:\nThe wrt (with respect to) textbox displays the element name to which the start position co\u2011ordinates are positioned to.\nThe Orientation section of the window is used to establish the Direction and Rotation angle of the wall.\nThe Direction textbox displays the direction of the wall (defined from the start to the end positions).\nThe direction may be changed using a number of methods. The direction can be re\u2011established by typing a new direction (for example: U, N, N45E, S30W15D) then click Enter.\nTwo other methods can be used to set the direction of the wall.\nThe Pick surface or edge to define direction allows the user to graphically pick the face or edge of an existing element.\nThe Rotation textbox displays the rotation angle of the curved wall. To populate it type a value for the Rotation angle then click Enter. Rotation angles can be entered in the same formats as Arc Angles.\nAlternatively, click Rotate angle using two picks to invoke the Positioning Control window allowing the user to make graphically selections of existing elements to establish the rotation angle.\nDecimal degrees\n123.25\nDegrees, minutes and seconds\n123\u00b015\u201905\u2019\u2019 or 123d15m05s\nDecimal grades\n130G12\nTyping a radius and click Enter.\nClick Measure Length and graphically selecting existing elements to establish the radius.\nTyping a radius and click Enter.\nTyping a radius and click Enter.\nClick Measure Length and graphically selecting existing elements to establish the radius.\nClick Measure Length and graphically selecting existing elements to establish the radius.\nEstablish the correct direction from the option lists and type the co-ordinates.\nClick Graphical Pick Start to invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nEstablish the correct direction from the option lists and type the co-ordinates.\nEstablish the correct direction from the option lists and type the co-ordinates.\nClick Graphical Pick Start to invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nClick Graphical Pick Start to invoke the Positioning Control window to graphically pick the position. The co-ordinates are populated automatically.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nAlternatively, the first two methods can be combined by utilizing the padlocks. Click Coordinate locked to unlock a value or click Coordinate unlocked to lock the value. A locked value is displayed in grey.\nNote:\nThe start of the arc remains stationary while the picked point projects an invisible line to the centre of the arc and the end of the arc snaps to this line thus creating the arc angle.\n\n\n\nRadius\nArc Angle\nCreate Curved Wall\nNote:"}
{"Headers": "Complex Curve", "Content": "To define a complex curve, the 2D Editor must be run using the Shape drop-down list. The curved beam is created and the Modify window replaces the Create window.\n\nClick Apply to create the curved wall. The Modify Curved Wall window replaces the Create Curved Wall window. If the option is greyed out, enter a valid name in the Name field to activate it.\nTo cancel the creation of the curved wall, click Dismiss. If the user navigates to another element, the Modify Curved Wall window closes automatically.\n\n\n\n2D Editor\nShape\nModify\nCreate\nApply\nModify\nCurved Wall\nCreate Curved Wall\nName\nDismiss\nModify Curved Wall"}
{"Headers": "Activate the Connectivity", "Content": "If the end of the wall proposed is in the same position as another end and the connectivity is activated, the miter of both ends is adjusted.\n\n\n\n"}
{"Headers": "Modify Curved Wall", "Content": "All the tasks associated with the modification of the curved wall element can be performed from the Modify Curved Wall window.\n\nThe material, section, position, orientation and miters can be modified in the same way as these options were selected in the Create Curved Wall window. The section can be modified the same way as for a straight wall.\nIf the connectivity is activated, the position and miters of the ends are adjusted.\nTo confirm the modification, click Apply.\nTo create a new wall component with the same parameters, click Repeat. The Create Curved Wall window is then displayed.\nTo close the Modify Curved Wall window, click Dismiss.\nClick Refresh to discard any modifications and display the original attributes.\n\n\n\nModify Curved Wall\nCreate Curved Wall\nApply\nRepeat\nCreate Curved Wall\nModify Curved Wall\nDismiss\nRefresh"}
{"Headers": "Create General Wall", "Content": "General walls can be used where the wall geometry is irregular, complex, or varies in thickness. General walls require the user to define the wall footprint as the cross-sectional shape of an extrusion. The cross sectional shape is then extruded through the wall height.\nReferring to the hierarchy, a general wall element must reside below an existing wall element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Wall element is the CE.\n\nOn the Building tab, in the Create group, select General Wall in the Create Element drop-down list.\nClick Create Element to display the Create General Wall window.\n\nNaming, material definition, and wall height can be selected in a similar manner to creating a straight wall.\nThe cross sectional shape of the wall element can be defined using the mechanisms contained in the Shape section of the window. As general walls are often implemented where complicated geometry is encountered, the 2D Contour Editor (available under the Complex shape option) is frequently utilized.\n\nThe 2D Contour Editor window allows the user to define a series of points, in a single plane, that are used to define the footprint of the general wall.\nOnce the wall footprint has been established the user can position and orientate the wall. Refer to Create Straight Wall for further information.\nOnce all required information has been entered click Apply to create the General Wall. The hierarchy section of the Building Applications window is automatically updated.\nThe Create General Wall window is closed and the Modify General Wall window is displayed.\n\n\n\nCreate Straight Wall\nSelect Structural Element\nBuilding Applications\nWall\nCE\nBuilding\nCreate\nGeneral Wall\nCreate Element\nCreate Element\n\nCreate Straight Wall\nGeneral Wall"}
{"Headers": "Modify General Wall", "Content": "To modify a general wall, navigate to the wall component. If the general wall is rectangular or circular in shape, the window used to modify the non-catalogued walls appears.\n\nThe material, height, shape, position and orientation can be modified the same way they are selected in the Creation window.\nClick Apply to confirm the modification, Repeat to create a new wall component with the same parameters, Dismiss to close the Modify General Wall window or Refresh to discard any modification and display the original attributes.\nTo modify a connected element, select it in the Go to connected element drop-down list at the bottom of the Building Applications window. The application automatically navigates to the element and a Modification window is displayed.\n\n\n\nCreation\nApply\nRepeat\nDismiss\nModify General Wall\nRefresh\nGo to connected element\nModification"}
{"Headers": "Ladders and Stairs", "Content": "The Building application provides functionality to model representations of ladders, handrailing and stairs.\nWithin the application the user can model:\nSteel Ladders (Vertical and Inclined)\nStraight and Curved Steel Handrailing\nConcrete Stairs and Landings\nSteel Stairs and Landings.\nSteel Ladders (Vertical and Inclined)\nSteel Ladders (Vertical and Inclined)\nStraight and Curved Steel Handrailing\nStraight and Curved Steel Handrailing\nConcrete Stairs and Landings\nConcrete Stairs and Landings\nSteel Stairs and Landings.\nSteel Stairs and Landings.\n\n\n"}
{"Headers": "Create Ladder", "Content": "Referring to the hierarchy, a ladder element must reside below an existing group element with a purpose set to Free.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Group element is the CE.\n\nTo represent a ladder, the application uses a number soft element types below a Group element (GENSEC).\n\nBelow the GENSEC (used to represent the Ladder Component) a SPINE element is used to store position information and a TMPL element used to store the geometry elements.\nOn the Building tab, in the Create group, select Ladder in the Create Element drop-down list.\nClick Create Element to display the Create Ladder window.\n\nBy default in the Naming pane of the Create Ladders window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Default Material drop-down list by default is set to Pyrocrete, the default material can be changed to another suitable material. From the Default Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight. The density of the material selected is shown in a tooltip.\nIn the Assembly pane of the Create Ladder window, by default None is displayed. The user can add a selected assembly if required. Refer to Create Assemblies for further information.\nClick Apply to create the Ladder element. The Modify Ladder window is displayed and the Ladder element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Ladder for further information.\nTo cancel the creation of the ladder, click Dismiss. If the user navigates to another element, the Modify Ladder window closes automatically.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\nNote:\nIt is also possible to create a ladder with AVEVA E3D Design using the Stairs, Ladders and Handrails application. On the Stairs Ladders and Handrails tab, in the Create group, click Rung Ladder.\n\n\n\nNaming\nCreate Assemblies\nModify Ladder\nSelect Structural Element\nBuilding Applications\nGroup\nCE\nBuilding\nCreate\nLadder\nCreate Element\nCreate Element\nCreate Ladder\nNaming\nCreate Ladders\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nDefault Material\nPyrocrete\nDefault Material\nAssembly\nCreate Ladder\nNone\nCreate Assemblies\nApply\nLadder\nModify\nLadder\nLadder\nBuilding Applications\nModify Ladder\nDismiss\nModify Ladder\nNote:\nAVEVA E3D Design\nStairs, Ladders and Handrails\nStairs Ladders and Handrails\nCreate\nRung Ladder"}
{"Headers": "Modify Ladder", "Content": "All the tasks associated with the modification of the ladder element can be performed from the Modify Ladder window.\n\nThe material can be modified the same way it is selected in the Create Ladder window. Refer to Create Concrete Flight for further information.\nClick Apply to confirm the modification, Repeat to create a new ladder with the same parameters, Dismiss to close the Modify Ladder window or Refresh to discard any modifications and display the original attributes.\n\n\n\nCreate Concrete Flight\nModify Ladder\nCreate Ladder\nCreate Concrete Flight\nApply\nRepeat\nDismiss\nModify Ladder\nRefresh"}
{"Headers": "Create Ladder Component", "Content": "Referring to the hierarchy, a ladder component element must reside below an existing ladder element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Ladder element is the CE.\n\nOn the Building tab, in the Create group, by default Rung Ladder is displayed in the Create Element drop-down list.\nClick Create Element to display the Creation Ladder window.\n\nBy default in the Naming pane of the Create Ladders window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Material drop-down list by default is set to MS-BS4360, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight. The density of the material selected is shown in a tooltip.\n\n\n\nNaming\nSelect Structural Element\nBuilding Applications\nLadder\nCE\nBuilding\nCreate\nRung Ladder\nCreate Element\nCreate Element\nCreation Ladder\nNaming\nCreate Ladders\nName\nNaming\nMaterial\nMS-BS4360\nMaterial"}
{"Headers": "Select the Ladder Options", "Content": "If the user requires standard stringers, select the Standard option in the Uprights drop\u2011down list. If the user requires reinforced stringers, select the Reinforced option.\nIf the user requires a cage, select the With option in the Cage drop-down list. Otherwise, select the Without option.\nIf the user requires an exit cage, select the With option in the Exit Cage drop-down list. Otherwise select the Without option.\nIf the user requires a gate, select the With option in the Gate drop-down list. Otherwise, select the Without option. Enter the distance between the axis of the ladder and the gate in the Gate distance field. To measure the distance click Measure Distance which invokes the Positioning Control window. The user is prompted to pick the start and end points.\nSelect the exit using the Exit drop-down list.\n\nEnter the distance between the axis of the ladder and the rungs in the Offset field. To measure the distance click Measure Offset which invokes the Positioning Control window. The user is prompted to pick the start and end points.\n\n\n\nStandard\nUprights\nReinforced\nWith\nCage\nWithout\nExit\n\nWithout\nWith\nGate\nWithout\nGate distance\nExit\nOffset"}
{"Headers": "Start Position and Height of the Ladder", "Content": "The user must first select the position and height of the ladder, the default position is the origin of the level with an upward (U) direction with respect to the level and a height of 4500.\n\nThere are a number of methods to select the position and height of the ladder:\nIn the graphical view, the positions proposed are shown by an arrow between the start and end.\nEnter an angle in the Rotation field. An angle may have the following forms:\ndecimal degrees\ndegrees, minutes and seconds\ndecimal grades.\nBy default the rotation is zero.\nAlternatively, click Rotate angle using two picks to invoke the Positioning Control window allowing the user to make graphically selections of existing elements to establish the rotation angle.\n\nClick Apply to create the ladder. The Modification ladder window replaces the Creation Ladder window. Enter a valid name in the Name field to activate it.\nTo cancel the creation of the ladder, click Dismiss. If the user navigates to another element, the Modification Ladder window closes automatically.\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades.\nEnter the values in the east, north and up fields of the Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Padlock to unlock it. If the direction is locked, the bottom position is adjusted for the direction. Otherwise the direction is calculated between both positions. The height is always calculated between both positions.\nClick Pick Top Level to select the top position in the graphical view to invoke the Positioning Control window. The user is prompted to pick the position. To avoid changing a desired value in a field, click Padlock to lock it. If the direction is locked, the bottom position is adjusted for the direction. Otherwise the direction is calculated between both positions. The height is always calculated between both positions.\nEnter the absolute top level (wrt World) in the Top Level field. If the height is locked, the bottom level adapts. If the height is not locked, the height adapts.\nClick Pick level which invokes the Positioning Control window. Pick a position in the graphical view to set the top level. If the height is locked, the bottom level adapts. If the height is not locked, the height adapts.\nEnter the value of the height in the Height field. The top position is adjusted to suit the new height.\nClick Measure to measure the height to invoke the Positioning Control window. The user is prompted to pick the start and end of the ladder. The top position is adjusted to suit the new height.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the height is locked, the level adapts. If the height is not locked, the height adapts.\nClick Pick level which invokes the Positioning Control window. Pick a position in the graphical view to set the bottom level. If the height is locked, the top level adapts. If the height is not locked, the height adapts.\nEnter the values in the Direction field. The direction is always shown with respect to the level. If the direction is locked, click Padlock to unlocked it. The end position is adjusted to suit the new direction and the existing height.\nClick Pick surface or edge to define direction to select the direction in the graphical view. The end position is adjusted to suit the new direction and the existing height. To reverse the direction, click Reverse Direction.\nEnter the values in the east, north and up fields of the Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Padlock to unlock it. If the direction is locked, the bottom position is adjusted for the direction. Otherwise the direction is calculated between both positions. The height is always calculated between both positions.\nEnter the values in the east, north and up fields of the Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Padlock to unlock it. If the direction is locked, the bottom position is adjusted for the direction. Otherwise the direction is calculated between both positions. The height is always calculated between both positions.\nClick Pick Top Level to select the top position in the graphical view to invoke the Positioning Control window. The user is prompted to pick the position. To avoid changing a desired value in a field, click Padlock to lock it. If the direction is locked, the bottom position is adjusted for the direction. Otherwise the direction is calculated between both positions. The height is always calculated between both positions.\nClick Pick Top Level to select the top position in the graphical view to invoke the Positioning Control window. The user is prompted to pick the position. To avoid changing a desired value in a field, click Padlock to lock it. If the direction is locked, the bottom position is adjusted for the direction. Otherwise the direction is calculated between both positions. The height is always calculated between both positions.\nEnter the absolute top level (wrt World) in the Top Level field. If the height is locked, the bottom level adapts. If the height is not locked, the height adapts.\nEnter the absolute top level (wrt World) in the Top Level field. If the height is locked, the bottom level adapts. If the height is not locked, the height adapts.\nClick Pick level which invokes the Positioning Control window. Pick a position in the graphical view to set the top level. If the height is locked, the bottom level adapts. If the height is not locked, the height adapts.\nClick Pick level which invokes the Positioning Control window. Pick a position in the graphical view to set the top level. If the height is locked, the bottom level adapts. If the height is not locked, the height adapts.\nEnter the value of the height in the Height field. The top position is adjusted to suit the new height.\nEnter the value of the height in the Height field. The top position is adjusted to suit the new height.\nClick Measure to measure the height to invoke the Positioning Control window. The user is prompted to pick the start and end of the ladder. The top position is adjusted to suit the new height.\nClick Measure to measure the height to invoke the Positioning Control window. The user is prompted to pick the start and end of the ladder. The top position is adjusted to suit the new height.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the height is locked, the level adapts. If the height is not locked, the height adapts.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the height is locked, the level adapts. If the height is not locked, the height adapts.\nClick Pick level which invokes the Positioning Control window. Pick a position in the graphical view to set the bottom level. If the height is locked, the top level adapts. If the height is not locked, the height adapts.\nClick Pick level which invokes the Positioning Control window. Pick a position in the graphical view to set the bottom level. If the height is locked, the top level adapts. If the height is not locked, the height adapts.\nEnter the values in the Direction field. The direction is always shown with respect to the level. If the direction is locked, click Padlock to unlocked it. The end position is adjusted to suit the new direction and the existing height.\nEnter the values in the Direction field. The direction is always shown with respect to the level. If the direction is locked, click Padlock to unlocked it. The end position is adjusted to suit the new direction and the existing height.\nClick Pick surface or edge to define direction to select the direction in the graphical view. The end position is adjusted to suit the new direction and the existing height. To reverse the direction, click Reverse Direction.\nClick Pick surface or edge to define direction to select the direction in the graphical view. The end position is adjusted to suit the new direction and the existing height. To reverse the direction, click Reverse Direction.\n123.25\n123.25\n123.25\n123\u00b015'05'' or 123d15m05s\n123\u00b015'05'' or 123d15m05s\n123\u00b015'05'' or 123d15m05s\n130G12\n130G12\n130G12\n\n\n\nPosition\nWrt\nPadlock\nwrt\nTop Level\nHeight\nwrt\nBottom Level\nDirection\nPadlock\nRotation\nAlternatively, click Rotate angle using two picks\ninvoke the Positioning Control\nallowing the user to make graphically selections of existing elements to establish the rotation angle.\nApply\nModification ladder\nName\nDismiss\nModification Ladder"}
{"Headers": "Modify Ladder Component", "Content": "All the tasks associated with the modification of the ladder component element can be performed from the Modification ladder window.\n\nThe material, options, positions and orientation can be modified the same way they are selected in the Creation Ladder window.\n\n\n\nModification ladder"}
{"Headers": "Create Staircase", "Content": "Stairs are used to provide access between different levels of the model. Defined as a series of stair flights and landings, the layout is controlled by the allowable going and rise of an applied standard.\nThe choice between concrete and steel is decided based on which Material element the stair is below.\nTo represent stairs, the application uses a number soft element types below a Group element.\nReferring to the hierarchy, a stair element must reside below an existing group element with a purpose set to Free.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Group element is the CE.\n\nThe hierarchy in the Model Explorer is displayed as shown.\n\nBelow the Flight and Landing handrail elements there a number of Sub Component elements that can be created to represent additional features (for example: Plate, Hole, and Reservation and so on.). These can be found as SBFI elements below a PANE or FLOOR.\nOn the Building tab, in the Create group, select Concrete Staircase, Steel Staircase or Spiral Staircase in the Create Element drop-down list.\nClick Create Element to display the Create Concrete Staircase window.\n\nBy default in the Naming pane of the Create Concrete Staircase window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Default Material drop-down list by default is set to Pyrocrete, the default material can be changed to another suitable material. From the Default Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight. The density of the material selected is shown in a tooltip.\nIn the Assembly pane of the Create Concrete Staircase window, by default None is displayed. The user can add a selected assembly if required. Refer to Create Assemblies for further information.\nClick Apply to create the Concrete Staircase element. The Modify Concrete Staircase window is displayed and the Concrete Staircase element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Concrete Staircase for further information.\nTo cancel the creation of the concrete staircase, click Dismiss. If the user navigates to another element, the window closes automatically.\nThe Staircase act as a storage element.\nThe Flight and Landing elements define the shape.\nThe Staircase act as a storage element.\nThe Staircase act as a storage element.\nThe Flight and Landing elements define the shape.\nThe Flight and Landing elements define the shape.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\nNote:\nIt is also possible to create a staircase with AVEVA E3D Design using the Stairs, Ladders and Handrails application. On the Stairs Ladders and Handrails tab, in the Create group, click Stair Flight.\n\n\n\nNaming\nCreate Assemblies\nModify Concrete Staircase\nSelect Structural Element\nBuilding Applications\nGroup\nCE\nBuilding\nCreate\nConcrete Staircase\nSteel Staircase\nSpiral Staircase\nCreate Element\nCreate Element\nCreate Concrete Staircase\nNaming\nCreate Concrete Staircase\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nDefault Material\nPyrocrete\nDefault Material\nAssembly\nCreate Concrete Staircase\nNone\nCreate Assemblies\nApply\nStaircase\nModify\nStaircase\nStaircase\nBuilding Applications\nModify Concrete Staircase\nDismiss\nNote:\nAVEVA E3D Design\nStairs, Ladders and Handrails\nStairs Ladders and Handrails\nCreate\nStair Flight"}
{"Headers": "Modify Concrete Staircase", "Content": "All the tasks associated with the modification of the concrete staircase element can be performed from the Modify Concrete Staircase window.\n\nThe material can be modified the same way it is selected in the Create Concrete Staircase window.\nTo confirm the modification, click Apply.\nTo create a new Concrete Staircase with the same parameters, click Repeat. The Create Concrete Staircase window is then displayed.\nClick Dismiss to close the Create Concrete Staircase window.\nIf you use AVEVA E3D Design to change the staircase, click Refresh to display the current attributes.\n\n\n\nModify Concrete Staircase\nCreate\nStaircase\nApply\nStaircase\nRepeat\nCreate\nStaircase\nDismiss\nCreate\nStaircase\nAVEVA E3D Design\nRefresh"}
{"Headers": "Create Concrete Flight", "Content": "Referring to the hierarchy, a concrete flight element must reside below an existing concrete staircase element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Concrete Staircase element is the CE.\n\nOn the Building tab, in the Create group, by default Flight is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Concrete Flight window.\n\nBy default in the Naming pane of the Create Concrete Flight window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Material drop-down list by default is set to Pyrocrete, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight, the density of the material selected is shown in a tooltip.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nSelect Structural Element\nBuilding Applications\nConcrete Staircase\nCE\nBuilding\nCreate\nFlight\nCreate Element\nCreate Element\nCreate Concrete Flight\nNaming\nCreate Concrete Flight\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nMaterial\nPyrocrete\nMaterial"}
{"Headers": "The Height of the Flight", "Content": "The user must define the top and bottom levels of the flight of stairs:\n\nThere are a number of ways to select the top and bottom levels of the flight:\nIf the user does not want the height to adapt to level changes, click Padlock to lock it.\nThe height of the flight is used to calculate the number of steps, the riser and the going in the following way:\nThe optimum riser is defined by the application assistant in a configuration file (for example: 180 according to CRT).\nThe average stride is also defined in the configuration file (for example: 630 according to CRT).\nIf the maximum number of steps (also defined in the configuration file) is exceeded a warning message is shown.\nEnter the absolute top level (wrt World) in the Top Level field. If the height is locked or the value is less than the bottom level, the bottom level adapts. If the height is not locked, the height adapts.\nSelect the top level using a position in the graphical view and click Pick Top Level. The view's mode changes and the Positioning Control window is displayed. Follow the prompt to Pick Top Level (Snap) Snap:. If the height is locked or the value is less than the bottom level, the bottom level adapts. If the height is not locked, the height adapts.\nEnter the height in the Height field. If the height is locked, click Padlock to unlock it.\nMeasure the height. Click Measure Height and the Positioning Control window is displayed. The user is prompted to Height:Pick Start (Snap) Snap: and Height:Pick End (Snap) Snap:. The bottom level or top level adapts as appropriate.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the height is locked or the value is greater than the top level, the top level adapts. If the height is not locked, the height adapts.\nSelect the bottom level using a position in the graphical view and click Pick Bottom Level. The view's mode changes and the Positioning Control window is displayed. Follow the prompt to Pick Bottom Level (Snap) Snap:. If the height is locked or the value is less than the top level, the top level adapts. If the height is not locked, the height adapts.\nEnter the absolute top level (wrt World) in the Top Level field. If the height is locked or the value is less than the bottom level, the bottom level adapts. If the height is not locked, the height adapts.\nEnter the absolute top level (wrt World) in the Top Level field. If the height is locked or the value is less than the bottom level, the bottom level adapts. If the height is not locked, the height adapts.\nSelect the top level using a position in the graphical view and click Pick Top Level. The view's mode changes and the Positioning Control window is displayed. Follow the prompt to Pick Top Level (Snap) Snap:. If the height is locked or the value is less than the bottom level, the bottom level adapts. If the height is not locked, the height adapts.\nSelect the top level using a position in the graphical view and click Pick Top Level. The view's mode changes and the Positioning Control window is displayed. Follow the prompt to Pick Top Level (Snap) Snap:. If the height is locked or the value is less than the bottom level, the bottom level adapts. If the height is not locked, the height adapts.\nEnter the height in the Height field. If the height is locked, click Padlock to unlock it.\nEnter the height in the Height field. If the height is locked, click Padlock to unlock it.\nMeasure the height. Click Measure Height and the Positioning Control window is displayed. The user is prompted to Height:Pick Start (Snap) Snap: and Height:Pick End (Snap) Snap:. The bottom level or top level adapts as appropriate.\nMeasure the height. Click Measure Height and the Positioning Control window is displayed. The user is prompted to Height:Pick Start (Snap) Snap: and Height:Pick End (Snap) Snap:. The bottom level or top level adapts as appropriate.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the height is locked or the value is greater than the top level, the top level adapts. If the height is not locked, the height adapts.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the height is locked or the value is greater than the top level, the top level adapts. If the height is not locked, the height adapts.\nSelect the bottom level using a position in the graphical view and click Pick Bottom Level. The view's mode changes and the Positioning Control window is displayed. Follow the prompt to Pick Bottom Level (Snap) Snap:. If the height is locked or the value is less than the top level, the top level adapts. If the height is not locked, the height adapts.\nSelect the bottom level using a position in the graphical view and click Pick Bottom Level. The view's mode changes and the Positioning Control window is displayed. Follow the prompt to Pick Bottom Level (Snap) Snap:. If the height is locked or the value is less than the top level, the top level adapts. If the height is not locked, the height adapts.\n\n\n\nwrt\nTop Level\nPositioning Control\nHeight\nPositioning Control\nwrt\nBottom Level\nPositioning Control\nOptimum riser\nAverage stride"}
{"Headers": "Stair Properties", "Content": "The properties of the flight of stairs must now be defined:\n\nEnter the width of the step in the Width field. Alternatively click Measure Step Width to invoke the Positioning Control window. The user is prompted to Height:Pick Start (Snap) Snap: and Height:Pick End (Snap) Snap:. The field is locked if the flight is not the first in a series of flights of steps. Click Padlock to unlock it.\nEnter the value of the Going in the Going field. Alternatively click Measure Going to invoke the Positioning Control window. The user is prompted to Height:Pick Start (Snap) Snap: and Height:Pick End (Snap) Snap:. The field is locked if the flight is not the first in a series of flights of steps. Click Padlock to unlock it.\nEnter the number of steps in the Step Number field. If the maximum number is exceeded, a warning message is shown.\nEnter the height of the step in the Riser field. Alternatively click Measure Riser to invoke the Positioning Control window. The user is prompted to Height:Pick Start (Snap) Snap: and Height:Pick End (Snap) Snap:. The field is locked if the flight is not the first in a series of flights of steps. Click Padlock to unlock it.\nEnter the value of the waist in the Waist field. Alternatively click Measure Waist to invoke the Positioning Control window. The user is prompted to Height:Pick Start (Snap) Snap: and Height:Pick End (Snap) Snap:. If the waist value is too small a warning message is shown and the value adjusted accordingly.\n\n\n\nWidth\nPositioning Control\nGoing\nPositioning Control\nStep Number\nRiser\nPositioning Control\nWaist\nPositioning Control"}
{"Headers": "Top Landing", "Content": "The top landing of the concrete flight must now be set:\n\nClose the drop-down list, the standard top configuration is used.\n\nAlternatively open the Top Landing drop-down list:\nType the offset from the top step to the landing into the Offset frame.\nClick Pick Top Landing Elevation and graphically pick the level of the top step to invoke the Positioning Control window. Follow the prompt Pick Top Landing Elevation (Snap) Snap:.\nSelect offset to rise of value.\nSelect offset to zero.\nType the thickness of the top landing into the Thickness frame.\nClick Pick Top Landing to graphically select the landing. Follow the prompt Pick Top Landing:. The thickness of the landing is the same as the floor or screed selected.\nType the offset from the top step to the landing into the Offset frame.\nType the offset from the top step to the landing into the Offset frame.\nClick Pick Top Landing Elevation and graphically pick the level of the top step to invoke the Positioning Control window. Follow the prompt Pick Top Landing Elevation (Snap) Snap:.\nClick Pick Top Landing Elevation and graphically pick the level of the top step to invoke the Positioning Control window. Follow the prompt Pick Top Landing Elevation (Snap) Snap:.\nSelect offset to rise of value.\nSelect offset to rise of value.\nSelect offset to zero.\nSelect offset to zero.\nType the thickness of the top landing into the Thickness frame.\nType the thickness of the top landing into the Thickness frame.\nClick Pick Top Landing to graphically select the landing. Follow the prompt Pick Top Landing:. The thickness of the landing is the same as the floor or screed selected.\nClick Pick Top Landing to graphically select the landing. Follow the prompt Pick Top Landing:. The thickness of the landing is the same as the floor or screed selected.\n\n\n\nPositioning Control"}
{"Headers": "Bottom Landing", "Content": "The bottom landing of the concrete flight must now be set:\n\nClose the drop-down list. The standard bottom configuration is used.\n\nAlternatively open the Bottom Landing drop-down list:\nType the offset from the bottom step to the landing into the Offset frame.\nClick Pick Bottom Landing Elevation and graphically pick the level of the bottom step to invoke the Positioning Control window. Follow the prompt Pick Bottom Landing Elevation (Snap) Snap:.\nSelect offset to rise value.\nSelect to offset to zero.\nType the thickness of the bottom landing into the Thickness frame.\nClick Pick Bottom Landing to graphically select the landing. Follow the prompt Pick Bottom Landing:. The thickness of the landing is the same as the floor or screed selected.\nType the offset from the bottom step to the landing into the Offset frame.\nType the offset from the bottom step to the landing into the Offset frame.\nClick Pick Bottom Landing Elevation and graphically pick the level of the bottom step to invoke the Positioning Control window. Follow the prompt Pick Bottom Landing Elevation (Snap) Snap:.\nClick Pick Bottom Landing Elevation and graphically pick the level of the bottom step to invoke the Positioning Control window. Follow the prompt Pick Bottom Landing Elevation (Snap) Snap:.\nSelect offset to rise value.\nSelect offset to rise value.\nSelect to offset to zero.\nSelect to offset to zero.\nType the thickness of the bottom landing into the Thickness frame.\nType the thickness of the bottom landing into the Thickness frame.\nClick Pick Bottom Landing to graphically select the landing. Follow the prompt Pick Bottom Landing:. The thickness of the landing is the same as the floor or screed selected.\nClick Pick Bottom Landing to graphically select the landing. Follow the prompt Pick Bottom Landing:. The thickness of the landing is the same as the floor or screed selected.\n\n\n\nPositioning Control"}
{"Headers": "Bottom Foot", "Content": "Close the drop-down list, the standard bottom foot configuration is used.\n\nAlternatively open the Bottom Foot drop-down list:\nType the height of the foot into the Height frame.\nClick Pick top of foot elevation and graphically pick the top of the foot to invoke the Positioning Control window. Follow the prompt Pick top of foot elevation (Snap) Snap:.\nType the length of the foot into the Length frame.\nClick Pick horizontal extent of foot and graphically pick the top of the foot to invoke the Positioning Control window. Follow the prompt Pick horizontal extent of foot (Snap) Snap:.\nType the height of the foot into the Height frame.\nType the height of the foot into the Height frame.\nClick Pick top of foot elevation and graphically pick the top of the foot to invoke the Positioning Control window. Follow the prompt Pick top of foot elevation (Snap) Snap:.\nClick Pick top of foot elevation and graphically pick the top of the foot to invoke the Positioning Control window. Follow the prompt Pick top of foot elevation (Snap) Snap:.\nType the length of the foot into the Length frame.\nType the length of the foot into the Length frame.\nClick Pick horizontal extent of foot and graphically pick the top of the foot to invoke the Positioning Control window. Follow the prompt Pick horizontal extent of foot (Snap) Snap:.\nClick Pick horizontal extent of foot and graphically pick the top of the foot to invoke the Positioning Control window. Follow the prompt Pick horizontal extent of foot (Snap) Snap:.\n\n\n\nPositioning Control\nPositioning Control"}
{"Headers": "Select the Justification", "Content": "Select the justification of the flight. Justification is used to position a flight next to a wall or in the centre of a landing.\n\n\n\n"}
{"Headers": "Select the Sense", "Content": "To create a flight after the other components of the stairs and to define the bottom position of the flight, select Ascending option.\n\nTo create a flight before the other components of the stairs and to define the top position of the flight, select Descending option.\n\n\n\nAscending\nDescending"}
{"Headers": "Position of the Flight", "Content": "There are two ways to select the position:\nEnter the values for east, north and up in the Position frame. The user can change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinate Locked to unlock it.\nClick Pick Position to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Position (Snap) Snap:. To avoid changing a desired value in a field, click Coordinate unlocked to lock it.\nEnter the values for east, north and up in the Position frame. The user can change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinate Locked to unlock it.\nEnter the values for east, north and up in the Position frame. The user can change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinate Locked to unlock it.\nClick Pick Position to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Position (Snap) Snap:. To avoid changing a desired value in a field, click Coordinate unlocked to lock it.\nClick Pick Position to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Position (Snap) Snap:. To avoid changing a desired value in a field, click Coordinate unlocked to lock it.\n\n\n\nPosition\nWrt\nPositioning Control"}
{"Headers": "Direction of the Flight", "Content": "In the graphical view, an arrow shows the direction of the flight.\nClick Apply to create the concrete flight. The Modify Concrete Flight window replaces the Create Concrete Flight window. Enter a valid name in the Name field to activate it.\nTo cancel the creation of the concrete flight, click Dismiss. Navigate to another element and the Create Concrete Flight window closes automatically.\nEnter the direction in the Direction field.\nClick Pick surface or edge to define direction to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Face or Edge:. Click Reverse Direction to reverse the direction.\nEnter the direction in the Direction field.\nEnter the direction in the Direction field.\nClick Pick surface or edge to define direction to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Face or Edge:. Click Reverse Direction to reverse the direction.\nClick Pick surface or edge to define direction to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Face or Edge:. Click Reverse Direction to reverse the direction.\n\n\n\nDirection\nPositioning Control\nApply\nModify Concrete Flight\nCreate Concrete Flight window\nName\nDismiss\nCreate Concrete Flight"}
{"Headers": "Modify Flight", "Content": "All the tasks associated with the modification of the concrete flight element can be performed from the Modify Concrete Flight window.\n\nTo modify the material, properties, position and direction, refer to Create Concrete Flight for further information.\n\n\n\nCreate Concrete Flight\nModify Concrete Flight\nCreate Concrete Flight"}
{"Headers": "Move Flights and Landings", "Content": "To move the flights and landings above the current flight, in the Sense area of the window select the Ascending direction.\n\nTo move the flights and landings below the current flight, select the Descending direction\n\nTo confirm the modification, click Apply.\nTo create a landing component, click Create Landing. The Create Landing window is displayed. Refer to Create Landing for further information.\nClick Dismiss to close the Modify Concrete Flight window.\nIf you use AVEVA E3D Design to change the concrete flight, click Refresh to display the current attributes.\n\n\n\nCreate Landing\nAscending\nDescending\nApply\nCreate Landing\nCreate Landing\nCreate Landing\nDismiss\nModify Concrete Flight\nAVEVA E3D Design\nRefresh"}
{"Headers": "Create Landing", "Content": "Referring to the hierarchy, a landing element must reside below an existing staircase element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Concrete Staircase element is the CE.\n\nOn the Building tab, in the Create group, select Landing in the Create Element drop-down list.\nClick Create Element to display the Create Landing window.\n\nBy default in the Naming pane of the Create Landing window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Material drop-down list by default is set to Pyrocrete, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight, the density of the material selected is shown in a tooltip.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nSelect Structural Element\nBuilding Applications\nConcrete Staircase\nCE\nBuilding\nCreate\nLanding\nCreate Element\nCreate Element\nCreate Landing\nNaming\nCreate Landing\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nMaterial\nPyrocrete\nMaterial"}
{"Headers": "Landing Thickness", "Content": "The thickness of the landing must now be set:\n\nTo stop the thickness to adapting to level changes, click Thickness changes to suit levels to lock the thickness.\nThe default top level is the level of the last step of the preceding flight. The default thickness is 300mm.\nEnter the absolute top level (wrt World) in the Top Level field.\nSelect the top level using a position in the graphical view and click Pick Top Level. The view's mode changes and the Positioning Control window is displayed. Follow the prompt to Pick Top Level (Snap) Snap:. If the height is locked or the value is less than the bottom level, the bottom level adapts. If the height is not locked, the height adapts.\nEnter the thickness in the Thickness field. If the height is locked, click Thickness changes to suit levels to unlock it.\nMeasure the thickness. Click Measure Height and the Positioning Control window is displayed. The user is prompted to Height:Pick Start (Snap) Snap: and Height:Pick End (Snap) Snap:. The bottom level or top level adapts as appropriate.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the height is locked or the value is greater than the top level, the top level adapts. If the height is not locked, the height adapts.\nEnter the absolute top level (wrt World) in the Top Level field.\nEnter the absolute top level (wrt World) in the Top Level field.\nSelect the top level using a position in the graphical view and click Pick Top Level. The view's mode changes and the Positioning Control window is displayed. Follow the prompt to Pick Top Level (Snap) Snap:. If the height is locked or the value is less than the bottom level, the bottom level adapts. If the height is not locked, the height adapts.\nSelect the top level using a position in the graphical view and click Pick Top Level. The view's mode changes and the Positioning Control window is displayed. Follow the prompt to Pick Top Level (Snap) Snap:. If the height is locked or the value is less than the bottom level, the bottom level adapts. If the height is not locked, the height adapts.\nEnter the thickness in the Thickness field. If the height is locked, click Thickness changes to suit levels to unlock it.\nEnter the thickness in the Thickness field. If the height is locked, click Thickness changes to suit levels to unlock it.\nMeasure the thickness. Click Measure Height and the Positioning Control window is displayed. The user is prompted to Height:Pick Start (Snap) Snap: and Height:Pick End (Snap) Snap:. The bottom level or top level adapts as appropriate.\nMeasure the thickness. Click Measure Height and the Positioning Control window is displayed. The user is prompted to Height:Pick Start (Snap) Snap: and Height:Pick End (Snap) Snap:. The bottom level or top level adapts as appropriate.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the height is locked or the value is greater than the top level, the top level adapts. If the height is not locked, the height adapts.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the height is locked or the value is greater than the top level, the top level adapts. If the height is not locked, the height adapts.\n\n\n\nwrt\nTop Level\nPositioning Control\nThickness\nPositioning Control\nwrt\nBottom Level"}
{"Headers": "Enter the Offset", "Content": "For a landing after a flight, select the offset.\n\n\n\n"}
{"Headers": "Select the Sense", "Content": "\n\n\nAscending\nDescending"}
{"Headers": "Select the Shape", "Content": "Select the shape using the Shape drop-down list.\nTo specify a rectangular shape, select the Rectangular option. To define the length and width:\nTo specify a circular shape, select the Circular option. To define the diameter:\nTo define a complex shape, initiate the 2D editor using the Complex option.\n\nThe 2D Contour Editor window allows the user to define a series of points, in a single plane, that are used to define the footprint of the landing.\nEnter the values in the Length and Width fields.\nMeasure the length. Click Measure Length and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nMeasure the length. Click Measure Width and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nClick Pick Corners to pick two opposite corners. The Positioning Control window is displayed. The user is prompted to Pick first corner (Snap) Snap: and Pick second corner(Snap) Snap:.\nDefine the length, click Pick Length by Position The Positioning Control window is displayed. The user is prompted to Pick length by position (Snap) Snap:.\nDefine the width, click Pick Width by Position The Positioning Control window is displayed. The user is prompted to Pick width by position (Snap) Snap:.\nEnter the values in the Length and Width fields.\nEnter the values in the Length and Width fields.\nMeasure the length. Click Measure Length and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nMeasure the length. Click Measure Length and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nMeasure the length. Click Measure Width and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nMeasure the length. Click Measure Width and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nClick Pick Corners to pick two opposite corners. The Positioning Control window is displayed. The user is prompted to Pick first corner (Snap) Snap: and Pick second corner(Snap) Snap:.\nClick Pick Corners to pick two opposite corners. The Positioning Control window is displayed. The user is prompted to Pick first corner (Snap) Snap: and Pick second corner(Snap) Snap:.\nDefine the length, click Pick Length by Position The Positioning Control window is displayed. The user is prompted to Pick length by position (Snap) Snap:.\nDefine the length, click Pick Length by Position The Positioning Control window is displayed. The user is prompted to Pick length by position (Snap) Snap:.\nDefine the width, click Pick Width by Position The Positioning Control window is displayed. The user is prompted to Pick width by position (Snap) Snap:.\nDefine the width, click Pick Width by Position The Positioning Control window is displayed. The user is prompted to Pick width by position (Snap) Snap:.\nEnter the value in the Diameter field.\nMeasure the Diameter. Click Measure Diameter and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nClick Pick position radius to define the diameter. the Positioning Control window is displayed. The user is prompted to Pick position on radius (Snap) Snap:.\nEnter the value in the Diameter field.\nEnter the value in the Diameter field.\nMeasure the Diameter. Click Measure Diameter and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nMeasure the Diameter. Click Measure Diameter and the Positioning Control window is displayed. The user is prompted to Measure Length:Pick Start (Snap) Snap: and Measure Length:Pick End (Snap) Snap:.\nClick Pick position radius to define the diameter. the Positioning Control window is displayed. The user is prompted to Pick position on radius (Snap) Snap:.\nClick Pick position radius to define the diameter. the Positioning Control window is displayed. The user is prompted to Pick position on radius (Snap) Snap:.\n\n\n\nShape\nRectangular\nLength\nWidth\nPositioning Control\nPositioning Control\nPositioning Control\nPositioning Control\nPositioning Control\nCircular\nDiameter\nPositioning Control\nPositioning Control\nComplex\n2D Contour Editor"}
{"Headers": "Reference", "Content": "The Reference is the vertex on a rectangular landing from which the position values are calculated in the graphical view. In the figure below the Reference is at vertex 6.\nTo change the Reference select the vertex from the drop-down list. A bounding box shows the new position of the landing. If it does not put the landing in the correct position select a different vertex from the drop-down list.\nFor circular and complex landings the reference is always the centre.\n\n\n\n"}
{"Headers": "Select the Position", "Content": "Enter the values in the fields for east, north and up in the Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinate Locked to unlock it.\nClick Pick Position to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Position (Snap) Snap:. To avoid changing a desired value in a field, click Coordinate unlocked to lock it.\nEnter the values in the fields for east, north and up in the Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinate Locked to unlock it.\nEnter the values in the fields for east, north and up in the Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinate Locked to unlock it.\nClick Pick Position to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Position (Snap) Snap:. To avoid changing a desired value in a field, click Coordinate unlocked to lock it.\nClick Pick Position to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Position (Snap) Snap:. To avoid changing a desired value in a field, click Coordinate unlocked to lock it.\n\n\n\nPosition\nWrt\nPositioning Control"}
{"Headers": "Direction of the Flight", "Content": "In the graphical view, an arrow shows the direction of the flight.\nClick Apply to create the landing. The Modify Landing window replaces the Create Landing window. Enter a valid name in the Name field to activate it.\nTo cancel the creation of the landing, click Dismiss. Navigate to another element and the window closes automatically.\nEnter the direction in the Direction field.\nClick Pick surface or edge to define direction to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Face or Edge:. Click Reverse Direction to reverse the direction.\nEnter the direction in the Direction field.\nEnter the direction in the Direction field.\nClick Pick surface or edge to define direction to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Face or Edge:. Click Reverse Direction to reverse the direction.\nClick Pick surface or edge to define direction to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Face or Edge:. Click Reverse Direction to reverse the direction.\n\n\n\nDirection\nPositioning Control\nApply\nLanding\nCreate Landing window\nName\nDismiss"}
{"Headers": "Modify Landing", "Content": "All the tasks associated with the modification of the landing element can be performed from the Modify Landing window.\n\nThe material, thickness, position, direction and shape can be modified the same way they are selected for creation. Refer to Create Landing for further information.\n\n\n\nCreate Landing\nModify Landing\nCreate Landing"}
{"Headers": "Move Landings and Flights", "Content": "To move the flights and landings above the current landing, from Sense select the Ascending direction.\n\nTo move the flights and landings below the current landing, select the Descending direction.\n\nTo confirm the modification, click Apply.\nTo create a flight component, click Create Flight. The appropriate Create Flight window is then displayed.\nClick Dismiss to close the Modify Landing window.\nIf you use AVEVA E3D Design to change the landing, click Refresh to display the current attributes.\n\n\n\nAscending\nDescending\nApply\nCreate Flight\nCreate Flight\nDismiss\nModify Landing\nAVEVA E3D Design\nRefresh"}
{"Headers": "Create Steel Flight", "Content": "Referring to the hierarchy, a steel flight element must reside below an existing steel staircase element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Steel Staircase element is the CE.\n\nOn the Building tab, in the Create group, by default Flight is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Stair Flight window.\n\nThe functionality of the Create Stair Flight window is explained. Refer to Create Stair Flight for further information.\n\n\n\nCreate Stair Flight\nSelect Structural Element\nBuilding Applications\nSteel Staircase\nCE\nBuilding\nCreate\nFlight\nCreate Element\nCreate Element\nCreate Stair Flight\nCreate Stair Flight\nCreate Stair Flight"}
{"Headers": "Modify Steel Flight", "Content": "All the tasks associated with the modification of the steel flight element can be performed from the Modify Stair Flight window.\n\nThe functionality available for the Modify Stair Flight window is identical to the Create Stair Flight window. Refer to Create Stair Flight for further information.\n\n\n\nCreate Stair Flight\nModify Stair Flight\nModify Stair Flight\nCreate Stair Flight\nCreate Stair Flight"}
{"Headers": "Create Spiral Staircase Component", "Content": "Referring to the hierarchy, a spiral staircase component element must reside below an existing spiral staircase element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Spiral Staircase element is the CE.\n\nOn the Building tab, in the Create group, by default Flight is displayed in the Create Element drop-down list.\nClick Create Element to display the Creation spiral staircase window.\n\nBy default in the Naming pane of the Creation spiral staircase window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Material drop-down list by default is set to Pyrocrete, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight, the density of the material selected is shown in a tooltip.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nSelect Structural Element\nBuilding Applications\nSpiral Staircase\nCE\nBuilding\nCreate\nFlight\nCreate Element\nCreate Element\nCreation spiral staircase\nNaming\nCreation spiral staircase\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nMaterial\nPyrocrete\nMaterial"}
{"Headers": "Select the Properties", "Content": "The properties of the spiral staircase must now be set:\n\nEnter the height of a step in the Riser field.\nMeasure the length. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nEnter the number of steps in the Step number field. The Flight Height changes according to the height from the riser and number of steps.\nEnter the width of a step in the Step width field.\nMeasure the Step Width. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nEnter the value of the inside radius of the newel in the Inside radius field.\nMeasure the Inside Radius. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nEnter the value of the angle of a step in the Step angle field.\nEnter the value of the height of the central core in the Core height field.\nMeasure the Core height. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nEnter the height of a step in the Riser field.\nEnter the height of a step in the Riser field.\nMeasure the length. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nMeasure the length. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nEnter the number of steps in the Step number field. The Flight Height changes according to the height from the riser and number of steps.\nEnter the number of steps in the Step number field. The Flight Height changes according to the height from the riser and number of steps.\nEnter the width of a step in the Step width field.\nEnter the width of a step in the Step width field.\nMeasure the Step Width. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nMeasure the Step Width. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nEnter the value of the inside radius of the newel in the Inside radius field.\nEnter the value of the inside radius of the newel in the Inside radius field.\nMeasure the Inside Radius. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nMeasure the Inside Radius. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nEnter the value of the angle of a step in the Step angle field.\nEnter the value of the angle of a step in the Step angle field.\nEnter the value of the height of the central core in the Core height field.\nEnter the value of the height of the central core in the Core height field.\nMeasure the Core height. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nMeasure the Core height. Click Measure and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\n\n\n\nRiser\nPositioning Control\nStep number\nStep width\nPositioning Control\nInside radius\nPositioning Control\nStep angle\nCore height\nPositioning Control"}
{"Headers": "Select the Position of the Stairs", "Content": "The default position is at the origin of the level.\nEnter the values in the fields for east, north and up in the Centre Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it.\nClick Pick position to select the position in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Position (Snap) Snap:. To avoid changing a desired value in a field, click Coordinates locked to lock it.\nEnter the values in the fields for east, north and up in the Centre Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it.\nEnter the values in the fields for east, north and up in the Centre Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it.\nClick Pick position to select the position in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Position (Snap) Snap:. To avoid changing a desired value in a field, click Coordinates locked to lock it.\nClick Pick position to select the position in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Position (Snap) Snap:. To avoid changing a desired value in a field, click Coordinates locked to lock it.\n\n\n\nCentre Position\nWrt\nPositioning Control"}
{"Headers": "Select the Orientation of the Stairs", "Content": "The default direction is up (U) with respect to the level with a rotation of zero.\nClick Apply to create the spiral staircase component. The Modification Spiral Staircase window replaces the Creation spiral staircase window. Enter a valid name in the Name field to activate it.\nTo cancel the creation of the staircase component, click Dismiss. If the user navigates to another element, the window closes automatically.\nEnter the values in the Direction and Rotation field. The direction is always shown with respect to the level.\nClick Pick surface or edge to define direction to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Face or Edge:. Click Reverse Direction to reverse the direction.\nClick Pick and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nEnter the values in the Direction and Rotation field. The direction is always shown with respect to the level.\nEnter the values in the Direction and Rotation field. The direction is always shown with respect to the level.\nClick Pick surface or edge to define direction to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Face or Edge:. Click Reverse Direction to reverse the direction.\nClick Pick surface or edge to define direction to select the position in the graphical view to invoke the Positioning Control window. Follow the prompt Pick Face or Edge:. Click Reverse Direction to reverse the direction.\nClick Pick and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\nClick Pick and the Positioning Control window is displayed. The user is prompted to Pick Start (Snap) Snap: and Pick End (Snap) Snap:.\n\n\n\nDirection\nRotation\nPositioning Control\nPositioning Control\nApply\nModification\nSpiral Staircase\nCreation spiral staircase\nName\nDismiss"}
{"Headers": "Modify Spiral Staircase Component", "Content": "All the tasks associated with the modification of the spiral staircase component element can be performed from the Modification Spiral Staircase window.\n\nThe material, properties, position and orientation can be modified the same way they are selected for creation. Refer to Create Spiral Staircase Component for further information.\n\n\n\nCreate Spiral Staircase Component\nModification\nSpiral Staircase\nCreate Spiral Staircase Component"}
{"Headers": "Handrail", "Content": "A handrail is usually used to demarcate access, or to provide edge protection to prevent a fall from height. A handrail may be positioned along the edge of a floor, up a stair flight, or simply between two designated positions.\nIn Concrete Building Design, a Handrail element is a SBFR.\nA HANDRA element represents the handrail within the sub-framework.\n\n\n\n"}
{"Headers": "Create Handrail", "Content": "Referring to the hierarchy, a handrail element must reside below an existing group element that can contain handrailing.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Group element is the CE.\n\nOn the Building tab, in the Create group, select Hand Rail in the Create Element drop-down list.\nClick Create Element to display the Create Hand Rail window.\n\nBy default in the Naming pane of the Create Hand Rail window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Default Material drop-down list by default is set to Pyrocrete, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight. The density of the material selected is shown in a tooltip.\nIn the Assembly pane of the Create Hand Rail window, by default None is displayed. The user can add a selected assembly if required. Refer to Create Assemblies for further information.\nClick Apply to create the Handrail element. The Modify Hand Rail window is displayed and the Handrail element is displayed in the Model Explorer and in the Building Applications window. Refer to Modify Ladder for further information.\nTo cancel the creation of the handrail, click Dismiss. If the user navigates to another element, the window closes automatically.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\nNote:\nIt is also possible to create a handrail with AVEVA E3D Design using the Stairs, Ladders and Handrails application. On the Stairs Ladders and Handrails tab, in the Create group, click Handrail.\n\n\n\nNaming\nCreate Assemblies\nModify Ladder\nSelect Structural Element\nBuilding Applications\nGroup\nCE\nBuilding\nCreate\nHand Rail\nCreate Element\nCreate Element\nCreate Hand Rail\nNaming\nCreate Hand Rail\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nDefault Material\nPyrocrete\nMaterial\nAssembly\nCreate Hand Rail\nNone\nCreate Assemblies\nApply\nHandrail\nModify\nHand Rail\nHandrail\nBuilding Applications\nModify Ladder\nDismiss\nNote:\nAVEVA E3D Design\nStairs, Ladders and Handrails\nStairs Ladders and Handrails\nCreate\nHandrail"}
{"Headers": "Modify Handrail", "Content": "All the tasks associated with the modification of the handrail element can be performed from the Modify Hand Rail window.\n\nThe material can be modified the same way it is selected in the Create Hand Rail window. Refer to Modify Handrail for further information.\nClick Apply to confirm the modification, Repeat to create a new handrail with the same parameters, Dismiss to close the Modify Hand Rail window or Refresh to discard any modifications and display the original attributes.\n\n\n\nModify Handrail\nModify Hand Rail\nCreate Hand Rail\nModify Handrail\nApply\nRepeat\nDismiss\nModify Hand Rail\nRefresh"}
{"Headers": "Create Straight/General Handrail", "Content": "Referring to the hierarchy, a straight/general handrail element (component of a handrail) must reside below an existing handrail element. In certain projects, it is possible to create non-cataloged handrailing (configurable by the application assistant). Refer to Modelling Slopes for further information.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Hand Rail element is the CE.\n\nOn the Building tab, in the Create group, select Straight Handrailing or General Handrailing in the Create Element drop-down list.\nClick Create Element to display the Create Handrail window.\n\nThe functionality of the Create Handrail window is explained. Refer to Create Handrail for further information.\n\n\n\nModelling Slopes\nCreate Handrail\nModelling Slopes\nSelect Structural Element\nBuilding Applications\nHand Rail\nCE\nBuilding\nCreate\nStraight Handrailing\nGeneral Handrailing\nCreate Element\nCreate Element\nCreate Handrail\nCreate Handrail\nCreate Handrail"}
{"Headers": "Modify Straight/General Handrail", "Content": "All the tasks associated with the modification of the straight/general handrail element can be performed from the Modify Handrail window.\n\nThe functionality available for the Modify Handrail window is identical to the Create Handrail window. Refer to Create Handrail for further information.\n\n\n\nCreate Handrail\nModify Handrail\nModify Handrail\nCreate Handrail\nCreate Handrail"}
{"Headers": "Create Gate on Grating", "Content": "Referring to the hierarchy, a gate (a sub-component of a grating component) must reside below an existing grating element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Grating Component element is the CE.\n\nOn the Building tab, in the Create group, by default gate is displayed in the Create Element drop-down list.\nClick Create Element to display the Create Sub-component window.\n\nBy default in the Naming pane of the Create Sub-component window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Material drop-down list by default is set according to the type of sub\u2011component but it can be modified. From the Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight. The density of the material selected is shown in a tooltip.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nSelect Structural Element\nBuilding Applications\nGrating Component\nCE\nBuilding\nCreate\ngate\nCreate Element\nCreate Element\n\nNaming\nCreate Sub-component\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nMaterial\nMaterial"}
{"Headers": "Sub-component Specification", "Content": "Choose the sub-component catalogue using the drop-down list in the Catalogue frame. The catalogue is activated by default on the first catalogue available that contains the type of component selected in the main window.\nRead the question displayed between the two lists in the Catalogue frame. Select an answer in the list of answers displayed below until the Selection complete message appears. Click on the question in the list above to reselect a question.\nAs soon as an element in the catalogue is selected, Properties is cleared if there are properties associated with this element.\n\n\n\nCatalogue\nCatalogue\nProperties"}
{"Headers": "Sub-component Properties", "Content": "Click Properties to display the properties of the sub-component.\n\n\n\n\n\nProperties"}
{"Headers": "Select the Face and Segment", "Content": "Choose a face in the faces drop-down list. In the graphical view, the axes show the origin of the face.\n\nNote:\nFor a gate, select the On top face.\n\n\n\nNote:"}
{"Headers": "Position of the Sub-component", "Content": "There various ways to enter the position of the sub-component:\nIn the graphical view, a sphere shows the proposed position. By default the offset is zero.\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/Height/Offset Locked to unlock it.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/Height/Offset Locked to unlock it.\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/Height/Offset Locked to unlock it.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nNote:\nUse a zero value for the displacement (Z).\n\n\n\nDistance\nHeight\nOffset\nPositioning Control\nAngle (X)\nPositioning Control\nNote:"}
{"Headers": "Orientation of the Sub-component", "Content": "To select the orientation of the sub-component:\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\nThe default value is the direction perpendicular to the face selected with a rotation of zero.\nIn the graphical view, an arrow shows the proposed direction. A line describing the angle in the trigonometric circle shows the proposed rotation.\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit.\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit.\nNote:\nUse the default orientation for a gate.\n\n\n\nDirection\nRotation\nSlope\nNote:"}
{"Headers": "Connect the Sub-component", "Content": "Click Apply to create the sub-component. The Sub-component Modification window replaces the Create Sub-component window. Enter a valid name in the Name field to activate it.\nTo cancel the creation of the sub-component, click Dismiss. If the user navigates to another element, the Sub-component Modification window closes automatically.\n\n\n\nApply\nSub-component Modification\nCreate\nSub-component\nName\nDismiss\nSub-component Modification"}
{"Headers": "Sub-Components", "Content": "In the Building Applications window sub-components are found below the owning element. In this example, the Door sub-component is owned by a straight wall.\n\nSub-component elements use SBFI and FIXING elements to represent the physical geometry. Sub-Fitting elements are used with straight walls and floors, while Fixing elements are used in curved walls, general handrails.\n\n\n"}
{"Headers": "Create Sub-component under a Straight Wall, a Curved Wall, a Beam or a Column", "Content": "From the Select Structural Element pane of the Building Applications window, make sure that the straight wall, the curved wall, the component of the beam or the component of the column is the CE.\n\nOn the Building tab, in the Create group, select the required sub-component in the Create Element drop-down list.\nClick Create Element to display the Create Sub-component window.\n\nBy default in the Naming pane of the Create Sub-component window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nSelect Structural Element\nBuilding Applications\nCE\nBuilding\nCreate\nsub-component\nCreate Element\nCreate Element\nCreate Sub-component\nNaming\nCreate Sub-component\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply"}
{"Headers": "Material", "Content": "Select the material desired using the Material drop-down list. The default material is selected according to the type of sub-component but it can be modified depending on the definition of the component in the catalogue.\n\n\n\nMaterial"}
{"Headers": "Sub-component Specification", "Content": "Choose the sub-component catalogue using the drop-down list in the Catalogue frame. The catalogue is activated by default on the first catalogue available that contains the type of component selected in the main window.\nRead the question displayed between the two lists in the Catalogue frame. Select an answer in the list of answers displayed below until the Selection complete message appears. Click on the question in the list above to reselect a question.\nAs soon as an element in the catalogue is selected, Properties is cleared if there are properties associated with this element.\n\n\n\nCatalogue\nCatalogue\nSelection\nProperties"}
{"Headers": "Position", "Content": "In the Position frame select the Face and Segment. Choose a p-line in the Face drop\u2011down list. In the graphical view the axes shows the origin of the face.\n\nFor a curved wall and a curved beam, choose the segment and the path using the Segment drop-down list. The type of each segment (straight or curved) is displayed in this list. For a straight wall, straight beam or column this list is greyed out.\n\n\n\n\n\nSegment"}
{"Headers": "Position of the Sub-component", "Content": "There are a number of methods available to enter the position of the sub-component:\n\nThe position proposed is shown in the graphical view by a sphere. By default the offset is zero.\n\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/ Height/Offset Locked to unlocked it.\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/ Height/Offset Locked to unlocked it.\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/ Height/Offset Locked to unlocked it.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nNote: To position a sub-component at the end of a wall, a beam or a column, select the closest face, unlock the Offset (Z) field and select the position in the graphical view using Pick Position.\n\n\n\nPositioning Control\nAngle (X)\nPositioning Control\nNote\n:\nOffset (Z)"}
{"Headers": "Orientation of the Sub-component", "Content": "There are three ways to select the orientation of the sub-component.\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\n50mm/m\nmillimeters per meter\n5%\npercent\n1F20\nfraction for example: 1 in 20\n50mm/m\nmillimeters per meter\n5%\npercent\n1F20\nfraction for example: 1 in 20\nThe default value is the direction perpendicular to the face selected, with a rotation of zero.\nIn the graphical view, an arrow shows the direction proposed. A line describing the angle in the trigonometric circle shows the proposed rotation.\n\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\n50mm/m\nmillimeters per meter\n5%\npercent\n1F20\nfraction for example: 1 in 20\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit. The slope can be indicated in the following forms:\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit. The slope can be indicated in the following forms:\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit. The slope can be indicated in the following forms:\nNote:\nThe mode of the graphical view reverts to the navigate mode after the selection.\nNote:\nTo orientate a sub-component at the end of a wall, beam or column, select the closest face, and then select the end in the graphical view using Pick surface or edge to define direction.\n\n\n\nDirection\nRotation\nNote:\nSlope\nNote:"}
{"Headers": "Connect the Sub-component", "Content": "The user can link the two sub-components together, the linked components have the same position and orientation. Common parameter values are also the same and can be used to align holes in different components or to align a door with an opening for example.\nThere are two ways to select the sub-component to be connected:\nThe position and orientation are modified to suit the selected sub-component. If the selected sub-component is already linked there are several options. The user may choose to replace the link (Yes) or just copy the position, orientation and parameters of the selected sub\u2011component (No) or do nothing (Cancel).\nEnter the name of the sub-component in the Connect field.\nPick the sub-component in the graphical view using Pick connection.\nEnter the name of the sub-component in the Connect field.\nEnter the name of the sub-component in the Connect field.\nPick the sub-component in the graphical view using Pick connection.\nPick the sub-component in the graphical view using Pick connection.\n\n\n\nConnect\nYes\nNo\nCancel"}
{"Headers": "Confirm the sub-component", "Content": "Click Apply to create the sub-component. If the catalogue item is not valid for this component an error message such as the following is displayed and the sub-component is not created.\n\nThe user must select an alternative element from the catalogue.\nThe Modify Sub-component window replaces the Create Sub-component window. Enter a valid name in the Name field to activate it.\nTo cancel the creation of the sub-component, click Dismiss. If the user navigates to another element, the Modify Sub-component window closes automatically.\nNote:\nIt is also possible to create a sub-component with AVEVA E3D Design using the Walls & Floors application:\nNote:\nIt is also possible to create a sub-component with AVEVA E3D Design using the Sections application. On the Sections tab, in the Create group, select click Fitting.\nCreate the sub-components under the slab component except for drainage channels that must be created under the screed component.\n\n\n\nApply\nModify Sub-component\nCreate Sub-component\nName\nDismiss\nModify Sub-component\nNote:\nAVEVA E3D Design\nWalls & Floors\nWalls & Floors\nCreate\nWall Sub-Fitting\nFittings\nWalls & Floors\nCreate\nCompound\nWall Fitting\nFittings\nNote:\nAVEVA E3D Design\nSections\nSections\nCreate\nclick Fitting"}
{"Headers": "Create Sub-Component under a General Wall, Slab, Base, Landing or Grating", "Content": "From the Select Structural Element pane of the Building Applications window, make sure that the general wall, slab component, base component or the grating component is the CE.\n\nOn the Building tab, in the Create group, select the required sub-component in the Create Element drop-down list.\nClick Create Element to display the Create Sub-component window.\n\nBy default in the Naming pane of the Create Sub-component window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nSelect Structural Element\nBuilding Applications\nCE\nBuilding\nCreate\nsub-component\nCreate Element\nCreate Element\nCreate Sub-component\nNaming\nCreate Sub-component\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply"}
{"Headers": "Material", "Content": "Select the material desired using the Material drop-down list. The default material is selected according to the type of sub-component but it can be modified depending on the definition of the component in the catalogue.\n\n\n\nMaterial"}
{"Headers": "Sub-component Specification", "Content": "Choose the sub-component catalogue using the drop-down list in the Catalogue frame. The catalogue is activated by default on the first catalogue available that contains the type of component selected in the main window.\nRead the question displayed between the two lists in the Catalogue frame. Select an answer in the list of answers displayed below until the Selection complete message appears. Click on the question in the list above to reselect a question.\nAs soon as an element in the catalogue is selected, Properties is cleared if there are properties associated with this element.\n\n\n\nCatalogue\nCatalogue\nSelection\nProperties"}
{"Headers": "Sub-component Properties", "Content": "Click Properties to display the properties of the sub-component.\n\n\n\n\nProperties"}
{"Headers": "Select the Face and Segment", "Content": "Choose a face in the faces drop-down list. In the graphical view, the axes show the origin of the face.\n\nFor the Around contour option, choose the segment of the path using the Segment drop\u2011down list. The type of each segment (Straight or curved) is displayed in this list.\n\n\n\n\nSegment"}
{"Headers": "Position the Sub-component", "Content": "There are a number of methods available to enter the position of the sub-component:\n\nThe position proposed is shown in the graphical view by a sphere. By default the offset is zero.\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/ Height/Offset Locked to unlocked it.\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/ Height/Offset Locked to unlocked it.\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/ Height/Offset Locked to unlocked it.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nNote:\nTo position a sub-component on a face of a hole, select the closest face, unlock the Offset (Z) field and select the position in the graphical view using Pick Position.\n\n\n\nPositioning Control\nAngle (X)\nPositioning Control\nNote:\nOffset (Z)"}
{"Headers": "Orientation of the Sub-component", "Content": "There are three ways to select the orientation of the sub-component.\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\nThe default value is the direction perpendicular to the face selected with a rotation of zero.\nIn the graphical view, an arrow shows the proposed direction. A line describing the angle in the trigonometric circle shows the proposed rotation.\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit.\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit.\nNote:\nTo orient a sub-component on a face of a hole, select the closest face, and then select the end in the graphical view using Pick position.\n\n\n\nDirection\nRotation\nSlope\nNote:"}
{"Headers": "Connect the Sub-component", "Content": "The user can link the two sub-components together, the linked components have the same position and orientation. Common parameter values are also the same, and can be used to align holes in different components or to align a door with an opening for example.\nThere are two ways to select the sub-component to be connected:\nThe position and orientation are modified to suit the selected sub-component. If the selected sub-component is already linked there are several options. The user may choose to replace the link (Yes) or just copy the position, orientation and parameters of the selected sub\u2011component (No) or do nothing (Cancel).\nEnter the name of the sub-component in the Connect field.\nPick the sub-component in the graphical view using Pick connection.\nEnter the name of the sub-component in the Connect field.\nEnter the name of the sub-component in the Connect field.\nPick the sub-component in the graphical view using Pick connection.\nPick the sub-component in the graphical view using Pick connection.\n\n\n\nConnect\nYes\nNo\nCancel"}
{"Headers": "Modify Sub-Component", "Content": "All the tasks associated with the modification of the sub-component element can be performed from the Modify Sub-component window.\n\nThere are a number of ways to modify a sub-component:\n\n\n\nModify Sub-component"}
{"Headers": "Material", "Content": "The material can be modified in the same way as it is selected for creation.\n\n\n"}
{"Headers": "Select the Sub-component Specification", "Content": "The user can change the specification of the sub-component by clicking question in the list above.\n\n\n"}
{"Headers": "Modify the Geometry of the Sub-component", "Content": "With free-form shapes, the user can click Contour to open the 2D Contour Editor and change the contour of the sub-component.\n\nThere are two ways to modify the depth:\nEnter a value in the Depth field.\nMeasure the value. Click Measure which invokes the Positioning Control window. The user is prompted to Measure Depth:Pick Start (Snap) Snap:, Measure Depth:Pick End (Snap) Snap:.\nEnter a value in the Depth field.\nEnter a value in the Depth field.\nMeasure the value. Click Measure which invokes the Positioning Control window. The user is prompted to Measure Depth:Pick Start (Snap) Snap:, Measure Depth:Pick End (Snap) Snap:.\nMeasure the value. Click Measure which invokes the Positioning Control window. The user is prompted to Measure Depth:Pick Start (Snap) Snap:, Measure Depth:Pick End (Snap) Snap:.\n\n\n"}
{"Headers": "Enter the Sub-component Properties", "Content": "Click Properties to display the properties of the sub-component. Ignore the Angle and Offset properties as they are calculated automatically by Concrete Design.\n\n\n\nProperties\nAngle\nOffset"}
{"Headers": "Select the Face and Segment", "Content": "The face and segment can be modified in the same way they are selected for creation.\n\n\n"}
{"Headers": "Enter the Position of the Sub-component", "Content": "The position can be modified the same way it is selected for creation. The user can select a p-point to position the sub-component using the Reference drop-down list.\nNote:\nTo select p-points on sub-components without positive geometry using Pick position.\n\n\n\nReference\nNote:"}
{"Headers": "Enter the Orientation of the Sub-component", "Content": "The orientation can be modified the same way it is selected for creation.\n\n\n"}
{"Headers": "Connect the Sub-component", "Content": "The sub-component may be connected to another sub-component, if required, in the same as for creation.\nFor sub-components of general walls, floors, bases, landings and gratings, the user can penetrate other elements with the same sub-component. Click Penetrate other elements to display the Penetrate other elements window.\n\nThere are two stages to use this window:\n\n\n\nPenetrate other elements\nPenetrate other elements\nOK"}
{"Headers": "Confirm the Sub-component", "Content": "Click Apply to confirm the modification of the sub-component. If the catalogue item is not valid for this component an error message such as the following is displayed and the sub\u2011component is not modified.\n\nAn alternative element must be selected from the catalogue.\nClick Dismiss to close the Modify Sub-component window.\nTo create a new sub-component with the same parameters, click Repeat. The Create Sub\u2011component window is then displayed.\nIf the AVEVA E3D Design is used to change the sub-component, click Refresh to display the current attributes.\nNote:\nSelect Repeat to copy sub-components as Copy on the main window does not work for sub-components.\n\n\n\nApply\nDismiss\nModify Sub-component\nRepeat\nCreate Sub\u2011component\nNote:\nRepeat\nCopy\nAVEVA E3D Design\nRefresh"}
{"Headers": "Position with Sub-component Polar Coordinates", "Content": "To position a sub-component using polar coordinates, a circular grid must be created. Refer to Reference Grids for further information.\n\n\n\nReference Grids\nReference Grids"}
{"Headers": "Propose Sub-Component Without Write Access to the Owning Component", "Content": "From the Select Structural Element pane of the Building Applications window, make sure that the sub-component is the CE.\n\nOn the Building tab, in the Create group, select the required sub-component in the Create Element drop-down list.\nClick Create Element to display the Propose Sub-component window.\n\nBy default in the Naming pane of the Proposed Sub-component window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Material drop-down list by default is set according to the type of sub\u2011component, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight. The density of the material selected is shown in a tooltip.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nSelect Structural Element\nBuilding Applications\nCE\nBuilding\nCreate\nsub-component\nCreate Element\nCreate Element\nPropose Sub-component\nNaming\nProposed Sub-component\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nMaterial\nMaterial"}
{"Headers": "Sub-component Specification", "Content": "Choose the sub-component catalogue using the drop-down list in the Catalogue frame. The catalogue is activated by default on the first catalogue available that contains the type of component selected in the main window.\nRead the question displayed between the two lists in the Catalogue frame. Select an answer in the list of answers displayed below until the Selection complete message appears. Click on the question in the list above to reselect a question.\nAs soon as an element in the catalogue is selected, Properties is cleared if there are properties associated with this element.\n\n\n\nCatalogue\nCatalogue\nSelection\nProperties"}
{"Headers": "Sub-component Properties", "Content": "Click Properties to display the properties of the sub-component. Do not fill in the Angle or Offset properties as these are calculated automatically by the application.\n\n\n\nProperties\nAngle\nOffset"}
{"Headers": "Select the Face and Segment", "Content": "Choose a p-line in the faces drop-down list. In the graphical view the axes show the origin of the face.\nFor a curved wall and a curved beam, choose the segment and the path using the Segment drop-down list. The type of each segment (straight or curved) is displayed in this list. For a straight wall, straight beam or column this list is greyed out.\n\n\n\n\nSegment"}
{"Headers": "Position the Sub-component", "Content": "There are a number of methods available to enter the position of the sub-component:\nThe position proposed is shown in the graphical view by a sphere. By default the offset is zero.\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/ Height/Offset Locked to unlock it.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/ Height/Offset Locked to unlock it.\nEnter the values in the Distance, Height and Offset fields. If the field is locked, click Distance/ Height/Offset Locked to unlock it.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nClick Measure to measure the values of the distances. The Positioning Control window is displayed. The user is prompted to Start:Pick Start (Snap) Snap:, Start:Pick End (Snap) Snap:.The end position is adjusted to suit the new length.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nEnter the values of the angles in the Angle (X) fields. The method is only available for curved segments. The distances in the X direction are adjusted.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nClick Pick position to select the position in the graphical view. To avoid changing a desired value in a field, click Distance/ Height/Offset Unlocked to lock it. Click Grid to display a grid positioned in the proposed position and in the proposed direction.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nType the elevation of the sub-component in the Level field. The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nClick Pick Level to select the level in the graphical view. The Positioning Control window is displayed. Follow the prompt Pick Level (Snap) Snap:.The height value is adjusted to suit.\nNote:\nTo position a sub-component on a face of a hole, select the closest face, unlock the Offset (Z) field and select the position in the graphical view using Pick Position.\n\n\n\nPositioning Control\nAngle (X)\nPositioning Control\nNote:\nOffset (Z)"}
{"Headers": "Orientation of the Sub-component", "Content": "There are three ways to select the orientation of the sub-component.\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\n50mm/m\nmillimeters per meter\n5%\npercent\n1F20\nfraction for example: 1 in 20\n50mm/m\nmillimeters per meter\n5%\npercent\n1F20\nfraction for example: 1 in 20\nThe default value is the direction perpendicular to the face selected with a rotation of zero.\nIn the graphical view, an arrow shows the proposed direction. A line describing the angle in the trigonometric circle shows the proposed rotation.\n\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\n50mm/m\nmillimeters per meter\n5%\npercent\n1F20\nfraction for example: 1 in 20\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level. The angle can be indicated in the following forms:\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit. The slope can be indicated in the following forms:\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The direction is perpendicular to a face or along a line.\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit. The slope can be indicated in the following forms:\nEnter the slope of the sub-component in the Slope field. The direction is adjusted to suit. The slope can be indicated in the following forms:\nNote:\nTo orient a sub-component on a face of a hole, select the closest face, and then select the end in the graphical view using Pick position.\n\n\n\nDirection\nRotation\nSlope\nNote:"}
{"Headers": "Connect the Sub-component", "Content": "Do not use the connection functionality until the proposal is approved.\n\n\n"}
{"Headers": "Confirm the Sub-component", "Content": "Click Apply to create the proposed sub-component. The proposed sub\u2011component is created under a suitable structure. The proposed sub-component has the name of the component followed by \u2018(proposed)\u2019. If no suitable structure is available the following message is displayed:\n\nClick Yes to create a structure for the current building.\nThe proposed sub-component is linked to the owning component using an association.\n\nIf no suitable association group is available the following message is displayed:\n\nThe Sub-component Modification window replaces the Proposed Sub-component window. Enter a valid name in the Name field to activate it.\nTo cancel the creation of the sub-component, click Dismiss.\n\n\n\nApply\nYes\nSub-component Modification\nProposed Sub-component\nName\nDismiss"}
{"Headers": "Modify Proposed Sub-Component", "Content": "All the tasks associated with the modification of the proposed sub-component element can be performed from the Modify Sub-component window.\n\nThe proposed sub-component can be modified in the same way as normal sub\u2011components. If the user has write access to the owning component, the following message appears when Apply is selected.\n\nClick Yes to convert this sub-component to a normal sub-component. The proposed sub\u2011component is deleted and the sub-component created under the component. The association is modified to include this sub-component.\n\n\n\nModify Sub-component\nApply\nYes"}
{"Headers": "Create Kicker", "Content": "Referring to the hierarchy, a kicker element must reside below an existing floor screed component (as it is a sub-component of a floor screed).\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Floor Screed Component element is the CE.\n\nOn the Building tab, in the Create group, select Kicker in the Create Element drop-down list.\nClick Create Element to display the Create Kicker window.\n\nBy default in the Naming pane of the Create Kicker window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Material drop-down list by default is C20/25 Screed, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight. The density of the material selected is shown in a tooltip.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\n\n\n\nNaming\nSelect Structural Element\nBuilding Applications\nFloor Screed Component\nCE\nBuilding\nCreate\nKicker\nCreate Element\nCreate Element\n\nNaming\nCreate Kicker\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nMaterial\nC20/25 Screed\nMaterial"}
{"Headers": "Define the Section", "Content": "To copy the section of another kicker, click Pick profile to copy and select the other kicker.\nTo reverse the direction of the section, click the Mirror section checkbox.\nTo define the section, click Catalogue. Use is the same as for a straight beam.\nTo copy the section of another kicker, click Pick profile to copy and select the other kicker.\nTo copy the section of another kicker, click Pick profile to copy and select the other kicker.\nTo reverse the direction of the section, click the Mirror section checkbox.\nTo reverse the direction of the section, click the Mirror section checkbox.\nTo define the section, click Catalogue. Use is the same as for a straight beam.\nTo define the section, click Catalogue. Use is the same as for a straight beam.\n\n\n\nMirror section\nCatalogue"}
{"Headers": "Position the Kicker", "Content": "Enter the values in the fields for east, north and up in the Position frame. The reference can also be changed by entering the name of an existing element in the Wrt field.\nClick Pick in the Position frame to select the position in the graphical view. To avoid changing a desired value in a field, click Coordinate unlocked to lock it.\nThe position is shown in the graphical view by a sphere.\nEnter the values in the fields for east, north and up in the Position frame. The reference can also be changed by entering the name of an existing element in the Wrt field.\nEnter the values in the fields for east, north and up in the Position frame. The reference can also be changed by entering the name of an existing element in the Wrt field.\nClick Pick in the Position frame to select the position in the graphical view. To avoid changing a desired value in a field, click Coordinate unlocked to lock it.\nThe position is shown in the graphical view by a sphere.\nClick Pick in the Position frame to select the position in the graphical view. To avoid changing a desired value in a field, click Coordinate unlocked to lock it.\n\n\n\nPosition\nWrt\nPosition"}
{"Headers": "Orientation of the Kicker", "Content": "\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The default direction is up (U) with respect to the level, with a rotation of zero. In the graphical view the orientation proposed is shown by an arrow positioned at the origin and in the direction of the value of the rotation.\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level.\nEnter the values in the Direction and Rotation fields. The direction is always shown with respect to the level.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The default direction is up (U) with respect to the level, with a rotation of zero. In the graphical view the orientation proposed is shown by an arrow positioned at the origin and in the direction of the value of the rotation.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. Select an object in the graphical view and drag the cursor to the desired face on edge. The default direction is up (U) with respect to the level, with a rotation of zero. In the graphical view the orientation proposed is shown by an arrow positioned at the origin and in the direction of the value of the rotation.\n\n\n\nDirection\nRotation"}
{"Headers": "Select the Mitres", "Content": "Three methods can be used to select each miter:\nBy default the miters are perpendicular to the direction of the kicker.\nEnter a direction in the field. The direction is always shown with respect to the level. If the direction is locked, click End direction always perpendicular to unlock it.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. The direction is perpendicular to the face selected.\nClick End direction free to choose the perpendicular to the direction of the kicker. The miter is calculated automatically when the direction of the kicker is modified.\nEnter a direction in the field. The direction is always shown with respect to the level. If the direction is locked, click End direction always perpendicular to unlock it.\nEnter a direction in the field. The direction is always shown with respect to the level. If the direction is locked, click End direction always perpendicular to unlock it.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. The direction is perpendicular to the face selected.\nClick Pick surface or edge to define direction to select the direction in the graphical view. Follow the prompt Pick Face or Edge. The direction is perpendicular to the face selected.\nClick End direction free to choose the perpendicular to the direction of the kicker. The miter is calculated automatically when the direction of the kicker is modified.\nClick End direction free to choose the perpendicular to the direction of the kicker. The miter is calculated automatically when the direction of the kicker is modified.\n\n\n"}
{"Headers": "Activate the Connectivity", "Content": "If the end of the kicker is in the same position as another end and if the connectivity is activated, the miters of both ends are adjusted.\n\n\n\n"}
{"Headers": "Choose the Shape of the Kicker", "Content": "There are two ways to define the shape of the kicker:\n\n\n"}
{"Headers": "Complex", "Content": "Select Complex from the Shape drop-down list. The 2D Spine Editor window is displayed.\n\nThe kicker is created and the Modification window replaces the Creation window.\n\n\n\nShape\nModification\nCreation"}
{"Headers": "Contour", "Content": "Select Contour from the Shape drop-down list. The Contour list is displayed. The list of contours includes the contour of the floor screed and all the holes in the floor slab. Select a contour. In the graphical view aid lines show the contour.\nClick Apply to create the kicker. The Modify Kicker window replaces the Create Kicker window. Enter a valid name in the Name field to activate it.\nTo cancel the creation of the kicker, click Dismiss. If the user navigates to another element, the window closes automatically.\n\n\n\nContour\nShape\nApply\nModify Kicker\nCreate Kicker\nName\nDismiss"}
{"Headers": "Modify Kicker", "Content": "All the tasks associated with the modification of the kicker element can be performed from the Modify Kicker window.\n\nThe material, section, position, orientation and miter can be modified the same way they were selected for creation.\nThe section can be modified the same way as for the straight beam. Refer to Modify Straight Beam for further information.\nIf the connectivity is activated, the position and miters of the ends are adjusted.\nTo confirm the modification, click Apply.\nTo create a new kicker with the same parameters, click Repeat. The Create Kicker window is then displayed.\nTo close the window, click Dismiss.\nIf AVEVA E3D Design is used to change the kicker, click Refresh to display the current attributes.\n\n\n\nModify Straight Beam\nModify Kicker\nModify Straight Beam\nApply\nRepeat\nCreate Kicker\nDismiss\nAVEVA E3D Design\nRefresh"}
{"Headers": "Management of Assemblies", "Content": "Assemblies can be created and modified, the user can also define which members of the assembly are displayed in the 3D graphical view.\n\n\n"}
{"Headers": "Create Assemblies", "Content": "Referring to the hierarchy, an assembly element must reside below an existing level element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Level element is the CE.\n\nOn the Building tab, in the Create group, select Assembly in the Create Element drop-down list.\nClick Create Element to display the Create Assembly window.\n\nThere are three steps to creating an assembly:\nName the Assembly\nInput a unique name for the assembly in the Name field.\nSelect the Members\nSelect the existing elements to add to this assembly from the list of elements that do not already belong to another assembly. At least one element must be selected.\nConfirm Assembly Creation\nClick Apply to create the assembly. The function attribute of the select elements is modified.\nTo cancel the creation of the assembly, click Dismiss. If the user navigateS to another element, the Create Assembly window closes automatically.\n\n\n\nSelect Structural Element\nBuilding Applications\nLevel\nCE\nBuilding\nCreate\nAssembly\nCreate Element\nCreate Element\nCreate Assembly\nName the Assembly\nName\nSelect the Members\nConfirm Assembly Creation\nApply\nDismiss\nCreate Assembly"}
{"Headers": "Assemblies Usage", "Content": "If the user navigates to a level, they can select an assembly and then the members of that assembly.\n\nThe user may also add all the members of the assembly to the graphical view using the pop\u2011up menu of the member list.\n\n\n"}
{"Headers": "Modify Assemblies", "Content": "To modify an assembly, the user must choose another assembly (or None) from the list on Modification window of each element.\n\n\n\n\nNone\nModification"}
{"Headers": "Modelling Slopes", "Content": "It may be required to create a sloping design element, the Building application has the functionality to create such an element, the user must first create the element required and add a negative to it.\n\n\n"}
{"Headers": "Create Sloping Screed", "Content": "To create a sloping screed, create a screed using the Concrete Design application and then add the slope using the Walls and Floors application.\nOn the Walls and Floors tab, in the Modify group, click Screed Slope to display the Screed Slope window.\n\nThe functionality of the Screed Slope window is explained. Refer to Modify Screed Slope for further information.\n\n\n\nModify Screed Slope\nConcrete Design\nWalls and Floors\nWalls and Floors\nModify\nScreed Slope\nScreed Slope\nScreed Slope\nModify Screed Slope"}
{"Headers": "Create Sloping Floor", "Content": "Referring to the hierarchy, a sloping floor element must reside below an existing floor slab element.\nFrom the Select Structural Element pane of the Building Applications window, make sure that the Floor Slab element is the CE.\n\nOn the Building tab, in the Create group, select Sloping Floor in the Create Element drop-down list.\nClick Create Element to display the Create Floor Slab window.\n\nBy default in the Naming pane of the Create Floor Slab window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nUse gaps in naming sequence\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nMaterial\nThe Material drop-down list by default is set to Pyrocrete, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nThe material is used to calculate the weight. The density of the material selected is shown in a tooltip.\nFloor Thickness\n\nThe Floor Thickness can be populated in several ways:\nIf the user does not want the thickness to adapt to level changes, click Thickness changes to suit levels to lock the thickness.\nThe default finished level is zero with respect to the level. The default screed thickness is zero. The default slab thickness is 300.\nA cone shows the top level of the slab in the graphical view\nSection Specification\nTo copy the section of another sloping floor, click Pick profile to copy and select the other floor. To define the section, click Catalogue.\n\nThere are six steps to using this window:\n\nThe properties of the floor can be modified using Properties.\nThe user can also change the justification of the floor using the Mirror Profile.\nStart / End Position\n\nThere are a number of methods available to select the start and end positions of the floor:\nThe default position is at the origin of the level with an eastward direction with respect to the level and a length of 5000 mm.\nIn the graphical view, the positions proposed are shown by an arrow between the start and end.\nSection Rotation\nEnter an angle in the Section Rotation field.\nThe angle can have the following forms:\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\nBy default the rotation of the section is zero.\nmiter\nBy default, the miters are perpendicular to the direction of the floor.\nConnectivity\nApply\nClick Apply to create the sloping floor. The Modify Floor Slab window replaces the Create Floor Slab window. Enter a valid name in the Name field to activate it.\nTo cancel the creation of the sloping floor, click Dismiss. If the user navigate to another element, the window closes automatically.\n123.25\ndecimal degrees\n123\u00b015'05'' or 123d15m05s\ndegrees, minutes and seconds\n130G12\ndecimal grades\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\nEnter the absolute top level (wrt World) in the Top Level field. If the thickness is locked or the value is less than the bottom level, the bottom level adapts. If the thickness is not locked, the thickness adapts.\nTo select the top level click Pick Top Level. The Positioning Control window is displayed. Follow the prompt Pick Top Level (Snap) Snap: and select the top level in the graphical view. If the thickness is locked or the value is less than the bottom level, the bottom level adapts. If the thickness is not locked, the thickness adapts. If a suitable element is selected the background colour of Top Level is changed to green and the tooltip indicates the connected element.\nEnter the thickness in the Thickness field. If the thickness is locked, click Other level changes to suit thickness to unlock it.\nClick Measure Height. The Positioning Control window is displayed. The user is prompted to Height:Pick Start (Snap) Snap:, Height:Pick End (Snap) Snap: and select two graphical picks.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the thickness is locked or if the value is greater than the top level, the top level adapts. If the thickness is not locked, the thickness adapts.\nTo select the bottom level click Pick Bottom Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the bottom level in the graphical view. If the thickness is locked or the value is less than the top level, the top level adapts. If the thickness is not locked, the thickness adapts. If a suitable element is selected the background colour of Bottom Level is changed to green and the tooltip indicates the connected element.\nEnter the absolute top level (wrt World) in the Top Level field. If the thickness is locked or the value is less than the bottom level, the bottom level adapts. If the thickness is not locked, the thickness adapts.\nEnter the absolute top level (wrt World) in the Top Level field. If the thickness is locked or the value is less than the bottom level, the bottom level adapts. If the thickness is not locked, the thickness adapts.\nTo select the top level click Pick Top Level. The Positioning Control window is displayed. Follow the prompt Pick Top Level (Snap) Snap: and select the top level in the graphical view. If the thickness is locked or the value is less than the bottom level, the bottom level adapts. If the thickness is not locked, the thickness adapts. If a suitable element is selected the background colour of Top Level is changed to green and the tooltip indicates the connected element.\nTo select the top level click Pick Top Level. The Positioning Control window is displayed. Follow the prompt Pick Top Level (Snap) Snap: and select the top level in the graphical view. If the thickness is locked or the value is less than the bottom level, the bottom level adapts. If the thickness is not locked, the thickness adapts. If a suitable element is selected the background colour of Top Level is changed to green and the tooltip indicates the connected element.\nEnter the thickness in the Thickness field. If the thickness is locked, click Other level changes to suit thickness to unlock it.\nEnter the thickness in the Thickness field. If the thickness is locked, click Other level changes to suit thickness to unlock it.\nClick Measure Height. The Positioning Control window is displayed. The user is prompted to Height:Pick Start (Snap) Snap:, Height:Pick End (Snap) Snap: and select two graphical picks.\nClick Measure Height. The Positioning Control window is displayed. The user is prompted to Height:Pick Start (Snap) Snap:, Height:Pick End (Snap) Snap: and select two graphical picks.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the thickness is locked or if the value is greater than the top level, the top level adapts. If the thickness is not locked, the thickness adapts.\nEnter the absolute bottom level (wrt World) in the Bottom Level field. If the thickness is locked or if the value is greater than the top level, the top level adapts. If the thickness is not locked, the thickness adapts.\nTo select the bottom level click Pick Bottom Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the bottom level in the graphical view. If the thickness is locked or the value is less than the top level, the top level adapts. If the thickness is not locked, the thickness adapts. If a suitable element is selected the background colour of Bottom Level is changed to green and the tooltip indicates the connected element.\nTo select the bottom level click Pick Bottom Level. The Positioning Control window is displayed. Follow the prompt Pick Bottom Level (Snap) Snap: and select the bottom level in the graphical view. If the thickness is locked or the value is less than the top level, the top level adapts. If the thickness is not locked, the thickness adapts. If a suitable element is selected the background colour of Bottom Level is changed to green and the tooltip indicates the connected element.\n1. Select the specification using the Specification drop-down list.\nSelect the section using the Generic Type drop-down list.\nSelect the size in the list of components. If the shape can be configured, there is only one component.\nChoose the alignment of the wall using the Justification, Member Line, and Joint Line drop-down lists.\n1. Select the specification using the Specification drop-down list.\nSelect the section using the Generic Type drop-down list.\nSelect the size in the list of components. If the shape can be configured, there is only one component.\nChoose the alignment of the wall using the Justification, Member Line, and Joint Line drop-down lists.\n1. Select the specification using the Specification drop-down list.\nEnter the values in the fields for east, north and the up in the Start Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it. If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. The length is always calculated between both positions.\nClick Pick in the Start Position frame to invoke the Positioning Control window. Follow the prompt Pick Start (Snap) Snap: and select the start position in the graphical view. To avoid modifying a desired value in a field, click Coordinates unlocked to lock it. If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. Its length is always calculated between both positions.\nEnter the values in the field for east, north and the up in the End Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it. If the direction is locked, the start position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. The length is always calculated between both positions.\nClick Pick in the End Position frame to invoke the Positioning Control window. Follow the prompt Pick End (Snap) Snap: and select the end position in the graphical view. To avoid modifying a desired value in a field, click Coordinates unlocked to lock it. If the direction is locked, the start position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. Its length is always calculated between both positions.\nEnter the value of the length in the Length field to invoke the Positioning Control window. The end position is adjusted to suit the new length. The user is prompted to Measure Length:Pick Start (Snap) Snap:, Measure Length:Pick End (Snap) Snap: and select two positions in the graphical view. The end position is adjusted to suit the new length.\nEnter the values in the Direction fields. The direction is in the following form:\n<Cardinal point> [<Angle> <Cardinal point>[[<Angle> <Cardinal point>]] wrt <Name> where\n<Cardinal point> est E (east), W(west), N(north), S(south), U(up) or D(down)\n<Angle> is a real value between 0 and 90.\n<Name> is the name of an existing element (/* or /-HR for example)\n[] indicates an optional part. The same axis may not be used several times.\nThe direction is always shown with respect to the level. If the direction is locked, it. click Coordinates locked to unlock it. The end position is adjusted to suit the new direction and the existing length. To avoid changing the desired direction, click Coordinates unlocked to lock it.\nClick Pick surface or edge to define direction and follow the prompt Pick Face or Edge to select the direction in the graphical view. Select an object in the graphical view and slide the cursor to the desired face. The direction is perpendicular to the selected face. The end position is adjusted to suit the new direction and the existing length. To reverse the direction, click Reverse Direction. To avoid changing the desired direction, click Coordinates unlocked to lock it.\nSelect the start position, then the end position using the Graphical Pick Start/End option in the drop-down list above the Position frames. The user is prompted to Pick Start (Snap) WP Snap:, Pick End (Snap) WP Snap: to select two positions in the graphical view. If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. The length is always calculated between both positions.\nSelect the start position using the Move Graphically drop-down list above the Position frames. Follow the prompt Pick Position:Pick Start (Snap) WP Snap:, and select a position in the graphical view. The end position is adjusted to suit the direction and current length.\nClick Flip start and end position to flip the start and end position. The start position takes the end position values. The end position takes the start position values. The length keeps the same value but the direction is reversed.\nClick Use end position for start to continue the floor from the previous values. The start position takes the end position values. The distance and direction keep the same values. The end position is calculated from the start position, length and direction values.\nEnter the values in the fields for east, north and the up in the Start Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it. If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. The length is always calculated between both positions.\nEnter the values in the fields for east, north and the up in the Start Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it. If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. The length is always calculated between both positions.\nClick Pick in the Start Position frame to invoke the Positioning Control window. Follow the prompt Pick Start (Snap) Snap: and select the start position in the graphical view. To avoid modifying a desired value in a field, click Coordinates unlocked to lock it. If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. Its length is always calculated between both positions.\nClick Pick in the Start Position frame to invoke the Positioning Control window. Follow the prompt Pick Start (Snap) Snap: and select the start position in the graphical view. To avoid modifying a desired value in a field, click Coordinates unlocked to lock it. If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. Its length is always calculated between both positions.\nEnter the values in the field for east, north and the up in the End Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it. If the direction is locked, the start position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. The length is always calculated between both positions.\nEnter the values in the field for east, north and the up in the End Position frame. The user can also change the reference by entering the name of an existing element in the Wrt field. If the field is greyed out, click Coordinates locked to unlock it. If the direction is locked, the start position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. The length is always calculated between both positions.\nClick Pick in the End Position frame to invoke the Positioning Control window. Follow the prompt Pick End (Snap) Snap: and select the end position in the graphical view. To avoid modifying a desired value in a field, click Coordinates unlocked to lock it. If the direction is locked, the start position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. Its length is always calculated between both positions.\nClick Pick in the End Position frame to invoke the Positioning Control window. Follow the prompt Pick End (Snap) Snap: and select the end position in the graphical view. To avoid modifying a desired value in a field, click Coordinates unlocked to lock it. If the direction is locked, the start position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. Its length is always calculated between both positions.\nEnter the value of the length in the Length field to invoke the Positioning Control window. The end position is adjusted to suit the new length. The user is prompted to Measure Length:Pick Start (Snap) Snap:, Measure Length:Pick End (Snap) Snap: and select two positions in the graphical view. The end position is adjusted to suit the new length.\nEnter the value of the length in the Length field to invoke the Positioning Control window. The end position is adjusted to suit the new length. The user is prompted to Measure Length:Pick Start (Snap) Snap:, Measure Length:Pick End (Snap) Snap: and select two positions in the graphical view. The end position is adjusted to suit the new length.\nEnter the values in the Direction fields. The direction is in the following form:\n<Cardinal point> [<Angle> <Cardinal point>[[<Angle> <Cardinal point>]] wrt <Name> where\n<Cardinal point> est E (east), W(west), N(north), S(south), U(up) or D(down)\n<Angle> is a real value between 0 and 90.\n<Name> is the name of an existing element (/* or /-HR for example)\n[] indicates an optional part. The same axis may not be used several times.\nThe direction is always shown with respect to the level. If the direction is locked, it. click Coordinates locked to unlock it. The end position is adjusted to suit the new direction and the existing length. To avoid changing the desired direction, click Coordinates unlocked to lock it.\nEnter the values in the Direction fields. The direction is in the following form:\nClick Pick surface or edge to define direction and follow the prompt Pick Face or Edge to select the direction in the graphical view. Select an object in the graphical view and slide the cursor to the desired face. The direction is perpendicular to the selected face. The end position is adjusted to suit the new direction and the existing length. To reverse the direction, click Reverse Direction. To avoid changing the desired direction, click Coordinates unlocked to lock it.\nClick Pick surface or edge to define direction and follow the prompt Pick Face or Edge to select the direction in the graphical view. Select an object in the graphical view and slide the cursor to the desired face. The direction is perpendicular to the selected face. The end position is adjusted to suit the new direction and the existing length. To reverse the direction, click Reverse Direction. To avoid changing the desired direction, click Coordinates unlocked to lock it.\nSelect the start position, then the end position using the Graphical Pick Start/End option in the drop-down list above the Position frames. The user is prompted to Pick Start (Snap) WP Snap:, Pick End (Snap) WP Snap: to select two positions in the graphical view. If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. The length is always calculated between both positions.\nSelect the start position, then the end position using the Graphical Pick Start/End option in the drop-down list above the Position frames. The user is prompted to Pick Start (Snap) WP Snap:, Pick End (Snap) WP Snap: to select two positions in the graphical view. If the direction is locked, the end position is adjusted to suit the direction. Otherwise the direction is calculated between both positions. The length is always calculated between both positions.\nSelect the start position using the Move Graphically drop-down list above the Position frames. Follow the prompt Pick Position:Pick Start (Snap) WP Snap:, and select a position in the graphical view. The end position is adjusted to suit the direction and current length.\nSelect the start position using the Move Graphically drop-down list above the Position frames. Follow the prompt Pick Position:Pick Start (Snap) WP Snap:, and select a position in the graphical view. The end position is adjusted to suit the direction and current length.\nClick Flip start and end position to flip the start and end position. The start position takes the end position values. The end position takes the start position values. The length keeps the same value but the direction is reversed.\nClick Flip start and end position to flip the start and end position. The start position takes the end position values. The end position takes the start position values. The length keeps the same value but the direction is reversed.\nClick Use end position for start to continue the floor from the previous values. The start position takes the end position values. The distance and direction keep the same values. The end position is calculated from the start position, length and direction values.\nClick Use end position for start to continue the floor from the previous values. The start position takes the end position values. The distance and direction keep the same values. The end position is calculated from the start position, length and direction values.\nEnter a direction in the field. The direction is always shown with respect to the level. If the direction is locked, click End direction always perpendicular to unlock it.\nClick Pick surface or edge to define direction and follow the prompt Pick Face or Edge to select the direction in the graphical view. The direction is perpendicular to the face selected.\nClick End direction free to choose the perpendicular to the direction of floor. The miter is calculated automatically when the direction of the floor is modified.\nEnter a direction in the field. The direction is always shown with respect to the level. If the direction is locked, click End direction always perpendicular to unlock it.\nEnter a direction in the field. The direction is always shown with respect to the level. If the direction is locked, click End direction always perpendicular to unlock it.\nClick Pick surface or edge to define direction and follow the prompt Pick Face or Edge to select the direction in the graphical view. The direction is perpendicular to the face selected.\nClick Pick surface or edge to define direction and follow the prompt Pick Face or Edge to select the direction in the graphical view. The direction is perpendicular to the face selected.\nClick End direction free to choose the perpendicular to the direction of floor. The miter is calculated automatically when the direction of the floor is modified.\nClick End direction free to choose the perpendicular to the direction of floor. The miter is calculated automatically when the direction of the floor is modified.\nNote:\nThe section is modified by default. If the section is the same, it is unnecessary to display this window when creating a second sloping floor.\nNote:\nThe positions can be modified if the connectivity is activated.\nNote:\nUse the rotation to define a cross-fall. The faces around the floor stays vertical if the catalogue element is defined correctly.\nNote:\nDo not use connectivity for a sloping floor.\n\n\n\nNaming\nSelect Structural Element\nBuilding Applications\nFloor Slab\nCE\nBuilding\nCreate\nSloping Floor\nCreate Element\nCreate Element\nCreate Floor Slab\nNaming\nCreate Floor Slab\nName\nNaming\nUse gaps in naming sequence\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nMaterial\nMaterial\nPyrocrete\nMaterial\nFloor Thickness\nwrt\nTop Level\nPositioning Control\nTop Level\nThickness\nPositioning Control\nwrt\nBottom Level\nPositioning Control\nBottom Level\nSection Specification\nCatalogue\nSpecification\nGeneric Type\nJustification\nMember Line\nJoint Line\nJustification\nDraft\nMember Line\nJoint Line\nModify Properties\nProperties\nThickness\nRotation\nApply\nDismiss\nNote:\nProperties\nMirror Profile\nStart / End Position\nStart Position\nStart Position\nEnd Position\nEnd Position\nLength\nDirection\nGraphical Pick\nStart/End\nMove Graphically\nNote:\nSection Rotation\nSection Rotation\nNote:\nConnectivity\nNote:\nApply\nApply\nModify Floor Slab\nCreate Floor Slab\nName\nDismiss"}
{"Headers": "Modify Sloping Floor", "Content": "All the tasks associated with the modification of the sloping floor element can be performed from the Modify Floor Slab window.\n\nThe material, levels, positions and miters can be modified the same way there were selected in the Creation form.\nTo copy the section of another floor, click Pick profile to copy and select the other floor. To modify the section, click Catalogue.\nThe user can also modify the properties using Properties.\nTo confirm the change, click Apply.\nTo create a new sloping floor component with the same parameters, click Repeat. The Create Floor Slab window is then displayed.\nClick Dismiss to close the Modify Floor Slab window.\nIf AVEVA E3D Design is used to change the floor, click Refresh to display the current attributes.\n\n\n\nModify Floor Slab\nCreation\nCatalogue\nProperties\nApply\nRepeat\nCreate Floor Slab\nDismiss\nModify Floor Slab\nAVEVA E3D Design\nRefresh"}
{"Headers": "Create Sloping Wall", "Content": "To create a sloping wall (a component of a wall), navigate to a wall and select the Straight Wall option in Create drop-down list.\n\nThe Create Straight Wall window is displayed.\n\nThere are eight steps to creating a sloping wall:\nNaming\nBy default in the Naming pane of the Create Sloping Wall window, the application automatically populates the Name field with a name based on the project or company autonaming rules. for further information on the autonaming rules, refer to Naming for further information.\nThe Use gaps in naming sequence checkbox is also selected by default, the user can select which auto name is to be used. To select the:\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nThe Material drop-down list by default is set to Pyrocrete, the material can be changed to another suitable material. From the Material drop-down list, the user can select from a list of suitable materials.\nHeight\n\nThe levels and height are the values at the start of the wall.\nSection\nTo create a sloping wall, use a rectangular section. For a wall with a variable height, use a section with a vertical slope. For a floor with a cross fall, use a section with a sloping base.\nStart / End Position\n\nTo create a slope, click Coordinates locked to unlock the Up field before selecting the start and end position.\nmiter\nUse perpendicular miters to avoid problems with the geometry.\nConnectivity\nThe connectivity functionality can be used.\nApply\nClick Apply to create the sloping wall.\nfirst available name, click first available name arrow.\nprevious available name, click previous available name arrow.\nnext available name, click next available name arrow.\nlast available name, click last available name arrow.\nfirst available name, click first available name arrow.\nfirst available name, click first available name arrow.\nprevious available name, click previous available name arrow.\nprevious available name, click previous available name arrow.\nnext available name, click next available name arrow.\nnext available name, click next available name arrow.\nlast available name, click last available name arrow.\nlast available name, click last available name arrow.\nNote:\nThe positions can be modified if the connectivity is activated.\n\n\n\nNaming\nStraight Wall\nCreate\nCreate Straight Wall\nNaming\nNaming\nCreate Sloping Wall\nName\nNaming\nUse gaps in naming sequence\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nMaterial\nPyrocrete\nMaterial\nHeight\nSection\nStart / End Position\nUp\nNote:\nConnectivity\nApply\nApply"}
{"Headers": "Building Applications Tools", "Content": "The section of the user guide provides the user with a more detailed description of the tools associated with the building applications.\n\n\n"}
{"Headers": "Read-only Mode", "Content": "If the user navigates to an element that is read-only, the properties can be displayed but cannot be modified.\nTo display the properties of the CE (that is read-only), on the Building Applications window, select an element as the CE.\n\nBy default, the Parameters window is displayed.\n\nThe user is unable to modify any of the parameters of the CE.\n\n\n\nBuilding Applications\nParameters"}
{"Headers": "Rename", "Content": "The user can rename the CE and all its members. For example if the CE is named /NAME and has members /NAME-1, /NAME-2, renaming the CE to /NEWNAME automatically renames its members /NEWNAME-1, /NEWNAME-2.\nTo rename the CE and all its members, on the Building tab, in the Modify group, click Rename to display the Rename window.\n\nFrom the Rename window, enter a new name in the Name field, to specify the names of the members, select the Confirm names checkbox. If there are too many members, the Confirm names checkbox is greyed out.\nThe user can choose whether to use any unused names or only use names that are after any existing names. Select the Use gaps in naming sequence checkbox.\nFrom the Source for naming pane of the Rename window, select a source of names. The source is used to calculate the names of the members. There are two ways to select the source:\nSelect the list displayed in the Source for naming pane of the Rename window.\nAlternatively, click Pick source for naming and select the element in the 3D graphical view.\nClick Apply to confirm the renaming of the CE and all its members.\nClick Dismiss to discard any inputs and close the Rename window.\nIf the user has selected the Confirm names checkbox, once the user has selected Apply a second Rename window is displayed.\n\nThe type, existing name (in parentheses) and the proposed name are displayed for each element. The user can modify the proposed name.\nClick OK to rename the CE and all its members and close the Rename window.\nClick Cancel to discard any inputs and close the Rename window.\n\n\n\nBuilding\nModify\nRename\nRename\nRename\nName\nConfirm names\nConfirm names\nUse gaps in naming sequence\nSource for naming\nRename\nSource for naming\nRename\nPick source for naming\nApply\nDismiss\nRename\nConfirm names\nApply\nRename\nOK\nRename\nCancel\nRename"}
{"Headers": "Copy", "Content": "The user can often save repetitive work by designing part of a model and then creating and repositioning one or more copies of that part of the design. To copy the CE, on the Building Applications tab, in the Modify group, click Copy to display the Copy window.\n\nFrom the Copy window, enter a new name for the CE in the Name field, the user can then position the new CE as required.\nSelect the Confirm names checkbox to specify the names of the members. If there are too many members the Confirm names checkbox is greyed out.\nTo select the naming method, select the Use gaps in naming sequence checkbox to choose whether to use any unused names or only use names that are after any existing names.\nFrom the Pick Target hierarchy pane of the Copy window, select the target hierarchy. The element must be the same type as the owner of the element to copy. The target hierarchy can be selected in two ways:\nNavigate to the required hierarchy from the list displayed in the Pick Target hierarchy pane of the Copy window.\nAlternatively, from the Copy window, select Pick Target hierarchy and select the element in the 3D graphical view.\nTo move the copy by a specified distance in a specified direction (offset). There are two ways to do this:\nEnter the co-ordinates in the fields for east, north and up, to avoid changing a co-ordinate in a field, click Coordinate unlocked to lock the co-ordinate field.\nThe reference for the new copied element can also be modified by entering the name of an existing element in the Wrt field. If the field is greyed out, click coordinate locked to unlock the field.\nAlternatively, from the Copy window, select Pick new position of reference to pick a new position in the 3D graphical view. The default origin is the origin of the element to be copied but you can select a p-point using the Reference drop-down list.\nClick Apply to copy the CE with a new name, then click Dismiss to close the Copy window.\nIf the Confirm names checkbox has been selected a second Copy window is displayed.\n\nThe type, name of the copied element (in parentheses) and the name of the new element are displayed for each element. The proposed name can be modified.\nClick OK to modify the names. The first Copy window is displayed so that it can be used to make another copy.\n\n\n\nBuilding Applications\nModify\nCopy\nCopy\nCopy\nName\nConfirm names\nConfirm names\nUse gaps in naming sequence\nPick Target hierarchy\nCopy\nPick Target hierarchy\nCopy\nCopy\nPick Target hierarchy\nCoordinate unlocked\nWrt\ncoordinate locked\nCopy\nPick new position of reference\nReference\nApply\nDismiss\nCopy\nConfirm names\nCopy\nOK\nCopy"}
{"Headers": "Split Straight Wall", "Content": "The user can split a straight wall.\nIn the Building Applications window, identify the required straight wall element as the CE, on the Building Applications tab, in the Modify group, click Split to display the Spilt vertically window.\n\nBy default in the Naming pane of the Split vertically window, the application automatically populates the Name field with a name based on the project or company rules.\nThe user can change the name which does not conform to the autonaming rules, to do this, type a new name into the Name field. If this name already exists, an Error window is displayed. If the name does not conform with the autonaming rules, Apply remains greyed out as long as the name is not properly entered.\nIn the Position pane of the Split vertically window, enter the distance from the start of the wall. The distance from the end of the wall is automatically calculated and displayed in the End field.\nAlternatively, click Graphical Pick, the user is prompted to Pick Position (Snap) WP Snap in the 3D graphical view. Once the selection has been made the user is prompted again to pick a position. The Start and End fields are automatically populated.\nClick Apply to split the straight wall. Click Split horizontally to split the straight wall horizontally. Refer to Split horizontally for further information.\nClick Dismiss to cancel the split, and close the Split vertically window.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nlast available name, click last available name.\nfirst available name, click first available name.\nfirst available name, click first available name.\nprevious available name, click previous available name.\nprevious available name, click previous available name.\nnext available name, click next available name.\nnext available name, click next available name.\nlast available name, click last available name.\nlast available name, click last available name.\nNote:\nAvoid sub-components when the split position is being defined, as these will only penetrate their owner.\n\n\n\nSplit horizontally\nBuilding Applications\nBuilding Applications\nModify\nSpilt vertically\nNaming\nSplit vertically\nName\nfirst available name\nprevious available name\nnext available name\nlast available name\nName\nError\nApply\nPosition\nSplit vertically\nEnd\nGraphical Pick\nPick Position (Snap) WP Snap\nStart\nEnd\nApply\nSplit horizontally\nSplit horizontally\nDismiss\nSplit vertically\nNote:"}
{"Headers": "Split horizontally", "Content": "To split the component horizontally, click Split horizontally to display the Split horizontally window.\n\nThere are three steps to use this window:\nNaming\nType the name of the new part of the element in the Name field. The name must not exist. If the name is compulsory for this project, Apply remains greyed out as long as the name not properly entered. If a name is proposed according to the project naming convention, the user can change the name or use the one proposed.\nSplit Level\nThere are two methods to define the split level:\nApply\nClick Apply to split the component. The sub-components are shared between the components depending on their position. If the sub-component is near the split line, the sub\u2011component stays in the original component but it penetrates the other component as well. The Modify Component window replaces the Split horizontally window. The new component can be modified. If Apply is greyed out, type a valid name in the Name field to activate it.\nDismiss\nClick Dismiss to cancel the split and close the Split horizontally window.\nTo split the component vertically, click Split vertically, to display the Split vertically window.\n\nType a value in the Split level field.\nClick Split Level, the user is prompted Pick split level (Snap) Snap and select the level in the 3D graphical view.\nType a value in the Split level field.\nType a value in the Split level field.\nClick Split Level, the user is prompted Pick split level (Snap) Snap and select the level in the 3D graphical view.\nClick Split Level, the user is prompted Pick split level (Snap) Snap and select the level in the 3D graphical view.\n\n\n\nSplit horizontally\nSplit horizontally\nNaming\nName\nApply\nSplit Level\nSplit level\nSplit Level\nPick split level (Snap) Snap\nApply\nApply\nModify Component\nSplit horizontally\nApply\nName\nDismiss\nDismiss\nSplit horizontally\nSplit vertically\nSplit vertically"}
{"Headers": "Split Floors, General Walls, Landings, Bases and Gratings", "Content": "To split a floor, general wall, landing, base or grating, navigate to the required element and identify it as the CE.\nOn the Building Applications tab, in the Modify group, click Split to display the Split vertically window.\n\n\n\nBuilding Applications\nModify\nSplit\nSplit vertically"}
{"Headers": "Split Vertically", "Content": "\nNaming\nType the name of the new part of the element in the Name field. The name must not exist. If the name is compulsory for this project, Apply remains greyed out as long as the name not properly entered. If a name is proposed according to the project naming convention, the user can change the name or use the one proposed.\nStart / End Position\nThere are three methods to define the start position in the Start Position frame:\nFrom the Vertex drop-down list, select a Vertex.\nEnter values in the East, North and Up fields.\nClick Graphically Pick Start, the user is prompted to Pick Start (Snap) Snap: and select the position in the graphical view. If the direction is not locked, the direction is modified to suit the start position.\nDirection\nThere are five methods to define the direction:\nApply\nClick Apply to split the component. The sub-components are shared between the components depending on their position. If the sub-component is near the split line, the sub\u2011component stays in the original component but it penetrates the other component as well. The Modify Component window replaces the Split vertically window.\nThe new component can be modified. If Apply is greyed out, type a valid name in the Name field to activate it.\nDismiss\nClick Dismiss to cancel the split and close the Modify Component window.\nSelect a vertex in the Vertex drop-down list in the End Position frame.\nEnter values in the East, North and Up fields in the End Position frame.\nClick Graphically Pick End in the End Position frame, the user is prompted Pick End (Snap) Snap:, and select the position in the 3D graphical view.\nType the direction in the Direction field.\nClick Pick surface or edge to define direction, the user is prompted Pick Face or Edge:, and select the position in the graphical view.\nSelect a vertex in the Vertex drop-down list in the End Position frame.\nSelect a vertex in the Vertex drop-down list in the End Position frame.\nEnter values in the East, North and Up fields in the End Position frame.\nEnter values in the East, North and Up fields in the End Position frame.\nClick Graphically Pick End in the End Position frame, the user is prompted Pick End (Snap) Snap:, and select the position in the 3D graphical view.\nClick Graphically Pick End in the End Position frame, the user is prompted Pick End (Snap) Snap:, and select the position in the 3D graphical view.\nType the direction in the Direction field.\nType the direction in the Direction field.\nClick Pick surface or edge to define direction, the user is prompted Pick Face or Edge:, and select the position in the graphical view.\nClick Pick surface or edge to define direction, the user is prompted Pick Face or Edge:, and select the position in the graphical view.\n\n\n\nNaming\nName\nApply\nStart Position\nVertex\nVertex\nEast\nNorth\nUp\nGraphically Pick Start,\nPick Start (Snap) Snap:\nDirection\nVertex\nEnd Position\nEast\nNorth\nUp\nEnd Position\nGraphically Pick End\nEnd Position\nPick End (Snap) Snap:\nDirection\nPick surface or edge to define direction\nPick Face or Edge:\n\nApply\nApply\nModify Component\nSplit vertically\nApply\nName\nDismiss\nDismiss\nModify Component"}
{"Headers": "Control the Graphical View", "Content": "To manage the list of visible objects in the graphical view (draw-list) or the representation of the objects in the graphical view, right click on the list of elements.\n\n\n\n"}
{"Headers": "Automatic Add CE", "Content": "If this option is active, the element is added to the graphical view when the element configuration window is displayed.\n\n\n"}
{"Headers": "Add CE", "Content": "The current element is added in the graphical view.\n\n\n"}
{"Headers": "Add CE with Colour", "Content": "The Colours window is displayed, when the user selects a colour, the current element is added in the graphical view in the selected colour.\n\n\n\nColours"}
{"Headers": "Add elements by name", "Content": "The Add elements by name window is displayed.\n\nType\nSelect the type of sub-component from the Type drop-down list.\nType the mask for the name in the Filter field is the wildcard for a single character. * is the wildcard character for multiple characters.\nColour\nClick Colour to select the colour.\nSelect the translucence of the owning component using the drop-down list.\nOk\nClick OK to add these elements to the graphical view with their owning components.\n\n\n\nAdd elements by name\nType\nType\nFilter\nColour\nColour\nOk\nOK"}
{"Headers": "Add elements by type", "Content": "All elements of the type selected from the sub-menu and belonging to the current element are added to the graphical view.\n\n\n"}
{"Headers": "Remove CE", "Content": "The element is removed from the graphical view.\n\n\n"}
{"Headers": "Remove All", "Content": "All the elements in the graphical view are removed.\n\n\n"}
{"Headers": "Remove elements by type", "Content": "All elements of the type selected from the sub-menu are removed from the graphical view.\n\n\n"}
{"Headers": "Apply negatives", "Content": "Changes the representation in the graphical view to activate the negatives (representation holes on / drawn).\n\n\n"}
{"Headers": "See negatives", "Content": "Changes the representation in the graphical view to deactivate the negatives (representation holes off).\n\n\n"}
{"Headers": "No Screeds", "Content": "Changes the representation level for the structure elements so that only the slab level of slabs and bases is shown.\n\n\n"}
{"Headers": "Include Screeds", "Content": "Changes the representation level for the structure elements so that only the slab level and finished level of slabs and bases is shown.\n\n\n"}
{"Headers": "Screeds Only", "Content": "Changes the representation level for the structure elements so that only the finished level of slabs and bases is shown.\n\n\n"}
{"Headers": "Automatic Mark Members", "Content": "If this option is activated, the name of all the members of the current element is displayed in the graphical view.\n\n\n"}
{"Headers": "Automatic Mark Connected", "Content": "If this option is activated, the name of all the elements connected to the current element is displayed in the graphical view.\n\n\n"}
{"Headers": "Display Aids", "Content": "If this option is activated, the proposed position, orientation and form of elements being modified or created is shown in the graphical view by graphical aids.\nCreate list with all connected elements: If this option is activated, the name of all the elements connected to the current element is displayed in the Go to connected element pane of the Building Applications window.\n\n\n\nGo to connected element"}
{"Headers": "Delete and Tidy", "Content": "Deletes the CE and deletes unwanted nodes and joints from the graphical view. Refer to Tidy Joints and Nodes for further information.\n\n\n\nTidy Joints and Nodes\nTidy Joints and Nodes"}
{"Headers": "Diagnostic Wizard", "Content": "The Diagnostic Wizard is an administration tool, which enables the user to translate elements from one catalogue to another for sprefs and matrefs.\nIt uses the DBCATALOGUE file to define which databases are associated with which project type and the CORRESPONDENCE file to define the translation of sprefs. It also checks that the data is correctly structured for Building Applications and can be useful for checking and modifying the project as required.\nTo analyze a project\u2019s data, on the Buildings tab, in the Tools group, click Check to display the Diagnostic Wizard window with the name of the selected element in the title bar.\n\nIf the CORRESPONDENCE file does not exist in the defaults directory for the project, an error message is displayed.\n\nIf the file is missing the user will not be able to translate sub-components. The user can generate a CORRESPONDENCE file by clicking Create File on the Diagnostic Wizard window.\nClick OK on the Error window to display the Diagnostic Wizard window with the name of the selected element in the title bar.\nProject Type\nThe project types and the associated databases are defined in the DBCATALOGUE parameter file. Check the project type checkbox to select which databases will be used for translating the catalogue and material references.\nSpecification\nThe specification frames show the number of components and sub-components that reference specifications in the databases associated with each project type. Elements that reference other specifications are shown as Other. Any elements that reference elements under a LIMBO specification are shown as Limbo. The selected project type is highlighted in green. Lines that contain components or sub-components that reference other project types are highlighted in cyan.\nTranslate\nTo translate specification references click Translate. Any components that share the same catalogue reference as specification components in the selected project type have their spref attribute modified to point to these specification components. Any sub-components found in the first column of the CORRESPONDENCE file have their spref attribute changed to point to the second column. The form values are updated when the translation is complete. Any components or sub-components that cannot be translated are shown on form in the form of a list.\n\nThe number of errors is displayed in the title of the window. To navigate to the component or sub-component that could not be translated in the Model Explorer, click on the required line in the list. Click Output to save the errors to a text file.\n\nThe user can navigate to a required location and name the text file.\nTo generate a new CORRESPONDENCE file, click Create File.\n\nThe file will contain two columns for all sub-component specification components and any equivalents that already exist in the CORRESPONDENCE file. Any sub-components that do not have an equivalent are added to the file. To use this file, it must be edited to add the equivalent specification references and then copied to the defaults directory to replace any existing file.\nMaterial\nThe material frame shows the number of components and sub-components that reference materials in the databases associated with each project type. Elements that reference other materials are shown as Other. The line belonging to the selected project type is highlighted in green. Lines that contain components or sub-components that don't reference the selected project type are highlighted in cyan.\nTo translate the material references to the selected project type, select the required materials from the drop-down lists and click Translate. The materials in the lists are from the selected project type. The screed material is used for screeds. The slab material is used for other concrete elements and the steel material is used for steel elements.\nThe values are updated when the translation is complete. Any components or sub-components that cannot be translated are shown on form in the form of a list.\nThe number of errors is shown in the title of the form. Select the line in the list to navigate to the component or sub-component that could not be translated. Click Output to save the errors to a text file.\nThe remaining gadgets on the window identify potential errors the selected elements. If potential errors are found, the associated gadgets are highlighted. Tidy or Modify are highlighted in red and Check are highlighted in yellow. To delete invalid elements click Tidy next to the list of elements. To modify the invalid elements click Modify next to the list of elements. Any elements that could not be deleted or modified are shown on a form.\nCheck enables the user to view a list of elements without modifying or deleting them.\n\nTo navigate to the an element in the Model Explorer, click on the required element in the list.\nClick Output to save the errors to a text file.\n\n\n\nDiagnostic Wizard\nBuildings\nTools\nCheck\nDiagnostic Wizard\nCreate File\nDiagnostic Wizard\nOK\nError\nDiagnostic Wizard\nProject Type\nSpecification\nOther\nLimbo\nTranslate\nTranslate\nOutput\nCreate File.\nMaterial\nOther\nTranslate\nOutput\nTidy\nModify\nCheck\nTidy\nModify\nCheck\nOutput"}
{"Headers": "Detected Errors", "Content": "PNODE elements unconnected to wall, column or beam components.\nCan be deleted by clicking Tidy.\nCMPF and CMFI elements that do not reference specification references or own SBFI elements.\nCan be deleted by clicking Tidy.\nSBFR, CWALL, CFLOOR or CSCREED elements that do not own components.\nCan be deleted by clicking Tidy.\nFLOOR or SCREED elements that do not have the correct values for the LEVEL attribute to allow anchor spacing checks to be carried out.\nThe values can be changed to 1 to 20 by clicking Modify.\nPNODE, SCTN, GENSEC, STWALL, WALL, GWALL, FLOOR, SCREED or PANEL elements owned by a FRMW.\nNew owning elements (CWALL, CFLOOR, CSCREED or SBFR) can be created and the elements included under them by clicking Modify. PNODE's are included into the first element found that owns them.\nSBFI or FIXING elements that reference a catalogue component but that also own a TMPL element.\nThe specification reference can be unset so only that the TMPL is used to define the sub-component geometry by clicking Modify.\nSBFI or FIXING elements that have a property called RULE that evaluates to false.\nThe user can navigate to each sub-component in turn to discover why the sub-component is invalid by selecting the line in the list that corresponds to the sub-component.\nPNODE elements unconnected to wall, column or beam components.\nCan be deleted by clicking Tidy.\nCMPF and CMFI elements that do not reference specification references or own SBFI elements.\nCan be deleted by clicking Tidy.\nSBFR, CWALL, CFLOOR or CSCREED elements that do not own components.\nCan be deleted by clicking Tidy.\nFLOOR or SCREED elements that do not have the correct values for the LEVEL attribute to allow anchor spacing checks to be carried out.\nThe values can be changed to 1 to 20 by clicking Modify.\nPNODE, SCTN, GENSEC, STWALL, WALL, GWALL, FLOOR, SCREED or PANEL elements owned by a FRMW.\nNew owning elements (CWALL, CFLOOR, CSCREED or SBFR) can be created and the elements included under them by clicking Modify. PNODE's are included into the first element found that owns them.\nSBFI or FIXING elements that reference a catalogue component but that also own a TMPL element.\nThe specification reference can be unset so only that the TMPL is used to define the sub-component geometry by clicking Modify.\nSBFI or FIXING elements that have a property called RULE that evaluates to false.\nThe user can navigate to each sub-component in turn to discover why the sub-component is invalid by selecting the line in the list that corresponds to the sub-component.\n\nPNODE elements unconnected to wall, column or beam components.\nCan be deleted by clicking Tidy.\nCMPF and CMFI elements that do not reference specification references or own SBFI elements.\nCan be deleted by clicking Tidy.\nSBFR, CWALL, CFLOOR or CSCREED elements that do not own components.\nCan be deleted by clicking Tidy.\nFLOOR or SCREED elements that do not have the correct values for the LEVEL attribute to allow anchor spacing checks to be carried out.\nThe values can be changed to 1 to 20 by clicking Modify.\nPNODE, SCTN, GENSEC, STWALL, WALL, GWALL, FLOOR, SCREED or PANEL elements owned by a FRMW.\nNew owning elements (CWALL, CFLOOR, CSCREED or SBFR) can be created and the elements included under them by clicking Modify. PNODE's are included into the first element found that owns them.\nSBFI or FIXING elements that reference a catalogue component but that also own a TMPL element.\nThe specification reference can be unset so only that the TMPL is used to define the sub-component geometry by clicking Modify.\nSBFI or FIXING elements that have a property called RULE that evaluates to false.\nThe user can navigate to each sub-component in turn to discover why the sub-component is invalid by selecting the line in the list that corresponds to the sub-component.\n\n\n\nPNODE elements unconnected to wall, column or beam components.\nTidy\nCMPF and CMFI elements that do not reference specification references or own SBFI elements.\nTidy\nSBFR, CWALL, CFLOOR or CSCREED elements that do not own components.\nTidy\nFLOOR or SCREED elements that do not have the correct values for the LEVEL attribute to allow anchor spacing checks to be carried out.\nModify\nPNODE, SCTN, GENSEC, STWALL, WALL, GWALL, FLOOR, SCREED or PANEL elements owned by a FRMW.\nModify\nSBFI or FIXING elements that reference a catalogue component but that also own a TMPL element.\nModify\nSBFI or FIXING elements that have a property called RULE that evaluates to false."}
{"Headers": "Concrete Quantities", "Content": "The Concrete Quantities functionality allows the user to create accurate and detailed reports of civil engineering concrete design practices.\nThe user will be able to view the following results:\nThe user will be able to view results in a variety of ways and also save them to a text file.\nTo carry out the concrete quantities calculations for a structural element, on the Buildings tab, in the Tools group, click Concrete Quantities to display the Concrete Quantities window.\n\nThe Concrete Quantities window allows the user to select the material type and the element types that the calculations will be applied to.\nBy default All the material types will be selected but the user can select an alternative material type from the Material drop-down list.\n\nThe limitation defined will apply to the concrete take off as a function of the MATREF attribute content.\nAfter selecting the material type, the user can select the element type that the concrete quantities calculations will be applied to. By default all of the elements are selected. Click to deselect the element type checkboxes which are not required for the take off calculations.\nEach element type is linked to a element that works as follows:\nObject type\nFLOOR\nWALL\nCOLUMN\nBEAM\nBASE\nSTAIRS\nWORLD\nSITE\nactive\nactive\nactive\nactive\nactive\nactive\nZONE\nactive\nactive\nactive\nactive\nactive\nactive\nSTRU\nactive\nactive\nactive\nactive\nactive\nactive\nFRMW\nactive\nactive\nactive\nactive\nactive\nactive\nSBFR\nactive\nactive\nactive\nCFLOOR\nactive\nactive\nCSCREE\nactive\nactive\nCWALL\nactive\nSTWALL\nactive\nWALL\nactive\nGWALL\nactive\nFLOOR\nactive\nactive\nactive\nSCREED\nactive\nactive\nGENSEC\nactive\nactive\nSCTN\nactive\nactive\nPANE\nactive\nactive\nactive\nObject type\nFLOOR\nWALL\nCOLUMN\nBEAM\nBASE\nSTAIRS\nWORLD\n\n\n\n\n\n\nSITE\nactive\nactive\nactive\nactive\nactive\nactive\nZONE\nactive\nactive\nactive\nactive\nactive\nactive\nSTRU\nactive\nactive\nactive\nactive\nactive\nactive\nFRMW\nactive\nactive\nactive\nactive\nactive\nactive\nSBFR\n\n\nactive\nactive\n\nactive\nCFLOOR\nactive\n\n\n\nactive\n\nCSCREE\nactive\n\n\n\nactive\n\nCWALL\n\nactive\n\n\n\n\nSTWALL\n\nactive\n\n\n\n\nWALL\n\nactive\n\n\n\n\nGWALL\n\nactive\n\n\n\n\nFLOOR\nactive\n\n\n\nactive\nactive\nSCREED\nactive\n\n\n\nactive\n\nGENSEC\n\n\nactive\nactive\n\n\nSCTN\n\n\nactive\nactive\n\n\nPANE\n\n\nactive\nactive\n\nactive\nClick OK to begin the concrete quantities calculations.\nA progress window is displayed showing how the concrete quantities calculations are progressing.\nThe user can interrupt the concrete quantities calculations process at any time by clicking Cancel.\nWhile the take off calculations are being carried out, the Concrete Quantities application automatically manages the procedure and displays all execution messages and errors (if there are any) in the Execution window at the end of procedure.\n\nAfter the concrete quantities calculations have been completed the basic results are displayed in the Results List pane of the Concrete Quantities window.\n\nTo display more detailed results of the concrete quantities required, click Output to display the Result window. Refer to Results for further information.\nObject type\nFLOOR\nWALL\nCOLUMN\nBEAM\nBASE\nSTAIRS\nWORLD\nSITE\nactive\nactive\nactive\nactive\nactive\nactive\nZONE\nactive\nactive\nactive\nactive\nactive\nactive\nSTRU\nactive\nactive\nactive\nactive\nactive\nactive\nFRMW\nactive\nactive\nactive\nactive\nactive\nactive\nSBFR\nactive\nactive\nactive\nCFLOOR\nactive\nactive\nCSCREE\nactive\nactive\nCWALL\nactive\nSTWALL\nactive\nWALL\nactive\nGWALL\nactive\nFLOOR\nactive\nactive\nactive\nSCREED\nactive\nactive\nGENSEC\nactive\nactive\nSCTN\nactive\nactive\nPANE\nactive\nactive\nactive\nCalculation of the volume of civil engineering concrete objects.\nCalculation of formwork surface areas for civil engineering concrete objects.\nCalculation of slab usable surface areas.\nCalculation of the volume of civil engineering concrete objects.\nCalculation of the volume of civil engineering concrete objects.\nCalculation of formwork surface areas for civil engineering concrete objects.\nCalculation of formwork surface areas for civil engineering concrete objects.\nCalculation of slab usable surface areas.\nCalculation of slab usable surface areas.\nFloor\nWall\nColumn\nBeam\nBase\nStair\nFloor\nFloor\nWall\nWall\nColumn\nColumn\nBeam\nBeam\nBase\nBase\nStair\nStair\nNote:\nAll is the default value that provides no limitations with regard to material when concrete take off is calculated.\nNote:\nThe messages displayed in the Execution window are also displayed on the Results window and will also be saved at the end of the savework file.\n\n\n\nResults\nConcrete Quantities\nBuildings\nTools\nConcrete Quantities\nConcrete Quantities\nConcrete Quantities\nAll\nMaterial\nNote:\nAll\nMATREF\nObject type\nFLOOR\nWALL\nCOLUMN\nBEAM\nBASE\nSTAIRS\nWORLD\nSITE\nZONE\nSTRU\nFRMW\nSBFR\nCFLOOR\nCSCREE\nCWALL\nSTWALL\nWALL\nGWALL\nFLOOR\nSCREED\nGENSEC\nSCTN\nPANE\nOK\nCancel.\nConcrete Quantities\nExecution\nNote:\nT\nExecution\nResults\nResults List\nConcrete Quantities\nOutput\nResult\nResults"}
{"Headers": "Results", "Content": "From the Result window, the user can view the detailed results of the concrete quantities calculations and save the results to an external file.\nSave Results\nThe user can save any of the results to a file from the Result window by selecting Savework > File, to display the Save the result window.\n\nBy default, a file location is displayed in the Save in box which the user can change. From the Save in drop-down list, select the location to which the result file is to be saved.\nIn the Filename box, input the name of the results file, then from the Save as type drop-down list, select a file type.\nClick Save to save the result file or Cancel to discard any inputs and close the Save the result window.\n\n\n\nResult\nSave Results\nResult\nSavework > File\nSave the result\nSave in\nSave in\nFilename\nSave as type\nSave\nCancel\nSave the result"}
{"Headers": "Details Tab", "Content": "By default the Result window is displayed with the Details tab selected. The user can select the other tabs to display the concrete quantities calculations for the element types.\n\nAll the results generated by the Concrete Quantities application makes no allowance for construction sequence of formwork configuration.\nIn AVEVA E3D Design, a mass look-up is used to provide the surface area and volume of an object as follows:\nVolume\n=\n!!CE.Nvol\nSurface area\n=\n!!CE.NSrf\nVolume\n=\n!!CE.Nvol\nSurface area\n=\n!!CE.NSrf\nCalculating take off for a concrete civil engineering object can be defined as follows:\nNet surface\n=\nSurface area above and below area\n+\ncontour surface area\n+\ncontour surface area of openings\n-\nSurface area above and below an opening (full penetration)\n+\nSurface area above and below an opening (limited penetration beneath)\n+\nSurface area below an opening (limited penetration above)\nNet volume\n=\nVolume - Opening volume\nNet surface\n=\nSurface area above and below area\n\n+\ncontour surface area\n\n+\ncontour surface area of openings\n\n-\nSurface area above and below an opening (full penetration)\n\n+\nSurface area above and below an opening (limited penetration beneath)\n\n+\nSurface area below an opening (limited penetration above)\nNet volume\n=\nVolume - Opening volume\n\nVolume\n=\n!!CE.Nvol\nSurface area\n=\n!!CE.NSrf\nNet surface\n=\nSurface area above and below area\n+\ncontour surface area\n+\ncontour surface area of openings\n-\nSurface area above and below an opening (full penetration)\n+\nSurface area above and below an opening (limited penetration beneath)\n+\nSurface area below an opening (limited penetration above)\nNet volume\n=\nVolume - Opening volume\n\n\n\nResult\nDetails\nConcrete Quantities\nAVEVA E3D Design"}
{"Headers": "Walls Tab", "Content": "To view the concrete quantities calculations for the Walls element, select the Walls tab. The Result window is populated with the results for the Walls element.\n\nThe sleeve and the opening are negative objects. Terms used in the results must be construed as follows:\n\u2022\nTotal volume of wall without sleeved holes\n=\n+\nWall volume\nSleeved holes volume\n\u2022\nTotal volume of wall with sleeved holes\n=\nWall volume\n\u2022\nTotal surface area of wall without sleeved holes\n=\n+\nWall surface area\nSleeved holes surface area\n\u2022\nTotal surface area of wall with sleeved holes\n=\nWall surface area\n\u2022\nWall formwork surface area\n=\n+\n-\n-\nWall surface area\nSurface area at bottom of boxed out section\nTop and bottom surface areas\nWall (end) side surface area (m2)\nTotal volume of wall without sleeved holes\n=\n+\nWall volume\nSleeved holes volume\nTotal volume of wall with sleeved holes\n=\nWall volume\nTotal surface area of wall without sleeved holes\n=\n+\nWall surface area\nSleeved holes surface area\nTotal surface area of wall with sleeved holes\n=\nWall surface area\nWall formwork surface area\n=\n+\n-\n-\nWall surface area\nSurface area at bottom of boxed out section\nTop and bottom surface areas\nWall (end) side surface area (m2)\n\n\u2022\nTotal volume of wall without sleeved holes\n=\n+\nWall volume\nSleeved holes volume\n\u2022\nTotal volume of wall with sleeved holes\n=\nWall volume\n\u2022\nTotal surface area of wall without sleeved holes\n=\n+\nWall surface area\nSleeved holes surface area\n\u2022\nTotal surface area of wall with sleeved holes\n=\nWall surface area\n\u2022\nWall formwork surface area\n=\n+\n-\n-\nWall surface area\nSurface area at bottom of boxed out section\nTop and bottom surface areas\nWall (end) side surface area (m2)\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\n\n\nWalls\nWalls\nResult\nWalls\n2"}
{"Headers": "Floors Tab", "Content": "To view the concrete quantities calculations for the Floors element, select the Floors tab. The Result window is populated with the results for the Floors element.\n\nThe sleeved hole and the opening are negative objects. Terms used in the results must be construed as follows:\n\u2022\nTotal volume of slab without sleeved holes\n=\n+\nSlab volume\nSleeved hole volume\n\u2022\nTotal volume of slab with sleeved holes\n=\nSlab volume\n\u2022\nTotal surface area of slab without sleeved holes\n=\n+\nSlab surface area\nSleeved holes surface area\n\u2022\nTotal surface area of slab with sleeved holes\n=\nSlab surface area\n\u2022\nFormwork surface area beneath slab\n=\n+\n-\nSlab bottom surface area\nSurface area covered by the objects beneath the slab\nSurface area of opening (opening, sleeved holes, .)\n\u2022\nSlab surface area (bottom + contours)\n=\n=\nFormwork surface area beneath slab\nContour surface areas (of the opening and the slab\n\u2022\nUsable slab surface area\n=\n+\n-\nSurface area above the slab\nSurface area of bottom of boxed out section\nSurface area covered by the objects above the slab\n\u2022\nSlab formwork surface area\n=\n+\n+\nFormwork surface area below slab\nSlab contour surface area\nOpening contour surface areas\nTotal volume of slab without sleeved holes\n=\n+\nSlab volume\nSleeved hole volume\nTotal volume of slab with sleeved holes\n=\nSlab volume\nTotal surface area of slab without sleeved holes\n=\n+\nSlab surface area\nSleeved holes surface area\nTotal surface area of slab with sleeved holes\n=\nSlab surface area\nFormwork surface area beneath slab\n=\n+\n-\nSlab bottom surface area\nSurface area covered by the objects beneath the slab\nSurface area of opening (opening, sleeved holes, .)\nSlab surface area (bottom + contours)\n=\n=\nFormwork surface area beneath slab\nContour surface areas (of the opening and the slab\nUsable slab surface area\n=\n+\n-\nSurface area above the slab\nSurface area of bottom of boxed out section\nSurface area covered by the objects above the slab\nSlab formwork surface area\n=\n+\n+\nFormwork surface area below slab\nSlab contour surface area\nOpening contour surface areas\n\n\u2022\nTotal volume of slab without sleeved holes\n=\n+\nSlab volume\nSleeved hole volume\n\u2022\nTotal volume of slab with sleeved holes\n=\nSlab volume\n\u2022\nTotal surface area of slab without sleeved holes\n=\n+\nSlab surface area\nSleeved holes surface area\n\u2022\nTotal surface area of slab with sleeved holes\n=\nSlab surface area\n\u2022\nFormwork surface area beneath slab\n=\n+\n-\nSlab bottom surface area\nSurface area covered by the objects beneath the slab\nSurface area of opening (opening, sleeved holes, .)\n\u2022\nSlab surface area (bottom + contours)\n=\n=\nFormwork surface area beneath slab\nContour surface areas (of the opening and the slab\n\u2022\nUsable slab surface area\n=\n+\n-\nSurface area above the slab\nSurface area of bottom of boxed out section\nSurface area covered by the objects above the slab\n\u2022\nSlab formwork surface area\n=\n+\n+\nFormwork surface area below slab\nSlab contour surface area\nOpening contour surface areas\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\n\n\nFloors\nFloors\nResult\nFloors"}
{"Headers": "Columns Tab", "Content": "To view the concrete quantities calculations for the columns element, select the Columns tab. The Result window is populated with the results for the columns element.\n\nThe sleeve is a negative object. Terms used in the results must be construed as follows:\n\u2022\nTotal column volume without sleeved holes\n=\n+\nColumn volume\nSleeved holes volume\n\u2022\nTotal column volume with sleeved holes\n=\nColumn volume\n\u2022\nTotal column surface area without sleeved holes\n=\n+\nColumn surface area\nSleeved holes surface area\n\u2022\nTotal column surface area with sleeved holes\n=\nColumn surface area\n\u2022\nColumn formwork surface area\n=\nColumn surface area\nTop and bottom surface areas\nTotal column volume without sleeved holes\n=\n+\nColumn volume\nSleeved holes volume\nTotal column volume with sleeved holes\n=\nColumn volume\nTotal column surface area without sleeved holes\n=\n+\nColumn surface area\nSleeved holes surface area\nTotal column surface area with sleeved holes\n=\nColumn surface area\nColumn formwork surface area\n=\nColumn surface area\nTop and bottom surface areas\n\n\u2022\nTotal column volume without sleeved holes\n=\n+\nColumn volume\nSleeved holes volume\n\u2022\nTotal column volume with sleeved holes\n=\nColumn volume\n\u2022\nTotal column surface area without sleeved holes\n=\n+\nColumn surface area\nSleeved holes surface area\n\u2022\nTotal column surface area with sleeved holes\n=\nColumn surface area\n\u2022\nColumn formwork surface area\n=\nColumn surface area\nTop and bottom surface areas\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\n\n\ncolumns\nColumns\nResult\ncolumns"}
{"Headers": "Beams Tab", "Content": "To view the concrete quantities calculations for the beams element, select the Beams tab. The Result window is populated with the results for the beams element.\n\nThe sleeve is a negative object, terms used in the results must be construed as follows:\n\u2022\nTotal beam volume without sleeved holes\n=\n+\nBeam volume\nSleeved holes volume\n\u2022\nTotal beam volume with sleeved holes\n=\nBeam volume\n\u2022\nTotal beam surface area without sleeved holes\n=\n+\nBeam surface areas\nSleeved holes surface area\n\u2022\nTotal beam surface area with sleeved holes\n=\nBeam surface area\n\u2022\nBeam formwork surface area\n=\n-\n-\nTotal Beam surface area\nTwo ends of Beam\nBeam top surface area\nTotal beam volume without sleeved holes\n=\n+\nBeam volume\nSleeved holes volume\nTotal beam volume with sleeved holes\n=\nBeam volume\nTotal beam surface area without sleeved holes\n=\n+\nBeam surface areas\nSleeved holes surface area\nTotal beam surface area with sleeved holes\n=\nBeam surface area\nBeam formwork surface area\n=\n-\n-\nTotal Beam surface area\nTwo ends of Beam\nBeam top surface area\n\n\u2022\nTotal beam volume without sleeved holes\n=\n+\nBeam volume\nSleeved holes volume\n\u2022\nTotal beam volume with sleeved holes\n=\nBeam volume\n\u2022\nTotal beam surface area without sleeved holes\n=\n+\nBeam surface areas\nSleeved holes surface area\n\u2022\nTotal beam surface area with sleeved holes\n=\nBeam surface area\n\u2022\nBeam formwork surface area\n=\n-\n-\nTotal Beam surface area\nTwo ends of Beam\nBeam top surface area\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\n\n\nbeams\nBeams\nResult\nbeams"}
{"Headers": "Bases Tab", "Content": "To view the concrete quantities calculations for the bases element, select the Bases tab. The Result window is populated with the results for the bases element.\n\nThe sleeve is a negative object. Terms used in the results must be construed as follows:\n\u2022\nTotal base volume without sleeved holes\n=\n+\nBase volume\nSleeved holes volume\n\u2022\nTotal base volume with sleeved holes\n=\nBase volume\n\u2022\nTotal base surface area without sleeved holes\n=\n+\nBase surface areas\nSleeved holes surface area\n\u2022\nTotal base surface area with sleeved holes\n=\nBase surface area\n\u2022\nBase gross upper surface area\n=\nBase top surface area\n\u2022\nBase contour surface area\n=\nBase formwork surface area\n\u2022\nOpening formwork surface area\n=\nOpening formwork surface area\n\u2022\nFormwork surface area\n=\n+\nBased formwork surface area\nOpening formwork surface area\nTotal base volume without sleeved holes\n=\n+\nBase volume\nSleeved holes volume\nTotal base volume with sleeved holes\n=\nBase volume\nTotal base surface area without sleeved holes\n=\n+\nBase surface areas\nSleeved holes surface area\nTotal base surface area with sleeved holes\n=\nBase surface area\nBase gross upper surface area\n=\nBase top surface area\nBase contour surface area\n=\nBase formwork surface area\nOpening formwork surface area\n=\nOpening formwork surface area\nFormwork surface area\n=\n+\nBased formwork surface area\nOpening formwork surface area\n\n\u2022\nTotal base volume without sleeved holes\n=\n+\nBase volume\nSleeved holes volume\n\u2022\nTotal base volume with sleeved holes\n=\nBase volume\n\u2022\nTotal base surface area without sleeved holes\n=\n+\nBase surface areas\nSleeved holes surface area\n\u2022\nTotal base surface area with sleeved holes\n=\nBase surface area\n\u2022\nBase gross upper surface area\n=\nBase top surface area\n\u2022\nBase contour surface area\n=\nBase formwork surface area\n\u2022\nOpening formwork surface area\n=\nOpening formwork surface area\n\u2022\nFormwork surface area\n=\n+\nBased formwork surface area\nOpening formwork surface area\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\n\n\nbases\nBases\nResult\nbases"}
{"Headers": "Stairs Tab", "Content": "To view the concrete quantities calculations for the stairs element, select the Stairs tab. The Result window is populated with the results for the stairs element.\n\nIn results, the terms are defined as follows:\n\u2022\nFlight\n\u2022\nTotal volume of flight\n=\nVolume of flight\n\u2022\nTotal surface area of light\n=\nSurface area of flight\n\u2022\nFlight formwork surface area\n=\n-\nSurface area of flight\nUnderside of flight\n\u2022\nUpper landing\n\u2022\nTotal volume of upper landing step\n=\nVolume of upper landing step\n\u2022\nTotal surface area of upper landing step\n=\nSurface area of upper landing step\n\u2022\nUpper landing step formwork surface area\n=\n-\nSurface area of upper landing step\nSurface area above upper landing\n\u2022\nLower landing\n\u2022\nTotal volume of Lower landing step\n=\nVolume of lower landing step\n\u2022\nTotal surface area of lower landing step\n=\nSurface area of lower landing step\n\u2022\nLower landing step formwork surface area\n=\n-\nSurface area of lower landing step\nSurface area above lower upper landing\nFlight\n\n\n\nTotal volume of flight\n=\nVolume of flight\n\nTotal surface area of light\n=\nSurface area of flight\n\nFlight formwork surface area\n=\n-\nSurface area of flight\nUnderside of flight\nUpper landing\n\n\n\nTotal volume of upper landing step\n=\nVolume of upper landing step\n\nTotal surface area of upper landing step\n=\nSurface area of upper landing step\n\nUpper landing step formwork surface area\n=\n-\nSurface area of upper landing step\nSurface area above upper landing\nLower landing\n\n\n\nTotal volume of Lower landing step\n=\nVolume of lower landing step\n\nTotal surface area of lower landing step\n=\nSurface area of lower landing step\n\nLower landing step formwork surface area\n=\n-\nSurface area of lower landing step\nSurface area above lower upper landing\n\n\u2022\nFlight\n\u2022\nTotal volume of flight\n=\nVolume of flight\n\u2022\nTotal surface area of light\n=\nSurface area of flight\n\u2022\nFlight formwork surface area\n=\n-\nSurface area of flight\nUnderside of flight\n\u2022\nUpper landing\n\u2022\nTotal volume of upper landing step\n=\nVolume of upper landing step\n\u2022\nTotal surface area of upper landing step\n=\nSurface area of upper landing step\n\u2022\nUpper landing step formwork surface area\n=\n-\nSurface area of upper landing step\nSurface area above upper landing\n\u2022\nLower landing\n\u2022\nTotal volume of Lower landing step\n=\nVolume of lower landing step\n\u2022\nTotal surface area of lower landing step\n=\nSurface area of lower landing step\n\u2022\nLower landing step formwork surface area\n=\n-\nSurface area of lower landing step\nSurface area above lower upper landing\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\u2022\n\n\n\nstairs\nStairs\nResult\nstairs"}
{"Headers": "Savework Preview Tab", "Content": "To preview all of the results of the concrete quantities calculations, select the Savework Preview tab.\n\n\n\n\nSavework Preview"}
{"Headers": "Building by Group of Rooms", "Content": "The Room Manager application allows users to group and manage individual rooms as it is often industry good practice to group areas that share a common purpose, for example: fire ratings, hazards and construction requirements.\n\n\n\nRoom Manager"}
{"Headers": "Hierarchy", "Content": "The Building by group of rooms hierarchy is specific to the Room Manager application:\nUnder the Groups of rooms element, the hierarchy is common to the Room Manager application. for further information on the specific hierarchy, refer to Specific Hierarchy.\nBuilding by group of rooms element (Group World (GPWL))\nGroups of rooms element (Group Set (GPSET))\nBuilding by group of rooms element (Group World (GPWL))\nBuilding by group of rooms element (Group World (GPWL))\nGroups of rooms element (Group Set (GPSET))\nGroups of rooms element (Group Set (GPSET))\n\n\n\nSpecific Hierarchy\nBuilding by group of rooms\nRoom Manager\nGroups of rooms\nRoom Manager\nSpecific Hierarchy"}
{"Headers": "Building by Group of Rooms Element", "Content": "Referring to the Room Manager hierarchy, the first task that the user should perform is to create a Building by Group of Rooms element in the Building Applications window.\n\n\n\nRoom Manager\nBuilding by Group of Rooms\nBuilding Applications"}
{"Headers": "Create Building by Group of Rooms", "Content": "To create a Building by Groups of rooms element, navigate to the world element in the Building Applications window and select Building by Groups of rooms from the Create drop-down list.\n\nThe Create Building by Groups of rooms window is displayed.\n\nThe Naming part of the Create Building by Groups of rooms window is identical in format and functionality as the Building by Room window, for further information refer to Building by Room Element.\nThe user must identify the building that the rooms will be available for selection as part of a group. From the Building pane of the Create Building by Groups of rooms window, click to select the building.\nTo select the purpose of the Building by Groups of rooms element, from the Purpose pane of the Building by Groups rooms window, select Construction Group or Fire Group.\nClick Apply to create the Building by Groups of rooms element. The Modify Building window is displayed and the Building by Groups of rooms (GPWL) element is displayed in the Building Applications window and in the Applications window. for further information on the Modify Building window, refer to Modify Building by Group of Rooms.\nClick Dismiss to discard any inputs and close the Create Building by Groups of rooms window.\n\n\n\nBuilding by Room Element\nModify Building by Group of Rooms\nBuilding by Groups of rooms\nBuilding Applications\nBuilding by Groups of rooms\nCreate\nCreate Building by Groups of rooms\nNaming\nCreate Building by Groups of rooms\nBuilding by Room\nBuilding by Room Element\nBuilding\nCreate Building by Groups of rooms\nBuilding by Groups of rooms\nPurpose\nBuilding by Groups rooms\nConstruction Group\nFire Group\nApply\nBuilding by Groups of rooms\nModify\nBuilding\nBuilding by Groups of rooms (GPWL)\nBuilding Applications window\nApplications\nModify Building\nModify Building by Group of Rooms\nDismiss to\nCreate Building by Groups of rooms"}
{"Headers": "Modify Building by Group of Rooms", "Content": "All the tasks associated with the modification of a Building by Group of Rooms element can be performed from the Modify Building window, the building and purpose can be modified.\n\nClick Apply to create the Building by Groups of rooms element with any modification, Repeat to copy the Building by Groups of rooms element, Refresh to discard any modification and display the original attributes or Dismiss to discard any inputs and close the Modify Building by Groups of rooms window.\n\n\n\nBuilding by Group of Rooms\nModify Building\nApply\nBuilding by Groups of rooms\nRepeat\nBuilding by Groups of rooms\nRefresh\nDismiss\nModify Building by Groups of rooms"}
{"Headers": "Groups of Rooms Element", "Content": "Referring to the Room Manager hierarchy, the user must create a Groups of rooms element (GPSET) below an existing Building by Groups of rooms (GPWL) element in the Building Applications window and as a LEV element in the Applications window. GPSET elements correspond to different levels within the building.\nTo create a new Groups of rooms (GPSET) element make sure a Building by Groups of rooms (GPWL) element is selected in the Building Applications window. From the Building Applications window, in Create group, select Group of rooms from the drop down list, The Create Group of rooms window is displayed.\n\nThe Naming part of the Create Building by Groups of rooms window is identical in format and functionality as the Building by Room window, for further information refer to Building by Room Element.\nAll the building levels that have rooms associated with them are displayed in the Level pane of the Create Group of rooms window. Only the rooms associated with the selected building level will be displayed in the Rooms pane of the Create Group of rooms window.\nThe user can determine the type of volume on which the application makes it calculations and displays the results in the Create Building by Groups of rooms window. To do this:\nClick Inventory volume to display the results of the Structure, Components and Inventory calculations.\nor\nClick Flooding volume to display the results of the Structure, Components and Inventory calculations.\nClick Apply to create a GPSET/LEV element, the Modify Group of rooms window is displayed and the GPSET element is displayed in the Building Applications window and as a LEV element in the Applications window. The total number of rooms and the total gross volume is displayed.\nClick Dismiss to discard any inputs and close the Create Group of rooms window.\n\n\n\n\nBuilding by Room Element\nRoom Manager\nGroups of rooms\n(GPSET)\nBuilding by Groups of rooms (GPWL)\nBuilding Applications window\nLEV\nApplications\nGPSET\nGroups of rooms\n(GPSET)\nBuilding by Groups of rooms (GPWL)\nBuilding Applications\nBuilding\nApplications\nCreate\nGroup of rooms\nCreate Group of rooms\nNaming\nCreate Building by Groups of rooms\nBuilding by Room\nBuilding by Room Element\nLevel\nCreate Group of rooms\nRooms\nCreate Group of rooms\nCreate Building by Groups of rooms\nInventory volume\nStructure, Components and Inventory\nFlooding volume\nStructure, Components and Inventory\nApply\nGPSET/LEV\nModify Group of room\nGPSET\nBuilding Applications\nLEV\nApplications\nDismiss\nCreate Group of rooms"}
{"Headers": "Calculations Based on Room Groups", "Content": "Describes the calculations based on room groups.\n\n\n"}
{"Headers": "Calculation of Surface Areas", "Content": "The functionality available from the Modify Group of rooms is identical to those available from the Modify Inventory Volume window, refer to Air Volumes and Surface Areas for further information.\n\n\n\nAir Volumes and Surface Areas\nModify Group of rooms\nModify Inventory Volume\nAir Volumes and Surface Areas"}
{"Headers": "Calculation of Ceiling Area", "Content": "The functionality available from the Modify Group of rooms is identical to those available from the Modify Inventory Volume window, refer to Ceiling Area for further information.\n\n\n\nCeiling Area\nModify Group of rooms\nModify Inventory Volume\nCeiling Area"}
{"Headers": "Calculation of Floor Area", "Content": "The functionality available from the Modify Group of rooms is identical to those available from the Modify Inventory Volume window, refer to Floor Area for further information.\n\n\n\nFloor Area\nModify Group of rooms\nModify Inventory Volume\nFloor Area"}
{"Headers": "Calculation of Air Volumes", "Content": "The functionality available from the Modify Group of rooms is identical to those available from the Modify Inventory Volume window, refer to Air Volumes and Surface Areas for further information.\n\n\n\nAir Volumes and Surface Areas\nModify Group of rooms\nModify Inventory Volume\nAir Volumes and Surface Areas"}
{"Headers": "Calculation of Flood Volumes", "Content": "The functionality available from the Modify Group of rooms is identical to those available from the Modify Inventory Volume window, refer to Flood Volume and Surface Area for further information.\nNote:\nTo calculate the flood volume of a group of connected rooms, the user must ensure that the top level of each flood volume is at the same level.\n\n\n\nFlood Volume and Surface Area\nModify Group of rooms\nModify Inventory Volume\nFlood Volume and Surface Area\nNote:"}
{"Headers": "Calculation of Inventories", "Content": "The functionality available from the Modify Group of rooms is identical to those available from the Modify Inventory Volume window, refer to Modify Inventory for further information.\nNote:\nUnlike the room inventory that is updated automatically, you need to update the room group inventory regularly.\n\n\n\nModify Inventory\nModify Group of rooms\nModify Inventory Volume\nModify Inventory\nNote:"}
{"Headers": "Cable Designer", "Content": "The Cabling System application is supplied as a module within the AVEVA E3D\u2122 suite and allows the creation and routing of cables, and if required enclose the routed cables within cable trays.\nThe application can be divided broadly into three parts, namely, Cableways, Cables and Cable Tray Material. The design process is as follows:\nCableways are created early in the 3D modelling process to reserve space in the model for the cables and cable trays.\nCables are selected from the catalogue, optionally connected to equipment, before being joined to a cableway and routed along a cableway.\nCable tray material is added to the cableways either automatically or manually. There is also an option to perform preliminary dressing of a cableway.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"Headers": "Work Area", "Content": "Many features of the Cable System discipline user interface are common to multiple AVEVA E3D Design disciplines, mostly with the exception of the functionality available for the selection on the CABLING SYSTEM tab.\n\nThe ADMIN tab is only available for selection, if the user is a member of the ADMIN team.\n\n\n\nAVEVA E3D Design\nCABLING SYSTEM\nADMIN"}
{"Headers": "PROJECT tab", "Content": "Provides access to a number of key commands and facilities, most of the functionality available for selection are common to multiple AVEVA E3D Design disciplines.\n\n\n\nAVEVA E3D Design"}
{"Headers": "CABLING SYSTEM tab", "Content": "Includes the following functionality specific to the CABLING SYSTEM discipline:\nCreate\nModify\nDelete\nTools\nPenetrate\nConnect\nCreate\nCreate\nModify\nModify\nDelete\nDelete\nTools\nTools\nPenetrate\nPenetrate\nConnect\nConnect\n\n\n\nCABLING SYSTEM"}
{"Headers": "PowerWheel\u2122", "Content": "Many operations in the CABLING SYSTEM discipline can be initiated using the PowerWheel\u2122. The equivalent functionality is also available from the CABLING SYSTEM UI, all out of the box configurations for the PowerWheel\u2122 can be customized.\n\nFor further information, refer to PowerWheel\u2122.\n\n\n\nCABLING SYSTEM\nCABLING SYSTEM"}
{"Headers": "Cabling System", "Content": "The Cabling System application creates cableways, cables and cableway material (trays/ladders). If required the cables can also be routed through the cableways. The application is divided into three main areas, Cableways, Cables and Cableway material.\nCableways are created early in the design process to reverse space for the cables and cableway material. Cables are selected from the catalog and optionally connected to equipment element. Alternatively, the cables and connecting equipment could come from the Cable diagrams. Cableway material is also selected from a catalog and added to the cableways either automatically or manually.\n\n\n"}
{"Headers": "Hierarchy", "Content": "All database elements are owned by other elements, therefore elements must be created in a strict order. The following database elements are common to all Model disciplines:\nWorld\nSite\nZone\nWorld\nWorld\nSite\nSite\nZone\nZone\n\n\n\nModel"}
{"Headers": "Cabling System Specific Hierarchy", "Content": "Below the zone level in the Cabling System application, the cabling system specific elements are:\nCableway (Cway)\nCableway Branch (Cwbran)\nCableway Material (Ctmrl)\nCableway Material Component\nCable.\nCableway (Cway)\nCableway (Cway)\nCableway Branch (Cwbran)\nCableway Branch (Cwbran)\nCableway Material (Ctmrl)\nCableway Material (Ctmrl)\nCableway Material Component\nCableway Material Component\nCable.\nCable.\n\n\n"}
{"Headers": "Cableway (Cway)", "Content": "Cway elements are administrative and can own a number of cableway branches with common default cabling application defaults and can have any number of ends.\n\n\n"}
{"Headers": "Cableway Branch (Cwbran)", "Content": "Cwbran elements define a section of the cableway (space for the cables and cableway material (CTMTRL) element(s)) with a known head and tail.\n\n\n"}
{"Headers": "Cableway Material (Ctmtrl)", "Content": "Ctmtrl elements defines the type of cable tray material used and own a section of the cableway (made up from cableway material components).\n\n\n"}
{"Headers": "Cableway Material Component", "Content": "Cableway material components are owned by the cableway material elements. These components are available in the catalog and dictate the shape and geometry of the cableway. Cableway material components can run from the head to tail of the owning branch but can also be connected to other branches.\n\n\n"}
{"Headers": "Cable", "Content": "Cable elements are created after the layout of the cabling system has been defined by cableways. The created cables are then routed either automatically or manually along the cableways to connect to the equipment. The cable references a cable specification that contains the physical properties of the cable.\n\n\n\n"}
{"Headers": "Defaults", "Content": "Specifies the application defaults which are used to pre-populate data on various windows as they are loaded.\nAll the cabling specifications available in the catalog are shown in the Cabling Application Defaults window and therefore all the cabling elements available from the catalog are determined by the currently selected cabling specification.\nTo avoid having to specify the specification again for each cable element, the default cabling specification can be set at Cableway or Cableway Branch level. The selected specification will be used automatically at lower levels unless it is changed (the default cabling specification is said to be cascaded down the hierarchy).\nBy default, some fields in the Cabling Application Defaults window are automatically populated with values from the currently selected specification.\n\n\n\n\nCabling Application Defaults\nCabling Application Defaults"}
{"Headers": "Storage Areas", "Content": "Use to define the location of the Cableway and Cable elements in the Design database hierarchy. Choose a location from the drop-down menu: if a location is not listed refer to the system administrator.\nThe list of available storage areas is only populated with zones where the purpose is set to CABL.\n\n\n"}
{"Headers": "Cable Data", "Content": "Use to define the Excess Length defaults (head and tail excesses which are used when the cable cutting lengths are calculated).\nSpecify the Proximity Distance default (the distance from the head; the software will start searching for cableway entry points).\nIf fill checks are to be carried out by default, click to check the Fill Check checkbox.\nNote:\nThe Excess Length must be entered in this order.\n\n\n\nExcess Length\nNote\n:\nProximity Distance\n\nFill Check"}
{"Headers": "Specification", "Content": "From the list of available materials and cables, use to select the Cableway Material and Cable defaults.\nSelect the default System Ref - No System, High Voltage System, Compartment Heating System, Emergency Lighting System or Fire Alarm System.\nUse to define the minimum distance between one cable tray and another. Enter the defaults for the First (head), Intermediate and End (tail) gaps.\nEnter the Min. Length Straight Tray default, this specifies the minimum length for a straight tray.\n\n\n\nCableway Material\nCable\nSystem Ref\nNo System\nHigh Voltage System\nCompartment Heating System\nEmergency Lighting System\nFire Alarm System\nFirst\nIntermediate\nEnd\nMin. Length Straight Tray"}
{"Headers": "Cableway Data", "Content": "Use to define the default Width and Height for the cableway volume (which includes the space for the cables volume and material) the access height default, maximum layers default, Cable Excess (excess length default) as a percentage of the total length of the cable.\nUse to specify the Maximum Fill default (based on the cross-sectional area of the cableway volume) and Fill Check Utility Allowance default based on the cross-sectional area of the cableway volume (the value must be greater than 1).\nClick to select the Allowable Class:\nClick the Create Head/Tail RNODEs checkbox to automatically create the head/tail RNODEs on the ends of the cableway branch.\nThe Purpose field is automatically populated with the CABL attribute by default.\nunset - default\nPOWER\nCOMMS\nSIGNAL\nCONTROL\nWIRE\nunset - default\nunset - default\nPOWER\nPOWER\nCOMMS\nCOMMS\nSIGNAL\nSIGNAL\nCONTROL\nCONTROL\nWIRE\nWIRE\nNote:\nMaximum fill can no longer be input at values greater than 100%.\n\n\n\nWidth\nHeight\nCable Excess\nMaximum Fill\nFill Check Utility Allowance\nNote\n:\nCreate Head/Tail RNODEs\nPurpose\nCABL"}
{"Headers": "Auto Routing Criteria", "Content": "Use to define the free-route tolerance - this is an extra 'length' that is added between the STAREF of the CABLE + First POINTR of the Free Route and Last POINTR of the Free Route and ENDREF of the CABLE. (As as the user may want to bend the cable into the STAREF / ENDREF further away than just the MINIMUM BEND RADIUS of the CABLE. If required bend radius checks can be carried out click to check the Perform bend radius checks checkbox).\nUse to switch on or off the layout cable mode (default is off).\nOptimize Auto-route map\nMinimize Free Route\nMinimize Total Length\nOptimize Auto-route map\nOptimize Auto-route map\nMinimize Free Route\nMinimize Free Route\nMinimize Total Length\nMinimize Total Length\n\n\n\nOptimize Auto-route map\nMinimize Free Route\nMinimize Total Length\nfree-route tolerance\n\nPerform bend radius checks\nayout cable mode\nOptimize Auto-route map\nMinimize Free Route\nMinimize Total Length"}
{"Headers": "Optimize Auto-route map", "Content": "Use to map the auto-route functionality in the most efficient way.\n\n\n"}
{"Headers": "Minimize Free Route", "Content": "Use to route the cable to or from the closets valid entry or exit point, finding the shortest path through the cableway branches.\n\n\n"}
{"Headers": "Minimize Total Length", "Content": "Use to take the shortest possible route between the start and end points, using any of the valid entry or exit points within the RANEQUIP range to minimize the length.\nNote:\nThe closest points will not always be used.\n\n\n\nNote\n:"}
{"Headers": "Reset", "Content": "Use Reset to populate the Settings window with the last saved version.\n\n\n\nReset\nSettings"}
{"Headers": "Default", "Content": "Use Default to populate the Settings window with the defaults.\n\n\n\nDefault\nSettings"}
{"Headers": "Interference Class Defaults", "Content": "Displays the interference class defaults (rules) available for selection for use with fill level calculations. Interference classes define which cables can be routed on a cableway or cableway segment. In the MODEL module the Interference Class Defaults window is read only.\n\nFor further information, refer to Cable, Cableway, Cabletray Volume, and .\n\n\n\nCable\nCableway\nCabletray Volume\nMODEL\nInterference Class Defaults\nCable\nCableway\nCabletray Volume\n"}
{"Headers": "Cableway", "Content": "Use to modify the currently selected cableway element.\n\n\n\n"}
{"Headers": "Cableway Branch", "Content": "Use to create a cableway branch which is the starting point from which all other cabling system elements are added. A cableway branch must be created below an existing Cableway element.\n\nThe functionality available from the Cableway Branch Create Tasks window is identical to that described in Cableway.\nThe newly created cableway branch is shown in the 3D view automatically routed along an orthogonal path connecting the Head and Tail positions. The Branch Tasks window is automatically displayed.\nNote:\nThe Cableway Branch Create Tasks window is automatically displayed once a Cableway element is created.\n\n\n\nNote\n:\nCableway Branch Create Tasks\nCableway Branch Create Tasks\nBranch Tasks"}
{"Headers": "Attributes Section", "Content": "Use to define the attributes of the cableway branch element.\n\nDescription\nEnter a description attribute for the cableway branch element.\nFunction\nEnter a function attribute for the cableway branch element.\nPurpose\nEnter a purpose attribute for the cableway branch element.\nUse Material\nSelect to use the cableway material along the entire cableway branch\nMaterial Type\nUse to route the cables correctly dependent upon the cableway type before the tray is dressed with material.\nUnset\nThe routing of the cables are not set or fixed.\nPerforated\nCables can be routed through the cableway tray from underneath.\nUnperforated\nCables cannot be routed through the cableway tray from underneath.\nUnset\nThe routing of the cables are not set or fixed.\nPerforated\nCables can be routed through the cableway tray from underneath.\nUnperforated\nCables cannot be routed through the cableway tray from underneath.\nBeta Angle\nEnter the angle for the cableway branch element, default is 0.00.\nUse Fixed Bends\nSelect to use fixed bends when routing the cables on the cableway branch.\nInside Radius\nDefines the bend applied to the cableway branch element, once it has been created and dressed, default is 0.0. The BRAD attribute is the radius of the RPATH.\nIf the cableway branch radius is changed, it is reflected on the points of the RPATH. When the justification is set and the cableway branch and radius are modified. The Fradius on the points of the RPATH change accordingly to the justification and direction of the bend and riser.\nOpen Direction\nEnter the direction of the open side of the cableway branch once it is dresses with material, default is U WRT/*.\nJustification\nThe cableway branch can be justified in both the horizontal and vertical planes, select the justification from the pull-down menu, default is Bottom - Center.\nIf the justification is modified after dressing, the material is aligned automatically with the volume. However some material can overlap and some gaps between cable trays can appear. Therefore the branch should be redressed after a change on justification.\nMax Cables\nDefine the maximum number of cables on the cableway branch.\nMinimum Layers\nDefine the minimum number of layers on the cableway branch, the default is 1.\nCable Layout\nDefine how the cables are routed on the cableway branch. The position of the first cable on the cableway is defined as listed below, further cables are routed away from it in the direction from Head to Tail.\nCable Excess\nDefine how much of an allowance for sagging (when the cable is supported in the cableway branch) is required, default is 0.\nMaximum Fill\nDefine the maximum fill level on the cableway branch (the software automatically calculates this value based on the horizontal fill (width of the tray) and the total width of the cables on the tray and all gaps included depending on the properties of the cable).\nCurrent Fill Level (%)\nDisplays the current fill level of the cableway branch element.\nAllowable Classes\nPositions multiple cable classes routed along a particular segment on a cableway branch. Segments can be added and/or removed.\n\nVolume\nDefines the volume size the cableway branch will occupy in the 3D model.\n\nShape\nDefines the shape of the volume in the 3D model, select Rectangular or Circular. Enter the cableway branch volume dimensions. A graphical representation of the dimensions can be viewed in the Cableway Branch Volume Dimensions window.\nClick show volume dimension sketch to display the Cableway Branch Volume Dimensions window.\n\nConnections\nUse the connections functionality to position and connect a cableway head and tail.\nDefines how the cableway branch head and tail are positioned and connected. By using the coordinates manually entered, an offset or by a location picked from the 3D view. These coordinates can then be locked.\n\nConnect From\nExplicit\nEast, North and Up - (default) positions the branch head using the coordinates manually entered, using an offset from the 3D view.\nHead of Cableway Branch\nPositions the branch head at the head of an existing cableway branch. When prompted, Pick CWBRAN in the 3D view at the position of the existing branch head.\nTail of Cableway Branch\nPositions the branch head at the tail of an existing cableway branch. When prompted, Pick CWBRAN in the 3D view at the position of the existing cableway branch tail.\nBranch Off\nPositions the branch head at a selected point on a existing branch.\nWhen prompted, Pick on the segment from which the branch should connect: to identify the segment.\nRoute Attachment Point\nPositions the branch head at the position of a selected route attachment point. When prompted Pick ATTA in the 3D view.\nJunction Box/Pull Pit\nPositions the branch head to a junction box or pull pit. When prompted Pick P Point of Junction Box or Pull Pit (Distance[0]) Snap: in the 3D view.\nNote:\nOnce the Create Cableway Branch link label is selected, the HCREF and TCREF attributes are set and the branch is created.\nPick Head Position\nWhen prompted, Pick to define position (Distance [0]) Snap: in the 3D view. Once selected, this will be used as the position for the new cableway branch head.\nTo lock the cableway branch head coordinates, click to check the Lock checkboxes.\nMoving the cableway branch a specified distance in a particular direction can be done by entering the required coordinate values and using the Lock checkboxes before creating the cableway branch.\nAlternatively, if the cableway branch has been created, select the branch and move it into the desired position using the Model Editor.\nCopy Tail Position\nThe coordinates of the tail are copied and these are populated in the window.\nExplicit\nEast, North and Up - (default) positions the branch head using the coordinates manually entered, using an offset from the 3D view.\nHead of Cableway Branch\nPositions the branch head at the head of an existing cableway branch. When prompted, Pick CWBRAN in the 3D view at the position of the existing branch head.\nTail of Cableway Branch\nPositions the branch head at the tail of an existing cableway branch. When prompted, Pick CWBRAN in the 3D view at the position of the existing cableway branch tail.\nBranch Off\nPositions the branch head at a selected point on a existing branch.\nWhen prompted, Pick on the segment from which the branch should connect: to identify the segment.\nRoute Attachment Point\nPositions the branch head at the position of a selected route attachment point. When prompted Pick ATTA in the 3D view.\nJunction Box/Pull Pit\nPositions the branch head to a junction box or pull pit. When prompted Pick P Point of Junction Box or Pull Pit (Distance[0]) Snap: in the 3D view.\n\nPick Head Position\nWhen prompted, Pick to define position (Distance [0]) Snap: in the 3D view. Once selected, this will be used as the position for the new cableway branch head.\n\nTo lock the cableway branch head coordinates, click to check the Lock checkboxes.\n\nMoving the cableway branch a specified distance in a particular direction can be done by entering the required coordinate values and using the Lock checkboxes before creating the cableway branch.\nAlternatively, if the cableway branch has been created, select the branch and move it into the desired position using the Model Editor.\nCopy Tail Position\nThe coordinates of the tail are copied and these are populated in the window.\nOffset\nUse to position the branch head explicitly, at the head/tail of the cableway branch, branch off or route attachment point using an offset.\n\nBranch Tail\nThe functionality available for selection from Branch Tail is identical to that previously described in Branch Head.\n\nCreate Orthogonal Route and Direction Sequence\nUse to constrain the cableway branch to an orthogonal route and define the direction that the route takes orthogonally.\nUpon creation, the cableway branch is displayed in the 3D view automatically routed along an orthogonal path connecting the head and tail positions.\nFor further information, refer to Cableway Branch, , and .\nUnset\nThe routing of the cables are not set or fixed.\nPerforated\nCables can be routed through the cableway tray from underneath.\nUnperforated\nCables cannot be routed through the cableway tray from underneath.\nExplicit\nEast, North and Up - (default) positions the branch head using the coordinates manually entered, using an offset from the 3D view.\nHead of Cableway Branch\nPositions the branch head at the head of an existing cableway branch. When prompted, Pick CWBRAN in the 3D view at the position of the existing branch head.\nTail of Cableway Branch\nPositions the branch head at the tail of an existing cableway branch. When prompted, Pick CWBRAN in the 3D view at the position of the existing cableway branch tail.\nBranch Off\nPositions the branch head at a selected point on a existing branch.\nWhen prompted, Pick on the segment from which the branch should connect: to identify the segment.\nRoute Attachment Point\nPositions the branch head at the position of a selected route attachment point. When prompted Pick ATTA in the 3D view.\nJunction Box/Pull Pit\nPositions the branch head to a junction box or pull pit. When prompted Pick P Point of Junction Box or Pull Pit (Distance[0]) Snap: in the 3D view.\nNote:\nOnce the Create Cableway Branch link label is selected, the HCREF and TCREF attributes are set and the branch is created.\nPick Head Position\nWhen prompted, Pick to define position (Distance [0]) Snap: in the 3D view. Once selected, this will be used as the position for the new cableway branch head.\nTo lock the cableway branch head coordinates, click to check the Lock checkboxes.\nMoving the cableway branch a specified distance in a particular direction can be done by entering the required coordinate values and using the Lock checkboxes before creating the cableway branch.\nAlternatively, if the cableway branch has been created, select the branch and move it into the desired position using the Model Editor.\nCopy Tail Position\nThe coordinates of the tail are copied and these are populated in the window.\nBottom - Center\nBottom - Left\nBottom - Right\nCenter - Center\nCenter Left\nCenter - Right\nTop - Center\nTop - Left\nTop - Right\nBottom - Center\nBottom - Center\nBottom - Left\nBottom - Left\nBottom - Right\nBottom - Right\nCenter - Center\nCenter - Center\nCenter Left\nCenter Left\nCenter - Right\nCenter - Right\nTop - Center\nTop - Center\nTop - Left\nTop - Left\nTop - Right\nTop - Right\nLeft\nLeft - Center\nCenter\nRight - Center\nRight\nUnset\nLeft\nLeft\nLeft - Center\nLeft - Center\nCenter\nCenter\nRight - Center\nRight - Center\nRight\nRight\nUnset\nUnset\nNote:\nThere are two types of inside/outside bends, fixed and variable. The fixed type will have different bend radius for an inside and outside bend. The variable type will have the same radius for both inside and outside bends.\nNote:\nIf a bend is selected that does not match the radius of any bend/riser in the catalog, the application searches for a bend/riser that is as close to the specified BRAD as possible. A Confirm window is displayed, click Yes to accept the nearest match or click No to ensure the branch is dressed with bends/risers that exactly match the BRAD.\nNote:\nOnce the Create Cableway Branch link label is selected, the HCREF and TCREF attributes are set and the branch is created.\nNote:\nIn the case of Branch Tail, the functionality available is Copy Head Position.\nNote:\nThe Direction Sequence and the Open Directory are compatible (for example - an open direction of U could be invalid if the Direction of Sequence was set to U-N-E or U-E-N).\n\n\n\nCableway Branch\nDescription\nFunction\nPurpose\nUse Material\nMaterial Type\nUnset\nPerforated\nUnperforated\nBeta Angle\nUse Fixed Bends\nInside Radius\nNote\n:\nNote\n:\nConfirm\nOpen Direction\nJustification\nMax Cables\nMinimum Layers\nCable Layout\nCable Excess\nMaximum Fill\nCurrent Fill Level (%)\nAllowable Classes\nVolume\nShape\nRectangular\nCircular\nCableway Branch Volume Dimensions\nCableway Branch Volume Dimensions\nConnections\nConnect From\nExplicit\nHead of Cableway Branch\nTail of Cableway Branch\nPick CWBRAN\nBranch Off\nPick on the segment from which the branch should connect:\nRoute Attachment Point\nPick ATTA\nJunction Box/Pull Pit\nPick P Point of Junction Box or Pull Pit (Distance[0]) Snap:\nNote\n:\nick Head Position\nPick to define position (Distance [0]) Snap:\nLock\nCopy Tail Position\nNote\n:\nOffset\nBranch Tail\nCreate Orthogonal Route and Direction Sequence\nNote\n:\nCableway Branch\n\n"}
{"Headers": "Cabletray Volume", "Content": "Use to select an existing cabletray and convert into volumes with dimensions extracted from the tray members. The zone where to create the new elements can also be selected and cableway branch attributes can be also set. By default the Cable Tray List tab is selected.\n\n\n\nCable Tray List"}
{"Headers": "Cable Tray List", "Content": "The Cable Tray Volumes window lists the cable trays from the current zone and also displays the Head Connection and Tail Connection of each branch.\n\nSelect Level\nUse to switch between World, Site or Zone levels in order to load trays for the selected level.\nRefresh Grid and Track CE are common to both the Cable Tray List and Cableway Branch List tabs.\nRefresh Grid\nClick Refresh Grid to re-display either grid to reflect any changes made that are not updated automatically.\nTrack CE\nTracks the current element in the Model Explorer.\nRefresh Grid\nClick Refresh Grid to re-display either grid to reflect any changes made that are not updated automatically.\nTrack CE\nTracks the current element in the Model Explorer.\nRight click in the grid to display the pop up menu.\nNavigate\nNavigate to the element in the Model Explorer.\nHighlight\nHighlights the element in the graphical view.\nUnhighlight\nRemoves the highlight from the element in the graphical view.\nExport to Excel\nDisplays a Save As window to navigate to a location and name the exported Excel file.\nPrint Preview\nDisplays the Print Preview utility.\nNavigate\nNavigate to the element in the Model Explorer.\nHighlight\nHighlights the element in the graphical view.\nUnhighlight\nRemoves the highlight from the element in the graphical view.\nExport to Excel\nDisplays a Save As window to navigate to a location and name the exported Excel file.\nPrint Preview\nDisplays the Print Preview utility.\nSet Cableway Branch Att\nUse to set cableway branch attributes prior to creating the volumes:\nDescription\nEnter a description for the cableway branch element.\nFunction\nEnter a function for the cableway branch element.\nPurpose\nEnter a purpose for the cableway branch element.\nCable Excess\nDefine how much of an allowance for sagging (when the cable is supported in the cableway branch) is required, default is 0.00.\nMaximum Fill (%)\nDefine the maximum fill level on the cableway branch (the software automatically calculates this value based on the cross sectional area).\nHeight\nEnter a height for the cableway branch element.\nBend Radius\nDefines the bend radius, this can be set to Auto or Manual:\nAuto\nThe bend radius for each BEND/ELBOW is automatically calculated and assigned to the corresponding POINTR element.\nManual\nEnter a bend radius of all POINTR elements, select if it is applied to the inner circle or centreline radius along with the units of measure.\nAuto\nThe bend radius for each BEND/ELBOW is automatically calculated and assigned to the corresponding POINTR element.\nManual\nEnter a bend radius of all POINTR elements, select if it is applied to the inner circle or centreline radius along with the units of measure.\nInterference\nThe functionality available is identical to that described in cableway.\nReset Fields\nUse to reset all fields in Set Cableway Branch Att to the default values.\nStorage Areas\nUse to select the new CWAY/CWBRANCH elements are to be stored.\nLoad Zones\nUse to populate a list of the available zones for the current element in the hierarchy. If a zone is not selected to create elements, the elements will be created in the same zone as the selected cabletray.\nShow Associations Manager\nTo create the volumes, an association group with the purpose set to TBAS dedicated to store associations between old cabletray elements and new cabletray elements must exist.\nIf the association group does not exist, an error message is displayed informing the required association group needs creating.\nWhen the association group exists a Confirm window is displayed, confirm the cableway volumes for the selected cabletray branches are to be created.\nVolumes for the tray have been created successfully.\nVolumes for the tray are not present.\n\nVolumes for the tray have been created successfully.\n\nVolumes for the tray are not present.\nRefresh Grid\nClick Refresh Grid to re-display either grid to reflect any changes made that are not updated automatically.\nTrack CE\nTracks the current element in the Model Explorer.\nNavigate\nNavigate to the element in the Model Explorer.\nHighlight\nHighlights the element in the graphical view.\nUnhighlight\nRemoves the highlight from the element in the graphical view.\nExport to Excel\nDisplays a Save As window to navigate to a location and name the exported Excel file.\nPrint Preview\nDisplays the Print Preview utility.\nAuto\nThe bend radius for each BEND/ELBOW is automatically calculated and assigned to the corresponding POINTR element.\nManual\nEnter a bend radius of all POINTR elements, select if it is applied to the inner circle or centreline radius along with the units of measure.\nVolumes for the tray have been created successfully.\nVolumes for the tray are not present.\n\n\n\nCable Tray Volumes\nSelect Level\nRefresh Grid\nTrack CE\nCable Tray List\nCableway Branch List\nRefresh Grid\nRefresh Grid\nTrack CE\nNavigate\nHighlight\nUnhighlight\nExport to Excel\nSave As\nPrint Preview\nSet Cableway Branch Att\nDescription\nFunction\nPurpose\nCable Excess\nMaximum Fill (%)\nHeight\nBend Radius\nAuto\nManual\nAuto\nManual\nInterference\nReset Fields\nSet Cableway Branch Att\nStorage Areas\nCWAY/CWBRANCH\nLoad Zones\nShow Associations Manager\nConfirm"}
{"Headers": "Cableway Branch List", "Content": "Once the cabletrays have been converted into volumes and displayed in the 3D view, the Cable Branch List tab is populated with name, associated-cabletray, head-connection and tail-connection of these converted cableways.\n\nRight-click in the grid to display a pop-up menu.\nNavigate\nNavigates to the element in the Model Explorer.\nModify Attributes\nDisplays the Cableway Branch Modify Tasks window.\nHighlight\nHighlights the element in the graphical view.\nUnhighlight\nRemoves the highlight from the element in the graphical view.\nExport to Excel\nDisplays a Save As window, navigate to a location and name the exported Excel file.\nPrint Preview\nDisplays the Print Preview utility.\nNavigate\nNavigates to the element in the Model Explorer.\nModify Attributes\nDisplays the Cableway Branch Modify Tasks window.\nHighlight\nHighlights the element in the graphical view.\nUnhighlight\nRemoves the highlight from the element in the graphical view.\nExport to Excel\nDisplays a Save As window, navigate to a location and name the exported Excel file.\nPrint Preview\nDisplays the Print Preview utility.\nRefresh Grid\nUse Refresh Grid to refresh either grid to reflect any changes that re not updated automatically.\nTrack CE\nUse Track CE to track the currently selected element in the Model Explorer.\nFor further information, refer to Branch, Create Route Attachment Points, and .\nNavigate\nNavigates to the element in the Model Explorer.\nModify Attributes\nDisplays the Cableway Branch Modify Tasks window.\nHighlight\nHighlights the element in the graphical view.\nUnhighlight\nRemoves the highlight from the element in the graphical view.\nExport to Excel\nDisplays a Save As window, navigate to a location and name the exported Excel file.\nPrint Preview\nDisplays the Print Preview utility.\nExtend/Connect Branch Head\nExtend/Connect Branch Tail\nConnect Branches\nDisconnect Branches\nShow/Hide Unconnected\nExtend/Connect Branch Head\nExtend/Connect Branch Head\nExtend/Connect Branch Tail\nExtend/Connect Branch Tail\nConnect Branches\nConnect Branches\nDisconnect Branches\nDisconnect Branches\nShow/Hide Unconnected\nShow/Hide Unconnected\nModify Branch Attributes\nCreate/Modify Route Points\nCreate/Modify Route Attachment Points\nCreate/Modify Route Nodes.\nModify Branch Attributes\nModify Branch Attributes\nCreate/Modify Route Points\nCreate/Modify Route Points\nCreate/Modify Route Attachment Points\nCreate/Modify Route Attachment Points\nCreate/Modify Route Nodes.\nCreate/Modify Route Nodes.\nDelete Cableway Branch\nDelete Owning Cableway.\nDelete Cableway Branch\nDelete Cableway Branch\nDelete Owning Cableway.\nDelete Owning Cableway.\n\n\n\nExtend/Connect Branch Head\nExtend/Connect Branch Tail\nConnect Branches\nDisconnect Branches\nShow/Hide Unconnected\nModify Branch Attributes\nCreate/Modify Route Points\nCreate/Modify Route Attachment Points\nCreate/Modify Route Nodes\nDelete Cableway Branch\nDelete Owning Cableway\nBranch\nCreate Route Attachment Points\nCable Branch List\nNavigate\nModify Attributes\nHighlight\nUnhighlight\nExport to Excel\nSave As\nPrint Preview\nRefresh Grid\nRefresh Grid\nTrack CE\nExtend/Connect Branch Head\nExtend/Connect Branch Tail\nConnect Branches\nDisconnect Branches\nShow/Hide Unconnected\nModify Branch Attributes\nCreate/Modify Route Points\nCreate/Modify Route Attachment Points\nCreate/Modify Route Nodes\nDelete Cableway Branch\nDelete Owning Cableway\nBranch\nCreate Route Attachment Points\n"}
{"Headers": "Extend/Connect Branch Head", "Content": "Connects the Head of the selected Cableway branch to another branch. When clicked, a prompt to pick on the branch segment where the branch head should connect to is displayed. Once picked it moves the head position of the selected branch to the picked position on the picked branch. A RATTA will automatically be created where the branches meet.\n\n\n\nbranch segment"}
{"Headers": "Extend/Connect Branch Tail", "Content": "Connects the Tail of the selected Cableway branch to another branch. When clicked, a prompt to pick on the branch segment where the branch tail should connect to is displayed. Once picked it moves the tail position of the selected branch to the picked position on the picked branch. A RATTA will automatically be created where the branches meet.\n\n\n\nbranch segment"}
{"Headers": "Connect Branches", "Content": "Connects two cableway branches. When clicked a prompt to Pick first branch and then second branch is displayed. Clicking Yes on the confirm dialog window connects the two branches. A RATTA will automatically be created where the branches meet.\n\n\n\nYes"}
{"Headers": "Disconnect Branches", "Content": "To disconnect the cableway branch from its connection points, make sure that the cableway branch to be disconnected is highlighted as the CE in the Model Explorer.\nA Confirm window is displayed, prompting Do you want to disconnect. Click Yes to disconnect the selected cableway branch, or click No to close the window and discard any inputs.\nNote:\nDisconnecting cableway branches means that cables will not be routed between the two branches.\n\n\n\nDo you want to disconnect\nYes\nNo\nNote\n:"}
{"Headers": "Show/Hide Unconnected", "Content": "Displays, in the graphical view, Unconnected labels on branch ends with unset connection references. When clicked the link changes to Hide Unconnected, which when clicked removes the Unconnected labels from the graphical view.\n\n\n\nUnconnected\nHide Unconnected\nUnconnected"}
{"Headers": "Modify Branch Attributes", "Content": "Displays the Cableway Branch Modify Tasks window.\n\n\n\nCableway Branch Modify Tasks"}
{"Headers": "Create/Modify Route Points", "Content": "Displays the Define Path/Route Tasks window with mode set to Creation as default.\n\n\n\nDefine Path/Route Tasks\nCreation"}
{"Headers": "Create/Modify Route Attachment Points", "Content": "Displays the Route Attachment Points Create Tasks window with mode set to Creation as default.\n\n\n\nRoute Attachment Points Create Tasks\nCreation"}
{"Headers": "Create/Modify Route Nodes", "Content": "Displays the Route Node Create Tasks form with mode set to Creation as default.\n\n\n\nRoute Node Create Tasks\nCreation"}
{"Headers": "Delete Cableway Branch", "Content": "Deletes the selected cableway branch.\n\n\n"}
{"Headers": "Delete Owning Cableway", "Content": "Deletes the owning cableway of selected branch and all its members.\n\n\n"}
{"Headers": "Branch Tasks", "Content": "Defines the path/routing, route node and attachment point creation and branch options for the cableway branch.\n\n\n\n"}
{"Headers": "Define the Path/Route", "Content": "Creates route points and positions these points on a cableway branch. A route point is a reference point inserted at a defined position on the cableway branch and provides a reference for routing the branch and for adding cable tray material.\n\nThe Define Path / Route Task window can be used as a dual purpose window, which allows the Creation of a new route point or the Modification of an existing route point.\nCableway Branch\nThe owning cableway branch element currently selected in the design database hierarchy is automatically displayed as the cableway branch.\nCurrent Element\nThe first automatically created POINT element of the RPATH element is displayed as the current element.\nDirection from Current Point\nDisplays the direction from the current route point to the next route point, default is U WRT /*.\nDistance from the Current Point\nDisplays the distance from the current route point to the next route point, default is 0mm.\nRoute Point Position\nUse to explicitly position a route point by manually entering coordinates, using an offset, by the selection of a position in the 3D view or by copying the position of the previous or next route point.\nExplicit\nExplicitly position the route point, input the coordinates:\nOffset\nUse to position the route point using an offset, default is 0mm.\n\nPick Position\nTo pick a position on the cableway branch in the 3D view, select Pick Position, a prompt to Pick to define position (Snap) Snap: is displayed.\nCopy Previous\nTo copy the position of the previous route point, select Copy Previous, the position of the previous route point is copied.\nCopy Next\nTo copy the position of the next route point, select Copy Next, the position of the next route point is copied.\nFillet Radius\nAfter the positioning of the route points for the cableway branch, define if a right angle bend in the cableway branch is replaced with a curve bend, input a Fillet Radius.\nInside Radius\nThe inside radius specified in the Attributes pane is displayed.\nSelect Route Point\nAll of the created route points are displayed, click to highlight a route point which displays the position in the 3D view.\n\nMode\nUse to define if the window is to be used to create a new route point or to modify an existing route point.\nBackwards\nUse to reverse the order of route points on the selected cableway branch. The route points are also reversed and displayed in the Select Route Point list. Click to select the Backwards checkbox.\nMark Route Points\nUse to display route points on the selected cableway branch the 3D view, click to select the Mark Route Points checkbox.\nList Associated Cables\nUse to display associated cables, click List Associated Cables to display the List of Cables window, listing all the associated cables.\nThe new route point is created and displayed in the Model Explorer and displayed in the Select Route Point part of the Define Path / Route Task window.\nTo return to the Define Path / Route Task window, select Back to Branch Task.\nE0 N0 U0 - (default) positions the branch head at the coordinates 0,0,0 (origin).\nE0 N0 U0 - (default) positions the branch head at the coordinates 0,0,0 (origin).\nE0 N0 U0 - (default) positions the branch head at the coordinates 0,0,0 (origin).\n\n\n\nDefine Path / Route Task\nCreation\nModification\nCableway Branch\nCurrent Element\nDirection from Current Point\nDistance from the Current Point\nRoute Point Position\n3D view\nExplicit\nOffset\nPick Position\n3D view\nPick Position\nPick to define position (Snap) Snap:\nCopy Previous\nCopy Previous\nCopy Next\nCopy Next\nFillet Radius\nFillet Radius\nInside Radius\nAttributes\nSelect Route Point\n3D view\nMode\nBackwards\nBackwards\nMark Route Points\n3D view\nMark Route Points\nList Associated Cables\nList Associated Cables\nList of Cables\nSelect Route Point\nDefine Path / Route Task\nDefine Path / Route Task\nBack to Branch Task"}
{"Headers": "Create Route Node", "Content": "Creates and positions a route node on a selected cableway branch. A route node is a multi-purpose reference point created on the cableway branch.\n\nThe Route Node Create Tasks window can be used as an dual purpose window, which allows the Creation of a new route node or the Modification of an existing route node.\nCableway Branch\nThe currently selected cableway branch in the model explorer is displayed.\nCurrent Element\nThe currently selected element in the model explorer is displayed.\nRoute Node Name\nEnter a name for the Route Node Name element or the name can be automatically generated using the Autonaming icon to the right of the text box.\nGeneral Attributes\nDefines the description, function and purpose for the route node.\nRoute Node Type\nUse to select the route node type:\n\nTakeoff - here\nDefines the node from which the cable can leave or enter the cableway.\nGap\nDefines the node which forces a gap to be left between the cable tray material and is positioned at the centre point of the gap. Gap (YOffset), defines the gap size default is 0mm.\nOffset\nUse this node to position transit glands and fittings.\nPenetration\nUse this node to hold references of penetrations.\nReport\nUse this node to report information (such as passing cables) from any position along the branch.\nPositioning\nDefines the position of the route node on the cableway branch.\nReference Point\nSelect a reference point from the drop-down menu (the Offset Distance is automatically populated) or select Pick, a prompt to Pick on the segment which RNODE should be placed is displayed.\nOffset Distance\nInput an offset distance in the Offset Distance box or select Pick a prompt to Pick to define position (Snap) Snap is displayed.\nMove Distance\nTo increase or decrease the Offset, select the appropriate arrow either side of the Move Offset box.\nProportional Distance\nEnter a proportional Distance.\nX Offset\nEnter an X axis offset.\nZ Offset\nEnter an Z axis offset.\nGap (Y Offset)\nReserves a space between cable trays. Enter the required distance.\nProportional Distance\nEnter a proportional Distance.\nX Offset\nEnter an X axis offset.\nZ Offset\nEnter an Z axis offset.\nGap (Y Offset)\nReserves a space between cable trays. Enter the required distance.\nReferences\nThe References part of the Route Node Create Tasks window defines.\nConnection\nAllows a Route Node to be connected to a Control Node. Clicking Pick displays the Select CNODE window.\nSpecification\nEnter a specification or select Choose to display the Choose Route Node window, from which a specification can be selected.\nConnection\nAllows a Route Node to be connected to a Control Node. Clicking Pick displays the Select CNODE window.\nSpecification\nEnter a specification or select Choose to display the Choose Route Node window, from which a specification can be selected.\nSelect the Mark Route Points checkbox to display the route point labels on the 3D view.\nList Associated Cables\nTo display associated cables, select List Associated Cables to display the List of Cables window, listing all the associated cables.\nThe new route node is a created and displayed the Model Explorer. The position of the created routed node on the cableway branch is shown in the 3D view.\nMark Route Nodes\nDisplays the route nodes on a cableway network and identifies their position in the 3D view.\n\nSelect which set of route nodes to display in the Mark Route Nodes window.\nMark Selected\nUse to select individual route nodes.\nUnmark Selected\nUse to unmark selected individual route nodes.\nMark All\nUse to select all route nodes in the list.\nUnmark All\nUse to de-select all the route nodes in the list.\nThe list of Route Nodes displayed is divided into the following columns:\nName\nDisplays the name of the route node.\nBranch name\nDisplays the cableway branch name.\nWorld position\nDisplays the route node's position with respect to World.\nType\nDisplays the type of route node.\nName\nDisplays the name of the route node.\nBranch name\nDisplays the cableway branch name.\nWorld position\nDisplays the route node's position with respect to World.\nType\nDisplays the type of route node.\nProportional Distance\nEnter a proportional Distance.\nX Offset\nEnter an X axis offset.\nZ Offset\nEnter an Z axis offset.\nGap (Y Offset)\nReserves a space between cable trays. Enter the required distance.\nConnection\nAllows a Route Node to be connected to a Control Node. Clicking Pick displays the Select CNODE window.\nSpecification\nEnter a specification or select Choose to display the Choose Route Node window, from which a specification can be selected.\nName\nDisplays the name of the route node.\nBranch name\nDisplays the cableway branch name.\nWorld position\nDisplays the route node's position with respect to World.\nType\nDisplays the type of route node.\nNote:\nWhen using the Move Offset and Proportional Distance functionality on Cableways with bends, the offset is measured from the edge of the bend rather than the Reference Point.\n\n\n\nRoute Node Create Tasks\nCreation\nModification\nCableway Branch\nCurrent Element\nRoute Node Name\nAutonaming\nGeneral Attributes\nRoute Node Type\nTakeoff - here\nGap\nOffset\nPenetration\nReport\nPositioning\nReference Point\nOffset Distance\nPick,\nPick on the segment which RNODE should be placed\nOffset Distance\nOffset Distance\nPick\nPick to define position (Snap) Snap\nMove Distance\nMove\nOffset\nNote\n:\nProportional Distance\nX Offset\nZ Offset\nGap (Y Offset)\nReferences\nReferences\nRoute Node Create Tasks\nConnection\nPick\nSelect CNODE\nSpecification\nChoose\nChoose Route Node\nMark Route Points\nList Associated Cables\nList Associated Cables\nList of Cables\nMark Route Nodes\nMark Route Nodes\nMark Selected\nUnmark Selected\nMark All\nUnmark All"}
{"Headers": "Create Route Attachment Points", "Content": "A routing connection attachment point (RATTA) is a reference point used to create a connection on the cableway at a position different from the Routing Branch Head or Routing Branch Tail which allows cables to join the cableway at this point when performing cable routing tasks.\n\nThe Route Attachments Points Create Tasks window is a dual purpose window, which allows the Creation of a new route attachment point or the Modification of an existing route attachment point.\nCableway Branch\nThe currently selected cableway branch in the model explorer is displayed.\nCurrent Element\nThe currently selected element in the model explorer is displayed.\nPositioning\nUse to position the route node to be defined on the cableway branch.\nReference Point\nSelect a reference point from the drop-down menu (the Offset Distance is automatically populated) or select Pick a prompt to Pick on the segment which RNODE should be placed is displayed.\nOffset Distance\nEnter an offset distance in the Offset Distance box or select Pick a prompt to Pick to define position (Snap) Snap is displayed.\nMove Distance\nUse to increase or decrease the Offset, select the appropriate arrow either side of the Move Offset box.\nMark Route Points\nSelect the Mark Route Points checkbox to display the route point labels on the 3D view.\nList Associated Cables\nUse to display associated cables, click List Associated Cables to display the List of Cables window, listing all the associated cables.\nThe new route attachment point is a created and displayed the Model Explorer. The position of the created routed attachment point on the cableway branch is shown in the 3D view.\nA cableway branch can be created and connected to another branch at the attachment point.\nNote:\nWhen using the Move Offset and Proportional Distance functionality on Cableways with bends, the offset is measured from the edge of the bend rather than the Reference Point.\n\n\n\nRoute Attachments Points Create Tasks\nCreation\nModification\nCableway Branch\nCurrent Element\nPositioning\nReference Point\nOffset Distance\nPick\nPick on the segment which RNODE should be placed\nOffset Distance\nOffset Distance\nPick\nPick to define position (Snap) Snap\nMove Distance\nMove Offset\nNote\n:\nMark Route Points\nMark Route Points\nList Associated Cables\nList Associated Cables\nList of Cables"}
{"Headers": "Delete Branch", "Content": "Use to delete a branch or branches, make sure that the branch to be deleted is highlighted as the CE in the Model Explorer.\nA Confirm window is displayed, prompting Are you sure to delete Cableway Branch. Click Yes to delete the selected cableway branch, or click No to close the window and discard any inputs.\nNote:\nIf the cableway branch contains cables, the Confirm window displayed, prompts There are cables routed on the cableway Still delete. When deleting a branch, any cables routed on the branch will have their status changed to un-routed.\n\n\n\nCE\nModel Explorer\nConfirm\nAre you sure to delete Cableway Branch\nYes\nNo\nNote\n:\nThere are cables routed on the cableway Still delete"}
{"Headers": "Disconnect Branch", "Content": "Use to disconnect the cableway branch from its connection points, make sure that the cableway branch to be disconnected is highlighted as the CE in the Model Explorer.\nA Confirm window is displayed, prompting Do you want to disconnect. Click Yes to disconnect the selected cableway branch or click No to close the window and discard any inputs.\nNote:\nDisconnecting cableway branches means that cables will not be routed between the two branches.\n\n\n\nCE\nModel Explorer\nConfirm\nDo you want to disconnect\nYes\nNo\nNote\n:"}
{"Headers": "Check Connections", "Content": "Use to check the cableway branch connections.\n\nSelect which set of connections to display in the Cableway Branch Connections window.\nCurrent Branch\nPopulates Cableway Branch Connections window with all the connections in the currently selected branch.\nCurrent Cableway\nPopulates Cableway Branch Connections window with all the connections in the currently selected cableway.\nCurrent Zone\nPopulates Cableway Branch Connections window with all the connections in the currently selected zone.\nCurrent Site\nPopulates Cableway Branch Connections window with all the connections in the currently selected site.\nTag\nUse to highlight the selected, connected, unconnected connections, connections that have errors, all of the connections, remove all of the connections or refresh the connections in the 3D view.\nBranch Connection\nLists all the branch connections for the selected option which are displayed in the Cableway Branch Connections window.\nConnected To\nStates if the branch connection is connected to another branch.\nStatus\nThe status (OK or Error) of the branch connection.\nMessages\nDisplays any relevant messages in the Cableway Branch Connections window.\nIf no connection errors are found, green ticks will be displayed in the Cableway Branch Connections window. A message Connections correct at this point is also displayed.\nIf connection errors are found, red balls will be displayed in the Cableway Branch Connection window. A message Error in connections at this point is also displayed. The connection errors will also be highlighted in red in the 3D view.\n\n\n\nCableway Branch Connections\nCurrent Branch\nCableway Branch Connections\nCurrent Cableway\nCableway Branch Connections\nCurrent Zone\nCableway Branch Connections\nCurrent Site\nCableway Branch Connections\nTag\nBranch Connection\nCableway Branch Connections\nConnected To\nStatus\nMessages\nCableway Branch Connections\nCableway Branch Connections\nConnections correct at this point\nCableway Branch Connection\nError in connections at this point"}
{"Headers": "Dressing", "Content": "Use to dress the cableway branch select Dressing from the Branch Tasks window.\nFor further information, refer to Branch Dressing, Cableway, Cableway, Connect Branch, , Hierarchy, and .\n\n\n\nBranch Dressing\nCableway\nCableway\nConnect Branch\nHierarchy\nDressing\nBranch Tasks\nBranch Dressing\nCableway\nCableway\nConnect Branch\n\nHierarchy\n"}
{"Headers": "Pull Pit Branch", "Content": "Use the functionality to modify the currently selected Pull Pit Branch element.\n\nThe functionality is identical to that already described in Modify PullPit Branch.\n\n\n"}
{"Headers": "Create CWAY in this Zone", "Content": "The currently selected zone in the Model Explorer is identified.\n\n\n"}
{"Headers": "Cableway IClass", "Content": "Use to specify the IClass of the newly created cableway branches (CWBRAN), (individual or multiple branches can be selected).\n\nCableway Branches\nNo\nCable number.\nName\nDefault cable name.\nClass\nAs newly created, the default is blank.\nRule\nAs newly created, the default is blank.\nRow\nLocation in the cable group for example six cables (two rows and three columns).\nColumn\nLocation in the cable group for example six cables (two rows and three columns).\nNo\nCable number.\nName\nDefault cable name.\nClass\nAs newly created, the default is blank.\nRule\nAs newly created, the default is blank.\nRow\nLocation in the cable group for example six cables (two rows and three columns).\n\nColumn\nLocation in the cable group for example six cables (two rows and three columns).\nInterference Class\nCable Route Rule\nUse to specify the rule to be used to control the type of cable that can be routed along the cableway branch.\nStandard iclass\nUse to specify the iclass for the selected cable(s), click Load to load the interference values from a database or select from the menu:\nPOWER\nCOMM\nSIGNAL\nCONTROL\nWIRE\nNote:\nDefault is unset.\nCable Route Rule\nUse to specify the rule to be used to control the type of cable that can be routed along the cableway branch.\nStandard iclass\nUse to specify the iclass for the selected cable(s), click Load to load the interference values from a database or select from the menu:\nFor further information, refer to Cable Junction Boxes, , , Junction Node, Pull Node, and Pull Pits.\nNo\nCable number.\nName\nDefault cable name.\nClass\nAs newly created, the default is blank.\nRule\nAs newly created, the default is blank.\nRow\nLocation in the cable group for example six cables (two rows and three columns).\nColumn\nLocation in the cable group for example six cables (two rows and three columns).\nCable Route Rule\nUse to specify the rule to be used to control the type of cable that can be routed along the cableway branch.\nStandard iclass\nUse to specify the iclass for the selected cable(s), click Load to load the interference values from a database or select from the menu:\nPOWER\nCOMM\nSIGNAL\nCONTROL\nWIRE\nNote:\nDefault is unset.\nPOWER\nCOMM\nSIGNAL\nCONTROL\nWIRE\nPOWER\nPOWER\nCOMM\nCOMM\nSIGNAL\nSIGNAL\nCONTROL\nCONTROL\nWIRE\nWIRE\nNote:\nDefault is unset.\n\n\n\nCable Junction Boxes\nJunction Node\nPull Node\nPull Pits\nCableway Branches\nNo\nName\nClass\nRule\nRow\nColumn\nInterference Class\nCable Route Rule\nStandard iclass\nNote\n:\nCable Junction Boxes\n\n\nJunction Node\nPull Node\nPull Pits"}
{"Headers": "Create Route Elements", "Content": "Use to create control, multiple route, pull pit and junction nodes.\n\n\n"}
{"Headers": "Control Node", "Content": "Use the functionality to modify the currently selected control node element.\n\nThe functionality is identical to that already described in Create Control Node.\n\n\n"}
{"Headers": "Multiple Route Nodes", "Content": "Use the functionality to modify the route nodes based on branches/individual nodes selected.\n\n\n\n"}
{"Headers": "Pull Node", "Content": "Use the functionality to modify the currently selected pull node element. The functionality is identical to that described in Create a Pull Node with the following exception.\n\nThe Connect Cable Way Branches pane is populated with all the cableway branches connected to the currently selected pull node.\nConnect Graphical Selection\nConnects the currently selected cableway branch in the 3D view to the pull node.\nDisconnect Graphical Selection\nDisconnects the currently selected cableway branch in the 3D view from the pull node.\nDisconnect List Selection\nDisconnects the currently selected cableway branch in the list from the pull node.\nConnect Graphical Selection\nConnects the currently selected cableway branch in the 3D view to the pull node.\nDisconnect Graphical Selection\nDisconnects the currently selected cableway branch in the 3D view from the pull node.\nDisconnect List Selection\nDisconnects the currently selected cableway branch in the list from the pull node.\nConnect Graphical Selection\nConnects the currently selected cableway branch in the 3D view to the pull node.\nDisconnect Graphical Selection\nDisconnects the currently selected cableway branch in the 3D view from the pull node.\nDisconnect List Selection\nDisconnects the currently selected cableway branch in the list from the pull node.\nNote:\nA pull node can have as many connections as required or a single cable way branch can be connected to a single pull node.\n\n\n\nCreate a Pull Node\nConnect Cable Way Branches\nNote\n:\nConnect Graphical Selection\nDisconnect Graphical Selection\nDisconnect List Selection"}
{"Headers": "Junction Node", "Content": "Use the functionality to modify the currently selected junction node element. The functionality is identical to that described in Create a Junction Node with the following exception.\nThe Connect Cable Way Branches pane is populated with all the cableway branches connected to the currently selected junction node.\n\nConnect Graphical Selection\nConnects the currently selected cableway branch in the 3D view to the junction node.\nDisconnect Graphical Selection\nDisconnects the currently selected cableway branch in the 3D view from the junction node.\nDisconnect List Selection\nDisconnects the currently selected cableway branch in the list from the junction node.\nConnect Graphical Selection\nConnects the currently selected cableway branch in the 3D view to the junction node.\nDisconnect Graphical Selection\nDisconnects the currently selected cableway branch in the 3D view from the junction node.\nDisconnect List Selection\nDisconnects the currently selected cableway branch in the list from the junction node.\nConnect Graphical Selection\nConnects the currently selected cableway branch in the 3D view to the junction node.\nDisconnect Graphical Selection\nDisconnects the currently selected cableway branch in the 3D view from the junction node.\nDisconnect List Selection\nDisconnects the currently selected cableway branch in the list from the junction node.\nNote:\nA junction node can have as many connections as required or a single cable way branch can be connected to a single junction node.\n\n\n\nCreate a Junction Node\nConnect Cable Way Branches\nNote\n:\nConnect Graphical Selection\nDisconnect Graphical Selection\nDisconnect List Selection"}
{"Headers": "Create Cableway Material", "Content": "All create material windows, are dual purpose windows to create a new cable tray material element (by default) or modify the attributes of an existing cable tray material element.\n\n\n"}
{"Headers": "Material", "Content": "Use to set the administrative attributes and dimensions which will create cable tray material along the entire selected cableway branch. The material main element must be created first.\n\nCableway\nThe currently selected cableway element in the model explorer is displayed.\nCurrent Branch\nThe owning cableway branch element is displayed.\nMaterial Name\nEnter a name for the Material Name element or the name can be automatically generated using the Autonaming icon to the right of the text box.\nAttributes\nUse to define the description, function and purpose attributes for the new material element.\nDescription\nEnter a description attribute for the material element.\nFunction\nEnter a function attribute for the material element.\nPurpose\nEnter a purpose attribute for the material element.\nFirst Gap\nDefine the size of the gap before every material component, except where there are two adjoining straights.\nIntermediate Gap\nDefines the gap distance between all adjoining straights.\nLast Gap\nDefines the size of the gap after every material component except where there are two adjoining straights.\nTier Heights\nDefine the tier height(s).\nWidth/Height\nBy default the Width and Height are populated with the default cableway width and height. Different width and height dimensions can be entered if required.\nList Associated Cables\nUse to display associated cables, click List Associated Cables to display the List of Cables window, listing all the associated cables.\nOnce created the material element is displayed in the 3D view and the Modify Material window is displayed.\nNote:\nMake sure that the required cableway branch element is selected as the CE in the design hierarchy.\nNote:\nOnly one material main element (CTMRL) can be created for a cableway branch element (CWBRAN).\n\n\n\nNote\n:\nCE\nNote\n:\nCableway\nCurrent Branch\nMaterial Name\nAutonaming\nAttributes\nDescription\nFunction\nPurpose\nFirst Gap\nIntermediate Gap\nLast Gap\nTier Heights\nWidth/Height\nWidth\nHeight\nList Associated Cables\nList Associated Cables\nModify Material"}
{"Headers": "Create Cable Tray Material Element", "Content": "Cable tray material elements (a template) are single pieces of material suitable for use with cable trays.\n\nIt is usual to build up the cabling design by adding material elements sequentially, starting at any point and positioning and orientating each material element as they proceed.\nCE\nSelects the currently selected element in the model explorer.\nSelect Element\nBy default, the straight element is displayed, depending on the element selected dictates which window is displayed. For example the selection of the Reducer element results in the Create Reducer window being displayed. The input required varies depending upon the material, the information can be applied to the same processes that are used to create all types of cable tray material elements.\nCress Backwards\nSpecify in which direction the material elements are added to the cableway branch, select Dress Backwards to reverse the direction.\nReference Point\nUse to position the origin of the material elements, select the required reference point or select Pick, a prompt to Pick on the segment which CTSTRA should be placed: is displayed. In both cases the Along Route (Zdis) field is automatically populated.\nOffsets\nPositions the material element relative to its reference point.\n\nAlong Route (Zdis)\nPositions the material element at an offset along the cableway route.\nPick Position\nSelect Pick Position, a prompt to Pick define position (Snap) Snap: is displayed to position the material element at the offset.\nAlign with gridline\nSelect Align with gridline, a prompt to Pick Grid to define position: is displayed to align the picked point with a gridline.\nMove Offset\nEnter distance to move the offset, to move the offset by this distance, press the appropriate arrow key.\nGap\nPositions the material element at an offset to the gap left between the cableway materials.\nProportion (Pkdis)\nPositions the material element at an proportional offset along the cableway.\nHorizontal (Xoff)\nPositions the material element at an horizontal offset along the cableway.\nVertical (Zoff)\nPositions the material element at an vertical offset along the cable way.\nAngle Attributes\nDefines the angle attributes for the material element.\n\nBeta Angle (Bang)\nEnter the orientation of the material element about its neutral axis in terms of an angular clockwise rotation, default is 0.\nAs the straight element is selected, Angle, Radius and Bend Type are unavailable.\nDimensions\nUse to view and input the material elements dimensions, some will be automatically populated by the cabling specification.\n\nTemplates\nUse to select a template for the material element and display the element in the 3D view.\n\nTemplate Zone\nSelect the zone in which the template resides from the drop-down menu.\nSelect Type\nSelect the template type from the drop-down menu.\nUse Templates\nSelect Use Templates to use the selected template for the cable tray material element.\nDisplay Preliminary Dressing\nShows any Preliminary Dressing of the cableway branch in the main 3D view. It is selected by default.\nMode\nAllows options of Creation or Modification to be selected. After creating a material element, selecting the Modification button displays the corresponding Modify window.\nFor further information, refer to Modify Material.\n\n\n\nModify Material\nCE\nSelect Element\nReducer\nCreate Reducer\nCress Backwards\nDress Backwards\nReference Point\nPick\nPick on the segment which CTSTRA should be placed:\n.\nAlong Route (Zdis)\nOffsets\nAlong Route (Zdis)\nPick Position\nPick Position\nPick define position (Snap) Snap:\n\nAlign with gridline\nAlign with gridline\nPick Grid to define position:\nMove Offset\nGap\nProportion (Pkdis)\nHorizontal (Xoff)\nVertical (Zoff)\nAngle Attributes\nBeta Angle (Bang)\nDimensions\nTemplates\nTemplate Zone\nSelect Type\nUse Templates\nUse Templates\nDisplay Preliminary Dressing\nMode\nCreation\nModification\nModification\nModify window\nModify Material"}
{"Headers": "Element Naming", "Content": "Enter a name for the Cable element or automatically generate a name using the Autonaming icon to the right of the text box.\nPrimary System\nUse to assign a cable to a system from the selection available:\nNo System-default\nHigh Voltage System\nCompartment Heating System\nEmergency Lighting System\nFire Alarm System\nNo System-default\nNo System-default\nHigh Voltage System\nHigh Voltage System\nCompartment Heating System\nCompartment Heating System\nEmergency Lighting System\nEmergency Lighting System\nFire Alarm System\nFire Alarm System\n\n\n\nAutonaming\nPrimary System"}
{"Headers": "Basic Data", "Content": "Use to define the description, function and purpose attributes for the new cable element.\nCable Type\nThis is a new attribute and currently only impacts TREFOIL Bundle types. When attempting to ROUTE a TREFOIL BUNDLE a check is run to ensure there are three CONDUCTORS. If there are not three CONDUCTORS, an appropriate error message is displayed.\nIt is possible for TREFOIL BUNDLES to have a NEUTRAL and EARTH cable that runs along with the three CONDUCTORs. This creates a layout similar to the one displayed below:\n\nSelect the cable type from the drop down list:\nProximity Distance\nSpecifies the distance from the head; the software will start searching for cableway entry points\nFill Check\nDefines if fill-level checks are carried out automatically; default is On.\nTouching\nDefines if the cable can be touching another cable; default is On.\nCable Gap\nDefines the minimum distance between this cable and another one.\nSpacing\nDefine the minimum distance in diameter multiplications between this cable and another one.\nExcess Lengths\nSpecifies head and tail excesses which are used when the cable cutting lengths are calculated.\nEnter the Head excess length, Head extra excess length, Tail excess length and Tail extra excess length.\nCable Length\nDisplays the total length of the routed cable including excess lengths (default value is 0).\nCable Free Length\nDisplays the length of cable being routed outside of cableway branches, including the head and tail excess lengths. Default value is 0 and the Start and End of the cable free length is 0 by default.\nRouting Status\nIdentifies the current status of the cable. Default status is 0 (Un-routed), other statuses are 1 (Routed), 2 (Routing Failed), 3 (Partially Routed), 4 (Partially failed), 5 (Manually Routed).\nRED - CONDUCTOR\nBLACK - NETURAL\nYELLOW - EARTH\nRED - CONDUCTOR\nRED - CONDUCTOR\nBLACK - NETURAL\nBLACK - NETURAL\nYELLOW - EARTH\nYELLOW - EARTH\nCONDUCTOR\nNEUTRAL\nEARTH\nUnset\nCONDUCTOR\nCONDUCTOR\nNEUTRAL\nNEUTRAL\nEARTH\nEARTH\nUnset\nUnset\nNote:\nIt also allows for the storage greater detail about the cables should it be required.\nNote:\nProvided the NEUTRAL and EARTH cables have touching false and an appropriate gap value set.\nNote:\nThe Excess Length must be entered in this order.\n\n\n\nCable Type\nNote\n:\nNote\n:\nProximity Distance\nFill Check\nTouching\nCable Gap\nSpacing\nExcess Lengths\nNote\n:\nCable Length\nCable Free Length\nStart\nEnd\nRouting Status"}
{"Headers": "Specification", "Content": "Choose Cable - As the cable references a cable specification that contains the physical properties for the cable, use to select a cable specification.\n\nUse the Table and Type filters to select a type of cable to be used; the grid is automatically populated with the available cables. An individual cable can be selected from the displayed grid.\nProperties\nUse to display the properties of the selected cable. Click Plot File to display a graphical image of the selected cable.\nThe Specification details, description, O.D and Interference class are displayed in the Specification window.\n\nNote:\nIf a cable specification is not chosen, it will lead to inaccurate cable tray fill level calculations, when the routing the cable.\n\n\n\nChoose Cable\nTable\nType\nProperties\nPlot File\nSpecification\nNote\n:"}
{"Headers": "Start", "Content": "Defines a Start Ref (starting point) in the 3D view or a piece of equipment for the cable to start at.\nIf a reference is known, enter the reference location in the Reference field.\nIf Pick is selected, a prompt to Identify Equi/Valve/Pcom/Elconn for Start Ref: in the 3D view is displayed. The Reference field is automatically populated with the reference.\nIf List Equipment is selected, the List of Equipment window is displayed. Choose a piece of equipment from the List Equipment for Selection part of the window. Click Apply to choose the piece of equipment and close the List of Equipment window. Select Cancel to discard any inputs and close the List of Equipment window.\n\n\n\nReference\nPick\nIdentify Equi/Valve/Pcom/Elconn for Start Ref:\nReference\nList Equipment\nList of Equipment\nList Equipment for Selection\nApply\nList of Equipment\nCancel\nList of Equipment"}
{"Headers": "End", "Content": "Defines a End Ref (finishing point) in the 3D view or a piece of equipment for the cable to end at.\nIf a reference is known, enter the reference location in the Reference field.\nIf Pick is selected, a prompted to Identify Equi/Valve/Pcom/Elconn for Start Ref: in the 3D view is displayed. The Reference field is automatically populated with the reference.\nIf List Equipment is selected, the List of Equipment window is displayed. Choose a piece of equipment from the List Equipment for Selection part of the window. Select Apply to choose the piece of equipment and close the List of Equipment window. Select Cancel to discard any inputs and close the List of Equipment window.\n\n\n\nReference\nPick\nIdentify Equi/Valve/Pcom/Elconn for Start Ref:\nReference\nList Equipment\nList of Equipment\nList Equipment for Selection\nApply\nList of Equipment\nCancel\nList of Equipment"}
{"Headers": "Tasks", "Content": "A cable element is created and displayed in the design hierarchy and the Modify Cable window is displayed.\nNote:\nThe cable will not initially be shown in the 3D view. Once it has been routed, the cable is displayed.\n\n\n\nModify Cable\nNote\n:"}
{"Headers": "Cable Layout", "Content": "Defines how the cables are routed in the cableway.\nFor further information, refer to Modify Cable and .\n\n\n\nModify Cable\nModify Cable\n"}
{"Headers": "Modify", "Content": "Use the modify functionality to modify cableways, branches, points, attachments, route, control, multiple route, pull, junction nodes, material, material element and cable elements. Depending on selections made, further windows prompting for user input are displayed.\n\n\n"}
{"Headers": "Branch", "Content": "Right-click on a branch to display a pop-up menu:\nNavigate\nNavigates to the selected branch in the model explorer.\nHighlight\nHighlights the selected branch in the 3D view.\nUnhighlight\nRemoves the highlight from the branch in the 3D view.\n3D View\nAdd\nBranch\nAdds the selected branch to the 3D view.\nRemove\nBranch\nRemoves the branch from the 3D view.\nExport to Excel\nExports the branch grid data to Excel.\nPrint Preview\nOpens the Print Preview window.\nNavigate\nNavigates to the selected branch in the model explorer.\nHighlight\nHighlights the selected branch in the 3D view.\nUnhighlight\nRemoves the highlight from the branch in the 3D view.\n3D View\n\n\nAdd\nBranch\nAdds the selected branch to the 3D view.\n\nRemove\nBranch\nRemoves the branch from the 3D view.\nExport to Excel\nExports the branch grid data to Excel.\nPrint Preview\nOpens the Print Preview window.\nNavigate\nNavigates to the selected branch in the model explorer.\nHighlight\nHighlights the selected branch in the 3D view.\nUnhighlight\nRemoves the highlight from the branch in the 3D view.\n3D View\nAdd\nBranch\nAdds the selected branch to the 3D view.\nRemove\nBranch\nRemoves the branch from the 3D view.\nExport to Excel\nExports the branch grid data to Excel.\nPrint Preview\nOpens the Print Preview window.\n\n\n\nNavigate\nHighlight\nUnhighlight\n3D View\nAdd\nBranch\nRemove\nBranch\nExport to Excel\nPrint Preview"}
{"Headers": "Route", "Content": "For further information, refer to Route Node Modify Tasks, Attachment, Point, Control Node, Multiple Route Nodes, Pull Node, and Junction Node.\n\n\n\nRoute Node Modify Tasks\nAttachment\nPoint\nControl Node\nMultiple Route Nodes\nPull Node\nJunction Node\nRoute Node Modify Tasks\nAttachment\nPoint\nControl Node\nMultiple Route Nodes\nPull Node\nJunction Node"}
{"Headers": "Route Node Modify Tasks", "Content": "Use the functionality to modify the currently selected route node element.\n\nThe functionality is identical to that already described in Create Route Node.\n\n\n"}
{"Headers": "Attachment", "Content": "Use the functionality to modify the currently selected route attachment element.\n\n\n\n"}
{"Headers": "Point", "Content": "Use the functionality to modify the currently selected point element.\n\n\n\n"}
{"Headers": "Modify Material", "Content": "Use the functionality to modify the cableway branch material; a cableway branch material element must already exist.\nThe Cableway, Current Branch and Material Name fields are automatically populated with the owning elements and current element.\n\nAttributes\nThe attributes entered in the Create Material window are automatically displayed in the Modify Material window. To modify any of the attributes or dimensions, modify the attribute or dimension then click Apply Changes to commit the changes or click Discard Changes to discard any inputs.\nAutoname Elements\nUsed to apply the autonaming rules to the material elements that are owned by the material main element (CTMRL); the software automatically creates a new name for the elements.\nList Associated Cables\nDisplay the List of Cables window populated with all the cables associated with the current cableway branch.\nPreliminary defined by User\nChanges the attributes of the cable tray dressing, dresses the whole/part of the branch or removes any dressing from the branch.\n\nDimension Options\nThe dimension fields are automatically populated with attributes defined by an external source:\nTray Length for Dressing with Straights\nInput the required tray length in the field (this dimension is a session default; it reverts to the default (2000mm) when a new material is created).\nAttributes\nDefines the attributes for the material element.\n\nFirst Gap\nEnter the size of the gap before every material component (except where there are two adjoining straights).\nIntermediate Gap\nEnter the gap distance between all adjoining straights.\nLast Gap\nEnter the size of the gap after every material component except where there are two adjoining straights.\nTier Heights\nEnter the tier height(s).\nWidth and Height\nBy default the Width and Height are populated with the default cableway width and height. Different width and height dimensions can be entered if required.\nDress Backwards\nUse to dress the branch backwards.\nTees, Crosses and Reducers\nUse to create tee, cross and reducer cable tray elements when dressing the cableway branches with material (checkbox i selected by default).\nDress Whole Branch\nSpecify which elements are to be dressed on the whole branch:\nDress Part of Branch\nSpecify which elements will be dressed on parts of the branch selected:\nRemove Dressing\nRemove dressing from parts or all of the branch:\nMaterial\nTo apply the preliminary dressing, click Apply.\nTo remove the preliminary dressing, click Remove.\nTo return to the Modify Material window, click Back to Cableway Material Modify Tasks.\n\nLoad from Application Data\nLoad from Specification\nLoad from File\nLoad from Application Data\nLoad from Application Data\nLoad from Specification\nLoad from Specification\nLoad from File\nLoad from File\nWith Cable Tray Components\nWith Only Straights\nWith Only Bends and Risers\nWith Only Bends, Riser and Reducers\nWith Only Tees and Crosses\nFill Gaps with Straights\nSort Tray Components\nWith Cable Tray Components\nWith Cable Tray Components\nWith Only Straights\nWith Only Straights\nWith Only Bends and Risers\nWith Only Bends and Risers\nWith Only Bends, Riser and Reducers\nWith Only Bends, Riser and Reducers\nWith Only Tees and Crosses\nWith Only Tees and Crosses\nFill Gaps with Straights\nFill Gaps with Straights\nSort Tray Components\nSort Tray Components\nPicked Point\nPicked Attachment Point\nStraights between Picked Components\nSegments with Straights\nSegment with All Components\nMultiple Segments in Line\nPicked Point\nPicked Point\nPicked Attachment Point\nPicked Attachment Point\nStraights between Picked Components\nStraights between Picked Components\nSegments with Straights\nSegments with Straights\nSegment with All Components\nSegment with All Components\nMultiple Segments in Line\nMultiple Segments in Line\nFrom Branch\nFrom Segment\nFrom Point\nAll Straights from Branch\nAll Straights from Segment\nFrom Branch\nFrom Branch\nFrom Segment\nFrom Segment\nFrom Point\nFrom Point\nAll Straights from Branch\nAll Straights from Branch\nAll Straights from Segment\nAll Straights from Segment\n\n\n\nLoad from Application Data\nLoad from Specification\nLoad from File\nWith Cable Tray Components\nWith Only Straights\nWith Only Bends and Risers\nWith Only Bends, Riser and Reducers\nWith Only Tees and Crosses\nFill Gaps with Straights\nSort Tray Components\nPicked Point\nPicked Attachment Point\nStraights between Picked Components\nSegments with Straights\nSegment with All Components\nMultiple Segments in Line\nFrom Branch\nFrom Segment\nFrom Point\nAll Straights from Branch\nAll Straights from Segment\nAttributes\nCreate Material\nModify Material\nApply Changes\nDiscard Changes\nAutoname Elements\nList Associated Cables\nList of Cables\nPreliminary defined by User\nDimension Options\nLoad from Application Data\nLoad from Specification\nLoad from File\nTray Length for Dressing with Straights\nFirst Gap\nIntermediate Gap\nLast Gap\nTier Heights\nWidth and Height\nWidth\nHeight\nDress Backwards\nTees, Crosses and Reducers\nDress Whole Branch\nWith Cable Tray Components\nWith Only Straights\nWith Only Bends and Risers\nWith Only Bends, Riser and Reducers\nWith Only Tees and Crosses\nFill Gaps with Straights\nSort Tray Components\nDress Part of Branch\nPicked Point\nPicked Attachment Point\nStraights between Picked Components\nSegments with Straights\nSegment with All Components\nMultiple Segments in Line\nRemove Dressing\nFrom Branch\nFrom Segment\nFrom Point\nAll Straights from Branch\nAll Straights from Segment\nMaterial\nApply\nRemove\nModify Material\nBack to Cableway Material Modify Tasks"}
{"Headers": "Load from Application Data", "Content": "Select from the Application Data. Application Data Areas and Elements are a new form of definition in the Design Database that are provided to assist Appware Applications to store model parts for copying and propagation within a design.\n\n\n\nApplication Data"}
{"Headers": "Load from Specification", "Content": "Select a specification to populate the dimension fields. After a few minutes, a Message window is displayed. Click OK to change the specifications.\n\n\n\nMessage\nOK"}
{"Headers": "Load from File", "Content": "The dimensions (which are automatically populated) are referenced to a specification or data from another source.\n\n\n"}
{"Headers": "With Cable Tray Components", "Content": "Adds cable tray components to the whole cableway branch, observing any gaps set.\n\n\n"}
{"Headers": "With Only Straights", "Content": "Adds straight components to the whole cableway branch. Selecting the Do not cut checkbox prevents components being cut to fit the designated cable tray length.\n\n\n\nDo not cut"}
{"Headers": "With Only Bends and Risers", "Content": "Actions the creation of bend and riser components, where appropriate, along the cableway branch. Further elements can then be added using one of the other Dress options.\n\n\n\nDress"}
{"Headers": "With Only Bends, Riser and Reducers", "Content": "Actions the creation of bend, riser and reducer components, where appropriate, along the cable branch. Further elements can then be added using one of the other Dress options.\n\n\n\nDress"}
{"Headers": "With Only Tees and Crosses", "Content": "Actions the creation of tee and cross components, where appropriate, along the cable branch. Further elements can then be added using one of the other Dress options.\n\n\n\nDress"}
{"Headers": "Fill Gaps with Straights", "Content": "Adds straight components to any gaps in the whole cableway branch.\n\n\n"}
{"Headers": "Sort Tray Components", "Content": "Sorts the tray components in the whole cableway branch.\n\n\n"}
{"Headers": "Picked Point", "Content": "Pick a point on the branch at which a component is to be added. A prompt to Pick near the rout point (POINTR) to be dressed: is displayed.\n\n\n\nPick near the rout point (POINTR) to be dressed:"}
{"Headers": "Picked Attachment Point", "Content": "Pick an attachment point on the branch at which a component is to be added. A prompt to Pick RATTA to dress: is displayed.\n\n\n\nPick RATTA to dress:"}
{"Headers": "Straights between Picked Components", "Content": "Adds straight components between the picked components on the cableway branch. A prompt to Pick First Element:, then Pick Second Element: is displayed.\n\n\n\nPick First Element:\nPick Second Element:"}
{"Headers": "Segments with Straights", "Content": "Adds straight components to a selected segment. Selecting the Do not cut checkbox prevents components being cut to fit the segment length. A prompt to Pick near the start of the segment to be dressed: is displayed.\n\n\n\nDo not cut\nPick near the start of the segment to be dressed"}
{"Headers": "Segment with All Components", "Content": "Adds all the required cabletray components to a selected segment. A prompt to Pick near the start of the segment to be dressed: is displayed.\n\n\n\nPick near the start of the segment to be dressed:"}
{"Headers": "Multiple Segments in Line", "Content": "Adds multiple segments in line on the cableway branch. A prompt to Pick near the first point to be dressed:, then Pick near the second point to be dressed: is displayed.\n\n\n\nPick near the first point to be dressed:\nPick near the second point to be dressed:"}
{"Headers": "From Branch", "Content": "Removes the cable tray material from the whole cableway branch.\n\n\n"}
{"Headers": "From Segment", "Content": "Removes the cable tray material from the selected segment.\n\n\n"}
{"Headers": "From Point", "Content": "Removes the cable tray material from a selected point on the branch.\n\n\n"}
{"Headers": "All Straights from Branch", "Content": "Removes all the straight elements from the whole branch.\n\n\n"}
{"Headers": "All Straights from Segment", "Content": "Removes all the straight elements from the selected segment.\n\n\n"}
{"Headers": "Preliminary Dressing Considering Branch Fill Levels", "Content": "Changes attributes of the dressing, dresses the whole or part of the branch or removes the dressing from the branch with consideration to branch fill level.\nThe Preliminary Dressing (Considering Branch fill levels) window has the same common layout as the Preliminary Dressing (User defined Dimensions) with the exception for the Attributes part of the window.\n\nAttributes\nUse to modify the attributes for the preliminary dressing (considering branch fill levels).\n\nFirst Gap\nEnter the size of the gap before every material component, (except where there are two adjoining straights).\nIntermediate Gap\nEnter the gap distance between all adjoining straights.\nLast Gap\nEnter the size of the gap after every material component except where there are two adjoining straights.\n\n\n\nPreliminary Dressing (Considering Branch fill levels)\nPreliminary Dressing (User defined Dimensions)\nAttributes\nFirst Gap\nIntermediate Gap\nLast Gap"}
{"Headers": "Dress using Templates", "Content": "Dresses the cableway branches using a selected template. The Dress using Templates window has the same common layout as the Preliminary Dressing (User defined Dimensions) and Preliminary Dressing (Considering Branch fill levels) with the exception for the Dimension Options and Attributes parts of the window.\n\nAttributes\nUse to modify the attributes for dress using templates.\nFirst Gap\nEnter the size of the gap before every material component. (Except where there are two adjoining straights).\nIntermediate Gap\nEnter the gap distance between all adjoining straights.\nLast Gap\nEnter the size of the gap after every material component except where there are two adjoining straights.\nBy default, the Width is populated with the default cableway width; a different width dimension can be entered if required.\nTo apply the changes, select Apply Changes.\nTo dress the branch backwards, select Dress Backwards.\n\n\n\n\nDress using Templates\nPreliminary Dressing (User defined Dimensions) and Preliminary Dressing (Considering Branch fill levels)\nDimension Options\nAttributes\nFirst Gap\nIntermediate Gap\nLast Gap\nWidth\nApply Changes\nDress Backwards"}
{"Headers": "Remove Dressing", "Content": "Remove dressing from parts or all of the branch:\nFrom Branch\nFrom Segment\nFrom Point\nAll Straights from Branch\nAll Straights from Segment\nFrom Branch\nFrom Branch\nFrom Segment\nFrom Segment\nFrom Point\nFrom Point\nAll Straights from Branch\nAll Straights from Branch\nAll Straights from Segment\nAll Straights from Segment\n\n\n\nFrom Branch\nFrom Segment\nFrom Point\nAll Straights from Branch\nAll Straights from Segment\nFrom Branch\nFrom Segment\nFrom Point\nAll Straights from Branch\nAll Straights from Segment"}
{"Headers": "Material Element", "Content": "Use the functionality to modify the currently selected material element. The Modify Straight window has the same common layout as the Create Straight with the exception for the modification functionality available from the window.\n\nProperties of Cable Tray Material Element\nUse to modify the cable tray material element\u2019s properties.\nProperties of Cable Tray Template Element\nUse to modify the cable tray template element properties.\nCopy with Gap\nCopies existing cabletray material element with gap.\nCopy without Gap\nCopies existing cabletray material element without gap.\nUpdate Rules\nUse the functionality to update template rules.\n\n\n\nModify Straight\nCreate Straight\nProperties of Cable Tray Material Element\nProperties of Cable Tray Template Element\nCopy with Gap\nCopy without Gap\nUpdate Rules"}
{"Headers": "Modify Cable", "Content": "Use to modify the currently selected cable element, this can also be used to route a cable.The Modify Cable window has the same common layout as the Create Cable window with the exception of the Disconnect and Define Auto Routing functionality.\n\nDisconnect\nDisconnect the selected or newly created cable, to disconnect the cable from its starting point. On the Start tab (Default), click Disconnect Start. A message window is displayed requiring confirmation. To disconnect a cable from its finishing point, click to select the End tab, then click Disconnect End.\n\nAuto Routing\nUse to route a cable automatically via the shortest route or by means of defined points. It can also be used to unroute or delete a cable.\nAutomatic Routing is used when the start and end point are known. The application routes the cable along connected cableways in the Zone(s) selected using the shortest route. The cable will be orthogonally routed to the nearest attachment point on a cableway.\nClick the expand arrow to display the auto routing options, then select the zone for cable routing from the list of available options.\n\nOnce the zone for cable routing has been selected, the cable can be routed orthogonally between the starting and ending points; click Auto-Route Cable.\nTo reload the zones containing cables, or to reset selection. Click Reload Zones/Deselect All. Right click on a zone in the list to navigate to the zone in the Model Explorer.\nDefine Route\nUse to define the route of the cable. For further information, refer to Define Route.\nDefine Route\nThrough PRP\u2019s\nUse to define the route through PRPs. For further information, refer to Define Route Through Preliminary Route Points (PRPs).\nManual Route\nCable\nUse to manually route the cable. For further information, refer to Manual Route Cable.\nFree Route\nCable\nUse to free route the cable. For further information, refer to Free Route Cable.\nModify Free\nPoints\nUse to modify free points. For further information, refer to Modify Route Point.\nUn-route\nCable\nUse to un-route the cable. For further information, refer to Unroute Cables.\nDelete\nCable\nUse to delete the currently selected cable. For further information, refer to Delete Cable.\n\nDefine Route\nUse to define the route of the cable. For further information, refer to Define Route.\n\nDefine Route\nThrough PRP\u2019s\nUse to define the route through PRPs. For further information, refer to Define Route Through Preliminary Route Points (PRPs).\n\nManual Route\nCable\nUse to manually route the cable. For further information, refer to Manual Route Cable.\n\nFree Route\nCable\nUse to free route the cable. For further information, refer to Free Route Cable.\n\nModify Free\nPoints\nUse to modify free points. For further information, refer to Modify Route Point.\n\nUn-route\nCable\nUse to un-route the cable. For further information, refer to Unroute Cables.\n\nDelete\nCable\nUse to delete the currently selected cable. For further information, refer to Delete Cable.\nDefine Route\nUse to define the route of the cable. For further information, refer to Define Route.\nDefine Route\nThrough PRP\u2019s\nUse to define the route through PRPs. For further information, refer to Define Route Through Preliminary Route Points (PRPs).\nManual Route\nCable\nUse to manually route the cable. For further information, refer to Manual Route Cable.\nFree Route\nCable\nUse to free route the cable. For further information, refer to Free Route Cable.\nModify Free\nPoints\nUse to modify free points. For further information, refer to Modify Route Point.\nUn-route\nCable\nUse to un-route the cable. For further information, refer to Unroute Cables.\nDelete\nCable\nUse to delete the currently selected cable. For further information, refer to Delete Cable.\n\n\n\nDefine Route\nDefine Route Through Preliminary Route Points (PRPs)\nManual Route Cable\nFree Route Cable\nModify Route Point\nUnroute Cables\nDelete Cable\nModify Cable\nCreate Cable\nDisconnect\nDefine Auto Routing\nDisconnect\nStart\nDisconnect Start\nDisconnect End\nAuto Routing\nexpand arrow\nAuto-Route Cable\nReload Zones/Deselect All\nDefine Route\nDefine Route\nDefine Route\nThrough PRP\u2019s\nDefine Route Through Preliminary Route Points (PRPs)\nManual Route\nCable\nManual Route Cable\nFree Route\nCable\nFree Route Cable\nModify Free\nPoints\nModify Route Point\nUn-route\nCable\nUnroute Cables\nDelete\nCable\nDelete Cable"}
{"Headers": "Define Route", "Content": "Cables can be routed by the selection of an entry and exit point on valid cableway branches. If a route has not been defined for the cable then suitable points will automatically be selected in the Cable Branch Entry and Cable Branch Exit parts of the Route Cable window. If a route has been defined then the corresponding entry and exit points will be selected.\n\nCableway Branch Entry\nThe entry point for the cable on a suitable cableway branch must be specified, from the Cableway Branch Entry part of the Route Cable window:\nIf Pick Routing Branch is selected, a prompt to Identify Cableway Branch in the 3D view is displayed. When selected, the name of the cableway branch is displayed on the window and its valid entry points are displayed in the Select Entry Points list. The required entry point must then be selected from the Select Entry Points list.\nRight clicking on any item in the Select Entry Points or Select Exit Points lists displays the option to open the List of Associated Cables. Other cables that have been routed through the same point are displayed in the List of Cables window.\n\nCableway Branch Exit\nSpecify the exit point for the cable on a suitable cableway branch, from the Cableway Branch Exit part of the Route Cable window.\n\nRouting Options\nThe Auto Head/Tail Free Route checkbox must be selected if the head and tail of the cable is to be automatically free-routed. This routes the cable outside of the cableway by creating POINTR elements from the cable\u2019s head/tail to the selected entry/exit point.\nAfter clicking the Define Specific Cableway Zones expand arrow, select which cableway zones can be used to route the cable. If no zones are defined, then cableways from all zones found in WORLD will be used to route the cable. For large projects this will take a long time. Right click on a zone in the list to give the option to navigate to the zone in the Model Explorer.\nRouting Tasks\nAutoRoute from\nEntry to Exit Point\nWhen the cableway entry and exit points have been specified, the cable can be routed; click AutoRoute from Entry to Exit Point.\nHead Free Route\nIf the Auto Head/Tail Free Route checkbox is not selected but free routing of the ends is required to make cable routing complete, a prompt will be displayed giving the option to route both Head and Tail.\nIf the start position of the cable does not match the position of the entry point, the cable will not be fully routed. To complete the routing click Head Free Route which will create POINTR elements from the cable\u2019s head to the selected cableway entry point.\nThe same process can be done for routing of the end of the cable; click Tail Free Route.\nTail Free Route\n\nAutoRoute from\nEntry to Exit Point\nWhen the cableway entry and exit points have been specified, the cable can be routed; click AutoRoute from Entry to Exit Point.\n\nHead Free Route\nIf the Auto Head/Tail Free Route checkbox is not selected but free routing of the ends is required to make cable routing complete, a prompt will be displayed giving the option to route both Head and Tail.\nIf the start position of the cable does not match the position of the entry point, the cable will not be fully routed. To complete the routing click Head Free Route which will create POINTR elements from the cable\u2019s head to the selected cableway entry point.\nThe same process can be done for routing of the end of the cable; click Tail Free Route.\n\nTail Free Route\nAutoRoute from\nEntry to Exit Point\nWhen the cableway entry and exit points have been specified, the cable can be routed; click AutoRoute from Entry to Exit Point.\nHead Free Route\nIf the Auto Head/Tail Free Route checkbox is not selected but free routing of the ends is required to make cable routing complete, a prompt will be displayed giving the option to route both Head and Tail.\nIf the start position of the cable does not match the position of the entry point, the cable will not be fully routed. To complete the routing click Head Free Route which will create POINTR elements from the cable\u2019s head to the selected cableway entry point.\nThe same process can be done for routing of the end of the cable; click Tail Free Route.\nTail Free Route\nNote:\nThe minimum end radius is determined by the selected specification and the radius is added to the cable RPATH. This functionality is only available for free cable routing.\nNote:\nThe MAXCAB (maximum quantity of cables on the cableway) and MAXLAY (maximum layers of cables on the cableway) attributes are also dependent upon the selected specification).\nNote:\nIf the Define Specific Cableway Zones list was not used, a prompt will be displayed with a message, to proceed with routing through any cableways found in WORLD.\n\n\n\nCable Branch Entry\nCable Branch Exit\nRoute Cable\nCableway Branch Entry\nCableway Branch Entry\nRoute Cable\nPick Routing Branch\nIdentify Cableway Branch\nSelect Entry Points\nSelect Entry Points\nSelect Entry Points\nSelect Exit Points\nList of Associated Cables\nList of Cables\nCableway Branch Exit\nCableway Branch Exit\nRoute Cable\nRouting Options\nAuto Head/Tail Free Route\nDefine Specific Cableway Zones\nNote\n:\nNote\n:\nRouting Tasks\nAutoRoute from\nEntry to Exit Point\nAutoRoute from Entry to Exit Point\nHead Free Route\nAuto Head/Tail Free Route\nHead Free Route\nTail Free Route\nTail Free Route\nNote\n:"}
{"Headers": "Define Route Through Preliminary Route Points (PRPs)", "Content": "Route Points can be used to constrain the route of a cable. These route points are points through which the cable must pass.The route points are defined when the cableway branch is created and/or modified.\nIf a route has not been defined for the cable, then a list of suitable routing branches will be displayed. Select a route point from Select Preliminary Route Points from Cwbranch list. If a route has been defined then the chosen PRPs will be displayed in the List of Preliminary Route Points list.\nRouting Through PRPs\nFrom the Routing Through PRPs part of the Route Through PRPs window, select the cableway branch and then the PRPs to route the cable on the branch.\n\nPick Routing Branch\nPopulates the Select Preliminary Route Points from Cwbranch list with route points contained within the picked branch. Right click on one of the points in the list to give the option to open the List of Associated Cables window, which will show other cables that have been routed through the same point.\nOnce a suitable point has been selected it can be added to the List of Preliminary Route Points using one of three methods:\nInserts the selected point above the PRP selected in the List of Preliminary Route Points.\nInserts the selected point below the PRP selected in the List of Preliminary Route Points.\nInserts the selected point at the bottom of the List of Preliminary Route Points.\n\nInserts the selected point above the PRP selected in the List of Preliminary Route Points.\n\nInserts the selected point below the PRP selected in the List of Preliminary Route Points.\n\nInserts the selected point at the bottom of the List of Preliminary Route Points.\nItems in the List of Preliminary Route Points can be organized using the buttons to the right of the list:\nMoves PRP to the top of the list.\nMoves PRP up one row.\nRemoves the PRP from the list.\nMoves the PRP from the list.\nMoves the PRP to the bottom of the list.\n\nMoves PRP to the top of the list.\n\nMoves PRP up one row.\n\nRemoves the PRP from the list.\n\nMoves the PRP from the list.\n\nMoves the PRP to the bottom of the list.\nRight click on an item in the List of Preliminary Route Points to display options to organize the list and to open the List of Associated Cables window.\n\nLabel All PRPs\nAdd labels for all PRPs to the graphical view.\nRemove\nRemoves all PRP-related labels from the graphical view.\n\nLabel All PRPs\nAdd labels for all PRPs to the graphical view.\n\nRemove\nRemoves all PRP-related labels from the graphical view.\nRouting Options\nAfter clicking the Define Specific Cableway Zones expand arrow, select which cableway zones can be used to route the cable. If no zones are defined, then cableway from all zones found in WORLD will be used to route the cable. For large projects this will take a long time. Right click on a zone in the list to give the option to Navigate To the zone in the Model Explorer. If required click Reload Zones/Deselect All.\nRouting Tasks\nRoute Cable\nUse to route the cable through the PRPs on the branch without having to connect to equipment.\n\nRoute Cable\nUse to route the cable through the PRPs on the branch without having to connect to equipment.\n\nInserts the selected point above the PRP selected in the List of Preliminary Route Points.\nInserts the selected point below the PRP selected in the List of Preliminary Route Points.\nInserts the selected point at the bottom of the List of Preliminary Route Points.\nMoves PRP to the top of the list.\nMoves PRP up one row.\nRemoves the PRP from the list.\nMoves the PRP from the list.\nMoves the PRP to the bottom of the list.\nLabel All PRPs\nAdd labels for all PRPs to the graphical view.\nRemove\nRemoves all PRP-related labels from the graphical view.\nRoute Cable\nUse to route the cable through the PRPs on the branch without having to connect to equipment.\n\n\n\nSelect Preliminary Route Points from Cwbranch\nList of Preliminary Route Points\nRouting Through PRPs\nRouting Through PRPs\nRoute Through PRPs\nPick Routing Branch\nSelect Preliminary Route Points\nfrom Cwbranch\nList of Associated Cables\nList of Preliminary Route Points\nInserts the selected point below the PRP selected in the List of Preliminary Route Points.\nList of Preliminary Route Points\nList of Preliminary Route Points\nList of Preliminary Route Points\nList of Associated Cables\nLabel All PRPs\nRemove\nRouting Options\nDefine Specific Cableway Zones\nNavigate To\nReload Zones/Deselect All\nRouting Tasks\nRoute Cable"}
{"Headers": "Manual Route Cable", "Content": "Allows cables to be routed manually or a cable route modified between its start and end references. The current cable segments, if existing, are automatically displayed in the Existing Cable Segments part of the Manual Route Cable window.\n\nCableway Branch Entry/Exit\nSelect the cableway branch to create the segment of the cable route, click Pick Routing Branch and then select a cableway branch from the 3D view. The Select Entry/Exit from select Cableway Branch list will populate and display the points along the cableway branch that can be used as entry and exit points. Select a point from the list and then click Add (either of them) next to Entry or Exit shown below the list. The selected entry and exit points for the segment must be on the same cableway branch.\nWhen the entry and exit points have been defined, the segment is created.\nTo insert the segment in between existing segments, select a segment from the Existing Cable Segments list.\nCreate Before\nSelected Segment\nInserts the segment before the selected segment.\nCreate After\nSelected Segment\nInserts the segment after the selected segment.\nCreate at Bottom of\nSegment List\nInserts the segment at the end of the cableway branch list.\n\nCreate Before\nSelected Segment\nInserts the segment before the selected segment.\n\nCreate After\nSelected Segment\nInserts the segment after the selected segment.\n\nCreate at Bottom of\nSegment List\nInserts the segment at the end of the cableway branch list.\nExisting Cable Segments\nAn existing cable segment can be modified. Select a segment from the Existing Cable Segments list which will fill the Entry and Exit lines and can then be changed in a similar way to the creation method. When new entry and exit points have been selected, the changes can be made. Click Modify Selected Segment.\n\nAdd or Remove Lables\nToggle to add or remove labels from the 3D graphical view.\nRemove Selected Route Segment\nUse to delete existing cable segments.\n\nAdd or Remove Lables\nToggle to add or remove labels from the 3D graphical view.\n\nRemove Selected Route Segment\nUse to delete existing cable segments.\nRouting Tasks\nAutomatically generate\nfree route\nAutomatically routes a cable using the head free route, intermediate free route and tail free route functionality after every segment is created.\nNote:\nThis will remove all POINTRS and then recreate them.\nHead Free Route\nGenerates a free route of POINTR elements from the cables start reference (STAREF) to the first segment.\nIntermediate Free Route\nGenerates free routes of POINTR elements between each segment.\nTail Free Route\nGenerate a free route of POINTR elements from the last segment to the cables end reference (ENDREF).\nDelete Free Routes\nDeletes all free routes for the cable by removing all POINTR elements.\nAutomatically generate\nfree route\nAutomatically routes a cable using the head free route, intermediate free route and tail free route functionality after every segment is created.\n\nHead Free Route\nGenerates a free route of POINTR elements from the cables start reference (STAREF) to the first segment.\n\nIntermediate Free Route\nGenerates free routes of POINTR elements between each segment.\n\nTail Free Route\nGenerate a free route of POINTR elements from the last segment to the cables end reference (ENDREF).\n\nDelete Free Routes\nDeletes all free routes for the cable by removing all POINTR elements.\nCreate Before\nSelected Segment\nInserts the segment before the selected segment.\nCreate After\nSelected Segment\nInserts the segment after the selected segment.\nCreate at Bottom of\nSegment List\nInserts the segment at the end of the cableway branch list.\nAdd or Remove Lables\nToggle to add or remove labels from the 3D graphical view.\nRemove Selected Route Segment\nUse to delete existing cable segments.\nAutomatically generate\nfree route\nAutomatically routes a cable using the head free route, intermediate free route and tail free route functionality after every segment is created.\nNote:\nThis will remove all POINTRS and then recreate them.\nHead Free Route\nGenerates a free route of POINTR elements from the cables start reference (STAREF) to the first segment.\nIntermediate Free Route\nGenerates free routes of POINTR elements between each segment.\nTail Free Route\nGenerate a free route of POINTR elements from the last segment to the cables end reference (ENDREF).\nDelete Free Routes\nDeletes all free routes for the cable by removing all POINTR elements.\nNote:\nWhen selecting different creations methods with entry and exit points already selected, a Confirm window to clear the selected Entry/Exit points will be displayed. Click Yes to accept or No to cancel.\nNote:\nThis will remove all POINTRS and then recreate them.\n\n\n\nExisting Cable Segments\nManual Route Cable\nCableway Branch Entry/Exit\nPick Routing Branch\nSelect Entry/Exit from select Cableway Branch\nAdd\nEntry\nExit\nExisting Cable Segments\nCreate Before\nSelected Segment\nCreate After\nSelected Segment\nCreate at Bottom of\nSegment List\nNote\n:\nConfirm\nYes\nNo\nExisting Cable Segments\nExisting Cable Segments\nEntry\nExit\nModify Selected Segment\nAdd or Remove Lables\nRemove Selected Route Segment\nRouting Tasks\nAutomatically generate\nfree route\nNote\n:\nHead Free Route\nIntermediate Free Route\nTail Free Route\nDelete Free Routes"}
{"Headers": "Free Route Cable", "Content": "The entry (head) and exit (tail) points of the cable can be selected in the 3D view through the selected cableway. The head free route and tail free route are created using the same process. A prompt to Pick to define position <Esc> to finish (Snap) Snap: is displayed and the Positioning window is displayed.\nAfter the two points have been selected and labelled in the 3D view, press Esc; a Confirm window is displayed.\nClick Yes to route the cable between the two points and display the Modify Free Point window with Modification selected as the default, which allows the modification of a route point.\nNote:\nThe minimum bend radius is dependent upon the specification, the radius is added to the cable RPATH. Only present on sections of free cable routing.\n\n\n\nPick to define position <Esc> to finish (Snap) Snap:\nPositioning\nEsc\nConfirm\nNote\n:\nYes\nModify Free Point\nModification"}
{"Headers": "Modify Route Point", "Content": "The Modify Free Point window is dual-purpose window, which allows the creation or modification of a free point and acts as a task hub for all the options available for free points. The Modify Free Point window is automatically displayed populated with all the routing points of the cableway.\n\nSelect the routing point to be modified, the Modify Free Point window is automatically populated with the attributes for the selected routing point. The Route Point Connectivity Data part of the Modify Free Point window, displays the direction and distance of the currently selected route point from the previous one.\nIf a change in direction from the previous route point is required, enter a new direction in the Direction from Previous field. If a change in distance from the previous route point is required, in the Distance from Previous field, enter a new distance.\nThe Position part of the Modify Free Point window, displays the co-ordinates of the currently selected free point. Position the route point using the generic positioning options.\n\n\n\nModify Free Point\nModify Free Point\nModify Free Point\nRoute Point Connectivity Data\nModify Free Point\nDirection from Previous field\nDistance from Previous field\nPosition\nModify Free Point"}
{"Headers": "Unroute Cables", "Content": "It may be necessary to unroute a previously routed cable as part of the design process. Select the routed cable to be unrouted in the 3D view or in the Model Explorer. A Confirm window is displayed.\n\nClick Yes to unroute the cable and remove it from the 3D view, or No to discard any inputs and close the Confirm window.\n\n\n\nConfirm\nYes\nNo\nConfirm"}
{"Headers": "Delete Cable", "Content": "Use to delete the currently selected element in the 3D view. Click Yes to delete the association, or No to maintain the association.\n\nFor further information, refer to Attachment, Cable, Cableway, Cableway Branch, , , , , , , and .\n\n\n\nAttachment\nCable\nCableway\nCableway Branch\nYes\nNo\nAttachment\nCable\nCableway\nCableway Branch\n\n\n\n\n\n\n"}
{"Headers": "Branch Tools", "Content": "Use the functionality to split, merge and reverse a cableway branch(es).\n\n\n"}
{"Headers": "Split Cableway Branches", "Content": "It may be necessary to split cableway branch(es) as a result of a project requirement or so that the cabling system can be viewed more clearly. Cableway branch(es) can be split at a specified point or on a plane. Dependent upon how the cableway branch will be split, dictates how the window is displayed.\n\n\n"}
{"Headers": "Split at Point", "Content": "Use to split cableway branch(es) at a picked or specified point (default).\n\nPick Point\nA prompt to Pick on the segment which the branch should be split: is displayed. Once selected the split point is labelled in the 3D view, and the Point Definition part of then Split Cableway Branch window, is populated with the coordinates of the split point. If required, select one or all of the Lock boxes to fix the co-ordinate along the axes.\nAlign\nUse to align with the segment.\nDistance From Segment Start\nThe distance from the start of the segment field is automatically populated.\nMove Offset\nDefines a value in the box and use the right or left arrow to respectively increase or decrease the Distance from segment start by that value.\nMoving Down-stream Components To\nUse to define where the components located down-stream of the split are moved to when splitting a cableway branch.\nNew Cableway\nComponents downstream of the split will be moved into a new cableway branch in the design hierarchy.\nExisting Cableway\nComponents downstream of the split will be moved into extra cableway branches in the design hierarchy.\nNew Cableway\nComponents downstream of the split will be moved into a new cableway branch in the design hierarchy.\nExisting Cableway\nComponents downstream of the split will be moved into extra cableway branches in the design hierarchy.\nClick Split, the cableway branch is split at the point picked and the split is also displayed in the Model Explorer.\nNew Cableway\nComponents downstream of the split will be moved into a new cableway branch in the design hierarchy.\nExisting Cableway\nComponents downstream of the split will be moved into extra cableway branches in the design hierarchy.\nNote:\nSelect Auto Name checkbox to apply the autonaming rules, the software automatically creates a new name for the element.\n\n\n\nPick Point\nPick on the segment which the branch should be split:\nPoint Definition\nSplit Cableway Branch\nAlign\nDistance From Segment Start\nMove Offset\nMoving Down-stream Components To\nNew Cableway\nExisting Cableway\nNote\n:\nAuto Name\nSplit,\nModel Explorer"}
{"Headers": "Split using Plane", "Content": "Chose Split using Plane from the Split options: drop-down menu, the Split Cableway Branch window is displayed with the relevant options displayed.\n\nUse to select the cableway branch(es) to spilt.\nAdd Ce\nAdds the currently selected element in design hierarchy into the Branches to Split list.\nAdd Selected\nPick the Cableway branch(es) in the 3D view, and click Add Selected. The branch or branch(es) are added to the Branch to Split list.\nID Selection\nPrompted to Pick a Cableway branch (or branches) to be split is displayed. Press Esc to finish.\nClear all\nTo remove all branch(es) in the Branch to Split list, click Clear all.\nAdd Ce\nAdds the currently selected element in design hierarchy into the Branches to Split list.\nAdd Selected\nPick the Cableway branch(es) in the 3D view, and click Add Selected. The branch or branch(es) are added to the Branch to Split list.\nID Selection\nPrompted to Pick a Cableway branch (or branches) to be split is displayed. Press Esc to finish.\nClear all\nTo remove all branch(es) in the Branch to Split list, click Clear all.\nPlane Definition\nUse to define, position and modify the cutting plane.\nTo create the plane, select Create Plane, a prompt to Pick on the segment which the branch should be split: is displayed, once the segment is selected the plane is displayed in the 3D view.\nTo align the plane with another element, select Align, a prompt to Pick to define position (Snap) Snap: is displayed. Once the selection has been made, the plane is aligned with the selected element in the 3D view.\nModify Plane\nUse to modify and/or explicitly position the plane, select Modify plane, the Modify plane window is displayed. Enter new plane parameters for the plane and select OK to commit changes.\nMoving Down-stream Components To\nDefine where the components located down-stream of the split are moved to when splitting a cableway branch.\nNew Cableway\nComponents downstream of the split will be moved into a new cableway branch in the design hierarchy.\nExisting Cableway\nComponents downstream of the split will be moved into extra cableway branches in the design hierarchy.\nNew Cableway\nComponents downstream of the split will be moved into a new cableway branch in the design hierarchy.\nExisting Cableway\nComponents downstream of the split will be moved into extra cableway branches in the design hierarchy.\nThe cableway branch is split using the plane and the split is also displayed in the Model Explorer.\nAdd Ce\nAdds the currently selected element in design hierarchy into the Branches to Split list.\nAdd Selected\nPick the Cableway branch(es) in the 3D view, and click Add Selected. The branch or branch(es) are added to the Branch to Split list.\nID Selection\nPrompted to Pick a Cableway branch (or branches) to be split is displayed. Press Esc to finish.\nClear all\nTo remove all branch(es) in the Branch to Split list, click Clear all.\nNew Cableway\nComponents downstream of the split will be moved into a new cableway branch in the design hierarchy.\nExisting Cableway\nComponents downstream of the split will be moved into extra cableway branches in the design hierarchy.\nNote:\nSelect Auto Name checkbox to apply the autonaming rules, the software automatically creates a new name for the element.\n\n\n\nSplit using Plane\nSplit options:\nSplit Cableway Branch\nAdd Ce\nBranches to Split\nAdd Selected\nAdd Selected\nBranch to Split\nID Selection\nPick a Cableway branch (or branches) to be split\nEsc\nClear all\nBranch to Split\nClear all\nPlane Definition\nCreate Plane\nPick on the segment which the branch should be split:\nAlign,\nPick to define position (Snap) Snap:\n\nModify Plane\nModify plane\nModify plane\nOK\nMoving Down-stream Components To\nNew Cableway\nExisting Cableway\nNote\n:\nAuto Name\nModel Explorer"}
{"Headers": "Merge Cableway Branches", "Content": "Use to merge the branches of split Cableway branches. The prompt to Pick First Branch is displayed, select the first branch, a prompt to Pick Second Branch is displayed.\nWhen the second branch has been selected, a Confirm message is displayed, prompting to click Yes to merge the cableway branches, or click No to discard any inputs and close the Confirm window.\n\n\n\nPick First Branch\nPick Second Branch\nConfirm\nYes\nNo\nConfirm"}
{"Headers": "Reverse Cableway Branch", "Content": "Use to reverse the head of a branch to become the tail of the branch and the tail of the branch to be the head of the branch. All other branch elements are not affected.\n\n\n"}
{"Headers": "Copy Cabling Elements", "Content": "Use the functionality to copy existing zones, cableways, cableway branch and cableway with cables along with their associated sub elements where applicable.\n\n\n"}
{"Headers": "Copy Cableway Elements", "Content": "The Copy Cableway Element window has a common layout irrespective of the element selected to be copied. The only difference being the type of element to be copied, which populates parts of the Copy Cableway Element window.\n\nSelect Options\nUse the functionality to choose which element is to be copied.\nSelect Elements\nUse the functionality to select the elements to be copied.\nBranch to Copy\nMake sure that the element to be copied is highlighted in the Model Explorer. With the element highlighted in the Model Explorer, select CE from the Copy Cableway Elements identify the element as the CE.\nName of New Branch\nEnter a name for the Branch element or the name can be automatically generated using the Autonaming icon to the right of the text box.\nNumber of Copies\nUse to define how many copies are required.\nOffset\nDefines the position of the copied element(s) at an offset to a selected element.\nUse to set the distance for the offset, this can be done in two ways:\nInput the distance in the co-ordinate boxes, select one or all of the Lock checkboxes to fix the current co-ordinate along the E, N or U axis.\nAlternatively, select Pick Offset, in the 3D view, a prompt to Please pick an Element to define offset (Snap) Snap: is displayed, click to identify the element.\nSelect Copy, the new element is created in the Model Explorer and a message is displayed to confirm the Copy was successful, click OK to close the message window.\nZone and its associated sub elements\nCableway\nCableway Branch\nCableway with Cables and its associated sub elements\nZone and its associated sub elements\nZone and its associated sub elements\nCableway\nCableway\nCableway Branch\nCableway Branch\nCableway with Cables and its associated sub elements\nCableway with Cables and its associated sub elements\nNote:\nThe inputs required for Copy Cableway Elements window is dependent upon the element selected.\nNote:\nAutoname Elements checkbox is only available with Zone and Cableway and Cables elements.\nNote:\nE (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (negative Up).\nNote:\nWhen copying connected cables, the newly created copies of the cables will not have associations with equipment.\n\n\n\nCopy Cableway Element\nCopy Cableway Element\nSelect Options\nNote\n:\nCopy Cableway Elements\nSelect Elements\nBranch to Copy\nModel Explorer\nModel Explorer\nCE\nCopy Cableway Elements\nName of New Branch\nAutonaming\nNote\n:\nNumber of Copies\nOffset\nNote\n:\nPick Offset\nPlease pick an Element to define offset (Snap) Snap: is displayed,\nCopy\nModel Explorer\nOK\nNote\n:"}
{"Headers": "Copy Cable", "Content": "Use the functionality as an aid to the design process, select an existing cable with or without its connections, which can then be copied and modified.\n\nCable To Copy\nMake sure that the element to be copied is highlighted in the Model Explorer. With the element highlighted in the Model Explorer, select CE from the Copy Cableway Elements identify the element as the CE.\nName of New Cable\nEnter a name for the Cable element or the name can be automatically generated using the Autonaming icon to the right of the text box.\nNumber of Copies\nUse to define how many copies are required.\nCable Attributes to Copy\nUse to specify which cable attributes are to be copied.\nSpec Ref\nIf the cable to be copied has a specification set, then selecting this checkbox will copy the specification reference of the cable.\nStart Ref\nIf the cable to be copied is connected to an element at its start point, selecting this checkbox will copy the start reference of the cable.\nEnd Ref\nIf the cable to be copied is connected to an element at its end point, selecting this checkbox will copy the end reference of the cable.\nSpec Ref\nIf the cable to be copied has a specification set, then selecting this checkbox will copy the specification reference of the cable.\nStart Ref\nIf the cable to be copied is connected to an element at its start point, selecting this checkbox will copy the start reference of the cable.\nEnd Ref\nIf the cable to be copied is connected to an element at its end point, selecting this checkbox will copy the end reference of the cable.\nCable Excesses Lengths\nThe head and tail excesses from the currently selected cable are automatically displayed, if the excesses are required click to check the Cable Excesses Lengths checkbox. The excesses can be modified with the functionality available from the Modify Cable window.\nMark Points\nIf Mark Points functionality is not enabled, there are no mark points on the currently selected cable. These can be added with the functionality available from the Modify Cable window.\nPreliminary Points\nIf Preliminary Points functionality is not enabled, there are no preliminary points on the currently selected cable. These can be added with the functionality available from the Modify Cable window.\nRoute Path\nUse to copy the route path, head and tail free routes.\nCopy Route Path\nSelecting this checkbox copies only the external geometry (EXTGEO's) of the cable. If the cable contains no external geometry, then this becomes the default toggle for choosing whether to copy the RPATH or not. The same applies to if the RPATH contains all EXTGEO's.\nHead Free Route\nThe Head Free Route checkbox is only activated when the Copy Route Path checkbox has been selected. Selecting this option will copy the first POINTR's up to the first and including all the EXTGEO's excluding the tail POINTR's so the tail can be free routed as required.\nTail Free Route\nThe Tail Free Route checkbox is only activated when the Copy Route Path checkbox has been selected. Selecting this option will copy all the EXTGEO's and the remaining POINTR's which come after the geometry members in the sequence. Leaving the head POINTR's so the head can be free routed as required.\nCopy Route Path\nSelecting this checkbox copies only the external geometry (EXTGEO's) of the cable. If the cable contains no external geometry, then this becomes the default toggle for choosing whether to copy the RPATH or not. The same applies to if the RPATH contains all EXTGEO's.\nHead Free Route\nThe Head Free Route checkbox is only activated when the Copy Route Path checkbox has been selected. Selecting this option will copy the first POINTR's up to the first and including all the EXTGEO's excluding the tail POINTR's so the tail can be free routed as required.\nTail Free Route\nThe Tail Free Route checkbox is only activated when the Copy Route Path checkbox has been selected. Selecting this option will copy all the EXTGEO's and the remaining POINTR's which come after the geometry members in the sequence. Leaving the head POINTR's so the head can be free routed as required.\nSelect Copy, the new element is created in the Model Explorer and a message is displayed to confirm the Copy was successful, click OK to close the message window.\nSpec Ref\nIf the cable to be copied has a specification set, then selecting this checkbox will copy the specification reference of the cable.\nStart Ref\nIf the cable to be copied is connected to an element at its start point, selecting this checkbox will copy the start reference of the cable.\nEnd Ref\nIf the cable to be copied is connected to an element at its end point, selecting this checkbox will copy the end reference of the cable.\nCopy Route Path\nSelecting this checkbox copies only the external geometry (EXTGEO's) of the cable. If the cable contains no external geometry, then this becomes the default toggle for choosing whether to copy the RPATH or not. The same applies to if the RPATH contains all EXTGEO's.\nHead Free Route\nThe Head Free Route checkbox is only activated when the Copy Route Path checkbox has been selected. Selecting this option will copy the first POINTR's up to the first and including all the EXTGEO's excluding the tail POINTR's so the tail can be free routed as required.\nTail Free Route\nThe Tail Free Route checkbox is only activated when the Copy Route Path checkbox has been selected. Selecting this option will copy all the EXTGEO's and the remaining POINTR's which come after the geometry members in the sequence. Leaving the head POINTR's so the head can be free routed as required.\n\n\n\nCable To Copy\nModel Explorer\nModel Explorer\nCE\nCopy Cableway Elements\nName of New Cable\nAutonaming\nNumber of Copies\nCable Attributes to Copy\nSpec Ref\nStart Ref\nEnd Ref\nCable Excesses Lengths\nCable Excesses Lengths\nModify Cable\nMark Points\nMark Points\nModify Cable\nPreliminary Points\nPreliminary Points\nModify Cable\nRoute Path\nCopy Route Path\nHead Free Route\nTail Free Route\nCopy\nModel Explorer\nOK"}
{"Headers": "Move Branch Segment", "Content": "Use to move a cableway segment to a new position, re-route cables and re-dress materials.\n\nIdentify Segment\nIdentifies the segment to be moved, click Pick a prompt to 'Pick on the segment to be moved' is displayed. The name of the 'picked' segment and the allowed offset direction are automatically displayed.\nOffset\nSpecifies the offset and increment, alternatively select Align the prompt 'Pick to define position' is displayed, pick a position to align in the 3D view.\nRe-route Cables\nUse to define if cables are re-routed.\nRe-dress Materials\nUse to define if cableways are re-dressed automatically.\nDisplay Hole Manager\nDisplays the Hole Manager.\nShow issues\nDisplays any issues which arise as a result of the move, the grid is automatically populated with all route attachment points (associated items), type and status.\n\nMove Segment\nUse to move the selected segment to the new location.\nRight-click menus:\nCables\nBranch\nRnode or Ratta\nCables\nCables\nBranch\nBranch\nRnode or Ratta\nRnode or Ratta\n\n\n\nCables\nBranch\nRnode or Ratta\nIdentify Segment\nPick\n'Pick on the segment to be moved'\nOffset\nAlign\n'Pick to define position'\nRe-route Cables\nRe-dress Materials\nDisplay Hole Manager\nShow issues\nMove Segment\nCables\nBranch\nRnode or Ratta"}
{"Headers": "Cables", "Content": "Right-click on a cable to display a pop-up menu:\nNavigate\nNavigates to the selected cable in the model explorer.\nHighlight\nHighlights the selected cable in the 3D view.\nUnhighlight\nRemoves the highlight from the cable in the 3D view.\n3D View\nAdd Cable\nAdds the selected cable to the 3D view.\nAdd Connected\nAdds the connection to the selected cable to the 3D view.\nRemove Cable\nRemoves the selected cable from the 3D view.\nRemove Connected\nRemoves the connection from the 3D view.\nExport to Excel\nExports the cable grid data to Excel.\nPrint Preview\nOpens the Print Preview window.\nNavigate\nNavigates to the selected cable in the model explorer.\nHighlight\nHighlights the selected cable in the 3D view.\nUnhighlight\nRemoves the highlight from the cable in the 3D view.\n3D View\n\n\nAdd Cable\nAdds the selected cable to the 3D view.\n\nAdd Connected\nAdds the connection to the selected cable to the 3D view.\n\nRemove Cable\nRemoves the selected cable from the 3D view.\n\nRemove Connected\nRemoves the connection from the 3D view.\nExport to Excel\nExports the cable grid data to Excel.\nPrint Preview\nOpens the Print Preview window.\nNavigate\nNavigates to the selected cable in the model explorer.\nHighlight\nHighlights the selected cable in the 3D view.\nUnhighlight\nRemoves the highlight from the cable in the 3D view.\n3D View\nAdd Cable\nAdds the selected cable to the 3D view.\nAdd Connected\nAdds the connection to the selected cable to the 3D view.\nRemove Cable\nRemoves the selected cable from the 3D view.\nRemove Connected\nRemoves the connection from the 3D view.\nExport to Excel\nExports the cable grid data to Excel.\nPrint Preview\nOpens the Print Preview window.\n\n\n\nNavigate\nHighlight\nUnhighlight\n3D View\nAdd Cable\nAdd Connected\nRemove Cable\nRemove Connected\nExport to Excel\nPrint Preview"}
{"Headers": "Rnode or Ratta", "Content": "Right click on a Rnode or Ratta to display a pop-up menu:\nNavigate\nNavigates to the selected Rnode or Ratta in the model explorer.\nHighlight\nHighlights the selected Rnode or Ratta in the 3D view.\nUnhighlight\nRemoves the highlight from the Rnode or Ratta in the 3D view.\n3D View\nAdd Branch\nAdds the selected Rnode or Ratta to the 3D view.\nRemove Branch\nRemoves the Rnode or Ratta from the 3D view.\nExport to Excel\nExports the Rnode or Ratta grid data to Excel.\nPrint Preview\nOpens the Print Preview window.\nNavigate\nNavigates to the selected Rnode or Ratta in the model explorer.\nHighlight\nHighlights the selected Rnode or Ratta in the 3D view.\nUnhighlight\nRemoves the highlight from the Rnode or Ratta in the 3D view.\n3D View\n\n\nAdd Branch\nAdds the selected Rnode or Ratta to the 3D view.\n\nRemove Branch\nRemoves the Rnode or Ratta from the 3D view.\nExport to Excel\nExports the Rnode or Ratta grid data to Excel.\nPrint Preview\nOpens the Print Preview window.\nNavigate\nNavigates to the selected Rnode or Ratta in the model explorer.\nHighlight\nHighlights the selected Rnode or Ratta in the 3D view.\nUnhighlight\nRemoves the highlight from the Rnode or Ratta in the 3D view.\n3D View\nAdd Branch\nAdds the selected Rnode or Ratta to the 3D view.\nRemove Branch\nRemoves the Rnode or Ratta from the 3D view.\nExport to Excel\nExports the Rnode or Ratta grid data to Excel.\nPrint Preview\nOpens the Print Preview window.\n\n\n\nNavigate\nHighlight\nUnhighlight\n3D View\nAdd Branch\nRemove Branch\nExport to Excel\nPrint Preview"}
{"Headers": "Branch Dressing", "Content": "Use the functionality to bulk-dress cableway branches, set a specification and dress the cableway branch(es).\n\nDependent upon the currently selected element in the Model Explorer determines which elements populate (displaying the name of the branch element, specifications and an indication if the element is dressed).\nSelect\nSelect at which level in the cabling hierarchy, the elements are to be dressed.\n\nCurrent Branch\nAutomatically populates the grid with the currently selected branch.\nCurrent Cableway\nAutomatically populates the grid with all the branches below the cableway element.\nCurrent Zone\nAutomatically populates the grid with all the branches below the zone element.\nCurrent Site\nAutomatically populates the grid with all the branches below the site loaded.\nCurrent Branch\nAutomatically populates the grid with the currently selected branch.\nCurrent Cableway\nAutomatically populates the grid with all the branches below the cableway element.\nCurrent Zone\nAutomatically populates the grid with all the branches below the zone element.\nCurrent Site\nAutomatically populates the grid with all the branches below the site loaded.\nUse the functionality to set the first, intermediate and last gaps, default is 0 unless previously specified.\n\nSpecification\nUse to select the specification for the branch element, then select Set Selected Cableway Branches to Specification to set the selected specification. All selected cableway branches will have the same material specification applied through branches, cableways, zones or sites.\n\nUse to create tee, cross and reducer cable tray elements when dressing the cableway branches with material (checkbox is selected by default.\nDimensions\nDefines how the cableway branch dimensions are set.\nDefined by User\nWhere the dimensions reflect those set on the CTMTRL element, which in turn unless manually modified come from the cableway branch dimensions.\nBased on branch\nfill levels\nWhere the dimensions are based on branch fill levels which takes into account branch levels.\nDefined by User\nWhere the dimensions reflect those set on the CTMTRL element, which in turn unless manually modified come from the cableway branch dimensions.\nBased on branch\nfill levels\nWhere the dimensions are based on branch fill levels which takes into account branch levels.\nThe order in which the cableway branches are selected determines the order in which they are dressed.\nRight-click Menu\nUse the functionality from the right-click menu to select all cableway branches, remove dressing from selected branches, export data to excel or create a print preview.\nCurrent Branch\nAutomatically populates the grid with the currently selected branch.\nCurrent Cableway\nAutomatically populates the grid with all the branches below the cableway element.\nCurrent Zone\nAutomatically populates the grid with all the branches below the zone element.\nCurrent Site\nAutomatically populates the grid with all the branches below the site loaded.\nDefined by User\nWhere the dimensions reflect those set on the CTMTRL element, which in turn unless manually modified come from the cableway branch dimensions.\nBased on branch\nfill levels\nWhere the dimensions are based on branch fill levels which takes into account branch levels.\nNote:\nThe preliminary and final material dressing are carried out at the same time, to dress preliminary first, use the functionality available from the Modify Material window.\nNote:\nGap values cannot be applied to circular cableway branches, always 0.\nNote:\nIf the same order of cableway branches are selected and the dimensions are on branch fill levels, an incorrect dressing depending on the fill levels of the cables may occur.\n\n\n\nNote\n:\nModify Material\nSelect\nCurrent Branch\nCurrent Cableway\nCurrent Zone\nCurrent Site\nNote\n:\nSpecification\nSet Selected Cableway Branches to Specification\nDimensions\nDefined by User\nBased on branch\nfill levels\nNote\n:\nRight-click Menu"}
{"Headers": "Automatic Reducers", "Content": "The cableway branch dressing functionality automatically dresses the cableway with reducers where required as long as the cableway branches are already connected, there is a common edge or the smaller branch is positioned appropriately to the larger one. The reducer is added to the cableway with the smallest width to make sure the required cableway volume is always achieved.\n\nNote:\nThere are three types of reducers Eccentric (Right), Concentric (centered) and Eccentric (Left).\n\n\n\nNote\n:"}
{"Headers": "Mark Nodes", "Content": "Displays the route nodes on a cableway network and identifies their position in the 3D view.\n\nSelect\nUse to select which set of route nodes are displayed:\nCurrent Branch\nAutomatically populates the grid with the currently selected branch.\nCurrent Cableway\nAutomatically populates the grid with all the elements below the cableway element.\nCurrent Zone\nAutomatically populates the grid with all the elements below the zone element.\nCurrent Site\nAutomatically populates the grid with all the elements below the site loaded.\nCurrent Branch\nAutomatically populates the grid with the currently selected branch.\nCurrent Cableway\nAutomatically populates the grid with all the elements below the cableway element.\nCurrent Zone\nAutomatically populates the grid with all the elements below the zone element.\nCurrent Site\nAutomatically populates the grid with all the elements below the site loaded.\nThe grid of route nodes is divided into the following columns:\nName\nDisplays the name of the route node.\nBranch name\nDisplays the cableway branch name.\nWorld position\nDisplays the route node position with respect to the world.\nType\nDisplays the type of route node.\nMark Selected\nMark the currently selected elements.\nUnmark Selected\nUnmarks selected elements.\nMark All\nMarks all the element in the grid.\nUnmark All\nUmnarks all the elements in the grid.\nName\nDisplays the name of the route node.\nBranch name\nDisplays the cableway branch name.\nWorld position\nDisplays the route node position with respect to the world.\nType\nDisplays the type of route node.\nMark Selected\nMark the currently selected elements.\nUnmark Selected\nUnmarks selected elements.\nMark All\nMarks all the element in the grid.\nUnmark All\nUmnarks all the elements in the grid.\nCurrent Branch\nAutomatically populates the grid with the currently selected branch.\nCurrent Cableway\nAutomatically populates the grid with all the elements below the cableway element.\nCurrent Zone\nAutomatically populates the grid with all the elements below the zone element.\nCurrent Site\nAutomatically populates the grid with all the elements below the site loaded.\nName\nDisplays the name of the route node.\nBranch name\nDisplays the cableway branch name.\nWorld position\nDisplays the route node position with respect to the world.\nType\nDisplays the type of route node.\nMark Selected\nMark the currently selected elements.\nUnmark Selected\nUnmarks selected elements.\nMark All\nMarks all the element in the grid.\nUnmark All\nUmnarks all the elements in the grid.\n\n\n\nSelect\nCurrent Branch\nCurrent Cableway\nCurrent Zone\nCurrent Site\nName\nBranch name\nWorld position\nType\nMark Selected\nUnmark Selected\nMark All\nUnmark All"}
{"Headers": "Pull Pits", "Content": "Pull pits allow access to the underground networks for both cable pulling and maintenance.\nUse to create, position or modify an existing pull pit element, these elements are similar to equipment elements where they can be modelled using primitives and templates.\n\nNote:\nPull Node (PULLN) are automatically created with every pull pit, which is then used as connection references for conduits inside the pull pits.\n\n\n\nNote\n:"}
{"Headers": "Zone", "Content": "The currently selected zone in the Model Explorer is identified.\n\n\n"}
{"Headers": "Pull Pit", "Content": "All the existing pull pit elements in the currently selected zone are displayed in the Pull Pit list.\nPick in 3D View\nUse to pick an existing pull pit from the 3D view.\nCreate Pull Pit\nUse to create an new pull pit element.\nDelete Selected\nUse to delete the selected pull pit element.\nRefresh Selected\nUse to refresh the 3D view.\nSelect CE\nUse to select the currently selected element.\nPick in 3D View\nUse to pick an existing pull pit from the 3D view.\nCreate Pull Pit\nUse to create an new pull pit element.\nDelete Selected\nUse to delete the selected pull pit element.\nRefresh Selected\nUse to refresh the 3D view.\nSelect CE\nUse to select the currently selected element.\n\nPick in 3D View\nUse to pick an existing pull pit from the 3D view.\nCreate Pull Pit\nUse to create an new pull pit element.\nDelete Selected\nUse to delete the selected pull pit element.\nRefresh Selected\nUse to refresh the 3D view.\nSelect CE\nUse to select the currently selected element.\n\n\n\nPull Pit\nPick in 3D View\nCreate Pull Pit\nDelete Selected\nRefresh Selected\nSelect CE"}
{"Headers": "Details", "Content": "Use to name, assign a specification, modify properties, position WRT to Zone or orientate WRT to Zone.\nName\nEnter a name for the pull pit element or the name can be automatically generated using the Autonaming icon to the right of the text box.\nSpec\nUse to select a template or primitive represent a pull pit element to display in the 3D view from the list.\nUser-defined template\nUse a user defined template from the catalog to represent the pullpit element in the 3D view.\nif required, modify its properties.\nUnset (Use Primitives)\nUse a no- descript and non-editable primitive to represent the pullpit element in the 3D view.\nUnset (No Primitives)\nUse an invisible primitive to represent the pullpit element in the 3D view.\nA Confirm window is displayed 'Do you want to delete all existing primitives'.\nUser-defined template\nUse a user defined template from the catalog to represent the pullpit element in the 3D view.\n\nif required, modify its properties.\n\nUnset (Use Primitives)\nUse a no- descript and non-editable primitive to represent the pullpit element in the 3D view.\n\nUnset (No Primitives)\nUse an invisible primitive to represent the pullpit element in the 3D view.\n\nA Confirm window is displayed 'Do you want to delete all existing primitives'.\nPosition WRT Zone\nFormat\nExplicitly position the pull pit element at E0, N0, U0 (default).\nOffset\nUse to position the pull pit element using an offset, default is 0mm.\nLock\nUse to lock the coordinates.\nPick New Position\nUse to pick a new position in the 3D view for the pull pit element.\nFormat\nExplicitly position the pull pit element at E0, N0, U0 (default).\nOffset\nUse to position the pull pit element using an offset, default is 0mm.\nLock\nUse to lock the coordinates.\nPick New Position\nUse to pick a new position in the 3D view for the pull pit element.\nOrientation WRT ZONE\nX Direction\nUse to orientate the pull pit element WRT to the zone.\nY Direction\nUse to orientate the pull pit element WRT to the zone.\nX Direction\nUse to orientate the pull pit element WRT to the zone.\nY Direction\nUse to orientate the pull pit element WRT to the zone.\nFor further information, refer to Pull Pit Branch and Pull Node.\nUser-defined template\nUse a user defined template from the catalog to represent the pullpit element in the 3D view.\nif required, modify its properties.\nUnset (Use Primitives)\nUse a no- descript and non-editable primitive to represent the pullpit element in the 3D view.\nUnset (No Primitives)\nUse an invisible primitive to represent the pullpit element in the 3D view.\nA Confirm window is displayed 'Do you want to delete all existing primitives'.\nFormat\nExplicitly position the pull pit element at E0, N0, U0 (default).\nOffset\nUse to position the pull pit element using an offset, default is 0mm.\nLock\nUse to lock the coordinates.\nPick New Position\nUse to pick a new position in the 3D view for the pull pit element.\nX Direction\nUse to orientate the pull pit element WRT to the zone.\nY Direction\nUse to orientate the pull pit element WRT to the zone.\n\n\n\nPull Pit Branch\nPull Node\nName\nAutonaming\nSpec\nUser-defined template\nUnset (Use Primitives)\nUnset (No Primitives)\nConfirm\n'Do you want to delete all existing primitives'\nPosition WRT Zone\nFormat\nOffset\nLock\nPick New Position\nOrientation WRT ZONE\nX Direction\nY Direction\nPull Pit Branch\nPull Node"}
{"Headers": "Cable Junction Boxes", "Content": "Junction boxes are a link between underground and over ground cable routing. Use the functionality to create, position or modify an existing junction box element.\n\nNote:\nCables are routed orthogonally and associated junction nodes (JNODE) are automatically created.\n\n\n\nNote\n:"}
{"Headers": "Zone", "Content": "The currently selected zone in the Model Explorer is identified.\n\n\n"}
{"Headers": "Junction Box", "Content": "All the existing junction box elements in the currently selected zone are displayed in the Junction Box list.\nPick in 3D view\nUse to pick an junction box from the 3D view.\nCreate Pull Pit\nUse to create an new junction box element.\nDelete Selected\nUse to delete the selected junction box element.\nRefresh Selected\nUse to refresh the 3D view.\nSelect CE\nUse to select the currently selected element.\nPick in 3D view\nUse to pick an junction box from the 3D view.\nCreate Pull Pit\nUse to create an new junction box element.\nDelete Selected\nUse to delete the selected junction box element.\nRefresh Selected\nUse to refresh the 3D view.\nSelect CE\nUse to select the currently selected element.\nPick in 3D view\nUse to pick an junction box from the 3D view.\nCreate Pull Pit\nUse to create an new junction box element.\nDelete Selected\nUse to delete the selected junction box element.\nRefresh Selected\nUse to refresh the 3D view.\nSelect CE\nUse to select the currently selected element.\n\n\n\nJunction Box\nPick in 3D view\nCreate Pull Pit\nDelete Selected\nRefresh Selected\nSelect CE"}
{"Headers": "Details", "Content": "Use to name, assign a specification, modify properties, position WRT to Zone or orientate WRT to Zone.\nName\nEnter a name for the junction box element or the name can be automatically generated using the Autonaming icon to the right of the text box.\nSpec\nUse to select a template or primitive to represent a cable junction box element in the 3D view.\nUser defined template\nUse a user defined template from the catalog to represent the cable junction box element in the 3D view.\nif required, modify its properties.\nUnset (Use Primitives)\nUse a non-descript and non-editable primitive to represent the cable junction box element in the 3D view.\nUnset (No Primitvies)\nUse an invisible primitive to represent the cable junction box element in the 3D view.\n\u2018\nA Confirm window is displayed 'Do you want to delete all existing primitives'.\nUser defined template\nUse a user defined template from the catalog to represent the cable junction box element in the 3D view.\n\nif required, modify its properties.\n\nUnset (Use Primitives)\nUse a non-descript and non-editable primitive to represent the cable junction box element in the 3D view.\n\nUnset (No Primitvies)\nUse an invisible primitive to represent the cable junction box element in the 3D view.\n\u2018\n\nA Confirm window is displayed 'Do you want to delete all existing primitives'.\nPosition WRT Zone\nFormat:\nExplicitly position the junction box element at E0, N0, U0 (default).\nOffset\nUse to position the junction box element using an offset, default is 0mm.\nLock\nUse to lock the coordinates.\nPick New Position\nUse to pick a new position in the 3D view for the junction box element.\nFormat:\nExplicitly position the junction box element at E0, N0, U0 (default).\nOffset\nUse to position the junction box element using an offset, default is 0mm.\nLock\nUse to lock the coordinates.\nPick New Position\nUse to pick a new position in the 3D view for the junction box element.\nOrientation WRT ZONE\nX Direction\nUse to orientate the junction box element WRT to the zone.\nY Direction\nUse to orientate the junction box element WRT to the zone.\nX Direction\nUse to orientate the junction box element WRT to the zone.\nY Direction\nUse to orientate the junction box element WRT to the zone.\nFor further information, refer to Junction Node and Pull Pit Branch.\nUser defined template\nUse a user defined template from the catalog to represent the cable junction box element in the 3D view.\nif required, modify its properties.\nUnset (Use Primitives)\nUse a non-descript and non-editable primitive to represent the cable junction box element in the 3D view.\nUnset (No Primitvies)\nUse an invisible primitive to represent the cable junction box element in the 3D view.\n\u2018\nA Confirm window is displayed 'Do you want to delete all existing primitives'.\nFormat:\nExplicitly position the junction box element at E0, N0, U0 (default).\nOffset\nUse to position the junction box element using an offset, default is 0mm.\nLock\nUse to lock the coordinates.\nPick New Position\nUse to pick a new position in the 3D view for the junction box element.\nX Direction\nUse to orientate the junction box element WRT to the zone.\nY Direction\nUse to orientate the junction box element WRT to the zone.\n\n\n\nJunction Node\nPull Pit Branch\nName\nAutonaming\nSpec\nUser defined template\nUnset (Use Primitives)\nUnset (No Primitvies)\nConfirm\n'Do you want to delete all existing primitives'\nPosition WRT Zone\nFormat:\nOffset\nLock\nPick New Position\nOrientation WRT ZONE\nX Direction\nY Direction\nJunction Node\nPull Pit Branch"}
{"Headers": "Cable Data", "Content": "Provides the name, number of and description for all cables in selected zones, unrouted cables in selected zones or cables in an equipment zone.\n\nLoad All Cables for Selected Zones\nAll cables present in the selected zones will be displayed when viewing cable data.\nLoad Unrouted Cables for Selected Zones\nAll unrouted cables present in the selected zones will be displayed when viewing cable data.\nLoad All Cables for Equipment Zone\nAll cables present in the selected cable and equipment zones will be displayed when viewing cable data. Select the required equipment zone, then select Next to move to the next window.\n\nPrevious\nReturn to the previous window.\nRefresh\nRefresh the current window.\nNext\nMove to the next window.\n\nPrevious\nReturn to the previous window.\n\nRefresh\nRefresh the current window.\n\nNext\nMove to the next window.\nThe Cable Data window is now populated with cable data, route information and a routing error list, to view click the relevant tab.\nCables (default) - use to view the bundle type, class type, start reference, end reference, specification, outside diameter, minimum bend radius, cross sectional area, voltage AC, voltage DC, current and proximity distance.\nUse the order functionality to determine the order in which the cable(s) should be routed.\nMove To Top\nMove selected cable(s) to the top of the cable list displayed in the Cable Data window.\nMove Up\nMove selected cable(s) up the order in the cable list displayed in the Cable Data window.\nMove Down\nMove selected cable(s) down the order in the cable list displayed in the Cable Data window.\nMove To Bottom\nMove selected cable(s) to the bottom of the cable list displayed in the Cable Data window.\n\nMove To Top\nMove selected cable(s) to the top of the cable list displayed in the Cable Data window.\n\nMove Up\nMove selected cable(s) up the order in the cable list displayed in the Cable Data window.\n\nMove Down\nMove selected cable(s) down the order in the cable list displayed in the Cable Data window.\n\nMove To Bottom\nMove selected cable(s) to the bottom of the cable list displayed in the Cable Data window.\nRoute Information\nDisplays routing information for the selected cable (route element, type and owner).\nRouting Error List\nDisplays all the errors which occurred whilst routing.\n\nRoute Cables\nUse to route the selected cable(s) from the Cable Data window.\nWhen routing multiple cables, a progress bar is displayed in bottom-right-hand corner of the view.\nUnroute Cables\nUse to unroute the selected cable(s) from the Cable Data window.\nUndo & Refresh\nUndo previous action and refresh the display in the Cable Data window.\nToggle display of\nProximity Distance\nUse to visualize the proximity distance in the 3D view.\nInterrupt\nUse to interrupt the application routing multiple cables. A message is displayed stating the routing has been aborted and the progress made.\nNote:\nAt the time the routing is stopped, all cables routed remain routed. That is, the process does not rewind.\n\nRoute Cables\nUse to route the selected cable(s) from the Cable Data window.\nWhen routing multiple cables, a progress bar is displayed in bottom-right-hand corner of the view.\n\n\nUnroute Cables\nUse to unroute the selected cable(s) from the Cable Data window.\n\nUndo & Refresh\nUndo previous action and refresh the display in the Cable Data window.\n\nToggle display of\nProximity Distance\nUse to visualize the proximity distance in the 3D view.\n\n\nInterrupt\nUse to interrupt the application routing multiple cables. A message is displayed stating the routing has been aborted and the progress made.\nPrevious\nReturn to the previous window.\nRefresh\nRefresh the current window.\nNext\nMove to the next window.\nMove To Top\nMove selected cable(s) to the top of the cable list displayed in the Cable Data window.\nMove Up\nMove selected cable(s) up the order in the cable list displayed in the Cable Data window.\nMove Down\nMove selected cable(s) down the order in the cable list displayed in the Cable Data window.\nMove To Bottom\nMove selected cable(s) to the bottom of the cable list displayed in the Cable Data window.\nRoute Cables\nUse to route the selected cable(s) from the Cable Data window.\nWhen routing multiple cables, a progress bar is displayed in bottom-right-hand corner of the view.\nUnroute Cables\nUse to unroute the selected cable(s) from the Cable Data window.\nUndo & Refresh\nUndo previous action and refresh the display in the Cable Data window.\nToggle display of\nProximity Distance\nUse to visualize the proximity distance in the 3D view.\nInterrupt\nUse to interrupt the application routing multiple cables. A message is displayed stating the routing has been aborted and the progress made.\nNote:\nAt the time the routing is stopped, all cables routed remain routed. That is, the process does not rewind.\nNote:\nThe equipment zone drop down is only enabled if the Load all cables for equipment zones option is selected.\nNote:\nAt the time the routing is stopped, all cables routed remain routed. That is, the process does not rewind.\n\n\n\nLoad All Cables for Selected Zones\nLoad Unrouted Cables for Selected Zones\nLoad All Cables for Equipment Zone\nNext\nNote\n:\nLoad all cables for equipment zones\nPrevious\nRefresh\nNext\nCable Data\nCables\nMove To Top\nCable Data\nMove Up\nCable Data\nMove Down\nCable Data\nMove To Bottom\nCable Data\nRoute Information\nRouting Error List\nRoute Cables\nCable Data\nUnroute Cables\nCable Data\nUndo & Refresh\nCable Data\nToggle display of\nProximity Distance\nInterrupt\nNote\n:"}
{"Headers": "List Cables", "Content": "Displays cables associated with the current cableway branch and their attributes.\n\nAll Cables Tab\nLists all the associated cables in the currently selected zone along with the Class Type, Start Ref, End Ref, Specification, Status and Total Length attributes.\nCable Passing Tab\nLists all the cables that pass through current cableway branch along with the Class Type, Start Ref, End Ref, Specification, Status and Total Length attributes.\nIncoming Cables Tab\nLists all the incoming cables in the currently selected zone along with the Class Type, Start Ref, End Ref, Specification, Status and Total Length attributes.\nOutgoing Cables Tab\nLists all the outcoming cable in the currently selected zone along with the Class Type, Start Ref, End Ref, Specification, Status and Total Length attributes.\nCables Arriving/Leaving Tab\nLists all cables that arrive to and leave from the current cableway branch.\nCables Fill level Tab\nLists the fill levels on passing, incoming, outgoing and arriving/leaving cables.\n\n\n\nAll Cables\nTab\nCable Passing Tab\nIncoming Cables Tab\nOutgoing Cables Tab\nCables Arriving/Leaving\nTab\nCables Fill level\nTab"}
{"Headers": "Fill Level Check", "Content": "Use to check the fill level check on the currently selected cableway branch, default is ON.\n\nLoad From\nUse to populate the Select Cableway Branch list with all the cableway branches from the currently selected Site, Zone, Cableway and Cableway Branch.\nA right click menu is also available from the Select Cableway Branch list:\n\nNavigate to\nNavigates to the selected cableway branch in the model explorer.\nHighlight\nHighlights the currently selected cableway branch in the 3D view.\nNavigate to\nNavigates to the selected cableway branch in the model explorer.\nHighlight\nHighlights the currently selected cableway branch in the 3D view.\nInterference-Class Preferences\nUse to check only the selected cables in segments, select from the available list:\nCurrent Branch\nThe branch points of the currently selected cableway branch is automatically displayed in the Branch Points. The elements are ordered from HEAD to TAIL and the associated fill levels are also displayed.\nThe colours on each individual cell correspond to the value entered in the Fill Check Utility Allowance field.\nGreen\nIf a cell is coloured green, then the maximum fill of the branch is greater than the fill level.\nYellow\nIf a cell is coloured yellow, then the fill level of the branch point is within the fill check allowance to the maximum fill of the cableway branch.\nRed\nIf a cell is coloured red, then the fill level of the branch exceeds the maximum fill of the cableway branch.\nGreen\nIf a cell is coloured green, then the maximum fill of the branch is greater than the fill level.\nYellow\nIf a cell is coloured yellow, then the fill level of the branch point is within the fill check allowance to the maximum fill of the cableway branch.\nRed\nIf a cell is coloured red, then the fill level of the branch exceeds the maximum fill of the cableway branch.\nA right click menu is also available from the Branch Points list:\nNavigate to\nNavigates to the selected branch point in the Model Explorer.\nList of Cables\nDisplays the List of Cables window with the selected branch point.\nExport to Excel\nExports the Branch Points list data to Excel.\nNavigate to\nNavigates to the selected branch point in the Model Explorer.\nList of Cables\nDisplays the List of Cables window with the selected branch point.\nExport to Excel\nExports the Branch Points list data to Excel.\nWhen a branch point is selected from the list, graphical aids are displayed in the 3D view with the correct tag and position of the selected branch point.\nExplain Fill Levels\nUse to view an explanation of connections and fill levels.\n\nConnections\nAny valid connections are automatically displayed, if there are no valid connections No Connections Associated is displayed.\nNavigate to\nNavigates to the selected cableway branch in the model explorer.\nHighlight\nHighlights the currently selected cableway branch in the 3D view.\nGreen\nIf a cell is coloured green, then the maximum fill of the branch is greater than the fill level.\nYellow\nIf a cell is coloured yellow, then the fill level of the branch point is within the fill check allowance to the maximum fill of the cableway branch.\nRed\nIf a cell is coloured red, then the fill level of the branch exceeds the maximum fill of the cableway branch.\nNavigate to\nNavigates to the selected branch point in the Model Explorer.\nList of Cables\nDisplays the List of Cables window with the selected branch point.\nExport to Excel\nExports the Branch Points list data to Excel.\naverage of all\nPOWER\nINSTRUMENT\nCOMM\nSIGNAL\nCONTROL\nWIRE\naverage of all\naverage of all\nPOWER\nPOWER\nINSTRUMENT\nINSTRUMENT\nCOMM\nCOMM\nSIGNAL\nSIGNAL\nCONTROL\nCONTROL\nWIRE\nWIRE\nNote:\nThis list can be customized.\nNote:\nIf the current element is a RATTA, RNODE, HATTA or TATTA when the Fill Levels window is first initialized the branch point is automatically selected.\n\n\n\nLoad From\nSelect Cableway Branch\nSelect Cableway Branch\nNavigate to\nHighlight\nInterference-Class Preferences\nNote\n:\nCurrent Branch\nBranch Points\nFill Check Utility Allowance\nGreen\nYellow\nRed\nBranch Points\nNavigate to\nList of Cables\nExport to Excel\nExplain Fill Levels\nConnections\nNo Connections Associated\nNote\n:\nFill Levels"}
{"Headers": "Cable Material - Dressing Based on Fill Level", "Content": "The dressing is around laid cables the software does not attempt to change the layout of existing cables.\nFor further information, refer to Cable and Defaults.\n\n\n\nCable\nDefaults\nCable\nDefaults"}
{"Headers": "Check", "Content": "Use to navigate to a current branch, cableway, site or zone, and check the cableway branch connections.\n\nTag\nHighlights selected, connected, unconnected or all of the connections in the 3D view. Connections with errors can also be highlighted or all highlights can be removed from the 3D view.\nRight click menu available from the Cableway Branch Connections list:\nNavigate on Selection\nUse to select an element in the list and Model Explorer.\nDisconnect\nDisconnects the branch.\nExport to Excel\nExport the Cableway Branch Connection list data to Excel.\nPrint Preview\nDisplays a print preview.\nNavigate on Selection\nUse to select an element in the list and Model Explorer.\nDisconnect\nDisconnects the branch.\nExport to Excel\nExport the Cableway Branch Connection list data to Excel.\nPrint Preview\nDisplays a print preview.\nNavigate on Selection\nUse to select an element in the list and Model Explorer.\nDisconnect\nDisconnects the branch.\nExport to Excel\nExport the Cableway Branch Connection list data to Excel.\nPrint Preview\nDisplays a print preview.\n\n\n\nTag\nCableway Branch Connections\nNavigate on Selection\nDisconnect\nExport to Excel\nPrint Preview"}
{"Headers": "Connect Branch", "Content": "Use to connect the branches of split Cableway branches.\nA prompt to Pick First Branch is displayed, select the first branch, a prompt to Pick Second Branch is displayed.\nWhen the second branch has been selected, a Confirm message is displayed, prompting to click Yes to connect the cableway branches, or click No to discard any inputs and close the Confirm window.\n\n\n\nPick First Branch\nPick Second Branch\nYes\nNo\nConfirm"}
{"Headers": "Disconnect", "Content": "Use the functionality to disconnect pieces of equipment (EQUI) or associated Electrical Connections (ELCONN).\n\n\n"}
{"Headers": "Disconnect Equipment", "Content": "To disconnect cables connected directly to the currently selected piece of equipment, make sure the required equipment element is highlighted as the CE in the Model Explorer.\nA Confirm window is displayed, prompting Disconnect all Cables directly connected to this Equipment?\nClick Yes to disconnect the selected equipment, or click No to close the window and discard any inputs.\n\n\n\nDisconnect all Cables directly connected to this Equipment?\nYes\nNo"}
{"Headers": "Cable Routing Rules", "Content": "When not routing cables on a cableway, such as within a cable pull pits, junction boxes or by free routes, the software applies cabling routing rules. The cables are routed orthogonally using the following calling routing rules.\n\n\n"}
{"Headers": "Rule One", "Content": "When a cable is routed from or to:\n1\nSource connection, equipment or electrical connection\n2, 4, 6, 8\nEntry into a cableway.\n3, 5, 7, 9\nExit from a cableway.\n10\nDestination connection, equipment or electrical connection.\n1\nSource connection, equipment or electrical connection\n2, 4, 6, 8\nEntry into a cableway.\n3, 5, 7, 9\nExit from a cableway.\n10\nDestination connection, equipment or electrical connection.\n\nThe cable will have a minimum straight length in the same direction as the connection point:\n1\nSource connection, equipment or electrical connection\n2, 4, 6, 8\nEntry into a cableway.\n3, 5, 7, 9\nExit from a cableway.\n10\nDestination connection, equipment or electrical connection.\nIf the cable has a bend radius greater than 0, then the bend radius for a metric project is plus 10mm or 1/2\" for an imperial project.\nIf the bend radius is equal to 0, then the bend radius for metric project is 100mm or 4\" for an imperial project.\nIf the cable has a bend radius greater than 0, then the bend radius for a metric project is plus 10mm or 1/2\" for an imperial project.\nIf the cable has a bend radius greater than 0, then the bend radius for a metric project is plus 10mm or 1/2\" for an imperial project.\nIf the bend radius is equal to 0, then the bend radius for metric project is 100mm or 4\" for an imperial project.\nIf the bend radius is equal to 0, then the bend radius for metric project is 100mm or 4\" for an imperial project.\nNote:\nWhen connected to equipment, elconn may not have a direction.\n\n\n\n1\n2, 4, 6, 8\n3, 5, 7, 9\n10\nNote\n:"}
{"Headers": "Rule Two", "Content": "The route of the cable can be calculated orthogonally, a check is made to determine if the bend radius fits the calculated route using the same rules detailed in rule one.\nExample One\nFor a cable in one plane, if the bend radius does not fit then the cable route fails.\n\nExample Two\nFor a cable in two planes, the software attempts to offset the first point by moving it back towards the starting point as a result the difference between the two points results in a 45 degree slope.\n\nIf this fails the software moves the second point to the same value as above (twice), if the bend radius does not fit, then the software moves the point back so the initial route is the minimum distance from the start.\n\nIf the bend radius does not fit, the software moves the next point forward so that the initial route is the minimum distance from the end.\n\nExample Three\nThe software follows the rules as describes in rule two and carries out these additional checks. The software checks the bend radius for point 1, if it does not fit the software moves back towards the start by the distance between point 1 and 2.\n\nThe bend radius is checked for a fit at point 1, if it does not fit the software moves point 3 towards the end by the distance between point 1 and 2.\n\nThe bend radius is checked for a fit at point 1, if this is not the case, move point 1 towards the start so the distance from the start is the minimum needed.\n\nThe bend radius is checked for a fit at point 1, if the bend radius does not fit, then the cable route is failed.\n\nIf the bend radius fits check point 3, if it does not fit then the software will move point 3 towards the end so the distance to the end is the minimum needed.\n\nNote:\nThis depends on what is larger, the offset value is the distance between the two points or the minimum bend radius of the routed cable.\n\n\n\nExample One\nExample Two\nNote\n:\nExample Three"}
{"Headers": "Bundles", "Content": "A cable bundle is a group of cables routed together as one group. They will share the same rectangular branches throughout the route, but may split into different conduits depending on Fill Levels.\nThe bundle is routed on any cableway branch that is valid, for example the correct ICLASS, if the tray has room and so on, and as long as it is within the 'RANEQUI' (Proximity Distance) of the STAREF/ENDREF. The RANEQUI is an attribute set on the cable to specify the area to look to find its way onto a 'Cableway Network'.\nA Cable bundle element stores information about how cables will be arranged in the LAYOUT attribute.\nEvery cable under bundle have the start and end ref belonging to the same equipment\nNote:\nThis also applies to ENDREF which is the 'End Reference and every cable in the bundle will have the same start and end as the bundle.\n\n\n\nNote\n:"}
{"Headers": "Create Bundle", "Content": "Use this functionality to route bundles as depicted by the layout arrangement so that they are positioned correctly on the cable tray.\n\nName\nEnter the name of the bundle.\nLayout Mode\nSelect from the list of layout modes:\nTREFOIL\nFLAT\nLAYERED\nPACKED\nFor further information, refer to .\nDescription\nEnter the description of the bundle.\nFunction\nEnter the function of the bundle.\nPurpose\nEnter the purpose of the bundle.\nName\nEnter the name of the bundle.\nLayout Mode\nSelect from the list of layout modes:\nFor further information, refer to .\nDescription\nEnter the description of the bundle.\nFunction\nEnter the function of the bundle.\nPurpose\nEnter the purpose of the bundle.\nLayout Modes\nThe following are graphical representations of the layout modes available.\n\nClick Apply the Create Bundle window is automatically changed to the Modify Bundle window. A Bundle element is also created in the Model Explorer.\nName\nEnter the name of the bundle.\nLayout Mode\nSelect from the list of layout modes:\nTREFOIL\nFLAT\nLAYERED\nPACKED\nFor further information, refer to .\nDescription\nEnter the description of the bundle.\nFunction\nEnter the function of the bundle.\nPurpose\nEnter the purpose of the bundle.\nTREFOIL\nFLAT\nLAYERED\nPACKED\nTREFOIL\nTREFOIL\nFLAT\nFLAT\nLAYERED\nLAYERED\nPACKED\nPACKED\n\n\n\nName\nLayout Mode\n\nDescription\nFunction\nPurpose\nLayout Modes\nApply\nCreate Bundle\nModify Bundle"}
{"Headers": "Modify Bundle", "Content": "Use the functionality available from the Modify Bundle window to create a new cable under the bundle, add a cable to the bundle, remove a cable from the bundle, delete a cable from the bundle and verify the layout.\n\nTo modify the name of a bundle, select the bundle element in the Model Explorer click CE, modify as required.\nTo modify the Layout Mode of the bundle, select from the list of modes available.\nIf there are any cables already in the bundle the details are displayed in the Cables in Bundle pane of the Modify Bundle window.\nCreate Cable\nDisplays the Create Cable window, use to create a new cable to add to the bundle.\nAdd Cable\nDisplays the Add cables to Bundle window, use to select cable(s) from a list of available cables to add to the bundle. Then click Insert cables to add the selected cable(s) to the bundle.\nNote:\nThe cable must have the same start and end equipment to be included in the bundle. If this is not the case the following error message is displayed:\nRemove Cable\nUse to remove the cable(s) from the bundle, select the cable(s) from the Cables in Bundle pane.\nRemove Cable\nUse to delete the cable(s) from the bundle, select the cable(s) from the Cables in Bundle pane.\nVerify Layout\nUse to verify the cable layout.\n\nCreate Cable\nDisplays the Create Cable window, use to create a new cable to add to the bundle.\n\nAdd Cable\nDisplays the Add cables to Bundle window, use to select cable(s) from a list of available cables to add to the bundle. Then click Insert cables to add the selected cable(s) to the bundle.\n\n\n\nRemove Cable\nUse to remove the cable(s) from the bundle, select the cable(s) from the Cables in Bundle pane.\n\nRemove Cable\nUse to delete the cable(s) from the bundle, select the cable(s) from the Cables in Bundle pane.\n\nVerify Layout\nUse to verify the cable layout.\n\nCreate Cable\nDisplays the Create Cable window, use to create a new cable to add to the bundle.\nAdd Cable\nDisplays the Add cables to Bundle window, use to select cable(s) from a list of available cables to add to the bundle. Then click Insert cables to add the selected cable(s) to the bundle.\nNote:\nThe cable must have the same start and end equipment to be included in the bundle. If this is not the case the following error message is displayed:\nRemove Cable\nUse to remove the cable(s) from the bundle, select the cable(s) from the Cables in Bundle pane.\nRemove Cable\nUse to delete the cable(s) from the bundle, select the cable(s) from the Cables in Bundle pane.\nVerify Layout\nUse to verify the cable layout.\nNote:\nThe cable must have the same start and end equipment to be included in the bundle. If this is not the case the following error message is displayed:\n\n\n\nModify Bundle\nLayout Mode\nCables in Bundle\nModify Bundle\nCreate Cable\nCreate Cable\nAdd Cable\nAdd cables to Bundle\nInsert cables\nNote\n:\nRemove Cable\nCables in Bundle\nRemove Cable\nCables in Bundle\nVerify Layout"}
{"Headers": "Cable Bundle Routing", "Content": "Cables that are part of a bundle are routed in the following ways:\nAlways routed through the same rectangular (VSHAPE 0) Cableway Branches (CWBRAN)\nSplit into different conduit (VSHAPE 1) Cableway Branches when they cannot fit onto the same one.\nAlways routed through the same rectangular (VSHAPE 0) Cableway Branches (CWBRAN)\nAlways routed through the same rectangular (VSHAPE 0) Cableway Branches (CWBRAN)\nSplit into different conduit (VSHAPE 1) Cableway Branches when they cannot fit onto the same one.\nSplit into different conduit (VSHAPE 1) Cableway Branches when they cannot fit onto the same one.\nNote:\nIf LAYOUT is enabled these cables will be arranged in accordance to the LAYMOD (Trefoil, Flat, Layered, Packed) of the Cable Bundle (BUNDLE).\n\n\n\nNote\n:"}
{"Headers": "Known Error Messages", "Content": "Error\nDescription\n125, 26 - No Space\n'Layout failed - Insufficient space in branch /CWAY-POWER02-BUILDING-B01/B1 to lay /CBLP-B01-AHU-001-01'\nThis error is displayed when trying to lay a cable in insufficient space within a 'routing volume'.\nIn this example: there is not enough space on the branch /CWAY-POWER02-BUILDING-B01/B1 to lay cable /CBLP-B01-AHU-001-01.\n125, 27 - Invalid Radius\nLayout failed - Radius of /CBLP-B01-AHU-001-01 in branch /CWAY-POWER02-BUILDING-B01/B1 would be less than minimum bend radius'\nThis error is displayed when trying to lay a cable, in the only place available and as a result causes the cable\u2019s bend radius to be smaller than the minimum.\nIn this example: the radius of cable /CBLP-B01-AHU-001-01 when being laid on the branch /CWAY-POWER02-BUILDING-B01/B1 causes the bend radius to be less than the cables minimum bend radius.\n125, 28 - Invalid Element\n'Layout failed - Element /EQUI-B01-AHU-02-001 is not a routing object'\nThis error is displayed when trying to perform layout on an element that is not of the correct type.\nIn this example: the element /EQUI-B01-AHU-02-001 which is an Equipment, is not of the correct type to perform layout on.\n125, 29 - Maxlay Reached - 125, 29\n'Layout failed - Exceeded maximum layers(3) in branch /CWAY-POWER02-BUILDING-B01/B1'\nThis error is displayed once the limit of layers on a tray is reached. (When multiple cables are stacked to fit them onto the tray (branches can be restricted to a certain number of layers).\nIn this example: to lay a cable we will have to exceed the maximum number of layers (which is 3), on the branch /CWAY-POWER02-BUILDING-B01/B1.\n125, 30 - Can Not Be Touching\n'Layout failed - /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 would be touching\u2019\nLaying cables have rules applied to them, one of these rules is that certain cables cannot touch.\nThis error is displayed when a cable touches another cable which has been be identified as prohibited.\nThe rule is applied when laying a cable or verifying existing laid cables.\nIn this example: cables /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 would be touching, producing an invalid layout.\n125, 31 - Can Not Stack Bigger Cable\n'Layout failed - Can not put bigger object /CBLP-B01-AHU-001-01 on top of smaller object /CBLP-B01-AHU-001-02'\nThis error is displayed when larger cables are stacked on top of smaller cables. The rule is applied when laying a cable or verifying existing laid cables.\nIn this example: the larger cable /CBLP-B01-AHU-001-01 cannot be placed on top of the smaller cable /CBLP-B01-AHU-001-02.\n125, 32 - Layer Not Aligned\n'Layout failed - /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 are not layered correctly'\nThis error is displayed when stack cable\u2019s centres are not aligned.\nThe rule is applied after laying a cable, or verifying existing laid cables.\nIn this example: cables /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 are not layered correctly.\n125, 33 - Not Tried\n'Layout failed - Layout process could not begin\u2019\nThis error is displayed when the layout process is unable to begin.\n125, 34 - First Layer Not At Bottom\n'Layout failed - /CBLP-B01-AHU-001-01 is not at bottom in branch /CWAY-POWER02-BUILDING-B01/B1'\nThis error is displayed when laying cables, the first layer is not on the bottom of the routing volume.\nIn this example: the layer which cable /CBLP-B01-AHU-001-01 has been laid on is not at the bottom of the branch /CWAY-POWER02-BUILDING-B01/B1.\n125. 35 - Collision\n'Layout failed - /CBLP-B01-AHU-001-01 collides with /CBLP-B01-AHU-001-02'\nThis error is displayed when cables collide with one another. The rule is applied after laying a cable or verifying existing laid cables.\nIn this example: the cable /CBLP-B01-AHU-001-01 collides with cable /CBLP-B01-AHU-001-02.\nSegment Not Found - 125, 36\n'Layout failed - Branch /CWAY-POWER02-BUILDING-B01/B1 does not have POWER segment to put /CBLP-B01-AHU-001-01 in'\nIdeally when laying cables in a segregated branch (a branch with multiple ICLASS segments) the cables are placed in the correct segments.\nThis error is displayed when a segment on the branch that matches the cables ICLASS cannot be found.\nIn this example: the branch /CWAY-POWER02-BUILDING-B01/B1 does not have a POWER ICLASS segment to place the cable /CBLP-B01-AHU-001-01 in.\nWrong Segment - 125, 37\n'Layout failed - /CBLP-B01-AHU-001-01 is not in correct segment at /CWAY-POWER02-BUILDING-B01/B1'\nWhile laying cables and verifying existing laid cables we need to check that the cable is laid in the correct segment of a segregated branch. This error is displayed is this is not the case.\nIn this example: the cable /CBLP-B01-AHU-001-01 is not in the correct segment on the branch /CWAY-POWER02-BUILDING-B01/B1.\nStacking Not Allowed - 125, 39\n'Layout failed - Not allowed to stack /CBLP-B01-AHU-001-01'\nWhile laying cables and verifying existing laid cables we need to check that the cable has been identified as stack able.\nFor example checking the cable itself is allowed to touch other cables, as well as the cables it touches are also allowed to touch other cables. Additionally we need to ensure that there is a cable underneath the cable we are attempting to stack, and that nothing is already stacked there.\nShould any of the statements be untrue then this error that is returned.\nIn this example: the cable /CBLP-B01-AHU-001-01 is not allowed to stack.\nNot Tried Invalid Layout - 125, 38\n'Layout failed - Layout could not begin because /CBLP-B01-AHU-001-01 has invalid layout at /CWAY-POWER02-BUILDING-B01/B1'\nBefore attempting to lay a cable we must first ensure that the branches have a valid layout. Should a branch be found with an invalid layout, this is the error that is returned.\nIn this example: layout could not begin because the cable /CBLP-B01-AHU-001-01 has an invalid layout on the branch /CWAY-POWER02-BUILDING-B01/B1.\nInvalid Setup - 125, 41\n'Layout failed - Invalid setup of /CBLP-P1502A-BUNDLE'\nBefore attempting to lay a cable bundle it must be first set it up, if this set up fails this error is returned.\nIn this example: the bundle /CBLP-P1502A-BUNDLE has an invalid setup to layout cannot proceed.\nRouting Status Mismatch - 125, 42\nBundle error - Cables in /CBLP-P1502A-BUNDLE do not have matching routing statuses'\nCables that are part of a bundle should always have matching routing statuses, for example: all be routed, all be laid, all be un-routed. If this is not the case, this is the error message that is returned.\nIn this example: the cables that are a part of the bundle /CBLP-P1502A-BUNDLE do not have matching routing statuses.\nUsed Tray Mismatch - 125, 43\n'Bundle error - Cables in /CBLP-P1502A-BUNDLE are not routed along the same trays\nCables that are a part of a bundle should be routed or routed and laid along the same rectangular cable trays. Should this rule be broken, this error is returned.\nIn this example: cables that are a part of the bundle /CBLP-P1502A-BUNDLE are not routed along the same trays.\nSpecification Mismatch - 125, 52\n'Routing bundle failed - Cables do not have the same SPREF'\nCables that are a part of a bundle are required to have the same specification, should this rule be broken this is error is returned.\nTrefoil Bad Cable Number - 125, 56\n'Routing bundle failed - TREFOIL bundle must have 3 cables of type CONDUCTOR'\nA bundle that is of type TREFOIL must have 3 cables of type CONDUCTOR so that the shape of the bundle can be created correctly. Should this rule be broken this error is returned.\nTrefoil Conductors Not Touching - 125, 57\n'Routing bundle failed - TREFOIL bundle must have 3 cables of type CONDUCTOR with CABLE TOUCHING TRUE'\nA bundle that is of type TREFOIL must have 3 cables of type CONDUCTOR and these CONDUCTORS must have CABLE TOUCHING TRUE so that the shape of the bundle can be created correctly. Should this rule be broken this error is returned.\nError\nDescription\n125, 26 - No Space\n'Layout failed - Insufficient space in branch /CWAY-POWER02-BUILDING-B01/B1 to lay /CBLP-B01-AHU-001-01'\nThis error is displayed when trying to lay a cable in insufficient space within a 'routing volume'.\nIn this example: there is not enough space on the branch /CWAY-POWER02-BUILDING-B01/B1 to lay cable /CBLP-B01-AHU-001-01.\n125, 27 - Invalid Radius\nLayout failed - Radius of /CBLP-B01-AHU-001-01 in branch /CWAY-POWER02-BUILDING-B01/B1 would be less than minimum bend radius'\nThis error is displayed when trying to lay a cable, in the only place available and as a result causes the cable\u2019s bend radius to be smaller than the minimum.\nIn this example: the radius of cable /CBLP-B01-AHU-001-01 when being laid on the branch /CWAY-POWER02-BUILDING-B01/B1 causes the bend radius to be less than the cables minimum bend radius.\n125, 28 - Invalid Element\n'Layout failed - Element /EQUI-B01-AHU-02-001 is not a routing object'\nThis error is displayed when trying to perform layout on an element that is not of the correct type.\nIn this example: the element /EQUI-B01-AHU-02-001 which is an Equipment, is not of the correct type to perform layout on.\n125, 29 - Maxlay Reached - 125, 29\n'Layout failed - Exceeded maximum layers(3) in branch /CWAY-POWER02-BUILDING-B01/B1'\nThis error is displayed once the limit of layers on a tray is reached. (When multiple cables are stacked to fit them onto the tray (branches can be restricted to a certain number of layers).\nIn this example: to lay a cable we will have to exceed the maximum number of layers (which is 3), on the branch /CWAY-POWER02-BUILDING-B01/B1.\n125, 30 - Can Not Be Touching\n'Layout failed - /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 would be touching\u2019\nLaying cables have rules applied to them, one of these rules is that certain cables cannot touch.\nThis error is displayed when a cable touches another cable which has been be identified as prohibited.\nThe rule is applied when laying a cable or verifying existing laid cables.\nIn this example: cables /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 would be touching, producing an invalid layout.\n125, 31 - Can Not Stack Bigger Cable\n'Layout failed - Can not put bigger object /CBLP-B01-AHU-001-01 on top of smaller object /CBLP-B01-AHU-001-02'\nThis error is displayed when larger cables are stacked on top of smaller cables. The rule is applied when laying a cable or verifying existing laid cables.\nIn this example: the larger cable /CBLP-B01-AHU-001-01 cannot be placed on top of the smaller cable /CBLP-B01-AHU-001-02.\n125, 32 - Layer Not Aligned\n'Layout failed - /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 are not layered correctly'\nThis error is displayed when stack cable\u2019s centres are not aligned.\nThe rule is applied after laying a cable, or verifying existing laid cables.\nIn this example: cables /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 are not layered correctly.\n125, 33 - Not Tried\n'Layout failed - Layout process could not begin\u2019\nThis error is displayed when the layout process is unable to begin.\n125, 34 - First Layer Not At Bottom\n'Layout failed - /CBLP-B01-AHU-001-01 is not at bottom in branch /CWAY-POWER02-BUILDING-B01/B1'\nThis error is displayed when laying cables, the first layer is not on the bottom of the routing volume.\nIn this example: the layer which cable /CBLP-B01-AHU-001-01 has been laid on is not at the bottom of the branch /CWAY-POWER02-BUILDING-B01/B1.\n125. 35 - Collision\n'Layout failed - /CBLP-B01-AHU-001-01 collides with /CBLP-B01-AHU-001-02'\n\nThis error is displayed when cables collide with one another. The rule is applied after laying a cable or verifying existing laid cables.\nIn this example: the cable /CBLP-B01-AHU-001-01 collides with cable /CBLP-B01-AHU-001-02.\nSegment Not Found - 125, 36\n'Layout failed - Branch /CWAY-POWER02-BUILDING-B01/B1 does not have POWER segment to put /CBLP-B01-AHU-001-01 in'\nIdeally when laying cables in a segregated branch (a branch with multiple ICLASS segments) the cables are placed in the correct segments.\nThis error is displayed when a segment on the branch that matches the cables ICLASS cannot be found.\nIn this example: the branch /CWAY-POWER02-BUILDING-B01/B1 does not have a POWER ICLASS segment to place the cable /CBLP-B01-AHU-001-01 in.\nWrong Segment - 125, 37\n'Layout failed - /CBLP-B01-AHU-001-01 is not in correct segment at /CWAY-POWER02-BUILDING-B01/B1'\nWhile laying cables and verifying existing laid cables we need to check that the cable is laid in the correct segment of a segregated branch. This error is displayed is this is not the case.\nIn this example: the cable /CBLP-B01-AHU-001-01 is not in the correct segment on the branch /CWAY-POWER02-BUILDING-B01/B1.\nStacking Not Allowed - 125, 39\n'Layout failed - Not allowed to stack /CBLP-B01-AHU-001-01'\nWhile laying cables and verifying existing laid cables we need to check that the cable has been identified as stack able.\nFor example checking the cable itself is allowed to touch other cables, as well as the cables it touches are also allowed to touch other cables. Additionally we need to ensure that there is a cable underneath the cable we are attempting to stack, and that nothing is already stacked there.\nShould any of the statements be untrue then this error that is returned.\nIn this example: the cable /CBLP-B01-AHU-001-01 is not allowed to stack.\nNot Tried Invalid Layout - 125, 38\n'Layout failed - Layout could not begin because /CBLP-B01-AHU-001-01 has invalid layout at /CWAY-POWER02-BUILDING-B01/B1'\nBefore attempting to lay a cable we must first ensure that the branches have a valid layout. Should a branch be found with an invalid layout, this is the error that is returned.\nIn this example: layout could not begin because the cable /CBLP-B01-AHU-001-01 has an invalid layout on the branch /CWAY-POWER02-BUILDING-B01/B1.\nInvalid Setup - 125, 41\n'Layout failed - Invalid setup of /CBLP-P1502A-BUNDLE'\nBefore attempting to lay a cable bundle it must be first set it up, if this set up fails this error is returned.\nIn this example: the bundle /CBLP-P1502A-BUNDLE has an invalid setup to layout cannot proceed.\nRouting Status Mismatch - 125, 42\nBundle error - Cables in /CBLP-P1502A-BUNDLE do not have matching routing statuses'\nCables that are part of a bundle should always have matching routing statuses, for example: all be routed, all be laid, all be un-routed. If this is not the case, this is the error message that is returned.\nIn this example: the cables that are a part of the bundle /CBLP-P1502A-BUNDLE do not have matching routing statuses.\nUsed Tray Mismatch - 125, 43\n'Bundle error - Cables in /CBLP-P1502A-BUNDLE are not routed along the same trays\nCables that are a part of a bundle should be routed or routed and laid along the same rectangular cable trays. Should this rule be broken, this error is returned.\nIn this example: cables that are a part of the bundle /CBLP-P1502A-BUNDLE are not routed along the same trays.\nSpecification Mismatch - 125, 52\n'Routing bundle failed - Cables do not have the same SPREF'\nCables that are a part of a bundle are required to have the same specification, should this rule be broken this is error is returned.\nTrefoil Bad Cable Number - 125, 56\n'Routing bundle failed - TREFOIL bundle must have 3 cables of type CONDUCTOR'\nA bundle that is of type TREFOIL must have 3 cables of type CONDUCTOR so that the shape of the bundle can be created correctly. Should this rule be broken this error is returned.\nTrefoil Conductors Not Touching - 125, 57\n'Routing bundle failed - TREFOIL bundle must have 3 cables of type CONDUCTOR with CABLE TOUCHING TRUE'\nA bundle that is of type TREFOIL must have 3 cables of type CONDUCTOR and these CONDUCTORS must have CABLE TOUCHING TRUE so that the shape of the bundle can be created correctly. Should this rule be broken this error is returned.\nError\nDescription\n125, 26 - No Space\n'Layout failed - Insufficient space in branch /CWAY-POWER02-BUILDING-B01/B1 to lay /CBLP-B01-AHU-001-01'\nThis error is displayed when trying to lay a cable in insufficient space within a 'routing volume'.\nIn this example: there is not enough space on the branch /CWAY-POWER02-BUILDING-B01/B1 to lay cable /CBLP-B01-AHU-001-01.\n125, 27 - Invalid Radius\nLayout failed - Radius of /CBLP-B01-AHU-001-01 in branch /CWAY-POWER02-BUILDING-B01/B1 would be less than minimum bend radius'\nThis error is displayed when trying to lay a cable, in the only place available and as a result causes the cable\u2019s bend radius to be smaller than the minimum.\nIn this example: the radius of cable /CBLP-B01-AHU-001-01 when being laid on the branch /CWAY-POWER02-BUILDING-B01/B1 causes the bend radius to be less than the cables minimum bend radius.\n125, 28 - Invalid Element\n'Layout failed - Element /EQUI-B01-AHU-02-001 is not a routing object'\nThis error is displayed when trying to perform layout on an element that is not of the correct type.\nIn this example: the element /EQUI-B01-AHU-02-001 which is an Equipment, is not of the correct type to perform layout on.\n125, 29 - Maxlay Reached - 125, 29\n'Layout failed - Exceeded maximum layers(3) in branch /CWAY-POWER02-BUILDING-B01/B1'\nThis error is displayed once the limit of layers on a tray is reached. (When multiple cables are stacked to fit them onto the tray (branches can be restricted to a certain number of layers).\nIn this example: to lay a cable we will have to exceed the maximum number of layers (which is 3), on the branch /CWAY-POWER02-BUILDING-B01/B1.\n125, 30 - Can Not Be Touching\n'Layout failed - /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 would be touching\u2019\nLaying cables have rules applied to them, one of these rules is that certain cables cannot touch.\nThis error is displayed when a cable touches another cable which has been be identified as prohibited.\nThe rule is applied when laying a cable or verifying existing laid cables.\nIn this example: cables /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 would be touching, producing an invalid layout.\n125, 31 - Can Not Stack Bigger Cable\n'Layout failed - Can not put bigger object /CBLP-B01-AHU-001-01 on top of smaller object /CBLP-B01-AHU-001-02'\nThis error is displayed when larger cables are stacked on top of smaller cables. The rule is applied when laying a cable or verifying existing laid cables.\nIn this example: the larger cable /CBLP-B01-AHU-001-01 cannot be placed on top of the smaller cable /CBLP-B01-AHU-001-02.\n125, 32 - Layer Not Aligned\n'Layout failed - /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 are not layered correctly'\nThis error is displayed when stack cable\u2019s centres are not aligned.\nThe rule is applied after laying a cable, or verifying existing laid cables.\nIn this example: cables /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 are not layered correctly.\n125, 33 - Not Tried\n'Layout failed - Layout process could not begin\u2019\nThis error is displayed when the layout process is unable to begin.\n125, 34 - First Layer Not At Bottom\n'Layout failed - /CBLP-B01-AHU-001-01 is not at bottom in branch /CWAY-POWER02-BUILDING-B01/B1'\nThis error is displayed when laying cables, the first layer is not on the bottom of the routing volume.\nIn this example: the layer which cable /CBLP-B01-AHU-001-01 has been laid on is not at the bottom of the branch /CWAY-POWER02-BUILDING-B01/B1.\n125. 35 - Collision\n'Layout failed - /CBLP-B01-AHU-001-01 collides with /CBLP-B01-AHU-001-02'\nThis error is displayed when cables collide with one another. The rule is applied after laying a cable or verifying existing laid cables.\nIn this example: the cable /CBLP-B01-AHU-001-01 collides with cable /CBLP-B01-AHU-001-02.\nSegment Not Found - 125, 36\n'Layout failed - Branch /CWAY-POWER02-BUILDING-B01/B1 does not have POWER segment to put /CBLP-B01-AHU-001-01 in'\nIdeally when laying cables in a segregated branch (a branch with multiple ICLASS segments) the cables are placed in the correct segments.\nThis error is displayed when a segment on the branch that matches the cables ICLASS cannot be found.\nIn this example: the branch /CWAY-POWER02-BUILDING-B01/B1 does not have a POWER ICLASS segment to place the cable /CBLP-B01-AHU-001-01 in.\nWrong Segment - 125, 37\n'Layout failed - /CBLP-B01-AHU-001-01 is not in correct segment at /CWAY-POWER02-BUILDING-B01/B1'\nWhile laying cables and verifying existing laid cables we need to check that the cable is laid in the correct segment of a segregated branch. This error is displayed is this is not the case.\nIn this example: the cable /CBLP-B01-AHU-001-01 is not in the correct segment on the branch /CWAY-POWER02-BUILDING-B01/B1.\nStacking Not Allowed - 125, 39\n'Layout failed - Not allowed to stack /CBLP-B01-AHU-001-01'\nWhile laying cables and verifying existing laid cables we need to check that the cable has been identified as stack able.\nFor example checking the cable itself is allowed to touch other cables, as well as the cables it touches are also allowed to touch other cables. Additionally we need to ensure that there is a cable underneath the cable we are attempting to stack, and that nothing is already stacked there.\nShould any of the statements be untrue then this error that is returned.\nIn this example: the cable /CBLP-B01-AHU-001-01 is not allowed to stack.\nNot Tried Invalid Layout - 125, 38\n'Layout failed - Layout could not begin because /CBLP-B01-AHU-001-01 has invalid layout at /CWAY-POWER02-BUILDING-B01/B1'\nBefore attempting to lay a cable we must first ensure that the branches have a valid layout. Should a branch be found with an invalid layout, this is the error that is returned.\nIn this example: layout could not begin because the cable /CBLP-B01-AHU-001-01 has an invalid layout on the branch /CWAY-POWER02-BUILDING-B01/B1.\nInvalid Setup - 125, 41\n'Layout failed - Invalid setup of /CBLP-P1502A-BUNDLE'\nBefore attempting to lay a cable bundle it must be first set it up, if this set up fails this error is returned.\nIn this example: the bundle /CBLP-P1502A-BUNDLE has an invalid setup to layout cannot proceed.\nRouting Status Mismatch - 125, 42\nBundle error - Cables in /CBLP-P1502A-BUNDLE do not have matching routing statuses'\nCables that are part of a bundle should always have matching routing statuses, for example: all be routed, all be laid, all be un-routed. If this is not the case, this is the error message that is returned.\nIn this example: the cables that are a part of the bundle /CBLP-P1502A-BUNDLE do not have matching routing statuses.\nUsed Tray Mismatch - 125, 43\n'Bundle error - Cables in /CBLP-P1502A-BUNDLE are not routed along the same trays\nCables that are a part of a bundle should be routed or routed and laid along the same rectangular cable trays. Should this rule be broken, this error is returned.\nIn this example: cables that are a part of the bundle /CBLP-P1502A-BUNDLE are not routed along the same trays.\nSpecification Mismatch - 125, 52\n'Routing bundle failed - Cables do not have the same SPREF'\nCables that are a part of a bundle are required to have the same specification, should this rule be broken this is error is returned.\nTrefoil Bad Cable Number - 125, 56\n'Routing bundle failed - TREFOIL bundle must have 3 cables of type CONDUCTOR'\nA bundle that is of type TREFOIL must have 3 cables of type CONDUCTOR so that the shape of the bundle can be created correctly. Should this rule be broken this error is returned.\nTrefoil Conductors Not Touching - 125, 57\n'Routing bundle failed - TREFOIL bundle must have 3 cables of type CONDUCTOR with CABLE TOUCHING TRUE'\nA bundle that is of type TREFOIL must have 3 cables of type CONDUCTOR and these CONDUCTORS must have CABLE TOUCHING TRUE so that the shape of the bundle can be created correctly. Should this rule be broken this error is returned.\n\n\n\nError\nDescription\n125, 26 - No Space\n'Layout failed - Insufficient space in branch /CWAY-POWER02-BUILDING-B01/B1 to lay /CBLP-B01-AHU-001-01'\n125, 27 - Invalid Radius\nLayout failed - Radius of /CBLP-B01-AHU-001-01 in branch /CWAY-POWER02-BUILDING-B01/B1 would be less than minimum bend radius'\n125, 28 - Invalid Element\n'Layout failed - Element /EQUI-B01-AHU-02-001 is not a routing object'\n125, 29 - Maxlay Reached - 125, 29\n'Layout failed - Exceeded maximum layers(3) in branch /CWAY-POWER02-BUILDING-B01/B1'\n125, 30 - Can Not Be Touching\n'Layout failed - /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 would be touching\u2019\n125, 31 - Can Not Stack Bigger Cable\n'Layout failed - Can not put bigger object /CBLP-B01-AHU-001-01 on top of smaller object /CBLP-B01-AHU-001-02'\n125, 32 - Layer Not Aligned\n'Layout failed - /CBLP-B01-AHU-001-01 and /CBLP-B01-AHU-001-02 are not layered correctly'\n125, 33 - Not Tried\n'Layout failed - Layout process could not begin\u2019\n125, 34 - First Layer Not At Bottom\n'Layout failed - /CBLP-B01-AHU-001-01 is not at bottom in branch /CWAY-POWER02-BUILDING-B01/B1'\n125. 35 - Collision\n'Layout failed - /CBLP-B01-AHU-001-01 collides with /CBLP-B01-AHU-001-02'\nSegment Not Found - 125, 36\n'Layout failed - Branch /CWAY-POWER02-BUILDING-B01/B1 does not have POWER segment to put /CBLP-B01-AHU-001-01 in'\nWrong Segment - 125, 37\n'Layout failed - /CBLP-B01-AHU-001-01 is not in correct segment at /CWAY-POWER02-BUILDING-B01/B1'\nStacking Not Allowed - 125, 39\n'Layout failed - Not allowed to stack /CBLP-B01-AHU-001-01'\nNot Tried Invalid Layout - 125, 38\n'Layout failed - Layout could not begin because /CBLP-B01-AHU-001-01 has invalid layout at /CWAY-POWER02-BUILDING-B01/B1'\nInvalid Setup - 125, 41\n'Layout failed - Invalid setup of /CBLP-P1502A-BUNDLE'\nRouting Status Mismatch - 125, 42\nBundle error - Cables in /CBLP-P1502A-BUNDLE do not have matching routing statuses'\nUsed Tray Mismatch - 125, 43\n'Bundle error - Cables in /CBLP-P1502A-BUNDLE are not routed along the same trays\nSpecification Mismatch - 125, 52\n'Routing bundle failed - Cables do not have the same SPREF'\nTrefoil Bad Cable Number - 125, 56\n'Routing bundle failed - TREFOIL bundle must have 3 cables of type CONDUCTOR'\nTrefoil Conductors Not Touching - 125, 57\n'Routing bundle failed - TREFOIL bundle must have 3 cables of type CONDUCTOR with CABLE TOUCHING TRUE'"}
{"Headers": "Cable Trays", "Content": "The Cable Trays application is supplied as part of AVEVA E3D Design suite. The application is a powerful suite of facilities designed by cable tray engineers, for creating, analyzing and documenting logically interconnected cable tray networks.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAVEVA E3D Design"}
{"Headers": "Assumptions", "Content": "The Cable Trays User Guide has been written for users familiar with cable tray design practices, who may or may not have prior knowledge of AVEVA E3D Design.\nIt is assumed that:\nYou has a valid AVEVA E3D Design licence and the software has been installed.\nYou know how to launch the Design module.\nYou are familiar with the basic Graphical User Interface (GUI) features as described in the AVEVA document Getting Started with Plant.\nYou are familiar with cable tray design practices.\nYou has a valid AVEVA E3D Design licence and the software has been installed.\nYou has a valid AVEVA E3D Design licence and the software has been installed.\nYou know how to launch the Design module.\nYou know how to launch the Design module.\nYou are familiar with the basic Graphical User Interface (GUI) features as described in the AVEVA document Getting Started with Plant.\nYou are familiar with the basic Graphical User Interface (GUI) features as described in the AVEVA document Getting Started with Plant.\nYou are familiar with cable tray design practices.\nYou are familiar with cable tray design practices.\n\n\n\nAVEVA E3D Design\nAVEVA E3D Design\nDesign\nGetting Started with Plant"}
{"Headers": "Cable Tray Application", "Content": "To enter the cable trays application from the Design ribbon, from the Quick Access Toolbar, select Cable Tray from the application drop-down list.\nNote:\nThe Cable Tray application can be entered direct from the Login screen. Refer to Getting Started with Plant for further information.\n\n\n\nDesign\nCable Tray\nNote\n:"}
{"Headers": "Design Features", "Content": "The Cable Tray application allows you to build up and detail complex cable tray networks by selecting components from the Cable Tray Catalog.\nUsing standard default settings, a conceptual layout can be created and analyzed rapidly, leaving the design details to a later post-approved stage.\n\n\n"}
{"Headers": "Hierarchy", "Content": "All database elements are owned by other elements, therefore elements must be created in a strict order, refer to the figure below for further information.\nThe following database elements are common to all Design disciplines:\nfor further information on the generic hierarchical structure and the design database, refer to Getting Started with Plant.\n\nWorld\nSite\nZone\nWorld\nWorld\nSite\nSite\nZone\nZone\n\n\n\nDesign"}
{"Headers": "Cable Tray Specific Hierarchy", "Content": "Below the zone level in the Cable Tray application, the cable tray specific elements are:\n\n\n"}
{"Headers": "Pipe (PIPE)", "Content": "The Pipe (PIPE) element(s) are administrative and can own a number of branches with a common pipe specification and have any number of ends. For further information, refer to Pipe Element.\n\n\n\nPipe Element\nPipe Element"}
{"Headers": "Branch (BRAN)", "Content": "The Branch (BRAN) element(s) own a section of pipe (made up from cable tray components) with a known head and tail. For further information, refer to Branch Element.\n\n\n\nBranch Element\nBranch Element"}
{"Headers": "Cable Tray Component", "Content": "The Cable Tray component element(s) are owned by Branch elements. These components dictate the shape and geometry of the cable tray. Cable tray components can run from the head to tail of the owning branch but can also be connected to other branches (for example - a tee component). For further information, refer to the figure below, and to Cable Tray Components.\n\nYou are not able to make any selections from the Cable Tray tab if the correct database hierarchy has not been configured beforehand. For example certain cable tray elements must reside below other elements in the database hierarchy (an overview of the database hierarchy is described in Hierarchy).\nIf a particular cable tray element cannot be created at the current position in the database hierarchy you receive an error message summarizing the problem, for example in the following window an error explains that the element you are attempting to create must be below a branch element.\n\n\n\n\nCable Tray Components\nHierarchy\nCable Tray Components\nHierarchy"}
{"Headers": "Pipe Element", "Content": "Referring to the Cable Tray Hierarchy, the first task that you should perform using the Cable Tray tab is to create a Pipe Element in the Design Database.\nBefore creating a Pipe Element the correct Database elements should already be present in the Model Explorer, for example, a World, Site and Zone should exist. If this is not the case, refer to Getting Started with Plant for a detailed explanation of creating these standard elements.\n\n\n\n\nHierarchy\nHierarchy\nPipe Element\nModel\nExplorer\nGetting Started with Plant"}
{"Headers": "Create Cable Tray", "Content": "To create a new Pipe element make sure the correct Zone element is selected in the Model Explorer.\nTo create a Pipe element, on the Cable Tray tab, in the Create group, click Cable Tray to display the Create Cable Tray Main window.\n\nIn the Name box, input the name of the new Pipe element.\nThe Wrt position of the new Pipe element within the Model Explorer displays by default.\n\n\n\nCable Tray\nCreate\nCable Tray\nCreate Cable Tray Main\nName\nWrt"}
{"Headers": "Cable Tray Specification", "Content": "To modify the cable tray specification, click Specifications to display the Default Specifications window.\n\nYou can choose from the list of cable tray specifications.\nClick OK to apply the selected specification to the cable tray or Cancel to discard any inputs and close the Default Specifications window. You are returned to the Create Cable Tray Main window.\nNote:\nAll cable tray components created below the branch use the Specification selected in the list. To use different specifications within a cable tray run, a new branch must be created at each point a different specification is used.\n\n\n\nSpecifications\nDefault Specifications\nNote\n:\nSpecification\nOK\nCancel\nDefault Specifications\nCreate Cable Tray Main"}
{"Headers": "Cable Tray Attributes", "Content": "To modify the cable tray attributes, click Attributes to display the Cable Tray Attributes window, refer to Database Management Reference Manual for further information.\n\nClick OK to save any changes or Cancel to discard any inputs and close the Cable Tray Attributes window. You are returned to the Create Cable Tray Main window.\nClick OK, to create a new Pipe and Branch element in the Model Explorer and display the Create Cable Tray Branch window, to define the branch, refer to Branch Element for further information.\n\nClick Cancel to discard any changes and close the Create Cable Tray Branch window.\n\n\n\nBranch Element\nAttributes\nCable Tray Attributes\nDatabase Management Reference Manual\nOK\nCancel\nCable Tray Attributes\nCreate Cable Tray Main\nOK\nCreate Cable Tray Branch\nBranch Element\nCancel\nCreate Cable Tray Branch"}
{"Headers": "Branch Element", "Content": "A branch is a section of cable tray made up from cable tray components with a known branch head or branch tail. You must define the position of the branch head (starting point) and branch tail (finishing point) by either explicitly entering the position or by the selection of cable tray components.\nThe Create Cable Tray Branch window displays by default when a new pipe element is created.\n\nThe Create Cable Tray Branch window allows you to define the name, specification and attributes of the branch under the pipe element.\n\nThe Name box is populated with a suggested Branch Name, you can accept the suggested Branch Name or input a new name for the Branch element.\nThe Wrt position of the new Pipe element within the Model Explorer displays by default.\n\n\n\nName\nWrt"}
{"Headers": "Branch Specification", "Content": "To modify the branch specification, click Specifications to display the Default Specifications window.\n\nYou can choose from the list of branch specifications.\nClick OK to apply the selected specification to the branch or Cancel to discard any inputs and close the Default Specifications window. You are returned to the Create Cable Tray Branch window.\nNote:\nAll branch components created below the branch use the Specification selected in the list. To use different specifications within a cable tray run, a new branch must be created at each point a different specification is used.\n\n\n\nSpecifications\nDefault Specifications\nNote\n:\nSpecification\nOK\nCancel\nDefault Specifications\nCreate Cable Tray Branch"}
{"Headers": "Branch Attributes", "Content": "To modify the cable tray attributes, click Attributes to display the Branch Attributes window. For further information, refer to Database Management Reference Manual.\n\nClick OK to save any changes or Cancel to discard any inputs and close the Branch Attributes window. You are returned to the Create Cable Tray Branch window.\nClick OK, the Model Explorer displays the Branch Name and the Branch at Explicit Position window displays by default, to position the branch. For further information, refer to Branch Head and Branch Tail Position.\n\nClick Cancel to discard any changes and close the Create Cable Tray Branch window.\n\n\n\nBranch Head and Branch Tail Position\nAttributes\nBranch Attributes\nDatabase Management Reference Manual\nOK\nCancel\nBranch Attributes\nCreate Cable Tray Branch\nOK\nBranch at Explicit Position\nBranch Head and Branch Tail Position\nCancel\nCreate Cable Tray Branch"}
{"Headers": "Branch Head and Branch Tail Position", "Content": "The Branch at Explicit Position window displays by default when a branch element is defined and added to the Model Explorer.\nThe Branch at Explicit Position window allows you to position the branch head and branch tail, set the branch width, branch direction and branch connection.\n\nTo define the branch head or branch tail, make sure the correct branch is highlighted in the Model Explorer and the correct branch name is shown at the top of the Branch at Explicit Position window.\nTo position the head or tail of the current branch, select Head or Tail from the drop-down list.\nPosition\nFormat\nSelect the position axis from the Position drop-down lists, choose from East/West, North/South and Up/Down. You can then input the explicit position values in the Position fields.\nWRT\nUse to define an element from which the coordinates are derived, refer to WRT for further information.\nPick\nYou are prompted to Pick Head Position (Distance[0] Snap: to position the branch head or Pick Tail Position (Distance[0] Snap: to position the branch tail in the 3D graphical view.\nOr use the functionality available from the Positioning window, refer to Positioning Control for further information.\nPositions the branch head or branch tail using a cursor pick in the 3D graphical view.\nOffset\nDisplays the Offset by functionality use to offset the branch head or the branch tail.\nNote:\nIf required, the axes all co-ordinates are interpreted with respect to must be set. Input dimensional values in the coordinates fields to define the position explicitly. Refer to Coordinates for further information.\nYou can then input the explicit offset values in the Offset fields.\nProperties\nWidth\nSets the branch width from the Width drop-down list.\nDirection\nInput a value in the field to define which direction the flow takes from the branch head or branch tail.\nConnection\nAn Open connection allows you to connect the branch head or branch tail to another branch.\nA Boxing connection terminates the branch head or branch tail, connection to another branch is not available.\nAttributes\nDisplays the Branch Attributes window. For further information, refer to Branch Attributes.\nPosition\n\nFormat\nSelect the position axis from the Position drop-down lists, choose from East/West, North/South and Up/Down. You can then input the explicit position values in the Position fields.\nWRT\nUse to define an element from which the coordinates are derived, refer to WRT for further information.\nPick\nYou are prompted to Pick Head Position (Distance[0] Snap: to position the branch head or Pick Tail Position (Distance[0] Snap: to position the branch tail in the 3D graphical view.\nOr use the functionality available from the Positioning window, refer to Positioning Control for further information.\nPositions the branch head or branch tail using a cursor pick in the 3D graphical view.\nOffset\nDisplays the Offset by functionality use to offset the branch head or the branch tail.\n\nYou can then input the explicit offset values in the Offset fields.\nProperties\n\nWidth\nSets the branch width from the Width drop-down list.\nDirection\nInput a value in the field to define which direction the flow takes from the branch head or branch tail.\nConnection\nAn Open connection allows you to connect the branch head or branch tail to another branch.\nA Boxing connection terminates the branch head or branch tail, connection to another branch is not available.\nAttributes\nDisplays the Branch Attributes window. For further information, refer to Branch Attributes.\nClick Apply to position the branch head or tail, Reset to discard any changes.\nThe branch consists of one piece of cable tray running in a straight line between the branch head and branch tail positions and displays as a line within the 3D graphical view, unless the branch head and branch tail are aligned along a common axis and have an equal bore size. The line indicates that the branch route is geometrically incorrect.\nOnce you have defined or selected the branch head and branch tail, the branch now consists of a single piece of cable tray running between the branch head and branch tail. The branch displays a dotted line, which means the branch route is geometrically incorrect.\nPosition\nFormat\nSelect the position axis from the Position drop-down lists, choose from East/West, North/South and Up/Down. You can then input the explicit position values in the Position fields.\nWRT\nUse to define an element from which the coordinates are derived, refer to WRT for further information.\nPick\nYou are prompted to Pick Head Position (Distance[0] Snap: to position the branch head or Pick Tail Position (Distance[0] Snap: to position the branch tail in the 3D graphical view.\nOr use the functionality available from the Positioning window, refer to Positioning Control for further information.\nPositions the branch head or branch tail using a cursor pick in the 3D graphical view.\nOffset\nDisplays the Offset by functionality use to offset the branch head or the branch tail.\nNote:\nIf required, the axes all co-ordinates are interpreted with respect to must be set. Input dimensional values in the coordinates fields to define the position explicitly. Refer to Coordinates for further information.\nYou can then input the explicit offset values in the Offset fields.\nProperties\nWidth\nSets the branch width from the Width drop-down list.\nDirection\nInput a value in the field to define which direction the flow takes from the branch head or branch tail.\nConnection\nAn Open connection allows you to connect the branch head or branch tail to another branch.\nA Boxing connection terminates the branch head or branch tail, connection to another branch is not available.\nAttributes\nDisplays the Branch Attributes window. For further information, refer to Branch Attributes.\nNote:\nIf required, the axes all co-ordinates are interpreted with respect to must be set. Input dimensional values in the coordinates fields to define the position explicitly.\nNote:\nIf required, the axes all co-ordinates are interpreted with respect to must be set. Input dimensional values in the coordinates fields to define the position explicitly. Refer to Coordinates for further information.\n\n\n\nBranch Attributes\nNote\n:\nHead\nTail\nPosition\nFormat\nPosition\nEast/West\nNorth/South\nUp/Down\nPosition\nWRT\nWRT\nPick\nPick Head Position (Distance[0] Snap:\nPick Tail Position (Distance[0] Snap:\nPositioning\nPositioning Control\nOffset\nOffset by\n\n\nNote\n:\nCoordinates\nOffset\nProperties\nWidth\nWidth\nDirection\nConnection\nBoxing\nAttributes\nBranch Attributes\nBranch Attributes\nApply\nReset"}
{"Headers": "Connect Branch", "Content": "The Connect Cable Tray Branch window allows you to connect the branch head or branch tail to an appropriate component (for example, a tee), or another branch.\nIf you are not at the branch level in the Model Explorer an error message displays summarizing the problem, for example in the following window an error explains that the element you are attempting to connect to is not at a branch.\n\nTo connect the branch head or branch tail, make sure the correct branch is highlighted in the Model Explorer, on the Cable Tray tab, in the Connect group, click Branch to display the Connect Cable Tray Branch window.\n\nThe Connect Cable Tray Branch window allows you to set the connection details of both the head and the tail of the selected branch, make sure the correct branch name is shown at the top of the Connect Cable Tray Branch window.\nTo connect the head or tail of the current branch to another branch or component, select Head or Tail from the drop-down list.\nIn the To drop-down list, you must choose from a list of available components or the head/tail of another branch to which the head/tail of the current branch is to be connected. You are required to identify the connection point of the existing cable tray component or branch to which the head/tail is to be connected.\nTee\nYou are prompted to Identify Tee in the 3D graphical view.\nAs two of the three ppoints available at the tee are already utilized, the Cable Tray application selects the free ppoint and connects the branch head or branch tail to that point.\nMultiway\nYou are prompted to Identify design ppoint in the 3D graphical view.\nYou must select the ppoint to connect to as multiple ppoints may be available.\nBranch Head\nYou are prompted to Identify BRAN in the 3D graphical view.\nYou must select the branch, or any part of the branch, to connect to.\nBranch Tail\nYou are prompted to Identify BRAN in the 3D graphical view.\nYou must select the branch, or any part of the branch, to connect to.\nFirst Member\nConnects the branch head or branch tail to the first member of the branch.\nLast Member\nConnects the branch head or branch tail to the last member of the branch.\nName\nDisplays the Name window, refer to Connect Branch to a Named Element for further information.\nCE\nSets the currently selected branch, from the Model Explorer or 3D graphical view, as the working branch.\nTee\nYou are prompted to Identify Tee in the 3D graphical view.\nAs two of the three ppoints available at the tee are already utilized, the Cable Tray application selects the free ppoint and connects the branch head or branch tail to that point.\nMultiway\nYou are prompted to Identify design ppoint in the 3D graphical view.\nYou must select the ppoint to connect to as multiple ppoints may be available.\nBranch Head\nYou are prompted to Identify BRAN in the 3D graphical view.\nYou must select the branch, or any part of the branch, to connect to.\nBranch Tail\nYou are prompted to Identify BRAN in the 3D graphical view.\nYou must select the branch, or any part of the branch, to connect to.\nFirst Member\nConnects the branch head or branch tail to the first member of the branch.\nLast Member\nConnects the branch head or branch tail to the last member of the branch.\nName\nDisplays the Name window, refer to Connect Branch to a Named Element for further information.\nCE\nSets the currently selected branch, from the Model Explorer or 3D graphical view, as the working branch.\nClick Apply, to connect the current branch, Reset to discard any changes or Dismiss to close the Connect Branch window.\nTee\nYou are prompted to Identify Tee in the 3D graphical view.\nAs two of the three ppoints available at the tee are already utilized, the Cable Tray application selects the free ppoint and connects the branch head or branch tail to that point.\nMultiway\nYou are prompted to Identify design ppoint in the 3D graphical view.\nYou must select the ppoint to connect to as multiple ppoints may be available.\nBranch Head\nYou are prompted to Identify BRAN in the 3D graphical view.\nYou must select the branch, or any part of the branch, to connect to.\nBranch Tail\nYou are prompted to Identify BRAN in the 3D graphical view.\nYou must select the branch, or any part of the branch, to connect to.\nFirst Member\nConnects the branch head or branch tail to the first member of the branch.\nLast Member\nConnects the branch head or branch tail to the last member of the branch.\nName\nDisplays the Name window, refer to Connect Branch to a Named Element for further information.\nCE\nSets the currently selected branch, from the Model Explorer or 3D graphical view, as the working branch.\n\n\n\nConnect Branch to a Named Element\nConnect Cable Tray Branch\nCable Tray\nConnect\nBranch\nConnect Cable Tray Branch\nConnect Cable Tray Branch\nConnect Cable Tray Branch\nHead\nTail\nTo\nTee\nIdentify Tee\nMultiway\nIdentify design ppoint\nBranch Head\nIdentify BRAN\nBranch Tail\nIdentify BRAN\nFirst Member\nLast Member\nName\nName\nConnect Branch to a Named Element\nCE\nApply\nReset\nDismiss\nConnect Branch"}
{"Headers": "Connect Branch to a Named Element", "Content": "The Name window allows you to connect a branch to a named element.\nSelect Name from the To drop-down list of the Connect Cable Tray Branch window to display the Name window.\n\nClick OK to identify the element and close the Name window, click Cancel to close the Name window.\nThe name of the element to connect to displays adjacent to the To drop-down list of the Connect Cable Tray Branch window. Click Apply to display the Confirm window.\n\nClick Yes to select the head of the named element as the connection point or No to select the tail of the named element as the connection point and close the Confirm window.\n\n\n\nName\nName\nTo\nConnect Cable Tray Branch\nName\nOK\nCancel\nName\nTo\nConnect Cable Tray Branch\nApply\nConfirm\nYes\nNo\nConfirm"}
{"Headers": "Create Branch", "Content": "Creates a new branch and displays the Create Cable Tray Branch window.\nFor further information, refer to Branch Element.\n\n\n\nBranch Element\nCreate Cable Tray Branch\nBranch Element"}
{"Headers": "Cable Tray Components", "Content": "Cable tray components are single elements used together to create a cable tray design.\nIt is usual for you to build up the cable tray design by adding components sequentially, starting at the branch head and positioning and orientating each component as they proceed until the branch tail is reached. You can insert a component into an existing sequence by navigating to the component immediately before the required location and then creating the new component.\nThere are many different combinations of cable trays that can be created, because of this the Cable Tray application uses a common layout for windows that are presented to you. The information can be applied to the same processes that are used to create all other types of cable tray components.\n\n\n"}
{"Headers": "Create Component", "Content": "Referring to the Cable Tray Hierarchy, a Cable Tray component must reside below an existing Branch element. For a more detailed explanation of creating a cable tray branch, refer to Branch Element.\n\nIf you are not at the Branch level in the Model Explorer an error message displays summarizing the problem, for example in the following window an error explains that the element you are attempting to create must reside below a branch or component element.\n\nThe Cable Tray Components window allows you to create and modify the components of a branch.\nOn the Cable Tray tab, in the Create group, click Components to display the Cable Tray Components window.\n\nAlthough a specification was selected earlier you can select a different specification for the component. The default specification is initially selected but you can select an alternative specification from the Cable Tray drop-down list.\nIf the selected specification does not match the branch specification when the component is created, you are prompted to confirm if the component specification should revert back to the branch specification.\n\nClick Yes to revert back to the branch specification or click No to create a component using an alternative specification and close the Confirm window.\n\nForwards\nCreates the component in the Head to Tail direction.\nBackwards\nCreates the component in the Tail to Head direction.\nForwards\nCreates the component in the Head to Tail direction.\nBackwards\nCreates the component in the Tail to Head direction.\nThe Cable Tray Components window displays all the component types available from the catalogue under the current piping specification set at the Pipe and Branch level.\n\nFixed Tray\nSelect Fixed Tray as component type .\nBend\nSelects a Bend as the component type to be inserted.\nRiser\nSelects a Riser as the component type to be inserted.\nReducer\nSelects a Reducer as the component type to be inserted.\nTee\nSelects a Tee as the component type to be inserted.\nCross\nSelects a Cross as the component type to be inserted.\nFixed Tray\nSelect Fixed Tray as component type .\nBend\nSelects a Bend as the component type to be inserted.\nRiser\nSelects a Riser as the component type to be inserted.\nReducer\nSelects a Reducer as the component type to be inserted.\nTee\nSelects a Tee as the component type to be inserted.\nCross\nSelects a Cross as the component type to be inserted.\n\nSelect the Default check box to apply the default selection type automatically for each component.\nSelect the Auto Conn check box to position, orientate and connect the component to the preceding component automatically.\nClick Re-select to modify an existing component using the CHOOSE window. The CHOOSE window displays changes for each component type. For further information, refer to Component Specific Information.\nThe Cable Tray Components window allows you to specify the position of the component.\n\nThro Cursor\nYou are prompted to Enter a 3-d position in the 3D graphical view.\nPositions a component using a cursor pick in the 3D graphical view.\nThro ID Cursor\nYou are prompted to Identify element in the 3D graphical view.\nPositions a component using an element pick in the 3D graphical view.\nThro Point\nYou are prompted to Identify design ppoint in the 3D graphical view.\nPositions a component using a ppoint pick in the 3D graphical view.\nThro Next\nAligns a component through the next component of the branch assembly.\nThro Tail\nAligns a component through the tail of the branch assembly.\nThro Previous\nAligns a component through the previous component of the branch assembly.\nThro Head\nAligns a component through the head of the branch assembly.\nConnect\nConnects a component to the previous component in the branch assembly.\nThro Cursor\nYou are prompted to Enter a 3-d position in the 3D graphical view.\nPositions a component using a cursor pick in the 3D graphical view.\nThro ID Cursor\nYou are prompted to Identify element in the 3D graphical view.\nPositions a component using an element pick in the 3D graphical view.\nThro Point\nYou are prompted to Identify design ppoint in the 3D graphical view.\nPositions a component using a ppoint pick in the 3D graphical view.\nThro Next\nAligns a component through the next component of the branch assembly.\nThro Tail\nAligns a component through the tail of the branch assembly.\nThro Previous\nAligns a component through the previous component of the branch assembly.\nThro Head\nAligns a component through the head of the branch assembly.\nConnect\nConnects a component to the previous component in the branch assembly.\n\nIn the Distance text field input a value to move a component a specified distance from the previous component.\nClick Create to create a component using the CHOOSE window. The CHOOSE window display changes for each component type. For further information, refer to Component Specific Information. Click CANCEL to discard any changes and close the Cable Tray Components window.\nForwards\nCreates the component in the Head to Tail direction.\nBackwards\nCreates the component in the Tail to Head direction.\nFixed Tray\nSelect Fixed Tray as component type .\nBend\nSelects a Bend as the component type to be inserted.\nRiser\nSelects a Riser as the component type to be inserted.\nReducer\nSelects a Reducer as the component type to be inserted.\nTee\nSelects a Tee as the component type to be inserted.\nCross\nSelects a Cross as the component type to be inserted.\nThro Cursor\nYou are prompted to Enter a 3-d position in the 3D graphical view.\nPositions a component using a cursor pick in the 3D graphical view.\nThro ID Cursor\nYou are prompted to Identify element in the 3D graphical view.\nPositions a component using an element pick in the 3D graphical view.\nThro Point\nYou are prompted to Identify design ppoint in the 3D graphical view.\nPositions a component using a ppoint pick in the 3D graphical view.\nThro Next\nAligns a component through the next component of the branch assembly.\nThro Tail\nAligns a component through the tail of the branch assembly.\nThro Previous\nAligns a component through the previous component of the branch assembly.\nThro Head\nAligns a component through the head of the branch assembly.\nConnect\nConnects a component to the previous component in the branch assembly.\n\n\n\nHierarchy\nBranch Element\nComponent Specific Information\nComponent Specific Information\nHierarchy\nBranch Element\nCable Tray Components\nCable Tray\nCreate\nComponents\nCable Tray Components\nCable Tray\nYes\nNo\nConfirm\nForwards\nBackwards\nCable Tray Components\nFixed Tray\nBend\nRiser\nReducer\nTee\nCross\nDefault\nAuto Conn\nRe-select\nCHOOSE\nCHOOSE\nComponent Specific Information\nCable Tray Components\nThro Cursor\nEnter a 3-d position\nThro ID Cursor\nIdentify element\nThro Point\nIdentify design ppoint\nThro Next\nThro Tail\nThro Previous\nThro Head\nConnect\nDistance\nCreate\nCHOOSE\nCHOOSE\nComponent Specific Information\nCANCEL\nCable Tray Components"}
{"Headers": "Component Specific Information", "Content": "Component specific information displays for each of the available component types.\n\n\n"}
{"Headers": "Fixed Tray", "Content": "The CHOOSE FTUB window displays when you select a Fixed Tray to be created.\n\nThe Setting, Current bore, Specification and Unforced Connections status display at the top of the CHOOSE FTUB window.\nSelect a component from the list of available components sorted by STYP.\nClick OK to create the component or CANCEL to discard any changes and close the CHOOSE FTUB window.\n\n\n\nCHOOSE FTUB\nCHOOSE FTUB\nOK\nCANCEL\nCHOOSE FTUB"}
{"Headers": "Bend", "Content": "The CHOOSE BEND window displays when you select a Bend to be created.\n\nThe Setting, Current bore, Specification and Unforced Connections status display at the top of the CHOOSE BEND window.\nSelect a component from the list of available components sorted by ANGL, STYP and RADI.\nClick OK to create the component or CANCEL to discard any changes and close the CHOOSE BEND window.\n\n\n\nCHOOSE BEND\nCHOOSE BEND\nOK\nCANCEL\nCHOOSE BEND"}
{"Headers": "Riser", "Content": "The CHOOSE ELBO window displays when you select a Riser to be created.\n\nThe Setting, Current bore, Specification and Unforced Connections status display at the top of the CHOOSE ELBO window.\nSelect a component from the list of available components sorted by STYP, ANGl and RADI.\nClick OK to create the component or CANCEL to discard any changes and close the CHOOSE ELBO window.\n\n\n\nCHOOSE ELBO\nCHOOSE ELBO\nOK\nCANCEL\nCHOOSE ELBO"}
{"Headers": "Tee", "Content": "The CHOOSE TEE window displays when you select a Tee to be created.\n\nThe Setting, Current bore, Specification and Unforced Connections status display at the top of the CHOOSE TEE window.\nSelect a component from the list of available components sorted by PBOR3, and RADI.\nClick OK to create the component or CANCEL to discard any changes and close the CHOOSE TEE window.\n\n\n\nCHOOSE TEE\nCHOOSE TEE\nOK\nCANCEL\nCHOOSE TEE"}
{"Headers": "Cross", "Content": "The CHOOSE CROS window displays when you select a Cross to be created.\n\nThe Setting, Current bore, Specification and Unforced Connections status display at the top of the CHOOSE CROS window.\nSelect a component from the list of available components sorted by PBOR3, and STYP.\nClick OK to create the component or CANCEL to discard any changes and close the CHOOSE CROS window.\n\n\n\nCHOOSE CROS\nCHOOSE CROS\nOK\nCANCEL\nCHOOSE CROS"}
{"Headers": "Reducer", "Content": "The CHOOSE REDU window displays when you select a Reducer to be created.\n\nThe Setting, Current bore, Specification and Unforced Connections status display at the top of the CHOOSE redu window.\nSelect a component from the list of available components sorted by PBOR1, and STYP.\nClick OK to create the component or CANCEL to discard any changes and close the CHOOSE REDU window.\n\n\n\nCHOOSE REDU\nCHOOSE redu\nOK\nCANCEL\nCHOOSE REDU"}
{"Headers": "Open Tray Direction", "Content": "When the first component of a branch or an unconnected component is created you must specify the open tray direction of the component, the Open Tray Direction window displays by default.\n\nThe component name and branch display at the top of the Open Tray Direction window.\nIn the Open Tray Direction box, input the direction of the new Cable Tray Element (the default direction is U (up)).\nClick OK to create the component or Cancel to discard any changes and close the Open Tray Direction window.\n\n\n\nOpen Tray Direction\nOpen Tray Direction\nOpen Tray Direction\nOK\nCancel\nOpen Tray Direction"}
{"Headers": "Route Cable Tray Components", "Content": "To continue routing, you must select the component from the chosen specification, then position and set orientation using the Model Editor, (refer to Editor for further information) or from the Cable Tray Components window.\n\nThe Cable Tray displays in the 3D graphical view:\n\n\n\n\nEditor\nEditor\nCable Tray Components"}
{"Headers": "Connect Component", "Content": "A cable tray component can be connected in such a way, so that it is orientated and positioned so that the p-arrive is directed towards and aligned with the p-leave of the previous piping component.\nNote:\nThe option checks that the components being connected have compatible connection types, unless Force connect is selected, refer to Auto Force Connect for further information.\n\n\n\nAuto Force Connect\nNote\n:\nAuto Force Connect"}
{"Headers": "Connect to Next Component", "Content": "To connect a component so that the p-leave is directed towards and aligned with the p\u2011arrive of the previous cable tray component, on the Cable Tray tab, in the Connect group, click Next.\n\n\n\nCable Tray\nConnect\nNext"}
{"Headers": "Connect to Previous Component", "Content": "To connect a component so that the p-arrive is directed towards and aligned with the p\u2011leave of the previous cable tray component, on the Cable Tray tab, in the Connect group, click Previous.\n\n\n\nCable Tray\nConnect\nPrevious"}
{"Headers": "Cable Tray Connection Reference", "Content": "When a multiway component is connected within a branch to another item (such as a tee, or the head or tail of another branch), the Connection Reference (CREF) attribute of the component identifies the connected item.\nTo disconnect the component, or connect it to a different item, on the Cable Tray tab, in the Connect group, click Connection Ref. to display the Connection Reference window.\n\nThe current connection displays in the Connection Reference window, click Unset to disconnect the current connection.\nYou can input an element to in the Connection Reference field.\nClick Apply to accept the change, Reset to remove all changes or Dismiss to close the Connection Reference window.\nNote:\nModification of the Connection Reference does not change the position or orientation of any components.\n\n\n\nCable Tray\nConnect\nConnection Ref.\nConnection Reference\nConnection Reference\nUnset\nConnection Reference\nApply\nReset\nDismiss\nNote\n:"}
{"Headers": "Automatic Reducer Creation", "Content": "When a change in size has been detected on a cable way, a reducer will be created at the location of the change in width on the smallest of the cable ways. The width will be taken from the CTMRL element of the connected branches, if none are found then it will be taken from the branch itself.\nAfter dressing the branches, you will be able to apply the material to the dressed branches which will create the CTRAY elements with the specifications that have been selected.\nNote:\nWhen a connected cable way branch is on the same center line and a width change is found a concentric reducer is created or when a connected cable way branch is on a different center line and a width change is found a eccentric reducer is created and the following tray elements are connected correctly.\n\n\n\nNote\n:"}
{"Headers": "Quick Cable Tray Routing", "Content": "Quick Cable Tray Routing is used when:\nClick the dotted line (ill-defined route), which then turns green, On the Cable Tray tab, in the Common group, click Model editor. Refer to Editor for further information.\n\nThe Quick Routing Handles display at the head and tail of the ill-defined route. Ill-defined routes are where the Head or Tail of a Branch have been defined but the route between has not.\n\nYou can now create a cable tray run between the head and tail of the branch, using the mouse, the quick routing handles and the options available from the Model Editor. Refer to Editor for further information.\nA change of direction displays in the 3D graphical view and the Model Explorer as an elbow or bend (dependent upon the specification). To make the choice of elbows or bends, right-click the cardinal direction handles to display the Model Editor menu.\n\nSelect Component Choice > Use Bends.\n\nThe head and tail of the branch has been defined but the route between the two has not, for example: implied pipe is not shown. (ill defined route = dotted line). The mouse is used to define the direction of the cable route, bends are automatically inserted when the route changes direction.\nBad alignment between two components, where the leave direction and arrive direction of adjacent elements do not match, (this can be due to the current design tolerance settings, for example: offset, angle and ratio).\nArrive or Leave where Head or Tail is undefined, where the end directly adjacent to a component is unset or ill-defined. An unset end is where the Head or Tail has its attributes left in the default state, whereas an ill-defined end is where, when the reference is set, the position is not with the reference item or when the end reference is not set, hence the end connection is unset.\nThe head and tail of the branch has been defined but the route between the two has not, for example: implied pipe is not shown. (ill defined route = dotted line). The mouse is used to define the direction of the cable route, bends are automatically inserted when the route changes direction.\nThe head and tail of the branch has been defined but the route between the two has not, for example: implied pipe is not shown. (ill defined route = dotted line). The mouse is used to define the direction of the cable route, bends are automatically inserted when the route changes direction.\nBad alignment between two components, where the leave direction and arrive direction of adjacent elements do not match, (this can be due to the current design tolerance settings, for example: offset, angle and ratio).\nBad alignment between two components, where the leave direction and arrive direction of adjacent elements do not match, (this can be due to the current design tolerance settings, for example: offset, angle and ratio).\nArrive or Leave where Head or Tail is undefined, where the end directly adjacent to a component is unset or ill-defined. An unset end is where the Head or Tail has its attributes left in the default state, whereas an ill-defined end is where, when the reference is set, the position is not with the reference item or when the end reference is not set, hence the end connection is unset.\nArrive or Leave where Head or Tail is undefined, where the end directly adjacent to a component is unset or ill-defined. An unset end is where the Head or Tail has its attributes left in the default state, whereas an ill-defined end is where, when the reference is set, the position is not with the reference item or when the end reference is not set, hence the end connection is unset.\n\n\n\nEditor\nEditor\nCable Tray\nCommon\nModel editor\nEditor\nEditor\n\nModel Editor\nComponent Choice > Use Bends"}
{"Headers": "Cable Tray Penetration", "Content": "On a typical project, it is necessary for designers to create holes in panel elements, for example: deck plates, gratings, floors. Due to implications on design integrity and cost, the hole creation process needs to be controlled and managed.\nThe Cable Tray Designer is not able to create holes in floor plates or wall panels as these items are created by another design discipline (Structural Department). These design items are held in another database for which the Cable Tray Designer has only read access.\nA method of requesting, approving or rejecting a hole between disciplines is required; this is known as Hole Management.\nThe Cable Tray Designer locates and sizes the hole and then makes a request for the hole to be created by the other discipline.\n\n\n"}
{"Headers": "Hole Management", "Content": "Hole Management is controlled and managed using the Hole Management application which allows for communication of hole data between disciplines including Request and Approval processes. Making sure holes are only created by users with appropriate write access permissions. Performing validation checks on managed holes and providing feedback to users on the hole status and the generation of reports for managed holes.\nGenerally in a project discipline Designers do not have write access to items created by other disciplines, for example: a Cable Tray designer does not have write access to structural elements and Structural designers do not have write access to cable tray elements.\nWith hole management, penetration holes are specified and requested by the penetrating discipline normally cable tray, HVAC or equipment designers and approved by the penetrated discipline, normally structural designers.\nThe specification of a penetration hole by the relevant discipline in the appropriate design application creates a virtual hole in the panel element, consisting of a FRMW and two FIXING elements. Each fixing element has a Specification Reference (Spref) attribute that points to the hole definition in the catalogue. An Association (ASSOC) element that references all the hole elements is also created.\nOnce the virtual hole has been created the penetrating discipline enters the Hole Management application and requests the hole. The owner of the panel, normally the Structural discipline, then reviews and approves (or rejects) the hole using the mechanism provided by the Hole Management application.\nThe act of approving the request creates the actual hole as a PFIT owned by the PANE element. The Hole Management application checks and validates the hole using the association restrictions and stores data on the hole history and status. Only valid holes may be approved. For a Structural penetration the structural designer may be both the requester and approver, although specific company procedures, controlled by DAC may be required if the Originator and Reviewer need to be different. For further information, refer to Hole Management System.\n\n\n\nHole Management\nHole Management System"}
{"Headers": "Check and Output Design Data", "Content": "On a typical project, it is necessary for Cable Tray Designers to check for errors and inconsistencies in the cable tray layout, checking for clashes (spatial interferences) between design elements.\nThese facilities are available from all Design applications, so the designer can readily check and output data from any combination of Design disciplines. For further information, refer to Data Check.\n\n\n\nDesign\nDesign\nData Check"}
{"Headers": "Import Cable Tray Data", "Content": "Import Cable Tray Data imports equipment tags, descriptions and other attributes from a CSV or Excel file.\nIt is anticipated that this function is used near the beginning of a project to pre-populate a Design database with a list of Cable Tray data from other Engineering data systems. It is not intended for the transfer of data from one Project to another. The geometry of the imported cable tray is not defined by this method. It is necessary to complete the definition of the cable tray by using the Design Equipment GUI.\nThe import is a two-stage process that initially analyzes the import file and reports errors and identifies if the entry is new or appears to exist already in the database. The second stage is to import those entries that you want to, based on the results of the analysis.\nThe content of the import file used as the input for this function must follow certain rules as described below; otherwise the data import is rejected by the system.\nOn the Cable Tray tab, in the Data group, click Import Cable Tray to display the CABLETRAY Data Import window.\n\nFrom the CABLETRAY Data Import window, navigate to and highlight the required import file. Select an option from the Files of type: pulldown list.\nClick Open to display the content of the selected spreadsheet in the Spread Sheet Import window.\nAt this stage no data has been loaded into the database. The window allows you to preview the data being loaded from the import file. When the file is loaded, some preliminary analysis of the data is carried out, and the icons, that display to the left of the table, indicate the result of that analysis.\nIndicates that a Cable Tray does not exist in the database. If this window is actioned, then the Cable Tray is created.\nIndicates that a Cable Tray already exists in the database. If the Load All Data function is actioned, then attributes of the Cable Tray are modified. No action is taken on rows with this Icon if the Load New Data option is actioned.\nIndicates that the system has identified a problem with this row of data. No action is taken on rows with this Icon when the Load All Data or Load New Data option is actioned. Selecting this row in the table displays a message in the Messages area of the window to indicate why this row cannot be processed.\nClicking Load All Data processes all of the rows that create a new element or modify an existing element. Clicking Load New Data option only processes the rows that create new elements.\n\nIndicates that a Cable Tray does not exist in the database. If this window is actioned, then the Cable Tray is created.\n\nIndicates that a Cable Tray already exists in the database. If the Load All Data function is actioned, then attributes of the Cable Tray are modified. No action is taken on rows with this Icon if the Load New Data option is actioned.\n\nIndicates that the system has identified a problem with this row of data. No action is taken on rows with this Icon when the Load All Data or Load New Data option is actioned. Selecting this row in the table displays a message in the Messages area of the window to indicate why this row cannot be processed.\nClicking Load All Data processes all of the rows that create a new element or modify an existing element. Clicking Load New Data option only processes the rows that create new elements.\nNew data is created at the current location in the database if an owning element field is not included in the imported file. Note that the owning element is considered to be the current element when the file was loaded and the rows of data analyzed, not the current element when a Load option is pressed. If an owning element field is provided in the import file, the system attempts to create elements under the specified owner.\nNow the Icons on the window indicate the result of the load operation.\nIndicates that the creation or modification operation was successful. An element has been created or modified in the database.\nIndicates that the operation has not completed successfully because of an error found while the system was trying to create or modify an element. If an attribute value is incorrect, as in the example above, then the element has been created, but not all of its attribute data has been loaded. You can choose to use the undo function to remove all of the changes made by the load operation and revert the database back to its state before the load, or to deal with the erroneous elements individually.\n\nIndicates that the creation or modification operation was successful. An element has been created or modified in the database.\n\nIndicates that the operation has not completed successfully because of an error found while the system was trying to create or modify an element. If an attribute value is incorrect, as in the example above, then the element has been created, but not all of its attribute data has been loaded. You can choose to use the undo function to remove all of the changes made by the load operation and revert the database back to its state before the load, or to deal with the erroneous elements individually.\nAnother import file can be loaded by using the File Open Icon, the Browse option or by typing a name directly into the filename field on the window.\nThe Reload Data option reloads the file shown in the filename field which may be necessary if the current element was incorrect or an owner element was missing when the file was first loaded.\nThe example above shows User Defined Element Types (UDETS), refer to the Lexicon Command Reference Manual, of equipment being created. If the imported file is carefully constructed it would be possible to import other element types provided that fields in the file contain all of the required data.\nIndicates that a Cable Tray does not exist in the database. If this window is actioned, then the Cable Tray is created.\nIndicates that a Cable Tray already exists in the database. If the Load All Data function is actioned, then attributes of the Cable Tray are modified. No action is taken on rows with this Icon if the Load New Data option is actioned.\nIndicates that the system has identified a problem with this row of data. No action is taken on rows with this Icon when the Load All Data or Load New Data option is actioned. Selecting this row in the table displays a message in the Messages area of the window to indicate why this row cannot be processed.\nClicking Load All Data processes all of the rows that create a new element or modify an existing element. Clicking Load New Data option only processes the rows that create new elements.\nIndicates that the creation or modification operation was successful. An element has been created or modified in the database.\nIndicates that the operation has not completed successfully because of an error found while the system was trying to create or modify an element. If an attribute value is incorrect, as in the example above, then the element has been created, but not all of its attribute data has been loaded. You can choose to use the undo function to remove all of the changes made by the load operation and revert the database back to its state before the load, or to deal with the erroneous elements individually.\nNote:\nThe Lexicon Database must be correctly configured, and the supplied values must be valid for the User Defined Attribute (UDA) being set.\n\n\n\nDesign\nNote\n:\nLexicon\nCable Tray\nData\nImport Cable Tray\nCABLETRAY Data Import\nCABLETRAY Data Import\nLexicon Command Reference Manual"}
{"Headers": "Rules for Content of the Import File", "Content": "An import file must have the following characteristics.\nAny import of new or modified element data is subject to the data access control configuration implemented for the current user and Project.\nThe function does not attempt to claim data automatically in an Explicit Claim database. If the data is imported into an Implicit Claim database, then the appropriate elements are claimed, if not already claimed by another user.\nExample of Data used as input to this function:\nType\nName\nspref\nDesc\npos\nBuilt\nEQUI\n/D1201\n/EQUI/Storage\n-Vessel/TYPEA\nStorage\nVessel\nX 9630 Y 3502 Z 6170\nfalse\nEQUI\n/C1101\nX 5360 Y 8850 Z 305\ntrue\nEQUI\n/E1302A\n/EQUI/Shell-Tube\n-Exchanger\nHeat\nExchanger\nX 9630 Y 3755 Z 8385\nfalse\nEQUI\n/E1302B\n/EQUI/Shell-Tube\n-Exchanger\nHeat\nExchanger\nX 9630 Y 3755 Z 9352\nfalse\nEQUI\n/P1501A\nPump\nX 9340 Y 12145 Z 645\nfalse\nEQUI\n/P1501B\nPump\nX 7510 Y 12145 Z 645\nfalse\nType\nName\nspref\nDesc\npos\nBuilt\nEQUI\n/D1201\n/EQUI/Storage\n-Vessel/TYPEA\nStorage\nVessel\nX 9630 Y 3502 Z 6170\nfalse\nEQUI\n/C1101\n\n\nX 5360 Y 8850 Z 305\ntrue\nEQUI\n/E1302A\n/EQUI/Shell-Tube\n-Exchanger\nHeat\nExchanger\nX 9630 Y 3755 Z 8385\nfalse\nEQUI\n/E1302B\n/EQUI/Shell-Tube\n-Exchanger\nHeat\nExchanger\nX 9630 Y 3755 Z 9352\nfalse\nEQUI\n/P1501A\n\nPump\nX 9340 Y 12145 Z 645\nfalse\nEQUI\n/P1501B\n\nPump\nX 7510 Y 12145 Z 645\nfalse\nTo import Unicode text from a CSV file, the file must be a Unicode format file. Some systems save CSV files as plain text files. To convert a file to Unicode format it is necessary to open the file with a tool that is capable of saving in Unicode format, for example Notepad or the transc text file conversion utility provided with the product.\nType\nName\nspref\nDesc\npos\nBuilt\nEQUI\n/D1201\n/EQUI/Storage\n-Vessel/TYPEA\nStorage\nVessel\nX 9630 Y 3502 Z 6170\nfalse\nEQUI\n/C1101\nX 5360 Y 8850 Z 305\ntrue\nEQUI\n/E1302A\n/EQUI/Shell-Tube\n-Exchanger\nHeat\nExchanger\nX 9630 Y 3755 Z 8385\nfalse\nEQUI\n/E1302B\n/EQUI/Shell-Tube\n-Exchanger\nHeat\nExchanger\nX 9630 Y 3755 Z 9352\nfalse\nEQUI\n/P1501A\nPump\nX 9340 Y 12145 Z 645\nfalse\nEQUI\n/P1501B\nPump\nX 7510 Y 12145 Z 645\nfalse\nThe file must be a valid CSV or Excel file.\nThe first row of the file contains a list of headings. Each heading represents a column in the file containing an attribute of the elements being loaded.\nThere must be a NAME column; otherwise the file does not load. The NAME column may contain the name of a new element, or the name of an existing element. If an existing element name is used, then this row is an update row for that element.\nAnother required column is the TYPE column which contains the database element type of the element being loaded, for example EQUI. If this column is absent, the file does not load. If the Project has been configured with User Defined Element Types (UDET), then this column can contain a valid UDET name (for example PUMP). If the named element already exists \u2013 but its element type does not match the TYPE in the file, then this row is ignored and an error is raised.\nA special column that may be included is the OWNER column. If this column is present, it must contain the name of an existing element that owns each imported item when it is created. The owner name is ignored if the imported item already exists \u2013 it is not possible to change the owner of existing Cable Trays by using the OWNER column. If the OWNER column does not exist in the file, then the owner is the current location in the Design DB hierarchy at the time that the file is loaded and analyzed. In this case, the current database element at the time that the file is loaded must be able to contain imported elements.\nThe remaining headings in the file must be valid attribute names for the element type being loaded. The attribute names may include User Defined Attribute (UDA) names.\nColumns cannot be added for array type attributes unless those attributes can be set using a list of values in a single field in the file. For example, the string \"10 20 30\" in a DESP field would set design parameter 1 to 10, 2 to 20 and 3 to 30.\nEvery row following the heading row must contain the correct number of fields (columns) as defined by the heading row.\nEvery row must contain valid values, or no values, for each field.\nIf a new element is being created, an attribute is set to its default value if a field in the file is empty. Two adjacent separators denote an empty field. The NAME and TYPE fields cannot be empty.\nIf an existing element is being modified, an attribute value remains unchanged if a field in the file is empty.\nIt is not possible to unset an attribute value from a file, other than by providing the default value. For example \"X0Y0Z0\" for a position.\nEach field in the file must be a text field. Care must be taken with fields containing values that are considered by Microsoft Excel to be a formula. For example a database reference number in the window \"=123/456\" would be considered to be a formula because of the \"=\" character. To overcome this, precede the \"=\" with a single quote character that forces the field to be treated as a text string. If the file does not load successfully into Microsoft Excel, it will not load successfully using this import function.\nThe file must be a valid CSV or Excel file.\nThe file must be a valid CSV or Excel file.\nThe first row of the file contains a list of headings. Each heading represents a column in the file containing an attribute of the elements being loaded.\nThe first row of the file contains a list of headings. Each heading represents a column in the file containing an attribute of the elements being loaded.\nThere must be a NAME column; otherwise the file does not load. The NAME column may contain the name of a new element, or the name of an existing element. If an existing element name is used, then this row is an update row for that element.\nThere must be a NAME column; otherwise the file does not load. The NAME column may contain the name of a new element, or the name of an existing element. If an existing element name is used, then this row is an update row for that element.\nAnother required column is the TYPE column which contains the database element type of the element being loaded, for example EQUI. If this column is absent, the file does not load. If the Project has been configured with User Defined Element Types (UDET), then this column can contain a valid UDET name (for example PUMP). If the named element already exists \u2013 but its element type does not match the TYPE in the file, then this row is ignored and an error is raised.\nAnother required column is the TYPE column which contains the database element type of the element being loaded, for example EQUI. If this column is absent, the file does not load. If the Project has been configured with User Defined Element Types (UDET), then this column can contain a valid UDET name (for example PUMP). If the named element already exists \u2013 but its element type does not match the TYPE in the file, then this row is ignored and an error is raised.\nA special column that may be included is the OWNER column. If this column is present, it must contain the name of an existing element that owns each imported item when it is created. The owner name is ignored if the imported item already exists \u2013 it is not possible to change the owner of existing Cable Trays by using the OWNER column. If the OWNER column does not exist in the file, then the owner is the current location in the Design DB hierarchy at the time that the file is loaded and analyzed. In this case, the current database element at the time that the file is loaded must be able to contain imported elements.\nA special column that may be included is the OWNER column. If this column is present, it must contain the name of an existing element that owns each imported item when it is created. The owner name is ignored if the imported item already exists \u2013 it is not possible to change the owner of existing Cable Trays by using the OWNER column. If the OWNER column does not exist in the file, then the owner is the current location in the Design DB hierarchy at the time that the file is loaded and analyzed. In this case, the current database element at the time that the file is loaded must be able to contain imported elements.\nThe remaining headings in the file must be valid attribute names for the element type being loaded. The attribute names may include User Defined Attribute (UDA) names.\nThe remaining headings in the file must be valid attribute names for the element type being loaded. The attribute names may include User Defined Attribute (UDA) names.\nColumns cannot be added for array type attributes unless those attributes can be set using a list of values in a single field in the file. For example, the string \"10 20 30\" in a DESP field would set design parameter 1 to 10, 2 to 20 and 3 to 30.\nColumns cannot be added for array type attributes unless those attributes can be set using a list of values in a single field in the file. For example, the string \"10 20 30\" in a DESP field would set design parameter 1 to 10, 2 to 20 and 3 to 30.\nEvery row following the heading row must contain the correct number of fields (columns) as defined by the heading row.\nEvery row following the heading row must contain the correct number of fields (columns) as defined by the heading row.\nEvery row must contain valid values, or no values, for each field.\nEvery row must contain valid values, or no values, for each field.\nIf a new element is being created, an attribute is set to its default value if a field in the file is empty. Two adjacent separators denote an empty field. The NAME and TYPE fields cannot be empty.\nIf a new element is being created, an attribute is set to its default value if a field in the file is empty. Two adjacent separators denote an empty field. The NAME and TYPE fields cannot be empty.\nIf an existing element is being modified, an attribute value remains unchanged if a field in the file is empty.\nIf an existing element is being modified, an attribute value remains unchanged if a field in the file is empty.\nIt is not possible to unset an attribute value from a file, other than by providing the default value. For example \"X0Y0Z0\" for a position.\nIt is not possible to unset an attribute value from a file, other than by providing the default value. For example \"X0Y0Z0\" for a position.\nEach field in the file must be a text field. Care must be taken with fields containing values that are considered by Microsoft Excel to be a formula. For example a database reference number in the window \"=123/456\" would be considered to be a formula because of the \"=\" character. To overcome this, precede the \"=\" with a single quote character that forces the field to be treated as a text string. If the file does not load successfully into Microsoft Excel, it will not load successfully using this import function.\nEach field in the file must be a text field. Care must be taken with fields containing values that are considered by Microsoft Excel to be a formula. For example a database reference number in the window \"=123/456\" would be considered to be a formula because of the \"=\" character. To overcome this, precede the \"=\" with a single quote character that forces the field to be treated as a text string. If the file does not load successfully into Microsoft Excel, it will not load successfully using this import function.\n\n\n\nDesign\nType\nName\nspref\nDesc\npos\nBuilt"}
{"Headers": "Modify Cable Tray", "Content": "Once the cable design has been completed it may be necessary to modify and orientate the branches or components.\nYou can modify head and tail details, connections, specifications and if required.\n\n\n"}
{"Headers": "Modify Branch", "Content": "Once the cable design has been completed it may be necessary to modify and orientate the branches or components.\nYou can modify head and tail details, connections, specifications and if required.\n\n\n"}
{"Headers": "Position Branch at an Explicit Position", "Content": "The Branch at Explicit Position window allows you to position the branch head and branch tail, set the branch width, branch direction and branch connection.\nOn the Cable Tray tab, in the Modify group, click Branch to display the Branch at Explicit Position window.\n\nTo modify branch head and branch tail details is identical to that described in Branch Element. For further information, refer to Branch Element.\n\n\n\nBranch Element\nBranch at Explicit Position\nCable Tray\nModify\nBranch\nBranch at Explicit Position\nBranch Element"}
{"Headers": "Modify Branch Specification", "Content": "To modify the branch specification on the Cable Tray tab, in the Modify group, click Branch to display the Modify Branch Specification window.\n\nClick CE to identify the equipment element as the current element. The Name and Specification of the current element display by default.\nYou can choose from the list of branch specifications.\nClick Apply to apply the selected specification to the branch, Reset to discard any changes or Dismiss to close the Modify Branch Specification window.\nNote:\nAll cable tray components created below the branch use the Specification selected in the list. To use different specifications within a cable tray run, a new branch must be created at each point a different specification is used.\n\n\n\nCable Tray\nModify\nBranch\nModify Branch Specification\nCE\nName\nSpecification\nNote\n:\nSpecification\nApply\nReset\nDismiss\nModify Branch Specification"}
{"Headers": "Modify Component", "Content": "You can change a component within a cable tray or adjust the position and orientation of a component.\n\n\n"}
{"Headers": "Modify Component Specification, Orientation and Position", "Content": "To modify the currently selected component, on the Cable Tray tab, in the Create group, click Component to display the Cable Tray Components window.\n\nTo modify component orientation and positioning is identical to that described in Create Component. For further information, refer to Create Component.\n\n\n\nCreate Component\nCable Tray\nCreate\nComponent\nCable Tray Components\nCreate Component"}
{"Headers": "Modify Component Connection", "Content": "You can change the connection properties of a component. To modify component connection is identical to that described in Connect Component. For further information, refer to Connect Component.\n\n\n\nConnect Component\nConnect Component"}
{"Headers": "Change Component Exit", "Content": "You can change the exit point of a multiway component, for example a tee, or a bend.\nTo change a component exit point, make sure the correct component is highlighted in the Model Explorer, on the Cable Tray tab, in the Tools group, click Change Exit. The exit point of the component displays in the 3D navigation view.\nThe same function can also be applied to a Bend to change the direction of the p-leave point. The Cable Tray application swaps the p-arrive and p-leave points of the component so that P1 is p-leave, and P2 is p-arrive.\n\n\n\nChange Exit"}
{"Headers": "Route Component", "Content": "You can change how branches are routed through a three way component.\nTo change a component route, make sure the correct component is highlighted in the Model Explorer, on the Cable Tray tab, in the Tools group, click Route component to display the Modify Route window.\n\nCE\nSets the currently selected component, from the Model Explorer or 3D graphical view, as the working component.\nRoute Through\nRoutes the branch through the tee (P1 to P2).\nBranch Off\nRoutes the branch through P1 and out P3.\nSplit Route\nRoutes the branch through P3 and out P2.\nCE\nSets the currently selected component, from the Model Explorer or 3D graphical view, as the working component.\nRoute Through\nRoutes the branch through the tee (P1 to P2).\nBranch Off\nRoutes the branch through P1 and out P3.\nSplit Route\nRoutes the branch through P3 and out P2.\nClick Apply to change the route, Reset to remove all changes or Dismiss to close the Modify Route window.\nCE\nSets the currently selected component, from the Model Explorer or 3D graphical view, as the working component.\nRoute Through\nRoutes the branch through the tee (P1 to P2).\nBranch Off\nRoutes the branch through P1 and out P3.\nSplit Route\nRoutes the branch through P3 and out P2.\n\n\n\nRoute component\nModify Route\nCE\nRoute Through\nBranch Off\nSplit Route\nApply\nReset\nDismiss"}
{"Headers": "Swap Branch", "Content": "You may want to change the direction of a three way component so that the offline leg (P3) is rotated through 180 degrees.\nTo change the offline leg component direction, make sure the correct component is highlighted in the Model Explorer, on the Cable Tray tab, in the Tools group, click Swap Branch. The changed direction of the component displays in the 3D navigation view.\n\n\n\nSwap Branch"}
{"Headers": "Move Component", "Content": "The Move function allows you to move a component in a set direction. The component can be moved by a set distance in that direction or it can be moved to a position relative to another element or relative to a plane through a set position.\nTo move a component, make sure the correct component is highlighted in the Model Explorer, on the Cable Tray tab, in the Tools group, click Move to display the Move window.\n\nFor further information, refer to Position and Orientate.\n\n\n\nMove\nMove\nMove\nPosition and Orientate"}
{"Headers": "Create Fixed Length Trays", "Content": "\nThe Cable Tray application allows you to apply Fixed Length Tray (FTUB) Components to all or part of a cable tray branch. Fixed length trays replace sections of implied straights.\nIf you are not at the branch or component level in the Model Explorer an error message displays summarizing the problem, for example in the following window an error explains that the element you are attempting to connect to is not at a branch.\n\nMake sure the correct branch or component is highlighted in the Model Explorer, on the Cable Tray tab, in the Tools group, click Fill with Straights to display the Fill Cable Tray B... window.\n\nThe Name of the current element displays by default.\nThe Fill drop-down list allows you to define the branch or components to which the applied Fixed Length Tray components are to be connected.\n\nBranch\nFixed Length Tray components are created for the branch.\nComponents\nYou are prompted to Identify the first component in the 3D graphical view, you are then prompted to Identify the Second component in the 3D graphical view\nFixed Length Tray components are created between the selected components.\nHead to Component\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are created from the branch head to the selected component.\nComponent to Tail\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are created from the branch tail to the selected component.\nBranch\nFixed Length Tray components are created for the branch.\nComponents\nYou are prompted to Identify the first component in the 3D graphical view, you are then prompted to Identify the Second component in the 3D graphical view\nFixed Length Tray components are created between the selected components.\nHead to Component\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are created from the branch head to the selected component.\nComponent to Tail\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are created from the branch tail to the selected component.\nClick OK to create the Fixed Length Tray components or Cancel to discard any changes and close the Fill Cable Tray B... window.\nBranch\nFixed Length Tray components are created for the branch.\nComponents\nYou are prompted to Identify the first component in the 3D graphical view, you are then prompted to Identify the Second component in the 3D graphical view\nFixed Length Tray components are created between the selected components.\nHead to Component\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are created from the branch head to the selected component.\nComponent to Tail\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are created from the branch tail to the selected component.\n\n\n\nCable Tray\nTools\nFill with Straights\nFill Cable Tray B...\nName\nFill\nBranch\nComponents\nIdentify the first component\nIdentify the Second component\nHead to Component\nIdentify the component\nComponent to Tail\nIdentify the component\nOK\nCancel\nFill Cable Tray B..."}
{"Headers": "Remove Fixed Length Trays", "Content": "\nThe Cable Tray application allows you to remove Fixed Length Tray (FTUB) Components from all or part of a cable tray branch.\nIf you are not at the branch or component level in the Model Explorer an error message displays summarizing the problem, for example in the following window an error explains that the element you are attempting to connect to is not at a branch.\n\nMake sure the correct branch or component is highlighted in the Model Explorer, on the Cable Tray tab, in the Tools group, click Remove Straights to display the Unfill Cable Tray B... window.\n\nThe Name of the current element displays by default.\nThe Unfill drop-down list allows you to define the branch or components to which the Fixed Length Tray components are to be removed.\n\nBranch\nFixed Length Tray components are removed from the branch.\nComponents\nYou are prompted to Identify the first component in the 3D graphical view, you are then prompted to Identify the Second component in the 3D graphical view\nFixed Length Tray components are removed between the selected components.\nHead to Component\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are removed from the branch head to the selected component.\nComponent to Tail\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are removed from the branch tail to the selected component.\nBranch\nFixed Length Tray components are removed from the branch.\nComponents\nYou are prompted to Identify the first component in the 3D graphical view, you are then prompted to Identify the Second component in the 3D graphical view\nFixed Length Tray components are removed between the selected components.\nHead to Component\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are removed from the branch head to the selected component.\nComponent to Tail\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are removed from the branch tail to the selected component.\nClick OK to create the Fixed Length Tray components or Cancel to discard any changes and close the Unfill Cable Tray B... window.\nBranch\nFixed Length Tray components are removed from the branch.\nComponents\nYou are prompted to Identify the first component in the 3D graphical view, you are then prompted to Identify the Second component in the 3D graphical view\nFixed Length Tray components are removed between the selected components.\nHead to Component\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are removed from the branch head to the selected component.\nComponent to Tail\nYou are prompted to Identify the component in the 3D graphical view.\nFixed Length Tray components are removed from the branch tail to the selected component.\n\n\n\nCable Tray\nTools\nRemove Straights\nUnfill Cable Tray B...\nName\nUnfill\nBranch\nComponents\nIdentify the first component\nIdentify the Second component\nHead to Component\nIdentify the component\nComponent to Tail\nIdentify the component\nOK\nCancel\nUnfill Cable Tray B..."}
{"Headers": "Work Area", "Content": "Most of the work area is common for all the design disciplines, but some areas with respect to the Cable Tray application can be customized to suit you.\n\n\n"}
{"Headers": "Choose Options", "Content": "Various Cable Tray application options can be preset, on the Cable Tray tab, in the Tools group, click Options to display the Choose Options window.\n\n\n\n\nCable Tray\nTools\nOptions\nChoose Options"}
{"Headers": "Default Selection", "Content": "Select the Default Selection check box to automatically select a specified (default) component sub-type, each time a generic component is created.\nClick to clear the Default Selection check box to ignore the default cable tray specification and display a list of available components irrespective of their specification.\nYou can also specify what information displays on the list of available components, refer to Selection Criteria for further information.\nSelection Criteria\nYou can specify what information displays on the list of available components, from the Selection Criteria drop-down list:\nBasic\nDisplays all the selector data\nText\nDisplays component and material descriptions\nAll\nDisplays the selector data and component and material descriptions\nBasic\nDisplays all the selector data\nText\nDisplays component and material descriptions\nAll\nDisplays the selector data and component and material descriptions\nBasic\nDisplays all the selector data\nText\nDisplays component and material descriptions\nAll\nDisplays the selector data and component and material descriptions\n\n\n\nSelection Criteria\nDefault Selection\nDefault Selection\nSelection Criteria\nSelection Criteria\nSelection Criteria\nBasic\nText\nAll"}
{"Headers": "Auto Connect", "Content": "Select the Auto Connect check box to automatically connect (position and orientate) the new component.\nNote:\nConnection only occurs if the connection types are compatible.\n\n\n\nAuto Connect\nNote\n:"}
{"Headers": "Auto Force Connect", "Content": "Select the Auto Force Connect check box to force the connection of incompatible connection types.\nNote:\nIf Auto Force Connect is used, when Data Consistency Checks are made, data inconsistencies display.\n\n\n\nAuto Force Connect\nNote\n:"}
{"Headers": "Obstruction Visualization", "Content": "You can view the obstruction level of a cable tray within the 3D graphical view. For further information, refer to Views.\n\n\n\nViews\nViews"}
{"Headers": "Cable Tray Menu Map", "Content": "The Cable Tray Menu Map only displays the menu map for options that are applicable to the Cable Tray application.\nModel editor\n\n\nNavigate to element\n\n\nMeasure distance >\nDistance\n\n\nAngle\n\nCopy element >\nWith Offset\n\n\nWith Rotation\n\n\nWith Mirror\n\nQuery design properties\n\n\nModify properties\n\n\nAttributes list\n\n\nPosition explicitly at co\u2011ordinates\n\n\nPosition relatively by >\nPosition\n\n\nMove\n\nRotate about axis >\nRotate\n\n\nOrientate\n\nSearch\n\n\nCollections\n\n\nClashes >\nClashes\n\n\nCheck CE\n\n\nAuto Clash\n\nChecker\n\n\nDelete >\nCE\n\n\nCE Members\n\n\nSelection\n\n\n\n\nCable Tray\n\n\nBranch\n\n\nComponent\n\n\n\n\n\nBranch\n\n\nSpecification\n\n\n\n\n\nOptions\n\n\nFill With Straights\n\n\nRemove Straights\n\n\nMove\n\n\nChange Exit\n\n\nRoute component\n\n\nSwap Branch\n\n\n\n\n\nHoles >\nHole Manager\n\n\nModify Hole\n\n\nGeneral Hole\n\n\nHole Report\n\n\n\n\nBranch\n\n\nNext\n\n\nPrevious\n\n\nConnection Ref.\n\n\n\n\n\nImport Cable Tray\n\n\nCommon\nModel editor\nNavigate to element\nMeasure distance >\nDistance\nAngle\nCopy element >\nWith Offset\nWith Rotation\nWith Mirror\nQuery design properties\nModify properties\nAttributes list\nPosition explicitly at co\u2011ordinates\nPosition relatively by >\nPosition\nMove\nRotate about axis >\nRotate\nOrientate\nSearch\nCollections\nClashes >\nClashes\nCheck CE\nAuto Clash\nChecker\nDelete >\nCE\nCE Members\nSelection\nCreate\nCable Tray\nBranch\nComponent\nModify\nBranch\nSpecification\nTools\nOptions\nFill With Straights\nRemove Straights\nMove\nChange Exit\nRoute component\nSwap Branch\nPenetrate\nHoles >\nHole Manager\nModify Hole\nGeneral Hole\nHole Report\nConnect\nBranch\nNext\nPrevious\nConnection Ref.\nData\nImport Cable Tray\n\n\n\nCommon\nCreate\nModify\nTools\nPenetrate\nConnect\nData"}
{"Headers": "Equipment Defaults", "Content": "The defaults define the appearance of a piece of equipment in the 3D graphical view. Refer to Drawing Representation Settings for further information.\n\n\n\n\nDrawing Representation Settings\nDrawing Representation Settings"}
{"Headers": "Work Area", "Content": "Many features of the EQUIPMENT discipline user interface are common to multiple AVEVA E3D Design design disciplines and are described in Common Functionality User Guide. With the exception of the functionality available for selection on the Equipment tab.\nTo enter the Equipment discipline, from the Quick Access Toolbar, select Equipment from the Disciplines drop-down list. When the Equipment discipline is opened, by default the Project tab is selected.\n\nThe work area provides access to a number of key commands and facilities. Most of the functionality available for selection are common to multiple AVEVA E3D Design disciplines and are described in Common Functionality.\nEquipment tab\nThe Equipment tab includes the following of functionality specific to the Piping discipline:\nCommon Group\nAll of the functionality available for selection in the Common group are common to multiple AVEVA E3D Design disciplines and are described in Common Functionality.\nPowerWheel\nMany operations in Equipment discipline can be initiated using the PowerWheel, refer to Common Functionality.\n\nAll of the out of box configurations for the power wheel can be customized, refer to Customizing guide.\nCreate\nModify\nTools\nDefaults\nReport\nAssociate.\nCreate\nCreate\nModify\nModify\nTools\nTools\nDefaults\nDefaults\nReport\nReport\nAssociate.\nAssociate.\nNote:\nThe Admin tab is only available for selection if you are a member of any team that contains the word ADMIN. For example, EQUIPADMIN, DESADMIN, ADMINXX. For administrative options, refer to the system administrator for further information.\nNote:\nThe equivalent functionality is also available from the Equipment User Interface (UI).\n\n\n\nEQUIPMENT\nEquipment\nEquipment\nDisciplines\n\nProject\nNote\n:\nAdmin\n\nEquipment tab\nEquipment\nCommon Group\nCommon\nCommon Functionality\nPowerWheel\nCommon Functionality\nNote\n:"}
{"Headers": "Import Equipment Data", "Content": "The Import Equipment Data functionality imports equipment tags, descriptions and other attributes from a CSV or Excel file.\nImport Equipment data pre-populates a database with a list of Equipment data from other Engineering data systems. It is not intended for the transfer of data from one project to another. The geometry of the imported equipment is not defined by this method. It is necessary to complete the definition of the Equipment by using the Equipment GUI.\nThe import is a two-stage process that initially analyzes the import file, reports errors and identifies if the entry is new or appears to exist already in the database. The second stage is to import those entries that the user requires, based on the results of the analysis.\nThe content of the import file used as the input for this function must follow certain rules, otherwise the data import is rejected by the system.\nOnce the file has been locate, click Open to display the Equipment Data Import window.\nData Import\nUse the Data Import window to import equipment tags, descriptions and other attributes from a CSV or Excel file.\n\nAt this stage no data has been loaded into the database. The window allows the user to preview the data being loaded from the import file. When the file is loaded, some preliminary analysis of the data is carried out, and the icons, displayed to the left of the table, indicate the result of that analysis.\nIndicates that an Equipment does not exist in the database. If this window is actioned, then the Equipment is created.\nIndicates that an Equipment already exists in the database. If the Load All Data function is actioned, then attributes of the Equipment are be modified. No action is taken on rows with this Icon if the Load New Data option is actioned.\nIndicates that the system has identified a problem with this row of data. No action is taken on rows with this Icon when the Load All Data or Load New Data option is actioned. Selecting the row in the table displays a message in the Messages area of the window indicating why the row cannot be processed.\nClick Load All Data to process all of the rows that create a new element or modify an existing element. Clicking Load New Data option only processes the rows that create new elements.\n\nIndicates that an Equipment does not exist in the database. If this window is actioned, then the Equipment is created.\n\nIndicates that an Equipment already exists in the database. If the Load All Data function is actioned, then attributes of the Equipment are be modified. No action is taken on rows with this Icon if the Load New Data option is actioned.\n\nIndicates that the system has identified a problem with this row of data. No action is taken on rows with this Icon when the Load All Data or Load New Data option is actioned. Selecting the row in the table displays a message in the Messages area of the window indicating why the row cannot be processed.\nClick Load All Data to process all of the rows that create a new element or modify an existing element. Clicking Load New Data option only processes the rows that create new elements.\nNew data is created at the current location in the database if an owning element field is not included in the imported file. Note that the owning element is considered to be the current element when the file was loaded and the rows of data analyzed, not the current element when a Load is started. If an owning element field is provided in the import file, the system attempts to create elements under the specified owner.\nThe Icons on the window indicate the result of the load operation.\nIndicates that the creation or modification operation was successful. An element has been created or modified in the database.\nIndicates that the operation has not completed successfully because of an error found while the system was attempting to create or modify an element. If an attribute value is incorrect, the element is created, but not all of its attribute data is loaded.\nSelect Undo to remove all of the changes made by the load operation and revert the database back to its state before the load, or to deal with the erroneous elements individually.\n\nIndicates that the creation or modification operation was successful. An element has been created or modified in the database.\n\nIndicates that the operation has not completed successfully because of an error found while the system was attempting to create or modify an element. If an attribute value is incorrect, the element is created, but not all of its attribute data is loaded.\nSelect Undo to remove all of the changes made by the load operation and revert the database back to its state before the load, or to deal with the erroneous elements individually.\nImport files can be loaded by using the File Open Icon, the Browse option or by typing a name directly into the Filename field on the Equipment Data Import window.\nClick Reload Data to reload the current file in the Select File field. The user may find this necessary if the current element was incorrect or an owner element was missing when the file was first loaded.\nIt is possible to load element types other than Equipment using this function. The example above shows User Defined Element Types (UDETs). If the imported file is carefully constructed it would be possible to import other element types provided that fields in the file contain all of the required data. For example, a nozzle list can be loaded provided that the owning equipment name is provided in an Owner field for each nozzle element, and the Type field identifies the element as a nozzle.\nIndicates that an Equipment does not exist in the database. If this window is actioned, then the Equipment is created.\nIndicates that an Equipment already exists in the database. If the Load All Data function is actioned, then attributes of the Equipment are be modified. No action is taken on rows with this Icon if the Load New Data option is actioned.\nIndicates that the system has identified a problem with this row of data. No action is taken on rows with this Icon when the Load All Data or Load New Data option is actioned. Selecting the row in the table displays a message in the Messages area of the window indicating why the row cannot be processed.\nClick Load All Data to process all of the rows that create a new element or modify an existing element. Clicking Load New Data option only processes the rows that create new elements.\nIndicates that the creation or modification operation was successful. An element has been created or modified in the database.\nIndicates that the operation has not completed successfully because of an error found while the system was attempting to create or modify an element. If an attribute value is incorrect, the element is created, but not all of its attribute data is loaded.\nSelect Undo to remove all of the changes made by the load operation and revert the database back to its state before the load, or to deal with the erroneous elements individually.\nNote:\nThe Lexicon Database must be correctly configured, and the supplied values must be valid for the User Defined Attribute (UDA) being set.\n\n\n\nNote\n:\nOpen\nEquipment Data Import\nData Import\nData Import\nLoad All Data\nLoad New Data\nLoad All Data\noad New Data\nMessages\nLoad New Data\nLoad\nUndo\nFile Open\nBrowse\nFilename\nEquipment Data Import\nReload Data\nSelect File"}
{"Headers": "Rules for Content of the Import File", "Content": "An import file must have the following characteristics:\nAny import of new or modified element data is subject to the data access control configuration implemented for the current user and Project.\nThe function does not attempt to claim data automatically in an Explicit Claim database. If the data is imported into an Implicit Claim database, then the appropriate elements are claimed, if not already claimed by another user.\nExample of Data used as input to this function:\nEQUI\n/D1201\n/EQUI/Storage-Vessel/TYPEA\nStorage Vessel\nX 9630 Y 3502 Z 6170\nfalse\nEQUI\n/C1101\n\n\nX 5360 Y 8850 Z 305\ntrue\nEQUI\n/E1302A\n/EQUI/Shell-Tube-Exchanger\nHeat Exchanger\nX 9630 Y 3755 Z 8385\nfalse\nEQUI\n/E1302B\n/EQUI/Shell-Tube-Exchanger\nHeat Exchanger\nX 9630 Y 3755 Z 9352\nfalse\nEQUI\n/P1501A\n\nPump\nX 9340 Y 12145 Z 645\nfalse\nEQUI\n/P1501B\n\nPump\nX 7510 Y 12145 Z 645\nfalse\nTo import Unicode text from a CSV file, the file must be a Unicode file format. Some systems save CSV files as plain text files. To convert a file to Unicode format it is necessary to open the file with a tool that is capable of saving in Unicode format, for example, Notepad or the transc text file conversion utility provided with the product.\nType\nName\nspref\nDesc\npos\nBuilt\nEQUI\n/D1201\n/EQUI/Storage-Vessel/TYPEA\nStorage Vessel\nX 9630 Y 3502 Z 6170\nfalse\nEQUI\n/C1101\nX 5360 Y 8850 Z 305\ntrue\nEQUI\n/E1302A\n/EQUI/Shell-Tube-Exchanger\nHeat Exchanger\nX 9630 Y 3755 Z 8385\nfalse\nEQUI\n/E1302B\n/EQUI/Shell-Tube-Exchanger\nHeat Exchanger\nX 9630 Y 3755 Z 9352\nfalse\nEQUI\n/P1501A\nPump\nX 9340 Y 12145 Z 645\nfalse\nEQUI\n/P1501B\nPump\nX 7510 Y 12145 Z 645\nfalse\nThe file must be a valid CSV or Excel file.\nThe first row of the file contains a list of headings. Each heading represents a column in the file containing an attribute of the elements being loaded.\nThere must be a NAME column; otherwise the file is not be loaded. The NAME column may contain the name of a new element, or the name of an existing element. If an existing element name is used, then this row is an update row for that element. The name used must obey the normal rules for element naming in Marine.\nAnother required column is the TYPE column which contains the database element type of the element being loaded, for example, EQUI. If this column is absent, the file is not loaded. If the Project has been configured with User Defined Element Types (UDET), then this column can contain a valid UDET name (for example, :PUMP). If the named element already exists \u2013 but its element type does not match the TYPE in the file, then this row is ignored and an error is raised.\nA column that may be included is the OWNER column. If this column is present, it must contain the name of an existing element that owns each imported item when it is created. The owner name is ignored if the imported item already exists \u2013 it is not possible to change the owner of existing Equipment by using the OWNER column. If the OWNER column does not exist in the file, then the owner is the current location in the Design DB hierarchy at the time that the file is loaded and analyzed. In this case, the current database element at the time that the file is loaded must be able to contain imported elements.\nThe remaining headings in the file must be valid attribute names for the element type being loaded. The attribute names may include User Defined Attribute (UDA) names.\nColumns cannot be added for array type attributes unless those attributes can be set using a list of values in a single field in the file. For example, the string \"10 20 30\" in a DESP field would set design parameter 1 to 10, 2 to 20 and 3 to 30.\nEvery row following the heading row must contain the correct number of fields (columns) as defined by the heading row.\nEvery row must contain valid values, or no values, for each field.\nIf a new element is being created, an attribute is set to its default value if a field in the file is empty. Two adjacent separators denote an empty field. The NAME and TYPE fields cannot be empty.\nIf an existing element is being modified, an attribute value remains unchanged if a field in the file is empty.\nIt is not possible to unset an attribute value from a file, other than by providing the default value. For example \"X0Y0Z0\" for a position.\nEach field in the file must be a text field. Care must be taken with fields containing values that are considered by Microsoft Excel to be a formula. For example a database reference number in the window \"=123/456\" would be considered to be a formula because of the \"=\" character. To overcome this, precede the \"=\" with a single quote character that forces the field to be treated as a text string. If the file does not load successfully into Microsoft Excel, it does not load successfully using this import function.\nThe file must be a valid CSV or Excel file.\nThe file must be a valid CSV or Excel file.\nThe first row of the file contains a list of headings. Each heading represents a column in the file containing an attribute of the elements being loaded.\nThe first row of the file contains a list of headings. Each heading represents a column in the file containing an attribute of the elements being loaded.\nThere must be a NAME column; otherwise the file is not be loaded. The NAME column may contain the name of a new element, or the name of an existing element. If an existing element name is used, then this row is an update row for that element. The name used must obey the normal rules for element naming in Marine.\nThere must be a NAME column; otherwise the file is not be loaded. The NAME column may contain the name of a new element, or the name of an existing element. If an existing element name is used, then this row is an update row for that element. The name used must obey the normal rules for element naming in Marine.\nAnother required column is the TYPE column which contains the database element type of the element being loaded, for example, EQUI. If this column is absent, the file is not loaded. If the Project has been configured with User Defined Element Types (UDET), then this column can contain a valid UDET name (for example, :PUMP). If the named element already exists \u2013 but its element type does not match the TYPE in the file, then this row is ignored and an error is raised.\nAnother required column is the TYPE column which contains the database element type of the element being loaded, for example, EQUI. If this column is absent, the file is not loaded. If the Project has been configured with User Defined Element Types (UDET), then this column can contain a valid UDET name (for example, :PUMP). If the named element already exists \u2013 but its element type does not match the TYPE in the file, then this row is ignored and an error is raised.\nA column that may be included is the OWNER column. If this column is present, it must contain the name of an existing element that owns each imported item when it is created. The owner name is ignored if the imported item already exists \u2013 it is not possible to change the owner of existing Equipment by using the OWNER column. If the OWNER column does not exist in the file, then the owner is the current location in the Design DB hierarchy at the time that the file is loaded and analyzed. In this case, the current database element at the time that the file is loaded must be able to contain imported elements.\nA column that may be included is the OWNER column. If this column is present, it must contain the name of an existing element that owns each imported item when it is created. The owner name is ignored if the imported item already exists \u2013 it is not possible to change the owner of existing Equipment by using the OWNER column. If the OWNER column does not exist in the file, then the owner is the current location in the Design DB hierarchy at the time that the file is loaded and analyzed. In this case, the current database element at the time that the file is loaded must be able to contain imported elements.\nThe remaining headings in the file must be valid attribute names for the element type being loaded. The attribute names may include User Defined Attribute (UDA) names.\nThe remaining headings in the file must be valid attribute names for the element type being loaded. The attribute names may include User Defined Attribute (UDA) names.\nColumns cannot be added for array type attributes unless those attributes can be set using a list of values in a single field in the file. For example, the string \"10 20 30\" in a DESP field would set design parameter 1 to 10, 2 to 20 and 3 to 30.\nColumns cannot be added for array type attributes unless those attributes can be set using a list of values in a single field in the file. For example, the string \"10 20 30\" in a DESP field would set design parameter 1 to 10, 2 to 20 and 3 to 30.\nEvery row following the heading row must contain the correct number of fields (columns) as defined by the heading row.\nEvery row following the heading row must contain the correct number of fields (columns) as defined by the heading row.\nEvery row must contain valid values, or no values, for each field.\nEvery row must contain valid values, or no values, for each field.\nIf a new element is being created, an attribute is set to its default value if a field in the file is empty. Two adjacent separators denote an empty field. The NAME and TYPE fields cannot be empty.\nIf a new element is being created, an attribute is set to its default value if a field in the file is empty. Two adjacent separators denote an empty field. The NAME and TYPE fields cannot be empty.\nIf an existing element is being modified, an attribute value remains unchanged if a field in the file is empty.\nIf an existing element is being modified, an attribute value remains unchanged if a field in the file is empty.\nIt is not possible to unset an attribute value from a file, other than by providing the default value. For example \"X0Y0Z0\" for a position.\nIt is not possible to unset an attribute value from a file, other than by providing the default value. For example \"X0Y0Z0\" for a position.\nEach field in the file must be a text field. Care must be taken with fields containing values that are considered by Microsoft Excel to be a formula. For example a database reference number in the window \"=123/456\" would be considered to be a formula because of the \"=\" character. To overcome this, precede the \"=\" with a single quote character that forces the field to be treated as a text string. If the file does not load successfully into Microsoft Excel, it does not load successfully using this import function.\nEach field in the file must be a text field. Care must be taken with fields containing values that are considered by Microsoft Excel to be a formula. For example a database reference number in the window \"=123/456\" would be considered to be a formula because of the \"=\" character. To overcome this, precede the \"=\" with a single quote character that forces the field to be treated as a text string. If the file does not load successfully into Microsoft Excel, it does not load successfully using this import function.\n\n\n"}
{"Headers": "Model Equipment", "Content": "Before modelling a piece of equipment, the correct database elements should already be present in the Model Explorer, for example, a World, Site and Zone should exist. If this is not the case, refer to for more information.\nThe Equipment discipline has the functionality to model pieces of equipment using the following methods:\nUsing primitives to create one-off pieces of equipment.\nDesign Templates use primitives and other elements to create equipment, the templates are generally parameterized (standard or selection table).\nImport models and different file formats using the Mechanical Equipment Interface functionality.\nUsing primitives to create one-off pieces of equipment.\nUsing primitives to create one-off pieces of equipment.\nDesign Templates use primitives and other elements to create equipment, the templates are generally parameterized (standard or selection table).\nDesign Templates use primitives and other elements to create equipment, the templates are generally parameterized (standard or selection table).\nImport models and different file formats using the Mechanical Equipment Interface functionality.\nImport models and different file formats using the Mechanical Equipment Interface functionality.\n\n\n\nModel Explorer"}
{"Headers": "Database Hierarchy", "Content": "All database elements are owned by other elements, therefore elements must be created in a strict order, see figure below.\nThe following database elements are common to multiple AVEVA E3D Design design disciplines:\nEquipment Specific Hierarchy\nBelow the zone level in the Equipment discipline, the specific elements are:\n\nEquipment\nThe Equipment (EQUI) element(s) are administrative and can own a number of Sub-equipment elements or Primitive and Nozzle elements. Refer Equipment Element to for further information.\nSub-equipment\nThe Sub-equipment (SUBE) element(s) are owned by Equipment elements. Sub-equipment elements can own a number of Primitive and Nozzle elements. Refer to Sub-Equipment for further information.\nPrimitive\nThe Primitive (for example, BOX or CYLI) element(s) are owned by Equipment or Sub-equipment elements. These elements dictate the shape and geometry of the equipment item. Refer to Primitives for further information.\nNozzle\nThe Nozzle (NOZZ) element(s) are owned by Equipment or Sub-equipment elements. These elements are used to connect an equipment item to pipework. Refer to Nozzle for further information.\nElectrical Component\nThe Electrical Component (ELCONN) element(s) are owned by Equipment or Sub-equipment elements. These elements are used to connect an equipment item to an electrical cable. Refer to Electrical Component for further information.\nDepending on the selections made from the Equipment tab, further windows are presented prompting for input and options allowing for the workflow to continue.\nFunctionality from the Equipment tab will be unavailable if the correct database hierarchy has not been configured beforehand. For example certain equipment elements must reside below other elements in the database hierarchy.\nIf a particular equipment element cannot be created at the current position in the database hierarchy the user receives an error message summarizing the problem.\n\nWorld\nSite\nZone\nWorld\nWorld\nSite\nSite\nZone\nZone\n\n\n\nEquipment Element\nSub-Equipment\nPrimitives\nNozzle\nElectrical Component\nEquipment Specific Hierarchy\n\nEquipment\nEquipment Element\nSub-equipment\nSub-Equipment\nPrimitive\nPrimitives\nNozzle\nNozzle\nElectrical Component\nElectrical Component"}
{"Headers": "Names", "Content": "Any element in the database may be named, names identify elements and can be used to produce meaningful reports from the database. Which elements have names the user is a matter of choice, but in general it is expected that all major design items such as Equipment, Nozzles, Pipes and Valves are named.\nConventionally, for equipment, all the main equipment and all of its nozzles are named. Nozzles usually carry the equipment name plus a suffix to identify the specific nozzle. For example nozzle 1 of an equipment called /YY9001 would probably be called /YY9001-N1, /YY9001/N1 or simply /YY9001/1. Whatever names are used, the naming convention is usually defined in the project specification used for the project. It is probable that the project has Autonaming rules set up for items such as nozzles so that the project conventions are followed in every detail.\nAttaching names to elements may be done in a number of ways. Most creation windows offer an opportunity to name the element being created and allows a name to be input without the preceding slash (/) character. The slash (/) is added automatically during the command processing.\nTo rename an element name, right-click an element in the Model Explorer and select Rename from the list to display the ReName window, refer to Rename for further information.\nNote:\nNames cannot contain spaces and are case sensitive, for example, /YY9001A is a different name from /YY9001a or /yy9001A. Elements in a database are unique, for example, they cannot have the same name or reference number.\n\n\n\nNote\n:\nRename\nReName\nRename"}
{"Headers": "Equipment Element", "Content": "The Equipment (EQUI) element(s) are administrative and can own a number of Sub-equipment elements or Primitive and Nozzle elements.\nUse the Equipment Creation window to create an administrative EQUI element in the design hierarchy.\n\nEnter a name for the EQUI element in the Naming field.\nThe equipment element can be positioned on one of three ways:\nThe Position pane sets the coordinates of the equipment element\u2019s origin.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Input an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Input an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Input an explicit position value in the Position field.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Input an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Input an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Input an explicit position value in the Position field.\nIf required, select one or all of the Lock check boxes to lock the explicit position of the current co-ordinate along the E/W, N/S or U/D axis.\nThe axes to which all co-ordinates are interpreted with respect to must be set.\nIn the wrt text box, input the name of the element to which all co-ordinates are interpreted with respect to, the default is /*.\nInput attributes of the equipment element in the Attributes pane:\nDescription\nInput the Description of the Equipment element.\nFunction\nInput the Function for the Equipment element.\nDesign Code\nInput the Design Code for the Equipment element.\nPaint Specification\nInput the Paint Specification for the Equipment element.\nInspection Schedule\nInput the Inspection Schedule for the Equipment element.\nDescription\nInput the Description of the Equipment element.\nFunction\nInput the Function for the Equipment element.\nDesign Code\nInput the Design Code for the Equipment element.\nPaint Specification\nInput the Paint Specification for the Equipment element.\nInspection Schedule\nInput the Inspection Schedule for the Equipment element.\nClick OK to create the Equipment element or Cancel to discard any inputs and close the Equipment Creation window. The Primitive gallery activates by default. Refer to Primitives for further information.\n\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Input an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Input an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Input an explicit position value in the Position field.\nDescription\nInput the Description of the Equipment element.\nFunction\nInput the Function for the Equipment element.\nDesign Code\nInput the Design Code for the Equipment element.\nPaint Specification\nInput the Paint Specification for the Equipment element.\nInspection Schedule\nInput the Inspection Schedule for the Equipment element.\nUsing the functionality available from the Positioning Control window, refer to COMMON for further information.\nUsing the cursor and picking a position in the graphical view\nUsing the functionality available from the Position pane of the Equipment Creation window.\nUsing the functionality available from the Positioning Control window, refer to COMMON for further information.\nUsing the functionality available from the Positioning Control window, refer to COMMON for further information.\nUsing the cursor and picking a position in the graphical view\nUsing the cursor and picking a position in the graphical view\nUsing the functionality available from the Position pane of the Equipment Creation window.\nUsing the functionality available from the Position pane of the Equipment Creation window.\n\n\n\nPrimitives\nEquipment Creation\nNaming\nPositioning Control\nCOMMON\nPosition\nEquipment Creation\nEast/West\nEast/West\nNorth/South\nNorth/South\nUp/Down\nUp/Down\nwrt\nAttributes\nDescription\nFunction\nDesign Code\nPaint Specification\nInspection Schedule\nOK\nCancel\nEquipment Creation\nPrimitive\nPrimitives"}
{"Headers": "Sub-Equipment", "Content": "A Sub-Equipment element is also an administrative element, which defines an equipment sub-assembly to be associated with an existing equipment element. The Sub-equipment (SUBE) element(s) are owned by Equipment elements. Sub-equipment elements can own a number of Primitive and Nozzle elements.\n\nEnter a name for the SUBE element in the Naming field.\nThe Position pane sets the coordinates of the sub-equipment element\u2019s origin.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Input an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Input an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Input an explicit position value in the Position field.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Input an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Input an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Input an explicit position value in the Position field.\nThe axes to which all co-ordinates are interpreted with respect to must be set.\nThe wrt text box displays the owning equipment element by default, the user can input an alternative value in the field.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Input an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Input an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Input an explicit position value in the Position field.\n\n\n\nNaming\nEast/West\nEast/West\nNorth/South\nNorth/South\nUp/Down\nUp/Down\nwrt"}
{"Headers": "Primitives", "Content": "Equipment elements consist of a collection of primitives, positioned in the 3D graphical view as a graphical representation of the piece of equipment. The primitives are created using parameters in the graphical view. The initial method of creation is the default although other methods are available for selection.\nFor example, the simple storage vessel shown below can be constructed from a cylinder for the main body, two dishes for the ends, two boxes for the support legs and a nozzle for the piping connection.\n\nPrimitive Gallery\nAll of the primitives are available for selection from the Primitive gallery.\n\nCreate a Box Primitive\nUse the functionality to create a box primitive (BOX) element in the design hierarchy, refer to for further information.\nCreate a Cylinder Primitive\nUse the functionality to create a cylinder primitive (CYLI) element, refer tor for further information.\nCreate a Cone Primitive\nUse the functionality to create a cone primitive element (CONE), refer to for further information.\nCreate a Snout Primitive\nUse the functionality to create a snout primitive element (SNOU), refer to for further information\nCreate a Pyramid Primitive\nUse the functionality to create a pyramid primitive element (PYRA), refer to for further information.\nCreate a Dish Primitive\nUse the functionality to create a dish primitive element (DISH), refer to for further information.\nCreate a Extrusion Primitive\nUse the functionality to create an extrusion primitive element (EXTR), refer to for further information.\nCreate a Circular Torus Primitive\nUse the functionality to create a circular torus primitive element (CTOR), refer to for further information.\nCreate a Rectangular Torus Primitive\nUse the functionality to create a rectangular torus primitive element (RTOR), refer to for further information.\nCreate a Sloped Cylinder Primitive\nUse the functionality to create a sloped cylinder primitive element (SLCY), refer to for further information.\nCreate a Revolution Primitive\nUse the functionality to create a revolution primitive element (REVO), refer to for further information.\n\nCreate a Box Primitive\nUse the functionality to create a box primitive (BOX) element in the design hierarchy, refer to for further information.\n\nCreate a Cylinder Primitive\nUse the functionality to create a cylinder primitive (CYLI) element, refer tor for further information.\n\nCreate a Cone Primitive\nUse the functionality to create a cone primitive element (CONE), refer to for further information.\n\nCreate a Snout Primitive\nUse the functionality to create a snout primitive element (SNOU), refer to for further information\n\nCreate a Pyramid Primitive\nUse the functionality to create a pyramid primitive element (PYRA), refer to for further information.\n\nCreate a Dish Primitive\nUse the functionality to create a dish primitive element (DISH), refer to for further information.\n\nCreate a Extrusion Primitive\nUse the functionality to create an extrusion primitive element (EXTR), refer to for further information.\n\nCreate a Circular Torus Primitive\nUse the functionality to create a circular torus primitive element (CTOR), refer to for further information.\n\nCreate a Rectangular Torus Primitive\nUse the functionality to create a rectangular torus primitive element (RTOR), refer to for further information.\n\nCreate a Sloped Cylinder Primitive\nUse the functionality to create a sloped cylinder primitive element (SLCY), refer to for further information.\n\nCreate a Revolution Primitive\nUse the functionality to create a revolution primitive element (REVO), refer to for further information.\nPositioning\nPrimitives and negative primitives are created using parameters in the graphical view aligned with the default axis system (X=E, Y=N and Z=U), this is the default option. Each primitive can be positioned using relative or absolute positioning through a series of prompts, refer to Position Fields (COMMON) and for further information.\nBox Primitive\nCreates a box primitive using parameters through a series of prompts in the graphical view,. For a definition of the parameters refer to and for further information.\n\nAfter selecting Create a Box Primitive from the Primitive Gallery, the prompt to Specify the first corner is displayed, click to identify the first corner position as the origin of the box primitive relative to its owner (EQUI element). Or input values into the dimension fields and press Enter.\n\nThe Specify the opposite corner prompt is displayed, input a value into the dimension fields and press Enter or click to identify the opposite corner of the box primitive.\n\nThe Specify the Z length prompt is displayed, input a value into the dimension field or click to identify the height of the box primitive.\n\nThroughout the box primitive creation process, press Esc to cancel the command, additional functionality is also available.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nW - Two Points\nPress the down arrow key and select Two Points to create a box primitive with two specified points (first and opposite corners).\nT - Three Points\nPress the down arrow key and select Three Points to create a box primitive with three specified points (first, opposite and height).\nF - Four Points\nPress the down arrow key and select Four Points to create a box primitive with relative positioning functionality, with four specified points (origin, X, Y,Z).\nE - Explicit\nPress the down arrow key and select Explicit to create a box primitive with absolute positioning functionality, in this case specified origin, width, length and height.\nBack\nPress the down arrow key and select Back to undo the last action.\nW - Two Points\nPress the down arrow key and select Two Points to create a box primitive with two specified points (first and opposite corners).\nT - Three Points\nPress the down arrow key and select Three Points to create a box primitive with three specified points (first, opposite and height).\nF - Four Points\nPress the down arrow key and select Four Points to create a box primitive with relative positioning functionality, with four specified points (origin, X, Y,Z).\nE - Explicit\nPress the down arrow key and select Explicit to create a box primitive with absolute positioning functionality, in this case specified origin, width, length and height.\nCylinder Primitive\nCreates a cylinder primitive through a series of prompts in the graphical view. For a definition of the parameters, refer to Cylinder Element (CYLINDER), Cylinder (SCYL) and Cylinder (LCYL) for further information.\n\nAfter selecting Create a Cylinder Primitive from the Primitive Gallery, the prompt to Specify the base centre is displayed, click to identify the base center position as the origin of the cylinder primitive relative to its owner (EQUI element). Or input values into the dimension fields and press Enter.\n\nThe Specify the diameter prompt is displayed, click to identify the diameter or input values in the dimension fields and press Enter.\n\nThe Specify the height prompt is displayed, click to identify the height of the cylinder or input a value in the dimension field and press Enter.\n\nThroughout the cylinder primitive creation process, press Esc to cancel the command, additional functionality is also available.\n\nRadius\nPress the down arrow key and select Radius to create the curved part of the cylinder primitive with a specified center point and radius.\nBack\nPress the down arrow key and select Back to undo the last action.\nRadius\nPress the down arrow key and select Radius to create the curved part of the cylinder primitive with a specified center point and radius.\nBack\nPress the down arrow key and select Back to undo the last action.\nCone Primitive\nCreates a cone primitive using parameters through a series of prompts in the graphical view, for a definition of the parameters refer to Cone Element (CONE) and Cone (SCON) for further information.\n\nAfter selecting Create a Cone Primitive from the Primitive Gallery, the prompt to Specify the base centre is displayed, click to identify the base center position as the origin of the cone primitive relative to its owner (EQUI element). Or input values into the dimension fields and press Enter.\n\nThe Specify the diameter prompt is displayed, click to identify the D-bottom diameter or input values in the dimension fields and press Enter.\n\nThe Specify the height prompt is displayed. click to identify the height of the vertex above the base or input a value in the dimension field and press Enter.\n\nThe Specify the diameter prompt is displayed, click to identify the D-top diameter or input values in the dimension fields and press Enter.\n\nThroughout the cone primitive creation process, press Esc to cancel the command, additional functionality is also available.\n\nTwo Points\nPress the down arrow key and select Two Points to create the curved part of the cone primitive with two specified points (diameter start and end).\nExplicit\nPress the down arrow key and select Explicit to create a cone primitive with an absolute positioning functionality, in this case specified origin, D-top, D-bottom and height.\nCentre+\nPress the down arrow and select Centre+ to create the curved part of the cone primitive with a specified center point and radius/diameter point.\nRadius\nPress the down arrow key and select Radius to create the curved part of the cone primitive with a specified center point and radius.\nBack\nPress the down arrow key and select Back to undo the action.\nTwo Points\nPress the down arrow key and select Two Points to create the curved part of the cone primitive with two specified points (diameter start and end).\nExplicit\nPress the down arrow key and select Explicit to create a cone primitive with an absolute positioning functionality, in this case specified origin, D-top, D-bottom and height.\nCentre+\nPress the down arrow and select Centre+ to create the curved part of the cone primitive with a specified center point and radius/diameter point.\nRadius\nPress the down arrow key and select Radius to create the curved part of the cone primitive with a specified center point and radius.\nBack\nPress the down arrow key and select Back to undo the action.\nSnout Primitive\nCreates a snout primitive using parameters through a series of prompts in the graphical view. Refer to Snout (LSNO) and Snout Element (SNOUT) for further information.\n\nAfter selecting Create a Snout Primitive from the Primitive Gallery, the prompt to Specify the base centre is displayed, click to identify the base center position as the origin of the snout primitive relative to its owner (EQUI element). Or input values into the dimension fields and press Enter.\n\nThe Specify the diameter prompt is displayed, click to identify the D-bottom diameter or input values in the dimension fields and press Enter.\n\nThe Specify the height prompt is displayed, click to identify the height of the snout or input a value in the dimension field and press Enter.\n\nThe Specify the diameter prompt is displayed, click to identify the D-top diameter or input a value in the dimension field and press Enter.\n\nThe Specify the offset prompt is displayed, click to identify the offset of the snout primitive or input values in the dimension fields and press Enter.\n\nThroughout the snout primitive creation process, press Esc to cancel the command, additional functionality is also available.\n\nTwo Points\nPress the down arrow key and select Two Points to create the curved part of the snout primitive with two specified points (diameter start and end).\nCentre+\nPress the down arrow and select Centre+ to create the curved part of the snout primitive with a specified center point and radius/diameter point.\nRadius\nPress the down arrow key and select Radius to create the curved part of the snout primitive with a specified center point and radius.\nBack\nThe option Back is available during the selection, Back moves back one step.\nTwo Points\nPress the down arrow key and select Two Points to create the curved part of the snout primitive with two specified points (diameter start and end).\nCentre+\nPress the down arrow and select Centre+ to create the curved part of the snout primitive with a specified center point and radius/diameter point.\nRadius\nPress the down arrow key and select Radius to create the curved part of the snout primitive with a specified center point and radius.\nBack\nThe option Back is available during the selection, Back moves back one step.\nPyramid Primitive\nCreates a pyramid primitive using parameters through a series of prompts in the graphical view. Refer to and for further information.\n\nAfter selecting Create a Pyramid Primitive from the Primitive Gallery, the prompt to Specify the base centre is displayed, click to identify the base centre as the origin of the pyramid primitive relative to its owner (EQUI element). Or input values into the dimension fields and press Enter.\n\nThe Specify the X length prompt is displayed, click to identify the bottom X length or input a value in the dimension field and press Enter.\n\nThe Specify the Y length prompt is displayed, click to identify the bottom Y length or input a value in the dimension field and press Enter.\n\nThe Specify the height prompt is displayed, click to identify the height of the pyramid or input a value in the dimension field and press Enter.\n\nThe Specify the X length prompt is displayed, click to indentify the top X length or input a value in the dimension field and press Enter.\n\nThe Specify the Y length prompt is displayed, click to indentify the top Y length or input a value in the dimension field and press Enter.\n\nThe Specify the offset prompt is displayed, click to indentify the offset for the pyramid or input a value in the dimension field and press Enter.\n\nThroughout the pyramid creation process, press Esc to cancel the command, additional functionality is also available.\n\nTwo Points\nPress the down arrow and select Two Points to create the base of the pyramid with two specified points (first and opposite corner).\nTwo Points\nPress the down arrow and select Two Points to create the base of the pyramid with two specified points (first and opposite corner).\nDish Primitive\nCreates a dish primitive using parameters through a series of prompts in the graphical view. Refer to and for further information.\n\nAfter selecting Create a Dish Primitive from the Primitive Gallery, the prompt Specify the base centre is displayed, click to indentify the base center position as the origin of the dish primitive relative to its owner (EQUI element). Or input values into the dimension fields and press Enter.\n\nThe Specify the diameter prompt is displayed, click to indentify the diameter of the dish primitive or input a value in the dimension field and press Enter.\n\nThe Specify the height prompt is displayed, click to indentify the height of the dish primitive r input a value in the dimension field and press Enter.\n\nThroughout the dish primitive creation process, press Esc to cancel the command, additional functionality is also available.\n\nTwo Points\nPress the down arrow key and select Two Points to create the base of the dish primitive (diameter start and end).\nCentre+\nPress the down arrow and select Centre+ to create the curved part of the dish primitive with a specified center point and radius/diameter point.\nRadius\nPress the down arrow key and select Radius to create the curved part of the dish primitive with a specified center point and radius.\nKnuckle Radius\nPress the down arrow key and select Knuckle Radius to create the transition between the cylinder and dish (knuckle).\nBack\nThe option Back is available during the selection, Back moves back one step.\nTwo Points\nPress the down arrow key and select Two Points to create the base of the dish primitive (diameter start and end).\nCentre+\nPress the down arrow and select Centre+ to create the curved part of the dish primitive with a specified center point and radius/diameter point.\nRadius\nPress the down arrow key and select Radius to create the curved part of the dish primitive with a specified center point and radius.\nKnuckle Radius\nPress the down arrow key and select Knuckle Radius to create the transition between the cylinder and dish (knuckle).\nBack\nThe option Back is available during the selection, Back moves back one step.\nExtrusion Primitive\nCreates an extrusion primitive using parameters through a series of prompts in the graphical view. Refer to for further information.\nAfter selecting Create an Extrusion primitive from the Primitive Gallery, the prompt to Specify first corner (fillet radius: 0mm) is displayed, click to identify the first vertice (SVER). Or input values into the dimension fields and press Enter.\n\nIf required, SVER element(s) can have radius applied to create a convex or concave fillet. press the down arrow key and select Fillet Radius, to display the Fillet radius <0mm> prompt. Input a value in the dimension field and press Enter.\n\nThe Specify second corner (fillet radius: 0mm) prompt is displayed, click to identify the second SVER element, or input values into the dimension fields and press Enter.\n\nThe Specify the next corner (fillet radius: 0mm) prompt is displayed, click to identify the next SVER element, or input values into the dimension fields and press Enter.\n\nContinue to identify SVER elements as required, once complete press the down arrow to select Height, the Specify the height prompt is displayed.\n\nClick to identify the height of the extrusion or input a value into the dimension field and press Enter.\nBack\nThe option Back is available during the selection, Back moves back one step.\nBack\nThe option Back is available during the selection, Back moves back one step.\nCircular Torus Primitive\nCreates an circular torus primitive using parameters through a series of prompts in the graphical view. Refer to and for further information.\n\nAfter selecting Create Circular Torus Primitive from the Primitive Gallery, the prompt to Specify the origin is displayed. Click to identify the origin of the circular torus primitive relative to its owner or input values into the dimension fields and press Enter.\n\nThe Specify the start point prompt is displayed, click to identify the start point of the outside radius or input values into the dimension fields and press Enter.\n\nThe Specify the sweep angle prompt is displayed, click to identify the sweep angle of the outside radius or input value into dimension field and press Enter.\n\nThe Specify the tube radius prompt is displayed, click to identify the inside radius or input a value in the dimension field and press Enter.\n\nThroughout the dish primitive creation process, press Esc to cancel the command, additional functionality is also available.\n\nDiameter\nPress the down arrow key and select Diameter to create the inside/outside radius of the circular torus primitive with a specified origin and diameter.\nBack\nThe option Back is available during the selection, Back moves back one step.\nDiameter\nPress the down arrow key and select Diameter to create the inside/outside radius of the circular torus primitive with a specified origin and diameter.\nBack\nThe option Back is available during the selection, Back moves back one step.\nRectangular Torus Primitive\nCreates an rectangular torus primitive using parameters through a series of prompts in the graphical view. Refer to and for further information.\n\nAfter selecting Create Rectangular Torus Primitive from the Primitive Gallery, the Specify the origin prompt is displayed, click to identify the origin of the rectangular torus primitive or input values into the dimension fields and press Enter.\n\nThe Specify sweep angle prompt is displayed, click to identify the sweep angle or input an value in the dimension field and press Enter.\n\nThe Specify the half width prompt is displayed, click to identify the width of the rectangular torus primitive or input a value in the dimension field and press Enter.\n\nThe Specify the height prompt is displayed, click to identify the height of the rectangular torus primitive or input a value in the dimension field and press Enter.\n\nThroughout the rectangular torus primitive creation process, press Esc to cancel the command, additional functionality is available.\n\nTwo Points\nPress the down arrow key and select Two Points to create a rectangular torus primitive (diameter start and end).\nExplicit\nPress the down arrow key and select Explicit to create a rectangular torus primitive with a specified origin, start angle, sweep angle, inner radius, outside radius and height.\nWidth\nPress the down arrow key and select Width of the rectangular torus primitive.\nCentre+\nPress the down arrow key and select Centre+ to create a rectangular torus primitive with a specified center point and a radius.\nBack\nThe option Back is available during the selection, Back moves back one step.\nTwo Points\nPress the down arrow key and select Two Points to create a rectangular torus primitive (diameter start and end).\nExplicit\nPress the down arrow key and select Explicit to create a rectangular torus primitive with a specified origin, start angle, sweep angle, inner radius, outside radius and height.\nWidth\nPress the down arrow key and select Width of the rectangular torus primitive.\nCentre+\nPress the down arrow key and select Centre+ to create a rectangular torus primitive with a specified center point and a radius.\nBack\nThe option Back is available during the selection, Back moves back one step.\nSloped Cylinder Primitive\nCreates an sloped cylinder primitive using parameters through a series of prompts in the graphical view. Refer to for further information.\n\nAfter selecting Create a Sloped Cylinder Primitive from the Primitive Gallery, the Specify the base centre prompt is displayed, click to identify the origin of the sloped cylinder primitive or input values into the dimension fields and press Enter.\n\nThe Specify the diameter prompt is displayed, click to identify the origin of the sloped cylinder or input a value in the dimension field and press Enter.\n\nThe Specify the height prompt is displayed, click to identify the height of the sloped cylinder or input a value in the dimension field and press Enter.\n\nThe Specify Rotation prompt is displayed, click to identify the rotation point for the slope or input a value in the dimension field and press Enter.\n\nThe Specify Angle prompt is displayed, click to identify the angle or input a value in the dimension field and press Enter.\n\nThroughout the sloped cylinder primitive creation process, press Esc to cancel the command, additional functionality is available.\n\nTwo Points\nPress the down arrow key and select Two Points to create the base diameter of the sloped cylinder primitive (diameter start and end).\nExplicit\nPress the down arrow key and select Explicit to create a sloped cylinder primitive with absolute positioning functionality, in this case specified origin, base diameter and height.\nRadius\nPress the down arrow key and select Radius to create the base diameter of the sloped cylinder primitive.\nCentre+\nPress the down arrow key and select Centre+ to specify the base center of the sloped cylinder primitive.\nBack\nPress the down arrow key and select Back to undo the action.\nFinish\nPress the down arrow key and select Finish to end the process.\nTwo Points\nPress the down arrow key and select Two Points to create the base diameter of the sloped cylinder primitive (diameter start and end).\nExplicit\nPress the down arrow key and select Explicit to create a sloped cylinder primitive with absolute positioning functionality, in this case specified origin, base diameter and height.\nRadius\nPress the down arrow key and select Radius to create the base diameter of the sloped cylinder primitive.\nCentre+\nPress the down arrow key and select Centre+ to specify the base center of the sloped cylinder primitive.\nBack\nPress the down arrow key and select Back to undo the action.\nFinish\nPress the down arrow key and select Finish to end the process.\n\nRevolution Primitive\nCreates a revolution primitive (2D shape) using parameters through a series of prompts in the graphical view. Refer to for further information.\nAfter selecting Create a Revolution Primitive from the Primitive Gallery, the Specify origin prompt is displayed, click to identify the origin of the revolution primitive (defines the axis about which the loop is rotated and the plane in which the loop is defined). Or input values into the dimension fields and press Enter.\n\nThe Specify first loop vertex (fillet radius: 0mm) prompt is displayed, click to identify the first loop vertex or input values into the dimension fields and press Enter. Vertices define the outline of the 2D shape\n\nIf required, press the down arrow key to create a convex or concave fillet at this point, this fillet radius becomes the new default.\n\nThe Specify second loop vertex (fillet radius: 0mm) prompt is displayed, click to identify the second loop vertex or input values into the dimension fields and press Enter.\n\nThe Specify next loop vertex (fillet radius: 0mm) prompt is displayed, click to identify the next loop vertex or input values into the dimension fields and press Enter.\n\nContinue identifying the vertices to complete the outline of the 2D shape, after the third selection, the Specify next loop vertex (fillet radius: 0mm) or <Angle> prompt is displayed.\n\nPress the down arrow key to create the angle to which the 2D shape will be rotated around the specified rotation axis.\n\nSelect Angle, the Specify revolution angle prompt is displayed, click to identify the revolution angle or enter an angle in the field and press Enter.\n\nNegative Primitives\nNegative primitives elements are used to represent holes or end preparations for structural items. It specifies the dimensions, orientation and obstruction geometry of each negative primitive.\nAll primitives have an equivalent negative primitives (with the exception of a nozzle primitive) whose attributes are the same but have different names in the design hierarchy.\n\nCreate a Negative Box Primitive\nUse the functionality to create a negative box primitive (NBOX) element, refer to for further information.\nCreate a Negative Cylinder Primitive\nUse the functionality to create a negative cylinder primitive (NCYLI) element, refer to for further information.\nCreate a Negative Cone Primitives\nUse the functionality to create a negative cone primitive (NCONE) element, refer to for further information.\nCreate a Negative Snout Primitive\nUse the functionality to create a negative snout primitive (NSNOU) element, refer to for further information.\nCreate a Negative Pyramid Primitive\nUse the functionality to create a negative pyramid primitive (NPYRA) element, refer to for further information.\nCreate a Negative Dish Primitive\nUse the functionality to create a negative dish primitive (NDISH) element, refer to for further information.\nCreate a Negative Extrusion Primitive\nUse the functionality to create a negative extrusion primitive (NEXTR) element, refer to for further information.\nCreate a Negative Circular Torus Primitive\nUse the functionality to create a negative circular torus primitive (NCTOR) element, refer to for further information.\nCreate a Negative Rectangular Torus Primitive\nUse the functionality to create a negative rectangular torus primitive (NRTOR) element, refer to for further information.\nCreate a Negative Sloped Cylinder Primitive\nUse the functionality to create a negative sloped cylinder primitive (NSLCY) element, refer to for further information.\nCreate a Negative Revolution Primitive\nUse the functionality to create a negative revolution primitive element (NREVO), refer to for further information.\n\nCreate a Negative Box Primitive\nUse the functionality to create a negative box primitive (NBOX) element, refer to for further information.\n\nCreate a Negative Cylinder Primitive\nUse the functionality to create a negative cylinder primitive (NCYLI) element, refer to for further information.\n\nCreate a Negative Cone Primitives\nUse the functionality to create a negative cone primitive (NCONE) element, refer to for further information.\n\nCreate a Negative Snout Primitive\nUse the functionality to create a negative snout primitive (NSNOU) element, refer to for further information.\n\nCreate a Negative Pyramid Primitive\nUse the functionality to create a negative pyramid primitive (NPYRA) element, refer to for further information.\n\nCreate a Negative Dish Primitive\nUse the functionality to create a negative dish primitive (NDISH) element, refer to for further information.\n\nCreate a Negative Extrusion Primitive\nUse the functionality to create a negative extrusion primitive (NEXTR) element, refer to for further information.\n\nCreate a Negative Circular Torus Primitive\nUse the functionality to create a negative circular torus primitive (NCTOR) element, refer to for further information.\n\nCreate a Negative Rectangular Torus Primitive\nUse the functionality to create a negative rectangular torus primitive (NRTOR) element, refer to for further information.\n\nCreate a Negative Sloped Cylinder Primitive\nUse the functionality to create a negative sloped cylinder primitive (NSLCY) element, refer to for further information.\n\nCreate a Negative Revolution Primitive\nUse the functionality to create a negative revolution primitive element (NREVO), refer to for further information.\nCheck the P-point Position of a Primitive\nA primitive contains a number of P-points indicating the position of a primitive. Once a primitive has been created, these P-point positions can be checked, for example, the CYLI primitive shown below displays its P-points.\n\nCreate a Box Primitive\nUse the functionality to create a box primitive (BOX) element in the design hierarchy, refer to for further information.\nCreate a Cylinder Primitive\nUse the functionality to create a cylinder primitive (CYLI) element, refer tor for further information.\nCreate a Cone Primitive\nUse the functionality to create a cone primitive element (CONE), refer to for further information.\nCreate a Snout Primitive\nUse the functionality to create a snout primitive element (SNOU), refer to for further information\nCreate a Pyramid Primitive\nUse the functionality to create a pyramid primitive element (PYRA), refer to for further information.\nCreate a Dish Primitive\nUse the functionality to create a dish primitive element (DISH), refer to for further information.\nCreate a Extrusion Primitive\nUse the functionality to create an extrusion primitive element (EXTR), refer to for further information.\nCreate a Circular Torus Primitive\nUse the functionality to create a circular torus primitive element (CTOR), refer to for further information.\nCreate a Rectangular Torus Primitive\nUse the functionality to create a rectangular torus primitive element (RTOR), refer to for further information.\nCreate a Sloped Cylinder Primitive\nUse the functionality to create a sloped cylinder primitive element (SLCY), refer to for further information.\nCreate a Revolution Primitive\nUse the functionality to create a revolution primitive element (REVO), refer to for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nW - Two Points\nPress the down arrow key and select Two Points to create a box primitive with two specified points (first and opposite corners).\nT - Three Points\nPress the down arrow key and select Three Points to create a box primitive with three specified points (first, opposite and height).\nF - Four Points\nPress the down arrow key and select Four Points to create a box primitive with relative positioning functionality, with four specified points (origin, X, Y,Z).\nE - Explicit\nPress the down arrow key and select Explicit to create a box primitive with absolute positioning functionality, in this case specified origin, width, length and height.\nRadius\nPress the down arrow key and select Radius to create the curved part of the cylinder primitive with a specified center point and radius.\nBack\nPress the down arrow key and select Back to undo the last action.\nTwo Points\nPress the down arrow key and select Two Points to create the curved part of the cone primitive with two specified points (diameter start and end).\nExplicit\nPress the down arrow key and select Explicit to create a cone primitive with an absolute positioning functionality, in this case specified origin, D-top, D-bottom and height.\nCentre+\nPress the down arrow and select Centre+ to create the curved part of the cone primitive with a specified center point and radius/diameter point.\nRadius\nPress the down arrow key and select Radius to create the curved part of the cone primitive with a specified center point and radius.\nBack\nPress the down arrow key and select Back to undo the action.\nTwo Points\nPress the down arrow ke"}
{"Headers": "Nozzle", "Content": "A nozzle is an interface point between the equipment and the connecting Pipework. Nozzles are positioned and oriented (and given a height dimension) like other primitives, but must be selected from the catalog via a Specification (for the bore to be assigned).\n\nUse the Create Nozzle window to define the nozzle specification.\nParameters\nDisplays the Primitives window, indicating the Parameters fields along the axis.\nName\nInput the nozzle name in the Name field.\nSpecification\nSelect a nozzle specification from the drop-down list of available specifications (selected from the catalog via a specification (for the bore to be assigned)).\nInsulation\nSelect an insulation specification from the drop down list of available specifications.\nGeneric Type\nSelect a nozzle type from the drop-down list of available generic types.\nBore\nThe Bore specifies the nominal bore of the nozzle. Select a bore from the drop-down list of available bore sizes.\nHeight\nInput the nozzle height in the Height field.\nTemperature\nInput the temperature to which the pipe can reach (the default is 0degC, this means that the temperature is ignored)\nDuty\nInput a value in the Duty field.\nPressure\nInput the pressure to which the nozzle must withstand (the default is 0pascal).\nDescription\nInput a description in the Description field.\nPurpose\nInput a purpose in the Purpose field.\nParameters\nDisplays the Primitives window, indicating the Parameters fields along the axis.\n\nName\nInput the nozzle name in the Name field.\nSpecification\nSelect a nozzle specification from the drop-down list of available specifications (selected from the catalog via a specification (for the bore to be assigned)).\nInsulation\nSelect an insulation specification from the drop down list of available specifications.\nGeneric Type\nSelect a nozzle type from the drop-down list of available generic types.\nBore\nThe Bore specifies the nominal bore of the nozzle. Select a bore from the drop-down list of available bore sizes.\nHeight\nInput the nozzle height in the Height field.\nTemperature\nInput the temperature to which the pipe can reach (the default is 0degC, this means that the temperature is ignored)\nDuty\nInput a value in the Duty field.\nPressure\nInput the pressure to which the nozzle must withstand (the default is 0pascal).\nDescription\nInput a description in the Description field.\nPurpose\nInput a purpose in the Purpose field.\nClick Create to display the Nozzle in the 3D view or close the Create Nozzle window to discard any inputs.The Modify Nozzle and Positioning Control windows are displayed by default.\n\nUse the positioning, rotation and align with functionality (refer to COMMOM for further information) to orientate the nozzle. For Select Nozzle or Next functionality, refer to Modify Nozzle for further information.\nParameters\nDisplays the Primitives window, indicating the Parameters fields along the axis.\nName\nInput the nozzle name in the Name field.\nSpecification\nSelect a nozzle specification from the drop-down list of available specifications (selected from the catalog via a specification (for the bore to be assigned)).\nInsulation\nSelect an insulation specification from the drop down list of available specifications.\nGeneric Type\nSelect a nozzle type from the drop-down list of available generic types.\nBore\nThe Bore specifies the nominal bore of the nozzle. Select a bore from the drop-down list of available bore sizes.\nHeight\nInput the nozzle height in the Height field.\nTemperature\nInput the temperature to which the pipe can reach (the default is 0degC, this means that the temperature is ignored)\nDuty\nInput a value in the Duty field.\nPressure\nInput the pressure to which the nozzle must withstand (the default is 0pascal).\nDescription\nInput a description in the Description field.\nPurpose\nInput a purpose in the Purpose field.\n\n\n\nModify Nozzle\nCreate Nozzle\nParameters\nPrimitives\nName\nName\nSpecification\nInsulation\nGeneric Type\nBore\nHeight\nHeight\nTemperature\nDuty\nDuty\nPressure\nDescription\nDescription\nPurpose\nPurpose\nCreate\nCreate Nozzle\nModify Nozzle\nPositioning Control\nCOMMOM\nSelect Nozzle\nNext\nModify Nozzle"}
{"Headers": "Navigator PowerWheel", "Content": "Use the Navigation functionality to navigate through the selected equipment or sub-equipment elements hierarchy.\n\n\n\n\nNavigation"}
{"Headers": "Electrical Component", "Content": "An electrical component in equipment, is a connection point between equipment and cables and can represent anything from an individual cable gland to a piece of electrical equipment, such as a generator. Electrical components must be selected from the catalog via a Selection Table. They are positioned and orientated within equipment in the same way as nozzles and primitives.\n\nUse the Create Electrical Component window to select an electrical component from the list of available catalog items. To name the component, either input a Name explicitly in the Name field, or select Autoname from the Name drop-down list.\nIf the project has been configured with User Defined Element Types based on electrical component (ELCONN) element type, they display in the User Defined Type drop-down list. When the electrical component element is created, it is created as the User Defined Type selected from this list. Selecting a User Defined Element Type may change the content of the Selection Table if the table has been configured to filter on element type.\nTo define the overall category of electrical component, select from the Table drop-down list.\nTo define the sub-category of electrical component, select from the Type drop-down list.\nIf required the search results can be grouped in Create Electrical Component window. Select a Column Header, for example RPM, and drag and drop the selection into the Drag a column header here to group by that column field.\nA component can be selected by clicking on a row in the table. Click Properties to display the Modify Properties window, the user can define parameterized data relevant to the selected electrical component.\nIf no parameters are required for the selected component, an Error window displays.\n\nClick Plotfile to display a diagram of the component, if one has been provided, with the component definition. The diagram can also form part of the Modify Properties window.\nTo create the currently selected electrical component, click Create. The component is created at the equipment origin.\n\nNote:\nIf parameterized data is not set, default values are applied.\n\n\n\nCreate Electrical Component\nName\nAutoname\nName\nUser Defined Type\nTable\nType\nCreate Electrical Component\nColumn Header\nRPM\nDrag\na column header here to group by that column\nProperties\nModify Properties\nNote\n:\nError\nPlotfile\nModify Properties\nCreate"}
{"Headers": "Standard Equipment", "Content": "Use the Standard Equipment functionality to build up a parameterized equipment item (templates) based on a specification of standard equipment types. Refer to Design Template for further information. Standard equipment may be selected from a Specification or from a Selection Table as configured in the Equipment catalog. Refer to Specification of Standard Equipment and Selection Table for further information. The selection table option is selected as default.\n\nTo name the equipment,either input a Name explicitly in the Name field, or select Autoname from the Name drop-down list.\nIf the project has been configured with User Defined Element Types based on Equipment, they display in the User Defined Element Type drop-down list. When the equipment element is created, it is created as the User Defined Type selected from this list. Selecting a User Defined Element Type may change the content of the Selection Table if the table has been configured to filter on element type.\n\n\n\nDesign Template\nSpecification of Standard Equipment\nSelection Table\nStandard Equipment\nDesign Template\nSpecification\nSelection Table\nSpecification of Standard Equipment\nSelection Table\nName\nAutoname\nName\nUser Defined Element Type"}
{"Headers": "Equipment Assembly Model Options", "Content": "The simplest approach to modelling Equipment is to create an Equipment element in Model and create a collection of primitives and nozzles under the Equipment element. In this case, no Design Template is used. The approach may be suitable for unique Equipment items that are not reused in the same project or in other projects.\nIn order to model an Equipment item containing Pipe and HVAC connections, and support steelwork, where the Equipment can be selected via an Equipment specification, it is necessary to create an Equipment Template. Refer to Design Template for further information.\n\n\n\nDesign Template\nDesign Template"}
{"Headers": "Modify Equipment", "Content": "Once the 3D Model has been completed it may be necessary to modify and orientate the equipment and sub-equipment elements.\n\n\n"}
{"Headers": "Modify Equipment Specifications", "Content": "The functionality available from the Modify Equipment Specification window enables the specification of the current element to be changed to another from the list of available specifications.\n\nThe name of the currently selected equipment element displays at the top of the Modify Equipment Specification window.\nClick CE to set the currently selected element, from the Model Explorer or graphical view, as the working element.\nStandard equipment may be selected from a Specification or from a Selection Table as configured in the Equipment catalog.\n\n\n\nModify Equipment Specification\nModify Equipment Specification\nCE\nSpecification\nSelection Table"}
{"Headers": "Align Primitives", "Content": "The align primitives functionality enables the alignment of one primitive with another using a graphical operation on the 3D view. The operation involves selecting a P-Point on two different primitives. The first primitive is moved and rotated so that the two identified P-Points are at the same position and point towards each other.\nThe result of the function is identical to the CONNECT command for primitive element connection. Refer to Primitive Element Connection for further information.\nThe Select First P-Point prompt is displayed.\n\nP-Points are displayed as white crosses, the nearest P-Point to the cursor is highlighted. Click to identify the first P-Point and press Enter.\nThe Select Second P-Point to Align prompt is displayed. Click to identify the second P-Point (on a different primitive) and press Enter.\n\nThe P-Point of the first primitive is aligned with the P-Point of the second primitive.\n\nThroughout the align primitives operation, press Esc to cancel the command.\nNote:\nThe default orientation of Extrusion and Revolution P-Points may prohibit the intended primitive alignment.\nNote:\nIf two P-Points are coincident, the P-Point with the highest number in the current element is selected.\n\n\n\nPrimitive Element Connection\nPrimitive Element Connection\nNote\n:\nSelect First P-Point\nEnter\nNote\n:\nSelect Second P-Point to Align\nEnter\nEsc"}
{"Headers": "Modify Nozzle", "Content": "The functionality available from the Modify Nozzle window enables a nozzle element to be modified, repositioned and reorientated, make sure the correct nozzle element is selected as the Current Element (CE) in the Model Explorer.\n\nClick parameters to display the Primitives window, indicating the Parameters fields along the axis for the currently selected primitive. Refer to Nozzle for further information.\nThe parameters fields (such as name, specification, generic type and so on) display the parameters for the currently selected nozzle. The functionality available from the parameters part of the Modify Nozzle window is identical to that available in the Create Nozzle window. Refer to Nozzle for further information.\nUse the Datum part of the Modify Nozzle window to define the datum point for a nozzle. The functionality available from the Datum part of the Modify Nozzle window is identical to that available from positioning control. Refer to COMMON for further information.\nThe Position part of the Modify Nozzle window allows each nozzle to be explicitly positioned with respect to (wrt) another element. The functionality available from the Position part of the Modify Nozzle window is identical to that available from positioning control. Refer to COMMON for further information.\nThe Rotate part of the Modify Nozzle window allows the user to rotate a nozzle about an axis. The functionality available from the Rotate part of the Modify Nozzle window is identical to that available from positioning control. Refer to COMMON for further information.\nThe Align with P-Point part of the Modify Nozzle window allows the user to align the current element with a P-point on another element. The functionality available from the Align P-Point part of the Modify Nozzle window is identical to that available from positioning control Refer to COMMON for further information.\nClick Select Nozzle to select a nozzle using a cursor pick in the graphical view. The Pick Nozzle : prompt is displayed.\nClick Next to modify the nozzle, the Create Nozzle window displays as default. Close the Modify Nozzle window to discard any inputs.\n\n\n\nNozzle\nNozzle\nModify Nozzle\nPrimitives\nParameters\nNozzle\nModify Nozzle\nCreate Nozzle\nNozzle\nModify Nozzle\nDatum\nModify Nozzle\nModify Nozzle\nModify Nozzle\nCOMMON\nRotate\nModify Nozzle\nModify Nozzle\nCOMMON\nModify Nozzle\nModify Nozzle\nSelect Nozzle\nPick Nozzle :\nNext\nCreate Nozzle\nModify Nozzle"}
{"Headers": "Electrical Components", "Content": "The functionality available from the Create Electrical Component window enables a electrical component element to be repositioned and reorientated, make sure the correct electrical component element is selected as the Current Element (CE) in the Model Explorer.\nThe Create Electrical Component window is displayed and is automatically populated with the properties and attributes of the CE as default. The functionality of the Create Electrical Component window has been previously described, refer to Electrical Component for further information.\nTo select another CE, select the correct element is selected in the Model Explorer, then from the Create Electrical Component window, click CE. The Create Electrical Component window is automatically populated with the properties and attributes of the newly selected CE.\n\n\n\nElectrical Component\nCreate Electrical Component\nCreate Electrical Component\nCreate Electrical Component\nElectrical Component\nModel Explorer\nCreate Electrical Component\nCreate Electrical Component"}
{"Headers": "Equipment Origin", "Content": "The origin point of an equipment item can also be modified, make sure the correct element is selected in the Model Explorer.\nEquipment ID Point\nTo modify an equipment origin using a cursor pick in the graphical view, the following prompt is displayed.\n\nEquipment Explicit\nUse the Modify Origin By window to modify an equipment origin using explicit position values.\n\nThe name of the currently selected equipment item displays at the top of the Modify Origin By window.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Enter an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Enter an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Enter an explicit position value in the Position field.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Enter an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Enter an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Enter an explicit position value in the Position field.\nClick Apply to modify the origin point or Cancel to discard any inputs and close the Modify Origin By window.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Enter an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Enter an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Enter an explicit position value in the Position field.\n\n\n\nEquipment ID Point\nEquipment Explicit\nModify Origin By\nModify Origin By\nEast/West\nEast/West\nNorth/South\nNorth/South\nUp/Down\nUp/Down\nApply\nCancel\nModify Origin By"}
{"Headers": "Sub-Equipment Origin", "Content": "Use the Modify SUBE Origin window to change the origin point of a Sub-equipment item, make sure the correct element is selected in the Model Explorer.\nSubEquipment ID point\nTo modify a Sub-equipment origin using a cursor pick in the graphical view, the following prompt is displayed.\n\nSubEquipment Explicit\nUse the Modify SUBE Origin window to modify a Sub-equipment origin using explicit position values.\n\nThe name of the currently selected equipment item displays at the top of the Modify SUBE Origin window.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Enter an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Enter an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Enter an explicit position value in the Position field.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Enter an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Enter an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Enter an explicit position value in the Position field.\nClick Apply to modify the origin point or Cancel to discard any inputs and close the Modify SUBE Origin window.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. Enter an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. Enter an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. Enter an explicit position value in the Position field.\n\n\n\nModify SUBE Origin\nSubEquipment ID point\nSubEquipment Explicit\nModify SUBE Origin\nModify SUBE Origin\nEast/West\nEast/West\nNorth/South\nNorth/South\nUp/Down\nUp/Down\nApply\nCancel\nModify SUBE Origin"}
{"Headers": "Equipment Spatial Associations", "Content": "The Equipment Associations utility allows geometrical constraints to be applied between Equipment and its surroundings for subsequent design checking. An Equipment Association is a design rule that can be checked by the system. The system reports success if a design constraint is satisfied by the model, otherwise it reports a failure.\nIt provides the ability to create, modify, delete and view details of Equipment Associations. Use the separate utility, called the Association Manager, to view these associations. Refer to Association Manager for further information.\n\n\n\nEquipment Associations\nAssociation Manager\nAssociation Manager"}
{"Headers": "Configure the System", "Content": "There are three project set up considerations for this utility, these are administration functions.\n\n\n"}
{"Headers": "Add Association Features to Equipment", "Content": "P-points, Design Points and P-lines can be selected as reference points for Associations. These can be picked in the 3D view when an Association is created.\nIt can be quite difficult to pick a particular graphical point in a 3D view where many elements are displayed. To make it easier to select reference points or lines to be used in an Association, it is recommended that Design Points are created in Design Templates, and P-points in catalog items that identify themselves as connection points for Associations.\nThe user can create Design Points or P-points with the PURPOSE attribute set to a four character value where the first two characters are chosen by the person defining the point, and the last two characters must be 'FA'. For example, an Equipment may be created with three Association Design Points with PURPOSE attributes set to CLFA for center-line, BOFA for bottom face and TOFA for top face. Any number of reference points can be created for each element, but it is recommended that only the most commonly used reference points on each type of Equipment or catalog item are defined in this way, otherwise they become difficult to identify in a 3D view.\n\n\n"}
{"Headers": "Create Equipment Association", "Content": "Use the Equipment Associations window to create, modify, delete an association or change a member of an association. An association comprises a primary and partner element, a geometric constraint and two reference planes.\nTo pick the primary member of the association in the graphical view, click Pick Association Item, the \u2018Pick an Element to associate with :\u2019 prompt is displayed.\n\nSelect the type of geometric association required from the Create a New Association list, refer to for further information.\nTo pick the partner element of the association in the graphical view, the Pick an Element to associate with :\u2019 prompt is displayed.\nThe Association Details part of the Equipment Associations window displays a list of current associations that the primary member participates in. The Associations can be modified, changed or deleted by selecting a row in this list.\n\n\n\nEquipment Associations\nPick Association Item\nPick an Element to associate with :\u2019\nCreate a New Association\n\nPick an Element to associate with :\u2019\nAssociation Details\nEquipment Associations"}
{"Headers": "Modify Association", "Content": "Use the Equipment Associations window to modify an association, click Pick Association Element, the \u2018Pick an Element to Associate with :\u2019 prompt is displayed.\nOnce selected, the Participates in Associations table in the Association Details part of the Equipment Associates window is populated with all of the associations for the picked element by default.\n\nSelect the association from the Participates in Associations table, then select Modify Association, or select Modify from the right-click options menu.\nThe association modification window for the selected association is displayed, modify as required, refer to Identify Reference Geometry, Association Reference Planes and Set Association Parameters for further information.\n\n\n\nIdentify Reference Geometry\nAssociation Reference Planes\nSet Association Parameters\nEquipment Associations\nPick Association Element\nPick an Element to Associate with :\u2019\nParticipates in Associations\nAssociation Details\nEquipment Associates\nParticipates in Associations\nModify Association\nModify\nIdentify Reference Geometry\nAssociation Reference Planes\nSet Association Parameters"}
{"Headers": "Change Association Partner", "Content": "If required the partner element of the association can be modified, from the Equipment Associations window, the prompt \u2018Pick an Element to associate with\u2019 is displayed. Select the new partner element in the graphical view, once selected the Equipment Associations window is automatically updated to reflect the change in the partner element.\n\n\n\nEquipment Associations\n\u2018Pick an Element to associate with\u2019\nEquipment Associations"}
{"Headers": "Delete Association", "Content": "To delete an association, select the association in the table and click Delete Association, or select Delete from the right-click options menu.\n\n\n\nDelete Association\nDelete"}
{"Headers": "Report Associations", "Content": "There are three ways to report on associations without selecting a specific element and showing the equipment association utility:\nInclude association results on a general report, refer to Include Association Results on a General Report for further information\nWrite a specific PML utility to produce customized reports, refer to Write PML Utility to Produce Customized Reports for further information\nProduce a standard association report, refer to Standard Association Report for further information.\nInclude association results on a general report, refer to Include Association Results on a General Report for further information\nInclude association results on a general report, refer to Include Association Results on a General Report for further information\nWrite a specific PML utility to produce customized reports, refer to Write PML Utility to Produce Customized Reports for further information\nWrite a specific PML utility to produce customized reports, refer to Write PML Utility to Produce Customized Reports for further information\nProduce a standard association report, refer to Standard Association Report for further information.\nProduce a standard association report, refer to Standard Association Report for further information.\n\n\n\nInclude Association Results on a General Report\nWrite PML Utility to Produce Customized Reports\nStandard Association Report\nInclude Association Results on a General Report\nWrite PML Utility to Produce Customized Reports\nStandard Association Report"}
{"Headers": "Delete Member of an Association", "Content": "If an element participating in an association is deleted, the TESTEV Association test returns the result FALSE to indicate that the association has failed. It is possible to find out which element has been deleted by inspecting the association members for a bad reference in the AMEMRF attribute.\n\n\n"}
{"Headers": "Create Design Points in the Equipment Application", "Content": "Add Association Features to Equipment describes how design points can be configured to use with the equipment associations utility. The functionality for creating and modifying design points is included in the Equipment discipline to allow design points to be defined directly on an equipment item. Refer to Design Points for further information.\n\n\n\nAdd Association Features to Equipment\nDesign Points\nAdd Association Features to Equipment\n\nDesign Points"}
{"Headers": "Customize Equipment Associations Utility", "Content": "Software developers with a detailed knowledge of the AVEVA product can use the provided APIs (Application Programming Interface) to customise the associations functionality. Refer to the following documents for further information:\n.NET Customization\nData Model\n.NET Customization\n.NET Customization\nData Model\nData Model\n\n\n\n.NET Customization\nData Model\n.NET Customization\nData Model"}
{"Headers": "Manage Associations", "Content": "The Manage Associations functionality enables all the associations created during the current session to be viewed, and if required association worlds or groups can also be created, modified or deleted.\n\n\n\nManage Associations"}
{"Headers": "Equipment Report", "Content": "The Equipment discipline provides functionality to generate reports independently from the supplied reporting functionality. Reports can be generated for all or individual equipment elements, nozzles and electrical components along with all of their attributes or chosen ones. The report once generated can then be exported to Excel for printing or further editing.\n\nUse the Equipment Report window to define the type of equipment element on which the report will be based, and which attributes and/or pseudo attributes will be included in the report. The report output can also be viewed and if necessary sorted then exported to Excel for printing, existing reports can also be opened in Excel from the Equipment Report window.\n\n\n\nEquipment Report\nEquipment Report"}
{"Headers": "Import/Export MEI", "Content": "AVEVA Mechanical Equipment Interface (MEI) is the interface for Model which imports 3D models from STEP AP203 files into 3D models in AVEVA E3D Design and exports 3D geometric models from the Model in STEP format. The resulting files can then be used to import 3D geometry into the systems that can read that format.\n\n\n\nAVEVA Mechanical Equipment Interface (MEI)"}
{"Headers": "Export Model", "Content": "There are two methods to export 3D geometric models from the Model databases in a .stp format, depending on knowledge and access rights.\n\n\n"}
{"Headers": "Export-DXF", "Content": "Use the DXF-Export functionality to extract 3D geometric models from Design databases and output them to a Drawing Interchange File (DXF or binary DXF). The resulting file can then be used to import 3D graphics models into AutoCAD or into other systems that can read DXF format files.\nThere are two methods to extract 3D geometric models, using the GUI or the command window, depending on knowledge and access rights. Refer to DXF-Export using the GUI or Command Window for Exporting DXF for further information.\n\n\n\nDXF-Export using the GUI\nCommand Window for Exporting DXF\nDXF-Export\nDXF-Export using the GUI\nCommand Window for Exporting DXF"}
{"Headers": "HVAC Designer", "Content": "Use the HVAC application to design and detail complex ducting networks within a full 3D environment by selecting components from the HVAC Catalog, and produce a clash free design.\nUsing standard default settings, a conceptual layout can be created and analyzed rapidly, leaving the design details to a later post-approval stage.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nHVAC Catalog\nHVAC Catalog"}
{"Headers": "Hierarchy", "Content": "All database elements are owned by other elements, therefore elements must be created in a strict order.\nThe following database elements are common to all the Design disciplines:\n\nBelow the ZONE level in the HVAC module, the HVAC specific elements are:\nThe HVAC (HVAC) is a top level element in the Design database under which Branch (BRAN) and Spools (HLIST) are created.\nBRANCH (BRAN) Element\nThe Branch (BRAN) is a sequence of HVAC component elements running between two points:\nHVAC Components are single pieces of HVAC used to create a HVAC design. Refer to HVAC Components for a full description.\nThe Spools (HLIST) contains a collection of HVAC Spool elements.\nEach HVAC Spool is a sequence of HVAC components combined together, for ease of fabrication.\nWorld\nSite\nZone\nWorld\nWorld\nSite\nSite\nZone\nZone\nHVAC (HVAC)\nBRANCH (BRAN)\nHVAC Component(s)\nSPOOLS (HSLIST)\nHVAC Spool\nHVAC (HVAC)\nHVAC (HVAC)\nBRANCH (BRAN)\nBRANCH (BRAN)\nHVAC Component(s)\nHVAC Component(s)\nSPOOLS (HSLIST)\nSPOOLS (HSLIST)\nHVAC Spool\nHVAC Spool\nBranch Head\nBranch Tail\nBranch Head\nBranch Head\nBranch Tail\nBranch Tail\n\n\n\nHVAC Components\nHVAC Components"}
{"Headers": "Default Detailing Specification", "Content": "The constructional details of components available from the HVAC Catalog are determined by the current detailing specification. To change the current detailing specification, select the required specification from the drop-down list.\n\nA detailing specification is only available at a Branch level. To use different detailing specifications within a ducting run a new branch must be created at each point where the detailing specification changes.\nNote:\nTo create or modify a detailing specification, refer to the System Administrator.\n\n\n\nHVAC Catalog\nHVAC Catalog\nNote\n:\n."}
{"Headers": "HVAC Window", "Content": "All of the tasks carried out that are associated with the creation or modification of HVAC are initiated from a central HVAC window which acts as a task hub. Depending on selections made in the HVAC window further windows are presented prompting for input.\n\nAfter inputting information in these windows the HVAC window is displayed allowing the workflow to continue.\n\n\n\nHVAC window\nHVAC window\nHVAC window"}
{"Headers": "Available Types", "Content": "After selecting a category of HVAC, choose a specific type of HVAC element from the Available Types list.\nWhen a selection is made from the Available Types drop-down list a separate window is displayed, input specific criteria based on what type of HVAC component is being created. For example: a prompt is displayed \u2018to enter dimensions for a straight piece of \u2018.\n\nIf the correct database hierarchy has not been configured beforehand certain Available Types are not available for selection. For example: certain HVAC elements must reside below other elements in the database hierarchy (an overview of the database hierarchy is described in Hierarchy).\nIf a particular HVAC element cannot be created at the current position in the database hierarchy an error message summarizing the problem is displayed, for example in the following window an error explains that the element being created must reside below an Zone, HVAC Element, HVAC Branch or HVAC Component.\n\nAfter populating the windows that are opened by selecting the Available Type, the HVAC Window is displayed.\nNote:\nThe windows that are presented are as a result of selecting an Available Type.\n\n\n\nHierarchy\ncategory\nAvailable Types\nAvailable Types\nNote\n:\nAvailable Type\nAvailable Types\nHierarchy"}
{"Headers": "Copy ID", "Content": "An existing piece of HVAC or equipment can be copied and then modified to create a new piece of HVAC or equipment.\nClick Copy ID, the prompt Identify element in the 3D View is displayed and the selected element is also displayed in a window.\n\nType in the new attributes for the new piece of HVAC or equipment and then click OK to create the new piece of HVAC or equipment.\nSpecify the Orientation, Position and Plane Positioning to another piece of HVAC of equipment as required.\nNote:\nChoose an existing piece of HVAC or equipment with attributes similar to what is required.\nNote:\nThe window displayed depends on the selection made.\n\n\n\nOrientation\nPosition\nPlane Positioning\nNote\n:\nCopy ID\nIdentify element\nNote\n:\nOK\nOrientation\nPosition\nPlane Positioning"}
{"Headers": "Merge Branches", "Content": "It may be necessary to merge the branches of split HVAC. On the HVAC tab, in the Tools group, click Merge.\nA prompt in the 3D View to First pick a connected branch to merge is displayed, once a connected branch is selected, the name of the branch is displayed at the top of the 3D View. A prompt to Secondly pick the branch to merge to is displayed, select a connected branch, the name of the branch is displayed at the top of the 3D View.\nThe confirm window is displayed, a prompt Do you really want to merge the two branches is displayed.\nClick Yes to merge the selected branches or click No to close the window and discard inputs.\n\n\n\nHVAC\nTools\nMerge\nFirst pick a connected branch to merge\nSecondly pick the branch to merge to\n,\nDo you really want to merge the two branches\nYes\nNo"}
{"Headers": "Work Area", "Content": "Most of the work area is common for all design disciplines, but some areas with respect to the HVAC application can be customized.\n\n\n"}
{"Headers": "PowerWheel", "Content": "Many operations in HVAC discipline can be initiated using the PowerWheel, refer to Common Functionality for further information.\n\nAll of the out of box configurations for the power wheel can be customized, refer to Customizing Guide for further information.\nNote:\nThe equivalent functionality is also available from the HVAC UI.\n\n\n\nCommon Functionality\nCommon Functionality\nNote\n:\nCustomizing Guide"}
{"Headers": "Defaults", "Content": "The default settings used to create the design model are taken from the current defaults file.\nThese default settings make sure you are in compliance with company standards and a high level of design consistency is maintained throughout the project.\nCreated items are generated using these defaults settings, any default setting can be overwritten. All dimensions (metric or imperial) must be compatible with the session units in force.\nThe current defaults file can be changed to use other default settings to comply with company standards and national/international standards.\n\nBrowse and choose an appropriate defaults file.\nNote:\nCADMETRIC.DEF and CADCIMPERIAL.DEF default files are supplied as standard.\n\n\n\nNote\n:"}
{"Headers": "Style", "Content": "Some HVAC windows can be customised by right-clicking on the HVAC window and selecting Styles options from the pop-up menu to display the HVAC Form Style window.\n\nShow Local Views\nSelect the Show Local Views check box to continuously display a 3D graphical view of the current component next to the Create/Modify window.\nDeselect the Show Local Views check box to remove the 3D graphical view.\n\nLocal Views Shade\nChange the appearance of the component in the Local View from a shaded view to a wire line view by selecting or deselecting the Local Views Shade check box. Selecting the check box will display a shaded view and deselecting will display a wire line view.\n\nOK/Apply\nThe Use OK on Create Forms check box allows you to change the OK buttons to Apply buttons on the Create/Modify windows.\nTo display the OK buttons, check the Use OK on Create Forms check box. Selecting this option will close the Create/Modify window when OK is clicked allowing you to only create or modify a single component.\nTo display the Apply buttons, deselect the Use OK on Create Forms check box. Selecting this option will not close the Create/Modify window when Apply is clicked allowing you to create or modify multiple instances of the same component.\nShow Pixmaps\nChoose to display a pictorial representation of the Available Types of components available when a selection is made in the Categories field on the HVAC Window.\nTo display a pictorial representation select the Show Pixmaps check box. For more information on the which representations are available refer to Component Palettes.\nTo remove the pictorial representations deselect the Show Pixmaps check box.\nShow Forms\nChoose whether or not to display the Create/Modify windows by selecting or deselecting the Show Forms check box.\nSelecting the Show Forms check box displays the Create/Modify windows automatically with the addition of a new component allowing you to change the default detailing specifications.\nDeselecting the Show Forms check box prevents the Create/Modify windows automatically displaying with the addition of a new component. Using this option allows you to connect components immediately using the default detailing specifications. You can modify any added component by selecting the component and clicking Modify CE on the HVAC Window.\nNote:\nNone of these style options can be seen until tasks are being performed, refer to HVAC Window.\nNote:\nThe Show Local Views check box must be selected for either option to display.\n\n\n\nHVAC Window\nHVAC Window\nComponent Palettes\nHVAC Window\nStyles options\nHVAC Form Style\nNote\n:\nHVAC Window\nShow Local Views\nShow Local Views\nCreate/Modify\nShow Local Views\nLocal Views Shade\nLocal View\nLocal Views Shade\nNote\n:\nShow Local Views\nOK/Apply\nUse OK on Create Forms\nOK\nApply\nCreate/Modify\nOK\nUse OK on Create Forms\nCreate/Modify\nOK\nApply\nUse OK on Create Forms\nCreate/Modify\nApply\nShow Pixmaps\nAvailable Types\nCategories\nHVAC Window\nShow Pixmaps\nComponent Palettes\nShow Pixmaps\nShow Forms\nShow Forms\nShow Forms\nShow Forms\nModify CE\nHVAC Window"}
{"Headers": "HVAC Window", "Content": "The HVAC Window can be used in either a Full or Brief format. Both the formats perform the same functions except the Full format has an additional option, Plane Positioning. To switch between Full or Brief formats, right-click on the HVAC window and select either Use Full Form or Use Brief Form from the pop-up menu.\nFor further information on the functions common to both forms refer to HVAC Window.\nPlane Positioning\nThe additional positioning aid to position elements defines a reference plane for use as a construction aid.\nThe plane is called the construction plane, the plane is defined in terms of its position (a point through which it passes) and its direction (the direction of a line normal to the plane).\n\nUse this option to define the construction plane\u2019s position and direction:\nPlane Direction\nDefine the direction of the normal to the plane:\nInput a direction.\nCursor\nSpecify the method of identification of a point through which the plane is constructed (p-arrive):\nUse the cursor to pick a new position in the 3D View. Before doing so you should reset the view to a Plan view. The first prompt Enter a 3-d position is used for the east and north coordinates. The view will then flip allowing you to pick a point to be used for the elevation of the element (Enter a 2nd point to define third coordinate).\nID P-Point\nSpecify the method of identification of a point through which the plane is constructed (p-arrive):\nA prompt to identify design ppoint to position the origin of the CE at a chosen P-point in the 3D graphical view is displayed, P-Points are described in the Getting Started with Plant and Basic Features of the Catalogue.\nID Element\nSpecify the method of identification of a point through which the plane is constructed (p-arrive):\nA prompt to identify element to position the origin of the CE at the location of the origin of a selected element in the 3D graphical view is displayed.\nPlane Direction\nDefine the direction of the normal to the plane:\nInput a direction.\nCursor\nSpecify the method of identification of a point through which the plane is constructed (p-arrive):\nUse the cursor to pick a new position in the 3D View. Before doing so you should reset the view to a Plan view. The first prompt Enter a 3-d position is used for the east and north coordinates. The view will then flip allowing you to pick a point to be used for the elevation of the element (Enter a 2nd point to define third coordinate).\nID P-Point\nSpecify the method of identification of a point through which the plane is constructed (p-arrive):\nA prompt to identify design ppoint to position the origin of the CE at a chosen P-point in the 3D graphical view is displayed, P-Points are described in the Getting Started with Plant and Basic Features of the Catalogue.\nID Element\nSpecify the method of identification of a point through which the plane is constructed (p-arrive):\nA prompt to identify element to position the origin of the CE at the location of the origin of a selected element in the 3D graphical view is displayed.\n\nPlane Direction\nDefine the direction of the normal to the plane:\nInput a direction.\nCursor\nSpecify the method of identification of a point through which the plane is constructed (p-arrive):\nUse the cursor to pick a new position in the 3D View. Before doing so you should reset the view to a Plan view. The first prompt Enter a 3-d position is used for the east and north coordinates. The view will then flip allowing you to pick a point to be used for the elevation of the element (Enter a 2nd point to define third coordinate).\nID P-Point\nSpecify the method of identification of a point through which the plane is constructed (p-arrive):\nA prompt to identify design ppoint to position the origin of the CE at a chosen P-point in the 3D graphical view is displayed, P-Points are described in the Getting Started with Plant and Basic Features of the Catalogue.\nID Element\nSpecify the method of identification of a point through which the plane is constructed (p-arrive):\nA prompt to identify element to position the origin of the CE at the location of the origin of a selected element in the 3D graphical view is displayed.\n\n\n\nHVAC Window\nBasic Features of the Catalogue\nPlane Positioning\nHVAC\nUse Full Form\nUse Brief Form\n\nHVAC Window\nPlane Positioning\nPlane Direction\nCursor\nEnter a 3-d position\nEnter a 2nd point to define third coordinate\nID P-Point\nidentify design ppoint\nBasic Features of the Catalogue\nID Element\nidentify element"}
{"Headers": "Component Palettes", "Content": "HVAC Component palettes display a pictorial representation of the components available when you select a Category from the HVAC Window if the Show Pixmaps check box has been selected. Refer to Show Pixmaps for more information.\nTo view the corresponding Create/Modify component window, click the required pixmap on the palette.\nNote:\nNot all the options in the Categories drop-down list have palettes available.\n\n\n\nHVAC Window\nCategory\nHVAC Window\nShow Pixmaps\nCreate/Modify component\nNote\n:"}
{"Headers": "Rectangular Ductwork", "Content": "To display the HVAC Rectangular Ductwork palette, click Rectangular from the Categories drop-down list on the HVAC Window.\n\n\n\n\nHVAC Window\nRectangular\nCategories\nHVAC Window"}
{"Headers": "Circular Ductwork", "Content": "To display the HVAC Circular Ductwork palette, click Circular from the Categories drop-down list on the HVAC Window.\n\n\n\n\nHVAC Window\nCircular\nCategories\nHVAC Window"}
{"Headers": "Flat Oval Ductwork", "Content": "To display the HVAC Flat Oval Ductwork palette, click Flat Oval from the Categories drop-down list on the HVAC Window.\n\n\n\n\nHVAC Window\nFlat Oval\nCategories\nHVAC Window"}
{"Headers": "Shape Transformation Items", "Content": "To display the HVAC Shape Transformation Items palette, click Transformations from the Categories drop-down list on the HVAC Window.\n\n\n\n\nHVAC Window\nTransformations\nCategories\nHVAC Window"}
{"Headers": "Branch Connectors", "Content": "To display the HVAC Branch Connectors palette, click Branch Connectors from the Categories drop-down list on the HVAC Window.\n\n\n\n\nHVAC Window\nBranch Connectors\nCategories\nHVAC Window"}
{"Headers": "Inline Plant Equipment", "Content": "To display the HVAC Inline Plant Equipment palette, click Inline Plant Equipment from the Categories drop-down list on the HVAC Window.\n\n\n\n\nHVAC Window\nPlant Equipment\nCategories\nHVAC Window"}
{"Headers": "Extra Inline Equipment", "Content": "To display the HVAC Extra Equipment palette, click Extra Inline Equipment from the Categories drop-down list on the HVAC Window.\n\n\n\n\nHVAC Window\nExtra Inline Equipment\nCategories\nHVAC Window"}
{"Headers": "Nozzle Items", "Content": "To display the HVAC Nozzle Items palette, click Equipment Nozzles from the Categories drop-down list on the HVAC Window.\n\n\n\n\nHVAC Window\nEquipment Nozzles\nCategories\nHVAC Window"}
{"Headers": "Components", "Content": "In this section, all of the HVAC components available for selection in the catalog database are described. If there is a requirement for a component which is not available, refer to system administrator. The information can be applied to the same processes that are used to create all other types of HVAC component, for a more detailed description of creating a HVAC component, refer to HVAC Components.\n\n\n\nHVAC Components\nHVAC Components"}
{"Headers": "Branches", "Content": "The branches option of the Categories drop-down list is an umbrella for the specific HVAC hierarchical elements which are available from the Available Types drop-down list.\n\n\n\nCategories\nAvailable Types"}
{"Headers": "HVAC System Element", "Content": "A HVAC System Element is a top level element in the design database under which other elements are created, for a more detailed description, refer to HVAC System Element.\n\n\n\nHVAC System Element\nHVAC System Element"}
{"Headers": "Main Branch Element", "Content": "A HVAC Main Branch is a starting point or branch head to which all other HVAC Component elements can be added, for a more detailed description, refer to HVAC Main Branch.\n\n\n\nHVAC Main Branch\nHVAC Main Branch"}
{"Headers": "Side Branch (off main)", "Content": "A HVAC Side Branch allows you to create additional branches off the Main Branch, for a more detailed description, refer to Side Branch.\n\n\n\nSide Branch\nSide Branch"}
{"Headers": "Rectangular", "Content": "The Rectangular option of the Categories drop-down list is an umbrella for the rectangular components for selection in the catalog database.\n\n\n\nRectangular\nCategories"}
{"Headers": "Straight", "Content": "The task of creating a HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Straight in the Available Type drop-down list to display the Straight window:\n\nFor a more detailed description, refer to Create/Modify HVAC Component.\n\n\n\nHVAC Window\nCreate/Modify HVAC Component\nHVAC Component\nHVAC Window\nRectangular\nCategories\nStraight\nAvailable Type\nStraight\nCreate/Modify HVAC Component"}
{"Headers": "Taper", "Content": "The task of creating a HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Taper in the Available Type drop-down list to display the Taper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Taper.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension or to exchange Duct Width LA dimension with Duct Depth LB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the A Offset Direction.\nIn the A Offset Direction enter the direction for the A Offset or B Offset relative to the Point of Origin Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).In the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Taper window was opened.\nClick Fit to orientate the Taper to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Taper component and close the Taper Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Taper window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nDuct Depth LB\nLength\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nTaper\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nTaper\nAvailable Type\nto display\nTaper\nPicture\nTaper\nNote\n:\nHVAC Catalog\nArrive\nLeave Extension\nauto\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nDuct Depth LB\nArrive Joint\nLeave Joint\nCreate/Modify HVAC Component\nArrive Joint\nLeave Joint\nA Offset Direction\nA Offset Direction\nA Offset\nB Offset\nPosition\nNote\n:\nDefaults\nTaper\nFit\nTaper\nOK\nTaper\nTaper\nHVAC Window\nCancel\nTaper"}
{"Headers": "Cranked Taper", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Cranked Taper in the Available Type drop-down list to display the Cranked Taper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Cranked Taper.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension or to exchange Duct Width LA dimension with Duct Depth LB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the A Offset Direction.\nIn the A Offset Direction enter the direction for the A Offset and B Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Cranked Taper window was opened.\nClick Fit to orientate the Cranked Taper to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Cranked Taper component and close the Cranked Taper Window. You will be returned to the HVAC Window\nClick Cancel to discard all field changes and close the Cranked Taper window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nDuct Depth LB\nLength\nA Offset\nB Offset\nA Back Extension\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nA Back Extension\nA Back Extension\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCranked Taper\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nCranked Taper\nAvailable Type\nCranked Taper\nPicture\nCranked Taper\nNote\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nDuct Depth LB\nArrive Joint\nCreate/Modify HVAC Component\nArrive Joint\nLeave Joint\nt Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\nCranked Taper\nHVAC Window\nCancel\nCranked Taper"}
{"Headers": "Square Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Square Bend in the Available Type drop-down list to display the Square Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Square Bend.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn the Leave Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Square Bend was opened.\nClick Fit to orientate the Square Bend to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Square Bend component and close the Square Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Square Bend window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nArrive Throat\nLeave Throat\nInside Radius\nBack Radius\nArrive to Back Fillet\nLeave to Back Fillet\nArrive Throat Fillet\nLeave to Throat Fillet\nAirturn Vanes\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nArrive Throat\nArrive Throat\nLeave Throat\nLeave Throat\nInside Radius\nInside Radius\nBack Radius\nBack Radius\nArrive to Back Fillet\nArrive to Back Fillet\nLeave to Back Fillet\nLeave to Back Fillet\nArrive Throat Fillet\nArrive Throat Fillet\nLeave to Throat Fillet\nLeave to Throat Fillet\nAirturn Vanes\nAirturn Vanes\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog. The Airturns Vanes default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nSquare Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nSquare Bend\nAvailable Type\nSquare Bend\nPicture\nSquare Bend\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct depth AB\nArrive Joint\nCreate/Modify HVAC Component\nArrive Joint\nLeave Joint\nLeave Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\nSquare Bend\nHVAC Window\n.\nCancel\nSquare Bend"}
{"Headers": "Radiused Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Radiused Bend in the Available Type drop-down list to display the Radiused Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Radius Bend.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn the Leave Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to rest all the fields back to when the Radiused Bend window was opened.\nClick Fit to orientate the Radiused Bend to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Radisued Bend component and close the Radiused Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Radiused Bend window.\nDuct Width AA\nDuct Depth AB\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populate with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRadius Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nRadiused Bend\nAvailable Type\nRadiused Bend\nPicture\nRadius Bend\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\nRadiused Bend\nHVAC Window\n.\nCancel\nRadiused Bend"}
{"Headers": "Mitred Elbow", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Mitred Elbow in the Available Type drop-down list to display the Mitred Elbow window:\n\nYou are required to input following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Mitred Elbow.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn the Leave Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Mitred Elbow window was opened.\nClick Fit to orientate the piece of HVAC to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Mitred Elbow component and close the Mitred Elbow Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Mitred Elbow window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nAngle\nArrive Throat\nLeave Throat\nInside Radius\nBack Radius\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nAngle\nAngle\nArrive Throat\nArrive Throat\nLeave Throat\nLeave Throat\nInside Radius\nInside Radius\nBack Radius\nBack Radius\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populate with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nMitred Elbow\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nMitred Elbow\nAvailable Type\nMitred Elbow\nPicture\nMitred Elbow\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\nMitred Elbow\nHVAC Window\nCancel\nMitred Elbow"}
{"Headers": "Crank Offset", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Cranked Offset in the Available Type drop-down list to display the Cranked Offset window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Crank Offset.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the A Offset Direction.\nIn the A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid dimension for are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Cranked Offset window was opened.\nClick Fit to orientate the Cranked Offset to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Cranked Offset component and close the Cranked Offset Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Cranked Offset window.\nDuct Width AA\nDuct Depth AB\nLength\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimension are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCrank Offset\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nCranked Offset\nAvailable Type\nCranked Offset\nPicture\nCrank Offset\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nA Offset Direction\nA Offset Direction\nPosition\nNote\n:\nDefaults\nFit\nCranked Offset\nOK\nCranked Offset\nHVAC Window\nCancel\nCranked Offset"}
{"Headers": "Mitred Offset", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Mitred Offset in the Available Type drop-down list to display the Mitred Offset window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Mitred Offset.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to HVAC Components for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Offset Direction.\nIn the Offset Direction enter the direction for the Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Mitred Offset window was opened.\nClick Fit to orientate the Mitred Offset to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Mitred Offset component and close the Mitred Offset window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Mitred Offset window.\nDuct Width AA\nDuct Depth AB\nDuct width LA\nLength\nA Offset\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct width LA\nDuct width LA\nLength\nLength\nA Offset\nA Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nMitred Offset\nHVAC Catalog\nHVAC Components\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nMitred Offset\nAvailable Type\nMitred Offset\nPicture\nMitred Offset\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nHVAC Components\nOffset Direction\nOffset Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\nMitred Offset\nHVAC Window\n.\nCancel\nMitred Offset"}
{"Headers": "Radiused Offset", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Radiused Offset in the Available Type drop-down list to display the Radiused Offset window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Radius Offset.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Offset Direction.\nIn the Offset Direction enter the direction for the Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Radiused Offset window was opened.\nClick Fit to orientate the Radiused Offset to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Radiused Offset component and close the Radiused Offset Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Radisued Offset window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nLength\nA Offset\nArrive Inside Radius\nArrive Back Radius\nLeave Inside Radius\nLeave Back Radius\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nLength\nLength\nA Offset\nA Offset\nArrive Inside Radius\nArrive Inside Radius\nArrive Back Radius\nArrive Back Radius\nLeave Inside Radius\nLeave Inside Radius\nLeave Back Radius\nLeave Back Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRadius Offset\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nRadiused Offset\nAvailable Type\nRadiused Offset\nPicture\nRadius Offset\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nCreate/Modify HVAC Component\nOffset Direction\nOffset Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\nRadiused Offset\nHVAC Window\nCancel\nRadisued Offset"}
{"Headers": "Radiused Threeway", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Radiused Threeway in the Available Type drop-down list to display the Radiused Threeway window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Radius Threeway.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension or to exchange Second Width dimension with Second Depth dimension.\nSpecify a type of joint to use for the Arrive Joint, Leave Joint and Branch Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, Leave Joint and Branch Joint you must enter the Leave Direction.\nIn the Leave Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).Using the Flip Arrive/Leave drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Radiused Threeway window was opened.\nClick OK to create the Radiused Threeway component and close the Radiused Threeway Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Radiused Threeway window.\nDuct Width AA\nDuct Depth AB\nSecond Width\nSecond Depth\nAngle\nSecond Angle\nInside Radius\nSecond Radius\nBranch A Offset\nBranch B Offset\nArrive Extension\nLeave Extension\nSecond Arrive Extension\nSecond Leave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nSecond Width\nSecond Width\nSecond Depth\nSecond Depth\nAngle\nAngle\nSecond Angle\nSecond Angle\nInside Radius\nInside Radius\nSecond Radius\nSecond Radius\nBranch A Offset\nBranch A Offset\nBranch B Offset\nBranch B Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nSecond Arrive Extension\nSecond Arrive Extension\nSecond Leave Extension\nSecond Leave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRadius Threeway\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nRadiused Threeway\nAvailable Type\nRadiused Threeway\nPicture\nRadius Threeway\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nFlip Arrive/Leave\nPosition\nNote\n:\nDefaults\nOK\nRadiused Threeway\nHVAC Window\nCancel\nRadiused Threeway"}
{"Headers": "TwinBend Threeway", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Twin Bend Threeway in the Available Type drop-down list to display the TwinBend Threeway window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Twin Bend Threeway.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension or to exchange Second Width dimension with Second Depth dimension.\nFrom the Flip Arrive/Leave drop-down list, select Yes or No to flip the direction of arrive and leave of the of the HVAC component.\nSpecify a type of joint to use for the Arrive Joint, Leave Joint and Branch Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn the Leave Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the TwinBend Threeway window was opened.\nClick OK to create the TwinBend Threeway component and close the TwinBend Threeway Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the TwinBend Threeway window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nSecond Width\nSecond Depth\nAngle\nSecond Angle\nInside Radius\nSecond Radius\nBranch B offset\nArrive Extension\nLeave Extension\nSecond Arrive Extension\nSecond Leave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nSecond Width\nSecond Width\nSecond Depth\nSecond Depth\nAngle\nAngle\nSecond Angle\nSecond Angle\nInside Radius\nInside Radius\nSecond Radius\nSecond Radius\nBranch B offset\nBranch B offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nSecond Arrive Extension\nSecond Arrive Extension\nSecond Leave Extension\nSecond Leave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nTwin Bend Threeway\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nTwin Bend Threeway\nAvailable Type\nTwinBend Threeway\nPicture\nTwin Bend Threeway\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nFlip Arrive/Leave\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nNote\n:\nDefaults\nOK\nTwinBend Threeway\nHVAC Window\nCancel\nTwinBend Threeway"}
{"Headers": "Breeches Threeway", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Breeches Threeway in the Available Type drop-down list to display the Breeches Threeway window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Breeches Threeway.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension or to exchange Duct Width LA dimension with Duct Depth LB dimension.\nSpecify a type of joint to use for the Arrive Joint, Leave Joint or Branch Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, Leave Joint and Branch Joint you must enter the Leave Direction.\nIn the Leave Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Breeches Threeway window was opened.\nClick OK to create the Breeches Threeway component and close the Breeches Threeway Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Breeches Threeway window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nDuct Depth LB\nBranch Width\nOverall length\nA Offset\nB Offset\nCutback Depth\nGap\nArrive Extension\nLeave Extension\nBranch Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nBranch Width\nBranch Width\nOverall length\nOverall length\nA Offset\nA Offset\nB Offset\nB Offset\nCutback Depth\nCutback Depth\nGap\nGap\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nBranch Extension\nBranch Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required direction.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nBreeches Threeway\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\n.\nRectangular\nCategories\nBreeches Threeway\nAvailable Type\nBreeches Threeway\nPicture\nBreeches Threeway\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nNote\n:\nDefaults\nOK\nBreeches Threeway\nHVAC Window\nCancel\nBreeches Threeway"}
{"Headers": "Square Threeway", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Square Threeway in the Available Type drop-down list to display the Square Threeway window:\n\nYou are required to input all the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Square Threeway.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint, Leave Joint or Branch Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, Leave Joint or Branch Joint you must enter the Leave Direction.\nIn the Leave Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).In the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Square Threeway window was opened.\nClick OK to create the Square Threeway component and close the Square Threeway Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Square Threeway window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nSecond Width\nArrive Throat\nLeave Throat\nInside Radius\nSecond Arrive Throat\nSecond Leave Throat\nSecond Radius\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nSecond Width\nSecond Width\nArrive Throat\nArrive Throat\nLeave Throat\nLeave Throat\nInside Radius\nInside Radius\nSecond Arrive Throat\nSecond Arrive Throat\nSecond Leave Throat\nSecond Leave Throat\nSecond Radius\nSecond Radius\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nSquare Threeway\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nSquare Threeway\nAvailable Type\nSquare Threeway\nHVAC\nPicture\nSquare Threeway\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nNote\n:\nDefaults\nOK\nSquare Threeway\nHVAC Window\nCancel\nSquare Threeway"}
{"Headers": "Cap End", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Cap End in the Available Type drop-down list to display the Cap End window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Cap End.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint. Refer to HVAC Components for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint you must enter the Width Direction.\nIn the Width Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Cap End window was opened.\nClick OK to create the Cap End component and close the Cap End Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Cap End window.\nDuct Width AA\nDuct Depth AB\nGraphical length\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nGraphical length\nGraphical length\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCap End\nHVAC Catalog\nHVAC Components\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nCap End\nAvailable Type\nCap End\nPicture\nCap End\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nHVAC Components\nWidth Direction\nWidth Direction\nPosition\nNote\n:\nModify\nDefaults\nOK\nCap End\nCap End\nHVAC Window\nCancel\nCap End"}
{"Headers": "Mesh End", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Mesh End in the Available Type drop-down list to display the Rectangular Mesh End window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Mesh End.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nIn the Width Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Rectangular Mesh End window was opened.\nClick OK to create the Rectangular Mesh End component and close the Rectangular Mesh End Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Rectangular Mesh End window.\nDuct Width AA\nDuct Depth AB\nMesh X Spacings\nMesh Y Spacings\nMesh Wire Gauge\nGraphical length\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nMesh X Spacings\nMesh X Spacings\nMesh Y Spacings\nMesh Y Spacings\nMesh Wire Gauge\nMesh Wire Gauge\nGraphical length\nGraphical length\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nMesh End\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nMesh End\nAvailable Type\nRectangular Mesh End\nPicture\nMesh End\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nCreate/Modify HVAC Component\nWidth Direction\nPosition\nNote\n:\nModify\nDefaults\nRectangular Mesh End\nOK\nRectangular Mesh End\nHVAC Window\nCancel\nRectangular Mesh End"}
{"Headers": "Material Connection", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Material Connection in the Available Type drop-down list to display the Material Connection window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Material Connection.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Use this type of joint for the inlet side of the component. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Width Direction.\nIn the Width Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Material Connection window was opened.\nClick Fit to orientate the Material Connection to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Material Connection component and close the Material Connection Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Material Connection window.\nDuct Width AA\nDuct Depth AB\nOverall length\nMat\u2019l Thickness\nArrive Slipover\nLeave Slipover\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nOverall length\nOverall length\nMat\u2019l Thickness\nMat\u2019l Thickness\nArrive Slipover\nArrive Slipover\nLeave Slipover\nLeave Slipover\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nMaterial Connection\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nMaterial Connection\nAvailable Type\nMaterial Connection\nPicture\nMaterial Connection\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nCreate/Modify HVAC Component\nWidth Direction\nWidth Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\nMaterial Connection\nHVAC Window\nCancel\nMaterial Connection"}
{"Headers": "Weather Skirt", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Weather Skirt in the Available Type drop-down list to display the Weather Skirt window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Weather Skirt.\nIn the A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Weather Skirt window was opened.\nClick Fit to Next to orientate the Weather Skirt to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Weather Skirt component and close the Weather Skirt Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Weather Skirt window.\nSkirt Width AA\nSkirt Depth AB\nDuct Width LA\nDuct Depth LB\nDistance from Leave\nHeight\nA Offset\nB Offset\nFirst Extension\nLast Extension\nSkirt Width AA\nSkirt Width AA\nSkirt Depth AB\nSkirt Depth AB\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nDistance from Leave\nDistance from Leave\nHeight\nHeight\nA Offset\nA Offset\nB Offset\nB Offset\nFirst Extension\nFirst Extension\nLast Extension\nLast Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nWeather Skirt\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nWeather Skirt\nAvailable Type\nWeather Skirt\nPicture\nWeather Skirt\nNote\n:\nHVAC Catalog\nA Offset Direction\nPosition\nNote\n:\nDefaults\nFit to Next\nOK\nWeather Skirt\nHVAC Window\nCancel\nWeather Skirt"}
{"Headers": "Two Bend Set-fill", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nFrom the HVAC Window select Rectangular in the Categories drop-down list and then Two Bend Setfill in the Available Type drop-down list to display the Two Bend Set-fill window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to actual piece of HVAC click Picture to display a detailed drawing for Two Bend Setfill.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint for both the 1st and 2nd Bends. Refer to Create/Modify HVAC Component for a detailed description.\nClick Defaults to reset all the fields back to when the Two Bend Setfill window.\nClick OK to create the Two Bend Setfill component and close the Two Bend Setfill Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Two Bend Setfill window.\nDuct Width AA\nDuct Depth AB\nInside Radius\n1st Bend - Arrive Extension\n1st Bend - Leave Extension\n2nd Bend - Arrive Extension\n2nd Bend - Leave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nInside Radius\nInside Radius\n1st Bend - Arrive Extension\n1st Bend - Arrive Extension\n1st Bend - Leave Extension\n1st Bend - Leave Extension\n2nd Bend - Arrive Extension\n2nd Bend - Arrive Extension\n2nd Bend - Leave Extension\n2nd Bend - Leave Extension\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension for the 1st and 2nd Bends default is auto but can be changed by you to a required dimension.\n\n\n\nHVAC Window\nHVAC Window\nTwo Bend Setfill\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nHVAC Window\nRectangular\nCategories\nTwo Bend Setfill\nAvailable Type\nTwo Bend Set-fill\nPicture\nTwo Bend Setfill\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nDefaults\nOK\nTwo Bend Setfill\nHVAC Window\nCancel"}
{"Headers": "Stiffening", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Stiffening in the Available Type drop-down list to display the Stiffening window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Stiffener.\nThe application has automatically calculated the required number of stiffeners to support the CE (using the current detailing specification and other parameters). The number is displayed in the Spec Requirement box.\nThe number of sides of the CE is automatically input into the Number of Sides box, in this case as the CE is a rectangular straight the number of sides is input as 4.\nClick OK Spec Requirement to confirm the automatically generated number of stiffeners is compatible with the detailing specification.\nIf this is not required, click Q Spec Req, to change the automatically generated number of stiffeners.\nAfter selecting the Spec Requirement you must enter the A Offset Direction.\nIn the A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Stiffening window was opened.\nClick OK to create the Stiffening Flanges and close the Stiffening window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Stiffening window.\nStiffener Width\nStiffener Depth\nDuct Width LA\nDuct Depth LB\nSpec Requirement\nNumber of Sides\nFace from Leave\nA Offset\nB Offset\nAngle\nStiffener Face\nOther Web\nWeb Thickness\nStiffener Width\nStiffener Width\nStiffener Depth\nStiffener Depth\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nSpec Requirement\nSpec Requirement\nNumber of Sides\nNumber of Sides\nFace from Leave\nFace from Leave\nA Offset\nA Offset\nB Offset\nB Offset\nAngle\nAngle\nStiffener Face\nStiffener Face\nOther Web\nOther Web\nWeb Thickness\nWeb Thickness\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ords 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ords 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ords 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nStiffening flanges are configured to suit each different component.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nStiffener\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nStiffening\nAvailable Type\nStiffening\nPicture\nStiffener\nNote\n:\nHVAC Catalog\nSpec Requirement\nNumber of Sides\nNote\n:\nOK Spec Requirement\nQ Spec Req\nA Offset Direction\nConnect\nUnchanged\nConnect\nUnchanged\nNote\n:\nModify\nDefaults\nOK\nHVAC Window\nCancel"}
{"Headers": "Access Panel", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Access Panel in the Available Type drop-down list to display the Access Panel window:\n\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Access Panel.\nClick Transpose Width/Depth to exchange Access Panel Width dimension with Access Panel Height dimension or to exchange MAIN Width LA dimension with MAIN Width LB dimension.\nIn Panel Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Clash Vol fields will be pre-populated with the obstruction volumes associated with the access panel and the ducting, but can be changed by you to the required joint.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Access Panel window was opened.\nClick Fit To Next to orientate the Access Panel to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Access Panel component and close the Access Panel Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Access Panel window.\nYou can select a standard stock access panel, using Select Size drop-down list, the Access Panel (W) and Access Panel (H) fields are populated with the standard sizes. If a standard stock size is not required, input the following dimensions:\nAccess Panel Width\nAccess Panel Height\nMAIN Width LA\nMAIN Depth LB\nFace over Duct\nDistance from Leave\nAdjustments Offset\nLateral Offset\nAngle Of Slope\nFixing to Duct\nInner Extension\nPanel Direction\nYou can select a standard stock access panel, using Select Size drop-down list, the Access Panel (W) and Access Panel (H) fields are populated with the standard sizes. If a standard stock size is not required, input the following dimensions:\nYou can select a standard stock access panel, using Select Size drop-down list, the Access Panel (W) and Access Panel (H) fields are populated with the standard sizes. If a standard stock size is not required, input the following dimensions:\nAccess Panel Width\nAccess Panel Width\nAccess Panel Height\nAccess Panel Height\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nFace over Duct\nFace over Duct\nDistance from Leave\nDistance from Leave\nAdjustments Offset\nAdjustments Offset\nLateral Offset\nLateral Offset\nAngle Of Slope\nAngle Of Slope\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nPanel Direction\nPanel Direction\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nAccess Panel\nHVAC Catalog\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nAccess Panel\nAvailable Type\nAccess Panel\nSelect Size\nPicture\nAccess Panel\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nAccess Panel Width\nAccess Panel Height\nMAIN Width LA\nMAIN Width LB\nPanel Direction\nPosition\nNote\n:\nDefaults\nFit To Next\nOK\nAccess Panel\nHVAC Window\nCancel\nAccess Panel"}
{"Headers": "Test Holes", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nFrom the HVAC Window select Rectangular in the Categories drop-down list and then Test Point in the Available Type drop-down list to display the Test Holes window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Test Holes.\nClick Transpose Width/Depth to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nIn Holes Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Clash Vol fields will be pre-populated with the obstruction volumes associated with the access panel and the ducting, but can be changed by you.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Test Holes window was opened.\nClick Fit To Next to orientate the Test Holes to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Test Holes component and close the Test Holes Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Test Holes window.\nNo Of Test Holes\nTest Hole Diameter\nTest Hole Height\nMAIN Width LA\nMAIN Depth LB\nDistance from Leave\nLateral Offset\nInner Extension\nNo Of Test Holes\nNo Of Test Holes\nTest Hole Diameter\nTest Hole Diameter\nTest Hole Height\nTest Hole Height\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nDistance from Leave\nDistance from Leave\nLateral Offset\nLateral Offset\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The No of Test Holes default is as defined in the HVAC Catalog but can be changed by you.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nTest Holes\nHVAC Window\nHVAC Component\nHVAC Window\nHVAC Window\nRectangular\nCategories\nTest Point\nAvailable Type\nTest Holes\nNote\n:\nHVAC Catalog\nHVAC Catalog\nPicture\nTest Holes\nTranspose Width/Depth\nMAIN Width LA\nMAIN Depth LB\nHoles Direction\nPosition\nNote\n:\nDefaults\nFit To Next\nOK\nTest Holes\nHVAC Window\n.\nCancel\nTest Holes"}
{"Headers": "\u2018A\u2019 Plane Splitter", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then \u2018A\u2019 Plane Splitter in the Available Type drop-down list to display the \u2018A\u2019Plane Splitter window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for \u2018A\u2019 Plane Splitter.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Width AB dimension or to exchange Duct Width LA dimension with Duct Width LB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the A Offset Direction.\nIn A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).In the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the \u2018A\u2019 Plane Splitter window was opened.\nClick Fit to orientate the \u2018A\u2019 Plane Splitter to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the \u2018A\u2019 Plane Splitter component and close the \u2018A\u2019 Plane Splitter Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the \u2018A\u2019 Plane Splitter window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nDuct Depth LB\nLength\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nSplitter F Offset\nSplitter L Offset\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nSplitter F Offset\nSplitter F Offset\nSplitter L Offset\nSplitter L Offset\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018A\u2019 Plane Splitter\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\n\u2018A\u2019 Plane Splitter\nAvailable Type\n\u2018A\u2019Plane Splitter\nPicture\n\u2018A\u2019 Plane Splitter\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Width AB\nDuct Width LA\nDuct Width LB\nCreate/Modify HVAC Component\nA Offset Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\n\nHVAC Window\nCancel"}
{"Headers": "\u2018B\u2019 Plane Splitter", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then \u2018B\u2019 Plane Splitter in the Available Type drop-down list to display the \u2018B\u2019Plane Splitter window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for \u2018B\u2019 Plane Splitter.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Width AB dimension or to exchange Duct Width LA dimension with Duct Width LB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the A Offset Direction.\nIn A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).In the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the \u2018B\u2019 Plane Splitter window was opened.\nClick Fit to orientate the \u2018B\u2019 Plane Splitter to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the \u2018B\u2019 Plane Splitter component and close the \u2018B\u2019 Plane Splitter Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the \u2018B\u2019 Plane Splitter window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nDuct Depth LB\nLength\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nSplitter F Offset\nSplitter L Offset\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nSplitter F Offset\nSplitter F Offset\nSplitter L Offset\nSplitter L Offset\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018B\u2019 Plane Splitter\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\n\u2018B\u2019 Plane Splitter\nAvailable Type\n\u2018B\u2019Plane Splitter\nPicture\n\u2018B\u2019 Plane Splitter\nNote\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Width AB\nDuct Width LA\nDuct Width LB\nCreate/Modify HVAC Component\nA Offset Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\n\nHVAC Window\nCancel"}
{"Headers": "Radiused Splitter", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Radiused Splitter in the Available Type drop-down list to display the Radiused Splitter window:\n\nYou are required to input dimensions for the new HVAC Component:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Radius Splitter.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to clear all the dimension currently in the window and set them to the dimension when the window was first opened.\nClick Fit to orientate the piece of HVAC to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Rectangular Radiused Splitter element in the Design database and close the Radiused Splitter Window. You will be returned to the HVAC Window.\nClick Cancel to close the Radiused Splitter window and discard any dimension input in the fields.\nDuct Width AA\nDuct Depth AB\nAngle\nBend Inside Radius\nBend Arrive Extension\nBend Leave Extension\nSplitter Radius\nSplitter Arrive Extension\nSplitter Leave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nAngle\nAngle\nBend Inside Radius\nBend Inside Radius\nBend Arrive Extension\nBend Arrive Extension\nBend Leave Extension\nBend Leave Extension\nSplitter Radius\nSplitter Radius\nSplitter Arrive Extension\nSplitter Arrive Extension\nSplitter Leave Extension\nSplitter Leave Extension\nClick Connect (default when create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated dimensions. These dimensions are governed by the detailed defined in the HVAC Catalog.\n\n\n\nHVAC Window\nRadius Splitter\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nRadiused Splitter\nAvailable Type\nRadiused Splitter\nPicture\nRadius Splitter\nNote\n:\nHVAC Catalog\nPosition\nDefaults\nFit\nOK\nRadiused Splitter\nHVAC Window\nCancel\nRadiused Splitter"}
{"Headers": "Deflectrol", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Deflectrol in the Available Type drop-down list to display the Deflectrol window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Deflectrol.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension to exchange Deflectrol Width dimension with Deflectrol Depth dimension.\nIn Deflectrol Direction specify the axis to be used. Valid axes for are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Deflectrol window was opened.\nClick Fit to orientate the Deflectrol component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Deflector component and close the Deflector Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the filed changes and close the Deflector window.\nDuct Width AA\nDuct Depth AB\nDeflectrol Width\nDeflectrol Depth\nDistance from Leave\nB Offset\nFirst Side Offset\nLeave Side Offset\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDeflectrol Width\nDeflectrol Width\nDeflectrol Depth\nDeflectrol Depth\nDistance from Leave\nDistance from Leave\nB Offset\nB Offset\nFirst Side Offset\nFirst Side Offset\nLeave Side Offset\nLeave Side Offset\nClick Connect (default when create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated dimensions. These dimensions are governed by the detailed defined in the HVAC Catalog.\n\n\n\nHVAC Window\nDeflectrol\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nDeflectrol\nAvailable Type\nDeflectrol\nPicture\nDeflectrol\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDeflectrol Direction\nPosition\nDefaults\nFit\nOK\nDeflector\nHVAC Window\n.\nCancel\nDeflector"}
{"Headers": "Internal Damper", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Internal Damper in the Available Type drop-down list to display the Internal Damper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Internal Damper.\nClick Transpose Width/Depth to exchange the Duct Width AA dimension with Duct Depth AB dimension.\nIn Handle Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Clash Vol fields will be pre-populated with the obstruction volumes associated with the access panel and the ducting, but can be changed by you.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Internal Damper window was opened.\nClick Fit To Next to orientate the Internal Damper to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Internal Damper component and close the Internal Damper Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Internal Damper window.\nDuct Width AA\nDuct Depth AB\nDistance From Leave\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDistance From Leave\nDistance From Leave\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nInternal Damper\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nInternal Damper\nAvailable Type\nInternal Damper\nNote\n:\nHVAC Catalog\nPicture\nInternal Damper\nTranspose Width/Depth\nHandle Direction\nPosition\nNote\n:\nDefaults\nFit To Next\nOK\nInternal Damper\nHVAC Window\nCancel\nInternal Damper"}
{"Headers": "Gasket", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Gasket in the Available Type drop-down list to display the Gasket window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Gasket.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nIn Width Direction enter the specify the Axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).In the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Gasket window was opened.\nClick Fit to orientate the Gasket to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Gasket component and close the Gasket Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Gasket window.\nDuct Width AA\nDuct Depth AB\nThickness\nFlange Face\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nThickness\nThickness\nFlange Face\nFlange Face\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the piece of HVAC at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the piece of HVAC at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the piece of HVAC at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the piece of HVAC but positions it at 0.00, in effect in a floating position.\n\n\n\nGasket\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC\nRectangular\nCategories\nGasket\nAvailable Type\nGasket\nPicture\nGasket\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nWidth Direction\nNote\n:\nDefaults\nFit\nOK\nGasket\nHVAC Window\nCancel\nGasket"}
{"Headers": "Turning Vanes", "Content": "The task of creating HVAC Component is initiated from the HVAC Window.\nSelect Rectangular in the Categories drop-down list and then Turning Vanes in the Available Type drop-down list to display the Turning Vanes window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Turning Vanes.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nUsing the Direction option buttons you can choose which direction the air turning vanes are be directed relative to the Leave Direction.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Turning Vanes window was opened.\nClick Fit to orientate the Turning Vanes to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Turning Vanes component and close the Turning Vanes Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Turning Vanes window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nLeave Throat\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nLeave Throat\nLeave Throat\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the piece of HVAC at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the piece of HVAC at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the piece of HVAC at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the piece of HVAC but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nTurning Vanes\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nRectangular\nCategories\nTurning Vanes\nAvailable Type\nTurning Vanes\nPicture\nTurning Vanes\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nNote\n:\nDefaults\nFit\nOK\nTurning Vanes\nHVAC Window\n.\nCancel\nTurning Vanes"}
{"Headers": "Circular", "Content": "The circular option of the Categories drop-down list is an umbrella for the circular components for selection in the catalog database.\n\n\n"}
{"Headers": "Circular Straight", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Straight in the Available Type drop-down list to display the Circular Straight window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Straight.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Circular Straight window was opened.\nClick Fit to orientate the Circular Straight component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Circular Straight component and close the Circular Straight Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Circular Straight window.\nDuct Diameter\nLength\nDuct Diameter\nDuct Diameter\nLength\nLength\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nStraight\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nStraight\nAvailable Type\nCircular Straight\nPicture\nStraight\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nPosition\nNote\n:\nDefaults\nFit\nOK\nCircular\nStraight\nHVAC Window\nCancel\nCircular Straight"}
{"Headers": "Male Coupling", "Content": "The task of creating a HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Male Coupling in the Available Type drop-down list to display the Male Coupling window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions acute to the actual piece of HVAC, click Picture to display a detailed drawing for Male Coupling.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Male Coupling window was opened.\nClick Fit to orientate the Male Coupling component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Male Coupling component and close the Male Coupling Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Male Coupling window.\nDuct Diameter\nLength\nMale Collar (A)\nMale Collar (L)\nDuct Diameter\nDuct Diameter\nLength\nLength\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nMale Coupling\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nMale Coupling\nAvailable Type\nMale Coupling\nPicture\nMale Coupling\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nPosition\nNote\n:\nDefaults\nFit\nOK\nMale Coupling\nHVAC Window\nCancel\nMale Coupling"}
{"Headers": "Taper", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Taper in the Available Type drop-down list to display the Circular Taper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Taper.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the A Offset Direction.\nIn A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Circular Taper window was opened.\nClick Fit to orientate the Circular Taper component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Circular Taper component and close the Circular Taper Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Circular Taper window.\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018L\u2019\nLength\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nMale Collar (A)\nMale Collar (L)\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018L\u2019\nDuct Diameter \u2018L\u2019\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nTaper\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nTaper\nAvailable Type\nCircular Taper\nPicture\nTaper\nNote\n:\nHVAC Catalog\nArrive and Leave Extension\nCreate/Modify HVAC Component\nA Offset Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\nCircular Taper\nHVAC Window\nCancel"}
{"Headers": "Mitred Offset", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Mitred Offset in the Available Type drop-down list to display the Mitred Offset window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Mitred Offset.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Offset Direction.\nIn Offset Direction enter the direction of the Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Mitred Offset window was opened.\nClick Fit to orientate the Mitred Offset component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Mitred Offset component and close the Mitred Offset Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Mitred Offset window.\nDuct Diameter\nLength\nOffset\nArrive CL Throat\nLeave CL Throat\nMale Collar (A)\nMale Collar (L)\nDuct Diameter\nDuct Diameter\nLength\nLength\nOffset\nOffset\nArrive CL Throat\nArrive CL Throat\nLeave CL Throat\nLeave CL Throat\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nMitred Offset\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nMitred Offset\nAvailable Type\nMitred Offset\nPicture\nMitred Offset\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nOffset Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\nMitred Offset\nHVAC Window\nCancel"}
{"Headers": "Elbow", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Mitred Elbow in the Available Type drop-down list to display the Circular Elbow window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Mitred Elbow.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the axes that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Circular Elbow window was opened.\nClick Fit to orientate the Circular Elbow component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Circular Elbow component and close the Circular Elbow Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Circular Elbow window.\nDuct Diameter\nAngle\nArrive Throat\nLeave Throat\nMale Collar (A)\nMale Collar (L)\nDuct Diameter\nDuct Diameter\nAngle\nAngle\nArrive Throat\nArrive Throat\nLeave Throat\nLeave Throat\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nMitred Elbow\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Window\nCircular\nCategories\nMitred Elbow\nAvailable Type\nCircular Elbow\nPicture\nMitred Elbow\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nLeave Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\nCircular Elbow\nHVAC Window\nCancel"}
{"Headers": "Radiused Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Radiused Bend in the Available Type drop-down list to display the Radiused Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Radius Bend.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the axes that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Radiused Bend window was opened.\nClick Fit to orientate the Radiused Bend component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Radiused Bend component and close the Radiused Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Radiused Bend window.\nDuct Diameter\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nMale Collar (A)\nMale Collar (L)\nDuct Diameter\nDuct Diameter\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRadius Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nRadiused Bend\nAvailable Type\nRadiused Bend\nPicture\nRadius Bend\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nLeave Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\nRadiused Bend\nHVAC Window\nCancel\nRadiused Bend"}
{"Headers": "3 Segment Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then 3 Segment Bend in the Available Type drop-down list to display the 3 Segment Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for 3 Segment Bend.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the axes that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the 3 Segment Bend window was opened.\nClick Fit to orientate the 3 Segment Bend component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the 3 Segment Bend component and close the 3 Segment Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the 3 Segment Bend window.\nDuct Diameter\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nMale Collar (A)\nMale Collar (L)\nDuct Diameter\nDuct Diameter\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n3 Segment Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Window\nCircular\nCategories\n3 Segment Bend\nAvailable Type\n3 Segment Bend\nPicture\n3 Segment Bend\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nLeave Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\n3 Segment Bend\nHVAC Window\nCancel\n3 Segment Bend"}
{"Headers": "4 Segment Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then 4 Segment Bend in the Available Type drop-down list to display the 4 Segment Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for 4 Segment Bend.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the axes that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the 4 Segment Bend window was opened.\nClick Fit to orientate the 4 Segment Bend component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the 4 Segment Bend component and close the 4 Segment Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the 4 Segment Bend window.\nDuct Diameter\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nMale Collar (A)\nMale Collar (L)\nDuct Diameter\nDuct Diameter\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n4 Segment Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\n4 Segment Bend\nAvailable Type\nPicture\n4 Segment Bend\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nLeave Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\n4 Segment Bend\nHVAC Window\nCancel\n4 Segment Bend"}
{"Headers": "5 Segment Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then 5 Segment Bend in the Available Type drop-down list to display the 5 Segment Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for 5 Segment Bend.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the axes that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the 5 Segment Bend window was opened.\nClick Fit to orientate the 5 Segment Bend component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the 5 Segment Bend component and close the 5 Segment Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the 5 Segment Bend window.\nDuct Diameter\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nMale Collar (A)\nMale Collar (L)\nDuct Diameter\nDuct Diameter\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n5 Segment Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nn HVAC Component\nHVAC Window\nCircular\nCategories\n5 Segment Bend\nAvailable Type\n5 Segment Bend\nPicture\n5 Segment Bend\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nLeave Direction\nPosition\nNote\n:\nDefaults\nFit\nOK\n5 Segment Bend\nHVAC Window\nCancel\n5 Segment Bend"}
{"Headers": "7 Segment Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then 7 Segment Bend in the Available Type drop-down list to display the 7 Segment Bend window:\n\nYou are required to input the following dimensions:\nTo visualized how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for 5 Segment Bend.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the axes that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the 7 Segment Bend window was opened.\nClick Fit to orientate the 7 Segment Bend component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the 7 Segment Bend component and close the 5 Segment Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the 7 Segment Bend window.\nDuct Diameter\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nMale Collar (A)\nMale Collar (L)\nDuct Diameter\nDuct Diameter\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n5 Segment Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nn HVAC Component\nHVAC Window\nCircular\nCategories\n7 Segment Bend\nAvailable Type\n7 Segment Bend\nPicture\n5 Segment Bend\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nLeave Direction\nPosition\nNote\n:\nDefaults\nFit\n7\nOK\n5 Segment Bend\nHVAC Window\nCancel\n7 Segment Bend"}
{"Headers": "Radiused Threeway", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Radiused Threeway in the Available Type drop-down list to display the Radiused Threeway window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Radius Threeway.\nSpecify a type of joint to use for the Arrive Joint, Leave Joint and Branch Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn the Leave Direction specify the axes that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nUsing the Flip Arrive/Leave drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Radiused Threeway window was opened.\nClick Fit to orientate the Radiused Threeway to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Radiused Threeway component and close the Radiused Threeway Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Radiused Threeway window.\nDuct Diameter\nSecond Diameter\nAngle\nSecond Angle\nInside Radius\nSecond Radius\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nSecond Arrive Extension\nSecond Leave Extension\nMale Collar (A)\nMale Collar (L)\nMale Collar (B)\nDuct Diameter\nDuct Diameter\nSecond Diameter\nSecond Diameter\nAngle\nAngle\nSecond Angle\nSecond Angle\nInside Radius\nInside Radius\nSecond Radius\nSecond Radius\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nSecond Arrive Extension\nSecond Arrive Extension\nSecond Leave Extension\nSecond Leave Extension\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nMale Collar (B)\nMale Collar (B)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRadius Threeway\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nn HVAC Component\nHVAC Window\nCircular\nCategories\nRadiused Threeway\nAvailable Type\nRadiused Threeway\nPicture\nRadius Threeway\nNote\n:\nHVAC Catalog\nArrive Joint\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nFlip Arrive/Leave\nPosition\nNote\n:\nDefaults\nFit\nOK\nRadiused Threeway\nHVAC Window\nCancel\nRadiused Threeway"}
{"Headers": "Circular Breeches", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Breeches in the Available Type drop-down list to display the Circular Breeches window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Breeches.\nSpecify a type of joint to use for the Arrive Joint, Leave Joint and Branch Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn the Leave Direction specify the axes that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nUsing the Flip Arrive/Leave drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Radiused Threeway window was opened.\nClick Fit to orientate the Radiused Threeway to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Radiused Threeway component and close the Radiused Threeway Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Radiused Threeway window.\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018L\u2019\nDuct Diameter \u2018B\u2019\nLength\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nBranch Extension\nMale Collar (A)\nMale Collar (L)\nMale (Collar B)\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018L\u2019\nDuct Diameter \u2018L\u2019\nDuct Diameter \u2018B\u2019\nDuct Diameter \u2018B\u2019\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nBranch Extension\nBranch Extension\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nMale (Collar B)\nMale (Collar B)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive, Leave and Branch Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nBreeches\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nBreeches\nAvailable Type\nCircular Breeches\nPicture\nBreeches\nNote\n:\nHVAC Catalog\nArrive Joint\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nFlip Arrive/Leave\nPosition\nNote\n:\nDefaults\nRadiused Threeway\nFit\nRadiused Threeway\nOK\nRadiused Threeway\nHVAC Window\nCancel\nRadiused Threeway"}
{"Headers": "Angled Breeches", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Angled Breeches in the Available Type drop-down list to display the Angled Breeches window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Angled Breeches.\nSpecify a type of joint to use for the Arrive Joint, Leave Joint and Branch Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the A Offset Direction.\nIn the A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid dimension for are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nUsing the Flip Arrive/Leave drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Angled Breeches window was opened.\nClick Fit to orientate the Angled Breeches to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Angled Breeches component and close the Angled Breeches Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Angled Breeches window.\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018L\u2019\nDuct diameter \u2018B\u2019\nLength\nBranch Length\nAngle\nB Offset\nArrive Extension\nLeave Extension\nBranch Extension\nMale Collar (A)\nMale Collar (L)\nMale Collar (B)\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018L\u2019\nDuct Diameter \u2018L\u2019\nDuct diameter \u2018B\u2019\nDuct diameter \u2018B\u2019\nLength\nLength\nBranch Length\nBranch Length\nAngle\nAngle\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nBranch Extension\nBranch Extension\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nMale Collar (B)\nMale Collar (B)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive, Leave and Branch Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nAngled Breeches\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC\nCircular\nCategories\nAngled Breeches\nAvailable Type\nAngled Breeches\nPicture\nAngled Breeches\nNote\n:\nHVAC Catalog\nArrive Joint\nCreate/Modify HVAC Component\nA Offset Direction\nA Offset Direction\nFlip Arrive/Leave\nPosition\nNote\n:\nDefaults\nFit\nOK\nAngled Breeches\nHVAC Window\nCancel\nAngled Breeches"}
{"Headers": "Side Branch Tee", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Side Branch Tee in the Available Type drop-down list to display the Circular Tee Piece window:\n\nThe Circular Tee Piece window default is a standard stock size, but can be changed by you using the following two methods:\nStandard Stock Sizes\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Main Sizes and Stock Branch Size drop-down lists, click the required dimensions for the HVAC component.\nIn the Brco Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Main Sizes drop-down list, select Special. The Stock Branch Sizes drop down list automatically changes to Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Tee Piece.\nSpecify a type of joint to use for the Arrive Joint, Leave Joint and Branch Joint. The default is Spec but can be changed by you. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Change Direction.\nIn the Change Direction specify the axes that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Radiused Threeway window was opened.\nClick Fit to orientate the Circular Tee Piece to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Circular Tee Piece component and close the Circular Tee Piece Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Circular Tee Piece window.\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018L\u2019\nBrco Diameter\nLength\nBrco Length\nCL From Leave\nAngles of Sides\nArrive Extension\nLeave Extension\nBranch Connection Extension\nInner Extension\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018L\u2019\nDuct Diameter \u2018L\u2019\nBrco Diameter\nBrco Diameter\nLength\nLength\nBrco Length\nBrco Length\nCL From Leave\nCL From Leave\nAngles of Sides\nAngles of Sides\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nBranch Connection Extension\nBranch Connection Extension\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nTee Piece\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nSide Branch Tee\nAvailable Type\nCircular Tee Piece\nHVAC Catalog\nBrco Direction\nStock Main Sizes\nSpecial\nStock Branch Sizes\nSpecial\nPicture\nTee Piece\nNote\n:\nHVAC Catalog\nArrive Joint\nCreate/Modify HVAC Component\nChange Direction\nChange Direction\nPosition\nConnect\nUnchanged\nNote\n:\nDefaults\nRadiused Threeway\nFit\nOK\nCircular Tee Piece\nHVAC Window\nCancel\nCircular Tee Piece"}
{"Headers": "Cap End", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Cap End in the Available Type drop-down list to display the Circular Cap End window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Cap End.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Circular Cap End window was opened.\nClick Fit to orientate the Circular Cap End to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Circular Cap End component and close the Circular Cap End Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Circular Cap End window\nDuct Diameter\nGraphical length\nDuct Diameter\nDuct Diameter\nGraphical length\nGraphical length\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCap End\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nCap End\nAvailable Type\nCircular\nCap End\nPicture\nCap End\nNote\n:\nHVAC Catalog\nArrive Joint\nCreate/Modify HVAC Component\nPosition\nNote\n:\nModify\nDefaults\nFit\nOK\nCap End\nHVAC Window\nCancel\nCap End"}
{"Headers": "Mesh End", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Mesh End in the Available Type drop-down list to display the Circular Mesh End window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Mesh End.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Circular Mesh End window was opened.\nClick Fit to orientate the Circular Mesh End to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Circular Mesh End component and close the Circular Mesh End Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Circular Mesh End window.\nDuct Diameter\nMesh X Spacings\nMesh Y Spacings\nMesh Wire Gauge\nGraphical length\nDuct Diameter\nDuct Diameter\nMesh X Spacings\nMesh X Spacings\nMesh Y Spacings\nMesh Y Spacings\nMesh Wire Gauge\nMesh Wire Gauge\nGraphical length\nGraphical length\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nMesh End\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nMesh End\nAvailable Type\nCircular Mesh End\nPicture\nMesh End\nNote\n:\nHVAC Catalog\nArrive Joint\nCreate/Modify HVAC Component\nPosition\nNote\n:\nModify\nDefaults\nCircular Mesh End\nFit\nOK\nCircular Mesh End\nHVAC Window\nCancel\nCircular Mesh End"}
{"Headers": "Material Connection", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Material Connection in the Available Type drop-down list to display the Material Connection window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Material Connection.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Material Connection window was opened.\nClick Fit to orientate the Material Connection to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Material Connection component and close the Material Connection Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Material Connection window.\nDuct Diameter\nOverall length\nMat\u2019l Thickness\nArrive Slipover\nLeave Slipover\nDuct Diameter\nDuct Diameter\nOverall length\nOverall length\nMat\u2019l Thickness\nMat\u2019l Thickness\nArrive Slipover\nArrive Slipover\nLeave Slipover\nLeave Slipover\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nMaterial Connection\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nMaterial Connection\nAvailable Type\nMaterial Connection\nPicture\nMaterial Connection\nNote\n:\nHVAC Catalog\nArrive Joint\nLeave Joint\nCreate/Modify HVAC Component\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nMaterial Connection\nFit\nOK\nMaterial Connection\nMaterial Connection\nHVAC Window\nCancel\nMaterial Connection"}
{"Headers": "Flexible Tube", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Flexible Tube in the Available Type drop-down list to display the Flexible Tube window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flexible Tube.\nIn the A Offset Direction enter the direction of the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Flexible Tube window was opened.\nClick Fit to orientate the Flexible Tube to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Flexible Tube component and close the Flexible Tube Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Flexible Tube window.\nDuct Diameter\nLength\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nDuct Diameter\nDuct Diameter\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nFlexible Tube\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nFlexible Tube\nAvailable Type\nFlexible Tube\nPicture\nFlexible Tube\nNote\n:\nHVAC Catalog\nA Offset Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFlexible Tube\nFit\nFlexible Tube\nOK\nFlexible Tube\nFlexible Tube\nHVAC Window\nCancel\nFlexible Tube"}
{"Headers": "Flexible Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Flexible Bend in the Available Type drop-down list to display the Flexible Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flexible Bend.\nIn the Leave Direction specify the axes that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Flexible Bend window was opened.\nClick Fit to orientate the Flexible Bend to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Flexible Bend component and close the Flexible Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Flexible Bend window.\nDuct Diameter\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nDuct Diameter\nDuct Diameter\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nFlexible Bend\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nFlexible Bend\nAvailable Type\nFlexible Bend\nPicture\nFlexible Bend\nNote\n:\nHVAC Catalog\nLeave Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nlexible Bend\nFit\nOK\nFlexible Bend\nHVAC Window\nCancel\nFlexible Bend"}
{"Headers": "Roof Cowl", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Roof Cowl in the Available Type drop-down list to display the Circular Cowl window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Weather Cowl.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Roof Cowl window was opened.\nClick Fit to orientate the Roof Cowl to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Roof Cowl component and close the Roof Cowl Window. You will be returned to the HVAC Window\nClick Cancel to discard all field changes and close the Roof Cowl window.\nDuct Diameter\nCowl Diameter\nCowl Height\nDuct to Cone\nDuct Diameter\nDuct Diameter\nCowl Diameter\nCowl Diameter\nCowl Height\nCowl Height\nDuct to Cone\nDuct to Cone\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Weather Cowl\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nRoof Cowl\nAvailable Type\nCircular Cowl\nPicture\nCircular Weather Cowl\nNote\n:\nHVAC Catalog\nArrive Joint\nCreate/Modify HVAC Component\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nRoof Cowl\nFit\nOK\nRoof Cowl\nHVAC Window\nCancel\nRoof Cowl"}
{"Headers": "Two Bend Setfill", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Two Bend Setfill in the Available Type drop-down list to display the Two Bend Setfill window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Two Bend Setfill.\nSpecify a type of joint to use for the 1st and 2nd Bend Arrive Joint and 1st and 2nd Bend Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nClick Defaults to reset all the fields back to when the Two Bend Setfill window was opened.\nClick OK to create the Two Bend Setfill component and close the Two Bend Setfill Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Two Bend Setfill window.\nDuct Diameter\nInside Radius\n1st Bend Arrive Extension\n1st Bend Leave Extension\n2nd Bend Arrive Extension\n2nd Bend Leave Extension\nDuct Diameter\nDuct Diameter\nInside Radius\nInside Radius\n1st Bend Arrive Extension\n1st Bend Arrive Extension\n1st Bend Leave Extension\n1st Bend Leave Extension\n2nd Bend Arrive Extension\n2nd Bend Arrive Extension\n2nd Bend Leave Extension\n2nd Bend Leave Extension\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension for the 1st and 2nd Bends default is auto but can be changed by you to a required dimension.\n\n\n\nHVAC Window\nTwo Bend Setfill\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nTwo Bend Setfill\nAvailable Type\nTwo Bend Setfill\nPicture\nTwo Bend Setfill\nNote\n:\nHVAC Catalog\nArrive Joint\nLeave Joint\nCreate/Modify HVAC Component\nDefaults\nTwo Bend Setfill\nOK\nTwo Bend Setfill\nHVAC Window\nCancel\nTwo Bend Setfill"}
{"Headers": "Two Bend Flexfill", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Two Bend Flexfill in the Available Type drop-down list to display the Two Bend Flex-fill window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Two Bend Flexfill.\nClick Defaults to reset all the fields back to when the Two Bend Flexfill window was opened.\nClick OK to create the Two Bend Flexfill component and close the Two Bend Flexfill Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Two Bend Flexfill window.\nDuct Diameter\nInside Radius\n1st Bend - Arrive Extension\n2nd Bend - Leave Extension\nDuct Diameter\nDuct Diameter\nInside Radius\nInside Radius\n1st Bend - Arrive Extension\n1st Bend - Arrive Extension\n2nd Bend - Leave Extension\n2nd Bend - Leave Extension\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\n\n\n\nHVAC Window\nTwo Bend Flexfill\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nTwo Bend Flexfill\nAvailable Type\nTwo Bend Flex-fill\nPicture\nTwo Bend Flexfill\nNote\n:\nHVAC Catalog\nDefaults\nTwo Bend Flexfill\nOK\nTwo Bend Flexfill\nHVAC Window\nCancel\nTwo Bend Flexfill"}
{"Headers": "Stiffening", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Stiffening in the Available Type drop-down list.\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Stiffener.\nThe application has automatically calculated the required number of stiffeners to support the CE (using the current detailing specification and other parameters). The number is displayed in the Spec Requirement box.\nThe number of sides of the CE is automatically input into the Number of Sides box, in this case as the CE is a rectangular straight the number of sides is input as 4.\nClick OK Spec Requirement to confirm the automatically generated number of stiffeners is compatible with the detailing specification.\nIf this is not required, click Q Spec Req, to change the automatically generated number of stiffeners.\nAfter selecting the Spec Requirement you must enter the A Offset Direction.\nIn the A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Stiffening window was opened.\nClick OK to create the Stiffening Flanges and close the Stiffening window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Stiffening window.\nStiffener Diameter\nDuct Diameter\nSpec Requirement\nFace from Leave\nA Offset\nB Offset\nAngle\nStiffener Face\nOther Web\nWeb Thickness\nStiffener Diameter\nStiffener Diameter\nDuct Diameter\nDuct Diameter\nSpec Requirement\nSpec Requirement\nFace from Leave\nFace from Leave\nA Offset\nA Offset\nB Offset\nB Offset\nAngle\nAngle\nStiffener Face\nStiffener Face\nOther Web\nOther Web\nWeb Thickness\nWeb Thickness\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ords 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ords 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ords 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nStiffening flanges are configured to suit each different component.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Stiffener\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nStiffening\nAvailable Type\nPicture\nCircular Stiffener\nNote\n:\nHVAC Catalog\nSpec Requirement\nNumber of Sides\nNote\n:\nOK Spec Requirement\nQ Spec Req\nA Offset Direction\nA Offset Direction\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nModify\nDefaults\nStiffening\nOK\nStiffening\nHVAC Window\nCancel\nStiffening"}
{"Headers": "Access Panel", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Access Panel in the Available Type drop-down list to display the Access Panel window:\n\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Access Panel.\nClick Transpose Width/Depth to exchange Access Panel Width dimension with Access Panel Height dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nIn Panel Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Clash Vol fields will be pre-populated with the obstruction volumes associated with the access panel and the ducting, but can be changed by you to the required joint.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Access Panel window was opened.\nClick Fit To Next to orientate the Access Panel to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Access Panel component and close the Access Panel Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Access Panel window.\nYou can select a standard stock access panel, using Select Size drop-down list, the Access Panel Width and Access Panel Height fields are populated with the standard sizes. If a standard stock size is not required, input the following dimensions:\nAccess Panel Width\nAccess Panel Height\nMAIN Width LA\nMAIN Depth LB\nFace over Duct\nDistance from Leave\nAdjustments Offset\nLateral Offset\nAngle of Slope\nFixing to Duct\nInner Extension\nPanel Direction\nYou can select a standard stock access panel, using Select Size drop-down list, the Access Panel Width and Access Panel Height fields are populated with the standard sizes. If a standard stock size is not required, input the following dimensions:\nYou can select a standard stock access panel, using Select Size drop-down list, the Access Panel Width and Access Panel Height fields are populated with the standard sizes. If a standard stock size is not required, input the following dimensions:\nAccess Panel Width\nAccess Panel Width\nAccess Panel Height\nAccess Panel Height\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nFace over Duct\nFace over Duct\nDistance from Leave\nDistance from Leave\nAdjustments Offset\nAdjustments Offset\nLateral Offset\nLateral Offset\nAngle of Slope\nAngle of Slope\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nPanel Direction\nPanel Direction\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nAccess Panel\nHVAC Catalog\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\n.\nCircular\nCategories\nAccess Panel\nAvailable Type\nAccess Panel\nSelect Size\nPicture\nAccess Panel\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nAccess Panel Width\nAccess Panel Height\nMAIN Width LA\nMAIN Depth LB\nPanel Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nDefaults\nFit To Next\nOK\nAccess Panel\nHVAC Window\nCancel\nAccess Panel"}
{"Headers": "Saddle", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Saddle in the Available Type drop-down list to display the Saddle window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Saddle.\nYou can also select a standard stock access panel, using Select Size drop-down list, the Saddle Overall Width and Saddle Overall Height fields are populated with the standard sizes.\nClick Transpose Width/Depth to exchange Saddle Overall Width dimension with Saddle Overall Height dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nIn Saddle Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).In the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Saddle window was opened.\nClick Fit To Next to orientate the Saddle to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Saddle component and close the Saddle Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Saddle window.\nSaddle Overall Width\nSaddle Overall Height\nMAIN Width LA\nMAIN Depth LB\nSaddle Depth\nDistance From Leave\nLateral Offset\nFixing to Duct\nInner Extension\nSaddle Direction\nSaddle Overall Width\nSaddle Overall Width\nSaddle Overall Height\nSaddle Overall Height\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nSaddle Depth\nSaddle Depth\nDistance From Leave\nDistance From Leave\nLateral Offset\nLateral Offset\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nSaddle Direction\nSaddle Direction\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nSaddle\nHVAC Catalog\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nSaddle\nAvailable Type\nSaddle\nPicture\nSaddle\nNote\n:\nHVAC Catalog\nHVAC Catalog\nSelect Size\nTranspose Width/Depth\nSaddle Overall Width\nSaddle Overall Height\nMAIN Width LA\nMAIN Depth LB\nSaddle Direction\nPosition\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nSaddle\nFit To Next\nOK\nSaddle\nHVAC Window\nCancel\nSaddle"}
{"Headers": "Test Point", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Test Point in the Available Type drop-down list to display the Test Holes window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Test Holes.\nIn Holes Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Clash Vol fields will be pre-populated with the obstruction volumes associated with the access panel and the ducting, but can be changed by you.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Test Holes window was opened.\nClick Fit To Next to orientate the Test Holes to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Test Holes component and close the Test Holes Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Test Holes window.\nNo Of Test Holes\nTest Hole Diameter\nTest Hole Height\nMAIN Diameter\nDistance From Leave\nLateral Offset\nInner Extension\nNo Of Test Holes\nNo Of Test Holes\nTest Hole Diameter\nTest Hole Diameter\nTest Hole Height\nTest Hole Height\nMAIN Diameter\nMAIN Diameter\nDistance From Leave\nDistance From Leave\nLateral Offset\nLateral Offset\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The No of Test Holes default is as defined in the HVAC Catalog but can be changed by you.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nTest Holes\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nTest Point\nAvailable Type\nTest Holes\nNote\n:\nHVAC Catalog\nHVAC Catalog\nPicture\nTest Holes\nHoles Direction\nPosition\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nDefaults\nTest Holes\nFit To Next\nOK\nTest Holes\nHVAC Window\nCancel\nTest Holes"}
{"Headers": "Internal Damper", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Internal Damper in the Available Type drop-down list to display the Internal Damper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Internal Damper.\nIn Handle Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Clash fields will be pre-populated with the obstruction volumes associated with the access panel and the ducting, but can be changed by you.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Internal Damper window was opened.\nClick Fit To Next to orientate the Internal Damper to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Internal Damper component and close the Internal Damper Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Internal Damper window.\nMAIN Diameter\nDistance From Leave\nMAIN Diameter\nMAIN Diameter\nDistance From Leave\nDistance From Leave\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nInternal Damper\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nInternal Damper\nAvailable Type\nInternal Damper\nNote\n:\nHVAC Catalog\nPicture\nInternal Damper\nHandle Direction\nClash\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nInternal Damper\nFit To Next\nOK\nInternal Damper\nHVAC Window\nCancel\nInternal Damper"}
{"Headers": "Gasket", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Circular in the Categories drop-down list and then Gasket in the Available Type drop-down list to display the Circular Gasket window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Gasket.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Circular Gasket window was opened.\nClick Fit to orientate the Circular Gasket to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Circular Gasket component and close the Circular Gasket Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Circular Gasket window.\nDuct Diameter\nThickness\nFlange Face\nDuct Diameter\nDuct Diameter\nThickness\nThickness\nFlange Face\nFlange Face\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the piece of HVAC at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the piece of HVAC at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the piece of HVAC at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the piece of HVAC but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nGasket\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nCircular\nCategories\nGasket\nAvailable Type\nCircular Gasket\nPicture\nGasket\nNote\n:\nHVAC Catalog\nPosition\nConnect\nUnchanged\nConnect\nCreate\nHVAC\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nCircular Gasket\nFit\nOK\nGasket\nHVAC Window\nCancel\nGasket"}
{"Headers": "Flat Oval", "Content": "The Flat Oval option of the Categories drop-down list is an umbrella for the flat oval components for selection in the catalog database.\n\n\n\nFlat Oval"}
{"Headers": "Flat Oval Straight", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then Straight in the Available Type drop-down list to display the Oval Straight window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Straight.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Width Direction.\nIn Width Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Oval Straight window was opened.\nClick Fit to orientate the Oval Straight component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Oval Straight component and close the Oval Straight Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Oval Straight window.\nDuct Width AA\nDuct Depth AB\nLength\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nStraight\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\nStraight\nAvailable Type\nOval\nStraight\nPicture\nStraight\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nCreate/Modify HVAC Component\nWidth Direction\nPosition\nConnect\nUnchanged\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nOval\nStraight\nFit\nOval\nStraight\nOK\nOval\nStraight\nOval\nStraight\nHVAC Window\nCancel\nOval\nStraight"}
{"Headers": "Male Coupling", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then Male Coupling in the Available Type drop-down list to display the Male Coupling window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Male Coupling.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Width Direction.\nIn Width Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Male Coupling window was opened.\nClick Fit to orientate the Male Coupling component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Male Coupling component and close the Male Coupling Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Male Coupling window.\nDuct Width AA\nDuct Depth AB\nLength\nMale Collar (A)\nMale Collar (L)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nMale Coupling\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\nMale Coupling\nAvailable Type\nMale Coupling\nPicture\nMale Coupling\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nWidth Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nMale Coupling\nFit\nOK\nMale Coupling\nHVAC Window\nCancel\nMale Coupling"}
{"Headers": "Taper", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then Taper in the Available Type drop-down list to display the FlatOval Taper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flat Oval Taper.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension or to exchanges Duct Width LA dimension with Duct Depth LB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the A Offset Direction.\nIn A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Flat Oval Taper window was opened.\nClick Fit to orientate the Flat Oval Taper component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Flat Oval Taper component and close the Flat Oval Taper Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Flat Oval Taper window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nDuct Depth LB\nLength\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nMale Collar (A)\nMale Collar (L)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nFlat Oval Taper\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\nTaper\nAvailable Type\nFlatOval Taper\nPicture\nFlat Oval Taper\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nA Offset Direction\nA Offset Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nFlat Oval Taper\nHVAC Window\nCancel"}
{"Headers": "\u2018A\u2019 Plane Offset", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then \u2018A\u2019 plane Offset in the Available Type drop-down list to display the Mitred A Offset window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for \u2018A\u2019 Plane Mitred Offset.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrjoint and Leajoint you must enter the Offset Direction.\nIn the Offset Direction enter the direction for the Offset relative to the Point of Origin. Valid directions are (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Mitred A Offset window was opened.\nClick Fit to orientate the Mitred A Offset to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Mitred A Offset component and close the Mitred A Offset Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Mitred A Offset window.\nDuct Width AA\nDuct Depth AB\nLength\nOffset\nArrive CL Throat\nLeave CL Throat\nMale Collar (A)\nMale Collar (L)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nOffset\nOffset\nArrive CL Throat\nArrive CL Throat\nLeave CL Throat\nLeave CL Throat\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018A\u2019 Plane Mitred Offset\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\n\u2018A\u2019 plane Offset\nAvailable Type\nMitred A Offset\nPicture\n\u2018A\u2019 Plane Mitred Offset\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nCreate/Modify HVAC Component\nOffset Direction\nOffset Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nDefaults\nMitred A Offset\nFit\nOK\nMitred A Offset\nHVAC Window\nCancel\nMitred A Offset"}
{"Headers": "\u2018B\u2019 Plane Offset", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then \u2018B\u2019 plane Offset in the Available Type drop-down list to display the Mitred B Offset window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for \u2018B\u2019 Plane Mitred Offset.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint). Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Offset Direction.\nIn the Offset Direction enter the direction for the Offset relative to the Point of Origin. Valid directions are (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Mitred B Offset window was opened.\nClick Fit to orientate the Mitred B Offset to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Mitred B Offset component and close the Mitred B Offset Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Mitred B Offset window.\nDuct Width AA\nDuct Depth AB\nLength\nOffset\nArrive CL Throat\nLeave CL Throat\nMale Collar (A)\nMale Collar (L)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nOffset\nOffset\nArrive CL Throat\nArrive CL Throat\nLeave CL Throat\nLeave CL Throat\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018B\u2019 Plane Mitred Offset\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\n\u2018B\u2019 plane Offset\nAvailable Type\nMitred B Offset\nPicture\n\u2018B\u2019 Plane Mitred Offset\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nCreate/Modify HVAC Component\nArrive Joint\nLeave Joint\nOffset Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nDefaults\nFit\nOK\nMitred B Offset\nHVAC Window\nCancel\nMitred B Offset"}
{"Headers": "\u2018A\u2019 Plane Mitred Elbow", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then \u2018A\u2019 Plane Mitred Elbow in the Available Type drop-down list to display the \u2018A\u2019 Plane Elbow window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for \u2018A\u2019 Plane Mitred Elbow.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the Axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the \u2018A\u2019 Plane Elbow window was opened.\nClick Fit to orientate the \u2018A\u2019 Plane Elbow component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the \u2018A\u2019 Plane Elbow component and close the \u2018A\u2019 Plane Elbow Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the \u2018A\u2019 Plane Elbow window.\nDuct Width AA\nDuct Depth AB\nAngle\nArrive Throat\nLeave Throat\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nAngle\nAngle\nArrive Throat\nArrive Throat\nLeave Throat\nLeave Throat\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018A\u2019 Plane Mitred Elbow\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\n\u2018A\u2019 Plane Mitred Elbow\nAvailable Type\n\u2018A\u2019 Plane Elbow\nPicture\n\u2018A\u2019 Plane Mitred Elbow\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nLeave Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\u2018A\u2019 Plane Elbow\nHVAC Window\nCancel"}
{"Headers": "\u2018B\u2019 Plane Mitred Elbow", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then \u2018B\u2019 Plane Mitred Elbow in the Available Type drop-down list to display the \u2018B\u2019 Plane Elbow window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for \u2018B\u2019 Plane Mitred Elbow.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the Axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the \u2018B\u2019 Plane Elbow window was opened.\nClick Fit to orientate the \u2018B\u2019 Plane Elbow component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the \u2018B\u2019 Plane Elbow component and close the \u2018B\u2019 Plane Elbow Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the \u2018B\u2019 Plane Elbow window.\nDuct Width AA\nDuct Depth AB\nAngle\nArrive Throat\nLeave Throat\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nAngle\nAngle\nArrive Throat\nArrive Throat\nLeave Throat\nLeave Throat\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018B\u2019 Plane Mitred Elbow\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\n\u2018B\u2019 Plane Mitred Elbow\nAvailable Type\n\u2018B\u2019 Plane Elbow\nPicture\n\u2018B\u2019 Plane Mitred Elbow\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\u2018B\u2019 Plane Elbow\nHVAC Window\nCancel"}
{"Headers": "\u2018A\u2019 Plane 3 Segment Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then \u2018A\u2019 Plane 3 Segment Bend in the Available Type drop-down list to display the 3 Segment A Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for \u2018A\u2019 Plane 3 Segment Bend.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the Axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the 3 Segment A Bend window was opened.\nClick Fit to orientate the 3 Segment A Bend component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the 3 Segment A Bend component and close the 3 Segment A Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the 3 Segment A Bend window.\nDuct Width AA\nDuct Depth AB\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018A\u2019 Plane 3 Segment Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\n\u2018A\u2019 Plane\n3 Segment Bend\nAvailable Type\n3 Segment A Bend\nPicture\n\u2018A\u2019 Plane 3 Segment Bend\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nLeave Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\n3 Segment A Bend\nFit\nOK\n3 Segment A Bend\nHVAC Window\nCancel"}
{"Headers": "\u2018B\u2019 Plane 3 Segment Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then \u2018B\u2019 Plane 3 Segment Bend in the Available Type drop-down list to display the 3 Segment B Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for \u2018B\u2019 Plane 3 Segment Bend.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the Axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the 3 Segment A Bend window was opened.\nClick Fit to orientate the 3 Segment B Bend component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the 3 Segment B Bend component and close the 3 Segment B Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the 3 Segment B Bend window.\nDuct Width AA\nDuct Depth AB\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018B\u2019 Plane 3 Segment Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\n\u2018B\u2019 Plane 3 Segment Bend\nAvailable Type\n3 Segment B Bend\nPicture\n\u2018B\u2019 Plane 3 Segment Bend\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n3 Segment B Bend\nHVAC Window"}
{"Headers": "\u2018A\u2019 Plane 4 Segment Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then \u2018A\u2019 Plane 4 Segment Bend in the Available Type drop-down list to display the 4 Segment A Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for \u2018A\u2019 Plane 4 Segment Bend.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the Axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the 4 Segment A Bend window was opened.\nClick Fit to orientate the 4 Segment A Bend component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the 4 Segment A Bend component and close the 4 Segment A Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the 4 Segment A Bend window.\nDuct Width AA\nDuct Depth AB\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018A\u2019 Plane 4 Segment Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\n\u2018A\u2019 Plane 4 Segment Bend\nAvailable Type\n4 Segment A Bend\nPicture\n\u2018A\u2019 Plane 4 Segment Bend\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n4 Segment A Bend\nHVAC Window"}
{"Headers": "\u2018B\u2019 Plane 4 Segment Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then \u2018B\u2019 Plane 4 Segment Bend in the Available Type drop-down list to display the 4 Segment B Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for \u2018B\u2019 Plane 4 Segment Bend.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the Axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the 4 Segment B Bend window was opened.\nClick Fit to orientate the 4 Segment B Bend component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the 4 Segment B Bend component and close the 4 Segment B Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the 4 Segment B Bend window.\nDuct Width AA\nDuct Depth AB\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018B\u2019 Plane 4 Segment Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\n\u2018B\u2019 Plane 4 Segment Bend\nAvailable Type\n4 Segment B Bend\nPicture\n\u2018B\u2019 Plane 4 Segment Bend\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n4 Segment B Bend\nHVAC Window"}
{"Headers": "\u2018A\u2019 Plane 5 Segment Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then \u2018A\u2019 Plane 5 Segment Bend in the Available Type drop-down list to display the 5 Segment A Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for \u2018A\u2019 Plane 5 Segment Bend.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the Axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the 5 Segment A Bend window was opened.\nClick Fit to orientate the 5 Segment A Bend component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the 5 Segment A Bend component and close the 5 Segment A Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the 5 Segment A Bend window.\nDuct Width AA\nDuct Depth AB\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018A\u2019 Plane 5 Segment Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\n\u2018A\u2019 Plane 5 Segment Bend\nAvailable Type\n5 Segment A Bend\nPicture\n\u2018A\u2019 Plane 5 Segment Bend\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\n5 Segment A Bend\nFit\nOK\n5 Segment A Bend\nHVAC Window"}
{"Headers": "\u2018B\u2019 Plane 5 Segment Bend", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then \u2018B\u2019 Plane 5 Segment Bend in the Available Type drop-down list to display the 5 Segment B Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for \u2018B\u2019 Plane 5 Segment Bend.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn Leave Direction specify the Axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the 5 Segment B Bend window was opened.\nClick Fit to orientate the 5 Segment B Bend component to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the 5 Segment B Bend component and close the 5 Segment B Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the 5 Segment B Bend window.\nDuct Width AA\nDuct Depth AB\nAngle\nInside Radius\nArrive Extension\nLeave Extension\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nAngle\nAngle\nInside Radius\nInside Radius\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions These dimensions are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\n\u2018B\u2019 Plane 5 Segment Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\n\u2018B\u2019 Plane 5 Segment Bend\nAvailable Type\n5 Segment B Bend\nPicture\n\u2018B\u2019 Plane 5 Segment Bend\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n5 Segment B Bend\nHVAC Window"}
{"Headers": "Cap End", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then Cap End in the Available Type drop-down list to display the FlatOval Cap End window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Cap End.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint. Refer to HVAC Components for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint you must enter the Width Direction.\nIn the Width Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the FlatOval Cap End window was opened.\nClick OK to create the FlatOval Cap End component and close the FlatOval Cap End Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the FlatOval Cap End window.\nDuct Width AA\nDuct Depth AB\nGraphical length\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nGraphical length\nGraphical length\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCap End\nHVAC Catalog\nHVAC Components\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\nCap End\nAvailable Type\nFlatOval\nCap End\nPicture\nCap End\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nArrive Joint\nHVAC Components\nWidth Direction\nWidth Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFlatOval\nOK\nFlatOval\nFlatOval Cap End\nHVAC Window\nCancel\nFlatOval Cap End"}
{"Headers": "Stiffening", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then Stiffening in the Available Type drop-down list to display the Stiffening window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Stiffening.\nThe application has automatically calculated the required number of stiffeners to support the CE (using the current detailing specification and other parameters). The number is displayed in the Spec Requirement box.\nThe number of sides of the CE is automatically input into the Number of Sides box, in this case as the CE is a rectangular straight the number of sides is input as 4.\nClick OK Spec Requirement to confirm the automatically generated number of stiffeners is compatible with the detailing specification.\nIf this is not required, click Q Spec Req, to change the automatically generated number of stiffeners.\nAfter selecting the Spec Requirement you must enter the Aoff Direction.\nIn the A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Stiffening window was opened.\nClick OK to create the Stiffening Flanges and close the Stiffening window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Stiffening window.\nStiffener Width\nStiffener Depth\nDuct Width LA\nDuct Depth LB\nSpec Requirement\nNumber of Sides\nFace from Leave\nA Offset\nB Offset\nAngle\nStiffener Face\nOther Web\nWeb Thickness\nStiffener Width\nStiffener Width\nStiffener Depth\nStiffener Depth\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nSpec Requirement\nSpec Requirement\nNumber of Sides\nNumber of Sides\nFace from Leave\nFace from Leave\nA Offset\nA Offset\nB Offset\nB Offset\nAngle\nAngle\nStiffener Face\nStiffener Face\nOther Web\nOther Web\nWeb Thickness\nWeb Thickness\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nStiffening flanges are configured to suit each different component.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nStiffening\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\nStiffening\nAvailable Type\nStiffening\nPicture\nStiffening\nNote\n:\nHVAC Catalog\nSpec Requirement\nNumber of Sides\nNote\n:\nOK Spec Requirement\nQ Spec Req\nA Offset Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nOK\nHVAC Window\nCancel"}
{"Headers": "Access Panel", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then Access Panel in the Available Type drop-down list to display the Access Panel window:\n\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Access Panel.\nClick Transpose Width/Depth to exchange Access Panel Width dimension with Access Panel Height dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nIn Panel Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Clash Vol fields will be pre-populated with the obstruction volumes associated with the access panel and the ducting, but can be changed by you to the required joint.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Access Panel window was opened.\nClick Fit To Next to orientate the Access Panel to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Access Panel component and close the Access Panel Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Access Panel window.\nYou can select a standard stock access panel, using Select Size drop-down list, the Access Panel Width and Access Panel Height fields are populated with the standard sizes. If a standard stock size is not required, input the following dimensions:\nAccess Panel Weight\nAccess Panel Height\nMAIN Width LA\nMAIN Depth LB\nFace over Duct\nDistance from Leave\nAdjustments Offset\nLateral Offset\nAngle of Slope\nFixing to Duct\nInner Extension\nPanel Direction\nYou can select a standard stock access panel, using Select Size drop-down list, the Access Panel Width and Access Panel Height fields are populated with the standard sizes. If a standard stock size is not required, input the following dimensions:\nYou can select a standard stock access panel, using Select Size drop-down list, the Access Panel Width and Access Panel Height fields are populated with the standard sizes. If a standard stock size is not required, input the following dimensions:\nAccess Panel Weight\nAccess Panel Weight\nAccess Panel Height\nAccess Panel Height\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nFace over Duct\nFace over Duct\nDistance from Leave\nDistance from Leave\nAdjustments Offset\nAdjustments Offset\nLateral Offset\nLateral Offset\nAngle of Slope\nAngle of Slope\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nPanel Direction\nPanel Direction\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nAccess Panel\nHVAC Catalog\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\nAccess Panel\nAvailable Type\nAccess Panel\nSelect Size\nPicture\nAccess Panel\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nAccess Panel Width\nAccess Panel Height\nMAIN Width LA\nMAIN Depth LB\nPanel Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nAccess Panel\nFit To Next\nOK\nAccess Panel\nHVAC Window\nCancel\nAccess Panel"}
{"Headers": "Saddle", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then Saddle in the Available Type drop-down list to display the Saddle window.\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC click Picture to display a detailed drawing for Saddle.\nYou can also select a standard stock access panel, using Select Size drop-down list, the Saddle Overall Width and Saddle Overall Height fields are populated with the standard sizes.\nClick Transpose Width/Depth to exchange Saddle Overall Width dimension with Saddle Overall Height dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nIn Saddle Direction specify the axis to be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Saddle window was opened.\nClick Fit To Next to orientate the Saddle to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Saddle component and close the Saddle Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Saddle window.\nSaddle Overall Width\nSaddle Overall Height\nMAIN Width LA\nMAIN Depth LB\nSaddle Depth\nDistance from Leave\nLateral Offset\nFixing to Duct\nInner Extension\nSaddle Direction\nSaddle Overall Width\nSaddle Overall Width\nSaddle Overall Height\nSaddle Overall Height\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nSaddle Depth\nSaddle Depth\nDistance from Leave\nDistance from Leave\nLateral Offset\nLateral Offset\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nSaddle Direction\nSaddle Direction\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nSaddle\nHVAC Catalog\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nFlat Oval\nCategories\nSaddle\nAvailable Type\nSaddle\nPicture\nSaddle\nNote\n:\nHVAC Catalog\nHVAC Catalog\nSelect Size\nTranspose Width/Depth\nSaddle Overall Width\nSaddle Overall Height\nMAIN Width LA\nMAIN Depth LB\nSaddle Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nSaddle\nFit To Next\nOK\nSaddle\nHVAC Window\nCancel\nSaddle"}
{"Headers": "Gasket", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Flat Oval in the Categories drop-down list and then Gasket in the Available Type drop-down list to display the FlatOval Gasket window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Gasket.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nIn Width Direction enter the specify the Axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Gasket window was opened.\nClick Fit to orientate the Gasket to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Gasket component and close the Gasket Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Gasket window.\nDuct Width AA\nDuct Depth AB\nThickness\nFlange Face\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nThickness\nThickness\nFlange Face\nFlange Face\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nGasket\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC\nFlat Oval\nCategories\nGasket\nAvailable Type\nFlatOval Gasket\nPicture\nGasket\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nWidth Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nGasket\nFit\nOK\nGasket\nHVAC Window\nCancel\nGasket"}
{"Headers": "Transformations", "Content": "The Transformations option of the Categories drop-down list is an umbrella for the Transformations components for selection in the catalog database.\n\n\n\nTransformations\nCategories"}
{"Headers": "Square to Round", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Transformations in the Categories drop-down list and then Square to Round in the Available Type drop-down list to display the Square to Round window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Square to Round.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Rectangle Joint and Circle Joint. Refer to Create a Component for a detailed description.\nAfter selecting the type of joint to use for the Rectangle Joint and Circle Joint you must enter the A Offset Direction.\nIn A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).Using the Flip Arrive/Leave drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Square to Round window was opened.\nClick Fit to orientate the Square to Round to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Square to Round component and close the Square to Round Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Square to Round window.\nDuct Width AA\nDuct Depth AB\nDuct Diameter\nLength\nA Offset\nB Offset\nRectangle Extension\nCircle Extension\nMale Collar\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Diameter\nDuct Diameter\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nRectangle Extension\nRectangle Extension\nCircle Extension\nCircle Extension\nMale Collar\nMale Collar\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Rectangle and Circle Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nSquare to Round\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nTransformations\nCategories\nSquare to Round\nAvailable Type\nSquare to Round\nPicture\nSquare to Round\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nA Offset Direction\nFlip Arrive/Leave\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nSquare to Round\nHVAC Window\nCancel\nSquare to Round"}
{"Headers": "Square to Flat Oval", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Transformations in the Categories drop-down list and then Square to Flat Oval in the Available Type drop-down list to display the Square to Flat Oval window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Square to Flatoval.\nClick Transpose Width/Depth to exchange Rectangle Width AA dimension with Rectangle Depth AB dimension or exchange Oval Width LA dimension with Oval Depth LB dimension.\nSpecify a type of joint to use for the Rectangle Joint and Oval Joint. Refer to Create a Component for a detailed description.\nAfter selecting the type of joint to use for the Rectangle Joint and Oval Joint you must enter the A Offset Direction.\nIn A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).Using the Flip Oval/Rect drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC, 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Square to Flat Oval window was opened.\nClick Fit to orientate the Square to Flat Oval to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Square to Flat Oval component and close the Square to Flat Oval Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Square to Flat Oval window.\nRectangle Width AA\nRectangle Depth AB\nOval Width LA\nOval Depth LB\nLength\nA Offset\nB Offset\nRectangle Extension\nOval Extension\nMale Collar\nRectangle Width AA\nRectangle Width AA\nRectangle Depth AB\nRectangle Depth AB\nOval Width LA\nOval Width LA\nOval Depth LB\nOval Depth LB\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nRectangle Extension\nRectangle Extension\nOval Extension\nOval Extension\nMale Collar\nMale Collar\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog. The Rectangle and Oval Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nSquare to Flatoval\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nTransformations\nCategories\nSquare to Flat Oval\nAvailable Type\nSquare to Flat Oval\nPicture\nSquare to Flatoval\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nRectangle Width AA\nRectangle Depth AB\nA Offset Direction\nFlip Oval/Rect\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nSquare to Flat Oval\nHVAC Window\nCancel\nSquare to Flat Oval"}
{"Headers": "FlatOval to Round", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Transformations in the Categories drop-down list and then Flat Oval to Round in the Available Type drop-down list to display the Flat Oval to Round window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flatoval to Round.\nClick Transpose Width/Depth to exchange Oval Width LA dimension with Oval Depth LB dimension.\nSpecify a type of joint to use for the Circle Joint and Oval Joint. Refer to Create a Component for a detailed description.\nAfter selecting the type of joint to use for the Circle Joint and Oval Joint you must enter the A Offset Direction.\nIn A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).Using the Flip Circle/Oval drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC, 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Round to Flat Oval window was opened.\nClick Fit to orientate the Round to Flat Oval to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Round to Flat Oval component and close the Round to Flat Oval Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Round to Flat Oval window.\nDuct Diameter\nOval Width LA\nOval Depth LB\nLength\nA Offset\nB Offset\nCircle Extension\nOval Extension\nCircle Male Collar\nOval Male Collar\nDuct Diameter\nDuct Diameter\nOval Width LA\nOval Width LA\nOval Depth LB\nOval Depth LB\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nCircle Extension\nCircle Extension\nOval Extension\nOval Extension\nCircle Male Collar\nCircle Male Collar\nOval Male Collar\nOval Male Collar\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog. The Circle and Oval Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nFlatoval to Round\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nTransformations\nCategories\nFlat Oval to Round\nAvailable Type\nFlat Oval to Round\nPicture\nFlatoval to Round\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nA Offset Direction\nFlip Circle/Oval\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nRound to Flat Oval\nHVAC Window\nCancel\nRound to Flat Oval"}
{"Headers": "Oval \u2018A\u2019 to Oval \u2018B\u2019", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Transformations in the Categories drop-down list and then Oval \u2018A\u2019 to Oval \u2018B\u2019 in the Available Type drop-down list to display the Oval A to Oval B window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Oval A to Oval B.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension or exchange Duct Width LA dimension with Duct Depth LB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the A Offset Direction.\nIn A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).Using the Flip Arrive/Leave drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC, 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Oval A to Oval B window was opened.\nClick Fit to orientate the Oval A to Oval B to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Oval A to Oval B component and close the Oval A to Oval B Window. You will be returned to the HVAC Window\nClick Cancel to discard all field changes and close the Oval A to Oval B window.\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nDuct Depth LB\nLength\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nMale Collar A\nMale Collar L\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nLength\nLength\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nMale Collar A\nMale Collar A\nMale Collar L\nMale Collar L\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog. The Arrive and Leave Extension default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nOval A to Oval B\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nTransformations\nCategories\nOval \u2018A\u2019 to Oval \u2018B\u2019\nAvailable Type\nOval A to Oval B\nPicture\nOval A to Oval B\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Depth AB\nCreate/Modify HVAC Component\nA Offset Direction\nFlip Arrive/Leave\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nOval A to Oval B\nFit\nOK\nOval A to Oval B\nHVAC Window\nCancel\nOval A to Oval B"}
{"Headers": "Spigot Box", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Transformations in the Categories drop-down list and then Spigot Box in the Available Type drop-down list to display the Spigot Box window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular to Rectangular Spigot Box.\nClick Transpose Width/Depth to exchange Duct Width LA dimension with Duct Depth LB dimension.\nSpecify a type of joint to use for the Circ Jnt (Circular Joint) and Rect Jnt (Rectangular Joint). Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Circle Joint and Rectangle Joint you must enter the A Offset Direction.\nIn A Offset Direction enter the direction for the A Offset relative to the Point of Origin. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).Using the Flip Rectangle / Circle drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC, 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Spigot Box window was opened.\nClick Fit to orientate the Spigot Box to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Spigot Box component and close the Spigot Box Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Spigot Box window.\nDuct Diameter\nDuct Width LA\nDuct Depth LB\nRectangle Box Height\nA Offset\nB Offset\nCircle Extension\nMale Collar\nDuct Diameter\nDuct Diameter\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nRectangle Box Height\nRectangle Box Height\nA Offset\nA Offset\nB Offset\nB Offset\nCircle Extension\nCircle Extension\nMale Collar\nMale Collar\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular to Rectangular Spigot Box\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nTransformations\nCategories\nSpigot Box\nAvailable Type\nSpigot Box\nPicture\nCircular to Rectangular Spigot Box\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nA Offset Direction\nFlip Rectangle / Circle\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nSpigot Box\nFit\nOK\nSpigot Box\nHVAC Window\n.\nCancel\nSpigot Box"}
{"Headers": "Linear Plenum", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Transformations in the Categories drop-down list and then Linear Plenum in the Available Type drop-down list to display the Linear Plenum window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular to Linear Plenum.\nClick Transpose Width/Depth to exchange Duct Width LA dimension with Duct Depth LB dimension.\nSpecify a type of joint to use for the Circle Joint and Rectangle Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Circle Joint and Rectangle Joint you must enter the Leave Direction.\nIn Leave Direction specify the Axis that should be used. Valid Axis are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).Using the Flip Rectangle / Circle drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC, 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Linear Plenum window was opened.\nClick Fit to orientate the Linear Plenum to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Linear Plenum component and close the Linear Plenum Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Linear Plenum window.\nDuct Diameter\nDuct Width LA\nDuct Depth LB\nRectangle Box Height\nHeight CL Circle\nA Offset\nCircle Extension\nMale Collar\nDuct Diameter\nDuct Diameter\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nRectangle Box Height\nRectangle Box Height\nHeight CL Circle\nHeight CL Circle\nA Offset\nA Offset\nCircle Extension\nCircle Extension\nMale Collar\nMale Collar\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular to Linear Plenum\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nTransformations\nCategories\nLinear Plenum\nAvailable Type\nLinear Plenum\nPicture\nCircular to Linear Plenum\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nLeave Direction\nFlip Rectangle / Circle\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nLinear Plenum\nFit\nLinear Plenum\nOK\nLinear Plenum\nLinear Plenum\nHVAC Window\nCancel\nLinear Plenum"}
{"Headers": "Circ>Rect Spigot Plate", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Transformations in the Categories drop-down list and then Circ>Rect Spigot Plate in the Available Type drop-down list to display the Spigot Plate window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular to Rectangular Spigot Box.\nClick Transpose Width/Depth to exchange Duct Width LA dimension with Duct Depth LB dimension.\nSpecify a type of joint to use for the Circle Joint and Rectangle Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Circle Joint and Rectangle Joint you must enter the A Offset Direction.\nIn A Offset Direction enter the direction for the A Offset. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).Using the Flip Rectangle / Circle drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC, 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Spigot Plate window was opened.\nClick Fit to orientate the Spigot Plate to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Spigot Plate component and close the Spigot Plate Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Spigot Plate window.\nDuct Diameter\nDuct Width LA\nDuct Depth LB\nA Offset\nB Offset\nTop Flange\nRight Flange\nLeft Flange\nBottom Flange\nCircle Extension\nMale Collar\nDuct Diameter\nDuct Diameter\nDuct Width LA\nDuct Width LA\nDuct Depth LB\nDuct Depth LB\nA Offset\nA Offset\nB Offset\nB Offset\nTop Flange\nTop Flange\nRight Flange\nRight Flange\nLeft Flange\nLeft Flange\nBottom Flange\nBottom Flange\nCircle Extension\nCircle Extension\nMale Collar\nMale Collar\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular to Rectangular Spigot Box\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nTransformations\nCategories\nCirc>Rect Spigot Plate\nAvailable Type\nSpigot Plate\nPicture\nCircular to Rectangular Spigot Box\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nA Offset Direction\nFlip Rectangle / Circle\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nSpigot Plate\nFit\nSpigot Plate\nOK\nSpigot Plate\nSpigot Plate\nHVAC Window\n.\nCancel\nSpigot Plate"}
{"Headers": "Oval>Rect Spigot Plate", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Transformations in the Categories drop-down list and then Oval>Rect Spigot Box in the Available Type drop-down list to display the Spigot Plate window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flat Oval to Rectangular Spigot Box.\nClick Transpose Width/Depth to exchange Oval Width AA dimension with Oval Depth AB dimension or to exchange Rectangle Duct Width dimension with Rectangle Duct Depth dimension.\nSpecify a type of joint to use for the Oval Joint and Rectangle Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Oval Joint and Rectangle Joint you must enter the A Offset Direction.\nIn A Offset Direction enter the direction for the A Offset. Valid directions are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).Using the Flip Rectangle / Oval drop-down list, you can choose whether to flip the direction of arrive and leave of the of the piece of HVAC, 180\u00b0 relative to the point of origin.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Spigot Plate window was opened.\nClick Fit to orientate the Spigot Plate to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Spigot Plate component and close the Spigot Plate Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Spigot Plate window.\nOval Width AA\nOval Depth AB\nRectangle Duct Width\nRectangle Duct Depth\nA Offset\nB Offset\nTop Flange\nRight Flange\nLeft Flange\nBottom Flange\nOval Extension\nMale Collar\nOval Width AA\nOval Width AA\nOval Depth AB\nOval Depth AB\nRectangle Duct Width\nRectangle Duct Width\nRectangle Duct Depth\nRectangle Duct Depth\nA Offset\nA Offset\nB Offset\nB Offset\nTop Flange\nTop Flange\nRight Flange\nRight Flange\nLeft Flange\nLeft Flange\nBottom Flange\nBottom Flange\nOval Extension\nOval Extension\nMale Collar\nMale Collar\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimension. These dimension are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nFlat Oval to Rectangular Spigot Box\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nTransformations\nCategories\nOval>Rect Spigot Box\nAvailable Type\nSpigot Plate\nPicture\nFlat Oval to Rectangular Spigot Box\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nA Offset Direction\nFlip Rectangle / Oval\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nSpigot Plate\nFit\nSpigot Plate\nOK\nSpigot Plate\nSpigot Plate\nHVAC Window\nCancel\nSpigot Plate"}
{"Headers": "Branch Connectors", "Content": "The Branch Connectors option of the Categories drop-down list is an umbrella for the branch connector components for selection in the catalog database.\nNote:\nAll rectangular branch connectors can be fitted to rectangular, circular or flat oval ducting.\n\n\n\nBranch Connectors\nCategories\nNote\n:"}
{"Headers": "Rectangular Boot r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then RECTANGULAR, Boot r in the Available Type drop-down list to display the Boot Brconnector window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Boot.\nClick Transpose Width/Depth to exchange Boot Width dimension with Boot Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Boot Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Boot Joint, you must enter the Boot Direction.\nIn Boot Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Boot Brconnector window was opened.\nClick Fit To Next to orientate the Boot Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Boot Branch Connector component and close the Boot Brconnector Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Boot Brconnector window.\nBoot Width\nBoot Depth\nMAIN Width LA\nMAIN Depth LB\nBoot Length\nDistance from Leave\nB offset\nBoot Extension\nFixing to Duct\nInner Extension\nBoot Width\nBoot Width\nBoot Depth\nBoot Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBoot Length\nBoot Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nBoot Extension\nBoot Extension\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Boot Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Boot\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nCategories\nRECTANGULAR, Boot r\nAvailable Type\nBoot Brconnector\nRectangular Boot\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBoot Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nBoot Brconnector\nFit To Next\nBoot Branch Connector\nOK\nBoot Branch Connector\nBoot Brconnector\nHVAC Window\nCancel\nBoot Brconnector"}
{"Headers": "Rectangular Square r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then RECTANGULAR, Square r in the Available Type drop-down list to display the Square Brconnector window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Square.\nClick Transpose Width/Depth to exchange Branch Connector Width dimension with Branch Connector Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Brco Brconnector window was opened.\nClick Fit To Next to orientate the Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Square Branch Connector component and close the Square Brconnector window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Square Brconnector window.\nBranch Connector Width\nBranch Connector Depth\nMAIN Width LA\nMAIN Depth LB\nBranch Connector Length\nDistance from Leave\nB offset\nBranch Connector Extension\nFixing to Duct\nInner Extension\nBranch Connector Width\nBranch Connector Width\nBranch Connector Depth\nBranch Connector Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBranch Connector Length\nBranch Connector Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nBranch Connector Extension\nBranch Connector Extension\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Square\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nRECTANGULAR, Square r\nAvailable Type\nSquare Brconnector\nPicture\nRectangular Square\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nBrco Brconnector\nFit To Next\nBranch Connector\nOK\nSquare Branch Connector\nSquare Brconnector\nHVAC Window\nCancel\nSquare Brconnector"}
{"Headers": "Rectangular Fish r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then RECTANGULAR, Fish r in the Available Type drop-down list to display the Fish Brconnector window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Fish.\nClick Transpose Width/Depth to exchange Fish Width dimension with Fish Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Fish Joint. Refer to HVAC Components for a detailed description.\nAfter selecting the type of joint to use for the Fish Joint, you must enter the Fish Direction.\nIn Fish Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Fish Brconnector window was opened.\nClick Fit To Next to orientate the Fish Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Fish Branch Connector component and close the Fish Brconnector Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Fish Brconnector window.\nFish Width\nFish Depth\nMAIN Width LA\nMAIN Depth LB\nFish Length\nDistance from Leave\nB Offset\nFish Extension\nFixing to Duct\nInner Extension\nFish Width\nFish Width\nFish Depth\nFish Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nFish Length\nFish Length\nDistance from Leave\nDistance from Leave\nB Offset\nB Offset\nFish Extension\nFish Extension\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fish Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Fish\nHVAC Catalog\nHVAC Catalog\nHVAC Components\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nRECTANGULAR, Fish r\nAvailable Type\nFish Brconnector\nPicture\nRectangular Fish\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nHVAC Components\nFish Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFish Brconnector\nFit To Next\nFish Branch Connector\nOK\nFish Branch Connector\nFish Brconnector\nHVAC Window\nCancel\nFish Brconnector"}
{"Headers": "Rectangular Angled r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then RECTANGULAR, Angled r in the Available Type drop-down list to display the Angled Brconnector window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Angled.\nClick Transpose Width/Depth to exchange Branch Connector Width dimension with Branch Connector Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to HVAC Components for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Angled Brconnector window was opened.\nClick Fit To Next to orientate the Angled Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Angled Branch Connector component and close the Angled Brconnector Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Angled Brconnector window.\nBranch Connector Width\nBranch Connector Depth\nMAIN Width LA\nMAIN Depth LB\nAngle to Main\nBranch Connector Length\nDistance From Leave\nB Offset\nBranch Connector Extension\nFixing to Duct\nInner Extension\nBranch Connector Width\nBranch Connector Width\nBranch Connector Depth\nBranch Connector Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nAngle to Main\nAngle to Main\nBranch Connector Length\nBranch Connector Length\nDistance From Leave\nDistance From Leave\nB Offset\nB Offset\nBranch Connector Extension\nBranch Connector Extension\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Angled\nHVAC Catalog\nHVAC Catalog\nHVAC Components\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nRECTANGULAR, Angled r\nAvailable Type\nAngled Brconnector\nPicture\nRectangular Angled\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nHVAC Components\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nAngled Brconnector\nFit To Next\nAngled Branch Connector\nOK\nAngled Branch Connector\nAngled Brconnector\nHVAC Window\nCancel\nAngled Brconnector"}
{"Headers": "Rectangular Tapered r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then RECTANGULAR, Tapered r in the Available Type drop-down list to display the Tapering Branch window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Tapered.\nClick Transpose Width/Depth to exchange Branch Connector Width dimension with Branch Connector Depth dimension, to exchange First Width dimension with First Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to HVAC Components for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Tapering Branch window was opened.\nClick Fit To Next to orientate the Tapering Branch to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Tapering Branch component and close the Tapering Branch Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Tapering Branch window.\nBranch Connector Width\nBranch Connector Depth\nFirst Width\nFirst Depth\nMAIN Width LA\nMAIN Depth LB\nBranch Connector Length\nDistance From Leave\nPosition B Offset\nFirst Extension\nEnd Extension\nTaper A Offset\nTaper B Offset\nFixing to Duct\nBranch Connector Width\nBranch Connector Width\nBranch Connector Depth\nBranch Connector Depth\nFirst Width\nFirst Width\nFirst Depth\nFirst Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBranch Connector Length\nBranch Connector Length\nDistance From Leave\nDistance From Leave\nPosition B Offset\nPosition B Offset\nFirst Extension\nFirst Extension\nEnd Extension\nEnd Extension\nTaper A Offset\nTaper A Offset\nTaper B Offset\nTaper B Offset\nFixing to Duct\nFixing to Duct\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The End Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Tapered\nHVAC Catalog\nHVAC Catalog\nHVAC Components\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nRECTANGULAR, Tapered r\nAvailable Type\nTapering Branch\nPicture\nRectangular Tapered\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nHVAC Components\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nTapering Branch\nFit To Next\nTapering Branch\nOK\nTapering Branch\nTapering Branch\nHVAC Window\nCancel\nTapering Branch"}
{"Headers": "Circular Boot c", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connector in the Categories drop-down list and then CIRCULAR, Boot c in the Available Type drop-down list to display the Boot Brconnector window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Boot.\nClick Transpose Width/Depth to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Boot Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Boot Joint, you must enter the Boot Direction.\nIn Boot Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Boot Brconnector window was opened.\nClick Fit To Next to orientate the Boot Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Boot Branch Connector component and close the Boot Brconnector Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Boot Brconnector window.\nBoot Diameter\nMAIN Width LA\nMAIN Depth LB\nBoot Length\nDistance from Leave\nB offset\nBoot Extension\nFixing to Duct\nMale Collar\nInner Extension\nBoot Diameter\nBoot Diameter\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBoot Length\nBoot Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nBoot Extension\nBoot Extension\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The End Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Boot\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connector\nCategories\nCIRCULAR, Boot c\nAvailable Type\nBoot Brconnector\nPicture\nCircular Boot\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBoot Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nBoot Brconnector\nFit To Next\nBoot Branch Connector\nOK\nBoot Branch Connector\nBoot Brconnector\nHVAC Window\nCancel\nBoot Brconnector"}
{"Headers": "Circular Square c", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then CIRCULAR, Square c in the Available Type drop-down list to display the Square Brcoconnector window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Square.\nClick Transpose Width/Depth to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint (Fish Joint). Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Square Brcoconnector window was opened.\nClick Fit To Next to orientate the Square Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Square Branch Connector component and close the Square Brcoconnector Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Square Brcoconnector window.\nBranch Connector Diameter\nMAIN Width LA\nMAIN Depth LB\nBranch Connector Length\nDistance from Leave\nB offset\nBranch Connector Extension\nFixing to Duct\nInner Extension\nBranch Connector Diameter\nBranch Connector Diameter\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBranch Connector Length\nBranch Connector Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nBranch Connector Extension\nBranch Connector Extension\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Square\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nCIRCULAR, Square c\nAvailable Type\nSquare Brcoconnector\nPicture\nCircular Square\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nDirection\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nSquare Brcoconnector\nFit To Next\nSquare Branch Connector\nOK\nSquare Branch Connector\nSquare Brcoconnector\nHVAC Window\nCancel\nSquare Brcoconnector"}
{"Headers": "Circular Fish c", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then CIRCULAR, Fish c in the Available Type drop-down list to display the Fish Brconnector window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Fish.\nClick Transpose Width/Depth to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Fish Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Fish Joint, you must enter the Fish Direction.\nIn Fish Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Fish Brconnector window was opened.\nClick Fit To Next to orientate the Fish Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Fish Branch Connector component and close the Fish Brconnector Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Fish Brconnector window.\nFish Diameter\nMAIN Width LA\nMAIN Depth LB\nFish Length\nDistance from Leave\nB offset\nFish Extension\nFixing to Duct\nMale Collar\nInner Extension\nFish Diameter\nFish Diameter\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nFish Length\nFish Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nFish Extension\nFish Extension\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fish Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Fish\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nCIRCULAR, Fish c\nAvailable Type\nFish Brconnector\nPicture\nCircular Fish\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nFish Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFish Brconnector\nFit To Next\nFish Branch Connector\nOK\nFish Branch Connector\nFish Brconnector\nHVAC Window\nCancel\nFish Brconnector"}
{"Headers": "Circular Angled c", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then CIRCULAR, Angled c in the Available Type drop-down list to display the Angled Broconnector window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Angled.\nClick Transpose Width/Depth to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint (Brco Joint). Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Angled Brconnector window was opened.\nClick Fit To Next to orientate the Angled Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Angled Branch Connector component and close the Angled Brconnector Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Angled Brconnector window.\nBranch Connector Diameter\nMAIN Width LA\nMAIN Depth LB\nAngle to MAIN\nBranch Connector Length\nDistance from Leave\nB offset\nBranch Connector Extension\nFixing to Duct\nMale Collar\nInner Extension\nBranch Connector Diameter\nBranch Connector Diameter\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nAngle to MAIN\nAngle to MAIN\nBranch Connector Length\nBranch Connector Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nBranch Connector Extension\nBranch Connector Extension\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Angled\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nCIRCULAR, Angled c\nAvailable Type\nAngled Broconnector\nPicture\nCircular Angled\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nAngled Brconnector\nFit To Next\nAngled Branch Connector\nOK\nAngled Branch Connector\nAngled Brconnector\nHVAC Window\nCancel\nAngled Brconnector"}
{"Headers": "Circular Conical c", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then CIRCULAR, Conical c in the Available Type drop-down list to display the Conical Brconnector window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Conical.\nClick Transpose Width/Depth to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Conical Brconnector window was opened.\nClick Fit To Next to orientate the Conical Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Conical Branch Connector component and close the Conical Brconnector Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Conical Brconnector window.\nBranch Connector Diameter\nMAIN Width LA\nMAIN Depth LB\nAngle to Sides\nBranch Connector Length\nDistance from Leave\nB offset\nBranch Connector Extension\nFixing to Duct\nMale Collar\nInner Extension\nBranch Connector Diameter\nBranch Connector Diameter\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nAngle to Sides\nAngle to Sides\nBranch Connector Length\nBranch Connector Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nBranch Connector Extension\nBranch Connector Extension\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Branch Connector Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Conical\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nCIRCULAR, Conical c\nAvailable Type\nConical Brconnector\nPicture\nCircular Conical\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nConical Brconnector\nFit To Next\nConical Branch Connector\nOK\nConical Branch Connector\nConical Brconnector\nHVAC Window\nCancel\nConical Brconnector"}
{"Headers": "Circular Square-Round c", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then CIRCULAR, Square-Round c in the Available Type drop-down list to display the SQRD Brconnector window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Square.\nClick Transpose Width/Depth to exchange Square Width dimension with Square Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the SQRD Brconnector window was opened.\nClick Fit To Next to orientate the Square - Round Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Square - Round Branch Connector component and close the SQRD Brconnector Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the SQRD Brconnector window.\nBranch Connector Diameter\nSquare Width\nSquare Depth\nMAIN Width LA\nMAIN Depth LB\nBranch Connector Length\nDistance from Leave\nPosition B offset\nRectangle Extension\nCircle Extension\nSquared A offset\nSquared B offset\nFixing to Duct\nMale Collar\nBranch Connector Diameter\nBranch Connector Diameter\nSquare Width\nSquare Width\nSquare Depth\nSquare Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBranch Connector Length\nBranch Connector Length\nDistance from Leave\nDistance from Leave\nPosition B offset\nPosition B offset\nRectangle Extension\nRectangle Extension\nCircle Extension\nCircle Extension\nSquared A offset\nSquared A offset\nSquared B offset\nSquared B offset\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Circle Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Square\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nCIRCULAR, Square-Round c\nAvailable Type\nSQRD Brconnector\nPicture\nCircular Square\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nSQRD Brconnector\nFit To Next\nSquare - Round Branch Connector\nOK\nSquare - Round Branch Connector\nSQRD Brconnector\nHVAC Window\nCancel\nSQRD Brconnector"}
{"Headers": "Circular Mitred c", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then CIRCULAR, Mitred c in the Available Type drop-down list to display the Mitred Brconnector window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Mitred.\nClick Transpose Width/Depth to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Mitred Brconnector window was opened.\nClick Fit To Next to orientate the Mitred Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Mitred Branch Connector component and close the Mitred Brconnector Window. You will be returned to the Create/Modify HVAC Component.\nClick Cancel to discard all field changes and close the Mitred Brconnector window.\nBranch Connector Diameter\nMAIN Width LA\nMAIN Depth LB\nBranch Connector Length\nDistance from Leave\nB offset\nBranch Connector Extension\nFixing to Duct\nMale Collar\nInner Extension\nBranch Connector Diameter\nBranch Connector Diameter\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBranch Connector Length\nBranch Connector Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nBranch Connector Extension\nBranch Connector Extension\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Branch Connector Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Mitred\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nCreate/Modify HVAC Component\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nCIRCULAR, Mitred c\nAvailable Type\nMitred Brconnector\nPicture\nCircular Mitred\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nMitred Brconnector\nFit To Next\nMitred Branch Connector\nOK\nMitred Branch Connector\nMitred Brconnector\nCreate/Modify HVAC Component\nCancel\nMitred Brconnector"}
{"Headers": "Flat Oval \u2018A\u2019 Boot f", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then FLAT OVAL, \u2018A\u2019 Boot f in the Available Type drop-down list to display the Oval \u2018A\u2019Boot Brco window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flat Oval \u2018A\u2019 Boot.\nClick Transpose Width/Depth to exchange Boot Width dimension with Boot Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Boot Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Boot Joint, you must enter the Boot Direction.\nIn Boot Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Oval \u2018A\u2019Boot Brconnector window was opened.\nClick Fit To Next to orientate the Oval \u2018A\u2019 Boot Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Oval \u2018A\u2019 Boot Branch Connector component and close the Oval \u2018A\u2019Boot Brconnector Window. You will be returned to the Create/Modify HVAC Component.\nClick Cancel to discard all field changes and close the Oval \u2018A\u2019Boot Brconnector window.\nBoot Width\nBoot Depth\nMAIN Width LA\nMAIN Depth LB\nBoot Length\nDistance From Leave\nB offset\nBoot Extension\nFixing to Duct\nMale Collar\nInner Extension\nBoot Width\nBoot Width\nBoot Depth\nBoot Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBoot Length\nBoot Length\nDistance From Leave\nDistance From Leave\nB offset\nB offset\nBoot Extension\nBoot Extension\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Boot Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nFlat Oval \u2018A\u2019 Boot\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nCreate/Modify HVAC Component\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nFLAT OVAL, \u2018A\u2019 Boot f\nAvailable Type\nOval \u2018A\u2019Boot Brco\nPicture\nFlat Oval \u2018A\u2019 Boot\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBoot Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nOval \u2018A\u2019Boot Brconnector\nFit To Next\nOval \u2018A\u2019 Boot Branch Connector\nOK\nOval \u2018A\u2019 Boot Branch Connector\nOval \u2018A\u2019Boot Brconnector\nCreate/Modify HVAC Component\nCancel\nOval \u2018A\u2019Boot Brconnector"}
{"Headers": "Flat Oval \u2018B\u2019 Boot f", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then OVAL FLAT, \u2018B\u2019 Boot f in the Available Type drop-down list to display the Oval \u2018B\u2019Boot Brco window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flat Oval \u2018B\u2019 Boot.\nClick Transpose Width/depth to exchange Boot Width dimension with Boot Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Boot Joint). Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Boot Joint, you must enter the Boot Direction.\nIn Boot Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Oval \u2018B\u2019Boot Brconnector window was opened.\nClick Fit To Next to orientate the Oval \u2018B\u2019 Boot Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Oval \u2018B\u2019 Boot Branch Connector component and close the Oval \u2018B\u2019Boot Brconnector Window. You will be returned to the Create/Modify HVAC Component.\nClick Cancel to discard all field changes and close the Oval \u2018B\u2019Boot Brconnector window.\nBoot Width\nBoot Depth\nMAIN Width LA\nMAIN Depth LB\nBoot Length\nDistance From Leave\nB offset\nBoot Extension\nFixing to Duct\nMale Collar\nInner Extension\nBoot Width\nBoot Width\nBoot Depth\nBoot Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBoot Length\nBoot Length\nDistance From Leave\nDistance From Leave\nB offset\nB offset\nBoot Extension\nBoot Extension\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Boot Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nFlat Oval \u2018B\u2019 Boot\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nCreate/Modify HVAC Component\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nOVAL FLAT, \u2018B\u2019 Boot f\nAvailable Type\nOval \u2018B\u2019Boot Brco\nPicture\nFlat Oval \u2018B\u2019 Boot\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/depth\nCreate/Modify HVAC Component\nBoot Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nOval \u2018B\u2019Boot Brconnector\nFit To Next\nOval \u2018B\u2019 Boot Branch Connector\nOK\nOval \u2018B\u2019 Boot Branch Connector\nOval \u2018B\u2019Boot Brconnector\nCreate/Modify HVAC Component\nCancel\nOval \u2018B\u2019Boot Brconnector"}
{"Headers": "Flat Oval \u2018A\u2019 Square f", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then FLAT OVAL, \u2018A\u2019 Square f in the Available Type drop-down list to display the Oval \u2018A\u2019 Square Brco window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flat Oval \u2018B\u2019 Square.\nClick Transpose Width/Depth to exchange Branch Connector Width dimension with Branch Connector Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Oval \u2018A\u2019 Square Brco window was opened.\nClick Fit To Next to orientate the Oval \u2018A\u2019 Square Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Oval \u2018A\u2019 Square Branch Connector component and close the Oval \u2018A\u2019 Square Brco Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Oval \u2018A\u2019 Square Brco window.\nBranch Connector Width\nBranch Connector Depth\nMAIN Width LA\nMAIN Depth LB\nBranch Connector Length\nDistance From Leave\nB offset\nBranch Connector Extension\nFixing to Duct\nMale Collar\nInner Extension\nBranch Connector Width\nBranch Connector Width\nBranch Connector Depth\nBranch Connector Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBranch Connector Length\nBranch Connector Length\nDistance From Leave\nDistance From Leave\nB offset\nB offset\nBranch Connector Extension\nBranch Connector Extension\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nFlat Oval \u2018B\u2019 Square\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nFLAT OVAL, \u2018A\u2019 Square f\nAvailable Type\nOval \u2018A\u2019 Square Brco\nPicture\nFlat Oval \u2018B\u2019 Square\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nOval \u2018A\u2019 Square Brco\nFit To Next\nOval \u2018A\u2019 Square Branch Connector\nOK\nOval \u2018A\u2019 Square Branch Connector\nOval \u2018A\u2019 Square Brco\nHVAC Window\nCancel\nOval \u2018A\u2019 Square Brco"}
{"Headers": "Flat Oval \u2018B\u2019 Square f", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then FLAT OVAL, \u2018B\u2019 Square f in the Available Type drop-down list to display the Oval \u2018B\u2019 Square Brco window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flat Oval \u2018B\u2019 Square.\nClick Transpose Width/Depth to exchange Branch Connector Width dimension with Branch Connector Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Oval \u2018B\u2019 Square Brco window was opened.\nClick Fit To Next to orientate the Oval \u2018B\u2019 Square Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Oval \u2018B\u2019 Square Branch Connector component and close the Oval \u2018B\u2019 Square Brco Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Oval \u2018B\u2019 Square Brco window.\nBranch Connector Width\nBranch Connector Depth\nMAIN Width LA\nMAIN Depth LB\nBranch Connector Length\nDistance from Leave\nB offset\nBrco Extension\nFixing to Duct\nMale Collar\nInner Extension\nBranch Connector Width\nBranch Connector Width\nBranch Connector Depth\nBranch Connector Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBranch Connector Length\nBranch Connector Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nBrco Extension\nBrco Extension\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nFlat Oval \u2018B\u2019 Square\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nFLAT OVAL, \u2018B\u2019 Square f\nAvailable Type\nOval \u2018B\u2019 Square Brco\nPicture\nFlat Oval \u2018B\u2019 Square\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nOval \u2018B\u2019 Square Brco\nFit To Next\nOval \u2018B\u2019 Square Branch Connector\nOK\nOval \u2018B\u2019 Square Branch Connector\nOval \u2018B\u2019 Square Brco\nHVAC Window\nCancel\nOval \u2018B\u2019 Square Brco"}
{"Headers": "Flat Oval \u2018A\u2019 Fish f", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connector in the Categories drop-down list and then FLAT OVAL, \u2018A\u2019 Fish f in the Available Type drop-down list to display the Oval \u2018A\u2019Fish Brco window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flat Oval \u2018A\u2019 Fish.\nClick Transpose Width/Depth to exchange Branch Connector Width dimension with Branch Connector Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Oval \u2018A\u2019 Fish Brco window was opened.\nClick Fit To Next to orientate the Oval \u2018A\u2019 Fish Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Oval \u2018A\u2019 Fish Branch Connector component and close the Oval \u2018A\u2019 Fish BrcoWindow. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Oval \u2018A\u2019 Fish Brco window.\nBranch Connector Width\nBranch connector Depth\nMAIN Width LA\nMAIN Depth LB\nBranch Connector Length\nDistance From Leave\nB offset\nBranch Connector Extension\nFixing to Duct\nMale Collar\nInner Extension\nBranch Connector Width\nBranch Connector Width\nBranch connector Depth\nBranch connector Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBranch Connector Length\nBranch Connector Length\nDistance From Leave\nDistance From Leave\nB offset\nB offset\nBranch Connector Extension\nBranch Connector Extension\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Branch Connector Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nFlat Oval \u2018A\u2019 Fish\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC\nBranch Connector\nCategories\nFLAT OVAL, \u2018A\u2019 Fish f\nAvailable Type\nOval \u2018A\u2019Fish Brco\nPicture\nFlat Oval \u2018A\u2019 Fish\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nOval \u2018A\u2019 Fish Brco\nFit To Next\nOval \u2018A\u2019 Fish Branch Connector\nOK\nOval \u2018A\u2019 Fish Branch Connector\nOval \u2018A\u2019 Fish Brco\nHVAC Window\nCancel\nOval \u2018A\u2019 Fish Brco"}
{"Headers": "Flat Oval \u2018B\u2019 Fish f", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then FLAT OVAL, \u2018B\u2019 Fish f in the Available Type drop-down list to display the Oval \u2018B\u2019 Fish Brco window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flat Oval \u2018B\u2019 Fish.\nClick Transpose Width/Depth to exchange Branch Connector Width dimension with Branch Connector Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Oval \u2018B\u2019 Fish Brco window was opened.\nClick Fit To Next to orientate the Oval \u2018B\u2019 Fish Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Oval \u2018B\u2019 Fish Branch Connector component and close the Oval \u2018B\u2019 Fish BrcoWindow. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Oval \u2018B\u2019 Fish Brco window.\nBranch Connector Width\nBranch Connector Depth\nMAIN Width LA\nMAIN Depth LB\nBranch Connector Length\nDistance From Leave\nB offset\nBranch Connector Extension\nFixing to Duct\nMale Collar\nInner Extension\nBranch Connector Width\nBranch Connector Width\nBranch Connector Depth\nBranch Connector Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nBranch Connector Length\nBranch Connector Length\nDistance From Leave\nDistance From Leave\nB offset\nB offset\nBranch Connector Extension\nBranch Connector Extension\nFixing to Duct\nFixing to Duct\nMale Collar\nMale Collar\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Branch Connector Extension default is auto but can be changed by you to a required dimension. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nFlat Oval \u2018B\u2019 Fish\nHVAC Catalog\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nFLAT OVAL, \u2018B\u2019 Fish f\nAvailable Type\nPicture\nFlat Oval \u2018B\u2019 Fish\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nOval \u2018B\u2019 Fish Brco\nFit To Next\nOval \u2018B\u2019 Fish Branch Connector\nOK\nOval \u2018B\u2019 Fish Branch Connector\nOval \u2018B\u2019 Fish Brco\nHVAC Window\nCancel\nOval \u2018B\u2019 Fish Brco"}
{"Headers": "Flat Oval \u2018A\u2019 Angled f", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then OVAL FLAT, \u2018A\u2019 Angled f in the Available Type drop-down list to display the Oval \u2018A\u2019 Angled Brco window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Angled.\nClick Transpose Width/Depth to exchange Branch Connector Width dimension with Branch Connector Depth dimension or to exchange MAIN Width LA dimension with MAIN depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to HVAC Components for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Oval \u2018A\u2019 Angled Brco window was opened.\nClick Fit To Next to orientate the Oval \u2018A\u2019 Angled Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Oval \u2018A\u2019 Angled Branch Connector component and close the Oval \u2018A\u2019 Angled Brco Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Oval \u2018A\u2019 Angled Brco window.\nBranch Connector Width\nBranch Connector Depth\nMAIN Width LA\nMAIN Depth LB\nAngle to Main\nBranch Connector Length\nDistance from Leave\nB offset\nBranch Connector Extension\nFixing to Duct\nInner Extension\nBranch Connector Width\nBranch Connector Width\nBranch Connector Depth\nBranch Connector Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nAngle to Main\nAngle to Main\nBranch Connector Length\nBranch Connector Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nBranch Connector Extension\nBranch Connector Extension\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Angled\nHVAC Catalog\nHVAC Catalog\nHVAC Components\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nOVAL FLAT, \u2018A\u2019 Angled f\nAvailable Type\nPicture\nRectangular Angled\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nHVAC Components\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\n\nFit To Next\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Flat Oval \u2018B\u2019 Angled f", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Branch Connectors in the Categories drop-down list and then FLAT OVAL, \u2018B\u2019 Angled f in the Available Type drop-down list to display the Oval \u2018B\u2019 Angled Brco window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Angled.\nClick Transpose Width/Depth to exchange Branch Connector Width dimension with Branch Connector Depth dimension or to exchange MAIN Width LA dimension with MAIN Depth LB dimension.\nSpecify a type of joint to use for the Branch Connector Joint. Refer to HVAC Components for a detailed description.\nAfter selecting the type of joint to use for the Branch Connector Joint, you must enter the Branch Connector Direction.\nIn Branch Connector Direction specify axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Oval \u2018B\u2019 Angled Brco window was opened.\nClick Fit To Next to orientate the Oval \u2018B\u2019 Angled Branch Connector to automatically fit this piece of HVAC to the next piece.\nClick OK to create the Oval \u2018B\u2019 Angled Branch Connector component and close the Oval \u2018B\u2019 Angled Brco Window. You will be returned to the HVAC Window.\nClick Cancel to discard all field changes and close the Oval \u2018B\u2019 Angled Brco window.\nBranch Connector Width\nBranch Connector Depth\nMAIN Width LA\nMAIN Depth LB\nAngle to Main\nBranch Connector Length\nDistance from Leave\nB offset\nBranch Connector Extension\nFixing to Duct\nInner Extension\nBranch Connector Width\nBranch Connector Width\nBranch Connector Depth\nBranch Connector Depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nAngle to Main\nAngle to Main\nBranch Connector Length\nBranch Connector Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nBranch Connector Extension\nBranch Connector Extension\nFixing to Duct\nFixing to Duct\nInner Extension\nInner Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Angled\nHVAC Catalog\nHVAC Catalog\nHVAC Components\nHVAC Window\nHVAC Component\nHVAC Window\nBranch Connectors\nCategories\nFLAT OVAL, \u2018B\u2019 Angled f\nAvailable Type\nPicture\nRectangular Angled\nNote\n:\nHVAC Catalog\nHVAC Catalog\nTranspose Width/Depth\nHVAC Components\nBranch Connector Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nOval \u2018B\u2019 Angled Brco\nFit To Next\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Inline Plant Equipment", "Content": "The Inline Plant Equipment option of the Categories drop-down list is an umbrella for the Inline Plant Equipment components for selection in the catalog database.\n\n\n\nInline Plant Equipment\nCategories"}
{"Headers": "Rectangular Fire Damper", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then RECTANGULAR, Fire Damper in the Available Type drop-down list to display the Rectangular Fire Damper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Fire Damper.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with the Duct Width AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Curtain Direction.\nIn the Curtain Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Rectangular Fire Damper window was opened.\nClick Fit to orientate the Rectangular Fire Damper to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Rectangular Fire Damper component and close the Rectangular Fire Damper Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Rectangular Fire Damper window.\nFD Name(Ref)\nDuct Width AA\nDuct Depth AB\nLength\nArrive Extension\nLeave Extension\nCurtain Height\nRight Width\nLeft Width\nBottom Width\nFD Name(Ref)\nFD Name(Ref)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nCurtain Height\nCurtain Height\nRight Width\nRight Width\nLeft Width\nLeft Width\nBottom Width\nBottom Width\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Manufacturer cannot be changed.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Fire Damper\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nRECTANGULAR, Fire Damper\nAvailable Type\nRectangular Fire Damper\nPicture\nRectangular Fire Damper\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Width AB dimension.\nCreate/Modify HVAC Component\nCurtain Direction\nCurtain Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nRectangular Fire Damper\nHVAC Window\nCancel\nRectangular Fire Damper"}
{"Headers": "Rectangular Flanged Fire Damper", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then RECTANGULAR, Flanged Fire Damper in the Available Type drop-down list to display the Rectangular Flanged FD window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Flanged Fire Damper.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with the Duct Width AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to HVAC Components for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Control Direction.\nIn the Control Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Actuator fields will be pre-populated with default values but can be changed by you.\nThe Clash Vol fields will be pre-populated with the obstruction volumes associated with the rectangular flanged FD component and the ducting, but can be changed by you.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Rectangular Flanged FD window was opened.\nClick Fit to orientate the Rectangular Flanged FD to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Rectangular Flanged FD component and close the Rectangular Flanged FD Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Rectangular Flanged FD window.\nFD Name(Ref)\nDuct Width AA\nDuct Depth AB\nLength\nControl Direction\nFD Name(Ref)\nFD Name(Ref)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nControl Direction\nControl Direction\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Flanged Fire Damper\nHVAC Catalog\nHVAC Components\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nRECTANGULAR, Flanged Fire Damper\nAvailable Type\nRectangular Flanged FD\nPicture\nRectangular Flanged Fire Damper\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nDuct Width AA\nDuct Width AB dimension.\nHVAC Components\nControl Direction\nControl Direction\nActuator\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nRectangular Flanged FD\nFit\nOK\nRectangular Flanged FD\nHVAC Window\nCancel\nRectangular Flanged FD"}
{"Headers": "Rectangular Control Damper", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then RECTANGULAR, Control Damper in the Available Type drop-down list to display the Control Damper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Control Damper.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with the Duct Width AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Handle Direction.\nIn the Handle Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol fields will be pre-populated with the obstruction volumes associated with the rectangular flanged FD component and the ducting, but can be changed by you.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Control Damper window was opened.\nClick Fit to orientate the Control Damper to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Control Damper component and close the Control Damper Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Control Damper window.\nVCD Name(Ref)\nDuct Width AA\nDuct Depth AB\nLength\nHandle Direction\nVCD Name(Ref)\nVCD Name(Ref)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nHandle Direction\nHandle Direction\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Control Damper\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nRECTANGULAR, Control Damper\nAvailable Type\nControl Damper\nPicture\nRectangular Control Damper\nNote\n:\nHVAC Catalog\nDuct Width AA\nDuct Width AB dimension.\nCreate/Modify HVAC Component\nHandle Direction\nDirection\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nControl Damper\nHVAC Window\nCancel\nControl Damper"}
{"Headers": "Rectangular Motorised Damper r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then RECTANGULAR, Motorised Damper in the Available Type drop-down list to display the Motorised Damper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Motorised Damper.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with the Duct Width AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Spindle Direction.\nIn the Spindle Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol fields will be pre-populated with the obstruction volumes associated with the rectangular flanged FD component and the ducting, but can be changed by you.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Motorised Damper window was opened.\nClick Fit to orientate the Motorised Damper to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Motorised Damper component and close the Motorised Damper Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Motorised Damper window.\nMVCD Name(Ref)\nDuct Width AA\nDuct Depth AB\nLength\nSpindle Direction\nMVCD Name(Ref)\nMVCD Name(Ref)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nSpindle Direction\nSpindle Direction\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Motorised Damper\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nRECTANGULAR, Motorised Damper\nAvailable Type\nMotorised Damper\nPicture\nRectangular Motorised Damper\nNote\n:\nHVAC Catalog\nDuct Width AA\nDuct Width AB dimension.\nCreate/Modify HVAC Component\nSpindle Direction\nSpindle Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nMotorised Damper\nFit\nOK\nMotorised Damper\nHVAC Window\nCancel\nMotorised Damper"}
{"Headers": "Rectangular Heater Battery r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then RECTANGULAR, Heater Battery in the Available Type drop-down list to display the Heater Battery window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Heater Battery.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with the Duct Width AB dimension.\nSpecify a type of joint to use for the Arrjoint (Arrive Joint) and Leajoint (Leave joint). Refer to HVAC Components for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Pipes Direction.\nIn the Pipes Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Heater Battery window was opened.\nClick Fit to orientate the Heater Battery to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Heater Battery component and close the Heater Battery Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Heater Battery window.\nHB Name(Ref)\nDuct Width AA\nDuct Depth AB\nLength\nHB Name(Ref)\nHB Name(Ref)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Heater Battery\nHVAC Catalog\nHVAC Components\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nRECTANGULAR, Heater Battery\nAvailable Type\nHeater Battery\nPicture\nRectangular Heater Battery\nNote\n:\nHVAC Catalog\nDuct Width AA\nDuct Width AB dimension.\nHVAC Components\nPipes Direction\nPipes Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nHeater Battery\nFit\nOK\nHeater Battery\nHVAC Window\nCancel\nHeater Battery"}
{"Headers": "Rectangular Cooler Battery r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then RECTANGULAR, Cooler Battery in the Available Type drop-down list to display the Cooler Battery window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Cooler Battery.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with the Duct Width AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Pipes Direction.\nIn the Pipes Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Cooler Battery window was opened.\nClick Fit to orientate the Cooler Battery to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Cooler Battery component and close the Cooler Battery Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Cooler Battery window.\nCB Name(Ref)\nDuct Width AA\nDuct Depth AB\nLength\nCB Name(Ref)\nCB Name(Ref)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Cooler Battery\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nRECTANGULAR, Cooler Battery\nAvailable Type\nCooler Battery\nPicture\nRectangular Cooler Battery\nNote\n:\nHVAC Catalog\nDuct Width AA\nDuct Width AB dimension.\nCreate/Modify HVAC Component\nPipes Direction\nPipes Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nCooler Battery\nHVAC Window\nCancel\nBattery"}
{"Headers": "Rectangular Silencer r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then RECTANGULAR, Silencer in the Available Type drop-down list to display the Silencer window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Silencer.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with the Duct Width AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Width Direction.\nIn the Width Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Silencer window was opened.\nClick Fit to orientate the Silencer to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Silencer component and close the Silencer Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Silencer window.\nName(Ref)\nDuct Width AA\nDuct Depth AB\nLength\nWidth Direction\nName(Ref)\nName(Ref)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nWidth Direction\nWidth Direction\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Silencer\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nRECTANGULAR, Silencer\nAvailable Type\nSilencer\nPicture\nRectangular Silencer\nNote\nHVAC Catalog\nDuct Width AA\nDuct Width AB dimension.\nCreate/Modify HVAC Component\nWidth Direction\nWidth Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nSilencer\nFit\nOK\nSilencer\nHVAC Window\n.\nCancel\nSilencer"}
{"Headers": "Rectangular Attenuated Bend r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then RECTANGULAR, Attenuated Bend in the Available Type drop-down list to display the Attenuated Bend window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Attenuated Bend.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with the Duct Width AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Leave Direction.\nIn the Leave Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Attenuated Bend window was opened.\nClick Fit to orientate the Attenuated Bend to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Attenuated Bend component and close the Attenuated Bend Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Attenuated Bend window.\nName(Ref)\nDuct Width AA\nDuct Depth AB\nDuct Width LA\nArrive Throat\nLeave Throat\nInside Radius\nBack Radius\nArrive Back Fillet\nLeave to Back Fillet\nArrive Throat Fillet\nLeave to Throat Fillet\nName(Ref)\nName(Ref)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nDuct Width LA\nDuct Width LA\nArrive Throat\nArrive Throat\nLeave Throat\nLeave Throat\nInside Radius\nInside Radius\nBack Radius\nBack Radius\nArrive Back Fillet\nArrive Back Fillet\nLeave to Back Fillet\nLeave to Back Fillet\nArrive Throat Fillet\nArrive Throat Fillet\nLeave to Throat Fillet\nLeave to Throat Fillet\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Attenuated Bend\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nRECTANGULAR, Attenuated Bend\nAvailable Type\nAttenuated Bend\nPicture\nRectangular Attenuated Bend\nNote\n:\nHVAC Catalog\nDuct Width AA\nDuct Width AB dimension.\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Rectangular General Plant Item r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then General Plant Item in the Available Type drop-down list to display the General Plant Item window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular General Plant Item.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with the Duct Width AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Operator Side.\nIn the Operator Side specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol fields will be pre-populated with the obstruction volumes associated with the rectangular flanged FD component and the ducting, but can be changed by you.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the General Plant Item window was opened.\nClick Fit to orientate the General Plant Item to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the General Plant Item component and close the General Plant Item Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the General Plant Item window.\nName(Ref)\nDuct Width AA\nDuct Depth AB\nLength\nName(Ref)\nName(Ref)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular General Plant Item\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nGeneral Plant Item\nAvailable Type\nGeneral Plant Item\nPicture\nRectangular General Plant Item\nNote\n:\nHVAC Catalog\nDuct Width AA\nDuct Width AB dimension.\nCreate/Modify HVAC Component\nOperator Side\nOperator Side\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Rectangular Grille off Brco", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then RECTANGULAR, GRILLE off Brco in the Available Type drop-down list to display the Off Brco Grille window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Grille Off Branch Connector.\nClick Transpose Width/Depth to exchange Branch Connector Width dimension with the Branch Connector Depth dimension.\nClick Transpose Width/Depth to exchange End Width dimension with the End Depth dimension.\nClick Transpose Width/Depth to exchange MAIN Width LA dimension with the MAIN Depth LB dimension.\nIn the Grille Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol OUT field is pre-populated with the obstruction volume associated with the Off Branch Connector Grille and the ducting.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Off Brco Grille window was opened.\nClick Fit to orientate the Off Branch Connector Grille to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Off Branch Connector Grille component and close the Off Brco Grille Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Off Brco Grille window.\nUNIT Name(Ref)\nBranch Connector Width\nBranch Connector Depth\nEnd width\nEnd depth\nMAIN Width LA\nMAIN Depth LB\nOverall Branch Connector Length\nDistance From Leave\nB offset\nGrille Length\n\u2018A\u2019 Extension\nFixing to Branch Connector\nEnd Joint\nEnd Joint Width\nEnd Joint Depth\nEnd Joint Thickness\nUNIT Name(Ref)\nUNIT Name(Ref)\nBranch Connector Width\nBranch Connector Width\nBranch Connector Depth\nBranch Connector Depth\nEnd width\nEnd width\nEnd depth\nEnd depth\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nOverall Branch Connector Length\nOverall Branch Connector Length\nDistance From Leave\nDistance From Leave\nB offset\nB offset\nGrille Length\nGrille Length\n\u2018A\u2019 Extension\n\u2018A\u2019 Extension\nFixing to Branch Connector\nFixing to Branch Connector\nEnd Joint\nEnd Joint\nEnd Joint Width\nEnd Joint Width\nEnd Joint Depth\nEnd Joint Depth\nEnd Joint Thickness\nEnd Joint Thickness\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe HVAC component can only be created following a HVAC branch connector element in the design hierarchy.\nNote:\nThe HVAC component can only be created under a branch connector element.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Grille Off Branch Connector\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nRECTANGULAR, GRILLE off Brco\nAvailable Type\nOff Brco Grille\nNote\n:\nNote\n:\nPicture\nRectangular Grille Off Branch Connector\nNote\n:\nHVAC Catalog\nBranch Connector Width\nBranch Connector Depth dimension.\nEnd Width\nEnd Depth dimension.\nMAIN Width LA\nMAIN Depth LB dimension.\nDirection\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Rectangular Grille in Line", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then RECTANGULAR, Grille in line in the Available Type drop-down list to display the In line Grille window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Grille (in line).\nClick Transpose Width/Depth to exchange Duct Width AA dimension with the Duct Depth AB dimension.\nClick Transpose Width/Depth to exchange End Width dimension with the End Depth dimension.\nIn the Width Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol OUT field is pre-populated with the obstruction volume associated with the In line Grille and the ducting.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the In line Grille window was opened.\nClick Fit to orientate the In line Grille to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the In line Grille component and close the In line Grille Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the In line Grille window.\nUNIT Name(Ref)\nDuct Width AA\nDuct Depth AB\nEnd Width\nEnd Depth\nGrille Length\n\u2018A\u2019 Extension\nFixing to Duct\nEnd Joint\nEnd Joint Width\nEnd Joint Depth\nEnd Joint Thickness\nUNIT Name(Ref)\nUNIT Name(Ref)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nEnd Width\nEnd Width\nEnd Depth\nEnd Depth\nGrille Length\nGrille Length\n\u2018A\u2019 Extension\n\u2018A\u2019 Extension\nFixing to Duct\nFixing to Duct\nEnd Joint\nEnd Joint\nEnd Joint Width\nEnd Joint Width\nEnd Joint Depth\nEnd Joint Depth\nEnd Joint Thickness\nEnd Joint Thickness\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Grille (in line)\nHVAC Catalog\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nRECTANGULAR, Grille in line\nAvailable Type\nIn line Grille\nPicture\nRectangular Grille (in line)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nDuct Width AA\nDuct Depth AB dimension.\nEnd Width\nEnd Depth dimension.\nDirection\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Rectangular Air Handling Unit", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then RECTANGULAR, Air Handling Unit in the Available Type drop-down list to display the Air Handling Unit window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Air Handling Unit.\nClick Transpose Width/Depth to exchange First Width AA dimension with the First Depth AB dimension.\nClick Transpose Width/Depth to exchange Second Width dimension with the Second Depth dimension.\nClick Transpose Width/Depth to exchange Third Width dimension with the Third Depth dimension.\nSpecify a type of joint to use for the Arrive Joint, Leave Joint and Branch Joint. Refer to Create/Modify HVAC Component for a detailed description.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Air Handling Unit window was opened.\nClick Fit to orientate the Air Handling Unit to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Air Handling Unit component and close the Air Handling Unit Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Air Handling Unit window.\nName(Ref)\nFirst Width AA\nFirst Depth AB\nSecond Width\nSecond Depth\nThird Width\nThird Depth\nOverall Unit Length\nOverall Unit Width\nOverall Unit Height\nBase Height\nFirst Height\nSecond Height\nThird EndPosition\nFirst Extension\nSecond Extension\nThird Extension\nName(Ref)\nName(Ref)\nFirst Width AA\nFirst Width AA\nFirst Depth AB\nFirst Depth AB\nSecond Width\nSecond Width\nSecond Depth\nSecond Depth\nThird Width\nThird Width\nThird Depth\nThird Depth\nOverall Unit Length\nOverall Unit Length\nOverall Unit Width\nOverall Unit Width\nOverall Unit Height\nOverall Unit Height\nBase Height\nBase Height\nFirst Height\nFirst Height\nSecond Height\nSecond Height\nThird EndPosition\nThird EndPosition\nFirst Extension\nFirst Extension\nSecond Extension\nSecond Extension\nThird Extension\nThird Extension\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nAn air handling unit can only be created as the first item in a HVAC branch.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nAir Handling Unit\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nRECTANGULAR, Air Handling Unit\nAvailable Type\nAir Handling Unit\nNote\n:\nPicture\nAir Handling Unit\nHVAC Catalog\nTranspose Width/Depth\nFirst Width AA\nFirst Depth AB dimension.\nWidth/Depth\nSecond Width\nSecond Depth dimension.\nTranspose Width/Depth\nThird Width\nThird Depth dimension.\nCreate/Modify HVAC Component\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel"}
{"Headers": "Rectangular Centrifugal Fan r", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then Centrifugal Fan in the Available Type drop-down list to display the Centrifugal Fan window:\n\nCentrifugal Fans can be left or right handed, from the Type drop-down list, select Left or Right.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Centrifugal Fan.\nClick Transpose Width/Depth to exchange Rectangle Width AA dimension with the Rectangle Depth AB dimension.\nSpecify a type of joint to use for the Rectangle Joint and Circle Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Rectangle Joint and Circle Joint you must enter the Circle Direction.\nIn the Circle Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Centrifugal Fan window was opened.\nClick Fit to orientate the Centrifugal Fan to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Centrifugal Fan component and close the Centrifugal Fan Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Centrifugal Fan window.\nName(Ref)\nRectangle Width AA\nRectangle Depth AB\nCircular Diameter\nCentrifugal Fans can be left or right handed, from the Type drop-down list, select Left or Right.\nOutside Diameter\nCenterline Height\nCircle Extension\nName(Ref)\nName(Ref)\nRectangle Width AA\nRectangle Width AA\nRectangle Depth AB\nRectangle Depth AB\nCircular Diameter\nCircular Diameter\nCentrifugal Fans can be left or right handed, from the Type drop-down list, select Left or Right.\nCentrifugal Fans can be left or right handed, from the Type drop-down list, select Left or Right.\nOutside Diameter\nOutside Diameter\nCenterline Height\nCenterline Height\nCircle Extension\nCircle Extension\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nAn centrifugal fan can only be created as the first item in a HVAC branch.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCentrifugal Fan\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nCentrifugal Fan\nAvailable Type\nCentrifugal Fan\nNote\nType\nLeft\nRight\nType\nLeft\nRight\nPicture\nCentrifugal Fan\nHVAC Catalog\nTranspose Width/Depth\nRectangle Width AA\nRectangle Depth AB dimension.\nCreate/Modify HVAC Component\nCircle Direction\nCircle Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel"}
{"Headers": "Circular Fire Damper", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then CIRCULAR, Fire Damper in the Available Type drop-down list to display the Circular Fire Damper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Fire Damper.\nSpecify a type of joint to use for the Arrjoint (Arrive Joint) and Leajoint (Leave joint). Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Curtain Direction.\nIn the Curtain Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Circular Fire Damper window was opened.\nClick Fit to orientate the Circular Fire Damper to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Circular Fire Damper component and close the Circular Fire Damper Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Circular Fire Damper window.\nFD Name(Ref)\nDuct Diameter\nLength\nArrive Extension\nLeave Extension\nCurtain Height\nRight Width\nLeft Width\nBottom Width\nFD Name(Ref)\nFD Name(Ref)\nDuct Diameter\nDuct Diameter\nLength\nLength\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nCurtain Height\nCurtain Height\nRight Width\nRight Width\nLeft Width\nLeft Width\nBottom Width\nBottom Width\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Manufacturer cannot be changed.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Fire Damper\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nCIRCULAR, Fire Damper\nAvailable Type\nCircular Fire Damper\nPicture\nCircular Fire Damper\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nCurtain Direction\nCurtain Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nCircular Fire Damper\nHVAC Window\nCancel\nCircular Fire Damper"}
{"Headers": "Circular Flanged Fire Damper", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then CIRCULAR, Flanged Fire Damper in the Available Type drop-down list to display the Circular Flanged FD window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Flanged Fire Damper.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Control Direction.\nIn the Control Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Actuator fields will be pre-populated with default values but can be changed by you.\nThe Clash Vol fields will be pre-populated with the obstruction volumes associated with the rectangular flanged FD component and the ducting, but can be changed by you.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Circular Flanged FD window was opened.\nClick Fit to orientate the Circular Flanged FD to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Circular Flanged FD component and close the Circular Flanged FD Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Circular Flanged FD window.\nFFD Name(Ref)\nDuct Diameter\nSquare Body Size\nBody Flanged Size\nLength\nArrive Extension\nLeave Extension\nFFD Name(Ref)\nFFD Name(Ref)\nDuct Diameter\nDuct Diameter\nSquare Body Size\nSquare Body Size\nBody Flanged Size\nBody Flanged Size\nLength\nLength\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Flanged Fire Damper\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nCIRCULAR, Flanged Fire Damper\nAvailable Type\nCircular Flanged FD\nPicture\nCircular Flanged Fire Damper\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nControl Direction\nControl Direction\nActuator\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nCircular Flanged FD\nHVAC Window\nCancel\nCircular Flanged FD"}
{"Headers": "Circular Control Damper", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then CIRCULAR, Control Damper in the Available Type drop-down list to display the Control Damper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Control Damper.\nSpecify a type of joint to use for the Arrjoint (Arrive Joint) and Leajoint (Leave joint). Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Handle Direction.\nIn the Handle Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol fields will be pre-populated with the obstruction volumes associated with the rectangular flanged FD component and the ducting, but can be changed by you.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Control Damper window was opened.\nClick Fit to orientate the Control Damper to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Control Damper component and close the Control Damper Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Control Damper window\nVCD Name(Ref)\nDuct Diameter\nSquare Body Size\nBody Flange Size\nLength\nArrive Extension\nLeave Extension\nVCD Name(Ref)\nVCD Name(Ref)\nDuct Diameter\nDuct Diameter\nSquare Body Size\nSquare Body Size\nBody Flange Size\nBody Flange Size\nLength\nLength\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Control Damper\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nCIRCULAR, Control Damper\nAvailable Type\nControl Damper\nPicture\nCircular Control Damper\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nHandle Direction\nDirection\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nControl Damper\nHVAC Window\nCancel\nControl Damper"}
{"Headers": "Circular Axial Flow Fan", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then CIRCULAR, Axial Flow Fan in the Available Type drop-down list to display the Axial Flow Fan window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Axial Flow Fan.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Motor Direction.\nIn the Motor Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Axial Flow Fan window was opened.\nClick Fit to orientate the Axial Flow Fan to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Axial Flow Fan component and close the Axial Flow Fan Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Axial Flow Fan window.\nName(Ref)\nDuct Diameter\nOverall Length\nMale Collar (A)\nMale Collar (L)\nMotor Height\nMotor Length\nMotor Width\nMotor Pos to Pa\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nOverall Length\nOverall Length\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nMotor Height\nMotor Height\nMotor Length\nMotor Length\nMotor Width\nMotor Width\nMotor Pos to Pa\nMotor Pos to Pa\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Axial Flow Fan\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nCIRCULAR, Axial Flow Fan\nAvailable Type\nAxial Flow Fan\nPicture\nCircular Axial Flow Fan\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nMotor Direction\nDirection\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Circular Silencer", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then CIRCULAR, Silencer in the Available Type drop-down list to display the Circular Silencer window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Silencer.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Circular Silencer window was opened.\nClick Fit to orientate the Circular Silencer to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Circular Silencer component and close the Circular Silencer Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Circular Silencer window.\nName(Ref)\nDuct Diameter\nOuter Diameter\nOverall Length\nExtension (A)\nExtension (L)\nMale Collar (A)\nMale Collar (L)\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nOuter Diameter\nOuter Diameter\nOverall Length\nOverall Length\nExtension (A)\nExtension (A)\nExtension (L)\nExtension (L)\nMale Collar (A)\nMale Collar (A)\nMale Collar (L)\nMale Collar (L)\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Extension (A) and Extension (L) default is auto but can be changed by you to a required dimension.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular Silencer\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nCIRCULAR, Silencer\nAvailable Type\nCircular Silencer\nPicture\nCircular Silencer\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nSilencer\nHVAC Window\nCancel\nSilencer"}
{"Headers": "Circular General Plant Item", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then CIRCULAR, General Plant Item in the Available Type drop-down list to display the General Plant Item window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular General Plant Item.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Operator Side.\nIn the Operator Side specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol fields will be pre-populated with the obstruction volumes associated with the rectangular flanged FD component and the ducting, but can be changed by you.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the General Plant Item window was opened.\nClick Fit to orientate the General Plant Item to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the General Plant Item component and close the General Plant Item Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the General Plant Item window.\nName(Ref)\nDuct Diameter\nBody Size (X)\nBody Size (Y)\nBody Flange Size\nLength\nArrive Extension\nLeave Extension\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nBody Size (X)\nBody Size (X)\nBody Size (Y)\nBody Size (Y)\nBody Flange Size\nBody Flange Size\nLength\nLength\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nCircular General Plant Item\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nCIRCULAR,\nGeneral Plant Item\nAvailable Type\nGeneral Plant Item\nPicture\nCircular General Plant Item\nNote\nHVAC Catalog\nCreate/Modify HVAC Component\nOperator Side\nOperator Side\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Grille Off Brco", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then Grille off brco in the Available Type drop-down list to display the Off Brco Grille window.\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Grille Off Branch Connector.\nClick Transpose Width/Depth to exchange MAIN Width LA dimension with the MAIN Depth LB dimension.\nIn the Grille Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol OUT field is pre-populated with the obstruction volume associated with the Off Brco Grille and the ducting.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Off Brco Grille window was opened.\nClick Fit to Next to orientate the Off Brco Grille to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Off Brco Grille component and close the Off Brco Grille Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Off Brco Grille window.\nUNIT Name(Ref)\nBranch Connector Diameter\nEnd Diameter\nMAIN Width LA\nMAIN Depth LB\nOverall Branch Connector Length\nDistance from Leave\nB offset\nGrille Length\n\u2018A\u2019 Extension\nFixing to Branch Connector\nEnd Joint\nEnd Joint Width\nEnd Joint Depth\nEnd Joint Thickness\nUNIT Name(Ref)\nUNIT Name(Ref)\nBranch Connector Diameter\nBranch Connector Diameter\nEnd Diameter\nEnd Diameter\nMAIN Width LA\nMAIN Width LA\nMAIN Depth LB\nMAIN Depth LB\nOverall Branch Connector Length\nOverall Branch Connector Length\nDistance from Leave\nDistance from Leave\nB offset\nB offset\nGrille Length\nGrille Length\n\u2018A\u2019 Extension\n\u2018A\u2019 Extension\nFixing to Branch Connector\nFixing to Branch Connector\nEnd Joint\nEnd Joint\nEnd Joint Width\nEnd Joint Width\nEnd Joint Depth\nEnd Joint Depth\nEnd Joint Thickness\nEnd Joint Thickness\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe HVAC component can only be created following a HVAC branch connector element in the design hierarchy.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nRectangular Grille Off Branch Connector\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nGrille off brco\nAvailable Type\nOff Brco Grille\nNote\n:\nPicture to display a detailed drawing for\nRectangular Grille Off Branch Connector\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nMAIN Width LA\nMAIN Depth LB dimension.\nDirection\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nto Next\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Circular Grille in line", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then CIRCULAR, Grille in line in the Available Type drop-down list to display the In line Grille window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Grille (in line).\nThe Clash Vol OUT field is pre-populated with the obstruction volume associated with the Off Brco Grille and the ducting.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the In line Grille window was opened.\nClick Fit to orientate the In line Grille to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the In line Grille component and close the In lineGrille Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the In line Grille window.\nUnit Name(Ref)\nDuct Diameter\nEnd Diameter\nGrille Length\n\u2018A\u2019 Extension\nFixing to Duct\nEnd Joint\nEnd Joint Width\nEnd Joint Depth\nEnd Joint Thickness\nUnit Name(Ref)\nUnit Name(Ref)\nDuct Diameter\nDuct Diameter\nEnd Diameter\nEnd Diameter\nGrille Length\nGrille Length\n\u2018A\u2019 Extension\n\u2018A\u2019 Extension\nFixing to Duct\nFixing to Duct\nEnd Joint\nEnd Joint\nEnd Joint Width\nEnd Joint Width\nEnd Joint Depth\nEnd Joint Depth\nEnd Joint Thickness\nEnd Joint Thickness\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Fixing to Duct joint default is joint defined in the HVAC Catalog but can be changed by you to the required joint.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nCircular Grille (in line)\nHVAC Catalog\nHVAC Catalog\nHVAC Window\nHVAC Component\nHVAC\nInline Plant Equipment\nCategories\nCIRCULAR, Grille in line\nAvailable Type\nIn line Grille\nPicture\nCircular Grille (in line)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Flat Oval Fire Damper f", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Inline Plant Equipment in the Categories drop-down list and then FLAT OVAL, Fire Damper in the Available Type drop-down list to display the Oval Fire Damper window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flat Oval Fire Damper.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with the Duct Width AB dimension.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Curtain Direction.\nIn the Curtain Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Oval Fire Damper window was opened.\nClick Fit to orientate the Oval Fire Damper to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Oval Fire Damper component and close the Oval Fire Damper Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Oval Fire Damper window.\nFD Name(Ref)\nDuct Width AA\nDuct Depth AB\nLength\nArrive Extension\nLeave Extension\nCurtain Height\nRight Width\nLeft Width\nBottom Width\nFD Name(Ref)\nFD Name(Ref)\nDuct Width AA\nDuct Width AA\nDuct Depth AB\nDuct Depth AB\nLength\nLength\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nCurtain Height\nCurtain Height\nRight Width\nRight Width\nLeft Width\nLeft Width\nBottom Width\nBottom Width\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Manufacturer cannot be changed.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nFlat Oval Fire Damper\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nInline Plant Equipment\nCategories\nFLAT OVAL, Fire Damper\nAvailable Type\nOval Fire Damper\nPicture\nFlat Oval Fire Damper\nNote\n:\nHVAC Catalog\nDuct Width AA\nDuct Width AB dimension.\nCreate/Modify HVAC Component\nCurtain Direction\nCurtain Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nOval Fire Damper\nFit\nOval Fire Damper\nOK\nOval Fire Damper\nOval Fire Damper\nHVAC Window\nCancel\nOval Fire Damper"}
{"Headers": "Extra Inline Equipment", "Content": "The Extra Inline Equipment option of the Categories drop-down list is an umbrella for the Inline Equipment components for selection in the catalog database.\n\n\n\nExtra Inline Equipment\nCategories"}
{"Headers": "Flat Low Vel\u2019 Terminal", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Flat Low Vel\u2019 Terminal in the Available Type drop-down list to display the Flat LV Terminal window:\n\nThe Flat LV Terminal window default is a standard stock size, but can be changed by you using the following two methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the size for the HVAC component.\nIn the Handling drop-down list, click the Handling of the Flat LV Terminal.\nIn the Direction X specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Face Clash Volume field is pre-populated with the obstruction volume associated with the Flat LV Terminal and the ducting.\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Size drop-down list, click Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Flat Low Velocity Terminal.\nSpecify a type of joint to use for the Arrive Joint and Leave Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint and Leave Joint you must enter the Direction X.\nIn the Direction X specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Face Clash Volume field is pre-populated with the obstruction volume associated with the Flat LV Terminal and the ducting.\nIn the Position list, select Connect or Unchanged:\nYou can orientate the face of the Flat LV Terminal component, from the Handling drop-down list, select Face Back or Face Front.\nClick Defaults to reset all the fields back to when the Flat LV Terminal window was opened.\nClick Fit to orientate the Flat LV Terminal to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Flat LV Terminal component and close the Flat LV Terminal Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Flat LV Terminal window.\nName(Ref)\nDuct Diameter\nEnd Width (A)\nEnd Height (D)\nEnd Depth\nPlenum Width (B)\nPlenum Height (E)\nPlenum Depth (G)\nTop Width (C)\nTop Height\nTop Depth (F)\nTop to Conn cl(l)\nCentreline Offset\nArrive Extension\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nEnd Width (A)\nEnd Width (A)\nEnd Height (D)\nEnd Height (D)\nEnd Depth\nEnd Depth\nPlenum Width (B)\nPlenum Width (B)\nPlenum Height (E)\nPlenum Height (E)\nPlenum Depth (G)\nPlenum Depth (G)\nTop Width (C)\nTop Width (C)\nTop Height\nTop Height\nTop Depth (F)\nTop Depth (F)\nTop to Conn cl(l)\nTop to Conn cl(l)\nCentreline Offset\nCentreline Offset\nArrive Extension\nArrive Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Catalog\nHVAC Catalog\nFlat Low Velocity Terminal\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC\nExtra Inline Equipment\nCategories\nFlat Low Vel\u2019 Terminal\nAvailable Type\nFlat LV Terminal\nStandard Stock Sizes\nName(Ref)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nHandling\nDirection X\nNon Standard Stock Sizes (Special)\nPicture\nFlat Low Velocity Terminal\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nDirection X\nDirection X\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Corner Mount LV Terminal", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Corner Mount LV Terminal in the Available Type drop-down list to display the Corner Mounting LVT window:\n\nThe Corner Mounting LVT window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nIn the Front Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Face Clash Vol field is pre-populated with the obstruction volume associated with the Corner Mounting LVT and the ducting.\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Sizes drop-down list, click Special.\nyou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for LV Terminal for Corner Mounting.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, you must enter the Front Direction.\nIn the Front Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Front Clash Vol field is pre-populated with the obstruction volume associated with the Corner Mounting LVT and the ducting.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Corner Mounting LVT window was opened.\nClick Fit to orientate the Corner Mounting LVT to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Corner Mounting LVT component and close the Corner Mounting LVT Window. You will be returned to the HVAC Window\nClick Cancel to discard all the field changes and close the Corner Mounting LVT window.\nName(Ref)\nDuct Diameter\nBody Radius (A)\nBody Length (B)\nBody clHeight (D)\nArrive Extension\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nBody Radius (A)\nBody Radius (A)\nBody Length (B)\nBody Length (B)\nBody clHeight (D)\nBody clHeight (D)\nArrive Extension\nArrive Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nLV Terminal for Corner Mounting\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nCorner Mount LV Terminal\nAvailable Type\nCorner Mounting LVT\nCorner Mounting LVT\nStandard Stock Sizes\nName(Ref)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nFront Direction\nNon Standard Stock Sizes (Special)\nPicture\nLV Terminal for Corner Mounting\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nFront Direction\nFront Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nCorner Mounting LVT\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Semi-C Air Displacement", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Semi-C Air Displacement in the Available Type drop-down list to display the Air Displacement Unit window:\n\nThe Air Displacement Unit window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nIn the Front Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Clash Vol fields are pre-populated with the obstruction volumes associated with the Air Displacement Unit and the ducting.\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Size drop-down list, click Special.\nyou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Semi Circular Air Displacement Unit.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, you must enter the Front Direction.\nIn the Front Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol fields are pre-populated with the obstruction volumes associated with the Air Displacement Unit component and the ducting.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Air Displacement Unit window was opened.\nClick Fit to orientate the Air Displacement Unit to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Air Displacement Unit component and close the Air Displacement Unit Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Air Displacement Unit window.\nName(Ref)\nDuct Diameter\nBody Radius (A)\nBody Length (B)\nBody CL Height (D)\nArrive Extension\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nBody Radius (A)\nBody Radius (A)\nBody Length (B)\nBody Length (B)\nBody CL Height (D)\nBody CL Height (D)\nArrive Extension\nArrive Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nSemi Circular Air Displacement Unit\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nSemi-C Air Displacement\nAvailable Type\nAir Displacement Unit\nStandard Stock Sizes\nName(Ref)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nStock Size\nFront Direction\nNon Standard Stock Sizes (Special)\nPicture\nSemi Circular Air Displacement Unit\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nFront Direction\nFront Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Circ Air Displacement Unit", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Circ Air Displacement Unit in the Available Type drop-down list to display the Air Displacement Unit window:\n\nThe Air Displacement Unit window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nIn the Front Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Clash Vol Diameter field is pre-populated with the obstruction volumes associated with the Air Displacement Unit and the ducting.\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Size drop-down list, click Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Air Displacement Unit.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, you must enter the Front Direction.\nIn the Front Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe ClashVol Diameter field is pre-populated with the obstruction volume associated with the Circ Air Displacement Unit component and the ducting.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Air Displacement Unit window was opened.\nClick Fit to orientate the Air Displacement Unit to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Air Displacement Unit component and close the Air Displacement Unit Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Air Displacement Unit window.\nName(Ref)\nDuct Diameter\nBody Diameter (A)\nBody Length (B)\nArrive Extension\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nBody Diameter (A)\nBody Diameter (A)\nBody Length (B)\nBody Length (B)\nArrive Extension\nArrive Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nCircular Air Displacement Unit\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nCirc Air Displacement Unit\nAvailable Type\nAir Displacement Unit\nAir Displacement Unit\nStandard Stock Sizes\nName(Ref)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nFront Direction\nNon Standard Stock Sizes (Special)\nPicture\nCircular Air Displacement Unit\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nFront Direction\nFront Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Rect Air Displacement Unit", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Rect Air Displacement Unit in the Available Type drop-down list to display the Air Displacement Unit window:\n\nThe Air Displacement Unit window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nIn the Front Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Clash Vol fields are pre-populated with the obstruction volumes associated with the Air Displacement Unit and the ducting.\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Sizes drop-down list, click Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Air Displacement Unit.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, you must enter the Front Direction.\nIn the Front Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol fields are pre-populated with the obstruction volume associated with the Rect Air Displacement Unit component and the ducting.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Air Displacement Unit window was opened.\nClick Fit to orientate the Air Displacement Unit to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Air Displacement Unit component and close the Air Displacement Unit Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Air Displacement Unit window.\nName(Ref)\nDuct Diameter\nBody Width (A)\nBody Length (B)\nBody Height (C)\nBody CL Height (E)\nArrive Extension\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nBody Width (A)\nBody Width (A)\nBody Length (B)\nBody Length (B)\nBody Height (C)\nBody Height (C)\nBody CL Height (E)\nBody CL Height (E)\nArrive Extension\nArrive Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nRectangular Air Displacement Unit\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nRect Air Displacement Unit\nAvailable Type\nAir Displacement Unit\nAir Displacement Unit\nStandard Stock Sizes\nName(Ref)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nStock Size\nFront Direction\nNon Standard Stock Sizes (Special)\nPicture\nRectangular Air Displacement Unit\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nFront Direction\nFront Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Rect Disp Unit - Rect Conn", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Rect Disp Unit - Rect Conn in the Available Type drop-down list to display the Air Displacement Unit window:\n\nThe Air Displacement Unit window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nIn the Front Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).The Clash Vol fields are pre-populated with the obstruction volumes associated with the Air Displacement Unit and the ducting.\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Size drop-down list, click Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Air Displacement Unit with Rectangular Connection.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, you must enter the Front Direction.\nIn the Front Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol fields are pre-populated with the obstruction volumes associated with the Air Displacement Unit component and the ducting.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Air Displacement Unit window was opened.\nClick Fit to orientate the Air Displacement Unit to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Air Displacement Unit component and close the Air Displacement Unit Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Air Displacement Unit window.\nName(Ref)\nDuct width AA\nDuct depth AB\nBody Width (A)\nBody Length (B)\nBody Height (C)\nBody CL Height (E)\nArrive Extension\nName(Ref)\nName(Ref)\nDuct width AA\nDuct width AA\nDuct depth AB\nDuct depth AB\nBody Width (A)\nBody Width (A)\nBody Length (B)\nBody Length (B)\nBody Height (C)\nBody Height (C)\nBody CL Height (E)\nBody CL Height (E)\nArrive Extension\nArrive Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote: T\nhe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nRectangular Air Displacement Unit with Rectangular Connection\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nRect Disp Unit - Rect Conn\nAvailable Type\nAir Displacement Unit\nAir Displacement Unit\nStandard Stock Sizes\nName(Ref)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nStock Size\nFront Direction\nNon Standard Stock Sizes (Special)\nPicture\nRectangular Air Displacement Unit with Rectangular Connection\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nFront Direction\nFront Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Connection Box Circ-Circ", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Connection Box Circ-Circ in the Available Type drop-down list to display the Connection Box window:\n\nThe Connection Box window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nIn the Leave Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Size drop-down list, click Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Connection Box \u2018Circ Inlet - Circ Outlet\u2019.\nClick Transpose Width/Depth to exchange the Box Width dimension with the Box Depth dimension.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, you must enter the Leave Direction.\nIn the Leave Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Connection Box window was opened.\nClick Fit to orientate the Connection Box to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Connection Box component and close the Connection Box Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Connection Box window.\nName(Ref)\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018L\u2019\nBox Width\nBox Depth\nBox Length\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nName(Ref)\nName(Ref)\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018L\u2019\nDuct Diameter \u2018L\u2019\nBox Width\nBox Width\nBox Depth\nBox Depth\nBox Length\nBox Length\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nConnection Box \u2018Circ Inlet - Circ Outlet\u2019\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nConnection Box Circ-Circ\nAvailable Type\nConnection Box\nConnection Box\nStandard Stock Sizes\nName(Ref)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nDirection\nNon Standard Stock Sizes (Special)\nPicture\nConnection Box \u2018Circ Inlet - Circ Outlet\u2019\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nLeave Direction\nLeave Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Connection Box Circ-Rect", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Connection Box Circ- Rect in the Available Type drop-down list to display the Connection Box window:\n\nThe Connection Box window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nYou can select the location of the circular entry on the rectangular box, using the Circle Entry drop-down list select: On SIDE of box, On TOP of box, On FRONT of box.\nIn the Key Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Size drop-down list, click Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Connection Box with \u2018Circ Inlet - Rect Outlet\u2019.\nClick Transpose Width/Depth to exchange the Duct Width LA dimension with the Duct Depth LB dimension.\nClick Transpose Width/Depth to exchange the Box Width dimension with the Box Depth dimension.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, you must enter the Leave Direction.\nIn the Key Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Connection Box window was opened.\nClick Fit to orientate the Connection Box to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Connection Box component and close the Connection Box Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Connection Box window.\nName(Ref)\nYou can select the location of the circular entry on the rectangular box, using the Circle Entry drop-down list select: On SIDE of box, On TOP of box, On FRONT of box.\nDuct Diameter \u2018A\u2019\nDuct width LA\nDuct depth LB\nBox Width\nBox Depth\nBox Length\nA Offset\nB Offset\nArrive Extension\nLeave Extension\nName(Ref)\nName(Ref)\nYou can select the location of the circular entry on the rectangular box, using the Circle Entry drop-down list select: On SIDE of box, On TOP of box, On FRONT of box.\nYou can select the location of the circular entry on the rectangular box, using the Circle Entry drop-down list select: On SIDE of box, On TOP of box, On FRONT of box.\nDuct Diameter \u2018A\u2019\nDuct Diameter \u2018A\u2019\nDuct width LA\nDuct width LA\nDuct depth LB\nDuct depth LB\nBox Width\nBox Width\nBox Depth\nBox Depth\nBox Length\nBox Length\nA Offset\nA Offset\nB Offset\nB Offset\nArrive Extension\nArrive Extension\nLeave Extension\nLeave Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nConnection Box with \u2018Circ Inlet - Rect Outlet\u2019\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nConnection Box Circ- Rect\nAvailable Type\nConnection Box\nConnection Box\nStandard Stock Sizes\nName(Ref)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nStock Size\nCircle Entry\nDirection\nNon Standard Stock Sizes (Special)\nStock Size\nSpecial\nPicture\nConnection Box with \u2018Circ Inlet - Rect Outlet\u2019\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nTranspose Width/Depth\nCreate/Modify HVAC Component\nLeave Direction\nKey Direction\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Circ Diffuser - Circ Inlet", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Circ Diffuser - Circ Inlet in the Available Type drop-down list to display the Circ Diffuser - Circ Inlet window:\n\nThe Circ Diffuser - Circ Inlet window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nThe Clash Vol OUT field will be pre-populated with the obstruction volume associated with the Circ Diffuser - Circ Inlet and the ducting, but can be changed by you to the required joint.\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Size drop-down list, click Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Diffuser with Circular Inlet.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nThe Clash Vol OUT field will be pre-populated with the obstruction volume associated with the Circ Diffuser - Circ Inlet and the ducting, but can be changed by you to the required joint.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Circ Diffuser - Circ Inlet window was opened.\nClick Fit to orientate the Circ Diffuser - Circ Inlet to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Circ Diffuser - Circ Inlet component and close the Circ Diffuser - Circ Inlet Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Circ Diffuser - Circ Inlet window.\nName(Ref)\nDuct Diameter\nOutlet Diameter\nBody Length\nArrive Extension\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nOutlet Diameter\nOutlet Diameter\nBody Length\nBody Length\nArrive Extension\nArrive Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nCircular Diffuser with Circular Inlet\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nCirc Diffuser - Circ Inlet\nAvailable Type\nCirc Diffuser - Circ Inlet\nCirc Diffuser - Circ Inlet\nStandard Stock Sizes\nNote\n:\nHVAC Catalog\nHVAC Catalog\nStock Size\nClash Vol OUT\nNon Standard Stock Sizes (Special)\nStock Size\nSpecial\nPicture\nCircular Diffuser with Circular Inlet\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nClash Vol OUT\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nCirc Diffuser - Circ Inlet\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Rect Diffuser - Circ Inlet", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Rect Diffuser - Circ Inlet in the Available Type drop-down list to display the Rect Diffuser - Circ Inlet window:\n\nThe Rect Diffuser - Circ Inlet window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nIn the Width Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe ClashVol OUT field will be pre-populated with the obstruction volume associated with the Circ Diffuser - Circ Inlet and the ducting, but can be changed by you to the required joint.\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Size drop-down list, click Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Diffuser with Circular Inlet.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, you must enter the Width Direction.\nIn the Width Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe ClashVol OUT field will be pre-populated with the obstruction volume associated with the Circ Diffuser - Circ Inlet and the ducting, but can be changed by you to the required joint.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Rect Diffuser - Circ Inlet window was opened.\nClick Fit to orientate the Rect Diffuser - Circ Inlet to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Rect Diffuser - Circ Inlet component and close the Rect Diffuser - Circ Inlet Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Rect Diffuser - Circ Inlet window.\nName(Ref)\nDuct Diameter\nOutlet Width\nOutlet Depth\nBody Length\nArrive Extension\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nOutlet Width\nOutlet Width\nOutlet Depth\nOutlet Depth\nBody Length\nBody Length\nArrive Extension\nArrive Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nRectangular Diffuser with Circular Inlet\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nRect Diffuser - Circ Inlet\nAvailable Type\nRect Diffuser - Circ Inlet\nRect Diffuser - Circ Inlet\nStandard Stock Sizes\nName(Ref)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nWidth Direction\nClashVol OUT\nNon Standard Stock Sizes (Special)\nStock Size\nSpecial\nPicture\nRectangular Diffuser with Circular Inlet\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nWidth Direction\nWidth Direction\nClashVol OUT\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\n\nHVAC Window\nCancel\n"}
{"Headers": "Rect Grille - Rect Inlet", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Rect Grille - Rect Inlet in the Available Type drop-down list to display the Rect Grille - Rect Inlet window:\n\nThe Rect Grille - Rect Inlet window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nIn the Width Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe Clash Vol OUT field will be pre-populated with the obstruction volume associated with the Circ Diffuser - Circ Inlet and the ducting, but can be changed by you to the required joint.\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Size drop-down list, click Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Rectangular Grille with Rectangular Inlet\u2019.\nClick Transpose Width/Depth to exchange Duct Width AA dimension with Duct Depth AB dimension.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nAfter selecting the type of joint to use for the Arrive Joint, you must enter the Width Direction.\nIn the Width Direction specify the axis that should be used. Valid axes are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (Negative Up).\nThe ClashVol OUT field will be pre-populated with the obstruction volume associated with the Circ Diffuser - Circ Inlet and the ducting, but can be changed by you to the required joint.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Rect Grille - Circ Inlet window was opened.\nClick Fit to orientate the Rect Grille - Circ Inlet to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Rect Grille - Circ Inlet component and close the Rect Grille - Circ Inlet Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Rect Grille - Circ Inlet window.\nName(Ref)\nDuct width AA\nDuct depth AB\nEnd Flange Width\nFlange Thickness\nInsertion Length\nArrive Extension\nName(Ref)\nName(Ref)\nDuct width AA\nDuct width AA\nDuct depth AB\nDuct depth AB\nEnd Flange Width\nEnd Flange Width\nFlange Thickness\nFlange Thickness\nInsertion Length\nInsertion Length\nArrive Extension\nArrive Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nRectangular Grille with Rectangular Inlet\u2019\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nRect Grille - Rect Inlet\nAvailable Type\nRect Grille - Rect Inlet\nRect Grille - Rect Inlet\nStandard Stock Sizes\nName(Ref)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nWidth Direction\nClash Vol OUT\nNon Standard Stock Sizes (Special)\nStock Size\nSpecial\nPicture\nRectangular Grille with Rectangular Inlet\u2019\nNote\n:\nHVAC Catalog\nTranspose Width/Depth\nCreate/Modify HVAC Component\nWidth Direction\nWidth Direction\nClashVol OUT\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nHVAC Window\nCancel\n"}
{"Headers": "Circular Air Intake Hood", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Circular Air Intake Hood in the Available Type drop-down list to display the Air Intake Hood window:\n\nThe Air Intake Hood window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Size drop-down list, click Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Air Intake Hood.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Air Intake Hood window was opened.\nClick Fit to orientate the Air Intake Hood to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Air Intake Hood component and close the Air Intake Hood Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Air Intake Hood window.\nName(Ref)\nDuct Diameter\nOverall Diameter\nOverall Height\nCowl Height\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nOverall Diameter\nOverall Diameter\nOverall Height\nOverall Height\nCowl Height\nCowl Height\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nCircular Air Intake Hood\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nCircular Air Intake Hood\nAvailable Type\nAir Intake Hood\nAir Intake Hood\nStandard Stock Sizes\nName(Ref)\nNote\n:\nHVAC Catalog\nHVAC Catalog\nStock Size\nNon Standard Stock Sizes (Special)\nStock Size\nSpecial\nPicture\nCircular Air Intake Hood\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nHVAC Window\nCancel\n"}
{"Headers": "Circular Air Extract Hood", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Extra Inline Equipment in the Categories drop-down list and then Circular Air Extract Hood in the Available Type drop-down list to display the Air Extract Hood window:\n\nThe Air Extract Hood window default is a standard stock size, but can be changed by you using one of the following methods:\nStandard Stock Sizes\nIn the Name(Ref) field, input the name of the HVAC component.\nTo choose from the standard stock sizes available from the HVAC Catalog, in the Stock Size drop-down list, click the required size for the HVAC component.\nNon Standard Stock Sizes (Special)\nIf you chose not to use a standard stock piece of HVAC, from the Stock Size drop-down list, click Special.\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for Circular Air Extract Hood.\nSpecify a type of joint to use for the Arrive Joint. Refer to Create/Modify HVAC Component for a detailed description.\nIn the Position list, select Connect or Unchanged:\nClick Defaults to reset all the fields back to when the Air Extract Hood window was opened.\nClick Fit to orientate the Air Extract Hood to automatically match the outlet (p-leave) of the previous piece of HVAC to the inlet (p-arrive) of the next piece.\nClick OK to create the Air Extract Hood component and close the Air Extract Hood Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the Air Extract Hood window.\nName(Ref)\nDuct Diameter\nTop Diameter\nOverall Diameter\nCowl Height (H)\nMid Section Height\nArrive Taper Height\nArrive Extension\nName(Ref)\nName(Ref)\nDuct Diameter\nDuct Diameter\nTop Diameter\nTop Diameter\nOverall Diameter\nOverall Diameter\nCowl Height (H)\nCowl Height (H)\nMid Section Height\nMid Section Height\nArrive Taper Height\nArrive Taper Height\nArrive Extension\nArrive Extension\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Connect (default when Create is selected) - connects the piece of HVAC to the previous one.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nClick Unchanged (default when Modify is selected) - positions the component at the co-ordinates 0.00.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. Mid Section Height and Arrive Taper Height can be changed by you.\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog.\nNote:\nUnchanged is usually used, when Modify is selected, it does not connect the component but positions it at 0.00, in effect in a floating position.\n\n\n\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nCircular Air Extract Hood\nHVAC Catalog\nCreate/Modify HVAC Component\nHVAC Window\nHVAC Component\nHVAC Window\nExtra Inline Equipment\nCategories\nCircular Air Extract Hood\nAvailable Type\nAir Extract Hood\nAir Extract Hood\nStandard Stock Sizes\nName(Ref\nNote\n:\nHVAC Catalog\nHVAC Catalog\nNon Standard Stock Sizes (Special)\nStock Size\nSpecial\nPicture\nCircular Air Extract Hood\nNote\n:\nHVAC Catalog\nCreate/Modify HVAC Component\nPosition\nConnect\nUnchanged\nConnect\nCreate\nUnchanged\nModify\nNote\n:\nUnchanged\nModify\nDefaults\nFit\nOK\nHVAC Window\n.\nCancel\n"}
{"Headers": "Equipment Nozzles", "Content": "HVAC Equipment nozzles act as an interface point between pieces of equipment and the connecting HVAC ducting, you can create, then position and orientate the HVAC Nozzle.\nAll of the HVAC Equipment Nozzle windows are dual purpose windows allowing you to either Create a new HVAC Equipment Nozzle element (by default) or Modify the attributes of an existing HVAC Equipment Nozzle.\nNote:\nBefore a HVAC Equipment Nozzle can be created, a piece of equipment must be created first, refer to Equipment User Guide.\n\n\n\nNote\n:\nEquipment User Guide"}
{"Headers": "Rectangular Nozzle", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Equipment Nozzles in the Categories drop-down list and then Rectangular Nozzle in the Available Type drop-down list to display the HVAC Equipment Nozzle window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for HVAC Equipment Nozzles.\nModify Orientation\nYou can modify the orientation of the existing nozzle, refer to Orientation.\nModify Position\nYou can modify the position of the existing nozzle, refer to Position.\nClick Defaults to reset all the fields back to when the HVAC Equipment Nozzle window was opened.\nClick Apply to create the HVAC Equipment Nozzle component and close the HVAC Equipment Nozzle Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the HVAC Equipment Nozzle window.\nName(Ref)\nYou can select a Duct/Nozzle Shape, using Duct / Nozzle Shape drop-down list\nDuct Width\nDuct Depth\nOverall Length\nEnd Flange Width\nEnd Flange Length\nFlange Thickness\nName(Ref)\nName(Ref)\nYou can select a Duct/Nozzle Shape, using Duct / Nozzle Shape drop-down list\nYou can select a Duct/Nozzle Shape, using Duct / Nozzle Shape drop-down list\nDuct Width\nDuct Width\nDuct Depth\nDuct Depth\nOverall Length\nOverall Length\nEnd Flange Width\nEnd Flange Width\nEnd Flange Length\nEnd Flange Length\nFlange Thickness\nFlange Thickness\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive Extension default is auto but can be changed by you to a required dimension.\n\n\n\nHVAC Window\nHVAC Equipment Nozzles\nHVAC Catalog\nOrientation\nPosition\nHVAC Window\nHVAC Component\nHVAC Window\n.\nEquipment Nozzles\nCategories\nRectangular Nozzle\nAvailable Type\nHVAC Equipment Nozzle\nPicture\nHVAC Equipment Nozzles\nNote\n:\nHVAC Catalog\nModify Orientation\nOrientation\nModify Position\nPosition\nDefaults\nApply\nHVAC Window\nCancel\n"}
{"Headers": "Circular Nozzle", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Equipment Nozzles in the Categories drop-down list and then Circular Nozzle in the Available Type drop-down list to display the HVAC Equipment Nozzle window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for HVAC Equipment Nozzles.\nModify Orientation\nYou can modify the orientation of the existing nozzle, refer to Orientation.\nModify Position\nYou can modify the position of the existing nozzle, refer to Position.\nClick Defaults to reset all the fields back to when the HVAC Equipment Nozzle window was opened.\nClick Apply to create the HVAC Equipment Nozzle component and close the HVAC Equipment Nozzle Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the HVAC Equipment Nozzle window.\nName(Ref)\nYou can select a Duct/Nozzle Shape, using Duct / Nozzle Shape drop-down list\nDuct Width\nDuct Depth\nOverall Length\nEnd Flange Width\nEnd Flange Length\nFlange Thickness\nName(Ref)\nName(Ref)\nYou can select a Duct/Nozzle Shape, using Duct / Nozzle Shape drop-down list\nYou can select a Duct/Nozzle Shape, using Duct / Nozzle Shape drop-down list\nDuct Width\nDuct Width\nDuct Depth\nDuct Depth\nOverall Length\nOverall Length\nEnd Flange Width\nEnd Flange Width\nEnd Flange Length\nEnd Flange Length\nFlange Thickness\nFlange Thickness\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive Extension default is auto but can be changed by you to a required dimension.\n\n\n\nHVAC Window\nHVAC Equipment Nozzles\nHVAC Catalog\nOrientation\nPosition\nHVAC Window\nHVAC Component\nHVAC Window\nEquipment Nozzles\nCategories\nCircular Nozzle\nAvailable Type\nHVAC Equipment Nozzle\nPicture\nHVAC Equipment Nozzles\nNote\n:\nHVAC Catalog\nModify Orientation\nOrientation\nModify Position\nPosition\nDefaults\nApply\nHVAC Window\nCancel\n"}
{"Headers": "Flat Oval Nozzle", "Content": "The task of creating an HVAC Component is initiated from the HVAC Window.\nSelect Equipment Nozzles in the Categories drop-down list and then Flat Oval Nozzle in the Available Type drop-down list to display the HVAC Equipment Nozzle window:\n\nYou are required to input the following dimensions:\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing for HVAC Equipment Nozzles.\nModify Orientation\nYou can modify the orientation of the existing nozzle, refer to Orientation.\nModify Position\nYou can modify the position of the existing nozzle, refer to Position.\nClick Defaults to reset all the fields back to when the HVAC Equipment Nozzle window was opened.\nClick Apply to create the HVAC Equipment Nozzle component and close the HVAC Equipment Nozzle Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the HVAC Equipment Nozzle window.\nName(Ref)\nYou can select a Duct/Nozzle Shape, using Duct / Nozzle Shape drop-down list\nDuct Width\nDuct Depth\nOverall Length\nEnd Flange Width\nEnd Flange Length\nFlange Thickness\nName(Ref)\nName(Ref)\nYou can select a Duct/Nozzle Shape, using Duct / Nozzle Shape drop-down list\nYou can select a Duct/Nozzle Shape, using Duct / Nozzle Shape drop-down list\nDuct Width\nDuct Width\nDuct Depth\nDuct Depth\nOverall Length\nOverall Length\nEnd Flange Width\nEnd Flange Width\nEnd Flange Length\nEnd Flange Length\nFlange Thickness\nFlange Thickness\nNote:\nThe fields will be pre-populated with default dimensions. These dimensions are governed by the details defined in the HVAC Catalog. The Arrive Extension default is auto but can be changed by you to a required dimension.\n\n\n\nHVAC Window\nHVAC Equipment Nozzles\nHVAC Catalog\nOrientation\nPosition\nHVAC Window\nHVAC Component\nHVAC Window\nEquipment Nozzles\nCategories\nFlat Oval Nozzle\nAvailable Type\nHVAC Equipment Nozzle\nPicture\nHVAC Equipment Nozzles\nNote\n:\nHVAC Catalog\nModify Orientation\nOrientation\nModify Position\nPosition\nDefaults\nApply\nHVAC Window\nCancel\n"}
{"Headers": "Modify Existing Nozzle", "Content": "To modify an existing HVAC Equipment Nozzle element first select an existing HVAC Equipment Nozzle element in the Model Explorer.\nSelect Equipment Nozzles in the Categories drop-down list and then MODIFY Existing Nozzle in the Available Type drop-down list to display the HVAC Equipment Nozzle window:\n\nThe HVAC Equipment Nozzle window will be populated with attributes of the currently selected element and the drop-down list in the top left of the window now has Modify as the default.\nTo visualize how the dimensions equate to the actual piece of HVAC, click Picture to display a detailed drawing.\nYou can now type in new attribute dimensions for the HVAC Equipment Nozzle element then click OK to commit the changes.\nModify Orientation\nYou can modify the orientation of the existing nozzle, refer to Orientation.\nModify Position\nYou can modify the position of the existing nozzle, refer to Position.\nClick Defaults to reset all the fields back to when the HVAC Equipment Nozzle window was opened.\nClick Apply to create the HVAC Equipment Nozzle component and close the HVAC Equipment Nozzle Window. You will be returned to the HVAC Window.\nClick Cancel to discard all the field changes and close the HVAC Equipment Nozzle window.\n\n\n\nOrientation\nPosition\nHVAC Window\nEquipment Nozzles\nCategories\nEquipment Nozzle\nHVAC Equipment Nozzle\nPicture\nOK\nModify Orientation\nOrientation\nModify Position\nPosition\nDefaults\nApply\nHVAC Window\nCancel\n"}
{"Headers": "User Defined Fittings", "Content": "Although it is recommended that the standard components supplied in the HVAC Catalog are used. There are occasions when non-standard HVAC components or user defined fittings are required. Before you can select a user defined fitting, the system administrator must first create the user defined catalog and specifications. Refer to the system administrator or System Administrator\u2019s Guide.\nAll HVAC Component windows are dual purpose windows allowing you to either Create a new HVAC Component element (by default) or Modify the attributes of an existing HVAC Component element.\nThe task of creating a User Defined Fitting is initiated from the HVAC Window.\nSelect User Defined Fittings in the Categories drop-down list to display the User Defined HVAC Fittings window:\n\nThe User Defined HVAC Fittings window is a dual purpose window allowing you to either Create a new User Defined HVAC Fitting (by default) or Modify a User Defined HVAC Fitting.\nYou can select from the drop-down list, the fittings available in the HVAC Fittings Catalogue.\n\nFor the purposes of this user guide, the Specification Data including HVAC Fittings Catalogue only contains the supplied catalogs provided by AVEVA. Catalogs are populated by the System Administrator.\n\nSelect an item from the choice available in the lower window, the selection is placed in the current selection window and the list of available choices moves down to the next level dependent upon what element is chosen. Continue to select from the available choices in the lower window until the fitting is complete.\nTo only select the default item for each level from the lower window, click to select the Default check box.\nTo automatically select an item when there is only one available at any level, click to select the Auto check box.\nFor further information on Joints and Connect drop-down list, refer to HVAC Window.\nNote:\nIf both Default and Auto check boxes are selected, the default item for each level and (if all levels have a default set) an overall default fitting will be selected.\u2018\n\n\n\nHVAC Catalog\nHVAC Window\nHVAC Window\nHVAC Catalog\nSystem Administrator\u2019s Guide\nCreate\nt\nModify\nHVAC\nHVAC Window\nUser Defined Fittings\nCategories\nUser Defined HVAC Fittings\nUser Defined HVAC Fittings\nCreate\nModify\nDefault\nAuto\nNote\n:\nDefault\nAuto\nHVAC Window"}
{"Headers": "User Defined Fittings Plotfile", "Content": "To visualize how the dimensions equate to the actual piece of HVAC click Plotfile to display a detailed drawing to refer to all the available HVAC Components as an annotated drawings, refer to HVAC Catalog.\n\nClick Properties to view the user defined fitting parameters displayed in the Modify Properties window:\n\nIf the default parameters are not suitable, you can then amend the available parameters as required and click Reset to change the parameters.\nClick OK to close the Modify Properties window.\nClick Cancel to close the Modify Properties window.\nFrom the drop-down list, select Connect or Unchanged:\nClick Default to clear all the dimensions currently in the window and set them to the dimensions when the window was first opened.\nClick Reset to change the properties of the HVAC Component and close the Modify Properties window. You will be returned to the HVAC Window.\n\n\n\nHVAC Catalog\nHVAC Window\nPlotfile\nHVAC Catalog\nProperties\nModify Properties\nReset\nOK\nCancel\nModify Properties\nConnect\nUnchanged\nDefault\nReset\nModify Properties\nHVAC Window"}
{"Headers": "Modify User Defined HVAC Fittings", "Content": "The attributes of an existing user defined fitting can be modified. The attributes that can be modified is dependent upon which item has been selected.\nFirst you must select the element, piece of HVAC or equipment in the Model Explorer, then select User Defined Fittings in the Categories drop-down list to display the User Defined HVAC Fittings window.\nThe Create/Modify window for the selected item is displayed, with Modify as the default. You can now modify the attributes as required and then click Apply to commit the changes.\n\n\n\nModel Explorer,\nUser Defined Fittings\nCategories\nCreate/Modify\nApply"}
{"Headers": "Assemblies", "Content": "Assemblies are a series of components and branches in a predefined configuration which can be copied into the Design many times. Assemblies are created using the HVAC Assemblies utility, refer to HVAC Assembly, these assemblies can then be selected from the Categories drop-down list by you.\nThe task of copying an assembly is initiated from the HVAC Window.\nSelect Assemblies in the Categories drop-down list to display the HVAC Assembly Creation window is displayed:\n\nIf required, select the Display Name/Description check box, to display the available assemblies by description. Otherwise the assemblies are displayed by Name.\nCreate connected to picked element\nYou can copy an HVAC assembly from the HVAC Catalog and connect it to an identified element.\n\nClick Create connected to picked element\nyou are prompted to Identify Component in the 3D graphical view. The HVAC Assembly is connected to the identified element.\nCreate at position in implied tube\nAllows you to copy a HVAC Assembly from the HVAC Catalog and connect it to an identified point on the tube.\nClick Create at position in implied tube, you are prompted to Identify an Insertion Point in Tube in the 3D Graphical View.\nThe HVAC Assembly is connected to the identified point in the tube.\nCreate connected to current element\nAllows you to copy a HVAC Assembly from the HVAC Catalog and connect to the Current Element.\nYou must select in the Model Explorer where to connect the assembly.\nAfter clicking Create connected to current element, the assembly is added to the current element\n\nNote:\nThe selected element must be a HVAC branch or component\n\n\n\nHVAC Assembly\nHVAC Window\nHVAC Catalog\nHVAC Catalog\nHVAC Catalog\nHVAC Assembly\nHVAC Window\nAssemblies\nCategories\nHVAC Assembly Creation\nCreate connected to picked element\nHVAC Catalog\nCreate connected to picked element\nIdentify Component\nCreate at position in implied tube\nHVAC Catalog\nIdentify an Insertion Point in Tube\nCreate connected to current element\nHVAC Catalog\nNote\n:"}
{"Headers": "HVAC Catalog", "Content": "The section gives an introduction to the way the HVAC catalog is used in creating the design model and lists the principal features of some standard catalog components to which you may want to refer when creating the design model. (For further information of the way in which the catalog is built up and used, refer to the Catalogs and Specifications Reference.)\n\n\n\nCatalogs and Specifications Reference\nHVAC\nCatalogs and Specifications Reference\n."}
{"Headers": "Application Files", "Content": "For the HVAC Designer application, files are generally stored in the directory:\nThe control file 'xmaincontrol' can be edited within a text editor, such as WordPad, to change the defaults.\n\n\n"}
{"Headers": "Sample Catalog", "Content": "HVAC Designer provides a sample catalogue of HVAC fittings.\nThe catalogue is stored in the Master Project (MAS)\nDatabase /MASTER-HVACCATA\nThe key element names are:\nCATA /CADCHVACCATA\n- HVAC Designer Standard Catalogue\n SECT /RMELBOW-SECT\n- Section for Rectangular Mitred Elbow\n  CATE /RMELBOW-SECT\n- Category for Rectangular Mitred Elbow\n   PTSE /RMELBOW-SECT\n- Point set for Rectangular Mitred Elbow\n   GMSE /RMELBOW-SECT\n- Geometry for Rectangular Mitred Elbow\n   SCOM /RMELBOW\n- Rectangular Mitred Elbow Component\nSECT /CADCHVACCATA-INFO\n- Section for HVAC Datasets\n CATE / CADCHVACCATA-DTSE\n- Category for HVAC Datasets\n  DTSE /RMELBOW-DETAIL-DATA\n- Data set for Mitred Elbow\n   DATA /RMELBOW-DETAIL-DATA-PLOT\n- Data (Property DATA)\n- etc for each property\nSECT /CADCHVACCATA-DETTEXT\n- Section for HVAC Detail Text\n CATE / CADCHVACCATA-DETCATE\n- Category for HVAC Detail Text\n  SDTE /RMELBOW-DETAIL\n- Detail Text for Mitred Elbow\nSPWL /CADCHVACSPECS\nHVAC Designer Standard Specifications\n SPEC /CADCHVACSPEC\nHVAC Designer Standard Specification\n  SELE\nSelector based on TYPE\n   SELE\nSelector based on STYPE\n    SPCO\nSpec component\nCATA /CADCHVACCATA\n- HVAC Designer Standard Catalogue\n SECT /RMELBOW-SECT\n- Section for Rectangular Mitred Elbow\n  CATE /RMELBOW-SECT\n- Category for Rectangular Mitred Elbow\n   PTSE /RMELBOW-SECT\n- Point set for Rectangular Mitred Elbow\n   GMSE /RMELBOW-SECT\n- Geometry for Rectangular Mitred Elbow\n   SCOM /RMELBOW\n- Rectangular Mitred Elbow Component\n\nSECT /CADCHVACCATA-INFO\n- Section for HVAC Datasets\n CATE / CADCHVACCATA-DTSE\n- Category for HVAC Datasets\n  DTSE /RMELBOW-DETAIL-DATA\n- Data set for Mitred Elbow\n   DATA /RMELBOW-DETAIL-DATA-PLOT\n- Data (Property DATA)\n- etc for each property\n\nSECT /CADCHVACCATA-DETTEXT\n- Section for HVAC Detail Text\n CATE / CADCHVACCATA-DETCATE\n- Category for HVAC Detail Text\n  SDTE /RMELBOW-DETAIL\n- Detail Text for Mitred Elbow\n\nSPWL /CADCHVACSPECS\nHVAC Designer Standard Specifications\n SPEC /CADCHVACSPEC\nHVAC Designer Standard Specification\n  SELE\nSelector based on TYPE\n   SELE\nSelector based on STYPE\n    SPCO\nSpec component\n\nCATA /CADCHVACCATA\n- HVAC Designer Standard Catalogue\n SECT /RMELBOW-SECT\n- Section for Rectangular Mitred Elbow\n  CATE /RMELBOW-SECT\n- Category for Rectangular Mitred Elbow\n   PTSE /RMELBOW-SECT\n- Point set for Rectangular Mitred Elbow\n   GMSE /RMELBOW-SECT\n- Geometry for Rectangular Mitred Elbow\n   SCOM /RMELBOW\n- Rectangular Mitred Elbow Component\nSECT /CADCHVACCATA-INFO\n- Section for HVAC Datasets\n CATE / CADCHVACCATA-DTSE\n- Category for HVAC Datasets\n  DTSE /RMELBOW-DETAIL-DATA\n- Data set for Mitred Elbow\n   DATA /RMELBOW-DETAIL-DATA-PLOT\n- Data (Property DATA)\n- etc for each property\nSECT /CADCHVACCATA-DETTEXT\n- Section for HVAC Detail Text\n CATE / CADCHVACCATA-DETCATE\n- Category for HVAC Detail Text\n  SDTE /RMELBOW-DETAIL\n- Detail Text for Mitred Elbow\nSPWL /CADCHVACSPECS\nHVAC Designer Standard Specifications\n SPEC /CADCHVACSPEC\nHVAC Designer Standard Specification\n  SELE\nSelector based on TYPE\n   SELE\nSelector based on STYPE\n    SPCO\nSpec component\n\n\n"}
{"Headers": "User Defined Components", "Content": "The HVAC application has an extensive parametric catalogue of components but there will always be the need for Special User Defined HVAC Fittings. It is recommended that the standard elements are used whenever possible, however, the HVAC window has a Category for User Defined Fittings.\n\nFirst the HVAC Administrator has to create a User Defined catalogue and specifications to populate this window. A tutorial style exercise follows to describe this process.\n\n\n\nUser Defined Fittings"}
{"Headers": "Tutorial Style Exercise", "Content": "An exercise is carried out from start to finish, to create a new User defined HVAC fitting for use in MODEL, covering all relevant points to successfully complete this task.\n\n\n"}
{"Headers": "Pre Conditions", "Content": "It is assumed that the Administrator is already a competent Cats&Specs user, comfortable with creating and editing macros to create the necessary database elements.\nThe Catalogue and Specification work covered in this tutorial can be done in the MODEL or PARAGON module. Since the work is mainly command line and macro driven, it is recommended to use MODEL with Read/Write access to the catalogue. To do this the Administrator should work in a project with such access rights, and then update the final project using macros.\nIn ADMIN, set MODEL module to Read/Write catalogue:\nEDIT MODULE DESI MODE CATA RW\nIn ADMIN, also create a catalogue database separate from the AVEVA Solutions Limited database, in which to create the User Defined Cats&Specs\nIt is assumed that the Administrator is already a competent Cats&Specs user, comfortable with creating and editing macros to create the necessary database elements.\nIt is assumed that the Administrator is already a competent Cats&Specs user, comfortable with creating and editing macros to create the necessary database elements.\nThe Catalogue and Specification work covered in this tutorial can be done in the MODEL or PARAGON module. Since the work is mainly command line and macro driven, it is recommended to use MODEL with Read/Write access to the catalogue. To do this the Administrator should work in a project with such access rights, and then update the final project using macros.\nThe Catalogue and Specification work covered in this tutorial can be done in the MODEL or PARAGON module. Since the work is mainly command line and macro driven, it is recommended to use MODEL with Read/Write access to the catalogue. To do this the Administrator should work in a project with such access rights, and then update the final project using macros.\nIn ADMIN, set MODEL module to Read/Write catalogue:\nIn ADMIN, set MODEL module to Read/Write catalogue:\nEDIT MODULE DESI MODE CATA RW\nEDIT MODULE DESI MODE CATA RW\nIn ADMIN, also create a catalogue database separate from the AVEVA Solutions Limited database, in which to create the User Defined Cats&Specs\nIn ADMIN, also create a catalogue database separate from the AVEVA Solutions Limited database, in which to create the User Defined Cats&Specs\n\n\n"}
{"Headers": "Requirements", "Content": "Example:\n\nIdentify the new components that are required:\nIdentify the new components that are required:\nIdentify the new components that are required:\nAbove is an example of 6 Threeway pieces that are not be covered by the Standard AVEVA Solutions Limited sample HVAC catalogue.\nTo make these pieces available as User Defined HVAC Fittings, follow this tutorial exercise:\nAbove is an example of 6 Threeway pieces that are not be covered by the Standard AVEVA Solutions Limited sample HVAC catalogue.\nAbove is an example of 6 Threeway pieces that are not be covered by the Standard AVEVA Solutions Limited sample HVAC catalogue.\nTo make these pieces available as User Defined HVAC Fittings, follow this tutorial exercise:\nTo make these pieces available as User Defined HVAC Fittings, follow this tutorial exercise:\n\n\n"}
{"Headers": "Create Top Level Elements in the New Database", "Content": "In the new catalogue database that has been created and added to the MDB, some top level elements are created to store the user defined HVAC catalogue.\nNEW CATA /My-udHVACcata setstar\nNEW SECT *-DETTEXT\nNEW CATE *-DETCATE\nNEW SPWL /My-udHVACspecs\nNEW SPEC /My-udHVACspec\nNotice in the above that the SPWL purpose is set to HVAC and the SPEC purpose is set to FITT. These settings are important because in MODEL this specification will then be listed on the HVAC User Defined Fittings form. Element type will be the first selector text on the same form.\n\n\n"}
{"Headers": "Identify an Existing Similar Component", "Content": "The most efficient way for the Administrator to create a new component is to copy an existing similar component and modify it.\nConsidering the six components in the example, copy /RSTHRE which is the standard component definition for a Rectangular Square Threeway\n\n\n"}
{"Headers": "Macros to Copy an Existing Component", "Content": "Write some simple macros to copy the existing component.\nExamples:\ncopyMac1\ncopyMac2\nmyUDCata\n-- Macro to make My catalogue from copy of existing similar standard\ncopyMac3\nmyUDCataDtse\n-- Macro to make My datasets from copy of existing similar standard\n\n\n\n/My-udHVACcata\ntail\nnew sect $1-SECT copy $2-SECT rename $2 $1\n$.\n$d2=\n/My-ud\ncata-DETCATE\ntail\nnew sdte $1 copy $2-DETAIL\nrtext |$2|\n$.\n$m/c:/MY-Macros/copyMac1 /My-Y-Type-3-Way1 /RSTHRE\n$m/c:/MY-Macros/copyMac2 /My-Y-Type-3-Way1-Detail /RSTHRE\n$m/c:/MY-Macros/copyMac1 /My-Y-Type-3-Way2 /RSTHRE\n$m/c:/MY-Macros/copyMac2 /My-Y-Type-3-Way2-Detail /RSTHRE\n$m/c:/MY-Macros/copyMac1 /My-Y-Type-3-Way3 /RSTHRE\n$m/c:/MY-Macros/copyMac2 /My-Y-Type-3-Way3-Detail /RSTHRE\n$m/c:/MY-Macros/copyMac1 /My-Angled-Type-3-Way1 /RSTHRE\n$m/c:/MY-Macros/copyMac2 /My-Angled-Type-3-Way1-Detail /RSTHRE\n$m/c:/MY-Macros/copyMac1 /My-Angled-Type-3-Way2 /RSTHRE\n$m/c:/MY-Macros/copyMac2 /My-Angled-Type-3-Way2-Detail /RSTHRE\n$m/c:/MY-Macros/copyMac1 /My-Angled-Type-3-Way3 /RSTHRE\n$m/c:/MY-Macros/copyMac2 /My-Angled-Type-3-Way3-Detail /RSTHRE\n$1-GMSE\nnew DTSE $1-DTSE copy /RSTHRE -DETAIL-DATA rename /RSTHRE $1\nNEX SCOM\nDTREF $1-DTSE\n$m/c:/MY-Macros/copyMac3 /My-Y-Type-3-Way1 /RSTHRE\n$m/c:/MY-Macros/copyMac3 /My-Y-Type-3-Way2 /RSTHRE\n$m/c:/MY-Macros/copyMac3 /My-Y-Type-3-Way3 /RSTHRE\n$m/c:/MY-Macros/copyMac3 /My-Angled-Type-3-Way1 /RSTHRE\n$m/c:/MY-Macros/copyMac3 /My-Angled-Type-3-Way2 /RSTHRE\n$m/c:/MY-Macros/copyMac3 /My-Angled-Type-3-Way3 /RSTHRE"}
{"Headers": "Run the Catalogue Macros", "Content": "In MODEL or PARAGON.\n$m//c:/MY-Macros/myUDCata\n$m//c:/MY-Macros/myUDCataDtse\nThese macros will create the database elements for the 6 example components.\nAll elements will be named and organized in a consistent manner.\nIt is advised that all elements, including primitives and ppoint elements, are named.\nThe macros will output some catalogue errors but there is no need to be concerned about these, this is simply because the model Design Parameters are not set at this stage.\nCatalogue error for component SCOM /My-Y-Type-3-Way1, catalogue primitive PTMIX /My-Y-Type-3-Way1-P6 - Design Parameter number ( 2 ) out of range.\n\n\n\n$m//c:/MY-Macros/myUDCata\n$m//c:/MY-Macros/myUDCataDtse"}
{"Headers": "Macros to Create Specification References", "Content": "Write a simple macro to create a Specification reference for the catalogue components created above.\nmyUDSpec\nReminder:\nSPWL %purp HVAC, SPEC %purp FITT to appear in the HVAC User Defined Fittings form.\nEach level of SELE with %tquestion and %tans causes a further level of questions in the HVAC UD Fittings form.\nBeware that a too lengthy %tans may prevent it from fitting into the form.\nSPWL %purp HVAC, SPEC %purp FITT to appear in the HVAC User Defined Fittings form.\nSPWL %purp HVAC, SPEC %purp FITT to appear in the HVAC User Defined Fittings form.\nEach level of SELE with %tquestion and %tans causes a further level of questions in the HVAC UD Fittings form.\nEach level of SELE with %tquestion and %tans causes a further level of questions in the HVAC UD Fittings form.\nBeware that a too lengthy %tans may prevent it from fitting into the form.\nBeware that a too lengthy %tans may prevent it from fitting into the form.\n\n\n"}
{"Headers": "Run the Specification Macro", "Content": "In MODEL or PARAGON.\n$m//c:/MY-Macros/myUDSpec\nThese macros will create the specification elements for the 6 example components. The TANS texts are the words that will appear on the Design form for User defined HVAC fittings.\n\n\n\n$m//c:/MY-Macros/myUDSpec"}
{"Headers": "Observe the User Defined HVAC Fittings form", "Content": "In HVAC Designer Application and from the HVAC window select the Category User Defined Fittings.\n\nThe Specification created is displayed, and the selectors available to select the six catalogue items. At the moment if you select any of these they will all be the same as the copied component /RSTHRE. So the next stage is to edit these components to be unique to match the initial requirements.\n\n\n\nUser Defined Fittings"}
{"Headers": "Make a Sketch", "Content": "For the example choose to make the 1st component of the 6 Threeway components illustrated previously. Make a pencil sketch of the component and mark it with all the variable Design Parameters to be used. It is recommended that the Administrator follows, as closely as possible to the list of Design Parameter/Properties listed in the HVAC User Guide. For example DESP[2] and DESP[3] are the arrive duct size .\n\n\n\n\nHVAC User Guide"}
{"Headers": "Some Conventions", "Content": "The component origin P0 is generally at the intersection of P1 and P2.\nP1 is normally the arrive point, P2 is the leave point and P3 is any third connection point.\nFor straight components P0 is normally at the arrive point, however for the likes of dampers, valves or grilles P0 will be wherever sensible, may be central or even at P2.\nThe axes are shown on the sketch above as used on HVAC components where Z is opposite to the PArrive, X and Y are the respective width and height of the arrive duct size.\nOn angled components PLeave is primarily towards X rather than -X.\nThe component origin P0 is generally at the intersection of P1 and P2.\nThe component origin P0 is generally at the intersection of P1 and P2.\nP1 is normally the arrive point, P2 is the leave point and P3 is any third connection point.\nP1 is normally the arrive point, P2 is the leave point and P3 is any third connection point.\nFor straight components P0 is normally at the arrive point, however for the likes of dampers, valves or grilles P0 will be wherever sensible, may be central or even at P2.\nFor straight components P0 is normally at the arrive point, however for the likes of dampers, valves or grilles P0 will be wherever sensible, may be central or even at P2.\nThe axes are shown on the sketch above as used on HVAC components where Z is opposite to the PArrive, X and Y are the respective width and height of the arrive duct size.\nThe axes are shown on the sketch above as used on HVAC components where Z is opposite to the PArrive, X and Y are the respective width and height of the arrive duct size.\nOn angled components PLeave is primarily towards X rather than -X.\nOn angled components PLeave is primarily towards X rather than -X.\n\n\n"}
{"Headers": "Edit the Detail Text", "Content": "The detail text is in the DATASET created earlier (that means, /My-Y-Type-3-Way1-DTSE).\nThis is presently a direct copy of the copied Threeway so it needs to be modified accordingly, such as: Rtext 'Rectangular Special Threeway Y type1'\n\n\n\n/My-Y-Type-3-Way1-DTSE"}
{"Headers": "Edit the Properties", "Content": "Because the example was copied from a standard component then the full list of properties has been inherited. A full list is available in the HVAC Designer User Guide.\nIt is therefore necessary to decide which properties are required for input for the new component.\nThe properties are in the DATASET created earlier (that means, /My-Y-Type-3-Way1-DTSE).\nThe long list of data elements (Properties of the Design element) can be shortened by setting the LHIDE attribute to true. Therefore, for the example only the following DATA elements set to LHIDE false are needed:-\nAARR -\nA of the Arrive Duct size (DESP[2])\nBARR -\nB of the Arrive Duct size (DESP[3])\nALEA -\nA of the Leave Duct size (DESP[4])\nABRA -\nA of the Branch Duct size (DESP[41])\nATHR -\nArrive Throat (DESP[12])\nLTHR -\nLeave Throat (DESP[13])\nBRLE -\nBranch Length (DESP[7])\nAOFF -\nOffset A (DESP[10])\nBANG -\nAngle B (DESP[10])\nAARR -\nA of the Arrive Duct size (DESP[2])\nBARR -\nB of the Arrive Duct size (DESP[3])\nALEA -\nA of the Leave Duct size (DESP[4])\nABRA -\nA of the Branch Duct size (DESP[41])\nATHR -\nArrive Throat (DESP[12])\nLTHR -\nLeave Throat (DESP[13])\nBRLE -\nBranch Length (DESP[7])\nAOFF -\nOffset A (DESP[10])\nBANG -\nAngle B (DESP[10])\nThe easiest way to do this is to use the List utility to add all data elements to a list and action the command LHIDE true, then navigate to the ones required for input and manually modify LHIDE false.\nThese are the properties that will appear on the Create/Modify User Defined components form:\n\nModify the text, set defaults and reorder the data elements to improve the presentation. To give:\n\nA PLOT file property will be completed later using a DRAFT picture of a sample component created in MODEL, but first, the geometry has to be completed.\nAARR -\nA of the Arrive Duct size (DESP[2])\nBARR -\nB of the Arrive Duct size (DESP[3])\nALEA -\nA of the Leave Duct size (DESP[4])\nABRA -\nA of the Branch Duct size (DESP[41])\nATHR -\nArrive Throat (DESP[12])\nLTHR -\nLeave Throat (DESP[13])\nBRLE -\nBranch Length (DESP[7])\nAOFF -\nOffset A (DESP[10])\nBANG -\nAngle B (DESP[10])\n\n\n\n/My-Y-Type-3-Way1-DTSE"}
{"Headers": "Hidden Properties", "Content": "Although only the above properties are shown, some of the other properties may need to be set, such as TYPE, SUBT, SHAP, FACE\nThe FACE property is subtly different from the SHAP property; mainly because of Branch connectors that can be of circular shape but connected to a rectangular or circular or flat oval main.\n\n\n\nThe TYPE property Attributes\nType DATA\nDkey TYPE\nPtype unset\nPproperty ( ATTRIB WDESP[66 ] )\nDproperty ( HASH ( 'THRE' ) )\nPurpose DESP\nNumber 66\nDtitle Type\nPunits unset\nRuse 1\nLhide true\nThe STYP property (Specific Type) Attributes\nType DATA\nDkey STYP\nPtype unset\nPproperty ( ATTRIB WDESP[67 ] )\nDproperty ( HASH ( 'YTYP' ) )\nPurpose DESP\nNumber 67\nDtitle Type\nPunits unset\nRuse 1\nLhide true\nThe SHAP property (Shape RECT, CIRC or OVAL) Attributes\nType DATA\nDkey SHAP\nPtype unset\nPproperty ( ATTRIB WDESP[40 ] )\nDproperty ( HASH ( 'RECT' ) )\nPurpose DESP\nNumber 40\nDtitle Type\nPunits unset\nRuse 1\nLhide true\nThe FACE property (Shape RECT, CIRC or OVAL) Attributes\nType DATA\nDkey FACE\nPtype unset\nPproperty ( ATTRIB WDESP[30 ] )\nDproperty ( HASH ( 'RECT' ) )\nPurpose DESP\nNumber 30\nDtitle Type\nPunits unset\nRuse 1\nLhide true"}
{"Headers": "Properties for Initial Joint Settings", "Content": "It is suggested that for initial creation the User Defined HVAC Fittings are created with a default joint of RE; to do this, set the following DATA elements as:\n\n\n\n*-ARRJ\nPproperty ( ATTRIB WDESP[58 ] )\nDproperty ( HASH ( 'RE' ) )\n*-AVAL\nPproperty ( ATTRIB DESP[68 ] )\nDproperty 0\n*-LEAJ\nPproperty ( ATTRIB WDESP[59 ] )\nDproperty ( HASH ( 'RE' ) )\n*-LVAL\nPproperty ( ATTRIB DESP[69 ] )\nDproperty 0\n*-BJNT\nPproperty ( ATTRIB WDESP[60 ] )\nDproperty ( HASH ( 'RE' ) )\n*-BVAL\nPproperty ( ATTRIB DESP[70 ] )\nDproperty 0"}
{"Headers": "Property for Leave Tubing", "Content": "For the correct leave tubing to be used for User Defined HVAC Fittings, it is necessary to create a DATA element in your DATASET\nNote: ID /CADCHVACSPEC/RTUBEB is generally used for Straight components but ID /CADCHVACSPEC/RTUBEA generally for non-angular components such as bends and threeways.\n\n\n\nNote\n:\nID /CADCHVACSPEC/RTUBEB\nID /CADCHVACSPEC/RTUBEA"}
{"Headers": "Properties for HVAC Sketches", "Content": "There are some properties required for all HVAC components because the standard HVAC Sketches functionality expects them. These are:\nThese properties are strings of text that are evaluated to describe the duct component.\nFor the example these may be:\n\n\n\nDATA */rtext (Property RTEX)\nDATA */Ductsizes (Property DUCT)\nDATA */Detail (Property DETA)\nDATA */Joints (Property JOIN)\nDATA */Fixing (Property FIXI)"}
{"Headers": "Model Set Design Parameters", "Content": "The component is already in a state where it can be created in MODEL or PARAGON although the Geometric representation will be not correct.\nIf working in MODEL use the Create User Defined HVAC Fittings form to create an instance of the new component that means, select the element, set some property values, and apply the form.\nIf working in PARAGON create a macro to set the model Design Parameters, such as:\nmodel set des para 1 0\nRepeat for 100 parameters set to 0\nmodel set des para 2 900\nmodel set des para 3 700\nmodel set des para 4 600\nmodel set des para 5 700\nmodel set des para 41 500\nmodel set des para 42 700\nmodel set des para 7 150\nmodel set des para 10 200\nmodel set des para 12 150\nmodel set des para 13 150\nmodel set des para 63 90\n-- 21 to 29 for Joints\nmodel set des para 21 50\nmodel set des para 22 50\nmodel set des para 23 5\nmodel set des para 24 50\nmodel set des para 25 50\nmodel set des para 26 5\nmodel set des para 27 50\nmodel set des para 28 50\nmodel set des para 29 5\nDESP[21] to [29] are reserved for the Arrj, Leaj and Bjnt\nIn MODEL these could be set by command line using desp n21 50 desp n22 50 desp n23 5 . However\u2026\nFor Joints Settings in MODEL: When the element is created, modify the joints using SHOW !!HVCJOINTMOD\n\n\n"}
{"Headers": "Edit the Point Set", "Content": "The Point set *-PTSE was inherited from the copied component, but it is now easy to modify the PTAX, PTMI, PTCA elements to be positioned using the new parameters.\nIn MODEL at the newly created Threeway element, use GOTO PTREF to navigate to the PTSE element and view it in the Members list.\nAttributes of the Parrive point:\nReminders\nSome commands to aid visualization:\nP1, P2, P3 reserved for 3 connections arrive, leave and branch\nP6 is required on all items at PL of the item, perpendicular to PL. This is used to aid connection of components where the appware by default uses: CONN and X is P6 of PREV although core code can now use the logic based on the PWIDTH and PHEIGHT attributes.\nP61 62 etc series are used as key dimension points to aid drafting. These are usually at the corners of the arrive duct size, add as many as required.\nP1, P2, P3 reserved for 3 connections arrive, leave and branch\nP1, P2, P3 reserved for 3 connections arrive, leave and branch\nP6 is required on all items at PL of the item, perpendicular to PL. This is used to aid connection of components where the appware by default uses: CONN and X is P6 of PREV although core code can now use the logic based on the PWIDTH and PHEIGHT attributes.\nP6 is required on all items at PL of the item, perpendicular to PL. This is used to aid connection of components where the appware by default uses: CONN and X is P6 of PREV although core code can now use the logic based on the PWIDTH and PHEIGHT attributes.\nP61 62 etc series are used as key dimension points to aid drafting. These are usually at the corners of the arrive duct size, add as many as required.\nP61 62 etc series are used as key dimension points to aid drafting. These are usually at the corners of the arrive duct size, add as many as required.\nIn MODEL - repre pp on pp num on update\nIn MODEL - pin6 at P6 pin6 dir p6 or pin6 dir p6 at p6 .\nIn MODEL - repre pp on pp num on update\nIn MODEL - repre pp on pp num on update\nIn MODEL - pin6 at P6 pin6 dir p6 or pin6 dir p6 at p6 .\nIn MODEL - pin6 at P6 pin6 dir p6 or pin6 dir p6 at p6 .\n\n\n\nName /My-Y-Type-3-Way1-PA1\nType PTAX\nLock false\nOwner /My-Y-Type-3-Way1-PTSE\nDescription unset\nNumber 1\nPconnect RECT\nPbore ( ATTRIB DDESP[2 ] + ATTRIB DDESP[3 ] )\nPdistance ( ATTRIB DESP[12 ] + ATTRIB DESP[4 ] / 2 )\nPaxis -Z\nPskey unset\nPurpose unset\nPvifilter 0\nPzaxis Y\nPwidth ( ATTRIB DDESP[2 ] )\nPheight ( ATTRIB DDESP[3 ] )"}
{"Headers": "Edit the Geometry Set", "Content": "Again, the geometry set *-GMSE was inherited from the copied component, but it is now easy to modify the Primitive elements to be positioned using the new parameters.\nIn MODEL at the newly created Threeway element, use GOTO GMREF to navigate to the GMSE element and view it in the Members list.\nReminders\nName all elements using setstar* to aid recognition\nNormal representation lev 0 - 10\nNegatives representation lev 9 - 10\nFlanges representation lev 6 - 10\nInsulation representation lev 7 - 10\nRemember to check these before the item is finished. It is suggested to use reporter to check these and a macro to make sure they are all corrected.\nName all elements using setstar* to aid recognition\nName all elements using setstar* to aid recognition\nNormal representation lev 0 - 10\nNormal representation lev 0 - 10\nNegatives representation lev 9 - 10\nNegatives representation lev 9 - 10\nFlanges representation lev 6 - 10\nFlanges representation lev 6 - 10\nInsulation representation lev 7 - 10\nInsulation representation lev 7 - 10\nRemember to check these before the item is finished. It is suggested to use reporter to check these and a macro to make sure they are all corrected.\nRemember to check these before the item is finished. It is suggested to use reporter to check these and a macro to make sure they are all corrected.\n\n\n"}
{"Headers": "Create a PLOT", "Content": "When the component looks OK in MODEL, create an example element that can be used on a DRAFT drawing to make a Plotfile.\nCreate the drawing in a similar style to the standard Plotfiles, where the philosophy was to do a Plan and elevation and an Isometric view giving all the data as on the Properties input form. There is a standard HVAC representation rule available in the DRAFT database that can be used to do a detailed Level 9, holes ON drawing.\nThe Plotfile should be named the same as the CATREF.\nThe PLOT property attributes:\nPproperty is the name of the file.\nDproperty is the name of the directory within the %AVEVA_DESIGN_PLOTS% directory.\n\n\n\nType DATA\nDkey PLOT\nPtype LPLT\nPproperty ( ATTRIB FLNM OF CATR  )\nDproperty ( 'HVACADV' )\nPurpose PLOT\nDtitle Plotfile\nLhide false\n%AVEVA_DESIGN_PLOTS%"}
{"Headers": "Testing", "Content": "When the Geometry, Point Set, Data Set, Detail Text and PLOT are complete it is advisable to do some testing:\nLevel6, level4, level9, level7 - Make sure the Design element displays correctly, each time combined with holes on/off, insulation on/off\nTest that implied tube displays correctly when a following item is moved to create a gap.\nTest that the automatic fill with straights utility works as expected when the new component is used in the branch\nTest that the HVAC Spooling and Sketches functionalities work as expected and produce good data on the final sketch.\nLevel6, level4, level9, level7 - Make sure the Design element displays correctly, each time combined with holes on/off, insulation on/off\nLevel6, level4, level9, level7 - Make sure the Design element displays correctly, each time combined with holes on/off, insulation on/off\nTest that implied tube displays correctly when a following item is moved to create a gap.\nTest that implied tube displays correctly when a following item is moved to create a gap.\nTest that the automatic fill with straights utility works as expected when the new component is used in the branch\nTest that the automatic fill with straights utility works as expected when the new component is used in the branch\nTest that the HVAC Spooling and Sketches functionalities work as expected and produce good data on the final sketch.\nTest that the HVAC Spooling and Sketches functionalities work as expected and produce good data on the final sketch.\n\n\n"}
{"Headers": "Detail Specifications", "Content": "A Detail Specification is a table of rules to define duct ranges with different Joints, standard length, material thickness or stiffening.\n\nThis information for HVAC is currently not stored in the specification database but in system files. The default directory for this is %AVEVA_DESIGN_DFLTS%/hvacadvspecs, however, this can be changed by the Administrator in the control file, xmaincontrol, mentioned earlier.\nThe list of detail specifications available to you is defined in\n      \n         \n            \n               \n                  |DW142TABLE6\n                \n               \n                  | |DW142TABLE6|\n                \n            \n            \n               \n                  |DW142TABLE7\n                \n               \n                  | |DW142TABLE7|\n                \n            \n            \n               \n                  |MODELONLY\n                \n               \n                  | |MODELONLY|\n                \n            \n            \n               \n                  |TUTORIAL\n                \n               \n                  | |TUTORIAL|\n                \n            \n         \n      \n   \n|DW142TABLE6\n| |DW142TABLE6|\n|DW142TABLE7\n| |DW142TABLE7|\n|MODELONLY\n| |MODELONLY|\n|TUTORIAL\n| |TUTORIAL|\nThese lines refer to files that have been saved into the same directory named: example\nWhen defining these files Administrators must make sure that they have r/w access, whereas you will never have write access to these files.\n         \n            \n               \n                  |DW142TABLE6\n                \n               \n                  | |DW142TABLE6|\n                \n            \n            \n               \n                  |DW142TABLE7\n                \n               \n                  | |DW142TABLE7|\n                \n            \n            \n               \n                  |MODELONLY\n                \n               \n                  | |MODELONLY|\n                \n            \n            \n               \n                  |TUTORIAL\n                \n               \n                  | |TUTORIAL|\n                \n            \n         \n      \n\n\n"}
{"Headers": "Insulation Specifications", "Content": "Insulation is applied at Branch level by setting of the ISPEC attribute. There is currently one insulation specification, named /CADCHVACISPEC, available in the HVAC application. However, if a User Defined Insulation specification is required it will be necessary for the HVAC Administrator to create a similar specification in a CATA database:\nnew spec /MyISpec copy /CADCHVACISPEC rename /CADCHVACISPEC /MyISpec\nThe SPWL will have a PURP HVAC and the SPEC will have a PURP INSU\nThe SPEC will have the MATREF set to a material in the properties database that has a valid material density.\nThe database structure for the insulation is as follows:\nSPWL\nPurp HVAC\nSPEC\nPurp INSU\nQuestion TYPE\nMatref /MyInsulationMaterial\nSELE\nQUES TEMP\nTANS 'INSU'\nTDEF 'NONE'\nSELE\nDESC '1\"'\nANSW 24\nMAXA 26\nQUES PBOR\nTDEF 'NONE'\nSPCO /MyISpec/INSU25\nMAXA 10000\nCATREF /INSU25\nSELE\nDESC '1.1/4\"  - For when in imperial units\nANSW 29      -- for 30mm insulation\nMAXA 31\nQUES PBOR\nTDEF 'NONE'\nSPCO /MyISpec/INSU30\nMAXA 10000\nCATREF /INSU30\nEtc\u2026\nSPWL\nPurp HVAC\n\n\n\n\n\nSPEC\nPurp INSU\nQuestion TYPE\nMatref /MyInsulationMaterial\n\n\nSELE\nQUES TEMP\nTANS 'INSU'\nTDEF 'NONE'\n\n\n\n\nSELE\nDESC '1\"'\nANSW 24\nMAXA 26\nQUES PBOR\nTDEF 'NONE'\n\n\n\n\nSPCO /MyISpec/INSU25\nMAXA 10000\nCATREF /INSU25\n\n\n\nSELE\nDESC '1.1/4\"  - For when in imperial units\nANSW 29      -- for 30mm insulation\nMAXA 31\nQUES PBOR\nTDEF 'NONE'\n\n\n\n\nSPCO /MyISpec/INSU30\nMAXA 10000\nCATREF /INSU30\nEtc\u2026\nThe CATREF element also must exist and can be defined by the administrator:\nBy creating these Cats&Specs elements this means that:\nSPWL\nPurp HVAC\nSPEC\nPurp INSU\nQuestion TYPE\nMatref /MyInsulationMaterial\nSELE\nQUES TEMP\nTANS 'INSU'\nTDEF 'NONE'\nSELE\nDESC '1\"'\nANSW 24\nMAXA 26\nQUES PBOR\nTDEF 'NONE'\nSPCO /MyISpec/INSU25\nMAXA 10000\nCATREF /INSU25\nSELE\nDESC '1.1/4\"  - For when in imperial units\nANSW 29      -- for 30mm insulation\nMAXA 31\nQUES PBOR\nTDEF 'NONE'\nSPCO /MyISpec/INSU30\nMAXA 10000\nCATREF /INSU30\nEtc\u2026\nInsulation Spec and thicknesses will appear on the Create Branch form\nInsulation weight will be used in weight calculations\nInsulation can be shown graphically by using IPARAM[1] in the catalogue geometry. (Actually IPARAM[2] could also be used if required for 2 level insulation but the standard catalogue has not included this in its geometry).\nInsulation Spec and thicknesses will appear on the Create Branch form\nInsulation Spec and thicknesses will appear on the Create Branch form\nInsulation weight will be used in weight calculations\nInsulation weight will be used in weight calculations\nInsulation can be shown graphically by using IPARAM[1] in the catalogue geometry. (Actually IPARAM[2] could also be used if required for 2 level insulation but the standard catalogue has not included this in its geometry).\nInsulation can be shown graphically by using IPARAM[1] in the catalogue geometry. (Actually IPARAM[2] could also be used if required for 2 level insulation but the standard catalogue has not included this in its geometry).\n\n\n"}
{"Headers": "User Definable Joints Set", "Content": "Prior to VERSION 12.0 the joints available for use on the HVAC components were a fixed set of joints, such as FJ25, FJ30, RE ., all defined in the macro hvcjoints.pmlobj. The HVAC Administrator is now able to define joints for rectangular, circular and flat oval ductwork.\nThere are 6 new sections (SECT) in the HVAC catalogue database.\nThese sections hold dataset elements (DATASET) for each joint, and each dataset has 7 data elements, \u2026/DESC \u2026/CODE \u2026/ALPH \u2026/NUME \u2026/HVJA \u2026/HVJB \u2026/HVJC\nExample\n/CADCHVACCATA-Joints-RECT/FJ30\nDESC ' 30 x 30 x 4 Angle Flange Joint (FJ30) '\nFUNC 'FJ30'\n/CADCHVACCATA-Joints-RECT/FJ30/DESC\nDKEY DESC\nPTYP TEXT\nPPRO ( ' 30 x 30 x 4 Angle Flange Joint (FJ30) ' )\nDTIT 'Description'\n/CADCHVACCATA-Joints-RECT/FJ30/CODE\nDKEY CODE\nPTYP TEXT\nPPRO ( 'FJ30' )\nDTIT 'Code'\n/CADCHVACCATA-Joints-RECT/FJ30/ALPH\nDKEY ALPH\nPTYP TEXT\nPPRO ( 'FJ' )\nDTIT 'Alpha'\n/CADCHVACCATA-Joints-RECT/FJ30/NUME\nDKEY NUME\nPTYP TEXT\nPPRO ( '30' )\nDTIT 'Numeric'\n/CADCHVACCATA-Joints-RECT/FJ30/HVJA\nDKEY HVJA\nPTYP REAL\nPPRO ( 30 )\nDTIT 'A Dimension'\n/CADCHVACCATA-Joints-RECT/FJ30/HVJB\nDKEY HVJB\nPTYP REAL\nPPRO ( 30 )\nDTIT 'B Dimension'\n/CADCHVACCATA-Joints-RECT/FJ30/HVJC\nDKEY HVJC\nPTYP REAL\nPPRO ( 4 )\nDTIT 'C Dimension'\nThe data in these data elements define a joint and all its relevant information to be used and displayed in the Joints window.\n\nThe joints provided in the standard product now use this new mechanism so that HVAC Administrators can remove and create joints. The standard joints and codes available currently are:\n\n\n"}
{"Headers": "Joints for Components of any shape", "Content": "MALE or M\nSocket and spigot male connection\nFEMA or F\nSocket and spigot female connection\nFJ25\n25x25x3 (1\"x1\"x1/8\") equal angle section joint\nFJ303\n30x30x3 (11/4\"x11/4\"x1/8\") equal angle section joint\nFJ30\n30x30x4 (11/4\"x11/4\"x3/16\") equal angle section joint\nFJ40\n40x40x4 (11/2\"x11/2\"x3/16\") equal angle section joint\nFJ45\n45x45x4 (13/4\"x13/4\"x3/16\") equal angle section joint\nFJ50\n50x50x5 (2\"x2\"x3/16\") equal angle section joint\nFJ60\n60x60x6 (21/4\"x21/4\"x1/4\") equal angle section joint\nFJ608\n60x60x8 (21/4\"x21/4\"x5/16\") equal angle section joint\nFJ6550\n65x50x6 (21/2\"x2\"x1/4\") unequal angle section joint\nFJ65\n65x65x6 (21/2\"x21/2\"x1/4\") equal angle section joint\nFJ70\n70x70x7 (23/4\"x23/4\"x5/16\") equal angle section joint\nFJ7550\n75x50x6 (3\"x2\"x1/4\") unequal angle section joint\nFJ75\n75x75x7 (3\"x3\"x5/16\") equal angle section joint\nFJ8060\n80x60x6 (31/4\"x21/4\"x1/4\") unequal angle section joint\nFJ80\n80x80x8 (31/4\"x31/4\"x5/16\") equal angle section joint\nFJ8010\n80x80x10 (31/4\"x31/4\"x3/8\") equal angle section joint\nFJ90\n90x90x9 (31/2\"x31/2\"x7/16\") equal angle section joint\nFJ10065\n100x65x6 (4\"x21/2\"x3/8\") unequal angle section joint\nFJ10080\n100x80x8 (4\"x31/4\"x3/8\") unequal angle section joint\nFJ100\n100x100x8 (4\"x4\"x3/8\") equal angle section joint\nFB253\n25x3 (1\"x1/8\") flat bar joint\nFB254\n25x4 (1\"x5/32\") flat bar joint\nFB304\n30x4 (11/4\"x5/32\") flat bar joint\nFB305\n30x5 (11/4\"x3/16\") flat bar joint\nFB354\n35x4 (13/8\"x5/32\") flat bar joint\nFB405\n40x5 (11/2\"x3/16\") flat bar joint\nFB505\n50x5 (2\"x3/16\") flat bar joint\nFB606\n60x6 (21/4\"x1/4\") flat bar joint\nFB6010\n60x10 (21/4\"x3/8\") flat bar joint\nFB8010\n80x10 (31/4\"x3/8\") flat bar joint\nFB8012\n80x12 (31/4\"x1/2\") flat bar joint\nCH7638\n76x38 (3\"x11/2\") rectangular channel section joint\nCH10251\n102x51 (4\"x2\") rectangular channel section joint\nCH12763\n127x63 (5\"x21/2\") rectangular channel section joint\nCH15276\n152x76 (6\"x3\") rectangular channel section joint\nRE\nRaw edge\nSF25\nSelf flange 25mm (1\")\nSF40\nSelf flange 40mm (11/2\")\nSF50\nSelf flange 50mm (2\")\nWELD or W\nWelded joint for branch connector or attachment fixed to a duct\nMALE or M\nSocket and spigot male connection\nFEMA or F\nSocket and spigot female connection\nFJ25\n25x25x3 (1\"x1\"x1/8\") equal angle section joint\nFJ303\n30x30x3 (11/4\"x11/4\"x1/8\") equal angle section joint\nFJ30\n30x30x4 (11/4\"x11/4\"x3/16\") equal angle section joint\nFJ40\n40x40x4 (11/2\"x11/2\"x3/16\") equal angle section joint\nFJ45\n45x45x4 (13/4\"x13/4\"x3/16\") equal angle section joint\nFJ50\n50x50x5 (2\"x2\"x3/16\") equal angle section joint\nFJ60\n60x60x6 (21/4\"x21/4\"x1/4\") equal angle section joint\nFJ608\n60x60x8 (21/4\"x21/4\"x5/16\") equal angle section joint\nFJ6550\n65x50x6 (21/2\"x2\"x1/4\") unequal angle section joint\nFJ65\n65x65x6 (21/2\"x21/2\"x1/4\") equal angle section joint\nFJ70\n70x70x7 (23/4\"x23/4\"x5/16\") equal angle section joint\nFJ7550\n75x50x6 (3\"x2\"x1/4\") unequal angle section joint\nFJ75\n75x75x7 (3\"x3\"x5/16\") equal angle section joint\nFJ8060\n80x60x6 (31/4\"x21/4\"x1/4\") unequal angle section joint\nFJ80\n80x80x8 (31/4\"x31/4\"x5/16\") equal angle section joint\nFJ8010\n80x80x10 (31/4\"x31/4\"x3/8\") equal angle section joint\nFJ90\n90x90x9 (31/2\"x31/2\"x7/16\") equal angle section joint\nFJ10065\n100x65x6 (4\"x21/2\"x3/8\") unequal angle section joint\nFJ10080\n100x80x8 (4\"x31/4\"x3/8\") unequal angle section joint\nFJ100\n100x100x8 (4\"x4\"x3/8\") equal angle section joint\nFB253\n25x3 (1\"x1/8\") flat bar joint\nFB254\n25x4 (1\"x5/32\") flat bar joint\nFB304\n30x4 (11/4\"x5/32\") flat bar joint\nFB305\n30x5 (11/4\"x3/16\") flat bar joint\nFB354\n35x4 (13/8\"x5/32\") flat bar joint\nFB405\n40x5 (11/2\"x3/16\") flat bar joint\nFB505\n50x5 (2\"x3/16\") flat bar joint\nFB606\n60x6 (21/4\"x1/4\") flat bar joint\nFB6010\n60x10 (21/4\"x3/8\") flat bar joint\nFB8010\n80x10 (31/4\"x3/8\") flat bar joint\nFB8012\n80x12 (31/4\"x1/2\") flat bar joint\nCH7638\n76x38 (3\"x11/2\") rectangular channel section joint\nCH10251\n102x51 (4\"x2\") rectangular channel section joint\nCH12763\n127x63 (5\"x21/2\") rectangular channel section joint\nCH15276\n152x76 (6\"x3\") rectangular channel section joint\nRE\nRaw edge\nSF25\nSelf flange 25mm (1\")\nSF40\nSelf flange 40mm (11/2\")\nSF50\nSelf flange 50mm (2\")\nWELD or W\nWelded joint for branch connector or attachment fixed to a duct\n\nMALE or M\nSocket and spigot male connection\nFEMA or F\nSocket and spigot female connection\nFJ25\n25x25x3 (1\"x1\"x1/8\") equal angle section joint\nFJ303\n30x30x3 (11/4\"x11/4\"x1/8\") equal angle section joint\nFJ30\n30x30x4 (11/4\"x11/4\"x3/16\") equal angle section joint\nFJ40\n40x40x4 (11/2\"x11/2\"x3/16\") equal angle section joint\nFJ45\n45x45x4 (13/4\"x13/4\"x3/16\") equal angle section joint\nFJ50\n50x50x5 (2\"x2\"x3/16\") equal angle section joint\nFJ60\n60x60x6 (21/4\"x21/4\"x1/4\") equal angle section joint\nFJ608\n60x60x8 (21/4\"x21/4\"x5/16\") equal angle section joint\nFJ6550\n65x50x6 (21/2\"x2\"x1/4\") unequal angle section joint\nFJ65\n65x65x6 (21/2\"x21/2\"x1/4\") equal angle section joint\nFJ70\n70x70x7 (23/4\"x23/4\"x5/16\") equal angle section joint\nFJ7550\n75x50x6 (3\"x2\"x1/4\") unequal angle section joint\nFJ75\n75x75x7 (3\"x3\"x5/16\") equal angle section joint\nFJ8060\n80x60x6 (31/4\"x21/4\"x1/4\") unequal angle section joint\nFJ80\n80x80x8 (31/4\"x31/4\"x5/16\") equal angle section joint\nFJ8010\n80x80x10 (31/4\"x31/4\"x3/8\") equal angle section joint\nFJ90\n90x90x9 (31/2\"x31/2\"x7/16\") equal angle section joint\nFJ10065\n100x65x6 (4\"x21/2\"x3/8\") unequal angle section joint\nFJ10080\n100x80x8 (4\"x31/4\"x3/8\") unequal angle section joint\nFJ100\n100x100x8 (4\"x4\"x3/8\") equal angle section joint\nFB253\n25x3 (1\"x1/8\") flat bar joint\nFB254\n25x4 (1\"x5/32\") flat bar joint\nFB304\n30x4 (11/4\"x5/32\") flat bar joint\nFB305\n30x5 (11/4\"x3/16\") flat bar joint\nFB354\n35x4 (13/8\"x5/32\") flat bar joint\nFB405\n40x5 (11/2\"x3/16\") flat bar joint\nFB505\n50x5 (2\"x3/16\") flat bar joint\nFB606\n60x6 (21/4\"x1/4\") flat bar joint\nFB6010\n60x10 (21/4\"x3/8\") flat bar joint\nFB8010\n80x10 (31/4\"x3/8\") flat bar joint\nFB8012\n80x12 (31/4\"x1/2\") flat bar joint\nCH7638\n76x38 (3\"x11/2\") rectangular channel section joint\nCH10251\n102x51 (4\"x2\") rectangular channel section joint\nCH12763\n127x63 (5\"x21/2\") rectangular channel section joint\nCH15276\n152x76 (6\"x3\") rectangular channel section joint\nRE\nRaw edge\nSF25\nSelf flange 25mm (1\")\nSF40\nSelf flange 40mm (11/2\")\nSF50\nSelf flange 50mm (2\")\nWELD or W\nWelded joint for branch connector or attachment fixed to a duct\n\n\n"}
{"Headers": "Joints for Rectangular Components Only", "Content": "RE25\nRaw edge, longitudinal seam notched back 25 (1\")\nRE40\nRaw edge, longitudinal seam notched back 40 (11/2\")\nRE50\nRaw edge, longitudinal seam notched back 50 (2\")\nDM30\nDuctmate\u2122 30mm (11/8\") flange\nDM40\nDuctmate\u2122 40mm (11/2\") flange\nIDC\nIntegral duct connector\nIDF\nIntegral duct flange\nVM20\nVerromez\u2122 20mm (3/4\") flange\nVM30\nVerromez\u2122 30mm (11/8\") flange\nVM40\nVerromez\u2122 40mm (11/2\") flange\nFLAT\nFor spigot plates only\nRE25\nRaw edge, longitudinal seam notched back 25 (1\")\nRE40\nRaw edge, longitudinal seam notched back 40 (11/2\")\nRE50\nRaw edge, longitudinal seam notched back 50 (2\")\nDM30\nDuctmate\u2122 30mm (11/8\") flange\nDM40\nDuctmate\u2122 40mm (11/2\") flange\nIDC\nIntegral duct connector\nIDF\nIntegral duct flange\nVM20\nVerromez\u2122 20mm (3/4\") flange\nVM30\nVerromez\u2122 30mm (11/8\") flange\nVM40\nVerromez\u2122 40mm (11/2\") flange\nFLAT\nFor spigot plates only\nA PML object HVACJOINTS is the only place that controls the HVAC Joint storage location.\nmethod .hvcJoints()\n-- Set defaults for the object members\nif (!!cdHVACunits eq 'MM') then\n!this.rectangularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-RECT ')\n!this.circularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-CIRC ')\n!this.flatOvalJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-FOVA ')\notherwise:\n!this.rectangularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-RECT-Imp ')\n!this.circularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-CIRC-Imp ')\n!this.flatOvalJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-FOVA-Imp ')\nendif\nendmethod\n-- Set defaults for the object members\nif (!!cdHVACunits eq 'MM') then\n!this.rectangularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-RECT ')\n!this.circularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-CIRC ')\n!this.flatOvalJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-FOVA ')\notherwise:\n\n!this.rectangularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-RECT-Imp ')\n!this.circularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-CIRC-Imp ')\n!this.flatOvalJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-FOVA-Imp ')\nendif\nendmethod\n\n\nRE25\nRaw edge, longitudinal seam notched back 25 (1\")\nRE40\nRaw edge, longitudinal seam notched back 40 (11/2\")\nRE50\nRaw edge, longitudinal seam notched back 50 (2\")\nDM30\nDuctmate\u2122 30mm (11/8\") flange\nDM40\nDuctmate\u2122 40mm (11/2\") flange\nIDC\nIntegral duct connector\nIDF\nIntegral duct flange\nVM20\nVerromez\u2122 20mm (3/4\") flange\nVM30\nVerromez\u2122 30mm (11/8\") flange\nVM40\nVerromez\u2122 40mm (11/2\") flange\nFLAT\nFor spigot plates only\n-- Set defaults for the object members\nif (!!cdHVACunits eq 'MM') then\n!this.rectangularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-RECT ')\n!this.circularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-CIRC ')\n!this.flatOvalJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-FOVA ')\notherwise:\n!this.rectangularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-RECT-Imp ')\n!this.circularJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-CIRC-Imp ')\n!this.flatOvalJointsStorage\n= object DBREF('/CADCHVACCATA-Joints-FOVA-Imp ')\nendif\nendmethod\n\n\n"}
{"Headers": "Defaults", "Content": "All the standard components have default values that can be changed by you. For example a Taper piece may have a default length of 500mm when in metric and 20inches when in imperial. The defaults are the values that appear on the creation form as the initial value. The Administrator can change these to 600mm or 24inches by creating or editing data elements as follows:\nThe standard HVAC defaults are stored as\n\nTo make user defaults :\nnew cata /USERHVACDFLTS copy /CADCHVACDFLTS rename $ /CADCHVACDFLTS /USERHVACDFLTS\nThen modify the data values, for example:\nThere is then a file %AVEVA_DESIGN_DFLTS%/hvacadv/userhvacmdflts that sets /USERHVACMDFLTS as the default.\nTo force this to always be the default, the administrator can edit the file %PMLUI%/des/ hvacadv/init.\n\n\n"}
{"Headers": "Units", "Content": "The defaults used must correspond to the units being used or else the default value of 500 may be interpreted as 500inches rather than the intended mm.\nThere is a concept of application units; where, variable !!CDHVACUNITS is set to 'MM' or 'INCH' in the defaults file.\nYou can select different defaults from Settings > Ductwork Defaults\n\n\n"}
{"Headers": "Weights", "Content": "The database mechanism for weights is as follows:\nConsider a HVAC branch:\n\nFor HVAC components the weight is calculated and set as DESP[87] by a macro %PMLUI%/des/hvacadv/mweight when an element is created or modified.\n\n\n"}
{"Headers": "Auto Naming", "Content": "The HVAC Administrator may define 'auto naming' rules for HVAC elements and HVAC branches, however, it is expected that you would define the HVAC and branch names.\nWith regard to component names (branch members) you have a utility that allows the HVAC elements to be assigned an item number and named accordingly.\nThis utility is called from the HVAC tab, in the Tools group, click Itemise and applies the same rules as HVAC Spooling where works fitted items are given a subnumber, for example 3.1 is a branch connector which is fitted to the above item 3.\n\nAn item is defined as works fitted by the property WKSF true.\n\n\n\nHVAC\nTools\nItemise"}
{"Headers": "HVAC Spools", "Content": "HVAC Spools are generated in MODEL, and is basically a group of connected HVAC components designated to be fitted together in the workshop prior to site assembly.\nThe elements in the database are:\n\u2026HVAC\nBRAN\nComponents\nHSLIST\nHSPOOL\nHSPOOL etc\u2026\n\u2026HVAC\n\n\nBRAN\n\n\n\nComponents\n\nHSLIST\n\n\n\nHSPOOL\n\n\n\nHSPOOL etc\u2026\nThere is a core PML object that can be used to interrogate HVAC Spool.\n!x = object HVACSPOOLMANAGER()\nName\nResult\nDescription\nRemarks\nHVACSPOOLMANAGER()\nCreates an empty HVAC Spool Manager PML object\nGENERATEHVACSPOOLS(DBREF)DBREF - Any HVAC Element\nGenerates HSPOOLS and HSLIST which owns them in the database.\nWhen GENERATEHVACSPOOLS is called from a HVAC element which already owns a HSLIST, it verifies the spool as it is, if found OK, no modification is done. If any differences or discrepancies present, then regenerate the appropriate spool/spools. This method does not delete the spool already created, but maintains the reference numbers of all the valid spools, so that the drawings generated from those spools remain intact.\nDELETEHVACSPOOLS (DBREF)DBREF - Any HVAC Element\nDelete HSLIST and HSPOOLS owned by the HVAC element\nYou cannot delete any spool or the HSLIST by any means other than this method. For ex. \"Delete HSPOOL \"will not delete the spool.\nVERIFYHVACSPOOLS(DBREF)DBREF - Any HVAC Element\nArray\nIf an element or elements in the constituent spools do not satisfy any of the criteria for a valid spool, error messages are returned as a string array. Returns an unset array if all the criteria are satisfied.\nFormat: <ELEMENT NAME> : <ERROR MESSAGE>\nSample error message:\n'HSLIST 1 of HVAC /HTEST : has 1 more spool(s)\n'HSPOOL 13 of HSLIST 1 of HVAC /HTEST : Invalid Spool (Start/End Reference Modified)\nVERIFYSPOOL(DBREF) DBREF - a HSPOOL\nString\nIf fails to satisfy any criteria, returns the error message; otherwise returns the message \"Successful\"\n\"Format:<ELEMENT NAME> : <ERROR MESSAGE>\nSample error message:\nHSPOOL 13 of HSLIST 1 of HVAC /\nHTEST : Invalid Spool (Start/End Reference Modified)\nGETMTOELEMENTSFORSPOOL(DBREF HSPOOL Type\nArray\nReturns the elements included in this HVAC spool\nName\nResult\nDescription\nRemarks\nHVACSPOOLMANAGER()\n\nCreates an empty HVAC Spool Manager PML object\n\nGENERATEHVACSPOOLS(DBREF)DBREF - Any HVAC Element\n\nGenerates HSPOOLS and HSLIST which owns them in the database.\nWhen GENERATEHVACSPOOLS is called from a HVAC element which already owns a HSLIST, it verifies the spool as it is, if found OK, no modification is done. If any differences or discrepancies present, then regenerate the appropriate spool/spools. This method does not delete the spool already created, but maintains the reference numbers of all the valid spools, so that the drawings generated from those spools remain intact.\nDELETEHVACSPOOLS (DBREF)DBREF - Any HVAC Element\n\nDelete HSLIST and HSPOOLS owned by the HVAC element\nYou cannot delete any spool or the HSLIST by any means other than this method. For ex. \"Delete HSPOOL \"will not delete the spool.\nVERIFYHVACSPOOLS(DBREF)DBREF - Any HVAC Element\nArray\nIf an element or elements in the constituent spools do not satisfy any of the criteria for a valid spool, error messages are returned as a string array. Returns an unset array if all the criteria are satisfied.\nFormat: <ELEMENT NAME> : <ERROR MESSAGE>\nSample error message:\n'HSLIST 1 of HVAC /HTEST : has 1 more spool(s)\n'HSPOOL 13 of HSLIST 1 of HVAC /HTEST : Invalid Spool (Start/End Reference Modified)\nVERIFYSPOOL(DBREF) DBREF - a HSPOOL\nString\nIf fails to satisfy any criteria, returns the error message; otherwise returns the message \"Successful\"\n\"Format:<ELEMENT NAME> : <ERROR MESSAGE>\nSample error message:\nHSPOOL 13 of HSLIST 1 of HVAC /\nHTEST : Invalid Spool (Start/End Reference Modified)\nGETMTOELEMENTSFORSPOOL(DBREF HSPOOL Type\nArray\nReturns the elements included in this HVAC spool\n\n\n\u2026HVAC\nBRAN\nComponents\nHSLIST\nHSPOOL\nHSPOOL etc\u2026\nName\nResult\nDescription\nRemarks\nHVACSPOOLMANAGER()\nCreates an empty HVAC Spool Manager PML object\nGENERATEHVACSPOOLS(DBREF)DBREF - Any HVAC Element\nGenerates HSPOOLS and HSLIST which owns them in the database.\nWhen GENERATEHVACSPOOLS is called from a HVAC element which already owns a HSLIST, it verifies the spool as it is, if found OK, no modification is done. If any differences or discrepancies present, then regenerate the appropriate spool/spools. This method does not delete the spool already created, but maintains the reference numbers of all the valid spools, so that the drawings generated from those spools remain intact.\nDELETEHVACSPOOLS (DBREF)DBREF - Any HVAC Element\nDelete HSLIST and HSPOOLS owned by the HVAC element\nYou cannot delete any spool or the HSLIST by any means other than this method. For ex. \"Delete HSPOOL \"will not delete the spool.\nVERIFYHVACSPOOLS(DBREF)DBREF - Any HVAC Element\nArray\nIf an element or elements in the constituent spools do not satisfy any of the criteria for a valid spool, error messages are returned as a string array. Returns an unset array if all the criteria are satisfied.\nFormat: <ELEMENT NAME> : <ERROR MESSAGE>\nSample error message:\n'HSLIST 1 of HVAC /HTEST : has 1 more spool(s)\n'HSPOOL 13 of HSLIST 1 of HVAC /HTEST : Invalid Spool (Start/End Reference Modified)\nVERIFYSPOOL(DBREF) DBREF - a HSPOOL\nString\nIf fails to satisfy any criteria, returns the error message; otherwise returns the message \"Successful\"\n\"Format:<ELEMENT NAME> : <ERROR MESSAGE>\nSample error message:\nHSPOOL 13 of HSLIST 1 of HVAC /\nHTEST : Invalid Spool (Start/End Reference Modified)\nGETMTOELEMENTSFORSPOOL(DBREF HSPOOL Type\nArray\nReturns the elements included in this HVAC spool\n\n\n"}
{"Headers": "DRAW Sketches", "Content": "The HVAC user has functionality to create HVAC Sketches of Spools generated in MODEL, based on the Property WKSF (Works Fitted) True/False.\nThe HVAC Administrator must first set up the Templates and Backing Sheets to be used for the HVAC Sketches.\nThis is an example of the HVAC Sketch in DRAW:\n\nThe tables on the drawing will look something like this:\n\nThe data on these tables will come from the Design database.\n\n\n"}
{"Headers": "HVAC Sketch Object", "Content": "Attributes\nAttribute\nReturn Type\nDescription\nHVAC Spool\ndbref\nHVAC spool to create HVAC sketch from\nStorage Area\ndbref\nPosition in DRAFT hierarchy where sketch is to be created\nDrawing Template\ndbref\nDrawing template to be used to create HVAC sketch with\nDrawing Prefix\nstring\nDrawing name prefix\nSheet Prefix\nstring\nSheet name prefix\nLog Messages\narray\nMessages created when processing the HVAC sketch\nSketch successfully generated\nBoolean\nTrue if sketch is successfully created\nAttribute\nReturn Type\nDescription\nHVAC Spool\ndbref\nHVAC spool to create HVAC sketch from\nStorage Area\ndbref\nPosition in DRAFT hierarchy where sketch is to be created\nDrawing Template\ndbref\nDrawing template to be used to create HVAC sketch with\nDrawing Prefix\nstring\nDrawing name prefix\nSheet Prefix\nstring\nSheet name prefix\nLog Messages\narray\nMessages created when processing the HVAC sketch\nSketch successfully generated\nBoolean\nTrue if sketch is successfully created\nFunctions\nAttribute\nReturn Type\nDescription\nCreate HVAC sketch\nCreates HVAC sketch from held data\nAttribute\nReturn Type\nDescription\nCreate HVAC sketch\n\nCreates HVAC sketch from held data\n\nAttribute\nReturn Type\nDescription\nHVAC Spool\ndbref\nHVAC spool to create HVAC sketch from\nStorage Area\ndbref\nPosition in DRAFT hierarchy where sketch is to be created\nDrawing Template\ndbref\nDrawing template to be used to create HVAC sketch with\nDrawing Prefix\nstring\nDrawing name prefix\nSheet Prefix\nstring\nSheet name prefix\nLog Messages\narray\nMessages created when processing the HVAC sketch\nSketch successfully generated\nBoolean\nTrue if sketch is successfully created\nAttribute\nReturn Type\nDescription\nCreate HVAC sketch\nCreates HVAC sketch from held data\n\n\n"}
{"Headers": "Drawing Template", "Content": "This is a typical Template:\nEach HVAC Sketch drawing is based on a Template which is used as the basic definition of the HVAC Sketch.\nThe Template Drawing contains views and layers like any other DRAFT Template drawing.\nFor other Drawing information the Template Drawing references a 'Backing Sheet'\n\nThis is a typical Template:\nEach HVAC Sketch drawing is based on a Template which is used as the basic definition of the HVAC Sketch.\nThe Template Drawing contains views and layers like any other DRAFT Template drawing.\nFor other Drawing information the Template Drawing references a 'Backing Sheet'\n\nThis is a typical Template:\nEach HVAC Sketch drawing is based on a Template which is used as the basic definition of the HVAC Sketch.\nThe Template Drawing contains views and layers like any other DRAFT Template drawing.\nFor other Drawing information the Template Drawing references a 'Backing Sheet'\n\n\n"}
{"Headers": "Backing Sheet", "Content": "This is a typical backing sheet.\nThe new HVAC Sketch will reference the 'Backing Sheet', which is generally user-defined.\nThis is a standard backing sheet which will contain the drawing title block, with drawing data displayed via intelligent text for example, #DATE<FR DRWG> and #:UDA_Name .\nIn addition to the standard title block, the backing sheet is used to identify and locate 'TABLES' that are to be used on the HVAC Sketch.\n\nThis is a typical backing sheet.\nThe new HVAC Sketch will reference the 'Backing Sheet', which is generally user-defined.\nThis is a standard backing sheet which will contain the drawing title block, with drawing data displayed via intelligent text for example, #DATE<FR DRWG> and #:UDA_Name .\nIn addition to the standard title block, the backing sheet is used to identify and locate 'TABLES' that are to be used on the HVAC Sketch.\nThese tables are identified by:\nMaterial Take Off\n- function 'MTO'\nSpPurpose 'TABLE'\n/ SpPurpose 'CELLS\nAssembly\n- function 'ASSEMBLY\nSpPurpose 'TABLE'\n/ SpPurpose 'CELLS\nEnd Points\n- function 'ENDPOINT\nSpPurpose 'TABLE'\n/ SpPurpose 'CELLS\nMaterial Take Off\n- function 'MTO'\nSpPurpose 'TABLE'\n/ SpPurpose 'CELLS\nAssembly\n- function 'ASSEMBLY\nSpPurpose 'TABLE'\n/ SpPurpose 'CELLS\nEnd Points\n- function 'ENDPOINT\nSpPurpose 'TABLE'\n/ SpPurpose 'CELLS\n\nThis is a typical backing sheet.\nThe new HVAC Sketch will reference the 'Backing Sheet', which is generally user-defined.\nThis is a standard backing sheet which will contain the drawing title block, with drawing data displayed via intelligent text for example, #DATE<FR DRWG> and #:UDA_Name .\nIn addition to the standard title block, the backing sheet is used to identify and locate 'TABLES' that are to be used on the HVAC Sketch.\nMaterial Take Off\n- function 'MTO'\nSpPurpose 'TABLE'\n/ SpPurpose 'CELLS\nAssembly\n- function 'ASSEMBLY\nSpPurpose 'TABLE'\n/ SpPurpose 'CELLS\nEnd Points\n- function 'ENDPOINT\nSpPurpose 'TABLE'\n/ SpPurpose 'CELLS\n\n\n"}
{"Headers": "Tables", "Content": "In database terms the Table is a NOTE of the Backing Sheet (BACK); there are two notes required, one for the Table headings and one for the Table cells. Both notes are positioned at the same point.\nExample:\nBACK named /DRA/MAS/BACKS/HVACSketch/A4 SETST\nNOTE named */ExampleTable function 'ENDPOINT SpPurpose 'TABLE'\nNOTE named */ExampleCells function 'ENDPOINT SpPurpose 'CELLS'\nBACK named /DRA/MAS/BACKS/HVACSketch/A4 SETST\n\nNOTE named */ExampleTable function 'ENDPOINT SpPurpose 'TABLE'\n\nNOTE named */ExampleCells function 'ENDPOINT SpPurpose 'CELLS'\n\nThe above is an example of a table defined on a backing sheet. Although this table is visible in the view, it will in practice have its visibility flag (LVIS) set to false. The reason being that this table is used by copying onto the HVAC Sketch Drawing then the cells of the table are populated with data from the actual HVAC Spool. The figure below shows the table in situ on the final HVAC Sketch Drawing.\n\nBACK named /DRA/MAS/BACKS/HVACSketch/A4 SETST\nNOTE named */ExampleTable function 'ENDPOINT SpPurpose 'TABLE'\nNOTE named */ExampleCells function 'ENDPOINT SpPurpose 'CELLS'\n\n\n"}
{"Headers": "MTO Tables", "Content": "\n\nThe above figures show the MTO/Material Take-off tables first on the backing sheet and then on the finished drawing. On this type of table the 'cells' data need to be attributes of the HVAC Spool elements. for example, DTXR and DTXS attributes as used in the Description and Detail columns.\nYou can also user PROP attributes such as PROP RTEX, PROP DUCT, PROP DETA etc as shown below\n\n\n"}
{"Headers": "Assembly Tables and Endpoint Tables", "Content": "\n\nThe above figures show the Assembly and End Point tables first on the backing sheet and then on the finished drawing. On the assembly type of table the 'cells' data need to be attributes of the HVAC Spool elements. for example, PROP FIXI attribute as used in the Assembly data column. Any attributes or expressions can be used. The data in the End Point table is controlled by the System.\n\n\n"}
{"Headers": "Styles", "Content": "All Drawing Styles and Representations are inherited from the template drawing.\nThese include the View Representations, text colours and font size for Labels and Dimensions.\nExamples\n\n\n"}
{"Headers": "Common Object", "Content": "The system uses 1 object that does all the work to produce HVAC Sketch Drawings. This is so you do not have to use the form and graphics mode to produce a batch of drawings.\nThe common object is a Global instance of a hvacSketches object called !!hvacSketch.\nThe key members are:\n!!hvacSketch.createIn\n= DBREF (Must be an existing Registry - REGI element)\n!!hvacSketch.selectedTemplate\n= DBREF (Must be an existing Drawing - DRWG element)\n!!hvacSketch.hvacSpool\n= DBREF (Must be an existing HVAC Spool -HSPOOL element)\n!!hvacSketch.createIn\n= DBREF (Must be an existing Registry - REGI element)\n!!hvacSketch.selectedTemplate\n= DBREF (Must be an existing Drawing - DRWG element)\n!!hvacSketch.hvacSpool\n= DBREF (Must be an existing HVAC Spool -HSPOOL element)\nOptional members are:\n!!hvacSketch.logFile\n= FILE (The Form or User must write and read this file)\n!!hvacSketch..drawingPrefix\n= STRING (Default is 'DR')\n!!hvacSketch..sheetPrefix\n= STRING (Default is 'S')\n!!hvacSketch.logFile\n= FILE (The Form or User must write and read this file)\n!!hvacSketch..drawingPrefix\n= STRING (Default is 'DR')\n!!hvacSketch..sheetPrefix\n= STRING (Default is 'S')\nOther Members set and used in the background by the system:\n!!hvacSketch..type\n= STRING (Will always be 'drawing' or 'drtmpl')\n!!hvacSketch..drawing\n= DBREF (System records the new drawing)\n!!hvacSketch..sheet\n= DBREF (System records the new sheet)\n!!hvacSketch..backingSheet\n= DBREF (System records the backing sheet being used)\n!!hvacSketch..mtoHeadings\n= ARRAY (Array of strings read from backing sheet MTO table)\n!!hvacSketch..assemblyHeadings\n= ARRAY (Array of strings read from assembly table)\n!!hvacSketch..logData\n= ARRAY (Array of comment strings that user or form can read)\n!!hvacSketch..type\n= STRING (Will always be 'drawing' or 'drtmpl')\n!!hvacSketch..drawing\n= DBREF (System records the new drawing)\n!!hvacSketch..sheet\n= DBREF (System records the new sheet)\n!!hvacSketch..backingSheet\n= DBREF (System records the backing sheet being used)\n!!hvacSketch..mtoHeadings\n= ARRAY (Array of strings read from backing sheet MTO table)\n!!hvacSketch..assemblyHeadings\n= ARRAY (Array of strings read from assembly table)\n!!hvacSketch..logData\n= ARRAY (Array of comment strings that user or form can read)\nExample\n!!hvacSketch.createIn\n= object DBREF ('/MyRegistry')\n!!hvacSketch.selectedTemplate\n= object DBREF ('/MyTemplateDrawing')\n!!hvacSketch.hvacSpool\n= object DBREF ('/MyHvacSpool')\n!!hvacSketch.createIn\n= object DBREF ('/MyRegistry')\n!!hvacSketch.selectedTemplate\n= object DBREF ('/MyTemplateDrawing')\n!!hvacSketch.hvacSpool\n= object DBREF ('/MyHvacSpool')\n-- Then to create the sketch\n!!hvacSpool.apply()\n!!hvacSketch.createIn\n= DBREF (Must be an existing Registry - REGI element)\n!!hvacSketch.selectedTemplate\n= DBREF (Must be an existing Drawing - DRWG element)\n!!hvacSketch.hvacSpool\n= DBREF (Must be an existing HVAC Spool -HSPOOL element)\n!!hvacSketch.logFile\n= FILE (The Form or User must write and read this file)\n!!hvacSketch..drawingPrefix\n= STRING (Default is 'DR')\n!!hvacSketch..sheetPrefix\n= STRING (Default is 'S')\n!!hvacSketch..type\n= STRING (Will always be 'drawing' or 'drtmpl')\n!!hvacSketch..drawing\n= DBREF (System records the new drawing)\n!!hvacSketch..sheet\n= DBREF (System records the new sheet)\n!!hvacSketch..backingSheet\n= DBREF (System records the backing sheet being used)\n!!hvacSketch..mtoHeadings\n= ARRAY (Array of strings read from backing sheet MTO table)\n!!hvacSketch..assemblyHeadings\n= ARRAY (Array of strings read from assembly table)\n!!hvacSketch..logData\n= ARRAY (Array of comment strings that user or form can read)\n!!hvacSketch.createIn\n= object DBREF ('/MyRegistry')\n!!hvacSketch.selectedTemplate\n= object DBREF ('/MyTemplateDrawing')\n!!hvacSketch.hvacSpool\n= object DBREF ('/MyHvacSpool')\n\n\n"}
{"Headers": "Log Messages", "Content": "To write any message to the Log Data from any PML function use :\n!!hvacSketchesLog('Text of your choice')\nTo clear the messages from the Log Data use:\n!!hvacSketch.emptyLogData()\nTo write to the log File use:\n!!hvacSketch.logFile\n= object FILE('%AVEVA_DESIGN_USER%/hvacSketches.txt')\n!!hvacSketch.openLogFile()\n!!hvacSketch.writeLogFile()\n- This write the contents of .logData to the .logFile\n!!hvacSketch.closeLogFile()\n!!hvacSketch.logFile\n= object FILE('%AVEVA_DESIGN_USER%/hvacSketches.txt')\n!!hvacSketch.openLogFile()\n\n!!hvacSketch.writeLogFile()\n- This write the contents of .logData to the .logFile\n!!hvacSketch.closeLogFile()\n\n\n!!hvacSketch.logFile\n= object FILE('%AVEVA_DESIGN_USER%/hvacSketches.txt')\n!!hvacSketch.openLogFile()\n!!hvacSketch.writeLogFile()\n- This write the contents of .logData to the .logFile\n!!hvacSketch.closeLogFile()\n\n\n"}
{"Headers": "How to Define Tables", "Content": "-- Under a 'Backing Sheet'\nBACK /ExampleBack SETST\n\n\nExample continued\u2026.\n-- Create NOTEs\nNOTE */---Table SETST\nFUNC '---' ('---' can be MTO, ENDPOINT or ASSEMBLY)\nSpPurpose TABLE\nSet the XYpos and usual attributes for text size colour .\nCreate and name TEXP and STRA elements under NOTE. In the example below there are 4 TEXP elements and 7 STRA elements (Shown in Black)\nNOTE */---Cells SETST\nFUNC '---' ('---' can be MTO, ENDPOINT or ASSEMBLY)\nSpPurpose TABLE\nSet the XYpos and usual attributes for text size colour .\nCreate and name TEXP and STRA elements under NOTE. In the example below there are 3 TEXP elements and 1 STRA element (Shown in Red).\nNote:\nThe */ColumnLine1 direction of 'From Point' and 'To Point' defines the direction of the rows. The */ColumnLine1 'From Point' and 'To Point' distance defines the spacing of the rows.\n\n\n\nNote\n:"}
{"Headers": "Dimensions", "Content": "Dimensions are controlled from the Template Drawing:\nA VIEW will only be dimensioned if it has a LAYER with a PURPose of 'DIMA';\nIf it does, then the dimensions will go into that layer.\nThe style of the dimension will be cascaded from the owning layer.\n\n\n"}
{"Headers": "Tags", "Content": "View Tags are controlled from the Template Drawing:\nA VIEW will only be tagged if it has a LAYER with a PURPose of 'LABA';\nIf it does, then the tags will go into that layer.\nThe style of the tag will be cascaded from the owning layer, or taken from a symbol template in the case of component tags.\nA typical symbol may look like this:\n\nTo control how the components of the HVAC Spool are tagged:\nFirstly:\nA LAYER with PURPose of 'LABA'\nMust own a TASK element with a SpPurpose of 'TAGDEF'\nWhich owns 4 Task Parameter elements (TKPARA)\nWith FUNCtion equal to 'TEMPLATE', 'OFFSET', 'TPEN' and 'FPEN'\nAnd suitable TPVALUEs\nA LAYER with PURPose of 'LABA'\n\nMust own a TASK element with a SpPurpose of 'TAGDEF'\n\n\nWhich owns 4 Task Parameter elements (TKPARA)\n\n\nWith FUNCtion equal to 'TEMPLATE', 'OFFSET', 'TPEN' and 'FPEN'\n\n\nAnd suitable TPVALUEs\nExample\nLAYER\nTASK\nTKPARA\nFUNC 'TEMPLATE' TKPARA '/MySymbol'\nTKPARA\nFUNC 'OFFSET' TKPARA '10 10'\nTKPARA\nFUNC 'TPEN' TKPARA '1'\nTKPARA\nFUNC 'FPEN' TKPARA '11'\nLAYER\n\n\n\nTASK\n\n\n\nTKPARA\n\n\nFUNC 'TEMPLATE' TKPARA '/MySymbol'\n\n\nTKPARA\n\n\nFUNC 'OFFSET' TKPARA '10 10'\n\n\nTKPARA\n\n\nFUNC 'TPEN' TKPARA '1'\n\n\nTKPARA\n\n\nFUNC 'FPEN' TKPARA '11'\nWhen tagging views the system will create a Symbolic Label (SLAB) for each component, using the attributes of the above task parameters.\nSecondly:\nA LAYER with PURPose of 'LABA'\nMust own a TASK element with a SpPurpose of ''ARRLAB'\nWhich owns 6 Task Parameter elements (TKPARA)\nAnd specific FUNCtions and suitable TPVALUEs\nA LAYER with PURPose of 'LABA'\n\nMust own a TASK element with a SpPurpose of ''ARRLAB'\n\n\nWhich owns 6 Task Parameter elements (TKPARA)\n\n\nAnd specific FUNCtions and suitable TPVALUEs\nExample\nLAYER\nTASK\nTKPARA\nFUNC 'Top Side' TKPARA 'On'\nTKPARA\nFUNC 'Bottom Side' TKPARA 'Off'\nTKPARA\nFUNC 'Left Side' TKPARA 'On'\nTKPARA\nFUNC 'Right Side TKPARA 'On'\nTKPARA\nFUNC 'Margin' TKPARA '5'\nTKPARA\nFUNC 'Minimum Gap' TKPARA '1'\nLAYER\n\n\n\nTASK\n\n\n\nTKPARA\n\n\nFUNC 'Top Side' TKPARA 'On'\n\n\nTKPARA\n\n\nFUNC 'Bottom Side' TKPARA 'Off'\n\n\nTKPARA\n\n\nFUNC 'Left Side' TKPARA 'On'\n\n\nTKPARA\n\n\nFUNC 'Right Side TKPARA 'On'\n\n\nTKPARA\n\n\nFUNC 'Margin' TKPARA '5'\n\n\nTKPARA\n\n\nFUNC 'Minimum Gap' TKPARA '1'\nWhen tagging views the system will now arrange the Label around the view, using the attributes of the above task parameters.\nA LAYER with PURPose of 'LABA'\nMust own a TASK element with a SpPurpose of 'TAGDEF'\nWhich owns 4 Task Parameter elements (TKPARA)\nWith FUNCtion equal to 'TEMPLATE', 'OFFSET', 'TPEN' and 'FPEN'\nAnd suitable TPVALUEs\nLAYER\nTASK\nTKPARA\nFUNC 'TEMPLATE' TKPARA '/MySymbol'\nTKPARA\nFUNC 'OFFSET' TKPARA '10 10'\nTKPARA\nFUNC 'TPEN' TKPARA '1'\nTKPARA\nFUNC 'FPEN' TKPARA '11'\nA LAYER with PURPose of 'LABA'\nMust own a TASK element with a SpPurpose of ''ARRLAB'\nWhich owns 6 Task Parameter elements (TKPARA)\nAnd specific FUNCtions and suitable TPVALUEs\nLAYER\nTASK\nTKPARA\nFUNC 'Top Side' TKPARA 'On'\nTKPARA\nFUNC 'Bottom Side' TKPARA 'Off'\nTKPARA\nFUNC 'Left Side' TKPARA 'On'\nTKPARA\nFUNC 'Right Side TKPARA 'On'\nTKPARA\nFUNC 'Margin' TKPARA '5'\nTKPARA\nFUNC 'Minimum Gap' TKPARA '1'\n\n\n"}
{"Headers": "HVAC Sketches Created in Batch", "Content": "The common object !!hvaSketch can be used in a macro to be run as a batch job:\n!!hvacSketch.createIn\n= object DBREF ('/MyRegistry')\n!!hvacSketch.hvacSketchLogFile\n= object FILE'%AVEVA_DESIGN_WORK%\\myLog')\n!!hvacSketch.selectedTemplate\n= object DBREF ('/MyTemplateDrawing')\n!!hvacSketch.hvacSpool\n= object DBREF ('/MyHvacSpool')\n         \n            \n               \n                   -- Set the Global instance of the !!hvacSketch\n                \n            \n            \n               \n                  !!hvacSketch.createIn\n                \n               \n                  = object DBREF ('/MyRegistry')\n                \n            \n            \n               \n                  !!hvacSketch.hvacSketchLogFile\n                \n               \n                  = object FILE'%AVEVA_DESIGN_WORK%\\myLog')\n                \n            \n            \n               \n                  !!hvacSketch.selectedTemplate\n                \n               \n                  = object DBREF ('/MyTemplateDrawing')\n                \n            \n            \n               \n                  !!hvacSketch.hvacSpool\n                \n               \n                  = object DBREF ('/MyHvacSpool')\n                \n            \n         \n      \n\n\n"}
{"Headers": "DRAW General", "Content": "Creating DRAW drawings of HVAC, such as Plans or General arrangements, is like any other discipline in DRAW. Sample representation rules and styles exist in the AVEVA Solutions Limited sample projects, however, the Administrator may choose to create company or project standard representations for the same.\nIt is also recommended that the HVAC DRAW Administrator creates a set of symbols such as End of Duct symbols, Air Flow Arrows, Duct Sizes . Note that (#DESP[2]) intelligent text expressions can be used.\nThe DRAW Administrator should also create a template Drwg and sheet so the HVAC user has quick access to creating a new drawing using the 'Create from Default Template' toolbar.\n\n\n\n\n"}
{"Headers": "HVAC Preview", "Content": "Use the HVAC application to design and detail complex ducting networks within a full 3D environment by selecting components from the HVAC Catalog, and produce a clash-free design. Using standards and specifications or custom specifications, a conceptual layout can be created and analyzed rapidly, leaving the design details to a later post-approval stage.\nNote:\nAn environment variable must be set to enable this functionality; refer to your system administrator for further information.\n\n\n\n\n\n\nHVAC Catalog\nNote\n:\nPROJECT\nOptions\nNew HVAC Application (Evaluation Only)\nDiscipline\nHVAC\nEnable\nEnd-User License Agreement\nAccept.\nNEW HVAC - EVAL\nNEW HVAC - EVAL ONLY"}
{"Headers": "HVAC Powerwheel", "Content": "Operations in the HVAC discipline can be initiated using the PowerWheel, however the equivalent is also available from the HVAC UI\n-\n\nNote:\nAll of the out-of-the-box configurations for the PowerWheel can be customized; refer to the customizing Guide for further information.\n\n\n\nNote\n:"}
{"Headers": "Model HVAC", "Content": "Before modelling HVAC, the correct database elements should already be present in the Model Explorer, for example: a World, Site and Zone should exist.\nAll database elements are owned by other elements, therefore elements must be created in a strict order.\nThe following database elements are common to all the Design disciplines:\nBelow the ZONE level in the HVAC module, the HVAC-specific elements are:\n\nHVAC (HVAC) Element\nThe HVAC (HVAC) is a top level element in the Design database under which Branch (BRAN) element(s) are created.\nBRANCH (BRAN) Element\nThe Branch (BRAN) is a sequence of HVAC component elements running between two points:\nHVAC Component Element\nHVAC Component element(s) are owned by branch elements.These components dictate the shape and geometry of the HVAC design. HVAC components can run from the head to tail of the owing branch but can also be connected to other branches.\nWorld\nSite\nZone.\nWorld\nWorld\nSite\nSite\nZone.\nZone.\nHVAC (HVAC)\nBRANCH (BRAN)\nHVAC Component(s).\nHVAC (HVAC)\nHVAC (HVAC)\nBRANCH (BRAN)\nBRANCH (BRAN)\nHVAC Component(s).\nHVAC Component(s).\nBranch Head\nBranch Tail\nBranch Head\nBranch Head\nBranch Tail\nBranch Tail\n\n\n\nHVAC (HVAC) Element\nBRANCH (BRAN) Element\nHVAC Component Element"}
{"Headers": "HVAC Editor Window", "Content": "All of the tasks carried out that are associated with the creation or modification of HVAC are initiated from a central HVAC Editor and HVAC Components Editor windows which act as a task hub.\n\nNew HVAC Element\nThe HVAC administrative element and associated branch element are displayed in the model hierarchy. These elements must be created below an existing HVAC zone element. The HVAC element(s) are a starting point for branches and can own a number of branches with differing specifications with any number of ends and components.\n\nName\nThe name of new HVAC element is auto generated as per project rules; if required you can enter another name for the new HVAC element.\nPrimary System\nUse to select the primary system to which it belongs; the default is No System.\nStandard\nUse to select the required standard\nSpecifications\nUse to select the required specification. By default, this specification will be used but an alternative specification can be selected from the Branch pane of the HVAC Editor window for individual HVAC branches.\nThere are two specifications - rectangular and circular (SIMDUCT-CLASS-C and SIMDUCT-CLASS-F (both specifications are the same except F is the fireproof specification). You can change the dimensions but not the specification. However the straight components can be modified as this could occur on site.\nThere is also a custom specification where you can modify any dimension on the HVAC components to suit your requirements.\nNote:\nStandards, specifications and defaults are created in Catalog.\nInsulation\nUse to select the required insulation. This functionality can be applied to the current element and to a range of components. The default is None.\nCustom Settings\nThis functionality is enabled once the Custom specification is selected from the Specification drop-down list.\nUse to select the required custom settings for the new HVAC element.\nNote:\nThe greyed-out custom settings will display whichever custom settings are linked to the selected specification (if any are linked).\nSet working HVAC\nSets the currently selected HVAC, from the Model Explorer or 3D graphical view, as the working HVAC.\nCreate new branch\nUse to create a new HVAC branch in the model hierarchy below the currently selected HVAC element.\nBranch Connections\nThe branch connections pane is automatically displayed in the HVAC Editor window with the head and tail positioned but not connected.\nName\nThe name of new HVAC element is auto generated as per project rules; if required you can enter another name for the new HVAC element.\nPrimary System\nUse to select the primary system to which it belongs; the default is No System.\nStandard\nUse to select the required standard\nSpecifications\nUse to select the required specification. By default, this specification will be used but an alternative specification can be selected from the Branch pane of the HVAC Editor window for individual HVAC branches.\nThere are two specifications - rectangular and circular (SIMDUCT-CLASS-C and SIMDUCT-CLASS-F (both specifications are the same except F is the fireproof specification). You can change the dimensions but not the specification. However the straight components can be modified as this could occur on site.\nThere is also a custom specification where you can modify any dimension on the HVAC components to suit your requirements.\nInsulation\nUse to select the required insulation. This functionality can be applied to the current element and to a range of components. The default is None.\nCustom Settings\nThis functionality is enabled once the Custom specification is selected from the Specification drop-down list.\n\nUse to select the required custom settings for the new HVAC element.\n\nSet working HVAC\nSets the currently selected HVAC, from the Model Explorer or 3D graphical view, as the working HVAC.\n\nCreate new branch\nUse to create a new HVAC branch in the model hierarchy below the currently selected HVAC element.\nBranch Connections\nThe branch connections pane is automatically displayed in the HVAC Editor window with the head and tail positioned but not connected.\n\nBranch Element\nThe Branch pane of the HVAC Editor window is populated with the auto-generated name of the branch and the specification of the HVAC element.\n\nName\nThe name of new HVAC branch element is auto generated as per project rules and with reference to it\u2019s owning HVAC element in the hierarchy; if required you can enter another name for the new HVAC element.\nSpecification\nThe specification of the owning HVAC element is displayed.\nInsulation\nThe insulation selected for the owning HVAC element is displayed.\nCustom Settings\nIf the owning element\u2019s specification has been selected as Custom, this functionality will not be greyed out; the custom settings for it\u2019s owning element is displayed.\nClose this form and open Create HVAC Component form\nUse to close the HVAC Editor window and open the HVAC Components Editor window populated with HVAC components available for selection as defined by the selected specification.\nName\nThe name of new HVAC branch element is auto generated as per project rules and with reference to it\u2019s owning HVAC element in the hierarchy; if required you can enter another name for the new HVAC element.\nSpecification\nThe specification of the owning HVAC element is displayed.\nInsulation\nThe insulation selected for the owning HVAC element is displayed.\nCustom Settings\nIf the owning element\u2019s specification has been selected as Custom, this functionality will not be greyed out; the custom settings for it\u2019s owning element is displayed.\n\nClose this form and open Create HVAC Component form\nUse to close the HVAC Editor window and open the HVAC Components Editor window populated with HVAC components available for selection as defined by the selected specification.\nBranch Head/Branch Tail\nUse the functionality available from the Branch Head/Branch Tail pane of the HVAC Editor window to define the branch head/ branch tail settings (how the branch head/branch tail will be connected and positioned. By default the Branch Head tab is displayed).\n\nPosition (Unconnected) label\nThe branch head is positioned at the default co-ordinates 0,0,0 (origin) but is not connected to any HVAC components.\nNote:\n'Positioned (Unconnected)' can also represent any unconnected head/tail in free space (and the label text should change to reflect connection status).\nSwitch values between head and tail\nSwitches all the data entered in the HVAC Head and Tail pane of the HVAC Editor window between the HVAC branch head or the HVAC branch tail tabs.\nDisconnect head\nDisconnects the branch head from the element it is currently connected to.\nReconnect head\nReconnects the branch head that has moved position to an equipment element.\nPick Branch in laser data to set head to\nUse to connect the laser data to position the head or tail of the HVAC branch at a position derived from the point cloud data.\nNote:\nThis functionality is not available for this release.\nPick item to connect head to\nConnects the branch head to a selected element.\nConnect head to first branch member\nConnects the branch head to the first branch member.\nRectangular\nDefines the branch head shape as Rectangular. The width and depth fields are automatically populated with dimensions governed by the selected specification. If required these dimensions can be switched.\nCircular\nDefines the branch head shape as Circular. A diameter field is automatically populated with a dimension governed by the selected specification.\nFlat Oval\nDefines the branch head shape as Flat Oval. A width and depth fields are automatically populated with dimensions governed by the selected specification.\nNote:\nWhen later creating an HVAC component to connect to the branch head, the shape of the HVAC must match the shape specified.\nDirection\nSpecifies the direction that the HVAC will take from the branch head.\nValid dimensions for the head direction are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (negative Up).\nZ Axis (HZAXIS)\nUse to define the Z direction, typically the \u2018up\u2019 direction) of the HVAC branch head (this ensures any selected component\u2019s Z axis aligns as expected with the branch\u2019s head Z axis)\nReverse Direction\nUse to switch the direction of the HVAC branch head.\nPosition\nFormat\nSelect the position format - ENU, XYZ or Grid.\nWRT\nPositions the HVAC branch head WRT to the named design element, for example the World, Zone.\nDisplay positions as offset from nearest grid plane\nDisplays the picked position as an offset from the nearest grid.\nWRT current element\nPositions the HVAC branch WRT to the currently selected element.\nWRT CE owner\nPositions the HVAC branch WRT to the currently selected element\u2019s owner in the model hierarchy.\nWRT world\nPositions the HVAC branch WRT to the WORLD element in the Model hierarchy.\nWRT picked element\nPositions the HVAC branch WRT to the picked element in the 3D view.\nPicked position\nPositions the HVAC branch WRT to the picked position in the 3D view.\nOffset\nPositions the HVAC branch at an offset distance from a known position.coordinates for the known\nEnter the co-ordinates for the known position, in the format selected.\nClick Offset\nEnter the co-ordinates for the offset or pick the position in the 3D view.\nNudge\nNudges the new HVAC branch by a defined distance to the right or to the left in the 3D view.\nPosition (Unconnected) label\nThe branch head is positioned at the default co-ordinates 0,0,0 (origin) but is not connected to any HVAC components.\n\nSwitch values between head and tail\nSwitches all the data entered in the HVAC Head and Tail pane of the HVAC Editor window between the HVAC branch head or the HVAC branch tail tabs.\n\nDisconnect head\nDisconnects the branch head from the element it is currently connected to.\n\nReconnect head\nReconnects the branch head that has moved position to an equipment element.\n\nPick Branch in laser data to set head to\nUse to connect the laser data to position the head or tail of the HVAC branch at a position derived from the point cloud data.\n\nPick item to connect head to\nConnects the branch head to a selected element.\n\nConnect head to first branch member\nConnects the branch head to the first branch member.\n\nRectangular\nDefines the branch head shape as Rectangular. The width and depth fields are automatically populated with dimensions governed by the selected specification. If required these dimensions can be switched.\n\nCircular\nDefines the branch head shape as Circular. A diameter field is automatically populated with a dimension governed by the selected specification.\n\nFlat Oval\nDefines the branch head shape as Flat Oval. A width and depth fields are automatically populated with dimensions governed by the selected specification.\nDirection\nSpecifies the direction that the HVAC will take from the branch head.\nValid dimensions for the head direction are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (negative Up).\nZ Axis (HZAXIS)\nUse to define the Z direction, typically the \u2018up\u2019 direction) of the HVAC branch head (this ensures any selected component\u2019s Z axis aligns as expected with the branch\u2019s head Z axis)\nReverse Direction\nUse to switch the direction of the HVAC branch head.\nPosition\n\n\nFormat\nSelect the position format - ENU, XYZ or Grid.\n\n\nWRT\nPositions the HVAC branch head WRT to the named design element, for example the World, Zone.\n\nDisplay positions as offset from nearest grid plane\nDisplays the picked position as an offset from the nearest grid.\n\nWRT current element\nPositions the HVAC branch WRT to the currently selected element.\n\nWRT CE owner\nPositions the HVAC branch WRT to the currently selected element\u2019s owner in the model hierarchy.\n\nWRT world\nPositions the HVAC branch WRT to the WORLD element in the Model hierarchy.\n\nWRT picked element\nPositions the HVAC branch WRT to the picked element in the 3D view.\n\nPicked position\nPositions the HVAC branch WRT to the picked position in the 3D view.\n\nOffset\nPositions the HVAC branch at an offset distance from a known position.coordinates for the known\nEnter the co-ordinates for the known position, in the format selected.\n\nClick Offset\n\nEnter the co-ordinates for the offset or pick the position in the 3D view.\n\nNudge\nNudges the new HVAC branch by a defined distance to the right or to the left in the 3D view.\n\nHVAC Components\nHVAC Components are single pieces of HVAC used together to create a HVAC design. It is usual to build up the HVAC design by adding components sequentially, starting at the branch head, and positioning and orientating each component as you proceed. You can insert a component into an existing sequence by navigating to the item immediately before the required location and then creating the new component.\nThere are many different combinations of HVAC component that can be created; because of this the HVAC application uses a common layout for the windows that are presented. For the same reason this document only includes a detailed description of how to create one specific type of HVAC component. The information can be applied to the same processes that are used to create all other types of HVAC component.\nHVAC Components Editor Window\nAll HVAC Component windows are dual-purpose windows used to either Create a new HVAC Component element (by default) or Modify the attributes of an existing Component element.\nReferring to the HVAC Hierarchy section, an HVAC Component must reside below an existing HVAC Branch element.\nDepending upon which specification is selected; different HVAC components are displayed in the HVAC Components Editor window.\n\nBranch\nUse to return to the HVAC Editor window to modify HVAC or branch attributes. The name of the currently selected branch selected in the model explorer is also displayed.\nBack\nClick to return to the HVAC Editor window.\nCreate\nSpecification\nThe specification selected in the Branch pane of the HVAC Editor window is displayed in the specification field.\nNote:\nIf a specification is selected that does not match the HVAC specification, an out-of-spec message is displayed in the HVAC Components Editor window.\nInsulation\nThe insulation specification selected in the Branch pane of the HVAC Editor window is displayed in the Insulation field.\nCustom Settings\nIf the Custom Specification/ Custom Settings is selected in the Branch pane of the HVAC Editor window, the setting is displayed in the Custom Settings field.\nBranch\nUse to return to the HVAC Editor window to modify HVAC or branch attributes. The name of the currently selected branch selected in the model explorer is also displayed.\nBack\nClick to return to the HVAC Editor window.\nCreate\n\nSpecification\nThe specification selected in the Branch pane of the HVAC Editor window is displayed in the specification field.\nInsulation\nThe insulation specification selected in the Branch pane of the HVAC Editor window is displayed in the Insulation field.\nCustom Settings\nIf the Custom Specification/ Custom Settings is selected in the Branch pane of the HVAC Editor window, the setting is displayed in the Custom Settings field.\nSelect the required HVAC component from the pictorial representation of the available components for selection governed by the specification.\n\nFrom the Modify pane of the HVAC Component Editor window, the specification can be changed if required. The HVAC component is displayed in the Model Explorer and the description of the selected component is also displayed in the HVAC Component Editor window.\nPosition\nPosition through branch head\nAligns the selected HVAC component through the branch head.\nPosition through previous element\nAligns the selected HVAC component through the previous HVAC component of the HVAC branch.\nPosition through next element\nAligns the selected HVAC component through the next HVAC component of the HVAC branch.\nPosition through branch tail\nAligns the selected HVAC component through the branch tail.\nConnect to previous component\nConnects the selected HVAC component to the previous one.\nDistance - Clear to use Clearance\nDisplays the actual clearance. To change the clearance input a new value into the text flied then press Enter.\nPosition through Pick\nInitiates the same functionality as that available from the Align with Feature on the Model Editor handle. the Position through Pick functionality is common through AVEVA E3D Design.\nFor use with the Offset functionality, to offset the selected position form the top of duct/bottom of duct.\nNote:\nThis functionality is not available for this release.\nOther\nCopy current component\nCopies the currently selected HVAC component.\nUse this functionality to check if there are no unset references or connections and to look for any potential issues.\nNote:\nThis functionality is not available for this release.\nDirection\nDirect Component\nUse the Direct functionality to modify the direction of HVAC elbow and bend components.\nAxes are displayed in the 3D view, dependent upon which direction is selected on the power compass.\nRotate Component\nUse the Rotate functionality to rotate HVAC tees and other non-symmetrical components such as bends or reducers.\nAxes are displayed in the 3D view, along with an angle representation dependent upon which angle is selected on the power compass.\nPosition Component\nUse the Position Component functionality to position HVAC components, input a value in the text field and select the direction from the Direction Power Wheel.\nUp, Down, Right and Left axes are displayed in the 3D view.\nNote:\nSub components also display the distance to the end of the owning straight element.\nWhen positioning a sub component\nA bar is displayed next to the positioning arrows, use to position the subcomponent to the respective edge of the owing straight element.\nNote:\nFor this release sub components can only be positioned using this functionality when owned by a straight element.\nDirect to head branch\nPositions the currently selected HVAC component directly to the HVAC head branch.\nDirect to previous element\nPositions the currently selected HVAC component directly to the previous HVAC element.\nDirect to next element\nPositions the currently selected HVAC component directly to the next HVAC element.\nDirect to branch head\nPositions the currently selected HVAC component directly to the HVAC branch head.\nDirect to Pick\nPositions the currently selected HVAC component directly to the picked HVAC component.\nPosition\n\n\nPosition through branch head\nAligns the selected HVAC component through the branch head.\n\nPosition through previous element\nAligns the selected HVAC component through the previous HVAC component of the HVAC branch.\n\nPosition through next element\nAligns the selected HVAC component through the next HVAC component of the HVAC branch.\n\nPosition through branch tail\nAligns the selected HVAC component through the branch tail.\n\nConnect to previous component\nConnects the selected HVAC component to the previous one.\n\nDistance - Clear to use Clearance\nDisplays the actual clearance. To change the clearance input a new value into the text flied then press Enter.\n\nPosition through Pick\nInitiates the same functionality as that available from the Align with Feature on the Model Editor handle. the Position through Pick functionality is common through AVEVA E3D Design.\n\n\nFor use with the Offset functionality, to offset the selected position form the top of duct/bottom of duct.\nOther\n\n\nCopy current component\nCopies the currently selected HVAC component.\n\n\nUse this functionality to check if there are no unset references or connections and to look for any potential issues.\nDirection\n\n\nDirect Component\nUse the Direct functionality to modify the direction of HVAC elbow and bend components.\n\nAxes are displayed in the 3D view, dependent upon which direction is selected on the power compass.\n\n\nRotate Component\nUse the Rotate functionality to rotate HVAC tees and other non-symmetrical components such as bends or reducers.\n\nAxes are displayed in the 3D view, along with an angle representation dependent upon which angle is selected on the power compass.\n\n\nPosition Component\nUse the Position Component functionality to position HVAC components, input a value in the text field and select the direction from the Direction Power Wheel.\n\nUp, Down, Right and Left axes are displayed in the 3D view.\n\n\nWhen positioning a sub component\nA bar is displayed next to the positioning arrows, use to position the subcomponent to the respective edge of the owing straight element.\n\n\nDirect to head branch\nPositions the currently selected HVAC component directly to the HVAC head branch.\n\nDirect to previous element\nPositions the currently selected HVAC component directly to the previous HVAC element.\n\nDirect to next element\nPositions the currently selected HVAC component directly to the next HVAC element.\n\nDirect to branch head\nPositions the currently selected HVAC component directly to the HVAC branch head.\n\nDirect to Pick\nPositions the currently selected HVAC component directly to the picked HVAC component.\n\nName\nThe name of new HVAC element is auto generated as per project rules; if required you can enter another name for the new HVAC element.\nPrimary System\nUse to select the primary system to which it belongs; the default is No System.\nStandard\nUse to select the required standard\nSpecifications\nUse to select the required specification. By default, this specification will be used but an alternative specification can be selected from the Branch pane of the HVAC Editor window for individual HVAC branches.\nThere are two specifications - rectangular and circular (SIMDUCT-CLASS-C and SIMDUCT-CLASS-F (both specifications are the same except F is the fireproof specification). You can change the dimensions but not the specification. However the straight components can be modified as this could occur on site.\nThere is also a custom specification where you can modify any dimension on the HVAC components to suit your requirements.\nNote:\nStandards, specifications and defaults are created in Catalog.\nInsulation\nUse to select the required insulation. This functionality can be applied to the current element and to a range of components. The default is None.\nCustom Settings\nThis functionality is enabled once the Custom specification is selected from the Specification drop-down list.\nUse to select the required custom settings for the new HVAC element.\nNote:\nThe greyed-out custom settings will display whichever custom settings are linked to the selected specification (if any are linked).\nSet working HVAC\nSets the currently selected HVAC, from the Model Explorer or 3D graphical view, as the working HVAC.\nCreate new branch\nUse to create a new HVAC branch in the model hierarchy below the currently selected HVAC element.\nBranch Connections\nThe branch connections pane is automatically displayed in the HVAC Editor window with the head and tail positioned but not connected.\nName\nThe name of new HVAC branch element is auto generated as per project rules and with reference to it\u2019s owning HVAC element in the hierarchy; if required you can enter another name for the new HVAC element.\nSpecification\nThe specification of the owning HVAC element is displayed.\nInsulation\nThe insulation selected for the owning HVAC element is displayed.\nCustom Settings\nIf the owning element\u2019s specification has been selected as Custom, this functionality will not be greyed out; the custom settings for it\u2019s owning element is displayed.\nClose this form and open Create HVAC Component form\nUse to close the HVAC Editor window and open the HVAC Components Editor window populated with HVAC components available for selection as defined by the selected specification.\nPosition (Unconnected) label\nThe branch head is positioned at the default co-ordinates 0,0,0 (origin) but is not connected to any HVAC components.\nNote:\n'Positioned (Unconnected)' can also represent any unconnected head/tail in free space (and the label text should change to reflect connection status).\nSwitch values between head and tail\nSwitches all the data entered in the HVAC Head and Tail pane of the HVAC Editor window between the HVAC branch head or the HVAC branch tail tabs.\nDisconnect head\nDisconnects the branch head from the element it is currently connected to.\nReconnect head\nReconnects the branch head that has moved position to an equipment element.\nPick Branch in laser data to set head to\nUse to connect the laser data to position the head or tail of the HVAC branch at a position derived from the point cloud data.\nNote:\nThis functionality is not available for this release.\nPick item to connect head to\nConnects the branch head to a selected element.\nConnect head to first branch member\nConnects the branch head to the first branch member.\nRectangular\nDefines the branch head shape as Rectangular. The width and depth fields are automatically populated with dimensions governed by the selected specification. If required these dimensions can be switched.\nCircular\nDefines the branch head shape as Circular. A diameter field is automatically populated with a dimension governed by the selected specification.\nFlat Oval\nDefines the branch head shape as Flat Oval. A width and depth fields are automatically populated with dimensions governed by the selected specification.\nNote:\nWhen later creating an HVAC component to connect to the branch head, the shape of the HVAC must match the shape specified.\nDirection\nSpecifies the direction that the HVAC will take from the branch head.\nValid dimensions for the head direction are E (East), N (North), U (Up), -E (negative East), -N (negative North) or -U (negative Up).\nZ Axis (HZAXIS)\nUse to define the Z direction, typically the \u2018up\u2019 direction) of the HVAC branch head (this ensures any selected component\u2019s Z axis aligns as expected with the branch\u2019s head Z axis)\nReverse Direction\nUse to switch the direction of the HVAC branch head.\nPosition\nFormat\nSelect the position format - ENU, XYZ or Grid.\nWRT\nPositions the HVAC branch head WRT to the named design element, for example the World, Zone.\nDisplay positions as offset from nearest grid plane\nDisplays the picked position as an offset from the nearest grid.\nWRT current element\nPositions the HVAC branch WRT to the currently selected element.\nWRT CE owner\nPositions the HVAC branch WRT to the currently selected element\u2019s owner in the model hierarchy.\nWRT world\nPositions the HVAC branch WRT to the WORLD element in the Model hierarchy.\nWRT picked element\nPositions the HVAC branch WRT to the picked element in the 3D view.\nPicked position\nPositions the HVAC branch WRT to the picked position in the 3D view.\nOffset\nPositions the HVAC branch at an offset distance from a known position.coordinates for the known\nEnter the co-ordinates for the known position, in the format selected.\nClick Offset\nEnter the co-ordinates for the offset or pick the position in the 3D view.\nNudge\nNudges the new HVAC branch by a defined distance to the right or to the left in the 3D view.\nBranch\nUse to return to the HVAC Editor window to modify HVAC or branch attributes. The name of the currently selected branch selected in the model explorer is also displayed.\nBack\nClick to return to the HVAC Editor window.\nCreate\nSpecification\nThe specification selected in the Branch pane of the HVAC Editor window is displayed in the specification field.\nNote:\nIf a specification is selected that does not match the HVAC specification, an out-of-spec message is displayed in the HVAC Components Editor window.\nInsulation\nThe insulation specification selected in the Branch pane of the HVAC Editor window is displayed in the Insulation field.\nCustom Settings\nIf the Custom Specification/ Custom Settings is selected in the Branch pane of the HVAC Editor window, the setting is displayed in the Custom Settings field.\nPosition\nPosition through branch head\nAligns the selected HVAC component through the branch head.\nPosition through previous element\nAligns the selected HVAC component through the previous HVAC component of the HVAC branch.\nPosition through next element\nAligns the selected HVAC component through the next HVAC component of the HVAC branch.\nPosition through branch tail\nAligns the selected HVAC component through the branch tail.\nConnect to previous component\nConnects the selected HVAC component to the previous one.\nDistance - Clear to use Clearance\nDisplays the actual clearance. To change the clearance input a new value into the text flied then press Enter.\nPosition through Pick\nInitiates the same functionality as that available from the Align with Feature on the Model Editor handle. the Position through Pick functionality is common through AVEVA E3D Design.\nFor use with the Offset functionality, to offset the selected position form the top of duct/bottom of duct.\nNote:\nThis functionality is not available for this release.\nOther\nCopy current component\nCopies the currently selected HVAC component.\nUse this functionality to check if there are no unset references or connections and to look for any potential issues.\nNote:\nThis functionality is not available for this release.\nDirection\nDirect Component\nUse the Direct functionality to modify the direction of HVAC elbow and bend components.\nAxes are displayed in the 3D view, dependent upon which direction is selected on the power compass.\nRotate Component\nUse the Rotate functionality to rotate HVAC tees and other non-symmetrical components such as bends or reducers.\nAxes are displayed in the 3D view, along with an angle representation dependent upon which angle is selected on the power compass.\nPosition Component\nUse the Position Component functionality to position HVAC components, input a value in the text field and select the direction from the Direction Power Wheel.\nUp, Down, Right and Left axes are displayed in the 3D view.\nNote:\nSub components also display the distance to the end of the owning straight element.\nWhen positioning a sub component\nA bar is displayed next to the positioning arrows, use to position the subcomponent to the respective edge of the owing straight element.\nNote:\nFor this release sub components can only be positioned using this functionality when owned by a straight element.\nDirect to head branch\nPositions the currently selected HVAC component directly to the HVAC head branch.\nDirect to previous element\nPositions the currently selected HVAC component directly to the previous HVAC element.\nDirect to next element\nPositions the currently selected HVAC component directly to the next HVAC element.\nDirect to branch head\nPositions the currently selected HVAC component directly to the HVAC branch head.\nDirect to Pick\nPositions the currently selected HVAC component directly to the picked HVAC component.\nNote:\nStandards, specifications and defaults are created in Catalog.\nNote:\nThe greyed-out custom settings will display whichever custom settings are linked to the selected specification (if any are linked).\nNote:\nThe functionality available from the Branch Head tab and Branch Tail tab are identical, therefore only the functionality for Branch Head will be described.\nNote:\n'Positioned (Unconnected)' can also represent any unconnected head/tail in free space (and the label text should change to reflect connection status).\nNote:\nThis functionality is not available for this release.\nNote:\nWhen later creating an HVAC component to connect to the branch head, the shape of the HVAC must match the shape specified.\nNote:\nIf a specification is selected that does not match the HVAC specification, an out-of-spec message is displayed in the HVAC Components Editor window.\nNote:\nThis functionality is not available for this release.\nNote:\nThis functionality is not available for this release.\nNote:\nSub components also display the distance to the end of the owning straight element.\nNote:\nFor this release sub components can only be positioned using this functionality when owned by a straight element.\n\n\n\nHVAC Editor and HVAC Components Editor\nNew HVAC Element\nName\nPrimary System\nNo System\nStandard\nSpecifications\nHVAC Editor\nNote\n:\nInsulation\nNone\nCustom Settings\nCustom\nSpecification\nNote\n:\nSet working HVAC\nCreate new branch\nBranch Connections\nHVAC Editor\nBranch Element\nBranch\nHVAC Editor\nName\nSpecification\nInsulation\nCustom Settings\nClose this form and open Create HVAC Component form\nHVAC Editor\nHVAC Components Editor\nBranch Head/Branch Tail\nBranch Head/Branch Tail\nHVAC Editor\nBranch Head\nNote\n:\nPosition (Unconnected) label\nNote\n:\nSwitch values between head and tail\nHVAC Head\nTail\nHVAC Editor\nDisconnect head\nReconnect head\nPick Branch in laser data to set head to\nNote\n:\nPick item to connect head to\nConnect head to first branch member\nRectangular\nCircular\nFlat Oval\nNote\n:\nDirection\nZ Axis (HZAXIS)\nReverse Direction\nPosition\nFormat\nWRT\nDisplay positions "}
{"Headers": "Insulation", "Content": "Use the functionality available from the Insulation group of the UI to select the Insulation specification, apply it to the current selected element (a branch or component) or to a range of components and view the insulation in the 3D view applied to the selection.\nApply to CE\nApplies the insulation specification to the currently selected HVAC element (branch or component).\nApply to Range\nApplies the insulation specification to a selected range in the 3D view.\nShow Insulation\nUse this toggle to enable/disable if the insulation is displayed in the 3D view.\nApply to CE\nApplies the insulation specification to the currently selected HVAC element (branch or component).\nApply to Range\nApplies the insulation specification to a selected range in the 3D view.\n\nShow Insulation\nUse this toggle to enable/disable if the insulation is displayed in the 3D view.\nSubcomponent\nA sub component element in HVAC is used for general purpose sub elements which are placed under their container elements and mapped with soft types. The element can take any element type based on the Spec Ref and Design parameters provided by the user. The position and orientation attributes are set with respect to the owner element.\nSub components such as branch connectors or access panels are present on the surface of a parent element, these element types have additional volume and will refer to the insulation specification, insulation is also applied to them as per the settings.\n\nOnce the insulation has been applied, check for clashes the results are displayed in the Clashes window.\n\nApply to CE\nApplies the insulation specification to the currently selected HVAC element (branch or component).\nApply to Range\nApplies the insulation specification to a selected range in the 3D view.\nShow Insulation\nUse this toggle to enable/disable if the insulation is displayed in the 3D view.\n\n\n\nApply to CE\nApply to Range\nShow Insulation\nSubcomponent\nClashes"}
{"Headers": "Joints", "Content": "Use the HVAC Joints functionality to add and/or modify the joints for custom components, to display each joint for the currently selected element and the others in the HVAC branch, display the configuration (arrive/leave), view a close up of the currently selected element in the 3D view and carry out compatibility checks. Some of the joints have geometry which can seen in the 3D view.\n\nThe HVAC Joints window is initially displayed empty. To display a list of available joints, select the required HVAC element in the 3D view or model hierarchy. The default joint is highlighted in the list. These joints are governed by the custom settings.\nThe functionality available for selection is dependent upon the currently selected element of the HVAC branch. For example - if the currently selected element is a standard HVAC component with an arrive and leave, branch connector or threeway HVAC element.\n\nShow CE\nClick to identify the currently selected element in the Model Explorer or 3D view as the current element.\nShow joints\nDisplays the joints of the HVAC branch in the 3D view and an compatibility check is carried out.\nThe joints for the entire HVAC branch are labelled in the 3D view\nNote:\nCross branch and branch joint connectors checking are not available for this release.\nIncompatible Joints\nIncompatible joints are identified after the compatibility check and labelled in the 3D view; select a joint from the list of available joints governed by the specification.\nSpecification Change\nSpecification changes are also identified after the compatibility check and labelled in the 3D view. In this example - a custom straight joins a standard straight.\nNote:\nStandard components do not have joints. There the HVAC Joints window is not populated and no geometry is displayed in the 3D view.\nBranch Connectors\nBranch connectors have only a fixing joint, which can be selected (no geometry is displayed in the 3D view).\nShow configurations\nDisplays the arrive and leave of the HVAC element in the 3D view.\nZoom\nProvides a close up of the currently selected element in the 3D view.\nMatch previous\nMatches the joint to the previous one.\nDefault\nSets the joints to the default.\nMatch next\nMatches the joint to the next one\n\nShow CE\nClick to identify the currently selected element in the Model Explorer or 3D view as the current element.\n\nShow joints\nDisplays the joints of the HVAC branch in the 3D view and an compatibility check is carried out.\n\nThe joints for the entire HVAC branch are labelled in the 3D view\n\n\n\nIncompatible Joints\nIncompatible joints are identified after the compatibility check and labelled in the 3D view; select a joint from the list of available joints governed by the specification.\n\n\n\nSpecification Change\nSpecification changes are also identified after the compatibility check and labelled in the 3D view. In this example - a custom straight joins a standard straight.\n\n\n\n\nBranch Connectors\nBranch connectors have only a fixing joint, which can be selected (no geometry is displayed in the 3D view).\n\n\n\nShow configurations\nDisplays the arrive and leave of the HVAC element in the 3D view.\n\n\nZoom\nProvides a close up of the currently selected element in the 3D view.\n\nMatch previous\nMatches the joint to the previous one.\n\nDefault\nSets the joints to the default.\n\nMatch next\nMatches the joint to the next one\n\nShow CE\nClick to identify the currently selected element in the Model Explorer or 3D view as the current element.\nShow joints\nDisplays the joints of the HVAC branch in the 3D view and an compatibility check is carried out.\nThe joints for the entire HVAC branch are labelled in the 3D view\nNote:\nCross branch and branch joint connectors checking are not available for this release.\nIncompatible Joints\nIncompatible joints are identified after the compatibility check and labelled in the 3D view; select a joint from the list of available joints governed by the specification.\nSpecification Change\nSpecification changes are also identified after the compatibility check and labelled in the 3D view. In this example - a custom straight joins a standard straight.\nNote:\nStandard components do not have joints. There the HVAC Joints window is not populated and no geometry is displayed in the 3D view.\nBranch Connectors\nBranch connectors have only a fixing joint, which can be selected (no geometry is displayed in the 3D view).\nShow configurations\nDisplays the arrive and leave of the HVAC element in the 3D view.\nZoom\nProvides a close up of the currently selected element in the 3D view.\nMatch previous\nMatches the joint to the previous one.\nDefault\nSets the joints to the default.\nMatch next\nMatches the joint to the next one\nNote:\nJoints can be modelled into specifications, but there will be no compatibility checks. The functionality available in the PIPING discipline (COCO tables) is not available in this release.\nNote:\nThis list of available joints can be filtered.\nNote:\nCross branch and branch joint connectors checking are not available for this release.\nNote:\nStandard components do not have joints. There the HVAC Joints window is not populated and no geometry is displayed in the 3D view.\n\n\n\nHVAC Joints\nNote\n:\nHVAC Joints\nNote\n:\nShow CE\nShow joints\nNote\n:\nIncompatible Joints\nSpecification Change\nNote\n:\nBranch Connectors\nShow configurations\nZoom\nMatch previous\nDefault\nMatch next"}
{"Headers": "Gaps", "Content": "Gaps exist between the created HVAC components and sub-components. The gaps between the created components and sub-components are left undefined and are automatically filled with implied duct work to complete the design model in the 3D view.\nTo fill the gaps and to also ensure the design can be prefabricated, it is necessary to specify the required fixed lengths of duct work straights between the components and sub components. These standard and non-standard straights required to fill each gap are then created in the design database and displayed in the hierarchy.\nUse the Gaps functionality to shows and fill the gaps in implied HVAC. The gaps can be filled from either direction; gaps will not be filled where there is a joint. This functionality can be applied to a SITE, ZONE or HVAC element.\n\nThe HVAC Gap Manager window is displayed with all the gaps in the currently selected element in the hierarchy. Any gap that is shorter then the allowable length defined in the selected specification is highlighted (these gaps will not be filled). The gaps displayed can be filtered using filter criteria.\nThe gaps are highlighted in the 3D view and the gaps are represented by the HVAC tube translucency setting.\nIf the gap is highlighted in the gap list, it is also highlighted in the 3D view.\n\nUse the right-click menu to centre on the selection or zoom to the selection in the 3D view. Both options available for selection are toggles.\n\nCentre on Selection\nCenters the selected gap in the 3D view.\nZoom to Selection in 3D View\nZooms to the selected gap in the 3D view.\nFill gaps from branch head\nWhen checked (default), fills the gaps in the currently selected HVAC from the branch head. Un-check to from the gaps from the branch tail.\nIf the length of the gap is more than the allowable length (defined in the specification) and the Fills gaps from branch head check box is checked, the gap is filled with a number of straights matching the standard length defined by the specification in the direction of the branch head.\nNote:\nStandard lengths can be manually lengthened.\nHighlight gaps\nHighlights the gaps in the currently selected HVAC branch in the 3D view. The gaps that are within the allowable length are translucent; short lengths are highlighted red.\nShow dimensions\nLabels the gaps in the currently selected HVAC branch in the 3D view.\nNote:\nThis functionality is not enabled until the Highlight Gaps is selected.\nPreview fill\nHighlights the gaps to be filled in the currently selected HVAC branch in the 3D view as red.\nNote:\nThe highlight colour is by default red - this can be modified in the Colour Settings. refer to your System Administrator for further information.\nFill gaps\nFills all the gaps in the currently selected HVAC branch.\nUnfill gaps\nUn fills all the gaps in the currently selected HVAC branch\nNote:\nUndo also un fills the gaps.\nCentre on Selection\nCenters the selected gap in the 3D view.\n\nZoom to Selection in 3D View\nZooms to the selected gap in the 3D view.\n\n\nFill gaps from branch head\nWhen checked (default), fills the gaps in the currently selected HVAC from the branch head. Un-check to from the gaps from the branch tail.\nIf the length of the gap is more than the allowable length (defined in the specification) and the Fills gaps from branch head check box is checked, the gap is filled with a number of straights matching the standard length defined by the specification in the direction of the branch head.\n\n\nHighlight gaps\nHighlights the gaps in the currently selected HVAC branch in the 3D view. The gaps that are within the allowable length are translucent; short lengths are highlighted red.\n\n\nShow dimensions\nLabels the gaps in the currently selected HVAC branch in the 3D view.\n\n\nPreview fill\nHighlights the gaps to be filled in the currently selected HVAC branch in the 3D view as red.\n\n\nFill gaps\nFills all the gaps in the currently selected HVAC branch.\n\nUnfill gaps\nUn fills all the gaps in the currently selected HVAC branch\n\nCentre on Selection\nCenters the selected gap in the 3D view.\nZoom to Selection in 3D View\nZooms to the selected gap in the 3D view.\nFill gaps from branch head\nWhen checked (default), fills the gaps in the currently selected HVAC from the branch head. Un-check to from the gaps from the branch tail.\nIf the length of the gap is more than the allowable length (defined in the specification) and the Fills gaps from branch head check box is checked, the gap is filled with a number of straights matching the standard length defined by the specification in the direction of the branch head.\nNote:\nStandard lengths can be manually lengthened.\nHighlight gaps\nHighlights the gaps in the currently selected HVAC branch in the 3D view. The gaps that are within the allowable length are translucent; short lengths are highlighted red.\nShow dimensions\nLabels the gaps in the currently selected HVAC branch in the 3D view.\nNote:\nThis functionality is not enabled until the Highlight Gaps is selected.\nPreview fill\nHighlights the gaps to be filled in the currently selected HVAC branch in the 3D view as red.\nNote:\nThe highlight colour is by default red - this can be modified in the Colour Settings. refer to your System Administrator for further information.\nFill gaps\nFills all the gaps in the currently selected HVAC branch.\nUnfill gaps\nUn fills all the gaps in the currently selected HVAC branch\nNote:\nUndo also un fills the gaps.\nNote:\nOnce a modification has been made, you must selected CE (located at the top left hand corner of the HVAC Gap Manager window) again.\nNote:\nStandard lengths can be manually lengthened.\nNote:\nThis functionality is not enabled until the Highlight Gaps is selected.\nNote:\nThe highlight colour is by default red - this can be modified in the Colour Settings. refer to your System Administrator for further information.\nNote:\nUndo also un fills the gaps.\n\n\n\nGaps\nNote\n:\nHVAC Gap Manager\nHVAC Gap Manager\nHVAC tube translucency setting\nCentre on Selection\nZoom to Selection in 3D View\nFill gaps from branch head\nFills gaps from branch head\nNote\n:\nHighlight gaps\nShow dimensions\nNote\n:\nHighlight Gaps\nPreview fill\nNote\n:\nFill gaps\nUnfill gaps\nNote\n:"}
{"Headers": "Drag", "Content": "Use the Drag Move functionality available from the Drag Move Branch window to move an HVAC Branch in a set direction; the Drag Move functionality is common through AVEVA 3D Design.\n\nUse the Move functionality available from the Move Branch window to move the currently selected HVAC branch in a set direction, the Move functionality is common through AVEVA 3D Design.\n\nNote:\nIf the HVAC branch is repositioned using the generic positioning commands, the branches connected do not move automatically with the item. The Drag Move function is used to move constrained networks of HVAC, Equipment and Nozzle elements all together. How the constrained network is created depends on the direction of the drag operation and the type of item being dragged.\n\n\n\nNote\n:\nDrag Move\nDrag Move\nDrag Move Branch\nDrag\nMove\nMove\nMove Branch\nMove"}
{"Headers": "Delete", "Content": "Use the functionality available from the Tools group to delete a selection, a current element or individual elements from the currently selected element; the Delete Range functionality is common through AVEVA 3D Design.\n\n\n\n\nTools\nDelete Range"}
{"Headers": "Modify", "Content": "Use the functionality to modify HVAC, HVAC component(s) and HVAC sub-component(s) specification, insulation, dimensions (dependent upon the selected component or sub component), position and direction.\nDouble click the required element in the 3D view; use the functionality available from one of the three Linear Movement Handles (clicking one of these three handles constrains the movement of the selection to be in the direction of the selected axis).\n\nUse the functionality available from the HVAC Component Editor window to modify HVAC, HVAC component(s) and HVAC sub-component(s) specification, insulation, dimensions (dependent upon the selected component or sub component), position and direction.\n\nRefer to AVEVA Catalog, Laser Data, Linear and Planar Movement, Color Settings - All Views and Graphics Settings - Drawlist for further information.\n\n\n"}
{"Headers": "Worked Example", "Content": "To create or modify a detailing specification, refer to the System Administrator.\nAll of the tasks carried out that are associated with the creation or modification of HVAC are initiated from a central HVAC Editor window which acts as a task hub. Depending on selections made in the window, further functionality becomes available.\nRefer to Advance Move - Common Functionality, Move Common functionality, Delete - common functionality and Position and Orientate - Common Functionality for further information.\n\n\n\n.\nHVAC Editor\nNEW HVAC - EVAL ONLY\nCreate\nHVAC\nHVAC Editor\nNote\n:\nNo System\nAir Conditioning Supply\nPrimary System\nAVEVA-HVAC-STANDARD\nStandard\nCustom\nSpecification\nPosition through Pick\nCreate HVAC Component Editor\nCoupling\nCoupling\nCoupling\nModify\nPosition\nHVAC Component Editor\nAVEVA- RECTANGULAR\nPosition through Pick\nPick A Position (Distance [0])\nStraight\nStraight\nModify\nPosition\nHVAC Component Editor\nModify\nHVAC Component Editor\nHVAC Straight\nStraight\nModify\nHVAC Component Editor\nHVAC Straight\nBend\nCircular Radiused Bend\nBend\nModify\nPosition\nHVAC Component Editor\nDirection\nHVAC Component Editor\nRotate Component\nStraight\nStraight\nModify\nPosition\nHVAC Component Editor\nModify\nHVAC Component Editor\nHVAC Straight\nIn line Equipment\nDamper\nCircular Fire Dampe\nHVAC Circular Fire Damper\nStraight\nStraight\nModify\nPosition\nHVAC Component Editor\nModify\nHVAC Component Editor\nHVAC Straight\nBend\nCircular 3 Segment Bend\nBend\nModify\nPosition\nHVAC Component Editor\nModify\nHVAC Component Editor\nAngle\nTHRE\nCircular Side Branch Tee Piece\nCircular Side Branch Tee Piece\nConfiguration 1_2\nTHRE 1\nModify\nPosition\nHVAC Component Editor\nDirection\nHVAC Component Editor\nDirect Component\nE\nTransformation\nSquare to Round Transformation\nTRANS 1\nModify\nPosition\nHVAC Component Editor\nOffset\nRectangular Radiused Offset\nOFST 1\nModify\nPosition\nHVAC Component Editor\nModify\nHVAC Component Editor\nA Offset\nDirection\nHVAC Component Editor\nRotate Component\nStraight\nStraight\nModify\nPosition\nHVAC Component Editor\nModify\nHVAC Component Editor\nHVAC Straight\nIn line Equipment\nDamper\nHVAC Damper\nStraight\nStraight\nModify\nPosition\nHVAC Component Editor\nModify\nHVAC Component Editor\nHVAC Straight\nTHRE\nRectangular Square Threeway\nConfiguration 2_1\nTHRE\nModify\nPosition\nHVAC Component Editor\nStraight\nStraight\nModify\nPosition\nHVAC Component Editor\nModify\nHVAC Component Editor\nHVAC Straight\nIn line Equipment\nDamper\nHVAC Damper\nStraight\nStraight\nModify\nPosition\nHVAC Component Editor\nModify\nHVAC Component Editor\nHVAC Straight\nStraight\nStraight\nModify\nPosition\nHVAC Component Editor\nTHRE\nRectangular Square Threeway\nConfiguration 2_1\nTHRE\nModify\nPosition\nHVAC Component Editor\nHVAC THRE\nDirection\nHVAC Component Editor\nRotate Component\nStraight\nStraight\nModify\nPosition\nHVAC Component Editor\nBend\nRectangular Radiused Bend\nHVAC Rectangular Radiused Bend\nModify\nPosition\nHVAC Component Editor\nDirection\nHVAC Component Editor\nRotate Component\nStraight\nStraight\nModify\nPosition\nHVAC Component Editor\nHVAC Straight\nEnd Pieces\nMesh Guard\nMesh Guard\nHVAC THRE1\nCreate\nHVAC\nHVAC Editor\nBRAN HVAC-7-B1\nHVAC THRE1\nCreate\nHVAC Component form\nHVAC Component Editor window\nStraight\nStraight\nModify\nPosition\nHVAC Component Editor\nHVAC Straight\nBend\nCircular 7 Segment Bend\nHVAC Circular Radiused Bend\nModify\nPosition\nHVAC Component Editor\nHVAC\nRadiused Bend\nDirection\nHVAC Component Editor\nDirect Component\nD\nMaterial Connection\nCircular Material Connection\nMaterial Connection\nEnd Pieces\nMesh Guard\nMesh Guard\nSub-Components All Shapes\nAccess Panel\n\u2018Pick the position for placement of components. Press ESC to finish\u2019\nModify\nHVAC Component Editor\nDIrection\nHVAC Component Editor\nPosition Component\nNote\n:\nModify\nGaps\nTools\nHVAC Gap Manager\nNote\n:\nHVAC Gap Manager\nPreview Fill\nFill gaps\nSTRT 1\nHVAC BRAN- 6-B1\nTools\nJoints\nHVAC Joints\nShow Joints\nHVAC Joints\nOFSET 1\nCE\nZoom\nHVAC Joints\nShow configuration\nArrive\nMatch next\nLeave\nMatch next,\nSTRT 12\nCE\nHVAC Joints\nCreate\nComponent\nHVAC Component Editor\nBranch Connectors All Shapes\nRectangular Square Branch\n\u2018Pick the position for placement of the components. Press ESC to finish:\nHVHAZCC 1\nHVAC Joints\nHVAC Joints\nShow joints\nFixing\nShow Joints\nBranch\nInsulation\nInsulation\n80mm insulation\nApply to Range\n\u2018Pick start element of sequence to apply insulation to:\nSTRT 1\nBRAN HVAC-6-B1 element\nPick end element of sequence to apply the insulation to:\nSTRT 15\nBRAN HVAC-6-B1 element\nShow Insulation"}
{"Headers": "Plant 3D model features", "Content": "The following outlines the plant 3D model import features:\nFeature\nPurpose\nInput Formats\nE3D Design Format\nMechanical Equipment Interface and STL\nVendor equipment import\nSTP, STL, SAT, IGES, XYZ\nGENPRI\nMultiCAD Import\nVendor equipment and plant model import\nAround 30 Native CAD formats. Refer to the User Guide and Release Notes for more information on exact versions.\nGENPRI + Hierarchy & Data\nModel Simplification\nVendor equipment import with simplification\nSTP\nA range of native CAD formats\nGENPRI + Limited Hierarchy & Data\nIFC\nPlant model import for referencing and coordination\nIFC 2X3 and 4\nGENPRI + Hierarchy & Data\nCADENAS \u2013 3DfindIT.com\nEquipment import from vendor catalogue\nN/A\nStandard Model Library - Equipment with Native Primitives\n3D DGN\nVendor equipment and plant model import\nDGN\nPOLYHE, POGO, (GENSEC)\n2D DWG/DXF\n2D plant layouts / overlays for 3D modelling purposes\nDWG/DXF\nAid elements\nSDNF\nSteel Detailing Import\nSteel Detailing Neutral File (OSDE)\nSCTN, GENSEC, PANEL\nE3D Structural Design/Bocad\nSteel Detailing Import\nABSI\nSCTN, GENSEC, PANEL\nWork Packs\nImport of WorkPacks\nExcel file\nWorkpack hierarchy\nPCF (E3D 4.0 onwards)\nImport of Pipe Spools\nPCF\nNative piping elements\nTerrain\nImport of terrain models\nIGES, STEP, STL and XYZ\nNative E3D Terrain Surface\nExcel\nImport of Excel files\nCSV, XLS, XLSX\nElements & Attributes\n(Intergraph S3D / PDS)\nImport of catalogues and plant models.\nNote:\nThis is not an import feature, but rather a conversion service. Not included in standard product - delivered as a service.\nS3D / PDS project data (project backup)\nNative AVEVA E3D Catalogues and Plant models\nFeature\nPurpose\nInput Formats\nE3D Design Format\nMechanical Equipment Interface and STL\nVendor equipment import\nSTP, STL, SAT, IGES, XYZ\nGENPRI\nMultiCAD Import\nVendor equipment and plant model import\nAround 30 Native CAD formats. Refer to the User Guide and Release Notes for more information on exact versions.\nGENPRI + Hierarchy & Data\nModel Simplification\nVendor equipment import with simplification\nSTP\nA range of native CAD formats\nGENPRI + Limited Hierarchy & Data\nIFC\nPlant model import for referencing and coordination\nIFC 2X3 and 4\nGENPRI + Hierarchy & Data\nCADENAS \u2013 3DfindIT.com\nEquipment import from vendor catalogue\nN/A\nStandard Model Library - Equipment with Native Primitives\n3D DGN\nVendor equipment and plant model import\nDGN\nPOLYHE, POGO, (GENSEC)\n2D DWG/DXF\n2D plant layouts / overlays for 3D modelling purposes\nDWG/DXF\nAid elements\nSDNF\nSteel Detailing Import\nSteel Detailing Neutral File (OSDE)\nSCTN, GENSEC, PANEL\nE3D Structural Design/Bocad\nSteel Detailing Import\nABSI\nSCTN, GENSEC, PANEL\nWork Packs\nImport of WorkPacks\nExcel file\nWorkpack hierarchy\nPCF (E3D 4.0 onwards)\nImport of Pipe Spools\nPCF\nNative piping elements\nTerrain\nImport of terrain models\nIGES, STEP, STL and XYZ\nNative E3D Terrain Surface\nExcel\nImport of Excel files\nCSV, XLS, XLSX\nElements & Attributes\n(Intergraph S3D / PDS)\nImport of catalogues and plant models.\nS3D / PDS project data (project backup)\nNative AVEVA E3D Catalogues and Plant models\nThe following outlines the plant 3D model export features:\nFeature\nPurpose\nExport Formats\nIFC\nPlant model export for referencing and coordination\nIFC 2X3 and 4\nMEI\nPlant Model export\nSTP, SAT, XGL\nReview Model\nVisualization and viewing\nRVM\nDGN\nPlant Model export\nDGN v7\nDXF\nPlant Model export\n3D DXF\nSDNF\nSteel Detailing Neutral File (OSDE)\nSDNF\nIDF\nISODraft - Pipe spool export\nIDF\nE3D Structural Design / BOCAD\nSteel detailing export\nABSI\n(Intergraph S3D)\nConversion of catalogues and plant models.\nNote:\nThis is not an export feature, but rather a conversion service. Not included in standard product - delivered as a service.\nS3D native project data\nPublish to AIM\nPublish to AVEVA Asset Information Management\nEIWM and ZGL/XGL\nFeature\nPurpose\nExport Formats\nIFC\nPlant model export for referencing and coordination\nIFC 2X3 and 4\nMEI\nPlant Model export\nSTP, SAT, XGL\nReview Model\nVisualization and viewing\nRVM\nDGN\nPlant Model export\nDGN v7\nDXF\nPlant Model export\n3D DXF\nSDNF\nSteel Detailing Neutral File (OSDE)\nSDNF\nIDF\nISODraft - Pipe spool export\nIDF\nE3D Structural Design / BOCAD\nSteel detailing export\nABSI\n(Intergraph S3D)\nConversion of catalogues and plant models.\nS3D native project data\nPublish to AIM\nPublish to AVEVA Asset Information Management\nEIWM and ZGL/XGL\n\nFeature\nPurpose\nInput Formats\nE3D Design Format\nMechanical Equipment Interface and STL\nVendor equipment import\nSTP, STL, SAT, IGES, XYZ\nGENPRI\nMultiCAD Import\nVendor equipment and plant model import\nAround 30 Native CAD formats. Refer to the User Guide and Release Notes for more information on exact versions.\nGENPRI + Hierarchy & Data\nModel Simplification\nVendor equipment import with simplification\nSTP\nA range of native CAD formats\nGENPRI + Limited Hierarchy & Data\nIFC\nPlant model import for referencing and coordination\nIFC 2X3 and 4\nGENPRI + Hierarchy & Data\nCADENAS \u2013 3DfindIT.com\nEquipment import from vendor catalogue\nN/A\nStandard Model Library - Equipment with Native Primitives\n3D DGN\nVendor equipment and plant model import\nDGN\nPOLYHE, POGO, (GENSEC)\n2D DWG/DXF\n2D plant layouts / overlays for 3D modelling purposes\nDWG/DXF\nAid elements\nSDNF\nSteel Detailing Import\nSteel Detailing Neutral File (OSDE)\nSCTN, GENSEC, PANEL\nE3D Structural Design/Bocad\nSteel Detailing Import\nABSI\nSCTN, GENSEC, PANEL\nWork Packs\nImport of WorkPacks\nExcel file\nWorkpack hierarchy\nPCF (E3D 4.0 onwards)\nImport of Pipe Spools\nPCF\nNative piping elements\nTerrain\nImport of terrain models\nIGES, STEP, STL and XYZ\nNative E3D Terrain Surface\nExcel\nImport of Excel files\nCSV, XLS, XLSX\nElements & Attributes\n(Intergraph S3D / PDS)\nImport of catalogues and plant models.\nNote:\nThis is not an import feature, but rather a conversion service. Not included in standard product - delivered as a service.\nS3D / PDS project data (project backup)\nNative AVEVA E3D Catalogues and Plant models\nFeature\nPurpose\nExport Formats\nIFC\nPlant model export for referencing and coordination\nIFC 2X3 and 4\nMEI\nPlant Model export\nSTP, SAT, XGL\nReview Model\nVisualization and viewing\nRVM\nDGN\nPlant Model export\nDGN v7\nDXF\nPlant Model export\n3D DXF\nSDNF\nSteel Detailing Neutral File (OSDE)\nSDNF\nIDF\nISODraft - Pipe spool export\nIDF\nE3D Structural Design / BOCAD\nSteel detailing export\nABSI\n(Intergraph S3D)\nConversion of catalogues and plant models.\nNote:\nThis is not an export feature, but rather a conversion service. Not included in standard product - delivered as a service.\nS3D native project data\nPublish to AIM\nPublish to AVEVA Asset Information Management\nEIWM and ZGL/XGL\nNote:\nThis is not an import feature, but rather a conversion service. Not included in standard product - delivered as a service.\nNote:\nThis is not an export feature, but rather a conversion service. Not included in standard product - delivered as a service.\n\n\n\nFeature\nPurpose\nInput Formats\nE3D Design Format\nNote:\nFeature\nPurpose\nExport Formats\nNote:"}
{"Headers": "Marine 3D model features", "Content": "The following outlines the marine 3D model import features:\nFeature\nPurpose\nInput Formats\nE3D Design Format\nSurface Manager\nImport of Hullform Surfaces\nSTP, SAT, IGS, DML\nE3D Hull Surface\nNAPA Import\nInternal surfaces (decks, bulkheads)\nCompartments\nNAPA Surface Definition File Format, STP, IGS\nPolyface\nSpace\nMechanical Equipment Interface and STL\nVendor equipment import\nSTP, STL, SAT, IGES, XYZ\nGENPRI\nMultiCAD Import\nVendor equipment model import\nAround 30 Native CAD formats. Refer to the User Guide and Release Notes for more information on exact versions.\nGENPRI + Hierarchy & Data\nModel Simplification\nVendor equipment import with simplification\nSTP\nA range of native CAD formats\nGENPRI + Limited Hierarchy & Data\nIFC\nModel import for referencing and coordination\nIFC 2X3 and 4\nGENPRI + Limited Hierarchy & Data\nCADENAS \u2013 3DfindIT.com\nEquipment import from vendor catalogue\nN/A\nStandard Model Library - Equipment with Native Primitives\n3D DGN\nVendor equipment and outfitting model import\nDGN\nPOLYHE, POGO, (GENSEC)\n2D DWG/DXF\n2D ship layouts / overlays for 3D modelling purposes\nDWG/DXF\nAid elements\nSDNF\nSteel Detailing Import\nSteel Detailing Neutral File (OSDE)\nSCTN, GENSEC, PANEL\nE3D Structural Design / Bocad\nSteel Detailing Import\nABSI\nSCTN, GENSEC, PANEL\nWork Packs\nImport of WorkPacks\nExcel file\nWorkpack hierarchy\nPCF (E3D 4.0 onwards)\nImport of Pipe Spools\nPCF\nNative piping elements\nExcel\nImport of Excel files\nCSV, XLS, XLSX\nElements & Attributes\nFeature\nPurpose\nInput Formats\nE3D Design Format\nSurface Manager\nImport of Hullform Surfaces\nSTP, SAT, IGS, DML\nE3D Hull Surface\nNAPA Import\nInternal surfaces (decks, bulkheads)\nCompartments\nNAPA Surface Definition File Format, STP, IGS\nPolyface\nSpace\nMechanical Equipment Interface and STL\nVendor equipment import\nSTP, STL, SAT, IGES, XYZ\nGENPRI\nMultiCAD Import\nVendor equipment model import\nAround 30 Native CAD formats. Refer to the User Guide and Release Notes for more information on exact versions.\nGENPRI + Hierarchy & Data\nModel Simplification\nVendor equipment import with simplification\nSTP\nA range of native CAD formats\nGENPRI + Limited Hierarchy & Data\nIFC\nModel import for referencing and coordination\nIFC 2X3 and 4\nGENPRI + Limited Hierarchy & Data\nCADENAS \u2013 3DfindIT.com\nEquipment import from vendor catalogue\nN/A\nStandard Model Library - Equipment with Native Primitives\n3D DGN\nVendor equipment and outfitting model import\nDGN\nPOLYHE, POGO, (GENSEC)\n2D DWG/DXF\n2D ship layouts / overlays for 3D modelling purposes\nDWG/DXF\nAid elements\nSDNF\nSteel Detailing Import\nSteel Detailing Neutral File (OSDE)\nSCTN, GENSEC, PANEL\nE3D Structural Design / Bocad\nSteel Detailing Import\nABSI\nSCTN, GENSEC, PANEL\nWork Packs\nImport of WorkPacks\nExcel file\nWorkpack hierarchy\nPCF (E3D 4.0 onwards)\nImport of Pipe Spools\nPCF\nNative piping elements\nExcel\nImport of Excel files\nCSV, XLS, XLSX\nElements & Attributes\nThe following outlines the marine 3D model export features:\nFeature\nPurpose\nExport Formats\nSurface Manager\nExport of Hullform Surfaces \u2013 Hull only\nSTP, SAT, IGS, DML\nIFC\nModel export \u2013 Outfitting only\nIFC 2X3 and 4\nMEI\nModel export \u2013 Outfitting only\nSTP, SAT, XGL\nReview Model\nVisualization and viewing \u2013 Hull & Outfitting\nRVM\nDGN\nShip Model export \u2013 Hull & outfitting\nDGN v7\nDXF\nShip Model export \u2013 Hull & Outfitting\n3D DXF\nSDNF\nSteel Detailing Neutral File (OSDE) \u2013 Outfitting Structures only\nSDNF\nE3D Structural Design / BOCAD\nSteel detailing export \u2013 Outfitting Structures only\nABSI\n(Intergraph S3D)\nConversion of catalogues and outfitting models.\nNote:\nNot included in the standard product - delivered as a service.\nS3D native project data\nPublish to AIM\nPublish to AVEVA Asset Information Management \u2013 Hull & Outfitting.\nEIWM and ZGL/XGL\nTransfer to AVEVA Marine\nTransfer the hull basic design model to AVEVA Marine 12 series \u2013 Hull only.\nSchema file + native DB transfer\nExport Hull Steel XML\nExport hull design model as XML to third party software - Hull only.\nXML\nFeature\nPurpose\nExport Formats\nSurface Manager\nExport of Hullform Surfaces \u2013 Hull only\nSTP, SAT, IGS, DML\nIFC\nModel export \u2013 Outfitting only\nIFC 2X3 and 4\nMEI\nModel export \u2013 Outfitting only\nSTP, SAT, XGL\nReview Model\nVisualization and viewing \u2013 Hull & Outfitting\nRVM\nDGN\nShip Model export \u2013 Hull & outfitting\nDGN v7\nDXF\nShip Model export \u2013 Hull & Outfitting\n3D DXF\nSDNF\nSteel Detailing Neutral File (OSDE) \u2013 Outfitting Structures only\nSDNF\nE3D Structural Design / BOCAD\nSteel detailing export \u2013 Outfitting Structures only\nABSI\n(Intergraph S3D)\nConversion of catalogues and outfitting models.\nS3D native project data\nPublish to AIM\nPublish to AVEVA Asset Information Management \u2013 Hull & Outfitting.\nEIWM and ZGL/XGL\nTransfer to AVEVA Marine\nTransfer the hull basic design model to AVEVA Marine 12 series \u2013 Hull only.\nSchema file + native DB transfer\nExport Hull Steel XML\nExport hull design model as XML to third party software - Hull only.\nXML\n\nFeature\nPurpose\nInput Formats\nE3D Design Format\nSurface Manager\nImport of Hullform Surfaces\nSTP, SAT, IGS, DML\nE3D Hull Surface\nNAPA Import\nInternal surfaces (decks, bulkheads)\nCompartments\nNAPA Surface Definition File Format, STP, IGS\nPolyface\nSpace\nMechanical Equipment Interface and STL\nVendor equipment import\nSTP, STL, SAT, IGES, XYZ\nGENPRI\nMultiCAD Import\nVendor equipment model import\nAround 30 Native CAD formats. Refer to the User Guide and Release Notes for more information on exact versions.\nGENPRI + Hierarchy & Data\nModel Simplification\nVendor equipment import with simplification\nSTP\nA range of native CAD formats\nGENPRI + Limited Hierarchy & Data\nIFC\nModel import for referencing and coordination\nIFC 2X3 and 4\nGENPRI + Limited Hierarchy & Data\nCADENAS \u2013 3DfindIT.com\nEquipment import from vendor catalogue\nN/A\nStandard Model Library - Equipment with Native Primitives\n3D DGN\nVendor equipment and outfitting model import\nDGN\nPOLYHE, POGO, (GENSEC)\n2D DWG/DXF\n2D ship layouts / overlays for 3D modelling purposes\nDWG/DXF\nAid elements\nSDNF\nSteel Detailing Import\nSteel Detailing Neutral File (OSDE)\nSCTN, GENSEC, PANEL\nE3D Structural Design / Bocad\nSteel Detailing Import\nABSI\nSCTN, GENSEC, PANEL\nWork Packs\nImport of WorkPacks\nExcel file\nWorkpack hierarchy\nPCF (E3D 4.0 onwards)\nImport of Pipe Spools\nPCF\nNative piping elements\nExcel\nImport of Excel files\nCSV, XLS, XLSX\nElements & Attributes\nFeature\nPurpose\nExport Formats\nSurface Manager\nExport of Hullform Surfaces \u2013 Hull only\nSTP, SAT, IGS, DML\nIFC\nModel export \u2013 Outfitting only\nIFC 2X3 and 4\nMEI\nModel export \u2013 Outfitting only\nSTP, SAT, XGL\nReview Model\nVisualization and viewing \u2013 Hull & Outfitting\nRVM\nDGN\nShip Model export \u2013 Hull & outfitting\nDGN v7\nDXF\nShip Model export \u2013 Hull & Outfitting\n3D DXF\nSDNF\nSteel Detailing Neutral File (OSDE) \u2013 Outfitting Structures only\nSDNF\nE3D Structural Design / BOCAD\nSteel detailing export \u2013 Outfitting Structures only\nABSI\n(Intergraph S3D)\nConversion of catalogues and outfitting models.\nNote:\nNot included in the standard product - delivered as a service.\nS3D native project data\nPublish to AIM\nPublish to AVEVA Asset Information Management \u2013 Hull & Outfitting.\nEIWM and ZGL/XGL\nTransfer to AVEVA Marine\nTransfer the hull basic design model to AVEVA Marine 12 series \u2013 Hull only.\nSchema file + native DB transfer\nExport Hull Steel XML\nExport hull design model as XML to third party software - Hull only.\nXML\nNote:\nNot included in the standard product - delivered as a service.\n\n\n\nFeature\nPurpose\nInput Formats\nE3D Design Format\nFeature\nPurpose\nExport Formats\nNote:"}
{"Headers": "Plant & Marine 2D Drawing Features", "Content": "The following outlines the 2D drawing import features which are applicable to process plant and marine shipbuilding projects.\nFeature\nPurpose\nInput Formats\nE3D Design Format\nDWG / DXF\nImport 2D drawings, backing sheets and symbol templates\nDWG / DXF\nNative E3D Draw format\nImage files\nBitmap images can be added to drawings by Copy/Paste\nBitmap\nBitmap embedded in drawing\nMS Excel\nAdd Excel tables etc to drawings\nMS Excel file\nImage of excel file embedded in drawing, Excel file can be opened by double click\nFeature\nPurpose\nInput Formats\nE3D Design Format\nDWG / DXF\nImport 2D drawings, backing sheets and symbol templates\nDWG / DXF\nNative E3D Draw format\nImage files\nBitmap images can be added to drawings by Copy/Paste\nBitmap\nBitmap embedded in drawing\nMS Excel\nAdd Excel tables etc to drawings\nMS Excel file\nImage of excel file embedded in drawing, Excel file can be opened by double click\nThe following outlines the 2D drawing export features which are applicable to process plant and marine shipbuilding projects.\nFeature\nPurpose\nExport Formats\nDGN Export\nExport of drawings in DGN format\nDGN\nDWG / DXF Export\nExport of drawings in DWG and DXF format\nDWG / DXF\nPDF Export\nExport of drawings in PDF format\nPDF\nSVG Export\nExport of drawings in SVG format\nSVG\nBitmap Export\nExport of drawings in a raster image format\nPNG, JPEG, IFF, BMP, GIF\nAVEVA Plot File Export (for example ISOs)\nExport of drawings in AVEVA Plot File Format \u2013 for historical compatibility only\nAVEVA Plot File\nFeature\nPurpose\nExport Formats\nDGN Export\nExport of drawings in DGN format\nDGN\nDWG / DXF Export\nExport of drawings in DWG and DXF format\nDWG / DXF\nPDF Export\nExport of drawings in PDF format\nPDF\nSVG Export\nExport of drawings in SVG format\nSVG\nBitmap Export\nExport of drawings in a raster image format\nPNG, JPEG, IFF, BMP, GIF\nAVEVA Plot File Export (for example ISOs)\nExport of drawings in AVEVA Plot File Format \u2013 for historical compatibility only\nAVEVA Plot File\n\nFeature\nPurpose\nInput Formats\nE3D Design Format\nDWG / DXF\nImport 2D drawings, backing sheets and symbol templates\nDWG / DXF\nNative E3D Draw format\nImage files\nBitmap images can be added to drawings by Copy/Paste\nBitmap\nBitmap embedded in drawing\nMS Excel\nAdd Excel tables etc to drawings\nMS Excel file\nImage of excel file embedded in drawing, Excel file can be opened by double click\nFeature\nPurpose\nExport Formats\nDGN Export\nExport of drawings in DGN format\nDGN\nDWG / DXF Export\nExport of drawings in DWG and DXF format\nDWG / DXF\nPDF Export\nExport of drawings in PDF format\nPDF\nSVG Export\nExport of drawings in SVG format\nSVG\nBitmap Export\nExport of drawings in a raster image format\nPNG, JPEG, IFF, BMP, GIF\nAVEVA Plot File Export (for example ISOs)\nExport of drawings in AVEVA Plot File Format \u2013 for historical compatibility only\nAVEVA Plot File\n\n\n\nFeature\nPurpose\nInput Formats\nE3D Design Format\nFeature\nPurpose\nExport Formats"}
{"Headers": "Plant & Marine analysis interfaces", "Content": "The following outlines the analysis features applicable for process plant and marine shipbuilding projects.\nFeature\nPurpose\nCaesar II Interface\nPipe stress analysis using Caesar II\nRohr 2 Interface\nPipe stress analysis using Rohr 2\nStructural Analysis Interface\nStructural analysis using STAAD Pro\nNote:\nFor the structural discipline in plant design projects and for the outfitting steel discipline in marine shipbuilding projects\nFeature\nPurpose\nCaesar II Interface\nPipe stress analysis using Caesar II\nRohr 2 Interface\nPipe stress analysis using Rohr 2\nStructural Analysis Interface\nStructural analysis using STAAD Pro\n\nFeature\nPurpose\nCaesar II Interface\nPipe stress analysis using Caesar II\nRohr 2 Interface\nPipe stress analysis using Rohr 2\nStructural Analysis Interface\nStructural analysis using STAAD Pro\nNote:\nFor the structural discipline in plant design projects and for the outfitting steel discipline in marine shipbuilding projects\nNote:\nFor the structural discipline in plant design projects and for the outfitting steel discipline in marine shipbuilding projects\n\n\n\nFeature\nPurpose\nNote:"}
{"Headers": "Marine specific analysis interfaces", "Content": "The following outlines the analysis features which are applicable for marine shipbuilding projects only.\nFeature\nPurpose\nHull FEM Export (XML)\nExport Idealized hull structural design model to third party software ( HyperMesh) for Finite Element Analysis. (Hull only)\nOCX Export\nExport of Hull Structural 3D arrangement model for class approval in DNVGL and so on (Hull only)\nFeature\nPurpose\nHull FEM Export (XML)\nExport Idealized hull structural design model to third party software ( HyperMesh) for Finite Element Analysis. (Hull only)\nOCX Export\nExport of Hull Structural 3D arrangement model for class approval in DNVGL and so on (Hull only)\nFeature\nPurpose\nHull FEM Export (XML)\nExport Idealized hull structural design model to third party software ( HyperMesh) for Finite Element Analysis. (Hull only)\nOCX Export\nExport of Hull Structural 3D arrangement model for class approval in DNVGL and so on (Hull only)\n\n\n\nFeature\nPurpose"}
{"Headers": "Import of mechanical CAD models for singular or composite equipment items", "Content": "Use the following as guidance on the import of singular equipment items such as pumps, centrifuges, heat exchangers and so on as well as composite or more complex models such as processing modules, skids, cranes or conveyor arrangements.\n\n\n"}
{"Headers": "Control over model creation or export from source tool", "Content": "This is where the E3D Design user has control over the creation and export of the mechanical CAD models from the authoring tool, for example where mechanical equipment are designed in-house within the same company or in close collaboration with an external company.\nIf possible try to make the exported model as light-weight as possible by removing unnecessary details already in the source tool before export, or where there are export options to reduce the level of detail.\nThere is one exception to this \u2013 where it is intended to use AVEVA Model Simplification for import, as this tools typically works best with a full solid model B-Rep model. In this case it may still be good to reduce the detail level before export, but avoid using shrinkwrap or any other simplification in the source tool that will produce an inconsistent or pre-joined exported model.\nFor Autodesk Inventor specifically:\nAvoid using the function remove internal faces. This may make the model look okay when shaded and viewed from standard directions, but can break up b-rep models, making them open-shells.\nAlso see the INTERFACES_Inventor-to-E3D_BestPractices document.\nFor large or complex models, where suitable try to split it up and export / import as separate files rather than one big file. This can for example be done by area or discipline. Consider the final deliverables to help determine the original model separation.\nAs the MultiCAD Import supports a wide range of native CAD formats in parallel with more generic formats such as STEP, it is recommended to try out several options to find the transfer format that gives the best results. Tests carried out by AVEVA have indicated that using native CAD format models can often give better results than more generic STEP files.\nAvoid importing models that have been through several format conversions, as this can often reduce the fidelity of the data as well as introduce errors in the import process. It is better to consistently use models directly from the original source tool where they have been created.\nWhen using Model Simplification to import to E3D Design:\nThis function typically provides better results with B-rep solid models that are not pre-joined or shrink wrapped.\nModels may generally contain B-Rep solids, Shells (open or not water tight bodies) and faceted bodies. A higher degree of B-Rep and less faceted bodies would yield better results. Open or not water tight bodies should also be avoided if possible as these do not process very well in Model Simplification.\nThe above guidance should be considered when preparing and exporting the CAD models from the source authoring tool. However, the results may vary depending on model properties and with different file formats, so we recommend trying different approaches to find the best option for your use case.\nIf possible try to make the exported model as light-weight as possible by removing unnecessary details already in the source tool before export, or where there are export options to reduce the level of detail.\nThere is one exception to this \u2013 where it is intended to use AVEVA Model Simplification for import, as this tools typically works best with a full solid model B-Rep model. In this case it may still be good to reduce the detail level before export, but avoid using shrinkwrap or any other simplification in the source tool that will produce an inconsistent or pre-joined exported model.\nFor Autodesk Inventor specifically:\nAvoid using the function remove internal faces. This may make the model look okay when shaded and viewed from standard directions, but can break up b-rep models, making them open-shells.\nAlso see the INTERFACES_Inventor-to-E3D_BestPractices document.\nIf possible try to make the exported model as light-weight as possible by removing unnecessary details already in the source tool before export, or where there are export options to reduce the level of detail.\nFor large or complex models, where suitable try to split it up and export / import as separate files rather than one big file. This can for example be done by area or discipline. Consider the final deliverables to help determine the original model separation.\nFor large or complex models, where suitable try to split it up and export / import as separate files rather than one big file. This can for example be done by area or discipline. Consider the final deliverables to help determine the original model separation.\nAs the MultiCAD Import supports a wide range of native CAD formats in parallel with more generic formats such as STEP, it is recommended to try out several options to find the transfer format that gives the best results. Tests carried out by AVEVA have indicated that using native CAD format models can often give better results than more generic STEP files.\nAs the MultiCAD Import supports a wide range of native CAD formats in parallel with more generic formats such as STEP, it is recommended to try out several options to find the transfer format that gives the best results. Tests carried out by AVEVA have indicated that using native CAD format models can often give better results than more generic STEP files.\nAvoid importing models that have been through several format conversions, as this can often reduce the fidelity of the data as well as introduce errors in the import process. It is better to consistently use models directly from the original source tool where they have been created.\nAvoid importing models that have been through several format conversions, as this can often reduce the fidelity of the data as well as introduce errors in the import process. It is better to consistently use models directly from the original source tool where they have been created.\nWhen using Model Simplification to import to E3D Design:\nThis function typically provides better results with B-rep solid models that are not pre-joined or shrink wrapped.\nModels may generally contain B-Rep solids, Shells (open or not water tight bodies) and faceted bodies. A higher degree of B-Rep and less faceted bodies would yield better results. Open or not water tight bodies should also be avoided if possible as these do not process very well in Model Simplification.\nWhen using Model Simplification to import to E3D Design:\nThe above guidance should be considered when preparing and exporting the CAD models from the source authoring tool. However, the results may vary depending on model properties and with different file formats, so we recommend trying different approaches to find the best option for your use case.\nThe above guidance should be considered when preparing and exporting the CAD models from the source authoring tool. However, the results may vary depending on model properties and with different file formats, so we recommend trying different approaches to find the best option for your use case.\nNotes:\nThe Model Simplification feature is based on CADFix PPS from ITI. ITI also offers an interactive version of this tool, allowing more detailed analysis of models to be simplified. The image displayed shows an example of a model with a lot of red icons in the Model Tree.\nThese red icons indicate open, non-watertight bodies that are not possible to simplify, and will explain why this model does not simplify very much. As mentioned above, AVEVA recommends customers to obtain models suitable for simplification containing watertight closed bodies only.\n\n\n\nAutodesk Inventor\nremove internal faces\nMultiCAD Import\nNotes:"}
{"Headers": "No control over model creation or export from source tool", "Content": "This is where the E3D Design user does not have control over the creation and export of the mechanical CAD model, for example where existing STP files are to be imported, or where files have been received from a vendor or company where it is not possible to impact the creation or export of the model.\nFor any model files larger than around 10MB or so, please consider using the Model Simplification tool. This has the potential to significantly reduce the size and complexity of the imported model, thereby improving the performance when using add-to-drawlist and related features in E3D Design.\n\n\n"}
{"Headers": "Alternative approaches", "Content": "For some situations and use cases, rather than importing CAD model files it could be considered to instead create parametric equipment templates directly in E3D Design, and then instantiate these according to actual dimensions.\n\n\n"}
{"Headers": "Import of 3D plant design models", "Content": "Use the following as guidance on the import of 3D plant design models. These can be for entire plant layout models, or parts of such models including equipment items, piping, structure, cableways and so on used in conjunction with additional plant modelling to be done in E3D Design.\nFor example where a plant has originally been designed with a different or legacy design tool, and users want to include this for reference while adding a new plant unit or extension in E3D Design. Or where buildings have been designed in an architectural design tool.\n\n\n"}
{"Headers": "No control over model creation or export from source tool", "Content": "This case is where the E3D Design user does not have control over the creation and export of the mechanical CAD model, for example where the original project data and design tool is no longer available, and only an export data set exists in a format that can be imported by E3D Design.\nNo specific recommendations, other than trying to achieve control over how models are created or exported from the source tools\nModel Simplification will typically not work for big plant models due to scalability issues.\nNo specific recommendations, other than trying to achieve control over how models are created or exported from the source tools\nNo specific recommendations, other than trying to achieve control over how models are created or exported from the source tools\nModel Simplification will typically not work for big plant models due to scalability issues.\nModel Simplification will typically not work for big plant models due to scalability issues.\n\n\n"}
{"Headers": "Import of mechanical CAD and plant design models", "Content": "Use the following as guidance on the import of mechanical CAD and plant design models.\n\n\n"}
{"Headers": "Converted models", "Content": "Apart from model size, the quality of the file to be imported is also of importance. CAD files that have been through several format conversions or version upgrades before attempting to import to E3D Design can not be expected to import without problems. Such conversions may in many cases degrade the data quality and cause import errors, geometrical misrepresentations and degraded performance.\nFor this reason it is highly recommended to always obtain CAD files straight from the authoring tool and avoid any fomat conversions or version upgrades.\n\n\n"}
{"Headers": "Behavior of imported models \u2013 geometry & modelling", "Content": "It is important to be aware that imported models are built up of different kinds of geometrical definition to those that have been natively created in E3D Design. Because of this, the application behavior may be different and the ability to modify the imported models in E3D Design will be limited.\n\n\n"}
{"Headers": "General", "Content": "Most of the general 3D model capabilities of E3D Design works just as well with imported models as with models that have been natively created withing E3D Design. These include clash checking, picking, dimensioning and so on.\nHowever, one difference between natively modelled and imported equipment is that the imported equipment will be represented by General Primitive (GENPRI) elements rather than boxes, cylinders ans so on. The GENPRI elements can be individually moved and rotated, but not scaled or modified in any other way that the native primitives can be.\nModelling activities for placing equipment on structural foundations and connecting pipes and cables heavily rely on snapping to P-Points and P-Lines as well as graphical snapping. Imported models will not have any P-Points or P-Lines, but the graphical snapping can still be used. However, many GENPRI elements from imported CAD models may have curves and details making it more difficult to find a distinct point to snap to, than with natively modelled equipment objects.\n\n\n"}
{"Headers": "Use of graphical explorer", "Content": "In projects were many or large and detailed CAD models have been imported, it may affect the overall performance of E3D Design. For this case it is recommended to only bring in the necessary parts of the 3D model into the view while working.\nTo view the entire project model or a larger section of it, AVEVA recommends using the Graphical Explorer which provides superior performance for large model viewing.\n\n\n"}
{"Headers": "Piping", "Content": "To be able to connect pipes to imported equipment items it is required to manually add nozzles. In many cases the geometrical representation of the nozzles are part of the imported model, but as these are not intelligent objectes, pipes can not be connected.\nDepending on the object structure of the imported model, the nozzle geometry may be represented as a separate GENPRI. In that case this GENPRI can be deleted and replaced by a native / intelligent nozzle.\nIf the nozzle is not represented by a separate GENPRI, then deleting this may remove too much of the imported model and it may have to be left in place. For this case the native nozzle can be modelled as superimposed on top of the imported nozzle geometry.\n\n\n"}
{"Headers": "Structural", "Content": "To place equipment relative to existing steelwork, or to model new steelwork in relation to equipment items, the structural application relies on grips obtained by snapping. As mentioned above, the GENPRI allows graphical snapping to be done even if it sometimes can be difficult find an ideal snapping point on curved and detailed primitives.\n\n\n"}
{"Headers": "Metadata", "Content": "AVEVA tries to conserve any metadata during imports where possible, but depending on the file format and tool used for import, some metadata may not be carried through the import process.\nFor such cases, we recommend to try and export the metadata separately from the source application, and import it into E3D Design using Excel Import.\nWhere AVEVA Engineering is being used it can also be considered to import the data there as this product has more possibilities for organizing and managing attribute data than E3D Design.\n\n\n"}
{"Headers": "Import of STEP, STL, IGS files and native mechanical CAD formats", "Content": "The Mechanical Equipment Interface (MEI) feature has long been available in E3D Design for import of STEP files.\nWith the release of E3D Design 3.1.4, a new feature called MultiCAD Import was introduced. This feature covers a wide range of native CAD formats, and is in many cases more efficient than MEI in terms of time taken to import the models as well as the efficiency of imported CAD models, for Add-to-Drawlist time and so on.\nIt is recommended to use the MultiCAD Import for this scenario, and AVEVA intends to fully replace MEI with MultiCAD over time and then deprecate the MEI Import function.\nWhile MutiCAD Inport works well for relatively small or medium-sized models, it is recommended to use Model Simplification for larger models to improve performance of the imported model. Please refer to Model Size and scalability for more information.\nFor the moment, the MEI Import is able to create native E3D Design nozzles which MultiCAD Import is not. AVEVA intends to cover this gap in MultiCAD Import over time. Until then, for cases where nozzle creation is of particular importance, MEI can be used.\n\n\n\nModel Size and scalability"}
{"Headers": "MEI Import: STEP files", "Content": "When using the MEI Import, you will typically get the most performant models by enabling the Save facet data option, and setting the Tolerance to the same value as the Arc Tolerance in Drawlist Graphics Settings, by default 1mm.\nMEI imports one level of any assembly hierarchy, names the E3D Design elements created, imports curved elements as E3D Design GENPRI elements but does not import metadata.\n\n\n\nSave facet data"}
{"Headers": "STL and IGS files", "Content": "For a general import of STL and IGS files AVEVA recommend the use of MultiCAD import. Import of STL files attempts to recognize simple primitives from STL facets and if successful can produce usable models, but in many cases produces less efficient E3D Design models where it will be better to select a different file format if possible\nThe Terrain import continues to use the MEI import for these file types.\nFor a general import of STL and IGS files AVEVA recommend the use of MultiCAD import. Import of STL files attempts to recognize simple primitives from STL facets and if successful can produce usable models, but in many cases produces less efficient E3D Design models where it will be better to select a different file format if possible\nFor a general import of STL and IGS files AVEVA recommend the use of MultiCAD import. Import of STL files attempts to recognize simple primitives from STL facets and if successful can produce usable models, but in many cases produces less efficient E3D Design models where it will be better to select a different file format if possible\nThe Terrain import continues to use the MEI import for these file types.\nThe Terrain import continues to use the MEI import for these file types.\n\n\n"}
{"Headers": "Model simplification", "Content": "Managing the import process - it is recommended to have a separate DESI DB for importing CAD models, which is not part of the regular project MDB\u2019s for users.\nModels can then be imported to this DB with different Model Simplification settings together with a fully detailed model using the MultiCAD Import, and then checks to assess the simplification results with regards to visual fidelity/preservation of necessary details against the performance to find the right balance.\nIt is then also possible to manually adjust the imported models, for example to copy SUBE or GENPRI from the fully detailed import to the simplified model where any important details have gone missing in the simplification process. Or to delete some complex geometry and manually replace by a box.\nOnce a suitable level-of-detail has been found, the model can then be copied into the real project DESI DB.\nRefer to the recommendations detailed in Control over model creation or export from source tool on how to obtain models most suitable for simplification.\n\n\n\nControl over model creation or export from source tool"}
{"Headers": "Import of DGN files", "Content": "AVEVA E3D Design includes a legacy DGN file format import feature. However, support for DGN format is expected to arrive in an upcoming version of Hoops Exchange, which will enable the MultiCAD Import feature to also support this format.\nOnce available, AVEVA will evaluate the new options and create guidelines based on the results.\n\n\n"}
{"Headers": "Import from/export to structural design", "Content": "Use the following as guidance on the import from and export to structural design.\n\n\n"}
{"Headers": "Import of IFC files", "Content": "For importing IFC Files, there are two different import tools that can be used. Depending on the type of model to be imported and its properties, as well as the requirements and desired results, either of these functions may work best.\nIFC Import\nMultiCAD Import\nTransfering models from Autodesk Revit\nThis is normally the best tool for importing a significant IFC Model\nThe IFC Explorer has extra facilities to handle elements of IFC classes groups and layers, and it always imports to an E3D Design Zone and stores repeated IFC property sets efficiently. In case the project requirements for IFC navigation are different than what the IFC Explorer provides then it is possible to configure an alternative flexible explorer for this purpose Sample Addin FlexibleExplorerAddin (aveva.com).\nFor cases where the requirements that go beyond the capabilities of the standard IFC Import process, there is an opportunity to customise the process by using PML Objects. For more information refer to How to customise ifc import and export processes (aveva.com).\nThis is normally the best tool for importing a significant IFC Model\nThis is normally the best tool for importing a significant IFC Model\nThe IFC Explorer has extra facilities to handle elements of IFC classes groups and layers, and it always imports to an E3D Design Zone and stores repeated IFC property sets efficiently. In case the project requirements for IFC navigation are different than what the IFC Explorer provides then it is possible to configure an alternative flexible explorer for this purpose Sample Addin FlexibleExplorerAddin (aveva.com).\nThe IFC Explorer has extra facilities to handle elements of IFC classes groups and layers, and it always imports to an E3D Design Zone and stores repeated IFC property sets efficiently. In case the project requirements for IFC navigation are different than what the IFC Explorer provides then it is possible to configure an alternative flexible explorer for this purpose Sample Addin FlexibleExplorerAddin (aveva.com).\nFor cases where the requirements that go beyond the capabilities of the standard IFC Import process, there is an opportunity to customise the process by using PML Objects. For more information refer to How to customise ifc import and export processes (aveva.com).\nFor cases where the requirements that go beyond the capabilities of the standard IFC Import process, there is an opportunity to customise the process by using PML Objects. For more information refer to How to customise ifc import and export processes (aveva.com).\nThe MultiCAD Import also offers an option to import IFC files which can be tried where the regular IFC Import does not provide the desired results\nThe MultiCAD Explorer does not have IFC specific groupings but can import to lower level elements, for example EQUI. The MultiCAD Import may therefore work better for importing for importing components rather than whole buildings\nFor 32bit versions of E3D Design, the MultiCAD Import can potentially import somewhat larger IFC files.\nThe MultiCAD Import also offers an option to import IFC files which can be tried where the regular IFC Import does not provide the desired results\nThe MultiCAD Import also offers an option to import IFC files which can be tried where the regular IFC Import does not provide the desired results\nThe MultiCAD Explorer does not have IFC specific groupings but can import to lower level elements, for example EQUI. The MultiCAD Import may therefore work better for importing for importing components rather than whole buildings\nThe MultiCAD Explorer does not have IFC specific groupings but can import to lower level elements, for example EQUI. The MultiCAD Import may therefore work better for importing for importing components rather than whole buildings\nFor 32bit versions of E3D Design, the MultiCAD Import can potentially import somewhat larger IFC files.\nFor 32bit versions of E3D Design, the MultiCAD Import can potentially import somewhat larger IFC files.\nFor cases where the model originates from Revit, MultiCAD Import also supports native Revit format. This might give better results than IFC depending on the model properties and requirements.\nRefer to the following documents that provide guidance on how to best prepare and export models from Revit:\nSuggested way to export model from Revit to E3D\nLimiting number of elements exported from Revit to E3D, using Revit IFC interface.\nFor cases where the model originates from Revit, MultiCAD Import also supports native Revit format. This might give better results than IFC depending on the model properties and requirements.\nFor cases where the model originates from Revit, MultiCAD Import also supports native Revit format. This might give better results than IFC depending on the model properties and requirements.\nRefer to the following documents that provide guidance on how to best prepare and export models from Revit:\nSuggested way to export model from Revit to E3D\nLimiting number of elements exported from Revit to E3D, using Revit IFC interface.\nRefer to the following documents that provide guidance on how to best prepare and export models from Revit:\n\n\n\nIFC Import\nultiCAD Import\nTransfering models from Autodesk Revit"}
{"Headers": "Export of IFC files", "Content": "There are many factors affecting the process of creating an IFC file. As a result, it is very difficult to make absolute recommendations. However, there are several things to consider that affect the file size, the time taken to export and the time taken to import into the receiving system. Refer to the IFC Export User Guide for more information.\n\n\n"}
{"Headers": "Import from TEKLA", "Content": "There are several methods available to import structural design data from TELKA. The main options are outlined as follows together with any particulars and considerations for each method.\nSDNF\nSDNF provides a way to import structural steel to E3D as intelligent elements, but has some limitations in what can be imported:\nSDNF can import Linear elements such as UB, UC and PFC, as well as planar types (flat plates but not bent plates).\nSDNF Cannot import Mechanical Items, and it can also not import Bolts or holes in linear elements. Holes in plates are possible but it depends if the source software can export them to the SDNF file.\nDuring import Linear elements can be mapped to AVEVA Catalogue elements and can be edited in E3D.\nIFC\nAnother option to import from TELKA is to use IFC which will be more complete, but the elements will not be native/editable and can only be used for referencing and coordination.\nTELKA Structures offers a number of export type options refer to for example https://telastructures.support.telka.com/2019i/en/int exporting into ifc\nAVEVA recommend the use of the Surface geometry (for IFC 2x3) or Reference view (for IFC4) options in TELKA to give the best results when the file is imported into E3D Design.\nIt is also important to do the IFC export from Tekla in a suitable scope per IFC file,(export in several smaller files than all in one big file). For example create one IFC export file for each framework in Tekla. Thus allowing the import of each file in E3D Design under different owners, which provides a more meaningful navigable hierarchy in E3D Design, and avoids getting too many members within a certain owner which could otherwise affect the performance in E3D Design, or even exceed the maximum number of members for an owner causing errors.\nThe Assembly level is stored as an AVEVA EQUI (Equipment) type and the single Part is stored as SUBE (Sub Equipment). All IFC imported elements are stored with the same Types in E3D regardless of their source application type. For example a Hole is also stored as a GENPRI under a SUBE under an EQUI.\nThere are also two DDSE (Data Sets) stored under each type, one dataset for the IFC attributes and the other for the attributes coming from the source application (Tekla). At Single part level (SUBE) again there are the two datasets and also the geometry which is stored as a GENPRI Element.\nGENPRI Elements can be moved and rotated in E3D but their geometry cannot be modified. They cannot be changed or mapped to Catalogue items.\nTEKLA also offers a bespoke interoperability feature that can be used to transfer data to E3D Design. Refer to https://support.tekla.com/doc/tekla-structures/2020/int_pdms_e3d for more information.\nNote:\nAVEVA is not able to provide more information about this option as it is developed and owned by TEKLA, but it seems that many AVEVA customers get better results using this capability than the other options of SDNF or IFC. But this may vary depending on the model data and requirements.\n\n\n\nSDNF\nIFC\nNote:"}
{"Headers": "Export to TEKLA", "Content": "Here we also have the option to use either SDNF, IFC or TELKA Interoperability, and the resulting model in TEKLA will have to be assessed to determine which method gives the best results.\n\n\n"}
{"Headers": "BOCAD and E3D Structural Design", "Content": "When importing from/exporting to BOCAD and AVEVA E3D Structural Design, the E3D Structural Design (ABSI) interface will give the best results.\n\n\n"}
{"Headers": "Use of imported models in drawings", "Content": "To get the best performance when working with model views in Draw:\nBring in the minimum needed for drawings in the draw list\nUse a suitable Hidden Line Representation (HLR)\nGlobal HLR Representation is better for larger models as it uses less resources\nGeneral wireframe mode provides better performance than hidden line. For this reason it is recommended to use the wireframe mode while arranging views and preparing the drawings, and then switch to Global Hidden Line to finalize the drawings\nThe edge representation and DUNION attribute for civil drawings works best when using the IFC Import.\nBring in the minimum needed for drawings in the draw list\nBring in the minimum needed for drawings in the draw list\nUse a suitable Hidden Line Representation (HLR)\nUse a suitable Hidden Line Representation (HLR)\nGlobal HLR Representation is better for larger models as it uses less resources\nGlobal HLR Representation is better for larger models as it uses less resources\nGeneral wireframe mode provides better performance than hidden line. For this reason it is recommended to use the wireframe mode while arranging views and preparing the drawings, and then switch to Global Hidden Line to finalize the drawings\nGeneral wireframe mode provides better performance than hidden line. For this reason it is recommended to use the wireframe mode while arranging views and preparing the drawings, and then switch to Global Hidden Line to finalize the drawings\nThe edge representation and DUNION attribute for civil drawings works best when using the IFC Import.\nThe edge representation and DUNION attribute for civil drawings works best when using the IFC Import.\n\n\n"}
{"Headers": "Flexible Mappings", "Content": "IFC Export is supplied with a sample configuration based on the APS sample Project. This mapping configuration file can be modified according to requirements using the functionality available from the Edit IFC mapping file window. Any matching element mapping based on the AVEVA E3D Design element type, and for which the AVEVA E3D Design rule is valid and evaluates to True, is selected and used for IFC Export.\nA mapping configuration file can be created, modified or deleted using the functionality available from the Edit IFC mappings file window and may be used for any number of exports.\nThe following information can also be specified:\n\nLoad a Mapping Configuration File\nModify a Mapping Configuration File\nLoad a Mapping Configuration File\nLoad a Mapping Configuration File\nModify a Mapping Configuration File\nModify a Mapping Configuration File\nWhich AVEVA E3D Design element corresponds to which IFC class.\nWhich AVEVA E3D Design elements should be excluded from IFC export.\nProperty set definitions.\nProperty mappings for each property set.\nWhether mapped but UNSET attributes should be exported.\nWhich AVEVA E3D Design element corresponds to which IFC class.\nWhich AVEVA E3D Design element corresponds to which IFC class.\nWhich AVEVA E3D Design elements should be excluded from IFC export.\nWhich AVEVA E3D Design elements should be excluded from IFC export.\nProperty set definitions.\nProperty set definitions.\nProperty mappings for each property set.\nProperty mappings for each property set.\nWhether mapped but UNSET attributes should be exported.\nWhether mapped but UNSET attributes should be exported.\nNote:\nThe mapping configuration file is validated against the mapping schema to warn the User against any error (syntax error or incorrect mapping file).\n\n\n\nLoad a Mapping Configuration File\nModify a Mapping Configuration File\nIFC Export\nEdit IFC mapping file\nTrue\nEdit\nIFC mappings file\nLoad a Mapping Configuration File\nModify a Mapping Configuration File\nUNSET\nNote\n:"}
{"Headers": "Element Mapping", "Content": "The mapping configuration file contains the information about how the data is exported to an IFC file, primarily the element types and their attributes that need to be exported.\n\nThe Export mapped unset attributes check box controls all the mapped properties that are exported to the IFC file or only those properties which have a set value in AVEVA E3D Design. By default, the check box is not checked.\nThe values exported for UNSET or empty evaluated property values are:\nProperty Value Expression Data Type\nValue used if unset\nSTRING\n\"\nINTEGER\n0\nREAL\n0.0\nLOGICAL\nFALSE\nProperty Value Expression Data Type\nValue used if unset\nSTRING\n\"\nINTEGER\n0\nREAL\n0.0\nLOGICAL\nFALSE\nThe E3D to IFC - element mappings pane of the Edit IFC mapping file window displays the E3D Elements, E3D Rules and IFC Elements (mapped elements) in the currently selected configuration mapping file.\n\nThe IFC Element column of the E3D to IFC - element mappings pane controls how the mapped AVEVA E3D Design elements are exported. Double click on the ... next to the required element in the IFC Element column to display the Pick IFC element window.\n\nSearch\nUse to search the IFC column for an IFC element.\nExport as element\nUse to select an IFC element type from the list of permitted element types for the currently selected IFC schema.\nExport as part of owner\nUse to export the geometry and attributes of the owning AVEVA E3D Design element.\nDo not export\nUse to specify that the geometry, attributes and any owned elements are not exported.\nNote:\nOnce the Do not export radio button is selected, all IFC element types are greyed out. Click OK, the entry in the IFC Element column is replaced with Exclude.\nSearch\nUse to search the IFC column for an IFC element.\nExport as element\nUse to select an IFC element type from the list of permitted element types for the currently selected IFC schema.\nExport as part of owner\nUse to export the geometry and attributes of the owning AVEVA E3D Design element.\nDo not export\nUse to specify that the geometry, attributes and any owned elements are not exported.\n\nProperty Value Expression Data Type\nValue used if unset\nSTRING\n\"\nINTEGER\n0\nREAL\n0.0\nLOGICAL\nFALSE\nSearch\nUse to search the IFC column for an IFC element.\nExport as element\nUse to select an IFC element type from the list of permitted element types for the currently selected IFC schema.\nExport as part of owner\nUse to export the geometry and attributes of the owning AVEVA E3D Design element.\nDo not export\nUse to specify that the geometry, attributes and any owned elements are not exported.\nNote:\nOnce the Do not export radio button is selected, all IFC element types are greyed out. Click OK, the entry in the IFC Element column is replaced with Exclude.\nNote:\nAny mapped property values which upon evaluation are UNSET or empty are also exported (this can also be achieved by manually editing the mapping configuration .xml file to True).\nNote:\nOnce the Do not export radio button is selected, all IFC element types are greyed out. Click OK, the entry in the IFC Element column is replaced with Exclude.\n\n\n\nExport mapped unset attributes\nNote\n:\nUNSET\nTrue\nUNSET\nProperty Value Expression Data Type\nValue used if unset\nSTRING\n\"\nINTEGER\n0\nREAL\n0.0\nLOGICAL\nFALSE\nE3D to IFC - element mappings\nEdit IFC mapping file\nE3D Elements\nE3D Rules\nIFC Elements\nIFC Element\nE3D to IFC - element mappings\n...\nIFC Element\nPick IFC element\nSearch\nExport as element\nExport as part of owner\nDo not export\nNote\n:\nDo not export\nOK\nIFC Element\nExclude"}
{"Headers": "Define AVEVA _EntityParameters PropertySet", "Content": "The AVEVA_EntityParameters PropertySet can be defined for each element mapping. A default AVEVA_EntityParameters PropertySet is applied to export each element if not defined. A Property defined in this PropertySet can be used to configure the attribute values for mapped IFC elements.\nTwo special Property can be configured to define relationship:\nThe ContainedIn property is configured to define containment relationship to the spatial structure element, to which the element is primarily associated.\nThe AggregateTo property is configured to define decomposition relationship being an aggregation. It determines that this element mapping is a part within an unordered whole/part decomposition relationship.\nThe ContainedIn property is configured to define containment relationship to the spatial structure element, to which the element is primarily associated.\nThe ContainedIn property is configured to define containment relationship to the spatial structure element, to which the element is primarily associated.\nThe AggregateTo property is configured to define decomposition relationship being an aggregation. It determines that this element mapping is a part within an unordered whole/part decomposition relationship.\nThe AggregateTo property is configured to define decomposition relationship being an aggregation. It determines that this element mapping is a part within an unordered whole/part decomposition relationship.\nNote:\nAn element mapping can only be part of a single decomposition (to allow hierarchical structures only).\nNote:\nThe supplied Sample mapping includes examples for AVEVA_EntityParameters PropertySet based on the APS Sample Project.\n\n\n\nContainedIn\nAggregateTo\nNote\n:\nNote\n:"}
{"Headers": "Create Spatial Hierarchical Mapping", "Content": "Use the Edit IFC mapping file window to define the spatial hierarchical mapping. AVEVA E3D Design elements type based on the E3DRule can be mapped to the inherited entity of IfcSpatialStructureElement.\nThe ContainedIn property can be defined as part of the AVEVA_EntityParameters Property Set to define the containment relationship to the spatial structure element.\nA ContainedIn property value is a string PML Expression that evaluates to the name of the aggregation element it is aggregated to.\nNote:\nThe supplied Sample mapping includes examples for ContainedIn property based on the APS Sample Project.\n\n\n\nEdit IFC mapping file\nIfcSpatialStructureElement\nContainedIn\nContainedIn\nNote\n:\nContainedIn"}
{"Headers": "Create a Mapping Configuration File", "Content": "\n\n\nIFC Export\nSettings\nSettings\nSettings\nBrowse for Mapping file\nSelect IFC Mapping file\nEdit Mapping File\nEdit IFC mapping file\nConfiguration name\nDescription\nSave As"}
{"Headers": "Load a Mapping Configuration File", "Content": "\n\n\nE3D to IFC Mappings\nSettings\nBrowse for mapping file\nSelect IFC Mapping file\nOpen\nE3D to IFC Mapping\nEdit Mappings file\nEdit IFC mapping file"}
{"Headers": "Modify a Mapping Configuration File", "Content": "For further information, refer to Element Mapping, Define AVEVA_EntityParameters_PropertySet, and Flexible Mapping Command Line IFC Export.\n\n\n\nLoad a Mapping Configuration File\nElement Mapping\nDefine AVEVA_EntityParameters_PropertySet\nFlexible Mapping Command Line IFC Export\nLoad a Mapping Configuration File\nSave\nElement Mapping\nDefine AVEVA_EntityParameters_PropertySet\nFlexible Mapping Command Line IFC Export"}
{"Headers": "IFC Spatial Structure", "Content": "An IFC file contains a single IfcProject container instance which is the root to which all other entities are linked.\nThere are several possible valid hierarchies of Ifc Spatial Structure instances, but the most common arrangement is:\nThe unique IfcProject usually contains (via an IfcRelAggregates instance) one or more IfcSite instances\nThe IfcSite instance(s) or the IfcProject contain (via IfcRelAggregates instance(s)) one or more IfcBuilding instances.\nThe IfcBuilding instance (s) usually contain (via IfcRelAggregates instance(s)) one or more IfcBuildingStorey instances\nIn addition IfcSite and IfcBuildingStorey instances may contain IfcSpace instances.\nThe unique IfcProject usually contains (via an IfcRelAggregates instance) one or more IfcSite instances\nThe unique IfcProject usually contains (via an IfcRelAggregates instance) one or more IfcSite instances\nThe IfcSite instance(s) or the IfcProject contain (via IfcRelAggregates instance(s)) one or more IfcBuilding instances.\nThe IfcSite instance(s) or the IfcProject contain (via IfcRelAggregates instance(s)) one or more IfcBuilding instances.\nThe IfcBuilding instance (s) usually contain (via IfcRelAggregates instance(s)) one or more IfcBuildingStorey instances\nThe IfcBuilding instance (s) usually contain (via IfcRelAggregates instance(s)) one or more IfcBuildingStorey instances\nIn addition IfcSite and IfcBuildingStorey instances may contain IfcSpace instances.\nIn addition IfcSite and IfcBuildingStorey instances may contain IfcSpace instances.\nNote:\nThis is the hierarchy supported by E3D Design IFC Export. There are several ways in which you can set up this hierarchy\n\n\n\nNote:"}
{"Headers": "Use the Default Hierarchy", "Content": "If your export mapping does not create an Ifc Spatial structure, the system will create a default one:\nAn IfcProject with name \"Default Project\"\nNo IfcSite is defined\nAn IfcBuilding with name \"SYSTEM_DEFAULT_BUILDING\" contained within the default IfcProject\nNo IfcBuilding Story or IfcSpace instances are created.\nAll Building Elements are \"spatially contained\" within that building\n(Note that some systems require an IfcSite or IfcBuildingStorey to be present in the IFC file, if this is required you must define it with one of the mapping options below).\n\n\n\n"}
{"Headers": "Map Existing E3D Elements to Spatial Entities", "Content": "Depending on how the E3D Model is structured, and which parts are to be exported to IFC, there may already be E3D elements which can be mapped to Ifc Spatial entities, and the Ifc attributes can either be defined explicitly in the mapping, or by expressions referring to E3D attributes.\nExample\nIn AREA02 of the AVEVA sample APS project, it is possible to use existing E3D elements with expressions to name the IfcSite and IfcBuildings appropriately (see example mapping ifc2x3_APS02.xml supplied with E3D Design, typically in the IFCSampleMappings folder %AVEVA_DESIGN_DFLTS%\\IFCSampleMappings)\nAn E3D Site is mapped to an IfcSite, with the name of the IfcSite extracted from the name of the E3D Site by a text expression for the value of the Name property of the AVEVA_EntityParameters property set created for it.\n\nE3D zone elements whose E3D name contains the string \u2018BUILDING\u2019 are mapped to IfcBuilding instances with an Ifc name derived from the E3D name by a text expression, and a ContainedIn property set to an expression evaluating to the Ifc name assigned to the IfcSite mapped from the owning E3D Site (property is in the AVEVA_EntityParameters property set).\n\nE3D STRU elements whose E3D name contains the string \u2018BUILDING\u2019 are mapped to IfcBuildingStorey instances with an Ifc name derived from the E3D name by a text expression, and a ContainedIn property set to an expression evaluating to the Ifc name assigned to the IfcBuilding mapped from the owning E3D Zone (property is in the AVEVA_EntityParameters property set).\nThis produces the following corresponding hierarchies when SITE-STRUCTURAL_AREA02 is exported with this mapping (a number of the E3D elements are exported to the SYSTEM_DEFAULT_SITE and the SYSATEM_DEFAULT_BUILDING, as the assumptions made in the mapping file ifc2x3_APS02.xml do not cover all the cases perfectly).\n\nNote\nThat these E3D elements must be included in the list of elements to be exported for the mappings to be processed, and that for an administrative element (for example a site or zone) to be exported it must have at least one member (an empty EQUI).\n\n\n\nNote\nExample\nName\nContainedIn\nContainedIn"}
{"Headers": "Create Special Purpose E3D Administrative Elements to Map to IFC Spatial Entities", "Content": "If the E3D elements in the project do not map naturally onto the Ifc spatial structure, it is possible to create a separate E3D Site containing dummy ZONES and EQUI for the mapping to recognise.\nThe properties of the Ifc spatial elements can be either be from data in the E3D database, or can be added in the mapping by a rule that only triggers for a single element.\nExample\nAdd an E3D SITE with four named ZONEs, each with a name, and each containing an empty unnamed EQUI:\n\nThe mapping can then have a different element mapping with a rule matching the name to create the IFC spatial elements and their ContainedIn hierarchy.\n\n\n\nOrdinary elements, for example a WALL can then be allocated to a Building storey by name, either fixed in the mapping, or by an expression.\n\nNote\nThat these E3D elements must be included in the list of elements to be exported for the mappings to be processed, and that for an administrative element (eg a site or zone) to be exported it must have at least one member (an empty EQUI).\n\n\n\nNote\nExample\nContainedIn"}
{"Headers": "Mapping Attributes and Containment of Spatial Elements", "Content": "The example expressions that follow may not apply in a user's environment (for example they may use User Defined Attributes which are not defined in the user's projects).\nIn addition to the system-required AVEVA_EntityParameters property set, other standard or custom property sets (such as Pset_BuildingCommon) can be defined as required by the receiving system or other local standards.\n\n\n"}
{"Headers": "IFCProject", "Content": "The unique IfcProject Instance cannot be configured \u2013 default attributes are used.\n\n\n"}
{"Headers": "IFCSite", "Content": "The following attributes of an IfcSite instance can be set by similarly named properties in the AVEVA_EntityParameters property set defined in the mapping.\nProperty Name\nExample Expressions\nName\n'AVEVA Example Site'\nDesc\nDescription\n:IFC_DESCRIPTION_UDA\nObject Type\nLongName\n'A sample site in Cambridge, United Kingdom'\nProperty Name\nExample Expressions\nName\n'AVEVA Example Site'\nDesc\nDescription\n:IFC_DESCRIPTION_UDA\nObject Type\n\nLongName\n'A sample site in Cambridge, United Kingdom'\n\nProperty Name\nExample Expressions\nName\n'AVEVA Example Site'\nDesc\nDescription\n:IFC_DESCRIPTION_UDA\nObject Type\nLongName\n'A sample site in Cambridge, United Kingdom'\n\n\n\nProperty Name\nExample Expressions\nName\nDescription\nObject Type\nLongName"}
{"Headers": "IFCBuilding", "Content": "The following attributes of an IfcBuilding instance can be set by similarly named properties in the AVEVA_EntityParameters property set defined in the mapping.\nProperty Name\nExample Expressions\nName\n'EV Hub'\nDescription\n|Electrical Vehicle Charging Hub|\nObjectType\nLongName\n:IFC_LONGNAME\nProperty Name\nExample Expressions\nName\n'EV Hub'\nDescription\n|Electrical Vehicle Charging Hub|\nObjectType\n\nLongName\n:IFC_LONGNAME\nThe following other properties with special meanings can also be set in the AVEVA_EntityParameters property set:\nProperty Name\nMeaning\nExample Expressions\nContainedIn\nThe (IFC) Name of an IfcSite in which the building is contained. If this is not supplied the system default IfcSite is used.\n'AVEVA Example Site'\n:IFC_CONTAINED_IN\nProperty Name\nMeaning\nExample Expressions\nContainedIn\nThe (IFC) Name of an IfcSite in which the building is contained. If this is not supplied the system default IfcSite is used.\n'AVEVA Example Site'\n:IFC_CONTAINED_IN\n\nProperty Name\nExample Expressions\nName\n'EV Hub'\nDescription\n|Electrical Vehicle Charging Hub|\nObjectType\nLongName\n:IFC_LONGNAME\nProperty Name\nMeaning\nExample Expressions\nContainedIn\nThe (IFC) Name of an IfcSite in which the building is contained. If this is not supplied the system default IfcSite is used.\n'AVEVA Example Site'\n:IFC_CONTAINED_IN\n\n\n\nProperty Name\nExample Expressions\nProperty Name\nMeaning\nExample Expressions"}
{"Headers": "IFCBuildingStorey", "Content": "The following attributes of an IfcBuildingStorey instance can be set by similarly named properties in the AVEVA_EntityParameters property set defined in the mapping.\nProperty Name\nExample Expressions\nName\n'EV Hub First Floor'\nDescription\n|Coffee Shop Floor above the Charging bays|\nObjectType\nLongName\n:IFC_LONGNAME\nElevation\n8.0m\nProperty Name\nExample Expressions\nName\n'EV Hub First Floor'\nDescription\n|Coffee Shop Floor above the Charging bays|\nObjectType\n\nLongName\n:IFC_LONGNAME\nElevation\n8.0m\nThe following other properties with special meanings can also be set in the AVEVA_EntityParameters property set.\nProperty Name\nMeaning\nExample Expressions\nContainedIn\nThe (IFC) Name of an IfcBuilding in which the building storey is contained. If this is not supplied the system default IfcBuilding is used\n'EV Hub'\n:IFC_CONTAINED_IN\nProperty Name\nMeaning\nExample Expressions\nContainedIn\nThe (IFC) Name of an IfcBuilding in which the building storey is contained. If this is not supplied the system default IfcBuilding is used\n'EV Hub'\n:IFC_CONTAINED_IN\nProperty Name\nExample Expressions\nName\n'EV Hub First Floor'\nDescription\n|Coffee Shop Floor above the Charging bays|\nObjectType\nLongName\n:IFC_LONGNAME\nElevation\n8.0m\nProperty Name\nMeaning\nExample Expressions\nContainedIn\nThe (IFC) Name of an IfcBuilding in which the building storey is contained. If this is not supplied the system default IfcBuilding is used\n'EV Hub'\n:IFC_CONTAINED_IN\n\n\n\nProperty Name\nExample Expressions\nProperty Name\nMeaning\nExample Expressions"}
{"Headers": "IFCSpace", "Content": "The following attributes of an IfcSpace instance can be set by similarly named properties in the AVEVA_EntityParameters property set defined in the mapping.\nProperty Name\nExample Expressions\nName\n'Charging Bay 15'\nDescription\nDesc\nObjectType\n|CCS/Chademo/AC EV Charger|\nLongName\n:IFC_LONGNAME\nElevationWithFlooring\n0.2m\nProperty Name\nExample Expressions\nName\n'Charging Bay 15'\nDescription\nDesc\nObjectType\n|CCS/Chademo/AC EV Charger|\nLongName\n:IFC_LONGNAME\nElevationWithFlooring\n0.2m\nThe following other properties with special meanings can also be set in the AVEVA_EntityParameters property set:\nProperty Name\nMeaning\nExample Expressions\nContainedIn\nThe (IFC) Name of an IfcBuildingStorey or IfcSite in which the space is contained.\n'EV Hub Charging Floor'\n:IFC_CONTAINED_IN\nProperty Name\nMeaning\nExample Expressions\nContainedIn\nThe (IFC) Name of an IfcBuildingStorey or IfcSite in which the space is contained.\n'EV Hub Charging Floor'\n:IFC_CONTAINED_IN\n\nProperty Name\nExample Expressions\nName\n'Charging Bay 15'\nDescription\nDesc\nObjectType\n|CCS/Chademo/AC EV Charger|\nLongName\n:IFC_LONGNAME\nElevationWithFlooring\n0.2m\nProperty Name\nMeaning\nExample Expressions\nContainedIn\nThe (IFC) Name of an IfcBuildingStorey or IfcSite in which the space is contained.\n'EV Hub Charging Floor'\n:IFC_CONTAINED_IN\n\n\n\nProperty Name\nExample Expressions\nProperty Name\nMeaning\nExample Expressions"}
{"Headers": "Mapping to IFC Non-Spatial Elements", "Content": "The IfcElement entity and classes derived from it make up most of the physical objects in an Ifc model, and are usually directly or indirectly spatially contained within an instance of an IfcSpatialStructure derived entity.\nMost mappings in a mapping configuration will therefore be element mappings, and there may be:\nMultiple mappings from the same E3D Element type(s) to different IFC Elements (controlled by the E3D rule)\nMultiple mappings to an IFC Element from different E3D elements\nMappings with an empty E3D Rule field, where the E3D element type(s) are enough to choose\nMappings with an empty E3D Elements field, where the E3D rule determines the IFC Element\nMappings with an empty IFC Element field which means Include E3D Elements of the specified types and matching any rule in the owning element \u2013 this includes geometry, and any relevant property sets\nMappings may have a special value in the IFC Element field, Exclude which means that the E3D element, and any geometry and properties and any children it has are completely excluded from the exported IFC file\nMultiple mappings from the same E3D Element type(s) to different IFC Elements (controlled by the E3D rule)\nMultiple mappings from the same E3D Element type(s) to different IFC Elements (controlled by the E3D rule)\nMultiple mappings to an IFC Element from different E3D elements\nMultiple mappings to an IFC Element from different E3D elements\nMappings with an empty E3D Rule field, where the E3D element type(s) are enough to choose\nMappings with an empty E3D Rule field, where the E3D element type(s) are enough to choose\nMappings with an empty E3D Elements field, where the E3D rule determines the IFC Element\nMappings with an empty E3D Elements field, where the E3D rule determines the IFC Element\nMappings with an empty IFC Element field which means Include E3D Elements of the specified types and matching any rule in the owning element \u2013 this includes geometry, and any relevant property sets\nMappings with an empty IFC Element field which means Include E3D Elements of the specified types and matching any rule in the owning element \u2013 this includes geometry, and any relevant property sets\nMappings may have a special value in the IFC Element field, Exclude which means that the E3D element, and any geometry and properties and any children it has are completely excluded from the exported IFC file\nMappings may have a special value in the IFC Element field, Exclude which means that the E3D element, and any geometry and properties and any children it has are completely excluded from the exported IFC file\nNote:\nThat IFC 4 added many new IFC Element types, and the examples here may use both schemas.\nNote:\nRemember that, as always, order is significant First match wins\n\n\n\nNote:\nNote:"}
{"Headers": "Example IFC Elements Selection Mappings", "Content": "The following includes examples of different ways to map E3D elements to IFC Eeements \u2013 many others are possible.\nAn element mapping has an optional list of E3D element types, and also an optional Boolean expression. In many cases only one or the other is required, but in others both are needed.\nExample\nTo distinguish between some E3D GENSEC elements which should be mapped to IfcBeam elements, and other that should be mapped to IfcColumn elements. Depending on how the structural model is defined, expressions may use text or geometric attributes such as:\nFor E3D Equipment it may well be desirable to use expressions based on full or partial text attributes, for example the complete name of the E3D element:\nSTRUCL EQ 'BEAM'\nPOSE[3] EQ POSS[3]\nPOSE[1] EQ POSS[1] AND POSE[2] EQ POSS[2]\nnamn eq 'Units-Heater'\nMATCHWILD(Namn,'*METER*')\nMATCHWILD(Desc,'*Pump*')\nMATCHWILD(Namn,'*CONNECTION_BOX*') OR MATCHWILD(Namn,'ELECTRIC_JB_*')\n:EQUI_SUB_GROUP eq 'Space Heater'\n:EXPECTED_IFC_CLASS EQ 'IFCFLOWTERMINAL'\n( TYPE OF OWNER EQ 'BRAN' ) \n( TYPE OF OWNER EQ 'BRAN' ) AND ( :HEAT_SYSTEM OF PIPE ) AND ( TYPE NE 'TUBI' )\n'SUPPO' inset (AHLIST)\nNOT ( UNSET ( MEM STRFLT ) AND UNSET (MEM RLADDR ) )\n'TMPL' inset (AHLIST)\nWhat is the Structural Classification of the section?\nSTRUCL EQ 'BEAM'\nAre the Up coordinates of the two ends the same (a beam)?\nPOSE[3] EQ POSS[3]\nAre the East and North coordinates of the two ends the same (a column)?\nPOSE[1] EQ POSS[1] AND POSE[2] EQ POSS[2]\nWhat is the Structural Classification of the section?\nSTRUCL EQ 'BEAM'\nWhat is the Structural Classification of the section?\nAre the Up coordinates of the two ends the same (a beam)?\nPOSE[3] EQ POSS[3]\nAre the Up coordinates of the two ends the same (a beam)?\nAre the East and North coordinates of the two ends the same (a column)?\nPOSE[1] EQ POSS[1] AND POSE[2] EQ POSS[2]\nAre the East and North coordinates of the two ends the same (a column)?\na partial name or description:\nMATCHWILD(Namn,'*METER*')\nMATCHWILD(Desc,'*Pump*')\nMATCHWILD(Namn,'*CONNECTION_BOX*') OR MATCHWILD(Namn,'ELECTRIC_JB_*')\na UDA (these UDAs are examples, not recommendations)\n:EQUI_SUB_GROUP eq 'Space Heater'\n:EXPECTED_IFC_CLASS EQ 'IFCFLOWTERMINAL'\nFor Piping, HVAC and similar, useful expressions can include attributes of the direct or indirectly owning elements, such as any element directly owned by a BRANCH\n( TYPE OF OWNER EQ 'BRAN' ) \na combination - in this case selecting items directly owned by a branch of a pipe with a given UDA value, but excluding implicit tubing\n( TYPE OF OWNER EQ 'BRAN' ) AND ( :HEAT_SYSTEM OF PIPE ) AND ( TYPE NE 'TUBI' )\nSupports, fixtures and fittings often have deeper hierarchies, perhaps including templates, so expressions including AHLIST (the list of the types of elements above the CE) can be useful, for example to map a STRU element which is directly or indirectly below a SUPPO element to an IfcElementAssembly\n'SUPPO' inset (AHLIST)\nMap STRU, FRMW and SBFR elements which have at least one member which is a Stairflight or a RungLadder to an IfcStair\nNOT ( UNSET ( MEM STRFLT ) AND UNSET (MEM RLADDR ) )\nAHLIST is also very useful in expressions where there is no Ifc element required (the Ifc Element name is omitted \u2013 meaning that matching items should be included in the same Ifc Element as their owner, or where the special value Exclude is used, in which case geometry and attributes of the matching element should not be exported at all). For example: elements directly or indirectly below a Temple should not be exported separately.\n'TMPL' inset (AHLIST)\na partial name or description:\nMATCHWILD(Namn,'*METER*')\nMATCHWILD(Desc,'*Pump*')\nMATCHWILD(Namn,'*CONNECTION_BOX*') OR MATCHWILD(Namn,'ELECTRIC_JB_*')\na partial name or description:\na UDA (these UDAs are examples, not recommendations)\n:EQUI_SUB_GROUP eq 'Space Heater'\n:EXPECTED_IFC_CLASS EQ 'IFCFLOWTERMINAL'\na UDA (these UDAs are examples, not recommendations)\nFor Piping, HVAC and similar, useful expressions can include attributes of the direct or indirectly owning elements, such as any element directly owned by a BRANCH\n( TYPE OF OWNER EQ 'BRAN' ) \nFor Piping, HVAC and similar, useful expressions can include attributes of the direct or indirectly owning elements, such as any element directly owned by a BRANCH\na combination - in this case selecting items directly owned by a branch of a pipe with a given UDA value, but excluding implicit tubing\n( TYPE OF OWNER EQ 'BRAN' ) AND ( :HEAT_SYSTEM OF PIPE ) AND ( TYPE NE 'TUBI' )\na combination - in this case selecting items directly owned by a branch of a pipe with a given UDA value, but excluding implicit tubing\nSupports, fixtures and fittings often have deeper hierarchies, perhaps including templates, so expressions including AHLIST (the list of the types of elements above the CE) can be useful, for example to map a STRU element which is directly or indirectly below a SUPPO element to an IfcElementAssembly\n'SUPPO' inset (AHLIST)\nSupports, fixtures and fittings often have deeper hierarchies, perhaps including templates, so expressions including AHLIST (the list of the types of elements above the CE) can be useful, for example to map a STRU element which is directly or indirectly below a SUPPO element to an IfcElementAssembly\nMap STRU, FRMW and SBFR elements which have at least one member which is a Stairflight or a RungLadder to an IfcStair\nNOT ( UNSET ( MEM STRFLT ) AND UNSET (MEM RLADDR ) )\nMap STRU, FRMW and SBFR elements which have at least one member which is a Stairflight or a RungLadder to an IfcStair\nAHLIST is also very useful in expressions where there is no Ifc element required (the Ifc Element name is omitted \u2013 meaning that matching items should be included in the same Ifc Element as their owner, or where the special value Exclude is used, in which case geometry and attributes of the matching element should not be exported at all). For example: elements directly or indirectly below a Temple should not be exported separately.\n'TMPL' inset (AHLIST)\nAHLIST is also very useful in expressions where there is no Ifc element required (the Ifc Element name is omitted \u2013 meaning that matching items should be included in the same Ifc Element as their owner, or where the special value Exclude is used, in which case geometry and attributes of the matching element should not be exported at all). For example: elements directly or indirectly below a Temple should not be exported separately.\n\n\n"}
{"Headers": "Properties and Attributes", "Content": "The following describes guidance o n and examples of AVEVA properties and attributes used during IFC Export.\n\n\n"}
{"Headers": "AVEVA_EntityParameters Property Set", "Content": "A Property set named AVEVA_EntityParameters may be attached to each element mapping and is used to control a number of the values of attributes of and relationships between Ifc entities in the generated IFC file.\nThe property set is itself exported to the IFC file, and this can be useful when debugging mappings, to check that the values of the expressions are what was expected. Some of the properties in these property sets are automatically generated with default value expressions, but if the user chooses to supply own expression, which will be used instead of the default expression.\nHere are the properties that can be added to the AVEVA_EntityParameters property set which have special meanings.\nName of the Property\nDefault Expression\nMeaning\nEntity\nThis property is used to transfer the IFC Entity name eg IFCBEAM. It should not be overridden.\nUUID\nIFCUID\nThis property is used to transfer the GlobalId attribute. It should not normally be overridden.\nName\nFLNN\nThis becomes the Name attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Name\nDescription\nDESC\nThis becomes the Description attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Desc.\nObjectType\nNAMN OF SPREF\nThis becomes the ObjectType attribute of the IFC Entity. It can be overridden.\nTag\nREFNO\nThis becomes the Tag attribute of the IFC Entity. It can be overridden.\nE3DType\nFULL\nThis is the E3D Element type of the E3D element. This is not otherwise used in the IFC files, but is included to aid understanding of the mapping.\nContainedIn\nThis property is used to define the Spatial hierarchy of the IFC element. It can be set both on Spatial elements (such as an IfcBuildingStorey \u2013 where it should be set to the Ifc name attribute of the containing IfcBuilding), and also on Ifc elements which are spatially contained within an Ifc spatial element.\nIn all case the expression should evaluate to a string which is the Ifc name of the containing element. If no suitable element with that name exists, an IfcBuilding is created.\nAggregateTo\nThis property is used for elements that for part of another non-spatial element such as an IfcAssembly.The expression should evaluate to a string which is the Ifc name of the aggregating element.\nNote:\nThat if AggregateTo has priority over ContainedIn. If an element has both AggregateTo and ContainedIn expressions defined, and the AggregateTo expression evaluates to a non-empty string, then ContainedIn is ignored. (Spatial containment is then managed at the aggregating element).\nLayer\nRefer to Presentation Layers\nSystem\nRefer to Systems\nMaterial\nRefer to Materials\nName of the Property\nDefault Expression\nMeaning\nEntity\n\nThis property is used to transfer the IFC Entity name eg IFCBEAM. It should not be overridden.\nUUID\nIFCUID\nThis property is used to transfer the GlobalId attribute. It should not normally be overridden.\nName\nFLNN\nThis becomes the Name attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Name\nDescription\nDESC\nThis becomes the Description attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Desc.\nObjectType\nNAMN OF SPREF\nThis becomes the ObjectType attribute of the IFC Entity. It can be overridden.\nTag\nREFNO\nThis becomes the Tag attribute of the IFC Entity. It can be overridden.\nE3DType\nFULL\nThis is the E3D Element type of the E3D element. This is not otherwise used in the IFC files, but is included to aid understanding of the mapping.\nContainedIn\n\nThis property is used to define the Spatial hierarchy of the IFC element. It can be set both on Spatial elements (such as an IfcBuildingStorey \u2013 where it should be set to the Ifc name attribute of the containing IfcBuilding), and also on Ifc elements which are spatially contained within an Ifc spatial element.\nIn all case the expression should evaluate to a string which is the Ifc name of the containing element. If no suitable element with that name exists, an IfcBuilding is created.\nAggregateTo\n\nThis property is used for elements that for part of another non-spatial element such as an IfcAssembly.The expression should evaluate to a string which is the Ifc name of the aggregating element.\nLayer\n\nRefer to Presentation Layers\nSystem\n\nRefer to Systems\nMaterial\n\nRefer to Materials\nName of the Property\nDefault Expression\nMeaning\nEntity\nThis property is used to transfer the IFC Entity name eg IFCBEAM. It should not be overridden.\nUUID\nIFCUID\nThis property is used to transfer the GlobalId attribute. It should not normally be overridden.\nName\nFLNN\nThis becomes the Name attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Name\nDescription\nDESC\nThis becomes the Description attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Desc.\nObjectType\nNAMN OF SPREF\nThis becomes the ObjectType attribute of the IFC Entity. It can be overridden.\nTag\nREFNO\nThis becomes the Tag attribute of the IFC Entity. It can be overridden.\nE3DType\nFULL\nThis is the E3D Element type of the E3D element. This is not otherwise used in the IFC files, but is included to aid understanding of the mapping.\nContainedIn\nThis property is used to define the Spatial hierarchy of the IFC element. It can be set both on Spatial elements (such as an IfcBuildingStorey \u2013 where it should be set to the Ifc name attribute of the containing IfcBuilding), and also on Ifc elements which are spatially contained within an Ifc spatial element.\nIn all case the expression should evaluate to a string which is the Ifc name of the containing element. If no suitable element with that name exists, an IfcBuilding is created.\nAggregateTo\nThis property is used for elements that for part of another non-spatial element such as an IfcAssembly.The expression should evaluate to a string which is the Ifc name of the aggregating element.\nNote:\nThat if AggregateTo has priority over ContainedIn. If an element has both AggregateTo and ContainedIn expressions defined, and the AggregateTo expression evaluates to a non-empty string, then ContainedIn is ignored. (Spatial containment is then managed at the aggregating element).\nLayer\nRefer to Presentation Layers\nSystem\nRefer to Systems\nMaterial\nRefer to Materials\nNote:\nThat if AggregateTo has priority over ContainedIn. If an element has both AggregateTo and ContainedIn expressions defined, and the AggregateTo expression evaluates to a non-empty string, then ContainedIn is ignored. (Spatial containment is then managed at the aggregating element).\nNote:\nExtra properties can be set with the same name as an attribute of the IFC element being created. For example IfcSpatialElement-derived elements, such as IfcBuilding, have a LongName attribute, and this can be set to a literal string or an expression by defining a LongName property in the AVEVA_EntityParameters property set.\n\n\n\nName of the Property\nDefault Expression\nMeaning\nNote:\nNote:"}
{"Headers": "Automatic Property Sets", "Content": "The automatic property sets generated for all E3D attributes (either all attributes with a value, or all including unset attributes), have been available since the first release of IFC Export.\nIf you are providing a full mapping, you will probably not need to export these sets, but will chose to export \"None\":\n\nThis does not top the export of AVEVA_EntityParameters, or and other property sets defined in the mapping.\n\n\n"}
{"Headers": "Standard and User Defined Property Sets", "Content": "It is possible to attach standard or other custom property sets to IFC instances, for example\n\nThis example uses several expression types, and the units of the expression result are applied to the Ifc property value. In addition, the @@IFCPOSITIVERATIOMEASURE in the Desc column in an example of an explicit type-override to control\nIf the expression returns a list of values, then an IfcPropertyListValue will be exported, otherwise an IfcPropertySingleValue.\n\n\n"}
{"Headers": "Data Types and Units for Properties", "Content": "The datatype of the IfcProperty NominalValue, is where possible, chosen automatically from the data type of the E3D expression used to create it, where that type is refer to the table.\nE3D Type\nIFC Measure\nUnits\nDistance\nIfcLengthMeasure\nmillimetre\nBore\nIfcLengthMeasure\nmillimetre\nArea\nIfcAreaMeasure\nsquare metre\nVolume\nIfcVolumeMeasure\ncubic metre\nAngle\nIfcPlaneAngleMeasure\nradian\nMass\nIfcMassMeasure\nkilogram\nPressure\nIfcPressureMeasure\npascal\nCurrent\nIfcElectricCurrentMeasure\nampere\nSpeed\nIfcLinearVelocityMeasure\nmetre/second\nPower\nIfcPowerMeasure\nkilowatt\nTorque\nIfcTorqueMeasure\nnewton metre\nVolumetric Flow\nIfcVolumetricFlowRateMeasure\ncubic metre/second\nDensity\nIfcMassDensityMeasure\nkilogram/cubic metre\nForce\nIfcForceMeasure\nnewton\nTemperature\nIfcTherodynamicTemperatureMeasure\nkelvin\nEMF\nIfcElectricVoltageMeasure\nvolt\nE3D Type\nIFC Measure\nUnits\nDistance\nIfcLengthMeasure\nmillimetre\nBore\nIfcLengthMeasure\nmillimetre\nArea\nIfcAreaMeasure\nsquare metre\nVolume\nIfcVolumeMeasure\ncubic metre\nAngle\nIfcPlaneAngleMeasure\nradian\nMass\nIfcMassMeasure\nkilogram\nPressure\nIfcPressureMeasure\npascal\nCurrent\nIfcElectricCurrentMeasure\nampere\nSpeed\nIfcLinearVelocityMeasure\nmetre/second\nPower\nIfcPowerMeasure\nkilowatt\nTorque\nIfcTorqueMeasure\nnewton metre\nVolumetric Flow\nIfcVolumetricFlowRateMeasure\ncubic metre/second\nDensity\nIfcMassDensityMeasure\nkilogram/cubic metre\nForce\nIfcForceMeasure\nnewton\nTemperature\nIfcTherodynamicTemperatureMeasure\nkelvin\nEMF\nIfcElectricVoltageMeasure\nvolt\nThe following Unitless values are supported:\nIn addition to the above lists , it is possible to specify the following measure types by reserved values in the Desc column of the property definition.\nDescription Keyword\nIfc Measure\nUnderlying Type\n@@IFCIDENTIFIER\nIfcIdentifier\nText\n@@IFCPOSITIVERATIOMEASURE\nIfcPositiveRatioMeasure\nNumeric\n@@IFCPOSITIVELENGTHMEASURE\nIfcPositiveLengthMeasure\nLength\nDescription Keyword\nIfc Measure\nUnderlying Type\n@@IFCIDENTIFIER\nIfcIdentifier\nText\n@@IFCPOSITIVERATIOMEASURE\nIfcPositiveRatioMeasure\nNumeric\n@@IFCPOSITIVELENGTHMEASURE\nIfcPositiveLengthMeasure\nLength\nE3D Type\nIFC Measure\nUnits\nDistance\nIfcLengthMeasure\nmillimetre\nBore\nIfcLengthMeasure\nmillimetre\nArea\nIfcAreaMeasure\nsquare metre\nVolume\nIfcVolumeMeasure\ncubic metre\nAngle\nIfcPlaneAngleMeasure\nradian\nMass\nIfcMassMeasure\nkilogram\nPressure\nIfcPressureMeasure\npascal\nCurrent\nIfcElectricCurrentMeasure\nampere\nSpeed\nIfcLinearVelocityMeasure\nmetre/second\nPower\nIfcPowerMeasure\nkilowatt\nTorque\nIfcTorqueMeasure\nnewton metre\nVolumetric Flow\nIfcVolumetricFlowRateMeasure\ncubic metre/second\nDensity\nIfcMassDensityMeasure\nkilogram/cubic metre\nForce\nIfcForceMeasure\nnewton\nTemperature\nIfcTherodynamicTemperatureMeasure\nkelvin\nEMF\nIfcElectricVoltageMeasure\nvolt\nDescription Keyword\nIfc Measure\nUnderlying Type\n@@IFCIDENTIFIER\nIfcIdentifier\nText\n@@IFCPOSITIVERATIOMEASURE\nIfcPositiveRatioMeasure\nNumeric\n@@IFCPOSITIVELENGTHMEASURE\nIfcPositiveLengthMeasure\nLength\nIfcText\nIfcReal\nIfcInteger\nIfcLogical\nIfcText\nIfcText\nIfcReal\nIfcReal\nIfcInteger\nIfcInteger\nIfcLogical\nIfcLogical\nNote:\nThat restrictions on values (eg ensuring that a positive length measure is greater than zero) are not implemented.Future releases may increase the range of measures supported.\n\n\n\nE3D Type\nIFC Measure\nUnits\nDescription Keyword\nIfc Measure\nUnderlying Type\nNote:"}
{"Headers": "Other IFC Relationships", "Content": "The following describes other IFC relationships.\n\n\n"}
{"Headers": "IFC Import", "Content": "The IFC Import User Interface (IFC Import) enables the processing of .IFC files in AVEVA Everything3D, the available functionality is the default.\n\n\n\n\n\n\n\n\n\n\n\n"}
{"Headers": "IFC Import Window", "Content": "The IFC Import window is displayed as a dockable window, initially docked at the right-hand side of the screen.\n\nFor further information, refer to Source, Destination, Settings, Logging, Import Using the Command Line, IFC Flexible Explorer.\n\n\n\nSource\nDestination\nSettings\nLogging\nImport Using the Command Line\nIFC Flexible Explorer\nIFC Import\nSource\nDestination\nSettings\nLogging\nImport Using the Command Line\nIFC Flexible Explorer"}
{"Headers": "Source", "Content": "Defines the details of the source data of the imported model.\n\nWhen an import transaction is completed and the IFC Import window is closed, the window settings are saved to a default file in the AVEVA_DESIGN_USER directory. The file is named ifcimport.impsav. When the IFC Import window is re-invoked, the System searches for this file and restores all but one of the IFC Import window values at the time of closing the IFC Import window.\nAll of the IFC Import window settings can be saved to a file, and reloaded into the IFC Import window.\nLoad:\nUse a file browser to select a previously created file to populate the IFC Import window fields. On loading a settings file, all the fields are repopulated except the field defining the import site destination. This makes sure that the import location is stated.\nReset:\nClears all fields and sets them to the System default values.\nImports a single .IFC file or a folder containing a set of IFC files as the import source (the default is File).\n\nEnter the file name/folder path or browse to locate the required file or folder.\nOnce the source data has been correctly defined, click Next to proceed to the Destination window.\nFor further information, refer to Destination, Settings, and Logging.\n\n\n\nDestination\nSettings\nLogging\nIFC Import\nIFC Import\nIFC Import\nIFC Import\nIFC Import\nIFC Import\nLoad:\nIFC Import\nReset:\nSource File or Folder\nFile\nNext\nDestination\nDestination\nSettings\nLogging"}
{"Headers": "Destination", "Content": "This section defines the details about the destination of the imported model. The main model is imported into the normal SITE, ZONE hierarchy.\n\nActivates a file browser which creates a file that can be used to repopulate the Import IFC window fields. The saved file is suffixed .impsav. For example:\nThe file can be used as a basis for a User-developed PML interface that can run in command line mode.\nIf required, a SITE element in the Model Explorer may be defined for the destination, specify the name of a SITE element or navigate to one and click CE.\nSpecify the name of a GPWL element or navigate to one and click CE. In order to be able to view the data in a form similar to the IFC import file, GPWL elements are created to reconstruct that hierarchy.\nBy default, IFC Import creates a GPWL element named /IFC_Import with a Function attribute set to IMPORT. Unless otherwise stated, subsequent import transactions will generate Group Set GPSET elements in that GPWL element.\nHowever, other GPWL elements can be created/chosen to receive the imported data. It is not essential to define a destination GPWL element, leaving the field blank means the default GPWL will be used.\nUse the Reference Datum part of the Destination window to select a Reference Datum from the populated list, create a Reference Datum, edit or delete an existing one. The Reference Datum is a holder for information about the transformation coordinate system, which allows the relocation of the imported model\u2019s origin and orientation.\n\nIf a Reference Datum is not required, leave the Use Reference Datum check box unselected. (By default the Use Reference Datum check box is not selected).\nUse the functionality available for selection from the Reference Datum window to name, locate and orientate the datum.\n\nFormat\nDefines the position axis using the Format drop-down lists, East/West, North/South and Up/Down. Explicit position values can be typed into the Position fields.\nOffset\nMoves an element(s) a specified distance in a specified direction, relative to its current position.\nLock\nSelect the check box to lock the specified coordinates.\nOrientation\nDefines the axes (fixed reference lines) of an element using explicit orientation values.\nEdit\nDefines the axes (fixed reference lines) of an element using explicit orientation values or the axes of an existing element. For further information, refer to Orientate.\nScale\nDisplays the current scale.\nFormat\nDefines the position axis using the Format drop-down lists, East/West, North/South and Up/Down. Explicit position values can be typed into the Position fields.\nOffset\nMoves an element(s) a specified distance in a specified direction, relative to its current position.\n\nLock\nSelect the check box to lock the specified coordinates.\nOrientation\nDefines the axes (fixed reference lines) of an element using explicit orientation values.\nEdit\nDefines the axes (fixed reference lines) of an element using explicit orientation values or the axes of an existing element. For further information, refer to Orientate.\nScale\nDisplays the current scale.\nUse the functionality available for selection from the Reference Datum window to modify the name, location and orientation of the Reference Datum.\n\nDeletes the currently selected Reference Datum. A Confirm window is displayed asking to confirm the deletion.\n\nFor further information, refer to Settings, Logging, and IFC Flexible Explorer.\nFormat\nDefines the position axis using the Format drop-down lists, East/West, North/South and Up/Down. Explicit position values can be typed into the Position fields.\nOffset\nMoves an element(s) a specified distance in a specified direction, relative to its current position.\nLock\nSelect the check box to lock the specified coordinates.\nOrientation\nDefines the axes (fixed reference lines) of an element using explicit orientation values.\nEdit\nDefines the axes (fixed reference lines) of an element using explicit orientation values or the axes of an existing element. For further information, refer to Orientate.\nScale\nDisplays the current scale.\nNote:\nThis is not necessarily the hierarchy of the source program from which the IFC import file comes.\nNote:\nAny previously set Function attribute of the User-defined GPWL element will be overwritten by IMPORT so that the GPSET element would then be viewable in the Flexible Explorer.\nNote:\nThe IFCGLOBAL Reference Datum is not modifiable (by default E0N0U0 / Y is N and Z is U). If accidentally deleted, it is regenerated.\nNote:\nThe functionality of the Reference Datum window is explained. For further information, refer to Create Reference Datum.\n\n\n\nSettings\nLogging\nIFC Flexible Explorer\nSITE\nZONE\nImport IFC\n-- IMPORT\n-- If you wish to use this as a source for your own IFCImporterObj based\n-- interface, change '!this' to the name of your export object variable.\n!this.setUserFileFolder('C:\\Users\\Public\\DOCUME~1\\AVEVA\\USERDATA\\')\n!this.setSrcFolderFlg(FALSE)\n!this.setSource('C:\\Users\\james.barrett\\Desktop\\1.ifc')\n!this.setRootDir('C:\\Users\\Public\\Documents\\AVEVA\\Projects\\E3D2.1\\AvevaPlantSample')\n!this.setDbTarget(=2013286748/50)\n!this.setRefDatumByName('IFCGLOBAL')\n!this.setScale(1)\n!this.setGroupWorld(=2013286748/47)\n!this.setRefDatumOption(TRUE)\n!this.setPrefix('')\n!this.setCacheFacets(TRUE)\n!this.setTolerance(10mm)\n!this.setBucketSize(100)\n!this.setUseBucketSize(true)\n!this.setLogFile('C:\\Users\\Public\\Documents\\AVEVA\\Projects\\E3D2.1\\AvevaPlantSample\\IFC_Export.log')\n!this.setLogDetail(2)\nSITE\nModel Explorer\nSITE\nCE\nGPWL\nCE\nGPWL\nNote\n:\nGPWL\n/IFC_Import\nFunction\nIMPORT\nGPSET\nGPWL\nGPWL\nGPWL\nGPWL\nNote\n:\nFunction\nGPWL\nIMPORT\nGPSET\nFlexible Explorer\nReference Datum\nDestination\nUse Reference Datum\nUse Reference Datum\nReference Datum\nFormat\nFormat\nEast/West\nNorth/South\nUp/Down\nPosition\nOffset\nLock\nOrientation\nEdit\nOrientate\nScale\nReference Datum\nNote\n:\nIFCGLOBAL Reference Datum\nNote\n:\nReference Datum\nConfirm\nSettings\nLogging\nIFC Flexible Explorer"}
{"Headers": "Settings", "Content": "Use the Settings window to define the settings for model import to be selected. By default (currently) the Settings window is correctly filled in and the blue tick icon is displayed and the Import functionality is available.\n\nUse the Tolerance part of the Settings window to Save Facet Data, select the Save Facet Data check box (a valid tolerance value must be entered), by default the Save Facet Data check box is not selected.\nThe default tolerance setting is that which is current in the graphics representation when the Settings window is displayed.\nUse the Storage part of the Settings window to specify the number of elements contained in each ZONE.\nSelect the Limit no. of import elements per ZONE check box. A valid number of import elements per ZONE value must be entered. By default, the Limit no. of import elements per ZONE check box is not selected.\nThe default number of import elements per ZONE setting is 100. A value of less than 25 or more than 1000 cannot be entered.\nWhen the model is imported, subsequent ZONE names are based on the name of the original ZONE.\n\nThe Naming functionality available from the Settings window, using a model prefix in the naming of the GroupSets and main model. If a prefix is not entered then the automatic naming functionality will be used based on the input file name.\nIn setting the model prefix, there maybe some tidying up and name validation required, and during the import process, there are checks to avoid duplicate names.\nBelow is the Model Explorer Group Set structures when a prefix of TestModel has been supplied.\n\nAnd here is the default situation when no prefix is given.\n\nFor further information, refer to Logging.\nNote:\nNo facet data will be saved by default.\nNote:\nIf the Save Facet Data check box is selected but no valid tolerance is entered, the orange triangle is displayed.\nNote:\nAutomatic naming can be overridden using the PML object and the userPostProcess function. In that User-developed function, it can be determined whatever post processing to undertake after the model is imported. Naming of elements is one aspect of this.\n\n\n\nLogging\nSettings\nSettings\nImport\nNote\n:\nTolerance\nSettings\nSave Facet Data\nSave Facet Data\nSave Facet Data\nNote\n:\nSave Facet Data\nSettings\nStorage\nSettings\nZONE\nLimit no. of import elements per ZONE\nZONE\nLimit no. of import elements per ZONE\nZONE\nZONE\nZONE\nNaming\nSettings\nGroupSets\nNote\n:\nuserPostProcess\nTestModel\nLogging"}
{"Headers": "Logging", "Content": "Use the Logging window to record the IFC Import process in a log file (the System automatically produces a log file).\n\nType\nSpecifies the level of content in the log file:\nBrief - To the industry standard.\nFull - To a level where problems can be isolated.\nLocation\nDisplays the Select log file window to navigate to the required log file.\nNote:\nThe log file location field cannot be empty.\nIf required, specify a name and alternative location.\nNote:\nWhen the source file or folder is selected on the first page, a default file name is generated based on the source name. So the log file will be placed next to the source file or folder.\nType\nSpecifies the level of content in the log file:\nLocation\nDisplays the Select log file window to navigate to the required log file.\nIf required, specify a name and alternative location.\nFor further information, refer to Source.\nType\nSpecifies the level of content in the log file:\nBrief - To the industry standard.\nFull - To a level where problems can be isolated.\nLocation\nDisplays the Select log file window to navigate to the required log file.\nNote:\nThe log file location field cannot be empty.\nIf required, specify a name and alternative location.\nNote:\nWhen the source file or folder is selected on the first page, a default file name is generated based on the source name. So the log file will be placed next to the source file or folder.\nBrief - To the industry standard.\nFull - To a level where problems can be isolated.\nBrief - To the industry standard.\nBrief - To the industry standard.\nFull - To a level where problems can be isolated.\nFull - To a level where problems can be isolated.\nNote:\nThe log file location field cannot be empty.\nNote:\nWhen the source file or folder is selected on the first page, a default file name is generated based on the source name. So the log file will be placed next to the source file or folder.\n\n\n\nSource\nLogging\nType\nBrief\nFull\nLocation\nSelect log file\nNote\n:\nNote\n:\nSource"}
{"Headers": "IFC Flexible Explorer", "Content": "The IFC model is imported into a flat structure, however, the IFC file contains structural information so that another view of the data may also be generated that better represents the IFC file.\nThe secondary IFC file hierarchy is created in the Group World (GPWL), using Group Sets (GPSET) and Group Items (GPITEM). Four data structures are created in the GPWL:\nThe reason for this apparent duplication is that the Flexible Explorer, which has a clearer presentation of the data than the Model Explorer is not available in PDMS 12.1. However the data in the Model Explorer can be viewed in PDMS 12.1 in a format similar to the Flexible Explorer but in a diminished mode called the IFC Flexible Explorer.\n\nCurrently there are four logical groupings that can be seen in the IFC Flexible Explorer:\nImported IFC files have a set of aggregate elements and set of spatial elements. A spatial project structure might define as many levels of decomposition as are necessary for the building project.\n\nElements within the spatial project structure are:\nThe spatial structure elements are linked together by a relationship object. If there are building elements and/or other elements directly related to the IfcBuildingStorey (like most building elements, such as walls, columns and so on), they are associated with the IfcBuildingStorey by using another relationship object.\nA recursive hierarchy of GPSETs and referenced IFC elements contained in GPITEMs shows these relationships that exist in the imported IFC file.\n\nSorting elements according to their IFC class or group allows an alternative view of the data in the IFC Flexible Explorer. The model can be viewed and inspected according to the IFC class or group as well as using additional functionality available from the IFC Flexible Explorer right-click menu to highlight, unhighlight, add, remove, view attributes, rename or delete a given IFC class.\n\nUse to highlight all the items of a given IFC class in the 3D view, for example: highlight all the IFCWallStandardCase imported from the IFC model.\n\nUsed to delete all the IFC elements or remove a specific IFC element.\n\nUse to add or remove all items of a given IFC class or group to/from the 3D view, for example Remove all ifc roof elements from the 3D view.\n\nImported IFC elements might have an associated IFCPropertySet or sets which contain a set of IFCPropertySingleValue. The IFC Flexible Explorer will display each element's associated properties that are stored in data sets.\nThere are IFCQuantity elements also associated with elements, the interface imports these into data sets as well.\nThe property node name that appears in the IFC Flexible Explorer is a concatenation of the imported Property Name and Property Value (highlighted in red). Selecting an IFC element Property navigates to the equivalent element in the Model Explorer.\n\nUse to display the Attribute window populated with all the attributes for the currently selected IFC class.\n\nUse to rename the currently selected IFC element, the node name displayed in the IFC Flexible Explorer is based on the Function attribute value on the GPSET. Changing the GPSET Function attribute will change the node name in the IFC Flexible Explorer.\n\nUse to highlight selected IFC entities in the 3D view.\n\nUse to unhighlight selected IFC entities in the 3D view.\n\nThe IFC System Representation element contains a grouping based on the IFC system, providing an alternative view of the data in the IFC Flexible Explorer. The model can be viewed and inspected, right-click on IFC elements in the IFC Flexible Explorer to highlight/unhighlight, add, remove and view the attributes of the elements.\n\nThe Layer Hierarchy Representation element groups and displays data in a layer hierarchy in the IFC Flexible Explorer. The layers of the model can be viewed and inspected, right-click to highlight/unhighlight, add, remove or view the attributes of the layers. The layers can also be renamed or deleted (see below).\n\nThe imported IFC model can be viewed in Draw, if required, the hierarchy of the imported model and/or the IFC element type can be viewed, launch the IFC Flexible Explorer from the menu bar.\n\nUse the functionality available from the IFC Flexible Explorer right-click menu in Draw to highlight/unhighlight, add or remove elements.\nUse to add, remove, highlight or unhighlight IFC elements, provided the 3D View is active.\n\nUse to view the attributes associated with IFC elements, the IFC imported model viewed in Draw is read only.\n\nUse to create a plan view for a specific IFC class, type or a building storey by selecting elements in the IFC Flexible Explorer.\n\nNavigate from the Model Explorer, 3D View or Drawing Sheet to the equivalent IFC Flexible Explorer node provided that its parent node is expanded in the IFC Flexible Explorer. Or navigate from the IFC Flexible Explorer to the equivalent element in the 3D view or the Model Explorer.\nIt is strongly advised against reordering the Hierarchical, Class Type representation or any logical grouping shown in the IFC Flexible Explorer. This is the representation of IFC model in the source file, and any kind of reordering will disrupt this representation and will probably result in a broken display.\nGrouping in the IFC Flexible Explorer\nIFC Hierarchical Representation\nIFC Class or Group Representation\nIFC System Representation\nIFC Layer Hierarchy Representation\nIFC Flexible Explorer in Draw\nSpecial conditions for the IFC Flexible Explorer\nNavigation Functionality\nReordering\nGrouping in the IFC Flexible Explorer\nGrouping in the IFC Flexible Explorer\nIFC Hierarchical Representation\nIFC Hierarchical Representation\nIFC Class or Group Representation\nIFC Class or Group Representation\nIFC System Representation\nIFC System Representation\nIFC Layer Hierarchy Representation\nIFC Layer Hierarchy Representation\nIFC Flexible Explorer in Draw\nIFC Flexible Explorer in Draw\nSpecial conditions for the IFC Flexible Explorer\nSpecial conditions for the IFC Flexible Explorer\nNavigation Functionality\nNavigation Functionality\nReordering\nReordering\nOne data structure to match the containment/decomposition hierarchy.\nThe next data structure to collect items according to their IFC class.\nThe next data structure to collect the items based on the System it is associated to.\nFinally, the data structure to group items based on Layer or display the Layer Hierarchy.\nOne data structure to match the containment/decomposition hierarchy.\nOne data structure to match the containment/decomposition hierarchy.\nThe next data structure to collect items according to their IFC class.\nThe next data structure to collect items according to their IFC class.\nThe next data structure to collect the items based on the System it is associated to.\nThe next data structure to collect the items based on the System it is associated to.\nFinally, the data structure to group items based on Layer or display the Layer Hierarchy.\nFinally, the data structure to group items based on Layer or display the Layer Hierarchy.\nIFC Hierarchical Representation\nIFC Class or Group Representation\nIFC System Representation\nIFC Layer Hierarchy Representation\nIFC Hierarchical Representation\nIFC Hierarchical Representation\nIFC Class or Group Representation\nIFC Class or Group Representation\nIFC System Representation\nIFC System Representation\nIFC Layer Hierarchy Representation\nIFC Layer Hierarchy Representation\nSite as IfcSite,\nBuilding as IfcBuilding,\nStorey as IfcBuildingStorey,\nSpace as IfcSpace.\nSite as IfcSite,\nSite as IfcSite,\nBuilding as IfcBuilding,\nBuilding as IfcBuilding,\nStorey as IfcBuildingStorey,\nStorey as IfcBuildingStorey,\nSpace as IfcSpace.\nSpace as IfcSpace.\nHighlight/Unhighlight all items of a given IFC class or group\nDelete IFC elements of a given IFC class or group\nAdd/Remove items of a given IFC class or group\nView attributes of the currently selected IFC element\nRename a given IFC element\nIFC entities in the 3D view\nHighlight/Unhighlight all items of a given IFC class or group\nHighlight/Unhighlight all items of a given IFC class or group\nDelete IFC elements of a given IFC class or group\nDelete IFC elements of a given IFC class or group\nAdd/Remove items of a given IFC class or group\nAdd/Remove items of a given IFC class or group\nView attributes of the currently selected IFC element\nView attributes of the currently selected IFC element\nRename a given IFC element\nRename a given IFC element\nIFC entities in the 3D view\nIFC entities in the 3D view\nIFC Flexible Explorer Right-click Menu in Draw\nIFC Flexible Explorer Right-click Menu in Draw\nIFC Flexible Explorer Right-click Menu in Draw\n3D View\nAttributes\nQuick View Creation\n3D View\n3D View\nAttributes\nAttributes\nQuick View Creation\nQuick View Creation\nNavigation Functionality\nReordering\nNavigation Functionality\nNavigation Functionality\nReordering\nReordering\nNote:\nSelecting an IFC element from the IFC Flexible Explorer navigates to the equivalent element in the 3D view and to Model Explorer.\nNote:\nRenaming elements in the IFC Flexible Explorer operates on the GPSET/GPITEM hierarchy, and not on the initial imported data structure. Additionally, the configuration of the IFC Flexible Explorer might mean that the displayed name of the GPSET or GPITEM is not the actual name in the Model Explorer.\n\n\n\nFlexible Explorer\nModel Explorer\nPDMS 12.1\nModel Explorer\nPDMS 12.1\nFlexible Explorer\nIFC Flexible Explorer\nIFC Flexible Explorer\nIfcSite\nIfcBuilding\nIfcBuildingStorey\nIfcSpace\nIfcBuildingStorey\nIfcBuildingStorey\nNote\n:\nIFC Flexible Explorer\nIFC Flexible Explorer\nIFC Flexible Explorer\nIFCWallStandardCase\nRemove all ifc roof elements from the 3D view\nIFCPropertySet\nIFCPropertySingleValue\nIFC Flexible Explorer\nIFCQuantity\nIFC Flexible Explorer\nProperty\nModel Explorer\nAttribute\nIFC Flexible Explorer\nFunction\nFunction\nIFC Flexible Explorer\nNote\n:\nIFC Flexible Explorer\nIFC Flexible Explorer\nModel Explorer\nIFC Flexible Explorer.\nIFC Flexible Explorer\nIFC Flexible Explorer.\nIFC Flexible Explorer\nIFC Flexible Explorer\nAttributes\nIFC Flexible Explorer\nIFC Flexible Explorer\nIFC Flexible Explorer\nIFC Flexible Explorer\nIFC Flexible Explorer"}
{"Headers": "Import Using the Command Line", "Content": "The import process is performed using a PML object IFCImporterObj. The UI provides a front end to prepare and validate the data before initiating the import. It is recommended to use this functionality if a User wishes to import their framework.\nThe command line syntax for importing an IFC file or folder is illustrated in the \"railtrack\" diagrams below.\nAs it has been indicated in the UI, there are four steps to building up the command line:\nWhen constructing the command line, there are more checks that have to be made in order to provide a valid command. These checks are made in the UI.\nThe full command is:\n\nThe individual components to this command are detailed below. As can be seen, certain parts can be bypassed. The implications of bypassing these parts are given.\n\n\nThe target element will be a SITE, under which a ZONE will be created for each IFC file to be imported. If this part of the syntax is not used, the current element is implied.\nThe IFC specific import options are as below, as can be seen from the diagrams above, these are optional components to the command line syntax.\n\nDefine the Reference Datum with the WRT or IN command component, the gid is a general PDMS element ID of a name or Reference Number.\nThe Group World that is to receive the GPSET's hierarchy is defined using the GPWL syntax component.\nTo rescale the imported model in a uniform scaling factor, use the SCALE syntax command.\n\nLogging is performed using the syntax below.\n\nA log file will be produced by default, the log file can be turned off. To produce a log file, select one of the options and provide a valid file path. If this is an existing file, it will be overwritten.\n\nWhen GENPRIs are displayed, the prevailing value of REPRE DARCTOL is used for the facet tolerance (that is by default 10 mm in PDMS and 1 mm in AVEVA Everything3D). If a GENPRI is imported with an explicit CTOL value set (Save Facet Data set in the UI) then these facets will be cached inside the DB (Database).\nThe cached facets will only be reused for display if the desired REPRE DARCTOL is close enough (between a factor of 0.8 and 4.0 times CTOL); otherwise they will be ignored. The GENPRI's underlying data will be faceted again from scratch with the desired tolerance. These facets will be discarded after use: that is the cached facets in the DB will not be overwritten.\nTo work with lighter geometric data, by slackening off the tolerance, they must change DARCTOL for everything; and if the facet data was saved with an unsuitable CTOL, it will not be useful.\nIf the CTOL value is unset, a default value is taken depending on the arc tolerance settings at the time.\n\n\n\nIFCImporterObj\nWRT\nIN\ngid\nSCALE\nREPRE DARCTOL\nCTOL\nSave Facet Data\nREPRE DARCTOL\nCTOL\nDARCTOL\nCTOL\nCTOL"}
{"Headers": "IFCImporterObj", "Content": "This section defines the API for the PML object that performs the import operation.\nNAME\nRESULT\nACTION\ngetBucketSize()\nREAL\nGets the number of imported elements per ZONE.\ngetUseBucketSize\nBOOLEAN\nGet Bucket Size usage flag.\ngetCacheFacets()\nBOOLEAN\nGet CTOL usage flag.\ngetDbTarget()\nDBREF\nGet DBREF of SITE to receive model.\ngetGroupWorld()\nDBREF\nGet DBREF of GPWL to receive parallel model.\ngetLogDetail()\nREAL\nSet logging levels.\ngetLogDetailText()\nSTRING\nConverts logging level into equivalent STRING.\n1. NONE\n2. BRIEF\n3. FULL\n4. DEBUG\ngetLogFile()\nSTRING\nGet full path name of log file.\ngetPrefix()\nSTRING\nGet the naming prefix.\ngetResult()\nSTRING\nGet result of Import operation.\ngetImportStatus()\nSTRING\nGet a fuller description of import status.\ngetRefDatum()\nDBREF\nGet the Reference Datum.\ngetScale()\nREAL\nGet the transform scale factor.\ngetSource()\nSTRING\nGet full path name of source file or folder.\ngetSrcFolderFlg()\nBOOLEAN\nGet source folder flag.\ngetTolerance()\nREAL\nGet CTOL value used for faceting.\ngetUserPostProcessor()\nSTRING\nGet the User-editable post-processor file name.\ngetUserPreProcessor()\nSTRING\nGet the User-editable pre-processor file name.\nifcimporterobj()\nNO RESULT\nConstructor.\nimport()\nSTRING\nImports the data and returns a result string.\npostProcess()\nNO RESULT\nSupplied post-processing function.\nsetBucketSize(REAL)\nNO RESULT\nSets the number of imported elements per ZONE.\nsetUseBucketSize(BOOLEAN)\nNO RESULT\nSet Bucket Size usage flag.\nsetCacheFacets(BOOLEAN)\nNO RESULT\nSet CTOL usage flag.\nsetDbTarget(DBREF)\nNO RESULT\nSet DBREF of SITE to receive model.\nsetGroupWorld(DBREF)\nNO RESULT\nSet DBREF of GPWL to receive parallel model.\nsetLogDetail(REAL)\nNO RESULT\nSet logging levels.\nsetLogFile(STRING)\nNO RESULT\nSet full path name of log file.\nsetPrefix( STRING )\nNO RESULT\nSet the naming prefix.\nsetRefDatum( DBREF )\nNO RESULT\nSet the Reference Datum.\nsetRefDatumByName(STRING)\nNO RESULT\nSets the Reference Datum by displayed name.\nsetRefDatumOption(BOOLEAN)\nNO RESULT\nSet flag indicating use of Reference Datum (true/false).\nsetScale( REAL )\nNO RESULT\nSet the transform scale factor.\nsetSource(STRING)\nNO RESULT\nSet full path name of source file or folder.\nsetSrcFolderFlg(BOOLEAN)\nNO RESULT\nSet True if source is a folder.\nsetTolerance(REAL)\nNO RESULT\nSet CTOL value used for faceting.\nsetUserPostProcessor()\nSTRING\nSet the User-editable post-processor file name.\nsetUserPreProcessor()\nSTRING\nSet the User-editable pre-processor file name.\nsplitIntoBuckets(BOOLEAN)\nNO RESULT\nSplit imported ZONE into buckets based on the bucket size, folder flag and source file name stored in imported ZONE description.\nuserPostProcess( STRING )\nNO RESULT\nPlugger for user post processing pml function.\nNAME\nRESULT\nACTION\ngetBucketSize()\nREAL\nGets the number of imported elements per ZONE.\ngetUseBucketSize\nBOOLEAN\nGet Bucket Size usage flag.\ngetCacheFacets()\nBOOLEAN\nGet CTOL usage flag.\ngetDbTarget()\nDBREF\nGet DBREF of SITE to receive model.\ngetGroupWorld()\nDBREF\nGet DBREF of GPWL to receive parallel model.\ngetLogDetail()\nREAL\nSet logging levels.\ngetLogDetailText()\nSTRING\nConverts logging level into equivalent STRING.\n1. NONE\n2. BRIEF\n3. FULL\n4. DEBUG\ngetLogFile()\nSTRING\nGet full path name of log file.\ngetPrefix()\nSTRING\nGet the naming prefix.\ngetResult()\nSTRING\nGet result of Import operation.\ngetImportStatus()\nSTRING\nGet a fuller description of import status.\ngetRefDatum()\nDBREF\nGet the Reference Datum.\ngetScale()\nREAL\nGet the transform scale factor.\ngetSource()\nSTRING\nGet full path name of source file or folder.\ngetSrcFolderFlg()\nBOOLEAN\nGet source folder flag.\ngetTolerance()\nREAL\nGet CTOL value used for faceting.\ngetUserPostProcessor()\nSTRING\nGet the User-editable post-processor file name.\ngetUserPreProcessor()\nSTRING\nGet the User-editable pre-processor file name.\nifcimporterobj()\nNO RESULT\nConstructor.\nimport()\nSTRING\nImports the data and returns a result string.\npostProcess()\nNO RESULT\nSupplied post-processing function.\nsetBucketSize(REAL)\nNO RESULT\nSets the number of imported elements per ZONE.\nsetUseBucketSize(BOOLEAN)\nNO RESULT\nSet Bucket Size usage flag.\nsetCacheFacets(BOOLEAN)\nNO RESULT\nSet CTOL usage flag.\nsetDbTarget(DBREF)\nNO RESULT\nSet DBREF of SITE to receive model.\nsetGroupWorld(DBREF)\nNO RESULT\nSet DBREF of GPWL to receive parallel model.\nsetLogDetail(REAL)\nNO RESULT\nSet logging levels.\nsetLogFile(STRING)\nNO RESULT\nSet full path name of log file.\nsetPrefix( STRING )\nNO RESULT\nSet the naming prefix.\nsetRefDatum( DBREF )\nNO RESULT\nSet the Reference Datum.\nsetRefDatumByName(STRING)\nNO RESULT\nSets the Reference Datum by displayed name.\nsetRefDatumOption(BOOLEAN)\nNO RESULT\nSet flag indicating use of Reference Datum (true/false).\nsetScale( REAL )\nNO RESULT\nSet the transform scale factor.\nsetSource(STRING)\nNO RESULT\nSet full path name of source file or folder.\nsetSrcFolderFlg(BOOLEAN)\nNO RESULT\nSet True if source is a folder.\nsetTolerance(REAL)\nNO RESULT\nSet CTOL value used for faceting.\nsetUserPostProcessor()\nSTRING\nSet the User-editable post-processor file name.\nsetUserPreProcessor()\nSTRING\nSet the User-editable pre-processor file name.\nsplitIntoBuckets(BOOLEAN)\nNO RESULT\nSplit imported ZONE into buckets based on the bucket size, folder flag and source file name stored in imported ZONE description.\nuserPostProcess( STRING )\nNO RESULT\nPlugger for user post processing pml function.\nThe member data for the object are as follows.\nNAME\nRESULT\nSTATUS\nACTION\nsource\nSTRING\nSETTABLE\nFull path name of source file or folder.\nsrcFolderFlg\nBOOLEAN\nSETTABLE\nTrue if source is a folder.\ndbTarget\nDBREF\nSETTABLE\nRefno of SITE to receive model.\ngroupWorld\nDBREF\nSETTABLE\nRefno of GPWL for parallel hierarchy.\nrefDatum\nDBREF\nSETTABLE\nReference Datum for import transformations.\nscale\nREAL\nSETTABLE\nModel scale factor.\ncacheFacets\nBOOLEAN\nSETTABLE\nTrue if using facet tolerance value.\ntolerance\nREAL\nSETTABLE\nFacet tolerance value.\nprefix\nSTRING\nSETTABLE\nModel naming prefix for post-processing.\nlogFile\nSTRING\nSETTABLE\nFull path name of log file.\nlogDetail\nREAL\nSETTABLE\nLogging levels:\n1. None\n2. Low\n3. Medium\n4. High\nresult\nSTRING\nGETTABLE\nShort result text.\nNAME\nRESULT\nSTATUS\nACTION\nsource\nSTRING\nSETTABLE\nFull path name of source file or folder.\nsrcFolderFlg\nBOOLEAN\nSETTABLE\nTrue if source is a folder.\ndbTarget\nDBREF\nSETTABLE\nRefno of SITE to receive model.\ngroupWorld\nDBREF\nSETTABLE\nRefno of GPWL for parallel hierarchy.\nrefDatum\nDBREF\nSETTABLE\nReference Datum for import transformations.\nscale\nREAL\nSETTABLE\nModel scale factor.\ncacheFacets\nBOOLEAN\nSETTABLE\nTrue if using facet tolerance value.\ntolerance\nREAL\nSETTABLE\nFacet tolerance value.\nprefix\nSTRING\nSETTABLE\nModel naming prefix for post-processing.\nlogFile\nSTRING\nSETTABLE\nFull path name of log file.\nlogDetail\nREAL\nSETTABLE\nLogging levels:\n1. None\n2. Low\n3. Medium\n4. High\nresult\nSTRING\nGETTABLE\nShort result text.\nBelow is an example of using the object in User-written PML.\nThe bucket splitting function is used to split the imported ZONE into a series of smaller ZONEs with a defined number of child elements. The default ZONE size of 100 can be customized if the import process is being performed from the command line. A value of less than 25 or more than 1000 cannot be entered. These are hard coded limits. For example:\nThe same core bucket splitting function is used to create multiple ZONEs and name the subsequent ZONEs based on the name of the original ZONE. This standalone function can also be called from the Command window to operate on elements other than ZONEs.\nFor example, in the Command window or a PML file, if !ref is the reference number of a ZONE, and the required !bucketSize is 50 ().\nThe function is not ZONE specific and can be used to partition any element.\nUse the setPrefix function to define the model naming prefix that is used in the naming algorithm.\nThis function call is to use the correct Reference Datum for applying transformations to the imported model. Internally, in the Application Data World the elements have a special suffix of -HDR which is not displayed.\nThe command above tells the importer to use the Reference Datum /IFCREVIT-HDR as its transformation data.\nTo use another ZONE that is outside the Application Data World, and is not controlled by this UI, you can set the Reference Datum using its DB Reference Number. For example:\nThere is scope to define additional operations before and after importing a model. These are pre- and post-processing functions that might operate on the model before or after it has been imported. User-defined pre- and post-processing functions can be called during the data transfer process.\nTemplate functions called userPreImpProcess.pmlfnc and userPostImpProcess.pmlfnc are supplied. The supplied default templates are called automatically from the Graphical User Interface post-process function. If the PML importer object is used, it is possible to provide the same additional functionality as required but they must be called manually when using the importer object.\nThese can be invoked using the commands:\nAlternatively, you may provide your own functions and inject them into the import process. This is achieved by providing a function or even a series of similar functions, <userFunction>.pmlfnc, for example, IFCPostProcessing.pmlfnc, in the PML search path and then plugging it or them into the System using the command line. These functions take one argument and must handle all PML errors internally. The functions return a string result value containing whatever message is to be transmitted to the running PML application. The template PML functions provide an example of how to structure the function.\nThese can be defined in the importer object as below, but there are defaults of:\nFor example:\nThe string values are used to construct a function name, for example, userPreImpProcess.pmlfnc, which the system will attempt to invoke. The import process will not fail if these functions are not found. They are normal PML functions that must be available in the PML search path. A PML REHASH ALL command might be necessary to refresh the PML index files. All error handling must be contained in the files themselves.\nWhen using the PML importer object directly, there are API functions on the importer object to set and get these values.\nFor example:\nPlease note that a parameter has been added to pre- or post-processing User function signatures to give User-access to the importer object itself. Note also that the User-definable functions must have a signature similar to the ones below, with the single parameter to the importer object. With the importer object, all the API functions become available within the pre- and post-processing functions.\nNAME\nRESULT\nACTION\ngetBucketSize()\nREAL\nGets the number of imported elements per ZONE.\ngetUseBucketSize\nBOOLEAN\nGet Bucket Size usage flag.\ngetCacheFacets()\nBOOLEAN\nGet CTOL usage flag.\ngetDbTarget()\nDBREF\nGet DBREF of SITE to receive model.\ngetGroupWorld()\nDBREF\nGet DBREF of GPWL to receive parallel model.\ngetLogDetail()\nREAL\nSet logging levels.\ngetLogDetailText()\nSTRING\nConverts logging level into equivalent STRING.\n1. NONE\n2. BRIEF\n3. FULL\n4. DEBUG\ngetLogFile()\nSTRING\nGet full path name of log file.\ngetPrefix()\nSTRING\nGet the naming prefix.\ngetResult()\nSTRING\nGet result of Import operation.\ngetImportStatus()\nSTRING\nGet a fuller description of import status.\ngetRefDatum()\nDBREF\nGet the Reference Datum.\ngetScale()\nREAL\nGet the transform scale factor.\ngetSource()\nSTRING\nGet full path name of source file or folder.\ngetSrcFolderFlg()\nBOOLEAN\nGet source folder flag.\ngetTolerance()\nREAL\nGet CTOL value used for faceting.\ngetUserPostProcessor()\nSTRING\nGet the User-editable post-processor file name.\ngetUserPreProcessor()\nSTRING\nGet the User-editable pre-processor file name.\nifcimporterobj()\nNO RESULT\nConstructor.\nimport()\nSTRING\nImports the data and returns a result string.\npostProcess()\nNO RESULT\nSupplied post-processing function.\nsetBucketSize(REAL)\nNO RESULT\nSets the number of imported elements per ZONE.\nsetUseBucketSize(BOOLEAN)\nNO RESULT\nSet Bucket Size usage flag.\nsetCacheFacets(BOOLEAN)\nNO RESULT\nSet CTOL usage flag.\nsetDbTarget(DBREF)\nNO RESULT\nSet DBREF of SITE to receive model.\nsetGroupWorld(DBREF)\nNO RESULT\nSet DBREF of GPWL to receive parallel model.\nsetLogDetail(REAL)\nNO RESULT\nSet logging levels.\nsetLogFile(STRING)\nNO RESULT\nSet full path name of log file.\nsetPrefix( STRING )\nNO RESULT\nSet the naming prefix.\nsetRefDatum( DBREF )\nNO RESULT\nSet the Reference Datum.\nsetRefDatumByName(STRING)\nNO RESULT\nSets the Reference Datum by displayed name.\nsetRefDatumOption(BOOLEAN)\nNO RESULT\nSet flag indicating use of Reference Datum (true/false).\nsetScale( REAL )\nNO RESULT\nSet the transform scale factor.\nsetSource(STRING)\nNO RESULT\nSet full path name of source file or folder.\nsetSrcFolderFlg(BOOLEAN)\nNO RESULT\nSet True if source is a folder.\nsetTolerance(REAL)\nNO RESULT\nSet CTOL value used for faceting.\nsetUserPostProcessor()\nSTRING\nSet the User-editable post-processor file name.\nsetUserPreProcessor()\nSTRING\nSet the User-editable pre-processor file name.\nsplitIntoBuckets(BOOLEAN)\nNO RESULT\nSplit imported ZONE into buckets based on the bucket size, folder flag and source file name stored in imported ZONE description.\nuserPostProcess( STRING )\nNO RESULT\nPlugger for user post processing pml function.\nNAME\nRESULT\nSTATUS\nACTION\nsource\nSTRING\nSETTABLE\nFull path name of source file or folder.\nsrcFolderFlg\nBOOLEAN\nSETTABLE\nTrue if source is a folder.\ndbTarget\nDBREF\nSETTABLE\nRefno of SITE to receive model.\ngroupWorld\nDBREF\nSETTABLE\nRefno of GPWL for parallel hierarchy.\nrefDatum\nDBREF\nSETTABLE\nReference Datum for import transformations.\nscale\nREAL\nSETTABLE\nModel scale factor.\ncacheFacets\nBOOLEAN\nSETTABLE\nTrue if using facet tolerance value.\ntolerance\nREAL\nSETTABLE\nFacet tolerance value.\nprefix\nSTRING\nSETTABLE\nModel naming prefix for post-processing.\nlogFile\nSTRING\nSETTABLE\nFull path name of log file.\nlogDetail\nREAL\nSETTABLE\nLogging levels:\n1. None\n2. Low\n3. Medium\n4. High\nresult\nSTRING\nGETTABLE\nShort result text.\nUserPreProcessor = |userPreImpProcess|\nUserPostProcessor = |userPostImpProcess|\nUserPreProcessor = |userPreImpProcess|\nUserPreProcessor = |userPreImpProcess|\nUserPostProcessor = |userPostImpProcess|\nUserPostProcessor = |userPostImpProcess|\ndefine method .setUserPreProcessor( !userPreProcessor is STRING )\ndefine method .getUserPreProcessor( ) is STRING\ndefine method .setUserPostProcessor( !userPostProcessor is STRING )\ndefine method .getUserPostProcessor( ) is STRING\ndefine method .setUserPreProcessor( !userPreProcessor is STRING )\ndefine method .setUserPreProcessor( !userPreProcessor is STRING )\ndefine method .getUserPreProcessor( ) is STRING\ndefine method .getUserPreProcessor( ) is STRING\ndefine method .setUserPostProcessor( !userPostProcessor is STRING )\ndefine method .setUserPostProcessor( !userPostProcessor is STRING )\ndefine method .getUserPostProcessor( ) is STRING\ndefine method .getUserPostProcessor( ) is STRING\ndefine function !!userPostImpProcess( !importer is IFCIMPORTEROBJ ) is STRING\ndefine function !!userPreImpProcess( !importer is IFCIMPORTEROBJ ) is STRING\ndefine function !!userPostImpProcess( !importer is IFCIMPORTEROBJ ) is STRING\ndefine function !!userPostImpProcess( !importer is IFCIMPORTEROBJ ) is STRING\ndefine function !!userPreImpProcess( !importer is IFCIMPORTEROBJ ) is STRING\ndefine function !!userPreImpProcess( !importer is IFCIMPORTEROBJ ) is STRING\nNote:\nThe templates do not do anything, but it is possible to use them as a framework for your own requirements.\n\n\n\nNAME\nRESULT\nACTION\ngetBucketSize()\ngetUseBucketSize\ngetCacheFacets()\nCTOL\ngetDbTarget()\nDBREF\ngetGroupWorld()\nDBREF\ngetLogDetail()\ngetLogDetailText()\ngetLogFile()\ngetPrefix()\ngetResult()\ngetImportStatus()\ngetRefDatum()\ngetScale()\ngetSource()\ngetSrcFolderFlg()\ngetTolerance()\nCTOL\ngetUserPostProcessor()\ngetUserPreProcessor()\nifcimporterobj()\nimport()\npostProcess()\nsetBucketSize(REAL)\nsetUseBucketSize(BOOLEAN)\nBucket Size\nsetCacheFacets(BOOLEAN)\nCTOL\nsetDbTarget(DBREF)\nDBREF\nsetGroupWorld(DBREF)\nDBREF\nsetLogDetail(REAL)\nsetLogFile(STRING)\nsetPrefix( STRING )\nsetRefDatum( DBREF )\nsetRefDatumByName(STRING)\nsetRefDatumOption(BOOLEAN)\nsetScale( REAL )\nsetSource(STRING)\nsetSrcFolderFlg(BOOLEAN)\nsetTolerance(REAL)\nCTOL\nsetUserPostProcessor()\nsetUserPreProcessor()\nsplitIntoBuckets(BOOLEAN)\nuserPostProcess( STRING )\nNAME\nRESULT\nSTATUS\nACTION\nCommand\nCommand\n!ref\n!bucketSize\n50 ()\nsetPrefix\nsetRefDatumByName\n-HDR\n/IFCREVIT-HDR\nNote\n:\nUserPreProcessor = |userPreImpProcess|\nUserPostProcessor = |userPostImpProcess|\nPML REHASH ALL\ndefine method .setUserPreProcessor( !userPreProcessor is STRING )\ndefine method .getUserPreProcessor( ) is STRING\ndefine method .setUserPostProcessor( !userPostProcessor is STRING )\ndefine method .getUserPostProcessor( ) is STRING\ndefine function !!userPostImpProcess( !importer is IFCIMPORTEROBJ ) is STRING\ndefine function !!userPreImpProcess( !importer is IFCIMPORTEROBJ ) is STRING"}
{"Headers": "Configuration", "Content": "The Source, Settings and Import windows are displayed by progressive disclosure:\nUse the functionality available from the Source window, you can select the CAD file format and CAD file to be imported.\nRefer to Model Simplification Settings for further information.\nBlue ticks indicate all entries are valid\nOrange triangles indicate mandatory entries are still required.\nBlue ticks indicate all entries are valid\nBlue ticks indicate all entries are valid\nOrange triangles indicate mandatory entries are still required.\nOrange triangles indicate mandatory entries are still required.\n\n\n\nModel Simplification Settings\nSource\nSettings\nImport\nSource\nTools\nImport\nModel Simplification.\nModel Simplification\nNative Model Simplification\nSource File\nSource File\nNext\nSettings\nNote\n:\nSelect a CAD File\nModel Simplification Settings"}
{"Headers": "Model Simplification Settings", "Content": "Use the functionality available from the Settings window to define the Simplification Settings (Configuration, Simplification Level, Cylindrical or Box simplification and which elements of the models are to be removed).\n\nRefer to Import for further information.\nStart - Internals are removed early in the process, so internal objects can be discarded if they cannot be seen through a gap bigger than the specified size. This can save processing time if there are complicated internal objects, as no attempt need be made to simplify the internal object.\nEnd - Holes are removed before Internals are processed, so more internals by be identified as they are no longer visible from the outside.\nBoth - The internal removal process is run twice, to remove as many internals as possible, while avoiding simplification of internal components when possible.\nStart - Internals are removed early in the process, so internal objects can be discarded if they cannot be seen through a gap bigger than the specified size. This can save processing time if there are complicated internal objects, as no attempt need be made to simplify the internal object.\nStart - Internals are removed early in the process, so internal objects can be discarded if they cannot be seen through a gap bigger than the specified size. This can save processing time if there are complicated internal objects, as no attempt need be made to simplify the internal object.\nEnd - Holes are removed before Internals are processed, so more internals by be identified as they are no longer visible from the outside.\nEnd - Holes are removed before Internals are processed, so more internals by be identified as they are no longer visible from the outside.\nBoth - The internal removal process is run twice, to remove as many internals as possible, while avoiding simplification of internal components when possible.\nBoth - The internal removal process is run twice, to remove as many internals as possible, while avoiding simplification of internal components when possible.\n\n\n\nImport\nSettings\nSimplification Settings\nSimplification Level\nCylindrical\nBox simplification\nBasic\nIntermediate\nAggressive\nFixed values\nAdvanced\nNote:\nAuto calculated values\nBase\nNotes:\nApply\nSimplification Level\nCylindrical\nBox\nIntermediate\nAggressive\nCylindrical\nExtrusion\nProfile\nExtrusion\nAdvanced\nInternals\nProcess Stage\nNote:\nAuto calculated value\nProcess Stage\nStart\nEnd\nBoth\nStart\nEnd\nBoth\nNew Configuration\nSave\nInformation\next\nImport\nBack\nSource\nImport"}
{"Headers": "Import", "Content": "Use the functionality available from the Import window to specify the Import Settings and Simplification Output. The progress of the import and any errors and/or messages can also be viewed here.\n\n\n\n\n\nImport\nImport Settings\nSimplification Output\nModel Explorer\nImport\nCE\nSelect Owner\nSelect Site or Zone\nCreate SUBE Level\nSave Facet Data\nSave Support Log\nImport\nModel Simplification\nBack\nSettings\nNote:\nModel Simplification\nNote:"}
{"Headers": "Errors and Warnings", "Content": "If the simplification progress fails, the relevant information is displayed in the messages window.\n\n\n\n"}
{"Headers": "Model Simplifier Object", "Content": "The PML-Callable Model Simplifier Object is the API, which may be used to simplify and import CAD models from the E3D Design command line, from macros or PML functions or objects.\nNote:\nNot all of the functions of the user interface are included, but enough for common use cases. Refer to Model Simplification Import Examples for further information.\n\n\n\nModel Simplification Import Examples\nPML-Callable Model Simplifier Object\nNote\n:\nModel Simplification Import Examples"}
{"Headers": "Simplification Settings Function", "Content": "Use the functionality to set or query most of the parameters set in the Simplification Settings pane of the Native Model Simplification window.\n\nNAME\nRESULT\nACTION\nsetSimplificationLevel(REAL)\nNO RESULT\nSet the overall simplification level, the overall parameter should be an integer; 1 for basic simplification, 2 for intermediate simplification (default) or 3 for aggressive simplification.\nNote:\nCalling this functions also sets the other parameters from this page to the defaults for that simplification level. This should be called before any other settings if these defaults are to be modified.\ngetSimplificationLevel()\nREAL\nReturns the current simplification level as an integer:1, 2 or 3.\nsetCylindricalSimplification(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the conversion of parts of the model to cylindrical shapes, default is TRUE.\ngetCylindricalSimplification()\nBOOLEAN\nReturns TRUE if cylindrical simplification is enabled, and FALSE otherwise.\nsetBoxSimplification(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the conversion of parts of the model to box shapes, default is TRUE.\ngetBoxSimplification()\nBOOLEAN\nReturns TRUE if box simplification is enabled, and FALSE otherwise.\nsetExtrusionSimplificationProfile(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the simplification of Extrusion Profiles from the model. The Default is TRUE.\nsetExtrusionSimplificationProfile ()\nBOOLEAN\nReturns TRUE if the simplification of Extrusion. Profiles is Enabled, and FALSE otherwise.\nsetInternalStage(STRING)\nNO RESULT\nSet the internal stage for removal of Internals during the simplification process. There are three choices: 'PRE', 'POST' or 'BOTH'. The Default is ' PRE'.\ngetInternalStage()\nSTRING\nReturns the string representation of Internal stage configured. For example, 'PRE'.\nsetRemoveHoles(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of small holes from the model, default is TRUE.\ngetRemoveHoles()\nBOOLEAN\nReturns TRUE if hole removal is enabled, and FALSE otherwise.\nsetRemoveHoleSize(STRING)\nNO RESULT\nSet the maximum size of hole to be removed, if hole removal is enabled. The parameter is a string including units, for example 150mm and not a number or an E3D length, default is 75mm.\ngetRemoveHoleSize()\nSTRING\nReturns the string representation of the maximum size of hole to be removed, if hole removal is enabled. For example 40mm.\nsetRemoveSmallBodies(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of small bodies from the model, default is TRUE.\ngetRemoveSmallBodies ()\nBOOLEAN\nReturns TRUE if small-body removal is enabled, and FALSE otherwise.\ngetRemoveSmallBodySize()\nSTRING\nReturns the string representation of the maximum size of body to be removed, if small-body removal is enabled. For example 40mm.\nsetRemoveInternals(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of internal bodies from the model, default is TRUE\ngetRemoveInternals ()\nBOOLEAN\nReturns TRUE if internal-body removal is enabled, and FALSE otherwise.\nsetRemoveInternalGapSize(STRING)\nNO RESULT\nSet the maximum size of gap to be ignored when deciding if a component is internal or not, if internal-body removal is enabled. The parameter is a string including units, for example 150mm and not a number or an E3D length, default is 75mm.\ngetRemoveInternalGapSize()\nSTRING\nReturns the string representation of the maximum size of gap to be ignored, if internal-body removal is enabled. For example 40mm.\nsetRemoveProtrusions(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of small protrusions from the model, default is TRUE.\ngetRemoveProtrusion ()\nBOOLEAN\nReturns TRUE if protrusion removal is enabled, and FALSE otherwise.\nsetRemoveProtrusionSize(STRING)\nNO RESULT\nSet the maximum size of protrusion to be removed, if protrusion removal is enabled. The parameter is a string including units, for example 150mm and not a number or an E3D length, default is 15mm.\ngetRemoveProtrusionSize()\nSTRING\nReturns the string representation of the maximum size of protrusion to be removed, if hole removal is enabled. For example 40mm.\nsetSimplificationLevel(REAL)\n\nNO RESULT\nSet the overall simplification level, the overall parameter should be an integer; 1 for basic simplification, 2 for intermediate simplification (default) or 3 for aggressive simplification.\ngetSimplificationLevel()\n\nREAL\nReturns the current simplification level as an integer:1, 2 or 3.\nsetCylindricalSimplification(BOOLEAN)\n\nNO RESULT\nEnables (TRUE) or disables (FALSE) the conversion of parts of the model to cylindrical shapes, default is TRUE.\ngetCylindricalSimplification()\n\nBOOLEAN\nReturns TRUE if cylindrical simplification is enabled, and FALSE otherwise.\nsetBoxSimplification(BOOLEAN)\n\nNO RESULT\nEnables (TRUE) or disables (FALSE) the conversion of parts of the model to box shapes, default is TRUE.\n\ngetBoxSimplification()\n\nBOOLEAN\nReturns TRUE if box simplification is enabled, and FALSE otherwise.\nsetExtrusionSimplificationProfile(BOOLEAN)\n\nNO RESULT\nEnables (TRUE) or disables (FALSE) the simplification of Extrusion Profiles from the model. The Default is TRUE.\nsetExtrusionSimplificationProfile ()\n\nBOOLEAN\nReturns TRUE if the simplification of Extrusion. Profiles is Enabled, and FALSE otherwise.\nsetInternalStage(STRING)\n\nNO RESULT\nSet the internal stage for removal of Internals during the simplification process. There are three choices: 'PRE', 'POST' or 'BOTH'. The Default is ' PRE'.\ngetInternalStage()\n\nSTRING\nReturns the string representation of Internal stage configured. For example, 'PRE'.\n\nsetRemoveHoles(BOOLEAN)\n\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of small holes from the model, default is TRUE.\ngetRemoveHoles()\n\nBOOLEAN\nReturns TRUE if hole removal is enabled, and FALSE otherwise.\nsetRemoveHoleSize(STRING)\n\nNO RESULT\nSet the maximum size of hole to be removed, if hole removal is enabled. The parameter is a string including units, for example 150mm and not a number or an E3D length, default is 75mm.\ngetRemoveHoleSize()\n\nSTRING\nReturns the string representation of the maximum size of hole to be removed, if hole removal is enabled. For example 40mm.\nsetRemoveSmallBodies(BOOLEAN)\n\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of small bodies from the model, default is TRUE.\ngetRemoveSmallBodies ()\n\nBOOLEAN\nReturns TRUE if small-body removal is enabled, and FALSE otherwise.\ngetRemoveSmallBodySize()\n\nSTRING\nReturns the string representation of the maximum size of body to be removed, if small-body removal is enabled. For example 40mm.\nsetRemoveInternals(BOOLEAN)\n\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of internal bodies from the model, default is TRUE\ngetRemoveInternals ()\n\nBOOLEAN\nReturns TRUE if internal-body removal is enabled, and FALSE otherwise.\nsetRemoveInternalGapSize(STRING)\n\nNO RESULT\nSet the maximum size of gap to be ignored when deciding if a component is internal or not, if internal-body removal is enabled. The parameter is a string including units, for example 150mm and not a number or an E3D length, default is 75mm.\ngetRemoveInternalGapSize()\n\nSTRING\nReturns the string representation of the maximum size of gap to be ignored, if internal-body removal is enabled. For example 40mm.\nsetRemoveProtrusions(BOOLEAN)\n\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of small protrusions from the model, default is TRUE.\ngetRemoveProtrusion ()\n\nBOOLEAN\nReturns TRUE if protrusion removal is enabled, and FALSE otherwise.\nsetRemoveProtrusionSize(STRING)\n\nNO RESULT\nSet the maximum size of protrusion to be removed, if protrusion removal is enabled. The parameter is a string including units, for example 150mm and not a number or an E3D length, default is 15mm.\ngetRemoveProtrusionSize()\n\nSTRING\nReturns the string representation of the maximum size of protrusion to be removed, if hole removal is enabled. For example 40mm.\n\nNAME\nRESULT\nACTION\nsetSimplificationLevel(REAL)\nNO RESULT\nSet the overall simplification level, the overall parameter should be an integer; 1 for basic simplification, 2 for intermediate simplification (default) or 3 for aggressive simplification.\nNote:\nCalling this functions also sets the other parameters from this page to the defaults for that simplification level. This should be called before any other settings if these defaults are to be modified.\ngetSimplificationLevel()\nREAL\nReturns the current simplification level as an integer:1, 2 or 3.\nsetCylindricalSimplification(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the conversion of parts of the model to cylindrical shapes, default is TRUE.\ngetCylindricalSimplification()\nBOOLEAN\nReturns TRUE if cylindrical simplification is enabled, and FALSE otherwise.\nsetBoxSimplification(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the conversion of parts of the model to box shapes, default is TRUE.\ngetBoxSimplification()\nBOOLEAN\nReturns TRUE if box simplification is enabled, and FALSE otherwise.\nsetExtrusionSimplificationProfile(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the simplification of Extrusion Profiles from the model. The Default is TRUE.\nsetExtrusionSimplificationProfile ()\nBOOLEAN\nReturns TRUE if the simplification of Extrusion. Profiles is Enabled, and FALSE otherwise.\nsetInternalStage(STRING)\nNO RESULT\nSet the internal stage for removal of Internals during the simplification process. There are three choices: 'PRE', 'POST' or 'BOTH'. The Default is ' PRE'.\ngetInternalStage()\nSTRING\nReturns the string representation of Internal stage configured. For example, 'PRE'.\nsetRemoveHoles(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of small holes from the model, default is TRUE.\ngetRemoveHoles()\nBOOLEAN\nReturns TRUE if hole removal is enabled, and FALSE otherwise.\nsetRemoveHoleSize(STRING)\nNO RESULT\nSet the maximum size of hole to be removed, if hole removal is enabled. The parameter is a string including units, for example 150mm and not a number or an E3D length, default is 75mm.\ngetRemoveHoleSize()\nSTRING\nReturns the string representation of the maximum size of hole to be removed, if hole removal is enabled. For example 40mm.\nsetRemoveSmallBodies(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of small bodies from the model, default is TRUE.\ngetRemoveSmallBodies ()\nBOOLEAN\nReturns TRUE if small-body removal is enabled, and FALSE otherwise.\ngetRemoveSmallBodySize()\nSTRING\nReturns the string representation of the maximum size of body to be removed, if small-body removal is enabled. For example 40mm.\nsetRemoveInternals(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of internal bodies from the model, default is TRUE\ngetRemoveInternals ()\nBOOLEAN\nReturns TRUE if internal-body removal is enabled, and FALSE otherwise.\nsetRemoveInternalGapSize(STRING)\nNO RESULT\nSet the maximum size of gap to be ignored when deciding if a component is internal or not, if internal-body removal is enabled. The parameter is a string including units, for example 150mm and not a number or an E3D length, default is 75mm.\ngetRemoveInternalGapSize()\nSTRING\nReturns the string representation of the maximum size of gap to be ignored, if internal-body removal is enabled. For example 40mm.\nsetRemoveProtrusions(BOOLEAN)\nNO RESULT\nEnables (TRUE) or disables (FALSE) the removal of small protrusions from the model, default is TRUE.\ngetRemoveProtrusion ()\nBOOLEAN\nReturns TRUE if protrusion removal is enabled, and FALSE otherwise.\nsetRemoveProtrusionSize(STRING)\nNO RESULT\nSet the maximum size of protrusion to be removed, if protrusion removal is enabled. The parameter is a string including units, for example 150mm and not a number or an E3D length, default is 15mm.\ngetRemoveProtrusionSize()\nSTRING\nReturns the string representation of the maximum size of protrusion to be removed, if hole removal is enabled. For example 40mm.\nNote:\nCalling this functions also sets the other parameters from this page to the defaults for that simplification level. This should be called before any other settings if these defaults are to be modified.\n\n\n\nSimplification Settings\nNative Model Simplification\nsetSimplificationLevel(REAL)\nNote\n:\ngetSimplificationLevel()\nsetCylindricalSimplification(BOOLEAN)\ngetCylindricalSimplification()\nsetBoxSimplification(BOOLEAN)\ngetBoxSimplification()\nsetExtrusionSimplificationProfile(BOOLEAN)\nsetExtrusionSimplificationProfile ()\nsetInternalStage(STRING)\ngetInternalStage()\nsetRemoveHoles(BOOLEAN)\ngetRemoveHoles()\nsetRemoveHoleSize(STRING)\ngetRemoveHoleSize()\nsetRemoveSmallBodies(BOOLEAN)\ngetRemoveSmallBodies ()\ngetRemoveSmallBodySize()\nsetRemoveInternals(BOOLEAN)\ngetRemoveInternals ()\nsetRemoveInternalGapSize(STRING)\ngetRemoveInternalGapSize()\nsetRemoveProtrusions(BOOLEAN)\ngetRemoveProtrusion ()\nsetRemoveProtrusionSize(STRING)\ngetRemoveProtrusionSize()"}
{"Headers": "Source Settings Function", "Content": "A Native license allows the simplification of any supported format, while a Basic license only allows simplification of STEP files.\n\nNAME\nRESULT\nACTION\nsetPreferNativeLicense(BOOLEAN)\nNO RESULT\nIn the unusual circumstance that both license types are available call this function with TRUE to use a Native license when simplifying a STEP file, thus reserving the Native license for your use in later simplifications. The duration of this license reservation depends on your licensing setup.\nNormally it is not necessary to call this function and a suitable license will be used for the simplification, if one is available, default is TRUE.\ngetPreferNativeLicense()\nBOOLEAN\nReturns true if a native license will always be used, if one is available.\nsetCadFormat(STRING)\nNO RESULT\nSet the format of the input CAD file. This string parameter must be one of the following string values (case is significant):\n|STEP| (default)\n|CATIA|\n|Creo|\n|Inventor|\n|NX|\n|Solid Edge|\n|SolidWORKS|.\ngetCadFormat()\nSTRING\nReturns one of the above strings for the currently selected CAD Format.\nsetInputFilePath(STRING)\nNO RESULT\nSet the path of the input CAD file as a string. The path cannot contain environment variable references or wild cards. (The PathName() function of a PML File object may be useful to expand these) default is ''.\ngetInputFilePath()\nSTRING\nReturns the path of the most recent input file.\nsetPreferNativeLicense(BOOLEAN)\n\nNO RESULT\nIn the unusual circumstance that both license types are available call this function with TRUE to use a Native license when simplifying a STEP file, thus reserving the Native license for your use in later simplifications. The duration of this license reservation depends on your licensing setup.\nNormally it is not necessary to call this function and a suitable license will be used for the simplification, if one is available, default is TRUE.\ngetPreferNativeLicense()\n\nBOOLEAN\nReturns true if a native license will always be used, if one is available.\nsetCadFormat(STRING)\n\nNO RESULT\nSet the format of the input CAD file. This string parameter must be one of the following string values (case is significant):\ngetCadFormat()\n\nSTRING\nReturns one of the above strings for the currently selected CAD Format.\nsetInputFilePath(STRING)\n\nNO RESULT\nSet the path of the input CAD file as a string. The path cannot contain environment variable references or wild cards. (The PathName() function of a PML File object may be useful to expand these) default is ''.\ngetInputFilePath()\n\nSTRING\nReturns the path of the most recent input file.\n\nNAME\nRESULT\nACTION\nsetPreferNativeLicense(BOOLEAN)\nNO RESULT\nIn the unusual circumstance that both license types are available call this function with TRUE to use a Native license when simplifying a STEP file, thus reserving the Native license for your use in later simplifications. The duration of this license reservation depends on your licensing setup.\nNormally it is not necessary to call this function and a suitable license will be used for the simplification, if one is available, default is TRUE.\ngetPreferNativeLicense()\nBOOLEAN\nReturns true if a native license will always be used, if one is available.\nsetCadFormat(STRING)\nNO RESULT\nSet the format of the input CAD file. This string parameter must be one of the following string values (case is significant):\n|STEP| (default)\n|CATIA|\n|Creo|\n|Inventor|\n|NX|\n|Solid Edge|\n|SolidWORKS|.\ngetCadFormat()\nSTRING\nReturns one of the above strings for the currently selected CAD Format.\nsetInputFilePath(STRING)\nNO RESULT\nSet the path of the input CAD file as a string. The path cannot contain environment variable references or wild cards. (The PathName() function of a PML File object may be useful to expand these) default is ''.\ngetInputFilePath()\nSTRING\nReturns the path of the most recent input file.\n|STEP| (default)\n|CATIA|\n|Creo|\n|Inventor|\n|NX|\n|Solid Edge|\n|SolidWORKS|.\n|STEP| (default)\n|STEP| (default)\n|CATIA|\n|CATIA|\n|Creo|\n|Creo|\n|Inventor|\n|Inventor|\n|NX|\n|NX|\n|Solid Edge|\n|Solid Edge|\n|SolidWORKS|.\n|SolidWORKS|.\nNote:\nSome of the functions described behave differently depending on the installation and license.\n\n\n\nNative\nBasic\nNote\n:\nsetPreferNativeLicense(BOOLEAN)\ngetPreferNativeLicense()\nsetCadFormat(STRING)\ngetCadFormat()\nsetInputFilePath(STRING)\ngetInputFilePath()"}
{"Headers": "Import Settings Functions", "Content": "Use the functionality to set or query most of the parameters set in the Import Settings.\n\nNAME\nRESULT\nACTION\nsetImportOwner(STRING)\nNO RESULT\nSet the owning element for the imported model. This must be a SITE or a ZONE. This must be supplied as a string containing one of the following:\na Refno for example |=2013286748/3116453|\na name, for example\n|/SITE-FOR-IMPORT|\nan empty string for the Current Element (the default) ||\ngetImportOwner()\nSTRING\nReturns a string which may be empty for Current Element or a string representation of the REFNO of the Import owner element.\nsetImportModelAs(STRING)\nNO RESULT\nOne of the following strings (case dependent) to set the type of the top-level E3D Design Element for the Import:\n|EQUI| (default)\n|VOLM|\n|SUBE\ngetImportModelAs()\nSTRING\nReturns one of the following strings (case dependent) to show the type of the top-level E3D Design Element for the Import:\n|EQUI|\n|VOLM|\n|SUBE|.\nsetImportOwner(STRING)\n\nNO RESULT\nSet the owning element for the imported model. This must be a SITE or a ZONE. This must be supplied as a string containing one of the following:\ngetImportOwner()\n\nSTRING\nReturns a string which may be empty for Current Element or a string representation of the REFNO of the Import owner element.\nsetImportModelAs(STRING)\n\nNO RESULT\nOne of the following strings (case dependent) to set the type of the top-level E3D Design Element for the Import:\ngetImportModelAs()\n\nSTRING\nReturns one of the following strings (case dependent) to show the type of the top-level E3D Design Element for the Import:\n\nNAME\nRESULT\nACTION\nsetImportOwner(STRING)\nNO RESULT\nSet the owning element for the imported model. This must be a SITE or a ZONE. This must be supplied as a string containing one of the following:\na Refno for example |=2013286748/3116453|\na name, for example\n|/SITE-FOR-IMPORT|\nan empty string for the Current Element (the default) ||\ngetImportOwner()\nSTRING\nReturns a string which may be empty for Current Element or a string representation of the REFNO of the Import owner element.\nsetImportModelAs(STRING)\nNO RESULT\nOne of the following strings (case dependent) to set the type of the top-level E3D Design Element for the Import:\n|EQUI| (default)\n|VOLM|\n|SUBE\ngetImportModelAs()\nSTRING\nReturns one of the following strings (case dependent) to show the type of the top-level E3D Design Element for the Import:\n|EQUI|\n|VOLM|\n|SUBE|.\na Refno for example |=2013286748/3116453|\na name, for example\n|/SITE-FOR-IMPORT|\nan empty string for the Current Element (the default) ||\na Refno for example |=2013286748/3116453|\na Refno for example |=2013286748/3116453|\na name, for example\na name, for example\n|/SITE-FOR-IMPORT|\n|/SITE-FOR-IMPORT|\nan empty string for the Current Element (the default) ||\nan empty string for the Current Element (the default) ||\n|EQUI| (default)\n|VOLM|\n|SUBE\n|EQUI| (default)\n|EQUI| (default)\n|VOLM|\n|VOLM|\n|SUBE\n|SUBE\n|EQUI|\n|VOLM|\n|SUBE|.\n|EQUI|\n|EQUI|\n|VOLM|\n|VOLM|\n|SUBE|.\n|SUBE|.\n\n\n\nImport Settings\nsetImportOwner(STRING)\ngetImportOwner()\nCurrent Element\nsetImportModelAs(STRING)\ngetImportModelAs()"}
{"Headers": "Simplification Output Settings", "Content": "Use the functionality to set or query most of the parameters set in the Output Settings.\n\nNAME\nRESULT\nACTION\nsetSaveSimplifiedFile(BOOLEAN)\nNO RESULT\nIf the parameter is TRUE (the default) the simplified CAD file (which is always a.stp file) is left on the file system for future use. If the parameter is FALSE the simplified file is deleted after import. The default is TRUE.\ngetSaveSimplifiedFile()\nBOOLEAN\nReturns TRUE is the simplified file will be saved, and FALSE otherwise.\nsetSaveSupportLog(BOOLEAN)\nNO RESULT\nIf the parameter is TRUE (the default) additional information useful for support calls and issue investigation left on the file system for future use. If the parameter is FALSE the information is not saved.\nThe default is TRUE.\nNote:\nIf a support log is saved, then the simplified File is always saved.\ngetSaveSupportLog()\nBOOLEAN\nReturns TRUE is the support log will be saved, and FALSE otherwise.\nsetOutputFolderPath(STRING)\nNO RESULT\nThis path is used only if the simplified file (and optionally the support log information) is saved, otherwise a temporary folder beneath %AVEVA_DESIGN_WORKS%\\ModelSimplification is created and used.\nOtherwise, this path is used for the simplified .stp file, and any support long information, and in addition various temporary files used during the simplification process. The path cannot contain environment variable references or wild cards. (The PathName() function of a PML File object may be useful to expand these.).\nIf the string is empty, then a default directory is used. The default value is |%AVEVA_DESIGN_USER%\\Model_Simplification_Results|\ngetOutputFolderPath()\nSTRING\nReturns the string set above.\nsetSaveSimplifiedFile(BOOLEAN)\n\nNO RESULT\nIf the parameter is TRUE (the default) the simplified CAD file (which is always a.stp file) is left on the file system for future use. If the parameter is FALSE the simplified file is deleted after import. The default is TRUE.\ngetSaveSimplifiedFile()\n\nBOOLEAN\nReturns TRUE is the simplified file will be saved, and FALSE otherwise.\nsetSaveSupportLog(BOOLEAN)\n\nNO RESULT\nIf the parameter is TRUE (the default) additional information useful for support calls and issue investigation left on the file system for future use. If the parameter is FALSE the information is not saved.\nThe default is TRUE.\ngetSaveSupportLog()\n\nBOOLEAN\nReturns TRUE is the support log will be saved, and FALSE otherwise.\nsetOutputFolderPath(STRING)\n\nNO RESULT\nThis path is used only if the simplified file (and optionally the support log information) is saved, otherwise a temporary folder beneath %AVEVA_DESIGN_WORKS%\\ModelSimplification is created and used.\nOtherwise, this path is used for the simplified .stp file, and any support long information, and in addition various temporary files used during the simplification process. The path cannot contain environment variable references or wild cards. (The PathName() function of a PML File object may be useful to expand these.).\nIf the string is empty, then a default directory is used. The default value is |%AVEVA_DESIGN_USER%\\Model_Simplification_Results|\ngetOutputFolderPath()\n\nSTRING\nReturns the string set above.\n\nNAME\nRESULT\nACTION\nsetSaveSimplifiedFile(BOOLEAN)\nNO RESULT\nIf the parameter is TRUE (the default) the simplified CAD file (which is always a.stp file) is left on the file system for future use. If the parameter is FALSE the simplified file is deleted after import. The default is TRUE.\ngetSaveSimplifiedFile()\nBOOLEAN\nReturns TRUE is the simplified file will be saved, and FALSE otherwise.\nsetSaveSupportLog(BOOLEAN)\nNO RESULT\nIf the parameter is TRUE (the default) additional information useful for support calls and issue investigation left on the file system for future use. If the parameter is FALSE the information is not saved.\nThe default is TRUE.\nNote:\nIf a support log is saved, then the simplified File is always saved.\ngetSaveSupportLog()\nBOOLEAN\nReturns TRUE is the support log will be saved, and FALSE otherwise.\nsetOutputFolderPath(STRING)\nNO RESULT\nThis path is used only if the simplified file (and optionally the support log information) is saved, otherwise a temporary folder beneath %AVEVA_DESIGN_WORKS%\\ModelSimplification is created and used.\nOtherwise, this path is used for the simplified .stp file, and any support long information, and in addition various temporary files used during the simplification process. The path cannot contain environment variable references or wild cards. (The PathName() function of a PML File object may be useful to expand these.).\nIf the string is empty, then a default directory is used. The default value is |%AVEVA_DESIGN_USER%\\Model_Simplification_Results|\ngetOutputFolderPath()\nSTRING\nReturns the string set above.\nNote:\nIf a support log is saved, then the simplified File is always saved.\n\n\n\nOutput Settings\nsetSaveSimplifiedFile(BOOLEAN)\ngetSaveSimplifiedFile()\nsetSaveSupportLog(BOOLEAN)\nNote\n:\ngetSaveSupportLog()\nsetOutputFolderPath(STRING)\n%AVEVA_DESIGN_WORKS%\\ModelSimplification\ngetOutputFolderPath()"}
{"Headers": "Import Operations", "Content": "Use the functionality to simplify and/or import the input file and to query the file path and any associated messages.\nsimplifyAndImport()\n\nNO RESULT\nThis function is the equivalent of the Import button on the user interface\nSimplifyOnly()\nNO RESULT\nThis function separates out some of the functionality of simplifyAndImport(BOOLEAN) for flexibility.\ngetSimplifiedFilePath()\n\nSTRING\nReturns the path of the last simplified .stp file, if saved, and an empty string otherwise.\ngetSimplificationMessage()\n\nSTRING\nReturns a string containing the messages similar to those sent to the progress window.\n\nNAME\nRESULT\nACTION\nsimplifyAndImport()\nNO RESULT\nThis function is the equivalent of the Import button on the user interface\nSimplifies the input file\nImports the simplified file into E3D Design\nSaves or deletes the simplified file, log files and any temporary files as requested.\nSimplifyOnly()\nNO RESULT\nThis function separates out some of the functionality of simplifyAndImport(BOOLEAN) for flexibility.\nSimplifies the input file and saves it\nSaves or deletes log files and any temporary files as requested.\ngetSimplifiedFilePath()\nSTRING\nReturns the path of the last simplified .stp file, if saved, and an empty string otherwise.\ngetSimplificationMessage()\nSTRING\nReturns a string containing the messages similar to those sent to the progress window.\nSimplifies the input file\nImports the simplified file into E3D Design\nSaves or deletes the simplified file, log files and any temporary files as requested.\nSimplifies the input file\nSimplifies the input file\nImports the simplified file into E3D Design\nImports the simplified file into E3D Design\nSaves or deletes the simplified file, log files and any temporary files as requested.\nSaves or deletes the simplified file, log files and any temporary files as requested.\nSimplifies the input file and saves it\nSaves or deletes log files and any temporary files as requested.\nSimplifies the input file and saves it\nSimplifies the input file and saves it\nSaves or deletes log files and any temporary files as requested.\nSaves or deletes log files and any temporary files as requested.\n\n\n\nsimplifyAndImport()\nSimplifyOnly()\ngetSimplifiedFilePath()\n.stp\ngetSimplificationMessage()"}
{"Headers": "Version Information", "Content": "Use the functionality to query the AVEVA Model Simplification version information.\ngetVersion()\n\nSTRING\nReturns a string containing the AVEVA Model Simplification version information.\n\nNAME\nRESULT\nACTION\ngetVersion()\nSTRING\nReturns a string containing the AVEVA Model Simplification version information.\n\n\n\ngetVersion()"}
{"Headers": "Error Handling", "Content": "Where possible, the set functions will raise a handleable error for invalid parameters:\nIf a license checkout fails, simplification will return false, and an error summary can be queried.\nIf a simplification completely fails (for example: a corrupt CAD file), simplification will return false, and an error summary can be queried.\nIf a simplification complete and import ran into an error, import will return false and again a string summary can be queried.\nNote:\nAt this stage we are using (130,11) messages with variable text.\n\n\n\nset\nNote\n:"}
{"Headers": "Model Simplification Import Examples", "Content": "import 'Aveva.ModelSimplification'\nusing namespace  'Aveva.ModelSimplification'\n!simplifierObj= object MODELSIMPLIFIEROBJ()\n!simplifierObj.setInputFilePath(|InputCADFilePath|)\n!simplifierObj.setSimplificationLevel(1)\n!simplifierObj.setCadFormat(|STEP|)\n!simplifierObj.setImportModelAs(|SUBE|)\n!simplifierObj.simplifyandimport()\nimport 'Aveva.ModelSimplification'\nusing namespace  'Aveva.ModelSimplification'\n!simplifierObj= object MODELSIMPLIFIEROBJ()\nQ var !simplifierObj.getOutputFolderPath()\nQ var !simplifierObj.getSimplifcationLevel()\ndefine function !!ModelSimplifcationBatchProcess()\n!inputCadFiles = ARRAY()\n!inputCadFiles.append(|InputCADFilePath|)\n!inputCadFiles.append(|InputCADFilePath|)\n!inputCadFiles.append(|InputCADFilePath|)\n!inputCadFiles.append(|InputCADFilePath|)\nusing namespace  'Aveva.ModelSimplification'\n!simplifierObj= object MODELSIMPLIFIEROBJ()\n!simplifierObj.setSimplificationLevel(1)\n!simplifierObj.setCadFormat(|STEP|)\n!simplifierObj.setImportModelAs(|SUBE|)\ndo !cadFile from 1 to !inputCadFiles.size()\n!simplifierObj.setInputFilePath(!inputCadFiles[!cadFile])\n!isSuccess = !simplifierObj.simplifyandimport()\nif(!isSuccess) then\n$p Simplification ran successfully.\nelse\n$p Simplification ran into an error\nendif\nenddo\nEndfunction\nimport 'Aveva.ModelSimplification'\nusing namespace  'Aveva.ModelSimplification'\n!simplifierObj= object MODELSIMPLIFIEROBJ()\n!simplifierObj.setInputFilePath(|InputCADFilePath|)\n!simplifierObj.setSimplificationLevel(1)\n!simplifierObj.setCadFormat(|STEP|)\n!simplifierObj.setImportModelAs(|SUBE|)\n!simplifierObj.simplifyandimport(1)\nimport 'Aveva.ModelSimplification'\nimport 'Aveva.ModelSimplification'\n\n\n\nSimple - just do it\nQuerying several of the default parameters\nBatch process using do loop\nTTY batch mode\nNote\n:\nimport 'Aveva.ModelSimplification'\nimport 'Aveva.ModelSimplification'"}
{"Headers": "MultiCAD Import", "Content": "MultiCAD Import enables the processing of files from multiple CAD software systems into an AVEVA E3D Design database. It can be run either from the AVEVA E3D Design Model user-interface, the E3D command line or a PML Object, including in batch mode.\nMultiCAD Import can import both 3D geometry and metadata from the CAD files, and the attributes imported and the model assembly structure (if any) can be explored using the MultiCAD Explorer.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"Headers": "MultiCAD Import", "Content": "The MultiCAD Import User Interface (henceforth called the MultiCAD Import in this guide enables the processing of files from multiple CAD software systems in AVEVA E3D Design.\n\n\n\nMultiCAD Import"}
{"Headers": "MultiCAD Import Window", "Content": "The MultiCAD Import window is displayed as a dockable window.\n\n\n\n\nMultiCAD Import"}
{"Headers": "MultiCAD Flexible Explorer", "Content": "The MultiCAD Flexible Explorer is displayed as a dockable window, initially docked at the right hand side of the 3D graphical view.\nThe MultiCAD model is imported into a flat structure, however, the MultiCAD file typically contains assembly information so that another view of the data may also be generated that better represents the file. The secondary MultiCAD file hierarchy is created in the Group World (GPWL), using Group Sets (GPSET) and Group Items (GPITEM).\nImported MultiCAD files define as many levels of decomposition as are necessary for the given model.\nThe model can be viewed using functionality already available in all explorers, using the right-click menu.\nNote:\nSelecting an element from the MultiCAD Flexible Explorer navigates to the equivalent element in the 3D graphical view and the Model Explorer.\nNote:\nThe node name displayed in the MultiCAD Flexible Explorer is based on the Function attribute value on the GPSET. Changing the GPSET Function attribute will change the node name in the MultiCAD Flexible Explorer.\nNote:\nRenaming elements in the MultiCAD Flexible Explorer operates on the GPSET/GPITEM hierarchy, and not on the initial imported data structure. Additionally, the configuration of the MultiCAD Flexible Explorer might mean that the displayed name of the GPSET or GPITEM is not the name displayed in the Model Explorer.\n\n\n\nMultiCAD Flexible Explorer\nNote\n:\nMultiCAD Flexible Explorer\nNote\n:\nNote\n:\nModel Explorer"}
{"Headers": "Reposition", "Content": "It is strongly advised against changing the position of elements in the hierarchical representation or any logical grouping shown in the MultiCAD Flexible Explorer. This is the representation of the model in the source file, and any kind of repositioning of elements will disrupt this representation and will probably result in a broken display.\n\n\n\nMultiCAD Flexible Explorer."}
{"Headers": "MultiCAD Flexible Explorer in Draw", "Content": "Navigate from the Model Explorer, 3D graphical view or Drawing Sheet to the equivalent MultiCAD Flexible Explorer node, provided that its parent node is expanded in the MultiCAD Flexible Explorer, or carry out the reverse.\n\n\n\nModel Explorer\nMultiCAD Flexible Explorer\nMultiCAD Flexible Explorer"}
{"Headers": "Source", "Content": "Defines the details of the imported model\u2019s source data.\n\nEnter the CAD file name in the Select a CAD File field, or browse to locate the required source file (a single CAD file), then click Open. Once the source file has been defined, click Go to next step.\n\n\n\nSelect a CAD File\nOpen\nGo to next step"}
{"Headers": "Settings", "Content": "Use the Settings window to define the settings for imported model. By default (currently) the Settings window is correctly filled in and the blue tick icon is displayed and the Import functionality is available.\n\n\n\n\nSettings"}
{"Headers": "Tolerance", "Content": "To increase the performance when displaying or working with the imported model click to check the Save Facet Data check box. (not checked by default).\nNote:\nAVEVA advise not to check the Save Facet Data check box.\n\n\n\nSave Facet Data\nNote:\nSave Facet Data"}
{"Headers": "Storage", "Content": "Use to limit the number of elements in each Level, by default the check box is selected by default.\nNote:\nA valid value must be set for No. of import elements per Level. The default value shown in the box is 100 a value of less than 25 or more than 1000 cannot be entered. If a value outside these limits is entered it will be automatically changed to the closest of the 2 limits.\nNote:\nThe AVEVA E3D Design database performs best when the number of members of each element is not excessive.\n\n\n\nNote\n:\nNo. of import elements per Level.\nNote\n:"}
{"Headers": "Reference Datum", "Content": "Use to position, orientate and scale the imported model as part of the import process. The position and orientation can be changed later using the common positioning and orientation functionality available in AVEVA E3D.\nScaling is particularly necessary if the input file does not contain units information (for example in a .stl file), or if the units information is incorrect (for example metres instead of millimetres).\nReference datums are shared between IFC Import, IFC Export and MultiCAD import, so some IFC terms are used. In particular the positioning facilities are more important when importing IFC models with geographic coordinates outside the range of the AVEVA E3D Design spatial map in earlier versions of AVEVA E3D Design.\nFor example:\nThe objects in a file have locations near 600km North and 300km West. A reference datum is created at 600km North and 300Km West. Import the file with respect to this datum, the geometry will be located in the E3D database near the origin.\nUse the Reference Datum pane of the MultiCAD Import window to select a suitable reference datum, the Use Reference Datum check box is not checked by default.\n\nUse the Reference Datum\nClick to check the check box to enable the reference datum functionality\nReference Datum\nUse to select the default, project specific reference datums or create a new reference datum.\nIFGLOBAL (default read only, no shift, rotation or scaling)\nnew Reference Datum - create a new reference datum using the Reference Datum window.\nInspect Reference Datum Properties\nDisplays the Reference Datum window populated with the name, datum properties, orientation and scale for the selected reference datum.\nDelete Reference Datum\nDeletes the selected reference datum.\nUse the Reference Datum\nClick to check the check box to enable the reference datum functionality\nReference Datum\nUse to select the default, project specific reference datums or create a new reference datum.\n\nInspect Reference Datum Properties\nDisplays the Reference Datum window populated with the name, datum properties, orientation and scale for the selected reference datum.\nDelete Reference Datum\nDeletes the selected reference datum.\nUse to review, edit or create a new reference datum, for the purposes of this guide a new reference datum will be created.\n\nAVEVA E3D DesignName\nEnter a name for the new reference datum (choose a name that is easy to identify and to reuse)\nDatum\nFormat\nDefines the position of the reference datum (use the common positioning functionality).\nOrientation\nDefines the orientation of the reference datum, default is Y is N and Z is U. Use the Orientate window to manually edit the orientate the reference datum.\nScale\nIf required, enter a scale factor (default is one).\nFor example - enter 25.4 to convert inches in the input file to mm to be written to the database.\nEdit\nEdit the position, orIentation or scale of an existing reference.\nNote:\nThis functionality is only available when an existing reference datum is selected and Inspect Reference Datum Properties is selected.\nAVEVA E3D DesignName\nEnter a name for the new reference datum (choose a name that is easy to identify and to reuse)\nDatum\n\nFormat\nDefines the position of the reference datum (use the common positioning functionality).\nOrientation\nDefines the orientation of the reference datum, default is Y is N and Z is U. Use the Orientate window to manually edit the orientate the reference datum.\nScale\nIf required, enter a scale factor (default is one).\nFor example - enter 25.4 to convert inches in the input file to mm to be written to the database.\nEdit\nEdit the position, orIentation or scale of an existing reference.\n\nUse the Reference Datum\nClick to check the check box to enable the reference datum functionality\nReference Datum\nUse to select the default, project specific reference datums or create a new reference datum.\nIFGLOBAL (default read only, no shift, rotation or scaling)\nnew Reference Datum - create a new reference datum using the Reference Datum window.\nInspect Reference Datum Properties\nDisplays the Reference Datum window populated with the name, datum properties, orientation and scale for the selected reference datum.\nDelete Reference Datum\nDeletes the selected reference datum.\nAVEVA E3D DesignName\nEnter a name for the new reference datum (choose a name that is easy to identify and to reuse)\nDatum\nFormat\nDefines the position of the reference datum (use the common positioning functionality).\nOrientation\nDefines the orientation of the reference datum, default is Y is N and Z is U. Use the Orientate window to manually edit the orientate the reference datum.\nScale\nIf required, enter a scale factor (default is one).\nFor example - enter 25.4 to convert inches in the input file to mm to be written to the database.\nEdit\nEdit the position, orIentation or scale of an existing reference.\nNote:\nThis functionality is only available when an existing reference datum is selected and Inspect Reference Datum Properties is selected.\nIFGLOBAL (default read only, no shift, rotation or scaling)\nIFGLOBAL (default read only, no shift, rotation or scaling)\nIFGLOBAL (default read only, no shift, rotation or scaling)\nnew Reference Datum - create a new reference datum using the Reference Datum window.\nnew Reference Datum - create a new reference datum using the Reference Datum window.\nnew Reference Datum - create a new reference datum using the Reference Datum window.\nNote:\nThe way in which position and orientation are designed for the IFC Import case is where the IFC file contains coordinates in a geographic coordinate system and these must be switched to position the imported objects in a more local project coordinate system.\nNote:\nThe reference datum is not where to position and orientate the object but where in the files\u2019s coordinate system to position at the E3D origin.\nNote:\nThis functionality is only available when an existing reference datum is selected and Inspect Reference Datum Properties is selected.\n\n\n\nNote\n:\nNote\n:\nReference Datum\nMultiCAD Import\nUse Reference Datum\nUse the Reference Datum\nReference Datum\nIFGLOBAL\nnew Reference Datum\nReference Datum\nInspect Reference Datum Properties\nReference Datum\nDelete Reference Datum\nName\nDatum\nFormat\nOrientation\nOrientate\nScale\nEdit\nNote\n:\nInspect Reference Datum Properties"}
{"Headers": "Import", "Content": "Use the functionality from the MultiCAD Import window to select the owning element for the imported model, which format, create a brief or full log file and specify its location and view the progress of the import along with any errors.\n\nImport Settings\nSelect Owner\nUse to choose which element the import will be added under in the hierarchy. The CE allows the current element to be selected.\nNote:\nIf the selected owner element is of the same type as the Import Model As element type, then the model is imported into that existing element, alongside an other members of that element.\nImport Model As\nUse to select what the import is classed as:\nEquipment\nVolume\nStructure\nFramework\nSub-Equipment\nSub-Volume\nSub-Structure\nSub-Frame.\nLogFile\nCreate a Log File\nCreates a log file (selected by default)\nType\nBrief\nSpecifies the level of the content in the file: brief - industry standard\nFull\nSpecifies the level of the content in the file: full - to a level where the problems can be isolated\nLocation\nUse to navigate to the required log file. Log file location field cannot be empty. If required, specify a name and alternative location.\nNote:\nWhen the source file or folder is selected on the first page, a default file name is generated based on the source name such that the log file is placed next to the source file or folder.\nProgress\nStages of the import can displayed in the Progress pane - Initialized, In Progress and Completed.\nIf import is not yet possible, a message is displayed such as 'Invalid Import Destination' to suggest what changes need to be made.\nIf an import is unsuccessful or partially successful, an error message is displayed providing further details.\nImport\nClick to start Import.\n\nSelect Owner\nUse to choose which element the import will be added under in the hierarchy. The CE allows the current element to be selected.\nImport Model As\nUse to select what the import is classed as:\n\nCreate a Log File\nCreates a log file (selected by default)\nType\n\nBrief\nSpecifies the level of the content in the file: brief - industry standard\nFull\nSpecifies the level of the content in the file: full - to a level where the problems can be isolated\nLocation\nUse to navigate to the required log file. Log file location field cannot be empty. If required, specify a name and alternative location.\nProgress\nStages of the import can displayed in the Progress pane - Initialized, In Progress and Completed.\nIf import is not yet possible, a message is displayed such as 'Invalid Import Destination' to suggest what changes need to be made.\nIf an import is unsuccessful or partially successful, an error message is displayed providing further details.\nImport\nClick to start Import.\n\nImport Settings\nSelect Owner\nUse to choose which element the import will be added under in the hierarchy. The CE allows the current element to be selected.\nNote:\nIf the selected owner element is of the same type as the Import Model As element type, then the model is imported into that existing element, alongside an other members of that element.\nImport Model As\nUse to select what the import is classed as:\nEquipment\nVolume\nStructure\nFramework\nSub-Equipment\nSub-Volume\nSub-Structure\nSub-Frame.\nLogFile\nCreate a Log File\nCreates a log file (selected by default)\nType\nBrief\nSpecifies the level of the content in the file: brief - industry standard\nFull\nSpecifies the level of the content in the file: full - to a level where the problems can be isolated\nLocation\nUse to navigate to the required log file. Log file location field cannot be empty. If required, specify a name and alternative location.\nNote:\nWhen the source file or folder is selected on the first page, a default file name is generated based on the source name such that the log file is placed next to the source file or folder.\nProgress\nStages of the import can displayed in the Progress pane - Initialized, In Progress and Completed.\nIf import is not yet possible, a message is displayed such as 'Invalid Import Destination' to suggest what changes need to be made.\nIf an import is unsuccessful or partially successful, an error message is displayed providing further details.\nImport\nClick to start Import.\nEquipment\nVolume\nStructure\nFramework\nSub-Equipment\nSub-Volume\nSub-Structure\nSub-Frame.\nEquipment\nEquipment\nVolume\nVolume\nStructure\nStructure\nFramework\nFramework\nSub-Equipment\nSub-Equipment\nSub-Volume\nSub-Volume\nSub-Structure\nSub-Structure\nSub-Frame.\nSub-Frame.\nNote:\nIf the selected owner element is of the same type as the Import Model As element type, then the model is imported into that existing element, alongside an other members of that element.\nNote:\nWhen the source file or folder is selected on the first page, a default file name is generated based on the source name such that the log file is placed next to the source file or folder.\n\n\n\nMultiCAD Import\nImport Settings\nSelect Owner\nNote\n:\nImport Model As\nImport Model As\nLogFile\nCreate a Log File\nType\nBrief\nFull\nLocation\nNote\n:\nProgress\nProgress\nInvalid Import Destination\nImport"}
{"Headers": "Import Formats", "Content": "Information is provided on IFC, STEP, STL, IGES, 2D DXF files.\n\n\n"}
{"Headers": "IFC Files", "Content": "Is the best tool for importing a significant IFC Model within the file size limits, the IFC Explorer has extra facilities to handle elements of IFC classes groups and layers, and always imports to an E3D zone and stores repeated IFC property sets efficiently.\nThe MultiCAD Explorer does not have IFC specific groupings but can import to lower level elements (for example EQUI, therefore excellent for importing components rather than whole buildings). The MultiCAD Import can potentially import somewhat larger IFC files.\n\n\n"}
{"Headers": "STEP Files", "Content": "Imports one level of any assembly hierarchy, names the E3D elements created, imports curved elements as E3D genpri elements but does not import metadata.\nImports the full assembly hierarchy (as an E3D secondary hierarchy visible in the MultiCAD Explorer). It does not name imported E3D elements, but does set descriptions. Facets curved objects on import and imports metadata.\n\n\n"}
{"Headers": "STL and IGS Files", "Content": "For a general import of STL and IGS files AVEVA recommend the use of MultiCAD import. Imports STL attempts to recognize simple primitives from STL facets and if successful can produce usable models, but in many cases produces less efficient E3D models. The terrain import continues to use the MEI import for these file types.\n\n\n"}
{"Headers": "2D DXF/DWG", "Content": "The 2D DXF/DWG Import tool is recommended for importing 2D layouts.\n\n\n"}
{"Headers": "Using the Command Line", "Content": "The command line syntax for importing a MultiCAD file or folder is illustrated below, it is a variant of the IMP command also used for MEI and IFC Imports.\nThe functionality does a number of checks dynamically before issuing an IMP command. When operating from the command line invalid data will generally result in an error, which can be handled in PML in the usual manner.\nIn these examples we will use \"W:\\example_data\\example.jt\" as a path to a CAD File.\nExample:\nThis command is the simplest form of the command - supplying a path to the CAD file, and using default values for all the other parameters. These other parameters can be added as required.\nThere are some other parameters and sub commands which apply to other variants of the IMP command, but not to IMP MULTICAD, these are not described here.\nExamples:\nThe bucketsize option is equivalent to the limit in the Storage pane of the MultiCAD Import window. The E3D Design database performs best when the number of members of each element is not excessive.\nSet a bucket size to limit, as far as possible, the number of elements in each level of the database to that number. The default is not to limit the number of members\nExamples:\nThis SCALE not displayed in the MultiCAD Import window. It applies a uniform scale to the imported model. This is combined with an scale from a reference datum and from units settings within the CAD file (if any). The default is a scale of 1.0.\nExamples:\nThis WRT option (or its IN synonym) takes a element which is typically a hidden zone whose name is that of the reference datum in the drop down list in the Reference Datum pane of the MultiCAD Import window with a suffix of -HDR. It is possible to navigate to the element in the hierarchy. The default is not to reposition, reorientate or scale the model.\nExamples:\nThis TO option is equivalent to the Select Owner field in the Import Settings pane of the MultiCAD Import window. It selects where in the E3D Design hierarchy the CAD model should be imported. Valid types are SITE, ZONE, EQUI, VOLM, STRU and FRMW, the default is the current element (CE).\nExamples:\nThis AS option is equivalent to the Import Model As drop- down list in the Import Settings pane of the MulitCAD Import window. It selects the type of E3D Element to be used as the main container element.\nValid element types are EQUI, VOLM, STRU, FRMW, SUBE, SVOLM, SUBS, SBFR (but must be compatible with the type of the TO element, for example: a SUBE cannot be created as a member of a FRMW).\nIf the TO type is the same as the AS type, then the model will be imported directly into the TO element, in addition to any members it already has.\nAny intermediate elements needed between the TO element and the AS type will be created automatically, the default is VOLM.\nExamples:\nThis GPWL option is not displayed in the MultiCAD Import window. It allows you to organize the secondary database hierarchy used for the MultiCAD Explorer.\nThe default Group World is shared with IFC import. If /IFC_Import Group World already exists in the Database then this is used as the default Group World, otherwise a Group World named /MultiCAD_Import Group World is created (if it does not already exist).\nLogging\nExamples:\nThis LOG option is equivalent to the LogFile pane of the MultiCAD Import window.\nA log file will be produced by default with a name based on that of the CAD file (the log file can be turned off). To produce a log file, select one of the options and provide a valid file path. If this is an existing file, it will be overwritten.\n\nNote:\nIn most cases when using the IMP MULTICAD command, it is better to use the SCALE option (if required) and the standard positioning and orientation commands rather than a reference datum.\n\n\n\nW:\\example_data\\example.jt\"\nIMP MULTICAD \"W:\\example_data\\example.jt\"\nIMP MULTICAD \"W:\\example_data\\example.jt\" BUCKETSIZE 50\nIMP MULTICAD \"W:\\example_data\\example.jt\" BUCK 100\nStorage\nMultiCAD Import\nIMP MULTICAD \"W:\\example_data\\example.jt\" SCALE 25.4\nIMP MULTICAD \"W:\\example_data\\example.jt\" SCALE 0.1\nMultiCAD Import\nreference datum\nIMP MULTICAD \"W:\\example_data\\example.jt\" WRT /IFCGLOBAL-HDR\nIMP MULTICAD \"W:\\example_data\\example.jt\" WRT /Scale1000-HDR\nReference Datum\nMultiCAD Import\nNote\n:\nIMP MULTICAD \"W:\\example_data\\example.jt\" TO CE\nIMP MULTICAD \"W:\\example_data\\example.jt\" TO /ZONE-XXXX\nIMP MULTICAD \"W:\\example_data\\example.jt\" TO SITE 3 of WORLD\nSelect Owner\nImport Settings\nMultiCAD Import\nIMP MULTICAD \"W:\\example_data\\example.jt\" AS EQUI\nIMP MULTICAD \"W:\\example_data\\example.jt\" AS VOLM\nImport Model As\nImport Settings\nMulitCAD Import\nIMP MULTICAD \"W:\\example_data\\example.jt\" GPWL /IFC_Import\nIMP MULTICAD \"W:\\example_data\\example.jt\" GPWL /CAD_Import_January\nMultiCAD Import\nMultiCAD Explorer.\nIMP MULTICAD \"W:\\example_data\\example.jt\" LOG OFF\nIMP MULTICAD \"W:\\example_data\\example.jt\" LOG BRIEF\nIMP MULTICAD \"W:\\example_data\\example.jt\" LOG BRIEF \"W:/logfiles/aLogfile.txt\"\nIMP MULTICAD \"W:\\example_data\\example.jt\" LOG FULL \"W:/logfiles/aLogfile.txt\"\nLogFile\nMultiCAD Import"}
{"Headers": "Structural Analysis Interface Administrator", "Content": "The Structural Analysis Interface (SAI) is a two way interface. It outputs the AVEVA E3D Design structural model into a STD file, ready to be used by Staad Pro for analysis. It can also import an STD file into an AVEVA E3D Design structural model.\n\n\n\n\n\n\n"}
{"Headers": "About this Guide", "Content": "The document provides guidance to the structural designer on how to setup and configure the Structural Analysis Interface.\nIt is assumed that the structural designer has a basic understanding of the AVEVA E3D Design software and Staad Pro software.\n\n\n"}
{"Headers": "SAI Project Setup", "Content": "This section describes the SAI project setup.\n\n\n"}
{"Headers": "Environment Variable Settings", "Content": "The interface stores the STD file and other user files in the %AVEVA_DESIGN_USER%\\SAIFiles\\ directory by default. The standard location for the %AVEVA_DESIGN_USER%\\SAIFiles\\ directory is C:\\Users\\Public\\Documents\\AVEVA\\USERDATA\\SAIFiles\\\nIf a different storage location is required, the environment variable SAI-SP can be used. To set the variable:\nCreate a folder, for example, D:\\StaadProTrans.\nAdd the following line in the evars.bat file:\nor set a project specific environment variable %abcSAISP%. Whereas abc stands for the project code. If both environment variables are set and both directories exist, the project specific directory is preferred. Write access must be granted to the desired directory.\n\n\n\nset SAISP=D:\\StaadProTrans\nabcSAISP"}
{"Headers": "User Defined Attributes", "Content": "The User Defined Attributes (UDAs) that are used in SAI are:\nUDA name\nType\nElement Types\nDescription\n:NDIST\nREAL\nSPLO\nDistance from the JLDATU of Joistart of the GENSEC to the position of the concentrated load. The distance is calculated and set by the interface during the creation or modification of the SPLOs.\n:NSDIST\nREAL\nSDLO\nDistance from the JLDATU of Joistart of the GENSEC to the start position of the distributed load. The distance is calculated and set by the interface during the creation or modification of the SPLOs.\n:NEDIST\nREAL\nSDLO\nDistance from the JLDATU of Joistart of the GENSEC to the end position of the distributed load. The distance is calculated and set by the interface during the creation or modification of the SPLOs.\n:MRELEASE\nREF\nRELE\nUsed for storing MEMBER RELEASE information for Staad Pro. The fixing of the connecting GENSEC of a release member. The attribute is set by the interface when the node release attribute is set.\nUDA name\nType\nElement Types\nDescription\n:NDIST\nREAL\nSPLO\nDistance from the JLDATU of Joistart of the GENSEC to the position of the concentrated load. The distance is calculated and set by the interface during the creation or modification of the SPLOs.\n:NSDIST\nREAL\nSDLO\nDistance from the JLDATU of Joistart of the GENSEC to the start position of the distributed load. The distance is calculated and set by the interface during the creation or modification of the SPLOs.\n:NEDIST\nREAL\nSDLO\nDistance from the JLDATU of Joistart of the GENSEC to the end position of the distributed load. The distance is calculated and set by the interface during the creation or modification of the SPLOs.\n:MRELEASE\nREF\nRELE\nUsed for storing MEMBER RELEASE information for Staad Pro. The fixing of the connecting GENSEC of a release member. The attribute is set by the interface when the node release attribute is set.\nThe UDAs are included in the AVEVA E3D Design project.\nTo manually set the UDAs, a datal is provided during installation of the interface. The file sai_uda_install_or_upgrade.mac is stored in [AVEVA E3D Design Installation Path]\\data, the UDAs can be setup in AVEVA Administration:\nUDA name\nType\nElement Types\nDescription\n:NDIST\nREAL\nSPLO\nDistance from the JLDATU of Joistart of the GENSEC to the position of the concentrated load. The distance is calculated and set by the interface during the creation or modification of the SPLOs.\n:NSDIST\nREAL\nSDLO\nDistance from the JLDATU of Joistart of the GENSEC to the start position of the distributed load. The distance is calculated and set by the interface during the creation or modification of the SPLOs.\n:NEDIST\nREAL\nSDLO\nDistance from the JLDATU of Joistart of the GENSEC to the end position of the distributed load. The distance is calculated and set by the interface during the creation or modification of the SPLOs.\n:MRELEASE\nREF\nRELE\nUsed for storing MEMBER RELEASE information for Staad Pro. The fixing of the connecting GENSEC of a release member. The attribute is set by the interface when the node release attribute is set.\nNote:\nFor customers who have installed previous versions (pre 12.0.SP6) of the Structural Analysis Interface, this macro must be run to upgrade the UDA settings. Data in UDAs stored in previously defined projects is not affected.\n\n\n\nUDA name\nType\nElement Types\nDescription\n$M [AVEVA E3D Design Installation Path]\\data\\sai_uda_install_or_upgrade.mac\nNote:"}
{"Headers": "Access Rights", "Content": "During output of the model, the num attributes of JLDATU, ENDATU and GENSEC are updated. The structural engineer that performs the model extraction must have write access to this attribute.\nThe Purpose attribute of GENSEC elements can also be updated by clicking Set Section Types on the Model Extraction part of the Structural Analysis Interface window during model extraction to a Staad Pro STD file.\n\n\n\nSet Section Types\nStructural Analysis Interface"}
{"Headers": "Set the Mapping File", "Content": "The mapping file is used to define the relationship between AVEVA E3D Design profile specifications and the Staad Pro profiles. The mapping file is named SAImap.pmldat and is located in the %AVEVA_DESIGN_USER%\\SAIFiles\\ directory after installation. If using an environment variable (refer to Environment Variable Settings for further information) to define another storage location you must copy this file to the required location. Mapping is required during the extraction of the model. The mapping file is compatible with the AVEVA E3D Design steel profile catalog. A mapping file for use with the previous steel profile catalog is included in the %AVEVA_DESIGN_USER%\\SAIFiles\\ directory and is named SAImap_Old_Catalogue.pmldat, to use this file, it must be renamed to SAImap.pmldat.\n\n\n\nEnvironment Variable Settings\nEnvironment Variable Settings"}
{"Headers": "Mapping File Contents", "Content": "The mapping file structure consists of three sections.\nIf multiple standards are used, the three sections can be repeated. '*' is used to allow comments in the mapping file.\nMEMBER PROPERTY section to define the Staad Pro database used;\nProfile mapping from Staad Pro to the AVEVA E3D Design profiles;\nUSERTABLES section to define the USER PROVIDED TABLE used.\nMEMBER PROPERTY section to define the Staad Pro database used;\nMEMBER PROPERTY section to define the Staad Pro database used;\nProfile mapping from Staad Pro to the AVEVA E3D Design profiles;\nProfile mapping from Staad Pro to the AVEVA E3D Design profiles;\nUSERTABLES section to define the USER PROVIDED TABLE used.\nUSERTABLES section to define the USER PROVIDED TABLE used.\n\n\n"}
{"Headers": "Keywords", "Content": "Two keywords divide the mapping file into different sections.\nMEMBER PROPERTY\nMEMBER PROPERTY defines the Staad Pro profile database used. The MEMBER PROPERTY keyword, followed by the standard profile database name, sets the profile database. An example of a British profile is:\nUSERTABLES\nUSERTABLES define the path of the USER PROVIDED TABLE ( UPTABLE ). The TABLE keyword followed by the <table num> and the Table file sets the used UPT. An example of an UPTABLE is:\nThe USER PROVIDED TABLE is usually generated and maintained in Staad Pro, which contains defined profiles used in Staad Pro. After the UPTABLE is created, the path of this file can be added into the mapping file below the keyword \"USERTABLES\".\n\n\n"}
{"Headers": "Profile Mapping", "Content": "The profile mapping consists of six columns delimited by ',' .The description of the six columns is:\n\n\n"}
{"Headers": "Column 1: Staad Pro Profiles", "Content": "The column contains information about the Staad Pro profile. There are various profile types in Staad Pro and they are:\n\n\n"}
{"Headers": "Standard Profile", "Content": "The Staad Pro profile name is used. The keyword TABLE is used followed by the profile name. For example, 'TABLE ST UC305X305X240'.\n\n\n"}
{"Headers": "Prismatic Sections", "Content": "The keyword is PRIS followed by <variable><value> pair. For example, a rectangle section with YD and ZD variables is defined with the depth and width defined in column 3:\nPRIS YD <depth*0.001> ZD <width*0.001>\n\n\n"}
{"Headers": "User Provided Table", "Content": "The \"UPTABLE num\" keyword followed by a variable description can be used to UPT profiles. The num must be defined in the previous section of the mapping file. For example:\nWhen the variables are defined in column 3.\nNote:\nDot(.) of profile name is not supported in the current version of SAI. 88.9_OD_5.5 and must be replaced by 88_OD_5 in the USER PROVIDED TABLE.\nNote:\nProfile names in STAAD Pro must follow a rule, rules can be generated for profiles of the same type.\nFor example, if there are two profiles called 88.9_OD_5.5 and 114.3OD8.6 in the USER PROVIDED TABLE, they can be better named as 88_OD_5 and 114_OD_8 respectively. A naming rule can be defined as <int(d1)>_OD_<int(d2)>. The suffix n in dn must follow the definition in the mapping file defined in column 3.\n\n\n\nNote:\nNote:"}
{"Headers": "Column 2: AVEVA E3D Design Reference", "Content": "The column contains the AVEVA E3D Design SPCO reference. For example:\nTABLE ST UC305X305X240  ,/BS-UC305x305x240\n\n\n"}
{"Headers": "Column 3: Design Parameters", "Content": "The column is used to name all the design parameters used in column 1. The names must not contain spaces. The names are read from left to right with the word on the left assigned to DESPARA 1. If only DESPARA 2 and DESPARA 3 are used, a DUMMY word is required to fill the gap for DESPARA 1. For example\nBased on this definition, if the GENSEC despara are 20 14 30, then the /Profile/Variable-SPCO is mapped to profile W14X30 in table 1 of UPT.\nUPTABLE 1 W<Heig>X<Widt>, /Profile/Variable-SPCO, despA Heig Widt\nNote:\nWhen a profile is a parametric profile, one record in the mapping file can be matched with several records in the USER PROVIDED TABLE.\nFor example, when the parameters are 20 14 30, the profile in the example is named W14X30 in Staad Pro. And when the parameters are 30 28 60, the profile is named W28X60. In this case, there must be at least two profiles in the USER PROVIDED TABLE matching the record W<Heig>X<Widt>.\n\n\n\nNote:"}
{"Headers": "Column 4: Mapping of UPTABLE Parameters", "Content": "The column is used while importing the Staad Pro model to AVEVA E3D Design. While importing the defined profiles, the interface can assess the UPTABLE parameters and the AVEVA E3D Design design parameters, and calculate the design parameters according to the values in the UPTABLE.\nFor example, the USER PROVIDED TABLE can be:\nWide Flange indicates that the UPTABLE is an UPTABLE of the \"H\" shape profile.\nH6003001220 is the name of the defined profile.\nThe numbers in the fourth line are the parameters of the shape for this profile. For the H profile, the 2nd number \"0.600000\" is the depth of the profile, the 4th number \"0.300000\" is width, the 3rd number \"0.012000\" is the web thickness and the 5th number \"0.020000\" is the flange thickness of the profile.\nWith those four parameters, the shape of the profile is defined. The other parameters are the analysis data of the profile in Staad Pro that are not used in AVEVA E3D Design.\nTo add the specification /DESPAR-SPEC/Beam_with_design_parameters into the mapping file, set Column 4:\nIn the specification /DESPAR-SPEC/Beam_with_design_parameters, d1 is the depth of the profile (d1 is the first design parameter of the GENSEC), d2 is the width, d3 is the web thickness and d4 is the flange thickness.\nThe order of this column is the same as the USER PROVIDED TABLE. In Column 4 of the example, only five parameters are added. The first one \"0\" is a dummy parameter. The 2nd one \"<0.001*d1>\" is an expression (expressions or variables are included in the bracket \"<>\"), <0.001*d1=2nd parameter in UPTABLE>. While importing, the interface calculates d1 by this expression.\nThe column does not affect the output function.\nUnit met\nWide Flange\nH6003001220\n0.018720 0.600000 0.012000 0.300000 0.020000 0.001185 0.000090 0.000002 0.007200 0.008000\nUPTABLE 1 H<int(d1)><int(d2)><int(d3)><int(d4)>,/DESPAR-SPEC/Beam_with_design_parameters,d1\n      d2 d3 d4 ,0 <0.001*d1> <0.001*d3> <0.001*d2> <0.001*d4>\n   \nNote:\nIf the parameters cannot be matched with the design parameters of the GENSEC in AVEVA E3D Design directly, expressions can be used.\n\n\n\nNote:"}
{"Headers": "Column 5 and 6: Profile Angle", "Content": "The interface only supports Y is U for Staad Pro. The Profile angle is the difference in angle between the AVEVA E3D Design profile and the Staad Pro profile. The method to set the angle is:\nDisplay the AVEVA E3D Design profile in Paragon:\n\nManually create a section in Staad Pro for the profile that is to be transferred from AVEVA E3D Design. In this case, the ST Angle profile is the correct profile.\nThe section is extruded in the global Z direction in decreasing Z direction. That is, the start point Z co-ordinate is larger than the end point. The view of the section from the Z axis is:\n\nRotate the Staad Pro section using the beta angle property until it is identical to the AVEVA E3D Design view. The angle is 75.6582 for the ST angle profile.\n\nThe value of column 5 is 75.6582 or the beta angle.\nThe value of column 6 is -14.3418 or -90 from column 5.\n\n\n"}
{"Headers": "Column 7: Mirror Flag", "Content": "In some cases, particularly with angle profiles, the profile shape must be mirrored to match the AVEVA E3D Design profile and the Staad Pro profile.\nThis value must be set to 1 to mirror the profile, or 0 to not mirror it.\n\n\n"}
{"Headers": "Column 8: Additional Parameters for Importing", "Content": "Column 8 is used when importing the Staad Pro model to AVEVA E3D Design. The column does not affect the output function.\nColumn 4 is used to assess the parameters in the USER PROVIDED TABLE and the AVEVA E3D Design design parameters. In some cases, the AVEVA E3D Design design parameters cannot be transferred to the USER PROVIDED TABLE directly, this column is used to modify the design parameters to make them available for transfer.\nThe specification is used, for example, /DESPAR-SPEC/Beam_with_design_parameters. The parameter values are set in Column 4. Refer to Column 4: Mapping of UPTABLE Parameters for further information:\nIf the model is imported with the parameters defined in Column 4. The model displays as:\n\nThe specification uses the parameter Depth Between Fillets (design parameter 8) to define the depth between the fillets and the parameter is not set. In this case, an expression can be added to define design parameter 8:\nAdd the parameters from d5 to d8. D5 to d7 are dummy parameters. Then add the expression \"d8=d1-d3*2\" to Column 8, the correct parameters can then be imported:\n\nAdditional expressions can be added to Column 8, these expressions must be split by a semicolon \";\".\nUPTABLE 1 H<int(d1)><int(d2)><int(d3)><int(d4)>,/DESPAR-SPEC/Beam_with_design_parameters,d1\n      d2 d3 d4 ,0 <0.001*d1> <0.001*d3> <0.001*d2> <0.001*d4>,0,-90\n   \nUPTABLE 1 H<int(d1)><int(d2)><int(d3)><int(d4)>,/DESPAR-SPEC/Beam_with_design_parameters,d1\n      d2 d3 d4 d5 d6 d7 d8,0 <0.001*d1> <0.001*d3> <0.001*d2> <0.001*d4>,0,-90,0, d8=d1-d3*2\n   \n\n\n\nColumn 4: Mapping of UPTABLE Parameters\nColumn 4: Mapping of UPTABLE Parameters"}
{"Headers": "Complete Definition Examples", "Content": "TABLE ST UC305X305X240  ,/BS-UC305x305x240    ,,,0,-90\nThe GENSEC with spref ,/BS-UC305x305x240 is output as TABLE ST UC305X305X240 .\nPRIS YD <depth*0.001> <width*0.001>, -BEAMS-SPEC/Rectangular_Profile, depth width, , 0, 90\nThe GENSEC is with spref /CONCRETE-BEAMS-SPEC/Rectangular_Profile, and despara 500\n      and 300, is output as PRIS YD 0.5 ZD 0.3.\n   \nUPTABLE 1 W<Heig>X<Widt>, /Profile/Variable-SPCO, despA Heig Widt , , 0, -90\nThe GENSEC is with spref /Profile/Variable-SPCO, and despara 100, 14 30, is output\n      as UPT 1 W14X30.\n   \nDue to the definition of the UPT in section 1, the output is:\nSTART USER TABLE\nTABLE 1 c:\\Staad Pro\\Table1.std\nEND\n\n\n"}
{"Headers": "Worked Example", "Content": "The example indicates how to set the profile mapping.\n\n\n"}
{"Headers": "Data from the STD File", "Content": "It is assumed that an STD file, named D:\\Staad\\model.std, must be imported into AVEVA E3D Design. The STD file contains (in the example, some text has been removed for visual representation):\nIn this STD file, find the records after the keyword \"START USER TABLE\":\nThe STD file references two USER PROVIDED TABLEs: D:\\Staad\\map1.txt and D:\\Staad\\map2.txt.\nThe data in the file D:\\Staad\\map1.txt is:\nThe data in the file D:\\Staad\\map2.txt is:\nD:\\Staad\\map1.txt describes the H sections using a name value, for example, \"H1800X400X30X40\". D:\\Staad\\map2.txt describes the PIPE sections using a name value, for example, \"90_OD_5\".\nSTART JOB INFORMATION\nENGINEER DATE 1-Jan-11\nEND JOB INFORMATION\nUNIT METER kN\nINPUT WIDTH 79\nJOINT COORDINATES\n       3               7.785               8.930               1.510\n       4               7.785               5.880               1.510\n   .......\nMEMBER INCIDENCES\n   10044          45          22\n   ........\nDEFINE MATERIAL START\nISOTROPIC STEEL\n   \u2026\u2026\nEND DEFINE MATERIAL\nSTART USER TABLE\nTABLE 1 D:\\Staad\\map1.txt\nTABLE 2 D:\\Staad\\map2.txt\nEND\nMEMBER PROPERTY BRITISH\n 10001 10004 10007 10010 10013 10016 10019 TABLE ST UC305X305X240\n    ......\nMEMBER PROPERTY\n 31 50 33 51 36 52 53 38 54 55 40 56 57\n  UPTABLE 1 H1800X400X30X40\n 43 58 59 60 44 45 61 46 62 47 63 49 64 -\n 65 10044 UPTABLE 2 90_OD_5\nSTART USER TABLE\nTABLE 1 D:\\Staad\\map1.txt\nTABLE 2 D:\\Staad\\map2.txt\nEND\nUNIT METER KN\nWide Flange\nH2000X400X20X40\n0.0704 2 0.02 0.4 0.04 0.0425336 0.000427947 2.21867e-005 0.04 0.02112\nH1800X400X30X40\n0.0836 1.8 0.03 0.4 0.04 0.0375062 0.000430537 3.25467e-005 0.054 0.02112\nH1600X400X30X40\n0.0776 1.6 0.03 0.4 0.04 0.0282526 0.000430087 3.07467e-005 0.048 0.02112\n\u2026\u2026\nUNIT METER KN\nPIPE\n90_OD_5\n0.0905 0.0055 0.000729 0.000729\n114_OD_6\n0.114 0.00602 0.001021 0.001021\n\u2026\u2026\nNote:\nThe interface uses a single mapping configuration file for importing STD files and exporting AVEVA E3D Design models. A \"strong\" naming convention must be used for profiles in Staad Pro, rules using parameters can then be set up in a clear and simple way, achieving \"one-to-one\" mapping.\nNote:\nIn cases when the profile naming rules result in a N-to-One mapping from STD profiles to AVEVA E3D Design specifications, incorrectly mapped profile names may be present. When the model is exported, the interface uses the first rule applicable.\n\n\n\nNote:\nNote:"}
{"Headers": "Add Data to the Mapping File", "Content": "Data can be added to the mapping file. It is assumed that the mapping file is a new file.\nAdd the records after the \"USERTABLES\" keyword to describe the two USER PROVIDED TABLEs:\nAdd the \"MEMBER PROPERTY\" keyword and add the records for the profiles in the two referenced files.\nIn the specification /DESPAR-SPEC/Beam_with_design_parameters, d1 is the depth of the profile (d1 is the first design parameter of the GENSEC), d2 is the width, d3 is the web thickness and d4 is the flange thickness. The profile can be named \"H<int(d1)>X<int(d2)>X<int(d3)>X<int(d4)>\" (the int() function is added the to make sure the parameters are in the name is an integer).\nThe first six record columns are defined in the mapping file:\nThe final line of the H profiles is defined:\nSet the profile of the PIPE section and the profiles after the keyword \"MEMBER PROPERTY\" are defined:\nCheck for standard profiles in the STD file and add their mapping records.\nThe profile \"TABLE ST UC305X305X240\" is used in the STD file. Add this profile to the mapping file:\nThe mapping file is completed:\nUSERTABLES\nTABLE 1 D:\\Staad\\map1.txt\nTABLE 2 D:\\Staad\\map2.txt\nUPTABLE 1 H<int(d1)>X<int(d2)>X<int(d3)>X<int(d4)> , /DESPAR-SPEC/Beam_with_design_parameters,d1\n      d2 d3 d4 d5 d6 d7 d8,0 <0.001*d1> <0.001*d3> <0.001*d2> <0.001*d4>,\n   \nUPTABLE 1 H<int(d1)>X<int(d2)>X<int(d3)>X<int(d4)> , /DESPAR-SPEC/Beam_with_design_parameters,d1 d2 d3 d4 d5 d6 d7 d8,0 <0.001*d1> <0.001*d3>\n      <0.001*d2> <0.001*d4> ,0,-90,0,d8=d1-d3*2;\n   \nUPTABLE 2 <int(d1)>_OD_<int(d2)>,/DESPAR-SPEC/Tube_with_design_parameters,d1 d2 d3,<0.001*d1>\n      <0.001*d1 - 0.001*d2*2> <0.001*d3>,0,-90\n   \nMEMBER PROPERTY BRITISH\nTABLE ST UC305X305X240  ,/BS-UC305x305x240    ,,,0,-90\nUSERTABLES\nTABLE 1 D:\\Staad\\map1.txt\nTABLE 2 D:\\Staad\\map2.txt\nMEMBER PROPERTY\nUPTABLE 1 H<int(d1)>X<int(d2)>X<int(d3)>X<int(d4)> , /DESPAR-SPEC/Beam_with_design_parameters,d1 d2 d3 d4 d5 d6 d7 d8,0 <0.001*d1> <0.001*d3>\n      <0.001*d2> <0.001*d4> ,0,-90,0,d8=d1-d3*2;\n   \nUPTABLE 2 <int(d1)>_OD_<int(d2)>,/DESPAR-SPEC/Tube_with_design_parameters,d1 d2 d3,<0.001*d1> <0.001*d1 .001*d2*2> <0.001*d3>,0,-90\nMEMBER PROPERTY BRITISH\nTABLE ST UC305X305X240  ,/BS-UC305x305x240    ,,,0,-90\nD:\\Staad\\map1.txt describes the H sections. The AVEVA E3D Design specification /DESPAR-SPEC/Beam_with_design_parameters is used to represent the profile in AVEVA E3D Design.\nD:\\Staad\\map1.txt contains the name of the H sections, for example, \"H1800X400X30X40\". The naming rule is H<Height>X<Width>X<int(d3)>X<int(d4)>.\nFor the \"H\" profile in the USER PROVIDED TABLE, the 2nd number is the depth of the profile, the 4th number is width, the 3rd number is the web thickness and the 5th number is the flange thickness of the profile.\nD:\\Staad\\map1.txt describes the H sections. The AVEVA E3D Design specification /DESPAR-SPEC/Beam_with_design_parameters is used to represent the profile in AVEVA E3D Design.\nD:\\Staad\\map1.txt describes the H sections. The AVEVA E3D Design specification /DESPAR-SPEC/Beam_with_design_parameters is used to represent the profile in AVEVA E3D Design.\nD:\\Staad\\map1.txt contains the name of the H sections, for example, \"H1800X400X30X40\". The naming rule is H<Height>X<Width>X<int(d3)>X<int(d4)>.\nD:\\Staad\\map1.txt contains the name of the H sections, for example, \"H1800X400X30X40\". The naming rule is H<Height>X<Width>X<int(d3)>X<int(d4)>.\nFor the \"H\" profile in the USER PROVIDED TABLE, the 2nd number is the depth of the profile, the 4th number is width, the 3rd number is the web thickness and the 5th number is the flange thickness of the profile.\nFor the \"H\" profile in the USER PROVIDED TABLE, the 2nd number is the depth of the profile, the 4th number is width, the 3rd number is the web thickness and the 5th number is the flange thickness of the profile.\nColumn 5 and column 6 can be set according to the methods Column 5 and 6: Profile Angle. Column 7 can be set according to the method Column 7: Mirror Flag. Column 8 can be set according to the method Column 8: Additional Parameters for Importing.\nColumn 5 and column 6 can be set according to the methods Column 5 and 6: Profile Angle. Column 7 can be set according to the method Column 7: Mirror Flag. Column 8 can be set according to the method Column 8: Additional Parameters for Importing.\nColumn 5 and column 6 can be set according to the methods Column 5 and 6: Profile Angle. Column 7 can be set according to the method Column 7: Mirror Flag. Column 8 can be set according to the method Column 8: Additional Parameters for Importing.\n\n\n\nColumn 5 and 6: Profile Angle\nColumn 7: Mirror Flag\nColumn 8: Additional Parameters for Importing\nColumn 5 and 6: Profile Angle\nColumn 7: Mirror Flag\nColumn 8: Additional Parameters for Importing"}
{"Headers": "Set the Material Mapping File", "Content": "GENSEC materials are based on the MATREF attribute of the GENSEC element. Rules are used to determine the material of the section.\n\n\n"}
{"Headers": "Material Reference (MATREF) Unset", "Content": "\nMaterial Property is set to STEEL.\n\n\n"}
{"Headers": "Material Reference (MATREF) Set", "Content": "When the MATREF is set, the SOLI element, that it references in the property database, determines the Material Property exported.\nWhen Built-in Names of Staad Pro are used:\n\nIf the DESC attribute of the SOLI element is set to \"STEEL\",\"CONCRETE\" or \"ALUMINUM\", the material property of the GENSEC in Staad Pro is set to the built-in properties of Staad Pro.\n\n\n"}
{"Headers": "When User-Defined Property is required", "Content": "When the DESC attribute of the SOLI element is not a Staad Pro built-in name, then it is assumed to be a user defined Staad Pro material. Elements (indicated as boxes in the example) may need to be created under the SOLI element, and the attributes of the created elements (indicated as ellipses in the example) must also be set:\n\n\n\n"}
{"Headers": "SOLI Element", "Content": "The DESC attribute of the SOLI element stores the name of the material in Staad Pro and the key word of the material type in Staad Pro. Keyword \"ISO\" or \"2DO\" is required as a prefix in the DESC attribute with \"/\". ISO is used for Isotropic and 2DO is used for OrthoTropic2D.\nThe system reads the members of the SOLI element and extracts the first instance of a particular property with an SREF set to ST/xxxxx where \"ST/\" is the key word to identify the element and \"xxxxx\" is the material property name in Staad Pro. The material properties values are set in the child elements of the SOLI element. There are no units to the values and the units must be compatible.\nIf there are 2 TAPR elements with Sref set to ST/CDAMP, only the first TAPR is read. The APROPERTY attribute of the first member wtih hardtype TAPR (the type is SAPR in the example) is the attribute to be extracted.\n\n\n"}
{"Headers": "Accurate Material Properties", "Content": "When more accurate material properties are required, a TEXT type UDA :STPROP can be created. The interface uses the value from this TEXT UDA rather than the real number. The number of significant figures increases if required.\n\n\n"}
{"Headers": "Features of SAI", "Content": "The SAI application features are:\nVarious types of data in the STD file can be transferred between AVEVA E3D Design and the STD file:\nType\nAVEVA E3D Design Type\nRemark\nNode elements\nJLDATU, ENDATU\nBeam elements\nGENSEC\nPlate elements\nPANE\nGROUP DEFINITION\nGPSET\nGroup definitions can only be imported from the STD file. The imported model can then be extracted to STD from AVEVA E3D Design with the imported group definitions.\nMEMBER RELEASES\nRELE\nSUPPORTS\nENDATU\nFixed, Fixed But and Pinned supports in STD are available.\nLoad Case\nLCDE\nThe available load cases are:\nNone\nDead\nLive\nWind\nRoof Live\nSeismic\nSnow\nFluids\nSoil\nRain Water / Ice\nPonding\nDust\nTraffic\nTemperature\nAccidental\nFlood\nIce\nWind on Ice\nCrane Hook\nGravity\nPush\nNodal Load\nNOLO\nNodal displacement\nNODI\nMember Load: Uniform Force, Uniform Moment, Trapezoida\nSDLO\nMember Load: Concentrated Force, Concentrated Moment,\nSPLO\nType\nAVEVA E3D Design Type\nRemark\nNode elements\nJLDATU, ENDATU\n\nBeam elements\nGENSEC\n\nPlate elements\nPANE\n\nGROUP DEFINITION\nGPSET\nGroup definitions can only be imported from the STD file. The imported model can then be extracted to STD from AVEVA E3D Design with the imported group definitions.\nMEMBER RELEASES\nRELE\n\nSUPPORTS\nENDATU\nFixed, Fixed But and Pinned supports in STD are available.\nLoad Case\nLCDE\nThe available load cases are:\nNone\nDead\nLive\nWind\nRoof Live\nSeismic\nSnow\nFluids\nSoil\nRain Water / Ice\nPonding\nDust\nTraffic\nTemperature\nAccidental\nFlood\nIce\nWind on Ice\nCrane Hook\nGravity\nPush\nNodal Load\nNOLO\n\nNodal displacement\nNODI\n\nMember Load: Uniform Force, Uniform Moment, Trapezoida\nSDLO\n\nMember Load: Concentrated Force, Concentrated Moment,\nSPLO\n\n\nType\nAVEVA E3D Design Type\nRemark\nNode elements\nJLDATU, ENDATU\nBeam elements\nGENSEC\nPlate elements\nPANE\nGROUP DEFINITION\nGPSET\nGroup definitions can only be imported from the STD file. The imported model can then be extracted to STD from AVEVA E3D Design with the imported group definitions.\nMEMBER RELEASES\nRELE\nSUPPORTS\nENDATU\nFixed, Fixed But and Pinned supports in STD are available.\nLoad Case\nLCDE\nThe available load cases are:\nNone\nDead\nLive\nWind\nRoof Live\nSeismic\nSnow\nFluids\nSoil\nRain Water / Ice\nPonding\nDust\nTraffic\nTemperature\nAccidental\nFlood\nIce\nWind on Ice\nCrane Hook\nGravity\nPush\nNodal Load\nNOLO\nNodal displacement\nNODI\nMember Load: Uniform Force, Uniform Moment, Trapezoida\nSDLO\nMember Load: Concentrated Force, Concentrated Moment,\nSPLO\nAbility to apply various structural loads;\nUse of a mapping file to map AVEVA E3D Design profiles to Staad Pro profile;\nAVEVA E3D Design structural model check and correction tools;\nOutput of Staad Pro STD file;\nImport of Staad Pro STD file into an AVEVA E3D Design structural model.\nRead a modified Staad Pro STD file that is initially exported from AVEVA E3D Design to update profile changes.\nAbility to apply various structural loads;\nAbility to apply various structural loads;\nUse of a mapping file to map AVEVA E3D Design profiles to Staad Pro profile;\nUse of a mapping file to map AVEVA E3D Design profiles to Staad Pro profile;\nAVEVA E3D Design structural model check and correction tools;\nAVEVA E3D Design structural model check and correction tools;\nOutput of Staad Pro STD file;\nOutput of Staad Pro STD file;\nImport of Staad Pro STD file into an AVEVA E3D Design structural model.\nImport of Staad Pro STD file into an AVEVA E3D Design structural model.\nRead a modified Staad Pro STD file that is initially exported from AVEVA E3D Design to update profile changes.\nRead a modified Staad Pro STD file that is initially exported from AVEVA E3D Design to update profile changes.\n\n\n\nType\nAVEVA E3D Design Type\nRemark"}
{"Headers": "Staad Pro Model Transfer", "Content": "In this section, the transfer concepts of the AVEVA E3D Design model to Staad Pro is discussed.\n\n\n"}
{"Headers": "GENSEC Types", "Content": "In AVEVA E3D Design, all GENSEC elements must be classified as COLUmns, BEAMs or BRACes for the interface to work. This is set in the Purpose attribute of the COLU, BEAM, BRAC and ROOF respectively. It can be set to individual GENSECs or to a higher level hierarchy. The reason for setting the purpose attribute is explained, refer to Hierarchy for further information.\nCOLUmns are GENSECs which are the main supporting column for the structure. These are usually the vertical columns in the model.\nBEAMs are the major horizontal GENSECs of the structural model. These are normally the GENSEC in the E-W, N-S directions of the structure.\nBRACes are the GENSECs that are used for strengthening the structure and are usually in non-orthogonal directions.\nA utility is provided by the interface to scan the hierarchy and set the GENSEC with the default purpose, it is not necessary to set this information manually.\n\n\n\nHierarchy\nHierarchy"}
{"Headers": "AVEVA E3D Design Model Extraction", "Content": "During the model extraction, the COLUmns are the first set of GENSECs that are scanned. Hence their end points and JLDATU are taken as the reference node positions. Following the COLUmns, the BEAMs are scanned and the BEAM end points are merged with the COLUmn reference node positions. The BRACes are the last GENSECs to be scanned. They take reference from the COLUmn and BEAM nodal positions.\n\n\n"}
{"Headers": "SAI Interface Modelling Requirements", "Content": "This section describes the SAI interface modelling requirements.\n\n\n"}
{"Headers": "Units and Up Direction", "Content": "The interface only allows SI units (Meter/kN) to be used when the AVEVA E3D Design project is a metric project, and Imperial units (Feet/KIP) when the AVEVA E3D Design project is an imperial project. The Up direction output is a standard Staad Pro convention which is Y.\n\n\n"}
{"Headers": "Connections", "Content": "All GENSECs must be connected correctly. Staad Pro nodes are derived from AVEVA E3D Design JLDATU for connected GENSEC elements, and ENDATU for free GENSEC ends. For Support in Staad Pro, the Fixity attribute of the ENDATU is set to FIXED or PINNED to define the end as a fixed/pinned support for free ends.\nWhen using the Beams & Columns application to create braces, care must be taken in ensuring correct JLDATU creation. Braces are preferably created by Bracing Configurations which make sure the correct JLDATU is created.\n\nErrors in Brace modelling result in the output on the right.\n\nUsing Bracing Configuration with the correct JLDATU created.\nWhen a GENSEC spans through another GENSEC element, the split functionality must be used to split the GENSEC, otherwise the connections between the intersection points are not created in the Staad Pro output, resulting in an error.\n\n\n"}
{"Headers": "Hierarchy", "Content": "The GENSECs are set as COLUmns, BEAMs or BRACes using the Purpose attribute. During output, the hierarchy can be defined. The hierarchy may be defined as GENSEC, SBFR, FRMW or STRU. Only GENSEC that have the Purpose attribute set as COLU, BEAM or BRAC are extracted. The model extraction process is explained. Refer to AVEVA E3D Design Model Extraction for further information.\nFor example, use FRMW as the hierarchy; the hierarchy setting should be:\nElement Type\nElement Name\nPurpose Attribute\nRemark\nFRMW\n/Columns\nCOLU\nHierarchy to store columns\nFRMW\n/Beams\nBEAM\nHierarchy to store beams\nFRMW\n/Braces\nBRAC\nHierarchy to store braces\nFRMW\n/Panels\nPANE\nHierarchy to store panels\nElement Type\nElement Name\nPurpose Attribute\nRemark\nFRMW\n/Columns\nCOLU\nHierarchy to store columns\nFRMW\n/Beams\nBEAM\nHierarchy to store beams\nFRMW\n/Braces\nBRAC\nHierarchy to store braces\nFRMW\n/Panels\nPANE\nHierarchy to store panels\n\nElement Type\nElement Name\nPurpose Attribute\nRemark\nFRMW\n/Columns\nCOLU\nHierarchy to store columns\nFRMW\n/Beams\nBEAM\nHierarchy to store beams\nFRMW\n/Braces\nBRAC\nHierarchy to store braces\nFRMW\n/Panels\nPANE\nHierarchy to store panels\n\n\n\nAVEVA E3D Design Model Extraction\nAVEVA E3D Design Model Extraction\nElement Type\nElement Name\nPurpose Attribute\nRemark"}
{"Headers": "Justification", "Content": "The interface recommends that NA is used as the Justification for columns and braces. CTOP is used as the Justification for beams (or TOS if using the old steel profile catalogue).\nIn Staad Pro, the centre line is used as a reference. Hence the output from the model has all profile strings together assuming the line between the nodes lies along the centre.\nThe offset switch outputs with an offset to compensate for the justification of the beam. Only the height is compensated with offset. The example displays the Model output without Output Offset.\n\nThe example displays the Model output with Output Offset.\n\n\n\n"}
{"Headers": "Node Tolerance", "Content": "\nNodes that are too close can be merged into one node when outputting the model. The node tolerances can be defined using the Settings part of the Structural Analysis Interface window.\nFor example, if there is a beam connected to a column and a brace connecting to the same column but with a different JLDATU, the two JLDATUs are merged if their distance is less than the node tolerance. The example displays JLDATUs of Braces merged to JLDATUs of Beams.\n\nRefer to Settings for further information.\n\n\n\nSettings\nSettings\nStructural Analysis Interface\nSettings"}
{"Headers": "Panels and Floors", "Content": "Panels and floors are output as Staad Pro plate elements.\nWhen panels or floors are built at the corner of GENSECs, the distance between the point of the plate and the centre line of the GENSEC may be too big so that the output model of the plate are separated from the main structure. When set, the Panel Tolerance in the Settings part of the Structural Analysis Interface window causes the interface to scan for the nearest node within the thickness of the plate and uses that node as the node for the plate.\n\nPlates can be meshed manually using the Mesh utilities provided in the Staad Pro interface and they can be output as well.\nIf the Staad Pro Mesh Generator is used, nodes must be manually created along the members supporting the plate. Using the Staad Pro interface manual mesh generator, the extra nodes along the member are created during the output.\n\n\n\nPanel Tolerance\nSettings\nStructural Analysis Interface"}
{"Headers": "Load Cases and Loads", "Content": "Load Cases must be defined for loads to be output. Loads with no load case information are not output.\n\n\n"}
{"Headers": "Catalogs", "Content": "Section profiles must be mapped correctly between AVEVA E3D Design and Staad Pro. Besides standard profiles, UPT and Prismatic profiles can also be used by setting the design parameters and mapping file accordingly. Refer to Structural Analysis Interface Administrator for further information.\n\n\n\nStructural Analysis Interface Administrator\nStructural Analysis Interface Administrator"}
{"Headers": "Materials", "Content": "Refer to Structural Analysis Interface Administrator for further information.\n\n\n\nStructural Analysis Interface Administrator\nStructural Analysis Interface Administrator"}
{"Headers": "Getting Started", "Content": "The SAI can be selected from the Interfaces tab.\nThe interface consists of five parts.\n\nDesigner Check - a set of checks designated for use by the Structural Designer to check for suitability of the model for output. Refer to Designer Check for further information;\nSettings - sets the output parameters. Refer to Settings for further information;\nAnalysis Information Input - a set of analysis information creation functions used to create loads for output and to assign Member Releases; Refer to Analysis Information for further information;\nModel Extraction - used to select the structure for output, including a set of Engineer Checks designated for use by the Structural Engineer to check for suitability of the model for output based on the Engineer's perspective. Refer to Engineer Check for further information;\nOther Features - provides additional tools to simplify additional tasks required for the structural analysis of the model. Refer to Other Features for further information.\nDesigner Check - a set of checks designated for use by the Structural Designer to check for suitability of the model for output. Refer to Designer Check for further information;\nDesigner Check - a set of checks designated for use by the Structural Designer to check for suitability of the model for output. Refer to Designer Check for further information;\nSettings - sets the output parameters. Refer to Settings for further information;\nSettings - sets the output parameters. Refer to Settings for further information;\nAnalysis Information Input - a set of analysis information creation functions used to create loads for output and to assign Member Releases; Refer to Analysis Information for further information;\nAnalysis Information Input - a set of analysis information creation functions used to create loads for output and to assign Member Releases; Refer to Analysis Information for further information;\nModel Extraction - used to select the structure for output, including a set of Engineer Checks designated for use by the Structural Engineer to check for suitability of the model for output based on the Engineer's perspective. Refer to Engineer Check for further information;\nModel Extraction - used to select the structure for output, including a set of Engineer Checks designated for use by the Structural Engineer to check for suitability of the model for output based on the Engineer's perspective. Refer to Engineer Check for further information;\nOther Features - provides additional tools to simplify additional tasks required for the structural analysis of the model. Refer to Other Features for further information.\nOther Features - provides additional tools to simplify additional tasks required for the structural analysis of the model. Refer to Other Features for further information.\n\n\n\nDesigner Check\nSettings\nAnalysis Information\nEngineer Check\nOther Features\nInterfaces\nDesigner Check\nDesigner Check\nSettings\nSettings\nAnalysis Information Input\nAnalysis Information\nModel Extraction\nEngineer Check\nOther Features\nOther Features"}
{"Headers": "Interface Introduction", "Content": "Details of the various parts of the interface can be found in this user guide, this is a quick review of what is necessary to output a model.\n\n\n"}
{"Headers": "Settings", "Content": "The Settings part of the Structural Analysis Interface window consists of three sections:\n\nHeader Section\nInformation from this section is output as the header information in the STD file. Currently only SI units and SPACE structure is supported.\nTolerances Section\nThe Tolerances section consists of tolerance information. These tolerances are used for node merging to avoid very short members in the exported STD file. Very short members can cause problems with Staad Pro calculations.\nOutput Settings Section\nThe Output Load check box determines whether to output the loads or not.\nThe Output Offset check box determines whether to output the offset or not. Refer to Justification for further information.\nClick Output Load Case Setting to display the Output Load Case Setting window, the load cases for output can be determined.\n\n\n\n\nJustification\nSettings\nStructural Analysis Interface\nHeader Section\nTolerances Section\nOutput Settings Section\nOutput Load\nOutput Offset\nJustification\nOutput Load Case Setting\nOutput Load Case Setting"}
{"Headers": "Designer Check", "Content": "First check for the model to make sure it is ready for outputting.\nNavigate to the Designer Check part of the Structural Analysis Interface window, select the EQUIP_SUPPORT hierarchy and select CE. Click Check All. The checking results display. Then fix the problems reported.\n\nIn the SAMPLE project, there are some GENSEC not properly connected and joints that are positioned within close proximity.\nThe reported errors can be safely ignored for this model.\n\n\n\nDesigner Check\nStructural Analysis Interface\nEQUIP_SUPPORT\nCE\nCheck All"}
{"Headers": "Analysis Information", "Content": "The Analysis Information Input part of the Structural Analysis Interface window allows the Engineer to set the supported analysis information in the model. The analysis information is stored in the model and the same analysis information is used in every analysis of the model.\n\n\n\n\n\nAnalysis Information Input\nStructural Analysis Interface"}
{"Headers": "Model Extraction", "Content": "The Model Extraction part of the Structural Analysis Interface window allows the Engineer to select the structure for output to the Staad Pro STD file.\n\n\n\n\nModel Extraction\nStructural Analysis Interface"}
{"Headers": "Engineer Check", "Content": "Step 4\nClick Check All in Output List. The result should be all checks have passed.\nClick Set Section Types to scan the hierarchy and set the GENSEC Purpose attribute to the correct section type.\n\nSet Section Types sets the Purpose attribute of vertical GENSECs to COLU, horizontal GENSECs to BEAM, and oblique GENSECs to BRAC. GENSECs with an angle in the horizontal direction with a value less than the input box are also set to BEAM.\n\nThe interface reads the Purpose attribute of the Hierarchy list to assess the GENSEC type.\n\n\n\nStep 4\nCheck All in Output List\nSet Section Types\nSet Section Types\nHierarchy"}
{"Headers": "Other Features", "Content": "The features are:\nStructural Simplification\nReplaces a structure with a single member to simplify analysis and can be used for roof structures, as an example.\nPanel Meshing\nA meshing tool for interactive meshing of plates. Such meshes enable nodes along GENSEC members to be created and connected to the GENSEC.\nImport Model\nImports an existing Staad Pro model into AVEVA E3D Design.\nRead STD file - makes use of the intermediate file created when extracting the model and the STD file that is modified in Staad Pro. With these files, the GENSEC profiles that are changed can be updated.\n\n\n\n\nStructural Simplification\nPanel Meshing\nImport Model\nStructural Simplification\nPanel Meshing\nImport Model"}
{"Headers": "Output a Model", "Content": "The section provides a simple tutorial on outputting a simple model.\n\n\n"}
{"Headers": "Output Settings", "Content": "Step 1\nFill the information in the Settings part of the Structural Analysis Interface window.\n\n\n\n\nStep 1\nSettings\nStructural Analysis Interface"}
{"Headers": "Designer Checking", "Content": "Step 2\nNavigate to the Designer Check part of the Structural Analysis Interface window, select the PIPERACK hierarchy and click CE. Click Check All, the result should be all checks have passed.\n\n\n\n\nStep 2\nDesigner Check\nStructural Analysis Interface\nPIPERACK\nCE\nCheck All"}
{"Headers": "Model Warning and Error", "Content": "\nIn the SAMPLE project, there are some GENSEC not properly connected and joints that are positioned within close proximity.\nThe reported errors can be safely ignored for this model.\n\n\n"}
{"Headers": "Output Content", "Content": "Step 3\nNavigate to the Model Extraction part of the Structural Analysis Interface window, select the PIPERACK hierarchy and click Add CE.\n\n\n\n\nStep 3\nModel Extraction\nStructural Analysis Interface\nPIPERACK\nAdd CE"}
{"Headers": "Output", "Content": "Step 5\nSelect Output to output the structure, the Staad Pro STD file is created.\n\n\n\n\nStep 5\nOutput"}
{"Headers": "Prefix Setting", "Content": "Prefix is used to define the prefix of the output STD file. The name of the file is the prefix+outfrome3d.std.\nClick to check what prefixes have already been used.\n\nAll output is sent to the %AVEVA_DESIGN_USER%\\SAIFiles\\ directory (or %SAISP% or %abcSAISP% directories if set up by the administrator, refer to Set the Mapping File for further information).\nThe standard location for the %AVEVA_DESIGN_USER%\\SAIFiles\\ directory is C:\\Users\\Public\\Documents\\AVEVA\\USERDATA\\SAIFiles\\\n\n\n\nSet the Mapping File\nPrefix\nSet the Mapping File"}
{"Headers": "Query", "Content": "The Query panel in the Other Features part of the Structural Analysis Interface window checks the GENSEC and node numbers that are generated by the output.\n\nThe Section Numbers window checks the number of GENSECs and their start/end node numbers. Click Select Current Section to navigate to a Section in the list.\n\nThe display information in the Section Numbers window comes from the STD file with the prefix input in the Prefix panel.\n\n\n\nQuery\nOther Features\nStructural Analysis Interface\nSection Numbers\nSelect Current Section\nSection\nSection Numbers\nPrefix"}
{"Headers": "Files", "Content": "The output file can be read into Staad Pro. Click Open STD File to view the STD file.\n\n\n\n\nOpen STD File"}
{"Headers": "Model Preparation", "Content": "Setup the UDA for SAI before using the project. Refer to Structural Analysis Interface Administrator for further information.\n\n\n\nStructural Analysis Interface Administrator\nStructural Analysis Interface Administrator"}
{"Headers": "Sections - Zero Length", "Content": "A zero length section has its joint start and end at identical positions or the length of the GENSEC is zero. These errors need to be corrected by deleting the zero length section or updating the joint start and/or end reference.\nIf GENSECS of this type are found, the interface displays a Confirm window. Click Yes, to delete all the zero length GENSECs found.\n\nClick No, all the zero length GENSECs are listed in the Checking Model window, and Delete Zero Length GENSEC is active. Click Delete Zero Length GENSEC to delete all the zero length GENSECs in the list, or click the lines in the list to navigate to the GENSEC and delete it manually.\n\n\n\n\nYes\nChecking Model\nDelete Zero Length GENSEC\nDelete Zero Length GENSEC"}
{"Headers": "Section/Joints - Duplicated Numbers", "Content": "When the model is output, the node or member numbers are stored with the model. In doing a second output, the interface maintains the numbers for the nodes.\nA check is performed for GENSEC/JLDATU/ENDATU duplicate number attributes. The numbers can be set to 0 so that the system can renumber the nodes or members while outputting.\nThe Set Duplicated Number to 0 in the Checking Models window is active. Click Set Duplicated Number to 0 to set the numbers of the GENSEC/JLDATU/ENDATU elements back to 0.\n\n\n\n\nSet Duplicated Number to 0\nChecking Models\nSet Duplicated Number to 0"}
{"Headers": "Sections - Offset to Joints", "Content": "Checks the GENSEC where the distance of the JLDATU references and the position of the GENSEC vary more than the distance input.\nThe offset can be caused by manual adjustment of the joint, causing incorrect beam positions when output.\nTo realign the joint, disconnect and reconnect the end of the beam. Refer to Connect Sections and Disconnect Sections for further information.\n\n\n\nConnect Sections\nDisconnect Sections\nConnect Sections\nDisconnect Sections"}
{"Headers": "Sections - Spref Unset", "Content": "SPREF not set for the GENSEC element. The SPREF must be set.\n\n\n"}
{"Headers": "Sections - Ends Unconnected", "Content": "Checks the GENSEC has no JOIS or JOIE references. The GENSEC must be connected.\nIn some cases, errors of this type can be ignored. For example, if one side of a beam has a free end, this error can be ignored.\n\n\n\n"}
{"Headers": "Joints - Disconnected", "Content": "Any issues can possibly be fixed by realigning the joint. Refer to Sections - Offset to Joints for further information.\n\nIf the joint is no longer required it can be selected and deleted. Refer to Delete for further information.\n\n\n\nSections - Offset to Joints\nDelete\nSections - Offset to Joints\nDelete"}
{"Headers": "Joints - Beyond Section Boundary", "Content": "Checks for JLDATU that lie outside the length of the owning GENSEC. The JLDATU must be corrected.\n\n\n\n"}
{"Headers": "Joints - Close Proximity", "Content": "Checks for JLDATU which are within the value specified. In the Settings, the JLDATU can be merged as a single node to output to the STD file.\n\n\n"}
{"Headers": "Engineer Check", "Content": "The Engineer Check function consists of various checks and options to correct errors. The checks can be made all at once with Check All or by or using the individual checks.\n\nThe various checks performed are:\nSections/Joints - Duplicate Numbers\nWhen the model is output, the node or member numbers are stored with the model. In doing a second output, the interface maintains the numbers for the nodes. The check makes sure that there are no duplicate numbers.\nThe function is the same as the Designer Check.\nAnalysis Data - Incorrect Definition\nThe function checks and reports the loads and release information errors for:\nLoads with no load case.\nLoads with no values set.\nRelease for GENSEC which is not found.\nSections - Spref Mapping\nChecks that all GENSEC spref are defined in the mapping file.\nSections/Joints - Duplicate Numbers\nWhen the model is output, the node or member numbers are stored with the model. In doing a second output, the interface maintains the numbers for the nodes. The check makes sure that there are no duplicate numbers.\nThe function is the same as the Designer Check.\nAnalysis Data - Incorrect Definition\nThe function checks and reports the loads and release information errors for:\nSections - Spref Mapping\nChecks that all GENSEC spref are defined in the mapping file.\n\nSections/Joints - Duplicate Numbers\nWhen the model is output, the node or member numbers are stored with the model. In doing a second output, the interface maintains the numbers for the nodes. The check makes sure that there are no duplicate numbers.\nThe function is the same as the Designer Check.\nAnalysis Data - Incorrect Definition\nThe function checks and reports the loads and release information errors for:\nLoads with no load case.\nLoads with no values set.\nRelease for GENSEC which is not found.\nSections - Spref Mapping\nChecks that all GENSEC spref are defined in the mapping file.\nLoads with no load case.\nLoads with no values set.\nRelease for GENSEC which is not found.\nLoads with no load case.\nLoads with no load case.\nLoads with no values set.\nLoads with no values set.\nRelease for GENSEC which is not found.\nRelease for GENSEC which is not found.\n\n\n\nCheck All"}
{"Headers": "Loads and End Conditions", "Content": "Load and member end properties can be created and stored in the AVEVA E3D Design database. These are used as analysis information and include:\nMember and Nodal loads\nMember release\nSupports\nMember and Nodal loads\nMember and Nodal loads\nMember release\nMember release\nSupports\nSupports\n\n\n"}
{"Headers": "Loads and Releases", "Content": "The Analysis Information Input part of the Structural Analysis Interface window is used for creating Loads and Releases for members.\n\nAll created loads must be associated with Load Cases. Loads without load cases are not output.\n\n\n\nAnalysis Information Input\nStructural Analysis Interface"}
{"Headers": "Load Cases", "Content": "To Create/Modify the load case set up, select Load Case to display the Load Case window. Load Cases are stored in a STRU element.\n\n\n\n\nLoad Case\nLoad Case"}
{"Headers": "Load Case STRU", "Content": "To create or set the load case storage hierarchy, select Load Case STRU to display the Load Case STRU window. Load Cases are stored in a STRU element.\n\nClick Create to create a new STRU in the current hierarchy and Apply to set the storage area for the selected STRU.\n\n\n\nLoad Case STRU\nLoad Case STRU\nCreate\nApply"}
{"Headers": "Create Load Case", "Content": "The Load Case window indicates the Load Case STRU selected. Input the Load Case information and the Load Case is created.\n\nSelect a Load Case Type from the drop-down list. For example, Dead, Wind or Live. Load Case Description is optional.\nThe Load Case Name must be unique in the project.\n\n\n\nLoad Case\nLoad Case Type\nLoad Case Description\nLoad Case Name"}
{"Headers": "Modify Load Case", "Content": "Select Modify from the drop-down list to modify the load case. The Load Case List window displays. Select the Load Case to be modified and select Apply.\n\nUpdate the Load Case information and select Modify when done.\n\n\n\n\nModify\nLoad Case List\nApply\nModify"}
{"Headers": "Delete Load Case", "Content": "Select Delete from the drop-down list, select a Load Case to be deleted in the Load Case List window prompted and select Apply. Then select Delete in the Load Case window to delete the load case.\n\n\n\nDelete\nLoad Case List\nApply\nDelete\nLoad Case"}
{"Headers": "Member Loads", "Content": "Member loads can be created and modified using Concentrated Load, Distributed Load or Modify Member Loads.\n\n\n\n\n"}
{"Headers": "Concentrated Load", "Content": "To create a Concentrated Load, click Concentrated Load to display the Create Concentrated Load window.\n\nSelect the Load Case and the GENSEC using the options provided and the Select By drop-down list.\n\nInput the various values. d1 is the distance from the connected JLDATU to the Load point. Force and Moments are based on the global co-ordinate system. Use Preview to check the position of the created Load.\n\n\n\n\nConcentrated Load\nCreate Concentrated Load\nSelect By\nd1\nPreview"}
{"Headers": "Distributed Load", "Content": "To create either Uniform or Trapezoidal loads, click Distributed Load to display the Create Distributed Load window.\n\nThe listed steps can be used to create the loads.\nSelect the load case;\nSelect the GENSEC;\nSet the distance where the load acts. If the Whole GENSEC check box is selected, the load is added on the whole GENSEC and d1 and d2 do not need to be input.\nSelect the Load Type. Trapezoidal Load requires the input of W1 and W2.\nSelect Apply to create the load, Preview to view the load.\nSelect the load case;\nSelect the load case;\nSelect the GENSEC;\nSelect the GENSEC;\nSet the distance where the load acts. If the Whole GENSEC check box is selected, the load is added on the whole GENSEC and d1 and d2 do not need to be input.\nSet the distance where the load acts. If the Whole GENSEC check box is selected, the load is added on the whole GENSEC and d1 and d2 do not need to be input.\nSelect the Load Type. Trapezoidal Load requires the input of W1 and W2.\nSelect the Load Type. Trapezoidal Load requires the input of W1 and W2.\nSelect Apply to create the load, Preview to view the load.\nSelect Apply to create the load, Preview to view the load.\nNote:\nUniform Load, Uniform Moment and Trapezoidal Load can be input.\n\n\n\nDistributed Load\nCreate Distributed Load\nWhole GENSEC\nd1\nd2\nApply\nPreview\nNote:"}
{"Headers": "Modify Member Loads", "Content": "Select Modify to modify the member loads.\n\nTo use this window, select the loads and then click Modify, Copy or Delete to edit the load.\nThe Load list is populated by selecting a Filter method.\n\nThe filter methods are:\nPick\nAllows the GENSEC to be picked from the 3D view, the loads are displayed in the Loads list.\nCollection\nDisplays all the defined collections, the required collection can be selected which loads all of the loads from the GENSEC elements in the list.\nCE\nCollects all of the loads from the current element into the Load list.\nLoad Case from CE\nDisplays the Load Cases in the system, required load cases can be selected and all the loads from the current element are loaded into the Load list.\nSelect to Modify, Copy or Delete the Loads.\n\n\n\nModify\nModify\nCopy\nDelete\nPick\nCollection\nCE\nLoad Case from CE\nModify\nCopy\nDelete"}
{"Headers": "Nodal Loads and Displacements", "Content": "Nodal Loads and displacements are created on JLDATUs or ENDATUs. Nodal Loads and displacements can be created and modified using Nodal Load, Nodal Displacement or Modify Nodal Loads.\n\n\n\n"}
{"Headers": "Nodal Load", "Content": "Click Nodal Load to display the Create Nodal Load window.\n\nInput the Force and Moments based on global co-ordinates and select the Load Case. Click Apply and pick the JLDATUs. Press ESC to end the consecutive picking and create nodal loads.\n\n\n\nNodal Load\nCreate Nodal Load\nApply\nESC"}
{"Headers": "Nodal Displacement", "Content": "Click Nodal Displacement to display the Nodal Displacement window.\n\nInput the displacement and rotation based on global co-ordinates and select the Load Case. Click Apply and pick the JLDATUs. Press ESC to end the consecutive picking and create nodal displacements.\n\n\n\nNodal Displacement\nNodal Displacement\nApply\nESC"}
{"Headers": "Modify Nodal Loads and Displacement", "Content": "Select Modify to modify the Nodal Loads and Displacements List.\n\nTo use this window, select the nodes and then click Modify, Copy or Delete to edit the load.\nThe Load list is populated by selecting a Filter method.\n\nThe filter methods are:\nPick\nAllows the GENSEC to be picked from the 3D view, the nodal loads and displacements are displayed in the Loads list.\nCollection\nDisplays all the defined collections, the required collection can be selected which loads all the nodal loads and displacements from the GENSEC elements.\nCE\nCollects all the nodal loads and displacements from the current element into the Load list.\nLoad Case from CE\nDisplays the Load Cases in the system, required load cases can be selected and all the nodal loads and displacements from the current element are loaded into the Load list.\nSelect to Modify, Copy or Delete the Loads.\n\n\n\nModify\nModify\nCopy\nDelete\nPick\nCollection\nCE\nLoad Case from CE\nModify\nCopy\nDelete"}
{"Headers": "Member Release", "Content": "Member release information can be created using the Nodal Release window.\n\nThe Release can be set as a Partial or Full Release. Select the GENSEC element from the Select By drop-down list. The release information displays if set for the GENSEC. The parameters and save information can be modified. If not already set, click Apply to create the information.\n\n\n\nNodal Release\nSelect By\nApply"}
{"Headers": "Support Information", "Content": "ENDATUs that are connected to columns can be set as Fixed or Pinned.\n\nFour options are available:\nChange ALL ENDATUs to FIXED: changes all ENDATUs in the current Hierarchy to FIXED.\nChange ALL ENDATUs to PINNED: changes all ENDATUs in the current Hierarchy to PINNED.\nChange Selected ENDATUs to FIXED: picked ENDATUs are set to FIXED.\nChange Selected ENDATUs to PINNED: picked ENDATUs are set to PINNED.\nChange ALL ENDATUs to FIXED: changes all ENDATUs in the current Hierarchy to FIXED.\nChange ALL ENDATUs to FIXED: changes all ENDATUs in the current Hierarchy to FIXED.\nChange ALL ENDATUs to PINNED: changes all ENDATUs in the current Hierarchy to PINNED.\nChange ALL ENDATUs to PINNED: changes all ENDATUs in the current Hierarchy to PINNED.\nChange Selected ENDATUs to FIXED: picked ENDATUs are set to FIXED.\nChange Selected ENDATUs to FIXED: picked ENDATUs are set to FIXED.\nChange Selected ENDATUs to PINNED: picked ENDATUs are set to PINNED.\nChange Selected ENDATUs to PINNED: picked ENDATUs are set to PINNED.\n\n\n\nChange ALL ENDATUs to FIXED\nChange ALL ENDATUs to PINNED\nChange Selected ENDATUs to FIXED\nChange Selected ENDATUs to PINNED"}
{"Headers": "Display", "Content": "The Display part of the Structural Analysis Interface window produces a graphical display of the members and node information.\n\n\n\n\nDisplay\nStructural Analysis Interface"}
{"Headers": "Structural Simplification", "Content": "Structural simplification is used by the Engineer to substitute a complex structure with an equivalent GENSEC of similar rigidity and strength. The example displays a structure that is replaced with a beam.\n\nClick Structural Simplification, to display the Structural Simplification window which is used for the simplification.\n\nThe required steps are:\nThe interface checks if there are replacement GENSECs when adding elements to the output list. If replacement GENSECS are found, the original or the replacement GENSEC can be output.\nSelect the Storage Area to store the replacement GENSECs.\nSelect the Structure which is to be replaced.\nModel the replacement GENSEC.\nSelect the Storage Area to store the replacement GENSECs.\nSelect the Storage Area to store the replacement GENSECs.\nSelect the Structure which is to be replaced.\nSelect the Structure which is to be replaced.\nModel the replacement GENSEC.\nModel the replacement GENSEC.\n\n\n\nStructural Simplification\nStructural Simplification"}
{"Headers": "Worked Example", "Content": "This chapter can be used as a guide to output structures using the APS project.\n\nThe structures are located at:\n\n\n\n"}
{"Headers": "GENSEC Connection", "Content": "The replacement GENSEC does not connect automatically. Connections can be made for the replacement GENSEC and the columns. Refer to Connect Sections for further information.\n\n\n\n\nConnect Sections\nConnect Sections"}
{"Headers": "Output", "Content": "Navigate to the Model Extraction part of the Structural Analysis Interface window and add the roof structure to the output list, a Question window displays.\n\nClick Yes, the hierarchy of the roof is added to the output list.\n\nClick No, the replacement GENSEC is added to the output list. The roof hierarchy can no longer be added to the output list.\n\n\n\n\nModel Extraction\nStructural Analysis Interface\nQuestion\nYes\nNo"}
{"Headers": "Panel Meshing", "Content": "There are two panels in this model. Plates need to be meshed into three or four node elements in Staad Pro. Use the Panel Meshing tools to mesh the panels for Staad Pro.\nSelect Panel Meshing to display the Panel Meshing window.\nSelect the PANE in SBFR EL(+)107820_TOS_PLATE in AVEVA E3D Design, use Pick Panel to select this PANE\n\nSelect Position picked from the Vertex Position drop-down list. Click the Derive points from graphic picks to pick the meshed points for this PANE.\nThe panels should be meshed according to the frames of the model. In this example, the panel should be meshed into four parts.\n\nWhen the panels are output, the interface scans for the nearest node within the thickness of the plate and uses that node as the node for the plate.\nIf there are beams under the panel, the nodes of the meshed panels should be created at the position of the JLDATUs of the connected beams. Then the nodes of the panel output can be merged to the nodes of the GENSECs. Otherwise the nodes of the panels maybe output as an orphan node.\nWhen selecting the points of the panels, always use the position of the JLDATUs If possible. In this example, four JLDATUs of the connecting beams are picked.\nHere use the type Element in the Positioning Control for picking GENSEC.\n\nPick the GENSEC near the JLDATU, the interface positions the JLDATUs and adds them to the point list.\n\nSimilarly, add the other three meshed panels to the list:\n\nIn the fourth panel, there is a penetration for a staircase. An enclosed panel is drawn for simplification.\n\nSimilarly, mesh the panel on the second floor into four panels.\n\nNote:\nSelect Projection to Panel from the Vertex Position drop-down list, the elevations of the vertexes are still on the panel, not the JLDATUs.\n\n\n\nPanel Meshing\nPanel Meshing\nPick Panel\nPosition picke\nVertex Position\nDerive points from graphic picks\nNote:"}
{"Headers": "Import Model", "Content": "If the model is updated in Staad Pro, the new model can be updated in AVEVA E3D Design, and the Merge function used to update the original model. Import the model using the Import Model from STD files window.\n\nNow there is a reference model, the model displays four new beams.\n\nSelect Merge in the window to display the Merge Imported Model window.\nBecause there are new beams in the imported model, create a new SBFR under the EQUIP_SUPPORT hierarchy, and set the Purpose attribute of the SBFR to BEAM to store the updated beams.\nClick CE to set the Origin Model and Update Model in the window, and click Compare Model, the compare result displays.\n\nIn the example, the panels in the origin model are on the top of the beams. The nodes of the panels are merged to the nodes of the beams where first output. The beams are output using the NA Pline, so the nodes of the imported panels are also on the elevation of the NA of the beams. The nodes of the panels are not the same as the origin model in AVEVA E3D Design. The panels are not updated here.\nSelect the 1st to 8th lines and click Update Selected to update those 8 GENSECs lines. Then, check that the new beams in the SBFR have been created, and the columns /ES.A/ES1, /ES.A/ES2, /ES.B/ES1 and /ES.B/ES2 are updated.\n\n\n\n\nImport Model from STD files\nMerge\nMerge Imported Model\nEQUIP_SUPPORT\nCE\nOrigin Model\nUpdate Model\nCompare Model\nUpdate Selected"}
{"Headers": "Assembly Planning", "Content": "This User Guide intends to give an impression of Assembly Planning in its current state with focus on the functionality to create assembly structures, and to populate assemblies with model parts. Assembly Planning provides functionality to manage the production breakdown structure of the design. It supports the definition of the build strategy and the creation of assembly production information.\nThe hierarchical assembly tree (the production breakdown structure) is defined and maintained in parallel with the design and modelling work. The rough build strategy is defined in the early phase of a project, and further refined into a detailed build strategy along with the refinement of the model. As soon as model parts are available in Design, they can be collected to nodes in the assembly tree. Thus, the Assembly view of the product is available from the very beginning of the design, and is continuously developed during the design process. Assembly Planning allows the detailed design model to be viewed as a production model.\nWith Assembly Planning the complete production breakdown structure is created and maintained. This includes the production hierarchy for the hull, but also the installation of Equipment, Electrical, HVAC and Outfit steel. An assembly could be a physical steel unit (including outfit installation), but an assembly could also correspond to a space (for example a compartment or a room) and thereby include all the prefabricated units, material and components to be installed into this space.\nIts main features are as follows:\nTools for creation and manipulation of the Assembly Tree.\nTools for the collection of objects / parts to assemblies.\nTools for creation and manipulation of the Assembly Tree.\nTools for creation and manipulation of the Assembly Tree.\nTools for the collection of objects / parts to assemblies.\nTools for the collection of objects / parts to assemblies.\n\n\n\n\n\n\nAssembly"}
{"Headers": "Data Model", "Content": "The data model for assemblies as depicted below is built by a set of ASMBLY type of elements. The assemblies (ASMBLY) are referring design elements through proxy elements (ASITEM) which are not visible to the user. The top most element of an assembly structure is the Assembly World (ASWL) type of element.\n\n\n\n"}
{"Headers": "Attributes on ASMBLY", "Content": "NAME\nAssembly path text.\nText\nASNAME\nLocal assembly node name.\nText\nDESC\nDescription.\nText\nASWLOC\nWorking location.\nText\nASDEST\nDestination.\nText\nASBUIL\nBuilding strategy.\nText\nASORI\nPredefined Assembly Orientation (*).\nInteger\nORI\nOrientation derived from ASORI.\nReal array\nASEWEI\nEstimated weight.\nReal\nName\nDescription\nType\nASECOG\nEstimated centre of gravity.\nReal array\nPOS\nPosition.\nReal array\nNote:\n\n\n(*) Predefined assembly orientations\n\n1 = -Z / Down\n4 = -X / West\n7 = (Not in use)\n2 = Z / Up\n5 = Y / North\n8 = (Not in use)\n3 = X / East\n6 = -Y / South\n9 = manual\n\nName\nDescription\nType\nNAME\nAssembly path text.\nText\nASNAME\nLocal assembly node name.\nText\nDESC\nDescription.\nText\nASWLOC\nWorking location.\nText\nASDEST\nDestination.\nText\nASBUIL\nBuilding strategy.\nText\nASORI\nPredefined Assembly Orientation (*).\nInteger\nORI\nOrientation derived from ASORI.\nReal array\nASEWEI\nEstimated weight.\nReal\nName\nDescription\nType\nASECOG\nEstimated centre of gravity.\nReal array\nPOS\nPosition.\nReal array\nNote:\n(*) Predefined assembly orientations\n1 = -Z / Down\n4 = -X / West\n7 = (Not in use)\n2 = Z / Up\n5 = Y / North\n8 = (Not in use)\n3 = X / East\n6 = -Y / South\n9 = manual\n\n\n\nNAME\nASNAME\nDESC\nASWLOC\nASDEST\nASBUIL\nASORI\nORI\nASEWEI\nName\nASECOG\nPOS\nNote\n:"}
{"Headers": "Attributes on ASITEM", "Content": "ASIQUA\nQuantity valid only for GPART type of elements assigned to assembly.\nInteger\nASMREF\nReference to design part.\nReference table\n\nName\nDescription\nType\nASIQUA\nQuantity valid only for GPART type of elements assigned to assembly.\nInteger\nASMREF\nReference to design part.\nReference table\n\n\n\nASIQUA\nASMREF"}
{"Headers": "Pseudo Attributes on ASMBLY", "Content": "SMEMB\nMembers of assembly (subassemblies and referred parts).\nSEXPND\nReferred design parts in entire structure below assembly.\nASORIS\nLike ASORI but expressed in the format of a text string. The format is configured by the general command: coord XYZ / ENU.\nASSEQ\nSequence number.\nASVDIR\nView direction vector looking at assembly plane. I.e. ASORI expressed as a vector.\n\nName\nDescription\nSMEMB\nMembers of assembly (subassemblies and referred parts).\nSEXPND\nReferred design parts in entire structure below assembly.\nASORIS\nLike ASORI but expressed in the format of a text string. The format is configured by the general command: coord XYZ / ENU.\nASSEQ\nSequence number.\nASVDIR\nView direction vector looking at assembly plane. I.e. ASORI expressed as a vector.\n\n\n\nSMEMB\nSEXPND\nASORIS\nASSEQ\nASVDIR"}
{"Headers": "Pseudo Attributes on ASITEM", "Content": "SITEM\nReferred part.\n\nName\nDescription\nSITEM\nReferred part.\n\n\n\nSITEM"}
{"Headers": "Pseudo Attributes on any Type of Element (Collected to an Assembly)", "Content": "ASIOWN\nOwning ASITEM.\nASMOWN\nOwning ASMBLY.\nASMBLD\nTrue/False whether assembled.\nASMBLS\n\u2018A\u2019/\u2019NA\u2019 whether assembled.\nASSEQ\nSequence number.\nASMBLB\nTrue/False whether the type of element is possible to collect to an assembly.\n\nName\nDescription\nASIOWN\nOwning ASITEM.\nASMOWN\nOwning ASMBLY.\nASMBLD\nTrue/False whether assembled.\nASMBLS\n\u2018A\u2019/\u2019NA\u2019 whether assembled.\nASSEQ\nSequence number.\nASMBLB\nTrue/False whether the type of element is possible to collect to an assembly.\n\n\n\nASIOWN\nASMOWN\nASMBLD\nASMBLS\nASSEQ\nASMBLB"}
{"Headers": "Customization", "Content": "The context sensitive menu of Assembly Planning is easily extended with user defined functions. Also, Assembly Planning shares the benefit of extending data definition based on the concept of UDET, UDA and USDA. These topics are given a short introduction below.\n\n\n\nAssembly Planning\nAssembly Planning"}
{"Headers": "AssemblySelection Object", "Content": "The purpose of this object is to expose element selections made in the Assembly Planning GUI back to PML. The object is defined as a PMLNet object and thereby requires the following to be used in PML.\nThe object also provides an event mechanism to announce when the current selection has changed.\nASSEMBLYSELECTION\nASSEMBLYSELECTION\nDefault constructor.\nASSEMBLYSELECTION\n(STRING)\nConstructor to name the object (required for the event mechanism to operate properly).\nADDEVENTHANDLER\n(STRING eventName, ANY object, STRING methodName)\nAdds an event handler that will invoke at changed selections in Assembly Planning GUI.\nREMOVEEVENTHANDLER\n(STRING eventName, REAL handle)\nRemove an event handler.\nASSEMBLYSELECTION\n\nASSEMBLYSELECTION\nDefault constructor.\nASSEMBLYSELECTION\n(STRING)\nConstructor to name the object (required for the event mechanism to operate properly).\nADDEVENTHANDLER\n(STRING eventName, ANY object, STRING methodName)\nAdds an event handler that will invoke at changed selections in Assembly Planning GUI.\nREMOVEEVENTHANDLER\n(STRING eventName, REAL handle)\nRemove an event handler.\nExamples utilizing the ASSEMBLYSELECTION object are to be found in PMLLIB in assembly/forms and assembly/userfunctions subfolders.\nASSEMBLYSELECTION\nASSEMBLYSELECTION\nDefault constructor.\nASSEMBLYSELECTION\n(STRING)\nConstructor to name the object (required for the event mechanism to operate properly).\nADDEVENTHANDLER\n(STRING eventName, ANY object, STRING methodName)\nAdds an event handler that will invoke at changed selections in Assembly Planning GUI.\nREMOVEEVENTHANDLER\n(STRING eventName, REAL handle)\nRemove an event handler.\nimport 'Aveva.AssemblyPlanning.Utilities'\nusing namespace 'Aveva.AssemblyPlanning.Utilities'\n\n\n\nASSEMBLYSELECTION\nASSEMBLYSELECTION\nASSEMBLYSELECTION\n(STRING)\nADDEVENTHANDLER\n(STRING eventName, ANY object, STRING methodName)\nREMOVEEVENTHANDLER\n(STRING eventName, REAL handle)"}
{"Headers": "AssemblyPlanningAddin.uic", "Content": "It is possible to append user defined functions to the context menu of Assembly Planning by editing the AssemblyPlanningAddin.uic file (refer to the User Guide for .NET Customization for more information). At delivery, the PML function Create Hierarchy from Space Arrangement is added to the file.\n\n\n\nAssemblyPlanningAddin.uic\nCreate Hierarchy from Space Arrangement"}
{"Headers": "User Defined Element Types (UDET)", "Content": "You can put restrictions on what type of assemblies that can be owned by another type of assemblies utilizing sub-typing based on UDETs. These restrictions are considered when defining or changing the assembly structure. Example of restricted assembly structure based on types defined in Lexicon. Type assembly of type ASM1 allow assembly of type ASM2 as member while ASM3 is the only allowed member to ASM2. ASITEM is a required member to allow design parts being collected to assembly.\n\n\n\n\n\n"}
{"Headers": "User System Defined Attributes (USDA)", "Content": "By sub-typing assemblies based on UDETs and connecting them to customized variants of attributes through USDAs, is a way to put restrictions on attribute values for certain assembly types. This means that if any of these attributes have USDA definitions with a limited set of allowed values, only these values are presented in drop down menus when edited from the Properties function. As in the example below assemblies of type ASM1 allow only the following working locations (i.e. restriction on ASWLOC attribute), 'Cutting shop', 'Hall A', 'Dry dock B' and 'Painting shop'.\n\n\n\n\nProperties"}
{"Headers": "User Defined Attributes (UDA)", "Content": "The Properties function also supports editing of user defined attributes like the PREPARATION attribute below, with default value 'No preparation required' applied on assemblies of type ASM1.\n\nThe properties below show some user configuration utilizing USDA and UDA for an assembly.\n\n\n\n\nProperties"}
{"Headers": "Hull Design", "Content": "The Hull Design application handles the hull steel design primarily in ships and other floating structures. The hull steel model is highly topological and benefits from the models made for common references, that is surfaces, curves and points. Hull model properties can be inherited from information added to any functional arrangements, that is space, area and curve arrangements. Hull specific drawings are created with specialized functions in the Draw application, integrated as part of the E3D Design.\n\n\n\n\n\n"}
{"Headers": "Basic Concepts", "Content": "This section describes the basic concepts of hull design.\n\n\n"}
{"Headers": "Definition and Outcome", "Content": "All hull steel definitions are made in panels, a suitable type of data container defined by the user, that holds all definitions of physical components (for example brackets and stiffeners) as well as definitions to make the model ready for production (for example shrinkage). All definitions and their topological connections represent the definition data for this specific part of the design. The panel that is displayed in a canvas is the geometrical outcome of these definitions. A change of a hull component is made by changing the definition or by changing the underlying elements that are referenced by the definition data (for example an underlying surface). The new outcome of the panel, the geometrical representation, is then generated by a simple recreate operation. Although changes are made to definition data, the application functions allow a user to interact with the outcome model, updating the definition data behind the scene and automatically recreates for a new outcome.\nThe definition of hull components is preferably made in groups, that is hull components that share the same properties. The update made to one of the instances is then affecting all the instances within this group. If this is not wanted, for example when one of the stiffeners in a group shall be defined with a different profile type and dimension, then the specific instance needs to be broken out from the group using the Regroup function.\n\n\n\nRegroup"}
{"Headers": "The Panel Concept", "Content": "The panel represents a part of the hull steel design that is suitable from the user's perspective. Typically, the panel is representing large parts of the design early in the process (for example a full deck) and later when detailing evolves in much smaller parts suitable for detail and production work.\nPanels are generated in zones that normally represent the design or the production blocks. The zones are best generated by using Space Management, where a space arrangement can be created and used to create both database structure and the actual zones. The zones will in this case relate to the corresponding space and thus get a geometrical representation.\nBelow is an example of a block arrangement in zones.\n\nThe data structure of panels is built up in a hierarchy. The pictures below show this hierarchy with top element names in the database. Each definition element can then have additional definition data in elements below, a stiffener can for example have a hole definition element.\n\nOne definition can generate one or many instances in the outcome model, that is several stiffeners can be the outcome of one stiffener definition as show below.\n\nIf specific changes shall be made to one of the instances, then that instance needs to be broken out from the group using the Regroup function.\n\n\n\nSpace Management\nRegroup"}
{"Headers": "The Panel Content", "Content": "This section describe the panel content functionality.\n\n\n"}
{"Headers": "Location", "Content": "The location of a panel is defining its geometrical position and its shape. Location can be a plane (grid plane or coordinate and axis) or a surface (sculptured or a polyface surface). It is the location that defines the shape of the panel, for example if it should be planar, knuckled or sculptured. Normally a panel has one location, but the panel model also allows for individual location data on points, curves, plates, brackets and stiffeners.\nFrom a topological perspective, the location definition should use the model entities available in the common reference model, that is surfaces, curves, points. This to create a model where global changes are easy and fast to carry through.\n\n\n"}
{"Headers": "Boundary", "Content": "The definition of the boundary of the panel is built up by limiting information. Limiting information can be references to other model entities or points and lines. The instance of the boundary will hold information about each individual limit of the boundary. An ambiguity in the definition may result in more than one possible outcome of the instance. This is resolved by adding an additional point or a box to the definition.\n\n\n"}
{"Headers": "Box", "Content": "A box element can be added on panel level to be used to resolve ambiguity when creating the geometrical outcome of the panel.\n\n\n"}
{"Headers": "Curves and Points", "Content": "Curves and points are defined in the common reference model but can also be defined in a panel context and used as location for the definition of other elements, for example stiffeners and seams. A curve resulting from an intersection between, for example a panel and a surface, will become local in the panel if the panel is selected as the first intersecting element and vice versa if the surface is the first selected intersecting element, then the curve will become a common reference curve.\nThe definition data for points and curves is the same as for the corresponding common reference elements.\nThe definition of a more complex free side of a panel is preferably made using a local panel curve. A typical scenario is to create a curve in the intersection with the panel and a surface and then create an offset curve at a distance that can adjust to its correct shape using the function Extend on the Common Reference ribbon. Interaction is in many cases simplified by restricting the curves with a box. Currently there is no interactive function for this, instead the definition element of the curve needs to be manually updated with a DBOX element (containing minimum and maximum points) as shown below.\n\n\n\n\nExtend\nCommon Reference"}
{"Headers": "Plate", "Content": "The plate is in the normal case, when a panel with one location, defined simply by a point and elements for material and side definitions. The plate can however be given its own location and boundary and optionally be defined with own hull elements.\n\n\n"}
{"Headers": "Stiffener", "Content": "The stiffener trace is defined by model references, points or plane definitions together with elements defining material, profile parameters, inclination, side information and end characteristics. Optionally it also contains definitions for holes, cutouts and notches.\n\n\n"}
{"Headers": "Face Plate", "Content": "The face plate is defined with a model reference to a limit or a hole together with elements defining material, profile parameters, inclination and end characteristics. Optionally it also contains definitions for holes, cutouts and notches.\n\n\n"}
{"Headers": "Pillar", "Content": "The pillar is defined by a model reference (to a curve) and elements defining side information and material and profile data.\n\n\n"}
{"Headers": "Bracket", "Content": "The bracket is defined with a plate definition element and elements for the bracket arm definition including model reference.\n\n\n"}
{"Headers": "Cutout", "Content": "The cutout definition contains a model reference element defining the penetrating elements. The cutout type and the cutout parameters (if needed) are attributes on the definition element. If clips are defined, these are elements below the cutout element.\n\n\n"}
{"Headers": "Clip", "Content": "The clip element, defined together with the cutout, contains attributes to define type and parameters. A material definition element is defined below to define material properties and directions. A clip is defined with thickness equal to zero by default. This is interpreted as the same thickness as the plate in which the cutout is added.\n\n\n"}
{"Headers": "Hole", "Content": "The hole is defined with a reference to the built in hole standard and necessary parameters for the selected hole type unless not a curve is referenced for the hole shape. The hole position may be given by an attached point element.\n\n\n"}
{"Headers": "Notch", "Content": "The notch is defined with a reference to the built in notch standard and necessary parameters for the selected notch type. The notch position is defined by model reference elements.\n\n\n"}
{"Headers": "Topology Concept", "Content": "In cases when models have dependencies, these shall be saved as references to objects or part of objects. Such references constitute the topology of the model.\nEach design model object holds references to the objects that are part of its definition, for example the surfaces, curves or panels defining a plane panel boundary. Thus, each object can be regenerated using its references. This might create a new instance with for example an updated outer contour if the referred objects have changed its position or shape.\nThe model can also extract and present depending objects, for example a deck will know about all the webs that are attached to it.\nTo benefit from the topology, it is essential that it is well defined. This means for example that a bulkhead that ends at a deck should have a limit definition that is a model reference. Preferable this reference should be as generic as possible. A reference to the deck surface is a better reference (from a topological perspective) than referencing the deck panel and referencing the deck panel is a better reference than referencing a grid plan. In any case, absolute coordinates should be avoided. When the referencing is to the underlying surface or the deck panel, a recreated bulkhead would then pick up location and shape changes of the deck as well as thickness compensate for the plate thickness in the deck plates.\nCircular references should be avoided. If for example two deck panels are connected, they should not refer each other directly, but rather reference a polyface representing for example a block limit.\nMany references are on component level, for example a bracket referring a stiffener on the same panel or on another panel. If the boundary definition of a bulkhead refers a deck and then a stiffener on that deck refer a stiffener on the bulkhead this may seem like a circular reference as the bulkhead refers the deck and vice versa. It is not as the topology must be viewed on component level. Thus, the boundary of the bulkhead is dependent on the deck position and plating while the deck stiffener is dependent on the bulkhead stiffener. So, it is quite possible to sort out for example in which order to regenerate the components of the panels.\n\n\n"}
{"Headers": "Inherit Information from Functional Arrangements", "Content": "Panels can inherit information from the functional model (that is space, area and curve arrangements) while modelling. The following inherit scenarios are valid:\nPanels defined in zones connected to spaces will get the space limits as boundary.\nPanels generated for a scantling area arrangement will get plate thicknesses as defined in the area arrangement\nStiffeners defined using curve arrangements will inherit the profile properties.\nPanels defined in zones connected to spaces will get the space limits as boundary.\nPanels defined in zones connected to spaces will get the space limits as boundary.\nPanels generated for a scantling area arrangement will get plate thicknesses as defined in the area arrangement\nPanels generated for a scantling area arrangement will get plate thicknesses as defined in the area arrangement\nStiffeners defined using curve arrangements will inherit the profile properties.\nStiffeners defined using curve arrangements will inherit the profile properties.\n\n\n"}
{"Headers": "One-Click Concept", "Content": "The modelling of hull entities often require a lot of user data to be added to get to its final state. A stiffener needs trace information, side information, material and profile properties, etcetera. Any incorrect user data is not shown fully until the hull component is presented graphically. To get a more immediate graphical feedback, a one-click concept is used, meaning the graphical feedback shall be available with minimum amount of data. Refining into full detailing can then be done with graphical feedback in all stages, avoiding unnecessary user mistakes.\n\n\n"}
{"Headers": "Copy and Clone Concept", "Content": "The cloning and copying of panels are processes where the definition data is adjusted to a new position in the design and is then recreated to generate a new outcome. In the simple case, the original model references can be used, that is when copying a floor panel bounded by the shell and the tank top along the ship. If the copying requires different model references to get a correct shape, then the involved surfaces need to be connected. This is done by updating the element reference stored in attribute Origrf. The surface which we aim to use in the new position (copying to) shall have this attribute set to the surface used in the original panel position.\nThe clone concept is extending the copying of panels by registering and using the connection between the copied panels. Modifications to one of the clones is by default propagating to all other connected cloned panels. If individual changes shall be made, the user needs to activate single mode editing which breaks the connection for specified hull components in the modified panel. All cloned panels have a full definition and the single panel edited hull component will use its own definition without affecting any of the clones.\nDeleting a cloned panel or a hull component on a cloned panel will automatically rearrange the registered connections making all remaining connections between all cloned panels still valid.\nThe relation between the cloned panels and their individual hull components is illustrated by the picture below.\n\nYou can at any time query if a panel has any clones. This is done by querying attribute Hascln on the panel element UPANEL.\n\n\n\nOrigrf\nHascln"}
{"Headers": "The Application Layout and Common Interaction", "Content": "The application is built up by windows in a canvas, ribbons with icon groups to access functions and modal functions docked inside panels.\n\n\n"}
{"Headers": "Ribbons", "Content": "The application contains ribbons with groups of functions organized in different tabs.\nThe main tabs when working with hull models are as follows:\nThe Hull Design tab\ncontains all functions to generate and modify hull panels.\nThe Arrangement tab\ncontains all functions to generate and modify space, area and curve arrangements.\nThe Common Reference tab\ncontains all functions to generate and modify common reference elements, that is surfaces, curves and points. Furthermore, it contains functions to simplify the grid definition for ships.\nThe Admin tab\nis used when managing data and contains general functions to support database management. It also contains functions that allows space arrangements to be used when setting up the database structure for a project and when creating zones that are geographically bounded.\nThe Hull Design tab\ncontains all functions to generate and modify hull panels.\nThe Arrangement tab\ncontains all functions to generate and modify space, area and curve arrangements.\nThe Common Reference tab\ncontains all functions to generate and modify common reference elements, that is surfaces, curves and points. Furthermore, it contains functions to simplify the grid definition for ships.\nThe Admin tab\nis used when managing data and contains general functions to support database management. It also contains functions that allows space arrangements to be used when setting up the database structure for a project and when creating zones that are geographically bounded.\n\nThe Hull Design tab\ncontains all functions to generate and modify hull panels.\nThe Arrangement tab\ncontains all functions to generate and modify space, area and curve arrangements.\nThe Common Reference tab\ncontains all functions to generate and modify common reference elements, that is surfaces, curves and points. Furthermore, it contains functions to simplify the grid definition for ships.\nThe Admin tab\nis used when managing data and contains general functions to support database management. It also contains functions that allows space arrangements to be used when setting up the database structure for a project and when creating zones that are geographically bounded.\n\n\n\nHull Design\nArrangement\nCommon Reference\nAdmin"}
{"Headers": "Property Grids", "Content": "Properties on all model elements are defined in attributes and can be viewed in the Attribute panel and changed using commands in the Command window. The complete set of attributes are presented in the Attribute panel. However, they are not presented in a very user-friendly way. Furthermore, changing properties using commands may be cumbersome and can lead to incorrect model elements in case wrong values are given. In the normal user case, the Property Grid panel should be used to modify and view properties. The Property Grid presents relevant property information in a format that is suitable to view and possibly change. Information is presented with enumerations in drop-down lists and validation checks are done on inserted data.\n\nThe changes that are made is updating the definition data of the selected component and a recreate operation is triggered to get the canvas updated using the new supplied properties. The change will propagate on all instances resulting of the updated definition. If only a specific instance shall be updated the function Regroup needs to be used in beforehand, extracting the specified instances into a new definition element.\n\n\n\nAttribute\nCommand\nAttribute\nProperty Grid\nProperty Grid\nRegroup"}
{"Headers": "Grips and Functions", "Content": "The interaction in the canvas with the model entities is by default on component level, for example picking will select a hull panel component rather than the full panel. This can be changed by using the Navigation option presented in the Power Wheel at a right-click.\n\n\n\n\nNavigation\nPower Wheel"}
{"Headers": "Grips", "Content": "Double-click a hull component (or a panel if navigated to), modelling grips are presented, to translate and eventually rotate or manipulate individual points if applicable.\n\nSelection of non-physical components like holes or seams are made possible by functions that presents model grips in canvas. These functions are found in the Visibility group on the Hull Design tab.\n\nGroups of components are not possible to move by modelling grips, instead the Property Grid should be used.\n\n\n\nVisibility\nHull Design\nProperty Grid"}
{"Headers": "The Step-in Concept", "Content": "The hull model is preferably defined by using common references to make the model easy to change and maintain. When the underlying model is needed, the system supplies a possibility to easily get this model into canvas and allowing for changes. This possibility is called the step-in concept.\nThe following possibilities are available, with more to be added in future releases of E3D Design:\nTask\nHow to step-in\nUpdate the location surface of a panel.\nSelect a panel and navigate to the panel (using the power wheel). The location surface is displayed in the canvas by a step-in operation, either by a double-click on the panel or using the in-canvas command In. Once the location surface is displayed, it can be changed with normal surface tools. Once ready use the Escape button on the keyboard. The surface will be removed from the canvas and the panel is recreated picking up the changes in the location surface.\nUpdate the location of a panel.\nDouble click on a panel to enter the Edit mode and then navigate (using the power wheel) to the panel. A modelling grip is displayed in the centre of the panel and when selected, you are asked to select a new location or to use the Arrow down on the keyboard for options:\nThe panel is updated when the selection of location is done.\nUpdate the location of a panel.\nDouble click on a limit handle to enter the Edit mode and then double click once more to go to Curve Editing mode. Grips are displayed and the curve geometry can be changed using them as well as other tools. Once ready use the Escape button on the keyboard. The limit and panel boundary is recreated picking up the changes in the curve.\nUpdate the trace curve of a stiffener.\nDouble click on a stiffener to enter the Edit mode and then double click once more to go to curve editing mode. Grips are displayed and the curve geometry can be changed using them as well as other tools. Once ready use the Escape button on the keyboard. The stiffener is recreated picking up the changes in the curve.\nTask\nHow to step-in\nUpdate the location surface of a panel.\nSelect a panel and navigate to the panel (using the power wheel). The location surface is displayed in the canvas by a step-in operation, either by a double-click on the panel or using the in-canvas command In. Once the location surface is displayed, it can be changed with normal surface tools. Once ready use the Escape button on the keyboard. The surface will be removed from the canvas and the panel is recreated picking up the changes in the location surface.\nUpdate the location of a panel.\nDouble click on a panel to enter the Edit mode and then navigate (using the power wheel) to the panel. A modelling grip is displayed in the centre of the panel and when selected, you are asked to select a new location or to use the Arrow down on the keyboard for options:\n\nThe panel is updated when the selection of location is done.\nUpdate the location of a panel.\nDouble click on a limit handle to enter the Edit mode and then double click once more to go to Curve Editing mode. Grips are displayed and the curve geometry can be changed using them as well as other tools. Once ready use the Escape button on the keyboard. The limit and panel boundary is recreated picking up the changes in the curve.\nUpdate the trace curve of a stiffener.\nDouble click on a stiffener to enter the Edit mode and then double click once more to go to curve editing mode. Grips are displayed and the curve geometry can be changed using them as well as other tools. Once ready use the Escape button on the keyboard. The stiffener is recreated picking up the changes in the curve.\n\nTask\nHow to step-in\nUpdate the location surface of a panel.\nSelect a panel and navigate to the panel (using the power wheel). The location surface is displayed in the canvas by a step-in operation, either by a double-click on the panel or using the in-canvas command In. Once the location surface is displayed, it can be changed with normal surface tools. Once ready use the Escape button on the keyboard. The surface will be removed from the canvas and the panel is recreated picking up the changes in the location surface.\nUpdate the location of a panel.\nDouble click on a panel to enter the Edit mode and then navigate (using the power wheel) to the panel. A modelling grip is displayed in the centre of the panel and when selected, you are asked to select a new location or to use the Arrow down on the keyboard for options:\nThe panel is updated when the selection of location is done.\nUpdate the location of a panel.\nDouble click on a limit handle to enter the Edit mode and then double click once more to go to Curve Editing mode. Grips are displayed and the curve geometry can be changed using them as well as other tools. Once ready use the Escape button on the keyboard. The limit and panel boundary is recreated picking up the changes in the curve.\nUpdate the trace curve of a stiffener.\nDouble click on a stiffener to enter the Edit mode and then double click once more to go to curve editing mode. Grips are displayed and the curve geometry can be changed using them as well as other tools. Once ready use the Escape button on the keyboard. The stiffener is recreated picking up the changes in the curve.\n\n\n\nIn\nEscape\nEdit\nArrow down\nEdit\nCurve Editing\nEscape\nEdit\nEscape"}
{"Headers": "Tooltips", "Content": "Tooltips can show properties of model entities when hovering on a model entity and pressing the <Shift> key.\n\nThe contents of the tooltip can be customized using the function Tooltips in the Configure group on the Admin ribbon tab.\n\n\n\nShift\nTooltips\nConfigure\nAdmin"}
{"Headers": "Setup and Standards", "Content": "This section describes the setup and standards functionality for hull design.\n\n\n"}
{"Headers": "Standards", "Content": "Material quality needs to be stored in AVEVA Catalog Application in PROP (Property Database). A hull material is defined by a SOLI element with a SOLEXT element used for additional information and a TDEN and SDEN element defining density of the material.\n\n\n\n"}
{"Headers": "Built-in Standards", "Content": "This section describes the built-in standards for hull design.\n\n\n"}
{"Headers": "Built-in Profiles", "Content": "The Hull Design built-in profile standard covers the profile types that are traditionally used in shipbuilding. Each profile has a type code and profiles are selected by using this type code.\nThe table below specifies the profile types normally used in shipbuilding. It shows the profile type, its cross-section and the parameters that are required to control the size of the profile section. When selecting a certain profile, it is important that the correct number of parameters is given in the order specified in the table.\n\n\n\nSome remarks on the built-in standard:\nA standard hole in Hull Design is defined by a hole designation (string) and parameters. The built-in standard is presented in the tables below.\n\n\nA standard hole is described in a co-ordinate system of its own. It is located by specifying the position of the origin of its local co-ordinate system. Turning of the hole is done by specifying the angle to which the u-axis should be turned, see the figure below.\n\nIn the specification of the different hole types the figures show the shape of the holes, their local co-ordinate system and thus their reference point. The figures also show how the holes will be oriented if no turning angle is specified.\nFlat bars:\nProfile type 11 has the same properties as a profile type 10, however profile type 11 cannot be converted into a plate part in the production programs.\nBulb bars:\nProfile type 21 is a special Polish variant of the ordinary bulb bar. If used in combination with any of the environment variables SBH_RUSSIAN_BULB, SBH_CHINESE_BULB or SBH_JAPANESE_BULB this profile type may be used for the type of bulb bar used in Russia, China or Japan.\nProfile type 23 is the big type of welded bulb bar with a constant bulb size that is manufactured by the INEXA steel mill and sold under the product name Jumbo Bulb Flat.\nU- and I-bars:\nThe built-in standard for U- and I-bars is according to DIN standard.\nFlat bars:\nProfile type 11 has the same properties as a profile type 10, however profile type 11 cannot be converted into a plate part in the production programs.\nFlat bars:\nProfile type 11 has the same properties as a profile type 10, however profile type 11 cannot be converted into a plate part in the production programs.\nBulb bars:\nProfile type 21 is a special Polish variant of the ordinary bulb bar. If used in combination with any of the environment variables SBH_RUSSIAN_BULB, SBH_CHINESE_BULB or SBH_JAPANESE_BULB this profile type may be used for the type of bulb bar used in Russia, China or Japan.\nProfile type 23 is the big type of welded bulb bar with a constant bulb size that is manufactured by the INEXA steel mill and sold under the product name Jumbo Bulb Flat.\nBulb bars:\nProfile type 21 is a special Polish variant of the ordinary bulb bar. If used in combination with any of the environment variables SBH_RUSSIAN_BULB, SBH_CHINESE_BULB or SBH_JAPANESE_BULB this profile type may be used for the type of bulb bar used in Russia, China or Japan.\nProfile type 23 is the big type of welded bulb bar with a constant bulb size that is manufactured by the INEXA steel mill and sold under the product name Jumbo Bulb Flat.\nU- and I-bars:\nThe built-in standard for U- and I-bars is according to DIN standard.\nU- and I-bars:\nThe built-in standard for U- and I-bars is according to DIN standard.\n\n\n\nFlat bars:\nBulb bars:\nU- and I-bars:"}
{"Headers": "Built-in Standard Notches", "Content": "A standard hole in Hull Design is defined by a hole designation (string) and parameters. The built-in standard is presented in tables below.\n\n\n\n\n\n\n\n\n\n"}
{"Headers": "Cutouts", "Content": "Cutouts are available from two groups. The first group is built in to support basic slot and lug configuration in structural design. The second group is the AVEVA Marine version of built-in cutouts. This will be further extended in future releases to also cover the external cutout definition of AVEVA Marine.\n\nThe DCTOUT element contains the definition data of the cutout. This is stored in the type of cutout in attribute Tpltyp and the parameters in attribute Tplpar. The clip definition element DCLIP resides below the cutout element and use the same attribute for the clip parameters.\n\n\n\nTpltyp\nTplpar"}
{"Headers": "Functional Overview", "Content": "This section describes the functional overview for hull design.\n\n\n"}
{"Headers": "The Hull Design Tab", "Content": "This section describes the functionality available from the hull design tab.\n\n\n"}
{"Headers": "Create", "Content": "This section describes the functionality available from the Create group.\n\n\n\n"}
{"Headers": "Panel", "Content": "This section describes the functionality available from the panel command.\n\nPanels are created in a zone selected as current element (CE) prior to the use of the subfunctions below. If the zone is defined with reference to a space, then all panels will get bounded by the geometry of this space.\nSubfunction\nDescription\nPlane\nCreate panel in plane.\nPick a grid position or select any of the optional ways to define the location plane of the panel.\nThe Offset option adds the given offset to any selected grid plane.\nBy default a plate will be added to the panel. The option Omit plate will suppress the creation of a plate.\nWhen the planes are accepted, panels are generated and displayed.\nRepetition Terms\nPanel location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\nSurface\nCreate panel in surface.\nPick the surfaces or key in the surface names. The selected elements are highlighted in the canvas. Accept the selected surfaces and the panels are generated and displayed.\nBy default a plate will be added to the panel. The option Omit plate will suppress the creation of a plate.\nWhen the selected surfaces are accepted, panels are generated and displayed.\nArrangements\nCreates panel from functional area arrangements.\nPick an area arrangement of scantling type then click Accept or select Curve Arrangement of Profile Trace type and / or Area Arrangement of Openings type.\nSubfunction\nDescription\nPlane\nCreate panel in plane.\nPick a grid position or select any of the optional ways to define the location plane of the panel.\n\nThe Offset option adds the given offset to any selected grid plane.\nBy default a plate will be added to the panel. The option Omit plate will suppress the creation of a plate.\nWhen the planes are accepted, panels are generated and displayed.\nRepetition Terms\nPanel location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\n\nSurface\nCreate panel in surface.\nPick the surfaces or key in the surface names. The selected elements are highlighted in the canvas. Accept the selected surfaces and the panels are generated and displayed.\n\nBy default a plate will be added to the panel. The option Omit plate will suppress the creation of a plate.\nWhen the selected surfaces are accepted, panels are generated and displayed.\nArrangements\nCreates panel from functional area arrangements.\nPick an area arrangement of scantling type then click Accept or select Curve Arrangement of Profile Trace type and / or Area Arrangement of Openings type.\n\n\nSubfunction\nDescription\nPlane\nCreate panel in plane.\nPick a grid position or select any of the optional ways to define the location plane of the panel.\nThe Offset option adds the given offset to any selected grid plane.\nBy default a plate will be added to the panel. The option Omit plate will suppress the creation of a plate.\nWhen the planes are accepted, panels are generated and displayed.\nRepetition Terms\nPanel location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\nSurface\nCreate panel in surface.\nPick the surfaces or key in the surface names. The selected elements are highlighted in the canvas. Accept the selected surfaces and the panels are generated and displayed.\nBy default a plate will be added to the panel. The option Omit plate will suppress the creation of a plate.\nWhen the selected surfaces are accepted, panels are generated and displayed.\nArrangements\nCreates panel from functional area arrangements.\nPick an area arrangement of scantling type then click Accept or select Curve Arrangement of Profile Trace type and / or Area Arrangement of Openings type.\n\n\n\nSubfunction\nDescription\nPlane\nOffset\nOmit\nplate\nSurface\nOmit\nplate\nArrangements\nAccept\nCurve Arrangement of Profile Trace\nArea Arrangement of Openings"}
{"Headers": "Seam", "Content": "This section describes the functionality available from the seam command.\n\nSubfunction\nDescription\nPlane\nCreate seam in the intersection with plane\nPick a panel and then define the intersection plane. Then pick a grid position or select any of the optional ways to define the intersection plane.\nThe Offset option adds the given offset to any selected grid plane.\nWhen the intersection planes are accepted, the seams are added to the panel.\nRepetition Terms\nSeam location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\nSurface\nCreate seam in the intersection with surface\nPick a panel and then pick surfaces. When the selected surfaces are accepted, seams are added to the panel.\nCurve\nCreate seam in selected curve.\nPick a panel and then pick curves located in the panel surface. Curves can either be local, defined in the panel, or global (common reference curves). When the selected curves are accepted, seams are added to the panel.\nArrangements\nCreate seam from seam arrangement\nPick a panel and then pick seam arrangement (global seams) located in the panel surface. When the selected seam arrangements are accepted, seams are added to the panel.\nSubfunction\nDescription\nPlane\nCreate seam in the intersection with plane\nPick a panel and then define the intersection plane. Then pick a grid position or select any of the optional ways to define the intersection plane.\n\nThe Offset option adds the given offset to any selected grid plane.\nWhen the intersection planes are accepted, the seams are added to the panel.\nRepetition Terms\nSeam location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\n\nSurface\nCreate seam in the intersection with surface\nPick a panel and then pick surfaces. When the selected surfaces are accepted, seams are added to the panel.\nCurve\nCreate seam in selected curve.\nPick a panel and then pick curves located in the panel surface. Curves can either be local, defined in the panel, or global (common reference curves). When the selected curves are accepted, seams are added to the panel.\nArrangements\nCreate seam from seam arrangement\nPick a panel and then pick seam arrangement (global seams) located in the panel surface. When the selected seam arrangements are accepted, seams are added to the panel.\n\nSubfunction\nDescription\nPlane\nCreate seam in the intersection with plane\nPick a panel and then define the intersection plane. Then pick a grid position or select any of the optional ways to define the intersection plane.\nThe Offset option adds the given offset to any selected grid plane.\nWhen the intersection planes are accepted, the seams are added to the panel.\nRepetition Terms\nSeam location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\nSurface\nCreate seam in the intersection with surface\nPick a panel and then pick surfaces. When the selected surfaces are accepted, seams are added to the panel.\nCurve\nCreate seam in selected curve.\nPick a panel and then pick curves located in the panel surface. Curves can either be local, defined in the panel, or global (common reference curves). When the selected curves are accepted, seams are added to the panel.\nArrangements\nCreate seam from seam arrangement\nPick a panel and then pick seam arrangement (global seams) located in the panel surface. When the selected seam arrangements are accepted, seams are added to the panel.\n\n\n\nSubfunction\nDescription\nPlane\nOffset\nSurface\nCurve\nArrangements"}
{"Headers": "Hole", "Content": "This section describes the functionality available from the hole command.\n\nSubfunction\nDescription\nStandard Hole\nCreate standard hole in panel.\nPick a panel and then give points. Indicate or key in the points. When points are accepted, the holes are created, by default as standard hole D1000, to get visual feedback. The wanted hole designation and size is defined in the next step using the property grid.\nFrom Curve\nCreate hole from curve.\nPick a panel and then pick curves located in a panel surface. Curves can either be local, defined in the panel, or global (common reference curves). When the selected curves are accepted, holes are added to the panel.\nSubfunction\nDescription\nStandard Hole\nCreate standard hole in panel.\nPick a panel and then give points. Indicate or key in the points. When points are accepted, the holes are created, by default as standard hole D1000, to get visual feedback. The wanted hole designation and size is defined in the next step using the property grid.\nFrom Curve\nCreate hole from curve.\nPick a panel and then pick curves located in a panel surface. Curves can either be local, defined in the panel, or global (common reference curves). When the selected curves are accepted, holes are added to the panel.\n\nSubfunction\nDescription\nStandard Hole\nCreate standard hole in panel.\nPick a panel and then give points. Indicate or key in the points. When points are accepted, the holes are created, by default as standard hole D1000, to get visual feedback. The wanted hole designation and size is defined in the next step using the property grid.\nFrom Curve\nCreate hole from curve.\nPick a panel and then pick curves located in a panel surface. Curves can either be local, defined in the panel, or global (common reference curves). When the selected curves are accepted, holes are added to the panel.\n\n\n\nSubfunction\nDescription\nStandard Hole\nFrom Curve"}
{"Headers": "Notch", "Content": "This section describes the functionality available from the notch command.\n\nIn order to get early visual feedback, all notches are created with default designation and size (R35). The wanted notch designation and size is defined in the next step using the property grid.\nSubfunction\nDescription\nAt Seam\nCreate notch at seam intersection.\nPick a panel and then a panel with seams at boundary intersections. Seams are displayed with graphical handles and you are prompted to pick the seams.\nWhen the seams are selected and accepted, the notches are added to the panel.\nAt Plane\nCreate notch at plane intersection\nPick a boundary limit of a panel (turned on using Limit in the Visibility group) and then define the intersection plane. There is a prompt to pick a grid position or to select any of the optional ways to define the intersection plane. Alternatives are presented in canvas when using arrow-down key:\nThe Offset option adds the given offset to any selected grid plane.\nWhen the intersection planes are accepted, the notches are added to the panel.\nRepetition Terms\nSeam location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\nCorner Notch\nCreate notch in corner.\nPick a panel and then corners (presented with model grips automatically).\nSelect and then accept the corners, the notches are added to the panel.\nSubfunction\nDescription\nAt Seam\nCreate notch at seam intersection.\nPick a panel and then a panel with seams at boundary intersections. Seams are displayed with graphical handles and you are prompted to pick the seams.\nWhen the seams are selected and accepted, the notches are added to the panel.\nAt Plane\nCreate notch at plane intersection\nPick a boundary limit of a panel (turned on using Limit in the Visibility group) and then define the intersection plane. There is a prompt to pick a grid position or to select any of the optional ways to define the intersection plane. Alternatives are presented in canvas when using arrow-down key:\n\nThe Offset option adds the given offset to any selected grid plane.\nWhen the intersection planes are accepted, the notches are added to the panel.\nRepetition Terms\nSeam location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\n\nCorner Notch\nCreate notch in corner.\nPick a panel and then corners (presented with model grips automatically).\nSelect and then accept the corners, the notches are added to the panel.\n\nSubfunction\nDescription\nAt Seam\nCreate notch at seam intersection.\nPick a panel and then a panel with seams at boundary intersections. Seams are displayed with graphical handles and you are prompted to pick the seams.\nWhen the seams are selected and accepted, the notches are added to the panel.\nAt Plane\nCreate notch at plane intersection\nPick a boundary limit of a panel (turned on using Limit in the Visibility group) and then define the intersection plane. There is a prompt to pick a grid position or to select any of the optional ways to define the intersection plane. Alternatives are presented in canvas when using arrow-down key:\nThe Offset option adds the given offset to any selected grid plane.\nWhen the intersection planes are accepted, the notches are added to the panel.\nRepetition Terms\nSeam location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\nCorner Notch\nCreate notch in corner.\nPick a panel and then corners (presented with model grips automatically).\nSelect and then accept the corners, the notches are added to the panel.\n\n\n\nSubfunction\nDescription\nAt Seam\nAt Plane\nLimit\nVisibility\nOffset\nCorner Notch"}
{"Headers": "Cutout", "Content": "Create cutout at stiffener intersection\nPick a panel and then intersecting stiffeners.\nWhen the selected stiffeners are accepted, the cutouts are added to the panel and presented to get immediate visual feedback. The default cutout type is the type T (direct with clip), which can be changed using the property grid.\n\n\n\nT"}
{"Headers": "Plate", "Content": "Create plate in panel.\nPick a panel boundary and give a point in the intended plate area.\nThe plate is created with a default thickness of 10 mm and with material side defined as positive. The properties of the plate can be adjusted using the property grid.\n\n\n"}
{"Headers": "Stiffener", "Content": "This section describes the functionality available from the stiffener command.\n\nIn order to get early visual feedback, all stiffeners are created with default profile type and parameters (10 100*8). The wanted profile type and parameters are defined in the next step using the property grid.\nSubfunction\nDescription\nAt Plane\nCreate stiffener at plane intersection.\nPick a panel and then define the intersection plane. Then pick a grid position or select any of the optional ways to define the intersection plane.\nThe Offset option adds the given offset to any selected grid plane.\nWhen the intersection planes are accepted, the stiffeners are added to the panel.\nRepetition Terms\nStiffener location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\nAt Intersection\nCreate stiffener in the intersection with surface\nPick a panel and then pick surfaces. When the selected surfaces are accepted, stiffeners are added to the panel.\nAlong Limit\nCreate stiffener along and parallel to a panel limit\nThe model grips for panel limits need to be visible to allow for picking. See functions Limits in the Visibility group.\nPick a panel and then pick limits on this panel. When the selected limits are accepted, stiffeners are added to the panel placed parallel to the selected limits.\nAlong Curve\nCreate stiffener in selected curve.\nPick a panel and then pick curves located in a panel surface. Curves can either be local, defined in the panel, or global (common reference curves). When the selected curves are accepted, stiffeners are added to the panel.\nSubfunction\nDescription\nAt Plane\nCreate stiffener at plane intersection.\nPick a panel and then define the intersection plane. Then pick a grid position or select any of the optional ways to define the intersection plane.\n\nThe Offset option adds the given offset to any selected grid plane.\nWhen the intersection planes are accepted, the stiffeners are added to the panel.\nRepetition Terms\nStiffener location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\n\nAt Intersection\nCreate stiffener in the intersection with surface\nPick a panel and then pick surfaces. When the selected surfaces are accepted, stiffeners are added to the panel.\nAlong Limit\nCreate stiffener along and parallel to a panel limit\nThe model grips for panel limits need to be visible to allow for picking. See functions Limits in the Visibility group.\nPick a panel and then pick limits on this panel. When the selected limits are accepted, stiffeners are added to the panel placed parallel to the selected limits.\nAlong Curve\nCreate stiffener in selected curve.\nPick a panel and then pick curves located in a panel surface. Curves can either be local, defined in the panel, or global (common reference curves). When the selected curves are accepted, stiffeners are added to the panel.\n\nSubfunction\nDescription\nAt Plane\nCreate stiffener at plane intersection.\nPick a panel and then define the intersection plane. Then pick a grid position or select any of the optional ways to define the intersection plane.\nThe Offset option adds the given offset to any selected grid plane.\nWhen the intersection planes are accepted, the stiffeners are added to the panel.\nRepetition Terms\nStiffener location can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\nAt Intersection\nCreate stiffener in the intersection with surface\nPick a panel and then pick surfaces. When the selected surfaces are accepted, stiffeners are added to the panel.\nAlong Limit\nCreate stiffener along and parallel to a panel limit\nThe model grips for panel limits need to be visible to allow for picking. See functions Limits in the Visibility group.\nPick a panel and then pick limits on this panel. When the selected limits are accepted, stiffeners are added to the panel placed parallel to the selected limits.\nAlong Curve\nCreate stiffener in selected curve.\nPick a panel and then pick curves located in a panel surface. Curves can either be local, defined in the panel, or global (common reference curves). When the selected curves are accepted, stiffeners are added to the panel.\n\n\n\nSubfunction\nDescription\nAt Plane\nOffset\nAt Intersection\nAlong Limit\nLimits\nVisibility\nAlong Curve"}
{"Headers": "Brackets", "Content": "Create bracket.\nBrackets can be placed in different ways depending on the selected model elements and their topology. The bracket location is always defined from the first selected stiffener.\nPick an orienting stiffener and then pick a connecting profile.\n\n\n"}
{"Headers": "Pillar", "Content": "Create pillar along curve.\nPillars are created along curves, so a prerequisite is to define curves, preferable in the panel context prior to using this function.\nPick a panel and then pick curves to define the pillar trace.\nThen the selected the curves must be accepted and pillars are added to the panel\nIf the panel only contains pillars, that is a pillar arrangement, then the boundary of the panel can be deleted to allow presentation only of the defined pillars.\n\n\n"}
{"Headers": "Face Plate", "Content": "Create face plate along limit or in hole.\nTo allow selection in canvas, the model grips for limits and holes need to be made visible.\nPick a panel and then pick panel limits or holes. When the selection is accepted, the face plates are added to the panel with default profile type and dimensions (10 100*8). Use the Property grid to adjust to correct dimensions.\n\n\n\nProperty"}
{"Headers": "Modify", "Content": "This section describes the functionality available from the Modify group.\n\n\n\n"}
{"Headers": "Regroup", "Content": "Regroup definition data for hull components that generates more than one instance.\nThe definition data for hull components can be valid for several instances, for example stiffeners defined in grid positions with the same profile properties are defined in only one definition. If changes shall be done that does not affect all instances, then the definition needs to be split into two or more hull components.\nPick a panel and then pick individual hull instances of components that shall be extracted into a new group (and taken out from the existing one). When accepted, the regrouping is done.\n\n\n"}
{"Headers": "Add Limits", "Content": "Add limits to panels.\nPick one or more panels. In the next step, pick one or more limiting elements in any order. When accepted the panel or panels are limited. In case of ambiguity, that is if more than one panel boundary is possible, select which panel part to keep. Default is to limit panels by other models but with arrow-down you can access other options like Limiting by a Grid Plane or adding an offset to a referred model used as a limit.\n\n\n\nLimiting by a Grid Plane"}
{"Headers": "Remove Limits", "Content": "Remove all limits of one or more panels.\nPick one or more panels. When accepted, the limits will be removed from the panels.\n\n\n"}
{"Headers": "Reset Limits", "Content": "This section describes the functionality available from the reset limit command.\n\nReset panel limits to those of the location surface or the containing space.\nReset the panel limits to the ones from a space linked to by the zone owning the panel.\nSelect one or more panels and accept. Any existing panel limits will be replaced by the ones from the space connected to each panel, if any.\nReset the panel limits to the ones from the surface in which the panel is located.\nSelect one or more panels and accept. Any existing panel limits will be replaced by the ones from the location surface of the panel, if any.\n\n\n"}
{"Headers": "Single Panel", "Content": "Sets editing mode to single panels only when panels are cloned.\n\n\n"}
{"Headers": "Tools", "Content": "This section desribes the functionality available from the Tools group.\n\n\n\n"}
{"Headers": "Copy", "Content": "This section describes the functionality available from the copy command.\n\nCreate one or many linked copies of a panel by translating along a main axis or by mirroring in a plane.\nMirror\nPick a panel and accept the selection.\nTranslate\nPick a panel and then select a grid position for location (the last panel location if a series of panels shall be created) or select arrow-down for options.\n\nThe function is creating a single copy panel in grid positions by default. The Option menu is used when multiple panels shall be created or if an absolute coordinate for location shall be given.\nIf multiple panels are created, define the offset by graphically placing an image of the panel along the grid.\n\n\n\nMirror\nTranslate\nOption"}
{"Headers": "Clone", "Content": "This section describes the functionality available from the clone command.\n\nCreate one or many linked copies of a panel by translating along a main axis or by mirroring in a plane. The created panels will be linked and a subsequent change to any of these linked panels will be applied to all (in case Single Panel mode is not selected).\nMirror\nPick a panel and accept the selection.\nTranslate\nPick a panel and then select a grid position for location (the last panel location if a series of panels shall be created) or select arrow-down for options.\n\nThis function is creating a single clone panel in grid positions by default. The Option menu is used when multiple cloned panels shall be created or if an absolute coordinate for location shall be given.\nIf multiple cloned panels are created, define the offset by graphically placing an image of the panel along the grid.\n\n\n\nSingle Panel\nMirror\nTranslate\nOption"}
{"Headers": "Recreate", "Content": "This section describes the functionality available from the recreate command.\nUpdates elements with definition data, that is panels, arrangements, surfaces, curves or points. Updated elements are recreated from its definition data and referenced surroundings.\nPick the elements and when accepted these elements are recreated.\n\nThe recreate function optimizes performance by only regenerating models that are affected by other changes. Invoke the Force option in the rare case the recreate function does not seem to update models as expected.\n\n\n\nForce"}
{"Headers": "Visibility", "Content": "This section describes the functionality available from the visibilty group.\n\nSome of the hull components are not represented by physical geometry, but still necessary to get visible in the canvas when modelling. The functions in this group turns on (or off) model handles for these types of components\n\n\n"}
{"Headers": "Space Management", "Content": "The Space Management application handles arrangement design which includes the definition of spaces, areas and curves possibly with functional data to specialize for a specific design purpose. The arrangements can be used to coordinate other design activities as well as be used downstream to support other design activities with geometry data and functional properties.\n\n\n\n\n\n\nSpace Management"}
{"Headers": "Basic Concepts", "Content": "This section describes the basic concepts of Space Management.\n\n\n"}
{"Headers": "Common Reference Model", "Content": "The design process in complex projects is characterised by a very high frequency of change and with multiple disciplines working in the same areas using the same basic data for referencing. To manage change and concurrency, we need to build a model that can handle both global and local changes and that can hold stable references to all other functional model entities. To support this, a Common Reference Model (CRM) is used.\nReferences to the CRM entities are registered by the referencing elements and can be found by querying the referencing element, that is q backref.\n\n\n\nq backref"}
{"Headers": "Model Entities in CRM", "Content": "The CRM is a collection of model entities that subdivides the project and can be used to support referencing and thus simplify in a process with high frequency of change and concurrency. These model entities all share some characteristics. They all have a geometry definition, does not contain any functional properties, can be presented graphically and can be referenced by other model entities. These model entities are:\nFurthermore, the grid system is considered to belong to the CRM being one very important entity to use for referencing.\nWhen limiting for example a surface by selecting limiting objects, the canvas can sometimes be cluttered and elements to be selected may be presented behind other elements. The user can in this case turn off the shading (using function Current View in the Settings group in the View tab) while selecting and then turn on shading again when the selection is ready.\nSurfaces\nCurves\nPoints\nSurfaces\nSurfaces\nCurves\nCurves\nPoints\nPoints\nNote: Turning shading on or off can also be done using short cut key F11.\n\n\n\nCurrent View\nSettings\nView\nNote\n:\nF11"}
{"Headers": "Surfaces", "Content": "Surfaces can be sculptured, knuckled or planar and are stored in a surface world (with element name SSOWLD). The surface world can be linked to a space that will automatically limit all the surfaces that are created in this surface world.\nEach surface is stored with a definition and an instance (containing the actual geometry of the surface). The surface data structure is presented below.\n\nKnuckled and planar surfaces are named polyface surfaces within this document.\n\n\n"}
{"Headers": "Curves", "Content": "Curves are created as the intersection between two elements, that is surfaces or planes. The resulting curve will be located in the first of the two intersection planes, that is a surface or a grid plane. The second intersection element can also be a plane and can also be defined as an absolute coordinate.\nThe common reference curves are stored in a curve world (with element name CURWLD). Local curves can be created and stored below other elements in applications working with curves. This is then further described in these application user guides, but generally the same functions and data structure is used also for these local curves.\nEach curve is stored with a definition and an instance (containing the actual geometry of the curve). The curve data structure is presented below.\n\n\n\n"}
{"Headers": "Points", "Content": "Points are created as the intersection between two elements, that is surfaces, planes or curves. The resulting point will be located in the first of the two intersection elements, that is a surface, a grid plane or a curve. The second intersection element can also be a plane defined as an absolute coordinate.\nThe common reference points are stored in a point world (with element name PNTWLD). Local points can be created and stored below other elements in applications working with points. This is then further described in these application manuals, but generally the same functions and data structure is used also for these local points.\nEach point is stored with a definition and an instance (containing the actual geometry of the point). The point data structure is presented below.\n\n\n\n"}
{"Headers": "Project Box", "Content": "The project box is limiting the created model elements when no limits are given explicitly or implicitly if a space is connected to for example a zone or a world.\nA project box is defined as an envelope element. The envelope is created in a surface world (below an SSOWLD element). Create the envelope in the Command window using the following commands:\nNEW ENVLOP\nNEW ENVDAT\nOnce created, use the property grid to update the two points that define the envelope box. If working in a ship project and if no envelope is created then the project box is by default the extension of the ship grid coordinates extended by 10 percent:\n\nA more refined enveloping can be achieved in various operations by selecting a space to act as an envelope. It is recommended to define a specific space arrangement of generic type with volume representing the exact maximum extension when creating surfaces. This arrangement should be used only for this purpose and not further divided and changed. The single space in this arrangement can be named and referenced by the surface world (SSOWLD) currently used. Any surface created in this world will automatically get limits from the envelope space.\nEnveloping is also achieved when modelling panels in zones with a space reference (normally a block arrangement space).\n\n\n\nCommand"}
{"Headers": "The Functional Use of CRM", "Content": "There are different functional properties and definitions that are needed to get the model in a state where it can be used in the design process. Depending on discipline and usage, these properties can vary and, in some cases, become contradictory. The CRM is therefore kept clean from all sorts of functional properties and this information is instead applied to a functional model layer, the Functional Arrangements as described in this document.\nFrom a user perspective, this is made transparent by specialized application functions. Consider for example a marine structural designer that needs to subdivide the project with decks and bulkheads or modelling design seams in positions where a thickness change is needed. While doing this modelling, two design entities are created, a surface or a curve in CRM representing the geometry, but also a functional entity that can host the properties of the decks and bulkheads or seams. Later, more functional entities will be created referencing the same surfaces, for example when creating fire zone limits or subdividing into different compartments or design areas.\nWhen the same marine structural designer is creating steel on one of the earlier created decks, the properties can be picked up from any of the related functional entities, but the actual reference stored with the created steel entity will be to the surface in the CRM.\nWhen changing the project breakdown, for example moving decks or bulkheads in a ship, the design change is made in one place affecting the CRM entity. All other functional and physical entities can then easily be recreated to get the correct updated geometry\n\n\n\nFunctional Arrangements\nFunctional Arrangements"}
{"Headers": "Functional Arrangements", "Content": "Functional arrangements can consist of spaces, areas or curves and are used to represent a design on a high level. Geometrically these arrangements are represented by volumes, surfaces and curves that are subdivided to a level decided by the user. The subdivided model is managed to avoid any accidental void areas and all geometry operations are registered to allow for recreation of the arrangement in case any surroundings are changed.\nOnce an arrangement is created, properties can be added to define its functional purpose.\n\n\n"}
{"Headers": "Envelopes and Subdivisions", "Content": "Individual spaces, areas and functional curve parts are not modelled. Instead they are created in a process where an envelope, a surface or a curve is subdivided by limits defined in CRM, that is surfaces, curves and grid positions. The starting point when creating a space arrangement is the envelope which is defined either as a number of limits forming a closed volume, an already created space or by selecting a modelled primitive. The area and curve arrangements are using one of the CRM entities surface or curves as starting point. Furthermore, already generated spaces, areas and functional curves can be defined as the starting point of a new arrangement. If these are space arrangements, a hierarchy of spaces can be created which is further explained below.\nThe subdivision is a completely automatic process. Spaces or areas are created in the arrangement when the subdivision results in closed volumes or areas.\nMany different arrangements can use the same subdividing limits, for example a certain deck surface is used as limit in a painting area arrangement as well as in a compartment arrangement. The modelling work made on this deck can be reused and parallel arrangements are automatically created referencing the same modelled geometry information.\n\n\n"}
{"Headers": "Hierarchies", "Content": "A hierarchy of spaces can be generated as there will be spaces within spaces. Hierarchies are created by selecting a space in any arrangement as an envelope and subdivide this space further with selected boundaries. The subdivided space is not changed and 'owns' the spaces resulting from its subdivision. A reference to the space selected as envelope for the new space arrangement is registered using the attribute hierarchy. This registration establishes the hierarchy and allow for querying the original space for sub-arrangements using the backref attribute (that is querying writing q backref on the command line).\n\n\n\nbackref\nq backref"}
{"Headers": "Geometry Operations", "Content": "This section describes the geometry operations of Space Management.\n\n\n\nSpace Management"}
{"Headers": "Space Arrangements", "Content": "Any closed volume, for example a sculptured surface or a space from another arrangement can be added or subtracted from an arrangement and two adjacent spaces within an arrangement can be merged into one space. The result of these operations is illustrated by the three pictures below:\nMerge Operation:\n\nSubtract Operation:\n\nAdd Operation\n\n\n\n"}
{"Headers": "Area Arrangements", "Content": "The merge operation works in a similar manner as for spaces, two adjacent functional areas can be merged into one.\nAdd and subtract are not applicable, instead an In-print function can be used. The purpose of the In-print function is to create a functional area arrangement bases on selected space arrangement, that is to make a floor plan. The functional areas will be limited by the same limits that were used to create the space arrangement.\n\n\n\nIn-print\nIn-print"}
{"Headers": "Curve Arrangement", "Content": "The merge operation works in a similar manner as for spaces, two adjacent functional curves can be merged into one.\n\n\n"}
{"Headers": "Void Entities", "Content": "Entities within an arrangement that are of no interest for the planned usage of an arrangement can be set to void, meaning these spaces, areas or functional curve entities will not be displayed or operated on.\n\n\n"}
{"Headers": "Functional Worlds and Arrangements", "Content": "A functional world, this is space, area or curve, is created with a type definition and all arrangements generated in this world will be of the same type. The type definition then controls the set of attributes on the arrangement, on the individual functional objects (for example spaces) and on the functional boundaries (for example space boundaries).\nIt is advisable to select a database when creating the top elements. If not, the arrangement will be stored in the first writable database.\n\n\n"}
{"Headers": "Space Arrangement Types", "Content": "The following space arrangement types are possible to define:\nType\nPurpose\nDefault Color\nTranslucency\nGeneric\nThis space arrangement type can be used when any of the specific types are not suitable.\nSalmon\n50%\nCompartment\nSpace arrangements of this type are suitable for hydrostatic and hydrodynamic calculations.\nBrightred\n50%\nLayout\nSpace arrangements of this kind are defined to handle all general layout work with possibilities to plan, store and follow up mass property data.\nPink\n50%\nPainting Areas\nThese space arrangements are defined to handle painting area calculations.\nDeeppink\n50%\nProduction Blocks\nSpace arrangements of this type are used to define the production block structure.\nMaroon\n50%\nZones\nSpace arrangements of this type are suitable for definition of zones in a ship structure.\nOrangered\n50%\nType\nPurpose\nDefault Color\nTranslucency\nGeneric\nThis space arrangement type can be used when any of the specific types are not suitable.\nSalmon\n50%\nCompartment\nSpace arrangements of this type are suitable for hydrostatic and hydrodynamic calculations.\nBrightred\n50%\nLayout\nSpace arrangements of this kind are defined to handle all general layout work with possibilities to plan, store and follow up mass property data.\nPink\n50%\nPainting Areas\nThese space arrangements are defined to handle painting area calculations.\nDeeppink\n50%\nProduction Blocks\nSpace arrangements of this type are used to define the production block structure.\nMaroon\n50%\nZones\nSpace arrangements of this type are suitable for definition of zones in a ship structure.\nOrangered\n50%\n\nType\nPurpose\nDefault Color\nTranslucency\nGeneric\nThis space arrangement type can be used when any of the specific types are not suitable.\nSalmon\n50%\nCompartment\nSpace arrangements of this type are suitable for hydrostatic and hydrodynamic calculations.\nBrightred\n50%\nLayout\nSpace arrangements of this kind are defined to handle all general layout work with possibilities to plan, store and follow up mass property data.\nPink\n50%\nPainting Areas\nThese space arrangements are defined to handle painting area calculations.\nDeeppink\n50%\nProduction Blocks\nSpace arrangements of this type are used to define the production block structure.\nMaroon\n50%\nZones\nSpace arrangements of this type are suitable for definition of zones in a ship structure.\nOrangered\n50%\n\n\n\nType\nPurpose\nDefault Color\nTranslucency"}
{"Headers": "Area Arrangement Types", "Content": "The following space arrangement types are possible to define:\nType\nPurpose\nDefault Colour\nTranslucency\nGeneric\nThis area arrangement type can be used when any of the specific types are not suitable.\nCyan\n50%\nScantling\nArea arrangement of this type can be used for definition of scantling data.\nSteelblue\n50%\nOpenings\nArea arrangement of this type can be used for definition of large openings.\nAquamarine\n50%\nInsulation\nThese area arrangements can be used to define insulation.\nLightblue\n50%\nPainting Areas\nThese area arrangements are defined to handle painting area calculations.\nMidnight\n50%\nType\nPurpose\nDefault Colour\nTranslucency\nGeneric\nThis area arrangement type can be used when any of the specific types are not suitable.\nCyan\n50%\nScantling\nArea arrangement of this type can be used for definition of scantling data.\nSteelblue\n50%\nOpenings\nArea arrangement of this type can be used for definition of large openings.\nAquamarine\n50%\nInsulation\nThese area arrangements can be used to define insulation.\nLightblue\n50%\nPainting Areas\nThese area arrangements are defined to handle painting area calculations.\nMidnight\n50%\n\nType\nPurpose\nDefault Colour\nTranslucency\nGeneric\nThis area arrangement type can be used when any of the specific types are not suitable.\nCyan\n50%\nScantling\nArea arrangement of this type can be used for definition of scantling data.\nSteelblue\n50%\nOpenings\nArea arrangement of this type can be used for definition of large openings.\nAquamarine\n50%\nInsulation\nThese area arrangements can be used to define insulation.\nLightblue\n50%\nPainting Areas\nThese area arrangements are defined to handle painting area calculations.\nMidnight\n50%\n\n\n\nType\nPurpose\nDefault Colour\nTranslucency"}
{"Headers": "Curve Arrangement Types", "Content": "The following Space Arrangement types are possible to define:\nType\nPurpose\nDefault Colour\nTranslucency\nGeneric\nThis curve arrangement type can be used when any of the specific types are not suitable.\nTan\n0%\nDesign Seam\nThese curve arrangements define design seams.\nSandybrown\n0%\nProfile Trace\nThese curve arrangements define profile traces for example transversals and longitudinals.\nDarkbrown\n0%\nType\nPurpose\nDefault Colour\nTranslucency\nGeneric\nThis curve arrangement type can be used when any of the specific types are not suitable.\nTan\n0%\nDesign Seam\nThese curve arrangements define design seams.\nSandybrown\n0%\nProfile Trace\nThese curve arrangements define profile traces for example transversals and longitudinals.\nDarkbrown\n0%\n\nType\nPurpose\nDefault Colour\nTranslucency\nGeneric\nThis curve arrangement type can be used when any of the specific types are not suitable.\nTan\n0%\nDesign Seam\nThese curve arrangements define design seams.\nSandybrown\n0%\nProfile Trace\nThese curve arrangements define profile traces for example transversals and longitudinals.\nDarkbrown\n0%\n\n\n\nType\nPurpose\nDefault Colour\nTranslucency"}
{"Headers": "Data Structure of Arrangements", "Content": "The data structure of all arrangements is built up in a hierarchy using nodes for the structure and attribute containers for the attributes that are specific to the arrangement type. The pictures below show the hierarchy with element names in the database.\n\n\n\n\n\n"}
{"Headers": "Attributes", "Content": "Attributes on space arrangements, on spaces and on space boundaries can be of different kinds and are also depending on the type of arrangement.\n\n\n"}
{"Headers": "Fixed Attributes", "Content": "Space arrangements, spaces and space boundaries, as well as functional areas and curves, are defined with attributes that store data to be used both during design work and in downstream usage of the arrangements. The attribute collection is depending on type of arrangement as described above. Below are the available attributes.\n\n\n"}
{"Headers": "Compartment Space Arrangement", "Content": "Attributes on element (SPMCSA).\nName\nDescription\nSPMPU\nPurpose code.\nDESC\nDescription.\nSPMCTY\nContent type. System defined values are:\nS - Stores\nA - Accommodation\nM - Machinery\nV - Void\nD - Dry cargo\nL - Liquid cargo\nSPMDE\nDensity. Unit is kg/m3.\nSPMCDE\nContent description.\nSPMALL\nStructure allowance. Value shall be in a range between 0 and 1 and is used to estimate steel reduction from compartments.\nSPMPER\nCompartment permeability. Value shall be in range between 0 and 1.\nSPMPED\nPermeability for use in damage calculations. Value shall be in range between 0 and 1.\nSPMTIC\nCompartment tightness code. System defined values are:\nair_tight\nnon_tight\noil_tight\nwater_tight\nweather_tight\nSPMTID\nCompartment tightness description.\nName\nDescription\nSPMPU\nPurpose code.\nDESC\nDescription.\nSPMCTY\nContent type. System defined values are:\nSPMDE\nDensity. Unit is kg/m3.\nSPMCDE\nContent description.\nSPMALL\nStructure allowance. Value shall be in a range between 0 and 1 and is used to estimate steel reduction from compartments.\nSPMPER\nCompartment permeability. Value shall be in range between 0 and 1.\nSPMPED\nPermeability for use in damage calculations. Value shall be in range between 0 and 1.\nSPMTIC\nCompartment tightness code. System defined values are:\nSPMTID\nCompartment tightness description.\n\nName\nDescription\nSPMPU\nPurpose code.\nDESC\nDescription.\nSPMCTY\nContent type. System defined values are:\nS - Stores\nA - Accommodation\nM - Machinery\nV - Void\nD - Dry cargo\nL - Liquid cargo\nSPMDE\nDensity. Unit is kg/m3.\nSPMCDE\nContent description.\nSPMALL\nStructure allowance. Value shall be in a range between 0 and 1 and is used to estimate steel reduction from compartments.\nSPMPER\nCompartment permeability. Value shall be in range between 0 and 1.\nSPMPED\nPermeability for use in damage calculations. Value shall be in range between 0 and 1.\nSPMTIC\nCompartment tightness code. System defined values are:\nair_tight\nnon_tight\noil_tight\nwater_tight\nweather_tight\nSPMTID\nCompartment tightness description.\nS - Stores\nA - Accommodation\nM - Machinery\nV - Void\nD - Dry cargo\nL - Liquid cargo\nS - Stores\nS - Stores\nA - Accommodation\nA - Accommodation\nM - Machinery\nM - Machinery\nV - Void\nV - Void\nD - Dry cargo\nD - Dry cargo\nL - Liquid cargo\nL - Liquid cargo\nair_tight\nnon_tight\noil_tight\nwater_tight\nweather_tight\nair_tight\nair_tight\nnon_tight\nnon_tight\noil_tight\noil_tight\nwater_tight\nwater_tight\nweather_tight\nweather_tight\n\n\n\nName\nDescription"}
{"Headers": "Layout Space Arrangement", "Content": "Attribute on element (SPMLSA).\nName\nDescription\nSPMPU\nPurpose code.\nDESC\nDescription.\nSPMCTY\nContent type. System defined values are:\nS - Stores\nA - Accommodation\nM - Machinery\nV - Void\nD - Dry cargo\nL - Liquid cargo\nSPMCDE\nContent description.\nSPMRFA\nRequired floor area.\nSPMRDH\nRequired deck hight.\nSPMTIC\nCompartment tightness code. System defined values are:\nair_tight\nnon_tight\noil_tight\nwater_tight\nweather_tight\nSPMTID\nCompartment tightness description.\nSPMNOC\nNoise category code. System defined values are:\nA - Intelligible speech-low noise\nB - Comfort\nC - Quiet\nD - Deafness avoidance\nE - Intelligible speech-high noise\nF - Intelligible speech-topside\nSPMNOD\nNoise category description.\nSPMTHC\nThermal insulation code.\nTPMTHD\nThermal insulation description.\nSPMACC\nAccess authorization code. System defined values are:\ncrew_only\nofficers_only\nrestricted\nunrestricted\nSPMACD\nAccess authorization description.\nSPMSAC\nSafety category code. System defined values are:\nA - safety class A\nB - safety class B\nC - safety class C\nSPMSAD\nSafety Category description.\nSPMSEC\nSecurity classification code. System defined values are:\nclassified\nsecret\nunclassified\nSPMSED\nSecurity classification description.\nSPMLSC\nSpace category.\nSPMEPC\nEstimated power consumption.\nSPMEHC\nEstimated HVAC capacity.\nSPMEWC\nEstimated weight of space contents.\nSPMCWC\nCalculated weight of space contents.\nSPMEWS\nEstimated weight of space steel structure.\nSPMCWS\nCalculated weight of space steel structure.\nSPMCOS\nCalculated center of steel structure.\nSPMEWL\nEstimated steel fillet weld length of space contents.\nSPMCWL\nCalculated steel filet weld length of space contents.\nSPMEWB\nEstimated steel butt weld length of space contents.\nSPMCWB\nCalculated steel butt weld length of space contents.\nSPMEAS\nEstimated steel paint areas of space contents.\nSPMCAS\nCalculated steel paint areas of space contents.\nSPMRSE\nRequired Services.\nTEMP\nTemperature.\nMAXTEM\nMaximum temperature.\nMINTEM\nMinimum temperature.\nHUMIDI\nDesign humidity.\nMAXHUM\nMaximum humidity.\nMINHUM\nMinimum humidity.\nPRES\nPressure.\nMAXPRE\nMaximum pressure.\nMINPRE\nMinimum pressure.\nMAXWAT\nMaximum water level.\nAIRCHA\nAir change rate.\nOCCUPA\nOccupancy.\nLIGHTI\nLighting requirements.\nMAXARE\nMaximum area.\nMINARE\nMinimum area.\nMAXVOL\nMaximum volume.\nMINVOL\nMinimum volume.\nName\nDescription\nSPMPU\nPurpose code.\nDESC\nDescription.\nSPMCTY\nContent type. System defined values are:\nSPMCDE\nContent description.\nSPMRFA\nRequired floor area.\nSPMRDH\nRequired deck hight.\nSPMTIC\nCompartment tightness code. System defined values are:\nSPMTID\nCompartment tightness description.\nSPMNOC\nNoise category code. System defined values are:\nSPMNOD\nNoise category description.\nSPMTHC\nThermal insulation code.\nTPMTHD\nThermal insulation description.\nSPMACC\nAccess authorization code. System defined values are:\nSPMACD\nAccess authorization description.\nSPMSAC\nSafety category code. System defined values are:\nSPMSAD\nSafety Category description.\nSPMSEC\nSecurity classification code. System defined values are:\nSPMSED\nSecurity classification description.\nSPMLSC\nSpace category.\nSPMEPC\nEstimated power consumption.\nSPMEHC\nEstimated HVAC capacity.\nSPMEWC\nEstimated weight of space contents.\nSPMCWC\nCalculated weight of space contents.\nSPMEWS\nEstimated weight of space steel structure.\nSPMCWS\nCalculated weight of space steel structure.\nSPMCOS\nCalculated center of steel structure.\nSPMEWL\nEstimated steel fillet weld length of space contents.\nSPMCWL\nCalculated steel filet weld length of space contents.\nSPMEWB\nEstimated steel butt weld length of space contents.\nSPMCWB\nCalculated steel butt weld length of space contents.\nSPMEAS\nEstimated steel paint areas of space contents.\nSPMCAS\nCalculated steel paint areas of space contents.\nSPMRSE\nRequired Services.\nTEMP\nTemperature.\nMAXTEM\nMaximum temperature.\nMINTEM\nMinimum temperature.\nHUMIDI\nDesign humidity.\nMAXHUM\nMaximum humidity.\nMINHUM\nMinimum humidity.\nPRES\nPressure.\nMAXPRE\nMaximum pressure.\nMINPRE\nMinimum pressure.\nMAXWAT\nMaximum water level.\nAIRCHA\nAir change rate.\nOCCUPA\nOccupancy.\nLIGHTI\nLighting requirements.\nMAXARE\nMaximum area.\nMINARE\nMinimum area.\nMAXVOL\nMaximum volume.\nMINVOL\nMinimum volume.\nAttributes on element (SPMLFA).\nName\nDescription\nSPMFCL\nInsulation code.\nName\nDescription\nSPMFCL\nInsulation code.\nAttributes on element (SPMPSA).\nName\nDescription\nFACODE\nFace code definition.\nSPMEAS\nEstimated steel paint areas of space contents.\nSPMCAS\nCalculated steel paint areas of space contents.\nName\nDescription\nFACODE\nFace code definition.\nSPMEAS\nEstimated steel paint areas of space contents.\nSPMCAS\nCalculated steel paint areas of space contents.\nAttributes on element (SPMPFA).\nName\nDescription\nFACODE\nFace code definition.\nName\nDescription\nFACODE\nFace code definition.\n\nName\nDescription\nSPMPU\nPurpose code.\nDESC\nDescription.\nSPMCTY\nContent type. System defined values are:\nS - Stores\nA - Accommodation\nM - Machinery\nV - Void\nD - Dry cargo\nL - Liquid cargo\nSPMCDE\nContent description.\nSPMRFA\nRequired floor area.\nSPMRDH\nRequired deck hight.\nSPMTIC\nCompartment tightness code. System defined values are:\nair_tight\nnon_tight\noil_tight\nwater_tight\nweather_tight\nSPMTID\nCompartment tightness description.\nSPMNOC\nNoise category code. System defined values are:\nA - Intelligible speech-low noise\nB - Comfort\nC - Quiet\nD - Deafness avoidance\nE - Intelligible speech-high noise\nF - Intelligible speech-topside\nSPMNOD\nNoise category description.\nSPMTHC\nThermal insulation code.\nTPMTHD\nThermal insulation description.\nSPMACC\nAccess authorization code. System defined values are:\ncrew_only\nofficers_only\nrestricted\nunrestricted\nSPMACD\nAccess authorization description.\nSPMSAC\nSafety category code. System defined values are:\nA - safety class A\nB - safety class B\nC - safety class C\nSPMSAD\nSafety Category description.\nSPMSEC\nSecurity classification code. System defined values are:\nclassified\nsecret\nunclassified\nSPMSED\nSecurity classification description.\nSPMLSC\nSpace category.\nSPMEPC\nEstimated power consumption.\nSPMEHC\nEstimated HVAC capacity.\nSPMEWC\nEstimated weight of space contents.\nSPMCWC\nCalculated weight of space contents.\nSPMEWS\nEstimated weight of space steel structure.\nSPMCWS\nCalculated weight of space steel structure.\nSPMCOS\nCalculated center of steel structure.\nSPMEWL\nEstimated steel fillet weld length of space contents.\nSPMCWL\nCalculated steel filet weld length of space contents.\nSPMEWB\nEstimated steel butt weld length of space contents.\nSPMCWB\nCalculated steel butt weld length of space contents.\nSPMEAS\nEstimated steel paint areas of space contents.\nSPMCAS\nCalculated steel paint areas of space contents.\nSPMRSE\nRequired Services.\nTEMP\nTemperature.\nMAXTEM\nMaximum temperature.\nMINTEM\nMinimum temperature.\nHUMIDI\nDesign humidity.\nMAXHUM\nMaximum humidity.\nMINHUM\nMinimum humidity.\nPRES\nPressure.\nMAXPRE\nMaximum pressure.\nMINPRE\nMinimum pressure.\nMAXWAT\nMaximum water level.\nAIRCHA\nAir change rate.\nOCCUPA\nOccupancy.\nLIGHTI\nLighting requirements.\nMAXARE\nMaximum area.\nMINARE\nMinimum area.\nMAXVOL\nMaximum volume.\nMINVOL\nMinimum volume.\nName\nDescription\nSPMFCL\nInsulation code.\nName\nDescription\nFACODE\nFace code definition.\nSPMEAS\nEstimated steel paint areas of space contents.\nSPMCAS\nCalculated steel paint areas of space contents.\nName\nDescription\nFACODE\nFace code definition.\nS - Stores\nA - Accommodation\nM - Machinery\nV - Void\nD - Dry cargo\nL - Liquid cargo\nS - Stores\nS - Stores\nA - Accommodation\nA - Accommodation\nM - Machinery\nM - Machinery\nV - Void\nV - Void\nD - Dry cargo\nD - Dry cargo\nL - Liquid cargo\nL - Liquid cargo\nair_tight\nnon_tight\noil_tight\nwater_tight\nweather_tight\nair_tight\nair_tight\nnon_tight\nnon_tight\noil_tight\noil_tight\nwater_tight\nwater_tight\nweather_tight\nweather_tight\nA - Intelligible speech-low noise\nB - Comfort\nC - Quiet\nD - Deafness avoidance\nE - Intelligible speech-high noise\nF - Intelligible speech-topside\nA - Intelligible speech-low noise\nA - Intelligible speech-low noise\nB - Comfort\nB - Comfort\nC - Quiet\nC - Quiet\nD - Deafness avoidance\nD - Deafness avoidance\nE - Intelligible speech-high noise\nE - Intelligible speech-high noise\nF - Intelligible speech-topside\nF - Intelligible speech-topside\ncrew_only\nofficers_only\nrestricted\nunrestricted\ncrew_only\ncrew_only\nofficers_only\nofficers_only\nrestricted\nrestricted\nunrestricted\nunrestricted\nA - safety class A\nB - safety class B\nC - safety class C\nA - safety class A\nA - safety class A\nB - safety class B\nB - safety class B\nC - safety class C\nC - safety class C\nclassified\nsecret\nunclassified\nclassified\nclassified\nsecret\nsecret\nunclassified\nunclassified\n\n\n\nName\nDescription\nName\nDescription\nName\nDescription\nName\nDescription"}
{"Headers": "Production Blocks Space Arrangement", "Content": "Attributes on element (SPMBSA).\nName\nDescription\nSPMEWS\nEstimated weight of space steel structure.\nSPMCWS\nCalculated weight of space steel structure.\nSPMCOS\nCalculated centre of steel structure.\nSPMAOF\nOffset aft.\nSPMFOF\nOffset forward.\nSPMSOF\nOffset starboard.\nSPMPOF\nOffset portside.\nSPMBOF\nOffset bottom.\nSPMTOF\nOffset top.\nSPMCOL\nColour code.\nName\nDescription\nSPMEWS\nEstimated weight of space steel structure.\nSPMCWS\nCalculated weight of space steel structure.\nSPMCOS\nCalculated centre of steel structure.\nSPMAOF\nOffset aft.\nSPMFOF\nOffset forward.\nSPMSOF\nOffset starboard.\nSPMPOF\nOffset portside.\nSPMBOF\nOffset bottom.\nSPMTOF\nOffset top.\nSPMCOL\nColour code.\n\nName\nDescription\nSPMEWS\nEstimated weight of space steel structure.\nSPMCWS\nCalculated weight of space steel structure.\nSPMCOS\nCalculated centre of steel structure.\nSPMAOF\nOffset aft.\nSPMFOF\nOffset forward.\nSPMSOF\nOffset starboard.\nSPMPOF\nOffset portside.\nSPMBOF\nOffset bottom.\nSPMTOF\nOffset top.\nSPMCOL\nColour code.\n\n\n\nName\nDescription"}
{"Headers": "Zones Space Arrangement", "Content": "Attributes on element (SPMZSA).\nName\nDescription\nSPMPU\nPurpose code.\nDESC\nDescription.\nName\nDescription\nSPMPU\nPurpose code.\nDESC\nDescription.\n\nName\nDescription\nSPMPU\nPurpose code.\nDESC\nDescription.\n\n\n\nName\nDescription"}
{"Headers": "Scantling Area Arrangement", "Content": "Attributes on element (FNCSSA)\nName\nDescription\nTGHETP\nType of tightness.\nTHICKN\nScantling thickness.\nMNSIDE\nMaterial direction. (Ship directions and positive/negative).\nMNDIRE\nStiffener direction. (Ship directions and positive/negative).\nTPLTYP\nType of profiles.\nDESP\nProfile design parameters.\nMATR\nMaterial reference.\nName\nDescription\nTGHETP\nType of tightness.\nTHICKN\nScantling thickness.\nMNSIDE\nMaterial direction. (Ship directions and positive/negative).\nMNDIRE\nStiffener direction. (Ship directions and positive/negative).\nTPLTYP\nType of profiles.\nDESP\nProfile design parameters.\nMATR\nMaterial reference.\n\nName\nDescription\nTGHETP\nType of tightness.\nTHICKN\nScantling thickness.\nMNSIDE\nMaterial direction. (Ship directions and positive/negative).\nMNDIRE\nStiffener direction. (Ship directions and positive/negative).\nTPLTYP\nType of profiles.\nDESP\nProfile design parameters.\nMATR\nMaterial reference.\n\n\n\nName\nDescription"}
{"Headers": "Opening Area Arrangement", "Content": "Attributes on element (FNCOSA).\nName\nDescription\nHOLDES\nHole designation.\nFICHOL\nFictitious hole.\nTIGHOL\nTight hole.\nCOVHOL\nCover hole.\nINSHOL\nInsert hole.\nDOUHOL\nDoubling hole.\nBEVCODE\nBevel code for hole.\nName\nDescription\nHOLDES\nHole designation.\nFICHOL\nFictitious hole.\nTIGHOL\nTight hole.\nCOVHOL\nCover hole.\nINSHOL\nInsert hole.\nDOUHOL\nDoubling hole.\nBEVCODE\nBevel code for hole.\n\nName\nDescription\nHOLDES\nHole designation.\nFICHOL\nFictitious hole.\nTIGHOL\nTight hole.\nCOVHOL\nCover hole.\nINSHOL\nInsert hole.\nDOUHOL\nDoubling hole.\nBEVCODE\nBevel code for hole.\n\n\n\nName\nDescription"}
{"Headers": "Insulation Area Arrangement", "Content": "Attributes on element (FNCISA)\nName\nDescription\nISPEC\nReference to insulation specification.\nSRFSID\nSide to apply insulation.\nSPMFCL\nInsulation code.\nName\nDescription\nISPEC\nReference to insulation specification.\nSRFSID\nSide to apply insulation.\nSPMFCL\nInsulation code.\n\nName\nDescription\nISPEC\nReference to insulation specification.\nSRFSID\nSide to apply insulation.\nSPMFCL\nInsulation code.\n\n\n\nName\nDescription"}
{"Headers": "Painting Area Arrangement", "Content": "Attributes on element (FNCPSA)\nName\nDescription\nFACODE\nFace code definition.\nSURECO\nSurface exposure code.\nName\nDescription\nFACODE\nFace code definition.\nSURECO\nSurface exposure code.\n\nName\nDescription\nFACODE\nFace code definition.\nSURECO\nSurface exposure code.\n\n\n\nName\nDescription"}
{"Headers": "Profile Trace Curve Arrangement", "Content": "Attributes on element (FNCTSA)\nName\nDescription\nTPLTYP\nType of profiles.\nTPLPAR\nProfile design parameters.\nMNDIRE\nStiffener direction. (Ship directions and positive/negative).\nMGRADE\nMaterial as text.\nMATR\nMaterial reference.\nName\nDescription\nTPLTYP\nType of profiles.\nTPLPAR\nProfile design parameters.\nMNDIRE\nStiffener direction. (Ship directions and positive/negative).\nMGRADE\nMaterial as text.\nMATR\nMaterial reference.\n\nName\nDescription\nTPLTYP\nType of profiles.\nTPLPAR\nProfile design parameters.\nMNDIRE\nStiffener direction. (Ship directions and positive/negative).\nMGRADE\nMaterial as text.\nMATR\nMaterial reference.\n\n\n\nName\nDescription"}
{"Headers": "Design Seam Curve Arrangement", "Content": "Attributes on element (FNCDBA).\nElement is currently without any functional attributes.\n\n\n"}
{"Headers": "Pseudo Attributes", "Content": "Point in Space (SPMSFP)\nSearches a space arrangement for a space where a position qualifier exists.\n\nCalled on:\nSpace layout (SPMSA).\nInput:\nPosition qualifier (Point).\nReturns:\nName of space.\nCalled on:\nSpace layout (SPMSA).\nInput:\nPosition qualifier (Point).\nReturns:\nName of space.\nSpace Bounding Box (SPMBB)\nReturns the bounding box of selected space in the form of an array of 6 real numbers which represent the minimum and maximum bounds.\n\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nThe space bounding box is returned in format:\nXmin Ymin Zmin Xmax Ymax Zmax.\nUnit is mm.\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nThe space bounding box is returned in format:\nXmin Ymin Zmin Xmax Ymax Zmax.\nUnit is mm.\nTotal Volume (SPMMVO)\nReturns the total volume of the selected space.\n\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nMoulded volume of space is returned.\nUnit is mm3.\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nMoulded volume of space is returned.\nUnit is mm3.\nCenter of Volume (SPMCOV)\nReturns the center of volume for the selected space.\n\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nThe center of volume in the format:\nX <value> Y <value> Z <value>.\nUnit is mm.\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nThe center of volume in the format:\nX <value> Y <value> Z <value>.\nUnit is mm.\nNet Volume (SPMNVO)\nReturns the net volume of the selected space compartment.\n\nCalled on:\nCompartment (SPMCSA)\nSpace (SPMSPC) If model type is compartment.\nInput:\nNone.\nReturns:\nNet volume of space is returned. Net volume is calculated as mould volume - structural allowance (SPMALL).\nUnit is mm3.\nCalled on:\nCompartment (SPMCSA)\nSpace (SPMSPC) If model type is compartment.\nInput:\nNone.\nReturns:\nNet volume of space is returned. Net volume is calculated as mould volume - structural allowance (SPMALL).\nUnit is mm3.\nFull Load Weight (SPMFLW)\nReturns the full load weight of the selected compartment.\n\nCalled on:\nCompartment (SPMCSA)\nSpace (SPMSPC) If model type is compartment.\nInput:\nNone.\nReturns:\nFull load weight of space is returned. Full load weight is calculated as net volume (SPMNVO) * permeability (SPMPER) * density (SPMDE).\nCalled on:\nCompartment (SPMCSA)\nSpace (SPMSPC) If model type is compartment.\nInput:\nNone.\nReturns:\nFull load weight of space is returned. Full load weight is calculated as net volume (SPMNVO) * permeability (SPMPER) * density (SPMDE).\nFloor Area (SPMCFA)\nReturns the floor area of the space as volume.\n\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nFloor area is returned. It is calculated as volume (SPMMVO)/ (ZMAX - ZMIN) fetched from SPMBB.\nUnit is mm2.\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nFloor area is returned. It is calculated as volume (SPMMVO)/ (ZMAX - ZMIN) fetched from SPMBB.\nUnit is mm2.\nArea of Face (SPMARA)\nReturns the area of the selected face.\n\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nThe area of the face is returned.\nUnit is mm2.\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nThe area of the face is returned.\nUnit is mm2.\nAdjoining Space (SPMAS)\nThe adjoining space pseudo attribute enables the user to find the SPMSPC element that is adjacent to the currently selected space in the hierarchy. Using a position qualifier which resides in the selected space as input, the attribute snaps a point to the closest face of the given point, and moves its location outside using the normal. Then, using the existing SPMSFT attribute, it finds the space in which the new point resides.\n\nCalled on:\nSpace (SPMSPC).\nInput:\nPosition Qualifier (Point).\nReturns:\nDBRef of adjoining space.\nCalled on:\nSpace (SPMSPC).\nInput:\nPosition Qualifier (Point).\nReturns:\nDBRef of adjoining space.\nClosest Face (SPMCF)\nThe closest face attribute works in a similar fashion to SPMAS in that it is called on a space and given a position qualifier. It works in a similar fashion to SPMAS, as if the attribute is able to successfully snap a point on the closest face to the given point, the DBRef of that face is returned.\n\nCalled on:\nSpace (SPMSPC).\nInput:\nPosition qualifier (Point).\nReturns:\nDBRef of closest face to the point.\nCalled on:\nSpace (SPMSPC).\nInput:\nPosition qualifier (Point).\nReturns:\nDBRef of closest face to the point.\nInherit Attribute Values in a Hierarchy (INHSRC)\nWhen creating a hierarchy of space arrangements, a reference to the space selected as envelope for the new space arrangement is registered using the attribute fhierarchy. This attribute is used by the inherit pseudo-attribute INHSRC which returns the element in a hierarchy where a specified attribute is set. Start point for the search is the current element (CE).\n\nCalled on:\nSpace elements (SPMCSA, SPMLSA, SPMPAS, SPMZSA, SPMGSA)\nInput:\nAttribute name.\nReturns:\nDBRef of element in hierarchy where given attribute is set.\nCalled on:\nSpace elements (SPMCSA, SPMLSA, SPMPAS, SPMZSA, SPMGSA)\nInput:\nAttribute name.\nReturns:\nDBRef of element in hierarchy where given attribute is set.\n\nCalled on:\nSpace layout (SPMSA).\nInput:\nPosition qualifier (Point).\nReturns:\nName of space.\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nThe space bounding box is returned in format:\nXmin Ymin Zmin Xmax Ymax Zmax.\nUnit is mm.\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nMoulded volume of space is returned.\nUnit is mm3.\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nThe center of volume in the format:\nX <value> Y <value> Z <value>.\nUnit is mm.\nCalled on:\nCompartment (SPMCSA)\nSpace (SPMSPC) If model type is compartment.\nInput:\nNone.\nReturns:\nNet volume of space is returned. Net volume is calculated as mould volume - structural allowance (SPMALL).\nUnit is mm3.\nCalled on:\nCompartment (SPMCSA)\nSpace (SPMSPC) If model type is compartment.\nInput:\nNone.\nReturns:\nFull load weight of space is returned. Full load weight is calculated as net volume (SPMNVO) * permeability (SPMPER) * density (SPMDE).\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nFloor area is returned. It is calculated as volume (SPMMVO)/ (ZMAX - ZMIN) fetched from SPMBB.\nUnit is mm2.\nCalled on:\nSpace (SPMSPC).\nInput:\nNone.\nReturns:\nThe area of the face is returned.\nUnit is mm2.\nCalled on:\nSpace (SPMSPC).\nInput:\nPosition Qualifier (Point).\nReturns:\nDBRef of adjoining space.\nCalled on:\nSpace (SPMSPC).\nInput:\nPosition qualifier (Point).\nReturns:\nDBRef of closest face to the point.\nCalled on:\nSpace elements (SPMCSA, SPMLSA, SPMPAS, SPMZSA, SPMGSA)\nInput:\nAttribute name.\nReturns:\nDBRef of element in hierarchy where given attribute is set.\n\n\n\nPoint in Space (SPMSFP)\nCalled on:\nInput:\nReturns:\nSpace Bounding Box (SPMBB)\nCalled on:\nInput:\nReturns:\nTotal Volume (SPMMVO)\nCalled on:\nInput:\nReturns:\nCenter of Volume (SPMCOV)\nCalled on:\nInput:\nReturns:\nNet Volume (SPMNVO)\nFull Load Weight (SPMFLW)\nFloor Area (SPMCFA)\nArea of Face (SPMARA)\nAdjoining Space (SPMAS)\nClosest Face (SPMCF)\nInherit Attribute Values in a Hierarchy (INHSRC)\nfhierarchy"}
{"Headers": "Making Calculations", "Content": "The space geometry can be used for searching and selecting elements from any discipline. The Search tool is activated (as a side pane) from the function Search in the Search group of the Home ribbon tab. The tool can be used to search exactly within the shape of a given space, using the tic box Within Shape. Once a selection of elements is available, it can be used for mass calculations.\nThe mass property functions, Volume, Area and Weight and Center of Gravity, can be found in the group Mass Properties on the Tools ribbon tab. Each of the mass property functions activates a side pane where a space can be referenced, and calculation can be defined to only calculate exactly within this given space.\nCalculation results can be stored in the Analysis database using a right-click menu on the calculation result.\n\n\n\nSearch\nSearch\nSearch\nHome\nWithin Shape\nVolume\nArea\nWeight and Center of Gravity\nMass Properties\nTools"}
{"Headers": "The Analysis Database", "Content": "The Analysis database needs to be setup in the Admin module where a database is created and read/write access is given to the Design module. Analysis data, stored in the Analysis database, is organized in packages (element GENPKG) and folders (GPKGFL), each with a filter rule that automatically sorts analysis data into the wanted package and folder, either created in advance or automatically when storing. A mass property results, calculated within a space, is stored in a package automatically created per used space and in a folder automatically created for each mass property calculation.\n\nThe stored calculation results can be reported on using the Report tool or further processes using Engineering tools.\n\n\n\nAdmin\nDesign\nReport\nEngineering"}
{"Headers": "Definition and Outcome", "Content": "A functional arrangement is created by several operations, dividing, merging, adding or subtracting. Typically, a larger volume is subdivided by surface or grid elements and then further refined by adding or subtracting of other volumetric elements.\nAll these operations (and the order of them) represent the definition data of the arrangement. The actual arrangement that is displayed in a canvas is the geometrical outcome of the definitions. A change of an arrangement is made by changing the definition or by changing the underlying elements that are referenced by the definition data. If a underlying surface, used as definition data in one or several arrangements, is changed then a new updated arrangement can be presented by a simple recreate operation.\n\n\n"}
{"Headers": "The Application Layout and Common Interaction", "Content": "The application is built up by windows in a canvas, ribbons with icon groups to access functions and modal functions docked in side panels.\n\n\n"}
{"Headers": "Ribbons", "Content": "The application contains ribbons with groups of functions organized in different tabs.\nThe main tabs when working with arrangements:\nThe Arrangement tab\ncontains all functions to generate and modify space, area and curve arrangements.\nThe Common Reference tab\ncontains all functions to generate and modify common reference elements, that means, surfaces, curves and points. Furthermore, it contains functions to simplify the grid definition for ships.\nThe Admin tab\nis used when managing data and contains general functions to support data base management. It also contains functions that allows space arrangements to be used when setting up the database structure for a project and when creating zones that are geographically bounded.\nThe Arrangement tab\ncontains all functions to generate and modify space, area and curve arrangements.\nThe Common Reference tab\ncontains all functions to generate and modify common reference elements, that means, surfaces, curves and points. Furthermore, it contains functions to simplify the grid definition for ships.\nThe Admin tab\nis used when managing data and contains general functions to support data base management. It also contains functions that allows space arrangements to be used when setting up the database structure for a project and when creating zones that are geographically bounded.\n\nThe Arrangement tab\ncontains all functions to generate and modify space, area and curve arrangements.\nThe Common Reference tab\ncontains all functions to generate and modify common reference elements, that means, surfaces, curves and points. Furthermore, it contains functions to simplify the grid definition for ships.\nThe Admin tab\nis used when managing data and contains general functions to support data base management. It also contains functions that allows space arrangements to be used when setting up the database structure for a project and when creating zones that are geographically bounded.\n\n\n\nArrangement\nCommon Reference\nAdmin"}
{"Headers": "Property Grids", "Content": "Properties on all model elements are defined in attributes and can be viewed in the attribute panel and changed using commands in the Command window. The complete set of attributes are presented in the Attribute panel; however, they are not presented in a very user-friendly way. Furthermore, changing properties using commands may be cumbersome and can lead to incorrect model elements in case wrong values are given. In the normal user case, the Property Grid panel should be used to modify and view properties. The Property Grid presents relevant property information in a format that is suitable to view and possibly change. Information is presented with enumerations in drop-down lists and validation checks is done on inserted data.\n\n\n\n\nCommand\nAttribute\nProperty Grid\nProperty Grid"}
{"Headers": "Grips and Functions", "Content": "The interaction in the canvas with the model entities is supported by displayed grips.\n\n\n"}
{"Headers": "Grips", "Content": "Double-click a CRM entity, the Everything 3D model editor grip is presented allowing for translation or rotation.\n\nDouble-click once more and the grips for modelling are presented. These grips can be used to move faces, edges and points.\n\n\n\n"}
{"Headers": "The Step-In Concept", "Content": "Double-click on arrangements (space, area or curve), and the grips are presented. One grip is presented to represent the context or location and several grips are presented for each divider.\n\nClick one of these grips and key in the in-canvas command IN, the underlying definition entity (for example envelope or dividing surface) is presented and can be adjusted if needed. Typing in-canvas OUT will remove presented entities from the canvas and recreate the arrangement to adjust for any changes made.\n\n\n\n\nIN\nOUT"}
{"Headers": "Tooltips", "Content": "Tooltips can show properties of model entities when hovering on a model entity and pressing the <Shift> key.\n\nThe contents of the tooltip can be customized using the function Tooltips in the Configure group on the Admin ribbon tab.\n\n\n\nShift\nTooltips\nConfigure\nAdmin"}
{"Headers": "Setup and Standards", "Content": "This section describes the setup and standards of Space Management.\n\n\n"}
{"Headers": "Top Level Elements", "Content": "The top element of any common reference element or arrangement is a world element, specific to the type of common reference element or type of arrangement. The top elements are:\nThe different world elements can be created using the functions under Worlds in the Create group of the General ribbon tab.\n\n\nThe specialization of arrangements, setting up the attribute collections for a specific pre-defined purpose is done by defining the type of arrangement. This is done on the world element, using the Property grid.\n\n\nSPMSW for space arrangements\nFNCAW for area arrangements\nFNCCW for curve arrangements\nSSOWLD for surfaces\nCURWLD for curves\nPNTWLD for points\nSPMSW for space arrangements\nSPMSW for space arrangements\nFNCAW for area arrangements\nFNCAW for area arrangements\nFNCCW for curve arrangements\nFNCCW for curve arrangements\nSSOWLD for surfaces\nSSOWLD for surfaces\nCURWLD for curves\nCURWLD for curves\nPNTWLD for points\nPNTWLD for points\n\n\n\nWorlds\nCreate\nGeneral\nProperty"}
{"Headers": "Setup", "Content": "The Configuration database is used to store standards such as compartment categories and noise categories. View and edit the Configuration database through the dialog below. On the ribbon go to Manage > Configure Group > Standards.\n\n\n\n\nConfiguration\n\nConfiguration\nManage > Configure Group > Standards"}
{"Headers": "Functional Overview", "Content": "This section describes the functional overview of Space Management.\n\n\n"}
{"Headers": "The Common Reference Tab", "Content": "The Common Reference tab on the ribbon contains all functions to create and modify model entities used for common references.\n\n\n\nCommon Reference"}
{"Headers": "Surface", "Content": "Creates a polyface surface. Enter the function and select positions (frame or longitudinal).\nUse the arrow-down displays options:\n\nAt enter the latest used grid planes are displayed and you are asked to select positions. The Z-axis grid positions are displayed the first time.\nAccept\nConfirms the input and creates the polyface surfaces.\nOffset\nAllows the definition of an offset value that is added to the given grid positions.\nX\nSwitches plane and allows the creation of polyface surfaces using the X-axis grid positions.\nY\nSwitches plane and allows the creation of polyface surfaces using the Y-axis grid positions.\nZ\nSwitches plane and allows the creation of polyface surfaces using the Z-axis grid positions.\nPlane\nIs used when the polyface surface shall be created at an absolute coordinate.\nLimit\nWill switch to create polyface surfaces by rectangle (using the currently used plane). Define the first and second corner of the polyface and then place it along the currently selected axis.\nPoints\nWill switch to create polyface by 3 Points. Define or Indicate 3 points then a polyface will be created from an inclined plane defined by 3 points.\nAngles\nWill switch to create a polyface by Angles. Define a Location along the one of main axis then define an angle in the other two of main axis optionally then an inclined polyface will be created with defined angles.\nAccept\nConfirms the input and creates the polyface surfaces.\nOffset\nAllows the definition of an offset value that is added to the given grid positions.\nX\nSwitches plane and allows the creation of polyface surfaces using the X-axis grid positions.\nY\nSwitches plane and allows the creation of polyface surfaces using the Y-axis grid positions.\nZ\nSwitches plane and allows the creation of polyface surfaces using the Z-axis grid positions.\nPlane\nIs used when the polyface surface shall be created at an absolute coordinate.\nLimit\nWill switch to create polyface surfaces by rectangle (using the currently used plane). Define the first and second corner of the polyface and then place it along the currently selected axis.\nPoints\nWill switch to create polyface by 3 Points. Define or Indicate 3 points then a polyface will be created from an inclined plane defined by 3 points.\nAngles\nWill switch to create a polyface by Angles. Define a Location along the one of main axis then define an angle in the other two of main axis optionally then an inclined polyface will be created with defined angles.\n\nAccept\nConfirms the input and creates the polyface surfaces.\nOffset\nAllows the definition of an offset value that is added to the given grid positions.\nX\nSwitches plane and allows the creation of polyface surfaces using the X-axis grid positions.\nY\nSwitches plane and allows the creation of polyface surfaces using the Y-axis grid positions.\nZ\nSwitches plane and allows the creation of polyface surfaces using the Z-axis grid positions.\nPlane\nIs used when the polyface surface shall be created at an absolute coordinate.\nLimit\nWill switch to create polyface surfaces by rectangle (using the currently used plane). Define the first and second corner of the polyface and then place it along the currently selected axis.\nPoints\nWill switch to create polyface by 3 Points. Define or Indicate 3 points then a polyface will be created from an inclined plane defined by 3 points.\nAngles\nWill switch to create a polyface by Angles. Define a Location along the one of main axis then define an angle in the other two of main axis optionally then an inclined polyface will be created with defined angles.\n\n\n\nAccept\nOffset\nX\nY\nZ\nPlane\nLimit\nPoints\nAngles"}
{"Headers": "Repetition Terms", "Content": "Surfaces can be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\n\n\n\n"}
{"Headers": "Curve", "Content": "Creates curves in any surface or plane. The type of curve to create is defined by using any of the sub-functions.\n\n\nSub-function\nDescription\nPlane\nCreates a curve or curves in surface or panel by intersection with plane.\nAccept the prompt to select location, surface or panel and then select the intersecting planes and also give absolute coordinates.\nRepetition Terms:\nCurves can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\nGrid Plane\nCreates a curve or curves in the grid plane by intersection with surface, grid plane or plane.\nSelect the Grid Plane and then the intersecting element.\nPoints\nCreates a knuckle or spline curve from selected points.\nPrerequisite for this function is that necessary points are created either in a point world (in CRM) or locally in another element for example in a panel.\nAccept the prompt to select points in order. By default, the function selects CRM points and creates a CRM curve. If instead a local curve is requested the mode is changed by using the drop-down function Curve at panel. Once accepted, a spline curve is created. If a polyline curve is requested, then the mode is changed by the drop-down function Polyline curve that must be selected prior to accepting the selected points.\nGeneral Cylinder\nCreates a general cylinder curve from a number of points selected in order. Select location surface and then select points in order. Choose projection direction. By default, the view direction is used. To change it key in the projection vector, or rotate the view with the scroll-button on the mouse or use the Power Compass visible in the canvas.\nOnce accepted, the general cylinder curve is projected and created as a curve in the selected surface.\nSurfaces\nCreates a curve between two intersecting surfaces or panels.\nSelect two intersecting surfaces or panels and when accepted select the intersecting surface or panel. The first element that is selected defines the location of the curve to be created.\nOffset\nCreates an offset curve from the selected curve with given offset value and direction.\nAt start of the function there is a prompt to select a curve to give an offset value (with sign to get direction). A new curve is created referencing the selected curve.\nEqual Girth\nCreates an equal girth length curve from a selected curve.\nSelect a curve created in a surface and give an offset value (with sign to get direction). A new curve is created referencing the selected curve.\nExternal Curve\nCreate a curve from a curve stored directly in a surface, for example boundary curves.\nPrior to using this function, the external curves must be made available in the canvas. Pick the surface making it current element in the database tree browser. The external curves are stored below the element SRFCGR, which should be dragged into the canvas. The external curves are made available for selection by picking the surface again and using the in-canvas command IN.\nThe external curves are now possible to pick, and the function External Curve is ready to use. To get better visualization, the shading in canvas can be turned off by using the F11 key on the keyboard.\nSelect external curves and curves are created when accepted.\nSub-function\nDescription\nPlane\nCreates a curve or curves in surface or panel by intersection with plane.\nAccept the prompt to select location, surface or panel and then select the intersecting planes and also give absolute coordinates.\nRepetition Terms:\nCurves can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\n\nGrid Plane\nCreates a curve or curves in the grid plane by intersection with surface, grid plane or plane.\nSelect the Grid Plane and then the intersecting element.\n\nPoints\nCreates a knuckle or spline curve from selected points.\nPrerequisite for this function is that necessary points are created either in a point world (in CRM) or locally in another element for example in a panel.\nAccept the prompt to select points in order. By default, the function selects CRM points and creates a CRM curve. If instead a local curve is requested the mode is changed by using the drop-down function Curve at panel. Once accepted, a spline curve is created. If a polyline curve is requested, then the mode is changed by the drop-down function Polyline curve that must be selected prior to accepting the selected points.\n\nGeneral Cylinder\nCreates a general cylinder curve from a number of points selected in order. Select location surface and then select points in order. Choose projection direction. By default, the view direction is used. To change it key in the projection vector, or rotate the view with the scroll-button on the mouse or use the Power Compass visible in the canvas.\n\n\n\nOnce accepted, the general cylinder curve is projected and created as a curve in the selected surface.\nSurfaces\nCreates a curve between two intersecting surfaces or panels.\nSelect two intersecting surfaces or panels and when accepted select the intersecting surface or panel. The first element that is selected defines the location of the curve to be created.\nOffset\nCreates an offset curve from the selected curve with given offset value and direction.\nAt start of the function there is a prompt to select a curve to give an offset value (with sign to get direction). A new curve is created referencing the selected curve.\nEqual Girth\nCreates an equal girth length curve from a selected curve.\nSelect a curve created in a surface and give an offset value (with sign to get direction). A new curve is created referencing the selected curve.\nExternal Curve\nCreate a curve from a curve stored directly in a surface, for example boundary curves.\nPrior to using this function, the external curves must be made available in the canvas. Pick the surface making it current element in the database tree browser. The external curves are stored below the element SRFCGR, which should be dragged into the canvas. The external curves are made available for selection by picking the surface again and using the in-canvas command IN.\n\nThe external curves are now possible to pick, and the function External Curve is ready to use. To get better visualization, the shading in canvas can be turned off by using the F11 key on the keyboard.\nSelect external curves and curves are created when accepted.\n\nSub-function\nDescription\nPlane\nCreates a curve or curves in surface or panel by intersection with plane.\nAccept the prompt to select location, surface or panel and then select the intersecting planes and also give absolute coordinates.\nRepetition Terms:\nCurves can also be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\nGrid Plane\nCreates a curve or curves in the grid plane by intersection with surface, grid plane or plane.\nSelect the Grid Plane and then the intersecting element.\nPoints\nCreates a knuckle or spline curve from selected points.\nPrerequisite for this function is that necessary points are created either in a point world (in CRM) or locally in another element for example in a panel.\nAccept the prompt to select points in order. By default, the function selects CRM points and creates a CRM curve. If instead a local curve is requested the mode is changed by using the drop-down function Curve at panel. Once accepted, a spline curve is created. If a polyline curve is requested, then the mode is changed by the drop-down function Polyline curve that must be selected prior to accepting the selected points.\nGeneral Cylinder\nCreates a general cylinder curve from a number of points selected in order. Select location surface and then select points in order. Choose projection direction. By default, the view direction is used. To change it key in the projection vector, or rotate the view with the scroll-button on the mouse or use the Power Compass visible in the canvas.\nOnce accepted, the general cylinder curve is projected and created as a curve in the selected surface.\nSurfaces\nCreates a curve between two intersecting surfaces or panels.\nSelect two intersecting surfaces or panels and when accepted select the intersecting surface or panel. The first element that is selected defines the location of the curve to be created.\nOffset\nCreates an offset curve from the selected curve with given offset value and direction.\nAt start of the function there is a prompt to select a curve to give an offset value (with sign to get direction). A new curve is created referencing the selected curve.\nEqual Girth\nCreates an equal girth length curve from a selected curve.\nSelect a curve created in a surface and give an offset value (with sign to get direction). A new curve is created referencing the selected curve.\nExternal Curve\nCreate a curve from a curve stored directly in a surface, for example boundary curves.\nPrior to using this function, the external curves must be made available in the canvas. Pick the surface making it current element in the database tree browser. The external curves are stored below the element SRFCGR, which should be dragged into the canvas. The external curves are made available for selection by picking the surface again and using the in-canvas command IN.\nThe external curves are now possible to pick, and the function External Curve is ready to use. To get better visualization, the shading in canvas can be turned off by using the F11 key on the keyboard.\nSelect external curves and curves are created when accepted.\n\n\n\nSub-function\nDescription\nPlane\nRepetition Terms:\nGrid Plane\nGrid Plane\nPoints\nCurve at panel\nPolyline curve\nGeneral Cylinder\nPower Compass\nSurfaces\nOffset\nEqual Girth\nExternal Curve\nIN\nExternal Curve\nF11"}
{"Headers": "Point", "Content": "Creates points in any surface, plane or curve. The type of point to create is defined by using any of the sub-functions.\n\nSub-function\nDescription\nCurve Intersection\nCreates a point or points from intersections with a curve.\nSelect a curve and then select another intersecting curve. The functions also supply options for this intersection. Use arrow-down instead of selecting the intersecting curve and the following options are available:\nSelect any of these options. This will prompt you to select any of these elements that will be used for the intersection of the selected curve and the creation of points in the intersection points.\nOn Surface or Panel\nCreate a point on a surface or a panel by a given infinite ray.\nSelect a surface (or a panel) and then a point in space. The selected surface Normal is used to define the infinite ray and the intersection point on the surface.\nDistance Along Curve\nCreates a point along a curve by distance along the curve.\nSelect a curve, a position on this curve and finally the distance along the curve (from the given point).\nSub-function\nDescription\nCurve Intersection\nCreates a point or points from intersections with a curve.\nSelect a curve and then select another intersecting curve. The functions also supply options for this intersection. Use arrow-down instead of selecting the intersecting curve and the following options are available:\n\nSelect any of these options. This will prompt you to select any of these elements that will be used for the intersection of the selected curve and the creation of points in the intersection points.\nOn Surface or Panel\nCreate a point on a surface or a panel by a given infinite ray.\nSelect a surface (or a panel) and then a point in space. The selected surface Normal is used to define the infinite ray and the intersection point on the surface.\nDistance Along Curve\nCreates a point along a curve by distance along the curve.\nSelect a curve, a position on this curve and finally the distance along the curve (from the given point).\n\nSub-function\nDescription\nCurve Intersection\nCreates a point or points from intersections with a curve.\nSelect a curve and then select another intersecting curve. The functions also supply options for this intersection. Use arrow-down instead of selecting the intersecting curve and the following options are available:\nSelect any of these options. This will prompt you to select any of these elements that will be used for the intersection of the selected curve and the creation of points in the intersection points.\nOn Surface or Panel\nCreate a point on a surface or a panel by a given infinite ray.\nSelect a surface (or a panel) and then a point in space. The selected surface Normal is used to define the infinite ray and the intersection point on the surface.\nDistance Along Curve\nCreates a point along a curve by distance along the curve.\nSelect a curve, a position on this curve and finally the distance along the curve (from the given point).\n\n\n\nSub-function\nDescription\nCurve Intersection\nOn Surface or Panel\nDistance Along Curve"}
{"Headers": "Quick Grid", "Content": "Creates a ship grid with frame and longitudinal positions\nThe window Quick Grid can be used when this function is activated. Fill in the start and end values and spacing to create the REFGRD and set the purpose of the created grid to \u2018SHIP\u2019 which identifies the main ship grid. The main ship grid is used to create model elements, for example curves and surfaces.\n\n\n\n\nQuick Grid"}
{"Headers": "Modify", "Content": "This section describes the functionality available from the Modify group.\n\n\n\n\nModify"}
{"Headers": "Editor", "Content": "Activate the Model Editor on the currently selected element (CE). The Model Editor can be used to move or rotate model elements.\n\n\n\nModel Editor\nModel Editor"}
{"Headers": "Divide", "Content": "\nSubfunction\nDescription\nPlane\nDivides a polyface surface into multiple faces by given planes.\nDefine a plane with absolute coordinates in X, Y or Z plane.\nRectangle\nDivides a polyface surface by a rectangle, creating an inner loop face.\nSelect a surface and then a face on the selected surface. The next step is to define the rectangle, within the selected face, by supplying two points.\nPolyline\nDivides a polyface surface by a polyline or by polygon.\nSelect a surface and then a face on the selected surface. The next step is to define the polyline, within the selected face, by supplying node points of the polyline. The final shape of the polyline shall divide the polyface into faces.\nSelect she Polygon and Extend options from the arrow-down options while using the Divide by Polyline function.\nPolyface\nDivides polyface surface into multiple faces by another polyface surface.\nSelect a surface and then the cutting polyface surface.\nSubfunction\nDescription\nPlane\nDivides a polyface surface into multiple faces by given planes.\nDefine a plane with absolute coordinates in X, Y or Z plane.\nRectangle\nDivides a polyface surface by a rectangle, creating an inner loop face.\nSelect a surface and then a face on the selected surface. The next step is to define the rectangle, within the selected face, by supplying two points.\nPolyline\nDivides a polyface surface by a polyline or by polygon.\nSelect a surface and then a face on the selected surface. The next step is to define the polyline, within the selected face, by supplying node points of the polyline. The final shape of the polyline shall divide the polyface into faces.\nSelect she Polygon and Extend options from the arrow-down options while using the Divide by Polyline function.\n\nPolyface\nDivides polyface surface into multiple faces by another polyface surface.\nSelect a surface and then the cutting polyface surface.\n\nSubfunction\nDescription\nPlane\nDivides a polyface surface into multiple faces by given planes.\nDefine a plane with absolute coordinates in X, Y or Z plane.\nRectangle\nDivides a polyface surface by a rectangle, creating an inner loop face.\nSelect a surface and then a face on the selected surface. The next step is to define the rectangle, within the selected face, by supplying two points.\nPolyline\nDivides a polyface surface by a polyline or by polygon.\nSelect a surface and then a face on the selected surface. The next step is to define the polyline, within the selected face, by supplying node points of the polyline. The final shape of the polyline shall divide the polyface into faces.\nSelect she Polygon and Extend options from the arrow-down options while using the Divide by Polyline function.\nPolyface\nDivides polyface surface into multiple faces by another polyface surface.\nSelect a surface and then the cutting polyface surface.\n\n\n\nSubfunction\nDescription\nPlane\nRectangle\nPolyline\nPolygon\nExtend\nDivide by Polyline\nPolyface"}
{"Headers": "Merge", "Content": "Merge two or more faces in a polyface surface.\nPick a polyface and when done the face modelling grips are displayed. You can now pick faces that should be merged together once the selection is accepted.\n\n\n"}
{"Headers": "Add Limit", "Content": "Add limits to a surface.\n\nSubfunction\nDescription\nSurface\nLimits a surface by other surfaces.\nPick surfaces that will limit the surface when selection is accepted.\nSpace\nLimits a surface by a space.\nPick a space and the space limits are then used as limiting elements when accepted.\nPrimitive\nLimits a surface by a box primitive.\nPick a box primitive. The minimum and maximum points are extracted from the primitive and are used to limit the surface once the operation has been accepted.\nSubfunction\nDescription\nSurface\nLimits a surface by other surfaces.\nPick surfaces that will limit the surface when selection is accepted.\nSpace\nLimits a surface by a space.\nPick a space and the space limits are then used as limiting elements when accepted.\nPrimitive\nLimits a surface by a box primitive.\nPick a box primitive. The minimum and maximum points are extracted from the primitive and are used to limit the surface once the operation has been accepted.\n\nSubfunction\nDescription\nSurface\nLimits a surface by other surfaces.\nPick surfaces that will limit the surface when selection is accepted.\nSpace\nLimits a surface by a space.\nPick a space and the space limits are then used as limiting elements when accepted.\nPrimitive\nLimits a surface by a box primitive.\nPick a box primitive. The minimum and maximum points are extracted from the primitive and are used to limit the surface once the operation has been accepted.\n\n\n\nSubfunction\nDescription\nSurface\nSpace\nPrimitive"}
{"Headers": "Remove Limit", "Content": "Removes limits from a limited surface.\nPick the surface where limits shall be removed. Once selected, all limiting elements are displayed. Select and accept the selection to remove the limiting elements\n\n\n"}
{"Headers": "Extend", "Content": "Extends an existing curve to by adding new segments and apply radius to create fillet curve.\n\n\n"}
{"Headers": "Tools", "Content": "Convert and import surfaces\n\n\n\n"}
{"Headers": "Recreate", "Content": "Recreates surface, curve or points.\nPick the element to be recreated. After accepting, the element is recreated using the definition data of the element.\n\n\n"}
{"Headers": "Import Surface", "Content": "Imports internal surfaces for example compartment limits from third-party software\u2019s via Surface Definition file .txt\nSurface file can be selected via Browse button and SSOWLD can be chosen from drop-down to store Surfaces.\n\nImport button will execute import operation to import surfaces and store them under the selected SSOWLD. Log windows will report accordingly.\n\n\n\n"}
{"Headers": "Convert RSO", "Content": "Converts a Reference Surface Object (RSO) into a polyface surface element (SRFSUR).\nSelect the RSO to be converted.\n\n\n"}
{"Headers": "Visibility", "Content": "\nDouble-click twice on a polyface and the model handles representing the vertexes, the edges and the faces are displayed. The functions in the visibility group can turn on or turn off these model handles.\n\nVertex\nTo display the vertex points of a polyface surface.\nEdge\nTo display the edges of a polyface surface.\nFace\nTo display the faces of a polyface surface.\nVertex\nTo display the vertex points of a polyface surface.\nEdge\nTo display the edges of a polyface surface.\nFace\nTo display the faces of a polyface surface.\n\nVertex\nTo display the vertex points of a polyface surface.\nEdge\nTo display the edges of a polyface surface.\nFace\nTo display the faces of a polyface surface.\n\n\n\nVertex\nEdge\nFace"}
{"Headers": "Advanced Modelling", "Content": "\nAdvanced modelling functions for polyface surface modelling. Mirror plane can be activated to create and modify polyface surface symmetrically. Mirror plane can be defined on X, Y, Z axis. X, Y, Z axis can be shifted from 0 to desired location by keying in the translation value. Mirror plane can be defined between two points as well.\n\n\n"}
{"Headers": "The Arrangements Tab", "Content": "The Arrangements tab on the ribbon contains all functions to create and modify model entities used for functional arrangements.\n\n\n\nArrangements"}
{"Headers": "Create", "Content": "Creates space, area and curve arrangements\n\n\n\n"}
{"Headers": "Space Arrangement", "Content": "Creates space arrangements.\n\nSubfunction\nDescription\nSurfaces\nCreates space arrangements from surfaces which forms a closed volume. Pick and select surfaces in the canvas and then confirm. Either click Enter or A. Another option is to use the arrow-down key that will present the Accept option in the canvas.\nPrimitives\nCreates space arrangements from primitives. Pick volume primitives in the canvas and accept when ready.\nSub-arrangement\nCreates space arrangement from an existing space as sub- arrangement. Pick a space in the canvas and accept when ready. The new arrangement will use the picked space as its envelope and as entry level in the new hierarchy.\nTable\nCreates space arrangements from table input. The function is further explained below\nSubfunction\nDescription\nSurfaces\nCreates space arrangements from surfaces which forms a closed volume. Pick and select surfaces in the canvas and then confirm. Either click Enter or A. Another option is to use the arrow-down key that will present the Accept option in the canvas.\nPrimitives\nCreates space arrangements from primitives. Pick volume primitives in the canvas and accept when ready.\nSub-arrangement\nCreates space arrangement from an existing space as sub- arrangement. Pick a space in the canvas and accept when ready. The new arrangement will use the picked space as its envelope and as entry level in the new hierarchy.\nTable\nCreates space arrangements from table input. The function is further explained below\nThe purpose of the Table function is to easily create a standardised space arrangement with or without a hierarchy of spaces.\nYou are expected to add space limits (the boundary limits of the space arrangement) and dividers into the form grid. If a space hierarchy is requested the dividers must be specified in levels and the tick box SpacesWithHierarchy must be ticked.\nThe space limits and dividers can be given as surfaces. Furthermore, the dividers can be given as grid positions and absolute coordinates.\nOnce the form grid is filled in it can be saved into an .xslx file and read at a later time if needed. When input data is ready the space arrangement can be created using the function Create Spaces, however, the destination space world (SPMSW) needs first to be made current element (CE).\n\nSubfunction\nDescription\nSurfaces\nCreates space arrangements from surfaces which forms a closed volume. Pick and select surfaces in the canvas and then confirm. Either click Enter or A. Another option is to use the arrow-down key that will present the Accept option in the canvas.\nPrimitives\nCreates space arrangements from primitives. Pick volume primitives in the canvas and accept when ready.\nSub-arrangement\nCreates space arrangement from an existing space as sub- arrangement. Pick a space in the canvas and accept when ready. The new arrangement will use the picked space as its envelope and as entry level in the new hierarchy.\nTable\nCreates space arrangements from table input. The function is further explained below\n\n\n\nSubfunction\nDescription\nSurfaces\nEnter\nA\nAccept\nPrimitives\nSub-arrangement\nTable\nTable\nSpacesWithHierarchy\nCreate Spaces"}
{"Headers": "Area Arrangement", "Content": "Creates an area arrangement from a surface.\nSelect a surface on which the area arrangement shall be based upon.\nClick Enter or A or use the arrow-down key to confirm the selection and accept the selected element:\n\n\n\n\nEnter\nA"}
{"Headers": "Curve Arrangement", "Content": "Creates a curve arrangement from a curve.\nSelect a curve on which the curve arrangement shall be based upon. To confirm the selection click Enter or A or use the arrow-down key to accept the selected element:\n\n\n\n\nEnter\nA"}
{"Headers": "Transversal Bulkhead", "Content": "Creates area arrangements of type scantling together with the underlying transversal polyface surfaces.\nIn this function, give frame positions:\n\nOption\nDescription\nAccept\nwill confirm the given position creation of polyface surface or polyface surfaces.\nOffset\nwill switch mode to define offset value from selected grid position.\nOption\nDescription\nAccept\nwill confirm the given position creation of polyface surface or polyface surfaces.\nOffset\nwill switch mode to define offset value from selected grid position.\nAfter accepting the position of bulkhead, the user will be asked to select surfaces or areas to limit the bulkheads and accept when ready.\nThe created area arrangement is of type scantling and will be stored in the first area world (FNCAW) of this type and the surface is created in the first surface world (SSOWLD).\nOption\nDescription\nAccept\nwill confirm the given position creation of polyface surface or polyface surfaces.\nOffset\nwill switch mode to define offset value from selected grid position.\n\n\n\nOption\nDescription\nAccept\nOffset"}
{"Headers": "Repetition Terms", "Content": "Surfaces can be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\n\n\n\n"}
{"Headers": "Longitudinal Bulkhead", "Content": "Creates area arrangements of type scantling together with the underlying transversal polyface surfaces.\nEnter the function and give the longitudinal positions:\n\nAfter accepting the position of the bulkhead select surfaces or areas to limit the bulkheads and accept when ready.\nThe created area arrangement is of type scantling and will be stored in the first area world (FNCAW) of this type and the surface is created in the first surface world (SSOWLD).\n\n\n"}
{"Headers": "Repetition Terms", "Content": "Surfaces can be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\n\n\n\n"}
{"Headers": "Deck", "Content": "Creates area arrangements of type scantling together with the underlying transversal polyface surfaces.\nEnter the function and give the longitudinal positions (Z coordinates):\n\nAfter accepting the position of decks, select surfaces or areas to limit the decks and accept when ready.\nThe created area arrangement is of type scantling and will be stored in the first area world (FNCAW) of this type and the surface is created in the first surface world (SSOWLD).\n\n\n"}
{"Headers": "Repetition Terms", "Content": "Surfaces can be created using repetition terms. Syntax for repetition is <start> <step> <end> <optional offset> as illustrated below:\n\n\n\n"}
{"Headers": "Add", "Content": "Adds a primitive or a space (from another space arrangement) to a selected space arrangement. The Add operation is explained in the Basic Concepts chapter of this user guide.\nEnter the function and select the space arrangement to which additions shall be made.\nSelect a primitive or a space (from another arrangement) to add to the selected space arrangement.\n\n\n\nBasic Concepts\nAdd\nBasic Concepts\n"}
{"Headers": "Subtract", "Content": "Subtracts a primitive or a space (from another space arrangement) to a selected space arrangement. The Subtract function is explained in the Basic Concepts chapter of this user guide.\nEnter the function and then select the space arrangement to which subtractions shall be made.\nThen select a primitive or a space (from another arrangement) to subtract from the selected space arrangement.\n\n\n\nBasic Concepts\nSubtract\nBasic Concepts"}
{"Headers": "Divide", "Content": "This section describes the functionality available from the divide right-click menu.\n\nSubfunction\nDescription\nSurface\nDivides functional arrangements with surfaces.\nSelect arrangements and when accepted also select dividing surfaces (possibly with an additional offset). When accepted, the arrangement is recreated using the new dividers and an updated arrangement is presented.\nPlane\nDivides functional arrangements with grid planes or absolute coordinates.\nSelect arrangements and when accepted also select dividing grid planes (possibly with an additional offset) or give absolute coordinates to define planes. When accepted, the arrangement is recreated using the new dividers and an updated arrangement is presented.\nCurve\nDivides functional curve or area arrangements with curves.\nSelect arrangements and when accepted also select dividing curves (possibly with an additional offset). When accepted, the arrangement is recreated using the new dividers and an updated arrangement is presented.\nAdd Dividers from Space Arrangement\nDivides a functional area arrangement with the dividers used in a selected space Arrangements.\nSelect the space arrangements and when accepted also select the area arrangement that shall be updated with the dividers extracted from the space arrangement. The area arrangement is recreated using the new dividers and an updated arrangement is presented.\nSubfunction\nDescription\nSurface\nDivides functional arrangements with surfaces.\nSelect arrangements and when accepted also select dividing surfaces (possibly with an additional offset). When accepted, the arrangement is recreated using the new dividers and an updated arrangement is presented.\nPlane\nDivides functional arrangements with grid planes or absolute coordinates.\nSelect arrangements and when accepted also select dividing grid planes (possibly with an additional offset) or give absolute coordinates to define planes. When accepted, the arrangement is recreated using the new dividers and an updated arrangement is presented.\nCurve\nDivides functional curve or area arrangements with curves.\nSelect arrangements and when accepted also select dividing curves (possibly with an additional offset). When accepted, the arrangement is recreated using the new dividers and an updated arrangement is presented.\nAdd Dividers from Space Arrangement\nDivides a functional area arrangement with the dividers used in a selected space Arrangements.\nSelect the space arrangements and when accepted also select the area arrangement that shall be updated with the dividers extracted from the space arrangement. The area arrangement is recreated using the new dividers and an updated arrangement is presented.\n\nSubfunction\nDescription\nSurface\nDivides functional arrangements with surfaces.\nSelect arrangements and when accepted also select dividing surfaces (possibly with an additional offset). When accepted, the arrangement is recreated using the new dividers and an updated arrangement is presented.\nPlane\nDivides functional arrangements with grid planes or absolute coordinates.\nSelect arrangements and when accepted also select dividing grid planes (possibly with an additional offset) or give absolute coordinates to define planes. When accepted, the arrangement is recreated using the new dividers and an updated arrangement is presented.\nCurve\nDivides functional curve or area arrangements with curves.\nSelect arrangements and when accepted also select dividing curves (possibly with an additional offset). When accepted, the arrangement is recreated using the new dividers and an updated arrangement is presented.\nAdd Dividers from Space Arrangement\nDivides a functional area arrangement with the dividers used in a selected space Arrangements.\nSelect the space arrangements and when accepted also select the area arrangement that shall be updated with the dividers extracted from the space arrangement. The area arrangement is recreated using the new dividers and an updated arrangement is presented.\n\n\n\nSubfunction\nDescription\nSurface\nPlane\nCurve\nAdd Dividers from Space Arrangement"}
{"Headers": "Replace Divider", "Content": "Replaces a divider of a functional arrangement with another divider.\nSelect an arrangement. The dividers are displayed in the canvas and then select a divider to be replaced. If the divider to be replaced is a plane divider you can move the divider with an offset or use one of the options:\n\nGrid Plane\nthis option will display the grid positions along the original axis of the divider to be replaced. It is not possible to select a new axis.\nCRM Object\nwill make it possible to select a CRM object (Curve or Surface).\nGrid Plane\nthis option will display the grid positions along the original axis of the divider to be replaced. It is not possible to select a new axis.\nCRM Object\nwill make it possible to select a CRM object (Curve or Surface).\nIf the divider to replace is a CRM object (surface or curve) there are no options, the new divider must also be a CRM object. If it is necessary to replace a plane CRM divider with a Plane divider this must be done in two steps with the Remove Divider and the Divide functions.\nGrid Plane\nthis option will display the grid positions along the original axis of the divider to be replaced. It is not possible to select a new axis.\nCRM Object\nwill make it possible to select a CRM object (Curve or Surface).\n\n\n\nGrid Plane\nCRM Object\nCRM\nRemove Divider\nDivide"}
{"Headers": "Remove Divider", "Content": "Removes a divider of a functional arrangement.\nSelect an arrangement. The dividers are displayed in canvas. Then select dividers to be removed from the arrangement.\n\n\n"}
{"Headers": "Merge", "Content": "Merges two or more spaces, areas or curve branches into one.\nSelect a curve branch, an area or a space to merge. Then select the functional elements of the same type and the merge is done when accepted.\n\n\n"}
{"Headers": "Name Spaces", "Content": "Name spaces in a space arrangement.\n\nThe renaming of spaces can be done on a full arrangement or on individual spaces. The names are using the following syntax:\nName = <prefix><running number><suffix>.\nA window is displayed with the possibility to define prefix and a suffix together with a starting number. A space or a space arrangement is made current element and the GetName function within the window is used to get the name into the window.\nNote: The Arrangement tick box must be ticked if renaming an arrangement.\n\n\n\nGetName\nNote\n:\nArrangement"}
{"Headers": "Recreate", "Content": "Recreates functional arrangements or common reference elements.\nSelect the element to be recreated. The selected element is recreated, adapting to the surrounding elements according its definition stored with the definition data.\n\n\n"}
{"Headers": "The Admin Tab", "Content": "The Arrangements tab on the ribbon contains all functions to create and modify model entities used for functional arrangements.\n\n\n\n\nArrangements"}
{"Headers": "Database Structure", "Content": "Creates the database structure for admin.\nPrerequisite for this function is a created space arrangement with spaces that represent the geographical distribution of databases intended for the project (that is one database per site and zone). All spaces must have names to be accepted for this purpose.\nWhen the function is activated a form is displayed. Make the space arrangement (SPMSA) the current element in the database tree browser and use the Get Spaces function available in the form. The form grid is then filled with the space arrangement data.\n\nOwning team and database numbers needs to be manually filled in, either using this window or after the data is exported (to an .xlsx file). When updated, the databases can be created in admin using the Import function available in the Utilities dropdown list.\n\n\n\nGet Spaces\nImport\nUtilities"}
{"Headers": "Zones", "Content": "Creates zones from space arrangement. This function has two different workflows.\nThe first scenario is that the database structure is created using the function Database Structure. The following steps must then be performed to create a site and a zone in each created database:\nThe second scenario of this function is to create zones within a specified database.\nThe following steps should be performed to create a site and a Zone in each created database:\n\nIn both scenarios the zones will be linked to the corresponding space by the Spcref attribute in zone which can be used as default boundary by applications adding elements into the zones.\n\n\n\nDatabase Structure\nSite per Database\nGet Arrangement\nOverview\nCreate\nZone\nSite per Database\nGet Site\nGet Arrangement\nOverview\nCreate\nSpcref"}
{"Headers": "Commands", "Content": "Below are listed the commands that operate on arrangements and reference elements. These can be useful in case only definition data exists and you need the geometry outcome to be generated.\nCommand Name\nDescription\nRCRPFA\nRecreate polyface.\nRCRSUI\nRecreate surface instance.\nRCRCUR\nRecreate curve.\nRCRPNT\nRecreate point.\nRCRENV\nRecreate envelope.\nRCRSPA\nRecreate space, area or curve arrangement.\nCommand Name\nDescription\nRCRPFA\nRecreate polyface.\nRCRSUI\nRecreate surface instance.\nRCRCUR\nRecreate curve.\nRCRPNT\nRecreate point.\nRCRENV\nRecreate envelope.\nRCRSPA\nRecreate space, area or curve arrangement.\n\nCommand Name\nDescription\nRCRPFA\nRecreate polyface.\nRCRSUI\nRecreate surface instance.\nRCRCUR\nRecreate curve.\nRCRPNT\nRecreate point.\nRCRENV\nRecreate envelope.\nRCRSPA\nRecreate space, area or curve arrangement.\n\n\n\nCommand Name\nDescription"}
{"Headers": "Appendices", "Content": "These appendices describe the available functionality for extract sample points and creating sample points.\n\n\n"}
{"Headers": "Extract Sample Points from a Surface, Overview", "Content": "The software described in this appendix is not included in the standard installation of TRIBON M3SP6, but can be made available by contacting local support.\nThis tool is implemented by the program sj708. This program creates a number of sample points from a surface by using the surface server to intersect a native surface or a NAPA surface. The points are extracted by cutting sections and waterlines and fitting a bi-arc curve to the curves cut, from the bi-arc curves the start and end positions of the bi arcs are used as sample points.\nThe file with the sample points can then be used as an input file to the Compare Surface function in AVEVA Everything3D Surface Manager to check that the surface has not been altered in moving it from TRIBON M3 environment to AVEVA Everything3D as a native surface.\n\n\n\nCompare Surface"}
{"Headers": "Creating Sample Points", "Content": "The tool is invoked by executing the program sj708 from a command prompt and then supplying the following information:\nThe fitting of bi-arcs are using the default tolerance for surface intersections, normally set to 0.5 mm.\nThe sample file below shows an example of a file created by the tool:\nSPHULL Surface name\n0.500 Intersection tolerance\n1 Plane x=1, y=2, z=3\n-3997.767 Plane coordinate\n1 Number of contours resulting from cut\n23 Number of sample points in contour\n-3997.767 0.404 9156.768 List of the sample points.\n-3997.767 0.404 9156.768\n-3997.767 464.703 9156.658\n-3997.767 929.001 9156.630\n-3997.767 1590.540 9156.431\n-3997.767 2252.079 9156.343\n-3997.767 2252.079 9156.343\n-3997.767 2644.825 9161.745\n-3997.767 3036.728 9186.652\n-3997.767 3469.494 9243.603\n-3997.767 3895.013 9339.537\n-3997.767 4338.791 9494.317\n-3997.767 4760.698 9701.479\n-3997.767 5121.943 9931.359\n-3997.767 5462.478 10191.395\n-3997.767 5691.602 10387.466\n-3997.767 5913.806 10591.396\n-3997.767 6293.704 10963.010\n-3997.767 6661.336 11346.797\n-3997.767 6962.589 11679.026\n-3997.767 7255.592 12018.557\n-3997.767 7508.713 12325.050\n-3997.767 7756.785 12635.654\nFull path and filename for the output file\nPath to the folder containing the surface files, dml or dms. ( Not prompted if a project is selected with SB_NAVARCH set or for projects using a NAPA surface)\nName of the surface\nLimits for the sections and waterlines, AFT, FWD, lower and upper\nDistance between cuts\nFull path and filename for the output file\nFull path and filename for the output file\nPath to the folder containing the surface files, dml or dms. ( Not prompted if a project is selected with SB_NAVARCH set or for projects using a NAPA surface)\nPath to the folder containing the surface files, dml or dms. ( Not prompted if a project is selected with SB_NAVARCH set or for projects using a NAPA surface)\nName of the surface\nName of the surface\nLimits for the sections and waterlines, AFT, FWD, lower and upper\nLimits for the sections and waterlines, AFT, FWD, lower and upper\nDistance between cuts\nDistance between cuts\n\n\n"}
{"Headers": "Interface Components", "Content": "When Surface Manager is started, an application window that is composed of various window elements is shown.\n\n\n\n"}
{"Headers": "Application Frame", "Content": "The application frame groups all other application windows into a single integrated unit. All windows can be moved around and arranged freely within the application frame.\n\n\n"}
{"Headers": "Graphics Window", "Content": "The graphics window is used to present the contents of the current scene. The navigation tools, that are included in the toolbar to the right, can be used to manipulate the viewed models in the window.\n\nWhen a BREP model is presented in the graphics window, the internal structure of the model is also shown. Faces are drawn as shaded surfaces and the bounding edges as yellow or blue lines. Edges that bounds exactly two faces are coloured yellow and the remaining edges are coloured blue. A blue edge inside a surface indicates that the bounded faces are unconnected. The most common reason for this is that the faces are unconnected in the file they are coming from or that the gaps between the faces are too big. Unconnected edges can be sewed together, either by just connecting then if the gaps are small or by slightly increasing the internal tolerance and then connecting them. Small black symbols are used to show the position of the vertices.\n\n\n"}
{"Headers": "Workspace Explorer", "Content": "The workspace explorer window includes two tabbed tree views that are used to explorer scenes and imported models. This window is by default docked to the left side of the application frame.\n\n\n"}
{"Headers": "Model View", "Content": "The model view is the basic tool to examine imported models and also the structure of these models. Models can be added to the current scene, and thereby presented in the graphic window, by selecting, and then dragging them to the graphics window. Functions can also be invoked from this view by right-clicking on a node and then selecting an appropriate function from the appearing pop-up menu.\n\nThe model tree is divided into two main areas, Hull Surfaces and Primitive Assemblies. Both areas can be used in a similar way, but the Hull Surfaces area is most suited to be used for surfaces to be released to a design project and the Primitive Assemblies area for more general models. The assembly tree structure is flattened out when models are imported to the Hull Surfaces area, but retained when the same model is imported to the Primitive Assemblies area.\n\n\n"}
{"Headers": "Scenes View", "Content": "The scenes view is used to explore created scenes and the model drops that are included in each scene. Context sensitive menus are available to create, make current, delete or change the properties of a scene.\n\n\n"}
{"Headers": "Message Window", "Content": "The message window is docked at the bottom of the application frame and used to present output from the execution of tools. Error or informational messages are also written to this window.\n\n\n"}
{"Headers": "Auxiliary Model View", "Content": "An auxiliary model tree window function has been made available in order to give the user the possibility to split the ordinary model tree anywhere in the tree structure.\nThis tool is particularly useful when checking the details in one tree and still having the overview in another tree.\n\n\n"}
{"Headers": "Surface Manager", "Content": "Sculptured surfaces are important objects used to represent geometrically complicated areas. The shell surface is an obvious such area as well as bow thruster tunnels and anchor tubes, but there are many others especially in more complicated ships.\nAVEVA Everything3D operates on sculptured surfaces by performing mathematical operation such as intersections and to generate volumes. All these type of operations need sculptured surfaces that are topologically correct in order to give correct results in design and production. The Surface Manager provides the tools to import, check, verify and in some cases also repair surfaces independently of their origin. If surfaces are created with tools outside AVEVA Marine Initial Design, the import can be made using standard formats.\nA shell surface of a ship may contain details that the shipyard wants to keep as their property and not share with for example, a subcontractor. The Surface Manager contains the necessary tools to share only the relevant part of the surface in these cases.\nMany external surface systems generate surfaces with many patches also in flat areas. This is affecting the performance of operations on the surface, for example, when intersecting the surface. The Surface Manager contains the tools to combine patches in flat areas, reducing the number of surfaces and by this increasing the overall performance in design and production.\n\n\n\n\n\n\n\n"}
{"Headers": "Keyboard Shortcuts", "Content": "Tools are normally selected by clicking on an button or selecting an item from a menu, but some of the tools can also be selected or invoked by using keyboard shortcuts. The table below lists the available keyboard shortcuts.\nFunctions\nShortcut Keys\nAuto Scale\nCtrl+A\nZoom to Model tool\nCtrl+B\nRestore Camera\nCtrl+E\nZoom Window tool\nCtrl+I\nWalk tool\nCtrl+M\nSpin tool\nCtrl+R\nSave Camera\nCtrl+S\nSlide tool\nCtrl+T\nMake next window current\nF6\nMake previous window current\nShift+F6\nToggle between full screen and normal mode\nF11\nFunctions\nShortcut Keys\nAuto Scale\nCtrl+A\nZoom to Model tool\nCtrl+B\nRestore Camera\nCtrl+E\nZoom Window tool\nCtrl+I\nWalk tool\nCtrl+M\nSpin tool\nCtrl+R\nSave Camera\nCtrl+S\nSlide tool\nCtrl+T\nMake next window current\nF6\nMake previous window current\nShift+F6\nToggle between full screen and normal mode\nF11\n\nFunctions\nShortcut Keys\nAuto Scale\nCtrl+A\nZoom to Model tool\nCtrl+B\nRestore Camera\nCtrl+E\nZoom Window tool\nCtrl+I\nWalk tool\nCtrl+M\nSpin tool\nCtrl+R\nSave Camera\nCtrl+S\nSlide tool\nCtrl+T\nMake next window current\nF6\nMake previous window current\nShift+F6\nToggle between full screen and normal mode\nF11\n\n\n\nFunctions\nShortcut Keys"}
{"Headers": "Overview", "Content": "Surface Manager is a tool that has primarily been designed to simplify the handling of surfaces in marine projects, but it could also be an excellent tool in other disciplines.\nAlmost all kinds of complex geometries can be handled, because models are internally represented by a very flexible and powerful boundary representation or \u2018Brep\u2019 model. The geometries are defined by a set of trimmed NURBS surfaces that are connected together through their boundaries.\nImproperly defined models are always a major problem when complex shapes should be transferred between different design systems. It could be small needle faces, degenerated faces, too big gaps etcetera that make an imported model unsuitable for further modelling. It's therefore essential to detect and if possible correct these types of defects to eliminate or at least minimize the risk for later failures in the modelling tools.\nTransfer of models have been made as seamless as possible, by including tools to, import and export, functions to visualize and inspect, and also functions to heal and optimize imported models.\nThis user guide describes concepts and functions that are currently implemented in this product.\n\n\n"}
{"Headers": "Tools and Functions", "Content": "The following sections will give the user some guidance through the various tools and their functionality.\n\n\n"}
{"Headers": "Workspaces", "Content": "During a session, models can be imported and new scenes can be created. A collection of these elements are called a workspace. A saved workspace can be seen as a snap shot of the current session.\n\n\n\nworkspace"}
{"Headers": "New Workspace", "Content": "A new workspace is created by clicking the New button in the workspace toolbar or by selecting the menu item File > New.\n\n\n\nNew\nFile > New"}
{"Headers": "Open Workspace", "Content": "A workspace that has been previously saved can be restored by clicking the Open Workspace button or by selecting the menu item File > Open Workspace. The current workspace is closed and a new is created with the contents of the opened workspace.\n\n\n\nOpen Workspace\nFile > Open Workspace"}
{"Headers": "Save Workspace", "Content": "A workspace can be saved by clicking on the Save Workspace button in the workspace toolbar or by selecting the menu item File > Save Workspace. The workspace is saved in a file named <workspace name>.tbw.\n\n\n\nSave Workspace\nFile > Save Workspace\n<workspace name>.tbw"}
{"Headers": "Scenes", "Content": "A scene contains a certain collection of model objects displayed in a specific way according to the user's choice regarding rotation, angle, perspective viewpoint . One of the scenes is always current, and this is the scene that is visible in the graphics window.\nThere are two predefined scenes and they have different configurations.\nBrowse0\nConfigured as a browse scene. All models are removed from the scene before new models are added.\nNormal0\nConfigured as a normal scene.\nBrowse0\nConfigured as a browse scene. All models are removed from the scene before new models are added.\nNormal0\nConfigured as a normal scene.\n\nBrowse0\nConfigured as a browse scene. All models are removed from the scene before new models are added.\nNormal0\nConfigured as a normal scene.\n\n\n\nBrowse0\nNormal0"}
{"Headers": "Scene Properties", "Content": "The scene properties are collected into a number of property pages and displayed by the property command for a scene. One exception is the box filter that is implemented by a separate command and dialog box.\n\n\n"}
{"Headers": "Model Type Filter", "Content": "Use the model type filter to restrict the presentation to certain model types. Be aware that it is necessary to select the parent model to be able to present child models. The model type filter settings can be found in the Type Filter property page.\n\n\n"}
{"Headers": "Scene Templates", "Content": "A simple way to create a scene with complex properties is to use a customized scene template. Such a template is easily created by saving an existing scene as a scene template. Every scene is based on a scene template. Two predefined scene templates are always available. A scene template contains basic scene properties such as scene type, presentation options, filter setting . Other scene properties of more temporary nature are not included in the scene template, such as model selections, the restriction box, saved camera positions .\nThe default location for saving or loading scene templates depends on the used operating system.\nWindows XP:\n[Drive]:\\Document and Settings\\<user>\\Application Data\\AVEVA\\SurfaceManager\\SceneTemplates.dat\nWindows Vista and Windows 7\n[Drive]:\\Users\\<user>\\AppData\\Roaming\\AVEVA\\SurfaceManager\\SceneTemplates.dat\nWindows XP:\n[Drive]:\\Document and Settings\\<user>\\Application Data\\AVEVA\\SurfaceManager\\SceneTemplates.dat\nWindows XP:\nWindows Vista and Windows 7\n[Drive]:\\Users\\<user>\\AppData\\Roaming\\AVEVA\\SurfaceManager\\SceneTemplates.dat\nWindows Vista and Windows 7\n\n\n\n[Drive]:\\Document and Settings\\<user>\\Application Data\\AVEVA\\SurfaceManager\\SceneTemplates.dat\n[Drive]:\\Users\\<user>\\AppData\\Roaming\\AVEVA\\SurfaceManager\\SceneTemplates.dat"}
{"Headers": "Scene Tools", "Content": "The most common scene tools are collected in the scene toolbar and the rest of the commands can be found in context sensitive menus.\nNew Scene\nThis is a quick way to create a scene that is based on the default scene template. Use the New command from the pop-up menu for Scenes to create a scene that is based on another template.\nPrevious Scene\nMake the previous scene current and visible in the graphics window.\nNext Scene\nMake the next scene current and visible in the graphics window.\nBox Selection Filter\nDefines a selection box that filters added model, only models inside or partly inside the box are added to the scene.\nSave as Scene Template\nUse the command Save as Scene Template from the right-click menu for a scene to create a customized scene template from the indicated scene. A dialog appears that allows the specification of name and description of the template. Click OK to create the template.\n\n\n\nNew Scene\nNew\nScenes\nPrevious Scene\nNext Scene\nBox Selection Filter\nSave as Scene Template\nSave as Scene Template\nOK"}
{"Headers": "Displaying Models", "Content": "The current scene is populated and thereby displayed by dragging one or several items from the model tree to the graphics window. Models are normally added primitive by primitive, but it is also possible to add a model face by face to enable the section of individual faces. This is done by dragging a faces node of a primitive instead of a higher level node.\n\n\n"}
{"Headers": "Rendering Options", "Content": "The rendering options can be reached from the menu Tools > Options\u2026\n\n\n\n\nTools > Options\u2026"}
{"Headers": "Rendering Styles", "Content": "Outline\nWith this option enabled all bounding edges of the faces in a BREP model are drawn. Edges between faces are coloured yellow, the remaining ones blue.\n\nWireframe\nWith this option enabled all lines of the facetted BREP models are drawn without shading.\n\nSmooth shading\nThis is the default rendering style. With this option enabled all faces in the BREP model are drawn as shaded surfaces.\n\n\n\n\nOutline\nWireframe\nSmooth shading"}
{"Headers": "Brep Rendering Options", "Content": "Show control points\nWith this option enabled the control points/control polygon of each face in the BREP model are drawn.\n\nShow normals\nWith this option enabled the normal of each face in the BREP model is drawn.\n\nThe direction of the normals can be changed by the command Flip Normal from the popup menu:\n\n\n\n\nShow control points\nShow normals\nFlip Normal"}
{"Headers": "Rendering Tolerance", "Content": "The default is 10 mm. The rendering tolerance determines how detailed the BREP model is facetted and drawn. The smaller the tolerance the smoother the shading will be with the drawing time increasing as well.\n\n\n"}
{"Headers": "Navigation Functions", "Content": "Navigation functions are used to change the view of the model items that is presented in the graphics window. All the tools are collected in a toolbar that is by default docked at the right side of the application frame. A tool is selected or invoked by clicking on one of the buttons in the toolbar. When a new tool is selected, the cursor will alter to the symbolic shape of the tool. A selected tool is current until another tool is selected. A move in the graphics window is initiated by selecting one of the move tools and then pressing the left mouse button and moving the mouse in an appropriate direction. The resulting movement is different for each individual tool. But, common for all move tools are that the direction and speed are determined by the distance between the button down position and the current cursor position. The movement is stopped when the mouse button is released.\nIndependent of the selected tool it is always possible to use the mouse wheel to zoom in-and out in the graphics window.\nSelect Tool\nThe select tool is used to select models in the graphics window. A model is selected by a single click on a model or by pressing the left mouse button and then dragging to make a rectangle select. Models can be added to the current selection by holding down the CTRL-key during the selection. Selection feedback is provided by highlighting the selected models.\nAuto Scale\nThe auto scale function scales the models to fit the graphics window. The current tool is not changed by this function.\nZoom Window\nThe zoom window tool defines a rectangular area of the displayed model to be visible in the graphics window. The zoom is initiated by pressing the right mouse button in the graphics window and then dragging until the requested area is covered by the rectangle. The zoom is preformed when the mouse button is released.\nZoom and Pan\nThe zoom and pan tool performs dynamic zooming or panning in the graphics window. Press the left mouse button and then move the cursor in the requested direction to either zoom or pan. Move the cursor up or down to zoom and sideways to pan.\nSlide\nSlide the model in the graphics window. Press and then move the cursor in the direction the model should be moved.\nSpin\nSpin the model around any axis. Press the mouse button and then move the cursor in different directions in order to rotate around different axis. The rotation centre is defined by the closest point on the model, under the cursor, when the rotation is initiated.\nWalk\nTool to walk around in the displayed model. Press the mouse button and then move upwards to move forward in the model and downwards to move backwards. Move the mouse to the left to walk to the left and move the mouse to the right to walk to the right. It's also possible to move the observer to a certain point by pressing the mouse key while holding down the CTRL-key. The observer is moved to the new position and positioned along the positive z-axis. This tool only works together with perspective camera.\nTilt\nTool to tilt the displayed model. Press the left mouse button and move the mouse to the left to rotate the displayed model clockwise or move the mouse to the right to rotate counter clockwise, around the view centre point.\nRestore Camera\nRestore previously saved camera view. Click on this button and the previously saved camera view is shown.\nSave Camera\nClick on this button and the current camera view is saved.\nTop View\nDisplay the models, looking down. Click this button and the models are automatically scaled to fit the view and displayed by looking down.\nFrame View - looking AFT\nDisplay the models, looking AFT. Click this button and the models are fitted to the view and displayed by looking in the backward direction.\nFrame View - looking FOR\nDisplay the models, looking FOR. Click this button and the models are fitted to the view and displayed by looking in the forward direction.\nSide View - looking port side\nDisplay the models, looking port side. Click this button and the models are fitted to the view and displayed by looking in the port side direction.\nIsometric View - looking AFT\nDisplay the models in an isometric view, looking. Click this button and the models are fitted to the view and displayed by an isometric projection. The main viewing direction is along the backward direction.\nIsometric View - looking FOR\nDisplay the models in an isometric view, looking FOR. Click this button and the models are fitted to the view and displayed by an isometric projection. The main viewing direction is along the forward direction.\nPerspective Camera\nToggles between the perspective and the parallel camera view. Click this button to toggle between the two camera types.\nSimple Measuring\nPresent model coordinates and distances. Click this button to select the measuring tool. And then click on a model in the graphics window and the model coordinate for the indicated point is presented in a dialog. It is also possible to press, drag and release the mouse button to present a distance between two model points.\n\n\n\nSelect Tool\nAuto Scale\nZoom Window\nZoom and Pan\nSlide\nSpin\nWalk\nTilt\nRestore Camera\nSave Camera\nTop View\nFrame View - looking AFT\nFrame View - looking FOR\nSide View - looking port side\nIsometric View - looking AFT\nIsometric View - looking FOR\nPerspective Camera\nSimple Measuring"}
{"Headers": "Common Commands", "Content": "The following commands are valid for most model items. Select one or in some cases several model items in the tree view or in the graphics window and then right-click to select one of the commands from the pop-up menu.\n\n\n"}
{"Headers": "Changing Root Node in Auxiliary Tree", "Content": "A new root can be selected in the auxiliary window by right-clicking on the new root node and then selecting the command New Window from Here. This command also ensures that the auxiliary window becomes visible.\nThe auxiliary tree can be toggled on or off by the command View > Auxiliary Tree.\n\n\n\nNew Window from Here\nView > Auxiliary Tree"}
{"Headers": "Hide/Unhide", "Content": "A model item can be hidden or made visible again in the graphics view by using the commands Hide or Unhide.\n\n\n\nHide\nUnhide"}
{"Headers": "Select in View", "Content": "The select in view command is a quick way to zoom in on one or more selected model items in the graphics window. It is possible to zoom a model item that is not included in the graphics window.\n\n\n"}
{"Headers": "Rename", "Content": "Change the name of an item in the workspace - it can be a model item or a scene.\n\n\n"}
{"Headers": "Delete", "Content": "Deletes model item(s). It could be hull surfaces, primitives, faces, scenes or the contents of a scene.\n\n\n"}
{"Headers": "Importing Models", "Content": "The Hull Surface area or the Primitive Assembly area is populated by importing geometry models from files or from marine projects. Models are imported by right-clicking on one of the areas, and then selecting an appropriate import command from the pop-up menu.\nA model can also be imported by dragging a file from the Windows Explorer to the Hull Surfaces/Primitive Assemblies node in the tree view.\n\n\n"}
{"Headers": "Import from File", "Content": "This function imports geometry models from a variety of different types of files. Currently, the following formats are supported:\nModels are imported by clicking on the command Import from File and then selecting one or more files to be imported.\nSTEP 203 format.\nSAT format.\nIGES format\nDML format. Native format for Initial Design Hull Forms.\nSTEP 203 format.\nSTEP 203 format.\nSAT format.\nSAT format.\nIGES format\nIGES format\nDML format. Native format for Initial Design Hull Forms.\nDML format. Native format for Initial Design Hull Forms.\n\n\n\nImport from File"}
{"Headers": "Import from project", "Content": "This function imports a hull surface from a marine project. The import is invoked by clicking on the menu item Import from Project and then selecting a hull surface from the shown drop-down list. The first time this function or a release function is invoked, a dialog is shown that enables the user to select a Marine project. This project cannot be changed during the rest of the session, but it's still possible to import from one project and release to another by following the following steps:\n\n\n\nImport from Project"}
{"Headers": "Releasing Models", "Content": "The release functions are used to release a hull surface and the belonging curves to a marine design project. If necessary, use the rename command to specify the correct surface name, before the surface is released.\n\n\n"}
{"Headers": "Release Surface", "Content": "Click on the command Release Surface to copy a surface to a marine design project. It's only possible to do a direct release from the Hull Surfaces area. A primitive in the Primitive Assemblies area can still be released by following the steps below:\n\n\n\nRelease Surface"}
{"Headers": "Release Surface as Symmetric", "Content": "This is basically the same function as Release Surface, but with the difference that the surface is marked as symmetric in the database. A symmetric surface is not allowed to cross the centreline.\n\n\n"}
{"Headers": "Exporting Models", "Content": "The export function saves a single surface/primitive or a hierarchy of models to a single file. The models can be exported in STEP, IGES or SAT format.\n\n\n"}
{"Headers": "Export to File", "Content": "Select the items to be exported by right-clicking on a primitive in the graphical view or a node in the model tree. Click on the Export to File in the popup menu, and then specify the file name and file format in the shown file dialog.\n\n\n\nExport to File"}
{"Headers": "Export to BLines File", "Content": "To allow users to further modify surfaces created in 3rd party software, the general import functions in Surface Manager along with the tools for extracting curves can prepare data for use in Lines/PACE. The export function creates a blines file with complete curve information, including data points, which allow users to continue working with the curves as if they were created in Lines/PACE.\nData points are approximated to generate a curve that is within a fixed tolerance of 0.5 mm from the original curve.\n\n\n"}
{"Headers": "Operations on Surfaces and Primitives", "Content": "The tools explained below have been developed to assist the user to find and optionally fix defects or weak spots in imported geometry.\n\n\n"}
{"Headers": "Mining Work Area", "Content": "Many features of the Mining discipline user interface are common to multiple AVEVA E3D Design disciplines, with the exception of the functionality available for selection on the Mining tab.\n\nProject tab\nProvides access to a number of key commands and facilities, most of the functionality available for selection are common to multiple AVEVA E3D Design disciplines.\nMining tab\nIncludes the following functionality specific to the Mining discipline:\nPowerWheel\u2122\nMany operations in the Mining discipline can be initiated using the PowerWheel. The equivalent functionality is also available from the Mining user interface, all of the out of box configurations for the PowerWheel can be customized.\n\nCreate\nModify\nTools\nStructure Storage\nSection Defaults\nCreate\nCreate\nModify\nModify\nTools\nTools\nStructure Storage\nStructure Storage\nSection Defaults\nSection Defaults\nNote:\nThe Admin tab is only available for selection, if you a member of the MININGADMIN team.\n\n\n\n\nNote\n:\nAdmin\nProject tab\nMining tab\nPowerWheel\u2122"}
{"Headers": "Create Conveyor", "Content": "Defines and creates a conveyor (CONVEY) element in the Mining hierarchy.\n\n\n\nConveyor detail pages (General, Arrangement details, Snub and Take up, Belts and Idlers, Tail, Head, and Build) are displayed by progressive disclosure:\nThe Build window shows which mandatory entries are still required.\n\nBlue ticks indicate that all entries are valid.\nA green circle indicates that all conveyor elements are ok.\nOrange triangles indicate that mandatory entries are still required.\nBlue ticks indicate that all entries are valid.\nBlue ticks indicate that all entries are valid.\nA green circle indicates that all conveyor elements are ok.\nA green circle indicates that all conveyor elements are ok.\nOrange triangles indicate that mandatory entries are still required.\nOrange triangles indicate that mandatory entries are still required.\n\n\n\nGeneral\nArrangement details\nSnub and Take up\nBelts and Idlers\nTail, Head\nBuild\nBuild"}
{"Headers": "Conveyor General Attributes", "Content": "Defines and creates the general attributes of the conveyor element.\n\nTag Number and Description\nBy default, displays the auto generated tag number. If required enter a project specific name.\nBy default, displays the description attribute. If required enter a project specific description attribute. The description attribute is optional but we recommend it.\nWorkflow\nChoose from one of the available basic arrangements or one of the methods to import conveyor profile from third party data.\nSelect the Basic Arrangement check box then select from straight, single curve, or two curves.\n\nSelect the Import Design check box to choose From Aid Group or From Excel.\n\nCharge position\nCreates the charge position for the conveyor element, using the coordinates manually entered, using an offset by or picked from the 3D view. These coordinates can then be locked.\nDischarge position\nCreates the discharge position for the conveyor element, using the coordinates manually entered, using an offset by or picked from the 3D view. These coordinates can then be locked.\nRefer to Conveyor Arrangement Details, Horizontal Support and Vertical Support for further information.\nNote: For imported conveyors, the charge and discharge positions are inactive because they will be determined by the imported data. Finish creating the conveyor and then use the tools on the General tab to make any necessary adjustments to the position and orientation of the conveyor.\n\n\n\nConveyor Arrangement Details\nHorizontal Support\nVertical Support\nTag Number\nDescription\nWorkflow\nBasic Arrangement\nImport Design\nFrom Aid Group\nFrom Excel\nCharge position\nDischarge position\nNote\nConveyor Arrangement Details\nHorizontal Support\nVertical Support"}
{"Headers": "Conveyor Arrangement Details", "Content": "Available only if a basic arrangement with one or more curves, or an import, has been selected.\nDisplays a graphical representation of the inflection point at each curve. The parameters define the position and geometry of each curve on the conveyor.\n\nInflection 1\nSpecifies the inflection point and radius of the first curve.\n\nRadius 1 (R1)\nSpecifies the radius of the curve of the conveyor element, the radius must be defined before the U1 and W1 dimensions.\nU1 Offset From Tail\nSpecifies the length of the offset distance from the tail (U1) with respect to the charge position.\nW1 Offset From Tail\nSpecifies the height of the offset from the tail (W1) with respect to the charge position.\nZoom In/Out\nZooms in/out to these dimensions in the 3D view.\nInflection 2\nSpecifies the inflection point and radius of the second curve.\n\nRadius 2 (R2)\nSpecifies the second radius of the curve of the conveyor element, the radius must be defined before the U2 and W2 dimensions.\nU2 Offset From Head\nSpecifies the length of the offset distance from the head (U2) with respect to the discharge position.\nW2 Offset From Head\nSpecifies the height of the offset from the head (W2) with respect to the discharge position.\nZoom In/Out\nZooms in/out to these dimensions in the 3D view.\n\n\n\nInflection 1\nRadius 1 (R1)\nU1 Offset From Tail\nW1 Offset From Tail\nZoom In/Out\nInflection 2\nRadius 2 (R2)\nU2 Offset From Head\nW2 Offset From Head\nZoom In/Out"}
{"Headers": "Conveyor Belt and Idlers", "Content": "Creates and defines the belt details and the idler dimensions.\n\nBelt Details\nDefines the width and thickness for the conveyor belt.\n\nIdlers\nDisplays a graphical representation of the Idlers, defines the dimensions of the Impact Zone Length and Impact, Return and Carrying Idler Space.\n\nL\nSpecifies the Impact Zone Length for the idlers.\nL2\nSpecifies the Impact Idler Space for the idlers.\nLC\nSpecifies the Carrying Idler Space for the idlers.\nLR\nSpecifies the Return Idler Space for the idlers, displays a list and graphical representation of impact, trough and return idlers available for selection from the catalogue. Idlers are displayed in groups and by default, the Impact tab is selected.\nTroughing Angle\nDisplays the troughing angle for the conveyor belt.\n\n\n\n\nBelt Details\nIdlers\nL\nL2\nLC\nLR\nTroughing Angle"}
{"Headers": "Single Tail Pulley", "Content": "Defines the distance and dimensions for a single tail pulley with a no snub pulley and the take-up at the head.\nDistance\nDisplays a graphical representation, define the distance from charge to tail pulley and the belt transition length from the tail pulley. By default the Distance tab is selected.\n\nL1\nSpecifies the distance from the centerline of the charge point to the center of the tail pulley\nZ1\nSpecifies the belt transition (troughed to flat) length of the belt.\nZoom In/Out\nZooms in/out to these dimensions in the 3D view.\nTail Pulley\nDisplays a graphical representation, defines the tail pulley\u2019s diameter, face width, wrap angle, offset A, shaft diameter and length.\n\nA\nSpecifies the tail pulley offset A\nD\nSpecifies the tail pulley diameter\nD\nSpecifies the tail pulley shaft diameter\nFACE WIDTH\nSpecifies the tail pulley face width.\nSHAFT LENGTH\nSpecifies the tail pulley shaft length\nWRAP ANGLE\nSpecifies the tail pulley wrap angle (the minimum is 180 degrees and the maximum is 240 degrees).\n\n\n\nDistance\nDistance\nL1\nZ1\nZoom In/Out\nTail Pulley\nA\nD\nD\nFACE WIDTH\nSHAFT LENGTH\nWRAP ANGLE"}
{"Headers": "Tail Pulley and Snub", "Content": "Displays a graphical representation of the snub tail pulley arrangement, define the snub distance between belt paths and the snub tail diameter, displays a graphical representation of the Snub Tail Pulley.\n\nD\nSpecifies the snub tail pulley shaft diameter\nJ\nSpecifies the snub distance J between belt path (both snub pulleys only).\n\n\n\nD\nJ"}
{"Headers": "Tail Pulley and Takeup", "Content": "Displays the take-up and counterweight arrangements for take-up at tail, the dimensions and details available depend upon the Take up at configuration selected.\n\n\n"}
{"Headers": "Tail - Gravity Horizontal", "Content": "Defines the takeup and counter weight dimensions for Takeup at Tail with Gravity Horizontal selected.\nTakeup\nDisplays a graphical representation of the Takeup arrangement.\n\nALPHA\nSpecifies the Alpha Angle\nD\nSpecifies the Takeup Diameter\nD1\nSpecifies the Takeup Snub Diameter1\nD2\nSpecifies the Takeup Snub Diameter2\nD3\nSpecifies the Takeup Snub Diameter3\nE\nSpecifies the Horizontal Length (E) from TAIL Pulley To Takeup\nH1\nSpecifies the Vertical Length (H1) From Working Position To Takeup\nH2\nSpecifies the Vertical Length (H2) From Working Position To Takeup\nZoom In/Out\nZooms in/out to these dimensions in the 3D view.\nCounter Weight\nDisplays the graphical representation of the Counter Weight arrangement.\n\nI\nSpecifies the Tower Height\nK\nSpecifies the Cable Distance\nL\nSpecifies the Distance from the Pulley\nNo OF BLOCKS\nSpecifies the Concrete Block No.Specifies the Concrete Block No\nMirror Off/On\nMirrors the tower position about the conveyer centerline.\nNext\nDisplays the orthogonal view of the counter weight arrangement.\n\nA\nSpecifies the Bearing Center Distance\nB\nSpecifies the Bearing Backing\nC\nSpecifies the Concrete Block Length\nH\nSpecifies the Tower Height\nM\nSpecifies the Distance to Floor\nO\nSpecifies the Distance to the Concrete Block\nW\nSpecifies the Width from the Pulley\nBack\nDisplays a graphical representation of the counter weight arrangement.\nMirror Off/On\nMirrors the tower position about the conveyer centerline.\n\n\n\nTakeup\nALPHA\nD\nD1\nD2\nD3\nE\nH1\nH2\nZoom In/Out\nCounter Weight\nI\nK\nL\nNo OF BLOCKS\nMirror Off/On\nNext\nA\nB\nC\nH\nM\nO\nW\nBack\nMirror Off/On"}
{"Headers": "Tail - Gravity Inclined", "Content": "Defines the takeup and counter weight dimensions for Takeup at Head with Gravity Horizontal selected.\nTakeup\nDisplays a graphical representation of the Takeup arrangement.\n\nALPHA\nSpecifies the Alpha Angle\nD\nSpecifies the Takeup Diameter\nD1\nSpecifies the Takeup Snub Diameter1\nD2\nSpecifies the Takeup Snub Diameter2\nE\nSpecifies the Horizontal Length (E) From TAIL Pulley To Takeup\nH\nSpecifies the Vertical Length (H) From Working Position To Takeup\nZoom In/Out\nZooms in/out to these dimensions in the 3D view.\nCounter Weight\nDisplays the graphical representation of the Counter Weight arrangement.\n\nI\nSpecifies the Tower Width\nL\nSpecifies the Distance From Pulley\nNo OF BLOCKS\nSpecifies the Concrete Block No.\nMirror Off/On\nMirrors the tower position about the conveyer centerline.\nNext\nDisplays the orthogonal view of the counter weight arrangement.\n\nA\nSpecifies the Bearing Center Distance\nB\nSpecifies the Bearing Backing\nC\nSpecifies the Concrete Block Length\nH\nSpecifies the Tower Height\nK\nSpecifies the Cable Distance\nM\nSpecifies the Distance to Floor\nO\nSpecifies the Distance to the Concrete Block\nW\nSpecifies the Width from the Pulley\nBack\nDisplays a graphical representation of the counter weight arrangement.\nMirror Off/On\nMirrors the tower position about the conveyer centerline.\n\n\n\nTakeup\nALPHA\nD\nD1\nD2\nE\nH\nZoom In/Out\nCounter Weight\nI\nL\nNo OF BLOCKS\nMirror Off/On\nNext\nA\nB\nC\nH\nK\nM\nO\nW\nBack\nMirror Off/On"}
{"Headers": "Tail with Screw", "Content": "Defines the takeup dimensions for Takeup at Tail with Screw selected, displays a graphical representation of the screw arrangement.\n\nB\nSpecifies the Bearing Center Pulleys\nC\nSpecifies the Path Screw Length\nH\nSpecifies the Height Screw Takeup\nW\nSpecifies the Width Screw Takeup.\n\n\n\nB\nC\nH\nW"}
{"Headers": "Single Head Pulley", "Content": "Defines the distance and dimensions for a single head pulley with a no snub pulley and the takeup at the HEAD.\nDistance\nDisplays a graphical representation, define the distance from discharge point to the head pulley and the belt transition length from the head pulley. By default the Distance tab is selected.\n\nL2\nSpecifies the distance from the centerline of the discharge point to the center of the head pulley\nZ2\nSpecifies the belt transition (troughed to flat) length of the belt.\nZoom In/Out\nZooms in/out to these dimensions in the 3D view.\nHead Pulley\nDisplays a graphical representation of the Head Pulley arrangement, defines the head pulley\u2019s diameter, face width, wrap angle and offset A, shaft diameter and length.\n\nA\nSpecifies the Head Pulley Offset A\nD\nSpecifies the Head Pulley Diameter\nFACE LENGTH\nSpecifies the Head Pulley Face Width\nSHAFT LENGTH\nSpecifies the Head Pulley Shaft Length\nWRAP ANGLE\nSpecifies the Head Pulley Wrap Angle (the minimum is 180 degrees and the maximum is 240).\n\n\n\nDistance\nDistance\nL2\nZ2\nZoom In/Out\nHead Pulley\nA\nD\nFACE LENGTH\nSHAFT LENGTH\nWRAP ANGLE"}
{"Headers": "Head Pulley and Snub", "Content": "Defines the snub distance between belt paths and the snub head diameter, displays a graphical representation of the Snub Head Pulley arrangement.\n\nD\nSpecifies the Snub Head Pulley Shaft Diameter\nJ\nSpecifies the Snub Distance Between Belt Path (both snub pulleys only).\n\n\n\nD\nJ"}
{"Headers": "Head Pulley and Takeup", "Content": "Displays the takeup and counterweight arrangements for takeup at head, the dimensions and details available depend upon the Take up at configuration selected.\n\n\n"}
{"Headers": "Head - Gravity Vertical", "Content": "Defines the takeup and counter weight dimensions for Takeup at head with Gravity Vertical selected.\nTakeup\nDisplays a graphical representation of the Takeup arrangement.\n\nD\nSpecifies the Takeup Diameter\nD1\nSpecifies the Takeup Snub Diameter1\nD2\nSpecifies the Takeup Snub Diameter2\nE\nSpecifies the Horizontal (E) from HEAD Pulley to Takeup\nH\nSpecifies the Vertical Length (H) From Working Position Takeup.\nCounter Weight\nDisplays the graphical representation of the Counter Weight arrangement.\n\nA\nSpecifies the Bearing Center Distance\nB\nSpecifies the Bearing Backing\nC\nSpecifies the Concrete Block Length\nN\nSpecifies the Concrete Block No.\n\n\n\nTakeup\nD\nD1\nD2\nE\nH\nCounter Weight\nA\nB\nC\nN"}
{"Headers": "Head - Gravity Horizontal", "Content": "Defines the takeup and counter weight dimensions for Takeup at Head with Gravity Horizontal selected.\nTakeup\nDisplays a graphical representation of the Takeup arrangement.\n\nALPHA\nSpecifies the Alpha Angle\nD\nSpecifies the Takeup Diameter\nD1\nSpecifies the Takeup Snub Diameter1\nD2\nSpecifies the Takeup Snub Diameter2\nD3\nSpecifies the Takeup Snub Diameter3\nE\nSpecifies the Horizontal Length (E) From Head Pulley to Takeup\nH1\nSpecifies the Vertical Length (H1) From Working Position To Takeup\nH2\nSpecifies the Vertical Length (H2) From Working Position To Takeup.\nCounter Weight\nDisplays the graphical representation of the Counter Weight arrangement.\n\nI\nSpecifies the Tower Width\nK\nSpecifies the Cable Distance\nL\nSpecifies the Distance From Pulley\nNo OF BLOCKS\nSpecifies the Concrete Block No.\nMirror Off/On\nMirrors the tower position about the conveyer centerline.\nNext\nDisplays the orthogonal view of the counter weight arrangement.\n\nA\nSpecifies the Bearing Center Distance\nB\nSpecifies the Bearing Backing\nC\nSpecifies the Concrete Block Length\nH\nSpecifies the Tower Height\nM\nSpecifies the Distance to Floor\nO\nSpecifies the Distance to Concrete Block\nW\nSpecifies the Width from Pulley.\nBack\nDisplays a graphical representation of the counter weight arrangement.\nMirror Off/On\nMirrors the tower position about the conveyer centerline.\n\n\n\nTakeup\nALPHA\nD\nD1\nD2\nD3\nE\nH1\nH2\nCounter Weight\nI\nK\nL\nNo OF BLOCKS\nMirror Off/On\nNext\nA\nB\nC\nH\nM\nO\nW\nBack\nMirror Off/On"}
{"Headers": "Head - Gravity Inclined", "Content": "Defines the takeup and counter weight dimensions for Takeup at Head with Gravity Inclined selected.\nTakeup\nDisplays a graphical representation of the Takeup arrangement.\n\nALPHA\nSpecifies the Alpha Angle\nD\nSpecifies the Takeup Diameter\nD1\nSpecifies the Takeup Snub Diameter1\nD2\nSpecifies the Takeup Snub Diameter2\nE\nSpecifies the Horizontal Length (E) From HEAD Pulley To Takeup\nH\nSpecifies the Vertical Length (H) From Working Position To Takeup\nZoom In/Out\nZooms in/out to these dimensions in the 3D view.\nCounter Weight\nDisplays the graphical representation of the Counter Weight arrangement.\n\nI\nSpecifies the Tower Width\nL\nSpecifies the Distance from Pulley\nNo OF BLOCKS\nSpecifies the Concrete Block No.\nMirror Off/On\nMirrors the tower position about the conveyer centerline.\nNext\nDisplays the orthogonal view of the counter weight arrangement.\n\nA\nSpecifies the Bearing Center Distance\nB\nSpecifies the Bearing Backing\nC\nSpecifies the Concrete Block Length\nH\nSpecifies the Tower Height\nK\nSpecifies the Cable Distance\nM\nSpecifies the Distance to Floor\nO\nSpecifies the Distance to Concrete Block\nW\nSpecifies the Width from Pulley\nBack\nDisplays a graphical representation of the counter weight arrangement.\nMirror Off/On\nMirrors the tower position about the conveyer centerline.\n\n\n\nTakeup\nALPHA\nD\nD1\nD2\nE\nH\nZoom In/Out\nCounter Weight\nI\nNo OF BLOCKS\nMirror Off/On\nNext\nA\nB\nC\nH\nK\nM\nO\nW\nBack\nMirror Off/On"}
{"Headers": "Head with Screw", "Content": "Defines the takeup dimensions for the Takeup at Head with Screw selected, displays a graphical representation of the screw arrangement.\n\nB\nSpecifies the Bearing Center Pulleys\nC\nSpecifies the Path Screw Length\nH\nSpecifies the Height Screw Takeup\nW\nSpecifies the Width Screw Takeup.\n\n\n\nB\nC\nH\nW"}
{"Headers": "Build Summary", "Content": "Displays the status and details of the conveyor element.\n\n\n\n"}
{"Headers": "Create Cover", "Content": "Creates a cover element for the currently selected (CE) conveyor element in the mining hierarchy. Displays a graphical representation of the accessory arrangement.\n\nEnter dimensions to define the extents of the cover.\nA\nDefines the cover length from the Tail pulley.\nB\nDefines the cover assembly clearance from the charge point.\nC\nDefines the cover assembly clearance from the Head pulley\nD\nDefines the cover section length - a length of zero means each straight or curve will be built as a single section.\n\n\n\nA\nB\nC\nD"}
{"Headers": "Create Support", "Content": "Create pulley support or frame structure elements in the Mining hierarchy.\n\n\n"}
{"Headers": "Create Pulley Support", "Content": "Use pulley support to create and define a pulley support element at the head and/or tail of the conveyor element.\n\n\n"}
{"Headers": "Vertical Support", "Content": "Defines the dimensions and profiles used in the vertical support, HEAD displayed by default. Displays a graphical representation of the vertical support arrangement.\n\nEnter the dimensions to define the vertical pulley support at the head/tail of the conveyor element.\nA\nHead Pulley Support Length\nB\nHead Offset from Frame Support\nC\nCenterline from Head Pulley to Top\nD\nCenterline from Head Pulley to Bottom\n1 (Profile 1)\nFor structural support elements only, profile of bar selected from the structural catalogue (Section Defaults).\n2 (Profile 2)\nFor structural support elements only, profile of leg selected from the structural catalogue Section (Defaults).\nRefer to Section Defaults and Structure Storage for further information.\nNote:\nVertical supports can be defined at the head or tail of the conveyor element.\n\n\n\nSection Defaults\nStructure Storage\nHEAD\nNote\n:\nA\nB\nC\nD\n1 (Profile 1)\n2 (Profile 2)\nSection Defaults\nStructure Storage"}
{"Headers": "Horizontal Support", "Content": "Defines the dimensions and profiles used in the tail pulley support, displays a graphical representation of the tail arrangement.\n\nEnter the dimensions to define the horizontal pulley support at the head/tail of the conveyor element.\nA\nTail Support Length\nB\nBearing Backing for Tail Pulley Support\nC\nTail Offset from Frame Support\nD\nBearing for Tail Pulley Support\nE\nTail Pulley Support Bar Height\nF\nTail Pulley Support Leg Width\n1 (Profile 1)\nFor structural support elements only, profile of bar selected from the structural catalogue (Section Defaults).\n2 (Profile 2)\nFor structural support elements only, profile of leg selected from the structural catalogue (Section Defaults).\n3 (Profile 3)\nFor structural support elements only, profile of leg selected from the structural catalogue (Section Defaults).\nRefer to Head, Section Defaults and Structure Storage for further information,\nNote:\nHorizontal supports can be defined at the head or tail of the conveyor element.\n\n\n\nHead\nSection Defaults\nStructure Storage\nNote\n:\nA\nB\nC\nD\nE\nF\n1 (Profile 1)\n2 (Profile 2)\n3 (Profile 3)\nHead\nSection Defaults\nStructure Storage"}
{"Headers": "Create Frame Support", "Content": "Use frame support to create and define a frame support element for the conveyor element.\n\n\n\n"}
{"Headers": "Box Truss", "Content": "Defines the dimensions and profiles used in the box truss structure element, displays a graphical representation of the box truss assembly.\nYou can create multiple frameworks on a conveyor. Use the\nicons in the Select Start and End section to specify the position of a framework. Click the left icon and then click on the required start position on the conveyor. Click the right icon and specify the end position. Click Select to confirm the positions.\n\nA\nFrame Total Length\nB\nFrame Internal Space\nC\nStart frame Distance from Tail\nD\nEnd Frame Distance from Head\nH\nFrame Support Height\n1 (Profile 1)\nFor structural support elements only, profile of leg selected from the structural catalogue (Section Defaults).\n2 (Profile 2)\nFor structural support elements only, profile of bar selected from the structural catalogue (Section Defaults).\n3 (Profile 3)\nFor structural support elements only, profile of bar selected from the structural catalogue (Section Defaults).\nRefer to Stringer, Section Defaults and Structure Storage for further information.\n\n\n\nStringer\nSection Defaults\nStructure Storage\nSelect Start and End\nSelect\nA\nB\nC\nD\nH\n1 (Profile 1)\n2 (Profile 2)\n3 (Profile 3)\nStringer\nSection Defaults\nStructure Storage"}
{"Headers": "Section Defaults", "Content": "Displays the profile specification, generic type and profile of a section selected from the structural catalogue for the pulley supports or frame support elements.\n\nProfile Specification\nDisplays a list of profile specifications available for selection from the structural catalogue.\nGeneric Type\nDisplays the generic type associated with the selected profile specification.\nProfile\nDisplays the profile associated with the selected profile specification.\nRefer to Box Truss, Stringer and Structure Storage for further information.\n\n\n\nBox Truss\nStringer\nStructure Storage\nProfile Specification\nGeneric Type\nProfile\nBox Truss\nStringer\nStructure Storage"}
{"Headers": "Structure Storage", "Content": "Displays zones in the catalogue database hierarchy where the structural elements (pulley support and frame support elements) can be correctly stored.\n\nRefer to Create Pulley Support and Create Frame Support for further information.\n\n\n\nCreate Pulley Support\nCreate Frame Support\nCreate Pulley Support\nCreate Frame Support"}
{"Headers": "Create Standard", "Content": "Select a parameterized equipment item (templates) based on a specification of standard equipment types.\nStandard equipment may be selected from a specification or from a selection table as configured in the Equipment catalogue, the selection table option is selected as default.\n\nPick coordinates in the 3D view to position the piece of standard equipment with precision.\nEquipment Origin\nSpecifies the position of the equipment origin.\nRefer to for further information.\n\n\n\nEquipment Origin\n"}
{"Headers": "Modify Conveyor", "Content": "\n\n\nModify the currently selected conveyor element in the Mining hierarchy, the functionality available is identical to that described in Create Conveyor.\nRebuilds the conveyor element with the modification(s).\nRefer to Create Conveyor for further information.\n\n\n\n\nCreate Conveyor\nCreate Conveyor"}
{"Headers": "Modify Cover", "Content": "Modify the currently selected cover element in the Mining hierarchy, the functionality available is identical to that described in Create Cover.\n\nRefer to Create Cover for further information.\n\n\n\nCreate Cover\nCreate Cover"}
{"Headers": "Modify Support", "Content": "Modifies a pulley support or frame structure element in the Mining hierarchy.\n\n\n"}
{"Headers": "Modify Pulley Support", "Content": "Modify the currently selected Pulley Support element in the Mining hierarchy, the functionality available is identical to that described in Create Pulley Support.\n\nRefer to Create Pulley Support for further information.\n\n\n\nCreate Pulley Support\nCreate Pulley Support"}
{"Headers": "Modify Frame Support", "Content": "Modify the currently selected Frame Support element in the Mining hierarchy, the functionality available is identical to that described in Create Frame Support.\n.\n\n\n"}
{"Headers": "Modify Standard", "Content": "Modify the currently selected standard element in the MINING hierarchy, the functionality available is identical to that described in Create Standard.\n\nRefer to Create Standard for further information.\n\n\n\nCreate Standard\nCreate Standard"}
{"Headers": "Tools", "Content": "Saves the current conveyor element and all the associated attributes to a selected location, loads a previously created conveyor element from a known location. Set the material reference for use in reporting and checking functionality. Zooms to the currently selected conveyor element in the 3D view and removes all the dimensions from the 3D view.\n\n\n"}
{"Headers": "Save Conveyor", "Content": "For conveyor element, exports a conveyor element as an excel file.\n\nLocation\nDisplays a list of available locations to export the excel file.\nFile name\nEnter a name for the excel file.\nSave as type\nDefault.\nLocation\nDisplays a list of available locations to export the excel file.\nFile name\nEnter a name for the excel file.\nSave as type\nDefault.\n\nLocation\nDisplays a list of available locations to export the excel file.\nFile name\nEnter a name for the excel file.\nSave as type\nDefault.\n\n\n\nLocation\nFile name\nSave as type"}
{"Headers": "Load Conveyor", "Content": "Imports a previously created conveyor element from a selected location in the format of an excel file.\n\nLocation\nDisplays available locations to load an existing conveyor element from in the format of an excel file.\nFile name\nOnce selected the file name for the selected conveyor excel file is displayed.\nLocation\nDisplays available locations to load an existing conveyor element from in the format of an excel file.\nFile name\nOnce selected the file name for the selected conveyor excel file is displayed.\n\nLocation\nDisplays available locations to load an existing conveyor element from in the format of an excel file.\nFile name\nOnce selected the file name for the selected conveyor excel file is displayed.\n\n\n\nLocation\nFile name"}
{"Headers": "Set Material", "Content": "The material reference (Matref) attribute can be modified so that attributes such as weight and COG can be calculated and then used with the checking and reporting functionality of AVEVA E3D Design.\n\nCE\nIdentifies the element in the hierarchy as the CE.\nMaterials\nDisplays a list of materials (Matref) available for selection.\nCascade material to all offspring\nClick to select the check box to cascade the Matref to all of the CE\u2019s offspring, by default the check box is not selected.\n\n\n\nCE\nMaterials\nCascade material to all offspring"}
{"Headers": "Zoom to Conveyor", "Content": "Zooms to the currently selected conveyor element in the 3D view.\n\n\n"}
{"Headers": "Clear All Dimensions", "Content": "Clears all the dimensional aids from the conveyor element in the 3D view.\n\n\n"}
{"Headers": "Piping Defaults", "Content": "Most of the work area is common to multiple AVEVA E3D Design design disciplines, but some areas with respect to the PIPING discipline can be customized. Use the Piping Application Defaults window to set the piping defaults.\nThe Piping Application Defaults window acts as a task hub, which allows the setting of default piping application options, for the component editor, pipe editor, selection, ISO view and Laser Data.\n\n\n\n\nPIPING\nPiping Application Defaults\nPiping Application Defaults\ncomponent editor\npipe editor\nselection\nISO view\nLaser Data"}
{"Headers": "Read Only", "Content": "The Piping Application Defaults window is available to everyone but some functions can be restricted by creating a team called PIPINGADMIN. If this team exists and the current user is not a member of the team, the Piping Application Defaults window is presented with certain functionality greyed out. This restricts the changes which can be made by the user because the Piping Application Defaults window buttons are no longer active.\n\n\n\n\nPiping\nApplication Defaults\nPiping Application Defaults\nPiping Application Defaults"}
{"Headers": "Piping Settings", "Content": "The Component part of the Piping Application Defaults window sets the default settings on the Piping Component Editor window.\n\nSnap distance\nSets the default snap distance (the minimum distance between the end of a component and the placement of a new component between which an automatic connection occurs) when creating a component. The selection is connected to the nearest component if placed within the set snap distance. The default is 2 * OD.\nUse tube tolerance\nUses a pre-set Data Consistency specific tube length to ensure the pipe is placed correctly.\nMinimum tube length\nSets the minimum tube distance between two components, the default is 100mm.\nNote:\nThe Data Consistency window must be used to set up the minimum tube lengths for different bore sizes.\nUse tube tolerance\nUses pre-set Data Consistency specific tube length to ensure the pipe is placed correctly.\nNote:\nIf the Snap Distance and Min Tube check boxes are selected, the tube tolerance check options (Datacon) are used.\nAuto align\nNewly created components are aligned to the previous component automatically.\nAuto create\nThe software determines if there is a requirement for associated components by default (for example, the associated components for a valve are a gasket and a flange).\nSelect adjacent out of specification\nAn alternative specification component can be used.\nSkip connected components\nThe piping application determines which components are connected, then positions the creation point approximately.\nMultiple slope functionality\nDisplays the point direction option on the Piping Component Editor window.\nNon standard branch connections\nSets the defaults for the non-standard branch connections.\nBoss connections not allowed in tube\nFor pipe tappings, specifies the boss type connections (for example, olets, half couplings, welded bosses) that can only be used on fittings and excluded from the tube.\nSnap distance\nSets the default snap distance (the minimum distance between the end of a component and the placement of a new component between which an automatic connection occurs) when creating a component. The selection is connected to the nearest component if placed within the set snap distance. The default is 2 * OD.\nUse tube tolerance\nUses a pre-set Data Consistency specific tube length to ensure the pipe is placed correctly.\nMinimum tube length\nSets the minimum tube distance between two components, the default is 100mm.\nUse tube tolerance\nUses pre-set Data Consistency specific tube length to ensure the pipe is placed correctly.\n\nAuto align\nNewly created components are aligned to the previous component automatically.\nAuto create\nThe software determines if there is a requirement for associated components by default (for example, the associated components for a valve are a gasket and a flange).\nSelect adjacent out of specification\nAn alternative specification component can be used.\nSkip connected components\nThe piping application determines which components are connected, then positions the creation point approximately.\nMultiple slope functionality\nDisplays the point direction option on the Piping Component Editor window.\nNon standard branch connections\nSets the defaults for the non-standard branch connections.\nBoss connections not allowed in tube\nFor pipe tappings, specifies the boss type connections (for example, olets, half couplings, welded bosses) that can only be used on fittings and excluded from the tube.\nThe Pipe/Branch part of the Piping Application Defaults window sets the default pipe editor settings on the Piping Component Editor window.\n\nSort piping specification list\nSorts the piping specification list alphabetically.\nAuto create gaskets and flanges at branch\nOn creation of a component, gaskets and flanges are automatically created.\nSort piping specification list\nSorts the piping specification list alphabetically.\nAuto create gaskets and flanges at branch\nOn creation of a component, gaskets and flanges are automatically created.\nThe Reselection part of the Piping Application Defaults window sets the default component selection settings on the Piping Component Editor window.\n\nDescriptions\nSets the display of the Description in the Component Type List from the Select and Reselect tabs.\nTag component\nSets the display value for the component tag in the 3D graphical view.\nTag constraints\nWhen a component is selected, adjacent constrained components are highlighted in the 3D graphical view.\nAuto reconnect\nReconnects components that are modified using the Reselect tab. Reconnection errors display in the Errors tab.\nReconnect free ends\nReconnects the branch head or branch tail if reselection of a component results in disconnection.\nIgnore positioned\nIgnores positioned components. Positioned components will normally not be moved when reconnected.\nDescriptions\nSets the display of the Description in the Component Type List from the Select and Reselect tabs.\nTag component\nSets the display value for the component tag in the 3D graphical view.\nTag constraints\nWhen a component is selected, adjacent constrained components are highlighted in the 3D graphical view.\nAuto reconnect\nReconnects components that are modified using the Reselect tab. Reconnection errors display in the Errors tab.\nReconnect free ends\nReconnects the branch head or branch tail if reselection of a component results in disconnection.\nIgnore positioned\nIgnores positioned components. Positioned components will normally not be moved when reconnected.\nThe Laser Data part of the Piping Application Defaults window sets the default settings for laser settings on the Piping Component Editor window.\n\nDirection rounding\nRounds to an orthogonal direction (ENUWSD) for each component from the laser pick.\nTolerance\nTolerance of the direction.\nDirection rounding\nRounds to an orthogonal direction (ENUWSD) for each component from the laser pick.\nTolerance\nTolerance of the direction.\nThe Direction Display part of the Piping Application Defaults window sets the default display settings on the Piping Component Editor window.\n\nDefault ISO view\nSets the default ISO view of elements displayed in the 3D graphical view. The ISO view updates depending on the type of the current project as well as the coordinate system.\nIf the current project is PLANT and the coordinates are ENU, the default ISO view is North.\nIf the current project is PLANT and the coordinates are XYZ, the default ISO view is Y.\nIf the current project is MARINE and the coordinates are ENU, the default ISO view is East.\nif the current project is MARINE and the coordinates are XYZ, the default ISO view is X.\nDefault ISO view\nSets the default ISO view of elements displayed in the 3D graphical view. The ISO view updates depending on the type of the current project as well as the coordinate system.\nIf the current project is PLANT and the coordinates are ENU, the default ISO view is North.\nIf the current project is PLANT and the coordinates are XYZ, the default ISO view is Y.\nIf the current project is MARINE and the coordinates are ENU, the default ISO view is East.\nif the current project is MARINE and the coordinates are XYZ, the default ISO view is X.\n\nSnap distance\nSets the default snap distance (the minimum distance between the end of a component and the placement of a new component between which an automatic connection occurs) when creating a component. The selection is connected to the nearest component if placed within the set snap distance. The default is 2 * OD.\nUse tube tolerance\nUses a pre-set Data Consistency specific tube length to ensure the pipe is placed correctly.\nMinimum tube length\nSets the minimum tube distance between two components, the default is 100mm.\nNote:\nThe Data Consistency window must be used to set up the minimum tube lengths for different bore sizes.\nUse tube tolerance\nUses pre-set Data Consistency specific tube length to ensure the pipe is placed correctly.\nNote:\nIf the Snap Distance and Min Tube check boxes are selected, the tube tolerance check options (Datacon) are used.\nAuto align\nNewly created components are aligned to the previous component automatically.\nAuto create\nThe software determines if there is a requirement for associated components by default (for example, the associated components for a valve are a gasket and a flange).\nSelect adjacent out of specification\nAn alternative specification component can be used.\nSkip connected components\nThe piping application determines which components are connected, then positions the creation point approximately.\nMultiple slope functionality\nDisplays the point direction option on the Piping Component Editor window.\nNon standard branch connections\nSets the defaults for the non-standard branch connections.\nBoss connections not allowed in tube\nFor pipe tappings, specifies the boss type connections (for example, olets, half couplings, welded bosses) that can only be used on fittings and excluded from the tube.\nSort piping specification list\nSorts the piping specification list alphabetically.\nAuto create gaskets and flanges at branch\nOn creation of a component, gaskets and flanges are automatically created.\nDescriptions\nSets the display of the Description in the Component Type List from the Select and Reselect tabs.\nTag component\nSets the display value for the component tag in the 3D graphical view.\nTag constraints\nWhen a component is selected, adjacent constrained components are highlighted in the 3D graphical view.\nAuto reconnect\nReconnects components that are modified using the Reselect tab. Reconnection errors display in the Errors tab.\nReconnect free ends\nReconnects the branch head or branch tail if reselection of a component results in disconnection.\nIgnore positioned\nIgnores positioned components. Positioned components will normally not be moved when reconnected.\nDirection rounding\nRounds to an orthogonal direction (ENUWSD) for each component from the laser pick.\nTolerance\nTolerance of the direction.\nDefault ISO view\nSets the default ISO view of elements displayed in the 3D graphical view. The ISO view updates depending on the type of the current project as well as the coordinate system.\nIf the current project is PLANT and the coordinates are ENU, the default ISO view is North.\nIf the current project is PLANT and the coordinates are XYZ, the default ISO view is Y.\nIf the current project is MARINE and the coordinates are ENU, the default ISO view is East.\nif the current project is MARINE and the coordinates are XYZ, the default ISO view is X.\nNote:\nThe Data Consistency window must be used to set up the minimum tube lengths for different bore sizes.\nNote:\nIf the Snap Distance and Min Tube check boxes are selected, the tube tolerance check options (Datacon) are used.\n\n\n\nComponent\nPiping Application Defaults\nPiping Component Editor\nSnap distance\n2 * OD\nUse tube tolerance\nMinimum tube length\nNote\n:\nData Consistency\nUse tube tolerance\nNote\n:\nSnap Distance\nMin Tube\nAuto align\nAuto create\nSelect adjacent out of specification\nSkip connected components\nMultiple slope functionality\nPiping Component Editor\nNon standard branch connections\nBoss connections not allowed in tube\nPipe/Branch\nPiping\nApplication Defaults\nPiping Component Editor\nSort piping specification list\nAuto create gaskets and flanges at branch\nReselection\nPiping\nApplication Defaults\nPiping Component Editor\nDescriptions\nTag component\nTag constraints\nAuto reconnect\nReselect\nReconnect free ends\nIgnore positioned\nLaser Data\nPiping Application Defaults\nPiping Component Editor\nDirection rounding\nTolerance\nDirection Display\nPiping\nApplication Defaults\nPiping Component Editor\nDefault ISO view\nNorth\nY\nEast\nX"}
{"Headers": "Piping Bend Radius Defaults", "Content": "The Piping Bend Radius Defaults limits the bend radii available for selection from the Bend Information part of the Component Editor window, when using variable radius bends.\nMultipliers\nUse to set the default range of multipliers available for selection from the Bend Information part of the Component Editor window. The actual bend radius is set to the multiplier * the outside diameter of the tube.\n\nDefined Value\nUse to set the define option as the only selection from the Bend Information part of the Component Editor window, when using variable radius bends.\n\nThis is a default setting in the file PMLUI\\dflts\\des which defines a PML global variable called !!limitRadiusOptions\n!!limitRadiusOptions = FALSE is the default and does not alter the multiplier list Setting it to true restricts it as shown.\n\n\n\nPiping Bend Radius Defaults\nBend Information\nComponent Editor\nMultipliers\nBend Information\nComponent Editor\n*\nDefined Value\nBend Information\nComponent Editor\n!!limitRadiusOptions\n!!limitRadiusOptions = FALSE"}
{"Headers": "Work Area", "Content": "Many features of the Piping discipline user interface are common to multiple AVEVA E3D Design design disciplines and are described in Common Functionality User Guide. With the exception of the functionality available for selection on the Piping tab.\nTo enter the Piping discipline, from the Quick Access Toolbar, select Piping from the Disciplines drop-down list. When the Piping discipline is opened, by default the Project tab is selected.\n\nNote:\nThe Admin tab is only available for selection, if you are a member of the PIPEADMIN team. For administrative options, refer to Integrator Administration for further information.\n\n\n\nCommon Functionality User Guide\nPiping\nQuick Access Toolbar\nPiping\nDisciplines\nProject\nNote\n:\nAdmin\nIntegrator Administration"}
{"Headers": "Database Hierarchy", "Content": "All database elements are owned by other elements, therefore elements must be created in a strict order.\nThe following database elements are common to multiple AVEVA E3D Design design disciplines:\nWorld\nSite\nZone\nWorld\nWorld\nSite\nSite\nZone\nZone\n\n\n"}
{"Headers": "Pipework Specific Hierarchy", "Content": "Below the zone level in the Piping discipline, the specific elements are:\n\nPipe (PIPE)\nThe Pipe (PIPE) element(s) are administrative and can own a number of branches with a common pipe specification and have any number of ends.\nBranch (BRAN)\nThe Branch (BRAN) element(s) own a section of pipe (made up from piping components) with a known head and tail.\nPiping Component\nThe Piping component element(s) are owned by branch elements. These components dictate the shape and geometry of the pipe work. Piping components can run from the head to tail of the owning branch but can also be connected to other branches (for example - a tee component).\nDepending on the selections further windows are displayed prompting for input and options allowing for the workflow to continue.\nPiping elements cannot be created or modified, if the correct database hierarchy has not been configured beforehand or if the correct current element has not been selected in the Model Explorer. For example certain piping elements must reside below other elements in the database hierarchy.\n\n\n\nPipe (PIPE)\nBranch (BRAN)\nPiping Component\nModel Explorer"}
{"Headers": "Create New Pipe Element", "Content": "The Pipe (PIPE) element(s) are administrative and can own a number of branches with a common pipe specification and have any number of ends.\n\nBy default the Primary System is No System, to change the type of primary system select a system from the Primary System drop-down list.\nChoose from the list of pipe specifications. All piping components later created below the branch use the Specification selected in the list. To use different specifications within a pipe run, a new branch must be created at each point a different specification is used.\nIf required, filter the list of specifications:\n\nThe Bore specifies the nominal bore and does not affect the pipe route (the default is unset).\nSelect an Insulation specification, if no insulation is required (the default is None), select None.\nSelect a Tracing specification, if no tracing is required (the default is None), select None.\nIn Temperature, enter the temperature to which the pipe can reach (the default is -10000degC, this means that the temperature is ignored).\nIn Pressure, enter the pressure to which the pipe must withstand (the default is 0pascal).\nThe Slope Ref specifies the slope reference attribute, which is governed by the catalog (the default is none). To change the slope reference attribute, select a slope reference from the Slope Ref: drop-down list.\nFrom the Fluid Ref drop down, select a fluid ref (defines the properties of the liquids or gases used with specific piping components). This governs the FluRef attribute on the pipe or branch.\nFrom the Bending Machine drop down, select the bending machine to be used when selecting bends within the pipe. This governs the BENDMACREFERENCE attribute on the pipe or branch.\nClick Apply, to create a new pipe and branch element in the Design database and display the Pipe Editor: Modify Pipe window, to define the branch, refer to for further information.\nA pipe and branch element has now been created in the design database.\nThe Pipe Editor: Modify Pipe window displays by default when a new pipe element is created. It is a dual purpose window which allows the definition of branch attributes and/or connect the branch head and branch tail or modify an existing branch.\nConnect Branch Head to First Branch Member.\n\nBy default, the Pipe Editor: Modify Pipe window is populated with the attributes of the Current Element (CE), if required, select another pipe as the CE.\nSet working pipe\nSets the currently selected pipe, from the Model Explorer or 3D graphical view, as the working pipe.\n\nSet working pipe\nSets the currently selected pipe, from the Model Explorer or 3D graphical view, as the working pipe.\n\nSet working pipe\nSets the currently selected pipe, from the Model Explorer or 3D graphical view, as the working pipe.\nNote:\nIf a new insulation and/or tracing specification is required, refer to the system administrator.\nNote:\nWhen a branch has a slope reference set Datacon checks if the slope is correct or not, that is within tolerance.\n\n\n\nPrimary System\nNo System\nPrimary System\nBore\nInsulation\nNone\nTracing\nNone\nNote\n:\nTemperature\nPressure\nSlope Ref\nSlope Ref:\nNote\n:\nFluid Ref\nBending Machine\nBENDMACREFERENCE\nApply\nPipe Editor: Modify Pipe\n\nPipe Editor: Modify Pipe\nPipe Editor: Modify Pipe\nSet working pipe\nModel Explorer"}
{"Headers": "Branch Element", "Content": "A branch is a section of pipe made up from piping components with a known branch head or branch tail. The position of the branch head (starting point) and branch tail (finishing point) can be defined by either explicitly entering the position or by the selection of piping components (such as tees) or equipment nozzles for the head or tail to connect to.\n\n\n\n"}
{"Headers": "Pipe Specification", "Content": "Use the Pipe Editor: Pipe window to select an alternative Pipe Specification by clicking Modify Pipe Attributes to display the Pipe Editor: Modify Pipe specification window.\nThe Pipe Editor: Modify Pipe specification window has the same functionality as the Pipe Editor: Create Pipe window, refer to Create New Pipe Element for further information.\n\n\n\nCreate New Pipe Element\nPipe Editor: Pipe\nPipe Specification\nModify Pipe Attributes\nPipe Editor: Modify Pipe\nPipe Editor: Modify Pipe\nPipe Editor: Create Pipe\nCreate New Pipe Element"}
{"Headers": "Pipe Connectivity", "Content": "The Connectivity part of the Pipe Editor: Modify Pipe window displays the connectivity status of each branch within the pipe assembly.\n\nTo delete a branch, right-click the selected branch and select Delete Branch.\n\n\n\nConnectivity\nPipe Editor: Modify Pipe\nDelete Branch"}
{"Headers": "Branch Specification", "Content": "If required, select an alternative Branch Specification by clicking Modify Branch Attributes to display the Pipe Editor: Modify Pipe branch specification window.\nThe Pipe Editor: Modify Pipe branch specification window has the same functionality as the Pipe Editor: Create Pipe window, refer to Create New Pipe Element for further information.\nAutoroute branch\nUse to route complete branches from head to tail (deletes existing components).\nCreate a new branch\nCreates a new branch for the pipe assembly. Refer to for further information.\nCreate components in the selected branch\nUse the window to create new components\n\nAutoroute branch\nUse to route complete branches from head to tail (deletes existing components).\n\nCreate a new branch\nCreates a new branch for the pipe assembly. Refer to for further information.\n\nCreate components in the selected branch\nUse the window to create new components\n\nAutoroute branch\nUse to route complete branches from head to tail (deletes existing components).\nCreate a new branch\nCreates a new branch for the pipe assembly. Refer to for further information.\nCreate components in the selected branch\nUse the window to create new components\n\n\n\nCreate New Pipe Element\nBranch Specification\nModify Branch Attributes\nPipe Editor: Modify Pipe\nPipe Editor: Modify Pipe\nPipe Editor: Create Pipe\nCreate New Pipe Element\nAutoroute branch\nCreate a new branch\n\nCreate components in the selected branch"}
{"Headers": "Define Branch Head and Branch Tail", "Content": "The Branch Head and Branch Tail tabs on the Pipe Editor: Modify Pipe window, are used to define the connection and position of the branch head or branch tail. As the functionality for the definition of the branch head or branch tail is identical, for the purposes of this user guide, only the branch head definition is described. By default the branch head tab is selected when the Pipe Editor: Modify Pipe window displays.\nFor example, to define the head of the branch, make sure the correct branch is highlighted in the design database and the correct branch name displays in the Connectivity part of the of the Pipe Editor: Modify Pipe window.\n\nThe Branch head tab of the Pipe Editor: Modify Pipe window is used to connect the branch head and define basic branch head details, the connection status of the selected branch displays by default:\nDisconnect head\nDisconnects the branch head from the element it is currently connected to, refer to for further information.\nReconnect head\nReconnects the branch head that has moved position to an equipment element, refer to Reconnect Pipe to Element for further information.\nPick Branch in laser data to set head to\nSelects the head/tail position, orientation of laser data, refer to Laser Data for further information.\nPick item to connect head to\nConnects the branch head to a selected element, refer to for further information.\nConnect head to first branch member\nConnects the branch head to the first branch member, refer to Connect Branch Head to First Branch Member for further information.\n\nDisconnect head\nDisconnects the branch head from the element it is currently connected to, refer to for further information.\n\nReconnect head\nReconnects the branch head that has moved position to an equipment element, refer to Reconnect Pipe to Element for further information.\n\nPick Branch in laser data to set head to\nSelects the head/tail position, orientation of laser data, refer to Laser Data for further information.\n\nPick item to connect head to\nConnects the branch head to a selected element, refer to for further information.\n\nConnect head to first branch member\nConnects the branch head to the first branch member, refer to Connect Branch Head to First Branch Member for further information.\nAs an alternative to connecting the branch head on the 3D graphical view, input the name of the equipment element in the Connect to field.\nThe Bore, Connection and Direction fields are automatically populated.\nIn the Bore drop-down list, select the nominal bore of the pipe from the list of available sizes in the catalog.\nIn the Connection drop-down list, select the type of head connection from the list of available connections in the catalog.\nThe Direction specifies which direction the flow takes from the Branch Head. (The head direction is the direction of flow and the tail direction is the opposite direction of the flow).\nUse the Position wrt World: part of the Pipe Editor: Modify Pipe window to position the branch head explicitly.\nOpposite Direction\nReverses the head/tail direction (used with Laser Modelling). Refer to Laser Data for further information.\nPick head position\nDisplays the Positioning Control window. Refer to Positioning Control for further information.\nThe prompt Modify Pipe - Select Head Position (Distance[0]) Snap: is displayed.\n\nOpposite Direction\nReverses the head/tail direction (used with Laser Modelling). Refer to Laser Data for further information.\n\nPick head position\nDisplays the Positioning Control window. Refer to Positioning Control for further information.\nThe prompt Modify Pipe - Select Head Position (Distance[0]) Snap: is displayed.\nIf required use the positioning aids available for selection from the Positioning Control window, to select the head position on the. 3D graphical view.\nOnce selected the Position wrt World: part of the Pipe Editor: Modify Pipe window is populated.\nTo select a different format view, right-click over Format.\nIf required, select the check box to lock the position.\nDisconnect head\nDisconnects the branch head from the element it is currently connected to, refer to for further information.\nReconnect head\nReconnects the branch head that has moved position to an equipment element, refer to Reconnect Pipe to Element for further information.\nPick Branch in laser data to set head to\nSelects the head/tail position, orientation of laser data, refer to Laser Data for further information.\nPick item to connect head to\nConnects the branch head to a selected element, refer to for further information.\nConnect head to first branch member\nConnects the branch head to the first branch member, refer to Connect Branch Head to First Branch Member for further information.\nOpposite Direction\nReverses the head/tail direction (used with Laser Modelling). Refer to Laser Data for further information.\nPick head position\nDisplays the Positioning Control window. Refer to Positioning Control for further information.\nThe prompt Modify Pipe - Select Head Position (Distance[0]) Snap: is displayed.\n\n\n\nLaser Data\nLaser Data\nBranch Head\nBranch Tail\nPipe Editor: Modify Pipe\nPipe Editor: Modify Pipe\nConnectivity\nPipe Editor: Modify Pipe\nBranch head\nPipe Editor: Modify Pipe\nDisconnect head\n\nReconnect head\nReconnect Pipe to Element\nPick Branch in laser data to set head to\nLaser Data\nPick item to connect head to\n\nConnect head to first branch member\nConnect Branch Head to First Branch Member\nConnect to\nBore\nConnection\nDirection\nBore\nConnection\nDirection\nPosition wrt World:\nPipe Editor: Modify Pipe\nOpposite Direction\nLaser Data\nPick head position\nPositioning Control\nPositioning Control\nModify Pipe - Select Head Position (Distance[0]) Snap:\nPositioning Control window\nPosition wrt World:\nPipe Editor: Modify Pipe\nFormat"}
{"Headers": "Position along Center Line", "Content": "If required, nudge the head direction, from the Position along center part of the Pipe Editor: Modify Pipe window. The nudge distance is controlled by the nudge increment which is set to 100mm by default.\nOr\nPick the head position along a selected center line, from the Position along center part of the Pipe Editor: Modify Pipe window, click\nPick head position along centre line\nDisplays the Positioning Control window. Refer to for further information.\nThe prompt Modify Pipe - Select Head Position (Distance[0]) Snap: is displayed.\n\nPick head position along centre line\nDisplays the Positioning Control window. Refer to for further information.\nThe prompt Modify Pipe - Select Head Position (Distance[0]) Snap: is displayed.\n\nPick head position along centre line\nDisplays the Positioning Control window. Refer to for further information.\nThe prompt Modify Pipe - Select Head Position (Distance[0]) Snap: is displayed.\n\n\n\nPosition\nPipe Editor: Modify Pipe\nPosition\nPipe Editor: Modify Pipe\nPick head position along centre line\nPositioning Control\n\nModify Pipe - Select Head Position (Distance[0]) Snap:"}
{"Headers": "Create Head Components", "Content": "Select the Create Head Components checkbox to create gasket/flanges at the head.\nClick Apply to create the head/tail.\n\n\n\nCreate Head Components\nApply"}
{"Headers": "Disconnect Pipe From Element", "Content": "As the functionality for the disconnection of the branch head or branch tail from an element is identical, for the purposes of this user guide, only the branch head disconnection is described.\nTo disconnect a branch head from an element, select the pipe or branch element in the Model Explorer.\nClick Set working pipe, to identify the element as the Current Element (CE), the attributes of the element are automatically populated in the Pipe Editor: Modify Pipe window.\nThe Branch Head tab of Pipe Editor: Modify Pipe window indicates that the selected branch head is connected.\nFrom the Branch Head tab of the Pipe Editor: Modify Pipe window, click Disconnect head to disconnect the branch head from the element it is connected to.\n\n\n\nSet working pipe\nPipe Editor: Modify Pipe\nBranch Head tab\nPipe Editor: Modify Pipe\nBranch Head\nPipe Editor: Modify Pipe\nDisconnect head"}
{"Headers": "Reconnect Pipe to Element", "Content": "As the functionality for re connection of the branch head or branch tail to an equipment element is identical, for the purposes of this user guide, only the branch head reconnect is described.\nTo reconnect a branch head to an equipment element, select the pipe or branch equipment element (that has been moved from its position) in the Model Explorer.\nClick Set working pipe, to identify the element as the Current Element (CE). The attributes of the element are automatically populated in the Pipe Editor: Modify Pipe window.\nThe Branch Head tab of Pipe Editor: Modify Pipe window indicates that the selected branch head is connected but requires reconnection.\n\nClick Reconnect to reconnect the branch head to the equipment element.\n\n\n\nModel Explorer\nSet working pipe\nPipe Editor: Modify Pipe\nBranch Head\nPipe Editor: Modify Pipe\nReconnect"}
{"Headers": "Connect Branch Head to Element", "Content": "As the functionality for the connection of the branch head or branch tail from an element is identical, for the purposes of this user guide, only the branch head connection is described.\nTo connect a branch head to an element, select the pipe or branch element in the Model Explorer.\nClick Set working pipe, to identify the element as the Current Element (CE), the attributes of the element are automatically populated in the Pipe Editor: Modify Pipe window.\nThe Branch Head tab of Pipe Editor: Modify Pipe window indicates that the selected branch head is undefined.\nFrom the Branch Head tab of the Pipe Editor: Modify Pipe window, click Pick item to connect head to, then Identify element to connect to:, select the element to connect to in the 3D graphical view.\nThe Connect to: field on the Branch Head tab is populated with the element name.\nThe List of connections: is populated and displays the connection status of each connection component.\n\nSelect a component from the List of Connections:.\nSelect a component or branch to which a connection cannot be made, a message displays on the 3D graphical view summarizing the problem, for example in the following window the element is already connected, only elements which are unconnected can be selected.\n\nSelect a component or branch to which a connection can be made, a message displays on the 3D graphical view highlighting the component, for example in the following window the component is available for connection.\n\nThe Connect functionality is only available for selection when the connection from the List of connections part of the Pipe Editor: Modify Pipe window is Unset.\n\nConnect the branch to the selected element in the List of Connections. Alternatively a connected branch can be disconnected from an element.\nConnect head to selected item\nConnects the branch head to the element, the window is populated with the attributes of the selected item.\nDisconnect connected branch\nDisconnects the connected branch from an element, click to display the Confirm window.\nClick Yes to disconnect the selected connection.\nClick No to discard any inputs and close the Confirm window.\n\nConnect head to selected item\nConnects the branch head to the element, the window is populated with the attributes of the selected item.\n\nDisconnect connected branch\nDisconnects the connected branch from an element, click to display the Confirm window.\n\nClick Yes to disconnect the selected connection.\nClick No to discard any inputs and close the Confirm window.\nOnce the branch head and branch tail has been defined or selected, the branch now consists of a single piece of pipe running between the branch head and branch tail. The branch displays a red dotted line, which means the branch route is geometrically incorrect a pipe run can now be created, refer to Quick Pipe Routing for further information.\nConnect head to selected item\nConnects the branch head to the element, the window is populated with the attributes of the selected item.\nDisconnect connected branch\nDisconnects the connected branch from an element, click to display the Confirm window.\nClick Yes to disconnect the selected connection.\nClick No to discard any inputs and close the Confirm window.\n\n\n\nQuick Pipe Routing\nSet working pipe\nPipe Editor: Modify Pipe\nBranch Head\nPipe Editor: Modify Pipe\nBranch Head\nPipe Editor: Modify Pipe\nPick item to connect head to\nIdentify element to connect to:,\nConnect to:\nBranch Head\nList of connections:\nList of Connections:\nList of connections\nPipe Editor: Modify Pipe\nUnset\nList of Connections\nConnect head to selected item\nDisconnect connected branch\nConfirm\nYes\nNo\nConfirm\nQuick Pipe Routing"}
{"Headers": "Quick Pipe Routing", "Content": "Quick Pipe Routing is used when:\nQuick Pipe Routing functionality is available through the Editor which is a mode of operation in Model which enables selection items in the graphical view to be reposition using the mouse.\nThe Quick Routing Handles are displayed at the head and tail of the ill-defined route. Ill-defined routes are where the Head or Tail of a Branch have defined but the route between has not. Once selected in the Editor mode the defined route is highlighted as blue.\n\nRight click on the defined route the quick routing handles and the item specific selection operations menu are displayed, refer to the Common guide (item-specific selection operations).\n\nCreate a pipe run between the head and tail of the branch, using the mouse, the quick routing handles and the options available from the quick pipe routing right click menu.\nA change of direction displays in the graphical view and the Model Explorer as an elbow or bend (dependent upon the specification). To make the choice of elbows or bends, right-click the cardinal direction handles to display the Editor menu.\n\n\nWhen using bends instead of elbows to reflect a change of direction, the default bend radius needs to be defined.\nFrom the quick pipe routing right click menu, select Component Choice > Set Default Bend Radius, the Bend Radius Choice window is displayed. The Current Branch is displayed and Bending Machine is selected as default.\nThe Bending Machine part of the Bend Radius Choice window indicates that the bending machine must be selected.\n\nOnce a bending machine has been selected from the list of available machines, the bendmac reference on either the branch, pipe or zone is assigned depending on the selected Set Owner Reference.\nA bending machine is automatically assigned to a zone, pipe or branch, using a bendmacref so that all bends will automatically be assigned a suitable bend radius to suit the assigned machine. The attribute is at pipe and branch because it is conceivable although unlikely that different branches may use different machines.\nA bendmacref is also used by pipe fabrication which manages pipe spools and ensures that the spool configuration will pass through the bending machine and can be manufactured. So a bendmacref is essential at the spooling phase if any of the branches contain spools\nAlternatively, the default radius can be defined using the Default Radius functionality, from the Bend Radius Choice window select Default Radius.\n\nThe default radius can be defined using two methods:\nBend Radius Factor - Use the bend radius factor to specify a factor which takes the current tube outside diameter and multiplies it by the factor available for selection from the Bend Radius Factor drop-down list. The bend radius factor is l then be used on all subsequent bends giving the appropriate radius according to their outside diameter.\nBend Radius - Explicitly enter a radius in the Bend Radius field, the bend radius is then be used on all subsequent bends giving the appropriate radius according to their outside diameter.\nTo automatically route multiple or single pipes orthogonally and with the minimum number of bends or elbows and where possible clash-free, refer to Pipe Router for further information.\nThe head and tail of the branch has been defined but the route between the two has not, for example: implied pipe is not shown. (ill defined route = dotted line). The mouse is used to define the direction of the pipe route, elbows or bends are automatically inserted when the route changes direction.\nBad alignment between two components, where the leave direction and arrive direction of adjacent elements do not match, (this can be due to the current design tolerance settings, for example: offset, angle and ratio).\nArrive or Leave where Head or Tail is undefined, where the end directly adjacent to a component is unset or ill-defined. An unset end is where the Head or Tail has its attributes left in the default state, whereas an ill-defined end is where, when the reference is set, the position is not with the reference item or when the end reference is not set, hence the end connection is unset.\nThe head and tail of the branch has been defined but the route between the two has not, for example: implied pipe is not shown. (ill defined route = dotted line). The mouse is used to define the direction of the pipe route, elbows or bends are automatically inserted when the route changes direction.\nThe head and tail of the branch has been defined but the route between the two has not, for example: implied pipe is not shown. (ill defined route = dotted line). The mouse is used to define the direction of the pipe route, elbows or bends are automatically inserted when the route changes direction.\nBad alignment between two components, where the leave direction and arrive direction of adjacent elements do not match, (this can be due to the current design tolerance settings, for example: offset, angle and ratio).\nBad alignment between two components, where the leave direction and arrive direction of adjacent elements do not match, (this can be due to the current design tolerance settings, for example: offset, angle and ratio).\nArrive or Leave where Head or Tail is undefined, where the end directly adjacent to a component is unset or ill-defined. An unset end is where the Head or Tail has its attributes left in the default state, whereas an ill-defined end is where, when the reference is set, the position is not with the reference item or when the end reference is not set, hence the end connection is unset.\nArrive or Leave where Head or Tail is undefined, where the end directly adjacent to a component is unset or ill-defined. An unset end is where the Head or Tail has its attributes left in the default state, whereas an ill-defined end is where, when the reference is set, the position is not with the reference item or when the end reference is not set, hence the end connection is unset.\nNote:\nAll the functionality available from the quick pipe routing right click menu is common throughout AVEVA E3D Design, refer to Common Functionality for further information. With the exception of Component Choice.\nNote:\nThe slope functionality is only available in the piping discipline, refer to Slope Pipe Window for further information.\nNote:\nTo check that a bend radius has bend defined correctly query the bend radius and also query dfbrad which is a pseudo attribute for the radius obtained from the bending machine (these values should be the same).\n\n\n\nSlope Pipe Window\nPipe Router\nQuick Routing Handles\nCommon guide\nModel Explorer\nEditor\nNote\n:\nCommon Functionality\nNote\n:\nSlope Pipe Window\nComponent Choice > Set Default Bend Radius\nBend Radius Choice\nCurrent Branch\nBending Machine\nBending Machine\nBend Radius Choice\nSet Owner Reference\nNote\n:\nDefault Radius\nBend Radius Choice\nDefault Radius\nBend Radius Factor\nBend Radius Factor\nBend Radius\nBend Radius\nPipe Router"}
{"Headers": "Slope", "Content": "Use the slope functionality to set the slope of a component\u2019s leave tube (using the p-leave ppoint) whilst using quick pipe router by specifying the required rate of fall or slope angle. Applies only to a component which involves a change of direction (such as an elbow).\n\nBy default, No Slope is selected (no slope will be applied to the pipe leg). To set the sloping angle, select Slope Angle, the Set Slope Angle window is displayed.\n\nEnter the sloping angle, click OK to apply the sloping angle, quick pipe router will route the pipe with the sloping angle or click Cancel to discard any inputs and close the window.\nNote:\nIf the default slope is set on a pipe or branch then extra functionality is available for selection, Default Slope Up and Default Slope Down. When selected, quick pipe router would route the pipe in accordance with the selected default slope.\n\n\n\nNo Slope\nSlope Angle\nSet Slope Angle\nOK\nCancel\nNote\n:\nDefault Slope Up\nDefault Slope Down"}
{"Headers": "Connect Branch Head to First Branch Member", "Content": "As the functionality for the connection of the branch head or branch tail from an element is identical, for the purposes of this user guide, only the branch head disconnection is described.\nTo connect the branch head to the first member in the branch hierarchy, select the branch equipment element in the Model Explorer.\nClick Set working pipe, to identify the element as the Current Element (CE), the attributes of the element are automatically populated in the Pipe Editor: Modify Pipe window.\nClick Connect head to first branch member to connect the branch head to the first member of the branch.\n\n\n\nModel Explorer\nSet working pipe\nPipe Editor: Modify Pipe\nConnect head to first branch member"}
{"Headers": "Create Other Branches", "Content": "To create a new branch under the pipe element identified as the CE, from the Pipe Editor: Modify Pipe window, click Create a new branch.\nA new branch is created in the Model Explorer and in the Connectivity part of the Pipe Editor: Modify Pipe window. Populate the Pipe Editor: Modify Pipe window with details and connections as required. Refer to Define Branch Head and Branch Tail for further information.\n\n\n\nDefine Branch Head and Branch Tail\nPipe Editor: Modify Pipe\nCreate a new branch\nConnectivity\nPipe Editor: Modify Pipe\nPipe Editor: Modify Pipe\nDefine Branch Head and Branch Tail"}
{"Headers": "Pipe Sketching", "Content": "Use the Pipe Sketching functionality to access design aids and tools to create a branch, insert components, copy and mirror piping components.\n\nAid Points\nUse the aid points functionality to create or add aid points to a branch. Aid points can also be deleted one at at time or at once.\nCreate Point\nUse to add aid points in the 3D graphical view.\nAdd (Insert) Point\nUse to add an additional aid point in the 3D graphical view.\nDelete\nUse to delete the last aid point from the 3D graphical view.\nDelete All Aid Points\nUse to delete all the aid points from the 3D graphical view.\n\nCreate Point\nUse to add aid points in the 3D graphical view.\n\nAdd (Insert) Point\nUse to add an additional aid point in the 3D graphical view.\n\nDelete\nUse to delete the last aid point from the 3D graphical view.\n\nDelete All Aid Points\nUse to delete all the aid points from the 3D graphical view.\nPosition Aid Points\nSelect an aid point from the Points drop down list, to view the frame, offset and world position of an aid point.\nUse the Orthogonal functionality to view the line between the aid points in the 3D graphical view as orthogonal.\nUse the Offset functionality to offset an aid point in the 3D graphical view.\n\nCreate Branch\nUse aid points to create a new branch in the 3D graphical view. The new branch attributes are based on the currently selected branch in the hierarchy. Depending upon the configuration of the aid points, a Choose window is displayed listing a selection of piping components.\nIf an intersection between the aid points and the currently selected branch exists, the new branch is added to the current branch.\nIf required the new branch can be created at an offset distance from the currently selected branch.\nInsert Flange Set\nUse to create a flange set at the intersection of an aid point line and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A series of Choose window are displayed listing the available flanges and gaskets. The flange set is then added to the branch at the intersection with the aid point\nInsert Valve Set\nUse to create a valve set at the intersection of an aid point and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A series of Choose window are displayed listing the available flanges, gasket and valves. The valve set is then added to the branch at the intersection with the aid point.\nInsert Expansion Loop\nUse to create an expansion loop at the intersection of an aid point line and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A Choose window is displayed listing the available elbows. The expansion loop is then added to the branch at the intersection with the aid point.\nInsert Bypass\nUse to create a bypass at the intersection of an aid point line and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A series of CHOOSE window are displayed listing the available tees and elbows. The expansion loop is then added to the branch at the intersection with the aid point.\nCopy Selection\nUse to copy one or more branch elements and position them at a new location in the currently selected branch (Make sure that all the components are connected and there are no unwanted components).\nNote:\nThe source branch component is usually the origin component from the selection.\nCopying and inserting components into branches at an angle to the copied elements is not supported. Where possible the application tries to build the copy correctly but most copied elements retain the orientation of the original.\n\nCreate Branch\nUse aid points to create a new branch in the 3D graphical view. The new branch attributes are based on the currently selected branch in the hierarchy. Depending upon the configuration of the aid points, a Choose window is displayed listing a selection of piping components.\nIf an intersection between the aid points and the currently selected branch exists, the new branch is added to the current branch.\nIf required the new branch can be created at an offset distance from the currently selected branch.\n\nInsert Flange Set\nUse to create a flange set at the intersection of an aid point line and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A series of Choose window are displayed listing the available flanges and gaskets. The flange set is then added to the branch at the intersection with the aid point\n\nInsert Valve Set\nUse to create a valve set at the intersection of an aid point and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A series of Choose window are displayed listing the available flanges, gasket and valves. The valve set is then added to the branch at the intersection with the aid point.\n\nInsert Expansion Loop\nUse to create an expansion loop at the intersection of an aid point line and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A Choose window is displayed listing the available elbows. The expansion loop is then added to the branch at the intersection with the aid point.\n\nInsert Bypass\nUse to create a bypass at the intersection of an aid point line and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A series of CHOOSE window are displayed listing the available tees and elbows. The expansion loop is then added to the branch at the intersection with the aid point.\n\nCopy Selection\nUse to copy one or more branch elements and position them at a new location in the currently selected branch (Make sure that all the components are connected and there are no unwanted components).\nCopying and inserting components into branches at an angle to the copied elements is not supported. Where possible the application tries to build the copy correctly but most copied elements retain the orientation of the original.\n\nCreate Point\nUse to add aid points in the 3D graphical view.\nAdd (Insert) Point\nUse to add an additional aid point in the 3D graphical view.\nDelete\nUse to delete the last aid point from the 3D graphical view.\nDelete All Aid Points\nUse to delete all the aid points from the 3D graphical view.\nCreate Branch\nUse aid points to create a new branch in the 3D graphical view. The new branch attributes are based on the currently selected branch in the hierarchy. Depending upon the configuration of the aid points, a Choose window is displayed listing a selection of piping components.\nIf an intersection between the aid points and the currently selected branch exists, the new branch is added to the current branch.\nIf required the new branch can be created at an offset distance from the currently selected branch.\nInsert Flange Set\nUse to create a flange set at the intersection of an aid point line and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A series of Choose window are displayed listing the available flanges and gaskets. The flange set is then added to the branch at the intersection with the aid point\nInsert Valve Set\nUse to create a valve set at the intersection of an aid point and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A series of Choose window are displayed listing the available flanges, gasket and valves. The valve set is then added to the branch at the intersection with the aid point.\nInsert Expansion Loop\nUse to create an expansion loop at the intersection of an aid point line and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A Choose window is displayed listing the available elbows. The expansion loop is then added to the branch at the intersection with the aid point.\nInsert Bypass\nUse to create a bypass at the intersection of an aid point line and an existing branch. Once the selection of the intersecting pipe in the 3D graphical view has been made, A series of CHOOSE window are displayed listing the available tees and elbows. The expansion loop is then added to the branch at the intersection with the aid point.\nCopy Selection\nUse to copy one or more branch elements and position them at a new location in the currently selected branch (Make sure that all the components are connected and there are no unwanted components).\nNote:\nThe source branch component is usually the origin component from the selection.\nCopying and inserting components into branches at an angle to the copied elements is not supported. Where possible the application tries to build the copy correctly but most copied elements retain the orientation of the original.\nNote:\nThe source branch component is usually the origin component from the selection.\n\n\n\nthe Pipe Sketching\nAid Points\nCreate Point\nAdd (Insert) Point\nDelete\nDelete All Aid Points\nPosition Aid Points\nPoints\nOrthogonal\nOffset\nCreate Branch\nChoose\nInsert Flange Set\nChoose\nInsert Valve Set\nChoose\nInsert Expansion Loop\nChoose\nInsert Bypass\nCHOOSE\nCopy Selection\nNote\n:"}
{"Headers": "Mirror Component Selection", "Content": "Use the Mirror Component Selection functionality to mirror an existing branch element.\nDirection\nUse to enter a direction for the mirror into the Direction field. Once an element has been picked in the 3D graphical view, a mirror plane is displayed in the 3D graphical view.\nPick Mirror Direction\nUse the Pick Mirror Direction functionality to pick a direction in the 3D graphical view. After a element has been picked in the 3D graphical view, a mirror plane is displayed in the 3D graphical view.\nPick Mirror Position\nUse to pick a mirror position in the 3D graphical view. Once selected the Positioning Control toolbar is displayed. Use its functionality to position the mirror plane.\nUse Bends instead of Elbows\nReplaces bends instead of elbows in the 3D graphical view.\n\nDirection\nUse to enter a direction for the mirror into the Direction field. Once an element has been picked in the 3D graphical view, a mirror plane is displayed in the 3D graphical view.\n\nPick Mirror Direction\nUse the Pick Mirror Direction functionality to pick a direction in the 3D graphical view. After a element has been picked in the 3D graphical view, a mirror plane is displayed in the 3D graphical view.\n\nPick Mirror Position\nUse to pick a mirror position in the 3D graphical view. Once selected the Positioning Control toolbar is displayed. Use its functionality to position the mirror plane.\n\nUse Bends instead of Elbows\nReplaces bends instead of elbows in the 3D graphical view.\n\nDirection\nUse to enter a direction for the mirror into the Direction field. Once an element has been picked in the 3D graphical view, a mirror plane is displayed in the 3D graphical view.\nPick Mirror Direction\nUse the Pick Mirror Direction functionality to pick a direction in the 3D graphical view. After a element has been picked in the 3D graphical view, a mirror plane is displayed in the 3D graphical view.\nPick Mirror Position\nUse to pick a mirror position in the 3D graphical view. Once selected the Positioning Control toolbar is displayed. Use its functionality to position the mirror plane.\nUse Bends instead of Elbows\nReplaces bends instead of elbows in the 3D graphical view.\n\n\n\nMirror Component Selection\nDirection\nDirection\nPick Mirror Direction\nPick Mirror Direction\nPick Mirror Position\nPositioning Control\nUse Bends instead of Elbows"}
{"Headers": "Pipework Components", "Content": "Pipework components are assemblies and single pieces of pipe used together to create a Pipework design.\nIt is usual to build up the pipework design by adding components sequentially, starting at the branch head and positioning and orientating each component as they proceed until the branch tail is reached. Insert a component into existing sequence by navigating to the component immediately before the required location and then creating the new component.\nThere are many different combinations of the pipework that can be created, because of this the Piping discipline uses a common layout for windows that are presented. The information can be applied to the same processes that are used to create all other types of Pipework components.\n\n\n"}
{"Headers": "Component Creation", "Content": "Referring to the , a pipework component must reside below an existing pipe branch element. Refer to Branch Element for a more detailed explanation of creating a pipework branch.\n\nIf the Current Element (CE) in the Model Explorer is not at the branch level, an error message is displayed summarizing the problem, for example in the following window an error explains that the element must reside below a branch or component element.\nSelect the correct branch element from the Model Explorer and click Set working pipe to display the Piping Component Editor window.\n\nThe Piping Component element(s) are owned by branch elements, these components dictate the shape and geometry of the pipework. Piping components can run from head to tail of the owning branch but can also be connected to other branches.\n\n\n\n\n\n\n\n\n\nHull Routing\n\n\n\nBranch Element\nHull Routing\n\nBranch Element\nModel Explorer\nModel Explorer\nSet working pipe\nPiping Component Editor\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nHull Routing"}
{"Headers": "Branch Specification", "Content": "The Spec:, Bore: and Branch Slope: of the currently selected pipe displays at the top of the window.\nSelect a different specification for the component, the branch specification is initially selected but an alternative specification can be selected.\nSelect a specification from the Select From Spec drop-down list. If a specification is selected that does not match the pipe specification, the Piping Component Editor window displays a Select Out of Spec message.\n\nClick Spec: to return the Select From Spec drop-down list to the current branch specification.\nSelect an insulation specification from the Insulation drop-down list. If no insulation is required, select None. (If a new specification is required, refer to the system administrator).\nSelect a tracing from the Tracing drop-down list. If no tracing is required, select None. (If a new specification is required, refer to the system administrator).\n\n\n\nSpec:\nBore:\nBranch Slope:\nSelect From Spec\nthe Piping Component Editor\nSelect Out of Spec\nSpec:\nSelect From Spec\nInsulation\nNone\nTracing\nNone"}
{"Headers": "Standard Components", "Content": "The Standard Components tab (displayed as default) provides quick access to the more commonly used components.\n\nThe Select tab displays all of the components available for selection from the catalog under the currently selected component and piping specification.\n\nFlange\nDisplays a list of available Flanges.\nElbow\nDisplays a list of available Elbows.\nTee\nDisplays a list of available Tees.\nReducer\nDisplays a list of available Reducers.\nValve\nDisplays a list of available Valves.\nAttachment\nDisplays a list of available Attachments.\nPcom\nDisplays a list of available Pcoms.\nWeld\nDisplays a list of available Welds.\nPipe Bend\nDisplays a list of available Pipe Bends.\nOlet\nDisplays a list of available Olets.\nCoupling\nDisplays a list of available Couplings.\nInstrument\nDisplays a list of available Instruments.\nCap\nDisplays a list of available Caps.\nGasket\nDisplays a list of available Gaskets.\n\nFlange\nDisplays a list of available Flanges.\n\nElbow\nDisplays a list of available Elbows.\n\nTee\nDisplays a list of available Tees.\n\nReducer\nDisplays a list of available Reducers.\n\nValve\nDisplays a list of available Valves.\n\nAttachment\nDisplays a list of available Attachments.\n\nPcom\nDisplays a list of available Pcoms.\n\nWeld\nDisplays a list of available Welds.\n\nPipe Bend\nDisplays a list of available Pipe Bends.\n\nOlet\nDisplays a list of available Olets.\n\nCoupling\nDisplays a list of available Couplings.\n\nInstrument\nDisplays a list of available Instruments.\n\nCap\nDisplays a list of available Caps.\n\nGasket\nDisplays a list of available Gaskets.\nAdditional Components\nThe Additional Components tab provides quick access to further components\n\nFilter\nDisplays a list of available Filters.\nCross\nDisplays a list of available Crosses.\nUnion\nDisplays a list of available Unions.\nThree Way Valve\nDisplays a list of available Three Way Valves.\nClosure\nDisplays a list of available Closures.\nBlind Flange\nDisplays a list of available Blind Flanges.\nTrap\nDisplays a list of available Traps.\nLap Joint Stub End\nDisplays a list of available Lap Joint Stub Ends.\nFixed Length Tube\nDisplays a list of available Fixed Length Tubes.\nFour Way Valve\nDisplays a list of available Four Way Valves.\nSHU\nDisplays a list of available SHUs.\nPlate\nDisplays a list of available Plates.\nAssembly\nDisplays a list of available Assemblies.\n\nFilter\nDisplays a list of available Filters.\n\nCross\nDisplays a list of available Crosses.\n\nUnion\nDisplays a list of available Unions.\n\nThree Way Valve\nDisplays a list of available Three Way Valves.\n\nClosure\nDisplays a list of available Closures.\n\nBlind Flange\nDisplays a list of available Blind Flanges.\n\nTrap\nDisplays a list of available Traps.\n\nLap Joint Stub End\nDisplays a list of available Lap Joint Stub Ends.\n\nFixed Length Tube\nDisplays a list of available Fixed Length Tubes.\n\nFour Way Valve\nDisplays a list of available Four Way Valves.\n\nSHU\nDisplays a list of available SHUs.\n\nPlate\nDisplays a list of available Plates.\n\nAssembly\nDisplays a list of available Assemblies.\nThe Select tab displays all of the additional components available for selection from the catalog under the currently selected piping specification.\nIf the selected component is not available from the catalog an Error window displays.\n\nClick OK to select another component.\nFlange\nDisplays a list of available Flanges.\nElbow\nDisplays a list of available Elbows.\nTee\nDisplays a list of available Tees.\nReducer\nDisplays a list of available Reducers.\nValve\nDisplays a list of available Valves.\nAttachment\nDisplays a list of available Attachments.\nPcom\nDisplays a list of available Pcoms.\nWeld\nDisplays a list of available Welds.\nPipe Bend\nDisplays a list of available Pipe Bends.\nOlet\nDisplays a list of available Olets.\nCoupling\nDisplays a list of available Couplings.\nInstrument\nDisplays a list of available Instruments.\nCap\nDisplays a list of available Caps.\nGasket\nDisplays a list of available Gaskets.\nFilter\nDisplays a list of available Filters.\nCross\nDisplays a list of available Crosses.\nUnion\nDisplays a list of available Unions.\nThree Way Valve\nDisplays a list of available Three Way Valves.\nClosure\nDisplays a list of available Closures.\nBlind Flange\nDisplays a list of available Blind Flanges.\nTrap\nDisplays a list of available Traps.\nLap Joint Stub End\nDisplays a list of available Lap Joint Stub Ends.\nFixed Length Tube\nDisplays a list of available Fixed Length Tubes.\nFour Way Valve\nDisplays a list of available Four Way Valves.\nSHU\nDisplays a list of available SHUs.\nPlate\nDisplays a list of available Plates.\nAssembly\nDisplays a list of available Assemblies.\n\n\n\nStandard Components\nSelect\nAdditional Components\nFilter\nCross\nUnion\nThree Way Valve\nClosure\nBlind Flange\nTrap\nLap Joint Stub End\nFixed Length Tube\nFour Way Valve\nSHU\nPlate\nAssembly\nSelect\nError\nOK"}
{"Headers": "Component Information", "Content": "The component information part of the Piping Component Editor window displays information specific (if relevant) to the selected standard or additional component.\n\n\n\nPiping Component Editor"}
{"Headers": "Flange", "Content": "Click Flange from the Standard Components tab to display the Reducing Flange Information in the Piping Component Editor window.\n\nThe Leave Bore drop-down list is not used for a flange.\nArrive major bore leave minor bore\nSets the orientation of the flange to arrive at a major bore and leave at a minor bore.\nArrive minor bore leave major bore\nSets the orientation of the flange to arrive at a minor bore and leave at a major bore.\n\nArrive major bore leave minor bore\nSets the orientation of the flange to arrive at a major bore and leave at a minor bore.\n\nArrive minor bore leave major bore\nSets the orientation of the flange to arrive at a minor bore and leave at a major bore.\n\nArrive major bore leave minor bore\nSets the orientation of the flange to arrive at a major bore and leave at a minor bore.\nArrive minor bore leave major bore\nSets the orientation of the flange to arrive at a minor bore and leave at a major bore.\n\n\n\nFlange\nStandard Components\nReducing Flange Information\nPiping Component Editor\nLeave Bore\nArrive major bore leave minor bore\nArrive minor bore leave major bore"}
{"Headers": "Elbow", "Content": "Click Elbow from the Standard Components tab to display the Elbow Information in the Piping Component Editor window.\n\nAngle\nSets the angle of the elbow.\nMin\nSets the minimum angle for the elbow.\nMax\nSets the maximum angle for the elbow.\nAngle\nSets the angle of the elbow.\nMin\nSets the minimum angle for the elbow.\nMax\nSets the maximum angle for the elbow.\n\nAngle\nSets the angle of the elbow.\nMin\nSets the minimum angle for the elbow.\nMax\nSets the maximum angle for the elbow.\n\n\n\nElbow\nStandard Components\nElbow Information\nPiping Component Editor\nAngle\nMin\nMax"}
{"Headers": "Tee", "Content": "Click Tee from the Standard Components tab to display the Connection Information in the Piping Component Editor window.\n\nSelect a value from the Conn Bore drop-down list.\nFlow through tee\nSets the flow direction through the tee.\nLeave by connection\nSets the flow direction to leave by the connection point.\nArrive by connection\nSets the flow direction to arrive at the connection point.\n\nFlow through tee\nSets the flow direction through the tee.\n\nLeave by connection\nSets the flow direction to leave by the connection point.\n\nArrive by connection\nSets the flow direction to arrive at the connection point.\n\nFlow through tee\nSets the flow direction through the tee.\nLeave by connection\nSets the flow direction to leave by the connection point.\nArrive by connection\nSets the flow direction to arrive at the connection point.\n\n\n\nTee\nStandard Components\nConnection Information\nPiping Component Editor\nConn Bore\nFlow through tee\nLeave by connection\nArrive by connection"}
{"Headers": "Reducer", "Content": "Click Reducer from the Standard Components tab to display the Reducer Information in the Piping Component Editor window.\n\nSelect a value from the Leave Bore drop-down list.\nArrive major bore leave minor bore\nSets the orientation of the reducer to arrive at a major bore and leave at a minor bore.\nArrive minor bore leave major bore\nSets the orientation of the reducer to arrive at a minor bore and leave at a major bore.\n\nArrive major bore leave minor bore\nSets the orientation of the reducer to arrive at a major bore and leave at a minor bore.\n\nArrive minor bore leave major bore\nSets the orientation of the reducer to arrive at a minor bore and leave at a major bore.\n\nArrive major bore leave minor bore\nSets the orientation of the reducer to arrive at a major bore and leave at a minor bore.\nArrive minor bore leave major bore\nSets the orientation of the reducer to arrive at a minor bore and leave at a major bore.\n\n\n\nReducer\nStandard Components\nReducer Information\nPiping Component Editor\nLeave Bore\nArrive major bore leave minor bore\nArrive minor bore leave major bore"}
{"Headers": "Bend", "Content": "Click Bend from the Standard Components tab to display the Bend Information in the Piping Component Editor window. The bend radius is calculated using the components OD and NB.\n\nSelect a value from the Radius drop-down list.\nSelect Define from the Radius drop-down list to input a bend dimension.\n\n\n\nBend\nStandard Components\nBend Information\nPiping Component Editor\nRadius\nDefine\nRadius"}
{"Headers": "Olet", "Content": "Click Olet from the Standard Components tab to display the Connection Information in the Piping Component Editor window.\n\nSelect a value from the Conn Bore drop-down list.\nFlow through tee\nSets the flow direction through the tee.\nLeave by connection\nSets the flow direction to leave by the connection point.\nArrive by connection\nSets the flow direction to arrive at the connection point.\n\nFlow through tee\nSets the flow direction through the tee.\n\nLeave by connection\nSets the flow direction to leave by the connection point.\n\nArrive by connection\nSets the flow direction to arrive at the connection point.\n\nFlow through tee\nSets the flow direction through the tee.\nLeave by connection\nSets the flow direction to leave by the connection point.\nArrive by connection\nSets the flow direction to arrive at the connection point.\n\n\n\nOlet\nStandard Components\nConnection Information\nPiping Component Editor\nConn Bore\nFlow through tee\nLeave by connection\nArrive by connection"}
{"Headers": "Coupling", "Content": "Click Coupling from the Standard Components tab to display the Reducing Coupling Information in the Piping Component Editor window.\n\nSelect a value from the Leave Bore drop-down list.\nArrive major bore leave minor bore\nSets the orientation of the coupling to arrive at a major bore and leave at a minor bore.\nArrive minor bore leave major bore\nSets the orientation of the coupling to arrive at a minor bore and leave at a major bore.\n\nArrive major bore leave minor bore\nSets the orientation of the coupling to arrive at a major bore and leave at a minor bore.\n\nArrive minor bore leave major bore\nSets the orientation of the coupling to arrive at a minor bore and leave at a major bore.\n\nArrive major bore leave minor bore\nSets the orientation of the coupling to arrive at a major bore and leave at a minor bore.\nArrive minor bore leave major bore\nSets the orientation of the coupling to arrive at a minor bore and leave at a major bore.\n\n\n\nCoupling\nStandard Components\nReducing Coupling Information\nPiping Component Editor\nLeave Bore\nArrive major bore leave minor bore\nArrive minor bore leave major bore"}
{"Headers": "Assembly", "Content": "Click Assembly from the Additional Components tab to display the Assemblies part of the Piping Component Editor window.\n\nChoose from a list of available assemblies in the Available sub-types for component drop-down list. The assemblies available for selection are those already created in the catalog, if the required assembly is not included, refer to the system administrator.\n\n\n\nAssembly\nAdditional Components\nAssemblies\nPiping Component Editor"}
{"Headers": "Create Mode", "Content": "Use the Create Mode part of the Piping Component Editor window to set the direction of flow, the software creates the component in the Head to Tail direction by default.\n\nCreate components in the flow direction\nCreates the component in the Head to Tail direction.\nCreate components against the flow direction\nCreates the component in the Tail to Head direction.\n\nCreate components in the flow direction\nCreates the component in the Head to Tail direction.\n\nCreate components against the flow direction\nCreates the component in the Tail to Head direction.\nIf the Auto. Create check box is selected, the software automatically determines if there is a requirement for an associated component (on a valve, the associated component would be a flange and gasket) and if so, what is the appropriate.\nIf the Out of Spec check box is selected, an alternative specification component can be used.\nIf the Skip Connected Comps check box is selected, the pipework application automatically determines which components are connected, then positions the creation point approximately.\nCreate components in the flow direction\nCreates the component in the Head to Tail direction.\nCreate components against the flow direction\nCreates the component in the Tail to Head direction.\n\n\n\nCreate Mode\nPiping Component Editor\nCreate components in the flow direction\nCreate components against the flow direction\nAuto. Create\nOut of Spec\nSkip Connected Comps"}
{"Headers": "Create Component", "Content": "Use the Create Components part of the Piping Component Editor window to connect or place the component.\nCreate component connected to previous\nConnects the component to the previous one or branch head/tail.\nCreate Component at picked position\nPositions the component at the point selected in the 3D graphical view.\nIdentify the branch leg for the component on the 3D graphical view, for example identify branch leg for Elbow: displays when an elbow is the selected component.\n\nCreate component connected to previous\nConnects the component to the previous one or branch head/tail.\n\nCreate Component at picked position\nPositions the component at the point selected in the 3D graphical view.\nIdentify the branch leg for the component on the 3D graphical view, for example identify branch leg for Elbow: displays when an elbow is the selected component.\n\nCreate component connected to previous\nConnects the component to the previous one or branch head/tail.\nCreate Component at picked position\nPositions the component at the point selected in the 3D graphical view.\nIdentify the branch leg for the component on the 3D graphical view, for example identify branch leg for Elbow: displays when an elbow is the selected component.\n\n\n\nCreate Components\nPiping Component Editor\nCreate component connected to previous\nCreate Component at picked position\nidentify branch leg for Elbow:"}
{"Headers": "Create Assemblies", "Content": "Use the Create Assemblies part of the Piping Component Editor window to connect or place the assembly.\nCreate assembly connected to previous\nConnects the assembly to the previous one or branch head/tail.\nCreate component in line at picked position.\nPositions the assembly at the point selected in the 3D graphical view.\nIdentify an insertion point in tube on the 3D graphical view.\nCreate component at 3D picked position\nInserts a new component after the current element in the branch Its position is determined by selection a position in the 3D graphical view. Once a selection has been made, the model editor is displayed for further positioning.\nFlip orientation of new components\nUse to flip the orientation of the new component.\n\nCreate assembly connected to previous\nConnects the assembly to the previous one or branch head/tail.\n\nCreate component in line at picked position.\nPositions the assembly at the point selected in the 3D graphical view.\nIdentify an insertion point in tube on the 3D graphical view.\n\nCreate component at 3D picked position\nInserts a new component after the current element in the branch Its position is determined by selection a position in the 3D graphical view. Once a selection has been made, the model editor is displayed for further positioning.\n\nFlip orientation of new components\nUse to flip the orientation of the new component.\n\nCreate assembly connected to previous\nConnects the assembly to the previous one or branch head/tail.\nCreate component in line at picked position.\nPositions the assembly at the point selected in the 3D graphical view.\nIdentify an insertion point in tube on the 3D graphical view.\nCreate component at 3D picked position\nInserts a new component after the current element in the branch Its position is determined by selection a position in the 3D graphical view. Once a selection has been made, the model editor is displayed for further positioning.\nFlip orientation of new components\nUse to flip the orientation of the new component.\n\n\n\nCreate Assemblies\nPiping Component Editor\nCreate assembly connected to previous\nCreate component in line at picked position.\nCreate component at 3D picked position\nFlip orientation of new components"}
{"Headers": "Component Sequence List", "Content": "Use the Component Sequence List part of the Piping component Editor, to scroll through and select individual components within the currently selected branch.\n\nThe Current Element (CE) is highlighted in the center of the Component Sequence List, if required select another component in the sequence list.\nMoves the start of the Component Sequence List.\nMoves one component to the left of the Component Sequence List.\nMoves one component to the right of the Component Sequence List.\nMoves to the end of the Component Sequence List.\n\nMoves the start of the Component Sequence List.\n\nMoves one component to the left of the Component Sequence List.\n\nMoves one component to the right of the Component Sequence List.\n\nMoves to the end of the Component Sequence List.\n\nMoves the start of the Component Sequence List.\nMoves one component to the left of the Component Sequence List.\nMoves one component to the right of the Component Sequence List.\nMoves to the end of the Component Sequence List.\nNote:\nThe sequence direction is determined by the routing direction, refer to for further information.\n\n\n\nComponent Sequence List\nPiping component Editor\nComponent Sequence List,\nNote\n:\n"}
{"Headers": "Route Pipe Components", "Content": "To continue routing pipework, select the component from the chosen specification, then position and set orientation using the Editor, (refer to Editor for further information).\nThe tube is not created explicitly, it is created automatically and implied between adjacent components. The tube is not displayed in the Model Explorer.\n\nThe tube is implied on the 3D graphical view:\n\n\n\n\nEditor\nModel Explorer"}
{"Headers": "Modify Piping Components", "Content": "Piping components, their orientation and/or position can be modified.\n\n\n\n\n"}
{"Headers": "Position Through", "Content": "Use the Position Through part of the Piping Component Editor window to adjust the position of a component.\n\nPosition through branch head\nAligns a component through the branch head.\nPosition through previous element\nAligns a component through the previous component of the branch assembly.\nPosition current element (align with previous)\nAligns a component with the previous component of the branch assembly.\nPosition through next component\nAligns a component through the next component of the branch assembly.\nPosition through branch tail\nAligns a component through the branch head.\nPosition through a cursor pick\nInitiates the same functionality as that available from the Align with Feature on the Model Editor Handle. Refer to for further information.\nPosition With Offset ON/OFF\nThis is a toggle button to specify whether to align a component with or without an offset.\nNote:\nIf this button is switched on, the Offset From Feature window is displayed when Position through a cursor pick is clicked.\nDistance - Click to use Clearance\nDisplays the actual clearance, to change the clearance input a new value into the text field then press Enter. To modify the distance, click the Distance - Click to use Clearance toggle, refer to for further information.\nDistance - Click to use Distance\nDisplays the actual distance from the previous component, to change the distance input a new value into the text field then press Enter.\nCopy current component\nCopies the currently selected component.\nConnect to previous component\nConnects the piping component to the previous piping component.\n\nPosition through branch head\nAligns a component through the branch head.\n\nPosition through previous element\nAligns a component through the previous component of the branch assembly.\n\nPosition current element (align with previous)\nAligns a component with the previous component of the branch assembly.\n\nPosition through next component\nAligns a component through the next component of the branch assembly.\n\nPosition through branch tail\nAligns a component through the branch head.\n\nPosition through a cursor pick\nInitiates the same functionality as that available from the Align with Feature on the Model Editor Handle. Refer to for further information.\n\nPosition With Offset ON/OFF\nThis is a toggle button to specify whether to align a component with or without an offset.\n\n\nDistance - Click to use Clearance\nDisplays the actual clearance, to change the clearance input a new value into the text field then press Enter. To modify the distance, click the Distance - Click to use Clearance toggle, refer to for further information.\n\nDistance - Click to use Distance\nDisplays the actual distance from the previous component, to change the distance input a new value into the text field then press Enter.\n\nCopy current component\nCopies the currently selected component.\n\nConnect to previous component\nConnects the piping component to the previous piping component.\n\nPosition through branch head\nAligns a component through the branch head.\nPosition through previous element\nAligns a component through the previous component of the branch assembly.\nPosition current element (align with previous)\nAligns a component with the previous component of the branch assembly.\nPosition through next component\nAligns a component through the next component of the branch assembly.\nPosition through branch tail\nAligns a component through the branch head.\nPosition through a cursor pick\nInitiates the same functionality as that available from the Align with Feature on the Model Editor Handle. Refer to for further information.\nPosition With Offset ON/OFF\nThis is a toggle button to specify whether to align a component with or without an offset.\nNote:\nIf this button is switched on, the Offset From Feature window is displayed when Position through a cursor pick is clicked.\nDistance - Click to use Clearance\nDisplays the actual clearance, to change the clearance input a new value into the text field then press Enter. To modify the distance, click the Distance - Click to use Clearance toggle, refer to for further information.\nDistance - Click to use Distance\nDisplays the actual distance from the previous component, to change the distance input a new value into the text field then press Enter.\nCopy current component\nCopies the currently selected component.\nConnect to previous component\nConnects the piping component to the previous piping component.\nNote:\nIf this button is switched on, the Offset From Feature window is displayed when Position through a cursor pick is clicked.\n\n\n\nPosition Through\nPiping Component Editor\nPosition through branch head\nPosition through previous element\nPosition current element (align with previous)\nPosition through next component\nPosition through branch tail\nPosition through a cursor pick\nAlign with Feature\n\nPosition With Offset ON/OFF\nNote\n:\nOffset From Feature\nPosition through a cursor\npick\nDistance - Click to use Clearance\nDistance - Click to use Clearance\n\nDistance - Click to use Distance\nCopy current component\nConnect to previous component"}
{"Headers": "Component Routing Direction", "Content": "The component routing direction can be reversed during component modification.\nChange to backwards mode\nChanges the routing direction from Tail to Head.\nChange to forwards mode\nChanges the routing direction from Head to Tail.\n\nChange to backwards mode\nChanges the routing direction from Tail to Head.\n\nChange to forwards mode\nChanges the routing direction from Head to Tail.\n\nChange to backwards mode\nChanges the routing direction from Tail to Head.\nChange to forwards mode\nChanges the routing direction from Head to Tail.\n\n\n\nChange to backwards mode\nChange to forwards mode"}
{"Headers": "3D Compass", "Content": "The 3D Compass part of the Piping Component Editor window can be used in two ways depending upon the type of component selected. By default, the Direction Tool is displayed as default.\nDirection Tool: the direction of elbows and bends can be changed.\nRotation Tool: tees and other non-symmetrical components such as valves or reducers can be rotated.\n\n\n\n\n3D\nCompass\nPiping Component Editor\nDirection Tool\nDirection Tool\nRotation Tool:"}
{"Headers": "Component Direction", "Content": "Use the Direct Component view displays a compass which to set the orthogonal direction of a component using the direction arrows and the direction plane selector of the compass.\n\nTo direct a component, select an outer arrow from the direction tool. For example, click the outer arrow W to direct a component to face the W axes.\nDirection ISO View\nUse the right click menu from the Direction Display part of the Create/Modify Pipe Component window to define the ISO view and coordinate system.\nRotate Component\nUse to rotate the component, refer to Rotation Tool for further information.\nSlope\nUse to set the current slope to up or down, refer to Slope Pipe Window for further information.\nReturn to default direction (also an Esc key)\nUse to return the component to the default direction. To modify the default direction, refer to Piping Defaults for further information.\nDirection field\nUse to input a desired direction in the Direction field, for example, input E in the Direction field to set the orthogonal direction of the component to face the E axes.\nMulti slope\nUse the Multi Slope check box, to add a slope to the orthogonal direction of the component or orientate the component about a selected p-point. Refer to for further information.\n\nDirection ISO View\nUse the right click menu from the Direction Display part of the Create/Modify Pipe Component window to define the ISO view and coordinate system.\n\nRotate Component\nUse to rotate the component, refer to Rotation Tool for further information.\n\nSlope\nUse to set the current slope to up or down, refer to Slope Pipe Window for further information.\n\nReturn to default direction (also an Esc key)\nUse to return the component to the default direction. To modify the default direction, refer to Piping Defaults for further information.\nDirection field\nUse to input a desired direction in the Direction field, for example, input E in the Direction field to set the orthogonal direction of the component to face the E axes.\nMulti slope\nUse the Multi Slope check box, to add a slope to the orthogonal direction of the component or orientate the component about a selected p-point. Refer to for further information.\nTo direct the component using a direction plane, click the Direction Plane Selector of the direction tool to set the direction plane. For example, click the top right section of the Direction Plane Selector to change the direction plane. The direction plane displayed depends upon the original orientation of the component.\n\nDirect a component 360 degrees through Up-East, East-Down, Down-West and West-up. The default rotation angle is 15 degrees.\n\nDirection ISO View\nUse the right click menu from the Direction Display part of the Create/Modify Pipe Component window to define the ISO view and coordinate system.\nRotate Component\nUse to rotate the component, refer to Rotation Tool for further information.\nSlope\nUse to set the current slope to up or down, refer to Slope Pipe Window for further information.\nReturn to default direction (also an Esc key)\nUse to return the component to the default direction. To modify the default direction, refer to Piping Defaults for further information.\nDirection field\nUse to input a desired direction in the Direction field, for example, input E in the Direction field to set the orthogonal direction of the component to face the E axes.\nMulti slope\nUse the Multi Slope check box, to add a slope to the orthogonal direction of the component or orientate the component about a selected p-point. Refer to for further information.\n\n\n\nSlope Pipe Window\nPiping Defaults\nDirect Component\nDirection ISO View\nDirection Display\nCreate/Modify Pipe Component\nRotate Component\nRotation Tool\nSlope\nSlope Pipe Window\nReturn to default direction (also an Esc key)\nPiping Defaults\nDirection field\nDirection\nE\nDirection\nMulti slope\nMulti Slope\n\nDirection Plane Selector\nDirection Plane Selector"}
{"Headers": "Slope", "Content": "Sloped components are components where a ppoint has its offset tolerance set in the catalog. The offset tolerance is a maximum angle to which a weld may be shaped to change the direction of flow. The slope is stored as an attribute called slopedir and as a direction.\nIf required, add a slope to the orthogonal direction of the component, from the 3D compass view, click Set the current slope to Up or Down.\n\nFrom the displayed menu, select:\nNo slope\nAdds no slope to the orthogonal direction of the component.\nSlope down\nAdds a downwards slope to the orthogonal direction of the component.\nSlope Up\nAdd an upwards slope to the orthogonal direction of the component.\nNo slope\nAdds no slope to the orthogonal direction of the component.\nSlope down\nAdds a downwards slope to the orthogonal direction of the component.\nSlope Up\nAdd an upwards slope to the orthogonal direction of the component.\nBy default, the slope of the currently selected branch is displayed, if required select another from a list of the available slopes in the catalog. Select the direction in the direction tool, to set the arrive/leave direction of the component plus the slope.\n\nIn the example shown below the tee is set to slope down 1 in 10 (5.7106 degrees)\n\nNo slope\nAdds no slope to the orthogonal direction of the component.\nSlope down\nAdds a downwards slope to the orthogonal direction of the component.\nSlope Up\nAdd an upwards slope to the orthogonal direction of the component.\nAdd a slope to the orthogonal direction of the component\nOrientate the component about a selected p-point\nAdd a slope to the orthogonal direction of the component\nAdd a slope to the orthogonal direction of the component\nOrientate the component about a selected p-point\nOrientate the component about a selected p-point\nNote:\nThe default maximum angle in the sample project is 11.31 degrees which gives a maximum possible change of direction of 1 in 5 (11.31 degrees).\n\n\n\nNote\n:\nSet the current slope to Up or Down\nNo slope\nSlope down\nSlope Up"}
{"Headers": "Multiple Slopes", "Content": "Multiple sloped components allow all ppoints to have offset tolerances set, thus allowing slopes in any direction. Multiple slopes mainly allow three way components to be placed at a high or low point and allow different in and out slopes. To enable this, the arrive and leave ppoints on the tee have their offset tolerance set.\nTo select an individual ppoint on a component for both orientation and direction change, select the Multi Slope check box to display the Current Point drop down list.\n\nIf the Current Point is fixed as shown above, this means the particular point does not have an offset tolerance so it can be orientated but the ppoint direction cannot be changed.\n\nComponent Orientation\nUse to orientate an individual component around a selected ppoint.\nPoint Direction\nUse to evaluate all the ppoints on the currently selected component to see if they are available for orientation and directing.\nComponent Orientation\nUse to orientate an individual component around a selected ppoint.\nPoint Direction\nUse to evaluate all the ppoints on the currently selected component to see if they are available for orientation and directing.\n\nIf the ppoints are fixed, an Error window is displayed.\n\nComponent Orientation\nUse to orientate an individual component around a selected ppoint.\nPoint Direction\nUse to evaluate all the ppoints on the currently selected component to see if they are available for orientation and directing.\n\n\n\nMulti Slope\nCurrent Point\nComponent Orientation\nPoint Direction\nError"}
{"Headers": "Rotation Tool", "Content": "Use the Rotation Tool to change the rotation orientation of a component using the rotation dial. Click Rotate Component to display the Rotation Tool. Dependent upon the currently selected component determines how the rotation tool is displayed.\nUse to rotate a component 360 degrees, the default rotation angle is 15 degrees.\nDirect Component\nUse to return to the direction tool, refer to Component Direction for further information.\n\nDirect Component\nUse to return to the direction tool, refer to Component Direction for further information.\n\nDirect Component\nUse to return to the direction tool, refer to Component Direction for further information.\n\n\n\nComponent Direction\nRotation Tool\nRotate Component\nRotation Tool\nDirect Component\nComponent Direction"}
{"Headers": "Rotate a flanged component", "Content": "Use the Bolt Hole Alignment window to rotate a flanged component so that it aligns with the bolt hole spacing by default, which means using the number of bolt holes in the component to determine the default angle increments of rotation.\nFor example, in this case the flanged component has eight bolt holes, therefore the available default angle increments of rotation are constrained to 45 degrees.\n\nTo remove the constraint and rotate the component without aligning to the bolt holes, from the Bolt Hole Alignment window, click Rotate By Bolt Hole Angle Increments Only.\n\nClick Rotate By Bolt Hole Angle Increments Only, then select the rotation angle which is no longer constrained by bolt hole alignment. A Question window is displayed:\n\nClick Yes to rotate the connected flanged components to the angle.\nClick No to close the Question window.\nOr\nClick Cancel to discard any inputs and close the Question window.\nTo return to 3D compass view of the Piping Component Editor window, click Direct Component.\n\n\n\nBolt Hole Alignment\nBolt Hole Alignment\nRotate By Bolt Hole Angle Increments Only.\nRotate By Bolt Hole Angle Increments Only\nQuestion\nYes\nNo\nQuestion\nCancel\nQuestion\nPiping Component Editor\nDirect Component"}
{"Headers": "Component Orientation", "Content": "Use the Orientation part of the Piping Component Editor window to adjust the orientation of a component.\n\nDirection towards next\nSets the orientation of a component towards the next component in the branch assembly.\nDirection towards previous\nSets the orientation of a component towards the previous component of the branch assembly.\nDirection towards pick\nPicks a position in the 3D graphical view to direct a component towards\nDirect towards head\nSets the orientation of a component towards the head of the branch assembly.\nDirect towards tail\nSets the orientation of a component towards the tail of the branch assembly.\nOrientate current component\nSets the orientation of the arrive point of the current component to the same orientation as the leave point of the previous component.\nSwap arrive and leave points (flip)\nFlips a component.\nAlign/selection component\nAligns the selected component with the arrive and leave direction of the branch leg.\nDirect selection/component\nAligns the selected component to the next/previous component within the route, where possible.\n\nDirection towards next\nSets the orientation of a component towards the next component in the branch assembly.\n\nDirection towards previous\nSets the orientation of a component towards the previous component of the branch assembly.\n\nDirection towards pick\nPicks a position in the 3D graphical view to direct a component towards\n\nDirect towards head\nSets the orientation of a component towards the head of the branch assembly.\n\nDirect towards tail\nSets the orientation of a component towards the tail of the branch assembly.\n\nOrientate current component\nSets the orientation of the arrive point of the current component to the same orientation as the leave point of the previous component.\n\nSwap arrive and leave points (flip)\nFlips a component.\n\nAlign/selection component\nAligns the selected component with the arrive and leave direction of the branch leg.\n\nDirect selection/component\nAligns the selected component to the next/previous component within the route, where possible.\nUse the Other part of the Piping component Editor, to manipulate components and pipework.\n\nRepeat the last create component operation to\nCreates an identical component to the last created component.\nConnect to previous component\nConnects the piping component to the previous piping component.\nchange flow through component\nModifies the arrive and leave direction of a multi-way component.\nAuto Complete\nUse to add components to fill gaps, head to first components, components in the middle of the branch or the last components to the tail (existing components are not moved).\n\nRepeat the last create component operation to\nCreates an identical component to the last created component.\n\nConnect to previous component\nConnects the piping component to the previous piping component.\n\nchange flow through component\nModifies the arrive and leave direction of a multi-way component.\n\nAuto Complete\nUse to add components to fill gaps, head to first components, components in the middle of the branch or the last components to the tail (existing components are not moved).\nOther\nadvanced positioning Drag\nDisplays the Drag Move window when a component is selected in the Model Explorer. Refer to for further information\nDisplays the Drag Move Branch window when a branch is selected in the Model Explorer. Refer to for further information.\nadvanced positioning Move\nDisplays the Move window when a component is selected in the Model Explorer. Refer to for further information.\nDisplays the Move Branch window when a branch is selected in the Model Explorer. Refer to for further information.\n\nadvanced positioning Drag\nDisplays the Drag Move window when a component is selected in the Model Explorer. Refer to for further information\nDisplays the Drag Move Branch window when a branch is selected in the Model Explorer. Refer to for further information.\n\nadvanced positioning Move\nDisplays the Move window when a component is selected in the Model Explorer. Refer to for further information.\nDisplays the Move Branch window when a branch is selected in the Model Explorer. Refer to for further information.\nIf the equipment is repositioned using the generic positioning commands, the pipes connected to the equipment do not move automatically with the item. The Drag function is used to move constrained networks of Piping, Equipment and Nozzle elements all together. How the constrained network is created depends on the direction of the drag operation and the type of item being dragged.\nDirection towards next\nSets the orientation of a component towards the next component in the branch assembly.\nDirection towards previous\nSets the orientation of a component towards the previous component of the branch assembly.\nDirection towards pick\nPicks a position in the 3D graphical view to direct a component towards\nDirect towards head\nSets the orientation of a component towards the head of the branch assembly.\nDirect towards tail\nSets the orientation of a component towards the tail of the branch assembly.\nOrientate current component\nSets the orientation of the arrive point of the current component to the same orientation as the leave point of the previous component.\nSwap arrive and leave points (flip)\nFlips a component.\nAlign/selection component\nAligns the selected component with the arrive and leave direction of the branch leg.\nDirect selection/component\nAligns the selected component to the next/previous component within the route, where possible.\nRepeat the last create component operation to\nCreates an identical component to the last created component.\nConnect to previous component\nConnects the piping component to the previous piping component.\nchange flow through component\nModifies the arrive and leave direction of a multi-way component.\nAuto Complete\nUse to add components to fill gaps, head to first components, components in the middle of the branch or the last components to the tail (existing components are not moved).\nadvanced positioning Drag\nDisplays the Drag Move window when a component is selected in the Model Explorer. Refer to for further information\nDisplays the Drag Move Branch window when a branch is selected in the Model Explorer. Refer to for further information.\nadvanced positioning Move\nDisplays the Move window when a component is selected in the Model Explorer. Refer to for further information.\nDisplays the Move Branch window when a branch is selected in the Model Explorer. Refer to for further information.\n\n\n\nOrientation\nPiping Component Editor\nDirection towards next\nDirection towards previous\nDirection towards pick\nDirect towards head\nDirect towards tail\nOrientate current component\nSwap arrive and leave points (flip)\nAlign/selection component\nDirect selection/component\nOther\nPiping component Editor\nRepeat the last create component operation to\nConnect to previous component\nchange flow through component\nAuto Complete\nOther\nadvanced positioning Drag\nDrag Move\n\nDrag Move Branch\n\nadvanced positioning Move\nMove\n\nMove Branch\n"}
{"Headers": "Reselect Component", "Content": "Use the Reselect tab to replace a piping component from a list of available components, select the Reselect tab to display the Current Elements (CEs) attributes and properties. The Reselect tab of the Piping Component Editor window displays all the components available from the catalog under the current piping specification.\n\nSelect a component from the Type drop-down list to filter the component type to modify.\nSelect a component specification from the Sub-Types drop-down list to filter the component by sub-type.\nSelect a component from list of available components, dependent upon which component is selected determines what component specific information is displayed.\n\nSelect Reconnection to re-establish adjacent connections. If an error occurs when the components is replace, the error tab displays, populated with the error.\n\n\n\nReselect\nReselect\nReselect\nPiping Component Editor\nType\nSub-Types\nReconnection"}
{"Headers": "Error Messages", "Content": "With the Errors tab selected, the Piping Component Editor window lists the components selected fro modification which produce an error in the selection process. An error is indicated with a description in the error list.\n\nWhen the error has been rectified, click Refresh to update the error list.\n\n\n\nErrors\nPiping Component Editor\nRefresh"}
{"Headers": "Non Standard Branch Connections", "Content": "The Non-standard connections functionality uses non-standard connections in the Piping discipline. A non-standard connection is essentially a branch connection at any point on the surface of the main branch. Normally these are tube connections which are inserted by drilling a hole at some point and welding the new branch into place.\nWith non-standard branch connections you can create and connect new branches or connect existing branches to components such as valves, reducers and elbows. The branch connects to a cartesian point (PIPCA) owned by the component or an element called a Pipe Tapping (PTAP) for tube to tube connections.\nUnlike other TEE or OLET type connections a special branch connection does not require additional components in the piping specification but it does require the AVEVA specification /General-Tappings which is contained in the DB MASTER/PIPECATA in the AVEVA MAS project.\n\nCreate a connection point and then if required position and orientate it.\nIf the non-standard branch connection is greyed out in the Tools group, refer to the system administrator.\n\n\n\nTools"}
{"Headers": "Connect Existing Branch", "Content": "Use the Non-standard Branch Connections window to connect existing branches.\n\nFrom the Main Branch pane, click Select, the prompt Identify Main Branch is displayed. Once the selection has been made, the selected branch name, bore and wall thickness are displayed in the Non-standard Branch Connections window and the Connect Existing Branch check box is automatically selected.\nFrom the Select Branch pane, click Select, the prompt Identify Stub in Branch is displayed. Once the selection has been made, the branch connects to a cartesian point (PIPCA) owned by the component. The selected branch name and bore are displayed in the Non-standard Branch Connections window. As the branch is not yet connected the Current connection details part of the Non-standard Branch Connections window head and tail are not connected.\nUse the Connection Details part of the Non-standard Connections window, to set the connection and tapping type, bore size and insert depth.\nThe actual connection can be edited by changing its type, or adding a connection component such as a half coupling.\nThe Branch Type can be selected from the drop-down list:\nInsert Connection\nThe branch tube is inserted into the main branch and welded.\nSurface Connection\nThe branch tube is placed on the main branch and welded.\nSaddle Connection\nThe branch tube is shaped to fit on the main branch and welded.\nExtruded Connection\nThe main branch tube is shaped by machine to form a tube to tube connection.\nBoss Connection\na fitting is selected from the spec and it is welded to form the branch connection.\nInsert Connection\nThe branch tube is inserted into the main branch and welded.\nSurface Connection\nThe branch tube is placed on the main branch and welded.\nSaddle Connection\nThe branch tube is shaped to fit on the main branch and welded.\nExtruded Connection\nThe main branch tube is shaped by machine to form a tube to tube connection.\nBoss Connection\na fitting is selected from the spec and it is welded to form the branch connection.\nIn the Note field, add a fabrication note which will appear on the piping isometrics\nThe Insert Depth value varies according to the Branch Type selected and is calculated using a set of standard calculations for branches on centerline. In some cases the calculation may need to be adjusted by eye to provide a more accurate material length. To do this enter a value into the Insert Depth field. The value shown in this field can be one of three types:\nInsert Depth (Default)\nthe standard calculation for this type of branch.\nInsert Depth (Actual)\nthe actual insert depth on the current connection.\nInsert Depth (User)\nthe current value entered but not yet fixed by clicking Apply. The button to the right of the insert depth will swap the insert values between actual and default.\nFor example if the default is 4.75mm and the actual is 14.57mm clicking Default will change the insert depth to 4.75 and the button will have a display of Actual. Clicking it again will return the insert depth value to 14.57.\nInsert Depth (Default)\nthe standard calculation for this type of branch.\nInsert Depth (Actual)\nthe actual insert depth on the current connection.\nInsert Depth (User)\nthe current value entered but not yet fixed by clicking Apply. The button to the right of the insert depth will swap the insert values between actual and default.\nFor example if the default is 4.75mm and the actual is 14.57mm clicking Default will change the insert depth to 4.75 and the button will have a display of Actual. Clicking it again will return the insert depth value to 14.57.\nClick Apply to create the connection or click Dismiss to discard any inputs and close the Non-standard Connections window.\nInsert Connection\nThe branch tube is inserted into the main branch and welded.\nSurface Connection\nThe branch tube is placed on the main branch and welded.\nSaddle Connection\nThe branch tube is shaped to fit on the main branch and welded.\nExtruded Connection\nThe main branch tube is shaped by machine to form a tube to tube connection.\nBoss Connection\na fitting is selected from the spec and it is welded to form the branch connection.\nInsert Depth (Default)\nthe standard calculation for this type of branch.\nInsert Depth (Actual)\nthe actual insert depth on the current connection.\nInsert Depth (User)\nthe current value entered but not yet fixed by clicking Apply. The button to the right of the insert depth will swap the insert values between actual and default.\nFor example if the default is 4.75mm and the actual is 14.57mm clicking Default will change the insert depth to 4.75 and the button will have a display of Actual. Clicking it again will return the insert depth value to 14.57.\nNote:\nBoss type elements must be in the branch specification, have a gtype of COUP and COMPTYPE eq 'PTAP' to be recognized by this application.\n\n\n\nNon-standard Branch Connections\nMain Branch\nSelect\nIdentify Main Branch\n\nNon-standard Branch Connections\nConnect Existing Branch\nSelect Branch\nSelect\nIdentify Stub in Branch\nNon-standard Branch Connections\nCurrent connection details\nNon-standard Branch Connections\nConnection Details\nNon-standard Connections\nBranch Type\nInsert Connection\nSurface Connection\nSaddle Connection\nExtruded Connection\nBoss Connection\nNote\n:\nNote\nInsert Depth\nBranch Type\nInsert Depth\nApply\nDefault\nActual\nApply\nDismiss\nNon-standard Connections"}
{"Headers": "Create New Branch", "Content": "Use then Non-standard Branch Connections window to connect a new branch, click Select, the prompt Identify Main Branch is displayed. Once the selection has been made, the selected branch name, bore and wall thickness are displayed in the Non-standard Branch Connections window. Select the Connect New Branch check box.\n\nThe Create New Branch pane is automatically displayed with a name for the new branch. Click Pick connection Point, the prompt Pick a surface Position to locate initial branch position: is displayed.\nThe new branch is initially positioned at the new connection point in the 3D graphical view, to adjust the position of the connection point, click Adjust position. The Locate Branch window is displayed and a positioning aid (plane) is displayed in the 3D graphical view.\nThe Locate Branch window is populated with the direction of the plane and branch also with the angle at which the new connection point is initially positioned.\n\nIf required, position the new connection, use the Nudge and Rotation parts of the Locate Branch window.\n\nClick OK to position the connection at the new location or click Dismiss to discard any inputs and close the Locate Branch window.\nFrom the Connection Details pane, set the connection and tapping type, bore size and insert depth.\nClick Apply to create the connection or click Dismiss to discard any inputs and close the Non-standard Connections window.\n\n\n\nNon-standard Branch Connections\nSelect,\nIdentify Main Branch\nNon-standard Branch Connections\nConnect New Branch\nCreate New Branch\nPick connection Point,\nPick a surface Position to locate initial branch position:\nAdjust position\nLocate Branch\nLocate Branch\nNudge\nRotation\nLocate Branch\nOK\nDismiss\nLocate Branch\nConnection Details\nApply\nDismiss\nNon-standard Connections"}
{"Headers": "Pipe Component Bore and Specification", "Content": "A pipe or branch and the components contained within can be viewed and their attributes modified. The same window is displayed for the currently selected branch or pipe.\n\n\n.\n\nSelect another branch in the design hierarchy, then click CE to populate the Modify Components window with its attributes.\nTo highlight selected components within the pipe or branch, click to highlight the components in the 3D graphical view, then click Select from 3D View. The selected components are highlighted in the Modify Components window.\nThe Insulation Specification can be added to the Modify Components window, click to check the Insulation Spec check box, the insulation specification displays in a separate column in the Modify Components window.\nThe Tracing Specification can be added to the Modify Components window, click to check the Tracing Spec check box, the tracing specification displays in a separate column in the Modify Components window.\n\n\n\n\n\n\nCE\nModify Components\nSelect from 3D View\nModify Components\nInsulation Specification\nModify Components\nInsulation Spec\nModify Components\nTracing Specification\nModify Components\nTracing Spec\nModify Components"}
{"Headers": "Component List", "Content": "The Component List tab on the Modify Components window displays the following:\nDesign Element\nDisplays the name of the element\nComponent Description\nDisplays the description of the component\nABORE\nDisplays the bore at the p-point where the flow enters the component\nLBORE\nDisplays the bore at the p-point where the flow leaves the component\nPBORE\nDisplays the bore at any of the p-points regardless of the flow direction\nSpec Component\nDisplays the current specification of the component\nNew Spec Component\nDisplays the new specification of the component\nNew Component\nDescription\nDisplays the description of the new component\nDesign Element\nDisplays the name of the element\nComponent Description\nDisplays the description of the component\nABORE\nDisplays the bore at the p-point where the flow enters the component\nLBORE\nDisplays the bore at the p-point where the flow leaves the component\nPBORE\nDisplays the bore at any of the p-points regardless of the flow direction\nSpec Component\nDisplays the current specification of the component\nNew Spec Component\nDisplays the new specification of the component\nNew Component\nDescription\nDisplays the description of the new component\nApply changes to like components check box - checking applies one component change to all like instances in the Component List.\nDesign Element\nDisplays the name of the element\nComponent Description\nDisplays the description of the component\nABORE\nDisplays the bore at the p-point where the flow enters the component\nLBORE\nDisplays the bore at the p-point where the flow leaves the component\nPBORE\nDisplays the bore at any of the p-points regardless of the flow direction\nSpec Component\nDisplays the current specification of the component\nNew Spec Component\nDisplays the new specification of the component\nNew Component\nDescription\nDisplays the description of the new component\n\n\n\nComponent List\nModify Components\nDesign Element\nComponent Description\nABORE\nLBORE\nPBORE\nSpec Component\nNew Spec Component\nNew Component\nDescription\nApply changes to like components\nComponent List"}
{"Headers": "Error Messages", "Content": "With the Error Messages tab selected, the Modify Components window lists the components selected for modification which produce an error in the selection process. When the selection process takes place, each selected item is scanned to find an equivalent in the new specification. Where an item cannot be found, an error is indicated with a description in the error list.\n\n\n\n\nError Messages\nModify Components"}
{"Headers": "Highlighting", "Content": "With the Highlighting tab selected, define the colour's used in the component list when selecting components from the list. Once a highlighting colour scheme has been defined this is restored upon re-entry into the discipline.\n\nThe Highlighting tab on the Modify Components window, displays:\nComponent\nDefines the colour of the selected component in the list.\nTube\nDefines the colour of the selected tube in the list.\nNo Specification\nDefines the colour of the selected component in the list, when there is no specification.\nComponent in Limbospec\nDefines the colour of the selected component when its in limbospec. (If a SPEC or SPCOM is removed, the data held within it is transferred to a special archive Specification named /*LIMBOSPEC. The data still exists, so that references to it are still valid, but it no longer forms part of the original named SPEC).\nInvalid pipng spec\nDefines the colour of selected component when its has an invalid pipe spec.\nSuccessfully Selected New Specification\nDefines the colour of the selected component in the list, when a new specification has been found.\nFailed to Select New Specification\nDefines the colour of the selected component in the list, when a new specification can be found.\nReset to Defaults\nReturns the highlight colours to the default settings.\nComponent\nDefines the colour of the selected component in the list.\nTube\nDefines the colour of the selected tube in the list.\nNo Specification\nDefines the colour of the selected component in the list, when there is no specification.\nComponent in Limbospec\nDefines the colour of the selected component when its in limbospec. (If a SPEC or SPCOM is removed, the data held within it is transferred to a special archive Specification named /*LIMBOSPEC. The data still exists, so that references to it are still valid, but it no longer forms part of the original named SPEC).\nInvalid pipng spec\nDefines the colour of selected component when its has an invalid pipe spec.\nSuccessfully Selected New Specification\nDefines the colour of the selected component in the list, when a new specification has been found.\nFailed to Select New Specification\nDefines the colour of the selected component in the list, when a new specification can be found.\nReset to Defaults\nReturns the highlight colours to the default settings.\nTo change any of the highlighted colours, click the colour to be changed to display a colour selection window.\n\nBy default, the Highlighting Colour window is displayed with a limited selection of colours, to extend the colour selection, click More.\n\nSelect the required highlighting colour, then click Reset, once set the colour palette changes to that colour and the highlighting is changed in the component list.\nSpecific highlighting can also be turned On and Off using the radio buttons next to each highlighting colour palette.\nComponent\nDefines the colour of the selected component in the list.\nTube\nDefines the colour of the selected tube in the list.\nNo Specification\nDefines the colour of the selected component in the list, when there is no specification.\nComponent in Limbospec\nDefines the colour of the selected component when its in limbospec. (If a SPEC or SPCOM is removed, the data held within it is transferred to a special archive Specification named /*LIMBOSPEC. The data still exists, so that references to it are still valid, but it no longer forms part of the original named SPEC).\nInvalid pipng spec\nDefines the colour of selected component when its has an invalid pipe spec.\nSuccessfully Selected New Specification\nDefines the colour of the selected component in the list, when a new specification has been found.\nFailed to Select New Specification\nDefines the colour of the selected component in the list, when a new specification can be found.\nReset to Defaults\nReturns the highlight colours to the default settings.\nNote:\nThe name of this window changes depending on which of the colours is selected on the Modify Components window. For example:\nNote:\nThe highlighting defaults are loaded if no highlighting scheme can be retrieved upon entering the Piping discipline.\n\n\n\nHighlighting\nHighlighting\nModify Components\nComponent\nTube\nNo Specification\nComponent in Limbospec\nInvalid pipng spec\nSuccessfully Selected New Specification\nFailed to Select New Specification\nReset to Defaults\nNote\n:\nModify Components\nHighlighting Colour\nMore\nReset\nOn\nOff\nNote\n:\n"}
{"Headers": "Pipe Details", "Content": "The Pipe Details pane of the Slope Pipe window displays the Current Element (CE), the slope reference, the slope angle, the direction of the slope and the slope format.\n\nCalculate the slope for the current element\nDisplays the details and a pictorial representation for the CE.\nChange to Backwards Calculation Mode\nClick to begin the slope at the tail of the pipe.\nChange to Forwards Calculation Mode\nClick to begin the slope at the head of the pipe.\nError Messages have been generated by the slope calculation\nDisplays the Slopes Pipe Messages window populated with warnings and error messages (if any).\nThe colour of the icon changes to red when a warning error is generated.\n\nCalculate the slope for the current element\nDisplays the details and a pictorial representation for the CE.\n\nChange to Backwards Calculation Mode\nClick to begin the slope at the tail of the pipe.\n\nChange to Forwards Calculation Mode\nClick to begin the slope at the head of the pipe.\n\nError Messages have been generated by the slope calculation\nDisplays the Slopes Pipe Messages window populated with warnings and error messages (if any).\nThe colour of the icon changes to red when a warning error is generated.\nSelect a slope gradient from the Slope Reference drop-down list to display a preview of the slope in the 3D Preview Pane.\nAlternatively, input a slope value into the Slope field and select the slope direction from the slope drop-down list.\nSelect a slope angle from the Slope Format drop-down list, the defined Slope Format displays in the Slope field.\nClick to check the Slope individual legs check box to apply a slope to an individual branch leg. Any previously calculated slope is removed from the 3D Preview Pane display.\nCalculate the slope for the current element\nDisplays the details and a pictorial representation for the CE.\nChange to Backwards Calculation Mode\nClick to begin the slope at the tail of the pipe.\nChange to Forwards Calculation Mode\nClick to begin the slope at the head of the pipe.\nError Messages have been generated by the slope calculation\nDisplays the Slopes Pipe Messages window populated with warnings and error messages (if any).\nThe colour of the icon changes to red when a warning error is generated.\n\n\n\nPipe Details\nSlope Pipe\nCalculate the slope for the current element\nChange to Backwards Calculation Mode\nChange to Forwards Calculation Mode\nError Messages have been generated by the slope calculation\nSlope Reference\nSlope\nSlope Format\nSlope Format\nSlope\nSlope individual legs\n3D Preview Pane"}
{"Headers": "Branch Legs", "Content": "The Branch Legs pane of the Slope Pipe window displays a numbered list of the branches and the components within the current pipe. In addition to the start and finish component for the branch leg, the list includes the length of the leg and the fall of the leg when the slope is applied. Vertical branch legs are not sloped and therefore always have a drop of zero.\n\nDuring the sloping process the Slope Pipe window lists the components selected for modification which produce a warning or caution. Click Error Messages have been generated by the slope calculation to view the details of the error.\n\n\n\n\nBranch Legs\nSlope Pipe\nSlope Pipe\nError Messages have been generated by the slope calculation"}
{"Headers": "Branch leg", "Content": "Once an entry has been selected from the list of available legs, the Branch leg pane of the Slope Pipe window is automatically populated with the functionality to anchor the selected branch leg and if available modify the slope. The pictorial representation of the CE is automatically labelled.\n\nIf the leg is nominally horizontal, the slope for the selected leg can be modified.\n\nIf the leg is nominally vertical, the slope for the selected branch leg cannot be modified, but the anchors for the branch leg can be defined.\n\nSelect the Slope leg check box to specify that the selected branch leg to be sloped, or select to uncheck the Slope leg check box to force the selected branch leg to be horizontal.\nSpecify the values for the slope, type the slope directly into the Slope field, the default slope format is defined from the selected Slope format in the Pipe Details pane of the Slope Pipe window. The Fall field is automatically populated with the correct value for the slope. These fields can be populated the other way round if required.\nThe direction of the slope can be set by selecting Up or Down from the drop-down list.\n\n\n\nBranch leg\nSlope Pipe\nSlope leg\nSlope leg\nSlope\nSlope format\nPipe Details\nSlope Pipe\nFall\nUp\nDown"}
{"Headers": "Anchors", "Content": "If necessary the selected branch leg can also be anchored to two different locations by, adjusting the vertical position of the leg to pass through the anchored positions. One or two anchor positions can be used.\nThe Anchors pane of the Slope Pipe window displays a numbered list of the branch legs within the current pipe. In addition to the anchor type, the list includes the component/distance for the branch leg, the point and the offset for the anchor.\n\nAdd an anchor point to the selected branch\nClick to add an anchor point to the selection.\nDelete the selected anchor point\nClick to delete the anchor point from the selection.\n\nAdd an anchor point to the selected branch\nClick to add an anchor point to the selection.\n\nDelete the selected anchor point\nClick to delete the anchor point from the selection.\nThe anchor type is used to specify the position of anchors. The anchor types available for selection from the Type drop-down list are:\nStart\nFixes the position of the anchor at the start of the branch leg.\nFinish\nFixes the position of the anchor at the finish of the branch leg. The position is only available for the second anchor.\nComponent\nFixes the position of the anchor(s) at a selected component within the branch leg.\nPosition\nFixes the position of the anchor(s) at a selected position within the branch leg.\nStart\nFixes the position of the anchor at the start of the branch leg.\nFinish\nFixes the position of the anchor at the finish of the branch leg. The position is only available for the second anchor.\nComponent\nFixes the position of the anchor(s) at a selected component within the branch leg.\nPosition\nFixes the position of the anchor(s) at a selected position within the branch leg.\nWhen the Component anchor types is selected, the Anchors pane of the Slope Pipe window is automatically updated with further fields requiring input.\n\nAdd an anchor point to the selected branch\nThe prompt \u2018Pick position (Distance [0]) Snap :\u2019 is displayed in the 3D Preview Pane. Click a position in the 3D Preview Pane to place an anchor.\n\nAdd an anchor point to the selected branch\nThe prompt \u2018Pick position (Distance [0]) Snap :\u2019 is displayed in the 3D Preview Pane. Click a position in the 3D Preview Pane to place an anchor.\nThe Component drop-down list identifies the component to which the anchor is to be positioned.\nThe Point drop-down list determines where on the picked component the anchor is to be positioned, select Top, Centre or Bottom.\nTo offset each anchor from the previous one by a specified distance relative to a picked position on the picked element., type the distance in the Offset field, select where to position the anchor relative to a position on the picked element.\nWhen the Position anchor type is selected, the Anchors pane of the Slope Pipe window is automatically updated with further fields requiring user input.\n\nPick a point\nThe prompt \u2018Pick position (Distance [0]) Snap : in\u2019 is displayed in the 3D Preview Pane. Click a position in the 3D Preview Pane to place an anchor.\n\nPick a point\nThe prompt \u2018Pick position (Distance [0]) Snap : in\u2019 is displayed in the 3D Preview Pane. Click a position in the 3D Preview Pane to place an anchor.\nThe horizontal distance from the start of the leg to the fixed position can be entered in the Distance field.\nThe Point drop-down list determines where on picked component the anchor is to be positioned, select Top, Centre or Bottom.\nTo offset each anchor from the previous one by a specified distance relative to a picked position on the picked element. Type the distance in the Offset field, then select where to position the anchor relative to a position on the picked element.\nAny inputs into the Slope Pipe window can be reversed:\nUndo the last change to the slope calculation\nDiscards the last change to the slope calculation.\nRedo the last change to the slope calculation\nRe-inserts the last change to the slope calculation.\n\nUndo the last change to the slope calculation\nDiscards the last change to the slope calculation.\n\nRedo the last change to the slope calculation\nRe-inserts the last change to the slope calculation.\nTo apply the slope, click Apply, to close the Slope Pipe window, click OK.\nTo discard any inputs and close the Slope Pipe window, click Cancel.\n\n\nAdd an anchor point to the selected branch\nClick to add an anchor point to the selection.\nDelete the selected anchor point\nClick to delete the anchor point from the selection.\nStart\nFixes the position of the anchor at the start of the branch leg.\nFinish\nFixes the position of the anchor at the finish of the branch leg. The position is only available for the second anchor.\nComponent\nFixes the position of the anchor(s) at a selected component within the branch leg.\nPosition\nFixes the position of the anchor(s) at a selected position within the branch leg.\nAdd an anchor point to the selected branch\nThe prompt \u2018Pick position (Distance [0]) Snap :\u2019 is displayed in the 3D Preview Pane. Click a position in the 3D Preview Pane to place an anchor.\nPick a point\nThe prompt \u2018Pick position (Distance [0]) Snap : in\u2019 is displayed in the 3D Preview Pane. Click a position in the 3D Preview Pane to place an anchor.\nUndo the last change to the slope calculation\nDiscards the last change to the slope calculation.\nRedo the last change to the slope calculation\nRe-inserts the last change to the slope calculation.\nNote:\nIf two anchors are used, the first anchor must be closer to the start of the branch leg than the second anchor.\n\n\n\nAnchors\nSlope Pipe\nNote\n:\nAdd an anchor point to the selected branch\nDelete the selected anchor point\nType\nStart\nFinish\nComponent\nPosition\nComponent\nAnchors\nSlope Pipe\nAdd an anchor point to the selected branch\nPick position (Distance [0]) Snap :\u2019\n\n3D Preview Pane\n3D Preview Pane\nComponent\nPoint\nTop\nCentre\nBottom\nOffset\nPosition\nAnchors\nSlope Pipe\nPick a point\nPick position (Distance [0]) Snap :\n3D Preview Pane\n3D Preview Pane\nDistance\nPoint\nTop\nCentre\nBottom\nOffset\nSlope Pipe\nUndo the last change to the slope calculation\nRedo the last change to the slope calculation\nApply\nSlope Pipe\nOK\nSlope Pipe\nCancel"}
{"Headers": "Splitting Pipes on a Plane", "Content": "Splits the pipe by inserting an pipe assembly at the point a cutting plane intersects the pipe.\nSelect Split Pipe on a Plane to display the relevant options in the Split Pipe window.\n\n\n\n\n\nSplit Pipe on a Plane\nSplit Pipe"}
{"Headers": "Plane definition", "Content": "Use the Plane definition part of the Split Pipe window to define, position and create the cutting plane.\n\nInput the required Plane size in the Plane Size field, to create and modify the plane, select Define Plane, select an design element on the 3D graphical view.\n\n\n\nPlane definition\nSplit Pipe\nPlane size\nPlane Size\nDefine Plane"}
{"Headers": "Move down-stream components to", "Content": "When splitting a pipe, define where the components located down stream of the split and inserted assembly are moved to from the Move down-stream components to part of the Split Pipe window.\n\nExisting\nPipe assemblies are inserted at the split position in the currently selected branch.\nNew Pipe\nComponents downstream of the split are moved into a new pipe in the design hierarchy.\nNew Bran\nComponents downstream of the split are split into extra branches in the design hierarchy.\nExisting\nPipe assemblies are inserted at the split position in the currently selected branch.\nNew Pipe\nComponents downstream of the split are moved into a new pipe in the design hierarchy.\nNew Bran\nComponents downstream of the split are split into extra branches in the design hierarchy.\n\nExisting\nPipe assemblies are inserted at the split position in the currently selected branch.\nNew Pipe\nComponents downstream of the split are moved into a new pipe in the design hierarchy.\nNew Bran\nComponents downstream of the split are split into extra branches in the design hierarchy.\n\n\n\nMove down-stream components to\nSplit Pipe\nExisting\nNew Pipe\nNew Bran"}
{"Headers": "Split Pipes into Segments", "Content": "Use Split Pipes in Segments, to split a single branch into segments of a user-defined length between components or features picked on the 3D graphical view (at each split, the choose pipe assembly is inserted). Select Split Pipes into a Segments from the Split Pipe Options on the Split Pipe window to display the relevant options.\n\nSplit By\nChoose the components or selected features adjacent to the pipe to identify the start and stop of the range selection from the Split By drop-down list. Refer to and for further information.\n\n\n\nSplit Pipes in Segments\nSplit Pipes into a Segments\nSplit Pipe Options\nSplit Pipe\nSplit By\nSplit By\n\n"}
{"Headers": "Pipe Assemblies", "Content": "Pipe Assemblies are used as an aid in the pipe splitting process, all of the tasks that a user would carry out that are associated with the use of assemblies as a splitting aid is initiated from a central Split Pipe window with the Assembly tab selected which acts as a task hub.\nChoose from a list of available assemblies in the Filter Assemblies By part of the Split Pipe window. The assemblies available for selection are those already created in the database, if the required assembly is not included, click Refresh to update the error list or refer to the system administrator.\n\n\n\n\nSplit Pipe\nAssembly\nFilter Assemblies By\nSplit Pipe"}
{"Headers": "Assembly Build Origin", "Content": "The final option available for plane splitting is the assembly build point; determine whether to build to the primary or secondary origin of the assembly, choose from the Assembly build origin drop-down list.\n\nThe primary and secondary origin points allows some control over where the assembly is positioned relative to the splitting point.\nOne of the most common types of assembly used in pipe splitting are a set of break flanges where the relevant points for positioning the assembly are on either flange face. In this case the primary origin point would be defined as the leave point (upstream flange face) and the secondary origin would be defined as being the arrive point (downstream flange face). Displayed below is a representation of the splitting procedure:\n\nFor more information on Assembly creation and usage.\n\n\n\n\nAssembly build origin"}
{"Headers": "Split Pipes", "Content": "Split\nClick Split to display the Confirm window, the split is labelled on the 3D graphical view.\n\nConfirm if the split points are acceptable and the changes can be accepted or rejected. If rejected, the process is restarted.\n\nThe resulting split with pipe assembly is inserted into the pipe.\n\nID Split\nIf required, pipes can be split using a defined plane by directly picking pipes using the mouse cursor. Click ID Split and then use the mouse cursor to select pipes that are split relative to the existing plane. Esc must be pressed to exit this mode.\nClick Flow to display the direction of flow for the selected pipe.\n\nClick Undo to discard any inputs or Dismiss to close the Split Pipe window.\n\nNote:\nThe option is only available when splitting a pipe with a plane.\n\n\n\nSplit\nSplit\nConfirm\nID Split\nNote\n:\nID Split\nEsc\nFlow\nUndo\nDismiss\nSplit Pipe"}
{"Headers": "Split Pipe Length", "Content": "In the Split Pipe Length drop-down list select Segment Length or Cut Pipe Length:\nSegment Length\nAllows the pipes to be split into segments of a particular length between selected components or selected features that are adjacent to the pipe. The split is made by inserting pipe assemblies into the branch. Tube length around bends and elbows is calculated as the centerline length.\nCut Pipe Length (Used for spool length)\nAllows the pipes to be cut at a particular length between selected components or selected features that are adjacent to the pipe. The cut is made by inserting pipe assemblies into the branch. Tube length around bends and elbows is calculated as the centerline length.\nMinimum Final Tube Length\nRestricts the length of the final tube to the final length value. If the final tube length is below this value, the previous spools are adjusted to make the final length within its tolerance.\nInput the following dimensions to the pipe in the Split Pipe Length part of the Split Pipe window:\nThe downstream components at each split may be inserted into the existing branch, a new branch or a new pipe depending on what is chosen from the Move down-stream components to part of the Split Pipe window. If a new branch or pipe is requested, the new items are given a default name based on the pipe name.\n\nSelect the assemblies to insert into the branch where the split occurs, refer to Pipe Assemblies and Assembly Build Origin for further information. Click Split to split selected pipes using components (refer to Component Picks for further information) or selected features adjacent to the pipe (refer to Feature Picks for further information).\n\nSegment Length - Segment Length must not be less than 100 or unset, if the length is set less than 100 or unset, an Error window is displayed.\nMinimum Final Tube Length\nSegment Length - Segment Length must not be less than 100 or unset, if the length is set less than 100 or unset, an Error window is displayed.\nSegment Length - Segment Length must not be less than 100 or unset, if the length is set less than 100 or unset, an Error window is displayed.\nMinimum Final Tube Length\nMinimum Final Tube Length\n\n\n\nPipe Assemblies\nAssembly Build Origin\nComponent Picks\nFeature Picks\nSplit Pipe Length\nSegment Length\nCut Pipe Length\nSegment Length\nCut Pipe Length\nMinimum Final Tube Length\nSplit Pipe Length\nSplit Pipe\nError\nMove down-stream components to\nSplit Pipe\nPipe Assemblies\nAssembly Build Origin\nSplit\nComponent Picks\nFeature Picks"}
{"Headers": "Split Pipe by moving Component", "Content": "To make a split by moving a component, select Split pipe by moving component from the Split Pipe Option part of the Split Pipe window. Once the selection has been made, where to move the components down-stream of the split (selection) must be selected. After selecting to where to move down-stream components. Click Split.\n\nThe prompt \u2018identify branch to split\u2019 is displayed in the status bar at the bottom left hand corner of the 3D graphical view. After making the selection, the prompt \u2018Pick the piping component\u2019 is displayed.\n\nOnce the piping component has been selected, the pipe is split at this point and all the components down stream of the split (component selected) are moved to a new pipe or branch in the design hierarchy.\n\n\n\n\n\nSplit pipe by moving component\nSplit Pipe Option\nSplit Pipe\nSplit\nidentify branch to split\u2019\n\nPick the piping component"}
{"Headers": "Merge branch/pipe", "Content": "As part of a project or design requirement, it may be necessary to merge individual piping components to form a single pipe or branch.\nIf necessary, navigate to the Current Element (CE) into which the others are to be merged, from the Merge Unit part of the Split Pipe window, select:\nOne Pipe\nMerges all the components into one pipe\nOne Bran\nMerges all the components into one branch\nOne Pipe\nMerges all the components into one pipe\nOne Bran\nMerges all the components into one branch\n\nFrom the Perform Commands part of the Split Pipe window, click Merge, the prompt \u2018Pick a Piping component - source element\u2019 is displayed in the status bar at the top left hand corner of the 3D graphical view. The section is highlighted in red, after making the selection the prompt \u2018Pick Piping Component - target element\u2019 is displayed.\nOnce the sections have been selected, the components are merged into one pipe or branch. All material properties for the merged section are taken from the settings for the CE.\nWhen sections are unabble to be merged, the following Error message displays.\n\nClick Flow to display the current direction of flow, Undo to discard any inputs or Dismiss to close the Split Pipe window.\nOne Pipe\nMerges all the components into one pipe\nOne Bran\nMerges all the components into one branch\nNote:\nAll sections to be merged must share a common axis with the current element, as defined by the line through their start and end positions.\n\n\n\nMerge Unit\nSplit Pipe\nOne Pipe\nOne Bran\nPerform Commands\nSplit Pipe\nMerge\nPick a Piping component - source element\u2019\n\u2018Pick Piping Component - target element\u2019\nNote\n:\nError\nFlow\nUndo\nDismiss\nSplit Pipe"}
{"Headers": "Split/Merge", "Content": "Split Pipe Options\nIn the Split Pipe Options part of the Split Pipe window, choose how the pipe is be split, dependent upon which option chosen determines what functionality is available for selection from the Split Pipe window.\n\nSplit Pipes on a Plane\nSplits the pipe by inserting an pipe assembly at the point a cutting plane intersects the pipe. Refer to Splitting Pipes on a Plane for further information, selected by default.\nSplit Pipes into Segments\nSplits the pipe into a number of segments using the inputted dimensions. The split is defined between two selected points (selection of these points can be achieved by choosing either the Feature pick or Component pick from the Split By drop-down list). Refer to Split Pipes into Segments for further information.\nSplit pipe by moving Component\nSplits the pipe at the split point and inserts an pipe assembly at that point. The down-stream components in the branch are then be moved. Refer to Move down-stream components to for further information.\nSplit Pipes on a Plane\nSplits the pipe by inserting an pipe assembly at the point a cutting plane intersects the pipe. Refer to Splitting Pipes on a Plane for further information, selected by default.\nSplit Pipes into Segments\nSplits the pipe into a number of segments using the inputted dimensions. The split is defined between two selected points (selection of these points can be achieved by choosing either the Feature pick or Component pick from the Split By drop-down list). Refer to Split Pipes into Segments for further information.\nSplit pipe by moving Component\nSplits the pipe at the split point and inserts an pipe assembly at that point. The down-stream components in the branch are then be moved. Refer to Move down-stream components to for further information.\n\nSplit Pipes on a Plane\nSplits the pipe by inserting an pipe assembly at the point a cutting plane intersects the pipe. Refer to Splitting Pipes on a Plane for further information, selected by default.\nSplit Pipes into Segments\nSplits the pipe into a number of segments using the inputted dimensions. The split is defined between two selected points (selection of these points can be achieved by choosing either the Feature pick or Component pick from the Split By drop-down list). Refer to Split Pipes into Segments for further information.\nSplit pipe by moving Component\nSplits the pipe at the split point and inserts an pipe assembly at that point. The down-stream components in the branch are then be moved. Refer to Move down-stream components to for further information.\n\n\n\nSplitting Pipes on a Plane\nSplit Pipes into Segments\nMove down-stream components to\nSplit Pipe Options\nSplit Pipe Options\nSplit Pipe\nSplit Pipe\nSplit Pipes on a Plane\nSplitting Pipes on a Plane\nSplit Pipes into Segments\nFeature pick\nComponent pick\nSplit By\nSplit Pipes into Segments\nSplit pipe by moving Component\nMove down-stream components to"}
{"Headers": "Detail Options", "Content": "Use the Details Options part of the Split Pipe window to add the pipe to be split to the Branches to Split list.\n\nAdd Ce\nAdds the currently selected element in the design hierarchy into the branch to be split list.\nAdd Selected\nThe prompt \u2018Pick a pipe branch (or branches) to split \u2018 is displayed in the status bar from the 3D graphical view of the pipework system.\nPress esc to finish\nID Selection\nPick multiple branches in the 3D graphical view.\nClear all\nRemove all of the elements to be split from the list.\nAdd Ce\nAdds the currently selected element in the design hierarchy into the branch to be split list.\nAdd Selected\nThe prompt \u2018Pick a pipe branch (or branches) to split \u2018 is displayed in the status bar from the 3D graphical view of the pipework system.\nPress esc to finish\nID Selection\nPick multiple branches in the 3D graphical view.\nClear all\nRemove all of the elements to be split from the list.\n\nAdd Ce\nAdds the currently selected element in the design hierarchy into the branch to be split list.\nAdd Selected\nThe prompt \u2018Pick a pipe branch (or branches) to split \u2018 is displayed in the status bar from the 3D graphical view of the pipework system.\nPress esc to finish\nID Selection\nPick multiple branches in the 3D graphical view.\nClear all\nRemove all of the elements to be split from the list.\n\n\n\nDetails Options\nSplit Pipe\nBranches to Split\nAdd Ce\nbranch to be split\nAdd Selected\nPick a pipe branch (or branches) to split\nesc\nID Selection\nClear all"}
{"Headers": "Pipe Isometric", "Content": "The Preview Isometric Drawing window is populated with an annotated and dimensioned isometric drawing of the pipe. A material list, title, pipe usage and explanation of the pipeline symbols.\n\n\n\n\nPreview Isometric Drawing"}
{"Headers": "System Isometric", "Content": "The Preview Isometric Drawing window is populated with an annotated and dimensioned isometric drawing of the CE (elements not currently displayed in the 3D graphical view are also added). A material list, title, pipe usage and explanation of the pipeline symbols.\nIf the currently selected element is a pipe with more than one branch, each branch displays on a different sheet.\n\n\n\n\nPreview Isometric Drawing"}
{"Headers": "Isometric Drawing Contents", "Content": "The content of each isometric drawing is calculated using complex algorithms to display all of the required data in the available space. the algorithms are controlled by Standard iso options selected before plotting the drawing.\nThe drawings are not to scale but display to show the information in the best way. Pipes with no components attached to them, at the end of the spool drawing, may even be abbreviated with just the annotation showing the length.l\nEach piping component in the Preview Isometric Drawing window is annotated and a symbol. The general format, annotations and dimensioning standard of the isometric drawing is governed by user in IsodraftI, refer to Using ISODRAFT for further information. The annotation data is also controlled by the selection made in the Spool module.\n\nPiping component annotations in the Preview Isometric Drawing window are governed by ISODRAFT. An example of some can be seen below:\nDimension\nValue display in dimensioning line break, or directed to line by arrow.\n\nSpool Number\nNumber in a double box with the spool prefix.\nArrow points at the first component in the spool.\nPart Number\nNumber in a rectangular box, along pipe or arrow pointing to component.\nFlanged components also show the Gasket (Gxx) and Bolt set (Bxx) numbers.\nWeld Number\nNumber in a circle\nKey for different types of weld displays on the plot.\nJoint Number\nNumber in a diamond, prefixed by letter showing type of joint.\nF = Flanged joint\nS = Screwed joint\nC = Compression joint\nRefer to the Piping Components in ISODRAFT for a full description of all of the symbols used in the plots.\nAnnotation\nKey\nRemarks\nDimension\nValue display in dimensioning line break, or directed to line by arrow.\nSpool Number\nNumber in a double box with the spool prefix.\nArrow points at the first component in the spool.\nPart Number\nNumber in a rectangular box, along pipe or arrow pointing to component.\nFlanged components also show the Gasket (Gxx) and Bolt set (Bxx) numbers.\nWeld Number\nNumber in a circle\nKey for different types of weld displays on the plot.\nJoint Number\nNumber in a diamond, prefixed by letter showing type of joint.\nF = Flanged joint\nS = Screwed joint\nC = Compression joint\n\n\n\nPreview Isometric Drawing\nUsing ISODRAFT\nPreview Isometric Drawing\nPiping Components in ISODRAFT"}
{"Headers": "Preview Isometric Drawing Window Toolbar", "Content": "The toolbar gives quick access to all the tasks associated with the Preview Isometric Drawing.\nDepending on the selections made from Preview Isometric Drawing toolbar, further windows are presented prompting for user input and options allowing for the workflow to continue.\nThe toolbar for the Preview Isometric Drawing displays as default when the Preview Isometric Drawing window displays.\n\nView the message file\nDisplays the Preview Isometric Messages window, where messages created during the generation of the isometric drawing can be viewed.\nSave As\nDisplays a Browser window, save the preview isometric drawing as a plot file.\nSave All\nDisplays a Browser window, save all the sheets of the preview isometric drawing as plot files.\nPrint Setup\nDisplays the printer settings.\nPrint Preview\nDisplays an on screen preview of the isometric.\nPrint\nPrints the currently selected preview isometric drawing.\nPrint All\nPrints all the sheets of the preview isometric drawing.\nHighlight On/Off\nHighlights all the display elements of the currently previewed isometric drawing sheet in the 3D View. Click again removes the highlighting.\nIf the elements are not currently displayed in the 3D View, click twice. The first click adds the elements to the 3D view, the second highlights the elements. Additional clicks turn the highlighting on and off. N.B. The highlighting only occurs if the Isometric Options file uses the Hitfile option.\nSheets drop-down list\nUse to navigate through the sheets of the isometric drawing.\n\nView the message file\nDisplays the Preview Isometric Messages window, where messages created during the generation of the isometric drawing can be viewed.\n\nSave As\nDisplays a Browser window, save the preview isometric drawing as a plot file.\n\nSave All\nDisplays a Browser window, save all the sheets of the preview isometric drawing as plot files.\n\nPrint Setup\nDisplays the printer settings.\n\nPrint Preview\nDisplays an on screen preview of the isometric.\n\nPrint\nPrints the currently selected preview isometric drawing.\n\nPrint All\nPrints all the sheets of the preview isometric drawing.\n\nHighlight On/Off\nHighlights all the display elements of the currently previewed isometric drawing sheet in the 3D View. Click again removes the highlighting.\nIf the elements are not currently displayed in the 3D View, click twice. The first click adds the elements to the 3D view, the second highlights the elements. Additional clicks turn the highlighting on and off. N.B. The highlighting only occurs if the Isometric Options file uses the Hitfile option.\n\nSheets drop-down list\nUse to navigate through the sheets of the isometric drawing.\n\nView the message file\nDisplays the Preview Isometric Messages window, where messages created during the generation of the isometric drawing can be viewed.\nSave As\nDisplays a Browser window, save the preview isometric drawing as a plot file.\nSave All\nDisplays a Browser window, save all the sheets of the preview isometric drawing as plot files.\nPrint Setup\nDisplays the printer settings.\nPrint Preview\nDisplays an on screen preview of the isometric.\nPrint\nPrints the currently selected preview isometric drawing.\nPrint All\nPrints all the sheets of the preview isometric drawing.\nHighlight On/Off\nHighlights all the display elements of the currently previewed isometric drawing sheet in the 3D View. Click again removes the highlighting.\nIf the elements are not currently displayed in the 3D View, click twice. The first click adds the elements to the 3D view, the second highlights the elements. Additional clicks turn the highlighting on and off. N.B. The highlighting only occurs if the Isometric Options file uses the Hitfile option.\nSheets drop-down list\nUse to navigate through the sheets of the isometric drawing.\n\n\n\nPreview Isometric Drawing\nPreview Isometric Drawing\nPreview Isometric Drawing\nPreview Isometric Drawing\nView the message file\nPreview Isometric Messages\nSave As\nBrowser\nSave All\nBrowser\nPrint Setup\nPrint Preview\nPrint\nPrint All\nHighlight On/Off\nSheets drop-down list"}
{"Headers": "Non Standard Branch Connections Isometrics", "Content": "Any non standard branch connection\u2019s position and type of connection are displayed as a detailed plot with a localized view in the Preview Isometric window.\n\n\n\n\n\nPreview Isometric"}
{"Headers": "Pipe Router", "Content": "The Pipe Router utility is a rule-based tool which automatically route multiple or single pipes. If non-orthogonal pipes are required, these can be created manually, refer to for further information.\nThe pipe(s) are routed, from the branch\u2019s head and ends at the branch\u2019s tail, positioning and orientating piping components (reducers and welds), and where appropriate adding connection components such as flanges and gaskets. The flow direction is always forwards (from head to tail). The pipes are created orthogonally and with the minimum number of bends or elbows and where possible clash-free.\nConstrain the route taken by the pipe(s) with the use of routing points, planes, rules and pipe racks and if required, modify the route once it has been created. Refer to Automatic Pipe Route Administration for further information.\nAll the tasks carried out in association with the Pipe Router utility are initiated from a central Pipe Router window which acts as a task hub.\n\nDefaults\nThe pipe router is supplied with defaults which can be modified if required.\n\nUse the File menu from the Pipe Router Defaults window, to save settings or load from settings from elsewhere, see System Administrator if new settings are required:\n\nThe Pipe Router Defaults window, contains all the tools to determine the defaults for the pipe router.\nThe Output messages to file fields, Directory and Filename specifies where to save and what to name the error messages file. The option to overwrite or add to the end of existing error file by selecting an option from the drop-down list is also available.\nTo remove the output message once a session check has been completed, click to select the Remove Message file at the end of session check box.\nTo specify what the Pipe Router does in the event of an error, from the Action on error drop-down list: select one of the available options.\nStop\nStops all further routing\nContinue\nContinues the routing even if an error occurs\nPause\nAn alert window is displayed, it must be acknowledged before the routing continues\nStop\nStops all further routing\nContinue\nContinues the routing even if an error occurs\nPause\nAn alert window is displayed, it must be acknowledged before the routing continues\nTo specify which component is used when the routing changes direction, from the Change direction using drop-down list select one of the available option.\nBend\nWhen a change of direction occurs, a bend is included in the routing and displays in the design database and 3D graphical view\nElbow\nWhen a change of direction occurs, an elbow is included in the routing and displays in the design database and 3D graphical view\nRule\nPipe Router searches for a rule which defines the type of component to use. To create this type of rule, refer to for further information.\nBend\nWhen a change of direction occurs, a bend is included in the routing and displays in the design database and 3D graphical view\nElbow\nWhen a change of direction occurs, an elbow is included in the routing and displays in the design database and 3D graphical view\nRule\nPipe Router searches for a rule which defines the type of component to use. To create this type of rule, refer to for further information.\nSpecify a default rule set from the Default rule set world drop-down list for all the branches created by Pipe Router which is automatically assigned as a low priority rule set. Here you or system administrator can create company and/or project specific rule sets. Refer to for further information.\nOnce the rule set has been specified define to what the rule set is applied, from the Applied to all drop-down list, select the required design hierarchy element.\nPipe Router automatically searches for and makes use of any routing planes and pipe racks with a branch to route the pipe on. The pipe racks exist within the search volume of a branch or branches, the default search volume is the volume between the head and tail of a pipe. The search can be extended outside this volume by inputting the distances in the In Z Direction (vertical) and In X/Y Directions (horizontal) fields.\nPipe Router automatically uses a routing plane or pipe rack to route a pipe only if the distance that it travels along the plane or rack is greater than a minimum travel distance. Enter the minimum distance, in the Minimum Travel Distance field.\nSpecify the minimum Pipe gap between pipes on racks (and other planes), and also specify in the Pipe gap rounding field the extent to which the gap size is rounded, which can help minimize construction errors.\nDefine a Route\nCreate the pipe and branch elements in the design hierarchy and connect or position their heads and tails and define bore. If the branch contains piping components, these must be selected. Refer to and for further information.\nRouting Pipes\nAdd the pipes to the Pipe Router window, and then route the pipes, Pipes can be added individually or in groups.\nBy default, the Pipe Router routes pipes in the order in which they are added to the Pipe Router window. The routing order can have an effect on the route taken by pipes. Refer to for further information. Pipe Router routes the selected pipes, adding elbows, gaskets and flanges, as required.\n\nWhen a pipe is added to Pipe Router, it is given a head and tail work-point. These are the points where a route begins and ends. Pipe Router positions work-points at a distance from the branch head or tail which allows for any connection components that are required.\n\nFor example, if the head of a branch is a flanged nozzle, then Pipe Router automatically adds a gasket and a flange. Pipe Router then begins routing the pipe from the end of the flange.\nHow Pipe Router Finds a Route\nThe Pipe Router creates a route using an algorithm which minimizes material cost while avoiding clashes with other objects. The algorithm has three modes of operation, described as Level 1, Level 2 and Level 3 modes. Pipe Router first searches for a route using Level 1 mode. If no clash-free Level 1 route is found, a search is made using Level 2 mode, and if no Level 2 route is found Level 3 mode is used.\nLevel One Mode\nIn level one mode, Pipe Router searches for an orthogonal route between the head and tail work-points of a pipe, using the minimum number of bends or elbows. Lever One routes (Box 3) shows examples of the routes available in level one mode.\nBox 1\nThe default route is ABC, as this requires only two bends. If this route is blocked, Pipe Router attempts to route ADE which uses three bends.\nBox 2\nIf Pipe Router cannot find a route using the routes on box one, it attempts the routes on box two, where route ABC uses three bends, and ADE uses four bends.\nBox 3\nFinally, if it is still unsuccessful in finding a route, Pipe Router attempts the routes on box three, where both routes use four bends.\nBox 1\nThe default route is ABC, as this requires only two bends. If this route is blocked, Pipe Router attempts to route ADE which uses three bends.\n\nBox 2\nIf Pipe Router cannot find a route using the routes on box one, it attempts the routes on box two, where route ABC uses three bends, and ADE uses four bends.\n\nBox 3\nFinally, if it is still unsuccessful in finding a route, Pipe Router attempts the routes on box three, where both routes use four bends.\n\nAn example of a Level One route displays a level one route in which the head work-point is facing up.\n\nLevel Two Mode\nIf all first level routes are blocked, Pipe Router attempts to find second level routes. In second level mode, Pipe Router withdraws the route into the box by a distance which enables the pipe to bypass the obstruction. Pipe Router then attempts the same routing patterns as those used in level one mode.\n\nLevel Three Mode\nIf Pipe Router cannot find a clash-free route using first and second level routes, it attempts to find a third level route. In third level mode, Pipe Router extends the box outwards until it bypasses the obstruction and then attempts to route the pipe using level one routing principles.\n\nAdding Components to a Route\nOnce Pipe Router has worked out a route, it constructs the Branch by adding whatever Elbows (or Bends) are needed.\nSpecify components in a Branch before routing, for example by importing a P&ID file as described in . Modify a routed Branch by adding other components, for example, Valves or Instruments, on the Piping tab, in the Modify group, click Component to display the Piping Component Editor window and create the components in the normal way.\nOnly the principal piping components need to be added. Pipe Router adds Flanges, Gaskets, lap joint stub ends and Welds as necessary, using the Connection Compatibility (COCO) tables to create the correct types.\nComponents can be locked into a given position, in which case they are not be moved, even if the Branch is re-routed. Refer to for further information about using locked components.\nIf there are particular constraints that must be placed on a Branch, for example, passing through a given point or plane, use one of the techniques described in .\nInsertion of Reducers at Bore Changes\nBefore Pipe Router positions any components on a Branch, it checks the Branch to see if it contains any components whose bore is different from the preceding component. If one is found, then by default the Pipe Router selects the first suitable Reducer that it finds in the catalog, regardless of whether it is concentric or eccentric.\nSet rules to specify whether concentric or eccentric Reducers are used. For information about routing rules, refer to for further information.\nHow Pipe Router Routes to Free Tails\nIf a Branch has a free Tail, that is, if the Tail is not connected to another Branch or the Tail position has not been specifically defined, Pipe Router automatically positions the Tail once it has positioned all of the components in the Branch and applied all constraints.\nIf this fails, for example, because there is a clash or a component positioning rule cannot be satisfied, then it introduces an Elbow after the constraint, before the first component. Pipe Router then positions the elbow in a direction that results in a clash-free route, and which satisfies component positioning and orientation rules.\nIf the Branch does not have any constraints, the position of the Tail depends on the position and orientation of the Branch Head. Often, this may be a Tee. Refer to for further information.\nTail direction: The TDIR attribute for a free tail is never set if the last constraint is a plane or a rack. In all other cases, TDIR is taken from the direction of the last component.\nHow the Pipe Router Positions Tees\nPipe Router checks each Branch for connections to other Branches, that is it looks for Tees or other components which have a CREF or CRFA attribute set.\nIf the Branch which connects to the Tee has a free Tail, then the Tee is treated the same as any other component.\nIn all other cases, the Tee influences the route taken by the original Branch. In general, Pipe Router selects the closest route to any constraints in the connecting Branch. If there are none, then it selects the route closest to the other end of the connecting Branch.\nTees which can be balanced are then positioned. Refer to for further information.\nWhere a Branch contains more than one Tee, the first Tee in the Branch influences the route taken. Pipe Router positions any subsequent Tees as close as possible to the next constraint, or the other end of the connecting branch.\nControl the position of a Tee by locking it in position, or by constraining the route, using a routing point. Refer to for further information.\nBalanced Tees\nPipe Router attempts to position a Tee to achieve balanced flow.\nThe Tee must be symmetric about a plane through P-arrive. The Pipe Router changes the arrive p-point to achieve this if the bores on the p-points are equal. It then checks the leave-bore and connect-bore. If the bores are equal then Pipe Router assumes that the Tee is T-shaped.\n\nThe Tail directions of /B1 and /B2 must either be equal and not in the axial direction between the Tail positions of the branches or opposite and in the axial direction between the Tail positions of the branches:\n\nThere must be no locked components on branch /B2, nor any after the Tee on branch /B1.\nIf there are multiway components in the Branches after the Tee, the Branches connected to them:\nThe Tail positions of /B1 and /B2 must be equal in two of the three orthogonal co-ordinates:\n\nThe specifications of the positionable components after the Tee on /B1 must be the same as the specifications of the components on branch /B2.\n\nThe Tee is positioned so that:\nIf any of these conditions are not satisfied, Pipe Router attempts moving the Tee back along the arrive direction (or forward along the leave direction).\nCovered Nozzles\nWhen the Pipe Router is routing a Branch there may be several others waiting to be routed. The best route for the current Branch may take the Pipe straight in front of other Nozzles, which is most likely to happen when routing from a line of Vessels. It can be avoided by:\nRefer to for further information.\nMake sure the Nozzles or Equipment owning them have obstruction volumes extending beyond their Nozzles which prevents other Pipes crossing in front of the Nozzle. The Branch connected to the Nozzle ignores this clash and successfully routes onto the Nozzle.\nConstraining a Route\nExcept in very simple cases, give Pipe Router more information about the route required to achieve a satisfactory route, then constrain a route using the following:\nThese constraints are described briefly in the following sections, and described in detail in later sections.\nLocked Components\nA locked component is a component whose position has been fixed before routing takes place. Pipe Router routes the Branch through the component. Locked components can be used to manually modify the route taken.\nIn cluttered areas, Pipe Router may not be able to find a clash-free route, in which case it puts in the simplest clashing route and informs you of the clash. Modify the route to obtain a clash-free route, by moving components away from clashes, locking them and re-routing. Both principal Piping components and router-created components (for example, Elbows), can be moved and locked.\nRouting Rules\nOne of the principal features of Pipe Router is its built-in rule engine. Use routing rules to control the selection, position and orientation of piping components, and to control how pipes use routing planes and pipe racks. Refer to for further information.\nRefer to Automatic Pipe Route Administration for further information about creating your own rules.\nRouting Points\nRouting Points are points through which a pipe must pass. Specify the position of a routing point, and the direction in which a pipe arrives at and leaves a routing point. Refer to for further information.\nRouting Planes\nRouting planes are orthogonal planes which attract pipes to them and then guide the pipes in the direction of the plane. Routing planes are useful, for example, where to group pipes together, perhaps along a wall or ceiling. Refer to for further information.\nPipe Racks\nIn Pipe Router, a pipe rack is composed of a group of routing planes which enables the modelling of the route used on a physical pipe rack. There are two ways in which to create a pipe rack. Create pipe racks on existing steelwork structures or model them as a group of planes.\nFind the second method useful when working on a conceptual design and does not want to spend time creating steelwork structures. Once a pipe rack has been created, use routing rule to specify how different sorts of pipe run on the rack. Refer to for further information.\n\nChecking the Status of a Branch\nOnce the pipe(s) have been routed, check the status of the branch, by selecting Display > Status Summary, the Pipe Router Status Summary window shows that two Branches have been routed successfully.\n\nChanging the Order in which Pipes are Routed\nPipe Router routes pipes in the order in which they are added to the Pipe Router window. However you may need to change the routing order of particular pipes to make sure that Pipe Router routes the most expensive pipes first. Or if working with pipes that are in close proximity to one another or where pipes cross paths.\nChange the routing order, by selecting from a choice of options in the Modify > Routing Order > from the Pipe Router window.\nTo reorder pipes according to their specification, select Group by specification check box, the display is reordered in alphabetical order of their specification names, for example, all pipes which use the specification A150, followed by all pipes which use the specification B150, and then the other pipe specifications in the sequence. Use this option in conjunction with the attribute radio buttons.\nFor example, reorder pipes so that all Pipe Router displays all pipes which use the specification A150 in descending order of their head bore, followed by all B150 specification pipes.\nRouting Messages\nAs Pipe Router routes a pipe, it examines each branch and generates a message about any routing errors that it finds. These messages can help you understand and correct errors. It can view these messages both during and after pipe routing, providing you have set up a file in which to store the messages, as described previously.\nTo view routing messages, select Display > Routing Messages from the Pipe Router window to display the Routing Messages window.\n\nThe Routing Messages window is empty if Pipe Router routes all pipes without any errors.\nSelect Control > Close to close the Routing Messages window.\nBranch Detail Window\nPipe Router enables you to view details of the components and constraints in a branch using the Branch Detail window. Select options to constrain the route taken by a branch.\nFor example, lock components in position, create routing points and add routing planes and pipe racks to the constraint list. All of these facilities are explained in later sections.\nSelect one of the routed Branches from the Pipe Router window and click Branch Detail to display the Branch Detail window, which contains details of the selected branch.\n\nRefer to for more information on the contents of the Branch Detail window.\nPositioning and Locking Components\nAdd components to Branches after they have been routed and control where the components are positioned. The effect that positioning and locking components has when a Branch is re-routed is also considered.\nDeletable, Positionable and Locked Components\nPipe Router sees all piping components as deletable, positionable or locked. If the Branch Detail window displays for a Branch that has been routed by the Pipe Router, all the components are listed as deletable.\nThe components that Pipe Router creates in a Branch are described as Deletable. If the branch is re-routed, Pipe Router deletes all the components that it has created and re-create them.\nAfter a Branch has been routed, components can be added manually in the normal way. Select the correct element in the Branch Members list, on the Piping tab, in the Create group, click Component to display the Piping Component Editor window. These components are described as Positionable. If the Branch is re-routed, these components are not deleted, but they may be moved to fit on the new route.\nPositionable components can be locked into a given position, in which case they are not moved, even if the Branch is re-routed.\nThe order of Positionable components in the Branch Members list is maintained, and so is their order relative to any constraints in the Branch. For example, if a Valve is added before a Locked Tee, the Valve is not be moved past the Tee.\nTo make changes to a Branch, and then re-route it, keeping some or all of the components that Pipe Router has added by making them positionable, rather than deletable. These can also be locked.\nTo change the status of a component, select it from the list on the Branch Detail window, and then select one of the options under the Modify menu on the window.\n\nThe choices are: Constraint, Toggle Head Lock, Toggle Tail Lock, Lock Position, Make Positionable, Make Deletable, Toggle Head/Tail Relative, Head W-P, and Tail W-P.\nPositioning Relative to the Head or Tail\nEach component in a branch is positioned relative to the head or tail of the branch. If a component is head relative, then Pipe Router places that component as close as possible to the head of the branch, allowing for other components and any constraints. If a component is tail relative, then that component is positioned as close as possible to the tail of the branch.\nPipe Router routes a pipe from head to tail and so all components are initially created head relative.\nChange the head/tail relative property of any positionable component. Select it in the list on the Branch Detail window, and then select Modify > Toggle Head/Tail Relative.\nHead and Tail Work-points\nEach Branch has a Head Work-point and a Tail Work-point. insert components between the Head (or Tail) and its work-point, which can be used, for example, to position a Valve directly onto a Nozzle.\nMoving the Head or Tail Work-point\nPosition the Head W-P after a particular component in a Branch or position the Tail W-P before a particular component, which enables the Valve to be positioned directly onto the Nozzle of vessel /VESS-1, then re-route the Pipe without affecting the position of the Valve.\nFrom the Branch Detail window, select Modify > Tail W-P to display the Modify Tail W-P window.\n\nFrom the Modify Tail W-P window, select VALVE 1, click OK.\nFrom the Pipe Router window, select the Route: Selected option.\n\nPipe Router re-routes the Pipe from the Head Work-point to the Tail Work-point, which is now positioned before VALV 1.\nCheck the position of the valve, display the Branch Detail window for the branch, then scroll to the bottom of the Components/Constraints list to display the details.\n\nLocking and Unlocking a Component\nPipe Router enables piping components to be locked in position, to make sure that a branch component remains in its current position, even if the branch is re-routed.\nTo lock a component, from the Branch Detail window, select the component to be locked in position, select Modify > Lock Position.\nTo unlock a locked component, select Modify > Make Positionable for main piping components, or Modify > Make Deletable for Pipe Router generated components.\nManually Routing Non-orthogonal Sections\nPipe Router is an orthogonal router so if non-orthogonal sections of pipe in a branch are required. Route these sections by hand and then lock all the components in the section (including the start and end bend or elbow) and route the remainder of the pipes using Pipe Router.\nAligned, Locked, Non-orthogonal Components\nIf two locked components with non-orthogonal arrive and/or leave direction are aligned, with no intervening components, so that a straight piece of tube can run between them without clashing, Pipe Router uses this route, which also happens if the first component is aligned with the head or the last component is aligned with the tail. If the straight, non-orthogonal routes clash, only orthogonal routes are considered to avoid the clash.\nThe default orthogonal route between the pump and the vessel.\nUsing aligned and locked elbows to give a non-orthogonal route.\n\nThe default orthogonal route between the pump and the vessel.\n\nUsing aligned and locked elbows to give a non-orthogonal route.\nIn all other cases Pipe Router attempts to insert a bend or elbow to turn into an orthogonal direction as close as possible to the component.\nNon-aligned Non-orthogonal Components\nIf non-orthogonal components are not aligned, only orthogonal routes between them are considered.\nNon-aligned components still give an orthogonal route.\n\nNon-aligned components still give an orthogonal route.\nNon-orthogonal Sections with Unlocked Components\nIf there are other, positionable, components between non-orthogonal locked components, orthogonal routing is used. Pipe Router may add connection components on to the locked components, but note that no bore change (which would require the addition of a reducer) is permitted.\nA positionable Tee has been inserted in the Branch, which has caused Pipe Router to revert to an orthogonal route, using additional Elbows.\nDetail of the area close to the Tee.\nThe route achieved with the Tee Locked.\n\nA positionable Tee has been inserted in the Branch, which has caused Pipe Router to revert to an orthogonal route, using additional Elbows.\n\nDetail of the area close to the Tee.\n\nThe route achieved with the Tee Locked.\nLock several non-orthogonal components in a row. For example, lock two 45 degree elbows to give a non-orthogonal section of pipe and place a locked valve on this section of pipe. Pipe Router does not route any part of the Branch between the elbows, providing that straight pipe does not clash; and it adds any necessary connection components to the valve. However, the valve must be locked: if it is positionable Pipe Router routes orthogonally between the elbows.\nIt may be better to continue in a non-orthogonal direction from a nozzle until a route has passed an obstruction, because this might give a shorter route with fewer elbows. Lock the elbow at \u2018A\u2019 to give this route:\n\nUsing Rules for Minimum Tube Length\nTo find that components such as Olets and Stub-in Tees are positioned immediately next to another component, if the COCO tables allow. Use the Upstream and Downstream Rules provided with Pipe Router to specify minimum lengths of Tube. Refer to for further information about using rules.\nCreate and Use Routing Points\nRouting Points can be used to constrain a route, these points are points through which a branch passes. To define the coordinates of a point and the direction in which a branch arrives at and leaves a point.\nTo add as many routing points as required but the points must be created at the correct position in the sequence of constraints.\nCreate a Routing Point\nTo create a routing point, select the required branch from the Pipe Router window, select Branch Detail to display the Branch Detail window. From the Branch Detail window, select Create > Routing Point to display the Create Routing Point window.\n\nTo enter the coordinates on the Create Routing Point window or use the other options available on the menu, which are similar to the normal AVEVA E3D\u2122 positioning options. Routing points can only be positioned after positionable or locked components.\nBy specifying a different arrive and leave direction, a bend or elbow has to be inserted at the position of the routing point. If a change of direction is not required, select the Through Direction and specify the direction for the pipe to take at that point. If the direction is unset, Pipe Router selects the best direction to minimize the number of bends or elbows used.\nUse DATUMs as Routing Points\nThere is an option on the Create Routing Point window which allows you to use an existing DATUM point as a routing point. Two branches should not use the same Datum point as a constraint since they would then clash.\nIf you wish to use a Datum where two branches meet, just one of the branches should have the point as a constraint. For example, Branch /P1/B1 ends at a Battery Limit and Branch P2/B1 connects to its Tail. Branch /P1/B1 should have the Datum as the last constraint and a Free Tail. The Head of Branch /P2/B1 is positioned at the Tail of /P1/B1.\nMoving a Routing Point\nTo modify the position of a routing point at any time. From the Pipe Router window, select the branch to modify, click Branch Detail to display the Branch Detail window.\nSelect the routing point to modify from the Components/Constraints list. Select Modify > Constraint to display the Modify Routing Point window. Select one of the following options, depending on the type of modification:\nMove > Distance\nTo move a routing point a distance in a specified direction either from the current location, or relative to another element which can be identified using the cursor or another method.\nMove > Towards\nTo move the point a specified distance towards another element, which can be identified using the cursor, by specifying a named element or, which may be the head, tail or, the next element in the branch.\nIf a DATUM has been used as a routing point, the standard AVEVA E3D\u2122 positioning options can be used to modify its position.\nRouting Rules\nRouting Rules are special AVEVA E3D\u2122 rules which are used to control how components are selected, positioned and orientated as Branches are routed and how Pipes are packed on Pipe Racks and Routing Planes.\nUse the sample routing rules supplied with the Pipe Router, or define routing rules refer to Automatic Pipe Route Administration for further information.\nRouting rules can be applied to individual branches or all branches within a particular site, zone, or pipe. Rules can be applied or removed to individual components, as required.\nExpressions\nA routing rule consists of AVEVA E3D\u2122 expressions. AVEVA E3D\u2122 expressions are described in detail in .\nAVEVA E3D\u2122 expressions consist of the following:\nFor a list of AVEVA E3D\u2122 attributes, refer to for further information.\nApply a Rule Set to a Branch\nOnce a rule set has been created, it can be applied to a branch. The rules then take effect on the components in the branch. From the Pipe Router window, select the branch with which you want to associate a rule set.\nFrom the Pipe Router window, select Settings > Apply Rules > To Branch to display the Apply Rules to SELECTED window.\n\nFirst select the rule world which contains the rule sets to apply to the branch from the RULE WORLD list, which contains all the Branches selected on the Pipe Router window. From the Rule sets available in current world list, select the rule set. The rule set can be added as high priority or low priority.\nClick Add HIGH to add the rule set to the High Priority Sets list or Add LOW to add the rule set to the Low Priority Sets list. Click Apply. You must then route the branch to apply the rules.\nPipe Router first checks to see if there are any rules that apply to a component from the high priority rule sets. If there are none then Pipe Router checks if there are any rules that apply in the low priority rule sets.\nFrom the Settings > Apply Rules options on the Pipe Router window applies the rule sets to a site, zone or pipe. In these cases all branches which are below them in the hierarchy also have the rule sets applied, unless they have rule sets specifically applied.\nBy default, Pipe Router applies all the rules in the specified sets to a branch, providing they are appropriate. However, to remove a rule from a particular component in a branch, or add one from another rule set.\nRemove a Rule Set\nTo remove a rule set, first select the branch from the Pipe Router window, then select Settings > Apply Rules > To Branch to display the Apply Rules window, the rule set to be removed must be selected. Click Remove HIGH or Remove LOW as appropriate. Click Apply.\nIf a Rule Set is applied to a Pipe, Site or Zone, it is removed from all Branches in that Pipe, Site or Zone.\nInclude a Rule from another Rule Set or World\nIf required, apply a rule to a component from another rule world or rule set, from the Pipe Router window, select the branches to apply the rule to, click Branch Detail. From the Branch Detail window, click Component Rules to display the Component Rules window, which can be used to add additional rules from the available rule sets, or from another rule world.\n\nFrom the Rules applying to current component list, select the component that the rule is applied to.\nThe letter that precedes the rule description shows where the rule was originally applied. The letters used are:\nFrom the Rules available list, select the rule to be applied to the selected component, then click Include. The rule is added to the list of rules which apply to the component. Click Dismiss to close the Component Rules window.\nDisabling a Rule from a Component\nToprevent Pipe Router from applying a rule to a particular component in a branch, from the Pipe Router window, select the branch which contains the component. Click Branch Detail to display the Branch Detail window. From the Branch Detail window, select the component to be excluded from the rule. Click Component Rules to display the Component Rules window.\nFrom the list of rules that apply to the current component, select the rule to disable from the component, then click Disable. Pipe Router places an asterisk (*) to the left of the rule description to indicate that the rule is now excluded from being used.\nTo re-enable a disabled rule, select the rule, the"}
{"Headers": "Automatic Pipe Route Administration", "Content": "Routing Rules are special AVEVA E3D Design rules which are used to control, for example, how Pipe Router selects, positions and orientates components as Branches are routed, and also how Pipes are packed on Pipe Racks and Routing Planes.\nYou can apply routing rules to individual branches or all branches within a particular site, zone, or pipe, and you can also apply rules to individual components and remove rules from individual components, as required.\nRouting Rule Purposes\nThere are different types of routing rules , which are used for different controls on the route. Rules are identified by their Purpose (PURP) attribute, and unlike other elements in AVEVA E3D\u2122, you cannot create different, user-defined purposes for routing rules.\nThe routing rules available are listed below, identified by their PURP attribute, and with a short description. The purpose is set to a four-letter code, but it sometimes displays as a more descriptive text on the AVEVA E3D\u2122 Router windows. How each rule is applied is described in detail in .\nPRPR\nAll rules with this Purpose are executed before a Branch is routed.\nSelection\nBEND\nBend or elbow selection: controls whether a bend or elbow is used for changing the direction of a pipe\nREDU\nReducer type: specified when concentric or eccentric reducers are used\nPositioning\nDNSM\nDownstream pipe requirement: the length of pipe required downstream to the next component\nUPSM\nUpstream pipe requirement: the length of pipe required upstream from the previous component\nELEV\nComponent elevation: absolute or relative elevation of a component\nLOCA\nComponent location: 3D position of a component\nOrientation\nMAJO\nOrientate on major axis: positioning on vertical or horizontal pipe segment.\nMINO\nOrientate on minor axis: such as the orientation of a handwheel\nClash exclusion\nCLEX\nThese rules are used to allow specified types of element to clash.\nPipe racks (and routing planes)\nTRAV\nPipe Rack travel plane selection: controls which pipe rack travel plane is used to route a particular type of branch\nENTR\nPipe Rack entry plane selection: controls which pipe rack entry plane is used to route a particular type of branch\nEXIT\nPipe Rack exit plane selection: controls which pipe rack exit plane is used to route a particular type of branch\nSHOE\nShoe height requirement\nWEIG\nIdentify heavy pipe\nADGP\nExtra gap required on plane or rack\nFLWI\nFlange width on plane or rack\nPost-processing\nPOPR\nAll rules with this Purpose are executed after a Branch has been routed.\nPRPR\nAll rules with this Purpose are executed before a Branch is routed.\nSelection\n\nBEND\nBend or elbow selection: controls whether a bend or elbow is used for changing the direction of a pipe\nREDU\nReducer type: specified when concentric or eccentric reducers are used\nPositioning\n\nDNSM\nDownstream pipe requirement: the length of pipe required downstream to the next component\nUPSM\nUpstream pipe requirement: the length of pipe required upstream from the previous component\nELEV\nComponent elevation: absolute or relative elevation of a component\nLOCA\nComponent location: 3D position of a component\nOrientation\n\nMAJO\nOrientate on major axis: positioning on vertical or horizontal pipe segment.\nMINO\nOrientate on minor axis: such as the orientation of a handwheel\nClash exclusion\n\nCLEX\nThese rules are used to allow specified types of element to clash.\nPipe racks (and routing planes)\nTRAV\nPipe Rack travel plane selection: controls which pipe rack travel plane is used to route a particular type of branch\nENTR\nPipe Rack entry plane selection: controls which pipe rack entry plane is used to route a particular type of branch\nEXIT\nPipe Rack exit plane selection: controls which pipe rack exit plane is used to route a particular type of branch\nSHOE\nShoe height requirement\nWEIG\nIdentify heavy pipe\nADGP\nExtra gap required on plane or rack\nFLWI\nFlange width on plane or rack\nPost-processing\n\nPOPR\nAll rules with this Purpose are executed after a Branch has been routed.\nHow Routing Rules are Constructed\nRouting rules consist of AVEVA E3D\u2122 expressions which define:\nAll rules must have a selection expression.\nRules which use logical expressions are called logical rules. A Rule which does not have a logical expression is called a real rule, because its action (see below) is a real expression.\nActions\nThe Logical expression in a rule tests whether or not the component satisfies the rule. If not, that is, if the logical expression evaluates to False, and the rule has an action, the action is applied. Pipe Router then re-tests the component. If the logical expression still evaluates to False, the Action is reversed.\nIf you do not define an action for these rules, then the default action is taken, which depends on the rule.\nUsing PML Functions in Routing Rules\nThe Logical and Action expressions in Routing rules can call PML functions, which allows you to define much more complex logical tests and actions than can be done using simple expressions. A function is called by setting the rule action to a text string which is the name of the .pmlobj file. The file contains the object definition, followed by a method definition.\nThe function must be defined using fixed names for the following elements:\nCEREF\nThe DBREF of the element the rule applies to.\nRESULT\nThe returned boolean result. (Logical parts of rules only.)\nRULEMETHOD\nThe method which is applied.\nOBSREF\nThe DBREF of the Element clashing with the Branch. (Clash exclusion rule only).\nCEREF\nThe DBREF of the element the rule applies to.\nRESULT\nThe returned boolean result. (Logical parts of rules only.)\nRULEMETHOD\nThe method which is applied.\nOBSREF\nThe DBREF of the Element clashing with the Branch. (Clash exclusion rule only).\nExamples of calling PML functions are given in the following sections:\nPre-processing rules\nRefer to for further information.\nMinor Axis orientation\nRefer to for further information.\nClash exclusion\nRefer to for further information.\nPost-processing rules\nRefer to for further information.\nPre-processing rules\nRefer to for further information.\nMinor Axis orientation\nRefer to for further information.\nClash exclusion\nRefer to for further information.\nPost-processing rules\nRefer to for further information.\nHow Routing Rules are Applied\nThe following sections describe in detail which expressions are required by each type of rule, and how the rules are applied. Most of the examples are taken from Rules supplied with the product. To see more examples, select Settings > Routing Rules from the Pipe Router window, which displays the Routing Rules window. Select a Rule Set, then select a Rule from the list. To see the expressions in the rule, select Modify to display the Rule Attributes window.\nPre-processing (PRPR)\nLogical, will have Action\nPre-processing (PRPR)\nLogical, will have Action\nAll rules with this Purpose are executed before a Branch is routed. The Action is normally a PML function, which must have been defined before the rule is applied.\nTypically this type of rule is used where it is simpler to have a single rule to create, position and orientate several components rather than have individual rules. For example:\nThe Selection part of the rule identifies a key component: for example, you can identify Valves which require control loops by setting a UDA to a certain value, and then setting the selection expression to select all the Valves with the given attribute value.\nThe PML function then creates, positions and orientates the components and finally sets the head working point attribute to the last component covered by the rule. AVEVA E3D\u2122 Router then takes over and routes the Branch.\nA suitable PML function displays following. Note that at the end of the positioning and orientating commands, the RLOC attribute is set to 0 (Locked).\nThe input to Pipe Router would be Pipes with a main Branch with the following sequence of components defined:\nThere would also be a second Branch, owning a Valve, with the Branch Head and Tail connected to the two Tees in the main Branch, which form the control loop.\nThe rule to call function displays and can be defined:\n\nThe rule is applied to the elements required in the normal way. An example of the control loop created displays in the following picture.\n\nSelection\nBend or elbow selection (BEND)\nLogical, no Action\nBend or elbow selection (BEND)\nLogical, no Action\nUsed to choose the type of component used to change direction. For example, the selection expression can be:\nand the logical:\nmakes sure that all Branches with bores less than or equal to 65 use Bends rather than Elbows.\n\nThe default method of changing direction, set on the Pipe Router Defaults window, is using Elbows.\n\nThe default method of changing direction, set on the Pipe Router Defaults window, is using a Rule. The rule specifies that small bore pipes change direction using Bends\nReducer Selection (REDU)\nLogical, no Action\nReducer Selection (REDU)\nLogical, no Action\nTo specify whether concentric or eccentric reducers are selected. For example, if the default reducers in a specification are eccentric, and you want concentric reducers in vertical sections of pipe but eccentric reducers in horizontal sections, the Selection expression in the rule can be:\nThe logical expression to specify eccentric reducers in all the selected cases would be:\n      \n         \n            \n               \n                  \n                \n               \n                  \n                \n            \n            \n               \n                  The default reducer in the Specification is eccentric.\n                \n               \n                  The rule specifies that reducers on vertical legs are concentric\n                \n            \n         \n      \n   \n\n\nThe default reducer in the Specification is eccentric.\nThe rule specifies that reducers on vertical legs are concentric\nPositioning\nThere are two pseudo-attributes which are particularly useful in positioning expressions:\nSTAP\nis the length of straight tube before the component.\nSTLE\nis the length of straight tube after the component.\nSTAP\nis the length of straight tube before the component.\nSTLE\nis the length of straight tube after the component.\nThe lengths are measured from the component up to one of the following:\nDownstream pipe requirement (DNSM)\nLogical, can have Action\nDownstream pipe requirement (DNSM)\nLogical, can have Action\nUsed to control the length of straight pipe which is downstream from the previous component. If the rule logical fails, the action, if it exists, is applied. The action should be an expression that moves the component a distance from the previous to make sure a straight length of pipe. For example:\nSelection\nLogical\nYou can omit the action by setting the Action field on the window to unset, but the result may be unpredictable, particularly if other rules are being applied, and it is not recommended. If no action exists, and component positioning is head relative, the component is moved 2/3 the distance along the leg, and then re-tested. If component positioning is tail relative, the preceding component is moved if necessary when it is positioned.\nA Tee is positioned by default.\nThe rule is applied and the Tee is moved 2/3 of the distance along the leg between the Elbow and the Routing Plane\nUpstream pipe requirement (UPSM)\nLogical, can have Action\n\nA Tee is positioned by default.\n\nThe rule is applied and the Tee is moved 2/3 of the distance along the leg between the Elbow and the Routing Plane\nUpstream pipe requirement (UPSM)\nLogical, can have Action\nThe rule controls the length of straight pipe which is upstream from the next component.\nSelection\nLogical\nAn example of an action is:\nwhere the POLAR AXES keywords are used to specify a position in terms of a distance in a given direction from a point, and PREVPP is the previous p-point.\nYou can omit the action by setting the Action field on the window to unset, but the result may be unpredictable, particularly if other rules are being applied, and it is not recommended. If no action exists, and component positioning is tail relative, the component is moved 1/3 of the upstream distance, and then re-tested. If component positioning is head relative, the following component is moved if necessary when it is positioned.\nElevation (ELEV)\nLogical, can have Action\nElevation (ELEV)\nLogical, can have Action\nThe rule controls the elevation of a component. The following example uses the CLOSEST keyword in the logical expression to specify that components must be positioned at a height greater or equal to 0.61m vertically above an EQUI whose purpose is FLOO.\nSelection\nLogical\nA position on the closest vertical segment of pipe equal to the required elevation is found. If no position on the existing pipe can be found, the action is applied with the position adjusted to minimize the use of bends or elbows.\nIf the logical test is False, any action set is applied.\nLocation (LOCA)\nLogical, can have Action\nLocation (LOCA)\nLogical, can have Action\nUsed to position a component at a given location. The following example is a test for a component in a sub-branch being positioned at p-point 4 of the connecting component in the owning branch:\nIf the logical test fails, the action is applied and the test repeated. If it fails again, a message is output.\nThe corresponding action expression would be:\nTo position the component at p-point 4 of the connecting component in the owning branch.\nOrientation\nMajor axis\nLogical, no Action\nMajor axis\nLogical, no Action\nControls the major orientation of the component, which is the arrive/leave axis. For example:\nIf this fails, the component is moved to each leg in turn until one is found that passes. No action is allowed.\nMinor axis\nLogical, can have Action\nMinor axis\nLogical, can have Action\nControls the minor orientation of a component, which is the axis perpendicular to the arrive/leave axis. Frequently this axis is the direction of a valve handwheel. For example:\nIf the rule logical fails, the action is applied. If the logical then fails, the component is moved to another leg, and re-tested. If the component clashes, it is moved along the leg and then re-tested.\nIf there is no action, the component is rotated in increments of 90 degrees to find a non-clashing orientation which passes the rule. If after four attempts it still fails, the component is moved along the leg and retried. If no suitable positions are found on the leg, the component is moved to the next leg and the procedure repeated.\nExamples using PML Functions\nThe following example shows how you can call PML functions for the Logical and Action expressions in a Minor Axis rule for positioning a Valve at and angle of 45 degrees.\nFirst, the Logical expression is set to ( 'minological' ), which calls the following PML function:\nIf the Logical test evaluates to False, that is, if P3 does not have the specified orientation, the Action is carried out.\nThe Action expression is set to ( 'minoaction' ), which orientates the P3 direction of the component:\n      \n         \n            \n               \n                  Clash Exclusion (CLEX) \n                \n               \n                  Logical\n                \n            \n         \n      \n   \nClash Exclusion (CLEX) \nLogical\nA Clash Exclusion rule allows certain clashes to be approved in advance. A use for this is specifying that only non hazardous pipes are allowed in certain areas. Clash exclusion rules can use expressions or functions.\nExample using Expressions\nFor example, the following rule can be used where two groups of elements are always allowed to clash. In this case, Branches carrying radioactive material have their PURP attribute set to RADI. All Zones which are safe for humans to enter have their PURP set to HUMA. The rule allows all Branches whose PURP is not set to RADI to pass through all human zones:\nSelection\nLogical\nThe selection part of the rule is used to identify the Branch or Branch member which is clashing and the logical applies to the obstruction clashing with the Branches.\nExample using a PML Function\nIf a more complicated solution is needed, use a PML function. A simple example is\nPipe Racks and Routing Planes\nAutomatic routing along Pipe Racks is described in . In summary, Pipe Router sees a Pipe Rack as a group of routing planes. Each plane has its FUNCTION attribute set, for example to UTIL for planes which are going to route utilities pipes. You should also make sure that Branches which are routed along Pipe Racks have their PURPOSE attribute set appropriately, so that you can identify which Branches should be routed along a given plane.\nTravel Plane Selection\nLogical, no Action\nTravel Plane Selection\nLogical, no Action\nTo control which travel plane of a pipe rack is used to carry a particular branch. An example of the selection expression, which would apply the rule to all Branches to with Purpose set to COOLING, is:\nAn example of the logical test, which routes the selected Branches along the Plane with its Function set to UTIL is:\nEntry Plane Selection\nLogical, no Action\nEntry Plane Selection\nLogical, no Action\nTo determine which entry plane is used to control a branch as it enters a pipe rack. Normally there is one above and one below, to allow for branches with both liquid and vapour contents to use the rack. An example of the selection might be:\nAn example of the test can be:\nwhich would cause pipes containing gas for cooling to use the upper entry/exit plane to get to/from the UTIL travel plane.\nExit Plane Selection\nLogical, no Action\nExit Plane Selection\nLogical, no Action\nThe rule determines which exit plane is used to control a branch as it exits a pipe rack. Normally there is one above and one below, to allow for branches with both liquid and vapour contents to use the rack. An example of the selection might be:\nAn example of the test can be:\nwhich would cause pipes containing gas for cooling to use the upper entry/exit plane to get to/from the UTIL travel plane.\nShoe Height\nReal\nShoe Height\nReal\nBranches routed via planes or pipe-racks can be offset by a user-specified distance from the plane to allow for shoe-heights. The shoe-height is specified using rules with PURPose SHOE.\nFor example:\nSelection:\nAction:\nHeavy Pipe\nLogical, no Action\nHeavy Pipe\nLogical, no Action\nYou can specify that heavy pipes are placed at the edges of routing planes and light ones at the center. When choosing this packing method, the PLPM attribute of the plane is set to WEIG, and Pipe Router looks for a weight rule to determine whether pipes are light or heavy.\nThe logical expression evaluates to False if the pipe is to be placed at the edge of the rack.\nFor example:\nSelection:\nLogical:\nAll Pipes with Bore greater than 300mm are placed at the edge of the rack.\nRefer to for further information on Pipe packing methods.\nExtra Gap\nReal\nExtra Gap\nReal\nAllows you to specify an additional gap between some pipes, for example, very hot pipes.\nAdditional gaps are determined by rules applied to the default bend or elbow of a branch. For example, for branches with temperature greater than 500 degrees, the following rule gives an additional gap of 0.2 times the arrive bore of the component:\nSelection:\nAction:\nFor more details of additional gaps, see .\nFlange Width (FLWI)\nReal\nFlange Width (FLWI)\nReal\nFlange width rules are used to set the gap between Pipes on Routing Planes and Pipe Racks when the Pipe run on the plane includes Flanges. The rule is applied to the default Flange for the Pipe. The gap can be calculated in several ways.\nExample 1\nSelection:\nAction:\nExample 2\nUses flange parameters:\nSelection:\nAction:\nExample 3\nThe next example uses a property of the Flange, which would be specified in a dataset:\nThe rule can then be:\nSelection:\nAction:\nRefer to for further information on how Flange widths are calculated.\nPost-processing\nPost-processing (POPR)\nLogical, will have Action\nPost-processing (POPR)\nLogical, will have Action\nAll rules with this Purpose are executed after a Branch has been successfully routed. They can be used to add extra details to a Branch such as Drains and Vents or slope the line. The Action is normally a PML function, which must have been defined before the rule is applied.\nThe following example creates an expansion loop:\nThe following illustrations show a Branch, with and without the Post-processing Rule applied.\n\n\nCreate and Edit Routing Rules\nAVEVA E3D\u2122 stores rules within a hierarchy. There are two administrative elements within the hierarchy:\nAVEVA E3D\u2122 stores routing rules, whose type is GRUL, within a rule set. When you can create a new rule, define the type of rule by selecting the correct purpose, the defining the expressions within it. The rule can now be applied to individual branches or all the branches in a particular site, zone or pipe.\nBy default, all rules in the rule sets applied to a branch are considered to be applied to each component in the branch. However, you can also disable any of the rules, or apply rules from other rule sets, to any individual component.\nA sample set of rules is provided with Pipe Router in the Sample Project. The Rule World is named /PIPES-RULES, and it owns several rule sets. The rules in the rule sets are examples which you can use to build a customized set, and do not necessarily represent good engineering practise.\nTo create a rule world:\nFrom the Pipe Router window, select Settings > Routing Rules to display the Routing Rules window. Select Create > Rule World to display the Create Rule World window. In the Name box, input a name for the rule world, click OK to create the Rule World.\nThe rule world is created and displays in the Members List. Create a rule set within the rule world.\nTo create a rule set:\nMake sure that at the level of the Rule World in which you want to create the rule set is selected. From the Routing Rules window, select Create > Rule Set to display the Create Rule Set window. In the Name box, input a name for the Rule Set. In the Function box, input the function of the rule set. (The function is a descriptive term which enables you and other users to identify the purpose of the rules contained within the rule set.) Click OK to create the Rule Set.\nThe set displays in the Members List. You can now create routing rules and store them within the rule set.\nCreate a Routing Rule:\nFrom the Pipe Router window, select Settings > Routing Rules to display the Routing Rules window.\n\nSelect where the rule is to be stored by first selecting the rule world from the Current Rule World drop-down list, and then the rule set from the Current Rule Set drop-down list.\nTo create a new rule, select Create > Rule > New to display the Create Rule window. A new rule element (GRUL) is created in the design hierarchy.\n\nTo name the new rule:\nIn the Name box, input a name for the new rule element, which is the name of the rule element (GRUL) that displays in the design hierarchy.\nClick OK to name the new rule element, close the Create New Rule window and display the Rule Attributes window.\nClick Cancel to discard inputs and close the Create New Rule window.\n\nIn the Description box, input a description for the rule. The description displays in the Routing Rules window.\nSelect a purpose for the rule from the Purpose drop-down list.\nIn the Selection box, input an expression. For example: ALL VALV WITH (ATTRIB STYP EQ \u2018GATE\u2019), this expression tells Pipe Router that the rule is applicable to all valves that have their attribute STYP set to GATE, that is, all gates valves.\nIn the Logical box, input an expression. For example: ( ATTRIB PDIR 3 EQ N ), this expression checks whether or not the direction of P3 on each gate valve is set to north. If it is, then the gate valve meets the criteria of the rule and no action is taken. If the direction of P3 is not north, then Pipe Router performs the action expression described in the next step.\nIn the Action box, input an expression. For example: (AXES PP 3 IS N AND AXES PL IS AXES PL OF PREV), this expression tells Pipe Router to change the direction of P3 to north, and make the leave direction the same as for the previous component.\nSelect the attribute of the CE, click Current Rule. The Rule Attributes window is now populated with the details for the current rule.\nTo test the rule:\nSet the extent of the test (World, Site, Zone, Pipe), from the Test Rule drop-down list, which performs the selection operation defined for the rule, then perform the logical test for each component selected, and report which components passed and which failed. The report displays in the Rules Testing window.\n\nClick OK to create the routing rule. You can now apply the rule to a Branch in the usual way.\nClick Cancel to discard any inputs and close the Rule Attributes window.\nTo copy a rule:\nTo copy an existing rule, from the Routing Rules window, select Create > Rule > Copy to display the Create Copy Rule window.\n\nTo name the copied rule:\nIn the Name box, input a name for the copied element, which is the name of the rule element (GRUL) that displays in the design hierarchy.\nClick OK to name the copied element and close the Create Copy Rule window and display the Rule Attributes window.\nClick Cancel to discard inputs and close the Create Copy Rule window\nWhen you create a copy of a rule, the Rule Attributes displays, filled in with the details of the copied rule. You can then edit the details of the rule, which enables you to select an existing rule and use its details as the starting point for a new rule or modify the details to suit your purpose.\nModify a Routing Rule\nEdit a routing rule, using as an example the sample rules supplied in the rule set TRAVEL-RULES. The rules are modified to give a better route for the pipe rack example in .\nUsing Rules to Specify How Pipes Use a Pipe Rack\nSpecify the type of pipes routed on each level of a pipe rack, using routing rules. For example, you can tell Pipe Router to place all process pipes on the bottom level of a rack and all utility pipes on the top level of a rack. If there are more than one entry/exit plane, you can specify the way in which pipes enter onto and exit from a particular level. For example, have all liquid utility pipes climbing onto a travel plane and all gas utility pipes dropping onto the same travel plane.\nFor example, you can edit the example pipe rack rules that are supplied with Pipe Router and apply them to avoid the pockets created by the default route.\nTo modify a routing rule, from the Pipe Router window, select Settings > Routing Rules to display the Routing Rules window.\n\nThe Rules available are supplied in the sample project. Make sure that the Current Rule World is set to PIPE-RULES and the Current Rule Set is TRAVEL-RULES. There are three Rules supplied: a Travel Plane Rule, an Entry Plane rule and an Exit Plane rule.\nTo see the expressions in the Travel Rule, you must select the rule in the list and then select Modify > Rule on the Routing Rules window. The Rule Attribute window displays and is populated with the attributes for Travel Rule.\n\nFrom the Rule Attributes window, note that:\nSelect the Exit rule in the list on the Routing Rules window and click Current Rule on the Rule Attributes window. Change the Logical expression to be:\nBefore you can test the rules, the Pipe PURP attribute must be set to PROC.\nSelect Purpose from the list of attributes. In the Value column, input PROC.\nPress the Enter Key and the Purpose row is highlighted to indicate that the update has succeeded.\nFrom the Rule Attributes window, you can now test the rule:\nFor example, the exit plane rule. Select the exit Plane rule in the list and make sure that Pipe 2001 is the Current Element. Set Test Rule to Pipe to display the Rule Testing window, which shows you that 1 Branch has been selected for the rule but 0 Plane. No Planes have been selected because there are no Planes with Function set to EXIT.\nTo modify the functions of the planes in the Pipe Rack:\nMake the Pipe Rack the current element and select Modify > Pipe Rack from the Pipe Router window.\nOn the Modify Pipe Rack window, change the Function of the planes:\nLevel 1 Upper Entry/Exit Plane:\nEXIT\nLevel 1 Travel Plane:\nPROC\nLevel 1 Lower Entry/Exit Plane:\nENTRY\n\nLevel 1 Upper Entry/Exit Plane:\nEXIT\n\nLevel 1 Travel Plane:\nPROC\n\nLevel 1 Lower Entry/Exit Plane:\nENTRY\nAssociate the Rule with the Branches required. Select the Branch 2001/B1 on the Routing Rules window. Select Settings > Branch Rules from the menu on the AVEVA E3D\u2122 Router window. On the Branch Rules window, set Apply rule sets to All Selected Branches. Select HIGH, and the rule is added to the window.\nNow re-route the Pipe. A more satisfactory route is obtained.\nDeleting a Rule World, Rule Set or Routing Rule\nTo delete a rule world, rule set, or routing rule, navigate to the rule world and rule set to be deleted from the Current Rule World and Current Rule Set drop-down lists. Select the rule to be deleted from the routing rules list. Select Delete > Rule World, Delete > Rule Set or Delete > Rule, as required.\nPlacing Pipes on Racks and Planes\nThe section describes how to set up rules which control:\nFlanges on Routing Planes\nBy default, Pipe Router runs pipes along Routing planes with the wall-to-wall Pipe Gap given on the Pipe Router Defaults window. Refer to for further information.\nIf you need to run sections of Pipes which include Flanges along routing planes, you can specify that the gap value is applied as a wall-to-flange (WF) gap, if the flanges can be staggered, or as a flange-to-flange (FF) gap, if the flanges are side-by-side on the plane. The default is wall-to-wall (WW) spacing. The spacing is controlled by the PLWW attribute of the RPLA. PLWW can be set to WW, WF or FF.\nIf WW or WF spacing is specified, the Pipe Router looks for rules of type FLWI and apply them. The size of flange is found using the Flange Width (FLWI) rule, which is applied to the default flange (for example, the flange which is obtained with an AVEVA E3D\u2122 SELECT) for each branch at its current bore, even if there are other flanges on the pipe rack.\nThe flange width taken as 0 if:\nIf necessary, specify an additional pipe-specific gap, for example, for very hot pipes.\nExample of Wall-to-Flange Spacing\nIf a rule is used, so that the flange width is set to 1.5 x bore, then wall-to-flange spacing is calculated:\nThe constant gap is set to 50mm. Then the center of an insulated branch of OD 200mm, bore 100mm would be placed 435mm from the center of an adjacent branch of OD 150mm, bore 140mm.\n\nExample of Flange-to-Flange Spacing\nIf the rule sets the flange width to 1.5 x bore, then flange-to-flange spacing is calculated:\n\u00bd OD Pipe A\n100\nFlange width Pipe A\n150\nGap\n50\nFlange width Pipe B\n210\n\u00bd OD Pipe B\n75\nTotal\n585\n\u00bd OD Pipe A\n100\nFlange width Pipe A\n150\nGap\n50\nFlange width Pipe B\n210\n\u00bd OD Pipe B\n75\nTotal\n585\n\nPacking Methods\nThere are two packing methods available. Pipe Router either places a pipe on a plane as near as possible to the edge of the plane, or packs heavy pipes at the edges of racks and light ones at the center. The packing method is an attribute of the Routing Plane. It can be set for the Travel Plane of pipe-racks and for individual planes.\nSelect the By Weight method, the PLPM (Plane Packing Method) attribute of the plane is set to WEIG, and Pipe Router looks for a weight rule, (PURP set to WEIG), to determine whether pipes are light or heavy.\nYou can use weight rules to determine whether pipes are packed at the top or bottom of vertical planes\nHorizontal Routing Planes\nIn the weight-related packing method on horizontal planes, for heavy pipes Pipe Router searches inwards from both edges looking for a free slot with a large enough gap between it and any adjacent pipe. The heavy pipe is placed closest to whichever edge a slot is found. For light pipes Router first looks in the middle of the plane or rack to see if this slot is free. Router then searches in both directions outwards looking for a free slot and use the closer to the center. Pipes for which no rule exists are treated as light pipes and placed in the center of the rack or plane.\nVertical Routing Planes\nThe weight-related packing method can also be applied to vertical routing planes with a horizontal travel direction. If the weight-related packing method is used then, for light pipes, Pipe Router searches downwards from the top edge of the routing plane edges looking for a free slot with a large enough gap between it and any adjacent pipe. For heavy pipes Pipe Router searches upwards from the bottom edge of the plane. Pipes for which no rule exists are treated as light pipes.\nExample of Weight-related Packing\nIf the third and sixth pipes to be packed on a rack are \u2018heavy\u2019 and the others are lig"}
{"Headers": "Pipe Fabrication", "Content": "Modelling\nSpooling and Checks\nDrawings\nExport Fabrication Data\nConfiguration.\nModelling\nModelling\nSpooling and Checks\nSpooling and Checks\nDrawings\nDrawings\nExport Fabrication Data\nExport Fabrication Data\nConfiguration.\nConfiguration.\n\n\n\nModelling\nSpooling and Checks\nDrawings\nExport Fabrication Data\nConfiguration\nModelling\nSpooling and Checks\nDrawings\nExport Fabrication Data\nConfiguration"}
{"Headers": "Modelling", "Content": "At the model stage, fabrication related features are defined, such as fabricated pipe ends, assignment of bending machines and design checks for fabrication. Additional catalog components are also provided as part of Pipe Fabrication.\nAssign Bending Machine\nA default Bending Machine Reference can be defined for a pipe specification and a Bending Machine Reference in the pipe structure can be modified.\nDefault Bending Machine Reference in Pipe Specification\nTo specify a default bending machine reference to each pipe specification using AVEVA Catalogue.\nWhenever a pipe is created, the BendMacReference attribute is populated with the default value assigned to the piping specification. By default, the BendMacReference attribute is assigned with a valid default bending machine reference from the pipe specification.\n\nModify Bending Machine Reference in Pipe Models\nIf a pipe bend Radius is too large and needs to be changed to a smaller bend radius for design reasons, then the BendMacReference attribute for the zone, pipe or branch can be modified to point to another Fabrication Machine World (FMWL), Group (FMGRP) or Machine (FMBEND).\n\nClick CE to identify the currently selected SITE, ZONE, PIPE or BRAN as the currently selected element.\nThe list of elements displays the Name, element type and BendMacReference attribute value of each element in the selected pipe structure. The user can select one or more elements to modify.\n\nSelect the Highlight selected elements check box to highlight the selected table item in the 3D graphical view.\nThe Assign Bending Machine part of the Assign Bending Machine window allows the user to assign a new bending machine and modify the bend radius of the selected element.\n\nAssign Bending Machine\nSelect an FMWLD, FMGRP or FMBEND from the drop-down list to assign a BendMacReference attribute value to the selected element.\nModify Bend Radius\nSelect the check box to modify the bend radius of the selected element by default. Refer to for further information.\nTidy\nSelect the check box to tidy the BendMacReference attribute value of the selected element by default. Refer to for further information.\nAssign Bending Machine\nSelect an FMWLD, FMGRP or FMBEND from the drop-down list to assign a BendMacReference attribute value to the selected element.\nModify Bend Radius\nSelect the check box to modify the bend radius of the selected element by default. Refer to for further information.\nTidy\nSelect the check box to tidy the BendMacReference attribute value of the selected element by default. Refer to for further information.\nClick Apply to assign a new BendMacReference modify the bend radius of the selected element.\nModify Bend Radius\nIf the Modify Bend radius check box is selected, the bend radius of the selected element is modified by default.\nThe example below shows the modified bend radius as part of a pipe structure.\n\nTidy BendMacReference Element\nIf the Tidy check box is selected, the BendMacReference attribute value of the selected element is tidied by default. If the BendMacReference attribute value of a branch is the same value as the owning pipe, the attribute value is removed from the branch.\nThe example below shows a pipe and branch with a duplicate BendMacReference attribute value.\n\nWhen the Tidy check box is selected, the BendMacReference attribute value is removed from the branch.\nDetails\nThe Details tab displays a list of change details for the pipework structure, calculated when the bending machine is assigned.\nErrors\nThe Errors tab displays a list of errors for the pipework structure, calculated when the bending machine is assigned.\nBending Error Types\nThere are three different error types that can be checked for:\nFabricated Pipe Ends\nThe Fabricated Pipe Ends window defines a plain, slanted or threaded pipe end.\n\n\n\n\n\n\nCreate Sniped Ends\nSpecify the angle for the Plain and display a Drawing Note.\nBy default, the slated angle is 0 which means it is a plain end.\nIf required, enter a statement in the Drawing Note field, the default is Plain End, the note is displayed on the drawing.\nClick Create Sniped Ends, select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe Plain fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nSpecify the angle for the Sniped End and display a Drawing Note.\nEnter a value (greater than 0) in the Slanted Angle field to define the angle of the Slanted End in degrees.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}, the note is displayed on the drawing.\nNote:\n{deg} is replaced by the value of the Slanted Angle value in the drawing.\nClick Create Sniped Ends. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe sniped fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nCreate Sniped Ends with Reference Plane\nCreates a slanted end by referencing a plane.\nEnter a value (greater than 0) in the Sniped Angle field to define the angle of the Sniped End in degrees.\nEnter a dimensional value in the Clearance field to define the reference plane clearance.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}. The note displays on the drawing.\nNote:\n{deg} is replaced by the value of the Sniped Angle value in the drawing.\nClick Create Sniped Ends with Reference Plane.\nThe prompt \u2018Pick pipe end:\u2019, is displayed then \u2018Pick plane:\u2019\nThe plane is used as the pipe end cutting standard in the 3D graphical view.\nThe Slated fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nCreate Thread End\nDefines a threaded end for a fabricated pipe end.\nClick Create Threaded End. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nSelect a Threaded Type from the Thread Type drop-down list.\nThe user can configure the Thread Type, refer to for further information.\nThe Threaded End consists of four attributes:\nConnection\nDescription\nBore of Picked Tube\nThread Length\nThe Thread information is shown on the drawing.\nIf a tube has thread information, the build length value starts with '*' as prefix.\nThe assembly table contains the thread information.\nRemove Fabricated End\nDeletes the Fabricated End (Sniped or Threaded). The user must select a pipe end in the 3D graphical view.\nDisplay Fabricated End\nDisplays information for the created Fabricated End.\n\nCreate Sniped Ends\n\nSpecify the angle for the Plain and display a Drawing Note.\n\nBy default, the slated angle is 0 which means it is a plain end.\nIf required, enter a statement in the Drawing Note field, the default is Plain End, the note is displayed on the drawing.\nClick Create Sniped Ends, select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe Plain fabricated end is added to the pipe and the orientation of the pipe end is displayed.\n\nSpecify the angle for the Sniped End and display a Drawing Note.\n\n\n\nEnter a value (greater than 0) in the Slanted Angle field to define the angle of the Slanted End in degrees.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}, the note is displayed on the drawing.\nClick Create Sniped Ends. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe sniped fabricated end is added to the pipe and the orientation of the pipe end is displayed.\n\nCreate Sniped Ends with Reference Plane\nCreates a slanted end by referencing a plane.\nEnter a value (greater than 0) in the Sniped Angle field to define the angle of the Sniped End in degrees.\nEnter a dimensional value in the Clearance field to define the reference plane clearance.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}. The note displays on the drawing.\nClick Create Sniped Ends with Reference Plane.\nThe prompt \u2018Pick pipe end:\u2019, is displayed then \u2018Pick plane:\u2019\nThe plane is used as the pipe end cutting standard in the 3D graphical view.\nThe Slated fabricated end is added to the pipe and the orientation of the pipe end is displayed.\n\nCreate Thread End\nDefines a threaded end for a fabricated pipe end.\nClick Create Threaded End. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\n\nSelect a Threaded Type from the Thread Type drop-down list.\nThe user can configure the Thread Type, refer to for further information.\nThe Threaded End consists of four attributes:\nThe Thread information is shown on the drawing.\nIf a tube has thread information, the build length value starts with '*' as prefix.\n\n\n\nThe assembly table contains the thread information.\n\n\nRemove Fabricated End\nDeletes the Fabricated End (Sniped or Threaded). The user must select a pipe end in the 3D graphical view.\n\nDisplay Fabricated End\nDisplays information for the created Fabricated End.\nModelling Consistency Checks\nPipes that are still being designed can be checked for fabrication readiness. Some of the checks require configurable dimensions or minimum distances. By default, the window is now populated with the details of the CE.\n\nTo add pipes to be checked, in the Model Explorer click to select the required pipe. Then select Add CE, the CE is displayed in the Modelling Consistency Check window.\nTo highlight the pipe to be checked in the 3D graphical view, click to select the Highlight selected elements check box. By default the check box is not selected.\nTo run modelling consistency checks, click Check, a short description (pass or fail) of the check is displayed on the Results tab.\n\nOn the CE tab, a more detailed description of the modelling consistency checks are displayed.\n\nOn the Options tab, all of the modelling consistency checks are displayed, by default all the checks are selected.\n\nAssign Bending Machine\nSelect an FMWLD, FMGRP or FMBEND from the drop-down list to assign a BendMacReference attribute value to the selected element.\nModify Bend Radius\nSelect the check box to modify the bend radius of the selected element by default. Refer to for further information.\nTidy\nSelect the check box to tidy the BendMacReference attribute value of the selected element by default. Refer to for further information.\nCreate Sniped Ends\nSpecify the angle for the Plain and display a Drawing Note.\nBy default, the slated angle is 0 which means it is a plain end.\nIf required, enter a statement in the Drawing Note field, the default is Plain End, the note is displayed on the drawing.\nClick Create Sniped Ends, select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe Plain fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nSpecify the angle for the Sniped End and display a Drawing Note.\nEnter a value (greater than 0) in the Slanted Angle field to define the angle of the Slanted End in degrees.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}, the note is displayed on the drawing.\nNote:\n{deg} is replaced by the value of the Slanted Angle value in the drawing.\nClick Create Sniped Ends. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe sniped fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nCreate Sniped Ends with Reference Plane\nCreates a slanted end by referencing a plane.\nEnter a value (greater than 0) in the Sniped Angle field to define the angle of the Sniped End in degrees.\nEnter a dimensional value in the Clearance field to define the reference plane clearance.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}. The note displays on the drawing.\nNote:\n{deg} is replaced by the value of the Sniped Angle value in the drawing.\nClick Create Sniped Ends with Reference Plane.\nThe prompt \u2018Pick pipe end:\u2019, is displayed then \u2018Pick plane:\u2019\nThe plane is used as the pipe end cutting standard in the 3D graphical view.\nThe Slated fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nCreate Thread End\nDefines a threaded end for a fabricated pipe end.\nClick Create Threaded End. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nSelect a Threaded Type from the Thread Type drop-down list.\nThe user can configure the Thread Type, refer to for further information.\nThe Threaded End consists of four attributes:\nConnection\nDescription\nBore of Picked Tube\nThread Length\nThe Thread information is shown on the drawing.\nIf a tube has thread information, the build length value starts with '*' as prefix.\nThe assembly table contains the thread information.\nRemove Fabricated End\nDeletes the Fabricated End (Sniped or Threaded). The user must select a pipe end in the 3D graphical view.\nDisplay Fabricated End\nDisplays information for the created Fabricated End.\nNot enough tube length before/after bend.\nThere is not enough straight tube length before or after a bend to change the bend radius. An instance can occur when changing a bending machine reference that uses a larger radius value.\nThe example below shows the effect of enlarging a bend radius on a tube.\nBending machine cannot handle the outside diameter\nThe new bending machine reference does not have a suitable bending dimension for the outside diameter of the target pipe.\nBendMacReference is not defined.\nThe BendMacReference attribute value is not defined for any of BRAN, PIPE and ZONE elements in the pipework structure.\nNot enough tube length before/after bend.\nThere is not enough straight tube length before or after a bend to change the bend radius. An instance can occur when changing a bending machine reference that uses a larger radius value.\nThe example below shows the effect of enlarging a bend radius on a tube.\nNot enough tube length before/after bend.\nBending machine cannot handle the outside diameter\nThe new bending machine reference does not have a suitable bending dimension for the outside diameter of the target pipe.\nBending machine cannot handle the outside diameter\nBendMacReference is not defined.\nThe BendMacReference attribute value is not defined for any of BRAN, PIPE and ZONE elements in the pipework structure.\nBendMacReference is not defined.\nConnection\nDescription\nBore of Picked Tube\nThread Length\nConnection\nConnection\nDescription\nDescription\nBore of Picked Tube\nBore of Picked Tube\nThread Length\nThread Length\nNote:\n{deg} is replaced by the value of the Slanted Angle value in the drawing.\nNote:\n{deg} is replaced by the value of the Sniped Angle value in the drawing.\n\n\n\nAssign Bending Machine\nDefault Bending Machine Reference in Pipe Specification\nBendMacReference\nBendMacReference\nModify Bending Machine Reference in Pipe Models\nBendMacReference\nCE\nHighlight selected elements\nAssign Bending Machine\nAssign Bending Machine\nFMWLD\nFMGRP\nFMBEND\nBendMacReference\n\nBendMacReference\n\nApply\nModify Bend Radius\nModify Bend radius\nTidy BendMacReference Element\nTidy\nBendMacReference\nBendMacReference\nBendMacReference\nTidy\nBendMacReference\nDetails\nDetails\nErrors\nErrors\nBending Error Types\nBendMacReference\nFabricated Pipe Ends\nFabricated Pipe Ends\n\n\n\n\n\nCreate Sniped Ends\nDrawing Note\nCreate Sniped Ends\nPick pipe end:\nSniped End\nSlanted Angle\nDrawing Note\nNote\n:\nSlanted Angle\nCreate Sniped Ends\nPick pipe end:\nCreate Sniped Ends with Reference Plane\nSniped Angle\nClearance\nNote\n:\nSniped Angle\nCreate Sniped Ends with Reference Plane\nPick pipe end:\nPick plane:\nCreate Thread End\nCreate Threaded End\nPick pipe end:\nThread Type\n\nRemove Fabricated End\nDisplay Fabricated End\nModelling Consistency Checks\nModel Explorer\nAdd CE\nModelling Consistency Check\nHighlight selected elements\nCheck\nResults\nCE\nOptions"}
{"Headers": "Spooling and Checks", "Content": "Pipe spool generation makes sure that all pipes spools include the necessary adjustments to be suitable for production in an automatic and configurable manner. The following must be considered:\nProduction Checks\n\n\n\n\n\nWeld Handling\nUse the Weld Handling window to create, modify, and delete welds in the currently selected spool. Also use the window, to view welds which could not be created.\n\n\n\n\nCreate Weld\nClick CE to identify the currently selected element as the working element. Use the Create part of the Weld Handling window to create and define a weld.\n\nSpec.\nSelect Spec to create a weld from the current pipe spec. The weld thickness is pre-defined by the spec.\nConfig.\nSelect Config to create a weld from a common weld spec. The weld thickness can be modified according to the design circumstance. Refer to for further information.\nZero Gap\nSelect to define a weld thickness of 0.\nFabrication Type\nSelect Manual, Machine, or Orbital, then Shop, Site or Field.\nCreate Welds on CE\nCreates a weld for the selected pipe with specific options for Fitting to Fitting Connection and Slip-On Flanges. Refer to for further information.\nCreate Welds by Picking\nCreates a weld by picking the specific element in the 3D graphical view.\nAppend Weld Number\nSelect the check box, the next available weld number is assigned to the current weld, by default.\nLeave the check box unchecked to assign the weld number manually.\nNote:\nThe weld number is a unique value. Duplicate weld numbers are highlighted by application.\n\nSpec.\nSelect Spec to create a weld from the current pipe spec. The weld thickness is pre-defined by the spec.\n\nConfig.\nSelect Config to create a weld from a common weld spec. The weld thickness can be modified according to the design circumstance. Refer to for further information.\n\nZero Gap\nSelect to define a weld thickness of 0.\n\nFabrication Type\nSelect Manual, Machine, or Orbital, then Shop, Site or Field.\n\nCreate Welds on CE\nCreates a weld for the selected pipe with specific options for Fitting to Fitting Connection and Slip-On Flanges. Refer to for further information.\n\nCreate Welds by Picking\nCreates a weld by picking the specific element in the 3D graphical view.\n\nAppend Weld Number\nSelect the check box, the next available weld number is assigned to the current weld, by default.\nLeave the check box unchecked to assign the weld number manually.\nModify and Delete Welds\nUse the Modify part of the Weld Handling window to modify and delete the currently selected weld.\n\nThe weld list displays weld information for the welds that can be modified.\nName\nName of the weld.\nWeld Type\nDisplays the weld type.\nFab. Type\nDisplays the weld fabrication type.\nSpool Limit\nDisplays the weld spool limit status.\nNumber\nDisplays the weld number.\nModify the properties of the Weld set in the 3D graphical view (Shop, Type).\nRefreshes the weld list.\nDeletes all welds in the weld list, a window displays asking you to confirm the deletion.\nBy default the Include Spool Limits check box is selected, allowing you to Include Spool Limits within the deletion.\nNote:\nIf the weld list only contains Spool Limit Welds and the delete button is pressed, the toggle is automatically set to true.\nDeletes all welds in the weld list, a window displays asking you to confirm the deletion.\nBy default the Include Spool Limits check box is selected, allowing you to Include Spool Limits within the deletion.\nNote:\nIf the weld list only contains Spool Limit Welds and the delete button is pressed, the toggle is automatically set to true.\nExport Weld List\nExports the weld list in an excel format to another location.\nZoom when selected\nSelect the check box to zoom to the weld information for the selected weld in the 3D graphical view.\nHighlight Elements\nSelect the check box to highlight the selected weld in the 3D graphical view.\nMark Weld Info.\nSelect the check box to display the weld information for the selected weld in the 3D graphical view.\nName\nName of the weld.\nWeld Type\nDisplays the weld type.\nFab. Type\nDisplays the weld fabrication type.\nSpool Limit\nDisplays the weld spool limit status.\nNumber\nDisplays the weld number.\n\nModify the properties of the Weld set in the 3D graphical view (Shop, Type).\n\nRefreshes the weld list.\n\nDeletes all welds in the weld list, a window displays asking you to confirm the deletion.\n\nBy default the Include Spool Limits check box is selected, allowing you to Include Spool Limits within the deletion.\n\nDeletes all welds in the weld list, a window displays asking you to confirm the deletion.\n\nBy default the Include Spool Limits check box is selected, allowing you to Include Spool Limits within the deletion.\nExport Weld List\nExports the weld list in an excel format to another location.\nZoom when selected\nSelect the check box to zoom to the weld information for the selected weld in the 3D graphical view.\nHighlight Elements\nSelect the check box to highlight the selected weld in the 3D graphical view.\nMark Weld Info.\nSelect the check box to display the weld information for the selected weld in the 3D graphical view.\nError tab\nWhen welds cannot be created between components, the name and description of the error populates the Error tab of the Weld Handling window.\n\nModify Spool\nUse the Modify Spool window to define pipe end & feed excess, loose components, spool limits, machine insertion direction and create multiple spools.\n\n\n\n\n\n\n\nUser End & Feed Excess\nUse the User End & Feed Excess part of the Modify Spool window to display and modify the end and feed excess values.\nEnd Excess - adds a surplus to the end of pipe pieces during production.\nFeed Excess - adds a surplus during the feeding of the pipe piece through the bending machine during production.\n\nShow User End Excesses\nDisplays or hides the end excess values in the 3D graphical view.\nSet User End Excess\nView or modify the end excess by picking a tube element on the 3D graphical view.\nShow User Feed Excess\nDisplays or hides the feed excess values in the 3D graphical view.\nSet User Feed Excess\nView or modify the feed excess by picking a tube element on the 3D graphical view.\nShow User End Excesses\nDisplays or hides the end excess values in the 3D graphical view.\n\nSet User End Excess\nView or modify the end excess by picking a tube element on the 3D graphical view.\n\nShow User Feed Excess\nDisplays or hides the feed excess values in the 3D graphical view.\nSet User Feed Excess\nView or modify the feed excess by picking a tube element on the 3D graphical view.\n\nComponents Attributes\nUse the Component Attributes part of the Modify Spool window to display and modify the component attributes.\n\nShow Loose Component\nDisplays or hides the loose component value in the 3D graphical view\nModify Component Attributes\nClick to display the Component Attributes window. Refer to for further information.\nShow Loose Component\nDisplays or hides the loose component value in the 3D graphical view\nModify Component Attributes\nClick to display the Component Attributes window. Refer to for further information.\n\nModify Component Attributes\nUse the Component Attributes window to define the attributes for piping components.\n\nDisplays the attribute settings for the previous piping component.\nDisplays the attribute settings for the next piping component.\nLoose Component\nSelect the check box to specify the piping component as a Loose Component.\nApply Default Loose Excess (200.00mm)\nThe check box becomes active when the user selects the Loose Component check box, the Offline Component check box must be left unchecked and the component must be positioned at the end of a spool.\nSelect the check box to define a Default Loose Excess of 200mm for the piping component.\nOffline Component\nSelect the check box to specify the piping component as an Offline Component.\nShop Fabrication Material\nSelect the check box to specify the piping component as a Shop Fabrication Material component.\n\nDisplays the attribute settings for the previous piping component.\n\nDisplays the attribute settings for the next piping component.\nLoose Component\nSelect the check box to specify the piping component as a Loose Component.\nApply Default Loose Excess (200.00mm)\nThe check box becomes active when the user selects the Loose Component check box, the Offline Component check box must be left unchecked and the component must be positioned at the end of a spool.\nSelect the check box to define a Default Loose Excess of 200mm for the piping component.\nOffline Component\nSelect the check box to specify the piping component as an Offline Component.\nShop Fabrication Material\nSelect the check box to specify the piping component as a Shop Fabrication Material component.\nSpool Limits\nUse the Spool Limits part of the Modify Spool window to display and modify the spool limits. A spool limit can be added or deleted. The spool limit is created with a field WELD component.\n\nShow Spool Limits\nDisplays the spool limits (welds) for the currently selected pipe on the 3D graphical view.\nHide Spool Limits\nHides the spool limits (welds) for the currently selected pipe on the 3D graphical view.\nAdd/Remove Spool Limit - No Welds/Welds\nCreate a spool limit for a component using a cursor pick on the 3D graphical view.\nPick first component or <ESC> to finish : on the 3D graphical view\nPossible spool limit positions are displayed as a square without fill, existing spool limits are displayed as a filled square.\nPick a second component adjacent to the first component. The second component is used to decide the exact position for a new spool limit.\nA Confirm window displays asking OK to add?, click Yes to add a new spool limit.\nIf the Add/Remove Spool Limits - No Welds is selected the weld is not displayed on the 3D graphical view.\nAdd/Remove Spool Limit - No Welds/Welds\nRemove a spool limit for a component using a cursor pick on the 3D graphical view.\nPick first component or <ESC> to finish : on the 3D graphical view\nPick a second component, a Confirm window is displayed asking OK to remove, click Yes to remove the spool limit.\nIf the spool limit location on the currently selected pipe already has a spool limit created without a field WELD component and Add/Remove Spool Limit - Welds is selected, the following Confirm window is displayed:\nClick Yes to replace the spool limit - without a weld component with a weld.\nShow Spool Limits\nDisplays the spool limits (welds) for the currently selected pipe on the 3D graphical view.\n\nHide Spool Limits\nHides the spool limits (welds) for the currently selected pipe on the 3D graphical view.\n\nAdd/Remove Spool Limit - No Welds/Welds\nCreate a spool limit for a component using a cursor pick on the 3D graphical view.\nPick first component or <ESC> to finish : on the 3D graphical view\nPossible spool limit positions are displayed as a square without fill, existing spool limits are displayed as a filled square.\n\n\nPick a second component adjacent to the first component. The second component is used to decide the exact position for a new spool limit.\nA Confirm window displays asking OK to add?, click Yes to add a new spool limit.\n\n\nIf the Add/Remove Spool Limits - No Welds is selected the weld is not displayed on the 3D graphical view.\n\n\nAdd/Remove Spool Limit - No Welds/Welds\nRemove a spool limit for a component using a cursor pick on the 3D graphical view.\nPick first component or <ESC> to finish : on the 3D graphical view\n\n\n\n\nPick a second component, a Confirm window is displayed asking OK to remove, click Yes to remove the spool limit.\n\n\n\nIf the spool limit location on the currently selected pipe already has a spool limit created without a field WELD component and Add/Remove Spool Limit - Welds is selected, the following Confirm window is displayed:\n\n\n\nClick Yes to replace the spool limit - without a weld component with a weld.\nMachine Insertion Direction\nUse the Set Machine Insertion Direction part of the Modify Spool window to define the bending direction for the spool.\n\nArrive\nSelect the radio button and specify the Arrive to define the spool arrive end as the machine insertion direction.\nLeave\nSelect the radio button and specify the Leave to define the spool leave end as the machine insertion direction.\nAuto\nBy default, the bending direction is assigned after the bending check algorithm has checked and optimized both directions.\nArrive\nSelect the radio button and specify the Arrive to define the spool arrive end as the machine insertion direction.\nLeave\nSelect the radio button and specify the Leave to define the spool leave end as the machine insertion direction.\nAuto\nBy default, the bending direction is assigned after the bending check algorithm has checked and optimized both directions.\nMultiple Spools\nUse the Create Multiple Spool part of the Modify Spool window to define a Spool Drawing (SPLDRG) element.\n\nThe Fabrication Explorer is automatically displayed, SPLDRG elements can be viewed in the Fabrication Explorer.\n\nUse the Modify Spool window to create a multiple spool.\n\nCreates the currently selected Department (ISODEP), Registry (ISOREG) or Spool Drawing (SPLDRG) element.\nDepartment\nSelect from the drop-down list to create a Department element. Enter a Department Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\nRegistry\nSelect from the drop-down list to create a Registry element. Enter a Registry Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\nSpool Drawing\nSelect from the drop-down list to create a Spool Drawing element. Enter a Spool Drawing Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\nAdds a spool to a spool drawing by picking the spool on the 3D graphical view.\nRemoves a spool from a spool drawing by picking the spool on the 3D graphical view.\nInclude field components into the Spool drawing.\nUpdate Part Number\nCreates Fabrication or Installation Isometrics.\nSearch Within\nSearch within the pipe, branch, zone, site or world.\n\nCreates the currently selected Department (ISODEP), Registry (ISOREG) or Spool Drawing (SPLDRG) element.\nDepartment\nSelect from the drop-down list to create a Department element. Enter a Department Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\nRegistry\nSelect from the drop-down list to create a Registry element. Enter a Registry Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\nSpool Drawing\nSelect from the drop-down list to create a Spool Drawing element. Enter a Spool Drawing Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\n\nAdds a spool to a spool drawing by picking the spool on the 3D graphical view.\n\nRemoves a spool from a spool drawing by picking the spool on the 3D graphical view.\n\nInclude field components into the Spool drawing.\nUpdate Part Number\nCreates Fabrication or Installation Isometrics.\nSearch Within\nSearch within the pipe, branch, zone, site or world.\nUse the bottom part of the Modify Spool window to define the links with Fabrication Checks and Weld Handling. Functionality is also available to clear all Aid Texts on the 3D graphical view.\n\nFabrication Checks\nClick to display the Fabrication Check window. Refer to for further information\nWeld Handling\nClick to display the Weld Handling window. Refer to for further information\nClear All\nRemoves all Aid Texts on the 3D graphical view.\nFabrication Checks\nClick to display the Fabrication Check window. Refer to for further information\nWeld Handling\nClick to display the Weld Handling window. Refer to for further information\nClear All\nRemoves all Aid Texts on the 3D graphical view.\nAdd Spool Attributes\nUse the Spool Attributes window to modify the spool name and other attributes. Functionality is also available to add a new attribute column to the list of available columns.\n\nCE\nIdentifies the currently selected element as the working element. The list of spool attributes is populated with all spools under the current element.\nExport\nExports the spool data to an excel file.\nHighlight when selected\nSelect the check box to highlight the selected spool in the 3D graphical view.\nCE\nIdentifies the currently selected element as the working element. The list of spool attributes is populated with all spools under the current element.\nExport\nExports the spool data to an excel file.\nHighlight when selected\nSelect the check box to highlight the selected spool in the 3D graphical view.\nAdd new columns using the ppGetColumnsForSpool.pmlfnc file, located in the pmlfnc folder. The following example describes how to add a new attribute column, called Paint, to the list of spool attributes.\nOpen the ppGetColumnsForSpool.pmlfnc file, the highlighted text in the example below displays the text required to be added to the file.\n\nReload the Spool Attributes window to the application using the Command Window, enter pml reload form !!pfSpoolAttributes.\nAdd new drop-down value list using the ppGetColumnsForSpool.pmlfnc file, located in the pmlfnc folder. The following example describes how to add a value list to the Paint attribute column.\nOpen the ppGetColumnsForSpool.pmlfnc file, the text in the example below displays the text required to be added to the file.\n\nReload the Spool Attributes window to the application using the Command Window, enter pml reload form !!pfSpoolAttributes.\nAlternatively, add a new drop-down value list using the ppGetColumnsForSpool.pmlfnc and pfGetValueListForSpool.pmlfnc files.\nOpen the ppGetColumnsForSpool.pmlfnc file, the highlighted text in the example below displays the text required to be added to the file.\n\nOpen the pfGetValueListForSpool.pmlfnc file, the highlighted text in the example below displays the text required to be added to the file.\n\nFabrication Check\nUse the Fabrication Check window to check pipe models for production readiness. Make sure a SITE or ZONE element is selected as the CE in the design hierarchy.\n\n\nAdd CE\nIdentifies the currently selected element as the working element. The list of available pipes is populated with all pipes under the current element.\nValidate\nValidates the current selection for production readiness. After validation, all errors and production information displays in the Check Results and the Details tabs.\nAfter validation, the pipe status is set to ready for production if there are no errors.\nRelease\nSets the pipe status to ready for production, regardless of outstanding production errors.\nAdd CE\nIdentifies the currently selected element as the working element. The list of available pipes is populated with all pipes under the current element.\nValidate\nValidates the current selection for production readiness. After validation, all errors and production information displays in the Check Results and the Details tabs.\nAfter validation, the pipe status is set to ready for production if there are no errors.\nRelease\nSets the pipe status to ready for production, regardless of outstanding production errors.\n\nZoom when selected\nSelect the check box to display the currently selected element in the 3D graphical view.\nModify Spool\nClick to display the Modify Spool window. Refer to for further information.\nWeld Handling\nClick to display the Weld Handling window. Refer to for further information.\nSelect Default Fabrication Machines\nClick to display the Default Fabrication Machines part Fabrication Check window. Refer to for further information.\nZoom when selected\nSelect the check box to display the currently selected element in the 3D graphical view.\nModify Spool\nClick to display the Modify Spool window. Refer to for further information.\nWeld Handling\nClick to display the Weld Handling window. Refer to for further information.\nSelect Default Fabrication Machines\nClick to display the Default Fabrication Machines part Fabrication Check window. Refer to for further information.\nUse the pipe status part of the fabrication check window to view the list of pipes contained within the currently selected site or zone element together with the fabrication status and if the pipe has passed the consistency check.\n\nRight-click on the Pipe part of the Fabrication Check window to display a pop-up menu of available options associated with the selection.\n\nValidate Pipes\nRuns the fabrication checks against the currently selected pipes and displays the result.\nSpools and pieces are generated after validation if there are no outstanding errors.\nValidate Pipes With\nUse the Select Fabrication Machines window to view the default bending machines available for selection.\nSet to Manually Bent\nAll pipe pieces containing bends in the selected pipe are set to manually bent.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks. Refer to for further information.\nRelease\nGenerates spool and piece elements for the currently selected pipes, the status is set to Ready for fabrication regardless of outstanding warnings.\nDelete Spool Information\nDeletes fabrication information for all pipe spools and pipe pieces in the currently selected pipes.\nAdd CE\nAdds all pipes under the CE element to the pipe list.\nRemove Selected\nRemoves the currently selected pipes from the pipe list.\nRemove All\nRemoves all pipes from the pipe list.\nSelect All\nSelects all pipes in the list of available pipes.\nUnselect All\nDeselects all pipes in the list of available pipes.\nAdd to 3D View\nAdds the selected pipes to the 3D graphical view.\nRemove from 3D View\nRemoves the selected pipes from the 3D graphical view.\nOptimization Priorities\nDisplays the Optimization Priorities window, use it to order the optimization priorities for the fabrication check. The modified priorities are temporary and is invalid after closing the Fabrication Check window. The functionality of the Optimization Priorities window is explained as part of the process for defining Optimization Criteria for Bending and Welding. Refer to for further information.\nZoom To\nDisplays the currently selected pipes in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe in the Design Explorer.\nValidate Pipes\nRuns the fabrication checks against the currently selected pipes and displays the result.\nSpools and pieces are generated after validation if there are no outstanding errors.\nValidate Pipes With\nUse the Select Fabrication Machines window to view the default bending machines available for selection.\nSet to Manually Bent\nAll pipe pieces containing bends in the selected pipe are set to manually bent.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks. Refer to for further information.\nRelease\nGenerates spool and piece elements for the currently selected pipes, the status is set to Ready for fabrication regardless of outstanding warnings.\nDelete Spool Information\nDeletes fabrication information for all pipe spools and pipe pieces in the currently selected pipes.\nAdd CE\nAdds all pipes under the CE element to the pipe list.\nRemove Selected\nRemoves the currently selected pipes from the pipe list.\nRemove All\nRemoves all pipes from the pipe list.\nSelect All\nSelects all pipes in the list of available pipes.\nUnselect All\nDeselects all pipes in the list of available pipes.\nAdd to 3D View\nAdds the selected pipes to the 3D graphical view.\nRemove from 3D View\nRemoves the selected pipes from the 3D graphical view.\nOptimization Priorities\nDisplays the Optimization Priorities window, use it to order the optimization priorities for the fabrication check. The modified priorities are temporary and is invalid after closing the Fabrication Check window. The functionality of the Optimization Priorities window is explained as part of the process for defining Optimization Criteria for Bending and Welding. Refer to for further information.\nZoom To\nDisplays the currently selected pipes in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe in the Design Explorer.\nUse the Spool part of the Fabrication Check window, to view the list of pipe spools contained within the CE, together with the fabrication status and spool type.\n\nRight-click on the Spool part of the Fabrication Check window to display a pop-up menu of available options associated with the selection.\n\nValidate Spools\nRuns the fabrication checks against the currently selected spools.\nValidate Spools With\nUse the Select Fabrication Machines window to view the default fabrication machines available for selection.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSet to Manually Bent\nAll pipe pieces containing bends in the selected pipe spool are set to manually bent.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks.\nRefer to for further information.\nRelease\nGenerates spool and piece elements for the currently selected spools, sets the status to Ready for fabrication regardless of outstanding warnings.\nDelete Spool Information\nDeletes fabrication information for all pipe spools and pipe pieces in the currently selected spools.\nModify Name\nUse the Rename Element window to rename individual spools.\nRename Spools\nRenames the currently selected spools by using auto-naming rules. If auto-naming is turned off, the menu is disabled.\nRename All Spools\nRenames all spools in the spool list by using auto-naming rules. If auto-naming is turned off, the menu is disabled.\nChange Spool Type\nSets the spool type of selected pipe spool, SHOP, FITT or SITE.\nZoom To\nDisplays the currently selected pipe spool in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe spool in the Design Explorer.\nHighlight\nHighlights the last selected pipe spool in the 3D graphical view.\nValidate Spools\nRuns the fabrication checks against the currently selected spools.\nValidate Spools With\nUse the Select Fabrication Machines window to view the default fabrication machines available for selection.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSet to Manually Bent\nAll pipe pieces containing bends in the selected pipe spool are set to manually bent.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks.\nRefer to for further information.\nRelease\nGenerates spool and piece elements for the currently selected spools, sets the status to Ready for fabrication regardless of outstanding warnings.\nDelete Spool Information\nDeletes fabrication information for all pipe spools and pipe pieces in the currently selected spools.\nModify Name\nUse the Rename Element window to rename individual spools.\n\nRename Spools\nRenames the currently selected spools by using auto-naming rules. If auto-naming is turned off, the menu is disabled.\nRename All Spools\nRenames all spools in the spool list by using auto-naming rules. If auto-naming is turned off, the menu is disabled.\nChange Spool Type\nSets the spool type of selected pipe spool, SHOP, FITT or SITE.\nZoom To\nDisplays the currently selected pipe spool in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe spool in the Design Explorer.\nHighlight\nHighlights the last selected pipe spool in the 3D graphical view.\nUse the Piece No. part of the Fabrication Check window to view the list of pipe pieces contained within the CE, together with the fabrication status.\n\nRight-click on the Piece No. part of the Fabrication Check window to display a pop-up menu of available options associated with the selection.\n\nValidate Pipe Pieces\nRuns the fabrication checks against the currently selected pipe pieces.\nValidate Pipe Pieces With\nUse the Select Fabrication Machines window to view a list of available fabrication machines for selection.\nSet to Manually Bent\nThe selected pipe piece is set to manually bent.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks. Refer to for further information.\nDelete Piece Information\nDeletes fabrication information for the currently selected pipe pieces.\nZoom To\nDisplays the currently selected pipe piece in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe piece in the Design Explorer.\nHighlight\nHighlights the last selected pipe piece in the 3D graphical view.\nValidate Pipe Pieces\nRuns the fabrication checks against the currently selected pipe pieces.\nValidate Pipe Pieces With\nUse the Select Fabrication Machines window to view a list of available fabrication machines for selection.\nSet to Manually Bent\nThe selected pipe piece is set to manually bent.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks. Refer to for further information.\nDelete Piece Information\nDeletes fabrication information for the currently selected pipe pieces.\nZoom To\nDisplays the currently selected pipe piece in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe piece in the Design Explorer.\nHighlight\nHighlights the last selected pipe piece in the 3D graphical view.\nThe Check Results tab displays a description of the Fabrication Check errors, the check results display are classified as:\n\nThe Details tab displays all values from the fabrication check, the values are stored in PPIECE elements.\n\nDefault Fabrication Machines\nWhen the default fabrication machines are selected, the fabrication checks only use these default fabrication machines, instead of using the BendMacReference attribute of the zone, pipe and branch.\nGalvanization Tank Check\nUse the Galvanization Tank Check window to check the validity of a galvanization tank against a pipe spool.\n\nThe list of available spools displays the currently selected pipe spools.\nCE\nIdentifies the currently selected element as the working element.\nSelect Galvanization Tank\nSelect a galvanization tank from the drop-down list to validate against the currently selected pipe spool.\nTank Dimensions\n(W x H x D)\nDisplays the galvanization tank\u2019s dimensions in the W x H x D format.\nZoom when Selected\nZooms to the currently selected spool in the 3D view.\nShow Spool Volume\nDisplays the spool volume in the 3D view.\nCheck\nChecks the validity of the galvanization tank against the currently selected pipe spool.\nStop\nCancels the current check.\nCE\nIdentifies the currently selected element as the working element.\nSelect Galvanization Tank\nSelect a galvanization tank from the drop-down list to validate against the currently selected pipe spool.\nTank Dimensions\n(W x H x D)\nDisplays the galvanization tank\u2019s dimensions in the W x H x D format.\nZoom when Selected\nZooms to the currently selected spool in the 3D view.\nShow Spool Volume\nDisplays the spool volume in the 3D view.\nCheck\nChecks the validity of the galvanization tank against the currently selected pipe spool.\nStop\nCancels the current check.\nAutomatic Flange Alignment\nFor pipe-pieces and pipe spools that have been set up to be machine welded, that system make sure it correctly orientates the piping model so flange-holes and spools align when assembled.\nThe system checks flange-alignment as part of the pipe-checking and Datacon functionality, refer to for further information.\nFabrication Machine\nThe system can check pipe pieces for production readiness against bending machines, welding machines, extrusion machines and the defined stock length of tubing.\nFabrication checks requests are made to a fabrication machine manager controlling the fabrication machines. Information about the welding/bending machine operation and their corresponding activity tables can be obtained from the Manager. Refer to for further information.\nSpec.\nSelect Spec"}
{"Headers": "Drawings", "Content": "The user can create three different types of drawings.\n\n\n"}
{"Headers": "Spool Drawings", "Content": "All of the tasks that a user would carry out that are associated with the creation, modification, drawing options and errors of Pipe Spool Drawings are initiated from a central Pipe Spool Drawing window which acts as a task hub.\nWhen the Pipe Spool Drawing window is opened, the application searches for valid pipe spools below the current element and loads them into the grid. To be valid for the production of pipe sketches, each pipe must be validated using the spooling and checks functionality and must be released for Fabrication. Refer to Spooling and Checks for further information.\nIt is recommended to select a Pipe Zone element as the CE in the Model Explorer.\n\n\n\n\n\nSpooling and Checks\nPipe Spool Drawings\nPipe Spool Drawing\nPipe Spool Drawing\nSpooling and Checks\nPipe Zone\nModel Explorer"}
{"Headers": "Export Fabrication Data", "Content": "Bending machine information can be saved and exported as an XML file. Use the Fabrication NC Data window to save the bending machine information as XML file. For example, the bending activities of a specified list of pipe pieces. Bending Machine NC Output allows the bending machine information such as the bending activities of a specified list of pipe pieces to be saved to a file.\n\nCE\nIdentifies the element in the Model Explorer as the CE.\nPipe Pieces\nView NC Data when selected\nSelect the View NC Data when selected to display the contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\nCreate .ben data files\nChanges the format of the bending program\nOptions\nFile\nSelect a file option from the drop-down list:\nOne File - to create a single file\nBy Pipe - to create a file for each pipe\nBy Pipe Spool - to create a file for each pipe spool\nBy Pipe Piece - to create a file for each pipe.\nName\nChoose a name option from the drop-down list:\nSelect Element Name, the name of the element (PPIECE, PSPOOL or PIPE) is used as the name of the output file.\nSelect Date & Sequence, the current date, time and sequence number is used as the name of the output file. For example, 20121107235358-1.xml.\nFolder\nDisplays the file path for the created .xml file, if required navigate to a different location, click Browse then navigate to the new location.\nSave Options\nClick Save Options to save the options.\nExport\nClick Export to export the NC data of the selected pipe pieces in the .xml format to a specified location. Once complete the name of the .xml file is displayed in the NC File column.\nThe contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\nStop\nClick Stop to stop the export process.\nCE\nIdentifies the element in the Model Explorer as the CE.\nPipe Pieces\n\nView NC Data when selected\nSelect the View NC Data when selected to display the contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\nCreate .ben data files\nChanges the format of the bending program\nOptions\n\nSelect a file option from the drop-down list:\nOne File - to create a single file\nBy Pipe - to create a file for each pipe\nBy Pipe Spool - to create a file for each pipe spool\nBy Pipe Piece - to create a file for each pipe.\nChoose a name option from the drop-down list:\nSelect Element Name, the name of the element (PPIECE, PSPOOL or PIPE) is used as the name of the output file.\nSelect Date & Sequence, the current date, time and sequence number is used as the name of the output file. For example, 20121107235358-1.xml.\nDisplays the file path for the created .xml file, if required navigate to a different location, click Browse then navigate to the new location.\nClick Save Options to save the options.\nExport\nClick Export to export the NC data of the selected pipe pieces in the .xml format to a specified location. Once complete the name of the .xml file is displayed in the NC File column.\nThe contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\n\nStop\nClick Stop to stop the export process.\n\nCE\nIdentifies the element in the Model Explorer as the CE.\nPipe Pieces\nView NC Data when selected\nSelect the View NC Data when selected to display the contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\nCreate .ben data files\nChanges the format of the bending program\nOptions\nFile\nSelect a file option from the drop-down list:\nOne File - to create a single file\nBy Pipe - to create a file for each pipe\nBy Pipe Spool - to create a file for each pipe spool\nBy Pipe Piece - to create a file for each pipe.\nName\nChoose a name option from the drop-down list:\nSelect Element Name, the name of the element (PPIECE, PSPOOL or PIPE) is used as the name of the output file.\nSelect Date & Sequence, the current date, time and sequence number is used as the name of the output file. For example, 20121107235358-1.xml.\nFolder\nDisplays the file path for the created .xml file, if required navigate to a different location, click Browse then navigate to the new location.\nSave Options\nClick Save Options to save the options.\nExport\nClick Export to export the NC data of the selected pipe pieces in the .xml format to a specified location. Once complete the name of the .xml file is displayed in the NC File column.\nThe contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\nStop\nClick Stop to stop the export process.\n\n\n\nFabrication NC Data\nBending Machine NC Output\nCE\nModel Explorer\nCE\nPipe Pieces\nView NC Data when selected\nAVEVA Everything3D Model Command Output\nCreate .ben data files\nOptions\nFile\nOne File\nBy Pipe\nBy Pipe Spool\nBy Pipe Piece\nName\nElement Name\nDate & Sequence\nFolder\nSave Options\nSave Options\nExport\nExport\nNC File\nAVEVA Everything3D Model Command Output\nStop\nStop"}
{"Headers": "Configuration", "Content": "Defines attributes of pipe bending, flange welding and extrusion machines. Weld handling information and default values for pipe checks and behavioral aspects. Creates new threaded ends or galvanization tank or the ability to view and/or edit an existing one. Applies a custom configuration to limit waste of material and cost.\nExport Fabrication Data\n\n\n\n\n\n\n\n\n\nExport Fabrication Data\nExport Fabrication Data\n\n\n\n\n\n"}
{"Headers": "Prepare the Site for Spool", "Content": "The consistency of the data should have been checked before the model is sent for spooling. However, it is best practice to check that the design data in the design model is consistent and make any changes (inserting shop or field welds) to the design model that are obviously needed after inspection, before any spooling is carried out.\nThe Spool module does not operate correctly if there are errors in the consistency check, warnings do not affect the operation. Make sure the ZONE SPOOL-PIPE element in the Model Explorer is the Current Element (CE).\n\nRefer to for further information.\n\n\n\n"}
{"Headers": "Pipework Spool", "Content": "The Spool module works with spooling networks, which are created by selecting pipework elements to be added to a Spool Drawing (SPLDRG). The selected elements must form an interconnected piping network but are not limited to a single branch or pipe in the design model.\nSpooling networks consist of interconnected spools and fields. Where a Spool is defined as a run of piping components and tube that is connected during fabrication and a FIELD is an individual or group of piping components that are connected during the erection phase.\nSpools and fields are defined by picking an element in the 3D View window. If the element has been defined as a fabrication element (For example, the SHOP Flag is true) it generates a Spool. Whereas, if the selected element has been defined as being fitted on site (For example, the SHOP Flag is false) it generates a FIELD.\nWhen an element is picked, the software searches all connected piping components and tube and then adds all adjacent components that have the same SHOP Flag status to that spool or field. The ends of the spools, called SPOOL BREAKS, occur when the SHOP Flag status changes.\nSPOOL BREAKS can be forced by defining Field Welds or Joints at the required point in the SPOOL. Field welds can be used to split a piping section at a particular component or at some defined point along a length of tube. The forced spool break is used to create a break at joint that does not have a field element in it (for example: a flanged joint with no gasket).\nBy setting the SFLimit (Spool/Field Limit) attribute for a SPLDRG to either BRAN, PIPE, ZONE or SITE (the default is WORLD), a spool break is enforced at any change at the corresponding element level.\nSPOOLING NETWORKS can be defined by picking each SPOOL and FIELD in sequence, to add to the SPOOL DRAWING or by picking two ends of a continuous piping network. SPOOL checks that it is an interconnected network before it adds all the spools and fields to the SPOOL DRAWING.\n\n\n\n\n"}
{"Headers": "Modify > SPLDRG Order", "Content": "Use Modify SPLDRG Order from the main menu bar to modify the existing order of the Spool Drawing (SPLDRG) without changing the design hierarchy, in the 3D graphical view pick the element to reorder SPLDRG Order.\nAfter the selection has been made the order of the SPLDEG order has been changed, without changing the design hierarchy.\n\n\n\nModify SPLDRG Order"}
{"Headers": "Modify > MTO Status", "Content": "Use the Set MTO status on isometric window to modify the MaterialTakeOff (MTO) Status information required for the backing sheet of the Pipe Sketch.\n\nThe name of the component displays in the Piping component part of the Set MTO status on isometric window. The Right Arrow moves to the Next element in the pipework network (downwards) and the Left Arrow moves to the previous element (upwards). Select from a list of available drawings for the drawing and MTO status.\n\n\n\nSet MTO status on isometric\nPiping component\nSet MTO status on isometric\nRight Arrow\nLeft Arrow"}
{"Headers": "Modify > Design Plotfile", "Content": "If an isometric is created for the branch containing the component to be modified, use the Detail Plotfile window to browse for the isometric.\n\nThe name of the piping component displays in the Component part of the Detail Plotfile window. The Right Arrow moves to the Next element in the pipework network (downwards) and the Left Arrow moves to the previous element (upwards).\nThe Components with detail plotfile part of the Detail Plotfile window displays all the piping components which have had isometrics created.\nNavigate to the required isometric. Once the isometric has been found, it displays in the Detail Plotfile part of the Detail Plotfile window.\n\n\n\nDetail Plotfile\nComponent\nDetail Plotfile\nRight Arrow\nLeft Arrow\nComponents with detail plotfile\nDetail Plotfile\nDetail Plotfile\nDetail Plotfile"}
{"Headers": "Modify > Attached Welds", "Content": "Attached Welds (AWELD) components provide a method for numbering the welds required for welded attachments. Typically these are used to secure the piping network to the support ATTAchments. Use the Number of Attached Welds window to create the required number of welds on each attachment in SPOOL.\n\nThe name of the Piping component displays in the Piping Component part of the Number of Attached Welds window. The Right Arrow moves to the Next element in the pipework network (downwards) and the Left Arrow moves to the previous element (upwards).\n\n\n\nNumber of Attached Welds\nPiping\nComponent\nNumber of Attached Welds\nRight Arrow\nLeft Arrow"}
{"Headers": "Display/Modify", "Content": "All of the elements created in AVEVA E3D Design have attributes, either general or special. Each element has different attributes that can be displayed or modified, because of this the Pipework discipline uses a common layout for windows that are presented. For the same reason this document only includes a detailed description of how to display or modify one set of element data. The information can be applied to the same processes that are used to display/modify all other types of element data.\nUse the Display/Modify SPLDRG window to view or modify any of the attributes in the currently selected Spool Drawing (SPLDRG). The SPLDRG attributes are displayed in a scrollable list in Spldrg Attributes part of the Display/Modify SPLDRG window.\n\n\n\n\nDisplay/Modify SPLDRG\nSpldrg Attributes\nDisplay/Modify SPLDRG"}
{"Headers": "Spool Reference Information", "Content": "The Spool Reference Information provides additional information on some important aspects of the Spool module, which is intended for experienced users and system administrators, to enable them to modify existing databases and catalogs making them compatible with Spool.\n\n\n"}
{"Headers": "Special Cases", "Content": "The following sub-sections contain descriptions of some special cases within SPOOL.\nShop Flag Status\nThe Shop Flag Status describes some of the special cases for the Shop Flag. These can effect the placement of Spool Breaks and the handling of some elements.\nATTAchments\nWhile ATTAs do have a Shop Flag, its status is ignored when spooling a piping network. For example: a shop false ATTA does not break a spool.\nLeave Tubes of Welds\nIf a spool is broken by inserting a field weld into the leave tube after the last component in a pipe, the section between the weld and the end of the tube is reassigned as the leave tube of the weld. Inserting a field weld is a modification to the DESIGN database and immediately after its creation the weld and its leave tube are not in the Spool Drawing.\nAdd the weld and its leave tube by updating the numbering of the Spool Drawing, in the normal way.\nWelds for OLETs\nAn OLET element has 3 p-points: P1 (p-arrive) and P2 (p-leave) in the main tube and P3 in the off-line leg. P1 and P2 are coincident and are normally treated as a single point.\nA problem can occur if points P1 and P2 have Ckeys of BWD or SWD. By default this should give two welds, one for each point, but the software recognises the OLET as a special case and only allocates one weld.\nNote:\nThe leave tube of a spec break ATTA (SPECBR attribute is True) still has an active Shop Flag.\n\n\n\nNote\n:"}
{"Headers": "Pipe Piece and Pipe Spool Data", "Content": "The following contains the detailed system-specific information about pipe pieces and pipe spools. It includes the underlying objects and functionality and the database attributes and pseudo-attributes.\n\n\n"}
{"Headers": "Pipe Spool Manager", "Content": "The Pipe Spool Manager contains the detailed system-specific information about pipe pieces and pipe spools. It includes the underlying objects and functionality and the database attributes and pseudo-attributes.\n\n\n"}
{"Headers": "Pipe Spool Reporting Data", "Content": "The Pipe Spool Reporting Data contains the detailed system-specific reporting information about pipe spools.\n\n\n"}
{"Headers": "Pipe Router", "Content": "The Pipe Router utility is a rule-based tool which automatically route multiple or single pipes. If non-orthogonal pipes are required, these can be created manually, refer to for further information.\nThe pipe(s) are routed, from the branch\u2019s head and ends at the branch\u2019s tail, positioning and orientating piping components (reducers and welds), and where appropriate adding connection components such as flanges and gaskets. The flow direction is always forwards (from head to tail). The pipes are created orthogonally and with the minimum number of bends or elbows and where possible clash-free.\nConstrain the route taken by the pipe(s) with the use of routing points, planes, rules and pipe racks and if required, modify the route once it has been created. Refer to Automatic Pipe Route Administration for further information.\nAll the tasks carried out in association with the Pipe Router utility are initiated from a central Pipe Router window which acts as a task hub.\n\nDefaults\nThe pipe router is supplied with defaults which can be modified if required.\n\nUse the File menu from the Pipe Router Defaults window, to save settings or load from settings from elsewhere, see System Administrator if new settings are required:\n\nThe Pipe Router Defaults window, contains all the tools to determine the defaults for the pipe router.\nThe Output messages to file fields, Directory and Filename specifies where to save and what to name the error messages file. The option to overwrite or add to the end of existing error file by selecting an option from the drop-down list is also available.\nTo remove the output message once a session check has been completed, click to select the Remove Message file at the end of session check box.\nTo specify what the Pipe Router does in the event of an error, from the Action on error drop-down list: select one of the available options.\nStop\nStops all further routing\nContinue\nContinues the routing even if an error occurs\nPause\nAn alert window is displayed, it must be acknowledged before the routing continues\nStop\nStops all further routing\nContinue\nContinues the routing even if an error occurs\nPause\nAn alert window is displayed, it must be acknowledged before the routing continues\nTo specify which component is used when the routing changes direction, from the Change direction using drop-down list select one of the available option.\nBend\nWhen a change of direction occurs, a bend is included in the routing and displays in the design database and 3D graphical view\nElbow\nWhen a change of direction occurs, an elbow is included in the routing and displays in the design database and 3D graphical view\nRule\nPipe Router searches for a rule which defines the type of component to use. To create this type of rule, refer to for further information.\nBend\nWhen a change of direction occurs, a bend is included in the routing and displays in the design database and 3D graphical view\nElbow\nWhen a change of direction occurs, an elbow is included in the routing and displays in the design database and 3D graphical view\nRule\nPipe Router searches for a rule which defines the type of component to use. To create this type of rule, refer to for further information.\nSpecify a default rule set from the Default rule set world drop-down list for all the branches created by Pipe Router which is automatically assigned as a low priority rule set. Here you or system administrator can create company and/or project specific rule sets. Refer to for further information.\nOnce the rule set has been specified define to what the rule set is applied, from the Applied to all drop-down list, select the required design hierarchy element.\nPipe Router automatically searches for and makes use of any routing planes and pipe racks with a branch to route the pipe on. The pipe racks exist within the search volume of a branch or branches, the default search volume is the volume between the head and tail of a pipe. The search can be extended outside this volume by inputting the distances in the In Z Direction (vertical) and In X/Y Directions (horizontal) fields.\nPipe Router automatically uses a routing plane or pipe rack to route a pipe only if the distance that it travels along the plane or rack is greater than a minimum travel distance. Enter the minimum distance, in the Minimum Travel Distance field.\nSpecify the minimum Pipe gap between pipes on racks (and other planes), and also specify in the Pipe gap rounding field the extent to which the gap size is rounded, which can help minimize construction errors.\nDefine a Route\nCreate the pipe and branch elements in the design hierarchy and connect or position their heads and tails and define bore. If the branch contains piping components, these must be selected. Refer to and for further information.\nRouting Pipes\nAdd the pipes to the Pipe Router window, and then route the pipes, Pipes can be added individually or in groups.\nBy default, the Pipe Router routes pipes in the order in which they are added to the Pipe Router window. The routing order can have an effect on the route taken by pipes. Refer to for further information. Pipe Router routes the selected pipes, adding elbows, gaskets and flanges, as required.\n\nWhen a pipe is added to Pipe Router, it is given a head and tail work-point. These are the points where a route begins and ends. Pipe Router positions work-points at a distance from the branch head or tail which allows for any connection components that are required.\n\nFor example, if the head of a branch is a flanged nozzle, then Pipe Router automatically adds a gasket and a flange. Pipe Router then begins routing the pipe from the end of the flange.\nHow Pipe Router Finds a Route\nThe Pipe Router creates a route using an algorithm which minimizes material cost while avoiding clashes with other objects. The algorithm has three modes of operation, described as Level 1, Level 2 and Level 3 modes. Pipe Router first searches for a route using Level 1 mode. If no clash-free Level 1 route is found, a search is made using Level 2 mode, and if no Level 2 route is found Level 3 mode is used.\nLevel One Mode\nIn level one mode, Pipe Router searches for an orthogonal route between the head and tail work-points of a pipe, using the minimum number of bends or elbows. Lever One routes (Box 3) shows examples of the routes available in level one mode.\nBox 1\nThe default route is ABC, as this requires only two bends. If this route is blocked, Pipe Router attempts to route ADE which uses three bends.\nBox 2\nIf Pipe Router cannot find a route using the routes on box one, it attempts the routes on box two, where route ABC uses three bends, and ADE uses four bends.\nBox 3\nFinally, if it is still unsuccessful in finding a route, Pipe Router attempts the routes on box three, where both routes use four bends.\nBox 1\nThe default route is ABC, as this requires only two bends. If this route is blocked, Pipe Router attempts to route ADE which uses three bends.\n\nBox 2\nIf Pipe Router cannot find a route using the routes on box one, it attempts the routes on box two, where route ABC uses three bends, and ADE uses four bends.\n\nBox 3\nFinally, if it is still unsuccessful in finding a route, Pipe Router attempts the routes on box three, where both routes use four bends.\n\nAn example of a Level One route displays a level one route in which the head work-point is facing up.\n\nLevel Two Mode\nIf all first level routes are blocked, Pipe Router attempts to find second level routes. In second level mode, Pipe Router withdraws the route into the box by a distance which enables the pipe to bypass the obstruction. Pipe Router then attempts the same routing patterns as those used in level one mode.\n\nLevel Three Mode\nIf Pipe Router cannot find a clash-free route using first and second level routes, it attempts to find a third level route. In third level mode, Pipe Router extends the box outwards until it bypasses the obstruction and then attempts to route the pipe using level one routing principles.\n\nAdding Components to a Route\nOnce Pipe Router has worked out a route, it constructs the Branch by adding whatever Elbows (or Bends) are needed.\nSpecify components in a Branch before routing, for example by importing a P&ID file as described in . Modify a routed Branch by adding other components, for example, Valves or Instruments, on the Piping tab, in the Modify group, click Component to display the Piping Component Editor window and create the components in the normal way.\nOnly the principal piping components need to be added. Pipe Router adds Flanges, Gaskets, lap joint stub ends and Welds as necessary, using the Connection Compatibility (COCO) tables to create the correct types.\nComponents can be locked into a given position, in which case they are not be moved, even if the Branch is re-routed. Refer to for further information about using locked components.\nIf there are particular constraints that must be placed on a Branch, for example, passing through a given point or plane, use one of the techniques described in .\nInsertion of Reducers at Bore Changes\nBefore Pipe Router positions any components on a Branch, it checks the Branch to see if it contains any components whose bore is different from the preceding component. If one is found, then by default the Pipe Router selects the first suitable Reducer that it finds in the catalog, regardless of whether it is concentric or eccentric.\nSet rules to specify whether concentric or eccentric Reducers are used. For information about routing rules, refer to for further information.\nHow Pipe Router Routes to Free Tails\nIf a Branch has a free Tail, that is, if the Tail is not connected to another Branch or the Tail position has not been specifically defined, Pipe Router automatically positions the Tail once it has positioned all of the components in the Branch and applied all constraints.\nIf this fails, for example, because there is a clash or a component positioning rule cannot be satisfied, then it introduces an Elbow after the constraint, before the first component. Pipe Router then positions the elbow in a direction that results in a clash-free route, and which satisfies component positioning and orientation rules.\nIf the Branch does not have any constraints, the position of the Tail depends on the position and orientation of the Branch Head. Often, this may be a Tee. Refer to for further information.\nTail direction: The TDIR attribute for a free tail is never set if the last constraint is a plane or a rack. In all other cases, TDIR is taken from the direction of the last component.\nHow the Pipe Router Positions Tees\nPipe Router checks each Branch for connections to other Branches, that is it looks for Tees or other components which have a CREF or CRFA attribute set.\nIf the Branch which connects to the Tee has a free Tail, then the Tee is treated the same as any other component.\nIn all other cases, the Tee influences the route taken by the original Branch. In general, Pipe Router selects the closest route to any constraints in the connecting Branch. If there are none, then it selects the route closest to the other end of the connecting Branch.\nTees which can be balanced are then positioned. Refer to for further information.\nWhere a Branch contains more than one Tee, the first Tee in the Branch influences the route taken. Pipe Router positions any subsequent Tees as close as possible to the next constraint, or the other end of the connecting branch.\nControl the position of a Tee by locking it in position, or by constraining the route, using a routing point. Refer to for further information.\nBalanced Tees\nPipe Router attempts to position a Tee to achieve balanced flow.\nThe Tee must be symmetric about a plane through P-arrive. The Pipe Router changes the arrive p-point to achieve this if the bores on the p-points are equal. It then checks the leave-bore and connect-bore. If the bores are equal then Pipe Router assumes that the Tee is T-shaped.\n\nThe Tail directions of /B1 and /B2 must either be equal and not in the axial direction between the Tail positions of the branches or opposite and in the axial direction between the Tail positions of the branches:\n\nThere must be no locked components on branch /B2, nor any after the Tee on branch /B1.\nIf there are multiway components in the Branches after the Tee, the Branches connected to them:\nThe Tail positions of /B1 and /B2 must be equal in two of the three orthogonal co-ordinates:\n\nThe specifications of the positionable components after the Tee on /B1 must be the same as the specifications of the components on branch /B2.\n\nThe Tee is positioned so that:\nIf any of these conditions are not satisfied, Pipe Router attempts moving the Tee back along the arrive direction (or forward along the leave direction).\nCovered Nozzles\nWhen the Pipe Router is routing a Branch there may be several others waiting to be routed. The best route for the current Branch may take the Pipe straight in front of other Nozzles, which is most likely to happen when routing from a line of Vessels. It can be avoided by:\nRefer to for further information.\nMake sure the Nozzles or Equipment owning them have obstruction volumes extending beyond their Nozzles which prevents other Pipes crossing in front of the Nozzle. The Branch connected to the Nozzle ignores this clash and successfully routes onto the Nozzle.\nConstraining a Route\nExcept in very simple cases, give Pipe Router more information about the route required to achieve a satisfactory route, then constrain a route using the following:\nThese constraints are described briefly in the following sections, and described in detail in later sections.\nLocked Components\nA locked component is a component whose position has been fixed before routing takes place. Pipe Router routes the Branch through the component. Locked components can be used to manually modify the route taken.\nIn cluttered areas, Pipe Router may not be able to find a clash-free route, in which case it puts in the simplest clashing route and informs you of the clash. Modify the route to obtain a clash-free route, by moving components away from clashes, locking them and re-routing. Both principal Piping components and router-created components (for example, Elbows), can be moved and locked.\nRouting Rules\nOne of the principal features of Pipe Router is its built-in rule engine. Use routing rules to control the selection, position and orientation of piping components, and to control how pipes use routing planes and pipe racks. Refer to for further information.\nRefer to Automatic Pipe Route Administration for further information about creating your own rules.\nRouting Points\nRouting Points are points through which a pipe must pass. Specify the position of a routing point, and the direction in which a pipe arrives at and leaves a routing point. Refer to for further information.\nRouting Planes\nRouting planes are orthogonal planes which attract pipes to them and then guide the pipes in the direction of the plane. Routing planes are useful, for example, where to group pipes together, perhaps along a wall or ceiling. Refer to for further information.\nPipe Racks\nIn Pipe Router, a pipe rack is composed of a group of routing planes which enables the modelling of the route used on a physical pipe rack. There are two ways in which to create a pipe rack. Create pipe racks on existing steelwork structures or model them as a group of planes.\nFind the second method useful when working on a conceptual design and does not want to spend time creating steelwork structures. Once a pipe rack has been created, use routing rule to specify how different sorts of pipe run on the rack. Refer to for further information.\n\nChecking the Status of a Branch\nOnce the pipe(s) have been routed, check the status of the branch, by selecting Display > Status Summary, the Pipe Router Status Summary window shows that two Branches have been routed successfully.\n\nChanging the Order in which Pipes are Routed\nPipe Router routes pipes in the order in which they are added to the Pipe Router window. However you may need to change the routing order of particular pipes to make sure that Pipe Router routes the most expensive pipes first. Or if working with pipes that are in close proximity to one another or where pipes cross paths.\nChange the routing order, by selecting from a choice of options in the Modify > Routing Order > from the Pipe Router window.\nTo reorder pipes according to their specification, select Group by specification check box, the display is reordered in alphabetical order of their specification names, for example, all pipes which use the specification A150, followed by all pipes which use the specification B150, and then the other pipe specifications in the sequence. Use this option in conjunction with the attribute radio buttons.\nFor example, reorder pipes so that all Pipe Router displays all pipes which use the specification A150 in descending order of their head bore, followed by all B150 specification pipes.\nRouting Messages\nAs Pipe Router routes a pipe, it examines each branch and generates a message about any routing errors that it finds. These messages can help you understand and correct errors. It can view these messages both during and after pipe routing, providing you have set up a file in which to store the messages, as described previously.\nTo view routing messages, select Display > Routing Messages from the Pipe Router window to display the Routing Messages window.\n\nThe Routing Messages window is empty if Pipe Router routes all pipes without any errors.\nSelect Control > Close to close the Routing Messages window.\nBranch Detail Window\nPipe Router enables you to view details of the components and constraints in a branch using the Branch Detail window. Select options to constrain the route taken by a branch.\nFor example, lock components in position, create routing points and add routing planes and pipe racks to the constraint list. All of these facilities are explained in later sections.\nSelect one of the routed Branches from the Pipe Router window and click Branch Detail to display the Branch Detail window, which contains details of the selected branch.\n\nRefer to for more information on the contents of the Branch Detail window.\nPositioning and Locking Components\nAdd components to Branches after they have been routed and control where the components are positioned. The effect that positioning and locking components has when a Branch is re-routed is also considered.\nDeletable, Positionable and Locked Components\nPipe Router sees all piping components as deletable, positionable or locked. If the Branch Detail window displays for a Branch that has been routed by the Pipe Router, all the components are listed as deletable.\nThe components that Pipe Router creates in a Branch are described as Deletable. If the branch is re-routed, Pipe Router deletes all the components that it has created and re-create them.\nAfter a Branch has been routed, components can be added manually in the normal way. Select the correct element in the Branch Members list, on the Piping tab, in the Create group, click Component to display the Piping Component Editor window. These components are described as Positionable. If the Branch is re-routed, these components are not deleted, but they may be moved to fit on the new route.\nPositionable components can be locked into a given position, in which case they are not moved, even if the Branch is re-routed.\nThe order of Positionable components in the Branch Members list is maintained, and so is their order relative to any constraints in the Branch. For example, if a Valve is added before a Locked Tee, the Valve is not be moved past the Tee.\nTo make changes to a Branch, and then re-route it, keeping some or all of the components that Pipe Router has added by making them positionable, rather than deletable. These can also be locked.\nTo change the status of a component, select it from the list on the Branch Detail window, and then select one of the options under the Modify menu on the window.\n\nThe choices are: Constraint, Toggle Head Lock, Toggle Tail Lock, Lock Position, Make Positionable, Make Deletable, Toggle Head/Tail Relative, Head W-P, and Tail W-P.\nPositioning Relative to the Head or Tail\nEach component in a branch is positioned relative to the head or tail of the branch. If a component is head relative, then Pipe Router places that component as close as possible to the head of the branch, allowing for other components and any constraints. If a component is tail relative, then that component is positioned as close as possible to the tail of the branch.\nPipe Router routes a pipe from head to tail and so all components are initially created head relative.\nChange the head/tail relative property of any positionable component. Select it in the list on the Branch Detail window, and then select Modify > Toggle Head/Tail Relative.\nHead and Tail Work-points\nEach Branch has a Head Work-point and a Tail Work-point. insert components between the Head (or Tail) and its work-point, which can be used, for example, to position a Valve directly onto a Nozzle.\nMoving the Head or Tail Work-point\nPosition the Head W-P after a particular component in a Branch or position the Tail W-P before a particular component, which enables the Valve to be positioned directly onto the Nozzle of vessel /VESS-1, then re-route the Pipe without affecting the position of the Valve.\nFrom the Branch Detail window, select Modify > Tail W-P to display the Modify Tail W-P window.\n\nFrom the Modify Tail W-P window, select VALVE 1, click OK.\nFrom the Pipe Router window, select the Route: Selected option.\n\nPipe Router re-routes the Pipe from the Head Work-point to the Tail Work-point, which is now positioned before VALV 1.\nCheck the position of the valve, display the Branch Detail window for the branch, then scroll to the bottom of the Components/Constraints list to display the details.\n\nLocking and Unlocking a Component\nPipe Router enables piping components to be locked in position, to make sure that a branch component remains in its current position, even if the branch is re-routed.\nTo lock a component, from the Branch Detail window, select the component to be locked in position, select Modify > Lock Position.\nTo unlock a locked component, select Modify > Make Positionable for main piping components, or Modify > Make Deletable for Pipe Router generated components.\nManually Routing Non-orthogonal Sections\nPipe Router is an orthogonal router so if non-orthogonal sections of pipe in a branch are required. Route these sections by hand and then lock all the components in the section (including the start and end bend or elbow) and route the remainder of the pipes using Pipe Router.\nAligned, Locked, Non-orthogonal Components\nIf two locked components with non-orthogonal arrive and/or leave direction are aligned, with no intervening components, so that a straight piece of tube can run between them without clashing, Pipe Router uses this route, which also happens if the first component is aligned with the head or the last component is aligned with the tail. If the straight, non-orthogonal routes clash, only orthogonal routes are considered to avoid the clash.\nThe default orthogonal route between the pump and the vessel.\nUsing aligned and locked elbows to give a non-orthogonal route.\n\nThe default orthogonal route between the pump and the vessel.\n\nUsing aligned and locked elbows to give a non-orthogonal route.\nIn all other cases Pipe Router attempts to insert a bend or elbow to turn into an orthogonal direction as close as possible to the component.\nNon-aligned Non-orthogonal Components\nIf non-orthogonal components are not aligned, only orthogonal routes between them are considered.\nNon-aligned components still give an orthogonal route.\n\nNon-aligned components still give an orthogonal route.\nNon-orthogonal Sections with Unlocked Components\nIf there are other, positionable, components between non-orthogonal locked components, orthogonal routing is used. Pipe Router may add connection components on to the locked components, but note that no bore change (which would require the addition of a reducer) is permitted.\nA positionable Tee has been inserted in the Branch, which has caused Pipe Router to revert to an orthogonal route, using additional Elbows.\nDetail of the area close to the Tee.\nThe route achieved with the Tee Locked.\n\nA positionable Tee has been inserted in the Branch, which has caused Pipe Router to revert to an orthogonal route, using additional Elbows.\n\nDetail of the area close to the Tee.\n\nThe route achieved with the Tee Locked.\nLock several non-orthogonal components in a row. For example, lock two 45 degree elbows to give a non-orthogonal section of pipe and place a locked valve on this section of pipe. Pipe Router does not route any part of the Branch between the elbows, providing that straight pipe does not clash; and it adds any necessary connection components to the valve. However, the valve must be locked: if it is positionable Pipe Router routes orthogonally between the elbows.\nIt may be better to continue in a non-orthogonal direction from a nozzle until a route has passed an obstruction, because this might give a shorter route with fewer elbows. Lock the elbow at \u2018A\u2019 to give this route:\n\nUsing Rules for Minimum Tube Length\nTo find that components such as Olets and Stub-in Tees are positioned immediately next to another component, if the COCO tables allow. Use the Upstream and Downstream Rules provided with Pipe Router to specify minimum lengths of Tube. Refer to for further information about using rules.\nCreate and Use Routing Points\nRouting Points can be used to constrain a route, these points are points through which a branch passes. To define the coordinates of a point and the direction in which a branch arrives at and leaves a point.\nTo add as many routing points as required but the points must be created at the correct position in the sequence of constraints.\nCreate a Routing Point\nTo create a routing point, select the required branch from the Pipe Router window, select Branch Detail to display the Branch Detail window. From the Branch Detail window, select Create > Routing Point to display the Create Routing Point window.\n\nTo enter the coordinates on the Create Routing Point window or use the other options available on the menu, which are similar to the normal AVEVA E3D\u2122 positioning options. Routing points can only be positioned after positionable or locked components.\nBy specifying a different arrive and leave direction, a bend or elbow has to be inserted at the position of the routing point. If a change of direction is not required, select the Through Direction and specify the direction for the pipe to take at that point. If the direction is unset, Pipe Router selects the best direction to minimize the number of bends or elbows used.\nUse DATUMs as Routing Points\nThere is an option on the Create Routing Point window which allows you to use an existing DATUM point as a routing point. Two branches should not use the same Datum point as a constraint since they would then clash.\nIf you wish to use a Datum where two branches meet, just one of the branches should have the point as a constraint. For example, Branch /P1/B1 ends at a Battery Limit and Branch P2/B1 connects to its Tail. Branch /P1/B1 should have the Datum as the last constraint and a Free Tail. The Head of Branch /P2/B1 is positioned at the Tail of /P1/B1.\nMoving a Routing Point\nTo modify the position of a routing point at any time. From the Pipe Router window, select the branch to modify, click Branch Detail to display the Branch Detail window.\nSelect the routing point to modify from the Components/Constraints list. Select Modify > Constraint to display the Modify Routing Point window. Select one of the following options, depending on the type of modification:\nMove > Distance\nTo move a routing point a distance in a specified direction either from the current location, or relative to another element which can be identified using the cursor or another method.\nMove > Towards\nTo move the point a specified distance towards another element, which can be identified using the cursor, by specifying a named element or, which may be the head, tail or, the next element in the branch.\nIf a DATUM has been used as a routing point, the standard AVEVA E3D\u2122 positioning options can be used to modify its position.\nRouting Rules\nRouting Rules are special AVEVA E3D\u2122 rules which are used to control how components are selected, positioned and orientated as Branches are routed and how Pipes are packed on Pipe Racks and Routing Planes.\nUse the sample routing rules supplied with the Pipe Router, or define routing rules refer to Automatic Pipe Route Administration for further information.\nRouting rules can be applied to individual branches or all branches within a particular site, zone, or pipe. Rules can be applied or removed to individual components, as required.\nExpressions\nA routing rule consists of AVEVA E3D\u2122 expressions. AVEVA E3D\u2122 expressions are described in detail in .\nAVEVA E3D\u2122 expressions consist of the following:\nFor a list of AVEVA E3D\u2122 attributes, refer to for further information.\nApply a Rule Set to a Branch\nOnce a rule set has been created, it can be applied to a branch. The rules then take effect on the components in the branch. From the Pipe Router window, select the branch with which you want to associate a rule set.\nFrom the Pipe Router window, select Settings > Apply Rules > To Branch to display the Apply Rules to SELECTED window.\n\nFirst select the rule world which contains the rule sets to apply to the branch from the RULE WORLD list, which contains all the Branches selected on the Pipe Router window. From the Rule sets available in current world list, select the rule set. The rule set can be added as high priority or low priority.\nClick Add HIGH to add the rule set to the High Priority Sets list or Add LOW to add the rule set to the Low Priority Sets list. Click Apply. You must then route the branch to apply the rules.\nPipe Router first checks to see if there are any rules that apply to a component from the high priority rule sets. If there are none then Pipe Router checks if there are any rules that apply in the low priority rule sets.\nFrom the Settings > Apply Rules options on the Pipe Router window applies the rule sets to a site, zone or pipe. In these cases all branches which are below them in the hierarchy also have the rule sets applied, unless they have rule sets specifically applied.\nBy default, Pipe Router applies all the rules in the specified sets to a branch, providing they are appropriate. However, to remove a rule from a particular component in a branch, or add one from another rule set.\nRemove a Rule Set\nTo remove a rule set, first select the branch from the Pipe Router window, then select Settings > Apply Rules > To Branch to display the Apply Rules window, the rule set to be removed must be selected. Click Remove HIGH or Remove LOW as appropriate. Click Apply.\nIf a Rule Set is applied to a Pipe, Site or Zone, it is removed from all Branches in that Pipe, Site or Zone.\nInclude a Rule from another Rule Set or World\nIf required, apply a rule to a component from another rule world or rule set, from the Pipe Router window, select the branches to apply the rule to, click Branch Detail. From the Branch Detail window, click Component Rules to display the Component Rules window, which can be used to add additional rules from the available rule sets, or from another rule world.\n\nFrom the Rules applying to current component list, select the component that the rule is applied to.\nThe letter that precedes the rule description shows where the rule was originally applied. The letters used are:\nFrom the Rules available list, select the rule to be applied to the selected component, then click Include. The rule is added to the list of rules which apply to the component. Click Dismiss to close the Component Rules window.\nDisabling a Rule from a Component\nToprevent Pipe Router from applying a rule to a particular component in a branch, from the Pipe Router window, select the branch which contains the component. Click Branch Detail to display the Branch Detail window. From the Branch Detail window, select the component to be excluded from the rule. Click Component Rules to display the Component Rules window.\nFrom the list of rules that apply to the current component, select the rule to disable from the component, then click Disable. Pipe Router places an asterisk (*) to the left of the rule description to indicate that the rule is now excluded from being used.\nTo re-enable a disabled rule, select the rule, the"}
{"Headers": "Automatic Pipe Route Administration", "Content": "Routing Rules are special AVEVA E3D Design rules which are used to control, for example, how Pipe Router selects, positions and orientates components as Branches are routed, and also how Pipes are packed on Pipe Racks and Routing Planes.\nYou can apply routing rules to individual branches or all branches within a particular site, zone, or pipe, and you can also apply rules to individual components and remove rules from individual components, as required.\nRouting Rule Purposes\nThere are different types of routing rules , which are used for different controls on the route. Rules are identified by their Purpose (PURP) attribute, and unlike other elements in AVEVA E3D\u2122, you cannot create different, user-defined purposes for routing rules.\nThe routing rules available are listed below, identified by their PURP attribute, and with a short description. The purpose is set to a four-letter code, but it sometimes displays as a more descriptive text on the AVEVA E3D\u2122 Router windows. How each rule is applied is described in detail in .\nPRPR\nAll rules with this Purpose are executed before a Branch is routed.\nSelection\nBEND\nBend or elbow selection: controls whether a bend or elbow is used for changing the direction of a pipe\nREDU\nReducer type: specified when concentric or eccentric reducers are used\nPositioning\nDNSM\nDownstream pipe requirement: the length of pipe required downstream to the next component\nUPSM\nUpstream pipe requirement: the length of pipe required upstream from the previous component\nELEV\nComponent elevation: absolute or relative elevation of a component\nLOCA\nComponent location: 3D position of a component\nOrientation\nMAJO\nOrientate on major axis: positioning on vertical or horizontal pipe segment.\nMINO\nOrientate on minor axis: such as the orientation of a handwheel\nClash exclusion\nCLEX\nThese rules are used to allow specified types of element to clash.\nPipe racks (and routing planes)\nTRAV\nPipe Rack travel plane selection: controls which pipe rack travel plane is used to route a particular type of branch\nENTR\nPipe Rack entry plane selection: controls which pipe rack entry plane is used to route a particular type of branch\nEXIT\nPipe Rack exit plane selection: controls which pipe rack exit plane is used to route a particular type of branch\nSHOE\nShoe height requirement\nWEIG\nIdentify heavy pipe\nADGP\nExtra gap required on plane or rack\nFLWI\nFlange width on plane or rack\nPost-processing\nPOPR\nAll rules with this Purpose are executed after a Branch has been routed.\nPRPR\nAll rules with this Purpose are executed before a Branch is routed.\nSelection\n\nBEND\nBend or elbow selection: controls whether a bend or elbow is used for changing the direction of a pipe\nREDU\nReducer type: specified when concentric or eccentric reducers are used\nPositioning\n\nDNSM\nDownstream pipe requirement: the length of pipe required downstream to the next component\nUPSM\nUpstream pipe requirement: the length of pipe required upstream from the previous component\nELEV\nComponent elevation: absolute or relative elevation of a component\nLOCA\nComponent location: 3D position of a component\nOrientation\n\nMAJO\nOrientate on major axis: positioning on vertical or horizontal pipe segment.\nMINO\nOrientate on minor axis: such as the orientation of a handwheel\nClash exclusion\n\nCLEX\nThese rules are used to allow specified types of element to clash.\nPipe racks (and routing planes)\nTRAV\nPipe Rack travel plane selection: controls which pipe rack travel plane is used to route a particular type of branch\nENTR\nPipe Rack entry plane selection: controls which pipe rack entry plane is used to route a particular type of branch\nEXIT\nPipe Rack exit plane selection: controls which pipe rack exit plane is used to route a particular type of branch\nSHOE\nShoe height requirement\nWEIG\nIdentify heavy pipe\nADGP\nExtra gap required on plane or rack\nFLWI\nFlange width on plane or rack\nPost-processing\n\nPOPR\nAll rules with this Purpose are executed after a Branch has been routed.\nHow Routing Rules are Constructed\nRouting rules consist of AVEVA E3D\u2122 expressions which define:\nAll rules must have a selection expression.\nRules which use logical expressions are called logical rules. A Rule which does not have a logical expression is called a real rule, because its action (see below) is a real expression.\nActions\nThe Logical expression in a rule tests whether or not the component satisfies the rule. If not, that is, if the logical expression evaluates to False, and the rule has an action, the action is applied. Pipe Router then re-tests the component. If the logical expression still evaluates to False, the Action is reversed.\nIf you do not define an action for these rules, then the default action is taken, which depends on the rule.\nUsing PML Functions in Routing Rules\nThe Logical and Action expressions in Routing rules can call PML functions, which allows you to define much more complex logical tests and actions than can be done using simple expressions. A function is called by setting the rule action to a text string which is the name of the .pmlobj file. The file contains the object definition, followed by a method definition.\nThe function must be defined using fixed names for the following elements:\nCEREF\nThe DBREF of the element the rule applies to.\nRESULT\nThe returned boolean result. (Logical parts of rules only.)\nRULEMETHOD\nThe method which is applied.\nOBSREF\nThe DBREF of the Element clashing with the Branch. (Clash exclusion rule only).\nCEREF\nThe DBREF of the element the rule applies to.\nRESULT\nThe returned boolean result. (Logical parts of rules only.)\nRULEMETHOD\nThe method which is applied.\nOBSREF\nThe DBREF of the Element clashing with the Branch. (Clash exclusion rule only).\nExamples of calling PML functions are given in the following sections:\nPre-processing rules\nRefer to for further information.\nMinor Axis orientation\nRefer to for further information.\nClash exclusion\nRefer to for further information.\nPost-processing rules\nRefer to for further information.\nPre-processing rules\nRefer to for further information.\nMinor Axis orientation\nRefer to for further information.\nClash exclusion\nRefer to for further information.\nPost-processing rules\nRefer to for further information.\nHow Routing Rules are Applied\nThe following sections describe in detail which expressions are required by each type of rule, and how the rules are applied. Most of the examples are taken from Rules supplied with the product. To see more examples, select Settings > Routing Rules from the Pipe Router window, which displays the Routing Rules window. Select a Rule Set, then select a Rule from the list. To see the expressions in the rule, select Modify to display the Rule Attributes window.\nPre-processing (PRPR)\nLogical, will have Action\nPre-processing (PRPR)\nLogical, will have Action\nAll rules with this Purpose are executed before a Branch is routed. The Action is normally a PML function, which must have been defined before the rule is applied.\nTypically this type of rule is used where it is simpler to have a single rule to create, position and orientate several components rather than have individual rules. For example:\nThe Selection part of the rule identifies a key component: for example, you can identify Valves which require control loops by setting a UDA to a certain value, and then setting the selection expression to select all the Valves with the given attribute value.\nThe PML function then creates, positions and orientates the components and finally sets the head working point attribute to the last component covered by the rule. AVEVA E3D\u2122 Router then takes over and routes the Branch.\nA suitable PML function displays following. Note that at the end of the positioning and orientating commands, the RLOC attribute is set to 0 (Locked).\nThe input to Pipe Router would be Pipes with a main Branch with the following sequence of components defined:\nThere would also be a second Branch, owning a Valve, with the Branch Head and Tail connected to the two Tees in the main Branch, which form the control loop.\nThe rule to call function displays and can be defined:\n\nThe rule is applied to the elements required in the normal way. An example of the control loop created displays in the following picture.\n\nSelection\nBend or elbow selection (BEND)\nLogical, no Action\nBend or elbow selection (BEND)\nLogical, no Action\nUsed to choose the type of component used to change direction. For example, the selection expression can be:\nand the logical:\nmakes sure that all Branches with bores less than or equal to 65 use Bends rather than Elbows.\n\nThe default method of changing direction, set on the Pipe Router Defaults window, is using Elbows.\n\nThe default method of changing direction, set on the Pipe Router Defaults window, is using a Rule. The rule specifies that small bore pipes change direction using Bends\nReducer Selection (REDU)\nLogical, no Action\nReducer Selection (REDU)\nLogical, no Action\nTo specify whether concentric or eccentric reducers are selected. For example, if the default reducers in a specification are eccentric, and you want concentric reducers in vertical sections of pipe but eccentric reducers in horizontal sections, the Selection expression in the rule can be:\nThe logical expression to specify eccentric reducers in all the selected cases would be:\n      \n         \n            \n               \n                  \n                \n               \n                  \n                \n            \n            \n               \n                  The default reducer in the Specification is eccentric.\n                \n               \n                  The rule specifies that reducers on vertical legs are concentric\n                \n            \n         \n      \n   \n\n\nThe default reducer in the Specification is eccentric.\nThe rule specifies that reducers on vertical legs are concentric\nPositioning\nThere are two pseudo-attributes which are particularly useful in positioning expressions:\nSTAP\nis the length of straight tube before the component.\nSTLE\nis the length of straight tube after the component.\nSTAP\nis the length of straight tube before the component.\nSTLE\nis the length of straight tube after the component.\nThe lengths are measured from the component up to one of the following:\nDownstream pipe requirement (DNSM)\nLogical, can have Action\nDownstream pipe requirement (DNSM)\nLogical, can have Action\nUsed to control the length of straight pipe which is downstream from the previous component. If the rule logical fails, the action, if it exists, is applied. The action should be an expression that moves the component a distance from the previous to make sure a straight length of pipe. For example:\nSelection\nLogical\nYou can omit the action by setting the Action field on the window to unset, but the result may be unpredictable, particularly if other rules are being applied, and it is not recommended. If no action exists, and component positioning is head relative, the component is moved 2/3 the distance along the leg, and then re-tested. If component positioning is tail relative, the preceding component is moved if necessary when it is positioned.\nA Tee is positioned by default.\nThe rule is applied and the Tee is moved 2/3 of the distance along the leg between the Elbow and the Routing Plane\nUpstream pipe requirement (UPSM)\nLogical, can have Action\n\nA Tee is positioned by default.\n\nThe rule is applied and the Tee is moved 2/3 of the distance along the leg between the Elbow and the Routing Plane\nUpstream pipe requirement (UPSM)\nLogical, can have Action\nThe rule controls the length of straight pipe which is upstream from the next component.\nSelection\nLogical\nAn example of an action is:\nwhere the POLAR AXES keywords are used to specify a position in terms of a distance in a given direction from a point, and PREVPP is the previous p-point.\nYou can omit the action by setting the Action field on the window to unset, but the result may be unpredictable, particularly if other rules are being applied, and it is not recommended. If no action exists, and component positioning is tail relative, the component is moved 1/3 of the upstream distance, and then re-tested. If component positioning is head relative, the following component is moved if necessary when it is positioned.\nElevation (ELEV)\nLogical, can have Action\nElevation (ELEV)\nLogical, can have Action\nThe rule controls the elevation of a component. The following example uses the CLOSEST keyword in the logical expression to specify that components must be positioned at a height greater or equal to 0.61m vertically above an EQUI whose purpose is FLOO.\nSelection\nLogical\nA position on the closest vertical segment of pipe equal to the required elevation is found. If no position on the existing pipe can be found, the action is applied with the position adjusted to minimize the use of bends or elbows.\nIf the logical test is False, any action set is applied.\nLocation (LOCA)\nLogical, can have Action\nLocation (LOCA)\nLogical, can have Action\nUsed to position a component at a given location. The following example is a test for a component in a sub-branch being positioned at p-point 4 of the connecting component in the owning branch:\nIf the logical test fails, the action is applied and the test repeated. If it fails again, a message is output.\nThe corresponding action expression would be:\nTo position the component at p-point 4 of the connecting component in the owning branch.\nOrientation\nMajor axis\nLogical, no Action\nMajor axis\nLogical, no Action\nControls the major orientation of the component, which is the arrive/leave axis. For example:\nIf this fails, the component is moved to each leg in turn until one is found that passes. No action is allowed.\nMinor axis\nLogical, can have Action\nMinor axis\nLogical, can have Action\nControls the minor orientation of a component, which is the axis perpendicular to the arrive/leave axis. Frequently this axis is the direction of a valve handwheel. For example:\nIf the rule logical fails, the action is applied. If the logical then fails, the component is moved to another leg, and re-tested. If the component clashes, it is moved along the leg and then re-tested.\nIf there is no action, the component is rotated in increments of 90 degrees to find a non-clashing orientation which passes the rule. If after four attempts it still fails, the component is moved along the leg and retried. If no suitable positions are found on the leg, the component is moved to the next leg and the procedure repeated.\nExamples using PML Functions\nThe following example shows how you can call PML functions for the Logical and Action expressions in a Minor Axis rule for positioning a Valve at and angle of 45 degrees.\nFirst, the Logical expression is set to ( 'minological' ), which calls the following PML function:\nIf the Logical test evaluates to False, that is, if P3 does not have the specified orientation, the Action is carried out.\nThe Action expression is set to ( 'minoaction' ), which orientates the P3 direction of the component:\n      \n         \n            \n               \n                  Clash Exclusion (CLEX) \n                \n               \n                  Logical\n                \n            \n         \n      \n   \nClash Exclusion (CLEX) \nLogical\nA Clash Exclusion rule allows certain clashes to be approved in advance. A use for this is specifying that only non hazardous pipes are allowed in certain areas. Clash exclusion rules can use expressions or functions.\nExample using Expressions\nFor example, the following rule can be used where two groups of elements are always allowed to clash. In this case, Branches carrying radioactive material have their PURP attribute set to RADI. All Zones which are safe for humans to enter have their PURP set to HUMA. The rule allows all Branches whose PURP is not set to RADI to pass through all human zones:\nSelection\nLogical\nThe selection part of the rule is used to identify the Branch or Branch member which is clashing and the logical applies to the obstruction clashing with the Branches.\nExample using a PML Function\nIf a more complicated solution is needed, use a PML function. A simple example is\nPipe Racks and Routing Planes\nAutomatic routing along Pipe Racks is described in . In summary, Pipe Router sees a Pipe Rack as a group of routing planes. Each plane has its FUNCTION attribute set, for example to UTIL for planes which are going to route utilities pipes. You should also make sure that Branches which are routed along Pipe Racks have their PURPOSE attribute set appropriately, so that you can identify which Branches should be routed along a given plane.\nTravel Plane Selection\nLogical, no Action\nTravel Plane Selection\nLogical, no Action\nTo control which travel plane of a pipe rack is used to carry a particular branch. An example of the selection expression, which would apply the rule to all Branches to with Purpose set to COOLING, is:\nAn example of the logical test, which routes the selected Branches along the Plane with its Function set to UTIL is:\nEntry Plane Selection\nLogical, no Action\nEntry Plane Selection\nLogical, no Action\nTo determine which entry plane is used to control a branch as it enters a pipe rack. Normally there is one above and one below, to allow for branches with both liquid and vapour contents to use the rack. An example of the selection might be:\nAn example of the test can be:\nwhich would cause pipes containing gas for cooling to use the upper entry/exit plane to get to/from the UTIL travel plane.\nExit Plane Selection\nLogical, no Action\nExit Plane Selection\nLogical, no Action\nThe rule determines which exit plane is used to control a branch as it exits a pipe rack. Normally there is one above and one below, to allow for branches with both liquid and vapour contents to use the rack. An example of the selection might be:\nAn example of the test can be:\nwhich would cause pipes containing gas for cooling to use the upper entry/exit plane to get to/from the UTIL travel plane.\nShoe Height\nReal\nShoe Height\nReal\nBranches routed via planes or pipe-racks can be offset by a user-specified distance from the plane to allow for shoe-heights. The shoe-height is specified using rules with PURPose SHOE.\nFor example:\nSelection:\nAction:\nHeavy Pipe\nLogical, no Action\nHeavy Pipe\nLogical, no Action\nYou can specify that heavy pipes are placed at the edges of routing planes and light ones at the center. When choosing this packing method, the PLPM attribute of the plane is set to WEIG, and Pipe Router looks for a weight rule to determine whether pipes are light or heavy.\nThe logical expression evaluates to False if the pipe is to be placed at the edge of the rack.\nFor example:\nSelection:\nLogical:\nAll Pipes with Bore greater than 300mm are placed at the edge of the rack.\nRefer to for further information on Pipe packing methods.\nExtra Gap\nReal\nExtra Gap\nReal\nAllows you to specify an additional gap between some pipes, for example, very hot pipes.\nAdditional gaps are determined by rules applied to the default bend or elbow of a branch. For example, for branches with temperature greater than 500 degrees, the following rule gives an additional gap of 0.2 times the arrive bore of the component:\nSelection:\nAction:\nFor more details of additional gaps, see .\nFlange Width (FLWI)\nReal\nFlange Width (FLWI)\nReal\nFlange width rules are used to set the gap between Pipes on Routing Planes and Pipe Racks when the Pipe run on the plane includes Flanges. The rule is applied to the default Flange for the Pipe. The gap can be calculated in several ways.\nExample 1\nSelection:\nAction:\nExample 2\nUses flange parameters:\nSelection:\nAction:\nExample 3\nThe next example uses a property of the Flange, which would be specified in a dataset:\nThe rule can then be:\nSelection:\nAction:\nRefer to for further information on how Flange widths are calculated.\nPost-processing\nPost-processing (POPR)\nLogical, will have Action\nPost-processing (POPR)\nLogical, will have Action\nAll rules with this Purpose are executed after a Branch has been successfully routed. They can be used to add extra details to a Branch such as Drains and Vents or slope the line. The Action is normally a PML function, which must have been defined before the rule is applied.\nThe following example creates an expansion loop:\nThe following illustrations show a Branch, with and without the Post-processing Rule applied.\n\n\nCreate and Edit Routing Rules\nAVEVA E3D\u2122 stores rules within a hierarchy. There are two administrative elements within the hierarchy:\nAVEVA E3D\u2122 stores routing rules, whose type is GRUL, within a rule set. When you can create a new rule, define the type of rule by selecting the correct purpose, the defining the expressions within it. The rule can now be applied to individual branches or all the branches in a particular site, zone or pipe.\nBy default, all rules in the rule sets applied to a branch are considered to be applied to each component in the branch. However, you can also disable any of the rules, or apply rules from other rule sets, to any individual component.\nA sample set of rules is provided with Pipe Router in the Sample Project. The Rule World is named /PIPES-RULES, and it owns several rule sets. The rules in the rule sets are examples which you can use to build a customized set, and do not necessarily represent good engineering practise.\nTo create a rule world:\nFrom the Pipe Router window, select Settings > Routing Rules to display the Routing Rules window. Select Create > Rule World to display the Create Rule World window. In the Name box, input a name for the rule world, click OK to create the Rule World.\nThe rule world is created and displays in the Members List. Create a rule set within the rule world.\nTo create a rule set:\nMake sure that at the level of the Rule World in which you want to create the rule set is selected. From the Routing Rules window, select Create > Rule Set to display the Create Rule Set window. In the Name box, input a name for the Rule Set. In the Function box, input the function of the rule set. (The function is a descriptive term which enables you and other users to identify the purpose of the rules contained within the rule set.) Click OK to create the Rule Set.\nThe set displays in the Members List. You can now create routing rules and store them within the rule set.\nCreate a Routing Rule:\nFrom the Pipe Router window, select Settings > Routing Rules to display the Routing Rules window.\n\nSelect where the rule is to be stored by first selecting the rule world from the Current Rule World drop-down list, and then the rule set from the Current Rule Set drop-down list.\nTo create a new rule, select Create > Rule > New to display the Create Rule window. A new rule element (GRUL) is created in the design hierarchy.\n\nTo name the new rule:\nIn the Name box, input a name for the new rule element, which is the name of the rule element (GRUL) that displays in the design hierarchy.\nClick OK to name the new rule element, close the Create New Rule window and display the Rule Attributes window.\nClick Cancel to discard inputs and close the Create New Rule window.\n\nIn the Description box, input a description for the rule. The description displays in the Routing Rules window.\nSelect a purpose for the rule from the Purpose drop-down list.\nIn the Selection box, input an expression. For example: ALL VALV WITH (ATTRIB STYP EQ \u2018GATE\u2019), this expression tells Pipe Router that the rule is applicable to all valves that have their attribute STYP set to GATE, that is, all gates valves.\nIn the Logical box, input an expression. For example: ( ATTRIB PDIR 3 EQ N ), this expression checks whether or not the direction of P3 on each gate valve is set to north. If it is, then the gate valve meets the criteria of the rule and no action is taken. If the direction of P3 is not north, then Pipe Router performs the action expression described in the next step.\nIn the Action box, input an expression. For example: (AXES PP 3 IS N AND AXES PL IS AXES PL OF PREV), this expression tells Pipe Router to change the direction of P3 to north, and make the leave direction the same as for the previous component.\nSelect the attribute of the CE, click Current Rule. The Rule Attributes window is now populated with the details for the current rule.\nTo test the rule:\nSet the extent of the test (World, Site, Zone, Pipe), from the Test Rule drop-down list, which performs the selection operation defined for the rule, then perform the logical test for each component selected, and report which components passed and which failed. The report displays in the Rules Testing window.\n\nClick OK to create the routing rule. You can now apply the rule to a Branch in the usual way.\nClick Cancel to discard any inputs and close the Rule Attributes window.\nTo copy a rule:\nTo copy an existing rule, from the Routing Rules window, select Create > Rule > Copy to display the Create Copy Rule window.\n\nTo name the copied rule:\nIn the Name box, input a name for the copied element, which is the name of the rule element (GRUL) that displays in the design hierarchy.\nClick OK to name the copied element and close the Create Copy Rule window and display the Rule Attributes window.\nClick Cancel to discard inputs and close the Create Copy Rule window\nWhen you create a copy of a rule, the Rule Attributes displays, filled in with the details of the copied rule. You can then edit the details of the rule, which enables you to select an existing rule and use its details as the starting point for a new rule or modify the details to suit your purpose.\nModify a Routing Rule\nEdit a routing rule, using as an example the sample rules supplied in the rule set TRAVEL-RULES. The rules are modified to give a better route for the pipe rack example in .\nUsing Rules to Specify How Pipes Use a Pipe Rack\nSpecify the type of pipes routed on each level of a pipe rack, using routing rules. For example, you can tell Pipe Router to place all process pipes on the bottom level of a rack and all utility pipes on the top level of a rack. If there are more than one entry/exit plane, you can specify the way in which pipes enter onto and exit from a particular level. For example, have all liquid utility pipes climbing onto a travel plane and all gas utility pipes dropping onto the same travel plane.\nFor example, you can edit the example pipe rack rules that are supplied with Pipe Router and apply them to avoid the pockets created by the default route.\nTo modify a routing rule, from the Pipe Router window, select Settings > Routing Rules to display the Routing Rules window.\n\nThe Rules available are supplied in the sample project. Make sure that the Current Rule World is set to PIPE-RULES and the Current Rule Set is TRAVEL-RULES. There are three Rules supplied: a Travel Plane Rule, an Entry Plane rule and an Exit Plane rule.\nTo see the expressions in the Travel Rule, you must select the rule in the list and then select Modify > Rule on the Routing Rules window. The Rule Attribute window displays and is populated with the attributes for Travel Rule.\n\nFrom the Rule Attributes window, note that:\nSelect the Exit rule in the list on the Routing Rules window and click Current Rule on the Rule Attributes window. Change the Logical expression to be:\nBefore you can test the rules, the Pipe PURP attribute must be set to PROC.\nSelect Purpose from the list of attributes. In the Value column, input PROC.\nPress the Enter Key and the Purpose row is highlighted to indicate that the update has succeeded.\nFrom the Rule Attributes window, you can now test the rule:\nFor example, the exit plane rule. Select the exit Plane rule in the list and make sure that Pipe 2001 is the Current Element. Set Test Rule to Pipe to display the Rule Testing window, which shows you that 1 Branch has been selected for the rule but 0 Plane. No Planes have been selected because there are no Planes with Function set to EXIT.\nTo modify the functions of the planes in the Pipe Rack:\nMake the Pipe Rack the current element and select Modify > Pipe Rack from the Pipe Router window.\nOn the Modify Pipe Rack window, change the Function of the planes:\nLevel 1 Upper Entry/Exit Plane:\nEXIT\nLevel 1 Travel Plane:\nPROC\nLevel 1 Lower Entry/Exit Plane:\nENTRY\n\nLevel 1 Upper Entry/Exit Plane:\nEXIT\n\nLevel 1 Travel Plane:\nPROC\n\nLevel 1 Lower Entry/Exit Plane:\nENTRY\nAssociate the Rule with the Branches required. Select the Branch 2001/B1 on the Routing Rules window. Select Settings > Branch Rules from the menu on the AVEVA E3D\u2122 Router window. On the Branch Rules window, set Apply rule sets to All Selected Branches. Select HIGH, and the rule is added to the window.\nNow re-route the Pipe. A more satisfactory route is obtained.\nDeleting a Rule World, Rule Set or Routing Rule\nTo delete a rule world, rule set, or routing rule, navigate to the rule world and rule set to be deleted from the Current Rule World and Current Rule Set drop-down lists. Select the rule to be deleted from the routing rules list. Select Delete > Rule World, Delete > Rule Set or Delete > Rule, as required.\nPlacing Pipes on Racks and Planes\nThe section describes how to set up rules which control:\nFlanges on Routing Planes\nBy default, Pipe Router runs pipes along Routing planes with the wall-to-wall Pipe Gap given on the Pipe Router Defaults window. Refer to for further information.\nIf you need to run sections of Pipes which include Flanges along routing planes, you can specify that the gap value is applied as a wall-to-flange (WF) gap, if the flanges can be staggered, or as a flange-to-flange (FF) gap, if the flanges are side-by-side on the plane. The default is wall-to-wall (WW) spacing. The spacing is controlled by the PLWW attribute of the RPLA. PLWW can be set to WW, WF or FF.\nIf WW or WF spacing is specified, the Pipe Router looks for rules of type FLWI and apply them. The size of flange is found using the Flange Width (FLWI) rule, which is applied to the default flange (for example, the flange which is obtained with an AVEVA E3D\u2122 SELECT) for each branch at its current bore, even if there are other flanges on the pipe rack.\nThe flange width taken as 0 if:\nIf necessary, specify an additional pipe-specific gap, for example, for very hot pipes.\nExample of Wall-to-Flange Spacing\nIf a rule is used, so that the flange width is set to 1.5 x bore, then wall-to-flange spacing is calculated:\nThe constant gap is set to 50mm. Then the center of an insulated branch of OD 200mm, bore 100mm would be placed 435mm from the center of an adjacent branch of OD 150mm, bore 140mm.\n\nExample of Flange-to-Flange Spacing\nIf the rule sets the flange width to 1.5 x bore, then flange-to-flange spacing is calculated:\n\u00bd OD Pipe A\n100\nFlange width Pipe A\n150\nGap\n50\nFlange width Pipe B\n210\n\u00bd OD Pipe B\n75\nTotal\n585\n\u00bd OD Pipe A\n100\nFlange width Pipe A\n150\nGap\n50\nFlange width Pipe B\n210\n\u00bd OD Pipe B\n75\nTotal\n585\n\nPacking Methods\nThere are two packing methods available. Pipe Router either places a pipe on a plane as near as possible to the edge of the plane, or packs heavy pipes at the edges of racks and light ones at the center. The packing method is an attribute of the Routing Plane. It can be set for the Travel Plane of pipe-racks and for individual planes.\nSelect the By Weight method, the PLPM (Plane Packing Method) attribute of the plane is set to WEIG, and Pipe Router looks for a weight rule, (PURP set to WEIG), to determine whether pipes are light or heavy.\nYou can use weight rules to determine whether pipes are packed at the top or bottom of vertical planes\nHorizontal Routing Planes\nIn the weight-related packing method on horizontal planes, for heavy pipes Pipe Router searches inwards from both edges looking for a free slot with a large enough gap between it and any adjacent pipe. The heavy pipe is placed closest to whichever edge a slot is found. For light pipes Router first looks in the middle of the plane or rack to see if this slot is free. Router then searches in both directions outwards looking for a free slot and use the closer to the center. Pipes for which no rule exists are treated as light pipes and placed in the center of the rack or plane.\nVertical Routing Planes\nThe weight-related packing method can also be applied to vertical routing planes with a horizontal travel direction. If the weight-related packing method is used then, for light pipes, Pipe Router searches downwards from the top edge of the routing plane edges looking for a free slot with a large enough gap between it and any adjacent pipe. For heavy pipes Pipe Router searches upwards from the bottom edge of the plane. Pipes for which no rule exists are treated as light pipes.\nExample of Weight-related Packing\nIf the third and sixth pipes to be packed on a rack are \u2018heavy\u2019 and the others are lig"}
{"Headers": "Pipe Fabrication", "Content": "Modelling\nSpooling and Checks\nDrawings\nExport Fabrication Data\nConfiguration.\nModelling\nModelling\nSpooling and Checks\nSpooling and Checks\nDrawings\nDrawings\nExport Fabrication Data\nExport Fabrication Data\nConfiguration.\nConfiguration.\n\n\n\nModelling\nSpooling and Checks\nDrawings\nExport Fabrication Data\nConfiguration\nModelling\nSpooling and Checks\nDrawings\nExport Fabrication Data\nConfiguration"}
{"Headers": "Modelling", "Content": "At the model stage, fabrication related features are defined, such as fabricated pipe ends, assignment of bending machines and design checks for fabrication. Additional catalog components are also provided as part of Pipe Fabrication.\nAssign Bending Machine\nA default Bending Machine Reference can be defined for a pipe specification and a Bending Machine Reference in the pipe structure can be modified.\nDefault Bending Machine Reference in Pipe Specification\nTo specify a default bending machine reference to each pipe specification using AVEVA Catalogue.\nWhenever a pipe is created, the BendMacReference attribute is populated with the default value assigned to the piping specification. By default, the BendMacReference attribute is assigned with a valid default bending machine reference from the pipe specification.\n\nModify Bending Machine Reference in Pipe Models\nIf a pipe bend Radius is too large and needs to be changed to a smaller bend radius for design reasons, then the BendMacReference attribute for the zone, pipe or branch can be modified to point to another Fabrication Machine World (FMWL), Group (FMGRP) or Machine (FMBEND).\n\nClick CE to identify the currently selected SITE, ZONE, PIPE or BRAN as the currently selected element.\nThe list of elements displays the Name, element type and BendMacReference attribute value of each element in the selected pipe structure. The user can select one or more elements to modify.\n\nSelect the Highlight selected elements check box to highlight the selected table item in the 3D graphical view.\nThe Assign Bending Machine part of the Assign Bending Machine window allows the user to assign a new bending machine and modify the bend radius of the selected element.\n\nAssign Bending Machine\nSelect an FMWLD, FMGRP or FMBEND from the drop-down list to assign a BendMacReference attribute value to the selected element.\nModify Bend Radius\nSelect the check box to modify the bend radius of the selected element by default. Refer to for further information.\nTidy\nSelect the check box to tidy the BendMacReference attribute value of the selected element by default. Refer to for further information.\nAssign Bending Machine\nSelect an FMWLD, FMGRP or FMBEND from the drop-down list to assign a BendMacReference attribute value to the selected element.\nModify Bend Radius\nSelect the check box to modify the bend radius of the selected element by default. Refer to for further information.\nTidy\nSelect the check box to tidy the BendMacReference attribute value of the selected element by default. Refer to for further information.\nClick Apply to assign a new BendMacReference modify the bend radius of the selected element.\nModify Bend Radius\nIf the Modify Bend radius check box is selected, the bend radius of the selected element is modified by default.\nThe example below shows the modified bend radius as part of a pipe structure.\n\nTidy BendMacReference Element\nIf the Tidy check box is selected, the BendMacReference attribute value of the selected element is tidied by default. If the BendMacReference attribute value of a branch is the same value as the owning pipe, the attribute value is removed from the branch.\nThe example below shows a pipe and branch with a duplicate BendMacReference attribute value.\n\nWhen the Tidy check box is selected, the BendMacReference attribute value is removed from the branch.\nDetails\nThe Details tab displays a list of change details for the pipework structure, calculated when the bending machine is assigned.\nErrors\nThe Errors tab displays a list of errors for the pipework structure, calculated when the bending machine is assigned.\nBending Error Types\nThere are three different error types that can be checked for:\nFabricated Pipe Ends\nThe Fabricated Pipe Ends window defines a plain, slanted or threaded pipe end.\n\n\n\n\n\n\nCreate Sniped Ends\nSpecify the angle for the Plain and display a Drawing Note.\nBy default, the slated angle is 0 which means it is a plain end.\nIf required, enter a statement in the Drawing Note field, the default is Plain End, the note is displayed on the drawing.\nClick Create Sniped Ends, select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe Plain fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nSpecify the angle for the Sniped End and display a Drawing Note.\nEnter a value (greater than 0) in the Slanted Angle field to define the angle of the Slanted End in degrees.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}, the note is displayed on the drawing.\nNote:\n{deg} is replaced by the value of the Slanted Angle value in the drawing.\nClick Create Sniped Ends. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe sniped fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nCreate Sniped Ends with Reference Plane\nCreates a slanted end by referencing a plane.\nEnter a value (greater than 0) in the Sniped Angle field to define the angle of the Sniped End in degrees.\nEnter a dimensional value in the Clearance field to define the reference plane clearance.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}. The note displays on the drawing.\nNote:\n{deg} is replaced by the value of the Sniped Angle value in the drawing.\nClick Create Sniped Ends with Reference Plane.\nThe prompt \u2018Pick pipe end:\u2019, is displayed then \u2018Pick plane:\u2019\nThe plane is used as the pipe end cutting standard in the 3D graphical view.\nThe Slated fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nCreate Thread End\nDefines a threaded end for a fabricated pipe end.\nClick Create Threaded End. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nSelect a Threaded Type from the Thread Type drop-down list.\nThe user can configure the Thread Type, refer to for further information.\nThe Threaded End consists of four attributes:\nConnection\nDescription\nBore of Picked Tube\nThread Length\nThe Thread information is shown on the drawing.\nIf a tube has thread information, the build length value starts with '*' as prefix.\nThe assembly table contains the thread information.\nRemove Fabricated End\nDeletes the Fabricated End (Sniped or Threaded). The user must select a pipe end in the 3D graphical view.\nDisplay Fabricated End\nDisplays information for the created Fabricated End.\n\nCreate Sniped Ends\n\nSpecify the angle for the Plain and display a Drawing Note.\n\nBy default, the slated angle is 0 which means it is a plain end.\nIf required, enter a statement in the Drawing Note field, the default is Plain End, the note is displayed on the drawing.\nClick Create Sniped Ends, select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe Plain fabricated end is added to the pipe and the orientation of the pipe end is displayed.\n\nSpecify the angle for the Sniped End and display a Drawing Note.\n\n\n\nEnter a value (greater than 0) in the Slanted Angle field to define the angle of the Slanted End in degrees.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}, the note is displayed on the drawing.\nClick Create Sniped Ends. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe sniped fabricated end is added to the pipe and the orientation of the pipe end is displayed.\n\nCreate Sniped Ends with Reference Plane\nCreates a slanted end by referencing a plane.\nEnter a value (greater than 0) in the Sniped Angle field to define the angle of the Sniped End in degrees.\nEnter a dimensional value in the Clearance field to define the reference plane clearance.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}. The note displays on the drawing.\nClick Create Sniped Ends with Reference Plane.\nThe prompt \u2018Pick pipe end:\u2019, is displayed then \u2018Pick plane:\u2019\nThe plane is used as the pipe end cutting standard in the 3D graphical view.\nThe Slated fabricated end is added to the pipe and the orientation of the pipe end is displayed.\n\nCreate Thread End\nDefines a threaded end for a fabricated pipe end.\nClick Create Threaded End. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\n\nSelect a Threaded Type from the Thread Type drop-down list.\nThe user can configure the Thread Type, refer to for further information.\nThe Threaded End consists of four attributes:\nThe Thread information is shown on the drawing.\nIf a tube has thread information, the build length value starts with '*' as prefix.\n\n\n\nThe assembly table contains the thread information.\n\n\nRemove Fabricated End\nDeletes the Fabricated End (Sniped or Threaded). The user must select a pipe end in the 3D graphical view.\n\nDisplay Fabricated End\nDisplays information for the created Fabricated End.\nModelling Consistency Checks\nPipes that are still being designed can be checked for fabrication readiness. Some of the checks require configurable dimensions or minimum distances. By default, the window is now populated with the details of the CE.\n\nTo add pipes to be checked, in the Model Explorer click to select the required pipe. Then select Add CE, the CE is displayed in the Modelling Consistency Check window.\nTo highlight the pipe to be checked in the 3D graphical view, click to select the Highlight selected elements check box. By default the check box is not selected.\nTo run modelling consistency checks, click Check, a short description (pass or fail) of the check is displayed on the Results tab.\n\nOn the CE tab, a more detailed description of the modelling consistency checks are displayed.\n\nOn the Options tab, all of the modelling consistency checks are displayed, by default all the checks are selected.\n\nAssign Bending Machine\nSelect an FMWLD, FMGRP or FMBEND from the drop-down list to assign a BendMacReference attribute value to the selected element.\nModify Bend Radius\nSelect the check box to modify the bend radius of the selected element by default. Refer to for further information.\nTidy\nSelect the check box to tidy the BendMacReference attribute value of the selected element by default. Refer to for further information.\nCreate Sniped Ends\nSpecify the angle for the Plain and display a Drawing Note.\nBy default, the slated angle is 0 which means it is a plain end.\nIf required, enter a statement in the Drawing Note field, the default is Plain End, the note is displayed on the drawing.\nClick Create Sniped Ends, select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe Plain fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nSpecify the angle for the Sniped End and display a Drawing Note.\nEnter a value (greater than 0) in the Slanted Angle field to define the angle of the Slanted End in degrees.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}, the note is displayed on the drawing.\nNote:\n{deg} is replaced by the value of the Slanted Angle value in the drawing.\nClick Create Sniped Ends. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nThe sniped fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nCreate Sniped Ends with Reference Plane\nCreates a slanted end by referencing a plane.\nEnter a value (greater than 0) in the Sniped Angle field to define the angle of the Sniped End in degrees.\nEnter a dimensional value in the Clearance field to define the reference plane clearance.\nIf required, enter a statement in the Drawing Note field, the default is Trim pipe end to {deg}. The note displays on the drawing.\nNote:\n{deg} is replaced by the value of the Sniped Angle value in the drawing.\nClick Create Sniped Ends with Reference Plane.\nThe prompt \u2018Pick pipe end:\u2019, is displayed then \u2018Pick plane:\u2019\nThe plane is used as the pipe end cutting standard in the 3D graphical view.\nThe Slated fabricated end is added to the pipe and the orientation of the pipe end is displayed.\nCreate Thread End\nDefines a threaded end for a fabricated pipe end.\nClick Create Threaded End. The user must select a pipe end in the 3D graphical view.\nThe prompt \u2018Pick pipe end:\u2019 is displayed.\nSelect a Threaded Type from the Thread Type drop-down list.\nThe user can configure the Thread Type, refer to for further information.\nThe Threaded End consists of four attributes:\nConnection\nDescription\nBore of Picked Tube\nThread Length\nThe Thread information is shown on the drawing.\nIf a tube has thread information, the build length value starts with '*' as prefix.\nThe assembly table contains the thread information.\nRemove Fabricated End\nDeletes the Fabricated End (Sniped or Threaded). The user must select a pipe end in the 3D graphical view.\nDisplay Fabricated End\nDisplays information for the created Fabricated End.\nNot enough tube length before/after bend.\nThere is not enough straight tube length before or after a bend to change the bend radius. An instance can occur when changing a bending machine reference that uses a larger radius value.\nThe example below shows the effect of enlarging a bend radius on a tube.\nBending machine cannot handle the outside diameter\nThe new bending machine reference does not have a suitable bending dimension for the outside diameter of the target pipe.\nBendMacReference is not defined.\nThe BendMacReference attribute value is not defined for any of BRAN, PIPE and ZONE elements in the pipework structure.\nNot enough tube length before/after bend.\nThere is not enough straight tube length before or after a bend to change the bend radius. An instance can occur when changing a bending machine reference that uses a larger radius value.\nThe example below shows the effect of enlarging a bend radius on a tube.\nNot enough tube length before/after bend.\nBending machine cannot handle the outside diameter\nThe new bending machine reference does not have a suitable bending dimension for the outside diameter of the target pipe.\nBending machine cannot handle the outside diameter\nBendMacReference is not defined.\nThe BendMacReference attribute value is not defined for any of BRAN, PIPE and ZONE elements in the pipework structure.\nBendMacReference is not defined.\nConnection\nDescription\nBore of Picked Tube\nThread Length\nConnection\nConnection\nDescription\nDescription\nBore of Picked Tube\nBore of Picked Tube\nThread Length\nThread Length\nNote:\n{deg} is replaced by the value of the Slanted Angle value in the drawing.\nNote:\n{deg} is replaced by the value of the Sniped Angle value in the drawing.\n\n\n\nAssign Bending Machine\nDefault Bending Machine Reference in Pipe Specification\nBendMacReference\nBendMacReference\nModify Bending Machine Reference in Pipe Models\nBendMacReference\nCE\nHighlight selected elements\nAssign Bending Machine\nAssign Bending Machine\nFMWLD\nFMGRP\nFMBEND\nBendMacReference\n\nBendMacReference\n\nApply\nModify Bend Radius\nModify Bend radius\nTidy BendMacReference Element\nTidy\nBendMacReference\nBendMacReference\nBendMacReference\nTidy\nBendMacReference\nDetails\nDetails\nErrors\nErrors\nBending Error Types\nBendMacReference\nFabricated Pipe Ends\nFabricated Pipe Ends\n\n\n\n\n\nCreate Sniped Ends\nDrawing Note\nCreate Sniped Ends\nPick pipe end:\nSniped End\nSlanted Angle\nDrawing Note\nNote\n:\nSlanted Angle\nCreate Sniped Ends\nPick pipe end:\nCreate Sniped Ends with Reference Plane\nSniped Angle\nClearance\nNote\n:\nSniped Angle\nCreate Sniped Ends with Reference Plane\nPick pipe end:\nPick plane:\nCreate Thread End\nCreate Threaded End\nPick pipe end:\nThread Type\n\nRemove Fabricated End\nDisplay Fabricated End\nModelling Consistency Checks\nModel Explorer\nAdd CE\nModelling Consistency Check\nHighlight selected elements\nCheck\nResults\nCE\nOptions"}
{"Headers": "Spooling and Checks", "Content": "Pipe spool generation makes sure that all pipes spools include the necessary adjustments to be suitable for production in an automatic and configurable manner. The following must be considered:\nProduction Checks\n\n\n\n\n\nWeld Handling\nUse the Weld Handling window to create, modify, and delete welds in the currently selected spool. Also use the window, to view welds which could not be created.\n\n\n\n\nCreate Weld\nClick CE to identify the currently selected element as the working element. Use the Create part of the Weld Handling window to create and define a weld.\n\nSpec.\nSelect Spec to create a weld from the current pipe spec. The weld thickness is pre-defined by the spec.\nConfig.\nSelect Config to create a weld from a common weld spec. The weld thickness can be modified according to the design circumstance. Refer to for further information.\nZero Gap\nSelect to define a weld thickness of 0.\nFabrication Type\nSelect Manual, Machine, or Orbital, then Shop, Site or Field.\nCreate Welds on CE\nCreates a weld for the selected pipe with specific options for Fitting to Fitting Connection and Slip-On Flanges. Refer to for further information.\nCreate Welds by Picking\nCreates a weld by picking the specific element in the 3D graphical view.\nAppend Weld Number\nSelect the check box, the next available weld number is assigned to the current weld, by default.\nLeave the check box unchecked to assign the weld number manually.\nNote:\nThe weld number is a unique value. Duplicate weld numbers are highlighted by application.\n\nSpec.\nSelect Spec to create a weld from the current pipe spec. The weld thickness is pre-defined by the spec.\n\nConfig.\nSelect Config to create a weld from a common weld spec. The weld thickness can be modified according to the design circumstance. Refer to for further information.\n\nZero Gap\nSelect to define a weld thickness of 0.\n\nFabrication Type\nSelect Manual, Machine, or Orbital, then Shop, Site or Field.\n\nCreate Welds on CE\nCreates a weld for the selected pipe with specific options for Fitting to Fitting Connection and Slip-On Flanges. Refer to for further information.\n\nCreate Welds by Picking\nCreates a weld by picking the specific element in the 3D graphical view.\n\nAppend Weld Number\nSelect the check box, the next available weld number is assigned to the current weld, by default.\nLeave the check box unchecked to assign the weld number manually.\nModify and Delete Welds\nUse the Modify part of the Weld Handling window to modify and delete the currently selected weld.\n\nThe weld list displays weld information for the welds that can be modified.\nName\nName of the weld.\nWeld Type\nDisplays the weld type.\nFab. Type\nDisplays the weld fabrication type.\nSpool Limit\nDisplays the weld spool limit status.\nNumber\nDisplays the weld number.\nModify the properties of the Weld set in the 3D graphical view (Shop, Type).\nRefreshes the weld list.\nDeletes all welds in the weld list, a window displays asking you to confirm the deletion.\nBy default the Include Spool Limits check box is selected, allowing you to Include Spool Limits within the deletion.\nNote:\nIf the weld list only contains Spool Limit Welds and the delete button is pressed, the toggle is automatically set to true.\nDeletes all welds in the weld list, a window displays asking you to confirm the deletion.\nBy default the Include Spool Limits check box is selected, allowing you to Include Spool Limits within the deletion.\nNote:\nIf the weld list only contains Spool Limit Welds and the delete button is pressed, the toggle is automatically set to true.\nExport Weld List\nExports the weld list in an excel format to another location.\nZoom when selected\nSelect the check box to zoom to the weld information for the selected weld in the 3D graphical view.\nHighlight Elements\nSelect the check box to highlight the selected weld in the 3D graphical view.\nMark Weld Info.\nSelect the check box to display the weld information for the selected weld in the 3D graphical view.\nName\nName of the weld.\nWeld Type\nDisplays the weld type.\nFab. Type\nDisplays the weld fabrication type.\nSpool Limit\nDisplays the weld spool limit status.\nNumber\nDisplays the weld number.\n\nModify the properties of the Weld set in the 3D graphical view (Shop, Type).\n\nRefreshes the weld list.\n\nDeletes all welds in the weld list, a window displays asking you to confirm the deletion.\n\nBy default the Include Spool Limits check box is selected, allowing you to Include Spool Limits within the deletion.\n\nDeletes all welds in the weld list, a window displays asking you to confirm the deletion.\n\nBy default the Include Spool Limits check box is selected, allowing you to Include Spool Limits within the deletion.\nExport Weld List\nExports the weld list in an excel format to another location.\nZoom when selected\nSelect the check box to zoom to the weld information for the selected weld in the 3D graphical view.\nHighlight Elements\nSelect the check box to highlight the selected weld in the 3D graphical view.\nMark Weld Info.\nSelect the check box to display the weld information for the selected weld in the 3D graphical view.\nError tab\nWhen welds cannot be created between components, the name and description of the error populates the Error tab of the Weld Handling window.\n\nModify Spool\nUse the Modify Spool window to define pipe end & feed excess, loose components, spool limits, machine insertion direction and create multiple spools.\n\n\n\n\n\n\n\nUser End & Feed Excess\nUse the User End & Feed Excess part of the Modify Spool window to display and modify the end and feed excess values.\nEnd Excess - adds a surplus to the end of pipe pieces during production.\nFeed Excess - adds a surplus during the feeding of the pipe piece through the bending machine during production.\n\nShow User End Excesses\nDisplays or hides the end excess values in the 3D graphical view.\nSet User End Excess\nView or modify the end excess by picking a tube element on the 3D graphical view.\nShow User Feed Excess\nDisplays or hides the feed excess values in the 3D graphical view.\nSet User Feed Excess\nView or modify the feed excess by picking a tube element on the 3D graphical view.\nShow User End Excesses\nDisplays or hides the end excess values in the 3D graphical view.\n\nSet User End Excess\nView or modify the end excess by picking a tube element on the 3D graphical view.\n\nShow User Feed Excess\nDisplays or hides the feed excess values in the 3D graphical view.\nSet User Feed Excess\nView or modify the feed excess by picking a tube element on the 3D graphical view.\n\nComponents Attributes\nUse the Component Attributes part of the Modify Spool window to display and modify the component attributes.\n\nShow Loose Component\nDisplays or hides the loose component value in the 3D graphical view\nModify Component Attributes\nClick to display the Component Attributes window. Refer to for further information.\nShow Loose Component\nDisplays or hides the loose component value in the 3D graphical view\nModify Component Attributes\nClick to display the Component Attributes window. Refer to for further information.\n\nModify Component Attributes\nUse the Component Attributes window to define the attributes for piping components.\n\nDisplays the attribute settings for the previous piping component.\nDisplays the attribute settings for the next piping component.\nLoose Component\nSelect the check box to specify the piping component as a Loose Component.\nApply Default Loose Excess (200.00mm)\nThe check box becomes active when the user selects the Loose Component check box, the Offline Component check box must be left unchecked and the component must be positioned at the end of a spool.\nSelect the check box to define a Default Loose Excess of 200mm for the piping component.\nOffline Component\nSelect the check box to specify the piping component as an Offline Component.\nShop Fabrication Material\nSelect the check box to specify the piping component as a Shop Fabrication Material component.\n\nDisplays the attribute settings for the previous piping component.\n\nDisplays the attribute settings for the next piping component.\nLoose Component\nSelect the check box to specify the piping component as a Loose Component.\nApply Default Loose Excess (200.00mm)\nThe check box becomes active when the user selects the Loose Component check box, the Offline Component check box must be left unchecked and the component must be positioned at the end of a spool.\nSelect the check box to define a Default Loose Excess of 200mm for the piping component.\nOffline Component\nSelect the check box to specify the piping component as an Offline Component.\nShop Fabrication Material\nSelect the check box to specify the piping component as a Shop Fabrication Material component.\nSpool Limits\nUse the Spool Limits part of the Modify Spool window to display and modify the spool limits. A spool limit can be added or deleted. The spool limit is created with a field WELD component.\n\nShow Spool Limits\nDisplays the spool limits (welds) for the currently selected pipe on the 3D graphical view.\nHide Spool Limits\nHides the spool limits (welds) for the currently selected pipe on the 3D graphical view.\nAdd/Remove Spool Limit - No Welds/Welds\nCreate a spool limit for a component using a cursor pick on the 3D graphical view.\nPick first component or <ESC> to finish : on the 3D graphical view\nPossible spool limit positions are displayed as a square without fill, existing spool limits are displayed as a filled square.\nPick a second component adjacent to the first component. The second component is used to decide the exact position for a new spool limit.\nA Confirm window displays asking OK to add?, click Yes to add a new spool limit.\nIf the Add/Remove Spool Limits - No Welds is selected the weld is not displayed on the 3D graphical view.\nAdd/Remove Spool Limit - No Welds/Welds\nRemove a spool limit for a component using a cursor pick on the 3D graphical view.\nPick first component or <ESC> to finish : on the 3D graphical view\nPick a second component, a Confirm window is displayed asking OK to remove, click Yes to remove the spool limit.\nIf the spool limit location on the currently selected pipe already has a spool limit created without a field WELD component and Add/Remove Spool Limit - Welds is selected, the following Confirm window is displayed:\nClick Yes to replace the spool limit - without a weld component with a weld.\nShow Spool Limits\nDisplays the spool limits (welds) for the currently selected pipe on the 3D graphical view.\n\nHide Spool Limits\nHides the spool limits (welds) for the currently selected pipe on the 3D graphical view.\n\nAdd/Remove Spool Limit - No Welds/Welds\nCreate a spool limit for a component using a cursor pick on the 3D graphical view.\nPick first component or <ESC> to finish : on the 3D graphical view\nPossible spool limit positions are displayed as a square without fill, existing spool limits are displayed as a filled square.\n\n\nPick a second component adjacent to the first component. The second component is used to decide the exact position for a new spool limit.\nA Confirm window displays asking OK to add?, click Yes to add a new spool limit.\n\n\nIf the Add/Remove Spool Limits - No Welds is selected the weld is not displayed on the 3D graphical view.\n\n\nAdd/Remove Spool Limit - No Welds/Welds\nRemove a spool limit for a component using a cursor pick on the 3D graphical view.\nPick first component or <ESC> to finish : on the 3D graphical view\n\n\n\n\nPick a second component, a Confirm window is displayed asking OK to remove, click Yes to remove the spool limit.\n\n\n\nIf the spool limit location on the currently selected pipe already has a spool limit created without a field WELD component and Add/Remove Spool Limit - Welds is selected, the following Confirm window is displayed:\n\n\n\nClick Yes to replace the spool limit - without a weld component with a weld.\nMachine Insertion Direction\nUse the Set Machine Insertion Direction part of the Modify Spool window to define the bending direction for the spool.\n\nArrive\nSelect the radio button and specify the Arrive to define the spool arrive end as the machine insertion direction.\nLeave\nSelect the radio button and specify the Leave to define the spool leave end as the machine insertion direction.\nAuto\nBy default, the bending direction is assigned after the bending check algorithm has checked and optimized both directions.\nArrive\nSelect the radio button and specify the Arrive to define the spool arrive end as the machine insertion direction.\nLeave\nSelect the radio button and specify the Leave to define the spool leave end as the machine insertion direction.\nAuto\nBy default, the bending direction is assigned after the bending check algorithm has checked and optimized both directions.\nMultiple Spools\nUse the Create Multiple Spool part of the Modify Spool window to define a Spool Drawing (SPLDRG) element.\n\nThe Fabrication Explorer is automatically displayed, SPLDRG elements can be viewed in the Fabrication Explorer.\n\nUse the Modify Spool window to create a multiple spool.\n\nCreates the currently selected Department (ISODEP), Registry (ISOREG) or Spool Drawing (SPLDRG) element.\nDepartment\nSelect from the drop-down list to create a Department element. Enter a Department Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\nRegistry\nSelect from the drop-down list to create a Registry element. Enter a Registry Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\nSpool Drawing\nSelect from the drop-down list to create a Spool Drawing element. Enter a Spool Drawing Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\nAdds a spool to a spool drawing by picking the spool on the 3D graphical view.\nRemoves a spool from a spool drawing by picking the spool on the 3D graphical view.\nInclude field components into the Spool drawing.\nUpdate Part Number\nCreates Fabrication or Installation Isometrics.\nSearch Within\nSearch within the pipe, branch, zone, site or world.\n\nCreates the currently selected Department (ISODEP), Registry (ISOREG) or Spool Drawing (SPLDRG) element.\nDepartment\nSelect from the drop-down list to create a Department element. Enter a Department Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\nRegistry\nSelect from the drop-down list to create a Registry element. Enter a Registry Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\nSpool Drawing\nSelect from the drop-down list to create a Spool Drawing element. Enter a Spool Drawing Name in the field to the right of the drop-down list, the element displays in the Fabrication Explorer.\n\nAdds a spool to a spool drawing by picking the spool on the 3D graphical view.\n\nRemoves a spool from a spool drawing by picking the spool on the 3D graphical view.\n\nInclude field components into the Spool drawing.\nUpdate Part Number\nCreates Fabrication or Installation Isometrics.\nSearch Within\nSearch within the pipe, branch, zone, site or world.\nUse the bottom part of the Modify Spool window to define the links with Fabrication Checks and Weld Handling. Functionality is also available to clear all Aid Texts on the 3D graphical view.\n\nFabrication Checks\nClick to display the Fabrication Check window. Refer to for further information\nWeld Handling\nClick to display the Weld Handling window. Refer to for further information\nClear All\nRemoves all Aid Texts on the 3D graphical view.\nFabrication Checks\nClick to display the Fabrication Check window. Refer to for further information\nWeld Handling\nClick to display the Weld Handling window. Refer to for further information\nClear All\nRemoves all Aid Texts on the 3D graphical view.\nAdd Spool Attributes\nUse the Spool Attributes window to modify the spool name and other attributes. Functionality is also available to add a new attribute column to the list of available columns.\n\nCE\nIdentifies the currently selected element as the working element. The list of spool attributes is populated with all spools under the current element.\nExport\nExports the spool data to an excel file.\nHighlight when selected\nSelect the check box to highlight the selected spool in the 3D graphical view.\nCE\nIdentifies the currently selected element as the working element. The list of spool attributes is populated with all spools under the current element.\nExport\nExports the spool data to an excel file.\nHighlight when selected\nSelect the check box to highlight the selected spool in the 3D graphical view.\nAdd new columns using the ppGetColumnsForSpool.pmlfnc file, located in the pmlfnc folder. The following example describes how to add a new attribute column, called Paint, to the list of spool attributes.\nOpen the ppGetColumnsForSpool.pmlfnc file, the highlighted text in the example below displays the text required to be added to the file.\n\nReload the Spool Attributes window to the application using the Command Window, enter pml reload form !!pfSpoolAttributes.\nAdd new drop-down value list using the ppGetColumnsForSpool.pmlfnc file, located in the pmlfnc folder. The following example describes how to add a value list to the Paint attribute column.\nOpen the ppGetColumnsForSpool.pmlfnc file, the text in the example below displays the text required to be added to the file.\n\nReload the Spool Attributes window to the application using the Command Window, enter pml reload form !!pfSpoolAttributes.\nAlternatively, add a new drop-down value list using the ppGetColumnsForSpool.pmlfnc and pfGetValueListForSpool.pmlfnc files.\nOpen the ppGetColumnsForSpool.pmlfnc file, the highlighted text in the example below displays the text required to be added to the file.\n\nOpen the pfGetValueListForSpool.pmlfnc file, the highlighted text in the example below displays the text required to be added to the file.\n\nFabrication Check\nUse the Fabrication Check window to check pipe models for production readiness. Make sure a SITE or ZONE element is selected as the CE in the design hierarchy.\n\n\nAdd CE\nIdentifies the currently selected element as the working element. The list of available pipes is populated with all pipes under the current element.\nValidate\nValidates the current selection for production readiness. After validation, all errors and production information displays in the Check Results and the Details tabs.\nAfter validation, the pipe status is set to ready for production if there are no errors.\nRelease\nSets the pipe status to ready for production, regardless of outstanding production errors.\nAdd CE\nIdentifies the currently selected element as the working element. The list of available pipes is populated with all pipes under the current element.\nValidate\nValidates the current selection for production readiness. After validation, all errors and production information displays in the Check Results and the Details tabs.\nAfter validation, the pipe status is set to ready for production if there are no errors.\nRelease\nSets the pipe status to ready for production, regardless of outstanding production errors.\n\nZoom when selected\nSelect the check box to display the currently selected element in the 3D graphical view.\nModify Spool\nClick to display the Modify Spool window. Refer to for further information.\nWeld Handling\nClick to display the Weld Handling window. Refer to for further information.\nSelect Default Fabrication Machines\nClick to display the Default Fabrication Machines part Fabrication Check window. Refer to for further information.\nZoom when selected\nSelect the check box to display the currently selected element in the 3D graphical view.\nModify Spool\nClick to display the Modify Spool window. Refer to for further information.\nWeld Handling\nClick to display the Weld Handling window. Refer to for further information.\nSelect Default Fabrication Machines\nClick to display the Default Fabrication Machines part Fabrication Check window. Refer to for further information.\nUse the pipe status part of the fabrication check window to view the list of pipes contained within the currently selected site or zone element together with the fabrication status and if the pipe has passed the consistency check.\n\nRight-click on the Pipe part of the Fabrication Check window to display a pop-up menu of available options associated with the selection.\n\nValidate Pipes\nRuns the fabrication checks against the currently selected pipes and displays the result.\nSpools and pieces are generated after validation if there are no outstanding errors.\nValidate Pipes With\nUse the Select Fabrication Machines window to view the default bending machines available for selection.\nSet to Manually Bent\nAll pipe pieces containing bends in the selected pipe are set to manually bent.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks. Refer to for further information.\nRelease\nGenerates spool and piece elements for the currently selected pipes, the status is set to Ready for fabrication regardless of outstanding warnings.\nDelete Spool Information\nDeletes fabrication information for all pipe spools and pipe pieces in the currently selected pipes.\nAdd CE\nAdds all pipes under the CE element to the pipe list.\nRemove Selected\nRemoves the currently selected pipes from the pipe list.\nRemove All\nRemoves all pipes from the pipe list.\nSelect All\nSelects all pipes in the list of available pipes.\nUnselect All\nDeselects all pipes in the list of available pipes.\nAdd to 3D View\nAdds the selected pipes to the 3D graphical view.\nRemove from 3D View\nRemoves the selected pipes from the 3D graphical view.\nOptimization Priorities\nDisplays the Optimization Priorities window, use it to order the optimization priorities for the fabrication check. The modified priorities are temporary and is invalid after closing the Fabrication Check window. The functionality of the Optimization Priorities window is explained as part of the process for defining Optimization Criteria for Bending and Welding. Refer to for further information.\nZoom To\nDisplays the currently selected pipes in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe in the Design Explorer.\nValidate Pipes\nRuns the fabrication checks against the currently selected pipes and displays the result.\nSpools and pieces are generated after validation if there are no outstanding errors.\nValidate Pipes With\nUse the Select Fabrication Machines window to view the default bending machines available for selection.\nSet to Manually Bent\nAll pipe pieces containing bends in the selected pipe are set to manually bent.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks. Refer to for further information.\nRelease\nGenerates spool and piece elements for the currently selected pipes, the status is set to Ready for fabrication regardless of outstanding warnings.\nDelete Spool Information\nDeletes fabrication information for all pipe spools and pipe pieces in the currently selected pipes.\nAdd CE\nAdds all pipes under the CE element to the pipe list.\nRemove Selected\nRemoves the currently selected pipes from the pipe list.\nRemove All\nRemoves all pipes from the pipe list.\nSelect All\nSelects all pipes in the list of available pipes.\nUnselect All\nDeselects all pipes in the list of available pipes.\nAdd to 3D View\nAdds the selected pipes to the 3D graphical view.\nRemove from 3D View\nRemoves the selected pipes from the 3D graphical view.\nOptimization Priorities\nDisplays the Optimization Priorities window, use it to order the optimization priorities for the fabrication check. The modified priorities are temporary and is invalid after closing the Fabrication Check window. The functionality of the Optimization Priorities window is explained as part of the process for defining Optimization Criteria for Bending and Welding. Refer to for further information.\nZoom To\nDisplays the currently selected pipes in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe in the Design Explorer.\nUse the Spool part of the Fabrication Check window, to view the list of pipe spools contained within the CE, together with the fabrication status and spool type.\n\nRight-click on the Spool part of the Fabrication Check window to display a pop-up menu of available options associated with the selection.\n\nValidate Spools\nRuns the fabrication checks against the currently selected spools.\nValidate Spools With\nUse the Select Fabrication Machines window to view the default fabrication machines available for selection.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSet to Manually Bent\nAll pipe pieces containing bends in the selected pipe spool are set to manually bent.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks.\nRefer to for further information.\nRelease\nGenerates spool and piece elements for the currently selected spools, sets the status to Ready for fabrication regardless of outstanding warnings.\nDelete Spool Information\nDeletes fabrication information for all pipe spools and pipe pieces in the currently selected spools.\nModify Name\nUse the Rename Element window to rename individual spools.\nRename Spools\nRenames the currently selected spools by using auto-naming rules. If auto-naming is turned off, the menu is disabled.\nRename All Spools\nRenames all spools in the spool list by using auto-naming rules. If auto-naming is turned off, the menu is disabled.\nChange Spool Type\nSets the spool type of selected pipe spool, SHOP, FITT or SITE.\nZoom To\nDisplays the currently selected pipe spool in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe spool in the Design Explorer.\nHighlight\nHighlights the last selected pipe spool in the 3D graphical view.\nValidate Spools\nRuns the fabrication checks against the currently selected spools.\nValidate Spools With\nUse the Select Fabrication Machines window to view the default fabrication machines available for selection.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSet to Manually Bent\nAll pipe pieces containing bends in the selected pipe spool are set to manually bent.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks.\nRefer to for further information.\nRelease\nGenerates spool and piece elements for the currently selected spools, sets the status to Ready for fabrication regardless of outstanding warnings.\nDelete Spool Information\nDeletes fabrication information for all pipe spools and pipe pieces in the currently selected spools.\nModify Name\nUse the Rename Element window to rename individual spools.\n\nRename Spools\nRenames the currently selected spools by using auto-naming rules. If auto-naming is turned off, the menu is disabled.\nRename All Spools\nRenames all spools in the spool list by using auto-naming rules. If auto-naming is turned off, the menu is disabled.\nChange Spool Type\nSets the spool type of selected pipe spool, SHOP, FITT or SITE.\nZoom To\nDisplays the currently selected pipe spool in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe spool in the Design Explorer.\nHighlight\nHighlights the last selected pipe spool in the 3D graphical view.\nUse the Piece No. part of the Fabrication Check window to view the list of pipe pieces contained within the CE, together with the fabrication status.\n\nRight-click on the Piece No. part of the Fabrication Check window to display a pop-up menu of available options associated with the selection.\n\nValidate Pipe Pieces\nRuns the fabrication checks against the currently selected pipe pieces.\nValidate Pipe Pieces With\nUse the Select Fabrication Machines window to view a list of available fabrication machines for selection.\nSet to Manually Bent\nThe selected pipe piece is set to manually bent.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks. Refer to for further information.\nDelete Piece Information\nDeletes fabrication information for the currently selected pipe pieces.\nZoom To\nDisplays the currently selected pipe piece in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe piece in the Design Explorer.\nHighlight\nHighlights the last selected pipe piece in the 3D graphical view.\nValidate Pipe Pieces\nRuns the fabrication checks against the currently selected pipe pieces.\nValidate Pipe Pieces With\nUse the Select Fabrication Machines window to view a list of available fabrication machines for selection.\nSet to Manually Bent\nThe selected pipe piece is set to manually bent.\nSet to Minimum Feed Excess\nAdd the default surplus during the feeding of the pipe-piece through the bending machine, when in production.\nSelect Default Fabrication Machines\nSelects the default fabrication machines to be used instead of the fabrication machines specified by BendMacReference in fabrication checks. Refer to for further information.\nDelete Piece Information\nDeletes fabrication information for the currently selected pipe pieces.\nZoom To\nDisplays the currently selected pipe piece in the 3D graphical view.\nNavigate To\nNavigates to the selected pipe piece in the Design Explorer.\nHighlight\nHighlights the last selected pipe piece in the 3D graphical view.\nThe Check Results tab displays a description of the Fabrication Check errors, the check results display are classified as:\n\nThe Details tab displays all values from the fabrication check, the values are stored in PPIECE elements.\n\nDefault Fabrication Machines\nWhen the default fabrication machines are selected, the fabrication checks only use these default fabrication machines, instead of using the BendMacReference attribute of the zone, pipe and branch.\nGalvanization Tank Check\nUse the Galvanization Tank Check window to check the validity of a galvanization tank against a pipe spool.\n\nThe list of available spools displays the currently selected pipe spools.\nCE\nIdentifies the currently selected element as the working element.\nSelect Galvanization Tank\nSelect a galvanization tank from the drop-down list to validate against the currently selected pipe spool.\nTank Dimensions\n(W x H x D)\nDisplays the galvanization tank\u2019s dimensions in the W x H x D format.\nZoom when Selected\nZooms to the currently selected spool in the 3D view.\nShow Spool Volume\nDisplays the spool volume in the 3D view.\nCheck\nChecks the validity of the galvanization tank against the currently selected pipe spool.\nStop\nCancels the current check.\nCE\nIdentifies the currently selected element as the working element.\nSelect Galvanization Tank\nSelect a galvanization tank from the drop-down list to validate against the currently selected pipe spool.\nTank Dimensions\n(W x H x D)\nDisplays the galvanization tank\u2019s dimensions in the W x H x D format.\nZoom when Selected\nZooms to the currently selected spool in the 3D view.\nShow Spool Volume\nDisplays the spool volume in the 3D view.\nCheck\nChecks the validity of the galvanization tank against the currently selected pipe spool.\nStop\nCancels the current check.\nAutomatic Flange Alignment\nFor pipe-pieces and pipe spools that have been set up to be machine welded, that system make sure it correctly orientates the piping model so flange-holes and spools align when assembled.\nThe system checks flange-alignment as part of the pipe-checking and Datacon functionality, refer to for further information.\nFabrication Machine\nThe system can check pipe pieces for production readiness against bending machines, welding machines, extrusion machines and the defined stock length of tubing.\nFabrication checks requests are made to a fabrication machine manager controlling the fabrication machines. Information about the welding/bending machine operation and their corresponding activity tables can be obtained from the Manager. Refer to for further information.\nSpec.\nSelect Spec"}
{"Headers": "Drawings", "Content": "The user can create three different types of drawings.\n\n\n"}
{"Headers": "Spool Drawings", "Content": "All of the tasks that a user would carry out that are associated with the creation, modification, drawing options and errors of Pipe Spool Drawings are initiated from a central Pipe Spool Drawing window which acts as a task hub.\nWhen the Pipe Spool Drawing window is opened, the application searches for valid pipe spools below the current element and loads them into the grid. To be valid for the production of pipe sketches, each pipe must be validated using the spooling and checks functionality and must be released for Fabrication. Refer to Spooling and Checks for further information.\nIt is recommended to select a Pipe Zone element as the CE in the Model Explorer.\n\n\n\n\n\nSpooling and Checks\nPipe Spool Drawings\nPipe Spool Drawing\nPipe Spool Drawing\nSpooling and Checks\nPipe Zone\nModel Explorer"}
{"Headers": "Export Fabrication Data", "Content": "Bending machine information can be saved and exported as an XML file. Use the Fabrication NC Data window to save the bending machine information as XML file. For example, the bending activities of a specified list of pipe pieces. Bending Machine NC Output allows the bending machine information such as the bending activities of a specified list of pipe pieces to be saved to a file.\n\nCE\nIdentifies the element in the Model Explorer as the CE.\nPipe Pieces\nView NC Data when selected\nSelect the View NC Data when selected to display the contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\nCreate .ben data files\nChanges the format of the bending program\nOptions\nFile\nSelect a file option from the drop-down list:\nOne File - to create a single file\nBy Pipe - to create a file for each pipe\nBy Pipe Spool - to create a file for each pipe spool\nBy Pipe Piece - to create a file for each pipe.\nName\nChoose a name option from the drop-down list:\nSelect Element Name, the name of the element (PPIECE, PSPOOL or PIPE) is used as the name of the output file.\nSelect Date & Sequence, the current date, time and sequence number is used as the name of the output file. For example, 20121107235358-1.xml.\nFolder\nDisplays the file path for the created .xml file, if required navigate to a different location, click Browse then navigate to the new location.\nSave Options\nClick Save Options to save the options.\nExport\nClick Export to export the NC data of the selected pipe pieces in the .xml format to a specified location. Once complete the name of the .xml file is displayed in the NC File column.\nThe contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\nStop\nClick Stop to stop the export process.\nCE\nIdentifies the element in the Model Explorer as the CE.\nPipe Pieces\n\nView NC Data when selected\nSelect the View NC Data when selected to display the contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\nCreate .ben data files\nChanges the format of the bending program\nOptions\n\nSelect a file option from the drop-down list:\nOne File - to create a single file\nBy Pipe - to create a file for each pipe\nBy Pipe Spool - to create a file for each pipe spool\nBy Pipe Piece - to create a file for each pipe.\nChoose a name option from the drop-down list:\nSelect Element Name, the name of the element (PPIECE, PSPOOL or PIPE) is used as the name of the output file.\nSelect Date & Sequence, the current date, time and sequence number is used as the name of the output file. For example, 20121107235358-1.xml.\nDisplays the file path for the created .xml file, if required navigate to a different location, click Browse then navigate to the new location.\nClick Save Options to save the options.\nExport\nClick Export to export the NC data of the selected pipe pieces in the .xml format to a specified location. Once complete the name of the .xml file is displayed in the NC File column.\nThe contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\n\nStop\nClick Stop to stop the export process.\n\nCE\nIdentifies the element in the Model Explorer as the CE.\nPipe Pieces\nView NC Data when selected\nSelect the View NC Data when selected to display the contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\nCreate .ben data files\nChanges the format of the bending program\nOptions\nFile\nSelect a file option from the drop-down list:\nOne File - to create a single file\nBy Pipe - to create a file for each pipe\nBy Pipe Spool - to create a file for each pipe spool\nBy Pipe Piece - to create a file for each pipe.\nName\nChoose a name option from the drop-down list:\nSelect Element Name, the name of the element (PPIECE, PSPOOL or PIPE) is used as the name of the output file.\nSelect Date & Sequence, the current date, time and sequence number is used as the name of the output file. For example, 20121107235358-1.xml.\nFolder\nDisplays the file path for the created .xml file, if required navigate to a different location, click Browse then navigate to the new location.\nSave Options\nClick Save Options to save the options.\nExport\nClick Export to export the NC data of the selected pipe pieces in the .xml format to a specified location. Once complete the name of the .xml file is displayed in the NC File column.\nThe contents of the .xml file is displayed in the AVEVA Everything3D Model Command Output window.\nStop\nClick Stop to stop the export process.\n\n\n\nFabrication NC Data\nBending Machine NC Output\nCE\nModel Explorer\nCE\nPipe Pieces\nView NC Data when selected\nAVEVA Everything3D Model Command Output\nCreate .ben data files\nOptions\nFile\nOne File\nBy Pipe\nBy Pipe Spool\nBy Pipe Piece\nName\nElement Name\nDate & Sequence\nFolder\nSave Options\nSave Options\nExport\nExport\nNC File\nAVEVA Everything3D Model Command Output\nStop\nStop"}
{"Headers": "Configuration", "Content": "Defines attributes of pipe bending, flange welding and extrusion machines. Weld handling information and default values for pipe checks and behavioral aspects. Creates new threaded ends or galvanization tank or the ability to view and/or edit an existing one. Applies a custom configuration to limit waste of material and cost.\nExport Fabrication Data\n\n\n\n\n\n\n\n\n\nExport Fabrication Data\nExport Fabrication Data\n\n\n\n\n\n"}
{"Headers": "Pipe Stress Interface", "Content": "The Pipe Stress Interface (PSI) provides two-way exchange of information between AVEVA E3D Design and the CAESAR II Pipe Stress system. Piping designers and stress engineers can exchange design and stress information seamlessly, to eliminate data re-entry and duplication.\nRefer to Pipe Stress Interface, Pipe Stress Interface Defaults, Modify Restraint Attributes and XML Schema for further information\n\n\n\n\nPipe Stress Interface\nModify Restraint Attributes\nXML Schema\nPipe Stress Interface\nPipe Stress Interface\nPipe Stress Interface Defaults\nModify Restraint Attributes\nXML Schema"}
{"Headers": "Assembly Manager", "Content": "A pipe assembly is a series of components and branches which are replica copies (in all aspects) of original components and branches. Or an assembly definition may be created to access existing macros or forms. Pipe assemblies are also used in Pipe Splitting, refer to Pipe Splitting for further information.\nAssembly Hierarchy\nTo create pipe assemblies, a separate hierarchy must be created in the Model Explorer to provide a storage area for elements which are not part of the design model, called the Application Data World Hierarchy.\n\nCreate Pipe Assemblies\nAll the tasks performed that are associated with creating or modifying pipe assemblies are initiated from the Pipe Assembly Manager window, the window acts as a task hub.\n\nApplication Dataworld Hierarchy\nAs with the Design Hierarchy, new or existing assemblies are stored in a hierarchy the elements must be stored within a world element, followed by an assembly area and assembly elements. Once the assembly element is created an element called a Design Data Set is created below it, this stores the rules associated with the assembly and its individual components.\n\nCreate Assembly World Element\nUse the Create Assembly World window to create an Assembly World element in the database hierarchy.\n\nInput the attributes for the assembly world element, click OK to create the assembly world element or click Cancel to discard any inputs and close the Create Assembly World window.\nCreate Assembly Area Element\nUse the Create Assembly Area window to create an assembly area element in the database hierarchy.\n\nInput the attributes for the assembly world element, click OK to create the assembly world element or click Cancel to discard any inputs and close the Create Assembly Area window.\nCreate Assembly Element\nUse the Create Assembly Area window to create an assembly element in the database hierarchy.\n\nInput the attributes for the assembly world element, click OK to create the assembly world element or click Cancel to discard any inputs and close the Create Assembly window.\nThe basic hierarchy has now been created is displayed in the Model Explorer and the Pipe Assembly Manager window which can now be populated with assemblies. The easiest way to create an assembly is to copy an existing assembly already created in the design, click Copy Design. The assembly displays in the Model Explorer and the Pipe Assembly Manager window.\nAdditional rules can now be added to the assembly and individual components within that assembly.\n\n\n\n\nNon-Graphical Assemblies\nTo enable an assembly to perform a function or display a window, the function or form rule needs to be created for the assembly.\nDisplay a Form\nUse the Pipe Assembly Rules window to create a form rule.\n\nIn the Form Name field, enter the name of the form to display when the assembly is used, the form name must not contain !! or ().\nClick OK, the Form Name is added to the Assembly Rules and stored in the Assembly Design Data Set so that it can be run each time the assembly is used.\nClick Cancel to discard any inputs and close the Pipe Assembly Rules window.\nPerform a Function\nUse the Pipe Assembly Rules window to create a func rule.\n\nIn the Function Name field, enter the name of the function to be performed when the assembly is used, the function must not contain !! or ().\nClick OK, the Function Name is added to the Assembly Rules and stored in the Assembly Design Data Set so that it can be run each time the assembly is used.\nClick Cancel to discard any inputs and close the Pipe Assembly Rules window.\nPrimary and Secondary Origins\nWhen an assembly is inserted into the design, the arrive point of the first component is used to position the assembly unless a primary origin is defined.\nUse the Pipe Assembly Rules window to set a primary origin.\n\nThe primary origin can be set by selecting the point in the 3D graphical view or the element name or reference number and the required PPOINT can be input.\nTo edit or delete any form, function or primary and secondary origin, from the Assembly Rules part of the Pipe Assembly Manager window, click Edit or Delete.\nAssembly Component Rules\nComponent rules are necessary to add greater flexibility to assemblies in general use. The concept of copying an assembly instance has limitations where specifications have different STYPEs, because the selection fails. For example the STYPE for a gasket in one specification is RF where in another it is G. To solve this problem, two assemblies can be created to cater for both cases by having rules in the assembly rules.\nAssembly rules multiple STYPEs, Positions, Orientation and restricting the STYPE to a particular SPEC/STYPE combination.\nEach component in the assembly may have instances of all rule types associated with it. When the component is copied into the design, the rules are evaluated in place of the default actions. If no rules are present than a new item is created using the same relative position and relative and orientation as that of the original. The distinct actions for each component are:\nThe addition of rules enables the default actions to be supplemented or overridden, refer to for further information.\nComponent Rules\nUse the Assembly Rules part of the Pipe Assembly window, to create addition rules or edit existing component rules, select the component to populate the Component Rules pane.\n\nStype\nUse the Pipe Assembly Rules window to create a new STYPE rule or edit an existing one.\n\nThe name of the Design Data Set is named, in the Alternative STYPE part of the Pipe Assembly Rules window. Input or amend the Specification and Stype.\nClick to select Apply to Similar Items check box to apply all similar items in the assembly.\nClick to select Force this SPEC/STYPE check box forces the assembly to use a particular specification and stype regardless of the pipe specification where the assembly is being built.\nClick OK to create or edit the Stype rule and close the Pipe Assembly Rules window or Cancel to discard any inputs and close the Pipe Assembly Rules window.\nPosition\nThe position rule replaces the default position of the component and may be through command such as THRO PT or Dist 1000. These lines are executed as complete positioning commands in place of the default position derived from the relative position in the assembly.\nUse the Pipe Assembly Rules window to create a new positioning command or edit an existing one.\nThe new or edited Positioning command overwrites the default Position.\n\nThe name of the Design Data Set is named, in the Positioning Command part of the Pipe Assembly Rules window. Input the Positioning Command.\nClick OK to create or edit the Position rule and close the Pipe Assembly Rules window or Cancel to discard any inputs and close the Pipe Assembly Rules window.\nOrientation\nOrientation rules can be in two forms, first as a single command in place of the default orientation, or as a trigger to prompt for orientation. For example ORI and P3 is D for a tee in a drain to always force it to point down. Or the command can be PROMPT, to ask for the orientation when the assembly is being built.\nUse the Pipe Assembly Rules window to create a new Orientation Command or edit an existing one.\nThe new or edited orientation command overwrites the default orientation command.\n\nThe name of the Design Data Set is named, in the Orientation Command part of the Pipe Assembly Rules window. Input the Orientation Command.\nClick OK to create or edit the Orientation rule and close the Pipe Assembly Rules window or Cancel to discard any inputs and close the Pipe Assembly Rules window.\nBore Selection\nThe components which make up an assembly can often be of differing bore sizes, to reduce the amount of selection, bore selection rules can be put in place to use other components as a reference rather than prompting to select a bore size.\nUse the Pipe Assembly Rules window to create a new Bore Selection rule or edit an existing one.\nThe new or edited Bore Selection rule overwrites the default bore selection.\n\nThe name of the Design Data Set is named, in the Bore Size part of the Pipe Assembly Rules window. From the Bore Type drop-down list, select the bore type to act as a reference.\nIn the Copy From field, identify the location of the existing assembly.\nSelect PICK, to select the component to act as a reference.\nClick OK to create or edit the Bore Size rule and close the Pipe Assembly Rules window or Cancel to discard any inputs and close the Pipe Assembly Rules window.\nKey Elements\nA Key Element (of which there can be only one) is provided to allow an existing element in the design to directly replace an assembly such that the assembly is built around an existing design element as if it was part of the assembly. In effect a design component is used as a positioning and orientation component for the rest of the assembly.\nSet a Key Element\nTo set a Key Element, right-click the component in the design hierarchy of the Pipe Assembly Manager window to display the Key Element drop-down menu.\n\nSelect Set Key Element from the drop-down list to display the key element in the design database.\nRemove Key Element\nTo remove a Key Element, right-click the component in the design hierarchy of the Pipe Assembly Manager window to display the Key Element drop-down menu.\nSelect Remove Key Element from the drop-down list, the key element is removed from the design database.\nSelection (STYPE) - SEL WITH STYP RF\nPosition - DIST 200 FROM PREV\nOrientation - ORI IS N WRT PREV\nBore Selection - Use PL of PREV ELBO.\nSelection (STYPE) - SEL WITH STYP RF\nSelection (STYPE) - SEL WITH STYP RF\nPosition - DIST 200 FROM PREV\nPosition - DIST 200 FROM PREV\nOrientation - ORI IS N WRT PREV\nOrientation - ORI IS N WRT PREV\nBore Selection - Use PL of PREV ELBO.\nBore Selection - Use PL of PREV ELBO.\nNote: Secondary origins are used in pipe splitting to derive correct spool lengths, refer to Spooling for further information.\nNote: The new or edited Stype rule overwrites the default Stype.\n\n\n\nPipe Splitting\nSpooling\nPipe Splitting\nPipe Splitting\nModel Explorer\nApplication Data World Hierarchy\nPipe Assembly Manager\nCreate Assembly World\nOK\nCancel\nCreate Assembly World\nCreate Assembly Area\nOK\nCancel\nCreate Assembly Area\nCreate Assembly Area\nOK\nCancel\nCreate Assembly\nModel Explorer\nPipe Assembly Manager\nCopy Design\nPipe Assembly Manager\n\n\n\n\n\n\n\n\n\n\n\n\n\nPipe Assembly Rules\nForm Name\nOK\nForm Name\nCancel\nPipe Assembly Rules\nPipe Assembly Rules\nFunction Name\nOK\nFunction Name\nCancel\nPipe Assembly Rules\nNote\n:\nSpooling\nPipe Assembly Rules\nAssembly Rules\nPipe Assembly Manager\nEdit\nDelete\n\nComponent Rules\nAssembly Rules\nPipe Assembly\nComponent Rules\nPipe Assembly Rules\nNote\n:\nStype\nDesign Data Set\nAlternative STYPE\nPipe Assembly Rules\nSpecification\nStype\nApply to Similar Items\nForce this SPEC/STYPE\nOK\nStype\nPipe Assembly Rules\nCancel\nPipe Assembly Rules\nPipe Assembly Rules\nPositioning\nDesign Data Set\nPositioning Command\nPipe Assembly Rules\nOK\nPosition\nPipe Assembly Rules\nCancel\nPipe Assembly Rules\nPipe Assembly Rules\nDesign Data Set\nOrientation Command\nPipe Assembly Rules\nOK\nPipe Assembly Rules\nCancel\nPipe Assembly Rules\nPipe Assembly Rules\n\nDesign Data Set\nBore Size\nPipe Assembly Rules\nBore Type\nCopy From\nPICK\nOK\nBore Size\nPipe Assembly Rules\nCancel\nPipe Assembly Rules\nPipe Assembly Manager\nKey Element\n\nSet Key Element\nPipe Assembly Manager\nKey Element\n\nRemove Key Element"}
{"Headers": "Hull Routing", "Content": "Use the functionality to route a pipe along the curve of a hull plate at a certain distance and offset.\n\nSurfaces\nSurface Selection\nUse to select the surface(s) upon which a routing curve is to be created. Prompt is displayed \u2018Identify element\u2019 selected panels are highlighted in red. Press Esc once the hull panels are selected/deselected. Also use to deselect panel(s).\nNote:\nOnly UPANEL or IPLATE are currently supported.\nRoute\nRoute Current Element\nUse to align the currently selected element (CE) with the hull.\nNote:\nIf the CE is not a bend or elbow this functionality is not available.\nRoute Next Component\nUse to position the next component created or copied at the curve of the hull.\nNote:\nSwitching between route modes updates the graphical aids and coordinates axis in the 3D graphical view.\nNote:\nIt is not possible always to position or copy the CE against the hull curve, however it is possible to draw the hull curve graphical aids.\nRouting Direction\nRoute With Flow\nUse to route the pipe in the head to tail direction.\nRoute Against Flow\nUse to route the pipe in the tail to head direction.\nCreate/Modify Component\nAngle\nIf the CE is an elbow or bend, use to modify the angle of the elbow or bend (a maximum and minimum angle can be specified).\nDirection towards pick\nIf the CE is an elbow or a bend, use to modify the angle of the CE so that the leave or arrive is pointing towards a picked element in the 3D graphical view.\nPosition at Curve\nIf the CE is an elbow or a bend use to position the P0 of the CE on the defined curve. A red translucent tube draw aid is displayed.\nNote:\nIt is not possible to use the position functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.\nCopy, Orientate and Position Current Component\nThis functionality is only available when using the route next component functionality.\nIf the CE is a bend or elbow, the CE can be copied and then orientated and positioned accordingly. A red translucent tube draw aid is displayed.\nIf it is not possible the CE at the curve, then the CE is copied and can be orientated but not positioned.\nNote:\nIt is not possible to use the copy functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.\nGraphical Aids\nIntersection\nCoordinates\nThe directions available for selection are based on a coordinate system:\nLocal - Based on the leave/arrive direction of the CE (elbow or bend)\nOrthogonal - Based on the leave/arrive direction of the CE (elbow or bend), these are projected in the horizontal plane\nWorld - World coordinate system: X,Y,Z and -X, -Y, -Z.\nDirection\nThe intersection direction is the direction of the hull plate in comparison to the CE and routing direction. The options available for selection are based on the coordinate system selected.\nThe available directions are demonstrated by the graphical aid axes in the 3D graphical view.\nFor example:\nIn the screen shot, the routing direction is the leave of the elbow is Y. So the routing line goes from the leave of the elbow in the Y direction. In relation to the routing line, the direction of the hull is either Y or -Z.\nSo in the example an intersection direction of -Z has been chosen. The blue lines show how this direction is used to calculate the graphical curve.\nEach spine is calculated by going along the routing direction (Leave direction (Y)) and at each gap interval (in this case 100mm), using the intersection direction to create a curve spine of a given length (In this case a distance of 250mm)\nA curve is then produced by joining up the ends of each of the spine lines.\nShow\nUse to toggle the graphical aids and hull curve in the 3D graphical view on or off.\nShow Helper Aids\nUse to display the blue graphical aid lines which can help to understand how the curve is being constructed.\nProjection Plane\nThe red plane graphical aid is displayed in the 3D graphical view (vertically or horizontally) is only available when the Normal Line Type functionality is selected. Refer to Line Type for further information.\nUsed to project the normal direction from the hull into the pipe or routing plane so that the component or next component can be routed against the curve.\nClear Aids/Surface Elements\nUse to clear the 3D graphical view of all graphical aids, for example - hull curve and selected surfaces).\nLine Type\nNormal\nUse to set the orientation of the spines coming from the hull to Normal.\nDraws the spines in the normal direction coming from the hull face. The normal direction is projected into the projection plane so that they are in line with the routing direction thus allowing the current or next component to be routed against the hull.\nNote:\nIn the normal mode, the spines are yellow with a green curve.\nOrthogonal\nDraws the spines in the opposite direction to the intersection direction. Only the local coordinate system is available.\nNote:\nIn the orthogonal mode, the spines are red with a yellow curve.\nLine Offsets\nDistance\nUse to set the length of the spines coming from the hull plate (which sets the position of the curve).\nGap\nUse to set the spacing between the blue graphical aid lines (These are positioned along the arrive/leave direction of the CE and are projected in the intersection direction until the shell plate is hit).\nComponent Sequence List\nUse to scroll through and select individual components within the currently selected branch, refer to Component Sequence List for further information.\nSurfaces\n\n\n\nSurface Selection\nUse to select the surface(s) upon which a routing curve is to be created. Prompt is displayed \u2018Identify element\u2019 selected panels are highlighted in red. Press Esc once the hull panels are selected/deselected. Also use to deselect panel(s).\nRoute\n\n\nRoute Current Element\nUse to align the currently selected element (CE) with the hull.\n\nRoute Next Component\nUse to position the next component created or copied at the curve of the hull.\nRouting Direction\n\n\nRoute With Flow\nUse to route the pipe in the head to tail direction.\n\nRoute Against Flow\nUse to route the pipe in the tail to head direction.\nCreate/Modify Component\n\nAngle\nIf the CE is an elbow or bend, use to modify the angle of the elbow or bend (a maximum and minimum angle can be specified).\n\nDirection towards pick\nIf the CE is an elbow or a bend, use to modify the angle of the CE so that the leave or arrive is pointing towards a picked element in the 3D graphical view.\n\nPosition at Curve\nIf the CE is an elbow or a bend use to position the P0 of the CE on the defined curve. A red translucent tube draw aid is displayed.\n\n\n\n\nCopy, Orientate and Position Current Component\nThis functionality is only available when using the route next component functionality.\nIf the CE is a bend or elbow, the CE can be copied and then orientated and positioned accordingly. A red translucent tube draw aid is displayed.\nIf it is not possible the CE at the curve, then the CE is copied and can be orientated but not positioned.\nGraphical Aids\n\nIntersection\n\n\nCoordinates\nThe directions available for selection are based on a coordinate system:\n\nDirection\nThe intersection direction is the direction of the hull plate in comparison to the CE and routing direction. The options available for selection are based on the coordinate system selected.\nThe available directions are demonstrated by the graphical aid axes in the 3D graphical view.\nFor example:\n\n\n\n\n\nIn the screen shot, the routing direction is the leave of the elbow is Y. So the routing line goes from the leave of the elbow in the Y direction. In relation to the routing line, the direction of the hull is either Y or -Z.\nSo in the example an intersection direction of -Z has been chosen. The blue lines show how this direction is used to calculate the graphical curve.\nEach spine is calculated by going along the routing direction (Leave direction (Y)) and at each gap interval (in this case 100mm), using the intersection direction to create a curve spine of a given length (In this case a distance of 250mm)\nA curve is then produced by joining up the ends of each of the spine lines.\n\nShow\nUse to toggle the graphical aids and hull curve in the 3D graphical view on or off.\n\nShow Helper Aids\nUse to display the blue graphical aid lines which can help to understand how the curve is being constructed.\nProjection Plane\n\n\nThe red plane graphical aid is displayed in the 3D graphical view (vertically or horizontally) is only available when the Normal Line Type functionality is selected. Refer to Line Type for further information.\nUsed to project the normal direction from the hull into the pipe or routing plane so that the component or next component can be routed against the curve.\n\nClear Aids/Surface Elements\nUse to clear the 3D graphical view of all graphical aids, for example - hull curve and selected surfaces).\nLine Type\n\n\n\nNormal\nUse to set the orientation of the spines coming from the hull to Normal.\nDraws the spines in the normal direction coming from the hull face. The normal direction is projected into the projection plane so that they are in line with the routing direction thus allowing the current or next component to be routed against the hull.\n\nOrthogonal\nDraws the spines in the opposite direction to the intersection direction. Only the local coordinate system is available.\nLine Offsets\n\nDistance\nUse to set the length of the spines coming from the hull plate (which sets the position of the curve).\n\nGap\nUse to set the spacing between the blue graphical aid lines (These are positioned along the arrive/leave direction of the CE and are projected in the intersection direction until the shell plate is hit).\nComponent Sequence List\nUse to scroll through and select individual components within the currently selected branch, refer to Component Sequence List for further information.\n\nSurfaces\nSurface Selection\nUse to select the surface(s) upon which a routing curve is to be created. Prompt is displayed \u2018Identify element\u2019 selected panels are highlighted in red. Press Esc once the hull panels are selected/deselected. Also use to deselect panel(s).\nNote:\nOnly UPANEL or IPLATE are currently supported.\nRoute\nRoute Current Element\nUse to align the currently selected element (CE) with the hull.\nNote:\nIf the CE is not a bend or elbow this functionality is not available.\nRoute Next Component\nUse to position the next component created or copied at the curve of the hull.\nNote:\nSwitching between route modes updates the graphical aids and coordinates axis in the 3D graphical view.\nNote:\nIt is not possible always to position or copy the CE against the hull curve, however it is possible to draw the hull curve graphical aids.\nRouting Direction\nRoute With Flow\nUse to route the pipe in the head to tail direction.\nRoute Against Flow\nUse to route the pipe in the tail to head direction.\nCreate/Modify Component\nAngle\nIf the CE is an elbow or bend, use to modify the angle of the elbow or bend (a maximum and minimum angle can be specified).\nDirection towards pick\nIf the CE is an elbow or a bend, use to modify the angle of the CE so that the leave or arrive is pointing towards a picked element in the 3D graphical view.\nPosition at Curve\nIf the CE is an elbow or a bend use to position the P0 of the CE on the defined curve. A red translucent tube draw aid is displayed.\nNote:\nIt is not possible to use the position functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.\nCopy, Orientate and Position Current Component\nThis functionality is only available when using the route next component functionality.\nIf the CE is a bend or elbow, the CE can be copied and then orientated and positioned accordingly. A red translucent tube draw aid is displayed.\nIf it is not possible the CE at the curve, then the CE is copied and can be orientated but not positioned.\nNote:\nIt is not possible to use the copy functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.\nGraphical Aids\nIntersection\nCoordinates\nThe directions available for selection are based on a coordinate system:\nLocal - Based on the leave/arrive direction of the CE (elbow or bend)\nOrthogonal - Based on the leave/arrive direction of the CE (elbow or bend), these are projected in the horizontal plane\nWorld - World coordinate system: X,Y,Z and -X, -Y, -Z.\nDirection\nThe intersection direction is the direction of the hull plate in comparison to the CE and routing direction. The options available for selection are based on the coordinate system selected.\nThe available directions are demonstrated by the graphical aid axes in the 3D graphical view.\nFor example:\nIn the screen shot, the routing direction is the leave of the elbow is Y. So the routing line goes from the leave of the elbow in the Y direction. In relation to the routing line, the direction of the hull is either Y or -Z.\nSo in the example an intersection direction of -Z has been chosen. The blue lines show how this direction is used to calculate the graphical curve.\nEach spine is calculated by going along the routing direction (Leave direction (Y)) and at each gap interval (in this case 100mm), using the intersection direction to create a curve spine of a given length (In this case a distance of 250mm)\nA curve is then produced by joining up the ends of each of the spine lines.\nShow\nUse to toggle the graphical aids and hull curve in the 3D graphical view on or off.\nShow Helper Aids\nUse to display the blue graphical aid lines which can help to understand how the curve is being constructed.\nProjection Plane\nThe red plane graphical aid is displayed in the 3D graphical view (vertically or horizontally) is only available when the Normal Line Type functionality is selected. Refer to Line Type for further information.\nUsed to project the normal direction from the hull into the pipe or routing plane so that the component or next component can be routed against the curve.\nClear Aids/Surface Elements\nUse to clear the 3D graphical view of all graphical aids, for example - hull curve and selected surfaces).\nLine Type\nNormal\nUse to set the orientation of the spines coming from the hull to Normal.\nDraws the spines in the normal direction coming from the hull face. The normal direction is projected into the projection plane so that they are in line with the routing direction thus allowing the current or next component to be routed against the hull.\nNote:\nIn the normal mode, the spines are yellow with a green curve.\nOrthogonal\nDraws the spines in the opposite direction to the intersection direction. Only the local coordinate system is available.\nNote:\nIn the orthogonal mode, the spines are red with a yellow curve.\nLine Offsets\nDistance\nUse to set the length of the spines coming from the hull plate (which sets the position of the curve).\nGap\nUse to set the spacing between the blue graphical aid lines (These are positioned along the arrive/leave direction of the CE and are projected in the intersection direction until the shell plate is hit).\nComponent Sequence List\nUse to scroll through and select individual components within the currently selected branch, refer to Component Sequence List for further information.\nLocal - Based on the leave/arrive direction of the CE (elbow or bend)\nOrthogonal - Based on the leave/arrive direction of the CE (elbow or bend), these are projected in the horizontal plane\nWorld - World coordinate system: X,Y,Z and -X, -Y, -Z.\nLocal - Based on the leave/arrive direction of the CE (elbow or bend)\nLocal - Based on the leave/arrive direction of the CE (elbow or bend)\nOrthogonal - Based on the leave/arrive direction of the CE (elbow or bend), these are projected in the horizontal plane\nOrthogonal - Based on the leave/arrive direction of the CE (elbow or bend), these are projected in the horizontal plane\nWorld - World coordinate system: X,Y,Z and -X, -Y, -Z.\nWorld - World coordinate system: X,Y,Z and -X, -Y, -Z.\nNote:\nCurrently this functionality only supports the new style IPLATEs.\nNote:\nOnly UPANEL or IPLATE are currently supported.\nNote:\nIf the CE is not a bend or elbow this functionality is not available.\nNote:\nSwitching between route modes updates the graphical aids and coordinates axis in the 3D graphical view.\nNote:\nIt is not possible always to position or copy the CE against the hull curve, however it is possible to draw the hull curve graphical aids.\nNote:\nIt is not possible to use the position functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.\nNote:\nIt is not possible to use the copy functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.\nNote:\nIn the normal mode, the spines are yellow with a green curve.\nNote:\nIn the orthogonal mode, the spines are red with a yellow curve.\n\n\n\nNote\n:\nSurfaces\nSurface Selection\nIdentify element\u2019\nEsc\nNote\n:\nRoute\nRoute Current Element\nNote\n:\nRoute Next Component\nNote\n:\nNote\n:\nRouting Direction\nRoute With Flow\nRoute Against Flow\nCreate/Modify Component\nAngle\nDirection towards pick\nPosition at Curve\nNote\n:\nCopy, Orientate and Position Current Component\nNote\n:\nGraphical Aids\nIntersection\nCoordinates\nLocal\nOrthogonal\nWorld\nDirection\nShow\nShow Helper Aids\nProjection Plane\nNormal Line Type\nLine Type\nClear Aids/Surface Elements\nLine Type\nNormal\nNormal\nNote\n:\nOrthogonal\nNote\n:\nLine Offsets\nDistance\nGap\nComponent Sequence List\nComponent Sequence List"}
{"Headers": "Worked Examples", "Content": "All of the tasks carried out that are associated with the creation and modification are initiated from the Hull Routing tab of the Piping Component Editor window. Depending on the selections made, further functionality becomes available.\n\n\n\nHull Routing\nPiping Component Editor"}
{"Headers": "Bocad Steel Interface", "Content": "AVEVA Bocad Steel Interface allows you to export and import files using the AVEVA Bocad Steel Interface (ABS) format. This is a proprietary encrypted and compressed file format designed to reduce transfer file size and to increase security.\nThe interface is compatible with AVEVA Everything3D\u2122 2.1 and beyond, henceforth known as the base product.\n\n\n\n\n\n"}
{"Headers": "Assumptions", "Content": "The AVEVA Bocad Steel Interface Reference Manual has been written for users familiar with structural design practices, who may or may not have prior knowledge of the base product.\nIt is assumed that:\nUsers have a valid base product license and the software has been installed.\nUsers have a basic knowledge of the base product.\nThe user is familiar with the basic graphical user interface (GUI) features.\nUsers have a valid base product license and the software has been installed.\nUsers have a valid base product license and the software has been installed.\nUsers have a basic knowledge of the base product.\nUsers have a basic knowledge of the base product.\nThe user is familiar with the basic graphical user interface (GUI) features.\nThe user is familiar with the basic graphical user interface (GUI) features.\n\n\n\n"}
{"Headers": "Export/Import", "Content": "AVEVA Bocad Steel Interface is an application which allows you to export and import files using the AVEVA Bocad Steel Interface (ABS) format.\n\n\n"}
{"Headers": "Export to AVEVA Bocad Steel", "Content": "Use the ABSI - Export window to export a steel structure to an ABS file.\n\n\n\n\nABSI - Export"}
{"Headers": "Mapping Files", "Content": "Click Mapping files to display the Export mapping files window which contains information about the mapping files that are to be used in the Export process.\n\nThe interface requires at least two external mapping tables to enable it to check that AVEVA Bocad Steel can accept the data. It also may use the Unicode mapping table if necessary. The mapping tables are for the Profiles and Materials between base product and the neutral file. The Unicode mapping table is to translate the base product Unicode strings into ASCII strings. The section Customize tells you how to arrange these files on the file system and what format they are to be. The interface also needs to know where the external mapping files are located on your computer network. For this, internal mapping tables are required. Refer to Internal Mapping Files which explains how to configure the interface to tell it where all the files are located.\nYou may have a generic set of mapping tables to map between the base product and AVEVA Bocad Steel. Or you may have a set for a particular steel fabricator.\nThe current file settings are indicated on the ABSI - Export mappings file window. Do not be concerned that the path name may be truncated by the insertion of the ellipsis (\u2026): it is modified only for display purposes on the window.\nThe system also checks that these files are compatible with AVEVA Bocad Steel by checking only the identification line at the top of each mapping table. Refer to External Mapping Files for further information about the format of these mapping files.\nThe two main options are System and Manual which are activated by selecting the appropriate radio button.\nSystem causes the interface to select automatically the mapping tables for AVEVA Bocad Steel according to the system configuration files.\nManual activates other radio buttons, which are initially greyed out for the System option. Selecting this option changes the window to be similar to below.\n\nYou can select the file type using the Profiles, Materials or Unicode radio buttons and enter the full path name of the file in the data entry area. You can also include system environment variables in the path name as long as they are in the proper base product format, for example AVEVA Bocad Steel %ENVVAR% being the base product representation of the ENVVAR environment variable.\nClick carriage return, the interface checks for existence of the file and compatibility with AVEVA Bocad Steel.\nYou can choose by hand which mapping file to use by either entering its name in the text data entry field, or by using the Browse option to bring up a File Browser. You may use this browser to search for the relevant mapping file.\nOnce you have entered all the correct data on the Export Mapping Files window, click OK the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.\nNote:\nThe check is only that the file applies to AVEVA Bocad Steel and not that it is a correct file type or that its contents are correctly formatted.\n\n\n\nCustomize\nInternal Mapping Files\nExternal Mapping Files\nMapping files\nExport mapping files\nCustomize\nInternal Mapping Files\nABSI -\nExport mappings file\nExternal Mapping Files\nUnicode\nNote:\nExport Mapping Files"}
{"Headers": "Error and Log File Messages", "Content": "Export file already exists\nFile exists, you will get the option to overwrite it.\nWrong place in database\nYou is most likely at the WORLD element in the database.\nIllegal Transfer letter\nYou can only use transfer letters between A and Z.\nNothing to export\nYou has deselected both the Linear Members and Plates options.\nCannot decrement Transfer letter\nYou can not decrease the Transfer letter, only increment it.\nExport file already exists\nFile exists, you will get the option to overwrite it.\nWrong place in database\nYou is most likely at the WORLD element in the database.\nIllegal Transfer letter\nYou can only use transfer letters between A and Z.\nNothing to export\nYou has deselected both the Linear Members and Plates options.\nCannot decrement Transfer letter\nYou can not decrease the Transfer letter, only increment it.\n\nExport file already exists\nFile exists, you will get the option to overwrite it.\nWrong place in database\nYou is most likely at the WORLD element in the database.\nIllegal Transfer letter\nYou can only use transfer letters between A and Z.\nNothing to export\nYou has deselected both the Linear Members and Plates options.\nCannot decrement Transfer letter\nYou can not decrease the Transfer letter, only increment it.\n\n\n\nExport file already exists\nWrong place in database\nIllegal Transfer letter\nNothing to export\nCannot decrement Transfer letter"}
{"Headers": "Export Information", "Content": "Click Export Information to display the ABSI - Export Information window which contains information about the export process.\n\nYou can either type the full path name of the output file, or click Browse to display a File Browser. The interface tests to see if the file exists and if it does, you will be asked whether you wish to overwrite it. If the file does exist and you want to overwrite it, the file mode beside Browse will change from WRITE to OVERWRITE. The output file is rechecked for write/overwrite status during the actual Export process. This is because you can perform Exports repeatedly without changing the output file name.\nYou can create and use any number of project header elements that are used to insert information into the transfer file. The interface assumes that there is a default one /FABGLOBAL. These elements are stored in the Application Data area. On export and import one can associate particular project header details with the transfer file. This can include the model offset and orientation to be applied to the model.\nDifferent transfers can use different headers. You can select the correct one, or create a new one in from the Project Header drop down list. It is up to you to ensure that the correct header is used.\n\nYou can view the information contained by the chosen header element by clicking Inspect which displays the ABSI - Export Header window.\n\nAt first the entry fields are inactive so you can just read the contents. To modify the contents of the fields click Edit on the Export File Header Details window and the fields become active allowing you to enter any revised data. Click Apply and the data will be transferred back to the chosen header object, overwriting the original data. Click Cancel to leave all the data unchanged.\n\nWith this window, you can define a model offset and rotation for ease of use in Bocad.\nUsing the toggles on the ABSI - Export Information window, you can select whether to export Straight or Curved members, and Plates, with the additional option of including their holes. You are able to export Plates without their holes.\nNote:\nIf you do not enter the full path name and just a plain file name, the output file is created in the folder which started the base product. You may also include system environment variables in the path name as long as they are in the proper base product format, for example: %ENVVAR% being the base product representation of the ENVVAR environment variable.\nNote:\nYou cannot modify or delete /FABGLOBAL.\n\n\n\nExport Information\nABSI - Export Information\nNote:\nABSI - Export Header\nExport File Header Details\nNote:\nABSI -"}
{"Headers": "Model Offsets and Orientations", "Content": "If you have already selected something to Export, the Export Information window is updated to include the 3d world limit box of the export items.\n\nYou can see the limit box of the items to be exported in global terms, or in terms of the selected header element.\n\nAVEVA Bocad Steel cannot handle such large coordinates as other AVEVA products, and here there is the opportunity to define in the file header a local origin, offset position and orientation in world coordinates. The model offset and orientation are used to translate the model in the ABS file. The East/North/Up position is entered in the fields indicated. It might take an iteration or two for the AVEVA model to be compatible with the AVEVA Bocad Steel model, such that the user of each system is happy with the Model Offset value. Once this is achieved, the Model Offset will be locked and it becomes fixed for future transfers. If you later try to modify these values, it must be an explicit decision. Refer to Managing the Model Limits and Offsets for further information.\n\nThe Model Offset values are stored in a system ZONE in the Application Data world /FABAPPDW. In case of emergency, using normal commands outside the interface, the ZONE can be locked or unlocked by hand.\nYou can transfer the minimum world coordinate of any model that is being displayed to the file header by pressing the World min button. Using the values as a basis, you can round the numbers to be more convenient.\n\n\n\nManaging the Model Limits and Offsets\nExport Information\nManaging the Model Limits and Offsets"}
{"Headers": "Create a new header block", "Content": "You can create a new header block by selecting New header\u2026 from the Project header drop down list.\n\nThe ABSI - Export Header window is displayed, you can populate the window with all the relevant details. Remember to fill in the name to appear in the header drop down list. This must be the basis of a valid Dabacon element name.\nThe Model Rotation is a rotation angle measured in degrees about the global Z axis following the right hand screw rule. It is usually assumed that the header is locked to prevent accidental changes\n\n\n\nNew header\u2026\nProject header\nABSI - Export Header\nModel Rotation"}
{"Headers": "Transfer User Data", "Content": "This version of the interface allows you to transfer up to 5 numerical values and 5 text values to AVEVA Bocad Steel. The data are associated with linear members or plates. There is the equivalent functionality in AVEVA Bocad Steel, but they operate in different ways.\nIf required, you can transfer specific information about the model hierarchy to assist the AVEVA Bocad Steel user in managing the model in AVEVA Bocad Steel. This functionality is covered by user data, the interface comes with two sample configurations, but you can create more.\n\nUse the toggles to turn fields on and off, you can then enter the Source type of element in the hierarchy above the element at which this data extraction is taking place. You can even extract data at the GENSEC, PANE or SCTN level. The attribute is the PDMS attribute name or the name of a user defined function that can perform more complex operations to return the correct value. As with all equivalent customization functionality, it is up to you to manage errors.\nBy default the system is suppled with two configurations, ANY and HIERARCHY. When viewing the HIERARCHY, ABSI Export User Data Set window is populated as follows:\n\nIf the attribute value is not immediately available, you can specify an alternative default attribute, function or value. And then if required enter descriptive text. The data on the window is encoded and included in the transfer file for the AVEVA Bocad Steel user to see what has been transferred.\n\nThis information is not stored in the database, but in the configuration file, which can be loaded by other projects. Refer to Customize for further information.\nThe interface checks that you are attempting to Export something and will output a message if there is nothing to export.\nOnce all the correct data has been entered on the Export Information window, click OK and the interface variables will be updated. Click Cancel to close the window, leaving the original interface variables unchanged.\n\n\n\nCustomize\nANY\nHIERARCHY.\nHIERARCHY, ABSI Export User Data Set\nCustomize\nExport Information\nCancel"}
{"Headers": "Run Information", "Content": "Click Run Information to display the Export window which allows you to view the Log File after the export process is complete by clicking to select the Log File? check box.\n\nClick the Brief or Verbose radio buttons, you can choose which format messages are displayed.\nThe Test Run? option allows you to suppress the updating of all the Export flags. This is so that you can see if there will be a successful Export of the model. You may find that the Profile or Material mapping files are not quite up to date which might cause a failure in the Export process. Therefore, you can select this option to define this as a test run.\nAfter the Export process has completed, Test Run? is reset to false. This is so that you are forced to state categorically each time the model is Exported that the run is a trial.\nOnce all the correct data has been entered on the Run Information window, click OK and the interface variables will be updated. Click Cancel to close the window, leaving the original interface variables unchanged.\n\n\n\nRun Information\nExport\nLog File?\nBrief\nVerbose\nRun Information"}
{"Headers": "Members and Export List", "Content": "The Members pane allows you to navigate around the database hierarchy.\nThough AVEVA E3D 2.1\u2122 creates only GENSEC elements, old models might still contain SCTNs as well. The interface will still find SCTNs and export them. If a model is being imported and there are pre-existing SCTNs, these will be preserved, but all new members will be created as GENSECs.\nIf you add something to the Export list and has the item on display in a 3D Volume View it will be enhanced by changing its colour. The Export list is managed such that duplicate elements are removed and that items are exported only once.\nThere are several methods of adding elements to the Export list:\nAdd CE\nAdds the current element to the list. This also implies all items below the current element in the database hierarchy. The WORL can not be added to the list.\nAdd by Pick\nAllows you to select an item from the 3D Volume View. It is similar to other pick functions. Selection of this option brings up a Status window and puts you into a mode where an item from the 3D Volume View can be picked. You can also pick a sequence of items in succession to add to the Export list. Press Esc when complete. If you do not want to continue, press Esc.\nAdd Structure\nAttempts to climb to the Structure owning the current element and add that to the Export list. A warning is displayed if there isn't an owning Structure.\nThere is also a set of methods by which you can remove items from the Export list. These options work only on entries in the Export list, rather than in the model. As with adding to the Export list, removing from the Export list will cause the item or items removed to be returned to the default colour as defined by this interface.\nNote:\nThe colour may be different from the colour in which it may have originally been added to the Drawlist.\nRemove CE\nLooks for the name of the current element in the list and removes it if present.\nRemove by Pick\nAllows you to select something from the 3D Volume View and, if it is present in the Export list, the name will be removed. As with the Add by Pick option, you may select a series of items to attempt to remove from the Export list until Esc is pressed.\nRemove Selected\nIs a means by which the item selected in the Export list is subsequently removed. Select the item first in the list, then click Remove Selected.\nClear\nRemoves everything from the list.\nAdd CE\nAdds the current element to the list. This also implies all items below the current element in the database hierarchy. The WORL can not be added to the list.\nAdd by Pick\nAllows you to select an item from the 3D Volume View. It is similar to other pick functions. Selection of this option brings up a Status window and puts you into a mode where an item from the 3D Volume View can be picked. You can also pick a sequence of items in succession to add to the Export list. Press Esc when complete. If you do not want to continue, press Esc.\nAdd Structure\nAttempts to climb to the Structure owning the current element and add that to the Export list. A warning is displayed if there isn't an owning Structure.\nThere is also a set of methods by which you can remove items from the Export list. These options work only on entries in the Export list, rather than in the model. As with adding to the Export list, removing from the Export list will cause the item or items removed to be returned to the default colour as defined by this interface.\nRemove CE\nLooks for the name of the current element in the list and removes it if present.\nRemove by Pick\nAllows you to select something from the 3D Volume View and, if it is present in the Export list, the name will be removed. As with the Add by Pick option, you may select a series of items to attempt to remove from the Export list until Esc is pressed.\nRemove Selected\nIs a means by which the item selected in the Export list is subsequently removed. Select the item first in the list, then click Remove Selected.\nClear\nRemoves everything from the list.\nYou may find that items are shown in the Export list do not exist, or have been renamed. The Export process will determine all the valid entries in the Export list and prepare the data accordingly. Clearing the list, or removing individual items will be performed as expected.\nAdd CE\nAdds the current element to the list. This also implies all items below the current element in the database hierarchy. The WORL can not be added to the list.\nAdd by Pick\nAllows you to select an item from the 3D Volume View. It is similar to other pick functions. Selection of this option brings up a Status window and puts you into a mode where an item from the 3D Volume View can be picked. You can also pick a sequence of items in succession to add to the Export list. Press Esc when complete. If you do not want to continue, press Esc.\nAdd Structure\nAttempts to climb to the Structure owning the current element and add that to the Export list. A warning is displayed if there isn't an owning Structure.\nThere is also a set of methods by which you can remove items from the Export list. These options work only on entries in the Export list, rather than in the model. As with adding to the Export list, removing from the Export list will cause the item or items removed to be returned to the default colour as defined by this interface.\nNote:\nThe colour may be different from the colour in which it may have originally been added to the Drawlist.\nRemove CE\nLooks for the name of the current element in the list and removes it if present.\nRemove by Pick\nAllows you to select something from the 3D Volume View and, if it is present in the Export list, the name will be removed. As with the Add by Pick option, you may select a series of items to attempt to remove from the Export list until Esc is pressed.\nRemove Selected\nIs a means by which the item selected in the Export list is subsequently removed. Select the item first in the list, then click Remove Selected.\nClear\nRemoves everything from the list.\nNote:\nPartial model transfers are supported by the interface, however, you must be aware of how the Import process handles partial model transfers. Refer to Comparison and Merging Processes.\nNote:\nThe colour may be different from the colour in which it may have originally been added to the Drawlist.\n\n\n\nComparison and Merging Processes\nNote:\nComparison and Merging Processes\nStatus\nNote:\nAdd by Pick\nEsc\nRemove Selected."}
{"Headers": "Error and Log File Messages", "Content": "Can't export the WORLD\nYou cannot export the WORLD\nNo owning Structure\nCannot climb to Structure element from current location in database.\nCan't export the WORLD\nYou cannot export the WORLD\nNo owning Structure\nCannot climb to Structure element from current location in database.\nClick Cancel to close the Export window.\nExport executes the Export process. As it proceeds you are kept informed of the progress by means of messages at the bottom of the main window as well as by windows and prompts.\nCan't export the WORLD\nYou cannot export the WORLD\nNo owning Structure\nCannot climb to Structure element from current location in database.\n\n\n\nCan't export the WORLD\nNo owning Structure\nCancel\nExport\nExport"}
{"Headers": "Control", "Content": "The Control drop-down menu has four options; Re-initialize, Configure, Map Converter and Exit. Changing any mapping files or any other variables:\nThe General drop-down menu has two options, Highlight and Clear ABSI History. Highlight displays the Highlighter window enabling you to identify new, changed and deleted items in the model. This has more relevance to the Import process, refer to Highlighting Changes in the Design for further information. Clear ABSI History enables one to clear the import/export history on the current element and all elements below that have date and time UDAs that are relevant to the AVEVA Bocad Steel Interface.\nRe-initialize reloads files to save you having to rebuild the whole user interface from scratch\nConfigure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information\nMap Converter starts the tool that helps you rebuild Profile mapping files\nExit removes all forms and menus and global variables associated with the interface.\nRe-initialize reloads files to save you having to rebuild the whole user interface from scratch\nRe-initialize reloads files to save you having to rebuild the whole user interface from scratch\nConfigure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information\nConfigure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information\nMap Converter starts the tool that helps you rebuild Profile mapping files\nMap Converter starts the tool that helps you rebuild Profile mapping files\nExit removes all forms and menus and global variables associated with the interface.\nExit removes all forms and menus and global variables associated with the interface.\n\n\n\nSystem Configuration\nHighlighting Changes in the Design\nControl\nRe-\ne\nConfigure, Map Converter and\nExit\nRe-\ne\nConfigure\nSystem Configuration\nMap Converter\nExit\nGeneral\nHighlight\nClear ABSI\nHistory\nHighlight\nHighlighter\nHighlighting Changes in the Design\nClear ABSI History"}
{"Headers": "The Export Process", "Content": "Exporting from the base product all items are exported using millimetres as the distance units.\nAll reference data, such as any pre-existing reference model from the current session are removed before exporting anything. for further information on Importing and for further information about saving the reference model, refer to Import from AVEVA Bocad Steel.\nPrior to any Export process, all fields are checked for validity.\nIn addition, there is an specific UDA, :FABEXCLUDE, attached to certain base product elements by which you can define whether the item is to be exported or not. Setting this logical flag to true will exclude the item from the Export process. Refer to UDAs for further information.\nBefore continuing, the Export process polls all the Configuration objects for the high water mark on Transfer and Revision numbers. It then updates the object applicable to the current MDB and user to contain the latest Transfer value. The list of all items listed in the Export list is then stored on Header element.\nAfter verifying that all the data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. This waiting time is user configurable. If there are errors raised by the external program you are notified and more detailed information is placed in the log file. If the waiting period expires without the interface detecting that the external program has completed - it may have crashed, or even not exist, you will be asked if to carry on waiting for another time unit.\n\nClick Yes and the interface will wait for another period of time. Click No to stop the interface where it is. Finally the system will indicate its completion, whether successful or not. This completion message should be read in conjunction with the log file, if any errors are indicated (if that option has been selected on the Run Information window).\n\n\n\nTo inspect the log file later, save it with the File > Save as option in the File Viewer window which will bring up a File Browser, or by clicking Save as to the suggested filename. Either way, if the file already exists, you will be asked whether to overwrite it. The log file window may then be closed by clicking Cancel.\n\nIf the Brief mode has been chosen on the Run Information window for displaying the log file, the window displaying the log file will filter out all Warning messages, leaving only the Error messages. Saving the log file, however, all messages will be retained in the file.\nIs the output file named?\nIs anything going to be exported?\nAre the mapping tables compatible with AVEVA Bocad Steel?\nIs there a valid Steel Standard table?\nIs the output file named?\nIs the output file named?\nIs anything going to be exported?\nIs anything going to be exported?\nAre the mapping tables compatible with AVEVA Bocad Steel?\nAre the mapping tables compatible with AVEVA Bocad Steel?\nIs there a valid Steel Standard table?\nIs there a valid Steel Standard table?\n\n\n\nImport from AVEVA Bocad Steel\nUDAs\nImport from AVEVA Bocad Steel\nUDAs\nRun Information\nFile Viewer\nRun Information"}
{"Headers": "Error and Log File Messages", "Content": "File does not exist\nSomehow there is no log file. Are there issues regarding access rights to your work folder?\nFile does not exist\nSomehow there is no log file. Are there issues regarding access rights to your work folder?\n\nFile does not exist\nSomehow there is no log file. Are there issues regarding access rights to your work folder?\n\n\n\nFile does not exist"}
{"Headers": "Exporting Linear Members", "Content": "A series of checks is made before a Linear Member is output.\nIf any of the above criteria is not satisfied, the linear member does not even get exported to the output file.\nAs has been indicated before, Linear Members can be transferred as either Straight or Curved. However, GENSECs can be compound shapes with both straight and arc sections.\nOnce the Linear Member has been output, the relevant UDAs specific for the interface associated with Export are updated. These are principally the element's internal ID and UUID numbers and transfer and revision numbers. This is only the minimum core database changes that affect the modification dates and times.\nThe interface may not be able to update the export information on the elements. This would usually be because the database is read-only. If this is the case, a session related macro file is produced for execution immediately afterwards, or when one has write access to the database. This file is called updateVersionNos<export date/time>.mac and is stored in your work folder.\nIs the SPRE set?\nIs it a zero length member?\nDoes it have a valid material?\nIs the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?\nAre the start and end points valid?\nIs the SPRE set?\nIs the SPRE set?\nIs it a zero length member?\nIs it a zero length member?\nDoes it have a valid material?\nDoes it have a valid material?\nIs the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?\nIs the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?\nAre the start and end points valid?\nAre the start and end points valid?\nNote:\nThis will have an effect on the subsequent import process as the member will appear to have been deleted by AVEVA Bocad Steel since its export. In fact, the linear member never made the transfer to there in the first place.\n\n\n\nNote:"}
{"Headers": "Error and Log File Messages", "Content": "Illegal or unset SPRE - not exported\nSPRE must be valid.\nZero length Linear Member - not exported\nLength less than user definable tolerance.\nNo material information - not exported\nCannot determine material properties for member.\nNo material match for nnnn. - Unknown material\n:FABMGRADE cannot be matched with a material in the Properties database.\nNo material property match\nAs above\nInconsistent material\nspecification\nThe element's MATR and :FABMGRADE attributes are not consistent.\nMultiply defined entries in\nMaterial Table\nEither a material to be mapped or a mapped profile appears more than once in the material file.\nNo match for material\nThe material is not in the material file\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThis should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.\nNo match for Cardinal Point nnnn\nPline or Cardinal Point not recognized. Neutral axis (Cardinal Point 10) assumed.\nNo Cardinal Point nnnn\nJUSL unset.\nBad Cardinal Point nnnn\nCardinal Point/Pline identified is not valid. Does it exist? Neutral axis (Cardinal Point 10) assumed.\nProblem exporting entity\nOther errors found.\nProfile cannot be mapped\nThe profile is not in the profile mapping file.\nProfile is not in the standard\nThe profile is in the profile mapping file but is not in any one of the set of standards.\nProfile is not the default\nThe profile is in the profile mapping file and is in one of the set of standards, but not the default standard.\nMultiply defined entries in\nProfile Table\nEither a profile to be mapped or a mapped profile appears more than once in the profile mapping file.\nIllegal or unset SPRE - not exported\nSPRE must be valid.\nZero length Linear Member - not exported\nLength less than user definable tolerance.\nNo material information - not exported\nCannot determine material properties for member.\nNo material match for nnnn. - Unknown material\n:FABMGRADE cannot be matched with a material in the Properties database.\nNo material property match\nAs above\nInconsistent material\nspecification\nThe element's MATR and :FABMGRADE attributes are not consistent.\nMultiply defined entries in\nMaterial Table\nEither a material to be mapped or a mapped profile appears more than once in the material file.\nNo match for material\nThe material is not in the material file\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThis should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.\nNo match for Cardinal Point nnnn\nPline or Cardinal Point not recognized. Neutral axis (Cardinal Point 10) assumed.\nNo Cardinal Point nnnn\nJUSL unset.\nBad Cardinal Point nnnn\nCardinal Point/Pline identified is not valid. Does it exist? Neutral axis (Cardinal Point 10) assumed.\nProblem exporting entity\nOther errors found.\nProfile cannot be mapped\nThe profile is not in the profile mapping file.\nProfile is not in the standard\nThe profile is in the profile mapping file but is not in any one of the set of standards.\nProfile is not the default\nThe profile is in the profile mapping file and is in one of the set of standards, but not the default standard.\nMultiply defined entries in\nProfile Table\nEither a profile to be mapped or a mapped profile appears more than once in the profile mapping file.\n\nIllegal or unset SPRE - not exported\nSPRE must be valid.\nZero length Linear Member - not exported\nLength less than user definable tolerance.\nNo material information - not exported\nCannot determine material properties for member.\nNo material match for nnnn. - Unknown material\n:FABMGRADE cannot be matched with a material in the Properties database.\nNo material property match\nAs above\nInconsistent material\nspecification\nThe element's MATR and :FABMGRADE attributes are not consistent.\nMultiply defined entries in\nMaterial Table\nEither a material to be mapped or a mapped profile appears more than once in the material file.\nNo match for material\nThe material is not in the material file\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThis should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.\nNo match for Cardinal Point nnnn\nPline or Cardinal Point not recognized. Neutral axis (Cardinal Point 10) assumed.\nNo Cardinal Point nnnn\nJUSL unset.\nBad Cardinal Point nnnn\nCardinal Point/Pline identified is not valid. Does it exist? Neutral axis (Cardinal Point 10) assumed.\nProblem exporting entity\nOther errors found.\nProfile cannot be mapped\nThe profile is not in the profile mapping file.\nProfile is not in the standard\nThe profile is in the profile mapping file but is not in any one of the set of standards.\nProfile is not the default\nThe profile is in the profile mapping file and is in one of the set of standards, but not the default standard.\nMultiply defined entries in\nProfile Table\nEither a profile to be mapped or a mapped profile appears more than once in the profile mapping file.\n\n\n\nIllegal or unset SPRE - not exported\nZero length Linear Member - not exported\nNo material information - not exported\nNo material match for nnnn. - Unknown material\nNo material property match\nInconsistent material\nspecification\nMultiply defined entries in\nMaterial Table\nNo match for material\nSyntax Error\nUn\ned Parse State\nNo match for Cardinal Point nnnn\nNo Cardinal Point nnnn\nBad Cardinal Point nnnn\nProblem exporting entity\nProfile cannot be mapped\nProfile is not in the standard\nProfile is not the default\nMultiply defined entries in\nProfile Table"}
{"Headers": "Exporting Plates", "Content": "Panels in the base product are to be transferred as Plates. This covers stiffeners, floor and toe plates. Bent plates are also transferred if they are expressed as their component flat plates. If Bent Plates are to be treated as Angle linear members then they should be modelled as such.\nIf the base product\u2019s penetration functionality is used to generate Catalogue holes, the resultant holes, kicker plates and stiffeners are not exported because they are contained in a Catalogue definition. Some holes and negative primitives can be exported. Refer to Transferring Holes for further information.\nThe Description attribute will be used to store the flooring type, such as grating or chequer plate. This is passed as the type field (up to 24 characters).\nThe Material Grade transferred represents the material type. This is a text attribute, rather than the number field in the base product. Therefore a User Defined Attribute (UDA), :FABMGRADE, has been defined within the base product to store this information.\nA basic series of tests is performed before the Plate is exported.\nIf any of the above criteria is not satisfied, the plate does not get exported in the output file.\nOnce the Plate has been output, the relevant UDAs specific for the interface associated with Export are updated. These are principally the element's internal ID and the UUID numbers and transfer and revision numbers.\nAlthough both plates and holes are supposed to have a clockwise definition (right hand screw rule) for their boundaries in either the base product or in the file, the interface must be able to cope with either clockwise or anti clockwise directions. In exporting plates the vertex order is converted to satisfy the right-hand screw rule.\nPlates with curved and straight segments to their boundaries can be transferred both to and from the base product. Because of the difference between the base product and boundary definitions, vertices will stand a high chance of being created in different places. Further, in order to recreate the shape, there may be a different number of vertices in the boundary. This makes it very difficult to compare the boundaries, especially on import.\nIn order to assist the transfer of these complex shapes, the vertices are given a type code as a design parameter. The code indicates whether the following boundary segment is straight, an arc, or whether the vertex is a created one not contained in the AVEVA Bocad Steel Interface file.\nIs there any geometry?\nIs the height valid?\nIs it justified correctly?\nDoes it have a valid material?\nAre there enough vertices?\nIs there any geometry?\nIs there any geometry?\nIs the height valid?\nIs the height valid?\nIs it justified correctly?\nIs it justified correctly?\nDoes it have a valid material?\nDoes it have a valid material?\nAre there enough vertices?\nAre there enough vertices?\nNote:\nAny edge preparation details and modelling, such as grinding, will be lost in the transfer operation.\nNote:\nThis has an effect on the subsequent import process as the plate will appear to have been deleted by AVEVA Bocad Steel since its export. In fact, the plate never made the transfer in the first place.\nNote:\nImporting a Plate previously defined in base product, you may find the order of vertices to have been reversed.\n\n\n\nTransferring Holes\n\nTransferring Holes\nNote:\nNote:\nNote:"}
{"Headers": "Circular Plates", "Content": "Circular plates in the base product are identified by the number of vertices, the geometry and possibly the vertex type codes. There is no short-hand definition of a circular plate in the base product. As a result, a certain amount of geometric testing is involved in identifying and exporting circular plates. The interface recognizes only 4 or 5 point circles, where the 5th point is a duplicate of the first point.\n\n\n"}
{"Headers": "Error and Log File Messages", "Content": "No geometry information - not exported\nNo PLOO element. Plate cannot be exported.\nPlate too thin -\nnot exported\nThickness less than user defined minimum. Plate not exported.\nNot enough vertices -\nnot exported\nFewer than 3 vertices. Cannot define valid geometry so Plate is not exported.\nNo material information - not exported\nCannot determine material properties for member. A matching set of :FABMGRADE and Matref cannot be determined.\nNo material match for nnnn\nUnknown material. :FABMGRADE cannot be matched with a material in the Properties database.\nNo material property match\nAs above\nInconsistent material\nspecification\nThe element's MATR and :FABMGRADE attributes are not consistent.\nMultiply defined entries in\nMaterial Table\nEither a material to be mapped or a mapped profile appears more than once in the material mapping file.\nNo match for material\nThe material is not in the material mapping file.\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThis should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.\nProblem exporting entity\nOther errors found.\nNo geometry information - not exported\nNo PLOO element. Plate cannot be exported.\nPlate too thin -\nnot exported\nThickness less than user defined minimum. Plate not exported.\nNot enough vertices -\nnot exported\nFewer than 3 vertices. Cannot define valid geometry so Plate is not exported.\nNo material information - not exported\nCannot determine material properties for member. A matching set of :FABMGRADE and Matref cannot be determined.\nNo material match for nnnn\nUnknown material. :FABMGRADE cannot be matched with a material in the Properties database.\nNo material property match\nAs above\nInconsistent material\nspecification\nThe element's MATR and :FABMGRADE attributes are not consistent.\nMultiply defined entries in\nMaterial Table\nEither a material to be mapped or a mapped profile appears more than once in the material mapping file.\nNo match for material\nThe material is not in the material mapping file.\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThis should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.\nProblem exporting entity\nOther errors found.\n\nNo geometry information - not exported\nNo PLOO element. Plate cannot be exported.\nPlate too thin -\nnot exported\nThickness less than user defined minimum. Plate not exported.\nNot enough vertices -\nnot exported\nFewer than 3 vertices. Cannot define valid geometry so Plate is not exported.\nNo material information - not exported\nCannot determine material properties for member. A matching set of :FABMGRADE and Matref cannot be determined.\nNo material match for nnnn\nUnknown material. :FABMGRADE cannot be matched with a material in the Properties database.\nNo material property match\nAs above\nInconsistent material\nspecification\nThe element's MATR and :FABMGRADE attributes are not consistent.\nMultiply defined entries in\nMaterial Table\nEither a material to be mapped or a mapped profile appears more than once in the material mapping file.\nNo match for material\nThe material is not in the material mapping file.\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThis should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.\nProblem exporting entity\nOther errors found.\n\n\n\nNo geometry information - not exported\nPlate too thin -\nnot exported\nNot enough vertices -\nnot exported\nNo material information - not exported\nNo material match for nnnn\nNo material property match\nInconsistent material\nspecification\nMultiply defined entries in\nMaterial Table\nNo match for material\nSyntax Error\nUn\ned Parse State\nProblem exporting entity"}
{"Headers": "Transferring Holes", "Content": "There is a limitation as to which holes are exported. Only secondary PLOO boundaries and NXTR elements can be handled as well as NBOX and NCYL under certain conditions. PLOOs are full depth penetrations: partial penetrations can be modelled using NXTR elements. Circular boundaries of holes and indentations can be imported and exported if recognized as such, by having 4 unique fillet vertices.\nOn import vertices in boundaries are given a DESP value according to the list below.\n      \n         \n            \n               \n                  PVTLastPoint\n                \n               \n                  0\n                \n            \n            \n               \n                  PVTStraight\n                \n               \n                  1\n                \n            \n            \n               \n                  PVTArc\n                \n               \n                  2\n                \n            \n            \n               \n                  PVTFillet\n                \n               \n                  3\n                \n            \n            \n               \n                  PVTCircle\n                \n               \n                  4\n                \n            \n         \n      \n   \nUsing these values specific shapes, such as circles, ellipses, ., can be detected.\nA message is output when the export process ignores most non loop-based negative primitives. This is because it is difficult to determine the geometric intersection with the PANEL, especially if the primitive axis is not perpendicular to the plate plane. In the future it may be possible to handle more of them, but only within tight geometrical constraints. Negative boxes and cylinders could be transferred only if a principal axis is parallel to the plate's normal. This means that the cylinder's Z-axis, and any of the box's X, Y or Z-axis must be parallel to the plate normal. We even have to limit NXTR elements those with an extrusion vector parallel to the panel plane normal. Some negatives are not exported at all:\n(NBOX)\nNPOLYH\n(NCYL)\nNSLC\nNSno\nNDIS\nNCON\nNPYR\nNCTO\nNRTO\n(NXTR)\nNREV\n(NBOX)\nNPOLYH\n(NCYL)\nNSLC\nNSno\nNDIS\nNCON\nNPYR\nNCTO\nNRTO\n(NXTR)\nNREV\n\n\n\nImported holes will be either NXTR or PLOO elements. A full penetration will be a PLOO, and a partial penetration will be an NXTR.\nAny other negatives will not be compared or merged on import. Other pre-existing negatives will be just moved and updated to maintain their original position and orientation.\n         \n            \n               \n                  PVTLastPoint\n                \n               \n                  0\n                \n            \n            \n               \n                  PVTStraight\n                \n               \n                  1\n                \n            \n            \n               \n                  PVTArc\n                \n               \n                  2\n                \n            \n            \n               \n                  PVTFillet\n                \n               \n                  3\n                \n            \n            \n               \n                  PVTCircle\n                \n               \n                  4\n                \n            \n         \n      \n(NBOX)\nNPOLYH\n(NCYL)\nNSLC\nNSno\nNDIS\nNCON\nNPYR\nNCTO\nNRTO\n(NXTR)\nNREV\n      \n         \n            \n               \n                  PVTLastPoint\n                \n               \n                  0\n                \n            \n            \n               \n                  PVTStraight\n                \n               \n                  1\n                \n            \n            \n               \n                  PVTArc\n                \n               \n                  2\n                \n            \n            \n               \n                  PVTFillet\n                \n               \n                  3\n                \n            \n            \n               \n                  PVTCircle\n                \n               \n                  4\n                \n            \n         \n      \n   \nPVTLastPoint\n0\nPVTStraight\n1\nPVTArc\n2\nPVTFillet\n3\nPVTCircle\n4\n\n\n"}
{"Headers": "The use of SAVEWORK on Export and Import", "Content": "In order for the AVEVA Bocad Steel Interface, and more specifically the AVEVA Bocad Steel program, to be able to detect model changes, the interface needs to manage modification dates and times. These values are stored in the database as text strings, based on the last recorded Dabacon model modification date and time. For us to then save these dates and times we need to lock the changes in with a SAVEWORK. This implies some significant time difference between setting a text string attribute and the SAVEWORK. This time difference is model size dependent. We compare the database modification times with the time stored on the attribute with a 5 minute time buffer in order to determine, to the best of our ability, whether an element has been changed.\nImporting does not do a SAVEWORK by itself, but because of this, there can become some significant time difference between the import, modification and database dates and times. Import, creation and modification dates and times are passed through the ABS file, but these can be significantly different from the Dabacon date and time.\nOverall, this will make it difficult to compare models purely on dates and times.\n\n\n"}
{"Headers": "Import from AVEVA Bocad Steel", "Content": "Minimizing changes to the database on Import are not as critical because we are changing the model anyway. However, only elements that are new or modified will have the Import date/time values set. Elements that are identical between the exiting model and the incoming model will not be affected. If necessary, the Modification and Creation date/time values are taken from the ABS file. Again, to minimize the time difference a database SAVEWORK is executed as soon as possible after the model import and merge. However, for large models, the time difference between Importing and SAVEWORK can be significant.\nThe critical time interval in this process is the time taken to compare and merge the models. This is also affected by the response time of the user to the screen prompt asking whether to proceed with the import process. f he should go for a coffee during the import, and come back to see the screen prompt, OK to Merge? all this time will be accumulated in the import process.\n\n\n\nOK to Merge?"}
{"Headers": "AVEVA Everything3D", "Content": "Use the ABSI - Import window to import a steel structure from an AVEVA Bocad Steel Interface file.\n\nA Warning window may be displayed stating mapping files are not found, this means local versions have not been set up, use the default set provided with the product.\n\n\n\nABSI -\nImport\nWarning"}
{"Headers": "Mapping Files", "Content": "Click Mapping files to display the ABSI - Import mapping files window populated with information about the mapping files that will be used in the Import process.\n\nThe interface requires at least two external mapping tables to enable the interface to check that the base product can accept the data. It also may use the internal Profile Orientation and/or the Unicode mapping table if necessary. The mapping tables are for the Profiles, Materials, Unicode text string and for mapping the Profile orientations between the AVEVA Bocad Steel Interface file and the AVEVA steel catalogue. The section Customize explains how you can arrange these files on the file system and what format they are to be. The interface also needs to know where the external mapping files are located on your computer network. For this internal mapping tables are required. Refer to Customize which explains how you can configure the interface to let it know where all the files are located.\nYou can have a generic set of mapping tables to map between the base product and AVEVA Bocad Steel. Or you can have a set for a particular steel fabricator.\nThe current file settings are indicated on this window.\nThe system also checks that these files are compatible with AVEVA Bocad Steel by checking only the identification line at the top of each mapping table. Refer to Internal Mapping Files for further information about the format of these mapping files.\nThe two main options are Auto and Manual which are activated by selecting the appropriate radio button on the left hand side of the Import mapping files window.\nThe Auto option causes the interface to select automatically the mapping tables for AVEVA Bocad Steel, according to the system configuration files. When you come to execute the Import process, the Auto flag will cause the correct mapping files to be used based on the Input file header.\nThe Manual option activates other buttons, which are initially greyed out for the System option. Selecting this option changes the window to be similar to below.\n\nYou can select the file type using the Profiles, Materials or Unicode radio buttons above the text data entry field and enter the full path name of the file in the data entry area. You can also include system environment variables in the path name as long as they are in the proper base product format, for example: %ENVVAR% being the representation of the ENVVAR environment variable.\nOn clicking carriage return, the interface will check for existence of the file and its compatibility with AVEVA Bocad Steel.\nYou can choose by hand which mapping file to use by either entering its name in the text data entry field, or by using the Browse option to bring up a File Browser. Use this browser to search for the relevant mapping file.\nOnce all the correct data has been entered on the Import mapping files window, click OK and it updates the interface variables. Click Cancel to close the window, leaving the original interface variables unchanged.\nNote:\nDo not be concerned that the path name may be truncated by the insertion of the ellipsis (\u2026): it is modified only for display purposes on the window.\nNote:\nThe check is only that the file applies to AVEVA Bocad Steel and not that it is a correct file type or that its contents are correctly formatted.\n\n\n\nCustomize\nCustomize\nInternal Mapping Files\nMapping files\nABSI -\nImport mapping files\nCustomize\nCustomize\nNote:\nInternal Mapping Files\nImport mapping files\nUnicode\nNote:\nImport mapping files"}
{"Headers": "Error and Log File Messages", "Content": "Internal error\nInternal lists are not in step.\nCannot find suitable\ninternal mapping list\nInternal mapping files not found.\nSuitable Mapping Table File not found\nMapping table found is not correct or it does not exist.\nNot a suitable Mapping\nTable File\nIncorrect format of file, or empty file.\nBad Map File\nMapping file is not correct format. Possibly it is from another operating system.\nError on File Browser window\nYou has entered incorrect data on the file browser.\nInternal error\nInternal lists are not in step.\nCannot find suitable\ninternal mapping list\nInternal mapping files not found.\nSuitable Mapping Table File not found\nMapping table found is not correct or it does not exist.\nNot a suitable Mapping\nTable File\nIncorrect format of file, or empty file.\nBad Map File\nMapping file is not correct format. Possibly it is from another operating system.\nError on File Browser window\nYou has entered incorrect data on the file browser.\n\nInternal error\nInternal lists are not in step.\nCannot find suitable\ninternal mapping list\nInternal mapping files not found.\nSuitable Mapping Table File not found\nMapping table found is not correct or it does not exist.\nNot a suitable Mapping\nTable File\nIncorrect format of file, or empty file.\nBad Map File\nMapping file is not correct format. Possibly it is from another operating system.\nError on File Browser window\nYou has entered incorrect data on the file browser.\n\n\n\nInternal error\nCannot find suitable\ninternal mapping list\nSuitable Mapping Table File not found\nNot a suitable Mapping\nTable File\nBad Map File\nError on File Browser window"}
{"Headers": "Import Information", "Content": "From the Import window, click Import Information to display the Import Information window which is populated with information about the import process.\n\nYou either types the full folder path name of the input file, or clicks Browse to bring up a File Browser. The interface tests to see if the file exists and if it does not you will be warned. As well as testing for the existence of the file, it is also tested for being a valid file by inspection of its header details.\nOn reading the file header information the interface will attempt to select a suitable header. If one does not exist you will be asked whether to create one for the import. If you want to override the recommended header element, it will be checked for compatibility.\nYou can view the header information of the chosen input file, click Inspect, to display the Input File Header Details from window with which you can determine whether the file is the correct one to Import.\nFrom the Attributes page, you can see what user data is being transferred from AVEVA Bocad Steel.\n\n\nUse the check boxes on the Import Information window, to select whether to import Linear Members and/or Plates or Holes.\nOnce all the correct data has been entered on the Import Information window, click OK and the interface variables updates. Click Cancel to close the window, leaving the original interface variables unchanged.\nNote:\nIf you do not enter the full path name, the input file is assumed to be in the folder from which started the base product. You can also include system environment variables in the path name as long as they are in the proper base product format, for example. %ENVVAR% being the base product representation of the ENVVAR environment variable.\n\n\n\nImport\nImport Information\nImport Information\nNote:\nInput File Header Details from\nAttributes\nImport Information\nHoles\nImport Information"}
{"Headers": "Error and Log File Messages", "Content": "Import file does not exist\nFile specified does not exist.\nNot an ABSI File\nFile specified is not an ABSI file. This may also arise if the file you are inspecting has been transferred across hardware platforms.\nNothing to import\nYou deselect everything.\nImport file does not exist\nFile specified does not exist.\nNot an ABSI File\nFile specified is not an ABSI file. This may also arise if the file you are inspecting has been transferred across hardware platforms.\nNothing to import\nYou deselect everything.\n\nImport file does not exist\nFile specified does not exist.\nNot an ABSI File\nFile specified is not an ABSI file. This may also arise if the file you are inspecting has been transferred across hardware platforms.\nNothing to import\nYou deselect everything.\n\n\n\nImport file does not exist\nNot an ABSI File\nNothing to import"}
{"Headers": "Import User Data", "Content": "When a user selects a file to import from AVEVA Bocad Steel, the file can be inspected to see what additional data is being transferred.\n\nFrom this window, you can see what data is being considered for transfer, the selected check boxes show what data will actually be transferred. There is also a field for a description of the data.\nOnce imported into PDMS, the data will be stored in UDAs, the numerical values will be stored in a real array, :FABRADATA. The text strings will be stored in an individual text UDA, :FABTADATA to :FABTEDATA. The index of these will direct you to the correct location.\nNote:\nImporting and exporting are two separate operations. The user data exported might have no correlation to the user data being imported. It is information that the receiver of the transfer file might find useful, once imported, you can use the data.\n\n\n\nNote:"}
{"Headers": "Run Information", "Content": "From the Import window, click Run Information to display the Import Run Information window. The window allows you to view the Log File after the import process is complete by clicking the Log File? check box.\n\nClick either the Brief or Verbose radio buttons you can choose which format messages are displayed, the detail of these messages is given elsewhere.\nAs part of the Import process a reference model is constructed against which comparisons will be made. Save Reference Model allows you to keep this. Otherwise it will be deleted on completion of the Import process.\nAfter the Import merging process has been performed, you can sort all new items into FRMW (Framework) elements according to their Material type. This option is selected by clicking the Sort on Material Type option.\nDuring the Import process, comparisons are made for Linear Members and Plates between the existing model data and the imported model data. The default system configuration compares all the relevant data transferred in the file between the models. However, you can select which attributes may be ignored by the comparison process by clicking Edit Attribute Comparison List to display the Comparison Checklist window.\n\nUse this window to deselect attributes for comparison but be aware that strange results may occur especially if you ignore positional and rotational attributes.\nFinally, there are two validity checks you can perform on the incoming data which will make sure a subsequent Import run will have a chance of success. Activating these options overrides completely the Import choices made on the main window. With these validity checks you will be able to see a log file before any data is merged whatsoever.\nProfile Mapping? enables you to see if the incoming Linear Member Profile specifications will be successfully mapped between systems. This is a relatively fast transaction as the file is just passed through the external program without any subsequent import or comparison in the base product. You will then be able to see the log file produced and take appropriate action.\nThere is a risk in either package that entity UUIDs may be duplicated. The Duplicate UUID selector gadget enables you to check for duplicate UUIDs in the incoming model. There are three options: NONE, NEW and GLOBAL. NONE deactivates the gadget and no checks are made. The import process just goes through unhindered. The NEW option allows you to check only the new imported items for duplicate UUIDs, while the GLOBAL option enables you to search all the available databases for duplicate UUIDs. Obviously these searches may involve a certain amount of time, but for the sake of validity, they would be worth using.\nOnce all the correct data has been entered on the Run Information window, click OK and the interface variables updates. Click Cancel to close the window, leaving the original interface variables unchanged\nNote:\nThis reference model will be deleted next time you Exports or Imports anything. It is only transient data. Also, it may not be a complete model as some items may already have been transferred into the main model on merging.\n\n\n\nImport\nRun Information\nImport Run Information\nLog File?\nBrief\nVerbose\nNote:\nComparison Checklist\nUUID\nRun Information"}
{"Headers": "Members and Operations", "Content": "On the Import window the Members list can be used to navigate around the database hierarchy.\nYou must state where the Imported model is to be located. This must be a SITE, ZONE or STRU element. Using the Members list, navigate round the database to the correct storage location and click Store in: CE. The window text indicates where the Imported model will reside. If there is not enough space on the window, the SITE's reference number is output rather than its name.\nThe Import process is essentially a three phase operation. First a reference model is built which is then compared with the original model identified during the Store in: CE operation. Then, if required, the changes, additions and deletions encountered in the comparison phase are transferred to the actual model. Thus, using the Operations toggles, you can control how the Import process is to proceed.\nYou should be aware of how the model manages partial model transfers and where temporarily imported data goes before it is merged into the pre-existing model. See the sections describing the Import, Comparison and Merging processes.\nCompare + Merge\nGoes through the complete Import process - that is the import, comparison and merging are all completed without any interaction with you. This is only to be performed if you are absolutely sure that they will get the desired result.\nCompare ( + Merge )\nImports the model and compare the reference model with the location chosen to be the storage area. At this point you will be asked whether to merge the models. Click Yes to continue with the merge process and complete the Import.\nMerge from File\nTakes a merge command file produced during the current session only and imports it directly into the model. The reference model must not have been deleted beforehand. Otherwise, you may lose any elements added to the model by AVEVA Bocad Steel. This is a very quick option and there are no checks, except what you want to do it.\nCompare + Merge\nGoes through the complete Import process - that is the import, comparison and merging are all completed without any interaction with you. This is only to be performed if you are absolutely sure that they will get the desired result.\nCompare ( + Merge )\nImports the model and compare the reference model with the location chosen to be the storage area. At this point you will be asked whether to merge the models. Click Yes to continue with the merge process and complete the Import.\nMerge from File\nTakes a merge command file produced during the current session only and imports it directly into the model. The reference model must not have been deleted beforehand. Otherwise, you may lose any elements added to the model by AVEVA Bocad Steel. This is a very quick option and there are no checks, except what you want to do it.\n\nCompare + Merge\nGoes through the complete Import process - that is the import, comparison and merging are all completed without any interaction with you. This is only to be performed if you are absolutely sure that they will get the desired result.\nCompare ( + Merge )\nImports the model and compare the reference model with the location chosen to be the storage area. At this point you will be asked whether to merge the models. Click Yes to continue with the merge process and complete the Import.\nMerge from File\nTakes a merge command file produced during the current session only and imports it directly into the model. The reference model must not have been deleted beforehand. Otherwise, you may lose any elements added to the model by AVEVA Bocad Steel. This is a very quick option and there are no checks, except what you want to do it.\nNote:\nThese options may be completely overridden if you want to perform a validity check as on the Run Information window.\n\n\n\nImport\nNote:\nRun Information\nYes"}
{"Headers": "Error and Log File Messages", "Content": "Bad element type\nYou is not trying to store imported data at a SITE, ZONE or STRU element.\nBad element type\nYou is not trying to store imported data at a SITE, ZONE or STRU element.\n\nBad element type\nYou is not trying to store imported data at a SITE, ZONE or STRU element.\n\n\n\nBad element type"}
{"Headers": "Import and Cancel", "Content": "Cancel closes the Import window.\nImport executes the Import process. As it proceeds you are kept informed of the progress.\n\n\n\nImport"}
{"Headers": "Import Bar Menu", "Content": "The Control drop-down menu has four options; Re-initialize, Configure, Map Convertor and Exit. Changing any mapping files or any other variables:\nThe General drop-down menu has two options, Highlight and Clear ABSI History. Highlight displays the Highlighter window enabling you to identify new, changed and deleted items in the model. This has more relevance to the Import process, refer to Highlighting Changes in the Design for further information. Clear ABSI History enables one to clear the import/export history on the current element and all elements below that have date and time UDAs that are relevant to the AVEVA Bocad Steel Interface.\nRe-initialize reloads files to save you having to rebuild the whole user interface from scratch\nConfigure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information\nMap Convertor starts the tool that helps you to rebuild Profile mapping files.\nExit removes all forms and menus and global variables associated with the interface.\nRe-initialize reloads files to save you having to rebuild the whole user interface from scratch\nRe-initialize reloads files to save you having to rebuild the whole user interface from scratch\nConfigure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information\nConfigure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information\nMap Convertor starts the tool that helps you to rebuild Profile mapping files.\nMap Convertor starts the tool that helps you to rebuild Profile mapping files.\nExit removes all forms and menus and global variables associated with the interface.\nExit removes all forms and menus and global variables associated with the interface.\n\n\n\nSystem Configuration\nHighlighting Changes in the Design\nControl\nRe-\ne\nConfigure, Map Convertor and\nExit\nRe-\ne\nConfigure\nSystem Configuration\nMap Convertor\nExit\nGeneral\nHighlight\nClear ABSI\nHistory\nHighlight\nHighlighter\nHighlighting Changes in the Design\nClear ABSI History"}
{"Headers": "Import Process", "Content": "After clicking OK the fields in the window are checked for validity:\nAfter verifying that all the data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. This waiting time is user configurable. If there are errors raised by the external program you are notified and more detailed information is placed in the log file. If the waiting period expires without the interface detecting that the external program has completed - it may have crashed, or not even exist. You will be asked if want to carry on waiting for another time unit.\n\nClick Yes and the interface will wait for another period of time. Click No causes the interface to stop where it is. Finally the system will indicate its completion, whether successful or not. This completion message should be read in conjunction with the log file, if any errors are indicated.\nYou will be alerted to unsuccessful runs by the external program displaying an Error window, after which the process exits.\n\nIf the external program successfully completes, the processed file will be imported into the design model. Any reference data which may have been retained by you before will have been deleted beforehand.\nThe status line will inform you of the progress on importing the data, the length of the input macro is about 25 times the number of elements. Thus a file transferring 300 members is about 7500 lines long. This calculation can be useful when considering the maximum input file size. The size applies to this file and not to the original SDNF source file.\nAfter the Import of everything, the material properties are reconciled with the :FABMGRADE attribute and, if possible, the MATR is also set to point to the appropriate property in the Properties database.\nAt this point, if you have chosen to be asked whether to Merge after the Compare operation, Confirm window is displayed.\n\nClick Yes and the interface continues with the Merge process.\nClick No and the Import process skips the Merging, but you are then given a chance to store the Merging commands in a file for use later on only in the current base product session. You cannot use a file from a previous session as the Import data may be incorrect.\n\nYou can save the Merge command file and then be prompted whether to see the Import log file. This Merge command file may then be used in the Merge from File option on the Import window. This latter option needs the reference model from this run to be kept. Therefore, you do not have the option below.\nIf you have merged the models, they will then be asked if they want to keep the reference model, verifying the option selected on the Run Information window.\n\nFinally, you are asked whether to view the log file, if they have chosen that option on the Run Information window.\n\nIf you want to inspect the log file, they can then save it with the File > Save as option in the File Viewer window which will bring up a File Browser, or by clicking Save as to the suggested filename. If the file exists, you will be asked whether they want to overwrite it. The log file window can then be closed by clicking Cancel.\n\nIf you have chosen Brief mode on the Run Information window for displaying the log file, the window displaying the log file will filter out all Warning messages, leaving only the Error messages. To save the log file, however, all messages will be retained in the file.\nClicking on a line containing a base product reference number causes all graphical views to zoom in to the chosen item and to identify it. The interface also navigates to the item in the database and leave you there to perform any queries or operations.\nIs the storage location valid?\nIs there a valid input file?\nDo we need to convert the file across platforms?\nAre the Profile and Material mapping files valid?\nIs the storage location valid?\nIs the storage location valid?\nIs there a valid input file?\nIs there a valid input file?\nDo we need to convert the file across platforms?\nDo we need to convert the file across platforms?\nAre the Profile and Material mapping files valid?\nAre the Profile and Material mapping files valid?\nNote:\nThis reference model will not be the complete model as imported as various attributes and elements might have been modified, deleted or moved around.\n\n\n\nOK\nYes\nNo\nbase product\nImport\nRun Information\nNote:\nRun Information\nFile Viewer\nRun Information"}
{"Headers": "Error and Log File Messages", "Content": "File does not exist\nSomehow there is no log file Are there issues regarding access rights to your work folder?\nInput file name not\nspecified\nSomething strange here. The name of the input command file generated has been forgotten.\nImport file does not exist\nSomething strange here. The input command file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to your work folder?\nData store unset\nThe data store variable is unset or the SITE you have intended to store the imported data in is invalid. Has it been deleted since you set the store variable?\nFile does not exist\nSomehow there is no log file Are there issues regarding access rights to your work folder?\nInput file name not\nspecified\nSomething strange here. The name of the input command file generated has been forgotten.\nImport file does not exist\nSomething strange here. The input command file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to your work folder?\nData store unset\nThe data store variable is unset or the SITE you have intended to store the imported data in is invalid. Has it been deleted since you set the store variable?\n\nFile does not exist\nSomehow there is no log file Are there issues regarding access rights to your work folder?\nInput file name not\nspecified\nSomething strange here. The name of the input command file generated has been forgotten.\nImport file does not exist\nSomething strange here. The input command file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to your work folder?\nData store unset\nThe data store variable is unset or the SITE you have intended to store the imported data in is invalid. Has it been deleted since you set the store variable?\n\n\n\nFile does not exist\nInput file name not\nspecified\nImport file does not exist\nData store unset"}
{"Headers": "Comparison and Merging Processes", "Content": "The Import, Comparison and Merge process involves three stages. First, the model is imported. You then has the option of comparing the imported model with the original model, after which they may merge the new data into the old model, or the comparison and merge process can be performed as one with no user interaction. Although you can tell the system to Import, Compare and Merge the model straight away this should only be performed if you are sure of the end result. It is advised that you compare the models first and then inspect the results before merging.\nYou can decide to keep the imported reference model as has been described above - but is warned that this is only to be regarded as transitory information. It may also not be a complete representation of the data imported as some of it will get transferred to the real design area.\nIf the target area is empty, the Compare/Merge processes are bypassed which can be a lot faster when importing large amounts of data.\n\n\n"}
{"Headers": "The Comparison Process", "Content": "There are three conditions the interface looks for:\nThe fact that an item is in the imported file and not in the original model is indicative of one of two cases: that the item has indeed been added by AVEVA Bocad Steel; or that the item was never exported in the first place for some reason. This latter case might also occur if the original model has had items added to it since the export happened. Further, items may appear to have been deleted and their \"clones\" imported when the import store location is not the same as it was for the export process.\nBelow is a diagram illustrating the route through which the data is imported, compared and merged. New items are green, changed items are orange and deleted items are red.\n\nIt is clear from the above diagram that the interface supports partial model transfer as it just identifies those new or changed items. Anything indicated as deleted is more an indication that the item is not present in the Imported file. It is not deleted from the Original Model during the Merge process: \"Deleted\" items are simply moved to another SITE to enable you to recover them if necessary. So parts of models can be merged into the original model with no loss of data.\nThe Comparison process allows any potential changes, additions and deletions to the original model to be detected and shown in a 3D Volume View window, if there is one present and if the items are in the current Drawlist.\nAs for both Linear Members and Plates you can select which attributes are significant for Comparison. This is performed using the Comparison Checklist window which is a child of the Import Run Information window. By default, all the attributes transferred through the file are compared.\nitems in the imported file that are not in the original model - Added items;\nitems in the original model that are not in the imported file - Deleted items;\nitems that it can match between the imported file and the original model and checks for modifications - Changed items.\nitems in the imported file that are not in the original model - Added items;\nitems in the imported file that are not in the original model - Added items;\nitems in the original model that are not in the imported file - Deleted items;\nitems in the original model that are not in the imported file - Deleted items;\nitems that it can match between the imported file and the original model and checks for modifications - Changed items.\nitems that it can match between the imported file and the original model and checks for modifications - Changed items.\nNote:\nThe Reference Model which is created is named according to your session, so that several user Reference Models could coexist at the same time. As they are named according to session, you are advised to take care to manage them and not to leave too many versions around to fill up your disk space.\n\n\n\nAdded\nDeleted\nChanged\nNote:\nImport Run Information"}
{"Headers": "Comparing Linear Members", "Content": "The following data attributes are compared between the original model and the reference model:\nImporting a Linear Member also sets the Import date and time UDAs. On merging members the revision number, transfer number and code are updated.\nThe log file messages recording any differences are of two formats: in Brief mode the results are presented on one line; in Verbose mode you are told what the old value was and the new value is so that they can see how the model has been changed. Refer to Brief Format for further information about the brief log file format.\nYou may get a lot of apparent changes which may be caused by the failure to map the profile types between systems. The log file will indicate which profiles have not been mapped. It is advised that you resolve the Profile Mapping issues first before becoming too concerned with other changes recorded in the log file.\nDuring the Import phase, an attempt is made to map the Cardinal Points in the incoming model with existing Plines that have been mapped onto them.\nStart and end of Pline defined by Cardinal Point\nOrientation and Beta angle\nSpecification Reference\nMaterial grade and reference\nStart and end of Pline defined by Cardinal Point\nStart and end of Pline defined by Cardinal Point\nOrientation and Beta angle\nOrientation and Beta angle\nSpecification Reference\nSpecification Reference\nMaterial grade and reference\nMaterial grade and reference\n\n\n\nBrief Format\nBrief Format"}
{"Headers": "Comparing Plates (PANE)", "Content": "The following data attributes are compared between the original model and the reference model:\nVertex positions are compared to within the user definable tolerance as described in the section on user customization of the interface.\nImporting a Plate also sets the Import date and time UDAs. On merging members the revision number, transfer number and code are updated.\nThe log file messages recording any differences are of two formats: in Brief mode the results are presented on one line; in Verbose mode you are told what the old value was and the new value is so that they can see how the model has been changed. Refer to Brief Format for further information about the brief log file format.\nWe now compare plates with holes as secondary loops (PLOO) or NXTR primitives. We can now merge the imported model including new holes created outside of. However, because of the complexity of the comparison process, it is difficult to compare holes between the original and imported model. Where possible all other negative primitives representing holes in the original model are maintained. Therefore the comparison does not go down to the level of holes.\nPosition, orientation\nMaterial grade and reference\nPanel loop height and justification\nNumber of vertices\nPosition, orientation\nPosition, orientation\nMaterial grade and reference\nMaterial grade and reference\nPanel loop height and justification\nPanel loop height and justification\nNumber of vertices\nNumber of vertices\nNote:\nIn Exporting a Plate, it has to be converted to the standard of being defined in a clockwise direction relative to the plane normal. Thus Importing a Plate previously defined in the base product you may find the order of vertices to have been reversed. This is because the base product is more tolerant about the ways in which you can define a plate.\n\n\n\nBrief Format\nBrief Format\nNote:"}
{"Headers": "The Merging Process", "Content": "Refer to diagram in Comparison and Merging Processes illustrating the route by which information is transferred from the Import, through the Comparison and on to the Merging processes.\nThe interface manages the Comparison and Merging of imported models so that other important engineering data is not lost or overwritten. However, other data, including connectivity may be lost.\nYou can separate the Comparison and Merging processes, so that they are able to view the log file in between operations. If you choose the Merge from File option on the main Import window, the Comparison process is deemed to have been completed and so all that remains to be done is the actual Merging. This is why the reference model for the current session must still be available, you will be prompted for confirmation.\n\nIf, during the Merge phase, items are to be merged, the lists of added and deleted items are reconciled with the original model - by being deleted or transferred from reference model. The storage SITE header details are then merged with the information in the header.\nAfter the main model Merging has been completed, if you have chosen the Sort on Material Type option on the Import window, any new items will be sorted into FRMW groups according to their material type as specified by the :FABMGRADE attribute.\nThe version numbering system is described below, in Technical Information.\n\n\n\nComparison and Merging Processes\nTechnical Information\nComparison and Merging Processes\nImport\nImport\nTechnical Information"}
{"Headers": "Additional Items", "Content": "Items added to the model are recorded as such; they are indicated by changing their colour, a suitable message is output to the log file and they are then transferred to a special area. Merging will transfer all the added items from the reference model to the original model. If required, they are then sorted according to material type.\nThe new items are gathered together into a site whose name is constructed from the Transfer and Revision Numbers so that you can easily locate all items added at a specific version or date.\nFor example, a new STRU may be created with the name of /FAB-NEW-DEMO-SYSTEM/A.1 under the container element as specified in the Store in: field on the Import window. The components of this name are as follows:\nthe system prefix\nidentification of new element container\nthe current MDB, for example: /DEMO\nthe current user name, for example: SYSTEM\nthe current Transfer letter, for example: 'A'\nthe current revision number, for example: '1'\nYou would thus be able to find all the added items to this MDB at this version.\n/FAB-\n                  \nthe system prefix\nNEW-\nidentification of new element container\n<mdb name>-\nthe current MDB, for example: /DEMO\n<user name>-/\nthe current user name, for example: SYSTEM\n<transfer nr>.\nthe current Transfer letter, for example: 'A'\n<revision nr>\nthe current revision number, for example: '1'\n\n\n\nImport\n/\nNEW-\n<mdb name>-\n<user name>-/\n<transfer nr>.\n<revision nr>"}
{"Headers": "Deleted Items", "Content": "Deleted items in the model are recorded as deleted during the Compare phase and remain in the reference model to be deleted later if not required. This separation of operations is so that you can see what will be deleted during the Merge process. Before deletion the objects are changed in colour so that they may be identified.\n'Deleted' items are disconnected from the old model and transferred from the current part of the database into a STRU created under the special 'Deleted' SITE.\nAs with the added items, the STRU is named out of components, thereby enabling you to determine at which version items may have been removed from the model.\nFor example, a new STRU may be created with the name of /FAB-OLD-DEMO-SYSTEM/A.1 under the special SITE /FAB-OLD-DEMO-SYSTEM. The components of this name are as follows:\nthe system prefix\nidentification of new element container\nthe current MDB, for example: /DEMO\nthe current user name, for example: SYSTEM\nthe current Transfer letter, for example: 'A'\nthe current revision number, for example: '1'\nYou would thus be able to find all the 'deleted' items to this MDB at this version.\n/FAB-\nthe system prefix\nOLD-\nidentification of new element container\n<mdb name>-\nthe current MDB, for example: /DEMO\n<user name>-/\nthe current user name, for example: SYSTEM\n<transfer nr>.\nthe current Transfer letter, for example: 'A'\n<revision nr>\nthe current revision number, for example: '1'\nNote:\nAn item is not actually deleted from the original model. The apparent deletion may, in fact, be because the item was never transferred to AVEVA Bocad Steel in the first place due to some reason. Alternatively it may have been created in the base product since the initial Export process had taken place.\n\n\n\nNote:\n/\n-\nOLD-\n<mdb name>-\n<user name>-/\n<transfer nr>.\n<revision nr>"}
{"Headers": "Changed Items", "Content": "In merging plates the interface tries to keep the original vertices as they may have been used for locating dimensions on drawings: it may be that just the positions have been changed. However, the comparison only works in list order: the interface does not look around for another vertex in the same physical place, although it may be in a different list position. Extra unwanted vertices are deleted on merging and all new vertices are added to the end of the list. A totally new Plate is just imported directly.\nNote:\nChanged objects are indicated as such by a change in colour.\n\n\n\nNote:"}
{"Headers": "Error and Warning Messages", "Content": "WARNING: Reference SITE\nnnnn contains transient data\nThe reference SITE is likely to be deleted some time.\nModel comparison\ncompleted\nProcess was successful.\nFailed to compare models\nDo they both exist?\nWARNING: Reference SITE\nnnnn contains transient data\nThe reference SITE is likely to be deleted some time.\nModel comparison\ncompleted\nProcess was successful.\nFailed to compare models\nDo they both exist?\n\nWARNING: Reference SITE\nnnnn contains transient data\nThe reference SITE is likely to be deleted some time.\nModel comparison\ncompleted\nProcess was successful.\nFailed to compare models\nDo they both exist?\n\n\n\nWARNING: Reference SITE\nnnnn contains transient data\nModel comparison\ncompleted\nFailed to compare models"}
{"Headers": "Validation Process", "Content": "As has been described in Comparison and Merging Processes there are two validation checks you can perform prior to the full import and merging of models.\nThe first option is for profile mapping. The Profile Mapping? Option on the Run Information window turns this on. The Import process initializes normally and calls the external program to process the incoming file. In so doing it checks for a complete mapping of the profiles in the mapping tables. A log file is produced. No further Import actions are undertaken with this option.\nSecond, you can check that there are not any duplicate UUIDs. This can quite easily come about if you copy members in AVEVA Bocad Steel without creating unique UUIDs for them. When they are imported into the base product, the Comparison process may fail as it could be uncertain as to which member it is supposed to be comparing.\nThe options for this check are NEW and GLOBAL. NONE turns the facility off. NEW checks among all this run's imported members contained in the reference model for duplicate UUIDs, while GLOBAL checks the whole structural database, both imported and existing elements. These can be quite slow options as the reference model must be created and compared anyway.\nAs this option also calls the external program which checks the mapping of profile names between systems, you will see that the log file may also list any problems with the mapping tables. So this option is actually a combination of this and the previously mentioned validity checking option. For a sample log file, refer to Sample Validity Check Log File for further information.\n\n\n\nComparison and Merging Processes\nSample Validity Check Log File\nComparison and Merging Processes\nRun Information\nSample Validity Check Log File"}
{"Headers": "Highlighting Changes in the Design", "Content": "You can display a Highlighter window from either the Import or Export windows by the General > Highlight menu bar option.\nThe window allows you to identify in a graphical window whatever they want, either according to Import date, or by Transfer/Revision number combinations. The Select by toggle switches the window into the appropriate mode. Both these options work from the start element selected and will indicate only those items that are in the drawlist.\n\n\n\nHighlighter\nImport\nExport"}
{"Headers": "Highlighting by Import Date", "Content": "The window below allows you to choose what to enhance on the screen according to the Import Date of an item.\n\nIn the Selected items box, you can select any combination of Added, Changed, or Deleted Items for identification, according to the date range described below.\nBy selecting the inclusive dates defining the limits of the range using the From and To date selector gadgets you can locate on the screen those items in the current drawlist which have been changed, added or deleted.\nNote:\nAs the 'deleted' elements are relocated in the database after Merging, the area where they are finally located should also be in the drawlist if you want to see what has been 'deleted'.\n\n\n\nNote:"}
{"Headers": "Highlighting by Version", "Content": "The window below allows you to choose what to indicate on the screen according to the Version of an item.\n\nThe functionality available to select changed, deleted or added items is identical to that for highlight by import date, refer to Highlighting by Import Date for further information.\nBy selecting the versions defining the limits of the range using the From and To version selector gadgets you can identify on the screen those items in the current drawlist which have been changed, added or deleted.\nNote:\nAs the 'deleted' elements are relocated in the database after Merging, the area where they are finally located should also be in the drawlist if you want to see what has been 'deleted'.\n\n\n\nHighlighting by Import Date\nHighlighting by Import Date\nNote:"}
{"Headers": "Error and Warning Messages", "Content": "Bad date input\nThe configuration of day, month and year is illegal. Or is the start date after the end date?\nBad version input\nIs the start version after the end version?\nNothing to highlight\nNothing satisfies the selection criteria.\nBad date input\nThe configuration of day, month and year is illegal. Or is the start date after the end date?\nBad version input\nIs the start version after the end version?\nNothing to highlight\nNothing satisfies the selection criteria.\n\nBad date input\nThe configuration of day, month and year is illegal. Or is the start date after the end date?\nBad version input\nIs the start version after the end version?\nNothing to highlight\nNothing satisfies the selection criteria.\n\n\n\nBad date input\nBad version input\nNothing to highlight"}
{"Headers": "Technical Information", "Content": "This section contains technical information which is not immediately specific to Products but of which you should be aware in order to get the best out of the interface.\n\n\n"}
{"Headers": "Recommended File Suffix", "Content": "Although it is not critical for this interface, the recommended suffix for the files is to be abs.\n\n\n"}
{"Headers": "Cardinal Points", "Content": "Below is a diagram illustrating the positions of the Cardinal Points.\nThe Cardinal Point imported should be retained for later export. This is because it is likely to be a source of confusion when a member originally laid out on Cardinal Point 14 (Top of Steel) is returned on the Cardinal Point 10 (Neutral Axis). It will cause minor problems in model versioning and comparisons.\n\n\n\n"}
{"Headers": "Default Orientations", "Content": "There is a neutral definition of the default orientation of profile shapes. This is closely based on the AISC standard.\nBelow is a diagram showing the default orientations of the Catalogue profiles.\n\n\n\n"}
{"Headers": "UDAs", "Content": "This section lists the UDAs defined for this interface, an attempt has been made to keep the unique abbreviation to 6 characters. The UDAs for this interface are:\n\n\n"}
{"Headers": "General Data", "Content": ":FABID/ATE\nTEXT\n30\nSCTN PANE GENSEC\nDate of Import\n:FABIT/IME\nTEXT\n30\nSCTN PANE GENSEC\nTime of Import\n:FABRE/VNO\nINT\n1\nSITE ZONE STRU SCTN PANE GENSEC\nRevision Nr (0)\n:FABTRA/NO\nINT\n1\nSITE ZONE STRU SCTN PANE GENSEC\nTransfer index(1)\n:FABTRR/VNO\nTEXT\n10\nSITE ZONE STRU SCTN PANE GENSEC\nRevision Text\n:FABEX/CLUDE\nLOG\n1\nSCTN PANE SJOI PJOI GENSEC\nExclude flag (f)\n:FABSTA/TUS\nTEXT\n10\nSCTN PANE GENSEC\nStatus text\n:FABCD/ATE\nTEXT\n30\nSCTN PANE GENSEC\nDate of Creation\n:FABMD/ATE\nTEXT\n30\nSCTN PANE GENSEC\nDate of Modification\n:FABCT/IME\nTEXT\n30\nSCTN PANE GENSEC\nTime of Creation\n:FABMT/IME\nTEXT\n30\nSCTN PANE GENSEC\nTime of Modification\n\nName\nType\nLen\nOn\nDescription\n:FABID/ATE\nTEXT\n30\nSCTN PANE GENSEC\nDate of Import\n:FABIT/IME\nTEXT\n30\nSCTN PANE GENSEC\nTime of Import\n:FABRE/VNO\nINT\n1\nSITE ZONE STRU SCTN PANE GENSEC\nRevision Nr (0)\n:FABTRA/NO\nINT\n1\nSITE ZONE STRU SCTN PANE GENSEC\nTransfer index(1)\n:FABTRR/VNO\nTEXT\n10\nSITE ZONE STRU SCTN PANE GENSEC\nRevision Text\n:FABEX/CLUDE\nLOG\n1\nSCTN PANE SJOI PJOI GENSEC\nExclude flag (f)\n:FABSTA/TUS\nTEXT\n10\nSCTN PANE GENSEC\nStatus text\n:FABCD/ATE\nTEXT\n30\nSCTN PANE GENSEC\nDate of Creation\n:FABMD/ATE\nTEXT\n30\nSCTN PANE GENSEC\nDate of Modification\n:FABCT/IME\nTEXT\n30\nSCTN PANE GENSEC\nTime of Creation\n:FABMT/IME\nTEXT\n30\nSCTN PANE GENSEC\nTime of Modification\n\n\n"}
{"Headers": "Structural Data", "Content": ":FABMG/RADE\nTEXT\n24\nSCTN PANE GENSEC\nMaterial Grade\n:FABMA/RK\nTEXT\n24\nSCTN PANE GENSEC\nInternal ID\n:FABEMA/RK\nTEXT\n24\nSCTN PANE GENSEC\nExternal UUID\n:FABPMARK\nTEXT\n24\nSCTN GENSEC PANE\nPiece Mark\n:FABSHPCOD\nTEXT\n30\nSCTN GENSEC\nProfile Shape Code\n:FABTYPE\nTEXT\n24\nSCTN GENSEC PANE\nMember Type\n:FABBOCPRF\nTEXT\n30\nSCTN GENSEC\nBocad Profile Type\n\nName\nType\nLen\nOn\nDescription\n:FABMG/RADE\nTEXT\n24\nSCTN PANE GENSEC\nMaterial Grade\n:FABMA/RK\nTEXT\n24\nSCTN PANE GENSEC\nInternal ID\n:FABEMA/RK\nTEXT\n24\nSCTN PANE GENSEC\nExternal UUID\n:FABPMARK\nTEXT\n24\nSCTN GENSEC PANE\nPiece Mark\n:FABSHPCOD\nTEXT\n30\nSCTN GENSEC\nProfile Shape Code\n:FABTYPE\nTEXT\n24\nSCTN GENSEC PANE\nMember Type\n:FABBOCPRF\nTEXT\n30\nSCTN GENSEC\nBocad Profile Type\n\n\n"}
{"Headers": "Project Data", "Content": ":FABEF/ID\nTEXT\n80\nSITE ZONE STRU\n'Engineering Firm Id'\n:FABCL/ID\nTEXT\n80\nSITE ZONE STRU\n'Client Id'\n:FABSTI/D\nTEXT\n80\nSITE ZONE STRU\n'Structure Id'\n:FABPR/ID\nTEXT\n80\nSITE ZONE STRU\n'Project Id'\n:FABMO/DNR\nINT\n1\nSITE ZONE STRU SCTN PANE GENSEC\nModel Number\n:FABDE/CODE\nTEXT\n80\nSITE ZONE STRU\n'Design Code'\n:FABSO/URCE\nTEXT\n64\nSITE ZONE STRU\nData Source\n:FABTA/RGET\nTEXT\n64\nSITE ZONE STRU\nTarget Contractor\n:FABID/ATE\nTEXT\n30\nSITE ZONE STRU\nDate of Import\n:FABIT/IME\nTEXT\n30\nSITE ZONE STRU\nTime of Import\n:FABEXCLUDE is a flag you can set on the items indicated. It is using this flag that you can control what is exported to the output file. By default the flag is false, that is the item is not excluded from the Export process.\n:FABEMARK is the external UUID (Universal Unique Identifier) item. If the item originated in the base product then this value will be the AVEVA database reference number with the leading equals sign, '=', removed.\n:FABMARK is the AVEVA internal database reference number. It may not be the same as :FABEMARK if the entity originated in AVEVA Bocad Steel.\n:FABSTATUS is used to give you a view of the current status of the element. It has four different settings: to signify the item originated in the base product; ADDED indicates that the item has been added to the model externally, by Merging; CHANGED means that the item has been modified externally; and DELETED means that the item was in the original design model but has not returned from the external model. This last case may occur for one of several reasons. The item may not have been exported in the first place; it may have been added after the model was exported or it was deleted by the external system for some reason.\nName\nType\nLen\nOn\nDescription/default\n:FABEF/ID\nTEXT\n80\nSITE ZONE STRU\n'Engineering Firm Id'\n:FABCL/ID\nTEXT\n80\nSITE ZONE STRU\n'Client Id'\n:FABSTI/D\nTEXT\n80\nSITE ZONE STRU\n'Structure Id'\n:FABPR/ID\nTEXT\n80\nSITE ZONE STRU\n'Project Id'\n:FABMO/DNR\nINT\n1\nSITE ZONE STRU SCTN PANE GENSEC\nModel Number\n:FABDE/CODE\nTEXT\n80\nSITE ZONE STRU\n'Design Code'\n:FABSO/URCE\nTEXT\n64\nSITE ZONE STRU\nData Source\n:FABTA/RGET\nTEXT\n64\nSITE ZONE STRU\nTarget Contractor\n:FABID/ATE\nTEXT\n30\nSITE ZONE STRU\nDate of Import\n:FABIT/IME\nTEXT\n30\nSITE ZONE STRU\nTime of Import\n\n\n"}
{"Headers": "Updating the UDAs", "Content": "This interface version has some additional UDAs that must be added in Lexicon. Running the interface. Run bocudaupgrade.pmlfnc in Lexicon to install them.\n\n\n"}
{"Headers": "Cross Referencing Models", "Content": "Cross referencing models is the mechanism by which you can identify members in different models other than by visual comparison. There are two scenarios: one where an element is created in the base product; the other is where it was created in AVEVA Bocad Steel, but is to be imported into the base product.\n\n\n"}
{"Headers": "Element Created in the Base Product", "Content": "When an element is created in the base product it gains a unique internal reference number of the form \"=<integer>/<integer>\", for example: =13/2305. On export from the base product this value, excluding the initial '=' character, will be passed through the UUID fields. AVEVA Bocad Steel will take this value and store it, and use it to allow the user of AVEVA Bocad Steel to identify the original member. On Export back to the base product, for any member which has this UUID attribute set, the original imported UUID will be returned. Thus a user of the base product will be able to spot any changes to the model. The Import system, then allows you to modify the existing structure, rather than just replacing it with a copy. In this way, any drawings, for example, which may have been produced between Export from and Import back to the base product, will retain their logical relationships to the steel members.\n\n\n\nmodify\nreplacing"}
{"Headers": "Element Created outside the Base Product", "Content": "A member created outside the base product will not have the UUID field set to be an internal reference number. The AVEVA Bocad Steel Interface would therefore know that it was importing a new element and would create it accordingly, whilst recording the external UUID as well.\nIf AVEVA Bocad Steel Interface detects that there are duplicate external UUIDs as it is preparing to export a model, the internal reference number is used in preference. This should give some chance of identifying the element if it returns from the external package. See the section regarding issues concerning entity comparison.\n\n\n"}
{"Headers": "Cross Database Working", "Content": "The base product has the ability to split the design model across several databases, some of which may be read only.\nExporting the model tries to update certain variables associated with the version management. However, if the database is read only, a macro file is produced that should be executed immediately as soon as you have write access to the database.\nThe file name is built upon the string \"updateVersionNos\" but with time stamp information attached so that they can be executed in chronological sequence. An example file name might be \"updateVersionNos201312593744.mac\", which was created at 09:37:44 on 25th January 2013.\nImporting an existing, though modified, model is more difficult. Obviously you must have write access to the database. The reference site is created in the same database as the target area specified on the Import window. This allows new items to be transferred between the reference site and the target site using the INCLUDE command.\nYou should make sure that the incoming data is not to be spread across databases.\nIf the target area is empty the Compare/Merge processes are bypassed which can be a lot faster when importing large amounts of data.\nUsers of multi-write databases need to be aware that elements that are to be exported must be claimed out prior to export. All elements that are likely to be affected by importing must also be claimed out.\nImportant:\nThis must be performed before any further import procedures are performed.\n\n\n\nImportant:\nImport"}
{"Headers": "Transfer of Curved Members", "Content": "Imported curved segments will be GENSECs and new straight segments will also be GENSECs. However, if merging with an existing model and the interface can identify the source member that was originally a SCTN, it will remain a SCTN.\nComparing GENSECs is only down to the point count level on the spine. The actual point attributes are not investigated, except for the start and end points. If there are the same numbers of POINSP and CURVE members respectively these are checked. Any alteration to these numbers will indicate changes. They must be inspected visually for comparisons. The re-imported CURVE element are likely to have changed because we only import 1 type - a THRU point, although there are 6 or 7 different types of CURVE points in the base product, each with different attribute combinations.\n\n\n"}
{"Headers": "Version Numbering", "Content": "The management of the attributes relevant to version numbering and revision control, that is :FABREVNO, :FABTRANO and :FABTRRVNO, is all performed in the base product user interface. The values of these attributes are not taken from the file. The header is used to transfer the main TransferLetter from the Configuration object, but the individual items are managed as described below.\nThe Configuration object should not be confused with the Header object. The former is used to store transfer indices - counts of Transfer Numbers and Revision numbers. These are for the whole database. The latter is used to store specific information pertaining to the transfer in question - for example: client information.\nBecause of the fact that the base product may be multi-user and that several user\u2019s may be concurrently accessing the design databases at any one time, there may be several Configuration objects, one for each possible MDB:User combination. At the start of the Export or Import process, a poll is taken of ALL these Configuration objects to determine which is the highwater mark. That is, which is the highest Transfer Number, or Revision Number. We then take that and modify the Configuration object for the current MDB:User. In this way, by polling all objects, we can determine the latest values.\nThe rules of precedence for the Transfer and Revision numbers are that a Transfer is higher. So that \"A.2\" is later than \"A.1\" and \"B.1\" is later than \"A.9\".\nIf there are more than 26 Transfers, the letter is recycled so that there may be slight problems at the wrap around.\nBelow are the rules by which the revision numbering is handled by the interface.\nEach Transfer has a Letter - A...Z\nEach Revision has a Number - 1,2,3...\nEach SITE, GENSEC, SCTN and PANE has 3 UDAs attached\nA TransferLetter for example: 'C',\nA RevisionNumber for example: '2'\nEach Transfer has a Letter - A...Z\nEach Transfer has a Letter - A...Z\nEach Revision has a Number - 1,2,3...\nEach Revision has a Number - 1,2,3...\nEach SITE, GENSEC, SCTN and PANE has 3 UDAs attached\nEach SITE, GENSEC, SCTN and PANE has 3 UDAs attached\nA TransferLetter for example: 'C',\nA TransferLetter for example: 'C',\nA RevisionNumber for example: '2'\nA RevisionNumber for example: '2'\nNote:\nThe UDA, :FABTRANO, is actually an index into a character string returning the equivalent character as the TransferLetter.\nNote:\nThis TransferLetter is cycled. As it passes 'Z' it will be succeeded by 'A'.\n\n\n\nNote:\nNote:"}
{"Headers": "On Transfer into the Base Product", "Content": "If an entity (SCTN, GENSEC or PANE) has been changed or is new, set its TransferLetter to be that of the owning SITE and note that there is at least 1 changed item.\nUpdate the entity's (SCTN, GENSEC or PANE) RevisionNumber to be the incremented value of that of the owning SITE, because we haven't yet changed the latter.\nIncrement the SITE's RevisionNumber, for example: '0' to '1' if any imported entities have changed.\nIf an entity (SCTN, GENSEC or PANE) has been changed or is new, set its TransferLetter to be that of the owning SITE and note that there is at least 1 changed item.\nIf an entity (SCTN, GENSEC or PANE) has been changed or is new, set its TransferLetter to be that of the owning SITE and note that there is at least 1 changed item.\nUpdate the entity's (SCTN, GENSEC or PANE) RevisionNumber to be the incremented value of that of the owning SITE, because we haven't yet changed the latter.\nUpdate the entity's (SCTN, GENSEC or PANE) RevisionNumber to be the incremented value of that of the owning SITE, because we haven't yet changed the latter.\nIncrement the SITE's RevisionNumber, for example: '0' to '1' if any imported entities have changed.\nIncrement the SITE's RevisionNumber, for example: '0' to '1' if any imported entities have changed.\n\n\n"}
{"Headers": "Exclusions", "Content": "This section lists the exclusions which have been identified.\nPenetration Holes\nThe interface does not allow the description of holes within Linear Members.\nTemplates\nCatalogu are not covered by Linear members and Plates contained in Templates or Groups will be transferred on export. There is no facility for constructing a new Template or Group on import. Elements that are in pre-existing Templates or Groups will be compared and merged, but new elements will not be placed in the same container.\nNon-prismatic end details\nLinear members in the current interface exchange format cannot describe any details at member/cleat ends apart from full orthogonal cuts. Hence, all sloped cuts, notches, . will be approximated from minimum to maximum local longitudinal co-ordinate, which should be conservative regarding clash detection. The interface only transfers fully prismatic Plates. Hence, the Plate cuts/intersections which are not fully orthogonal to the Plate's local plane cannot be transferred. Such Plates will be exported 'uncut', which again should be conservative for clash detection.\n\n\n"}
{"Headers": "Issues", "Content": "The interface allows only for the transfer of a character descriptor for a Profile. For a successful data transfer, there will need to be co-ordination between users of each package to make sure that the geometric description associated with the catalogue name is identical and that there is a means of correlation between the packages.\nIn the base product, the structural model may contain two views of the data: one view defined by logical connectivity by references to the connecting items; and the physical view defined by the relative location of items. So, while we may logically relate two items, they may not necessarily be physically close to each other. Thus, transferring the model will necessarily involve the loss of real connectivity information which will be difficult to reconstitute correctly on Import.\nThe interface will output a warning message when sections are met which cannot be handled or are unexpected.\nThe double quote character \" in text fields, particularly in profile names is not allowed. This can cause problems with imperial sized items in the catalogue that use the character to indicate inches. It is not allowed in ANY text fields.\n\n\n"}
{"Headers": "Units", "Content": "This is a statement of how the interface handles units.\nThe AVEVA Bocad Steel Interface attempts to keep the behaviour of the system as consistent as possible across versions of the base product. Holes are always imported as NXTR elements because the interface does not do any shape recognition. This highlights a possible issue in exporting a model and re-importing. While a secondary PLOO would represent a hole, this would have to be represented on import as a negative extrusion, NXTR. So round tripping data will cause secondary PLOO elements as well as other negative primitives, to be converted to NXTR elements.\nWhen importing into an empty area and using the \"Import linear members as GENSECs\" option, straight members may not be converted to GENSECS. This often occurs with a file that was previously exported from another base product model. The UUID attribute on the imported element may refer to an element with the same database reference number in the current model. Do not use the option to convert all straight members into GENSECs when importing a file containing elements that originated in the base product.\n\n\n"}
{"Headers": "Stairs, Ladders and Handrailing", "Content": "Certain components of Stairs, Ladders and Handrailing (SLH) will be transferred in the application. These are the GENSEC, SCTN, PANE, RAIL and KICKPL. Any of these elements that are directly or indirectly referenced, such as in templates, will be transferred. However, catalogue components themselves will not be transferred. Further, certain advanced detailing features of the handrailing, such as gaps might not be transferred.\nBecause of the nature of SLH, round-tripping of the data is difficult as it is challenging to reconstruct the complex data structures.\nIn detail, the treatment of SLH is as follows:\n\n\n"}
{"Headers": "ABSI Export of SLH - Stairs Ladders & Handrail", "Content": "Only valid in AVEVA E3D 2.1\u2122\nOnly Detailed Mode Stairs' Ladders & Handrail will be exported. (Not Model Mode)\nCatalogue based components will not be exported (For example: A Catalogue based Post, or Rung or Tread and so on).\nOnly valid in AVEVA E3D 2.1\u2122\nOnly valid in AVEVA E3D 2.1\u2122\nOnly Detailed Mode Stairs' Ladders & Handrail will be exported. (Not Model Mode)\nOnly Detailed Mode Stairs' Ladders & Handrail will be exported. (Not Model Mode)\nCatalogue based components will not be exported (For example: A Catalogue based Post, or Rung or Tread and so on).\nCatalogue based components will not be exported (For example: A Catalogue based Post, or Rung or Tread and so on).\n\n\n"}
{"Headers": "Stairs", "Content": "Stringers, Treads, and Extensions (STRSTR, TREAD, TOPEXT, BOTEXT) - Can contain GENSEC and PANEL elements / Templates (TMPL). All GENSEC and PANEL elements will be exported as any other Curved Linear Member or Planar Member.\nStringers, Treads, and Extensions (STRSTR, TREAD, TOPEXT, BOTEXT) - Can contain GENSEC and PANEL elements / Templates (TMPL). All GENSEC and PANEL elements will be exported as any other Curved Linear Member or Planar Member.\nStringers, Treads, and Extensions (STRSTR, TREAD, TOPEXT, BOTEXT) - Can contain GENSEC and PANEL elements / Templates (TMPL). All GENSEC and PANEL elements will be exported as any other Curved Linear Member or Planar Member.\n\n\n"}
{"Headers": "Ladders", "Content": "Rungs, Stiles, Hoops, Cage Bars, Gates (LDRRNG, LDRSTR, HOOPSE, RLCAGE, RLGATE) - Can contain GENSEC and PANEL elements / Templates (TMPL). All GENSEC and PANEL elements will be exported as any other Curved Linear Member or Planar Member.\nRungs, Stiles, Hoops, Cage Bars, Gates (LDRRNG, LDRSTR, HOOPSE, RLCAGE, RLGATE) - Can contain GENSEC and PANEL elements / Templates (TMPL). All GENSEC and PANEL elements will be exported as any other Curved Linear Member or Planar Member.\nRungs, Stiles, Hoops, Cage Bars, Gates (LDRRNG, LDRSTR, HOOPSE, RLCAGE, RLGATE) - Can contain GENSEC and PANEL elements / Templates (TMPL). All GENSEC and PANEL elements will be exported as any other Curved Linear Member or Planar Member.\n\n\n"}
{"Headers": "Handrails", "Content": "Rails (RAIL) - exported as Curved Linear Members\nKick Plates (KICKPL) - exported as Curved Linear Members\nPosts, Panels, Gates and Terminations (HRPOST, HRPANE, HRGATE, HRTERM) - Can contain GENSEC and PANEL elements / Templates (TMPL). All GENSEC and PANEL elements will be exported as any other Curved Linear Member or Planar Member.\nRails (RAIL) - exported as Curved Linear Members\nRails (RAIL) - exported as Curved Linear Members\nKick Plates (KICKPL) - exported as Curved Linear Members\nKick Plates (KICKPL) - exported as Curved Linear Members\nPosts, Panels, Gates and Terminations (HRPOST, HRPANE, HRGATE, HRTERM) - Can contain GENSEC and PANEL elements / Templates (TMPL). All GENSEC and PANEL elements will be exported as any other Curved Linear Member or Planar Member.\nPosts, Panels, Gates and Terminations (HRPOST, HRPANE, HRGATE, HRTERM) - Can contain GENSEC and PANEL elements / Templates (TMPL). All GENSEC and PANEL elements will be exported as any other Curved Linear Member or Planar Member.\n\n\n"}
{"Headers": "Import Log Files", "Content": "In order to minimize the size of log files, especially when large models are being compared you can ask the interface to output Verbose or Brief log files.\n\n\n"}
{"Headers": "Brief Format", "Content": "In Brief log files, details of the comparison will be condensed onto a single line per item. This will be in the form of the following:\n\n\n"}
{"Headers": "Linear Members", "Content": "Linear members are either straight or curved. Modifications to straight members are detailed as below\nLINMEM <ID> <state> <point> <size> <material> <rotation> <start> <end>\nfor example:\nLINMEM =1234/5678 C Y Y Y N Y Y\nThe ID field will contain the internal database reference number by which the model components are to be identified between model versions. The state field may contain one of three options, A for added, D for deleted or C for changed. The other fields contain either a Y or N indicating whether the attribute at that location has been changed or not.\nFor curved members the member type is CURMEM but the attributes inspected for comparison are the same. The individual internal points along the SPINE are not compared.\n\n\n\nID\nA\nD\nC\nY\nN"}
{"Headers": "Plates", "Content": "PLATE <ID> <state> <point> <height> <material> <pos> <ori> <vertexCount> <changedVertex>\nThe rules for values in each of the above fields are as for the Linear Members.\nNote that holes themselves are not compared. This is principally because the transfer is incomplete anyway. The interface only transfers PLOO and NXTR based penetrations. No other negative primitives can be transferred at the moment.\nBelow is a sample portion of log file in brief format following an Import:\n\n\n\nAll profiles were mapped\nThe following profiles were not in the specified standards\nHP200x54 has                    1 occurrences\nAll mapped profiles were in the default standard\n======================================\nLINMEM =15322/447 C   Y   N   Y   N   N   N\nLINMEM =15322/448 C   Y   N   Y   N   N   N\nLINMEM =15322/449 C   N   N   Y   N   N   N\nLINMEM =15322/450 C   Y   N   Y   N   N   N\nLINMEM =15322/451 C   Y   N   N   Y   N   N   N\nPLATE  =15322/1015 C   N   N   N   N   Y   N   Y\nPLATE  =15322/1104 C   N   N   N   Y   N   N   Y\nPLATE  =15322/296 C   N   N   N   Y   Y   N   Y\nPLATE  =15322/414 C   N   N   N   Y   Y   N   Y\nPLATE  =15322/598 C   N   N   N   N   Y   N   Y\nPLATE  =15322/722 C   N   N   N   N   Y   N   Y\nLINMEM =15322/423 D   N   N   N   N   N   N   N\nLINMEM =15322/878 D   N   N   N   N   N   N   N\nPLATE  =15322/553 D   N   N   N   N   N   N   N"}
{"Headers": "Verbose Format", "Content": "In Verbose log files, full details of the comparison will be listed.\nBelow is a portion of verbose log file of the same Import as above:\n\n\n\nCHANGES to mapped entities in /TEST-INTERFACE\nGENSEC =15322/447 in /TEST-INTERFACE\n     Rotation 'S 57.2932 D WRT /*' changed from 'N 57.2932 U WRT /*'\n     Just 'TOAY' changed from 'TOAX'\nGENSEC =15322/448 in /TEST-INTERFACE\n     Rotation 'N 57.3314 D WRT /*' changed from 'S 57.3314 U WRT /*'\n     Just 'TOAY' changed from 'TOAX'\nGENSEC =15322/449 in /TEST-INTERFACE\n     Rotation 'E WRT /*' changed from 'W WRT /*'\nGENSEC =15322/450 in /TEST-INTERFACE\n     Rotation 'S 32.925 D WRT /*' changed from 'N 32.925 U WRT /*'\n     Just 'TOAY' changed from 'TOAX'\n PANE =15322/1015 in /TEST-INTERFACE\n     Ori 'Y is E 0.053013 D WRT /* and Z is W 19.7106 N 89.9437 D WRT /*' changed\n         from 'Y is W 0.053 U WRT /* and Z is E 19.721 S 89.9437 U WRT /*'\n     Vertex 1 'E 134350.001 N 179399.999 U 104251.185 WRT /*' changed from 'E 137050\n         N 179400 U 104248.687 WRT /*'\n     Vertex 2 'E 134350.001 N 181874.999 U 104252.005 WRT /*' changed from 'E 134350.001\n         N 179399.999 U 104251.185 WRT /*'\n     Vertex 3 'E 134575.001 N 181874.999 U 104251.797 WRT /*' changed from 'E 134350.001\n         N 181874.999 U 104252.005 WRT /*'\n     Vertex 4 'E 134575.001 N 182099.999 U 104251.872 WRT /*' changed from 'E 134575.001\n         N 181874.999 U 104251.797 WRT /*'\n     Vertex 5 'E 137050 N 182100 U 104249.582 WRT /*' changed from 'E 134575.001 N\n         182099.999 U 104251.872 WRT /*'\n     Vertex 6 'E 137050 N 179400 U 104248.687 WRT /*' changed from 'E 137050 N 182100\n         U 104249.582 WRT /*'\n PANE =15322/1104 in /TEST-INTERFACE\n   Position 'E 144350 N 169625 U 104250 WRT /*' changed from 'E 144450 N 172000 U\n         104250 WRT /*'\n     Vertex 1 'E 144350 N 172100 U 104250 WRT /*' changed from 'E 144350 N 169625\n         U 104250 WRT /*'\n     Vertex 2 'E 147050 N 172100 U 104250 WRT /*' changed from 'E 144350 N 172100\n         U 104250 WRT /*'\n     Vertex 3 'E 147050 N 169400 U 104250 WRT /*' changed from 'E 147050 N 172100\n         U 104250 WRT /*'\n     Vertex 4 'E 144575 N 169400 U 104250 WRT /*' changed from 'E 147050 N 169400\n         U 104250 WRT /*'\n     Vertex 5 'E 144575 N 169625 U 104250 WRT /*' changed from 'E 144575 N 169400\n         U 104250 WRT /*'\n     Vertex 6 'E 144350 N 169625 U 104250 WRT /*' changed from 'E 144575 N 169625\n         U 104250 WRT /*'\n===========================\nCHANGES >>>> 70 detected\nADDITIONS to mapped entities in /TEST-INTERFACE\n===========================\nADDITIONS >>>> 0 detected\nDELETIONS to mapped entities in /TEST-INTERFACE\n LINMEM =15322/423 has been deleted.\n LINMEM =15322/878 has been deleted.\n PLATE  =15322/553 has been deleted.\n===========================\nDELETIONS >>>> 3 detected"}
{"Headers": "Sample Validity Check Log File", "Content": "The Sample Validity Check log file displays shows a sample portion of a log file from an Import validity checking process to check for duplicate mark numbers.\n\n\n"}
{"Headers": "Environment", "Content": "This section describes the system architecture, the relationship between internal and external mappings, mappings files and overloading mapping files.\n\n\n"}
{"Headers": "System Architecture", "Content": "The diagram below illustrates the whole AVEVA Bocad Steel Interface system architecture.\n\n\n\n"}
{"Headers": "Mapping Files", "Content": "There are two types of mapping files: internal and external mapping files.\nInternal mapping files are prepared by the system administrator. They tell the interface where on the computer network the external mapping files may be found. The format of the internal mapping files is described in Internal Mapping Files.\nExternal mapping files are files which determine how the interface handles the data for going to or coming from AVEVA Bocad Steel; for example, the Profile, Unicode and Material mapping files. The format of the external mapping files is described in External Mapping Files.\n\n\n\nInternal Mapping Files\nExternal Mapping Files\nInternal mapping files\nInternal Mapping Files\nExternal mapping files\nExternal Mapping Files"}
{"Headers": "Overloading Mapping Files", "Content": "Overloading of mapping files is permitted and may occur. This means that a file that is found in the first folder will be overwritten by a file with the same identifying characteristics, though not necessarily with the same filename (Internal Mapping Files), found later in any of the succeeding folders. For example, a project mapping file could overload a company mapping file.\nThe sequence of environment variables is set to the locations of the internal mapping files. The interface will search all the folders pointed to by these variables and locate all files with the suffix .map in each sub-folder called BocadMaps. The .map files will be imported during system initialization as internal mapping files. The internal mapping files then become the basis for locating the external mapping files.\nHowever, this does not alter the search rules for the external mapping files as based on the content of the identification line in the internal mapping file.\nThe diagram below illustrates how these environment variables may be used to select and overload sets of internal mapping files.\n\nYou does not have to use all three defaults variables.\n\n\n\nInternal Mapping Files\nInternal Mapping Files\n.map\nBocadMaps\n.map"}
{"Headers": "Relationship between Internal and External Mapping Files", "Content": "For the purposes of this section, the variable BOCDATA is assumed to have been set up in your system initialization process to point to the folder containing the external mapping files.\nThe environment variable BOCDATA should point to a single folder only. This variable may be made to be project specific, so that the internal mapping files may be kept unchanged, but you will be able to pick up mapping files from a project-specific location.\n\nYou should take care in using environment variables in internal mapping files, as a recursive scan is not performed at this level. In this case the variable must point to only one folder.\nNote:\nBOCMAPS is not a variable specifically required by this interface.\n\n\n\nNote:"}
{"Headers": "Upgrading a Project", "Content": "After you have set the appropriate environment variables, some upgrade macros must be run on the project which:\nUpdate catalogues to include the Pline representation of the Cardinal Points.\nInstall the UDAs which requires.\nUpdate catalogues to include the Pline representation of the Cardinal Points.\nUpdate catalogues to include the Pline representation of the Cardinal Points.\nInstall the UDAs which requires.\nInstall the UDAs which requires.\nNote:\nThis process can be repeated as the supplied software performs the correct checks to see whether the project needs updating.\n\n\n\nNote:"}
{"Headers": "Cardinal Point Plines", "Content": "The standard AVEVA Solutions Limited steelwork catalogue at AVEVA E3D 2.1\u2122 2.1 is already compatible with SDNF. Older catalogues, and user catalogues might need to be upgraded to include the Pline representations of the SDNF Cardinal Points. Refer to Cardinal Points for further information.\nYou may upgrade the catalogues by performing the following actions:\nThere are 15 Cardinal Points defined in the AVEVA Bocad Steel Interface. The interface uses only 14 of them. Of the remaining Cardinal Points the interface tries to use those between 1 and 10.\nIf you have not used Plines representing Cardinal Points to place Linear Members in the base product, during the Export or Import processes an attempt is made to map existing Plines onto Cardinal Points.\nThis mapping is performed using information stored in a configuration file, bocloadcpdata.pmlfnc in the PMLLIB\\Bocad\\functions folder in the installation folder. This basic Pline mapping for the old (that is pre AVEVA E3D 2.1\u2122 2.1) structural catalogue and the new AVEVA E3D 2.1\u2122 2.1 supplied catalogue are as follows:\nNote:\nThis upgrade process works only for the supplied catalogues. Further, it only works on the old British, American and DIN catalogues, to upgrade them to the new Plines. The mechanism should be easily extended to include other supplied catalogues. Upgrading user catalogues is described elsewhere.\n\n\n\nNote:\nbocloadcpdata.pmlfnc\nPMLLIB\\Bocad\\functions"}
{"Headers": "Symmetric Sections about Y Axis", "Content": "For symmetrical profiles in the new catalogue, which are symmetrical about the Y axis, the Plines below are mapped to Cardinal Points. It might appear confusing, but the left/right relationship depends on how you look at the profile - in the same direction as the profile vector, or against it.\nLBOT\n\n3\nCBOT\n\n2\nRBOT\n\n1\nLMID\n\n6\nCMID\n\n5\nRMID\n\n4\nLTOP\n\n9\nCTOP\n\n8\nRTOP\n\n7\nNA\n\n10\nBNA\n\n11\nLNA\n\n13\nRNA\n\n12\nTNA\n\n14\nFor angle and channel profiles in the new catalogue the Pline mapping is as follows. This difference is principally because of the SDNF definition of the default profile orientation.\nLBOT\n\n1\nCBOT\n\n2\nRBOT\n\n3\nLMID\n\n4\nCMID\n\n5\nRMID\n\n6\nLTOP\n\n7\nCTOP\n\n8\nRTOP\n\n9\nNA\n\n10\nBNA\n\n11\nLNA\n\n12\nRNA\n\n13\nTNA\n\n14\nFor the old (E3D1.1) catalogue the Plines are mapped as follows. For symmetric sections that are symmetrical about the Y axis. Symmetric Sections about Y Axis\nRBOS\n\nSNFA\n\n1\nBOS\n\nSNFB\n\n2\nSS\n\nSNFB\n\n2\nLBOS\n\nSNFC\n\n3\nRIGH\n\nSNFD\n\n4\nNARO\n\nSNFD\n\n4\nAA\n\nSNFD\n\n4\nMM\n\nSNFF\n\n6\nNALO\n\nSNFF\n\n6\nLEFT\n\nSNFF\n\n6\nRTOS\n\nSNFG\n\n7\nGG\n\nSNFH\n\n8\nTOS\n\nSNFH\n\n8\nLTOS\n\nSNFI\n\n9\nNA\n\nSNFJ\n\n10\n\nPline\nis mapped to\nCardinal Point\nLBOT\n3\nCBOT\n2\nRBOT\n1\nLMID\n6\nCMID\n5\nRMID\n4\nLTOP\n9\nCTOP\n8\nRTOP\n7\nNA\n10\nBNA\n11\nLNA\n13\nRNA\n12\nTNA\n14\nPline\nis mapped to\nCardinal Point\nLBOT\n1\nCBOT\n2\nRBOT\n3\nLMID\n4\nCMID\n5\nRMID\n6\nLTOP\n7\nCTOP\n8\nRTOP\n9\nNA\n10\nBNA\n11\nLNA\n12\nRNA\n13\nTNA\n14\nPline\nmapped to\nPline\nwhich is\nCardinal Point\nRBOS\nSNFA\n1\nBOS\nSNFB\n2\nSS\nSNFB\n2\nLBOS\nSNFC\n3\nRIGH\nSNFD\n4\nNARO\nSNFD\n4\nAA\nSNFD\n4\nMM\nSNFF\n6\nNALO\nSNFF\n6\nLEFT\nSNFF\n6\nRTOS\nSNFG\n7\nGG\nSNFH\n8\nTOS\nSNFH\n8\nLTOS\nSNFI\n9\nNA\nSNFJ\n10\n\n\n\nPline\nPline\nCardinal Point"}
{"Headers": "Angles", "Content": "TOAX\n\nSNFA\n\n1\nTOAY\n\nSNFA\n\n1\nRTTA\n\nSNFC\n\n3\nLBOA\n\nSNFG\n\n7\nNA\n\nSNFJ\n\n10\nNAT\n\nSNFK\n\n11\nNAL\n\nSNFL\n\n12\n\nPline\nmapped to\nPline\nwhich is\nCardinal Point\nTOAX\nSNFA\n1\nTOAY\nSNFA\n1\nRTTA\nSNFC\n3\nLBOA\nSNFG\n7\nNA\nSNFJ\n10\nNAT\nSNFK\n11\nNAL\nSNFL\n12\n\n\n\nPline\nPline\nCardinal Point"}
{"Headers": "Channels", "Content": "LTOC\n\nSNFA\n\n1\nRTOC\n\nSNFC\n\n3\nFOC\n\nSNFD\n\n4\nROC\n\nSNFF\n\n6\nLBOC\n\nSNFG\n\n7\nRBOC\n\nSNFI\n\n9\nNA\n\nSNFJ\n\n10\nTOC\n\nSNFK\n\n11\nBOC\n\nSNFN\n\n14\nFor further explanation of the reasons why the mapping may seem inconsistent, see the section describing the assumed default profile orientations in the file and Cardinal Points locations and the Structural Design User Guide. In particular your attention is drawn to the different handedness of the coordinate systems as illustrated below.\n\nThe main differences arise from the mapping of the profile orientations in the Catalogue onto the agreed format. The difference is most apparent in channel and angle profiles. The diagram below illustrates the mappings of the Plines to Cardinal Points.\n\nIf you want to create profiles, you must provide a Pline set similar to the ones provided here to map onto the Cardinal Point Pline set. If they are named differently, there must be a mapping to Cardinal Points as shown above. Further, you may have to manage the orientation of the profile with regard to the intermediate arrangement by using the Profile Orientation mapping file (External Mapping Files).\nPline\nmapped to\nPline\nwhich is\nCardinal Point\nLTOC\nSNFA\n1\nRTOC\nSNFC\n3\nFOC\nSNFD\n4\nROC\nSNFF\n6\nLBOC\nSNFG\n7\nRBOC\nSNFI\n9\nNA\nSNFJ\n10\nTOC\nSNFK\n11\nBOC\nSNFN\n14\nNote:\nThe different Y directions to match the default angle orientations in each system.\n\n\n\nCardinal Points\nExternal Mapping Files\nPline\nPline\nCardinal Point\nCardinal Points\nNote:\nExternal Mapping Files"}
{"Headers": "Update Catalogs not supplied by AVEVA Solutions Limited", "Content": "The interface tries to find the correct Justification Pline by comparing the positions of their ends and the start and end of the imported member.\nThis section gives details on how you can update the steel catalogues to include the Plines necessary for the interface.\nThe macro file, bocusercataupgr.pmlfnc in the bocad\\dflts\\user\\upgrade folder in your data folder provides the basis on which you may build their own mechanism for updating the catalogues automatically. When the changes are complete you should perform a PML REHASH ALL operation in a command window. We have indicated where you may have to modify this file with lines prefixed by:\nThe macro must be run for each catalogue (CATA element) you want to update. You may have to modify it in a different way for each catalogue. (Details about how the file should be modified are given in following sections.)\nYou can write a macro which will call all the modified files in turn and so upgrade all catalogues at once. The macro takes one argument which is the DBREF (the database reference number) of the catalogue to be updated.\nTo update individual catalogues, run the upgrade macro as follows:\nImportant:\nThe naming conventions and database structure for the Pline sets should be similar to those used in the supplied Catalogues.\n\n\n\nImportant:\nbocusercataupgr.pmlfnc\nbocad\\dflts\\user\\upgrade\nPML REHASH ALL\n\u00bc\ncall !!bocUserCataUpgr( !!CE )"}
{"Headers": "Generic Catalogue Shapes", "Content": "The supplied catalog contains profiles of 7 standard generic shapes which are detailed in the Structural Design User Guide. That manual explains the parameterization method for these shapes. As a result, there are 7 generic macros in the PMLLIB\\bocad\\upgrade folder in the installation folder, one for updating the Pline set of each standard shape. These are:\nTee shape\nbocupgradet.pmlfnc\nI shape\nbocupgradei.pmlfnc\nO, Tube, CHS shape\nbocupgradeo.pmlfnc\nC, Channel shape\nbocupgradec.pmlfnc\nL, Angle shape\nbocupgradel.pmlfnc\nRHS shape\nbocupgraderhs.pmlfnc\nBulb shape\nbocupgradebulb.pmlfnc\nIf you has other additional shapes, or have parameterized them in a different way from the supplied catalogues, you will have to write their own macro for their own shape based on the most suitable one provided. Please take note of the catalogue profile orientation with regard to the format.\n\nProfile Shape\nMacro\nTee shape\nbocupgradet.pmlfnc\nI shape\nbocupgradei.pmlfnc\nO, Tube, CHS shape\nbocupgradeo.pmlfnc\nC, Channel shape\nbocupgradec.pmlfnc\nL, Angle shape\nbocupgradel.pmlfnc\nRHS shape\nbocupgraderhs.pmlfnc\nBulb shape\nbocupgradebulb.pmlfnc\n\n\n"}
{"Headers": "Customize the Pline Generating Macros", "Content": "In order to customize the generic Pline generating macros listed above, or to create their own, you will need to understand fully how the profile in question is parameterized in their catalogue database, and how the profile shape is positioned relative to the Neutral Axis and the X/Y origin in the catalogue.\nThe structure of all the supplied macros is similar.\nThe macro first builds a list of any Plines that already exist. Any Plines that are not available and are needed by the AVEVA Bocad Steel Interface as listed in the !!BOCCPPKeys array, are then created. Doing this makes sure the latest configuration is being used.\nWe then need to define the Cardinal Point Pline location parameters related to the method of catalogue parameterization. These are Xoff, YOff, nYOff and nXOff. We also need to work out the location of the geometric centre relative to the method of profile definition. These location parameters are XCOff and YCOff. You will see above that the definition is in terms of a text string which describes a formula. Later on in the macro, this text string is inserted into the command line. This use of PML allows you to insert formulae into the Pline definition, rather than the immediately evaluated formula.\nUsing these Pline location parameters, all the Cardinal Point Plines required for the application can be located. Refer to Cardinal Points for further information.\nIf you are extending or modifying the application, all you need to do is to modify the part of the macro which calculates the location parameters. You should, however, pay close attention to the default profile orientations within AVEVA Bocad Steel Interface.\nThe structure of the upgrade process allows you to run the macro during the project as well as at project initiation. Any database relationships that refer to the old Plines will be maintained, for example, dimensions.\n\n\n\nCardinal Points\nCardinal Points"}
{"Headers": "Map Pline Set Names to Profile Shapes", "Content": "Once you have defined their generic shapes you need to be able to map the Pline set names to that shape. This is done by filling in a mapping file of PML objects in the bocusercataupgr.pmlfnc macro file. The first set in the UserMap array may have to be modified, and you may have to extend the list for their own additional specific shapes.\nFor example, a complete mapping for a Pline set consists of the following:\nThis means that the Pline set (PTSS) named /USER-PTSS-I is to be modified using the PML macro represented by the variable !Ishape.\nFurther up, you can see that the !IShape variable is associated with the macro !!bocUpgradeI( ). The args value is true or false depending on whether the catalogue to be updated is based on the old or new catalogues. This is most important when considering C or L shaped profiles where the orientations change.\n  -- Map Shapes to generic update macros\n    !TShape             = |!!BOCUpgradeT|\n    !IShape             = |!!BOCUpgradeI|\n    !OShape             = |!!BOCUpgradeO|\n    !CShape             = |!!BOCUpgradeC|\n    !LShape             = |!!BOCUpgradeL|\n    !RHSShape           = |!!BOCUpgradeRHS|\n    !BULBShape         = |!!BOCUpgradeBULB|\n-- >>>> User to add any specific shapes here\n--    !USERAShape         = |!!BOCUpgradeUSERA|\n  -- >>>> User Map definition between PTSS and Shape code\n    !UserMap = ARRAY\n    !UserMap[ 1 ]         = object BOCMAPOBJ\n    !UserMap[ 1 ].Name   = |/USER-PTSS-I|\n    !UserMap[ 1 ].Macro   = !IShape\n    !UserMap[ 1 ].Args   = |(false)|\n\n\n\nbocusercataupgr.pmlfnc"}
{"Headers": "Catalog Upgrade Step-by-Step", "Content": "Below are instructions to create and upgrade the Catalogue based on the requirement to create a new profile shape in both the base product and AVEVA Bocad Steel. Any operations that require changes to system mapping files or PML macro files, should be preceded by backing up the files first.\n\n\n"}
{"Headers": "New Profile Shape Definition", "Content": "Create the new 2D profile shape. Determine the generic shape and parameterization best suited to the required profile.\nAt this point do not include Cardinal Point Plines in the Pline set, just place other Plines you will find useful and name them accordingly. Do not include any Plines with the special PKEY values as these will be added in the upgrade process. Build the new catalogue, recording which parameters apply to which dimension.\nIn AVEVA Bocad Steel create the profile such that its default orientation will be the same as that in the base product when laid out from start to end.\nWith predefined profiles, such as unequal angles, the default orientation may be different. In this case, you may need to use mirroring and/or rotation transformations to get to the correct \"starting position\". Mirroring represents a transformation about the Y axis: rotation is about the Z axis, following the \"Right Hand Screw Rule\". Keep a record of these necessary transformations as they will go into the orientation mapping file.\nOn the 2D profile in each package locate where the Cardinal Points and their Pline equivalents will be. In the PARAGON module, place any other Plines that you may find useful. Record the correspondence between Cardinal Points and Pline names. Remember also that any mirroring and rotation will affect the Cardinal Point locations.\nIf the new profile is not one of the existing shapes, you may need to assign a new profile integer shape code to it for use in the profile mapping file.\nAlso, if the new profiles are for a new country standard, you may need to assign a new country code to this. This country code abbreviation is stored in the internal steel standards file. This abbreviation is also used in the profile mapping file.\nNote:\nThe coordinate system in the base product is right handed, whereas in the neutral file it is left handed. The Cardinal Point : Pline equivalencing by superposition is illustrated above for an unequal angle profile. Using this kind of diagram you will be able to determine the mappings between Plines and Cardinal Points.\n\n\n\nNote:"}
{"Headers": "Upgrade the Catalog for the AVEVA Bocad Steel Interface", "Content": "Upgrading the Catalog involves adding Plines to be equivalent to the Cardinal Points.\nIn Paragon determine the parameterized geometry and Pline positioning for the Cardinal Points.\nIf you are extending an existing generic shape use the existing upgrade file provided. Or if the profile can be based on an existing generic shape, use a customized copy of the bocupgrade<*>.pmlfnc macro. Modify the profile upgrade macro to account for the new parameterization to create and locate the Plines for the Cardinal Points. Use an existing example as a guide.\nRun boccataupgrade.pmlfnc macro for upgrading standard catalogues.\nInspect the macro bocusercataupgr.pmlfnc to extend any lists to include the new profile shape, associating it with any new profile upgrade macro. Once modified, perform a PML REHASH ALL command in a Command window, if necessary, then run this macro.\n!Ishape = |bocupgradei()|\n!UserMap[ 1 ] = object BOCMAPOBJ( )\n!UserMap[ 1 ].Name = |/USER-PTSS-I|\n!UserMap[ 1 ].Macro = !Ishape\n!UserMap[ 1 ].Args = |( false )|\n\n\n\nbocupgrade<*>.pmlfnc\nboccataupgrade.pmlfnc\nbocusercataupgr.pmlfnc\nPML REHASH ALL"}
{"Headers": "Modify the Orientation Mapping File", "Content": "For the chosen profile in the chosen standard, if any transformations are to be applied to convert from the base product to the default system, they are to be recorded in the orientation mapping file. If the profile requires no transformations, it need not be listed in this file. In the example below, the British type 9 profiles are orientated by mirroring (1) and then rotating by 180 degrees. British type 8 profiles are not mirrored (0) and just rotated by 180 degrees.\nAVEVA BOCAD\nBRI 2 0 180\nBRI 4 1 180\nDIN 2 0 180\nDIN 4 1 180\n\n\n"}
{"Headers": "Modify the Profile Mapping File", "Content": "Any new profiles requiring mapping between the base product and the external steel detailing system should be entered in the mapping file. Refer to Profile Mapping Files for further information on the profile mapping file structure.\n\n\n\nProfile Mapping Files\nProfile Mapping Files"}
{"Headers": "Re-initialize the System and Save the UI Binaries", "Content": "On the Export or Import main forms use Control > Re-initialize for resetting the configuration data only.\nOr execute call !!bocimpexp() in a command window to re-initialize the system.\nHowever this last option is very brutal as all settings will be lost because the windows and menus are regenerated. You will then have to regenerate UI binaries after this.\n\n\n\nControl > Re-\ne\ncall !!bocimpexp()"}
{"Headers": "Installation of User Defined Attributes", "Content": "Before you start designing steelwork, the application requires a set of User Defined Attributes (UDAs) specifically for storing related information. These are installed by performing the following actions:\nMore UDAs might be required in a later version of the application, so you will need to upgrade their current projects if they are to use this later version. The macro has been configured to keep existing UDA definitions so that you will not lose data.\nEnter the LEXICON module with write access to all the relevant Dictionary databases.\nExecute the upgrade macro by the following command:\ncall !!bocUDAUpgrade( )\nExit from LEXICON, saving the changes.\nEnter the LEXICON module with write access to all the relevant Dictionary databases.\nEnter the LEXICON module with write access to all the relevant Dictionary databases.\nExecute the upgrade macro by the following command:\ncall !!bocUDAUpgrade( )\nExecute the upgrade macro by the following command:\nExit from LEXICON, saving the changes.\nExit from LEXICON, saving the changes.\nNote:\nThis upgrade may be run even if the UDAs exist already. In this way you may upgrade the system whenever necessary; for example, to include more UDAs needed for a later version of the application.\n\n\n\ncall !!bocUDAUpgrade( )\nNote:"}
{"Headers": "Special SITES", "Content": "When the AVEVA Bocad Steel Interface application imports a model, some SITE elements might be created. Typically these will be called something like /FAB-OLD-DEMO-SYSTEM. These SITEs store items which have been 'deleted' from the model during the Export/Import cycle. These SITEs will be created only when needed, you can always recover elements from this area if they need to later on.\nThe name of deleted element SITEs are built up of the following components:\n/FAB-\nthe system prefix\nOLD-\nidentification of a SITE for \u2018deleted\u2019 elements\n<mdb name>\nthe current MDB, for example /DEMO\n<user name>\nthe current user name, for example SYSTEM\n/FAB-\nthe system prefix\nOLD-\nidentification of a SITE for \u2018deleted\u2019 elements\n<mdb name>\nthe current MDB, for example /DEMO\n<user name>\nthe current user name, for example SYSTEM\nThe application checks that you have read/write access to their specific SITEs, since you and the application may need to edit certain attributes.\nThe SITE for deleted elements is described in more detail in the User Guide, will store the 'deleted' elements in STRUs according to the Import revision, so that you can quickly isolate which items were deleted at which time.\nYou will note that the SITE names contain the current MDB and the current user name. This is to facilitate multi-user working, and multiple accesses to the database. There may be several of these, depending on which MDB and/or user has access to the particular database.\n/FAB-\nthe system prefix\nOLD-\nidentification of a SITE for \u2018deleted\u2019 elements\n<mdb name>\nthe current MDB, for example /DEMO\n<user name>\nthe current user name, for example SYSTEM\n\n\n\n/FAB-\nOLD-\n<mdb name>\n<user name>"}
{"Headers": "Customize", "Content": "You can set PML variables to customize. They are set in the file called bocuserdata.pmlfnc found in the bocad\\dflts\\user\\bocpml\\functions folder in your data area of the application.\nThe user modifiable function bocuserdata.pmlfnc is found in bocad\\dflts\\user\\bocpml\\functions\nIf you customize the AVEVA Bocad Steel Interface forms, you must reload the base product's user interface from macros in order to rebuild it. If you change variables in your data area, you can use the Re-initialize option on the main Import or Export forms.\nAlternatively, you may reload the AVEVA Bocad Steel Interface system variables and rebuild the forms using the following command, after you have saved the bocuserdata.pmlfnc file:\nHowever, if you find that the user interface forms are damaged, reload the UI from macros. A typical message indicating this condition might be:\ncall !!bocImpExp( )\nObject does not have a member .targetlist\nNote:\nYou must also load the AVEVA Bocad Steel Interface UI from macros if you make any changes to the internal mapping files\n\n\n\nbocuserdata.pmlfnc\nbocad\\dflts\\user\\bocpml\\functions\nbocuserdata.pmlfnc\nRe-\ne\nbocuserdata.pmlfnc\ncall !!bocImpExp( )\nObject does not have a member .targetlist\nNote:"}
{"Headers": "Color Code", "Content": "You can change the colors of the objects on the screen using the variables listed below. If you want to change them, the list of colour numbers is given in the Model Reference Manual. The default settings are:\nThe duplicate colour is used when the import system searches for items with duplicated mark numbers.\n!!bocColChanged     = ( 12 )  $* Mauve\n!!bocColAdded       = ( 5 )   $* Green\n!!bocColDuplicate   = ( 6 )   $* Cyan\n!!bocColDeleted     = ( 2 )   $* Red\n!!bocColExported    = ( 3 )   $* Orange\n!!bocColDefault     = ( 1 )   $* Grey\n\n\n\n!!bocColChanged     = ( 12 )  $* Mauve\n!!bocColAdded       = ( 5 )   $* Green\n!!bocColDuplicate   = ( 6 )   $* Cyan\n!!bocColDeleted     = ( 2 )   $* Red\n!!bocColExported    = ( 3 )   $* Orange\n!!bocColDefault     = ( 1 )   $* Grey"}
{"Headers": "Tolerance Settings", "Content": "You can modify the distance tolerance (the separation, in millimetres, below which two points are considered coincident), the minimum Plate thickness, and the minimum length of Linear Members. The minimum tolerance is used as a fine tolerance value in vector comparisons, such as for angles.\n-- Set distance tolerance\n!!bocDistTol        = ( 1 )\n!!bocMinTol         = ( 0.01 )\n\n\n\n-- Set distance tolerance\n!!bocDistTol        = ( 1 )\n!!bocMinTol         = ( 0.01 )"}
{"Headers": "Waiting Time", "Content": "The system wait time represents a unit of time which the application will wait while the external program is executing. If there is no response within this time, the application may assume that the external program has stopped for some reason. This may not be the case - it may just be working hard!\nYou will be asked whether they want to wait for another unit period. This variable is nominally measured in seconds, but it is also dependent on how busy the computer is on other tasks as well.\nThere is also a variable, !!bocNoOfTries, which is used to determine how many iterations of the waiting loop the application goes through before prompting you for further information.\n-- Set wait time\n!!bocWaitTime      = ( 5 )\n!!bocNoOfTries     = ( 5 )\n\n\n\n-- Set wait time\n!!bocWaitTime      = ( 5 )\n!!bocNoOfTries     = ( 5 )"}
{"Headers": "Ignore Material Flag", "Content": "You can choose to ignore any errors caused by different material mappings by using this flag. What this means is that on comparing the original model with the imported model, any difference in material is not raised as an error.\n-- Ignore Material changes\n!!BOCIgnoreMatl  = false\n\n\n\n-- Ignore Material changes\n!!BOCIgnoreMatl  = false"}
{"Headers": "External Mapping File Separator", "Content": "The separator character for the external mapping files may be either a space or a comma. Using the variables below, you can indicate their choice.\nThere is a third file format for Profile mapping files. The BLOCK format is described elsewhere and is indicated here with !!bocBlockSep. Block formatted files are pre-processed by a separate tool for more efficient reading and parsing.\n-- Mapping File separators\n!!bocProfSep         = !!bocBlockSep\n!!bocMatSep          = !!bocCommaSep\n!!bocOriSep          = !!bocSpaceSep\nNote:\nAll the files of the same type (either Material, Orientation or Profile) must use the same separator consistently: you cannot have some Material files space separated, while others are comma separated.\n\n\n\nNote:\nAll\n-- Mapping File separators\n!!bocProfSep         = !!bocBlockSep\n!!bocMatSep          = !!bocCommaSep\n!!bocOriSep          = !!bocSpaceSep"}
{"Headers": "Pre- and Post-processing Macros", "Content": "You can write their own macros to be run before and after the both the Export and Import processes have taken place. This lets you build a model in the base product which then needs some sort of pre- or post-processing. This is performed using the variables below:\nThe above syntax defines the names of macros which are to be found in the folder structure below the %PMLLIB% environment variable. They are named as above with the PML suffix, '.pmlfnc'.\nThese macros will be called before and after the process has been executed. These macros should have either no arguments and return no value or have a single FILE argument and return no argument. The optional FILE argument refers to the ABSI log file.\n-- Pre/Post Export User Defined Macros\n!!bocPreExpMac  = |bocpreexport|\n!!bocPostExpMac = |bocpostexport|\n!!bocPreImpMac = |bocpreimport|\n!!bocPostImpMac = |bocpostimport|\nNote:\nIt is for you to handle all internal errors within the macros. Errors that are not handled could cause the transfer process to crash.\n\n\n\n-- Pre/Post Export User Defined Macros\n!!bocPreExpMac  = |bocpreexport|\n!!bocPostExpMac = |bocpostexport|\n%PMLLIB%\nNote:"}
{"Headers": "User-definable Material Macro", "Content": "You may modify the sample macro, bocgetusermatl.pmlfnc, as named by the !!bocMaterialMac global variable and given in the bocad\\dflts\\user\\bocpml\\functions folder in the user data folder, if you have specific requirements as to where the material information resides. The bocgetusermatl.pmlfnc function can then be modified. Once modified, you should execute a PML REHASH ALL command.\nThe example macro is as follows:\nThe above example assumes that the material information for GENSECs resides on the catalogue component in the UDA :MATERIAL. If, for any reason, a material cannot be identified, a default value of 'St 37-2' is assigned.\nThe application assumes, by default, that this file exists under the above name in a folder below the %PMLLIB% search path, and that the starting point for database navigation is the current element under consideration, that is a Section, a GENSEC or Panel. for further information of how you can configure the system to use a material macro with a name of your choice, refer to User-definable Material Macro for further information.\nRegarding the naming of this macro, refer to User-definable Material Macro for further information.\ndefine function !!bocGetUserMatl( ) is STRING\n  -- initialization\n  !material = STRING( )\n  !material = |unset|\n  !start = ( ref )\n  -- Set default material\n  !defaultMaterial = |St 37-2|\n  -- Some User specific PML to get the required info\n  !type = ( type )\n  if( !type eq |GENSEC| )then\n    -- Material stored on Catalogue component\n    goto catr\n    handle any\n      -- Bad or null reference\n      !material = !defaultMaterial\n      golabel /Finished\n    endhandle\n    !material = ( :Material )\n    handle any\n      !material = !defaultMaterial\n      golabel /Finished\n    endhandle\n    if( !material eq |unset| or $\n        !material.unset( ) or $\n        !material.length( ) eq 0 )then\n      -- Use default material\n      !material = !defaultMaterial\n    endif\n  elseif( !type eq |PANE| )then\n    -- Try to return :FABMGRADE or default material\n     !material = ( :FABMGRADE )\n    if( !material eq |unset| or $\n        !material.unset( ) or $\n        !material.length( ) eq 0 )then\n      -- Use default material\n      !material = !defaultMaterial\n    endif\n  endif\n  -- Return string and exit\n  label /Finished\n  $!start\n  return !material\nendfunction\nNote:\nIn writing your own macro, you must handle all errors encountered so that the macro will always safely return a valid PML string, whatever it may be.\nAlso, that materials for Panels must also be determined using this macro.\n\n\n\nUser-definable Material Macro\nUser-definable Material Macro\nbocgetusermatl.pmlfnc\n!!bocMaterialMac\nbocad\\dflts\\user\\bocpml\\functions\nPML REHASH ALL\n%PMLLIB%\nUser-definable Material Macro\nNote:\nUser-definable Material Macro"}
{"Headers": "Maximum File Size", "Content": "For reading many files, such as the mapping files, log files or even some internal files, there is a current size limit of 500000 lines.\nThis may be modified by changing the lines below.\nNote:\nThat this is not the size of the input model file. It is the estimated size of the internal macro file produced during the translation process.\n\n\n\nNote:"}
{"Headers": "Profile Mapping Files", "Content": "This section describes the formats for the mapping files between catalogues and those of external 3D steel detailing packages. The mapping files will indicate a correlation between the profile in AVEVA E3D 2.1\u2122 and its equivalent in the other system, to which, or from which, data are to be transferred. It is your responsibility to make sure that any geometrical modelling required in either system is suitably reproduced in the other. The mapping files supplied are modifiable and extensible by you.\n\n\n"}
{"Headers": "Replacement of SCTNs with GENSECs on Import", "Content": "The base product structural user interface creates GENSEC elements for all structural members, whether they are straight or curved. In the first phase of import, all structural members are imported as GENSEC elements. If you are importing to update and existing model, the database type of elements is not changed.\n\n\n"}
{"Headers": "File Headers", "Content": "You can select whether the file will contain listings of all the mapping files or just the section count table. This is done by the !!bocBriefHdr variable in the bocuserdata.pmlfnc file. By default the files have brief headers, but if you want to include details of all the files used for the translation, the variable can be switched to 'false'.\n    -- Brief/Verbose Bocad Interface file header\n    !!bocBriefHdr = true\n\n\n\nbocuserdata.pmlfnc\n    -- Brief/Verbose Bocad Interface file header\n    !!bocBriefHdr = true"}
{"Headers": "Local User Configuration", "Content": "As has been described above, the file bocuserdata.pmlfnc can be modified by hand to provide a degree of customization. This overwrites the system variables in bocsystemdata.pmlfnc.\nNote:\nThis latter function must not be modified.\n\n\n\nbocuserdata.pmlfnc\nbocsystemdata.pmlfnc\nNote:"}
{"Headers": "System Configuration", "Content": "There is a third level of customization available that is accessible by a graphical user interface. This window has access to versions of all the variables in the bocuserdata.pmlfnc function, but it does not modify that function at all. Therefore, at this point, you are working with a local set of configuration data. This file also stores the settings on the attribute comparison window that drives the Compare/Merge operation.\nThe System Configuration window is accessible from either the main Import or Export window using Control > Configure.\n\nThe System Configuration window has five tabs Run Parameters, Model Parameters, Display Colours, Environment Parameters and Macros. The detail of the attributes can be read above. The forms do have some data validation, where appropriate.\n\n\n\n\n\n\nBy default, the system looks for a file ABSI.xml in your work area. If present, this file is accessed when this window, and even when the whole system, is initialized. If this file is not available, then the default values that are used are set in bocsystemdata.pmlfnc and subsequently overwritten by bocuserdata.pmlfnc. You can save the window, settings to this default file using the Control > Save option. To save the settings to another file, use the Control > Save as... option.\nTo load any settings file other than the default one use Control > Load... option. A file browser is displayed allowing you to choose where to locate the new file.\nTo restore the main default settings at window initialization, just delete the ABSI.xml file.\nClick Reset to reset the values using the normal form initialization process with the current variables and any saved ABSI.xml file.\nThe Re-initialize option goes right back to the source variables in the system and user data and the default ABSI.xml files.\nClick OK to transfer the settings to the main Import/Export system for use in that session. Once the window is displayed again, any unsaved attributes will be lost.\n\n\n\nbocuserdata.pmlfnc\nSystem\nConfiguration\nControl > Configure\nSystem Configuration\nRun Parameters, Model Parameters,\nDisplay Colours, Environment Parameters\nMacros\nABSI.xml\nbocsystemdata.pmlfnc\nbocuserdata.pmlfnc\nControl > Save\nControl > Save as...\nControl > Load...\nABSI.xml\nReset\nABSI.xml\nRe-\ne\nABSI.xml\nOK"}
{"Headers": "Internal Mapping Files", "Content": "The application relies on several internal mapping files. These define where external mapping files are located on your system network, or they define the mapping of strings or attributes between the base product and the intermediate file. It is your responsibility to modify them correctly so that they indicate the correct file location.\nInternal mapping files are loaded on start-up of the application. If there are any problems on loading, you will be prompted to confirm that you want to carry on with using the application, although it is frequently inadvisable. If you do not continue, a fatal error is raised and the application exited.\nInternal mapping files must have a suffix '.map' and be stored in one of 3 areas pointed to by the environment variables for the system default area, the project defaults, for example: SAMDFLTS, and your work area. In locating the map files, the folders are searched in the listed sequence. This enables you to have company, project and user mapping files that can overload the previously installed versions. The example internal files supplied by the system should be found in the folder, BocadMaps.\nInternal mapping files are of the form of an asterisk (*) separated sequence of strings. The first line of the file is taken to be a file identifier, the precise rules for which are defined below.\nAs an aid to generalising your application, you may include environment variables in the path names as long as they are defined in the base product format; for example:\nThese environment variables cannot be search paths: they must translate to a reference to a single folder.\nNote:\nIf you change any of the internal mapping files, you must reload the base product's user application from macros. Alternatively you can use the Re-initialize menu option on the main Import and Export forms, you should then resave the binary UI.\n\n\n\nNote:\nRe-\ne\nBocadMaps\n%ENVVAR%\\\n\u00bc"}
{"Headers": "Error and Log File Messages", "Content": "Bad Map File\nOn attempting to load the internal mapping file, there are several potential errors: it is not of the correct format; it may not exist; it may contain empty lines; the first line is not correct.\nNo Mapping Table\ndefined for selection\nThe internal files recognize AVEVA Bocad Steel, but there are no mapping table files associated with it.\nBad Map File\nOn attempting to load the internal mapping file, there are several potential errors: it is not of the correct format; it may not exist; it may contain empty lines; the first line is not correct.\nNo Mapping Table\ndefined for selection\nThe internal files recognize AVEVA Bocad Steel, but there are no mapping table files associated with it.\n\nBad Map File\nOn attempting to load the internal mapping file, there are several potential errors: it is not of the correct format; it may not exist; it may contain empty lines; the first line is not correct.\nNo Mapping Table\ndefined for selection\nThe internal files recognize AVEVA Bocad Steel, but there are no mapping table files associated with it.\n\n\n\nBad Map File\nNo Mapping Table\ndefined for selection"}
{"Headers": "File Mapping Tables", "Content": "The file mapping tables indicate the location of external Profile, Orientation, Unicode and Material mapping tables in the folder structure. The internal mapping tables may be specific to either the project or the company.\nThe tables are searched first for a project-specific set before a company-specific set.\nThe files consist of a first line, then a series of pairs of * separated values (with no spaces), indicating the location of the mapping file.\nThe first line in each file is a pair of values, the second of which is used to identify the list.\nThe second part must be one of:\nThe project-specific Profile mapping files for the TST project may be similar to:\nPRF\nfor a Profile mapping table\nORI\nfor a Profile Orientation mapping table\nMAT\nfor a Material mapping table\nUNI\nfor a Unicode text string conversion file\nPRF\nfor a Profile mapping table\nORI\nfor a Profile Orientation mapping table\nMAT\nfor a Material mapping table\nUNI\nfor a Unicode text string conversion file\nand a companywide Unicode test string mapping table may look like:\nThe Material mapping tables are defined in a similar way. For example a project-specific Material mapping file, using a previously defined environment variable, BOCDATA, might look like:\nA companywide Profile Orientation mapping table would look similar to the following:\nfor further information of the format of the external mapping files, consult the relevant section in this guide.\nPRF\nfor a Profile mapping table\nORI\nfor a Profile Orientation mapping table\nMAT\nfor a Material mapping table\nUNI\nfor a Unicode text string conversion file\nTSTPRF*TSTPRF\nBOCAD*C:\\AVEVA\\Plant\\Bocad\\maps\\Bocad\\Bocad.map\nAVEVA*C:\\AVEVA\\Plant\\AVEVA\\maps\\xxxx\\E3D.map\nANYUNI*ANYUNI\nBOCAD*C:\\AVEVA\\Plant\\Bocad\\maps\\Bocad\\BocadUni.map\nAVEVA*C:\\AVEVA\\Plant\\AVEVA\\maps\\xxxx\\E3DUni.map\nTSTMAT*TSTMAT\nBOCAD*%BOCDATA%\\Bocad\\Bocad.map\nAVEVA*%BOCDATA%\\AVEVA\\AVEVAMat.map\nANYORI*ANYORI\nBOCAD*%BOCMAIN%\\maps\\Bocad\\BocadOri.map\nAVEVA*%BOCMAIN%\\maps\\AVEVA\\AVEVAOri.map\nThe first part of this identifier text is either the three-letter name of the project, for example: TST for the TST000 project, or ANY, signifying a companywide table for any project.\nThe first part of this identifier text is either the three-letter name of the project, for example: TST for the TST000 project, or ANY, signifying a companywide table for any project.\nThe first part of this identifier text is either the three-letter name of the project, for example: TST for the TST000 project, or ANY, signifying a companywide table for any project.\n\n\n\nTST\nANY\nPRF\nORI\nMAT\nUNI\nTSTPRF*TSTPRF\nBOCAD*C:\\AVEVA\\Plant\\Bocad\\maps\\Bocad\\Bocad.map\nAVEVA*C:\\AVEVA\\Plant\\AVEVA\\maps\\xxxx\\\n.map\nANYUNI*ANYUNI\nBOCAD*C:\\AVEVA\\Plant\\Bocad\\maps\\Bocad\\BocadUni.map\nAVEVA*C:\\AVEVA\\Plant\\AVEVA\\maps\\xxxx\\\nUni.map"}
{"Headers": "Error and Log File Messages", "Content": "Environment variable \u2018$nnnn' not understood. - The application cannot determine the meaning of %nnnn% in the mapping file.\nThe application search order is for mapping files for:\nThe data lines are arranged, as in the above examples, as pairs between data found in the base product and that to be output in the file generated by the Export process.\nUser macro nnnn\nnot found\nCannot find user macro.\nError in user macro\nnnnn\nPML programming error in user macro.\nUser macro nnnn\nnot found\nCannot find user macro.\nError in user macro\nnnnn\nPML programming error in user macro.\n\nUser macro nnnn\nnot found\nCannot find user macro.\nError in user macro\nnnnn\nPML programming error in user macro.\n\n\n\nEnvironment variable \u2018$nnnn' not understood\nUser macro nnnn\nnot found\nError in user macro\nnnnn"}
{"Headers": "Steel Standards Mapping Files", "Content": "There are two situations for choosing whether a particular steel profile is permitted or not. The situations are Default or MulTiple.\nThe default steel standard is that listed as the first entry in the Steel Standard mapping file. This is the preferred standard.\nIf the profiles come from the other listed standards, they are deemed to be acceptable. In this case, a warning message will be output to the log file. Profiles taken from standards which are not in the list are flagged as errors.\nThe Steel Standards mapping files may be project or company specific. The identification convention used in the first line of the file, by which we identify the file, is similar to that mentioned above for other internal mapping files. It is the second entry on the first line which is critical. In this case, it is composed of two parts. The first part is either the three-letter name of the project, for example: TST, or it is the word ANY signifying that the file is company specific; that is for ANY project. The second part, STD, is compulsory.\nThe lines are * separated pairs (with no spaces), only the first value of which is used internally. The second value can be for information, as these files will be listed as comments in the exported file. The first value of each entry must be the country code for the profile standards, as recorded in the external Profile mapping files and as suggested in the section discussing the format of the Profile mapping files.\nThe sequence of search is for a project-specific mapping file, and then a company-specific file.\nA project-specific mapping file for the TST project might look like:\nA company-specific file for ANY project might look like:\nTSTSTD*TSTSTD\nEUR*Euronorm\nBRI*British\nAME*American\nANYSTD*ANYSTD\nEUR*Euronorm\nBRI*British\nAME*American\nGER*German\nCAN*Canadian\nJAP*Japanese\n\n\n\nDefault\nMul\nTip\nle\nTST,\nANY\nSTD\n*\nTST\nANY"}
{"Headers": "External Mapping Files", "Content": "While setting up the Export or Import variables, the external mapping files are initially tested to see if they are valid. At the top of each file is a check line indicating that the file is related to AVEVA Bocad Steel. The check line must be of the form:\nAVEVA BOCAD\nNote:\nTab characters are not permitted in the mapping files.\nComments may be included in the mapping files. They are indicated by a hash (#) character as the first non-blank character on the line.\nBlank lines are also permitted.\n\n\n\nNote:"}
{"Headers": "Error and Log File Messages", "Content": "Suitable Mapping Table File not found\nFile specified in the mapping table is not found.\nNot a suitable Mapping Table File - Is it empty?\nThe header may not be of the correct format. The header is incorrect.\nSuitable Mapping Table File not found\nFile specified in the mapping table is not found.\nNot a suitable Mapping Table File - Is it empty?\nThe header may not be of the correct format. The header is incorrect.\n\nSuitable Mapping Table File not found\nFile specified in the mapping table is not found.\nNot a suitable Mapping Table File - Is it empty?\nThe header may not be of the correct format. The header is incorrect.\n\n\n\nSuitable Mapping Table File not found\nNot a suitable Mapping Table File - Is it empty?"}
{"Headers": "Data Fields in Profile Mapping Files", "Content": "Because in the base product element names cannot contain spaces, space-separated mapping files receive special treatment to allow spaces in external Profile names. A description of the individual fields in the Profile Mapping Files is given after this section.\nThe file format has four or five fields per line. Four fields are used for old format mapping files where the AVEVA profile name is either the Catalogue or the Specification name. Five fields are for either the newer format (version 2) or the Block format mapping files. These include both the AVEVA Catalogue\u2122 and the Specification name. Version 2 files are differentiated from the Block format files by having a different header line which includes a single version number, rather than a description of the column widths. The Block format file is recommended.\nThe fields are read in the following order.\nRefer to External Mapping File Separator for further information on how you can specify which separator which the application use to discriminate between fields.\n\n\n\nExternal Mapping File Separator\nExternal Mapping File Separator"}
{"Headers": "CSV Format for Profile Mapping Files", "Content": "You can also use Comma Separated Variable (CSV) format for the Profile mapping. In CSV format, the fields are separated by commas rather than by spaces. This means, therefore, that the names of profiles must not contain commas, but the external profile name can still contain spaces.\nCSV format allows you to manage the mapping files in a spreadsheet program. If you are constructing a CSV file by hand, you should be aware how a CSV file handles commas in fields. Again, CSV files, managed in a spreadsheet program, can be converted easily to Block format.\n\n\n"}
{"Headers": "Record Structure for Profile Mapping File", "Content": "The mapping file consists of records of catalogue or specification profile name matched with the external profile name and two other fields giving the origin and profile shape code as recognized by the external package.\nThe profile names for the external package must be ascertained by you and matched correctly with the equivalent name.\n\n\n"}
{"Headers": "Steel Standard Field", "Content": "Sometimes the project requires that the designer cannot mix profiles from more than one steel standard at the same time. Therefore, we need to record the origin of the profile. This is done in the third field, the steel standard field, which is currently codified as follows:\nAmerica\nAME\nBritain\nBRI\nCanada\nCAN\nEuronorm\nEUR\nGermany\nGER\nJapan\nJAP\nIf you want to include profiles or joints from another standard or country, you must add a new and unique identifier.\n\nCountry\nCode\nAmerica\nAME\nBritain\nBRI\nCanada\nCAN\nEuronorm\nEUR\nGermany\nGER\nJapan\nJAP\n\n\n"}
{"Headers": "Profile Shape Code Field", "Content": "The Profile Type field defines exactly what shape the profile is. This is because there may be many occurrences of the same profile name in the 3D steel detailing package, but used in different manners. For example, only those T shapes which are derived from cutting up I shapes may be stored. This could be recorded in the file as follows:\nW21X44\nW21X44\nAME\n1\nI shape\nWT10.5X22\nW21X44\nAME\n10\nTee ex W21X44\nThe profile shape codes for the new AVEVA supplied catalogue are as follows:\n1\nI-shape (BEAM)\n2\nL-shape (ANG)\n3\nZ-shape\n4\nC shape (BSC)\n5\nFlatBar\n6\nTube (TUBE)\n7\nBar (TUBE)\n8\nRH-shape (BOX)\n9\nTC-Shape (BSC)\n10\nT-shape (TEE)\n12\n\n13\nCone\n\nExternal\nOrigin\nShape Code\nDescription\nW21X44\nW21X44\nAME\n1\nI shape\nWT10.5X22\nW21X44\nAME\n10\nTee ex W21X44\nType Code\nShape\n1\nI-shape (BEAM)\n2\nL-shape (ANG)\n3\nZ-shape\n4\nC shape (BSC)\n5\nFlatBar\n6\nTube (TUBE)\n7\nBar (TUBE)\n8\nRH-shape (BOX)\n9\nTC-Shape (BSC)\n10\nT-shape (TEE)\n12\n13\nCone\n\n\n"}
{"Headers": "Extending the Profile Mapping File", "Content": "To extend the facilities provided by the system, the ASCII file may be extended. Once you have found a match between the base product catalogue profile name and the equivalent profile in AVEVA Bocad Steel, the name match may be added to the file, along with the catalogue origin and profile shape code.\n\n\n"}
{"Headers": "Sample Profile Mapping File", "Content": "The actual shape code number is not critical: the combination of the shape code and the country code IS critical. The combination of the shape and country codes enable us to identify exactly which AVEVA Catalogue\u2122 item is being used. The list of country codes has been extended for the new AVEVA structural profile catalogue. This allows us to differentiate between the old and new catalogues, and the equivalent shapes in each catalogue. This means that we can apply treatment, such as rotation or mirroring, to any particular shape.\nBelow is a short extract of a Profile mapping file between the base product and AVEVA Bocad Steel.\nThis file has 5 columns consisting of the following:\nAVEVA BOCAD 5 22 22 19 3 3\nC10x15.3  AISC/C10x15.3  USC10*15.3   AME 4 \nC10x20    AISC/C10x20    USC10*20     AME 4 \nC10x25    AISC/C10x25    USC10*25     AME 4 \nC10x30    AISC/C10x30    USC10*30     AME 4 \nC12x20.7  AISC/C12x20.7  USC12*20.7   AME 4 \nC12x25    AISC/C12x25    USC12*25     AME 4 \nC12x30    AISC/C12x30    USC12*30     AME 4 \nC15x33.9  AISC/C15x33.9  USC15*33.9   AME 4 \nC15x40    AISC/C15x40    USC15*40     AME 4 \nC15x50    AISC/C15x50    USC15*50     AME 4 \nC3x4.1    AISC/C3x4.1    USC3*4.1     AME 4 \nC3x5      AISC/C3x5      USC3*5       AME 4 \nC3x6      AISC/C3x6      USC3*6       AME 4\nThe AVEVA Catalogue\u2122 element name\nThe AVEVA Specification element name\nThe name of the profile in the external application (for example: Bocad)\nThe letter code for the Specification\nThe Shape Code.\nThe AVEVA Catalogue\u2122 element name\nThe AVEVA Catalogue\u2122 element name\nThe AVEVA Specification element name\nThe AVEVA Specification element name\nThe name of the profile in the external application (for example: Bocad)\nThe name of the profile in the external application (for example: Bocad)\nThe letter code for the Specification\nThe letter code for the Specification\nThe Shape Code.\nThe Shape Code.\nNote:\nThe identification line at the top of the file which indicates the Target Package, for example: BOCAD. It also indicates the version number of the mapping file structure for example: 2 (it is not complete in any way).\n\n\n\nAVEVA BOCAD 5 22 22 19 3 3\nC10x15.3  AISC/C10x15.3  USC10*15.3   AME 4 \nC10x20    AISC/C10x20    USC10*20     AME 4 \nC10x25    AISC/C10x25    USC10*25     AME 4 \nC10x30    AISC/C10x30    USC10*30     AME 4 \nC12x20.7  AISC/C12x20.7  USC12*20.7   AME 4 \nC12x25    AISC/C12x25    USC12*25     AME 4 \nC12x30    AISC/C12x30    USC12*30     AME 4 \nC15x33.9  AISC/C15x33.9  USC15*33.9   AME 4 \nC15x40    AISC/C15x40    USC15*40     AME 4 \nC15x50    AISC/C15x50    USC15*50     AME 4 \nC3x4.1    AISC/C3x4.1    USC3*4.1     AME 4 \nC3x5      AISC/C3x5      USC3*5       AME 4 \nC3x6      AISC/C3x6      USC3*6       AME 4\nNote:"}
{"Headers": "Section Profiles sized by Design Parameters", "Content": "To export or import a profile defined by design parameters to AVEVA Bocad Steel, you need to add a line at the bottom of the mapping file as follows:\nFor example:\n\n\n\nCATREF SPREF\nPRS@2@4@1@3\nEUR\n1\nWhere\nPDMS profile name gives the Catalogue and Specification names of the profile used in PDMS.\nBOCAD profile name is the name of the AVEVA Bocad Steel profile followed by design parameter numbers prefixed by @ symbol\nStandard Key word is the country code for the type of standard.\nShape Code is the profile number given by the table above.\nIf the profile name is not found earlier in the mapping file, the application will try to map the profile to the PDMS profile finding the name that matches the prefix before the first @ in the name.\nIf a match is found, the order of the parameters will be used to set the corresponding design parameters in PDMS.\nBelow is an extract of the mapping file for just parameterized profiles.\n\nThere are three formats for Profile mapping files, the first two formats may be space or comma separated. And are indicated as such by setting the !!bocProfSep variable as !!bocSpaceSep or !!bocCommaSep.\nThe first has been described here, each line in the mapping file contains 4 fields - the AVEVA Catalogue\u2122 or specification profile name, the external profile name, the country code and the shape code. Interpretation of the first field depends upon the !!bocProfMapRef variable as 'SPRE' or 'CATR'.\nIn this format, each line in the mapping file contains 5 fields - the AVEVA Catalogue\u2122 profile name, - the AVEVA specification profile name, the external profile name, the country code and the shape code. Which of the AVEVA columns is picked also depends upon the !!SDNFProfMapRef variable. In order to distinguish this file from the previous format, the header line has an additional \"version\" field.\nFor example\nAVEVA\nFRAMEWORKS\n2\nAVEVA\nFRAMEWORKS\n2\nThe third, and now preferred, format is the Block format, a space separated file that has been pre-processed to facilitate more rapid parsing. Again, each record has 5 fields selectable according to the !!bocProfMapRef variable. This file has a header with more fields describing the column sizes for the file.\nFor example\nAVEVA\nFRAMEWORKS\n5 19 19 16 3 3\nAVEVA\nFRAMEWORKS\n5 19 19 16 3 3\nThis file type is indicated by setting the !!bocProfSep variable to be !!bocBlockSep, refer to AVEVA ABSI/SDNF Mapping File Convertor for further information.\nPDMS profile names\nBOCAD profile name\nStandard Key word\nShape Code\nFor example:\nCATREF SPREF\nPRS@2@4@1@3\nEUR\n1\nAVEVA\nFRAMEWORKS\n2\nAVEVA\nFRAMEWORKS\n5 19 19 16 3 3\n\n\n\nAVEVA ABSI/SDNF Mapping File Convertor\nWhere\nAVEVA ABSI/SDNF Mapping File Convertor"}
{"Headers": "New profile catalogue elements sized by Design Parameters", "Content": "Some additional design profiles are provided for PDMS as follows:\nThese profiles may be optionally added to a catalogue by entering into Paragon and running the following function in a command window:\n\n\n"}
{"Headers": "Error and Log File Messages", "Content": "Profile cannot be\nmapped\nThe profile is not in the Profile Mapping File.\nProfile is not in\nthe standard\nThe profile is in the Profile Mapping File but is not in any one of the set of standards.\nProfile is not the default\nThe profile is in the Profile Mapping File and is in one of the set of standards, but not the default standard.\nMultiply defined entries\nin Profile Table\nEither a profile to be mapped or a mapped profile appears more than once in the Profile Mapping File.\nProfile cannot be\nmapped\nThe profile is not in the Profile Mapping File.\nProfile is not in\nthe standard\nThe profile is in the Profile Mapping File but is not in any one of the set of standards.\nProfile is not the default\nThe profile is in the Profile Mapping File and is in one of the set of standards, but not the default standard.\nMultiply defined entries\nin Profile Table\nEither a profile to be mapped or a mapped profile appears more than once in the Profile Mapping File.\n\nProfile cannot be\nmapped\nThe profile is not in the Profile Mapping File.\nProfile is not in\nthe standard\nThe profile is in the Profile Mapping File but is not in any one of the set of standards.\nProfile is not the default\nThe profile is in the Profile Mapping File and is in one of the set of standards, but not the default standard.\nMultiply defined entries\nin Profile Table\nEither a profile to be mapped or a mapped profile appears more than once in the Profile Mapping File.\n\n\n\nProfile cannot be\nmapped\nProfile is not in\nthe standard\nProfile is not the default\nMultiply defined entries\nin Profile Table"}
{"Headers": "AVEVA ABSI/SDNF Mapping File Convertor", "Content": "This is a tool to format the profile mapping files shared by the SDNF and ABSI interfaces and the AVEVA Bocad Steel from CSV files to a format for more streamlined use. It transforms input files, including formulaic entries into a \"block\" format where we know how big each field is. This makes the reading of the files much faster.\nIn order to speed up the interface the top line of the mapping file gives details of the field widths in the rest of the file. For example:\nThe converter does run stand-alone from the AVEVA E3D 2.1\u2122 install folder, but it is also accessible from the Control menus on the Export and Import main dialogs for both SDNF and ABSI interfaces.\nThe format of the file is as follows\u2026\n[PDMS Catref name, PDMS Specref name] [External profile name, country code, shape code]\nFor example:\nThe shape and country codes are internal to us to help us uniquely identify the profile. At translation time, using a combination of these fields we can build a dictionary for profile mapping between PDMS/AVEVA E3D 2.1\u2122 and Bocad, for example.\nCOMMENT;CATREF;SPREF;EXTERNAL;STANDARD;SHAPE\n#;EU_BF100x7;EU-BF100x7;;EU;21\n;EU_CF_CHS101.6x2.0;EU-CF-CHS101.6x2.0;=CHS{1}*{2};EU;7\n;EU_CF_CHS101.6x2.5;EU-CF-CHS101.6x2.5;=CHS{1}*{2};EU;7\n;EU_CF_CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU;7\nGoes to\nAVEVA BOCAD 5 19 19 19 3 2\nEU_CF_CHS101.6x2.0 EU-CF-CHS101.6x2.0 CHS101.6*2.0       EU 7\nEU_CF_CHS101.6x2.5 EU-CF-CHS101.6x2.5 CHS101.6*2.5       EU 7\nEU_CF_CHS101.6x3.0 EU-CF-CHS101.6x3.0 EU-CF-CHS101.6x3.0 EU 7\nEU_CF_CHS101.6x2.0 EU-CF-CHS101.6x2.0 CHS101.6*2.0       EU 7\n\n\n\nCOMMENT;CATREF;SPREF;EXTERNAL;STANDARD;SHAPE\n#;EU_BF100x7;EU-BF100x7;;EU;21\n;EU_CF_CHS101.6x2.0;EU-CF-CHS101.6x2.0;=CHS{1}*{2};EU;7\n;EU_CF_CHS101.6x2.5;EU-CF-CHS101.6x2.5;=CHS{1}*{2};EU;7\n;EU_CF_CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU;7\nAVEVA BOCAD 5 19 19 19 3 2\nEU_CF_CHS101.6x2.0 EU-CF-CHS101.6x2.0 CHS101.6*2.0       EU 7\nEU_CF_CHS101.6x2.5 EU-CF-CHS101.6x2.5 CHS101.6*2.5       EU 7\nEU_CF_CHS101.6x3.0 EU-CF-CHS101.6x3.0 EU-CF-CHS101.6x3.0 EU 7\nEU_CF_CHS101.6x2.0 EU-CF-CHS101.6x2.0 CHS101.6*2.0       EU 7"}
{"Headers": "The Convertor", "Content": "It is accessed from the Interfaces tab.\n\nIt can also be accessed if you set up a link to run the program from within the AVEVA E3D installation.\n\n\n\nInterfaces"}
{"Headers": "Operation", "Content": "There are 4 main combinations of settings:\nSource folder unchecked/ External folder unchecked\n(user specified output file name - allows producing temporary or copy files)\nInput source file and target file names. Transform source file -> external file\nFor example: Bocad-BS.csv -> externalFileName.map\nSource folder unchecked/ External folder checked\n(output file name derived from input file name)\nInput source file and external folder names. Transform source file -> external file in target folder\nFor example: Bocad-BS.csv -> Bocad-BS.map in external folder\nSource folder checked/ External folder unchecked\n(merge all CSV files into a stated file)\nInput source folder and external file names. Transform and merge all source files -> 1 big target file\nFor example: (Bocad-ASNZ.csv, Bocad-BS.csv, \u2026 Bocad-US.csv) -> externalFileName.map\nSource folder checked/ External folder checked\n(bulk processing of multiple CSV files)\nInput source folder and external folder names. Transform all source files in source folder -> 1 external file per source file in external folder\nFor example: Bocad-ASNZ.csv, Bocad-BS.csv, \u2026 Bocad-US.csv -> Bocad-ASNZ.map, Bocad-BS.map, \u2026 Bocad-US.map\nThe latter 2 options enable you to build larger compound mapping files of various sets of standards. By default, we issue a single file per standard. However, you are able to concatenate various standards into the working set using the bulk options.\n\n\n\nunchecked\nunchecked\nfile\nBocad-BS.csv -> externalFileName.map\nunchecked\nchecked\nocad-BS.csv -> Bocad-BS.map\nchecked\nunchecked\n(Bocad-ASNZ.csv, Bocad-BS.csv, \u2026 Bocad-US.csv) -> externalFileName.map\nchecked\nchecked\nBocad-ASNZ.csv, Bocad-BS.csv, \u2026 Bocad-US.csv -> Bocad-ASNZ.map, Bocad-BS.map, \u2026 Bocad-US.map\nbulk"}
{"Headers": "Small details", "Content": "The CSV file separator can be ',' ';' or tab you have to tell the spreadsheet package what the field separator is as the source file is opened.\nThe formulae can use either '{}' or '()'. Formulae also begin with '='. This is often an indicator for internal formulae. In order to see the formulae without the system making any attempt to evaluate them, you will have to turn this feature off, by showing the fields only.\nThe translator saves the previous configuration settings in the first place it can find out of the folders pointed to by the environment variables \"AVEVA_DESIGN_USER\", \"PDMSUSER\", \"TEMP\".\n\n\n"}
{"Headers": "Workflow for Mapping file conversion", "Content": "The workflow is essentially converting a .csv file to a .map file, you will spend time in Excel editing the .csv file. When done, it should go through the mapping tool to produce a .map file.\nIf there are errors, the converter produces an annotated .map.csv file which enables you to see where the problems are. Ideally the problems should be rectified in the main source .csv file and the file converted again.\nFor both AVEVA E3D 2.1\u2122/PDMS and AVEVA Bocad Steel, the source file for the mapping file production will be the .csv file. The resultant mapping file is shared by the SDNF and ABSI interfaces as well as the AVEVA Bocad Steel product.\nThe conversion process can rely on other tables and files that are relevant to the external package. The External data folder is the folder that contains the converter related files, for example: the alle_prof.inp, profitab.inp and the generic.lis files for Bocad. For the converting of mapping files for other applications there is a recommended file structure to aid the conversion. We will have another folder with the profile lists and anything else we need. This is described in detail below.\nThe other targets that the tool lists are more for round-tripping E3D->E3D or PDMS->PDMS. In this case the 2nd and 3rd columns will be the same now, if you have used the CATR, the 1st and 3rd columns would be the same.\n\n\n\n.csv\n.map\n.csv\n.map\n.map.csv\n.csv\n.csv\nExternal data folder"}
{"Headers": "Installed mapping files", "Content": "We supply mapping files for AVEVA E3D 2.1\u2122 and PDMS to allow round tripping of data, for Bocad and a sample set for Intergraph Frameworks, the originators of the SDNF file format.\nHow you use the Frameworks files as a template to build mapping files for other targets will be described below.\n\nThe source CSV files are in a folder <target>_CSV, and the output mapping files are in a folder <target_Maps>.\n\nThe system is configured to pick these up automatically using the BLOCKMAPS environment variable. If you place them somewhere else on the file system, you will have to tell the interfaces where they are.\n\nThe source file text below\n\nIs translated to:\n\n\n\n"}
{"Headers": "Building Mapping Files for any other target application", "Content": "There are basic lists that the interfaces and convertor rely on.\n\n\n"}
{"Headers": "Old Catalog Shape Codes", "Content": "1\nBEAM - I-shape\n1\nRSJ - I-shape\n1\nDBEA - I-shape\n1\nDINI - I-shape\n1\nJISI - I-shape\n2\nANG - L-shape\n2\nLP - L-shape\n3\nZEE - Z-shape\n4\nBSC - C-shape\n4\nDBSC - C-shape\n4\nCHAN - C-shape\n4\nDINU - C-shape\n5\nFBAR - Flat bar\n5\nFB - Flat bar\n6\nRBAR - Bar\n7\nTUBE - Tube\n8\nBOX - RH-shape\n9\nBSC - TC-shape\n10\nTEE - T-shape\n11\nSBAR - Square bar\n12\nHBAR - Hexagonal bar\n13\nCONE - Cone\n14\nTR - Stair tread\n15\nRECT - Rectangular concrete profile\n21\nBULB - Bulb\n1\nBEAM - I-shape\n1\nRSJ - I-shape\n1\nDBEA - I-shape\n1\nDINI - I-shape\n1\nJISI - I-shape\n2\nANG - L-shape\n2\nLP - L-shape\n3\nZEE - Z-shape\n4\nBSC - C-shape\n4\nDBSC - C-shape\n4\nCHAN - C-shape\n4\nDINU - C-shape\n5\nFBAR - Flat bar\n5\nFB - Flat bar\n6\nRBAR - Bar\n7\nTUBE - Tube\n8\nBOX - RH-shape\n9\nBSC - TC-shape\n10\nTEE - T-shape\n11\nSBAR - Square bar\n12\nHBAR - Hexagonal bar\n13\nCONE - Cone\n14\nTR - Stair tread\n15\nRECT - Rectangular concrete profile\n21\nBULB - Bulb\n\n1\nBEAM - I-shape\n1\nRSJ - I-shape\n1\nDBEA - I-shape\n1\nDINI - I-shape\n1\nJISI - I-shape\n2\nANG - L-shape\n2\nLP - L-shape\n3\nZEE - Z-shape\n4\nBSC - C-shape\n4\nDBSC - C-shape\n4\nCHAN - C-shape\n4\nDINU - C-shape\n5\nFBAR - Flat bar\n5\nFB - Flat bar\n6\nRBAR - Bar\n7\nTUBE - Tube\n8\nBOX - RH-shape\n9\nBSC - TC-shape\n10\nTEE - T-shape\n11\nSBAR - Square bar\n12\nHBAR - Hexagonal bar\n13\nCONE - Cone\n14\nTR - Stair tread\n15\nRECT - Rectangular concrete profile\n21\nBULB - Bulb\n\n\n"}
{"Headers": "New Catalog Shape Code", "Content": "1\nPFI - parallel flange I\n1\nPLTG - plate girder\n1\nTFI - tapered flange I\n2\nANGL - angle - no differentiation\n3\nZED - Z profile\n4\nTFC - tapered flange C\n4\nCEE - C shape\n4\nPFC - parallel flange C\n5\nFBAR - flat bar\n6\nRBAR - reinforcing bar (solid)\n7\nCTUB - circular tube\n8\nRTUB - rectangular tube\n8\nBOXG - box grinder\nq\nPFT - parallel flange T\n10\nTF - tapered flange T\n10\nTFWT - tapered web and flange T\n12\nHBAR - hexagonal bar\n21\nBFLA - bulb flat\n1\nPFI - parallel flange I\n1\nPLTG - plate girder\n1\nTFI - tapered flange I\n2\nANGL - angle - no differentiation\n3\nZED - Z profile\n4\nTFC - tapered flange C\n4\nCEE - C shape\n4\nPFC - parallel flange C\n5\nFBAR - flat bar\n6\nRBAR - reinforcing bar (solid)\n7\nCTUB - circular tube\n8\nRTUB - rectangular tube\n8\nBOXG - box grinder\nq\nPFT - parallel flange T\n10\nTF - tapered flange T\n10\nTFWT - tapered web and flange T\n12\nHBAR - hexagonal bar\n21\nBFLA - bulb flat\nAnd the design parameter shapes are:\n1\nDPFI - Design Parameter Parallel Flange I\n1\nDPLG - Design Parameter Plate Girder\n1\nDTWI - Design Parameter Tapered Web I\n2\nDANG - Design Parameter Equal or Unequal Angle\n3\nDZED - Design Parameter Z Profile\n4\nDCEE - Design Parameter Flanged C Profile\n4\nDPFC - Design Parameter Parallel Flange Channel\n5\nDFBA - Design Parameter Flat Bar\n6\nDRBA - Design Parameter Round Bar\n7\nDCTU - Design Parameter Circular Tube\n8\nDRTU - Design Parameter Rectangular or Square Tube\n8\nDBXG - Design Parameter Box Girder\n10\nDPFT - Design Parameter Parallel Flange Tee\n12\nDHBA - Design Parameter Hex Bar\n13\nDCON - Design Parameter Cone\n1\nDPFI - Design Parameter Parallel Flange I\n1\nDPLG - Design Parameter Plate Girder\n1\nDTWI - Design Parameter Tapered Web I\n2\nDANG - Design Parameter Equal or Unequal Angle\n3\nDZED - Design Parameter Z Profile\n4\nDCEE - Design Parameter Flanged C Profile\n4\nDPFC - Design Parameter Parallel Flange Channel\n5\nDFBA - Design Parameter Flat Bar\n6\nDRBA - Design Parameter Round Bar\n7\nDCTU - Design Parameter Circular Tube\n8\nDRTU - Design Parameter Rectangular or Square Tube\n8\nDBXG - Design Parameter Box Girder\n10\nDPFT - Design Parameter Parallel Flange Tee\n12\nDHBA - Design Parameter Hex Bar\n13\nDCON - Design Parameter Cone\n\n1\nPFI - parallel flange I\n1\nPLTG - plate girder\n1\nTFI - tapered flange I\n2\nANGL - angle - no differentiation\n3\nZED - Z profile\n4\nTFC - tapered flange C\n4\nCEE - C shape\n4\nPFC - parallel flange C\n5\nFBAR - flat bar\n6\nRBAR - reinforcing bar (solid)\n7\nCTUB - circular tube\n8\nRTUB - rectangular tube\n8\nBOXG - box grinder\nq\nPFT - parallel flange T\n10\nTF - tapered flange T\n10\nTFWT - tapered web and flange T\n12\nHBAR - hexagonal bar\n21\nBFLA - bulb flat\n1\nDPFI - Design Parameter Parallel Flange I\n1\nDPLG - Design Parameter Plate Girder\n1\nDTWI - Design Parameter Tapered Web I\n2\nDANG - Design Parameter Equal or Unequal Angle\n3\nDZED - Design Parameter Z Profile\n4\nDCEE - Design Parameter Flanged C Profile\n4\nDPFC - Design Parameter Parallel Flange Channel\n5\nDFBA - Design Parameter Flat Bar\n6\nDRBA - Design Parameter Round Bar\n7\nDCTU - Design Parameter Circular Tube\n8\nDRTU - Design Parameter Rectangular or Square Tube\n8\nDBXG - Design Parameter Box Girder\n10\nDPFT - Design Parameter Parallel Flange Tee\n12\nDHBA - Design Parameter Hex Bar\n13\nDCON - Design Parameter Cone\n\n\n"}
{"Headers": "Catalog Country Codes", "Content": "AS\nAustralia\nASNZ\nAustralia and New Zealand (shared standards)\nBR\nBrazil (these profiles are not currently in the catalogue)\nBS\nBritish\nCA\nCanada\nCE\nChile\nDIN\nDIN\nEU\nEurope\nIS\nIndia\nJA\nJapan\nNZ\nNew Zealand\nRU\nRussia\nSA\nSouth Africa\nSW\nSweden\nUS\nAmerica\nSB\nSolid bar profiles, common to many countries\nDPP\nDesign parameter profiles - generic\nFP\nFabricated profiles\nCONC\nConcrete\nMISC\nMiscellaneous\nAS\nAustralia\nASNZ\nAustralia and New Zealand (shared standards)\nBR\nBrazil (these profiles are not currently in the catalogue)\nBS\nBritish\nCA\nCanada\nCE\nChile\nDIN\nDIN\nEU\nEurope\nIS\nIndia\nJA\nJapan\nNZ\nNew Zealand\nRU\nRussia\nSA\nSouth Africa\nSW\nSweden\nUS\nAmerica\nSB\nSolid bar profiles, common to many countries\nDPP\nDesign parameter profiles - generic\nFP\nFabricated profiles\nCONC\nConcrete\nMISC\nMiscellaneous\nIt must be noted that these lists are not fixed, if you wish to create a new country catalogue, then create a new country abbreviation and then use it consistently. So too with the profile shapes, the lists indicated are related to the supplied catalogues and gtypes.\nIf you create their own catalogues and GTYPEs, just set up a new meaning, the interface documentation also describes the requirements of catalogues, plines and orientation mapping files that must be satisfied for a successful translation.\nAS\nAustralia\nASNZ\nAustralia and New Zealand (shared standards)\nBR\nBrazil (these profiles are not currently in the catalogue)\nBS\nBritish\nCA\nCanada\nCE\nChile\nDIN\nDIN\nEU\nEurope\nIS\nIndia\nJA\nJapan\nNZ\nNew Zealand\nRU\nRussia\nSA\nSouth Africa\nSW\nSweden\nUS\nAmerica\nSB\nSolid bar profiles, common to many countries\nDPP\nDesign parameter profiles - generic\nFP\nFabricated profiles\nCONC\nConcrete\nMISC\nMiscellaneous\n\n\n"}
{"Headers": "Source CSV file", "Content": "The source CSV file is of the form:\nIn the example above, the ';' character is used as a field separator. The converter also allows ',' and the tab character. To manage the file in a spreadsheet program, you will have to tell it which character to use.\nThere are 6 columns:\nCOMMENT\nIf the field in this column begins with a '#' the whole record is ignored. After conversion, a .map.csv file is produced which is re-convertible, but which may contain error messages in this column.\nCATREF\nThis contains the PDMS/AVEVA E3D 2.1\u2122 Catalogue component name.\nSPREF\nThis contains the PDMS/AVEVA E3D 2.1\u2122 Specification component name.\nEXTERNAL\nThis contains the name, or formula, of the profile in the target external system.\nSTANDARD\nThis is the abbreviation chosen to indicate to which standard the profile is related\nSHAPE\nThis defined the profile shape.\nCOMMENT\nIf the field in this column begins with a '#' the whole record is ignored. After conversion, a .map.csv file is produced which is re-convertible, but which may contain error messages in this column.\nCATREF\nThis contains the PDMS/AVEVA E3D 2.1\u2122 Catalogue component name.\nSPREF\nThis contains the PDMS/AVEVA E3D 2.1\u2122 Specification component name.\nEXTERNAL\nThis contains the name, or formula, of the profile in the target external system.\nSTANDARD\nThis is the abbreviation chosen to indicate to which standard the profile is related\nSHAPE\nThis defined the profile shape.\nThe top line of the file must contain these headings, or precisely 6 fields which are taken to be column names.\nBy using a = in front of the external profile name, the name will be interpreted as a formula that defines value substitution. This means that the formula will be interpreted by replacing the {n} by the n'th group of number of the name contained in second column. Up to 9 substitutions are allowed. The characters that are considered as a number are: 0123456789 and '-' and '/'. The characters '-' and '/' should be enclosed by at least one digit on each side to be consider as part of a number group.\nFor example:\nEPPKORE/508~D12.7\n=TUBE{1}*{2}\nEPPKORE/L45x45x4x4\n=L{1}*{3}\nEPPKORE/L50x30x3x3\n=L{1}*{2}*{3}\nEPPKORE/H496x199x9x14\n=JPH{1}*{2}*{3}*{4}\nEPPAISC/HSS4-1/2x4-1/2x1/8\n=USHSS{1}*{2}*{3}\nEPPAISC/14.000~D.625\n=TUBE{1}\"*{2}\"\nEPPKORE/508~D12.7\n=TUBE{1}*{2}\nEPPKORE/L45x45x4x4\n=L{1}*{3}\nEPPKORE/L50x30x3x3\n=L{1}*{2}*{3}\nEPPKORE/H496x199x9x14\n=JPH{1}*{2}*{3}*{4}\nEPPAISC/HSS4-1/2x4-1/2x1/8\n=USHSS{1}*{2}*{3}\nEPPAISC/14.000~D.625\n=TUBE{1}\"*{2}\"\nThe new csv file will have the formulas interpreted, in the example:\nEPPKORE/508~D12.7\nTUBE508*12.7\nEPPKORE/L45x45x4x4\nL45*4\nEPPKORE/L50x30x3x3\nL50*30*3\nEPPKORE/H496x199x9x14\nJPH496*199*9*14\nEPPAISC/HSS4-1/2x4-1/2x1/8\nJSHSS4-1/2*4-1/2*1/8\nEPPAISC/14.000~D.625\nTUBE14.000\"*.625\"\nEPPKORE/508~D12.7\nTUBE508*12.7\nEPPKORE/L45x45x4x4\nL45*4\nEPPKORE/L50x30x3x3\nL50*30*3\nEPPKORE/H496x199x9x14\nJPH496*199*9*14\nEPPAISC/HSS4-1/2x4-1/2x1/8\nJSHSS4-1/2*4-1/2*1/8\nEPPAISC/14.000~D.625\nTUBE14.000\"*.625\"\n\nCOMMENT\nIf the field in this column begins with a '#' the whole record is ignored. After conversion, a .map.csv file is produced which is re-convertible, but which may contain error messages in this column.\nCATREF\nThis contains the PDMS/AVEVA E3D 2.1\u2122 Catalogue component name.\nSPREF\nThis contains the PDMS/AVEVA E3D 2.1\u2122 Specification component name.\nEXTERNAL\nThis contains the name, or formula, of the profile in the target external system.\nSTANDARD\nThis is the abbreviation chosen to indicate to which standard the profile is related\nSHAPE\nThis defined the profile shape.\nEPPKORE/508~D12.7\n=TUBE{1}*{2}\nEPPKORE/L45x45x4x4\n=L{1}*{3}\nEPPKORE/L50x30x3x3\n=L{1}*{2}*{3}\nEPPKORE/H496x199x9x14\n=JPH{1}*{2}*{3}*{4}\nEPPAISC/HSS4-1/2x4-1/2x1/8\n=USHSS{1}*{2}*{3}\nEPPAISC/14.000~D.625\n=TUBE{1}\"*{2}\"\nEPPKORE/508~D12.7\nTUBE508*12.7\nEPPKORE/L45x45x4x4\nL45*4\nEPPKORE/L50x30x3x3\nL50*30*3\nEPPKORE/H496x199x9x14\nJPH496*199*9*14\nEPPAISC/HSS4-1/2x4-1/2x1/8\nJSHSS4-1/2*4-1/2*1/8\nEPPAISC/14.000~D.625\nTUBE14.000\"*.625\"\nCOMMENT;CATREF;SPREF;EXTERNAL;STANDARD;SHAPE\n#;EU_BF100x7;EU-BF100x7;;EU;21\n;EU_CF_CHS101.6x2.0;EU-CF-CHS101.6x2.0;=CHS{1}*{2};EU;7\n;EU_CF_CHS101.6x2.5;EU-CF-CHS101.6x2.5;=CHS{1}*{2};EU;7\n;EU_CF_CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU;7\n\n\n\nCOMMENT;CATREF;SPREF;EXTERNAL;STANDARD;SHAPE\n#;EU_BF100x7;EU-BF100x7;;EU;21\n;EU_CF_CHS101.6x2.0;EU-CF-CHS101.6x2.0;=CHS{1}*{2};EU;7\n;EU_CF_CHS101.6x2.5;EU-CF-CHS101.6x2.5;=CHS{1}*{2};EU;7\n;EU_CF_CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU;7\n.map.csv\nEPPKORE/508~D12.7\n=TUBE{1}*{2}\nEPPKORE/L45x45x4x4\n=L{1}*{3}\nEPPKORE/L50x30x3x3\n=L{1}*{2}*{3}\nEPPKORE/H496x199x9x14\n=JPH{1}*{2}*{3}*{4}\nEPPAISC/HSS4-1/2x4-1/2x1/8\n=USHSS{1}*{2}*{3}\nEPPAISC/14.000~D.625\n=TUBE{1}\"*{2}\"\nEPPKORE/508~D12.7\nTUBE508*12.7\nEPPKORE/L45x45x4x4\nL45*4\nEPPKORE/L50x30x3x3\nL50*30*3\nEPPKORE/H496x199x9x14\nJPH496*199*9*14\nEPPAISC/HSS4-1/2x4-1/2x1/8\nJSHSS4-1/2*4-1/2*1/8\nEPPAISC/14.000~D.625\nTUBE14.000\"*.625\""}
{"Headers": "Supporting external profile data files", "Content": "For generating mapping files for applications other than AVEVA Bocad, AVEVA E3D 2.1\u2122 or PDMS, there is a folder and file structure you will need to follow. The files for Frameworks will provide a template. However, the TEST mapping file is the only one that has been completed.\nThere are three separate folders: the source csv files, the resultant mapping files and the supporting data files.\n\nThe important file to note is the shapes.txt file, this is a file that links the shape to the file tables in the standard folders below. Below is a sample of the shapes.txt file.\n\nThis indicates, for example, that files C.txt (line 7) are related to the shape code 4, which you will see above refers to C shapes. The profile tables related to the external package may then be sorted into folders named according to the standard to which they apply.\nThis will assist in housekeeping, as this is just a sample data set, the C.txt contains just 1 entry, UNP220. The interface now has enough information to perform the conversion.\n\n\n\ncsv\nshapes.txt\nshapes.txt\nC.txt\nC.txt"}
{"Headers": "Editing the .csv file", "Content": "The entries are not necessarily in the same order as input, this is because they are sorted on output as well for ease of searching.\n\n\n\n"}
{"Headers": "Material Mapping Files", "Content": "Elements cannot be transferred through the AVEVA Bocad Steel Interface if they do not have a valid material associated with them.\nThe existing base product material description may not be recognized; consequently, there must be a means by which we can translate the material description between systems. This is performed by means of a Material mapping file which relates the base product text description of a material to that output to, or found in, an ABS file.\nWhen the application is started, the Properties database is searched for SOLI elements which may define materials used to fabricate elements in the base product. An internal list is then built for rapid reference.\nMaterials are usually associated with the base product elements using the Material Reference attribute, MATR, which points to a SOLI element in the Properties database. However, you may want to use the local :FABMGRADE attribute to specify the material. Either of these should be set for the application to be able to export elements successfully.\nIf the above system is still not specific enough, there is a mechanism by which you can define from where the material information is to be derived. Refer to Error and Log File Messages for further information.\nWhen an element is exported, its material is determined by inspecting the :FABMGRADE attribute first, then the Description attribute of the SOLI element to which the MATR refers. If that fails, the user configurable mechanism is invoked. The text is then transferred locally to the :FABMGRADE attribute on the GENSEC, SCTN or PANE element. The text is then looked up in the Material mapping file to check that there is a translation into the file replacement text. The local material text is still exported.\nWhen an element is to be imported, the file material description is looked up in the material mapping file and translated into the base product equivalent text string. This is then initially copied into the :FABMGRADE attribute of the element before any attempt is made to rationalise the MATR. If a SOLI element with this material text is found, the application will set the MATR to point to the correct SOLI element.\nAs with the profile mapping file, the first line is an identifier which indicates the external package or system with which the file is associated.\nNote:\nYou can modify and extend the mapping file.\n\n\n\nError and Log File Messages\nNote:\nError and Log File Messages\nexported\nimported"}
{"Headers": "Error and Log File Messages", "Content": "Multiply defined entries in Material Table\nEither a material to be mapped or a mapped profile appears more than once in the Material Mapping File.\nNo match for material\nThe material is not in the Material Mapping File.\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse\nState\nThis should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.\nMultiply defined entries in Material Table\nEither a material to be mapped or a mapped profile appears more than once in the Material Mapping File.\nNo match for material\nThe material is not in the Material Mapping File.\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse\nState\nThis should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.\n\nMultiply defined entries in Material Table\nEither a material to be mapped or a mapped profile appears more than once in the Material Mapping File.\nNo match for material\nThe material is not in the Material Mapping File.\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse\nState\nThis should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.\n\n\n\nMultiply defined entries in Material Table\nNo match for material\nSyntax Error\nUnrecognized Parse\nState"}
{"Headers": "Error and Log File Messages", "Content": "User macro nnnn\nnot found\nCannot find user macro.\nError in user\nmacro nnnn\nPML programming error in user macro.\nUser macro nnnn\nnot found\nCannot find user macro.\nError in user\nmacro nnnn\nPML programming error in user macro.\n\nUser macro nnnn\nnot found\nCannot find user macro.\nError in user\nmacro nnnn\nPML programming error in user macro.\n\n\n\nUser macro nnnn\nnot found\nError in user\nmacro nnnn"}
{"Headers": "Sample Material Mapping File", "Content": "Below is a sample comma separated mapping (CSV) file to map between the base product materials found in the Properties database and the file targeted at AVEVA Bocad Steel.\nAVEVA,BOCAD\n\"unset\",\"unset\"\n\"TREAD-ALU\",\"TREAD-Aluminum\"\n\"ALUMINIUM\",\"Aluminum\"\n\"GR 420 I\",\"GR 420 I\"\n\"Pyrocrete\",\"Fire concrete\"\n\"Tread Grade\",\"Tread Grade\"\n\"LDPHP-GRADE\",\"LDPHP-GRADE\"\n\"Aluminium, cast\",\"Aluminium, cast\"\n\"Aluminium, wrought\",\"Wrought Aluminium\"\n\"Aluminium, Duralumin\",\"Duralumin\"\n\"Brass, red 80% Cu\",\"Red Brass \"\n\"Brass, yellow 65% Cu\",\"Yellow Brass \"\n\"Brass, cast\",\"Cast Brass\"\n\"Steel, carbon\",\"Carbon Steel\"\n\"Steel, chrome\",\"Chrome Steel\"\n\"Steel, Ni-chrome\",\"Ni Steel\"\n\n\n"}
{"Headers": "Profile Orientation Mapping Files", "Content": "Using the Profile Orientation Mapping File you can define how the interface translates a profile from the base product format into the Neutral File format on Export, or from it on Import. Refer to the User Guide for further information of how the Neutral File understands default orientations of certain profiles.\nIf you define their own catalogue profiles, or modify the supplied ones, and need to transform them into or from the neutral format, this mapping file should be used. In all cases an Orientation mapping file should be available, even if it is empty apart from the first line.\nBelow is an example file:\nThe first line is the file identification line, described as for the Material or Profile mapping files. The structure of the rest of the mapping file is of a comma or space separated file with four fields per line.\nThe first two fields provide the identification of the profile for treatment. The first of the identification fields states the steel standard from which the profile is to be taken. The second is the actual profile type (shape) code according to the codes given. Thus, in the example above, you can see that the channels (type 2) and angles (type 4) from the Euronorm, DIN and British Standard catalogues have been identified for special treatment.\nThe third and fourth fields describe what you want to do with the profile shape. The third is the mirroring flag, which should be set to 1 if the profile is to be reflected about the Y-axis. This will commonly be the case for angle profiles. no mirroring is indicated by a value of 0 in this field.\nThe last field defines how much additional angular rotation you want to apply to the shape. For example, some catalogues may define the long leg of an unequal angle to be on the horizontal, whereas AVEVA Bocad Steel Interface expects it to be vertical. The rotation angle must be between -180 and +180 degrees.\nIf, during the Import or Export process, an entry for a specific profile is not found, no action is taken, and no error message is output as it is assumed that you do not want it to receive special treatment.\nThe following figure illustrates the effect of each operation on different catalogue representations of an angle profile. We re-emphasise the difference in the handedness of the coordinate systems.\n\nAVEVA BOCAD\nBRI 2 0 180\nBRI 4 1 180\nDIN 2 0 180\nDIN 4 1 180\nEUR 2 0 180\nEUR 4 1 180\nNote:\nMirroring will change the start and end positions of the linear member. It is therefore advisable that if you can achieve the same result purely by rotation, then the latter is the preferred option. In this way you will avoid confusion in AVEVA Bocad Steel.\n\n\n\nNote:"}
{"Headers": "Mirrored Profiles", "Content": "In the base product it is possible to set a mirror flag which implies that the profile is to be mirrored about the local Y axis, while keeping all other geometric attributes unchanged. Also you might wish to define a new arrangement of profile in the catalogue that would need mirroring before being written in the ABS file using the Orientation Mapping File. Under normal circumstances the ABS file would simply transfer a mirror flag, indicating what is required and how to interpret the geometric data.\nUnfortunately, AVEVA Bocad Steel cannot handle mirroring, in any form. Therefore the ABSI interface has to handle all this internally before export, and after import. However, it is impossible to completely undo the transformations that have been performed on an element for export when the interface is re-importing the same element. For example: the ends might have been swapped round, or the end connectivity might be changed. In these situations the Compare/Merge might highlight a changed element even though it appears to occupy exactly the same location.\n\n\n"}
{"Headers": "Unicode Text String Description Files", "Content": "Users who take advantage of the Unicode features of the base product may have issues when exporting and importing a model. The primary danger is where there are catalogue profile or material names in the base product that contain Unicode characters. Therefore, a dictionary file may be written to convert any base product strings that contain Unicode characters into equivalent strings that do not. It is these latter strings that will appear in the file. This might actually be a description of the profile, rather than the known profile name. This could be to inform or alert you of the external application of what the profile is meant to be.\nBecause there are strings other than the profile names that appear in the file, this Unicode description file should be regarded as a kind of dictionary, a look-up for any string, rather than just a profile name description table. Therefore, its format and use is different from that of the other mapping files. It is used immediately prior to writing out the text strings and it is only to contain the strings that require stripping of Unicode characters. It is also used on file import.\n\nThis Unicode description file may be customized for each target system, in the same way as the other mapping tables. This will contain:\nSo a dictionary for export might look like:\nYou are not forced to prepare one of these files: the system will cope if one does not exist. It would just mean that the strings would not be translated and you would have to take his chance with the target package. Further, the file can be empty, but if there are any strings requiring description, there must be the ENCODING: statement as the first non comment line in the file.\nIt should be noted that text fields are of a fixed maximum width. If the resultant text is too long, it will be truncated, and you are warned. Ideally, the translation should succeed with no truncation warnings, and all profiles mapped either by the main mapping file or through using the Unicode description file. If, however, you decide to output in UTF-8 characters, and thereby diverge from the literal interpretation of the format, truncation will not take place.\nOn import the system will attempt to recognize names in the dictionary, and to translate them back into the original names. This is in addition to the usual profile and material mapping files.\nENCODING:ASCII\n# header texts\n# non-ASCII profiles\n:\u0393\u03c1x\u03bdx\u03b8:Corinthian Column, 1 cubit:\n# non-ASCII materials\n|\u03c7\u03ac\u03bb\u03c5\u03b2\u03b1, \u03b1\u03bd\u03b8\u03c1\u03b1|Green-veined marble|\nAn indication of the encoding to be used for the file\nUnicode UTF-8 with a Byte Order Mark (BOM):\nENCODING:UTF8BOM\nUnicode UTF-8 without BOM:\nENCODING:UTF8noBOM\nForce to Default encoding:\nENCODING:DEFAULT\nForce to ASCII:\nENCODING:ASCII\nA set of string substitutions to be used whenever a quoted-string is written to the file.\nAs potentially any character can be used in the string, first non-space character of the line is used as a delimiter for that line\nOnly complete strings would be substituted\nComment lines are indicated by '#'\nnot every string needs to be in the dictionary - others would be passed through without error (but would trigger a warning if characters were lost in the encoding)\nAn indication of the encoding to be used for the file\nUnicode UTF-8 with a Byte Order Mark (BOM):\nENCODING:UTF8BOM\nUnicode UTF-8 without BOM:\nENCODING:UTF8noBOM\nForce to Default encoding:\nENCODING:DEFAULT\nForce to ASCII:\nENCODING:ASCII\nAn indication of the encoding to be used for the file\nA set of string substitutions to be used whenever a quoted-string is written to the file.\nAs potentially any character can be used in the string, first non-space character of the line is used as a delimiter for that line\nOnly complete strings would be substituted\nComment lines are indicated by '#'\nnot every string needs to be in the dictionary - others would be passed through without error (but would trigger a warning if characters were lost in the encoding)\nA set of string substitutions to be used whenever a quoted-string is written to the file.\n\n\n"}
{"Headers": "Supplementary Information", "Content": "The Appendix describes the following:\nModification Dates and Times and the Base Product\nFirst Time Export to AVEVA Bocad Steel\nImport from AVEVA Bocad Steel\nSubsequent Export to AVEVA Bocad Steel\nRemoval of History Data\nDesign Parameter Sized Profiles\nManaging the Model Limits and Offsets\nInitialization of the ABSI Application\nCatalog Versions\nApplication Tools\nUser Customization.\nModification Dates and Times and the Base Product\nModification Dates and Times and the Base Product\nFirst Time Export to AVEVA Bocad Steel\nFirst Time Export to AVEVA Bocad Steel\nImport from AVEVA Bocad Steel\nImport from AVEVA Bocad Steel\nSubsequent Export to AVEVA Bocad Steel\nSubsequent Export to AVEVA Bocad Steel\nRemoval of History Data\nRemoval of History Data\nDesign Parameter Sized Profiles\nDesign Parameter Sized Profiles\nManaging the Model Limits and Offsets\nManaging the Model Limits and Offsets\nInitialization of the ABSI Application\nInitialization of the ABSI Application\nCatalog Versions\nCatalog Versions\nApplication Tools\nApplication Tools\nUser Customization.\nUser Customization.\n\n\n\nModification Dates and Times and the Base Product\nFirst Time Export to AVEVA Bocad Steel\nImport from AVEVA Bocad Steel\nSubsequent Export to AVEVA Bocad Steel\nRemoval of History Data\nDesign Parameter Sized Profiles\nManaging the Model Limits and Offsets\nInitialization of the ABSI Application\nCatalog Versions\nApplication Tools\nUser Customization\nModification Dates and Times and the Base Product\nFirst Time Export to AVEVA Bocad Steel\nImport from AVEVA Bocad Steel\nSubsequent Export to AVEVA Bocad Steel\nRemoval of History Data\nDesign Parameter Sized Profiles\nManaging the Model Limits and Offsets\nInitialization of the ABSI Application\nCatalog Versions\nApplication Tools\nUser Customization"}
{"Headers": "Modification Dates and Times and the Base Product", "Content": "An important feature of the AVEVA Bocad Steel Interface is the ability to compare and merge elements. In AVEVA Bocad Steel this feature is very dependent on the base product passing the correct modification dates.\nIn the base product Dabacon database there are three different values that could represent the date/time of modification:\nThere are also two UDA values that store the internal and external ID; :FABMARK and :FABEMARK respectively. The latter value is passed in the ABS file as the unique identifier (UUID) by which each system can uniquely identify each element.\nFurther, in order to complete the historical information, the element's Creation date and time are set and passed in the ABS file. As far as the base product is concerned, this is generally the time of the CRDATE or LASTMOD. Once set, the Creation date and time are not modified.\nWhich Modification date and time values we use for transferring in the ABS file are subject to several conditions.\nThe :FABMDATE and :FABMTIME UDA pair, representing some nominal modification date/time;\nThe :FABIDATE and :FABITIME UDA pair representing the Import date/time;\nThe LASTMOD value from the database representing the last time stamp on the Dabacon element. his is set by the SAVEWORK command.\nThe :FABMDATE and :FABMTIME UDA pair, representing some nominal modification date/time;\nThe :FABMDATE and :FABMTIME UDA pair, representing some nominal modification date/time;\nThe :FABIDATE and :FABITIME UDA pair representing the Import date/time;\nThe :FABIDATE and :FABITIME UDA pair representing the Import date/time;\nThe LASTMOD value from the database representing the last time stamp on the Dabacon element. his is set by the SAVEWORK command.\nThe LASTMOD value from the database representing the last time stamp on the Dabacon element. his is set by the SAVEWORK command.\n\n\n\ncorrect"}
{"Headers": "First Time Export to AVEVA Bocad Steel", "Content": "Because any interaction with the database is considered as a change, it is essential to minimize the number of database changes and the time differences between them. For an element that has been created in the base product we have to set at least the Modification date/Time, and the internal and external IDs prior to export. Following export, a SAVEWORK command is executed on the data, as soon as possible after the export, in order to minimize the time difference between the Modification date (the date/time at which the data was extracted from the element), and the time that field was locked on the database by a SAVEWORK. This introduces a time difference - a buffer - between values. The Modification date/time will be the LASTMOD value.\n\n\n\nlocked"}
{"Headers": "Subsequent Export to AVEVA Bocad Steel", "Content": "The challenge now is to determine what has changed since the last export. This is the issue. With so many values of date and time, which do we choose? Here is the algorithm.\nThe value of the buffer is critical. The default value is 3 minutes. However, for larger models, this buffer should be larger, possibly as high as 15 minutes. The buffer does not affect the time difference between export/import transactions, rather it represents the elapsed time of the previous export/import transaction. We cannot store this value in the database, because we do not know to which particular transaction the buffer value would refer. For example, we might import several files of varying size in quick succession, or edit the model outside of the ABSI system.\nTherefore, there is a PML global variable that can be changed by hand using the experience of previous transactions. It can be locally changed in the current base product session using the command below, but it will revert to the default value of 3 minutes on session start-up.\nThere are 3 dates/times IDATE, MDATE, LASTMOD.  (IDATE represents the :FABIDATE and\n         :FABITIME UDA values; MDATE similarly; LASTMOD is the last database SAVEWORK date/time)\nIf MDATE UDA is unset\n      Use LASTMOD as MDATE\nIf IDATE UDA is unset\nUse LASTMOD as IDATE\n-For comparison, find out TESTDATE\nIf the IDATE UDA is set\nuse later of IDATE and MDATE as TESTDATE\nelse\nuse MDATE as TESTDATE (Item has not been imported)\nif ( (TESTDATE + buffer) > LASTMOD )  item has NOT changed within buffer time of the\n         SAVEWORK\n!!bocExpTimBuf = (15)\nNote:\nThis can also be configured in the bocuserdata.pmlfnc user configuration command file.\n\n\n\nThere are 3 dates/times IDATE, MDATE, LASTMOD.  (IDATE represents the :FABIDATE and\n         :FABITIME UDA values; MDATE similarly; LASTMOD is the last database SAVEWORK date/time)\nIf MDATE UDA is unset\n      Use LASTMOD as MDATE\nIf IDATE UDA is unset\nUse LASTMOD as IDATE\n-For comparison, find out TESTDATE\nIf the IDATE UDA is set\nuse later of IDATE and MDATE as TESTDATE\nelse\nuse MDATE as TESTDATE (Item has not been imported)\nif ( (TESTDATE + buffer) > LASTMOD )  item has NOT changed within buffer time of the\n         SAVEWORK\nNote:\n!!bocExpTimBuf = (15)"}
{"Headers": "Removal of History Data", "Content": "There is a facility on the main Import and Export forms to remove the history data on the current element and its children using the menu option below.\n\n\n\n"}
{"Headers": "Design Parameter Sized Profiles", "Content": "When exporting from the base product to Bocad, there must be an entry in the profile mapping file that corresponds to the profile in the base product.\nIf exporting channels (for example: channel_with_design_parameters) or angles (for example: angle_with_design_parameters) you must make sure the ABSI p-lines in the catalogue have been created otherwise issues with offsets from NA p-line will occur.\nIf exporting angle profiles, ensure that the required parameters are placed in the export file by correctly giving the order of parameters in the mapping file. If the thickness of the legs are the same, the parameter must be repeated in the Bocad profile name, for example:\nAngle_with_design_parametersBLL@1@2@3@3@4@5@6@7@8EUR\nIf exporting I (sometimes known as H) profiles (for example: Beam_with_design_parameters), all the design parameters must be completed consistently. If the depth between fillets, flange thickness and overall depth are not consistent, it is possible that the geometry in the base product and Bocad will not be the same. This can be avoided by using the BT_Variable profile supplied with the product (run !!boccatadespar() in PARAGONmodule).\nMapping files are primarily used on import. However the shape code is read from the mapping file when exporting from the base product and the Bocad name is ignored when importing design parameter profiles (those that have @ in the Bocad name) into Bocad.For this reason when re-importing profiles from Bocad into the base product the Bocad name can be different to that in the mapping file.\nFor example BT_Variable might be mapped to BT@3@1@4@2 but be returned as PRS300*50*1000*20.\nIf you add these names to the mapping file (in our example as PRS@3@1@4@2), you will still be able to export these profiles into the base product.\nIt is important to reorder the design parameters into the documented order using the mapping file. To see the order in the base product using the Query>Properties window.\nWhen importing from Bocad to the base product, duplicate Bocad names are not allowed in the mapping file.\n\nI\n1\nBT\nBT300*10*500*20\nDepth\n\nL\n2\nBLL\n\nLeg length Y\n\nZ\n3\nBLZ\n\nDepth\n\nU\n4\nBLU\n\nDepth\n\nPlate\n5\nBL,PL\n\nDepth\n\nFull Tube\n6\nBAR,\nROND,...\n\nOut radius\n\nTube\n7\nCHS,\nTUBE,\nPIPE,...\n\nOut radius\n\nSquare Tube\n8\nMSH,\nTUBER,\nTUBEC\n\nDepth\n\nC\n9\nBLC\n\nDepth\n\nT\n10\nBLT\n\nWidth\n\nCone\n13\nCONE\n\nStart diam\nTable continued:\nPar 2\nPar 3\nPar 4\nPar 5\nWidth\nWeb thick\nFlange thick\nUnit weight\nLeg length X\nThickness Y leg\nThickness X leg\nX-offset\nWeb thick\nWidth\nFlange thick\nX-offset\nWidth\nWeb thick\nFlange thick\nWidth\nThick\nUnit weight\nThick\nUnit weight\nWidth\nWall thick X\nWall thick Y\nUnit weight\nWidth\nWeb thick\nFlange thick\nX-offset\nDepth\nWeb thick\nFlange thick\nDepth to NA\nEnd diam\nWall thick\n\n\nWidth\nWeb thick\nFlange thick\nUnit weight\n\nLeg length X\nThickness Y leg\nThickness X leg\nX-offset\n\nWeb thick\nWidth\nFlange thick\nX-offset\n\nWidth\nWeb thick\nFlange thick\n\n\nWidth\n\n\n\n\nThick\nUnit weight\n\n\n\nThick\nUnit weight\n\n\n\nWidth\nWall thick X\nWall thick Y\nUnit weight\n\nWidth\nWeb thick\nFlange thick\nX-offset\n\nDepth\nWeb thick\nFlange thick\nDepth to NA\n\nEnd diam\nWall thick\n\n\nTable continued:\n\nRoot radius\nCross sectional area\nDepth between fillets\nNominal depth\n\nY-offset\nUnit weight\nRoot radius\nToe radius\n\n\n\n\n\n\nUnit weight\nRoot radius\nToe radius\nFlange taper\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nExternal corner radius\nInternal corner radius\n\n\n\nUnit weight\nRoot radius\nToe radius\nFlange taper\n\nUnit weight\nRoot radius\nNominal width\nNominal depth\n\n\n\n\n\nTable continued:\n\nNominal width\n\n\n\n\nBackmark for bigger leg\nBackmark for smaller leg\n\n\n\n\n\n\n\n\nDepth between fillets\nNominal depth\nNominal width\nBackmark\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nDepth between fillets\nNominal depth\nNominal width\nBackmark\n\nOriginal depth\nOriginal width\nOriginal weight\nBackmark\n\n\n\n\n\nTable continued:\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nSection Type\nBocad Profile Type\nBocad Generic Name\nDenomination\nPar 1\nI\n1\nBT\nBT300*10*500*20\nDepth\nL\n2\nBLL\nLeg length Y\nZ\n3\nBLZ\nDepth\nU\n4\nBLU\nDepth\nPlate\n5\nBL,PL\nDepth\nFull Tube\n6\nBAR,\nROND,...\nOut radius\nTube\n7\nCHS,\nTUBE,\nPIPE,...\nOut radius\nSquare Tube\n8\nMSH,\nTUBER,\nTUBEC\nDepth\nC\n9\nBLC\nDepth\nT\n10\nBLT\nWidth\nCone\n13\nCONE\nStart diam\nPar 2\nPar 3\nPar 4\nPar 5\nWidth\nWeb thick\nFlange thick\nUnit weight\nLeg length X\nThickness Y leg\nThickness X leg\nX-offset\nWeb thick\nWidth\nFlange thick\nX-offset\nWidth\nWeb thick\nFlange thick\nWidth\nThick\nUnit weight\nThick\nUnit weight\nWidth\nWall thick X\nWall thick Y\nUnit weight\nWidth\nWeb thick\nFlange thick\nX-offset\nDepth\nWeb thick\nFlange thick\nDepth to NA\nEnd diam\nWall thick\nPar 6\nPar 7\nPar 8\nPar 9\nRoot radius\nCross sectional area\nDepth between fillets\nNominal depth\nY-offset\nUnit weight\nRoot radius\nToe radius\nUnit weight\nRoot radius\nToe radius\nFlange taper\nExternal corner radius\nInternal corner radius\nUnit weight\nRoot radius\nToe radius\nFlange taper\nUnit weight\nRoot radius\nNominal width\nNominal depth\nPar 10\nPar 11\nPar 12\nPar 13\nNominal width\nBackmark for bigger leg\nBackmark for smaller leg\nDepth between fillets\nNominal depth\nNominal width\nBackmark\nDepth between fillets\nNominal depth\nNominal width\nBackmark\nOriginal depth\nOriginal width\nOriginal weight\nBackmark\nPar 14\n\n\n\nQuery>Properties"}
{"Headers": "Managing the Model Limits and Offsets", "Content": "Exporting to AVEVA Bocad Steel\nImporting from AVEVA Bocad Steel.\nExporting to AVEVA Bocad Steel\nExporting to AVEVA Bocad Steel\nImporting from AVEVA Bocad Steel.\nImporting from AVEVA Bocad Steel.\n\n\n\nExporting to AVEVA Bocad Steel\nImporting from AVEVA Bocad Steel\nExporting to AVEVA Bocad Steel\nImporting from AVEVA Bocad Steel"}
{"Headers": "Exporting to AVEVA Bocad Steel", "Content": "The 3d global limit box of the data to be exported is calculated as the export list is modified. This feedback is for information only to guide you in choosing a suitable model offset for Bocad.\n\nThe model offset position and orientation are stored in a special site in the Application Data World, /FABAPPDW. By default the position is at E0 N0 U0 in world space and the default orientation is \"Y is North and Z is Up\" in world space. This is usually locked to prevent you from accidentally modifying the offset position that has been agreed with the AVEVA Bocad Steel user.\n\nYou can modify the header details by inspecting the chosen header and pressing Edit. Press Apply to update the header data or Cancel leave the header data unchanged.\n\nTo create a new header block, select New header\u2026 from the drop down list.\n\nA new header element is created with default values that can be edited as desired. For convenience it is advised that the header is given a name by which it can be easily identified.\n\n\n\n\nEdit\nApply\nCancel\nNew header\u2026"}
{"Headers": "Importing from AVEVA Bocad Steel", "Content": "Any offset value in the ABS file from Bocad, is taken and set on the offset reference zone.\n\n\n"}
{"Headers": "Initialization of the ABSI Application", "Content": "Sometimes the application might not start up correctly, or even at all. This could be caused by the automatic loading of the configuration file, ABSI.xml. If there are errors in this file, such as certain header elements have been deleted, or options are no longer available, then the initialization might fail. You can delete or rename this file which is found in the user area, the application should then start up with the default settings.\n\n\n"}
{"Headers": "Catalog Versions", "Content": "During the lifetime of this application, updates to the Catalog are quite likely. For example a typical change might be the default orientation of an unequal angle. This has been a cause of problems in the past when operating the application on both PDMS12.1 and AVEVA E3D 2.1\u2122.\nYou can perform a quick check to validate the profile orientation using the following lines either in the command window or as a macro.\nObviously you should change the SPRE to be the profile under investigation. By comparing the view between versions you can see if there is any difference in configuration between versions.\nYou must be aware that the Catalogue update function might need to be changed to locate the Plines correctly according to the Cardinal Points. Refer to Cardinal Points for further information.\nNEW SITE /TestAngleOri\nNEW ZONE\nNEW STRU\nNEW FRMW\nNEW GENSEC SPRE /L100x50x10\nJUSL SNFG\nNEW SPINE\nNEW POINSP at E0\nNEW POINSP at E500\n\n\n\nCardinal Points\nNEW SITE /TestAngleOri\nNEW ZONE\nNEW STRU\nNEW FRMW\nNEW GENSEC SPRE /L100x50x10\nJUSL SNFG\nNEW SPINE\nNEW POINSP at E0\nNEW POINSP at E500\nCardinal Points"}
{"Headers": "Application Tools", "Content": "The application is supplied with the following functions:\nManaging ABSI UDA visibility\nColoring Phases\nSort members according to leading member UUID\nMerging SITES\nUser Customization\nInitialization of the ABSI Application\nCatalog Versions.\nManaging ABSI UDA visibility\nManaging ABSI UDA visibility\nColoring Phases\nColoring Phases\nSort members according to leading member UUID\nSort members according to leading member UUID\nMerging SITES\nMerging SITES\nUser Customization\nUser Customization\nInitialization of the ABSI Application\nInitialization of the ABSI Application\nCatalog Versions.\nCatalog Versions.\n\n\n\nManaging ABSI UDA visibility\nColoring Phases\nSort members according to leading member UUID\nMerging SITES\nUser Customization\nInitialization of the ABSI Application\nCatalog Versions\nManaging ABSI UDA visibility\nColoring Phases\nSort members according to leading member UUID\nMerging SITES\nUser Customization\nInitialization of the ABSI Application\nCatalog Versions"}
{"Headers": "Managing ABSI UDA visibility", "Content": "For various reasons, the UDAs that are created to manage the ABSI data are normally hidden. If you wish to see them on a one-off basis in the main product you can use the function !!bocshowuda(). To inspect an element, identify and locate the element, type !!bocshowuda() in a command window and the ABSI UDAs listed are listed.\nTo modify their visibility more permanently in LEXICON use the function !!bocvisibleudas(). This has several arguments because this function also works on OpenSteel UDAs. ABSI UDAs have FAB as their prefix, OpenSteel UDAs have SDNF as their prefix.\n!!bocvisibleudas( !prefix, !globalVisibility, !localList)\nWhere:\n!prefix = |SDNF| or |FAB|\nFor SDNF or FAB - goes to either /SDNF-UWRL or /FAB-UWRL\n!globalVisibility = true or false\nTo set ALL SDNF or FAB UDAs visible or invisible\n!localList\nA space separated string list of UDAs to be visible whatever, for example: |FABEMARK FABCRDATE|\n!prefix = |SDNF| or |FAB|\nFor SDNF or FAB - goes to either /SDNF-UWRL or /FAB-UWRL\n!globalVisibility = true or false\nTo set ALL SDNF or FAB UDAs visible or invisible\n!localList\nA space separated string list of UDAs to be visible whatever, for example: |FABEMARK FABCRDATE|\nFor example:\n!!bocvisibleudas( |FAB|, false, |FABEMARK| ), this would hide all ABSI UDAs except :FABEMARK.\n!prefix = |SDNF| or |FAB|\nFor SDNF or FAB - goes to either /SDNF-UWRL or /FAB-UWRL\n!globalVisibility = true or false\nTo set ALL SDNF or FAB UDAs visible or invisible\n!localList\nA space separated string list of UDAs to be visible whatever, for example: |FABEMARK FABCRDATE|\n\n\n\nbocshowuda()\n!!bocshowuda()\n!!bocvisibleudas()\n!!bocvisibleudas( !prefix, !globalVisibility, !localList)\n!!bocvisibleudas( |FAB|, false, |FABEMARK| ),"}
{"Headers": "Sorting into Phases", "Content": "If the imported model has Phase information in the user data from Bocad, you can sort the elements according to Phases.\nFor the purposes of this example, we assume that Bocad has been configured to export phase data in the fields shown. The example PML function supplied is !!bocuserphasesort().\n\nThe user data from Bocad is stored in the UDAs :FABRADATA[1] and :FABTADATA. If the data change, or the location of this information in the user data fields changes, then this function must be modified accordingly. Use the data, the elements will be sorted into FRMW according to their phases.\n\nThe function to perform this task is !!bocuserphasesort. You needs to enter the command in the command window and identify the required element to be sorted.\n!!bocuserphasesort ( )\nFor example:\n!!bocuserphasesort ( ), this will produce a log file called absiphasesort.txt in C:\\temp listing any comments.\n\nThis can take a long time, especially for large models, see below. In this case it is recommended to switch into TTY (non-graphical) mode, and perform the operation there.\n\nYou can then return to the graphical mode to use the Phase colouring function, refer to Coloring Phases for further information.\n\nNote:\nYou are free to modify it if required.\n\n\n\nColoring Phases\nNote:\n!!bocuserphasesort.\n!!bocuserphasesort ( )\n!!bocuserphasesort ( ),\nColoring Phases"}
{"Headers": "Coloring Phases", "Content": "This is a more general function than just colouring phases, it allows you to enhance members and member groups of the current element (CE) in the graphical view.\n!!bocusercolour( !level, !startColour )\nThe !level argument determines how many levels down in the hierarchy you wish to differentiate the members:\nLevel 1\nColours only the immediate children of the CE.\nLevel 3\nColours up to 3 levels down.\nPhase Sorting\nThe !startColour is a starting value of the colour number for the colouring sequence.\nLevel 1\nColours only the immediate children of the CE.\nLevel 3\nColours up to 3 levels down.\nPhase Sorting\nThe !startColour is a starting value of the colour number for the colouring sequence.\nThe following sequence shows the effect of different level settings on the colouring. The first image is of the raw state.\n\n\n\n\n\n\nLevel 1\nColours only the immediate children of the CE.\nLevel 3\nColours up to 3 levels down.\nPhase Sorting\nThe !startColour is a starting value of the colour number for the colouring sequence.\n\n\n\n\n!!bocusercolour( !level, !startColour )"}
{"Headers": "Sort members according to leading member UUID", "Content": "This user function is aimed at the situation where the main steelwork has been designed in PDMS, and exported to Bocad for detailing.\nThe detail plates are added to the model in Bocad and associated with a main member. In Bocad terms this is referred to as the leading member. In this situation a different set of user data is required to associate the new elements with the leading member.\n\nWith this information, new elements that have the leading member\u2019s UUID set can be moved into the existing PDMS database hierarchy to be alongside the owning member.\n\nUsing the leading member\u2019s UUID and the :FABEMARK, the child element is moved to the right place in the hierarchy. As before, if this data is in another slot in the user data set, then the function must be changed. When at the suitable element in the hierarchy, you can sort the data, to do this, type the following command in the Command Window:\n!!bocusersortwuuid( )\n\nFor example: the stiffener elements have been moved to be with their leading member in the hierarchy.\n\n\n\nCommand Window\n!!bocusersortwuuid( )"}
{"Headers": "Merging SITES", "Content": "You can import parts of the model into different SITEs and then merge them, to do this type the following command in the Command Window:\n!!bocusermergesites( !destination, !source )\nThe !source and !destination variables are database reference numbers of SITES. The merge process takes the members of the source SITE and relocates them into the destination SITE. The function does not work at a lower level than a SITE, although it could be modified easily.\n\n\n\nCommand Window\n!!bocusermergesites( !destination, !source )\n!source\n!destination"}
{"Headers": "User Customization", "Content": "You can manage the hierarchy using Bocad data, to demonstrate the user customization capabilities of the ABSI interface various functions have been supplied that are easily accessible.\n\n\n"}
{"Headers": "Export", "Content": "As a demonstration of the export customization, AVEVA have provided a function that will produce a comma separated variable file, a CSV file of the hierarchy on each principal element exported. This might be useful for reporting purposes of for Bocad itself in managing the model. This is accessed by attaching the !!bocpostexport function. From the ABSI Export window, navigate to the ABSI - System Configuration window.\n\nFrom the ABSI - System Configuration window, select the Macros tab enter the Post export Macro Name.\n\nFollowing an export procedure, a CSV file is produced alongside the ABSI file, this can then be read by spreadsheet applications that can accept CSV files.\n\n\n\n\n!!bocpostexport\nABSI Export\nABSI - System Configuration\nABSI - System Configuration\nMacros\nPost export Macro Name"}
{"Headers": "Import", "Content": "An example of customization is included in the application, this can be accessed by setting the import pre- and post- processing functions to be bocpreimport and bocpostimport respectively.\n\nThe pre- import function is called after you have initiated the import process and checks whether the target storage location is empty. This is because there are different processing options depending on whether the target storage location is empty or not.\nIf the storage location is empty the application sorts all incoming entities according to phases. This is because the model has been created in Bocad. Refer to Sorting into Phases for further information.\nIf the storage location already has something in it, the data imported from Bocad will be merged into the existing model. In this case, the new details that have been associated with existing members are moved into the same location in the database hierarchy. All members are sorted according to UUID, all other members that have been newly imported from Bocad are sorted into phases. Refer to Sort members according to leading member UUID and Sorting into Phases for further information.\n\n\n\nSorting into Phases\nSort members according to leading member UUID\nSorting into Phases\nSorting into Phases\nSort members according to leading member UUID\nSorting into Phases"}
{"Headers": "Structural Design", "Content": "The Structural Design User Guide introduces some of the facilities provided by the application for the design and documentation of logically interconnected structures. It explains the main application concepts and the applications that support it, and indicates how to apply these to design projects.\nThe structural applications offer these key benefits:\nStructures is an umbrella to four applications supplied within the AVEVA E3D Design suite. The applications within structures allows you to build up detailed and complex structures within a full 3D environment.\nThe Structures comprises four applications:\nThe applications are designed to use specification data when structural components are selected from the Catalogue database, so that design consistency and conformity to standards are maintained. It is important, therefore, that the structural Catalogue databases are properly maintained.\nStructural elements are named in accordance with a predefined set of rules, so that their positions in the database hierarchy are always obvious without the need to input specific texts during the design process.\nWhen grid storage mode is used, structural elements are automatically stored in the appropriate hierarchy.\nTemporary lists of elements can be set up, so that a design operation can be carried out on all elements within the list simultaneously. A great deal of repetitive work can be avoided when commonly-repeated design modifications are carried out.\nThe applications incorporate a number of geometric design aids, such as 3D reference grids, to make it easy to position structural elements accurately within the 3D model.\nWhere possible, the Model applications create and maintain connectivity of the structural network automatically.\nNon-standard structural components, such as complex panels and floor plates, may be created by defining the required shape as a 2D profile and then extruding this to the desired thickness.\nNegative primitives and shapes may be used in the structural catalogue to define complex joint geometry and end preparations for structural sections, so that weld preparations and fitting allowances can be modelled easily.\nTemplates may be used to define the basic structure of built-up girders and similar components, so that the detailed design of such items becomes a matter of inputting the required dimensional and positional data.\nMultiple copies of design components may be created by specifying the number of copies required and their relative positions and orientations. For example, a complete roof structure can be created by designing a single roof truss and then, in one operation, making as many copies as are necessary to support the length of the roof, with each truss displaced by a given distance relative to the preceding one.\nMuch repetitive work can be avoided in symmetrical designs by making copies of interconnected parts of the structure and reflecting them about specified axes, so that the design pattern is repeated as required.\nJoint positions may be finely adjusted to make sure they are assembled accurately, using any standard datum line to define the precise alignment of a joint with its attached sections.\nSections and panels (for example, wall plates and floor plates) may be divided at intersections, after the overall size and shape have been defined, without affecting any of their logical interconnections. The \u2018macrostructure\u2019 (for example, complete areas to be covered) can be designed first and then subdivided into a manageable \u2018microstructure\u2019 for fabrication purposes at a later stage (typically, to make the most efficient use of stock panel sizes). The edges of panels may be notched to fit around section profiles, and the edges of adjacent panels may be shaped such they interlock automatically.\nPenetrations may be created as catalogue elements. A penetration can incorporate appropriate sleeving or kick plates, and may be inserted into a structural section or panel as a complete entity, with the dimensions and position of the penetration derived automatically from the dimensions of the pipe/duct/cable tray passing though it.\nMulti-disciplinary clash checks can be carried out at any stage of the design, thus avoiding spatial conflicts within the overall 3D model which can be expensive to rectify at the construction stage. These clash checks are particularly important where different features of the 3Dmodel are under the control of different designers.\nAt any stage of the design, reports can be created listing specified data from the current database. A standard report template can be specified, so that lists of commonly-required information can be derived very quickly, or report format can be designed to suit a particular need. The resultant output, which can include data from any design discipline, sorted as required, can be either displayed on the screen or sent to a file (for storage and/or for printing).\nThe applications are designed to use specification data when structural components are selected from the Catalogue database, so that design consistency and conformity to standards are maintained. It is important, therefore, that the structural Catalogue databases are properly maintained.\nThe applications are designed to use specification data when structural components are selected from the Catalogue database, so that design consistency and conformity to standards are maintained. It is important, therefore, that the structural Catalogue databases are properly maintained.\nStructural elements are named in accordance with a predefined set of rules, so that their positions in the database hierarchy are always obvious without the need to input specific texts during the design process.\nStructural elements are named in accordance with a predefined set of rules, so that their positions in the database hierarchy are always obvious without the need to input specific texts during the design process.\nWhen grid storage mode is used, structural elements are automatically stored in the appropriate hierarchy.\nWhen grid storage mode is used, structural elements are automatically stored in the appropriate hierarchy.\nTemporary lists of elements can be set up, so that a design operation can be carried out on all elements within the list simultaneously. A great deal of repetitive work can be avoided when commonly-repeated design modifications are carried out.\nTemporary lists of elements can be set up, so that a design operation can be carried out on all elements within the list simultaneously. A great deal of repetitive work can be avoided when commonly-repeated design modifications are carried out.\nThe applications incorporate a number of geometric design aids, such as 3D reference grids, to make it easy to position structural elements accurately within the 3D model.\nThe applications incorporate a number of geometric design aids, such as 3D reference grids, to make it easy to position structural elements accurately within the 3D model.\nWhere possible, the Model applications create and maintain connectivity of the structural network automatically.\nWhere possible, the Model applications create and maintain connectivity of the structural network automatically.\nNon-standard structural components, such as complex panels and floor plates, may be created by defining the required shape as a 2D profile and then extruding this to the desired thickness.\nNon-standard structural components, such as complex panels and floor plates, may be created by defining the required shape as a 2D profile and then extruding this to the desired thickness.\nNegative primitives and shapes may be used in the structural catalogue to define complex joint geometry and end preparations for structural sections, so that weld preparations and fitting allowances can be modelled easily.\nNegative primitives and shapes may be used in the structural catalogue to define complex joint geometry and end preparations for structural sections, so that weld preparations and fitting allowances can be modelled easily.\nTemplates may be used to define the basic structure of built-up girders and similar components, so that the detailed design of such items becomes a matter of inputting the required dimensional and positional data.\nTemplates may be used to define the basic structure of built-up girders and similar components, so that the detailed design of such items becomes a matter of inputting the required dimensional and positional data.\nMultiple copies of design components may be created by specifying the number of copies required and their relative positions and orientations. For example, a complete roof structure can be created by designing a single roof truss and then, in one operation, making as many copies as are necessary to support the length of the roof, with each truss displaced by a given distance relative to the preceding one.\nMultiple copies of design components may be created by specifying the number of copies required and their relative positions and orientations. For example, a complete roof structure can be created by designing a single roof truss and then, in one operation, making as many copies as are necessary to support the length of the roof, with each truss displaced by a given distance relative to the preceding one.\nMuch repetitive work can be avoided in symmetrical designs by making copies of interconnected parts of the structure and reflecting them about specified axes, so that the design pattern is repeated as required.\nMuch repetitive work can be avoided in symmetrical designs by making copies of interconnected parts of the structure and reflecting them about specified axes, so that the design pattern is repeated as required.\nJoint positions may be finely adjusted to make sure they are assembled accurately, using any standard datum line to define the precise alignment of a joint with its attached sections.\nJoint positions may be finely adjusted to make sure they are assembled accurately, using any standard datum line to define the precise alignment of a joint with its attached sections.\nSections and panels (for example, wall plates and floor plates) may be divided at intersections, after the overall size and shape have been defined, without affecting any of their logical interconnections. The \u2018macrostructure\u2019 (for example, complete areas to be covered) can be designed first and then subdivided into a manageable \u2018microstructure\u2019 for fabrication purposes at a later stage (typically, to make the most efficient use of stock panel sizes). The edges of panels may be notched to fit around section profiles, and the edges of adjacent panels may be shaped such they interlock automatically.\nSections and panels (for example, wall plates and floor plates) may be divided at intersections, after the overall size and shape have been defined, without affecting any of their logical interconnections. The \u2018macrostructure\u2019 (for example, complete areas to be covered) can be designed first and then subdivided into a manageable \u2018microstructure\u2019 for fabrication purposes at a later stage (typically, to make the most efficient use of stock panel sizes). The edges of panels may be notched to fit around section profiles, and the edges of adjacent panels may be shaped such they interlock automatically.\nPenetrations may be created as catalogue elements. A penetration can incorporate appropriate sleeving or kick plates, and may be inserted into a structural section or panel as a complete entity, with the dimensions and position of the penetration derived automatically from the dimensions of the pipe/duct/cable tray passing though it.\nPenetrations may be created as catalogue elements. A penetration can incorporate appropriate sleeving or kick plates, and may be inserted into a structural section or panel as a complete entity, with the dimensions and position of the penetration derived automatically from the dimensions of the pipe/duct/cable tray passing though it.\nMulti-disciplinary clash checks can be carried out at any stage of the design, thus avoiding spatial conflicts within the overall 3D model which can be expensive to rectify at the construction stage. These clash checks are particularly important where different features of the 3Dmodel are under the control of different designers.\nMulti-disciplinary clash checks can be carried out at any stage of the design, thus avoiding spatial conflicts within the overall 3D model which can be expensive to rectify at the construction stage. These clash checks are particularly important where different features of the 3Dmodel are under the control of different designers.\nAt any stage of the design, reports can be created listing specified data from the current database. A standard report template can be specified, so that lists of commonly-required information can be derived very quickly, or report format can be designed to suit a particular need. The resultant output, which can include data from any design discipline, sorted as required, can be either displayed on the screen or sent to a file (for storage and/or for printing).\nAt any stage of the design, reports can be created listing specified data from the current database. A standard report template can be specified, so that lists of commonly-required information can be derived very quickly, or report format can be designed to suit a particular need. The resultant output, which can include data from any design discipline, sorted as required, can be either displayed on the screen or sent to a file (for storage and/or for printing).\nSections\nPlates\nWalls and Floors\nStairs Ladders and Handrails\nSections\nSections\nPlates\nPlates\nWalls and Floors\nWalls and Floors\nStairs Ladders and Handrails\nStairs Ladders and Handrails\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nModel"}
{"Headers": "Structural Defaults", "Content": "Sets the structural application default options for connectivity tolerances, miter tolerance, joint dominance and connection colours.\n\nThe Connectivity Tolerances part of the Structural Settings window sets the default tolerances for structural connections.\nNode merge radius\nInput a dimensional value in the field to define the tolerance at which primary or secondary nodes are merged into a single node upon creation.\nMaximum depth offset\nInput a dimensional value in the field to define the maximum physical distance between elements that are connected or disconnected using dynamic connectivity. The clasher functionality evaluates the value; if elements are not within the tolerance range, they are not connected. Elements that are outside of the tolerance range when moved are disconnected.\nNode merge radius\nInput a dimensional value in the field to define the tolerance at which primary or secondary nodes are merged into a single node upon creation.\nMaximum depth offset\nInput a dimensional value in the field to define the maximum physical distance between elements that are connected or disconnected using dynamic connectivity. The clasher functionality evaluates the value; if elements are not within the tolerance range, they are not connected. Elements that are outside of the tolerance range when moved are disconnected.\nThe miter Tolerance part of the Structural Settings window sets the default tolerances for miterd sections.\nMaximum offset\nInput a dimensional value in the field to define the vertical offset tolerance between the justification lines of miterd sections when they are not co-planar.\nMaximum offset\nInput a dimensional value in the field to define the vertical offset tolerance between the justification lines of miterd sections when they are not co-planar.\nThe Joint Dominance Default part of the Structural Settings window sets the default joint connection properties for connected sections.\nFalse\nSelect the option button to define created joints as subordinate.\nTrue\nSelect the option button to define created joints as dominant.\nFalse\nSelect the option button to define created joints as subordinate.\nTrue\nSelect the option button to define created joints as dominant.\nRefer to Dominant and Subordinate Connections for further information.\nThe Stair Flight Calculate Mode part of the Structural Settings window sets the default properties for creating edge to calculated position stair flights.\nFalse\nSelect the option button to turn edge to calculated position stair flight functionality off.\nTrue\nSelect the option button to turn edge to calculated position stair flight functionality on.\nFalse\nSelect the option button to turn edge to calculated position stair flight functionality off.\nTrue\nSelect the option button to turn edge to calculated position stair flight functionality on.\nRefer to for further information.\nThe Section Default Settings part of the Structural Settings window sets the default Memberline property for creating sections.\nSelect the Default member line to justification line check box to create structural sections with a Memberline property identical to the Justification property defined in the Default Section Specification.\n\nIf the Default member line to justification line check box is not selected, the Memberline property of created structural sections is set to NA.\n\nRefer to Default Section Specification for further information.\nThe Check Connection Colours part of the Structural Settings window sets the default display colours for queried connections.\nBoth ends connected\nDisplays the default colour for elements that are connected at both ends.\nClick the colour palette to modify the default display colour.\nNeither end connected\nDisplays the default colour for elements that are not connected at either end.\nClick the colour palette to modify the default display colour.\nOne end connected\nDisplays the default colour for elements that are connected at one end.\nClick the colour palette to modify the default display colour.\nBoth ends connected\nDisplays the default colour for elements that are connected at both ends.\nClick the colour palette to modify the default display colour.\nNeither end connected\nDisplays the default colour for elements that are not connected at either end.\nClick the colour palette to modify the default display colour.\nOne end connected\nDisplays the default colour for elements that are connected at one end.\nClick the colour palette to modify the default display colour.\nThe Weld Representation part of the Structural Settings window sets the default display settings and tolerances for welds.\nWeld Visible\nSelect the check box to display welds in the 3D view.\nDeselect the check box to turn off the display of welds in the 3D view.\nSize Proportional to connection\nSelect the check box to control the display size of welds in proportion to the connection in the 3D view.\nMove the Proportional Size slider to define the size of the weld.\nDefault Size\nInput a dimensional value in the field to control the display size of welds in 3D view using an explicit value.\nThe functionality becomes available when the Size Proportional to connection check box is deselected.\nNote:\nInserting a value of 0mm removes the display of welds from the 3D view.\nMaximum Tolerance\nInput a dimensional value in the field to define the maximum allowed distance for the creation of welds between panel edges or between panel edges and section edges. The default value is 10mm.\nWeld Visible\nSelect the check box to display welds in the 3D view.\nDeselect the check box to turn off the display of welds in the 3D view.\nSize Proportional to connection\nSelect the check box to control the display size of welds in proportion to the connection in the 3D view.\nMove the Proportional Size slider to define the size of the weld.\nDefault Size\nInput a dimensional value in the field to control the display size of welds in 3D view using an explicit value.\nThe functionality becomes available when the Size Proportional to connection check box is deselected.\nMaximum Tolerance\nInput a dimensional value in the field to define the maximum allowed distance for the creation of welds between panel edges or between panel edges and section edges. The default value is 10mm.\nClick Reset to revert to the values applied when the Structural Settings window was opened.\nClick Apply to accept the default values.\nNode merge radius\nInput a dimensional value in the field to define the tolerance at which primary or secondary nodes are merged into a single node upon creation.\nMaximum depth offset\nInput a dimensional value in the field to define the maximum physical distance between elements that are connected or disconnected using dynamic connectivity. The clasher functionality evaluates the value; if elements are not within the tolerance range, they are not connected. Elements that are outside of the tolerance range when moved are disconnected.\nMaximum offset\nInput a dimensional value in the field to define the vertical offset tolerance between the justification lines of miterd sections when they are not co-planar.\nFalse\nSelect the option button to define created joints as subordinate.\nTrue\nSelect the option button to define created joints as dominant.\nFalse\nSelect the option button to turn edge to calculated position stair flight functionality off.\nTrue\nSelect the option button to turn edge to calculated position stair flight functionality on.\nBoth ends connected\nDisplays the default colour for elements that are connected at both ends.\nClick the colour palette to modify the default display colour.\nNeither end connected\nDisplays the default colour for elements that are not connected at either end.\nClick the colour palette to modify the default display colour.\nOne end connected\nDisplays the default colour for elements that are connected at one end.\nClick the colour palette to modify the default display colour.\nWeld Visible\nSelect the check box to display welds in the 3D view.\nDeselect the check box to turn off the display of welds in the 3D view.\nSize Proportional to connection\nSelect the check box to control the display size of welds in proportion to the connection in the 3D view.\nMove the Proportional Size slider to define the size of the weld.\nDefault Size\nInput a dimensional value in the field to control the display size of welds in 3D view using an explicit value.\nThe functionality becomes available when the Size Proportional to connection check box is deselected.\nNote:\nInserting a value of 0mm removes the display of welds from the 3D view.\nMaximum Tolerance\nInput a dimensional value in the field to define the maximum allowed distance for the creation of welds between panel edges or between panel edges and section edges. The default value is 10mm.\nNote:\nInserting a value of 0mm removes the display of welds from the 3D view.\n\n\n\nDominant and Subordinate Connections\nDefault Section Specification\nConnectivity Tolerances\nStructural Settings\nNode merge radius\nMaximum depth offset\nTolerance\nStructural Settings\nMaximum offset\nJoint Dominance Default\nStructural Settings\nFalse\nTrue\nDominant and Subordinate Connections\nStair Flight Calculate Mode\nStructural Settings\nFalse\nTrue\n\nSection Default Settings\nStructural Settings\nDefault member line to justification line\nDefault member line to justification line\nDefault Section Specification\nCheck Connection Colours\nStructural Settings\nBoth ends connected\nNeither end connected\nOne end connected\nWeld Representation\nStructural Settings\nWeld Visible\nSize Proportional to connection\nProportional Size\nDefault Size\nSize Proportional to connection\nNote:\nMaximum Tolerance\nReset\nStructural Settings\nApply"}
{"Headers": "Hierarchy", "Content": "All database elements are owned by other elements, therefore elements must be created in a strict order.\nThe following database elements are common to all Model disciplines:\nWorld\nSite\nZone.\nWorld\nWorld\nSite\nSite\nZone.\nZone.\n\n\n\nModel"}
{"Headers": "Administrative Hierarchy", "Content": "Below the zone level of the hierarchy, there are three common administrative elements that are only available for selection in the four applications under structures:\nSection and panel elements can be created using grid storage mode which allows for the automatic creation of structural hierarchy elements. Refer to Section and Panel Storage for further information.\nElements created in grid storage mode refer to grid planes and are created as FRMW members. FRMW elements are created automatically when required.\nSTRU elements refer to a reference grid and are automatically created when the first element is positioned on a new reference grid (not associated with a STRU).\nIf the current element is a World, SITE or ZONE, elements are automatically created when the first element is positioned on a new reference grid (not associated with a STRU).\nStructure (STRU)\nFramework (FRMW)\nSub-Frame (SBFR).\nStructure (STRU)\nStructure (STRU)\nFramework (FRMW)\nFramework (FRMW)\nSub-Frame (SBFR).\nSub-Frame (SBFR).\n\n\n\nSection and Panel Storage\nSection and Panel Storage"}
{"Headers": "Create Structure", "Content": "Creates a structure database element.\nA structure element is an administrative element that can own a number of framework elements, this allows structures to be separated for ease of modelling and reporting.\nBefore creating a structure element, the correct database elements must already be present in the Model Explorer, that is a World, Site and Zone must exist. If this is not the case, refer to Getting Started with Plant for a detailed explanation of creating these standard elements.\n\nName/Autoname\nSelect Name from the drop-down list, this allows you to input the name of the structure element or select Autoname.\nPurpose\nAllows you to input the purpose of the structure element. The window displays the default option unset.\nAttributes\nClick to display the Attributes window. Refer to Structure Properties for further information.\nOK\nClick OK to create the structure element in the Model Explorer and close the Create Structure window.\nCancel\nClick Cancel to discard any inputs and close the Create Structure window.\nName/Autoname\nSelect Name from the drop-down list, this allows you to input the name of the structure element or select Autoname.\nPurpose\nAllows you to input the purpose of the structure element. The window displays the default option unset.\nAttributes\nClick to display the Attributes window. Refer to Structure Properties for further information.\nOK\nClick OK to create the structure element in the Model Explorer and close the Create Structure window.\nCancel\nClick Cancel to discard any inputs and close the Create Structure window.\n\nName/Autoname\nSelect Name from the drop-down list, this allows you to input the name of the structure element or select Autoname.\nPurpose\nAllows you to input the purpose of the structure element. The window displays the default option unset.\nAttributes\nClick to display the Attributes window. Refer to Structure Properties for further information.\nOK\nClick OK to create the structure element in the Model Explorer and close the Create Structure window.\nCancel\nClick Cancel to discard any inputs and close the Create Structure window.\n\n\n\nStructure Properties\nName/Autoname\nName\nAutoname\nPurpose\nAttributes\nAttributes\nStructure Properties\nOK\nOK\nCreate Structure\nCancel\nCancel\nCreate Structure"}
{"Headers": "Structure Properties", "Content": "The Properties window displays the default properties for a structure element, modify as required. Refer to Properties for further information.\n\nThe general and positional properties of STRU elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.\nGeometry\nGrid reference\nDisplays the name of the associated reference grid.\nA Nulref value represents a structure element that is not associated with a reference grid.\nGeometry\n\nGrid reference\nDisplays the name of the associated reference grid.\nA Nulref value represents a structure element that is not associated with a reference grid.\n\nGeometry\nGrid reference\nDisplays the name of the associated reference grid.\nA Nulref value represents a structure element that is not associated with a reference grid.\n\n\n\nProperties\nModify Section Properties\nProperties\n.\nProperties\nModify Section Properties\nGeometry\nGrid reference\nNulref"}
{"Headers": "Create Framework", "Content": "Creates a framework database element.\nA framework element is an administrative element that can own a number of components that form a structure. A complex structure can be divided into logical frameworks for ease of modelling and reporting.\nThe database elements that represent physical structural components are:\n\nName/Autoname\nSelect Name from the drop-down list, this allows you to input the name of the framework element or select Autoname.\nPurpose\nAllows you to input the purpose of the framework element. The window displays the default option unset.\nAttributes\nClick to display the Attributes window. Refer to Framework Properties for further information.\nOK\nClick OK to create the framework element in the Model Explorer and close the Create Framework window.\nCancel\nClick Cancel to discard any inputs and close the Create Framework window.\nName/Autoname\nSelect Name from the drop-down list, this allows you to input the name of the framework element or select Autoname.\nPurpose\nAllows you to input the purpose of the framework element. The window displays the default option unset.\nAttributes\nClick to display the Attributes window. Refer to Framework Properties for further information.\nOK\nClick OK to create the framework element in the Model Explorer and close the Create Framework window.\nCancel\nClick Cancel to discard any inputs and close the Create Framework window.\n\nName/Autoname\nSelect Name from the drop-down list, this allows you to input the name of the framework element or select Autoname.\nPurpose\nAllows you to input the purpose of the framework element. The window displays the default option unset.\nAttributes\nClick to display the Attributes window. Refer to Framework Properties for further information.\nOK\nClick OK to create the framework element in the Model Explorer and close the Create Framework window.\nCancel\nClick Cancel to discard any inputs and close the Create Framework window.\nGeneric Section (GENSEC)\nPanel (PANE)\nStair Flight (STRFLT)\nHandrail (HANDRA)\nRung Ladder (RLADDR).\nGeneric Section (GENSEC)\nGeneric Section (GENSEC)\nPanel (PANE)\nPanel (PANE)\nStair Flight (STRFLT)\nStair Flight (STRFLT)\nHandrail (HANDRA)\nHandrail (HANDRA)\nRung Ladder (RLADDR).\nRung Ladder (RLADDR).\n\n\n\nFramework Properties\nName/Autoname\nName\nAutoname\nPurpose\nAttributes\nAttributes\nFramework Properties\nOK\nOK\nCreate Framework\nCancel\nCancel\nCreate Framework"}
{"Headers": "Framework Properties", "Content": "The Properties window displays the default properties for a framework element, modify as required. Refer to Properties for further information.\n\nThe general and specification properties of FRMW elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.\nGeometry\nGrid reference\nDisplays the name of the associated grid plane.\nA Nulref value represents a framework element that is not associated with a grid plane.\nGeometry\n\nGrid reference\nDisplays the name of the associated grid plane.\nA Nulref value represents a framework element that is not associated with a grid plane.\n\nGeometry\nGrid reference\nDisplays the name of the associated grid plane.\nA Nulref value represents a framework element that is not associated with a grid plane.\n\n\n\nProperties\nModify Section Properties\nProperties\nProperties\nModify Section Properties\nGeometry\nGrid reference\nNulref"}
{"Headers": "Create Sub-Frame", "Content": "Creates a sub-frame database element.\nA sub-frame element is an optional administrative element that can own a number of components that form a structure. A complex framework can be divided into logical sub-frameworks for ease of modelling and reporting.\n\nName/Autoname\nSelect Name from the drop-down list, this allows you to input the name of the sub-frame element or select Autoname.\nPurpose\nAllows you to input the purpose of the sub-frame element. The window displays the default option unset.\nAttributes\nClick to display the Attributes window. Refer to Sub-Frame Properties for further information.\nOK\nClick OK to create the sub-frame element in the Model Explorer and close the Create Sub-Frame window.\nCancel\nClick Cancel to discard any inputs and close the Create Sub-Frame window.\nName/Autoname\nSelect Name from the drop-down list, this allows you to input the name of the sub-frame element or select Autoname.\nPurpose\nAllows you to input the purpose of the sub-frame element. The window displays the default option unset.\nAttributes\nClick to display the Attributes window. Refer to Sub-Frame Properties for further information.\nOK\nClick OK to create the sub-frame element in the Model Explorer and close the Create Sub-Frame window.\nCancel\nClick Cancel to discard any inputs and close the Create Sub-Frame window.\n\nName/Autoname\nSelect Name from the drop-down list, this allows you to input the name of the sub-frame element or select Autoname.\nPurpose\nAllows you to input the purpose of the sub-frame element. The window displays the default option unset.\nAttributes\nClick to display the Attributes window. Refer to Sub-Frame Properties for further information.\nOK\nClick OK to create the sub-frame element in the Model Explorer and close the Create Sub-Frame window.\nCancel\nClick Cancel to discard any inputs and close the Create Sub-Frame window.\n\n\n\nSub-Frame Properties\nName/Autoname\nName\nAutoname\nPurpose\nAttributes\nAttributes\nSub-Frame Properties\nOK\nOK\nCreate Sub-Frame\nCancel\nCancel\nCreate Sub-Frame"}
{"Headers": "Sub-Frame Properties", "Content": "The Properties window displays the default properties for a sub-frame element, modify as required. Refer to Properties for further information.\n\nThe general and specification properties of SBFR elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.\nGeometry\nGrid reference\nDisplays the name of the associated grid plane.\nA Nulref value represents a sub-frame element that is not associated with a grid plane.\nGeometry\n\nGrid reference\nDisplays the name of the associated grid plane.\nA Nulref value represents a sub-frame element that is not associated with a grid plane.\n\nGeometry\nGrid reference\nDisplays the name of the associated grid plane.\nA Nulref value represents a sub-frame element that is not associated with a grid plane.\n\n\n\nProperties\nModify Section Properties\nProperties\nProperties\nModify Section Properties\nGeometry\nGrid reference\nA Nulref"}
{"Headers": "Model-to-Catalog Cross-Reference", "Content": "To make sure design consistency and conformity with company standards, the basic definitions of all items which can be used in the structural design are held in a Catalog database. The database holds definitions of all available profiles and materials for structural columns/beams/bracing, all standard types of joint, and all auxiliary fittings. When an item is added to a 3D model, the item position and orientation is stored in the database, but the physical properties of the item are specified by the setting up of a cross-reference (called a Specification Reference or SpecRef) which points to an appropriate entry in the Catalog database.\n\n\n\nCatalog\nSpecification Reference\nSpecRef\nCatalog"}
{"Headers": "Sections", "Content": "The Sections application allows you to create and modify structural sections. Fittings and joints can be specified and section connections defined.\n\n\n"}
{"Headers": "Section Settings", "Content": "Before a structure can be designed, various settings must be defined to determine, for example, the default structural components for creation of structural sections.\n\n\n"}
{"Headers": "Default Section Specification", "Content": "Sets the default specification for the creation of structural sections. The default specification fields can be populated with values from a picked section. The default specification field values can also be applied to existing sections.\nThe following default structural components, can be defined:\n\nA series of drop-down lists allows you to define the default section specification.\nStructural Classification\nInput a value in the field or select the default structural classification from the drop-down list to be used for the creation of structural sections.\nDefault Material\nInput a value in the field or select the default material from the drop-down list to be used for the creation of structural sections.\nThe materials drop-down list is populated with the materials that are associated with the currently selected specification.\nDefault Justification\nInput a value in the field or select the default justification from the drop-down list to be used for the creation of structural sections.\nFor example, select CTOP from the drop-down list to justify the section to the centre top P-line.\nThe justification drop-down list is populated with the justification options that are associated with the currently selected profile.\nFunctionality is available to create structural sections with a Memberline property identical to the Justification property. Refer to Structural Defaults for further information\nProfile Specification\nInput a value in the field or select the default specification from the drop-down list to be used for the creation of structural sections.\nWhen a new default specification is selected, the type and profile drop-down lists are populated with the components that were used when the specification was most recently selected.\nGeneric Type\nInput a value in the field or select the default type from the drop-down list to be used for the creation of structural sections.\nThe type drop-down list is populated with the section types that are associated with the currently selected specification.\nProfile\nInput a value in the field or select the default profile from the drop-down list to be used for the creation of structural sections.\nThe profile drop-down list is populated with the section types that are associated with the currently selected specification. The three profiles that were most recently used in the current session display at the top of the drop-down list.\nProfile Properties\nAllows you to modify the property values of the default profile. Refer to Modify Properties for further information.\n\nStructural Classification\nInput a value in the field or select the default structural classification from the drop-down list to be used for the creation of structural sections.\n\nDefault Material\nInput a value in the field or select the default material from the drop-down list to be used for the creation of structural sections.\nThe materials drop-down list is populated with the materials that are associated with the currently selected specification.\n\nDefault Justification\nInput a value in the field or select the default justification from the drop-down list to be used for the creation of structural sections.\nFor example, select CTOP from the drop-down list to justify the section to the centre top P-line.\nThe justification drop-down list is populated with the justification options that are associated with the currently selected profile.\nFunctionality is available to create structural sections with a Memberline property identical to the Justification property. Refer to Structural Defaults for further information\n\nProfile Specification\nInput a value in the field or select the default specification from the drop-down list to be used for the creation of structural sections.\nWhen a new default specification is selected, the type and profile drop-down lists are populated with the components that were used when the specification was most recently selected.\n\nGeneric Type\nInput a value in the field or select the default type from the drop-down list to be used for the creation of structural sections.\nThe type drop-down list is populated with the section types that are associated with the currently selected specification.\n\nProfile\nInput a value in the field or select the default profile from the drop-down list to be used for the creation of structural sections.\nThe profile drop-down list is populated with the section types that are associated with the currently selected specification. The three profiles that were most recently used in the current session display at the top of the drop-down list.\n\n\nProfile Properties\nAllows you to modify the property values of the default profile. Refer to Modify Properties for further information.\nCopy Defaults from Existing Profile\nClick to populate the default section specification fields with values from a picked section.\nYou are prompted to Select section\nClick to identify a section using a cursor pick in the 3D view.\nThe Class, Material, Justification, Spec, Type and Profile fields are populated with the default values of the identified section.\nApply Defaults to Existing Profiles\nApplies the values in the default section specification fields to pre-selected sections.\nThe values from the Structural classification, Default material, Default justification, Profile specification, Generic type and Profile fields are applied.\nDefault values can only be applied to GENSEC or SCTN elements.\nIf a selected section is locked or claimed by another user, the default section specification values cannot be applied.\nStructural Classification\nInput a value in the field or select the default structural classification from the drop-down list to be used for the creation of structural sections.\nDefault Material\nInput a value in the field or select the default material from the drop-down list to be used for the creation of structural sections.\nThe materials drop-down list is populated with the materials that are associated with the currently selected specification.\nDefault Justification\nInput a value in the field or select the default justification from the drop-down list to be used for the creation of structural sections.\nFor example, select CTOP from the drop-down list to justify the section to the centre top P-line.\nThe justification drop-down list is populated with the justification options that are associated with the currently selected profile.\nFunctionality is available to create structural sections with a Memberline property identical to the Justification property. Refer to Structural Defaults for further information\nProfile Specification\nInput a value in the field or select the default specification from the drop-down list to be used for the creation of structural sections.\nWhen a new default specification is selected, the type and profile drop-down lists are populated with the components that were used when the specification was most recently selected.\nGeneric Type\nInput a value in the field or select the default type from the drop-down list to be used for the creation of structural sections.\nThe type drop-down list is populated with the section types that are associated with the currently selected specification.\nProfile\nInput a value in the field or select the default profile from the drop-down list to be used for the creation of structural sections.\nThe profile drop-down list is populated with the section types that are associated with the currently selected specification. The three profiles that were most recently used in the current session display at the top of the drop-down list.\nProfile Properties\nAllows you to modify the property values of the default profile. Refer to Modify Properties for further information.\nStructural classification\nDefault material\nDefault justification\nProfile specification\nGeneric type\nProfile\nProfile properties\nStructural classification\nStructural classification\nDefault material\nDefault material\nDefault justification\nDefault justification\nProfile specification\nProfile specification\nGeneric type\nGeneric type\nProfile\nProfile\nProfile properties\nProfile properties\nNote:\nThe prompt does not display if the section element is already selected.\n\n\n\nStructural Defaults\nModify Properties\nStructural Classification\nDefault Material\nDefault Justification\nStructural Defaults\nProfile Specification\nGeneric Type\nProfile\nProfile Properties\nModify Properties\nCopy Defaults from Existing Profile\nSelect section\nNote:\nApply Defaults to Existing Profiles"}
{"Headers": "Snap Points", "Content": "Snap points allow you to position the start point or end point of a created section. Snap points can point to a node, item, Pline or grid. Snap points can also be directional, for example, allowing you to create a section perpendicular to an existing element. You can define the snap points that are available for section creation. Refer to Object Snaps and P-line Filters for further information.\n\n\n\nObject Snaps and P-line Filters\nObject Snaps and P-line Filters"}
{"Headers": "Section and Panel Storage", "Content": "Stores structural sections or panels in a specific area of the hierarchy. Structural sections or panels can be associated with a grid plane or a framework/sub-framework element.\nIf a storage area is not defined prior to creation of a section or panel, an error message displays summarizing the problem.\n\nThere are two different modes available for the storage of structural elements:\nThe state of the structural storage setting (grid storage or manual storage) is saved and restored between sessions.\nIf the structural storage area is locked, then the structure and framework are also saved and restored between sessions.\nThe serialisation file is stored in the AVEVA_DESIGN_USER directory, and is named structural-storage.pmldat.\nGrid Storage\nManual Storage\nGrid Storage\nGrid Storage\nManual Storage\nManual Storage\n\n\n\nGrid Storage\nManual Storage\nGrid Storage\nManual Storage"}
{"Headers": "Grid Storage", "Content": "Sets the structure and grid plane that sections and panels are associated with.\n\nThe Structures and Grid Plane drop-down lists are populated with the association properties of the currently selected section or panel.\nStructures\nDisplays the name of the STRU element that is associated with the currently selected section or panel.\nSelect from the drop down list to identify an alternative STRU.\nGrid Plane\nDisplays the name of the grid plane that is associated with the currently selected section or panel.\nSelect from the drop-down list to identify an alternative grid plane.\nGrid Plane Selection\nSelect Lock from the drop-down list to prevent grid storage area modification. The Structure and Grid Plane drop-down lists become inactive.\nSelect Unlock from the drop-down list to allow grid storage area modification. The Structure and Grid Plane drop-down lists become active.\nStructures\nDisplays the name of the STRU element that is associated with the currently selected section or panel.\nSelect from the drop down list to identify an alternative STRU.\nGrid Plane\nDisplays the name of the grid plane that is associated with the currently selected section or panel.\nSelect from the drop-down list to identify an alternative grid plane.\nGrid Plane Selection\nSelect Lock from the drop-down list to prevent grid storage area modification. The Structure and Grid Plane drop-down lists become inactive.\nSelect Unlock from the drop-down list to allow grid storage area modification. The Structure and Grid Plane drop-down lists become active.\nIf a section or panel is moved, the associated grid storage area is updated to reflect the new grid plane.\nIf a section or panel is copied, the associated grid storage area is updated to reflect the new grid plane.\nIf multiple sections or panels are moved or copied and one of the grid storage areas is locked, the moved/new sections/panels are all associated with the locked grid storage area.\nStructures\nDisplays the name of the STRU element that is associated with the currently selected section or panel.\nSelect from the drop down list to identify an alternative STRU.\nGrid Plane\nDisplays the name of the grid plane that is associated with the currently selected section or panel.\nSelect from the drop-down list to identify an alternative grid plane.\nGrid Plane Selection\nSelect Lock from the drop-down list to prevent grid storage area modification. The Structure and Grid Plane drop-down lists become inactive.\nSelect Unlock from the drop-down list to allow grid storage area modification. The Structure and Grid Plane drop-down lists become active.\n\n\n\nStructures\nGrid Plane\nStructures\nGrid Plane\nGrid Plane Selection\nLock\nStructure\nGrid Plane\nUnlock\nStructure\nGrid Plane"}
{"Headers": "Manual Storage", "Content": "Sets the structure and framework/sub-framework elements that sections or panels are associated with.\n\nSelect a FRMW or SBFR element in the Model Explorer to populate the Structure and Storage drop-down lists.\nStructure\nDisplays the name of the STRU element that is associated with the currently selected section or panel.\nSelect from the drop down list to identify an alternative STRU.\nStorage Area\nDisplays the name of the FRMW or SBFR element that owns the currently selected section or panel.\nSelect from the drop down list to identify an alternative FRMW or SBFR.\nStorage Selection\nSelect Lock from the drop-down list to prevent storage area modification. The Structure and Storage Area drop-down lists become inactive.\nSelect Unlock from the drop-down list to allow storage area modification. The Structure and Storage Area drop-down lists become active.\nStructure\nDisplays the name of the STRU element that is associated with the currently selected section or panel.\nSelect from the drop down list to identify an alternative STRU.\nStorage Area\nDisplays the name of the FRMW or SBFR element that owns the currently selected section or panel.\nSelect from the drop down list to identify an alternative FRMW or SBFR.\nStorage Selection\nSelect Lock from the drop-down list to prevent storage area modification. The Structure and Storage Area drop-down lists become inactive.\nSelect Unlock from the drop-down list to allow storage area modification. The Structure and Storage Area drop-down lists become active.\nIf a section or panel is moved, the associated manual storage area is unchanged.\nIf a section or panel is copied, the new section is associated with the same manual storage area as the original section.\nIf multiple sections or panels are moved or copied and one of the manual storage areas is locked, the moved/new sections/panels are all associated with the locked manual storage area.\nStructure\nDisplays the name of the STRU element that is associated with the currently selected section or panel.\nSelect from the drop down list to identify an alternative STRU.\nStorage Area\nDisplays the name of the FRMW or SBFR element that owns the currently selected section or panel.\nSelect from the drop down list to identify an alternative FRMW or SBFR.\nStorage Selection\nSelect Lock from the drop-down list to prevent storage area modification. The Structure and Storage Area drop-down lists become inactive.\nSelect Unlock from the drop-down list to allow storage area modification. The Structure and Storage Area drop-down lists become active.\n\n\n\nStructure\nStorage\nStructure\nStorage Area\nStorage Selection\nLock\nStructure\nStorage Area\nStructure\nStorage Area"}
{"Headers": "Create Sections", "Content": "Each structural column or beam displays in the 3D model as a section (GENSEC) element. Each straight or curved section comprises straight and curved segments and its geometry is defined by extruding a 2D catalogue profile along a path. The path lies on a plane and is represented by a SPINE element, owned by the GENSEC, whose route is specified by a sequence of Spine Points (POINSP).\nPOINSPs are created at the start, the end and at each change of direction. Each segment linking adjacent spine points can be a straight line or circular arc achieved by inserting Curve (CURVE) elements.\nGENSECs can be connected to other GENSEC elements, fittings and joints can also be applied to them.\nA GENSEC element can be owned by a FRMW or a SBFR element and each element which makes up a GENSEC element has attributes unique to each of them.\n\nGENSEC\nA GENSEC can represent any component whose geometry is defined by sweeping a 2D profile along a linear or curved path (its SPINE element). It has a uniform cross-section along its length, defined by reference to a Catalogue Profile element.\nSPINE\nA SPINE defines the path through which a cross-sectional Profile must be swept to generate a GENSEC. The route of the Spine is defined by a sequence of Spine Points (POINSP): one at the start, one at the end, and one at each change of direction. Each segment linking adjacent Spine Points can be either a straight line or an arc of a circle: the latter is achieved by the insertion of a CURVE element. In its simplest form, the SPINE is defined as a line between two fixed points. In its more general form, where the SPINE consists of a sequence of straight and/or curved segments, it can represent, for example, curved beams or curved walls.\nPOINSP\nA POINSP element defines the start and end of a SPINE path, and any location along the path at which there is a change of direction.\nCURVE\nA CURVE element defines a segment of a SPINE path. It defines the geometry of the SPINE between the POINSPs either side of it in the members list.\n\nThe geometry of a section is defined by two types of properties setting:\n\nTo provide a method for referring to individual edges and faces of a section, each is identified by a named line which runs along the length and curve of the section. These reference lines (which are derived from the section\u2019s profile definition in the catalogue) are called Plines. As an example, some of the most commonly used p-lines for an I-shaped Profile might be positioned and named as:\n\nNodes\nThe application uses the concept of Nodes to represent basic analytical points within a structure. Nodes have two main functions:\nIts cross-section is defined by reference to a Specification Reference (SPREF) element (for example, I\u2011beam, T-section and Channel).\nAll other aspects of its geometry are defined by setting specific design properties (in most cases these are set automatically by the application as the 3D model is manipulated graphically). Two of the most important properties are the Start Position and the End Position, since the positions of these points effectively determine the length and orientation of the item.\nIts cross-section is defined by reference to a Specification Reference (SPREF) element (for example, I\u2011beam, T-section and Channel).\nIts cross-section is defined by reference to a Specification Reference (SPREF) element (for example, I\u2011beam, T-section and Channel).\nAll other aspects of its geometry are defined by setting specific design properties (in most cases these are set automatically by the application as the 3D model is manipulated graphically). Two of the most important properties are the Start Position and the End Position, since the positions of these points effectively determine the length and orientation of the item.\nAll other aspects of its geometry are defined by setting specific design properties (in most cases these are set automatically by the application as the 3D model is manipulated graphically). Two of the most important properties are the Start Position and the End Position, since the positions of these points effectively determine the length and orientation of the item.\nTo identify the points at which logical connections are made between adjoining sections.\nTo define how applied stresses can affect individual points in the structure (for passing design data to separate stress analysis programs).\nTo identify the points at which logical connections are made between adjoining sections.\nTo identify the points at which logical connections are made between adjoining sections.\nTo define how applied stresses can affect individual points in the structure (for passing design data to separate stress analysis programs).\nTo define how applied stresses can affect individual points in the structure (for passing design data to separate stress analysis programs).\nNote:\nRefer to Structural Catalog for further information.\n\n\n\nStructural Catalog\nGENSEC\nSPINE\nPOINSP\nCURVE\nSpecification Reference\nStart Position\nEnd Position\nPlines\nI\n-\nNote:\nStructural Catalog\nNodes\nNodes"}
{"Headers": "Straight Sections", "Content": "Creates a straight section.\n\n\n"}
{"Headers": "Create Single Straight Section", "Content": "Creates a single straight section with a defined start point and end point.\nYou are prompted to Start point or\nInput values in the dimension fields and press Enter or click to identify the start position.\nYou are then prompted to End point or\nInput values in the dimension fields and press Enter or click to identify the end position. A straight section is created and displays in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nContinuous\nPress the down arrow key and select Continuous to create multiple straight sections. The start point of each new created section is positioned at the end point of the previously created section. Refer to Create Continuous Straight Sections for further information.\nRepeat\nPress the down arrow key and select Repeat to create multiple straight sections. You must define the start point and end point of each created section. Refer to Create Multiple Straight Sections for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle\nInput an angular value in the field and press Enter to set the angle of the section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nContinuous\nPress the down arrow key and select Continuous to create multiple straight sections. The start point of each new created section is positioned at the end point of the previously created section. Refer to Create Continuous Straight Sections for further information.\nRepeat\nPress the down arrow key and select Repeat to create multiple straight sections. You must define the start point and end point of each created section. Refer to Create Multiple Straight Sections for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle\nInput an angular value in the field and press Enter to set the angle of the section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nThe new GENSEC element displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nContinuous\nPress the down arrow key and select Continuous to create multiple straight sections. The start point of each new created section is positioned at the end point of the previously created section. Refer to Create Continuous Straight Sections for further information.\nRepeat\nPress the down arrow key and select Repeat to create multiple straight sections. You must define the start point and end point of each created section. Refer to Create Multiple Straight Sections for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle\nInput an angular value in the field and press Enter to set the angle of the section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\n\n\nCreate Continuous Straight Sections\nCreate Multiple Straight Sections\nNon-Routed Item\nStart point or\nEnter\nEnd point or\nEnter\nESC\nContinuous\nContinuous\nCreate Continuous Straight Sections\nRepeat\nRepeat\nCreate Multiple Straight Sections\nMirror\nMirror\nBeta\nBeta\nBeta angle\nEnter\nParallel\nParallel\nBack\nBack\nPerpendicular\nPerpendicular\nNon-Routed Item"}
{"Headers": "Create Continuous Straight Sections", "Content": "Creates continuous straight sections where the start point of each new created section is positioned at the end point of the previously created section.\nYou are prompted to Start point or\nInput values in the dimension fields and press Enter or click to identify the start position.\nYou are then prompted to End point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the end position.\nThe prompt is repeated, allowing you to create multiple sections.\nInput F at the prompt and press Enter to end the command. Multiple straights sections are created and display in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\n\nSingle\nPress the down arrow key and select Single to create a single straight section. Refer to Create Single Straight Section for further information.\nRepeat\nPress the down arrow key and select Repeat to create multiple straight sections. You must define the start point and end point of each created section. Refer to Create Multiple Straight Sections for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nSingle\nPress the down arrow key and select Single to create a single straight section. Refer to Create Single Straight Section for further information.\nRepeat\nPress the down arrow key and select Repeat to create multiple straight sections. You must define the start point and end point of each created section. Refer to Create Multiple Straight Sections for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nThe new GENSEC elements display in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nSingle\nPress the down arrow key and select Single to create a single straight section. Refer to Create Single Straight Section for further information.\nRepeat\nPress the down arrow key and select Repeat to create multiple straight sections. You must define the start point and end point of each created section. Refer to Create Multiple Straight Sections for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\n\n\nCreate Single Straight Section\nCreate Multiple Straight Sections\nNon-Routed Item\nStart point or\nEnter\nEnd point or <Finish>\nEnter\nF\nEnter\nESC\nSingle\nSingle\nCreate Single Straight Section\nRepeat\nRepeat\nCreate Multiple Straight Sections\nMirror\nMirror\nBeta\nBeta\nBeta angle <#>\nEnter\nParallel\nParallel\nBack\nBack\nFinish\nFinish\nPerpendicular\n\nNon-Routed Item"}
{"Headers": "Create Multiple Straight Sections", "Content": "Creates multiple straight sections with defined start and end points.\nYou are prompted to Start point or\nInput values in the dimension fields and press Enter or click to identify the start position.\nYou are then prompted to End point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the end position.\nThe section creation process is repeated, allowing you to create multiple sections with defined start and end points.\nInput F at the prompt and press Enter to end the command. Multiple straights sections are created and display in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nSingle\nPress the down arrow key and select Single to create a single straight section. Refer to Create Single Straight Section for further information.\nContinuous\nPress the down arrow key and select Continuous to create multiple straight sections. The start point of each new created section is positioned at the end point of the previously created section. Refer to Create Continuous Straight Sections for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle\nInput an angular value in the field and press Enter to set the angle of the section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nSingle\nPress the down arrow key and select Single to create a single straight section. Refer to Create Single Straight Section for further information.\nContinuous\nPress the down arrow key and select Continuous to create multiple straight sections. The start point of each new created section is positioned at the end point of the previously created section. Refer to Create Continuous Straight Sections for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle\nInput an angular value in the field and press Enter to set the angle of the section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nThe new GENSEC elements display in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nSingle\nPress the down arrow key and select Single to create a single straight section. Refer to Create Single Straight Section for further information.\nContinuous\nPress the down arrow key and select Continuous to create multiple straight sections. The start point of each new created section is positioned at the end point of the previously created section. Refer to Create Continuous Straight Sections for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle\nInput an angular value in the field and press Enter to set the angle of the section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\n\n\nCreate Single Straight Section\nCreate Continuous Straight Sections\nNon-Routed Item\nStart point or\nEnter\nEnd point or <Finish>\nEnter\nF\nEnter\nESC\nSingle\nSingle\nCreate Single Straight Section\nContinuous\nContinuous\nCreate Continuous Straight Sections\nMirror\nMirror\nBeta\nBeta\nBeta angle\nEnter\nParallel\n\nBack\nBack\nFinish\nFinish\nPerpendicular\n\nNon-Routed Item"}
{"Headers": "Curved Sections", "Content": "Creates a curved section.\n\n\n"}
{"Headers": "Create Free Definition Curved Sections", "Content": "Creates curved sections, any number of points can be selected to change the direction.\nYou are prompted to Start point or\nInput values in the dimension fields and press Enter or click to identify the start position.\nYou are then prompted to Fillet point (R=#mm) or <Radius>\nInput values in the dimension fields and press Enter or click to identify the fillet position.\nYou are then prompted to Fillet point (R=#mm) or <Radius>\nInput values in the dimension fields and press Enter or click to identify the fillet position.\nYou are then prompted to Fillet point (R=#mm) or <Finish>\nThe prompt is repeated, allowing you to create multiple curves.\nInput F at the prompt and press Enter to end the command. A curved section is created and displays in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nFixed angle\nPress the down arrow key and select Fixed angle to create curved sections with a specified fixed angle. Refer to Create Fixed Angle Curved Sections for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the curved section.\nYou are prompted to Curve radius <#>\nInput a dimensional value in the field and press Enter to set the radii of the curved section.\nAngle\nPress the down arrow key and select Angle to create a curved section with a specified angle.\nYou are prompted to Curve angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nFixed angle\nPress the down arrow key and select Fixed angle to create curved sections with a specified fixed angle. Refer to Create Fixed Angle Curved Sections for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the curved section.\nYou are prompted to Curve radius <#>\nInput a dimensional value in the field and press Enter to set the radii of the curved section.\nAngle\nPress the down arrow key and select Angle to create a curved section with a specified angle.\nYou are prompted to Curve angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new GENSEC element displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nFixed angle\nPress the down arrow key and select Fixed angle to create curved sections with a specified fixed angle. Refer to Create Fixed Angle Curved Sections for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the curved section.\nYou are prompted to Curve radius <#>\nInput a dimensional value in the field and press Enter to set the radii of the curved section.\nAngle\nPress the down arrow key and select Angle to create a curved section with a specified angle.\nYou are prompted to Curve angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nCreate Fixed Angle Curved Sections\nNon-Routed Item\nStart point or\nEnter\nFillet point (R=#mm) or <Radius>\nEnter\nFillet point (R=#mm) or <Radius>\nEnter\nFillet point (R=#mm) or <Finish>\nF\nEnter\nESC\nFixed angle\nFixed angle\nCreate Fixed Angle Curved Sections\nRadius\nRadius\nCurve radius <#>\nEnter\nAngle\nAngle\nCurve angle <#>\nEnter\nMirror\nMirror\nBeta\nBeta\nBeta angle <#>\nEnter\nParallel\n\nBack\nBack\nPerpendicular\nPerpendicular\nFinish\nFinish\nNon-Routed Item"}
{"Headers": "Create Fixed Angle Curved Sections", "Content": "Creates curved sections with a specified fixed angle, a fillet with the specified radius can be included.\nYou are prompted to Start point or\nInput values in the dimension fields and press Enter or click to identify the start position.\nYou are then prompted to Fillet point (A=#,R=#mm) or <Radius>\nInput values in the dimension fields and press Enter or click to identify the fillet position.\nYou are then prompted to Fillet point (A=#,R=#mm) or <Radius>\nInput values in the dimension fields and press Enter or click to identify the fillet position.\nYou are then prompted to Fillet point (A=#,R=#mm) or <Finish>\nInput values in the dimension fields and press Enter or click to identify the fillet position.\nThe prompt is repeated, allowing you to create multiple curves.\nInput F at the prompt and press Enter to end the command. A curved section is created and displays in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nFree definition\nPress the down arrow key and select Free definition to create curved sections without a fixed angle. Refer to Create Free Definition Curved Sections for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the curved section.\nYou are prompted to Curve radius <#>\nInput a dimensional value in the field and press Enter to set the radii of the curved section.\nAngle\nPress the down arrow key and select Angle to create a curved section with a specified angle.\nYou are prompted to Curve angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nFree definition\nPress the down arrow key and select Free definition to create curved sections without a fixed angle. Refer to Create Free Definition Curved Sections for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the curved section.\nYou are prompted to Curve radius <#>\nInput a dimensional value in the field and press Enter to set the radii of the curved section.\nAngle\nPress the down arrow key and select Angle to create a curved section with a specified angle.\nYou are prompted to Curve angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new GENSEC element displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nFree definition\nPress the down arrow key and select Free definition to create curved sections without a fixed angle. Refer to Create Free Definition Curved Sections for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the curved section.\nYou are prompted to Curve radius <#>\nInput a dimensional value in the field and press Enter to set the radii of the curved section.\nAngle\nPress the down arrow key and select Angle to create a curved section with a specified angle.\nYou are prompted to Curve angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the curved section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nCreate Free Definition Curved Sections\nNon-Routed Item\nStart point or\nEnter\nFillet point (A=#,R=#mm) or <Radius>\nEnter\nFillet point (A=#,R=#mm) or <Radius>\nEnter\nFillet point (A=#,R=#mm) or <Finish>\nEnter\nF\nEnter\nESC\nFree definition\nFree definition\nCreate Free Definition Curved Sections\nRadius\nRadius\nCurve radius <#>\nEnter\nAngle\nAngle\nCurve angle <#>\nEnter\nMirror\nMirror\nBeta\nBeta\nBeta angle <#>\nEnter\nParallel\nParallel\nBack\nBack\nPerpendicular\nPerpendicular\nFinish\nFinish\nNon-Routed Item"}
{"Headers": "Create Arc Section with Specified Centre Point and Sweep Angle", "Content": "Creates an arc section with a specified centre point and sweep angle.\nYou are prompted to Centre point or\nInput values in the dimension fields and press Enter or click to identify the centre point position.\nYou are then prompted to Diameter or <Radius>\nInput a dimensional value in the field and press Enter or click to identify the diameter of the arc section.\nYou are then prompted to Start angle or <#deg>\nInput an angular value in the field and press Enter or click to identify the start point.\nYou are then prompted to Sweep angle or <#deg>\nInput an angular value in the field and press Enter or click to identify the end point. An arc section is created and displays in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nEnds + Radius\nPress the down arrow key and select Ends + Radius to create an arc with specified end points and a radius. Refer to Create Arc Section with Specified End Points and Radius for further information.\nThree Point\nPress the down arrow key and select Three Point to create an arc with three specified points. Refer to Create Arc Section with Three Specified Points for further information.\nSemi-Circle\nPress the down arrow key and select Semi-Circle to create a semi-circle arc. Refer to Create Semi-Circle Arc Section for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the arc section.\nYou are prompted to Radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the arc section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create an arc section with a fixed diameter.\nYou are prompted to Diameter or <Radius>\nInput a dimensional value in the field and press Enter to set the diameter of the arc section.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nEnds + Radius\nPress the down arrow key and select Ends + Radius to create an arc with specified end points and a radius. Refer to Create Arc Section with Specified End Points and Radius for further information.\nThree Point\nPress the down arrow key and select Three Point to create an arc with three specified points. Refer to Create Arc Section with Three Specified Points for further information.\nSemi-Circle\nPress the down arrow key and select Semi-Circle to create a semi-circle arc. Refer to Create Semi-Circle Arc Section for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the arc section.\nYou are prompted to Radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the arc section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create an arc section with a fixed diameter.\nYou are prompted to Diameter or <Radius>\nInput a dimensional value in the field and press Enter to set the diameter of the arc section.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nThe new GENSEC displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nEnds + Radius\nPress the down arrow key and select Ends + Radius to create an arc with specified end points and a radius. Refer to Create Arc Section with Specified End Points and Radius for further information.\nThree Point\nPress the down arrow key and select Three Point to create an arc with three specified points. Refer to Create Arc Section with Three Specified Points for further information.\nSemi-Circle\nPress the down arrow key and select Semi-Circle to create a semi-circle arc. Refer to Create Semi-Circle Arc Section for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the arc section.\nYou are prompted to Radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the arc section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create an arc section with a fixed diameter.\nYou are prompted to Diameter or <Radius>\nInput a dimensional value in the field and press Enter to set the diameter of the arc section.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\n\n\nCreate Arc Section with Specified End Points and Radius\nCreate Arc Section with Three Specified Points\nCreate Semi-Circle Arc Section\nNon-Routed Item\nCentre point or\nEnter\nDiameter or <Radius>\nEnter\nStart angle or <#deg>\nEnter\nSweep angle or <#deg>\nEnter\nESC\nEnds + Radius\nEnds + Radius\nCreate Arc Section with Specified End Points and Radius\nThree Point\nThree Point\nCreate Arc Section with Three Specified Points\nSemi-Circle\nSemi-Circle\nCreate Semi-Circle Arc Section\nRadius\nRadius\nRadius or <Diameter>\nEnter\nMirror\nMirror\nBeta\nBeta\nBeta angle <#>\nEnter\nParallel\nParallel\nBack\nBack\nDiameter\nDiameter\nDiameter or <Radius>\nEnter\nPerpendicular\nPerpendicular\nNon-Routed Item"}
{"Headers": "Create Arc Section with Specified End Points and Radius", "Content": "Creates an arc section with specified end points and a radius.\nYou are prompted to Start point or\nInput values in the dimension fields and press Enter or click to identify the start point position.\nYou are then prompted to End point (R=#mm) or <Radius>\nClick to identify the end point position.\nYou are then prompted to Indicate side for arc or\nClick to identify the position of the arc section. An arc section is created and displays in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nCentre + Sweep\nPress the down arrow key and select Centre + Sweep to create an arc with a specified centre point and sweep angle. Refer to Create Arc Section with Specified Centre Point and Sweep Angle for further information.\nThree Point\nPress the down arrow key and select Three Point to create an arc with three specified points. Refer to Create Arc Section with Three Specified Points for further information.\nSemi-Circle\nPress the down arrow key and select Semi-Circle to create a semi-circle arc. Refer to Create Semi-Circle Arc Section for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the arc section.\nYou are prompted to Curve radius <#>\nInput a dimensional value in the field and press Enter to set the radii of the arc section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nCentre + Sweep\nPress the down arrow key and select Centre + Sweep to create an arc with a specified centre point and sweep angle. Refer to Create Arc Section with Specified Centre Point and Sweep Angle for further information.\nThree Point\nPress the down arrow key and select Three Point to create an arc with three specified points. Refer to Create Arc Section with Three Specified Points for further information.\nSemi-Circle\nPress the down arrow key and select Semi-Circle to create a semi-circle arc. Refer to Create Semi-Circle Arc Section for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the arc section.\nYou are prompted to Curve radius <#>\nInput a dimensional value in the field and press Enter to set the radii of the arc section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nThe new GENSEC displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nCentre + Sweep\nPress the down arrow key and select Centre + Sweep to create an arc with a specified centre point and sweep angle. Refer to Create Arc Section with Specified Centre Point and Sweep Angle for further information.\nThree Point\nPress the down arrow key and select Three Point to create an arc with three specified points. Refer to Create Arc Section with Three Specified Points for further information.\nSemi-Circle\nPress the down arrow key and select Semi-Circle to create a semi-circle arc. Refer to Create Semi-Circle Arc Section for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the arc section.\nYou are prompted to Curve radius <#>\nInput a dimensional value in the field and press Enter to set the radii of the arc section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\n\n\nCreate Arc Section with Specified Centre Point and Sweep Angle\nCreate Arc Section with Three Specified Points\nCreate Semi-Circle Arc Section\nNon-Routed Item\nStart point or\nEnter\nEnd point (R=#mm) or <Radius>\nIndicate side for arc or\nESC\nCentre + Sweep\nCentre + Sweep\nCreate Arc Section with Specified Centre Point and Sweep Angle\nThree Point\nThree Point\nCreate Arc Section with Three Specified Points\nSemi-Circle\nSemi-Circle\nCreate Semi-Circle Arc Section\nRadius\nRadius\nCurve radius <#>\nEnter\nMirror\nMirror\nBeta\nBeta\nBeta angle <#>\nEnter\nParallel\n\nBack\nBack\nPerpendicular\n\nNon-Routed Item"}
{"Headers": "Create Arc Section with Three Specified Points", "Content": "Creates an arc section with three specified points.\nYou are prompted to 1st circumference point or\nInput values in the dimension fields and press Enter or click to identify the first circumference point position.\nYou are then prompted to 2nd circumference point or\nInput values in the dimension fields and press Enter or click to identify the second circumference point position.\nYou are then prompted to 3rd circumference point or\nInput values in the dimension fields and press Enter or click to identify the third circumference point position. An arc section is created and displays in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nEnds + Radius\nPress the down arrow key and select Ends + Radius to create an arc with specified end points and a radius. Refer to Create Arc Section with Specified End Points and Radius for further information.\nCentre + Sweep\nPress the down arrow key and select Centre + Sweep to create an arc with a specified centre point and sweep angle. Refer to Create Arc Section with Specified Centre Point and Sweep Angle for further information.\nSemi-Circle\nPress the down arrow key and select Semi-Circle to create a semi-circle arc. Refer to Create Semi-Circle Arc Section for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nEnds + Radius\nPress the down arrow key and select Ends + Radius to create an arc with specified end points and a radius. Refer to Create Arc Section with Specified End Points and Radius for further information.\nCentre + Sweep\nPress the down arrow key and select Centre + Sweep to create an arc with a specified centre point and sweep angle. Refer to Create Arc Section with Specified Centre Point and Sweep Angle for further information.\nSemi-Circle\nPress the down arrow key and select Semi-Circle to create a semi-circle arc. Refer to Create Semi-Circle Arc Section for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nThe new GENSEC displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nEnds + Radius\nPress the down arrow key and select Ends + Radius to create an arc with specified end points and a radius. Refer to Create Arc Section with Specified End Points and Radius for further information.\nCentre + Sweep\nPress the down arrow key and select Centre + Sweep to create an arc with a specified centre point and sweep angle. Refer to Create Arc Section with Specified Centre Point and Sweep Angle for further information.\nSemi-Circle\nPress the down arrow key and select Semi-Circle to create a semi-circle arc. Refer to Create Semi-Circle Arc Section for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\n\n\nCreate Arc Section with Specified End Points and Radius\nCreate Arc Section with Specified Centre Point and Sweep Angle\nCreate Semi-Circle Arc Section\nNon-Routed Item\n1st circumference point or\nEnter\n2nd circumference point or\nEnter\n3rd circumference point or\nEnter\nESC\nEnds + Radius\nEnds + Radius\nCreate Arc Section with Specified End Points and Radius\nCentre + Sweep\nCentre + Sweep\nCreate Arc Section with Specified Centre Point and Sweep Angle\nSemi-Circle\nSemi-Circle\nCreate Semi-Circle Arc Section\nMirror\nMirror\nBeta\nBeta\nBeta angle <#>\nEnter\nParallel\nParallel\nBack\nBack\nPerpendicular\nPerpendicular\nNon-Routed Item"}
{"Headers": "Create Semi-Circle Arc Section", "Content": "Creates a semi-circle arc section.\nYou are prompted to Start point or\nInput values in the dimension fields and press Enter or click to identify the start point position.\nYou are then prompted to End point or\nInput a dimensional value in the field and press Enter or click to identify the end point position.\nYou are then prompted to Indicate side for arc or\nClick to identify the position of the arc section. An arc section is created and displays in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nEnds + Radius\nPress the down arrow key and select Ends + Radius to create an arc with specified end points and a radius. Refer to Create Arc Section with Specified End Points and Radius for further information.\nCentre + Sweep\nPress the down arrow key and select Centre + Sweep to create an arc with a specified centre point and sweep angle. Refer to Create Arc Section with Specified Centre Point and Sweep Angle for further information.\nThree Point\nPress the down arrow key and select Three Point to create an arc with three specified points. Refer to Create Arc Section with Three Specified Points for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nEnds + Radius\nPress the down arrow key and select Ends + Radius to create an arc with specified end points and a radius. Refer to Create Arc Section with Specified End Points and Radius for further information.\nCentre + Sweep\nPress the down arrow key and select Centre + Sweep to create an arc with a specified centre point and sweep angle. Refer to Create Arc Section with Specified Centre Point and Sweep Angle for further information.\nThree Point\nPress the down arrow key and select Three Point to create an arc with three specified points. Refer to Create Arc Section with Three Specified Points for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nThe new GENSEC displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nEnds + Radius\nPress the down arrow key and select Ends + Radius to create an arc with specified end points and a radius. Refer to Create Arc Section with Specified End Points and Radius for further information.\nCentre + Sweep\nPress the down arrow key and select Centre + Sweep to create an arc with a specified centre point and sweep angle. Refer to Create Arc Section with Specified Centre Point and Sweep Angle for further information.\nThree Point\nPress the down arrow key and select Three Point to create an arc with three specified points. Refer to Create Arc Section with Three Specified Points for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the arc section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\n\n\nCreate Arc Section with Specified End Points and Radius\nCreate Arc Section with Specified Centre Point and Sweep Angle\nCreate Arc Section with Three Specified Points\nNon-Routed Item\nStart point or\nEnter\nEnd point or\nEnter\nIndicate side for arc or\nESC\nEnds + Radius\nEnds + Radius\nCreate Arc Section with Specified End Points and Radius\nCentre + Sweep\nCentre + Sweep\nCreate Arc Section with Specified Centre Point and Sweep Angle\nThree Point\nThree Point\nCreate Arc Section with Three Specified Points\nMirror\nMirror\nBeta\nBeta\nBeta angle <#>\nEnter\nParallel\nParallel\nBack\nBack\nPerpendicular\nPerpendicular\nNon-Routed Item"}
{"Headers": "Create Ring Section with Specified Centre Point", "Content": "Creates a ring section with a specified centre point.\nYou are prompted to Centre point or\nInput values in the dimension fields and press Enter or click to identify the centre point position.\nYou are then prompted to Diameter or <Radius>\nInput a dimensional value in the field and press Enter or click to identify the diameter of the ring section.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nThree Point\nPress the down arrow key and select Three Point to create a ring with three specified points. Refer to Create Ring Section with Three Specified Points for further information.\nTwo Point\nPress the down arrow key and select Two Point to create a ring with two specified points. Refer to Create Ring Section with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the ring section.\nYou are prompted to Radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the ring section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the ring section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create a ring section with a fixed diameter.\nYou are prompted to Diameter or <Radius>\nInput a dimensional value in the field and press Enter to set the diameter of the ring section.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nThree Point\nPress the down arrow key and select Three Point to create a ring with three specified points. Refer to Create Ring Section with Three Specified Points for further information.\nTwo Point\nPress the down arrow key and select Two Point to create a ring with two specified points. Refer to Create Ring Section with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the ring section.\nYou are prompted to Radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the ring section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the ring section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create a ring section with a fixed diameter.\nYou are prompted to Diameter or <Radius>\nInput a dimensional value in the field and press Enter to set the diameter of the ring section.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nThe new GENSEC displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nThree Point\nPress the down arrow key and select Three Point to create a ring with three specified points. Refer to Create Ring Section with Three Specified Points for further information.\nTwo Point\nPress the down arrow key and select Two Point to create a ring with two specified points. Refer to Create Ring Section with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to modify the radii of the ring section.\nYou are prompted to Radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the ring section.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the ring section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create a ring section with a fixed diameter.\nYou are prompted to Diameter or <Radius>\nInput a dimensional value in the field and press Enter to set the diameter of the ring section.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\n\n\nCreate Ring Section with Three Specified Points\nCreate Ring Section with Two Specified Points\nNon-Routed Item\nCentre point or\nEnter\nDiameter or <Radius>\nEnter\nESC\nThree Point\nThree Point\nCreate Ring Section with Three Specified Points\nTwo Point\nTwo Point\nCreate Ring Section with Two Specified Points\nRadius\nRadius\nRadius or <Diameter>\nEnter\nMirror\nMirror\nBeta\nBeta\nBeta angle <#>\nEnter\nParallel\nParallel\nBack\nBack\nDiameter\nDiameter\nDiameter or <Radius>\nEnter\nPerpendicular\n\nNon-Routed Item"}
{"Headers": "Create Ring Section with Three Specified Points", "Content": "Creates a ring section with three specified points.\nYou are prompted to 1st Circumference point or\nInput values in the dimension fields and press Enter or click to identify the first circumference point position.\nYou are then prompted to 2nd Circumference point or\nInput values in the dimension fields and press Enter or click to identify the second circumference point position.\nYou are then prompted to 3rd Circumference point or\nInput values in the dimension fields and press Enter or click to identify the third circumference point position. A ring section is created and displays in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nCentre +\nPress the down arrow key and select Centre + to create a ring with a specified centre point. Refer to Create Ring Section with Specified Centre Point for further information.\nTwo Point\nPress the down arrow key and select Two Point to create a ring with two specified points. Refer to Create Ring Section with Two Specified Points for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the ring section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nCentre +\nPress the down arrow key and select Centre + to create a ring with a specified centre point. Refer to Create Ring Section with Specified Centre Point for further information.\nTwo Point\nPress the down arrow key and select Two Point to create a ring with two specified points. Refer to Create Ring Section with Two Specified Points for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the ring section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nThe new GENSEC displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nCentre +\nPress the down arrow key and select Centre + to create a ring with a specified centre point. Refer to Create Ring Section with Specified Centre Point for further information.\nTwo Point\nPress the down arrow key and select Two Point to create a ring with two specified points. Refer to Create Ring Section with Two Specified Points for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the ring section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\n\n\nCreate Ring Section with Specified Centre Point\nCreate Ring Section with Two Specified Points\nNon-Routed Item\n1st Circumference point or\nEnter\n2nd Circumference point or\nEnter\n3rd Circumference point or\nEnter\nESC\nCentre +\nCentre +\nCreate Ring Section with Specified Centre Point\nTwo Point\nTwo Point\nCreate Ring Section with Two Specified Points\nBack\nBack\nMirror\nMirror\nBeta\nBeta\nBeta angle <#>\nEnter\nParallel\nParallel\nPerpendicular\nPerpendicular\nNon-Routed Item"}
{"Headers": "Create Ring Section with Two Specified Points", "Content": "Creates a ring section with two specified points.\nYou are prompted to Start diameter point or\nInput values in the dimension fields and press Enter or click to identify the first diameter point position.\nYou are then prompted to End diameter point or\nInput a dimensional value in the field and press Enter or click to identify the diameter of the ring section. A ring section is created and displays in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nCentre +\nPress the down arrow key and select Centre + to create a ring with a specified centre point. Refer to Create Ring Section with Specified Centre Point for further information.\nThree Point\nPress the down arrow key and select Three Point to create a ring with three specified points. Refer to Create Ring Section with Three Specified Points for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the ring section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nCentre +\nPress the down arrow key and select Centre + to create a ring with a specified centre point. Refer to Create Ring Section with Specified Centre Point for further information.\nThree Point\nPress the down arrow key and select Three Point to create a ring with three specified points. Refer to Create Ring Section with Three Specified Points for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the ring section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\nThe new GENSEC displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nCentre +\nPress the down arrow key and select Centre + to create a ring with a specified centre point. Refer to Create Ring Section with Specified Centre Point for further information.\nThree Point\nPress the down arrow key and select Three Point to create a ring with three specified points. Refer to Create Ring Section with Three Specified Points for further information.\nMirror\nPress the down arrow key and select Mirror to reposition the section as a reflection of the original position.\nBeta\nPress the down arrow key and select Beta to rotate the section.\nYou are prompted to Beta angle <#>\nInput an angular value in the field and press Enter to set the angle of the ring section.\nParallel\nPress the down arrow key and select Parallel to orientate the web of the section parallel to the X, Y plane of the LCS.\nThe left side of the context editor indicates that parallel mode is selected.\nBack\nPress the down arrow key and select Back to undo the last action.\nPerpendicular\nPress the down arrow key and select Perpendicular to orientate the web of the section perpendicular to the X, Y plane of the LCS. The default creation mode is perpendicular.\n\n\n\nCreate Ring Section with Specified Centre Point\nCreate Ring Section with Three Specified Points\nNon-Routed Item\nStart diameter point or\nEnter\nEnd diameter point or\nEnter\nESC\nCentre +\n\nCreate Ring Section with Specified Centre Point\nThree Point\nThree Point\nCreate Ring Section with Three Specified Points\nMirror\nMirror\nBeta\nBeta\nBeta angle <#>\nEnter\nParallel\nParallel\nBack\nBack\nPerpendicular\nPerpendicular\nNon-Routed Item"}
{"Headers": "Section Connectivity", "Content": "When sections (GENSEC) are connected, the connection between the two sections is represented on the owning section as justification line datum (JLDATU), positioning line datum (PLDATU) and fixing (FIXING) elements in the Model Explorer.\nIn the structural hierarchy, JLDATU, PLDATU and FIXING elements are created each time an owning and attached section are connected. By default, the JLDATU, PLDATU and FIXING elements are deleted if a connected GENSEC is deleted.\n\nJustification Line Datum (JLDATU)\nJLDATU elements are owned by GENSEC elements. The JLDATU element contains the justification line datum for the connection. The justification line datum represents the connection distance measured from the start of the owning GENSEC. JLDATU elements are administrative and can own PLDATU elements.\nPositioning Line Datum (PLDATU)\nPLDATU elements are owned by JLDATU elements. By default, a PLDATU element is created for each connection. The PLDATU element contains the positioning line datum for the connection. The positioning line datum represents the Pline that the attached section is trimmed to. PLDATU elements are administrative and can own FIXING elements.\nFixing (FIXING)\nFIXING elements are owned by PLDATU elements and have the same position as a PLDATU. FIXING elements contain properties for:\nConnectivity to the structural 3D model\nTrimming attached members\nSpecification Reference (SPREF attribute) for the joint/fitting.\nConnectivity to the structural 3D model\nConnectivity to the structural 3D model\nTrimming attached members\nTrimming attached members\nSpecification Reference (SPREF attribute) for the joint/fitting.\nSpecification Reference (SPREF attribute) for the joint/fitting.\n\n\n\nJustification Line Datum (JLDATU)\nPositioning Line Datum (PLDATU)\nFixing (FIXING)"}
{"Headers": "Justification Line Datum Properties", "Content": "The Properties window allows you to view the status of the JLDATU. Refer to Properties for further information.\n\nThe general properties of JLDATU elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.\nPositional\nDistance from start\nInput a value in the field to modify the justification line datum position.\nProportional dist\nInput a value in the field to modify the justification line datum position proportionally. The distance is measured as a decimal value of the owning section size. For example, insert 0.5 to move the fixing half of the distance of the owning section.\nPositional\n\nDistance from start\nInput a value in the field to modify the justification line datum position.\nProportional dist\nInput a value in the field to modify the justification line datum position proportionally. The distance is measured as a decimal value of the owning section size. For example, insert 0.5 to move the fixing half of the distance of the owning section.\n\nPositional\nDistance from start\nInput a value in the field to modify the justification line datum position.\nProportional dist\nInput a value in the field to modify the justification line datum position proportionally. The distance is measured as a decimal value of the owning section size. For example, insert 0.5 to move the fixing half of the distance of the owning section.\n\n\n\nProperties\nModify Section Properties\nProperties\nProperties\nModify Section Properties\nPositional\nDistance from start\nProportional dist\n0.5"}
{"Headers": "Positioning Line Datum Properties", "Content": "The Properties window allows you to view the status of the PLDATU. Refer to Properties for further information.\n\nThe general properties of PLDATU elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.\nPositional\nPositioning line lock\nSelect from the drop-down list to define the lock status of the Pline connection.\nSelect True to lock the Pline connection, the connection manager does not attempt to trim the attached section to the most appropriate Pline of the owning section when modified.\nSelect False to unlock the Pline connection, the connection manager attempts to trim the attached section to the most appropriate Pline of the owning section when modified.\nBy default, the positioning line lock property is set to true if the section end trimming has been forced to a Pline. Refer to Trim Connected Section Ends for further information.\nPositioning line\nSelect from the drop-down list to modify the Pline to which the attached section is trimmed.\nPreferred Y axis direction\nDisplays the direction of the Y axis.\nPositional\n\nPositioning line lock\nSelect from the drop-down list to define the lock status of the Pline connection.\nSelect True to lock the Pline connection, the connection manager does not attempt to trim the attached section to the most appropriate Pline of the owning section when modified.\nSelect False to unlock the Pline connection, the connection manager attempts to trim the attached section to the most appropriate Pline of the owning section when modified.\nBy default, the positioning line lock property is set to true if the section end trimming has been forced to a Pline. Refer to Trim Connected Section Ends for further information.\nPositioning line\nSelect from the drop-down list to modify the Pline to which the attached section is trimmed.\nPreferred Y axis direction\nDisplays the direction of the Y axis.\n\nPositional\nPositioning line lock\nSelect from the drop-down list to define the lock status of the Pline connection.\nSelect True to lock the Pline connection, the connection manager does not attempt to trim the attached section to the most appropriate Pline of the owning section when modified.\nSelect False to unlock the Pline connection, the connection manager attempts to trim the attached section to the most appropriate Pline of the owning section when modified.\nBy default, the positioning line lock property is set to true if the section end trimming has been forced to a Pline. Refer to Trim Connected Section Ends for further information.\nPositioning line\nSelect from the drop-down list to modify the Pline to which the attached section is trimmed.\nPreferred Y axis direction\nDisplays the direction of the Y axis.\n\n\n\nProperties\nModify Section Properties\nTrim Connected Section Ends\nProperties\nProperties\nModify Section Properties\nPositional\nPositioning line lock\nTrue\nFalse\nTrim Connected Section Ends\nPositioning line\nPreferred Y axis direction"}
{"Headers": "Fixing Properties", "Content": "The Properties window allows you to view the status of the FIXING. Refer to Properties for further information.\n\nThe general properties of FIXING elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.\nSpecification\nReference\nDisplays the name of the specification reference (SPREF attribute) of the joint/fitting catalogue item associated with the connection.\nA value of Null Element indicates that a catalogue item is not associated with the connection, this is the default for a joint. Refer to Joints for further information.\nWhen a fitting is created, the field is populated with the specification reference of the selected fitting. Refer to Create Section Fitting for further information.\nParameters\nInput a dimensional value in the Clearance field to modify the clearance distance required for the fixing. The clearance displays in the 3D view.\nMaterial\nInput a value in the field or select a material from the drop-down list to modify the fixing material.\nThe material ref drop-down list is populated with the materials that are associated with the currently selected specification reference.\nPositional\nPosition\nInput dimensional values in the field to explicitly modify the position of the section. The section is repositioned.\nOrientation\nInput values in the field to modify the direction of the X, Y and Z axis.\nDistance from start\nInput a dimensional value in the field to modify the position of the fixing explicitly. The distance in measured from the start point of the owning section.\nProportional dist\nInput a value in the field to modify the fixing position proportionally. The distance is measured as a decimal value of the owning section size. For example, insert 0.5 to move the fixing half of the distance of the owning section.\nPositioning line\nSelect from the drop-down list to modify the Pline to which the attached section is trimmed.\nPreferred Y axis direction\nDisplays the direction of the Y axis.\nPositional\nCutback\nInput a dimensional value in the field to modify the cutting plane distance.\nCutting plane normal\nInput a directional value in the field to modify the cutting plane direction.\nJoining line\nInput a value in the field or select a justification from the drop-down list to modify the justification of the joining line.\nJoint dominance\nInput a value in the field to modify the joint dominance.\nInput True in the field to define the joint as dominant.\nInput False in the field to define the joint as subordinate.\nRefer to Dominant and Subordinate Connections for further information.\nSpecification\n\nReference\nDisplays the name of the specification reference (SPREF attribute) of the joint/fitting catalogue item associated with the connection.\nA value of Null Element indicates that a catalogue item is not associated with the connection, this is the default for a joint. Refer to Joints for further information.\nWhen a fitting is created, the field is populated with the specification reference of the selected fitting. Refer to Create Section Fitting for further information.\nParameters\nInput a dimensional value in the Clearance field to modify the clearance distance required for the fixing. The clearance displays in the 3D view.\nMaterial\nInput a value in the field or select a material from the drop-down list to modify the fixing material.\nThe material ref drop-down list is populated with the materials that are associated with the currently selected specification reference.\nPositional\n\nPosition\nInput dimensional values in the field to explicitly modify the position of the section. The section is repositioned.\nOrientation\nInput values in the field to modify the direction of the X, Y and Z axis.\nDistance from start\nInput a dimensional value in the field to modify the position of the fixing explicitly. The distance in measured from the start point of the owning section.\nProportional dist\nInput a value in the field to modify the fixing position proportionally. The distance is measured as a decimal value of the owning section size. For example, insert 0.5 to move the fixing half of the distance of the owning section.\nPositioning line\nSelect from the drop-down list to modify the Pline to which the attached section is trimmed.\nPreferred Y axis direction\nDisplays the direction of the Y axis.\nPositional\n\nCutback\nInput a dimensional value in the field to modify the cutting plane distance.\nCutting plane normal\nInput a directional value in the field to modify the cutting plane direction.\nJoining line\nInput a value in the field or select a justification from the drop-down list to modify the justification of the joining line.\nJoint dominance\nInput a value in the field to modify the joint dominance.\nInput True in the field to define the joint as dominant.\nInput False in the field to define the joint as subordinate.\nRefer to Dominant and Subordinate Connections for further information.\n\nSpecification\nReference\nDisplays the name of the specification reference (SPREF attribute) of the joint/fitting catalogue item associated with the connection.\nA value of Null Element indicates that a catalogue item is not associated with the connection, this is the default for a joint. Refer to Joints for further information.\nWhen a fitting is created, the field is populated with the specification reference of the selected fitting. Refer to Create Section Fitting for further information.\nParameters\nInput a dimensional value in the Clearance field to modify the clearance distance required for the fixing. The clearance displays in the 3D view.\nMaterial\nInput a value in the field or select a material from the drop-down list to modify the fixing material.\nThe material ref drop-down list is populated with the materials that are associated with the currently selected specification reference.\nPositional\nPosition\nInput dimensional values in the field to explicitly modify the position of the section. The section is repositioned.\nOrientation\nInput values in the field to modify the direction of the X, Y and Z axis.\nDistance from start\nInput a dimensional value in the field to modify the position of the fixing explicitly. The distance in measured from the start point of the owning section.\nProportional dist\nInput a value in the field to modify the fixing position proportionally. The distance is measured as a decimal value of the owning section size. For example, insert 0.5 to move the fixing half of the distance of the owning section.\nPositioning line\nSelect from the drop-down list to modify the Pline to which the attached section is trimmed.\nPreferred Y axis direction\nDisplays the direction of the Y axis.\nPositional\nCutback\nInput a dimensional value in the field to modify the cutting plane distance.\nCutting plane normal\nInput a directional value in the field to modify the cutting plane direction.\nJoining line\nInput a value in the field or select a justification from the drop-down list to modify the justification of the joining line.\nJoint dominance\nInput a value in the field to modify the joint dominance.\nInput True in the field to define the joint as dominant.\nInput False in the field to define the joint as subordinate.\nRefer to Dominant and Subordinate Connections for further information.\n\n\n\nProperties\nModify Section Properties\nJoints\nCreate Section Fitting\nDominant and Subordinate Connections\nProperties\nProperties\nModify Section Properties\nSpecification\nReference\nJoints\nCreate Section Fitting\nParameters\nClearance\nMaterial\nPositional\nPosition\nOrientation\nDistance from start\nProportional dist\n0.5\nPositioning line\nPreferred Y axis direction\nPositional\nCutback\nCutting plane normal\nJoining line\nJoint dominance\nTrue\nFalse\nDominant and Subordinate Connections"}
{"Headers": "Attached Sections", "Content": "The Properties window allows you to view the connection status of the attached section. Refer to Properties for further information.\n\nDesign\nStart joint\nDisplays the name of the fixing which is attached to the owning section. Displays the name of the owning section to which the start of the attached section is connected.\nEnd joint\nDisplays the name of the fixing which is attached to the owning section. Displays the name of the owning section to which the end of the attached section is connected.\nStart cut\nDisplays the direction of the cut at the start of the attached section.\nEnd cut\nDisplays the direction of the cut at the end of the attached section.\nDesign\n\nStart joint\nDisplays the name of the fixing which is attached to the owning section. Displays the name of the owning section to which the start of the attached section is connected.\nEnd joint\nDisplays the name of the fixing which is attached to the owning section. Displays the name of the owning section to which the end of the attached section is connected.\nStart cut\nDisplays the direction of the cut at the start of the attached section.\nEnd cut\nDisplays the direction of the cut at the end of the attached section.\n\nDesign\nStart joint\nDisplays the name of the fixing which is attached to the owning section. Displays the name of the owning section to which the start of the attached section is connected.\nEnd joint\nDisplays the name of the fixing which is attached to the owning section. Displays the name of the owning section to which the end of the attached section is connected.\nStart cut\nDisplays the direction of the cut at the start of the attached section.\nEnd cut\nDisplays the direction of the cut at the end of the attached section.\n\n\n\nProperties\nProperties\nProperties\nDesign\nStart joint\nEnd joint\nStart cut\nEnd cut"}
{"Headers": "Dominant and Subordinate Connections", "Content": "When a connected section is repositioned, the effect on the owning and attached sections depends upon whether or not the joint dominance property of the FIXING element is defined as dominant or subordinate.\nIf joint dominance is set to False, the joint is subordinate (also described by saying that the section is dominant). If joint dominance is set to True, the joint is dominant. The default joint dominance property for a connection can be defined, refer to Structural Defaults for further information.\nConsider these effects, where the owning section is moved:\n\n\n\n\nStructural Defaults\nStructural Defaults"}
{"Headers": "Dynamic Connectivity Rules", "Content": "The connectivity between structural section elements is maintained automatically by the connection manager. Connectivity tolerances are used by the clash check facility to determine if an attached section should be disconnected. Refer to Structural Defaults for further information. Modifications to GENSEC element properties can affect connectivity or geometry between the owning and attached sections.\nIf any of these properties are modified, the connection manager uses a set of dynamic connectivity rules to determine the effect on existing connections between owning and attached sections that have been modified.\nThe most important property to consider when modifications are made is the joint dominance property of a FIXING. Refer to Dominant and Subordinate Connections for further information.\nMove Owning Section\nIf the joint dominance property is False and exceeds the structural connectivity tolerances, the attached section is disconnected and the JLDATU, PLDATU and FIXING elements are deleted. If the attached section does not exceed the structural connectivity tolerances, the connection is maintained and Z distance from the start position is updated.\nIf the joint dominance property is True, the connection between the owning and attached sections is maintained.\nStretch Owning Section\nIf the start of the owning section is stretched and the joint dominance property is False, the JLDATU position (Z distance from the start position) is modified and the attached section does not change direction.\nIf the start of the owning section is stretched and the joint dominance property is True, the JLDATU position (Z distance from the start position) is maintained and the attached section changes orientation when reconnected.\nIf the end of the owning section is stretched, the JLDATU position is not modified and has no effect on the attached section regardless of the joint dominance property (which controls the Z distance from the start position).\nRe-orientate Owning Section\nIf the joint dominance property is False and exceeds the structural connectivity tolerances, the attached section is disconnected and the JLDATU, PLDATU and FIXING elements are deleted. If the attached section does not exceed the structural connectivity tolerances, the connection is maintained and the start distance of the joint is maintained.\nIf the joint dominance property is True, the connection between the owning and attached sections is maintained.\nMove Attached Section\nIf the JLDATU contains one PLDATU and one FIXING, the JLDATU position is moved to the attached section position.\nIf the JLDATU contains more than one PLDATU, a new JLDATU, PLDATU and FIXING is created at the attached section position. The old FIXING is deleted.\nIf the PLDATU owns more than one FIXING, a new JLDATU, PLDATU and FIXING is created at the attached section position. The old FIXING is deleted.\nIf a JLDATU or PLDATU no longer contain any members, they are deleted.\nCopy Attached Section\nIf the copied attached section is positioned on the same owning section and has the same orientation as the original, a new JLDATU, PLDATU and FIXING is created at the attached section position.\nModify Specification Reference of Owning Section\nIf a new specification reference property is applied, the connection of the attached section is maintained and trimmed to the most appropriate Pline.\nModify Specification Reference of Owning Section\nIf a new specification reference property is applied, the connection of the attached section is maintained and trimmed to the most appropriate Pline.\nModify Beta Angle of Owning Section\nIf the beta angle of the owning section is modified, the connection of the attached section is maintained and trimmed to the most appropriate Pline.\nModify Justification Line of Owning Section\nIf the justification line of the owning section is modified, the attached section is trimmed to the PLDATU positioning line property, the direction of the attached section may be modified, dependent on the joint dominance property.\nMirror Owning Section\nIf the mirror property of the owning section is modified, the connection of the attached section is maintained and trimmed to the most appropriate Pline.\nForce Position Line\nIf the Pline of a PLDATU is modified, the attached member is trimmed to the selected Pline. Subsequent modifications may result in modification to a different Pline.\nAlternatively, you can manually trim the connected section ends to a new Pline to update the PLDATU positioning line property. Refer to Trim Connected Section Ends for further information.\nDATAL\nDynamic connectivity is active by default, but is inactive when running in a datal. In some circumstances the RECONNECT command.\ncan be used to inactivate dynamic connectivity. The IGNORE option is a temporary switch which can be added at the end of a macro to ignore any modifications made within the macro. After running the macro, dynamic connectivity resumes.\nPosition\nStart position\nEnd position\nBeta angle\nSpecification reference\nParameters\nJustification\nMirror\nMember line\nPosition\nPosition\nStart position\nStart position\nEnd position\nEnd position\nBeta angle\nBeta angle\nSpecification reference\nSpecification reference\nParameters\nParameters\nJustification\nJustification\nMirror\nMirror\nMember line\nMember line\n\n\n\nStructural Defaults\nDominant and Subordinate Connections\nTrim Connected Section Ends\nStructural Defaults\nDominant and Subordinate Connections\nMove Owning Section\nFalse\nTrue\nStretch Owning Section\nFalse\nTrue\nRe-orientate Owning Section\nFalse\nTrue\nMove Attached Section\nCopy Attached Section\nModify Specification Reference of Owning Section\nModify Specification Reference of Owning Section\nModify Beta Angle of Owning Section\nModify Justification Line of Owning Section\nMirror Owning Section\nForce Position Line\nTrim Connected Section Ends\nDATAL"}
{"Headers": "Automatic Section Connection", "Content": "Sets the default connection status when a new section is created.\nIf the selection is highlighted, automatic section end connection is on.\nIf the selection is not highlighted, automatic section end connection is off.\n\n\n"}
{"Headers": "Connect Sections", "Content": "Connects the ends of two or more straight or curved sections.\nYou are prompted to Pick section\nClick to identify the owning section to connect.\nYou are then prompted to Pick section end(s) or <Finish>\nClick to identify the attached section to connect at the end nearest to the connection point.\nThe prompt is repeated, allowing you to create multiple connections.\nInput F at the prompt and press Enter to end the command. The sections are connected and the connection status displays in the 3D view.\n\nThroughout the section connection process you can press ESC to cancel the command. Additional functionality is also available.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nFinish\nPress the down arrow key and select Finish to end the command.\nThe new JLDATU, PLDATU and FIXING elements are added to the owning section and display in the Model Explorer.\n\nIf a connection cannot be made, a Warning message displays on the status bar.\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nPick section\nPick section end(s) or <Finish>\nF\nEnter\nESC\nFinish\nFinish"}
{"Headers": "Disconnect Sections", "Content": "Disconnects two or more section ends.\nYou are prompted to Pick connected end(s) or <Finish>\nClick to identify the section to disconnect, at the end nearest to the connection point.\nThe prompt is repeated, allowing you to disconnect multiple connections.\nInput F at the prompt and press Enter to end the command. The sections are disconnected and the connection status displays in the 3D view.\nThroughout the section disconnection process you can press ESC to cancel the command. Additional functionality is also available.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe JLDATU, PLDATU and FIXING elements are removed from the owning section.\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nPick connected end(s) or <Finish>\nF\nEnter\nESC\nFinish"}
{"Headers": "Trim Connected Section Ends", "Content": "Forces the section end trimming to an alternative Pline.\nWhen a connection is modified, the connection manager uses a set of dynamic connectivity rules to trim the attached section to the most appropriate Pline of the owning section. When a section end is trimmed to an alternative Pline the Positioning line lock property of the PLDATU is set to True which stops the connection manager from trimming to a different Pline if further modifications are made.\nYou are prompted to Pick connected end(s) or Finish\nClick to identify the attached section at the end nearest to the connection point.\nYou are then prompted to Select P-line\nClick to identify the Pline which corresponds to the required section end point (for example, NAR/NAL for a web connection or TOS/BOS for a flange connection, refer to Structural Catalog for further information).\nThe prompt is repeated, allowing you to trim multiple connections. Press ESC to end the command.\nThroughout the section trimming process you can press ESC to cancel the command. Additional functionality is also available.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nFinish\nPress the down arrow key and select Finish to end the command.\n\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nStructural Catalog\nPositioning line lock\nTrue\nPick connected end(s) or Finish\nSelect P-line\nStructural Catalog\nESC\nESC\nFinish\nFinish"}
{"Headers": "End Datum at Section End", "Content": "Creates an un-connected joint at a specified section end. Functionality is also available to:\nEnd Datum (ENDATU) elements have two main functions:\nYou are prompted to Select section end(s) or <Finish>\nClick to identify the section end(s) to associate with the joint and press Enter to display the End Datum window.\n\nThe End Datum window allows you to associate a catalogue specification with the currently selected joints and modify the dimensions of the joint component parts.\nSpecification\nSelect from the drop down list to display all the available groups of joint component covered by a specification. Once a specification has been selected from the drop-down list, the Joint Group and Joint galleries are automatically populated with joint group and joint components available for selection.\nJoint Group\nSelect from the gallery to display all the available joint components. Once a group has been selected, the Joint gallery is automatically populated with the joint components available for selection.\nJoint\nSelect a joint component from the gallery. Once a joint has been selected, the Design Parameters fields are automatically populated with default values.\nDesign Parameters\nInput values in the fields to modify the dimensions of the joint component parts.\nDetail\nClick to display a detailed image of the joint. The image window displays a detailed description of the joint geometry and the different parameters and variables that can be applied to the joint.\nInclude Weld Geometry\nSelect the check box to include the weld geometry for an end datum joint.\nNote:\nThe functionality is only available for welded joints created from catalogue joints. The functionality is not available for welded joints created from template joints because the welds must be included in the template.\nThe example displays a welded joint created from a catalogue joint. The weld geometry displays in the 3D view.\nThe connection status of welded joints can be inspected and modified using the Connection Review window. Refer to Review Connections for further information.\nSpecification\nSelect from the drop down list to display all the available groups of joint component covered by a specification. Once a specification has been selected from the drop-down list, the Joint Group and Joint galleries are automatically populated with joint group and joint components available for selection.\nJoint Group\nSelect from the gallery to display all the available joint components. Once a group has been selected, the Joint gallery is automatically populated with the joint components available for selection.\nJoint\nSelect a joint component from the gallery. Once a joint has been selected, the Design Parameters fields are automatically populated with default values.\nDesign Parameters\nInput values in the fields to modify the dimensions of the joint component parts.\nDetail\nClick to display a detailed image of the joint. The image window displays a detailed description of the joint geometry and the different parameters and variables that can be applied to the joint.\n\nInclude Weld Geometry\nSelect the check box to include the weld geometry for an end datum joint.\nThe example displays a welded joint created from a catalogue joint. The weld geometry displays in the 3D view.\n\nThe connection status of welded joints can be inspected and modified using the Connection Review window. Refer to Review Connections for further information.\nClick Apply to accept the fitting component settings.\nThroughout the joint creation process you can press ESC to cancel the command. Additional functionality is also available.\nConnect to Panel\nPress the down arrow key and select Connect to Panel to connect section end(s) to a panel or floor element.\nYou are prompted to Select Panel/Floor to Connect to or\nClick to identify the panel or floor element to associate with the joint and press Enter to display the End Datum window.\nThe section ends are extended to meet the panel surface.\nConnecting to a panel in this way sets the CONREF attribute of each end datum, creating a reference between the end datum and the panel.\nFinish\nPress the down arrow key and select Finish to end the command.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nConnect to Panel\nPress the down arrow key and select Connect to Panel to connect section end(s) to a panel or floor element.\nYou are prompted to Select Panel/Floor to Connect to or\nClick to identify the panel or floor element to associate with the joint and press Enter to display the End Datum window.\nThe section ends are extended to meet the panel surface.\nConnecting to a panel in this way sets the CONREF attribute of each end datum, creating a reference between the end datum and the panel.\nFinish\nPress the down arrow key and select Finish to end the command.\nBack\nPress the down arrow key and select Back to undo the last action.\nA joint is created and displays in the 3D view.\n\nThe new ENDATU and FIXING elements display in the Model Explorer.\n\nSpecification\nSelect from the drop down list to display all the available groups of joint component covered by a specification. Once a specification has been selected from the drop-down list, the Joint Group and Joint galleries are automatically populated with joint group and joint components available for selection.\nJoint Group\nSelect from the gallery to display all the available joint components. Once a group has been selected, the Joint gallery is automatically populated with the joint components available for selection.\nJoint\nSelect a joint component from the gallery. Once a joint has been selected, the Design Parameters fields are automatically populated with default values.\nDesign Parameters\nInput values in the fields to modify the dimensions of the joint component parts.\nDetail\nClick to display a detailed image of the joint. The image window displays a detailed description of the joint geometry and the different parameters and variables that can be applied to the joint.\nInclude Weld Geometry\nSelect the check box to include the weld geometry for an end datum joint.\nNote:\nThe functionality is only available for welded joints created from catalogue joints. The functionality is not available for welded joints created from template joints because the welds must be included in the template.\nThe example displays a welded joint created from a catalogue joint. The weld geometry displays in the 3D view.\nThe connection status of welded joints can be inspected and modified using the Connection Review window. Refer to Review Connections for further information.\nConnect to Panel\nPress the down arrow key and select Connect to Panel to connect section end(s) to a panel or floor element.\nYou are prompted to Select Panel/Floor to Connect to or\nClick to identify the panel or floor element to associate with the joint and press Enter to display the End Datum window.\nThe section ends are extended to meet the panel surface.\nConnecting to a panel in this way sets the CONREF attribute of each end datum, creating a reference between the end datum and the panel.\nFinish\nPress the down arrow key and select Finish to end the command.\nBack\nPress the down arrow key and select Back to undo the last action.\nConnect section ends to a panel or floor element.\nAutomatically create baseplates at section ends.\nConnect section ends to a panel or floor element.\nConnect section ends to a panel or floor element.\nAutomatically create baseplates at section ends.\nAutomatically create baseplates at section ends.\nas analytical points when using application data for structural analysis;\nto own a Joint (FIXING) for referencing a catalogue joint element on an un-connected section end.\nas analytical points when using application data for structural analysis;\nas analytical points when using application data for structural analysis;\nto own a Joint (FIXING) for referencing a catalogue joint element on an un-connected section end.\nto own a Joint (FIXING) for referencing a catalogue joint element on an un-connected section end.\nNote:\nThe functionality is only available for welded joints created from catalogue joints. The functionality is not available for welded joints created from template joints because the welds must be included in the template.\n\n\n\nReview Connections\nSelect section end(s) or <Finish>\nEnter\nEnd Datum\nEnd Datum\nSpecification\nJoint Group\nJoint\nJoint Group\nJoint\nJoint\nDesign Parameters\nDesign Parameters\nDetail\nInclude Weld Geometry\nNote:\nConnection Review\nReview Connections\nApply\nESC\nConnect to Panel\nConnect to Panel\nSelect Panel/Floor to Connect to or\nEnter\nEnd Datum\nFinish\nFinish\nBack\nBack"}
{"Headers": "End Datum Properties", "Content": "The Properties window allows you to view the status of the ENDATU element. Refer to Properties for further information.\n\nThe general properties of ENDATU elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.\nPositional\nDistance from start\nInput a value in the field to modify the end datum position, measured from the start point of the structural section that the joint is attached to.\nPreferred Y axis direction\nDisplays the direction of the Y axis.\nPositioning line\nSelect from the drop-down list to modify the Pline to which the joint is attached.\nDesign\nOwner reference\nAllows you to view the identification code of the structural support section that the joint is attached to.\nPositional\n\nDistance from start\nInput a value in the field to modify the end datum position, measured from the start point of the structural section that the joint is attached to.\nPreferred Y axis direction\nDisplays the direction of the Y axis.\nPositioning line\nSelect from the drop-down list to modify the Pline to which the joint is attached.\nDesign\n\nOwner reference\nAllows you to view the identification code of the structural support section that the joint is attached to.\n\nPositional\nDistance from start\nInput a value in the field to modify the end datum position, measured from the start point of the structural section that the joint is attached to.\nPreferred Y axis direction\nDisplays the direction of the Y axis.\nPositioning line\nSelect from the drop-down list to modify the Pline to which the joint is attached.\nDesign\nOwner reference\nAllows you to view the identification code of the structural support section that the joint is attached to.\n\n\n\nProperties\nModify Section Properties\nProperties\nProperties\nModify Section Properties\nPositional\nDistance from start\nPreferred Y axis direction\nPositioning line\nDesign\nOwner reference"}
{"Headers": "View Section End Connections", "Content": "Displays the section end connection status for all structural sections in the 3D view.\nIf the selection is highlighted, check end connections is on.\nIf the selection is not highlighted, check end connections is off.\nThe end connection status is highlighted in the 3D view using default colours. The default colours for each connection type can be modified. Refer to Structural Defaults for further information. The end connection status is indicated for all sections in the 3D view.\nBoth ends connected\nThe sections that are connected at both ends are highlighted in the 3D view.\nThe default colour is green.\nNeither end connected\nThe sections that are not connected at either end are highlighted in the 3D view.\nThe default colour is red.\nOne end connected\nThe sections that are connected at one end are highlighted in the 3D view. The end that is not connected is indicated.\nThe default colour is blue.\nBoth ends connected\nThe sections that are connected at both ends are highlighted in the 3D view.\nThe default colour is green.\nNeither end connected\nThe sections that are not connected at either end are highlighted in the 3D view.\nThe default colour is red.\nOne end connected\nThe sections that are connected at one end are highlighted in the 3D view. The end that is not connected is indicated.\nThe default colour is blue.\n\nBoth ends connected\nThe sections that are connected at both ends are highlighted in the 3D view.\nThe default colour is green.\nNeither end connected\nThe sections that are not connected at either end are highlighted in the 3D view.\nThe default colour is red.\nOne end connected\nThe sections that are connected at one end are highlighted in the 3D view. The end that is not connected is indicated.\nThe default colour is blue.\n\n\n\nStructural Defaults\nStructural Defaults\nBoth ends connected\nNeither end connected\nOne end connected"}
{"Headers": "Review Connections", "Content": "Displays the connection status of structural elements. Built-in checks are used to verify the integrity of selected elements, and a property grid can be used to make corrections where required. Elements requiring attention are grouped in a Flexible Explorer and highlighted in the 3D view.\nYou are prompted to Select Connected Items\nClick to identify the section and panel elements for review and press Enter to display the Connection Review window.\n\nThe top part of the Connection Review window is a Flexible Explorer, where elements from the initial selection are categorised, and can be used for navigation. The bottom part of the Connection Review window is a property grid, where results of various checks are displayed, and corrections can be made.\nThe selection in the explorer affects the display of the property grid. If multiple elements are selected, common attributes and validity check results display in the property grid. Any attributes which do not share a common value in the selection are empty in the property grid display.\nIf elements from different database types are selected, the property grid displays as empty.\nThe Model tab displays the selected elements grouped by category. For example, GENSEC elements are grouped by catalogue reference.\nThe Validation tab displays the selected elements grouped by validation status. Various checks are carried out on structural elements to ensure their validity. Any elements which return validation warnings or failures are highlighted. Refer to Validation Checks for further information.\nAny elements that are not checked for validation are grouped by No Validation Available.\nThe Validation tab displays the validation status together with the number of elements that return warnings or failures.\nPass\nWarning\nFail\nPass\n\nWarning\n\nFail\n\n\nThe Rules tab displays the selected elements grouped by rule review status. Defined rules can be created for catalogue and template elements. Refer to Rule Sets for further information. Any elements which return rule review warnings or failures are highlighted.\nAny elements that are not associated with rules are grouped by No Rules Available.\nThe Rules tab displays the rule review status together with the number of elements that return warnings or failures.\n\nFunctionality is available to manipulate the selection or modify the display in the 3D view.\nRefresh\nRefreshes the window with the current selection and performs validation checks.\nNew Selection\nReplaces the Flexible Explorer with the current selection of sections and panels in the 3D view.\nSelect CE\nReplaces the Flexible Explorer with the currently selected element from the Model Explorer and all member elements. The functionality can be used to populate the Flexible Explorer with administrative elements, for example, STRU or ZONE elements. The results if a collection can be used to populate the connection review list.\nToggle Track Current Element\nTurns the tracking of the currently selected element in the 3D view or Model Explorer on and off.\nIf multiple elements are selected in the 3D view, tracking does not apply.\nNavigate to Selected\nZooms to the currently selected Flexible Explorer element in the 3D view.\nToggle Transparency\nTurns the transparency of elements in the 3D view on and off. Elements selected in the Flexible Explorer remain solid.\nToggle Positive Highlighting\nTurns the highlight of elements which pass the validation checks on or off in the 3D view. Elements which passed the validation checks are highlighted green.\nThe functionality is only available from the Validation or Rules tabs.\n\nRefresh\nRefreshes the window with the current selection and performs validation checks.\n\nNew Selection\nReplaces the Flexible Explorer with the current selection of sections and panels in the 3D view.\n\nSelect CE\nReplaces the Flexible Explorer with the currently selected element from the Model Explorer and all member elements. The functionality can be used to populate the Flexible Explorer with administrative elements, for example, STRU or ZONE elements. The results if a collection can be used to populate the connection review list.\n\nToggle Track Current Element\nTurns the tracking of the currently selected element in the 3D view or Model Explorer on and off.\nIf multiple elements are selected in the 3D view, tracking does not apply.\n\nNavigate to Selected\nZooms to the currently selected Flexible Explorer element in the 3D view.\n\nToggle Transparency\nTurns the transparency of elements in the 3D view on and off. Elements selected in the Flexible Explorer remain solid.\n\nToggle Positive Highlighting\nTurns the highlight of elements which pass the validation checks on or off in the 3D view. Elements which passed the validation checks are highlighted green.\nThe functionality is only available from the Validation or Rules tabs.\nRight-click on any element in the Flexible Explorer to display a drop-down menu.\n\nSelect All Members of Same Type\nSelects all members of the current element. This functionality can be used to select an entire group. Any element which contains elements with other types are not selected. For example, a fixing with a template member.\nNavigate to\nNavigates to the owning element of the currently selected element. For example, Navigate to Panel displays if a weld is currently selected that is owned by a panel.\nSelect All Members of Same Type\nSelects all members of the current element. This functionality can be used to select an entire group. Any element which contains elements with other types are not selected. For example, a fixing with a template member.\nNavigate to\nNavigates to the owning element of the currently selected element. For example, Navigate to Panel displays if a weld is currently selected that is owned by a panel.\nRight-click on a joint element in the Flexible Explorer to display a drop-down menu.\n\nOpen Auto-Joint State Form\nDisplays the Joint List window for all selected joints. Functionality is available for automatic joints, including the ability to re-select from the specification. Refer to Automatic Joint and Baseplate Selection State for further information.\nOpen Auto-Joint State Form\nDisplays the Joint List window for all selected joints. Functionality is available for automatic joints, including the ability to re-select from the specification. Refer to Automatic Joint and Baseplate Selection State for further information.\nRight-click on a bounded plate element in the Flexible Explorer to display a drop-down menu.\n\nOpen Bounded Plate Health Check\nDisplays the Bounded Plate Health Checker window for all selected elements. Functionality is available to check the status and modify bounded plates. Refer to Bounded Plate Health Checker for further information.\nOpen Bounded Plate Health Check\nDisplays the Bounded Plate Health Checker window for all selected elements. Functionality is available to check the status and modify bounded plates. Refer to Bounded Plate Health Checker for further information.\nRight click on a handrail component element in the Flexible Explorer to display a drop-down menu.\n\nOpen Handrail Components Form\nDisplays the Handrail Components window for the handrail which owns the selected component. Functionality is available to modify components and set connection references. Refer to Components for more information.\nOpen Handrail Components Form\nDisplays the Handrail Components window for the handrail which owns the selected component. Functionality is available to modify components and set connection references. Refer to Components for more information.\n\nPass\nWarning\nFail\nRefresh\nRefreshes the window with the current selection and performs validation checks.\nNew Selection\nReplaces the Flexible Explorer with the current selection of sections and panels in the 3D view.\nSelect CE\nReplaces the Flexible Explorer with the currently selected element from the Model Explorer and all member elements. The functionality can be used to populate the Flexible Explorer with administrative elements, for example, STRU or ZONE elements. The results if a collection can be used to populate the connection review list.\nToggle Track Current Element\nTurns the tracking of the currently selected element in the 3D view or Model Explorer on and off.\nIf multiple elements are selected in the 3D view, tracking does not apply.\nNavigate to Selected\nZooms to the currently selected Flexible Explorer element in the 3D view.\nToggle Transparency\nTurns the transparency of elements in the 3D view on and off. Elements selected in the Flexible Explorer remain solid.\nToggle Positive Highlighting\nTurns the highlight of elements which pass the validation checks on or off in the 3D view. Elements which passed the validation checks are highlighted green.\nThe functionality is only available from the Validation or Rules tabs.\nSelect All Members of Same Type\nSelects all members of the current element. This functionality can be used to select an entire group. Any element which contains elements with other types are not selected. For example, a fixing with a template member.\nNavigate to\nNavigates to the owning element of the currently selected element. For example, Navigate to Panel displays if a weld is currently selected that is owned by a panel.\nOpen Auto-Joint State Form\nDisplays the Joint List window for all selected joints. Functionality is available for automatic joints, including the ability to re-select from the specification. Refer to Automatic Joint and Baseplate Selection State for further information.\nOpen Bounded Plate Health Check\nDisplays the Bounded Plate Health Checker window for all selected elements. Functionality is available to check the status and modify bounded plates. Refer to Bounded Plate Health Checker for further information.\nOpen Handrail Components Form\nDisplays the Handrail Components window for the handrail which owns the selected component. Functionality is available to modify components and set connection references. Refer to Components for more information.\nNote:\nThe prompt does not display if the section or panel elements are already selected.\nNote:\nThe Connection Review window performs validation checks on the selected elements when opened, it may take significant time to perform the validation checks.\nNote:\nThe size of each section can be modified by clicking and dragging the space underneath the explorer.\nNote:\nAny elements which return validation warnings or failures are highlighted red or yellow in the 3D view when using the Validation or Rules tabs.\n\n\n\nValidation Checks\nRule Sets\nAutomatic Joint and Baseplate Selection State\nBounded Plate Health Checker\nComponents\nSelect Connected Items\nNote:\nEnter\nConnection Review\nNote:\nConnection Review\nConnection Review\nConnection Review\nNote:\nModel\nValidation\nValidation Checks\nNo Validation Available\nValidation\nPass\nWarning\nFail\nRules\nRule Sets\nNo Rules Available\nRules\nRefresh\nNew Selection\nSelect CE\nToggle Track Current Element\nNavigate to Selected\nToggle Transparency\nToggle Positive Highlighting\nValidation\nRules\nNote:\nValidation\nRules\nSelect All Members of Same Type\nNavigate to\nNavigate to Panel\nOpen Auto-Joint State Form\nJoint List\nAutomatic Joint and Baseplate Selection State\nOpen Bounded Plate Health Check\nBounded Plate Health Checker\nBounded Plate Health Checker\nOpen Handrail Components Form\nHandrail Components window\nComponents"}
{"Headers": "Validation Checks", "Content": "The Properties tab displays the status of validation checks for the currently selected elements in the Flexible Explorer.\n\nAll validation checks are calculated when the Connection Review window is opened, and the results are not stored in the database. If modifications are made, use Refresh to run the validation checks again.\nThe Properties tab displays the status of each validation check.\nPass\nWarning\nFail\nPass\n\nWarning\n\nFail\n\nSome validation checks only occur if conditions are met. For example, the weld check for panels only occurs if welds are included in the panel. The checks for all elements are:\nGENSECs\nEnd Connections\nChecks the validity of the start and end connections. Both ends of the section should be connected, either via a fixing or an endatum.\nBoth ends connected.\nOne end disconnected.\nBoth ends disconnected.\nPanels\nWeld Check\nChecks the welds in the panel are aligned with the automatic weld placement algorithm (if welds are included).\nWeld placement is aligned with the algorithm.\nWelds are not placed in alignment with the algorithm.\nBounded Plates\nHealth Check\nChecks that bounded plates are valid according to the bounded plate health checker.\nBounded plates are valid.\nBounded plates do not align with the current boundary conditions.\nBounded plates have missing elements or invalid references in the structural connection set.\nWeld Check\nThe functionality is identical to the panels weld check.\nCatalog Joints\nConnection Check\nChecks that the CREF attribute of the fixing is set to a valid GENSEC or SCTN.\nConnection reference is valid.\nConnection reference is invalid, unset or not set to a GENSEC or SCTN element.\nCatalog Weld Check\nChecks that any welds in the STWSET for this fixing align with the JWELD definition in the catalog (If welds are included).\nWelds align with catalog definition.\nWelds have different positions compared to the catalog definition.\nInvalid references, or a different number of welds found compared to the catalog definition.\nTemplate Joints\nConnection Check\nThe functionality is identical to the catalog joints connection check.\nTemplate Rule Check\nChecks the template parameters and primitive elements are correct when compared with the template definition.\nAll template rules are valid and aligned with expected values.\nSome attributes of template elements differ from expected rule values. Specific attributes are indicated in the property grid description box.\nPanel Fittings\nTemplate Rule Check\nThe functionality is identical to the template joints template rule check (if fitting is a template).\nCatalog Weld Check\nThe functionality is identical to the catalog joints catalog weld check (if fitting is not a template and welds are included).\nGENSEC Fittings\nCurrently no checks available.\nWelds\nDetail Check\nChecks the Structural Weld Detail Reference (STWDTR) attribute is set to a valid weld detail.\nSTWDTR attribute is valid.\nSTWDTR attribute is unset.\nSTWDTR attribute is invalid.\nConnection Check\nChecks welds have two valid references in the Structural Weld Reference Array (STWRFA).\nAt least two valid elements in the STWRFA attribute.\nLess than two references in the array, or duplicate references found.\nInvalid connection references in the array.\nHandrail Components\nHandrail Connection Check\nChecks if a handrail component (Post, Termination, Panel or Gate) has a valid connection reference (CONREF).\nConnection reference is valid.\nConnection reference is unset or invalid.\nGENSECs\n\n\nEnd Connections\nChecks the validity of the start and end connections. Both ends of the section should be connected, either via a fixing or an endatum.\n\n\nBoth ends connected.\n\n\nOne end disconnected.\n\n\nBoth ends disconnected.\nPanels\n\n\nWeld Check\nChecks the welds in the panel are aligned with the automatic weld placement algorithm (if welds are included).\n\n\nWeld placement is aligned with the algorithm.\n\n\nWelds are not placed in alignment with the algorithm.\nBounded Plates\n\n\nHealth Check\nChecks that bounded plates are valid according to the bounded plate health checker.\n\n\nBounded plates are valid.\n\n\nBounded plates do not align with the current boundary conditions.\n\n\nBounded plates have missing elements or invalid references in the structural connection set.\nThe functionality is identical to the panels weld check.\nCatalog Joints\n\n\nConnection Check\nChecks that the CREF attribute of the fixing is set to a valid GENSEC or SCTN.\n\n\nConnection reference is valid.\n\n\nConnection reference is invalid, unset or not set to a GENSEC or SCTN element.\nCatalog Weld Check\nChecks that any welds in the STWSET for this fixing align with the JWELD definition in the catalog (If welds are included).\n\n\nWelds align with catalog definition.\n\n\nWelds have different positions compared to the catalog definition.\n\n\nInvalid references, or a different number of welds found compared to the catalog definition.\nTemplate Joints\n\n\nConnection Check\nThe functionality is identical to the catalog joints connection check.\nTemplate Rule Check\nChecks the template parameters and primitive elements are correct when compared with the template definition.\n\n\nAll template rules are valid and aligned with expected values.\n\n\nSome attributes of template elements differ from expected rule values. Specific attributes are indicated in the property grid description box.\nPanel Fittings\n\n\nTemplate Rule Check\nThe functionality is identical to the template joints template rule check (if fitting is a template).\nCatalog Weld Check\nThe functionality is identical to the catalog joints catalog weld check (if fitting is not a template and welds are included).\nGENSEC Fittings\nCurrently no checks available.\nWelds\n\n\nDetail Check\nChecks the Structural Weld Detail Reference (STWDTR) attribute is set to a valid weld detail.\n\n\nSTWDTR attribute is valid.\n\n\nSTWDTR attribute is unset.\n\n\nSTWDTR attribute is invalid.\nConnection Check\nChecks welds have two valid references in the Structural Weld Reference Array (STWRFA).\n\n\nAt least two valid elements in the STWRFA attribute.\n\n\nLess than two references in the array, or duplicate references found.\n\n\nInvalid connection references in the array.\nHandrail Components\n\n\nHandrail Connection Check\n\nChecks if a handrail component (Post, Termination, Panel or Gate) has a valid connection reference (CONREF).\n\n\nConnection reference is valid.\n\n\nConnection reference is unset or invalid.\n\nPass\nWarning\nFail\nGENSECs\nEnd Connections\nChecks the validity of the start and end connections. Both ends of the section should be connected, either via a fixing or an endatum.\nBoth ends connected.\nOne end disconnected.\nBoth ends disconnected.\nPanels\nWeld Check\nChecks the welds in the panel are aligned with the automatic weld placement algorithm (if welds are included).\nWeld placement is aligned with the algorithm.\nWelds are not placed in alignment with the algorithm.\nBounded Plates\nHealth Check\nChecks that bounded plates are valid according to the bounded plate health checker.\nBounded plates are valid.\nBounded plates do not align with the current boundary conditions.\nBounded plates have missing elements or invalid references in the structural connection set.\nWeld Check\nThe functionality is identical to the panels weld check.\nCatalog Joints\nConnection Check\nChecks that the CREF attribute of the fixing is set to a valid GENSEC or SCTN.\nConnection reference is valid.\nConnection reference is invalid, unset or not set to a GENSEC or SCTN element.\nCatalog Weld Check\nChecks that any welds in the STWSET for this fixing align with the JWELD definition in the catalog (If welds are included).\nWelds align with catalog definition.\nWelds have different positions compared to the catalog definition.\nInvalid references, or a different number of welds found compared to the catalog definition.\nTemplate Joints\nConnection Check\nThe functionality is identical to the catalog joints connection check.\nTemplate Rule Check\nChecks the template parameters and primitive elements are correct when compared with the template definition.\nAll template rules are valid and aligned with expected values.\nSome attributes of template elements differ from expected rule values. Specific attributes are indicated in the property grid description box.\nPanel Fittings\nTemplate Rule Check\nThe functionality is identical to the template joints template rule check (if fitting is a template).\nCatalog Weld Check\nThe functionality is identical to the catalog joints catalog weld check (if fitting is not a template and welds are included).\nGENSEC Fittings\nCurrently no checks available.\nWelds\nDetail Check\nChecks the Structural Weld Detail Reference (STWDTR) attribute is set to a valid weld detail.\nSTWDTR attribute is valid.\nSTWDTR attribute is unset.\nSTWDTR attribute is invalid.\nConnection Check\nChecks welds have two valid references in the Structural Weld Reference Array (STWRFA).\nAt least two valid elements in the STWRFA attribute.\nLess than two references in the array, or duplicate references found.\nInvalid connection references in the array.\nHandrail Components\nHandrail Connection Check\nChecks if a handrail component (Post, Termination, Panel or Gate) has a valid connection reference (CONREF).\nConnection reference is valid.\nConnection reference is unset or invalid.\n\n\n\nProperties\nConnection Review\nRefresh\nProperties\nPass\nWarning\nFail\nGENSECs\nEnd Connections\nPanels\nWeld Check\nBounded Plates\nHealth Check\nWeld Check\nCatalog Joints\nConnection Check\nCatalog Weld Check\nTemplate Joints\nConnection Check\nTemplate Rule Check\nPanel Fittings\nTemplate Rule Check\nCatalog Weld Check\nGENSEC Fittings\nWelds\nDetail Check\nConnection Check\nHandrail Components\nHandrail Connection Check"}
{"Headers": "Rule Review", "Content": "The Rules tab supports the rules engine and provides functionality to review the currently selected elements in the Flexible Explorer against the original design intent. Use the Rules tab to:\n\nRules are categorized into groups determined by their purpose. The Rules tab displays the status of each rules check:\nPass\nThe property value is aligned with the rule.\nAccepted\nThe property value is not aligned with rule but has been accepted (refer to accepting values for further information).\nWarning\nThe property value is not aligned with rule, but the value is in the valid values list.\nFail\nThe property value is not aligned with rule.\nPass\n\nThe property value is aligned with the rule.\nAccepted\n\nThe property value is not aligned with rule but has been accepted (refer to accepting values for further information).\nWarning\n\nThe property value is not aligned with rule, but the value is in the valid values list.\nFail\n\nThe property value is not aligned with rule.\nRight-click on any rule to display a drop-down menu.\n\nReset All Values to Rule\nChanges each rule-driven attribute/property of the element to the rule-driven value. Rules are re-executed in order from top to bottom, as some rules may influence others.\nReset <rule> to Rule\nChanges the currently selected attribute/property to the rule-driven value.\nNavigate to <rule>\nOpens the Ruleset Browser window to find the currently selected rule.\nExpand All\nExpands all rules to display information about the executed logic.\nReset Expansion\nResets the grid to the original expansion.\nCollapse All\nCollapses all rules to the category level.\nReset All Values to Rule\nChanges each rule-driven attribute/property of the element to the rule-driven value. Rules are re-executed in order from top to bottom, as some rules may influence others.\nReset <rule> to Rule\nChanges the currently selected attribute/property to the rule-driven value.\nNavigate to <rule>\nOpens the Ruleset Browser window to find the currently selected rule.\nExpand All\nExpands all rules to display information about the executed logic.\nReset Expansion\nResets the grid to the original expansion.\nCollapse All\nCollapses all rules to the category level.\nAccept Value\nRight-click on an attribute that does not align with the rule, to display an additional option from the drop-down menu to accept the current value.\n\nValues which are accepted are considered to pass the rule check in the Connection Review window, even though the value of the property does not align with the rule.\nRules which are accepted for each element are stored in the database. To find which rules are accepted for an element outside the window, query the ROKEYS and ROVALS attributes. These represent the names of accepted attributes, and values which have been accepted.\nIf the property value is changed after acceptance, the rule review again reports a warning or fail. If the value is changed to align with the rule, the review reports a pass, even if another value was accepted.\nA value can be rejected after it has been accepted to undo the acceptance.\n\nPass\nThe property value is aligned with the rule.\nAccepted\nThe property value is not aligned with rule but has been accepted (refer to accepting values for further information).\nWarning\nThe property value is not aligned with rule, but the value is in the valid values list.\nFail\nThe property value is not aligned with rule.\nReset All Values to Rule\nChanges each rule-driven attribute/property of the element to the rule-driven value. Rules are re-executed in order from top to bottom, as some rules may influence others.\nReset <rule> to Rule\nChanges the currently selected attribute/property to the rule-driven value.\nNavigate to <rule>\nOpens the Ruleset Browser window to find the currently selected rule.\nExpand All\nExpands all rules to display information about the executed logic.\nReset Expansion\nResets the grid to the original expansion.\nCollapse All\nCollapses all rules to the category level.\nIdentify which attributes and properties of an element have been set by the rules engine.\nCheck that any rule-derived properties still follow the original design intent.\nReset attributes to the original rule-derived value if they are different.\nMake manual adjustments to any values using the property grid.\nAccept variances from the design intent and prevent the system from checking further.\nNavigate to the original rule to interrogate the logic.\nIdentify which attributes and properties of an element have been set by the rules engine.\nIdentify which attributes and properties of an element have been set by the rules engine.\nCheck that any rule-derived properties still follow the original design intent.\nCheck that any rule-derived properties still follow the original design intent.\nReset attributes to the original rule-derived value if they are different.\nReset attributes to the original rule-derived value if they are different.\nMake manual adjustments to any values using the property grid.\nMake manual adjustments to any values using the property grid.\nAccept variances from the design intent and prevent the system from checking further.\nAccept variances from the design intent and prevent the system from checking further.\nNavigate to the original rule to interrogate the logic.\nNavigate to the original rule to interrogate the logic.\n\n\n\nRules\nRules\nRules\nPass\nAccepted\nWarning\nFail\nReset All Values to Rule\nReset <rule> to Rule\nNavigate to <rule>\nRuleset Browser\nExpand All\nReset Expansion\nCollapse All\nAccept Value\nConnection Review"}
{"Headers": "Joints", "Content": "Each connected section is created with JLDATU, PLDATU and FIXING elements in the Design database.\n\nIn order to represent the connections properly, a catalogue specification must be associated with each joint (in the same way that each section profile is defined by an associated catalogue specification). Joint detail can be automatically defined when sections are connected, refer to Automatic Joint Selection for further information. Alternatively, joint detail can be manually created, refer to Modify Joint for further information.\nA merged joint can be created from one or more existing joints, refer to Create Merged Joint for further information.\n\n\n\nAutomatic Joint Selection\nModify Joint\nCreate Merged Joint\nAutomatic Joint Selection\nModify Joint\nCreate Merged Joint"}
{"Headers": "Automatic Joint Selection", "Content": "The automatic joint selection setting changes the behaviour of the structural application to automatically select details for created joints where possible. The setting requires configuration in the catalogue to work correctly:\nAutomatic joint selection can be turned on or off using the Fluent UI.\nIf the option is highlighted, automatic joint selection is on.\nIf the option is not highlighted, automatic joint selection is off.\nAutomatic Joint Selection On\nWhen automatic joint selection is turned on, the functionality differs for joint creation and joint modification.\nJoint Creation\nThe functionality automatically selects joints when a section connection is made, refer to Connect Sections for further information. Each connection is analyzed and logic stored in the joint specification is applied. Any associated rules are also executed. If no match is found between the current joint and the criteria defined in the automatic joint specification, no joint detail is applied.\nJoint Modification\nThe automatic joint system can execute and change connections when sections are modified. Connections can be changed as per the dynamic connectivity rules, refer to Dynamic Connectivity Rules for further information. If a connection changes when automatic joints are turned on and correctly configured, the following logic is applied:\nAutomatic Joint Selection Off or No Automatic Joint Specification found in Project\nWhen automatic joint selection is turned off, the functionality differs for joint creation and joint modification.\nJoint Creation\nWhen a section connection is made, no joint specification is applied.\nJoint Modification\nWhen a section is modified, the joints on any connections remain unchanged\nAn automatic joint specification must be defined in PARAGON using the Structural Joints Specification window, refer to Structural Specifications for further information.\nThe specification and default specific type must be chosen in the Joint List window, refer to Automatic Joint and Baseplate Selection State for further information.\nAn automatic joint specification must be defined in PARAGON using the Structural Joints Specification window, refer to Structural Specifications for further information.\nAn automatic joint specification must be defined in PARAGON using the Structural Joints Specification window, refer to Structural Specifications for further information.\nThe specification and default specific type must be chosen in the Joint List window, refer to Automatic Joint and Baseplate Selection State for further information.\nThe specification and default specific type must be chosen in the Joint List window, refer to Automatic Joint and Baseplate Selection State for further information.\nIf the specification reference of the fixing is unset, the system attempts to select and create a joint from the specification.\nIf the specification reference is set, and was previously selected from an automatic joint specification, the system attempts to update the joint based on the current design context.\nIf the existing detail is valid, any rules on the joint are re-executed to align with the current context.\nOtherwise, if a new valid detail is found, the existing joint is removed and a new one added to replace it.\nIf the specification reference is selected from a manual specification, the joint is not updated. Once created, automatic joints can be managed using the Joint List window.\nIf the specification reference of the fixing is unset, the system attempts to select and create a joint from the specification.\nIf the specification reference of the fixing is unset, the system attempts to select and create a joint from the specification.\nIf the specification reference is set, and was previously selected from an automatic joint specification, the system attempts to update the joint based on the current design context.\nIf the existing detail is valid, any rules on the joint are re-executed to align with the current context.\nOtherwise, if a new valid detail is found, the existing joint is removed and a new one added to replace it.\nIf the specification reference is set, and was previously selected from an automatic joint specification, the system attempts to update the joint based on the current design context.\nIf the specification reference is selected from a manual specification, the joint is not updated. Once created, automatic joints can be managed using the Joint List window.\nIf the specification reference is selected from a manual specification, the joint is not updated. Once created, automatic joints can be managed using the Joint List window.\n\n\n\nStructural Specifications\nAutomatic Joint and Baseplate Selection State\nConnect Sections\nDynamic Connectivity Rules\nStructural Specifications\nAutomatic Joint and Baseplate Selection State\nAutomatic Joint Selection On\nJoint Creation\nConnect Sections\nJoint Modification\nDynamic Connectivity Rules\nAutomatic Joint Selection Off or No Automatic Joint Specification found in Project\nJoint Creation\nJoint Modification"}
{"Headers": "Automatic Joint Reselection", "Content": "Automatically modifies the catalogue specification associated with selected joints.\nIf connections are created without joint detailing, modifications are made to sections in the model or to the automatic joint specification, it may be necessary to apply automatic joint selection to a set of selected joints.\nYou are prompted to Select section(s)\nClick to identify the sections that contain joints to be modified and press Enter. The joints are highlighted in the 3D view, each joint displays as a joint pin.\n\nThe selection status of each joint is indicated by the joint pin colour.\nYou are then prompted to Select joints\nClick to identify the joints to be modified and press Enter to automatically modify the catalogue specification associated with each selected joint.\nEach connection is analyzed and criteria stored in the joint selection specification is applied. If no match is found between the current joint and the criteria defined in the automatic joint specification, the joint detail is not modified.\nCyan = Unselected joint\nRed = Selected joint.\nCyan = Unselected joint\nCyan = Unselected joint\nRed = Selected joint.\nRed = Selected joint.\nNote:\nThe prompt does not display if the section elements are already selected.\n\n\n\nSelect section(s)\nNote\n:\nEnter\nSelect joints\nEnter"}
{"Headers": "Automatic Joint and Baseplate Selection State", "Content": "Displays joint information and performs automatic joint selection on selected joints.\nDisplays baseplate information and performs automatic baseplate selection on end datums at section ends.\n\nSelection\nClick to update the joint list to include joints that are currently selected in the 3D view.\nTrack\nSelect the check box to track the currently selected element in the Model Explorer or 3D view.\nIf a single selection is made in the joint list, the FIXING is selected in the Model Explorer.\nIf a GENSEC is selected in the Model Explorer, the FIXINGs at each end are selected in the joint list.\nIf the GENSEC start or end has no connection, only one FIXING is selected in the joint list.\nIf neither the GENSEC start or end is connected, the joint list is cleared.\nIf any element under the GENSEC is selected, that specifically defines the geometry of the GENSEC, for example, SPINE or POINSP, the behavior is the same as picking a GENSEC.\nIf a JLDATU or PLDATU is selected in the Model Explorer, the FIXINGs located under the picked datum are selected in the joint list.\nIf a specific FIXING is selected in the 3D view using the PowerWheel, the FIXING is selected in the joint list.\nIf a FIXING is picked in the Model Explorer, or any item under the FIXING, for example, a TMPL or element that makes up the template, the owning FIXING is selected in the joint list.\nThe joint list is cleared if:\nAn element is selected in the 3D view that is not in the GENSEC hierarchy.\nAny element is selected in the Model Explorer that is not in the GENSEC hierarchy.\nA GENSEC or FIXING is selected in the 3d view or model explorer that is not in the current selection list.\nShow Tags\nSelect the check box to display automatic joint selection tags in the 3D view for the currently selected joints in the joint list.\nSelect Description from the drop-down list to display the desc attribute of the catalogue reference of the joint.\nSelect Reference from the drop-down list to display the name of the specification reference.\nSelect Joint Name from the drop-down list to display the name of the joint in the design database.\nNote:\nIf there is no description set, or the joint is not named, the name of the specification reference is displayed by default.\nRefresh\nClick to refresh the joint list, the joint list is not updated to include joints that are currently selected in the 3D view.\nAutomatic Joint Specification\nSelect from the drop-down list to define the currently used joint selection specification. If there are no automatic joint specifications, the drop-down list becomes inactive.\nAutomatic Baseplate Specification\nSelect from the drop-down list to define the currently used baseplate selection specification. If there are no automatic baseplate specifications, the drop-down list becomes inactive.\nType\nSelect an STYP element from the drop-down list to be applied to all currently selected joints in the joint list that match the criteria stored in the automatic joint specification. If no match is found between a selected joint and the criteria defined in the automatic joint specification, the joint detail is not modified.\nSelect Default from the drop-down list to apply the default Specification Component (SPCO) or a defined SPCO to all currently selected joints in the joint list that match the criteria stored in the automatic joint specification. The applied SPCO is specified in the automatic joint specification.\nSelection\nClick to update the joint list to include joints that are currently selected in the 3D view.\nTrack\nSelect the check box to track the currently selected element in the Model Explorer or 3D view.\nIf a single selection is made in the joint list, the FIXING is selected in the Model Explorer.\nIf a GENSEC is selected in the Model Explorer, the FIXINGs at each end are selected in the joint list.\nIf a JLDATU or PLDATU is selected in the Model Explorer, the FIXINGs located under the picked datum are selected in the joint list.\nIf a specific FIXING is selected in the 3D view using the PowerWheel, the FIXING is selected in the joint list.\nIf a FIXING is picked in the Model Explorer, or any item under the FIXING, for example, a TMPL or element that makes up the template, the owning FIXING is selected in the joint list.\nThe joint list is cleared if:\nShow Tags\nSelect the check box to display automatic joint selection tags in the 3D view for the currently selected joints in the joint list.\nSelect Description from the drop-down list to display the desc attribute of the catalogue reference of the joint.\nSelect Reference from the drop-down list to display the name of the specification reference.\nSelect Joint Name from the drop-down list to display the name of the joint in the design database.\n\nRefresh\nClick to refresh the joint list, the joint list is not updated to include joints that are currently selected in the 3D view.\nAutomatic Joint Specification\nSelect from the drop-down list to define the currently used joint selection specification. If there are no automatic joint specifications, the drop-down list becomes inactive.\nAutomatic Baseplate Specification\nSelect from the drop-down list to define the currently used baseplate selection specification. If there are no automatic baseplate specifications, the drop-down list becomes inactive.\nType\nSelect an STYP element from the drop-down list to be applied to all currently selected joints in the joint list that match the criteria stored in the automatic joint specification. If no match is found between a selected joint and the criteria defined in the automatic joint specification, the joint detail is not modified.\nSelect Default from the drop-down list to apply the default Specification Component (SPCO) or a defined SPCO to all currently selected joints in the joint list that match the criteria stored in the automatic joint specification. The applied SPCO is specified in the automatic joint specification.\n\nThe Joint List part of the Joint List window displays details for selected joints in the 3D view.\n\nFilter criteria can be used to specify which joints are displayed in the joint list. Refer to GUI Grid Data for further information.\nJoint Name\nDisplays the name of the joint (FIXING) element.\nSpecification\nDisplays the joint specification from which the joint was selected.\nComponent\nDisplays the name of the specification reference.\nDescription\nDisplays the description from the joint, or from the catalogue if the joint description is unset.\nType\nDisplays the STYPE of the joint, TYPE is displayed if the STYPE in unset.\nDefault\nDisplays the default STYPE for the joint.\nIf the default is set to = and the Type is set to Default, the application ignores the Type (STYP) and selects the first specification component (SPCO) where all the other criteria are met.\nIf the default is set to WEL, the application uses the WEL (SPCO) if all the other criteria are met.\nPos Line\nDisplays the Pline that the attached section is connected to.\nSelection\nDisplays the joint selection specification status.\nAutomatic\nAn automatic joint selection specification is applied to the joint.\nManual\nA standard joint specification is applied to the joint.\nUnset\nThe joint specification is unset.\nInvalid\nThe joint specification reference is set, but is pointing to an unknown element.\nChoices\nDisplays the number of choices available for the joint in the automatic joint specification. The automatic joint selection system makes a default choice if there is more than one joint detail option available. If there is more than one choice, an alternative joint detail can be selected using the Select alternative joint drop-down list.\nMessage\nIndicates the validity of joints with automatic joint selection applied.\nValid\nThe current automatic joint selection specification is valid for the joint.\nUpdate Selection\nThe current automatic joint selection specification is not valid for the joint and must be reselected.\nAttached Section\nDisplays the catalogue reference of the attached section.\nOwner Type\nDisplays the owning element type.\nAccess\nIndicates if current access to the joint is write or read only.\nJoint Name\nDisplays the name of the joint (FIXING) element.\nSpecification\nDisplays the joint specification from which the joint was selected.\nComponent\nDisplays the name of the specification reference.\nDescription\nDisplays the description from the joint, or from the catalogue if the joint description is unset.\nType\nDisplays the STYPE of the joint, TYPE is displayed if the STYPE in unset.\nDefault\nDisplays the default STYPE for the joint.\nIf the default is set to = and the Type is set to Default, the application ignores the Type (STYP) and selects the first specification component (SPCO) where all the other criteria are met.\nIf the default is set to WEL, the application uses the WEL (SPCO) if all the other criteria are met.\nPos Line\nDisplays the Pline that the attached section is connected to.\nSelection\nDisplays the joint selection specification status.\nAutomatic\nAn automatic joint selection specification is applied to the joint.\nManual\nA standard joint specification is applied to the joint.\nUnset\nThe joint specification is unset.\nInvalid\nThe joint specification reference is set, but is pointing to an unknown element.\nChoices\nDisplays the number of choices available for the joint in the automatic joint specification. The automatic joint selection system makes a default choice if there is more than one joint detail option available. If there is more than one choice, an alternative joint detail can be selected using the Select alternative joint drop-down list.\nMessage\nIndicates the validity of joints with automatic joint selection applied.\nValid\nThe current automatic joint selection specification is valid for the joint.\nUpdate Selection\nThe current automatic joint selection specification is not valid for the joint and must be reselected.\nAttached Section\nDisplays the catalogue reference of the attached section.\nOwner Type\nDisplays the owning element type.\nAccess\nIndicates if current access to the joint is write or read only.\nIf an invalid joint is selected, the joint reference remains unchanged and a warning displays in the first column. Hover over the warning to display a tooltip message summarizing the problem.\n\nRight click on the headings part of the joint list to display a drop-down menu which allows you to show and hide column data. The column settings are preserved between sessions.\n\nRight-click on the joint list to display a drop-down menu.\n\nAutomatic Joint Select\nClick to perform automatic joint selection for all currently selected joints in the joint list.\nRe-execute Rules\nClick to re-execute the rules for the currently selected joints or baseplates in the joint list and to reset their design parameters based on the rules associated with the joint.\nAdd to 3D View\nClick to display the currently selected joints in the 3D view.\nFocus on Joint\nClick to modify the display of the 3D view to include the currently selected joints.\nNavigate to\nClick to navigate to the currently selected element in the 3D view and the Model Explorer.\nExport to Excel\nExports the joint list to an Excel file. Click to display the Save to Excel window. Navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the joint list in the Print Preview window.\nAutomatic Joint Select\nClick to perform automatic joint selection for all currently selected joints in the joint list.\nRe-execute Rules\nClick to re-execute the rules for the currently selected joints or baseplates in the joint list and to reset their design parameters based on the rules associated with the joint.\nAdd to 3D View\nClick to display the currently selected joints in the 3D view.\nFocus on Joint\nClick to modify the display of the 3D view to include the currently selected joints.\nNavigate to\nClick to navigate to the currently selected element in the 3D view and the Model Explorer.\nExport to Excel\nExports the joint list to an Excel file. Click to display the Save to Excel window. Navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the joint list in the Print Preview window.\nThe Messages part of the Joint List window displays a message summary for the currently selected joint.\n\nThe Select from Automatic Joint Specification part of the Joint List window displays the automatic joint selection status and the current specification.\n\nAutomatic\nClick to perform automatic joint selection for all currently selected joints in the joint list.\nSelect Alternative Joint\nUse the drop-down list to select an alternative joint component from the joint specification that matches the criteria for the selected joint. The option is only active if the joint list is populated and more than one automatic joint is available.\nFunctionality is available to select alternative joints for more than one joint. However, the joints selected in the joint list must have the same alternatives available. If they do not, the alternative joint list becomes inactive\nAutomatic\nClick to perform automatic joint selection for all currently selected joints in the joint list.\nSelect Alternative Joint\nUse the drop-down list to select an alternative joint component from the joint specification that matches the criteria for the selected joint. The option is only active if the joint list is populated and more than one automatic joint is available.\nFunctionality is available to select alternative joints for more than one joint. However, the joints selected in the joint list must have the same alternatives available. If they do not, the alternative joint list becomes inactive\n\nSelection\nClick to update the joint list to include joints that are currently selected in the 3D view.\nTrack\nSelect the check box to track the currently selected element in the Model Explorer or 3D view.\nIf a single selection is made in the joint list, the FIXING is selected in the Model Explorer.\nIf a GENSEC is selected in the Model Explorer, the FIXINGs at each end are selected in the joint list.\nIf the GENSEC start or end has no connection, only one FIXING is selected in the joint list.\nIf neither the GENSEC start or end is connected, the joint list is cleared.\nIf any element under the GENSEC is selected, that specifically defines the geometry of the GENSEC, for example, SPINE or POINSP, the behavior is the same as picking a GENSEC.\nIf a JLDATU or PLDATU is selected in the Model Explorer, the FIXINGs located under the picked datum are selected in the joint list.\nIf a specific FIXING is selected in the 3D view using the PowerWheel, the FIXING is selected in the joint list.\nIf a FIXING is picked in the Model Explorer, or any item under the FIXING, for example, a TMPL or element that makes up the template, the owning FIXING is selected in the joint list.\nThe joint list is cleared if:\nAn element is selected in the 3D view that is not in the GENSEC hierarchy.\nAny element is selected in the Model Explorer that is not in the GENSEC hierarchy.\nA GENSEC or FIXING is selected in the 3d view or model explorer that is not in the current selection list.\nShow Tags\nSelect the check box to display automatic joint selection tags in the 3D view for the currently selected joints in the joint list.\nSelect Description from the drop-down list to display the desc attribute of the catalogue reference of the joint.\nSelect Reference from the drop-down list to display the name of the specification reference.\nSelect Joint Name from the drop-down list to display the name of the joint in the design database.\nNote:\nIf there is no description set, or the joint is not named, the name of the specification reference is displayed by default.\nRefresh\nClick to refresh the joint list, the joint list is not updated to include joints that are currently selected in the 3D view.\nAutomatic Joint Specification\nSelect from the drop-down list to define the currently used joint selection specification. If there are no automatic joint specifications, the drop-down list becomes inactive.\nAutomatic Baseplate Specification\nSelect from the drop-down list to define the currently used baseplate selection specification. If there are no automatic baseplate specifications, the drop-down list becomes inactive.\nType\nSelect an STYP element from the drop-down list to be applied to all currently selected joints in the joint list that match the criteria stored in the automatic joint specification. If no match is found between a selected joint and the criteria defined in the automatic joint specification, the joint detail is not modified.\nSelect Default from the drop-down list to apply the default Specification Component (SPCO) or a defined SPCO to all currently selected joints in the joint list that match the criteria stored in the automatic joint specification. The applied SPCO is specified in the automatic joint specification.\nJoint Name\nDisplays the name of the joint (FIXING) element.\nSpecification\nDisplays the joint specification from which the joint was selected.\nComponent\nDisplays the name of the specification reference.\nDescription\nDisplays the description from the joint, or from the catalogue if the joint description is unset.\nType\nDisplays the STYPE of the joint, TYPE is displayed if the STYPE in unset.\nDefault\nDisplays the default STYPE for the joint.\nIf the default is set to = and the Type is set to Default, the application ignores the Type (STYP) and selects the first specification component (SPCO) where all the other criteria are met.\nIf the default is set to WEL, the application uses the WEL (SPCO) if all the other criteria are met.\nPos Line\nDisplays the Pline that the attached section is connected to.\nSelection\nDisplays the joint selection specification status.\nAutomatic\nAn automatic joint selection specification is applied to the joint.\nManual\nA standard joint specification is applied to the joint.\nUnset\nThe joint specification is unset.\nInvalid\nThe joint specification reference is set, but is pointing to an unknown element.\nChoices\nDisplays the number of choices available for the joint in the automatic joint specification. The automatic joint selection system makes a default choice if there is more than one joint detail option available. If there is more than one choice, an alternative joint detail can be selected using the Select alternative joint drop-down list.\nMessage\nIndicates the validity of joints with automatic joint selection applied.\nValid\nThe current automatic joint selection specification is valid for the joint.\nUpdate Selection\nThe current automatic joint selection specification is not valid for the joint and must be reselected.\nAttached Section\nDisplays the catalogue reference of the attached section.\nOwner Type\nDisplays the owning element type.\nAccess\nIndicates if current access to the joint is write or read only.\nAutomatic Joint Select\nClick to perform automatic joint selection for all currently selected joints in the joint list.\nRe-execute Rules\nClick to re-execute the rules for the currently selected joints or baseplates in the joint list and to reset their design parameters based on the rules associated with the joint.\nAdd to 3D View\nClick to display the currently selected joints in the 3D view.\nFocus on Joint\nClick to modify the display of the 3D view to include the currently selected joints.\nNavigate to\nClick to navigate to the currently selected element in the 3D view and the Model Explorer.\nExport to Excel\nExports the joint list to an Excel file. Click to display the Save to Excel window. Navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the joint list in the Print Preview window.\nAutomatic\nClick to perform automatic joint selection for all currently selected joints in the joint list.\nSelect Alternative Joint\nUse the drop-down list to select an alternative joint component from the joint specification that matches the criteria for the selected joint. The option is only active if the joint list is populated and more than one automatic joint is available.\nFunctionality is available to select alternative joints for more than one joint. However, the joints selected in the joint list must have the same alternatives available. If they do not, the alternative joint list becomes inactive\nIf the GENSEC start or end has no connection, only one FIXING is selected in the joint list.\nIf neither the GENSEC start or end is connected, the joint list is cleared.\nIf any element under the GENSEC is selected, that specifically defines the geometry of the GENSEC, for example, SPINE or POINSP, the behavior is the same as picking a GENSEC.\nIf the GENSEC start or end has no connection, only one FIXING is selected in the joint list.\nIf the GENSEC start or end has no connection, only one FIXING is selected in the joint list.\nIf neither the GENSEC start or end is connected, the joint list is cleared.\nIf neither the GENSEC start or end is connected, the joint list is cleared.\nIf any element under the GENSEC is selected, that specifically defines the geometry of the GENSEC, for example, SPINE or POINSP, the behavior is the same as picking a GENSEC.\nIf any element under the GENSEC is selected, that specifically defines the geometry of the GENSEC, for example, SPINE or POINSP, the behavior is the same as picking a GENSEC.\nAn element is selected in the 3D view that is not in the GENSEC hierarchy.\nAny element is selected in the Model Explorer that is not in the GENSEC hierarchy.\nA GENSEC or FIXING is selected in the 3d view or model explorer that is not in the current selection list.\nAn element is selected in the 3D view that is not in the GENSEC hierarchy.\nAn element is selected in the 3D view that is not in the GENSEC hierarchy.\nAny element is selected in the Model Explorer that is not in the GENSEC hierarchy.\nAny element is selected in the Model Explorer that is not in the GENSEC hierarchy.\nA GENSEC or FIXING is selected in the 3d view or model explorer that is not in the current selection list.\nA GENSEC or FIXING is selected in the 3d view or model explorer that is not in the current selection list.\nNote:\nIf there is no description set, or the joint is not named, the name of the specification reference is displayed by default.\n\n\n\nGUI Grid Data\nSelection\nTrack\nShow Tags\nDescription\nReference\nJoint Name\nNote:\nRefresh\nAutomatic Joint Specification\nAutomatic Baseplate Specification\nType\nDefault\nJoint List\nJoint List\nGUI Grid Data\nJoint Name\nSpecification\nComponent\nDescription\nType\nDefault\n=\nType\nDefault\nWEL\nWEL\nPos Line\nSelection\nAutomatic\nManual\nUnset\nInvalid\nChoices\nSelect alternative joint\nMessage\nValid\nUpdate Selection\nAttached Section\nOwner Type\nAccess\nAutomatic Joint Select\nRe-execute Rules\nAdd to 3D View\nFocus on Joint\nNavigate to\nExport to Excel\nSave to Excel\nPrint Preview\nPrint Preview\nMessages\nJoint List\nSelect from Automatic Joint Specification\nJoint List\nAutomatic\nSelect Alternative Joint"}
{"Headers": "Create Merged Joint", "Content": "Creates a Merged Fixing (MFIX) element from one or more existing joints. A merged joint can be used to indicate such things as a gusset plate or a star plate.\nMerged joints are soft fixings that display in the Model Explorer as PLDATU, MFIX and TMPL elements, owned by the first JLDATU within a GENSEC element. Refer to Section Connectivity for further information.\nYou are prompted to Select owning section\nClick to identify the section to associate with the merged joint using a cursor pick in the 3D view.\nYou are then prompted to Select joints\nThe joints are highlighted in the 3D view, each joint displays as a joint pin.\n\nThe selection status of each joint is indicated by the joint pin colour.\nClick to identify the joints to be merged and press Enter to display the Merged Joint window.\n\nThe Merged Joint window allows you to associate a catalogue specification with the currently selected joints and modify the dimensions of the merged joint component parts.\nSelection\nClick to remove all joints from the current selection.\nThe number of currently selected joints displays adjacent to the icon.\nNote:\nThe functionality is only available when a merged joint is created.\nSpecification\nSelect from the drop-down list to display all the available groups of merged joint components covered by a specification. Once a specification has been selected from the drop-down list, the Joint Group and Joint galleries are automatically populated with joint group and joint components available for selection.\nNote:\nAn automatically selected joint is displayed as Unset in the specification and can be modified to a standard joint using the drop-down list.\nNote:\nThe functionality is only available when a merged joint is created.\nJoint Group\nSelect from the gallery to display all the available joint components. Once a group has been selected, the Joint gallery is automatically populated with the joint components available for selection.\nNote:\nThe functionality is only available when a merged joint is created.\nJoint\nSelect a joint component from the gallery. Once a joint has been selected, the Design Parameters fields are automatically populated with default values.\nReference\nClick to associate a reference element with the merged joint. The reference element can be either a section or a panel.\nNote:\nSelection of a reference element is not required for all merged joints.\nYou are prompted to Select reference element\nClick to identify the section or panel to associate with the merged joint using a cursor pick in the 3D view.\nYou are prompted to Set specification\nPress Enter to associate the reference element with the merged joint.\nUpdate\nClick to update the merged joint with modified design parameters.\nNote:\nThe functionality is only available when a merged joint is modified.\nDesign Parameters\nInput values in the fields to modify the dimensions of the merged joint component parts.\nDetail\nClick to display a detailed image of the merged joint. The image window displays a detailed description of the merged joint geometry and the different parameters and variables that can be applied to the merged joint.\n\nSelection\nClick to remove all joints from the current selection.\nThe number of currently selected joints displays adjacent to the icon.\n\nSpecification\nSelect from the drop-down list to display all the available groups of merged joint components covered by a specification. Once a specification has been selected from the drop-down list, the Joint Group and Joint galleries are automatically populated with joint group and joint components available for selection.\n\nJoint Group\nSelect from the gallery to display all the available joint components. Once a group has been selected, the Joint gallery is automatically populated with the joint components available for selection.\n\nJoint\nSelect a joint component from the gallery. Once a joint has been selected, the Design Parameters fields are automatically populated with default values.\n\nReference\nClick to associate a reference element with the merged joint. The reference element can be either a section or a panel.\nYou are prompted to Select reference element\nClick to identify the section or panel to associate with the merged joint using a cursor pick in the 3D view.\nYou are prompted to Set specification\nPress Enter to associate the reference element with the merged joint.\n\nUpdate\nClick to update the merged joint with modified design parameters.\n\nDesign Parameters\nInput values in the fields to modify the dimensions of the merged joint component parts.\n\nDetail\nClick to display a detailed image of the merged joint. The image window displays a detailed description of the merged joint geometry and the different parameters and variables that can be applied to the merged joint.\n\nClick Apply to accept the merged joint settings.\nIf the Gtype of the owning section is CTUB (Circular Hollow Section), you are prompted to Set P-line\nClick to identify the P-line position of the owning section and press Enter.\nA merged joint is created and displays in the 3D view.\n\nThe new PLDATU, MFIX and TMPL elements display in the Model Explorer. The original FIXING JLDATU, PLDATU and FIXING elements are retained.\n\nSelection\nClick to remove all joints from the current selection.\nThe number of currently selected joints displays adjacent to the icon.\nNote:\nThe functionality is only available when a merged joint is created.\nSpecification\nSelect from the drop-down list to display all the available groups of merged joint components covered by a specification. Once a specification has been selected from the drop-down list, the Joint Group and Joint galleries are automatically populated with joint group and joint components available for selection.\nNote:\nAn automatically selected joint is displayed as Unset in the specification and can be modified to a standard joint using the drop-down list.\nNote:\nThe functionality is only available when a merged joint is created.\nJoint Group\nSelect from the gallery to display all the available joint components. Once a group has been selected, the Joint gallery is automatically populated with the joint components available for selection.\nNote:\nThe functionality is only available when a merged joint is created.\nJoint\nSelect a joint component from the gallery. Once a joint has been selected, the Design Parameters fields are automatically populated with default values.\nReference\nClick to associate a reference element with the merged joint. The reference element can be either a section or a panel.\nNote:\nSelection of a reference element is not required for all merged joints.\nYou are prompted to Select reference element\nClick to identify the section or panel to associate with the merged joint using a cursor pick in the 3D view.\nYou are prompted to Set specification\nPress Enter to associate the reference element with the merged joint.\nUpdate\nClick to update the merged joint with modified design parameters.\nNote:\nThe functionality is only available when a merged joint is modified.\nDesign Parameters\nInput values in the fields to modify the dimensions of the merged joint component parts.\nDetail\nClick to display a detailed image of the merged joint. The image window displays a detailed description of the merged joint geometry and the different parameters and variables that can be applied to the merged joint.\nCyan = Deselected joint\nRed = Selected joint.\nCyan = Deselected joint\nCyan = Deselected joint\nRed = Selected joint.\nRed = Selected joint.\nNote:\nThe prompt does not display if the section element is already selected.\nNote:\nThe functionality is only available when a merged joint is created.\nNote:\nAn automatically selected joint is displayed as Unset in the specification and can be modified to a standard joint using the drop-down list.\nNote:\nThe functionality is only available when a merged joint is created.\nNote:\nThe functionality is only available when a merged joint is created.\nNote:\nSelection of a reference element is not required for all merged joints.\nNote:\nThe functionality is only available when a merged joint is modified.\n\n\n\nSection Connectivity\nSection Connectivity\nSelect owning section\nNote:\nSelect joints\nEnter\nMerged Joint\nMerged Joint\nSelection\nNote:\nSpecification\nJoint Group\nJoint\nNote:\nUnset\nNote:\nJoint Group\nJoint\nNote:\nJoint\nDesign Parameters\nReference\nNote:\nSelect reference element\nSet specification\nEnter\nUpdate\nNote\n:\nDesign Parameters\nDetail\nApply\nSet P-line\nEnter"}
{"Headers": "Create Section Fitting", "Content": "Creates a Fitting (FIXING) element which can be used to represent any item which is attached to the structure but which does not form an integral part of it. It may be used to indicate such things as the presence of a connected implied load, such as a pipe hanger attachment, or an ancillary item such as a web stiffener or a flange plate.\nSection fittings are auxiliary structural catalogue items that display in the Model Explorer as JLDATU, PLDATU and FIXING elements owned by GENSEC elements. Refer to Section Connectivity for further information. Each section fitting is designed to be associated with one or more Plines for the section profile it is attached to. One section fitting type can be applied to all sizes of a profile category.\nYou are prompted to Select section\nClick to identify the section to associate with the fitting, the Section Fitting window displays.\nThe Section Fitting window allows you to associate a catalogue specification with the fitting and modify the dimensions of the fitting component parts.\n\nSpecification\nSelect from the drop down list to display all the available groups of fitting component available for the section. Once a specification has been selected from the drop-down list, the Fitting Group and Fitting galleries are automatically populated with fitting group and fitting components available for selection.\nFitting Group\nSelect from the gallery to display all the available fitting components. Once a group has been selected, the Fitting gallery is automatically populated with the fitting components available for selection.\nFitting\nSelect a fitting component from the gallery. Once a fitting has been selected, the Design Parameters fields are automatically populated with default values.\nDesign Parameters\nInput values in the fields to modify the dimensions of the fitting component parts.\nDetail\nClick to display a detailed image of the fitting. The Image window displays a detailed description of the fitting geometry and the different parameters and variables that can be applied to the fitting.\nInclude Weld Geometry\nSelect the check box to include the weld geometry for a section fitting.\nNote:\nThe functionality is only available for welded fittings created from catalogue joints. The functionality is not available for welded fittings created from template joints because the welds must be included in the template.\nThe example displays a welded fitting created from a catalogue joint. The weld geometry displays in the 3D view.\nThe connection status of welded fittings can be inspected and modified using the Connection Review window. Refer to Review Connections for further information.\nSpecification\nSelect from the drop down list to display all the available groups of fitting component available for the section. Once a specification has been selected from the drop-down list, the Fitting Group and Fitting galleries are automatically populated with fitting group and fitting components available for selection.\nFitting Group\nSelect from the gallery to display all the available fitting components. Once a group has been selected, the Fitting gallery is automatically populated with the fitting components available for selection.\nFitting\nSelect a fitting component from the gallery. Once a fitting has been selected, the Design Parameters fields are automatically populated with default values.\nDesign Parameters\nInput values in the fields to modify the dimensions of the fitting component parts.\nDetail\nClick to display a detailed image of the fitting. The Image window displays a detailed description of the fitting geometry and the different parameters and variables that can be applied to the fitting.\n\nInclude Weld Geometry\nSelect the check box to include the weld geometry for a section fitting.\nThe example displays a welded fitting created from a catalogue joint. The weld geometry displays in the 3D view.\n\nThe connection status of welded fittings can be inspected and modified using the Connection Review window. Refer to Review Connections for further information.\nClick Apply to accept the fitting component settings.\nYou are prompted to Set P-line or <CTOP>\nClick to identify the P-line position of the fitting and press Enter.\nYou are then prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting. A fitting is created and displays in the 3D view, measured from the start of the selected P-line.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals, measured from the start of the selected P-line.\nThroughout the fitting creation process you can press ESC to cancel the command. Additional functionality is also available.\nAngle\nPress the down arrow key and select Angle to rotate the fitting.\nYou are prompted to Specify Angle <#deg>\nInput an angular value in the field and press Enter or click to identify the angle of the fitting.\nBasepoint\nPress the down arrow key and select Basepoint to identify a base point to position the fitting.\nYou are then prompted to Specify base point or\nInput a dimensional value in the field and press Enter or click to identify the basepoint from which the position of the fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals, measured from the basepoint.\nRepeat\nPress the down arrow key and select Repeat to create multiple fittings.\nYou are prompted to Specify Distance or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nThe prompt is repeated allowing you to create multiple fittings.\nInput F at the prompt and press Enter to end the command.\nStart\nPress the down arrow key and select Start to identify the start of the section as the base point from which the position of the fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nEnd\nPress the down arrow key and select End to identify the end of the section as the base point from which the position of the fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x-200mm;2x-100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nNote:\nNegative incremental values should be used to position fittings measured from the end of the section.\nBack\nPress the down arrow key and select Back to undo the last action.\nSingle\nPress the down arrow key and select Single to create a single fitting.\nYou are then prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nAngle\nPress the down arrow key and select Angle to rotate the fitting.\nYou are prompted to Specify Angle <#deg>\nInput an angular value in the field and press Enter or click to identify the angle of the fitting.\nBasepoint\nPress the down arrow key and select Basepoint to identify a base point to position the fitting.\nYou are then prompted to Specify base point or\nInput a dimensional value in the field and press Enter or click to identify the basepoint from which the position of the fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals, measured from the basepoint.\nRepeat\nPress the down arrow key and select Repeat to create multiple fittings.\nYou are prompted to Specify Distance or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nThe prompt is repeated allowing you to create multiple fittings.\nInput F at the prompt and press Enter to end the command.\nStart\nPress the down arrow key and select Start to identify the start of the section as the base point from which the position of the fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nEnd\nPress the down arrow key and select End to identify the end of the section as the base point from which the position of the fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x-200mm;2x-100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nBack\nPress the down arrow key and select Back to undo the last action.\nSingle\nPress the down arrow key and select Single to create a single fitting.\nYou are then prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new JLDATU, PLDATU and FIXING elements display in the Model Explorer.\n\nSpecification\nSelect from the drop down list to display all the available groups of fitting component available for the section. Once a specification has been selected from the drop-down list, the Fitting Group and Fitting galleries are automatically populated with fitting group and fitting components available for selection.\nFitting Group\nSelect from the gallery to display all the available fitting components. Once a group has been selected, the Fitting gallery is automatically populated with the fitting components available for selection.\nFitting\nSelect a fitting component from the gallery. Once a fitting has been selected, the Design Parameters fields are automatically populated with default values.\nDesign Parameters\nInput values in the fields to modify the dimensions of the fitting component parts.\nDetail\nClick to display a detailed image of the fitting. The Image window displays a detailed description of the fitting geometry and the different parameters and variables that can be applied to the fitting.\nInclude Weld Geometry\nSelect the check box to include the weld geometry for a section fitting.\nNote:\nThe functionality is only available for welded fittings created from catalogue joints. The functionality is not available for welded fittings created from template joints because the welds must be included in the template.\nThe example displays a welded fitting created from a catalogue joint. The weld geometry displays in the 3D view.\nThe connection status of welded fittings can be inspected and modified using the Connection Review window. Refer to Review Connections for further information.\nAngle\nPress the down arrow key and select Angle to rotate the fitting.\nYou are prompted to Specify Angle <#deg>\nInput an angular value in the field and press Enter or click to identify the angle of the fitting.\nBasepoint\nPress the down arrow key and select Basepoint to identify a base point to position the fitting.\nYou are then prompted to Specify base point or\nInput a dimensional value in the field and press Enter or click to identify the basepoint from which the position of the fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals, measured from the basepoint.\nRepeat\nPress the down arrow key and select Repeat to create multiple fittings.\nYou are prompted to Specify Distance or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nThe prompt is repeated allowing you to create multiple fittings.\nInput F at the prompt and press Enter to end the command.\nStart\nPress the down arrow key and select Start to identify the start of the section as the base point from which the position of the fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nEnd\nPress the down arrow key and select End to identify the end of the section as the base point from which the position of the fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x-200mm;2x-100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nNote:\nNegative incremental values should be used to position fittings measured from the end of the section.\nBack\nPress the down arrow key and select Back to undo the last action.\nSingle\nPress the down arrow key and select Single to create a single fitting.\nYou are then prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nFinish\nPress the down arrow key and select Finish to end the command.\nNote:\nThe functionality is only available for welded fittings created from catalogue joints. The functionality is not available for welded fittings created from template joints because the welds must be included in the template.\nNote:\nNegative incremental values should be used to position fittings measured from the end of the section.\n\n\n\nSection Connectivity\nReview Connections\nSection Connectivity\nSelect section\nSection Fitting\nSection Fitting\nSpecification\nFitting Group\nFitting\nFitting Group\nFitting\nFitting\nDesign Parameters\nDesign Parameters\nDetail\nImage\nInclude Weld Geometry\nNote:\nConnection Review\nReview Connections\nApply\nSet P-line or <CTOP>\nEnter\nSpecify Distance or\nEnter\nEnter\n5x200mm;2x100mm\nESC\nAngle\nAngle\nSpecify Angle <#deg>\nEnter\nBasepoint\nBasepoint\nSpecify base point or\nEnter\nSpecify Distance or\nEnter\n5x200mm;2x100mm\nRepeat\nRepeat\nSpecify Distance or <Finish>\nEnter\nF\nEnter\nStart\nStart\nSpecify Distance or\nEnter\n5x200mm;2x100mm\nEnd\nEnd\nSpecify Distance or\nEnter\n5x-200mm;2x-100mm\nNote:\nBack\nBack\nSingle\nSingle\nSpecify Distance or\nEnter\nFinish\nFinish"}
{"Headers": "Copy Section Fitting", "Content": "Copies a fitting to the same section or copies multiple fittings to multiple sections.\n\n\n"}
{"Headers": "Copy Fitting to Same Section", "Content": "Copies a fitting to a specified position on the same section and P-line as the original fitting.\nYou are prompted to Select section(s)\nClick to identify the section that contains the fitting to be copied and press Enter. The fittings are highlighted in the 3D view, each fitting displays as a fitting pin.\n\nYou are then prompted to Select fitting or\nClick to identify the fitting to be copied.\nYou are then prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting. The fitting is copied to the new position, measured from the start of the P-line that the original fitting is on.\nAlternatively, input a value in the field to define a number of copied fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals, measured from the start of the P-line that the original fitting is on.\nThroughout the copy fitting process you can press ESC to cancel the command. Additional functionality is also available.\nCopy to sections\nPress the down arrow key and select Copy to sections to copy multiple fittings on the same section to multiple sections. Refer to Copy Multiple Fittings to Multiple Sections for further information.\nAngle\nPress the down arrow key and select Angle to rotate the fitting.\nYou are prompted to Specify Angle <#deg>\nInput an angular value in the field and press Enter or click to identify the angle of the fitting.\nBasepoint\nPress the down arrow key and select Basepoint to identify a base point to position the copied fitting.\nYou are then prompted to Specify base point or\nInput a dimensional value in the field and press Enter or click to identify the basepoint from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals, measured from the basepoint.\nOffset\nPress the down arrow key and select Offset to identify an offset from the existing fitting to position the copied fitting.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals, measured from the existing fitting.\nRepeat\nPress the down arrow key and select Repeat to create multiple fittings.\nYou are prompted to Specify Distance or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nThe prompt is repeated allowing you to create multiple fittings.\nInput F at the prompt and press Enter to end the command.\nStart\nPress the down arrow key and select Start to identify the start of the section as the base point from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nEnd\nPress the down arrow key and select End to identify the end of the section as the base point from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x-200mm;2x-100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nNote:\nNegative incremental values should be used to position fittings measured from the end of the section.\nFitting\nPress the down arrow key and select Fitting to identify an existing fitting as the base point from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nBack\nPress the down arrow key and select Back to undo the last action.\nSingle\nPress the down arrow key and select Single to create a single fitting.\nYou are then prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nCopy to sections\nPress the down arrow key and select Copy to sections to copy multiple fittings on the same section to multiple sections. Refer to Copy Multiple Fittings to Multiple Sections for further information.\nAngle\nPress the down arrow key and select Angle to rotate the fitting.\nYou are prompted to Specify Angle <#deg>\nInput an angular value in the field and press Enter or click to identify the angle of the fitting.\nBasepoint\nPress the down arrow key and select Basepoint to identify a base point to position the copied fitting.\nYou are then prompted to Specify base point or\nInput a dimensional value in the field and press Enter or click to identify the basepoint from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals, measured from the basepoint.\nOffset\nPress the down arrow key and select Offset to identify an offset from the existing fitting to position the copied fitting.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals, measured from the existing fitting.\nRepeat\nPress the down arrow key and select Repeat to create multiple fittings.\nYou are prompted to Specify Distance or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nThe prompt is repeated allowing you to create multiple fittings.\nInput F at the prompt and press Enter to end the command.\nStart\nPress the down arrow key and select Start to identify the start of the section as the base point from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nEnd\nPress the down arrow key and select End to identify the end of the section as the base point from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x-200mm;2x-100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nFitting\nPress the down arrow key and select Fitting to identify an existing fitting as the base point from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nBack\nPress the down arrow key and select Back to undo the last action.\nSingle\nPress the down arrow key and select Single to create a single fitting.\nYou are then prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new JLDATU, PLDATU and FIXING elements display in the Model Explorer.\n\nCopy to sections\nPress the down arrow key and select Copy to sections to copy multiple fittings on the same section to multiple sections. Refer to Copy Multiple Fittings to Multiple Sections for further information.\nAngle\nPress the down arrow key and select Angle to rotate the fitting.\nYou are prompted to Specify Angle <#deg>\nInput an angular value in the field and press Enter or click to identify the angle of the fitting.\nBasepoint\nPress the down arrow key and select Basepoint to identify a base point to position the copied fitting.\nYou are then prompted to Specify base point or\nInput a dimensional value in the field and press Enter or click to identify the basepoint from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals, measured from the basepoint.\nOffset\nPress the down arrow key and select Offset to identify an offset from the existing fitting to position the copied fitting.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals, measured from the existing fitting.\nRepeat\nPress the down arrow key and select Repeat to create multiple fittings.\nYou are prompted to Specify Distance or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nThe prompt is repeated allowing you to create multiple fittings.\nInput F at the prompt and press Enter to end the command.\nStart\nPress the down arrow key and select Start to identify the start of the section as the base point from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nEnd\nPress the down arrow key and select End to identify the end of the section as the base point from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x-200mm;2x-100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nNote:\nNegative incremental values should be used to position fittings measured from the end of the section.\nFitting\nPress the down arrow key and select Fitting to identify an existing fitting as the base point from which the position of the copied fitting is measured.\nYou are prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nAlternatively, input a value in the field to define a number of fittings and the distance between each fitting and press Enter to end the command. For example, input 5x200mm;2x100mm to create five fittings at 200mm intervals, followed by two fittings at 100mm intervals.\nBack\nPress the down arrow key and select Back to undo the last action.\nSingle\nPress the down arrow key and select Single to create a single fitting.\nYou are then prompted to Specify Distance or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nFinish\nPress the down arrow key and select Finish to end the command.\nNote:\nThe prompt does not display if the section element is already selected.\nNote:\nNegative incremental values should be used to position fittings measured from the end of the section.\n\n\n\nCopy Multiple Fittings to Multiple Sections\nSelect section(s)\nNote:\nEnter\nSelect fitting or\nSpecify Distance or\nEnter\n5x200mm;2x100mm\nESC\nCopy to sections\nCopy to sections\nCopy Multiple Fittings to Multiple Sections\nAngle\nAngle\nSpecify Angle <#deg>\nEnter\nBasepoint\nBasepoint\nSpecify base point or\nEnter\nSpecify Distance or\nEnter\n5x200mm;2x100mm\nOffset\nOffset\nSpecify Distance or\nEnter\n5x200mm;2x100mm\nRepeat\nRepeat\nSpecify Distance or <Finish>\nEnter\nF\nStart\nStart\nSpecify Distance or\nEnter\n5x200mm;2x100mm\nEnd\nEnd\nSpecify Distance or\nEnter\n5x-200mm;2x-100mm\nNote:\nFitting\nFitting\nSpecify Distance or\nEnter\n5x200mm;2x100mm\nBack\nBack\nSingle\nSingle\nSpecify Distance or\nEnter\nFinish\nFinish"}
{"Headers": "Copy Multiple Fittings to Multiple Sections", "Content": "Copies multiple fittings on the same section to multiple sections.\nYou are prompted to Select section(s)\nClick to identify the section that contains the fittings to be copied and press Enter. The fittings are highlighted in the 3D view, each fitting displays as a fitting pin.\n\nYou are then prompted to Select fitting or\nInput C at the prompt and press Enter.\nYou are then prompted to Select fittings\nClick to identify the fittings to be copied and press Enter.\nYou are then prompted to Select sections\nClick to identify the sections to copy the fittings to and press Enter.\nThe fittings are copied to identified sections, the position of the copied fittings is identical to the position of the original fittings.\n\nThe new JLDATU, PLDATU and FIXING elements display in the Model Explorer.\n\nNote:\nThe prompt does not display if the section element is already selected.\n\n\n\nSelect section(s)\nNote:\nEnter\nSelect fitting or\nC\nEnter\nSelect fittings\nEnter\nSelect sections\nEnter"}
{"Headers": "Modify Sections", "Content": "Once a section has been completed, it may be necessary to modify the section, fixings or joints. A section can be modified, the type, geometry and position of fixings and joints can be modified and bracing gaps defined.\nEditor is a mode of operation in Model which allows you to reposition selected items using the mouse pointer. Refer to Non-Routed Item for further information.\n\n\n\nNon-Routed Item\nModel\nNon-Routed Item"}
{"Headers": "Modify Section Properties", "Content": "The properties of selected sections can be modified using the Properties window. Refer to Properties for further information.\n\nThe properties of the GENSEC element can be modified to change a number of settings.\nGeneral\nName\nInput a value in the field to modify the name. By default, all member names are modified to reflect the new name.\nDescription\nInput a value in the field to modify the description.\nFunction\nInput a value in the field to modify the function.\nPurpose\nInput a value in the field to modify the purpose.\nLock\nInput a value in the field to modify the lock status.\nInput True in the field to lock the section for modification.\nInput False in the field to unlock the section for modification.\nSpecification\nClassification\nInput a value in the field or select a classification from the drop-down list to modify the section classification.\nReference\nDisplays the specification reference of the section which is populated from the Spec, Type and Profile fields.\nSpec\nInput a value in the field or select a specification from the drop-down list to modify the section specification.\nWhen a specification is selected, the type and profile drop-down lists are populated with the components that were used when the specification was most recently selected.\nType\nInput a value in the field or select a type from the drop-down list to modify the section type.\nThe type drop-down list is populated with the section types that are associated with the currently selected specification.\nProfile\nInput a value in the field or select a profile from the drop-down list to modify the section profile.\nThe profile drop-down list is populated with the section types that are associated with the currently selected specification.\nMaterial\nInput a value in the field or select a material from the drop-down list to modify the section material.\nThe material ref drop-down list is populated with the materials that are associated with the currently selected specification.\nJustification\nInput a value in the field or select a justification from the drop-down list to modify the section justification.\nFor example, select CTOP from the drop-down list to trim the element to the centre top Pline.\nThe justification drop-down list is populated with the justification options that are associated with the currently selected profile.\nMemberline\nInput a value in the field or select a justification from the drop-down list to modify the justification leaving the member line.\nParameters\nClick to view the design parameters of the section.\nPreferred specification\nAllows you to view the preferred specification status of the currently selected section.\nTrue indicates that the section is a preferred specification.\nFalse indicates that the section is not a preferred specification.\nPositional\nBeta angle\nInput an angular value in the field or select a rotation angle from the drop-down list to modify the beta angle of the section.\nPosition\nInput dimensional values in the field to explicitly modify the position of the section. The section is repositioned.\nOrientation\nInput values in the field to modify the direction of the X, Y and Z axis.\nStart position\nInput dimensional values in the field to explicitly modify the start point of the section.\nEnd position\nInput dimensional values in the field to explicitly modify the end point of the section.\nMirror\nInput a value in the field to modify the mirror status.\nInput True in the field to define the section as mirrored from the position in which it was created.\nInput False in the field to define section as not mirrored.\nDesign\nStart joint\nDisplays the name of the owning section to which the start joint is attached.\nEnd joint\nDisplays the name of the owning section to which the end joint is attached.\nStart cut\nDisplays the direction of the start cut.\nEnd cut\nDisplays the direction of the end cut.\nGeneral\n\nName\nInput a value in the field to modify the name. By default, all member names are modified to reflect the new name.\nDescription\nInput a value in the field to modify the description.\nFunction\nInput a value in the field to modify the function.\nPurpose\nInput a value in the field to modify the purpose.\nLock\nInput a value in the field to modify the lock status.\nInput True in the field to lock the section for modification.\nInput False in the field to unlock the section for modification.\nSpecification\n\nClassification\nInput a value in the field or select a classification from the drop-down list to modify the section classification.\nReference\nDisplays the specification reference of the section which is populated from the Spec, Type and Profile fields.\nSpec\nInput a value in the field or select a specification from the drop-down list to modify the section specification.\nWhen a specification is selected, the type and profile drop-down lists are populated with the components that were used when the specification was most recently selected.\nType\nInput a value in the field or select a type from the drop-down list to modify the section type.\nThe type drop-down list is populated with the section types that are associated with the currently selected specification.\nProfile\nInput a value in the field or select a profile from the drop-down list to modify the section profile.\nThe profile drop-down list is populated with the section types that are associated with the currently selected specification.\nMaterial\nInput a value in the field or select a material from the drop-down list to modify the section material.\nThe material ref drop-down list is populated with the materials that are associated with the currently selected specification.\nJustification\nInput a value in the field or select a justification from the drop-down list to modify the section justification.\nFor example, select CTOP from the drop-down list to trim the element to the centre top Pline.\nThe justification drop-down list is populated with the justification options that are associated with the currently selected profile.\nMemberline\nInput a value in the field or select a justification from the drop-down list to modify the justification leaving the member line.\nParameters\nClick to view the design parameters of the section.\nPreferred specification\nAllows you to view the preferred specification status of the currently selected section.\nTrue indicates that the section is a preferred specification.\nFalse indicates that the section is not a preferred specification.\nPositional\n\nBeta angle\nInput an angular value in the field or select a rotation angle from the drop-down list to modify the beta angle of the section.\nPosition\nInput dimensional values in the field to explicitly modify the position of the section. The section is repositioned.\nOrientation\nInput values in the field to modify the direction of the X, Y and Z axis.\nStart position\nInput dimensional values in the field to explicitly modify the start point of the section.\nEnd position\nInput dimensional values in the field to explicitly modify the end point of the section.\nMirror\nInput a value in the field to modify the mirror status.\nInput True in the field to define the section as mirrored from the position in which it was created.\nInput False in the field to define section as not mirrored.\nDesign\n\nStart joint\nDisplays the name of the owning section to which the start joint is attached.\nEnd joint\nDisplays the name of the owning section to which the end joint is attached.\nStart cut\nDisplays the direction of the start cut.\nEnd cut\nDisplays the direction of the end cut.\n\nGeneral\nName\nInput a value in the field to modify the name. By default, all member names are modified to reflect the new name.\nDescription\nInput a value in the field to modify the description.\nFunction\nInput a value in the field to modify the function.\nPurpose\nInput a value in the field to modify the purpose.\nLock\nInput a value in the field to modify the lock status.\nInput True in the field to lock the section for modification.\nInput False in the field to unlock the section for modification.\nSpecification\nClassification\nInput a value in the field or select a classification from the drop-down list to modify the section classification.\nReference\nDisplays the specification reference of the section which is populated from the Spec, Type and Profile fields.\nSpec\nInput a value in the field or select a specification from the drop-down list to modify the section specification.\nWhen a specification is selected, the type and profile drop-down lists are populated with the components that were used when the specification was most recently selected.\nType\nInput a value in the field or select a type from the drop-down list to modify the section type.\nThe type drop-down list is populated with the section types that are associated with the currently selected specification.\nProfile\nInput a value in the field or select a profile from the drop-down list to modify the section profile.\nThe profile drop-down list is populated with the section types that are associated with the currently selected specification.\nMaterial\nInput a value in the field or select a material from the drop-down list to modify the section material.\nThe material ref drop-down list is populated with the materials that are associated with the currently selected specification.\nJustification\nInput a value in the field or select a justification from the drop-down list to modify the section justification.\nFor example, select CTOP from the drop-down list to trim the element to the centre top Pline.\nThe justification drop-down list is populated with the justification options that are associated with the currently selected profile.\nMemberline\nInput a value in the field or select a justification from the drop-down list to modify the justification leaving the member line.\nParameters\nClick to view the design parameters of the section.\nPreferred specification\nAllows you to view the preferred specification status of the currently selected section.\nTrue indicates that the section is a preferred specification.\nFalse indicates that the section is not a preferred specification.\nPositional\nBeta angle\nInput an angular value in the field or select a rotation angle from the drop-down list to modify the beta angle of the section.\nPosition\nInput dimensional values in the field to explicitly modify the position of the section. The section is repositioned.\nOrientation\nInput values in the field to modify the direction of the X, Y and Z axis.\nStart position\nInput dimensional values in the field to explicitly modify the start point of the section.\nEnd position\nInput dimensional values in the field to explicitly modify the end point of the section.\nMirror\nInput a value in the field to modify the mirror status.\nInput True in the field to define the section as mirrored from the position in which it was created.\nInput False in the field to define section as not mirrored.\nDesign\nStart joint\nDisplays the name of the owning section to which the start joint is attached.\nEnd joint\nDisplays the name of the owning section to which the end joint is attached.\nStart cut\nDisplays the direction of the start cut.\nEnd cut\nDisplays the direction of the end cut.\n\n\n\nProperties\nProperties\nProperties\nGeneral\nName\nDescription\nFunction\nPurpose\nLock\nTrue\nFalse\nSpecification\nClassification\nReference\nSpec\nType\nProfile\nSpec\nType\nProfile\nMaterial\nJustification\nMemberline\nParameters\nPreferred specification\nTrue\nFalse\nPositional\nBeta angle\nPosition\nOrientation\nStart position\nEnd position\nMirror\nTrue\nFalse\nDesign\nStart joint\nEnd joint\nStart cut\nEnd cut"}
{"Headers": "Modify Joint", "Content": "Modifies the catalogue specification associated with each joint. For example, a web cleat or a welded joint.\nModify Joint Specification\nModifies the joint specification.\nYou are prompted to Select section(s)\nClick to identify the sections that contain joints to be modified and press Enter. The joints are highlighted in the 3D view, each joint displays as a joint pin.\n\nThe connection type and selection status of each joint is indicated by the joint pin colour.\nRefer to Dominant and Subordinate Connections for further information.\nYou are then prompted to Select joints\nClick to identify the joints to be modified and press Enter to display the Modify Joint window.\n\nThe Modify Joint window allows you to associate a catalogue specification with the currently selected joints and modify the dimensions of the joint component parts.\nSelection\nClick to remove all joints from the current selection.\nThe number of currently selected joints displays adjacent to the icon.\nSpecification\nSelect from the drop-down list to display all the available groups of joint component covered by a specification. Once a specification has been selected from the drop-down list, the Joint Group and Joint galleries are automatically populated with joint group and joint components available for selection.\nNote:\nAn automatically selected joint is displayed as Unset in the specification and can be modified to a standard joint using the drop-down list.\nJoint Group\nSelect from the gallery to display all the available joint components. Once a group has been selected, the Joint gallery is automatically populated with the joint components available for selection.\nJoint\nSelect a joint component from the gallery. Once a joint has been selected, the Design Parameters fields are automatically populated with default values.\nDesign Parameters\nInput values in the fields to modify the dimensions of the joint component parts.\nInclude Weld Geometry\nSelect the check box to include the weld geometry for a welded joint.\nNote:\nThe functionality is only available for welded joints created from catalogue joints. The functionality is not available for welded joints created from template joints because the welds must be included in the template.\nThe example displays a welded joint created from a catalogue joint. The weld geometry displays in the 3D view.\nThe connection status of welded joints can be inspected and modified using the Connection Review window. Refer to Review Connections for further information.\nDetail\nClick to display a detailed image of the joint. The image window displays a detailed description of the joint geometry and the different parameters and variables that can be applied to the joint.\n\nSelection\nClick to remove all joints from the current selection.\nThe number of currently selected joints displays adjacent to the icon.\n\nSpecification\nSelect from the drop-down list to display all the available groups of joint component covered by a specification. Once a specification has been selected from the drop-down list, the Joint Group and Joint galleries are automatically populated with joint group and joint components available for selection.\n\nJoint Group\nSelect from the gallery to display all the available joint components. Once a group has been selected, the Joint gallery is automatically populated with the joint components available for selection.\n\nJoint\nSelect a joint component from the gallery. Once a joint has been selected, the Design Parameters fields are automatically populated with default values.\n\nDesign Parameters\nInput values in the fields to modify the dimensions of the joint component parts.\n\nInclude Weld Geometry\nSelect the check box to include the weld geometry for a welded joint.\nThe example displays a welded joint created from a catalogue joint. The weld geometry displays in the 3D view.\n\nThe connection status of welded joints can be inspected and modified using the Connection Review window. Refer to Review Connections for further information.\n\nDetail\nClick to display a detailed image of the joint. The image window displays a detailed description of the joint geometry and the different parameters and variables that can be applied to the joint.\n\nClick Apply to accept the joint component settings.\nYou are prompted to Set specification\nPress Enter to associate the joint specification with the currently selected joints.\nSelection\nClick to remove all joints from the current selection.\nThe number of currently selected joints displays adjacent to the icon.\nSpecification\nSelect from the drop-down list to display all the available groups of joint component covered by a specification. Once a specification has been selected from the drop-down list, the Joint Group and Joint galleries are automatically populated with joint group and joint components available for selection.\nNote:\nAn automatically selected joint is displayed as Unset in the specification and can be modified to a standard joint using the drop-down list.\nJoint Group\nSelect from the gallery to display all the available joint components. Once a group has been selected, the Joint gallery is automatically populated with the joint components available for selection.\nJoint\nSelect a joint component from the gallery. Once a joint has been selected, the Design Parameters fields are automatically populated with default values.\nDesign Parameters\nInput values in the fields to modify the dimensions of the joint component parts.\nInclude Weld Geometry\nSelect the check box to include the weld geometry for a welded joint.\nNote:\nThe functionality is only available for welded joints created from catalogue joints. The functionality is not available for welded joints created from template joints because the welds must be included in the template.\nThe example displays a welded joint created from a catalogue joint. The weld geometry displays in the 3D view.\nThe connection status of welded joints can be inspected and modified using the Connection Review window. Refer to Review Connections for further information.\nDetail\nClick to display a detailed image of the joint. The image window displays a detailed description of the joint geometry and the different parameters and variables that can be applied to the joint.\nCyan = Subordinate joint\nOrange = Dominant joint\nYellow = End datum joint\nRed = Selected joint (dominant, subordinate or end datum).\nCyan = Subordinate joint\nCyan = Subordinate joint\nOrange = Dominant joint\nOrange = Dominant joint\nYellow = End datum joint\nYellow = End datum joint\nRed = Selected joint (dominant, subordinate or end datum).\nRed = Selected joint (dominant, subordinate or end datum).\nNote:\nThe prompt does not display if the section elements are already selected.\nNote:\nAn automatically selected joint is displayed as Unset in the specification and can be modified to a standard joint using the drop-down list.\nNote:\nThe functionality is only available for welded joints created from catalogue joints. The functionality is not available for welded joints created from template joints because the welds must be included in the template.\n\n\n\nDominant and Subordinate Connections\nReview Connections\nModify Joint Specification\nSelect section(s)\nNote:\nEnter\nDominant and Subordinate Connections\nSelect joints\nEnter\nModify Joint\nModify Joint\nSelection\nSpecification\nJoint Group\nJoint\nNote:\nUnset\nJoint Group\nJoint\nJoint\nDesign Parameters\nDesign Parameters\nInclude Weld Geometry\nNote:\nConnection Review\nReview Connections\nDetail\nApply\nSet specification\nEnter"}
{"Headers": "Unset Joint Specification", "Content": "Clears the template and design parameters associated with selected joints.\nYou are prompted to Select owning section\nClick to identify the sections that contain joints to be modified and press Enter. The joints are highlighted in the 3D view, each joint displays as a joint pin.\n\nThe connection type and selection status of each joint is indicated by the joint pin colour.\nRefer to Dominant and Subordinate Connections for further information.\nYou are then prompted to Select joints\nClick to identify the joints to be modified and press Enter to clear the template and design parameters associated with selected joints\nCyan = Subordinate joint\nOrange = Dominant joint\nYellow = End datum joint\nRed = Selected joint (dominant, subordinate or end datum).\nCyan = Subordinate joint\nCyan = Subordinate joint\nOrange = Dominant joint\nOrange = Dominant joint\nYellow = End datum joint\nYellow = End datum joint\nRed = Selected joint (dominant, subordinate or end datum).\nRed = Selected joint (dominant, subordinate or end datum).\nNote:\nThe functionality is not available for merged joints.\n\n\n\nDominant and Subordinate Connections\nNote:\nSelect owning section\nEnter\nDominant and Subordinate Connections\nSelect joints\nEnter"}
{"Headers": "Modify Merged Joint", "Content": "Modifies the design parameters associated with a merged joint.\nYou are prompted to Select owning section\nClick to identify the section that contains the merged joint to be modified and press Enter. The merged joint is highlighted in the 3D view and is displayed as a merged joint pin.\n\nThe selection status of the merged joint is indicated by the merged joint pin colour.\nYou are then prompted to Select joints\nClick to identify the merged joint to be modified and press Enter to display the Merged Joint window.\n\nThe functionality of the Merged Joint window is explained. Refer to Create Merged Joint for further information.\nYellow = Not selected\nRed = Selected.\nYellow = Not selected\nYellow = Not selected\nRed = Selected.\nRed = Selected.\nNote:\nThe prompt does not display if the section element is already selected.\n\n\n\nCreate Merged Joint\nSelect owning section\nNote:\nEnter\nSelect joints\nEnter\nMerged Joint\nMerged Joint\nCreate Merged Joint"}
{"Headers": "Delete Merged Joint", "Content": "Deletes a merged joint. The joints are returned to their previous state prior to being merged.\nYou are prompted to Select owning section\nClick to identify the section that contains the merged joint to be deleted and press Enter. The merged joint is highlighted in the 3D view and is displayed as a merged joint pin.\n\nThe selection status of the merged joint is indicated by the merged joint pin colour.\nYou are then prompted to Select joints\nClick to identify the merged joint to be deleted and press Enter to delete the merged joint.\nYellow = Not selected\nRed = Selected.\nYellow = Not selected\nYellow = Not selected\nRed = Selected.\nRed = Selected.\nNote:\nThe prompt does not display if the section element is already selected.\n\n\n\nSelect owning section\nNote:\nEnter\nSelect joints\nEnter"}
{"Headers": "Modify Fitting", "Content": "Modifies the catalogue specification associated with each fitting.\nModify Fitting Specification\nModifies the fitting specification.\nYou are prompted to Select section(s)\nClick to identify the sections that contain fittings to be modified and press Enter. The fittings are highlighted in the 3D view, each fitting displays as a fitting pin.\n\nThe selection status of the each fitting is indicated by the fitting pin colour.\nYou are then prompted to Select fittings\nClick to identify the fittings to be modified and press Enter to display the Section Fitting window.\n\nThe functionality of the Section Fitting window is explained, with the exception of the Selection part of the window. Refer to Create Section Fitting for further information.\nSelection\nClick to remove all fittings from the current selection.\nThe number of currently selected fittings displays adjacent to the icon.\n\nSelection\nClick to remove all fittings from the current selection.\nThe number of currently selected fittings displays adjacent to the icon.\nClick Apply to accept the fitting component settings.\nYou are prompted to Set specification\nPress Enter to associate the fitting specification with the currently selected fittings.\nSelection\nClick to remove all fittings from the current selection.\nThe number of currently selected fittings displays adjacent to the icon.\nPink = Not selected\nRed = Selected.\nPink = Not selected\nPink = Not selected\nRed = Selected.\nRed = Selected.\nNote:\nThe prompt does not display if the section elements are already selected.\n\n\n\nCreate Section Fitting\nModify Fitting Specification\nSelect section(s)\nNote:\nEnter\nSelect fittings\nEnter\nSection Fitting\nSection Fitting\nSelection\nCreate Section Fitting\nSelection\nApply\nSet specification\nEnter"}
{"Headers": "Navigator PowerWheel\u2122", "Content": "Use the navigation functionality to navigate through the selected section element hierarchy.\n\n\n\n"}
{"Headers": "Extend Section", "Content": "Lengthens or shortens straight or curved sections using either:\nFunctionality is also available to extend or trim the connected end of a GENSEC. Refer to Non-Routed Item for further information.\nThe extended section endpoints can be cut to align with the plane or extended without cutting.\nYou are prompted to Select section end(s) to extend or\nClick to identify a section end to extend.\nYou are then prompted to Select section end(s) to extend or <Next>\nThe prompt is repeated, allowing you to identify multiple section ends to extend.\nInput N at the prompt and press Enter to specify the extension plane.\nYou are then prompted to Select first plane point or <Panel>\nInput values in the dimension fields and press Enter or click to identify the first point of the plane.\nYou are then prompted to Select second plane point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the second point of the plane.\nYou are then prompted to Select third plane point or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the third point of the plane.\nThe section ends are extended to the intersection with the plane.\nThroughout the extend process you can press ESC to cancel the command. Additional functionality is also available.\nPerpendicular to section\nPress the down arrow key and select Perpendicular to section to extend a section end to align with the plane without cutting the endpoint.\nNormal to plane\nPress the down arrow key and select Normal to plane to cut the endpoint of the extended section to align with the plane.\nNext\nPress the down arrow key and select Next to proceed to the next extend process.\nExtend by value\nPress the down arrow key and select Extend by value to extend a section end using an extension value, measured from the current position of the section end.\nYou are prompted to Specify extension or\nInput a dimensional value in the field an press Enter to define the section extension value.\nOverall length\nPress the down arrow key and select Overall length to extend a section end using an overall section length value.\nYou are prompted to Specify overall length or\nInput a dimensional value in the field an press Enter to define the section length value.\nPanel\nPress the down arrow key and select Panel to extend a section end to a panel intersection.\nYou are prompted to Select Panel to extend to or\nClick to identify an intersecting panel to define the extension point.\nLcs\nPress the down arrow key and select Lcs to extend a section end to align with the origin of the local coordinate system.\nSurface\nPress the down arrow key and select Surface to extend a section end to align with a plane derived from a picked surface.\nYou are prompted to Select Surface to extend to or\nOffset\nPress the down arrow key and select Offset to create a plane that is offset from the picked points.\nYou are prompted to Specify offset\nInput a dimensional value in the field an press Enter to define the offset value.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nPerpendicular to section\nPress the down arrow key and select Perpendicular to section to extend a section end to align with the plane without cutting the endpoint.\nNormal to plane\nPress the down arrow key and select Normal to plane to cut the endpoint of the extended section to align with the plane.\nNext\nPress the down arrow key and select Next to proceed to the next extend process.\nExtend by value\nPress the down arrow key and select Extend by value to extend a section end using an extension value, measured from the current position of the section end.\nYou are prompted to Specify extension or\nInput a dimensional value in the field an press Enter to define the section extension value.\nOverall length\nPress the down arrow key and select Overall length to extend a section end using an overall section length value.\nYou are prompted to Specify overall length or\nInput a dimensional value in the field an press Enter to define the section length value.\nPanel\nPress the down arrow key and select Panel to extend a section end to a panel intersection.\nYou are prompted to Select Panel to extend to or\nClick to identify an intersecting panel to define the extension point.\nLcs\nPress the down arrow key and select Lcs to extend a section end to align with the origin of the local coordinate system.\nSurface\nPress the down arrow key and select Surface to extend a section end to align with a plane derived from a picked surface.\nYou are prompted to Select Surface to extend to or\nOffset\nPress the down arrow key and select Offset to create a plane that is offset from the picked points.\nYou are prompted to Specify offset\nInput a dimensional value in the field an press Enter to define the offset value.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nPerpendicular to section\nPress the down arrow key and select Perpendicular to section to extend a section end to align with the plane without cutting the endpoint.\nNormal to plane\nPress the down arrow key and select Normal to plane to cut the endpoint of the extended section to align with the plane.\nNext\nPress the down arrow key and select Next to proceed to the next extend process.\nExtend by value\nPress the down arrow key and select Extend by value to extend a section end using an extension value, measured from the current position of the section end.\nYou are prompted to Specify extension or\nInput a dimensional value in the field an press Enter to define the section extension value.\nOverall length\nPress the down arrow key and select Overall length to extend a section end using an overall section length value.\nYou are prompted to Specify overall length or\nInput a dimensional value in the field an press Enter to define the section length value.\nPanel\nPress the down arrow key and select Panel to extend a section end to a panel intersection.\nYou are prompted to Select Panel to extend to or\nClick to identify an intersecting panel to define the extension point.\nLcs\nPress the down arrow key and select Lcs to extend a section end to align with the origin of the local coordinate system.\nSurface\nPress the down arrow key and select Surface to extend a section end to align with a plane derived from a picked surface.\nYou are prompted to Select Surface to extend to or\nOffset\nPress the down arrow key and select Offset to create a plane that is offset from the picked points.\nYou are prompted to Specify offset\nInput a dimensional value in the field an press Enter to define the offset value.\nFinish\nPress the down arrow key and select Finish to end the command.\na plane created from a maximum of three identified points\na panel intersection\na section extension value\nan overall section length value\na local coordinate system intersection\na plane derived from a picked surface\nan offset vale\na plane created from a maximum of three identified points\na plane created from a maximum of three identified points\na panel intersection\na panel intersection\na section extension value\na section extension value\nan overall section length value\nan overall section length value\na local coordinate system intersection\na local coordinate system intersection\na plane derived from a picked surface\na plane derived from a picked surface\nan offset vale\nan offset vale\n\n\n\nNon-Routed Item\nNon-Routed Item\nSelect section end(s) to extend or\nSelect section end(s) to extend or <Next>\nN\nEnter\nSelect first plane point or <Panel>\nEnter\nSelect second plane point or <Finish>\nEnter\nSelect third plane point or <Finish>\nEnter\nESC\nPerpendicular to section\nPerpendicular to section\nNormal to plane\nNormal to plane\nNext\nNext\nExtend by value\nExtend by value\nSpecify extension or\nEnter\nOverall length\nOverall length\nSpecify overall length or\nEnter\nPanel\nPanel\nSelect Panel to extend to or\nLcs\nLcs\nSurface\nSurface\nSelect Surface to extend to or\nOffset\nOffset\nSpecify offset\nEnter\nFinish\nFinish"}
{"Headers": "Miter Sections", "Content": "Miters a straight section end to another straight section end.\nTo successfully miter two section ends, points which concern relative position, orientation and other attributes of the two sections must be considered:\nYou are prompted to Select first section end to miter or\nClick to identify the first straight section.\nYou are then prompted to Select second section end to miter or\nClick to identify the second straight section. The two sections are extended or shortened to create the mitered ends. The Start Cut and End Cut properties of each section is modified to indicate the cut angle of the miterd end.\nThroughout the mitering process you can press ESC to cancel the command. Additional functionality is also available.\nMiter only\nPress the down arrow key and select miter only to miter the section ends. The connectivity status of the mitered ends, is not changed.\nFinish\nPress the down arrow key and select Finish to end the command.\nMiter and connect\nPress the down arrow key and select miter and connect to miter the section ends. The two mitered ends are connected.\nRepeat\nPress the down arrow key and select Repeat to create multiple mitered section ends.\nYou are prompted to Select first section end to miter or <Finish>\nClick to identify the first straight section.\nYou are then prompted to Select first section end to miter or <Finish>\nThe process is repeated allowing you to miter multiple section ends.\nInput F at the prompt and press Enter to end the command.\n\nMiter only\nPress the down arrow key and select miter only to miter the section ends. The connectivity status of the mitered ends, is not changed.\nFinish\nPress the down arrow key and select Finish to end the command.\nMiter and connect\nPress the down arrow key and select miter and connect to miter the section ends. The two mitered ends are connected.\nRepeat\nPress the down arrow key and select Repeat to create multiple mitered section ends.\nYou are prompted to Select first section end to miter or <Finish>\nClick to identify the first straight section.\nYou are then prompted to Select first section end to miter or <Finish>\nThe process is repeated allowing you to miter multiple section ends.\nInput F at the prompt and press Enter to end the command.\n\nIf the section ends cannot be mitered, a Warning message displays on the status bar.\nMiter only\nPress the down arrow key and select miter only to miter the section ends. The connectivity status of the mitered ends, is not changed.\nFinish\nPress the down arrow key and select Finish to end the command.\nMiter and connect\nPress the down arrow key and select miter and connect to miter the section ends. The two mitered ends are connected.\nRepeat\nPress the down arrow key and select Repeat to create multiple mitered section ends.\nYou are prompted to Select first section end to miter or <Finish>\nClick to identify the first straight section.\nYou are then prompted to Select first section end to miter or <Finish>\nThe process is repeated allowing you to miter multiple section ends.\nInput F at the prompt and press Enter to end the command.\nThe sections must not be parallel.\nThe sections do not have to be the same Gtype but unacceptable results may occur.\nThe sections do not have to be the same Beta Angle but unacceptable results may occur.\nThe sections do not have to be co-planar but must be within the Offset depth tolerance.\nThe Y direction of the sections do not have to be the same but unacceptable results may occur.\nThe sections must not be parallel.\nThe sections must not be parallel.\nThe sections do not have to be the same Gtype but unacceptable results may occur.\nThe sections do not have to be the same Gtype but unacceptable results may occur.\nThe sections do not have to be the same Beta Angle but unacceptable results may occur.\nThe sections do not have to be the same Beta Angle but unacceptable results may occur.\nThe sections do not have to be co-planar but must be within the Offset depth tolerance.\nThe sections do not have to be co-planar but must be within the Offset depth tolerance.\nThe Y direction of the sections do not have to be the same but unacceptable results may occur.\nThe Y direction of the sections do not have to be the same but unacceptable results may occur.\n\n\n\nSelect first section end to miter or\nSelect second section end to miter or\nStart Cut\nEnd Cut\nESC\nMiter only\nFinish\nFinish\nMiter and connect\nRepeat\nRepeat\nSelect first section end to miter or <Finish>\nSelect first section end to miter or <Finish>\nF"}
{"Headers": "Perpendicular Section End Cut", "Content": "Modifies the section end cut to be perpendicular to the angle of the section.\nYou are prompted to Select section end or\n\nClick to identify the section end. The section end cut is modified to be perpendicular to the angle of the section.\nThe process is repeated allowing you to modify multiple section end cuts.\nPress the down arrow key and select Finish to end the command.\nThroughout the process you can press ESC to cancel the command.\n\n\n\n\nSelect section end or\nFinish\nESC"}
{"Headers": "Fillet Section", "Content": "Merges two non parallel, coplanar sections and applies a curved fillet, regardless of specification, justification or beta angle.\nIf the sections are parallel, or not coplanar, a Warning message displays on the status bar.\nThe properties of the merged sections and fillet are inherited from the first picked section.\nYou are prompted to Pick first Section end to fillet\nClick to identify the first section end to apply a fillet to.\nYou are then prompted to Pick second Section end to fillet\nClick to identify the second section end to apply a fillet to.\nYou are then prompted to Fillet radius (R = #) or <Finish>\nInput a dimensional value in the field and press Enter to define the radius of the fillet. The default is 1000mm.\nInput F at the prompt and press Enter to end the command. The sections are merged and a fillet is created.\nThroughout the fillet process you can press ESC to cancel the command. Additional functionality is also available.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nFinish\nPress the down arrow key and select Finish to end the command.\n\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nPick first Section end to fillet\nPick second Section end to fillet\nFillet radius (R = #) or <Finish>\nEnter\nF\nEnter\nESC\nFinish"}
{"Headers": "Split Section, Panel or Bounded Plate", "Content": "Splits a section, panel or bounded plate into multiple sections/panels/bounded plates.\nIt is often easier to 3D model an overall structure and then split it into smaller components for fabrication or assembly purposes.\nNote:\nIf the automatic weld creation functionality is enabled, a connection is made between the split panels or split bounded plates and welds are created.\n\n\n\nNote:"}
{"Headers": "Split Section or Panel at Intersection", "Content": "Splits sections or panels at a section/panel intersection.\nYou are prompted to Select element(s) to split\nClick to identify a section or panel to split.\nYou are then prompted to Select element(s) to split or <Next>\nThe prompt is repeated, allowing you to identify multiple sections or panels to split.\nInput N at the prompt and press Enter to specify the split points.\nYou are then prompted to Select element(s) to split with or <Plane>\nClick to identify an intersecting section or panel to define a split point.\nYou are then prompted to Select element(s) to split with or <Next>\nThe prompt is repeated, allowing you to identify multiple sections or panels and define additional split points.\nInput N at the prompt and press Enter to end the command. The sections and panels are split at the intersecting split points.\nThroughout the split process you can press ESC to cancel the command. Additional functionality is also available.\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a section or panel using a plane. Refer to Split Section or Panel using a Plane for further information.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a section or panel using a plane. Refer to Split Section or Panel using a Plane for further information.\n\nThe new GENSEC and PANE elements display in the Model Explorer.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a section or panel using a plane. Refer to Split Section or Panel using a Plane for further information.\nNote:\nThe prompt does not display if the section or panel element is already selected.\nNote:\nThe prompt does not display if the section or panel element is already selected.\n\n\n\nSplit Section or Panel using a Plane\nSelect element(s) to split\nNote:\nSelect element(s) to split or <Next>\nNote:\nN\nEnter\nSelect element(s) to split with or <Plane>\nSelect element(s) to split with or <Next>\nN\nEnter\nESC\nNext\nNext\nPlane\n\nSplit Section or Panel using a Plane"}
{"Headers": "Split Section or Panel using a Plane", "Content": "Splits sections or panels using a plane created from a maximum of three identified points.\nYou are prompted to Select element(s) to split\nClick to identify a section or panel to split.\nYou are then prompted to Select element(s) to split or <Next>\nThe prompt is repeated, allowing you to identify multiple sections or panels to split.\nInput N at the prompt and press Enter to specify the split plane.\nYou are then prompted to Select element(s) to split with or <Plane>\nInput P at the prompt and press Enter to specify the plane.\nYou are then prompted to Select first point or\nInput values in the dimension fields and press Enter or click to identify the first point of the plane.\nYou are then prompted to Select second point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the second point of the plane.\nYou are then prompted to Select third point or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the third point of the plane.\nThe sections and panels are split at the intersection with the plane.\nThroughout the split process you can press ESC to cancel the command. Additional functionality is also available.\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a section or panel using a plane.\nLCS\nPress the down arrow key and select LCS to split a section or panel at an alignment point with the origin of the local coordinate system.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a section or panel using a plane.\nLCS\nPress the down arrow key and select LCS to split a section or panel at an alignment point with the origin of the local coordinate system.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new GENSEC and PANE elements display in the Model Explorer.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a section or panel using a plane.\nLCS\nPress the down arrow key and select LCS to split a section or panel at an alignment point with the origin of the local coordinate system.\nFinish\nPress the down arrow key and select Finish to end the command.\nNote:\nThe prompt does not display if the section or panel element is already selected.\nNote:\nThe prompt does not display if the section or panel element is already selected.\n\n\n\nSelect element(s) to split\nNote\n:\nSelect element(s) to split or <Next>\nNote\n:\nN\nEnter\nSelect element(s) to split with or <Plane>\nP\nEnter\nSelect first point or\nEnter\nSelect second point or <Finish>\nEnter\nSelect third point or <Finish>\nEnter\nESC\nNext\nNext\nPlane\nPlane\nLCS\nLCS\nFinish\nFinish"}
{"Headers": "Split Bounded Plate at Section Intersection", "Content": "Splits bounded plates at section intersections.\nYou are prompted to Select element(s) to split\nClick to identify a bounded plate to split.\nYou are then prompted to Select element(s) to split or <Next>\nThe prompt is repeated, allowing you to identify multiple bounded plates to split.\nInput N at the prompt and press Enter to specify the split points.\nYou are then prompted to Select element(s) to split with (Gap width: #mm) or <Plane>\nClick to identify an intersecting section to define a split point.\nYou are then prompted to Select element(s) to split with (Gap width: #mm) or <Next>\nThe prompt is repeated, allowing you to identify multiple sections and define additional split points.\nInput N at the prompt and press Enter to end the command. The bounded plates are split at the intersecting split points.\nThroughout the split process you can press ESC to cancel the command. Additional functionality is also available.\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounded plate using a plane. Refer to Split Bounded Plate using a Plane for further information.\nGap\nPress the down arrow key and select Gap to create a gap between the split plates.\nYou are prompted to Specify gap width or <#mm>\nInput a dimensional value in the field and press Enter to define the gap. The default is 0.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounded plate using a plane. Refer to Split Bounded Plate using a Plane for further information.\nGap\nPress the down arrow key and select Gap to create a gap between the split plates.\nYou are prompted to Specify gap width or <#mm>\nInput a dimensional value in the field and press Enter to define the gap. The default is 0.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nThe new PANE, PLOO and STCSET elements display in the Model Explorer. The structural connections of each split bounded plate are updated. Refer to Split Bounded Plate Structural Connections for further information.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounded plate using a plane. Refer to Split Bounded Plate using a Plane for further information.\nGap\nPress the down arrow key and select Gap to create a gap between the split plates.\nYou are prompted to Specify gap width or <#mm>\nInput a dimensional value in the field and press Enter to define the gap. The default is 0.\nBack\nPress the down arrow key and select Back to undo the last action.\nNote:\nThe prompt does not display if the bounded plate element is already selected.\nNote:\nThe prompt does not display if the bounded element is already selected.\n\n\n\nSplit Bounded Plate using a Plane\nSplit Bounded Plate Structural Connections\nSelect element(s) to split\nNote:\nSelect element(s) to split or <Next>\nNote:\nN\nEnter\nSelect element(s) to split with (Gap width: #mm) or <Plane>\nSelect element(s) to split with (Gap width: #mm) or <Next>\nN\nEnter\nESC\nNext\nNext\nPlane\n\nSplit Bounded Plate using a Plane\nGap\nGap\nSpecify gap width or <#mm>\nEnter\nBack\nBack\nSplit Bounded Plate Structural Connections"}
{"Headers": "Split Bounded Plate using a Plane", "Content": "Splits bounded plates using a plane created from a maximum of three identified points.\nYou are prompted to Select element(s) to split\nClick to identify a bounded plate to split.\nYou are then prompted to Select element(s) to split or <Next>\nThe prompt is repeated, allowing you to identify multiple bounded plates to split.\nInput N at the prompt and press Enter to specify the split plane.\nYou are then prompted to Select element(s) to split with (Gap width: #mm) or <Plane>\nInput P at the prompt and press Enter to specify the plane.\nYou are then prompted to Select first point (Gap: #mm) or\nInput values in the dimension fields and press Enter or click to identify the first point of the plane.\nYou are then prompted to Select second point (Gap: #mm) or <Finish>\nInput values in the dimension fields and press Enter or click to identify the second point of the plane.\nYou are then prompted to Select third point (Gap: #mm) or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the third point of the plane.\nThe bounded plates are split at the intersection with the plane.\nThroughout the split process you can press ESC to cancel the command. Additional functionality is also available.\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounded plate using a plane.\nGap\nPress the down arrow key and select Gap to create a gap between the split plates.\nYou are prompted to Specify gap width or <#mm>\nInput a dimensional value in the field and press Enter to define the gap. The default is 0.\nLCS\nPress the down arrow key and select LCS to split a bounded plate at an alignment point with the origin of the local coordinate system.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounded plate using a plane.\nGap\nPress the down arrow key and select Gap to create a gap between the split plates.\nYou are prompted to Specify gap width or <#mm>\nInput a dimensional value in the field and press Enter to define the gap. The default is 0.\nLCS\nPress the down arrow key and select LCS to split a bounded plate at an alignment point with the origin of the local coordinate system.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new PANE, PLOO and STCSET elements display in the Model Explorer. Refer to Split Bounded Plate Structural Connections for further information.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounded plate using a plane.\nGap\nPress the down arrow key and select Gap to create a gap between the split plates.\nYou are prompted to Specify gap width or <#mm>\nInput a dimensional value in the field and press Enter to define the gap. The default is 0.\nLCS\nPress the down arrow key and select LCS to split a bounded plate at an alignment point with the origin of the local coordinate system.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nNote:\nThe prompt does not display if the bounded plate element is already selected.\nNote:\nThe prompt does not display if the bounded plate element is already selected.\n\n\n\nSplit Bounded Plate Structural Connections\nSelect element(s) to split\nNote:\nSelect element(s) to split or <Next>\nNote:\nN\nEnter\nSelect element(s) to split with (Gap width: #mm) or <Plane>\nP\nEnter\nSelect first point (Gap: #mm) or\nEnter\nSelect second point (Gap: #mm) or <Finish>\nEnter\nSelect third point (Gap: #mm) or <Finish>\nEnter\nESC\nNext\nNext\nPlane\nPlane\nGap\nGap\nSpecify gap width or <#mm>\nEnter\nLCS\nLCS\nBack\nBack\nFinish\nFinish\nSplit Bounded Plate Structural Connections"}
{"Headers": "Split Bounded Plate Structural Connections", "Content": "The example displays a rectangular bounded plate with four Structural Connections (STCONN) associated with each of the bounded plate edges. The defined split plane is also displayed.\n\nWhen the bounded plate is split, the structural connections of each split bounded plate is updated.\n\nA new structural connection (displayed in red in the example) is created on each split bounded plate to account for the created edges.\nMutual referencing is established between the structural connection vertices of the adjacent structural connections corresponding to the split geometry. For example:\nThe STCVER1 of STCONN2 on Split Bounded Plate 1 references the STCVER2 of STCONN4 on Split Bounded Plate 2 using the STCREF attribute.\nThe STCVER2 of STCONN4 on Split Bounded Plate 2 references the STCVER1 of STCONN2 on Split Bounded Plate 1 using the STCREF attribute.\nThe STCVER1 of STCONN2 on Split Bounded Plate 1 references the STCVER2 of STCONN4 on Split Bounded Plate 2 using the STCREF attribute.\nThe STCVER1 of STCONN2 on Split Bounded Plate 1 references the STCVER2 of STCONN4 on Split Bounded Plate 2 using the STCREF attribute.\nThe STCVER2 of STCONN4 on Split Bounded Plate 2 references the STCVER1 of STCONN2 on Split Bounded Plate 1 using the STCREF attribute.\nThe STCVER2 of STCONN4 on Split Bounded Plate 2 references the STCVER1 of STCONN2 on Split Bounded Plate 1 using the STCREF attribute.\n\n\n"}
{"Headers": "Split Bounded Plate Bounding Elements at Section Intersection", "Content": "Splits bounded plate bounding elements at section intersections.\nYou are prompted to Select element(s) to split\nClick to identify a bounding element to split.\nYou are then prompted to Select element(s) to split or <Next>\nThe prompt is repeated, allowing you to identify multiple bounding elements to split.\nInput N at the prompt and press Enter to specify the split points.\nYou are then prompted to Select element(s) to split with or <Plane>\nClick to identify an intersecting section to define a split point.\nYou are then prompted to Select element(s) to split with or <Next>\nThe prompt is repeated, allowing you to identify multiple sections and define additional split points.\nInput N at the prompt and press Enter to end the command. The bounding elements are split at the intersecting split points.\nThroughout the split process you can press ESC to cancel the command. Additional functionality is also available.\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounding element using a plane. Refer to Split Bounded Plate Bounding Elements using a Plane for further information.\nLCS\nPress the down arrow key and select LCS to split a bounding element at an alignment point with the origin of the local coordinate system.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounding element using a plane. Refer to Split Bounded Plate Bounding Elements using a Plane for further information.\nLCS\nPress the down arrow key and select LCS to split a bounding element at an alignment point with the origin of the local coordinate system.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nThe new GENSEC elements display in the Model Explorer. The structural connections of each split bounded plate are updated. Refer to Split Bounded Plate Bounding Element Structural Connections for further information.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounding element using a plane. Refer to Split Bounded Plate Bounding Elements using a Plane for further information.\nLCS\nPress the down arrow key and select LCS to split a bounding element at an alignment point with the origin of the local coordinate system.\nBack\nPress the down arrow key and select Back to undo the last action.\nNote:\nIf the bounded plate is selected as an element to split, it will be split as well as the bounding elements.\nNote:\nThe prompt does not display if the bounding element is already selected.\nNote:\nThe prompt does not display if the bounding element is already selected.\n\n\n\nSplit Bounded Plate Bounding Elements using a Plane\nSplit Bounded Plate Bounding Element Structural Connections\nNote:\nSelect element(s) to split\nNote:\nSelect element(s) to split or <Next>\nNote:\nN\nEnter\nSelect element(s) to split with or <Plane>\nSelect element(s) to split with or <Next>\nN\nEnter\nESC\nNext\nNext\nPlane\nPlane\nSplit Bounded Plate Bounding Elements using a Plane\nLCS\nLCS\nBack\nBack\nSplit Bounded Plate Bounding Element Structural Connections"}
{"Headers": "Split Bounded Plate Bounding Elements using a Plane", "Content": "Splits bounded plate bounding elements using a plane created from a maximum of three identified points.\nYou are prompted to Select element(s) to split\nClick to identify a bounding element to split.\nYou are then prompted to Select element(s) to split or <Next>\nThe prompt is repeated, allowing you to identify multiple bounding elements to split.\nInput N at the prompt and press Enter to specify the split plane.\nYou are then prompted to Select element(s) to split with or <Plane>\nInput P at the prompt and press Enter to specify the plane.\nYou are then prompted to Select first point or\nInput values in the dimension fields and press Enter or click to identify the first point of the plane.\nYou are then prompted to Select second point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the second point of the plane.\nYou are then prompted to Select third point or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the third point of the plane.\nThe bounding elements are split at the intersection with the plane.\nThroughout the split process you can press ESC to cancel the command. Additional functionality is also available.\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounding element using a plane.\nLCS\nPress the down arrow key and select LCS to split a bounding element at an alignment point with the origin of the local coordinate system.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounding element using a plane.\nLCS\nPress the down arrow key and select LCS to split a bounding element at an alignment point with the origin of the local coordinate system.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new GENSEC elements display in the Model Explorer. Refer to Split Bounded Plate Bounding Element Structural Connections for further information.\n\nNext\nPress the down arrow key and select Next to proceed to the next split process.\nPlane\nPress the down arrow key and select Plane to split a bounding element using a plane.\nLCS\nPress the down arrow key and select LCS to split a bounding element at an alignment point with the origin of the local coordinate system.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nNote:\nIf the bounded plate is selected as an element to split, it will be split as well as the bounding elements.\nNote:\nThe prompt does not display if the bounding element is already selected.\nNote:\nThe prompt does not display if the bounding element is already selected.\n\n\n\nSplit Bounded Plate Bounding Element Structural Connections\nNote:\nSelect element(s) to split\nNote:\nSelect element(s) to split or <Next>\nNote:\nN\nEnter\nSelect element(s) to split with or <Plane>\nP\nEnter\nSelect first point or\nEnter\nSelect second point or <Finish>\nEnter\nSelect third point or <Finish>\nEnter\nESC\nNext\nNext\nPlane\nPlane\nLCS\nLCS\nBack\nBack\nFinish\nFinish\nSplit Bounded Plate Bounding Element Structural Connections"}
{"Headers": "Split Bounded Plate Bounding Element Structural Connections", "Content": "The example displays four GENSEC bounding elements that are bound to a rectangular plate. Each GENSEC has a Structural Connection (STCONN) associated with the bounded plate edge. The defined split plane is also displayed.\n\nWhen the bounding element is split, a GENSEC is created with a connection to the bounded plate edge (STCONN5).\n\nRefer to Non-Routed Item, Bounded Plate Health Checker and Create Panel Welds for further information.\n\n\n\nNon-Routed Item\nBounded Plate Health Checker\nCreate Panel Welds\nNon-Routed Item\nBounded Plate Health Checker\nCreate Panel Welds"}
{"Headers": "Splice Sections", "Content": "Divides sections into smaller lengths using a splice.\n\n\n"}
{"Headers": "Splice Section at Panel Intersection", "Content": "Splices sections at a panel intersection.\nYou are prompted to Pick element(s) to splice\nClick to identify a section to splice.\nYou are then prompted to Pick element(s) to splice or <Next>\nThe prompt is repeated, allowing you to identify multiple sections to splice.\nInput N at the prompt and press Enter to specify the splice point.\nYou are then prompted to Pick panel to splice with or <Plane>\nClick to identify an intersecting panel to define a splice point.\nThe sections are spliced at the intersecting panel points.\nThroughout the splice process you can press ESC to cancel the command. Additional functionality is also available.\nNext\nPress the down arrow key and select Next to proceed to the next splice process.\nPlane\nPress the down arrow key and select Plane to splice a section using a plane. Refer to Splice Section using a Plane for further information.\n\nNext\nPress the down arrow key and select Next to proceed to the next splice process.\nPlane\nPress the down arrow key and select Plane to splice a section using a plane. Refer to Splice Section using a Plane for further information.\n\nThe new GENSEC elements display in the Model Explorer.\n\nNext\nPress the down arrow key and select Next to proceed to the next splice process.\nPlane\nPress the down arrow key and select Plane to splice a section using a plane. Refer to Splice Section using a Plane for further information.\nNote:\nThe prompt does not display if the section element is already selected.\nNote:\nThe prompt does not display if the section element is already selected.\n\n\n\nSplice Section using a Plane\nPick element(s) to splice\nNote:\nPick element(s) to splice or <Next>\nNote:\nN\nEnter\nPick panel to splice with or <Plane>\nESC\nNext\nNext\nPlane\nPlane\nSplice Section using a Plane"}
{"Headers": "Splice Section using a Plane", "Content": "Splices sections using a plane created from a maximum of three identified points.\nYou are prompted to Pick element(s) to splice\nClick to identify a section to splice.\nYou are then prompted to Pick element(s) to splice or <Next>\nThe prompt is repeated, allowing you to identify multiple sections to splice.\nInput N at the prompt and press Enter to specify the splice plane.\nYou are then prompted to Pick panel to splice with or <Plane>\nInput P at the prompt and press Enter to specify the plane.\nYou are then prompted to Pick first point or\nInput values in the dimension fields and press Enter or click to identify the first point of the plane.\nYou are then prompted to Pick second point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the second point of the plane.\nYou are then prompted to Pick third point or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the third point of the plane.\nThe sections are spliced at the intersection with the plane.\nThroughout the splice process you can press ESC to cancel the command. Additional functionality is also available.\nNext\nPress the down arrow key and select Next to proceed to the next splice process.\nPlane\nPress the down arrow key and select Plane to splice a section using a plane.\nLCS\nPress the down arrow key and select LCS to splice a section at an alignment point with the origin of the local coordinate system.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nNext\nPress the down arrow key and select Next to proceed to the next splice process.\nPlane\nPress the down arrow key and select Plane to splice a section using a plane.\nLCS\nPress the down arrow key and select LCS to splice a section at an alignment point with the origin of the local coordinate system.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new GENSEC elements display in the Model Explorer.\n\nNext\nPress the down arrow key and select Next to proceed to the next splice process.\nPlane\nPress the down arrow key and select Plane to splice a section using a plane.\nLCS\nPress the down arrow key and select LCS to splice a section at an alignment point with the origin of the local coordinate system.\nFinish\nPress the down arrow key and select Finish to end the command.\nNote:\nThe prompt does not display if the section element is already selected.\nNote:\nThe prompt does not display if the section element is already selected.\n\n\n\nPick element(s) to splice\nNote:\nPick element(s) to splice or <Next>\nNote:\nN\nEnter\nPick panel to splice with or <Plane>\nP\nEnter\nPick first point or\nEnter\nPick second point or <Finish>\nEnter\nPick third point or <Finish>\nEnter\nESC\nNext\nNext\nPlane\nPlane\nLCS\nLCS\nFinish\nFinish"}
{"Headers": "Merge Sections", "Content": "Merges two non parallel, colinear sections, regardless of specification, justification or beta angle.\nIf the sections are parallel, or not colinear, a Warning message displays on the status bar.\nThe properties of the merged sections are inherited from the first picked section.\nYou are prompted to Select first element to merge\nClick to identify the first section to merge.\nYou are then prompted to Select second section to merge\nClick to identify the second section to merge.\nThe sections are merged.\nThroughout the merge process you can press ESC to cancel the command.\n\n\n\n\nSelect first element to merge\nSelect second section to merge\nESC"}
{"Headers": "Bracing", "Content": "Creates a standard bracing configuration which can be highly advantageous during the design process. A bracing gap can be created to define the gap between the bracing connection and a reference element.\n\n\n"}
{"Headers": "Bracing Configurations", "Content": "Bracing configurations are created as GENSEC elements. Refer to Default Section Specification for further information. You can create bracing configurations with appropriate connections at the end of the bracing sections, between GENSEC elements.\nThe supported bracing configurations are:\nDiagonal Bracing\n\nKnee Bracing\n\nCross Bracing\n\nK Bracing\n\nDiamond Bracing\n\n\n\n\nDefault Section Specification\nDefault Section Specification\nDiagonal Bracing\nKnee Bracing\nCross Bracing\nK Bracing\nDiamond Bracing"}
{"Headers": "Bracing Gaps", "Content": "As part of the design process, once bracing configurations have been created the bracing gaps may require adjusting. The bracing gap distance is measured from the bracing connection to a reference element.\n\nYou are prompted to Select bracing element\nClick to identify a bracing element.\nYou are then prompted to Select bracing element or <Next>\nThe prompt is repeated, allowing you to identify multiple bracing elements in the bracing configuration.\nInput N at the prompt and press Enter to specify the bracing.\nYou are then prompted to Select gap reference 1/2 (Diagonal)\nClick to identify all bracing elements in the bracing configuration.\nYou are then prompted to Select gap reference 2/2 (Diagonal) or <Next>\nInput N at the prompt and press Enter to modify the bracing gap.\nYou are then prompted to Select gap to modify <Finish>\nClick a bracing gap identifier to modify a bracing gap.\nYou are then prompted to Specify the gap\nInput a dimensional value in the field and press Enter to set the bracing gap distance.\nYou are then prompted to Select gap to modify <Finish>\nYou can continue to identify bracing gap identifiers and modify individual bracing gaps as required.\nThe bracing gap identification and gap modification process is repeated, allowing you to define multiple bracing gaps.\nInput F at the prompt and press Enter to end the command.\nThroughout the bracing gap modification process you can press ESC to cancel the command. Additional functionality is also available.\nNext\nPress the down arrow key and select Next to proceed to the next bracing gap process.\nKnee bracing\nPress the down arrow key and select Knee bracing to define a Knee bracing configuration.\nDiagonal bracing\nPress the down arrow key and select Diagonal bracing to define a diagonal bracing configuration.\nK bracing\nPress the down arrow key and select K bracing to define a K bracing configuration.\nCross bracing\nPress the down arrow key and select Cross bracing to define a cross bracing configuration.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nNext\nPress the down arrow key and select Next to proceed to the next bracing gap process.\nKnee bracing\nPress the down arrow key and select Knee bracing to define a Knee bracing configuration.\nDiagonal bracing\nPress the down arrow key and select Diagonal bracing to define a diagonal bracing configuration.\nK bracing\nPress the down arrow key and select K bracing to define a K bracing configuration.\nCross bracing\nPress the down arrow key and select Cross bracing to define a cross bracing configuration.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nNext\nPress the down arrow key and select Next to proceed to the next bracing gap process.\nKnee bracing\nPress the down arrow key and select Knee bracing to define a Knee bracing configuration.\nDiagonal bracing\nPress the down arrow key and select Diagonal bracing to define a diagonal bracing configuration.\nK bracing\nPress the down arrow key and select K bracing to define a K bracing configuration.\nCross bracing\nPress the down arrow key and select Cross bracing to define a cross bracing configuration.\nFinish\nPress the down arrow key and select Finish to end the command.\nNote:\nThe prompt indicates the number of bracing elements identified, the number of bracing elements in the current bracing configuration and the bracing configuration type.\n\n\n\nSelect bracing element\nSelect bracing element or <Next>\nN\nEnter\nSelect gap reference 1/2 (Diagonal)\nNote:\nSelect gap reference 2/2 (Diagonal) or <Next>\nN\nEnter\nSelect gap to modify <Finish>\nSpecify the gap\nEnter\nSelect gap to modify <Finish>\nF\nEnter\nESC\nNext\nNext\nKnee bracing\nKnee bracing\nDiagonal bracing\nDiagonal bracing\nK bracing\nK bracing\nCross bracing\nCross bracing\nFinish\nFinish"}
{"Headers": "View Section Dimensions", "Content": "Displays section dimension tags for the currently selected section elements in the 3D view.\nRepeat the command to remove the dimension tags from the 3D view.\n\nIf the currently selected element is not a section or a panel, a user message displays indicating that the currently selected element cannot be dimensioned.\n\n\n\n"}
{"Headers": "Plates Settings", "Content": "Plates allows you to add a floor plate and panels to a structure that already exists.\nFunctionality is available to add planar material to a 3D model in any orientation. Throughout this text, the term panel is used for such items in all descriptions, regardless of whether the element represents a horizontal floor plate, a vertical wall panel, a sloping roof panel, or any similar planar item.\nBefore a panel can be designed, various settings must be defined to determine, for example, the default panel specification.\nBefore a panel can be designed, various settings must be defined to determine, for example, the default panel specification.\nBefore a panel can be designed, various settings must be defined to determine, for example, the default panel specification.\n\n\n\nPlates"}
{"Headers": "Default Panel Specification", "Content": "Sets the default specification for the creation of panels. The default specification field values can also be applied to existing panels.\nThe following default panel components can be defined:\n\nA series of drop-down lists allows you to define the default panel specification.\nClass\nInput a value in the field or select the default panel classification from the drop-down list to be used for the creation of panels.\nDefault Material\nInput a value in the field or select the default material from the drop-down list to be used for the creation of panels.\nThe materials drop-down list is populated with the materials that are associated with the currently selected specification.\nDefault Justification\nInput a value in the field or select the default justification from the drop-down list to be used for the creation of panels.\nSpecification\nInput a value in the field or select the default specification from the drop-down list to be used for the creation of panels.\nPanel Thickness\nInput a value in the field or select the default thickness from the drop-down list to be used for the creation of panels.\nThe panel thickness drop-down list is populated with the thicknesses that are associated with the currently selected specification.\nDrawing Edge Defaults\nAllows you to define the default drawing edge defaults for panel elements. Refer to Drawing Edge Defaults for further information.\nClass\nInput a value in the field or select the default panel classification from the drop-down list to be used for the creation of panels.\nDefault Material\nInput a value in the field or select the default material from the drop-down list to be used for the creation of panels.\nThe materials drop-down list is populated with the materials that are associated with the currently selected specification.\nDefault Justification\nInput a value in the field or select the default justification from the drop-down list to be used for the creation of panels.\nSpecification\nInput a value in the field or select the default specification from the drop-down list to be used for the creation of panels.\nPanel Thickness\nInput a value in the field or select the default thickness from the drop-down list to be used for the creation of panels.\nThe panel thickness drop-down list is populated with the thicknesses that are associated with the currently selected specification.\nDrawing Edge Defaults\nAllows you to define the default drawing edge defaults for panel elements. Refer to Drawing Edge Defaults for further information.\n\nClass\nInput a value in the field or select the default panel classification from the drop-down list to be used for the creation of panels.\nDefault Material\nInput a value in the field or select the default material from the drop-down list to be used for the creation of panels.\nThe materials drop-down list is populated with the materials that are associated with the currently selected specification.\nDefault Justification\nInput a value in the field or select the default justification from the drop-down list to be used for the creation of panels.\nSpecification\nInput a value in the field or select the default specification from the drop-down list to be used for the creation of panels.\nPanel Thickness\nInput a value in the field or select the default thickness from the drop-down list to be used for the creation of panels.\nThe panel thickness drop-down list is populated with the thicknesses that are associated with the currently selected specification.\nDrawing Edge Defaults\nAllows you to define the default drawing edge defaults for panel elements. Refer to Drawing Edge Defaults for further information.\nPanel classification\nDefault material\nDefault justification\nSpecification\nPanel thickness\nDrawing edge defaults\nPanel classification\nPanel classification\nDefault material\nDefault material\nDefault justification\nDefault justification\nSpecification\nSpecification\nPanel thickness\nPanel thickness\nDrawing edge defaults\nDrawing edge defaults\n\n\n\nDrawing Edge Defaults\nClass\nDefault Material\nDefault Justification\nSpecification\nPanel Thickness\nDrawing Edge Defaults\nDrawing Edge Defaults"}
{"Headers": "Apply Defaults to Existing Panels", "Content": "Applies the values in the default panel specification fields to pre-selected panels.\nThe values from the Class, Default material, Default justification, Specification and Panel thickness fields are applied.\nDefaults values can only be applied to PANE or BPANEL elements.\nIf a selected panel is locked or claimed by another user, the default panel specification values cannot be applied.\n\n\n"}
{"Headers": "Drawing Edge Defaults", "Content": "Modifies the default drawing edge display for panel elements.\n\nThe list of available Elements displays each associated element type and the current default edge display setting.\nThe Common Surface Edges part of the Drawing Edge Defaults window allows you to modify the default edge display setting for the currently selected element.\nAlways Shown\nSelect the option button to always display common surface edges.\nNot Shown Between Members\nSelect the option button to omit the display of common surface edges between member elements.\nNot Shown Between Members and Peers\nSelect the option button to omit the display of common surface edges between member elements and peer elements.\nAlways Shown\nSelect the option button to always display common surface edges.\nNot Shown Between Members\nSelect the option button to omit the display of common surface edges between member elements.\nNot Shown Between Members and Peers\nSelect the option button to omit the display of common surface edges between member elements and peer elements.\n\nAlways Shown\nSelect the option button to always display common surface edges.\nNot Shown Between Members\nSelect the option button to omit the display of common surface edges between member elements.\nNot Shown Between Members and Peers\nSelect the option button to omit the display of common surface edges between member elements and peer elements.\n\n\n\nCommon Surface Edges\nDrawing Edge Defaults\nAlways Shown\nNot Shown Between Members\nNot Shown Between Members and Peers"}
{"Headers": "Create Panels", "Content": "Creates a Panel (PANE) element which can be used to represent any sheet material used to clad a structural model.\nWith a similar principle to that for representing a Section (which is an extruded 2D catalogue Profile), a Panel is represented by extruding a user-defined 2D shape. Its geometry is defined by two types of data:\n\nEach Panel Vertex can have an optional Fillet Radius setting which represents a circular arc which curves towards (positive radius) or away from (negative radius) the vertex position, as shown:\n\nThe default radius of zero denotes a point.\nBounded Plate connections are represented using Structural Connection Set (STCSET), Structural Connection (STCONN) and Structural Connection Vertex (STCVER) elements.\n\nPANE\nPANE elements can be owned by FRMW or SBFR elements. By default a PANE element is created for each panel. PANE elements can own PLOO elements and STCSET elements.\nPLOO\nPLOO elements can be owned by PANE elements. The PLOO defines the height (thickness) of the panel and can own PAVE elements.\nPAVE\nPAVE elements can be owned by PLOO elements. By default, a PAVE element is created for each vertex of the panel.\nSTCSET\nSTCSET elements can be owned by PANE elements. The STCSET contains a collection of structural connections. By default, a STCSET element is created for each collection of structural connections. STCSET elements can own STCONN elements.\nSTCONN\nSTCONN elements can be owned by STCSET elements. The STCONN represents a connection between a structural element, (for example, a bounded plate) and a structural section. By default, a STCONN element is created for each connection between a structural element and a structural section. STCONN elements can own STCVER elements.\nSTCVER\nSTCVER elements can be owned by STCONN elements. The STCVER contains structural connection information.\nThe panel\u2019s planar area is defined by a Panel Loop (PLOO) element, which is itself defined by a linked set of Panel Vertex (PAVE) elements, each of which has a specific position in the panel\u2019s 2D coordinate system. Each panel Edge is defined by a line that joins adjacent vertices.\nThe panel thickness is defined by setting the Height (HEIG) attribute of the Panel Loop, the distance through which the 2D Panel Loop is extruded to form the 3D panel.\nThe panel\u2019s planar area is defined by a Panel Loop (PLOO) element, which is itself defined by a linked set of Panel Vertex (PAVE) elements, each of which has a specific position in the panel\u2019s 2D coordinate system. Each panel Edge is defined by a line that joins adjacent vertices.\nThe panel\u2019s planar area is defined by a Panel Loop (PLOO) element, which is itself defined by a linked set of Panel Vertex (PAVE) elements, each of which has a specific position in the panel\u2019s 2D coordinate system. Each panel Edge is defined by a line that joins adjacent vertices.\nThe panel thickness is defined by setting the Height (HEIG) attribute of the Panel Loop, the distance through which the 2D Panel Loop is extruded to form the 3D panel.\nThe panel thickness is defined by setting the Height (HEIG) attribute of the Panel Loop, the distance through which the 2D Panel Loop is extruded to form the 3D panel.\nNote:\nThe justification of a panel that results may be dependent upon the clockwise/anticlockwise direction of creation for the panel.\n\n\n\nNote:\nPANE\nPLOO\nPAVE\nSTCSET\nSTCONN\nSTCVER"}
{"Headers": "Create Rectangle Panel with Two Specified Points", "Content": "Creates a rectangle panel with two specified points.\nYou are prompted to First corner (Thk: #mm, Just: #, fillet: #mm) or\nInput values in the dimension fields and press Enter or click to identify the first corner position.\nYou are then prompted to Second corner (Thk: #mm, Just: #, fillet: #mm) or\nInput values in the dimension fields and press Enter or click to identify the second corner position. A rectangle panel is created and displays in the 3D view.\nThroughout the panel creation process you can press ESC to cancel the command. Additional functionality is also available.\nFillet\nPress the down arrow key and select Fillet to create a panel with a specified fillet.\nYou are prompted to Fillet or <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nThickness\nPress the down arrow key and select Thickness to create a panel with a specified thickness.\nYou are prompted to Panel thickness or <#>\nInput a dimensional value in the field and press Enter to set the thickness of the panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nFillet\nPress the down arrow key and select Fillet to create a panel with a specified fillet.\nYou are prompted to Fillet or <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nThickness\nPress the down arrow key and select Thickness to create a panel with a specified thickness.\nYou are prompted to Panel thickness or <#>\nInput a dimensional value in the field and press Enter to set the thickness of the panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nThe new PANE element displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nFillet\nPress the down arrow key and select Fillet to create a panel with a specified fillet.\nYou are prompted to Fillet or <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nThickness\nPress the down arrow key and select Thickness to create a panel with a specified thickness.\nYou are prompted to Panel thickness or <#>\nInput a dimensional value in the field and press Enter to set the thickness of the panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\nBack\nPress the down arrow key and select Back to undo the last action.\n\n\n\nNon-Routed Item\nFirst corner (Thk: #mm, Just: #, fillet: #mm) or\nEnter\nSecond corner (Thk: #mm, Just: #, fillet: #mm) or\nEnter\nESC\nFillet\nFillet\nFillet or <#>\nEnter\nThickness\nThickness\nPanel thickness or <#>\nEnter\nJustification\nJustification\nEnter\nTop\nTop\nBottom\nBottom\nCentre\nCentre\nBack\nBack\nNon-Routed Item"}
{"Headers": "Create Multiple Point Panel", "Content": "Creates a multiple point panel.\nYou are prompted to First point (Thk: #mm, Just: #, fillet: #mm, Plane: Working Plane) or\nInput values in the dimension fields and press Enter or click to identify the first point position.\nYou are then prompted to Next point (Thk: #mm, Just: #, fillet: #mm) or\nInput values in the dimension fields and press Enter or click to identify the next point position.\nYou are then prompted to Next point (Thk: #mm, Just: #, fillet: #mm) or <Finish>\nThe prompt is repeated, allowing you to create multiple panel points.\nInput F at the prompt and press Enter to end the command. A multiple point panel is created and displays in the 3D view.\nThroughout the panel creation process you can press ESC to cancel the command. Additional functionality is also available.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nFillet\nPress the down arrow key and select Fillet to create a panel with a specified fillet.\nYou are prompted to Fillet (Thk: #mm, Just: #) <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nManual Plane\nPress the down arrow key and select Manual Plane to create a panel on a plane defined by the first three selected panel points.\nFor example, a sloped panel can be created by picking a panel point on a different elevation without the need to change to local coordinate system mode.\nThe selected plane is used for all subsequent multiple point panels in the current session until changed.\nWorking Plane\nPress the down arrow key and select Working Plane to create a panel on the working plane.\nThe selected plane is used for all subsequent multiple point panels in the current session until changed.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\nArc\nPress the down arrow key and select Arc to create a 3 points, Radius or Centre curved panel edge.\nThickness\nPress the down arrow key and select Thickness to define the thickness of the panel.\nYou are prompted to Panel thickness <#>\nInput a dimensional value in the field and press Enter to set the thickness of the panel.\nRadius\nPress the down arrow key and select Radius to create a panel edge with a specified radius.\nYou are prompted to Radius <#>\nInput a dimensional value in the field and press Enter to set the radius of the panel edge.\nCentre\nPress the down arrow key and select Centre to create a curved panel edge with a defined centre point.\nYou are prompted to Centre point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the curve centre point position.\nYou are then prompted to Arc radius or\nInput a dimensional value in the field and press Enter to set the radii of the curve.\nYou are then prompted to End point (Thk: #mm, Just: #) or <Finish>\nInput values in the dimension fields and press Enter or click to identify the curve end point position.\nStraight\nPress the down arrow key and select Straight to create a straight panel edge.\nYou are prompted to Next point (Thk: #mm, Just: #, fillet #mm) or <Finish>\nInput values in the dimension fields and press Enter or click to identify the next straight point position.\n3 points\nPress the down arrow key and select 3 points to create a curved panel edge with 3 points.\nYou are prompted to Middle point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the curve middle point position.\nYou are then prompted to End point (Thk: #mm, Just: #) or <Finish>\nInput values in the dimension fields and press Enter or click to identify the curve end point position.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nFillet\nPress the down arrow key and select Fillet to create a panel with a specified fillet.\nYou are prompted to Fillet (Thk: #mm, Just: #) <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nManual Plane\nPress the down arrow key and select Manual Plane to create a panel on a plane defined by the first three selected panel points.\nFor example, a sloped panel can be created by picking a panel point on a different elevation without the need to change to local coordinate system mode.\nThe selected plane is used for all subsequent multiple point panels in the current session until changed.\nWorking Plane\nPress the down arrow key and select Working Plane to create a panel on the working plane.\nThe selected plane is used for all subsequent multiple point panels in the current session until changed.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\nArc\nPress the down arrow key and select Arc to create a 3 points, Radius or Centre curved panel edge.\nThickness\nPress the down arrow key and select Thickness to define the thickness of the panel.\nYou are prompted to Panel thickness <#>\nInput a dimensional value in the field and press Enter to set the thickness of the panel.\nRadius\nPress the down arrow key and select Radius to create a panel edge with a specified radius.\nYou are prompted to Radius <#>\nInput a dimensional value in the field and press Enter to set the radius of the panel edge.\nCentre\nPress the down arrow key and select Centre to create a curved panel edge with a defined centre point.\nYou are prompted to Centre point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the curve centre point position.\nYou are then prompted to Arc radius or\nInput a dimensional value in the field and press Enter to set the radii of the curve.\nYou are then prompted to End point (Thk: #mm, Just: #) or <Finish>\nInput values in the dimension fields and press Enter or click to identify the curve end point position.\nStraight\nPress the down arrow key and select Straight to create a straight panel edge.\nYou are prompted to Next point (Thk: #mm, Just: #, fillet #mm) or <Finish>\nInput values in the dimension fields and press Enter or click to identify the next straight point position.\n3 points\nPress the down arrow key and select 3 points to create a curved panel edge with 3 points.\nYou are prompted to Middle point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the curve middle point position.\nYou are then prompted to End point (Thk: #mm, Just: #) or <Finish>\nInput values in the dimension fields and press Enter or click to identify the curve end point position.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new PANE element displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nFillet\nPress the down arrow key and select Fillet to create a panel with a specified fillet.\nYou are prompted to Fillet (Thk: #mm, Just: #) <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nManual Plane\nPress the down arrow key and select Manual Plane to create a panel on a plane defined by the first three selected panel points.\nFor example, a sloped panel can be created by picking a panel point on a different elevation without the need to change to local coordinate system mode.\nThe selected plane is used for all subsequent multiple point panels in the current session until changed.\nWorking Plane\nPress the down arrow key and select Working Plane to create a panel on the working plane.\nThe selected plane is used for all subsequent multiple point panels in the current session until changed.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\nArc\nPress the down arrow key and select Arc to create a 3 points, Radius or Centre curved panel edge.\nThickness\nPress the down arrow key and select Thickness to define the thickness of the panel.\nYou are prompted to Panel thickness <#>\nInput a dimensional value in the field and press Enter to set the thickness of the panel.\nRadius\nPress the down arrow key and select Radius to create a panel edge with a specified radius.\nYou are prompted to Radius <#>\nInput a dimensional value in the field and press Enter to set the radius of the panel edge.\nCentre\nPress the down arrow key and select Centre to create a curved panel edge with a defined centre point.\nYou are prompted to Centre point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the curve centre point position.\nYou are then prompted to Arc radius or\nInput a dimensional value in the field and press Enter to set the radii of the curve.\nYou are then prompted to End point (Thk: #mm, Just: #) or <Finish>\nInput values in the dimension fields and press Enter or click to identify the curve end point position.\nStraight\nPress the down arrow key and select Straight to create a straight panel edge.\nYou are prompted to Next point (Thk: #mm, Just: #, fillet #mm) or <Finish>\nInput values in the dimension fields and press Enter or click to identify the next straight point position.\n3 points\nPress the down arrow key and select 3 points to create a curved panel edge with 3 points.\nYou are prompted to Middle point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the curve middle point position.\nYou are then prompted to End point (Thk: #mm, Just: #) or <Finish>\nInput values in the dimension fields and press Enter or click to identify the curve end point position.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nNon-Routed Item\nFirst point (Thk: #mm, Just: #, fillet: #mm, Plane: Working Plane) or\nEnter\nNext point (Thk: #mm, Just: #, fillet: #mm) or\nEnter\nNext point (Thk: #mm, Just: #, fillet: #mm) or <Finish>\nF\nEnter\nESC\nJustification\nJustification\nEnter\nFillet\nFillet\nFillet (Thk: #mm, Just: #) <#>\nEnter\nManual Plane\nManual Plane\nWorking Plane\nWorking Plane\nTop\nTop\nBottom\nBottom\nCentre\nCentre\nArc\nArc\n3 points\nRadius\nCentre\nThickness\nThickness\nPanel thickness <#>\nEnter\nRadius\nRadius\nRadius <#>\nEnter\nCentre\nCentre\nCentre point (Thk: #mm, Just: #) or\nEnter\nArc radius or\nEnter\nEnd point (Thk: #mm, Just: #) or <Finish>\nEnter\nStraight\nStraight\nNext point (Thk: #mm, Just: #, fillet #mm) or <Finish>\nEnter\n3 points\n3 points\nMiddle point (Thk: #mm, Just: #) or\nEnter\nEnd point (Thk: #mm, Just: #) or <Finish>\nEnter\nBack\nBack\nFinish\nFinish\nNon-Routed Item"}
{"Headers": "Create Bounded Plate", "Content": "Creates multiple bounded plates using a specified surface point as a reference plane.\nYou are prompted to Select top surface of section\nClick to identify the top surface of the section to be used as the reference plane for the created bounded plates.\nYou are then prompted to Select bounding elements\nDrag a rectangular fence around the items to be selected, only sections and panels parallel to the reference plane are selected. Alternatively, click to select the initial bounding element then press Shift and click to select additional bounding elements. Press Enter to identify the bounding elements.\n\nYou are then prompted to Select sections and/or panels for notches\nDrag a rectangular fence around the items to be selected, only sections that intersect with the reference plane and panels parallel to the reference plane are selected. Alternatively, click to select the initial notching element then press Shift and click to select additional notching elements. Press Enter to identify the notching elements.\n\nYou are then prompted to Select boundary alignment <Inside>\nInput I at the prompt and press Enter to create bounding plates with inside alignment.\nYou are then prompted to Specify edge offset (include notches, Profile cut) or <#mm>\nInput a dimensional value in the field and press Enter to set the edge offset.\nYou are then prompted to Confirm plate properties <Thk: #mm, Just: #>\nThe default plate properties are populated using the default panel specification. Refer to Default Panel Specification for further information\nPress Enter to set the plate properties.\nMultiple bounded plates are created and display in the 3D view.\nThroughout the bounded plate creation process you can press ESC to cancel the command. Additional functionality is also available.\nInside\nPress the down arrow key and select Inside to create bounding plates with inside alignment. The created plates are aligned with the inside edge of the bounding elements.\nCentre\nPress the down arrow key and select Centre to create bounding plates with centre alignment. The created plates are aligned with the centre of the bounding elements.\nYou are prompted to Specify gap between adjacent plates (include notches, Profile cut) or <#mm>\nInput a dimensional value in the field and press Enter to set the gap between adjacent plates.\nOutside\nPress the down arrow key and select Outside to create bounding plates with outside alignment. The created plates are aligned with the outside edge of the bounding elements. Bounding plates with adjacent edges are automatically detected and aligned to the centre to avoid an overlap.\nYou are prompted to Specify gap between adjacent plates (include notches, Profile cut) or <#mm>\nInput a dimensional value in the field and press Enter to set the gap between adjacent plates.\nExclude notches\nPress the down arrow key and select Exclude notches to create bounding plates with notches, any associated offset value is excluded.\nOutline cut\nPress the down arrow key and select Outline cut to create bounding plates with notches that align to the outline of the notched sections.\nBack\nPress the down arrow key and select Back to undo the last action.\nInclude notches\nPress the down arrow key and select Include notches to create bounding plates with notches, any associated offset value is included.\nProfile cut\nPress the down arrow key and select Profile cut to create bounding plates with notches that align to the profile of the notched sections.\nThickness\nPress the down arrow key and select Thickness to define the thickness of the bounding plate.\nYou are prompted to Panel thickness <#>\nInput a dimensional value in the field and press Enter to set the thickness of the bounded plate.\nJustification\nPress the down arrow key and select Justification to define the justification position of the bounded plates.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nTop\nPress the down arrow key and select Top to create bounded plates with top justification.\nBottom\nPress the down arrow key and select Bottom to create bounded plates with bottom justification.\nCentre\nPress the down arrow key and select Centre to create bounded plates with centre justification.\n\nInside\nPress the down arrow key and select Inside to create bounding plates with inside alignment. The created plates are aligned with the inside edge of the bounding elements.\n\nCentre\nPress the down arrow key and select Centre to create bounding plates with centre alignment. The created plates are aligned with the centre of the bounding elements.\n\nYou are prompted to Specify gap between adjacent plates (include notches, Profile cut) or <#mm>\nInput a dimensional value in the field and press Enter to set the gap between adjacent plates.\nOutside\nPress the down arrow key and select Outside to create bounding plates with outside alignment. The created plates are aligned with the outside edge of the bounding elements. Bounding plates with adjacent edges are automatically detected and aligned to the centre to avoid an overlap.\n\nYou are prompted to Specify gap between adjacent plates (include notches, Profile cut) or <#mm>\nInput a dimensional value in the field and press Enter to set the gap between adjacent plates.\nExclude notches\nPress the down arrow key and select Exclude notches to create bounding plates with notches, any associated offset value is excluded.\n\nOutline cut\nPress the down arrow key and select Outline cut to create bounding plates with notches that align to the outline of the notched sections.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nInclude notches\nPress the down arrow key and select Include notches to create bounding plates with notches, any associated offset value is included.\n\nProfile cut\nPress the down arrow key and select Profile cut to create bounding plates with notches that align to the profile of the notched sections.\n\nThickness\nPress the down arrow key and select Thickness to define the thickness of the bounding plate.\nYou are prompted to Panel thickness <#>\nInput a dimensional value in the field and press Enter to set the thickness of the bounded plate.\nJustification\nPress the down arrow key and select Justification to define the justification position of the bounded plates.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nTop\nPress the down arrow key and select Top to create bounded plates with top justification.\nBottom\nPress the down arrow key and select Bottom to create bounded plates with bottom justification.\nCentre\nPress the down arrow key and select Centre to create bounded plates with centre justification.\n\nThe new PANE elements display in the Model Explorer.\n\nInside\nPress the down arrow key and select Inside to create bounding plates with inside alignment. The created plates are aligned with the inside edge of the bounding elements.\nCentre\nPress the down arrow key and select Centre to create bounding plates with centre alignment. The created plates are aligned with the centre of the bounding elements.\nYou are prompted to Specify gap between adjacent plates (include notches, Profile cut) or <#mm>\nInput a dimensional value in the field and press Enter to set the gap between adjacent plates.\nOutside\nPress the down arrow key and select Outside to create bounding plates with outside alignment. The created plates are aligned with the outside edge of the bounding elements. Bounding plates with adjacent edges are automatically detected and aligned to the centre to avoid an overlap.\nYou are prompted to Specify gap between adjacent plates (include notches, Profile cut) or <#mm>\nInput a dimensional value in the field and press Enter to set the gap between adjacent plates.\nExclude notches\nPress the down arrow key and select Exclude notches to create bounding plates with notches, any associated offset value is excluded.\nOutline cut\nPress the down arrow key and select Outline cut to create bounding plates with notches that align to the outline of the notched sections.\nBack\nPress the down arrow key and select Back to undo the last action.\nInclude notches\nPress the down arrow key and select Include notches to create bounding plates with notches, any associated offset value is included.\nProfile cut\nPress the down arrow key and select Profile cut to create bounding plates with notches that align to the profile of the notched sections.\nThickness\nPress the down arrow key and select Thickness to define the thickness of the bounding plate.\nYou are prompted to Panel thickness <#>\nInput a dimensional value in the field and press Enter to set the thickness of the bounded plate.\nJustification\nPress the down arrow key and select Justification to define the justification position of the bounded plates.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nTop\nPress the down arrow key and select Top to create bounded plates with top justification.\nBottom\nPress the down arrow key and select Bottom to create bounded plates with bottom justification.\nCentre\nPress the down arrow key and select Centre to create bounded plates with centre justification.\nNote:\nThe reference plane defined from the surface pick passes through the world position of the section, disregarding the justification. The functionality works optimally for sections with the justification set to top.\n\n\n\nDefault Panel Specification\nSelect top surface of section\nNote:\nSelect bounding elements\nShift\nEnter\nSelect sections and/or panels for notches\nShift\nEnter\nSelect boundary alignment <Inside>\nI\nEnter\nSpecify edge offset (include notches, Profile cut) or <#mm>\nEnter\nConfirm plate properties <Thk: #mm, Just: #>\nDefault Panel Specification\nEnter\nESC\nInside\nInside\nCentre\nCentre\nSpecify gap between adjacent plates (include notches, Profile cut) or <#mm>\nEnter\nOutside\nOutside\nSpecify gap between adjacent plates (include notches, Profile cut) or <#mm>\nEnter\nExclude notches\nExclude notches\nOutline cut\nOutline cut\nBack\nBack\nInclude notches\nInclude notches\nProfile cut\nProfile cut\nThickness\nThickness\nPanel thickness <#>\nEnter\nJustification\nJustification\nTop\nTop\nBottom\nBottom\nCentre\nCentre"}
{"Headers": "Weld Creation with Bounded Plates", "Content": "The weld creation functionality can use the information from Structural Connection (STCONN) elements on bounded plates to create welds around bounded plates, with their respective connection and specification references populated.\n\nThe welds are created as part of the create bounded plates process. Each weld corresponds to a bounding or notching element.\nRefer to Non-Routed Item, Bounded Plate Health Checker and Create Panel Welds for further information.\n\n\n\nNon-Routed Item\nBounded Plate Health Checker\nCreate Panel Welds\nNon-Routed Item\nBounded Plate Health Checker\nCreate Panel Welds"}
{"Headers": "Create Arc Panel with Specified Centre Point and Sweep Angle", "Content": "Creates an arc panel with a specified centre point and sweep angle.\nYou are prompted to Centre point or\nInput values in the dimension fields and press Enter or click to identify the centre point position.\nYou are then prompted to Inner Diameter or <Radius>\nInput a dimensional value in the field and press Enter or click to identify the diameter of the arc panel.\nYou are then prompted to Panel width (Thk: #mm, Just: #) or\nInput a dimensional value in the field and press Enter or click to identify the width of the arc panel.\nYou are then prompted to Start angle or <#deg>\nInput an angular value in the field and press Enter or click to identify the start point.\nYou are then prompted to Sweep angle or <#deg>\nInput an angular value in the field and press Enter or click to identify the end point. An arc panel is created and displays in the 3D view.\nThroughout the panel creation process you can press ESC to cancel the command. Additional functionality is also available.\nThree point\nPress the down arrow key and select Three point to create an arc with three specified points. Refer to Create Arc Panel with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create an arc with two specified points. Refer to Create Arc Panel with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to create an arc panel with a fixed inner or outer radius.\nYou are prompted to Inner radius or <Diameter> or Outer radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the arc panel.\nOuter\nPress the down arrow key and select Outer to create an arc panel with a defined outer diameter or radius.\nYou are prompted to Outer diameter or <Radius> or Outer radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the outer diameter or radius of the arc panel.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create an arc panel with a fixed inner or outer diameter.\nYou are prompted to Inner diameter or <Radius> or Outer diameter or <Radius>\nInput a dimensional value in the field and press Enter to set the inner or outer diameter of the arc panel.\nInner\nPress the down arrow key and select Inner to create an arc panel with a defined inner diameter or radius.\nYou are prompted to Inner diameter or <Radius> or Inner radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the inner diameter or radius of the arc panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nThree point\nPress the down arrow key and select Three point to create an arc with three specified points. Refer to Create Arc Panel with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create an arc with two specified points. Refer to Create Arc Panel with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to create an arc panel with a fixed inner or outer radius.\nYou are prompted to Inner radius or <Diameter> or Outer radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the arc panel.\nOuter\nPress the down arrow key and select Outer to create an arc panel with a defined outer diameter or radius.\nYou are prompted to Outer diameter or <Radius> or Outer radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the outer diameter or radius of the arc panel.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create an arc panel with a fixed inner or outer diameter.\nYou are prompted to Inner diameter or <Radius> or Outer diameter or <Radius>\nInput a dimensional value in the field and press Enter to set the inner or outer diameter of the arc panel.\nInner\nPress the down arrow key and select Inner to create an arc panel with a defined inner diameter or radius.\nYou are prompted to Inner diameter or <Radius> or Inner radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the inner diameter or radius of the arc panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nThe new PANE element displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nThree point\nPress the down arrow key and select Three point to create an arc with three specified points. Refer to Create Arc Panel with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create an arc with two specified points. Refer to Create Arc Panel with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to create an arc panel with a fixed inner or outer radius.\nYou are prompted to Inner radius or <Diameter> or Outer radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the arc panel.\nOuter\nPress the down arrow key and select Outer to create an arc panel with a defined outer diameter or radius.\nYou are prompted to Outer diameter or <Radius> or Outer radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the outer diameter or radius of the arc panel.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create an arc panel with a fixed inner or outer diameter.\nYou are prompted to Inner diameter or <Radius> or Outer diameter or <Radius>\nInput a dimensional value in the field and press Enter to set the inner or outer diameter of the arc panel.\nInner\nPress the down arrow key and select Inner to create an arc panel with a defined inner diameter or radius.\nYou are prompted to Inner diameter or <Radius> or Inner radius or <Diameter>\nInput a dimensional value in the field and press Enter to set the inner diameter or radius of the arc panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\n\n\nCreate Arc Panel with Three Specified Points\nCreate Arc Panel with Two Specified Points\nNon-Routed Item\nCentre point or\nEnter\nInner Diameter or <Radius>\nEnter\nPanel width (Thk: #mm, Just: #) or\nEnter\nStart angle or <#deg>\nEnter\nSweep angle or <#deg>\nEnter\nESC\nThree point\nThree point\nCreate Arc Panel with Three Specified Points\nTwo point\nTwo point\nCreate Arc Panel with Two Specified Points\nRadius\nRadius\nInner radius or <Diameter> or Outer radius or <Diameter>\nEnter\nOuter\nOuter\nOuter diameter or <Radius>\nOuter radius or <Diameter>\nEnter\nBack\nBack\nDiameter\nDiameter\nInner diameter or <Radius>\nOuter diameter or <Radius>\nEnter\nInner\nInner\nInner diameter or <Radius>\nInner radius or <Diameter>\nEnter\nJustification\nJustification\nEnter\nTop\nTop\nBottom\nBottom\nCentre\nCentre\nNon-Routed Item"}
{"Headers": "Create Arc Panel with Three Specified Points", "Content": "Creates an arc panel with three specified points.\nYou are prompted to 1st circumference point or\nInput values in the dimension fields and press Enter or click to identify the first circumference point position.\nYou are then prompted to 2nd circumference point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the second circumference point position.\nYou are then prompted to 3rd circumference point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the third circumference point position.\nYou are then prompted to Specify panel width (Thk: #mm, Just: #) or\nInput a dimensional value in the field and press Enter or click to identify the width of the panel. An arc panel is created and displays in the 3D view.\nThroughout the panel creation process you can press ESC to cancel the command. Additional functionality is also available.\nCentre+\nPress the down arrow key and select Centre+ to create an arc with a specified centre point and sweep angle. Refer to Create Arc Panel with Specified Centre Point and Sweep Angle for further information.\nTwo point\nPress the down arrow key and select Two point to create an arc with two specified points. Refer to Create Arc Panel with Two Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nCentre+\nPress the down arrow key and select Centre+ to create an arc with a specified centre point and sweep angle. Refer to Create Arc Panel with Specified Centre Point and Sweep Angle for further information.\nTwo point\nPress the down arrow key and select Two point to create an arc with two specified points. Refer to Create Arc Panel with Two Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nThe new PANE displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nCentre+\nPress the down arrow key and select Centre+ to create an arc with a specified centre point and sweep angle. Refer to Create Arc Panel with Specified Centre Point and Sweep Angle for further information.\nTwo point\nPress the down arrow key and select Two point to create an arc with two specified points. Refer to Create Arc Panel with Two Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\n\n\nCreate Arc Panel with Specified Centre Point and Sweep Angle\nCreate Arc Panel with Two Specified Points\nNon-Routed Item\n1st circumference point or\nEnter\n2nd circumference point (Thk: #mm, Just: #) or\nEnter\n3rd circumference point (Thk: #mm, Just: #) or\nEnter\nSpecify panel width (Thk: #mm, Just: #) or\nEnter\nESC\nCentre+\nCentre+\nCreate Arc Panel with Specified Centre Point and Sweep Angle\nTwo point\nTwo point\nCreate Arc Panel with Two Specified Points\nJustification\nJustification\nEnter\nBack\nBack\nTop\nTop\nBottom\nBottom\nCentre\nCentre\nNon-Routed Item"}
{"Headers": "Create Arc Panel with Two Specified Points", "Content": "Creates an arc panel with two specified points.\nYou are prompted to Start diameter point or\nInput values in the dimension fields and press Enter or click to identify the first diameter point position.\nYou are then prompted to End diameter point (Thk: #mm, Just: #) or\nInput a dimensional value in the field and press Enter or click to identify the diameter of the ring panel.\nYou are then prompted to Specify panel width (Thk: #mm, Just: #) or\nInput a dimensional value in the field and press Enter or click to identify the width of the panel. An arc panel is created and displays in the 3D view.\nThroughout the panel creation process you can press ESC to cancel the command. Additional functionality is also available.\nCentre+\nPress the down arrow key and select Centre+ to create an arc with a specified centre point and sweep angle. Refer to Create Arc Panel with Specified Centre Point and Sweep Angle for further information.\nThree point\nPress the down arrow key and select Three point to create an arc with three specified points. Refer to Create Arc Panel with Three Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nCentre+\nPress the down arrow key and select Centre+ to create an arc with a specified centre point and sweep angle. Refer to Create Arc Panel with Specified Centre Point and Sweep Angle for further information.\nThree point\nPress the down arrow key and select Three point to create an arc with three specified points. Refer to Create Arc Panel with Three Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nThe new PANE displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nCentre+\nPress the down arrow key and select Centre+ to create an arc with a specified centre point and sweep angle. Refer to Create Arc Panel with Specified Centre Point and Sweep Angle for further information.\nThree point\nPress the down arrow key and select Three point to create an arc with three specified points. Refer to Create Arc Panel with Three Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\n\n\nCreate Arc Panel with Specified Centre Point and Sweep Angle\nCreate Arc Panel with Three Specified Points\nNon-Routed Item\nStart diameter point or\nEnter\nEnd diameter point (Thk: #mm, Just: #) or\nEnter\nSpecify panel width (Thk: #mm, Just: #) or\nEnter\nESC\nCentre+\nCentre+\nCreate Arc Panel with Specified Centre Point and Sweep Angle\nThree point\nThree point\nCreate Arc Panel with Three Specified Points\nJustification\nJustification\nEnter\nBack\nBack\nTop\nTop\nBottom\nBottom\nCentre\nCentre\nNon-Routed Item"}
{"Headers": "Create Ring Panel with Specified Centre Point", "Content": "Creates a ring panel with a specified centre point.\nYou are prompted to Centre point or\nInput values in the dimension fields and press Enter or click to identify the centre point position.\nYou are then prompted to Outer diameter (Thk: #mm, Just: #) or <Radius>\nInput a dimensional value in the field and press Enter or click to identify the diameter of the ring panel.\nYou are then prompted to Panel width (Thk: #mm, Just: #) or\nInput a dimensional value in the field and press Enter or click to identify the width of the ring panel. An ring panel is created and displays in the 3D view.\nThroughout the panel creation process you can press ESC to cancel the command. Additional functionality is also available.\nThree point\nPress the down arrow key and select Three point to create a ring panel with three specified points. Refer to Create Ring Panel with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create a ring panel with two specified points. Refer to Create Ring Panel with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to create a ring panel with a outer radius.\nYou are prompted to Outer radius (Thk: #mm, Just: #) or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the ring panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create a ring panel with a fixed outer diameter.\nYou are prompted to Outer diameter (Thk: #mm, Just: #) or <Radius>\nInput a dimensional value in the field and press Enter to set the outer diameter of the ring panel.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nThree point\nPress the down arrow key and select Three point to create a ring panel with three specified points. Refer to Create Ring Panel with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create a ring panel with two specified points. Refer to Create Ring Panel with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to create a ring panel with a outer radius.\nYou are prompted to Outer radius (Thk: #mm, Just: #) or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the ring panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create a ring panel with a fixed outer diameter.\nYou are prompted to Outer diameter (Thk: #mm, Just: #) or <Radius>\nInput a dimensional value in the field and press Enter to set the outer diameter of the ring panel.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nThe new PANE displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nThree point\nPress the down arrow key and select Three point to create a ring panel with three specified points. Refer to Create Ring Panel with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create a ring panel with two specified points. Refer to Create Ring Panel with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to create a ring panel with a outer radius.\nYou are prompted to Outer radius (Thk: #mm, Just: #) or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the ring panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create a ring panel with a fixed outer diameter.\nYou are prompted to Outer diameter (Thk: #mm, Just: #) or <Radius>\nInput a dimensional value in the field and press Enter to set the outer diameter of the ring panel.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\n\n\nCreate Ring Panel with Three Specified Points\nCreate Ring Panel with Two Specified Points\nNon-Routed Item\nCentre point or\nEnter\nOuter diameter (Thk: #mm, Just: #) or <Radius>\nEnter\nPanel width (Thk: #mm, Just: #) or\nEnter\nESC\nThree point\nThree point\nCreate Ring Panel with Three Specified Points\nTwo point\nTwo point\nCreate Ring Panel with Two Specified Points\nRadius\nRadius\nOuter radius (Thk: #mm, Just: #) or <Diameter>\nEnter\nJustification\nJustification\nEnter\nBack\nBack\nDiameter\nDiameter\nOuter diameter (Thk: #mm, Just: #) or <Radius>\nEnter\nTop\nTop\nBottom\nBottom\nCentre\nCentre\nNon-Routed Item"}
{"Headers": "Create Ring Panel with Three Specified Points", "Content": "Creates a ring panel with three specified points.\nYou are prompted to 1st circumference point or\nInput values in the dimension fields and press Enter or click to identify the first circumference point position.\nYou are then prompted to 2nd circumference point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the second circumference point position.\nYou are then prompted to 3rd circumference point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the third circumference point position.\nYou are then prompted to Panel width (Thk: #mm, Just: #) or\nInput a dimensional value in the field and press Enter or click to identify the width of the ring panel. A ring panel is created and displays in the 3D view.\nThroughout the panel creation process you can press ESC to cancel the command. Additional functionality is also available.\nCentre+\nPress the down arrow key and select Centre+ to create a ring panel with a specified centre point. Refer to Create Ring Panel with Specified Centre Point for further information.\nTwo point\nPress the down arrow key and select Two point to create a ring panel with two specified points. Refer to Create Ring Panel with Two Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nCentre+\nPress the down arrow key and select Centre+ to create a ring panel with a specified centre point. Refer to Create Ring Panel with Specified Centre Point for further information.\nTwo point\nPress the down arrow key and select Two point to create a ring panel with two specified points. Refer to Create Ring Panel with Two Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nThe new PANE displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nCentre+\nPress the down arrow key and select Centre+ to create a ring panel with a specified centre point. Refer to Create Ring Panel with Specified Centre Point for further information.\nTwo point\nPress the down arrow key and select Two point to create a ring panel with two specified points. Refer to Create Ring Panel with Two Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\n\n\nCreate Ring Panel with Specified Centre Point\nCreate Ring Panel with Two Specified Points\nNon-Routed Item\n1st circumference point or\nEnter\n2nd circumference point (Thk: #mm, Just: #) or\nEnter\n3rd circumference point (Thk: #mm, Just: #) or\nEnter\nPanel width (Thk: #mm, Just: #) or\nEnter\nESC\nCentre+\nCentre+\nCreate Ring Panel with Specified Centre Point\nTwo point\nTwo point\nCreate Ring Panel with Two Specified Points\nJustification\nJustification\nEnter\nBack\nBack\nTop\nTop\nBottom\nBottom\nCentre\nCentre\nNon-Routed Item"}
{"Headers": "Create Ring Panel with Two Specified Points", "Content": "Creates a ring panel with two specified points.\nYou are prompted to Start diameter point or\nInput values in the dimension fields and press Enter or click to identify the first diameter point position.\nYou are then prompted to End diameter point (Thk: #mm, Just: #) or\nInput a dimensional value in the field and press Enter or click to identify the diameter of the ring section.\nYou are then prompted to Panel width (Thk: #mm, Just: #) or\nInput a dimensional value in the field and press Enter or click to identify the width of the ring panel. A ring panel is created and displays in the 3D view.\nThroughout the panel creation process you can press ESC to cancel the command. Additional functionality is also available.\nCentre+\nPress the down arrow key and select Centre+ to create a ring panel with a specified centre point. Refer to Create Ring Panel with Specified Centre Point for further information.\nThree point\nPress the down arrow key and select Three point to create a ring panel with three specified points. Refer to Create Ring Panel with Three Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nCentre+\nPress the down arrow key and select Centre+ to create a ring panel with a specified centre point. Refer to Create Ring Panel with Specified Centre Point for further information.\nThree point\nPress the down arrow key and select Three point to create a ring panel with three specified points. Refer to Create Ring Panel with Three Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nThe new PANE displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nCentre+\nPress the down arrow key and select Centre+ to create a ring panel with a specified centre point. Refer to Create Ring Panel with Specified Centre Point for further information.\nThree point\nPress the down arrow key and select Three point to create a ring panel with three specified points. Refer to Create Ring Panel with Three Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\n\n\nCreate Ring Panel with Specified Centre Point\nCreate Ring Panel with Three Specified Points\nNon-Routed Item\nStart diameter point or\nEnter\nEnd diameter point (Thk: #mm, Just: #) or\nEnter\nPanel width (Thk: #mm, Just: #) or\nEnter\nESC\nCentre+\nCentre+\nCreate Ring Panel with Specified Centre Point\nThree point\nThree point\nCreate Ring Panel with Three Specified Points\nJustification\nJustification\nEnter\nBack\nBack\nTop\nTop\nBottom\nBottom\nCentre\nCentre\nNon-Routed Item"}
{"Headers": "Create Disc Panel with Specified Centre Point", "Content": "Creates a disc panel with a specified centre point.\nYou are prompted to Centre point or\nInput values in the dimension fields and press Enter or click to identify the centre point position.\nYou are then prompted to Diameter (Thk: #mm, Just: #) or <Radius>\nInput a dimensional value in the field and press Enter or click to identify the diameter of the disc panel. A disc panel is created and displays in the 3D view.\nThroughout the section creation process you can press ESC to cancel the command. Additional functionality is also available.\nThree point\nPress the down arrow key and select Three point to create a disc panel with three specified points. Refer to Create Disc Panel with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc panel with two specified points. Refer to Create Disc Panel with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to create a disc panel with a fixed radius.\nYou are prompted to Radius (Thk: #mm, Just: #) or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the disc panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create a disc panel with a fixed diameter.\nYou are prompted to Diameter (Thk: #mm, Just: #) or <Radius>\nInput a dimensional value in the field and press Enter to set the diameter of the disc panel.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nThree point\nPress the down arrow key and select Three point to create a disc panel with three specified points. Refer to Create Disc Panel with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc panel with two specified points. Refer to Create Disc Panel with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to create a disc panel with a fixed radius.\nYou are prompted to Radius (Thk: #mm, Just: #) or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the disc panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create a disc panel with a fixed diameter.\nYou are prompted to Diameter (Thk: #mm, Just: #) or <Radius>\nInput a dimensional value in the field and press Enter to set the diameter of the disc panel.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nThe new PANE displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nThree point\nPress the down arrow key and select Three point to create a disc panel with three specified points. Refer to Create Disc Panel with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc panel with two specified points. Refer to Create Disc Panel with Two Specified Points for further information.\nRadius\nPress the down arrow key and select Radius to create a disc panel with a fixed radius.\nYou are prompted to Radius (Thk: #mm, Just: #) or <Diameter>\nInput a dimensional value in the field and press Enter to set the radii of the disc panel.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nDiameter\nPress the down arrow key and select Diameter to create a disc panel with a fixed diameter.\nYou are prompted to Diameter (Thk: #mm, Just: #) or <Radius>\nInput a dimensional value in the field and press Enter to set the diameter of the disc panel.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\n\n\nCreate Disc Panel with Three Specified Points\nCreate Disc Panel with Two Specified Points\nNon-Routed Item\nCentre point or\nEnter\nDiameter (Thk: #mm, Just: #) or <Radius>\nEnter\nESC\nThree point\nThree point\nCreate Disc Panel with Three Specified Points\nTwo point\nTwo point\nCreate Disc Panel with Two Specified Points\nRadius\nRadius\nRadius (Thk: #mm, Just: #) or <Diameter>\nEnter\nJustification\nJustification\nEnter\nBack\nBack\nDiameter\nDiameter\nDiameter (Thk: #mm, Just: #) or <Radius>\nEnter\nTop\nTop\nBottom\nBottom\nCentre\nCentre\nNon-Routed Item"}
{"Headers": "Create Disc Panel with Three Specified Points", "Content": "Creates a disc panel with three specified points.\nYou are prompted to 1st circumference point or\nInput values in the dimension fields and press Enter or click to identify the first circumference point position.\nYou are then prompted to 2nd circumference point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the second circumference point position.\nYou are then prompted to 3rd circumference point (Thk: #mm, Just: #) or\nInput values in the dimension fields and press Enter or click to identify the third circumference point position. A disc panel is created and displays in the 3D view.\nThroughout the panel creation process you can press ESC to cancel the command. Additional functionality is also available.\nCentre+\nPress the down arrow key and select Centre+ to create a disc panel with a specified centre point. Refer to Create Disc Panel with Specified Centre Point for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc panel with two specified points. Refer to Create Disc Panel with Two Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nCentre+\nPress the down arrow key and select Centre+ to create a disc panel with a specified centre point. Refer to Create Disc Panel with Specified Centre Point for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc panel with two specified points. Refer to Create Disc Panel with Two Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\nThe new PANE displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nCentre+\nPress the down arrow key and select Centre+ to create a disc panel with a specified centre point. Refer to Create Disc Panel with Specified Centre Point for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc panel with two specified points. Refer to Create Disc Panel with Two Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\n\n\n\nCreate Disc Panel with Specified Centre Point\nCreate Disc Panel with Two Specified Points\nNon-Routed Item\n1st circumference point or\nEnter\n2nd circumference point (Thk: #mm, Just: #) or\nEnter\n3rd circumference point (Thk: #mm, Just: #) or\nEnter\nESC\nCentre+\nCentre+\nCreate Disc Panel with Specified Centre Point\nTwo point\nTwo point\nCreate Disc Panel with Two Specified Points\nJustification\nJustification\nEnter\nBack\nBack\nTop\nTop\nBottom\nBottom\nCentre\nCentre\nNon-Routed Item"}
{"Headers": "Create Disc Panel with Two Specified Points", "Content": "Creates a disc panel with two specified points.\nYou are prompted to Start diameter point or\nInput values in the dimension fields and press Enter or click to identify the first diameter point position.\nYou are then prompted to End diameter point (Thk: #mm, Just: #) or\nInput a dimensional value in the field and press Enter or click to identify the diameter of the disc panel. A disc panel is created and displays in the 3D view.\nThroughout the panel creation process you can press ESC to cancel the command. Additional functionality is also available.\nCentre+\nPress the down arrow key and select Centre+ to create a disc panel with a specified centre point. Refer to Create Disc Panel with Specified Centre Point for further information.\nThree point\nPress the down arrow key and select Three point to create a ring panel with three specified points. Refer to Create Disc Panel with Three Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\n\nCentre+\nPress the down arrow key and select Centre+ to create a disc panel with a specified centre point. Refer to Create Disc Panel with Specified Centre Point for further information.\nThree point\nPress the down arrow key and select Three point to create a ring panel with three specified points. Refer to Create Disc Panel with Three Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\n\nThe new PANE displays in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nCentre+\nPress the down arrow key and select Centre+ to create a disc panel with a specified centre point. Refer to Create Disc Panel with Specified Centre Point for further information.\nThree point\nPress the down arrow key and select Three point to create a ring panel with three specified points. Refer to Create Disc Panel with Three Specified Points for further information.\nJustification\nPress the down arrow key and select Justification to define the justification position of the panel.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a panel with top justification.\nCentre\nPress the down arrow key and select Centre to create a panel with centre justification.\nBottom\nPress the down arrow key and select Bottom to create a panel with bottom justification.\n\n\n\nCreate Disc Panel with Specified Centre Point\nCreate Disc Panel with Three Specified Points\nNon-Routed Item\nStart diameter point or\nEnter\nEnd diameter point (Thk: #mm, Just: #) or\nEnter\nESC\nCentre+\nCentre+\nCreate Disc Panel with Specified Centre Point\nThree point\nThree point\nCreate Disc Panel with Three Specified Points\nJustification\nJustification\nEnter\nBack\nBack\nTop\nTop\nCentre\nCentre\nBottom\nBottom\nNon-Routed Item"}
{"Headers": "Negative Extrusions", "Content": "Creates a negative extrusion by positioning PAVE elements to form a Loop (LOOP) and then extruding them. A negative extrusion represents a negative volume, that is, a hole.\nA negative extrusion is owned by the panel through which the hole is positioned.\nThe example displays a negative extrusion through a floor plate, a column passes through the negative extrusion.\n\nVertices V1-V4 define the negative extrusion; the vertex numbering is independent of the panel vertices.\nThe outer edge of the negative extrusion (V1-V2) extends beyond the outer edge of the panel to make sure that the hole penetrates through the panel edge. Similarly, it may be necessary to define the thickness of the negative extrusion to exceed the thickness of the panel to make sure that the hole penetrates completely through the panel.\n\n\n"}
{"Headers": "Create Rectangle Negative Extrusion with Two Specified Points", "Content": "Creates a rectangle negative extrusion with two specified points.\nYou are prompted to Select panel\nClick to identify the panel using a cursor pick in the 3D view.\nYou are then prompted to First corner (Surface: #, Depth: #mm) or\nInput values in the dimension fields and press Enter or click to identify the first corner position.\nYou are then prompted to Second corner (Surface: #, Depth: #mm) or\nInput values in the dimension fields and press Enter or click to identify the second corner position. A rectangle negative extrusion is created and displays in the 3D view.\nThroughout the negative extrusion creation process you can press ESC to cancel the command. Additional functionality is also available.\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nFillet\nPress the down arrow key and select Fillet to create a negative extrusion with a specified fillet.\nYou are prompted to Specify the Fillet <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nFillet\nPress the down arrow key and select Fillet to create a negative extrusion with a specified fillet.\nYou are prompted to Specify the Fillet <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nThe new PLOO and PAVE elements display in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nFillet\nPress the down arrow key and select Fillet to create a negative extrusion with a specified fillet.\nYou are prompted to Specify the Fillet <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\nBack\nPress the down arrow key and select Back to undo the last action.\nNote:\nThe prompt does not display if the panel is already selected.\n\n\n\nNon-Routed Item\nSelect panel\nNote\n:\nFirst corner (Surface: #, Depth: #mm) or\nEnter\nSecond corner (Surface: #, Depth: #mm) or\nEnter\nESC\nReference Point\nReference Point\nReference Point or\nEnter\nDepth\nDepth\nSpecify the Depth <#>\nEnter\nSurface\nSurface\nEnter\nFillet\nFillet\nSpecify the Fillet <#>\nEnter\nTop\nTop\nBottom\nBottom\nBack\nBack\nNon-Routed Item"}
{"Headers": "Create Multiple Point Negative Extrusion", "Content": "Creates a multiple point negative extrusion.\nYou are prompted to Select panel\nClick to identify the panel using a cursor pick in the 3D view.\nYou are then prompted to First point (Surface: #, Depth: #mm) or\nInput values in the dimension fields and press Enter or click to identify the first point position.\nYou are then prompted to Next point (Surface: #, Depth: #mm) or\nInput values in the dimension fields and press Enter or click to identify the next point position.\nYou are then prompted to Next point (Surface: #, Depth: #mm) or <Finish>\nThe prompt is repeated, allowing you to create multiple negative extrusion points.\nInput F at the prompt and press Enter to end the command. A multiple point negative extrusion is created and displays in the 3D view.\nThroughout the negative extrusion creation process you can press ESC to cancel the command. Additional functionality is also available.\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nFillet\nPress the down arrow key and select Fillet to create a negative extrusion with a specified fillet.\nYou are prompted to Specify the Filllet <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nFillet\nPress the down arrow key and select Fillet to create a negative extrusion with a specified fillet.\nYou are prompted to Specify the Filllet <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new PLOO and PAVE elements display in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nFillet\nPress the down arrow key and select Fillet to create a negative extrusion with a specified fillet.\nYou are prompted to Specify the Filllet <#>\nInput a dimensional value in the field and press Enter to set the fillet of the panel.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nNote:\nThe prompt does not display if the panel is already selected.\n\n\n\nNon-Routed Item\nSelect panel\nNote\n:\nFirst point (Surface: #, Depth: #mm) or\nEnter\nNext point (Surface: #, Depth: #mm) or\nEnter\nNext point (Surface: #, Depth: #mm) or <Finish>\nF\nEnter\nESC\nReference Point\nReference Point\nReference Point or\nEnter\nDepth\nDepth\nSpecify the Depth <#>\nEnter\nSurface\nSurface\nEnter\nFillet\nFillet\nSpecify the Filllet <#>\nEnter\nTop\nTop\nBottom\nBottom\nBack\nBack\nFinish\nFinish\nNon-Routed Item"}
{"Headers": "Create Disc Negative Extrusion with Specified Centre Point", "Content": "Creates a disc negative extrusion with a specified centre point.\nYou are prompted to Select panel\nClick to identify the panel using a cursor pick in the 3D view.\nYou are then prompted to Centre point (Surface: #, Depth: #mm) or\nInput values in the dimension fields and press Enter or click to identify the centre point position.\nYou are then prompted to Specify radius (Surface: #, Depth: #mm) or\nInput a dimensional value in the field and press Enter or click to identify the radius of the disc negative extrusion. A disc negative extrusion is created and displays in the 3D view.\nThroughout the negative extrusion creation process you can press ESC to cancel the command. Additional functionality is also available.\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nThree point\nPress the down arrow key and select Three point to create a disc negative extrusion with three specified points. Refer to Create Disc Negative Extrusion with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc negative extrusion with two specified points. Refer to Create Disc Negative Extrusion with Two Specified Points for further information.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\n\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nThree point\nPress the down arrow key and select Three point to create a disc negative extrusion with three specified points. Refer to Create Disc Negative Extrusion with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc negative extrusion with two specified points. Refer to Create Disc Negative Extrusion with Two Specified Points for further information.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\n\nThe new PLOO and PAVE elements display in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nThree point\nPress the down arrow key and select Three point to create a disc negative extrusion with three specified points. Refer to Create Disc Negative Extrusion with Three Specified Points for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc negative extrusion with two specified points. Refer to Create Disc Negative Extrusion with Two Specified Points for further information.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\nNote:\nThe prompt does not display if the panel is already selected.\n\n\n\nCreate Disc Negative Extrusion with Three Specified Points\nCreate Disc Negative Extrusion with Two Specified Points\nNon-Routed Item\nSelect panel\nNote\n:\nCentre point (Surface: #, Depth: #mm) or\nEnter\nSpecify radius (Surface: #, Depth: #mm) or\nEnter\nESC\nReference Point\nReference Point\nReference Point or\nEnter\nThree point\nThree point\nCreate Disc Negative Extrusion with Three Specified Points\nTwo point\nTwo point\nCreate Disc Negative Extrusion with Two Specified Points\nDepth\nDepth\nSpecify the Depth <#>\nEnter\nSurface\nSurface\nEnter\nBack\nBack\nTop\nTop\nBottom\nBottom\nNon-Routed Item"}
{"Headers": "Create Disc Negative Extrusion with Three Specified Points", "Content": "Creates a disc negative extrusion with three specified points.\nYou are prompted to Select panel\nClick to identify the panel using a cursor pick in the 3D view.\nYou are then prompted to 1st circumference point (Surface: #, Depth: #mm) or\nInput values in the dimension fields and press Enter or click to identify the first circumference point position.\nYou are then prompted to 2nd circumference point (Surface: #, Depth: #mm) or\nInput values in the dimension fields and press Enter or click to identify the second circumference point position.\nYou are then prompted to 3rd circumference point (Surface: #, Depth: #mm) or\nInput values in the dimension fields and press Enter or click to identify the third circumference point position. A disc negative extrusion is created and displays in the 3D view.\nThroughout the negative extrusion creation process you can press ESC to cancel the command. Additional functionality is also available.\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nCentre+\nPress the down arrow key and select Centre+ to create a disc negative extrusion with a specified centre point. Refer to Create Disc Negative Extrusion with Specified Centre Point for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc negative extrusion with two specified points. Refer to Create Disc Negative Extrusion with Two Specified Points for further information.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\n\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nCentre+\nPress the down arrow key and select Centre+ to create a disc negative extrusion with a specified centre point. Refer to Create Disc Negative Extrusion with Specified Centre Point for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc negative extrusion with two specified points. Refer to Create Disc Negative Extrusion with Two Specified Points for further information.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\n\nThe new PLOO and PAVE elements display in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nCentre+\nPress the down arrow key and select Centre+ to create a disc negative extrusion with a specified centre point. Refer to Create Disc Negative Extrusion with Specified Centre Point for further information.\nTwo point\nPress the down arrow key and select Two point to create a disc negative extrusion with two specified points. Refer to Create Disc Negative Extrusion with Two Specified Points for further information.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\nNote:\nThe prompt does not display if the panel is already selected.\n\n\n\nCreate Disc Negative Extrusion with Specified Centre Point\nCreate Disc Negative Extrusion with Two Specified Points\nNon-Routed Item\nSelect panel\nNote\n:\n1st circumference point (Surface: #, Depth: #mm) or\nEnter\n2nd circumference point (Surface: #, Depth: #mm) or\nEnter\n3rd circumference point (Surface: #, Depth: #mm) or\nEnter\nESC\nReference Point\nReference Point\nReference Point or\nEnter\nCentre+\nCentre+\nCreate Disc Negative Extrusion with Specified Centre Point\nTwo point\nTwo point\nCreate Disc Negative Extrusion with Two Specified Points\nDepth\nDepth\nSpecify the Depth <#>\nEnter\nSurface\nSurface\nEnter\nBack\nBack\nTop\nTop\nBottom\nBottom\nNon-Routed Item"}
{"Headers": "Create Disc Negative Extrusion with Two Specified Points", "Content": "Creates a disc negative extrusion with two specified points.\nYou are prompted to Select panel\nClick to identify the panel using a cursor pick in the 3D view.\nYou are then prompted to Start diameter point (Surface: #, Depth: #mm) or\nInput values in the dimension fields and press Enter or click to identify the start diameter point position.\nYou are then prompted to End Diameter Point (Surface: #, Depth: #mm) or\nInput a dimensional value in the field and press Enter or click to identify the diameter of the disc negative extrusion. A disc negative extrusion is created and displays in the 3D view.\nThroughout the panel creation process you can press ESC to cancel the command. Additional functionality is also available.\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nCentre+\nPress the down arrow key and select Centre+ to create a disc negative extrusion with a specified centre point. Refer to Create Disc Negative Extrusion with Specified Centre Point for further information.\nThree point\nPress the down arrow key and select Three point to create a disc negative extrusion with three specified points. Refer to Create Disc Negative Extrusion with Three Specified Points for further information.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\n\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nCentre+\nPress the down arrow key and select Centre+ to create a disc negative extrusion with a specified centre point. Refer to Create Disc Negative Extrusion with Specified Centre Point for further information.\nThree point\nPress the down arrow key and select Three point to create a disc negative extrusion with three specified points. Refer to Create Disc Negative Extrusion with Three Specified Points for further information.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\n\nThe new PLOO and PAVE elements display in the Model Explorer.\n\nRefer to Non-Routed Item for further information.\nReference Point\nPress the down arrow key and select Reference Point to define a reference point from which the first extrusion point is measured.\nYou are prompted to Reference Point or\nInput values in the dimension fields and press Enter or click to identify the reference point position.\nCentre+\nPress the down arrow key and select Centre+ to create a disc negative extrusion with a specified centre point. Refer to Create Disc Negative Extrusion with Specified Centre Point for further information.\nThree point\nPress the down arrow key and select Three point to create a disc negative extrusion with three specified points. Refer to Create Disc Negative Extrusion with Three Specified Points for further information.\nDepth\nPress the down arrow key and select Depth to define the depth of the negative extrusion.\nYou are prompted to Specify the Depth <#>\nThe default depth value is identical to the associated panel thickness. Input a dimensional value in the field and press Enter to set the depth of the negative extrusion.\nSurface\nPress the down arrow key and select Surface to define the surface position of the negative extrusion.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nBack\nPress the down arrow key and select Back to undo the last action.\nTop\nPress the down arrow key and select Top to create a negative extrusion aligned to the top of the associated panel.\nBottom\nPress the down arrow key and select Bottom to create a negative extrusion aligned to the bottom of the associated panel.\nNote:\nThe prompt does not display if the panel is already selected.\n\n\n\nCreate Disc Negative Extrusion with Specified Centre Point\nCreate Disc Negative Extrusion with Three Specified Points\nNon-Routed Item\nSelect panel\nNote\n:\nStart diameter point (Surface: #, Depth: #mm) or\nEnter\nEnd Diameter Point (Surface: #, Depth: #mm) or\nEnter\nESC\nReference Point\nReference Point\nReference Point or\nEnter\nCentre+\nCentre+\nCreate Disc Negative Extrusion with Specified Centre Point\nThree point\nThree point\nCreate Disc Negative Extrusion with Three Specified Points\nDepth\nDepth\nSpecify the Depth <#>\nEnter\nSurface\nSurface\nEnter\nBack\nBack\nTop\nTop\nBottom\nBottom\nNon-Routed Item"}
{"Headers": "Create Panel Fittings", "Content": "Creates a Panel Fitting (PFIT) element which can be used to represent any item which is attached to a Panel. These can be used to indicate such things as the presence of the penetrating item or an ancillary item such as an inspection cover, doorway or manhole. A PFIT is positioned relative to the origin of its owning panel.\nAs with a bolted joint, panel fittings can incorporate (or consist entirely of) negative volumes which represent holes in their owning panels.\nA panel fitting is positioned relative to its owning panel\u2019s origin by setting the position properties and is orientated about an axis perpendicular to the panel by setting the beta angle properties. It can be justified to align its origin plane with the top face, centre plane, or bottom face of the panel by setting the justification property. As an example, a stylised manhole might be defined.\n\nA PFIT is a catalogue item which can be used to represent any type of geometric entity which is to be owned by, and positioned relative to, a panel. Typically, the catalogue might include panel fittings which represent, for example, doors, windows, access manholes and lifting lugs.\nYou are prompted to Select panel\nClick to identify the panel to associate with the fitting to display the Panel Fitting window.\n\nThe Panel Fitting window allows you to associate a catalogue specification with the fitting and modify the dimensions of the fitting component parts. The functionality of the Panel Fitting window is identical to the Section Fitting window. Refer to Create Section Fitting for further information.\nOnce a fitting has been selected using the Panel Fitting window. You can position the fitting on the panel.\nYou are prompted to Specify Position (Just: #) or\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nA fitting is created and displays in the 3D view.\nThroughout the fitting creation process you can press ESC to cancel the command. Additional functionality is also available.\nJustification\nPress the down arrow key and select Justification to define the justification position of the fitting.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nAngle\nPress the down arrow key and select Angle to rotate the fitting.\nYou are prompted to Specify Angle <#deg>\nInput an angular value in the field and press Enter or click to identify the angle of the fitting.\nRepeat\nPress the down arrow key and select Repeat to create multiple fittings.\nYou are prompted to Specify position (Just: #) or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nThe prompt is repeated allowing you to create multiple fittings.\nInput F at the prompt and press Enter to end the command.\nTop outwards\nPress the down arrow key and select Top outwards to create a fitting with top outward justification.\nTop inwards\nPress the down arrow key and select Top inwards to create a fitting with top inward justification.\nCentre outwards\nPress the down arrow key and select Centre outwards to create a fitting with centre outward justification.\nCentre inwards\nPress the down arrow key and select Centre inwards to create a fitting with centre inward justification.\nBottom outwards\nPress the down arrow key and select Bottom outwards to create a fitting with bottom outward justification.\nBottom inwards\nPress the down arrow key and select Bottom inwards to create a fitting with bottom inward justification.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nJustification\nPress the down arrow key and select Justification to define the justification position of the fitting.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\n\nAngle\nPress the down arrow key and select Angle to rotate the fitting.\nYou are prompted to Specify Angle <#deg>\nInput an angular value in the field and press Enter or click to identify the angle of the fitting.\nRepeat\nPress the down arrow key and select Repeat to create multiple fittings.\nYou are prompted to Specify position (Just: #) or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nThe prompt is repeated allowing you to create multiple fittings.\nInput F at the prompt and press Enter to end the command.\nTop outwards\nPress the down arrow key and select Top outwards to create a fitting with top outward justification.\nTop inwards\nPress the down arrow key and select Top inwards to create a fitting with top inward justification.\nCentre outwards\nPress the down arrow key and select Centre outwards to create a fitting with centre outward justification.\nCentre inwards\nPress the down arrow key and select Centre inwards to create a fitting with centre inward justification.\nBottom outwards\nPress the down arrow key and select Bottom outwards to create a fitting with bottom outward justification.\nBottom inwards\nPress the down arrow key and select Bottom inwards to create a fitting with bottom inward justification.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new PFIT element displays in the Model Explorer.\n\nJustification\nPress the down arrow key and select Justification to define the justification position of the fitting.\nInput a justification value in the field and press Enter or press the down arrow key and select a justification value.\nAngle\nPress the down arrow key and select Angle to rotate the fitting.\nYou are prompted to Specify Angle <#deg>\nInput an angular value in the field and press Enter or click to identify the angle of the fitting.\nRepeat\nPress the down arrow key and select Repeat to create multiple fittings.\nYou are prompted to Specify position (Just: #) or <Finish>\nInput a dimensional value in the field and press Enter or click to identify the position of the fitting.\nThe prompt is repeated allowing you to create multiple fittings.\nInput F at the prompt and press Enter to end the command.\nTop outwards\nPress the down arrow key and select Top outwards to create a fitting with top outward justification.\nTop inwards\nPress the down arrow key and select Top inwards to create a fitting with top inward justification.\nCentre outwards\nPress the down arrow key and select Centre outwards to create a fitting with centre outward justification.\nCentre inwards\nPress the down arrow key and select Centre inwards to create a fitting with centre inward justification.\nBottom outwards\nPress the down arrow key and select Bottom outwards to create a fitting with bottom outward justification.\nBottom inwards\nPress the down arrow key and select Bottom inwards to create a fitting with bottom inward justification.\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nCreate Section Fitting\nSelect panel\nPanel Fitting\nPanel Fitting\nPanel Fitting\nSection Fitting\nCreate Section Fitting\nPanel Fitting\nSpecify Position (Just: #) or\nEnter\nESC\nJustification\nJustification\nEnter\nAngle\nAngle\nSpecify Angle <#deg>\nEnter\nRepeat\nRepeat\nSpecify position (Just: #) or <Finish>\nEnter\nF\nEnter\nTop outwards\nTop outwards\nTop inwards\nTop inwards\nCentre outwards\nCentre outwards\nCentre inwards\nCentre inwards\nBottom outwards\nBottom outwards\nBottom inwards\nBottom inwards\nFinish\nFinish"}
{"Headers": "Create Panel Welds", "Content": "Creates a Structural Weld Set (STWSET) element which owns one or more Structural Weld (STWELD) elements which are used to represent welds between panel edges or between panel edges and section edges. STWELD elements contain the weld information. For example, the connection reference and the weld geometry.\nSTWELD elements are owned by Panel (PANE elements).\n\nThe example displays a weld between panel edges.\n\nThe example displays a weld between a panel edge and a section edge.\n\nWeld Settings\nBefore welds can be modelled, various settings must be defined to determine, for example, the weld creation tolerance and the weld properties for the creation of welds.\nDefault Weld Specification\nSets the default specification for the creation of panel welds.\n\nAutomatic Weld Creation\nSets the default weld creation status when a new connection is made between panel edges or between panel edges and section edges.\nIf the selection is highlighted, automatic weld creation is on.\nIf the selection is not highlighted, automatic weld creation is off.\nAutomatic welds can be created when using the following processes:\nCreate Welds from Selection\nCreates multiple welds using a selection of sections and panels. For example, a deck of (non-bounded) panels with support beams underneath\n\nWelds are created for:\nYou are prompted to Select panels and sections\nDrag a rectangular fence around the items to be selected. Alternatively, click to select the initial item then press Shift and click to select additional items.\n\nPress Enter to create the welds.\nWelds are created between the selected panels and the adjacent panels and sections. The created welds display in the 3D view.\n\nWelds are created between the underside of the panel and the intersecting edges of the supporting beams (the example is viewed from underneath the deck).\n\nWelds can be created for overlapping plates.\n\nIn the example, the red coloured welds are owned by the blue panel (currently selected), while the blue coloured welds are owned by the other panels.\n\nThe connection status of panel welds can be inspected and modified using the Connection Review window. Refer to Review Connections for further information.\nThe direction of the weld displays in the 3D view when a weld is selected on the Connection Review window. Alternatively, the direction of the currently selected weld in the 3D view can be indicated by an arrow using the command window.\nThe STWDIR attribute, owned by a Structural Weld element (STWELD), can be queried for deck plates. The example syntax queries the weld direction of pin 1 of the STWELD:\nBy default, all welds owned by a deck plate point downwards with respect to the owner.\n\nThe PPOS and PDIR psuedo attributes, defined in the RPATH element and owned by a STWELD element, can be queried for straight welds. The example syntax queries the weld directions of pin 1 and pin 2 of the STWELD:\nBuy default, the start direction points into the weld and the end direction points away from the weld.\n\nUpdate Welds from Selection\nChecks the status of welds between panel edges or between panel edges and section edges. If applicable, you can update or repair welds as well as remove connectivity.\nYou are prompted to Select panels\nDrag a rectangular fence around the items to be selected. Alternatively, click to select the initial item then press Shift and click to select additional items.\n\nPress Enter to update the welds.\nWelds are evaluated, updated and deleted automatically.\nThere are various modification scenarios which result in weld update or deletion.\nRemoved Panel Supporting Sections\nPanel supporting sections are deleted, the welds that reference the deleted sections remain.\n\nWith the panel selected, click Update to remove the welds, all other welds are updated to fill the void.\n\nModified Profile Specification of Attached Sections\nThe profile specification of panel supporting sections are modified using the Properties window, the welds that reference the modified sections must be updated to reflect the modifications.\n\nWith the panel selected, click Update to update the welds to reflect the panel supporting section modifications.\n\nPanel Moved away from Elements connected by Welds\nA panel containing welds is moved away from supporting sections, the welds that reference the supporting sections remain.\n\nWith the panel selected, click Update to remove the welds as the distance between the panel and the supporting sections is too large to create valid welds.\n\nPanel Edge Extension along Weld Direction\nThe panel edge is extended along the direction of the weld, the weld is not extended.\n\nWith the panel selected, click Update to extend the weld.\n\nWeld Active Properties\nA series of drop-down lists are available to define the active properties for the creation of panel welds.\nWeld Rule or Explicit\nSelect Weld Rule from the drop-down list to define a rule based weld.\nSelect Explicit Weld from the drop-down list to define an explicit weld selection.\nWeld Categories\nIf Weld Rule is selected from the Weld Rule or Explicit drop-down list, a list of all Rule (DRULE) elements with a purpose of WELD in the catalogue are available for selection. The Rule Value (RVALUE) must have an answer which is a reference to a Weld Detail (WDET) element.\nIf Explicit Weld is selected from the Weld Rule or Explicit drop-down list, a list of all Structural Section (STSE) elements with a purpose of WELD in the catalogue are available for selection.\nWeld Details\nIf Weld Rule is selected from the Weld Rule or Explicit drop-down list, the Weld Details drop-down list become inactive as the weld detail is chosen automatically.\nIf Explicit Weld is selected from the Weld Rule or Explicit drop-down list, a list of all WDET elements associated with the selected STSE element are available for selection.\nWeld Rule or Explicit\nSelect Weld Rule from the drop-down list to define a rule based weld.\nSelect Explicit Weld from the drop-down list to define an explicit weld selection.\nWeld Categories\nIf Weld Rule is selected from the Weld Rule or Explicit drop-down list, a list of all Rule (DRULE) elements with a purpose of WELD in the catalogue are available for selection. The Rule Value (RVALUE) must have an answer which is a reference to a Weld Detail (WDET) element.\nIf Explicit Weld is selected from the Weld Rule or Explicit drop-down list, a list of all Structural Section (STSE) elements with a purpose of WELD in the catalogue are available for selection.\nWeld Details\nIf Weld Rule is selected from the Weld Rule or Explicit drop-down list, the Weld Details drop-down list become inactive as the weld detail is chosen automatically.\nIf Explicit Weld is selected from the Weld Rule or Explicit drop-down list, a list of all WDET elements associated with the selected STSE element are available for selection.\n\nWeld Rule or Explicit\nSelect Weld Rule from the drop-down list to define a rule based weld.\nSelect Explicit Weld from the drop-down list to define an explicit weld selection.\nWeld Categories\nIf Weld Rule is selected from the Weld Rule or Explicit drop-down list, a list of all Rule (DRULE) elements with a purpose of WELD in the catalogue are available for selection. The Rule Value (RVALUE) must have an answer which is a reference to a Weld Detail (WDET) element.\nIf Explicit Weld is selected from the Weld Rule or Explicit drop-down list, a list of all Structural Section (STSE) elements with a purpose of WELD in the catalogue are available for selection.\nWeld Details\nIf Weld Rule is selected from the Weld Rule or Explicit drop-down list, the Weld Details drop-down list become inactive as the weld detail is chosen automatically.\nIf Explicit Weld is selected from the Weld Rule or Explicit drop-down list, a list of all WDET elements associated with the selected STSE element are available for selection.\nCreate bounded plate. Refer to Create Bounded Plate for further information.\nModify panel or bounded plate, for example, splitting a panel Refer to Split Section, Panel or Bounded Plate for further information.\nExtend panel edge. Refer to Extend Panel Edge for further information.\nCreate bounded plate. Refer to Create Bounded Plate for further information.\nCreate bounded plate. Refer to Create Bounded Plate for further information.\nModify panel or bounded plate, for example, splitting a panel Refer to Split Section, Panel or Bounded Plate for further information.\nModify panel or bounded plate, for example, splitting a panel Refer to Split Section, Panel or Bounded Plate for further information.\nExtend panel edge. Refer to Extend Panel Edge for further information.\nExtend panel edge. Refer to Extend Panel Edge for further information.\nPlate-to-plate connections: Panels within the user selection with edges that are very close to each other (within the set weld creation tolerance) have welds created in the gap between them.\nPlate-to-beam connections: Primary beams within the user selection which an edge of a panel lies on, and secondary beams within the user selection have one or two welds created between the intersecting edges.\nPlate-to-plate connections: Panels within the user selection with edges that are very close to each other (within the set weld creation tolerance) have welds created in the gap between them.\nPlate-to-plate connections: Panels within the user selection with edges that are very close to each other (within the set weld creation tolerance) have welds created in the gap between them.\nPlate-to-beam connections: Primary beams within the user selection which an edge of a panel lies on, and secondary beams within the user selection have one or two welds created between the intersecting edges.\nPlate-to-beam connections: Primary beams within the user selection which an edge of a panel lies on, and secondary beams within the user selection have one or two welds created between the intersecting edges.\nNote:\nThe prompt does not display if the section and panel elements are already selected.\nNote:\nThe prompt does not display if the section and panel elements are already selected.\nNote:\nIf the automatic weld creation functionality is not enabled when panels or bounded plates are merged or split, welds can be updated by manually selecting the required items.\nNote:\nIt is not necessary to select the panel that contains that weld in order to update it. The presence of a BACKREF attribute on the structural welds means the neighbouring panel that is connected to the weld can be picked, and the weld is updated.\n\n\n\nCreate Bounded Plate\nSplit Section, Panel or Bounded Plate\nExtend Panel Edge\nReview Connections\nWeld Settings\nDefault Weld Specification\nAutomatic Weld Creation\nCreate Bounded Plate\nSplit Section, Panel or Bounded Plate\nExtend Panel Edge\nCreate Welds from Selection\nSelect panels and sections\nNote\n:\nShift\nEnter\nConnection Review\nReview Connections\nConnection Review\npin 1 at pos dir stwdir\nUpdate Welds from Selection\nSelect panels\nNote\n:\nShift\nEnter\nNote\n:\nRemoved Panel Supporting Sections\nUpdate\nModified Profile Specification of Attached Sections\nProperties\nUpdate\nPanel Moved away from Elements connected by Welds\nUpdate\nPanel Edge Extension along Weld Direction\nUpdate\nNote\n:\nWeld Active Properties\nWeld Rule or Explicit\nWeld Rule\nExplicit Weld\nWeld Categories\nWeld Rule\nWeld Rule or Explicit\nExplicit Weld\nWeld Rule or Explicit\nWeld Details\nWeld Rule\nWeld Rule or Explicit\nWeld Details\nExplicit Weld\nWeld Rule or Explicit"}
{"Headers": "Modify Panels", "Content": "Once a panel has been completed, it may be necessary to modify the panel or fixings. A panel can be modified using the Properties window or using grips. The type, geometry and position of fixings can be modified.\nEditor is a mode of operation in Model which allows you to reposition selected items using the mouse pointer. Refer to Non-Routed Item for further information.\n\n\n\nNon-Routed Item\nProperties\nModel\nNon-Routed Item"}
{"Headers": "Modify Panel Properties", "Content": "The general properties of selected panels can be modified using the Properties window. Refer to Properties for further information.\n\nThe general and positional properties of PANE elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.\nSpecification\nClassification\nInput a value in the field or select a classification from the drop-down list to modify the panel classification.\nReference\nDisplays the specification reference of the panel which is populated from the Spec, Panel fields.\nSpec\nInput a value in the field or select a specification from the drop-down list to modify the panel specification.\nWhen a specification is selected, the panel drop-down list is populated with the components that were used when the specification was most recently selected.\nPanel\nInput a value in the field or select a panel from the drop-down list to modify the panel component type.\nThe thickness drop-down list is populated with the component type thickness.\nThickness\nAllows you to view the thickness of the currently selected panel.\nMaterial\nInput a value in the field or select a justification from the drop-down list to modify the panel justification position.\nFor example, select Top from the drop-down list to modify the justification position of the panel to top.\nSurface justification\nInput a value in the field or select a justification from the drop-down list to modify the panel justification position.\nFor example, select Top from the drop-down list to modify the justification position of the panel to top.\nDesign\nDrawing level\nInput a value in the field to modify the drawing level of the panel. Refer to Component Visibility, Drawing Level and Obstruction for further information.\nAlternatively, click the field and click to display the Int32 Collection Editor window. Refer to Modify Drawing Level for further information.\nClasher\nObstruction level\nSelect from the drop-down list to modify the obstruction level of the currently selected panel. Refer to Component Visibility, Drawing Level and Obstruction for further information.\nSpecification\n\nClassification\nInput a value in the field or select a classification from the drop-down list to modify the panel classification.\nReference\nDisplays the specification reference of the panel which is populated from the Spec, Panel fields.\nSpec\nInput a value in the field or select a specification from the drop-down list to modify the panel specification.\nWhen a specification is selected, the panel drop-down list is populated with the components that were used when the specification was most recently selected.\nPanel\nInput a value in the field or select a panel from the drop-down list to modify the panel component type.\nThe thickness drop-down list is populated with the component type thickness.\nThickness\nAllows you to view the thickness of the currently selected panel.\nMaterial\nInput a value in the field or select a justification from the drop-down list to modify the panel justification position.\nFor example, select Top from the drop-down list to modify the justification position of the panel to top.\nSurface justification\nInput a value in the field or select a justification from the drop-down list to modify the panel justification position.\nFor example, select Top from the drop-down list to modify the justification position of the panel to top.\nDesign\n\nDrawing level\nInput a value in the field to modify the drawing level of the panel. Refer to Component Visibility, Drawing Level and Obstruction for further information.\nAlternatively, click the field and click to display the Int32 Collection Editor window. Refer to Modify Drawing Level for further information.\nClasher\n\nObstruction level\nSelect from the drop-down list to modify the obstruction level of the currently selected panel. Refer to Component Visibility, Drawing Level and Obstruction for further information.\n\nSpecification\nClassification\nInput a value in the field or select a classification from the drop-down list to modify the panel classification.\nReference\nDisplays the specification reference of the panel which is populated from the Spec, Panel fields.\nSpec\nInput a value in the field or select a specification from the drop-down list to modify the panel specification.\nWhen a specification is selected, the panel drop-down list is populated with the components that were used when the specification was most recently selected.\nPanel\nInput a value in the field or select a panel from the drop-down list to modify the panel component type.\nThe thickness drop-down list is populated with the component type thickness.\nThickness\nAllows you to view the thickness of the currently selected panel.\nMaterial\nInput a value in the field or select a justification from the drop-down list to modify the panel justification position.\nFor example, select Top from the drop-down list to modify the justification position of the panel to top.\nSurface justification\nInput a value in the field or select a justification from the drop-down list to modify the panel justification position.\nFor example, select Top from the drop-down list to modify the justification position of the panel to top.\nDesign\nDrawing level\nInput a value in the field to modify the drawing level of the panel. Refer to Component Visibility, Drawing Level and Obstruction for further information.\nAlternatively, click the field and click to display the Int32 Collection Editor window. Refer to Modify Drawing Level for further information.\nClasher\nObstruction level\nSelect from the drop-down list to modify the obstruction level of the currently selected panel. Refer to Component Visibility, Drawing Level and Obstruction for further information.\n\n\n\nProperties\nModify Section Properties\nComponent Visibility, Drawing Level and Obstruction\nModify Drawing Level\nComponent Visibility, Drawing Level and Obstruction\nProperties\nProperties\nModify Section Properties\nSpecification\nClassification\nReference\nSpec\nPanel\nSpec\nPanel\nThickness\nMaterial\nSurface justification\nDesign\nDrawing level\nComponent Visibility, Drawing Level and Obstruction\nInt32 Collection Editor\nModify Drawing Level\nClasher\nObstruction level\nComponent Visibility, Drawing Level and Obstruction"}
{"Headers": "Modify Drawing Level", "Content": "The Int32 Collection Editor window allows you to modify the drawing level properties of the currently selected panel which affects the way elements are displayed in the 3D view and how they are dealt with when checking for clashes between design elements.\n\nThe Int32 Collection Editor window allows you to add, remove and modify the drawing level members and their values.\nThe list of available Members displays the drawing level members for the currently selected panel.\nClick to move the currently selected member up one position.\nClick to move the currently selected member down one position.\nAdd\nClick to add a member to the list of available Members.\nRemove\nClick to delete a member from the list of available Members.\n\nClick to move the currently selected member up one position.\n\nClick to move the currently selected member down one position.\nAdd\nClick to add a member to the list of available Members.\nRemove\nClick to delete a member from the list of available Members.\nThe list of available Properties displays the editable properties for the currently selected member.\nYou can define the view for the list of available Properties and modify property values.\nCategorized\nClick to list the properties by category.\nAlphabetical\nClick to list the properties alphabetically.\nValue\nInput a drawing level value to define the drawing level. Refer to Component Visibility, Drawing Level and Obstruction for further information.\n\nCategorized\nClick to list the properties by category.\n\nAlphabetical\nClick to list the properties alphabetically.\n\nValue\nInput a drawing level value to define the drawing level. Refer to Component Visibility, Drawing Level and Obstruction for further information.\nClick OK to apply the drawing level properties or Cancel to discard any changes and close the Int32 Collection Editor window.\nClick to move the currently selected member up one position.\nClick to move the currently selected member down one position.\nAdd\nClick to add a member to the list of available Members.\nRemove\nClick to delete a member from the list of available Members.\nCategorized\nClick to list the properties by category.\nAlphabetical\nClick to list the properties alphabetically.\nValue\nInput a drawing level value to define the drawing level. Refer to Component Visibility, Drawing Level and Obstruction for further information.\n\n\n\nComponent Visibility, Drawing Level and Obstruction\nInt32 Collection Editor\nInt32 Collection Editor\nAdd\nRemove\nCategorized\nAlphabetical\nValue\nComponent Visibility, Drawing Level and Obstruction\nOK\nCancel\nInt32 Collection Editor"}
{"Headers": "Modify Panel Loop Properties", "Content": "The panel loop properties of selected panels can be modified using the Properties window. Refer to Properties for further information.\n\nThe properties of the PLOO element can be modified to change a number of settings.\nThe general properties of PLOO elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.\nThe specification properties of PLOO elements are identical to PANE properties. Refer to Modify Panel Properties for further information.\nGeometry\nHeight\nInput dimensional values in the field to explicitly modify the height (thickness) of the panel.\nThe height is also indicated on the Thickness property of the owning PANE element.\nGeometry\n\nHeight\nInput dimensional values in the field to explicitly modify the height (thickness) of the panel.\nThe height is also indicated on the Thickness property of the owning PANE element.\n\nGeometry\nHeight\nInput dimensional values in the field to explicitly modify the height (thickness) of the panel.\nThe height is also indicated on the Thickness property of the owning PANE element.\n\n\n\nProperties\nModify Section Properties\nModify Panel Properties\nProperties\nProperties\nModify Section Properties\nModify Panel Properties\nGeometry\nHeight\nThickness"}
{"Headers": "Modify Panel Vertex Properties", "Content": "The panel vertex properties of selected panels can be modified using the Properties window. Refer to Properties for further information.\n\nThe properties of the PAVE element can be modified to change a number of settings.\nThe general and positional properties of PAVE elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.\nDesign\nFillet radius\nInput a dimensional value in the field to modify the fillet radius for the panel vertex.\nDesign\n\nFillet radius\nInput a dimensional value in the field to modify the fillet radius for the panel vertex.\n\nDesign\nFillet radius\nInput a dimensional value in the field to modify the fillet radius for the panel vertex.\n\n\n\nProperties\nModify Section Properties\nProperties\nProperties\nModify Section Properties\nDesign\nFillet radius"}
{"Headers": "Modify Panel Fitting", "Content": "Modifies the catalogue specification associated with each panel fitting.\nModify Fitting Specification\nModifies the fitting specification.\nYou are prompted to Select panel(s)\nClick to identify the panels that contain fittings to be modified and press Enter. The fittings are highlighted in the 3D view, each fitting displays as a fitting pin.\n\nThe selection status of the each fitting is indicated by the fitting pin colour.\nYou are then prompted to Select fittings\nClick to identify the fittings to be modified and press Enter to display the Panel Fitting window.\n\nThe functionality of the Panel Fitting window is explained, with the exception of the Selection part of the window. Refer to Create Section Fitting for further information.\nSelection\nClick to remove all fittings from the current selection.\nThe number of currently selected fittings displays adjacent to the icon.\n\nSelection\nClick to remove all fittings from the current selection.\nThe number of currently selected fittings displays adjacent to the icon.\nClick Apply to accept the fitting component settings.\nYou are prompted to Set specification\nPress Enter to associate the fitting specification with the currently selected fittings.\n\nSelection\nClick to remove all fittings from the current selection.\nThe number of currently selected fittings displays adjacent to the icon.\nPink = Not selected\nRed = Selected.\nPink = Not selected\nPink = Not selected\nRed = Selected.\nRed = Selected.\nNote: The prompt does not display if the panel elements are already selected.\n\n\n\nCreate Section Fitting\nModify Fitting Specification\nSelect panel(s)\nNote\n:\nEnter\nSelect fittings\nEnter\nPanel Fitting\nPanel Fitting\nSelection\nCreate Section Fitting\nSelection\nApply\nSet specification\nEnter"}
{"Headers": "Modify Panel Fitting Properties", "Content": "The properties of selected fittings can be modified using the Properties window. Refer to Properties for further information.\n\nThe general and positional properties of PFIT elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.\nSpecification\nSurface justification\nInput a value in the field or select a justification from the drop-down list to modify the fitting justification position.\nFor example, select Top outward from the drop-down list to modify the justification position of the fitting to top outward.\nReference\nDisplays the specification reference of the fitting which is populated from the Spec, Sub-type and Fitting fields.\nSpec\nInput a value in the field or select a specification from the drop-down list to modify the fitting specification.\nWhen a specification is selected, the type and fitting drop-down lists are populated with the components that were used when the specification was most recently selected.\nSub-type\nInput a value in the field or select a sub-type from the drop-down list to modify the fitting sub-type.\nThe sub-type drop-down list is populated with the fitting sub-types that are associated with the currently selected specification.\nFitting\nInput a value in the field or select a fitting from the drop-down list to modify the panel fitting.\nThe fitting drop-down list is populated with the fitting types that are associated with the currently selected specification.\nMaterial\nInput a value in the field or select a material from the drop-down list to modify the fitting material.\nThe material drop-down list is populated with the materials that are associated with the currently selected specification.\nSpecification\n\nSurface justification\nInput a value in the field or select a justification from the drop-down list to modify the fitting justification position.\nFor example, select Top outward from the drop-down list to modify the justification position of the fitting to top outward.\nReference\nDisplays the specification reference of the fitting which is populated from the Spec, Sub-type and Fitting fields.\nSpec\nInput a value in the field or select a specification from the drop-down list to modify the fitting specification.\nWhen a specification is selected, the type and fitting drop-down lists are populated with the components that were used when the specification was most recently selected.\nSub-type\nInput a value in the field or select a sub-type from the drop-down list to modify the fitting sub-type.\nThe sub-type drop-down list is populated with the fitting sub-types that are associated with the currently selected specification.\nFitting\nInput a value in the field or select a fitting from the drop-down list to modify the panel fitting.\nThe fitting drop-down list is populated with the fitting types that are associated with the currently selected specification.\nMaterial\nInput a value in the field or select a material from the drop-down list to modify the fitting material.\nThe material drop-down list is populated with the materials that are associated with the currently selected specification.\n\nSpecification\nSurface justification\nInput a value in the field or select a justification from the drop-down list to modify the fitting justification position.\nFor example, select Top outward from the drop-down list to modify the justification position of the fitting to top outward.\nReference\nDisplays the specification reference of the fitting which is populated from the Spec, Sub-type and Fitting fields.\nSpec\nInput a value in the field or select a specification from the drop-down list to modify the fitting specification.\nWhen a specification is selected, the type and fitting drop-down lists are populated with the components that were used when the specification was most recently selected.\nSub-type\nInput a value in the field or select a sub-type from the drop-down list to modify the fitting sub-type.\nThe sub-type drop-down list is populated with the fitting sub-types that are associated with the currently selected specification.\nFitting\nInput a value in the field or select a fitting from the drop-down list to modify the panel fitting.\nThe fitting drop-down list is populated with the fitting types that are associated with the currently selected specification.\nMaterial\nInput a value in the field or select a material from the drop-down list to modify the fitting material.\nThe material drop-down list is populated with the materials that are associated with the currently selected specification.\n\n\n\nProperties\nModify Section Properties\nProperties\nProperties\nModify Section Properties\nSpecification\nSurface justification\nReference\nSpec\nSub-type\nFitting\nSpec\nSub-type\nFitting\nMaterial"}
{"Headers": "Navigator PowerWheel\u2122", "Content": "Use the navigation functionality to navigate through the selected panel element hierarchy.\n\n\n\n"}
{"Headers": "Merge Panels", "Content": "Merges two coplanar panels, regardless of specification, justification or beta angle.\nIf the panels are not coplanar, a Warning message displays on the status bar.\nThe properties of the merged panels are inherited from the first picked panel.\nWhen panels are merged, no connections are made between the merged items. However, any existing welds (that might be referencing other unrelated elements) under both panels are grouped together under the merged panel.\nYou are prompted to Select first element to merge\nClick to identify the first panel to merge.\nYou are then prompted to Select next Panel to merge\nClick to identify the second panel to merge.\nYou are then prompted to Select next Panel to merge or <Finish>\nThe prompt is repeated, allowing you to select multiple panels.\nInput F at the prompt and press Enter to end the command. The panels are merged.\nThroughout the merge process you can press ESC to cancel the command. Additional functionality is also available.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nFinish\nPress the down arrow key and select Finish to end the command.\n\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nSelect first element to merge\nSelect next Panel to merge\nSelect next Panel to merge or <Finish>\nF\nEnter\nESC\nFinish\nFinish"}
{"Headers": "Expand/Contract Panel", "Content": "Expands/contracts a panel outline using a specified offset value.\n\n\n"}
{"Headers": "Expand/Contract Complete Panel", "Content": "Expands/contracts the complete panel.\nYou are prompted to Pick panel\nClick to identify the panel to expand/contract.\nYou are then prompted to Define the offset distance: or <Select Vertices>\nInput a dimensional value in the field and press Enter or click to identify the expansion/contraction position.\nThe panel is expanded/contracted.\nThroughout the expand/contract process you can press ESC to cancel the command. Additional functionality is also available.\nSelect Vertices\nPress the down arrow key and select Select Vertices to expand/contract selected panel vertices. Refer to Expand/Contract Selected Panel Vertices for further information.\n\nSelect Vertices\nPress the down arrow key and select Select Vertices to expand/contract selected panel vertices. Refer to Expand/Contract Selected Panel Vertices for further information.\n\nSelect Vertices\nPress the down arrow key and select Select Vertices to expand/contract selected panel vertices. Refer to Expand/Contract Selected Panel Vertices for further information.\nNote:\nThe prompt does not display if the panel element is already selected.\n\n\n\nExpand/Contract Selected Panel Vertices\nPick panel\nNote\n:\nDefine the offset distance: or <Select Vertices>\nEnter\nESC\nSelect Vertices\nSelect Vertices\nExpand/Contract Selected Panel Vertices"}
{"Headers": "Expand/Contract Selected Panel Vertices", "Content": "Expands/contracts selected panel vertices by creating a polygon that selects the vertices contained within it.\nYou are prompted to Pick panel\nClick to identify the panel to expand/contract.\nYou are then prompted to Define the offset distance: or <Select Vertices>\nInput S at the prompt and press Enter to define the polygon vertex points.\nYou are then prompted to Pick the first polygon vertex or <All>\nClick to identify the first polygon point.\nYou are then prompted to Pick next polygon vertex or\nClick to identify the next polygon point.\nYou are then prompted to Pick next polygon vertex or <Close>\nThe prompt is repeated, allowing you to identify multiple polygon points.\nInput C at the prompt and press Enter to create the polygon. The panel vertices that are contained within the polygon are selected.\nYou are then prompted to Define the offset distance: or <Select Vertices>\nInput a dimensional value in the field and press Enter or click to identify the expansion/contraction position.\nThe panel is expanded/contracted.\nThroughout the expand/contract process you can press ESC to cancel the command. Additional functionality is also available.\nAll\nPress the down arrow key and select All to expand/contract the complete panel. Refer to Expand/Contract Complete Panel for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nSelect Vertices\nPress the down arrow key and select Select Vertices to create a polygon that selects the panel vertices contained within it.\nClose\nPress the down arrow key and select Close to create the polygon. The panel vertices that are contained within the polygon are selected.\n\nAll\nPress the down arrow key and select All to expand/contract the complete panel. Refer to Expand/Contract Complete Panel for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nSelect Vertices\nPress the down arrow key and select Select Vertices to create a polygon that selects the panel vertices contained within it.\nClose\nPress the down arrow key and select Close to create the polygon. The panel vertices that are contained within the polygon are selected.\n\nAll\nPress the down arrow key and select All to expand/contract the complete panel. Refer to Expand/Contract Complete Panel for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nSelect Vertices\nPress the down arrow key and select Select Vertices to create a polygon that selects the panel vertices contained within it.\nClose\nPress the down arrow key and select Close to create the polygon. The panel vertices that are contained within the polygon are selected.\nNote:\nThe prompt does not display if the panel element is already selected.\n\n\n\nExpand/Contract Complete Panel\nPick panel\nNote\n:\nDefine the offset distance: or <Select Vertices>\nS\nEnter\nPick the first polygon vertex or <All>\nPick next polygon vertex or\nPick next polygon vertex or <Close>\nC\nEnter\nDefine the offset distance: or <Select Vertices>\nEnter\nESC\nAll\nAll\nExpand/Contract Complete Panel\nBack\nBack\nSelect Vertices\nClose\nClose"}
{"Headers": "Panel Origin", "Content": "Modifies the panel origin vertex position.\nWhen creating a panel the Origin is placed at the first vertex by default and the X and Y co-ordinates of all other vertices in the panel relate to this position. The coordinates of all vertices owned by the current panel loop are recalculated relative to the new origin such that their positions in the 3D model remain unchanged.\nYou are prompted to Pick near vertex for new origin\nClick to identify the panel origin vertex point.\n\n\n\nOrigin\nX\nY\nPick near vertex for new origin"}
{"Headers": "Drawing Edges", "Content": "Modifies the drawing edge display for panel elements.\n\nThe functionality available on the Drawing Edge Representation window is identical to that from the Drawing Edge Defaults window. Refer to Drawing Edge Defaults for further information.\n\n\n\nDrawing Edge Defaults\nDrawing Edge Representation\nDrawing Edge Defaults\nDrawing Edge Defaults"}
{"Headers": "Extend Panel Edge", "Content": "Extends panel edges to a panel edge, section edge or panel surface.\nNote:\nIf the automatic weld creation functionality is enabled, a connection is made between the two items and a weld is created.\n\n\n\nNote\n:"}
{"Headers": "Extend Single Panel Edge", "Content": "Extends a single panel edge to a panel or section edge. If the vertices describing the edge do not align with the selected item, they are modified to align. Other edges adjacent to the selected edge remain at their previous locations.\n\nThe example displays a single panel edge extension to a panel.\n\nYou are prompted to Select edge of panel or\nClick to identify the panel edge to extend.\nYou are then prompted to Pick Section to extend to or\nInput E at the prompt and press Enter to extend to a single panel edge.\nYou are then prompted to Pick edge of panel to extend to or\nClick to identify the panel edge to extend to.\nYou are then prompted to Specify gap value <#>\nInput a dimensional value in the field and press Enter to set the gap between the panels.\nThe panel edge is extended.\nThroughout the extend process you can press ESC to cancel the command. Additional functionality is also available.\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge. Refer to Extend Multiple Panel Edges for further information.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge. Refer to Drag Multiple Panel Edges for further information.\nSIngle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel surface. Refer to Extend Panel Edge to Panel Surface for further information.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge. Refer to Extend Multiple Panel Edges for further information.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge. Refer to Drag Multiple Panel Edges for further information.\nSIngle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel surface. Refer to Extend Panel Edge to Panel Surface for further information.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge. Refer to Extend Multiple Panel Edges for further information.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge. Refer to Drag Multiple Panel Edges for further information.\nSIngle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel surface. Refer to Extend Panel Edge to Panel Surface for further information.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\n\n\nExtend Multiple Panel Edges\nDrag Multiple Panel Edges\nExtend Panel Edge to Panel Surface\nSelect edge of panel or\nPick Section to extend to or\nE\nEnter\nPick edge of panel to extend to or\nSpecify gap value <#>\nEnter\nESC\nMultiple Edges\nMultiple Edges\nExtend Multiple Panel Edges\nDrag Multiple\nDrag Multiple\nDrag Multiple Panel Edges\nSIngle Edge\nSingle Edge\nEdge of panel\nEdge of panel\nSurface of panel\nSurface of panel\nExtend Panel Edge to Panel Surface\nSection\nSection"}
{"Headers": "Extend Multiple Panel Edges", "Content": "Extends selected panel edges to a panel or section edge. If the vertices describing the edges do not align with the selected item, they are modified to align. Relative geometry between the selected edges is not maintained.\n\nThe example displays a multiple panel edge extension to a section.\n\nYou are prompted to Select edge of panel or\nInput M at the prompt and press Enter to extend multiple panel edges.\nYou are then prompted to Select start vertex or\nClick to identify the start vertex to extend.\nYou are then prompted to Select end vertex or\nClick to identify the end vertex to extend.\nYou are then prompted to Select vertex between start and end or\nClick to identify the through vertex to extend.\nYou are then prompted to Pick Section to extend to or\nClick to identify the section to extend to.\nYou are them prompted to Select P-Line\nClick to identify the section P-line to extend to.\nYou are then prompted to Specify gap value <#>\nInput a dimensional value in the field and press Enter to set the gap between the panel and section.\nThe panel edges are extended.\nThroughout the extend process you can press ESC to cancel the command. Additional functionality is also available.\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge. Refer to Drag Multiple Panel Edges for further information.\nSingle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge. Refer to Extend Single Panel Edge for further information.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel surface. Refer to Extend Panel Edge to Panel Surface for further information.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge. Refer to Drag Multiple Panel Edges for further information.\nSingle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge. Refer to Extend Single Panel Edge for further information.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel surface. Refer to Extend Panel Edge to Panel Surface for further information.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge. Refer to Drag Multiple Panel Edges for further information.\nSingle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge. Refer to Extend Single Panel Edge for further information.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel surface. Refer to Extend Panel Edge to Panel Surface for further information.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\n\n\nDrag Multiple Panel Edges\nExtend Single Panel Edge\nExtend Panel Edge to Panel Surface\nSelect edge of panel or\nM\nEnter\nSelect start vertex or\nSelect end vertex or\nSelect vertex between start and end or\nPick Section to extend to or\nSelect P-Line\nSpecify gap value <#>\nEnter\nESC\nMultiple Edges\nMultiple Edges\nDrag Multiple\nDrag Multiple\nDrag Multiple Panel Edges\nSingle Edge\nSingle Edge\nExtend Single Panel Edge\nEdge of panel\nEdge of panel\nSurface of panel\nSurface of panel\nExtend Panel Edge to Panel Surface\nSection\nSection"}
{"Headers": "Drag Multiple Panel Edges", "Content": "Drags selected panel edges to a panel or section edge, the nearest edge connects to the selected item but maintains the relative geometry of the selected edges.\n\nThe example displays a dragged panel edge extension to a panel.\n\nYou are prompted to Select edge of panel or\nInput D at the prompt and press Enter to drag multiple panel edges.\nYou are then prompted to Select start vertex or\nClick to identify the start vertex to extend.\nYou are then prompted to Select end vertex or\nClick to identify the end vertex to extend.\nYou are then prompted to Select vertex between start and end or\nClick to identify the through vertex to extend.\nYou are then prompted to Pick Section to extend to or\nInput E at the prompt and press Enter to extend to a single panel edge.\nYou are then prompted to Pick edge of panel to extend to or\nClick to identify the panel edge to extend to.\nYou are then prompted to Specify gap value <#>\nInput a dimensional value in the field and press Enter to set the gap between the panels.\nThe panel edges are extended.\nThroughout the extend process you can press ESC to cancel the command. Additional functionality is also available.\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge. Refer to Extend Multiple Panel Edges for further information.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge.\nSingle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge. Refer to Extend Single Panel Edge for further information.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel surface. Refer to Extend Panel Edge to Panel Surface for further information.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge. Refer to Extend Multiple Panel Edges for further information.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge.\nSingle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge. Refer to Extend Single Panel Edge for further information.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel surface. Refer to Extend Panel Edge to Panel Surface for further information.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge. Refer to Extend Multiple Panel Edges for further information.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge.\nSingle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge. Refer to Extend Single Panel Edge for further information.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel surface. Refer to Extend Panel Edge to Panel Surface for further information.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\n\n\nExtend Multiple Panel Edges\nExtend Single Panel Edge\nExtend Panel Edge to Panel Surface\nSelect edge of panel or\nD\nEnter\nSelect start vertex or\nSelect end vertex or\nSelect vertex between start and end or\nPick Section to extend to or\nE\nEnter\nPick edge of panel to extend to or\nSpecify gap value <#>\nEnter\nESC\nMultiple Edges\nMultiple Edges\nExtend Multiple Panel Edges\nDrag Multiple\nDrag Multiple\nSingle Edge\nSingle Edge\nExtend Single Panel Edge\nEdge of panel\nEdge of panel\nSurface of panel\nSurface of panel\nExtend Panel Edge to Panel Surface\nSection\nSection"}
{"Headers": "Extend Panel Edge to Panel Surface", "Content": "Extends single or multiple panel edges to a panel surface.\nThe example displays a single panel edge extension to a panel surface.\n\nYou are prompted to Select edge of panel or\nClick to identify the panel edge to extend.\nYou are then prompted to Pick Section to extend to or\nInput P at the prompt and press Enter to extend a single panel edge to a panel surface.\nYou are then prompted to Pick surface of panel to extend to or\nClick to identify the panel edge to extend to.\nYou are then prompted to Specify gap value <#>\nInput a dimensional value in the field and press Enter to set the gap between the panels.\nThe panel edge is extended.\nThroughout the extend process you can press ESC to cancel the command. Additional functionality is also available.\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge. Refer to Extend Multiple Panel Edges for further information.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge. Refer to Drag Multiple Panel Edges for further information.\nSingle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge. Refer to Extend Single Panel Edge for further information.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge. Refer to Extend Multiple Panel Edges for further information.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge. Refer to Drag Multiple Panel Edges for further information.\nSingle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge. Refer to Extend Single Panel Edge for further information.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\nRefer to Create Panel Welds further information.\nMultiple Edges\nPress the down arrow key and select Multiple Edges to extend selected panel edges to a panel or section edge. Refer to Extend Multiple Panel Edges for further information.\nDrag Multiple\nPress the down arrow key and select Drag Multiple to drag selected panel edges to a panel or section edge. Refer to Drag Multiple Panel Edges for further information.\nSingle Edge\nPress the down arrow key and select Single Edge to extend a single panel edge to a panel or section edge. Refer to Extend Single Panel Edge for further information.\nEdge of panel\nPress the down arrow key and select Edge of panel to extend single or multiple panel edges to a panel edge.\nSurface of panel\nPress the down arrow key and select Surface of panel to extend single or multiple panel edges to a panel.\nSection\nPress the down arrow key and select Section to extend single or multiple panel edges to a section.\n\n\n\nExtend Multiple Panel Edges\nDrag Multiple Panel Edges\nExtend Single Panel Edge\nCreate Panel Welds\nSelect edge of panel or\nPick Section to extend to or\nP\nEnter\nPick surface of panel to extend to or\nSpecify gap value <#>\nEnter\nESC\nMultiple Edges\nMultiple Edges\nExtend Multiple Panel Edges\nDrag Multiple\nDrag Multiple\nDrag Multiple Panel Edges\nSingle Edge\nSingle Edge\nExtend Single Panel Edge\nEdge of panel\nEdge of panel\nSurface of panel\nSurface of panel\nSection\nSection\nCreate Panel Welds"}
{"Headers": "Bounded Plate Health Checker", "Content": "Checks the status of bounded plates. If applicable, you can update or repair them as well as remove connectivity.\nAfter the health check is carried out, the results can be displayed on the screen or exported to an excel file.\nThe Bounded Plate Health Checker window is populated with the currently selected bounded plates. By default, the health check is carried out when the window is opened or when a bounded plate is added.\n\nThe Bounded Plates tab displays the health check results.\nHighlight\nIndicates the currently selected bounded plate when highlight mode is on.\nName\nDisplays the name of the bounded plate.\nStatus\nDisplays the health check status of the bounded plate.\nPass\nThe bounded plate has passed the health check and no further action is required.\nWarning\nThe bounded plate has failed the health check and has a fixable issue. For example, a change to the plate geometry.\nClick Update or Reset Selection to resolve the issue.\nFail\nThe bounded plate has failed the health check and the issue cannot be fixed using Update or Reset Selection. For example a bounding element has been deleted which is deemed permanent and deliberate.\nClick Remove Connectivity to make the plate unbounded.\nComment\nDisplays a brief description of the bounded plate status.\nHighlight\n\nIndicates the currently selected bounded plate when highlight mode is on.\nName\n\nDisplays the name of the bounded plate.\nStatus\n\nDisplays the health check status of the bounded plate.\nPass\n\nThe bounded plate has passed the health check and no further action is required.\nWarning\n\nThe bounded plate has failed the health check and has a fixable issue. For example, a change to the plate geometry.\nClick Update or Reset Selection to resolve the issue.\nFail\n\nThe bounded plate has failed the health check and the issue cannot be fixed using Update or Reset Selection. For example a bounding element has been deleted which is deemed permanent and deliberate.\nClick Remove Connectivity to make the plate unbounded.\nComment\n\nDisplays a brief description of the bounded plate status.\nRight-click on the bounded plate list to display a drop-down menu.\n\nExports the bounded plate list to an Excel file. Click to display the Save As window. Navigate to a location and name the exported Excel file.\nClick to display the bounded plate list in the Print Preview window.\nThe right hand side of the Bounded Plate Health Checker window allows you to select and modify the bounded plates.\nAdd CE\nReplaces the bounded plate list with the currently selected bounded plate in the 3D view.\nAdd Selection\nReplaces the bounded plate list with the current selection of bounded plates in the 3D view.\nNavigate to Selected\nZooms to the currently selected bounded plate in the 3D view.\nHighlight Mode\nClick to turn highlight mode on or off. If highlight mode is on, the currently selected bounded plate is highlighted in the 3D view.\nUpdate or Reset Selection\nClick Update or Reset Selection to resolve an issue with the currently selected bounded plate. The bounded plate is either updated to a new shape or reset back to the original shape, depending on the issue.\nThe functionality is only available when a bounded plate with a warning status is selected.\nRemove Connectivity\nClick Remove Connectivity to make the currently selected plate unbounded, the STCSET is deleted and the bounded plate is removed from the Bounded Plate Health Checker window. The bounded plate becomes a regular panel.\n\nAdd CE\nReplaces the bounded plate list with the currently selected bounded plate in the 3D view.\n\nAdd Selection\nReplaces the bounded plate list with the current selection of bounded plates in the 3D view.\n\nNavigate to Selected\nZooms to the currently selected bounded plate in the 3D view.\n\nHighlight Mode\nClick to turn highlight mode on or off. If highlight mode is on, the currently selected bounded plate is highlighted in the 3D view.\n\nUpdate or Reset Selection\nClick Update or Reset Selection to resolve an issue with the currently selected bounded plate. The bounded plate is either updated to a new shape or reset back to the original shape, depending on the issue.\nThe functionality is only available when a bounded plate with a warning status is selected.\n\nRemove Connectivity\nClick Remove Connectivity to make the currently selected plate unbounded, the STCSET is deleted and the bounded plate is removed from the Bounded Plate Health Checker window. The bounded plate becomes a regular panel.\nWhen a bounded plate, notching element or the plate bounding elements are modified, the status may change to warning when a health check is carried out. There are various modification scenarios which result in a warning which can be fixed.\nModified Panel Geometry\nThe geometry of the panel is modified using a grip.\n\nThe warning message displays with the comment Panel geometry has changed\nClick Update or Reset Selection to reset the panel back to the original geometry.\n\nModified Panel Orientation\nThe orientation of the panel is changed using the ROTATE in canvas command.\n\nThe warning message displays with the comment Panel orientation altered\nClick Update or Reset Selection to reset the panel back to the original orientation.\n\nPanel Moved out of Reference Plane\nThe panel is moved away from the reference plane.\n\nThe warning message displays with the comment Panel moved out of reference plane\nClick Update or Reset Selection to reset the panel back to the original position.\n\nMoved Notching Element\nThe notching element is moved to a different position.\n\nThe warning message displays with the comment Notching element has been modified\nClick Update or Reset Selection to move the panel notching to the correct position around the notching element.\n\nModified Notching Element Size\nThe size of the notching element is modified.\n\nThe warning message displays with the comment Notching element has been modified\nClick Update or Reset Selection to modify the panel notching to the correct size around the notching element.\n\nNotching Element Moved out of Reference Plane\nThe notching element is moved away from the reference plane.\n\nThe warning message displays with the comment Position of bonding condition has changed\nClick Update or Reset Selection to delete the notching from the panel.\n\nDeleted Notching Element\nThe notching element is deleted.\n\nThe warning message displays with the comment Notching element is missing\nClick Update or Reset Selection to delete the notching from the panel.\n\nMoved Bounding Elements\nBounding elements are moved to a different position.\n\nThe warning message displays with the comment Position of bounding condition has changed\nClick Update or Reset Selection to reset the panel back to the original position.\n\nSplit Bounding Elements\nBounding elements are split.\n\nThe warning message displays with the comment Bounding conditions have changed\nClick Update or Reset Selection to correct the bounding conditions.\nSplit Bounded Plate Plane Intersects with different Bounding Element\nThe split plane of a split bounded plate intersects with a different bounding element as a result of moving a bounding element to a different position.\n\nThe fail message displays with the comment Bounding structure is not closed\nDeleted Split Bounded Plate Element\nA bounded element is deleted that is part of a split bounded plate.\n\nThe fail message displays with the comment Bounding element is missing\nRefer to Create Bounded Plate, Split Section, Panel or Bounded Plate and Non-Routed Item for further information.\nHighlight\nIndicates the currently selected bounded plate when highlight mode is on.\nName\nDisplays the name of the bounded plate.\nStatus\nDisplays the health check status of the bounded plate.\nPass\nThe bounded plate has passed the health check and no further action is required.\nWarning\nThe bounded plate has failed the health check and has a fixable issue. For example, a change to the plate geometry.\nClick Update or Reset Selection to resolve the issue.\nFail\nThe bounded plate has failed the health check and the issue cannot be fixed using Update or Reset Selection. For example a bounding element has been deleted which is deemed permanent and deliberate.\nClick Remove Connectivity to make the plate unbounded.\nComment\nDisplays a brief description of the bounded plate status.\nExport to Excel\nExports the bounded plate list to an Excel file. Click to display the Save As window. Navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the bounded plate list in the Print Preview window.\nAdd CE\nReplaces the bounded plate list with the currently selected bounded plate in the 3D view.\nAdd Selection\nReplaces the bounded plate list with the current selection of bounded plates in the 3D view.\nNavigate to Selected\nZooms to the currently selected bounded plate in the 3D view.\nHighlight Mode\nClick to turn highlight mode on or off. If highlight mode is on, the currently selected bounded plate is highlighted in the 3D view.\nUpdate or Reset Selection\nClick Update or Reset Selection to resolve an issue with the currently selected bounded plate. The bounded plate is either updated to a new shape or reset back to the original shape, depending on the issue.\nThe functionality is only available when a bounded plate with a warning status is selected.\nRemove Connectivity\nClick Remove Connectivity to make the currently selected plate unbounded, the STCSET is deleted and the bounded plate is removed from the Bounded Plate Health Checker window. The bounded plate becomes a regular panel.\n\n\n\nCreate Bounded Plate\nSplit Section, Panel or Bounded Plate\nNon-Routed Item\nBounded Plate Health Checker\nBounded Plates\nHighlight\nName\nStatus\nPass\nWarning\nUpdate or Reset Selection\nFail\nUpdate or Reset Selection\nRemove Connectivity\nComment\nExport to Excel\nSave As\nPrint Preview\nPrint Preview\nBounded Plate Health Checker\nAdd CE\nAdd Selection\nNavigate to Selected\nHighlight Mode\nUpdate or Reset Selection\nUpdate or Reset Selection\nRemove Connectivity\nRemove Connectivity\nBounded Plate Health Checker\nModified Panel Geometry\nPanel geometry has changed\nUpdate or Reset Selection\nModified Panel Orientation\nROTATE\nPanel orientation altered\nUpdate or Reset Selection\nPanel Moved out of Reference Plane\nPanel moved out of reference plane\nUpdate or Reset Selection\nMoved Notching Element\nNotching element has been modified\nUpdate or Reset Selection\nModified Notching Element Size\nNotching element has been modified\nUpdate or Reset Selection\nNotching Element Moved out of Reference Plane\nPosition of bonding condition has changed\nUpdate or Reset Selection\nDeleted Notching Element\nNotching element is missing\nUpdate or Reset Selection\nMoved Bounding Elements\nPosition of bounding condition has changed\nUpdate or Reset Selection\nSplit Bounding Elements\nBounding conditions have changed\nUpdate or Reset Selection\nSplit Bounded Plate Plane Intersects with different Bounding Element\nBounding structure is not closed\nDeleted Split Bounded Plate Element\nBounding element is missing\nCreate Bounded Plate\nSplit Section, Panel or Bounded Plate\nNon-Routed Item"}
{"Headers": "View Panel Dimensions", "Content": "Displays panel dimension tags for the currently selected panel elements in the 3D view.\nRepeat the command to remove the dimension tags from the 3D view.\n\nIf the currently selected element is not a section or a panel, a user message displays indicating that the currently selected element cannot be dimensioned.\n\n\n\n"}
{"Headers": "Walls and Floors", "Content": "The Walls and Floors application allows you to create and modify walls, floors and screeds.Fittings can be specified and wall connections defined.\n\n\n"}
{"Headers": "Walls and Floors Settings", "Content": "Walls and Floors allows you to add walls floors and screeds to a structure that already exists.\n\n\n"}
{"Headers": "Default Wall and Floor Specifications", "Content": "Sets the default specification for the creation of walls and floors.\nBefore walls and floors can be designed as part of the overall 3D model, various options must be defined which determine, for example, the tolerances used for walls and floors during the design process.\n\n\n"}
{"Headers": "Floor Representation", "Content": "Modifies the level and obstruction which affect the way elements are displayed in the 3D view and how they are dealt with when checking for clashes between design elements.\n\n\n\n"}
{"Headers": "Floor Tolerances", "Content": "Modifies the tolerances (clearances) of floor elements to suit project/model requirements.\n\n\n\n"}
{"Headers": "Floor Specification", "Content": "Sets the floor/screed elements available for selection from the structural catalogue as determined by the default specification. The default specification defines properties such as material and cross-sectional profiles.\n\nCE\nClick to identify the currently selected element as the working element.\nSpecification\nClick to display all the available groups of floors/screeds covered by a specification.\nOnce a group of floors/screeds has been selected from the drop-down list, the list of available Specifications is populated.\nSelect a specification to be used as the default floor/screed specification from the list of available Specifications.\nThickness\nInput a dimensional value in the field to define the default fitness for floors/screeds.\nUse as default thickness\nThe check box is inactive for the Floor/Screed Specification (Default) window.\nCE\nClick to identify the currently selected element as the working element.\nSpecification\nClick to display all the available groups of floors/screeds covered by a specification.\nOnce a group of floors/screeds has been selected from the drop-down list, the list of available Specifications is populated.\nSelect a specification to be used as the default floor/screed specification from the list of available Specifications.\nThickness\nInput a dimensional value in the field to define the default fitness for floors/screeds.\nUse as default thickness\nThe check box is inactive for the Floor/Screed Specification (Default) window.\nClick Apply to define the floor/screed specification default.\nClick Cancel to discard any inputs and close the Floor/Screed Specification (Default) window.\nCE\nClick to identify the currently selected element as the working element.\nSpecification\nClick to display all the available groups of floors/screeds covered by a specification.\nOnce a group of floors/screeds has been selected from the drop-down list, the list of available Specifications is populated.\nSelect a specification to be used as the default floor/screed specification from the list of available Specifications.\nThickness\nInput a dimensional value in the field to define the default fitness for floors/screeds.\nUse as default thickness\nThe check box is inactive for the Floor/Screed Specification (Default) window.\n\n\n\nCE\nSpecification\nThickness\nUse as default thickness\nFloor/Screed Specification (Default)\nApply\nCancel\nFloor/Screed Specification (Default)"}
{"Headers": "Wall Tolerances", "Content": "Modifies the default tolerances for walls.\nWhen a joint which has one or more attached sections is repositioned, the effect on those sections depends upon whether or not the joint has been defined as dominant or subordinate, as defined by the setting of the joint\u2019s Joint Freedom (JFRE) attribute.\nThe standard default is for joints to be subordinate.\n\n\n\n"}
{"Headers": "Wall Cut Plane", "Content": "Specifies the start or end of the wall\u2019s cut plane with the use of selection functionality.\n\n\n\n"}
{"Headers": "Wall Specification", "Content": "Sets the wall elements available for selection from the structural catalogue as determined by the default specification. The default specification defines properties such as material and cross-sectional profiles\n\nSpecification Data\nUse the Specification Data part of the Wall Specification (Default) window to select any of the specifications from the catalogue.\nClick Specification to identify the current specification as the wall specification (default).\nFrom the Generic Type drop-down list, select a standard from the list of available standards, once the selection has been carried out the Generic Type part of the window is automatically populated the generic types from the catalogue.\nPline Settings\nUse the Pline Settings part of the Wall Specification (Default) window to modify the Pline settings, by default the settings are set as NA (neutral axis) (normal choice of justification setting in practice is NA).\nFrom the Justification drop-down list, select the justification from the available list, (justification determines the \u2018Setting out\u2019 position of the wall, that is the axis about which the geometry is offset).\nFrom the Member line drop-down list, select the member line from the available list (determines how walls are shown in wireline views and drawings).\nFrom the Joint Line drop-down list, select the joint line from the available list (determines the position of a joint relative to an attached section).\nOptions\nUse the checkboxes in the Options part of the Wall Specification (Default) window to re-trim all attached sections or use as the default profile.\nClick Properties to display the properties of the profile.\nClick Plotfile to display a graphical representation of the profile.\nClick Apply to use these settings as the new default, the current specification is updated.\nClick Dismiss to discard any information and close the Wall Specification (Default) window.\n\n\n\nSpecification Data\nSpecification Data\nWall Specification (Default)\nSpecification\nGeneric Type\nGeneric Type\nPline Settings\nPline Settings\nWall Specification (Default)\nJustification\nMember line\nJoint Line\nOptions\nOptions\nWall Specification (Default)\nProperties\nPlotfile\nApply\nDismiss\nWall Specification (Default)"}
{"Headers": "Administrative Hierarchy", "Content": "Below the zone in all applications under structures, have three administrative elements in common (these database elements are only available in the four applications) in this case the Walls and Floors application.\nHowever unique to the Walls and Floors application these administrative elements can be used as a means of organizing elements in the 3D model which represent the areas of the building. Refer to Building Levels for further information.\n\n\n\n\nBuilding Levels\nBuilding Levels"}
{"Headers": "Building Levels", "Content": "Creates/modifies the levels within a building and creates storage areas for elements.\n\nYou can create, modify or delete building levels and then associated storage areas. It is normal practice to create building levels (STR) and then associate storage areas to FRMW/SBFR elements.\nControl\nThe Control drop-down list allows you to identify the CE, refresh the window and close the window.\nCE\nClick to identify the currently selected element as the working element.\nA Confirm window displays:\nClick Yes to populate the Building Levels window with the details of the CE.\nOr\nClick No to discard any inputs.\nRefresh\nClick to refresh the Building Levels window.\nClose\nClick to close the Building Levels window.\nCE\nClick to identify the currently selected element as the working element.\nA Confirm window displays:\n\nClick Yes to populate the Building Levels window with the details of the CE.\nOr\nClick No to discard any inputs.\nRefresh\nClick to refresh the Building Levels window.\nClose\nClick to close the Building Levels window.\nSettings\nThe Settings drop-down list allows you to set/unset storage areas and define the datum to which all elevations are referenced to.\nUnset Storage Area\nBy default the setting is not applied which means storage areas are automatically set.\nWrt\nAllows you to define the datum to which the elevations are applied (elevations are absolute with respect to the datum).\nUnset Storage Area\nBy default the setting is not applied which means storage areas are automatically set.\nWrt\nAllows you to define the datum to which the elevations are applied (elevations are absolute with respect to the datum).\nCreate\nThe Create drop-down list allows you create a new building level element. Refer to Create Building Level for further information.\nModify\nThe Modify drop-down list allows you modify a building level element. Refer to Modify Building Level for further information.\nDelete\nThe delete drop-down list allows you to delete a building level element.\nLevel\nClick to delete the currently selected building level. A Confirm window displays.\nClick Yes to delete the selected building level.\nOr\nClick No to discard any inputs and close the Confirm window.\nLevel\nClick to delete the currently selected building level. A Confirm window displays.\n\nClick Yes to delete the selected building level.\nOr\nClick No to discard any inputs and close the Confirm window.\n\nCE\nClick to identify the currently selected element as the working element.\nA Confirm window displays:\nClick Yes to populate the Building Levels window with the details of the CE.\nOr\nClick No to discard any inputs.\nRefresh\nClick to refresh the Building Levels window.\nClose\nClick to close the Building Levels window.\nUnset Storage Area\nBy default the setting is not applied which means storage areas are automatically set.\nWrt\nAllows you to define the datum to which the elevations are applied (elevations are absolute with respect to the datum).\nLevel\nClick to delete the currently selected building level. A Confirm window displays.\nClick Yes to delete the selected building level.\nOr\nClick No to discard any inputs and close the Confirm window.\n\n\n\nCreate Building Level\nModify Building Level\nControl\nControl\nCE\nConfirm\nYes\nBuilding Levels\nNo\nRefresh\nBuilding Levels\nClose\nBuilding Levels\nSettings\nSettings\nUnset Storage Area\nWrt\nCreate\nCreate\nCreate Building Level\nModify\nModify Building Level\nDelete\nLevel\nConfirm\nYes\nNo\nConfirm"}
{"Headers": "Create Building Level", "Content": "Creates a new building level.\n\nName\nInput a name for the new building level element or select Autoname.\nAttributes\nAllows you to view and define the new building level attributes.\nElevation\nAllows you to input the elevation position for the new building level element.\nOK\nClick OK to create the building level element in the Design Database and close the Create Level window.\nCancel\nClick Cancel to discard any changes and close the Create Level window.\nName\nInput a name for the new building level element or select Autoname.\nAttributes\nAllows you to view and define the new building level attributes.\nElevation\nAllows you to input the elevation position for the new building level element.\nOK\nClick OK to create the building level element in the Design Database and close the Create Level window.\nCancel\nClick Cancel to discard any changes and close the Create Level window.\nBuilding levels can be modified and deleted. Refer to Modify Building Level for further information.\nName\nInput a name for the new building level element or select Autoname.\nAttributes\nAllows you to view and define the new building level attributes.\nElevation\nAllows you to input the elevation position for the new building level element.\nOK\nClick OK to create the building level element in the Design Database and close the Create Level window.\nCancel\nClick Cancel to discard any changes and close the Create Level window.\n\n\n\nModify Building Level\nName\nAutoname\nAttributes\nElevation\nOK\nOK\nCancel\nCancel\nModify Building Level"}
{"Headers": "Modify Building Level", "Content": "Modifies the elevation of an existing building level element.\n\nModify the elevation as required and click OK to save the change or click Cancel to discard any inputs and close the Elevation window.\nYou can also set/unset the purpose attribute of the STRU element, when set the STRU element is assigned a purpose attribute and displayed in the Building Levels window.\nThe administrative SBFR level in particular is used to emphasise building elements, such as wall and floors. The elements are called soft type elements which are used at the SBFR level in the hierarchy to represent walls, floors and fittings. Soft type elements have the same attributes as standard elements (GENSEC) but are named differently to identify them.\n\n\n\n\nOK\nCancel\nElevation\nBuilding Levels"}
{"Headers": "Create Straight Wall", "Content": "Creates a Straight Wall element (STWALL) which is a soft type element used as part of the building representation rather than for structural design.\nThe straight wall element is a type of a Generic Section (GENSEC), used to represent a wall created by extruding a 2D catalogue profile with a start and finish position.\n\nThe Positioning Control window also displays, the positioning functionality available for selection is common throughout all design disciplines. Refer to Positioning Control for further information.\nYou are prompted to Define Straight wall start (Distance [0]) Snap:\nFrom the Straight Wall window there are three options available:\nClick Define Start/End Explicitly to position the start of the wall explicitly by inputting explicit X, Y and Z co-ordinates. Refer to Define Vertex Explicitly for further information.\nClick Define end a given distance and direction from start to position the end of the wall by specifying a distance and direction from the start of the wall. Refer to Define Vertex Offset from Previous for further information\nClick Perpendicular from to create a wall perpendicular to the wall specified for the new wall start. You are prompted to Pick straight Section/Wall to derive perpendicular from:\nClick Perpendicular to create a wall perpendicular to a selected wall. You are prompted to Pick straight Section/Wall to derive perpendicular end to:\nIf the Confirm check box in the Verification window is selected a line is drawn in the 3D view to indicate the position of the wall. Click Accept to draw the new wall or Reject to start again.\nSingle - Start and end points are individually defined for each section.\nContinuous - Start point of subsequent walls is the end point of previous.\nRadial - Start point for subsequent walls is the same as the first.\nSingle - Start and end points are individually defined for each section.\nSingle - Start and end points are individually defined for each section.\nContinuous - Start point of subsequent walls is the end point of previous.\nContinuous - Start point of subsequent walls is the end point of previous.\nRadial - Start point for subsequent walls is the same as the first.\nRadial - Start point for subsequent walls is the same as the first.\n\n\n\nPositioning Control\nDefine Vertex Explicitly\nDefine Vertex Offset from Previous\nPositioning Control\nPositioning Control\nDefine Straight wall start (Distance [0]) Snap:\nStraight Wall\nSingle\nContinuous\nRadial\nDefine Start/End Explicitly\nDefine Vertex Explicitly\nDefine end a given distance and direction\nDefine Vertex Offset from Previous\nPerpendicular from\nPick straight Section/Wall to derive perpendicular from:\nPerpendicular to\nPick straight Section/Wall to derive perpendicular end to:\nConfirm\nVerification\nAccept\nReject"}
{"Headers": "Define Vertex Explicitly", "Content": "Positions each vertex explicitly with respect to (WRT) another element.\n\n\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. The user can then input an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. The user can then input an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. The user can then input an explicit position value in the Position field.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. The user can then input an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. The user can then input an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. The user can then input an explicit position value in the Position field.\nIf required, select one or all of the Lock check boxes to lock the explicit position of the current co-ordinate along the E/W, N/S or U/D axis.\nThe axes to which all co-ordinates are interpreted with respect to must be set.\nIn the WRT text box, input the name of the element to which all co-ordinates are interpreted with respect to, the default is World.\nClick Apply to create the vertex or Cancel to discard any inputs and close the Define straight wall start/Define straight wall end window.\nEast/West\nFrom the drop down menu, click to identify the direction of the East/West axis. The user can then input an explicit position value in the Position field.\nNorth/South\nFrom the drop down menu, click to identify the direction of the North/South axis. The user can then input an explicit position value in the Position field.\nUp/Down\nFrom the drop down menu, click to identify the direction of the Up/Down axis. The user can then input an explicit position value in the Position field.\n\n\n\nEast/West\nEast/West\nNorth/South\nNorth/South\nUp/Down\nUp/Down\nLock\nWRT\nApply\nCancel\nDefine straight wall start/Define straight wall end"}
{"Headers": "Define Vertex Offset from Previous", "Content": "Positions a vertex at a defined point relative to the position of the preceding vertex\n\nInput a value in the Direction field to define the direction of the vertex relative to the preceding vertex.\nInput a value in the Distance field to define the distance of the vertex relative to the preceding vertex.\nIf required, select one or all of the Lock check boxes to lock the explicit position of the current co-ordinate.\nClick Apply to create the vertex or Cancel to discard any inputs and close the Define straight wall end window.\n\n\n\nDirection\nDistance\nApply\nCancel\nDefine straight wall end"}
{"Headers": "Create Ring Wall", "Content": "Creates a Ring Wall (WALL) which is a soft type element of a Generic Section (GENSEC), used to represent a wall created by extruding a catalogue profile, spine shape which follows a circular arc (up to a full circle).\n\nThe Circle Definition part of the Ring Wall window, defines whether the wall is a full circle or a semi circle.\nYou must then select how the ring wall is created, from the Create Methods part of the Ring Wall:\nThrough 3 points\nClick to create a ring wall which passes through three defined points. You are prompted to define three points in the 3D view.\nDerived from a picked item\nClick to create an offset ring wall on a structure that already exists. You are prompted to pick an item in the 3D view.\nFillet\nClick to create a ring wall with a specified radius between two picked tangent lines.\nTangential to 3 lines\nClick to creates a ring wall which forms the tangents to three straight lines.\nFixed radius, tangential to a circle\nClick to create a ring wall with a specified radius which touches another ring wall at one point.\nFixed radius, passing through 2 points\nClick to create a ring wall with a specified radius which passes through two picked points and curves towards a picked direction.\nTangential to a circle\nClick to create a ring wall which intersects a ring wall that already exists.\nTangential to 2 circles\nClick to create a ring wall which touches two other ring walls tangentially.\nDerived diameter\nClick to create a ring wall from three defined points.\nDerived diameter on working plane\nClick to create a ring wall on the working plane. The wall is created irrespective of the distance above the working plane and the wall parameters are defined.\nFixed diameter\nClick to create a ring wall with a fixed diameter around a single point.\nFixed diameter on working plane\nClick to create a ring wall with a fixed diameter around a single point. The wall is created on the working plane irrespective of the distance the single point is above the working plane.\nDerived radius\nClick to create a ring wall to a predetermined radius.\nDerived radius on the working plane\nClick to create a ring wall to a predetermined radius. The wall is created on the working plane irrespective of the distance the predetermined radius points are above the working plane.\nFixed radius\nClick to create a ring wall with a fixed radius.\nFixed radius on the working plane\nClick to create a ring wall with a fixed radius. The wall is created on the working plane irrespective of the distance the fixed radius points are above the working plane.\nDefine explicitly\nClick to create a ring wall explicitly.\nA Confirm window displays:\nClick OK to replace the Define Ring Section, the Create Wall (Ring) window displays.\nOr click No to close the Confirm window.\nRefer to Create Ring Wall Explicitly for further information.\n\nThrough 3 points\nClick to create a ring wall which passes through three defined points. You are prompted to define three points in the 3D view.\n\nDerived from a picked item\nClick to create an offset ring wall on a structure that already exists. You are prompted to pick an item in the 3D view.\n\nFillet\nClick to create a ring wall with a specified radius between two picked tangent lines.\n\nTangential to 3 lines\nClick to creates a ring wall which forms the tangents to three straight lines.\n\nFixed radius, tangential to a circle\nClick to create a ring wall with a specified radius which touches another ring wall at one point.\n\nFixed radius, passing through 2 points\nClick to create a ring wall with a specified radius which passes through two picked points and curves towards a picked direction.\n\nTangential to a circle\nClick to create a ring wall which intersects a ring wall that already exists.\n\nTangential to 2 circles\nClick to create a ring wall which touches two other ring walls tangentially.\n\nDerived diameter\nClick to create a ring wall from three defined points.\n\nDerived diameter on working plane\nClick to create a ring wall on the working plane. The wall is created irrespective of the distance above the working plane and the wall parameters are defined.\n\nFixed diameter\nClick to create a ring wall with a fixed diameter around a single point.\n\nFixed diameter on working plane\nClick to create a ring wall with a fixed diameter around a single point. The wall is created on the working plane irrespective of the distance the single point is above the working plane.\n\nDerived radius\nClick to create a ring wall to a predetermined radius.\n\nDerived radius on the working plane\nClick to create a ring wall to a predetermined radius. The wall is created on the working plane irrespective of the distance the predetermined radius points are above the working plane.\n\nFixed radius\nClick to create a ring wall with a fixed radius.\n\nFixed radius on the working plane\nClick to create a ring wall with a fixed radius. The wall is created on the working plane irrespective of the distance the fixed radius points are above the working plane.\n\nDefine explicitly\nClick to create a ring wall explicitly.\nA Confirm window displays:\nClick OK to replace the Define Ring Section, the Create Wall (Ring) window displays.\nOr click No to close the Confirm window.\nRefer to Create Ring Wall Explicitly for further information.\n\nThrough 3 points\nClick to create a ring wall which passes through three defined points. You are prompted to define three points in the 3D view.\nDerived from a picked item\nClick to create an offset ring wall on a structure that already exists. You are prompted to pick an item in the 3D view.\nFillet\nClick to create a ring wall with a specified radius between two picked tangent lines.\nTangential to 3 lines\nClick to creates a ring wall which forms the tangents to three straight lines.\nFixed radius, tangential to a circle\nClick to create a ring wall with a specified radius which touches another ring wall at one point.\nFixed radius, passing through 2 points\nClick to create a ring wall with a specified radius which passes through two picked points and curves towards a picked direction.\nTangential to a circle\nClick to create a ring wall which intersects a ring wall that already exists.\nTangential to 2 circles\nClick to create a ring wall which touches two other ring walls tangentially.\nDerived diameter\nClick to create a ring wall from three defined points.\nDerived diameter on working plane\nClick to create a ring wall on the working plane. The wall is created irrespective of the distance above the working plane and the wall parameters are defined.\nFixed diameter\nClick to create a ring wall with a fixed diameter around a single point.\nFixed diameter on working plane\nClick to create a ring wall with a fixed diameter around a single point. The wall is created on the working plane irrespective of the distance the single point is above the working plane.\nDerived radius\nClick to create a ring wall to a predetermined radius.\nDerived radius on the working plane\nClick to create a ring wall to a predetermined radius. The wall is created on the working plane irrespective of the distance the predetermined radius points are above the working plane.\nFixed radius\nClick to create a ring wall with a fixed radius.\nFixed radius on the working plane\nClick to create a ring wall with a fixed radius. The wall is created on the working plane irrespective of the distance the fixed radius points are above the working plane.\nDefine explicitly\nClick to create a ring wall explicitly.\nA Confirm window displays:\nClick OK to replace the Define Ring Section, the Create Wall (Ring) window displays.\nOr click No to close the Confirm window.\nRefer to Create Ring Wall Explicitly for further information.\n\n\n\nCreate Ring Wall Explicitly\nCircle Definition\nRing Wall\nCreate Methods\nRing Wall\nThrough 3 points\nDerived from a picked item\nFillet\nTangential to 3 lines\nFixed radius, tangential to a circle\nFixed radius, passing through 2 points\nTangential to a circle\nTangential to 2 circles\nDerived diameter\nDerived diameter on working plane\nFixed diameter\nFixed diameter on working plane\nDerived radius\nDerived radius on the working plane\nFixed radius\nFixed radius on the working plane\nDefine explicitly\nConfirm\nOK\nCreate Wall (Ring)\nNo\nConfirm\nCreate Ring Wall Explicitly"}
{"Headers": "Create User Defined Wall", "Content": "Creates a User Defined Wall (GWALL, a soft type element of a Panel (PANE), used to represent a cross-section (usually horizontal) which is extruded (usually vertically) to represent, for example a structural column.\n\nYou can create a set of vertices in a number of ways, specific to other attributes necessary to relate these vertices to a 3D representation.\nFloors, Screeds and User Defined Walls (GWALL) are soft types of panel, and are created from the same window. In the latter case, the thickness of the panel is equivalent to the height of the user-defined wall.\nRefer to Create Floor for further information.\n\n\n\nCreate Floor\nCreate Floor"}
{"Headers": "Create Compound Wall", "Content": "Creates a Compound Wall (CWALL) which can be used as an alternative administrative element in the design hierarchy.\n\n\n\n"}
{"Headers": "Create Floors", "Content": "Creates a floor, screed, negative extrusion, compound floor or compound screed.\nFloor elements are not part of the catalogue and are therefore a 2D user defined shape extruded through a thickness. These elements are intended to represent any sheet material but in general are used to represent concrete slabs.\nThe planar area of the floor is defined by a Panel Loop (PLOO) element. A Panel Loop is itself defined by linking together a set of panel vertex (PAVE) elements, each of which has a specific position in the 2D co-ordinate system of the panel. Each panel edge is defined by a line joining adjacent vertices.\nThe floor thickness is defined by setting the height attribute of the PLOO element which represents the distance through which the 2D panel loop is extruded to form the floor panel.\n\n\n\n"}
{"Headers": "Create Floor", "Content": "Creates a Floor (FLOOR) element. Floors are soft types of panel, and are created from the same window as User Defined Walls and Screeds.\nMake sure a suitable default floor specification and a default storage area at the current building level are defined. A Compound Floor (CFLOOR) element can also be used as a suitable storage area.\n\nSet the Justification to Bottom (this allows you to position the bottom face of the floor on the top of the supporting sections).\nSet the Thickness, if a floor specification has been set, the default thickness is shown, entering a new value is permitted.\nIf a Confirm window displays, click Yes to override the default thickness value and change it to Unset.\nClick No to disregard the entered thickness value and retain the default value.\nBy default, Representation is set to Predefined: Default. These settings (Levels and Obstruction) affect the way items display in 3D views and how they are dealt with when checking for clashes between design items.\nFor example: you can define four vertices, V1-V4, to define the overall area of the floor which is shown shaded in the diagram. Refer to Component Visibility, Drawing Level and Obstruction for further information\n\nThe Create Methods part of the Create Floor window allows you to define each vertex.\nDerived points from graphic picks\nAllows you to pick a point graphically with the Positioning Control window.\nDerive points from centres & plines\nAllows you to construct a point from the intersection of two Plines with a floor that already exists.\nTrace boundary of another extrusion/panel\nAllows you to create vertices which follow the shape of a floor that already exists.\nExplicitly defined position\nAllows you to specify a position by entering explicit co-ordinates.\nPoint offset from previous\nAllows you to specify a distance and direction which define a point relative to the position of the vertex that precedes it.\nDefine arc fillet\nAllows you to construct a fillet arc with a specified radius between two picked tangent lines.\nDerived arc passing through three points\nAllows you to construct a fillet arc that passes through three picked points.\nFixed radius arc, passing through 2 points\nAllows you to construct a fillet arc with a specified radius, that passes through two picked points, which curves towards a picked direction.\n\nDerived points from graphic picks\nAllows you to pick a point graphically with the Positioning Control window.\n\nDerive points from centres & plines\nAllows you to construct a point from the intersection of two Plines with a floor that already exists.\n\nTrace boundary of another extrusion/panel\nAllows you to create vertices which follow the shape of a floor that already exists.\n\nExplicitly defined position\nAllows you to specify a position by entering explicit co-ordinates.\n\nPoint offset from previous\nAllows you to specify a distance and direction which define a point relative to the position of the vertex that precedes it.\n\nDefine arc fillet\nAllows you to construct a fillet arc with a specified radius between two picked tangent lines.\n\nDerived arc passing through three points\nAllows you to construct a fillet arc that passes through three picked points.\n\nFixed radius arc, passing through 2 points\nAllows you to construct a fillet arc with a specified radius, that passes through two picked points, which curves towards a picked direction.\nFor the purpose of this user guide, two options are used to illustrate the principles:\nClick Derive Points From Graphic Picks. The Positioning Control window displays and indicates that you are now in event-driven graphics mode, ready to pick the position of the first vertex.\nFrom the Positioning Control window, select Element then Intersect, you are prompted to \u2018Define vertex (Intersection [1]) Snap:\u2019\nPick the column and either of the beams whose intersection coincides with V1 in the diagram. From the Create Methods part of the Create Floor window, \u2018No vertices currently defined\u2019 is automatically changed to \u20181 Vertices defined (no Floor created)\u2019. After the definition of this first vertex, Remove Previous Point becomes active. From this, you are able to delete the previous vertex definition.\nRepeat this point-picking procedure to define V2 and V3, in that order. As soon as you have defined three vertices, the plane of the new floor is shown in the 3D view (as a triangle) and a FLOOR element added into the Model Explorer.\nFrom the Create Methods part of the Create Floor window, \u20181 Vertices defined (no Panel created)\u2019 is automatically changed to \u20183 Vertices defined (Panel created)\u2019.\nOnce the third vertex is defined, an axis aid displays at the default floor origin. It shows the floors axis system. The Y (North) direction is defined by the direction from vertex 1 to vertex 2.\n\nAs a demonstration, V4 is positioned relative to V3. Click Point Offset From Previous. The Define vertex window displays in which you can specify the required offset.\n\nSet the Direction and the Distance, click Apply to create the vertex, or click Dismiss to discard any information and close the Define vertex window.\nThe Create Methods part of the Create Floor window, is automatically changed to \u20184 Vertices defined (Floor created)\u2019.\nIf required, you can modify the floor vertices immediately, to do this, select the Display modification form check box.\nClick OK to complete the floor creation operation.\nOnce the floor element is created, the Model Explorer now includes one FLOOR, one PLOO and four PAVE elements.\nDerived points from graphic picks\nAllows you to pick a point graphically with the Positioning Control window.\nDerive points from centres & plines\nAllows you to construct a point from the intersection of two Plines with a floor that already exists.\nTrace boundary of another extrusion/panel\nAllows you to create vertices which follow the shape of a floor that already exists.\nExplicitly defined position\nAllows you to specify a position by entering explicit co-ordinates.\nPoint offset from previous\nAllows you to specify a distance and direction which define a point relative to the position of the vertex that precedes it.\nDefine arc fillet\nAllows you to construct a fillet arc with a specified radius between two picked tangent lines.\nDerived arc passing through three points\nAllows you to construct a fillet arc that passes through three picked points.\nFixed radius arc, passing through 2 points\nAllows you to construct a fillet arc with a specified radius, that passes through two picked points, which curves towards a picked direction.\nDerive Points From Graphic Picks\nPoint Offset From Previous.\nDerive Points From Graphic Picks\nDerive Points From Graphic Picks\nPoint Offset From Previous.\nPoint Offset From Previous.\nNote:\nThe first vertex defined for a new floor becomes the origin (as displayed) by default. You can change this if required.\n\n\n\nComponent Visibility, Drawing Level and Obstruction\nJustification\nThickness\nConfirm\nYes\nNo\nRepresentation\nComponent Visibility, Drawing Level and Obstruction\nCreate Methods\nCreate Floor\nDerived points from graphic picks\nPositioning Control\nDerive points from centres & plines\nTrace boundary of another extrusion/panel\nExplicitly defined position\nPoint offset from previous\nDefine arc fillet\nDerived arc passing through three points\nFixed radius arc, passing through 2 points\nDerive Points From Graphic Picks\nPositioning Control\nPositioning Control\nElement\nIntersect\nDefine vertex (Intersection [1]) Snap\nCreate Methods\nCreate Floor\n\u2018No vertices currently defined\u2019\n\u20181 Vertices defined (no Floor created)\u2019\nRemove Previous Point\nNote:\nCreate Methods\nCreate Floor\n\u20181 Vertices defined (no Panel created)\u2019\n\u20183 Vertices defined (Panel created)\u2019.\nPoint Offset From Previous\nDefine vertex\nDirection\nDistance\nApply\nDismiss\nDefine vertex\nCreate Methods\nCreate Floor\n\u20184 Vertices defined (Floor created)\u2019\nDisplay modification form\nOK"}
{"Headers": "Create Screed", "Content": "Creates a Screed (SCREED) element, Screeds are soft types of panel, and are created from the same window as Floors and User defined Walls.\nMake sure a suitable default floor specification and a default storage area at the current building level are defined. A Compound Floor (CFLOOR) or Compound Screed (CSCREED) element can also be used as a suitable storage area.\n\nThe functionality available from the Create Screed window is identical to the functionality available from the Create Floor window. Refer to Create Floor for further information.\nOnce the screed element has been created, the Model Explorer now includes one FLOOR, one PLOO and four PAVE elements.\n\n\n\nCreate Floor\nCreate Screed\nCreate Floor\nCreate Floor"}
{"Headers": "Create Negative Extrusion", "Content": "Creates a Negative Extrusion (NXTR) by positioning PAVE elements to form a Loop (LOOP) and then extruding them. A negative extrusion represents a negative volume, that is, a hole.\nA negative extrusion is owned by the floor/screed through which the hole is positioned.\n\nThe display of the negative extrusion volume in the 3D view can be modified. Refer to Component Visibility, Drawing Level and Obstruction for further information.\nTo achieve the correct justification and orientation for the negative extrusion relative to the owning floor/screed, from the Settings part of the window, click Surface. Then pick the upper face of the floor/screed.\nThe hole penetrates into the panel thickness from this surface.\nSet Hole Depth (equivalent to the thickness of the negative extrusion). A large depth makes it easy to see the volume of the negative extrusion once created. A depth slightly greater than the floor/screed thickness would normally suffice, since the application automatically adds 1mm to make sure that the hole always cuts through the referenced surface. The settings pane of the Create Negative Extrusion window is populated.\nUse any combination of the methods used to create and modify negative extrusion vertices. Refer to Measure Distance for further information. You can now create the four vertices needed to define the required hole round the column. For ease of positioning, V1 and V2 can be aligned with the outer face of the column (although any position beyond the floor/screed edge is satisfactory).\nWhen the four vertices are created, click OK to display the Loop Vertex Editor window. The functionality of the Loop Vertex Editor window is explained. Refer to Modify Floor/Screed Definition for further information.\nWhen created, the negative extrusion appears as an outline volume superimposed on the design in the graphical view. If positioned correctly, the upper face slightly protrudes from the top face of the floor/screed.\nNote:\nTo get a better view, zoom in close to the floor/screed and the column of interest and look along (and slightly above) the floor/screed.\n\n\n\nComponent Visibility, Drawing Level and Obstruction\nMeasure Distance\nModify Floor/Screed Definition\n\nComponent Visibility, Drawing Level and Obstruction\nSettings\nSurface\nNote:\nHole Depth\nCreate Negative Extrusion\nMeasure Distance\nOK\nLoop Vertex Editor\nLoop Vertex Editor\nModify Floor/Screed Definition"}
{"Headers": "Create Compound Floor", "Content": "Creates a Compound Floor (CFLOOR) which can be used as an administrative element in the hierarchy as a storage area for all compound floor elements.\n\n\n\n"}
{"Headers": "Create Compound Screed", "Content": "Creates a Compound Screed (CSCREE) which can be used as an administrative element in the hierarchy as a storage area for all compound screed elements.\n\n\n\n"}
{"Headers": "Wall Connectivity", "Content": "Sets the wall connection status.\n\n\n"}
{"Headers": "Connect Walls", "Content": "Connects two wall ends. The selected wall ends are connected to make a corner.\nA connection between two wall ends is facilitated by a Primary Joint (PJOI) element. The PJOI is owned by a Primary Node (PNOD) element, which is positioned on the justification line of the owning wall at the intersection between the attached and owning walls.\nYou are prompted to First wall end:\nClick to identify the first wall end.\nYou are then prompted to Second wall end:\nClick to identify the second wall end.\nThe wall connection process is repeated, allowing you to create multiple connections. Press ESC to end the command.\n\n\n\nFirst wall end:\nSecond wall end:\nESC"}
{"Headers": "Connect Wall to Wall", "Content": "Connects a wall end to any point on an intersecting wall.\nA connection between an attached wall end to any point of an owning wall is facilitated by a Secondary Joint (SJOI) element. The SJOI is owned by a Secondary Node (SNOD) element, which is positioned on the justification line of the owning wall at the intersection between the attached and owning walls.\nYou are prompted to Identify wall end to be connected to\nClick to identify the wall to connect the wall end to.\nYou are then prompted to Identify wall end to be connected\nClick to identify the wall to be connected.\nThe prompt is repeated, allowing you to connect multiple wall ends to the first wall end selection.\nPress ESC to connect the wall end to the intersecting wall.\n\n\n\nIdentify wall end to be connected to\nIdentify wall end to be connected\nESC"}
{"Headers": "Align Wall Connections", "Content": "Aligns the attached wall ends of the currently selected owning wall in line with the Z axis if the wall position has been modified. All SNOD elements are realigned to the correct position.\n\n\n"}
{"Headers": "Disconnect Walls", "Content": "Disconnects multiple wall ends.\nYou are prompted to Identify wall end to be disconnected.\nClick to identify the first wall end to be disconnected.\nYou are then prompted to Identify wall end to be disconnected.\nClick the identify the second wall end to be disconnected.\nThe prompt is repeated, allowing you to disconnect multiple wall ends.\nPress ESC to disconnect the wall ends.\n\n\n\nIdentify wall end to be disconnected.\nIdentify wall end to be disconnected"}
{"Headers": "Tidy Joints and Nodes", "Content": "Deletes unwanted nodes and joints when a connected wall is deleted from the 3D model.\n\n\n"}
{"Headers": "Tidy Joints", "Content": "Removes unwanted SNOD and SJOI elements when a connected wall is deleted from the 3D model.\nSelect the Mark Joint for Deletion, Delete Node if empty check boxes as required.\nOn the Tidy Joints window, click CE to identify the elements to be checked as the CE.\nThe joint for deletion is labelled in the 3D view and the number of joints to delete displays in the Tidy Joints window.\n\n\n\n\nMark Joint for Deletion\nDelete Node if empty\nTidy Joints\nCE\nTidy Joints"}
{"Headers": "Tidy Nodes", "Content": "Removes unwanted SJOI elements when a connected wall is deleted from the 3D model.\nSelect the Mark Nodes for Deletion check box as required.\nOn the Tidy Nodes window, click CE to identify the elements to be checked as the CE.\nThe node for deletion is labelled in the 3D view and the number of nodes to delete displays in the Tidy Nodes window.\n\n\n\n\nMark Nodes for Deletion\nTidy Nodes\nCE\nTidy Nodes"}
{"Headers": "View Wall End Connections", "Content": "Displays the wall end connection status for all walls in the 3D view. The connection types that are highlighted in the 3D view can be defined.\n\nCE\nClick to identify the currently selected element as the working element.\nBoth ends connected\nSelect the check box to highlight the walls that are connected at both ends in the 3D view.\nClick the colour palette to modify the highlight colour in the 3D view.\nNeither end connected\nSelect the check box to highlight the walls that are not connected at either end in the 3D view.\nClick the colour palette to modify the highlight colour in the 3D view.\nOne end unconnected\nSelect the check box to highlight the walls that are connected at one end in the 3D view. The end that is not connected is indicated.\nClick the colour palette to modify the highlight colour in the 3D view.\nCE\nClick to identify the currently selected element as the working element.\nBoth ends connected\nSelect the check box to highlight the walls that are connected at both ends in the 3D view.\nClick the colour palette to modify the highlight colour in the 3D view.\nNeither end connected\nSelect the check box to highlight the walls that are not connected at either end in the 3D view.\nClick the colour palette to modify the highlight colour in the 3D view.\nOne end unconnected\nSelect the check box to highlight the walls that are connected at one end in the 3D view. The end that is not connected is indicated.\nClick the colour palette to modify the highlight colour in the 3D view.\nClick Cancel to close the Highlight Connections window, the highlighted connections are removed from the 3D view.\n\nCE\nClick to identify the currently selected element as the working element.\nBoth ends connected\nSelect the check box to highlight the walls that are connected at both ends in the 3D view.\nClick the colour palette to modify the highlight colour in the 3D view.\nNeither end connected\nSelect the check box to highlight the walls that are not connected at either end in the 3D view.\nClick the colour palette to modify the highlight colour in the 3D view.\nOne end unconnected\nSelect the check box to highlight the walls that are connected at one end in the 3D view. The end that is not connected is indicated.\nClick the colour palette to modify the highlight colour in the 3D view.\n\n\n\nCE\nBoth ends connected\nNeither end connected\nOne end unconnected\nCancel\nHighlight Connections"}
{"Headers": "Create Wall Fittings", "Content": "Creates a Single Wall Fitting (FITT) which is used to represent any type of geometric entity that is owned by, and positioned relative to, a wall. Typically, the catalogue might include wall fittings which represent, for example, doors, windows, fire protection and electrical fittings.\nAll of the tasks that are associated with the creation of a wall fitting are initiated from the Wall Fittings window which acts as a task hub.\n\nAid lines also display in the 3D view to indicate the origin for the fitting.\nAll the tasks that are associated with the creation or modification of wall fittings are initiated from a central Wall Fittings window which acts as task hub. Dependant on selections made in the Wall Fittings window you are presented with further windows which prompt input.\nBy default the Create Standard option (single fitting) is selected.\nFrom the Specification Data part of the Wall Fittings window, by default Electrical Fittings is selected. If another type of wall fitting is required, select from the drop-down list of available options.\n\nSpecification Data\nThe Current Selection part of the Wall Fittings window, by default is empty. Dependant upon the selection of specification made, you are presented with a list of fittings available for selection from the catalogue.\nNo Selection\nIf required, you can create a fitting without a specification (to be used when you want to create an arbitrary fitting for positioning purposes or where a compound fitting needs to be created which has its own specific sub-fittings). To do this, select the No Selection check box.\nDefault\nWhen the Default check box is selected, only the fittings from the default specification are available for selection.\nAuto\nWhen the Auto check box is selected, the fitting is automatically selected, where only one fitting is available for selection.\nIf both the Default and Auto check boxes are selected, the default fitting is automatically selected.\nOnce the Specification Data has been defined, the required fitting can be selected from the Wall Fitting window.\nThe Owning Type part of the Wall Fittings window is automatically populated with the types available for selection under the specification.\nClick the required type and it displays in the Current Selection window.\nThe Owning Type window automatically changes to the Type window which displays a list of fittings. Click to select one of the items. The selected item displays in the Current Selection window and a sub-section item displays in the Type window.\nClick the next selection in the Type window and the selected sub-section item appears in the Current Selection window.\nWhen the selection process is complete the Type window changes to Selection Complete.\n\nProperties\nTo modify the properties of the fitting, click Properties to display the Modify Properties window. The name of the CE displays, by default.\nThe functionality available for modification depends on the type of wall fitting selected:\nElectrical Fittings: You can modify the Pline offset, which uses the Pline of a wall to calculate the offset between two elements that already exist.\n\nClick Default to return to the default setting.\nClick Reset to return to a previous setting.\nClick OK to accept the modified properties.\nClick Cancel to discard any inputs and close the Modify Properties window.\nFire Protection: You cannot modify any properties.\nStandard Windows: You can modify the inset from the Modify Properties window, the Inset from the wall face can be set manually or select Measure Inset from the wall face to pick the inset in the 3D view.\n\nThe Open Angle refers to the window opening angle in the representation of the window in the 3D view.\nClick Default to return to the default setting.\nClick Reset to return to a previous setting.\nClick OK to accept the modified properties.\nClick Cancel to discard any inputs and close the Modify Properties window.\nStandard Door: You can modify the inset from the wall face, from the Standard Door Modify Properties window. The Inset from the wall face can be set manually or picked in the 3D view, select Measure Inset from the wall face.\n\nThe Open Angle refers to the door opening angle in the representation of the door in the 3D view.\nClick Default to return to the default setting.\nClick Reset to return to a previous setting.\nClick OK to accept the modified properties.\nClick Cancel to discard any inputs and close the Modify Properties window.\nExample Openings: You can modify the dimensions for the opening. From the Example Opening Modify Properties window for General Rectangular Hole for Walls the X dimension, Y dimension, X offset dimension and Y offset dimension can be set manually or picked in the 3D view. Select the appropriate option.\n\nFrom the Modify Properties window for General Circular Hole for Walls only the diameter can be Input or measured.\nClick Default to go back the default setting.\nClick Reset to return to a previous setting.\nClick OK to accept the modified properties.\nPlotfile\nTo view a pictorial representation of the wall fitting, from the Wall Fittings window, select Plotfile, to display the Plotfile window. The plotfile functionality depends on the type of wall fitting selected:\n\nElectrical Fittings\nPlotfile functionality is available.\nFire Protection\nPlotfile functionality is not available.\nStandard Window\nPlotfile functionality is not available.\nStandard Door\nPlotfile functionality is not available.\nExample Openings\nPlotfile functionality is not available.\nReload\nReturns to the default window.\nElectrical Fittings\nPlotfile functionality is available.\nFire Protection\nPlotfile functionality is not available.\nStandard Window\nPlotfile functionality is not available.\nStandard Door\nPlotfile functionality is not available.\nExample Openings\nPlotfile functionality is not available.\nReload\nReturns to the default window.\nPositioning\nFrom the Positioning part of the Wall Fittings window, you must specify the distance offset from the outside or inside of the wall.\nThe location of the fitting on the wall is set by the input of the distance along the wall and the elevation. These two dimensions are measured from the origin of the owning wall indicated by the aid line in the graphic display.\nTo position the fitting directly on the wall, click Position fitting to display the Positioning Control window. You are prompted to Position Fitting (Snap) Snap. Refer to Positioning Control for further information.\nSub-Fitting Orientation\nThe Sub-Fitting Orientation part of the Wall Fittings windows allows you to orientate a sub-compound fitting relative to the owning compound fitting.\nInput the direction of the Z axis of the fitting in the Sub-Fitting Direction (Z) field.\nInput the rotation of the fitting about its Z axis in the Rotation Angle (Z axis) filed.\nClick Apply to create the wall fitting or click Dismiss to discard any inputs and close the Wall Fittings window.\nCompound Wall Fitting\nCreates a Compound Wall Fitting (CMFI) which can own a number of Wall Sub-Fittings (SBFI).\nAll of the tasks that are associated with the creation of a compound wall fitting are initiated from the Wall Fittings window which acts as a task hub. By default, Create Compound is selected.\n\nThe procedure to create the compound fitting is the same as for the standard fitting. Refer to Create Wall Fittings for further information.\nWall Sub-Fitting\nCreates Wall Sub-Fitting (SBFI) components which can be owned by a Compound Wall Fitting (CMFI) and can be modified as a group. For example, if a power switch is created as a compound wall fitting, sockets can be created as wall sub-fittings owned by the switch. If the switch position is changed the sockets move with it.\nAll of the tasks that are associated with the creation of a wall sub-fitting are initiated from the Wall Fittings window which acts as a task hub. By default, Create Sub-Compound is selected.\nThe procedure to create the sub-compound fitting is the same as for the standard fitting. Refer to Create Wall Fittings for further information.\nElectrical Fittings\nPlotfile functionality is available.\nFire Protection\nPlotfile functionality is not available.\nStandard Window\nPlotfile functionality is not available.\nStandard Door\nPlotfile functionality is not available.\nExample Openings\nPlotfile functionality is not available.\nReload\nReturns to the default window.\nNote:\nThe sub-fitting orientation functionality is only available when the CE is a sub-fitting.\n\n\n\nPositioning Control\nCreate Wall Fittings\nCreate Wall Fittings\nWall Fittings\nWall Fittings\nCreate Standard\nWall Fittings\nElectrical Fittings\nSpecification Data\nCurrent Selection\nWall Fittings\nNo Selection\nNo Selection\nDefault\nDefault\nAuto\nAuto\nDefault\nAuto\nSpecification Data\nWall Fitting\nOwning Type\nWall Fittings\nCurrent Selection\nOwning Type\nType\nCurrent Selection\nType\nType\nCurrent Selection\nType\nSelection Complete\nProperties\nProperties\nModify Properties\nElectrical Fittings\nDefault\nReset\nOK\nCance\nModify Properties\nFire Protection\nStandard Windows\nModify Properties\nInset from the wall face\nMeasure Inset from the wall face\nOpen Angle\nDefault\nReset\nOK\nCance\nModify Properties\nStandard Door\nModify Properties\nInset from the wall face\nMeasure Inset from the wall face\nOpen Angle\nDefault\nReset\nOK\nCance\nModify Properties\nExample Openings\nModify Properties\nModify Properties\nDefault\nReset\nOK\nPlotfile\nWall Fittings\nPlotfile\nPlotfile\nElectrical Fittings\nFire Protection\nStandard Window\nStandard Door\nExample Openings\nReload\nPositioning\nPositioning\nWall Fittings\nPosition fitting\nPositioning Control\nPosition Fitting (Snap) Snap\nPositioning Control\nSub-Fitting Orientation\nNote:\nSub-Fitting Orientation\nWall Fittings\nSub-Fitting Direction (Z)\nRotation Angle (Z axis)\nApply\nDismiss\nWall Fittings\nCompound Wall Fitting\nWall Fittings\nCreate Compound\nCreate Wall Fittings\nWall Sub-Fitting\nWall Fittings\nCreate Sub-Compound\nCreate Wall Fittings"}
{"Headers": "Create Floor Fittings", "Content": "Creates a Single Floor Fitting (PFIT) which can be used to represent any type of geometric entity that is owned by, and positioned relative to, a floor.\nAll of the tasks that are associated with the creation of a single floor fitting are initiated from the Floor Fittings window which acts as a task hub.\n\nAid lines display in the 3D view to indicate the origin for the fitting.\nThe functionality available from the Floor Fittings window is identical to that available from Wall Fittings window (refer to Create Wall Fittings for further information) with the exception of the Positioning part of the window.\nReference Datum\nThe reference datum allows you to specify the positioning of the fitting within the thickness of the floor/screed and the direction of fitting with respect to the floor/screed.\n\nFrom the Positioning part of the Floor Fittings window, select the reference datum from the drop-down list.\nThe location of the fitting on the floor is set by the input of the X Position and Y position. These two dimensions are measured from the origin of the owning wall indicated by the aid line in the graphic display.\nSelect Position fitting to display the Positioning Control window, you are prompted to Position Floor Fitting (Snap) Snap to position the fitting directly on the floor. Refer to Positioning Control for further information.\nClick Apply to insert the floor fitting or click Cancel to discard any information and close the Floor Fittings window.\nCompound Floor Fitting\nCreates a Compound Floor Fitting (CMPF) which can own a number of Floor Sub-Fittings (SBFI).\nAll of the tasks that are associated with the creation of a compound floor fitting are initiated from the Floor Fittings window which acts as a task hub. By default, Create Compound is selected.\n\nThe functionality available is identical to floor fittings. Refer to Create Floor Fittings for further information.\nFloor Sub-Fitting\nCreates Floor Sub-Fitting (SBFI) components which can be owned by a Compound Floor Fitting (CMPF) and can be modified as a group. For example, if a table is created as a compound floor fitting, chairs can be created as floor sub-fittings owned by the table. If the table position is changed the chairs move with it.\nAll of the tasks that are associated with the creation of a floor sub-fitting are initiated from the Floor Fittings window which acts as a task hub. By default, Create Sub-Compound is selected.\nThe functionality available is identical to floor fittings. Refer to Create Floor Fittings for further information.\n\n\n\nCreate Wall Fittings\nPositioning Control\nCreate Floor Fittings\nCreate Floor Fittings\nFloor Fittings\nFloor Fittings\nWall Fittings\nCreate Wall Fittings\nReference Datum\nPositioning\nFloor Fittings\nPosition fitting\nPositioning Control\nPosition Floor Fitting (Snap) Snap\nPositioning Control\nApply\nCancel\nFloor Fittings\nCompound Floor Fitting\nFloor Fittings\nCreate Compound\nCreate Floor Fittings\nFloor Sub-Fitting\nFloor Fittings\nCreate Sub-Compound\nCreate Floor Fittings"}
{"Headers": "Modify Walls", "Content": "Modifies the wall definition, specification, origin, justification or start/end position.\nThe functionality is identical whichever element is selected to be modified with one exception, the modification of the definition of a STWALL and WALL.\n\n\n"}
{"Headers": "Modify Straight Wall", "Content": "Modifies the position, length and direction of a straight wall.\nBy default the Start position of the current element displays as East, North and Up coordinates with respect to the world.\n\nClick Select CE to identify the currently selected element as the working element. Alternatively, click Pick a Wall to select a different wall, you are prompted to Pick Wall to Modify: The name of the selected element displays in the Modify STWALL window.\nThe Start position is indicated in the 3D view.\nThe Position options allow you to specify the point on the element to which the position coordinates apply. You can specify Start, End or Centre from the drop-down list.\nDependant on the option specified, modification of coordinates has an effect on the CE. Refer to Coordinates for further information.\nStart\nRelocates the start position of the element to the specified coordinates, and leaves its end position unchanged.\nEnd\nRelocates the end position of the element to the specified coordinates, and leaves its start position unchanged.\nCentre\nRelocates the entire element, locates its centre at the specified coordinates and modifies the start and end positions.\nStart\nRelocates the start position of the element to the specified coordinates, and leaves its end position unchanged.\nEnd\nRelocates the end position of the element to the specified coordinates, and leaves its start position unchanged.\nCentre\nRelocates the entire element, locates its centre at the specified coordinates and modifies the start and end positions.\nTo define a position by reference to design items that already exist, use the Positioning Control window and the cursor to identify the required position using a cursor pick in the 3D view. Refer to Positioning Control for further information.\nThe Settings option allows you to change the length and direction of the wall.\nThe End Direction option allows you to change the end direction to Perpendicular or you can Maintain the original direction.\nClick Apply to modify the straight wall or click Cancel to discard any inputs and close the Modify STWALL window.\nStart\nRelocates the start position of the element to the specified coordinates, and leaves its end position unchanged.\nEnd\nRelocates the end position of the element to the specified coordinates, and leaves its start position unchanged.\nCentre\nRelocates the entire element, locates its centre at the specified coordinates and modifies the start and end positions.\n\n\n\nCoordinates\nPositioning Control\nSelect CE\nPick a Wall\nPick Wall to Modify:\nModify STWALL\nStart\nPosition\nStart\nEnd\nCentre\nCoordinates\nStart\nEnd\nCentre\nPositioning Control\nPositioning Control\nSettings\nEnd Direction\nPerpendicular\nMaintain\nApply\nCancel\nModify STWALL"}
{"Headers": "Modify Ring Wall", "Content": "Modifies the curve, position and orientation of a ring wall.\nBy default, the Positioning Control window displays. Refer to Positioning Control for further information.\n\nBy default, the Start and End positions, and the orientation of the current element are displayed in the Modify Wall (Ring) window.\nClick Select to define the CE or to pick a curved section using a cursor pick in the 3D view.\nThe Settings options allows you to change the radius of the ring wall.\nThe Angles option allows you to change the point on the circle of the ring wall where the Start and End are located.\nIn the Position and Orientation window, click the Position drop-down menu to select the Origin, Radius or Start and End Angles to change. If required, use the Lock check boxes to fix the current co-ordinate along any axis.\nThe Orientation option allows you to change the orientation of the wall. The settings are mirrored by the axes that display the 3D view. Only the Y and Z axes can be changed.\nClick Apply to accept the changes or click Dismiss to discard any inputs and close the Modify Wall (Ring) window.\n\n\n\nPositioning Control\nPositioning Control\nPositioning Control\nModify Wall (Ring)\nSelect\nSettings\nAngles\nPosition and Orientation\nPosition\nLock\nOrientation\nApply\nDismiss\nModify Wall (Ring)"}
{"Headers": "Modify Wall Specification", "Content": "Modifies the wall specification using available elements from the structural catalogue.\nAll of the tasks that are associated with the modification of a wall specification are initiated from the Wall Specification window which acts as a task hub.\n\nThe functionality available from the Wall Specification window is identical to that available from the Default Wall Specification window. Refer Wall Specification for further information.\n\n\n\nWall Specification\nWall Specification\nWall Specification\nDefault Wall Specification\nWall Specification"}
{"Headers": "Modify Wall Position Origin", "Content": "Modifies the vertex position of the wall origin.\nYou are prompted to Pick near vertex for new origin\nClick to identify the wall vertex origin using a cursor pick in the 3D view.\n\n\n\nPick near vertex for new origin"}
{"Headers": "Modify Wall Justification", "Content": "Modifies the wall pline justification.\n\nTo change the justification select the required Pline justification from the drop-down list. Refer to Wall Specification for further information.\nTo select the justification manually from the 3D view click Justification, you are prompted to Identify Pline to justify to, select the pline using a cursor pick in the 3D view.\nTo maintain attachment to an attached wall select the Re-trim attached wall check box.\nClick Apply to accept the changes or click Dismiss to discard any inputs and close the Wall Justification window.\nThe modification procedure for the wall Member Line and Joint Line is the same.\n\n\n\nWall Specification\nWall Specification\nIdentify Pline to justify to\nRe-trim attached wall\nApply\nDismiss\nWall Justification\nMember Line\nJoint Line"}
{"Headers": "Flip Wall", "Content": "Flips the wall element 180 degrees.\n\n\n"}
{"Headers": "Modify Floors", "Content": "Modifies the floor definition, justification, thickness, negative extrusion, origin or specification.\n\n\n"}
{"Headers": "Modify Floor/Screed Definition", "Content": "Modifies the PLOO geometry of a floor/screed.\nThe Loop Vertex Editor window allows you to move, add and delete vertices, edges and arcs. The vertices can be expanded or contracted by a specified amount.\nA group of vertices can be selected to be copied and inserted in a different part of the loop. Tools are provided to modify the group, for example, move the origin or mirroring, before the group is inserted.\n\nFrom the Loop Vertex Editor window, you can select these options.\nControl > CE\nClick to modify the CE. The CE name displays at the top of the window. Navigating to another floor/screed and selecting this option makes the new CE the floor/screed being edited by the window.\nControl > Close\nClick to close the Loop Vertex Editor window.\nSettings > Confirm\nWhen Confirm is selected, you must click Modify at the bottom of the window to implement each modification. When Confirm is not selected, each modification is implemented immediately.\nSettings > Confirm on delete\nWhen Confirm is selected, you must confirm each deletion in order to complete the command. When Confirm is not selected, deletions are implemented immediately.\nSettings > Tag Edges\nWhen Tag Edges is selected, each edge is tagged with the number of the vertex at its start.\nSettings > Display Axes\nWhen Display Axes is selected, the axes of the floor/screed are displayed at the first vertex.\nSettings > Free rotate\nWhen Free rotate is selected, groups of vertices can be orientated automatically when moved from one edge to another.\nUtilities > Remove coincident\nVertices are deleted by this option when where more vertices have the same position.\nControl > CE\nClick to modify the CE. The CE name displays at the top of the window. Navigating to another floor/screed and selecting this option makes the new CE the floor/screed being edited by the window.\nControl > Close\nClick to close the Loop Vertex Editor window.\nSettings > Confirm\nWhen Confirm is selected, you must click Modify at the bottom of the window to implement each modification. When Confirm is not selected, each modification is implemented immediately.\nSettings > Confirm on delete\nWhen Confirm is selected, you must confirm each deletion in order to complete the command. When Confirm is not selected, deletions are implemented immediately.\nSettings > Tag Edges\nWhen Tag Edges is selected, each edge is tagged with the number of the vertex at its start.\nSettings > Display Axes\nWhen Display Axes is selected, the axes of the floor/screed are displayed at the first vertex.\nSettings > Free rotate\nWhen Free rotate is selected, groups of vertices can be orientated automatically when moved from one edge to another.\nUtilities > Remove coincident\nVertices are deleted by this option when where more vertices have the same position.\nThe options in the Mode Selection part of the Loop Vertex Editor window allow the modification of a single vertex, an edge or a group of vertices.\nSelect all\nAllows the selection of all vertices in the loop so they can be modified as a group.\nSelect group to modify\nAllows the selection of a number of individual vertices so that they can be modified as a group.\nSelect edge to modify\nAllows the selection of an edge to be modified. The adjacent Edge area displays the current edge number.\nSelect point to modify\nAllows the selection of a vertex to be modified. The adjacent Vertex area displays the current vertex number.\nCreate points\nAllows the creation of a new vertex which is allocated the next number in the sequence after the current vertex.\nSelect all\nAllows the selection of all vertices in the loop so they can be modified as a group.\nSelect group to modify\nAllows the selection of a number of individual vertices so that they can be modified as a group.\nSelect edge to modify\nAllows the selection of an edge to be modified. The adjacent Edge area displays the current edge number.\nSelect point to modify\nAllows the selection of a vertex to be modified. The adjacent Vertex area displays the current vertex number.\nCreate points\nAllows the creation of a new vertex which is allocated the next number in the sequence after the current vertex.\nThe Vertex/Edge part of the Loop Vertex Editor window contains a Select option and a counter that displays the current vertex or edge depending on the current mode. If Select edge to modify is selected, the counter label changes to Edge and the counter displays the current edge.\nThe Select vertex/edge option allows you to pick a vertex in the 3D view. The adjacent Vertex/Edge counter displays the current vertex/edge number which is also tagged in the 3D view. You can navigate to a specific vertex or edge by typing its number in the text box or by using the up/down arrows to step through the list.\nWhen a group of vertices are modified, the options in the Group part of the Loop Vertex Editor window become active. These allow the modification of the current group.\nReverse group definition\nReverses the group definition by renumbering all the group vertices in the opposite direction (clockwise or anticlockwise).\nMove start forwards\nMoves the open-side of the group and the origin for the vertex numbering one place forward.\nMove start backwards\nMoves the open-side of the group and the origin for the vertex numbering one place backwards.\nReverse group definition\nReverses the group definition by renumbering all the group vertices in the opposite direction (clockwise or anticlockwise).\nMove start forwards\nMoves the open-side of the group and the origin for the vertex numbering one place forward.\nMove start backwards\nMoves the open-side of the group and the origin for the vertex numbering one place backwards.\nThe Expand/Contract part of the Loop Vertex Editor window expands or contracts a group as specified.\nExpand Group moves each edge of the group outwards by the distance specified in the Expand/Contract text box normal to its own direction.\nContract Group moves each edge of the group inwards by the distance specified in the Expand/Contract text box normal to its own direction.\nSelect the Retain Fillet Radius check box to preserve the fillet radius of expanded/contracted curves. If the check box is not selected, the fillet radius of curves is expanded/contracted. The fillet radius is expanded/contracted if a curve has a positive fillet radius value. The fillet radius is not expanded/contracted if a curve has a negative or zero fillet radius value. If the fillet radius is too small for the boundary offset, the fillet radius is automatically modified to 0mm.\nIf an edge is modified, the functionality in the Line area become active. These options allow the modification of the current edge.\nExtend start of line\nMoves the Start vertex along the edge direction to align it through a picked position. Use the Positioning Control options to pick the required position. Refer to Positioning Control for further information. Alternatively, if a line is selected the End vertex is moved along the edge direction until it intersects the picked line. These operations can change the edge length.\nExtend end of line\nMoves the End vertex along the edge direction to align it through a picked position. Use the Positioning Control options to pick the required position. Refer to Positioning Control for further information. Alternatively, if a line is selected the Start vertex is moved along the edge direction until it intersects the picked line. These operations can change the edge length.\nMake line parallel\nMoves the free vertex around the reference vertex to align the edge with a picked line. The operation maintains the edge length.\nExtend start of line\nMoves the Start vertex along the edge direction to align it through a picked position. Use the Positioning Control options to pick the required position. Refer to Positioning Control for further information. Alternatively, if a line is selected the End vertex is moved along the edge direction until it intersects the picked line. These operations can change the edge length.\nExtend end of line\nMoves the End vertex along the edge direction to align it through a picked position. Use the Positioning Control options to pick the required position. Refer to Positioning Control for further information. Alternatively, if a line is selected the Start vertex is moved along the edge direction until it intersects the picked line. These operations can change the edge length.\nMake line parallel\nMoves the free vertex around the reference vertex to align the edge with a picked line. The operation maintains the edge length.\nThe options in the Rotate part of the Loop Vertex Editor window allows the rotation of groups of vertices in these ways:\nRotate anticlockwise rotates the edge anticlockwise, through the rotation angle specified in the Angle text box, about the reference end. The operation maintains the edge length.\nRotate clockwise rotates the edge clockwise, through the rotation angle specified in the Angle text box, about the reference end. The operation maintains the edge length.\nThe Modify part of the Loop Vertex Editor window enables you to perform operations on the current group selection.\nInsert selected\nMoves a vertex group by inserting it at a different position in the loop sequence. Use the vertex selector to navigate to the required point in the sequence. The group is inserted after the current vertex.\nMirror\nMoves the current vertex, edge or group such that the new positions are derived by reflecting the original positions about a picked line (for example, an edge or a pline).\nDelete selection\nDeletes a group, edge or vertex from the loop definition.\nDefine/Modify arc\nManipulates a fillet arc at the current loop vertex. When selected the Modified Arc window displays, the Loop Vertex Editor window becomes temporarily inactive.\nInsert selected\nMoves a vertex group by inserting it at a different position in the loop sequence. Use the vertex selector to navigate to the required point in the sequence. The group is inserted after the current vertex.\nMirror\nMoves the current vertex, edge or group such that the new positions are derived by reflecting the original positions about a picked line (for example, an edge or a pline).\nDelete selection\nDeletes a group, edge or vertex from the loop definition.\nDefine/Modify arc\nManipulates a fillet arc at the current loop vertex. When selected the Modified Arc window displays, the Loop Vertex Editor window becomes temporarily inactive.\n\nThe Vertex part of the Loop Vertex Editor window displays co-ordinate data about the current vertex, edge or group depending on the Selection Mode.\nVertex X and Y co-ordinates are displayed with respect to the floor/screed origin.\nEdge co-ordinates are given for the start or end of the edge. An aid displays in the 3D view indicating which is the start and which is the end. By default the START edge displays in uppercase and the end displays in lowercase. Only the START is affected by any modifications made to the currently displayed co-ordinates.\nSelect End to display the END of the edge in uppercase and the start in lowercase. Modifications made to the currently displayed co-ordinates only affect the END.\nModifying the length in both these cases moves the start or end accordingly.\nThe Aligned option displays both the START and END of the edge in uppercase.\nControl > CE\nClick to modify the CE. The CE name displays at the top of the window. Navigating to another floor/screed and selecting this option makes the new CE the floor/screed being edited by the window.\nControl > Close\nClick to close the Loop Vertex Editor window.\nSettings > Confirm\nWhen Confirm is selected, you must click Modify at the bottom of the window to implement each modification. When Confirm is not selected, each modification is implemented immediately.\nSettings > Confirm on delete\nWhen Confirm is selected, you must confirm each deletion in order to complete the command. When Confirm is not selected, deletions are implemented immediately.\nSettings > Tag Edges\nWhen Tag Edges is selected, each edge is tagged with the number of the vertex at its start.\nSettings > Display Axes\nWhen Display Axes is selected, the axes of the floor/screed are displayed at the first vertex.\nSettings > Free rotate\nWhen Free rotate is selected, groups of vertices can be orientated automatically when moved from one edge to another.\nUtilities > Remove coincident\nVertices are deleted by this option when where more vertices have the same position.\nSelect all\nAllows the selection of all vertices in the loop so they can be modified as a group.\nSelect group to modify\nAllows the selection of a number of individual vertices so that they can be modified as a group.\nSelect edge to modify\nAllows the selection of an edge to be modified. The adjacent Edge area displays the current edge number.\nSelect point to modify\nAllows the selection of a vertex to be modified. The adjacent Vertex area displays the current vertex number.\nCreate points\nAllows the creation of a new vertex which is allocated the next number in the sequence after the current vertex.\nReverse group definition\nReverses the group definition by renumbering all the group vertices in the opposite direction (clockwise or anticlockwise).\nMove start forwards\nMoves the open-side of the group and the origin for the vertex numbering one place forward.\nMove start backwards\nMoves the open-side of the group and the origin for the vertex numbering one place backwards.\nExtend start of line\nMoves the Start vertex along the edge direction to align it through a picked position. Use the Positioning Control options to pick the required position. Refer to Positioning Control for further information. Alternatively, if a line is selected the End vertex is moved along the edge direction until it intersects the picked line. These operations can change the edge length.\nExtend end of line\nMoves the End vertex along the edge direction to align it through a picked position. Use the Positioning Control options to pick the required position. Refer to Positioning Control for further information. Alternatively, if a line is selected the Start vertex is moved along the edge direction until it intersects the picked line. These operations can change the edge length.\nMake line parallel\nMoves the free vertex around the reference vertex to align the edge with a picked line. The operation maintains the edge length.\nInsert selected\nMoves a vertex group by inserting it at a different position in the loop sequence. Use the vertex selector to navigate to the required point in the sequence. The group is inserted after the current vertex.\nMirror\nMoves the current vertex, edge or group such that the new positions are derived by reflecting the original positions about a picked line (for example, an edge or a pline).\nDelete selection\nDeletes a group, edge or vertex from the loop definition.\nDefine/Modify arc\nManipulates a fillet arc at the current loop vertex. When selected the Modified Arc window displays, the Loop Vertex Editor window becomes temporarily inactive.\n\n\n\nPositioning Control\nPositioning Control\nLoop Vertex Editor\nLoop Vertex Editor\nControl > CE\nControl > Close\nLoop Vertex Editor\nSettings > Confirm\nConfirm\nModify\nConfirm\nSettings > Confirm on delete\nConfirm\nConfirm\nSettings > Tag Edges\nTag Edges\nSettings > Display Axes\nDisplay Axes\nSettings > Free rotate\nFree rotate\nUtilities > Remove coincident\nMode Selection\nLoop Vertex Editor\nSelect all\nSelect group to modify\nSelect edge to modify\nEdge\nSelect point to modify\nVertex\nCreate points\nVertex/Edge\nLoop Vertex Editor\nSelect\nSelect edge to modify\nEdge\nSelect vertex/edge\nVertex/Edge\nGroup\nLoop Vertex Editor\nReverse group definition\nMove start forwards\nMove start backwards\nExpand/Contract\nLoop Vertex Editor\nExpand Group\nExpand/Contract\nContract Group\nExpand/Contract\nRetain Fillet Radius\nLine\nExtend start of line\nStart\nPositioning Control\nPositioning Control\nEnd\nExtend end of line\nEnd\nPositioning Control\nPositioning Control\nStart\nMake line parallel\nRotate\nLoop Vertex Editor\nRotate anticlockwise\nAngle\nRotate clockwise\nAngle\nModify\nLoop Vertex Editor\nInsert selected\nMirror\nDelete selection\nDefine/Modify arc\nModified Arc\nLoop Vertex Editor\nVertex\nLoop Vertex Editor\nSTART\nend\nSTART\nEnd\nEND\nstart\nEND\nAligned\nSTART\nEND"}
{"Headers": "Modify Floor/Screed Justification", "Content": "Sets the direction used to justify the floor/screed relative to the plane.\n\n\nSelect Bottom, Centre or Top from the justification list.\nClick Apply to modify the floor/screed justification or click Dismiss to discard any information and close the Set Justification window.\nThe in/out check box sets the direction relative to the plane.\n\n\n\nBottom\nCentre\nTop\nApply\nDismiss\nSet Justification\nin/out"}
{"Headers": "Modify Floor/Screed Thickness", "Content": "Modifies the thickness attribute of a floor/screed element.\n\nIf the element identified as the CE is not a floor, screed or negative extrusion, a warning message displays:\n\nModify the thickness of the CE as required.\nClick Apply to modify the thickness attribute.\nOr\nClick Cancel to discard any inputs and close the Screed Thickness window.\n\n\n\nApply\nCancel\nScreed Thickness"}
{"Headers": "Modify Floor/Screed Negative Extrusion", "Content": "Modifies the PLOO geometry of a negative extrusion.\nThe Loop Vertex Editor window allows you to move, add and delete vertices, edges and arcs. The vertices can be expanded or contracted by a specified amount.\nA group of vertices may be selected to be copied and inserted in a different part of the loop. Tools are provided to modify the group, for example, move the origin or mirroring, before the group is inserted.\n\nThe functionality of the Loop Vertex Editor is explained. Refer to Modify Floor/Screed Definition for further information.\n\n\n\nModify Floor/Screed Definition\nLoop Vertex Editor\nModify Floor/Screed Definition"}
{"Headers": "Position Floor/Screed Origin", "Content": "Modifies the vertex position of the floor origin.\nYou are prompted to Pick near vertex for new origin\nClick to identify the floor vertex origin using a cursor pick in the 3D view.\n\n\n\nPick near vertex for new origin"}
{"Headers": "Modify Floor/Screed Specification", "Content": "Modifies the floor/screed specification using available elements from the structural catalogue.\nThe functionality is only available for PANEL or one of its soft type elements. If another element is selected as the CE, a warning message displays.\n\nThe functionality available is identical to that described in default specification. Refer to Floor Specification and Wall Specification for further information.\n\n\n\nFloor Specification\nWall Specification\nFloor Specification\nWall Specification"}
{"Headers": "Modify Wall and Floor Fittings", "Content": "Modifies the catalogue specification associated with each wall, floor or screed fitting.\n\n\n"}
{"Headers": "Modify Wall Fitting", "Content": "Modifies the catalogue specification associated with each wall fitting.\nAll of the tasks that are associated with the modification of wall fittings are initiated from the Wall Fittings window which acts as a task hub.\n\nBy default, Modify CE displays in the drop-down menu and the CE is described.\nAlternatively, select Modify PICK from the drop-down menu to modify a fitting using a cursor pick in the 3D view.\nYou are prompted to Pick Wall Fitting to Modify:\nThe Wall Fittings window is populated with the specification data and positioning details of the identified wall fitting.\nThe functionality available from the window is identical to Wall Fittings window which is used in the creation of a wall fitting. Refer to Create Wall Fittings for further information.\n\n\n\nCreate Wall Fittings\nWall Fittings\nModify CE\nModify PICK\nPick Wall Fitting to Modify:\nWall Fittings\nCreate Wall Fittings"}
{"Headers": "Modify Floor/Screed Fitting", "Content": "Modifies the catalogue specification associated with each floor or screed fitting.\nAll of the tasks that are associated with the modification of floor fittings are initiated from the Floor Fittings window which acts as a task hub.\n\nBy default, Modify CE displays in the drop-down menu and the CE is described.\nAlternatively, select Modify PICK from the drop-down menu to modify a fitting using a cursor pick in the 3D view.\nYou are prompted to Pick Floor Fitting to Modify:\nThe Floor Fittings window is populated with the specification data and positioning details of the identified floor fitting.\nThe functionality available from the window is identical to Floor Fittings window which is used in the creation of a floor fitting. Refer to Create Floor Fittings for further information.\n\n\n\nCreate Floor Fittings\nFloor Fittings\nModify CE\nModify PICK\nPick Floor Fitting to Modify:\nFloor Fittings\nCreate Floor Fittings"}
{"Headers": "Split Wall", "Content": "Splits a straight wall into shorter lengths where it intersects with another element.\nThe Split Walls window must be populated before any elements can be picked in the 3D view.\n\nThe only method to select Elements to be split on and Elements to be split in the 3D view is Pick using cursor.\nFrom the Connections at split part of the Split Walls window, you can specify how the ends of the new shorter length walls are to be connected at the split points:\nNone\nSNODs are not created at the split points and the wall ends are not trimmed back.\nNodes\nWall ends are connected to SNODs, but are not trimmed back.\nTrimmed\nWall ends are connected to SNODs and are trimmed back to the geometry of attached items at the point of connection.\nIf a wall to be split is not perpendicular to a wall or section defining a split point, the cut planes are orientated automatically in the correct directions for the joints.\nNone\nSNODs are not created at the split points and the wall ends are not trimmed back.\nNodes\nWall ends are connected to SNODs, but are not trimmed back.\nTrimmed\nWall ends are connected to SNODs and are trimmed back to the geometry of attached items at the point of connection.\nIf a wall to be split is not perpendicular to a wall or section defining a split point, the cut planes are orientated automatically in the correct directions for the joints.\nSelect the Confirm before splitting check box to display a Confirm window before each split occurs.\nClick Apply, you are prompted to Identify item to be split on\nClick to identify the items in the 3D view which determine the split points. When the items have been identified, press ESC.\nYou are then prompted to Identify wall to be split\nClick to identify the walls to split in the 3D view. When these items have been identified, press ESC.\nIf the Confirm Before Splitting check box was selected, a Confirm window displays.\nClick Yes to split the walls\nOr\nClick No to discard any inputs and close the Confirm window.\nClick Cancel to discard any information and close the Split Walls window.\nNone\nSNODs are not created at the split points and the wall ends are not trimmed back.\nNodes\nWall ends are connected to SNODs, but are not trimmed back.\nTrimmed\nWall ends are connected to SNODs and are trimmed back to the geometry of attached items at the point of connection.\nIf a wall to be split is not perpendicular to a wall or section defining a split point, the cut planes are orientated automatically in the correct directions for the joints.\n\n\n\nSplit Walls\nElements to be split on\nElements to be split\nPick using cursor\nConnections at split\nSplit Walls\nNone\nNodes\nTrimmed\nConfirm before splitting\nConfirm\nApply\nIdentify item to be split on\nESC.\nIdentify wall to be split\nESC\nConfirm Before Splitting\nConfirm\nYes\nNo\nConfirm\nCancel\nSplit Walls"}
{"Headers": "Splice Wall", "Content": "Divides a wall into smaller lengths using a splice.\nYou must specify the plane to create the splice.\n\nThe splice can be applied to the CE, the current list or elements picked from the 3D view by the selection of CE, List or Pick from the options listed on the top left of the window. If the List or Pick option is selected, all of the elements selected are spliced at their intersection with the plane.\nTo specify the size of the plane, input a value in the Plane size text box.\nPosition the plane with the Cursor or Intersection options from the window or by inputting co\u2011ordinates in the appropriate text boxes.\nSelect the Confirm before splicing check box to display a Confirm window before each splice occurs.\nClick Apply, you are prompted to Identify walls to be spliced\nClick to identify the walls in the 3D view. When the items have been identified, press ESC.\nIf the Confirm Before Splicing check box was selected, a Confirm window displays.\nClick Yes to splice the walls\nOr\nClick No to discard any inputs and close the Confirm window.\nClick Cancel to discard any information and close the Splice Wall on Plane window.\n\n\n\nCE\nList\nPick\nList\nPick\nPlane size\nConfirm before splicing\nConfirm\nApply\nIdentify walls to be spliced\nESC.\nConfirm Before Splicing\nConfirm\nYes\nNo\nConfirm\nCancel\nSplice Wall on Plane"}
{"Headers": "Merge Walls", "Content": "Merges individual colinear walls to form a single wall.\n\nMake the first wall to be picked the CE, this is the dominant wall, that is the wall that all other picked walls are merged into and whose attributes the merged walls inherit.\nClick CE in the Merge Walls window.\nSelect the Merge from location from the drop-down menu.\nClick Apply and the prompt Identify walls to be included in merge displays in the bottom left hand corner of the screen.\nIf ESC is pressed before at least one wall to merge has been picked, an error message displays.\nIf ESC is pressed before the key wall is picked an error message displays.\n\nWhen all the walls have been identified click ESC.\nThe confirmation message displays.\nClick OK to merge the walls.\nThe merged walls have the database Reference No. of the wall picked first (the dominant wall).\nClick Cancel to discard any information and close the Merge Walls window.\n\n\n\nCE\nMerge Walls\nMerge from\nApply\nIdentify walls to be included in merge\nESC\nESC\nESC\nOK\nCancel\nMerge Walls"}
{"Headers": "Mitre Ends", "Content": "Miters a straight wall end to another straight wall end.\nYou are prompted to Pick ends of wall to be mitered\nYou must pick two walls to be mitered, once both walls are picked, the walls are mitered automatically.\n\n\n\nPick ends of wall to be mitered"}
{"Headers": "Wall Ends", "Content": "Extends and trims wall ends.\n\n\n"}
{"Headers": "Extend Through", "Content": "Sets a plane, position and orientation to extend either end of the wall to. The wall only extends along its Z axis, that is its extrusion direction, as the plane is infinite in its planar dimensions.\nIn the application, a plane\u2019s direction is defined by the direction of a vector normal (that is perpendicular in all directions) to the plane. The position of the plane is defined by the start position of that vector.\n\nThe End of Section drop-down list allows you to specify which end of the wall is extended (or trimmed) to the plane. Four choices are available:\nWhen the Extend Section - Relative window displays, a label is placed at each end of the section to identify which end is the Start and which is the End.\nYou can define the plane position explicitly by inputting co-ordinates in the Plane Direction East/West, North/South and Up/Down fields of the window, or with the Cursor and Intersection functionality and selection of the position in the 3D view.\nThe Plane Direction is set by default to Up, however any direction can be input to orientate the plane. The plane aid and direction vector in the 3D view helps you to visualize the position and direction of the plane.\nClick Apply to extend the end of the current element to the plane. The position of any Secondary Nodes owned by the wall is measured from its start position. Select the Maintain Node Positions check box to make sure the Secondary Nodes stay in their original position when the start position of the wall is moved. Otherwise, the Secondary Nodes move with the start position, their Z distance attributes are maintained.\nSelect the Cut end(s) to plane check box to orientate the end of the wall to the plane direction after it has been extended or trimmed.\nNearest end \u2013 The default setting. The end of the wall nearest to the plane is repositioned.\nStart \u2013 The start position of the wall is moved.\nEnd \u2013 The end position of the wall is moved.\nPick \u2013 Click Apply and you are prompted to pick which end of the wall is to be re-positioned.\nNearest end \u2013 The default setting. The end of the wall nearest to the plane is repositioned.\nNearest end \u2013 The default setting. The end of the wall nearest to the plane is repositioned.\nStart \u2013 The start position of the wall is moved.\nStart \u2013 The start position of the wall is moved.\nEnd \u2013 The end position of the wall is moved.\nEnd \u2013 The end position of the wall is moved.\nPick \u2013 Click Apply and you are prompted to pick which end of the wall is to be re-positioned.\nPick \u2013 Click Apply and you are prompted to pick which end of the wall is to be re-positioned.\n\n\n\nEnd of Section\nNearest end\nStart\nEnd\nPick\nExtend Section - Relative\nStart\nEnd\nPlane Direction\nCursor\nIntersection\nPlane Direction\nUp\nApply\nMaintain Node Positions\nZ distance\nCut end(s) to plane"}
{"Headers": "Extend By", "Content": "Lengthens or shortens a wall by moving the start or end position by a specified amount.\n\nWhen the window displays, a label is placed at either end of the section to identify the Start and End locations. The Extend drop-down menu allows you to select which end of the section is extended, the choices being Start, End or Pick.\nIf the Pick option is selected, you are prompted to select the end of the wall to be re-positioned then click Apply.\nYou can move the end of a wall either by Distance or by a Proportion of the wall\u2019s current length, by selecting the appropriate option and inputting the desired amount. Inputting a positive value lengthens the wall and inputting a negative value shortens it.\nTo maintain the position of any Secondary Node owned by the wall, select the Maintain Node Positions check box.\n\n\n\nStart\nEnd\nExtend\nStart\nEnd\nPick\nPick\nApply\nDistance\nProportion\nMaintain Node Positions"}
{"Headers": "Trim Ends", "Content": "Trims the length of an attached wall to intersect with an owning wall if a wall position has been modified.\nYou are prompted to Identify end to be trimmed\nClick to identify the attached wall end to trim\nThe prompt is repeated, allowing you to select multiple attached wall ends.\nPress ESC to trim the attached wall ends to the owning wall.\n\n\n\nIdentify end to be trimmed\nESC"}
{"Headers": "Trim Connected", "Content": "Trims the length of all attached wall ends to intersect with a selected owning wall if a wall position has been modified.\nYou are prompted to Identify element attached ends are to be trimmed to:\nBy default, all wall ends that are attached to the selected owning wall are trimmed and the command ends automatically.\n\n\n\nIdentify element attached ends are to be trimmed to:"}
{"Headers": "Split Floor/Screed", "Content": "Splits a floor or a screed into multiple floors.\nA floor/screed can only be split along the axis of an element that already exists. To introduce a split line anywhere else, create a section where the split is to occur, split the floor, then delete the section.\nYou are prompted to Identify PANE SCREED FLOOR GWALL to be split\nClick to identify the floor/screed to split.\nYou are then prompted to Pick SCTN STWALL PANE SCREED FLOOR GWALL to be split on\nClick to identify the structure position to split the floor/screed. Once the selections have been made the floor/screed is split.\n\n\n\nIdentify PANE SCREED FLOOR GWALL to be split\nPick SCTN STWALL PANE SCREED FLOOR GWALL to be split on"}
{"Headers": "Modify Screed Slope", "Content": "Applies a single slope to a screed element with the addition of a negative volume to the screed definition.\nOnly one slope can be applied to any screed element, to apply multiple slopes to an area, you must first split the overall screed into separate elements.\n\nThe Current Element part of the Screed Slope window allows you to select the screed element to apply the slope to\nCE\nClick to select the existing screed as the current element.\nPick Element from 3D View\nPrompts you to pick a screed in the 3D view.\nCE\nClick to select the existing screed as the current element.\nPick Element from 3D View\nPrompts you to pick a screed in the 3D view.\nThe Position part of the Screed Slope window allows you to position a point through which the sloped surface passes.\nOrigin\nRefers to the lowest or highest point on the surface.\nThrough\nThe slope and direction can be changed so that the slope passes through the defined point.\nOrigin\nRefers to the lowest or highest point on the surface.\nThrough\nThe slope and direction can be changed so that the slope passes through the defined point.\nThe Slope part of the Screed Slope window allows you position the slope edge points.\nAbout Edge\nAllows you to define the slope start point.\nYou are prompted to Pick edge to slope from db Element:\nClick to identify the screed edge to be used as the slope start point using a cursor pick in the 3D view.\nAbout Edges\nAllows you to define the slope start and end points.\nYou are prompted to Slope edge line, first:\nClick to identify the screed edge to be used as the slope start point using a cursor pick in the 3D view.\nYou are prompted to Slope edge line, second:\nClick to identify the screed edge to be used as the slope end point using a cursor pick in the 3D view.\nBy default, the slope angle is calculated between the two picked points.\nAbout Edge\nAllows you to define the slope start point.\nYou are prompted to Pick edge to slope from db Element:\nClick to identify the screed edge to be used as the slope start point using a cursor pick in the 3D view.\nAbout Edges\nAllows you to define the slope start and end points.\nYou are prompted to Slope edge line, first:\nClick to identify the screed edge to be used as the slope start point using a cursor pick in the 3D view.\nYou are prompted to Slope edge line, second:\nClick to identify the screed edge to be used as the slope end point using a cursor pick in the 3D view.\nBy default, the slope angle is calculated between the two picked points.\nThe Settings part of the Screed Slope window allows you to define the slope contour, angle and direction.\nTo define the slope contour, from the Type drop-down list, select Straight or Conical. The angle of the slope normal to the screed plane must now be defined, input the slope angle in degrees into the Slope field.\nThe direction along which the slope angle is measured from the screed plane, displays in the Direction field, by default.\nSelect the Lock check box to make sure that the angle is calculated so that the slope passes through the defined point.\nWhen an area has been subdivided into individual screeds to achieve a multi-faceted surface, if required, you can align the slope with one or two abutting screed slopes.\nClick Apply to display the outline of the new screed layout in the 3D view.\nClick Cancel to close the Screed Slope window.\nCE\nClick to select the existing screed as the current element.\nPick Element from 3D View\nPrompts you to pick a screed in the 3D view.\nOrigin\nRefers to the lowest or highest point on the surface.\nThrough\nThe slope and direction can be changed so that the slope passes through the defined point.\nAbout Edge\nAllows you to define the slope start point.\nYou are prompted to Pick edge to slope from db Element:\nClick to identify the screed edge to be used as the slope start point using a cursor pick in the 3D view.\nAbout Edges\nAllows you to define the slope start and end points.\nYou are prompted to Slope edge line, first:\nClick to identify the screed edge to be used as the slope start point using a cursor pick in the 3D view.\nYou are prompted to Slope edge line, second:\nClick to identify the screed edge to be used as the slope end point using a cursor pick in the 3D view.\nBy default, the slope angle is calculated between the two picked points.\n\n\n\nCurrent Element\nScreed Slope\nCE\nPick Element from 3D View\nPosition\nScreed Slope\nOrigin\nThrough\nSlope\nScreed Slope\nAbout Edge\nPick edge to slope from db Element:\nAbout Edges\nSlope edge line, first:\nSlope edge line, second:\nSettings\nScreed Slope\nType\nStraight\nConical\nSlope\nDirection\nLock\nApply\nCancel\nScreed Slope"}
{"Headers": "Walls and Floors Tools", "Content": "The Walls and Floors application provides functionality (tools) that allow you to modify the material of the CE, split or merge the CE, move walls or trace a boundary of a floor screed or negative extrusion.\n\n\n"}
{"Headers": "Material", "Content": "Modifies the materials used in the 3D model. The material reference (Matref) attribute can be modified so that attributes such as weight and COG can be calculated and then used with the checking and reporting functionality of the application.\n\nYou can assign a material (Matref) to the CE, list or a picked element. The material part of the Set Material window is populated with a list of available materials for selection. If a material is not available for selection, refer to the administrator for further information.\nFrom the drop-down menu select the element to be modified. It can be the CE, selected from a collection or picked with the cursor in the 3D view.\nIf the Cascade Material to all offspring check box is selected, any associated items (for example: fittings) have their material changed as well.\nFrom the Materials list, select the required material.\nClick Apply to change the material or click Cancel to discard any information and close the Set Material window.\n\n\n\nCascade Material to all offspring\nMaterials\nApply\nCancel\nSet Material"}
{"Headers": "Trace", "Content": "Traces the boundary of an existing floor, screed or negative extrusion to create a new surrounding wall, floor or screed.\n\nYou must first identify the floor screed or negative extrusion that already exists, from which its boundary is to be changed:\nFrom the Boundary Tracing window, select CE, or select Pick. You are prompted to Pick Element for Boundary Tracing: The name of the selected element displays in the Boundary Tracing window.\nFrom the Trace part of the Boundary Trace window, select the type of element to be created - Walls, Floor or Screed.\nThe Offsets part of the Boundary Tracing window allows you to position the new element:\nBoundary positions the edges of the new element relative to the edges of the traced element. A positive boundary offset positions the new edges outside the traced boundary, a negative boundary offset positions the new edges inside the traced boundary.\nElevation positions the vertical position of the new element.\nMiter Walls check box is only available when the element to be traced is a wall element, the functionality allows you to determine if junctions between the walls are to be miterd.\nClick Apply to trace the boundary.\nA Confirm window displays, click Yes to retain the boundary.\nClick No to abandon the trace.\nClick Cancel to discard any information and close the Boundary Tracing window.\n\n\n\nBoundary Tracing\nCE\nPick\nPick Element for Boundary Tracing:\nBoundary Tracing\nTrace\nBoundary Trace\nWalls\nFloor\nScreed\nBoundary Tracing\nBoundary\nElevation\nMiter Walls\nConfirm\nYes\nNo\nCancel\nBoundary Tracing"}
{"Headers": "Structural Catalog", "Content": "Structural Catalogues are used for the creation of the design model. Some of the principal features are listed for standard catalogue components. The structural catalogue can be stored and modified with AVEVA Catalog.\nAll profiles, joints and fittings used in the design are selected from the catalogue database by setting the specification reference for the corresponding design element so that it points to the required catalogue entry.\n\n\n"}
{"Headers": "Profiles", "Content": "The structural profile catalogue only contains profiles detailed in the National Standards or other recognized national bodies, for example, Institutes of Steel Construction.\nThe scope of the profile catalogue includes the following considerations:\nProfiles from the following national standards are included:\n\n\nAustralia/New Zealand\nEurope\nSouth Africa\nCanada\nIndia\nUK\nChile\nJapan\nUSA\nChina\nRussia\nProfile sizes produced by individual manufacturers that may not conform to National Standards are not included.\nCold formed profiles are included where they occur in the standards. Proprietary cold formed profiles from different manufacturers are not included.\nSolid bars, of various cross section, which occur in the majority of referenced standards are included in a common separate category, for example, flat bar, circular bar.\nProfile sizes produced by individual manufacturers that may not conform to National Standards are not included.\nProfile sizes produced by individual manufacturers that may not conform to National Standards are not included.\nCold formed profiles are included where they occur in the standards. Proprietary cold formed profiles from different manufacturers are not included.\nCold formed profiles are included where they occur in the standards. Proprietary cold formed profiles from different manufacturers are not included.\nSolid bars, of various cross section, which occur in the majority of referenced standards are included in a common separate category, for example, flat bar, circular bar.\nSolid bars, of various cross section, which occur in the majority of referenced standards are included in a common separate category, for example, flat bar, circular bar.\nAustralia/New Zealand\nAustralia/New Zealand\nAustralia/New Zealand\nEurope\nEurope\nEurope\nSouth Africa\nSouth Africa\nSouth Africa\nCanada\nCanada\nCanada\nIndia\nIndia\nIndia\nUK\nUK\nUK\nChile\nChile\nChile\nJapan\nJapan\nJapan\nUSA\nUSA\nUSA\nChina\nChina\nChina\nRussia\nRussia\nRussia\n\n\n\nNational Standards"}
{"Headers": "Hierarchy", "Content": "The catalogue contains a single Structural Section (STSE) element to contain all design parameter profiles.\nThe STSE contains a Structural Category (STCA) element for each design parameter profile Generic TYPE (GTYPE) which contains a single SPRF element, a GMSS element, a PTSS element and a DTSE element applicable to the specific profile.\n\n\n\n"}
{"Headers": "Standard Profiles - Naming & Descriptions", "Content": "All standard profiles are named in accordance with the nomenclature given in the appropriate standard and prefixed by an abbreviation for the standard and the profile type, for example, BS_UB254x46x37. This avoids name clashes where similar profiles are in two or more standards, for example L100x100x10.\nThe Description attribute of the SPRF element is populated with the name given in the appropriate standard or local convention, for example, 254x146UB37.\nThe SPRF Description attribute is used for profile selection. If the Description attribute is unset, the SPRF Name attribute is displayed.\n\n\n"}
{"Headers": "Standard Profiles - Generic Types", "Content": "The standard profile GTYPEs in the catalogue are:\nAngle\nParallel Flange Tee\nBox Girder\nAsymmetric Plate Girder\nCircular Bar\nTapered Flange Channel\nC Profile\nTapered Flange I\nCircular Tube\nTapered Flange Tee\nFlat Bar\nTapered Flange Tapered Web Tee\nHexagonal Bar\nRectangular Tube\nParallel Flange Channel\nZ Profile\nParallel Flange I\n\n\n\nANGL\nAngle\nPFT\nParallel Flange Tee\nBOXG\nBox Girder\nPLTG\nAsymmetric Plate Girder\nCBAR\nCircular Bar\nTFC\nTapered Flange Channel\nCEE\nC Profile\nTFI\nTapered Flange I\nCTUB\nCircular Tube\nTFT\nTapered Flange Tee\nFBAR\nFlat Bar\nTFTW\nTapered Flange Tapered Web Tee\nHBAR\nHexagonal Bar\nRTUB\nRectangular Tube\nPFC\nParallel Flange Channel\nZED\nZ Profile\nPFI\nParallel Flange I\nANGL\nANGL\nANGL\nPFT\nPFT\nPFT\nBOXG\nBOXG\nBOXG\nPLTG\nPLTG\nPLTG\nCBAR\nCBAR\nCBAR\nTFC\nTFC\nTFC\nCEE\nCEE\nCEE\nTFI\nTFI\nTFI\nCTUB\nCTUB\nCTUB\nTFT\nTFT\nTFT\nFBAR\nFBAR\nFBAR\nTFTW\nTFTW\nTFTW\nHBAR\nHBAR\nHBAR\nRTUB\nRTUB\nRTUB\nPFC\nPFC\nPFC\nZED\nZED\nZED\nPFI\nPFI\nPFI\n\n\n"}
{"Headers": "Standard Profiles - Parameters", "Content": "The standard parameter list for all GTYPEs is:\nNo.\nParameter Description\nDKEY\nData Type\n1\nDepth\nDPTH\nGeometry\n2\nWidth A\nWIDA\nGeometry\n3\nWidth B\nWIDB\nGeometry\n4\nWidth C\nWIDC\nGeometry\n5\nWeb Thickness\nWTHK\nGeometry\n6\nFlange Thickness A\nFTKA\nGeometry\n7\nFlange Thickness B\nFTKB\nGeometry\n8\nRadius A\nRADA\nGeometry\n9\nRadius B\nRAD B\nGeometry\n10\nRadius C\nRAD C\nGeometry\n11\nCofG X Axis Offset\nCGXO\nGeometry\n12\nCofG Y Axis Offset\nCGYO\nGeometry\n13\nFlange Thickness Centre Offset\nFTCO\nGeometry\n14\nFlange Slope (degrees)\nFSLO\nGeometry\n15\nWeb Slope (degrees)\nWSLO\nGeometry\n16\nGage Line A\nGLNA\nData\n17\nGage Line B\nGLNB\nData\n18\nGage Line C\nGLNC\nData\n19\nMaximum Bolt Diameter A\nMBDA\nData\n20\nMaximum Bolt Diameter B\nMBDB\nData\n21\nMass per Unit Length\nMAUL\nData\n22\nSurface Area per meter\nSAPM\nData\n23\nCross Sectional Area\nXSAR\nData\nNo.\nParameter Description\nDKEY\nData Type\n1\nDepth\nDPTH\nGeometry\n2\nWidth A\nWIDA\nGeometry\n3\nWidth B\nWIDB\nGeometry\n4\nWidth C\nWIDC\nGeometry\n5\nWeb Thickness\nWTHK\nGeometry\n6\nFlange Thickness A\nFTKA\nGeometry\n7\nFlange Thickness B\nFTKB\nGeometry\n8\nRadius A\nRADA\nGeometry\n9\nRadius B\nRAD B\nGeometry\n10\nRadius C\nRAD C\nGeometry\n11\nCofG X Axis Offset\nCGXO\nGeometry\n12\nCofG Y Axis Offset\nCGYO\nGeometry\n13\nFlange Thickness Centre Offset\nFTCO\nGeometry\n14\nFlange Slope (degrees)\nFSLO\nGeometry\n15\nWeb Slope (degrees)\nWSLO\nGeometry\n16\nGage Line A\nGLNA\nData\n17\nGage Line B\nGLNB\nData\n18\nGage Line C\nGLNC\nData\n19\nMaximum Bolt Diameter A\nMBDA\nData\n20\nMaximum Bolt Diameter B\nMBDB\nData\n21\nMass per Unit Length\nMAUL\nData\n22\nSurface Area per meter\nSAPM\nData\n23\nCross Sectional Area\nXSAR\nData\n\nOnly the required common parameters are used to create each profile.\nNo.\nParameter Description\nDKEY\nData Type\n1\nDepth\nDPTH\nGeometry\n2\nWidth A\nWIDA\nGeometry\n3\nWidth B\nWIDB\nGeometry\n4\nWidth C\nWIDC\nGeometry\n5\nWeb Thickness\nWTHK\nGeometry\n6\nFlange Thickness A\nFTKA\nGeometry\n7\nFlange Thickness B\nFTKB\nGeometry\n8\nRadius A\nRADA\nGeometry\n9\nRadius B\nRAD B\nGeometry\n10\nRadius C\nRAD C\nGeometry\n11\nCofG X Axis Offset\nCGXO\nGeometry\n12\nCofG Y Axis Offset\nCGYO\nGeometry\n13\nFlange Thickness Centre Offset\nFTCO\nGeometry\n14\nFlange Slope (degrees)\nFSLO\nGeometry\n15\nWeb Slope (degrees)\nWSLO\nGeometry\n16\nGage Line A\nGLNA\nData\n17\nGage Line B\nGLNB\nData\n18\nGage Line C\nGLNC\nData\n19\nMaximum Bolt Diameter A\nMBDA\nData\n20\nMaximum Bolt Diameter B\nMBDB\nData\n21\nMass per Unit Length\nMAUL\nData\n22\nSurface Area per meter\nSAPM\nData\n23\nCross Sectional Area\nXSAR\nData\n\n\n\nNo.\nParameter Description\nDKEY\nData Type"}
{"Headers": "P-line Identification", "Content": "Each P-line is identified by a two, three or four letter code (known as its PKEY) which identifies its relative position in the 2D profile\nStandard P-lines\nAll GTYPES have a common set of 14 standard P-lines.\nPKEY\nDescription\nLBOT\nLeft Bottom\nCBOT\nCentre Bottom\nRBOT\nRight Bottom\nLMID\nLeft Middle\nCMID\nCentre Middle\nRMID\nRight Middle\nLTOP\nLeft Top\nCTOP\nCentre Top\nRTOP\nRight Top\nNA\nNeutral Axis\nBNA\nBottom Neutral Axis\nLNA\nLeft Neutral Axis\nRNA\nRight Neutral Axis\nTNA\nTop Neutral Axis\nPKEY\nDescription\nLBOT\nLeft Bottom\nCBOT\nCentre Bottom\nRBOT\nRight Bottom\nLMID\nLeft Middle\nCMID\nCentre Middle\nRMID\nRight Middle\nLTOP\nLeft Top\nCTOP\nCentre Top\nRTOP\nRight Top\nNA\nNeutral Axis\nBNA\nBottom Neutral Axis\nLNA\nLeft Neutral Axis\nRNA\nRight Neutral Axis\nTNA\nTop Neutral Axis\n9 of the P-lines are positioned at the corners and centrelines of a bounding box drawn around the profile.\n\nThe remaining 5 P-lines are positioned at the Neutral Axis (NA) and on the bounding box, where lines drawn through the NA in X and Y directions to intersect the bounding box.\n\nFor symmetrical profiles, some P-lines are coincident. For asymmetrical profiles, no P-lines are coincident.\n\nGeneric Type Specific P-lines\nGTYPE specific P-lines ensure the trimming functionality is maintained.\nPKEY\nDescription\nGTYPE\nCconnect\nNAL\nNeutral Axis Left\nPFI, PFT, TFI, TFT\nANY\nNAR\nNeutral Axis Right\nPFI, PFT, TFI, TFT\nANY\nIMID\nInside Middle\nANGL, PFC, TFC\nANY\nIBOT\nInside Bottom\nANGL\nANY\nAA\nCircumference 0\u00b0\nCTUB\nANY\nBB\nCircumference 15\u00b0\nCTUB\nunset\nCC\nCircumference 30\u00b0\nCTUB\nunset\nDD\nCircumference 45\u00b0\nCTUB\nunset\nEE\nCircumference 60\u00b0\nCTUB\nunset\nFF\nCircumference 75\u00b0\nCTUB\nunset\nGG\nCircumference 90\u00b0\nCTUB\nunset\nHH\nCircumference 105\u00b0\nCTUB\nunset\nII\nCircumference 120\u00b0\nCTUB\nunset\nJJ\nCircumference 135\u00b0\nCTUB\nunset\nKK\nCircumference 150\u00b0\nCTUB\nunset\nLL\nCircumference 165\u00b0\nCTUB\nunset\nMM\nCircumference 180\u00b0\nCTUB\nunset\nNN\nCircumference 195\u00b0\nCTUB\nunset\nOO\nCircumference 210\u00b0\nCTUB\nunset\nPP\nCircumference 225\u00b0\nCTUB\nunset\nQQ\nCircumference 240\u00b0\nCTUB\nunset\nRR\nCircumference 255\u00b0\nCTUB\nunset\nSS\nCircumference 270\u00b0\nCTUB\nunset\nTT\nCircumference 285\u00b0\nCTUB\nunset\nUU\nCircumference 300\nCTUB\nunset\nVV\nCircumference 315\u00b0\nCTUB\nunset\nWW\nCircumference 330\u00b0\nCTUB\nunset\nXX\nCircumference 345\u00b0\nCTUB\nunset\nNAAA\nNA 0\u00b0\nCTUB\nANY\nNACC\nNA 30\u00b0\nCTUB\nANY\nNAEE\nNA 60\u00b0\nCTUB\nANY\nNAGG\nNA 90\u00b0\nCTUB\nANY\nNAII\nNA 120\u00b0\nCTUB\nANY\nNAKK\nNA 150\u00b0\nCTUB\nANY\nNAMM\nNA 180\u00b0\nCTUB\nANY\nNAOO\nNA 210\u00b0\nCTUB\nANY\nNAQQ\nNA 240\u00b0\nCTUB\nANY\nNASS\nNA 270\u00b0\nCTUB\nANY\nNAUU\nNA 300\u00b0\nCTUB\nANY\nNAWW\nNA 330\u00b0\nCTUB\nANY\nLTFL\nLeft Top Flange\nPLTG, BOXG\nANY\nRTFL\nRight Top Flange\nPLTG, BOXG\nANY\nLBFL\nLeft Bottom Flange\nPLTG, BOXG\nANY\nRBFL\nRight Bottom Flange\nPLTG, BOXG\nANY\nITFL\nInside Top Flange Left\nPFI, PLTG\nunset\nITFR\nInside Top Flange Right\nPFI, PFC, PLTG\nunset\nIBFR\nInside Bottom Flange Right\nPFI, PFC, PLTG\nunset\nIBFL\nInside Bottom Flange Left\nPFI, PLTG\nunset\nHTLA\nHole Top Left Gage A\nPFI, PFT, TFI, TFT, TWT, TFWT, ZED, PLTG\nBOLT\nHTLB\nHole Top Left Gage B\nPFI, PFT, PLTG\nBOLT\nHTLC\nHole Top Left Gage C\nPFI, PFT, ANGL\nBOLT\nHTRA\nHole Top Right Gage A\nPFI, PFC, PFT, TFI, TFC, TFT, TWT, TFWT,PLTG\nBOLT\nHTRB\nHole Top Right Gage B\nPFI, PFT, PLTG\nBOLT\nHTRC\nHole Top Right Gage C\nPFI, PFT\nBOLT\nHBLA\nHole Bottom Left Gage A\nPFI, TFI, PLTG\nBOLT\nHBLB\nHole Bottom Left Gage B\nPFI, ANGL, PLTG\nBOLT\nHBLC\nHole Bottom Left Gage C\nPFI, PLTG\nBOLT\nHBRA\nHole Bottom Right Gage A\nPFI, PFC, TFI, TFC, ANGL, ZED, PLTG\nBOLT\nHBRB\nHole Bottom Right Gage B\nPFI, PLTG\nBOLT\nHBRC\nHole Bottom Right Gage C\nPFI, PLTG\nBOLT\nIFAT\nInside Face Top\nANGL\nunset\nIFAB\nInside Face Bottom\nANGL\nunset\nPKEY\nDescription\nGTYPE\nCconnect\nNAL\nNeutral Axis Left\nPFI, PFT, TFI, TFT\nANY\nNAR\nNeutral Axis Right\nPFI, PFT, TFI, TFT\nANY\nIMID\nInside Middle\nANGL, PFC, TFC\nANY\nIBOT\nInside Bottom\nANGL\nANY\nAA\nCircumference 0\u00b0\nCTUB\nANY\nBB\nCircumference 15\u00b0\nCTUB\nunset\nCC\nCircumference 30\u00b0\nCTUB\nunset\nDD\nCircumference 45\u00b0\nCTUB\nunset\nEE\nCircumference 60\u00b0\nCTUB\nunset\nFF\nCircumference 75\u00b0\nCTUB\nunset\nGG\nCircumference 90\u00b0\nCTUB\nunset\nHH\nCircumference 105\u00b0\nCTUB\nunset\nII\nCircumference 120\u00b0\nCTUB\nunset\nJJ\nCircumference 135\u00b0\nCTUB\nunset\nKK\nCircumference 150\u00b0\nCTUB\nunset\nLL\nCircumference 165\u00b0\nCTUB\nunset\nMM\nCircumference 180\u00b0\nCTUB\nunset\nNN\nCircumference 195\u00b0\nCTUB\nunset\nOO\nCircumference 210\u00b0\nCTUB\nunset\nPP\nCircumference 225\u00b0\nCTUB\nunset\nQQ\nCircumference 240\u00b0\nCTUB\nunset\nRR\nCircumference 255\u00b0\nCTUB\nunset\nSS\nCircumference 270\u00b0\nCTUB\nunset\nTT\nCircumference 285\u00b0\nCTUB\nunset\nUU\nCircumference 300\nCTUB\nunset\nVV\nCircumference 315\u00b0\nCTUB\nunset\nWW\nCircumference 330\u00b0\nCTUB\nunset\nXX\nCircumference 345\u00b0\nCTUB\nunset\nNAAA\nNA 0\u00b0\nCTUB\nANY\nNACC\nNA 30\u00b0\nCTUB\nANY\nNAEE\nNA 60\u00b0\nCTUB\nANY\nNAGG\nNA 90\u00b0\nCTUB\nANY\nNAII\nNA 120\u00b0\nCTUB\nANY\nNAKK\nNA 150\u00b0\nCTUB\nANY\nNAMM\nNA 180\u00b0\nCTUB\nANY\nNAOO\nNA 210\u00b0\nCTUB\nANY\nNAQQ\nNA 240\u00b0\nCTUB\nANY\nNASS\nNA 270\u00b0\nCTUB\nANY\nNAUU\nNA 300\u00b0\nCTUB\nANY\nNAWW\nNA 330\u00b0\nCTUB\nANY\nLTFL\nLeft Top Flange\nPLTG, BOXG\nANY\nRTFL\nRight Top Flange\nPLTG, BOXG\nANY\nLBFL\nLeft Bottom Flange\nPLTG, BOXG\nANY\nRBFL\nRight Bottom Flange\nPLTG, BOXG\nANY\nITFL\nInside Top Flange Left\nPFI, PLTG\nunset\nITFR\nInside Top Flange Right\nPFI, PFC, PLTG\nunset\nIBFR\nInside Bottom Flange Right\nPFI, PFC, PLTG\nunset\nIBFL\nInside Bottom Flange Left\nPFI, PLTG\nunset\nHTLA\nHole Top Left Gage A\nPFI, PFT, TFI, TFT, TWT, TFWT, ZED, PLTG\nBOLT\nHTLB\nHole Top Left Gage B\nPFI, PFT, PLTG\nBOLT\nHTLC\nHole Top Left Gage C\nPFI, PFT, ANGL\nBOLT\nHTRA\nHole Top Right Gage A\nPFI, PFC, PFT, TFI, TFC, TFT, TWT, TFWT,PLTG\nBOLT\nHTRB\nHole Top Right Gage B\nPFI, PFT, PLTG\nBOLT\nHTRC\nHole Top Right Gage C\nPFI, PFT\nBOLT\nHBLA\nHole Bottom Left Gage A\nPFI, TFI, PLTG\nBOLT\nHBLB\nHole Bottom Left Gage B\nPFI, ANGL, PLTG\nBOLT\nHBLC\nHole Bottom Left Gage C\nPFI, PLTG\nBOLT\nHBRA\nHole Bottom Right Gage A\nPFI, PFC, TFI, TFC, ANGL, ZED, PLTG\nBOLT\nHBRB\nHole Bottom Right Gage B\nPFI, PLTG\nBOLT\nHBRC\nHole Bottom Right Gage C\nPFI, PLTG\nBOLT\nIFAT\nInside Face Top\nANGL\nunset\nIFAB\nInside Face Bottom\nANGL\nunset\n\nExtra P-lines on bolt gage lines are available.\nRelevant P-lines must have the Cconnect attribute set to ANY to maintain trimming functionality.\nPKEY\nDescription\nLBOT\nLeft Bottom\nCBOT\nCentre Bottom\nRBOT\nRight Bottom\nLMID\nLeft Middle\nCMID\nCentre Middle\nRMID\nRight Middle\nLTOP\nLeft Top\nCTOP\nCentre Top\nRTOP\nRight Top\nNA\nNeutral Axis\nBNA\nBottom Neutral Axis\nLNA\nLeft Neutral Axis\nRNA\nRight Neutral Axis\nTNA\nTop Neutral Axis\nPKEY\nDescription\nGTYPE\nCconnect\nNAL\nNeutral Axis Left\nPFI, PFT, TFI, TFT\nANY\nNAR\nNeutral Axis Right\nPFI, PFT, TFI, TFT\nANY\nIMID\nInside Middle\nANGL, PFC, TFC\nANY\nIBOT\nInside Bottom\nANGL\nANY\nAA\nCircumference 0\u00b0\nCTUB\nANY\nBB\nCircumference 15\u00b0\nCTUB\nunset\nCC\nCircumference 30\u00b0\nCTUB\nunset\nDD\nCircumference 45\u00b0\nCTUB\nunset\nEE\nCircumference 60\u00b0\nCTUB\nunset\nFF\nCircumference 75\u00b0\nCTUB\nunset\nGG\nCircumference 90\u00b0\nCTUB\nunset\nHH\nCircumference 105\u00b0\nCTUB\nunset\nII\nCircumference 120\u00b0\nCTUB\nunset\nJJ\nCircumference 135\u00b0\nCTUB\nunset\nKK\nCircumference 150\u00b0\nCTUB\nunset\nLL\nCircumference 165\u00b0\nCTUB\nunset\nMM\nCircumference 180\u00b0\nCTUB\nunset\nNN\nCircumference 195\u00b0\nCTUB\nunset\nOO\nCircumference 210\u00b0\nCTUB\nunset\nPP\nCircumference 225\u00b0\nCTUB\nunset\nQQ\nCircumference 240\u00b0\nCTUB\nunset\nRR\nCircumference 255\u00b0\nCTUB\nunset\nSS\nCircumference 270\u00b0\nCTUB\nunset\nTT\nCircumference 285\u00b0\nCTUB\nunset\nUU\nCircumference 300\nCTUB\nunset\nVV\nCircumference 315\u00b0\nCTUB\nunset\nWW\nCircumference 330\u00b0\nCTUB\nunset\nXX\nCircumference 345\u00b0\nCTUB\nunset\nNAAA\nNA 0\u00b0\nCTUB\nANY\nNACC\nNA 30\u00b0\nCTUB\nANY\nNAEE\nNA 60\u00b0\nCTUB\nANY\nNAGG\nNA 90\u00b0\nCTUB\nANY\nNAII\nNA 120\u00b0\nCTUB\nANY\nNAKK\nNA 150\u00b0\nCTUB\nANY\nNAMM\nNA 180\u00b0\nCTUB\nANY\nNAOO\nNA 210\u00b0\nCTUB\nANY\nNAQQ\nNA 240\u00b0\nCTUB\nANY\nNASS\nNA 270\u00b0\nCTUB\nANY\nNAUU\nNA 300\u00b0\nCTUB\nANY\nNAWW\nNA 330\u00b0\nCTUB\nANY\nLTFL\nLeft Top Flange\nPLTG, BOXG\nANY\nRTFL\nRight Top Flange\nPLTG, BOXG\nANY\nLBFL\nLeft Bottom Flange\nPLTG, BOXG\nANY\nRBFL\nRight Bottom Flange\nPLTG, BOXG\nANY\nITFL\nInside Top Flange Left\nPFI, PLTG\nunset\nITFR\nInside Top Flange Right\nPFI, PFC, PLTG\nunset\nIBFR\nInside Bottom Flange Right\nPFI, PFC, PLTG\nunset\nIBFL\nInside Bottom Flange Left\nPFI, PLTG\nunset\nHTLA\nHole Top Left Gage A\nPFI, PFT, TFI, TFT, TWT, TFWT, ZED, PLTG\nBOLT\nHTLB\nHole Top Left Gage B\nPFI, PFT, PLTG\nBOLT\nHTLC\nHole Top Left Gage C\nPFI, PFT, ANGL\nBOLT\nHTRA\nHole Top Right Gage A\nPFI, PFC, PFT, TFI, TFC, TFT, TWT, TFWT,PLTG\nBOLT\nHTRB\nHole Top Right Gage B\nPFI, PFT, PLTG\nBOLT\nHTRC\nHole Top Right Gage C\nPFI, PFT\nBOLT\nHBLA\nHole Bottom Left Gage A\nPFI, TFI, PLTG\nBOLT\nHBLB\nHole Bottom Left Gage B\nPFI, ANGL, PLTG\nBOLT\nHBLC\nHole Bottom Left Gage C\nPFI, PLTG\nBOLT\nHBRA\nHole Bottom Right Gage A\nPFI, PFC, TFI, TFC, ANGL, ZED, PLTG\nBOLT\nHBRB\nHole Bottom Right Gage B\nPFI, PLTG\nBOLT\nHBRC\nHole Bottom Right Gage C\nPFI, PLTG\nBOLT\nIFAT\nInside Face Top\nANGL\nunset\nIFAB\nInside Face Bottom\nANGL\nunset\nNote:\nEach P-line is extruded in the design model to represent a line running along the length of a section.\n\n\n\nNote:\nStandard P-lines\nPKEY\nDescription\nPKEY\nDescription\nGTYPE\nCconnect"}
{"Headers": "Design Parameter Profiles - Generic Types", "Content": "The design parameter GTYPEs in the catalogue are:\nDesign Parameter Parallel Flange I\nDesign Parallel Flange Channel\nDesign Parameter Parallel Flange Tee\nDesign Parameter Angle\nDesign Parameter Rectangular Tube\nDesign Parameter Circular Tube\nDesign Parameter Z Profile\nDesign Parameter C Profile\nDesign Parameter Asymmetric Plate Girder\nDesign Parameter Box Girder\nDesign Parameter Flat Bar\nDesign Parameter Round Bar\nDesign Parameter Hexagonal Bar\nDesign Parameter Cone\nDesign Parameter Tapered Web I\nDesign parameter equivalents of all standard profiles are available with the exception of tapered flange profiles.\nDPFI\nDesign Parameter Parallel Flange I\nDPFC\nDesign Parallel Flange Channel\nDPFT\nDesign Parameter Parallel Flange Tee\nDANG\nDesign Parameter Angle\nDRTU\nDesign Parameter Rectangular Tube\nDCTU\nDesign Parameter Circular Tube\nDZED\nDesign Parameter Z Profile\nDCEE\nDesign Parameter C Profile\nDPLG\nDesign Parameter Asymmetric Plate Girder\nDBXG\nDesign Parameter Box Girder\nDFBA\nDesign Parameter Flat Bar\nDRBA\nDesign Parameter Round Bar\nDHBA\nDesign Parameter Hexagonal Bar\nDCON\nDesign Parameter Cone\nDTWI\nDesign Parameter Tapered Web I\nDPFI\nDPFI\nDPFI\nDPFC\nDPFC\nDPFC\nDPFT\nDPFT\nDPFT\nDANG\nDANG\nDANG\nDRTU\nDRTU\nDRTU\nDCTU\nDCTU\nDCTU\nDZED\nDZED\nDZED\nDCEE\nDCEE\nDCEE\nDPLG\nDPLG\nDPLG\nDBXG\nDBXG\nDBXG\nDFBA\nDFBA\nDFBA\nDRBA\nDRBA\nDRBA\nDHBA\nDHBA\nDHBA\nDCON\nDCON\nDCON\nDTWI\nDTWI\nDTWI\n\n\n"}
{"Headers": "Design Parameter Profiles - Parameters", "Content": "Design parameter profiles have the same DKEY and Descriptions as the equivalent standard profiles, however, only those parameters required for the profile are included in the Data Set.\nDP No.\nDesign Parameter Description\nDKEY\nData Type\nDESP 1\nDepth\nDPTH\nGeometry\nDESP 2\nWidth\nWIDA\nGeometry\nDESP 3\nWeb Thickness\nWTHK\nGeometry\nDESP 4\nFlange Thickness A\nFTKA\nGeometry\nDESP 5\nRoot Radius\nRADA\nGeometry\nDESP 6\nGage Line A\nGLNA\nData\nDESP 6\nGage Line B\nGLNB\nData\nDESP 7\nGage Line C\nGLNC\nData\nDESP 8\nMass per Unit Length\nMAUL\nData\nDESP 9\nSurface Area per meter\nSAPM\nData\nDESP 10\nCross Sectional Area\nXSAR\nData\nDP No.\nDesign Parameter Description\nDKEY\nData Type\nDESP 1\nDepth\nDPTH\nGeometry\nDESP 2\nWidth\nWIDA\nGeometry\nDESP 3\nWeb Thickness\nWTHK\nGeometry\nDESP 4\nFlange Thickness A\nFTKA\nGeometry\nDESP 5\nRoot Radius\nRADA\nGeometry\nDESP 6\nGage Line A\nGLNA\nData\nDESP 6\nGage Line B\nGLNB\nData\nDESP 7\nGage Line C\nGLNC\nData\nDESP 8\nMass per Unit Length\nMAUL\nData\nDESP 9\nSurface Area per meter\nSAPM\nData\nDESP 10\nCross Sectional Area\nXSAR\nData\n\nDP No.\nDesign Parameter Description\nDKEY\nData Type\nDESP 1\nDepth\nDPTH\nGeometry\nDESP 2\nWidth\nWIDA\nGeometry\nDESP 3\nWeb Thickness\nWTHK\nGeometry\nDESP 4\nFlange Thickness A\nFTKA\nGeometry\nDESP 5\nRoot Radius\nRADA\nGeometry\nDESP 6\nGage Line A\nGLNA\nData\nDESP 6\nGage Line B\nGLNB\nData\nDESP 7\nGage Line C\nGLNC\nData\nDESP 8\nMass per Unit Length\nMAUL\nData\nDESP 9\nSurface Area per meter\nSAPM\nData\nDESP 10\nCross Sectional Area\nXSAR\nData\n\n\n\nDP No.\nDesign Parameter Description\nDKEY\nData Type"}
{"Headers": "Display Levels & Obstruction Values", "Content": "Generally profile geometry sets have two representations, simple and actual, whilst enclosed shapes have internal obstruction volumes.\nThe display levels and obstruction values are as follows:\nRepresentation\nDrawing Levels\nObstruction Value\nSimple\n0 - 3\n0\nActual\n4 - 8\n2\nObstruction\n9 - 10\n1\nRepresentation\nDrawing Levels\nObstruction Value\nSimple\n0 - 3\n0\nActual\n4 - 8\n2\nObstruction\n9 - 10\n1\n\nGTYPE\nSimple\nActual\nObstruction\nPFI\nNone\nPFC\nNone\nRTUB\nCTUB\nBOXG\nFBAR\nNone\nCBAR\nNone\nGTYPE\nSimple\nActual\nObstruction\nPFI\n\n\nNone\nPFC\n\n\nNone\nRTUB\n\n\n\nCTUB\n\n\nBOXG\n\n\nFBAR\n\nNone\nCBAR\n\nNone\n\nRepresentation\nDrawing Levels\nObstruction Value\nSimple\n0 - 3\n0\nActual\n4 - 8\n2\nObstruction\n9 - 10\n1\nGTYPE\nSimple\nActual\nObstruction\nPFI\nNone\nPFC\nNone\nRTUB\nCTUB\nBOXG\nFBAR\nNone\nCBAR\nNone\n\n\n\nRepresentation\nDrawing Levels\nObstruction Value\nGTYPE\nSimple\nActual\nObstruction"}
{"Headers": "Catalogue Requirements for Bounded Plate Notches", "Content": "When creating notches in bounded plates for profiles, two types of notches may be formed.\nA Profile notch follows the outline of the structural profile and sets the plate back from the profile by the specified offset.\n\nAn Outline notch uses the extremities of the structural profile and sets the plate back from the extremities by the specified offset.\n\nAdditional geometry has been added to all the GTYPE geometry sets (GMSS) to enable the creation of Profile and Outline notches.\nFor Profile notches, the geometry is on Level 11 - 12 and is, essentially, a copy of the actual geometry on Level 4 - 8.\nFor Outline notches, the geometry is on Level 13 - 14 and is a rectangle covering the extremities of the profile.\nThe following GTYPEs, due to their shape, have a single additional geometry element on Level 11 - 14 that is used for both Profile and Outline notches:\nThe Level settings for the notch geometry should not be changed as the bounded plate utility uses the geometry on the stated levels.\nBOXG\nCTUB\nFBAR\nHBAR\nRBAR\nRTUB\nBOXG\nBOXG\nCTUB\nCTUB\nFBAR\nFBAR\nHBAR\nHBAR\nRBAR\nRBAR\nRTUB\nRTUB\n\n\n\nProfile\nOutline"}
{"Headers": "Sample Joints", "Content": "Details the sample joints of the DRAW module.\n\n\n"}
{"Headers": "Hierarchy", "Content": "The catalogue contains a separate CATA element for joints.\nThe hierarchy for joints is divided into joint groups, for example, similar joint types are grouped together in an STSE element.\nEach STSE element owns one or more STCA element, one for each joint type.\nEach STCA element owns all the elements that define the joint, for example, JOIN, GMSE, NGMS, PTSS, PTSE and DTSE.\n\nThe joint groups and sub-types are:\nBeam to Beam Joints\nBeam to Column Joints\nSplice Joints\nBracing Joints\nBaseplates\n\nEqual size beams\nSmall beams to large beams\nLarge beams to small beams\nEqual size beams\nEqual size beams\nSmall beams to large beams\nSmall beams to large beams\nLarge beams to small beams\nLarge beams to small beams\nBeam to column web\nBeam to column flange\nBeam to column web\nBeam to column web\nBeam to column flange\nBeam to column flange\nEqual sections\nUnequal sections\nEqual sections\nEqual sections\nUnequal sections\nUnequal sections\nBolted connections\nWelded connections\nBolted connections\nBolted connections\nWelded connections\nWelded connections\nRectangular\nCircular\nRectangular\nRectangular\nCircular\nCircular\n\n\n\nBeam to Beam Joints\nBeam to Column Joints\nSplice Joints\nBracing Joints\nBaseplates"}
{"Headers": "Joint Names", "Content": "Joints are named from a simple coding system comprising of:\nFor example: J1S1_WEL_PFC_PFC_001 and J2S6_FPL_CTUB_PFI_4H_001.\nAdditional information may be included, for example:\nThe suffix is either a sequential number or VAR (meaning the joint has no parameters, only design parameters and is variable).\nJoint group code\nSub-type code\nJoint type code\nOwning GTYPE\nAttached GTYPE\nAdditional information\nSuffix\nJoint group code\nJoint group code\nSub-type code\nSub-type code\nJoint type code\nJoint type code\nOwning GTYPE\nOwning GTYPE\nAttached GTYPE\nAttached GTYPE\nAdditional information\nAdditional information\nSuffix\nSuffix\n4H, 4 holes\n8H, 8 holes\n4H, 4 holes\n4H, 4 holes\n8H, 8 holes\n8H, 8 holes\n\n\n"}
{"Headers": "Joint Type Codes", "Content": "The table summarizes the joint type codes that are available in the catalogue.\nJoint Group\nJoint Group Description\nSub-type Code\nSub-Type\nJoint Type Code\nJoint Type\nJ1\nBeam to Beam Joints\nS1\nEqual Size Beams\nWEL\nWelded\nBWC\nBolted Web Cleats\nBEP\nBolted End Plate\nBFP\nBolted Fin Plate\nS2\nSmall to Large Beams\nWEL\nWelded\nBWC\nBolted Web Cleats\nBEP\nBolted End Plates\nBFP\nBolted Fin Plate\nPLH\nPlated Haunch\nSNS\nSnipe and Stiffeners\nSNG\nSnipe and Gusset\nS3\nLarge to Small Beam\nWEL\nWelded\nBWC\nBolted Web Cleats\nBEC\nBolted End Plates\nBFP\nBolted Fin Plate\nPLH\nPlated Haunch\nJ2\nBeam to Column Joints\nS4\nColumn Flange\nFPL\nFin Plate\nFEP\nFlexible End Plate\nFDE\nFull Depth End Plate\nBWC\nBolted Web Cleat\nS5\nColumn Web\nFPL\nFin Plate\nFEP\nFlexible End Plate\nFDE\nFull Depth End Plate\nBWC\nBolted Web Cleat\nTOE\nToe Plate and Stiffener\nS6\nTubular Column\nWEL\nWelded\nDOP\nDoubler Plate\nFPL\nFin Plate\nSEP\nStub Brkt End Plate\nJ3\nSplice Joints\nS7\nEqual Sections\nAPE\nApex Haunch (Moment)\nBSP\nBolted Splice Plates\nDPL\nDivision Plate\nEPL\nEnd Plates\nS8\nUnequal Sections\nBSP\nBolted Splice Plates\nDPL\nDivision Plate\nEPL\nEnd Plates\nJ4\nBracing Joints\nS9\nBolted Connection\nBOL\nBolted Connection x 2 Holes\nBOL\nBolted Connection x 4 Holes\nS10\nWelded Connection\nWN1\nWing Plate - 1 x Stiff\nWN3\nWing Plate - 3 x Stiff\nJ5\nBaseplate Joints\nS11\nBaseplate\nSQR_4H\nSqr./Rect.4 x Holes\nSqr./Rect.4 x Holes - Stiffs.\nSQR_6H\nSqr./Rect.6 x Holes\nSqr./Rect.6 x Holes - Stiffs.\nCIR_4H\nCircular 4 x Holes\nCircular 4 x Holes - Stiffs.\nCIR_6H\nCircular 6 x Holes\nCircular 6 x Holes -Stiffs.\nJoint Group\nJoint Group Description\nSub-type Code\nSub-Type\nJoint Type Code\nJoint Type\nJ1\nBeam to Beam Joints\nS1\nEqual Size Beams\nWEL\nWelded\nBWC\nBolted Web Cleats\nBEP\nBolted End Plate\nBFP\nBolted Fin Plate\nS2\nSmall to Large Beams\nWEL\nWelded\nBWC\nBolted Web Cleats\nBEP\nBolted End Plates\nBFP\nBolted Fin Plate\nPLH\nPlated Haunch\nSNS\nSnipe and Stiffeners\nSNG\nSnipe and Gusset\nS3\nLarge to Small Beam\nWEL\nWelded\nBWC\nBolted Web Cleats\nBEC\nBolted End Plates\nBFP\nBolted Fin Plate\nPLH\nPlated Haunch\nJ2\nBeam to Column Joints\nS4\nColumn Flange\nFPL\nFin Plate\nFEP\nFlexible End Plate\nFDE\nFull Depth End Plate\nBWC\nBolted Web Cleat\nS5\nColumn Web\nFPL\nFin Plate\nFEP\nFlexible End Plate\nFDE\nFull Depth End Plate\nBWC\nBolted Web Cleat\nTOE\nToe Plate and Stiffener\nS6\nTubular Column\nWEL\nWelded\nDOP\nDoubler Plate\nFPL\nFin Plate\nSEP\nStub Brkt End Plate\nJ3\nSplice Joints\nS7\nEqual Sections\nAPE\nApex Haunch (Moment)\nBSP\nBolted Splice Plates\nDPL\nDivision Plate\nEPL\nEnd Plates\nS8\nUnequal Sections\nBSP\nBolted Splice Plates\nDPL\nDivision Plate\nEPL\nEnd Plates\nJ4\nBracing Joints\nS9\nBolted Connection\nBOL\nBolted Connection x 2 Holes\nBOL\nBolted Connection x 4 Holes\nS10\nWelded Connection\nWN1\nWing Plate - 1 x Stiff\nWN3\nWing Plate - 3 x Stiff\nJ5\nBaseplate Joints\nS11\nBaseplate\nSQR_4H\nSqr./Rect.4 x Holes\nSqr./Rect.4 x Holes - Stiffs.\nSQR_6H\nSqr./Rect.6 x Holes\nSqr./Rect.6 x Holes - Stiffs.\nCIR_4H\nCircular 4 x Holes\nCircular 4 x Holes - Stiffs.\nCIR_6H\nCircular 6 x Holes\nCircular 6 x Holes -Stiffs.\n\nJoint Group\nJoint Group Description\nSub-type Code\nSub-Type\nJoint Type Code\nJoint Type\nJ1\nBeam to Beam Joints\nS1\nEqual Size Beams\nWEL\nWelded\nBWC\nBolted Web Cleats\nBEP\nBolted End Plate\nBFP\nBolted Fin Plate\nS2\nSmall to Large Beams\nWEL\nWelded\nBWC\nBolted Web Cleats\nBEP\nBolted End Plates\nBFP\nBolted Fin Plate\nPLH\nPlated Haunch\nSNS\nSnipe and Stiffeners\nSNG\nSnipe and Gusset\nS3\nLarge to Small Beam\nWEL\nWelded\nBWC\nBolted Web Cleats\nBEC\nBolted End Plates\nBFP\nBolted Fin Plate\nPLH\nPlated Haunch\nJ2\nBeam to Column Joints\nS4\nColumn Flange\nFPL\nFin Plate\nFEP\nFlexible End Plate\nFDE\nFull Depth End Plate\nBWC\nBolted Web Cleat\nS5\nColumn Web\nFPL\nFin Plate\nFEP\nFlexible End Plate\nFDE\nFull Depth End Plate\nBWC\nBolted Web Cleat\nTOE\nToe Plate and Stiffener\nS6\nTubular Column\nWEL\nWelded\nDOP\nDoubler Plate\nFPL\nFin Plate\nSEP\nStub Brkt End Plate\nJ3\nSplice Joints\nS7\nEqual Sections\nAPE\nApex Haunch (Moment)\nBSP\nBolted Splice Plates\nDPL\nDivision Plate\nEPL\nEnd Plates\nS8\nUnequal Sections\nBSP\nBolted Splice Plates\nDPL\nDivision Plate\nEPL\nEnd Plates\nJ4\nBracing Joints\nS9\nBolted Connection\nBOL\nBolted Connection x 2 Holes\nBOL\nBolted Connection x 4 Holes\nS10\nWelded Connection\nWN1\nWing Plate - 1 x Stiff\nWN3\nWing Plate - 3 x Stiff\nJ5\nBaseplate Joints\nS11\nBaseplate\nSQR_4H\nSqr./Rect.4 x Holes\nSqr./Rect.4 x Holes - Stiffs.\nSQR_6H\nSqr./Rect.6 x Holes\nSqr./Rect.6 x Holes - Stiffs.\nCIR_4H\nCircular 4 x Holes\nCircular 4 x Holes - Stiffs.\nCIR_6H\nCircular 6 x Holes\nCircular 6 x Holes -Stiffs.\n\n\n\nJoint Group\nJoint Group Description\nSub-type Code\nSub-Type\nJoint Type Code\nJoint Type"}
{"Headers": "Sample Fittings", "Content": "Details the sample fittings of the DRAW module.\n\n\n"}
{"Headers": "Convert Section, Joint and Fitting Elements", "Content": "To enable the use of the most recent structural functionality, it is necessary to convert Section (SCTN) elements to GENSEC elements. As part of the conversion process:\nRefer to Convert Sections for further information.\nThe profile specification of the GENSEC and FIXING elements must also be converted for compatibility with the most recent profile specification catalogue. Refer to Convert Profile Specification for further information.\nFitting (FITT) and Joint (SJOI) elements are converted to Fitting (FIXING) and Joint (FIXING) elements.\nPrimary Node (PNODE)/Primary Joint (PJOI) elements are converted to End Datum (ENDATU) elements that own a Joint (FIXING) with the referenced joint.\nFitting (FITT) and Joint (SJOI) elements are converted to Fitting (FIXING) and Joint (FIXING) elements.\nFitting (FITT) and Joint (SJOI) elements are converted to Fitting (FIXING) and Joint (FIXING) elements.\nPrimary Node (PNODE)/Primary Joint (PJOI) elements are converted to End Datum (ENDATU) elements that own a Joint (FIXING) with the referenced joint.\nPrimary Node (PNODE)/Primary Joint (PJOI) elements are converted to End Datum (ENDATU) elements that own a Joint (FIXING) with the referenced joint.\n\n\n\nConvert Sections\nConvert Profile Specification\nConvert Sections\nConvert Profile Specification"}
{"Headers": "Convert Sections", "Content": "Converts Section (SCTN) elements to General Section (GENSEC) elements. Section child elements are also converted to appropriate elements.\nThe conversion of SCTN elements to GENSEC elements is an administration task, access is only available to users with administration rights (member of the STRUADMIN team).\n\nThe Add Elements part of the Convert SCTN/GENSEC window allows the administrator to select the SCTN elements for conversion.\nAdd Elements\nAllows the administrator to select the elements to convert. The administrator can select individual SCTN elements or convert all elements that are contained in a SITE, ZONE, STRU, FRMW or SBFR.\nSelect Current Element from the drop-down list to add the currently selected element to the list of selected elements.\nSelect Element Members from the drop-down list to add the members of the currently selected element to the list of selected elements.\nClick Add to populate the list of selected elements with the current selection.\nNamed Element\nInput an element name in the field and click Add to add an element to the list of selected elements.\nAdd Elements\nAllows the administrator to select the elements to convert. The administrator can select individual SCTN elements or convert all elements that are contained in a SITE, ZONE, STRU, FRMW or SBFR.\nSelect Current Element from the drop-down list to add the currently selected element to the list of selected elements.\nSelect Element Members from the drop-down list to add the members of the currently selected element to the list of selected elements.\nClick Add to populate the list of selected elements with the current selection.\nNamed Element\nInput an element name in the field and click Add to add an element to the list of selected elements.\nThe Selected Elements part of the Convert SCTN/GENSEC window allows the administrator to view and modify the elements included in the conversion.\n\nWhen the conversion is complete, the Initial SCTNs and Final GENSECs columns are populated with the number of original sections and the number of converted sections.\nRight-click on the list of selected elements to display a drop-down menu.\n\nRemove Selected Element(s)\nClick to remove the currently selected elements from the list of selected elements.\nRemove all elements\nClick to remove all elements from the list of selected elements.\nEnhance SCTNs in 3D View\nClick to highlight the currently selected elements in the 3D view.\nUnenhance all elements\nClick to remove the highlight in the 3D view for the currently selected elements.\nNavigate to\nClick to navigate to the currently selected element in the 3D view and the Model Explorer.\nExport to Excel\nAllows the administrator to export the list of selected elements to an Excel file. Click to display the Save to Excel window. The administrator can navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the list of selected elements in the Print Preview window.\nRemove Selected Element(s)\nClick to remove the currently selected elements from the list of selected elements.\nRemove all elements\nClick to remove all elements from the list of selected elements.\nEnhance SCTNs in 3D View\nClick to highlight the currently selected elements in the 3D view.\n\nUnenhance all elements\nClick to remove the highlight in the 3D view for the currently selected elements.\nNavigate to\nClick to navigate to the currently selected element in the 3D view and the Model Explorer.\nExport to Excel\nAllows the administrator to export the list of selected elements to an Excel file. Click to display the Save to Excel window. The administrator can navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the list of selected elements in the Print Preview window.\nThe Conversion Summary part of the Convert SCTN/GENSEC window allows the administrator to view the summary for converted elements.\n\nThe Log File part of the Convert SCTN/GENSEC window allows the administrator to define the location of the conversion summary log file.\n\nClick Browse to open the Log File for Convert SCTN to GENSEC Process window, the administrator can navigate to the required location and modify the filename of the log file.\nClick Apply to convert the SCTN elements to GENSEC elements.\nDuring conversion, a progress bar displays in the bottom right corner of the application window, allowing the administrator to track conversion progress.\n\nWhen the SCTN to GENSEC conversion is complete, the GENSEC elements display in the Model Explorer. All FITT and SJOI elements are converted to FIXING elements.\n\nThe converted elements are highlighted in the 3D view.\n\nThe example is an extract of a log file created when SCTN to GENSEC conversion is complete.\nAdd Elements\nAllows the administrator to select the elements to convert. The administrator can select individual SCTN elements or convert all elements that are contained in a SITE, ZONE, STRU, FRMW or SBFR.\nSelect Current Element from the drop-down list to add the currently selected element to the list of selected elements.\nSelect Element Members from the drop-down list to add the members of the currently selected element to the list of selected elements.\nClick Add to populate the list of selected elements with the current selection.\nNamed Element\nInput an element name in the field and click Add to add an element to the list of selected elements.\nRemove Selected Element(s)\nClick to remove the currently selected elements from the list of selected elements.\nRemove all elements\nClick to remove all elements from the list of selected elements.\nEnhance SCTNs in 3D View\nClick to highlight the currently selected elements in the 3D view.\nUnenhance all elements\nClick to remove the highlight in the 3D view for the currently selected elements.\nNavigate to\nClick to navigate to the currently selected element in the 3D view and the Model Explorer.\nExport to Excel\nAllows the administrator to export the list of selected elements to an Excel file. Click to display the Save to Excel window. The administrator can navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the list of selected elements in the Print Preview window.\n\n\n\nAdd Elements\nConvert SCTN/GENSEC\nAdd Elements\nCurrent Element\nElement Members\nAdd\nNamed Element\nAdd\nSelected Elements\nConvert SCTN/GENSEC\nRemove Selected Element(s)\nRemove all elements\nEnhance SCTNs in 3D View\nUnenhance all elements\nNavigate to\nExport to Excel\nSave to Excel\nPrint Preview\nPrint Preview\nConversion Summary\nConvert SCTN/GENSEC\nLog File\nConvert SCTN/GENSEC\nBrowse\nLog File for Convert SCTN to GENSEC Process\nApply"}
{"Headers": "Convert Profile Specification", "Content": "Converts the profile specification of GENSEC and FIXING elements for compatibility with the most recent profile specification catalogue.\nThe profile specification conversion of GENSEC and FIXING elements is an administration task, access is only available to users with administration rights (member of the STRUADMIN team).\nThe Convert Profile Sprefs window allows the administrator to convert the profile specification of GENSEC and FIXING elements.\n\nThe Add Elements part of the Convert Profile Sprefs window allows the administrator to select the GENSEC elements for conversion.\nAdd Elements\nAllows the administrator to select the elements to convert. The administrator can select individual GENSEC elements or convert all elements that are contained in a SITE, ZONE, STRU, FRMW or SBFR.\nSelect Current Element from the drop-down list to add the currently selected element to the list of selected elements.\nSelect Element Members from the drop-down list to add the members of the currently selected element to the list of selected elements.\nClick Add to populate the list of selected elements with the current selection.\nNamed Element\nInput an element name in the field and click Add to add an element to the list of selected elements.\nAdd Elements\nAllows the administrator to select the elements to convert. The administrator can select individual GENSEC elements or convert all elements that are contained in a SITE, ZONE, STRU, FRMW or SBFR.\nSelect Current Element from the drop-down list to add the currently selected element to the list of selected elements.\nSelect Element Members from the drop-down list to add the members of the currently selected element to the list of selected elements.\nClick Add to populate the list of selected elements with the current selection.\nNamed Element\nInput an element name in the field and click Add to add an element to the list of selected elements.\nThe Selected Elements part of the Convert Profile Sprefs window allows the administrator to view and modify the elements included in the conversion.\n\nWhen the conversion is complete, the Attempted and Succeeded columns are populated with the number of profile specifications that were attempted for conversion and the number that were successfully converted.\nRight-click on the list of selected elements to display a drop-down menu.\n\nRemove Selected Element(s)\nClick to remove the currently selected elements from the list of selected elements.\nRemove all elements\nClick to remove all elements from the list of selected elements.\nEnhance Profiles in 3D View\nClick to highlight the currently selected profiles in the 3D view.\nUnenhance all elements\nClick to remove the highlight in the 3D view for the currently selected profiles.\nNavigate to\nClick to navigate to the currently selected element in the 3D view and the Model Explorer.\nExport to Excel\nAllows the administrator to export the list of selected elements to an Excel file. Click to display the Save to Excel window. The administrator can navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the list of selected elements in the Print Preview window.\nRemove Selected Element(s)\nClick to remove the currently selected elements from the list of selected elements.\nRemove all elements\nClick to remove all elements from the list of selected elements.\nEnhance Profiles in 3D View\nClick to highlight the currently selected profiles in the 3D view.\n\nUnenhance all elements\nClick to remove the highlight in the 3D view for the currently selected profiles.\nNavigate to\nClick to navigate to the currently selected element in the 3D view and the Model Explorer.\nExport to Excel\nAllows the administrator to export the list of selected elements to an Excel file. Click to display the Save to Excel window. The administrator can navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the list of selected elements in the Print Preview window.\nThe Mapping File part of the Convert Profile Sprefs window allows the administrator to define the location of the mapping file used for the conversion.\n\nClick Browse to open the Mapping File window, the administrator can navigate to the required location and select an alternative mapping file.\nThe example is an extract of a mapping file that indicates the old and new profile specifications.\nThe Conversion Summary part of the Convert Profile Sprefs window allows the administrator to view the summary for converted elements.\n\nThe Log File part of the Convert Profile Sprefs window allows the administrator to define the location of the conversion summary log file.\n\nClick Browse to open the Log File for Convert SCTN to GENSEC Process window, the administrator can navigate to the required location and modify the filename of the log file.\nClick Apply to convert the profile specifications.\nA Confirm window displays informing the administrator that the catalogue specifications must be translated before the conversion of profile specifications. Click Yes to continue with the conversion.\n\nDuring conversion, a progress bar displays in the bottom right corner of the application window, allowing the administrator to track conversion progress.\n\nWhen the profile specification conversion is complete, The converted elements are highlighted in the 3D view.\n\nThe example is an extract of a log file created when profile specification conversion is complete.\nAdd Elements\nAllows the administrator to select the elements to convert. The administrator can select individual GENSEC elements or convert all elements that are contained in a SITE, ZONE, STRU, FRMW or SBFR.\nSelect Current Element from the drop-down list to add the currently selected element to the list of selected elements.\nSelect Element Members from the drop-down list to add the members of the currently selected element to the list of selected elements.\nClick Add to populate the list of selected elements with the current selection.\nNamed Element\nInput an element name in the field and click Add to add an element to the list of selected elements.\nRemove Selected Element(s)\nClick to remove the currently selected elements from the list of selected elements.\nRemove all elements\nClick to remove all elements from the list of selected elements.\nEnhance Profiles in 3D View\nClick to highlight the currently selected profiles in the 3D view.\nUnenhance all elements\nClick to remove the highlight in the 3D view for the currently selected profiles.\nNavigate to\nClick to navigate to the currently selected element in the 3D view and the Model Explorer.\nExport to Excel\nAllows the administrator to export the list of selected elements to an Excel file. Click to display the Save to Excel window. The administrator can navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the list of selected elements in the Print Preview window.\nNote:\nSCTN, FITT and SJOI elements must be converted to GENSEC and FIXING elements prior to conversion of the profile specification. Refer to Convert Sections for further information.\n\n\n\nConvert Sections\nNote:\nConvert Sections\nConvert Profile Sprefs\nAdd Elements\nConvert Profile Sprefs\nAdd Elements\nCurrent Element\nElement Members\nAdd\nNamed Element\nAdd\nSelected Elements\nConvert Profile Sprefs\nRemove Selected Element(s)\nRemove all elements\nEnhance Profiles in 3D View\nUnenhance all elements\nNavigate to\nExport to Excel\nSave to Excel\nPrint Preview\nPrint Preview\nMapping File\nConvert Profile Sprefs\nBrowse\nMapping File\nConversion Summary\nConvert Profile Sprefs\nLog File\nConvert Profile Sprefs\nBrowse\nLog File for Convert SCTN to GENSEC Process\nApply\nConfirm"}
{"Headers": "Stairs, Ladders and Handrails", "Content": "The Stairs, Ladders and Handrails (SLH) application allows you to design and detail stairs, ladders and handrails within a full 3D environment, with the support of tools to produce a clash free design.\nIt is not recommended to copy projects created in the AVEVA Access, Stairs and Ladders application into SLH.\n\n\n"}
{"Headers": "Stairs, Ladders and Handrails Hierarchy", "Content": "Below the administrative elements (STRU, FRMW or SBFR) in SLH, the specific elements are:\nThe SLH specific hierarchy is also governed by the representation mode that the SLH element is created in. Refer to Layout Hierarchy and Detail Hierarchy for further information.\nStair Flights (STRFLT)\nStep Ladders (SLADDR)\nLadder (RLADDR)\nHandrail (HANDRA)\nStair Flights (STRFLT)\nStair Flights (STRFLT)\nStep Ladders (SLADDR)\nStep Ladders (SLADDR)\nLadder (RLADDR)\nLadder (RLADDR)\nHandrail (HANDRA)\nHandrail (HANDRA)\n\n\n\nLayout Hierarchy\nDetail Hierarchy\nLayout Hierarchy\nDetail Hierarchy"}
{"Headers": "Stairs, Ladders and Handrails Window", "Content": "All the tasks that are associated with the creation or modification of SLH elements are available for selection from a central window, which acts as a task hub.\nYou are presented with a series of windows initially focusing on the essential detail, then further windows focusing on additional detail (progressive disclosure), prompting you for input.\nAfter inputting information into the window, you are always returned to the central window allowing for workflow to continue.\nThe essential and additional detail required is determined by standards and defaults. Refer to Standards and Defaults for further information.\n\n\n\nStandards and Defaults\nStandards and Defaults"}
{"Headers": "Standards and Defaults", "Content": "Government, industry or project standards are used to make sure conformance for the SLH elements is achieved. The creation and modification of standards is an administrative task. Refer to Standard for further information.\nDefaults are related to the standards and are organized and stored in default files. These default files are used to make sure a particular setting or value is assigned automatically, thus enforcing good practice with minimal input. The creation and modification of defaults is an administrative task. Refer to Defaults for further information.\n\n\n\nStandard\nDefaults\nStandard\nDefaults"}
{"Headers": "Representation Mode", "Content": "You can use two modes whilst working with SLH.\nLayout Mode\nThe Layout mode can be used by different disciplines, the layout mode allows you to quickly create a flight of stairs, ladders or handrails whose geometry complies with the selected standard with minimal input. The flight of stairs, ladders or handrails are graphically displayed as a standard representation, which can then be clash tested or drafted.\nDetail Mode\nThe Detail mode is intended for use by structural designers, which enables you to create detailed stair flights, ladders or handrails which can then be clash tested and drafted.\nNote:\nA stair flight, ladder or handrail element created in the Layout mode can be modified to produce a Detail mode representation of the element, without deletion or re-creation. An element created in the Detail mode cannot be modified to produce the element in the Layout mode.\n\n\n\nLayout Mode\nDetail Mode\nNote:\ncan\ncannot"}
{"Headers": "Stair Flight", "Content": "Each stair flight element displays in the 3D view as a Stair Flight (STRFLT) element. The STRFLT element is a top level administrative element owned by the structural administrative elements.\nThe STRFLT element enables you to create a rule based linear Stair Flight with its assembly broken down into its logical component parts, the lower level elements of SLH hierarchy are used to represent the detail of the STRFLT element in the 3D model.\nNote:\nAt the time of release, a STRSTR element cannot be created for a Concrete Stair Flight.\n\n\n\nNote:"}
{"Headers": "Layout Hierarchy", "Content": "When the SLADDR element is created in layout mode, below the SLADDR level in SLH hierarchy, the SLH specific elements are:\n\nSTEP LADDER RAIL (SLRAIL)\nSLRAIL elements are only available during the creation of a Layout SLADDR element. The creation of all other handrails is a separate task. Refer to Handrails for further information.\n\n\n\nHandrails\nSTEP LADDER RAIL (SLRAIL)\nHandrails"}
{"Headers": "Detail Hierarchy", "Content": "When the element is created in detail mode or converted from layout mode, below the SLADDR level in SLH hierarchy, the SLH specific elements are:\n\nTOP EXTENSION (TOPEXT)\nTOPEXT owns the PANEL element used to 3D model the physical representation of the top extension of the Step Ladder. It is defined by the extrusion of a profile representing the panel's shape (the Panel Loop (PLOOP)) through a given distance (equivalent to the panel thickness). A PAVE element defines each vertex of a Panel Loop or each connected end of a Panel Linear Joint.\nTREAD SET (TREADS)\nThe TREADS element is used to manage the ownership of individual TREAD elements.\nTREAD (TREAD)\nTREAD owns the elements used to 3D 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 SLADDR.\nPANEL, TMPL or Catalogue elements can be used to 3D model the rise or tread in the SLADDR.\nSTAIR STRINGER (STRSTR)\nSTRSTR owns the two GENSEC elements used to 3D model the main supports of the Step Ladder. The GENSEC elements are automatically mitred by the application at the upper and lower elevations of the STRSTR, dependent upon the relevant selections.\n\n\n\nTOP EXTENSION (TOPEXT)\nTREAD SET (TREADS)\nTREAD (TREAD)\nSTAIR STRINGER (STRSTR)"}
{"Headers": "Create Stair Flight", "Content": "Creates a Stair Flight (STRFLT) element.\nAll of the STRFLT creation tasks are initiated from a central Create Stair Flight window which acts a task hub. The General Attributes window is always initially displayed, regardless of the selected SLH element or representation mode, further windows are presented (progressive disclosure) prompting for input.\n\nMandatory entry required\n\nMandatory entry required\n\nMandatory entry required\n\n\n\nCreate Stair Flight\nGeneral Attributes"}
{"Headers": "Layout Mode", "Content": "By default the Representation Mode is Layout and the General Attributes part of the Create Stair Flight window displays.\n\n\n\n\nLayout\nGeneral Attributes\nCreate Stair Flight"}
{"Headers": "General Attributes", "Content": "From the General Attributes part of the Create Handrail window, select a default specification from the drop-down list of available specifications, if there are no default specifications, you must contact the administrator.\nIn the Name field, type the name for the new handrail, or select Autoname Handrail.\nIf required, input a description for the handrail in the Description field.\nThe Height field is automatically populated with the default height of the handrail, once the default specification has been selected.\n\nUse the Single Rail check box to specify if the single handrail is to be wall mounted or floor mounted. Select the Single Rail check box, then Wall Mounted or Floor Mounted.\nClick Next to display the Handrail Details part of the Create Handrail window. Refer to Handrail Details for further information.\nClick Cancel to discard any inputs and close the Create Handrail window.\nNote:\nIf you select the Single Rail check box, kickplates are not available for selection.\n\n\n\nHandrail Details\nGeneral Attributes\nCreate Handrail\nName\nAutoname Handrail\nDescription\nHeight\nSingle Rail\nSingle Rail\nWall Mounted\nFloor Mounted\nNote:\nSingle Rail\nNext\nHandrail Details\nCreate Handrail\nHandrail Details\nCancel\nCreate Handrail"}
{"Headers": "Reference Points", "Content": "To create a new SLADDR element, you must select a start (FROM Reference Point) and end (TO Reference Point) from the Reference Points part of the Create Step Ladder window. By default no reference points are selected.\n\nThe functionality available in the Reference Points part of the Create Step Ladder window is identical to the Reference Points part of the Create Stair Flight window (with the exception of the Edge to Calculated Position functionality). Refer to Reference Points for further information.\nClick Next to display the Step Ladder Configuration part of the Create Step Ladder window. Refer to Step Ladder Configuration for further information\nClick Back to return to the General Attributes part of the Create Step Ladder window.\nClick Cancel to discard any inputs and close the Create Step Ladder window.\n\n\n\nReference Points\nStep Ladder Configuration\n(FROM Reference Point)\n(TO Reference Point)\nReference Points\nCreate Step Ladder\nReference Points\nCreate Step Ladder\nReference Points\nCreate Stair Flight\nEdge to Calculated Position\nReference Points\nNext\nStep Ladder Configuration\nCreate Step Ladder\nStep Ladder Configuration\nBack\nGeneral Attributes\nCreate Step Ladder\nCancel\nCreate Step Ladder"}
{"Headers": "Stair Configuration", "Content": "The functionality available in the Step Ladder Configuration part of the Create Step Ladder window is identical to the Stair Configuration part of the Create Stair Flight window (with the exception of the Handrail Configuration drop-down list). Refer to Stair Configuration for further information.\n\n\n\nStair Configuration\nStep Ladder Configuration\nCreate Step Ladder\nStair Configuration\nCreate Stair Flight\nHandrail Configuration\nStair Configuration"}
{"Headers": "Extension and Landings", "Content": "The Extension and Landings part of the Create Stair Flight window, with Detail mode selected, has mostly the same functionality as that available from the Layout mode with the exception of the Stringer functionality.\nIf required, you can crank the bottom of the stringers or extend them through the floor.\n\nCranked Bottom\nFrom the Stringer Options part of the Create Stair Flight window, select the Crank Bottom of Stringers check box (only for stairs to a plane). The stringers of the stair are cranked at the selected plane and displayed in the 3D view.\n\nExtend Bottom Through Floor\nWhere the bottom of a stair flight is coming down to a plane which may be, for example a grated or plated platform, the stringers may need to be extended through the thickness of the grating/plating to support members below.\nFrom the Stringer Options part of the Create Stair Flight window, select the Extend Bottom Through Floor check box. The stringers of the stair are cranked at the selected plane and displayed in the 3D view.\n\nLanding Floor Finish Level\nYou can specify if the landing (represented as a PANE element) is on top of or flush with TOS of the stringers, from the Finished Floor Level part of the Extensions and Landings window, select Above TOS or Flush with TOS.\n\nAbove TOS\nFlush TOS\n\nAbove TOS\n\n\nFlush TOS\n\nClick Next to display the Specifications part of the Create Stair Flight window. Refer to Specifications for further information.\nClick Back to return to the Stair Configuration part of the Create Stair Flight window.\nClick Cancel to discard any inputs and close the Create Stair Flight window.\nAbove TOS\nFlush TOS\n\n\n\nSpecifications\nExtension and Landings\nCreate Stair Flight\nDetail\nLayout\nCranked Bottom\nStringer Options\nCreate Stair Flight\nCrank Bottom of Stringers\nExtend Bottom Through Floor\nStringer Options\nCreate Stair Flight\nExtend\nBottom Through Floor\nLanding Floor Finish Level\nFinished Floor Level\nExtensions and Landings\nAbove TOS\nFlush with TOS\nAbove TOS\nFlush TOS\nNext\nSpecifications\nCreate Stair\nFlight\nSpecifications\nBack\nStair Configuration\nCreate Stair Flight\nCancel\nCreate Stair Flight"}
{"Headers": "Rises Above/Below", "Content": "Use to move the intermediate landing up or down the STRFLT within the boundaries set by the defaults.\nFrom the Rises Above or Rises Below boxes, select the number of rises above and below the landing. If you change the number of rises above the landing the number of rises below the intermediate landing automatically adjusts within the height constraint and vice versa.\n\nNote:\nA minimum of two treads at the bottom and top of any stair flight is required.\n\n\n\nRises Above\nRises Below\nNote:"}
{"Headers": "Pick Tread", "Content": "Use to pick the location of the intermediate landing in the 3D view, the treads available for selection are displayed solid objects.\n\nClick Pick Tread, you are prompted to SLH Stair Flight - Pick an aid line Pick Aid.\n\nThe intermediate landing automatically moves up or down depending upon the selection made in the 3D view, the Rises Above and Rises Below boxes are also automatically updated to reflect the amendment.\nFinished Floor Level\nAt the time of this release, a TOS Finished Floor Level is the only option available.\n\n\nTo create the new stair flight element, click Build Stair Flight.\nUpon creation of the STRFLT element, the MODEL module analyzes the horizontal (Overall Going) and vertical (Overall Rise) distances between the Lower and Upper Work Points (LWP/UWP) and validates 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 creates the Stair Flight and populates the attributes with the appropriate data.\nClick Back to return to the Stair Configuration part of the Create Stair Flight window.\nClick Cancel to discard any inputs and close the Create Stair Flight window.\nNote:\nA minimum of two treads at the bottom and top of any stair flight is required.\n\n\n\nPick Tread\nSLH Stair Flight - Pick an aid line Pick Aid.\nNote:\nRises Above\nRises Below\nFinished Floor Level\nBuild Stair Flight\nBack\nStair Configuration\nCreate Stair Flight\nCancel\nCreate Stair Flight"}
{"Headers": "Detail Mode", "Content": "Detail mode is intended for use by structural designers, which enables you to create detailed step ladders which can then be clash tested and drafted.\n\n\n\n"}
{"Headers": "Specifications", "Content": "The Specifications part of the Create Rung Ladder window displays all the available specifications for the rung ladder from the defaults.\n\nThe choices made on previous parts of the Create Rung Ladder determines which specifications are available for selection.\nFrom the Ladder Specifications part of the Create Rung Ladder window:\nRung\nThe selected defaults determines which rungs can be used for different width ranges. Once you have selected the width of the ladder, the rungs available for selection are then filtered.\nStile\nThe selected defaults determines which stiles can be used for different height ranges. Once you have selected the top and bottom elevations and the height of ladder has been calculated, the stiles available for selection are then filtered.\nRung\nThe selected defaults determines which rungs can be used for different width ranges. Once you have selected the width of the ladder, the rungs available for selection are then filtered.\nStile\nThe selected defaults determines which stiles can be used for different height ranges. Once you have selected the top and bottom elevations and the height of ladder has been calculated, the stiles available for selection are then filtered.\nFrom the Cage Specifications part of the Create Rung Ladder window:\nHoop\nThe hoop specifications available for selection are determined by the selected defaults.\nTop Hoop\nThe top hoop specifications available for selection are determined by the selected defaults.\nThe functionality is only available if top hoops are defined for the selected defaults.\nBottom Hoop\nThe bottom hoop specifications available for selection are determined by the selected defaults.\nThe functionality is only available if bottom hoops are defined for the selected defaults.\nBar\nThe bar specifications available for selection are determined by the selected defaults.\nHoop\nThe hoop specifications available for selection are determined by the selected defaults.\nTop Hoop\nThe top hoop specifications available for selection are determined by the selected defaults.\nThe functionality is only available if top hoops are defined for the selected defaults.\nBottom Hoop\nThe bottom hoop specifications available for selection are determined by the selected defaults.\nThe functionality is only available if bottom hoops are defined for the selected defaults.\nBar\nThe bar specifications available for selection are determined by the selected defaults.\nThe gate specifications available for selection from the Gate drop-down list are determined by the default specification. The default is None.\nClick Next to display the Ladder Details part of the Create Rung Ladder window. Refer to Ladder Details for further information.\nClick Back to return to the Ladder Assembly part of the Create Rung Ladder window.\nClick Cancel to discard any inputs and close the Create Rung Ladder window.\nRung\nThe selected defaults determines which rungs can be used for different width ranges. Once you have selected the width of the ladder, the rungs available for selection are then filtered.\nStile\nThe selected defaults determines which stiles can be used for different height ranges. Once you have selected the top and bottom elevations and the height of ladder has been calculated, the stiles available for selection are then filtered.\nHoop\nThe hoop specifications available for selection are determined by the selected defaults.\nTop Hoop\nThe top hoop specifications available for selection are determined by the selected defaults.\nThe functionality is only available if top hoops are defined for the selected defaults.\nBottom Hoop\nThe bottom hoop specifications available for selection are determined by the selected defaults.\nThe functionality is only available if bottom hoops are defined for the selected defaults.\nBar\nThe bar specifications available for selection are determined by the selected defaults.\n\n\n\nLadder Details\nSpecifications\nCreate Rung Ladder\nCreate Rung Ladder\nLadder Specifications\nCreate Rung Ladder\nRung\nStile\nCage Specifications\nCreate Rung Ladder\nHoop\nTop Hoop\nBottom Hoop\nBar\nGate\nNone\nNext\nLadder Details\nCreate Rung Ladder\nLadder Details\nBack\nLadder Assembly\nCreate Rung Ladder\nCancel\nCreate Rung Ladder"}
{"Headers": "Step Ladder", "Content": "Each step ladder element displays in the 3D view as a Step Ladder (SLADDR) element. The SLADDR element is a top level administrative element owned by the structural administrative elements.\nThe SLADDR element enables you to create a rule based linear Step Ladder with its assembly broken down into its logical component parts, the lower level elements of SLH hierarchy are used to represent the detail of the SLADDR element in the 3D model.\n\n\n"}
{"Headers": "Create Step Ladder", "Content": "Creates a Step Ladder (SLADDR) element.\nAll of the SLADDR creation tasks are initiated from a central Create Step Ladder window which acts as a task hub. The General Attributes part of the window is always initially displayed, regardless of the selected SLH element or representation mode, further windows are presented (progressive disclosure) prompting for input.\n\nMandatory entry required\n\nMandatory entry required\n\nMandatory entry required\n\n\n\nCreate Step Ladder\nGeneral Attributes"}
{"Headers": "Layout Mode", "Content": "By default the Representation Mode is Layout and the General Attributes part of the Create Step Ladder window displays.\n\n\n\n\nLayout\nGeneral Attributes\nCreate Step Ladder"}
{"Headers": "Step Ladder Configuration", "Content": "By default, the Step Ladder Configuration part of the Create Step Ladder window is populated with all the allowable configurations.\nThe configurations that display in the Step Ladder Configuration part of the Create Step Ladder window is dependent upon which defaults are set by the administrator.\nEdge to plane, top extension\nEdge to plane, no extension\nEdge to edge, top extension\nEdge to edge, no extension\n\nEdge to plane, top extension\n\nEdge to plane, no extension\n\nEdge to edge, top extension\n\nEdge to edge, no extension\n\nThe functionality available in the Step Ladder Configuration part of the Create Step Ladder window is identical to the Stair Configuration part of the Create Stair Flight window (with the exception of the Handrail Configuration drop-down list). Refer to Stair Configuration for further information.\nClick Next to display the Step Ladder Details part of the Create Step Ladder window. Refer to Step Ladder Details for further information\nClick Back to return to the Reference Points part of the Create Step Ladder window.\nClick Cancel to discard any inputs and close the Create Step Ladder window.\nEdge to plane, top extension\nEdge to plane, no extension\nEdge to edge, top extension\nEdge to edge, no extension\n\n\n\nStair Configuration\nStep Ladder Details\nStep Ladder Configuration\nCreate Step Ladder\nStep Ladder Configuration\nCreate Step Ladder\nEdge to plane, top extension\nEdge to plane, no extension\nEdge to edge, top extension\nEdge to edge, no extension\nStep Ladder Configuration\nCreate Step Ladder\nStair Configuration\nCreate Stair Flight\nHandrail Configuration\nStair Configuration\nNext\nStep Ladder Details\nCreate Step Ladder\nStep Ladder Details\nBack\nReference Points\nCreate Step Ladder\nCancel\nCreate Step Ladder"}
{"Headers": "General Attributes", "Content": "The functionality available in the General Attributes part of the Create Step Ladder window is identical to that in Layout mode. Refer to General Attributes for further information.\n\n\n\nGeneral Attributes\nGeneral Attributes\nCreate Step Ladder\nLayout\nGeneral Attributes"}
{"Headers": "Reference Points", "Content": "The functionality available in the Reference Points part of the Create Step Ladder window is identical to the Reference Points part of the Create Stair Flight window. Refer to Reference Points for further information.\n\n\n\nReference Points\nReference Points\nCreate Step Ladder\nReference Points\nCreate Stair Flight\nReference Points"}
{"Headers": "Handrail Assembly", "Content": "The Handrail Assembly part of the Create Step Ladder window is automatically populated with all of the available handrail assemblies for selection. A 3D graphical representation of the handrail assembly also displays.\n\nClick Next to display the Specifications part of the Create Step Ladder window. Refer to Specifications for further information.\nClick Back to return to the Step Ladder Configuration part of the Create Step Ladder window.\nClick Cancel to discard any inputs and close the Create Step Ladder window.\nNote:\nStep ladder handrails may not be displayed correctly if the values on the Step Ladder Details part of the Create Step Ladder window are unrealistic or do not allow the geometry to be calculated correctly. Modifying values such as Bend Radius or Exit Extension will resolve the issue. The displayed aids give an indication of the result and will adjust if the values on the on the Step Ladder Details part of the Create Step Ladder window are modified.\n\n\n\nSpecifications\nHandrail Assembly\nCreate Step Ladder\nNote:\nStep Ladder Details\nCreate Step Ladder\nBend Radius\nExit Extension\nStep Ladder Details\nCreate Step Ladder\nNext\nSpecifications\nCreate Step Ladder\nSpecifications\nBack\nStep Ladder Configuration\nCreate Step Ladder\nCancel\nCreate Step Ladder"}
{"Headers": "Step Ladder Details", "Content": "The functionality available in the Step Ladder Details part of the Create Step Ladder window is identical to that in Layout mode. Refer to Step Ladder Details for further information.\n\n\n\nStep Ladder Details\nStep Ladder Details\nCreate Step Ladder\nLayout\nStep Ladder Details"}
{"Headers": "Rung Ladder", "Content": "RLADDR is an SLH element which enables you to create a rule based Rung Ladder and also introduces a new middle tier hierarchy to enable the decomposition of the RLADDR into its individual assemblies of Ladder Stringers, Ladder Rungs, Ladder Safety Cages and Exit directions. The lower level elements of GENSEC, PANEL, LDDRUN and CAGSEC are used to represent the ladder element in the 3D model.\n\n\n"}
{"Headers": "Layout Rung Ladder Hierarchy", "Content": "When the RLADDR element is created in the layout mode, below the administrative SLH elements, the RLADDR specific elements are:\n\nRUNG LADDER (RLADDR)\nThe RLADDR element is a top level SLH administrative element owned by other structural administrative elements. For example, STRU, FRWM and /or SBFR.\nRUNG LADDER CAGE (RLCAGE)\nThe RLCAGE element is an administrative element which owns the Cage Segment (CAGSEG) element.\nRUNG LADDER GATE (RLGATE)\nThe RLGATE element represents the gate on the rung ladder.\nNote:\nIn Layout mode, the RLADDR element has no assemblies.\n\n\n\nRUNG LADDER (RLADDR)\nRUNG LADDER CAGE (RLCAGE)\nRUNG LADDER GATE (RLGATE)\nNote:\nLayout"}
{"Headers": "Detail Rung Ladder Hierarchy", "Content": "When the RLADDR element is created in detail mode, below the administrative SLH elements, the RLADDR specific elements are:\n\nRUNG LADDER (RLADDR)\nThe Ladder element (RLADDR) is a top level administrative element owned by other SLH administrative elements. For example, STRU, FRWM and /or SBFR.\nRLCAGE (RUNG LADDER CAGE)\nThe RLCAGE element is an administrative element which owns the Cage Segment (CAGSEG) element.\nCAGE SEGMENT (CAGSEG)\nThe CAGSEG element owns the GENSEC and PANEL steelwork elements used to 3D model the physical representation of the cage. By default, there are two cage segments, one representing the entry/exit at the top of the ladder and the other representing the remainder of the cage itself. The mechanism allows the entry/exit detailing of the cage to be modified individually from the remainder of the cage.\nLADDER STRINGER (LDRSTR)\nThe LDRSTR element is an administrative element which owns the appropriate number of GENSEC steelwork elements used to 3D model the main supports of the rung ladder.\nLADDER RUNG SET (RUNGSE)\nThe RUNGSE element is an administrative element which is used to manage the ownership of individual LDRRUN elements. The element is dependent upon the design of the rung and intended to support a variety of rung types.\nLADDER RUNG (LDRRUN)\nThe LDDRUN element owns the GENSEC, PANEL or catalogue elements used to 3D model the physical representation of the rung.\n\n\n\nRUNG LADDER (RLADDR)\nRLCAGE (RUNG LADDER CAGE)\nCAGE SEGMENT (CAGSEG)\nLADDER STRINGER (LDRSTR)\nLADDER RUNG SET (RUNGSE)\nLADDER RUNG (LDRRUN)"}
{"Headers": "Create Rung Ladder", "Content": "Creates a Rung Ladder (RLADDR) element.\nAll of the RLADDR creation tasks are initiated from a central Create Rung Ladder window which acts as a task hub. The General Attributes window is always initially displayed, regardless of the selected SLH element or representation mode, further windows are presented (progressive disclosure) prompting for input.\n\n\n\n\nCreate Rung Ladder\nGeneral Attributes"}
{"Headers": "Layout Mode", "Content": "By default the Representation Mode is Layout and the General Attributes part of the Create Rung Ladder window is displayed.\n\n\n\nLayout\nGeneral Attributes\nCreate Rung Ladder"}
{"Headers": "Position and Elevation", "Content": "The functionality available for the Position and Elevation part of the Create Rung Ladder window, in Detail mode, is identical to that described in Layout mode. Refer to Position and Elevation for further information.\n\n\n\nPosition and Elevation\nPosition and Elevation\nCreate Rung Ladder\nPosition and Elevation"}
{"Headers": "Detail Mode", "Content": "Detail mode is intended for use by structural designers to fully define the rung ladder, by selecting a default, an assembly and the specification references of the ladder components.\n\nA rung ladder element created in Layout can be modified to a detailed representation without deleting and re-creating the element.\n\n\n\nDetail\nLayout"}
{"Headers": "General Attributes", "Content": "The functionality available for the General Attributes part of the Create Rung Ladder window, in Detail mode, is identical to that described in Layout mode. Refer to General Attributes for further information.\n\n\n\nGeneral Attributes\nGeneral Attributes\nCreate Rung Ladder\nGeneral Attributes"}
{"Headers": "Ladder Assembly", "Content": "The Ladder Assembly part of the Create Rung Ladder window is automatically populated with all of the available assemblies for selection that contain the selected exit type. A 3D graphical representation of the assembly also displays.\n\nClick Next to display the Specifications part of the Create Rung Ladder window. Refer to Specifications for further information.\nClick Back to return to the Position and Elevation part of the Create Rung Ladder window.\nClick Cancel to discard any inputs and close the Create Rung Ladder window.\n\n\n\nSpecifications\nLadder Assembly\nCreate Rung Ladder\nNext\nSpecifications\nCreate Rung Ladder\nSpecifications\nBack\nPosition and Elevation\nCreate Rung Ladder\nCancel\nCreate Rung Ladder"}
{"Headers": "Ladder Details", "Content": "The Ladder Details part of the Create Rung Ladder window is populated with the selected and calculated values, most of these values are constrained by the specifications. Any of the ladder dimensions can be modified as long as the dimensions remain within the maximum and minimum tolerances of the associated standard.\n\nIf you input a dimension which is not within the maximum and minimum tolerances of the associated standard, an error message displays summarizing the problem.\n\nAny of the dimensions in the Create Rung Ladder window can be labelled in the 3D view. To label the dimension, click Dimension adjacent to dimension field.\n\nLadder Details\nThe Ladder Details part of the Create Rung Ladder window is populated with the selected and calculated values, most of these values are constrained by the specifications.\n\nThe SLH application endeavours to calculate the initial rung spacing to be as close to the associated standard and therefore makes the bottom rung spacing equal to the rung spacing.\n\nIf required you can modify the rung spacing and as a result the bottom rung spacing. From the Ladder Details part of the Create Rung Ladder window, input the new rung spacing into the Rung Spacing field, then press Enter.\nTo return the rung and bottom rung spacing back to that of equal spacing, click the = icon.\nStile/Cage Exit Width\nThe Cage Details part of the Create Rung Ladder window only displays if the Omit Cage or Omit Top Rung check box on the General Attributes part of the Create Rung Ladder window is not selected.\nThe Cage Details part of the Create Rung Ladder window is populated with the selected and calculated values, most of these values are constrained by the specifications.\nOther cage details are inactive dependent on the selections made:\nFlare Offset - only available if an assembly with a cage flare has been selected.\nCage Clearance (Side Exit) - only available for side ladders.\n\nThe SLH application endeavours to calculate the initial cage hoop spacing to be as close to the associated standard and therefore makes the top hoop spacing equal to the cage hoop spacing.\n\nIf required, you can modify the cage hoop spacing. From the Ladder Details part of the Create Rung Ladder window, input the new spacing into the Cage Hoop Spacing field, then press Enter.\nTo return the cage hoop and top hoop spacing back to that of equal spacing, click the = icon.\nClick Build Rung Ladder to create the rung ladder element and close the Create Rung Ladder window.\nClick Back to return to the Specifications part of the Create Rung Ladder window.\nClick Cancel to discard any inputs and close the Create Rung Ladder window.\nRung Ladder Summary\nThe Rung Ladder Summary part of the Create Rung Ladder window, is populated with the main attributes of the rung ladder.\n\n\n\n\nLadder Details\nCreate Rung Ladder\nCreate Rung Ladder\nDimension\nLadder Details\nLadder Details\nCreate Rung Ladder\nLadder Details\nCreate Rung Ladder\nRung Spacing\nEnter\n=\nStile/Cage Exit Width\nCage Details\nCreate Rung Ladder\nOmit Cage\nOmit Top Rung\nGeneral Attributes\nCreate Rung Ladder\nCage Details\nCreate Rung Ladder\nFlare Offset\nCage Clearance (Side Exit)\nLadder Details\nCreate Rung Ladder\nCage Hoop Spacing\nEnter\n=\nBuild Rung Ladder\nCreate Rung Ladder\nBack\nSpecifications\nCreate Rung Ladder\nCancel\nCreate Rung Ladder\nRung Ladder Summary\nRung Ladder Summary\nCreate Rung Ladder"}
{"Headers": "Handrails", "Content": "The Handrail is an assembly which comprises components such as posts, rails, panels, kickplates as well as gate and termination features. In MODEL, there are two types of handrail:\nThe Handrail element (HANDRA) is a top level administrative element owned by the other SLH administrative elements, that is STRFLT, STRU, FRWM and SUBFR elements.\nContinuous\nPanelled\nContinuous\nContinuous\nPanelled\nPanelled\n\n\n"}
{"Headers": "Layout Handrails Hierarchy", "Content": "When the Handrail element (HANDRA) is created in Layout, below the SLH administrative elements, the HANDRA specific elements are:\n\nROUTE PATH (RPATH)\nThe Routing Path element defines an open path or closed boundary:\nROUTE POINT (POINTR)\nThe Point element defines the picked points or curve of the RPATH element.\nFree form interactive sketching using the Route sketching functionality\nTracing existing profiles or boundaries.\nFree form interactive sketching using the Route sketching functionality\nFree form interactive sketching using the Route sketching functionality\nTracing existing profiles or boundaries.\nTracing existing profiles or boundaries.\nNote:\nIn Layout, the HANDRA element does not own any detailing components (for example: rails, kickplates).\n\n\n\nLayout\nNote:\nLayout\nROUTE PATH (RPATH)\nROUTE POINT (POINTR)"}
{"Headers": "Detail Handrails Hierarchy", "Content": "When the Handrail element (HANDRA) is created in Detail, below the SLH administrative elements, the HANDRA specific elements are:\n\nPost Set (POSTSE)\nThe POSTSE is responsible for the ownership and management of multiple HRPOST elements.\nHandrail Post (HRPOST)\nThe HRPOST element represents the post detail which references the catalogue items or templates as it has a SPREF attribute. The position of the HRPOST is defined with respect to the owning HANDRA in terms of its position along the path and the offset from the path of the HANDRA.\nRail Set (RAILSE)\nRAILSE is responsible for the ownership and management of multiple RAIL elements whose physical representation is 3D modelled using a RAIL element.\nHandrail Rail (RAIL)\nRAIL is used to 3D 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.\nThe RAIL shares the same underlying attributes and behaviour as the KICKPL element.\nHandrail Kickplate Set (HRKPSE)\nHRKPSE is responsible for the ownership and management of multiple Kickplate elements whose physical representation is 3D modelled using a KICKPL element.\nKickplate (KICKPL)\nKICKPL is used to 3D model the detail representation of a kickplate and follows the path of the HANDRA, the KICKPL references the existing catalogue steel profiles via its SPREF attribute and the position of the KICKPL is defined with respect to the owning HANDRA in terms of its position along the path and the offset from the path of the HANDRA.\nThe KICKPL shares the same underlying attributes and behaviour as RAIL element.\nHandrail Panel Set (HRPNSE)\nHRPNSE is responsible for the ownership and management of multiple HRPANE elements.\nHandrail Panel (HRPANE)\nHRPANE is the database element responsible for the representation of 'panelised' sections of Handrail where the Panel size is determined by its Panel Size attribute. The detail of the HRPANE is represented using the existing database functionality of TMPL and FIXING elements and the route of the HRPANE elements is defined using the RPATH routing object.\nHandrail Feature (HRFEAT)\nHRFEAT owns HRGATE elements. The HRFEAT also owns RATTA elements which at this hierarchical level provide a connectivity mechanism to/from the boundary of the HANDRA.\nHandrail Gate (HRGATE)\nHRGATE is an element used to represent access locations along the path of the HANDRA. There can be multiple HRGATE elements in any HANDRA and the position of the HRGATE is managed by the application as a position along the RPATH element. HRGATE elements are managed as negative geometry and penetrate only the HANDRA. Additional detail for the HRGATE is represented using the existing database functionality of TMPL and FIXING elements.\nTerminations (HRTERM)\nThe Termination element represents, for example, Loops, End Plates or Posts.\n\n\n\nDetail\nPost Set (POSTSE)\nHandrail Post (HRPOST)\nRail Set (RAILSE)\nHandrail Rail (RAIL)\nHandrail Kickplate Set (HRKPSE)\nKickplate (KICKPL)\nHandrail Panel Set (HRPNSE)\nHandrail Panel (HRPANE)\nHandrail Feature (HRFEAT)\nHandrail Gate (HRGATE)\nTerminations (HRTERM)"}
{"Headers": "Create Handrail", "Content": "Creates a Handrail (HANDRA) element.\nAll of the HANDRA creation tasks are initiated from a central Create Handrail window which acts as a task hub. The General Attributes window is always initially displayed, regardless of the selected SLH element or representation mode, further windows are presented (progressive disclosure) prompting for input.\n\nBy default, Layout is selected and General Attributes displays.\n\n\n\nCreate Handrail\nGeneral Attributes\nLayout\nGeneral Attributes"}
{"Headers": "Layout Mode", "Content": "Layout is a basic representation of the intended handrail. The database only contains the handrail and its intended route plus any openings for gates, the handrail does not own any detailed components. Refer to Layout Handrails Hierarchy for further information.\n\n\n\nLayout Handrails Hierarchy\nLayout\nLayout Handrails Hierarchy"}
{"Headers": "Handrail Details", "Content": "Use the Handrail Details part of the Create Handrail window to view and, if required, modify (within the maximum and minimum limits) the default values for the handrail and the addition or removal of a kickplate.\nIf required, you can display any of the dimensions from the Handrail Details window in the 3D view. To label a dimension, click Display alongside the dimension field.\n\nClick Next to display the Route Definition part of the Create Handrail window. Refer to Route Definition for further information.\nClick Back to return to the Select Assembly part of the Create Handrail window.\nClick Cancel to discard any inputs and close the Create Handrail window.\n\n\n\nRoute Definition\nHandrail Details\nCreate Handrail\nHandrail Details\nDisplay\nNext\nRoute Definition\nCreate Handrail\nRoute Definition\nBack\nSelect Assembly\nCreate Handrail\nCancel\nCreate Handrail"}
{"Headers": "Route Definition", "Content": "The functionality available for the Route Definition part of the Create Handrail window, in Detail mode, is identical to that described in Layout mode, with the exception of Route Point Tools. Refer to Route Definition for further information.\nRoute Point Tools\nUse the Route Point Tools to close, move or delete the route points of the handrail:\nClose Handrail\nClick to close the route of the handrail, for example if the handrail has three sides, The close handrail functionality closes the three sides to make a square.\nSelect Route Point\nAllows you to select a route point in the RPATH.\nYou are prompted to Pick route point to make current\nEach route point is labelled in the 3D view.\nMove Current Route Point\nAllows you to move a current route point in the RPATH.\nYou are prompted to Pick new position for current route point (Distance [0]) WP Snap:\nDelete Current Route Point\nDeletes the current route point.\nDelete Route Points\nYou are prompted to Pick first route point of sequence to be deleted\nOnce the selection has been made, you are prompted to Pick last route of sequence to be deleted#\nOnce the selection has been made the route points are deleted, you are then prompted to Pick position of new route point (Distance [0]) WP Snap:\nDelete All Route Points\nDeletes all the route points of the handrail, you are prompted with a Confirm window: Delete all route points?.\n\nClose Handrail\nClick to close the route of the handrail, for example if the handrail has three sides, The close handrail functionality closes the three sides to make a square.\n\nSelect Route Point\nAllows you to select a route point in the RPATH.\nYou are prompted to Pick route point to make current\nEach route point is labelled in the 3D view.\n\nMove Current Route Point\nAllows you to move a current route point in the RPATH.\nYou are prompted to Pick new position for current route point (Distance [0]) WP Snap:\n\nDelete Current Route Point\nDeletes the current route point.\n\nDelete Route Points\nYou are prompted to Pick first route point of sequence to be deleted\nOnce the selection has been made, you are prompted to Pick last route of sequence to be deleted#\nOnce the selection has been made the route points are deleted, you are then prompted to Pick position of new route point (Distance [0]) WP Snap:\n\nDelete All Route Points\nDeletes all the route points of the handrail, you are prompted with a Confirm window: Delete all route points?.\nHandrail Connections\nHandrail posts, panels, gates and terminations have a connection reference attribute (CONREF). Information from a connected element can be used in rules to determine the parameters and geometry of the posts.\nAn example handrail assembly which uses connected elements to influence the posts is provided in the APS project, use either of the Sample Welded assemblies.\nClick Pick connection elements for components to allow connection references to be added to handrail posts.\nYou are prompted to Pick connection elements for handrail components:\nPick a connection element in the 3D view. Multiple connection elements can be specified.\nOnce created, each post, panel and gate references the closest connection element within 150mm.\nValid elements for connection are:\nWhen modifying a handrail with connections, any connected sections/panels will are highlighted in red.\nA list of connected handrail components for a given section, panel or wall can be retrieved using the BACKREF attribute.\nClick Next to display the Openings part of the Create Handrail window. Refer to Openings for further information.\nClick Back to return to the Handrail Details part of the Create Handrail window.\nClick Cancel to discard any inputs and close the Create Handrail window.\nClose Handrail\nClick to close the route of the handrail, for example if the handrail has three sides, The close handrail functionality closes the three sides to make a square.\nSelect Route Point\nAllows you to select a route point in the RPATH.\nYou are prompted to Pick route point to make current\nEach route point is labelled in the 3D view.\nMove Current Route Point\nAllows you to move a current route point in the RPATH.\nYou are prompted to Pick new position for current route point (Distance [0]) WP Snap:\nDelete Current Route Point\nDeletes the current route point.\nDelete Route Points\nYou are prompted to Pick first route point of sequence to be deleted\nOnce the selection has been made, you are prompted to Pick last route of sequence to be deleted#\nOnce the selection has been made the route points are deleted, you are then prompted to Pick position of new route point (Distance [0]) WP Snap:\nDelete All Route Points\nDeletes all the route points of the handrail, you are prompted with a Confirm window: Delete all route points?.\nGENSEC (including stair string`ers)\nPANE\nWALL\nGWALL\nFLOOR\nGENSEC (including stair string`ers)\nGENSEC (including stair string`ers)\nPANE\nPANE\nWALL\nWALL\nGWALL\nGWALL\nFLOOR\nFLOOR\n\n\n\nRoute Definition\nOpenings\nRoute Definition part\nCreate Handrail\nRoute Definition\nRoute Point Tools\nRoute Point Tools\nClose Handrail\nSelect Route Point\nPick route point to make current\nMove Current Route Point\nPick new position for current route point (Distance [0]) WP Snap:\nDelete Current Route Point\nDelete Route Points\nPick first route point of sequence to be deleted\nPick last route of sequence to be deleted#\nPick position of new route point (Distance [0]) WP Snap:\nDelete All Route Points\nConfirm\nDelete all route points?\nHandrail Connections\nPick connection elements for components\nPick connection elements for handrail components:\nNext\nOpenings\nCreate Handrail\nOpenings\nBack\nHandrail Details\nCreate Handrail\nCancel\nCreate Handrail"}
{"Headers": "Openings", "Content": "Use the Openings part of the Create Handrail window to create a handrail opening.\n\nBy default, the width of the opening displays in the Width field. To display the Width dimension in the 3D view, select Display. Add Opening is the only functionality available for selection, from the Openings part of the Create Handrail window, click Add Opening.\n\nThe Positioning Control window displays and you are prompted to Pick the position to insert gate opening (Snap) Snap:\nSelect the opening position in the 3D view.\nUpon selection, the Openings part of the Create Handrail window, is populated with the opening coordinates (width is dictated by the default file).\n\nIf required, you can also pick a new opening position, add or delete an opening:\nAdd Opening\nYou are prompted to Pick position to insert gate (Snap) Snap: and the Positioning Control window displays. Refer to Positioning Control for further information. Once the new position is selected in the 3D view, the Openings part of the Create Handrail window is populated with coordinates of the Opening.\nPick New Position\nYou are prompted to Pick new position for gate (Snap) Snap: and the Positioning Control window displays. Refer to Positioning Control for further information. Once the new position is selected in the 3D view, the Openings part of the Create Handrail window is populated with coordinates of the Opening.\nDelete Opening\nA Confirm window displays: Delete the selected openings.\n\nAdd Opening\nYou are prompted to Pick position to insert gate (Snap) Snap: and the Positioning Control window displays. Refer to Positioning Control for further information. Once the new position is selected in the 3D view, the Openings part of the Create Handrail window is populated with coordinates of the Opening.\n\nPick New Position\nYou are prompted to Pick new position for gate (Snap) Snap: and the Positioning Control window displays. Refer to Positioning Control for further information. Once the new position is selected in the 3D view, the Openings part of the Create Handrail window is populated with coordinates of the Opening.\n\nDelete Opening\nA Confirm window displays: Delete the selected openings.\nHandrail Summary\nThe Handrail Summary part of the Create Handrail window, is populated with the main attributes of the handrail. If required, before the creation of the handrail element, you can select the attribute by name and modify it from the displayed part of the Create Handrail window\n\nClick Build Handrail to create the handrail (created in Detail) in the 3D view.\nClick Back to return to the Route Definition part of the Create Handrail window.\nClick Cancel to discard any inputs and close the Create Handrail window.\nAdd Opening\nYou are prompted to Pick position to insert gate (Snap) Snap: and the Positioning Control window displays. Refer to Positioning Control for further information. Once the new position is selected in the 3D view, the Openings part of the Create Handrail window is populated with coordinates of the Opening.\nPick New Position\nYou are prompted to Pick new position for gate (Snap) Snap: and the Positioning Control window displays. Refer to Positioning Control for further information. Once the new position is selected in the 3D view, the Openings part of the Create Handrail window is populated with coordinates of the Opening.\nDelete Opening\nA Confirm window displays: Delete the selected openings.\n\n\n\nPositioning Control\nPositioning Control\nOpenings\nCreate Handrail\nWidth\nDisplay. Add Opening\nOpenings\nCreate Handrail\nAdd Opening\nPositioning Control\nPick the position to insert gate opening (Snap) Snap:\nOpenings\nCreate Handrail\nAdd Opening\nPick position to insert gate (Snap) Snap:\nPositioning Control\nPositioning Control\nOpenings\nCreate Handrail\nPick New Position\nPick new position for gate (Snap) Snap:\nPositioning Control\nPositioning Control\nOpenings\nCreate Handrail\nDelete Opening\nConfirm\nDelete the selected openings.\nHandrail Summary\nHandrail Summary\nCreate Handrail\nCreate Handrail\nBuild Handrail\n.\nBack\nRoute Definition\nCreate Handrail\nCancel\nCreate Handrail"}
{"Headers": "Detail Mode", "Content": "The Detail mode is a more complex physical representation of the handrail where the database contains items for the individual posts, rails, kickplates, gates and terminations.\n\n\n\n\nDetail"}
{"Headers": "General Attributes", "Content": "The functionality available from the General Attributes part of the Create Handrail window, in Detail mode, is identical to that described in Layout mode. Refer to General Attributes for further information.\n\n\n\nGeneral Attributes\nGeneral Attributes\nCreate Handrail\nGeneral Attributes"}
{"Headers": "Select Assembly", "Content": "The Select Assembly part of the Create Handrail window is automatically populated with all of the handrail assemblies available for selection governed by the default file. A 3D representation of the handrail assembly also displays.\n\nSelect the Flip Left/Right Handrail check box to flip the handrail.\nClick Next to display the Handrail Details part of the Create Handrail window. Refer to Handrail Details for further information.\nClick Back to return to the General Attributes part of the Create Handrail window.\nClick Cancel to discard any inputs and close the Create Handrail window.\nNote:\nThe position of the RPATH relative to the handrail assembly displays to assist you in the creation of a suitable RPATH.\n\n\n\nHandrail Details\nSelect Assembly\nCreate Handrail\nNote:\nFlip Left/Right Handrail\nNext\nHandrail Details\nCreate Handrail\nHandrail Details\nBack\nGeneral Attributes\nCreate Handrail\nCancel\nCreate Handrail"}
{"Headers": "Curved Handrails", "Content": "If required, SLH can create curved handrails. The functionality to create a curved handrail is identical to that for the creation of a straight handrail. With the exception that curved handrails can only be created with the Copy Route Path functionality from the Route Definition part of the Create Handrail window and you must select a curved GENSEC element.\n\nYou are prompted to Pick element to copy route path from, from the 3D view.\n\nKickplates on Curved Handrails\nKickplates on curved segments of a handrail (not corners) follow the curved route path, a segmented kickplate terminates at the end of each curve. A continuous kickplate runs the whole length of the handrail.\n\n\n\n\nCopy Route Path\nRoute Definition\nCreate Handrail\nPick element to copy route path from\nKickplates on Curved Handrails"}
{"Headers": "Handrails on Stairs", "Content": "Handrails can be created with a stair flight in Layout, if handrails are required in Detail or those stair flights created without handrails use the handrail functionality.\nIrrelevant of which method is used, the position and orientation of the route path are determined by which part of the stair flight is picked and the finished floor level (FFL).\nCreate Route Points\nThe functionality to create route points on a stair flight is identical to that described earlier in this guide. Refer to Route Definition for further information.\nCopy Route Path\nIf you select a stair stringer to trace for the route path of the handrail, the SLH application creates the current route point at the end of the stringer at the FFL, and then routes the handrail along the centre of the stringer.\n\nIf you select a landing or tread as the element to trace for the route path of the handrail, the SLH application creates the current route point at the FFL, then routes the handrail up the right hand side of the stair flight.\n\n\n\n\nRoute Definition\nLayout\nDetail\nCreate Route Points\nRoute Definition\nCopy Route Path"}
{"Headers": "Modify Stair Flight", "Content": "Modifies the stair flight attributes.\nAll of the STRFLT modification tasks are initiated from a central Modify Stair Flight window which acts as a task hub.\nThe functionality available for the Modify Stair Flight window is identical to the Create Stair Flight window. Refer to Create Stair Flight for further information.\n\nThe stair flight is represented in the 3D view as construction lines.\n\nModify the stair flight as required, click Modify Stair Flight to commit the changes\nClick Cancel to discard any changes and close the Modify Stair Flight window.\n\nClick Yes to delete the handrail elements\nClick No to close the window without any modification to the stair flight.\nNote:\nIf the stair flight and associated handrails have been created in Layout mode and the Stair Flight is then modified into a Detail mode stair flight, a Confirm window displays:\n\n\n\nCreate Stair Flight\nModify Stair Flight\nModify Stair Flight\nCreate Stair Flight\nCreate Stair Flight\nModify Stair Flight\nCancel\nModify Stair Flight\nNote:\nConfirm\nYes\nNo"}
{"Headers": "Modify Step Ladder", "Content": "Modifies the step ladder attributes.\nAll of the SLADDR modification tasks are initiated from a central Modify Step Ladder window which acts as a task hub.\nThe functionality available for the Modify Step Ladder window is identical to the Create Step Ladder window. Refer to Create Step Ladder for further information.\n\nThe step ladder is represented in the 3D view as construction lines.\n\nModify the step ladder as required, click Modify Step Ladder to commit the changes.\nClick Cancel to discard any changes and close the Modify Step Ladder window.\n\n\n\nCreate Step Ladder\nModify Step Ladder\nModify Step Ladder\nCreate Step Ladder\nCreate Step Ladder\nModify Step Ladder\nCancel\nModify Step Ladder"}
{"Headers": "Modify Rung Ladder", "Content": "Modifies the rung ladder attributes.\nAll of the RLADDR modification tasks are initiated from a central Modify Rung Ladder window which acts as a task hub.\nThe functionality available for the Modify Rung Ladder window is identical to the Create Rung Ladder window. Refer to Create Rung Ladder for further information.\nThe rung ladder is represented in the 3D view as construction lines.\n\nModify the rung ladder as required, click Modify Rung Ladder to commit the changes.\nClick Cancel to discard any changes and close the Modify Rung Ladder window.\n\n\n\nCreate Rung Ladder\nModify Rung Ladder\nModify Rung Ladder\nCreate Rung Ladder\nCreate Rung Ladder\nModify Rung Ladder\nCancel\nModify Rung Ladder"}
{"Headers": "Modify Handrail", "Content": "Modifies the handrail attributes.\nAll of the HANDRA modification tasks are initiated from a central Modify Handrail window which acts as a task hub.\nThe functionality available for the Modify Handrail window is identical to the Create Handrail window. Refer to Create Handrail for further information.\nThe handrail is represented in the 3D view as construction lines.\n\n\nModify the handrail as required, click Modify Handrails, a Confirm window displays:\n\nClick Yes to remove any previously added details.\nClick No to discard any changes.\nClick Cancel to discard any changes and close the Modify Handrail window.\nNote:\nIf you attempt to modify a Layout mode handrail element from the Modify group, an error message displays summarizing the problem.\n\n\n\nCreate Handrail\nModify Handrail\nModify Handrail\nCreate Handrail\nCreate Handrail\nNote:\nModify\nModify Handrails\nConfirm\nYes\nNo\nCancel\nModify Handrail"}
{"Headers": "Stairs, Ladders and Handrails Tools", "Content": "SLH provides functionality which allows you to \u2018fine tune\u2019 handrails, for example: modify individual components of the handrail assembly, split and merge handrails. You can also select other functionality which is common to all disciplines. Refer to Common Functionality for further information.\n\n\n\nCommon Functionality\nCommon Functionality"}
{"Headers": "Components", "Content": "Modifies individual or multiple handrail components.\nThe functionality allows you to manipulate:\nIf a particular SLH element cannot be created at the current position in the database hierarchy, a message displays.\n\nThe used handrail components determines which tabs of the Modify Handrail Components window are populated and are available for selection.\nGates\nPosts\nTerminations\nRails\nKickplates\nPanels (only available with panelled handrails selected as the CE).\nGates\nGates\nPosts\nPosts\nTerminations\nTerminations\nRails\nRails\nKickplates\nKickplates\nPanels (only available with panelled handrails selected as the CE).\nPanels (only available with panelled handrails selected as the CE).\n\n\n\nModify Handrail Components"}
{"Headers": "SDNF Export/Import", "Content": "AVEVA SDNF is the interface for Model which allows you to export and import files using the structural Steel Detailing Neutral File (SDNF) format.\nThe AVEVA SDNF interface uses a large proportion of the information transferable in SDNF format. The SDNF file, its format and contents are explained. Refer to Technical Information for further information.\n\n\n\nTechnical Information\nModel\nTechnical Information"}
{"Headers": "Export to SDNF", "Content": "Exports a steel structure to a SDNF file.\n\n\n\n"}
{"Headers": "Target Information", "Content": "Click Target Information to display the Export Target Information window which contains information about the 3D steel detailing package to which the SDNF file is being transferred.\n\nThe interface requires at least two external mapping tables for each Target Package in order to check that the Target Package can accept the data. It also may use the Profile Orientation and/or the Unicode mapping tables if necessary. The mapping tables are for the Profiles, Materials and for mapping the Profile Orientations between the application and the neutral file. The Unicode mapping table is to translate the applications Unicode strings into ASCII strings. The file arrangement on the system and required format is explained. Refer to Customise SDNF for further information. The interface also needs to know where the external mapping files are located on the computer network. For this, internal mapping tables are required. The configuration and location of files is explained. Refer to Internal Mapping Files for further information.\nFor example you may have a generic set of mapping tables to map between the application and SDNF for a particular steel fabricator, or you may have a similar set for each 3D steel detailing package.\nThe current file settings are indicated on the Export Target Information window. Changing the Target Package by using the Target Package drop-down list on the right-hand side of the window may cause the text to change giving the full path names of the respective files. Do not be concerned that the path name may be truncated by the insertion of the ellipsis (\u2026): it is modified only for display purposes on the window.\nThe system also checks that these files are compatible with the Target Package by checking only the identification line at the top of each mapping table. The format of the mapping files is detailed. Refer to External Mapping Files for further information.\nThe two main options are, Auto and Manual which are activated by selecting the appropriate option button.\nAuto causes the interface to select automatically the mapping tables for the Target Package indicated by the Target Package drop-down list on the right hand side of the window, according to the system configuration files. The files selected are dependent upon how you have configured the internal mapping files.\nManual activates other option buttons, which are greyed out for the Auto option. Selecting this option changes the display of the window. For example:\n\nYou can select the file type using the Profiles, Materials, Orient'n or Unicode radio buttons and input the full path name of the file in the data entry area. You can also include system environment variables in the path name as long as they are in the proper format, for example, %ENVVAR% being the representation of the ENVVAR environment variable.\nPress Enter, the interface checks for the existence of the file and compatibility with the Target Package indicated by the Package drop-down list.\nYou can choose by hand which mapping file to use either by inputting its name in the text data entry field, or by using the Browse option to display a File Browser. You can use this browser to search for the relevant mapping file.\nOnce you have input all the correct data on the Export Target Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.\nError and Log File Messages\nInternal error\nInternal lists are not in step.\nCannot find suitable internal mapping list\nInternal mapping files not found.\nSuitable Mapping Table File not found\nMapping table found is not for the correct Target Package, or it does not exist.\nNot a suitable Mapping Table File\nIncorrect format of file, or empty file, or wrong Target Package.\nBad Map File\nMapping file is not correct format. Possibly it is from another operating system.\nError on SDNF File Browser form\nYou have input incorrect data on the file browser.\nInternal error\nInternal lists are not in step.\nCannot find suitable internal mapping list\nInternal mapping files not found.\nSuitable Mapping Table File not found\nMapping table found is not for the correct Target Package, or it does not exist.\nNot a suitable Mapping Table File\nIncorrect format of file, or empty file, or wrong Target Package.\nBad Map File\nMapping file is not correct format. Possibly it is from another operating system.\nError on SDNF File Browser form\nYou have input incorrect data on the file browser.\n\nInternal error\nInternal lists are not in step.\nCannot find suitable internal mapping list\nInternal mapping files not found.\nSuitable Mapping Table File not found\nMapping table found is not for the correct Target Package, or it does not exist.\nNot a suitable Mapping Table File\nIncorrect format of file, or empty file, or wrong Target Package.\nBad Map File\nMapping file is not correct format. Possibly it is from another operating system.\nError on SDNF File Browser form\nYou have input incorrect data on the file browser.\nNote:\nThe check is only that the file applies to the Target Package and not that it is a correct file type or format.\n\n\n\nCustomise SDNF\nInternal Mapping Files\nExternal Mapping Files\nTarget Information\nExport Target Information\nCustomise SDNF\nInternal Mapping Files\nExport Target Information\nExternal Mapping Files\nAuto\nManual\nAuto\nManual\nAuto\nProfiles\nMaterials\nOrient'n\nUnicode\nEnter\nNote:\nBrowse\nExport Target Information\nOK\nCancel\nError and Log File Messages\nInternal error\nCannot find suitable internal mapping list\nSuitable Mapping Table File not found\nNot a suitable Mapping Table File\nBad Map File\nError on SDNF File Browser form"}
{"Headers": "Export/Import different SDNF Format", "Content": "The interface can read SDNF files to both version 2 and version 3 of the format (but it will write to only version 3). The format is described elsewhere. Principally in version three files, there are many more records attached to each linear member and the method of plate definition has changed. The interface does use some of this new information, principally the date and times of creation and modification.\n\n\n"}
{"Headers": "Export Information", "Content": "Click Export Information to display the Export Information window which contains information about the export process.\n\nYou can either type the full path name of the output file, or click Browse to display a File Browser. The interface checks that the file exists and if it does, you are asked whether to overwrite it. If the file does exist and you want to overwrite it, the file mode beside Browse changes from WRITE to OVERWRITE. The output file is rechecked for write/overwrite status during the actual Export process because you can perform Exports repeatedly without changing the output file name.\nThe SDNF file may have several sections: a header, Packet 00; a set of Linear Members, Packet 10; a set of Plates, Packet 20 and their holes (Packet 22); a set of Connection Details, Packet 40, and a set of Arc Members (Packet 60). The header is compulsory: any other Packets are optional.\nSelecting the information to be contained in Packet 00 is performed by navigating to, or below, the relevant SITE, ZONE or STRU element which contains the required header information. Open the Members list window on the main Export window. When at, or below, the correct element, click Use CE on this window, the source text indicates from where the interface gets the information. If there is not enough space on the window the element's reference number is output rather than its name.\nTo view the information contained by the chosen header element, click Inspect to display the Export File Header Details window.\n\nAt first the entry fields are greyed out but you can read the contents. To modify the contents of the fields click Edit on the Export File Header Details window and the fields become active and allow you to input any revised data. Click Apply and the data is transferred back to the chosen header object, overwriting the original data. Click Cancel to leave all the data unchanged.\n\nThe Previous Revision and Transfer information, if changed, is transferred not to the header object but to the Configuration Site for the specific current MDB/user combination. During Export or Import AVEVA SDNF inspects all the available Configuration Sites in order to elucidate the most recent Transfer letter and Revision number. The information is then stored in the site for the current user and allows for multi-user access to the databases.\nUsing the toggles on the Export Information window, you can select whether to export Packet 10 (Straight), Packet 60 (Curved) or Packet 20 (Plates) with the option of their holes, Packet 22 (Holes). You cannot output Packet 40 (End Connections) without outputting either Packet 10 (Straight) or Packet 60 (Curved). If you want neither Packet 10 nor Packet 60, the sub-options, Members only and Members + End Connections are inactivated and greyed out. Similarly, one cannot output Packet 22 (Holes) without outputting Packet 20 (Plates). You are able to export Plates without their holes.\nThe interface checks that you are attempting to Export something and outputs a message accordingly.\nOnce all the correct data has been input on the Export Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.\nError and Log File Messages\nExport file already exists\nFile exists, you receive the option to overwrite it.\nWrong place in database\nYou are most likely at the WORLD element in the database.\nIllegal Transfer letter\nYou can only use transfer letters between A and Z.\nNothing to export\nYou have deselected both the Linear Members and Plates options.\nCannot decrement Transfer letter\nYou cannot decrease the Transfer letter, only increment it.\nExport file already exists\nFile exists, you receive the option to overwrite it.\nWrong place in database\nYou are most likely at the WORLD element in the database.\nIllegal Transfer letter\nYou can only use transfer letters between A and Z.\nNothing to export\nYou have deselected both the Linear Members and Plates options.\nCannot decrement Transfer letter\nYou cannot decrease the Transfer letter, only increment it.\n\nExport file already exists\nFile exists, you receive the option to overwrite it.\nWrong place in database\nYou are most likely at the WORLD element in the database.\nIllegal Transfer letter\nYou can only use transfer letters between A and Z.\nNothing to export\nYou have deselected both the Linear Members and Plates options.\nCannot decrement Transfer letter\nYou cannot decrease the Transfer letter, only increment it.\nNote:\nIf you do not input the full path name and just a plain file name, the output file is created in the folder which started the application. You can also include system environment variables in the path name as long as they are in the correct format, for example, %ENVVAR% being the representation of the ENVVAR environment variable.\n\n\n\nExport Information\nExport Information\nBrowse\nBrowse\nWRITE\nOVERWRITE\nNote:\nMembers\nExport\nUse CE\nInspect\nExport File Header Details\nEdit\nExport File Header Details\nApply\nCancel\nExport Information\nPacket 10 (Straight), Packet 60 (Curved) or Packet 20 (Plates) with the option of their holes, Packet 22 (Holes)\nMembers only\nMembers + End Connections\nExport Information\nOK\nCancel\nError and Log File Messages\nExport file already exists\nWrong place in database\nIllegal Transfer letter\nNothing to export\nCannot decrement Transfer letter"}
{"Headers": "Run Information", "Content": "Click Run Information to display the Export window which allows you to view the Log File after the export process is complete and select the Log File? check box.\n\nClick either the Brief or Verbose radio buttons to choose which format messages are displayed.\nThe Test Run? option allows you to suppress the updating of all the Export flags, allowing you to check if Export of the model will be successful. You may find that the Profile or Material mapping files are not quite up to date which might cause a failure in the Export process. Therefore, you can select this option to define this as a test run.\nAfter the Export process has completed, Test Run? is reset to false. You are then forced to state categorically each time the model is Exported that the run is a trial.\nOnce all the correct data has been input on the Run Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.\n\n\n\nRun Information\nExport\nLog File?\nBrief\nVerbose\nTest Run?\nTest Run?\nRun Information\nOK\nCancel"}
{"Headers": "Members and Export List", "Content": "The Members part allows you to navigate around the database hierarchy.\nThough the application will create only GENSEC elements, old models might still contain SCTNs as well. The interface will still find SCTNs and export them. If a model is being imported and there are pre-existing SCTNs, these will be preserved, but all new members will be created as GENSECs.\nYou must input the elements to be exported, but need not select only SCTNs, GENSECs or PANEs. The interface locates all SCTNs, GENSECs and PANEs contained in, or implied by, the Export list. If you add something to the Export list and the item display in the 3D view it is highlighted and its colour changes. The Export list is managed such that duplicate elements are removed and that items are exported only once.\nThere are several methods of adding elements to the Export list.\nAdd CE adds the current element to the list and implies all items below the current element in the database hierarchy. The WORL can not be added to the list.\nThe Add by Pick option allows you to select an item from the 3D view. It is similar to other pick functions. Selecting this option brings up a Status window and puts you into a mode where an item from the 3D view can be picked. You can also pick a sequence of items in succession to add to the Export list. Press the ESC key when complete. If you do not want to continue, press the ESC key.\nAdd Structure attempts to climb to the Structure owning the current element and add that to the Export list. A warning message displays if there isn't an owning Structure.\nThere is also a set of methods by which you can remove items from the Export list. These options work only on entries in the Export list, rather than in the model. As with adding to the Export list, when items are removed from the Export list, the highlight is removed from the item or items and they are returned to the default colours as defined by this interface.\nRemove CE looks for the name of the current element in the list and removes it if present.\nRemove by Pick allows you to select something from the 3D view and, if it is present in the Export list, the name is removed. As with the Add by Pick option, you can select a series of items to remove from the Export list until the ESC key is pressed.\nRemove Selected is a means by which the item selected in the Export list is subsequently removed. Select the item first in the list, then click Remove Selected.\nClear just removes everything from the list.\nYou may find that items that display in the Export list do not exist, or have been renamed. The Export process determines all the valid entries in the Export list and prepares the data accordingly. Clearing the list, or removing individual items is performed as expected.\nError and Log File Messages\nCan't export the WORLD\nYou cannot export the WORLD\nNo owning Structure\nCannot climb to Structure element from current location in database.\nCan't export the WORLD\nYou cannot export the WORLD\nNo owning Structure\nCannot climb to Structure element from current location in database.\nCancel closes the AVEVA SDNF Export window.\nExport executes the Export process. As it proceeds you are kept informed of the progress by means of messages at the bottom of the main Model window as well as by forms and prompts.\nControl\nThe Control drop-down menu has four options; Re-initialize, Configure, Map Converter and Exit.\nAfter changing any mapping files or any other variables:\nRe-initialize reloads the files to save you having to rebuild the whole user interface from scratch.\nConfigure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information.\nMap Converter starts the tool that helps you rebuild Profile mapping files. Refer to External Mapping Files for further information.\nExit command removes all forms and menus and global variables associated with the interface.\nThe General drop-down menu has one option, Highlight which displays the Highlighter window enabling you to identify new, changed and deleted items in the model. The Highlighter window has more relevance to the Import process and is described in detail. Refer to Validation Process for further information.\nCan't export the WORLD\nYou cannot export the WORLD\nNo owning Structure\nCannot climb to Structure element from current location in database.\nNote:\nPartial model transfers are supported by the interface, however, you must be aware of how the Import process handles partial model transfers. Refer to Comparison and Merge Processes for further information.\nNote:\nThe colour may be different from the colour in which it may have originally been added to the Drawlist.\n\n\n\nComparison and Merge Processes\nExternal Mapping Files\nValidation Process\nNote:\nComparison and Merge Processes\nAdd CE\nAdd by Pick\nStatus\nESC\nThese options work only on entries in the Export list, rather than in the model\nNote:\nRemove CE\nRemove by Pick\nAdd by Pick\nESC\nRemove Selected\nRemove Selected\nClear\nError and Log File Messages\nCan't export the WORLD\nNo owning Structure\nCancel\nAVEVA SDNF Export\nExport\nControl\nControl\nRe-initialize, Configure, Map Converter\nExit\nRe-initialize\nConfigure\nMap Converter\nExternal Mapping Files\nExit\nGeneral\nHighlight\nHighlighter\nHighlighter\nValidation Process"}
{"Headers": "Export Process", "Content": "Exporting from the application, all items are exported using millimeters as the distance units.\nAll reference data, such as any pre-existing reference model, is removed before exporting anything. Details about saving the reference model are available. Refer to Import from SDNF for further information.\nPrior to any Export process, all fields are checked for validity.\nIn addition, there is an SDNF specific UDA, :SDNFEXCLUDE, attached to certain application elements by which you can define whether the item is to be exported or not. Setting this logical flag to true excludes the item from the Export process. Refer to UDAs for further information.\nBefore continuing, the Export process polls all the Configuration objects for the high water mark on Transfer and Revision numbers. It then updates the object applicable to the current MDB and user to contain the latest Transfer value.\nThe list of all items listed in the Export list is then stored on Header element.\nAfter verifying that all the data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. The amount of waiting time is configurable. If there are errors raised by the external program you are notified and more detailed information is placed in the log file. If the waiting period expires without the interface detecting that the external program has completed - it may have crashed, or even not exist, you are asked if to carry on waiting for another time unit.\n\nClick Yes and the interface waits for another period of time. Click No to stop the interface where it is. Finally the system indicates its completion, whether successful or not. The completion message should be read in conjunction with the log file, if any errors are indicated.\n\nThe message indicates a successful completion.\n\nThe error message indicates that a problem was encountered in the external program.\nOn completion of the external program, the status file is inspected and, if the result is favourable, you are then asked whether or not to view the log file, if that option has been selected on the Run Information window.\n\n\nTo inspect the log file later, save it with the File > Save as option in the File Viewer window which opens a File Browser, or click Save as to the suggested filename. Either way, if the file already exists, you are asked whether to overwrite it. The log file window may then be closed, click Cancel.\n\nIf the Brief mode has been chosen on the Run Information window for displaying the log file, the window displaying the log file filters out all warning messages, leaving only the error messages. Saving the log file, however, all messages are retained in the file.\nError and Log File Messages\nFile does not exist\nSomehow there is no log file. Are there issues regarding access rights to the%AVEVA_DESIGN_WORK% folder?\nFile does not exist\nSomehow there is no log file. Are there issues regarding access rights to the%AVEVA_DESIGN_WORK% folder?\n\nFile does not exist\nSomehow there is no log file. Are there issues regarding access rights to the%AVEVA_DESIGN_WORK% folder?\nIs the output file named?\nIs anything going to be exported?\nAre the mapping tables compatible with the Target Package?\nIs there a valid Steel Standard table?\nIs the output file named?\nIs the output file named?\nIs anything going to be exported?\nIs anything going to be exported?\nAre the mapping tables compatible with the Target Package?\nAre the mapping tables compatible with the Target Package?\nIs there a valid Steel Standard table?\nIs there a valid Steel Standard table?\n\n\n\nImport from SDNF\nUDAs\nImport from SDNF\nUDAs\nYes\nNo\nRun Information\nFile > Save as\nFile Viewer\nSave as\nCancel\nBrief\nRun Information\nError and Log File Messages\nFile does not exist"}
{"Headers": "Export Linear Members", "Content": "A series of checks is made before a Linear Member is output.\nIf any of the criteria is not satisfied, the linear member does not even get exported to the SDNF output file. As has been indicated before, Linear Members can be transferred as either Straight in Packet 10 or Curved in Packet 60. In SDNF, curved members are just circular arcs. However, GENSECs can be compound shapes with both straight and arc sections. As a result, SCTNs and straight portions of GENSECs are transferred through Packet 10, and the curved segments are transferred through Packet 60. Consult the section on importing Linear Members for further information about the reconstruction of complex GENSECs.\nIf the Linear Member is connected, the interface determines the offset of each end from its associated node.\nOnce the Linear Member has been output, the relevant UDAs specific for the interface associated with Export are updated. These are the mark numbers, the export date and time and transfer and revision numbers.\nThe SDNF interface may not be able to update the export information on the elements, usually because the database is read-only. If this is the case, a session related macro file is produced for execution immediately afterwards, or when one has write access to the database. The file is called updateVersionNos<export date/time>.mac and is stored in the AVEVA_DESIGN_WORK folder.\nError and Log File Messages\nIllegal or unset SPRE - Not exported\nSPRE must be valid.\nZero length Linear Member - Not exported\nLength less than user definable tolerance.\nNo material information - Not exported\nCannot determine material properties for member.\nNo material match for nnnn. - Unknown material\n:SDNFMGRADE cannot be matched with a material in the Properties database.\nNo material property match\n:SDNFMGRADE cannot be matched with a material in the Properties database.\nInconsistent material\nspecification\nThe element's MATR and :SDNFMGRADE attributes are not consistent.\nMultiply defined entries in Material Table\nEither a material to be mapped or a mapped profile appears more than once in the material file.\nNo match for material\nThe material is not in the material file\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThe error should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state is also output.\nNo match for Cardinal Point nnnn\nPline or Cardinal Point not recognized. Neutral axis (Cardinal Point 10) assumed.\nNo Cardinal Point nnnn\nJUSL unset.\nBad Cardinal Point nnnn\nCardinal Point/Pline identified is not valid. Does it exist? Neutral axis (Cardinal Point 10) assumed.\nProblem exporting entity\nOther errors found.\nProfile cannot be mapped\nThe profile is not in the profile mapping file.\nProfile is not in the standard\nThe profile is in the profile mapping file but is not in any one of the set of standards.\nProfile is not the default\nThe profile is in the profile mapping file and is in one of the set of standards, but not the default standard.\nMultiply defined entries in Profile Table\nEither a profile to be mapped or a mapped profile appears more than once in the profile mapping file.\nIllegal or unset SPRE - Not exported\nSPRE must be valid.\nZero length Linear Member - Not exported\nLength less than user definable tolerance.\nNo material information - Not exported\nCannot determine material properties for member.\nNo material match for nnnn. - Unknown material\n:SDNFMGRADE cannot be matched with a material in the Properties database.\nNo material property match\n:SDNFMGRADE cannot be matched with a material in the Properties database.\nInconsistent material\nspecification\nThe element's MATR and :SDNFMGRADE attributes are not consistent.\nMultiply defined entries in Material Table\nEither a material to be mapped or a mapped profile appears more than once in the material file.\nNo match for material\nThe material is not in the material file\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThe error should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state is also output.\nNo match for Cardinal Point nnnn\nPline or Cardinal Point not recognized. Neutral axis (Cardinal Point 10) assumed.\nNo Cardinal Point nnnn\nJUSL unset.\nBad Cardinal Point nnnn\nCardinal Point/Pline identified is not valid. Does it exist? Neutral axis (Cardinal Point 10) assumed.\nProblem exporting entity\nOther errors found.\nProfile cannot be mapped\nThe profile is not in the profile mapping file.\nProfile is not in the standard\nThe profile is in the profile mapping file but is not in any one of the set of standards.\nProfile is not the default\nThe profile is in the profile mapping file and is in one of the set of standards, but not the default standard.\nMultiply defined entries in Profile Table\nEither a profile to be mapped or a mapped profile appears more than once in the profile mapping file.\n\nIllegal or unset SPRE - Not exported\nSPRE must be valid.\nZero length Linear Member - Not exported\nLength less than user definable tolerance.\nNo material information - Not exported\nCannot determine material properties for member.\nNo material match for nnnn. - Unknown material\n:SDNFMGRADE cannot be matched with a material in the Properties database.\nNo material property match\n:SDNFMGRADE cannot be matched with a material in the Properties database.\nInconsistent material\nspecification\nThe element's MATR and :SDNFMGRADE attributes are not consistent.\nMultiply defined entries in Material Table\nEither a material to be mapped or a mapped profile appears more than once in the material file.\nNo match for material\nThe material is not in the material file\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThe error should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state is also output.\nNo match for Cardinal Point nnnn\nPline or Cardinal Point not recognized. Neutral axis (Cardinal Point 10) assumed.\nNo Cardinal Point nnnn\nJUSL unset.\nBad Cardinal Point nnnn\nCardinal Point/Pline identified is not valid. Does it exist? Neutral axis (Cardinal Point 10) assumed.\nProblem exporting entity\nOther errors found.\nProfile cannot be mapped\nThe profile is not in the profile mapping file.\nProfile is not in the standard\nThe profile is in the profile mapping file but is not in any one of the set of standards.\nProfile is not the default\nThe profile is in the profile mapping file and is in one of the set of standards, but not the default standard.\nMultiply defined entries in Profile Table\nEither a profile to be mapped or a mapped profile appears more than once in the profile mapping file.\nIs the SPRE set?\nIs it a zero length member?\nDoes it have a valid material?\nIs the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?\nAre the start and end points valid?\nIs the SPRE set?\nIs the SPRE set?\nIs it a zero length member?\nIs it a zero length member?\nDoes it have a valid material?\nDoes it have a valid material?\nIs the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?\nIs the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?\nAre the start and end points valid?\nAre the start and end points valid?\nNote:\nSubsequent import processes are affected if the member appears to have been deleted by the external steel detailing package since its export. In fact, the linear member might never made the transfer to the Target Package in the first place.\n\n\n\nNote:\nError and Log File Messages\nIllegal or unset SPRE - Not exported\nZero length Linear Member - Not exported\nNo material information - Not exported\nNo material match for nnnn. - Unknown material\nNo material property match\nInconsistent material\nspecification\nMultiply defined entries in Material Table\nNo match for material\nSyntax Error\nUnrecognized Parse State\nNo match for Cardinal Point nnnn\nNo Cardinal Point nnnn\nBad Cardinal Point nnnn\nProblem exporting entity\nProfile cannot be mapped\nProfile is not in the standard\nProfile is not the default\nMultiply defined entries in Profile Table"}
{"Headers": "Export Plates", "Content": "Panels in the application are to be transferred as Plates using Packet 20, inclusive of stiffeners, floor and toe plates. Bent plates are also transferred if they are expressed as their component flat plates. If Bent Plates are to be treated as Angle linear members then they should be modelled as such.\nIf the Penetration Application is used to generate Catalogue holes, the resultant holes, kicker plates and stiffeners are not exported because they are contained in a Catalogue definition. Some holes and negative primitives can be transferred from the model.\nThe Description attribute is used to store the flooring type, such as grating or chequer plate and is passed as the type field (up to 24 characters).\nThe Material Grade transferred in Packet 20 represents the material type. It is a text attribute, rather than the number field in the application. Therefore a User Defined Attribute (UDA), :SDNFMGRADE, has been defined within the application to store this information.\nA basic series of tests is performed before the Plate is exported.\nIf any of the criteria is not satisfied, the plate does not get exported in the SDNF output file.\nOnce the Plate has been output, the relevant UDAs specific for the interface associated with Export are updated. These are the mark numbers, the Export date and time and transfer and revision numbers.\nAlthough both plates and holes are supposed to have a clockwise definition (right hand screw rule) for their boundaries in either the application or in the SDNF file, the interface must be able to cope with either clockwise or anti clockwise directions. In exporting plates the vertex order is converted to satisfy the right-hand screw rule.\nComplex Plates (Type 1)\nPlates with curved and straight segments to their boundaries can be transferred both to and from the application. Because of the difference between the application and SDNF boundary definitions, vertices stand a high chance of being created in different places. Further, in order to recreate the shape, there may be a different number of vertices in the boundary. It can become very difficult to compare the boundaries, especially on import.\nIn order to assist the transfer of these complex shapes, the vertices are given a type code as a design parameter. The code indicates whether the following boundary segment is straight, an arc, or whether the vertex is a created one not contained in the SDNF file.\nComplex Plates (Type 2 - Circular Ones)\nCircular plates in the application are identified by the number of vertices, the geometry and possibly the vertex type codes. There is no short-hand definition of a circular plate in the application. As a result, a certain amount of geometric testing is involved in identifying and exporting circular plates. The interface recognizes only 4 or 5 point circles, where the 5th point is a duplicate of the first point.\nError and Log File Messages\nNo geometry information - Not exported\nNo PLOO element. Plate cannot be exported.\nPlate too thin - Not exported\nThickness less than user defined minimum. Plate not exported.\nNot enough vertices - Not exported\nFewer than 3 vertices. Cannot define valid geometry so Plate is not exported.\nNo material information - Not exported\nCannot determine material properties for member. A matching set of :SDNFMGRADE and Matref cannot be determined.\nNo material match for nnnn\nUnknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.\nNo material property match\nUnknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.\nInconsistent material specification\nThe element's MATR and :SDNFMGRADE attributes are not consistent.\nMultiply defined entries in Material Table\nEither a material to be mapped or a mapped profile appears more than once in the material mapping file.\nNo match for material\nThe material is not in the material mapping file.\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThe error should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state is also output.\nProblem exporting entity\nOther errors found.\nNo geometry information - Not exported\nNo PLOO element. Plate cannot be exported.\nPlate too thin - Not exported\nThickness less than user defined minimum. Plate not exported.\nNot enough vertices - Not exported\nFewer than 3 vertices. Cannot define valid geometry so Plate is not exported.\nNo material information - Not exported\nCannot determine material properties for member. A matching set of :SDNFMGRADE and Matref cannot be determined.\nNo material match for nnnn\nUnknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.\nNo material property match\nUnknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.\nInconsistent material specification\nThe element's MATR and :SDNFMGRADE attributes are not consistent.\nMultiply defined entries in Material Table\nEither a material to be mapped or a mapped profile appears more than once in the material mapping file.\nNo match for material\nThe material is not in the material mapping file.\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThe error should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state is also output.\nProblem exporting entity\nOther errors found.\n\nNo geometry information - Not exported\nNo PLOO element. Plate cannot be exported.\nPlate too thin - Not exported\nThickness less than user defined minimum. Plate not exported.\nNot enough vertices - Not exported\nFewer than 3 vertices. Cannot define valid geometry so Plate is not exported.\nNo material information - Not exported\nCannot determine material properties for member. A matching set of :SDNFMGRADE and Matref cannot be determined.\nNo material match for nnnn\nUnknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.\nNo material property match\nUnknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.\nInconsistent material specification\nThe element's MATR and :SDNFMGRADE attributes are not consistent.\nMultiply defined entries in Material Table\nEither a material to be mapped or a mapped profile appears more than once in the material mapping file.\nNo match for material\nThe material is not in the material mapping file.\nSyntax Error\nOther, less specific, errors.\nUnrecognized Parse State\nThe error should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state is also output.\nProblem exporting entity\nOther errors found.\nIs there any geometry?\nIs the height valid?\nIs it justified correctly?\nDoes it have a valid material?\nAre there enough vertices?\nIs there any geometry?\nIs there any geometry?\nIs the height valid?\nIs the height valid?\nIs it justified correctly?\nIs it justified correctly?\nDoes it have a valid material?\nDoes it have a valid material?\nAre there enough vertices?\nAre there enough vertices?\nNote:\nAny edge preparation details and modelling, such as grinding, will be lost in the transfer operation.\nNote:\nSubsequent import processes are affected if the plate appears to have been deleted by the external steel detailing package since its export. In fact, the plate might never made the transfer to the Target Package in the first place.\nNote: In Exporting a Plate, it has to be converted to the SDNF standard of being defined in a clockwise direction relative to the plane normal. Thus Importing a Plate previously defined in Model, you may find the order of vertices to have been reversed. Model is more tolerant about the ways in which you can define a plate.\n\n\n\nstiffeners, floor and toe plates\nPenetration Application\nNote:\nNote:\nNote\n:\nComplex Plates (Type 1)\nComplex Plates (Type 2 - Circular Ones)\nError and Log File Messages\nNo geometry information - Not exported\nPlate too thin - Not exported\nNot enough vertices - Not exported\nNo material information - Not exported\nNo material match for nnnn\nNo material property match\nInconsistent material specification\nMultiply defined entries in Material Table\nNo match for material\nSyntax Error\nUnrecognized Parse State\nProblem exporting entity"}
{"Headers": "Transfer of Holes", "Content": "There is a limitation as to which holes are exported. Only secondary PLOO boundaries and NXTR elements can be handled as well as NBOX and NCYL under certain conditions. PLOOs are full depth penetrations: partial penetrations can be modelled using NXTR elements. Circular boundaries of holes and indentations can be imported and exported if recognized as such, by having 4 unique fillet vertices.\nOn import, vertices in boundaries are given a DESP value.\nUsing these values, specific shapes can be detected, For example circles or ellipses.\nA message is output when the export process ignores most non loop-based negative primitives. It is difficult to determine the geometric intersection with the PANEL, especially if the primitive axis is not perpendicular to the plate plane. In the future it may be possible to handle some of them, but still only within tight geometrical constraints. Negative boxes and cylinders can be transferred only if a principal axis is parallel to the plate's normal. The cylinder's Z-axis, and any of the box's X, Y or Z-axis must be parallel to the plate normal. We even have to limit NXTR elements those with an extrusion vector parallel to the panel plane normal. Some negatives are not exported at all:\n(NBOX)\nNPOLYH\n(NCYL)\nNSLC\nNSNO\nNDIS\nNCON\nNPYR\nNCTO\nNRTO\n(NXTR)\nNREV\n(NBOX)\nNPOLYH\n(NCYL)\nNSLC\nNSNO\nNDIS\nNCON\nNPYR\nNCTO\nNRTO\n(NXTR)\nNREV\n\n\n\nImported holes are either NXTR or PLOO elements. A full penetration is a PLOO, and a partial penetration is an NXTR.\nAny other negatives are not compared or merged on import. Other pre-existing negatives are moved and updated to maintain the original position and orientation.\nPVTLastPoint\n0\nPVTStraight\n1\nPVTArc\n2\nPVTFillet\n3\nPVTCircle\n4\n(NBOX)\nNPOLYH\n(NCYL)\nNSLC\nNSNO\nNDIS\nNCON\nNPYR\nNCTO\nNRTO\n(NXTR)\nNREV\nPVTLastPoint\n0\nPVTStraight\n1\nPVTArc\n2\nPVTFillet\n3\nPVTCircle\n4\nPVTLastPoint\n0\nPVTStraight\n1\nPVTArc\n2\nPVTFillet\n3\nPVTCircle\n4\n\n\n"}
{"Headers": "Exporting Connections", "Content": "End connections and base plates are modelled in Design Catalogue items and transferred to the SDNF file using end coding information stored in the CTYA attribute of the Catalogue component. A mapping table is required to enable the information to be transferred in order that a corresponding entity can be created in the external 3D steel detailing package. Once the end has been detailed, the resultant geometry may be returned to Model as Plate members in Packet 20 for graphical and clash checks. In the application, joint selection is controlled by specification.\n\nAs it exports Connections (PJOI and SJOI elements), the interface uses only the old connectivity model. New connectivity elements, such as FIXIngs are not handled. The system initially checks that the SPRE attribute is set.\nIf so, the CTYA of the relevant Catalogue component is checked against the Connection mapping table. If it is valid, the local CTYS or CTYE attribute of the attached member is set for the sake of consistency. As it is doing so, the interface also checks that the connectivity references are consistent. The CTYA attribute is then matched against the required text for output in the SDNF file.\nThe interface also determines the identifier and end of the Linear Member to which the joint is attached.\nError and Log File Messages\nIllegal or unset SPRE\nSPRE must be valid.\nNo Connection Type - Not exported\nCannot determine CTYA attribute. Joint cannot be exported.\nInconsistent connectivity - Not exported\nConnectivity not consistent, so the joint cannot be exported. There is probably something more fundamentally wrong with the model.\nProblem exporting entity\nOther errors found.\nIllegal or unset SPRE\nSPRE must be valid.\nNo Connection Type - Not exported\nCannot determine CTYA attribute. Joint cannot be exported.\nInconsistent connectivity - Not exported\nConnectivity not consistent, so the joint cannot be exported. There is probably something more fundamentally wrong with the model.\nProblem exporting entity\nOther errors found.\n\nIllegal or unset SPRE\nSPRE must be valid.\nNo Connection Type - Not exported\nCannot determine CTYA attribute. Joint cannot be exported.\nInconsistent connectivity - Not exported\nConnectivity not consistent, so the joint cannot be exported. There is probably something more fundamentally wrong with the model.\nProblem exporting entity\nOther errors found.\n\n\n\nError and Log File Messages\nIllegal or unset SPRE\nNo Connection Type - Not exported\nInconsistent connectivity - Not exported\nProblem exporting entity"}
{"Headers": "Test AVEVA SDNF Export", "Content": "A test can be performed after installing the AVEVA SDNF product to make sure that the installation is complete and correct. All the required testing material can be found below the sub-folder SDNF\\test\\results\\export in the user data folder.\nThe test creates an SDNF model file output.\nInitial Configuration\nEnter Model. You must have write access to the database, even though you are testing the Export process. The interface records the date and time of export as well as the revision numbers of the elements transferred.\nSet the test project variables:\nChoose the SITE to export to SDNF by selecting SITE /TEST-SDNF-INTERFACE from the hierarchy list and drag it into the 3D display window.\nWhen that is finished, bring the SITE into view by adjusting the view limits. Refer to Limits for further information.\nIf required, modify the 3D view. Refer to Views for further information.\n\nPrepare for Export\nThe Export window allows you to export a steel structure to a SDNF file.\nYou may be asked to install a Configuration details element. If so, accept the request.\n\nOn this window and associated windows, fill in the details prior to Export.\nTarget Information\nClick Target information on the Export window to display the Export Target Information window.\nSelect the Auto option button and select AVEVA from the list of Target Packages on the Target Package drop-down list on the right hand side of the window. The system automatically detects the Target Package's Profile mapping table and Material mapping table.\nSelect the profile mapping file for the old catalogue named Aveva_E3D1.1.map. located in the Blockmaps\\Aveva folder.\nWhen the details are correct click OK.\nExport Information\nClick Export information on the Export window to display the Export Information window.\nIn the output file name field, input SDNF-Test.sdn\nCheck that the SDNF file header (Packet 00) is coming from /SDNF-CONFIG-DEMO-SYSTEM. Use the navigator and browser if necessary.\nSelect which SDNF Packets to export: Packet 10 (Straight), Members + End Connections and Packet 20 (Plates).\nWhen the details are correct click OK.\nRun Information\nClick Run information on the Export window to display the Export Run Information window.\nSelect the Log File? check box and choose Verbose for the message mode.\nDo not select the Test Run? check box as this is not a test run.\nWhen the details are correct, click OK.\nThe Main Export\nTo add the SITE to be exported to SDNF, Select SITE /TEST-SDNF-INTERFACE in the Members list. Click Add CE, all the members in the 3D view change colour to indicate they are being exported.\nThe Export window look similar to this.\n\n\n\n\nCreate Export File\nOn the AVEVA SDNF - Export window, click Export.\nThe status line displays the progress of the task.\nWhen the process is complete, you are asked whether to inspect the log file. You can then save it with the File > Save as option on the SDNF File Viewer window to display a File Browser, or click Save as to the suggested filename. The log file window can then be closed, click Cancel.\nCheck the SDNF Output Files.\nNote:\nThe configuration details should be available to the SDNF interface user always in read/write mode. This is because the export and import processes store information about how many transfers there have been made by the interface, and in which direction.\n\n\n\nLimits\nViews\nAVEVA SDNF\nSDNF\\test\\results\\export\nInitial Configuration\nModel\nLimits\nViews\nPrepare for Export\nExport\nNote:\nTarget Information\nTarget information\nExport\nExport Target Information\nAuto\nAVEVA\nTarget Package\nAveva_E3D1.1.map\nBlockmaps\\Aveva\nOK\nExport Information\nExport information\nExport\nExport Information\nSDNF-Test.sdn\nOK\nRun Information\nRun information\nExport\nExport Run Information\nLog File?\nVerbose\nTest Run?\nOK\nThe Main Export\nMembers\nAdd CE\nExport\nCreate Export File\nAVEVA SDNF - Export\nFile > Save\nSave\nCancel"}
{"Headers": "Import from SDNF", "Content": "Imports a steel structure from a SDNF file.\n\n\n\n"}
{"Headers": "Source Information", "Content": "Click Source Information to display the Import Source Information window which contains information about the 3D steel detailing package which the SDNF file is being transferred from.\n\nThe interface requires at least two external mapping tables for each Source Package to check that the design can accept the data. It also may use the Profile Orientation and/or the Unicode mapping table if necessary. The mapping tables are for the Steel Profiles, Materials, Unicode text string and for mapping the Profile orientations between the Neutral File and Model. The file arrangement on the system and required format is explained. Refer to Customise SDNF for further information. The interface also needs to know where the external mapping files are located on the computer network. For this internal mapping tables are required. The configuration and location of files is explained. Refer to Internal Mapping Files for further information.\nFor example, you can have a generic set of mapping tables to map between SDNF and the application for a particular steel fabricator. Or you can have a similar set for each 3D steel detailing package.\nThe current file settings are indicated on this window. Changing the Source Package using the Source Package drop-down list on the right hand side of the window may cause the text to change giving the full path names of the respective files.\nThe system also checks that these files are compatible with the Source Package by checking only the identification line at the top of each mapping table. The format of the mapping files is explained.Refer to Internal Mapping Files for further information.\nThe two main options are Auto and Manual which are activated by selecting the appropriate option button on the left hand side of the window.\nThe Auto option causes the interface to select automatically the mapping tables for the Source Package indicated by the Source Package drop-down list on the right hand side of the window, according to the system configuration files. When you execute the Import process, the Auto flag causes the correct mapping files to be used based on the Issue field in the Input file header. Details about the Input file header are available. Refer to Technical Information for further information.\nThe Manual option activates other option buttons, which are initially greyed out for the Auto option. Selecting this option changes the display of the window. For example\n\nYou can select the file type using the Profiles/Materials/Orient'n or Unicode radio buttons and input the full path name of the file in the data entry area. You can also include system environment variables in the path name as long as they are in the proper format, for example, %ENVVAR% being the representation of the ENVVAR environment variable.\nPress Enter, the interface checks for existence of the file and compatibility with the Source Package indicated by the Package drop-down list.\nYou can choose by hand which mapping file to use by either inputting its name in the text data entry field, or by using the Browse option to display a File Browser. Use this browser to search for the relevant mapping file.\nOnce all the correct data has been input on the Source Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.\nError and Log File Messages\nInternal error\nInternal lists are not in step.\nCannot find suitable internal mapping list\nInternal mapping files not found.\nSuitable Mapping Table File not found\nMapping table found is not for the correct Source Package, or it does not exist.\nNot a suitable Mapping Table File\nIncorrect format of file, or empty file, or wrong Source Package.\nBad Map File\nMapping file is not correct format. Possibly it is from another operating system.\nError on SDNF File Browser form\nYou have input incorrect data on the file browser.\nInternal error\nInternal lists are not in step.\nCannot find suitable internal mapping list\nInternal mapping files not found.\nSuitable Mapping Table File not found\nMapping table found is not for the correct Source Package, or it does not exist.\nNot a suitable Mapping Table File\nIncorrect format of file, or empty file, or wrong Source Package.\nBad Map File\nMapping file is not correct format. Possibly it is from another operating system.\nError on SDNF File Browser form\nYou have input incorrect data on the file browser.\n\nInternal error\nInternal lists are not in step.\nCannot find suitable internal mapping list\nInternal mapping files not found.\nSuitable Mapping Table File not found\nMapping table found is not for the correct Source Package, or it does not exist.\nNot a suitable Mapping Table File\nIncorrect format of file, or empty file, or wrong Source Package.\nBad Map File\nMapping file is not correct format. Possibly it is from another operating system.\nError on SDNF File Browser form\nYou have input incorrect data on the file browser.\nNote:\nDo not be concerned that the path name may be truncated by the insertion of the ellipsis (\u2026): it is modified only for display purposes on the window.\nNote:\nThe check is only that the file applies to the Source Package and not that it is a correct file type or format.\n\n\n\nCustomise SDNF\nInternal Mapping Files\nInternal Mapping Files\nTechnical Information\nSource Information\nImport Source Information\nCustomise SDNF\nInternal Mapping Files\nNote:\nInternal Mapping Files\nAuto\nManual\nAuto\nTechnical Information\nManual\nAuto\nProfiles/Materials/Orient'n\nUnicode\nEnter\nNote:\nSource Information\nOK\nCancel\nError and Log File Messages\nInternal error\nCannot find suitable internal mapping list\nSuitable Mapping Table File not found\nNot a suitable Mapping Table File\nBad Map File\nError on SDNF File Browser form"}
{"Headers": "Import Information", "Content": "Click Import Information to display the Import Information window which contains information about the import process.\n\nEither type the full folder path name of the input file, or click Browse to display a File Browser. The interface checks that the file exists and if it does not you are warned. As well as testing for the existence of the file, it is also tested for being a valid SDNF file by inspection of its header details.\nIn addition to the basic check for the input file being in SDNF format, the initial comments are scanned for the presence of a data table, which may list the Packets to follow and the number of items to be transferred in each one. If this table is present, it is analyzed and the check boxes determining which Packets may be Imported are selected or deselected accordingly. Refer to Technical Information for further information.\nOn inputting the name of the file, if it is from a recognized SDNF Source Package and if Auto mode is set on the Source Information window, the Profile and Material mapping files are selected automatically and indicated in the Source Information window, if it currently displays, along with the updated Source Package drop-down list.\nTo view the SDNF Header (Packet 00) of the chosen input file, click Inspect to display the Input File Header Details window with which you can determine whether the file is the correct one to Import.\n\nUsing the check boxes on the Import Information window, if they are active, you can select whether to import Packet 10 (Linear Members), Packet 60 (Curved Members) and/or Packet 20 (Plates) or Packet 22 (Holes).\n\nOnce all the correct data has been input on the Import Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.\nError and Log File Messages\nImport file does not exist\nFile specified does not exist.\nNot an SDNF File\nFile specified is not an SDNF file. The error may also arise if the file you are inspecting has been transferred across hardware platforms.\nNothing to import\nYou have deselected everything.\nCannot autodetect Source Package\nIf the AUTO option is on, the header of the Input file does not contain the Source Package information. The mapping table information has to be set by hand.\nImport file does not exist\nFile specified does not exist.\nNot an SDNF File\nFile specified is not an SDNF file. The error may also arise if the file you are inspecting has been transferred across hardware platforms.\nNothing to import\nYou have deselected everything.\nCannot autodetect Source Package\nIf the AUTO option is on, the header of the Input file does not contain the Source Package information. The mapping table information has to be set by hand.\nAuto-detection of SDNF Formats\nThe system can automatically detect which version of the file you are inputting.\nYou can set up the default SDNF format version in the SDNFUserData.pmlfnc file, the default version of which can be found in the SDNF\\dflts\\user\\SDNFPML\\functions folder in the user data folder. The !!SDNFSDNFVersion variable must be precisely one of the two suggested text strings.\nYou can inspect the file header as before and an added line indicates which SDNF version it has found.\n\nIf you change the version setting, the system does not work because it is expecting a file of a radically different format. However, the interface fails in a controlled manner producing a \"catch-all\" error message.\n\nIf you manually select the wrong SDNF version, you may also get an error message in the log file about syntax errors in the incoming file, indicating that the Packet 0 records are different.\nImport file does not exist\nFile specified does not exist.\nNot an SDNF File\nFile specified is not an SDNF file. The error may also arise if the file you are inspecting has been transferred across hardware platforms.\nNothing to import\nYou have deselected everything.\nCannot autodetect Source Package\nIf the AUTO option is on, the header of the Input file does not contain the Source Package information. The mapping table information has to be set by hand.\n  -- Default SDNF file format\n  -- currently |2.0| or |3.0|\n  !!SDNFSDNFVersion    = |3.0|\nNote:\nIf you do not input the full path name, the input file is assumed to be in the folder from which started the application. You can also include system environment variables in the path name as long as they are in the proper format, for example, %ENVVAR% being the representation of the ENVVAR environment variable.\nNote:\nYou cannot import Packet 40 (Connection Details) with this version of the interface. The interface checks that you are attempting to Import something if both options are unchecked.\n\n\n\nTechnical Information\nImport Information\nImport Information\nBrowse\nNote:\nTechnical Information\nAuto\nSource Information\nSource Information\nInput File Header Details\nImport Information\nPacket 10 (Linear Members)\nPacket 60 (Curved Members)\nPacket 20 (Plates)\nPacket 22 (Holes)\nNote:\nImport Information\nOK\nCancel\nError and Log File Messages\nImport file does not exist\nNot an SDNF File\nNothing to import\nCannot autodetect Source Package\nAuto-detection of SDNF Formats\nSDNFUserData.pmlfnc\nSDNF\\dflts\\user\\SDNFPML\\functions\n!!SDNFSDNFVersion"}
{"Headers": "Run Information", "Content": "Click Run Information to display the Import Run Information window which allows you to view the Log File after the import process is complete, select the Log File? check box.\n\nClick either the Brief or Verbose option buttons to choose which format messages are displayed.\nAs part of the Import process a reference model is constructed against which comparisons are made. Save Reference Model allows you to keep this. Otherwise it is deleted on completion of the Import process.\nAfter the Import merging process has been performed, you can sort all new items into FRMW (Framework) elements according to their Material type. Select the Sort on Material Type check box.\nDuring the Import process, comparisons are made for Linear and Curved Members and Plates between the existing model data and the imported model data. The default AVEVA SDNF system configuration compares all the relevant data transferred in the SDNF file between the models. However, you can select which attributes may be ignored by the comparison process, click Edit Attribute Comparison List.\n\nUsing this window you can deselect attributes for comparison but must be aware that strange results may occur especially if you ignore positional and rotational attributes.\nFinally, there are two validity checks that you can perform on the incoming data which make sure that a subsequent Import run has a chance of success. Activating these options overrides completely the Import choices made on the main window. With these validity checks you are able to view a log file before any data is merged whatsoever.\nProfile Mapping? enables you to view if the incoming Linear Member Profile specifications are successfully mapped between systems. The transaction is relatively fast as the SDNF file is passed through the external program without any subsequent import or comparison in the application. You are then able to view the log file produced and take appropriate action.\nThere is a risk in the external detailing package that entity mark numbers may be duplicated. The Duplicate Mark drop-down list enables you to check for duplicate numbers in the incoming model. There are three options: NONE, NEW and GLOBAL. NONE deactivates the drop-down list and no checks are made. The import process just goes through unhindered. The NEW option allows you to check only the new imported items for duplicate mark numbers, while the GLOBAL option enables you to search all the available Design databases for duplicate numbers. Obviously these searches may involve a certain amount of time, but for the sake of validity, they would be worth using.\nOnce all the correct data have been input on the Run Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged\nNote:\nThe reference model is deleted next time you Export or Import anything. Also, it may not be a complete model as some items may already have been transferred into the main model on merging.\n\n\n\nRun Information\nImport Run Information\nLog File?\nBrief\nVerbose\nSave Reference Model\nNote:\nSort on Material Type\nEdit Attribute Comparison List\nProfile Mapping?\nDuplicate Mark\nNONE\nNEW\nGLOBAL\nNONE\nNEW\nGLOBAL\nRun Information\nOK\nCancel"}
{"Headers": "Members and Operations", "Content": "On the Import window the Members list can be used to navigate around the database hierarchy.\nYou must state where the Imported model is to be located. The location must be a SITE, ZONE or STRU element. Using the Members list, navigate round the database to the correct storage location and click Store in: CE. The window text indicates where the Imported model resides. If there is not enough space on the window, the SITE's reference number is output rather than its name.\nThe Import process is essentially a three phase operation. First a reference model is built which is then compared with the original model identified during the Store in: CE operation. Then, if required, the changes, additions and deletions encountered in the comparison phase are transferred to the actual model. Thus, using the Operations toggles, you can control how the Import process is to proceed.\nYou should be aware of how the model manages partial model transfers and where temporarily imported data goes before it is merged into the pre-existing model. Refer to Comparison and Merge Processes for further information.\nCompare ( + Merge ) imports the model and compares the reference model with the location chosen to be the storage area. At this point you are asked whether to merge the models. Click Yes to continue with the merge process and complete the Import.\nCompare + Merge just goes through the complete Import process. For example, the import, comparison and merging are completed without any interaction. The action is only to be performed if you are absolutely sure that the outcome is correct.\nMerge from File takes a merge command file produced during the current session only and imports it directly into the model. The reference model must not have been deleted beforehand. Otherwise, you may lose any elements added to the model by the external detailing package. The option is very quick and there are no system checks.\nError and Log File Messages\nBad element type\nYou are not trying to store imported data at a SITE, ZONE or STRU element.\nBad element type\nYou are not trying to store imported data at a SITE, ZONE or STRU element.\nImport and Cancel\nThe Control item on the Import window has just one option, Exit, which removes all forms and menus and global variables associated with the interface.\nCancel closes the Import window.\nImport executes the Import process. As it proceeds you are kept informed of the progress.\nImport Bar Menu\nThe Control item on the Import window has four options: Re-initialize, Configure, Mapping Convertor and Exit. If you change any mapping files or any other variables:\nRe-initialize reloads these files to save you having to rebuild the whole User Interface from scratch.\nConfigure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information.\nMap Converter starts the tool that helps you rebuild Profile mapping files, refer to External Mapping Files for further information.\nExit command removes all forms and menus and global variables associated with the interface.\nThe General item has one option, Highlight which displays the Highlighter window enabling you to identify new, changed and deleted items in the model.\nBad element type\nYou are not trying to store imported data at a SITE, ZONE or STRU element.\nNote:\nThese options may be completely overridden if you want to perform a validity check as on the Run Information window.\n\n\n\nComparison and Merge Processes\nExternal Mapping Files\nImport\nStore in: CE\nStore in: CE\nOperations\nNote:\nRun Information\nComparison and Merge Processes\nCompare ( + Merge )\nYes\nCompare + Merge\nMerge from File\nError and Log File Messages\nBad element type\nImport and Cancel\nImport\nExit\nCancel\nImport\nImport\nImport Bar Menu\nControl\nImport\nRe-initialize, Configure, Mapping Convertor\nExit\nRe-initialize\nConfigure\nMap Converter\nExternal Mapping Files\nExit\nGeneral\nHighlight\nHighlighter"}
{"Headers": "Import Process", "Content": "Click OK to check the fields in the window for validity:\nAfter verifying that all the data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. The amount of waiting time is configurable. If there are errors raised by the external program you are notified and more detailed information is placed in the log file. If the waiting period expires without the interface detecting that the external program has completed - it may have crashed, or not even exist. You are asked if you want to carry on waiting for another time unit.\n\nClick Yes and the interface waits for another period of time. Click No to stop the interface where it is. Finally the system indicates its completion, whether successful or not. The completion message should be read in conjunction with the log file, if any errors are indicated.\nYou are alerted to unsuccessful runs by the external program displaying an error message, after which the process exits.\n\nIf the external program successfully completes, the processed SDNF file is imported into MODEL. Any reference data which may have been retained is deleted.\nThe status line informs you of the progress on importing the data. As a rough guide, the length of the input macro is about 25 times the number of elements. Thus a file transferring 300 members is about 7500 lines long.\nAfter the Import of everything, the material properties are reconciled with the :SDNFMGRADE attribute and, if possible, the MATR is also set to point to the appropriate property in the Properties database.\nAt this point, if you have chosen to be asked whether to Merge after the Compare operation, a Confirm window displays.\n\nClick Yes to continue with the Merge process.\nClick No and the Import process skips the Merge process, you are then given a chance to store the Merging commands in a file for use later only in the current session. You cannot use a file from a previous SDNF session as the Import data may be incorrect.\n\nYou can save the Merge command file and then be prompted whether to view the Import log file. The Merge command file may then be used in the Merge from File option on the AVEVA SDNF - Import window. The latter option needs the reference model from this run to be kept. Therefore, some other options become unavailable.\nIf you have merged the models, you are then asked if you want to keep the reference model, verifying the option selected on the Run Information window.\nThis reference model will not be the complete model as imported as various attributes and elements might have been modified, deleted or moved around.\n\nFinally, you are then asked whether to view the log file, if you have chosen that option on the Run Information window.\n\nIf you want to inspect the log file, you can save it with the File > Save as option in the SDNF File Viewer window which displays a File Browser, or click Save as to the suggested filename. If the file exists, you are asked if you want to overwrite it. The log file window can then be closed, click Cancel.\n\nIf you have chosen Brief mode on the Run Information window for displaying the log file, the window displaying the log file filters out all warning messages, leaving only the error messages. To save the log file, however, all messages are be retained in the file.\nIf you click a line containing an application reference number, the chosen item displays in all graphical views. The interface also navigates to the item in the database, allowing you to perform further queries or operations.\nError and Log File Messages\nFile does not exist\nSomehow there is no log file. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?\nInput file name not specified\nSomething strange here. The name of the macro generated has been forgotten.\nImport file does not exist\nSomething strange here. The macro file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?\nData store unset\nThe data store variable is unset or the SITE you had intended to store the imported data in is invalid. Has it been deleted since you set the store variable?\nFile does not exist\nSomehow there is no log file. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?\nInput file name not specified\nSomething strange here. The name of the macro generated has been forgotten.\nImport file does not exist\nSomething strange here. The macro file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?\nData store unset\nThe data store variable is unset or the SITE you had intended to store the imported data in is invalid. Has it been deleted since you set the store variable?\n\nFile does not exist\nSomehow there is no log file. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?\nInput file name not specified\nSomething strange here. The name of the macro generated has been forgotten.\nImport file does not exist\nSomething strange here. The macro file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?\nData store unset\nThe data store variable is unset or the SITE you had intended to store the imported data in is invalid. Has it been deleted since you set the store variable?\nIs the storage location valid?\nIs there a valid input file?\nDo we need to convert the file across platforms?\nAre the Profile and Material mapping files valid for the Source Package as identified in the Header of the input file?\nIs the storage location valid?\nIs the storage location valid?\nIs there a valid input file?\nIs there a valid input file?\nDo we need to convert the file across platforms?\nDo we need to convert the file across platforms?\nAre the Profile and Material mapping files valid for the Source Package as identified in the Header of the input file?\nAre the Profile and Material mapping files valid for the Source Package as identified in the Header of the input file?\nNote:\nThis calculation can be useful when considering the maximum input file size, the size applies to this file, and not the original SDNF source file.\n\n\n\nOK\nYes\nNo\nNote:\nConfirm\nYes\nNo\nMerge from File\nAVEVA SDNF - Import\nRun Information\nRun Information\nFile > Save as\nCancel\nBrief\nRun Information\nError and Log File Messages\nFile does not exist\nInput file name not specified\nImport file does not exist\nData store unset"}
{"Headers": "Comparison and Merge Processes", "Content": "The Import, Comparison and Merge process involves three stages. First, the model is imported. You then have the option of comparing the imported model with the original model, after which you may merge the new data into the old model, or the comparison and merge process can be performed as one with no interaction. Though you can tell the system to Import, Compare and Merge the model straight away this should only be performed if you are sure of the end result. It is advised that you Compare the models first and inspect the results before Merging.\nYou can decide to keep the imported reference model, but are warned that this is only to be regarded as transitory information. It may also not be a complete representation of the data imported as some of it is transferred to the real design area.\nIf the target area is empty, the Compare/Merge processes are bypassed which can be a lot faster when importing large amounts of data.\nThe Comparison Process\nThere are three conditions the AVEVA SDNF looks for:\nThe fact that an item is in the imported file and not in the original model is indicative of one of two cases: that the item has indeed been added by the external steel detailing package; or that the item was never exported in the first place for some reason. The latter case might also occur if the original model has had items added to it since the export happened. Further, items may appear to have been deleted and their clones imported when the import store location is not the same as it was for the export process.\nThe diagram illustrates the route through which the data is imported, compared and merged. New items are green, changed items are orange and deleted items are red.\n\nThe interface supports partial model transfer as it just identifies those new or changed items. Anything indicated as deleted is more an indication that the item is not present in the Imported SDNF file. It is not deleted from the Original Model during the Merge process: \"Deleted\" items are moved to another SITE to enable you to recover them if necessary. So parts of models can be merged into the original model with no loss of data.\nThe Comparison process allows any potential changes, additions and deletions to the original model to be detected and enhanced in a 3D view, if there is one present and if the items are in the current Drawlist.\nAs for both Linear Members and Plates you can select which attributes are significant for Comparison. The Comparison Checklist window which is a child of the Import Run Information window allows for this. By default, all the attributes transferred through the SDNF file are compared.\nCompare Linear Members\nThe detailed data attributes are compared between the original model and the reference model:\nImporting a Linear Member also sets the Import date and time UDAs. On merging members the revision number, transfer number and code are updated.\nThe log file messages recording any differences are of two formats: in Brief mode the results are presented on one line; in Verbose mode you are told what the old value was and the new value is so that you can view how the model has been changed. Details about the brief log file format are available. Refer to Brief Format for further information.\nYou may get a lot of apparent changes which may be caused by the failure to map the profile types between systems. The log file indicates which profiles have not been mapped. It is advised that you resolve the Profile Mapping issues first before becoming too concerned with other changes recorded in the log file.\nDuring the Import phase, an attempt is made to map the SDNF Cardinal Points in the incoming model with existing Plines that have been mapped onto them.\nCompare Plates (PANE)\nThe detailed data attributes are compared between the original model and the reference model:\nVertex positions are compared to within the user definable tolerance as described in the section on user customization of the interface.\nImporting a Plate also sets the Import date and time UDAs. On merging members the revision number, transfer number and code are updated.\nThe log file messages, recording any differences, are of two formats: in Brief mode the results are presented on one line; in Verbose mode you are told what the old value was and the new value is so that you can view how the model has been changed. Details about the brief log file format are available. Refer to Brief Format for further information.\nWe now compare plates with holes as secondary loops (PLOO) or NXTR primitives. We can now merge the imported model including new holes created outside of the application. However, because of the complexity of the comparison process, it is difficult to compare holes between the original and imported model. Where possible all other negative primitives representing holes in the original model are maintained. Therefore the comparison does not go down to the level of holes.\nMerge Process\nRefer to Comparison and Merge Processes for further information. The diagram illustrates the route by which information is transferred from the Import, through the Comparison and on to the Merging processes.\nThe AVEVA SDNF interface manages the Comparison and Merging of imported models so that other important engineering data is not lost or overwritten. However, other data, including connectivity may be lost.\nYou can separate the Comparison and Merging processes, so that you are able to view the log file in between operations. If you choose the Merge from File option on the main SDNF Import window, the Comparison process is deemed to have been completed and all that remains to be done is the actual Merging. The reference model for the current session must still be available. You are prompted for confirmation.\n\nIf, during the Merge phase, items are to be merged, the lists of added and deleted items are reconciled with the original model - by being deleted or transferred from the reference model. The storage SITE header details are then merged with the information in the SDNF header (Packet 00).\nAfter the main model Merging has been completed, if you have chosen the Sort on Material Type option on the Import window, any new items are sorted into FRMW groups according to their material type as specified by the :SDNFMGRADE attribute.\nThe version numbering system is described. Refer to Technical Information for further information.\nAdditional Items\nItems added to the model are recorded as such; they are indicated by changing their colour, a suitable message is output to the log file and they are then transferred to a special area. Merging transfers all the added items from the reference model to the original model. If required, they are then sorted according to material type.\nThe new items are gathered together into a site whose name is constructed from the Transfer and Revision Numbers so that you can easily locate all items added at a specific version or date.\nFor example, a new STRU may be created with the name of /SDNF-NEW-DEMO-SYSTEM/A.1 under the container element as specified in the Store in: field on the Import window. The components of this name are:\nthe system prefix\nidentification of new element container\nthe current MDB, for example, /DEMO\nthe current user name, for example, SYSTEM\nthe current Transfer letter, for example, 'A'\nthe current revision number, for example, '1'\nYou would be able to find all the added items to this MDB at this version.\nDeleted Items\nDeleted items in the model are recorded as deleted during the Compare phase and remain in the reference model to be deleted later if not required. The separation of operations allows you to view items that are deleted during the Merge process. Before deletion the objects are changed in colour so that they may be identified.\n'Deleted' items are disconnected from the old model and transferred from the current part of the database into a STRU created under the special 'Deleted' SITE.\nAs with the added items, the STRU is named out of components, thereby enabling you to determine at which version items may have been removed from the model.\nFor example, a new STRU may be created with the name of /SDNF-OLD-DEMO-SYSTEM/A.1 under the special SITE /SDNF-OLD-DEMO-SYSTEM. The components of this name are:\n/SDNF-\nthe system prefix\nOLD-\nidentification of new element container\n<mdb name>-\nthe current MDB, for example, /DEMO\n<user name>-/\nthe current user name, for example, SYSTEM\n<transfer nr>.\nthe current Transfer letter, for example, 'A'\n<revision nr>\nthe current revision number, for example, '1'\n/SDNF-\nthe system prefix\nOLD-\nidentification of new element container\n<mdb name>-\nthe current MDB, for example, /DEMO\n<user name>-/\nthe current user name, for example, SYSTEM\n<transfer nr>.\nthe current Transfer letter, for example, 'A'\n<revision nr>\nthe current revision number, for example, '1'\nYou would be able to find all the 'deleted' items to this MDB at this version.\nChanged Items\nIn merging Plates, the interface tries to keep the original vertices as they may have been used for locating dimensions on drawings: it may be that just the positions have been changed. However, the comparison only works in list order: the interface does not look around for another vertex in the same physical place, although it may be in a different list position. Extra unwanted vertices are deleted on merging and all new vertices are added to the end of the list. A totally new Plate is just imported directly.\nChanged objects are indicated as such by a change in colour.\nError and Warning Messages\nWARNING: Reference SITE nnnn contains transient data\nThe reference SITE is likely to be deleted some time.\nModel comparison completed\nProcess was successful.\nFailed to compare models\nDo they both exist?\nWARNING: Reference SITE nnnn contains transient data\nThe reference SITE is likely to be deleted some time.\nModel comparison completed\nProcess was successful.\nFailed to compare models\nDo they both exist?\n\n/SDNF-\nthe system prefix\nNEW-\nidentification of new element container\n<mdb name>-\nthe current MDB, for example, /DEMO\n<user name>-/\nthe current user name, for example, SYSTEM\n<transfer nr>.\nthe current Transfer letter, for example, 'A'\n<revision nr>\nthe current revision number, for example, '1'\n/SDNF-\nthe system prefix\nOLD-\nidentification of new element container\n<mdb name>-\nthe current MDB, for example, /DEMO\n<user name>-/\nthe current user name, for example, SYSTEM\n<transfer nr>.\nthe current Transfer letter, for example, 'A'\n<revision nr>\nthe current revision number, for example, '1'\nWARNING: Reference SITE nnnn contains transient data\nThe reference SITE is likely to be deleted some time.\nModel comparison completed\nProcess was successful.\nFailed to compare models\nDo they both exist?\nitems in the imported file that are not in the original model - Added items;\nitems in the original model that are not in the imported file - Deleted items;\nitems that it can match between the imported file and the original model and checks for modifications - Changed items.\nitems in the imported file that are not in the original model - Added items;\nitems in the imported file that are not in the original model - Added items;\nitems in the original model that are not in the imported file - Deleted items;\nitems in the original model that are not in the imported file - Deleted items;\nitems that it can match between the imported file and the original model and checks for modifications - Changed items.\nitems that it can match between the imported file and the original model and checks for modifications - Changed items.\nStart and end of Pline defined by Cardinal Point\nOrientation and Beta angle\nSpecification Reference\nStart and End releases\nMaterial grade and reference\nHold and Paint Spec UDAs\nFireproofing data\nStart and end of Pline defined by Cardinal Point\nStart and end of Pline defined by Cardinal Point\nOrientation and Beta angle\nOrientation and Beta angle\nSpecification Reference\nSpecification Reference\nStart and End releases\nStart and End releases\nMaterial grade and reference\nMaterial grade and reference\nHold and Paint Spec UDAs\nHold and Paint Spec UDAs\nFireproofing data\nFireproofing data\nPosition, orientation\nMaterial grade and reference\nHold and Paint Spec UDAs\nPanel loop height and justification\nNumber of vertices\nFireproofing data\nPosition, orientation\nPosition, orientation\nMaterial grade and reference\nMaterial grade and reference\nHold and Paint Spec UDAs\nHold and Paint Spec UDAs\nPanel loop height and justification\nPanel loop height and justification\nNumber of vertices\nNumber of vertices\nFireproofing data\nFireproofing data\nNote:\nThe Reference Model which is created is named according to the user session, so that several Reference Models can coexist at the same time. As they are named according to session, you are advised to take care to manage them and not to leave too many versions around to fill up disk space.\nNote:\nIn Exporting a Plate, it has to be converted to the SDNF standard of being defined in a clockwise direction relative to the plane normal. Thus Importing a Plate previously defined in Model you may find the order of vertices to have been reversed. Model is more tolerant about the ways in which you can define a plate.\nNote:\nAn item is not actually deleted from the original model. The apparent deletion may, in fact, be because the item was never transferred to the external detailing package in the first place due to some reason. Alternatively it may have been created in Model since the initial Export process had taken place.\n\n\n\nBrief Format\nBrief Format\nComparison and Merge Processes\nTechnical Information\nThe Comparison Process\n\nAdded\nDeleted\nChanged\nclones\nNote:\nComparison Checklist\nImport Run Information\nCompare Linear Members\nBrief\nVerbose\nBrief Format\nCompare Plates (PANE)\nBrief Format\nNote:\nMerge Process\nComparison and Merge Processes\nMerge from File\nImport\nSort on Material Type\nImport\nTechnical Information\nAdditional Items\nStore in:\nImport\n/SDNF-\nNEW-\n<mdb name>-\n<user name>-/\n<transfer nr>.\n<revision nr>\nDeleted Items\nNote\n:\n/SDNF-\nOLD-\n<mdb name>-\n<user name>-/\n<transfer nr>.\n<revision nr>\nChanged Items\nError and Warning Messages\nWARNING: Reference SITE nnnn contains transient data\nModel comparison completed\nFailed to compare models"}
{"Headers": "Validation Process", "Content": "As has been described in Comparison and Merge Processes there are two validation checks that can be performed prior to the full import and merging of models.\nThe first option is for profile mapping. The Profile Mapping? check box on the Run Information window turns this on. The Import process initializes normally and calls the external program to process the incoming SDNF file. In so doing it checks for a complete mapping of the profiles in the mapping tables. A log file is produced. No further Import actions are undertaken with this option.\nSecond, you can check that there are not any duplicate external mark numbers. Duplicates can quite easily come about if you copy members in the external detailing package without creating unique mark numbers for them. When they are imported into the application, the Comparison process may fail as it can be uncertain as to which member it is supposed to be comparing.\nThe options for this check are NEW and GLOBAL. NONE turns the facility off. NEW checks among all this run's imported members contained in the reference model for duplicate mark numbers, while GLOBAL checks the whole structural database, both imported and existing elements. These can be quite slow options as the reference model must be created and compared anyway.\nAs this option also calls the external program which checks the mapping of profile names between systems, the log file may also list any problems with the mapping tables. So this option is actually a combination of this and the validity checking option.\nRefer to Sample Validity Check Log File for further information.\nHighlight Changes in the Design\nFrom either the Import or Export windows, select General > Highlight from the top of the window to display the Highlighter window. The window allows you to identify in a graphical window whatever you want, either according to Import date, or by Transfer/Revision number combinations. The By option button switches the window into the appropriate mode. Both options work from the start element selected and indicate only those items that are in the drawlist.\nHighlight by Import Date\nThe window allows you to choose what to enhance on the screen according to the Import Date of an item.\n\nThe Selected items box part of the window allows you to select any combination of Added, Changed, or Deleted Items for identification, according to the date range.\nBy selecting the inclusive dates defining the limits of the range using the From and To date drop-down lists you can locate on the screen those items in the current drawlist which have been changed, added or deleted.\nHighlight by Version\nThe window allows you to choose what to indicate on the screen according to the Version of an item.\n\nThe rules of selecting the changed, deleted or added items are the same as Highlighting by Import Date.\nBy selecting the versions defining the limits of the range using the From and To version drop-down lists you can identify on the screen those items in the current drawlist which have been changed, added or deleted.\nError and Warning Messages\nBad date input\nThe configuration of day, month and year is illegal. Or is the start date after the end date?\nBad version input\nIs the start version after the end version?\nNothing to highlight\nNothing satisfies the selection criteria.\nBad date input\nThe configuration of day, month and year is illegal. Or is the start date after the end date?\nBad version input\nIs the start version after the end version?\nNothing to highlight\nNothing satisfies the selection criteria.\n\nBad date input\nThe configuration of day, month and year is illegal. Or is the start date after the end date?\nBad version input\nIs the start version after the end version?\nNothing to highlight\nNothing satisfies the selection criteria.\nNote:\nAs the 'deleted' elements are relocated in the database after Merging, the area where they are finally located should also be in the drawlist if you want to view what has been 'deleted'.\nNote:\nAs the 'deleted' elements are relocated in the database after Merging, the area where they are finally located should also be in the drawlist if you want to view what has been 'deleted'.\n\n\n\nComparison and Merge Processes\nSample Validity Check Log File\nComparison and Merge Processes\nProfile Mapping?\nRun Information\nNEW\nGLOBAL\nNONE\nNEW\nGLOBAL\nSample Validity Check Log File\nHighlight Changes in the Design\nImport\nExport\nGeneral > Highlight\nHighlighter\nBy option\nHighlight by Import Date\nSelected items\nNote:\nHighlight by Version\nNote:\nError and Warning Messages\nBad date input\nBad version input\nNothing to highlight"}
{"Headers": "Test AVEVA SDNF Import", "Content": "The test can be performed after installing the AVEVA SDNF product to make sure that the installation is complete and correct. The test must follow immediately the Export test described. Refer to Test AVEVA SDNF Export for further information. All the required testing material can be found below the sub-folder SDNF\\test\\results\\export in the user data folder.\nTake the SDNF file exported in the export test and modify it in a text editor. While referring to the description of the SDNF format. You can modify, for example, a mark number, a material and positions. Comparing the files SDNF-Test.sdn in the SDNF\\test\\results\\export and the SDNF\\test\\results\\import folders, which is found in the user data area, gives you some examples of edits that can be tested. Make sure that the resultant SDNF file is valid SDNF. Save the modified file under a different name, or in a different folder.\nThe test described imports an SDNF model file.\nInitial Configuration\nEnter Model. You should have write access to the database to enable you to import the new data. The interface records the date and time of import as well as the revision numbers of the elements transferred.\nSet the test project variables:\nSelect the Structures application.\nChoose the SITE to import from SDNF by selecting SITE /TEST-SDNF-INTERFACE from the hierarchy list and drag it into the 3D view.\nWhen that is finished, bring the SITE into view by adjusting the view limits. Refer to Limits for further information.\nIf required, modify the 3D view. Refer to Views for further information.\n\nPrepare to Import\nThe Import window allows you to import a steel structure from a SDNF file.\nYou may be asked to install a Configuration details element. If so, accept the request.\n\nOn this window and associated windows, you need to fill in the details prior to Import.\nSource Information\nClick Source information on the Import window to display the Source Information window.\nSelect the Auto option button and select AVEVA from the list of Source Packages on the Source Package drop-down list on the right hand side of the window. The system automatically detects the Source Package's Profile mapping table and Material mapping table.\nWhen the details are correct click OK.\nImport Information\nClick Import information on the Import window to display the Import Information window.\nIn the file name field, input the full path name of the modified source file.\nSelect which SDNF Packets to import: Packet 10 (Straight) and Packet 20 (Plates).\nWhen the details are correct click OK.\nRun Information\nClick Run information on the Import window to display the Import Run Information window.\nSelect the Log File? check box and choose Verbose for the message mode to get a verbose log file.\nSelect the Save Reference Model? check box in order to safe any reference model.\nFinally, you need to sort any new members added to the model by material type. Select the Sort on Material type? check box.\nA validity check on the incoming data, prior to importing it, can be performed.\nWhen the details are correct click OK.\nMain Import\nSelect the SITE into which the SDNF file is to be imported. Select SITE /TEST-SDNF-INTERFACE in the Members list and click CE by Store in:.\nA two stage import is then performed. Comparing the models first before Merging. So, select the Compare (+ Merge) option button.\nThe Import window should now look similar to this.\n\n\n\n\nImport the SDNF File\nOn the Import window, click OK.\nThe status line keeps you informed of the progress of the task.\nAfter the first stage of Import has taken place, you are asked by a Prompt window with the message. SDNF Interface (Confirm) - Model comparison completed. OK to merge models?. Click Yes to continue with the Merge process.\nWhen the process is complete a Confirm window is displayed.\n\nYou are then asked if you want to inspect the log file. If you do, you can save it with the File > Save as option in the SDNF File Viewer window to display a File Browser, or click Save as to the suggested filename. The log file window can be closed by the Cancel.\nCheck the log file against the changes made in the source SDNF file. The file should list the differences, changes, additions and deletions which have been made in the file.\nCompare Imported Model with the Original\nPrior to performing this test, you can copy the /TEST-SDNF-INTERFACE as a reference model to /ORIG-TEST-SDNF-INTERFACE. The reference model can be used to visually compare the imported model with the original. You can do this by adding the original model to the Drawlist in a different colour so that it is superimposed on the modified model. You can then inspect the 3D view closely for the differences recorded in the log file.\nYou can then Export the merged model to a file SDNF-Test-Mrg.sdn and compare the new SDNF file with the one provided in the test/results/import folder.\nPerform a Validity Check\nIf you want to perform a validity check on the incoming data before it is imported, display the Run Information window from the main Import window. Select GLOBAL for the Duplicate Mark Number search criterion. Click OK and fill in all the details on the main Import window.\nOnce all the details are correct on the Import window, click OK. The validation process is performed and in due course you are prompted to view the log file. Save the log file as SDNF-Test-Vfy.log and compare it with the results supplied in the test/results/import folder.\n\n\n\n\nTest AVEVA SDNF Export\nLimits\nViews\nTest AVEVA SDNF Export\nSDNF\\test\\results\\export\nSDNF-Test.sdn\nSDNF\\test\\results\\export\nSDNF\\test\\results\\import\nInitial Configuration\nModel\nLimits\nViews\nPrepare to Import\nImport\nSource Information\nImport\nSource Information\nAuto\nAVEVA\nSource Package\nOK\nImport Information\nImport information\nImport\nImport Information\nOK\nRun Information\nRun information\nImport\nImport Run Information\nLog File?\nVerbose\nSave Reference Model?\nSort on Material type?\nOK\nMain Import\nCE\nStore in:\nCompare (+ Merge)\nImport\nImport the SDNF File\nImport\nOK\nSDNF Interface (Confirm) - Model comparison completed. OK to merge models?\nYes\nConfirm\nFile > Save as\nSDNF File Viewer\nSave as\nCancel\nCompare Imported Model with the Original\nSDNF-Test-Mrg.sdn\ntest/results/import\nPerform a Validity Check\nRun Information\nImport\nGLOBAL\nOK\nImport\nImport\nOK\nSDNF-Test-Vfy.log\ntest/results/import"}
{"Headers": "Technical Information", "Content": "You should be aware of certain technical information, which is not immediately specific to AVEVA Products, in order to get the best out of the interface.\n\n\n"}
{"Headers": "SDNF - Structural Steel Detailing Neutral File Format", "Content": "All of the related Packets must be output at the same time. You cannot export a set of Linear Members and some time later another set.\nComments may be inserted anywhere through the file. They are indicated by the # symbol as the first non blank character.\nLines, apart from the Packet identifications, are free format delimited by spaces, up to a maximum length of 132 characters.\nText or character values are enclosed in double quotation marks, '\"'.\nAny '\"' characters within such values are replaced with '.\nThe SDNF format is described as an ASCII file without further description of encodings or character sets. The SDNF interface attempts to transfer non-ASCII characters where appropriate, but warns if any characters with their 8th bit set are written to an SDNF file.\nExport/Import different SDNF Formats\nThe interface can read SDNF files in both version 2 and version 3 of the format but write to only version 3.\nAuto-detection of SDNF Formats\nThe system can automatically detect which version of the file you are inputting, you should need to do no more.\nYou can inspect the file header as before and an added line indicates which SDNF version it has found.\n\nPacket 00 - Title Packet\nPacket 00 is the SDNF file header. Only 1 Packet of this type must be included. It describes the run for the data transfer. Its record structure is:\n\nrepeat Record 11 as stated in Record 10\nPacket 10 - Linear Members\nStraight Linear Members are the elements represented in Model by SCTNs and the straight segments of multi-segment GENSECs - straight prismatic profiles. They are described in the SDNF file.\n\nThere are several ways of defining a Linear Member using different combinations of the data elements, some of which are not interpretable by other systems. The method of interpretation of these fields is defined.\nLocation of Linear Members in Space\nClose and rigorous study of the definition of Linear Members in SDNF reveals that there are many ways in which a Linear Member may be located in space. Combinations of information stored in records 3 to 5 per Linear Member determine the location. The main requirement is that the Cardinal Point is to be used to draw the lines in schematic drawings such that, where possible, a connected model may be deduced.\nMore generally, the interpretation is:\nRecord 4 is ignored completely - (2D X/Y offsets)\nThe Start and End cutbacks (Record 3) are ignored by default but can be enabled. Refer to Linear Member Cutbacks for further information.\nThe Start and End Position of the Member (Record 3) is the start and end position of the 'real length of steel' located on the line described by the Cardinal Point (Record 1).\nThe 3D Start and End Eccentricities (Record 5) then define the real start and end of the Cardinal Point 'Line' relative to the Node, if any. Thus, using Record 5 with Record 3, the Node position can be determined. AVEVA SDNF would export this value, but does not do anything with it on import.\nAll packages are assumed to export the start and end positions of the Linear Member's Cardinal Point line.\nRotation and Orientation Vector\nThe Rotation and Orientation Vector attributes of a Linear Member determine the orientation of the element about its axis. The Orientation Vector defines the default orientation of the member before any rotation has been applied to it.\nThe Rotation is then taken as a right handed rotation about the axis from that default vector as one looks along the member from start to end - the local Z axis.\nPacket 20 - Plates\nPlates are represented in the application by PANE elements as loops on the upper and lower faces.\n\nEach plate is represented by a variable number of records:\n\nPlate periphery defines the type of boundary: 0 is a boundary with straight edges; 1 is a boundary with straight and curved segments; 2 is a circle. For both boundaries type 0 and 1, there are 2 loops of vertices, one for the plate top and the other for the plate bottom. For circular plates (type 2) there are 2 vertices representing the circle centre on the top and bottom faces.\nEach set of vertex coordinates is followed by a flag that indicates whether the following boundary segment is straight or curved. In the case of the circular plate the \"flag\" is the circle radius.\n\nThe last vertex in the boundary, a duplicate of the first, has a connection flag of 0. Straight segments are indicated by the flag value of 1, curved segments by 2.\n\nRules of interpretation apply to the fields.\nOrder of Vertices\nWhen exporting, the vertices describing a Plate are assumed to be defined in a manner according to the Right Hand Screw Rule, where the vertices are in a clockwise order when viewed along the normal to the Plate plane. For version 3 files, there is less of a requirement for the vertices to follow this rule as the interface can determine the plane normal from the separation between the loops.\nWhen importing, the vertices may be defined in either direction.\nPlate Origin\nThe Plate Origin is taken to be the position of the first vertex. This can cause confusion on import when the plate's origin has appeared to have changed. The more important thing is to see if the plate is in the same place.\nPlate Orientation\nThe vector from the first vertex to the next vertex is taken as the local X axis. Knowing the fact that the plate is defined in a Right Hand Screw Rule manner, the plane normal can be determined, in turn determining the local Z axis. The Y axis then becomes the vector cross product of the Z and X axes.\nPacket 22 - Holes\nThe geometric description of holes is very similar to that of their owning plates. Tests are made on import to verify that the hole does penetrate the owning plate. A hole completely penetrating the plate is translated into a secondary PLOO. Partially penetrating holes - depressions in the plate surface - are represented as NXTR elements.\nPacket description\n\nEach hole is represented by a variable number of records:\n\nSometimes, holes have been allocated to the wrong plate, this can be because the plates do not have a unique identifier.\nHole periphery defines the type of boundary: 0 is a boundary with straight edges; 1 is a boundary with straight and curved segments; 2 is a circle. For both boundaries type 0 and 1, there are 2 loops of vertices, one for the hole top and the other for the hole bottom. For circular holes (type 2) there are 2 vertices representing the circle centre on the top and bottom faces.\nEach set of vertex coordinates is followed by a flag that indicates whether the following boundary segment is straight or curved. In the case of the circular hole the \"flag\" is the circle radius.\n\nThe last vertex in the boundary, a duplicate of the first, has a connection flag of 0. Straight segments are indicated by the flag value of 1, curved segments by 2.\n\nPacket 30 - Member Loading\nLoading of elements is not transferred by this interface.\n\nNo loads along the member are catered for.\nPacket 40 - Connection Details\nThe Connection Details attached to one or each end of a Linear Member are described here. In design terms they are modelled by Primary or Secondary Joints. The mechanism by which the description text in record 3 is obtained is explained. The record structure is:\n\nThe description is purely textual, no geometry is passed, for example, sniping.\nPacket 50 - Grid Packet\nGrid Packets are not transferred in this interface.\n\nPacket 60 - Format Definition\n\nFor the succeeding records, each arc member is represented by the 11 records, total of 11 times n records, where n is number of members from Record 2 (376 in the example).\n\nNote:\nThe Issue Code (Record 8) holds the Source Package of the SDNF file.\nNote:\nThe sense of this eccentricity is a vector from the end of the member to the node position.\n\n\n\nLinear Member Cutbacks\nth\nExport/Import different SDNF Formats\nAuto-detection of SDNF Formats\nPacket 00 - Title Packet\nNote:\nPacket 10 - Linear Members\nLocation of Linear Members in Space\nLinear Member Cutbacks\nNote:\nRotation and Orientation Vector\nPacket 20 - Plates\nOrder of Vertices\nPlate Origin\nPlate Orientation\nPacket 22 - Holes\nPacket 30 - Member Loading\nPacket 40 - Connection Details\nPacket 50 - Grid Packet\nPacket 60 - Format Definition"}
{"Headers": "Recommended SDNF File Suffix", "Content": "Although it is not critical for this interface, the recommended suffix for the SDNF files is to be '.sdn'.\n\n\n"}
{"Headers": "Cardinal Points", "Content": "The diagram illustrates the positions of the Intergraph FrameWorks Cardinal Points. FrameWorks cannot handle Cardinal Points above Point 10, but for this interface it is expected that all interfaces in this project are able to handle all 14.\nOn transfer between systems, the Cardinal Point imported should be retained for later export. A source of confusion can be when a member originally laid out on Cardinal Point 14 (Top of Steel) is returned on the Cardinal Point 10 (Neutral Axis). It causes minor problems in model versioning and comparisons.\n\n\n\n"}
{"Headers": "Cross Reference Models", "Content": "Cross referencing models is the mechanism by which you can identify members in different models other than by visual comparison. There are two scenarios: one where an element is created in Model; the other is where it was created in any other system, but is to be imported into Model. The Id field in the SDNF file is not a reliable identifier as it tends to be only a sequential item count produced on the generation of the SDNF file.\nElement created in Model\nWhen an element is created in Model it gains a unique internal reference number of the form \"=<integer>/<integer>\", for example, =13/2305. On export from Model this value, excluding the initial '=' character, is passed through in Packet 10 or 20 in the Mark fields. These are text strings on Records 3 and 3a respectively. Any system importing this file should be able to take this value and store it, or use it to you to identify the Design member in the external steel detailing package.\nOn Export back to the application, for any member which has this Mark attribute set, the original imported Mark value appears again in the SDNF file. Thus you are able to spot any changes to the model. The AVEVA SDNF Import system, then allows you to modify the existing structure, rather than just replacing it with a copy. In this way, any drawings for example, which may have been produced between Export from and Import back to Model, retain their logical relationships to the steel members.\nElement created outside Design\nA member created outside Model does not have the Mark field set to be an application internal reference number. The AVEVA SDNF interface would therefore know that it was importing a new element and would create it accordingly, whilst recording the external Mark number as well.\nIf SDNF detects that there are duplicate external mark numbers as it is preparing to export a model, the internal reference number is used in preference. The SDNF interface then has some chance of identifying the element if it returns from the external package. Refer to Issues Concerning Entity Comparison for further information.\n\n\n\nIssues Concerning Entity Comparison\nElement created in Model\nElement created outside Design\nIssues Concerning Entity Comparison"}
{"Headers": "Stairs Ladders Handrails Functionality", "Content": "The SLH application provides a bespoke database architecture of SLH elements comprising of administrative elements.\nThe elements are the high level administrative elements that are owned by the existing STRU hierarchy element, the elements, with their easily identifiable element type definition, supports the \u2018Assembly\u2019 type concept employed throughout the application where all of the detailed 3D modelling is represented using the existing structural objects such as Gensec, Panel, and Template. For a detailed explanation of the elements, refer to the Structural Design User Guide. Throughout the application, the workflow associated with the creation and modification of the elements follows a consistent format through a common user interface.\n\n\n\nStructural Design User Guide"}
{"Headers": "SLH Specific Hierarchy", "Content": "The SLH elements of Stair Flight, Step Ladder, Rung Ladder and Handrail are all POS/ORI elements whose hierarchical ownership is that of a STRU. The SLH elements should be considered as fabrications in their own right as they in turn own specific objects fulfilling an engineering function whose naming convention reflects the engineering function.\n\nThe elements have been architected to suit specific functionality and workflow to provide definite engineering purpose and their attributes set accurately mirrors the engineering criteria for that object. The attributes are evaluated by the system in response to the user\u2019s interaction with the 3D model environment and the relevant attributes are managed through the database hierarchy by the SLH application.\n\n\n"}
{"Headers": "Application Data Worlds (APPLDW)", "Content": "For more detailed information regarding Application Data Worlds sets refer to the Design Reference Manual Creating the Model.\nApplication Data Worlds and their elements assist applications to store assemblies and 3D model parts for copying and propagation within a design. They have some similarities with Templates, but are more general in content.\nThey are used for SLH assembly data and also by the Piping discipline.\nThe elements available are administrative elements allowing applications to organize data storage areas of design objects that are not part of the design itself, but supplementary objects used to create and maintain the 3D model. They are not accessed (unless specifically instructed to do so) when performing 3D model queries such as clashing, mass properties, collections and they are similar to catalogue and in particular Template definitions.\n\n\n\nDesign Reference Manual Creating the Model"}
{"Headers": "Stair Flight (STRFLT) Hierarchy", "Content": "The Stair Flight element (STRFLT) is a top level administrative element owned by a STRU element.\nThe STRFLT as a steelwork assembly enables the user to create a rule based linear Stair Flight and it introduces a middle tier hierarchy to enable the decomposition of the STRFLT assembly into its logical component parts, the existing lower level elements of GENSEC and PANEL are used to represent the detail of the 3D model.\n\nStair Stringer (STRSTR)\nSTRSTR owns the two GENSEC elements used to model the main supports of the Stair Flight. The GENSEC elements are automatically miterd by the application at the upper and lower elevations of the STRSTR, dependent upon the relevant Selections.\nRoute Path (RPATH)\nThe Routing Path element defines an open path or closed boundary using the following:\nRoute Point (POINTR)\nPOINTR elements are significant point references which form the RPath.\nTop Extension (TOPEXT)\nTOPEXT owns the PANEL element used to model the physical representation of the top extension of the stair flight. It is defined by the extrusion of a profile representing the panel's shape (the Panel Loop. PLOOP) through a given distance (equivalent to the panel thickness). A PAVE element defines each vertex of a Panel Loop.\nBottom Extension (BOTEXT)\nBOTEXT owns the PANEL and Stringer elements used to model the physical representation of the bottom extension of the stair flight. It is defined by the extrusion of a profile representing the panel's shape (the Panel Loop. PLOOP) through a given distance (equivalent to the panel thickness). A PAVE element defines each vertex of a Panel Loop.\nIntermediate Landing (INTLNG)\nINTLNG owns the PANEL and Stringer elements used to model the physical representation of the intermediate landing of the stair flight. It is defined by the extrusion of a profile representing the panel's shape (the Panel Loop. PLOOP) through a given distance (equivalent to the panel thickness). A PAVE element defines each vertex of a Panel Loop.\nTread Set (TREADS)\nThe TREADS element is used to manage the ownership of individual TREAD elements.\nTread (TREAD)\nTREAD owns the 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.\nPANEL, TMPL or Catalog elements can be used to model the rise or tread in the STRFLT.\nDescription of Stair Flight Elements\nThe following figure shows some of the attributes of the STRFLT elements and the elements that it owns. The figure also indicates the engineering significance of the attributes to the geometrical representation of the STRFLT.\n\nUpon creation of the Stair Flight the system analyzes the horizontal (Overall Going) and vertical (Overall Rise) distances between the Lower and Upper Work Points (LWP/UWP) and validates 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 creates the Stair Flight and populates the attributes with the appropriate data.\n\nFree form sketching\nTracing existing profiles or boundaries.\nFree form sketching\nFree form sketching\nTracing existing profiles or boundaries.\nTracing existing profiles or boundaries.\n\n\n\nStair Stringer (STRSTR)\nRoute Path (RPATH)\nRoute Point (POINTR)\nTop Extension (TOPEXT)\nBottom Extension (BOTEXT)\nIntermediate Landing (INTLNG)\nTread Set (TREADS)\nTread (TREAD)\nDescription of Stair Flight Elements"}
{"Headers": "Step Ladder (SLADDR) Hierarchy", "Content": "The Step Ladder element (SLADDR) is a top level administrative element owned by a STRU element.\nThe SLADDR as a steelwork assembly enables the user to create a rule based linear step ladder and it introduces a middle tier hierarchy to enable the decomposition of the SLADDR assembly into its logical component parts, the existing lower level elements of GENSEC and PANEL are used to represent the detail of the 3D model.\n\nStair Stringer (STRSTR)\nSTRSTR owns the two GENSEC elements used to model the main supports of the Step Ladder. The GENSEC elements are automatically miterd by the application at the upper and lower elevations of the STRSTR, dependent upon the relevant selections.\nTread Set (TREADS)\nThe TREADS element is used to manage the ownership of individual TREAD elements.\nTread (TREAD)\nTREAD owns the elements used to model the rise or tread in the SLADDR. 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 SLADDR.\nPANEL, TMPL or Catalog elements can be used to model the rise or tread in the SLADDR.\nTop Extension (TOPEXT)\nTOPEXT owns the PANEL element used to model the physical representation of the top extension of the step ladder. It is defined by the extrusion of a profile representing the panel's shape (the Panel Loop. PLOOP) through a given distance (equivalent to the panel thickness). A PAVE element defines each vertex of a Panel Loop.\nStep Ladder Rail (SLRAIL)\nSLRAIL owns the GENSEC elements used to model the rails of the Step Ladder.\n\n\n\nStair Stringer (STRSTR)\nTread Set (TREADS)\nTread (TREAD)\nTop Extension (TOPEXT)\nStep Ladder Rail (SLRAIL)"}
{"Headers": "Ladder (RLADDR) Hierarchy", "Content": "The Ladder element (RLADDR) is a top level administrative element owned by a STRU element.\nThe RLADDR as a structural assembly introduces functionality enabling the user to create a rule based RLADDR and also introduces a middle tier hierarchy to enable the decomposition of the RLADDR into its individual assemblies of Stringers, Rungs, Safety Cages. Throughout the middle tier hierarchy the elements owned by GENSECs are used to represent the detail of the 3D model.\n\nRung Ladder (RLADDR)\nThe Ladder element (RLADDR) is a top level administrative element owned by other SLH administrative elements i.e STRU, FRWM and /or SBFR.\nRung Ladder Cage (RLCAGE)\nThe RLCAGE element is an administrative element which owns the Cage Segment (CAGSEG) element.\nCage Segment (CAGSEG)\nThe CAGSEG element owns the GENSEC and PANEL steelwork elements used to model the physical representation of the cage. By default, there are two cage segments, one representing the entry/exit at the top of the ladder and the other representing the remainder of the cage itself. This mechanism allows the entry/exit detailing of the cage to be modified individually from the remainder of the cage.\nLadder Stringer (LDRSTR)\nThe LDRSTR element is an administrative element which owns the appropriate number of GENSEC steelwork elements used to model the main supports of the rung ladder.\nLadder Rung Set (RUNGSE)\nThe RUNGSE element is an administrative element which is used to manage the ownership of individual LDRRUN elements. This is dependent upon the design of the rung and is intended to support a variety of rung types.\nLadder Rung (LDRRUN)\nThe LDDRUN element owns the GENSEC, PANEL or catalogue elements used to model the physical representation of the rung.\n\n\n\nRung Ladder (RLADDR)\nRung Ladder Cage (RLCAGE)\nCage Segment (CAGSEG)\nLadder Stringer (LDRSTR)\nLadder Rung Set (RUNGSE)\nLadder Rung (LDRRUN)"}
{"Headers": "Handrail (HANDRA) Hierarchy", "Content": "The Handrail element (HANDRA) is a top level administrative element owned primarily by the STRU element as well as other administrative elements.\nThe Handrail introduces functionality enabling the user to create rule based arrangements and layouts of Handrails and introduces a new middle tier hierarchy to enable the decomposition of the Handrail into its individual components, TMPLs are used to represent the detail of the 3D model.\n\nThe underlying technology responsible for defining the route of the Handrail element is the Routing Path element, this provides the functionality to define an open path or closed boundary via the following;\nPost Set (POSTSE)\nThe POSTSE is responsible for the ownership and management of multiple HRPOST elements.\nHandrail Post (HRPOST)\nHRPOST element represents the post detail which references the catalogue items or templates as it has a SPREF attribute, the position of the HRPOST is defined with respect to the owning HANDRA in terms of its position along the path and the offset from the path of the HANDRA.\nRail Set (RAILSE)\nRAILSE is responsible for the ownership and management of multiple RAIL elements whose physical representation is modelled using a RAIL element.\nHandrail Rail (RAIL)\nRAIL 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.\nThe RAIL shares the same underlying attributes and behavior as the KICKPL element.\nHandrail Kick Plate Set (HRKPSE)\nHRKPSE is responsible for the ownership and management of multiple Kick plate elements whose physical representation is modelled using a KICKPL element.\nKick Plate (KICKPL)\nKICKPL is used to model the detail representation of a kick plate and follows the path of the HANDRA, the KICKPL references the existing catalogue steel profiles via its SPREF attribute and the position of the KICKPL is defined with respect to the owning HANDRA in terms of its position along the path and the offset from the path of the HANDRA.\nThe KICKPL shares the same underlying attributes and behavior as RAIL element.\nHandrail Panel Set (HRPNSE)\nHRPNSE is responsible for the ownership and management of multiple HRPANE elements.\nHandrail Panel (HRPANE)\nHRPANE is the database element responsible for the representation of 'panelised' sections of Handrail where the Panel size is determined by its Panel Size attribute. The detail of the HRPANE is represented using the existing database functionality of TMPL and the route of the HRPANE elements is defined using the RPATH routing object.\nHandrail Feature (HRFEAT)\nHRFEAT owns HRGATE elements. The HRFEAT also owns RATTA elements which at this hierarchical level provide a connectivity mechanism to/from the boundary of the HANDRA.\nHandrail Gate (HRGATE)\nHRGATE is an element used to represent access locations along the path of the HANDRA and there can be multiple HRGATE elements in any HANDRA and the position of the HRGATE is managed by the application as a position along the RPATH element. HRGATE elements are managed as negative geometry and penetrate only the HANDRA and additional detail for the HRGATE is represented using the existing database functionality of TMPL.\nTerminations (TERM)\nThe Termination element represents any shape Loops, End Plates, post, and so on.\nFree form interactive sketching using the Route sketching functionality\nTracing existing profiles or boundaries.\nFree form interactive sketching using the Route sketching functionality\nFree form interactive sketching using the Route sketching functionality\nTracing existing profiles or boundaries.\nTracing existing profiles or boundaries.\n\n\n\nPost Set (POSTSE)\nHandrail Post (HRPOST)\nRail Set (RAILSE)\nHandrail Rail (RAIL)\nHandrail Kick Plate Set (HRKPSE)\nKick Plate (KICKPL)\nHandrail Panel Set (HRPNSE)\nHandrail Panel (HRPANE)\nHandrail Feature (HRFEAT)\nHandrail Gate (HRGATE)\nTerminations (TERM)"}
{"Headers": "SLH Administration Tasks", "Content": "All the tasks that an administrator would carry out that are associated with the creation or modification of SLH Standards, Defaults, Assemblies and Templates are initiated from a central SLH Administration Tasks window which acts as a task hub.\nDepending on selections made in the SLH Administration Tasks window, the administrator is presented with further windows prompting for input. After inputting information in the windows the administrator is always returned to the SLH Administration Tasks window allowing for workflow to continue.\nTo open the SLH Administration Tasks window, on the Admin tab in the Structures group, click SLH Tasks to display the SLH Administration Tasks window.\n\nThe general user is not able to access the Admin Tasks window as it is available only to users of an administrator level (member of the STRUADMIN or SLHADMIN team).\n\n\n\nSLH Administration Tasks\nSLH Administration Tasks\nSLH Administration Tasks\nSLH Administration Tasks\nSLH Tasks\nSLH Administration Tasks\nAdmin Tasks"}
{"Headers": "SLH Administrative Hierarchy", "Content": "Before any standards, defaults, assemblies or templates can be created, the administrator must create some essential database elements using the SLH Administration Tasks window. All standards, defaults, assemblies and templates are stored in an application data world.\n\n\n\nSLH Administration Tasks"}
{"Headers": "Application Data World (APPLDW)", "Content": "Application Data Worlds and the Elements available are administrative elements allowing applications to organize data storage areas of design objects that are not part of the design itself, but supplementary objects used to create and maintain the 3D model. They have some similarities with Templates, but are more general in content.\nThey are not accessed (unless specifically instructed to do so) when performing 3D model queries such as clashing, mass properties and collections, they are similar to catalogue and in particular Template definitions.\n\n\n"}
{"Headers": "Create Data World", "Content": "To create a Data World element, from the Data World part of the SLH Administration Tasks window, click Create next to the Data World drop-down list to display the Create SLH Application Data World window.\n\nThe owning database displays at the top of the Create SLH Application Data World window.\nName\nInput a name for the new Data World element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nName\nInput a name for the new Data World element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nClick Create to create the Data World element or Cancel to discard any inputs and close the Create SLH Application Data World window.\nThe Data World element displays in the Model Explorer.\n\nName\nInput a name for the new Data World element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\n\n\n\nSLH Administration Tasks\nCreate\nCreate SLH Application Data World\nCreate SLH Application Data World\nName\nDescription\nFunction\nCreate\nCancel\nCreate SLH Application Data World"}
{"Headers": "Modify Data World", "Content": "To modify a Data World element, from the Data World part of the SLH Administration Tasks window, click the Data World drop-down list to display the list of available Data Worlds which can be modified. Select the Data World to be modified, then select Modify to display the Modify SLH Application Data World window.\n\nThe functionality of the Modify SLH Application Data World window is identical to the Create SLH Application Data World window. Refer to Create Data World for further information.\n\n\n\nCreate Data World\nSLH Administration Tasks\nData World\nModify\nModify SLH Application Data World\nModify SLH Application Data World\nCreate SLH Application Data World\nCreate Data World"}
{"Headers": "Delete Data World", "Content": "To delete a Data World element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Defaults", "Content": "The Defaults part of the SLH Administration Tasks window allows the administrator to create and modify the Defaults available to the user. Read-only Defaults can be viewed.\nDefaults reference standards, define values for parameters and govern which profiles/parts can be used for the different SLH elements.\n\nCreating a new SLH Default displays two new elements in the Model Explorer:\nThere is no limit to the number of APPDAR and APPLDA elements that can appear in the SLH application, the administrator has the flexibility to create any number of Defaults.\nThe administrator may need to create parts and possibly catalog items before creating a Default. Refer to the Catalog and Specifications User Guide for further information.\nApplication Data Area (APPDAR)\nApplication Data Standard (APPLDA).\nApplication Data Area (APPDAR)\nApplication Data Area (APPDAR)\nApplication Data Standard (APPLDA).\nApplication Data Standard (APPLDA).\n\n\n\nDefaults\nSLH Administration Tasks\nCatalog and Specifications User Guide"}
{"Headers": "Assemblies", "Content": "The Assemblies part of the SLH Administration Tasks window allows the administrator to create and modify the Assemblies available to the user. An assembly must be added to the defaults before it is available to a user.\nThe administrator can create three different types of SLH Assembly. Each new SLH Assembly displays a new element in the Model Explorer:\n\nThere is no limit to the number of HANDRA, RLADDR and SLADDR elements that can appear in the SLH application, the administrator has the flexibility to create any number of Assemblies.\nHandrail (HANDRA)\nRung Ladder (RLADDR)\nStep Ladder (SLADDR)\nHandrail (HANDRA)\nHandrail (HANDRA)\nRung Ladder (RLADDR)\nRung Ladder (RLADDR)\nStep Ladder (SLADDR)\nStep Ladder (SLADDR)\n\n\n\nAssemblies\nSLH Administration Tasks"}
{"Headers": "Standard", "Content": "The Standards part of the SLH Administration Tasks window allows the administrator to create and modify the Standards which the defaults reference. Read-only standards can be viewed.\n\nCreating a new SLH Standard displays two new elements in the Model Explorer:\nThere is no limit to the number of APPDAR and APPLDA elements that can appear in the SLH application, the administrator has the flexibility to create any number of Standards.\nApplication Data Area (APPDAR)\nApplication Data Standard (APPLDA).\nApplication Data Area (APPDAR)\nApplication Data Area (APPDAR)\nApplication Data Standard (APPLDA).\nApplication Data Standard (APPLDA).\n\n\n\nStandards\nSLH Administration Tasks"}
{"Headers": "Create Standard Area", "Content": "To create a Standard Area element make sure the correct Data World is selected in the Data World part of the SLH Administration Tasks window.\nTo create a Standard Area element, from the Standards part of the SLH Administration Tasks window, click Create next to the Area drop-down list to display the Create SLH Area for Standards window.\n\nThe owning Data World displays at the top of the Create SLH Area for Standards window.\nName\nInput a name for the new Standard Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nName\nInput a name for the new Standard Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nClick Create to create the Standard Area element or Cancel to discard any inputs and close the Create SLH Area for Standards window.\nThe Standard Area element displays in the Model Explorer.\n\nName\nInput a name for the new Standard Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\n\n\n\nData World\nSLH Administration Tasks\nStandards\nSLH Administration Tasks\nCreate\nCreate SLH Area for Standards\nCreate SLH Area for Standards\nName\nDescription\nFunction\nCreate\nCancel\nCreate SLH Area for Standards"}
{"Headers": "Modify Standard Area", "Content": "To modify a Standard Area element, from the Standards part of the SLH Administration Tasks window, click the Area drop-down list to display the list of available Areas which can be modified. Select the Area to be modified, then select Modify, to display the Modify SLH Area for Standards window.\n\nThe functionality of the Modify SLH Area for Standards window is identical to the Create SLH Area for Standards window. Refer to Create Standard Area for further information.\n\n\n\nCreate Standard Area\nStandards\nSLH Administration Tasks\nArea\nModify\nModify SLH Area for Standards\nModify SLH Area for Standards\nCreate SLH Area for Standards\nCreate Standard Area"}
{"Headers": "Delete Standard Area", "Content": "To delete a Standard Area element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Create Standard", "Content": "To create a Standard element make sure the correct Standard Area is selected in the Standards part of the SLH Administration Tasks window.\nTo create a Standard element, from the Standards part of the SLH Administration Tasks window, click Create next to the Standards drop-down list to display the Create Standard window.\n\nNote:\nAll mandatory parts of the Create Standard window are indicated with an amber triangle. The SLH application replaces the amber triangle with a green tick when the Create Standard window has been populated with the required data.\n\n\n\nStandards\nSLH Administration\nTasks\nStandards\nSLH Administration Tasks\nCreate\nCreate Standard\nNote\n:\nCreate Standard\nCreate Standard"}
{"Headers": "General", "Content": "The General part of the Create Rung Ladder Gate Template window displays by default, the administrator can name and describe the new Rung Ladder Gate Template element.\n\nName\nInput a name for the new Rung Ladder Gate Template in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nName sub-elements\nSelect the check box for the SLH application to name new elements by default.\nHow the posts are mounted\nThe Side Mounted radio button creates a Rung Ladder Gate Template with side mounted posts and is selected by default.\nSelect the Top Mounted radio button to create a Rung Ladder Gate Template with top mounted posts.\nName\nInput a name for the new Rung Ladder Gate Template in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nName sub-elements\nSelect the check box for the SLH application to name new elements by default.\nHow the posts are mounted\nThe Side Mounted radio button creates a Rung Ladder Gate Template with side mounted posts and is selected by default.\nSelect the Top Mounted radio button to create a Rung Ladder Gate Template with top mounted posts.\nClick Next to display the Parameters part of the Create Rung Ladder Gate Template window. Refer to Rung Ladder Gate Template Parameters for further information.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nName\nInput a name for the new Rung Ladder Gate Template in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nName sub-elements\nSelect the check box for the SLH application to name new elements by default.\nHow the posts are mounted\nThe Side Mounted radio button creates a Rung Ladder Gate Template with side mounted posts and is selected by default.\nSelect the Top Mounted radio button to create a Rung Ladder Gate Template with top mounted posts.\n\n\n\nRung Ladder Gate Template Parameters\nGeneral\nCreate Rung Ladder Gate Template\nName\nDescription\nName sub-elements\nHow the posts are mounted\nSide Mounted\nTop Mounted\nNext\nParameters\nCreate Rung Ladder Gate Template\nRung Ladder Gate Template Parameters\nCancel\nSLH Administration Tasks"}
{"Headers": "Stair Flight", "Content": "The Stair Flight part of the Create Standard window allows the administrator to define the Pitch Validation Formula and Constraints for the stair flight.\n\nTo remove Stair Flights from the standard, click to clear the Included check box.\nPitch Validation Formula\nThe user is required to select the pitch validation formula. Standards define the pitch validation in different ways, the Pitch Validation Formula part of the Create Standard window has three default formulas:\nSelect the required radio button to define the pitch validation formula.\n\nConstraints\nThe administrator is required to complete the minimum and maximum values of all constraints for the stair flight. Blank values are only permitted for certain constraints.\nAcceptable values input by the administrator into the minimum or maximum cells of the Constraints list are highlighted in green.\n\nIf a value is entered and it is incorrect, an error message displays summarizing the problem.\n\nAll errors display at the bottom of the list of constraints. When there are no errors the status displays as Complete.\n\nTo visualize how the constraints equate to the stair flight, click Show diagram to display the Stair Flight Parameters window.\n\nClick Next to display the Handrail part of the Create Standard window. Refer to Handrail for further information.\nClick Back to return to the General part of the Create Standard window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n2 x Rise + Going\nRise + Going\nRise x Going\n2 x Rise + Going\n2 x Rise + Going\nRise + Going\nRise + Going\nRise x Going\nRise x Going\n\n\n\nHandrail\nStair Flight\nCreate Standard\nIncluded\nPitch Validation Formula\nPitch Validation Formula\nCreate Standard\nConstraints\nShow diagram\nStair Flight Parameters\nNext\nCreate Standard\nHandrail\nBack\nCreate Standard\nCancel\nSLH Administration Tasks"}
{"Headers": "Handrail", "Content": "The Handrail part of the Create Standard window allows the administrator to define the Constraints for the handrail.\n\nTo remove Handrails from the standard, click to clear the Included check box.\nThe administrator is required to complete the minimum and maximum values of all constraints for the handrail. Blank values are only permitted for certain constraints.\nAcceptable values input by the administrator into the minimum or maximum cells of the Constraints list are highlighted in green.\n\nIf a value is entered and it is incorrect, an error message displays summarizing the problem.\n\nAll errors display at the bottom of the list of constraints. When there are no errors the status displays as Complete.\n\nTo visualize how the constraints equate to the handrail, click Show diagram to display the Handrail Parameters window.\n\nClick Next to display the Rung Ladder part of the Create Standard window. Refer to Rung Ladder for further information.\nClick Back to return to the Stair Flight part of the Create Standard window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nRung Ladder\nHandrail\nCreate Standard\nIncluded\nShow diagram\nHandrail Parameters\nNext\nRung Ladder\nCreate Standard\nRung Ladder\nBack\nStair Flight\nCreate Standard\nCancel\nSLH Administration Tasks"}
{"Headers": "Rung Ladder", "Content": "The Rung Ladder part of the Create Standard window allows the administrator to define the Constraints for the rung ladder.\n\nTo remove the Rung Ladder element from the standard, click to clear the Included check box.\nThe administrator is required to complete the minimum and maximum values of all constraints for the rung ladder. Blank values are only permitted for certain constraints.\nAcceptable values input by the administrator into the minimum or maximum cells of the Constraints list are highlighted in green.\n\nIf a value is entered and it is incorrect, an error message displays summarizing the problem.\n\nAll errors display at the bottom of the list of constraints. When there are no errors the status displays as Complete.\n\nTo visualize how the constraints equate to the rung ladder, click Show diagram to display the Rung Ladder Parameters window.\n\nClick Next to display the Step Ladder part of the Create Standard window. Refer to Step Ladder for further information.\nClick Back to return to the Handrail part of the Create Standard window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nStep Ladder\nRung Ladder\nCreate Standard\nIncluded\nShow diagram\nRung Ladder Parameters\nNext\nStep Ladder\nCreate Standard\nStep Ladder\nBack\nHandrail\nCreate Standard\nCancel\nSLH Administration Tasks"}
{"Headers": "Step Ladder", "Content": "The Step Ladder part of the Create Standard window allows the administrator to define the Constraints for the step ladder.\n\nTo remove the Step Ladder element from the standard, click to clear the Included check box.\nThe administrator is required to complete the minimum and maximum values of all constraints for the step ladder. Blank values are only permitted for certain constraints.\nAcceptable values input by the administrator into the minimum or maximum cells of the Constraints list are highlighted in green.\n\nIf a value is entered and it is incorrect, an error message displays summarizing the problem.\n\nAll errors display at the bottom of the list of constraints. When there are no errors the status displays as Complete.\n\nTo visualise how the constraints equate to the step ladder, click Show diagram to display the Step Ladder Parameters window.\n\nClick Create to create the standard.\nClick Back to return to the Handrail part of the Create Standard window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nThe Standard element displays in the Model Explorer.\n\n\n\n\nStep Ladder\nCreate Standard\nIncluded\nShow diagram\nStep Ladder Parameters\nCreate\nBack\nHandrail\nCreate Standard\nCancel\nSLH Administration Tasks"}
{"Headers": "Modify Standard", "Content": "To modify a Standard element, from the Standards part of the SLH Administration Tasks window, click the Standards drop-down list to display the list of available Standards which can be modified. Select the Standard to be modified, then select Modify, to display the Modify Standard window.\n\nThe functionality of the Modify Standard window is identical to the Create Standard window. Refer to Create Standard for further information.\n\n\n\nCreate Standard\nStandards\nSLH Administration Tasks\nStandards\nModify\nModify Standard\nModify Standard\nCreate Standard\nCreate Standard"}
{"Headers": "Delete Standard", "Content": "To delete a Standard element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Copy Standard", "Content": "Copying an existing Standard provides a quick and efficient method of creating new standards and editing the properties in the SLH Administration Tasks window.\nTo create a new Standard element from an existing element make sure the correct Standard element is selected in the Model Explorer.\nTo copy an existing Standard element, right-click and select Copy from the drop-down list.\nTo paste a copy of the Standard element, right-click and select Paste from the drop-down list.\nTo rename the pasted Standard element, right-click and select Rename from the drop-down list to display the Name window. Refer to the Common Functionality User Guide for further information.\nThe copied element displays in the SLH Administration Tasks window.\nNote:\nIt is recommended to modify the description attribute of the standard so it can be distinguished from the original in the list of tasks.\n\n\n\nSLH Administration Tasks\nCopy\nPaste\nRename\nName\nCommon Functionality User Guide\nSLH Administration Tasks\nNote\n:"}
{"Headers": "Create Default Area", "Content": "To create a Default Area element make sure the correct Data World is selected in the Data World part of the SLH Administration Tasks window.\nTo create a Default Area element, from the Defaults part of the SLH Administration Tasks window, click Create next to the Area drop-down list to display the Create SLH Area for Defaults window.\n\nThe owning Data World displays at the top of the Create SLH Area for Defaults window.\nName\nInput a name for the new Default Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nName\nInput a name for the new Default Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nClick Create to create the Default Area element, or Cancel to discard any inputs and close the Create SLH Area for Defaults window.\nThe Default Area element displays in the Model Explorer.\n\nName\nInput a name for the new Default Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\n\n\n\nData World\nSLH Administration Tasks\nDefaults\nSLH Administration Tasks\nCreate\nCreate SLH Area for Defaults\nCreate SLH Area for Defaults\nName\nDescription\nFunction\nCreate\nCancel\nCreate SLH Area for Defaults"}
{"Headers": "Modify Default Area", "Content": "To modify a Default Area element, from the Defaults part of the SLH Administration Tasks window, click the Area drop-down list to display the list of available Areas which can be modified. Select the Area to be modified, then select Modify, to display the Modify SLH Area for Defaults window.\n\nThe functionality of the Modify SLH Area for Defaults window is identical to the Create SLH Area for Defaults window. Refer to Create Default Area for further information.\n\n\n\nCreate Default Area\nDefaults\nSLH Administration Tasks\nArea\nModify\nModify SLH Area for Defaults\nModify SLH Area for Defaults\nCreate SLH Area for Defaults\nCreate Default Area"}
{"Headers": "Delete Default Area", "Content": "To delete a Default Area element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Create Default", "Content": "To create a Default element make sure the correct Defaults Area is selected in the Defaults part of the SLH Administration Tasks window.\nTo create a Default element, from the Defaults part of the SLH Administration Tasks window, click Create next to the Defaults drop-down list to display the Create Defaults window.\n\nNote:\nAll mandatory parts of the Create Defaults window are indicated with an amber triangle. The SLH application replaces the amber triangle with a green tick when the Create Defaults window has been populated with the required data.\n\n\n\nDefaults\nSLH Administration\nTasks\nDefaults\nSLH Administration Tasks\nCreate\nCreate Defaults\nNote\n:\nCreate Defaults\nCreate Defaults"}
{"Headers": "Stair Flight Constraints", "Content": "Constraints allow the administrator to specify the standard to be used for the stair flight and the default values. SLH checks to make sure that the default values are between the minimum and maximum values specified in the standard.\n\nTo remove the Stair Flight element from the Defaults, click to clear the Included check box.\nSelect a standard from the Use min/max values from standard drop-down list to specify the standard on which the defaults are to be based.\nTo visualize how the constraints equate to the stair flight, click Show diagram to display the Stair Flight Parameters window.\n\nThe Constraints list is populated with the minimum and maximum values from the selected standard.\n\nBy default, SLH populates each cell with the minimum column of the Constraints list with a minimum standard value or the maximum column of the Constraints list with a maximum standard value. Acceptable values input by the administrator into the cell of the Constraints list are highlighted in grey.\nThe administrator can input an explicit valid value into the Valid Value cell if the cell is not highlighted with a background color.\nIf a value is entered and it is incorrect, an error message displays summarizing the problem.\n\nUse pitch formula rather than angle to calculate stair\nBy default, the stair flight is calculated from the angle, select the check box to calculate the stair flight from the pitch formula.\nAllow intermediate landing\nSelect the check box to enable the user to define an intermediate landing for the stair flight, when the maximum number of rises is exceeded.\nSelecting the Allow intermediate landing check box displays the Default Landing Thickness field.\nDefault Landing Thickness\nInput a default value for the landing thickness in the field.\nAllow cranked stringer\nONLY available when 'To plane' functionality is used.\nSelect the check box to enable the user to define a cranked stringer for the stair flight.\nExtensions\nExtensions are horizontal landings at the top and bottom of a stair flight.\nMinimum Extension - default minimum extension.\nMaximum Extension - default maximum extension.\nNosing Offset\nONLY available for selection in Detail.\nThe distance between the nose of the tread to the front edge of the stringer. This is measured from the nosing of the treads perpendicular to the front edge of the stringer.\nThe administrator can input a value into the optional field.\nAllowable Configurations\nSelect the check boxes to enable the user to define a configuration for the stair flight.\nNote:\nAt least one configuration between edges and one configuration for a plane must be selected.\nThe administrator can choose from:\nNo extensions\nBottom extension\nTop extension\nTop and bottom extension\nInitial rise without extension\nInitial rise with top extension\nTo plane with no extensions\nTo plane with top extension\nUse pitch formula rather than angle to calculate stair\nBy default, the stair flight is calculated from the angle, select the check box to calculate the stair flight from the pitch formula.\nAllow intermediate landing\nSelect the check box to enable the user to define an intermediate landing for the stair flight, when the maximum number of rises is exceeded.\nSelecting the Allow intermediate landing check box displays the Default Landing Thickness field.\nDefault Landing Thickness\nInput a default value for the landing thickness in the field.\nAllow cranked stringer\nONLY available when 'To plane' functionality is used.\nSelect the check box to enable the user to define a cranked stringer for the stair flight.\nExtensions\nExtensions are horizontal landings at the top and bottom of a stair flight.\nMinimum Extension - default minimum extension.\nMaximum Extension - default maximum extension.\nNosing Offset\nONLY available for selection in Detail.\nThe distance between the nose of the tread to the front edge of the stringer. This is measured from the nosing of the treads perpendicular to the front edge of the stringer.\nThe administrator can input a value into the optional field.\nAllowable Configurations\nSelect the check boxes to enable the user to define a configuration for the stair flight.\nThe administrator can choose from:\nClick Next to display the Detailing for Stair Flight part of the Create Defaults window. Refer to Stair Flight Detailing for further information.\nClick Back to return to the General part of the Create Defaults window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nUse pitch formula rather than angle to calculate stair\nBy default, the stair flight is calculated from the angle, select the check box to calculate the stair flight from the pitch formula.\nAllow intermediate landing\nSelect the check box to enable the user to define an intermediate landing for the stair flight, when the maximum number of rises is exceeded.\nSelecting the Allow intermediate landing check box displays the Default Landing Thickness field.\nDefault Landing Thickness\nInput a default value for the landing thickness in the field.\nAllow cranked stringer\nONLY available when 'To plane' functionality is used.\nSelect the check box to enable the user to define a cranked stringer for the stair flight.\nExtensions\nExtensions are horizontal landings at the top and bottom of a stair flight.\nMinimum Extension - default minimum extension.\nMaximum Extension - default maximum extension.\nNosing Offset\nONLY available for selection in Detail.\nThe distance between the nose of the tread to the front edge of the stringer. This is measured from the nosing of the treads perpendicular to the front edge of the stringer.\nThe administrator can input a value into the optional field.\nAllowable Configurations\nSelect the check boxes to enable the user to define a configuration for the stair flight.\nNote:\nAt least one configuration between edges and one configuration for a plane must be selected.\nThe administrator can choose from:\nNo extensions\nBottom extension\nTop extension\nTop and bottom extension\nInitial rise without extension\nInitial rise with top extension\nTo plane with no extensions\nTo plane with top extension\nNo extensions\nBottom extension\nTop extension\nTop and bottom extension\nInitial rise without extension\nInitial rise with top extension\nTo plane with no extensions\nTo plane with top extension\nNo extensions\nNo extensions\nBottom extension\nBottom extension\nTop extension\nTop extension\nTop and bottom extension\nTop and bottom extension\nInitial rise without extension\nInitial rise without extension\nInitial rise with top extension\nInitial rise with top extension\nTo plane with no extensions\nTo plane with no extensions\nTo plane with top extension\nTo plane with top extension\nNote:\nAt least one configuration between edges and one configuration for a plane must be selected.\n\n\n\nStair Flight Detailing\nIncluded\nUse min/max values from standard\nShow diagram\nStair Flight Parameters\nUse pitch formula rather than angle to calculate stair\nAllow intermediate landing\nAllow intermediate landing\nDefault Landing Thickness\nDefault Landing Thickness\nAllow cranked stringer\nExtensions\nMinimum Extension\nMaximum Extension\nNosing Offset\nAllowable Configurations\nNote\n:\nNext\nDetailing for Stair Flight\nCreate Defaults\nStair Flight Detailing\nBack\nCreate Defaults\nCancel\nSLH Administration Tasks"}
{"Headers": "Stair Flight Detailing", "Content": "The Detailing for Stair Flight part of the Create Defaults window allows the administrator to define the parts and profiles allowed for the default.\n\nTread Specification\nThe Tread Specification list allows the administrator to add or remove default tread specifications.\n\nAdd Part\nClick to display the Tread Specification window.\nRemove Selected Part\nClick to remove the currently selected tread specification from the Tread Specification list.\n\nAdd Part\nClick to display the Tread Specification window.\n\nRemove Selected Part\nClick to remove the currently selected tread specification from the Tread Specification list.\nThe Tread Specification window allows the administrator to add a tread specification to the Tread Specification list.\nFrom the Select Component part of the Tread Specification window, select the required tread from the list of available components. A graphical representation of the selected tread component is displayed in the 3D view.\nClick Apply to add the currently selected tread to the Tread Specification list, or click Cancel to discard any changes and close the Tread Specification window.\nAdd Part\nClick to display the Tread Specification window.\nRemove Selected Part\nClick to remove the currently selected tread specification from the Tread Specification list.\n\n\n\nDetailing for Stair Flight\nCreate Defaults\nTread Specification\nAdd Part\nTread Specification\nRemove Selected Part\nTread Specification\nTread Specification\nSelect Component\nTread Specification\nApply\nCancel\nTread Specification"}
{"Headers": "Stringer Specification", "Content": "The Stringer Specification list allows the administrator to add or remove stringer specifications.\n\nAdd Profile\nClick to display the Stringer Specification window.\nRemove Selected Profile\nClick to remove the currently selected stringer profile from the Stringer Specification list.\n\nAdd Profile\nClick to display the Stringer Specification window.\n\nRemove Selected Profile\nClick to remove the currently selected stringer profile from the Stringer Specification list.\nThe Stringer Specification window allows the administrator to add a stringer specification to the Stringer Specification list.\n\nStandard\nSelect a standard from the drop-down list to specify the profile standard to be used for the stair flight.\nThe selection determines the options available from the Generic Type drop-down list and the Profile Size list.\nGeneric Type\nSelect a type from the drop-down list to specify the profile type to be used for the stair flight.\nThe selection determines the options available from the Profile Size list.\nProfile Size\nSelect a profile size from the drop-down list.\nJustification Rule for P-Line\nP-Line Justification\nSelect a P-line justification value from the drop-down list.\nMember Line Justification\nSelect a member line justification value from the drop-down list.\nJoint Line Justification\nSelect a joint line justification value from the drop-down list.\nStandard\nSelect a standard from the drop-down list to specify the profile standard to be used for the stair flight.\nThe selection determines the options available from the Generic Type drop-down list and the Profile Size list.\nGeneric Type\nSelect a type from the drop-down list to specify the profile type to be used for the stair flight.\nThe selection determines the options available from the Profile Size list.\nProfile Size\nSelect a profile size from the drop-down list.\nP-Line Justification\nSelect a P-line justification value from the drop-down list.\nMember Line Justification\nSelect a member line justification value from the drop-down list.\nJoint Line Justification\nSelect a joint line justification value from the drop-down list.\nClick Apply to add the profile specification to the Stringer Specification list, or click Cancel to discard any changes and close the Stringer Specification window.\nClick Next to display the Constraints for Handrail part of the Create Defaults window. Refer to Handrail Constraints for further information.\nClick Back to return to the Constraints for Stair Flight part of the Create Defaults window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nAdd Profile\nClick to display the Stringer Specification window.\nRemove Selected Profile\nClick to remove the currently selected stringer profile from the Stringer Specification list.\nStandard\nSelect a standard from the drop-down list to specify the profile standard to be used for the stair flight.\nThe selection determines the options available from the Generic Type drop-down list and the Profile Size list.\nGeneric Type\nSelect a type from the drop-down list to specify the profile type to be used for the stair flight.\nThe selection determines the options available from the Profile Size list.\nProfile Size\nSelect a profile size from the drop-down list.\nJustification Rule for P-Line\nP-Line Justification\nSelect a P-line justification value from the drop-down list.\nMember Line Justification\nSelect a member line justification value from the drop-down list.\nJoint Line Justification\nSelect a joint line justification value from the drop-down list.\n\n\n\nHandrail Constraints\nAdd Profile\nStringer Specification\nRemove Selected Profile\nStringer Specification\nStandard\nGeneric Type\nProfile Size\nGeneric Type\nProfile Size\nProfile Size\nJustification Rule for P-Line\nP-Line Justification\n\nMember Line Justification\nJoint Line Justification\nApply\nCancel\nStringer Specification\nNext\nConstraints for Handrail\nCreate Defaults\nHandrail Constraints\nBack\nConstraints for Stair Flight\nCreate Defaults\nCancel\nSLH Administration Tasks"}
{"Headers": "Handrail Constraints", "Content": "Constraints allow the administrator to specify the standard to be used for the handrail and the default values. By default, SLH checks to make sure that the values are between the minimum and maximum values specified in the standard.\n\nTo remove Handrail from the Defaults, click to clear the Included check box.\nThe functionality available from the Constraints for Handrail part of the Create Defaults window is identical to that available from the Constraints for Stair Flight part of the Create Defaults window, with the exception of the Allow trace boundary check box. Refer to Stair Flight Constraints for further information.\nSelect the Allow trace boundary check box to allow the user to trace the boundary (Copy Route Path) of an extrusion element such as a platform when creating a handrail. By default, the check box is not selected.\nClick Next to display the Detailing for Handrail part of the Create Defaults window. Refer to Handrail Detailing for further information.\nClick Back to return to the Detailing for Stair Flight part of the Create Defaults window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nStair Flight Constraints\nHandrail Detailing\nIncluded\nConstraints for Handrail\nCreate Defaults\nConstraints for Stair Flight\nCreate Defaults\nAllow trace boundary\nStair Flight Constraints\nAllow trace boundary\nCopy Route Path\nNext\nDetailing for Handrail\nCreate Defaults\nHandrail Detailing\nBack\nCreate Defaults\nCancel\nSLH Administration Tasks"}
{"Headers": "Handrail Detailing", "Content": "The Detailing for Handrail part of the Create Defaults window is populated with the assembly items in the database. The functionality available allows the administrator to define the assemblies, parts and profiles allowed for the default.\n\nThe administrator must select at least one handrail assembly for the handrail defaults. The selection determines which assemblies are available to the user.\nInclude new assemblies automatically\nSelect the check box to include newly created assemblies in the list of available assemblies.\nBy default, the check box is not selected.\nInclude All\nClick to include all assemblies from the database in the list of available assemblies.\nExclude All\nClick to exclude all assemblies from the database in the list of available assemblies.\nDisplay\nClick to display the Select Assembly window.\nInclude new assemblies automatically\nSelect the check box to include newly created assemblies in the list of available assemblies.\nBy default, the check box is not selected.\nInclude All\nClick to include all assemblies from the database in the list of available assemblies.\nExclude All\nClick to exclude all assemblies from the database in the list of available assemblies.\nDisplay\nClick to display the Select Assembly window.\nThe Select Assembly window allows the administrator to add an assembly to the list of available assemblies.\n\nSelect the required assembly from the Select Assembly list. A 3D graphical representation of selected assembly is also displayed.\nClick Select to add the currently selected assembly to the list of available assemblies, or click Cancel to close the Select Assembly window.\n\nTo include an assembly in the list of available assemblies that has not been previously included, select the check box in the included column adjacent to the assembly.\nInclude new assemblies automatically\nSelect the check box to include newly created assemblies in the list of available assemblies.\nBy default, the check box is not selected.\nInclude All\nClick to include all assemblies from the database in the list of available assemblies.\nExclude All\nClick to exclude all assemblies from the database in the list of available assemblies.\nDisplay\nClick to display the Select Assembly window.\n\n\n\nDetailing for Handrail\nCreate Defaults\nInclude new assemblies automatically\nInclude All\nExclude All\nDisplay\nSelect Assembly\nSelect Assembly\nSelect\nCancel\nSelect Assembly"}
{"Headers": "Handrail Part", "Content": "Component parts of the handrail can be added and removed from the list of available parts.\nAll of the functionality for the addition and removal of Gate Parts, Termination Parts, Post Parts and Panel Parts is identical, therefore for the purposes of this administrator guide, only a Gate part is added.\nFrom the Detailing for Handrail part of the Create Defaults window, select the Gates tab to display the Gate Part list.\n\nAdd Part\nClick to display the Gate Part window.\nRemove\nSelected Part\nClick to remove the currently selected part from the Gate Part list.\n\nAdd Part\nClick to display the Gate Part window.\n\nRemove\nSelected Part\nClick to remove the currently selected part from the Gate Part list.\nThe Gate Part window allows the administrator to add a gate to the list of available parts.\n\nSelect the required gate from the list of available components. A 3D graphical representation of selected gate is displayed.\nClick Apply to add the currently selected part to the Gate Part list, or click Cancel to discard any changes and close the Gate Part window.\nAdd Part\nClick to display the Gate Part window.\nRemove\nSelected Part\nClick to remove the currently selected part from the Gate Part list.\n\n\n\nDetailing for Handrail\nCreate Defaults\nGates\nAdd Part\nGate Part\nRemove\nSelected Part\nGate Part\nApply\nCancel\nGate Part"}
{"Headers": "Handrail Profile Specification", "Content": "Profile Specifications can be added and removed from the list of available defaults.\nAll of the functionality for the addition and removal of Top Rail Specifications, Intermediate Rail Specifications, and Kickplate Specifications is identical, therefore for the purposes of this administrator guide, only a Top Rail Specification is added.\nFrom the Detailing for Handrail part of the Create Defaults window, select the Top Rail tab to display the Top Rail Specification list.\n\nAdd Profile\nSpecification\nClick to display the Top Rail Specification window.\nRemove Selected\nProfile Specification\nClick to remove the currently selected profile from the Top Rail list.\n\nAdd Profile\nSpecification\nClick to display the Top Rail Specification window.\n\nRemove Selected\nProfile Specification\nClick to remove the currently selected profile from the Top Rail list.\n\nAdd Profile\nSpecification\nClick to display the Top Rail Specification window.\nRemove Selected\nProfile Specification\nClick to remove the currently selected profile from the Top Rail list.\n\n\n\nDetailing for Handrail\nCreate Defaults\nTop Rail\nAdd Profile\nSpecification\nTop Rail Specification\nRemove Selected\nProfile Specification"}
{"Headers": "Top Rail Specification", "Content": "The Top Rail Specification window allows the administrator to add a profile specification to the Top Rail Specification list.\n\nStandard\nSelect a standard from the drop-down list to specify the profile standard to be used for the handrail.\nThe selection determines the options available from the Generic Type drop-down list and the Profile Size list.\nGeneric Type\nSelect a type from the drop-down list to specify the profile type to be used for the handrail.\nThe selection determines the options available from the Profile Size list.\nProfile Size\nSelect a profile size from the drop-down list.\nJustification Rule for P-Line\nP-Line Justification\nSelect a P-line justification value from the drop-down list.\nMember Line Justification\nSelect a member line justification value from the drop-down list.\nJoint Line Justification\nSelect a joint line justification value from the drop-down list.\nStandard\nSelect a standard from the drop-down list to specify the profile standard to be used for the handrail.\nThe selection determines the options available from the Generic Type drop-down list and the Profile Size list.\nGeneric Type\nSelect a type from the drop-down list to specify the profile type to be used for the handrail.\nThe selection determines the options available from the Profile Size list.\nProfile Size\nSelect a profile size from the drop-down list.\nJustification Rule for P-Line\nP-Line Justification\nSelect a P-line justification value from the drop-down list.\nMember Line Justification\nSelect a member line justification value from the drop-down list.\nJoint Line Justification\nSelect a joint line justification value from the drop-down list.\nClick Apply to add the profile specification to the Top Rail Specification list, or click Cancel to discard any changes and close the Top Rail Specification window.\nClick Next to display the Constraints for Rung Ladder part of the Create Defaults window. Refer to Rung Ladder Constraints for further information.\nClick Back to return to the Constraints for Handrail part of the Create Defaults window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nStandard\nSelect a standard from the drop-down list to specify the profile standard to be used for the handrail.\nThe selection determines the options available from the Generic Type drop-down list and the Profile Size list.\nGeneric Type\nSelect a type from the drop-down list to specify the profile type to be used for the handrail.\nThe selection determines the options available from the Profile Size list.\nProfile Size\nSelect a profile size from the drop-down list.\nJustification Rule for P-Line\nP-Line Justification\nSelect a P-line justification value from the drop-down list.\nMember Line Justification\nSelect a member line justification value from the drop-down list.\nJoint Line Justification\nSelect a joint line justification value from the drop-down list.\n\n\n\nRung Ladder Constraints\nTop Rail Specification\nStandard\nGeneric Type\nProfile Size\nGeneric Type\nProfile Size\nProfile Size\nJustification Rule for P-Line\nP-Line Justification\nMember Line Justification\nJoint Line Justification\nApply\nCancel\nTop Rail Specification\nNext\nConstraints for Rung Ladder\nCreate Defaults\nRung Ladder Constraints\nBack\nConstraints for Handrail\nCreate Defaults\nCancel\nSLH Administration Tasks"}
{"Headers": "Rung Ladder Constraints", "Content": "Constraints allow the administrator to specify the standard to be used for the rung ladder and the default values. By default, SLH checks to make sure that the default values are between the minimum and maximum values specified in the standard.\n\nTo remove Rung Ladders from the Defaults, click to clear the Included check box.\nThe functionality available from the Constraints for Rung Ladder part of the Create Defaults window is identical to that available from the Constraints for Stair Flight part of the Create Defaults window. Refer to Stair Flight Constraints for further information.\nThe Cage part of the Create Defaults window allows the administrator to define the defaults and specify the allowable configurations for the rung ladder cage.\n\nAllow cage omission\nSelect the check box to allow the user to omit the cage completely when creating a rung ladder.\nOmit cage by default\nSelect the check box to omit the cage by default.\nFlared cages in\nlayout mode\nSelect a cage type from the drop-down list to define the type of flared cage used:\nNone - the cage is not flared.\nConcentric - the cage has a concentric flare at the bottom of the cage.\nEccentric - the cage has an eccentric flare at bottom of cage.\nFlared cage offset\nInput a value in the field to define the flare for rung ladder cage assemblies with a flared cage.\nExit hoop extension\nInput a value in the field to define the distance that the exit cage hoop bars extend into the platform beyond the picked edge. The distance is measured from the picked edge to the end of the bars.\nThe value coupled with the Top Exit Distance gives the total length of the exit hoop bars.\nTop hoop offset\nInput a value in the field to define the distance that the top tube cage hoop is offset from the top rung (or Upper Work Point) and measured from the bottom of the hoop.\nSide exit cage clearance\nInput a value in the field to define the distance between the cage and the picked edge.\nThe ladder origin is therefore positioned at this value plus half the cage width.\nCage exit width\n(front exit)\nInput a value in the field to define the cage exit width for a front exit rung ladder.\nAllow cage omission\nSelect the check box to allow the user to omit the cage completely when creating a rung ladder.\nOmit cage by default\nSelect the check box to omit the cage by default.\nFlared cages in\nlayout mode\nSelect a cage type from the drop-down list to define the type of flared cage used:\nFlared cage offset\nInput a value in the field to define the flare for rung ladder cage assemblies with a flared cage.\nExit hoop extension\nInput a value in the field to define the distance that the exit cage hoop bars extend into the platform beyond the picked edge. The distance is measured from the picked edge to the end of the bars.\nThe value coupled with the Top Exit Distance gives the total length of the exit hoop bars.\nTop hoop offset\nInput a value in the field to define the distance that the top tube cage hoop is offset from the top rung (or Upper Work Point) and measured from the bottom of the hoop.\nSide exit cage clearance\nInput a value in the field to define the distance between the cage and the picked edge.\nThe ladder origin is therefore positioned at this value plus half the cage width.\nCage exit width\n(front exit)\nInput a value in the field to define the cage exit width for a front exit rung ladder.\nThe Top part of the Create Defaults window allows the administrator to define the defaults for the top of the rung ladder.\n\nAllow top rung omission\nSelect the check box to allow the user to omit the top rung of the ladder when creating a rung ladder.\nNot selected means the top rung is level with FFL.\nThe Omit check box and the Curtail distance field is displayed.\nOmit\nSelect the check box to omit the top rung of the ladder by default when creating a ladder.\nCurtail distance\nInput a value in the field to define the distance the stiles are extended above the top rung.\nAllow top rung omission\nSelect the check box to allow the user to omit the top rung of the ladder when creating a rung ladder.\nNot selected means the top rung is level with FFL.\nThe Omit check box and the Curtail distance field is displayed.\nOmit\nSelect the check box to omit the top rung of the ladder by default when creating a ladder.\nCurtail distance\nInput a value in the field to define the distance the stiles are extended above the top rung.\nThe Bottom part of the Create Defaults window allows the administrator to define the defaults for the bottom of the rung ladder.\n\nAlways truncate\nSelect the check box to truncate the stiles at the bottom of the rung ladder by default, if the check box is not selected the user has the option to truncate or not.\nTruncate stile after bottom rung\nSelect the radio button to allow the user to truncate stiles below the bottom rung, the Curtail distance field is displayed.\nCurtail distance\nInput a value in the field to define the distance to truncate the stiles below the bottom rung.\nUse clearance from bottom\nSelect the radio button to allow the user to truncate stiles from the finished floor level, the Clearance from FFL field is displayed.\nClearance from FFL\nInput a value in the field to define the distance to truncate the stiles the stated distance from the finished floor level.\nAlways truncate\nSelect the check box to truncate the stiles at the bottom of the rung ladder by default, if the check box is not selected the user has the option to truncate or not.\nTruncate stile after bottom rung\nSelect the radio button to allow the user to truncate stiles below the bottom rung, the Curtail distance field is displayed.\nCurtail distance\nInput a value in the field to define the distance to truncate the stiles below the bottom rung.\nUse clearance from bottom\nSelect the radio button to allow the user to truncate stiles from the finished floor level, the Clearance from FFL field is displayed.\nClearance from FFL\nInput a value in the field to define the distance to truncate the stiles the stated distance from the finished floor level.\nClick Next to display the Detailing for Rung Ladder part of the Create Defaults window. Refer to Rung Ladder Detailing for further information.\nClick Back to return to the Detailing for Handrail part of the Create Defaults window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nAllow cage omission\nSelect the check box to allow the user to omit the cage completely when creating a rung ladder.\nOmit cage by default\nSelect the check box to omit the cage by default.\nFlared cages in\nlayout mode\nSelect a cage type from the drop-down list to define the type of flared cage used:\nNone - the cage is not flared.\nConcentric - the cage has a concentric flare at the bottom of the cage.\nEccentric - the cage has an eccentric flare at bottom of cage.\nFlared cage offset\nInput a value in the field to define the flare for rung ladder cage assemblies with a flared cage.\nExit hoop extension\nInput a value in the field to define the distance that the exit cage hoop bars extend into the platform beyond the picked edge. The distance is measured from the picked edge to the end of the bars.\nThe value coupled with the Top Exit Distance gives the total length of the exit hoop bars.\nTop hoop offset\nInput a value in the field to define the distance that the top tube cage hoop is offset from the top rung (or Upper Work Point) and measured from the bottom of the hoop.\nSide exit cage clearance\nInput a value in the field to define the distance between the cage and the picked edge.\nThe ladder origin is therefore positioned at this value plus half the cage width.\nCage exit width\n(front exit)\nInput a value in the field to define the cage exit width for a front exit rung ladder.\nAllow top rung omission\nSelect the check box to allow the user to omit the top rung of the ladder when creating a rung ladder.\nNot selected means the top rung is level with FFL.\nThe Omit check box and the Curtail distance field is displayed.\nOmit\nSelect the check box to omit the top rung of the ladder by default when creating a ladder.\nCurtail distance\nInput a value in the field to define the distance the stiles are extended above the top rung.\nAlways truncate\nSelect the check box to truncate the stiles at the bottom of the rung ladder by default, if the check box is not selected the user has the option to truncate or not.\nTruncate stile after bottom rung\nSelect the radio button to allow the user to truncate stiles below the bottom rung, the Curtail distance field is displayed.\nCurtail distance\nInput a value in the field to define the distance to truncate the stiles below the bottom rung.\nUse clearance from bottom\nSelect the radio button to allow the user to truncate stiles from the finished floor level, the Clearance from FFL field is displayed.\nClearance from FFL\nInput a value in the field to define the distance to truncate the stiles the stated distance from the finished floor level.\nNone - the cage is not flared.\nConcentric - the cage has a concentric flare at the bottom of the cage.\nEccentric - the cage has an eccentric flare at bottom of cage.\nNone - the cage is not flared.\nNone - the cage is not flared.\nConcentric - the cage has a concentric flare at the bottom of the cage.\nConcentric - the cage has a concentric flare at the bottom of the cage.\nEccentric - the cage has an eccentric flare at bottom of cage.\nEccentric - the cage has an eccentric flare at bottom of cage.\n\n\n\nStair Flight Constraints\nRung Ladder Detailing\nIncluded\nConstraints for Rung Ladder\nCreate Defaults\nConstraints for Stair Flight\nCreate Defaults\nStair Flight Constraints\nCage\nCreate Defaults\nAllow cage omission\nOmit cage by default\nFlared cages in\nlayout mode\nFlared cage offset\nExit hoop extension\nTop hoop offset\nSide exit cage clearance\nCage exit width\n(front exit)\nTop\nCreate Defaults\nAllow top rung omission\nOmit\nCurtail distance\nOmit\nCurtail distance\nBottom\nCreate Defaults\nAlways truncate\nTruncate stile after bottom rung\nCurtail distance\nCurtail distance\nUse clearance from bottom\nClearance from FFL\nClearance from FFL\nNext\nDetailing for Rung Ladder\nCreate Defaults\nRung Ladder Detailing\nBack\nDetailing for Handrail\nCreate Defaults\nCancel\nSLH Administration Tasks"}
{"Headers": "Rung Ladder Detailing", "Content": "The Detailing for Rung Ladder part of the Create Defaults window allows the administrator to define the assemblies, parts and profiles allowed for the default.\n\nThe administrator must select at least one rung ladder assembly for the rung ladder defaults. The selection determines which assemblies are available to the User for selection.\nThe functionality available from the Detailing for Rung Ladder part of the Create Defaults window is identical to that available from the Detailing for Handrail part of the Create Defaults window. Refer to Handrail Detailing for further information.\n\n\n\nHandrail Detailing\nCreate Defaults\nDetailing for Rung Ladder\nCreate Defaults\nDetailing for Handrail\nCreate Defaults\nHandrail Detailing"}
{"Headers": "Rung Ladder Range Limits, Specifications and Parts", "Content": "The bottom of the Detailing for Rung Ladder part of the Create Defaults window allows the administrator to define the range limits, specifications and parts for the rung ladder assembly.\n\n\n\n\nDetailing for Rung Ladder\nCreate Defaults"}
{"Headers": "Rung Ladder Range Limit", "Content": "Range Limits for the rung ladder can be added and removed from the list of defaults.\nAll of the functionality for the addition and removal of range limits for Rungs and Stiles is identical, therefore for the purposes of this administrator guide, only a Rung range limit is added.\nFrom the Detailing for Rung Ladder part of the Create Defaults window, select the Rungs tab to display the Width between stiles range list.\n\nRange Limit\nInput a value in the field to define the width between stiles range for the ladder rungs, the default value is All.\nAdd Range Limit\nClick to add a range limit to the Width between stiles range list.\nRemove Selected Range\nClick to remove a range limit from the Width between stiles range list.\nRange Limit\nInput a value in the field to define the width between stiles range for the ladder rungs, the default value is All.\n\nAdd Range Limit\nClick to add a range limit to the Width between stiles range list.\n\nRemove Selected Range\nClick to remove a range limit from the Width between stiles range list.\n\nRange Limit\nInput a value in the field to define the width between stiles range for the ladder rungs, the default value is All.\nAdd Range Limit\nClick to add a range limit to the Width between stiles range list.\nRemove Selected Range\nClick to remove a range limit from the Width between stiles range list.\n\n\n\nDetailing for Rung Ladder\nCreate Defaults\nRungs\nRange Limit\nAdd Range Limit\nRemove Selected Range"}
{"Headers": "Rung Ladder Profile Specification", "Content": "Profile Specifications can be added and removed from the list of defaults. The available Profile Specifications are determined by Range Limit values. Refer to Rung Ladder Range Limit for further information.\nFrom the Detailing for Rung Ladder part of the Create Defaults window, select the Rungs tab to display the Rungs Specification list.\n\nAll of the functionality for the addition and removal of Rung Specifications, Stringer Specifications, Cage Hoop Specifications and Cage Bar Specifications is identical to that available from the Detailing for Handrail part of the Create Defaults window. Refer to Handrail Profile Specification for further information.\n\n\n\nRung Ladder Range Limit\nHandrail Profile Specification\nRung Ladder Range Limit\nDetailing for Rung Ladder\nCreate Defaults\nRungs\nDetailing for Handrail\nCreate Defaults\nHandrail Profile Specification"}
{"Headers": "Rung Ladder Part", "Content": "Parts of the rung ladder can be added and removed from the list of defaults. The available Parts are determined by Range Limit values. Refer to Rung Ladder Range Limit for further information.\nFrom the Detailing for Rung Ladder part of the Create Defaults window, select the Rungs tab to display the Rungs Part list.\n\nAll of the functionality for the addition and removal of Rung Parts, and Gate Parts is identical to that available from the Detailing for Handrail part of the Create Defaults window. Refer to Handrail Part for further information.\nClick Next to display the Constraints for Step Ladder part of the Create Defaults window. Refer to Step Ladder Constraints for further information.\nClick Back to return to the Constraints for Rung Ladder part of the Create Defaults window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nRung Ladder Range Limit\nHandrail Part\nStep Ladder Constraints\nRung Ladder Range Limit\nDetailing for Rung Ladder\nCreate Defaults\nRungs\nDetailing for Handrail\nCreate Defaults\nHandrail Part\nNext\nConstraints for Step Ladder\nCreate Defaults\nStep Ladder Constraints\nBack\nConstraints for Rung Ladder\nCreate Defaults\nCancel\nSLH Administration Tasks"}
{"Headers": "Step Ladder Constraints", "Content": "Constraints allow the administrator to specify the standard to be used for the step ladder and the default values. By default, SLH checks to make sure that the default values are between the minimum and maximum values specified in the standard.\n\nThe functionality available from the Constraints for Step Ladder part of the Create Defaults window is identical to that available from the Constraints for Stair Flight part of the Create Defaults window. Refer to Stair Flight Constraints for further information.\nThe Step Ladder part of the Create Defaults window allows the administrator to define the defaults for the step ladder.\n\nTop Extension Min\nInput a value in the field to define the minimum top extension distance.\nTop Extension Max\nInput a value in the field to define the maximum top extension distance.\nNosing Offset\nInput a value in the field to define the distance between the nose of the tread to the front edge of the stringer. This is measured from the nosing of the treads perpendicular to the front edge of the stringer.\nTop Stringer Gap\nInput a value in the field to define the distance for the stringer gap from the selected edge at the top of the step ladder.\nBott Stringer Gap\nInput a value in the field to define the distance for the stringer gap from the selected edge at the bottom of the step ladder.\nStringer Snipe\nInput a value in the field to define the distance for the stringer snipe.\nTop Extension Min\nInput a value in the field to define the minimum top extension distance.\nTop Extension Max\nInput a value in the field to define the maximum top extension distance.\nNosing Offset\nInput a value in the field to define the distance between the nose of the tread to the front edge of the stringer. This is measured from the nosing of the treads perpendicular to the front edge of the stringer.\nTop Stringer Gap\nInput a value in the field to define the distance for the stringer gap from the selected edge at the top of the step ladder.\nBott Stringer Gap\nInput a value in the field to define the distance for the stringer gap from the selected edge at the bottom of the step ladder.\nStringer Snipe\nInput a value in the field to define the distance for the stringer snipe.\nThe Handrail part of the Create Defaults window allows the administrator to define the defaults for the handrail.\n\nTop Post Offset\nInput a value in the field to define the distance from the top of the step ladder to the top post.\nMax Post spacing\nInput a value in the field to define the maximum distance between the posts.\nPost extension\nInput a value in the field to define the post extension distance.\nBend radius\nInput a value in the field to define the bend radius for the exit handrails.\nMinimum Exit Height\nInput a value in the field to define the minimum height for the exit handrails.\nExit Extension\nInput a value in the field to define exit handrail extension distance from the edge of the step ladder.\nTop Post Offset\nInput a value in the field to define the distance from the top of the step ladder to the top post.\nMax Post spacing\nInput a value in the field to define the maximum distance between the posts.\nPost extension\nInput a value in the field to define the post extension distance.\nBend radius\nInput a value in the field to define the bend radius for the exit handrails.\nMinimum Exit Height\nInput a value in the field to define the minimum height for the exit handrails.\nExit Extension\nInput a value in the field to define exit handrail extension distance from the edge of the step ladder.\nAllowable Configurations\nThe Allowable configurations part of the Create Defaults window allows the administrator to define the available configurations for the step ladder.\n\nThe administrator can choose from:\nUse Top\nStringer Gap\nSelect the check box to allow a top stringer gap for to plane with no extensions and no extensions step ladders.\nUse Bottom\nStringer Gap\nSelect the check box to allow a bottom stringer gap for top extension and no extensions step ladders.\nUse Top\nStringer Gap\nSelect the check box to allow a top stringer gap for to plane with no extensions and no extensions step ladders.\nUse Bottom\nStringer Gap\nSelect the check box to allow a bottom stringer gap for top extension and no extensions step ladders.\nClick Next to display the Detailing for Step Ladder part of the Create Defaults window. Refer to Step Ladder Detailing for further information.\nClick Back to return to the Detailing for Rung Ladder part of the Create Defaults window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nTop Extension Min\nInput a value in the field to define the minimum top extension distance.\nTop Extension Max\nInput a value in the field to define the maximum top extension distance.\nNosing Offset\nInput a value in the field to define the distance between the nose of the tread to the front edge of the stringer. This is measured from the nosing of the treads perpendicular to the front edge of the stringer.\nTop Stringer Gap\nInput a value in the field to define the distance for the stringer gap from the selected edge at the top of the step ladder.\nBott Stringer Gap\nInput a value in the field to define the distance for the stringer gap from the selected edge at the bottom of the step ladder.\nStringer Snipe\nInput a value in the field to define the distance for the stringer snipe.\nTop Post Offset\nInput a value in the field to define the distance from the top of the step ladder to the top post.\nMax Post spacing\nInput a value in the field to define the maximum distance between the posts.\nPost extension\nInput a value in the field to define the post extension distance.\nBend radius\nInput a value in the field to define the bend radius for the exit handrails.\nMinimum Exit Height\nInput a value in the field to define the minimum height for the exit handrails.\nExit Extension\nInput a value in the field to define exit handrail extension distance from the edge of the step ladder.\nUse Top\nStringer Gap\nSelect the check box to allow a top stringer gap for to plane with no extensions and no extensions step ladders.\nUse Bottom\nStringer Gap\nSelect the check box to allow a bottom stringer gap for top extension and no extensions step ladders.\nTo plane with top extension\nTo plane with no extensions\nTop extension\nNo extensions\nTo plane with top extension\nTo plane with top extension\nTo plane with no extensions\nTo plane with no extensions\nTop extension\nTop extension\nNo extensions\nNo extensions\n\n\n\nStair Flight Constraints\nStep Ladder Detailing\nConstraints for Step Ladder\nCreate Defaults\nConstraints for Stair Flight\nCreate Defaults\nStair Flight Constraints\nStep Ladder\nCreate Defaults\nTop Extension Min\nTop Extension Max\nNosing Offset\nTop Stringer Gap\nBott Stringer Gap\nStringer Snipe\nHandrail\nCreate Defaults\nTop Post Offset\nMax Post spacing\nPost extension\nBend radius\nMinimum Exit Height\nExit Extension\nAllowable Configurations\nCreate Defaults\nUse Top\nStringer Gap\nto plane with no extensions\nno extensions\nUse Bottom\nStringer Gap\ntop extension\nno extensions\nNext\nDetailing for Step Ladder\nCreate Defaults\nStep Ladder Detailing\nBack\nDetailing for Rung Ladder\nCreate Defaults\nCancel\nSLH Administration Tasks"}
{"Headers": "Step Ladder Detailing", "Content": "The Detailing for Step Ladder part of the Create Defaults window allows the administrator to define the assemblies and profile specifications allowed for the default.\n\nThe administrator must select at least one step ladder assembly for the step ladder defaults. The selection determines which assemblies are available to the user for selection.\nThe functionality available from the Detailing for Step Ladder part of the Create Defaults window is identical to that available from the Detailing for Handrail part of the Create Defaults window. Refer to Handrail Detailing for further information.\n\n\n\nHandrail Detailing\nDetailing for Step Ladder\nCreate Defaults\nDetailing for Step Ladder\nCreate Defaults\nDetailing for Handrail\nCreate Defaults\nHandrail Detailing"}
{"Headers": "Step Ladder Profile Specification", "Content": "Profile Specifications can be added and removed from the list of available defaults.\nAll of the functionality for the addition and removal of Tread Specifications, Stringer Specifications, Handrail Specifications and Post Specifications is identical, therefore for the purposes of this administrator guide, only a Tread Specification is added.\nFrom the Detailing for Step Ladder part of the Create Defaults window, select the Treads tab to display the Tread Specification list.\n\nAdd Profile Specification\nClick to display the Tread Specification window.\nRemove Selected Profile Specification\nClick to remove the currently selected profile from the Tread Specification list.\n\nAdd Profile Specification\nClick to display the Tread Specification window.\n\nRemove Selected Profile Specification\nClick to remove the currently selected profile from the Tread Specification list.\nThe Tread Specification window allows the administrator to add a profile specification to the Tread Specification list.\n\nSelect the required tread from the list of available components. A 3D graphical representation of the selected tread is displayed.\nClick Apply to add the profile specification to the Tread Specification list, or click Cancel to discard any changes and close the Tread Specification window.\nClick Create to create the defaults.\nClick Back to return to the Constraints for Step Ladder part of the Create Defaults window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nSelect the Make available to users check box to allow the user to access the default.\nThe Default element displays in the Model Explorer.\n\nAdd Profile Specification\nClick to display the Tread Specification window.\nRemove Selected Profile Specification\nClick to remove the currently selected profile from the Tread Specification list.\nNote:\nOnce the defaults have been made available to users, it is not possible to make them unavailable.\n\n\n\nDetailing for Step Ladder\nCreate Defaults\nTreads\nAdd Profile Specification\nTread Specification\nRemove Selected Profile Specification\nTread Specification\nApply\nCancel\nTread Specification\nCreate\nBack\nConstraints for Step Ladder\nCreate Defaults\nCancel\nSLH Administration Tasks\nMake available to users\nNote\n:"}
{"Headers": "Modify Default", "Content": "To modify a Default element, from the Defaults part of the SLH Administration Tasks window, click the Defaults drop-down list to display the list of available Defaults which can be modified. Select the Default to be modified, then select Modify, to display the Modify Defaults window.\n\nThe functionality of the Modify Defaults window is identical to the Create Defaults window. Refer to Create Default for further information.\n\n\n\nCreate Default\nDefaults\nSLH Administration Tasks\nDefaults\nModify\nModify Defaults\nModify Defaults\nCreate Defaults\nCreate Default"}
{"Headers": "Delete Default", "Content": "To delete a Default element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Copy Default", "Content": "Copying an existing default provides a quick and efficient method of creating new defaults and editing the properties in the SLH Administration Tasks window.\nTo create a new Default element from an existing element make sure the correct Default element is selected in the Model Explorer.\nTo copy an existing Default element, right-click and select Copy from the drop-down list.\nTo paste a copy of the Default element, right-click and select Paste from the drop-down list.\nTo rename the pasted Default element, right-click and select Rename from the drop-down list to display the Name window. Refer to Common Functionality User Guide for further information.\nThe copied element displays in the SLH Administration Tasks window.\n\n\n\nSLH Administration Tasks\nCopy\nPaste\nRename\nName\nCommon Functionality User Guide\nSLH Administration Tasks"}
{"Headers": "Assembly Hierarchy Elements", "Content": "A number of hierarchy elements require creation from the Application Data World before the administrator can create the Assembly elements:\n\nSLH Assembly Area (APPDAR)\nSLH Assembly Element (APPLDA)\nSLH Assembly Zone (ZONE)\nSLH Application Data (STRU).\nSLH Assembly Area (APPDAR)\nSLH Assembly Area (APPDAR)\nSLH Assembly Element (APPLDA)\nSLH Assembly Element (APPLDA)\nSLH Assembly Zone (ZONE)\nSLH Assembly Zone (ZONE)\nSLH Application Data (STRU).\nSLH Application Data (STRU).\n\n\n"}
{"Headers": "Create Assembly Area", "Content": "To create an Assembly Area element make sure the correct Data World is selected in the Data World part of the SLH Administration Tasks window.\nTo create an Assembly Area element, from the Assemblies part of the SLH Administration Tasks window, click Create next to the Area drop-down list to display the Create SLH Area for Assemblies window.\n\nThe owning Data World displays at the top of the Create SLH Area for Assemblies window.\nName\nInput a name for the new Assembly Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nName\nInput a name for the new Assembly Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nClick Create to create the Assembly Area element, or Cancel to discard any inputs and close the Create SLH Area for Assemblies window.\nThe Assembly Area element displays in the Model Explorer.\n\nName\nInput a name for the new Assembly Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\n\n\n\nData World\nSLH Administration Tasks\nAssemblies\nSLH Administration Tasks\nCreate\nCreate SLH Area for Assemblies\nCreate SLH Area for Assemblies\nName\nDescription\nFunction\nCreate\nCancel\nCreate SLH Area for Assemblies"}
{"Headers": "Modify Assembly Area", "Content": "To modify an Assembly Area element, from the Assemblies part of the SLH Administration Tasks window, click the Area drop-down list to display the list of available Areas which can be modified. Select the Area to be modified, then select Modify to display the Modify SLH Area for Defaults window.\n\nThe functionality of the Modify SLH Area for Assemblies window is identical to the Create SLH Area for Assemblies window. Refer to Create Assembly Area for further information.\n\n\n\nCreate Assembly Area\nAssemblies\nSLH Administration Tasks\nArea\nModify\nModify SLH Area for Defaults\nModify SLH Area for Assemblies\nCreate SLH Area for Assemblies\nCreate Assembly Area"}
{"Headers": "Delete Assembly Area", "Content": "To delete an Assembly Area, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Create Assembly Element", "Content": "To create an Assembly Element make sure the correct Assembly Area is selected in the Assemblies part of the SLH Administration Tasks window.\nTo create an Assembly Element, from the Assemblies part of the SLH Administration Tasks window, click Create next to the Element drop-down list to display the Create SLH Application Data window.\n\nThe owning Assembly Area displays at the top of the Create SLH Application Data window.\nName\nInput a name for the new Assembly Element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nName\nInput a name for the new Assembly Element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nClick Create to create the Assembly Element, or Cancel to discard any inputs and close the Create SLH Application Data window.\nThe Assembly Element displays in the Model Explorer.\n\nName\nInput a name for the new Assembly Element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\n\n\n\nAssemblies\nSLH Administration Tasks\nAssemblies\nSLH Administration Tasks\nCreate\nCreate SLH Application Data\nCreate SLH Application Data\nName\nDescription\nFunction\nCreate\nCancel\nCreate SLH Application Data"}
{"Headers": "Modify Assembly Element", "Content": "To modify an Assembly Element, from the Assemblies part of the SLH Administration Tasks window, click the Element drop-down list to display the list of available Elements which can be modified. Select the Element to be modified, then select Modify to display the Modify SLH Application Data window.\n\nThe functionality of the Modify SLH Application Data window is identical to the Create SLH Application Data window. Refer to Create Assembly Element for further information.\n\n\n\nCreate Assembly Element\nSLH Administration Tasks\nElement\nModify\nModify SLH Application Data\nModify SLH Application Data\nCreate SLH Application Data\nCreate Assembly Element"}
{"Headers": "Delete Assembly Element", "Content": "To delete an Assembly Element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Create Zone Element", "Content": "To create a Zone element make sure the correct Assembly Element is selected in the Assemblies part of the SLH Administration Tasks window.\nTo create a Zone element, from the Assemblies part of the SLH Administration Tasks window, click Create next to the Zone drop-down list to display the Create SLH Assembly Zone window.\n\nThe owning Assembly element displays at the top of the Create SLH Assembly Zone window.\nName\nInput a name for the new Zone element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nName\nInput a name for the new Zone element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nClick Create to create the Zone element, or Cancel to discard any inputs and close the Create SLH Assembly Zone window.\nThe Zone element displays in the Model Explorer.\n\nName\nInput a name for the new Zone element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\n\n\n\nAssemblies\nSLH Administration Tasks\nAssemblies\nSLH Administration Tasks\nCreate\nCreate SLH Assembly Zone\nCreate SLH Assembly Zone\nName\nDescription\nFunction\nCreate\nCancel\nCreate SLH Assembly Zone"}
{"Headers": "Modify Zone Element", "Content": "To modify a Zone element, from the Assemblies part of the SLH Administration Tasks window, click the Zone drop-down list to display the list of available Zones which can be modified. Select the Zone to be modified, then select Modify to display the Modify SLH Assembly Zone window.\n\nThe functionality of the Modify SLH Assembly Zone window is identical to the Create SLH Assembly Zone window. Refer to Create Zone Element for further information.\n\n\n\nCreate Zone Element\nAssemblies\nSLH Administration Tasks\nZone\nModify\nModify SLH Assembly Zone\nModify SLH Assembly Zone\nCreate SLH Assembly Zone\nCreate Zone Element"}
{"Headers": "Delete Zone Element", "Content": "To delete a Zone element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Create Structure Element", "Content": "To create a Structure element make sure the correct Zone element is selected in the Assemblies part of the SLH Administration Tasks window.\nTo create a Structure element, from the Assemblies part of the SLH Administration Tasks window, click Create next to the Structure drop-down list to display the Create SLH Assembly Structure window.\n\nThe owning Zone element displays at the top of the Create SLH Assembly Structure window.\nName\nInput a name for the new Structure element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nName\nInput a name for the new Structure element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nClick Create to create the Structure element, or Cancel to discard any inputs and close the Create SLH Assembly Structure window.\nThe Structure element displays in the Model Explorer.\n\nName\nInput a name for the new Structure element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\n\n\n\nAssemblies\nSLH Administration Tasks\nAssemblies\nSLH Administration Tasks\nCreate\nCreate SLH Assembly Structure\nCreate SLH Assembly Structure\nName\nDescription\nFunction\nCreate\nCancel\nCreate SLH Assembly Structure"}
{"Headers": "Modify Structure Element", "Content": "To modify a Structure Element, from the Assemblies part of the SLH Administration Tasks window, click the Structure drop-down list to display the list of available Structures which can be modified. Select the Structure to be modified, then select Modify to display the Modify SLH Assembly Structure window.\n\nThe functionality of the Modify SLH Assembly Structure window is identical to the Create SLH Assembly Structure window. Refer to Create Structure Element for further information.\n\n\n\nCreate Structure Element\nAssemblies\nSLH Administration Tasks\nStructure\nModify\nModify SLH Assembly Structure\nModify SLH Assembly Structure\nCreate SLH Assembly Structure\nCreate Structure Element"}
{"Headers": "Delete Structure Element", "Content": "To delete a Structure element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Create Handrail Assembly", "Content": "To create a Handrail Assembly element, make sure the correct Structure element is selected in the Assemblies part of the SLH Administration Tasks window.\nTo create a Handrail Assembly element, from the Assemblies part of the SLH Administration Tasks window, click Create next to the Handrail drop-down list to display the Create Handrail Assembly window.\n\nNote:\nAll mandatory parts of the Create Handrail Assembly window are indicated with an amber triangle. The SLH application replaces the amber triangle with a green tick when the Create Handrail Assembly window has been populated with the required data.\n\n\n\nAssemblies\nSLH Administration\nTasks\nAssemblies\nSLH Administration Tasks\nCreate\nCreate Handrail Assembly\nNote\n:\nCreate Handrail Assembly\nCreate Handrail Assembly"}
{"Headers": "General", "Content": "The General part of the Create Tread Template window displays by default, the administrator can name and describe the new Tread Template element.\n\nName\nInput a name for the new Tread Template in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nName sub-elements\nSelect the check box for the SLH application to name new elements by default.\nTread Type\nSelect the Stair radio button to create a Tread Template for a Stair Flight.\nSelect the Step Ladder radio button to create a Tread Template for a Step Ladder.\nName\nInput a name for the new Tread Template in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nName sub-elements\nSelect the check box for the SLH application to name new elements by default.\nTread Type\nSelect the Stair radio button to create a Tread Template for a Stair Flight.\nSelect the Step Ladder radio button to create a Tread Template for a Step Ladder.\nClick Next to display the Parameters part of the Create Tread Template window. Refer to Tread Template Parameters for further information.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nName\nInput a name for the new Tread Template in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nName sub-elements\nSelect the check box for the SLH application to name new elements by default.\nTread Type\nSelect the Stair radio button to create a Tread Template for a Stair Flight.\nSelect the Step Ladder radio button to create a Tread Template for a Step Ladder.\n\n\n\nTread Template Parameters\nCreate Tread Template\nName\nDescription\nName sub-elements\nTread Type\nStair\nStep Ladder\nNext\nParameters\nCreate Tread Template\nTread Template Parameters\nCancel\nSLH Administration Tasks"}
{"Headers": "Continuous Handrail Select Specifications", "Content": "The Select Specifications part of the Create Handrail Assembly window allows the administrator to define the profile specifications of the top rail, other rails, post parts and the kickplate.\nThese parts and profiles are used when the user creates a handrail. When the user modifies the handrail parts the allowable values are taken from the defaults.\n\nTop Rail Specification\nClick Select to display the Top Rail Specification window.\nThe functionality of the Top Rail Specification window is explained as part of the process to create a Default. Refer to Handrail Profile Specification for further information.\nOther Rail Specification\nClick Select to display the Other Rail Specification window.\nThe functionality available from the Other Rail Specification window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nPost Part\nClick Select to display the Post Part window.\nThe functionality available from the Post Part window is identical to that available from the Gate Part window. Refer to Handrail Part for further information.\nKickplate Specification\nClick Select to display the Kickplate Specification window.\nThe functionality available from the Kickplate Specification window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nTop Rail Specification\nClick Select to display the Top Rail Specification window.\nThe functionality of the Top Rail Specification window is explained as part of the process to create a Default. Refer to Handrail Profile Specification for further information.\nOther Rail Specification\nClick Select to display the Other Rail Specification window.\nThe functionality available from the Other Rail Specification window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nPost Part\nClick Select to display the Post Part window.\nThe functionality available from the Post Part window is identical to that available from the Gate Part window. Refer to Handrail Part for further information.\nKickplate Specification\nClick Select to display the Kickplate Specification window.\nThe functionality available from the Kickplate Specification window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nClick Next to display the Assembly Details part of the Create Handrail Assembly window. Refer to Continuous Handrail Assembly Details for further information.\nClick Back to return to the General part of the Create Handrail Assembly window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nTop Rail Specification\nClick Select to display the Top Rail Specification window.\nThe functionality of the Top Rail Specification window is explained as part of the process to create a Default. Refer to Handrail Profile Specification for further information.\nOther Rail Specification\nClick Select to display the Other Rail Specification window.\nThe functionality available from the Other Rail Specification window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nPost Part\nClick Select to display the Post Part window.\nThe functionality available from the Post Part window is identical to that available from the Gate Part window. Refer to Handrail Part for further information.\nKickplate Specification\nClick Select to display the Kickplate Specification window.\nThe functionality available from the Kickplate Specification window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\n\n\n\nHandrail Profile Specification\nHandrail Profile Specification\nHandrail Part\nHandrail Profile Specification\nContinuous Handrail Assembly Details\nSelect Specifications\nCreate Handrail Assembly\nTop Rail Specification\nSelect\nTop Rail Specification\nTop Rail Specification\n\nHandrail Profile Specification\nOther Rail Specification\nSelect\nOther Rail Specification\nOther Rail Specification\nTop Rail Specification\nHandrail Profile Specification\nPost Part\nSelect\nPost Part\nPost Part\nGate Part\nHandrail Part\nKickplate Specification\nSelect\nKickplate Specification\nKickplate Specification\nTop Rail Specification\nHandrail Profile Specification\nNext\nCreate Handrail Assembly\nContinuous Handrail Assembly Details\nBack\nCreate Handrail Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Continuous Handrail Assembly Details", "Content": "The Assembly Details part of the Create Handrail Assembly window allows the administrator to define the continuous Handrail Assembly dimensions and is populated with constraints set in defaults.\n\nFrom the Assembly Details part of the Create Handrail Assembly window, define the continuous handrail dimensions.\nThe following values are used to display the handrail assembly, these values are taken from the defaults and used when a handrail is created.\nPost Spacing\nThe post spacing is the distance between the posts. The value, end and corner distances calculate the number of posts in the assembly.\nPost End Distance\nThe value defines the distance from the end of the handrail to the first and last post in the assembly.\nPost Corner Distance\nThe value defines the distance from the corner of the handrail to the first and last post of the assembly segment.\nRail Bend Radius\nThe value defines the bend radius for the rails of the assembly.\nKickplate Z Offset\nThe value defines the vertical distance from the route path to the kick plate. The position of the kick plate also depends on the justification chosen.\nKickplate X Offset\nThe value defines the horizontal distance from the route path to the kick plate.\nPost length\nThe value defines the length of all the posts in the assembly.\nPost X Offset\nThe value defines the horizontal distance from the route path to the post in the assembly.\nPost Z Offset\nThe value defines the vertical distance from the route path to the post in the assembly.\nPost Spacing\nThe post spacing is the distance between the posts. The value, end and corner distances calculate the number of posts in the assembly.\nPost End Distance\nThe value defines the distance from the end of the handrail to the first and last post in the assembly.\nPost Corner Distance\nThe value defines the distance from the corner of the handrail to the first and last post of the assembly segment.\nRail Bend Radius\nThe value defines the bend radius for the rails of the assembly.\nKickplate Z Offset\nThe value defines the vertical distance from the route path to the kick plate. The position of the kick plate also depends on the justification chosen.\nKickplate X Offset\nThe value defines the horizontal distance from the route path to the kick plate.\nPost length\nThe value defines the length of all the posts in the assembly.\nPost X Offset\nThe value defines the horizontal distance from the route path to the post in the assembly.\nPost Z Offset\nThe value defines the vertical distance from the route path to the post in the assembly.\nThe Rails list allows the administrator to add, delete and define the assembly rails.\n\nAdd Rail\nClick to add a new row to the Rails list. The values are copied from the previous rail.\nDelete Rail\nClick to remove the currently selected row from the Rails list.\nTop Distance\nInput a value to define the distance of the rail from the top rail. The value of the top row is always zero and is not editable.\nIf a new value is entered, the SLH application adjusts the values in the Height above FFL and Spacing columns accordingly.\nHeight above FFL\nInput a value to define the distance of the rail from the route path (normally positioned at finished floor level).\nIf a new value is entered, the SLH application adjusts the values in the Top Distance and Spacing columns accordingly.\nSpacing\nInput a value to define the distance of the rail from the rail above. The value of the top row is always zero and is not editable.\nIf a new value is entered, the SLH application adjusts the values in the Top Distance and Height above FFL columns accordingly.\nX Offset\nInput a value to define the horizontal distance of the rail from the route path.\n\nAdd Rail\nClick to add a new row to the Rails list. The values are copied from the previous rail.\n\nDelete Rail\nClick to remove the currently selected row from the Rails list.\nTop Distance\nInput a value to define the distance of the rail from the top rail. The value of the top row is always zero and is not editable.\nIf a new value is entered, the SLH application adjusts the values in the Height above FFL and Spacing columns accordingly.\nHeight above FFL\nInput a value to define the distance of the rail from the route path (normally positioned at finished floor level).\nIf a new value is entered, the SLH application adjusts the values in the Top Distance and Spacing columns accordingly.\nSpacing\nInput a value to define the distance of the rail from the rail above. The value of the top row is always zero and is not editable.\nIf a new value is entered, the SLH application adjusts the values in the Top Distance and Height above FFL columns accordingly.\nX Offset\nInput a value to define the horizontal distance of the rail from the route path.\nPost Spacing\nThe post spacing is the distance between the posts. The value, end and corner distances calculate the number of posts in the assembly.\nPost End Distance\nThe value defines the distance from the end of the handrail to the first and last post in the assembly.\nPost Corner Distance\nThe value defines the distance from the corner of the handrail to the first and last post of the assembly segment.\nRail Bend Radius\nThe value defines the bend radius for the rails of the assembly.\nKickplate Z Offset\nThe value defines the vertical distance from the route path to the kick plate. The position of the kick plate also depends on the justification chosen.\nKickplate X Offset\nThe value defines the horizontal distance from the route path to the kick plate.\nPost length\nThe value defines the length of all the posts in the assembly.\nPost X Offset\nThe value defines the horizontal distance from the route path to the post in the assembly.\nPost Z Offset\nThe value defines the vertical distance from the route path to the post in the assembly.\nAdd Rail\nClick to add a new row to the Rails list. The values are copied from the previous rail.\nDelete Rail\nClick to remove the currently selected row from the Rails list.\nTop Distance\nInput a value to define the distance of the rail from the top rail. The value of the top row is always zero and is not editable.\nIf a new value is entered, the SLH application adjusts the values in the Height above FFL and Spacing columns accordingly.\nHeight above FFL\nInput a value to define the distance of the rail from the route path (normally positioned at finished floor level).\nIf a new value is entered, the SLH application adjusts the values in the Top Distance and Spacing columns accordingly.\nSpacing\nInput a value to define the distance of the rail from the rail above. The value of the top row is always zero and is not editable.\nIf a new value is entered, the SLH application adjusts the values in the Top Distance and Height above FFL columns accordingly.\nX Offset\nInput a value to define the horizontal distance of the rail from the route path.\n\n\n\nAssembly Details\nCreate Handrail Assembly\nAssembly Details\nCreate Handrail Assembly\nPost Spacing\nPost End Distance\nPost Corner Distance\nRail Bend Radius\nKickplate Z Offset\nKickplate X Offset\nPost length\nPost X Offset\nPost Z Offset\nAdd Rail\nDelete Rail\nTop Distance\nHeight above FFL\nSpacing\nHeight above FFL\nTop Distance\nSpacing\nSpacing\nTop Distance\nHeight above FFL\nX Offset"}
{"Headers": "Panelled Handrail Assembly", "Content": "The administrator can select Specifications (refer to Panelled Handrail Select Specifications for further information) and define Assembly Details (refer to Panelled Handrail Assembly Details for further information) for the Panelled Handrail Assembly.\n\n\n\nPanelled Handrail Select Specifications\nPanelled Handrail Assembly Details\nPanelled Handrail Select Specifications\nPanelled Handrail Assembly Details"}
{"Headers": "Panelled Handrail Select Specifications", "Content": "The Select Specifications part of the Create Handrail Assembly window allows the administrator to define the panel parts and the profile specification for the kickplate. Panel Parts of the handrail can be added and removed from the list of defaults.\nThe list of panel parts in the handrail assembly are used to calculate the number and length of the panels when the user creates a handrail from the assembly.\n\nAll of the functionality for the addition and removal of Panel Parts, is identical to that available from the Detailing for Handrail part of the Create Defaults window. Refer to Handrail Part for further information.\nKickplate Specification\nClick Select to display the Kickplate Specification window.\nThe functionality available from the Kickplate Specification window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nKickplate Specification\nClick Select to display the Kickplate Specification window.\nThe functionality available from the Kickplate Specification window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nClick Next to display the Assembly Details part of the Create Handrail Assembly window. Refer to Panelled Handrail Assembly Details for further information.\nClick Back to return to the General part of the Create Handrail Assembly window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nKickplate Specification\nClick Select to display the Kickplate Specification window.\nThe functionality available from the Kickplate Specification window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\n\n\n\nHandrail Part\nHandrail Profile Specification\nPanelled Handrail Assembly Details\nSelect Specifications\nCreate Handrail Assembly\nDetailing for Handrail\nCreate Defaults\nHandrail Part\nKickplate Specification\nSelect\nKickplate Specification\nKickplate Specification\nTop Rail Specification window\nHandrail Profile Specification\nNext\nAssembly Details\nCreate Handrail Assembly\nPanelled Handrail Assembly Details\nBack\nGeneral\nCreate Handrail Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Panelled Handrail Assembly Details", "Content": "The Assembly Details part of the Create Handrail Assembly window allows the administrator to define the Handrail Assembly dimensions.\n\nPost Spacing\nInput the distance between the posts, end and corner distances to calculate the number of posts in the assembly.\nPost End Distance\nInput a value to define the distance from the end of the handrail to the first and last post in the assembly.\nPost Corner Distance\nInput a value to define the distance from the corner of the handrail to the first and last post of the assembly segment.\nRail Bend Radius\nInput a value to define the bend radius for the rails of the assembly.\nKickplate Z Offset\nInput a value to define the vertical distance from the route path to the kick plate. The position of the kick plate also depends on the justification chosen.\nKickplate X Offset\nInput a value to define the horizontal distance from the route path to the kick plate.\nPanel X Offset\nInput a value to define the horizontal distance from the route path to the panel in the assembly.\nPost Z Offset\nInput a value to define the vertical distance from the route path to the panel in the assembly.\nPost Spacing\nInput the distance between the posts, end and corner distances to calculate the number of posts in the assembly.\nPost End Distance\nInput a value to define the distance from the end of the handrail to the first and last post in the assembly.\nPost Corner Distance\nInput a value to define the distance from the corner of the handrail to the first and last post of the assembly segment.\nRail Bend Radius\nInput a value to define the bend radius for the rails of the assembly.\nKickplate Z Offset\nInput a value to define the vertical distance from the route path to the kick plate. The position of the kick plate also depends on the justification chosen.\nKickplate X Offset\nInput a value to define the horizontal distance from the route path to the kick plate.\nPanel X Offset\nInput a value to define the horizontal distance from the route path to the panel in the assembly.\nPost Z Offset\nInput a value to define the vertical distance from the route path to the panel in the assembly.\nClick Create to create the assembly.\nClick Back to return to the Select Specifications part of the Create Handrail Assembly window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nThe Assembly element displays in the Model Explorer and the 3D view.\n\nPost Spacing\nInput the distance between the posts, end and corner distances to calculate the number of posts in the assembly.\nPost End Distance\nInput a value to define the distance from the end of the handrail to the first and last post in the assembly.\nPost Corner Distance\nInput a value to define the distance from the corner of the handrail to the first and last post of the assembly segment.\nRail Bend Radius\nInput a value to define the bend radius for the rails of the assembly.\nKickplate Z Offset\nInput a value to define the vertical distance from the route path to the kick plate. The position of the kick plate also depends on the justification chosen.\nKickplate X Offset\nInput a value to define the horizontal distance from the route path to the kick plate.\nPanel X Offset\nInput a value to define the horizontal distance from the route path to the panel in the assembly.\nPost Z Offset\nInput a value to define the vertical distance from the route path to the panel in the assembly.\n\n\n\nAssembly Details\nCreate Handrail Assembly\nPost Spacing\nPost End Distance\nPost Corner Distance\nRail Bend Radius\nKickplate Z Offset\nKickplate X Offset\nPanel X Offset\nPost Z Offset\nCreate\nBack\nSelect Specifications\nCreate Handrail Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Modify Handrail Assembly", "Content": "To modify a Handrail Assembly element, from the Assemblies part of the SLH Administration Tasks window, click the Handrail drop-down list to display the list of available Handrails which can be modified. Select the Handrail to be modified, then select Modify, to display the Modify Handrail Assembly window.\n\nThe functionality of the Modify Handrail Assembly window is identical to the Create Handrail Assembly window. Refer to Create Handrail Assembly for further information.\n\n\n\nCreate Handrail Assembly\nAssemblies\nSLH Administration Tasks\nHandrail\nModify\nModify Handrail Assembly\nModify Handrail Assembly\nCreate Handrail Assembly\nCreate Handrail Assembly"}
{"Headers": "Delete Handrail Assembly", "Content": "To delete a Handrail Assembly element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Copy Handrail Assembly", "Content": "Copying an existing handrail assembly provides a quick and efficient method of creating new assemblies and editing the properties in the SLH Administration Tasks window.\nTo create a new Handrail Assembly element from an existing element make sure the correct Handrail Assembly element is selected in the Model Explorer.\nTo copy an existing Handrail Assembly element, right-click and select Copy from the drop-down list.\nTo paste a copy of the Handrail Assembly element, right-click and select Paste from the drop-down list.\nTo rename the pasted Handrail Assembly element, right-click and select Rename from the drop-down list to display the Name window. Refer to Common Functionality User Guide for further information. The copied element displays in the SLH Administration Tasks window.\n\n\n\nSLH Administration Tasks\nCopy\nPaste\nRename\nName\nCommon Functionality User Guide\nSLH Administration Tasks"}
{"Headers": "Create Rung Ladder Assembly", "Content": "To create a Rung Ladder Assembly element make sure the correct Structure element is selected in the Assemblies part of the SLH Administration Tasks window.\nTo create a Rung Ladder Assembly element, from the Assemblies part of the SLH Administration Tasks window, click Create next to the Rung Ladder drop-down list to display the Create Rung Ladder Assembly window.\n\nPreview\nThe Preview part of the Create Rung Ladder Assembly window displays throughout the creation process. The SLH application updates the Preview display each time the administrator clicks Next or Back.\n\nClick to manually update the Preview display.\n\nClick to manually update the Preview display.\nSummary\nThe Summary part of the Create Rung Ladder Assembly window displays throughout the creation process. The SLH application updates the Summary display each time the summary data is changed.\n\nClick to manually update the Preview display.\nNote:\nAll mandatory parts of the Create Rung Ladder Assembly window are indicated with an amber triangle. The SLH application replaces the amber triangle with a green tick when the Create Rung Ladder Assembly window has been populated with the required data.\n\n\n\nAssemblies\nSLH Administration\nTasks\nAssemblies\nSLH Administration Tasks\nCreate\nCreate Rung Ladder Assembly\nNote\n:\nCreate Rung Ladder Assembly\nCreate Rung Ladder Assembly\nPreview\nPreview\nCreate Rung Ladder Assembly\nNext\nBack\nSummary\nSummary\nCreate Rung Ladder Assembly"}
{"Headers": "Stiles Specification", "Content": "The Specification for Stiles part of the Create Rung Ladder Assembly window allows the administrator to define the stile specification and p-line justification for the Rung Ladder Assembly.\n\nStile\nClick Select to display the Select Stile window.\nThe functionality available from the Select Stile window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nOnce the stile specification has been chosen, the preview is updated with the new profile.\nMirror\nClick MIrror to mirror the stringer of the Rung Ladder.\nStile\nClick Select to display the Select Stile window.\nThe functionality available from the Select Stile window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nOnce the stile specification has been chosen, the preview is updated with the new profile.\nMirror\nClick MIrror to mirror the stringer of the Rung Ladder.\nClick Next to display the Front Exit for Stiles part of the Create Rung Ladder Assembly window. Refer to Stiles Front Exit for further information.\nClick Back to return to the General part of the Create Rung Ladder Assembly window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nStile\nClick Select to display the Select Stile window.\nThe functionality available from the Select Stile window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nOnce the stile specification has been chosen, the preview is updated with the new profile.\nMirror\nClick MIrror to mirror the stringer of the Rung Ladder.\n\n\n\nHandrail Profile Specification\nStiles Front Exit\nSpecification for Stiles\nCreate Rung Ladder Assembly\nStile\nSelect\nSelect Stile\nSelect Stile\nTop Rail Specification\nHandrail Profile Specification\nMirror\nMIrror\nNext\nFront Exit for Stiles\nCreate Rung Ladder Assembly\nStiles Front Exit\nBack\nGeneral\nCreate Rung Ladder Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Stiles Front Exit", "Content": "The Front Exit for Stiles part of the Create Rung Ladder Assembly window allows the administrator to select or define the front exit shape for the Rung Ladder Assembly.\n\nThe administrator can select a Front Exit Shape from the display. Alternatively, the administrator can modify a selected shape with the Shape Editor. Refer to Front Exit Shape Editor for further information.\nClick Next to display the Stile Connection for Cage part of the Create Rung Ladder Assembly window. Refer to Cage Stile Connection for further information.\nClick Back to return to the Specification for Stiles part of the Create Rung Ladder Assembly window.\nClick Cancel to delete the assembly and return to the SLH Administration Tasks window.\n\n\n\nFront Exit Shape Editor\nCage Stile Connection\nFront Exit for Stiles\nCreate Rung Ladder Assembly\nFront Exit Shape Editor\nNext\nStile Connection for Cage\nCreate Rung Ladder Assembly\nCage Stile Connection\nBack\nSpecification for Stiles\nCreate Rung Ladder Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Front Exit Shape Editor", "Content": "The Shape Editor part of the Create Rung Ladder Assembly window allows the administrator to specify the front exit shape for the Rung Ladder Assembly.\nClick Shape Editor to display the Shape Editor part of the Create Rung Ladder Assembly window.\n\nThe X column defines the horizontal offset of the left stile. The Z column defines the vertical offset. The administrator can modify the values to define the new shape.\nTo visualize the dimensions of the shape, click View Dimensions to display the Front Exit Style Dimensions window.\n\nThe administrator can view all Rules associated with the shape, click View Full Rules to display the Stiles (Front Exit) Rules window.\n\nClick Dismiss to return to the Shape Editor part of the Create Rung Ladder Assembly window.\nClick Apply Changes to accept the changes made to the shape.\nClick Back to Selection to discard any inputs and return to the Front Exit for Stiles part of the Create Rung Ladder Assembly window.\n\n\n\nShape Editor\nCreate Rung Ladder Assembly\nShape Editor\nShape Editor\nCreate Rung Ladder Assembly\nX\nZ\nView Dimensions\nFront Exit Style Dimensions\nView Full Rules\nStiles (Front Exit) Rules\nDismiss\nShape Editor\nCreate Rung Ladder Assembly\nApply Changes\nBack to Selection\nFront Exit for Stiles\nCreate Rung Ladder Assembly"}
{"Headers": "Cage Stile Connection", "Content": "The Stile Connection for Cage part of the Create Rung Ladder Assembly window allows the administrator to define the dimensions for the Cage Hoop Start Position.\n\nThe cage hoop start position is defined in terms of the stile properties. The width is defined in terms of an A dimension and the depth in terms of a B dimension. The width is the distance between the point defined by the width inside the stiles and the start position of the hoop. The depth is the distance between the center of the rung and the start position of the hoop.\n\n\n\nStile Connection for Cage\nCreate Rung Ladder Assembly"}
{"Headers": "Cage Tube Shape", "Content": "The Tube Shape for Cage part of the Create Rung Ladder Assembly window allows the administrator to select or define the tube shape for the Rung Ladder Assembly.\n\nThe administrator can select a Tube Shape from the display. Alternatively, the administrator can modify a selected shape with the Bar Editor (refer to Tube Shape Bar Editor for further information) and the Shape Editor (refer to Tube Shape Editor for further information).\nClick Next to display the Front Exit Shape for Cage part of the Create Rung Ladder Assembly window. Refer to Cage Front Exit Shape for further information.\nClick Back to return to the Stile Connection part of the Create Rung Ladder Assembly window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nTube Shape Bar Editor\nTube Shape Editor\nCage Front Exit Shape\nTube Shape for Cage\nCreate Rung Ladder Assembly\nTube Shape Bar Editor\nTube Shape Editor\nNext\nCreate Rung Ladder Assembly\nCage Front Exit Shape\nBack\nCreate Rung Ladder Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Tube Shape Bar Editor", "Content": "The Position Cage Bars part of the Create Rung Ladder Assembly window allows the administrator to position the vertical cage bars for the Rung Ladder Assembly.\nClick Bar Editor to display the Position Cage Bars part of the Create Rung Ladder Assembly window.\n\nThe administrator can modify the values to define the new bar. If the X and Y columns are left blank the position is defined using the Degrees column.\nDegrees\nThe Degrees column defines the rotation of the bar.\nX\nThe X column defines the horizontal offset parallel to the rungs.\nY\nThe Y column defines the horizontal offset perpendicular to the rungs.\nDegrees\nThe Degrees column defines the rotation of the bar.\nX\nThe X column defines the horizontal offset parallel to the rungs.\nY\nThe Y column defines the horizontal offset perpendicular to the rungs.\nThe rows are used to define half of the final shape which is symmetrical. If the 180deg row is used the bar is not duplicated.\nClick Apply Changes to accept the changes made to the bar.\nClick Back to Selection to discard any inputs and return to the Tube Shape for Cage part of the Create Rung Ladder Assembly window.\nDegrees\nThe Degrees column defines the rotation of the bar.\nX\nThe X column defines the horizontal offset parallel to the rungs.\nY\nThe Y column defines the horizontal offset perpendicular to the rungs.\n\n\n\nPosition Cage Bars\nCreate Rung Ladder Assembly\nBar Editor\nPosition Cage Bars\nCreate Rung Ladder Assembly\nDegrees\nDegrees\nX\nX\nY\nY\nApply Changes\nBack to Selection\nTube Shape for Cage\nCreate Rung Ladder Assembly"}
{"Headers": "Cage Front Exit Shape", "Content": "The Front Exit Shape for Cage part of the Create Rung Ladder Assembly window allows the administrator to select or define the front exit shape for the Rung Ladder Assembly.\n\nThe administrator can select a Front Exit Shape from the display. Alternatively, the administrator can modify a selected shape with the Bar Editor (refer to Front Exit Shape Bar Editor for further information) and the Shape Editor (refer to Front Exit Shape Editor for further information).\nClick Next to display the Side Exit Shape for Cage part of the Create Rung Ladder Assembly window. Refer to Cage Side Exit Shape for further information.\nClick Back to return to the Tube Shape for Cage part of the Create Rung Ladder Assembly window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nFront Exit Shape Bar Editor\nFront Exit Shape Editor\nCage Side Exit Shape\nFront Exit Shape for Cage\nCreate Rung Ladder Assembly\nFront Exit Shape Bar Editor\nFront Exit Shape Editor\nNext\nSide Exit Shape for Cage\nCreate Rung Ladder Assembly\nCage Side Exit Shape\nBack\nTube Shape for Cage\nCreate Rung Ladder Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Front Exit Shape Bar Editor", "Content": "The Position Cage Bars part of the Create Rung Ladder Assembly window allows the administrator to position the front exit vertical bars for the Rung Ladder Assembly.\nClick Bar Editor to display the Position Cage Bars part of the Create Rung Ladder Assembly window.\n\nThe functionality available from the Front Exit Shape Bar Editor is identical to that available from the Tube Shape Bar Editor. Refer to Tube Shape Bar Editor for further information.\n\n\n\nTube Shape Bar Editor\nPosition Cage Bars\nCreate Rung Ladder Assembly\nBar Editor\nPosition Cage Bars\nCreate Rung Ladder Assembly\nFront Exit Shape Bar Editor\nTube Shape Bar Editor\nTube Shape Bar Editor"}
{"Headers": "Cage Side Exit Shape", "Content": "The Side Exit Shape for Cage part of the Create Rung Ladder Assembly window allows the administrator to select or define the side exit shape for the Rung Ladder Assembly.\n\nThe administrator can select a Side Exit Shape from the display. Alternatively, the administrator can modify a selected shape with the Bar Editor (refer to Side Exit Shape Bar Editor for further information) and the Shape Editor (refer to Side Exit Shape Editor for further information).\nThe corner segment is the L shaped part of the cage from the stile to the cage exit. Input a value in the field to define the Corner Segment Offset (the default is 0 mm).\nClick Next to display the Flare for Cage part of the Create Rung Ladder Assembly window. Refer to Cage Flare for further information.\nClick Back to return to the Front Exit Shape for Cage part of the Create Rung Ladder Assembly window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nSide Exit Shape Bar Editor\nSide Exit Shape Editor\nCage Flare\nSide Exit Shape for Cage\nCreate Rung Ladder Assembly\nSide Exit Shape Bar Editor\nSide Exit Shape Editor\nCorner Segment Offset\nNext\nFlare for Cage\nCreate Rung Ladder Assembly\nCage Flare\nBack\nFront Exit Shape for Cage\nCreate Rung Ladder Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Side Exit Shape Bar Editor", "Content": "The Position Cage Bars part of the Create Rung Ladder Assembly window allows the administrator to position the side exit vertical bars for the Rung Ladder Assembly.\nClick Bar Editor to display the Position Cage Bars part of the Create Rung Ladder Assembly window.\n\nThe functionality available from the Side Exit Shape Bar Editor is identical to that available from the Tube Shape Bar Editor. Refer to Tube Shape Bar Editor for further information.\n\n\n\nTube Shape Bar Editor\nPosition Cage Bars\nCreate Rung Ladder Assembly\nBar Editor\nPosition Cage Bars\nCreate Rung Ladder Assembly\nSide Exit Shape Bar Editor\nTube Shape Bar Editor\nTube Shape Bar Editor"}
{"Headers": "Side Exit Shape Editor", "Content": "The Shape Editor part of the Create Rung Ladder Assembly window allows the administrator to specify the side exit shape for the Rung Ladder Assembly.\nClick Shape Editor to display the Shape Editor part of the Create Rung Ladder Assembly window.\n\nThe functionality available from the Side Exit Shape Editor is identical to that available from the Tube Shape Editor. Refer to Tube Shape Editor for further information.\n\n\n\nTube Shape Editor\nShape Editor\nCreate Rung Ladder Assembly\nShape Editor\nShape Editor\nCreate Rung Ladder Assembly\nSide Exit Shape Editor\nTube Shape Editor\nTube Shape Editor"}
{"Headers": "Cage Flare", "Content": "The Flare for Cage part of the Create Rung Ladder Assembly window allows the administrator to select the cage flare for the Rung Ladder Assembly.\n\nThe administrator can select a Flare type from the display. The options available are:\nClick Next to display the Representation for Details part of the Create Rung Ladder Assembly window. Refer to Rung Ladder Details for further information.\nClick Back to return to the Side Exit Shape for Cage part of the Create Rung Ladder Assembly window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nConcentric\nEccentric\nNone\nConcentric\nConcentric\nEccentric\nEccentric\nNone\nNone\n\n\n\nRung Ladder Details\nFlare for Cage\nCreate Rung Ladder Assembly\nNext\nRepresentation for Details\nCreate Rung Ladder Assembly\nRung Ladder Details\nBack\nSide Exit Shape for Cage\nCreate Rung Ladder Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Rung Ladder Details", "Content": "The Representation for Details part of the Create Rung Ladder Assembly window allows the administrator to preview the Rung Ladder Assembly in a number of different configurations.\n\nExit Type\nSelect a type from the drop-down list to preview an exit type for the Rung Ladder Assembly. The options available are:\nFront Exit\nLeft Side Exit\nRight Side Exit\nOmit Cage\nSelect the check box to remove the cage from the Preview display.\nExit Type\nSelect a type from the drop-down list to preview an exit type for the Rung Ladder Assembly. The options available are:\nOmit Cage\nSelect the check box to remove the cage from the Preview display.\nClick Build Assembly to create the assembly.\nClick Back to return to the Flare for Cage part of the Create Handrail Assembly window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nExit Type\nSelect a type from the drop-down list to preview an exit type for the Rung Ladder Assembly. The options available are:\nFront Exit\nLeft Side Exit\nRight Side Exit\nOmit Cage\nSelect the check box to remove the cage from the Preview display.\nFront Exit\nLeft Side Exit\nRight Side Exit\nFront Exit\nFront Exit\nLeft Side Exit\nLeft Side Exit\nRight Side Exit\nRight Side Exit\n\n\n\nRepresentation for Details\nCreate Rung Ladder Assembly\nExit Type\nOmit Cage\nBuild Assembly\nBack\nFlare for Cage\nCreate Handrail Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Modify Rung Ladder Assembly", "Content": "To modify a Rung Ladder Assembly element, from the Assemblies part of the SLH Administration Tasks window, click the Rung Ladder drop-down list to display the list of available Rung Ladders which can be modified. Select the Rung Ladder to be modified, then select Modify, to display the Modify Rung Ladder Assembly window.\n\nThe functionality of the Modify Rung Ladder Assembly window is identical to the Create Rung Ladder Assembly window. Refer to Create Rung Ladder Assembly for further information.\n\n\n\nCreate Rung Ladder Assembly\nAssemblies\nSLH Administration Tasks\nRung Ladder\nModify\nModify Rung Ladder Assembly\nModify Rung Ladder Assembly\nCreate Rung Ladder Assembly\nCreate Rung Ladder Assembly"}
{"Headers": "Delete Rung Ladder Assembly", "Content": "To delete a Rung Ladder Assembly element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Copy Rung Ladder Assembly", "Content": "Copying an existing Rung Ladder Assembly provides a quick and efficient method of creating new assemblies and editing the properties in the SLH Administration Tasks window.\nTo create a new Rung Ladder Assembly element from an existing element make sure the correct Rung Ladder Assembly element is selected in the Model Explorer.\nTo copy an existing Rung Ladder Assembly element, right-click and select Copy from the drop-down list.\nTo paste a copy of the Rung Ladder Assembly element, right-click and select Paste from the drop-down list.\nTo rename the pasted Rung Ladder Assembly element, right-click and select Rename from the drop-down list to display the Name window. Refer to Common Functionality User Guide for further information.\nThe copied element displays in the SLH Administration Tasks window.\n\n\n\nSLH Administration Tasks\nCopy\nPaste\nRename\nName\nCommon Functionality User Guide\nSLH Administration Tasks"}
{"Headers": "Create Step Ladder Assembly", "Content": "To create a Step Ladder Assembly element make sure the correct Structure element is selected in the Assemblies part of the SLH Administration Tasks window.\nTo create a Step Ladder Assembly element, from the Assemblies part of the SLH Administration Tasks window, click Create next to the Step Ladder drop-down list to display the Create Step Ladder Handrail Assembly window.\n\nNote:\nAll mandatory parts of the Create Step Ladder Handrail Assembly window are indicated with an amber triangle. The SLH application replaces the amber triangle with a green tick when the Create Step Ladder Handrail Assembly window has been populated with the required data.\n\n\n\nAssemblies\nSLH Administration\nTasks\nAssemblies\nSLH Administration Tasks\nCreate\nCreate Step Ladder Handrail Assembly\nNote\n:\nCreate Step Ladder Handrail Assembly\nCreate Step Ladder Handrail Assembly"}
{"Headers": "Handrail Specification", "Content": "The Specifications part of the Create Step Ladder Handrail Assembly window allows the administrator to define the handrail specification and p-line justification for the Step Ladder Assembly.\n\nPreview\nThe Preview part of the Create Step Ladder Handrail Assembly window displays throughout the creation process. The SLH application updates the Preview display each time the administrator clicks Next or Back.\n\nClick to manually update the Preview display.\n\nClick to manually update the Preview display.\nTo visualize how the handrail clear width parameters equate to the step ladder, click Show diagram to display the Handrail Clear Width window.\n\nStringer\nClick Select to display the Select Stringer window.\nThe functionality available from the Select Stringer window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nHandrail\nClick Select to display the Select Handrail window.\nThe functionality available from the Select Handrail window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nPosts\nClick Select to display the Select Posts window.\nThe functionality available from the Select Posts window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nStringer\nClick Select to display the Select Stringer window.\nThe functionality available from the Select Stringer window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nHandrail\nClick Select to display the Select Handrail window.\nThe functionality available from the Select Handrail window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nPosts\nClick Select to display the Select Posts window.\nThe functionality available from the Select Posts window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nClick Next to display the Handrail Bottom Shape part of the Create Step Ladder Handrail Assembly window. Refer to Handrail Bottom Shape for further information.\nClick Back to return to the General part of the Create Step Ladder Handrail Assembly window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nClick to manually update the Preview display.\nStringer\nClick Select to display the Select Stringer window.\nThe functionality available from the Select Stringer window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nHandrail\nClick Select to display the Select Handrail window.\nThe functionality available from the Select Handrail window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nPosts\nClick Select to display the Select Posts window.\nThe functionality available from the Select Posts window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\n\n\n\nHandrail Profile Specification\nHandrail Profile Specification\nHandrail Profile Specification\nHandrail Bottom Shape\nSpecifications\nCreate Step Ladder Handrail Assembly\nPreview\nPreview\nCreate Step Ladder Handrail Assembly\nNext\nBack\nShow diagram\nHandrail Clear Width\nStringer\nSelect\nSelect Stringer\nSelect Stringer\nTop Rail Specification window\nHandrail Profile Specification\nHandrail\nSelect\nSelect Handrail\nSelect Handrail\nTop Rail Specification window\nHandrail Profile Specification\nPosts\nSelect\nSelect Posts\nSelect Posts\nTop Rail Specification window\nHandrail Profile Specification\nNext\nHandrail Bottom Shape\nCreate Step Ladder Handrail Assembly\nHandrail Bottom Shape\nBack\nGeneral\nCreate Step Ladder Handrail Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Handrail Bottom Shape", "Content": "The Handrail Bottom Shape part of the Create Step Ladder Handrail Assembly window allows the administrator to select and define the Handrail Bottom Shape for the Step Ladder Assembly.\n\nThe administrator can select a Handrail Bottom Shape from the display. Alternatively, the administrator can modify a selected shape with the Shape Editor. Refer to Handrail Bottom Shape Editor for further information.\nClick Next to display the Handrail Top Shape part of the Create Step Ladder Handrail Assembly window. Refer to Handrail Top Shape for further information.\nClick Back to return to the Specifications part of the Create Step Ladder Handrail Assembly window.\nClick Cancel to delete the assembly and return to the SLH Administration Tasks window.\n\n\n\nHandrail Bottom Shape Editor\nHandrail Top Shape\nHandrail Bottom Shape\nCreate Step Ladder Handrail Assembly\nHandrail Bottom Shape Editor\nNext\nHandrail Top Shape\nCreate Step Ladder Handrail Assembly\nHandrail Top Shape\nBack\nSpecifications\nCreate Step Ladder Handrail Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Handrail Bottom Shape Editor", "Content": "The Shape Editor part of the Create Step Ladder Handrail Assembly window allows the administrator to define the handrail bottom shape for the Step Ladder Assembly.\nClick Shape Editor to display the Shape Editor part of the Create Step Ladder Handrail Assembly window.\n\nThe No column defines the number of points applied to the bottom handrail shape.\nThe A column defines the handrail length. The administrator can modify the values to define the new shape.\nThe Radius column defines the handrail bend radius. The administrator can modify the values to define the new shape.\nTo visualize the dimensions of the shape, click View Dimensions to display the Bottom Handrail Dimensions window.\n\nThe administrator can view all Rules associated with the shape, click View Full Rules to display the Step Ladder Handrail Rules - Bottom Shape window.\n\nClick Dismiss to return to the Shape Editor part of the Create Step Ladder Handrail Assembly window.\nClick Apply Changes to accept the changes made to the shape.\nClick Back to Selection to discard any inputs and return to the Handrail Bottom Shape part of the Create Step Ladder Handrail Assembly window.\n\n\n\nShape Editor\nCreate Step Ladder Handrail Assembly\nShape Editor\nShape Editor\nCreate Step Ladder Handrail Assembly\nNo\nA\nRadius\nView Dimensions\nBottom Handrail Dimensions\nView Full Rules\nStep Ladder Handrail Rules - Bottom Shape\nDismiss\nShape Editor\nCreate Step Ladder Handrail Assembly\nApply Changes\nBack to Selection\nHandrail Bottom Shape\nCreate Step Ladder Handrail Assembly"}
{"Headers": "Handrail Top Shape", "Content": "The Handrail Top Shape part of the Create Step Ladder Handrail Assembly window allows the administrator to select or define the Handrail Bottom Shape for the Step Ladder Assembly.\n\nThe administrator can select a Handrail Top Shape from the display. Alternatively, the administrator can modify a selected shape with the Shape Editor. Refer to Handrail Top Shape Editor for further information.\nSelect the Omit Horizontal Mid Rail check box to remove the mid rail from the Top Handrail of the Step Ladder Assembly.\nClick Build Assembly to create the assembly.\nClick Back to return to the Handrail Bottom Shape part of the Create Step Ladder Handrail Assembly window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nHandrail Top Shape Editor\nHandrail Top Shape\nCreate Step Ladder Handrail Assembly\nHandrail Top Shape Editor\nOmit Horizontal Mid Rail\nBuild Assembly\nBack\nHandrail Bottom Shape\nCreate Step Ladder Handrail Assembly\nCancel\nSLH Administration Tasks"}
{"Headers": "Handrail Top Shape Editor", "Content": "The Shape Editor part of the Create Step Ladder Handrail Assembly window allows the administrator to define the handrail top shape for the Step Ladder Assembly.\nClick Shape Editor to display the Shape Editor part of the Create Step Ladder Handrail Assembly window.\n\nNo\nThe No column defines the number of points applied to the top handrail shape.\nThe last two points are assigned to the horizontal mid rail (if included in the Step Ladder Assembly).\nY\nThe Y column defines the horizontal offset for the handrail. The administrator can modify the values to define the new shape.\nZ\nThe Y column defines the vertical offset for the handrail. The administrator can modify the values to define the new shape.\nRadius\nThe Radius column defines the handrail bend radius. The administrator can modify the values to define the new shape.\nNo\nThe No column defines the number of points applied to the top handrail shape.\nThe last two points are assigned to the horizontal mid rail (if included in the Step Ladder Assembly).\nY\nThe Y column defines the horizontal offset for the handrail. The administrator can modify the values to define the new shape.\nZ\nThe Y column defines the vertical offset for the handrail. The administrator can modify the values to define the new shape.\nRadius\nThe Radius column defines the handrail bend radius. The administrator can modify the values to define the new shape.\nTo visualize the dimensions of the shape, click View Dimensions to display the Top Handrail Dimensions window.\n\nThe administrator can view all Rules associated with the shape, click View Full Rules to display the Step Ladder Handrail Rules - Top Shape window.\n\nClick Dismiss to return to the Shape Editor part of the Create Step Ladder Handrail Assembly window.\nClick Apply Changes to accept the changes made to the shape.\nClick Back to Selection to discard any inputs and return to the Handrail Top Shape part of the Create Step Ladder Handrail Assembly window.\nNo\nThe No column defines the number of points applied to the top handrail shape.\nThe last two points are assigned to the horizontal mid rail (if included in the Step Ladder Assembly).\nY\nThe Y column defines the horizontal offset for the handrail. The administrator can modify the values to define the new shape.\nZ\nThe Y column defines the vertical offset for the handrail. The administrator can modify the values to define the new shape.\nRadius\nThe Radius column defines the handrail bend radius. The administrator can modify the values to define the new shape.\n\n\n\nShape Editor\nCreate Step Ladder Handrail Assembly\nShape Editor\nShape Editor\nCreate Step Ladder Handrail Assembly\nNo\nNo\nY\nY\nZ\nY\nRadius\nRadius\nView Dimensions\nTop Handrail Dimensions\nView Full Rules\nStep Ladder Handrail Rules - Top Shape\nDismiss\nShape Editor\nCreate Step Ladder Handrail Assembly\nApply Changes\nBack to Selection\nHandrail Top Shape\nCreate Step Ladder Handrail Assembly"}
{"Headers": "Modify Step Ladder Assembly", "Content": "To modify a Step Ladder Assembly element, from the Assemblies part of the SLH Administration Tasks window, click the Step Ladder drop-down list to display the list of available Step Ladders which can be modified. Select the Step Ladder to be modified, then select Modify, to display the Modify Step Ladder Handrail Assembly window.\n\nThe functionality of the Modify Step Ladder Handrail Assembly window is identical to the Create Step Ladder Handrail Assembly window. Refer to Create Step Ladder Assembly for further information.\n\n\n\nCreate Step Ladder Assembly\nAssemblies\nSLH Administration Tasks\nStep Ladder\nModify\nModify Step Ladder Handrail Assembly\nModify Step Ladder Handrail Assembly\nCreate Step Ladder Handrail Assembly\nCreate Step Ladder Assembly"}
{"Headers": "Delete Step Ladder Assembly", "Content": "To delete a Step Ladder Assembly element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Copy Step Ladder Assembly", "Content": "Copying an existing Step Ladder Assembly provides a quick and efficient method of creating new assemblies and editing the properties in the SLH Administration Tasks window.\nTo create a new Step Ladder Assembly element from an existing element make sure the correct Step Ladder Assembly element is selected in the Model Explorer.\nTo copy an existing Step Ladder Assembly element, right-click and select Copy from the drop-down list.\nTo paste a copy of the Step Ladder Assembly element, right-click and select Paste from the drop-down list.\nTo rename the pasted Step Ladder Assembly element, right-click and select Rename from the drop-down list to display the Name window. Refer to Common Functionality User Guide for further information.\nThe copied element displays in the SLH Administration Tasks window.\n\n\n\nSLH Administration Tasks\nCopy\nPaste\nRename\nName\nCommon Functionality User Guide\nSLH Administration Tasks"}
{"Headers": "Templates", "Content": "The Templates part of the SLH Administration Tasks window allows the administrator to create and modify the Templates available to the user.\n\nThe administrator can create six different types of SLH Template. Each new SLH Template displays as a TMPL element in the Model Explorer:\nThere is no limit to the number of TMPL elements that can appear in the SLH application, the administrator has the flexibility to create any number of Templates.\nTread Template\nPost Template\nHandrail Gate Template\nTermination Template\nHandrail Panel Template\nRung Ladder Gate Template\nTread Template\nTread Template\nPost Template\nPost Template\nHandrail Gate Template\nHandrail Gate Template\nTermination Template\nTermination Template\nHandrail Panel Template\nHandrail Panel Template\nRung Ladder Gate Template\nRung Ladder Gate Template\n\n\n\nTemplates\nSLH Administration Tasks"}
{"Headers": "Template Hierarchy Elements", "Content": "A number of hierarchy elements require creation before the administrator can create the Template elements:\n\nSLH Template World (TPWL)\nSLH Template Area (TMAR)\nSLH Template World (TPWL)\nSLH Template World (TPWL)\nSLH Template Area (TMAR)\nSLH Template Area (TMAR)\n\n\n"}
{"Headers": "Create Template World", "Content": "To create a Template World element, from the Templates part of the SLH Administration Tasks window, click Create next to the World drop-down list to display the Create SLH Template World window.\n\nThe owning database displays at the top of the Create SLH Template World window.\nName\nInput a name for the new Template World element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nName\nInput a name for the new Template World element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nClick Create to create the Template World element, or Cancel to discard any inputs and close the Create SLH Template World window.\nThe Template World element displays in the Model Explorer.\n\nName\nInput a name for the new Template World element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\n\n\n\nTemplates\nSLH Administration Tasks\nCreate\nCreate SLH Template World\nCreate SLH Template World\nName\nDescription\nFunction\nCreate\nCancel\nCreate SLH Template World"}
{"Headers": "Modify Template World", "Content": "To modify a Template World element, from the Templates part of the SLH Administration Tasks window, click the World drop-down list to display the list of available Template Worlds which can be modified. Select the Template World to be modified, then select Modify to display the Modify SLH Template World window.\n\nThe functionality of the Modify SLH Template World window is identical to the Create SLH Template World window. Refer to Create Template World for further information.\n\n\n\nCreate Template World\nTemplates\nSLH Administration Tasks\nWorld\nModify\nModify SLH Template World\nModify SLH Template World\nCreate SLH Template World\nCreate Template World"}
{"Headers": "Delete Template World", "Content": "To delete a Template World element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Create Template Area", "Content": "To create a Template Area element, from the Templates part of the SLH Administration Tasks window, click Create next to the Area drop-down list to display the Create SLH Template Area window.\n\nThe owning Template World displays at the top of the Create SLH Template Area window.\nName\nInput a name for the new Template Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nName\nInput a name for the new Template Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\nClick Create to create the Template Area element, or Cancel to discard any inputs and close the Create SLH Template Area window.\nThe Template Area element displays in the Model Explorer.\n\nName\nInput a name for the new Template Area element in the field.\nDescription\nThe administrator can input a description into the optional field. If populated, the description displays in the list of administration tasks.\nFunction\nThe administrator can input a function into the optional field.\n\n\n\nTemplates\nSLH Administration Tasks\nCreate\nCreate SLH Template Area\nCreate SLH Template Area\nName\nDescription\nFunction\nCreate\nCancel\nCreate SLH Template Area"}
{"Headers": "Modify Template Area", "Content": "To modify a Template Area element, from the Templates part of the SLH Administration Tasks window, click the Area drop-down list to display the list of available Template Areas which can be modified. Select the Template Area to be modified, then select Modify to display the Modify SLH Template Area window.\n\nThe functionality of the Modify SLH Template Area window is identical to the Create SLH Template Area window. Refer to Create Template Area for further information.\n\n\n\nCreate Template Area\nTemplates\nSLH Administration Tasks\nArea\nModify\nModify SLH Template Area\nModify SLH Template Area\nCreate SLH Template Area\nCreate Template Area"}
{"Headers": "Delete Template Area", "Content": "To delete a Template Area element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Create Tread Template", "Content": "Tread templates are used in the creation of stair flights and step ladders. The allowable treads are defined in the defaults by referencing tread parts. Tread parts are created in the PARAGON module. Refer to Catalog and Specifications User Guide for further information. Tread parts reference either catalog or template treads.\nTo create a Tread Template element make sure the correct Area element is selected in the Templates part of the SLH Administration Tasks window.\nTo create a Tread Template element, from the Templates part of the SLH Administration Tasks window, click Create next to the Treads drop-down list to display the Create Tread Template window.\n\nNote:\nAll mandatory parts of the Create Tread Template window are indicated with an amber triangle. The SLH application replaces the amber triangle with a green tick when the Create Tread Template window has been populated with the required data.\n\n\n\nCatalog and Specifications User Guide\nSLH Administration\nTasks\nTemplates\nSLH Administration Tasks\nCreate\nCreate Tread Template\nNote\n:\nCreate Tread Template\nCreate Tread Template"}
{"Headers": "Tread Template Parameters", "Content": "The Parameters part of the Create Tread Template window allows the administrator to define the Tread Template dimensions.\n\nTread Width\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nTread Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nTread Thickness\nInput a value to define the tread thickness for the template.\nBack Height\nInput a value to define the back height for the template.\nBack Thickness\nInput a value to define the back thickness for the template.\nFront Height\nInput a value to define the front height for the template.\nFront Thickness\nInput a value to define the front thickness for the template.\nEnd Height\nInput a value to define the end height for the template.\nEnd Thickness\nInput a value to define the end thickness for the template.\nEnd Offset from Front\nInput a value to define the gap between the front of the tread to the end plates.\nTo remove the end offset from front element from the template, click to clear the Included check box.\nEnd Offset from Back\nInput a value to define the gap between the back of the tread to the end plates.\nTo remove the end offset from back element from the template, click to clear the Included check box.\nEnd Chamfer\nInput a value to define the end chamfer for the template.\nTo remove the end chamfer element from the template, click to clear the Included check box.\nTread Bend Radius\nInput a value to define the tread bend radius for the template.\nTo remove the tread bend radius element from the template, click to clear the Included check box.\nTread Width\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nTread Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nTread Thickness\nInput a value to define the tread thickness for the template.\nBack Height\nInput a value to define the back height for the template.\nBack Thickness\nInput a value to define the back thickness for the template.\nFront Height\nInput a value to define the front height for the template.\nFront Thickness\nInput a value to define the front thickness for the template.\nEnd Height\nInput a value to define the end height for the template.\nEnd Thickness\nInput a value to define the end thickness for the template.\nEnd Offset from Front\nInput a value to define the gap between the front of the tread to the end plates.\nTo remove the end offset from front element from the template, click to clear the Included check box.\nEnd Offset from Back\nInput a value to define the gap between the back of the tread to the end plates.\nTo remove the end offset from back element from the template, click to clear the Included check box.\n\nEnd Chamfer\nInput a value to define the end chamfer for the template.\nTo remove the end chamfer element from the template, click to clear the Included check box.\nTread Bend Radius\nInput a value to define the tread bend radius for the template.\nTo remove the tread bend radius element from the template, click to clear the Included check box.\nThe diagram below illustrates the Tread Template dimensions as an example:\n\nClick Next to display the Profiles part of the Create Tread Template window. Refer to Tread Template Profiles for further information.\nClick Back to return to the Parameters part of the Create Tread Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nTread Width\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nTread Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nTread Thickness\nInput a value to define the tread thickness for the template.\nBack Height\nInput a value to define the back height for the template.\nBack Thickness\nInput a value to define the back thickness for the template.\nFront Height\nInput a value to define the front height for the template.\nFront Thickness\nInput a value to define the front thickness for the template.\nEnd Height\nInput a value to define the end height for the template.\nEnd Thickness\nInput a value to define the end thickness for the template.\nEnd Offset from Front\nInput a value to define the gap between the front of the tread to the end plates.\nTo remove the end offset from front element from the template, click to clear the Included check box.\nEnd Offset from Back\nInput a value to define the gap between the back of the tread to the end plates.\nTo remove the end offset from back element from the template, click to clear the Included check box.\nEnd Chamfer\nInput a value to define the end chamfer for the template.\nTo remove the end chamfer element from the template, click to clear the Included check box.\nTread Bend Radius\nInput a value to define the tread bend radius for the template.\nTo remove the tread bend radius element from the template, click to clear the Included check box.\n\n\n\nTread Template Profiles\nCreate Tread Template\nTread Width\nVariable\nDefault\nFixed\nValue\nTread Depth\nVariable\nDefault\nFixed\nValue\nTread Thickness\nBack Height\nBack Thickness\nFront Height\nFront Thickness\nEnd Height\nEnd Thickness\nEnd Offset from Front\nIncluded\nEnd Offset from Back\nIncluded\nEnd Chamfer\nIncluded\nTread Bend Radius\nIncluded\nNext\nProfiles\nCreate Tread Template\nTread Template Profiles\nBack\nParameters\nCreate Tread Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Tread Template Profiles", "Content": "The Profiles part of the Create Tread Template window allows the administrator to define the Profiles used in the tread template. The profiles are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nThe Profiles list displays all of the profiles available for the template. The administrator can add, remove and replace profiles. The currently selected profile displays in the 3D view.\nAdd\nClick to add a profile to the Profiles list.\nRemove\nClick to remove a profile from the Profiles list.\nReplace\nClick to replace the currently selected profile in the Profiles list.\nSpecification\nClick Select to display the Profile for tread template window.\nThe functionality available from the Profile for tread template window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nThe selected Profile Type and Profile Size values display in the Profile column of the Profiles list.\nThe selected P-Line Justification value displays in the Justification column of the Profiles list.\nAngle of Rotation\nInput a value to define the rotation angle for the profile.\nThe Angle of Rotation value displays in the Rotation column of the Profiles list.\nConfiguration\nSelect a configuration from the drop-down list to specify the profile type.\nThis is only a label, it does not affect the geometry of the profile. The selected Configuration value displays in the Description column of the Profiles list.\nStart Point\nSelect a start point from the drop-down list to define the start p-point position for the profile.\nThe selected Start Point value displays in the Start column of the Profiles list.\nEnd Point\nSelect an end point from the drop-down list to define the end p-point position for the profile.\nThe selected End Point value displays in the End column of the Profiles list.\nFlip\nClick Flip to display swap values of the Start Point and End Point drop-down lists.\nAdd\nClick to add a profile to the Profiles list.\nRemove\nClick to remove a profile from the Profiles list.\nReplace\nClick to replace the currently selected profile in the Profiles list.\nSpecification\nClick Select to display the Profile for tread template window.\nThe functionality available from the Profile for tread template window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nThe selected Profile Type and Profile Size values display in the Profile column of the Profiles list.\nThe selected P-Line Justification value displays in the Justification column of the Profiles list.\nAngle of Rotation\nInput a value to define the rotation angle for the profile.\nThe Angle of Rotation value displays in the Rotation column of the Profiles list.\nConfiguration\nSelect a configuration from the drop-down list to specify the profile type.\nThis is only a label, it does not affect the geometry of the profile. The selected Configuration value displays in the Description column of the Profiles list.\nStart Point\nSelect a start point from the drop-down list to define the start p-point position for the profile.\nThe selected Start Point value displays in the Start column of the Profiles list.\nEnd Point\nSelect an end point from the drop-down list to define the end p-point position for the profile.\nThe selected End Point value displays in the End column of the Profiles list.\nFlip\nClick Flip to display swap values of the Start Point and End Point drop-down lists.\nClick Next to display the Plates part of the Create Tread Template window. Refer to Tread Template Plates for further information.\nClick Back to return to the Parameters part of the Create Tread Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nAdd\nClick to add a profile to the Profiles list.\nRemove\nClick to remove a profile from the Profiles list.\nReplace\nClick to replace the currently selected profile in the Profiles list.\nSpecification\nClick Select to display the Profile for tread template window.\nThe functionality available from the Profile for tread template window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nThe selected Profile Type and Profile Size values display in the Profile column of the Profiles list.\nThe selected P-Line Justification value displays in the Justification column of the Profiles list.\nAngle of Rotation\nInput a value to define the rotation angle for the profile.\nThe Angle of Rotation value displays in the Rotation column of the Profiles list.\nConfiguration\nSelect a configuration from the drop-down list to specify the profile type.\nThis is only a label, it does not affect the geometry of the profile. The selected Configuration value displays in the Description column of the Profiles list.\nStart Point\nSelect a start point from the drop-down list to define the start p-point position for the profile.\nThe selected Start Point value displays in the Start column of the Profiles list.\nEnd Point\nSelect an end point from the drop-down list to define the end p-point position for the profile.\nThe selected End Point value displays in the End column of the Profiles list.\nFlip\nClick Flip to display swap values of the Start Point and End Point drop-down lists.\n\n\n\nHandrail Profile Specification\nTread Template Plates\nProfiles\nCreate Tread Template\nAdd\nRemove\nReplace\nSpecification\nSelect\nProfile for tread template\nTop Rail Specification\nHandrail Profile Specification\n\nAngle of Rotation\nConfiguration\nStart Point\nEnd Point\nFlip\nFlip\nNext\nPlates\nCreate Tread Template\nTread Template Plates\nBack\nParameters\nCreate Tread Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Tread Template Plates", "Content": "The Plates part of the Create Tread Template window allows the administrator to define the Plates used in the tread template. The plates are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nThe Plates list displays all of the plates available for the template. The administrator can add, remove and replace plates. The currently selected plate displays in the 3D view.\nAdd\nClick to add a plate to the Plates list.\nRemove\nClick to remove a plate from the Plates list.\nReplace\nClick to replace the currently selected plate in the Plates list.\nPlate Type\nSelect a type from the drop-down list to define the p-point positions of the plate.\nThe selected Plate Type values display in the Description and Points columns of the Plates list, the SLH application automatically updates the thickness and orientation to reflect the selected plate type.\nPlate Thickness\nThe Plate Thickness value displays in the Thickness column of the Plates list.\nPlate Orientation\nThe Plate Orientation value displays in the Orientation column of the Profiles list.\nAdd\nClick to add a plate to the Plates list.\nRemove\nClick to remove a plate from the Plates list.\nReplace\nClick to replace the currently selected plate in the Plates list.\nPlate Type\nSelect a type from the drop-down list to define the p-point positions of the plate.\nThe selected Plate Type values display in the Description and Points columns of the Plates list, the SLH application automatically updates the thickness and orientation to reflect the selected plate type.\nPlate Thickness\nThe Plate Thickness value displays in the Thickness column of the Plates list.\nPlate Orientation\nThe Plate Orientation value displays in the Orientation column of the Profiles list.\nClick Build Template to create the tread template.\nClick Back to return to the Profiles part of the Create Tread Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nThe Template element displays in the Model Explorer and the 3D view.\n\nAdd\nClick to add a plate to the Plates list.\nRemove\nClick to remove a plate from the Plates list.\nReplace\nClick to replace the currently selected plate in the Plates list.\nPlate Type\nSelect a type from the drop-down list to define the p-point positions of the plate.\nThe selected Plate Type values display in the Description and Points columns of the Plates list, the SLH application automatically updates the thickness and orientation to reflect the selected plate type.\nPlate Thickness\nThe Plate Thickness value displays in the Thickness column of the Plates list.\nPlate Orientation\nThe Plate Orientation value displays in the Orientation column of the Profiles list.\n\n\n\nPlates\nCreate Tread Template\nAdd\nRemove\nReplace\nPlate Type\nPlate Thickness\nPlate Orientation\nBuild Template\nBack\nProfiles\nCreate Tread Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Modify Tread Template", "Content": "To modify a Tread Template element, from the Templates part of the SLH Administration Tasks window, click the Treads drop-down list to display the list of available Treads which can be modified. Select the Tread to be modified, then select Modify to display the Modify Tread Template window.\n\nThe functionality of the Modify Tread Template window is identical to the Create Tread Template window. Refer to Create Tread Template for further information.\n\n\n\nCreate Tread Template\nTemplates\nSLH Administration Tasks\nTreads\nModify\nModify Tread Template\nModify Tread Template\nCreate Tread Template\nCreate Tread Template"}
{"Headers": "Delete Tread Template", "Content": "To delete a Tread Template element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Copy Tread Template", "Content": "Copying an existing Tread Template provides a quick and efficient method of creating new templates and editing the properties in the SLH Administration Tasks window.\nTo create a new Tread Template element from an existing element make sure the correct Tread Template element is selected in the Model Explorer.\nTo copy an existing Tread Template element, right-click and select Copy from the drop-down list.\nTo paste a copy of the Tread Template element, right-click and select Paste from the drop-down list.\nTo rename the pasted Tread Template element, right-click and select Rename from the drop-down list to display the Name window. Refer to Common Functionality User Guide for further information.\nThe copied element displays in the SLH Administration Tasks window.\n\n\n\nSLH Administration Tasks\nCopy\nPaste\nRename\nName\nCommon Functionality User Guide\nSLH Administration Tasks"}
{"Headers": "Create Post Template", "Content": "Post templates are used in the creation of handrails. The allowable posts are defined in the defaults by referencing post parts. Post parts are created in the PARAGON module. Refer to Catalog and Specifications User Guide for further information. Post parts reference either catalog or template posts.\nTo create a Post Template element make sure the correct Area element is selected in the Templates part of the SLH Administration Tasks window.\nTo create a Post Template element, from the Templates part of the SLH Administration Tasks window, click Create next to the Post drop-down list to display the Create Post Template window.\n\nNote:\nAll mandatory parts of the Create Post Template window are indicated with an amber triangle. The SLH application replaces the amber triangle with a green tick when the Create Post Template window has been populated with the required data.\n\n\n\nCatalog and Specifications User Guide\nTemplates\nSLH Administration\nTasks\nTemplates\nSLH Administration Tasks\nCreate\nCreate Post Template\nNote\n:\nCreate Post Template\nCreate Post Template"}
{"Headers": "Post Template Parameters", "Content": "The Parameters part of the Create Post Template window allows the administrator to define the Post Template dimensions.\n\nPost Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Vertical Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Horizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail Height\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail Height\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nTo remove the mounting plate thickness element from the template, click to clear the Included check box.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nTo remove the mounting plate width element from the template, click to clear the Included check box.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nTo remove the mounting plate length element from the template, click to clear the Included check box.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\nTo remove the extension plate thickness element from the template, click to clear the Included check box.\nPost Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Vertical Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Horizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail Height\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail Height\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nTo remove the mounting plate thickness element from the template, click to clear the Included check box.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nTo remove the mounting plate width element from the template, click to clear the Included check box.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nTo remove the mounting plate length element from the template, click to clear the Included check box.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\nTo remove the extension plate thickness element from the template, click to clear the Included check box.\nThe diagram below illustrates the Post Template dimensions as an example:\n\nClick Next to display the Profiles part of the Create Post Template window. Refer to Post Template Profiles for further information.\nClick Back to return to the General part of the Create Post Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nPost Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Vertical Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Horizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail Height\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail Height\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nTo remove the mounting plate thickness element from the template, click to clear the Included check box.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nTo remove the mounting plate width element from the template, click to clear the Included check box.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nTo remove the mounting plate length element from the template, click to clear the Included check box.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\nTo remove the extension plate thickness element from the template, click to clear the Included check box.\n\n\n\nPost Template Profiles\nParameters\nCreate Post Template\nPost Length\nVariable\nDefault\nFixed\nValue\nBottom Vertical Offset\nVariable\nDefault\nFixed\nValue\nBottom Horizontal Offset\nVariable\nDefault\nFixed\nValue\nExtension Length\nVariable\nDefault\nFixed\nValue\nExtension Plate Depth\nVariable\nDefault\nFixed\nValue\nUpper Intermediate Rail Height\nIncluded\nLower Intermediate Rail Height\nIncluded\nMounting Plate Thickness\nIncluded\nMounting Plate Width\nIncluded\nMounting Plate Length\nIncluded\nExtension Plate Thickness\nIncluded\nNext\nProfiles\nCreate Post Template\nPost Template Profiles\nBack\nGeneral\nCreate Post Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Post Template Profiles", "Content": "The Profiles part of the Create Post Template window allows the administrator to define the Profiles used in the post template. The profiles are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nThe functionality of the Profiles part of the Create Post Template window is identical to the Profiles part of the Create Tread Template window. Refer to Tread Template Profiles for further information.\nClick Next to display the Plates part of the Create Post Template window. Refer to Post Template Plates for further information.\nClick Back to return to the Parameters part of the Create Post Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nTread Template Profiles\nPost Template Plates\nProfiles\nCreate Post Template\nProfiles\nCreate Post Template\nProfiles\nCreate Tread Template\nTread Template Profiles\nNext\nPlates\nCreate Post Template\nPost Template Plates\nBack\nParameters\nCreate Post Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Post Template Plates", "Content": "The Plates part of the Create Post Template window allows the administrator to define the Plates used in the post template. The plates are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nThe functionality of the Plates part of the Create Post Template window is identical to the Plates part of the Create Tread Template window. Refer to Tread Template Plates for further information.\nClick Build Template to create the post template.\nClick Back to return to the Profiles part of the Create Post Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nThe Template element displays in the Model Explorer and the 3D view.\n\n\n\n\nTread Template Plates\nPlates\nCreate Post Template\nPlates\nCreate Post Template\nPlates\nCreate Tread Template\nTread Template Plates\nBuild Template\nBack\nProfiles\nCreate Post Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Modify Post Template", "Content": "To modify a Post Template element, from the Templates part of the SLH Administration Tasks window, click the Posts drop-down list to display the list of available Posts which can be modified. Select the Post to be modified, then select Modify to display the Modify Post Template window.\n\nThe functionality of the Modify Post Template window is identical to the Create Post Template window. Refer to Create Post Template for further information.\n\n\n\nCreate Post Template\nTemplates\nSLH Administration Tasks\nPosts\nModify\nModify Post Template\nModify Post Template\nCreate Post Template\nCreate Post Template"}
{"Headers": "Delete Post Template", "Content": "To delete a Post Template element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Copy Post Template", "Content": "Copying an existing Post Template provides a quick and efficient method of creating new templates and editing the properties in the SLH Administration Tasks window.\nTo create a new Post Template element from an existing element make sure the correct Post Template element is selected in the Model Explorer.\nTo copy an existing Post Template element, right-click and select Copy from the drop-down list.\nTo paste a copy of the Post Template element, right-click and select Paste from the drop-down list.\nTo rename the pasted Post Template element, right-click and select Rename from the drop-down list to display the Name window. Refer to Common Functionality User Guide for further information.\nThe copied element displays in the SLH Administration Tasks window.\n\n\n\nSLH Administration Tasks\nCopy\nPaste\nRename\nName\nCommon Functionality User Guide\nSLH Administration Tasks"}
{"Headers": "Create Handrail Gate Template", "Content": "Gate templates are used in the creation of handrails. The allowable gates are defined in the defaults by referencing gate parts. Gate parts are created in the PARAGON module. Refer to the Catalog and Specifications User Guide for further information. Gate parts reference either catalog or template gates.\nTo create a Gate Template element make sure the correct Area element is selected in the Templates part of the SLH Administration Tasks window.\nTo create a Gate Template element, from the Templates part of the SLH Administration Tasks window, click Create next to the Handrail Gates drop-down list to display the Create Gate Template window.\n\nNote:\nAll mandatory parts of the Create Gate Template window are indicated with an amber triangle. The SLH application replaces the amber triangle with a green tick when the Create Gate Template window has been populated with the required data.\n\n\n\nCatalog and Specifications User Guide\nTemplates\nSLH Administration\nTasks\nTemplates\nSLH Administration Tasks\nCreate\nCreate Gate Template\nNote\n:\nCreate Gate Template\nCreate Gate Template"}
{"Headers": "Gate Template Parameters", "Content": "The Parameters part of the Create Gate Template window allows the administrator to define the Gate Template dimensions.\n\nTop Rail Height\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWidth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nHorizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nPlate Thickness\nInput a value to define the plate thickness for the template.\nTo remove the plate thickness element from the template, click to clear the Included check box.\nPlate Depth\nInput a value to define the plate depth for the template.\nTo remove the plate depth element from the template, click to clear the Included check box.\nLock Clearance\nInput a value to define the lock clearance for the template.\nTo remove the lock clearance element from the template, click to clear the Included check box.\nHinge Clearance\nInput a value to define the hinge clearance for the template.\nTo remove the hinge clearance element from the template, click to clear the Included check box.\nBottom Clearance\nInput a value to define the bottom clearance for the template.\nTo remove the bottom clearance element from the template, click to clear the Included check box.\nTop Rail Height\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWidth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nHorizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nPlate Thickness\nInput a value to define the plate thickness for the template.\nTo remove the plate thickness element from the template, click to clear the Included check box.\nPlate Depth\nInput a value to define the plate depth for the template.\nTo remove the plate depth element from the template, click to clear the Included check box.\nLock Clearance\nInput a value to define the lock clearance for the template.\nTo remove the lock clearance element from the template, click to clear the Included check box.\nHinge Clearance\nInput a value to define the hinge clearance for the template.\nTo remove the hinge clearance element from the template, click to clear the Included check box.\nBottom Clearance\nInput a value to define the bottom clearance for the template.\nTo remove the bottom clearance element from the template, click to clear the Included check box.\nThe diagram below illustrates the Gate Template dimensions as an example:\n\nClick Next to display the Profiles part of the Create Gate Template window. Refer to Gate Template Profiles for further information.\nClick Back to return to the General part of the Create Gate Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nTop Rail Height\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWidth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nHorizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nPlate Thickness\nInput a value to define the plate thickness for the template.\nTo remove the plate thickness element from the template, click to clear the Included check box.\nPlate Depth\nInput a value to define the plate depth for the template.\nTo remove the plate depth element from the template, click to clear the Included check box.\nLock Clearance\nInput a value to define the lock clearance for the template.\nTo remove the lock clearance element from the template, click to clear the Included check box.\nHinge Clearance\nInput a value to define the hinge clearance for the template.\nTo remove the hinge clearance element from the template, click to clear the Included check box.\nBottom Clearance\nInput a value to define the bottom clearance for the template.\nTo remove the bottom clearance element from the template, click to clear the Included check box.\n\n\n\nGate Template Profiles\nParameters\nCreate Gate Template\nTop Rail Height\nVariable\nDefault\nFixed\nValue\nWidth\nVariable\nDefault\nFixed\nValue\nHorizontal Offset\nVariable\nDefault\nFixed\nValue\nUpper Intermediate Rail\nIncluded\nLower Intermediate Rail\nIncluded\nPlate Thickness\nIncluded\nPlate Depth\nIncluded\nLock Clearance\nIncluded\nHinge Clearance\nIncluded\nBottom Clearance\nIncluded\nNext\nProfiles\nCreate Gate Template\nGate Template Profiles\nBack\nGeneral\nCreate Gate Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Gate Template Profiles", "Content": "The Profiles part of the Create Gate Template window allows the administrator to define the Profiles used in the gate template. The profiles are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nAdd\nClick to add a profile to the Profiles list.\nRemove\nClick to remove a profile from the Profiles list.\nReplace\nClick to replace the currently selected profile in the Profiles list.\nSpecification\nClick Select to display the Profile for gate template window.\nThe functionality available from the Profile for gate template window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nThe selected Profile Type and Profile Size values display in the Profile column of the Profiles list.\nThe selected P-Line Justification value displays in the Justification column of the Profiles list.\nAngle of Rotation\nInput a value to define the rotation angle for the profile.\nThe Angle of Rotation value displays in the Rotation column of the Profiles list.\nBend Radius\nInput a value to define the bend radius for the profile.\nThe Bend Radius value displays in the Radius column of the Profiles list.\nIf there are three or more points, point two will be radiused. If there are five points, point four will also be radiused.\nConfiguration\nSelect a configuration from the drop-down list to specify the profile type.\nThe selected Configuration value displays in the Description column of the Profiles list.\nFirst Point\nSelect a first point from the drop-down list to define the first p-point position for the profile.\nThe selected First Point value displays in the first numbered column of the Profiles list.\nSecond Point\nSelect a second point from the drop-down list to define the second p-point position for the profile.\nThe selected Second Point value displays in the second numbered column of the Profiles list.\nThird Point\nSelect a third point from the drop-down list to define the third p-point position for the profile.\nThe selected Third Point value displays in the third numbered column of the Profiles list.\nFourth Point\nSelect a fourth point from the drop-down list to define the fourth p-point position for the profile.\nThe selected Fourth Point value displays in the fourth numbered column of the Profiles list.\nFifth Point\nSelect a fifth point from the drop-down list to define the fifth p-point position for the profile.\nThe selected Fifth Point value displays in the fifth numbered column of the Profiles list.\nFlip\nClick Flip to reverse the order of the defined points.\nAdd\nClick to add a profile to the Profiles list.\nRemove\nClick to remove a profile from the Profiles list.\nReplace\nClick to replace the currently selected profile in the Profiles list.\nSpecification\nClick Select to display the Profile for gate template window.\nThe functionality available from the Profile for gate template window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nThe selected Profile Type and Profile Size values display in the Profile column of the Profiles list.\nThe selected P-Line Justification value displays in the Justification column of the Profiles list.\nAngle of Rotation\nInput a value to define the rotation angle for the profile.\nThe Angle of Rotation value displays in the Rotation column of the Profiles list.\nBend Radius\nInput a value to define the bend radius for the profile.\nThe Bend Radius value displays in the Radius column of the Profiles list.\nIf there are three or more points, point two will be radiused. If there are five points, point four will also be radiused.\nConfiguration\nSelect a configuration from the drop-down list to specify the profile type.\nThe selected Configuration value displays in the Description column of the Profiles list.\nFirst Point\nSelect a first point from the drop-down list to define the first p-point position for the profile.\nThe selected First Point value displays in the first numbered column of the Profiles list.\nSecond Point\nSelect a second point from the drop-down list to define the second p-point position for the profile.\nThe selected Second Point value displays in the second numbered column of the Profiles list.\nThird Point\nSelect a third point from the drop-down list to define the third p-point position for the profile.\nThe selected Third Point value displays in the third numbered column of the Profiles list.\nFourth Point\nSelect a fourth point from the drop-down list to define the fourth p-point position for the profile.\nThe selected Fourth Point value displays in the fourth numbered column of the Profiles list.\nFifth Point\nSelect a fifth point from the drop-down list to define the fifth p-point position for the profile.\nThe selected Fifth Point value displays in the fifth numbered column of the Profiles list.\nFlip\nClick Flip to reverse the order of the defined points.\nClick Next to display the Plates part of the Create Gate Template window. Refer to Gate Template Plates for further information.\nClick Back to return to the Parameters part of the Create Gate Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nAdd\nClick to add a profile to the Profiles list.\nRemove\nClick to remove a profile from the Profiles list.\nReplace\nClick to replace the currently selected profile in the Profiles list.\nSpecification\nClick Select to display the Profile for gate template window.\nThe functionality available from the Profile for gate template window is identical to that available from the Top Rail Specification window. Refer to Handrail Profile Specification for further information.\nThe selected Profile Type and Profile Size values display in the Profile column of the Profiles list.\nThe selected P-Line Justification value displays in the Justification column of the Profiles list.\nAngle of Rotation\nInput a value to define the rotation angle for the profile.\nThe Angle of Rotation value displays in the Rotation column of the Profiles list.\nBend Radius\nInput a value to define the bend radius for the profile.\nThe Bend Radius value displays in the Radius column of the Profiles list.\nIf there are three or more points, point two will be radiused. If there are five points, point four will also be radiused.\nConfiguration\nSelect a configuration from the drop-down list to specify the profile type.\nThe selected Configuration value displays in the Description column of the Profiles list.\nFirst Point\nSelect a first point from the drop-down list to define the first p-point position for the profile.\nThe selected First Point value displays in the first numbered column of the Profiles list.\nSecond Point\nSelect a second point from the drop-down list to define the second p-point position for the profile.\nThe selected Second Point value displays in the second numbered column of the Profiles list.\nThird Point\nSelect a third point from the drop-down list to define the third p-point position for the profile.\nThe selected Third Point value displays in the third numbered column of the Profiles list.\nFourth Point\nSelect a fourth point from the drop-down list to define the fourth p-point position for the profile.\nThe selected Fourth Point value displays in the fourth numbered column of the Profiles list.\nFifth Point\nSelect a fifth point from the drop-down list to define the fifth p-point position for the profile.\nThe selected Fifth Point value displays in the fifth numbered column of the Profiles list.\nFlip\nClick Flip to reverse the order of the defined points.\n\n\n\nHandrail Profile Specification\nGate Template Plates\nProfiles\nCreate Gate Template\nAdd\nRemove\nReplace\nSpecification\nSelect\nProfile for gate template\nProfile for gate template\nTop Rail Specification\nHandrail Profile Specification\n\nAngle of Rotation\nBend Radius\nConfiguration\nFirst Point\nSecond Point\nThird Point\nFourth Point\nFifth Point\nFlip\nFlip\nNext\nPlates\nCreate Gate Template\nGate Template Plates\nBack\nParameters\nCreate Gate Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Gate Template Plates", "Content": "The Plates part of the Create Gate Template window allows the administrator to define the Plates used in the gate template. The plates are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nThe Plates list displays all of the plates available for the template. The administrator can add, remove and replace plates. The currently selected plate displays in the 3D view.\nAdd\nClick to add a plate to the Plates list.\nRemove\nClick to remove a plate from the Plates list.\nReplace\nClick to replace the currently selected plate in the Plates list.\nPlate Thickness\nSelect a thickness from the drop-down list to define the thickness of the plate.\nThe selected Plate Thickness value displays in the Thickness column of the Plates list.\nPlate Type\nSelect a type from the drop-down list to define the p-point positions of the plate.\nThe selected Plate Type values display in the Description and Points columns of the Plates list, the SLH application automatically updates the thickness and orientation to reflect the selected plate type.\nPlate Orientation\nSelect an orientation from the drop-down list to define the orientation of the plate.\nThe selected Plate Orientation value displays in the Orientation column of the Profiles list.\nAdd\nClick to add a plate to the Plates list.\nRemove\nClick to remove a plate from the Plates list.\nReplace\nClick to replace the currently selected plate in the Plates list.\nPlate Thickness\nSelect a thickness from the drop-down list to define the thickness of the plate.\nThe selected Plate Thickness value displays in the Thickness column of the Plates list.\nPlate Type\nSelect a type from the drop-down list to define the p-point positions of the plate.\nThe selected Plate Type values display in the Description and Points columns of the Plates list, the SLH application automatically updates the thickness and orientation to reflect the selected plate type.\nPlate Orientation\nSelect an orientation from the drop-down list to define the orientation of the plate.\nThe selected Plate Orientation value displays in the Orientation column of the Profiles list.\nClick Build Template to create the gate template.\nClick Back to return to the Profiles part of the Create Gate Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nThe Template element displays in the Model Explorer and the 3D view.\n\nAdd\nClick to add a plate to the Plates list.\nRemove\nClick to remove a plate from the Plates list.\nReplace\nClick to replace the currently selected plate in the Plates list.\nPlate Thickness\nSelect a thickness from the drop-down list to define the thickness of the plate.\nThe selected Plate Thickness value displays in the Thickness column of the Plates list.\nPlate Type\nSelect a type from the drop-down list to define the p-point positions of the plate.\nThe selected Plate Type values display in the Description and Points columns of the Plates list, the SLH application automatically updates the thickness and orientation to reflect the selected plate type.\nPlate Orientation\nSelect an orientation from the drop-down list to define the orientation of the plate.\nThe selected Plate Orientation value displays in the Orientation column of the Profiles list.\n\n\n\nPlates\nCreate Gate Template\nAdd\nRemove\nReplace\nPlate Thickness\nPlate Type\nPlate Orientation\nBuild Template\nBack\nProfiles\nCreate Gate Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Modify Handrail Gate Template", "Content": "To modify a Gate Template element, from the Templates part of the SLH Administration Tasks window, click the Handrail Gates drop-down list to display the list of available Gates which can be modified. Select the Gate to be modified, then select Modify to display the Modify Gate Template window.\n\nThe functionality of the Modify Gate Template window is identical to the Create Gate Template window. Refer to Create Handrail Gate Template for further information.\n\n\n\nCreate Handrail Gate Template\nTemplates\nSLH Administration Tasks\nHandrail Gates\nModify\nModify Gate Template\nModify Gate Template\nCreate Gate Template\nCreate Handrail Gate Template"}
{"Headers": "Delete Handrail Gate Template", "Content": "To delete a Gate Template element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Copy Handrail Gate Template", "Content": "Copying an existing Gate Template provides a quick and efficient method of creating new templates and editing the properties in the SLH Administration Tasks window.\nTo create a new Gate Template element from an existing element make sure the correct Gate Template element is selected in the Model Explorer.\nTo copy an existing Gate Template element, right-click and select Copy from the drop-down list.\nTo paste a copy of the Gate Template element, right-click and select Paste from the drop-down list.\nTo rename the pasted Gate Template element, right-click and select Rename from the drop-down list to display the Name window. Refer to Common Functionality User Guide for further information.\nThe copied element displays in the SLH Administration Tasks window.\n\n\n\nSLH Administration Tasks\nCopy\nPaste\nRename\nName\nCommon Functionality User Guide\nSLH Administration Tasks"}
{"Headers": "Create Termination Template", "Content": "Termination templates are used in the creation of handrails. The allowable terminations are defined in the defaults by referencing termination parts. Termination parts are created in the PARAGON module. Refer to Catalog and Specifications User Guide for further information. Termination parts reference either catalog or template terminations.\nTo create a Termination Template element make sure the correct Area element is selected in the Templates part of the SLH Administration Tasks window.\nTo create a Termination Template element, from the Templates part of the SLH Administration Tasks window, click Create next to the Terminations drop-down list to display the Create Termination Template window.\n\nNote:\nAll mandatory parts of the Create Termination Template window are indicated with an amber triangle. The SLH application replaces the amber triangle with a green tick when the Create Termination Template window has been populated with the required data.\n\n\n\nCatalog and Specifications User Guide\nTemplates\nSLH Administration\nTasks\nTemplates\nSLH Administration Tasks\nCreate\nCreate Termination Template\nNote\n:\nCreate Termination Template\nCreate Termination Template"}
{"Headers": "Termination Template Parameters", "Content": "The Parameters part of the Create Termination Template window allows the administrator to define the Termination Template dimensions.\n\nTop Rail Height\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWidth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nHorizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nPlate Thickness\nInput a value to define the plate thickness for the template.\nTo remove the plate thickness element from the template, click to clear the Included check box.\nPlate Depth\nInput a value to define the plate depth for the template.\nTo remove the plate depth element from the template, click to clear the Included check box.\nPlate Width\nInput a value to define the plate width for the template.\nTo remove the plate width element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\nTop Rail Height\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWidth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nHorizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nPlate Thickness\nInput a value to define the plate thickness for the template.\nTo remove the plate thickness element from the template, click to clear the Included check box.\nPlate Depth\nInput a value to define the plate depth for the template.\nTo remove the plate depth element from the template, click to clear the Included check box.\nPlate Width\nInput a value to define the plate width for the template.\nTo remove the plate width element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\nThe diagram below illustrates the Termination Template dimensions as an example:\n\nClick Next to display the Profiles part of the Create Termination Template window. Refer to Termination Template Profiles for further information.\nClick Back to return to the General part of the Create Termination Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nTop Rail Height\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWidth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nHorizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nPlate Thickness\nInput a value to define the plate thickness for the template.\nTo remove the plate thickness element from the template, click to clear the Included check box.\nPlate Depth\nInput a value to define the plate depth for the template.\nTo remove the plate depth element from the template, click to clear the Included check box.\nPlate Width\nInput a value to define the plate width for the template.\nTo remove the plate width element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\n\n\n\nTermination Template Profiles\nParameters\nCreate Termination Template\nTop Rail Height\nVariable\nDefault\nFixed\nValue\nWidth\nVariable\nDefault\nFixed\nValue\nHorizontal Offset\nVariable\nDefault\nFixed\nValue\nExtension Length\nVariable\nDefault\nFixed\nValue\nExtension Plate Depth\nVariable\nDefault\nFixed\nValue\nUpper Intermediate Rail\nIncluded\nLower Intermediate Rail\nIncluded\nPlate Thickness\nIncluded\nPlate Depth\nIncluded\nPlate Width\nIncluded\nMounting Plate Thickness\nMounting Plate Width\nMounting Plate Length\nExtension Plate Thickness\nNext\nProfiles\nCreate Termination Template\nTermination Template Profiles\nBack\nGeneral\nCreate Termination Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Termination Template Profiles", "Content": "The Profiles part of the Create Termination Template window allows the administrator to define the Profiles used in the termination template. The profiles are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nThe functionality of the Profiles part of the Create Termination Template window is identical to the Profiles part of the Create Gate Template window. Refer to Gate Template Profiles for further information.\nClick Next to display the Plates part of the Create Termination Template window. Refer to Termination Template Plates for further information.\nClick Back to return to the Parameters part of the Create Termination Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nGate Template Profiles\nTermination Template Plates\nProfiles\nCreate Termination Template\nProfiles\nCreate Termination Template\nProfiles\nCreate Gate Template\nGate Template Profiles\nNext\nPlates\nCreate Termination Template\nTermination Template Plates\nBack\nParameters\nCreate Termination Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Termination Template Plates", "Content": "The Plates part of the Create Termination Template window allows the administrator to define the Plates used in the termination template. The plates are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nThe functionality of the Plates part of the Create Termination Template window is identical to the Plates part of the Create Tread Template window. Refer to Tread Template Plates for further information.\nClick Build Template to create the termination template.\nClick Back to return to the Profiles part of the Create Termination Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nThe Template element displays in the Model Explorer and the 3D view.\n\n\n\n\nTread Template Plates\nPlates\nCreate Termination Template\nPlates\nCreate Termination Template\nCreate Tread Template\nTread Template Plates\nBuild Template\nBack\nProfiles\nCreate Termination Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Modify Termination Template", "Content": "To modify a Termination Template element, from the Templates part of the SLH Administration Tasks window, click the Terminations drop-down list to display the list of available Terminations which can be modified. Select the Termination to be modified, then select Modify to display the Modify Termination Template window.\n\nThe functionality of the Modify Termination Template window is identical to the Create Termination Template window. Refer to Create Termination Template for further information.\n\n\n\nCreate Termination Template\nTemplates\nSLH Administration Tasks\nTerminations\nModify\nModify Termination Template\nModify Termination Template\nCreate Termination Template\nCreate Termination Template"}
{"Headers": "Delete Termination Template", "Content": "To delete a Termination Template element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Copy Termination Template", "Content": "Copying an existing Termination Template provides a quick and efficient method of creating new templates and editing the properties in the SLH Administration Tasks window.\nTo create a new Termination Template element from an existing element make sure the correct Termination Template element is selected in the Model Explorer.\nTo copy an existing Termination Template element, right-click and select Copy from the drop-down list.\nTo paste a copy of the Termination Template element, right-click and select Paste from the drop-down list.\nTo rename the pasted Termination Template element, right-click and select Rename from the drop-down list to display the Name window. Refer to Common Functionality User Guide for further information.\nThe copied element displays in the SLH Administration Tasks window.\n\n\n\nSLH Administration Tasks\nCopy\nPaste\nRename\nName\nCommon Functionality User Guide\nSLH Administration Tasks"}
{"Headers": "Create Handrail Panel Template", "Content": "Panel templates are used in the creation of handrails. The allowable panels are defined in the defaults by referencing panel parts. Panel parts are created in the PARAGON module. Refer to Catalog and Specifications User Guide for further information. Panel parts reference either catalog or template handrails.\nTo create a Panel Template element make sure the correct Area element is selected in the Templates part of the SLH Administration Tasks window.\nTo create a Panel Template element, from the Templates part of the SLH Administration Tasks window, click Create next to the Handrail Panels drop-down list to display the Create Panel Template window.\n\nNote:\nAll mandatory parts of the Create Panel Template window are indicated with an amber triangle. The SLH application replaces the amber triangle with a green tick when the Create Panel Template window has been populated with the required data.\n\n\n\nCatalog and Specifications User Guide\nTemplates\nSLH Administration\nTasks\nTemplates\nSLH Administration Tasks\nCreate\nCreate Panel Template\nNote\n:\nCreate Panel Template\nCreate Panel Template"}
{"Headers": "Panel Template Mandatory Parameters", "Content": "The Mandatory Parameters part of the Create Panel Template window allows the administrator to define the required Panel Template dimensions.\n\nPanel Length\nSelect the Variable radio button to input a value in the Default field. The administrator is also required to input a value in the Minimum and Maximum fields to define the minimum and maximum allowable panel length dimensions. The post spacing is recalculated when a value is entered.\nSelect the Fixed radio button to input a Fixed value in the Value field. The minimum and maximum values are equal and the fields are not available for modification.\nPost Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Vertical Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Horizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWing Length\nSelect the Variable radio button to input a Default value in the Default field. The panel length is calculated again once a value is entered into the field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nPost Spacing\nInput a value to define the post spacing for the template. The panel length is recalculated based on the wing length and the number of posts.\nPanel Length\nSelect the Variable radio button to input a value in the Default field. The administrator is also required to input a value in the Minimum and Maximum fields to define the minimum and maximum allowable panel length dimensions. The post spacing is recalculated when a value is entered.\nSelect the Fixed radio button to input a Fixed value in the Value field. The minimum and maximum values are equal and the fields are not available for modification.\nPost Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Vertical Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Horizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWing Length\nSelect the Variable radio button to input a Default value in the Default field. The panel length is calculated again once a value is entered into the field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nPost Spacing\nInput a value to define the post spacing for the template. The panel length is recalculated based on the wing length and the number of posts.\nThe diagram below illustrates the Panel Template dimensions as an example:\n\nClick Next to display the Optional Parameters part of the Create Panel Template window. Refer to Panel Template Optional Parameters for further information.\nClick Back to return to the General part of the Create Panel Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nPanel Length\nSelect the Variable radio button to input a value in the Default field. The administrator is also required to input a value in the Minimum and Maximum fields to define the minimum and maximum allowable panel length dimensions. The post spacing is recalculated when a value is entered.\nSelect the Fixed radio button to input a Fixed value in the Value field. The minimum and maximum values are equal and the fields are not available for modification.\nPost Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Vertical Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Horizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWing Length\nSelect the Variable radio button to input a Default value in the Default field. The panel length is calculated again once a value is entered into the field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nPost Spacing\nInput a value to define the post spacing for the template. The panel length is recalculated based on the wing length and the number of posts.\n\n\n\nPanel Template Optional Parameters\nMandatory Parameters\nCreate Panel Template\nPanel Length\nVariable\nDefault\nMinimum\nMaximum\nFixed\nValue\nPost Length\nVariable\nDefault\nFixed\nValue\nBottom Vertical Offset\nVariable\nDefault\nFixed\nValue\nBottom Horizontal Offset\nVariable\nDefault\nFixed\nValue\nExtension Length\nVariable\nDefault\nFixed\nValue\nExtension Plate Depth\nVariable\nDefault\nFixed\nValue\nWing Length\nVariable\nDefault\nFixed\nValue\nPost Spacing\nNext\nOptional Parameters\nCreate Panel Template\nPanel Template Optional Parameters\nBack\nGeneral\nCreate Panel Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Panel Template Optional Parameters", "Content": "The Optional Parameters part of the Create Panel Template window allows the administrator to define the optional Panel Template dimensions.\n\nUpper Intermediate Rail Height\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail Height\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nTo remove the mounting plate thickness element from the template, click to clear the Included check box.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nTo remove the mounting plate width element from the template, click to clear the Included check box.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nTo remove the mounting plate length element from the template, click to clear the Included check box.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\nTo remove the extension plate thickness element from the template, click to clear the Included check box.\nThe functionality is not available for top mounted handrail panel templates.\nRise\nInput a value to define the rise for the template.\nThe panel template rise is the vertical distance of the panel from the RPATH when a panel assembly is used on a slope.\nUpper Intermediate Rail Height\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail Height\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nTo remove the mounting plate thickness element from the template, click to clear the Included check box.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nTo remove the mounting plate width element from the template, click to clear the Included check box.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nTo remove the mounting plate length element from the template, click to clear the Included check box.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\nTo remove the extension plate thickness element from the template, click to clear the Included check box.\nThe functionality is not available for top mounted handrail panel templates.\nRise\nInput a value to define the rise for the template.\nThe panel template rise is the vertical distance of the panel from the RPATH when a panel assembly is used on a slope.\nThe diagram below illustrates the Panel Template dimensions as an example:\n\nClick Next to display the Profiles part of the Create Panel Template window. Refer to Panel Template Profiles for further information.\nClick Back to return to the Mandatory Parameters part of the Create Panel Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nUpper Intermediate Rail Height\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail Height\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nTo remove the mounting plate thickness element from the template, click to clear the Included check box.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nTo remove the mounting plate width element from the template, click to clear the Included check box.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nTo remove the mounting plate length element from the template, click to clear the Included check box.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\nTo remove the extension plate thickness element from the template, click to clear the Included check box.\nThe functionality is not available for top mounted handrail panel templates.\nRise\nInput a value to define the rise for the template.\nThe panel template rise is the vertical distance of the panel from the RPATH when a panel assembly is used on a slope.\n\n\n\nPanel Template Profiles\nOptional Parameters\nCreate Panel Template\nUpper Intermediate Rail Height\nIncluded\nLower Intermediate Rail Height\nIncluded\nMounting Plate Thickness\nIncluded\nMounting Plate Width\nIncluded\nMounting Plate Length\nIncluded\nExtension Plate Thickness\nIncluded\nRise\nNext\nProfiles\nCreate Panel Template\nPanel Template Profiles\nBack\nMandatory Parameters\nCreate Panel Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Panel Template Profiles", "Content": "The Profiles part of the Create Panel Template window allows the administrator to define the Profiles used in the panel template. The profiles are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nThe functionality of the Profiles part of the Create Panel Template window is identical to the Profiles part of the Create Gate Template window. Refer to Gate Template Profiles for further information.\nClick Next to display the Plates part of the Create Panel Template window. Refer to Panel Template Plates for further information.\nClick Back to return to the Optional Parameters part of the Create Panel Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nGate Template Profiles\nPanel Template Plates\nProfiles\nCreate Panel Template\nProfiles\nCreate Panel Template\nProfiles\nCreate Gate Template\nGate Template Profiles\nNext\nPlates\nCreate Panel Template\nPanel Template Plates\nBack\nOptional Parameters\nCreate Panel Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Panel Template Plates", "Content": "The Plates part of the Create Panel Template window allows the administrator to define the Plates used in the panel template. The plates are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nThe functionality of the Plates part of the Create Panel Template window is identical to the Plates part of the Create Gate Template window. Refer to Gate Template Plates for further information.\nClick Build Template to create the panel template.\nClick Back to return to the Profiles part of the Create Panel Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nThe Template element displays in the Model Explorer and the 3D view.\n\n\n\n\nGate Template Plates\nPlates\nCreate Panel Template\nPlates\nCreate Panel Template\nPlates\nCreate Gate Template\nGate Template Plates\nBuild Template\nBack\nProfiles\nCreate Panel Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Modify Handrail Panel Template", "Content": "To modify a Panel Template element, from the Templates part of the SLH Administration Tasks window, click the Handrail Panels drop-down list to display the list of available Handrail Panels which can be modified. Select the Handrail Panel to be modified, then select Modify to display the Modify Panel Template window.\n\nThe functionality of the Modify Panel Template window is identical to the Create Panel Template window. Refer to Create Handrail Panel Template for further information.\n\n\n\nCreate Handrail Panel Template\nTemplates\nSLH Administration Tasks\nHandrail Panels\nModify\nModify Panel Template\nModify Panel Template\nCreate Panel Template\nCreate Handrail Panel Template"}
{"Headers": "Delete Handrail Panel Template", "Content": "To delete a Panel Template element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Copy Handrail Panel Template", "Content": "Copying an existing Panel Template provides a quick and efficient method of creating new templates and editing the properties in the SLH Administration Tasks window.\nTo create a new Panel Template element from an existing element make sure the correct Panel Template element is selected in the Model Explorer.\nTo copy an existing Panel Template element, right-click and select Copy from the drop-down list.\nTo paste a copy of the Panel Template element, right-click and select Paste from the drop-down list.\nTo rename the pasted Panel Template element, right-click and select Rename from the drop-down list to display the Name window. Refer to Common Functionality User Guide for further information.\nThe copied element displays in the SLH Administration Tasks window.\n\n\n\nSLH Administration Tasks\nCopy\nPaste\nRename\nName\nCommon Functionality User Guide\nSLH Administration Tasks"}
{"Headers": "Create Rung Ladder Gate Template", "Content": "Rung ladder gate templates are used in the creation of rung ladders. The allowable gates are defined in the defaults by referencing gate parts. Gate parts are created in the PARAGON module. Refer to Catalog and Specifications User Guide for further information. Gate parts reference either catalogue or template gates.\nTo create a Rung Ladder Gate Template element make sure the correct Area element is selected in the Templates part of the SLH Administration Tasks window.\nTo create a Rung Ladder Gate Template element, from the Templates part of the SLH Administration Tasks window, click Create next to the Ladder Gates drop-down list to display the Create Rung Ladder Gate Template window.\n\nNote:\nAll mandatory parts of the Create Rung Ladder Gate Template window are indicated with an amber triangle. The SLH application replaces the amber triangle with a green tick when the Create Rung Ladder Gate Template window has been populated with the required data.\n\n\n\nCatalog and Specifications User Guide\nTemplates\nSLH Administration\nTasks\nTemplates\nSLH Administration Tasks\nCreate\nCreate Rung Ladder Gate Template\nNote\n:\nCreate Rung Ladder Gate Template\nCreate Rung Ladder Gate Template"}
{"Headers": "Rung Ladder Gate Template Parameters", "Content": "The Parameters part of the Create Rung Ladder Gate Template window allows the administrator to define the Rung Ladder Gate Template dimensions.\n\nTop Rail Height\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWidth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Horizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Vertical Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nPlate Thickness\nInput a value to define the plate thickness for the template.\nTo remove the mounting thickness element from the template, click to clear the Included check box.\nPlate Depth\nInput a value to define the plate depth for the template.\nTo remove the plate depth element from the template, click to clear the Included check box.\nLock Clearance\nInput a value to define the lock clearance for the template.\nTo remove the lock clearance element from the template, click to clear the Included check box.\nHinge Clearance\nInput a value to define the hinge clearance for the template.\nTo remove the hinge clearance element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nTo remove the mounting plate thickness element from the template, click to clear the Included check box.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nTo remove the mounting plate width element from the template, click to clear the Included check box.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nTo remove the mounting plate length element from the template, click to clear the Included check box.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\nTo remove the extension plate thickness element from the template, click to clear the Included check box.\nTop Rail Height\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWidth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Horizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Vertical Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nPlate Thickness\nInput a value to define the plate thickness for the template.\nTo remove the mounting thickness element from the template, click to clear the Included check box.\nPlate Depth\nInput a value to define the plate depth for the template.\nTo remove the plate depth element from the template, click to clear the Included check box.\nLock Clearance\nInput a value to define the lock clearance for the template.\nTo remove the lock clearance element from the template, click to clear the Included check box.\nHinge Clearance\nInput a value to define the hinge clearance for the template.\nTo remove the hinge clearance element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nTo remove the mounting plate thickness element from the template, click to clear the Included check box.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nTo remove the mounting plate width element from the template, click to clear the Included check box.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nTo remove the mounting plate length element from the template, click to clear the Included check box.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\nTo remove the extension plate thickness element from the template, click to clear the Included check box.\nThe diagram below illustrates the Rung Ladder Gate Template dimensions:\n\nClick Next to display the Profiles part of the Create Rung Ladder Gate Template window. Refer to Rung Ladder Gate Template Profiles for further information.\nClick Back to return to the General part of the Create Rung Ladder Gate Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nTop Rail Height\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nWidth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Horizontal Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nBottom Vertical Offset\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Length\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nExtension Plate Depth\nSelect the Variable radio button to input a Default value in the Default field.\nSelect the Fixed radio button to input a Fixed value in the Value field.\nUpper Intermediate Rail\nInput a value to define the upper intermediate rail height for the template.\nTo remove the upper intermediate rail height element from the template, click to clear the Included check box.\nLower Intermediate Rail\nInput a value to define the lower intermediate rail height for the template.\nTo remove the lower intermediate rail height element from the template, click to clear the Included check box.\nPlate Thickness\nInput a value to define the plate thickness for the template.\nTo remove the mounting thickness element from the template, click to clear the Included check box.\nPlate Depth\nInput a value to define the plate depth for the template.\nTo remove the plate depth element from the template, click to clear the Included check box.\nLock Clearance\nInput a value to define the lock clearance for the template.\nTo remove the lock clearance element from the template, click to clear the Included check box.\nHinge Clearance\nInput a value to define the hinge clearance for the template.\nTo remove the hinge clearance element from the template, click to clear the Included check box.\nMounting Plate Thickness\nInput a value to define the mounting plate thickness for the template.\nTo remove the mounting plate thickness element from the template, click to clear the Included check box.\nMounting Plate Width\nInput a value to define the mounting plate width for the template.\nTo remove the mounting plate width element from the template, click to clear the Included check box.\nMounting Plate Length\nInput a value to define the mounting plate length for the template.\nTo remove the mounting plate length element from the template, click to clear the Included check box.\nExtension Plate Thickness\nInput a value to define the extension plate thickness for the template.\nTo remove the extension plate thickness element from the template, click to clear the Included check box.\n\n\n\nRung Ladder Gate Template Profiles\nParameters\nCreate Rung Ladder Gate Template\nTop Rail Height\nVariable\nDefault\nFixed\nValue\nWidth\nVariable\nDefault\nFixed\nValue\nBottom Horizontal Offset\nVariable\nDefault\nFixed\nValue\nBottom Vertical Offset\nVariable\nDefault\nFixed\nValue\nExtension Length\nVariable\nDefault\nFixed\nValue\nExtension Plate Depth\nVariable\nDefault\nFixed\nValue\nUpper Intermediate Rail\nIncluded\nLower Intermediate Rail\nIncluded\nPlate Thickness\nIncluded\nPlate Depth\nIncluded\nLock Clearance\nIncluded\nHinge Clearance\nIncluded\nMounting Plate Thickness\nIncluded\nMounting Plate Width\nIncluded\nMounting Plate Length\nIncluded\nExtension Plate Thickness\nIncluded\nNext\nProfiles\nCreate Rung Ladder Gate Template\nRung Ladder Gate Template Profiles\nBack\nGeneral\nCreate Rung Ladder Gate Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Rung Ladder Gate Template Profiles", "Content": "The Profiles part of the Create Rung Ladder Gate Template window allows the administrator to define the Profiles used in the rung ladder gate template. The profiles are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nThe functionality of the Profiles part of the Create Ring Ladder Gate Template window is identical to the Profiles part of the Create Gate Template window. Refer to Gate Template Profiles for further information.\nClick Next to display the Plates part of the Create Rung Ladder Gate Template window. Refer to Rung Ladder Gate Template Plates for further information.\nClick Back to return to the Parameters part of the Create Rung Ladder Gate Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\n\n\n\nGate Template Profiles\nRung Ladder Gate Template Plates\nProfiles\nCreate Rung Ladder Gate Template\nProfiles\nCreate Ring Ladder Gate Template\nProfiles\nCreate Gate Template\nGate Template Profiles\nNext\nPlates\nCreate Rung Ladder Gate Template\nRung Ladder Gate Template Plates\nBack\nParameters\nCreate Rung Ladder Gate Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Rung Ladder Gate Template Plates", "Content": "The Plates part of the Create Rung Ladder Gate Template window allows the administrator to define the Plates used in the rung ladder gate template. The plates are positioned using p-points which are specified by the administrator. If a p-point is selected that requires the presence of a parameter, the SLH application includes the parameter by default.\n\nThe functionality of the Plates part of the Create Rung Ladder Gate Template window is identical to the Plates part of the Create Gate Template window. Refer to Gate Template Plates for further information.\nClick Build Template to create the rung ladder gate template.\nClick Back to return to the Profiles part of the Create Rung Ladder Gate Template window.\nClick Cancel to discard any inputs and return to the SLH Administration Tasks window.\nThe Template element displays in the Model Explorer and the 3D view.\n\n\n\n\nGate Template Plates\nPlates\nCreate Rung Ladder Gate Template\nPlates\nCreate Rung Ladder Gate Template\nPlates\nCreate Gate Template\nGate Template Plates\nBuild Template\nBack\nProfiles\nCreate Rung Ladder Gate Template\nCancel\nSLH Administration Tasks"}
{"Headers": "Modify Rung Ladder Gate Template", "Content": "To modify a Rung Ladder Gate Template element, from the Templates part of the SLH Administration Tasks window, click the Ladder Gates drop-down list to display the list of available Ladder Gates which can be modified. Select the Ladder Gate to be modified, then select Modify to display the Modify Rung Ladder Gate Template window.\n\nThe functionality of the Modify Rung Ladder Gate Template window is identical to the Create Rung Ladder Gate Template window. Refer to Create Rung Ladder Gate Template for further information.\n\n\n\nCreate Rung Ladder Gate Template\nTemplates\nSLH Administration Tasks\nLadder Gates\nModify\nModify Rung Ladder Gate Template\nModify Rung Ladder Gate Template\nCreate Rung Ladder Gate Template\nCreate Rung Ladder Gate Template"}
{"Headers": "Delete Rung Ladder Gate Template", "Content": "To delete a Rung Ladder Gate Template element, navigate to the item to be deleted in the Model Explorer, right-click the selection and select Delete from the drop-down list. A Confirm window displays asking the administrator to OK the deletion. Click Yes to delete the item.\n\n\n\nModel Explorer\nDelete\nConfirm\nOK\nYes"}
{"Headers": "Copy Rung Ladder Gate Template", "Content": "Copying an existing rung ladder gate template provides a quick and efficient method of creating new templates and editing the properties in the SLH Administration Tasks window.\nTo create a new Rung Ladder Gate Template element from an existing element make sure the correct Rung Ladder Gate Template element is selected in the Model Explorer.\nTo copy an existing Rung Ladder Gate Template element, right-click and select Copy from the drop-down list.\nTo paste a copy of the Rung Ladder Gate Template element, right-click and select Paste from the drop-down list.\nTo rename the pasted Rung Ladder Gate Template element, right-click and select Rename from the drop-down list to display the Name window. Refer to Common Functionality User Guide for further information.\nThe copied element displays in the SLH Administration Tasks window.\n\n\n\nSLH Administration Tasks\nCopy\nPaste\nRename\nName\nCommon Functionality User Guide\nSLH Administration Tasks"}
{"Headers": "Supports", "Content": "The Supports application is supplied as part of AVEVA E3D Design. The application is a powerful suite of facilities designed by engineers, for creating, analyzing and documenting logically interconnected support structures.\nThe Supports application allows you to create supports for piping, cable trays and HVAC. It is highly interactive, enabling you to design supports with the minimum of effort. The Supports application is also highly configurable, allowing the administrator to define project-related defaults, to control the design of supports, and to determine the range and types of ancillary components that can be used on a project.\nThe standard supports in the application are designed using structural sections and are template driven. A default set of structural templates based on British Standard steelwork sections is supplied with the Supports application. Any relevant national standard for steelwork sections can be used by configuring the supplied templates. Refer to Project Setup for further information.\nIf the templates supplied do not suit project or company requirements, the administrator may configure them. Alternatively, contact AVEVA Solutions to investigate the requirement.\nAncillaries are elements, such as u-bolts, bolt-on shoes, anchors, or slip-units, which are attached to pipes. Ancillaries associated with the templates are those suitable for, or available with the standard.\nAncillaries for cable trays and HVAC, sometimes referred to as fixings, are deemed to be the responsibility of the relevant contractor and are not dealt with in this application.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nProject Setup\nAVEVA E3D Design\nProject Setup"}
{"Headers": "Support Catalogs and Specifications", "Content": "The Supports application is supplied with a catalogue and specifications. The range of bores and components in the catalogue are fixed.\nThe /MDS-Ancillaries specification contains all ancillary types, and the /MDF-Structures specification contains the SREF attachments for standard frameworks.\nThe /MDP specification contains the preliminary support type available within the supports application.\nThe /RPAD-MDS-PLATE-MATERIAL specification contains the material used for reinforcing pad type supports.\nNote:\nThe catalogue and associated specifications must NOT be modified.\n\n\n\n/MDS-Ancillaries\n/MDF-Structures\n/MDP\n/RPAD-MDS-PLATE-MATERIAL\nNote\n:"}
{"Headers": "Supports", "Content": "Depending on the selections made from the Supports tab, you are presented with further windows prompting for input and options allowing for the workflow to continue.\nYou are not able to make any selections from the Supports tab if the correct database hierarchy has not been configured beforehand. For example certain support elements must reside below other elements in the database hierarchy.\n\n\n\nSupports\nSupports"}
{"Headers": "Design Features", "Content": "The Supports application allows you to build up and detail supports by selecting components from the MDS database.\nUsing standard default settings, a conceptual layout can be created and analyzed rapidly, leaving the design details to a later post-approved stage.\n\n\n"}
{"Headers": "Hierarchy", "Content": "All database elements are owned by other elements, therefore elements must be created in a strict order.\nThe following database elements are common to all Model disciplines:\nfor further information on the generic hierarchical structure and the design database, refer to How Data is Stored.\nWorld\nSite\nZone\nWorld\nWorld\nSite\nSite\nZone\nZone\n\n\n\nHow Data is Stored\nModel\nHow Data is Stored"}
{"Headers": "Supports Specific Hierarchy", "Content": "A support can be associated with a pipe, HVAC or cable tray element. By default, when a pipe, HVAC or cable tray element is added to the 3D view, all associated supports are also added to the display.\n\nBelow the Zone level in the Supports application, the support specific elements are:\n\nSupport (SUPPO)\nSupport (SUPPO) elements are administrative and can own Supcomp (SUPC), Structure (STRU), Trunnion (TRUNNI) and Hanger (HANG) elements.\nSupcomp (SUPC)\nSupcomp (SUPC) elements own Ancillary (ANCI) elements. For example, anchors or pipe shoes.\nAncillary (ANCI)\nAncillary (ANCI) elements are owned by SUPC elements. These elements dictate the ancillary components used for the support. For example, shoe, guide or stop elements.\nStructure (STRU)\nStructure (STRU) elements are owned by SUPPO elements and can own a number of Framework (FRMW) and Template (TMPL) elements.\nFramework (FRMW)\nFramework (FRMW) elements own Section (GENSEC) elements.\nSection (GENSEC)\nSection (GENSEC) elements are owned by FRMW elements. These elements dictate the shape and geometry of the support framework.\nTemplate (TMPL)\nTemplate (TMPL) elements contain the support template elements.\n\n\nTrunnion (TRUNNI)\nTrunnion (TRUNNI) elements are owned by SUPPO elements and can own a number of Trunnion Ancillary (TRANCI), Trunnion Reducer (TRREDU), Weld (WELD) and Plate (PLAT) elements. The TRUNNI element stores the head and tail position of the trunnion branch.\nTrunnion Ancillary (TRANCI)\nTrunnion Ancillary (TRANCI) elements own Specification Reference (SSREFE) elements. TRANCI elements dictate the trunnion ancillary elements that connect the trunnion to the pipe. For example, pipe rest or clamp elements.\nSpecification Reference (SSREFE)\nSpecification Reference (SSREFE) elements store the specification reference of the trunnion and the design parameters. For example, the height of the ancillary. The element is normally a hidden element and can only be queried from the command line.\nTrunnion Reducer (TRREDU)\nTrunnion Reducer (TRREDU) elements are owned by TRUNNI elements. These elements allow the trunnion to be set to a different bore than the branch being supported.\nWeld (WELD)\nWeld (WELD) elements are owned by TRUNNI elements. These elements store information about the welds that are associated with the trunnion.\nPlate (PLAT)\nPlate (PLAT) elements are owned by TRUNNI elements. These elements dictate the shape and geometry of the plates that are associated with the trunnion.\nHanger (HANG)\nHanger (HANG) elements are owned by SUPPO elements, a HANG element is created for each hanger assembly. For example, a variable spring or hanger rod. HANG elements can own a number of Variable Spring (VSPR), Hanger Rod (HROD), Hanger Nut (HNUT), Turnbuckle (TRNB), Rod Connection Plate (RCPL) and Hanger Ancillary (HANCI) and elements.\n\n\nVariable Spring (VSPR)\nVariable Spring (VSPR) elements are owned by HANG elements. These elements dictate the shape and geometry of the variable spring.\nHanger Rod (HROD)\nHanger (HANG) elements are owned by SUPPO elements, a HANG element is created for each hanger assembly. For example, a variable spring or hanger rod. HANG elements can own a number of Variable Spring (VSPR), Hanger Rod (HROD), Hanger Nut (HNUT), Turnbuckle (TRNB), Rod Connection Plate (RCPL) and Hanger Ancillary (HANCI) and elements.\nHanger Nut (HNUT)\nHanger Nut (HNUT) elements are owned by HANG elements. These elements dictate the shape and geometry of the hanger nut.\nTurnbuckle (TRNB)\nTurnbuckle (TRNB) elements are owned by HANG elements. These elements dictate the shape and geometry of the turnbuckle.\nRod Connection Plate (RCPL)\nRod Connection Plate (RCPL) elements are owned by HANG elements. These elements dictate the shape and geometry of the rod connection plate when the hanger is supported between two beams.\nHanger Ancillary (HANCI)\nHanger Ancillary (HANCI) elements are owned by HANG elements. These elements define the connectivity between the hanger end and the supporting structural element.\n\n\n\nSupport (SUPPO)\nSupcomp (SUPC)\nAncillary (ANCI)\nStructure (STRU)\nFramework (FRMW)\nSection (GENSEC)\nTemplate (TMPL)\nTrunnion (TRUNNI)\nTrunnion Ancillary (TRANCI)\nSpecification Reference (SSREFE)\nTrunnion Reducer (TRREDU)\nWeld (WELD)\nPlate (PLAT)\nHanger (HANG)\nVariable Spring (VSPR)\nHanger Rod (HROD)\nHanger Nut (HNUT)\nTurnbuckle (TRNB)\nRod Connection Plate (RCPL)\nHanger Ancillary (HANCI)"}
{"Headers": "Support Storage Area and Default Templates", "Content": "When entered, the Supports application searches for the existence of Support Application Data World (APPLDW) elements for framework templates, special templates and hanger templates. If they do not exist, entry to the application is stopped, an error message is displayed, and you can re-enter the General application. If this occurs, refer to the administrator.\nThe administrator controls the selection of which zones are displayed. Refer to Default Creation Zone and Templates for further information.\nYou can define the default zone for the storage of supports upon creation by selecting a zone from the Storage Area drop-down list.\n\nAdditional functionality is available to define the default zone for support creation. You can also define the default templates for framework supports, special supports and hangers. Refer to Application Defaults for further information.\n\n\n\nDefault Creation Zone and Templates\nApplication Defaults\nDefault Creation Zone and Templates\nStorage Area\nApplication Defaults"}
{"Headers": "Support Catalogs", "Content": "Functionality is available to use multiple MDU catalogues in a session to read data from when creating a support.\nThe administrator controls the selection of which catalogues are displayed. Refer to Multiple Support Catalogs for further information.\nYou can define the current MDU catalogue by selecting a catalogue from the MDU drop-down list.\n\n\n\n\nMultiple Support Catalogs\nMultiple Support Catalogs\nMDU"}
{"Headers": "Data Access Control", "Content": "The teams owning the database mechanisms handle the method of controlling data access. In addition, the following access control features allow you to specify in additional detail what operations a user can carry out on elements in the database. This is known as Data Access Control (DAC).\nWith DAC switched on, all general users are prevented from carrying out any operation on any part of the database unless they have specifically been given the necessary access rights. DAC uses the following administration database elements:\nWhen you select a pipe to create a support, the application first checks if it can claim the branch. If it cannot claim the branch, an error message displays. A check is made at branch level because another user can modify the branch while it is being supported. This can compromise the integrity of the model because the user may move the branch leg that is being supported.\nIf the user can claim the element, a further check is made to see if sufficient access rights are available to create supports.\nIf the status of the pipe is set to locked or issued, an error message displays summarizing the problem upon creation or modification of a support.\n\nRole defines the type of operations a user can carry out. For example, creating, modifying and deleting elements. Roles are defined as a collection of permissible operations (Perops).\nScope defines the part of the database in which a user can work.\nAccess Control Rights (ACRs) are a combination of a role and a scope. Users can, and usually will, have several ACRs, allowing them to carry out specified operations on specified parts of the database.\nRole defines the type of operations a user can carry out. For example, creating, modifying and deleting elements. Roles are defined as a collection of permissible operations (Perops).\nRole defines the type of operations a user can carry out. For example, creating, modifying and deleting elements. Roles are defined as a collection of permissible operations (Perops).\nScope defines the part of the database in which a user can work.\nScope defines the part of the database in which a user can work.\nAccess Control Rights (ACRs) are a combination of a role and a scope. Users can, and usually will, have several ACRs, allowing them to carry out specified operations on specified parts of the database.\nAccess Control Rights (ACRs) are a combination of a role and a scope. Users can, and usually will, have several ACRs, allowing them to carry out specified operations on specified parts of the database.\nNote:\nTo use DAC it must be switched on for the project, otherwise only the teams owning database controls will apply.\n\n\n\nNote\n:\nRole\nScope\nAccess Control Rights (ACRs)"}
{"Headers": "Support Editor", "Content": "Modifies the currently selected support.\nAll of the tasks that are associated with the creation or modification of supports and ancillaries are initiated from a central Support Editor window which acts as a task hub.\nDepending on the selections made in the Support Editor window, you are presented with further windows prompting for input. After inputting information in these windows you are returned to the Support Editor window, allowing the workflow to continue.\nYou can define the following Support types:\nBy default, the display of the Support Editor window is configured for the settings of the currently selected support type.\n\nThe Support Editor window allows you to create, position and refine the detailing for the support and the associated ancillaries. Only the options available for the selected support type are active.\nThe support name displays at the top of the Support Editor window. By default, the Supports application populates the Name field. Refer to Auto Name Defaults for further information. You can input a value in the field to modify the support name.\nIf an invalid support name is input, an error message displays summarizing the problem and the support name reverts to the previous valid name.\n\nThe following naming conventions cannot be used:\nClick Apply to create the support and close the Support Editor window.\nClick Cancel to discard any inputs and close the Support Editor window. A confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nBy default, the supports application carries out a health check on the created support upon completion. Refer to Health Check for further information.\nPreliminary Supports\nFramework Supports\nAncillaries\nTrunnions\nHangers\nSpecial Supports\nPreliminary Supports\nPreliminary Supports\nFramework Supports\nFramework Supports\nAncillaries\nAncillaries\nTrunnions\nTrunnions\nHangers\nHangers\nSpecial Supports\nSpecial Supports\nExisting support name\nExisting support name followed by.1\nSupport name beginning with = or *\nExisting support name\nExisting support name\nExisting support name followed by.1\nExisting support name followed by.1\nSupport name beginning with = or *\nSupport name beginning with = or *\nNote:\nIf Cancel was applied on an existing support, A confirm window displays informing you that the support will be to returned to the original state prior to modification. Click Yes to discard any modifications.\n\n\n\nAuto Name Defaults\nHealth Check\nSupport Editor\nSupport Editor\nSupport Editor\nSupport Editor\nSupport Editor\nSupport Editor\nName\nAuto Name Defaults\nApply\nSupport Editor\nCancel\nSupport Editor\nYes\nNote\n:\nCancel\nYes\nHealth Check"}
{"Headers": "Framework Options", "Content": "Sets specific framework options, dependent on the combination of supports and ancillaries used to create the support.\nFor example, the options part of the Support Editor window allows you to define the build type and size of the packing piece associated with an XFT22 Support.\n\nThe framework options are only available for specific scenarios. If the required scenario is not satisfied, an error is displayed. For example, an XFT03 support can be aligned to the top or bottom of a structural beam.\n\nTo enable the functionality, the following build scenario must be satisfied:\nThe table displays the available framework options on the Support Editor window.\nSupport\nDrop-down list\nDescription\nXFT03, XFT04\nBuild\nYou can specify the alignment of the framework support to a structural element.\nSelect Top from the drop-down list to align the ancillary to the top of a structural element.\nSelect Bottom from the drop-down list to align the ancillary to the bottom of a structural element.\nYou are prompted to Identify Structural Element to slide to\nXFT13\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect After Column from the drop-down list to position the framework support build point behind a steel column.\nSelect Before Column from the drop-down list to position the framework support build point in front of a steel column.\nXCT06, XDT03, XFT14\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect After Column from the drop-down list to position the framework support build point behind a steel column.\nSelect Before Column from the drop-down list to position the framework support build point in front of a steel column.\nSelect Web of Beam from the drop-down list to position the framework support build point within the web of a beam.\nSelect Below Beam from the drop-down list to position the framework support below a horizontal beam.\nSelect Face to Vert B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a vertical baseplate.\nSelect End to Vert B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a vertical baseplate.\nSelect Face to Hori B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a horizontal baseplate.\nSelect Wall from the drop-down list to position the framework support build point to a wall.\nXFT15\nBuild\nYou can specify the position of the build point of the framework support.\nSelect Web to Web from the drop-down list to position the framework support build points within the web of two beams.\nSelect Web to Below from the drop-down list to position the framework support build points using the web of a beam and the bottom of a flange connection beam.\nSelect Below Common from the drop-down list to position the crossbar of the framework support underneath the lowest of two beams positioned at different heights.\nSelect Below Uncommon from the drop-down list to position the crossbar of the framework support underneath two beams positioned at the same height.\nXFT17, XFT40\nSlide to Beam\nYou can specify the connection point of the framework support to an ancillary.\nSelect Centreline from the drop-down list to connect the ancillary to the centre point of the framework support.\nSelect Front Backmark from the drop-down list to connect the ancillary to the front of the framework support.\nSelect Rear Backmark from the drop-down list to connect the ancillary to the back of the framework support.\nXFT18, XFT19\nSlide to Beam\nYou can specify the connection point of the framework support to an ancillary.\nSelect Top from the drop-down list to connect the ancillary to the top of the framework support.\nSelect Bottom from the drop-down list to connect the ancillary to the bottom of the framework support.\nXFT21\nPosition\nYou can specify the connection point of the framework support to two ancillaries.\nSelect Square (Change Datum Dir.) from the drop down list, the Supports application allows you to manually align the support if the two pipes are not positioned at the same level.\nThe Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\nSelect Square (Change Datum Dir.) from the drop down list, the Supports application positions the framework support at an angle to connect to both ancillaries.\nXFT22\nType\nSelect a bedplate type for the framework support from the drop down list.\nXFT22\nSize\nSelect a bedplate size for the framework support from the drop down list.\nXFT23, XFT41\nCap Size\nSelect a cap size from the drop-down list to define the dimensions of the steelwork cap.\nXFT24\nDimensions\nSelect a predefined dimension for the framework support from the drop down list.\nXFT25\nType\nSelect a packing piece type from the drop down list.\nXFT25\nSize\nSelect a packing piece size from the drop down list.\nXFT28\nGrating bolts\nYou can specify the inclusion of grating bolts for the framework support.\nSelect Not-Apply Grating Bolt from the drop down list to exclude grating bolts from the framework support.\nSelect Apply Grating Bolt from the drop down list to include grating bolts in the framework support assembly.\nXFT33\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect After Column from the drop-down list to position the framework support build point behind a steel column.\nSelect Before Column from the drop-down list to position the framework support build point in front of a steel column.\nSelect To Web of Beam from the drop-down list to position the framework support build point within the web of a beam.\nSelect Below Beam from the drop-down list to position the framework support below a horizontal beam.\nSelect Face to Vert B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a vertical baseplate.\nSelect End to Vert B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a vertical baseplate.\nSelect Face to Hori B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a horizontal baseplate.\nXFT34A, XFT34B\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect To Web of Beam from the drop-down list to position the framework support build point within the web of a beam.\nSelect End to Vert B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a vertical baseplate.\nSelect Wall from the drop-down list to position the framework support build point to a wall.\nXFT34C\nBuild\nYou can specify the position of the build point of the framework support.\nSelect Below Beam from the drop-down list to position the framework support below a horizontal beam.\nSelect End to Hori B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a horizontal baseplate.\nXGT05\nSize\nSelect a framework section size from the drop down list.\nXVT07, XVT08, XVT09\nBuild\nYou can specify the position of the build point of the framework support.\nSelect Under Lug from the drop-down list to position the framework support build points under a lug.\nSelect Under Dummy Legs from the drop-down list to position the framework support build points under dummy legs.\nSupport\nDrop-down list\nDescription\nXFT03, XFT04\nBuild\nYou can specify the alignment of the framework support to a structural element.\nSelect Top from the drop-down list to align the ancillary to the top of a structural element.\nSelect Bottom from the drop-down list to align the ancillary to the bottom of a structural element.\nYou are prompted to Identify Structural Element to slide to\nXFT13\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect After Column from the drop-down list to position the framework support build point behind a steel column.\nSelect Before Column from the drop-down list to position the framework support build point in front of a steel column.\nXCT06, XDT03, XFT14\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect After Column from the drop-down list to position the framework support build point behind a steel column.\nSelect Before Column from the drop-down list to position the framework support build point in front of a steel column.\nSelect Web of Beam from the drop-down list to position the framework support build point within the web of a beam.\nSelect Below Beam from the drop-down list to position the framework support below a horizontal beam.\nSelect Face to Vert B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a vertical baseplate.\nSelect End to Vert B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a vertical baseplate.\nSelect Face to Hori B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a horizontal baseplate.\nSelect Wall from the drop-down list to position the framework support build point to a wall.\nXFT15\nBuild\nYou can specify the position of the build point of the framework support.\nSelect Web to Web from the drop-down list to position the framework support build points within the web of two beams.\nSelect Web to Below from the drop-down list to position the framework support build points using the web of a beam and the bottom of a flange connection beam.\nSelect Below Common from the drop-down list to position the crossbar of the framework support underneath the lowest of two beams positioned at different heights.\nSelect Below Uncommon from the drop-down list to position the crossbar of the framework support underneath two beams positioned at the same height.\nXFT17, XFT40\nSlide to Beam\nYou can specify the connection point of the framework support to an ancillary.\nSelect Centreline from the drop-down list to connect the ancillary to the centre point of the framework support.\nSelect Front Backmark from the drop-down list to connect the ancillary to the front of the framework support.\nSelect Rear Backmark from the drop-down list to connect the ancillary to the back of the framework support.\nXFT18, XFT19\nSlide to Beam\nYou can specify the connection point of the framework support to an ancillary.\nSelect Top from the drop-down list to connect the ancillary to the top of the framework support.\nSelect Bottom from the drop-down list to connect the ancillary to the bottom of the framework support.\nXFT21\nPosition\nYou can specify the connection point of the framework support to two ancillaries.\nSelect Square (Change Datum Dir.) from the drop down list, the Supports application allows you to manually align the support if the two pipes are not positioned at the same level.\nThe Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\nSelect Square (Change Datum Dir.) from the drop down list, the Supports application positions the framework support at an angle to connect to both ancillaries.\nXFT22\nType\nSelect a bedplate type for the framework support from the drop down list.\nXFT22\nSize\nSelect a bedplate size for the framework support from the drop down list.\nXFT23, XFT41\nCap Size\nSelect a cap size from the drop-down list to define the dimensions of the steelwork cap.\nXFT24\nDimensions\nSelect a predefined dimension for the framework support from the drop down list.\nXFT25\nType\nSelect a packing piece type from the drop down list.\nXFT25\nSize\nSelect a packing piece size from the drop down list.\nXFT28\nGrating bolts\nYou can specify the inclusion of grating bolts for the framework support.\nSelect Not-Apply Grating Bolt from the drop down list to exclude grating bolts from the framework support.\nSelect Apply Grating Bolt from the drop down list to include grating bolts in the framework support assembly.\nXFT33\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect After Column from the drop-down list to position the framework support build point behind a steel column.\nSelect Before Column from the drop-down list to position the framework support build point in front of a steel column.\nSelect To Web of Beam from the drop-down list to position the framework support build point within the web of a beam.\nSelect Below Beam from the drop-down list to position the framework support below a horizontal beam.\nSelect Face to Vert B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a vertical baseplate.\nSelect End to Vert B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a vertical baseplate.\nSelect Face to Hori B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a horizontal baseplate.\nXFT34A, XFT34B\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect To Web of Beam from the drop-down list to position the framework support build point within the web of a beam.\nSelect End to Vert B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a vertical baseplate.\nSelect Wall from the drop-down list to position the framework support build point to a wall.\nXFT34C\nBuild\nYou can specify the position of the build point of the framework support.\nSelect Below Beam from the drop-down list to position the framework support below a horizontal beam.\nSelect End to Hori B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a horizontal baseplate.\nXGT05\nSize\nSelect a framework section size from the drop down list.\nXVT07, XVT08, XVT09\nBuild\nYou can specify the position of the build point of the framework support.\nSelect Under Lug from the drop-down list to position the framework support build points under a lug.\nSelect Under Dummy Legs from the drop-down list to position the framework support build points under dummy legs.\n\nSupport\nDrop-down list\nDescription\nXFT03, XFT04\nBuild\nYou can specify the alignment of the framework support to a structural element.\nSelect Top from the drop-down list to align the ancillary to the top of a structural element.\nSelect Bottom from the drop-down list to align the ancillary to the bottom of a structural element.\nYou are prompted to Identify Structural Element to slide to\nXFT13\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect After Column from the drop-down list to position the framework support build point behind a steel column.\nSelect Before Column from the drop-down list to position the framework support build point in front of a steel column.\nXCT06, XDT03, XFT14\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect After Column from the drop-down list to position the framework support build point behind a steel column.\nSelect Before Column from the drop-down list to position the framework support build point in front of a steel column.\nSelect Web of Beam from the drop-down list to position the framework support build point within the web of a beam.\nSelect Below Beam from the drop-down list to position the framework support below a horizontal beam.\nSelect Face to Vert B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a vertical baseplate.\nSelect End to Vert B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a vertical baseplate.\nSelect Face to Hori B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a horizontal baseplate.\nSelect Wall from the drop-down list to position the framework support build point to a wall.\nXFT15\nBuild\nYou can specify the position of the build point of the framework support.\nSelect Web to Web from the drop-down list to position the framework support build points within the web of two beams.\nSelect Web to Below from the drop-down list to position the framework support build points using the web of a beam and the bottom of a flange connection beam.\nSelect Below Common from the drop-down list to position the crossbar of the framework support underneath the lowest of two beams positioned at different heights.\nSelect Below Uncommon from the drop-down list to position the crossbar of the framework support underneath two beams positioned at the same height.\nXFT17, XFT40\nSlide to Beam\nYou can specify the connection point of the framework support to an ancillary.\nSelect Centreline from the drop-down list to connect the ancillary to the centre point of the framework support.\nSelect Front Backmark from the drop-down list to connect the ancillary to the front of the framework support.\nSelect Rear Backmark from the drop-down list to connect the ancillary to the back of the framework support.\nXFT18, XFT19\nSlide to Beam\nYou can specify the connection point of the framework support to an ancillary.\nSelect Top from the drop-down list to connect the ancillary to the top of the framework support.\nSelect Bottom from the drop-down list to connect the ancillary to the bottom of the framework support.\nXFT21\nPosition\nYou can specify the connection point of the framework support to two ancillaries.\nSelect Square (Change Datum Dir.) from the drop down list, the Supports application allows you to manually align the support if the two pipes are not positioned at the same level.\nThe Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\nSelect Square (Change Datum Dir.) from the drop down list, the Supports application positions the framework support at an angle to connect to both ancillaries.\nXFT22\nType\nSelect a bedplate type for the framework support from the drop down list.\nXFT22\nSize\nSelect a bedplate size for the framework support from the drop down list.\nXFT23, XFT41\nCap Size\nSelect a cap size from the drop-down list to define the dimensions of the steelwork cap.\nXFT24\nDimensions\nSelect a predefined dimension for the framework support from the drop down list.\nXFT25\nType\nSelect a packing piece type from the drop down list.\nXFT25\nSize\nSelect a packing piece size from the drop down list.\nXFT28\nGrating bolts\nYou can specify the inclusion of grating bolts for the framework support.\nSelect Not-Apply Grating Bolt from the drop down list to exclude grating bolts from the framework support.\nSelect Apply Grating Bolt from the drop down list to include grating bolts in the framework support assembly.\nXFT33\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect After Column from the drop-down list to position the framework support build point behind a steel column.\nSelect Before Column from the drop-down list to position the framework support build point in front of a steel column.\nSelect To Web of Beam from the drop-down list to position the framework support build point within the web of a beam.\nSelect Below Beam from the drop-down list to position the framework support below a horizontal beam.\nSelect Face to Vert B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a vertical baseplate.\nSelect End to Vert B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a vertical baseplate.\nSelect Face to Hori B/Plt from the drop-down list to position the face of the framework support to a Ppoint on a horizontal baseplate.\nXFT34A, XFT34B\nBuild\nYou can specify the position of the build point of the framework support.\nSelect On Column CL from the drop-down list to position the framework support build point at the centre point of a steel column.\nSelect To Web of Beam from the drop-down list to position the framework support build point within the web of a beam.\nSelect End to Vert B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a vertical baseplate.\nSelect Wall from the drop-down list to position the framework support build point to a wall.\nXFT34C\nBuild\nYou can specify the position of the build point of the framework support.\nSelect Below Beam from the drop-down list to position the framework support below a horizontal beam.\nSelect End to Hori B/Plt from the drop-down list to position the end of the framework support to a Ppoint on a horizontal baseplate.\nXGT05\nSize\nSelect a framework section size from the drop down list.\nXVT07, XVT08, XVT09\nBuild\nYou can specify the position of the build point of the framework support.\nSelect Under Lug from the drop-down list to position the framework support build points under a lug.\nSelect Under Dummy Legs from the drop-down list to position the framework support build points under dummy legs.\nThe support must be associated with a vertical pipe.\nThe support must be created using the correct datum attachment direction. Refer to Datum Attachment Direction for further information.\nThe support must be created using the To beam support configuration. Refer to Support Configurations for further information.\nThe support must be associated with a vertical pipe.\nThe support must be associated with a vertical pipe.\nThe support must be created using the correct datum attachment direction. Refer to Datum Attachment Direction for further information.\nThe support must be created using the correct datum attachment direction. Refer to Datum Attachment Direction for further information.\nThe support must be created using the To beam support configuration. Refer to Support Configurations for further information.\nThe support must be created using the To beam support configuration. Refer to Support Configurations for further information.\n\n\n\nDatum Attachment Direction\nSupport Configurations\nDatum Attachment Direction\nSupport Editor\nDatum Attachment Direction\nTo beam\nSupport Configurations\nSupport Editor\nSupport\nDrop-down list\nDescription\nIdentify Structural Element to slide to\nSquare (Change Datum Dir.)\nDatum attachment direction\nDatum Attachment Direction\nSquare (Change Datum Dir.)\nNot-Apply Grating Bolt\nApply Grating Bolt\nTo Web of Beam\nTo Web of Beam"}
{"Headers": "2D View", "Content": "The 2D View part of the Support Editor window allows you to modify the size and position of the support. By default, a separate tab displays on the Support Editor window for each support or ancillary currently being created or modified.\nClick a tab on the Support Editor window to display a 2D cross section view of the support or ancillary.\nA separate tab displays for the following support types:\nPreliminary Tab\nFramework Tab\nAncillary Tab\nBranch Reinforcement Tab\nTrunnion Tab\nHanger Tab\nSpecials Tab\nLighting Tab\nWitch Hanger Manufacturer\u2019s Interface\nLICAD Manufacturer\u2019s Interface\nPreliminary Tab\nPreliminary Tab\nFramework Tab\nFramework Tab\nAncillary Tab\nAncillary Tab\nBranch Reinforcement Tab\nBranch Reinforcement Tab\nTrunnion Tab\nTrunnion Tab\nHanger Tab\nHanger Tab\nSpecials Tab\nSpecials Tab\nLighting Tab\nLighting Tab\nWitch Hanger Manufacturer\u2019s Interface\nWitch Hanger Manufacturer\u2019s Interface\nLICAD Manufacturer\u2019s Interface\nLICAD Manufacturer\u2019s Interface\n\n\n\nPreliminary Tab\nFramework Tab\nAncillary Tab\nBranch Reinforcement Tab\nTrunnion Tab\nHanger Tab\nSpecials Tab\nLighting Tab\nWitch Hanger Manufacturer\u2019s Interface\nLICAD Manufacturer\u2019s Interface\n2D View\nSupport Editor\nSupport Editor\nSupport Editor\nPreliminary Tab\nFramework Tab\nAncillary Tab\nBranch Reinforcement Tab\nTrunnion Tab\nHanger Tab\nSpecials Tab\nLighting Tab\nWitch Hanger Manufacturer\u2019s Interface\nLICAD Manufacturer\u2019s Interface"}
{"Headers": "Preliminary Tab", "Content": "The preliminary support tab allows you to size and position a preliminary support.\n\nSelect default tab\nClick to display the default preliminary support tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the preliminary support and the associated ancillaries. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the preliminary support.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nDistance/Clearance\nAllows you to define the position of the preliminary support.\nClick to display . By default, the field is populated with a clearance value. For example, the distance from the end of a preceding elbow on the pipe. Input a dimensional value in the field to modify the Clearance distance explicitly.\nClick to display . By default, the field is populated with a distance value. For example, the distance from the centreline of a preceding elbow on the pipe. Input a dimensional value in the field to modify the Distance explicitly.\nDistance from Support/Distance from pipe element\nAllows you to define the position of the preliminary support.\nClick to display . By default, the field is populated with a distance value of 200mm, measured from the preceding support along the pipe route. Input a dimensional value in the field to modify the Distance from Support explicitly.\nIf a there is not a preceding support along the pipe route, a Warning message displays summarizing the problem.\nClick to display . By default, the field is populated with a distance value, measured from the preceding pipe element along the pipe route. For example, the distance from the centreline of a preceding tee on the pipe. Input a dimensional value in the field to modify the Distance from pipe element explicitly.\n\nSelect default tab\nClick to display the default preliminary support tab. The default tab is the first tab created and is positioned furthest left.\n\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n\n2D/3D View\nClick to display a 3D view of the preliminary support and the associated ancillaries. Refer to 3D View Tab for further information.\n\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the preliminary support.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\n\n\nDistance/Clearance\nAllows you to define the position of the preliminary support.\nClick to display . By default, the field is populated with a clearance value. For example, the distance from the end of a preceding elbow on the pipe. Input a dimensional value in the field to modify the Clearance distance explicitly.\nClick to display . By default, the field is populated with a distance value. For example, the distance from the centreline of a preceding elbow on the pipe. Input a dimensional value in the field to modify the Distance explicitly.\n\nDistance from Support/Distance from pipe element\nAllows you to define the position of the preliminary support.\nClick to display . By default, the field is populated with a distance value of 200mm, measured from the preceding support along the pipe route. Input a dimensional value in the field to modify the Distance from Support explicitly.\nIf a there is not a preceding support along the pipe route, a Warning message displays summarizing the problem.\n\nClick to display . By default, the field is populated with a distance value, measured from the preceding pipe element along the pipe route. For example, the distance from the centreline of a preceding tee on the pipe. Input a dimensional value in the field to modify the Distance from pipe element explicitly.\n\nSelect default tab\nClick to display the default preliminary support tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the preliminary support and the associated ancillaries. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the preliminary support.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nDistance/Clearance\nAllows you to define the position of the preliminary support.\nClick to display . By default, the field is populated with a clearance value. For example, the distance from the end of a preceding elbow on the pipe. Input a dimensional value in the field to modify the Clearance distance explicitly.\nClick to display . By default, the field is populated with a distance value. For example, the distance from the centreline of a preceding elbow on the pipe. Input a dimensional value in the field to modify the Distance explicitly.\nDistance from Support/Distance from pipe element\nAllows you to define the position of the preliminary support.\nClick to display . By default, the field is populated with a distance value of 200mm, measured from the preceding support along the pipe route. Input a dimensional value in the field to modify the Distance from Support explicitly.\nIf a there is not a preceding support along the pipe route, a Warning message displays summarizing the problem.\nClick to display . By default, the field is populated with a distance value, measured from the preceding pipe element along the pipe route. For example, the distance from the centreline of a preceding tee on the pipe. Input a dimensional value in the field to modify the Distance from pipe element explicitly.\n\n\n\n3D View Tab\nSelect default tab\nSelect ancillary tab by canvas pick\nIdentify ancillary in current support\n2D/3D View\n3D View Tab\nDimensions\nDimensions\nDistance/Clearance\nClearance\nDistance\nDistance from Support/Distance from pipe element\nDistance from Support\nDistance from pipe element"}
{"Headers": "Framework Tab", "Content": "By default, a separate tab displays on the Support Editor window for the framework support and each of the associated ancillaries.\nThe framework support tab allows you to size and position a framework support. Functionality is also available to add a crossbar and bracing to the framework support. The framework support can also be viewed in a 3D view.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the framework support and the associated ancillaries. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the framework support.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nBuild by Cursor\nClick to identify the first element to support from using a cursor pick in the 3D view.\nYou are prompted to Identify first element to support from\nYou must then identify the second element to support from using a cursor pick in the 3D view.\nYou are prompted to Identify second element to support from\nThe support is created using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified supporting elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\nBuild By Clearance\nClick to identify the element to support from using a cursor pick in the 3D view.\nYou are prompted to Identify element to support from\nThe application creates the support using the dimensions gained from the position of the identified element. The clearances are calculated from the default values, obtained from:\nThe values stored against each ancillary standard in the Aveva Catalogue\u2122 defaults database. If unset, the clearance values from the Supports Application Defaults window are used. Refer to Supports Defaults for further information.\nThe build style of the framework stored against the :MDSBUILDSTYL uda at each framework template STRU element. That is, the default is INSIDE and the alternative value is OUTSIDE.\nThe clearance values and all other default values can be queried by displaying the Supports Application Defaults window. Refer to Supports Defaults and Automatic Steelwork Orientation for further information.\nBy default, connections are made to the identified elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\nCreate Bracing\nAllows you to define bracing for the framework support. Refer to Bracing for further information.\nCreate Crossbar\nClick to add a crossbar to a framework support. You must identify one or more ancillaries to associate with the crossbar using a cursor pick in the 3D view.\nYou are prompted to Identify Ancillary to support\nYou can continue to identify additional ancillaries using a cursor pick in the 3D view.\nPress ESC to add the crossbar.\nDistance/Clearance\nAllows you to position the framework support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position of the framework support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\n\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n\n2D/3D View\nClick to display a 3D view of the framework support and the associated ancillaries. Refer to 3D View Tab for further information.\n\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the framework support.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\n\n\nBuild by Cursor\nClick to identify the first element to support from using a cursor pick in the 3D view.\nYou are prompted to Identify first element to support from\nYou must then identify the second element to support from using a cursor pick in the 3D view.\nYou are prompted to Identify second element to support from\nThe support is created using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified supporting elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\n\nBuild By Clearance\nClick to identify the element to support from using a cursor pick in the 3D view.\nYou are prompted to Identify element to support from\nThe application creates the support using the dimensions gained from the position of the identified element. The clearances are calculated from the default values, obtained from:\nThe clearance values and all other default values can be queried by displaying the Supports Application Defaults window. Refer to Supports Defaults and Automatic Steelwork Orientation for further information.\nBy default, connections are made to the identified elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\n\nCreate Bracing\nAllows you to define bracing for the framework support. Refer to Bracing for further information.\n\nCreate Crossbar\nClick to add a crossbar to a framework support. You must identify one or more ancillaries to associate with the crossbar using a cursor pick in the 3D view.\nYou are prompted to Identify Ancillary to support\nYou can continue to identify additional ancillaries using a cursor pick in the 3D view.\nPress ESC to add the crossbar.\n\nDistance/Clearance\nAllows you to position the framework support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nDistance from Support/Distance from pipe element\nAllows you to position of the framework support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nCycle End Position\nAllows you to position the framework support on a cable tray bend, tee, cross, elbow or reducer created as a member of a PIPE element using the Cable Tray module.\nClick Cycle End Position to move the framework support to a different component end position ppoint. Repeat the command to cycle through the available ppoints.\nThe example displays the available end-point positions for a reducer.\nNote:\nPpoints not consistent with the current configuration are skipped, for example, a vertical end for a CT03 framework with a tee on its side.\nCycle End Position\nAllows you to position the framework support on a cable tray bend, tee, cross, elbow or reducer created as a member of a PIPE element using the Cable Tray module.\nClick Cycle End Position to move the framework support to a different component end position ppoint. Repeat the command to cycle through the available ppoints.\nThe example displays the available end-point positions for a reducer.\n\n\nPosition Around Tray\nAllows you to position the framework support on a cable tray bend, tee, cross, riser or reducer created as a member of a CWAY element using the Cabling System module. Refer to Cable Tray Bend Supports (CWAY Elements) for further information.\nPosition Around Tray\nAllows you to position the framework support on a cable tray bend, tee, cross, riser or reducer created as a member of a CWAY element using the Cabling System module. Refer to Cable Tray Bend Supports (CWAY Elements) for further information.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the framework support and the associated ancillaries. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the framework support.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nBuild by Cursor\nClick to identify the first element to support from using a cursor pick in the 3D view.\nYou are prompted to Identify first element to support from\nYou must then identify the second element to support from using a cursor pick in the 3D view.\nYou are prompted to Identify second element to support from\nThe support is created using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified supporting elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\nBuild By Clearance\nClick to identify the element to support from using a cursor pick in the 3D view.\nYou are prompted to Identify element to support from\nThe application creates the support using the dimensions gained from the position of the identified element. The clearances are calculated from the default values, obtained from:\nThe values stored against each ancillary standard in the Aveva Catalogue\u2122 defaults database. If unset, the clearance values from the Supports Application Defaults window are used. Refer to Supports Defaults for further information.\nThe build style of the framework stored against the :MDSBUILDSTYL uda at each framework template STRU element. That is, the default is INSIDE and the alternative value is OUTSIDE.\nThe clearance values and all other default values can be queried by displaying the Supports Application Defaults window. Refer to Supports Defaults and Automatic Steelwork Orientation for further information.\nBy default, connections are made to the identified elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\nCreate Bracing\nAllows you to define bracing for the framework support. Refer to Bracing for further information.\nCreate Crossbar\nClick to add a crossbar to a framework support. You must identify one or more ancillaries to associate with the crossbar using a cursor pick in the 3D view.\nYou are prompted to Identify Ancillary to support\nYou can continue to identify additional ancillaries using a cursor pick in the 3D view.\nPress ESC to add the crossbar.\nDistance/Clearance\nAllows you to position the framework support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position of the framework support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nCycle End Position\nAllows you to position the framework support on a cable tray bend, tee, cross, elbow or reducer created as a member of a PIPE element using the Cable Tray module.\nClick Cycle End Position to move the framework support to a different component end position ppoint. Repeat the command to cycle through the available ppoints.\nThe example displays the available end-point positions for a reducer.\nNote:\nPpoints not consistent with the current configuration are skipped, for example, a vertical end for a CT03 framework with a tee on its side.\nPosition Around Tray\nAllows you to position the framework support on a cable tray bend, tee, cross, riser or reducer created as a member of a CWAY element using the Cabling System module. Refer to Cable Tray Bend Supports (CWAY Elements) for further information.\nThe values stored against each ancillary standard in the Aveva Catalogue\u2122 defaults database. If unset, the clearance values from the Supports Application Defaults window are used. Refer to Supports Defaults for further information.\nThe build style of the framework stored against the :MDSBUILDSTYL uda at each framework template STRU element. That is, the default is INSIDE and the alternative value is OUTSIDE.\nThe values stored against each ancillary standard in the Aveva Catalogue\u2122 defaults database. If unset, the clearance values from the Supports Application Defaults window are used. Refer to Supports Defaults for further information.\nThe values stored against each ancillary standard in the Aveva Catalogue\u2122 defaults database. If unset, the clearance values from the Supports Application Defaults window are used. Refer to Supports Defaults for further information.\nThe build style of the framework stored against the :MDSBUILDSTYL uda at each framework template STRU element. That is, the default is INSIDE and the alternative value is OUTSIDE.\nThe build style of the framework stored against the :MDSBUILDSTYL uda at each framework template STRU element. That is, the default is INSIDE and the alternative value is OUTSIDE.\nNote:\nPpoints not consistent with the current configuration are skipped, for example, a vertical end for a CT03 framework with a tee on its side.\n\n\n\n3D View Tab\nSupports Connectivity\nSupports Defaults\nSupports Defaults\nAutomatic Steelwork Orientation\nSupports Connectivity\nBracing\nPreliminary Tab\nPreliminary Tab\nCable Tray Bend Supports (CWAY Elements)\nSupport Editor\nSelect default tab\nSelect ancillary tab by canvas pick\nIdentify ancillary in current support\n2D/3D View\n3D View Tab\nDimensions\nDimensions\nBuild by Cursor\nIdentify first element to support from\nIdentify second element to support from\nDimensions\nSupports Connectivity\nBuild By Clearance\nIdentify element to support from\nSupports Defaults\nSupports Defaults\nAutomatic Steelwork Orientation\nDimensions\nSupports Connectivity\nCreate Bracing\nBracing\nCreate Crossbar\nIdentify Ancillary to support\nESC\nDistance/Clearance\nPreliminary Tab\nDistance from Support/Distance from pipe element\nPreliminary Tab\nCycle End Position\nCycle End Position\nNote\n:\nPosition Around Tray\nCable Tray Bend Supports (CWAY Elements)"}
{"Headers": "3D View Tab", "Content": "The 3D View part of the Support Editor window allows you to view a 3D representation of the support and the associated ancillaries.\n\n2D/3D View\nClick to return to a 2D View.\nView along centreline of pipe\nClick to view a 3D representation of the support and the associated ancillaries along the centreline of the pipe.\nView perpendicular to pipe\nClick to view a 3D representation of the support and the associated ancillaries perpendicular to the pipe.\nView vertical to pipe\nClick to view a 3D representation of the support and the associated ancillaries vertical to the pipe.\n\n2D/3D View\nClick to return to a 2D View.\n\nView along centreline of pipe\nClick to view a 3D representation of the support and the associated ancillaries along the centreline of the pipe.\n\n\nView perpendicular to pipe\nClick to view a 3D representation of the support and the associated ancillaries perpendicular to the pipe.\n\n\nView vertical to pipe\nClick to view a 3D representation of the support and the associated ancillaries vertical to the pipe.\n\nThe 3D view of the support and the associated ancillaries can be manipulated with the middle mouse button. Refer to Middle Button Drag for further information.\n2D/3D View\nClick to return to a 2D View.\nView along centreline of pipe\nClick to view a 3D representation of the support and the associated ancillaries along the centreline of the pipe.\nView perpendicular to pipe\nClick to view a 3D representation of the support and the associated ancillaries perpendicular to the pipe.\nView vertical to pipe\nClick to view a 3D representation of the support and the associated ancillaries vertical to the pipe.\n\n\n\nMiddle Button Drag\n3D View\nSupport Editor\n2D/3D View\nView along centreline of pipe\nView perpendicular to pipe\nView vertical to pipe\nMiddle Button Drag"}
{"Headers": "Automatic Steelwork Orientation", "Content": "The Supports application can automatically orientate the support structure steel members of a framework support, dependant on the orientation of identified stiffeners. This function is available when you create a framework support using the build by cursor method within the framework creation process. The example indicates a typical example of a framework support (XFT08).\n\nThe correct orientation is achieved by utilizing appropriate templates. Each standard template has four alternatives. The names of the alternative templates are followed by a suffix, which is a configuration code based on the orientation of the stiffeners. Only templates that are built up from angle profiles have oriented alternatives.\nThe template catalogue has left and right hand versions of a template.\nWhen the support framework is created using the build by cursor method. You are prompted to identify the first stiffener, then the second stiffener.\nOnce the stiffeners are identified, the Supports application checks that their gtype is angle. If so, the orientation of the stiffener is stored as a number in user-defined attribute (uda) :MdsTmplOri at STRU level. The Supports application then checks for the existence of an oriented template with this number; if found, this is used instead of the standard template.\nAll settings (number of bars, min/max bore, etc) are always obtained from the standard template, except the value stored in uda :MDSBuildStyl, that is copied from the alternative.\nCurrently, only DIN frames have oriented alternatives, stored in APPLDW/SUPPORT/FRAMES/ORI/. These are as follows:\nXFT03\nXFT23\nXFT04\nXFT31\nXFT05\nXFT32\nXFT06\nXFT35\nXFT08\nXFT36\nXFT09\nXFT37\nXFT18\nXFT40\nXFT19\nXFT42\nXFT03\nXFT23\nXFT04\nXFT31\nXFT05\nXFT32\nXFT06\nXFT35\nXFT08\nXFT36\nXFT09\nXFT37\nXFT18\nXFT40\nXFT19\nXFT42\n\nXFT03\nXFT23\nXFT04\nXFT31\nXFT05\nXFT32\nXFT06\nXFT35\nXFT08\nXFT36\nXFT09\nXFT37\nXFT18\nXFT40\nXFT19\nXFT42\nNote:\nSubsequent modifications of the support using build by clearance or dimensions methods selects the oriented template first.\n\n\n\nNote\n:"}
{"Headers": "Supports Connectivity", "Content": "When a framework support section (GENSEC) is connected to a structural support section (GENSEC), the connection between the two sections is represented on the attached framework support section as End Datum (ENDATU) and Fixing (FIXING) elements in the Model Explorer. To avoid the necessity to write to the structural database, the connection is not represented on the structural support section.\nIn the supports hierarchy, ENDATU and FIXING elements are created each time an attached section is connected. By default, the ENDATU and FIXING elements are deleted if a connected support is deleted.\n\nWhen creating a framework using Create By Cursor or Create By Clearance, if the structural element that is picked is not a steel profile (GENSEC or HSTIFF) a civils connection is created. Examples of such elements are: FLOOR, STWALL, PANE.\nA civils connection is similar to a steelwork end-plate connection. It consists of an ENDATU and a FIXING. Unlike a steelwork connection, it uses the CONREF attribute on the ENDATU to link to the civils element that it is connected to. There is also a return reference on the civils element, ENDRFA that returns all the civils connections referencing that element.\nEnd Datum (ENDATU)\nENDATU elements are owned by GENSEC elements. By default, an ENDATU element is created for each connection. The ENDATU element contains the positioning line datum for the connection. The positioning line datum represents the Pline that the attached section is trimmed to. ENDATU elements can own FIXING elements.\nFixing (FIXING)\nFIXING elements are owned by ENDATU elements and have the same position as the ENDATU. FIXING elements contain properties for:\nFramework Support Section Properties\nThe GENSEC properties for the attached framework support are identical to the fixing properties for structural sections. Refer to Attached Sections for further information.\nEnd Datum Properties\nThe ENDATU properties for a framework support section are identical to the end datum properties for structural sections. Refer to End Datum Properties for further information.\nFixing Properties\nThe FIXING properties for a framework support section are identical to the fixing properties for structural sections. Refer to Fixing Properties for further information.\nReconnect Framework Support\nReconnects the currently selected framework support if it is moved and the connection does not move with it.\nOn the command line, input the command RECONNECT and press Enter.\nAlthough each connection has created ENDATU and FIXING elements in the Design database, these do not yet have any geometry associated with them. In order to represent them properly, a catalogue specification must be associated with each joint. Refer to Joint Specification for further information.\nConnectivity to the structural 3D model\nTrimming attached members\nSpecification Reference (SPREF attribute) for the joint.\nConnectivity to the structural 3D model\nConnectivity to the structural 3D model\nTrimming attached members\nTrimming attached members\nSpecification Reference (SPREF attribute) for the joint.\nSpecification Reference (SPREF attribute) for the joint.\n\n\n\nAttached Sections\nEnd Datum Properties\nFixing Properties\nJoint Specification\nEnd Datum (ENDATU)\nFixing (FIXING)\nFramework Support Section Properties\nAttached Sections\nEnd Datum Properties\nEnd Datum Properties\nFixing Properties\nFixing Properties\nReconnect Framework Support\nRECONNECT\nEnter\nJoint Specification"}
{"Headers": "Bracing", "Content": "Sets the bracing for the currently selected framework support.\n\nThe bracing support name displays at the top of the Bracing window.\nThe Options part of the Bracing window allows you to define the bracing type, size and style.\n\nCE\nClick to select existing bracing as the current element\nThe option becomes active when bracing has been created.\nPick\nClick to select existing bracing using a cursor pick in the 3D view.\nThe option becomes active when bracing has been created.\nYou are prompted to Identify brace member to be modified\nNew Brace\nClick to create new bracing.\nThe option becomes active when bracing has been created.\nMirror Brace\nClick to mirror the bracing on its axis.\nThe option becomes active when bracing has been created.\nNudge Brace\nAllows you to nudge the bracing by a set distance. Refer to Nudge Bracing for further information.\nThe option becomes active when bracing has been created.\nAllows you to delete the currently selected bracing. A confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nType\nSelect a bracing type from the drop-down list.\nSize\nSelect a bracing size from the drop-down list.\nOutside Frame\nClick to select outside frame as the current bracing style. All other support types are deactivated.\nInside Frame\nClick to select inside frame as the current bracing style. All other support types are deactivated.\nInfront Frame\nClick to select infront frame as the current bracing style. All other support types are deactivated.\nBehind Frame\nClick to select behind frame as the currently selected bracing style. All other support types are deactivated.\nUnder Cantilever\nClick to select under cantilever as the currently selected bracing style. All other support types are deactivated.\nInfront Cantilever\nClick to select infront cantilever as the currently selected bracing style. All other support types are deactivated.\nBehind Cantilever\nClick to select behind cantilever as the currently selected bracing style. All other support types are deactivated.\n\nCE\nClick to select existing bracing as the current element\nThe option becomes active when bracing has been created.\n\nPick\nClick to select existing bracing using a cursor pick in the 3D view.\nThe option becomes active when bracing has been created.\nYou are prompted to Identify brace member to be modified\n\nNew Brace\nClick to create new bracing.\nThe option becomes active when bracing has been created.\n\nMirror Brace\nClick to mirror the bracing on its axis.\nThe option becomes active when bracing has been created.\n\nNudge Brace\nAllows you to nudge the bracing by a set distance. Refer to Nudge Bracing for further information.\nThe option becomes active when bracing has been created.\n\n\nAllows you to delete the currently selected bracing. A confirm window displays asking you to OK the deletion. Click Yes to delete the item.\n\nType\nSelect a bracing type from the drop-down list.\n\nSize\nSelect a bracing size from the drop-down list.\n\nOutside Frame\nClick to select outside frame as the current bracing style. All other support types are deactivated.\n\nInside Frame\nClick to select inside frame as the current bracing style. All other support types are deactivated.\n\nInfront Frame\nClick to select infront frame as the current bracing style. All other support types are deactivated.\n\nBehind Frame\nClick to select behind frame as the currently selected bracing style. All other support types are deactivated.\n\nUnder Cantilever\nClick to select under cantilever as the currently selected bracing style. All other support types are deactivated.\n\nInfront Cantilever\nClick to select infront cantilever as the currently selected bracing style. All other support types are deactivated.\n\nBehind Cantilever\nClick to select behind cantilever as the currently selected bracing style. All other support types are deactivated.\nThe Dimensions part of the Bracing window allows you to define the bracing dimensions, angle and offset.\n\nDim \u2018L\u2019\nThe field is populated by default, you can modify the dimension value to define the length of the bracing.\nSelect the L option button to lock the Dim \u2018L\u2019 dimension.\nDim \u2018H\u2019\nThe field is populated by default, you can modify the dimension value to define the height of the bracing.\nSelect the H option button to lock the Dim \u2018H\u2019 dimension.\nAngle\nThe field is populated by default, you can modify the angle value to define the bracing angle.\nSelect the A option button to lock the angle.\nOffset\nThe field is populated by default, you can modify the dimension value to define a bracing offset distance.\nDim \u2018L\u2019\nThe field is populated by default, you can modify the dimension value to define the length of the bracing.\nSelect the L option button to lock the Dim \u2018L\u2019 dimension.\nDim \u2018H\u2019\nThe field is populated by default, you can modify the dimension value to define the height of the bracing.\nSelect the H option button to lock the Dim \u2018H\u2019 dimension.\nAngle\nThe field is populated by default, you can modify the angle value to define the bracing angle.\nSelect the A option button to lock the angle.\nOffset\nThe field is populated by default, you can modify the dimension value to define a bracing offset distance.\nThe bottom of the Bracing window allows you to view an illustration of the bracing and define the graphical display settings for the bracing dimensions.\nView Standard\nClick to display the View Multi Discipline Standard window. The functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\nShow/hide Dimensions\nClick to display the bracing dimensions in the 3D view.\n\nView Standard\nClick to display the View Multi Discipline Standard window. The functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\n\nShow/hide Dimensions\nClick to display the bracing dimensions in the 3D view.\nClick Apply to create the bracing, you must identify the associated framework support section using a cursor pick in the 3D view.\nYou are prompted to Identify frame member to be braced\nYou must then identify the associated supporting section using a cursor pick in the 3D view.\nYou are prompted to Identify supporting member\nClick Cancel to close the Bracing window.\nBy default, a connection is made between the framework support bracing section (GENSEC) and the structural support section (GENSEC). Refer to Supports Connectivity for further information.\nCE\nClick to select existing bracing as the current element\nThe option becomes active when bracing has been created.\nPick\nClick to select existing bracing using a cursor pick in the 3D view.\nThe option becomes active when bracing has been created.\nYou are prompted to Identify brace member to be modified\nNew Brace\nClick to create new bracing.\nThe option becomes active when bracing has been created.\nMirror Brace\nClick to mirror the bracing on its axis.\nThe option becomes active when bracing has been created.\nNudge Brace\nAllows you to nudge the bracing by a set distance. Refer to Nudge Bracing for further information.\nThe option becomes active when bracing has been created.\nAllows you to delete the currently selected bracing. A confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nType\nSelect a bracing type from the drop-down list.\nSize\nSelect a bracing size from the drop-down list.\nOutside Frame\nClick to select outside frame as the current bracing style. All other support types are deactivated.\nInside Frame\nClick to select inside frame as the current bracing style. All other support types are deactivated.\nInfront Frame\nClick to select infront frame as the current bracing style. All other support types are deactivated.\nBehind Frame\nClick to select behind frame as the currently selected bracing style. All other support types are deactivated.\nUnder Cantilever\nClick to select under cantilever as the currently selected bracing style. All other support types are deactivated.\nInfront Cantilever\nClick to select infront cantilever as the currently selected bracing style. All other support types are deactivated.\nBehind Cantilever\nClick to select behind cantilever as the currently selected bracing style. All other support types are deactivated.\nDim \u2018L\u2019\nThe field is populated by default, you can modify the dimension value to define the length of the bracing.\nSelect the L option button to lock the Dim \u2018L\u2019 dimension.\nDim \u2018H\u2019\nThe field is populated by default, you can modify the dimension value to define the height of the bracing.\nSelect the H option button to lock the Dim \u2018H\u2019 dimension.\nAngle\nThe field is populated by default, you can modify the angle value to define the bracing angle.\nSelect the A option button to lock the angle.\nOffset\nThe field is populated by default, you can modify the dimension value to define a bracing offset distance.\nView Standard\nClick to display the View Multi Discipline Standard window. The functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\nShow/hide Dimensions\nClick to display the bracing dimensions in the 3D view.\n\n\n\nNudge Bracing\nView Multi Discipline Support Standard\nSupports Connectivity\nBracing\nOptions\nBracing\nCE\nPick\nIdentify brace member to be modified\nNew Brace\nMirror Brace\nNudge Brace\nNudge Bracing\nYes\nType\nSize\nOutside Frame\nInside Frame\nInfront Frame\nBehind Frame\nUnder Cantilever\nInfront Cantilever\nBehind Cantilever\nDimensions\nBracing\nDim \u2018L\u2019\nL\nDim \u2018H\u2019\nH\nAngle\nA\nOffset\nBracing\nView Standard\nView Multi Discipline Standard\nView Multi Discipline Standard\nView Multi Discipline Support Standard\nShow/hide Dimensions\nApply\nIdentify frame member to be braced\nIdentify supporting member\nCancel\nBracing\nSupports Connectivity"}
{"Headers": "Nudge Bracing", "Content": "Nudges the bracing position by a set distance.\nFrom the Bracing window, click Nudge Brace to display the Modify Bracing window.\n\nBy\nInsert a value in the field to define the distance to nudge the bracing.\nMove North\nClick to nudge the bracing north, the nudge distance is defined by the value entered in the By field.\nMove Up\nClick to nudge the bracing up, the nudge distance is defined by the value entered in the By field.\nMove East\nClick to nudge the bracing east, the nudge distance is defined by the value entered in the By field.\nMove West\nClick to nudge the bracing west, the nudge distance is defined by the value entered in the By field.\nMove Down\nClick to nudge the bracing down, the nudge distance is defined by the value entered in the By field.\nMove South\nClick to nudge the bracing south, the nudge distance is defined by the value entered in the By field.\n\nBy\nInsert a value in the field to define the distance to nudge the bracing.\n\nMove North\nClick to nudge the bracing north, the nudge distance is defined by the value entered in the By field.\n\nMove Up\nClick to nudge the bracing up, the nudge distance is defined by the value entered in the By field.\n\nMove East\nClick to nudge the bracing east, the nudge distance is defined by the value entered in the By field.\n\nMove West\nClick to nudge the bracing west, the nudge distance is defined by the value entered in the By field.\n\nMove Down\nClick to nudge the bracing down, the nudge distance is defined by the value entered in the By field.\n\nMove South\nClick to nudge the bracing south, the nudge distance is defined by the value entered in the By field.\nClick Cancel to close the Modify Bracing window.\nBy\nInsert a value in the field to define the distance to nudge the bracing.\nMove North\nClick to nudge the bracing north, the nudge distance is defined by the value entered in the By field.\nMove Up\nClick to nudge the bracing up, the nudge distance is defined by the value entered in the By field.\nMove East\nClick to nudge the bracing east, the nudge distance is defined by the value entered in the By field.\nMove West\nClick to nudge the bracing west, the nudge distance is defined by the value entered in the By field.\nMove Down\nClick to nudge the bracing down, the nudge distance is defined by the value entered in the By field.\nMove South\nClick to nudge the bracing south, the nudge distance is defined by the value entered in the By field.\n\n\n\nBracing\nNudge Brace\nModify Bracing\nBy\nMove North\nBy\nMove Up\nBy\nMove East\nBy\nMove West\nBy\nMove Down\nBy\nMove South\nBy\nCancel\nModify Bracing"}
{"Headers": "Cable Tray Bend Supports (CWAY Elements)", "Content": "Cable tray framework supports can be created on cable tray bends, tees, crosses, risers and reducers that are created as a member of a CWAY element using the Cabling System module. There are some specific dependencies and limitations, refer to the following for further information:\nDependency on Cable Way Path Data\nDependency on Ancillary Properties\nLimitations on Functionality for Stacked Trays\nPosition on Tray Bend Tab\nPosition on Tray Tee Tab\nPosition on Tray Cross Tab\nPosition on Tray Riser Tab\nPosition on Tray Reducer Tab\nDependency on Cable Way Path Data\nDependency on Cable Way Path Data\nDependency on Ancillary Properties\nDependency on Ancillary Properties\nLimitations on Functionality for Stacked Trays\nLimitations on Functionality for Stacked Trays\nPosition on Tray Bend Tab\nPosition on Tray Bend Tab\nPosition on Tray Tee Tab\nPosition on Tray Tee Tab\nPosition on Tray Cross Tab\nPosition on Tray Cross Tab\nPosition on Tray Riser Tab\nPosition on Tray Riser Tab\nPosition on Tray Reducer Tab\nPosition on Tray Reducer Tab\n\n\n\nDependency on Cable Way Path Data\nDependency on Ancillary Properties\nLimitations on Functionality for Stacked Trays\nPosition on Tray Bend Tab\nPosition on Tray Tee Tab\nPosition on Tray Cross Tab\nPosition on Tray Riser Tab\nPosition on Tray Reducer Tab\nDependency on Cable Way Path Data\nDependency on Ancillary Properties\nLimitations on Functionality for Stacked Trays\nPosition on Tray Bend Tab\nPosition on Tray Tee Tab\nPosition on Tray Cross Tab\nPosition on Tray Riser Tab\nPosition on Tray Reducer Tab"}
{"Headers": "Dependency on Cable Way Path Data", "Content": "The Supports application is dependent on the correct definition of the cable way path data and the consistency of the dressed material. The inside radius is used to determine the bend start and end points for CTBEND and CTTEE elements, and hence if the support lies on a tangent straight or on the curve.\nIn the example, the inside radius has been defined as too short in the RPATH data (INSRAD of POSREF of the CTTEE), and so the start of the angle has moved away from the end of the tangent length where it would be expected to lie.\n\n\n\n"}
{"Headers": "Dependency on Ancillary Properties", "Content": "Setting the design parameter for tray width on the datum ancillary depends on a data set property being available, with a DKEY value of TWTH or OWID, and a PPRO value using a single design parameter, for example, ( ATTRIB DESP[8 ] ). Any customer defined ancillary must comply with this if the correct ancillary width is required, for example, when cable tray clips are used.\n\n\n\n"}
{"Headers": "Limitations on Functionality for Stacked Trays", "Content": "The application is currently limited in its ability to handle stacked trays on the same support. Positioning around the tray is limited by the combination of supported components. Using the example below, the support functions as expected on the straight line of the main branch but does not give good results if the support is moved to the P3 of the tee. If the results of any position change are not acceptable, click Reset to revert to the previously saved position.\n\n\n\n\nReset"}
{"Headers": "Position on Tray Bend Tab", "Content": "The Position on Tray Bend tab allows you to position a framework support on a cable tray bend. The framework support is positioned using a defined ppoint and a distance or angle value.\n\nFrom ppoint\nSelect from the drop-down list to specify the ppoint from which the distance or angle is measured.\nDistance\nInput a value in the field to explicitly modify the position of the support from the ppoint. The support is moved in a linear direction.\nAngle\nInput a value in the field to explicitly modify the position of the support from the ppoint. The support is moved around the radius of the bend.\nFrom ppoint\nSelect from the drop-down list to specify the ppoint from which the distance or angle is measured.\nDistance\nInput a value in the field to explicitly modify the position of the support from the ppoint. The support is moved in a linear direction.\nAngle\nInput a value in the field to explicitly modify the position of the support from the ppoint. The support is moved around the radius of the bend.\n\nClick Reset to revert the support to the position when the Position on Tray Bend tab was opened.\nClick Close to close the Position on Tray Bend tab when the support is in the desired position.\nFrom ppoint\nSelect from the drop-down list to specify the ppoint from which the distance or angle is measured.\nDistance\nInput a value in the field to explicitly modify the position of the support from the ppoint. The support is moved in a linear direction.\nAngle\nInput a value in the field to explicitly modify the position of the support from the ppoint. The support is moved around the radius of the bend.\n\n\n\nPosition on Tray Bend\nFrom ppoint\nDistance\nAngle\nReset\nPosition on Tray Bend\nClose\nPosition on Tray Bend"}
{"Headers": "Position on Tray Tee Tab", "Content": "The Position on Tray Tee tab allows you to position a framework support on a cable tray tee. The framework support is positioned using a defined ppoint and a distance or angle value.\n\nThe functionality is identical to positioning a support on a cable tray bend. Refer to Position on Tray Bend Tab for further information.\n\nNote:\nThe Angle field is not available when positioning a support from ppoint 3.\n\n\n\nPosition on Tray Bend Tab\nPosition on Tray Tee\nPosition on Tray Bend Tab\nNote\n:\nAngle"}
{"Headers": "Position on Tray Cross Tab", "Content": "The Position on Tray Cross tab allows you to position a framework support on a cable tray cross. The framework support is positioned using a defined ppoint and a distance value.\n\nThe functionality is identical to positioning a support on a cable tray bend. Refer to Position on Tray Bend Tab for further information.\n\nFramework CT03 can be positioned at an appropriate component endpoint when a cable tray direction is sideways.\nNote:\nThe Angle field is not available when positioning a support on a cable tray cross.\n\n\n\nPosition on Tray Bend Tab\nPosition on Tray Cross\nPosition on Tray Bend Tab\nNote\n:\nAngle"}
{"Headers": "Position on Tray Riser Tab", "Content": "The Position on Tray Riser tab allows you to position a framework support on a cable tray riser. The framework support is positioned using a defined ppoint, the distance is restricted to the tangent length of the riser.\n\nThe functionality is identical to positioning a support on a cable tray bend. Refer to Position on Tray Bend Tab for further information.\n\nFrameworks CT01, CT02 and CT04 can only be positioned on the horizontal end of the riser.\nNote:\nThe Angle field is not available when positioning a support on a cable tray riser.\n\n\n\nPosition on Tray Bend Tab\nPosition on Tray Riser\nPosition on Tray Bend Tab\nNote\n:\nAngle"}
{"Headers": "Position on Tray Reducer Tab", "Content": "The Position on Tray Reducer tab allows you to position a framework support on a cable tray reducer. The framework support is positioned using a defined ppoint and a distance value.\n\nThe functionality is identical to positioning a support on a cable tray bend. Refer to Position on Tray Bend Tab for further information.\nSupports on reducers take account of the angled centreline between the tangent ends.\n\nNote:\nThe Angle field is not available when positioning a support on a cable tray reducer.\n\n\n\nPosition on Tray Bend Tab\nPosition on Tray Reducer\nPosition on Tray Bend Tab\nNote\n:\nAngle"}
{"Headers": "Ancillary Tab", "Content": "By default, a separate tab displays on the Support Editor window for each ancillary associated with a support.\nThe 2D View part of the Support Editor window allows you to modify the size and position of the ancillary.\n\nThe values in the text fields can be modified to define the size and position of an ancillary.\nThe ancillary number displays at the top-left of the 2D view and corresponds to the ancillary number in the 3D view.\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the ancillary.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nAdditional Gussets\nSelect from the drop-down list to define the number of required additional gussets for the ancillary.\nReinforcing Pad\nSelect the check box to add a reinforcing pad to the ancillary. The reinforcing pad displays as a separate tab\nSet Height to Steel/Bedplate\nClick to set the height of the ancillary to align to a steelwork section or a bedplate. You must select a steelwork section or a bedplate using a a cursor pick in the 3D view.\nYou are prompted to Identify Steelwork to Support Shoe from\nSet Parameters to Default\nClick to set the ancillary to its default values.\nA confirm window displays asking you to OK the action. Click Yes to set the ancillary to its default values.\nAdd Associated Ancillary\nAllows you to create additional associated ancillaries. For example, guides, lugs, slip units and stops. Click to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries. Refer to Ancillary Selection for further information.\nEach associated ancillary displays as a separate tab.\nAdjust to Steelwork\nClick to align the ancillary to an associated steelwork section, guide or box using a cursor pick in the 3D view\nYou are prompted to Identify section to set height to\nAlternatively, you may be prompted to Identify section to bolt guide to\nAlternatively, you may be prompted to Identify section or box to stop\nReselect Ancillary Type\nAllows you to modify the ancillary type associated with the support. Click to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries. Refer to Ancillary Selection for further information.\nDistance/Clearance\nAllows you to position the ancillary support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position of the ancillary support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nSet Ancillary as Offline/Set Ancillary on Centre-Line\nAllows you to define the position of the ancillary.\nClick to display . The ancillary is created away from the centre-line of the pipe. For example, you may want to create an ancillary on a flange, a tee or on the start of a bend.\nClick to display . The ancillary is created on the centre-line of the pipe.\nNote:\nThe functionality is not available for Ancillary Components (AC), Branch Bracings (BR) and Manufacturer Hangers (MH) ancillaries because it should not be possible to create these ancillary types away from the centre-line of the pipe.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\n\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the ancillary.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\n\n\nAdditional Gussets\nSelect from the drop-down list to define the number of required additional gussets for the ancillary.\n\nReinforcing Pad\nSelect the check box to add a reinforcing pad to the ancillary. The reinforcing pad displays as a separate tab\n\nSet Height to Steel/Bedplate\nClick to set the height of the ancillary to align to a steelwork section or a bedplate. You must select a steelwork section or a bedplate using a a cursor pick in the 3D view.\nYou are prompted to Identify Steelwork to Support Shoe from\n\nSet Parameters to Default\nClick to set the ancillary to its default values.\nA confirm window displays asking you to OK the action. Click Yes to set the ancillary to its default values.\n\nAdd Associated Ancillary\nAllows you to create additional associated ancillaries. For example, guides, lugs, slip units and stops. Click to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries. Refer to Ancillary Selection for further information.\nEach associated ancillary displays as a separate tab.\n\nAdjust to Steelwork\nClick to align the ancillary to an associated steelwork section, guide or box using a cursor pick in the 3D view\nYou are prompted to Identify section to set height to\nAlternatively, you may be prompted to Identify section to bolt guide to\nAlternatively, you may be prompted to Identify section or box to stop\n\nReselect Ancillary Type\nAllows you to modify the ancillary type associated with the support. Click to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries. Refer to Ancillary Selection for further information.\n\nDistance/Clearance\nAllows you to position the ancillary support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nDistance from Support/Distance from pipe element\nAllows you to position of the ancillary support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nSet Ancillary as Offline/Set Ancillary on Centre-Line\nAllows you to define the position of the ancillary.\nClick to display . The ancillary is created away from the centre-line of the pipe. For example, you may want to create an ancillary on a flange, a tee or on the start of a bend.\nClick to display . The ancillary is created on the centre-line of the pipe.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the ancillary.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nAdditional Gussets\nSelect from the drop-down list to define the number of required additional gussets for the ancillary.\nReinforcing Pad\nSelect the check box to add a reinforcing pad to the ancillary. The reinforcing pad displays as a separate tab\nSet Height to Steel/Bedplate\nClick to set the height of the ancillary to align to a steelwork section or a bedplate. You must select a steelwork section or a bedplate using a a cursor pick in the 3D view.\nYou are prompted to Identify Steelwork to Support Shoe from\nSet Parameters to Default\nClick to set the ancillary to its default values.\nA confirm window displays asking you to OK the action. Click Yes to set the ancillary to its default values.\nAdd Associated Ancillary\nAllows you to create additional associated ancillaries. For example, guides, lugs, slip units and stops. Click to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries. Refer to Ancillary Selection for further information.\nEach associated ancillary displays as a separate tab.\nAdjust to Steelwork\nClick to align the ancillary to an associated steelwork section, guide or box using a cursor pick in the 3D view\nYou are prompted to Identify section to set height to\nAlternatively, you may be prompted to Identify section to bolt guide to\nAlternatively, you may be prompted to Identify section or box to stop\nReselect Ancillary Type\nAllows you to modify the ancillary type associated with the support. Click to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries. Refer to Ancillary Selection for further information.\nDistance/Clearance\nAllows you to position the ancillary support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position of the ancillary support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nSet Ancillary as Offline/Set Ancillary on Centre-Line\nAllows you to define the position of the ancillary.\nClick to display . The ancillary is created away from the centre-line of the pipe. For example, you may want to create an ancillary on a flange, a tee or on the start of a bend.\nClick to display . The ancillary is created on the centre-line of the pipe.\nNote:\nThe functionality is not available for Ancillary Components (AC), Branch Bracings (BR) and Manufacturer Hangers (MH) ancillaries because it should not be possible to create these ancillary types away from the centre-line of the pipe.\nNote:\nThe functionality is not available for Ancillary Components (AC), Branch Bracings (BR) and Manufacturer Hangers (MH) ancillaries because it should not be possible to create these ancillary types away from the centre-line of the pipe.\n\n\n\nAncillary Selection\nAncillary Selection\nPreliminary Tab\nPreliminary Tab\nSupport Editor\n2D View\nSupport Editor\nSelect default tab\nSelect ancillary tab by canvas pick\nIdentify ancillary in current support\nDimensions\nDimensions\nAdditional Gussets\nReinforcing Pad\nSet Height to Steel/Bedplate\nIdentify Steelwork to Support Shoe from\nSet Parameters to Default\nYes\nAdd Associated Ancillary\nAncillary Selection\nAncillary Selection\nAncillary Selection\nAdjust to Steelwork\nIdentify section to set height to\nIdentify section to bolt guide to\nIdentify section or box to stop\nReselect Ancillary Type\nAncillary Selection\nAncillary Selection\nAncillary Selection\nDistance/Clearance\nPreliminary Tab\nDistance from Support/Distance from pipe element\nPreliminary Tab\nSet Ancillary as Offline/Set Ancillary on Centre-Line\nNote\n:"}
{"Headers": "Ancillary Selection", "Content": "Displays a filtered list of all available/unavailable ancillaries for the selected pipe bore.\n\nAvailable\nThe Available tab allows you to select an ancillary from a filtered list of available ancillaries that are suitable for the pipe to be supported.\nThe bottom part of the window displays the specification of the pipe that the support is to be associated with.\nUnavailable\nThe Unavailable tab displays a filtered list of ancillaries that are not suitable for the pipe to be supported.\nThe bottom part of the window indicates why the currently selected ancillary is not suitable for the pipe to be supported.\n\nPreview\nThe Preview part of the Ancillary Selection window allows you to view a 2D representation of the currently selected ancillary.\n\n\n\nAvailable\nAvailable\nUnavailable\nUnavailable\nPreview\nPreview\nAncillary Selection"}
{"Headers": "Filter Ancillary Type", "Content": "The List By Type part of the Ancillary Selection window allows you to define the list of available ancillaries by type.\nAll\nClick to display all available ancillaries in the list of available/unavailable ancillaries.\nAnchors\nClick to display all available anchors in the list of available/unavailable ancillaries.\nAncillaries\nClick to display all available ancillaries in the list of available/unavailable ancillaries.\nBolts\nClick to display all available bolts in the list of available/unavailable ancillaries.\nGuides\nClick to display all available guides in the list of available/unavailable ancillaries.\nLugs\nClick to display all available lugs in the list of available/unavailable ancillaries.\nRests\nClick to display all available rests in the list of available/unavailable ancillaries.\nSlip Units\nClick to display all available slip units in the list of available/unavailable ancillaries.\nStops\nClick to display all available stops in the list of available/unavailable ancillaries.\nAll\nClick to display all available ancillaries in the list of available/unavailable ancillaries.\nAnchors\nClick to display all available anchors in the list of available/unavailable ancillaries.\nAncillaries\nClick to display all available ancillaries in the list of available/unavailable ancillaries.\nBolts\nClick to display all available bolts in the list of available/unavailable ancillaries.\nGuides\nClick to display all available guides in the list of available/unavailable ancillaries.\nLugs\nClick to display all available lugs in the list of available/unavailable ancillaries.\nRests\nClick to display all available rests in the list of available/unavailable ancillaries.\nSlip Units\nClick to display all available slip units in the list of available/unavailable ancillaries.\nStops\nClick to display all available stops in the list of available/unavailable ancillaries.\n\nAll\nClick to display all available ancillaries in the list of available/unavailable ancillaries.\nAnchors\nClick to display all available anchors in the list of available/unavailable ancillaries.\nAncillaries\nClick to display all available ancillaries in the list of available/unavailable ancillaries.\nBolts\nClick to display all available bolts in the list of available/unavailable ancillaries.\nGuides\nClick to display all available guides in the list of available/unavailable ancillaries.\nLugs\nClick to display all available lugs in the list of available/unavailable ancillaries.\nRests\nClick to display all available rests in the list of available/unavailable ancillaries.\nSlip Units\nClick to display all available slip units in the list of available/unavailable ancillaries.\nStops\nClick to display all available stops in the list of available/unavailable ancillaries.\n\n\n\nList By Type\nAncillary Selection\nAll\nAnchors\nAncillaries\nBolts\nGuides\nLugs\nRests\nSlip Units\nStops"}
{"Headers": "View Ancillary Standard", "Content": "The Ancillary Selection window allows you to view an illustration of the selected ancillary, click View to display the View Multi Discipline Standard window.\nThe functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\n\n\n\nView Multi Discipline Support Standard\nAncillary Selection\nView\nView Multi Discipline Standard\nView Multi Discipline Standard\nView Multi Discipline Support Standard"}
{"Headers": "Branch Reinforcement Tab", "Content": "By default, a separate tab displays on the Support Editor window for each branch reinforcement.\nThe 2D View part of the Support Editor window allows you to modify the size and position of the branch reinforcement.\n\nThe values in the text fields can be modified to define the size and position of a branch reinforcement.\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the branch reinforcement. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the branch reinforcement.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nReinforcing Pad\nSelect the check box to add a reinforcing pad to the branch reinforcement.\nType\nSelect from the drop-down list to define the reinforcing pad type for the branch reinforcement.\nThickness\nInput a dimensional value in the field to define the thickness of the reinforcing pad.\nClearance\nInput a dimensional value in the field to define the clearance distance required for the reinforcing pad.\nAxial Adjustment\nInput a dimensional value in the field to define the position of the reinforcing pad connections along the pipe axis.\nRadial Adjustment\nInput a dimensional value in the field to define the position of the reinforcing pad connections along the pipe radius.\nSet Parameters to Default\nClick to set the branch reinforcement to its default values.\nA confirm window displays asking you to OK the action. Click Yes to set the branch reinforcement to its default values.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\n\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n\n2D/3D View\nClick to display a 3D view of the branch reinforcement. Refer to 3D View Tab for further information.\n\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the branch reinforcement.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\n\n\nReinforcing Pad\nSelect the check box to add a reinforcing pad to the branch reinforcement.\n\nType\nSelect from the drop-down list to define the reinforcing pad type for the branch reinforcement.\n\n\nThickness\nInput a dimensional value in the field to define the thickness of the reinforcing pad.\n\nClearance\nInput a dimensional value in the field to define the clearance distance required for the reinforcing pad.\n\nAxial Adjustment\nInput a dimensional value in the field to define the position of the reinforcing pad connections along the pipe axis.\n\nRadial Adjustment\nInput a dimensional value in the field to define the position of the reinforcing pad connections along the pipe radius.\n\nSet Parameters to Default\nClick to set the branch reinforcement to its default values.\nA confirm window displays asking you to OK the action. Click Yes to set the branch reinforcement to its default values.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the branch reinforcement. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the branch reinforcement.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nReinforcing Pad\nSelect the check box to add a reinforcing pad to the branch reinforcement.\nType\nSelect from the drop-down list to define the reinforcing pad type for the branch reinforcement.\nThickness\nInput a dimensional value in the field to define the thickness of the reinforcing pad.\nClearance\nInput a dimensional value in the field to define the clearance distance required for the reinforcing pad.\nAxial Adjustment\nInput a dimensional value in the field to define the position of the reinforcing pad connections along the pipe axis.\nRadial Adjustment\nInput a dimensional value in the field to define the position of the reinforcing pad connections along the pipe radius.\nSet Parameters to Default\nClick to set the branch reinforcement to its default values.\nA confirm window displays asking you to OK the action. Click Yes to set the branch reinforcement to its default values.\n\n\n\n3D View Tab\nSupport Editor\n2D View\nSupport Editor\nSelect default tab\nSelect ancillary tab by canvas pick\nIdentify ancillary in current support\n2D/3D View\n3D View Tab\nDimensions\nDimensions\nReinforcing Pad\nType\nThickness\nClearance\nAxial Adjustment\nRadial Adjustment\nSet Parameters to Default\nYes"}
{"Headers": "Trunnion Tab", "Content": "By default, a separate tab displays on the Support Editor window for the trunnion and each of the associated ancillaries.\nThe 2D View part of the Support Editor window allows you to modify the size and position of the trunnion and each of the associated ancillaries.\n\nThe values in the text fields can be modified to define the size and position of a trunnion.\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the trunnion. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the trunnion.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nBore\nSelect from the drop-down list to define the bore size of the trunnion leg.\nPlate\nSelect from the drop-down list to define a plate for the Trunnion.\nSet Trunnion Height by pick\nClick to modify the height of the trunnion using a cursor pick in the 3D view. For example to align to a floor or wall element.\nYou are prompted to Identify element to set trunnion to\nSet Trunnion Material\nAllows you to modify the material for the trunnion. Refer to Modify Trunnion Material for further information.\nCreate Base Component\nAllows you to associate an additional ancillary with the base of the trunnion. Click to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries. Refer to Ancillary Selection for further information.\nThe associated ancillary displays as a separate tab.\nComponent - Click to Support Pipe\nAllows you to define the position of the trunnion. Click to move the trunnion from an elbow, tee, bend or reducer to the tube of the pipe.\nBy default, the trunnion size and the associated ancillaries are modified by the supports application, if required.\nPipe - Click to Support Component\nAllows you to define the position of the trunnion. Click to position the trunnion from the tube of the pipe to an elbow, tee, bend or reducer.\nBy default, the trunnion size and the associated ancillaries are modified by the supports application, if required.\nDistance/Clearance\nAllows you to position the trunnion. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position of the trunnion. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\n\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n\n2D/3D View\nClick to display a 3D view of the trunnion. Refer to 3D View Tab for further information.\n\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the trunnion.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\n\n\nBore\nSelect from the drop-down list to define the bore size of the trunnion leg.\n\nPlate\nSelect from the drop-down list to define a plate for the Trunnion.\n\nSet Trunnion Height by pick\nClick to modify the height of the trunnion using a cursor pick in the 3D view. For example to align to a floor or wall element.\nYou are prompted to Identify element to set trunnion to\n\nSet Trunnion Material\nAllows you to modify the material for the trunnion. Refer to Modify Trunnion Material for further information.\n\nCreate Base Component\nAllows you to associate an additional ancillary with the base of the trunnion. Click to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries. Refer to Ancillary Selection for further information.\nThe associated ancillary displays as a separate tab.\n\nComponent - Click to Support Pipe\nAllows you to define the position of the trunnion. Click to move the trunnion from an elbow, tee, bend or reducer to the tube of the pipe.\nBy default, the trunnion size and the associated ancillaries are modified by the supports application, if required.\n\nPipe - Click to Support Component\nAllows you to define the position of the trunnion. Click to position the trunnion from the tube of the pipe to an elbow, tee, bend or reducer.\nBy default, the trunnion size and the associated ancillaries are modified by the supports application, if required.\n\nDistance/Clearance\nAllows you to position the trunnion. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nDistance from Support/Distance from pipe element\nAllows you to position of the trunnion. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the trunnion. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the trunnion.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nBore\nSelect from the drop-down list to define the bore size of the trunnion leg.\nPlate\nSelect from the drop-down list to define a plate for the Trunnion.\nSet Trunnion Height by pick\nClick to modify the height of the trunnion using a cursor pick in the 3D view. For example to align to a floor or wall element.\nYou are prompted to Identify element to set trunnion to\nSet Trunnion Material\nAllows you to modify the material for the trunnion. Refer to Modify Trunnion Material for further information.\nCreate Base Component\nAllows you to associate an additional ancillary with the base of the trunnion. Click to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries. Refer to Ancillary Selection for further information.\nThe associated ancillary displays as a separate tab.\nComponent - Click to Support Pipe\nAllows you to define the position of the trunnion. Click to move the trunnion from an elbow, tee, bend or reducer to the tube of the pipe.\nBy default, the trunnion size and the associated ancillaries are modified by the supports application, if required.\nPipe - Click to Support Component\nAllows you to define the position of the trunnion. Click to position the trunnion from the tube of the pipe to an elbow, tee, bend or reducer.\nBy default, the trunnion size and the associated ancillaries are modified by the supports application, if required.\nDistance/Clearance\nAllows you to position the trunnion. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position of the trunnion. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\n\n\n3D View Tab\nModify Trunnion Material\nAncillary Selection\nPreliminary Tab\nPreliminary Tab\nSupport Editor\n2D View\nSupport Editor\nSelect default tab\nSelect ancillary tab by canvas pick\nIdentify ancillary in current support\n2D/3D View\n3D View Tab\nDimensions\nDimensions\nBore\nPlate\nSet Trunnion Height by pick\nIdentify element to set trunnion to\nSet Trunnion Material\nModify Trunnion Material\nCreate Base Component\nAncillary Selection\nAncillary Selection\nAncillary Selection\nComponent - Click to Support Pipe\nPipe - Click to Support Component\nDistance/Clearance\nPreliminary Tab\nDistance from Support/Distance from pipe element\nPreliminary Tab"}
{"Headers": "Modify Trunnion Material", "Content": "Sets the material for the trunnion.\n\nThe Select Trunnion Material window displays all available materials for the currently selected trunnion.\nSelect a material from the list of available materials.\nClick OK to apply the material or Cancel to discard any inputs and close the Select Trunnion Material window.\n\n\n\nSelect Trunnion Material\nOK\nCancel\nSelect Trunnion Material"}
{"Headers": "Hanger Tab", "Content": "By default, a separate tab displays on the Support Editor window for the hanger and each of the associated ancillaries.\nThe 2D View part of the Support Editor window allows you to modify the size and position of the hanger and each of the associated ancillaries.\n\nThe values in the text fields can be modified to define the size and position of a hanger.\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the hanger. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the hanger.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nChange hanger rod size\nAllows you to modify the size of the hanger rod. Refer to Modify Hanger Rod Size for further information.\nSelect spring for hanger\nAllows you to modify the spring type for the hanger. Refer to Modify Hanger Spring Type for further information.\nModify Spring Travel\nAllows you to modify the spring travel for the hanger. Refer to Modify Hanger Spring Travel for further information.\nDistance/Clearance\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position of the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\n\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n\n2D/3D View\nClick to display a 3D view of the hanger. Refer to 3D View Tab for further information.\n\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the hanger.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\n\n\nChange hanger rod size\nAllows you to modify the size of the hanger rod. Refer to Modify Hanger Rod Size for further information.\n\nSelect spring for hanger\nAllows you to modify the spring type for the hanger. Refer to Modify Hanger Spring Type for further information.\n\nModify Spring Travel\nAllows you to modify the spring travel for the hanger. Refer to Modify Hanger Spring Travel for further information.\n\nDistance/Clearance\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nDistance from Support/Distance from pipe element\nAllows you to position of the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the hanger. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the hanger.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nChange hanger rod size\nAllows you to modify the size of the hanger rod. Refer to Modify Hanger Rod Size for further information.\nSelect spring for hanger\nAllows you to modify the spring type for the hanger. Refer to Modify Hanger Spring Type for further information.\nModify Spring Travel\nAllows you to modify the spring travel for the hanger. Refer to Modify Hanger Spring Travel for further information.\nDistance/Clearance\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position of the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\n\n\n3D View Tab\nModify Hanger Rod Size\nModify Hanger Spring Type\nModify Hanger Spring Travel\nPreliminary Tab\nPreliminary Tab\nSupport Editor\n2D View\nSupport Editor\nSelect default tab\nSelect ancillary tab by canvas pick\nIdentify ancillary in current support\n2D/3D View\n3D View Tab\nDimensions\nDimensions\nChange hanger rod size\nModify Hanger Rod Size\nSelect spring for hanger\nModify Hanger Spring Type\nModify Spring Travel\nModify Hanger Spring Travel\nDistance/Clearance\nPreliminary Tab\nDistance from Support/Distance from pipe element\nPreliminary Tab"}
{"Headers": "Modify Hanger Rod Size", "Content": "Sets the size of the hanger rod.\n\nThe current rod size displays at the top of the window.\nThe Change Hanger Rod Size window displays all available rod sizes for the currently selected hanger.\nSelect a rod size from the list of available rod sizes.\nClick OK to modify the rod size or Cancel to discard any inputs and close the Change Hanger Rod Size window.\n\n\n\nChange Hanger Rod Size\nOK\nCancel\nChange Hanger Rod Size"}
{"Headers": "Modify Hanger Spring Type", "Content": "Modifies the hanger spring type.\n\nThe setting, current bore and specification status display at the top of the CHOOSE VSPR window.\nSelect a component from the list of available components sorted by STYP, TTYP and UTYP.\nClick OK to modify the component or Cancel to discard any changes and close the CHOOSE VSPR window.\n\n\n\nCHOOSE VSPR\nOK\nCancel\nCHOOSE VSPR"}
{"Headers": "Modify Hanger Spring Travel", "Content": "Modifies the hanger spring travel distance.\n\nThe name of the spring, and the owning hanger, displays at the top of the Modify Spring/Constant Travel window.\nInput a value in the field to define the spring travel distance.\nThe minimum and maximum allowable travel distances display at the bottom of the window.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\n\nClick Cancel to close the Modify Spring/Constant Travel window.\n\n\n\nModify Spring/Constant Travel\nCancel\nModify Spring/Constant Travel"}
{"Headers": "Specials Tab", "Content": "The Specials tab allows you to position a special support. The special support can also be viewed in a 3D view.\n\nThe value in the text field can be modified to define the position of a special support.\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the special support and the associated ancillaries. Refer to 3D View Tab for further information.\nCreate support connection\nAllows you to connect a special support section to a supporting element. For example, a structural section.\nYou are prompted to Pick support section\nYou must identify the special support section for connection using a cursor pick in the 3D view.\nYou are then prompted to Pick element to connect\nYou must identify the structural section for connection using a cursor pick in the 3D view.\nThe support is modified using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified elements. Refer to Supports Connectivity for further information.\nCreate Bracing\nAllows you to define bracing for the framework support. Refer to Bracing for further information.\nCreate Crossbar\nClick to add a crossbar to a framework support. You must identify one or more ancillaries to associate with the crossbar using a cursor pick in the 3D view.\nYou are prompted to Identify Ancillary to support\nYou can continue to identify additional ancillaries using a cursor pick in the 3D view.\nPress ESC to add the crossbar.\nDistance/Clearance\nAllows you to position the special support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position of the special support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\n\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n\n2D/3D View\nClick to display a 3D view of the special support and the associated ancillaries. Refer to 3D View Tab for further information.\n\nCreate support connection\nAllows you to connect a special support section to a supporting element. For example, a structural section.\n\nYou are prompted to Pick support section\nYou must identify the special support section for connection using a cursor pick in the 3D view.\nYou are then prompted to Pick element to connect\nYou must identify the structural section for connection using a cursor pick in the 3D view.\nThe support is modified using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified elements. Refer to Supports Connectivity for further information.\n\n\nCreate Bracing\nAllows you to define bracing for the framework support. Refer to Bracing for further information.\n\nCreate Crossbar\nClick to add a crossbar to a framework support. You must identify one or more ancillaries to associate with the crossbar using a cursor pick in the 3D view.\nYou are prompted to Identify Ancillary to support\nYou can continue to identify additional ancillaries using a cursor pick in the 3D view.\nPress ESC to add the crossbar.\n\nDistance/Clearance\nAllows you to position the special support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nDistance from Support/Distance from pipe element\nAllows you to position of the special support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the special support and the associated ancillaries. Refer to 3D View Tab for further information.\nCreate support connection\nAllows you to connect a special support section to a supporting element. For example, a structural section.\nYou are prompted to Pick support section\nYou must identify the special support section for connection using a cursor pick in the 3D view.\nYou are then prompted to Pick element to connect\nYou must identify the structural section for connection using a cursor pick in the 3D view.\nThe support is modified using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified elements. Refer to Supports Connectivity for further information.\nCreate Bracing\nAllows you to define bracing for the framework support. Refer to Bracing for further information.\nCreate Crossbar\nClick to add a crossbar to a framework support. You must identify one or more ancillaries to associate with the crossbar using a cursor pick in the 3D view.\nYou are prompted to Identify Ancillary to support\nYou can continue to identify additional ancillaries using a cursor pick in the 3D view.\nPress ESC to add the crossbar.\nDistance/Clearance\nAllows you to position the special support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position of the special support. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\n\n\n3D View Tab\nSupports Connectivity\nBracing\nPreliminary Tab\nPreliminary Tab\nSelect default tab\nSelect ancillary tab by canvas pick\nIdentify ancillary in current support\n2D/3D View\n3D View Tab\nCreate support connection\nPick support section\nPick element to connect\nSupports Connectivity\nCreate Bracing\nBracing\nCreate Crossbar\nIdentify Ancillary to support\nESC\nDistance/Clearance\nPreliminary Tab\nDistance from Support/Distance from pipe element\nPreliminary Tab"}
{"Headers": "Lighting Tab", "Content": "The Lighting tab allows you to position a lighting support. The lighting support can also be viewed in a 3D view.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the special support and the associated ancillaries. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the lighting support.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nBuild by Cursor\nClick to identify the element to support from using a cursor pick in the 3D view.\nYou are prompted to Pick surface of ceiling/wall to connect to\nThe support is created using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified supporting elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\n\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\n\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n\n2D/3D View\nClick to display a 3D view of the special support and the associated ancillaries. Refer to 3D View Tab for further information.\n\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the lighting support.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\n\n\nBuild by Cursor\nClick to identify the element to support from using a cursor pick in the 3D view.\nYou are prompted to Pick surface of ceiling/wall to connect to\nThe support is created using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified supporting elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\nBy default, the Select Required Template window is displayed when the Lighting tab is displayed which allows you to modify the lighting support template. Refer to Select Required Template for further information.\nSelect default tab\nClick to display the default tab. The default tab is the first tab created and is positioned furthest left.\nSelect ancillary tab by canvas pick\nClick to display the tab for an identified ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary in current support\n2D/3D View\nClick to display a 3D view of the special support and the associated ancillaries. Refer to 3D View Tab for further information.\nDimensions\nInput values in the Dimensions fields to explicitly modify the dimensions of the lighting support.\nIf a value is entered that is outside the allowable range, an error message displays summarizing the problem.\nBuild by Cursor\nClick to identify the element to support from using a cursor pick in the 3D view.\nYou are prompted to Pick surface of ceiling/wall to connect to\nThe support is created using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified supporting elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\n\n\n\n3D View Tab\nSupports Connectivity\nSelect Required Template\nSelect default tab\nSelect ancillary tab by canvas pick\nIdentify ancillary in current support\n2D/3D View\n3D View Tab\nDimensions\nDimensions\nBuild by Cursor\nPick surface of ceiling/wall to connect to\nDimensions\nSupports Connectivity\nSelect Required Template\nSelect Required Template"}
{"Headers": "Select Required Template", "Content": "The Select Required Template window allows you to select a lighting support template.\n\nSelect a lighting support template from the list of available templates, the template displays in the 3D view.\nThe Filter field allows you to restrict the elements shown in the list to names containing given characters. By default, the list displays all elements of the given type, as indicated by the * in the Filter fields. The wildcards available are:\nThe Show drop-down list allows you to filter the list of available templates by type, select All, Wall Mounted or Ceiling Mounted.\nSelect the Mirror check box to reposition the template with respect to a specified plane.\nClick Cancel to close the Select Required Template window.\n* Any number of any characters\n? Single character\n* Any number of any characters\n* Any number of any characters\n? Single character\n? Single character\n\n\n\nFilter\nShow\nAll\nWall Mounted\nCeiling Mounted\nMirror\nCancel"}
{"Headers": "Witch Hanger Manufacturer\u2019s Interface", "Content": "By default, a separate tab displays on the Support Editor window for the hanger and the associated load data values.\nThe 2D View part of the Support Editor window allows you to modify the size and position of the hanger.\n\n2D/3D View\nClick to display a 3D view of the hanger. Refer to 3D View Tab for further information.\nWitch Hanger Interface\nClick to display the Witch Hanger interface.\nDistance/Clearance\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to to Preliminary Tab for further information.\n\n2D/3D View\nClick to display a 3D view of the hanger. Refer to 3D View Tab for further information.\n\nWitch Hanger Interface\nClick to display the Witch Hanger interface.\n\nDistance/Clearance\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nDistance from Support/Distance from pipe element\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to to Preliminary Tab for further information.\nThe Data part of the Support Editor window allows you to modify the applicable loading values for transfer to the manufacturer\u2019s interface.\n\nInput values in the fields to define the applicable load values for the hanger.\nIf a modification is made to the hanger in AVEVA E3D Design, the hanger must be checked in the Witch Hanger interface before it can be applied. A message displays at the bottom of the Support Editor window indicating that the hanger must be checked in the Witch Hanger interface.\n\nThe hanger interface software stores hanger interface transfer data using a known file structure within the current project.\nFor example, if the APS (Aveva Plant Sample) project is being used, the following file structure is generated.\n/AvevaPlantSample\n/AvevaPlantSample/apshid\n/AvevaPlantSample/apshid/cplData\n/AvevaPlantSample/apshid/cplData/interfaceDB\n/AvevaPlantSample/apshid/cplData/legacyIO\n/AvevaPlantSample/apshid/cplData/xmlTransfer\n/AvevaPlantSample/apshid/cplData/legacyIO/if\n/AvevaPlantSample/apshid/cplData/legacyIO/of\n2D/3D View\nClick to display a 3D view of the hanger. Refer to 3D View Tab for further information.\nWitch Hanger Interface\nClick to display the Witch Hanger interface.\nDistance/Clearance\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to to Preliminary Tab for further information.\n\n\n\n3D View Tab\nPreliminary Tab\nPreliminary Tab\nSupport Editor\n2D View\nSupport Editor\n2D/3D View\n3D View Tab\nWitch Hanger Interface\nDistance/Clearance\nPreliminary Tab\nDistance from Support/Distance from pipe element\nPreliminary Tab\nData\nSupport Editor\nAVEVA E3D Design\nSupport Editor"}
{"Headers": "LICAD Manufacturer\u2019s Interface", "Content": "By default, a separate tab displays on the Support Editor window for the hanger and the associated load data values.\nThe 2D View part of the Support Editor window allows you to modify the size and position of the hanger.\n\n2D/3D View\nClick to display a 3D view of the hanger. Refer to 3D View Tab for further information.\nLICAD Interface\nClick to display the LICAD interface.\nDistance/Clearance\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\n2D/3D View\nClick to display a 3D view of the hanger. Refer to 3D View Tab for further information.\n\nLICAD Interface\nClick to display the LICAD interface.\n\nDistance/Clearance\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\nDistance from Support/Distance from pipe element\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nThe Data part of the Support Editor window allows you to modify the applicable loading values for transfer to the manufacturer\u2019s interface.\n\nInput values in the fields to define the applicable load values for the hanger.\nIf a modification is made to the hanger in AVEVA E3D Design, the hanger must be checked in the LICAD interface before it can be applied. A message displays at the bottom of the Support Editor window indicating that the hanger must be checked in the LICAD interface.\n\nThe hanger interface software stores hanger interface transfer data using a known file structure within the current project.\nFor example, if the APS (Aveva Plant Sample) project is being used, the following file structure is generated.\n/AvevaPlantSample\n/AvevaPlantSample/apshid\n/AvevaPlantSample/apshid/lisegaData\n/AvevaPlantSample/apshid/lisegaData/interfaceDB\n/AvevaPlantSample/apshid/lisegaData/legacyIO\n/AvevaPlantSample/apshid/lisegaData/xmlTransfer\n/AvevaPlantSample/apshid/lisegaData/LegacyIO/if\n/AvevaPlantSample/apshid/lisegaData/LegacyIO/of\n2D/3D View\nClick to display a 3D view of the hanger. Refer to 3D View Tab for further information.\nLICAD Interface\nClick to display the LICAD interface.\nDistance/Clearance\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\nDistance from Support/Distance from pipe element\nAllows you to position the hanger. The functionality is identical to the positioning of a preliminary support. Refer to Preliminary Tab for further information.\n\n\n\n3D View Tab\nPreliminary Tab\nPreliminary Tab\nSupport Editor\n2D View\nSupport Editor\n2D/3D View\n3D View Tab\nLICAD Interface\nDistance/Clearance\nPreliminary Tab\nDistance from Support/Distance from pipe element\nPreliminary Tab\nData\nSupport Editor\nAVEVA E3D Design\nSupport Editor"}
{"Headers": "Common Functions", "Content": "The Common part of the Support Editor window allows you to add a pipe, HVAC duct, cable tray, or guide to a support. Functionality is also available to position the support, rotate a support and the associated ancillaries and modify the steelwork template.\n\nSupport additional pipe HVAC, or cable tray\nClick to add a pipe, HVAC duct or cable tray to a support. You must identify the element using a cursor pick in the 3D view.\nYou are prompted to Identify element you wish to support\nOnce the selection is made, the Ancillary Selection window displays. You must select an ancillary from the list of available ancillaries. The functionality of the Ancillary Selection window is explained. Refer to Ancillary Selection for further information.\nThe new ancillary is created and displays on the Support Editor window as a new tab.\nPosition Through\nAllows you to position the support through a picked element. Refer to Position Through a Picked Element for further information.\nRotate\nClick to rotate the support 180 degrees around the datum position.\nRotate Component\nAllows you to rotate an individual support or hanger ancillary. Refer to Rotate Component or Rotate Hanger Component for further information.\nSet Steelwork Template\nAllows you to modify the steelwork template for the framework support. Refer to Modify Steelwork Template for further information.\nSet Framework Orthogonal to Pipe or Cable tray\nClick to modify the position of the support framework with respect to the supported sloped pipe or cable tray. The support framework position can be orthogonal or non-orthogonal with respect to the supported sloped pipe or cable tray.\n\nSupport additional pipe HVAC, or cable tray\nClick to add a pipe, HVAC duct or cable tray to a support. You must identify the element using a cursor pick in the 3D view.\nYou are prompted to Identify element you wish to support\nOnce the selection is made, the Ancillary Selection window displays. You must select an ancillary from the list of available ancillaries. The functionality of the Ancillary Selection window is explained. Refer to Ancillary Selection for further information.\nThe new ancillary is created and displays on the Support Editor window as a new tab.\n\nPosition Through\nAllows you to position the support through a picked element. Refer to Position Through a Picked Element for further information.\n\nRotate\nClick to rotate the support 180 degrees around the datum position.\n\nRotate Component\nAllows you to rotate an individual support or hanger ancillary. Refer to Rotate Component or Rotate Hanger Component for further information.\n\nSet Steelwork Template\nAllows you to modify the steelwork template for the framework support. Refer to Modify Steelwork Template for further information.\n\nSet Framework Orthogonal to Pipe or Cable tray\nClick to modify the position of the support framework with respect to the supported sloped pipe or cable tray. The support framework position can be orthogonal or non-orthogonal with respect to the supported sloped pipe or cable tray.\n\n\nSupport additional pipe HVAC, or cable tray\nClick to add a pipe, HVAC duct or cable tray to a support. You must identify the element using a cursor pick in the 3D view.\nYou are prompted to Identify element you wish to support\nOnce the selection is made, the Ancillary Selection window displays. You must select an ancillary from the list of available ancillaries. The functionality of the Ancillary Selection window is explained. Refer to Ancillary Selection for further information.\nThe new ancillary is created and displays on the Support Editor window as a new tab.\nPosition Through\nAllows you to position the support through a picked element. Refer to Position Through a Picked Element for further information.\nRotate\nClick to rotate the support 180 degrees around the datum position.\nRotate Component\nAllows you to rotate an individual support or hanger ancillary. Refer to Rotate Component or Rotate Hanger Component for further information.\nSet Steelwork Template\nAllows you to modify the steelwork template for the framework support. Refer to Modify Steelwork Template for further information.\nSet Framework Orthogonal to Pipe or Cable tray\nClick to modify the position of the support framework with respect to the supported sloped pipe or cable tray. The support framework position can be orthogonal or non-orthogonal with respect to the supported sloped pipe or cable tray.\n\n\n\nAncillary Selection\nPosition Through a Picked Element\nRotate Component\nRotate Hanger Component\nModify Steelwork Template\nCommon\nSupport Editor\nSupport additional pipe HVAC, or cable tray\nIdentify element you wish to support\nAncillary Selection\nAncillary Selection\nAncillary Selection\nSupport Editor\nPosition Through\nPosition Through a Picked Element\nRotate\nRotate Component\nRotate Component\nRotate Hanger Component\nSet Steelwork Template\nModify Steelwork Template\nSet Framework Orthogonal to Pipe or Cable tray"}
{"Headers": "Position Through a Picked Element", "Content": "Displays the Position Through tab and the Positioning Control window. Refer to Positioning Control for further information.\n\nThe Position Through tab allows you to align a support to a picked element or move a support explicitly.\nCurrent Selection\nBy default, the Pline NA of the first vertical member on the support is selected as the point to align. If this does not exist, the Pline NA of the first support member is selected as the point to align.\nClick Change to modify the support member to align.\nYou must identify the support member using a cursor pick in the 3D view.\nYou are prompted to Select Origin Choose element to align from (Distance [0]) Snap :\nAlign along pipe\nAligns the support along the pipe.\nClick to identify the element to align the support with using a cursor pick in the 3D view.\nYou are prompted to Pick point to align with (Distance [0]) Snap :\nAlign in horizontal plane\nAligns the support on a horizontal plane. The functionality is only available for supports on sloped pipes.\nClick to identify the element to align the support with using a cursor pick in the 3D view.\nYou are prompted to Pick point to align with (Distance [0]) Snap :\nAlign in vertical plane\nAligns the support on a vertical plane. The functionality is only available for supports on sloped pipes.\nClick to identify the element to align the support with using a cursor pick in the 3D view.\nYou are prompted to Pick point to align with (Distance [0]) Snap :\nMove By Distance\nInput a dimensional value in the field to move the support explicitly.\n\nCurrent Selection\nBy default, the Pline NA of the first vertical member on the support is selected as the point to align. If this does not exist, the Pline NA of the first support member is selected as the point to align.\nClick Change to modify the support member to align.\nYou must identify the support member using a cursor pick in the 3D view.\nYou are prompted to Select Origin Choose element to align from (Distance [0]) Snap :\n\nAlign along pipe\nAligns the support along the pipe.\nClick to identify the element to align the support with using a cursor pick in the 3D view.\nYou are prompted to Pick point to align with (Distance [0]) Snap :\n\nAlign in horizontal plane\nAligns the support on a horizontal plane. The functionality is only available for supports on sloped pipes.\nClick to identify the element to align the support with using a cursor pick in the 3D view.\nYou are prompted to Pick point to align with (Distance [0]) Snap :\n\nAlign in vertical plane\nAligns the support on a vertical plane. The functionality is only available for supports on sloped pipes.\nClick to identify the element to align the support with using a cursor pick in the 3D view.\nYou are prompted to Pick point to align with (Distance [0]) Snap :\n\nMove By Distance\nInput a dimensional value in the field to move the support explicitly.\nWhen the support is aligned or moved, the 3D view displays the new location, the original location displays as an outline.\n\nClick Reset to return the support to the original position or Close to close the Position Through tab.\nCurrent Selection\nBy default, the Pline NA of the first vertical member on the support is selected as the point to align. If this does not exist, the Pline NA of the first support member is selected as the point to align.\nClick Change to modify the support member to align.\nYou must identify the support member using a cursor pick in the 3D view.\nYou are prompted to Select Origin Choose element to align from (Distance [0]) Snap :\nAlign along pipe\nAligns the support along the pipe.\nClick to identify the element to align the support with using a cursor pick in the 3D view.\nYou are prompted to Pick point to align with (Distance [0]) Snap :\nAlign in horizontal plane\nAligns the support on a horizontal plane. The functionality is only available for supports on sloped pipes.\nClick to identify the element to align the support with using a cursor pick in the 3D view.\nYou are prompted to Pick point to align with (Distance [0]) Snap :\nAlign in vertical plane\nAligns the support on a vertical plane. The functionality is only available for supports on sloped pipes.\nClick to identify the element to align the support with using a cursor pick in the 3D view.\nYou are prompted to Pick point to align with (Distance [0]) Snap :\nMove By Distance\nInput a dimensional value in the field to move the support explicitly.\n\n\n\nPositioning Control\nPosition Through\nPositioning Control\nPositioning Control\nPosition Through\nCurrent Selection\nChange\nSelect Origin Choose element to align from (Distance [0]) Snap :\nAlign along pipe\nPick point to align with (Distance [0]) Snap :\nAlign in horizontal plane\nPick point to align with (Distance [0]) Snap :\nAlign in vertical plane\nPick point to align with (Distance [0]) Snap :\nMove By Distance\nReset\nClose\nPosition Through"}
{"Headers": "Rotate Component", "Content": "Rotates an individual support ancillary.\nIf the support contains more than one ancillary, or an ancillary is not currently selected, you must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary to rotate\n\nThe ancillary name displays at the top of the Rotate Ancillary window.\nInput a value in the Angle field to rotate the ancillary. For example input 180 in the Angle field to rotate the Ancillary 180 degrees. The default rotation angle is 90 degrees.\nClick Align to align the ancillary to a surface using a cursor pick in the 3D view.\nYou are prompted to Pick a surface to align with :\nClick OK to rotate the ancillary or Cancel to discard any changes and close the Rotate window.\n\n\n\nIdentify ancillary to rotate\nRotate Ancillary\nAngle\n180\nAngle\n180\nAlign\nPick a surface to align with :\nOK\nCancel\nRotate"}
{"Headers": "Rotate Hanger Component", "Content": "Rotates an individual hanger ancillary.\n\nThe hanger name displays at the top of the Rotate One Hanger Component window.\nInput a value in the Angle field to rotate the hanger. For example input 180 in the Angle field to rotate the hanger ancillary 180 degrees. The default rotation angle is 90 degrees.\nClick Apply to rotate the hanger ancillary.\nYou are prompted to Identify hanger component to rotate\nClick to identify the hanger ancillary using a cursor pick in the 3D view. The hanger ancillary is rotated.\nClick Cancel to close the Rotate One Hanger Component window.\n\n\n\nRotate One Hanger Component\nAngle\n180\nAngle\n180\nApply\nIdentify hanger component to rotate\nCancel\nRotate One Hanger Component"}
{"Headers": "Modify Steelwork Template", "Content": "Modifies the steelwork template for the support.\n\nThe Set Steelwork Template window displays all available/unavailable steelwork templates for the currently selected framework support. The active status for each steelwork template is indicated by the colour of the Min Bore and Max Bore columns, green indicates active and amber indicates inactive.\nSelect a steelwork template from the list of available steelwork templates. The selected steelwork template displays in the 3D view.\nClick OK to apply the steelwork template or Cancel to discard any inputs and close the Set Steelwork Template window.\n\n\n\nSet Steelwork Template\nOK\nCancel\nSet Steelwork Template"}
{"Headers": "Primary and Additional Functions", "Content": "The bottom part of the Support Editor window displays the Primary and Additional tabs. The Primary tab allows you to process commands that are commonly used. For example, create connections and copy components. The Additional tab allows you to process commands that are less commonly used. For example, add reference supports and compensation plates.\n\n\n\nSupport Editor\nPrimary\nAdditional\nPrimary\nAdditional"}
{"Headers": "Create", "Content": "The Create part of the Support Editor window allows you to create a support packing piece or view, create modify and delete welding information.\n\nWeld\nAllows you to view, create, modify or delete welding information for the framework support. Refer to Create Framework Support Weld for further information.\nPacker\nClick to add a packing piece to a framework support to make up for height differences between the crossbar and support ancillaries. You must select an ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify Support Ancillary (ANCI) to Add Packing Piece to\nThe new packing piece is created on the selected ancillary and displays on the Support Editor window as a new tab.\n\nWeld\nAllows you to view, create, modify or delete welding information for the framework support. Refer to Create Framework Support Weld for further information.\n\nPacker\nClick to add a packing piece to a framework support to make up for height differences between the crossbar and support ancillaries. You must select an ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify Support Ancillary (ANCI) to Add Packing Piece to\nThe new packing piece is created on the selected ancillary and displays on the Support Editor window as a new tab.\n\nWeld\nAllows you to view, create, modify or delete welding information for the framework support. Refer to Create Framework Support Weld for further information.\nPacker\nClick to add a packing piece to a framework support to make up for height differences between the crossbar and support ancillaries. You must select an ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify Support Ancillary (ANCI) to Add Packing Piece to\nThe new packing piece is created on the selected ancillary and displays on the Support Editor window as a new tab.\n\n\n\nCreate Framework Support Weld\nCreate\nSupport Editor\nWeld\nCreate Framework Support Weld\nPacker\nIdentify Support Ancillary (ANCI) to Add Packing Piece to\nSupport Editor"}
{"Headers": "Create Framework Support Weld", "Content": "Sets the welding information for a framework support.\n\nThe top part of the Framework Weld Selection window displays a list of available framework members, welds and ppoints. You can create, modify, delete and show a weld.\nMembers\nSelect a member from the list to define the support frame member to be used for the weld. By default, the list of available welds is populated with the welds that are associated with the currently selected member.\nWelds\nSelect a weld from the list to define the weld to be modified. By default, the Section Weld Data and Section Weld Position parts of the Framework Selection window are populated with the details of the currently selected weld.\nPpoints\nThe list of Ppoints displays the Ppoints associated with the currently selected weld.\nNew Weld\nAllows you to create a new weld for the currently selected support. Refer to Create New Weld for further information\nDelete Weld\nClick to delete the currently selected weld.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld.\nShow Weld\nSelect the check box to display the currently selected weld in the 3D view.\nMembers\nSelect a member from the list to define the support frame member to be used for the weld. By default, the list of available welds is populated with the welds that are associated with the currently selected member.\nWelds\nSelect a weld from the list to define the weld to be modified. By default, the Section Weld Data and Section Weld Position parts of the Framework Selection window are populated with the details of the currently selected weld.\nPpoints\nThe list of Ppoints displays the Ppoints associated with the currently selected weld.\nNew Weld\nAllows you to create a new weld for the currently selected support. Refer to Create New Weld for further information\nDelete Weld\nClick to delete the currently selected weld.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld.\nShow Weld\nSelect the check box to display the currently selected weld in the 3D view.\nThe Section/Weld Data part of the Framework Weld Selection window allows you to reselect a weld and define the weld specification.\n\nAll welds, created or modified, are stored in a TMPL element at the STRU level of the support in the database. They are displayed together with all relevant welding information in the weld list.\nReselect Std\nAllows you to reselect a weld specification from a list of existing standard weld templates.\nClick to display the Select Standard Weld window. The functionality of the Select Standard Weld window is explained as part of the process to create a weld. Refer to Create New Weld for further information.\nGeneric\nSelect the option button to create or modify the weld for all occurrences of the joint throughout the templates.\nCurrent Joint\nSelect the option button to create or modify the weld for the currently selected joint only.\nOwner\nBy default, the field is populated with the name of the section that owns the weld.\nWeld name\nBy default, the field is populated with the name of the weld as stored in the TMPL in the database.\nSymbol Name\nBy default, the field is populated with the name of the symbol that is output on the support drawing.\nDescription\nBy default, the field is populated with the description of the weld.\nWeld Size\nYou can input a weld size value in the field.\nPpoints\nYou can input a Ppoint value in the field to associate the weld with a Ppoint.\nReselect Std\nAllows you to reselect a weld specification from a list of existing standard weld templates.\nClick to display the Select Standard Weld window. The functionality of the Select Standard Weld window is explained as part of the process to create a weld. Refer to Create New Weld for further information.\nGeneric\nSelect the option button to create or modify the weld for all occurrences of the joint throughout the templates.\nCurrent Joint\nSelect the option button to create or modify the weld for the currently selected joint only.\nOwner\nBy default, the field is populated with the name of the section that owns the weld.\nWeld name\nBy default, the field is populated with the name of the weld as stored in the TMPL in the database.\nSymbol Name\nBy default, the field is populated with the name of the symbol that is output on the support drawing.\nDescription\nBy default, the field is populated with the description of the weld.\nWeld Size\nYou can input a weld size value in the field.\nPpoints\nYou can input a Ppoint value in the field to associate the weld with a Ppoint.\nThe Set Weld Position part of the Framework Weld Selection window allows you to position the weld.\n\nSingle Position\nClick the option button to position a weld with a single position.\nStart End\nClick the option button to position a weld with a start point and an end point.\nStart\nInput a value in the field to define the weld start point.\nAlternatively click Pick to define the weld start point using a cursor pick in the 3D view. Refer to Weld Start/End Position for further information.\nEnd\nInput a value in the field to define the weld end point.\nAlternatively click Pick to define the weld end point using a cursor pick in the 3D view. Refer to Weld Start/End Position for further information.\nSingle Position\nClick the option button to position a weld with a single position.\nStart End\nClick the option button to position a weld with a start point and an end point.\nStart\nInput a value in the field to define the weld start point.\nAlternatively click Pick to define the weld start point using a cursor pick in the 3D view. Refer to Weld Start/End Position for further information.\nEnd\nInput a value in the field to define the weld end point.\nAlternatively click Pick to define the weld end point using a cursor pick in the 3D view. Refer to Weld Start/End Position for further information.\nClick Save to apply the weld to the framework support or Cancel to discard any changes and close the Framework Weld Selection window.\nMembers\nSelect a member from the list to define the support frame member to be used for the weld. By default, the list of available welds is populated with the welds that are associated with the currently selected member.\nWelds\nSelect a weld from the list to define the weld to be modified. By default, the Section Weld Data and Section Weld Position parts of the Framework Selection window are populated with the details of the currently selected weld.\nPpoints\nThe list of Ppoints displays the Ppoints associated with the currently selected weld.\nNew Weld\nAllows you to create a new weld for the currently selected support. Refer to Create New Weld for further information\nDelete Weld\nClick to delete the currently selected weld.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld.\nShow Weld\nSelect the check box to display the currently selected weld in the 3D view.\nReselect Std\nAllows you to reselect a weld specification from a list of existing standard weld templates.\nClick to display the Select Standard Weld window. The functionality of the Select Standard Weld window is explained as part of the process to create a weld. Refer to Create New Weld for further information.\nGeneric\nSelect the option button to create or modify the weld for all occurrences of the joint throughout the templates.\nCurrent Joint\nSelect the option button to create or modify the weld for the currently selected joint only.\nOwner\nBy default, the field is populated with the name of the section that owns the weld.\nWeld name\nBy default, the field is populated with the name of the weld as stored in the TMPL in the database.\nSymbol Name\nBy default, the field is populated with the name of the symbol that is output on the support drawing.\nDescription\nBy default, the field is populated with the description of the weld.\nWeld Size\nYou can input a weld size value in the field.\nPpoints\nYou can input a Ppoint value in the field to associate the weld with a Ppoint.\nSingle Position\nClick the option button to position a weld with a single position.\nStart End\nClick the option button to position a weld with a start point and an end point.\nStart\nInput a value in the field to define the weld start point.\nAlternatively click Pick to define the weld start point using a cursor pick in the 3D view. Refer to Weld Start/End Position for further information.\nEnd\nInput a value in the field to define the weld end point.\nAlternatively click Pick to define the weld end point using a cursor pick in the 3D view. Refer to Weld Start/End Position for further information.\n\n\n\nCreate New Weld\nCreate New Weld\nWeld Start/End Position\nWeld Start/End Position\nFramework Weld Selection\nMembers\nWelds\nSection Weld Data\nSection Weld Position\nFramework Selection\nPpoints\nNew Weld\nCreate New Weld\nDelete Weld\nYes\nShow Weld\nSection/Weld Data\nFramework Weld Selection\nReselect Std\nSelect Standard Weld\nSelect Standard Weld\nCreate New Weld\nGeneric\nCurrent Joint\nOwner\nWeld name\nSymbol Name\nDescription\nWeld Size\nPpoints\nSet Weld Position\nFramework Weld Selection\nSingle Position\nStart End\nStart\nPick\nWeld Start/End Position\nEnd\nPick\nWeld Start/End Position\nSave\nCancel\nFramework Weld Selection"}
{"Headers": "Create New Weld", "Content": "Sets a weld specification from a list of existing standard weld templates.\n\nSelect a weld type from the Existing Areas drop-down list. By default, the Existing Welds list is populated with the welds that are available.\nSelect a weld from the Existing Welds list. By default, the Supports application displays the name, symbol name and description for the currently selected weld.\nClick Apply to populate the Framework Weld Selection window with the weld details or Cancel to discard any changes and close the Select Standard Weld window.\n\n\n\nExisting Areas\nExisting Welds\nExisting Welds\nApply\nFramework Weld Selection\nCancel"}
{"Headers": "Weld Start/End Position", "Content": "Sets the weld start and end points.\n\nThe top of the Set Weld Position window displays Start or End, indicating the currently selected weld position.\nSingle Pline\nClick the option button to position a weld using a single pline.\nPline Intersections\nClick the option button to position a weld using pline intersections.\nPlines\nSelect a PKEY from the Plines drop down list. You can then click Identify Pline to select a Pline using a cursor pick in the 3D view.\nYou are prompted to Identify PLIN\nEach Pline is identified by a two, three or four letter code (known as its PKEY) which identifies its relative position in the 2D profile. Refer to P-line Identification for further information.\nIntersecting Section\nSelect an intersection from the Intersecting Section drop down list. You can then click Identify GENSEC to select a GENSEC using a cursor pick in the 3D view.\nYou are prompted to Identify element\nWeld Definition\nBy default, the field is populated with the name of the weld position.\nSingle Pline\nClick the option button to position a weld using a single pline.\nPline Intersections\nClick the option button to position a weld using pline intersections.\nPlines\nSelect a PKEY from the Plines drop down list. You can then click Identify Pline to select a Pline using a cursor pick in the 3D view.\nYou are prompted to Identify PLIN\nEach Pline is identified by a two, three or four letter code (known as its PKEY) which identifies its relative position in the 2D profile. Refer to P-line Identification for further information.\nIntersecting Section\nSelect an intersection from the Intersecting Section drop down list. You can then click Identify GENSEC to select a GENSEC using a cursor pick in the 3D view.\nYou are prompted to Identify element\nWeld Definition\nBy default, the field is populated with the name of the weld position.\nClick OK to apply the weld position or Cancel to discard any changes and close the Set Weld Position window.\nSingle Pline\nClick the option button to position a weld using a single pline.\nPline Intersections\nClick the option button to position a weld using pline intersections.\nPlines\nSelect a PKEY from the Plines drop down list. You can then click Identify Pline to select a Pline using a cursor pick in the 3D view.\nYou are prompted to Identify PLIN\nEach Pline is identified by a two, three or four letter code (known as its PKEY) which identifies its relative position in the 2D profile. Refer to P-line Identification for further information.\nIntersecting Section\nSelect an intersection from the Intersecting Section drop down list. You can then click Identify GENSEC to select a GENSEC using a cursor pick in the 3D view.\nYou are prompted to Identify element\nWeld Definition\nBy default, the field is populated with the name of the weld position.\n\n\n\nP-line Identification\nSet Weld Position\nSingle Pline\nPline Intersections\nPlines\nPlines\nIdentify Pline\nIdentify PLIN\nP-line Identification\nIntersecting Section\nIntersecting Section\nIdentify GENSEC\nIdentify element\nWeld Definition\nOK\nCancel\nSet Weld Position"}
{"Headers": "Modify", "Content": "The Modify part of the Support Editor window allows you to modify the support datum component, joint specification, trimming of connected sections and hanger connections.\n\nDatum Component\nClick to define a new datum ancillary for the support.\nIf the support contains two ancillaries, the new datum ancillary is allocated, by default.\nIf the support contains more than two ancillaries, you must identify the new datum ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify the new datum ancillary\nA confirm window displays asking you to OK the selection. Click Yes to apply the selected ancillary as the datum ancillary.\nModify Connection\nAllows you to apply a catalogue specification and modify a framework support section connection. Refer to Joint Specification for further information\nForce Connection to P-Line\nAllows you to force the trimming of a connected section end to an alternative Pline. Refer to Trim Connected Section Ends for further information.\nReconnect Hanger\nAllows you to reconnect a hanger to the same structural elements (if elements have been moved) or to a different set of compatible structural elements.\nThe reconnection process is dependent on the current hanger type. Refer to Hanger for further information.\nCrossbar Associations\nClick to modify the crossbar association of framework support ancillaries.\nWhen additional ancillaries are added to a framework support, they are associated to the same crossbar as the datum ancillary, by default. It may be necessary to associate added ancillaries to an alternative crossbar.\nNote:\nThe crossbar association of the datum ancillary cannot be modified.\nYou are prompted to Identify ancillary to associate with a crossbar\nYou can continue to identify additional ancillaries using a cursor pick in the 3D view.\nPress ESC to associate the crossbar.\nYou are then prompted to Identify crossbar to support the ancillary\nClick to identify the crossbar. The crossbar association of the selected ancillaries is modified.\n\nDatum Component\nClick to define a new datum ancillary for the support.\nIf the support contains two ancillaries, the new datum ancillary is allocated, by default.\nIf the support contains more than two ancillaries, you must identify the new datum ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify the new datum ancillary\nA confirm window displays asking you to OK the selection. Click Yes to apply the selected ancillary as the datum ancillary.\n\n\nModify Connection\nAllows you to apply a catalogue specification and modify a framework support section connection. Refer to Joint Specification for further information\n\nForce Connection to P-Line\nAllows you to force the trimming of a connected section end to an alternative Pline. Refer to Trim Connected Section Ends for further information.\n\nReconnect Hanger\nAllows you to reconnect a hanger to the same structural elements (if elements have been moved) or to a different set of compatible structural elements.\nThe reconnection process is dependent on the current hanger type. Refer to Hanger for further information.\n\nCrossbar Associations\nClick to modify the crossbar association of framework support ancillaries.\nWhen additional ancillaries are added to a framework support, they are associated to the same crossbar as the datum ancillary, by default. It may be necessary to associate added ancillaries to an alternative crossbar.\nYou are prompted to Identify ancillary to associate with a crossbar\nYou can continue to identify additional ancillaries using a cursor pick in the 3D view.\nPress ESC to associate the crossbar.\nYou are then prompted to Identify crossbar to support the ancillary\nClick to identify the crossbar. The crossbar association of the selected ancillaries is modified.\n\nDatum Component\nClick to define a new datum ancillary for the support.\nIf the support contains two ancillaries, the new datum ancillary is allocated, by default.\nIf the support contains more than two ancillaries, you must identify the new datum ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify the new datum ancillary\nA confirm window displays asking you to OK the selection. Click Yes to apply the selected ancillary as the datum ancillary.\nModify Connection\nAllows you to apply a catalogue specification and modify a framework support section connection. Refer to Joint Specification for further information\nForce Connection to P-Line\nAllows you to force the trimming of a connected section end to an alternative Pline. Refer to Trim Connected Section Ends for further information.\nReconnect Hanger\nAllows you to reconnect a hanger to the same structural elements (if elements have been moved) or to a different set of compatible structural elements.\nThe reconnection process is dependent on the current hanger type. Refer to Hanger for further information.\nCrossbar Associations\nClick to modify the crossbar association of framework support ancillaries.\nWhen additional ancillaries are added to a framework support, they are associated to the same crossbar as the datum ancillary, by default. It may be necessary to associate added ancillaries to an alternative crossbar.\nNote:\nThe crossbar association of the datum ancillary cannot be modified.\nYou are prompted to Identify ancillary to associate with a crossbar\nYou can continue to identify additional ancillaries using a cursor pick in the 3D view.\nPress ESC to associate the crossbar.\nYou are then prompted to Identify crossbar to support the ancillary\nClick to identify the crossbar. The crossbar association of the selected ancillaries is modified.\nNote:\nThe crossbar association of the datum ancillary cannot be modified.\n\n\n\nJoint Specification\nTrim Connected Section Ends\nHanger\nModify\nSupport Editor\nDatum Component\nIdentify the new datum ancillary\nYes\nModify Connection\nJoint Specification\nForce Connection to P-Line\nTrim Connected Section Ends\nReconnect Hanger\nHanger\nCrossbar Associations\nNote\n:\nIdentify ancillary to associate with a crossbar\nESC\nIdentify crossbar to support the ancillary"}
{"Headers": "Joint Specification", "Content": "Applies a catalogue specification and modifies a framework support section connection.\n\nThe Joint List part of the Joint Specification window allows you to specify the joint to define.\n\nPick\nClick to define the joint to be modified using a cursor pick in the 3D view.\nYou are prompted to Identify Section End Connected or Connection Joint\nApply to all Joints\nSelect from the drop-down list to modify the specification, alignment and dimensions of all joints on the currently selected framework support.\nAlternatively, you can select an individual joint to modify from the drop-down list.\nPick\nClick to define the joint to be modified using a cursor pick in the 3D view.\nYou are prompted to Identify Section End Connected or Connection Joint\nApply to all Joints\nSelect from the drop-down list to modify the specification, alignment and dimensions of all joints on the currently selected framework support.\nAlternatively, you can select an individual joint to modify from the drop-down list.\nThe MDS Joint Specification part of the Joint Specification window allows you to define the specification for the joint.\n\nSpecification\nSelect a specification from the drop-down list to define the joint specification for the support framework. The selection determines the options available from the Sub-Type drop-down list and the list of available joint specifications.\nSelect None from the drop-down list to clear the joint specification.\nSub-Type\nSelect a sub-type from the drop-down list to define the joint sub-type for the support framework. The selection determines the options available from the list of available joint specifications.\nJoint Specifications\nSelect a joint specification from the list of available joint specifications.\nSpecification\nSelect a specification from the drop-down list to define the joint specification for the support framework. The selection determines the options available from the Sub-Type drop-down list and the list of available joint specifications.\nSelect None from the drop-down list to clear the joint specification.\nSub-Type\nSelect a sub-type from the drop-down list to define the joint sub-type for the support framework. The selection determines the options available from the list of available joint specifications.\nJoint Specifications\nSelect a joint specification from the list of available joint specifications.\nThe Joint Alignment part of the Joint Specification window allows you to define the alignment properties for the joint.\n\nJustification\nSelect from the drop-down list to identify the Pline to associate the joint with.\nFlip\nClick to flip the joint by 180 degrees.\nCutback\nInput the length by which the attached section is to be trimmed to allow for the joint geometry.\nLoop\nClick L, C or R to loop through the left, centre or right Plines for the available options in the justification drop-down list.\nY Direction\nInput a value in the field to define the Y direction of the joint.\nJustification\nSelect from the drop-down list to identify the Pline to associate the joint with.\nFlip\nClick to flip the joint by 180 degrees.\nCutback\nInput the length by which the attached section is to be trimmed to allow for the joint geometry.\nLoop\nClick L, C or R to loop through the left, centre or right Plines for the available options in the justification drop-down list.\nY Direction\nInput a value in the field to define the Y direction of the joint.\nThe Joint Dimensions part of the Joint Specification window allows you to define the size and profile of the joint.\n\nLength\nInput a value in the field to define the length of the joint.\nWidth\nInput a value in the field to define the width of the joint.\nThickness\nInput a value in the field to define the thickness of the joint.\nO-Beam c/c\nInput a value in the field to modify the width from the Owning Beam (OPAR) to the centre of the bolt holes.\nA-Beam c/c\nInput a value in the field to modify the height from the Attached Beam (APAR) to the centre of the bolt holes.\nBolt Dia.\nInput a value in the field to define the bolt diameter for the joint.\nPlate Angle\nInput a value in the field to define the plate angle for the joint.\nDefault\nClick to set the joint to the default dimensions.\nLength\nInput a value in the field to define the length of the joint.\nWidth\nInput a value in the field to define the width of the joint.\nThickness\nInput a value in the field to define the thickness of the joint.\nO-Beam c/c\nInput a value in the field to modify the width from the Owning Beam (OPAR) to the centre of the bolt holes.\nA-Beam c/c\nInput a value in the field to modify the height from the Attached Beam (APAR) to the centre of the bolt holes.\nBolt Dia.\nInput a value in the field to define the bolt diameter for the joint.\nPlate Angle\nInput a value in the field to define the plate angle for the joint.\nDefault\nClick to set the joint to the default dimensions.\nClick Apply to apply the catalogue specification to the fixing of the connection.\nClick View to display the View Multi Discipline Standard window. The functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\nClick Cancel to discard any changes and close the Joint Specification window.\nPick\nClick to define the joint to be modified using a cursor pick in the 3D view.\nYou are prompted to Identify Section End Connected or Connection Joint\nApply to all Joints\nSelect from the drop-down list to modify the specification, alignment and dimensions of all joints on the currently selected framework support.\nAlternatively, you can select an individual joint to modify from the drop-down list.\nSpecification\nSelect a specification from the drop-down list to define the joint specification for the support framework. The selection determines the options available from the Sub-Type drop-down list and the list of available joint specifications.\nSelect None from the drop-down list to clear the joint specification.\nSub-Type\nSelect a sub-type from the drop-down list to define the joint sub-type for the support framework. The selection determines the options available from the list of available joint specifications.\nJoint Specifications\nSelect a joint specification from the list of available joint specifications.\nJustification\nSelect from the drop-down list to identify the Pline to associate the joint with.\nFlip\nClick to flip the joint by 180 degrees.\nCutback\nInput the length by which the attached section is to be trimmed to allow for the joint geometry.\nLoop\nClick L, C or R to loop through the left, centre or right Plines for the available options in the justification drop-down list.\nY Direction\nInput a value in the field to define the Y direction of the joint.\nLength\nInput a value in the field to define the length of the joint.\nWidth\nInput a value in the field to define the width of the joint.\nThickness\nInput a value in the field to define the thickness of the joint.\nO-Beam c/c\nInput a value in the field to modify the width from the Owning Beam (OPAR) to the centre of the bolt holes.\nA-Beam c/c\nInput a value in the field to modify the height from the Attached Beam (APAR) to the centre of the bolt holes.\nBolt Dia.\nInput a value in the field to define the bolt diameter for the joint.\nPlate Angle\nInput a value in the field to define the plate angle for the joint.\nDefault\nClick to set the joint to the default dimensions.\n\n\n\nView Multi Discipline Support Standard\nJoint List\nPick\nIdentify Section End Connected or Connection Joint\nApply to all Joints\nMDS Joint Specification\nSpecification\nNone\nSub-Type\nJoint Specifications\nJoint Alignment\nJustification\nFlip\nCutback\nLoop\nY Direction\nJoint Dimensions\nLength\nWidth\nThickness\nO-Beam c/c\nA-Beam c/c\nBolt Dia.\nPlate Angle\nDefault\nApply\nView\nView Multi Discipline Standard\nView Multi Discipline Standard\nView Multi Discipline Support Standard\nCancel\nJoint Specification"}
{"Headers": "Trim Connected Section Ends", "Content": "Functionality is available to force the trimming of a connected section end to an alternative Pline.\nYou are prompted to Identify Pline to force connect to\nClick to identify the Pline which corresponds to the required section end point.\nYou are then prompted to Identify section end connected or connection point\nClick to identify the attached section at the end nearest to the connection point. The connection of the attached section is moved to the selected Pline.\n\n\n\nPline to force connect to\nIdentify section end connected or connection point"}
{"Headers": "Orientate", "Content": "The Orientate part of the Support Editor window allows you to rotate or mirror the support position. Functionality is also available to flip a selected ancillary.\n\nAll Components\nAllows you to rotate all support or hanger ancillaries. Refer to Rotate All Components or Rotate All Hanger Components for further information.\nFlip\nClick to flip a selected ancillary by 180 degrees. You must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify Ancillary to Flip\nMirror\nClick to mirror the support, perpendicular to the datum ancillary, repositioning the members through the structure origin.\n\nAll Components\nAllows you to rotate all support or hanger ancillaries. Refer to Rotate All Components or Rotate All Hanger Components for further information.\n\nFlip\nClick to flip a selected ancillary by 180 degrees. You must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify Ancillary to Flip\n\nMirror\nClick to mirror the support, perpendicular to the datum ancillary, repositioning the members through the structure origin.\n\nAll Components\nAllows you to rotate all support or hanger ancillaries. Refer to Rotate All Components or Rotate All Hanger Components for further information.\nFlip\nClick to flip a selected ancillary by 180 degrees. You must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify Ancillary to Flip\nMirror\nClick to mirror the support, perpendicular to the datum ancillary, repositioning the members through the structure origin.\n\n\n\nRotate All Components\nRotate All Hanger Components\nOrientate\nSupport Editor\nAll Components\nRotate All Components\nRotate All Hanger Components\nFlip\nIdentify Ancillary to Flip\nMirror"}
{"Headers": "Rotate All Components", "Content": "Rotates all ancillaries for the support.\n\nThe support name displays at the top of the Rotate All Components window.\nInput a value in the Angle field to rotate all ancillaries for the support. For example input 180 in the Angle field to rotate the ancillaries 180 degrees. The default rotation angle is 90 degrees.\nClick Apply to rotate the ancillaries or Cancel to discard any changes and close the Rotate All Components window.\n\n\n\nRotate All\nComponents\nAngle\n180\nAngle\n180\nApply\nCancel\nRotate All\nComponents"}
{"Headers": "Rotate All Hanger Components", "Content": "Rotates all ancillaries for the hanger.\n\nThe hanger name displays at the top of the Rotate All Hanger Components window.\nInput a value in the Angle field to rotate ancillaries for the hanger. For example input 180 in the Angle field to rotate the hanger ancillary 180 degrees. The default rotation angle is 90 degrees.\nClick Apply to rotate the hanger ancillaries.\nYou are prompted to Identify hanger to rotate all components\nClick to identify the hanger using a cursor pick in the 3D view. The hanger ancillaries are rotated.\nClick Cancel to close the Rotate All Hanger Components window.\n\n\n\nRotate All Hanger Components\nAngle\n180\nAngle\n180\nApply\nIdentify hanger to rotate all components\nCancel\nRotate All Hanger Components"}
{"Headers": "Position", "Content": "The Position part of the Support Editor window provides tools for fine-tuning the positioning of supports.\n\nNudge Support Component\nAllows you to nudge a support component. Refer to Nudge Support Component for further information.\nFlip Field Weld\nClick to flip the position of the field weld to the opposite end of a framework support steelwork member.\nThe field weld position displays in the 3D view.\n\nNudge Support Component\nAllows you to nudge a support component. Refer to Nudge Support Component for further information.\n\nFlip Field Weld\nClick to flip the position of the field weld to the opposite end of a framework support steelwork member.\nThe field weld position displays in the 3D view.\n\nNudge Support Component\nAllows you to nudge a support component. Refer to Nudge Support Component for further information.\nFlip Field Weld\nClick to flip the position of the field weld to the opposite end of a framework support steelwork member.\nThe field weld position displays in the 3D view.\n\n\n\nNudge Support Component\nPosition\nSupport Editor\nNudge Support Component\nNudge Support Component\nFlip Field Weld"}
{"Headers": "Nudge Support Component", "Content": "Nudges a support component forwards or backwards by a specified distance.\n\nPick\nClick to pick an ancillary to nudge.You must select an ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary to nudge\nIf the support contains more than one ancillary, you can continue to select additional ancillaries to nudge.\nPress ESC to finish selecting ancillaries.\nCE\nClick to select the existing ancillary as the Current Element\nDistance\nInsert a value in the field to define the distance to nudge the ancillary.\nNudge Forward\nClick to nudge the ancillary forwards, the nudge distance is defined by the value entered in the Distance field.\nNudge Backward\nClick to nudge the ancillary backwards, the nudge distance is defined by the value entered in the Distance field.\nThrough\nClick to align the ancillary through a picked element. You must identify an element using a cursor pick in the 3D view.\nYou are prompted to Identify element to move selected components through\nReset\nClick to reset the ancillary to the default position. A confirm window displays asking you to OK the action. Click Yes to reset the position of the ancillary.\n\nPick\nClick to pick an ancillary to nudge.You must select an ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary to nudge\nIf the support contains more than one ancillary, you can continue to select additional ancillaries to nudge.\nPress ESC to finish selecting ancillaries.\n\nCE\nClick to select the existing ancillary as the Current Element\n\nDistance\nInsert a value in the field to define the distance to nudge the ancillary.\n\nNudge Forward\nClick to nudge the ancillary forwards, the nudge distance is defined by the value entered in the Distance field.\n\nNudge Backward\nClick to nudge the ancillary backwards, the nudge distance is defined by the value entered in the Distance field.\n\nThrough\nClick to align the ancillary through a picked element. You must identify an element using a cursor pick in the 3D view.\nYou are prompted to Identify element to move selected components through\n\nReset\nClick to reset the ancillary to the default position. A confirm window displays asking you to OK the action. Click Yes to reset the position of the ancillary.\nClick Cancel to close the Nudge Support Component window.\nPick\nClick to pick an ancillary to nudge.You must select an ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary to nudge\nIf the support contains more than one ancillary, you can continue to select additional ancillaries to nudge.\nPress ESC to finish selecting ancillaries.\nCE\nClick to select the existing ancillary as the Current Element\nDistance\nInsert a value in the field to define the distance to nudge the ancillary.\nNudge Forward\nClick to nudge the ancillary forwards, the nudge distance is defined by the value entered in the Distance field.\nNudge Backward\nClick to nudge the ancillary backwards, the nudge distance is defined by the value entered in the Distance field.\nThrough\nClick to align the ancillary through a picked element. You must identify an element using a cursor pick in the 3D view.\nYou are prompted to Identify element to move selected components through\nReset\nClick to reset the ancillary to the default position. A confirm window displays asking you to OK the action. Click Yes to reset the position of the ancillary.\n\n\n\nPick\nIdentify ancillary to nudge\nESC\nCE\nDistance\nNudge Forward\nDistance\nNudge Backward\nDistance\nThrough\nIdentify element to move selected components through\nReset\nYes\nCancel\nNudge Support Component"}
{"Headers": "View", "Content": "The View part of the Support Editor window allows you to view ancillaries that are associated with a framework support crossbar and flip the ADP view direction, this can improve drawing clarity.\n\nAssociations\nClick to display ancillaries that are associated with a crossbar in the 3D view. You must identify a crossbar using a cursor pick in the 3D view.\nYou are prompted to Identify cross bar belonging to support\nAll Ancillaries associated with the selected crossbar are highlighted in the 3D view.\nYou can continue to identify crossbars using a cursor pick in the 3D view.\nPress ESC to finish selecting crossbars.\nView Direction\nClick to flip the ADP view direction by 180 degrees.\nA confirm window displays asking you to OK the action. Click Yes to flip the view directions.\n\nAssociations\nClick to display ancillaries that are associated with a crossbar in the 3D view. You must identify a crossbar using a cursor pick in the 3D view.\nYou are prompted to Identify cross bar belonging to support\nAll Ancillaries associated with the selected crossbar are highlighted in the 3D view.\nYou can continue to identify crossbars using a cursor pick in the 3D view.\nPress ESC to finish selecting crossbars.\n\nView Direction\nClick to flip the ADP view direction by 180 degrees.\nA confirm window displays asking you to OK the action. Click Yes to flip the view directions.\n\nAssociations\nClick to display ancillaries that are associated with a crossbar in the 3D view. You must identify a crossbar using a cursor pick in the 3D view.\nYou are prompted to Identify cross bar belonging to support\nAll Ancillaries associated with the selected crossbar are highlighted in the 3D view.\nYou can continue to identify crossbars using a cursor pick in the 3D view.\nPress ESC to finish selecting crossbars.\nView Direction\nClick to flip the ADP view direction by 180 degrees.\nA confirm window displays asking you to OK the action. Click Yes to flip the view directions.\n\n\n\nView\nSupport Editor\nAssociations\nIdentify cross bar belonging to support\nESC\nView Direction\nYes"}
{"Headers": "Delete", "Content": "The Delete part of the Support Editor window allows you to delete support components, packing pieces or connections.\n\nComponent\nClick to delete an ancillary from the support. The datum ancillary cannot be deleted.\nIf the support contains two ancillaries, the ancillary to be deleted is selected, by default. A confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nIf the support contains more than two ancillaries, you must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify atta/plat to delete\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nPacker\nClick to delete a packing piece from the support. You must identify the packing piece using a cursor pick in the 3D view.\nYou are prompted to Identify Support Packing Piece to Delete\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nConnections\nClick to delete all connections and joints for the support. Any dimensions that became inactive due to the connection are enabled.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\n\nComponent\nClick to delete an ancillary from the support. The datum ancillary cannot be deleted.\nIf the support contains two ancillaries, the ancillary to be deleted is selected, by default. A confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nIf the support contains more than two ancillaries, you must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify atta/plat to delete\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\n\nPacker\nClick to delete a packing piece from the support. You must identify the packing piece using a cursor pick in the 3D view.\nYou are prompted to Identify Support Packing Piece to Delete\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\n\nConnections\nClick to delete all connections and joints for the support. Any dimensions that became inactive due to the connection are enabled.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\n\nComponent\nClick to delete an ancillary from the support. The datum ancillary cannot be deleted.\nIf the support contains two ancillaries, the ancillary to be deleted is selected, by default. A confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nIf the support contains more than two ancillaries, you must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify atta/plat to delete\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nPacker\nClick to delete a packing piece from the support. You must identify the packing piece using a cursor pick in the 3D view.\nYou are prompted to Identify Support Packing Piece to Delete\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nConnections\nClick to delete all connections and joints for the support. Any dimensions that became inactive due to the connection are enabled.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\n\n\n\nDelete\nSupport Editor\nComponent\nYes\nIdentify atta/plat to delete\nYes\nPacker\nIdentify Support Packing Piece to Delete\nYes\nConnections\nYes"}
{"Headers": "Copy", "Content": "The Copy part of the Support Editor window allows you to copy an ancillary or copy the framework dimensions from an existing support.\n\nComponent\nClick to copy a support ancillary.\nIf the ancillary is not selected and the support contains more than one ancillary, you must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify source ancillary to copy or <ESC> to finish :\nYou must then identify the pipe to associate the ancillary with, using a cursor pick in the 3D view.\nYou are then prompted to Identify tube of pipe to add ancillary or <ESC> to finish :\nThe new ancillary is created and displays on the Support Editor window as a new tab.\nNote:\nIf you create the new ancillary on the same branch as the original ancillary, the new copy is placed in the same position as the original and rotated by 90 degrees.\nPress ESC to finish copying ancillaries.\nLike\nClick to copy the dimensions of another support of the same standard. The number of associated pipes, cable trays, and HVAC elements does not have to be the same on each support. You must identify the support to copy the dimensions from using a cursor pick in the 3D view.\nYou are prompted to Identify support to copy framework attributes from\n\nComponent\nClick to copy a support ancillary.\nIf the ancillary is not selected and the support contains more than one ancillary, you must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify source ancillary to copy or <ESC> to finish :\nYou must then identify the pipe to associate the ancillary with, using a cursor pick in the 3D view.\nYou are then prompted to Identify tube of pipe to add ancillary or <ESC> to finish :\nThe new ancillary is created and displays on the Support Editor window as a new tab.\nPress ESC to finish copying ancillaries.\n\nLike\nClick to copy the dimensions of another support of the same standard. The number of associated pipes, cable trays, and HVAC elements does not have to be the same on each support. You must identify the support to copy the dimensions from using a cursor pick in the 3D view.\nYou are prompted to Identify support to copy framework attributes from\n\nComponent\nClick to copy a support ancillary.\nIf the ancillary is not selected and the support contains more than one ancillary, you must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify source ancillary to copy or <ESC> to finish :\nYou must then identify the pipe to associate the ancillary with, using a cursor pick in the 3D view.\nYou are then prompted to Identify tube of pipe to add ancillary or <ESC> to finish :\nThe new ancillary is created and displays on the Support Editor window as a new tab.\nNote:\nIf you create the new ancillary on the same branch as the original ancillary, the new copy is placed in the same position as the original and rotated by 90 degrees.\nPress ESC to finish copying ancillaries.\nLike\nClick to copy the dimensions of another support of the same standard. The number of associated pipes, cable trays, and HVAC elements does not have to be the same on each support. You must identify the support to copy the dimensions from using a cursor pick in the 3D view.\nYou are prompted to Identify support to copy framework attributes from\nNote:\nIf you create the new ancillary on the same branch as the original ancillary, the new copy is placed in the same position as the original and rotated by 90 degrees.\n\n\n\nCopy\nSupport Editor\nComponent\nIdentify source ancillary to copy or <ESC> to finish :\nIdentify tube of pipe to add ancillary or <ESC> to finish :\nSupport Editor\nNote\n:\nESC\nLike\nIdentify support to copy framework attributes from"}
{"Headers": "Change To", "Content": "The Change To part of the Support Editor window allows you to modify the framework support template.\n\nYou can select a framework template from the gallery to modify the framework support. The selected framework template displays in the 2D view. Refer to 2D View for further information.\nSelect the template from the gallery to modify the framework support to an L bracket support type.\nSelect the template from the gallery to modify the framework support to a standing goal post support type.\nSelect the template from the gallery to modify the framework support to a hanging goal post support type.\nSelect the template from the gallery to modify the framework support to a standing half goal post support type.\nSelect the template from the gallery to modify the framework support to a hanging half goal post support type.\nSelect the template from the gallery to modify the framework support to a braced bracket support type.\nSelect the template from the gallery to modify the framework support to a horizontal bar support type.\n\nSelect the template from the gallery to modify the framework support to an L bracket support type.\n\nSelect the template from the gallery to modify the framework support to a standing goal post support type.\n\nSelect the template from the gallery to modify the framework support to a hanging goal post support type.\n\nSelect the template from the gallery to modify the framework support to a standing half goal post support type.\n\nSelect the template from the gallery to modify the framework support to a hanging half goal post support type.\n\nSelect the template from the gallery to modify the framework support to a braced bracket support type.\n\nSelect the template from the gallery to modify the framework support to a horizontal bar support type.\n\nSelect the template from the gallery to modify the framework support to an L bracket support type.\nSelect the template from the gallery to modify the framework support to a standing goal post support type.\nSelect the template from the gallery to modify the framework support to a hanging goal post support type.\nSelect the template from the gallery to modify the framework support to a standing half goal post support type.\nSelect the template from the gallery to modify the framework support to a hanging half goal post support type.\nSelect the template from the gallery to modify the framework support to a braced bracket support type.\nSelect the template from the gallery to modify the framework support to a horizontal bar support type.\n\n\n\n2D View\nChange To\nSupport Editor\n2D View"}
{"Headers": "Special Supports", "Content": "The Special part of the Support Editor window displays when a multi discipline special support, HVAC special support, racking special support or lighting support is created or modified. If a special support is created from existing supports, the Support Editor window allows you to select the support to be used. Refer to Create Special Support from Existing Supports for further information.\n\nYou can define the framework for the special support.\nCopy Section\nClick to copy a support member from the currently selected special support using a cursor pick in the 3D view.\nYou are prompted to Identify section to copy\nA message displays informing you that the identified section has been copied and moved up 300mm and named.\nCopy Project Special\nAllows you to copy a project special template into an existing special support. Refer to Create Project Special Support for further information.\nMove Project Special Joint/Section\nYou can extend certain section ends depending upon the special template configuration using a cursor pick in the 3D view.\nYou are prompted to Identify section/joint to move\nYou must then identify an element to define the position of the section end.\nYou are then prompted to Identify GENSEC\nThe section end extends to the selected element.\nInclude Section into Special\nClick to include a section member that is not part of the current special support using a cursor pick in the 3D view.\nYou are prompted to Identify section to include into support\nCreate Stiffener Box\nClick to add a stiffener box to the currently selected special support using a cursor pick in the 3D view.\nA BOX element is added to the special support with a default size of Xlength 100mm, Ylength 100mm and Zlength 100mm.\nModify Stiffener Material/Size\nAllows you to define the material and size of a stiffener box. Refer to Modify Stiffener Box Material and Size for further information.\nDelete Stiffener\nClick to delete a stiffener box from the currently selected special support.\nIf the special support contains more than one stiffener box you must identify the element using a cursor pick in the 3D view.\nYou are prompted to Identify stiffener plate to delete (BOX)\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\n\nCopy Section\nClick to copy a support member from the currently selected special support using a cursor pick in the 3D view.\nYou are prompted to Identify section to copy\nA message displays informing you that the identified section has been copied and moved up 300mm and named.\n\nCopy Project Special\nAllows you to copy a project special template into an existing special support. Refer to Create Project Special Support for further information.\n\nMove Project Special Joint/Section\nYou can extend certain section ends depending upon the special template configuration using a cursor pick in the 3D view.\nYou are prompted to Identify section/joint to move\nYou must then identify an element to define the position of the section end.\nYou are then prompted to Identify GENSEC\nThe section end extends to the selected element.\n\nInclude Section into Special\nClick to include a section member that is not part of the current special support using a cursor pick in the 3D view.\nYou are prompted to Identify section to include into support\n\nCreate Stiffener Box\nClick to add a stiffener box to the currently selected special support using a cursor pick in the 3D view.\nA BOX element is added to the special support with a default size of Xlength 100mm, Ylength 100mm and Zlength 100mm.\n\nModify Stiffener Material/Size\nAllows you to define the material and size of a stiffener box. Refer to Modify Stiffener Box Material and Size for further information.\n\nDelete Stiffener\nClick to delete a stiffener box from the currently selected special support.\nIf the special support contains more than one stiffener box you must identify the element using a cursor pick in the 3D view.\nYou are prompted to Identify stiffener plate to delete (BOX)\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\n\nCopy Section\nClick to copy a support member from the currently selected special support using a cursor pick in the 3D view.\nYou are prompted to Identify section to copy\nA message displays informing you that the identified section has been copied and moved up 300mm and named.\nCopy Project Special\nAllows you to copy a project special template into an existing special support. Refer to Create Project Special Support for further information.\nMove Project Special Joint/Section\nYou can extend certain section ends depending upon the special template configuration using a cursor pick in the 3D view.\nYou are prompted to Identify section/joint to move\nYou must then identify an element to define the position of the section end.\nYou are then prompted to Identify GENSEC\nThe section end extends to the selected element.\nInclude Section into Special\nClick to include a section member that is not part of the current special support using a cursor pick in the 3D view.\nYou are prompted to Identify section to include into support\nCreate Stiffener Box\nClick to add a stiffener box to the currently selected special support using a cursor pick in the 3D view.\nA BOX element is added to the special support with a default size of Xlength 100mm, Ylength 100mm and Zlength 100mm.\nModify Stiffener Material/Size\nAllows you to define the material and size of a stiffener box. Refer to Modify Stiffener Box Material and Size for further information.\nDelete Stiffener\nClick to delete a stiffener box from the currently selected special support.\nIf the special support contains more than one stiffener box you must identify the element using a cursor pick in the 3D view.\nYou are prompted to Identify stiffener plate to delete (BOX)\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\n\n\n\nCreate Special Support from Existing Supports\nCreate Project Special Support\nModify Stiffener Box Material and Size\nSpecial\nSupport Editor\nSupport\nCreate Special Support from Existing Supports\nCopy Section\nIdentify section to copy\nCopy Project Special\nCreate Project Special Support\nMove Project Special Joint/Section\nIdentify section/joint to move\nIdentify GENSEC\nInclude Section into Special\nIdentify section to include into support\nCreate Stiffener Box\nModify Stiffener Material/Size\nModify Stiffener Box Material and Size\nDelete Stiffener\nIdentify stiffener plate to delete (BOX)\nYes"}
{"Headers": "Create Project Special Support", "Content": "Copies a project special template into an existing special support. This speeds up the process of creating a special support with a complicated configuration and can be used repeatedly on a project.\nProject specials are pre-defined in various application data worlds called APPLDW/SUPPORT/FRAMES/SPECIALS/<suffix>. The piping project specials are contained in the PIPE zone of the application data world. The HVAC project specials are contained in the HVAC zone of the application data world. The cable tray project specials are contained in the Tray zone of the application data world.\n\nThe Select Project Special Template window allows you to select a project special template and copy it into an existing special support.\nSelect a Project Special Template from the list of available templates, the template displays in the 3D view.\nThe Filter field allows you to restrict the elements shown in the list to names containing given characters. By default, the list displays all elements of the given type, as indicated by the * in the Filter fields. The wildcards available are:\nSelect the Mirror check box to reposition the template with respect to a specified plane.\nClick Cancel to close the Select Project Special Template window.\n* Any number of any characters\n? Single character\n* Any number of any characters\n* Any number of any characters\n? Single character\n? Single character\n\n\n\nProject Special Template\nFilter\nMirror\nCancel"}
{"Headers": "Modify Stiffener Box Material and Size", "Content": "Sets the material and size of a stiffener box.\nIf the special support contains more than one stiffener box you must identify the element using a cursor pick in the 3D view.\nYou are prompted to Identify stiffener plate (BOX)\n\nThe special support name displays at the top of the Set Stiffener/Material Size window.\nSelect a stiffener box to be modified from the list of available stiffeners.\nThe list of available stiffeners displays all of the stiffener boxes that can be modified for the currently selected special support. Select a material type from the list of available materials.\nXlen\nInput a dimensional value in the field to define the Xlength size of the stiffener box. The default size is 100mm.\nYlen\nInput a dimensional value in the field to define the Ylength size of the stiffener box. The default size is 100mm.\nZlen\nInput a dimensional value in the field to define the Zlength size of the stiffener box. The default size is 100mm.\nSelect All Stiffeners\nSelect the check box to define the size and material for all stiffener boxes in the list of available stiffeners.\nXlen\nInput a dimensional value in the field to define the Xlength size of the stiffener box. The default size is 100mm.\nYlen\nInput a dimensional value in the field to define the Ylength size of the stiffener box. The default size is 100mm.\nZlen\nInput a dimensional value in the field to define the Zlength size of the stiffener box. The default size is 100mm.\nSelect All Stiffeners\nSelect the check box to define the size and material for all stiffener boxes in the list of available stiffeners.\nClick Apply to modify the size and material of the stiffener box. Click Cancel to discard any changes and close the Set Stiffener/Material Size window.\nXlen\nInput a dimensional value in the field to define the Xlength size of the stiffener box. The default size is 100mm.\nYlen\nInput a dimensional value in the field to define the Ylength size of the stiffener box. The default size is 100mm.\nZlen\nInput a dimensional value in the field to define the Zlength size of the stiffener box. The default size is 100mm.\nSelect All Stiffeners\nSelect the check box to define the size and material for all stiffener boxes in the list of available stiffeners.\n\n\n\nIdentify stiffener plate (BOX)\nSet Stiffener/Material Size\nXlen\nYlen\nZlen\nSelect All Stiffeners\nApply\nCancel\nSet Stiffener/Material Size"}
{"Headers": "Create Special Support from Existing Supports", "Content": "Creates a special support from existing supports, you can select the supports to be used.\n\nThe special support name displays at the top of the Support Editor window.\nThe top part of the support editor window allows you to define the support type.\nBuild\nSelect from the drop-down list to define the special support type. The available support types are:\nMulti Discipline Support\nHVAC Support\nRacking Support\nBuild\nSelect from the drop-down list to define the special support type. The available support types are:\nYou must select existing supports to create as special supports. The first support identified is used as the master support. The datum of the master support is used as the datum for the resulting special support.\nSupport Name\nInput the name of the existing support in the field. Alternatively, click CE to populate the field with a the name of the currently selected support.\nAdd Support\nClick to add the currently selected support to the list of supports.\nAdd By Cursor\nClick to add a support to the list of supports using a cursor pick in the 3D view.\nYou are prompted to Identify Support to Add (Existing MDS Support) to a Special Framework or <ESC> to finish :\nYou can continue to identify additional supports using a cursor pick in the 3D view.\nPress ESC to add the supports to the list of supports.\nA confirm window displays asking you to OK the selection. Click Yes to add the selected supports to the list of supports.\nRemove Support\nClick to remove the currently selected support from the list of supports.\nUse Selected Support as Master\nClick to assign the currently selected support as the master support.\nA confirm window displays asking you to OK the selection. Click Yes to apply the selected support as the master support.\nSupport Name\nInput the name of the existing support in the field. Alternatively, click CE to populate the field with a the name of the currently selected support.\nAdd Support\nClick to add the currently selected support to the list of supports.\nAdd By Cursor\nClick to add a support to the list of supports using a cursor pick in the 3D view.\nYou are prompted to Identify Support to Add (Existing MDS Support) to a Special Framework or <ESC> to finish :\nYou can continue to identify additional supports using a cursor pick in the 3D view.\nPress ESC to add the supports to the list of supports.\nA confirm window displays asking you to OK the selection. Click Yes to add the selected supports to the list of supports.\nRemove Support\nClick to remove the currently selected support from the list of supports.\nUse Selected Support as Master\nClick to assign the currently selected support as the master support.\nA confirm window displays asking you to OK the selection. Click Yes to apply the selected support as the master support.\nClick Apply to create the special support or Cancel to discard any inputs and close the Create a Special Support window. A confirm window displays asking you to OK the selection. Click Yes to create the special support.\nBuild\nSelect from the drop-down list to define the special support type. The available support types are:\nMulti Discipline Support\nHVAC Support\nRacking Support\nSupport Name\nInput the name of the existing support in the field. Alternatively, click CE to populate the field with a the name of the currently selected support.\nAdd Support\nClick to add the currently selected support to the list of supports.\nAdd By Cursor\nClick to add a support to the list of supports using a cursor pick in the 3D view.\nYou are prompted to Identify Support to Add (Existing MDS Support) to a Special Framework or <ESC> to finish :\nYou can continue to identify additional supports using a cursor pick in the 3D view.\nPress ESC to add the supports to the list of supports.\nA confirm window displays asking you to OK the selection. Click Yes to add the selected supports to the list of supports.\nRemove Support\nClick to remove the currently selected support from the list of supports.\nUse Selected Support as Master\nClick to assign the currently selected support as the master support.\nA confirm window displays asking you to OK the selection. Click Yes to apply the selected support as the master support.\nMulti Discipline Support\nHVAC Support\nRacking Support\nMulti Discipline Support\nMulti Discipline Support\nHVAC Support\nHVAC Support\nRacking Support\nRacking Support\n\n\n\nSupport Editor\nBuild\nSupport Name\nCE\nAdd Support\nAdd By Cursor\nIdentify Support to Add (Existing MDS Support) to a Special Framework or <ESC> to finish :\nESC\nYes\nRemove Support\nUse Selected Support as Master\nYes\nApply\nCancel\nCreate a Special Support\nYes"}
{"Headers": "Reference Supports", "Content": "The Reference Supports part of the Support Editor window allows you to add an existing ancillary to a support as a referenced support.\n\nFor example, when creating a new framework support, if there is an ancillary created on another pipe that you wish reference to the support, you can select the ancillary and it becomes associated with the support.\nThe availability of reference support functionality is defined by the administrator, refer to Unique Support Names (MDSUNIQUENAMES) for further information.\nThe reference supports functionality is available for the following framework supports:\nAdd Reference Support\nClick to reference an existing ancillary with a support. You must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify standalone ancillary to add\nThe ancillary is added to the support as a reference support and a new tab is created for the ancillary in the Support Editor window.\nThe unique name for the referenced ancillary is retained. You can modify the dimensions of the framework to include the added ancillary. Refer to 2D View for further information.\nRemove Reference Support\nClick to remove a referenced ancillary from the support. A confirm window displays informing you that the changes cannot be cancelled. Click Yes to continue.\nYou must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify reference support ancillary to remove\nA confirm window displays asking you to OK the reference removal. Click Yes to remove the reference from the support. The tab containing the ancillary is removed from the Support Editor window.\nRemove All Supports\nClick to remove all referenced ancillaries from the support. A confirm window displays informing you that the changes cannot be cancelled. Click Yes to continue.\nA confirm window then displays asking you to OK the reference removal. Click Yes to remove the references from the support. The tabs containing the ancillaries are removed from the Support Editor window.\n\nAdd Reference Support\nClick to reference an existing ancillary with a support. You must identify the ancillary using a cursor pick in the 3D view.\n\nYou are prompted to Identify standalone ancillary to add\nThe ancillary is added to the support as a reference support and a new tab is created for the ancillary in the Support Editor window.\nThe unique name for the referenced ancillary is retained. You can modify the dimensions of the framework to include the added ancillary. Refer to 2D View for further information.\n\n\nRemove Reference Support\nClick to remove a referenced ancillary from the support. A confirm window displays informing you that the changes cannot be cancelled. Click Yes to continue.\nYou must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify reference support ancillary to remove\nA confirm window displays asking you to OK the reference removal. Click Yes to remove the reference from the support. The tab containing the ancillary is removed from the Support Editor window.\n\nRemove All Supports\nClick to remove all referenced ancillaries from the support. A confirm window displays informing you that the changes cannot be cancelled. Click Yes to continue.\nA confirm window then displays asking you to OK the reference removal. Click Yes to remove the references from the support. The tabs containing the ancillaries are removed from the Support Editor window.\n\nAdd Reference Support\nClick to reference an existing ancillary with a support. You must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify standalone ancillary to add\nThe ancillary is added to the support as a reference support and a new tab is created for the ancillary in the Support Editor window.\nThe unique name for the referenced ancillary is retained. You can modify the dimensions of the framework to include the added ancillary. Refer to 2D View for further information.\nRemove Reference Support\nClick to remove a referenced ancillary from the support. A confirm window displays informing you that the changes cannot be cancelled. Click Yes to continue.\nYou must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify reference support ancillary to remove\nA confirm window displays asking you to OK the reference removal. Click Yes to remove the reference from the support. The tab containing the ancillary is removed from the Support Editor window.\nRemove All Supports\nClick to remove all referenced ancillaries from the support. A confirm window displays informing you that the changes cannot be cancelled. Click Yes to continue.\nA confirm window then displays asking you to OK the reference removal. Click Yes to remove the references from the support. The tabs containing the ancillaries are removed from the Support Editor window.\nXFT03\nXFT04\nXFT07\nXFT08\nXFT09\nXFT10\nXFT11\nXFT13\nXFT14\nXFT15\nXFT17\nXFT24\nXFT03\nXFT03\nXFT04\nXFT04\nXFT07\nXFT07\nXFT08\nXFT08\nXFT09\nXFT09\nXFT10\nXFT10\nXFT11\nXFT11\nXFT13\nXFT13\nXFT14\nXFT14\nXFT15\nXFT15\nXFT17\nXFT17\nXFT24\nXFT24\n\n\n\nUnique Support Names (MDSUNIQUENAMES)\n2D View\nReference Supports\nSupport Editor\nUnique Support Names (MDSUNIQUENAMES)\nAdd Reference Support\nIdentify standalone ancillary to add\nSupport Editor\n2D View\nRemove Reference Support\nYes\nIdentify reference support ancillary to remove\nYes\nSupport Editor\nRemove All Supports\nYes\nYes\nSupport Editor"}
{"Headers": "Compensation Plates", "Content": "The Compensation Plates part of the Support Editor window allows you to create and modify compensating plates in order to fill any gaps between framework supports and ancillaries.\n\nCompensating plate options, sizing rules and materials are defined by the administrator, refer to Compensation Plates for further information.\nThe compensating plate functionality is available for the following framework supports:\nCreate Compensation\nClick to create a compensation plate. You must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ANCI\nThe compensating plate is added to the framework support and displays in the 3D view. The compensation plate can then be modified.\nModify Compensations\nAllows you to modify a compensation plate. Refer to Modify Compensation Plate Material and Size for further information.\nDelete Compensations\nClick to delete a compensation plate. You must identify the compensation plate or the associated ancillary using a cursor pick in the 3D view.\nYou are prompted to Pick compensation plate/profile or compensated ancillary\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\n\nCreate Compensation\nClick to create a compensation plate. You must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ANCI\nThe compensating plate is added to the framework support and displays in the 3D view. The compensation plate can then be modified.\n\nModify Compensations\nAllows you to modify a compensation plate. Refer to Modify Compensation Plate Material and Size for further information.\n\nDelete Compensations\nClick to delete a compensation plate. You must identify the compensation plate or the associated ancillary using a cursor pick in the 3D view.\nYou are prompted to Pick compensation plate/profile or compensated ancillary\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\n\nCreate Compensation\nClick to create a compensation plate. You must identify the ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ANCI\nThe compensating plate is added to the framework support and displays in the 3D view. The compensation plate can then be modified.\nModify Compensations\nAllows you to modify a compensation plate. Refer to Modify Compensation Plate Material and Size for further information.\nDelete Compensations\nClick to delete a compensation plate. You must identify the compensation plate or the associated ancillary using a cursor pick in the 3D view.\nYou are prompted to Pick compensation plate/profile or compensated ancillary\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nXFT03\nXFT04\nXFT07\nXFT08\nXFT09\nXFT10\nXFT11\nXFT13\nXFT14\nXFT15\nXFT17\nXFT24\nXFT03\nXFT03\nXFT04\nXFT04\nXFT07\nXFT07\nXFT08\nXFT08\nXFT09\nXFT09\nXFT10\nXFT10\nXFT11\nXFT11\nXFT13\nXFT13\nXFT14\nXFT14\nXFT15\nXFT15\nXFT17\nXFT17\nXFT24\nXFT24\n\n\n\nCompensation Plates\nModify Compensation Plate Material and Size\nCompensation Plates\nSupport Editor\nCompensation Plates\nCreate Compensation\nIdentify ANCI\nModify Compensations\nModify Compensation Plate Material and Size\nDelete Compensations\nPick compensation plate/profile or compensated ancillary\nYes"}
{"Headers": "Modify Compensation Plate Material and Size", "Content": "Sets the material and size of a compensation plate.\n\nIf the framework support contains more than one compensation plate, you can select a compensation plate to modify from the drop-down list.\nInput a value in the X-size or Y-Size text fields to define the dimensions of the compensation plate.\nSelect the appropriate material from the Matref drop-down list.\nSelect the Display Dimensions check box to display the compensating plate dimensions in the 3D view. Clear the check box to remove the compensating plate dimensions from the 3D view.\nClick Default to return the compensating plate to the default settings. Click Reset to return the compensating plate to the state prior to modifying.\nClick Cancel to close the Compensation window.\n\n\n\nX-size\nY-Size\nMatref\nDisplay Dimensions\nDefault\nReset\nCancel\nCompensation"}
{"Headers": "Framework Support", "Content": "Creates a framework support.\nThe standard framework supports in the Supports application are designed using structural sections and are template driven.\nYou can create the following types of framework support:\nMulti Discipline Framework\nCable Tray Framework\nHVAC Framework\nGuide Framework\nVessel Framework\nMulti Discipline Framework\nMulti Discipline Framework\nCable Tray Framework\nCable Tray Framework\nHVAC Framework\nHVAC Framework\nGuide Framework\nGuide Framework\nVessel Framework\nVessel Framework\n\n\n\nMulti Discipline Framework\nCable Tray Framework\nHVAC Framework\nGuide Framework\nVessel Framework\nMulti Discipline Framework\nCable Tray Framework\nHVAC Framework\nGuide Framework\nVessel Framework"}
{"Headers": "Multi Discipline Framework", "Content": "Creates a multi discipline framework support from a selection in the Multi Discipline Frameworks gallery.\nThe multi discipline framework supports in the Supports application are used for supporting pipework. A default set of multi discipline framework support templates are supplied with the Supports application.\nYou can create multi discipline framework supports using a combination of framework types and ancillaries, you are guided by a series of prompts throughout the creation process.\nFor example, to create an XFT09 multi discipline framework support with an XAT003 ancillary that is connected to steelwork, on the Multi Discipline Frameworks gallery, click XFT09.\n\nYou are prompted to Identify tube of datum pipe or support\nClick to identify the pipe to support using a cursor pick in the 3D view to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries for the selected pipe bore. Refer to Ancillary Selection for further information.\nSelect XAT003 - Clamp on pipe shoe for N.B. 3/4\" to 20\" on the Ancillary Selection window and click OK.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nYou are prompted to Please identify element to Support from or press <Esc> to create by Dimension\nClick to identify the element to support from using a cursor pick in the 3D view.\nYou are then prompted to Please identify other element to Support from or press <Esc> to create by Clearance\nClick to identify the second element to support from using a cursor pick in the 3D view to display the Support Editor window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\nPress ESC to modify the support creation method.\nCreate by Dimension\nPress ESC to create the support using the default dimensions, no connections are made to steelwork.\nCreate by Clearance\nPress ESC to create the support using the dimensions gained from the position of the identified element.\nThe clearances are calculated from the default values, obtained from:\nThe values stored against each ancillary standard in the Aveva Catalogue\u2122 defaults database. If unset, the clearance values from the Supports Application Defaults window are used. Refer to Supports Defaults for further information.\nThe build style of the framework stored against the :MDSBUILDSTYL uda at each framework template STRU element. That is, the default is INSIDE and the alternative value is OUTSIDE.\nThe clearance values and all other default values can be queried by displaying the Supports Application Defaults window. Refer to Supports Defaults and Automatic Steelwork Orientation for further information.\nCreate by Dimension\nPress ESC to create the support using the default dimensions, no connections are made to steelwork.\n\nCreate by Clearance\nPress ESC to create the support using the dimensions gained from the position of the identified element.\n\nThe clearances are calculated from the default values, obtained from:\nThe clearance values and all other default values can be queried by displaying the Supports Application Defaults window. Refer to Supports Defaults and Automatic Steelwork Orientation for further information.\nCertain supports do not require you to pick a second element to support from (for example XFT04).\nIn this case, once the element to support from has been picked, the support is created using either the create by cursor or create by clearance method, whichever is appropriate. If both methods are appropriate, the support is created using the create by cursor method.\nCreate by Cursor\nThe support is created using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified supporting elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\nCreate by Cursor\nThe support is created using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified supporting elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\n\nThe new SUPPO, SUPC, ANCI, STRU, FRMW, GENSEC and TMPL elements are added to the owning ZONE and display in the Model Explorer.\n\nCreate by Dimension\nPress ESC to create the support using the default dimensions, no connections are made to steelwork.\nCreate by Clearance\nPress ESC to create the support using the dimensions gained from the position of the identified element.\nThe clearances are calculated from the default values, obtained from:\nThe values stored against each ancillary standard in the Aveva Catalogue\u2122 defaults database. If unset, the clearance values from the Supports Application Defaults window are used. Refer to Supports Defaults for further information.\nThe build style of the framework stored against the :MDSBUILDSTYL uda at each framework template STRU element. That is, the default is INSIDE and the alternative value is OUTSIDE.\nThe clearance values and all other default values can be queried by displaying the Supports Application Defaults window. Refer to Supports Defaults and Automatic Steelwork Orientation for further information.\nCreate by Cursor\nThe support is created using dimensions gained from the positions of the identified elements.\nBy default, connections are made to the identified supporting elements which results in some Dimensions fields becoming inactive. Refer to Supports Connectivity for further information.\nThe values stored against each ancillary standard in the Aveva Catalogue\u2122 defaults database. If unset, the clearance values from the Supports Application Defaults window are used. Refer to Supports Defaults for further information.\nThe build style of the framework stored against the :MDSBUILDSTYL uda at each framework template STRU element. That is, the default is INSIDE and the alternative value is OUTSIDE.\nThe values stored against each ancillary standard in the Aveva Catalogue\u2122 defaults database. If unset, the clearance values from the Supports Application Defaults window are used. Refer to Supports Defaults for further information.\nThe values stored against each ancillary standard in the Aveva Catalogue\u2122 defaults database. If unset, the clearance values from the Supports Application Defaults window are used. Refer to Supports Defaults for further information.\nThe build style of the framework stored against the :MDSBUILDSTYL uda at each framework template STRU element. That is, the default is INSIDE and the alternative value is OUTSIDE.\nThe build style of the framework stored against the :MDSBUILDSTYL uda at each framework template STRU element. That is, the default is INSIDE and the alternative value is OUTSIDE.\nNote:\nThe prompt does not display if the pipe to be supported is already selected.\nNote:\nIf you create a support on a vertical pipe or create an ancillary on a vertical framework section, the Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\n\n\n\nAncillary Selection\nSupport Editor\nDatum Attachment Direction\nSupports Defaults\nSupports Defaults\nAutomatic Steelwork Orientation\nSupports Connectivity\nMulti Discipline Frameworks\nMulti Discipline Frameworks\nIdentify tube of datum pipe or support\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nXAT003 - Clamp on pipe shoe for N.B. 3/4\" to 20\"\nAncillary Selection\nOK\nCancel\nAncillary Selection\nPlease identify element to Support from or press <Esc> to create by Dimension\nPlease identify other element to Support from or press <Esc> to create by Clearance\nSupport Editor\nSupport Editor\nSupport Editor\nNote\n:\nDatum attachment direction\nDatum Attachment Direction\nESC\nCreate by Dimension\nESC\nCreate by Clearance\nESC\nSupports Defaults\nSupports Defaults\nAutomatic Steelwork Orientation\nCreate by Cursor\nDimensions\nSupports Connectivity"}
{"Headers": "Datum Attachment Direction", "Content": "Sets the direction angle of an ancillary that is positioned on a vertical pipe or a vertical framework section.\n\nInput a value in the Ancillary Direction field, for example, input N to direct the ancillary north.\nClick OK to apply the ancillary direction, the Support Editor window displays, by default. Click Cancel to discard any changes and close the Datum attachment direction window.\n\n\n\nAncillary Direction\nN\nOK\nSupport Editor\nCancel\nDatum attachment direction"}
{"Headers": "Support Configurations", "Content": "Sets the orientation of the support framework to allow for connection to a structural component.\nThe support configuration functionality is available for the following framework supports:\n\nAbove beam\nSelect from the gallery to orientate the support framework to align above a horizontal beam.\nOnto column\nSelect from the gallery to orientate the support framework to align with a vertical column.\nTo beam\nSelect from the gallery to orientate the support framework to align with a horizontal beam.\nAbove beam\nSelect from the gallery to orientate the support framework to align above a horizontal beam.\nOnto column\nSelect from the gallery to orientate the support framework to align with a vertical column.\nTo beam\nSelect from the gallery to orientate the support framework to align with a horizontal beam.\nClick Cancel to discard any changes and close the Support Configurations window.\nAbove beam\nSelect from the gallery to orientate the support framework to align above a horizontal beam.\nOnto column\nSelect from the gallery to orientate the support framework to align with a vertical column.\nTo beam\nSelect from the gallery to orientate the support framework to align with a horizontal beam.\nXFT03\nXFT04\nXFT03\nXFT03\nXFT04\nXFT04\n\n\n\nAbove beam\nOnto column\nTo beam\nCancel\nSupport Configurations"}
{"Headers": "Open/Closed End Clearance", "Content": "The clearance between the ancillary and the open/closed ends of a framework support can be modified for each ancillary at each bore. Refer to Framework Clearance Option, Closed End Clearance, Open End Clearance for further information.\n\n\n\nFramework Clearance Option, Closed End Clearance, Open End Clearance\nFramework Clearance Option, Closed End Clearance, Open End Clearance"}
{"Headers": "Cable Tray Framework", "Content": "Creates a cable tray framework support from a selection in the Cable Tray Frameworks gallery.\nThe cable tray framework supports in the Supports application are used for supporting cable trays, (both piping based cable trays (BRAN) and cable trays (CTRAY)). A default set of cable tray framework support templates are supplied with the Supports application.\nYou can create cable tray framework supports using a combination of framework types and ancillaries, you are guided by a series of prompts throughout the creation process.\nFor example, to create an XCT05 cable tray framework support with an XCA02 ancillary that is connected to steelwork, on the Cable Tray Frameworks gallery, click XCT05.\n\nYou are prompted to Identify section of datum cable rack or support\nClick to identify the cable tray to support using a cursor pick in the 3D view to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries for the selected cable tray. Refer to Ancillary Selection for further information.\nSelect XCA02 - Cable Clip on the Ancillary Selection window and click OK, to display the Support Editor window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nYou are prompted to Please identify element to Support from or press <Esc> to create by Dimension\nClick to identify the element to support from using a cursor pick in the 3D view.\nYou are then prompted to Please identify other element to Support from or press <Esc> to create by Clearance\nClick to identify the second element to support from using a cursor pick in the 3D view to display the Support Editor window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\nPress ESC to modify the support creation method.\nCreate by Dimension\nRefer to Multi Discipline Framework for further information.\nCreate by Clearance\nRefer to Multi Discipline Framework for further information.\nCreate by Dimension\nRefer to Multi Discipline Framework for further information.\n\nCreate by Clearance\nRefer to Multi Discipline Framework for further information.\n\nCertain supports do not require you to pick a second element to support from (for example XCT01).\nIn this case, once the element to support from has been picked, the support is created using either the create by cursor or create by clearance method, whichever is appropriate. If both methods are appropriate, the support is created using the create by cursor method. Refer to Multi Discipline Framework for further information.\n\nThe new SUPPO, SUPC, ANCI, STRU, FRMW and GENSEC elements are added to the owning ZONE and display in the Model Explorer.\n\nCreate by Dimension\nRefer to Multi Discipline Framework for further information.\nCreate by Clearance\nRefer to Multi Discipline Framework for further information.\nNote:\nOnly the support framework can be created for cable trays with non-standard bore sizes, ancillaries cannot be created.\nNote:\nThe prompt does not display if the cable tray to be supported is already selected.\nNote:\nIf you create a support on a vertical pipe or create an ancillary on a vertical framework section, the Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\n\n\n\nAncillary Selection\nSupport Editor\nDatum Attachment Direction\nMulti Discipline Framework\nMulti Discipline Framework\nMulti Discipline Framework\nCable Tray Frameworks\nNote\n:\nCable Tray Frameworks\nIdentify section of datum cable rack or support\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nXCA02 - Cable Clip\nAncillary Selection\nOK\nSupport Editor\nCancel\nAncillary Selection\nPlease identify element to Support from or press <Esc> to create by Dimension\nPlease identify other element to Support from or press <Esc> to create by Clearance\nSupport Editor\nSupport Editor\nSupport Editor\nNote\n:\nDatum attachment direction\nDatum Attachment Direction\nESC\nCreate by Dimension\nMulti Discipline Framework\nCreate by Clearance\nMulti Discipline Framework\nMulti Discipline Framework"}
{"Headers": "HVAC Framework", "Content": "Creates a HVAC framework support from a selection in the HVAC Frameworks gallery.\nThe HVAC framework supports in the Supports application are used for supporting HVAC ducts. A default set of HVAC framework support templates are supplied with the Supports application.\nYou can create HVAC framework supports using a combination of framework types and ancillaries, you are guided by a series of prompts throughout the creation process.\nFor example, to create an XDT01 HVAC framework support with an XRT02 HVAC-REST ancillary that is connected to steelwork, on the HVAC Frameworks gallery, click XDT01.\n\nYou are prompted to Identify HVAC section of datum HVAC or support\nClick to identify the HVAC duct to support using a cursor pick in the 3D view to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries for the selected HVAC duct. Refer to Ancillary Selection for further information.\nSelect XRT02 - HVAC-REST on the Ancillary Selection window and click OK, to display the Support Editor window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nYou are prompted to Please identify element to Support from or press <Esc> to create by Dimension\nClick to identify the element to support from using a cursor pick in the 3D view.\nYou are then prompted to Please identify other element to Support from or press <Esc> to create by Clearance\nClick to identify the second element to support from using a cursor pick in the 3D view to display the Support Editor window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\nPress ESC to modify the support creation method.\nCreate by Dimension\nRefer to Multi Discipline Framework for further information.\nCreate by Clearance\nRefer to Multi Discipline Framework for further information.\nCreate by Dimension\nRefer to Multi Discipline Framework for further information.\n\nCreate by Clearance\nRefer to Multi Discipline Framework for further information.\n\nCertain supports do not require you to pick a second element to support from (for example XDT02).\nIn this case, once the element to support from has been picked, the support is created using either the create by cursor or create by clearance method, whichever is appropriate. If both methods are appropriate, the support is created using the create by cursor method. Refer to Multi Discipline Framework for further information.\n\nThe new SUPPO, SUPC, ANCI, STRU, FRMW and GENSEC elements are added to the owning ZONE and display in the Model Explorer.\n\nCreate by Dimension\nRefer to Multi Discipline Framework for further information.\nCreate by Clearance\nRefer to Multi Discipline Framework for further information.\nNote:\nOnly the support framework can be created for HVAC ducts with non-standard bore sizes, ancillaries cannot be created.\nNote:\nThe prompt does not display if the HVAC duct to be supported is already selected.\nNote:\nIf you create a support on a vertical pipe or create an ancillary on a vertical framework section, the Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\n\n\n\nAncillary Selection\nSupport Editor\nDatum Attachment Direction\nMulti Discipline Framework\nMulti Discipline Framework\nMulti Discipline Framework\nHVAC Frameworks\nNote\n:\nHVAC Frameworks\nIdentify HVAC section of datum HVAC or support\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nXRT02 - HVAC-REST\nAncillary Selection\nOK\nSupport Editor\nCancel\nAncillary Selection\nPlease identify element to Support from or press <Esc> to create by Dimension\nPlease identify other element to Support from or press <Esc> to create by Clearance\nSupport Editor\nSupport Editor\nSupport Editor\nNote\n:\nDatum attachment direction\nDatum Attachment Direction\nESC\nCreate by Dimension\nMulti Discipline Framework\nCreate by Clearance\nMulti Discipline Framework\nMulti Discipline Framework"}
{"Headers": "Guide Framework", "Content": "Creates a guide framework support from a selection in the Guide Frameworks gallery.\nThe guide framework supports in the Supports application are used for supporting pipework. A default set of guide framework support templates are supplied with the Supports application.\nYou can create guide framework supports using defined framework types, you are guided by a series of prompts throughout the creation process.\nFor example, to create an XGT05 guide framework support that is connected to steelwork, on the Guide Frameworks gallery, click XGT05.\n\nYou are prompted to Identify tube of datum pipe or support\nYou are prompted to Please identify element to Support from or press <Esc> to create by Dimension\nClick to identify the element to support from using a cursor pick in the 3D view.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\nThroughout the support creation process you can press ESC to access additional functionality.\n\nCreate by Dimension\nPress ESC to create the support using the default dimensions, no connections are made to steelwork.\nCreate by Dimension\nPress ESC to create the support using the default dimensions, no connections are made to steelwork.\n\nThe new SUPPO, SUPC, ANCI, STRU, FRMW and GENSEC elements are added to the owning ZONE and display in the Model Explorer.\n\nCreate by Dimension\nPress ESC to create the support using the default dimensions, no connections are made to steelwork.\nNote:\nThe prompt does not display if the pipe to be supported is already selected.\nNote:\nIf you create a support on a vertical pipe or create an ancillary on a vertical framework section, the Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\n\n\n\nSupport Editor\nDatum Attachment Direction\nGuide Frameworks\nGuide Frameworks\nIdentify tube of datum pipe or support\nNote\n:\nPlease identify element to Support from or press <Esc> to create by Dimension\nSupport Editor\nSupport Editor\nNote\n:\nDatum attachment direction\nDatum Attachment Direction\nCreate by Dimension\nESC"}
{"Headers": "Vessel Framework", "Content": "Creates a vessel framework support from a selection in the Vessel Frameworks gallery.\nThe vessel framework supports in the Supports application are used for supporting pipework. A default set of vessel framework support templates are supplied with the Supports application.\nYou can create vessel framework supports using a combination of framework types and ancillaries, you are guided by a series of prompts throughout the creation process.\n\nFor example, to create an XVT07 vessel support with an XLT03 ancillary, on the Vessel Frameworks gallery, click XVT07.\n\nYou are prompted to Identify tube of datum pipe or support\nClick to identify the pipe to support using a cursor pick in the 3D view to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries for the selected pipe bore. Refer to Ancillary Selection for further information.\nSelect XLT03 - Type A - CS and Alloy Support Lug for Vertical Pipes NPS 2-3 on the Ancillary Selection window and click OK.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nYou are then prompted to Identify first support bracket\nClick to identify the first support bracket using a cursor pick in the 3D view.\nYou are then prompted to Identify second support bracket\nClick to identify the second support bracket using a cursor pick in the 3D view.\nYou are then prompted to Identify vessel wall\nClick to identify the vessel wall using a cursor pick in the 3D view to display the Support Editor window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, LUG, LUANCI, STRU, SUBS, BOX, FRMW and GENSEC elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nSome vessel framework supports require the creation of support brackets on the vessel before creation. In most cases, support brackets can be created as box primitives.\nNote:\nThe prompt does not display if the pipe to be supported is already selected.\nNote:\nIf you create a support on a vertical pipe or create an ancillary on a vertical framework section, the Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\n\n\n\nAncillary Selection\nSupport Editor\nDatum Attachment Direction\nVessel Frameworks\nNote\n:\nVessel Frameworks\nIdentify tube of datum pipe or support\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nXLT03 - Type A - CS and Alloy Support Lug for Vertical Pipes NPS 2-3\nAncillary Selection\nOK\nCancel\nAncillary Selection\nIdentify first support bracket\nIdentify second support bracket\nIdentify vessel wall\nSupport Editor\nSupport Editor\nSupport Editor\nNote\n:\nDatum attachment direction\nDatum Attachment Direction"}
{"Headers": "Preliminary Support", "Content": "Creates a preliminary support from a selection in the Preliminary gallery.\nThe preliminary supports in the Supports application are template driven. A default set of preliminary support templates are supplied with the supports application.\nYou can create the following types of preliminary support:\n\nOn the Preliminary gallery, click the required preliminary support.\nYou are prompted to Identify element you wish to support\nClick to identify the element to support using a cursor pick in the 3D view to display the Support Editor window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and ANCI, elements are added to the owning ZONE and display in the Model Explorer.\n\nPreliminary anchor\nPreliminary guide\nPreliminary constant effort spring hanger\nPreliminary fixed hanger\nPreliminary variable spring hanger\nPreliminary hold down\nPreliminary rest\nPreliminary stop\nPreliminary anchor\nPreliminary anchor\nPreliminary guide\nPreliminary guide\nPreliminary constant effort spring hanger\nPreliminary constant effort spring hanger\nPreliminary fixed hanger\nPreliminary fixed hanger\nPreliminary variable spring hanger\nPreliminary variable spring hanger\nPreliminary hold down\nPreliminary hold down\nPreliminary rest\nPreliminary rest\nPreliminary stop\nPreliminary stop\nNote:\nThe prompt does not display if the element to be supported is already selected.\n\n\n\nSupport Editor\nPreliminary\nPreliminary\nIdentify element you wish to support\nNote\n:\nSupport Editor\nSupport Editor\nSupport Editor"}
{"Headers": "Convert Preliminary Support to Framework Support", "Content": "Converts an existing preliminary support to a framework support, ancillary or trunnion.\nFor example, an XAT001 support shoe can be created from a preliminary support that is configured with an ANCHOR (AN) support function. Refer to Ancillary Data for further information.\nTo convert an existing preliminary support into an ancillary, you must first select the preliminary support.\n\nOn the Stand Alone Supports gallery, click Ancillaries to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries. Refer to Ancillary Selection for further information.\nSelect XAT001 - Pipe shoe for N.B. 3/4\" to 20\" on the Ancillary Selection window and Click OK.\nThe Supports application detects that the support function of the chosen ancillary differs from that of the preliminary support function. This is because the preliminary support function is \u2018AN\u2019 and the XAT001 support shoe support function is \u2018AT\u2019. A Confirm message displays:\n\nClick Yes to confirm the conversion of the preliminary support to an XAT001 support shoe. The Support Editor window displays, you can modify the XAT001 support shoe. Refer to Support Editor for further information.\n\nNote:\nA preliminary support cannot be converted if it is locked or stored in a read only database. A confirm window displays summarizing the problem. Click Yes to continue with the conversion process. A new support is created at the same position as the preliminary support. The original preliminary support is not deleted.\nNote:\nDependant on the type of support to be converted from a preliminary support, you may be required to select additional components to complete the conversion process. For example, when converting a preliminary support to a slip unit, you are prompted to Identify Atta. You must select an appropriate component to associate the slip unit with. For example an XAT001 general ancillary.\n\n\n\nAncillary Data\nAncillary Selection\nSupport Editor\nNote\n:\nYes\nAncillary Data\nStand Alone Supports\nAncillaries\nAncillary Selection\nAncillary Selection\nAncillary Selection\nXAT001 - Pipe shoe for N.B. 3/4\" to 20\"\nAncillary Selection\nOK\nYes\nSupport Editor\nSupport Editor\nNote\n:\nIdentify Atta"}
{"Headers": "Convert Preliminary Support and Add to Existing Support", "Content": "Adds an existing preliminary support to an existing support and converts it to a support ancillary.\n\nOn the Support Editor window, click Support additional pipe HVAC, or cable tray. Refer to Support Editor for further information.\nYou are prompted to Identify element you wish to support :\nClick to identify the preliminary support to convert using a cursor pick in the 3D view to display the Ancillary Selection window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries. Refer to Ancillary Selection for further information.\nSelect an Ancillary on the Ancillary Selection window and Click OK.\nIf the supports application detects that the support function of the chosen ancillary differs from that of the preliminary support function a Confirm message displays.\n\nClick Yes to confirm the conversion of the preliminary support to an ancillary.\nThe support is added as an ancillary to the existing support and renamed, by default. A new tab is created on the Support Editor window allowing you to modify the size and position of the ancillary.\nClick Apply to convert the support or Cancel to discard any changes and close the Support Editor window.\n\nThe preliminary support is converted to an ANCI element and added to the existing support in the Model Explorer.\n\nNote:\nThe preliminary support is only added to the existing support if unique special support numbering is set to No, refer to Supports Defaults for further information. If the unique special support numbering is set to Yes, the preliminary support is added to the existing support as a reference support. Refer to Reference Supports for further information.\nA preliminary support cannot be converted if it is locked or stored in a read only database. A confirm window displays summarizing the problem. Click Yes to continue with the conversion process. A new support is created at the same position as the preliminary support in the current supports zone. The original preliminary support is not deleted.\n\n\n\nSupports Defaults\nReference Supports\nSupport Editor\nAncillary Selection\nNote\n:\nSupports Defaults\nReference Supports\nYes\nSupport Editor\nSupport additional pipe HVAC, or cable tray\nSupport Editor\nIdentify element you wish to support :\nAncillary Selection\nAncillary Selection\nAncillary Selection\nan Ancillary\nAncillary Selection\nOK\nYes\nSupport Editor\nApply\nCancel\nSupport Editor"}
{"Headers": "Convert Preliminary Support to Hanger", "Content": "Converts an existing preliminary support to a hanger.\nAll hanger types, including interface hangers, can be created from an existing preliminary support. For the purposes of this guide, only the creation of a single to beam hanger is described.\nYou can create steelwork hangers using a combination of hanger types and ancillaries, you are guided by a series of prompts throughout the creation process.\nFor example, to create a FH T1 M1 B6 fixed hanger from an existing preliminary hanger, on the Hangers to Steelwork gallery, click Single to Beam.\n\nYou are prompted to Identify tube of datum pipe or support\nClick to identify the existing preliminary support using a cursor pick in the 3D view.\nYou are then prompted to Identify steelwork member to connect hanger to\nClick to identify the supporting steelwork section using a cursor pick in the 3D view to display the Template Hanger Creation window. Refer to Template Hanger Creation for further information\nSelect FH T1 M1 B6 - Fixed Hanger NPS 3 - 24 on the Template Hanger Creation window and click OK.\nClick Cancel to discard any changes and close the Template Hanger Creation window.\nThe Supports application detects that the support function of the chosen hanger differs from that of the preliminary support function. This is because the preliminary support function is \u2018AN\u2019 and the hanger support function is \u2018FH\u2019. A Confirm message displays:\n\nClick Yes to confirm the conversion of the preliminary support to a hanger. The Support Editor window displays, you can modify the hanger. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and HANG elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the existing preliminary support is already selected.\n\n\n\nTemplate Hanger Creation\nSupport Editor\nHangers to Steelwork\nSingle to Beam\nIdentify tube of datum pipe or support\nNote\n:\nIdentify steelwork member to connect hanger to\nTemplate Hanger Creation\nTemplate Hanger Creation\nFH T1 M1 B6 - Fixed Hanger NPS 3 - 24\nTemplate Hanger Creation\nOK\nCancel\nTemplate Hanger Creation\nYes\nSupport Editor\nSupport Editor"}
{"Headers": "Convert Preliminary Support to Special Support", "Content": "Converts an existing preliminary support to a special support.\nYou can create special supports using a combination of framework types and ancillaries, you are guided by a series of prompts throughout the creation process.\nYou are prompted to Identify tube of datum pipe or support\nClick to identify the existing preliminary support using a cursor pick in the 3D view to display the Ancillary Selection window.\n\nThe Ancillary Selection window displays all of the available/unavailable ancillaries for the existing preliminary support. Refer to Ancillary Selection for further information.\nSelect the required ancillary, for example, XAN02, on the Ancillary Selection window and click OK, to display the Support Editor window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe project special template can then be copied into the existing special support using the Special part of the Support Editor window. Refer to Special Supports for further information.\n\nThe new SUPPO, SUPC, ANCI, STRU, FRMW and GENSEC elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the existing preliminary support is already selected.\n\n\n\nAncillary Selection\nSpecial Supports\nIdentify tube of datum pipe or support\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nAncillary Selection\nOK\nSupport Editor\nCancel\nAncillary Selection\nSpecial\nSupport Editor\nSpecial Supports"}
{"Headers": "Ancillaries", "Content": "Creates an ancillary support.\nThe ancillaries in the Supports application are template driven. Default template sets are supplied with the Supports application.\nYou can create the following types of ancillaries.\nAnchor\nAncillary\nBranch Reinforcement\nGuide\nLug\nStop\nAnchor\nAnchor\nAncillary\nAncillary\nBranch Reinforcement\nBranch Reinforcement\nGuide\nGuide\nLug\nLug\nStop\nStop\n\n\n\nAnchor\nAncillary\nBranch Reinforcement\nGuide\nLug\nStop\nAnchor\nAncillary\nBranch Reinforcement\nGuide\nLug\nStop"}
{"Headers": "Anchor", "Content": "Creates an anchor support from a selection in the Stand Alone Supports gallery.\nThe anchors in the Supports application are template driven. A default set of anchor templates are supplied with the Supports application.\nTo create an anchor, on the Stand Alone Supports gallery, click Anchors.\n\nYou are prompted to Identify element you wish to support\nClick to identify the pipe to support using a cursor pick in the 3D view to display the Ancillary Selection window.\nThe Ancillary Selection window displays a filtered list of all available/unavailable anchors for the selected pipe bore. Refer to Ancillary Selection for further information.\nYou must select an anchor from the list of available anchors. For example, click XAN02 - Pipe Shoe Anchor and click OK to display the Support Editor Window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and ANCI elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the element to be supported is already selected.\nNote:\nIf you create an anchor on a vertical pipe or a vertical framework section, the Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\n\n\n\nAncillary Selection\nSupport Editor\nDatum Attachment Direction\nStand Alone Supports\nStand Alone Supports\nAnchors\nIdentify element you wish to support\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nXAN02 - Pipe Shoe Anchor\nOK\nSupport Editor\nCancel\nAncillary Selection\nSupport Editor\nSupport Editor\nNote\n:\nDatum attachment direction\nDatum Attachment Direction"}
{"Headers": "Ancillary", "Content": "Creates an ancillary support from a selection in the Stand Alone Supports gallery.\nThe ancillaries in the Supports application are template driven. A default set of ancillary templates are supplied with the Supports application.\nTo create an ancillary, on the Stand Alone Supports gallery, click Ancillary.\n\nYou are prompted to Identify element you wish to support\nClick to identify the element to support using a cursor pick in the 3D view to display the Ancillary Selection window.\nThe Ancillary Selection window displays a filtered list of all available/unavailable anchors for the selected pipe bore. Refer to Ancillary Selection for further information.\nYou must select an ancillary from the list of available ancillaries. For example, click XAT001 - Pipe shoe for N.B. 3/4\" to 20\" and click OK to display the Support Editor window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and ANCI elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the element to be supported is already selected.\nNote:\nIf you create an anchor on a vertical pipe or a vertical framework section, the Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\n\n\n\nAncillary Selection\nSupport Editor\nDatum Attachment Direction\nStand Alone Supports\nStand Alone Supports\nAncillary.\nIdentify element you wish to support\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nXAT001 - Pipe shoe for N.B. 3/4\" to 20\"\nOK\nSupport Editor\nCancel\nAncillary Selection\nSupport Editor\nSupport Editor\nNote\n:\nDatum attachment direction\nDatum Attachment Direction"}
{"Headers": "Branch Reinforcement", "Content": "Creates a branch reinforcement from a selection in the Stand Alone Supports gallery.\nThe branch reinforcements in the Supports application are template driven. A default set of branch reinforcement templates are supplied with the Supports application.\nTo create a branch reinforcement, on the Stand Alone Supports gallery, click Branch Reinforcement.\n\nYou are prompted to Identify suitable TEE, OLET, FLANGE, ELBOW, PCOM or REDU component to support\nClick to identify the element to support using a cursor pick in the 3D view to display the Ancillary Selection window.\n\nThe Ancillary Selection window displays a filtered list of all available/unavailable branch reinforcements for the selected pipe bore. Refer to Ancillary Selection for further information.\nYou must select a branch reinforcement from the list of available branch reinforcements. For example, click XBR04 - 4 Way Brace for Open Ended Connection to Pipe and click OK.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nYou are then prompted to Identify second branch tube\n\nClick to identify the branch tube to support using a cursor pick in the 3D view to display the Support Editor window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and ANCI elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the element to be supported is already selected.\n\n\n\nAncillary Selection\nSupport Editor\nStand Alone Supports\nStand Alone Supports\nBranch Reinforcement.\nIdentify suitable TEE, OLET, FLANGE, ELBOW, PCOM or REDU component to support\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nXBR04 - 4 Way Brace for Open Ended Connection to Pipe\nOK\nCancel\nAncillary Selection\nIdentify second branch tube\nSupport Editor\nSupport Editor\nSupport Editor"}
{"Headers": "Guide", "Content": "Creates a guide support from a selection in the Stand Alone Supports gallery.\nThe guides in the Supports application are template driven. A default set of guide templates are supplied with the Supports application.\nTo create a guide, on the Stand Alone Supports gallery, click Guides.\n\nYou are prompted to Identify tube of datum pipe\nClick to identify the pipe to support using a cursor pick in the 3D view to display the Ancillary Selection window.\nThe Ancillary Selection window displays a filtered list of all available/unavailable guides for the selected pipe bore. Refer to Ancillary Selection for further information.\nYou must select a guide from the list of available guides. For example, click XGT02 - Pipe guide for uninsulated pipes and click OK to display the Support Editor Window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and ANCI elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the element to be supported is already selected.\n\n\n\nAncillary Selection\nSupport Editor\nStand Alone Supports\nStand Alone Supports\nGuides\nIdentify tube of datum pipe\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nXGT02 - Pipe guide for uninsulated pipes\nOK\nSupport Editor\nCancel\nAncillary Selection\nSupport Editor\nSupport Editor"}
{"Headers": "Lug", "Content": "Creates a lug support from a selection in the Stand Alone Supports gallery.\nThe lugs in the Supports application are template driven. A default set of lug templates are supplied with the Supports application.\nTo create a lug, on the Stand Alone Supports gallery, click Lugs.\n\nYou are prompted to Identify tube of datum pipe\nClick to identify the pipe to support using a cursor pick in the 3D view to display the Ancillary Selection window.\nThe Ancillary Selection window displays a filtered list of all available/unavailable lugs for the selected pipe bore. Refer to Ancillary Selection for further information.\nYou must select a lug from the list of available lugs. For example, click XLT01A - Shear Lug (Lug only) and click OK to display the Support Editor Window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, LUG and LUANCI elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the element to be supported is already selected.\n\n\n\nAncillary Selection\nSupport Editor\nStand Alone Supports\nStand Alone Supports\nLugs\nIdentify tube of datum pipe\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nXLT01A - Shear Lug (Lug only)\nOK\nSupport Editor\nCancel\nAncillary Selection\nSupport Editor\nSupport Editor"}
{"Headers": "Stop", "Content": "Creates a stop support from a selection in the Stand Alone Supports gallery.\nThe stops in the Supports application are template driven. A default set of stop templates are supplied with the Supports application.\nTo create a stop, on the Stand Alone Supports gallery, click Stops.\n\nYou are prompted to Identify tube of datum pipe\nClick to identify the pipe to support using a cursor pick in the 3D view to display the Ancillary Selection window.\nThe Ancillary Selection window displays a filtered list of all available/unavailable stops for the selected pipe bore. Refer to Ancillary Selection for further information.\nYou must select a stop from the list of available stops. For example, click XST01 - Pipe stop for insulated C.S. pipes and click OK.\nYou are prompted to Identify steelwork to guide from or ESC\nClick to identify the associated steelwork using a cursor pick in the 3D view to display the Support Editor Window. Alternatively, press ESC to create a stop with default values.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and ANCI elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the element to be supported is already selected.\n\n\n\nAncillary Selection\nSupport Editor\nStand Alone Supports\nStand Alone Supports\nStops\nIdentify tube of datum pipe\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nXST01 - Pipe stop for insulated C.S. pipes\nOK\nIdentify steelwork to guide from or ESC\nSupport Editor\nESC\nCancel\nAncillary Selection\nSupport Editor\nSupport Editor"}
{"Headers": "Special Support", "Content": "Creates a special support for a project that requires a support that does not conform to any of the supplied configurations.\nYou can create the following types of special support:\nSpecial supports can also be created from an existing multi discipline support, HVAC support or racking support. Refer to Create Special Support from Existing Supports for further information.\nMulti Discipline Special Support\nHVAC Special Support\nRacking Special Support\nLighting Support\nMulti Discipline Special Support\nMulti Discipline Special Support\nHVAC Special Support\nHVAC Special Support\nRacking Special Support\nRacking Special Support\nLighting Support\nLighting Support\n\n\n\nMulti Discipline Special Support\nHVAC Special Support\nRacking Special Support\nLighting Support\nCreate Special Support from Existing Supports\nMulti Discipline Special Support\nHVAC Special Support\nRacking Special Support\nLighting Support\nCreate Special Support from Existing Supports"}
{"Headers": "Multi Discipline Special Support", "Content": "Creates a special support that supports pipework.\nYou can create multi discipline special supports using a combination of framework types and ancillaries, you are guided by a series of prompts throughout the creation process.\nYou are prompted to Identify tube of datum pipe or support\nClick to identify the pipe to support using a cursor pick in the 3D view to display the Ancillary Selection window.\n\nThe Ancillary Selection window displays all of the available/unavailable ancillaries for the selected pipe bore. Refer to Ancillary Selection for further information.\nSelect the required ancillary, for example, XAT003, on the Ancillary Selection window and click OK, to display the Support Editor window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC, ANCI, STRU, FRMW and GENSEC elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the pipe to be supported is already selected.\nNote:\nIf you create a special support on a vertical pipe or create an ancillary on a vertical framework section, the Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\n\n\n\nAncillary Selection\nSupport Editor\nDatum Attachment Direction\nIdentify tube of datum pipe or support\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nAncillary Selection\nOK\nSupport Editor\nCancel\nAncillary Selection\nSupport Editor\nSupport Editor\nNote\n:\nDatum attachment direction\nDatum Attachment Direction"}
{"Headers": "HVAC Special Support", "Content": "Creates a special support that supports a HVAC duct.\nYou can create HVAC special supports using a combination of framework types and ancillaries, you are guided by a series of prompts throughout the creation process.\nYou are prompted to Identify element you wish to support\nClick to identify the HVAC duct to support using a cursor pick in the 3D view to display the Ancillary Selection window.\n\nThe Ancillary Selection window displays all of the available/unavailable ancillaries for the selected HVAC duct. Refer to Ancillary Selection for further information.\nSelect the required ancillary on the Ancillary Selection window and click OK, to display the Support Editor window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC, ANCI, STRU, FRMW and GENSEC elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the HVAC duct to be supported is already selected.\nNote:\nIf you create a special support on a vertical HVAC duct, the Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\n\n\n\nAncillary Selection\nSupport Editor\nDatum Attachment Direction\nIdentify element you wish to support\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nAncillary Selection\nOK\nSupport Editor\nCancel\nAncillary Selection\nSupport Editor\nSupport Editor\nNote\n:\nDatum attachment direction\nDatum Attachment Direction"}
{"Headers": "Racking Special Support", "Content": "Creates a special support that supports a cable tray.\nYou can create racking special supports using a combination framework types and ancillaries, you are guided by a series of prompts throughout the creation process.\nYou are prompted to Identify element you wish to support\n\nThe Ancillary Selection window displays all of the available/unavailable ancillaries for the selected cable tray. Refer to Ancillary Selection for further information.\nSelect the required ancillary on the Ancillary Selection window and click OK, to display the Support Editor window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC, ANCI, STRU, FRMW and GENSEC elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the cable tray to be supported is already selected.\nNote:\nIf you create a special support on a vertical cable tray, the Datum attachment direction window displays by default. Refer to Datum Attachment Direction for further information.\n\n\n\nAncillary Selection\nSupport Editor\nDatum Attachment Direction\nIdentify element you wish to support\nNote\n:\nAncillary Selection\nAncillary Selection\nAncillary Selection\nOK\nSupport Editor\nCancel\nAncillary Selection\nSupport Editor\nSupport Editor\nNote\n:\nDatum attachment direction\nDatum Attachment Direction"}
{"Headers": "Lighting Support", "Content": "Creates a special support that supports electrical light fittings. A light fitting is identified as an EQUIP element with the Purpose attribute set to LIGH.\nYou can create lighting supports using a lighting support template, you are guided by a series of prompts throughout the creation process.\nYou are prompted to Identify Lighting Equipment you wish to support\nClick to identify the light fitting to support using a cursor pick in the 3D view to display the Select Required Template and Support Editor windows.\n\nThe Select Required Template window displays all of the available lighting support templates for the selected light fitting. Refer to Select Required Template for further information.\nSelect the required template, for example, Lighting hanger (wall mounted), on the Select Required Template window and click Cancel to close the window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, STRU, SUBS, CYLI, BOX, FRMW and GENSEC elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the light fitting to be supported is already selected.\n\n\n\nSelect Required Template\nSupport Editor\nIdentify Lighting Equipment you wish to support\nNote\n:\nSelect Required Template\nSupport Editor\nSelect Required Template\nSelect Required Template\nLighting hanger (wall mounted)\nSelect Required Template\nCancel\nSupport Editor\nSupport Editor"}
{"Headers": "Hanger", "Content": "Creates a hanger support.\nThe standard Supports application for hangers allows you to create fixed and variable pipe hangers. The application is interactive and configurable, and simplifies:\nHangers are designed using the hanger components catalogue of a given supplier and are template-driven.\nThe available hanger types can contain three prefix characters:\nFor example, a T1 M2 B4 hanger has a T1 type top connection, M2 type middle connection, and a B4 type pipe connection.\nYou can create the following types of hanger:\nDefinition of project related defaults\nControl of hanger design\nDetermination of range, types, and configuration of hanger components that can be used on the project.\nDefinition of project related defaults\nDefinition of project related defaults\nControl of hanger design\nControl of hanger design\nDetermination of range, types, and configuration of hanger components that can be used on the project.\nDetermination of range, types, and configuration of hanger components that can be used on the project.\nT (Top)\nM (Middle)\nB (Bottom).\nT (Top)\nT (Top)\nM (Middle)\nM (Middle)\nB (Bottom).\nB (Bottom).\nSteelwork Hanger\nSpring Hanger\nSteelwork Hanger\nSteelwork Hanger\nSpring Hanger\nSpring Hanger\n\n\n\nSteelwork Hanger\nSpring Hanger\nSteelwork Hanger\nSpring Hanger"}
{"Headers": "Steelwork Hanger", "Content": "Steelwork hangers in the Supports application are used for supporting pipework from structural section elements. You can create the following types of steelwork hanger:\nSingle to Beam Hanger\nSingle to Double Channels Hanger\nDouble to Beam Hanger\nDouble to Channels Hanger\nSingle to Beam Hanger\nSingle to Beam Hanger\nSingle to Double Channels Hanger\nSingle to Double Channels Hanger\nDouble to Beam Hanger\nDouble to Beam Hanger\nDouble to Channels Hanger\nDouble to Channels Hanger\n\n\n\nSingle to Beam Hanger\nSingle to Double Channels Hanger\nDouble to Beam Hanger\nDouble to Channels Hanger\nSingle to Beam Hanger\nSingle to Double Channels Hanger\nDouble to Beam Hanger\nDouble to Channels Hanger"}
{"Headers": "Single to Beam Hanger", "Content": "Creates a single to beam hanger from a selection in the Hangers to Steelwork gallery.\nThe single to beam hangers in the Supports application are used for supporting pipework using a single hanger connected to a single structural section. A default set of hanger templates are supplied with the Supports application.\nYou can create steelwork hangers using a combination of hanger types and ancillaries, you are guided by a series of prompts throughout the creation process.\nFor example, to create a FH T1 M1 B6 fixed hanger, on the Hangers to Steelwork gallery, click Single to Beam.\n\nYou are prompted to Identify tube of datum pipe or support\nClick to identify the pipe to support using a cursor pick in the 3D view.\nYou are then prompted to Identify steelwork member to connect hanger to\nClick to identify the supporting steelwork section using a cursor pick in the 3D view to display the Template Hanger Creation window. Refer to Template Hanger Creation for further information\nSelect FH T1 M1 B6 - Fixed Hanger NPS 3 - 24 on the Template Hanger Creation window and click OK to display the Support Editor window.\nClick Cancel to discard any changes and close the Template Hanger Creation window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and HANG elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the pipe to be supported is already selected.\n\n\n\nTemplate Hanger Creation\nSupport Editor\nHangers to Steelwork\nHangers to Steelwork\nSingle to Beam\nIdentify tube of datum pipe or support\nNote\n:\nIdentify steelwork member to connect hanger to\nTemplate Hanger Creation\nTemplate Hanger Creation\nFH T1 M1 B6 - Fixed Hanger NPS 3 - 24\nTemplate Hanger Creation\nOK\nSupport Editor\nCancel\nTemplate Hanger Creation\nSupport Editor\nSupport Editor"}
{"Headers": "Template Hanger Creation", "Content": "Displays all of the available fixed and variable hangers for the selected pipe bore.\n\nFixed Hangers\nThe Fixed Hangers tab allows you to select a hanger from a filtered list of available fixed hangers that are suitable for the pipe to be supported.\nVariable Hangers\nThe Variable Hangers tab allows you to select a hanger from a filtered list of available variable hangers that are suitable for the pipe to be supported.\n\nPreview\nThe Preview part of the Template Hanger Creation window allows you to view a 2D representation of the currently selected hanger.\n\n\n\nFixed Hangers\nFixed Hangers\nVariable Hangers\nVariable Hangers\nPreview\nPreview\nTemplate Hanger Creation"}
{"Headers": "View Hanger Standard", "Content": "Displays an illustration of the selected hanger, click View to display the View Multi Discipline Standard window.\nThe functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\nFunctionality is also available to view a representation of the hanger configuration, click View Config to display the Hanger Configuration Viewer window.\n\nClick Cancel to close the Hanger Configuration Viewer window.\n\n\n\nView Multi Discipline Support Standard\nView\nView Multi Discipline Standard\nView Multi Discipline Standard\nView Multi Discipline Support Standard\nView Config\nHanger Configuration Viewer\nCancel\nHanger Configuration Viewer"}
{"Headers": "Single to Double Channels Hanger", "Content": "Creates a single to double channels hanger from a selection in the Hangers to Steelwork gallery.\nThe single to double channels hangers in the Supports application are used for supporting pipework using a single hanger connected to two channelled structural sections. A default set of hanger templates are supplied with the Supports application.\nYou can create steelwork hangers using a combination of hanger types and ancillaries, you are guided by a series of prompts throughout the creation process.\nFor example, to create a VH T4 M3 B1 variable hanger, on the Hangers to Steelwork gallery, click Single to Double Channels.\n\nYou are prompted to Identify tube of datum pipe or support\nClick to identify the pipe to support using a cursor pick in the 3D view.\nYou are then prompted to Identify first channel\nClick to identify the first supporting steelwork section using a cursor pick in the 3D view.\nYou are then prompted to Identify second channel\nClick to identify the second supporting steelwork section using a cursor pick in the 3D view to display the Template Hanger Creation window. Refer to Template Hanger Creation for further information.\nSelect VH T4 M3 B1 - Variable Hanger NPS 3/4 - 6 on the Template Hanger Creation window and click OK to display the Support Editor window.\nClick Cancel to discard any changes and close the Template Hanger Creation window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and HANG elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the pipe to be supported is already selected.\n\n\n\nTemplate Hanger Creation\nSupport Editor\nHangers to Steelwork\nHangers to Steelwork\nSingle to Double Channels\nIdentify tube of datum pipe or support\nNote\n:\nIdentify first channel\nIdentify second channel\nTemplate Hanger Creation\nTemplate Hanger Creation\nVH T4 M3 B1 - Variable Hanger NPS 3/4 - 6\nTemplate Hanger Creation\nOK\nSupport Editor\nCancel\nTemplate Hanger Creation\nSupport Editor\nSupport Editor"}
{"Headers": "Double to Beam Hanger", "Content": "Creates a double to beam hanger from a selection in the Hangers to Steelwork gallery.\nThe double to beam hangers in the Supports application are used for supporting pipework using two hangers connected to either a single perpendicular structural section or two parallel structural sections.\nYou can create steelwork hangers using a combination of hanger types and ancillaries, you are guided by a series of prompts throughout the creation process.\nFor example, to create a VH T4 M1 B14 variable hanger with an XAT003 ancillary, on the Hangers to Steelwork gallery, click Double to Beam.\n\nYou are prompted to Identify tube of datum pipe or support\nClick to identify the pipe to support using a cursor pick in the 3D view.\nYou are then prompted to Identify first steelwork member to connect hanger to\nClick to identify the first supporting steelwork section using a cursor pick in the 3D view.\nYou are then prompted to Identify second steelwork member to connect hanger to\nClick to identify the second supporting steelwork section using a cursor pick in the 3D view to display the Template Hanger Creation window. Refer to Template Hanger Creation for further information.\nSelect VH T4 M1 B14 - Variable Hanger NPS 3 - 24 on the Template Hanger Creation window and click OK to display the Ancillary Selection window.\nClick Cancel to discard any changes and close the Template Hanger Creation window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries for the selected pipe bore. Refer to Ancillary Selection for further information.\nSelect XAT003 - Clamp on pipe shoe for N.B. 3/4\" to 20\" on the Ancillary Selection window and click OK, to display the Support Editor window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and HANG elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the pipe to be supported is already selected.\n\n\n\nTemplate Hanger Creation\nAncillary Selection\nSupport Editor\nHangers to Steelwork\nHangers to Steelwork\nDouble to Beam\nIdentify tube of datum pipe or support\nNote\n:\nIdentify first steelwork member to connect hanger to\nIdentify second steelwork member to connect hanger to\nTemplate Hanger Creation\nTemplate Hanger Creation\nVH T4 M1 B14 - Variable Hanger NPS 3 - 24\nTemplate Hanger Creation\nOK\nAncillary Selection\nCancel\nTemplate Hanger Creation\nAncillary Selection\nAncillary Selection\nXAT003 - Clamp on pipe shoe for N.B. 3/4\" to 20\"\nAncillary Selection\nOK\nSupport Editor\nCancel\nAncillary Selection\nSupport Editor\nSupport Editor"}
{"Headers": "Double to Channels Hanger", "Content": "Creates a double to channels hanger from a selection in the Hangers to Steelwork gallery.\nThe double to channels hangers in the Supports application are used for supporting pipework using two hangers, each hanger is connected to two channelled structural sections\nYou can create steelwork hangers using a combination of hanger types and ancillaries, you are guided by a series of prompts throughout the creation process.\nFor example, to create a VH T4 M2 B13 variable hanger with an XAT005 ancillary, On the Hangers to Steelwork gallery, click Double to Channels.\n\nYou are prompted to Identify tube of datum pipe or support\nClick to identify the pipe to support using a cursor pick in the 3D view.\nYou are then prompted to Identify first steelwork member to connect hanger to\nClick to identify the first supporting steelwork section using a cursor pick in the 3D view.\nYou are then prompted to Identify first adjacent steelwork member to connect hanger to\nClick to identify the first adjacent supporting steelwork section using a cursor pick in the 3D view.\nYou are then prompted to Identify the first member of the second pair to connect hanger to\nClick to identify the second supporting steelwork section using a cursor pick in the 3D view.\nYou are then prompted to Identify the second adjacent steelwork member of the second pair\nClick to identify the second adjacent supporting steelwork section using a cursor pick in the 3D view to display the Template Hanger Creation window. Refer to Template Hanger Creation for further information.\nSelect VH T4 M2 B13 - Variable Hanger NPS 3 - 24 on the Template Hanger Creation window and click OK to display the Ancillary Selection window.\nClick Cancel to discard any changes and close the Template Hanger Creation window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries for the selected pipe bore. Refer to Ancillary Selection for further information.\nSelect XAT005 - Reinforcing plate (cut from pipe) on the Ancillary Selection window and click OK, to display the Support Editor window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and HANG elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the pipe to be supported is already selected.\n\n\n\nTemplate Hanger Creation\nAncillary Selection\nSupport Editor\nHangers to Steelwork\nHangers to Steelwork\nDouble to Channels\nIdentify tube of datum pipe or support\nNote\n:\nIdentify first steelwork member to connect hanger to\nIdentify first adjacent steelwork member to connect hanger to\nIdentify the first member of the second pair to connect hanger to\nIdentify the second adjacent steelwork member of the second pair\nTemplate Hanger Creation\nTemplate Hanger Creation\nVH T4 M2 B13 - Variable Hanger NPS 3 - 24\nTemplate Hanger Creation\nOK\nAncillary Selection\nCancel\nTemplate Hanger Creation\nAncillary Selection\nAncillary Selection\nXAT005 - Reinforcing plate (cut from pipe)\nAncillary Selection\nOK\nSupport Editor\nCancel\nAncillary Selection\nSupport Editor\nSupport Editor"}
{"Headers": "Spring Hanger", "Content": "Creates a spring hanger from a selection in the Springs gallery.\nThe spring hangers in the Supports application are used for supporting pipework using a sprung pedestal. A default set of hanger templates are supplied with the Supports application.\nYou can create spring hangers using a combination of hanger types, ancillaries and springs, you are guided by a series of prompts throughout the creation process.\nFor example, to create a VHB16 variable hanger with an XAT005 ancillary and a BM1 spring, on the Springs gallery, click Pedestal.\n\nYou are prompted to Identify tube of datum pipe\nClick to identify the pipe to support using a cursor pick in the 3D view to display the Template Hanger Creation window. Refer to Template Hanger Creation for further information.\nSelect VH B15 - Variable Pedestal NPS 3 - 24 on the Template Hanger Creation window and click OK to display the Ancillary Selection window.\nClick Cancel to discard any changes and close the Template Hanger Creation window.\nThe Ancillary Selection window displays all of the available/unavailable ancillaries for the selected pipe bore. Refer to Ancillary Selection for further information.\nSelect XAT005 - Reinforcing plate (cut from pipe) on the Ancillary Selection window and click OK, to display the Choose VSPR window.\nClick Cancel to discard any changes and close the Ancillary Selection window.\nThe Choose VSPR window displays all of the variable springs for the selected hanger. Refer to Modify Hanger Spring Type for further information.\nSelect VAR EFFORT BM1 SPRING TYPE 1 RANGE V3 on the Choose VSPR window and click OK, to display the Support Editor window.\nClick Cancel to discard any changes and close the Choose VSPR window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, SUPC and HANG elements are added to the owning ZONE and display in the Model Explorer.\n\nNote:\nThe prompt does not display if the pipe to be supported is already selected.\n\n\n\nTemplate Hanger Creation\nAncillary Selection\nModify Hanger Spring Type\nSupport Editor\nSprings\nSprings\nPedestal\nIdentify tube of datum pipe\nNote\n:\nTemplate Hanger Creation\nTemplate Hanger Creation\nVH B15 - Variable Pedestal NPS 3 - 24\nTemplate Hanger Creation\nOK\nAncillary Selection\nCancel\nTemplate Hanger Creation\nAncillary Selection\nAncillary Selection\nXAT005 - Reinforcing plate (cut from pipe)\nAncillary Selection\nOK\nChoose VSPR\nCancel\nAncillary Selection\nChoose VSPR\nModify Hanger Spring Type\nVAR EFFORT BM1 SPRING TYPE 1 RANGE V3\nChoose VSPR\nOK\nSupport Editor\nCancel\nChoose VSPR\nSupport Editor\nSupport Editor"}
{"Headers": "Hanger Manufacturer\u2019s Design Interface", "Content": "Hangers can be created by interfacing with the Witch Hanger interface (Carpenter & Paterson Ltd. hanger design software) or the LICAD interface (Lisega GMBH hanger design software).\nThe hanger design interface can be interfaced with the supports application to build hangers from manufacturer\u2019s catalogues.\nThe support is created in the 3D model using AVEVA E3D Design and then output to the manufacturer\u2019s interface for design and processing.\nWhen a support has been configured in the manufacturer\u2019s interface, control returns to AVEVA E3D Design and the support can be built in the model using data supplied by the manufacturer.\nThe manufacturer\u2019s interface can be used to define hangers that are connected to steelwork or civil elements.\nOnce a hanger type selection has been made, the manufacturer's hanger interface can be accessed using the Support Editor window. Refer to Support Editor for further information.\n\n\n\nSupport Editor\nAVEVA E3D Design\nAVEVA E3D Design\nSupport Editor\nSupport Editor"}
{"Headers": "Trunnion", "Content": "Creates a trunnion support from a selection in the Trunnions gallery.\nThe trunnions in the Supports application are template driven. A default set of trunnion templates are supplied with the Supports application.\nA trunnion support can be created on the following types of piping component:\nYou can create trunnions with a number of associated ancillaries, you are guided by a series of prompts throughout the creation process.\nA trunnion is designed to a standard. A trunnion can have associated ancillaries, which are themselves standards.\nFor example, to create an XTT06 trunnion with an associated ancillary, weld and plates, on the Trunnions gallery, click XTT06.\n\nYou are prompted to Identify tube of datum pipe\nClick to identify the piping component to support using a cursor pick in the 3D view to display the Support Editor window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\n\nThe new SUPPO, TRUNNI, TRANCI, TRREDU, WELD and PLAT elements are added to the owning ZONE and display in the Model Explorer.\n\nElbow\nBend\nTee\nReducer\nTube\nElbow\nElbow\nBend\nBend\nTee\nTee\nReducer\nReducer\nTube\nTube\nNote:\nA plate is cut from an elbow of the same size and is itemised as extra material on the isometric drawing.\nNote:\nThe prompt does not display if the piping component to be supported is already selected.\nNote:\nIn some cases, you are required to select the trunnion build direction. Refer to Trunnion Build Direction for further information.\n\n\n\nSupport Editor\nTrunnion Build Direction\nTrunnions\nNote\n:\nTrunnions\nIdentify tube of datum pipe\nNote\n:\nSupport Editor\nSupport Editor\nSupport Editor\nNote\n:\nTrunnion Build Direction"}
{"Headers": "Trunnion Build Direction", "Content": "In some cases, for example, when creating an XTT42 trunnion, you are required to select the trunnion build direction.\nIf the elbow has neither an arrive or leave pointing in the up or down direction, a Confirm window displays.\n\nClick Yes to build the trunnion in the arrive direction. Click No to build the trunnion in the leave direction.\n\nIf the elbow has an arrive or leave pointing in the up or down direction, a Confirm window displays.\n\nClick Yes to build the trunnion in the vertical direction. Click No to build the trunnion in the horizontal direction.\n\n\n\nConfirm\nYes\nNo\nConfirm\nYes\nNo"}
{"Headers": "Modify Support", "Content": "Modifies a support or its ancillaries.\nYou are prompted to Pick Support :\nClick to identify the support using a cursor pick in the 3D view to display the Support Editor window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\nModify Framework Support containing a Locked Ancillary\nYou can modify a framework support if it contains a locked ancillary. If the ancillary is locked by the Lock attribute, or the Position attribute is locked by Data Access Control, the support can be modified but only certain modifications are allowed. Functionality is available to use Status Control and DAC to lock ancillaries in response to design approval whilst allowing scope for acceptable modification thereafter.\nYou may not make modifications that affect the whole support, for example, modifying the position, flipping or mirroring. You may not make modifications that affect the locked ancillary directly, for example, modifying the datum ancillary, reselecting the ancillary, adding or modifying packing pieces or compensation plates, or modifying reinforcement pad details.\nConfigurations FT05 and CT03 do not support further modification when an ancillary is locked as the application requires write access to the whole support.\nYou can make modifications to the support that do not impact the locked ancillary, for example, adding a pipe, tray or duct, extending sections, adding bracing or reselecting structural members. Modifications cannot be made to a locked ancillary, for example, as a result of a structural change, and if needed this is detected by the support health check.\nNote:\nThe prompt does not display if the support to be modified is already selected.\n\n\n\nSupport Editor\nPick Support :\nNote\n:\nSupport Editor\nSupport Editor\nSupport Editor"}
{"Headers": "Convert Support to Special Support", "Content": "Creates a special support from an existing support for a project that does not conform to any of the supplied configurations.\nA confirm window displays asking you to OK the conversion. Click Yes to convert the support to a special support.\n\nThe special support can then be modified using the Support Editor window. Refer to Support Editor for further information.\n\n\n\nSupport Editor\nYes\nSupport Editor\nSupport Editor"}
{"Headers": "Delete Support", "Content": "Deletes a support or a number of supports.\nThe functionality allows you to:\nDelete Selected Support\nDelete All Supports\nDelete Selected Support\nDelete Selected Support\nDelete All Supports\nDelete All Supports\n\n\n\nDelete Selected Support\nDelete All Supports\nDelete Selected Support\nDelete All Supports"}
{"Headers": "Delete Selected Support", "Content": "Deletes a support.\nYou are prompted to Pick Support or <ESC> to finish :\nClick to identify the support(s) to be deleted using a cursor pick in the 3D view.\nPress ESC to delete the selected support(s).\nIf the support(s) are associated with reference supports, a confirm window displays asking you if reference supports are to be included in the deletion. Click Yes to delete reference supports, click No to omit reference supports from the deletion.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the support(s).\nNote:\nThe prompt does not display if the support(s) to be deleted are already selected.\n\n\n\nPick Support or <ESC> to finish :\nNote\n:\nESC\nYes\nNo\nYes"}
{"Headers": "Delete All Supports", "Content": "Deletes all supports on a pipe, branch, HVAC duct or cable tray. Supports that are locked or claimed by another user are not deleted.\nIf the supports are associated with reference supports, a confirm window displays asking you if reference supports are to be included in the deletion. Click Yes to delete reference supports, click No to omit reference supports from the deletion.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the supports.\n\n\n\nYes\nNo\nYes"}
{"Headers": "Supports Defaults", "Content": "Displays the Supports application defaults.\nThe Supports application defaults are set by the administrator. You can modify some of the defaults using the Supports Application Defaults window. Refer to Application Defaults for further information.\n\n\n\n\nApplication Defaults\nSupports Application Defaults\nApplication Defaults"}
{"Headers": "Reload the Latest Defaults", "Content": "Reloads the latest Supports application defaults.\nA Confirm window displays, click Yes to reload the defaults.\n\n\n\n\nYes"}
{"Headers": "Weld Defaults", "Content": "Sets the default weld definitions.\nWelds for ancillaries and joints are created in the DESI database called /MDS/WELDS by the administrator. Most of the Framework welds for sections and joints are also created in this way. However, some welds are not part of the template and must be created during Support creation. Refer to Create Framework Support Weld for further information.\nYou can view the default welds for:\nStandard Welds\nFramework Weld Selection\nAncillary Weld Selection\nStandard Welds\nStandard Welds\nFramework Weld Selection\nFramework Weld Selection\nAncillary Weld Selection\nAncillary Weld Selection\n\n\n\nCreate Framework Support Weld\nStandard Welds\nFramework Weld Selection\nAncillary Weld Selection\nCreate Framework Support Weld\nStandard Welds\nFramework Weld Selection\nAncillary Weld Selection"}
{"Headers": "Standard Welds", "Content": "Sets the weld areas and weld items for the project.\n\nThe list of existing areas displays all currently available created weld areas.\nCreate Weld Area\nAllows you to create a weld area for the storage of weld items. Refer to Create Weld Area for further information\nDelete Weld Area\nClick to delete the currently selected weld area.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld area.\nCreate Weld Area\nAllows you to create a weld area for the storage of weld items. Refer to Create Weld Area for further information\nDelete Weld Area\nClick to delete the currently selected weld area.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld area.\nThe list of existing welds displays the available weld items for the currently selected weld area.\nCreate Weld\nAllows you to create a weld item. Refer to Create and Modify Weld Item for further information\nDelete Weld\nClick to delete the currently selected weld item.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld item.\nModify Weld\nAllows you to modify a weld item. Refer to Create and Modify Weld Item for further information\nCreate Weld\nAllows you to create a weld item. Refer to Create and Modify Weld Item for further information\nDelete Weld\nClick to delete the currently selected weld item.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld item.\nModify Weld\nAllows you to modify a weld item. Refer to Create and Modify Weld Item for further information\nThe name, symbol name and description for the currently selected weld item displays at the bottom of the Standard Welds window.\nClick OK to define the standard welds or Cancel to discard any inputs and close the Standard Welds window.\nCreate Weld Area\nAllows you to create a weld area for the storage of weld items. Refer to Create Weld Area for further information\nDelete Weld Area\nClick to delete the currently selected weld area.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld area.\nCreate Weld\nAllows you to create a weld item. Refer to Create and Modify Weld Item for further information\nDelete Weld\nClick to delete the currently selected weld item.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld item.\nModify Weld\nAllows you to modify a weld item. Refer to Create and Modify Weld Item for further information\n\n\n\nCreate Weld Area\nCreate and Modify Weld Item\nCreate and Modify Weld Item\nCreate Weld Area\nCreate Weld Area\nDelete Weld Area\nYes\nCreate Weld\nCreate and Modify Weld Item\nDelete Weld\nYes\nModify Weld\nCreate and Modify Weld Item\nStandard Welds\nCancel"}
{"Headers": "Create Weld Area", "Content": "Sets the name for a new weld area.\n\nInput a name for the new weld area in the Area Name field.\nClick Apply to create a weld area or Cancel to discard any inputs and close the Standard Welds window.\n\n\n\nArea Name\nApply\nCancel"}
{"Headers": "Create and Modify Weld Item", "Content": "Sets the name and description for a weld item.\n\nBy default, the Weld Name and Symbol Name fields are populated with the default storage paths for the weld item, you can modify the path.\nInput a name for the weld item in the Weld Name field.\nInput a name for the weld item in the Symbol Name field.\nInput a description for the weld item in the Description field.\nClick Apply to create/modify a weld item or Cancel to discard any inputs and close the Standard Welds window.\n\n\n\nWeld Name\nSymbol Name\nWeld Name\nSymbol Name\nDescription\nApply\nCancel"}
{"Headers": "Framework Weld Selection", "Content": "Sets the available welds and Ppoints for framework support templates.\n\nThe top part of the Framework Weld Selection window displays a list of available framework types, framework templates, structural members, welds and Ppoints. A visual representation of the currently selected template displays in the view.\nAvailable Types\nSelect an available framework type from the list. By default, the list of available templates is populated with the templates that are associated with the currently selected framework type.\nTemplates\nSelect an available template from the list. By default, the list of available structural members is populated with the members that are associated with the currently selected template.\nStructural Members\nSelect a member from the list. By default, the list of available welds and list of available Ppoints are populated with the welds and Ppoints that are associated with the currently selected member.\nWelds\nSelect a weld from the list to display the weld on the visual representation of the currently selected template.\nPpoints\nSelect a Ppoint from the list to display the Ppoint on the visual representation of the currently selected Template.\nPpoints only display in the list if the joint has a Ppoint with a number of 300 or higher, is a PTCA Ppoint and has a purpose of MWEL.\nView Standard\nAllows you to view an illustration of the selected template. Click to display the View Multi Discipline Standard window.\nThe functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\nAvailable Types\nSelect an available framework type from the list. By default, the list of available templates is populated with the templates that are associated with the currently selected framework type.\nTemplates\nSelect an available template from the list. By default, the list of available structural members is populated with the members that are associated with the currently selected template.\nStructural Members\nSelect a member from the list. By default, the list of available welds and list of available Ppoints are populated with the welds and Ppoints that are associated with the currently selected member.\nWelds\nSelect a weld from the list to display the weld on the visual representation of the currently selected template.\nPpoints\nSelect a Ppoint from the list to display the Ppoint on the visual representation of the currently selected Template.\nPpoints only display in the list if the joint has a Ppoint with a number of 300 or higher, is a PTCA Ppoint and has a purpose of MWEL.\nView Standard\nAllows you to view an illustration of the selected template. Click to display the View Multi Discipline Standard window.\nThe functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\nClick Cancel to close the Framework Weld Selection window.\nAvailable Types\nSelect an available framework type from the list. By default, the list of available templates is populated with the templates that are associated with the currently selected framework type.\nTemplates\nSelect an available template from the list. By default, the list of available structural members is populated with the members that are associated with the currently selected template.\nStructural Members\nSelect a member from the list. By default, the list of available welds and list of available Ppoints are populated with the welds and Ppoints that are associated with the currently selected member.\nWelds\nSelect a weld from the list to display the weld on the visual representation of the currently selected template.\nPpoints\nSelect a Ppoint from the list to display the Ppoint on the visual representation of the currently selected Template.\nPpoints only display in the list if the joint has a Ppoint with a number of 300 or higher, is a PTCA Ppoint and has a purpose of MWEL.\nView Standard\nAllows you to view an illustration of the selected template. Click to display the View Multi Discipline Standard window.\nThe functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\n\n\n\nView Multi Discipline Support Standard\nFramework Weld Selection\nAvailable Types\nTemplates\nStructural Members\nWelds\nPpoints\nView Standard\nView Multi Discipline Standard\nView Multi Discipline Standard\nView Multi Discipline Support Standard\nCancel\nFramework Weld Selection"}
{"Headers": "Ancillary Weld Selection", "Content": "Sets the available welds for ancillary templates.\n\nThe top part of the Ancillary Weld Selection window displays a list of available ancillary types, weld Ppoints and welds.\nAvailable Types\nSelect an available ancillary type from the list. By default, the list of available weld Ppoints and list of available welds are populated with the Ppoints and Welds that are associated with the currently selected ancillary.\nWeld Ppoints\nThe list of available weld Ppoints displays the weld Ppoints associated with the currently selected ancillary.\nSelect a Ppoint in the list to display the welds associated with the Ppoint.\nPpoints only display in the list if the ancillary has a Ppoint with a number of 300 or higher, is a PTCA Ppoint and has a purpose of MWEL.\nWelds\nThe list of available welds displays the welds associated with the currently selected ancillary.\nCreate Weld\nAllows you to select a standard weld to associate with the ancillary. Click to display the Select Standard Weld window.\nThe functionality of the Select Standard Weld window is explained as part of the process to create a framework support weld. Refer to Create New Weld for further information.\nPpoints only display in the list if the ancillary has a Ppoint with a number of 300 or higher, is a PTCA Ppoint and has a purpose of MWEL.\nDelete Weld\nClick to delete the currently selected weld.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld.\nView Standard\nAllows you to view an illustration of the selected ancillary. Click to display the View Multi Discipline Standard window.\nThe functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\nAvailable Types\nSelect an available ancillary type from the list. By default, the list of available weld Ppoints and list of available welds are populated with the Ppoints and Welds that are associated with the currently selected ancillary.\nWeld Ppoints\nThe list of available weld Ppoints displays the weld Ppoints associated with the currently selected ancillary.\nSelect a Ppoint in the list to display the welds associated with the Ppoint.\nPpoints only display in the list if the ancillary has a Ppoint with a number of 300 or higher, is a PTCA Ppoint and has a purpose of MWEL.\nWelds\nThe list of available welds displays the welds associated with the currently selected ancillary.\nCreate Weld\nAllows you to select a standard weld to associate with the ancillary. Click to display the Select Standard Weld window.\nThe functionality of the Select Standard Weld window is explained as part of the process to create a framework support weld. Refer to Create New Weld for further information.\nPpoints only display in the list if the ancillary has a Ppoint with a number of 300 or higher, is a PTCA Ppoint and has a purpose of MWEL.\nDelete Weld\nClick to delete the currently selected weld.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld.\nView Standard\nAllows you to view an illustration of the selected ancillary. Click to display the View Multi Discipline Standard window.\nThe functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\nClick Save to save the ancillary weld data or Cancel to discard any inputs and close the Ancillary Weld Selection window.\nAvailable Types\nSelect an available ancillary type from the list. By default, the list of available weld Ppoints and list of available welds are populated with the Ppoints and Welds that are associated with the currently selected ancillary.\nWeld Ppoints\nThe list of available weld Ppoints displays the weld Ppoints associated with the currently selected ancillary.\nSelect a Ppoint in the list to display the welds associated with the Ppoint.\nPpoints only display in the list if the ancillary has a Ppoint with a number of 300 or higher, is a PTCA Ppoint and has a purpose of MWEL.\nWelds\nThe list of available welds displays the welds associated with the currently selected ancillary.\nCreate Weld\nAllows you to select a standard weld to associate with the ancillary. Click to display the Select Standard Weld window.\nThe functionality of the Select Standard Weld window is explained as part of the process to create a framework support weld. Refer to Create New Weld for further information.\nPpoints only display in the list if the ancillary has a Ppoint with a number of 300 or higher, is a PTCA Ppoint and has a purpose of MWEL.\nDelete Weld\nClick to delete the currently selected weld.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the weld.\nView Standard\nAllows you to view an illustration of the selected ancillary. Click to display the View Multi Discipline Standard window.\nThe functionality of the View Multi Discipline Standard window is explained. Refer to View Multi Discipline Support Standard for further information.\n\n\n\nCreate New Weld\nView Multi Discipline Support Standard\nAncillary Weld Selection\nAvailable Types\nWeld Ppoints\nWelds\nCreate Weld\nSelect Standard Weld\nSelect Standard Weld\nCreate New Weld\nDelete Weld\nYes\nView Standard\nView Multi Discipline Standard\nView Multi Discipline Standard\nView Multi Discipline Support Standard\nSave\nCancel\nAncillary Weld Selection"}
{"Headers": "Supports Tools", "Content": "Modifies the support configuration and associations.\nThe tools available are:\nSupports Browser\nCopy Support\nAlign Supports with Pipe\nReinforcing Pad\nLock/Unlock Support\nSupports ADP Drawlist\nSupports Wizard\nHealth Check\nModify ADP Location Position\nDrawing Comment\nIsometric Control\nDrawing Note\nSpecial Frame Direction\nSet Ancillary Material\nSet Structural Material\nBed/Anchor Plate Reference\nAdd Snipes to Steelwork Members\nSpooling\nAdd Pipe Stress Interface Data\nTrimmer Requirement\nCreate Support Group\nAdd Support to Group\nRemove Support from Group\nView Multi Discipline Support Standard\nView Support Dimensions\nView Pipe Rests\nView Pipe Dimensions\nSupports Browser\nSupports Browser\nCopy Support\nCopy Support\nAlign Supports with Pipe\nAlign Supports with Pipe\nReinforcing Pad\nReinforcing Pad\nLock/Unlock Support\nLock/Unlock Support\nSupports ADP Drawlist\nSupports ADP Drawlist\nSupports Wizard\nSupports Wizard\nHealth Check\nHealth Check\nModify ADP Location Position\nModify ADP Location Position\nDrawing Comment\nDrawing Comment\nIsometric Control\nIsometric Control\nDrawing Note\nDrawing Note\nSpecial Frame Direction\nSpecial Frame Direction\nSet Ancillary Material\nSet Ancillary Material\nSet Structural Material\nSet Structural Material\nBed/Anchor Plate Reference\nBed/Anchor Plate Reference\nAdd Snipes to Steelwork Members\nAdd Snipes to Steelwork Members\nSpooling\nSpooling\nAdd Pipe Stress Interface Data\nAdd Pipe Stress Interface Data\nTrimmer Requirement\nTrimmer Requirement\nCreate Support Group\nCreate Support Group\nAdd Support to Group\nAdd Support to Group\nRemove Support from Group\nRemove Support from Group\nView Multi Discipline Support Standard\nView Multi Discipline Support Standard\nView Support Dimensions\nView Support Dimensions\nView Pipe Rests\nView Pipe Rests\nView Pipe Dimensions\nView Pipe Dimensions\n\n\n\nSupports Browser\nCopy Support\nAlign Supports with Pipe\nReinforcing Pad\nLock/Unlock Support\nSupports ADP Drawlist\nSupports Wizard\nHealth Check\nModify ADP Location Position\nDrawing Comment\nIsometric Control\nDrawing Note\nSpecial Frame Direction\nSet Ancillary Material\nSet Structural Material\nBed/Anchor Plate Reference\nAdd Snipes to Steelwork Members\nSpooling\nAdd Pipe Stress Interface Data\nTrimmer Requirement\nCreate Support Group\nAdd Support to Group\nRemove Support from Group\nView Multi Discipline Support Standard\nView Support Dimensions\nView Pipe Rests\nView Pipe Dimensions\nSupports Browser\nCopy Support\nAlign Supports with Pipe\nReinforcing Pad\nLock/Unlock Support\nSupports ADP Drawlist\nSupports Wizard\nHealth Check\nModify ADP Location Position\nDrawing Comment\nIsometric Control\nDrawing Note\nSpecial Frame Direction\nSet Ancillary Material\nSet Structural Material\nBed/Anchor Plate Reference\nAdd Snipes to Steelwork Members\nSpooling\nAdd Pipe Stress Interface Data\nTrimmer Requirement\nCreate Support Group\nAdd Support to Group\nRemove Support from Group\nView Multi Discipline Support Standard\nView Support Dimensions\nView Pipe Rests\nView Pipe Dimensions"}
{"Headers": "Supports Browser", "Content": "Provides a graphical method for viewing different support types within the project.\n\nThe Supports Browser displays the support elements in a hierarchy. To expand an element hierarchy, click to the left of the element name. To contract an expanded element, click to the left of the element name.\nAll Supports\nExpands the hierarchy to display all support zones and the supports within each zone.\nSupported Pipes\nExpands the hierarchy to display all supported pipe zones and the pipe supports within each zone.\nSupported HVAC\nExpands the hierarchy to display all supported HVAC zones and the HVAC supports within each zone.\nSupported TRAY\nExpands the hierarchy to display all supported cable tray zones and the cable tray supports within each zone.\nSupported Lighting\nExpands the hierarchy to display all supported lighting supports within each zone.\nUnsupported Elements\nExpands the hierarchy to display all unsupported pipe HVAC and cable tray zones and the unsupported elements within each zone.\nOrphaned Supports\nExpands the hierarchy to display all supports that are not associated with a pipe, HVAC duct or cable tray.\nAll Supports\nExpands the hierarchy to display all support zones and the supports within each zone.\nSupported Pipes\nExpands the hierarchy to display all supported pipe zones and the pipe supports within each zone.\nSupported HVAC\nExpands the hierarchy to display all supported HVAC zones and the HVAC supports within each zone.\nSupported TRAY\nExpands the hierarchy to display all supported cable tray zones and the cable tray supports within each zone.\nSupported Lighting\nExpands the hierarchy to display all supported lighting supports within each zone.\nUnsupported Elements\nExpands the hierarchy to display all unsupported pipe HVAC and cable tray zones and the unsupported elements within each zone.\nOrphaned Supports\nExpands the hierarchy to display all supports that are not associated with a pipe, HVAC duct or cable tray.\nTo run a health check, right-click a supported ZONE element to display a drop-down menu. Refer to Health Check for further information.\n\nTo modify a support, right-click a SUPPO element to display a drop-down menu.\n\nThe available menu options display.\nModify Support\nClick to display the Support Editor window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\nDelete Support\nClick to delete the support, a confirm window displays asking you to OK the deletion. Click Yes to delete the support.\nAdd Supported Elements\nClick to add the supported elements. For example, a supported pipe.\nAdd Supported Elements\nClick to display the Supports Wizard.\nThe functionality of the Supports Wizard window is explained. Refer to Supports Wizard for further information.\nZoom to\nClick to zoom to the support in the 3D view.\nModify Support\nClick to display the Support Editor window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\nDelete Support\nClick to delete the support, a confirm window displays asking you to OK the deletion. Click Yes to delete the support.\nAdd Supported Elements\nClick to add the supported elements. For example, a supported pipe.\nAdd Supported Elements\nClick to display the Supports Wizard.\nThe functionality of the Supports Wizard window is explained. Refer to Supports Wizard for further information.\nZoom to\nClick to zoom to the support in the 3D view.\n\nAll Supports\nExpands the hierarchy to display all support zones and the supports within each zone.\nSupported Pipes\nExpands the hierarchy to display all supported pipe zones and the pipe supports within each zone.\nSupported HVAC\nExpands the hierarchy to display all supported HVAC zones and the HVAC supports within each zone.\nSupported TRAY\nExpands the hierarchy to display all supported cable tray zones and the cable tray supports within each zone.\nSupported Lighting\nExpands the hierarchy to display all supported lighting supports within each zone.\nUnsupported Elements\nExpands the hierarchy to display all unsupported pipe HVAC and cable tray zones and the unsupported elements within each zone.\nOrphaned Supports\nExpands the hierarchy to display all supports that are not associated with a pipe, HVAC duct or cable tray.\nModify Support\nClick to display the Support Editor window.\nThe functionality of the Support Editor window is explained. Refer to Support Editor for further information.\nDelete Support\nClick to delete the support, a confirm window displays asking you to OK the deletion. Click Yes to delete the support.\nAdd Supported Elements\nClick to add the supported elements. For example, a supported pipe.\nAdd Supported Elements\nClick to display the Supports Wizard.\nThe functionality of the Supports Wizard window is explained. Refer to Supports Wizard for further information.\nZoom to\nClick to zoom to the support in the 3D view.\n\n\n\nHealth Check\nSupport Editor\nSupports Wizard\nAll Supports\nSupported Pipes\nSupported HVAC\nSupported TRAY\nSupported Lighting\nUnsupported Elements\nOrphaned Supports\nHealth Check\nModify Support\nSupport Editor\nSupport Editor\nSupport Editor\nDelete Support\nYes\nAdd Supported Elements\nAdd Supported Elements\nSupports Wizard\nSupports Wizard\nSupports Wizard\nZoom to"}
{"Headers": "Copy Support", "Content": "Copies a support.\nYou are prompted to Identify source support to copy or <ESC> to finish :\n\nClick to identify the support to copy using a cursor pick in the 3D view to display the Copy Support window.\nDistance\nInput a dimensional value in the field to define the distance between the copied supports.\nIf a distance is not entered, the support is copied a default distance of 300mm along the pipe.\nAlign with selected framework\nSelect the check box to align the copied support to the original support. The copied support is offset by the distance entered in the Distance field.\nDistance\nInput a dimensional value in the field to define the distance between the copied supports.\nIf a distance is not entered, the support is copied a default distance of 300mm along the pipe.\nAlign with selected framework\nSelect the check box to align the copied support to the original support. The copied support is offset by the distance entered in the Distance field.\nYou are prompted to Identify tube of pipe to add DATUM ancillary of the support or <ESC> to finish :\nClick to identify the pipe to associate with the copied support.\nYou can continue to click the pipe to copy additional supports. The Distance value can be modified between each copy.\nPress ESC to finish copying supports.\nBy default, the supports application defines the support name for the copied support. The support name can be modified. Refer to Support Editor for further information.\nDistance\nInput a dimensional value in the field to define the distance between the copied supports.\nIf a distance is not entered, the support is copied a default distance of 300mm along the pipe.\nAlign with selected framework\nSelect the check box to align the copied support to the original support. The copied support is offset by the distance entered in the Distance field.\nNote:\nThe prompt does not display if the support to be copied is already selected.\n\n\n\nSupport Editor\nIdentify source support to copy or <ESC> to finish :\nNote\n:\nDistance\nAlign with selected framework\nDistance\nIdentify tube of pipe to add DATUM ancillary of the support or <ESC> to finish :\nDistance\nESC\nSupport Editor"}
{"Headers": "Align Supports with Pipe", "Content": "Realigns supports that have become misaligned due to pipe modification.\nYou are prompted to Identify an element (ANCI, SUPPORT or BRAN) to realign or <ESC> to finish :\nClick to identify the ancillary, support or branch to realign using a cursor pick in the 3D view to display the Align Support window.\nIf an ancillary or support is selected, the selected ancillary or support is realigned.\nIf a branch is selected, then all supports on the selected branch are realigned.\n\nBy default, the supports are realigned to the centreline of the pipe.\nSupport\nThe support name displays in the field.\nAncillary\nThe ancillary name displays in the field.\nOffline\nCurrently all supports are set to FALSE indicating a status of not offline.\nResult\nIf a support is successfully aligned to the centreline of the pipe, Aligned displays in the column.\nIf a support is already aligned to the centreline of the pipe or has an offline status of TRUE, Skipped displays in the column and the position of the support is not modified.\nIf a support contains an invalid reference to the pipe, a confirm window displays asking you to identify an element to support.\nClick Yes to associate the support with a pipe using a cursor pick in the 3D View.\nYou are prompted to Identify en element to support or <ESC> to finish :\nThe support is aligned on the leave tube of the selected element.\nSupport\nThe support name displays in the field.\nAncillary\nThe ancillary name displays in the field.\nOffline\nCurrently all supports are set to FALSE indicating a status of not offline.\nResult\nIf a support is successfully aligned to the centreline of the pipe, Aligned displays in the column.\nIf a support is already aligned to the centreline of the pipe or has an offline status of TRUE, Skipped displays in the column and the position of the support is not modified.\nIf a support contains an invalid reference to the pipe, a confirm window displays asking you to identify an element to support.\n\nClick Yes to associate the support with a pipe using a cursor pick in the 3D View.\nYou are prompted to Identify en element to support or <ESC> to finish :\nThe support is aligned on the leave tube of the selected element.\nRight-click a support to display the drop-down menu.\n\nClear All\nClick to remove all supports from the Align Support window.\nNavigate on Selection\nClick to navigate to the currently selected support in the Model Explorer.\nCentre on Selection\nClick to centre the currently selected support in the 3D View.\nExport to Excel\nAllows you to export the support list to an Excel file. Click to display the Save to Excel window. You can navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the support list in the Print Preview window.\nClear All\nClick to remove all supports from the Align Support window.\nNavigate on Selection\nClick to navigate to the currently selected support in the Model Explorer.\nCentre on Selection\nClick to centre the currently selected support in the 3D View.\nExport to Excel\nAllows you to export the support list to an Excel file. Click to display the Save to Excel window. You can navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the support list in the Print Preview window.\n\nSupport\nThe support name displays in the field.\nAncillary\nThe ancillary name displays in the field.\nOffline\nCurrently all supports are set to FALSE indicating a status of not offline.\nResult\nIf a support is successfully aligned to the centreline of the pipe, Aligned displays in the column.\nIf a support is already aligned to the centreline of the pipe or has an offline status of TRUE, Skipped displays in the column and the position of the support is not modified.\nIf a support contains an invalid reference to the pipe, a confirm window displays asking you to identify an element to support.\nClick Yes to associate the support with a pipe using a cursor pick in the 3D View.\nYou are prompted to Identify en element to support or <ESC> to finish :\nThe support is aligned on the leave tube of the selected element.\nClear All\nClick to remove all supports from the Align Support window.\nNavigate on Selection\nClick to navigate to the currently selected support in the Model Explorer.\nCentre on Selection\nClick to centre the currently selected support in the 3D View.\nExport to Excel\nAllows you to export the support list to an Excel file. Click to display the Save to Excel window. You can navigate to a location and name the exported Excel file.\nPrint Preview\nClick to display the support list in the Print Preview window.\nNote:\nThe prompt does not display if the ancillary, support or branch to be aligned is already selected.\n\n\n\nIdentify an element (ANCI, SUPPORT or BRAN) to realign or <ESC> to finish :\nNote\n:\nAlign Support\nSupport\nAncillary\nOffline\nResult\nAligned\nSkipped\nYes\nIdentify en element to support or <ESC> to finish :\nClear All\nAlign Support\nNavigate on Selection\nCentre on Selection\nExport to Excel\nSave to Excel\nPrint Preview\nPrint Preview"}
{"Headers": "Reinforcing Pad", "Content": "Associates reinforcing pads with support structural members. The reinforcing pad is positioned at the end of a support structural member. Once positioned, the size, plate thickness and corner radius of the reinforcing pad can be modified.\n\n\n"}
{"Headers": "Create Reinforcing Pad", "Content": "Creates a reinforcing pad at the end of a support structural member.\nYou are prompted to Identify the end of section to add the pad to :\nClick to identify the end of the support structural member to be associated with the reinforcing pad using a cursor pick in the 3D view.\nThe reinforcing pad is created and displays in the 3D view.\n\nThe new PNOD and PJOI elements are added to the owning FRMW and display in the Model Explorer.\n\n\n\n\nIdentify the end of section to add the pad to :"}
{"Headers": "Modify Reinforcing Pad", "Content": "Modifies the size, plate thickness or corner radius of a reinforcing pad.\nYou are prompted to Pick the section end where the pad is connected to :\nClick to identify the end of the support structural member associated with the reinforcing Pad using a cursor pick in the 3D view to display the Modify Pad window.\n\nThe reinforcing pad name displays at the top of the Modify Pad window.\nSize\nInput a dimensional value in the field to modify the size of the reinforcing pad.\nPlate Thickness\nInput a dimensional value in the field to modify the plate thickness of the reinforcing pad.\nCorner Radius\nInput a dimensional value in the field to modify the corner radius of all the reinforcing pad corners.\nSize\nInput a dimensional value in the field to modify the size of the reinforcing pad.\nPlate Thickness\nInput a dimensional value in the field to modify the plate thickness of the reinforcing pad.\nCorner Radius\nInput a dimensional value in the field to modify the corner radius of all the reinforcing pad corners.\nClick Apply to modify the reinforcing pad or Cancel to discard any changes and close the Modify Pad window.\nSize\nInput a dimensional value in the field to modify the size of the reinforcing pad.\nPlate Thickness\nInput a dimensional value in the field to modify the plate thickness of the reinforcing pad.\nCorner Radius\nInput a dimensional value in the field to modify the corner radius of all the reinforcing pad corners.\n\n\n\nPick the section end where the pad is connected to :\nModify Pad\nModify Pad\nSize\nPlate Thickness\nCorner Radius\nApply\nCancel\nModify Pad"}
{"Headers": "Delete Reinforcing Pad", "Content": "Deletes a reinforcing pad.\nYou are prompted to Pick the section end where the pad is connected to :\nClick to identify the end of the support structural member associated with the reinforcing pad using a cursor pick in the 3D view.\nA confirm window displays asking you to OK the deletion. Click Yes to delete the item.\nIf the support structural member is associated with more than one reinforcing pad, an error message displays summarizing the problem.\n\nNote:\nThe prompt does not display if the support structural member associated with the reinforcing pad is already selected.\n\n\n\nPick the section end where the pad is connected to :\nNote\n:\nYes"}
{"Headers": "Lock/Unlock Support", "Content": "Locks or unlocks a support for modification. When a support is locked it cannot be modified or deleted.\nThe following conditions must be met to enable the lock functionality:\nThe support must not be currently claimed by another user\nThe support must not be located in a read only database\nA successful DAC check can be carried out on the support\nThe support must not be currently claimed by another user\nThe support must not be currently claimed by another user\nThe support must not be located in a read only database\nThe support must not be located in a read only database\nA successful DAC check can be carried out on the support\nA successful DAC check can be carried out on the support\n\n\n"}
{"Headers": "Lock Support", "Content": "You are prompted to Pick Support or <ESC> to finish:\nClick to identify the support(s) to be locked using a cursor pick in the 3D view.\nPress ESC to lock the selected support(s).\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nPick Support or <ESC> to finish:\nNote\n:\nESC"}
{"Headers": "Drawing Comment", "Content": "Creates, modifies and removes a drawing comment associated with a support.\nYou are prompted to Identify Support to modify the drawing comment :\nClick to identify the support using a cursor pick in the 3D view to display the Modify Drawing Comment window.\n\nCE\nClick to select the existing support as the current element. Alternatively you can input the support name in the field.\nIdentify by Cursor\nClick to identify the support using a cursor pick in the 3D view.\nYou are prompted to Identify support to modify the drawing comment :\nComment\nInput, modify or delete the data in the field.\nCE\nClick to select the existing support as the current element. Alternatively you can input the support name in the field.\nIdentify by Cursor\nClick to identify the support using a cursor pick in the 3D view.\nYou are prompted to Identify support to modify the drawing comment :\nComment\nInput, modify or delete the data in the field.\nClick Apply to modify the drawing comment or Cancel to discard any changes and close the Modify Drawing Comment window.\nCE\nClick to select the existing support as the current element. Alternatively you can input the support name in the field.\nIdentify by Cursor\nClick to identify the support using a cursor pick in the 3D view.\nYou are prompted to Identify support to modify the drawing comment :\nComment\nInput, modify or delete the data in the field.\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nIdentify Support to modify the drawing comment :\nNote\n:\nModify Drawing Comment\nCE\nIdentify by Cursor\nIdentify support to modify the drawing comment :\nComment\nApply\nCancel\nModify Drawing Comment"}
{"Headers": "Isometric Control", "Content": "Controls the isometric drawing representation and material list settings for supports and their associated ancillaries.\nYou are prompted to Pick Support :\nClick to identify the support using a cursor pick in the 3D view to display the Isometric Material List Control window.\n\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nAncillaries\nThe column is populated with a list of ancillaries for the currently selected support.\nMaterial\nSelect from the drop down list to modify the isometric drawing representation for the currently selected ancillary.\nSelect ON to include the ancillary on the isometric material list.\nSelect OFF to exclude the ancillary from the isometric material list.\nSelect Dotted with Dims to include the ancillary on the isometric drawing representation and display as dotted with dimensions.\nSelect Dotted without Dims to include the ancillary on the isometric drawing representation and display as dotted without dimensions.\nSupport Tag\nSelect from the drop down list to modify the isometric drawing representation for the currently selected ancillary.\nSelect ON to include support tags on the isometric drawing representation.\nSelect OFF to exclude support tags from the isometric drawing representation.\nSet Material to\nSelect from the drop down list to modify the Material Column for all ancillaries in the list.\nYou can select from:\nReset\nON\nOFF\nDotted with Dims\nDotted without Dims\nSelect Reset to return the Material column to the settings prior to modification.\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nAncillaries\nThe column is populated with a list of ancillaries for the currently selected support.\nMaterial\nSelect from the drop down list to modify the isometric drawing representation for the currently selected ancillary.\nSelect ON to include the ancillary on the isometric material list.\nSelect OFF to exclude the ancillary from the isometric material list.\nSelect Dotted with Dims to include the ancillary on the isometric drawing representation and display as dotted with dimensions.\nSelect Dotted without Dims to include the ancillary on the isometric drawing representation and display as dotted without dimensions.\nSupport Tag\nSelect from the drop down list to modify the isometric drawing representation for the currently selected ancillary.\nSelect ON to include support tags on the isometric drawing representation.\nSelect OFF to exclude support tags from the isometric drawing representation.\nSet Material to\nSelect from the drop down list to modify the Material Column for all ancillaries in the list.\nYou can select from:\nSelect Reset to return the Material column to the settings prior to modification.\nClick Apply to accept the isometric drawing representation and material list settings or Cancel to discard any changes and close the Isometric Material List Control window.\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nAncillaries\nThe column is populated with a list of ancillaries for the currently selected support.\nMaterial\nSelect from the drop down list to modify the isometric drawing representation for the currently selected ancillary.\nSelect ON to include the ancillary on the isometric material list.\nSelect OFF to exclude the ancillary from the isometric material list.\nSelect Dotted with Dims to include the ancillary on the isometric drawing representation and display as dotted with dimensions.\nSelect Dotted without Dims to include the ancillary on the isometric drawing representation and display as dotted without dimensions.\nSupport Tag\nSelect from the drop down list to modify the isometric drawing representation for the currently selected ancillary.\nSelect ON to include support tags on the isometric drawing representation.\nSelect OFF to exclude support tags from the isometric drawing representation.\nSet Material to\nSelect from the drop down list to modify the Material Column for all ancillaries in the list.\nYou can select from:\nReset\nON\nOFF\nDotted with Dims\nDotted without Dims\nSelect Reset to return the Material column to the settings prior to modification.\nReset\nON\nOFF\nDotted with Dims\nDotted without Dims\nReset\nReset\nON\nON\nOFF\nOFF\nDotted with Dims\nDotted with Dims\nDotted without Dims\nDotted without Dims\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nPick Support :\nNote\n:\nIsometric Material List Control\nCE\nIdentify By Cursor\nPick Support :\nSelect Support\nAncillaries\nMaterial\nON\nOFF\nDotted with Dims\nDotted without Dims\nSupport Tag\nON\nOFF\nSet Material to\nMaterial\nReset\nON\nOFF\nDotted with Dims\nDotted without Dims\nReset\nMaterial\nApply\nCancel"}
{"Headers": "Drawing Note", "Content": "Creates, modifies and removes notes for the drawing deliverable. By default, the origin of the selected member is used as the note position.\nYou are prompted to Pick Support :\nClick to identify the support using a cursor pick in the 3D view to display the Notes window.\n\nThe support name displays at the top of the Notes window.\nCE\nClick to select the existing as the Current Element.\nThe selected Name in the field.\nIdentify By Cursor\nClick to identify the element to associate with the note using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Support field is populated with the name of the identified support.\nMembers\nSelect a member to associate with the note from the list of available members.\nApply Note\nClick to associate the note with the selected support member.\nRemove Note\nClick to remove the associated note from the selected support member.\nModify Note Position\nAllows you to define the note position. Refer to Modify Note Position for further information.\nCE\nClick to select the existing as the Current Element.\nThe selected Name in the field.\nIdentify By Cursor\nClick to identify the element to associate with the note using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Support field is populated with the name of the identified support.\nMembers\nSelect a member to associate with the note from the list of available members.\nApply Note\nClick to associate the note with the selected support member.\nRemove Note\nClick to remove the associated note from the selected support member.\nModify Note Position\nAllows you to define the note position. Refer to Modify Note Position for further information.\nClick Cancel to close the Notes window.\nCE\nClick to select the existing as the Current Element.\nThe selected Name in the field.\nIdentify By Cursor\nClick to identify the element to associate with the note using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Support field is populated with the name of the identified support.\nMembers\nSelect a member to associate with the note from the list of available members.\nApply Note\nClick to associate the note with the selected support member.\nRemove Note\nClick to remove the associated note from the selected support member.\nModify Note Position\nAllows you to define the note position. Refer to Modify Note Position for further information.\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nModify Note Position\nPick Support :\nNote\n:\nNotes\nNotes\nCE\nIdentify By Cursor\nPick Support :\nSupport\nMembers\nApply Note\nRemove Note\nModify Note Position\nModify Note Position\nCancel\nNotes"}
{"Headers": "Modify Note Position", "Content": "The Modify Note Position window allows you to define the position of the Note on the drawing deliverable.The selection also displays the Positioning Control window. Refer to Positioning Control for further information.\nYou are prompted to Modify Position (Distance[0]) Snap :\n\nThe support name displays at the top of the Note Position window.\nPosition\nYou can pick a note position using a cursor pick in the 3D view.\nAlternatively, select the position axis from the Position drop-down lists, choose from East/West, North/South and Up/Down. You can then input the explicit position values in the Position fields.\nLock\nSelect the check boxes to lock the explicit position of the note.\nwrt\nInput the name of the element to which all co-ordinates are interpreted with respect to. The default wrt is world.\nPosition\nYou can pick a note position using a cursor pick in the 3D view.\nAlternatively, select the position axis from the Position drop-down lists, choose from East/West, North/South and Up/Down. You can then input the explicit position values in the Position fields.\nLock\nSelect the check boxes to lock the explicit position of the note.\nwrt\nInput the name of the element to which all co-ordinates are interpreted with respect to. The default wrt is world.\nClick Apply to modify the note position or Cancel to discard any changes and close the Note Position window.\nPosition\nYou can pick a note position using a cursor pick in the 3D view.\nAlternatively, select the position axis from the Position drop-down lists, choose from East/West, North/South and Up/Down. You can then input the explicit position values in the Position fields.\nLock\nSelect the check boxes to lock the explicit position of the note.\nwrt\nInput the name of the element to which all co-ordinates are interpreted with respect to. The default wrt is world.\n\n\n\nPositioning Control\nModify Note Position\nPositioning Control\nPositioning Control\nModify Position (Distance[0]) Snap :\nNote Position\nPosition\nPosition\nEast/West\nNorth/South\nUp/Down\nPosition\nLock\nwrt\nApply\nCancel\nNote Position"}
{"Headers": "Special Frame Direction", "Content": "Sets the frame view direction on special supports for use in drawing production.\nSpecial support frameworks created in the Supports application have their frame direction set automatically and this is used to define the main view direction in automated drawing production. The Special Frame Direction window provides more specific control of this, and allows you to set a view direction on structures added manually to special supports.\n\nCE\nClick to select the existing special support as the current element.\nThe support name displays in the field.\nNote:\nThe field is populated if the special support is already selected.\nIdentify By Cursor\nClick to identify a special support using a cursor pick in the 3D view.\nYou are prompted to Pick Special Support Structure :\nThe CE field is populated with the name of the identified special support.\nFrame View Direction\nInput a value in the field to define the frame view direction. For example, input W WRT /* to define a West direction with respect to the World element.\nCE\nClick to select the existing special support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a special support using a cursor pick in the 3D view.\nYou are prompted to Pick Special Support Structure :\nThe CE field is populated with the name of the identified special support.\nFrame View Direction\nInput a value in the field to define the frame view direction. For example, input W WRT /* to define a West direction with respect to the World element.\nClick Apply to set the special support frame view direction or Cancel to discard any inputs and close the Special Frame Direction window.\nCE\nClick to select the existing special support as the current element.\nThe support name displays in the field.\nNote:\nThe field is populated if the special support is already selected.\nIdentify By Cursor\nClick to identify a special support using a cursor pick in the 3D view.\nYou are prompted to Pick Special Support Structure :\nThe CE field is populated with the name of the identified special support.\nFrame View Direction\nInput a value in the field to define the frame view direction. For example, input W WRT /* to define a West direction with respect to the World element.\nNote:\nThe field is populated if the special support is already selected.\nNote:\nThe setting can be used in conjunction with View Direction, available on the Support Editor window, which sets the view direction to be opposite. The Supports Drawing application automatically changes a stored frame direction of West, South or Down to East, North or Up respectively. This can be overridden using View Direction to force the main view to be West, South or Down. Refer to View for further information.\n\n\n\nView\nSpecial Frame Direction\nCE\nNote\n:\nIdentify By Cursor\nPick Special Support Structure :\nCE\nFrame View Direction\nW WRT /*\nApply\nCancel\nSpecial Frame Direction\nNote\n:\nView Direction\nSupport Editor\nView Direction\nView"}
{"Headers": "Set Ancillary Material", "Content": "Sets the support ancillary material.\nYou are prompted to Pick Support :\nClick to identify the support using a cursor pick in the 3D view to display the Set Ancillary Material window.\n\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nAncillaries\nThe column is populated with a list of ancillaries for the currently selected support.\nAncillary Code\nThe column is populated with the ancillary Code for each item in the list.\nAncillary Type\nThe column is populated with the ancillary type for each item in the list.\nMaterial\nSelect from the drop-down list to modify the material for an individual ancillary element.\nSet material of all general type ancillaries to:\nSelect from the drop down list to modify the material used for all General ancillaries in the Ancillary Type column.\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nAncillaries\nThe column is populated with a list of ancillaries for the currently selected support.\nAncillary Code\nThe column is populated with the ancillary Code for each item in the list.\nAncillary Type\nThe column is populated with the ancillary type for each item in the list.\nMaterial\nSelect from the drop-down list to modify the material for an individual ancillary element.\nSet material of all general type ancillaries to:\nSelect from the drop down list to modify the material used for all General ancillaries in the Ancillary Type column.\nClick Reset to revert to the values when changes were last applied or when the when the Set Ancillary Material window was opened.\nClick Apply to modify the ancillary materials or Cancel to discard any changes and close the Set Ancillary Material window.\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nAncillaries\nThe column is populated with a list of ancillaries for the currently selected support.\nAncillary Code\nThe column is populated with the ancillary Code for each item in the list.\nAncillary Type\nThe column is populated with the ancillary type for each item in the list.\nMaterial\nSelect from the drop-down list to modify the material for an individual ancillary element.\nSet material of all general type ancillaries to:\nSelect from the drop down list to modify the material used for all General ancillaries in the Ancillary Type column.\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nPick Support :\nNote\n:\n\nCE\nIdentify By Cursor\nPick Support :\nSelect Support\nAncillaries\nAncillary Code\nAncillary Type\nMaterial\nSet material of all general type ancillaries to:\nGeneral\nAncillary Type\nReset\nApply\nCancel"}
{"Headers": "Set Structural Material", "Content": "Sets the material for sections, joints, plates, boxes or primitives.\nYou are prompted to Pick Support :\nClick to identify the support using a cursor pick in the 3D view to display the Set Gensec/Joint/Plate Material window.\n\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nStructures\nThe column is populated with a list of structures for the currently selected support.\nStructure Type\nThe column is populated with the structure type for each item in the list.\nMaterial\nSelect from the drop-down list to modify the material used for an individual structural element.\nSet material of all structures to:\nSelect from the drop down list to modify the material used for all structural elements in the Structures column.\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nStructures\nThe column is populated with a list of structures for the currently selected support.\nStructure Type\nThe column is populated with the structure type for each item in the list.\nMaterial\nSelect from the drop-down list to modify the material used for an individual structural element.\nSet material of all structures to:\nSelect from the drop down list to modify the material used for all structural elements in the Structures column.\nClick Reset to revert to the values when changes were last applied or when the Set Gensec/Joint/Plate Material window was opened.\nClick Apply to modify the structural materials or Cancel to discard any changes and close the Set Gensec/Joint/Plate Material window.\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nStructures\nThe column is populated with a list of structures for the currently selected support.\nStructure Type\nThe column is populated with the structure type for each item in the list.\nMaterial\nSelect from the drop-down list to modify the material used for an individual structural element.\nSet material of all structures to:\nSelect from the drop down list to modify the material used for all structural elements in the Structures column.\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nPick Support :\nNote\n:\n\nCE\nIdentify By Cursor\nPick Support :\nSelect Support\nStructures\nStructure Type\nMaterial\nSet material of all structures to:\nStructures\nReset\nApply\nCancel"}
{"Headers": "Bed/Anchor Plate Reference", "Content": "References a support steelwork member to a bedplate or an anchor.\nYou are prompted to Pick Support :\nThe prompt does not display if the support is already selected.\nClick to identify the support using a cursor pick in the 3D view to display the Bed/Anchor Plate References window.\n\nThe framework support name displays at the top of the Bed/Anchor Plate References window.\nSet Reference\nClick to reference a bedplate or an anchor using a cursor pick in the 3D view.\nYou are prompted to Identify base/anchor plate to reference\nThe reference displays in the list of available references.\nClear Reference\nClick Clear Reference to remove the currently selected reference from the list of available references.\nSet Reference\nClick to reference a bedplate or an anchor using a cursor pick in the 3D view.\nYou are prompted to Identify base/anchor plate to reference\nThe reference displays in the list of available references.\nClear Reference\nClick Clear Reference to remove the currently selected reference from the list of available references.\nClick Cancel to close the Bed/Anchor Plate References window.\nSet Reference\nClick to reference a bedplate or an anchor using a cursor pick in the 3D view.\nYou are prompted to Identify base/anchor plate to reference\nThe reference displays in the list of available references.\nClear Reference\nClick Clear Reference to remove the currently selected reference from the list of available references.\n\n\n\nPick Support :\nBed/Anchor Plate References\nBed/Anchor Plate References\nSet Reference\nIdentify base/anchor plate to reference\nClear Reference\nClear Reference\nCancel"}
{"Headers": "Add Snipes to Steelwork Members", "Content": "Creates and modifies snipes on support structural members. A snipe is a cut angle on the support structural member, such that a corner is removed.\n\nThis feature currently only works with angular support structural members. For example, steelwork profiles of type GENSEC and gtype ANG. Two cases are catered for:\nSnipe on end of leg attached to stiffener\nSnipe on free end of support structural member.\nSnipe on end of leg attached to stiffener\nSnipe on end of leg attached to stiffener\nSnipe on free end of support structural member.\nSnipe on free end of support structural member.\n\n\n"}
{"Headers": "Snipe on End of Leg Attached to Stiffener", "Content": "When the support structural member is attached to a stiffener the following calculations are used, where\nSL =\nSnipe length on the leg of the framework\nFL =\nLength of leg\nM1 =\nControl gap for back-to-back. The default is 10 mm.\nM2 =\nLength in the opposite direction of M1 on flange of stiffener\nM3 =\nDistance between flange top outside edge of stiffener and leg point connected with the flange top of stiffener (default = 25 mm)\nWhen L > M1 + FL + M2 and M2 >= 25mm, Snip is not provided on support leg as below.\nWhen L > M1 + FL + M2 and M2 < 25mm Snip is to be provided on support leg as below\nWhen L =< M1 + FL and M2 (=M1 + FL - L) =< 0 (zero) mm Snip is to be provided on support leg as below\nSL =\nSnipe length on the leg of the framework\nFL =\nLength of leg\nM1 =\nControl gap for back-to-back. The default is 10 mm.\nM2 =\nLength in the opposite direction of M1 on flange of stiffener\nM3 =\nDistance between flange top outside edge of stiffener and leg point connected with the flange top of stiffener (default = 25 mm)\nWhen L > M1 + FL + M2 and M2 >= 25mm, Snip is not provided on support leg as below.\n\nWhen L > M1 + FL + M2 and M2 < 25mm Snip is to be provided on support leg as below\n\nWhen L =< M1 + FL and M2 (=M1 + FL - L) =< 0 (zero) mm Snip is to be provided on support leg as below\n\n\nSL =\nSnipe length on the leg of the framework\nFL =\nLength of leg\nM1 =\nControl gap for back-to-back. The default is 10 mm.\nM2 =\nLength in the opposite direction of M1 on flange of stiffener\nM3 =\nDistance between flange top outside edge of stiffener and leg point connected with the flange top of stiffener (default = 25 mm)\nWhen L > M1 + FL + M2 and M2 >= 25mm, Snip is not provided on support leg as below.\nWhen L > M1 + FL + M2 and M2 < 25mm Snip is to be provided on support leg as below\nWhen L =< M1 + FL and M2 (=M1 + FL - L) =< 0 (zero) mm Snip is to be provided on support leg as below\n\n\n"}
{"Headers": "Snipe on Free End of Support Structural Member", "Content": "When the support structural member is not attached to a stiffener the following calculation is used:\n\n\n\n"}
{"Headers": "Applicable Templates", "Content": "The snipes described in Snipe on Free End of Support Structural Member have been added to angle support structural members of all templates in databases MDS/DESITMPL-DIN and MDS/DESITMPL-DIN-ORI. The list of modified templates is as follows:\nXFT03\nXFT11\nXFT34A\nXFT04\nXFT18\nXFT34B\nXFT05\nXFT19\nXFT36\nXFT06\nXFT21\nXFT37\nXFT07\nXFT29\nXFT38\nXFT08\nXFT31\nXFT39\nXFT09\nXFT32\nXFT40\nXFT10\nXFT33\nXFT42\nXFT03\nXFT11\nXFT34A\nXFT04\nXFT18\nXFT34B\nXFT05\nXFT19\nXFT36\nXFT06\nXFT21\nXFT37\nXFT07\nXFT29\nXFT38\nXFT08\nXFT31\nXFT39\nXFT09\nXFT32\nXFT40\nXFT10\nXFT33\nXFT42\n\nXFT03\nXFT11\nXFT34A\nXFT04\nXFT18\nXFT34B\nXFT05\nXFT19\nXFT36\nXFT06\nXFT21\nXFT37\nXFT07\nXFT29\nXFT38\nXFT08\nXFT31\nXFT39\nXFT09\nXFT32\nXFT40\nXFT10\nXFT33\nXFT42\n\n\n\nSnipe on Free End of Support Structural Member\nSnipe on Free End of Support Structural Member"}
{"Headers": "Create Snipes", "Content": "Snipes can be created automatically when a support framework is created or modified, they can also be created manually.\n\n\n"}
{"Headers": "Automatically Create Snipes", "Content": "If the support leg is attached to a stiffener and the configuration conforms to the conditions described in Snipe on End of Leg Attached to Stiffener, snipes are automatically created when a support framework is created or modified (using the support framework window).\nThe snipe size is automatically calculated as follows:\nIf the support leg is already connected by a joint to the stiffener, then the snipe is not created, whereas the connection by joint is not allowed by the application if the snipe already exists.\nSnipes created in this way can be modified or deleted. Refer to Manually Create Snipes for further information.\nWhen the calculated size is less than the minimum allowable, the snipe is not created. The minimum snipe is set at 10mm and cannot be changed.\nIf the calculated size is greater than the maximum allowable, then the maximum size is used instead. The maximum size depends on the angle size and is calculated as the difference between the size of the angle leg where the snipe is intended/created and the thickness of the angle leg.\nWhen the calculated size is less than the minimum allowable, the snipe is not created. The minimum snipe is set at 10mm and cannot be changed.\nWhen the calculated size is less than the minimum allowable, the snipe is not created. The minimum snipe is set at 10mm and cannot be changed.\nIf the calculated size is greater than the maximum allowable, then the maximum size is used instead. The maximum size depends on the angle size and is calculated as the difference between the size of the angle leg where the snipe is intended/created and the thickness of the angle leg.\nIf the calculated size is greater than the maximum allowable, then the maximum size is used instead. The maximum size depends on the angle size and is calculated as the difference between the size of the angle leg where the snipe is intended/created and the thickness of the angle leg.\n\n\n\nSnipe on End of Leg Attached to Stiffener\nManually Create Snipes\nSnipe on End of Leg Attached to Stiffener\nManually Create Snipes"}
{"Headers": "Manually Create Snipes", "Content": "Manually creates a support framework snipe.\nYou are prompted to Pick Section :\nClick to identify the support structural member using a cursor pick in the 3D view to display the Snipes window.\n\nThe Snipes window allows you to create, modify, delete, position and size snipes.\nCE\nClick to select the existing support structural member as the current element. Alternatively you can input a name in the field.\nPick section end\nClick to identify the end of the support structural member to be associated with the Snipe using a cursor pick in the 3D view.\nYou are prompted Pick SNIPE edge or leg of end of angle where you want it to be created:\nThe 3D view indicates the position of the Snipe and that it has not been created. Click Apply to create the Snipe.\nEnable disable/automatic creation of snipes\nClick Auto to identify the end of the support structural member to be associated with the snipe using a cursor pick in the 3D view.\nYou are prompted Pick SNIPE edge or leg of end of angle where you want it to be created:\nThe 3D view indicates the position of the snipe and that it has been created.\nYou can continue to identify additional support structural member ends to be associated with Snipes.\nClick Auto again to disable the functionality.\nSelect Sniped End\nSelect the Start option button to associate the start of the currently selected support structural member with the Snipe.\nSelect the End option button to associate the end of the currently selected support structural member with the Snipe.\nSelect Angle Leg\nSelect the Top option button to associate the top of the currently selected support structural member with the Snipe.\nSelect the Left option button to associate the top of the currently selected support structural member with the Snipe.\nSnipe Length\nInput a dimensional value in the field to define the snipe length.\nThe Supports application checks the entered values. If a value is less than the minimum (fixed at 10mm) then it is reset to the minimum size. If it is greater than the maximum, it is reset to the maximum size. The maximum size depends on the angle size and is calculated using the difference between the size of the angle leg where the snipe is intended/created and the thickness of the angle leg.\nSnipe Height\nInput a dimensional value in the field to define the snipe height.\nThe Supports application checks the entered values. If a value is less than the minimum (fixed at 10mm) then it is reset to the minimum size. If it is greater than the maximum, it is reset to the maximum size. The maximum size depends on the angle size and is calculated using the difference between the size of the angle leg where the snipe is intended/created and the thickness of the angle leg.\nLock\nClick Lock to lock the values of the Snipe Length and Snipe Height fields. If you input a value into one of the fields, the other field is populated with the same value, by default\nClick Lock again to disable the functionality.\nApply to All\nSelect the check box to create snipes on all available surfaces of the support structural member. The number of snipes to be created is indicated adjacent to the check box.\n\nCE\nClick to select the existing support structural member as the current element. Alternatively you can input a name in the field.\n\nPick section end\nClick to identify the end of the support structural member to be associated with the Snipe using a cursor pick in the 3D view.\nYou are prompted Pick SNIPE edge or leg of end of angle where you want it to be created:\nThe 3D view indicates the position of the Snipe and that it has not been created. Click Apply to create the Snipe.\n\n\nEnable disable/automatic creation of snipes\nClick Auto to identify the end of the support structural member to be associated with the snipe using a cursor pick in the 3D view.\nYou are prompted Pick SNIPE edge or leg of end of angle where you want it to be created:\nThe 3D view indicates the position of the snipe and that it has been created.\n\nYou can continue to identify additional support structural member ends to be associated with Snipes.\nClick Auto again to disable the functionality.\n\nSelect Sniped End\nSelect the Start option button to associate the start of the currently selected support structural member with the Snipe.\nSelect the End option button to associate the end of the currently selected support structural member with the Snipe.\n\nSelect Angle Leg\nSelect the Top option button to associate the top of the currently selected support structural member with the Snipe.\nSelect the Left option button to associate the top of the currently selected support structural member with the Snipe.\n\nSnipe Length\nInput a dimensional value in the field to define the snipe length.\nThe Supports application checks the entered values. If a value is less than the minimum (fixed at 10mm) then it is reset to the minimum size. If it is greater than the maximum, it is reset to the maximum size. The maximum size depends on the angle size and is calculated using the difference between the size of the angle leg where the snipe is intended/created and the thickness of the angle leg.\n\nSnipe Height\nInput a dimensional value in the field to define the snipe height.\nThe Supports application checks the entered values. If a value is less than the minimum (fixed at 10mm) then it is reset to the minimum size. If it is greater than the maximum, it is reset to the maximum size. The maximum size depends on the angle size and is calculated using the difference between the size of the angle leg where the snipe is intended/created and the thickness of the angle leg.\n\nLock\nClick Lock to lock the values of the Snipe Length and Snipe Height fields. If you input a value into one of the fields, the other field is populated with the same value, by default\nClick Lock again to disable the functionality.\n\nApply to All\nSelect the check box to create snipes on all available surfaces of the support structural member. The number of snipes to be created is indicated adjacent to the check box.\nClick Create to create a snipe.\nClick Modify to modify an existing snipe.\nClick Delete to delete an existing snipe.\nClick Cancel to discard any changes and close the Snipes window.\n\nThe new JLDATU, PLDATU and FIXING elements are added to the owning GENSEC and display in the Model Explorer.\n\nCE\nClick to select the existing support structural member as the current element. Alternatively you can input a name in the field.\nPick section end\nClick to identify the end of the support structural member to be associated with the Snipe using a cursor pick in the 3D view.\nYou are prompted Pick SNIPE edge or leg of end of angle where you want it to be created:\nThe 3D view indicates the position of the Snipe and that it has not been created. Click Apply to create the Snipe.\nEnable disable/automatic creation of snipes\nClick Auto to identify the end of the support structural member to be associated with the snipe using a cursor pick in the 3D view.\nYou are prompted Pick SNIPE edge or leg of end of angle where you want it to be created:\nThe 3D view indicates the position of the snipe and that it has been created.\nYou can continue to identify additional support structural member ends to be associated with Snipes.\nClick Auto again to disable the functionality.\nSelect Sniped End\nSelect the Start option button to associate the start of the currently selected support structural member with the Snipe.\nSelect the End option button to associate the end of the currently selected support structural member with the Snipe.\nSelect Angle Leg\nSelect the Top option button to associate the top of the currently selected support structural member with the Snipe.\nSelect the Left option button to associate the top of the currently selected support structural member with the Snipe.\nSnipe Length\nInput a dimensional value in the field to define the snipe length.\nThe Supports application checks the entered values. If a value is less than the minimum (fixed at 10mm) then it is reset to the minimum size. If it is greater than the maximum, it is reset to the maximum size. The maximum size depends on the angle size and is calculated using the difference between the size of the angle leg where the snipe is intended/created and the thickness of the angle leg.\nSnipe Height\nInput a dimensional value in the field to define the snipe height.\nThe Supports application checks the entered values. If a value is less than the minimum (fixed at 10mm) then it is reset to the minimum size. If it is greater than the maximum, it is reset to the maximum size. The maximum size depends on the angle size and is calculated using the difference between the size of the angle leg where the snipe is intended/created and the thickness of the angle leg.\nLock\nClick Lock to lock the values of the Snipe Length and Snipe Height fields. If you input a value into one of the fields, the other field is populated with the same value, by default\nClick Lock again to disable the functionality.\nApply to All\nSelect the check box to create snipes on all available surfaces of the support structural member. The number of snipes to be created is indicated adjacent to the check box.\nNote:\nThe prompt does not display if the support structural member is already selected.\n\n\n\nPick Section :\nNote\n:\nSnipes\nSnipes\nCE\nPick section end\nPick SNIPE edge or leg of end of angle where you want it to be created:\nApply\nEnable disable/automatic creation of snipes\nAuto\nPick SNIPE edge or leg of end of angle where you want it to be created:\nAuto\nSelect Sniped End\nStart\nEnd\nSelect Angle Leg\nTop\nLeft\nSnipe Length\nSnipe Height\nLock\nLock\nSnipe Length\nSnipe Height\nLock\nApply to All\nCreate\nModify\nDelete\nCancel\nSnipes"}
{"Headers": "Spooling", "Content": "Creates spools for the steelwork erection procedure. The framework design is split into logical sections (spools) ready for fabrication.The ADP drawing displays which spool the steelwork section belongs to in the material list.\nYou are prompted to Pick Support :\nClick to identify the support using a cursor pick in the 3D view to display the Framework Spooling window.\n\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nSpool\nSelect a spool from the drop-down list.\nMembers\nThe list of available members displays the content of the currently selected spool.\nNew\nClick to create a new spool. The next available number is assigned to the spool, by default.\nRemove\nClick to remove a spool. A Confirm window displays asking you to OK the action. Click Yes to remove the spool, the content of the spool is added to Spool 1.\nYou can remove only the last spool in the sequence.\nAdd\nClick to add a section to the currently selected spool. You must select a support section using a cursor pick in the 3D view.\nYou are prompted to Identify GENSEC\nRenumber\nClick to renumber the spool.\nHighlight\nClick to highlight the currently selected spool members in the 3D view.\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nSpool\nSelect a spool from the drop-down list.\nMembers\nThe list of available members displays the content of the currently selected spool.\nNew\nClick to create a new spool. The next available number is assigned to the spool, by default.\nRemove\nClick to remove a spool. A Confirm window displays asking you to OK the action. Click Yes to remove the spool, the content of the spool is added to Spool 1.\nYou can remove only the last spool in the sequence.\nAdd\nClick to add a section to the currently selected spool. You must select a support section using a cursor pick in the 3D view.\nYou are prompted to Identify GENSEC\nRenumber\nClick to renumber the spool.\nHighlight\nClick to highlight the currently selected spool members in the 3D view.\nClick Cancel to close the Framework Spooling window.\nCE\nClick to select the existing support as the current element.\nThe support name displays in the field.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support :\nThe Select Support field is populated with the name of the identified support.\nSpool\nSelect a spool from the drop-down list.\nMembers\nThe list of available members displays the content of the currently selected spool.\nNew\nClick to create a new spool. The next available number is assigned to the spool, by default.\nRemove\nClick to remove a spool. A Confirm window displays asking you to OK the action. Click Yes to remove the spool, the content of the spool is added to Spool 1.\nYou can remove only the last spool in the sequence.\nAdd\nClick to add a section to the currently selected spool. You must select a support section using a cursor pick in the 3D view.\nYou are prompted to Identify GENSEC\nRenumber\nClick to renumber the spool.\nHighlight\nClick to highlight the currently selected spool members in the 3D view.\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nPick Support :\nNote\n:\nFramework Spooling\nCE\nIdentify By Cursor\nPick Support :\nSelect Support\nSpool\nMembers\nNew\nRemove\nYes\nAdd\nIdentify GENSEC\nRenumber\nHighlight\nCancel\nFramework Spooling"}
{"Headers": "Add Pipe Stress Interface Data", "Content": "Sets the pipe stress interface data for an ancillary.\nYou are prompted to Identify ancillary to modify or <ESC> to finish :\nClick to identify the ancillary using a cursor pick in the 3D view to display the Data window.\n\nCE\nClick to select the existing ancillary as the current element.\nThe ancillary name displays in the field.\nIdentify\nClick to identify an ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary to modify or <ESC> to finish :\nThe Ancillary field is populated with the name of the identified ancillary.\nPipe Stress Interface Data\nYou can update the data attribute fields for the ancillary.\nCE\nClick to select the existing ancillary as the current element.\nThe ancillary name displays in the field.\nIdentify\nClick to identify an ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary to modify or <ESC> to finish :\nThe Ancillary field is populated with the name of the identified ancillary.\nPipe Stress Interface Data\nYou can update the data attribute fields for the ancillary.\nClick Apply to apply the modifications to the Data window.\nClick OK to apply the modifications and close the Data window.\nClick Cancel to discard any inputs and close the Data window.\nCE\nClick to select the existing ancillary as the current element.\nThe ancillary name displays in the field.\nIdentify\nClick to identify an ancillary using a cursor pick in the 3D view.\nYou are prompted to Identify ancillary to modify or <ESC> to finish :\nThe Ancillary field is populated with the name of the identified ancillary.\nPipe Stress Interface Data\nYou can update the data attribute fields for the ancillary.\nNote:\nThe prompt does not display if the ancillary is already selected.\n\n\n\nIdentify ancillary to modify or <ESC> to finish :\nNote\n:\nData\nCE\nIdentify\nIdentify ancillary to modify or <ESC> to finish :\nAncillary\nPipe Stress Interface Data\nApply\nData\nOK\nData\nCancel\nData"}
{"Headers": "Trimmer Requirement", "Content": "Sets the trimmer requirements for supports.\nYou are prompted to Pick Support or <ESC> to finish :\nClick to identify the support using a cursor pick in the 3D view.\nYou can continue to identify additional supports.\nPress ESC to end the selection process and display the Set Trimmer window.\n\nThe Set Trimmer window displays all the identified supports and the current trimmer requirement status.\nCE\nClick to select the existing support as the current element.\nThe CE is added to the list of available supports.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support or <ESC> to finish :\nThe identified support is added to the list of available supports.\nSupport\nThe column displays the support name.\nTrimmer\nThe column displays the trimmer requirement status.\nTRUE indicates a trimmer is required.\nFALSE indicates a trimmer is not required.\nSelect All Supports\nSelect the check box to apply or remove a trimmer requirement for all supports in the list of available supports.\nApply Trimmer\nSelect from the drop down list to apply a trimmer requirement to the currently selected support. A confirm window displays asking you to OK the addition. Click Yes to add the trimmer steel requirement.\nRemove Trimmer\nSelect from the drop down list to remove a trimmer requirement from the currently selected support. A confirm window displays asking you to OK the deletion. Click Yes to delete the trimmer steel requirement.\nCE\nClick to select the existing support as the current element.\nThe CE is added to the list of available supports.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support or <ESC> to finish :\nThe identified support is added to the list of available supports.\nSupport\nThe column displays the support name.\nTrimmer\nThe column displays the trimmer requirement status.\nSelect All Supports\nSelect the check box to apply or remove a trimmer requirement for all supports in the list of available supports.\nApply Trimmer\nSelect from the drop down list to apply a trimmer requirement to the currently selected support. A confirm window displays asking you to OK the addition. Click Yes to add the trimmer steel requirement.\n\nRemove Trimmer\nSelect from the drop down list to remove a trimmer requirement from the currently selected support. A confirm window displays asking you to OK the deletion. Click Yes to delete the trimmer steel requirement.\n\nClick Cancel to close the Set Trimmer window.\nCE\nClick to select the existing support as the current element.\nThe CE is added to the list of available supports.\nIdentify By Cursor\nClick to identify a support using a cursor pick in the 3D view.\nYou are prompted to Pick Support or <ESC> to finish :\nThe identified support is added to the list of available supports.\nSupport\nThe column displays the support name.\nTrimmer\nThe column displays the trimmer requirement status.\nTRUE indicates a trimmer is required.\nFALSE indicates a trimmer is not required.\nSelect All Supports\nSelect the check box to apply or remove a trimmer requirement for all supports in the list of available supports.\nApply Trimmer\nSelect from the drop down list to apply a trimmer requirement to the currently selected support. A confirm window displays asking you to OK the addition. Click Yes to add the trimmer steel requirement.\nRemove Trimmer\nSelect from the drop down list to remove a trimmer requirement from the currently selected support. A confirm window displays asking you to OK the deletion. Click Yes to delete the trimmer steel requirement.\nTRUE indicates a trimmer is required.\nFALSE indicates a trimmer is not required.\nTRUE indicates a trimmer is required.\nTRUE indicates a trimmer is required.\nFALSE indicates a trimmer is not required.\nFALSE indicates a trimmer is not required.\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nPick Support or <ESC> to finish :\nNote\n:\nESC\nSet Trimmer\nSet Trimmer\nCE\nIdentify By Cursor\nPick Support or <ESC> to finish :\nSupport\nTrimmer\nSelect All Supports\nApply Trimmer\nYes\nRemove Trimmer\nYes\nCancel\nSet Trimmer"}
{"Headers": "Create Support Group", "Content": "Creates a support group for two or more supports. The first support group member can be created from a trunnion or a framework support.\nYou are prompted to Identify support framework to create a group or <ESC> to finish:\nClick to identify the first support group member using a cursor pick in the 3D view.\nThe support group is created, additional supports can then be added to the support group\n\nAn identifier [1] is added to the support name.\n\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nIdentify support framework to create a group or <ESC> to finish:\nNote\n:"}
{"Headers": "Add Support to Group", "Content": "Adds the currently selected support to an existing support group.\nIf the first support group member is a trunnion, only hangers can be added to the group.\nIf the first support group member is a framework support, hangers or trunnions can be added to the group.\nYou are prompted to Identify group to add support to:\nClick to identify the first support group member using a cursor pick in the 3D view.\n\nThe added support group member is renamed to be identical to the first support group member and an identifier [2] is added.\n\nIf the currently selected element is not a support, an error message displays summarizing the problem.\n\nClick to identify a support using a cursor pick in the 3D view.\n\n\n\nIdentify group to add support to:"}
{"Headers": "Remove Support from Group", "Content": "Removes a support from a support group.\nYou are prompted to Identify support to remove from a group or <ESC> to finish:\nClick to identify the last support group member using a cursor pick in the 3D view.\n\nThe removed support group member is renamed to be unique and the identifier [2] is removed.\n\nIf the selected element is not the last support member in the support group, an error message displays summarizing the problem.\n\nClick to identify the last support member in the support group using a cursor pick in the 3D view.\nNote:\nOnly the last support group member can be removed from the support group.\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nNote\n:\nIdentify support to remove from a group or <ESC> to finish:\nNote\n:"}
{"Headers": "View Multi Discipline Support Standard", "Content": "Displays a support illustration.\nYou are prompted to Pick Support :\nClick to identify the support using a cursor pick in the 3D view to display the View Multi Discipline Standard window.\n\nThe top of the View Multi Discipline Standard window displays the number of sheets and the currently displayed sheet number.\nClick to display the previous sheet of the illustration.\nClick to display the next sheet of the illustration.\n\nClick to display the previous sheet of the illustration.\n\nClick to display the next sheet of the illustration.\nThe bottom of the View Multi Discipline Standard window displays the name of the support.\nClick Cancel to close the View Multi Discipline Standard window.\nIf the currently selected element is not a support, an error message displays summarizing the problem.\n\nYou are prompted to Identify a support\nClick to identify a support using a cursor pick in the 3D view.\nClick to display the previous sheet of the illustration.\nClick to display the next sheet of the illustration.\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nPick Support :\nNote\n:\nView Multi Discipline Standard\nView Multi Discipline Standard\nView Multi Discipline Standard\nCancel\nView Multi Discipline Standard\nIdentify a support"}
{"Headers": "View Support Dimensions", "Content": "Displays support dimension tags in the 3D view.\nYou are prompted to Pick Support :\nClick to identify the support using a cursor pick in the 3D view.\nYou can continue to select additional supports.\nPress ESC to end the selection process and display the dimension tags for the selected supports.\nRepeat the command to remove the dimension tags from the 3D view.\n\nIf the currently selected element is not a support, a Message window displays instructing you to pick a valid support member.\n\nNote:\nThe prompt does not display if the support is already selected.\n\n\n\nPick Support :\nNote\n:\nESC\nMessage"}
{"Headers": "View Pipe Rests", "Content": "Displays pipe rests in the 3D view.\nAll pipe rests are highlighted in the 3D view with a pin.\nRepeat the command to remove the pin from the pipe rests in the 3D view.\n\n\n\n"}
{"Headers": "View Pipe Dimensions", "Content": "Displays dimension tags for pipes and branches in the 3D view. The functionality also displays the position and function type of supports on the pipe.\nYou are prompted to Pick Pipe Branch(es) or <ESC> to finish :\nClick to identify the branch using a cursor pick in the 3D view.\nYou can continue to identify additional branches on the pipe.\nPress ESC to end the selection process and display the dimension tags for the selected branches.\nRepeat the command to remove the dimension tags from the 3D view.\n\nNote:\nThe prompt does not display if the Branch is already selected.\n\n\n\nPick Pipe Branch(es) or <ESC> to finish :\nNote\n:\nESC"}
{"Headers": "Overview of the Supports Application", "Content": "The Supports application allows you to create standard supports for pipework, cable trays, (both piping based cable trays (BRAN) and cable trays (CTRAY) created by the Cabling System) and HVAC. The application is highly interactive, enabling you to design supports with the minimum of effort. It is also highly configurable, allowing you to define project related defaults to control the design of supports and to determine the range and types of ancillary support components that can be used on the project.\nThe standard supports in this application, which are designed using structural sections, are template driven. A default set of structural templates based on British Standard Steelwork Sections is supplied with the application. All of these templates can be configured to suit the needs of an office or project to adopt a relevant national standard for steelwork sections. Refer to Framework Template Administration for further information.\nAncillaries are items that are attached to the supported object. For example, u-bolts, bolt-on shoes, anchors, and slip-units. The ancillaries associated with the template reflect those available with, or, suitable for, the standard. If the available templates do not reflect what you want to build, either ask your administrator to work with AVEVA Solutions to get your requirement designated as a new standard (and hence a new template) or create as a special support. A good example of a special, support is an additional brace to an existing template. This must be designed as, or converted to, a special with the extra brace added in using the standard Structures application. Otherwise a new template/standard is required.\nVessel Supports are identified as template/standard driven.\nAncillaries for cable tray and HVAC, sometimes referred to as fixings, are deemed to be the responsibility of the relevant contractor and are not dealt with in this application.\n\n\n\nFramework Template Administration\nFramework Template Administration"}
{"Headers": "Administrator\u2019s Role", "Content": "The administrator is responsible for initial setup of the default DATASETS stored in AVEVA Catalog, the default files associated with the Supports application (refer to the Supports Administrator Guide for further information) and setup of the structural steel sizes associated with the framework templates. The Supports application is supplied with a British Steel set of framework templates, which the administrator can modify to suit the specific requirements of the project.\n\n\n\nSupports Administrator Guide\nSupports Administrator Guide"}
{"Headers": "Supports Catalogs and Specifications", "Content": "The Supports application is supplied with a catalog and specification. The range of bore and components in the catalog are fixed and should be adequate for all projects. The catalog supplied and associated \u2018/MDS\u2019 specification must not be modified by the administrator or any other user.\n\n\n"}
{"Headers": "Project Setup", "Content": "This section describes the project setup for MDS.\n\n\n"}
{"Headers": "Projects and Databases", "Content": "This section describes the projects and databases for MDS.\n\n\n"}
{"Headers": "Supplied Projects", "Content": "The Supports application is supplied as part of AVEVA E3D Design. The Supports application relies upon certain project databases within the supplied APS (AVEVA Project Sample) and ACP (AVEVA Catalog Project) projects along with any client specific project data.\nProject APS:\nContains sample databases that are intended to be copied into client projects and configured to suit your own needs.\nThe APS project also hosts the installation version of the MDU database. MDU can be configured to enable creation of user defined ancillaries.\nProject ACP:\nContains AVEVA Supports catalogue data. The data contained within ACP is not intended to be modified.\nProject CPL and PSL:\nIf a manufacturer\u2019s interface is used for hanger design, then the\n/MDS/HANGERS database is not used, and the manufacturer\u2019s projects can be selected instead.\nProject APS:\nContains sample databases that are intended to be copied into client projects and configured to suit your own needs.\nThe APS project also hosts the installation version of the MDU database. MDU can be configured to enable creation of user defined ancillaries.\nProject ACP:\nContains AVEVA Supports catalogue data. The data contained within ACP is not intended to be modified.\nProject CPL and PSL:\nIf a manufacturer\u2019s interface is used for hanger design, then the\n/MDS/HANGERS database is not used, and the manufacturer\u2019s projects can be selected instead.\n\nProject APS:\nContains sample databases that are intended to be copied into client projects and configured to suit your own needs.\nThe APS project also hosts the installation version of the MDU database. MDU can be configured to enable creation of user defined ancillaries.\nProject ACP:\nContains AVEVA Supports catalogue data. The data contained within ACP is not intended to be modified.\nProject CPL and PSL:\nIf a manufacturer\u2019s interface is used for hanger design, then the\n/MDS/HANGERS database is not used, and the manufacturer\u2019s projects can be selected instead.\n\n\n\nAVEVA E3D Design"}
{"Headers": "Supplied Databases", "Content": "This section describes the supplied databases for MDS.\n\n\n"}
{"Headers": "Project ACP", "Content": "Database Name\nDb Number\nDescription\nMDS/CATA\n7320\nCatalogues and specifications\nMASTER/MDSDICT\n7323\nMDS LEXICON database\nMDS/PROP\n7328\nProperties database\nDatabase Name\nDb Number\nDescription\nMDS/CATA\n7320\nCatalogues and specifications\nMASTER/MDSDICT\n7323\nMDS LEXICON database\nMDS/PROP\n7328\nProperties database\n\nDatabase Name\nDb Number\nDescription\nMDS/CATA\n7320\nCatalogues and specifications\nMASTER/MDSDICT\n7323\nMDS LEXICON database\nMDS/PROP\n7328\nProperties database\n\n\n\nDatabase Name\nDb Number\nDescription"}
{"Headers": "Project APS", "Content": "Database Name\nDb Number\nDescription\nMDS/DRAFT\n7322\nDRAFT libraries/templates\nMDS/DESITMPL-BS\n7324\nFramework templates for BS steel\nMDS/DESITMPL-PSL\n7326\nHanger templates for Pipe Support Ltd\nMDS/DESITMPL-GRI\n7327\nHanger templates for Grinnell\nMDS/DESITMPL-AISC\n7329\nFramework templates for AISC Steel\nMDS/DESI-SPECIAL-TMPL-BS\n7330\nProject special framework templates for BS Steel\nMDS/DESI-SPECIAL-TMPL-DIN\n7331\nProject special framework templates for DIN Steel\nMDS/DESI-SPECIAL-TMPL-AISC\n7332\nProject special framework templates for AISC Steel\nMDS/DESITMPL-PIHASA\n7333\nFramework templates for Pihasa\nMDS/WELDS\n7334\nWeld templates DATASETS database\nMDS/DESITPML-DIN\n7350\nFramework templates for DIN Steel\nMDS/MDSAPPDEFAULTS\n7351\nMDS Application Defaults database\nMDS/DESITMPL-BS-ORI\n7352\nOrientated Framework templates for BS Steel\nMDS/DESITMPL-AISC-ORI\n7353\nOrientated Framework templates for AISC Steel\nMDS/DESITMPL-DIN-ORI\n7354\nOrientated Framework templates for DIN Steel\nMDU/CATA\n7355\nMDS Catalogue for USER DEFINED Ancillaries\nMDS/DESITMPL-OGLAEND\n7356\nFramework templates for Oglaend\nDatabase Name\nDb Number\nDescription\nMDS/DRAFT\n7322\nDRAFT libraries/templates\nMDS/DESITMPL-BS\n7324\nFramework templates for BS steel\nMDS/DESITMPL-PSL\n7326\nHanger templates for Pipe Support Ltd\nMDS/DESITMPL-GRI\n7327\nHanger templates for Grinnell\nMDS/DESITMPL-AISC\n7329\nFramework templates for AISC Steel\nMDS/DESI-SPECIAL-TMPL-BS\n7330\nProject special framework templates for BS Steel\nMDS/DESI-SPECIAL-TMPL-DIN\n7331\nProject special framework templates for DIN Steel\nMDS/DESI-SPECIAL-TMPL-AISC\n7332\nProject special framework templates for AISC Steel\nMDS/DESITMPL-PIHASA\n7333\nFramework templates for Pihasa\nMDS/WELDS\n7334\nWeld templates DATASETS database\nMDS/DESITPML-DIN\n7350\nFramework templates for DIN Steel\nMDS/MDSAPPDEFAULTS\n7351\nMDS Application Defaults database\nMDS/DESITMPL-BS-ORI\n7352\nOrientated Framework templates for BS Steel\nMDS/DESITMPL-AISC-ORI\n7353\nOrientated Framework templates for AISC Steel\nMDS/DESITMPL-DIN-ORI\n7354\nOrientated Framework templates for DIN Steel\nMDU/CATA\n7355\nMDS Catalogue for USER DEFINED Ancillaries\nMDS/DESITMPL-OGLAEND\n7356\nFramework templates for Oglaend\n\nDatabase Name\nDb Number\nDescription\nMDS/DRAFT\n7322\nDRAFT libraries/templates\nMDS/DESITMPL-BS\n7324\nFramework templates for BS steel\nMDS/DESITMPL-PSL\n7326\nHanger templates for Pipe Support Ltd\nMDS/DESITMPL-GRI\n7327\nHanger templates for Grinnell\nMDS/DESITMPL-AISC\n7329\nFramework templates for AISC Steel\nMDS/DESI-SPECIAL-TMPL-BS\n7330\nProject special framework templates for BS Steel\nMDS/DESI-SPECIAL-TMPL-DIN\n7331\nProject special framework templates for DIN Steel\nMDS/DESI-SPECIAL-TMPL-AISC\n7332\nProject special framework templates for AISC Steel\nMDS/DESITMPL-PIHASA\n7333\nFramework templates for Pihasa\nMDS/WELDS\n7334\nWeld templates DATASETS database\nMDS/DESITPML-DIN\n7350\nFramework templates for DIN Steel\nMDS/MDSAPPDEFAULTS\n7351\nMDS Application Defaults database\nMDS/DESITMPL-BS-ORI\n7352\nOrientated Framework templates for BS Steel\nMDS/DESITMPL-AISC-ORI\n7353\nOrientated Framework templates for AISC Steel\nMDS/DESITMPL-DIN-ORI\n7354\nOrientated Framework templates for DIN Steel\nMDU/CATA\n7355\nMDS Catalogue for USER DEFINED Ancillaries\nMDS/DESITMPL-OGLAEND\n7356\nFramework templates for Oglaend\n\n\n\nDatabase Name\nDb Number\nDescription"}
{"Headers": "Projects CPL, PSL and LIS", "Content": "The following manufacturer\u2019s interfaces can be used instead of the standard MDS hanger interface:\nCPL - Witch Hanger from Carpenter & Paterson Ltd (supplied)\nPSL - PS Designer from PSL\nLIS - LICAD from Lisega (not supplied)\nCPL - Witch Hanger from Carpenter & Paterson Ltd (supplied)\nCPL - Witch Hanger from Carpenter & Paterson Ltd (supplied)\nPSL - PS Designer from PSL\nPSL - PS Designer from PSL\nLIS - LICAD from Lisega (not supplied)\nLIS - LICAD from Lisega (not supplied)\n\n\n"}
{"Headers": "LISEGA (LIS) Project Setup", "Content": "This section describes the LISEGA (LIS) Project Setup.\nThe LISEGA (LIS) project is not supplied by AVEVA.\nProject setup is required to use the LISEGA supports third party hanger interface.\nIt is necessary to download the latest LISEGA databases from the LISEGA website.\nA new AVEVA E3D Design project must be created using AVEVA Administration\u2122. The project must be given an appropriate name and project code. For example, LISEGA and LIS.\n\nThe username, password and other aspects of the project can be modified using AVEVA Administration\u2122.\nA LISEGA team can be created for the new project.\nPlaceholder databases must be created for the LISEGA databases (downloaded from the LISEGA website).\nCreate the following databases in the new LIS project.\nlis6993_0001:\nName\nLS_CATA\nOwning team\nLISEGA\nDatabase Type\nCatalogue\nAccess Mode\nMultiwrite\nDB Number\n6993\nlis6994_0001:\nName\nH&S_DICT\nOwning team\nLISEGA\nDatabase Type\nDictionary\nAccess Mode\nUpdate\nDB Number\n6994\nlis6993_0001:\nName\nLS_CATA\n\nOwning team\nLISEGA\n\nDatabase Type\nCatalogue\n\nAccess Mode\nMultiwrite\n\nDB Number\n6993\nlis6994_0001:\nName\nH&S_DICT\n\nOwning team\nLISEGA\n\nDatabase Type\nDictionary\n\nAccess Mode\nUpdate\n\nDB Number\n6994\nWhen the databases have been created, it is necessary to copy the downloaded LISEGA databases over the top of the placeholder databases in the %lis000% folder. For example, C:\\Users\\Public\\Documents\\AVEVA\\Projects\\E3D2.1\\LISEGA\\lis000\nWhen the databases have been overwritten, the LISEGA databases can be included in an engineering project.\nlis6993_0001:\nName\nLS_CATA\nOwning team\nLISEGA\nDatabase Type\nCatalogue\nAccess Mode\nMultiwrite\nDB Number\n6993\nlis6994_0001:\nName\nH&S_DICT\nOwning team\nLISEGA\nDatabase Type\nDictionary\nAccess Mode\nUpdate\nDB Number\n6994\nImportant: LISEGA administers project databases separately to AVEVA. There may be discrepancies between the LISEGA projects and the provided information. If differences occur, please contact LISEGA support for further information.\n\n\n\nImportant:\nAVEVA E3D Design"}
{"Headers": "Project Database Setup", "Content": "This section describes the project database setup for MDS.\n\n\n"}
{"Headers": "Project Schema", "Content": "The databases used by the Supports application are split into two classes:\nThe following diagram displays the relationships between the different databases required for use in the Supports application.\n\n      \n         \n            \n               \n                  *\n                \n               \n                  One of the databases listed in each class is required to be used in an MDB.\n                \n            \n            \n               \n                  **\n                \n               \n                  These databases are optional and should be used in addition to their like named counterpart.\n                     For example, MDS/DESITMPL-BS-ORI should be used with MDS/DESITMPL-BS.\n                  \n                \n            \n            \n               \n                  ***\n                \n               \n                  Optional databases provided by the hanger manufacturers to be used in conjunction\n                     with their design interfaces.\n                  \n                \n            \n         \n      \n   \nOne of the databases listed in each class is required to be used in an MDB.\nThese databases are optional and should be used in addition to their like named counterpart.\n                     For example, MDS/DESITMPL-BS-ORI should be used with MDS/DESITMPL-BS.\n                  \nOptional databases provided by the hanger manufacturers to be used in conjunction\n                     with their design interfaces.\n                  \n\n         \n            \n               \n                  *\n                \n               \n                  One of the databases listed in each class is required to be used in an MDB.\n                \n            \n            \n               \n                  **\n                \n               \n                  These databases are optional and should be used in addition to their like named counterpart.\n                     For example, MDS/DESITMPL-BS-ORI should be used with MDS/DESITMPL-BS.\n                  \n                \n            \n            \n               \n                  ***\n                \n               \n                  Optional databases provided by the hanger manufacturers to be used in conjunction\n                     with their design interfaces.\n                  \n                \n            \n         \n      \nAVEVA controlled reference libraries. These databases are maintained by AVEVA and generally regarded as being non-user definable. These databases should be included in customer projects as foreign imports from the AVEVA ACP project.\nUser definable template and configuration databases. These databases contain client/project specific customized supports data. Basic versions of these databases should initially be copied into a client project from the APS project and then modified to suit. You are then free to include the customized versions of these databases either in a local project or by foreign project reference.\nAVEVA controlled reference libraries. These databases are maintained by AVEVA and generally regarded as being non-user definable. These databases should be included in customer projects as foreign imports from the AVEVA ACP project.\nAVEVA controlled reference libraries. These databases are maintained by AVEVA and generally regarded as being non-user definable. These databases should be included in customer projects as foreign imports from the AVEVA ACP project.\nUser definable template and configuration databases. These databases contain client/project specific customized supports data. Basic versions of these databases should initially be copied into a client project from the APS project and then modified to suit. You are then free to include the customized versions of these databases either in a local project or by foreign project reference.\nUser definable template and configuration databases. These databases contain client/project specific customized supports data. Basic versions of these databases should initially be copied into a client project from the APS project and then modified to suit. You are then free to include the customized versions of these databases either in a local project or by foreign project reference.\n\n\n"}
{"Headers": "Project Defaults", "Content": "Client application/supports defaults are stored in an instance of the MDS/APPDEFAULTS database. This database is customizable and can be stored locally within a project environment or referenced from a foreign project.\nFrom time to time, AVEVA updates the database schema in the MDS/APPDEFAULTS. The Supports administrator can update the customized versions of the project when necessary. Tools are provided to achieve this and are contained within AVEVA Catalog. Refer to Update Existing Client Project Application Defaults Databases for further information.\n\n\n\nUpdate Existing Client Project Application Defaults Databases\nUpdate Existing Client Project Application Defaults Databases"}
{"Headers": "Reinforcing Pad Material", "Content": "When the Supports application creates a reinforcing pad on a tube element, it automatically sets the MTOREF attribute to the SPREF of the LSTU to allocate material for the pad. Currently there is no method to set the required length apart from the MTOLENGTH attribute of the detail reference of the lstu spref. It is recommended that this attribute is set to the maximum length of a reinforcing pad so that the maximum length is ordered in all cases.\n\n\n"}
{"Headers": "Reinforcing Pad Length", "Content": "The length of a reinforcing pad can be displayed on an Isometric drawing.\n\nThe reinforcing pad is displayed as a miscellaneous component.\nThe reinforcing pad must be associated with an EXTT dataset. The example displays the EXTT attribute associated with an AT29 reinforcing pad. The EXTT dataset can be added using the Model View window. Refer to Model View for further information.\n\n\n\n\nModel View\nModel View\nModel View"}
{"Headers": "Configuration Checklist", "Content": "This section describes the configuration checklist for MDS.\n\n\n"}
{"Headers": "Project Configuration", "Content": "The table contains all the steps an administrator must check when attempting to configure the Supports application for a project\u2019s requirements.\nStep\nDescription\n1\nLaunch AVEVA Catalog, as a user that has permissions to modify the catalogue and display the Supports Admin Data window.\nModify the defaults:\nModel Application Defaults. For example, clearance, overlap, pipe slope.\nApplication Support Type. For example, FT03 is not needed by project.\nReplacement Support Name. For example, FT09 displays in Model and Draw application as PS132.\nSupport Descriptions. For example, a pedestal support for an elbow is described as a Duck Foot.\nAvailable Support Ancillaries. For example, AT01 is not allowed on Support Type FT08.\nModify the Hangers Configuration Description and Configuration name (optional).\nRemove configurations that are not used on the Project (optional). NOT RECOMMENDED.\n2\nLaunch AVEVA Catalog, as a user that has permissions to modify the catalogue and display the Supports Ancillary Data window.\nComplete all dimensions (design parameters), weight, minimum and maximum values required by the project\n3\nModify the project specification to match settings used in step 2. For example the pipe class \u2018CS\u2019 for carbon steel to match the :MDSPipeMat uda at specification level in the project.\n4\nLaunch AVEVA Catalog, as a user that has permissions to modify the catalogue and display the Supports Admin Data window.\nModify the support zone identification (Zone ID) settings.\n5\nModify DES-SUPP-NAMES* in the project default directory for:\nAuto naming files.\n6\nStructural Design Templates - Refer to the Framework Template Administration section for further information.\n7\nHanger Design Templates - Check that the Template represents the configuration defined in the Supports Admin Data and Supports Hanger Data windows. Not required if using a Supports Hanger Manufacturer Interface.\n8\nDrawing Backing Sheets \u2011 Create/modify to suit project requirements.\nStep\nDescription\n1\nLaunch AVEVA Catalog, as a user that has permissions to modify the catalogue and display the Supports Admin Data window.\nModify the defaults:\nModel Application Defaults. For example, clearance, overlap, pipe slope.\nApplication Support Type. For example, FT03 is not needed by project.\nReplacement Support Name. For example, FT09 displays in Model and Draw application as PS132.\nSupport Descriptions. For example, a pedestal support for an elbow is described as a Duck Foot.\nAvailable Support Ancillaries. For example, AT01 is not allowed on Support Type FT08.\nModify the Hangers Configuration Description and Configuration name (optional).\nRemove configurations that are not used on the Project (optional). NOT RECOMMENDED.\n2\nLaunch AVEVA Catalog, as a user that has permissions to modify the catalogue and display the Supports Ancillary Data window.\nComplete all dimensions (design parameters), weight, minimum and maximum values required by the project\n3\nModify the project specification to match settings used in step 2. For example the pipe class \u2018CS\u2019 for carbon steel to match the :MDSPipeMat uda at specification level in the project.\n4\nLaunch AVEVA Catalog, as a user that has permissions to modify the catalogue and display the Supports Admin Data window.\nModify the support zone identification (Zone ID) settings.\n5\nModify DES-SUPP-NAMES* in the project default directory for:\nAuto naming files.\n6\nStructural Design Templates - Refer to the Framework Template Administration section for further information.\n7\nHanger Design Templates - Check that the Template represents the configuration defined in the Supports Admin Data and Supports Hanger Data windows. Not required if using a Supports Hanger Manufacturer Interface.\n8\nDrawing Backing Sheets \u2011 Create/modify to suit project requirements.\n\nStep\nDescription\n1\nLaunch AVEVA Catalog, as a user that has permissions to modify the catalogue and display the Supports Admin Data window.\nModify the defaults:\nModel Application Defaults. For example, clearance, overlap, pipe slope.\nApplication Support Type. For example, FT03 is not needed by project.\nReplacement Support Name. For example, FT09 displays in Model and Draw application as PS132.\nSupport Descriptions. For example, a pedestal support for an elbow is described as a Duck Foot.\nAvailable Support Ancillaries. For example, AT01 is not allowed on Support Type FT08.\nModify the Hangers Configuration Description and Configuration name (optional).\nRemove configurations that are not used on the Project (optional). NOT RECOMMENDED.\n2\nLaunch AVEVA Catalog, as a user that has permissions to modify the catalogue and display the Supports Ancillary Data window.\nComplete all dimensions (design parameters), weight, minimum and maximum values required by the project\n3\nModify the project specification to match settings used in step 2. For example the pipe class \u2018CS\u2019 for carbon steel to match the :MDSPipeMat uda at specification level in the project.\n4\nLaunch AVEVA Catalog, as a user that has permissions to modify the catalogue and display the Supports Admin Data window.\nModify the support zone identification (Zone ID) settings.\n5\nModify DES-SUPP-NAMES* in the project default directory for:\nAuto naming files.\n6\nStructural Design Templates - Refer to the Framework Template Administration section for further information.\n7\nHanger Design Templates - Check that the Template represents the configuration defined in the Supports Admin Data and Supports Hanger Data windows. Not required if using a Supports Hanger Manufacturer Interface.\n8\nDrawing Backing Sheets \u2011 Create/modify to suit project requirements.\n\n\n\nFramework Template Administration\nStep\nDescription\nAVEVA Catalog\nSupports Admin Data\nModel\nModel\nDraw\nAVEVA Catalog\nSupports Ancillary Data\nAVEVA Catalog\nSupports Admin Data\nFramework Template Administration\nSupports Admin Data\nSupports Hanger Data"}
{"Headers": "Framework Template Administration", "Content": "This section describes the framework template administration for MDS.\n\n\n"}
{"Headers": "Template Modification Rules", "Content": "This section describes the template modification rules for MDS.\n\n\n"}
{"Headers": "Special Instructions", "Content": "Supports application Structural Design Templates may be configured to an alternative National Standard for Steelwork Sections than the British Standard supplied as default. This may be a different size from the same steelwork standard or a different size from a different standard.\nApply the following rules when replacing the default size to make sure the Supports application functions correctly:\nWhen a framework is created, the template is copied to the datum support (the first pipe identified will be the datum support) and then the framework is stretched and re-sized, depending on the method of creation used. For example, Cursor, Dimensions or Clearance. Therefore the initial positioning and orientation of the sections within the structure are critical.\nAn example of replacing the default steelwork size is shown in Framework Setup.\nThe origin of each template must remain in the same position when the steelwork size is modified. The example shown in this section has the origin on the back mark of the cross bar. Move the origin to align with the back when the size is changed. This makes sure that the origin is placed in the correct position in relationship to the datum ancillary (ANCI) when the framework is generated.\nDO NOT modify the position of the section starts and ends in relationship to the structure orientation.\nUse the naming convention described in Framework Naming Conventions.\nThere is a limit of fifty structural templates per support type.\nAll structural sections defined as GENSEC elements in the default templates will have a numerical value set against their design parameter attribute. For example, the default value for design parameter number 1 of GENSEC \u2018/SUPPORT/FRAMES/BS/FT09/1-BAR-1\u2019 is set to \u20181140\u2019. This value is the maximum allowable length for this particular GENSEC. The value is checked against the actual length of a GENSEC element, named <structurename>-BAR-1, and is created automatically during the creation of a Pipe Support by the Supports application. Clients may modify this attribute in their template database as part of their configuration.\nWhere a template contains internal joints, it may be necessary to modify the specification reference to a handed joint when a mirror operation is performed. To do this, set the uda :MdsMirror to the spref required for a mirrored joint, when the joint is created in the template.\nThe origin of each template must remain in the same position when the steelwork size is modified. The example shown in this section has the origin on the back mark of the cross bar. Move the origin to align with the back when the size is changed. This makes sure that the origin is placed in the correct position in relationship to the datum ancillary (ANCI) when the framework is generated.\nThe origin of each template must remain in the same position when the steelwork size is modified. The example shown in this section has the origin on the back mark of the cross bar. Move the origin to align with the back when the size is changed. This makes sure that the origin is placed in the correct position in relationship to the datum ancillary (ANCI) when the framework is generated.\nDO NOT modify the position of the section starts and ends in relationship to the structure orientation.\nDO NOT modify the position of the section starts and ends in relationship to the structure orientation.\nUse the naming convention described in Framework Naming Conventions.\nUse the naming convention described in Framework Naming Conventions.\nThere is a limit of fifty structural templates per support type.\nThere is a limit of fifty structural templates per support type.\nAll structural sections defined as GENSEC elements in the default templates will have a numerical value set against their design parameter attribute. For example, the default value for design parameter number 1 of GENSEC \u2018/SUPPORT/FRAMES/BS/FT09/1-BAR-1\u2019 is set to \u20181140\u2019. This value is the maximum allowable length for this particular GENSEC. The value is checked against the actual length of a GENSEC element, named <structurename>-BAR-1, and is created automatically during the creation of a Pipe Support by the Supports application. Clients may modify this attribute in their template database as part of their configuration.\nAll structural sections defined as GENSEC elements in the default templates will have a numerical value set against their design parameter attribute. For example, the default value for design parameter number 1 of GENSEC \u2018/SUPPORT/FRAMES/BS/FT09/1-BAR-1\u2019 is set to \u20181140\u2019. This value is the maximum allowable length for this particular GENSEC. The value is checked against the actual length of a GENSEC element, named <structurename>-BAR-1, and is created automatically during the creation of a Pipe Support by the Supports application. Clients may modify this attribute in their template database as part of their configuration.\nWhere a template contains internal joints, it may be necessary to modify the specification reference to a handed joint when a mirror operation is performed. To do this, set the uda :MdsMirror to the spref required for a mirrored joint, when the joint is created in the template.\nWhere a template contains internal joints, it may be necessary to modify the specification reference to a handed joint when a mirror operation is performed. To do this, set the uda :MdsMirror to the spref required for a mirrored joint, when the joint is created in the template.\nNote:\nExternal joints to support frameworks also use the :MdsMirror mechanism.\n\n\n\nFramework Naming Conventions\nFramework Setup\nFramework Naming Conventions\n<structurename>\n-BAR-1\nNote\n:\nFramework Setup"}
{"Headers": "Framework Setup", "Content": "This section describes the framework setup for MDS.\n\n\n"}
{"Headers": "Replacing the Default Steelwork Section Size", "Content": "The Supports application is supplied with a default set of frameworks based on British Steelwork standards. The project can modify the steelwork sizes and the following example explains how the administrator makes the alternatives available. In the example, support type FT09 option 1, which uses 60x60x8 angle British Steel Standard is changed to 2x2x3/8 AISC Standard.\n\n\n\nProperties"}
{"Headers": "Modifying the Design Template\u2019s Minimum/Maximum Lengths", "Content": "All structural sections defined in the Design Template Database have their design parameter set to the maximum usable length. The Supports application issues a warning to the user when the Support Integrity Checker is actioned at the end of each creation or modification process. This check is only a warning and the user is allowed to complete the support. The warning indicates to the user that either the support is stressed or the steelwork size needs increasing.\nIt is also possible to define a minimum length by setting design parameter 2. For example, if the design parameters of a section are set to 1000 100, the maximum length is 1000 and the minimum length is 100.\n\n\n"}
{"Headers": "Creating Template Internal Joints", "Content": "Create template internal joints using standard structural connections. If a joint needs to be \u2018handed\u2019 for mirrored frameworks, use the uda :MdsMirror at the catalogue join element to store the joint reference.\n\n\n"}
{"Headers": "Modifying the Appearance of Joints and Fittings on the Supports ADP Drawing", "Content": "If you do not want a template joint or fitting to appear on the Supports ADP drawing, set the FIXING function attribute to DUMMY. Joints and fixings are then ignored on the drawing material list and are not tagged in the graphical views. Use this attribute when a joint, which has no physical properties, is used to cut-out a section.\n\n\n"}
{"Headers": "Naming Conventions", "Content": "This section describes the naming conventions for MDS.\n\n\n"}
{"Headers": "Framework Naming Conventions", "Content": "Make sure each framework conforms to the following naming conventions. This enables the Supports application to navigate to the appropriate element and customize the application for both the Model and Draw stages of support production. Failure to apply these naming conventions may cause the applications to fail to produce supports.\nAPPLDW\n/SUPPORT/FRAMES/{name}\n/SUPPORT/FRAMES/BS\nAPPLDA\n/SUPPORT/FRAMES/{name}/DATA/{type}\n/SUPPORT/FRAMES/BS/DATA/FT\nZONE\n/SUPPORT/FRAMES/{name}/{frameworktype}\n/SUPPORT/FRAMES/BS/FT09\nSTRU\n/SUPPORT/FRAMES/{name}/{frameworktype}/{option}\n/SUPPORT/FRAMES/BS/FT09/1\nFRMW\n/SUPPORT/FRAMES/{name}/{frameworktype}/{option}-FRMW1\n/SUPPORT/FRAMES/BS/FT09/1-FRMW1\nGENSEC\nCROSSBAR\n\n\n/SUPPORT/FRAMES/{name}/{frameworktype/{option}-BAR-1\n/SUPPORT/FRAMES/BS/FT09/1-BAR-1\n\nVERTICAL MEMBERS (if required)\n\n\n/SUPPORT/FRAMES/{name}/{frameworktype}/{option}-V1 or V2\n/SUPPORT/FRAMES/BS/FT09/1-V1\nSUBS\n/SUPPORT/FRAMES/{name}/{frameworktype}/{option}-SUBS1\n/SUPPORT/FRAMES/BS/FT29/1-SUBS1\nJLDATU\n/SUPPORT/FRAMES/{name}/{frameworktype]/{option}-V1/S1\n/SUPPORT/FRAMES/BS/FT09/10-V1/S1\nPLDATU\n/SUPPORT/FRAMES/{name/{frameworktype}/{option}-V1/S1/PLDAT\n/SUPPORT/FRAMES/BS/FT09/10-V1/S1/PLDAT\nFIXING\n/SUPPORT/FRAMES/{name}/{frameworktype/{option}-V1/S1/IJOINT1\n/SUPPORT/FRAMES/BS/FT09/10-V1/S1/IJOINT1\nThere are two zones for each of these framework types: FT03, FT04, FT14, FT15, FT18, and FT19. Each one is supplied with the suffix -H or -V. For example, /SUPPORT/FRAMES/BS/FT03H.\nThe suffix allows the orientation of members within the structure to be different when used with vertical or horizontal lines.\nType\nName format\nExample\nAPPLDW\n/SUPPORT/FRAMES/{name}\n/SUPPORT/FRAMES/BS\nAPPLDA\n/SUPPORT/FRAMES/{name}/DATA/{type}\n/SUPPORT/FRAMES/BS/DATA/FT\nZONE\n/SUPPORT/FRAMES/{name}/{frameworktype}\n/SUPPORT/FRAMES/BS/FT09\nSTRU\n/SUPPORT/FRAMES/{name}/{frameworktype}/{option}\n/SUPPORT/FRAMES/BS/FT09/1\nFRMW\n/SUPPORT/FRAMES/{name}/{frameworktype}/{option}-FRMW1\n/SUPPORT/FRAMES/BS/FT09/1-FRMW1\nGENSEC\nCROSSBAR\n/SUPPORT/FRAMES/{name}/{frameworktype/{option}-BAR-1\n/SUPPORT/FRAMES/BS/FT09/1-BAR-1\nVERTICAL MEMBERS (if required)\n/SUPPORT/FRAMES/{name}/{frameworktype}/{option}-V1 or V2\n/SUPPORT/FRAMES/BS/FT09/1-V1\nSUBS\n/SUPPORT/FRAMES/{name}/{frameworktype}/{option}-SUBS1\n/SUPPORT/FRAMES/BS/FT29/1-SUBS1\nJLDATU\n/SUPPORT/FRAMES/{name}/{frameworktype]/{option}-V1/S1\n/SUPPORT/FRAMES/BS/FT09/10-V1/S1\nPLDATU\n/SUPPORT/FRAMES/{name/{frameworktype}/{option}-V1/S1/PLDAT\n/SUPPORT/FRAMES/BS/FT09/10-V1/S1/PLDAT\nFIXING\n/SUPPORT/FRAMES/{name}/{frameworktype/{option}-V1/S1/IJOINT1\n/SUPPORT/FRAMES/BS/FT09/10-V1/S1/IJOINT1\n\n\n\nModel\nDraw"}
{"Headers": "Available Templates", "Content": "This section describes the available templates for MDS.\n\n\n"}
{"Headers": "Extending the Number of Steelwork Framework Types Available", "Content": "The supplied set of templates contain, typically, four options for each framework. To extend this number, create extra structures using the naming convention in Framework Naming Conventions. To reduce the number of framework types, delete unwanted structures from the design template database. The supplied specification handles up to fifty options per framework type.\n\n\n\nFramework Naming Conventions\nFramework Naming Conventions"}
{"Headers": "Template Options", "Content": "This section describes the template options for MDS.\n\n\n"}
{"Headers": "Availability of Cross Bars", "Content": "Each standard has the ability to add up to a maximum of six cross bars. In some circumstances the office or project standard may not want a particular standard to allow cross bar creation. Control this by setting the :Mdsbars attribute at the template zone level. Use a \u2018true\u2019 setting to allow cross bar creation and \u2018false\u2019 to prevent it.\n\n\n"}
{"Headers": "Creation of Standard in the Horizontal or Vertical Plane", "Content": "Some standards allow the creation of a support in the horizontal or vertical plane. In some circumstances the office or project standard may not allow both. Control this by setting the :MdsHV attribute at the template zone level.\n:MdsHV\nDescription\nBOTH\nAllows creation in the horizontal and vertical plane\nHORI\nAllows creation in the horizontal plane only\nVERT\nAllows creation on the vertical plane only\n:MdsHV\nDescription\nBOTH\nAllows creation in the horizontal and vertical plane\nHORI\nAllows creation in the horizontal plane only\nVERT\nAllows creation on the vertical plane only\n\n:MdsHV\nDescription\nBOTH\nAllows creation in the horizontal and vertical plane\nHORI\nAllows creation in the horizontal plane only\nVERT\nAllows creation on the vertical plane only\n\n\n\n:MdsHV\nDescription"}
{"Headers": "Maximum Section Lengths", "Content": "At each section within the template, design parameter 1 is set to the maximum length allowed. The support integrity checker monitors this value against the actual length and issues a message to the user when the support has been completed. If the :MdsCheck attribute is set to true, the user is not allowed to complete the support without making the section length less than the maximum allowed. If the :MdsCheck attribute is set to false, a warning is issued and the support is completed.\n\n\n"}
{"Headers": "Cross Bar Overlap Override", "Content": "When a support is created, it uses the application overlap default, obtained from the Supports Application Defaults window.\n\nThis value is used to overlap the steelwork for welding (as per the rules defined for each standard).\n\nThis value can be overridden on each bar of the template by setting the :MdsOlap attribute. If the uda :MdsOlap is set to OVERLAP, the application uses the overlap value stored in the uda :MdsOnum instead of the global steelwork overlap value.\n\n\n\nSupports Application Defaults"}
{"Headers": "Vertical Section Overlap", "Content": "The vertical GENSEC is extended past the cross bar by the application overlap value, in order to weld the GENSEC together. In some circumstances the vertical member may need to be flush with the top of the cross bar. To achieve this, set the uda :MdsOlap value at the vertical GENSEC to OVERLAP and the uda :MdsOnum value to -100 (if the cross bar depth is 100).\nThe following example is the standard/default configuration with the :MdsOlap unset <default>.\n\nThe following example assumes a common template GENSEC size of 100x100x8 angle. The vertical GENSEC uda :MdsOlap value is set to OVERLAP and the :MdsOnum value is set to -100, (the depth of the cross bar being 100).\n\n\n\n"}
{"Headers": "Mitred Frameworks", "Content": "Mitred templates can be created using a combination of appropriate overlap overrides and bar end plane manipulation.\nThe following example describes the modification of an FT09 template standard to include miterd internal faces.\n\nThe example displays a horizontal bar and two vertical legs of a profile sized 70mm x 70mm x 6mm. The bar and vertical legs have been extended so that each end is flush with the steelwork adjacent to it. The horizontal bar justification p-line is CBOT and the vertical bars are justified to the NA p-line.\nTo miter the framework, two steps are required:\n\n\n"}
{"Headers": "Modify End Plane Direction - Horizontal Bar", "Content": "The horizontal bar ends must be modified so that they are cut in the required plane directions for a 45-degree miter. The plane directions are controlled by the DRNEND and DRNSTART attributes on the GENSEC element. The attributes set the plane normal direction of each end of the GENSEC.\nThe example displays the settings:\n\nThe bar ends are cut in the desired direction to produce a miter.\nNote:\nThe plane normal origin is set at the end point of the justification line of the GENSEC (CBOT in this case).\n\n\n\nNote\n:"}
{"Headers": "Modify End Overlaps - Horizontal Bar", "Content": "When the end directions have been defined for the horizontal bar, the overlap values must be overwritten. When the FT09 standard is built, the ends of the bar are extended so that they are initially flush with the outside of each vertical bar. The bar must be offset at each end to move the miter plane from the built position to the required position.\nThe example displays the CBOT p-line as the plane origin at either end of the GENSEC. When the FT09 standard is built, the CBOT is initially extended to the outside face of each vertical bar. In order to move the miter plane into the correct position, an offset distance equal to the width of the vertical bar must be applied. In this case the vertical bar width is 70mm).\n\nThe offset override can be applied by setting attribute values on the horizontal bar. The overlap values are applied at both ends of the horizontal bar:\nNote:\nThe OVERLAP keyword instructs the software to override the system overlap value.\n\n\n\nNote\n:"}
{"Headers": "Modify the End Plane Direction - Vertical Bars", "Content": "Modifications can be made to vertical bars. In this case, the bars are justified to the neutral axis p-line (NA) instead of CBOT.\nThe example displays the settings:\n\n\n\n"}
{"Headers": "Modify the End Overlaps - Horizontal Bar", "Content": "The vertical bar ends must be modified to ensure that the miter plane is positioned correctly when the framework is built.\nIn this case, the offset value is not the same as the horizontal bar because the NA p-line is being used as the justification line. This means that the offset distance is measured from the NA p-line to the outside leg of the vertical bar and the length of the vertical bars must be reduced by this amount during the framework build. In the example, the distance between the NA p-line end to the outside face of the bar is 50.7mm.\nThe example displays the settings:.\n\nThe modifications ensure that a mitered framework is built when the selected standard is created.\n\n\nThe template administrator can manually modify bar lengths in the template to display a representative view of the template as it is built in the model.\nThe example displays a template that has been modified to look more like the framework as it is generated in the Supports application. The bar lengths have been manually altered to show the appropriate miter.\n\nNote:\nThe layout of the template members may not look the same as the built support. The example displays template members when modifications are made.\nNote: Manual adjustments do not have any impact on the way the framework is built in the model.\n\n\n\nNote\n:\nNote\n:"}
{"Headers": "Maximum Allowable Bore Sizes", "Content": "Each support framework has the functionality to control the minimum and maximum pipe bore allowed for the template at the owning ZONE and the individual template STRU elements. Setting the minimum and maximum bore at the owning ZONE of the templates defines the minimum and maximum bore for the entire framework. It is also possible to set the minimum and maximum bore at the STRU for each individual framework template. For example, if the first template for FT09 is 60x06x8 angle, the :MdsMaxBore to is set to 100 and the :MdsMinBore to is set to 50, a pipe cannot be added to the support which is less than 50 or greater than 100. If the support is created on a pipe that is larger or smaller than this range, the template is not available upon creation and the Supports application attempts to select the next valid template in the list. The minimum and maximum bore must be set at the owning ZONE for the templates and must encompass the size range of all the individual templates below it.\n\n\n"}
{"Headers": "Allowable Dimension Ranges", "Content": "The support framework can be configured to set the minimum and maximum dimension values for each pipe bore allowed on the framework. This is achieved by setting the MdsRange: UDA of the template STRU.\nNote:\nAllowable dimensions and their effect on the framework differ between standards. Detailed information about allowable dimensions for each standard are contained within the SupportConfiguration.xml file. Refer to Dimension Customization for further information.\n\n\n\nDimension Customization\nNote\n:\nDimension Customization"}
{"Headers": "Example: Single Bore Ranges", "Content": "The example displays an FT35 framework template which is configured by setting four dimensional values.\n\nThe MDSRange UDA for the first template is set to:\nThis is interpreted as:\n\nThe example contains 2 dimension ranges separated by the ' \\ ' character. Each range is made up of 4 values separated by the ',' character. The comma separated range values are:\nDescription\nThe dimension is controlled by this range.\nThe minimum length of the dimension.\nThe maximum length of the dimension.\nThe pipe bore that the dimension values apply to.\nExample\n1\n0\n914\n50\nFor the example template and the range in the above table we can say the following: For pipe bores up to 50mm, dimension 1 must be between 0 and 914mm.\nIt is possible to define a dimension range for more than one dimension at a time. In the above example, Range 2 defines values for multiple dimensions. Multiple dimension assignments are always encapsulated by brackets () and are separated by the '/' character.\nDescription\nThe dimension is controlled by this range. Additional '/' character separated values encapsulated in brackets define multiple dimension ranges.\nThe minimum length of the dimension.\nThe maximum length of the dimension.\nThe pipe bore that the dimension values apply to.\nExample\n(3/4)\n0\n610\n50\nThe values in Range 2 mean that for pipe bores up to 50mm, dimensions 3 and 4 must be between 0 and 610mm.\nField 1\nField 2\nField 3\nField 4\nDescription\nThe dimension is controlled by this range.\nThe minimum length of the dimension.\nThe maximum length of the dimension.\nThe pipe bore that the dimension values apply to.\nExample\n1\n0\n914\n50\nField 1\nField 2\nField 3\nField 4\nDescription\nThe dimension is controlled by this range. Additional '/' character separated values encapsulated in brackets define multiple dimension ranges.\nThe minimum length of the dimension.\nThe maximum length of the dimension.\nThe pipe bore that the dimension values apply to.\nExample\n(3/4)\n0\n610\n50\nNote:\nDimension 2 is omitted as it does not need to be checked.\n\n\n\nNote\n:\nField 1\nField 2\nField 3\nField 4\nDescription\nExample\nDescription\nExample"}
{"Headers": "Example: Multiple Bore Ranges", "Content": "It is possible to set range values for dimensions so that when larger bore pipes are used on the framework, the allowable dimensions can be reduced as necessary. For example, the range used for SIngle Bore Ranges can be modified if larger pipes are used by adding additional dimensional ranges. Refer to Example: Single Bore Ranges for further information. In this case, additional values for 100mm pipe bores are created.\n\nRange 1 and Range 3 both set a dimensional range for dimension 1 of the framework. If the framework supports 50mm bore pipes, the dimension 1 range is 0 - 914mm as defined by Range 1. If the framework supports 100mm bore pipes, the dimension 1 range is 0 - 500mm as defined by range 3.\nNote:\nFor a mixture of pipe bores used on a framework, the largest pipe bore is always used to apply the appropriate range values.\n\n\n\nExample: Single Bore Ranges\nExample: Single Bore Ranges\nNote\n:"}
{"Headers": "Automatic Steelwork Orientation", "Content": "The Supports application can automatically orientate the support structure steel members of a framework type support, dependant on the orientation of identified stiffeners. The correct orientation is achieved by utilizing appropriate templates. Each standard template has four alternatives as depicted in the example for an FT08 support frame.\n\nThe alternative templates are named in the form:\nwhere suffix, is a configuration code based on the orientation of the stiffeners. For example, /SUPPORT/FRAMES/BS/FT08/1/1, /SUPPORT/FRAMES/BS/FT08/1/2.\nOnly templates that are built up from angle profiles have oriented alternatives.\nThe user-defined attribute (uda) :MdsTmplOri is included in the MDS project MASTER/MDSDICT, which is used to store the orientation of stiffeners as an integer. This uda is available at STRU level and the default value is \"0\".\n/{standard_template_name}/{suffix}\n\n\n\nsuffix"}
{"Headers": "Project Special Templates", "Content": "This section describes the project special templates for MDS.\n\n\n"}
{"Headers": "Philosophy", "Content": "Project special templates allow for the creation of a special support with some GENSEC members very quickly, and if necessary to complete the design of the support in the standard Supports application.\nWrite access is required to the project special discipline zones owned by the APPLDW, for example, /SUPPORT/FRAMES/SPECIALS/BS to create your own Project Special structural templates.\nThe origin of a support structure is always at the P9 of the DATUM ancillary of the current support being created. The copied members of a project special template are positioned relative to the support structure origin position.\n\n\n"}
{"Headers": "Storage Areas", "Content": "It is mandatory that project special templates zones are stored in an APPLDW named /SUPPORT/FRAMES/SPECIALS/{name}.\nThree zones are required to store the project special structure templates. Name them as follows to enable the Supports application to recognize the appropriate discipline templates:\nIn the Supports application, if a discipline zone exists, for example, /SUPPORT/SPECIALS/BS/PIPE, the STRU elements are displayed in the Select Project Special Template window. Otherwise you are informed that the zone /SUPPORT/SPECIALS/BS/PIPE does not exist, and the Copy Project Special operation is aborted. If the zone exists but there are no STRU elements, an empty list displays on the Select Project Special Template window.\n/SUPPORT/SPECIALS/{name}/PIPE, the PIPING template zone.\n/SUPPORT/SPECIALS/{name}/HVAC, the HVAC template zone.\n/SUPPORT/SPECIALS/{name}/TRAY, the Cable Tray template zone.\n/SUPPORT/SPECIALS/{name}/PIPE, the PIPING template zone.\n/SUPPORT/SPECIALS/{name}/PIPE, the PIPING template zone.\n/SUPPORT/SPECIALS/{name}/HVAC, the HVAC template zone.\n/SUPPORT/SPECIALS/{name}/HVAC, the HVAC template zone.\n/SUPPORT/SPECIALS/{name}/TRAY, the Cable Tray template zone.\n/SUPPORT/SPECIALS/{name}/TRAY, the Cable Tray template zone.\nNote:\nThe application dataworld associated with special supports must have the purpose set to MDSS to be registered for use with the Supports application.\n\n\n\nSelect Project Special\nSelect Project Special\nNote\n:"}
{"Headers": "Filter Settings at a Piping or Tray Project Special Template", "Content": "The uda :MdsHv setting at the STRU element of the project special template is the only filtering mechanism available. It can be set to HORI, VERT, or BOTH. For example, only available on horizontal pipes or trays, only available on vertical pipes or trays or available on both horizontal and vertical trays. These settings are relative to the orientation of the current pipe or tray being supported by the special support.\nThe list of piping and cable tray project special templates displayed, and available to the user, is the same list as the STRU members that currently exist in the appropriate discipline template zone. It is filtered according to the settings of the uda :MdsHv at the structural template, and the orientation of the pipe or tray being supported.\nThe selected structural template is copied into the special support being created without any modifications to the design of its members. None of the attributes at the project special STRU template or any of its members are used by the Supports application for either of these disciplines. They are not required and should not be set.\nThe project special templates members in the piping and cable tray disciplines are copied exactly into the special support and positioned relative to the special support origin currently being created. There is no automatic modification of the positions and length of the template members when they are copied into the support.\n\n\n"}
{"Headers": "Filter and Build Settings at an HVAC Project Special Template", "Content": "HVAC project special templates allow frameworks to be built with limited automated re-sizing for variable size ducting.\n\n\n"}
{"Headers": "HVAC Structure Template", "Content": "The list of HVAC templates, for the HVAC STRT element to be supported, is filtered on the settings of two uda\u2019s. They are :MdsHv (described in Filter Settings at a Piping or Tray Project Special Template) and :MdsRange and are both attributes of the STRU template.\nThe second filter control, :MdsRange, is implemented for HVAC templates only. It controls whether insulation exists on the HVAC STRT element being supported. The settings are shown in the table below:\n0\nRestricts the STRU template to support only HVAC STRT elements that are uninsulated.\n1\nRestricts the STRU template to support only HVAC STRT elements that are insulated.\n2, any other value, or left unset\nAllows the STRU template to support HVAC STRT elements that are either uninsulated or insulated.\nHaving set the udas at the STRU templates, consider also :MdsCheck. Set this uda at the time the template is selected and/or built from the list displayed in the Select Project Special Template window. The options are shown in the table below:\ntrue\nIncludes the insulation thickness of the HVAC STRT element in the design and build calculations of the STRU template members copied to the current HVAC Special Support.\nfalse\n(default setting)\nExclude the insulation thickness of the HVAC STRT element in the design and build calculations of the STRU template members copied to the current HVAC Special Support.\n\nSetting\nAction\n0\nRestricts the STRU template to support only HVAC STRT elements that are uninsulated.\n1\nRestricts the STRU template to support only HVAC STRT elements that are insulated.\n2, any other value, or left unset\nAllows the STRU template to support HVAC STRT elements that are either uninsulated or insulated.\nSetting\nAction\ntrue\nIncludes the insulation thickness of the HVAC STRT element in the design and build calculations of the STRU template members copied to the current HVAC Special Support.\nfalse\n(default setting)\nExclude the insulation thickness of the HVAC STRT element in the design and build calculations of the STRU template members copied to the current HVAC Special Support.\n\n\n\nFilter Settings at a Piping or Tray Project Special Template\nFilter Settings at a Piping or Tray Project Special Template\nSetting\nAction"}
{"Headers": "HVAC Structure Template Members", "Content": "Like a standard framework template, HVAC special template members are added to the template relative to the origin of the template STRU.\nEach of the HVAC Project Special Support templates are built on a base HVAC STRT duct sized 500mm wide x 500mm high. This is done to enable relative sizing and positioning of template members when the HVAC special template is built on a different duct size.\n\nWhen the template is built, new elements are created and positioned as required for each support case.\nIt is possible to create GENSECS (representing framework bars), SUBS (representing items, for example, end plates) and EXTR (extrusions which can be used to represent, for example, linings).\nIt is possible to control the relative positions of the GENSEC, SUBS and EXTR element types (including the vertices of EXTR elements when they are applied to a duct of different size to a reference duct 500mm x 500mm. It is also possible to control the relative extension of GENSEC elements.\nThe control of element relative positioning and extension is controlled by the UDAs:\nBoth UDAs are configured as a series of character delimited instructions, a typical instruction string is:\nThe instruction string can be broken down into three sections (delimited by the '\\' character).\n\n\n\n\n:MdsConfigA\n:MdsConfigB"}
{"Headers": "Element Positioning", "Content": "Description\nField to control whether or not relative positioning is enabled for the current element.\nAn E3D model direction wrt the owning STRU. If positioning is required, any positive offsets are performed in this direction.\nDistance proportion of the calculated difference between the reference HVAC duct and the supported HVAC in the model that will be used to offset the current element. For example, if a 300mm x 300mm HVAC is being supported, the difference is 300mm - 500mm = -200mm and bar positions will need to move to suit the smaller duct.\nThe cross-sectional dimension to be used to calculate any dimension differences between the reference HVAC and the current element.\n\nExample\nTRUE\nW\n0.5\nWIDTH\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nDescription\nField to control whether or not relative positioning is enabled for the current element.\nAn E3D model direction wrt the owning STRU. If positioning is required, any positive offsets are performed in this direction.\nDistance proportion of the calculated difference between the reference HVAC duct and the supported HVAC in the model that will be used to offset the current element. For example, if a 300mm x 300mm HVAC is being supported, the difference is 300mm - 500mm = -200mm and bar positions will need to move to suit the smaller duct.\nThe cross-sectional dimension to be used to calculate any dimension differences between the reference HVAC and the current element.\nExample\nTRUE\nW\n0.5\nWIDTH\n\n\n\nDescription\nExample"}
{"Headers": "GENSEC START / GENSEC END Extension", "Content": "Description\nField to control whether or not an extension change is enabled for the current element for the START or END of the GENSEC.\nDistance proportion of the calculated difference between the reference HVAC duct and the HVAC being supported in the model that is used to offset the current element. For example, if a 300mm x 300mm HVAC is supported, the difference is 300mm - 500mm = -200mm and bar positions will need to move to suit the smaller duct.\nExample\nTRUE\n0.5\n\nEnable START/END Extension\nProportion of difference from Reference Duct\nDescription\nField to control whether or not an extension change is enabled for the current element for the START or END of the GENSEC.\nDistance proportion of the calculated difference between the reference HVAC duct and the HVAC being supported in the model that is used to offset the current element. For example, if a 300mm x 300mm HVAC is supported, the difference is 300mm - 500mm = -200mm and bar positions will need to move to suit the smaller duct.\nExample\nTRUE\n0.5\n\n\n\nEnable START/END Extension\nProportion of difference from Reference Duct\nDescription\nExample"}
{"Headers": "Example: Add a Support Bar at the Datum", "Content": "\nWhen adding a framework bar to the template, note that the bar must be named with the convention <template STRU name> -BAR- <incremented bar number>\nThe :MDSConfigA UDA is set as:\n\n\n"}
{"Headers": "Element Positioning", "Content": "Value\nFALSE\n\n\n\nDescription\nNo relative positioning required.\nNo value required.\nNo value required.\nNo value required.\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nValue\nFALSE\nDescription\nNo relative positioning required.\nNo value required.\nNo value required.\nNo value required.\n\n\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nValue\nDescription"}
{"Headers": "GENSEC START Extension", "Content": "Value\nTRUE\n0.5\nDescription\nGENSEC start extension is required.\nBar start is extended by 0.5 x (500 - HVAC width).\n\nEnable START extension\nProportion of difference from Reference Duct\nValue\nTRUE\n0.5\nDescription\nGENSEC start extension is required.\nBar start is extended by 0.5 x (500 - HVAC width).\n\n\n\nEnable START extension\nProportion of difference from Reference Duct\nValue\nDescription"}
{"Headers": "GENSEC END Extension", "Content": "Value\nTRUE\n0.5\nDescription\nGENSEC end extension is required.\nBar end is extended by 0.5 x (500 - HVAC width).\nThe overview of the setup for the bar is that no relative position change is required when the bar is created as the bar is always the same position relative to the datum. However, the start and end of the bar must be extended relative to the width of the duct that the framework is created against.\nEnable END extension\nProportion of difference from reference duct\nValue\nTRUE\n0.5\nDescription\nGENSEC end extension is required.\nBar end is extended by 0.5 x (500 - HVAC width).\n\n\n\nEnable END extension\nProportion of difference from reference duct\nValue\nDescription"}
{"Headers": "Example: Add a Bar above the HVAC", "Content": "\nIn this case, relative positioning of the bar must be enabled as it is affected by any height changes to the duct. GENSEC start and end extensions are the same as bar 1.\nThe configuration is:\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nValue\nTRUE\nU\n1\nHEIGHT\nDescription\nRelative positioning required.\nOffsets are in the UP direction, relative to STRU orientation.\nBar is offset by 1 x (500 - HVAC dimension in relative direction, for example, HEIGHT).\nThe HVAC dimension that is compared against the reference.\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nValue\nTRUE\nU\n1\nHEIGHT\nDescription\nRelative positioning required.\nOffsets are in the UP direction, relative to STRU orientation.\nBar is offset by 1 x (500 - HVAC dimension in relative direction, for example, HEIGHT).\nThe HVAC dimension that is compared against the reference.\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nValue\nTRUE\nU\n1\nHEIGHT\nDescription\nRelative positioning required.\nOffsets are in the UP direction, relative to STRU orientation.\nBar is offset by 1 x (500 - HVAC dimension in relative direction, for example, HEIGHT).\nThe HVAC dimension that is compared against the reference.\n\n\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nValue\nDescription"}
{"Headers": "Example: Add a Vertical Bar to the Framework", "Content": "\nWhen adding a vertical bar to the template, note that the vertical bar must be named with the convention <template STRU name> -V<incremented bar number>. In this case, relative positioning of the vertical bar must be enabled as it is affected by any width changes to the duct. Relative extension of the GENSEC end is required but no extension of the START is required.\nThe configuration is:\n\n\n"}
{"Headers": "Element Positioning", "Content": "Value\nTRUE\nW\n0.5\nWIDTH\nDescription\nRelative positioning required.\nOffsets are in the WEST direction, relative to STRU orientation.\nBar is offset by 0.5 x (500 - HVAC dimension in relative direction, for example, WIDTH).\nThe HVAC dimension that is compared against the reference.\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nValue\nTRUE\nW\n0.5\nWIDTH\nDescription\nRelative positioning required.\nOffsets are in the WEST direction, relative to STRU orientation.\nBar is offset by 0.5 x (500 - HVAC dimension in relative direction, for example, WIDTH).\nThe HVAC dimension that is compared against the reference.\n\n\n\nValue\nDescription"}
{"Headers": "GENSEC END Extension", "Content": "Value\nTRUE\n1\nDescription\nGENSEC end extension is required.\nBar end is extended by 1 x (500 - HVAC height).\n\nEnable END Extension\nProportion of difference from Reference Duct\nValue\nTRUE\n1\nDescription\nGENSEC end extension is required.\nBar end is extended by 1 x (500 - HVAC height).\n\n\n\nEnable END Extension\nProportion of difference from Reference Duct\nValue\nDescription"}
{"Headers": "Example: Add a Guide Bar to the Framework", "Content": "\nThe bar requires relative positioning changes to two axes where both height and width differences occur. Both the :MDSConfigA and :MDSConfigB UDAs are used. :MDSConfigA controls the width positioning of the bar and :MDSConfigB controls the height positioning. No bar extension changes are required in this case.\nThe configuration is:\n\n\n"}
{"Headers": "Element Positioning :MDSConfigA", "Content": "Value\nTRUE\nW\n0.5\nWIDTH\nDescription\nRelative positioning required.\nOffsets are in the WEST direction, relative to STRU orientation.\nBar is offset by 0.5 x (500 - HVAC dimension in relative direction, for example, WIDTH).\nThe HVAC dimension that is compared against the reference.\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nValue\nTRUE\nW\n0.5\nWIDTH\nDescription\nRelative positioning required.\nOffsets are in the WEST direction, relative to STRU orientation.\nBar is offset by 0.5 x (500 - HVAC dimension in relative direction, for example, WIDTH).\nThe HVAC dimension that is compared against the reference.\n\n\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nValue\nDescription"}
{"Headers": "Element Positioning :MDSConfigB", "Content": "Value\nTRUE\nU\n1\nHEIGHT\nDescription\nRelative positioning required.\nOffsets are in the UP direction relative to STRU orientation.\nBar is offset by 1 x (500 - HVAC dimension in relative direction, for example, HEIGHT).\nThe HVAC dimension that is compared against the reference.\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from reference duct\nHVAC Relative dimension\nValue\nTRUE\nU\n1\nHEIGHT\nDescription\nRelative positioning required.\nOffsets are in the UP direction relative to STRU orientation.\nBar is offset by 1 x (500 - HVAC dimension in relative direction, for example, HEIGHT).\nThe HVAC dimension that is compared against the reference.\n\n\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from reference duct\nHVAC Relative dimension\nValue\nDescription"}
{"Headers": "Example: Add a Lining to the Framework", "Content": "\nThe lining is built from the following element hierarchy.\n\nIt is possible to apply relative position changes to the SUBS, EXTR and VERT elements in the hierarchy. There is no need to consider changes occurring as a result of height difference because the liner is located under the datum of the duct being supported. Differences in width must be accounted for. Each vertex of the liner must be configured to move relative to any difference in width. Vertexes 1 and 4 must respond to width changes in the west direction and vertexes 2 and 3 must move in the east direction.\nNote:\nAdditional bars have been added and BAR 1 has been shifted down to allow for the liner thickness. These processes are not documented in this example.\n\n\n\nNote\n:"}
{"Headers": "Element Positioning: Vertex 1 and Vertex 4", "Content": "The configuration is:\nValue\nTRUE\nW\n0.5\nWIDTH\nDescription\nRelative positioning required.\nOffsets are in the WEST direction, relative to STRU orientation.\nBar is offset by 0.5 x (500 - HVAC dimension in relative direction, for example, WIDTH).\nThe HVAC dimension that is compared against the reference.\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nValue\nTRUE\nW\n0.5\nWIDTH\nDescription\nRelative positioning required.\nOffsets are in the WEST direction, relative to STRU orientation.\nBar is offset by 0.5 x (500 - HVAC dimension in relative direction, for example, WIDTH).\nThe HVAC dimension that is compared against the reference.\n\n\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative Dimension\nValue\nDescription"}
{"Headers": "Element Positioning: Vertex 2 and Vertex 3", "Content": "The configuration is:\nValue\nTRUE\nE\n0.5\nWIDTH\nDescription\nRelative positioning required.\nOffsets are in the EAST direction, relative to STRU orientation.\nBar is offset by 0.5 x (500 - HVAC dimension in relative direction, for example, WIDTH).\nThe HVAC dimension that is compared against the reference.\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative dimension\nValue\nTRUE\nE\n0.5\nWIDTH\nDescription\nRelative positioning required.\nOffsets are in the EAST direction, relative to STRU orientation.\nBar is offset by 0.5 x (500 - HVAC dimension in relative direction, for example, WIDTH).\nThe HVAC dimension that is compared against the reference.\n\n\n\nEnable Relative Element Positioning\nMove Direction\nProportion of difference from Reference Duct\nHVAC Relative dimension\nValue\nDescription"}
{"Headers": "Supports Automatic Drawing Production", "Content": "The Area Based ADP can be configured for use with supports. The use of supports ADP is explained. Refer to Supports Automatic Drawing Production for further information.\nNote:\nThe ABA defaults can also be changed by the supports user.\n\n\n\nSupports Automatic Drawing Production\nSupports Automatic Drawing Production\nNote\n:"}
{"Headers": "Supports ABA Defaults", "Content": "The ABA Defaults window allows you to define the Supports ABA defaults in the Draw application.\n\nThe ABA Defaults window can be used to:\nYour project can be organized in a way that different disciplines use different ABA libraries; the defaults file for supports ABA drawings is:\nStandard ABA Libraries are used, where available, with specific supports area and template libraries.\nTo select a different defaults file to that initially loaded, enter the name of the file in the Defaults File field and press Enter. The values held in the defaults file display on the ABA Defaults window. Alternatively, click Defaults File to browse to and select the required ABA defaults file.\nDRA-MDS-ABA-DEFAULTS\nDefine the ABA data structure\nModify the ABA data structure\nSet file locations for log files and batch files\nSet the batch user configuration\nInput text (data) files and supplied template data files\nDefine the ABA data structure\nDefine the ABA data structure\nModify the ABA data structure\nModify the ABA data structure\nSet file locations for log files and batch files\nSet file locations for log files and batch files\nSet the batch user configuration\nSet the batch user configuration\nInput text (data) files and supplied template data files\nInput text (data) files and supplied template data files\n\n\n\nABA Defaults\nDraw\nEnter\nABA Defaults\nDefaults File"}
{"Headers": "Dimension Customization", "Content": "Controls the default representation of support dimensions.\nThe DimensionControlDesigner.exe tool allows you to customize existing supports and add new supports to the application. The tool is installed into the AVEVA E3D Design installation directory.\n\nThe Dimension Control Designer window allows you to apply custom configuration to support dimensions.\nTo open the SupportsConfiguration.xml file, click File and select Open from the drop-down menu. The left hand part of the Dimension Control Designer window displays the content of the SupportConfiguration.xml which is located in the AVEVA E3D Design installation directory. You can modify the xml text directly.\nThe bottom part of the Dimension Control Designer window displays errors and warnings for the XML file.\nThe file location displays in the status bar.\nA simplified version of the SupportConfiguration.xml is:\nThe Mappings part of the SupportConfiguration.xml displays all of the configured supports. The example displays one support identified as FT09. The support is configured by a representation of the same name. Multiple supports can use the same representation.\nThe Representation part of the SupportConfiguration.xml displays the filename of the image file used for the support and each of the specified dimension nodes.\nEach representation contains an image, the standard images supplied with AVEVA E3D Design do not require a file extension. To apply a custom png image, the image must be located in the custom support configuration directory, and the file name specified in the Image id attribute.\nIn the example, the mycustomsupport.png is located in the same directory as the SupportConfiguration.xml.\nIn the example, the mycustomsupport.png is located in a subdirectory named myPngImages.\nThe dimension nodes can be configured to have as many dimensions as required. For example:\nThe dimension nodes can be configured to display a specified number of decimal places. The example specifies three decimal places.\nThe dimension nodes are then accessed via the GetDimensionById and SetDimensionById api calls. For example:\nThe dimension node x and y values indicate the centre point position of the dimension box within the control, defined as a decimal value. For example a position of x=\"0.5\" and y=\"0.5\" positions the centre point of the dimension box directly in the centre of the control. Valid values are from 0.0 to 1.0.\nYou can also configure the size of the dimension boxes. The default size is 54 pixels. The example positions the dimension1 text box directly in the centre of the control, with a width of 100 pixels.\nThe dimension type can also be configured. The default dimension type is distance. The example defines the dimension type as an angle.\n<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n<DimensionControlConfiguration id=\"Aveva.Supports.Presentation.DimensionControl\">\n  <Mappings>\n    <Mapping name=\"FT09\" representationId=\"ft09\"/>\n  </Mappings>\n  <Representations>\n    <Representation id=\"ft09\">\n      <Image id=\"ft09_dim\" />\n      <Dimension id=\"dimension3\" x=\"0.1\" y=\"0.3\" />\n      <Dimension id=\"dimension2\" x=\"0.41\" y=\"0.73\" size=\"35\"/>\n      <Dimension id=\"dimension1\" x=\"0.5\" y=\"0.82\"/>\n      <Dimension id=\"dimension4\" x=\"0.9\" y=\"0.3\"/>\n      <Dimension id=\"distance\" x=\"0.5\" y=\"0.95\" size=\"80\"/>\n      <Dimension id=\"anAngle\" x=\"0.5\" y=\"0.95\" type=\"angle\"/>\n    </Representation>\n  </Representations>\n</Supports>\n<Image id=\"mycustomsupport.png\" />\n<Image id=\"myPngImages\\mycustomsupport.png\" />\n<Dimension id=\"aSpecialDimension\" x=\"0.1\" y=\"0.3\" />\n<Dimension id=\"hei\" x=\"0.19\" y=\"0.50\" dp=\"3\" />\nGetDimensionById('aSpecialDimension')\n<Dimension id=\"dimension1\" x=\"0.5\" y=\"0.5\" size=\"100\" />\n<Dimension id=\"anAngle\" x=\"0.5\" y=\"0.95\" type=\"angle\"/>\n\n\n\nAVEVA E3D Design\nDimension Control Designer\nFile\nOpen\nDimension Control Designer\nAVEVA E3D Design\nDesigner\nMappings\nRepresentation\nAVEVA E3D Design"}
{"Headers": "File", "Content": "The File part of the Dimension Control Designer window allows you to open and save a SupportConfiguration.xml file and close the DimensionControlDesigner.exe tool. Click File to display a drop-down menu.\n\nOpen\nSelect from the drop-down menu to open an existing SupportConfiguration.xml file.\nSave\nSelect from the drop-down menu to save an existing SupportConfiguration.xml file.\nSave As\nSelect from the drop-down menu to save an existing SupportConfiguration.xml file with a new filename.\nRevert to Saved Version\nSelect from the drop-down menu to revert the current SupportConfiguration.xml file at the point when it was last saved.\nExit\nClick to close the DimensionControlDesigner.exe tool.\nOpen\nSelect from the drop-down menu to open an existing SupportConfiguration.xml file.\nSave\nSelect from the drop-down menu to save an existing SupportConfiguration.xml file.\nSave As\nSelect from the drop-down menu to save an existing SupportConfiguration.xml file with a new filename.\nRevert to Saved Version\nSelect from the drop-down menu to revert the current SupportConfiguration.xml file at the point when it was last saved.\nExit\nClick to close the DimensionControlDesigner.exe tool.\n\nOpen\nSelect from the drop-down menu to open an existing SupportConfiguration.xml file.\nSave\nSelect from the drop-down menu to save an existing SupportConfiguration.xml file.\nSave As\nSelect from the drop-down menu to save an existing SupportConfiguration.xml file with a new filename.\nRevert to Saved Version\nSelect from the drop-down menu to revert the current SupportConfiguration.xml file at the point when it was last saved.\nExit\nClick to close the DimensionControlDesigner.exe tool.\n\n\n\nFile\nDimension Control Designer\nFile\nOpen\nSave\nSave As\nRevert to Saved Version\nExit"}
{"Headers": "Navigate", "Content": "The Navigate part of the Dimension Control Designer window allows you to display a specific part of the SupportConfiguration.xml file. Click Navigate to display a drop-down menu.\n\nCurrent Representation\nSelect from the drop-down menu to display the representation for the currently selected support in the left hand part of the window.\nCurrent Dimension Box\nSelect from the drop-down menu to display the details of the currently selected dimension box in the left hand part of the window.\nCurrent Mapping\nSelect from the drop-down menu to display the mapping for the currently selected support in the left hand part of the window.\nCurrent Representation\nSelect from the drop-down menu to display the representation for the currently selected support in the left hand part of the window.\nCurrent Dimension Box\nSelect from the drop-down menu to display the details of the currently selected dimension box in the left hand part of the window.\nCurrent Mapping\nSelect from the drop-down menu to display the mapping for the currently selected support in the left hand part of the window.\n\nCurrent Representation\nSelect from the drop-down menu to display the representation for the currently selected support in the left hand part of the window.\nCurrent Dimension Box\nSelect from the drop-down menu to display the details of the currently selected dimension box in the left hand part of the window.\nCurrent Mapping\nSelect from the drop-down menu to display the mapping for the currently selected support in the left hand part of the window.\n\n\n\nNavigate\nDimension Control Designer\nNavigate\nCurrent Representation\nCurrent Dimension Box\nCurrent Mapping"}
{"Headers": "Create a Support", "Content": "The Create Support part of the Dimension Control Designer window allows you to create a support from new or using an existing Support.\n\nSupport Name\nInput a name for the support in the field.\nCreate New Representation\nSelect the option button to create a new support mapping and representation. By default the representation name is the same as the support name. If a clash occurs, a unique name is used.\nUse Existing Representation\nSelect the option button to create a new support mapping and representation from an existing support.\nYou must select the existing support to use as a basis for the new support from the drop-down list.\nSupport Name\nInput a name for the support in the field.\nCreate New Representation\nSelect the option button to create a new support mapping and representation. By default the representation name is the same as the support name. If a clash occurs, a unique name is used.\nUse Existing Representation\nSelect the option button to create a new support mapping and representation from an existing support.\nYou must select the existing support to use as a basis for the new support from the drop-down list.\n\nSupport Name\nInput a name for the support in the field.\nCreate New Representation\nSelect the option button to create a new support mapping and representation. By default the representation name is the same as the support name. If a clash occurs, a unique name is used.\nUse Existing Representation\nSelect the option button to create a new support mapping and representation from an existing support.\nYou must select the existing support to use as a basis for the new support from the drop-down list.\n\n\n\nCreate Support\nDimension Control Designer\nSupport Name\nCreate New Representation\nUse Existing Representation"}
{"Headers": "Current Support", "Content": "The Current Support part of the Dimension Control Designer window allows you to select, preview and modify the currently selected support.\n\nCurrent Support\nSelect a support from the drop-down list. The currently selected support displays in the preview and the left hand part of the Dimension Control Designer window.\nClick to display the previous support in the preview and the left hand part of the Dimension Control Designer window.\nClick to display the next support in the preview and the left hand part of the Dimension Control Designer window.\nClick to update the support preview.\nPreview\nDisplays a preview of the currently selected support. You can modify the position of a dimension box using the arrow keys on the keyboard. By default, the xml code is updated.\nAdd Dimension\nInput a valid dimension box value and click Add to create a new dimension box. For example:\n<Dimension id=\"\nx=\"0.5\" y=\"0.95\" />\nCurrent Support\nSelect a support from the drop-down list. The currently selected support displays in the preview and the left hand part of the Dimension Control Designer window.\n\nClick to display the previous support in the preview and the left hand part of the Dimension Control Designer window.\n\nClick to display the next support in the preview and the left hand part of the Dimension Control Designer window.\n\nClick to update the support preview.\nPreview\nDisplays a preview of the currently selected support. You can modify the position of a dimension box using the arrow keys on the keyboard. By default, the xml code is updated.\nAdd Dimension\nInput a valid dimension box value and click Add to create a new dimension box. For example:\n\nCurrent Support\nSelect a support from the drop-down list. The currently selected support displays in the preview and the left hand part of the Dimension Control Designer window.\nClick to display the previous support in the preview and the left hand part of the Dimension Control Designer window.\nClick to display the next support in the preview and the left hand part of the Dimension Control Designer window.\nClick to update the support preview.\nPreview\nDisplays a preview of the currently selected support. You can modify the position of a dimension box using the arrow keys on the keyboard. By default, the xml code is updated.\nAdd Dimension\nInput a valid dimension box value and click Add to create a new dimension box. For example:\n<Dimension id=\"\nx=\"0.5\" y=\"0.95\" />\n<Dimension id=\"\nx=\"0.5\" y=\"0.95\" />\n\n\n\nCurrent Support\nDimension Control Designer\nCurrent Support\nDimension Control Designer\nDimension Control Designer\nDimension Control Designer\nPreview\nAdd Dimension\nAdd"}
{"Headers": "Default Support Configuration File", "Content": "You can modify the location of the default SupportConfiguration.xml used when AVEVA E3D Design is opened. You must locate and open the evars.init file. The Environment variable must be modified to locate the new SupportConfiguration.xml file.\nFor example, if the location of the SupportConfiguration.xml file is C:\\MDS, the evars.init must be updated to read:\n\n\n\nAVEVA E3D Design"}
{"Headers": "Special Cases", "Content": "In some of the cases, support ancillaries can be separated into multiple sub-configurations (for example, A,B,C,D) within the SupportConfiguration.xml file. It is important to ensure that any MDU based copies of such standards adhere to the naming convention of the original. For example, if a copy of AT145 is made to AT690, additional representations of AT690A and AT690B must be created in the supports configuration file because AT145 has an A and B representation.\n<Mapping name=\"AT145A\" representationId=\"at03\"/>\n<Mapping name=\"AT690A\" representationId=\"at03\"/>\n<Mapping name=\"AT510A\" representationId=\"at03\"/>\n<Mapping name=\"AT697A\" representationId=\"at03\"/>\n<Mapping name=\"AT145B\" representationId=\"at140\"/>\n<Mapping name=\"AT690B\" representationId=\"at140\"/>\n\n\n"}
{"Headers": "Overview of the Supports Application", "Content": "The Supports application allows you to create standard supports for pipework, cable trays, (both piping based cable trays (BRAN) and cable trays (CTRAY) created by the cabling system) and HVAC. The application is highly interactive, enabling you to design supports with the minimum of effort. It is also highly configurable allowing the administrator to define project-related defaults to control the design of supports and to determine the range and types of ancillary support components that can be used on the project.\nThe standard supports in this application, which are designed using structural sections, are template-driven. A default set of structural templates based on British Standard Steelwork Sections is supplied with the application. All of these templates can be configured to suit the needs of an office or project to adopt a relevant national standard for steelwork sections.\n\n\n"}
{"Headers": "Administrator\u2019s Role", "Content": "The administrator is responsible for initial setup of the supports defaults in the DATASETS stored in AVEVA Catalog, the default files associated with the Supports application (refer to the Supports Administrator Guide for further information) and setup of the structural steel sizes associated with the framework templates. The Supports application is supplied with a British Steel set of framework templates, which the administrator can modify to suit the specific requirements of the project.\n\n\n\nSupports Administrator Guide"}
{"Headers": "Support Catalogs and Specifications", "Content": "The Supports application is supplied with a catalog and specification. The range of bore and components in the catalog are fixed and should be adequate for all projects. The catalog supplied and associated \u2018/MDS\u2019 specification must not be modified by the administrator or any other user.\n\n\n"}
{"Headers": "Area Based ADP (Draw Users)", "Content": "The only functionality a normal Draw user has within the Area Based ADP application is the ability to create drawings using administrative elements previously defined by the administrator. For example, templates and tasks. If any of the components covered in this user guide do not exist, consult the administrator. You can view the ABA defaults. Refer to Supports ABA Defaults for further information.\n\n\n\nSupports ABA Defaults\nDraw\nSupports ABA Defaults"}
{"Headers": "Create Supports ABA Drawing", "Content": "Creates supports ABA drawings by selecting the supports to be drawn and the template used. Additional functionality is available to view existing supports ABA drawings and the stored log files that are generated when drawings are created.\n\nThe Load Supports drop-down menu allows you to define the available supports for drawing.\n\nCE & Below\nSelect from the drop-down menu to populate the list of frameworks, hangers, ancillaries and lighting supports with all supports below the current element, including the support the current element belongs to.\nAll in MDB\nSelect from the drop-down menu to populate the list of frameworks, hangers, ancillaries and lighting supports with all supports in the current database.\nDrawing Registry\nSelect the drawing registry to write the drawing to.\nClick CE to select the current registry element on the Draw Explorer.\nFrameworks\nSelect the framework elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Frames check box to select all of the frameworks in the list.\nHangers\nSelect the hanger elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Hangers check box to select all of the hangers in the list.\nAncillaries\nSelect the ancillary elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Ancillaries check box to select all of the ancillaries in the list.\nLighting Supports\nSelect the lighting support elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Light supports check box to select all of the lighting supports in the list.\nSelection Filter\nAllows you to restrict the supports that display in the list of frameworks, hangers, ancillaries and lighting supports to names containing given characters. By default, the list displays all elements of the given type, as indicated by the * in the field. The wildcards you can use are:\n* Any number of any characters\n? Single character\nA logical expression can be used to filter on any attribute data available on the support. For example:\nA wildcard string to match by name.\n*011*\nAn expression to match by a UDA value.\n(attrib :SafetyRating gt 6)\nAn expression to match by a Status Control value.\n(attrib STVDSC( /SupportStatus ) eq 'Approved')\nTemplate\nSelect an ABA template from the drop-down list.\nUpdate\nSelect the option button to update the design graphics, tagging, and any tasks assigned to the template. No layers are deleted through this process, allowing you to add 2D layer elements if required.\nRegenerate\nSelect the option button to regenerate the design graphics, tagging, and any tasks assigned to the template. The drawing is effectively deleted and re-created. Regenerate can be used if a new drawing is required without additions (for example 2D layers).\nDelete\nClick to delete the currently selected drawlist.\nExisting Drawings\nAllows you to view existing drawings. Click to display the ABA Browse Sheets window. Refer to ABA Browse Sheets for further information.\nStored LogFiles\nAllows you to view the run time logfiles. Click to display the File Browser window. Refer to File Browser for further information.\nDetail Sheets\nSelect the check box to create steelwork shop detail drawings.\nCE & Below\nSelect from the drop-down menu to populate the list of frameworks, hangers, ancillaries and lighting supports with all supports below the current element, including the support the current element belongs to.\nAll in MDB\nSelect from the drop-down menu to populate the list of frameworks, hangers, ancillaries and lighting supports with all supports in the current database.\nDrawing Registry\nSelect the drawing registry to write the drawing to.\nClick CE to select the current registry element on the Draw Explorer.\nFrameworks\nSelect the framework elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Frames check box to select all of the frameworks in the list.\nHangers\nSelect the hanger elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Hangers check box to select all of the hangers in the list.\nAncillaries\nSelect the ancillary elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Ancillaries check box to select all of the ancillaries in the list.\nLighting Supports\nSelect the lighting support elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Light supports check box to select all of the lighting supports in the list.\nSelection Filter\nAllows you to restrict the supports that display in the list of frameworks, hangers, ancillaries and lighting supports to names containing given characters. By default, the list displays all elements of the given type, as indicated by the * in the field. The wildcards you can use are:\nA logical expression can be used to filter on any attribute data available on the support. For example:\nTemplate\nSelect an ABA template from the drop-down list.\nUpdate\nSelect the option button to update the design graphics, tagging, and any tasks assigned to the template. No layers are deleted through this process, allowing you to add 2D layer elements if required.\nRegenerate\nSelect the option button to regenerate the design graphics, tagging, and any tasks assigned to the template. The drawing is effectively deleted and re-created. Regenerate can be used if a new drawing is required without additions (for example 2D layers).\nDelete\nClick to delete the currently selected drawlist.\nExisting Drawings\nAllows you to view existing drawings. Click to display the ABA Browse Sheets window. Refer to ABA Browse Sheets for further information.\nStored LogFiles\nAllows you to view the run time logfiles. Click to display the File Browser window. Refer to File Browser for further information.\nDetail Sheets\nSelect the check box to create steelwork shop detail drawings.\nClick Apply to create individual supports ABA drawings for each of the selected supports or Cancel to discard any changes and close the Create Supports Drawing window.\nThe supports ABA drawings are created.\n\nA drawing is created together with sheet and library elements and displays in the Draw Explorer.\n\nCE & Below\nSelect from the drop-down menu to populate the list of frameworks, hangers, ancillaries and lighting supports with all supports below the current element, including the support the current element belongs to.\nAll in MDB\nSelect from the drop-down menu to populate the list of frameworks, hangers, ancillaries and lighting supports with all supports in the current database.\nDrawing Registry\nSelect the drawing registry to write the drawing to.\nClick CE to select the current registry element on the Draw Explorer.\nFrameworks\nSelect the framework elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Frames check box to select all of the frameworks in the list.\nHangers\nSelect the hanger elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Hangers check box to select all of the hangers in the list.\nAncillaries\nSelect the ancillary elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Ancillaries check box to select all of the ancillaries in the list.\nLighting Supports\nSelect the lighting support elements to include on the drawing.\nClick CE to select the current element on the drawing canvas or Model Explorer.\nSelect the All Light supports check box to select all of the lighting supports in the list.\nSelection Filter\nAllows you to restrict the supports that display in the list of frameworks, hangers, ancillaries and lighting supports to names containing given characters. By default, the list displays all elements of the given type, as indicated by the * in the field. The wildcards you can use are:\n* Any number of any characters\n? Single character\nA logical expression can be used to filter on any attribute data available on the support. For example:\nA wildcard string to match by name.\n*011*\nAn expression to match by a UDA value.\n(attrib :SafetyRating gt 6)\nAn expression to match by a Status Control value.\n(attrib STVDSC( /SupportStatus ) eq 'Approved')\nTemplate\nSelect an ABA template from the drop-down list.\nUpdate\nSelect the option button to update the design graphics, tagging, and any tasks assigned to the template. No layers are deleted through this process, allowing you to add 2D layer elements if required.\nRegenerate\nSelect the option button to regenerate the design graphics, tagging, and any tasks assigned to the template. The drawing is effectively deleted and re-created. Regenerate can be used if a new drawing is required without additions (for example 2D layers).\nDelete\nClick to delete the currently selected drawlist.\nExisting Drawings\nAllows you to view existing drawings. Click to display the ABA Browse Sheets window. Refer to ABA Browse Sheets for further information.\nStored LogFiles\nAllows you to view the run time logfiles. Click to display the File Browser window. Refer to File Browser for further information.\nDetail Sheets\nSelect the check box to create steelwork shop detail drawings.\n* Any number of any characters\n? Single character\n* Any number of any characters\n* Any number of any characters\n? Single character\n? Single character\nA wildcard string to match by name.\nA wildcard string to match by name.\nA wildcard string to match by name.\nAn expression to match by a UDA value.\nAn expression to match by a UDA value.\nAn expression to match by a UDA value.\nAn expression to match by a Status Control value.\nAn expression to match by a Status Control value.\nAn expression to match by a Status Control value.\n\n\n\nABA Browse Sheets\nFile Browser\nCE & Below\nAll in MDB\nDrawing Registry\nCE\nFrameworks\nCE\nAll Frames\nHangers\nCE\nAll Hangers\nAncillaries\nCE\nAll Ancillaries\nLighting Supports\nCE\nAll Light supports\nSelection Filter\n*011*\n(attrib :SafetyRating gt 6)\n(attrib STVDSC( /SupportStatus ) eq 'Approved')\nTemplate\nUpdate\nRegenerate\nDelete\nExisting Drawings\nABA Browse Sheets\nABA Browse Sheets\nStored LogFiles\nFile Browser\nFile Browser\nDetail Sheets\nApply\nCancel\nCreate Supports Drawing"}
{"Headers": "User View", "Content": "Creates a user view on an existing supports ABA drawing.\nA user view is an additional view created by copying an existing view at a selected location on the existing drawing. The view is regenerated each time the supports ABA drawing is recreated, and the drawing creation process updates any Draw elements. For example dimensions and labels. The user view is recognized by setting the view attribute SpPurpose to USER. A user view can only be created from a valid supports ABA view, and not from an existing user view.\nYou are required to have sufficient working knowledge of Draw to make use of this functionality.\nYou can modify and position the user view as required. Attributes can be modified and view elements created or deleted.\nYou are prompted to Select element\nClick to identify an element on the existing view to be copied. By default, the Point Construction Option Form window displays which allows you to define the frame position for the user view. Refer to Define View Frame with Cursor for further information.\nYou are then prompted to Specify position\nInput values in the dimension fields and press Enter or click to identify the view position.\nThe user view is created as an exact copy of the original view at the specified location.\n\n\n\nDefine View Frame with Cursor\nDraw\nDraw\nSelect element\nPoint Construction Option Form\nDefine View Frame with Cursor\nSpecify position\nEnter"}
{"Headers": "Over View", "Content": "Creates an over view on an existing supports ABA drawing.\nAn over view is an additional view created by copying an existing view at the exact location of the original view.\nThe view is not regenerated each time the supports ABA drawing is recreated. The over view is recognized by setting the view attribute SpPurpose to USER. An over view can only be created from a valid supports ABA view, and not from an existing user view.\nAn over view only copies the support elements. For example, dimensions and labels are not copied.\nYou are prompted to Select element\nThe over view is created as an exact copy of the original view at the same location. An additional note inside parenthesis is added to the existing view title. For example, (Support shown in full detail for clarity).\nThe purpose of this type of view is to clarify the design of the support elements, For example, in a plan view, by drawing the support elements in full if they are obscured and drawn in 'hidden detail' representation below the main structural supporting steelwork members.\n\n\n\nSelect element"}
{"Headers": "Data Management Facilities", "Content": "A number of data management facilities are available for supports ABA drawings.\n\n\n"}
{"Headers": "Revision Control", "Content": "Records of drawings, as they are at a particular time, can be saved. These records are known as revisions. Revisions can subsequently be compared with each other or with the drawing in it\u2019s current state.\n\nThe MDS Revision Control window allows you to define revision information, create and delete revisions.\nCE\nClick to identify the currently selected element as the working element.\nName\nSelect from the drop-down list to define the revision. The drop-down list is empty until a revision is created.\nRevision\nInput a value in the field to define the revision.\nDescription\nInput a revision description in the field.\nBy\nInput a value in the field to identify the person that created the revision.\nDate\nSelect a revision date from the drop-down lists.\nChecked\nInput a value in the field to identify the person that checked the revision.\nApproved\nInput a value in the field to identify the person that approved the revision.\nNew Revision\nClick to create a new revision.\nDelete Revi\nClick to delete the currently selected revision.\nClear\nClick to clear the By, Checked and Approved fields.\nCE\nClick to identify the currently selected element as the working element.\nName\nSelect from the drop-down list to define the revision. The drop-down list is empty until a revision is created.\nRevision\nInput a value in the field to define the revision.\nDescription\nInput a revision description in the field.\nBy\nInput a value in the field to identify the person that created the revision.\nDate\nSelect a revision date from the drop-down lists.\nChecked\nInput a value in the field to identify the person that checked the revision.\nApproved\nInput a value in the field to identify the person that approved the revision.\nNew Revision\nClick to create a new revision.\nDelete Revi\nClick to delete the currently selected revision.\nClear\nClick to clear the By, Checked and Approved fields.\nClick Apply to update the revision information, the revision information displays on the drawing. Subsequent updates of drawings retain revision information.\nClick Cancel to discard any changes and close the Revision Control window.\n\nCE\nClick to identify the currently selected element as the working element.\nName\nSelect from the drop-down list to define the revision. The drop-down list is empty until a revision is created.\nRevision\nInput a value in the field to define the revision.\nDescription\nInput a revision description in the field.\nBy\nInput a value in the field to identify the person that created the revision.\nDate\nSelect a revision date from the drop-down lists.\nChecked\nInput a value in the field to identify the person that checked the revision.\nApproved\nInput a value in the field to identify the person that approved the revision.\nNew Revision\nClick to create a new revision.\nDelete Revi\nClick to delete the currently selected revision.\nClear\nClick to clear the By, Checked and Approved fields.\n\n\n\nCE\nName\nRevision\nDescription\nBy\nDate\nChecked\nApproved\nNew Revision\nDelete Revi\nClear\nBy\nChecked\nApproved\nApply\nCancel"}
{"Headers": "Layer Control", "Content": "Sets the layers for a supports ABA drawing.\n\nThe Supports Layer Control window allows you to view all of the layer elements and define the view display.\nView\nSelect a view from the drop-down list. By default, the list of available layers is populated with the view member elements.\nSelect the check box adjacent to the drop-down list to display the view on the supports ABA drawing.\nDeselect the check box adjacent to the drop-down list to remove the view from the supports ABA drawing display.\nLayer\nSelect a layer from the list. By default, the list of available layer members is populated with the layer member elements.\nLayer Members\nAllows you to define the display of layer member elements on the supports ABA drawing.\nSelect a layer member to remove it from the supports ABA drawing, the layer member is indicated as (Hidden) on the list of available layer members.\nRepeat the command to display the layer member on the supports ABA drawing.\nView\nSelect a view from the drop-down list. By default, the list of available layers is populated with the view member elements.\nSelect the check box adjacent to the drop-down list to display the view on the supports ABA drawing.\nDeselect the check box adjacent to the drop-down list to remove the view from the supports ABA drawing display.\nLayer\nSelect a layer from the list. By default, the list of available layer members is populated with the layer member elements.\nLayer Members\nAllows you to define the display of layer member elements on the supports ABA drawing.\nSelect a layer member to remove it from the supports ABA drawing, the layer member is indicated as (Hidden) on the list of available layer members.\nRepeat the command to display the layer member on the supports ABA drawing.\n\nTo modify the display of a layer, right-click a layer on the list of available layers to display a drop-down menu.\n\nThe available menu options display.\nShow All\nClick to display all of the members of the selected layer on the supports ABA drawing.\nHide All\nClick to remove all of the members of the selected layer from the supports ABA drawing.\nShow/Hide on selection\nAllows you to define the display of layer elements on the supports ABA drawing.\nSelect a layer to remove it from the supports ABA drawing, the layer is indicated as (Hidden) on the list of available layers.\nRepeat the command to display the layer on the supports ABA drawing.\nHide Layer by Cursor\nClick to remove a layer from the supports ABA drawing using a cursor pick.\nYou are prompted to Select element\nClick to identify an element, all of associated layer member elements are removed from the supports ABA drawing. The layer is indicated as (Hidden) on the list of available layers.\nShow All\nClick to display all of the members of the selected layer on the supports ABA drawing.\nHide All\nClick to remove all of the members of the selected layer from the supports ABA drawing.\nShow/Hide on selection\nAllows you to define the display of layer elements on the supports ABA drawing.\nSelect a layer to remove it from the supports ABA drawing, the layer is indicated as (Hidden) on the list of available layers.\nRepeat the command to display the layer on the supports ABA drawing.\nHide Layer by Cursor\nClick to remove a layer from the supports ABA drawing using a cursor pick.\nYou are prompted to Select element\nClick to identify an element, all of associated layer member elements are removed from the supports ABA drawing. The layer is indicated as (Hidden) on the list of available layers.\nTo modify the display of a layer member, right-click a layer member on the list of available layer members to display a drop-down menu.\n\nThe available menu options display.\nShow All\nClick to display all of the members of the selected layer on the supports ABA drawing.\nHide All\nClick to remove all of the members of the selected layer from the supports ABA drawing using a cursor pick.\nYou are prompted to Select element\nClick to identify an element, the layer members are removed from the supports ABA drawing. The layer members are indicated as (Hidden) on the list of available layers.\nHide Member by Cursor\nClick to remove a layer member from the supports ABA drawing using a cursor pick.\nYou are prompted to Select element\nClick to identify an element, the layer member is removed from the supports ABA drawing. The layer member is indicated as (Hidden) on the list of available layers.\nShow All\nClick to display all of the members of the selected layer on the supports ABA drawing.\nHide All\nClick to remove all of the members of the selected layer from the supports ABA drawing using a cursor pick.\nYou are prompted to Select element\nClick to identify an element, the layer members are removed from the supports ABA drawing. The layer members are indicated as (Hidden) on the list of available layers.\nHide Member by Cursor\nClick to remove a layer member from the supports ABA drawing using a cursor pick.\nYou are prompted to Select element\nClick to identify an element, the layer member is removed from the supports ABA drawing. The layer member is indicated as (Hidden) on the list of available layers.\nClick Cancel to close the Supports Layer Control window.\nView\nSelect a view from the drop-down list. By default, the list of available layers is populated with the view member elements.\nSelect the check box adjacent to the drop-down list to display the view on the supports ABA drawing.\nDeselect the check box adjacent to the drop-down list to remove the view from the supports ABA drawing display.\nLayer\nSelect a layer from the list. By default, the list of available layer members is populated with the layer member elements.\nLayer Members\nAllows you to define the display of layer member elements on the supports ABA drawing.\nSelect a layer member to remove it from the supports ABA drawing, the layer member is indicated as (Hidden) on the list of available layer members.\nRepeat the command to display the layer member on the supports ABA drawing.\nShow All\nClick to display all of the members of the selected layer on the supports ABA drawing.\nHide All\nClick to remove all of the members of the selected layer from the supports ABA drawing.\nShow/Hide on selection\nAllows you to define the display of layer elements on the supports ABA drawing.\nSelect a layer to remove it from the supports ABA drawing, the layer is indicated as (Hidden) on the list of available layers.\nRepeat the command to display the layer on the supports ABA drawing.\nHide Layer by Cursor\nClick to remove a layer from the supports ABA drawing using a cursor pick.\nYou are prompted to Select element\nClick to identify an element, all of associated layer member elements are removed from the supports ABA drawing. The layer is indicated as (Hidden) on the list of available layers.\nShow All\nClick to display all of the members of the selected layer on the supports ABA drawing.\nHide All\nClick to remove all of the members of the selected layer from the supports ABA drawing using a cursor pick.\nYou are prompted to Select element\nClick to identify an element, the layer members are removed from the supports ABA drawing. The layer members are indicated as (Hidden) on the list of available layers.\nHide Member by Cursor\nClick to remove a layer member from the supports ABA drawing using a cursor pick.\nYou are prompted to Select element\nClick to identify an element, the layer member is removed from the supports ABA drawing. The layer member is indicated as (Hidden) on the list of available layers.\n\n\n\nView\nLayer\nLayer Members\nShow All\nHide All\nShow/Hide on selection\nHide Layer by Cursor\nSelect element\nShow All\nHide All\nSelect element\nHide Member by Cursor\nSelect element\nCancel"}
{"Headers": "Drawing Lock", "Content": "Locks or unlocks a a supports ABA drawing.\n\nThe Modify Drawing Lock window allows you to lock or unlock a supports ABA drawing, preventing any further modifications.\nCE\nClick to identify the currently selected drawing element as the working element.\nThe drawing name and current lock status displays.\nSelect Lock Drawing from the drop-down list to lock the supports ABA drawing.\nSelect Unlock Drawing from the drop-down list to unlock the supports ABA drawing.\nCE\nClick to identify the currently selected drawing element as the working element.\nThe drawing name and current lock status displays.\n\nSelect Lock Drawing from the drop-down list to lock the supports ABA drawing.\nSelect Unlock Drawing from the drop-down list to unlock the supports ABA drawing.\nA locked drawing cannot be deleted or overwritten via the supports ABA drawing creation process, even if the support name is selected in the Create Supports Drawing window.\nYou can check the ABA log file, for example, %AVEVA_DESIGN_ABA_LOG%/Aba_7-June-07_10-52-36.log, for the list of supports ABA drawings successfully created or aborted. A typical ABA log file output is:\nCE\nClick to identify the currently selected drawing element as the working element.\nThe drawing name and current lock status displays.\nSelect Lock Drawing from the drop-down list to lock the supports ABA drawing.\nSelect Unlock Drawing from the drop-down list to unlock the supports ABA drawing.\n====================================\nABA Log File - Processing 1 Drawings\n====================================\nEntry for Drawing /MDS-ABA-3-VIEWS(METRIC)-PS01005-AREA (=23706/324,=22384/63420)\nEnd of Process List\nProcessing Drawing (1 of 1)\n-------------------------------------------------------------\n7 Jun 2007 10:52:37\nCannot delete old drawing /MDS-ABA-3-VIEWS(METRIC)-PS01005-AREA as it is locked - Drawing aborted\nDrawing (1 of 1) Processed\n-------------------------------------------------------------\nDraft run-time warnings:\n64,353)  0 elements with null or illegal IDNM attributes have been deleted. IDLIST\n         /MDS-ABA-3-VIEWS(METRIC)-PS01005-AREA/S1/V7/IDLIST/IDLI\n64,353)  0 elements with null or illegal DDNM attributes have been deleted. VIEW /MDS-ABA-3-VIEWS(METRIC)-PS01005-AREA/S1/V7\n64,353)  0 elements with null or illegal IDNM attributes have been deleted. VIEW /MDS-ABA-3-VIEWS(METRIC)-PS01005-AREA/S1/V7\nCannot delete old drawing /MDS-ABA-3-VIEWS(METRIC)-PS01005-AREA as it is locked - Drawing aborted\n\n\n\nModify Drawing Lock\nCE\nLock Drawing\nUnlock Drawing\nCreate Supports Drawing\n====================================\nABA Log File - Processing 1 Drawings\n====================================\nEntry for Drawing /\n-ABA-3-VIEWS(METRIC)-PS01005-AREA (=23706/324,=22384/63420)\nEnd of Process List\nProcessing Drawing (1 of 1)\n-------------------------------------------------------------\n7 Jun 2007 10:52:37\nCannot delete old drawing /\n-ABA-3-VIEWS(METRIC)-PS01005-AREA as it is locked - Drawing aborted\nDrawing (1 of 1) Processed\n-------------------------------------------------------------\nDraft run-time warnings:\n64,353)  0 elements with null or illegal IDNM attributes have been deleted. IDLIST\n         /\n-ABA-3-VIEWS(METRIC)-PS01005-AREA/S1/V7/IDLIST/IDLI\n64,353)  0 elements with null or illegal DDNM attributes have been deleted. VIEW /\n-ABA-3-VIEWS(METRIC)-PS01005-AREA/S1/V7\n64,353)  0 elements with null or illegal IDNM attributes have been deleted. VIEW /\n-ABA-3-VIEWS(METRIC)-PS01005-AREA/S1/V7\nCannot delete old drawing /\n-ABA-3-VIEWS(METRIC)-PS01005-AREA as it is locked - Drawing aborted"}
{"Headers": "Scale Override", "Content": "Overrides the scale calculated by DRAW to fit the support within the view and defines a scale to be used.\n\nThe sheet name displays at the top of the MDS Scale Override window.\nSelect a Scale from the drop-down list to define the scale of the view.\nClick OK to apply the scale override or Cancel to discard any changes and close the MDS Scale Override window.\n\n\n\nScale\nOK\nCancel"}
{"Headers": "Rescale Pipe Symbols", "Content": "Rescales pipe symbols to suit the VSCA view scale attribute.\nYou are prompted to Select element\nClick to identify an element, all pipe symbols are rescaled for the view associated with the selected element.\nNote:\nCurrently only two types of pipe symbols can be rescaled on supports ABA drawings. Both pipe symbols are represented by DRAW Symbol Label (SLAB) elements with the Template Reference (TMRF) attribute set to either /DRA/MAS/SYMBOLS/GEN/BREAKS/BB-1 or /MDS/ABA/TAGS/BREAK/PIPE.\n\n\n\nSelect element\nNote\n:"}
{"Headers": "Terrain Work Area", "Content": "Many features of the Terrain discipline user interface are common to multiple AVEVA E3D Design disciplines, mostly with the exception of the functionality available for selection on the Terrain tab.\n\nProject tab\nProvides access to a number of key commands and facilities, most of the functionality available for selection are common to multiple AVEVA E3D Design disciplines.\nTerrain tab\nIncludes the following functionality specific to the Terrain discipline:\nCreate\nModify\nDelete\nCreate\nCreate\nModify\nModify\nDelete\nDelete\nNote:\nThe Admin tab is only available for selection, if you a member of the ADMIN team.\n\n\n\nTerrain\nTerrain\nNote\n:\nAdmin\nProject tab\nTerrain tab\nTerrain"}
{"Headers": "Terrain Definition Model", "Content": "A Terrain Model in AVEVA E3D Design is a volumetric representation of a terrain surface, possibly with user-defined additions and/or subtractions, subdivided into a volumetric cell structure. The individual cells can contain different sets of contour line curves at user-defined elevations.\n\n\n\nTerrain"}
{"Headers": "Terrain Definition Model Hierarchy", "Content": "The Terrain Model World (TRNWLD) element contains the Terrain Definition Model, hence the geometry stored in this element is never considered by clash detection.\n\nAll database elements are owned by other elements, therefore elements must be created in a strict order.\nTRNWLD elements are administrative and can own a number of Terrain Definition (TRNDEF) and Terrain Surface (TRNSUR) elements. Below the TRNWLD element level the area specific elements are:\nTRNDEF\nThe Terrain Definition (TRNDEF) is a volume defined as a rectangular section from the Terrain, with a thickness added below the lowest point from the surface. More than one definition can be created for a single surface, allowing the Terrain to be split up. The definitions for one surface should not overlap.\nPositive and negative primitives can be defined to define changes to the terrain, these are added to the Terrain Definition when modifying it.\nTerrain Primitive Holder (TRNPRI), Terrain Restriction Rectangle (TRNRR) and Terrain Solid Primitive Holder (TRNSLD) elements are owned by TRNDEF elements.\nTRNDEF elements are linked to TRNSUR elements are linked by a property called SurLnk which is the reference to terrain surface. TRNDEF elements are also linked to TRNMOD elements by a property called DeflLnk which is the link to terrain definition.\nTRNPRI\nTRNPRI elements are owned by TRNDEF elements, these elements are container elements for primitives elements.\nThe TRNPRI elements has a property called the Terrain Definition Volume or Tvol. The volume is calculated by the solid described as the terrain surface with the bottom plane defined by the Bothei attribute and with the TRNRR element applied. The volume is calculated when the command GENTRM is used.\nTRNRR\nTRNRR elements are owned by TRBDEF elements, the rectangle is used to restrict the Terrain Definition Model.\nTRNSLD\nTRNSLD elements are owned by TRNDEF elements, the element contains the volumetric representation of the Terrain Definition Model.\nTRNSUR\nA terrain surface is imported and created by the IMP command. This is the same command that is used by the Mechanical Equipment Interface (MEI).\nThe following import formats are supported IGES, STEP, STL and XYZ. A terrain model in XYZ format is defined by a large number of points. These points are triangulated and a triangulated surface is created.\nAn imported terrain surface is defined by a TRNSUR element, a GENPRI element is used to hold the imported geometry.\nTRNMOD\nTRNMOD elements are administrative and are owned by a SITE or ZONE element. TRNMOD elements can own a number of Terrain Contour Line Collection (TRNCLC) and Terrain Cell Collection (TRNCC) elements.\nTRNCC\nTRNCC elements own Terrain Cell Element (TRNCEL).\nTRNCEL\nTRNCEL elements own Curve Collection Within a Cell (TRNCUC) elements.\nTRNCUC\nTRNCUC elements own Curve Set Within a Cell Element (TRNCUS) elements.\nTRNCUS\nTRNCUS elements own Terrain Curve (Trncurve) elements.\nTRNCLC\nTRNCLC elements own Set of Contour Lines (TRNCLS) elements.\nTRNCLS\nTRNCLS elements own Group of Contour Lines (TRNCLG) elements.\nRefer to Create Terrain Definition, Create Terrain Model and Create Terrain Surface for further information.\n\n\n\nCreate Terrain Definition\nCreate Terrain Model\nCreate Terrain Surface\nTRNDEF\nTerrain Definition\nTRNPRI\nTRNRR\nTRNSLD\nTRNSUR\nTRNMOD\nTRNCC\nTRNCEL\nTRNCUC\nTRNCUS\nTRNCLC\nTRNCLS\nCreate Terrain Definition\nCreate Terrain Model\nCreate Terrain Surface"}
{"Headers": "Create Terrain World", "Content": "Defines and creates a Terrain World (TRNWLD) element in the terrain hierarchy.\n\nIf autonaming is enabled, the suggested name can be accepted by clicking OK or a new name can be typed and then applied by clicking OK.\nNote:\nThe new Terrain World must be named.\n\n\n\nTerrain World\nOK\nOK\nNote\n:"}
{"Headers": "Create Terrain Surface", "Content": "Defines and creates a Terrain Surface (TRNSUR) element in the Terrain hierarchy.\n\nCreate Surface\nThe Terrain Surface is the whole reference surface imported from a file and has no thickness.\nTerrain World\nDisplays the currently selected Terrain World.\nThe Terrain World can be changed by selecting a different one in the hierarchy and clicking refresh .\nA Terrain World must be selected. If a Terrain World is not selected in the hierarchy an error message is displayed.\nImport File Name\nThe import file can be opened by clicking or typing the path manually. The Surface is named automatically from the file it is imported from.\nThe following file types can be imported:\nA terrain model in XYZ format is defined by a large number of points. These points are triangulated and a triangulated surface is created, this is computationally costly and may take longer to import than other file formats.\nAfter the file is selected, a graphical aid is displayed to show where in the Model the surface will be imported to. The position will be its raw coordinates from the file if the Datum Position is left at 0,0,0. If Datum Position is altered this allows the user to choose the position within the file that will be at the origin (0,0,0) in Model.\n\nAngle from North\nRotates the surface.\n\nDatum Position\nCreates the datum position for the Surface element, using the coordinates manually entered, using an offset or picked from the 3D view. These coordinates can then be locked.\nRefer to Create Terrain Definition, Create Terrain Model and Add Contours for further information.\nXYZ (.xyz)\nSTEP (.stp)\nSTL (.stl)\nIGES (.igs)\nXYZ (.xyz)\nXYZ (.xyz)\nSTEP (.stp)\nSTEP (.stp)\nSTL (.stl)\nSTL (.stl)\nIGES (.igs)\nIGES (.igs)\nNote:\nLarge files may take several minutes to import.\n\n\n\nCreate Terrain Definition\nCreate Terrain Model\nAdd Contours\nTerrain Surface\nTerrain\nCreate Surface\nTerrain World\nImport File Name\nNote\n:\nDatum Position\nCreate Terrain Definition\nCreate Terrain Model\nAdd Contours"}
{"Headers": "Create Terrain Definition", "Content": "Defines and creates a Terrain Definition (TRNDEF) element in the Terrain hierarchy.\n\nSurface\nDisplays the name of the surface being worked on.\nName\nIf autonaming is enabled, the suggested name can be accepted by clicking OK or a new name can be typed and then applied by clicking OK.\nBase Thickness\nEnter a value to add a thickness below the lowest point from the surface.\nPosition\nCreates the position for the Definition element, using the coordinates manually entered, using an offset or picked from the 3D view. These coordinates can then be locked.\nWidth/Length\nThe size of the Model to be created from the terrain definition and is set by entering a value for the Width and Length. The values define the restriction rectangle using graphical aids with dimensions on the sides of the rectangle for width and length.\n\nOnce the definition is created, click the next arrow. The definition is displayed as a volume.\n\nRefer to Create Terrain Surface, Create Terrain Model, Add Contours and Modify Terrain Definition for further information.\n\n\n\nCreate Terrain Surface\nCreate Terrain Model\nAdd Contours\nModify Terrain Definition\nTerrain Definition\nTerrain\nSurface\nName\nOK\nOK\nBase Thickness\nPosition\nWidth/Length\nWidth\nLength\nCreate Terrain Surface\nCreate Terrain Model\nAdd Contours\nModify Terrain Definition"}
{"Headers": "Create Terrain Model", "Content": "The Terrain Model (TRNMOD) is the physical clash-able element created under a Zone and generated from a Terrain definition.\nOptionally, a grid may be referenced. If a grid is referenced, the terrain model will be divided into cells using the unrestricted planes of the referenced grid as dividing planes, otherwise only one cell is generated.\n\nDefinition\nDisplays the name of the definition being worked on.\nName\nIf autonaming is enabled, the suggested name can be accepted by clicking OK or a new name can be typed and then applied by clicking OK.\nZone\nAny existing zone can be used.\nThe name of the zone can be typed or selected in the hierarchy and set by clicking Set Zone from Current Element .\nGrid\nAdd a grid from the drop down list containing all the grids found in the current MDB.\nRefer to Create Terrain Surface, Create Terrain Definition and Add Contours for further information.\nNote:\nAdding a grid is optional.\n\n\n\nCreate Terrain Surface\nCreate Terrain Definition\nAdd Contours\nTerrain Model\nTerrain\nDefinition\nName\nOK\nOK\nZone\nSet Zone from Current Element\nGrid\nNote\n:\nCreate Terrain Surface\nCreate Terrain Definition\nAdd Contours"}
{"Headers": "Add Contours", "Content": "Contours are added from a reference elevation up and down at spacings for the major and minor contours.\n\nMinor contour spacing must be a factor of the major contour spacing, for example, if major spacing is 10000mm, then a minor spacing of 2500mm is permitted, but a minor spacing of 4000mm is rejected. A warning message is displayed.\n\nClick Apply to create the contours.\n\nRefer to Create Terrain Surface, Create Terrain Definition, Create Terrain Model, Show All Contours, Show Major Contours, Show No Contours and Contour Annotations for further information.\nNote:\nAdding minor contours is optional.\n\n\n\nCreate Terrain Surface\nCreate Terrain Definition\nCreate Terrain Model\nShow All Contours\nShow Major Contours\nShow No Contours\nContour Annotations\nNote\n:\nApply\nCreate Terrain Surface\nCreate Terrain Definition\nCreate Terrain Model\nShow All Contours\nShow Major Contours\nShow No Contours\nContour Annotations"}
{"Headers": "Modify Terrain Surface", "Content": "Modify the currently selected surface element in the hierarchy, the functionality available is identical to that described in Surface.\n\nRefer to Create Terrain Surface for further information.\n\n\n\nCreate Terrain Surface\nCreate Terrain Surface"}
{"Headers": "Modify Terrain Definition", "Content": "Modify the currently selected definition element in the hierarchy, the majority of the functionality available is identical to that described in Definition.\n\nCreate Primitive\nWhen modifying the Definition, positive or negative primitives can be added using the buttons. When the Definition is updated, either by clicking Update Definition , or by clicking the next arrow, the updates are applied to the Definition and the Model if a model is defined for that Definition.\nThe Show Negatives check box toggles visualisation On or Off. When On the negatives can be seen before applying the changes.\nRefer to Create Terrain Definition for further information.\n\n\n\nCreate Terrain Definition\nCreate Primitive\nUpdate Definition\nShow Negatives\nOn\nOff\nOn\nCreate Terrain Definition"}
{"Headers": "Modify Terrain Model", "Content": "Modify the currently selected model element in the hierarchy, the functionality available is identical to that described in Model.\n\nRefer to Create Terrain Model for further information.\n\n\n\nCreate Terrain Model\nCreate Terrain Model"}
{"Headers": "Show All Contours", "Content": "Displays both the Major and Minor contour lines.\n\nRefer to Show Major Contours, Show No Contours and Add Contours for further information.\n\n\n\nShow Major Contours\nShow No Contours\nAdd Contours\nShow Major Contours\nShow No Contours\nAdd Contours"}
{"Headers": "Show Major Contours", "Content": "Displays only the Major contours lines.\n\nRefer to Show All Contours, Show No Contours and Add Contours for further information.\n\n\n\nShow All Contours\nShow No Contours\nAdd Contours\nShow All Contours\nShow No Contours\nAdd Contours"}
{"Headers": "Show No Contours", "Content": "No Contour lines are displayed.\n\nRefer to Show All Contours, Show Major Contours and Add Contours for further information.\n\n\n\nShow All Contours\nShow Major Contours\nAdd Contours\nShow All Contours\nShow Major Contours\nAdd Contours"}
{"Headers": "Contour Annotations", "Content": "Displays the Contour line annotations, if All Contours is selected, all the contours are displayed annotated.\n\nIf Major Contours Only is selected, only the Major contours are displayed annotated.\n\nIf No Contours is selected, then no annotations are displayed.\nRefer to Add Contours, Show All Contours, Show Major Contours and Show No Contours for information.\n\n\n\nAdd Contours\nShow All Contours\nShow Major Contours\nShow No Contours\nAll Contours\nMajor Contours Only\nNo Contours\nAdd Contours\nShow All Contours\nShow Major Contours\nShow No Contours"}
{"Headers": "Draw User guide", "Content": "The Draw User guide describes the facilities provided by Draw. Draw is used to generate fully annotated engineering drawings from design data.\nDRAW is the drawing production module of the AVEVA E3D Design platform. It allows you to generate fully annotated engineering drawings directly from data in the 3D model, created from the Model module. Drawings can be easily updated to reflect changes in the 3D model.\nWithin Draw there is specific functionality associated with the production of drawings.\nRefer to General Functions and Automatic Drawing Production for further information.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nGeneral Functions\nAutomatic Drawing Production\nGeneral Functions\nAutomatic Drawing Production"}
{"Headers": "General Functions", "Content": "The Draw graphical user interface has been designed to allow you to generate and retrieve industry-standard engineering drawings quickly and efficiently.\nDimensioning and other annotations can then be added. It is not necessary to make any calculations or input any data, as all annotation information comes directly from the 3D model.\n\n\n"}
{"Headers": "Drawing Creation", "Content": "You select the particular part of the 3D model and the direction and scale to use.\nThe 3D model can be viewed from any angle at any scale, including isometric views, with perspective if required. The appearance of the 3D graphics is controlled from representation rules that are pre-defined by the administrator allowing for different types of design items to have different line styles and colours applied to them. The required representation can be selected during view creation.\nVarious levels of wire-line and hidden-line removal can be used. Sectional views can be generated by the creation of flat or stepped section planes, and there are no restrictions on the number of planes created or the selection of items that can be sectioned. The scale of the 3D graphics can be selected from a set of Metric, Architectural and Engineering values, with the option of an automatic scale selection to use the largest scale possible for the given design data and drawing sheet size.\n\n\n"}
{"Headers": "Hierarchy", "Content": "Facilities are available for specifying details of the hierarchy within the DRAW database for the location of the drawings and their sheets.\n\n\n"}
{"Headers": "Labels", "Content": "Labels can be attached to any design element and used to display any attribute of the element. You can control the format, content and appearance of the labels, with suitable project defaults defined by the administrator. Direct reference to the design data, combined with a simple update annotation operation, means that the annotation always reflects the current state of the 3D model. The position and orientation of the labels can be modified graphically, for a clear drawing layout.\n\n\n"}
{"Headers": "Dimensions", "Content": "There are four generic dimension types available in Draw, namely, Linear, Angular, Radial and Pitch Circle Diameter. These allow intelligent dimensions to be created to dimensioning standards.\nDimensions are calculated directly from the 3D model. The format, content and appearance of the dimensions can be controlled. The administrator can define suitable project defaults.\nAs with labelling, direct reference to the design data means that the annotation always reflects the current state of the 3D model, with a simple update annotation operation.\nOnce the dimensions have been created, the position and orientation of dimensions can be adjusted graphically.\n\n\n"}
{"Headers": "2D Draft", "Content": "Draw's intelligent 2D drafting allows additional 2D annotation (manually drafted graphics and text) to be generated on the drawing sheet. Operations such as grouping, multiple copying, rubber banding, nested symbols, symbol libraries, and full element modification functions are available. The facility is not intended to be used as a drafting application.\nLike other Draw data, all 2D annotation can be linked to the design data and can easily be updated to follow the changes that occur in the 3D model.\n\n\n"}
{"Headers": "Automatic Drawing Production", "Content": "The Automatic Drawing Production (ADP) functionality enables annotated drawings to be produced automatically. You can set rules that determine how the annotation is produced. The drawings can then be modified, if necessary, using the normal drawing modification operations in Draw.\nThe functionality contains separate utilities, which are used for different disciplines. The utilities are:\nGeneral ADP\nSpool Drawings\nHVAC Sketches\nIsometric ADP\nArea Based ADP\nGeneral ADP\nGeneral ADP\nSpool Drawings\nSpool Drawings\nHVAC Sketches\nHVAC Sketches\nIsometric ADP\nIsometric ADP\nArea Based ADP\nArea Based ADP\n\n\n"}
{"Headers": "User Interface", "Content": "Many features of the Draw module user interface are common to multiple AVEVA E3D Design modules and are described in Common Functionality.\n\n\n\nCommon Functionality\nCommon Functionality\n."}
{"Headers": "Tabs", "Content": "The Draw interface includes the following tabs:\nIf a label, view (2D or 3D) or intelligent table is selected, a tab containing options specific to labels, views or intelligent tables displays:\nWhen Draw is opened, the Home tab displays initially.\n\n\nA further tab may display which contains options specific to the type of view (for example, 2D or 3D) and elements currently selected.\nIf required, the tabs, apart from their titles, can be hidden to save space.\n\nTo hide the tabs, right-click a tab and select Minimize the Ribbon from the drop-down menu, or double click the title of an open tab with the left mouse button.\nRepeat the procedure to re-display the tabs.\nProject\nHome\nDraw\nAnnotate\nUpdate\nTools\nInterfaces\nManage\nAuto\nArea\nProject\nProject\nHome\nHome\nDraw\nDraw\nAnnotate\nAnnotate\nUpdate\nUpdate\nTools\nTools\nInterfaces\nInterfaces\nManage\nManage\nAuto\nAuto\nArea\nArea\nFormat 2D View\nFormat 3D Tab\nLabel Format Tab\nIntelligent Table Tab\nFormat 2D View\nFormat 2D View\nFormat 3D Tab\nFormat 3D Tab\nLabel Format Tab\nLabel Format Tab\nIntelligent Table Tab\nIntelligent Table Tab\nNote:\nYou must be a free user or a member of the DRAWADMIN team to display the Admin tab. Refer to Draw Administrator for further information.\nNote:\nMany of the tabs contain drop-down lists, allowing you to select further options. In many cases, the Draw module displays the drop-down list function that was most recently selected.\nIn this User Guide, the default names of the drop-down lists are given - the first option on each menu.\n\n\n\nProject\nHome\nDraw\nAnnotate\nUpdate\nTools\nInterfaces\nManage\nAuto\nArea\nDraw Administrator\nFormat 2D View\nFormat 3D Tab\nLabel Format Tab\nProject\nHome\nDraw\nAnnotate\nUpdate\nTools\nInterfaces\nManage\nAuto\nArea\nNote\n:\nAdmin\nDraw Administrator\nFormat 2D View\nFormat 3D Tab\nLabel Format Tab\nIntelligent Table Tab\nHome\nMinimize the Ribbon\nNote\n:"}
{"Headers": "Project", "Content": "The Project tab provides access to a number of key commands and facilities.\n\nSave Work\nClick to save changes made to data in the Draw module. The facility is also available on the Quick Access Toolbar by default.\nGet Work\nClick to refresh the databases with changes made by other users since the session was started. The facility is also available on the Quick Access Toolbar by default.\nNew Drawing\nAllows you to create new drawing sheets, backing sheets, symbol templates and overlay sheets. Refer to Create Drawing Sheet from a Drawing Type and Template for further information.\nPrint Drawing\nAllows you to set the printing options and print drawing sheets. Refer to Print Sheets for further information.\nExport Drawing\nAllows you to export drawings sheets to other file formats. Refer to Output Facilities for further information.\nHelp\nClick to open the support and information page, which displays general information about the product (for example, the software version). You can access Online Help, facilities to contact AVEVA and check for software updates. Refer to On-Line Help for further information.\nOptions\nAllows you to configure the Draw module. Refer to Options and Setup for further information.\nModules\nAllows you to switch to a different module. A menu displays listing the available modules.\nMonitor\nSpecon\nPropcon\nIsodraft\nModel\nParagon\nSpool\nYou can select the required module to open, the Draw module is closed.\nExit\nClick to Exit the Draw module.\nSave Work\nClick to save changes made to data in the Draw module. The facility is also available on the Quick Access Toolbar by default.\nGet Work\nClick to refresh the databases with changes made by other users since the session was started. The facility is also available on the Quick Access Toolbar by default.\nNew Drawing\nAllows you to create new drawing sheets, backing sheets, symbol templates and overlay sheets. Refer to Create Drawing Sheet from a Drawing Type and Template for further information.\nPrint Drawing\nAllows you to set the printing options and print drawing sheets. Refer to Print Sheets for further information.\nExport Drawing\nAllows you to export drawings sheets to other file formats. Refer to Output Facilities for further information.\nHelp\nClick to open the support and information page, which displays general information about the product (for example, the software version). You can access Online Help, facilities to contact AVEVA and check for software updates. Refer to On-Line Help for further information.\nOptions\nAllows you to configure the Draw module. Refer to Options and Setup for further information.\nModules\nAllows you to switch to a different module. A menu displays listing the available modules.\nYou can select the required module to open, the Draw module is closed.\nExit\nClick to Exit the Draw module.\n\nSave Work\nClick to save changes made to data in the Draw module. The facility is also available on the Quick Access Toolbar by default.\nGet Work\nClick to refresh the databases with changes made by other users since the session was started. The facility is also available on the Quick Access Toolbar by default.\nNew Drawing\nAllows you to create new drawing sheets, backing sheets, symbol templates and overlay sheets. Refer to Create Drawing Sheet from a Drawing Type and Template for further information.\nPrint Drawing\nAllows you to set the printing options and print drawing sheets. Refer to Print Sheets for further information.\nExport Drawing\nAllows you to export drawings sheets to other file formats. Refer to Output Facilities for further information.\nHelp\nClick to open the support and information page, which displays general information about the product (for example, the software version). You can access Online Help, facilities to contact AVEVA and check for software updates. Refer to On-Line Help for further information.\nOptions\nAllows you to configure the Draw module. Refer to Options and Setup for further information.\nModules\nAllows you to switch to a different module. A menu displays listing the available modules.\nMonitor\nSpecon\nPropcon\nIsodraft\nModel\nParagon\nSpool\nYou can select the required module to open, the Draw module is closed.\nExit\nClick to Exit the Draw module.\nMonitor\nSpecon\nPropcon\nIsodraft\nModel\nParagon\nSpool\nMonitor\nMonitor\nSpecon\nSpecon\nPropcon\nPropcon\nIsodraft\nIsodraft\nModel\nModel\nParagon\nParagon\nSpool\nSpool\n\n\n\nQuick Access Toolbar\nQuick Access Toolbar\nCreate Drawing Sheet from a Drawing Type and Template\nPrint Sheets\nOutput Facilities\nOn-Line Help\nOptions and Setup\nProject\nSave Work\nQuick Access Toolbar\nGet Work\nQuick Access Toolbar\nNew Drawing\nCreate Drawing Sheet from a Drawing Type and Template\nPrint Drawing\nPrint Sheets\nExport Drawing\nOutput Facilities\nHelp\nOn-Line Help\nOptions\nOptions and Setup\nModules\nExit\nExit"}
{"Headers": "Home", "Content": "\n\nProject Group\nOpen\nAllows you to browse for and open a sheet. Refer to Open Sheet for further information.\nClose\nClick to display a drop-down list with the following options:\nCurrent Drawing\nAllows you to close the current sheet, backing sheet and overlays. Refer to Close Drawing for further information.\nAll Drawings\nAllows you to close all open sheets, backing sheets and overlays. Refer to Close Drawing for further information.\nNew\nClick to display a drop-down list with the following options:\nDrawing Type\nAllows you to create a new drawing sheet by selecting a drawing type and template. Refer to Create Drawing Sheet from a Drawing Type and Template for further information.\nQuick Sheet\nAllows you to create a new drawing sheet. Refer to Create Drawing Sheet from Quick Sheet Option for further information.\nVisual Layers\nAllows you to create and modify layers for the current drawing sheet. Refer to Create and Modify Visual Layers for further information.\nView Group\nQuick View\nAllows you to create a plan view containing objects selected in the Model Explorer. Refer to Create Quick View for further information.\nAdvanced\nClick to display a drop-down list with the following options:\nLocation Defined\nAllows you to create a marine specific view based on a physical or imaginary model plane. Refer to Create Location Defined View for further information.\nMulti-Location\nAllows you to create a marine specific view consisting of projections of the hull surface intersections using a series of planes. Refer to Create Multi-Location View for further information.\nExpansion\nAllows you to create a marine specific view of model elements that are unfolded from their curved shape into a flat form. Refer to Create Expansion View for further information.\nDesign\nAllows you to create a new view containing an easily selected and managed list of objects with a specified view direction or scale. Refer to Create Design View for further information.\nProjection\nClick to display a drop-down list with the following options:\nProjection\nAllows you to create a Projection view with a preview image of the view to be created. Refer to Create Orthographic Projection View for further information.\nQuick Projection\nAllows you to create a Projection view without a preview image of the view to be created. Refer to Create Quick Projection View for further information.\nDetail\nClick to display a drop-down list with the following options:\nDetail\nAllows you to create a Detail view. Refer to Create Detail View for further information.\nLocation Defined Detail\nAllows you to create a Location Defined Detail view. Refer to Create Location Defined Detail View for further information.\nSection\nAllows you to create a Section view. Refer to Create Section View for further information.\nBasic\nAllows you to create a Basic view. Refer to Create Basic View for further information.\nRegion\nAllows you to create a new region. Refer to Create Regions for further information.\nDraw Group\nLine\nAllows you to draw lines. Refer to Draw Lines for further information.\nCloud\nClick to display a drop-down list with the following options:\nCloud\nAllows you to draw clouds. Refer to Draw Clouds and Outlines for further information.\nOutline\nAllows you to draw outlines. Refer to Draw Clouds and Outlines for further information.\nCircle Centre-Radius\nClick to display a drop-down with the following options:\nCircle Centre-Radius\nAllows you to draw circles by specifying their radii. Refer to Draw Circle with Specified Radiusfor further information.\nCircle Two-Points\nAllows you to draw circles by specifying their diameters. Refer to Draw Circle with Two Specified Points for further information.\nCircle Centre-Diameter\nAllows you to draw circles by specifying their centre points and diameters. Refer to Draw Circle with Specified Diameter for further information.\nRectangle\nAllows you to draw rectangles. Refer to Draw Rectangles and Diamonds for further information.\nDiamond\nAllows you to draw diamonds. Refer to Draw Rectangles and Diamonds for further information.\nTriangle\nAllows you to draw equilateral triangles. Refer to Draw Equilateral Triangles for further information.\nHexagon Two-Points\nAllows you to draw hexagons by specifying their point to point diameters. Refer to Draw Hexagon with Specified Point to Point Diameter for further information.\nHexagon End-Point\nAllows you to draw hexagons by specifying their centre to point radius. Refer to Draw Hexagon with Specified Center to Point Radius for further information.\nEllipse Axis-Edge\nAllows you to draw ellipses by specifying the length of their axes. Refer to Draw Ellipse with Specified Length of Axes for further information.\nEllipse Centre\nAllows you to draw ellipses by specifying the radius of the first axis and the length of the second. Refer to Draw Ellipse with Specified Radius of First Axis and Length of Second for further information.\nArc Angle\nAllows you to draw arcs by specifying their centre points, start points and sweep angles. Refer to Draw Arc with Specified Center, End and Angle for further information.\nArc Three-Points\nAllows you to draw arcs by specifying their start points, end points and through points. Refer to Draw Arc with Specified Start, End and Through Points for further information.\nElliptical Arc\nAllows you to draw elliptical arcs. Refer to Draw Elliptical Arc with Specified Axes, Start and End Angle for further information.\nAnnotate Group\nOrthogonal Chained\nAllows you to add various types of linear dimension annotations. Refer to Add Linear Dimensions for further information.\nClick to display a drop-down list with the following options:\nOrthogonal Chained\nAligned Chained\nCombined Left\nCombined Right\nAligned Combined\nBaseline Left\nBaseline Right\nAligned Baseline\nChained\nAllows you to add various types of angular dimension annotations. Refer to Add Angular Dimensions for further information.\nClick to display a drop-down list with the following options:\nChained\nBaseline\nCombined\nAcross Diameter\nAllows you to add various types of radial dimension annotations. Refer to Add Radial Dimensions for further information.\nClick to display a drop-down list with the following options:\nAcross Diameter\nAcross Diameter Leaderline\nDiameter Leaderline\nDiameter Pointer Leaderline\nDiameter Internal Leaderline\nInternal Radius\nInternal Radius Leaderline\nExternal Radius Leaderline\nExternal Point Leaderline\nRadius Internal Leaderline\nAcrossPCD\nAllows you to add various types of pitch circle dimension annotations. Refer to Add Pitch Circle Dimensions for further information.\nClick to display a drop-down list with the following options:\nAcross PCD\nAcross PCD Leaderline\nPCD Leaderline\nPCD Pointer Leaderline\nPCD Internal Leaderline\nInternal PCR\nInternal PCR Leaderline\nExternal PCR Leaderline\nExternal PCR Pointer Leaderline\nPCR Internal Leaderline\nTools Group\nDelete\nAllows you to delete objects. Refer to Delete for further information.\nCut\nClick to display a drop-down list with the following options:\nCut\nAllows you to cut objects. Refer to Cut Objects for further information.\nCut with Base Point\nAllows you to cut objects. A base point is specified during the cut process. You must specify the new position for the base point during the paste process to determine the placement of the object(s). Refer to Cut Objects using Base Point for further information.\nCopy\nClick to display a drop-down list with the following options:\nCopy\nAllows you to copy objects. Refer to Copy Objects for further information.\nCopy with Base Point\nAllows you to copy objects. A base point is specified during the copy process. You must specify the new position for the base point during the paste process to determine the placement of the object(s). Refer to Copy Objects using Base Point or further information.\nPaste\nClick to display a drop-down list with the following options:\nPaste\nAllows you to paste objects. Refer to Move Objects and Copy Objects for further information.\nPaste with Original Coordinates\nAllows you to paste objects to a different drawing at the same position as the original. Refer to Move Objects and Copy Objects for further information.\nZoom Extents\nAllows you to define the magnification of the drawing in the view. Refer to Zoom Options for further information.\nClick to display a drop-down list with the following options:\nZoom Extents\nZoom In\nZoom Out\nZoom Realtime\nZoom Window\nZoom Dynamic\nZoom Scale\nZoom Centre\nZoom Object\nRedo\nAllows you to re-insert changes since the session was last saved. Refer to Undo and Redo Changes for further information.\nClick to display a drop-down list with the following options:\nRedo\nSelect from the drop-down list to redo the last undone change. You can continue to redo undone modifications.\nRedo Multiple\nSelect from the drop-down list to redo a specified number of undone changes, or a group of undone changes.\nRedo All\nSelect from the drop-down list to redo all undone changes.\nUndo\nAllows you to remove changes since the session was last saved. Refer to Undo and Redo Changes for further information.\nClick to display a drop-down list with the following options:\nUndo\nSelect from the drop-down list to undo the last change. You can continue to undo previous modifications.\nUndo Multiple\nSelect from the drop-down list to undo a specified number of changes, or a group of changes.\nUndo All\nSelect from the drop-down list to undo all changes made since the last save.\nPan Realtime\nAllows you to define the position of the drawing in the view. Refer to Pan Options for further information.\nClick to display a drop-down list with the following options:\nPan Realtime\nPan Point\nPan Left\nPan Right\nPan Top\nPan Bottom\nDisplay Group\nActive Properties\nAllows you to view and change the default properties that are applied to new objects when they are created, and to subsequently apply these properties to selected objects if required. Refer to Active Properties for further information.\nProperty Grid\nAllows you to define object properties. Refer to Properties for further information.\nPower Selector\nAllows you to quickly select primitives or annotations based on filter criteria. Functionality is also available to select annotations based on the intelligent link to the 3D model. Refer to Power Selector for further information.\nTabbed View\nClick to toggle the drawing display in tabs (the default format), or in windows.\nRep. & Hatch Rules\nAllows you to create and modify representation and hatch rules. Refer to Create and Modify Representation and Hatch Styles for further information.\nObject Snaps\nAids the positioning of objects by placing them relative to the geometry of existing objects. Refer to Object Snaps for further information.\nActive Visual Styles\nAllows you to set the default visual style for labels, text, dimensions, rulers, baselines, centrelines, view frames and connectors. Refer to Active Visual Styles for further information.\nUpdate Group\nCurrent Owner\nAllows you to manually update the view for the current owner with any database or settings changes.\nNote:\nThe changes are applied automatically if is set on the Status Bar.\nProject Group\nOpen\nAllows you to browse for and open a sheet. Refer to Open Sheet for further information.\nClose\nClick to display a drop-down list with the following options:\nAllows you to close the current sheet, backing sheet and overlays. Refer to Close Drawing for further information.\nAllows you to close all open sheets, backing sheets and overlays. Refer to Close Drawing for further information.\nNew\nClick to display a drop-down list with the following options:\nAllows you to create a new drawing sheet by selecting a drawing type and template. Refer to Create Drawing Sheet from a Drawing Type and Template for further information.\nAllows you to create a new drawing sheet. Refer to Create Drawing Sheet from Quick Sheet Option for further information.\nVisual Layers\nAllows you to create and modify layers for the current drawing sheet. Refer to Create and Modify Visual Layers for further information.\nView Group\nQuick View\nAllows you to create a plan view containing objects selected in the Model Explorer. Refer to Create Quick View for further information.\nAdvanced\nClick to display a drop-down list with the following options:\nAllows you to create a marine specific view based on a physical or imaginary model plane. Refer to Create Location Defined View for further information.\nAllows you to create a marine specific view consisting of projections of the hull surface intersections using a series of planes. Refer to Create Multi-Location View for further information.\nAllows you to create a marine specific view of model elements that are unfolded from their curved shape into a flat form. Refer to Create Expansion View for further information.\nDesign\nAllows you to create a new view containing an easily selected and managed list of objects with a specified view direction or scale. Refer to Create Design View for further information.\nProjection\nClick to display a drop-down list with the following options:\nAllows you to create a Projection view with a preview image of the view to be created. Refer to Create Orthographic Projection View for further information.\nAllows you to create a Projection view without a preview image of the view to be created. Refer to Create Quick Projection View for further information.\nDetail\nClick to display a drop-down list with the following options:\nAllows you to create a Detail view. Refer to Create Detail View for further information.\nAllows you to create a Location Defined Detail view. Refer to Create Location Defined Detail View for further information.\nSection\nAllows you to create a Section view. Refer to Create Section View for further information.\nBasic\nAllows you to create a Basic view. Refer to Create Basic View for further information.\nRegion\nAllows you to create a new region. Refer to Create Regions for further information.\nDraw Group\nLine\nAllows you to draw lines. Refer to Draw Lines for further information.\nCloud\nClick to display a drop-down list with the following options:\nAllows you to draw clouds. Refer to Draw Clouds and Outlines for further information.\nAllows you to draw outlines. Refer to Draw Clouds and Outlines for further information.\nCircle Centre-Radius\nClick to display a drop-down with the following options:\nAllows you to draw circles by specifying their radii. Refer to Draw Circle with Specified Radiusfor further information.\nAllows you to draw circles by specifying their diameters. Refer to Draw Circle with Two Specified Points for further information.\nAllows you to draw circles by specifying their centre points and diameters. Refer to Draw Circle with Specified Diameter for further information.\nAllows you to draw rectangles. Refer to Draw Rectangles and Diamonds for further information.\nAllows you to draw diamonds. Refer to Draw Rectangles and Diamonds for further information.\nAllows you to draw equilateral triangles. Refer to Draw Equilateral Triangles for further information.\nAllows you to draw hexagons by specifying their point to point diameters. Refer to Draw Hexagon with Specified Point to Point Diameter for further information.\nAllows you to draw hexagons by specifying their centre to point radius. Refer to Draw Hexagon with Specified Center to Point Radius for further information.\nAllows you to draw ellipses by specifying the length of their axes. Refer to Draw Ellipse with Specified Length of Axes for further information.\nAllows you to draw ellipses by specifying the radius of the first axis and the length of the second. Refer to Draw Ellipse with Specified Radius of First Axis and Length of Second for further information.\nAllows you to draw arcs by specifying their centre points, start points and sweep angles. Refer to Draw Arc with Specified Center, End and Angle for further information.\nAllows you to draw arcs by specifying their start points, end points and through points. Refer to Draw Arc with Specified Start, End and Through Points for further information.\nAllows you to draw elliptical arcs. Refer to Draw Elliptical Arc with Specified Axes, Start and End Angle for further information.\nAnnotate Group\nOrthogonal Chained\nAllows you to add various types of linear dimension annotations. Refer to Add Linear Dimensions for further information.\nClick to display a drop-down list with the following options:\nChained\nAllows you to add various types of angular dimension annotations. Refer to Add Angular Dimensions for further information.\nClick to display a drop-down list with the following options:\nAcross Diameter\nAllows you to add various types of radial dimension annotations. Refer to Add Radial Dimensions for further information.\nClick to display a drop-down list with the following options:\nAcrossPCD\nAllows you to add various types of pitch circle dimension annotations. Refer to Add Pitch Circle Dimensions for further information.\nClick to display a drop-down list with the following options:\nTools Group\nDelete\nAllows you to delete objects. Refer to Delete for further information.\nCut\nClick to display a drop-down list with the following options:\nAllows you to cut objects. Refer to Cut Objects for further information.\nAllows you to cut objects. A base point is specified during the cut process. You must specify the new position for the base point during the paste process to determine the placement of the object(s). Refer to Cut Objects using Base Point for further information.\nCopy\nClick to display a drop-down list with the following options:\nAllows you to copy objects. Refer to Copy Objects for further information.\nAllows you to copy objects. A base point is specified during the copy process. You must specify the new position for the base point during the paste process to determine the placement of the object(s). Refer to Copy Objects using Base Point or further information.\nPaste\nClick to display a drop-down list with the following options:\nAllows you to paste objects. Refer to Move Objects and Copy Objects for further information.\nAllows you to paste objects to a different drawing at the same position as the original. Refer to Move Objects and Copy Objects for further information.\nZoom Extents\nAllows you to define the magnification of the drawing in the view. Refer to Zoom Options for further information.\nClick to display a drop-down list with the following options:\nRedo\nAllows you to re-insert changes since the session was last saved. Refer to Undo and Redo Changes for further information.\nClick to display a drop-down list with the following options:\nSelect from the drop-down list to redo the last undone change. You can continue to redo undone modifications.\nSelect from the drop-down list to redo a specified number of undone changes, or a group of undone changes.\nSelect from the drop-down list to redo all undone changes.\nUndo\nAllows you to remove changes since the session was last saved. Refer to Undo and Redo Changes for further information.\nClick to display a drop-down list with the following options:\nSelect from the drop-down list to undo the last change. You can continue to undo previous modifications.\nSelect from the drop-down list to undo a specified number of changes, or a group of changes.\nSelect from the drop-down list to undo all changes made since the last save.\nPan Realtime\nAllows you to define the position of the drawing in the view. Refer to Pan Options for further information.\nClick to display a drop-down list with the following options:\nDisplay Group\nActive Properties\nAllows you to view and change the default properties that are applied to new objects when they are created, and to subsequently apply these properties to selected objects if required. Refer to Active Properties for further information.\nProperty Grid\nAllows you to define object properties. Refer to Properties for further information.\nPower Selector\nAllows you to quickly select primitives or annotations based on filter criteria. Functionality is also available to select annotations based on the intelligent link to the 3D model. Refer to Power Selector for further information.\nTabbed View\nClick to toggle the drawing display in tabs (the default format), or in windows.\nRep. & Hatch Rules\nAllows you to create and modify representation and hatch rules. Refer to Create and Modify Representation and Hatch Styles for further information.\nObject Snaps\nAids the positioning of objects by placing them relative to the geometry of existing objects. Refer to Object Snaps for further information.\nActive Visual Styles\nAllows you to set the default visual style for labels, text, dimensions, rulers, baselines, centrelines, view frames and connectors. Refer to Active Visual Styles for further information.\nUpdate Group\nCurrent Owner\nAllows you to manually update the view for the current owner with any database or settings changes.\n\nProject Group\nOpen\nAllows you to browse for and open a sheet. Refer to Open Sheet for further information.\nClose\nClick to display a drop-down list with the following options:\nCurrent Drawing\nAllows you to close the current sheet, backing sheet and overlays. Refer to Close Drawing for further information.\nAll Drawings\nAllows you to close all open sheets, backing sheets and overlays. Refer to Close Drawing for further information.\nNew\nClick to display a drop-down list with the following options:\nDrawing Type\nAllows you to create a new drawing sheet by selecting a drawing type and template. Refer to Create Drawing Sheet from a Drawing Type and Template for further information.\nQuick Sheet\nAllows you to create a new drawing sheet. Refer to Create Drawing Sheet from Quick Sheet Option for further information.\nVisual Layers\nAllows you to create and modify layers for the current drawing sheet. Refer to Create and Modify Visual Layers for further information.\nView Group\nQuick View\nAllows you to create a plan view containing objects selected in the Model Explorer. Refer to Create Quick View for further information.\nAdvanced\nClick to display a drop-down list with the following options:\nLocation Defined\nAllows you to create a marine specific view based on a physical or imaginary model plane. Refer to Create Location Defined View for further information.\nMulti-Location\nAllows you to create a marine specific view consisting of projections of the hull surface intersections using a series of planes. Refer to Create Multi-Location View for further information.\nExpansion\nAllows you to create a marine specific view of model elements that are unfolded from their curved shape into a flat form. Refer to Create Expansion View for further information.\nDesign\nAllows you to create a new view containing an easily selected and managed list of objects with a specified view direction or scale. Refer to Create Design View for further information.\nProjection\nClick to display a drop-down list with the following options:\nProjection\nAllows you to create a Projection view with a preview image of the view to be created. Refer to Create Orthographic Projection View for further information.\nQuick Projection\nAllows you to create a Projection view without a preview image of the view to be created. Refer to Create Quick Projection View for further information.\nDetail\nClick to display a drop-down list with the following options:\nDetail\nAllows you to create a Detail view. Refer to Create Detail View for further information.\nLocation Defined Detail\nAllows you to create a Location Defined Detail view. Refer to Create Location Defined Detail View for further information.\nSection\nAllows you to create a Section view. Refer to Create Section View for further information.\nBasic\nAllows you to create a Basic view. Refer to Create Basic View for further information.\nRegion\nAllows you to create a new region. Refer to Create Regions for further information.\nDraw Group\nLine\nAllows you to draw lines. Refer to Draw Lines for further information.\nCloud\nClick to display a drop-down list with the following options:\nCloud\nAllows you to draw clouds. Refer to Draw Clouds and Outlines for further information.\nOutline\nAllows you to draw outlines. Refer to Draw Clouds and Outlines for further information.\nCircle Centre-Radius\nClick to display a drop-down with the following options:\nCircle Centre-Radius\nAllows you to draw circles by specifying their radii. Refer to Draw Circle with Specified Radiusfor further information.\nCircle Two-Points\nAllows you to draw circles by specifying their diameters. Refer to Draw Circle with Two Specified Points for further information.\nCircle Centre-Diameter\nAllows you to draw circles by specifying their centre points and diameters. Refer to Draw Circle with Specified Diameter for further information.\nRectangle\nAllows you to draw rectangles. Refer to Draw Rectangles and Diamonds for further information.\nDiamond\nAllows you to draw diamonds. Refer to Draw Rectangles and Diamonds for further information.\nTriangle\nAllows you to draw equilateral triangles. Refer to Draw Equilateral Triangles for further information.\nHexagon Two-Points\nAllows you to draw hexagons by specifying their point to point diameters. Refer to Draw Hexagon with Specified Point to Point Diameter for further information.\nHexagon End-Point\nAllows you to draw hexagons by specifying their centre to point radius. Refer to Draw Hexagon with Specified Center to Point Radius for further information.\nEllipse Axis-Edge\nAllows you to draw ellipses by specifying the length of their axes. Refer to Draw Ellipse with Specified Length of Axes for further information.\nEllipse Centre\nAllows you to draw ellipses by specifying the radius of the first axis and the length of the second. Refer to Draw Ellipse with Specified Radius of First Axis and Length of Second for further information.\nArc Angle\nAllows you to draw arcs by specifying their centre points, start points and sweep angles. Refer to Draw Arc with Specified Center, End and Angle for further information.\nArc Three-Points\nAllows you to draw arcs by specifying their start points, end points and through points. Refer to Draw Arc with Specified Start, End and Through Points for further information.\nElliptical Arc\nAllows you to draw elliptical arcs. Refer to Draw Elliptical Arc with Specified Axes, Start and End Angle for further information.\nAnnotate Group\nOrthogonal Chained\nAllows you to add various types of linear dimension annotations. Refer to Add Linear Dimensions for further information.\nClick to display a drop-down list with the following options:\nOrthogonal Chained\nAligned Chained\nCombined Left\nCombined Right\nAligned Combined\nBaseline Left\nBaseline Right\nAligned Baseline\nChained\nAllows you to add various types of angular dimension annotations. Refer to Add Angular Dimensions for further information.\nClick to display a drop-down list with the following options:\nChained\nBaseline\nCombined\nAcross Diameter\nAllows you to add various types of radial dimension annotations. Refer to Add Radial Dimensions for further information.\nClick to display a drop-down list with the following options:\nAcross Diameter\nAcross Diameter Leaderline\nDiameter Leaderline\nDiameter Pointer Leaderline\nDiameter Internal Leaderline\nInternal Radius\nInternal Radius Leaderline\nExternal Radius Leaderline\nExternal Point Leaderline\nRadius Internal Leaderline\nAcrossPCD\nAllows you to add various types of pitch circle dimension annotations. Refer to Add Pitch Circle Dimensions for further information.\nClick to display a drop-down list with the following options:\nAcross PCD\nAcross PCD Leaderline\nPCD Leaderline\nPCD Pointer Leaderline\nPCD Internal Leaderline\nInternal PCR\nInternal PCR Leaderline\nExternal PCR Leaderline\nExternal PCR Pointer Leaderline\nPCR Internal Leaderline\nTools Group\nDelete\nAllows you to delete objects. Refer to Delete for further information.\nCut\nClick to display a drop-down list with the following options:\nCut\nAllows you to cut objects. Refer to Cut Objects for further information.\nCut with Base Point\nAllows you to cut objects. A base point is specified during the cut process. You must specify the new position for the base point during the paste process to determine the placement of the object(s). Refer to Cut Objects using Base Point for further information.\nCopy\nClick to display a drop-down list with the following options:\nCopy\nAllows you to copy objects. Refer to Copy Objects for further information.\nCopy with Base Point\nAllows you to copy objects. A base point is specified during the copy process. You must specify the new position for the base point during the paste process to determine the placement of the object(s). Refer to Copy Objects using Base Point or further information.\nPaste\nClick to display a drop-down list with the following options:\nPaste\nAllows you to paste objects. Refer to Move Objects and Copy Objects for further information.\nPaste with Original Coordinates\nAllows you to paste objects to a different drawing at the same position as the original. Refer to Move Objects and Copy Objects for further information.\nZoom Extents\nAllows you to define the magnification of the drawing in the view. Refer to Zoom Options for further information.\nClick to display a drop-down list with the following options:\nZoom Extents\nZoom In\nZoom Out\nZoom Realtime\nZoom Window\nZoom Dynamic\nZoom Scale\nZoom Centre\nZoom Object\nRedo\nAllows you to re-insert changes since the session was last saved. Refer to Undo and Redo Changes for further information.\nClick to display a drop-down list with the following options:\nRedo\nSelect from the drop-down list to redo the last undone change. You can continue to redo undone modifications.\nRedo Multiple\nSelect from the drop-down list to redo a specified number of undone changes, or a group of undone changes.\nRedo All\nSelect from the drop-down list to redo all undone changes.\nUndo\nAllows you to remove changes since the session was last saved. Refer to Undo and Redo Changes for further information.\nClick to display a drop-down list with the following options:\nUndo\nSelect from the drop-down list to undo the last change. You can continue to undo previous modifications.\nUndo Multiple\nSelect from the drop-down list to undo a specified number of changes, or a group of changes.\nUndo All\nSelect from the drop-down list to undo all changes made since the last save.\nPan Realtime\nAllows you to define the position of the drawing in the view. Refer to Pan Options for further information.\nClick to display a drop-down list with the following options:\nPan Realtime\nPan Point\nPan Left\nPan Right\nPan Top\nPan Bottom\nDisplay Group\nActive Properties\nAllows you to view and change the default properties that are applied to new objects when they are created, and to subsequently apply these properties to selected objects if required. Refer to Active Properties for further information.\nProperty Grid\nAllows you to define object properties. Refer to Properties for further information.\nPower Selector\nAllows you to quickly select primitives or annotations based on filter criteria. Functionality is also available to select annotations based on the intelligent link to the 3D model. Refer to Power Selector for further information.\nTabbed View\nClick to toggle the drawing display in tabs (the default format), or in windows.\nRep. & Hatch Rules\nAllows you to create and modify representation and hatch rules. Refer to Create and Modify Representation and Hatch Styles for further information.\nObject Snaps\nAids the positioning of objects by placing them relative to the geometry of existing objects. Refer to Object Snaps for further information.\nActive Visual Styles\nAllows you to set the default visual style for labels, text, dimensions, rulers, baselines, centrelines, view frames and connectors. Refer to Active Visual Styles for further information.\nUpdate Group\nCurrent Owner\nAllows you to manually update the view for the current owner with any database or settings changes.\nNote:\nThe changes are applied automatically if is set on the Status Bar.\nOrthogonal Chained\nAligned Chained\nCombined Left\nCombined Right\nAligned Combined\nBaseline Left\nBaseline Right\nAligned Baseline\nOrthogonal Chained\nOrthogonal Chained\nAligned Chained\nAligned Chained\nCombined Left\nCombined Left\nCombined Right\nCombined Right\nAligned Combined\nAligned Combined\nBaseline Left\nBaseline Left\nBaseline Right\nBaseline Right\nAligned Baseline\nAligned Baseline\nChained\nBaseline\nCombined\nChained\nChained\nBaseline\nBaseline\nCombined\nCombined\nAcross Diameter\nAcross Diameter Leaderline\nDiameter Leaderline\nDiameter Pointer Leaderline\nDiameter Internal Leaderline\nInternal Radius\nInternal Radius Leaderline\nExternal Radius Leaderline\nExternal Point Leaderline\nRadius Internal Leaderline\nAcross Diameter\nAcross Diameter\nAcross Diameter Leaderline\nAcross Diameter Leaderline\nDiameter Leaderline\nDiameter Leaderline\nDiameter Pointer Leaderline\nDiam"}
{"Headers": "Draw", "Content": "\n\nMeasure Group\nDistance\nAllows you to measure the distance between two points. Refer to Measure Distance between Two Points for further information.\nAngle\nAllows you to measure the angle between two points. Refer to Measure Angle between two Points for further information.\nCumulative Length\nAllows you to measure the cumulative lengths of multiple objects. Refer to Measure Cumulative Lengths of Objects for further information.\nID Point\nAllows you to display the coordinates of a point. Refer to Display Point Coordinates for further information.\nDraw Group\nLine\nAllows you to draw lines. Refer to Draw Lines for further information.\nCloud\nAllows you to draw clouds and outlines. Refer to Draw Clouds and Outlines for further information.\nClick to display a drop-down list with the following options:\nCloud\nOutline\nCircle Centre-Radius\nClick to display a drop-down list with the following options:\nCircle Centre-Radius\nAllows you to draw circles by specifying their radii. Refer to Draw Circle with Specified Radius for further information.\nCircle Two-Points\nAllows you to draw circles by specifying their diameters Refer to Draw Circle with Two Specified Points for further information.\nCircle Centre- Diameter\nAllows you to draw circles by specifying their centre points and diameters. Refer to Draw Circle with Specified Diameter for further information.\nRectangle\nClick to display a drop-down list with the following options:\nRectangle\nAllows you to draw rectangles. Refer to Draw Rectangles and Diamonds for further information.\nDiamond\nAllows you to draw diamonds. Refer to Draw Rectangles and Diamonds for further information.\nArc Angle\nClick to display a drop-down list with the following options:\nArc Angle\nAllows you to draw arcs by specifying their centre points, start points and sweep angles. Refer to Draw Arc with Specified Center, End and Angle for further information.\nArc Three-Points\nAllows you to draw arcs by specifying their start points, end points and through points. Refer to Draw Arc with Specified Start, End and Through Points for further information.\nTriangle\nAllows you to draw equilateral triangles. Refer to Draw Equilateral Triangles for further information.\nHexagon End-Point\nClick to display a drop-down list with the following options:\nHexagon End-Point\nAllows you to draw hexagons by specifying their centre to point radius. Refer toDraw Hexagon with Specified Center to Point Radius for further information.\nHexagon Two-Points\nAllows you to draw hexagons by specifying their point to point diameters. Refer to Draw Hexagon with Specified Point to Point Diameter for further information.\nHexagon Edge\nAllows you to draw hexagons by specifying their centre to side radius. Refer to Draw Hexagon with Specified Center to Side Radius for further information.\nAxis - Axis-Edge\nClick to display a drop-down list with the following options:\nEllipse Axis-Edge\nAllows you to draw ellipses by specifying the length of their axes. Refer to Draw Ellipse with Specified Length of Axes for further information.\nEllipse Centre\nAllows you to draw ellipses by specifying the radius of the first axis and the length of the second. Refer to Draw Ellipse with Specified Radius of First Axis and Length of Second for further information.\nElliptical Arc\nAllows you to draw elliptical arcs. Refer to Draw Elliptical Arc with Specified Axes, Start and End Angle for further information.\nTangent\nAllows you to draw tangent lines. Refer to Draw Tangent Lines for further information.\nConnector\nAllows you to draw connectors. Refer to Draw Connectors for further information.\nConstruct Group\nRay Line\nAllows you to draw ray lines. Refer to Add Ray Lines for further information.\nXLine\nClick to display a drop-down list with the following options:\nXLine\nAllows you to draw xlines by selecting two points. Refer to Add XLines with Two Selected Points for further information.\nHorizontal\nAllows you to draw horizontal xlines. Refer to Add Horizontal XLines for further information.\nVertical\nAllows you to draw vertical xlines. Refer to Add Vertical XLines for further information.\nAngle\nAllows you to draw xlines at a specified angle. Refer to Add XLines with a Specified Angle for further information.\nBisect\nAllows you to draw bisecting xlines. Refer to Add Bisect XLines for further information.\nModify Group\nMove\nAllows you to move objects. Refer to Move Objects for further information.\nCopy & Paste\nAllows you to copy and paste objects. Refer to Copy and Paste Objects for further information.\nOffset\nAllows you to offset objects. Refer to Offset Objects for further information.\nRotate\nAllows you to rotate objects. Refer to Rotate Objects for further information.\nMirror\nAllows you to mirror objects. Refer to Mirror Objects for further information.\nScale\nAllows you to scale objects. Refer to Scale Objects for further information.\nArray\nAllows you to create arrays of objects. Refer to Create Arrays of Objects for further information.\nStretch\nAllows you to stretch objects. Refer to Stretch Objects for further information.\nExplode\nClick to display a drop-down list with the following options:\nExplode\nAllows you to explode objects. Refer to Explode Objects for further information.\nMerge\nAllows you to merge objects. Refer to Merge Objects for further information.\nLengthen\nAllows you to change the length of objects. Refer to Change Length of Objects for further information.\nTrim\nClick to display a drop-down list with the following options:\nTrim\nAllows you to trim objects. Refer to Trim Objects for further information.\nExtend\nAllows you to extend objects. Refer to Extend Objects for further information.\nFillet\nClick to display a drop-down list with the following options:\nFillet\nAllows you to fillet objects with a radius of 0 degrees. Refer to Fillet Objects for further information.\nFilletR\nAllows you to fillet objects with a selected fillet arc radius. Refer to Fillet Objects for further information.\nChamfer\nAllows you to chamfer objects. Refer to Chamfer Objects for further information.\nSend to Back\nAllows you to move objects to the back of the drawing canvas. Refer to Send to Back for further information.\nBring to Front\nAllows you to move objects to the front of the drawing canvas. Refer to Bring to Front for further information.\nAlign Views\nAllows you to align views on the drawing canvas, views can be aligned horizontally or vertically. Refer to Align Views for further information.\nQuick Add\nAllows you to quickly and easily add model elements to selected views. Refer to Quick Add for further information.\nDelete Group\nDelete\nAllows you to delete objects. Refer to Delete for further information.\nMeasure Group\nDistance\nAllows you to measure the distance between two points. Refer to Measure Distance between Two Points for further information.\nAngle\nAllows you to measure the angle between two points. Refer to Measure Angle between two Points for further information.\nCumulative Length\nAllows you to measure the cumulative lengths of multiple objects. Refer to Measure Cumulative Lengths of Objects for further information.\nID Point\nAllows you to display the coordinates of a point. Refer to Display Point Coordinates for further information.\nDraw Group\nLine\nAllows you to draw lines. Refer to Draw Lines for further information.\nCloud\nAllows you to draw clouds and outlines. Refer to Draw Clouds and Outlines for further information.\nClick to display a drop-down list with the following options:\nCircle Centre-Radius\nClick to display a drop-down list with the following options:\nAllows you to draw circles by specifying their radii. Refer to Draw Circle with Specified Radius for further information.\nAllows you to draw circles by specifying their diameters Refer to Draw Circle with Two Specified Points for further information.\nAllows you to draw circles by specifying their centre points and diameters. Refer to Draw Circle with Specified Diameter for further information.\nRectangle\nClick to display a drop-down list with the following options:\nAllows you to draw rectangles. Refer to Draw Rectangles and Diamonds for further information.\nAllows you to draw diamonds. Refer to Draw Rectangles and Diamonds for further information.\nArc Angle\nClick to display a drop-down list with the following options:\nAllows you to draw arcs by specifying their centre points, start points and sweep angles. Refer to Draw Arc with Specified Center, End and Angle for further information.\nAllows you to draw arcs by specifying their start points, end points and through points. Refer to Draw Arc with Specified Start, End and Through Points for further information.\nTriangle\nAllows you to draw equilateral triangles. Refer to Draw Equilateral Triangles for further information.\nHexagon End-Point\nClick to display a drop-down list with the following options:\nAllows you to draw hexagons by specifying their centre to point radius. Refer toDraw Hexagon with Specified Center to Point Radius for further information.\nAllows you to draw hexagons by specifying their point to point diameters. Refer to Draw Hexagon with Specified Point to Point Diameter for further information.\nAllows you to draw hexagons by specifying their centre to side radius. Refer to Draw Hexagon with Specified Center to Side Radius for further information.\nAxis - Axis-Edge\nClick to display a drop-down list with the following options:\nAllows you to draw ellipses by specifying the length of their axes. Refer to Draw Ellipse with Specified Length of Axes for further information.\nAllows you to draw ellipses by specifying the radius of the first axis and the length of the second. Refer to Draw Ellipse with Specified Radius of First Axis and Length of Second for further information.\nAllows you to draw elliptical arcs. Refer to Draw Elliptical Arc with Specified Axes, Start and End Angle for further information.\nTangent\nAllows you to draw tangent lines. Refer to Draw Tangent Lines for further information.\nConnector\nAllows you to draw connectors. Refer to Draw Connectors for further information.\nConstruct Group\nRay Line\nAllows you to draw ray lines. Refer to Add Ray Lines for further information.\nXLine\nClick to display a drop-down list with the following options:\nAllows you to draw xlines by selecting two points. Refer to Add XLines with Two Selected Points for further information.\nAllows you to draw horizontal xlines. Refer to Add Horizontal XLines for further information.\nAllows you to draw vertical xlines. Refer to Add Vertical XLines for further information.\nAllows you to draw xlines at a specified angle. Refer to Add XLines with a Specified Angle for further information.\nAllows you to draw bisecting xlines. Refer to Add Bisect XLines for further information.\nModify Group\nMove\nAllows you to move objects. Refer to Move Objects for further information.\nCopy & Paste\nAllows you to copy and paste objects. Refer to Copy and Paste Objects for further information.\nOffset\nAllows you to offset objects. Refer to Offset Objects for further information.\nRotate\nAllows you to rotate objects. Refer to Rotate Objects for further information.\nMirror\nAllows you to mirror objects. Refer to Mirror Objects for further information.\nScale\nAllows you to scale objects. Refer to Scale Objects for further information.\nArray\nAllows you to create arrays of objects. Refer to Create Arrays of Objects for further information.\nStretch\nAllows you to stretch objects. Refer to Stretch Objects for further information.\nExplode\nClick to display a drop-down list with the following options:\nAllows you to explode objects. Refer to Explode Objects for further information.\nAllows you to merge objects. Refer to Merge Objects for further information.\nLengthen\nAllows you to change the length of objects. Refer to Change Length of Objects for further information.\nTrim\nClick to display a drop-down list with the following options:\nAllows you to trim objects. Refer to Trim Objects for further information.\nAllows you to extend objects. Refer to Extend Objects for further information.\nFillet\nClick to display a drop-down list with the following options:\nAllows you to fillet objects with a radius of 0 degrees. Refer to Fillet Objects for further information.\nAllows you to fillet objects with a selected fillet arc radius. Refer to Fillet Objects for further information.\nAllows you to chamfer objects. Refer to Chamfer Objects for further information.\nSend to Back\nAllows you to move objects to the back of the drawing canvas. Refer to Send to Back for further information.\nBring to Front\nAllows you to move objects to the front of the drawing canvas. Refer to Bring to Front for further information.\nAlign Views\nAllows you to align views on the drawing canvas, views can be aligned horizontally or vertically. Refer to Align Views for further information.\nQuick Add\nAllows you to quickly and easily add model elements to selected views. Refer to Quick Add for further information.\nDelete Group\nDelete\nAllows you to delete objects. Refer to Delete for further information.\n\nMeasure Group\nDistance\nAllows you to measure the distance between two points. Refer to Measure Distance between Two Points for further information.\nAngle\nAllows you to measure the angle between two points. Refer to Measure Angle between two Points for further information.\nCumulative Length\nAllows you to measure the cumulative lengths of multiple objects. Refer to Measure Cumulative Lengths of Objects for further information.\nID Point\nAllows you to display the coordinates of a point. Refer to Display Point Coordinates for further information.\nDraw Group\nLine\nAllows you to draw lines. Refer to Draw Lines for further information.\nCloud\nAllows you to draw clouds and outlines. Refer to Draw Clouds and Outlines for further information.\nClick to display a drop-down list with the following options:\nCloud\nOutline\nCircle Centre-Radius\nClick to display a drop-down list with the following options:\nCircle Centre-Radius\nAllows you to draw circles by specifying their radii. Refer to Draw Circle with Specified Radius for further information.\nCircle Two-Points\nAllows you to draw circles by specifying their diameters Refer to Draw Circle with Two Specified Points for further information.\nCircle Centre- Diameter\nAllows you to draw circles by specifying their centre points and diameters. Refer to Draw Circle with Specified Diameter for further information.\nRectangle\nClick to display a drop-down list with the following options:\nRectangle\nAllows you to draw rectangles. Refer to Draw Rectangles and Diamonds for further information.\nDiamond\nAllows you to draw diamonds. Refer to Draw Rectangles and Diamonds for further information.\nArc Angle\nClick to display a drop-down list with the following options:\nArc Angle\nAllows you to draw arcs by specifying their centre points, start points and sweep angles. Refer to Draw Arc with Specified Center, End and Angle for further information.\nArc Three-Points\nAllows you to draw arcs by specifying their start points, end points and through points. Refer to Draw Arc with Specified Start, End and Through Points for further information.\nTriangle\nAllows you to draw equilateral triangles. Refer to Draw Equilateral Triangles for further information.\nHexagon End-Point\nClick to display a drop-down list with the following options:\nHexagon End-Point\nAllows you to draw hexagons by specifying their centre to point radius. Refer toDraw Hexagon with Specified Center to Point Radius for further information.\nHexagon Two-Points\nAllows you to draw hexagons by specifying their point to point diameters. Refer to Draw Hexagon with Specified Point to Point Diameter for further information.\nHexagon Edge\nAllows you to draw hexagons by specifying their centre to side radius. Refer to Draw Hexagon with Specified Center to Side Radius for further information.\nAxis - Axis-Edge\nClick to display a drop-down list with the following options:\nEllipse Axis-Edge\nAllows you to draw ellipses by specifying the length of their axes. Refer to Draw Ellipse with Specified Length of Axes for further information.\nEllipse Centre\nAllows you to draw ellipses by specifying the radius of the first axis and the length of the second. Refer to Draw Ellipse with Specified Radius of First Axis and Length of Second for further information.\nElliptical Arc\nAllows you to draw elliptical arcs. Refer to Draw Elliptical Arc with Specified Axes, Start and End Angle for further information.\nTangent\nAllows you to draw tangent lines. Refer to Draw Tangent Lines for further information.\nConnector\nAllows you to draw connectors. Refer to Draw Connectors for further information.\nConstruct Group\nRay Line\nAllows you to draw ray lines. Refer to Add Ray Lines for further information.\nXLine\nClick to display a drop-down list with the following options:\nXLine\nAllows you to draw xlines by selecting two points. Refer to Add XLines with Two Selected Points for further information.\nHorizontal\nAllows you to draw horizontal xlines. Refer to Add Horizontal XLines for further information.\nVertical\nAllows you to draw vertical xlines. Refer to Add Vertical XLines for further information.\nAngle\nAllows you to draw xlines at a specified angle. Refer to Add XLines with a Specified Angle for further information.\nBisect\nAllows you to draw bisecting xlines. Refer to Add Bisect XLines for further information.\nModify Group\nMove\nAllows you to move objects. Refer to Move Objects for further information.\nCopy & Paste\nAllows you to copy and paste objects. Refer to Copy and Paste Objects for further information.\nOffset\nAllows you to offset objects. Refer to Offset Objects for further information.\nRotate\nAllows you to rotate objects. Refer to Rotate Objects for further information.\nMirror\nAllows you to mirror objects. Refer to Mirror Objects for further information.\nScale\nAllows you to scale objects. Refer to Scale Objects for further information.\nArray\nAllows you to create arrays of objects. Refer to Create Arrays of Objects for further information.\nStretch\nAllows you to stretch objects. Refer to Stretch Objects for further information.\nExplode\nClick to display a drop-down list with the following options:\nExplode\nAllows you to explode objects. Refer to Explode Objects for further information.\nMerge\nAllows you to merge objects. Refer to Merge Objects for further information.\nLengthen\nAllows you to change the length of objects. Refer to Change Length of Objects for further information.\nTrim\nClick to display a drop-down list with the following options:\nTrim\nAllows you to trim objects. Refer to Trim Objects for further information.\nExtend\nAllows you to extend objects. Refer to Extend Objects for further information.\nFillet\nClick to display a drop-down list with the following options:\nFillet\nAllows you to fillet objects with a radius of 0 degrees. Refer to Fillet Objects for further information.\nFilletR\nAllows you to fillet objects with a selected fillet arc radius. Refer to Fillet Objects for further information.\nChamfer\nAllows you to chamfer objects. Refer to Chamfer Objects for further information.\nSend to Back\nAllows you to move objects to the back of the drawing canvas. Refer to Send to Back for further information.\nBring to Front\nAllows you to move objects to the front of the drawing canvas. Refer to Bring to Front for further information.\nAlign Views\nAllows you to align views on the drawing canvas, views can be aligned horizontally or vertically. Refer to Align Views for further information.\nQuick Add\nAllows you to quickly and easily add model elements to selected views. Refer to Quick Add for further information.\nDelete Group\nDelete\nAllows you to delete objects. Refer to Delete for further information.\nCloud\nOutline\nCloud\nCloud\nOutline\nOutline\n\n\n\nMeasure Distance between Two Points\nMeasure Cumulative Lengths of Objects\nDisplay Point Coordinates\nDraw Lines\nDraw Rectangles and Diamonds\nDraw Rectangles and Diamonds\nDraw Arc with Specified Center, End and Angle\nDraw Arc with Specified Start, End and Through Points\nDraw Equilateral Triangles\nDraw Hexagon with Specified Center to Point Radius\nDraw Hexagon with Specified Point to Point Diameter\nDraw Hexagon with Specified Center to Side Radius\nDraw Ellipse with Specified Length of Axes\nDraw Ellipse with Specified Radius of First Axis and Length of Second\nDraw Elliptical Arc with Specified Axes, Start and End Angle\nDraw Tangent Lines\nDraw Connectors\nAdd Ray Lines\nAdd XLines with Two Selected Points\nAdd Horizontal XLines\nAdd Vertical XLines\nAdd XLines with a Specified Angle\nAdd Bisect XLines\nMove Objects\nCopy and Paste Objects\nOffset Objects\nRotate Objects\nMirror Objects\nScale Objects\nCreate Arrays of Objects\nStretch Objects\nExplode Objects\nMerge Objects\nChange Length of Objects\nTrim Objects\nExtend Objects\nFillet Objects\nFillet Objects\nChamfer Objects\nSend to Back\nBring to Front\nAlign Views\nQuick Add\nDelete\nMeasure Group\nDistance\nMeasure Distance between Two Points\nAngle\nMeasure Angle between two Points\nCumulative Length\nMeasure Cumulative Lengths of Objects\nID Point\nDisplay Point Coordinates\nDraw Group\nLine\nDraw Lines\nCloud\nDraw Clouds and Outlines\nCircle Centre-Radius\nCircle Centre-Radius\nDraw Circle with Specified Radius\nCircle Two-Points\nDraw Circle with Two Specified Points\nCircle Centre- Diameter\nDraw Circle with Specified Diameter\nRectangle\nRectangle\nDraw Rectangles and Diamonds\nDiamond\nDraw Rectangles and Diamonds\nArc Angle\nArc Angle\nDraw Arc with Specified Center, End and Angle\nArc Three-Points\nDraw Arc with Specified Start, End and Through Points\nTriangle\nDraw Equilateral Triangles\nHexagon End-Point\nHexagon End-Point\nDraw Hexagon with Specified Center to Point Radius\nHexagon Two-Points\nDraw Hexagon with Specified Point to Point Diameter\nHexagon Edge\nDraw Hexagon with Specified Center to Side Radius\nAxis - Axis-Edge\nEllipse Axis-Edge\nDraw Ellipse with Specified Length of Axes\nEllipse Centre\nDraw Ellipse with Specified Radius of First Axis and Length of Second\nElliptical Arc\nDraw Elliptical Arc with Specified Axes, Start and End Angle\nTangent\nDraw Tangent Lines\nConnector\nDraw Connectors\nConstruct Group\nRay Line\nAdd Ray Lines\nXLine\nXLine\nAdd XLines with Two Selected Points\nHorizontal\nAdd Horizontal XLines\nVertical\nAdd Vertical XLines\nAngle\nAdd XLines with a Specified Angle\nBisect\nAdd Bisect XLines\nModify Group\nMove\nMove Objects\nCopy & Paste\nCopy and Paste Objects\nOffset\nOffset Objects\nRotate\nRotate Objects\nMirror\nMirror Objects\nScale\nScale Objects\nArray\nCreate Arrays of Objects\nStretch\nStretch Objects\nExplode\nExplode\nExplode Objects\nMerge\nMerge Objects\nLengthen\nChange Length of Objects\nTrim\nTrim\nTrim Objects\nExtend\nExtend Objects\nFillet\nFillet\nFillet Objects\nFilletR\nFillet Objects\nChamfer\nChamfer Objects\nSend to Back\nSend to Back\nBring to Front\nBring to Front\nAlign Views\nAlign Views\nQuick Add\nQuick Add\nDelete Group\nDelete\nDelete"}
{"Headers": "Annotate", "Content": "\n\nInsert Group\nText\nAllows you to add text to a drawing. Refer to Add Text to Drawings for further information\nSymbol\nAllows you to insert symbols. Refer to Add Symbols to Drawings for further information.\nImage\nAllows you to insert images. Refer to Add Images to Drawings for further information.\nTable\nAllows you to add intelligent tables to a drawing. Refer to Add Tables to Drawings for further information.\nOverlay\nAllows you to add an overlay to a sheet. Refer to Add Overlays to Drawings for further information.\nMarker\nAllows you to place marker points on a drawing. Refer to Add Marker Points for further information.\nConnection Point\nAllows you add connection points on a symbol (SYMB) element. Refer to Add Connection Points for further information.\nAnnotate Group\nLabel\nAllows you to label design objects. Refer to Label Objects for further information.\nAdvanced\nClick to display a drop-down list with the following options:\nWeight and CoG\nAllows you to add a weight and centre of gravity label to a view. Refer to Weight and Center of Gravity Label for further information.\n3D Coordinate\nAllows you to add labels containing positional information to a view. Refer to 3D Coordinate Label for further information.\nAuto-Tag\nAllows you to apply automatic tagging to design objects. Refer to Automatic Tagging for further information.\nPipe End Labels\nAllows you to add labels to pipe ends. Refer to Pipe End Labels for further information.\nClick to display a drop-down list with the following options:\nIdentified\nAutomatic\nLabel Placement\nClick to display a drop-down list with the following options:\nLabel Placement\nAllows you to tidy up crowded areas of labelling, minimizing label overlap and leader-line crossing. Refer to Label Placement for further information.\nLabel Alignment\nAllows you to horizontally or vertically align labels and text annotations,. Refer to Label Alignment for further information.\nGap\nAllows you to add gaps to label leader lines. Refer to Leader Line Gaps for further information.\nAcross PCD\nAllows you to add various types of pitch circle dimension annotations. Refer to Add Pitch Circle Dimensions for further information.\nClick to display a drop-down list with the following options:\nAcross PCD\nAcross PCD Leaderline\nPCD Leaderline\nPCD Pointer Leaderline\nPCD Internal Leaderline\nInternal PCR\nInternal PCR Leaderline\nExternal PCR Leaderline\nExternal PCR Pointer Leaderline\nPCR Internal Leaderline\nAcross Diameter\nAllows you to add various types of radial dimension annotations. Refer to Add Radial Dimensions for further information.\nClick to display a drop-down list with the following options:\nAcross Diameter\nAcross Diameter Leaderline\nDiameter Leaderline\nDiameter Pointer Leaderline\nDiameter Internal Leaderline\nInternal Radius\nInternal Radius Leaderline\nExternal Radius Leaderline\nExternal Point Leaderline\nRadius Internal Leaderline\nChained\nAllows you to add various types of angular dimension annotations. Refer to Add Angular Dimensions for further information.\nClick to display a drop-down list with the following options:\nChained\nBaseline\nCombined\nOrthogonal Chained\nAllows you to add various types of linear dimension annotations. Refer to Add Linear Dimensions for further information.\nClick to display a drop-down list with the following options:\nOrthogonal Chained\nAligned Chained\nCombined Left\nCombined Right\nAligned Combined\nBaseline Left\nBaseline Right\nAligned Baseline\nGrid Ruler\nClick to display a drop-down list with the following options:\nGrid Ruler\nAllows you to add a grid ruler to an orthogonal view. Refer to Create Grid Ruler for further information.\nBase Line Ruler\nAllows you to add a base line ruler to an orthogonal view. Refer to Create Base Line Ruler for further information.\nCentre Line Ruler\nAllows you to add a centre line ruler to an orthogonal view. Refer to Create Center Line Ruler for further information.\nBase Line and Centre Line Ruler\nAllows you to add a base line and a centre line ruler to an orthogonal view. Refer to Create Center Line and Base Line Ruler for further information.\nTools Group\nClean Up Annotation\nAllows you to delete elements with null or illegal design element reference (DDNM) attributes. Refer to Clean Up Annotations for further information.\nSort Dimensions\nAllows you to reorder dimensions that are not in the correct order. Refer to Sort Dimensions for further information.\nFill\nAllows you to fill objects on a drawing. Refer to Fill Objects for further information.\nBlanking Margin\nAllows you to set the blanking margin for all labels and dimensions on a sheet. Refer to Label and Dimension Blanking for further information.\nEnable Blanking\nAllows you to turn blanking on for all labels and dimensions on a sheet. Refer to Label and Dimension Blanking for further information.\nDisable Blanking\nAllows you to turn blanking off for all labels and dimensions on a sheet. Refer to Label and Dimension Blanking for further information.\nHidden Annotation\nTurns the display of annotations on or off. Refer to Hidden Annotation for further information.\nModel Ref. Check\nTurns the Model Reference Check feature on or off. Refer to Model Reference Check for further information.\nPrimitives\nSelect the toggle option to apply the Model Reference Check or Model Invalid Reference Check to primitives. Refer to Model Reference Check or Model Invalid Reference Check for further information.\nLabels\nSelect the toggle option to apply the Model Reference Check or Model Invalid Reference Check to labels. Refer to Model Reference Check or Model Invalid Reference Check for further information.\nDimensions\nSelect the toggle option to apply the Model Reference Check or Model Invalid Reference Check to dimensions. Refer to Model Reference Check or Model Invalid Reference Check for further information.\nModel Invalid Ref. Check\nTurns the Model Invalid Reference Check feature on or off. Refer to Model Invalid Reference Check for further information.\nInsert Group\nText\nAllows you to add text to a drawing. Refer to Add Text to Drawings for further information\nSymbol\nAllows you to insert symbols. Refer to Add Symbols to Drawings for further information.\nImage\nAllows you to insert images. Refer to Add Images to Drawings for further information.\nTable\nAllows you to add intelligent tables to a drawing. Refer to Add Tables to Drawings for further information.\nOverlay\nAllows you to add an overlay to a sheet. Refer to Add Overlays to Drawings for further information.\nMarker\nAllows you to place marker points on a drawing. Refer to Add Marker Points for further information.\nConnection Point\nAllows you add connection points on a symbol (SYMB) element. Refer to Add Connection Points for further information.\nAnnotate Group\nLabel\nAllows you to label design objects. Refer to Label Objects for further information.\nAdvanced\nClick to display a drop-down list with the following options:\nAllows you to add a weight and centre of gravity label to a view. Refer to Weight and Center of Gravity Label for further information.\nAllows you to add labels containing positional information to a view. Refer to 3D Coordinate Label for further information.\nAuto-Tag\nAllows you to apply automatic tagging to design objects. Refer to Automatic Tagging for further information.\nPipe End Labels\nAllows you to add labels to pipe ends. Refer to Pipe End Labels for further information.\nClick to display a drop-down list with the following options:\nLabel Placement\nClick to display a drop-down list with the following options:\nAllows you to tidy up crowded areas of labelling, minimizing label overlap and leader-line crossing. Refer to Label Placement for further information.\nAllows you to horizontally or vertically align labels and text annotations,. Refer to Label Alignment for further information.\nGap\nAllows you to add gaps to label leader lines. Refer to Leader Line Gaps for further information.\nAcross PCD\nAllows you to add various types of pitch circle dimension annotations. Refer to Add Pitch Circle Dimensions for further information.\nClick to display a drop-down list with the following options:\nAcross Diameter\nAllows you to add various types of radial dimension annotations. Refer to Add Radial Dimensions for further information.\nClick to display a drop-down list with the following options:\nChained\nAllows you to add various types of angular dimension annotations. Refer to Add Angular Dimensions for further information.\nClick to display a drop-down list with the following options:\nOrthogonal Chained\nAllows you to add various types of linear dimension annotations. Refer to Add Linear Dimensions for further information.\nClick to display a drop-down list with the following options:\nGrid Ruler\nClick to display a drop-down list with the following options:\nAllows you to add a grid ruler to an orthogonal view. Refer to Create Grid Ruler for further information.\nAllows you to add a base line ruler to an orthogonal view. Refer to Create Base Line Ruler for further information.\nAllows you to add a centre line ruler to an orthogonal view. Refer to Create Center Line Ruler for further information.\nAllows you to add a base line and a centre line ruler to an orthogonal view. Refer to Create Center Line and Base Line Ruler for further information.\n\nClean Up Annotation\nAllows you to delete elements with null or illegal design element reference (DDNM) attributes. Refer to Clean Up Annotations for further information.\nSort Dimensions\nAllows you to reorder dimensions that are not in the correct order. Refer to Sort Dimensions for further information.\nFill\nAllows you to fill objects on a drawing. Refer to Fill Objects for further information.\nBlanking Margin\nAllows you to set the blanking margin for all labels and dimensions on a sheet. Refer to Label and Dimension Blanking for further information.\nEnable Blanking\nAllows you to turn blanking on for all labels and dimensions on a sheet. Refer to Label and Dimension Blanking for further information.\nDisable Blanking\nAllows you to turn blanking off for all labels and dimensions on a sheet. Refer to Label and Dimension Blanking for further information.\nHidden Annotation\nTurns the display of annotations on or off. Refer to Hidden Annotation for further information.\nModel Ref. Check\nTurns the Model Reference Check feature on or off. Refer to Model Reference Check for further information.\nPrimitives\nSelect the toggle option to apply the Model Reference Check or Model Invalid Reference Check to primitives. Refer to Model Reference Check or Model Invalid Reference Check for further information.\nLabels\nSelect the toggle option to apply the Model Reference Check or Model Invalid Reference Check to labels. Refer to Model Reference Check or Model Invalid Reference Check for further information.\nDimensions\nSelect the toggle option to apply the Model Reference Check or Model Invalid Reference Check to dimensions. Refer to Model Reference Check or Model Invalid Reference Check for further information.\nModel Invalid Ref. Check\nTurns the Model Invalid Reference Check feature on or off. Refer to Model Invalid Reference Check for further information.\n\nInsert Group\nText\nAllows you to add text to a drawing. Refer to Add Text to Drawings for further information\nSymbol\nAllows you to insert symbols. Refer to Add Symbols to Drawings for further information.\nImage\nAllows you to insert images. Refer to Add Images to Drawings for further information.\nTable\nAllows you to add intelligent tables to a drawing. Refer to Add Tables to Drawings for further information.\nOverlay\nAllows you to add an overlay to a sheet. Refer to Add Overlays to Drawings for further information.\nMarker\nAllows you to place marker points on a drawing. Refer to Add Marker Points for further information.\nConnection Point\nAllows you add connection points on a symbol (SYMB) element. Refer to Add Connection Points for further information.\nAnnotate Group\nLabel\nAllows you to label design objects. Refer to Label Objects for further information.\nAdvanced\nClick to display a drop-down list with the following options:\nWeight and CoG\nAllows you to add a weight and centre of gravity label to a view. Refer to Weight and Center of Gravity Label for further information.\n3D Coordinate\nAllows you to add labels containing positional information to a view. Refer to 3D Coordinate Label for further information.\nAuto-Tag\nAllows you to apply automatic tagging to design objects. Refer to Automatic Tagging for further information.\nPipe End Labels\nAllows you to add labels to pipe ends. Refer to Pipe End Labels for further information.\nClick to display a drop-down list with the following options:\nIdentified\nAutomatic\nLabel Placement\nClick to display a drop-down list with the following options:\nLabel Placement\nAllows you to tidy up crowded areas of labelling, minimizing label overlap and leader-line crossing. Refer to Label Placement for further information.\nLabel Alignment\nAllows you to horizontally or vertically align labels and text annotations,. Refer to Label Alignment for further information.\nGap\nAllows you to add gaps to label leader lines. Refer to Leader Line Gaps for further information.\nAcross PCD\nAllows you to add various types of pitch circle dimension annotations. Refer to Add Pitch Circle Dimensions for further information.\nClick to display a drop-down list with the following options:\nAcross PCD\nAcross PCD Leaderline\nPCD Leaderline\nPCD Pointer Leaderline\nPCD Internal Leaderline\nInternal PCR\nInternal PCR Leaderline\nExternal PCR Leaderline\nExternal PCR Pointer Leaderline\nPCR Internal Leaderline\nAcross Diameter\nAllows you to add various types of radial dimension annotations. Refer to Add Radial Dimensions for further information.\nClick to display a drop-down list with the following options:\nAcross Diameter\nAcross Diameter Leaderline\nDiameter Leaderline\nDiameter Pointer Leaderline\nDiameter Internal Leaderline\nInternal Radius\nInternal Radius Leaderline\nExternal Radius Leaderline\nExternal Point Leaderline\nRadius Internal Leaderline\nChained\nAllows you to add various types of angular dimension annotations. Refer to Add Angular Dimensions for further information.\nClick to display a drop-down list with the following options:\nChained\nBaseline\nCombined\nOrthogonal Chained\nAllows you to add various types of linear dimension annotations. Refer to Add Linear Dimensions for further information.\nClick to display a drop-down list with the following options:\nOrthogonal Chained\nAligned Chained\nCombined Left\nCombined Right\nAligned Combined\nBaseline Left\nBaseline Right\nAligned Baseline\nGrid Ruler\nClick to display a drop-down list with the following options:\nGrid Ruler\nAllows you to add a grid ruler to an orthogonal view. Refer to Create Grid Ruler for further information.\nBase Line Ruler\nAllows you to add a base line ruler to an orthogonal view. Refer to Create Base Line Ruler for further information.\nCentre Line Ruler\nAllows you to add a centre line ruler to an orthogonal view. Refer to Create Center Line Ruler for further information.\nBase Line and Centre Line Ruler\nAllows you to add a base line and a centre line ruler to an orthogonal view. Refer to Create Center Line and Base Line Ruler for further information.\nTools Group\nClean Up Annotation\nAllows you to delete elements with null or illegal design element reference (DDNM) attributes. Refer to Clean Up Annotations for further information.\nSort Dimensions\nAllows you to reorder dimensions that are not in the correct order. Refer to Sort Dimensions for further information.\nFill\nAllows you to fill objects on a drawing. Refer to Fill Objects for further information.\nBlanking Margin\nAllows you to set the blanking margin for all labels and dimensions on a sheet. Refer to Label and Dimension Blanking for further information.\nEnable Blanking\nAllows you to turn blanking on for all labels and dimensions on a sheet. Refer to Label and Dimension Blanking for further information.\nDisable Blanking\nAllows you to turn blanking off for all labels and dimensions on a sheet. Refer to Label and Dimension Blanking for further information.\nHidden Annotation\nTurns the display of annotations on or off. Refer to Hidden Annotation for further information.\nModel Ref. Check\nTurns the Model Reference Check feature on or off. Refer to Model Reference Check for further information.\nPrimitives\nSelect the toggle option to apply the Model Reference Check or Model Invalid Reference Check to primitives. Refer to Model Reference Check or Model Invalid Reference Check for further information.\nLabels\nSelect the toggle option to apply the Model Reference Check or Model Invalid Reference Check to labels. Refer to Model Reference Check or Model Invalid Reference Check for further information.\nDimensions\nSelect the toggle option to apply the Model Reference Check or Model Invalid Reference Check to dimensions. Refer to Model Reference Check or Model Invalid Reference Check for further information.\nModel Invalid Ref. Check\nTurns the Model Invalid Reference Check feature on or off. Refer to Model Invalid Reference Check for further information.\nIdentified\nAutomatic\nIdentified\nIdentified\nAutomatic\nAutomatic\nAcross PCD\nAcross PCD Leaderline\nPCD Leaderline\nPCD Pointer Leaderline\nPCD Internal Leaderline\nInternal PCR\nInternal PCR Leaderline\nExternal PCR Leaderline\nExternal PCR Pointer Leaderline\nPCR Internal Leaderline\nAcross PCD\nAcross PCD\nAcross PCD Leaderline\nAcross PCD Leaderline\nPCD Leaderline\nPCD Leaderline\nPCD Pointer Leaderline\nPCD Pointer Leaderline\nPCD Internal Leaderline\nPCD Internal Leaderline\nInternal PCR\nInternal PCR\nInternal PCR Leaderline\nInternal PCR Leaderline\nExternal PCR Leaderline\nExternal PCR Leaderline\nExternal PCR Pointer Leaderline\nExternal PCR Pointer Leaderline\nPCR Internal Leaderline\nPCR Internal Leaderline\nAcross Diameter\nAcross Diameter Leaderline\nDiameter Leaderline\nDiameter Pointer Leaderline\nDiameter Internal Leaderline\nInternal Radius\nInternal Radius Leaderline\nExternal Radius Leaderline\nExternal Point Leaderline\nRadius Internal Leaderline\nAcross Diameter\nAcross Diameter\nAcross Diameter Leaderline\nAcross Diameter Leaderline\nDiameter Leaderline\nDiameter Leaderline\nDiameter Pointer Leaderline\nDiameter Pointer Leaderline\nDiameter Internal Leaderline\nDiameter Internal Leaderline\nInternal Radius\nInternal Radius\nInternal Radius Leaderline\nInternal Radius Leaderline\nExternal Radius Leaderline\nExternal Radius Leaderline\nExternal Point Leaderline\nExternal Point Leaderline\nRadius Internal Leaderline\nRadius Internal Leaderline\nChained\nBaseline\nCombined\nChained\nChained\nBaseline\nBaseline\nCombined\nCombined\nOrthogonal Chained\nAligned Chained\nCombined Left\nCombined Right\nAligned Combined\nBaseline Left\nBaseline Right\nAligned Baseline\nOrthogonal Chained\nOrthogonal Chained\nAligned Chained\nAligned Chained\nCombined Left\nCombined Left\nCombined Right\nCombined Right\nAligned Combined\nAligned Combined\nBaseline Left\nBaseline Left\nBaseline Right\nBaseline Right\nAligned Baseline\nAligned Baseline\n\n\n\nAdd Text to Drawings\nAdd Symbols to Drawings\nAdd Images to Drawings\nAdd Tables to Drawings\nAdd Overlays to Drawings\nAdd Marker Points\nAdd Connection Points\nLabel Objects\nWeight and Center of Gravity Label\n3D Coordinate Label\nAutomatic Tagging\nPipe End Labels\nLabel Placement\nLabel Alignment\nLeader Line Gaps\nAdd Pitch Circle Dimensions\nAdd Radial Dimensions\nAdd Angular Dimensions\nAdd Linear Dimensions\nCreate Grid Ruler\nCreate Base Line Ruler\nCreate Center Line Ruler\nCreate Center Line and Base Line Ruler\nClean Up Annotations\nSort Dimensions\nFill Objects\nLabel and Dimension Blanking\nLabel and Dimension Blanking\nLabel and Dimension Blanking\nHidden Annotation\nModel Reference Check\nModel Reference Check\nModel Invalid Reference Check\nModel Reference Check\nModel Invalid Reference Check\nModel Reference Check\nModel Invalid Reference Check\nModel Invalid Reference Check\nInsert Group\nText\nAdd Text to Drawings\nSymbol\nAdd Symbols to Drawings\nImage\nAdd Images to Drawings\nTable\nAdd Tables to Drawings\nOverlay\nAdd Overlays to Drawings\nMarker\nAdd Marker Points\nConnection Point\nAdd Connection Points\nAnnotate Group\nLabel\nLabel Objects\nAdvanced\nWeight and CoG\nWeight and Center of Gravity Label\n3D Coordinate\n3D Coordinate Label\nAuto-Tag\nAutomatic Tagging\nPipe End Labels\nPipe End Labels\nLabel Placement\nLabel Placement\nLabel Placement\nLabel Alignment\nLabel Alignment\nGap\nLeader Line Gaps\nAcross PCD\nAdd Pitch Circle Dimensions\nAcross Diameter\nAdd Radial Dimensions\nChained\nAdd Angular Dimensions\nOrthogonal Chained\nAdd Linear Dimensions\nGrid Ruler\nGrid Ruler\nCreate Grid Ruler\nBase Line Ruler\nCreate Base Line Ruler\nCentre Line Ruler\nCreate Center Line Ruler\nBase Line and Centre Line Ruler\nCreate Center Line and Base Line Ruler\nClean Up Annotation\nClean Up Annotations\nSort Dimensions\nSort Dimensions\nFill\nFill Objects\nBlanking Margin\nLabel and Dimension Blanking\nEnable Blanking\nLabel and Dimension Blanking\nDisable Blanking\nLabel and Dimension Blanking\nHidden Annotation\nHidden Annotation\nModel Ref. Check\nModel Reference Check\nPrimitives\nModel Reference Check\nModel Invalid Reference Check\nLabels\nModel Reference Check\nModel Invalid Reference Check\nDimensions\nModel Reference Check\nModel Invalid Reference Check\nModel Invalid Ref. Check\nModel Invalid Reference Check"}
{"Headers": "Update", "Content": "\nAdvanced Group\nPicture\nAllows you to update picture files. Refer to System Update for further information.\nBacking Sheets\nAllows you to update backing sheets with any database changes. Refer to System Update for further information.\nInstances\nAllows you to update template instancing. Refer to System Update for further information.\nDrawing Group\nDesign\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to update the sheet with any design changes from the database. Refer to Drawing Elements for further details.\nCurrent Owner\nSelect from the drop-down list to update the current owner with any design changes from the database. Refer to Current Owner for further details.\nNote:\nThe changes are applied automatically if is set on the Status Bar.\nAnnotation\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to update the sheet with any annotation changes from the database. Refer to Drawing Elements for further details.\nCurrent Owner\nSelect from the drop-down list to update the current owner with any annotation changes from the database. Refer to Current Owner for further details.\nAll\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to update the sheet with any design and annotation changes from the database. Refer to Drawing Elements for further details.\nCurrent Owner\nSelect from the drop-down list to update the current owner with any design and annotation changes from the database. Refer to Current Owner for further details.\nGrid Annotations Group\nUpdate\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to manually update the sheet with any reference grid annotation changes from the database. Refer to Update and Regenerate Reference Grid Annotations for further details.\nCurrent Owner\nSelect from the drop-down list to manually update the current owner with any reference grid annotation changes from the database. Refer to Current Owner for further details.\nRegenerate\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to manually regenerate the sheet with any reference grid annotation changes from the database. Refer to Update and Regenerate Reference Grid Annotations for further details.\nCurrent Owner\nSelect from the drop-down list to manually regenerate the current owner with any reference grid annotation changes from the database. Refer to Current Owner for further information.\nTagging Group\nTagging\nAllows you to update automatically generated labels with any database changes. Refer to Update and Regenerate Tagging for further details.\nAutolabels Group\nUpdate\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to manually update the sheet with any autolabel annotation changes from the database. Refer to Update and Regenerate Autolabels for further details.\nCurrent Owner\nSelect from the drop-down list to manually update the current owner with any autolabel annotation changes from the database. Refer to Current Owner for further details.\nRegenerate\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to manually regenerate the sheet with any autolabel annotation changes from the database. Refer to Update and Regenerate Autolabels for further details.\nCurrent Owner\nSelect from the drop-down list to manually regenerate the current owner with any autolabel annotation changes from the database. Refer to Current Owner for further information.\nAdvanced Group\nPicture\nAllows you to update picture files. Refer to System Update for further information.\nBacking Sheets\nAllows you to update backing sheets with any database changes. Refer to System Update for further information.\nInstances\nAllows you to update template instancing. Refer to System Update for further information.\nDrawing Group\nDesign\nClick to display a drop-down list with the following options:\nSelect from the drop-down list to update the sheet with any design changes from the database. Refer to Drawing Elements for further details.\nSelect from the drop-down list to update the current owner with any design changes from the database. Refer to Current Owner for further details.\nAnnotation\nClick to display a drop-down list with the following options:\nSelect from the drop-down list to update the sheet with any annotation changes from the database. Refer to Drawing Elements for further details.\nSelect from the drop-down list to update the current owner with any annotation changes from the database. Refer to Current Owner for further details.\nAll\nClick to display a drop-down list with the following options:\nSelect from the drop-down list to update the sheet with any design and annotation changes from the database. Refer to Drawing Elements for further details.\nSelect from the drop-down list to update the current owner with any design and annotation changes from the database. Refer to Current Owner for further details.\nGrid Annotations Group\nUpdate\nClick to display a drop-down list with the following options:\nSelect from the drop-down list to manually update the sheet with any reference grid annotation changes from the database. Refer to Update and Regenerate Reference Grid Annotations for further details.\nSelect from the drop-down list to manually update the current owner with any reference grid annotation changes from the database. Refer to Current Owner for further details.\nRegenerate\nClick to display a drop-down list with the following options:\nSelect from the drop-down list to manually regenerate the sheet with any reference grid annotation changes from the database. Refer to Update and Regenerate Reference Grid Annotations for further details.\nSelect from the drop-down list to manually regenerate the current owner with any reference grid annotation changes from the database. Refer to Current Owner for further information.\nTagging Group\nTagging\nAllows you to update automatically generated labels with any database changes. Refer to Update and Regenerate Tagging for further details.\nAutolabels Group\nUpdate\nClick to display a drop-down list with the following options:\nSelect from the drop-down list to manually update the sheet with any autolabel annotation changes from the database. Refer to Update and Regenerate Autolabels for further details.\nSelect from the drop-down list to manually update the current owner with any autolabel annotation changes from the database. Refer to Current Owner for further details.\nRegenerate\nClick to display a drop-down list with the following options:\nSelect from the drop-down list to manually regenerate the sheet with any autolabel annotation changes from the database. Refer to Update and Regenerate Autolabels for further details.\nSelect from the drop-down list to manually regenerate the current owner with any autolabel annotation changes from the database. Refer to Current Owner for further information.\n\nAdvanced Group\nPicture\nAllows you to update picture files. Refer to System Update for further information.\nBacking Sheets\nAllows you to update backing sheets with any database changes. Refer to System Update for further information.\nInstances\nAllows you to update template instancing. Refer to System Update for further information.\nDrawing Group\nDesign\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to update the sheet with any design changes from the database. Refer to Drawing Elements for further details.\nCurrent Owner\nSelect from the drop-down list to update the current owner with any design changes from the database. Refer to Current Owner for further details.\nNote:\nThe changes are applied automatically if is set on the Status Bar.\nAnnotation\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to update the sheet with any annotation changes from the database. Refer to Drawing Elements for further details.\nCurrent Owner\nSelect from the drop-down list to update the current owner with any annotation changes from the database. Refer to Current Owner for further details.\nAll\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to update the sheet with any design and annotation changes from the database. Refer to Drawing Elements for further details.\nCurrent Owner\nSelect from the drop-down list to update the current owner with any design and annotation changes from the database. Refer to Current Owner for further details.\nGrid Annotations Group\nUpdate\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to manually update the sheet with any reference grid annotation changes from the database. Refer to Update and Regenerate Reference Grid Annotations for further details.\nCurrent Owner\nSelect from the drop-down list to manually update the current owner with any reference grid annotation changes from the database. Refer to Current Owner for further details.\nRegenerate\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to manually regenerate the sheet with any reference grid annotation changes from the database. Refer to Update and Regenerate Reference Grid Annotations for further details.\nCurrent Owner\nSelect from the drop-down list to manually regenerate the current owner with any reference grid annotation changes from the database. Refer to Current Owner for further information.\nTagging Group\nTagging\nAllows you to update automatically generated labels with any database changes. Refer to Update and Regenerate Tagging for further details.\nAutolabels Group\nUpdate\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to manually update the sheet with any autolabel annotation changes from the database. Refer to Update and Regenerate Autolabels for further details.\nCurrent Owner\nSelect from the drop-down list to manually update the current owner with any autolabel annotation changes from the database. Refer to Current Owner for further details.\nRegenerate\nClick to display a drop-down list with the following options:\nSheet\nSelect from the drop-down list to manually regenerate the sheet with any autolabel annotation changes from the database. Refer to Update and Regenerate Autolabels for further details.\nCurrent Owner\nSelect from the drop-down list to manually regenerate the current owner with any autolabel annotation changes from the database. Refer to Current Owner for further information.\nNote:\nThe changes are applied automatically if is set on the Status Bar.\n\n\n\nSystem Update\nSystem Update\nSystem Update\nDrawing Elements\nCurrent Owner\nStatus Bar\nDrawing Elements\nCurrent Owner\nDrawing Elements\nCurrent Owner\nUpdate and Regenerate Reference Grid Annotations\nCurrent Owner\nUpdate and Regenerate Reference Grid Annotations\nCurrent Owner\nUpdate and Regenerate Tagging\nUpdate and Regenerate Autolabels\nCurrent Owner\nUpdate and Regenerate Autolabels\nCurrent Owner\nAdvanced Group\nPicture\nSystem Update\nBacking Sheets\nSystem Update\nInstances\nSystem Update\nDrawing Group\nDesign\nSheet\nDrawing Elements\nCurrent Owner\nCurrent Owner\nNote\n:\nStatus Bar\nAnnotation\nSheet\nDrawing Elements\nCurrent Owner\nCurrent Owner\nAll\nSheet\nDrawing Elements\nCurrent Owner\nCurrent Owner\nGrid Annotations Group\nUpdate\nSheet\nUpdate and Regenerate Reference Grid Annotations\nCurrent Owner\nCurrent Owner\nRegenerate\nSheet\nUpdate and Regenerate Reference Grid Annotations\nCurrent Owner\nCurrent Owner\nTagging Group\nTagging\nUpdate and Regenerate Tagging\nAutolabels Group\nUpdate\nSheet\nUpdate and Regenerate Autolabels\nCurrent Owner\nCurrent Owner\nRegenerate\nSheet\nUpdate and Regenerate Autolabels\nCurrent Owner\nCurrent Owner"}
{"Headers": "Tools", "Content": "\n\nDisplay Group\nCommands\nClick to display the Command Window. Refer to Command Window for further information.\nMessages\nClick to display the Messages window, which displays a list of messages issued by the application during the session. Refer to Messages for further information.\nAppware Load Errors\nClick to display the Default Load Errors window. Refer to Appware Load Errors for further information.\nExplorers Group\nDraw Explorer\nAllows you to open and close the Draw Explorer. Refer to Draw Explorer for further information.\nDepartment\nClick to display a drop-down list with the following options:\nCreate\nAllows you to create a new department. Refer to Create and Modify Departments for further information.\nModify\nAllows you to modify the attributes of a department. Refer to Modify Department Attributes for further information.\nRegistry\nClick to display a drop-down list with the following options:\nCreate\nAllows you to create a new registry. Refer to Create and Modify Registries for further information.\nModify\nAllows you to modify the attributes of a registry. Refer to Modify Registry Attributes for further information.\nDrawing\nClick to display a drop-down list with the following options:\nCreate Explicitly\nAllows you to create a new drawing. Refer to Create and Modify Departments for further information.\nModify\nAllows you to modify the attributes of a drawing Refer to Modify Drawing Attributes for further information.\nModel Explorer\nAllows you to open and close the Model Explorer. Refer to Model Explorer for further information.\nFabrication Explorer\nAllows you to open and close the Model Explorer. Refer to Fabrication Explorer for further information.\nIFC Explorer\nAllows you to open and close the IFC Flexible Explorer. Refer to IFC Flexible Explorer for further information.\nMultiCAD Explorer\nAllows you to open and close the MultiCAD Explorer. Refer to MultiCAD Flexible Explorer in Draw for further information.\nSearch Group\nSearch\nAllows you to open and close the Search and Search Result windows. Refer to Search for further information.\nCollections\nReport Group\nRun Report\nAllows you to run pre-defined reports supplied with the product or created in Report Designer. Refer to Report Designer for further information.\nDesigner\nAllows you to open the Report Designer, in which more complex user-defined reports and report templates can be created. Refer to Report Designer for further information.\nSimple\nAllows you to create a report with basic formatting. Refer to Simple Reports for further information.\nClash Plotting\nRefer to Clash Plotting for further information.\nDefaults Group\nUser Defaults\nAllows you to set user-specific default settings. Refer to Modify User Defaults for further information.\n3D Graphics\nAllows you to change the 3D graphic settings. Refer to Graphics Drawlist for further information.\nColours\nAllows you to change colour settings for the current 3D view. Refer to Colour Settings for more information.\nCurrent 3D View\nAllows you to change view settings for the current 3D view. Refer to Current View for more information.\nPick through translucent\nAllows you to pick an element through a translucent element. Refer to Translucent Pick for more information.\nDisplay Group\nCommands\nClick to display the Command Window. Refer to Command Window for further information.\nMessages\nClick to display the Messages window, which displays a list of messages issued by the application during the session. Refer to Messages for further information.\nAppware Load Errors\nClick to display the Default Load Errors window. Refer to Appware Load Errors for further information.\nExplorers Group\nDraw Explorer\nAllows you to open and close the Draw Explorer. Refer to Draw Explorer for further information.\nDepartment\nClick to display a drop-down list with the following options:\nAllows you to create a new department. Refer to Create and Modify Departments for further information.\nAllows you to modify the attributes of a department. Refer to Modify Department Attributes for further information.\nRegistry\nClick to display a drop-down list with the following options:\nAllows you to create a new registry. Refer to Create and Modify Registries for further information.\nAllows you to modify the attributes of a registry. Refer to Modify Registry Attributes for further information.\nDrawing\nClick to display a drop-down list with the following options:\nAllows you to create a new drawing. Refer to Create and Modify Departments for further information.\nAllows you to modify the attributes of a drawing Refer to Modify Drawing Attributes for further information.\nModel Explorer\nAllows you to open and close the Model Explorer. Refer to Model Explorer for further information.\nFabrication Explorer\nAllows you to open and close the Model Explorer. Refer to Fabrication Explorer for further information.\nIFC Explorer\nAllows you to open and close the IFC Flexible Explorer. Refer to IFC Flexible Explorer for further information.\nMultiCAD Explorer\nAllows you to open and close the MultiCAD Explorer. Refer to MultiCAD Flexible Explorer in Draw for further information.\nSearch Group\nSearch\nAllows you to open and close the Search and Search Result windows. Refer to Search for further information.\nCollections\nReport Group\nRun Report\nAllows you to run pre-defined reports supplied with the product or created in Report Designer. Refer to Report Designer for further information.\nDesigner\nAllows you to open the Report Designer, in which more complex user-defined reports and report templates can be created. Refer to Report Designer for further information.\nSimple\nAllows you to create a report with basic formatting. Refer to Simple Reports for further information.\nClash Plotting\nRefer to Clash Plotting for further information.\nDefaults Group\nUser Defaults\nAllows you to set user-specific default settings. Refer to Modify User Defaults for further information.\n3D Graphics\nAllows you to change the 3D graphic settings. Refer to Graphics Drawlist for further information.\nColours\nAllows you to change colour settings for the current 3D view. Refer to Colour Settings for more information.\nCurrent 3D View\nAllows you to change view settings for the current 3D view. Refer to Current View for more information.\nPick through translucent\nAllows you to pick an element through a translucent element. Refer to Translucent Pick for more information.\n\nDisplay Group\nCommands\nClick to display the Command Window. Refer to Command Window for further information.\nMessages\nClick to display the Messages window, which displays a list of messages issued by the application during the session. Refer to Messages for further information.\nAppware Load Errors\nClick to display the Default Load Errors window. Refer to Appware Load Errors for further information.\nExplorers Group\nDraw Explorer\nAllows you to open and close the Draw Explorer. Refer to Draw Explorer for further information.\nDepartment\nClick to display a drop-down list with the following options:\nCreate\nAllows you to create a new department. Refer to Create and Modify Departments for further information.\nModify\nAllows you to modify the attributes of a department. Refer to Modify Department Attributes for further information.\nRegistry\nClick to display a drop-down list with the following options:\nCreate\nAllows you to create a new registry. Refer to Create and Modify Registries for further information.\nModify\nAllows you to modify the attributes of a registry. Refer to Modify Registry Attributes for further information.\nDrawing\nClick to display a drop-down list with the following options:\nCreate Explicitly\nAllows you to create a new drawing. Refer to Create and Modify Departments for further information.\nModify\nAllows you to modify the attributes of a drawing Refer to Modify Drawing Attributes for further information.\nModel Explorer\nAllows you to open and close the Model Explorer. Refer to Model Explorer for further information.\nFabrication Explorer\nAllows you to open and close the Model Explorer. Refer to Fabrication Explorer for further information.\nIFC Explorer\nAllows you to open and close the IFC Flexible Explorer. Refer to IFC Flexible Explorer for further information.\nMultiCAD Explorer\nAllows you to open and close the MultiCAD Explorer. Refer to MultiCAD Flexible Explorer in Draw for further information.\nSearch Group\nSearch\nAllows you to open and close the Search and Search Result windows. Refer to Search for further information.\nCollections\nReport Group\nRun Report\nAllows you to run pre-defined reports supplied with the product or created in Report Designer. Refer to Report Designer for further information.\nDesigner\nAllows you to open the Report Designer, in which more complex user-defined reports and report templates can be created. Refer to Report Designer for further information.\nSimple\nAllows you to create a report with basic formatting. Refer to Simple Reports for further information.\nClash Plotting\nRefer to Clash Plotting for further information.\nDefaults Group\nUser Defaults\nAllows you to set user-specific default settings. Refer to Modify User Defaults for further information.\n3D Graphics\nAllows you to change the 3D graphic settings. Refer to Graphics Drawlist for further information.\nColours\nAllows you to change colour settings for the current 3D view. Refer to Colour Settings for more information.\nCurrent 3D View\nAllows you to change view settings for the current 3D view. Refer to Current View for more information.\nPick through translucent\nAllows you to pick an element through a translucent element. Refer to Translucent Pick for more information.\n\n\n\nCommand Window\nMessages\nAppware Load Errors\nDraw Explorer\nCreate and Modify Departments\nModify Department Attributes\nCreate and Modify Registries\nModify Registry Attributes\nCreate and Modify Departments\nModify Drawing Attributes\nModel Explorer\nFabrication Explorer\nIFC Flexible Explorer\nMultiCAD Flexible Explorer in Draw\nSearch\nReport Designer\nReport Designer\nSimple Reports\nClash Plotting\nModify User Defaults\nGraphics Drawlist\nColour Settings\nTranslucent Pick\nDisplay Group\nCommands\nCommand\nCommand Window\nMessages\nMessages\nAppware Load Errors\nAppware Load Errors\nExplorers Group\nDraw Explorer\nDraw Explorer\nDepartment\nCreate\nCreate and Modify Departments\nModify\nModify Department Attributes\nRegistry\nCreate\nCreate and Modify Registries\nModify\nModify Registry Attributes\nDrawing\nCreate Explicitly\nCreate and Modify Departments\nModify\nModify Drawing Attributes\nModel Explorer\nModel Explorer\n\nFabrication Explorer\nFabrication Explorer\n\nIFC Explorer\nIFC Flexible Explorer\nMultiCAD Explorer\nMultiCAD Flexible Explorer in Draw\nSearch Group\nSearch\nSearch\n\nCollections\nReport Group\nRun Report\nReport Designer\nDesigner\nReport Designer\nSimple\nSimple Reports\nClash Plotting\nClash Plotting\nDefaults Group\nUser Defaults\nModify User Defaults\n3D Graphics\nGraphics Drawlist\n\nColours\nColour Settings\nCurrent 3D View\nCurrent View\nPick through translucent\nTranslucent Pick"}
{"Headers": "Interfaces", "Content": "\nImport Group\nExcel\nAllows you to add Excel tables to a drawing. Refer to Add Excel Tables for further information.\nImport CAD File\nAllows you to import a CAD drawing as a new drawing sheet or symbol template. Refer to Create Sheet or Template from Imported CAD File for further information.\nMapping Settings\nAllows you to create fill type and line type mappings for imported CAD (.dwg or .dxf) files. Refer to Mapping Settings for further information.\nContext Group\nConfigure\nAllows you to configure the default settings for Design In Context. Refer to Configure for more information.\nBrowse\nAllows you to do all the navigating activity for Design In Context. Refer to Associated Documents for more information.\nAVEVA NET\nAllows you to display the currently selected item in the explorer in the AVEVA NET Dashboard. Refer to AVEVA NET Dashboard for more information.\nImport Group\nExcel\nAllows you to add Excel tables to a drawing. Refer to Add Excel Tables for further information.\nImport CAD File\nAllows you to import a CAD drawing as a new drawing sheet or symbol template. Refer to Create Sheet or Template from Imported CAD File for further information.\nMapping Settings\nAllows you to create fill type and line type mappings for imported CAD (.dwg or .dxf) files. Refer to Mapping Settings for further information.\nContext Group\nConfigure\nAllows you to configure the default settings for Design In Context. Refer to Configure for more information.\nBrowse\nAllows you to do all the navigating activity for Design In Context. Refer to Associated Documents for more information.\nAVEVA NET\nAllows you to display the currently selected item in the explorer in the AVEVA NET Dashboard. Refer to AVEVA NET Dashboard for more information.\n\nImport Group\nExcel\nAllows you to add Excel tables to a drawing. Refer to Add Excel Tables for further information.\nImport CAD File\nAllows you to import a CAD drawing as a new drawing sheet or symbol template. Refer to Create Sheet or Template from Imported CAD File for further information.\nMapping Settings\nAllows you to create fill type and line type mappings for imported CAD (.dwg or .dxf) files. Refer to Mapping Settings for further information.\nContext Group\nConfigure\nAllows you to configure the default settings for Design In Context. Refer to Configure for more information.\nBrowse\nAllows you to do all the navigating activity for Design In Context. Refer to Associated Documents for more information.\nAVEVA NET\nAllows you to display the currently selected item in the explorer in the AVEVA NET Dashboard. Refer to AVEVA NET Dashboard for more information.\n\n\n\nAdd Excel Tables\nCreate Sheet or Template from Imported CAD File\nMapping Settings\nAssociated Documents\nAVEVA NET Dashboard\nImport Group\nExcel\nAdd Excel Tables\nImport CAD File\nCreate Sheet or Template from Imported CAD File\nMapping Settings\nMapping Settings\nContext Group\nConfigure\nConfigure\nBrowse\nAssociated Documents\nAVEVA NET\nAVEVA NET Dashboard"}
{"Headers": "Manage", "Content": "\n\nExtracts Group\nExtract Control\nAllows you to manage items claimed to the current extract database.\nCommunications\nAllows you to view the Communications of the local and remote Daemons, if they are running.\nStates\nAllows you to check the Locking and Isolation of locations.\nTransactions\nAllows you to view Global transaction commands and view what has happened to them.\nRefer to the Global for further details of the Transfer, Extract Control, Communications, States and Transactions functionality.\nStatus Group\nStatus Controller\nClick to display the Status Controller window, which allows the you to control and report on the status of individual 3D model objects as they progress through their lifecycle.\nRefer to Status Control for further information.\nHistory Group\nDB Listing\nClick to display the DB Listing window, which allows you to query and output aspects of the database. For example, to report changes since a certain date. Refer to DB Listing for details of the facilities.\nSession Comment\nClick to display the Savework / Session Comment window, which allows you to input comments regarding the current session. Refer to Session Comment for details of the facilities.\nAccess Group\nClaimlists\nClick to display the Multiwrite Claim Lists window, which allows you to view and manage user element claims. Refer to Claimlists for details of the facilities.\nData Access Control\nClick to display the Query Data Access Control window, which allows you to view the access rights for project users. Refer to Data Access Control for details of the facilities.\nHierarchy Group\nInclude\nClick to display the Include window, which allows you to move elements from the members list of one owner to that of another. Refer to Include for further information.\nReverse\nClick to reverse the entire members list order of an element. Refer to Reverse Order for further information.\nReorder\nClick to display the Reorder window, which allows you to rearrange the members list order for any owning element. Refer to Reorder for further information.\nRefer to Hierarchy for details of the facilities.\nQuery Group\nProject\nClick to display the Query Project window, which allows you to perform queries on a range of project data. Refer to Project for further information.\nUser Status\nClick to display the User Status window, which displays information about the user sessions currently in the project. Refer to User Status for details of the facilities.\nRevision Group\nEditor\nAllows you to create and modify revisions. Refer to Create and Modify Revisions for further information.\nCompare\nAllows you to compare two revisions selected from the From and To lists. Refer to Compare Revisions and Add Revision Clouds for further information.\nTo\nAllows you to select two revisions to compare with each other. Refer to Compare Revisions and Add Revision Clouds for further information.\nFrom\nConfigure\nClick to display the Configure window, which allows the movement of external reference data into project(s). Refer to Configuration DB for further information.\nExtracts Group\nExtract Control\nAllows you to manage items claimed to the current extract database.\nCommunications\nAllows you to view the Communications of the local and remote Daemons, if they are running.\nStates\nAllows you to check the Locking and Isolation of locations.\nTransactions\nAllows you to view Global transaction commands and view what has happened to them.\nRefer to the Global for further details of the Transfer, Extract Control, Communications, States and Transactions functionality.\nStatus Group\nStatus Controller\nClick to display the Status Controller window, which allows the you to control and report on the status of individual 3D model objects as they progress through their lifecycle.\nRefer to Status Control for further information.\nHistory Group\nDB Listing\nClick to display the DB Listing window, which allows you to query and output aspects of the database. For example, to report changes since a certain date. Refer to DB Listing for details of the facilities.\nSession Comment\nClick to display the Savework / Session Comment window, which allows you to input comments regarding the current session. Refer to Session Comment for details of the facilities.\nAccess Group\nClaimlists\nClick to display the Multiwrite Claim Lists window, which allows you to view and manage user element claims. Refer to Claimlists for details of the facilities.\nData Access Control\nClick to display the Query Data Access Control window, which allows you to view the access rights for project users. Refer to Data Access Control for details of the facilities.\nHierarchy Group\nInclude\nClick to display the Include window, which allows you to move elements from the members list of one owner to that of another. Refer to Include for further information.\nReverse\nClick to reverse the entire members list order of an element. Refer to Reverse Order for further information.\nReorder\nClick to display the Reorder window, which allows you to rearrange the members list order for any owning element. Refer to Reorder for further information.\nRefer to Hierarchy for details of the facilities.\nQuery Group\nProject\nClick to display the Query Project window, which allows you to perform queries on a range of project data. Refer to Project for further information.\nUser Status\nClick to display the User Status window, which displays information about the user sessions currently in the project. Refer to User Status for details of the facilities.\nRevision Group\nEditor\nAllows you to create and modify revisions. Refer to Create and Modify Revisions for further information.\nCompare\nAllows you to compare two revisions selected from the From and To lists. Refer to Compare Revisions and Add Revision Clouds for further information.\nTo\nAllows you to select two revisions to compare with each other. Refer to Compare Revisions and Add Revision Clouds for further information.\nFrom\nConfigure\nClick to display the Configure window, which allows the movement of external reference data into project(s). Refer to Configuration DB for further information.\n\nExtracts Group\nExtract Control\nAllows you to manage items claimed to the current extract database.\nCommunications\nAllows you to view the Communications of the local and remote Daemons, if they are running.\nStates\nAllows you to check the Locking and Isolation of locations.\nTransactions\nAllows you to view Global transaction commands and view what has happened to them.\nRefer to the Global for further details of the Transfer, Extract Control, Communications, States and Transactions functionality.\nStatus Group\nStatus Controller\nClick to display the Status Controller window, which allows the you to control and report on the status of individual 3D model objects as they progress through their lifecycle.\nRefer to Status Control for further information.\nHistory Group\nDB Listing\nClick to display the DB Listing window, which allows you to query and output aspects of the database. For example, to report changes since a certain date. Refer to DB Listing for details of the facilities.\nSession Comment\nClick to display the Savework / Session Comment window, which allows you to input comments regarding the current session. Refer to Session Comment for details of the facilities.\nAccess Group\nClaimlists\nClick to display the Multiwrite Claim Lists window, which allows you to view and manage user element claims. Refer to Claimlists for details of the facilities.\nData Access Control\nClick to display the Query Data Access Control window, which allows you to view the access rights for project users. Refer to Data Access Control for details of the facilities.\nHierarchy Group\nInclude\nClick to display the Include window, which allows you to move elements from the members list of one owner to that of another. Refer to Include for further information.\nReverse\nClick to reverse the entire members list order of an element. Refer to Reverse Order for further information.\nReorder\nClick to display the Reorder window, which allows you to rearrange the members list order for any owning element. Refer to Reorder for further information.\nRefer to Hierarchy for details of the facilities.\nQuery Group\nProject\nClick to display the Query Project window, which allows you to perform queries on a range of project data. Refer to Project for further information.\nUser Status\nClick to display the User Status window, which displays information about the user sessions currently in the project. Refer to User Status for details of the facilities.\nRevision Group\nEditor\nAllows you to create and modify revisions. Refer to Create and Modify Revisions for further information.\nCompare\nAllows you to compare two revisions selected from the From and To lists. Refer to Compare Revisions and Add Revision Clouds for further information.\nTo\nAllows you to select two revisions to compare with each other. Refer to Compare Revisions and Add Revision Clouds for further information.\nFrom\nConfigure\nClick to display the Configure window, which allows the movement of external reference data into project(s). Refer to Configuration DB for further information.\n\n\n\nGlobal\nInclude\nReverse Order\nReorder\nHierarchy\nProject\nUser Status\nCreate and Modify Revisions\nConfiguration DB\nExtracts Group\nExtract Control\nCommunications\nStates\nTransactions\nGlobal\nTransfer\nExtract\nControl\nCommunications\nStates\nTransactions\nStatus Group\nStatus Controller\nStatus Controller\nStatus Control\nHistory Group\nDB Listing\nDB Listing\nDB Listing\nSession Comment\nSavework / Session Comment\nSession Comment\nAccess Group\nClaimlists\nClaimlists\nData Access Control\nData Access Control\nHierarchy Group\nInclude\nInclude\nReverse\nReverse Order\nReorder\nReorder\nReorder\nHierarchy\nQuery Group\nProject\nQuery Project\nProject\nUser Status\nUser Status\nRevision Group\nEditor\nCreate and Modify Revisions\nCompare\nCompare Revisions and Add Revision Clouds\nTo\nCompare Revisions and Add Revision Clouds\nFrom\nConfigure\nConfigure\nConfiguration DB"}
{"Headers": "Auto", "Content": "\n\nCreate Group\nGeneral\nClick to display a drop-down list with the following options:\nDrawing\nAllows you to create a general ADP drawing. Refer to Create General ADP Drawings for further information.\nSheet\nAllows you to create a general ADP sheet. Refer to Create General ADP Sheets for further information.\nView\nAllows you to create a general ADP view. Refer to Create General ADP Views for further information.\nSpool Drawings\nAllows you to create a new pipe spool drawing. Refer to Spool Drawings for further information.\nHVAC Sketches\nAllows you to create a new HVAC sketch. Refer to Create HVAC Sketches for further information.\nIsometric Drawings\nIsometric ADP defaults are defined by the administrator. Refer to Defaults for further information.\nModify Group\nGeneral\nClick to display a drop-down list with the following options:\nDrawing\nAllows you to modify a general ADP drawing. Refer to Modify General ADP Drawings for further details.\nSheet\nAllows you to modify a general ADP sheet. Refer to Modify General ADP Sheets for further details.\nView\nAllows you to modify a general ADP view. Refer to Modify General ADP View for further details.\nTools Group\nEquipment Centres\nAllows you to define the setup of equipment centrelines on a general ADP view. Refer to Equipment Centerlines for further details.\nWeld Labels\nAllows you to label welds. Refer to Create Weld Labels for further information.\nIsometric Tools Group\nDrawing Search\nAllows you to search for Isometric ADP drawings. Refer to Search for Isometric ADP Drawings for further information.\nIsometric Direction\nAllows you to modify the view direction of an Isometric ADP drawing. Refer to Isometric Direction for further information.\nNudge Up\nAllows you to increase the view scale of the Isometric ADP drawing. Refer to Nudge the View Scale for further information.\nNudge Down\nAllows you to decrease the view scale of the Isometric ADP drawing. Refer to Nudge the View Scale for further information.\nNudge Factor\nAllows you to define the scale used to nudge the view scale. Refer to Nudge the View Scale for further information.\nDimension Cycle\nAllows you to define the display style of dimensions on the Isometric ADP drawing. Refer to Dimension Style for further information.\nLog\nAllows you to view the log file for the generated Isometric ADP drawing. Refer to Log File for further information.\nRevision\nAllows you to define the revision status of the Isometric ADP drawing. Refer to Revision Details for further information.\nVisibility\nAllows you to specify the visible layers for the Isometric ADP drawing. Refer to Layer Visibility for further information.\nDefaults Group\nGeneral\nThe default files used for General ADP production are defined by the administrator. Refer to Set ADP Defaults for further information.\nIsometric\nThe default files used for Isometric ADP production are defined by the administrator. Refer to Defaults for further information.\nPipe Spool Administration\nAllows you to define the sheet template and backing sheet settings for pipe spool drawings.\nCreate Group\nGeneral\nClick to display a drop-down list with the following options:\nAllows you to create a general ADP drawing. Refer to Create General ADP Drawings for further information.\nAllows you to create a general ADP sheet. Refer to Create General ADP Sheets for further information.\nAllows you to create a general ADP view. Refer to Create General ADP Views for further information.\nSpool Drawings\nAllows you to create a new pipe spool drawing. Refer to Spool Drawings for further information.\nHVAC Sketches\nAllows you to create a new HVAC sketch. Refer to Create HVAC Sketches for further information.\nIsometric Drawings\nIsometric ADP defaults are defined by the administrator. Refer to Defaults for further information.\nModify Group\nGeneral\nClick to display a drop-down list with the following options:\nAllows you to modify a general ADP drawing. Refer to Modify General ADP Drawings for further details.\nAllows you to modify a general ADP sheet. Refer to Modify General ADP Sheets for further details.\nAllows you to modify a general ADP view. Refer to Modify General ADP View for further details.\nTools Group\nEquipment Centres\nAllows you to define the setup of equipment centrelines on a general ADP view. Refer to Equipment Centerlines for further details.\nWeld Labels\nAllows you to label welds. Refer to Create Weld Labels for further information.\nIsometric Tools Group\nDrawing Search\nAllows you to search for Isometric ADP drawings. Refer to Search for Isometric ADP Drawings for further information.\nIsometric Direction\nAllows you to modify the view direction of an Isometric ADP drawing. Refer to Isometric Direction for further information.\nNudge Up\nAllows you to increase the view scale of the Isometric ADP drawing. Refer to Nudge the View Scale for further information.\nNudge Down\nAllows you to decrease the view scale of the Isometric ADP drawing. Refer to Nudge the View Scale for further information.\nNudge Factor\nAllows you to define the scale used to nudge the view scale. Refer to Nudge the View Scale for further information.\nDimension Cycle\nAllows you to define the display style of dimensions on the Isometric ADP drawing. Refer to Dimension Style for further information.\nLog\nAllows you to view the log file for the generated Isometric ADP drawing. Refer to Log File for further information.\nRevision\nAllows you to define the revision status of the Isometric ADP drawing. Refer to Revision Details for further information.\nVisibility\nAllows you to specify the visible layers for the Isometric ADP drawing. Refer to Layer Visibility for further information.\nDefaults Group\nGeneral\nThe default files used for General ADP production are defined by the administrator. Refer to Set ADP Defaults for further information.\nIsometric\nThe default files used for Isometric ADP production are defined by the administrator. Refer to Defaults for further information.\nPipe Spool Administration\nAllows you to define the sheet template and backing sheet settings for pipe spool drawings.\n\nCreate Group\nGeneral\nClick to display a drop-down list with the following options:\nDrawing\nAllows you to create a general ADP drawing. Refer to Create General ADP Drawings for further information.\nSheet\nAllows you to create a general ADP sheet. Refer to Create General ADP Sheets for further information.\nView\nAllows you to create a general ADP view. Refer to Create General ADP Views for further information.\nSpool Drawings\nAllows you to create a new pipe spool drawing. Refer to Spool Drawings for further information.\nHVAC Sketches\nAllows you to create a new HVAC sketch. Refer to Create HVAC Sketches for further information.\nIsometric Drawings\nIsometric ADP defaults are defined by the administrator. Refer to Defaults for further information.\nModify Group\nGeneral\nClick to display a drop-down list with the following options:\nDrawing\nAllows you to modify a general ADP drawing. Refer to Modify General ADP Drawings for further details.\nSheet\nAllows you to modify a general ADP sheet. Refer to Modify General ADP Sheets for further details.\nView\nAllows you to modify a general ADP view. Refer to Modify General ADP View for further details.\nTools Group\nEquipment Centres\nAllows you to define the setup of equipment centrelines on a general ADP view. Refer to Equipment Centerlines for further details.\nWeld Labels\nAllows you to label welds. Refer to Create Weld Labels for further information.\nIsometric Tools Group\nDrawing Search\nAllows you to search for Isometric ADP drawings. Refer to Search for Isometric ADP Drawings for further information.\nIsometric Direction\nAllows you to modify the view direction of an Isometric ADP drawing. Refer to Isometric Direction for further information.\nNudge Up\nAllows you to increase the view scale of the Isometric ADP drawing. Refer to Nudge the View Scale for further information.\nNudge Down\nAllows you to decrease the view scale of the Isometric ADP drawing. Refer to Nudge the View Scale for further information.\nNudge Factor\nAllows you to define the scale used to nudge the view scale. Refer to Nudge the View Scale for further information.\nDimension Cycle\nAllows you to define the display style of dimensions on the Isometric ADP drawing. Refer to Dimension Style for further information.\nLog\nAllows you to view the log file for the generated Isometric ADP drawing. Refer to Log File for further information.\nRevision\nAllows you to define the revision status of the Isometric ADP drawing. Refer to Revision Details for further information.\nVisibility\nAllows you to specify the visible layers for the Isometric ADP drawing. Refer to Layer Visibility for further information.\nDefaults Group\nGeneral\nThe default files used for General ADP production are defined by the administrator. Refer to Set ADP Defaults for further information.\nIsometric\nThe default files used for Isometric ADP production are defined by the administrator. Refer to Defaults for further information.\nPipe Spool Administration\nAllows you to define the sheet template and backing sheet settings for pipe spool drawings.\n\n\n\nCreate General ADP Drawings\nCreate General ADP Sheets\nCreate General ADP Views\nSpool Drawings\nCreate HVAC Sketches\nDefaults\nModify General ADP Drawings\nModify General ADP Sheets\nModify General ADP View\nEquipment Centerlines\nCreate Weld Labels\nSearch for Isometric ADP Drawings\nIsometric Direction\nNudge the View Scale\nNudge the View Scale\nNudge the View Scale\nDimension Style\nLog File\nRevision Details\nLayer Visibility\nSet ADP Defaults\nDefaults\nCreate Group\nGeneral\nDrawing\nCreate General ADP Drawings\nSheet\nCreate General ADP Sheets\nView\nCreate General ADP Views\nSpool Drawings\nSpool Drawings\nHVAC Sketches\nCreate HVAC Sketches\nIsometric Drawings\nDefaults\n\nModify Group\nGeneral\nDrawing\nModify General ADP Drawings\nSheet\nModify General ADP Sheets\nView\nModify General ADP View\nTools Group\nEquipment Centres\nEquipment Centerlines\nWeld Labels\nCreate Weld Labels\nIsometric Tools Group\nDrawing Search\nSearch for Isometric ADP Drawings\nIsometric Direction\nIsometric Direction\nNudge Up\nNudge the View Scale\nNudge Down\nNudge the View Scale\nNudge Factor\nNudge the View Scale\nDimension Cycle\nDimension Style\nLog\nLog File\nRevision\nRevision Details\nVisibility\nLayer Visibility\nDefaults Group\nGeneral\nSet ADP Defaults\n\nIsometric\nDefaults\nPipe Spool Administration"}
{"Headers": "Area", "Content": "\n\nArea-Based Auto Group\nCreate Drawings\nAllows you to create new drawings using the Area-Based Automatic Drawing Production facility. Refer to ABA Drawing Process for further information.\nLog Files\nClick to display the Area ADP File Browser window, which allows you to browse for and open files that log Area-Based Automatic Drawing Production data. Refer to File Browser for further information.\nBrowse\nClick to display the ABA Browse Sheets window, which allows you to browse for and open the drawings produced with the Area-Based Automatic Drawing Production facility. Refer to ABA Browse Sheets for further information.\nDefaults\nAllows you to set defaults for Area-Based Automatic Drawing Production. Refer to ABA Defaults for further information.\nCreate Group\nLibrary\nClick to display a drop-down list with the following options:\nArea Library\nABA Area Libraries are defined by the administrator. Refer to Create and Modify Area Libraries for further information.\nArea\nABA Areas are defined by the administrator. Refer to Create and Modify Areas for further information.\nClassification\nABA Classifications are defined by the administrator. Refer to Create and Modify Classifications for further information.\nTask\nABA Tasks are defined by the administrator. Refer to Create and Modify Tasks for further information.\nLabelling\nABA Labelling Conventions are defined by the administrator. Refer to Create and Modify Labelling for further information.\nTemplate\nClick to display a drop-down list with the following options:\nDrawing\nABA Template Drawings are defined by the administrator. Refer to Create and Modify Template Drawings for further information.\nView\nABA Template Views are defined by the administrator. Refer to Create and Modify ABA Template View for further information.\nAuto Number Rules\nAuto Number Rules are defined by the administrator. Refer to Create and Modify Auto Number Rules for further information.\nKeyplan Layers\nKeyplan Layers are defined by the administrator. Refer to Create and Modify Keyplan Layers for further information.\nModify Group\nLibrary\nClick to display a drop-down list with the following options:\nArea Library\nABA Area Libraries are defined by the administrator. Refer to Create and Modify Area Libraries for further information.\nArea\nABA Areas are defined by the administrator. Refer to Create and Modify Areas for further information.\nClassification\nABA Classifications are defined by the administrator. Refer to Create and Modify Classifications for further information.\nTask\nABA Tasks are defined by the administrator. Refer to Create and Modify Tasks for further information.\nLabelling\nABA Labelling Conventions are defined by the administrator. Refer to Create and Modify Labelling for further information.\nTemplate\nClick to display a drop-down list with the following options:\nDrawing\nABA Template Drawings are defined by the administrator. Refer to Create and Modify Template Drawings for further information.\nSheet\nABA Template Sheets are defined by the administrator. Refer to Create ABA Template Sheet for further information.\nView\nABA Template Views are defined by the administrator. Refer to Create and Modify ABA Template View for further information.\nAuto Number Rules\nAuto Number Rules are defined by the administrator. Refer to Create and Modify Auto Number Rules for further information.\nSupports Group\nNew Drawing\nAllows you to create ABA drawings. Click to display the Create MDS Drawing window. The functionality of the Create MDS Drawing window is explained as part of the process to create ABA drawings for Supports. Refer to Create Supports ABA Drawing for further information.\nNew User View\nAllows you to create a User View on an existing ABA drawing. The process to create a User View is explained as part of the process to create ABA drawings for Supports. Refer to User View for further information.\nNew Over View\nAllows you to create an Over View on an existing ABA drawing. The process to create an Over View is explained as part of the process to create ABA drawings for Supports. Refer to User View for further information.\nRevision Control\nAllows you to update the Revision data on the ABA drawing sheet. Click to display the MDS Revision Control window. The functionality of the MDS Revision Control window is explained as part of the process to create ABA drawings for Supports. Refer to Revision Control for further information.\nLayer Control\nAllows you to control the layers for the ABA drawing. Click to display the MDS Layer Control window. The functionality of the MDS Layer Control window is explained as part of the process to create ABA drawings for Supports. Refer to Layer Control for further information.\nDrawing Lock\nAllows you to lock an ABA drawing, preventing any changes to be made. Click to display the Modify Drawing Lock window. The functionality of the Modify Drawing Lock window is explained as part of the process to create ABA drawings for Supports. Refer to Drawing Lock for further information.\nScale Override\nAllows you to control the view scale for the ABA drawing. Click to display the MDS Scale Override window. The functionality of the MDS Scale Override window is explained as part of the process to create ABA drawings for Supports. Refer to Scale Override for further information.\nRescale Pipe Symbols\nAllows you to rescale pipe symbols on an existing ABA drawing. The process to rescale pipe symbols is explained as part of the process to create ABA drawings for Supports. Refer to Rescale Pipe Symbols for further information.\nArea-Based Auto Group\nCreate Drawings\nAllows you to create new drawings using the Area-Based Automatic Drawing Production facility. Refer to ABA Drawing Process for further information.\nLog Files\nClick to display the Area ADP File Browser window, which allows you to browse for and open files that log Area-Based Automatic Drawing Production data. Refer to File Browser for further information.\nBrowse\nClick to display the ABA Browse Sheets window, which allows you to browse for and open the drawings produced with the Area-Based Automatic Drawing Production facility. Refer to ABA Browse Sheets for further information.\nDefaults\nAllows you to set defaults for Area-Based Automatic Drawing Production. Refer to ABA Defaults for further information.\nCreate Group\nLibrary\nClick to display a drop-down list with the following options:\nABA Area Libraries are defined by the administrator. Refer to Create and Modify Area Libraries for further information.\nABA Areas are defined by the administrator. Refer to Create and Modify Areas for further information.\nABA Classifications are defined by the administrator. Refer to Create and Modify Classifications for further information.\nABA Tasks are defined by the administrator. Refer to Create and Modify Tasks for further information.\nABA Labelling Conventions are defined by the administrator. Refer to Create and Modify Labelling for further information.\nTemplate\nClick to display a drop-down list with the following options:\nABA Template Drawings are defined by the administrator. Refer to Create and Modify Template Drawings for further information.\nABA Template Views are defined by the administrator. Refer to Create and Modify ABA Template View for further information.\nAuto Number Rules\nAuto Number Rules are defined by the administrator. Refer to Create and Modify Auto Number Rules for further information.\nKeyplan Layers\nKeyplan Layers are defined by the administrator. Refer to Create and Modify Keyplan Layers for further information.\nModify Group\nLibrary\nClick to display a drop-down list with the following options:\nABA Area Libraries are defined by the administrator. Refer to Create and Modify Area Libraries for further information.\nABA Areas are defined by the administrator. Refer to Create and Modify Areas for further information.\nABA Classifications are defined by the administrator. Refer to Create and Modify Classifications for further information.\nABA Tasks are defined by the administrator. Refer to Create and Modify Tasks for further information.\nABA Labelling Conventions are defined by the administrator. Refer to Create and Modify Labelling for further information.\nTemplate\nClick to display a drop-down list with the following options:\nABA Template Drawings are defined by the administrator. Refer to Create and Modify Template Drawings for further information.\nABA Template Sheets are defined by the administrator. Refer to Create ABA Template Sheet for further information.\nABA Template Views are defined by the administrator. Refer to Create and Modify ABA Template View for further information.\nAuto Number Rules\nAuto Number Rules are defined by the administrator. Refer to Create and Modify Auto Number Rules for further information.\nSupports Group\nNew Drawing\nAllows you to create ABA drawings. Click to display the Create MDS Drawing window. The functionality of the Create MDS Drawing window is explained as part of the process to create ABA drawings for Supports. Refer to Create Supports ABA Drawing for further information.\nNew User View\nAllows you to create a User View on an existing ABA drawing. The process to create a User View is explained as part of the process to create ABA drawings for Supports. Refer to User View for further information.\nNew Over View\nAllows you to create an Over View on an existing ABA drawing. The process to create an Over View is explained as part of the process to create ABA drawings for Supports. Refer to User View for further information.\nRevision Control\nAllows you to update the Revision data on the ABA drawing sheet. Click to display the MDS Revision Control window. The functionality of the MDS Revision Control window is explained as part of the process to create ABA drawings for Supports. Refer to Revision Control for further information.\nLayer Control\nAllows you to control the layers for the ABA drawing. Click to display the MDS Layer Control window. The functionality of the MDS Layer Control window is explained as part of the process to create ABA drawings for Supports. Refer to Layer Control for further information.\nDrawing Lock\nAllows you to lock an ABA drawing, preventing any changes to be made. Click to display the Modify Drawing Lock window. The functionality of the Modify Drawing Lock window is explained as part of the process to create ABA drawings for Supports. Refer to Drawing Lock for further information.\nScale Override\nAllows you to control the view scale for the ABA drawing. Click to display the MDS Scale Override window. The functionality of the MDS Scale Override window is explained as part of the process to create ABA drawings for Supports. Refer to Scale Override for further information.\nRescale Pipe Symbols\nAllows you to rescale pipe symbols on an existing ABA drawing. The process to rescale pipe symbols is explained as part of the process to create ABA drawings for Supports. Refer to Rescale Pipe Symbols for further information.\n\nArea-Based Auto Group\nCreate Drawings\nAllows you to create new drawings using the Area-Based Automatic Drawing Production facility. Refer to ABA Drawing Process for further information.\nLog Files\nClick to display the Area ADP File Browser window, which allows you to browse for and open files that log Area-Based Automatic Drawing Production data. Refer to File Browser for further information.\nBrowse\nClick to display the ABA Browse Sheets window, which allows you to browse for and open the drawings produced with the Area-Based Automatic Drawing Production facility. Refer to ABA Browse Sheets for further information.\nDefaults\nAllows you to set defaults for Area-Based Automatic Drawing Production. Refer to ABA Defaults for further information.\nCreate Group\nLibrary\nClick to display a drop-down list with the following options:\nArea Library\nABA Area Libraries are defined by the administrator. Refer to Create and Modify Area Libraries for further information.\nArea\nABA Areas are defined by the administrator. Refer to Create and Modify Areas for further information.\nClassification\nABA Classifications are defined by the administrator. Refer to Create and Modify Classifications for further information.\nTask\nABA Tasks are defined by the administrator. Refer to Create and Modify Tasks for further information.\nLabelling\nABA Labelling Conventions are defined by the administrator. Refer to Create and Modify Labelling for further information.\nTemplate\nClick to display a drop-down list with the following options:\nDrawing\nABA Template Drawings are defined by the administrator. Refer to Create and Modify Template Drawings for further information.\nView\nABA Template Views are defined by the administrator. Refer to Create and Modify ABA Template View for further information.\nAuto Number Rules\nAuto Number Rules are defined by the administrator. Refer to Create and Modify Auto Number Rules for further information.\nKeyplan Layers\nKeyplan Layers are defined by the administrator. Refer to Create and Modify Keyplan Layers for further information.\nModify Group\nLibrary\nClick to display a drop-down list with the following options:\nArea Library\nABA Area Libraries are defined by the administrator. Refer to Create and Modify Area Libraries for further information.\nArea\nABA Areas are defined by the administrator. Refer to Create and Modify Areas for further information.\nClassification\nABA Classifications are defined by the administrator. Refer to Create and Modify Classifications for further information.\nTask\nABA Tasks are defined by the administrator. Refer to Create and Modify Tasks for further information.\nLabelling\nABA Labelling Conventions are defined by the administrator. Refer to Create and Modify Labelling for further information.\nTemplate\nClick to display a drop-down list with the following options:\nDrawing\nABA Template Drawings are defined by the administrator. Refer to Create and Modify Template Drawings for further information.\nSheet\nABA Template Sheets are defined by the administrator. Refer to Create ABA Template Sheet for further information.\nView\nABA Template Views are defined by the administrator. Refer to Create and Modify ABA Template View for further information.\nAuto Number Rules\nAuto Number Rules are defined by the administrator. Refer to Create and Modify Auto Number Rules for further information.\nSupports Group\nNew Drawing\nAllows you to create ABA drawings. Click to display the Create MDS Drawing window. The functionality of the Create MDS Drawing window is explained as part of the process to create ABA drawings for Supports. Refer to Create Supports ABA Drawing for further information.\nNew User View\nAllows you to create a User View on an existing ABA drawing. The process to create a User View is explained as part of the process to create ABA drawings for Supports. Refer to User View for further information.\nNew Over View\nAllows you to create an Over View on an existing ABA drawing. The process to create an Over View is explained as part of the process to create ABA drawings for Supports. Refer to User View for further information.\nRevision Control\nAllows you to update the Revision data on the ABA drawing sheet. Click to display the MDS Revision Control window. The functionality of the MDS Revision Control window is explained as part of the process to create ABA drawings for Supports. Refer to Revision Control for further information.\nLayer Control\nAllows you to control the layers for the ABA drawing. Click to display the MDS Layer Control window. The functionality of the MDS Layer Control window is explained as part of the process to create ABA drawings for Supports. Refer to Layer Control for further information.\nDrawing Lock\nAllows you to lock an ABA drawing, preventing any changes to be made. Click to display the Modify Drawing Lock window. The functionality of the Modify Drawing Lock window is explained as part of the process to create ABA drawings for Supports. Refer to Drawing Lock for further information.\nScale Override\nAllows you to control the view scale for the ABA drawing. Click to display the MDS Scale Override window. The functionality of the MDS Scale Override window is explained as part of the process to create ABA drawings for Supports. Refer to Scale Override for further information.\nRescale Pipe Symbols\nAllows you to rescale pipe symbols on an existing ABA drawing. The process to rescale pipe symbols is explained as part of the process to create ABA drawings for Supports. Refer to Rescale Pipe Symbols for further information.\n\n\n\nABA Drawing Process\nFile Browser\nABA Browse Sheets\nABA Defaults\nCreate and Modify Area Libraries\nCreate and Modify Areas\nCreate and Modify Classifications\nCreate and Modify Tasks\nCreate and Modify Labelling\nCreate and Modify Template Drawings\nCreate and Modify ABA Template View\nCreate and Modify Auto Number Rules\nCreate and Modify Keyplan Layers\nCreate and Modify Area Libraries\nCreate and Modify Areas\nCreate and Modify Classifications\nCreate and Modify Tasks\nCreate and Modify Labelling\nCreate and Modify Template Drawings\nCreate ABA Template Sheet\nCreate and Modify ABA Template View\nCreate and Modify Auto Number Rules\nCreate Supports ABA Drawing\nUser View\nUser View\nRevision Control\nLayer Control\nDrawing Lock\nScale Override\nRescale Pipe Symbols\nArea-Based Auto Group\nCreate Drawings\nABA Drawing Process\nLog Files\nArea ADP File Browser\nFile Browser\nBrowse\nABA Browse Sheets\nABA Browse Sheets\nDefaults\nABA Defaults\nCreate Group\nLibrary\nArea Library\nCreate and Modify Area Libraries\n\nArea\nCreate and Modify Areas\n\nClassification\nCreate and Modify Classifications\n\nTask\nCreate and Modify Tasks\n\nLabelling\nCreate and Modify Labelling\n\nTemplate\nDrawing\nCreate and Modify Template Drawings\n\nView\nCreate and Modify ABA Template View\nAuto Number Rules\nCreate and Modify Auto Number Rules\n\nKeyplan Layers\nCreate and Modify Keyplan Layers\n\nModify Group\nLibrary\nArea Library\nCreate and Modify Area Libraries\n\nArea\nCreate and Modify Areas\n\nClassification\nCreate and Modify Classifications\n\nTask\nCreate and Modify Tasks\n\nLabelling\nCreate and Modify Labelling\n\nTemplate\nDrawing\nCreate and Modify Template Drawings\n\nSheet\nCreate ABA Template Sheet\nView\nCreate and Modify ABA Template View\nAuto Number Rules\nCreate and Modify Auto Number Rules\n\nSupports Group\nNew Drawing\nCreate MDS Drawing\nCreate MDS Drawing\n. Refer to\nCreate Supports ABA Drawing\nNew User View\nUser View\nNew Over View\nUser View\nRevision Control\nMDS Revision Control\nMDS Revision Control\nRevision Control\nLayer Control\nMDS Layer Control\nMDS Layer Control\nLayer Control\nDrawing Lock\nModify Drawing Lock\nModify Drawing Lock\nDrawing Lock\nScale Override\nMDS Scale Override\nMDS Scale Override\nScale Override\nRescale Pipe Symbols\nRescale Pipe Symbols"}
{"Headers": "Quick Access Toolbar", "Content": "Adds options on the Project tab to the Quick Access Toolbar for quick and convenient access.\n\nBy default, the Quick Access Toolbar includes the following options.\nSave Work\nClick to save any changes made to data using the DRAW module. The facility is also available on the Project tab.\nGet Work\nClick to refresh the databases with changes made by other users since the session was started. The facility is also available on the Project tab.\nUndo\nClick to Undo the last change made to a drawing. You can continue to undo previous modifications.\nRedo\nClick to reverse the last undo made to a drawing. You can continue to redo undone modifications.\n\nSave Work\nClick to save any changes made to data using the DRAW module. The facility is also available on the Project tab.\n\nGet Work\nClick to refresh the databases with changes made by other users since the session was started. The facility is also available on the Project tab.\n\nUndo\nClick to Undo the last change made to a drawing. You can continue to undo previous modifications.\n\nRedo\nClick to reverse the last undo made to a drawing. You can continue to redo undone modifications.\nTo add a tab option to the Quick Access Toolbar, right-click the required option and select Add to Quick Access Toolbar from the drop-down list.\n\nThe tab option displays on the Quick Access Toolbar.\n\nBy default, the Quick Access Toolbar is positioned above the tabs. To position the Quick Access Toolbar below the tabs, right-click a tab and select Show Quick Access Toolbar Below the Ribbon from the drop-down list.\nAlternatively, on the Quick Access Toolbar, click Quick Access Toolbar and select Show Below the Ribbon from the drop-down list.\n\nWhen the Quick Access Toolbar is positioned below the ribbon, the drop-down list options become Show Quick Access Toolbar Above the Ribbon and Show Above the Ribbon.\nCustomize Quick Access Toolbar includes options for item removal and can also be returned to the default settings.\nSave Work\nClick to save any changes made to data using the DRAW module. The facility is also available on the Project tab.\nGet Work\nClick to refresh the databases with changes made by other users since the session was started. The facility is also available on the Project tab.\nUndo\nClick to Undo the last change made to a drawing. You can continue to undo previous modifications.\nRedo\nClick to reverse the last undo made to a drawing. You can continue to redo undone modifications.\n\n\n\nProject\nProject\nSave Work\nProject\nGet Work\nProject\nUndo\nRedo\nAdd to Quick Access Toolbar\nShow Quick Access Toolbar Below the Ribbon\nQuick Access Toolbar\nShow Below the Ribbon\nShow Quick Access Toolbar Above the Ribbon\nShow Above the Ribbon\nCustomize Quick Access Toolbar"}
{"Headers": "Draw Explorer", "Content": "Provides a graphical method for using the Draw Database.\n\nAbove the navigation tree is a search filter field as well as a drop-down list where predefined search filters can be selected. You can navigate to the selected filter in the explorer tree.\nClick Search to search for items. Refer to Search for further information.\nThe Draw Explorer displays the Draw database elements in a hierarchy. To expand an element hierarchy, click to the left of the element name. To contract an expanded element, click to the left of the element name.\nThe diagram illustrates the Draw database hierarchy and the owning relationship between Draw elements. The uppermost element is the World - represented symbolically as /*. The administrative elements Department (DEPT), Registry (REGI) and Drawing (DRWG) can be viewed in the Draw Explorer and module browsers, but cannot be displayed graphically in the Draw Canvas.\nThe principal elements are the owning Drawing (DRWG) element and member Sheets (SHEE). A Drawing can contain one or more Sheet (SHEE) elements and a Sheet is the highest level element that can be displayed in the Draw Canvas. The Sheet is defined by the elements stored below, with Views (VIEW), Regions (REGION) and annotation forming the Sheet appearance.\n\nTo modify elements in the Draw database, right-click an element to display a drop-down menu.\n\nAvailable menu options are dependant on the currently selected element type.\nOpen\nClick to open the element at sheet level or below in a new tab.\nAttributes\nClick to display the Attributes window. Refer to Attributes Window for further information.\nRename\nClick to rename the selected element. Refer to Rename Element for further information.\nDelete\nClick to delete the currently selected element. A confirm window displays asking you to OK the deletion. Click Yes to delete the element.\nDelete Members\nClick to delete members from an element. A confirm window displays asking you to OK the deletion. Click Yes to delete the members.\nSelect Element\nClick to select an element in the 2D view.\nHighlight Entities\nClick to highlight the currently selected elements in the 2D view.\nUnhighlight All Entities\nClick to remove the highlight from the currently highlighted elements in the 2D view.\nAdd To Current Collection\nClick to add the selected element to the list in the Collections window. Refer to Collections for further information.\nAdd Members to Current Collection\nClick to add members of the selected element to the list in the Collections window. Refer to Collections for further information.\nAdd Hierarchy to Current Collection\nClick to add the selected element hierarchy to the list in the Collections window. Refer to Collections for further information.\nNew Explorer\nAllows you to create a new explorer for the selected element or the element owner in the database hierarchy.\nCopy\nClick to copy the selected element and any associated members.\nPaste\nClick to paste a copied element and any associated members.\nOpen\nClick to open the element at sheet level or below in a new tab.\nAttributes\nClick to display the Attributes window. Refer to Attributes Window for further information.\nRename\nClick to rename the selected element. Refer to Rename Element for further information.\nDelete\nClick to delete the currently selected element. A confirm window displays asking you to OK the deletion. Click Yes to delete the element.\nDelete Members\nClick to delete members from an element. A confirm window displays asking you to OK the deletion. Click Yes to delete the members.\nSelect Element\nClick to select an element in the 2D view.\nHighlight Entities\nClick to highlight the currently selected elements in the 2D view.\nUnhighlight All Entities\nClick to remove the highlight from the currently highlighted elements in the 2D view.\nAdd To Current Collection\nClick to add the selected element to the list in the Collections window. Refer to Collections for further information.\nAdd Members to Current Collection\nClick to add members of the selected element to the list in the Collections window. Refer to Collections for further information.\nAdd Hierarchy to Current Collection\nClick to add the selected element hierarchy to the list in the Collections window. Refer to Collections for further information.\nNew Explorer\nAllows you to create a new explorer for the selected element or the element owner in the database hierarchy.\nCopy\nClick to copy the selected element and any associated members.\nPaste\nClick to paste a copied element and any associated members.\nYou can right-click the element name field at the top of the Draw Explorer to display a drop-down menu containing element naming options.\n\nUndo\nClick to undo the last action carried out in the element name field.\nCut\nClick to copy and remove selected text from the element name field to the clipboard.\nCopy\nClick to copy selected text from the element name field to the clipboard.\nPaste\nClick to paste copied text into the element name field.\nDelete\nClick to delete selected text in the element name field.\nSelect All\nClick to select all text in the element name field.\nRight to left Reading order\nClick to display the text in the element name field in right to left reading format.\nShow Unicode control characters\nClick to display Unicode control characters in the element name field.\nInsert Unicode control character\nSelect a character from the drop-down menu to insert a unicode control into the element name field.\nUndo\nClick to undo the last action carried out in the element name field.\nCut\nClick to copy and remove selected text from the element name field to the clipboard.\nCopy\nClick to copy selected text from the element name field to the clipboard.\nPaste\nClick to paste copied text into the element name field.\nDelete\nClick to delete selected text in the element name field.\nSelect All\nClick to select all text in the element name field.\nRight to left Reading order\nClick to display the text in the element name field in right to left reading format.\nShow Unicode control characters\nClick to display Unicode control characters in the element name field.\nInsert Unicode control character\nSelect a character from the drop-down menu to insert a unicode control into the element name field.\nRename Element\nRenames an element.\n\nThe Element Naming window allows you to rename the selected element and its members.\nCE\nClick to identify the currently selected element as the working element.\nName\nInput a new name for the element in the field.\nOnly\nSelect from the drop-down list, the name change is applied to the current element only.\nRe-name all\nSelect from the drop-down list, the name change is cascaded down to those members of the current element which incorporate the affected text within their names.\nNote:\nRe-name all is recommended to rename the entire hierarchy below the currently selected element.\nUn-name\nSelect from the drop-down list, the name becomes unset (the element is then identified only by its reference number).\nCE\nClick to identify the currently selected element as the working element.\nName\nInput a new name for the element in the field.\nOnly\nSelect from the drop-down list, the name change is applied to the current element only.\nRe-name all\nSelect from the drop-down list, the name change is cascaded down to those members of the current element which incorporate the affected text within their names.\nUn-name\nSelect from the drop-down list, the name becomes unset (the element is then identified only by its reference number).\nClick Reset to revert to the values applied when the Element Naming window was opened.\nClick Apply to confirm the modifications or Dismiss to discard any changes and close the Element Naming window.\nOpen\nClick to open the element at sheet level or below in a new tab.\nAttributes\nClick to display the Attributes window. Refer to Attributes Window for further information.\nRename\nClick to rename the selected element. Refer to Rename Element for further information.\nDelete\nClick to delete the currently selected element. A confirm window displays asking you to OK the deletion. Click Yes to delete the element.\nDelete Members\nClick to delete members from an element. A confirm window displays asking you to OK the deletion. Click Yes to delete the members.\nSelect Element\nClick to select an element in the 2D view.\nHighlight Entities\nClick to highlight the currently selected elements in the 2D view.\nUnhighlight All Entities\nClick to remove the highlight from the currently highlighted elements in the 2D view.\nAdd To Current Collection\nClick to add the selected element to the list in the Collections window. Refer to Collections for further information.\nAdd Members to Current Collection\nClick to add members of the selected element to the list in the Collections window. Refer to Collections for further information.\nAdd Hierarchy to Current Collection\nClick to add the selected element hierarchy to the list in the Collections window. Refer to Collections for further information.\nNew Explorer\nAllows you to create a new explorer for the selected element or the element owner in the database hierarchy.\nCopy\nClick to copy the selected element and any associated members.\nPaste\nClick to paste a copied element and any associated members.\nUndo\nClick to undo the last action carried out in the element name field.\nCut\nClick to copy and remove selected text from the element name field to the clipboard.\nCopy\nClick to copy selected text from the element name field to the clipboard.\nPaste\nClick to paste copied text into the element name field.\nDelete\nClick to delete selected text in the element name field.\nSelect All\nClick to select all text in the element name field.\nRight to left Reading order\nClick to display the text in the element name field in right to left reading format.\nShow Unicode control characters\nClick to display Unicode control characters in the element name field.\nInsert Unicode control character\nSelect a character from the drop-down menu to insert a unicode control into the element name field.\nCE\nClick to identify the currently selected element as the working element.\nName\nInput a new name for the element in the field.\nOnly\nSelect from the drop-down list, the name change is applied to the current element only.\nRe-name all\nSelect from the drop-down list, the name change is cascaded down to those members of the current element which incorporate the affected text within their names.\nNote:\nRe-name all is recommended to rename the entire hierarchy below the currently selected element.\nUn-name\nSelect from the drop-down list, the name becomes unset (the element is then identified only by its reference number).\nNote:\nRe-name all is recommended to rename the entire hierarchy below the currently selected element.\n\n\n\nSearch\nSearch\nDraw Explorer\nOpen\nAttributes\nAttributes\nAttributes Window\nRename\nRename Element\nDelete\nOK\nYes\nDelete Members\nYes\nSelect Element\nHighlight Entities\nUnhighlight All Entities\nAdd To Current Collection\nCollections\nCollections\nAdd Members to Current Collection\nCollections\nCollections\nAdd Hierarchy to Current Collection\nCollections\nCollections\nNew Explorer\nCopy\nPaste\nUndo\nCut\nCopy\nPaste\nDelete\nSelect All\nRight to left Reading order\nShow Unicode control characters\nInsert Unicode control character\nRename Element\nElement Naming\nCE\nName\nOnly\nRe-name all\nNote\n:\nRe-name all\nUn-name\nReset\nElement Naming\nApply\nDismiss\nElement Naming"}
{"Headers": "Active Properties", "Content": "Displays the default properties that are applied to new objects when they are created and subsequently applies the properties to selected objects, if required.\n\nThe current active properties display and can be modified. When a new object is created, these properties are automatically applied to that object.\nTo apply the current properties to an object, select the check boxes for those properties to be applied, and select a property from the drop-down list.\nPick the selected entity properties and select them as current\nClick to set the selected properties as the active properties. If multiple objects are selected they must have the same properties.\nApply the current setting to the selected entities\nClick to apply the active properties to a selected object using a cursor pick.\n\nPick the selected entity properties and select them as current\nClick to set the selected properties as the active properties. If multiple objects are selected they must have the same properties.\n\nApply the current setting to the selected entities\nClick to apply the active properties to a selected object using a cursor pick.\n\nPick the selected entity properties and select them as current\nClick to set the selected properties as the active properties. If multiple objects are selected they must have the same properties.\nApply the current setting to the selected entities\nClick to apply the active properties to a selected object using a cursor pick.\n\n\n\nPick the selected entity properties and select them as current\nApply the current setting to the selected entities"}
{"Headers": "Vertex Editor", "Content": "Sets selected vertex properties.\nThe Vertex Editor is only available if a single object is selected and an appropriate element, for example, an LDIM or a CONNCT element displays in the Properties window.\n\nThe top part of the Vertex Editor window displays a list of vertices for the object.\nSelect a vertex to display a list of available properties on the bottom part of the Vertex Editor window. The vertex properties can be modified.\nAdd\nClick to add a vertex to the list of available vertices.\nRemove\nClick to remove the currently selected vertex from the list of available vertices.\nUp\nClick to move the currently selected vertex up one position on the list of available vertices.\nDown\nClick to move the currently selected vertex down one position on the list of available vertices.\nPick Vertex on canvas\nAllows the selection of a vertex on the drawing canvas.\nYou are prompted to Select objects\nClick to identify the vertex.\nThe vertex is selected in the list of available vertices and the command ends automatically.\nSwitch to loop vertex\nDraws a shield vertex at the start point or end point of a connector.\nYou are prompted to Snap to positions to create connections for a loop vertex or\nInput values in the dimension fields and press Enter or click to identify the connection point.\nYou are then prompted to Snap to positions to create connection points for a loop vertex or <Finish>\nThe prompt is repeated, multiple connection points can be created.\nInput F at the prompt and press Enter to end the shield vertex creation process.\n\nAdd\nClick to add a vertex to the list of available vertices.\n\nRemove\nClick to remove the currently selected vertex from the list of available vertices.\n\nUp\nClick to move the currently selected vertex up one position on the list of available vertices.\n\nDown\nClick to move the currently selected vertex down one position on the list of available vertices.\n\nPick Vertex on canvas\nAllows the selection of a vertex on the drawing canvas.\nYou are prompted to Select objects\nClick to identify the vertex.\nThe vertex is selected in the list of available vertices and the command ends automatically.\n\nSwitch to loop vertex\nDraws a shield vertex at the start point or end point of a connector.\nYou are prompted to Snap to positions to create connections for a loop vertex or\nInput values in the dimension fields and press Enter or click to identify the connection point.\nYou are then prompted to Snap to positions to create connection points for a loop vertex or <Finish>\nThe prompt is repeated, multiple connection points can be created.\nInput F at the prompt and press Enter to end the shield vertex creation process.\n\nAdd\nClick to add a vertex to the list of available vertices.\nRemove\nClick to remove the currently selected vertex from the list of available vertices.\nUp\nClick to move the currently selected vertex up one position on the list of available vertices.\nDown\nClick to move the currently selected vertex down one position on the list of available vertices.\nPick Vertex on canvas\nAllows the selection of a vertex on the drawing canvas.\nYou are prompted to Select objects\nClick to identify the vertex.\nThe vertex is selected in the list of available vertices and the command ends automatically.\nSwitch to loop vertex\nDraws a shield vertex at the start point or end point of a connector.\nYou are prompted to Snap to positions to create connections for a loop vertex or\nInput values in the dimension fields and press Enter or click to identify the connection point.\nYou are then prompted to Snap to positions to create connection points for a loop vertex or <Finish>\nThe prompt is repeated, multiple connection points can be created.\nInput F at the prompt and press Enter to end the shield vertex creation process.\n\n\n\nProperties\nVertex Editor\nVertex Editor\nAdd\nRemove\nUp\nDown\nPick Vertex on canvas\nSelect objects\nSwitch to loop vertex\nSnap to positions to create connections for a loop vertex or\nEnter\nSnap to positions to create connection points for a loop vertex or <Finish>\nF\nEnter"}
{"Headers": "Database Hierarchy", "Content": "The hierarchy of elements in the Draw database is:\n\n\nNote:\nAutomatically created system elements do not display.\n\n\n\nNote\n:"}
{"Headers": "Options and Setup", "Content": "You can set various display, view, system, drafting, printing and file options. Appware load errors can be viewed and user defaults modified.\n\n\n"}
{"Headers": "Configuration Options", "Content": "Sets the coordinate display, explorer settings, form display and unit settings.\nThe following configuration options can be defined:\nCoordinates\nExplorer Settings\nConfiguration\nUnits\nCoordinates\nCoordinates\nExplorer Settings\nExplorer Settings\nConfiguration\nConfiguration\nUnits\nUnits\n\n\n\nCoordinates\nExplorer Settings\nConfiguration\nUnits\nCoordinates\nExplorer Settings\nConfiguration\nUnits"}
{"Headers": "View Options", "Content": "Sets the display, view, drafting and system settings.\nRefer to PowerCompass\u2122 for further information.\n\n\n\nPowerCompass\u2122\nPowerCompass\u2122"}
{"Headers": "Animation and Colour Display Options", "Content": "Sets the default animation, colours, axis options and crosshair options.\n\nAnimation\nSelect the Animate zoom changes check box to animate zoom changes.\nMove the Animation Time (seconds) slider to define the animation duration.\nColours\nYou can specify custom colours for various elements of the application's interface.\nSelect the element to modify from the list and click Modify to display the Color window.\n\nThe Color window allows you to define and select the colour for the currently selected element.\nBasic colors\nSelect a basic colour on the palette.\nCustom colors\nSelect a custom colour on the palette\nCrosshair\nMove the crosshair to specify a colour on the palette.\nSlider\nMove the slider to specify a colour.\nHue, Sat, Lum\nInput values in the fields to specify the colour values explicitly.\nRed, Green, Blue\nInput values in the fields to specify the colour values explicitly.\nAdd to Custom Colors\nClick to add the currently selected colour to the Custom colors palette.\nBasic colors\nSelect a basic colour on the palette.\nCustom colors\nSelect a custom colour on the palette\nCrosshair\nMove the crosshair to specify a colour on the palette.\nSlider\nMove the slider to specify a colour.\nHue, Sat, Lum\nInput values in the fields to specify the colour values explicitly.\nRed, Green, Blue\nInput values in the fields to specify the colour values explicitly.\nAdd to Custom Colors\nClick to add the currently selected colour to the Custom colors palette.\nClick OK to apply the colour or Cancel to discard any changes and close the Color Window.\nAxis Options\nYou can specify the size and position of the Axis icon.\nSelect the Draw Axis Icon check box to display the Axis Icon in the viewport.\nCrosshair Colour Mode\nYou can control the appearance of the crosshair.\nSelect the RGB option button to display the crosshair in colour mode, the X axis is red, the Y axis is green and the Z axis is blue.\nSelect the Grayscale option button to display the crosshair in grayscale mode.\nMove the Crosshair size slider to define the size of the crosshair.\nClick Reset to restore the default configuration settings. Refer to Reset Configuration for further information.\nClick Apply to update the selected settings.\nBasic colors\nSelect a basic colour on the palette.\nCustom colors\nSelect a custom colour on the palette\nCrosshair\nMove the crosshair to specify a colour on the palette.\nSlider\nMove the slider to specify a colour.\nHue, Sat, Lum\nInput values in the fields to specify the colour values explicitly.\nRed, Green, Blue\nInput values in the fields to specify the colour values explicitly.\nAdd to Custom Colors\nClick to add the currently selected colour to the Custom colors palette.\n\n\n\nReset Configuration\nAnimation\nAnimate zoom changes\nAnimation Time (seconds)\nColours\nModify\nColor\nColor\nBasic colors\nCustom colors\nCrosshair\nSlider\nHue, Sat, Lum\nRed, Green, Blue\nAdd to Custom Colors\nCustom colors\nOK\nCancel\nColor\nAxis Options\nDraw Axis Icon\nCrosshair Colour Mode\nRGB\nGrayscale\nCrosshair size\nReset\nReset Configuration\nApply"}
{"Headers": "Object Selection and Object Snap Settings", "Content": "Sets the default object selection, object snap, dynamic hint and anti aliasing options.\n\nSelection Settings\nAllows you to define the way in which objects are selected.\nPickbox Size\nMove the slider to define the display size of the pick box.\nGrip Size\nMove the slider to define the display size of the grip.\nMax number of Grips\nInput a value in the field to specify the maximum number of grips that can display simultaneously.\nSingle selection mode\nSelect the check box to specify that holding down Shift adds or removes selected objects.\nPickbox Size\nMove the slider to define the display size of the pick box.\nGrip Size\nMove the slider to define the display size of the grip.\nMax number of Grips\nInput a value in the field to specify the maximum number of grips that can display simultaneously.\nSingle selection mode\nSelect the check box to specify that holding down Shift adds or removes selected objects.\nObject Snap Settings\nAllows you to define the snap marker size and aperture box size. Functionality is also available to specify the Grid Settings and Object Snap settings.\nSnap Marker SIze\nMove the slider to define the size of the snap marker.\nAperture Box Size\nMove the slider to define the size of the aperture box.\nDisplay snap aperuture box\nSelect the check box to draw the snap aperture box while specifying coordinates with the mouse.\nAdvanced\nAllows you to specify the Object Snap settings and Grid settings. Refer to Object Snaps and Grid Settings for further information.\nSnap Marker SIze\nMove the slider to define the size of the snap marker.\nAperture Box Size\nMove the slider to define the size of the aperture box.\nDisplay snap aperuture box\nSelect the check box to draw the snap aperture box while specifying coordinates with the mouse.\nAdvanced\nAllows you to specify the Object Snap settings and Grid settings. Refer to Object Snaps and Grid Settings for further information.\nDynamic Hints Settings\nSelect the Animate dynamic hints check box to display hints with full opacity only when the you are not active (for example, you are not moving the mouse).\nDe-select the Animate dynamic hints check box to display hints at all times, regardless of your activity.\nAnti-aliasing\nSelect the Anti-aliasing check box to turn on anti-aliasing.\nClick Reset to restore the default configuration settings. Refer to Reset Configuration for further information.\nClick Apply to update the selected settings.\nContext Editor Precision\nSpecifies the number of decimal characters displayed on the context editor. The default value is 0.\nIn the example, the Decimal precision is 2 which displays two decimal characters on the context editor.\n\nPickbox Size\nMove the slider to define the display size of the pick box.\nGrip Size\nMove the slider to define the display size of the grip.\nMax number of Grips\nInput a value in the field to specify the maximum number of grips that can display simultaneously.\nSingle selection mode\nSelect the check box to specify that holding down Shift adds or removes selected objects.\nSnap Marker SIze\nMove the slider to define the size of the snap marker.\nAperture Box Size\nMove the slider to define the size of the aperture box.\nDisplay snap aperuture box\nSelect the check box to draw the snap aperture box while specifying coordinates with the mouse.\nAdvanced\nAllows you to specify the Object Snap settings and Grid settings. Refer to Object Snaps and Grid Settings for further information.\n\n\n\nObject Snaps\nGrid Settings\nReset Configuration\nSelection Settings\nPickbox Size\nGrip Size\nMax number of Grips\nSingle selection mode\nShift\nObject Snap Settings\nSnap Marker SIze\nAperture Box Size\nDisplay snap aperuture box\nAdvanced\nObject Snaps\nGrid Settings\nDynamic Hints Settings\nAnimate dynamic hints\nAnimate dynamic hints\nAnti-aliasing\nReset\nReset Configuration\nApply\nContext Editor Precision\nDecimal precision"}
{"Headers": "View Configuration Options", "Content": "Sets the default view configuration, view regeneration and view projection options.\n\nThe sliders can be used to change the sensitivities of view operations. Move the slider to the right to increase the sensitivity.\nMoving the Curve Vectorization Precision slider to the right specifies more precise curve generation, this can degrade performance for extensive drawings.\nRegeneration\nSelect the Automatic regen on zoom change check box to automatically regenerate objects when the scale is changed.\nAutomatic regeneration is performed in the background, so you can always view the best curve vectorization, without performance penalties, when working with a drawing.\nProjection\nYou can define the default view angle for a projection. Refer to Create Orthographic Projection View for further information.\nSelect the First angle option button to display the defining points of each view of a 3-dimensional object, in the direction of the viewer's gaze onto the interior walls of an imaginary 3-dimensional box surrounding the object.\n\nSelect the Third angle option button to produce orthographic views of 3-dimensional objects The defining points of each view of the object project onto the external face of an imaginary 3-dimensional box. The viewpoint is changed by rotation through 90 degree increments about the centre of the object.\n\nDrawlist\nYou can define the default drawlist behaviour for creating projection, section and detail views. These view types are all created from a source view.\nSelect the New Drawlist option button to create a new drawlist as a copy of the source view drawlist.\nSelect the Share Drawlist option button to reference the drawlist from the source view drawlist.\nClick Reset to restore the default configuration settings. Refer to Reset Configuration for further information.\nClick Apply to update the selected settings.\n\n\n\nCreate Orthographic Projection View\nReset Configuration\nCurve Vectorization Precision\nRegeneration\nAutomatic regen on zoom change\nProjection\nCreate Orthographic Projection View\nFirst angle\nThird angle\nDrawlist\nNew Drawlist\nShare Drawlist\nReset\nReset Configuration\nApply"}
{"Headers": "Naming System Options", "Content": "Sets the default naming system options for drawing tabs.\n\nSettings are remembered between sessions and changes are made as soon as they are applied.\nShort Name\nSelect the option button to display the short name.\nFull Name\nSelect the option button to display the full evaluated name.\nIndexed Name\nSelect the option button to display a name built from the owner name, ref number and drawing name or special system prefix with record number.\nTitle or Short Name\nSelect the option button to display the title or, if unset, the short name.\nTitle or Full Name\nSelect the option button to display the title or, if unset, the full evaluated name.\nTitle or Indexed Name\nSelect the option button to display the title or, if unset, the indexed name\nShort Name\nSelect the option button to display the short name.\nFull Name\nSelect the option button to display the full evaluated name.\nIndexed Name\nSelect the option button to display a name built from the owner name, ref number and drawing name or special system prefix with record number.\nTitle or Short Name\nSelect the option button to display the title or, if unset, the short name.\nTitle or Full Name\nSelect the option button to display the title or, if unset, the full evaluated name.\nTitle or Indexed Name\nSelect the option button to display the title or, if unset, the indexed name\nClick Reset to restore the default configuration settings. Refer to Reset Configuration for further information.\nClick Apply to update the selected settings.\nShort Name\nSelect the option button to display the short name.\nFull Name\nSelect the option button to display the full evaluated name.\nIndexed Name\nSelect the option button to display a name built from the owner name, ref number and drawing name or special system prefix with record number.\nTitle or Short Name\nSelect the option button to display the title or, if unset, the short name.\nTitle or Full Name\nSelect the option button to display the title or, if unset, the full evaluated name.\nTitle or Indexed Name\nSelect the option button to display the title or, if unset, the indexed name\n\n\n\nReset Configuration\nShort Name\nFull Name\nIndexed Name\nTitle or Short Name\nTitle or Full Name\nTitle or Indexed Name\nReset\nReset Configuration\nApply"}
{"Headers": "Object Visibility System Options", "Content": "Sets the object visibility, print and display calculation options.\n\nObject Visibility\nObject Visibility is used to specify the algorithm that determines the visibility of objects inserted in blocks.\nYou can independently set algorithms to be used when the application tests if an object's layer is on, or if it should be visible in the printout.\nPerformance\nPerformance is used to set how the extents of a 3D model or its parts are determined by the application.\nFor complicated drawings, exact extents calculations can be time-consuming and can therefore degrade the performance of the Zoom Extents operations. If performance is an issue, it is recommended that approximate calculations are used.\nAdditionally, whether or not entities should be autoregenerated when the zoom level changes can be specified. By default this feature is on, but it can be turned off to improve performance. If the feature is off, you can force regeneration with the REGEN command.\nClick Reset to restore the default configuration settings. Refer to Reset Configuration for further information.\nClick Apply to update the selected settings.\n\n\n\nReset Configuration\nObject Visibility\nPerformance\nReset\nReset Configuration\nApply"}
{"Headers": "Reset Configuration", "Content": "Restores project configuration settings to their default settings.\n\nYou can select the check boxes to specify the settings to be restored to their defaults.\nClick Select all to select all available settings.\nClick Clear all to de-select all available settings.\nClick OK to reset the selected settings or Cancel to discard any changes and close the Reset Settings window.\n\n\n\nSelect all\nClear all\nOK\nCancel\nReset Settings"}
{"Headers": "Appware Load Errors", "Content": "Displays errors received during the Draw Appware load process.\n\nThe Default Load Errors window displays a list of load errors. If no load errors are received during the Draw Appware load process, the message No Errors Occurred During Load displays.\nClick Cancel to close the Default Load Errors window\n\n\n\nDefault Load Errors\nNo Errors Occurred During Load\nCancel\nDefault Load Errors"}
{"Headers": "Modify User Defaults", "Content": "Sets system level defaults for individual users.\n\nThe functionality of the User Defaults window is explained as part of the process to set the system defaults. Refer to Set System Defaults for further information.\nNote:\nSubsequent changes made to defaults at system level overwrite user level defaults. Therefore all user-level defaults should be set after all system level defaults are set.\n\n\n\nSet System Defaults\nUser Defaults\nSet System Defaults\nNote\n:"}
{"Headers": "Basic Operations", "Content": "There are a number of basic operations within the Draw application.\n\n\n"}
{"Headers": "Open Sheet", "Content": "Opens a drawing sheet from a selection in the database hierarchy.\nThe Open window displays the database hierarchy. The functionality of the Open window is the same as the Hierarchy Browser window, except as described. Refer to Create Departments, Registries and Drawings with the Hierarchy Browser Window or Open Window for further information.\n\nThe Open window allows you to browse for the required sheet.\nThe Search Project field finds any elements of the appropriate type with a name that contains the search fragment (anywhere in the name). Prefixing the search fragment with a forward slash '/' to indicate the \u2018name begins with\u2019 results in a faster search.\n\nThe list in the lower-right corner of the window allows you to restrict the window display to thumbnails for a selected type of element.\nSheets are listed in the right-hand part of the Open window. Select the required sheet, or input a name in the Name field, and click Open. If the selected sheet is claimed by another user or if it belongs to a read-only database, you are given the option to open the drawing as a temporary copy.\nAlternatively, select the required sheet, or input a name in the Name field, and click Open Temporary Copy. The sheet is opened as a copy in a temporary workspace not meant for storage. If the selected sheet is claimed by another user, you can temporarily modify a sheet without excluding others from modifying the original sheet. All functionality is available when a sheet is opened as a temporary copy, modifications to the sheet are not stored when a Save Work is carried out.\nBy default, a notification band is displayed at the top of the drawing canvas when a sheet is opened as a temporary copy.\n\nClick Cancel to discard any changes and close the Open window.\nView Loading Settings\nIf the number of entities in a view exceeds a set limit, a thumbnail (bitmap) of the view is displayed on the drawing canvas when the drawing is opened, instead of the design geometry that is normally displayed. The functionality enables quick loading of larger drawings and is defined by the administrator.\nThe example displays a view where the number of entities does not exceed the set limit.\n\nThe example displays the same view where the number of entities exceeds the set limit.\n\nWhen a thumbnail is displayed:\nThe view can be displayed correctly by making it the current owner.\nIf no thumbnail exists, which is the case for drawings generated in DRAFT 12.1 or previous releases of Draw, a blank sheet is displayed when the number of entities in a view exceeds the set limit.\nYou cannot access the entities in the view\nNothing happens when clicking on the view\nDraw does not navigate to model elements.\nYou cannot access the entities in the view\nYou cannot access the entities in the view\nNothing happens when clicking on the view\nNothing happens when clicking on the view\nDraw does not navigate to model elements.\nDraw does not navigate to model elements.\nNote:\nTo create sheets and views, refer to Create Drawing Sheets and Support Elements and Create Views for further information.\nNote:\nGenerally the name search is not case sensitive. However, the 'name begins with' search is case sensitive, although fully capitalized element names are still matched upon.\n\n\n\nCreate Drawing Sheets and Support Elements\nCreate Views\nCreate Departments, Registries and Drawings with the Hierarchy Browser Window or Open Window\nNote\n:\nCreate Drawing Sheets and Support Elements\nCreate Views\nOpen\nOpen\nHierarchy Browser\nCreate Departments, Registries and Drawings with the Hierarchy Browser Window or Open Window\nOpen\nSearch Project\nNote\n:\nOpen\nName\nOpen\nName\nOpen Temporary Copy\nCancel\nOpen\nView Loading Settings"}
{"Headers": "Select View", "Content": "Selects a view on the currently displayed sheet.\nTo select a view, right-click the drawing and select Navigator from the Wheel menu.\nA gallery of thumbnail views displays for the current sheet.\n\nThe first thumbnail is of the sheet itself, followed by all other available views.\nHover the cursor over a thumbnail to display the name of the view, the currently selected thumbnail is highlighted on the drawing.\n\nClick the arrow at either end of the gallery to scroll to the left or to the right and display further thumbnails views.\nClick a thumbnail to display the selected view full size on the screen.\n\n\n\n"}
{"Headers": "Tab Groups", "Content": "If more than one drawing is open, Draw displays each drawing in the view as a tab (provided that Tabbed View is the current view format, refer to Tabbed View for further information). You can click a tab to display the drawing in the view.\nThe tab view of open drawings can be grouped to display the drawings in a split horizontal or vertical window.\nTo create a new horizontal tab group, right-click the drawing tab to be viewed in a split window and select New Horizontal Tab Group from the drop-down list.\n\nThe drawing tab displays in a split window and a tab group is created.\n\nTo create a new vertical tab group, right-click the drawing tab to be viewed in a split window and select New Vertical Tab Group from the drop-down list.\n\nThe drawing tab displays in a split window and a tab group is created.\n\nWhen tab groups are created, you can move drawing tabs from one tab group to another.\nTo move an existing drawing tab to a newer horizontal or vertical tab group, right-click the drawing tab to be moved and select Move to Next Tab Group from the drop-down list.\n\nTo move an existing drawing tab to a previous horizontal or vertical tab group, right-click the drawing tab to be moved and select Move to Previous Tab Group from the drop-down list.\n\n\n\n\nTabbed View\nNew Horizontal Tab Group\nNew Vertical Tab Group\nMove to Next Tab Group\nMove to Previous Tab Group"}
{"Headers": "Power Selector", "Content": "Quickly selects primitives or annotations based on filter criteria. Functionality is also available to select annotations based on an intelligent link to the model.\n\nSelect entity group\nSelect Primitive from the drop-down list to select primitive elements using primitive filter criteria. Refer to Primitive Selection for further information.\nSelect Annotation from the drop-down list to select label or dimension elements using annotation filter criteria. Refer to Annotation Selection for further information.\nSelect entity source\nSelect All from the drop-down list to filter the selection of all elements on the current sheet.\nSelect Current Owner from the drop-down list to filter the selection of all elements that you currently own.\nFill filters automatically from selected entity\nClick to filter the selection of all elements that match a picked element.\nYou are prompted to Select entity\nClick to identify the element, the filter fields are populated with the element properties.\nSelect matching entities and zoom\nClick to select all elements that match the filter criteria, the extent of the selected elements displays on the drawing canvas.\nSend results to collection form\nClick to select all elements that match the filter criteria, the Collections window displays. Refer to Collections for further information.\nClean Power Selector Form\nClick to remove all defined filter criteria from the Power Selector window.\n\nSelect entity group\nSelect Primitive from the drop-down list to select primitive elements using primitive filter criteria. Refer to Primitive Selection for further information.\nSelect Annotation from the drop-down list to select label or dimension elements using annotation filter criteria. Refer to Annotation Selection for further information.\n\nSelect entity source\nSelect All from the drop-down list to filter the selection of all elements on the current sheet.\nSelect Current Owner from the drop-down list to filter the selection of all elements that you currently own.\n\nFill filters automatically from selected entity\nClick to filter the selection of all elements that match a picked element.\nYou are prompted to Select entity\nClick to identify the element, the filter fields are populated with the element properties.\n\nSelect matching entities and zoom\nClick to select all elements that match the filter criteria, the extent of the selected elements displays on the drawing canvas.\n\nSend results to collection form\nClick to select all elements that match the filter criteria, the Collections window displays. Refer to Collections for further information.\n\nClean Power Selector Form\nClick to remove all defined filter criteria from the Power Selector window.\n\nSelect entity group\nSelect Primitive from the drop-down list to select primitive elements using primitive filter criteria. Refer to Primitive Selection for further information.\nSelect Annotation from the drop-down list to select label or dimension elements using annotation filter criteria. Refer to Annotation Selection for further information.\nSelect entity source\nSelect All from the drop-down list to filter the selection of all elements on the current sheet.\nSelect Current Owner from the drop-down list to filter the selection of all elements that you currently own.\nFill filters automatically from selected entity\nClick to filter the selection of all elements that match a picked element.\nYou are prompted to Select entity\nClick to identify the element, the filter fields are populated with the element properties.\nSelect matching entities and zoom\nClick to select all elements that match the filter criteria, the extent of the selected elements displays on the drawing canvas.\nSend results to collection form\nClick to select all elements that match the filter criteria, the Collections window displays. Refer to Collections for further information.\nClean Power Selector Form\nClick to remove all defined filter criteria from the Power Selector window.\n\n\n\nPrimitive Selection\nAnnotation Selection\nCollections\nSelect entity group\nPrimitive\nPrimitive Selection\nAnnotation\nAnnotation Selection\nSelect entity source\nAll\nCurrent Owner\nFill filters automatically from selected entity\nSelect entity\nSelect matching entities and zoom\nSend results to collection form\nCollections\nCollections\nClean Power Selector Form\nPower Selector"}
{"Headers": "Close Drawing", "Content": "Closes the current drawing, all open drawings or all drawings except the current drawing.\nTo close the current drawing, you can right-click the drawing tab and select Close from the drop-down list.\nIf more than one drawing is open, you can close all drawings except the currently selected drawing. Right-click the drawing tab to remain open and select Close All Tabs Except This from the drop-down list.\n\n\n\n\nClose\nClose All Tabs Except This"}
{"Headers": "Pan and Zoom", "Content": "Sets the position and magnification of the drawing in the view.\n\n\n"}
{"Headers": "Pan and Zoom using the Mouse", "Content": "Sets the position and magnification of the drawing in the view using the mouse.\nTo zoom in to a drawing, roll the mouse wheel up.\nTo zoom out from a drawing, roll the mouse wheel down.\nTo pan, click and hold the mouse wheel and drag the drawing in the required direction.\nTo zoom in to a drawing, roll the mouse wheel up.\nTo zoom in to a drawing, roll the mouse wheel up.\nTo zoom out from a drawing, roll the mouse wheel down.\nTo zoom out from a drawing, roll the mouse wheel down.\nTo pan, click and hold the mouse wheel and drag the drawing in the required direction.\nTo pan, click and hold the mouse wheel and drag the drawing in the required direction.\n\n\n"}
{"Headers": "Pan Options", "Content": "Sets the position of the drawing in the view.\nPan Realtime\nSelect from the drop-down list, you can then click and hold the mouse wheel and drag the drawing in the required direction.\nPan Point\nSelect from the drop-down list to pan from one specified point to another.\nYou are prompted to Specify base point\nClick to identify the point to pan from.\nYou are then prompted to Specify the second point\nClick to identify the point to pan from.\nThe drawing view pans to the selected point.\nPan Left\nSelect from the drop-down list to pan the drawing view to the left.\nPan Right\nSelect from the drop-down list to pan the drawing view to the Right.\nPan Top\nSelect from the drop-down list to pan the drawing view to up.\nPan Bottom\nSelect from the drop-down list to pan the drawing view down.\nPan Realtime\nSelect from the drop-down list, you can then click and hold the mouse wheel and drag the drawing in the required direction.\nPan Point\nSelect from the drop-down list to pan from one specified point to another.\nYou are prompted to Specify base point\nClick to identify the point to pan from.\nYou are then prompted to Specify the second point\nClick to identify the point to pan from.\nThe drawing view pans to the selected point.\nPan Left\nSelect from the drop-down list to pan the drawing view to the left.\nPan Right\nSelect from the drop-down list to pan the drawing view to the Right.\nPan Top\nSelect from the drop-down list to pan the drawing view to up.\nPan Bottom\nSelect from the drop-down list to pan the drawing view down.\n\nPan Realtime\nSelect from the drop-down list, you can then click and hold the mouse wheel and drag the drawing in the required direction.\nPan Point\nSelect from the drop-down list to pan from one specified point to another.\nYou are prompted to Specify base point\nClick to identify the point to pan from.\nYou are then prompted to Specify the second point\nClick to identify the point to pan from.\nThe drawing view pans to the selected point.\nPan Left\nSelect from the drop-down list to pan the drawing view to the left.\nPan Right\nSelect from the drop-down list to pan the drawing view to the Right.\nPan Top\nSelect from the drop-down list to pan the drawing view to up.\nPan Bottom\nSelect from the drop-down list to pan the drawing view down.\n\n\n\nPan Realtime\nPan Point\nSpecify base point\nSpecify the second point\nPan Left\nPan Right\nPan Top\nPan Bottom"}
{"Headers": "Zoom Options", "Content": "Sets the magnification of the drawing in the view.\nZoom Extents\nSelect from the drop-down list to display the drawing view at full size on the screen.\nZoom In\nSelect from the drop-down list to zoom in to a drawing.\nZoom Out\nSelect from the drop-down list to zoom out from a drawing.\nZoom Realtime\nSelect from the drop-down list, you can then click and hold the mouse wheel and drag the view in the required direction.\nTo zoom in to a drawing, roll the mouse wheel up.\nTo zoom out from a drawing, roll the mouse wheel down.\nZoom Window\nSelect from the drop-down list to zoom into a defined area.\nYou are prompted to Specify first corner\nClick to identify the first corner of the zoom area.\nYou are then prompted to Specify opposite corner\nClick to identify the opposite corner of the zoom area.\nThe drawing view zooms to the selected zoom area.\nZoom Dynamic\nSelect from the drop-down list to display an area selection box.\nMove the cursor as required until the left side of the area selection box corresponds to the left side of the area to be zoomed into and click the left mouse button.\nThen move the mouse left or right to define the size of the area selection box.\nClick the left mouse button and move the mouse up or down to define position of the area selection box.\nPress Enter to zoom to the selection box area.\nZoom Scale\nSelect from the drop-down list to zoom by a defined scale.\nYou are prompted to Enter Scale factor (nX or nXP)\nInput a value at the prompt, for example, 2x to zoom in at twice the scale.\nZoom Centre\nSelect from the drop-down list to zoom using a specified center point.\nYou are prompted to Specify centre point\nClick to identify the center point.\nYou are then prompted to Enter magnification factor or new height\nInput a value at the prompt, for example, 2x to zoom in at twice the scale.\nAlternatively, you can click the drawing to identify the height of the zoom area from the center point.\nZoom Object\nSelect from the drop-down list to zoom in to a selected object or objects.\nYou are prompted to Select objects\nClick to identify the zoom object or objects.\nPress Enter to zoom to the selected object area.\nZoom Extents\nSelect from the drop-down list to display the drawing view at full size on the screen.\nZoom In\nSelect from the drop-down list to zoom in to a drawing.\nZoom Out\nSelect from the drop-down list to zoom out from a drawing.\nZoom Realtime\nSelect from the drop-down list, you can then click and hold the mouse wheel and drag the view in the required direction.\nTo zoom in to a drawing, roll the mouse wheel up.\nTo zoom out from a drawing, roll the mouse wheel down.\nZoom Window\nSelect from the drop-down list to zoom into a defined area.\nYou are prompted to Specify first corner\nClick to identify the first corner of the zoom area.\nYou are then prompted to Specify opposite corner\nClick to identify the opposite corner of the zoom area.\nThe drawing view zooms to the selected zoom area.\nZoom Dynamic\nSelect from the drop-down list to display an area selection box.\nMove the cursor as required until the left side of the area selection box corresponds to the left side of the area to be zoomed into and click the left mouse button.\nThen move the mouse left or right to define the size of the area selection box.\nClick the left mouse button and move the mouse up or down to define position of the area selection box.\nPress Enter to zoom to the selection box area.\nZoom Scale\nSelect from the drop-down list to zoom by a defined scale.\nYou are prompted to Enter Scale factor (nX or nXP)\nInput a value at the prompt, for example, 2x to zoom in at twice the scale.\nZoom Centre\nSelect from the drop-down list to zoom using a specified center point.\nYou are prompted to Specify centre point\nClick to identify the center point.\nYou are then prompted to Enter magnification factor or new height\nInput a value at the prompt, for example, 2x to zoom in at twice the scale.\nAlternatively, you can click the drawing to identify the height of the zoom area from the center point.\nZoom Object\nSelect from the drop-down list to zoom in to a selected object or objects.\nYou are prompted to Select objects\nClick to identify the zoom object or objects.\nPress Enter to zoom to the selected object area.\n\nZoom Extents\nSelect from the drop-down list to display the drawing view at full size on the screen.\nZoom In\nSelect from the drop-down list to zoom in to a drawing.\nZoom Out\nSelect from the drop-down list to zoom out from a drawing.\nZoom Realtime\nSelect from the drop-down list, you can then click and hold the mouse wheel and drag the view in the required direction.\nTo zoom in to a drawing, roll the mouse wheel up.\nTo zoom out from a drawing, roll the mouse wheel down.\nZoom Window\nSelect from the drop-down list to zoom into a defined area.\nYou are prompted to Specify first corner\nClick to identify the first corner of the zoom area.\nYou are then prompted to Specify opposite corner\nClick to identify the opposite corner of the zoom area.\nThe drawing view zooms to the selected zoom area.\nZoom Dynamic\nSelect from the drop-down list to display an area selection box.\nMove the cursor as required until the left side of the area selection box corresponds to the left side of the area to be zoomed into and click the left mouse button.\nThen move the mouse left or right to define the size of the area selection box.\nClick the left mouse button and move the mouse up or down to define position of the area selection box.\nPress Enter to zoom to the selection box area.\nZoom Scale\nSelect from the drop-down list to zoom by a defined scale.\nYou are prompted to Enter Scale factor (nX or nXP)\nInput a value at the prompt, for example, 2x to zoom in at twice the scale.\nZoom Centre\nSelect from the drop-down list to zoom using a specified center point.\nYou are prompted to Specify centre point\nClick to identify the center point.\nYou are then prompted to Enter magnification factor or new height\nInput a value at the prompt, for example, 2x to zoom in at twice the scale.\nAlternatively, you can click the drawing to identify the height of the zoom area from the center point.\nZoom Object\nSelect from the drop-down list to zoom in to a selected object or objects.\nYou are prompted to Select objects\nClick to identify the zoom object or objects.\nPress Enter to zoom to the selected object area.\n\n\n\nZoom Extents\nZoom In\nZoom Out\nZoom Realtime\nZoom Window\nSpecify first corner\nSpecify opposite corner\nZoom Dynamic\nEnter\nZoom Scale\nEnter Scale factor (nX or nXP)\n2x\nZoom Centre\nSpecify centre point\nEnter magnification factor or new height\n2x\nZoom Object\nSelect objects\nEnter"}
{"Headers": "Undo and Redo Changes", "Content": "Removes or re-inserts changes since the session was last saved.\nChanges can be also be removed and re-inserted using the Quick Access Toolbar.\nUndo\nSelect from the drop-down list to undo the last change. You can continue to undo previous modifications, each time Undo is clicked the previous change is rolled back.\nUndo multiple\nSelect from the drop-down list to undo a specified number of changes or a group of changes.\nYou are prompted to Enter the number of actions to undo or <1>\nInput the number of actions to undo at the prompt, then press Enter.\nThroughout the undo process you can press ESC to cancel the command. Additional functionality is also available.\nBegin\nPress the down arrow key and select Begin to create a group of actions. Refer Create a Group of Actions for further information.\nAll\nPress the down arrow key and select All to undo all changes since the last save.\nUndo all\nSelect from the drop-down list to undo all changes since the last save.\nRedo\nSelect from the drop-down list to redo the last undone change. You can continue to redo undone modifications, each time Redo is clicked the next undo is reinserted.\nRedo multiple\nSelect from the drop-down list to redo a specified number of changes or a groups of changes.\nYou are prompted to Enter the number of actions to redo or <Last>\nInput the number of actions to undo at the prompt, then press Enter.\nThroughout the redo process you can press ESC to cancel the command. Additional functionality is also available.\nAll\nPress the down arrow key and select All to redo all undone changes since the last save.\nLast\nPress the down arrow key and select Last to redo the last undone change.\nRedo all\nSelect from the drop-down list to redo all undone changes since the last save.\nUndo\nSelect from the drop-down list to undo the last change. You can continue to undo previous modifications, each time Undo is clicked the previous change is rolled back.\nUndo multiple\nSelect from the drop-down list to undo a specified number of changes or a group of changes.\nYou are prompted to Enter the number of actions to undo or <1>\nInput the number of actions to undo at the prompt, then press Enter.\nThroughout the undo process you can press ESC to cancel the command. Additional functionality is also available.\n\n\nBegin\nPress the down arrow key and select Begin to create a group of actions. Refer Create a Group of Actions for further information.\n\nAll\nPress the down arrow key and select All to undo all changes since the last save.\nUndo all\nSelect from the drop-down list to undo all changes since the last save.\nRedo\nSelect from the drop-down list to redo the last undone change. You can continue to redo undone modifications, each time Redo is clicked the next undo is reinserted.\nRedo multiple\nSelect from the drop-down list to redo a specified number of changes or a groups of changes.\nYou are prompted to Enter the number of actions to redo or <Last>\nInput the number of actions to undo at the prompt, then press Enter.\nThroughout the redo process you can press ESC to cancel the command. Additional functionality is also available.\n\n\nAll\nPress the down arrow key and select All to redo all undone changes since the last save.\n\nLast\nPress the down arrow key and select Last to redo the last undone change.\nRedo all\nSelect from the drop-down list to redo all undone changes since the last save.\n\nUndo\nSelect from the drop-down list to undo the last change. You can continue to undo previous modifications, each time Undo is clicked the previous change is rolled back.\nUndo multiple\nSelect from the drop-down list to undo a specified number of changes or a group of changes.\nYou are prompted to Enter the number of actions to undo or <1>\nInput the number of actions to undo at the prompt, then press Enter.\nThroughout the undo process you can press ESC to cancel the command. Additional functionality is also available.\nBegin\nPress the down arrow key and select Begin to create a group of actions. Refer Create a Group of Actions for further information.\nAll\nPress the down arrow key and select All to undo all changes since the last save.\nUndo all\nSelect from the drop-down list to undo all changes since the last save.\nRedo\nSelect from the drop-down list to redo the last undone change. You can continue to redo undone modifications, each time Redo is clicked the next undo is reinserted.\nRedo multiple\nSelect from the drop-down list to redo a specified number of changes or a groups of changes.\nYou are prompted to Enter the number of actions to redo or <Last>\nInput the number of actions to undo at the prompt, then press Enter.\nThroughout the redo process you can press ESC to cancel the command. Additional functionality is also available.\nAll\nPress the down arrow key and select All to redo all undone changes since the last save.\nLast\nPress the down arrow key and select Last to redo the last undone change.\nRedo all\nSelect from the drop-down list to redo all undone changes since the last save.\nNote:\nChanges made prior to the last save (refer to Quick Access Toolbar for further information) cannot be undone.\n\n\n\nQuick Access Toolbar\nQuick Access Toolbar\nCreate a Group of Actions\nNote\n:\nQuick Access Toolbar\nQuick Access Toolbar\nUndo\nUndo\nUndo multiple\nEnter the number of actions to undo or <1>\nEnter\nESC\nBegin\nBegin\nCreate a Group of Actions\nAll\nAll\nUndo all\nRedo\nRedo\nRedo multiple\nEnter the number of actions to redo or <Last>\nEnter\nESC\nAll\nAll\nLast\nLast\nRedo all"}
{"Headers": "Print Sheets", "Content": "Sets the printing options and allows you to print drawing sheets.\n\nPrint/Plot\nClick to print the current sheet.\nWhen Print/Plot is selected, the current print settings are saved.\nMulti Print/Plot\nAllows you to print multiple sheets, Click to display the Open window.\nThe functionality of the Open window is explained, refer to Export Multiple Sheets for further information.\nClick Open to print the selected sheets.\nDuring the print process, a progress bar displays which tracks the progress.\nClick Cancel to cancel the print process,\nCopies\nInput the number of copies required in the field.\nSpecify the printer to use\nSelect the printer or plotter from the drop-down list. The default printing device is pre-selected.\nPrint to File\nSelect the check box to print to a file output. For example a .prn file.\nWhen Print/Plot is selected, the Save As window displays.\nYou must input a filename and select the required file type. The default filename is the drawing name.\nClick Save to print the file or Cancel to discard any changes and close the Save As window.\nPrinter Properties\nClick to define the printer specific properties for the currently selected printer.\nSpecify plot styles\nAllows you to define the colour, fill and line style settings for the print. Click to display a drop-down list.\nSelect Default from the drop-down list, the colour, fill and line style settings are not changed.\nSelect Monochrome from the drop-down list to print all colours as black and white.\nSelect Greyscale from the drop-down list to print all colours as greyscale.\nSelect All Filltypes as Solid from the drop-down list to print all filled objects with a solid fill. For example, all objects with shaded fill properties are printed with a solid fill.\nSelect All Linetypes as Solid from the drop-down list to print all lines with a solid line type. For example, all dashed lines are printed as solid lines.\nAs well as the default plot styles provided with the product, additional plot styles can be created. Refer to Plot Style for further information.\nSpecify the object type to be printed\nAllows you to define the printed area. Click to display a drop-down list.\nSelect Sheet from the drop-down list to print the currently selected sheet.\nSelect Display from the drop-down list to print the current display area of a sheet.\nSelect Extents from the drop-down list to print the extents of a sheet.\nSelect Window from the drop-down list to print a defined display area. Click Specify window to define the display area to be printed.\nSpecify window\nClick to define the display area to be printed. The application displays the current sheet.\nYou are prompted to Specify first corner\nClick to identify the first corner of the output area.\nYou are then prompted to Specify opposite corner\nClick to identify the opposite corner of the output area.\nSelect one of the available scale presets\nAllows you to define the printed drawing scale. Click to display a drop-down list.\nYou can select a preset scale from the drop-down list.\nAlternatively, input scale nominator and denominator values in the adjacent fields.\nFit to paper\nSelect the check box to scale the printed output to the selected page size, by default.\nSpecify paper orientation\nAllows you to define the printed page orientation. Click to display a drop-down list.\nSelect Landscape Orientation to print the sheet as Landscape.\nSelect Landscape Upside Down Orientation to print the sheet as Landscape Upside down. The option can be used for flip book backing sheets.\nSelect Portrait Orientation to print the sheet as Portrait.\nSelect Landscape Upside Down Orientation to print the sheet as Landscape Upside down. The option can be used for flip book backing sheets.\nSelect one of paper sizes available or the current printer\nAllows you to define the printed page size. Click to display a drop-down list, you can select an available page size.\nPage Setup\nAllows you to view and/or select further paper size properties. Click to display the Page Setup window.\nAll of the page setup properties can be updated in the Print Options with the exception of margins. Refer to Print Margins for further information\nClick OK to apply the page setup modifications or Cancel to discard any changes and close the Page Setup window.\nCentre the Print\nSelect the check box to center the printed output on the paper.\nAlternatively, you can de-select the check box and input coordinates in the X and Y fields to define the center point of the printed area.\nScale Line Weight\nSelect the check box to scale line weights on the printed output.\nAuto Preview\nSelect the check box to update the print preview as the print settings are changed, by default.\nShow View Frames\nSelect the check box to include the frames of all View frame owners (for example, Views, Regions and Sheets) in the printed output.\nPreview\nClick to update the print preview.\nPrint/Plot\nClick to print the current sheet.\nWhen Print/Plot is selected, the current print settings are saved.\nMulti Print/Plot\nAllows you to print multiple sheets, Click to display the Open window.\nThe functionality of the Open window is explained, refer to Export Multiple Sheets for further information.\nClick Open to print the selected sheets.\nDuring the print process, a progress bar displays which tracks the progress.\n\nClick Cancel to cancel the print process,\nCopies\nInput the number of copies required in the field.\nSpecify the printer to use\nSelect the printer or plotter from the drop-down list. The default printing device is pre-selected.\nPrint to File\nSelect the check box to print to a file output. For example a .prn file.\nWhen Print/Plot is selected, the Save As window displays.\n\nYou must input a filename and select the required file type. The default filename is the drawing name.\nClick Save to print the file or Cancel to discard any changes and close the Save As window.\nPrinter Properties\nClick to define the printer specific properties for the currently selected printer.\nSpecify plot styles\nAllows you to define the colour, fill and line style settings for the print. Click to display a drop-down list.\n\nSelect Default from the drop-down list, the colour, fill and line style settings are not changed.\nSelect Monochrome from the drop-down list to print all colours as black and white.\nSelect Greyscale from the drop-down list to print all colours as greyscale.\nSelect All Filltypes as Solid from the drop-down list to print all filled objects with a solid fill. For example, all objects with shaded fill properties are printed with a solid fill.\nSelect All Linetypes as Solid from the drop-down list to print all lines with a solid line type. For example, all dashed lines are printed as solid lines.\nAs well as the default plot styles provided with the product, additional plot styles can be created. Refer to Plot Style for further information.\nSpecify the object type to be printed\nAllows you to define the printed area. Click to display a drop-down list.\n\nSelect Sheet from the drop-down list to print the currently selected sheet.\nSelect Display from the drop-down list to print the current display area of a sheet.\nSelect Extents from the drop-down list to print the extents of a sheet.\nSelect Window from the drop-down list to print a defined display area. Click Specify window to define the display area to be printed.\nSpecify window\nClick to define the display area to be printed. The application displays the current sheet.\nYou are prompted to Specify first corner\nClick to identify the first corner of the output area.\nYou are then prompted to Specify opposite corner\nClick to identify the opposite corner of the output area.\nSelect one of the available scale presets\nAllows you to define the printed drawing scale. Click to display a drop-down list.\n\nYou can select a preset scale from the drop-down list.\nAlternatively, input scale nominator and denominator values in the adjacent fields.\nFit to paper\nSelect the check box to scale the printed output to the selected page size, by default.\nSpecify paper orientation\nAllows you to define the printed page orientation. Click to display a drop-down list.\n\nSelect Landscape Orientation to print the sheet as Landscape.\nSelect Landscape Upside Down Orientation to print the sheet as Landscape Upside down. The option can be used for flip book backing sheets.\nSelect Portrait Orientation to print the sheet as Portrait.\nSelect Landscape Upside Down Orientation to print the sheet as Landscape Upside down. The option can be used for flip book backing sheets.\nSelect one of paper sizes available or the current printer\nAllows you to define the printed page size. Click to display a drop-down list, you can select an available page size.\n\nPage Setup\nAllows you to view and/or select further paper size properties. Click to display the Page Setup window.\n\nAll of the page setup properties can be updated in the Print Options with the exception of margins. Refer to Print Margins for further information\nClick OK to apply the page setup modifications or Cancel to discard any changes and close the Page Setup window.\nCentre the Print\nSelect the check box to center the printed output on the paper.\nAlternatively, you can de-select the check box and input coordinates in the X and Y fields to define the center point of the printed area.\nScale Line Weight\nSelect the check box to scale line weights on the printed output.\nAuto Preview\nSelect the check box to update the print preview as the print settings are changed, by default.\nShow View Frames\nSelect the check box to include the frames of all View frame owners (for example, Views, Regions and Sheets) in the printed output.\nPreview\nClick to update the print preview.\n\nPrint/Plot\nClick to print the current sheet.\nWhen Print/Plot is selected, the current print settings are saved.\nMulti Print/Plot\nAllows you to print multiple sheets, Click to display the Open window.\nThe functionality of the Open window is explained, refer to Export Multiple Sheets for further information.\nClick Open to print the selected sheets.\nDuring the print process, a progress bar displays which tracks the progress.\nClick Cancel to cancel the print process,\nCopies\nInput the number of copies required in the field.\nSpecify the printer to use\nSelect the printer or plotter from the drop-down list. The default printing device is pre-selected.\nPrint to File\nSelect the check box to print to a file output. For example a .prn file.\nWhen Print/Plot is selected, the Save As window displays.\nYou must input a filename and select the required file type. The default filename is the drawing name.\nClick Save to print the file or Cancel to discard any changes and close the Save As window.\nPrinter Properties\nClick to define the printer specific properties for the currently selected printer.\nSpecify plot styles\nAllows you to define the colour, fill and line style settings for the print. Click to display a drop-down list.\nSelect Default from the drop-down list, the colour, fill and line style settings are not changed.\nSelect Monochrome from the drop-down list to print all colours as black and white.\nSelect Greyscale from the drop-down list to print all colours as greyscale.\nSelect All Filltypes as Solid from the drop-down list to print all filled objects with a solid fill. For example, all objects with shaded fill properties are printed with a solid fill.\nSelect All Linetypes as Solid from the drop-down list to print all lines with a solid line type. For example, all dashed lines are printed as solid lines.\nAs well as the default plot styles provided with the product, additional plot styles can be created. Refer to Plot Style for further information.\nSpecify the object type to be printed\nAllows you to define the printed area. Click to display a drop-down list.\nSelect Sheet from the drop-down list to print the currently selected sheet.\nSelect Display from the drop-down list to print the current display area of a sheet.\nSelect Extents from the drop-down list to print the extents of a sheet.\nSelect Window from the drop-down list to print a defined display area. Click Specify window to define the display area to be printed.\nSpecify window\nClick to define the display area to be printed. The application displays the current sheet.\nYou are prompted to Specify first corner\nClick to identify the first corner of the output area.\nYou are then prompted to Specify opposite corner\nClick to identify the opposite corner of the output area.\nSelect one of the available scale presets\nAllows you to define the printed drawing scale. Click to display a drop-down list.\nYou can select a preset scale from the drop-down list.\nAlternatively, input scale nominator and denominator values in the adjacent fields.\nFit to paper\nSelect the check box to scale the printed output to the selected page size, by default.\nSpecify paper orientation\nAllows you to define the printed page orientation. Click to display a drop-down list.\nSelect Landscape Orientation to print the sheet as Landscape.\nSelect Landscape Upside Down Orientation to print the sheet as Landscape Upside down. The option can be used for flip book backing sheets.\nSelect Portrait Orientation to print the sheet as Portrait.\nSelect Landscape Upside Down Orientation to print the sheet as Landscape Upside down. The option can be used for flip book backing sheets.\nSelect one of paper sizes available or the current printer\nAllows you to define the printed page size. Click to display a drop-down list, you can select an available page size.\nPage Setup\nAllows you to view and/or select further paper size properties. Click to display the Page Setup window.\nAll of the page setup properties can be updated in the Print Options with the exception of margins. Refer to Print Margins for further information\nClick OK to apply the page setup modifications or Cancel to discard any changes and close the Page Setup window.\nCentre the Print\nSelect the check box to center the printed output on the paper.\nAlternatively, you can de-select the check box and input coordinates in the X and Y fields to define the center point of the printed area.\nScale Line Weight\nSelect the check box to scale line weights on the printed output.\nAuto Preview\nSelect the check box to update the print preview as the print settings are changed, by default.\nShow View Frames\nSelect the check box to include the frames of all View frame owners (for example, Views, Regions and Sheets) in the printed output.\nPreview\nClick to update the print preview.\n\n\n\nExport Multiple Sheets\nPrint Margins\nPrint/Plot\nPrint/Plot\nMulti Print/Plot\nOpen\nOpen\nExport Multiple Sheets\nOpen\nCancel\nCopies\nSpecify the printer to use\nPrint to File\nPrint/Plot\nSave As\nSave\nCancel\nSave As\nPrinter Properties\nSpecify plot styles\nDefault\nMonochrome\nGreyscale\nAll Filltypes as Solid\nAll Linetypes as Solid\nPlot Style\nSpecify the object type to be printed\nSheet\nDisplay\nExtents\nWindow\nSpecify window\nSpecify window\nSpecify first corner\nSpecify opposite corner\nSelect one of the available scale presets\nFit to paper\nSpecify paper orientation\nLandscape Orientation\nLandscape Upside Down Orientation\nPortrait Orientation\nLandscape Upside Down Orientation\nSelect one of paper sizes available or the current printer\nPage Setup\nPage Setup\nPrint Margins\nOK\nCancel\nPage Setup\nCentre the Print\nX\nY\nScale Line Weight\nAuto Preview\nShow View Frames\nPreview"}
{"Headers": "Create and Modify Visual Layers", "Content": "Sets the available Visual Layers for the current Sheet and defines the layer properties.\n\n\n"}
{"Headers": "Active Visual Styles", "Content": "When labels, text, dimensions, rulers, baselines, center lines, view frames and connectors are added to a drawing they are assigned a default visual style which controls their appearance.\nA user-defined visual style can be set as the default visual style for labels, text, dimensions, rulers, baselines, center lines, view frames and connectors. The creation and modification of visual styles is an administrative task, refer to Visual Styles for further information.\n\n\n\nVisual Styles"}
{"Headers": "Create Drawing Sheets and Support Elements", "Content": "You can create a drawing sheet belonging to a new branch of the hierarchy. Functionality is also available to quickly create a Drawing Sheet from a standard template with a single click.\nAn administrative element can be created only at one level lower than an existing element, which then owns it. Consequently, to create a drawing in a new branch of the hierarchy, the upper elements of that branch, firstly a Department and then a Registry, must be created before the Drawing and its Sheet are created.\nVarious element types are used to support and augment standard drawing sheets. For example, backing sheets, overlays, symbols, representation styles and hatching styles.\n\n\n\nDepartment\nRegistry\nDrawing\nSheet"}
{"Headers": "Create Departments, Registries and Drawings", "Content": "Departments, Registries and Drawings can be created in a number of different ways.\n\n\n"}
{"Headers": "Create Departments, Registries and Drawings with the Hierarchy Browser Window or Open Window", "Content": "Creates a department, registry or drawing using the Hierarchy Browser or Open window.\nThe functionality to create a department, registry or drawing with the Open window is identical to Hierarchy Browser window.\n\nTo create a department (DEPT) element, on the left-hand part of the Hierarchy Browser window, right-click the Project element and select New > New Department from the drop-down list.\nAlternatively, on the right-hand part of the Hierarchy Browser window, select an existing DEPT element, right click and select New > New Department from the drop-down list.\nThe DEPT element is created and displays in the Hierarchy Browser window. You can then input a name for the department.\n\nTo create a registry (REGI) element, on the left-hand part of the Hierarchy Browser window, right-click the DEPT element that the REGI element is to be created in and select New > New Registry from the drop-down list.\nAlternatively, on the right-hand part of the Hierarchy Browser window, select an existing REGI element, right click and select New > New Registry from the drop-down list.\nThe REGI element is created and displays in the Hierarchy Browser window. You can then input a name for the registry.\n\nTo create a drawing (DRWG) element, on the left-hand part of the Hierarchy Browser window, right-click the REGI element that the DRWG element is to be created in and select New > New Drawing from the drop-down list.\nAlternatively, on the right-hand part of the Hierarchy Browser window, select an existing DRWG element, right-click and select New > New Drawing from the drop-down list.\nThe DRWG element is created and displays in the Hierarchy Browser window. You can then input a name for the drawing.\n\nAdditional functionality to create a new department, registry or drawing in the Hierarchy Browser window or Open window is also available.\nSelect the element that the department, registry or drawing is to be created in and click New. You must then select the required element type. For example:\n\nThe department, registry or drawing element is created and displays in the Hierarchy Browser window.\n\nYou can rename the currently selected element at any time. Right-click and select Rename from the drop-down list and input the new name.\nFor further information on the facilities provided by the Hierarchy Browser window and the Open window, refer to Open Sheet.\n\n\n\nOpen Sheet\nHierarchy Browser\nOpen\nOpen\nHierarchy Browser\nHierarchy Browser\nProject\nNew > New Department\nHierarchy Browser\nHierarchy Browser\nHierarchy Browser\nNew > New Registry\nHierarchy Browser\nNew > New Registry\nHierarchy Browser\nHierarchy Browser\nNew > New Drawing\nHierarchy Browser\nHierarchy Browser\nHierarchy Browser\nOpen\nNew\nHierarchy Browser\nRename\nHierarchy Browser\nOpen\nOpen Sheet"}
{"Headers": "Create and Modify Departments", "Content": "Creates a department and sets the department attributes.\nRefer to Modify Department Attributes for further information.\n\n\n\nModify Department Attributes\nModify Department Attributes"}
{"Headers": "Create and Modify Registries", "Content": "Creates a registry and sets the registry attributes.\nRefer to Modify Registry Attributes for further in formation.\n\n\n\nModify Registry Attributes\nModify Registry Attributes"}
{"Headers": "Create and Modify Drawings", "Content": "Creates a drawing and sets the drawing attributes.\nRefer to Modify Drawing Attributes for further information.\n\n\n\nModify Drawing Attributes\nModify Drawing Attributes"}
{"Headers": "Create Drawing from Drawing Type and Template", "Content": "Creates a drawing from a selected drawing type and template.\n\nSelect Drawing from the available Drawing Types.\nSelect a Template Type from the drop-down list to filter the available Templates. The appearance of the templates is pre-defined by the administrator allowing for the production of company standard drawings.\nIndividual templates are defined for the various drawing types.\nTT/DRA/PRJ/TMP/ADP-PGA\nSelect from the drop-down list to create a drawing using the ADP drawing template.\nTT/DRA/PRJ/TMP/CLASH\nSelect from the drop-down list to create a drawing using the Clash drawing template.\nTT/DRA/PRJ/TMP/ELEC\nSelect from the drop-down list to create a drawing using the pre-defined Electrical drawing template.\nTT/DRA/PRJ/TMP/EQUI\nSelect from the drop-down list to create a drawing using the Equipment drawing template.\nTT/DRA/PRJ/TMP/HVAC\nSelect from the drop-down list to create a drawing using the HVAC drawing template.\nTT/DRA/PRJ/TMP/HvacSketch\nSelect from the drop-down list to create a drawing using the HVAC Sketch drawing template.\nTT/DRA/PRJ/TMP/PIPING\nSelect from the drop-down list to create a drawing using the Piping drawing template.\nTT/DRA/PRJ/TMP/PipeFabrication\nSelect from the drop-down list to create a drawing using the Pipe Fabrication drawing template.\nTT/DRA/PRJ/TMP/PipeSketch\nSelect from the drop-down list to create a drawing using the Pipe Sketch drawing template.\nTT/DRA/PRJ/TMP/STRUCTURAL\nSelect from the drop-down list to create a drawing using the Structural drawing template.\nTT/DRA/PRJ/TMP/Marine\nAvailable for use with Marine projects only. Select from the drop-down list to create a drawing using the Marine drawing template.\nTT/DRA/PRJ/TMP/ADP-PGA\nSelect from the drop-down list to create a drawing using the ADP drawing template.\nTT/DRA/PRJ/TMP/CLASH\nSelect from the drop-down list to create a drawing using the Clash drawing template.\nTT/DRA/PRJ/TMP/ELEC\nSelect from the drop-down list to create a drawing using the pre-defined Electrical drawing template.\nTT/DRA/PRJ/TMP/EQUI\nSelect from the drop-down list to create a drawing using the Equipment drawing template.\nTT/DRA/PRJ/TMP/HVAC\nSelect from the drop-down list to create a drawing using the HVAC drawing template.\nTT/DRA/PRJ/TMP/HvacSketch\nSelect from the drop-down list to create a drawing using the HVAC Sketch drawing template.\nTT/DRA/PRJ/TMP/PIPING\nSelect from the drop-down list to create a drawing using the Piping drawing template.\nTT/DRA/PRJ/TMP/PipeFabrication\nSelect from the drop-down list to create a drawing using the Pipe Fabrication drawing template.\nTT/DRA/PRJ/TMP/PipeSketch\nSelect from the drop-down list to create a drawing using the Pipe Sketch drawing template.\nTT/DRA/PRJ/TMP/STRUCTURAL\nSelect from the drop-down list to create a drawing using the Structural drawing template.\nTT/DRA/PRJ/TMP/Marine\nAvailable for use with Marine projects only. Select from the drop-down list to create a drawing using the Marine drawing template.\nClick Create to display the Create Drawing window.\n\nThe Create Drawing window is very similar to the Hierarchy Browser window. Refer to Create Departments, Registries and Drawings with the Hierarchy Browser Window or Open Window.\nYou can browse the hierarchy to select the registry that the drawing is to be created in. Either input a name in the Name field, or leave it blank if the drawing is to be assigned a default name.\nClick Create to create the drawing or Cancel to discard any inputs and close the Create Drawing window.\nA drawing is created together with sheet and library elements.\n\nTT/DRA/PRJ/TMP/ADP-PGA\nSelect from the drop-down list to create a drawing using the ADP drawing template.\nTT/DRA/PRJ/TMP/CLASH\nSelect from the drop-down list to create a drawing using the Clash drawing template.\nTT/DRA/PRJ/TMP/ELEC\nSelect from the drop-down list to create a drawing using the pre-defined Electrical drawing template.\nTT/DRA/PRJ/TMP/EQUI\nSelect from the drop-down list to create a drawing using the Equipment drawing template.\nTT/DRA/PRJ/TMP/HVAC\nSelect from the drop-down list to create a drawing using the HVAC drawing template.\nTT/DRA/PRJ/TMP/HvacSketch\nSelect from the drop-down list to create a drawing using the HVAC Sketch drawing template.\nTT/DRA/PRJ/TMP/PIPING\nSelect from the drop-down list to create a drawing using the Piping drawing template.\nTT/DRA/PRJ/TMP/PipeFabrication\nSelect from the drop-down list to create a drawing using the Pipe Fabrication drawing template.\nTT/DRA/PRJ/TMP/PipeSketch\nSelect from the drop-down list to create a drawing using the Pipe Sketch drawing template.\nTT/DRA/PRJ/TMP/STRUCTURAL\nSelect from the drop-down list to create a drawing using the Structural drawing template.\nTT/DRA/PRJ/TMP/Marine\nAvailable for use with Marine projects only. Select from the drop-down list to create a drawing using the Marine drawing template.\n\n\n\nCreate Departments, Registries and Drawings with the Hierarchy Browser Window or Open Window\nDrawing\nTemplate Type\nTT/DRA/PRJ/TMP/ADP-PGA\nTT/DRA/PRJ/TMP/CLASH\nTT/DRA/PRJ/TMP/ELEC\nTT/DRA/PRJ/TMP/EQUI\nTT/DRA/PRJ/TMP/HVAC\nTT/DRA/PRJ/TMP/HvacSketch\nTT/DRA/PRJ/TMP/PIPING\nTT/DRA/PRJ/TMP/PipeFabrication\nTT/DRA/PRJ/TMP/PipeSketch\nTT/DRA/PRJ/TMP/STRUCTURAL\nTT/DRA/PRJ/TMP/Marine\nCreate\nCreate Drawing\nCreate Drawing\nCreate Departments, Registries and Drawings with the Hierarchy Browser Window or Open Window\nName\nCreate\nCancel\nCreate Drawing"}
{"Headers": "Modify Department Attributes", "Content": "Sets the attributes for the currently selected department.\n\nThe Department Attributes window allows you to specify a number of attribute settings for the department.\nThe department name displays at the top of the Department Attributes window.\n\n\n\nDepartment Attributes\nDepartment Attributes"}
{"Headers": "Size and Units", "Content": "The Size and Units tab on the Department Attributes window allows you to select the units for the department and set the precision.\n\nWidth\nInput a dimensional value in the field to define the department page width.\nAlternatively, you can select a standard page size from the drop-down list. The Width field is then populated, by default.\nHeight\nInput a dimensional value in the field to define the department page height.\nAlternatively, you can select a standard page size from the drop-down list. The Height field is then populated, by default.\nBacking Sheet\nAllows you to define a backing sheet for the department.\nSelect the Unset option button to define the backing sheet as Unset.\nSelect the Reference option button to reference a pre-defined backing sheet. You must select a reference backing sheet from the drop-down list.\nSelect the Filename option button to reference a backing sheet from a filename. You must input a filename in the field.\nDistance\nSelect from the drop-down list to define the unit of measure for distance.\nBore\nSelect from the drop-down list to define the unit of measure for bore.\nPrecision\nAllows you to specify the precision to which values are expressed.\nInput a value in the Metric field to define the precision for the metric values in decimal places.\nInput a value in the Imperial field to define the precision for the imperial values in decimal places.\nInput a value in the Fractions field to define the precision for imperial fractional values.\nSelect from the Angles drop-down list to define the way in which angles are stored and input a value in the field. Angles are stored decimally, to the nearest whole number of degrees, to the nearest minute, or to the nearest second.\nWidth\nInput a dimensional value in the field to define the department page width.\nAlternatively, you can select a standard page size from the drop-down list. The Width field is then populated, by default.\nHeight\nInput a dimensional value in the field to define the department page height.\nAlternatively, you can select a standard page size from the drop-down list. The Height field is then populated, by default.\nBacking Sheet\nAllows you to define a backing sheet for the department.\nSelect the Unset option button to define the backing sheet as Unset.\nSelect the Reference option button to reference a pre-defined backing sheet. You must select a reference backing sheet from the drop-down list.\nSelect the Filename option button to reference a backing sheet from a filename. You must input a filename in the field.\nDistance\nSelect from the drop-down list to define the unit of measure for distance.\nBore\nSelect from the drop-down list to define the unit of measure for bore.\nPrecision\nAllows you to specify the precision to which values are expressed.\nInput a value in the Metric field to define the precision for the metric values in decimal places.\nInput a value in the Imperial field to define the precision for the imperial values in decimal places.\nInput a value in the Fractions field to define the precision for imperial fractional values.\nSelect from the Angles drop-down list to define the way in which angles are stored and input a value in the field. Angles are stored decimally, to the nearest whole number of degrees, to the nearest minute, or to the nearest second.\n\nWidth\nInput a dimensional value in the field to define the department page width.\nAlternatively, you can select a standard page size from the drop-down list. The Width field is then populated, by default.\nHeight\nInput a dimensional value in the field to define the department page height.\nAlternatively, you can select a standard page size from the drop-down list. The Height field is then populated, by default.\nBacking Sheet\nAllows you to define a backing sheet for the department.\nSelect the Unset option button to define the backing sheet as Unset.\nSelect the Reference option button to reference a pre-defined backing sheet. You must select a reference backing sheet from the drop-down list.\nSelect the Filename option button to reference a backing sheet from a filename. You must input a filename in the field.\nDistance\nSelect from the drop-down list to define the unit of measure for distance.\nBore\nSelect from the drop-down list to define the unit of measure for bore.\nPrecision\nAllows you to specify the precision to which values are expressed.\nInput a value in the Metric field to define the precision for the metric values in decimal places.\nInput a value in the Imperial field to define the precision for the imperial values in decimal places.\nInput a value in the Fractions field to define the precision for imperial fractional values.\nSelect from the Angles drop-down list to define the way in which angles are stored and input a value in the field. Angles are stored decimally, to the nearest whole number of degrees, to the nearest minute, or to the nearest second.\n\n\n\nSize and Units\nDepartment Attributes\nWidth\nWidth\nHeight\nHeight\nBacking Sheet\nUnset\nReference\nFilename\nDistance\nBore\nPrecision\nMetric\nImperial\nFractions\nAngles"}
{"Headers": "Intelligent Text", "Content": "The Intelligent Text tab on the Department Attributes window allows you to select an output format for the positional code words used to request the position of certain elements.\nThese expand to a string providing the location expressed in either the ENU (East North Up) coordinate system, as an absolute position (XYZ), or as a purely numerical output (Numbers only).\n\n\n\n\nIntelligent Text\nDepartment Attributes"}
{"Headers": "Pens", "Content": "The Pens tab on the Department Attributes window allows you to define the line colour, line style, text and hatch pattern.\n\nColour\nSelect from the drop-down list to define the representation colour for lines and text.\nAlternatively, click Pick to display the Pick a colour window.\nThe Pick a colour window allows you to define the text, line or hatch pattern colour.\nSelect a colour from the palette, the colour is indicated at the bottom of the Pick a colour window.\nClick More to display a large colour palette. When the large colour palette displays, you can click Less to display a small colour palette.\nClick Reset to revert to the colour selected when the Pick a colour window was opened.\nClose the window to apply the selected colour or click Cancel to discard any changes and close the Pick a colour window.\nFont\nSelect from the drop-down list to define the font.\nStyle\nSelect from the drop-down lists to define the line style and thickness for each line type.\nAlternatively, click Select to display the User-defined linear styles window. Refer to User-Defined Linear Styles for further information. If a user-defined linear style is selected, the check box and field are populated, by default.\nSelect from the drop-down list to define the hatch pattern.\nAlternatively, click Select to display the User-defined fill styles window. The functionality of the User-defined fill styles window is identical to the User-defined linear styles window. Refer to User-Defined Linear Styles for further information. If a user-defined fill style is selected, the check box and field are populated, by default.\nColour\nSelect from the drop-down list to define the representation colour for lines and text.\nAlternatively, click Pick to display the Pick a colour window.\n\nThe Pick a colour window allows you to define the text, line or hatch pattern colour.\nSelect a colour from the palette, the colour is indicated at the bottom of the Pick a colour window.\nClick More to display a large colour palette. When the large colour palette displays, you can click Less to display a small colour palette.\nClick Reset to revert to the colour selected when the Pick a colour window was opened.\nClose the window to apply the selected colour or click Cancel to discard any changes and close the Pick a colour window.\nFont\nSelect from the drop-down list to define the font.\nStyle\nSelect from the drop-down lists to define the line style and thickness for each line type.\nAlternatively, click Select to display the User-defined linear styles window. Refer to User-Defined Linear Styles for further information. If a user-defined linear style is selected, the check box and field are populated, by default.\nSelect from the drop-down list to define the hatch pattern.\nAlternatively, click Select to display the User-defined fill styles window. The functionality of the User-defined fill styles window is identical to the User-defined linear styles window. Refer to User-Defined Linear Styles for further information. If a user-defined fill style is selected, the check box and field are populated, by default.\n\nColour\nSelect from the drop-down list to define the representation colour for lines and text.\nAlternatively, click Pick to display the Pick a colour window.\nThe Pick a colour window allows you to define the text, line or hatch pattern colour.\nSelect a colour from the palette, the colour is indicated at the bottom of the Pick a colour window.\nClick More to display a large colour palette. When the large colour palette displays, you can click Less to display a small colour palette.\nClick Reset to revert to the colour selected when the Pick a colour window was opened.\nClose the window to apply the selected colour or click Cancel to discard any changes and close the Pick a colour window.\nFont\nSelect from the drop-down list to define the font.\nStyle\nSelect from the drop-down lists to define the line style and thickness for each line type.\nAlternatively, click Select to display the User-defined linear styles window. Refer to User-Defined Linear Styles for further information. If a user-defined linear style is selected, the check box and field are populated, by default.\nSelect from the drop-down list to define the hatch pattern.\nAlternatively, click Select to display the User-defined fill styles window. The functionality of the User-defined fill styles window is identical to the User-defined linear styles window. Refer to User-Defined Linear Styles for further information. If a user-defined fill style is selected, the check box and field are populated, by default.\n\n\n\nUser-Defined Linear Styles\nUser-Defined Linear Styles\nPens\nDepartment Attributes\nColour\nPick\nPick a colour\nPick a colour\nPick a colour\nMore\nLess\nReset\nPick a colour\nCancel\nPick a colour\nFont\nStyle\nSelect\nUser-defined linear styles\nUser-Defined Linear Styles\nSelect\nUser-defined fill styles\nUser-defined fill styles\nUser-defined linear styles\nUser-Defined Linear Styles"}
{"Headers": "User-Defined Linear Styles", "Content": "Applies a user-defined linear style to a department.\n\nThe User-defined linear styles window allows you to select a user-defined line style from a list of available Style Tables and a list of available Styles.\nThe left-hand part of the User-defined linear styles window displays a list of available Style Tables. Select a row to change the display of the List of available Styles.\nThe right-hand part of the User-defined linear styles window displays a list of available styles. Select a row to be used as the line style.\nClick to scroll to the left side of the currently selected list.\nClick to scroll to the left of the currently selected list.\nClick to scroll to the right of the currently selected list.\nClick to scroll to the right side of the currently selected list.\nClick to scroll to the top of the currently selected list.\nClick to scroll up the currently selected list.\nClick to scroll down the currently selected list.\nClick to scroll to the bottom of the currently selected list.\n\nClick to scroll to the left side of the currently selected list.\n\nClick to scroll to the left of the currently selected list.\n\nClick to scroll to the right of the currently selected list.\n\nClick to scroll to the right side of the currently selected list.\n\nClick to scroll to the top of the currently selected list.\n\nClick to scroll up the currently selected list.\n\nClick to scroll down the currently selected list.\n\nClick to scroll to the bottom of the currently selected list.\nClick Select to apply the user-defined line style or Cancel to discard any changes and close the User-defined linear styles window.\nClick to scroll to the left side of the currently selected list.\nClick to scroll to the left of the currently selected list.\nClick to scroll to the right of the currently selected list.\nClick to scroll to the right side of the currently selected list.\nClick to scroll to the top of the currently selected list.\nClick to scroll up the currently selected list.\nClick to scroll down the currently selected list.\nClick to scroll to the bottom of the currently selected list.\n\n\n\nUser-defined linear styles\nUser-defined linear styles\nUser-defined linear styles\nSelect\nCancel\nUser-defined linear styles"}
{"Headers": "Miscellaneous", "Content": "The Miscellaneous tab on the Department Attributes window allows you to define a number of department attributes.\n\nNull Text\nWhen it is not possible to extract data from an attribute, the intelligent text system returns an error and (by default) substitutes the text \u2018---\u2019 for the missing data. The NTEXT attribute allows you to substitute their own \u2018null text\u2019.\nFor example:\nNTEXT \u2019No data\u2019\nDate Format\nAllows you to set the date format by selecting an option from the drop-down list.\nDimension Terminator\nAllows you to define the dimension terminator by selecting an option from the drop-down list.\nLeader Terminator\nAllows you to define the leader terminator by selecting an option from the drop-down list.\nRuleset Reference\nAllows you to select a default rule set reference from the drop-down list.\nHatching Ruleset Reference\nAllows you to select a default hatching rule set reference from the drop-down list.\nNull Text\nWhen it is not possible to extract data from an attribute, the intelligent text system returns an error and (by default) substitutes the text \u2018---\u2019 for the missing data. The NTEXT attribute allows you to substitute their own \u2018null text\u2019.\nFor example:\nDate Format\nAllows you to set the date format by selecting an option from the drop-down list.\nDimension Terminator\nAllows you to define the dimension terminator by selecting an option from the drop-down list.\nLeader Terminator\nAllows you to define the leader terminator by selecting an option from the drop-down list.\nRuleset Reference\nAllows you to select a default rule set reference from the drop-down list.\nHatching Ruleset Reference\nAllows you to select a default hatching rule set reference from the drop-down list.\nClick Reset to revert to the values applied when the Department Attributes window was opened.\nClick Apply to modify the department attributes or Cancel to discard any changes and close the Department Attributes window.\nNull Text\nWhen it is not possible to extract data from an attribute, the intelligent text system returns an error and (by default) substitutes the text \u2018---\u2019 for the missing data. The NTEXT attribute allows you to substitute their own \u2018null text\u2019.\nFor example:\nNTEXT \u2019No data\u2019\nDate Format\nAllows you to set the date format by selecting an option from the drop-down list.\nDimension Terminator\nAllows you to define the dimension terminator by selecting an option from the drop-down list.\nLeader Terminator\nAllows you to define the leader terminator by selecting an option from the drop-down list.\nRuleset Reference\nAllows you to select a default rule set reference from the drop-down list.\nHatching Ruleset Reference\nAllows you to select a default hatching rule set reference from the drop-down list.\n\n\n\nMiscellaneous\nDepartment Attributes\nNull Text\nDate Format\nDimension Terminator\nLeader Terminator\nRuleset Reference\nHatching Ruleset Reference\nReset\nDepartment Attributes\nApply\nCancel\nDepartment Attributes"}
{"Headers": "Modify Registry Attributes", "Content": "Sets the attributes for the currently selected registry.\n\nThe Registry Attributes window allows you to specify a number of attribute settings for the registry. The functionality of the Registry Attributes window is identical to the Department Attributes window. Refer to Modify Department Attributes for further information.\n\n\n\nModify Department Attributes\nRegistry Attributes\nRegistry Attributes\nDepartment Attributes\nModify Department Attributes"}
{"Headers": "Modify Drawing Attributes", "Content": "Sets the attributes for the currently selected drawing.\n\nThe Drawing Attributes window allows you to specify a number of attribute settings for the drawing. The functionality of the Drawing Attributes window is identical to the Department Attributes window. Refer to Modify Department Attributes for further information.\n\n\n\nModify Department Attributes\nDrawing Attributes\nDrawing Attributes\nDepartment Attributes\nModify Department Attributes"}
{"Headers": "Create Drawing Sheets", "Content": "Drawing sheets can be created in a number of different ways.\n\n\n"}
{"Headers": "Create Drawing Sheet from Hierarchy Browser or Open Window", "Content": "Creates a drawing sheet using the Hierarchy Browser or Open window.\nThe functionality to create a drawing sheet with the Open window is identical to Hierarchy Browser window.\n\nTo create a drawing sheet (SHEE) element, on the left-hand part of the Hierarchy Browser window, right-click the DRWG element that the SHEE element is to be created in and select New > New Sheet from the drop-down list.\nAlternatively, in the right-hand part of the Hierarchy Browser window, select an existing SHEE element, right-click and select New > New Sheet from the drop-down list.\nThe SHEE element is created and displays in the Hierarchy Browser window. You can then input a name for the sheet.\n\nAdditional functionality to create a new sheet in the Hierarchy Browser window or Open window is also available.\nSelect the DRWG element that the SHEE element is to be created in and click New. You must then select New Sheet from the drop-down list.\n\nThe SHEE element is created and displays in the Hierarchy Browser window. The sheet is assigned a default name of the drawing name followed by /S and the next available number.\nCertain attributes of a drawing, for example, its size and backing sheet (if set), are inherited as the default attributes of sheets created for that drawing. These can be changed if required, for example by using the Properties. In turn, attributes set for a sheet are inherited as the default attributes of the views of that sheet.\nYou can rename the currently selected element at any time. Right-click and select Rename from the drop-down list and input the new name.\nFor further information on the facilities provided by the Hierarchy Browser window and the Open window, refer to Open Sheet.\n\n\n\nProperties\nOpen Sheet\nHierarchy Browser\nOpen\nOpen\nHierarchy Browser\nHierarchy Browser\nNew > New Sheet\nHierarchy Browser\nNew > New Sheet\nHierarchy Browser\nHierarchy Browser\nOpen\nNew\nNew Sheet\nHierarchy Browser\n/S\nProperties\nHierarchy Browser\nOpen\nOpen Sheet"}
{"Headers": "Create Drawing Sheet from a Drawing Type and Template", "Content": "Creates a drawing sheet from a selected drawing type and template.\n\nSelect Sheet from the available Drawing Types.\nSelect the required Template and click Create to display the Create Sheet window.\n\nThe Create Sheet window is very similar to the Hierarchy Browser window. Refer to Create Drawing Sheet from Hierarchy Browser or Open Window for further information.\nYou can browse the hierarchy to select the drawing that the sheet is to be created in. Either input a name in the Name field, or leave it blank if the sheet is to be assigned a default name.\nClick Create to create the sheet or Cancel to discard any inputs and close the Create Sheet window\nThe sheet element is created and assigned a default name of the drawing name followed by /S and the next available number.\nCertain attributes of a drawing, for example, its size and backing sheet (if set), are inherited as the default attributes of sheets created for that drawing. These can be changed if required, for example, with the Properties window. In turn, attributes set for a sheet are inherited as the default attributes of the views of that sheet.\n\n\n\n\nCreate Drawing Sheet from Hierarchy Browser or Open Window\nProperties\nSheet\nCreate\nCreate Sheet\nCreate Sheet\nHierarchy Browser\nCreate Drawing Sheet from Hierarchy Browser or Open Window\nName\nCreate\nCancel\nCreate Sheet\n/S\nProperties"}
{"Headers": "Create Drawing Sheet from Quick Sheet Option", "Content": "Creates a sheet using the least amount of steps.\nThe drawing element that the sheet is to be created in must be selected on the Draw Explorer prior to registry creation.\nThe new sheet is assigned a default name consisting of the drawing name followed by /S and a number.\nNote:\nCertain attributes of a drawing, for example, its size and backing sheet (if set), are inherited as the default attributes of sheets created for that drawing. These can be changed if required, for example, with the Properties window. In turn, attributes set for a sheet are inherited as the default attributes of the views of that sheet.\n\n\n\nProperties\n/S\nNote\n:\nProperties"}
{"Headers": "Create Backing Sheets, Overlays, Symbol Templates, Isodraft Symbol Templates and Sheet Templates", "Content": "Creates additional elements to construct and augment a drawing sheet. For example, backing sheets, overlays and symbol templates.\n\nThe creation of symbol templates is an administrator task, refer to Create Symbol Template for further information.\nThe creation of Isodraft templates is an administrator task, refer to Create Isodraft Symbol Template for further information.\nSelect the required drawing type, for example, Backing Sheet, Overlay Sheet, Symbol Template, Isodraft Sheet Template, or Sheet Template (Supports).\nIf Backing Sheet or Overlay Sheet is selected, you must select a Template Type from the drop-down list to filter the available Templates.\nWhen the required drawing type and (where applicable) the template is selected, click Create to display a Create window. For example, Create Overlay Sheet.\n\nThe Create windows are very similar to the Hierarchy Browser window. Refer to Create Drawing Sheet from Hierarchy Browser or Open Window for further information.\nYou can browse the hierarchy to select the library element that the new element is to be created under (refer to Database Hierarchy for further information).\nEither input a name in the Name field, or leave it blank if the element is to be assigned a default name.\nClick Create to create the new element. A new element is created and opened.\nUse the drawing and annotation facilities (refer to Add and Modify Drawing Objects and Add Annotation for further information) to create, for example, the required symbol or backing sheet borders.\nThe new element can then be added to drawing sheets:\nBacking sheets can be assigned to a sheet automatically when created, either inherited from the owning drawing or taken from a selected template. It can subsequently be changed if required, for example, with the Properties window.\nTo add symbols to a drawing, refer to Add Symbols to Drawings for further information.\nTo add an overlay to a drawing, refer to Add Overlays to Drawings for further information.\nBacking sheets can be assigned to a sheet automatically when created, either inherited from the owning drawing or taken from a selected template. It can subsequently be changed if required, for example, with the Properties window.\nBacking sheets can be assigned to a sheet automatically when created, either inherited from the owning drawing or taken from a selected template. It can subsequently be changed if required, for example, with the Properties window.\nTo add symbols to a drawing, refer to Add Symbols to Drawings for further information.\nTo add symbols to a drawing, refer to Add Symbols to Drawings for further information.\nTo add an overlay to a drawing, refer to Add Overlays to Drawings for further information.\nTo add an overlay to a drawing, refer to Add Overlays to Drawings for further information.\nNote:\nIsodraft symbol templates can also be imported.\nNote:\nMany attributes of the new elements (for example, sheet dimensions) are inherited from the library element they are created under. Refer to Standard Model Library Manager for further information.\n\n\n\nCreate Symbol Template\nCreate Isodraft Symbol Template\nCreate Drawing Sheet from Hierarchy Browser or Open Window\nDatabase Hierarchy\nStandard Model Library Manager\nAdd and Modify Drawing Objects\nAdd Annotation\nProperties\nAdd Symbols to Drawings\nAdd Overlays to Drawings\nCreate Symbol Template\nCreate Isodraft Symbol Template\nNote\n:\nBacking Sheet\nOverlay Sheet\nTemplate Type\nCreate\nCreate\nCreate Overlay Sheet\nCreate\nHierarchy Browser\nCreate Drawing Sheet from Hierarchy Browser or Open Window\nDatabase Hierarchy\nName\nCreate\nNote\n:\nStandard Model Library Manager\nAdd and Modify Drawing Objects\nAdd Annotation\nProperties\nAdd Symbols to Drawings\nAdd Overlays to Drawings"}
{"Headers": "Create Sheet or Template from Imported CAD File", "Content": "Creates a drawing sheet or template from an imported CAD (.dwg or .dxf) file.\nYou must browse for and select the required CAD file, then click Open to display the Import Dxf/Dwg file(s) window.\n\nThe General Settings tab on the Import Dxf/Dwg file(s) window allows you to define the general settings and scale for the imported CAD Drawing.\nDrawing name\nA default name is generated automatically based on the name of the original file. Input a value to modify the name of the imported CAD drawing. The imported drawing is saved in the database with the given name.\nIf multiple files are selected for import, the field becomes inactive and all filenames are generated automatically based on the name of the original file.\nImport as\nSelect from the drop-down list to define the element to be used as the basis for the import.\nThe available options are:\nBacking sheet\nISO symbol template\nOverlay\nSheet\nSheet template\nSymbol template\nImport empty blocks\nSelect the check box to import empty blocks (blocks without elements).\nDe-select the check box to omit all empty blocks from the import.\nImport attributes definitions as text\nSelect the check box to import attribute definitions as TEXP elements.\nAutomatic size\nSelect the check box to import the drawing using an automatically calculated size.\nDe-select the check box to import the drawing using a selected picture size or a custom size.\nCustom size\nSelect the check box to enable the X and Y fields.\nInput values in the fields to explicitly define the picture size of the imported CAD drawing, on the X axis and Y axis.\nOpen after import\nSelect the check box to open the file once the import has completed.\nDrawing name\nA default name is generated automatically based on the name of the original file. Input a value to modify the name of the imported CAD drawing. The imported drawing is saved in the database with the given name.\nIf multiple files are selected for import, the field becomes inactive and all filenames are generated automatically based on the name of the original file.\nImport as\nSelect from the drop-down list to define the element to be used as the basis for the import.\nThe available options are:\nImport empty blocks\nSelect the check box to import empty blocks (blocks without elements).\nDe-select the check box to omit all empty blocks from the import.\nImport attributes definitions as text\nSelect the check box to import attribute definitions as TEXP elements.\nAutomatic size\nSelect the check box to import the drawing using an automatically calculated size.\nDe-select the check box to import the drawing using a selected picture size or a custom size.\nCustom size\nSelect the check box to enable the X and Y fields.\nInput values in the fields to explicitly define the picture size of the imported CAD drawing, on the X axis and Y axis.\nOpen after import\nSelect the check box to open the file once the import has completed.\nThe Fill Types Mapping tab on the Import Dxf/Dwg file(s) window displays a list of all fill types used in the imported CAD drawings and the mapped AVEVA fill types based on general mapping settings. Refer to Mapping Settings for further information.\n\nTo modify a fill type mapping, select a row on the list and select a mapped fill type from the drop-down list.\nIf a fill type is not mapped in the general mapping settings, the mapped fill type is set to Off.\nThe Line Types Mapping tab on the Import Dxf/Dwg file(s) window displays a list of all line types used in the imported CAD drawings and the mapped AVEVA line types based on general mapping settings. Refer to Mapping Settings for further information.\n\nTo modify a line type mapping, select a row on the list and select a mapped line type from the drop-down list.\nIf a line type is not mapped in the general mapping settings, the mapped line type is set to ByLayer.\nClick OK to apply the general settings and mappings, the Hierarchy Browser window displays. Click Cancel to discard any changes and close the Import Dxf/Dwg file(s) window.\n\nSelect the owning element for the imported CAD Drawing from the hierarchy.\nClick OK to import the drawing or Cancel to discard any changes and close the Hierarchy Browser window. A progress window displays while the import takes place.\n\nClick Abort to cancel the import.\nA new sheet is added to the drawing. For example:\n\nDrawing name\nA default name is generated automatically based on the name of the original file. Input a value to modify the name of the imported CAD drawing. The imported drawing is saved in the database with the given name.\nIf multiple files are selected for import, the field becomes inactive and all filenames are generated automatically based on the name of the original file.\nImport as\nSelect from the drop-down list to define the element to be used as the basis for the import.\nThe available options are:\nBacking sheet\nISO symbol template\nOverlay\nSheet\nSheet template\nSymbol template\nImport empty blocks\nSelect the check box to import empty blocks (blocks without elements).\nDe-select the check box to omit all empty blocks from the import.\nImport attributes definitions as text\nSelect the check box to import attribute definitions as TEXP elements.\nAutomatic size\nSelect the check box to import the drawing using an automatically calculated size.\nDe-select the check box to import the drawing using a selected picture size or a custom size.\nCustom size\nSelect the check box to enable the X and Y fields.\nInput values in the fields to explicitly define the picture size of the imported CAD drawing, on the X axis and Y axis.\nOpen after import\nSelect the check box to open the file once the import has completed.\nBacking sheet\nISO symbol template\nOverlay\nSheet\nSheet template\nSymbol template\nBacking sheet\nBacking sheet\nISO symbol template\nISO symbol template\nOverlay\nOverlay\nSheet\nSheet\nSheet template\nSheet template\nSymbol template\nSymbol template\nNote:\nIt is the responsibility of the user to make sure that imported files do not contain malicious code. AVEVA recommends never to import files that are not from a trusted source. AVEVA does not recommend importing files that are excessively large, in rare cases this can cause the application to crash due to the process going above the 32-bit process limit.\n\n\n\nMapping Settings\nMapping Settings\nNote\n:\nOpen\nImport Dxf/Dwg file(s)\nGeneral Settings\nImport Dxf/Dwg file(s)\nDrawing name\nImport as\nImport empty blocks\nImport attributes definitions as text\nAutomatic size\nCustom size\nOpen after import\nFill Types Mapping\nImport Dxf/Dwg file(s)\nMapping Settings\nOff\nLine Types Mapping\nImport Dxf/Dwg file(s)\nMapping Settings\nByLayer\nOK\nCancel\nImport Dxf/Dwg file(s)\nOK\nCancel\nHierarchy Browser\nAbort"}
{"Headers": "Mapping Settings", "Content": "Creates fill type and line type mappings for imported CAD (.dwg or .dxf) files.\n\nThe existing user-defined mappings display in the Available Maps list.\nThe Map Actions display underneath the list. To modify a mapping, select a row, input the name of the original document fill/line type and select a mapped fill/line type from the drop-down list.\nCreate a new mapping\nDisplays the Add New Map window.\nInput a name in the field.\nClick OK to create the mapping or Cancel to discard any changes and close the Add New Map window. The created mapping displays in the Available Maps list.\nDelete selected mappings\nClick to delete the selected mapping from the Available Maps list.\n\nCreate a new mapping\nDisplays the Add New Map window.\n\nInput a name in the field.\nClick OK to create the mapping or Cancel to discard any changes and close the Add New Map window. The created mapping displays in the Available Maps list.\n\nDelete selected mappings\nClick to delete the selected mapping from the Available Maps list.\nSet Default Mappings\nSets the default mappings for imported CAD drawings.\nSelect the check box adjacent to the required mapping on the Available Maps list.\nClick Save to save the mapping settings or click Cancel to discard any changes and close the Mapping Settings window.\nCreate a new mapping\nDisplays the Add New Map window.\nInput a name in the field.\nClick OK to create the mapping or Cancel to discard any changes and close the Add New Map window. The created mapping displays in the Available Maps list.\nDelete selected mappings\nClick to delete the selected mapping from the Available Maps list.\n\n\n\nAvailable Maps\nMap Actions\nCreate a new mapping\nAdd New Map\nOK\nCancel\nAdd New Map\nAvailable Maps\nDelete selected mappings\nAvailable Maps\nSet Default Mappings\nAvailable Maps\nSave\nCancel\nMapping Settings"}
{"Headers": "Create and Modify Representation and Hatch Styles", "Content": "Sets the display of drawing elements and defines the hatching style.\nGlobal styles can be overridden by user-defined styles which can be applied to drawing items. The styles are stored in local Representation Libraries.\n\n\n\n"}
{"Headers": "Create and Modify Representation Styles", "Content": "Select the Rep. Rules tab to display the current user-defined representation styles for the drawing.\nRepresentation Styles\nThe Representation Styles part of the Representation and Hatch Rules window allows you to add, remove and define representation styles (STYL).\n\nAdd\nClick Add from the drop down list to create a representation style. A new representation style with a default name and attributes is created and added to the list of available representation styles.\nRemove\nClick to delete the currently selected representation style.\nAdd\nClick Add from the drop down list to create a representation style. A new representation style with a default name and attributes is created and added to the list of available representation styles.\nRemove\nClick to delete the currently selected representation style.\nColour and Style Attributes\nThe Color and Style Attributes part of the Representation and Hatch Rules window allows you to select the line styles, colours and model visual layers for the available representation styles.\n\nStandard options of line colour, style and model visual layer are set explicitly by selecting system-defined settings from the colour, line-pattern and thickness, and model visual layer drop-down lists.\nClick to display the colour, line-pattern and thickness, and model visual layer drop-down lists for a representation style.\nClick to minimize the colour, line-pattern and thickness, and model visual layer drop-down lists for a representation style.\n\nClick to display the colour, line-pattern and thickness, and model visual layer drop-down lists for a representation style.\n\nClick to minimize the colour, line-pattern and thickness, and model visual layer drop-down lists for a representation style.\nRepresentation Style Attributes\nThe Style Attributes part of the Representation and Hatch Rules window allows you to define the display of a number of design items.\n\nTube (TUBE)\nSelect the check box to display all pipes.\nDe-select the check box to suppress the display of all pipes.\nObstructions (OBST)\nSelect the check box to display all obstructions.\nDe-select the check box to suppress the display of all obstructions.\nProfile (PRFG)\nSelect the check box to display all steelwork profiles.\nDe-select the check box to suppress the display of all steelwork profiles.\nPiping Symbols (PSYM)\nSelect the check box to display all piping symbols.\nDe-select the check box to suppress the display of all piping symbols.\nInsulation (INSU)\nSelect the check box to display all insulation.\nDe-select the check box to suppress the display of all insulation.\nP-Line (PLFG)\nSelect the check box to display all steelwork stick build representation.\nDe-select the check box to suppress the display of all steelwork stick build representation.\nCentreline (CLFG)\nSelect the check box to display all center lines.\nDe-select the check box to suppress the display of all center lines.\nDrawing Level (DLEV)\nInput a value to modify the drawing level. The default value is 6.\nTube (TUBE)\nSelect the check box to display all pipes.\nDe-select the check box to suppress the display of all pipes.\nObstructions (OBST)\nSelect the check box to display all obstructions.\nDe-select the check box to suppress the display of all obstructions.\nProfile (PRFG)\nSelect the check box to display all steelwork profiles.\nDe-select the check box to suppress the display of all steelwork profiles.\nPiping Symbols (PSYM)\nSelect the check box to display all piping symbols.\nDe-select the check box to suppress the display of all piping symbols.\nInsulation (INSU)\nSelect the check box to display all insulation.\nDe-select the check box to suppress the display of all insulation.\nP-Line (PLFG)\nSelect the check box to display all steelwork stick build representation.\nDe-select the check box to suppress the display of all steelwork stick build representation.\nCentreline (CLFG)\nSelect the check box to display all center lines.\nDe-select the check box to suppress the display of all center lines.\nDrawing Level (DLEV)\nInput a value to modify the drawing level. The default value is 6.\nRepresentation Rule Attributes\nThe Representation Rule Attributes part of the Representation and Hatch Rules window allows you to define some representation rule attributes.\n\nNo HLR\nSelect the check box to remove Hidden Line Representation.\nSymbol\nSelect the check box to display 2D Symbolic representation.\nNo HLR\nSelect the check box to remove Hidden Line Representation.\nSymbol\nSelect the check box to display 2D Symbolic representation.\nTo apply the currently selected representation style to design items, click Select Items.\nYou are prompted to Select design item\n\nClick to identify the required items.\nWhen all required items have been selected, press Enter.The selected representation style is then applied to the items.\nTo apply the currently selected representation style to design items and to their significant owners, click Select Owners.\nYou are then prompted to Select design owner\n\nClick to identify the required items.\nWhen all the required items have been selected, press Enter. The selected representation style is then applied to the items and their owners.\nAdd\nClick Add from the drop down list to create a representation style. A new representation style with a default name and attributes is created and added to the list of available representation styles.\nRemove\nClick to delete the currently selected representation style.\nClick to display the colour, line-pattern and thickness, and model visual layer drop-down lists for a representation style.\nClick to minimize the colour, line-pattern and thickness, and model visual layer drop-down lists for a representation style.\nTube (TUBE)\nSelect the check box to display all pipes.\nDe-select the check box to suppress the display of all pipes.\nObstructions (OBST)\nSelect the check box to display all obstructions.\nDe-select the check box to suppress the display of all obstructions.\nProfile (PRFG)\nSelect the check box to display all steelwork profiles.\nDe-select the check box to suppress the display of all steelwork profiles.\nPiping Symbols (PSYM)\nSelect the check box to display all piping symbols.\nDe-select the check box to suppress the display of all piping symbols.\nInsulation (INSU)\nSelect the check box to display all insulation.\nDe-select the check box to suppress the display of all insulation.\nP-Line (PLFG)\nSelect the check box to display all steelwork stick build representation.\nDe-select the check box to suppress the display of all steelwork stick build representation.\nCentreline (CLFG)\nSelect the check box to display all center lines.\nDe-select the check box to suppress the display of all center lines.\nDrawing Level (DLEV)\nInput a value to modify the drawing level. The default value is 6.\nNo HLR\nSelect the check box to remove Hidden Line Representation.\nSymbol\nSelect the check box to display 2D Symbolic representation.\nNote:\nYou can click to deselect a selected item.\nNote:\nYou can click to deselect a selected item.\n\n\n\nRep. Rules\nRepresentation Styles\nRepresentation Styles\nRepresentation and Hatch Rules\nAdd\nAdd\nRemove\nColour and Style Attributes\nColor and Style Attributes\nRepresentation and Hatch Rules\nRepresentation Style Attributes\nStyle Attributes\nRepresentation and Hatch Rules\nTube (TUBE)\nObstructions (OBST)\nProfile (PRFG)\nPiping Symbols (PSYM)\nInsulation (INSU)\nP-Line (PLFG)\nCentreline (CLFG)\nDrawing Level (DLEV)\nRepresentation Rule Attributes\nRepresentation Rule Attributes\nRepresentation and Hatch Rules\nNo HLR\nSymbol\nSelect Items\nSelect design item\nNote\n:\nEnter\nSelect Owners\nSelect design owner\nNote\n:\nEnter"}
{"Headers": "Create and Modify Hatch Rules", "Content": "Select the Hatch Rules tab to display the current user-defined hatching styles for the drawing.\n\nHatching Styles\nThe Hatching Styles part of the Representation and Hatch Rules window allows you to add and remove hatching styles.\n\nAdd\nClick to create a hatching style. A new hatching style with a default name and attributes is created and added to the list of available hatching styles.\nRemove\nClick to delete the currently selected hatching style.\nAdd\nClick to create a hatching style. A new hatching style with a default name and attributes is created and added to the list of available hatching styles.\nRemove\nClick to delete the currently selected hatching style.\nTo modify the currently selected hatching style, you can modify the attributes that display in the lower sections of the Representation and Hatch Rules window.\nHatching Colour and Style\nThe Hatching Colour and Style part of the Representation and Hatch Rules window allows you to select the line styles, colours and fills for the currently selected hatching style.\n\nClick to display the colour, fill and line style drop-down lists for a line type.\nClick to minimize the colour, fill and line style drop-down lists for a line type.\n\nClick to display the colour, fill and line style drop-down lists for a line type.\n\nClick to minimize the colour, fill and line style drop-down lists for a line type.\nYou can select a colour, fill and line style from the drop-down lists for each available hatching style.\nHatching Rules\nThe Hatching Rules part of the Representation and Hatch Rules window allows you to define the items to which hatching styles apply.\n\nYou can define the element surfaces to be considered for hatching.\nOnly Sectioned Surfaces\nSelect the option button to apply hatching only to surfaces cut by a section plane.\nAll Primitive Surfaces\nSelect the option button to apply hatching to all surfaces, the element need not be cut by a section plane.\nOnly Sectioned Surfaces\nSelect the option button to apply hatching only to surfaces cut by a section plane.\nAll Primitive Surfaces\nSelect the option button to apply hatching to all surfaces, the element need not be cut by a section plane.\nYou can define the surface direction of elements to be considered for hatching. The element to be hatched must also meet the criteria defined using the option buttons in the Consider part of the window.\nAll Surfaces in All Directions\nSelect the option button to apply hatching to all element surfaces\nOnly Surfaces Perpendicular to the View Direction\nSelect the option button to apply hatching only to surfaces perpendicular to the view direction. For example, if the view direction is north then the south face of the element is hatched.\nOnly Surfaces Facing in a Specified Direction\nSelect the option button to apply hatching to surfaces using a specified direction, instead of using the view direction.\nThe Direction and Derived option buttons become active.\nFor example, if six surfaces of a box are required to have different hatching styles then six hatching rules are applied.\nDirection\nInput a value in the field to apply hatching to surfaces matching the specified direction. For example, Input N in the field to apply hatching to surfaces in the North direction.\nDerived\nClick to define the object to associate with the Direction hatching using a cursor pick.\nYou are prompted to Select design item\nClick to identify the design element.\nAll Surfaces in All Directions\nSelect the option button to apply hatching to all element surfaces\nOnly Surfaces Perpendicular to the View Direction\nSelect the option button to apply hatching only to surfaces perpendicular to the view direction. For example, if the view direction is north then the south face of the element is hatched.\nOnly Surfaces Facing in a Specified Direction\nSelect the option button to apply hatching to surfaces using a specified direction, instead of using the view direction.\nThe Direction and Derived option buttons become active.\nFor example, if six surfaces of a box are required to have different hatching styles then six hatching rules are applied.\nDirection\nInput a value in the field to apply hatching to surfaces matching the specified direction. For example, Input N in the field to apply hatching to surfaces in the North direction.\nDerived\nClick to define the object to associate with the Direction hatching using a cursor pick.\nYou are prompted to Select design item\nClick to identify the design element.\nHatch Flags\nThe Hatch Flags part of the Representation and Hatch Rules window allows you to define hatching for pipe and HVAC duct cross-sections.\n\nPiping Symbols\nSelect the check box to apply hatching to the cross-section of a pipe or HVAC duct with a pipe end symbol or duct end symbol.\nDe-select the check box to apply hatching to the full cross-section of a pipe or HVAC duct.\nPiping Symbols\nSelect the check box to apply hatching to the cross-section of a pipe or HVAC duct with a pipe end symbol or duct end symbol.\nDe-select the check box to apply hatching to the full cross-section of a pipe or HVAC duct.\nTo apply the currently selected hatching style to design items, click Select Items.\nYou are prompted to Select design item\n\nClick to identify the required items.\nWhen all required items have been selected, press Enter. The selected hatching style is then applied to the items.\nTo apply the currently selected hatching style to design items and to their significant owners, click Select Owners.\nYou are then prompted to Select design owner\n\nClick to identify the required items.\nWhen all the required items have been selected, press Enter. The selected representation style is then applied to the items and their owners.\nAdd\nClick to create a hatching style. A new hatching style with a default name and attributes is created and added to the list of available hatching styles.\nRemove\nClick to delete the currently selected hatching style.\nClick to display the colour, fill and line style drop-down lists for a line type.\nClick to minimize the colour, fill and line style drop-down lists for a line type.\nOnly Sectioned Surfaces\nSelect the option button to apply hatching only to surfaces cut by a section plane.\nAll Primitive Surfaces\nSelect the option button to apply hatching to all surfaces, the element need not be cut by a section plane.\nAll Surfaces in All Directions\nSelect the option button to apply hatching to all element surfaces\nOnly Surfaces Perpendicular to the View Direction\nSelect the option button to apply hatching only to surfaces perpendicular to the view direction. For example, if the view direction is north then the south face of the element is hatched.\nOnly Surfaces Facing in a Specified Direction\nSelect the option button to apply hatching to surfaces using a specified direction, instead of using the view direction.\nThe Direction and Derived option buttons become active.\nFor example, if six surfaces of a box are required to have different hatching styles then six hatching rules are applied.\nDirection\nInput a value in the field to apply hatching to surfaces matching the specified direction. For example, Input N in the field to apply hatching to surfaces in the North direction.\nDerived\nClick to define the object to associate with the Direction hatching using a cursor pick.\nYou are prompted to Select design item\nClick to identify the design element.\nPiping Symbols\nSelect the check box to apply hatching to the cross-section of a pipe or HVAC duct with a pipe end symbol or duct end symbol.\nDe-select the check box to apply hatching to the full cross-section of a pipe or HVAC duct.\nNote:\nYou can click to deselect a selected item.\nNote:\nYou can click to deselect a selected item.\n\n\n\nHatch Rules\nHatching Styles\nHatching Styles\nRepresentation and Hatch Rules\nAdd\nRemove\nRepresentation and Hatch Rules\nHatching Colour and Style\nHatching Colour and Style\nRepresentation and Hatch Rules\nHatching Rules\nHatching Rules\nRepresentation and Hatch Rules\nOnly Sectioned Surfaces\nAll Primitive Surfaces\nConsider\nAll Surfaces in All Directions\nOnly Surfaces Perpendicular to the View Direction\nOnly Surfaces Facing in a Specified Direction\nDirection\nDerived\nDirection\nN\nDerived\nDirection\nSelect design item\nHatch Flags\nHatch Flags\nRepresentation and Hatch Rules\nPiping Symbols\nSelect Items\nSelect design item\nNote\n:\nEnter\nSelect Owners\nSelect design owner\nNote\n:\nEnter"}
{"Headers": "Create and Modify Views", "Content": "A View determines which 3D model items display on the Sheet that owns the View. Each View element defines:\nThe viewing parameters (for example, looking direction or scale)\nThe size, position and orientation of the View on the Sheet\nThe contents of the View (the Drawlist).\nThe viewing parameters (for example, looking direction or scale)\nThe viewing parameters (for example, looking direction or scale)\nThe size, position and orientation of the View on the Sheet\nThe size, position and orientation of the View on the Sheet\nThe contents of the View (the Drawlist).\nThe contents of the View (the Drawlist).\n\n\n\nView\n)"}
{"Headers": "Create Views", "Content": "If a Sheet has been created from a template, the Sheet normally contains at least one View, depending on how the template has been set up by the administrator. An existing View can be modified using the Format 2D tab (refer to Format 2D View for further information). Further Views can be created on a Sheet using the options on that tab, or on the Home tab in the View group. You must be at Sheet level or below before a View can be created.\nYou can also refer to Create Regions for further information.\nNote:\nAttributes set at Sheet level are inherited as the default attributes of Views within the Sheet.\n\n\n\nFormat 2D View\nCreate Regions\nFormat 2D View\nHome\nView\nSheet level\nNote\n:\nCreate Regions"}
{"Headers": "Create Quick View", "Content": "Creates a plan view containing objects selected in the Model Explorer.\n\n\n"}
{"Headers": "Create Advanced View", "Content": "Creates a marine specific 2D view of the model.\n\n\n"}
{"Headers": "Create Location Defined View", "Content": "Creates a location defined view which is used to present a part of the model in a 2D view, the view is based on a physical or imaginary model plane. The model element or plane used is defined as the view location. The view location forms the basis for the view limits, view content and view direction.\nThe location defined view functionality can be invoked using the Fluent UI or the Model Explorer.\n\nThe Create Location Defined View window allows you to define the view visual style, view scale, view title, view location and the elements that are added to the view.\nView Style\nSelect from the drop down list to define the view visual style. The creation and modification of visual styles is an administrative task, refer to Visual Styles for further information.\nThe location defined view can be displayed using a visual style with symbolic representation. The creation and modification of visual styles with symbolic representation is an administrative task, refer to Symbolic Representation for further information.\nView Scale\nSelect from the drop-down list to define the scale for the view. The default is Unset, this option automatically calculates the view scale to fit within the view frame.\nIf the view style has a predefined scale, this scale is used as the default value. The predefined view scale is displayed in the drop-down list.\n\nAll scale values use the metric system, if the view style predefined scale uses a different system, the scale value is converted to the metric system.\nIf a view scale is used, the view frame size is automatically calculated.\nView Title\nInput the view title in the field. The view title is restricted to a limit of 1000 characters and can include symbols, numbers and spaces. The view title can be displayed on the drawing canvas as intelligent text and is displayed in the Active Properties window if the view is selected as the Current Owner.\nDefinition\nThe Definition tab allows you to define the view location and the element types that are added to the view.\nView Location\nA location defined view is defined on a plane. This plane can be derived from a model element, a grid position or a coordinate value. For example:\nIf the View Location field is empty or the entered value is not valid, an error message is displayed.\n\nSelect a design element from the Model Explorer or click on an element on any view on the drawing canvas and click CE to populate the View Location field with the selected element.\nElements\nSelect the required check boxes to define the element types that are added to the view.\nAlternatively, select the All Elements check box to add all element types to the view.\nLimits\nThe Limits tab becomes available when a valid View Location is defined and allows you to define the depth, orientation and view limits.\nVolume Criteria\nThe volume criteria displays the view location.\n\nSection planes, used for clipping, are created along with the definition of the location defined view. For orthogonal locations, the planes are aligned with the view limits with the exception of the planes representing the depth which are parallel to location plane. By default, the planes representing the depth are created \u00b1100 mm from the view position in the view direction. For an inclined location, the section planes still represent an orthogonal system but are based on the inclined plane representing the location. As the system of section planes are orthogonal and aligned with the view orientation, they can be modified using the Section functionality available on Format 2D tab. Refer to Format 2D View for further information.\n\nDepth Behind\nInput a value in the field to define the elements that display in the view, measured from the location plane. All elements that are positioned within the depth value display in the location defined view. The default is 100mm.\nDepth in Front\nInput a value in the field to define the elements that display in the view, measured from the location plane. All elements that are positioned within the depth value display in the location defined view. The default is 100mm.\nOrientation\nInput a value in the field or select from the drop-down list to modify the view orientation. Only a view orientation along the same plane can be used. For example a view in the X orientation can be modified to -X.\nView Limits\nAs the location defined view manages the section planes, the functionality to create or remove section planes is disabled in the View Limits window. Refer to Modify View Limits for further information.\nClick Continue to continue the process or Cancel to discard any changes and close the Create Location Defined View window.\nIf a view scale is defined, you are prompted to Specify the centre point or\nInput values in the dimension fields and press Enter or click to identify the center of the view.\nIf a view scale is not defined, you are prompted to Specify the first corner or\nInput values in the dimension fields and press Enter or click to identify the first corner of the view.\nYou are then prompted to Specify the opposite corner or\nInput values in the dimension fields and press Enter or click to identify the opposite corner of the view. The view is created.\nThroughout the view creation process you can press ESC to cancel the command. Additional functionality is also available.\nScale Factor\nPress the down arrow key and select Scale Factor to define a different scale factor for the location defined view.\nInput the required scale at the prompt and press Enter.\nCentre-Width\nPress the down arrow key and select Centre-Width to create a location defined view with a specified center point.\nYou are then prompted to Specify the centre point or\nInput values in the dimension fields and press Enter or click to identify the center of the view.\nYou are then prompted to Specify the width or\nInput a dimensional value in the field and press Enter or move the cursor left or right to define the width of the view. Click to confirm the required width.\nYou are then prompted to Specify the height or\nInput a dimensional value in the field and press Enter or move the cursor up or down to define the height of the view. Click to confirm the required height. The view is created.\nCorner\nPress the down arrow key and select Corner to create a location defined view with specified corners. The process is identical to creating a location defined view with a view scale that is not defined, described previously.\nCentre-Scale\nPress the down arrow key and select Centre-Scale to create a location defined view with a specified center point and view scale.\nYou are prompted to Scale or\nInput a value in the field and press Enter to define the scale of the view.\nYou are then prompted to Specify the centre point or\nInput values in the dimension fields and press Enter or click to identify the center of the view. The view is created.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nScale Factor\nPress the down arrow key and select Scale Factor to define a different scale factor for the location defined view.\nInput the required scale at the prompt and press Enter.\nCentre-Width\nPress the down arrow key and select Centre-Width to create a location defined view with a specified center point.\nYou are then prompted to Specify the centre point or\nInput values in the dimension fields and press Enter or click to identify the center of the view.\nYou are then prompted to Specify the width or\nInput a dimensional value in the field and press Enter or move the cursor left or right to define the width of the view. Click to confirm the required width.\nYou are then prompted to Specify the height or\nInput a dimensional value in the field and press Enter or move the cursor up or down to define the height of the view. Click to confirm the required height. The view is created.\nCorner\nPress the down arrow key and select Corner to create a location defined view with specified corners. The process is identical to creating a location defined view with a view scale that is not defined, described previously.\nCentre-Scale\nPress the down arrow key and select Centre-Scale to create a location defined view with a specified center point and view scale.\nYou are prompted to Scale or\nInput a value in the field and press Enter to define the scale of the view.\nYou are then prompted to Specify the centre point or\nInput values in the dimension fields and press Enter or click to identify the center of the view. The view is created.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nThe new VIEW element displays in the Draw Explorer.\n\nScale Factor\nPress the down arrow key and select Scale Factor to define a different scale factor for the location defined view.\nInput the required scale at the prompt and press Enter.\nCentre-Width\nPress the down arrow key and select Centre-Width to create a location defined view with a specified center point.\nYou are then prompted to Specify the centre point or\nInput values in the dimension fields and press Enter or click to identify the center of the view.\nYou are then prompted to Specify the width or\nInput a dimensional value in the field and press Enter or move the cursor left or right to define the width of the view. Click to confirm the required width.\nYou are then prompted to Specify the height or\nInput a dimensional value in the field and press Enter or move the cursor up or down to define the height of the view. Click to confirm the required height. The view is created.\nCorner\nPress the down arrow key and select Corner to create a location defined view with specified corners. The process is identical to creating a location defined view with a view scale that is not defined, described previously.\nCentre-Scale\nPress the down arrow key and select Centre-Scale to create a location defined view with a specified center point and view scale.\nYou are prompted to Scale or\nInput a value in the field and press Enter to define the scale of the view.\nYou are then prompted to Specify the centre point or\nInput values in the dimension fields and press Enter or click to identify the center of the view. The view is created.\nBack\nPress the down arrow key and select Back to undo the last action.\nAn X plane view is a transverse section, typically on a frame. For example, input FR172 to create the view plane using frame 172.\nA Y plane view is a longitudinal elevation. For example, input LP0 to create an elevation on the centreline.\nA Z plane view is a plan view, For example, input Z=5000 to create a plan view at 5 metres above base.\nThe name of a panel or reference surface object can be input to define the view plane.\nA reference surface object, panel or panel component can be selected in an existing view to define the location defined view. The view direction is defined by the location of the selected element.\nAn X plane view is a transverse section, typically on a frame. For example, input FR172 to create the view plane using frame 172.\nAn X plane view is a transverse section, typically on a frame. For example, input FR172 to create the view plane using frame 172.\nA Y plane view is a longitudinal elevation. For example, input LP0 to create an elevation on the centreline.\nA Y plane view is a longitudinal elevation. For example, input LP0 to create an elevation on the centreline.\nA Z plane view is a plan view, For example, input Z=5000 to create a plan view at 5 metres above base.\nA Z plane view is a plan view, For example, input Z=5000 to create a plan view at 5 metres above base.\nThe name of a panel or reference surface object can be input to define the view plane.\nThe name of a panel or reference surface object can be input to define the view plane.\nA reference surface object, panel or panel component can be selected in an existing view to define the location defined view. The view direction is defined by the location of the selected element.\nA reference surface object, panel or panel component can be selected in an existing view to define the location defined view. The view direction is defined by the location of the selected element.\nNote:\nThe # character is a special character in AVEVA E3D Design, input ## to output a single # character in the view title.\n\n\n\nVisual Styles\nSymbolic Representation\nFormat 2D View\nModify View Limits\nCreate Location Defined View\nView Style\nVisual Styles\nSymbolic Representation\nView Scale\nView Title\nActive Properties\nNote\n:\n##\n#\nDefinition\nDefinition\nView Location\nView Location\nCE\nView Location\nElements\nAll Elements\nLimits\nLimits\nView Location\nVolume Criteria\nSection\nFormat 2D\nFormat 2D View\nDepth Behind\nDepth in Front\nOrientation\nX\n-X\nView Limits\nView Limits\nModify View Limits\nContinue\nCancel\nCreate Location Defined View\nSpecify the centre point or\nEnter\nSpecify the first corner or\nEnter\nSpecify the opposite corner or\nEnter\nESC\nScale Factor\nScale Factor\nEnter\nCentre-Width\nCentre-Width\nSpecify the centre point or\nEnter\nSpecify the width or\nEnter\nSpecify the height or\nEnter\nCorner\nCorner\nCentre-Scale\nCentre-Scale\nScale or\nEnter\nSpecify the centre point or\nEnter\nBack\nBack"}
{"Headers": "Create Multi-Location View", "Content": "Creates a multi-location view which is traditionally used to present a ship's hull form graphically on a 2D drawing. The multi-location view consists of projections of the hull surface intersections using a series of planes. The planes are normally equally spaced in each of the three axes (X, Y, and Z). In naval architecture, a multi-location view type is dependent on whether the planes are perpendicular to the X-, Y- or Z- axis: body plan, half-breadth plan or sheer plan.\n\nThe Create Multi-Location View window allows you to define the view visual style, view title, view scale, view locations, the view surface and the elements that are added to the view.\nView Style\nSelect from the drop down list to define the view visual style. The creation and modification of visual styles is an administrative task, refer to Visual Styles for further information.\nView Title\nInput the view title in the field. The view title is restricted to a limit of 1000 characters and can include symbols, numbers and spaces. The view title can be displayed on the drawing canvas as intelligent text and is displayed in the Active Properties window if the view is selected as the Current Owner.\nView Scale\nSelect from the drop-down list to define the scale for the view. The default is Unset, this option automatically calculates the view scale to fit within the view frame.\nIf the view style has a predefined scale, this scale is used as the default value. The predefined view scale is displayed in the drop-down list.\n\nAll scale values use the metric system, if the view style predefined scale uses a different system, the scale value is converted to the metric system.\nIf a view scale is used, the view frame size is automatically calculated.\nDefinition\nThe Definition tab allows you to define the view location(s) and the element types that are added to the view.\nView Location\nTo create a Multi-Location view, at least one location must be specified. A series of locations can be specified using valid syntax. For example:\nAs an alternative to a long enumeration of locations, repetition syntax can be used in the form of start(step)end, for example:\nThe repetition syntax can be used in combination with ordinary enumeration, for example:\nIf the View Location field is empty or the entered value is not valid, an error message is displayed.\n\nView Surface\nTo add elements located within a surface area to the view, input a value in the field to define the Surface (SRFSUR) element or click Select Surface to add a surface element using the Model Explorer or an existing view.\nYou are prompted to Select design element\nClick to identify the design element to be added to the view. The Select Surface field is updated to indicate the added design element.\nIf a surface element is selected, it is added to the drawlist as a design element and so is every location that is not a grid element. If you select a surface element, the drawlist is populated so that elements are filtered by surface. The intent is that only model elements with a relation to the selected surface appear in the view. The filtering is implemented by adding two rules for every selected element type. The CRITERIA of the rules makes use of the TOPLOC pseudo attribute:\nThe criteria collects all elements in a hierarchy under SELECTED_TYPE that have their location defined by /SURFACE.\nTOPLOC is currently implemented for ICRPNT, ICRCUR and SRFSUR (points, curves and surfaces). The resulting list of model elements can be of the following types when TYPENAME UPANEL or TYPENAME UPANEL_MEM is used:\nIf a surface element is not selected, normal ADDE statements are used. For example:\nThe primary purpose of using TOPLOC/TOPLIM is for performance reasons. Using the criteria ALL UPANEL instead of ALL FROM TOPLOC(UPANEL) of /SURFACE and ALL FROM TOPLIM(UPANEL) of /SURFACE could result in a very significant loss of performance.\nElements\nSelect the required check boxes to define the element types that are added to the view.\nAlternatively, select the All Elements check box to add all element types to the view.\nAn X plane view is a transverse section, typically on a frame. For example, input FR90;FR93;FR96;FR99 to create the view planes using frames 90, 93, 96, and 99.\nA Y plane view is a longitudinal elevation. For example, input LP0;LP1;LP2 to create elevations on the centreline using longitudinal positions LP0, LP1 and LP2.\nA Z plane view is a plan view, For example, input Z=5000;Z=10000 to create a plan view at 5 metres and 10 metres above the base.\nAn X plane view is a transverse section, typically on a frame. For example, input FR90;FR93;FR96;FR99 to create the view planes using frames 90, 93, 96, and 99.\nAn X plane view is a transverse section, typically on a frame. For example, input FR90;FR93;FR96;FR99 to create the view planes using frames 90, 93, 96, and 99.\nA Y plane view is a longitudinal elevation. For example, input LP0;LP1;LP2 to create elevations on the centreline using longitudinal positions LP0, LP1 and LP2.\nA Y plane view is a longitudinal elevation. For example, input LP0;LP1;LP2 to create elevations on the centreline using longitudinal positions LP0, LP1 and LP2.\nA Z plane view is a plan view, For example, input Z=5000;Z=10000 to create a plan view at 5 metres and 10 metres above the base.\nA Z plane view is a plan view, For example, input Z=5000;Z=10000 to create a plan view at 5 metres and 10 metres above the base.\nFR0(5)50\nZ=500(500)10000\nFR0(5)50\nFR0(5)50\nZ=500(500)10000\nZ=500(500)10000\nFR0(5)50;FR60;FR70;FR80;FR100(5)120\nZ=0(500)5000;Z=6000;Z=8000;Z=10000(500)15000\nFR0(5)50;FR60;FR70;FR80;FR100(5)120\nFR0(5)50;FR60;FR70;FR80;FR100(5)120\nZ=0(500)5000;Z=6000;Z=8000;Z=10000(500)15000\nZ=0(500)5000;Z=6000;Z=8000;Z=10000(500)15000\nIPLATE\nINBNDRY/ILIM\nISTIFF\nIHOLE\nIPLATE\nIPLATE\nINBNDRY/ILIM\nINBNDRY/ILIM\nISTIFF\nISTIFF\nIHOLE\nIHOLE\nNote:\nThe # character is a special character in AVEVA E3D Design, input ## to output a single # character in the view title.\n\n\n\nVisual Styles\nCreate Multi-Location View\nView Style\nVisual Styles\nView Title\nActive Properties\nNote\n:\n##\n#\nView Scale\nDefinition\nDefinition\nView Location\nFR90;FR93;FR96;FR99\nLP0;LP1;LP2\nZ=5000;Z=10000\nView Location\nView Surface\nSelect Surface\nSelect design element\nSelect Surface\nElements\nAll Elements"}
{"Headers": "Create Expansion View", "Content": "Creates a view of model elements that are unfolded from their curved shape into a flat form. This type of representation is only relevant for model elements with a relation to a sculptured surface where the relation can be described by a curve on the surface. It is always the curves that are unfolded. For example:\nThe expansion view is a specific way of representing the model and there are some limitations as to which functions are available. The view direction is always implicitly selected from the expansion view setup. The view direction is dependent on the expansion coordinate system. The default expansion coordinate system dictates the view direction. For example, -Z specifies a downward view direction. Therefore, view direction selection is disabled.\nThe functionality to create projection or section views is disabled because you cannot modify the view direction. These functions create a copy of the existing view with a different view direction, which is of no use for an expansion view.\nOther functions that are disabled, or are of no use for expansion views are:\n\nThe Create Expansion View window allows you to define the view visual style, view title, view scale, the expansion surface, the expansion coordinates and the elements that are added to the view.\nView Style\nSelect from the drop down list to define the view visual style. The creation and modification of visual styles is an administrative task, refer to Visual Styles for further information.\nView Title\nInput the view title in the field. The view title is restricted to a limit of 1000 characters and can include symbols, numbers and spaces. The view title can be displayed on the drawing canvas as intelligent text and is displayed in the Active Properties window if the view is selected as the Current Owner.\nView Scale\nSelect from the drop-down list to define the scale for the view. The default is Unset, this option automatically calculates the view scale to fit within the view frame.\nIf the view style has a predefined scale, this scale is used as the default value. The predefined view scale is displayed in the drop-down list.\n\nAll scale values use the metric system, if the view style predefined scale uses a different system, the scale value is converted to the metric system.\nIf a view scale is used, the view frame size is automatically calculated.\nDefinition\nThe Definition tab allows you to define the expansion surface, the expansion coordinate system and the element types that are added to the view.\nExpansion Surface\nTo add elements located within a surface area to the view, input a value in the field to define the Surface (SRFSUR) element or click Select Surface to add a surface element using the Model Explorer or an existing view.\nYou are prompted to Select design element\nClick to identify the surface element to be added to the view. The Select Surface field is updated to indicate the added surface element.\nIf a surface element is selected, it is added to the drawlist as a design element and so is every location that is not a grid element. If you select a surface element, the drawlist is populated so that elements are filtered by surface. The intent is that only model elements with a relation to the selected surface appear in the view. The filtering is implemented by adding two rules for every selected element type. The CRITERIA of the rules makes use of the TOPLOC pseudo attribute:\nThe criteria collects all elements in a hierarchy under SELECTED_TYPE that have their location defined by /SURFACE.\nTOPLOC is currently implemented for ICRPNT, ICRCUR and SRFSUR (points, curves and surfaces). The resulting list of model elements can be of the following types when TYPENAME UPANEL or TYPENAME UPANEL_MEM is used:\nIf a surface element is not selected, normal ADDE statements are used. For example:\nThe primary purpose of using TOPLOC is for performance reasons. Using the criteria ALL UPANEL instead of ALL FROM TOPLOC(UPANEL) of /SURFACE could result in a very significant loss of performance.\nIf the Expansion Surface field is empty or the entered value is not valid, an error message is displayed.\n\nExpansion Coordinate System\nThe expansion coordinate system enables DRAW to perform unfolding of model elements. The default values are suitable for unfolding the main ship hull surface where the expansion direction is normally in a for/aft direction (along the X-axis) and the expansion direction is in the portside/starboard direction (along the Y-axis). When unfolding surfaces other than the main ship hull, it is possible to input alternative values for Expansion Origin, Main Direction and Expansion Direction.\nElements\nSelect the required check boxes to define the element types that are added to the view.\nCurves created by intersecting the surface (with a plane for instance).\nStiffeners with a trace defined by a curve in the surface, the trace curve is unfolded.\nPanels limited by the surface, the boundary limits located within the surface are unfolded.\nCurves created by intersecting the surface (with a plane for instance).\nCurves created by intersecting the surface (with a plane for instance).\nStiffeners with a trace defined by a curve in the surface, the trace curve is unfolded.\nStiffeners with a trace defined by a curve in the surface, the trace curve is unfolded.\nPanels limited by the surface, the boundary limits located within the surface are unfolded.\nPanels limited by the surface, the boundary limits located within the surface are unfolded.\nSection planes: all functionality related to the creation and modification of section planes is disabled.\nDetail view\nQuick add\nPerspective view: the perspective angle is always zero and cannot be modified.\nHatching (using a hatching representation rule set or local hatching rules): Inhibiting any setting of a hatching rule set has no effect.\nSection planes: all functionality related to the creation and modification of section planes is disabled.\nSection planes: all functionality related to the creation and modification of section planes is disabled.\nDetail view\nDetail view\nQuick add\nQuick add\nPerspective view: the perspective angle is always zero and cannot be modified.\nPerspective view: the perspective angle is always zero and cannot be modified.\nHatching (using a hatching representation rule set or local hatching rules): Inhibiting any setting of a hatching rule set has no effect.\nHatching (using a hatching representation rule set or local hatching rules): Inhibiting any setting of a hatching rule set has no effect.\nIPLATE\nINBNDRY/ILIM\nISTIFF\nIHOLE\nIPLATE\nIPLATE\nINBNDRY/ILIM\nINBNDRY/ILIM\nISTIFF\nISTIFF\nIHOLE\nIHOLE\nNote:\nThe # character is a special character in AVEVA E3D Design, input ## to output a single # character in the view title.\n\n\n\nCreate Expansion View\nView Style\nVisual Styles\nView Title\nActive Properties\nNote\n:\n##\n#\nView Scale\nDefinition\nDefinition\nExpansion Surface\nSelect Surface\nSelect design element\nSelect Surface\nExpansion Surface\nExpansion Coordinate System\nExpansion Origin\nMain Direction\nExpansion Direction\nElements"}
{"Headers": "Create Design View", "Content": "Creates a new view containing an easily selected and managed list of objects with a specified view direction or scale.\n\n\n"}
{"Headers": "Create Projection View", "Content": "Creates a projection view of the objects in an existing 2D view.\n\n\n"}
{"Headers": "Create Section View", "Content": "Creates a section view of the objects in an existing 2D view.\nWhen section views are added to a drawing, a View Section Indicator (VSI) can be assigned to display on both the source view and the section view. The VSI indicates the geometry, limits and look direction of the cutting plane on the source view, and displays a title on the section view. A VSI identifier character is allocated to the VSI in order to uniquely identify the section view (For example, A).\n\nThe visual style of the of the VSI is configured by the administrator. The VSI definition in use is determined by the user defaults (refer to Modify User Defaults for further information) or system defaults (refer to Set System Defaults for further information), if unset, no VSI is created.\nOnce the Draw application has generated the VSI, it can be modified by the user as required. Modification of the VSI has no effect on the section view definition, any changes are purely cosmetic.\nUpdating the section view or the corresponding cutting plane definition automatically updates the VSI and any modifications to the VSI are lost.\n\n\n\nModify User Defaults\nSet System Defaults\nModify User Defaults\nSet System Defaults"}
{"Headers": "Create Detail View", "Content": "Creates a detail view that displays a selected area of an existing view\nYou are prompted to Select view\nClick to identify the view to create a detail view from.\nYou are then prompted to Specify the first corner or <Share Drawlist>\n\nInput values in the dimension fields and press Enter or click to identify the first corner of the area to be included in the view.\nYou are then prompted to Specify the opposite corner or\nInput values in the dimension fields and press Enter or click to identify the opposite corner of the area to be included in the view. The selected area is represented by a shaded box.\n\nYou are then prompted to Specify a point or <Scale>\nThe view scale displays at the cursor.\n\nInput values in the dimension fields or click to identify the location of the new view.\nAn outline is placed on the source view, indicating the area comprising the detail view. The command ends automatically.\nThroughout the view creation process you can press ESC to cancel the command. Additional functionality is also available.\nShare Drawlist\nPress the down arrow key and select Share Drawlist to reference the drawlist from the source view drawlist.\nNew Drawlist\nPress the down arrow key and select New Drawlist to create a new drawlist as a copy of the source view drawlist.\nPolygon\nPress the down arrow key and select Polygon to create a detail view with a polygonal selection. Refer to Create Detail View with Polygonal Selection for further information.\nRectangle\nPress the down arrow key and select Rectangle to create a detail rectangular detail view.\nBack\nPress the down arrow key and select Back to undo the last action.\nScale\nPress the down arrow key and select Scale to specify a scale for the view. Input the required scale at the prompt and press Enter. You are returned to the Specify a point or <Scale> prompt.\n\nShare Drawlist\nPress the down arrow key and select Share Drawlist to reference the drawlist from the source view drawlist.\nNew Drawlist\nPress the down arrow key and select New Drawlist to create a new drawlist as a copy of the source view drawlist.\nPolygon\nPress the down arrow key and select Polygon to create a detail view with a polygonal selection. Refer to Create Detail View with Polygonal Selection for further information.\nRectangle\nPress the down arrow key and select Rectangle to create a detail rectangular detail view.\nBack\nPress the down arrow key and select Back to undo the last action.\nScale\nPress the down arrow key and select Scale to specify a scale for the view. Input the required scale at the prompt and press Enter. You are returned to the Specify a point or <Scale> prompt.\n\nThe new VIEW element displays in the Draw Explorer.\n\nShare Drawlist\nPress the down arrow key and select Share Drawlist to reference the drawlist from the source view drawlist.\nNew Drawlist\nPress the down arrow key and select New Drawlist to create a new drawlist as a copy of the source view drawlist.\nPolygon\nPress the down arrow key and select Polygon to create a detail view with a polygonal selection. Refer to Create Detail View with Polygonal Selection for further information.\nRectangle\nPress the down arrow key and select Rectangle to create a detail rectangular detail view.\nBack\nPress the down arrow key and select Back to undo the last action.\nScale\nPress the down arrow key and select Scale to specify a scale for the view. Input the required scale at the prompt and press Enter. You are returned to the Specify a point or <Scale> prompt.\nNote:\nThe prompt does not display if a view is already selected.\nNote:\nIntelligent grip points are retained for the detail view.\n\n\n\nCreate Detail View with Polygonal Selection\nSelect view\nNote\n:\nSpecify the first corner or <Share Drawlist>\nEnter\nSpecify the opposite corner or\nEnter\nSpecify a point or <Scale>\nNote\n:\nESC\nShare Drawlist\nShare Drawlist\nNew Drawlist\nNew Drawlist\nPolygon\nPolygon\nCreate Detail View with Polygonal Selection\nRectangle\nRectangle\nBack\nBack\nScale\nScale\nEnter\nSpecify a point or <Scale>\nDraw Explorer"}
{"Headers": "Create Location Defined Detail View", "Content": "Creates a location defined detail view that displays as an orthogonal view based on a location plane, view direction and view depth defined from an existing view\nYou are prompted to Select view\nClick to identify the view to create a detail view from.\nYou are then prompted to Specify first point for location plane\n\nInput values in the dimension fields and press Enter or click to identify the first point of the location plane. The coordinate value in the view direction of the first point selected for the location plane will be the centre of the new detail view (of relevance for views of extended limits in the view direction). Hence, if the view has a large depth, it is recommended to select the point by snapping to a model element which will display in the center of the detail view.\nYou are then prompted to Specify the second point for location plane or\nInput values in the dimension fields and press Enter or click to identify the second point of the location plane. Orthogonal locking is applied automatically, the location plane is represented by either a horizontal or vertical line.\nYou are then prompted to Specify 'Depth in Front' or\nThe depth in front and depth behind is represented by a shaded box which is formed symmetrically around the location plane. The blue arrow indicates the view direction for the detail view. To specify the detail view direction, move the cursor to the appropriate side of the location plane. For example, if the required view direction is a view from the right, move the cursor to the right of the location plane.\n\nInput values in the dimension fields and press Enter or click to identify the depth of the detail view.\nYou are then prompted to Specify a point or <Scale>\nThe view scale displays at the cursor.\n\nInput values in the dimension fields or click to identify the location of the new view.\nAn outline is placed on the source view, indicating the area comprising the detail view. The command ends automatically.\nThroughout the view creation process you can press ESC to cancel the command. Additional functionality is also available.\nBack\nPress the down arrow key and select Back to undo the last action.\nIndividual Depths\nPress the down arrow key and select Individual Depths to specify the depth in front and the depth behind values individually by specifying separate points for the respective depths.\nScale\nPress the down arrow key and select Scale to specify a scale for the view. Input the required scale at the prompt and press Enter. You are returned to the Specify a point or <Scale> prompt.\nHeight/Width\nPress the down arrow key and select Height or Width to define the view height or width (the available option is dependent on the view directions of the source view and the target detail view). The specified depth and length of the location plane represents the other two dimensions limiting the resulting detail view. If a Height or Width value are not specified, both the height and width of the detail view are derived from the length of location plane.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nIndividual Depths\nPress the down arrow key and select Individual Depths to specify the depth in front and the depth behind values individually by specifying separate points for the respective depths.\nScale\nPress the down arrow key and select Scale to specify a scale for the view. Input the required scale at the prompt and press Enter. You are returned to the Specify a point or <Scale> prompt.\nHeight/Width\nPress the down arrow key and select Height or Width to define the view height or width (the available option is dependent on the view directions of the source view and the target detail view). The specified depth and length of the location plane represents the other two dimensions limiting the resulting detail view. If a Height or Width value are not specified, both the height and width of the detail view are derived from the length of location plane.\nA View Section Indicator (VSI) is applied to both the source view and the detail view. The VSI represents the limits and view direction of the location plane on the source view and displays a title on the location defined detail view. A VSI identifier character is allocated to the VSI in order to uniquely identify the detail view (For example, A)\n\nThe visual style of the of the VSI is configured by the administrator. The VSI definition in use is determined by the user defaults (refer to Modify User Defaults for further information) or system defaults (refer to Set System Defaults for further information), if unset, no VSI is created.\nOnce the Draw application has generated the VSI, it can be modified by the user as required. Modification of the VSI has no effect on the location defined detail view definition, any changes are purely cosmetic.\nIf a location detail view is deleted, the related VSI is removed from the source view.\nThe new VIEW element displays in the Draw Explorer.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nIndividual Depths\nPress the down arrow key and select Individual Depths to specify the depth in front and the depth behind values individually by specifying separate points for the respective depths.\nScale\nPress the down arrow key and select Scale to specify a scale for the view. Input the required scale at the prompt and press Enter. You are returned to the Specify a point or <Scale> prompt.\nHeight/Width\nPress the down arrow key and select Height or Width to define the view height or width (the available option is dependent on the view directions of the source view and the target detail view). The specified depth and length of the location plane represents the other two dimensions limiting the resulting detail view. If a Height or Width value are not specified, both the height and width of the detail view are derived from the length of location plane.\nNote:\nThe prompt does not display if a view is already selected.\n\n\n\nModify User Defaults\nSet System Defaults\nSelect view\nNote\n:\nSpecify first point for location plane\nEnter\nSpecify the second point for location plane or\nEnter\nSpecify 'Depth in Front' or\nEnter\nSpecify a point or <Scale>\nESC\nBack\nBack\nIndividual Depths\nIndividual Depths\nScale\nScale\nEnter\nSpecify a point or <Scale>\nHeight/Width\nHeight\nWidth\nModify User Defaults\nSet System Defaults"}
{"Headers": "Create Basic View", "Content": "Creates a basic view area, to which elements can subsequently be assigned.\nYou are prompted to Specify the first corner or <Use predefined>\nInput values in the dimension fields or click to identify the first corner of the view.\nYou are then prompted to Specify the opposite corner or\nInput values in the dimension fields or click to identify the opposite corner of the view.\nThe view is created. Elements can be added to the view using the Drawlist functionality, accessible from the Format 2D tab. Refer to Format 2D View for further information.\nThroughout the view creation process you can press ESC to cancel the command. Additional functionality is also available.\nCentre\nPress the down arrow key and select Centre to define the center of the view. Refer to Create Basic View with Specified Center Point for further information.\nUse predefined\nPress the down arrow key and select Use predefined to create a predefined view area in the center of the drawing sheet.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nCentre\nPress the down arrow key and select Centre to define the center of the view. Refer to Create Basic View with Specified Center Point for further information.\nUse predefined\nPress the down arrow key and select Use predefined to create a predefined view area in the center of the drawing sheet.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nThe new VIEW element displays in the Draw Explorer.\n\nCentre\nPress the down arrow key and select Centre to define the center of the view. Refer to Create Basic View with Specified Center Point for further information.\nUse predefined\nPress the down arrow key and select Use predefined to create a predefined view area in the center of the drawing sheet.\nBack\nPress the down arrow key and select Back to undo the last action.\n\n\n\nFormat 2D View\nCreate Basic View with Specified Center Point\nSpecify the first corner or <Use predefined>\nSpecify the opposite corner or\nFormat 2D\nFormat 2D View\nESC\nCentre\nCentre\nCreate Basic View with Specified Center Point\nUse predefined\nUse\npredefined\nBack\nBack\nDraw Explorer"}
{"Headers": "Modify 2D View using Grip Points", "Content": "Modifies the currently selected 2D View. You can manipulate the grip points to modify a 2D View.\n\n\n\n\n2D View"}
{"Headers": "Modify Size of 2D View using Grip Points", "Content": "Sets the size of a 2D view.\nClick a square grip point around the edge of the view. The grip point displays red.\nYou are prompted to Specify stretch point\nMove the cursor to modify the size of the view. The design elements within the view move in relation to the cursor. A preview image displays.\n\nInput values in the dimension fields and press Enter or click to identify the size of the view.\nNote:\nTo modify the size of the view and maintain the location of the design elements within the view, press and hold the Control key while moving the cursor.\n\n\n\nSpecify stretch point\nNote\n:\nControl\nEnter"}
{"Headers": "Modify Scale of Design Elements within 2D View using Grip Points", "Content": "Sets the scale of design elements within the a 2D view.\nClick a triangular grip point.\nYou are prompted to Specify stretch point\nTo increase the size of the design elements within the view, move the cursor away from the design elements. The further the cursor is moved, the larger the design elements become. To decrease the size of the design elements within the view, move the cursor towards the design elements. The further the cursor is moved, the smaller the design elements become. A preview image displays.\n\nInput values in the dimension fields and press Enter or click to identify the design element scale.\n\n\n\nSpecify stretch point\nEnter"}
{"Headers": "Modify Position of 2D View using Grip Points", "Content": "Sets the position of a 2D view while maintaining its size, and the position and size of the design elements within it.\nClick the square grip point in the centre of the view,\nYou are prompted to Specify stretch point\nMove the cursor to specify a position for the view. A preview image displays.\n\nInput values in the dimension fields and press Enter or click to identify the new position for the centre point of the view.\n\n\n\nSpecify stretch point\nEnter"}
{"Headers": "Modify Section Plane using Grip Points", "Content": "Modifies the section plane using grip points. Grip points can be moved, rotated and flipped.\nPosition Section Plane\nMoves all of the grip points to reposition the entire section plane using either the 2D or 3D functionality.\nClick the square grip point in the centre of the section plane.\nYou are prompted to Specify stretch point\nMove the cursor to specify a position for the section plane. A preview displays.\n\nInput values in the dimension fields and press Enter or click to identify the position for the center point of the section plane.\nRotate Section Plane\nRotates all of the grip points to reposition the entire section plane using either the 2D or 3D functionality.\nClick the rotate grip point above the center of the section plane.\nYou are prompted to Specify angle\nMove the cursor to specify the rotation angle for the section plane. A preview displays.\n\nInput an angular value in the field and press Enter or click to identify the rotation angle of the section plane.\nFlip Section Plane\nFlips all of the grip points to reposition the entire section plane using either the 2D or 3D functionality.\nClick the square grip point below the centre of the section plane.\nYou are prompted to Specify stretch point\nMove the cursor to specify a position for the section plane. A preview displays.\n\nClick within the drawn area of the view to flip the section plane.\nAlternatively, you can flip all of the grip points to modify reposition the entire section plane using the 3D functionality.\nClick the half-filled square grip point.\nYou are prompted to Specify hidden side\nMove the cursor to specify a position for the section plane. A hatched area indicates the side of the plane that an area of the view is removed from.\n\nClick within the drawn area of the view to flip the section plane.\nNote:\nIntelligent (circle) grip points are not retained for repositioned section planes. By default, circle grip points are modified to square grip points.\nNote:\nIntelligent (circle) grip points are not retained for rotated section planes. By default, circle grip points are modified to square grip points.\nNote:\nIntelligent (circle) grip points are retained for flipped section planes.\n\n\n\nPosition Section Plane\nSpecify stretch point\nEnter\nNote\n:\nRotate Section Plane\nSpecify angle\nEnter\nNote\n:\nFlip Section Plane\nSpecify stretch point\nSpecify hidden side\nNote\n:"}
{"Headers": "Modify Location Defined View", "Content": "A location defined view can be modified using the Format 2D tab (refer to Format 2D View for further information). Additional modification options are available using the Properties window. Refer to Properties for further information.\n\nAdvanced view type\nDisplays the view type. By default, the field is populated with Location Defined. The view type cannot be modified.\nDepth Behind\nInput a value in the field to define the elements that display in the view, measured from the location plane. All elements that are positioned within the depth value display in the location defined view. The default is 100mm.\nDepth in Front\nInput a value in the field to define the elements that display in the view, measured from the location plane. All elements that are positioned within the depth value display in the location defined view. The default is 100mm.\nLocation Plane\nInput a value in the field to modify the location plane. Only a location plane along the same orientation can be used.\nThe location plane value determines the location orientation for the view. It also determines an initial box for the view limits.\nLocation planes based on physical planes can be used for any model element with POS, ORI and WVOL (considered with respect to the world).\nThe POS serves as a basis for the depth.\nThe ORI serves as a basis for the initial view direction.\nThe enclosing box volume (WVOL) is retrieved from the model element that serves as a basis for the location.\nLocation planes based on frame positions (for example, FR23) refer to a GRIDPL element that behaves like a model element when it comes to POS, ORI and WVOL.\nLocation planes based on coordinate values, for example, POS and ORI (direction) are implicitly defined by the coordinate value (for example, X=1000 where POS=1000,0,0 and DIR=X). The enclosing box volume is defined by the WVOL for the closest GRIDPL.\nOrientation\nInput a value in the field or select from the drop-down list to modify the view orientation. Only a view orientation along the same plane can be used. For example a view in the X orientation can be modified to -X.\nAdvanced view type\nDisplays the view type. By default, the field is populated with Location Defined. The view type cannot be modified.\nInput a value in the field to define the elements that display in the view, measured from the location plane. All elements that are positioned within the depth value display in the location defined view. The default is 100mm.\nInput a value in the field to define the elements that display in the view, measured from the location plane. All elements that are positioned within the depth value display in the location defined view. The default is 100mm.\nInput a value in the field to modify the location plane. Only a location plane along the same orientation can be used.\nThe location plane value determines the location orientation for the view. It also determines an initial box for the view limits.\nLocation planes based on physical planes can be used for any model element with POS, ORI and WVOL (considered with respect to the world).\nLocation planes based on frame positions (for example, FR23) refer to a GRIDPL element that behaves like a model element when it comes to POS, ORI and WVOL.\nLocation planes based on coordinate values, for example, POS and ORI (direction) are implicitly defined by the coordinate value (for example, X=1000 where POS=1000,0,0 and DIR=X). The enclosing box volume is defined by the WVOL for the closest GRIDPL.\nInput a value in the field or select from the drop-down list to modify the view orientation. Only a view orientation along the same plane can be used. For example a view in the X orientation can be modified to -X.\n\nAdvanced view type\nDisplays the view type. By default, the field is populated with Location Defined. The view type cannot be modified.\nDepth Behind\nInput a value in the field to define the elements that display in the view, measured from the location plane. All elements that are positioned within the depth value display in the location defined view. The default is 100mm.\nDepth in Front\nInput a value in the field to define the elements that display in the view, measured from the location plane. All elements that are positioned within the depth value display in the location defined view. The default is 100mm.\nLocation Plane\nInput a value in the field to modify the location plane. Only a location plane along the same orientation can be used.\nThe location plane value determines the location orientation for the view. It also determines an initial box for the view limits.\nLocation planes based on physical planes can be used for any model element with POS, ORI and WVOL (considered with respect to the world).\nThe POS serves as a basis for the depth.\nThe ORI serves as a basis for the initial view direction.\nThe enclosing box volume (WVOL) is retrieved from the model element that serves as a basis for the location.\nLocation planes based on frame positions (for example, FR23) refer to a GRIDPL element that behaves like a model element when it comes to POS, ORI and WVOL.\nLocation planes based on coordinate values, for example, POS and ORI (direction) are implicitly defined by the coordinate value (for example, X=1000 where POS=1000,0,0 and DIR=X). The enclosing box volume is defined by the WVOL for the closest GRIDPL.\nOrientation\nInput a value in the field or select from the drop-down list to modify the view orientation. Only a view orientation along the same plane can be used. For example a view in the X orientation can be modified to -X.\nThe POS serves as a basis for the depth.\nThe ORI serves as a basis for the initial view direction.\nThe enclosing box volume (WVOL) is retrieved from the model element that serves as a basis for the location.\nThe POS serves as a basis for the depth.\nThe POS serves as a basis for the depth.\nThe ORI serves as a basis for the initial view direction.\nThe ORI serves as a basis for the initial view direction.\nThe enclosing box volume (WVOL) is retrieved from the model element that serves as a basis for the location.\nThe enclosing box volume (WVOL) is retrieved from the model element that serves as a basis for the location.\n\n\n\nFormat 2D View\nProperties\nFormat 2D\nFormat 2D View\nProperties\nProperties\nAdvanced view type\nLocation Defined\nDepth Behind\nDepth in Front\nLocation Plane\nOrientation\nX\n-X"}
{"Headers": "Modify Multi-Location View", "Content": "A multi-location view can be modified using the Format 2D tab (refer to Format 2D View for further information). Additional modification options are available using the Properties window. Refer to Properties for further information.\n\nAdvanced view type\nDisplays the view type. By default, the field is populated with Multi-Location. The view type cannot be modified.\nDepth Behind\nInput a value in the field to define the elements that display in the view, measured from each location plane. All elements that are positioned within the depth value display in the multi-location view. The default is 100mm.\nDepth in Front\nInput a value in the field to define the elements that display in the view, measured from each location plane. All elements that are positioned within the depth value display in the multi-location view. The default is 100mm.\nLocation Plane\nInput a value in the field to modify a location plane.\nThe first location plane value determines the location orientation for the view and all subsequent planes must have the same orientation. It also determines an initial box for the view limits. The view limits box is then enlarged to encompass the other location planes.\nLocation planes based on physical planes can be used for any model element with POS, ORI and WVOL (considered with respect to the world).\nThe POS serves as a basis for the depth.\nThe ORI serves as a basis for the initial view direction.\nThe enclosing box volume (WVOL) is retrieved from the model element that serves as a basis for the location.\nLocation planes based on frame positions (for example, FR23) refer to a GRIDPL element that behaves like a model element when it comes to POS, ORI and WVOL.\nLocation planes based on coordinate values, for example, POS and ORI (direction) are implicitly defined by the coordinate value (for example, X=1000 where POS=1000,0,0 and DIR=X). The enclosing box volume is defined by the WVOL for the closest GRIDPL.\nMore\nInput a value in the field to add a location plane. The location plane must have the same orientation as the existing location planes.\nOrientation\nInput a value in the field or select from the drop-down list to modify the view orientation. Only a view orientation along the same plane can be used. For example a view in the X orientation can be modified to -X.\nSurface\nDisplays the view surface which is defined when the multi-location view is created. The surface value cannot be modified.\nAdvanced view type\nDisplays the view type. By default, the field is populated with Multi-Location. The view type cannot be modified.\nInput a value in the field to define the elements that display in the view, measured from each location plane. All elements that are positioned within the depth value display in the multi-location view. The default is 100mm.\nInput a value in the field to define the elements that display in the view, measured from each location plane. All elements that are positioned within the depth value display in the multi-location view. The default is 100mm.\nInput a value in the field to modify a location plane.\nThe first location plane value determines the location orientation for the view and all subsequent planes must have the same orientation. It also determines an initial box for the view limits. The view limits box is then enlarged to encompass the other location planes.\nLocation planes based on physical planes can be used for any model element with POS, ORI and WVOL (considered with respect to the world).\nLocation planes based on frame positions (for example, FR23) refer to a GRIDPL element that behaves like a model element when it comes to POS, ORI and WVOL.\nLocation planes based on coordinate values, for example, POS and ORI (direction) are implicitly defined by the coordinate value (for example, X=1000 where POS=1000,0,0 and DIR=X). The enclosing box volume is defined by the WVOL for the closest GRIDPL.\nInput a value in the field to add a location plane. The location plane must have the same orientation as the existing location planes.\nInput a value in the field or select from the drop-down list to modify the view orientation. Only a view orientation along the same plane can be used. For example a view in the X orientation can be modified to -X.\nDisplays the view surface which is defined when the multi-location view is created. The surface value cannot be modified.\nView Limits\nThe view limits are derived from the location planes that serve as a basis for the locations and the depth, and is extended by 5%. This offset cannot be modified. The multi-location view is limits defined, which means the view holds the limits of what to display and does not depend on the implicit limits specified by the actual content of the ID list. Limit restriction on the view is essential for multi-location views that typically refer to ID lists with rule-based contents (based on element type) and not individual model elements. For rule-based ID lists, the limits derived from the content can, in the worst case, be the world.\nLimits on the view and limits on the ID list are maintained by the multi-location functionality to represent the actual collection of elements to be considered for the view. The view is then further reduced using the geometrical information of the section planes to define the multi-location view result.\nFor multi-location views based on a frame position (for example, FR23) or coordinate values (for example, X=1000), the extension of the view is, in some cases, clipped smaller than the ship extents. As a work around, you can manually adjust the section planes from which the clipping is derived.\nThe Lock View Frame to Limits property is initially set to No for multi-location views.\nID List\nThe ID list is specifically adjusted for multi-location views such that the limits applied on the view are applied not only on ID list (IDLI) but also on the members of ID list. The ID list is initially populated with the content selected during the creation operation, ID list entries can be added or removed using the Drawlist Manager. Refer to Define View Contents for further information.\nDetail Views created from a Multi-Location View\nIt is possible to create Detail Views from multi location views, all of the properties from the original view are inherited, the location planes cannot be changed.\nApplicable Elements for a Multi-Location View\nAny type of element can be used as a location provided that the position (POS) and orientation (ORI) are defined. If POS and ORI are among the attributes provided by ATTLIS, the element is a candidate. The ORI must be different from the Origin. Further, the element must be able to provide an extension box (by WVOL attribute) that has a zero area when intersected by the location plane (derived from POS and ORI).\nMulti-location View and Representation Style\nTo produce a multi-location view similar to a bodyplan view, the correct representation style must be applied. In the RRUL element, the Repstyle attribute must be set to SymbolicMultiLoc.\nWhen applied, the SymbolicMultiLoc repstyle will give intersections with each location plane. Multi-location representation can be applied to:\nOrdinary representation is the default representation. If a rule is not specifically set for multi-location representation, ordinary representation is applied.\nAdvanced view type\nDisplays the view type. By default, the field is populated with Multi-Location. The view type cannot be modified.\nDepth Behind\nInput a value in the field to define the elements that display in the view, measured from each location plane. All elements that are positioned within the depth value display in the multi-location view. The default is 100mm.\nDepth in Front\nInput a value in the field to define the elements that display in the view, measured from each location plane. All elements that are positioned within the depth value display in the multi-location view. The default is 100mm.\nLocation Plane\nInput a value in the field to modify a location plane.\nThe first location plane value determines the location orientation for the view and all subsequent planes must have the same orientation. It also determines an initial box for the view limits. The view limits box is then enlarged to encompass the other location planes.\nLocation planes based on physical planes can be used for any model element with POS, ORI and WVOL (considered with respect to the world).\nThe POS serves as a basis for the depth.\nThe ORI serves as a basis for the initial view direction.\nThe enclosing box volume (WVOL) is retrieved from the model element that serves as a basis for the location.\nLocation planes based on frame positions (for example, FR23) refer to a GRIDPL element that behaves like a model element when it comes to POS, ORI and WVOL.\nLocation planes based on coordinate values, for example, POS and ORI (direction) are implicitly defined by the coordinate value (for example, X=1000 where POS=1000,0,0 and DIR=X). The enclosing box volume is defined by the WVOL for the closest GRIDPL.\nMore\nInput a value in the field to add a location plane. The location plane must have the same orientation as the existing location planes.\nOrientation\nInput a value in the field or select from the drop-down list to modify the view orientation. Only a view orientation along the same plane can be used. For example a view in the X orientation can be modified to -X.\nSurface\nDisplays the view surface which is defined when the multi-location view is created. The surface value cannot be modified.\nThe POS serves as a basis for the depth.\nThe ORI serves as a basis for the initial view direction.\nThe enclosing box volume (WVOL) is retrieved from the model element that serves as a basis for the location.\nThe POS serves as a basis for the depth.\nThe POS serves as a basis for the depth.\nThe ORI serves as a basis for the initial view direction.\nThe ORI serves as a basis for the initial view direction.\nThe enclosing box volume (WVOL) is retrieved from the model element that serves as a basis for the location.\nThe enclosing box volume (WVOL) is retrieved from the model element that serves as a basis for the location.\nSurface (SRFSUR)\nBoundary/Limit (IBNDRY/ILIM)\nStiffener (ISTIFF)\nSurface (SRFSUR)\nSurface (SRFSUR)\nBoundary/Limit (IBNDRY/ILIM)\nBoundary/Limit (IBNDRY/ILIM)\nStiffener (ISTIFF)\nStiffener (ISTIFF)\n\n\n\nFormat 2D View\nProperties\nDefine View Contents\nFormat 2D\nFormat 2D View\nProperties\nProperties\nAdvanced view type\nMulti-Location\nDepth Behind\nDepth in Front\nLocation Plane\nMore\nOrientation\nX\n-X\nSurface\nView Limits\nLock View Frame to Limits\nNo\nID List\nDefine View Contents\nDetail Views created from a Multi-Location View\nApplicable Elements for a Multi-Location View\nMulti-location View and Representation Style\nRepstyle\nSymbolicMultiLoc"}
{"Headers": "Modify Expansion View", "Content": "An expansion view can be modified using the Format 2D tab (refer to Format 2D View for further information).\nWhen an expansion view is created, it must remain as an expansion view. An expansion view cannot be modified to any other view type. A new view must be created if an expansion view for another surface is required.\n\nAdvanced view type\nDisplays the view type. By default, the field is populated with Expansion. The view type cannot be modified.\nExpansion Direction\nDisplays the expansion direction which is defined when the expansion view is created. The expansion direction cannot be modified.\nMain Direction\nDisplays the main direction which is defined when the expansion view is created. The main direction cannot be modified.\nOrigin\nDisplays the origin which is defined when the expansion view is created. The origin cannot be modified.\nSurface\nDisplays the view surface which is defined when the expansion view is created. The surface value cannot be modified.\nAdvanced view type\nDisplays the view type. By default, the field is populated with Expansion. The view type cannot be modified.\nDisplays the expansion direction which is defined when the expansion view is created. The expansion direction cannot be modified.\nDisplays the main direction which is defined when the expansion view is created. The main direction cannot be modified.\nDisplays the origin which is defined when the expansion view is created. The origin cannot be modified.\nDisplays the view surface which is defined when the expansion view is created. The surface value cannot be modified.\nView Limits\nThe view limits are initially set to the limits of the selected surface and can be modified. The view limits affect the drawlist selection, only model elements fully or partially within the view limits are drawn.\nThe view limits are used for 3D clipping, only the parts of the model elements that are within the view limits will be unfolded. This avoids unfolding curves in a geometrically tricky part of the surface. This type of clipping is unique for the expansion view and is a substitute for section planes which are not available for expansion views.\nID List\nThe ID list is initially populated with the content selected during the creation operation, ID list entries can be added or removed using the Drawlist Manager. Refer to Define View Contents for further information.\nMulti-location View and Representation Style\nTo produce an expansion view, the correct representation style must be applied. In the RRUL element the Repstyle attribute must be set to Expansion.\nWhen applied, the SymbolicMultiLoc repstyle unfolds the curve representation of the model elements. Expansion representation can be applied to:\nThe model elements are unfolded if they have a relation to the expansion surface setup for the view, otherwise they are ignored.\nNote that if Expansion is setup for an element type (for example, an equipment element) that does not support this representation style it is not drawn. Drawing the element with ordinary representation in the view does work.\nView Type\nWhen the model elements in the expansion view are drawn with the Expansion representation style, the view type is irrelevant. The functionality to change the view type is not disabled, it could be relevant if model elements are drawn with the default representation style in the same view. This is probably a less common use case, but Draw does not inhibit such a view setup.\nAdvanced view type\nDisplays the view type. By default, the field is populated with Expansion. The view type cannot be modified.\nExpansion Direction\nDisplays the expansion direction which is defined when the expansion view is created. The expansion direction cannot be modified.\nMain Direction\nDisplays the main direction which is defined when the expansion view is created. The main direction cannot be modified.\nOrigin\nDisplays the origin which is defined when the expansion view is created. The origin cannot be modified.\nSurface\nDisplays the view surface which is defined when the expansion view is created. The surface value cannot be modified.\nCurve (CRMCUR)\nStiffener (ISTIFF)\nBoundary (IBNDRY)\nCurve Arrangement (FNCCAR)\nArea Arrangement (FNCAAR)\nCurve (CRMCUR)\nCurve (CRMCUR)\nStiffener (ISTIFF)\nStiffener (ISTIFF)\nBoundary (IBNDRY)\nBoundary (IBNDRY)\nCurve Arrangement (FNCCAR)\nCurve Arrangement (FNCCAR)\nArea Arrangement (FNCAAR)\nArea Arrangement (FNCAAR)\nNote:\nThe Perspective angle property cannot be modified for an expansion view.\n\n\n\nFormat 2D View\nDefine View Contents\nFormat 2D\nFormat 2D View\nAdvanced view type\nExpansion\nExpansion Direction\nMain Direction\nOrigin\nSurface\nNote\n:\nPerspective angle\nView Limits\nID List\nDefine View Contents\nMulti-location View and Representation Style\nRepstyle\nExpansion\nView Type"}
{"Headers": "Modify P-line Availability Property", "Content": "Sets the P-line availability property of a view.\nOn the list of available properties, select Yes from the P-Line Availability drop-down list to make all P-lines available for snapping when creating or modifying annotations for the view. This requires an update design to take effect (which may have a performance impact on update design and the size of the drawing in memory). Select No from the P-Line Availability drop-down list to make only MEML P-lines available for snapping. The choice of P-line can then be modified using the Property Grid.\n\n\n\nYes\nP-Line Availability\nNo\nP-Line Availability"}
{"Headers": "Format 2D View", "Content": "2D Views are formatted using the Format 2D tab. The tab only displays when a view is selected on a drawing sheet.\n\n\n\nProjection\nClick to display a drop-down list with the following options:\nAllows you to create an orthographic projection view of the objects in an existing 2D view, with a preview image of the view. Refer to Create Orthographic Projection View for further information.\nAllows you to create an orthographic projection view of the objects in an existing 2D view without a preview image of the view. Refer to Create Quick Projection View for further information.\nDetail\nAllows you to create a Detail view, which displays a selected area of an existing view. Refer to Create Detail View for further information.\nSection\nAllows you to create a section view, which is a simple section through an existing view. Refer to Create Section View for further information.\nQuick Section\nAllows you to create a section view, which is a simple section through an existing view, without a preview image of the view. Refer to Create Quick Section View for further information.\nSection Group\nDisplay\nClick to turn the display of section planes on or off. A shaded area indicates an area that is removed from the view.\nFunctionality is available to modify the section planes. Refer to Modify Section Plane using Grip Points for further information.\nCreate\nAllows you to create a section plane, an existing view can be modified to display only specific parts of it. Refer to Create 2D Section Planes for further information\nModify Cutting List\nAllows you to modify the drawlist for the view. Click to display the Drawlist Management window.\nRefer to Define View Contents for further information.\nSelect Cutting List\nEach section plane can be associated with a pre-defined cutting list, which is effectively a drawlist. Elements within the cutting list can be removed from the view, allowing for other elements to remain within the view even though a section plane exists. Refer to Apply Cutting List to Section Plane for further information.\nPick Section Plane\nClick to apply a cutting list to a section plane. Refer to Apply Cutting List to Section Plane for further information.\nOpen/Closed\nSelect from the drop-down list to define the shape of a section plane.\nSelect Open to define a section plane as an open ended shape. For example, an L shape consisting of two planes.\nSelect Closed to define a section plane as a closed shape. For example, a rectangle.\nGrid Group\nAnnotation\nAllows you to define the display of reference grid annotations for the view. Refer to Reference Grid Annotations for further information.\nModify Group\nEdit in 3D\nClick to display a view in the 3D window and display the Format 3D tab. Refer to The 3D View and Format 3D Tab for further information.\nView Limits\nAllows you to define the view limits by supplying coordinates that define a 3D box. Refer to Modify View Limits for further information.\nMatchlines\nClick to turn the display of matchlines on or off.\nScale Group\nType\nAllows you to set the type of scale for the view. Click to display a drop-down list with the following options:\nScale\nAllows you to select the scale for the view.\nClick to display a drop-down list with the available options. The available options are determined by the selected scale type.\nSelect Auto to re-center the model geometry contained by the view and select the best-fit predefined scale to display the model within the view frame.\nDirection Group\nDown\nAllows you to set the view direction.\nClick to display a drop-down list with the following options:\nDirection\nDisplays coordinates and indicates the current view direction. For example, D for down or E for East, W 45 S 35.26 D for ISO 1. You can input values in the field to specify the view direction. The field can be modified.\nRotation\nDisplays the current view angle. The field can be modified.\nRepresentation Styles Group\nView Type\nAllows you to select the view type. Click to display a drop-down list with the following options:\nStyle\nAllows you to select a discipline specific view style.\nClick to display a drop-down list with the available options.\nFor example, select PIPE+PIPEINSUL-Solid from the drop-down list to display pipe insulation as a solid line. Alternatively, select PIPE+PIPEINSUL-Dashed from the drop-down list to display pipe insulation as a dashed line.\nHatching Rule\nAllows you to select discipline specific view hatching.\nClick to display a drop-down list with the available options.\nFor example, select Hatch-Equip from the drop-down list to display hatching for equipment elements in the view.\nLocal Rules Group\nRepresentation\nAllows you to select and apply local view rules to items in the view's drawlist, overriding the selected discipline specific view style rules for those items. Refer to Create and Apply Local Rules for further information.\nHatching\nAllows you to select and apply local hatching rules to items in the view's drawlist, overriding the selected discipline specific hatching style rules for those items. Refer to Create and Apply Local Hatching Rules for further information.\nDrawlist Group\nManager\nAllows you to create, modify and populate drawlists. Refer to Define View Contents for further information.\nQuick Add\nAllows you to quickly and easily add model elements to selected views. Refer to Quick Add for further information.\nPoint Cloud Group\nDisplay\nClick to display a drop-down list with the following options:\nAllows you to define the display of laser data for the view. Refer to Laser Data for further information.\nLow density point laser data is laser survey data that has not been defined as detailed laser data. Refer to Detail Laser Data for further information.\nClick to remove low density point laser data from the view.\nRepeat the command to add low density point laser data to the view\nUpdate Group\nCurrent Owner\nUsed to manually update the current owner with any database or settings changes.\n\nView Group\nProjection\nClick to display a drop-down list with the following options:\nProjection\nAllows you to create an orthographic projection view of the objects in an existing 2D view, with a preview image of the view. Refer to Create Orthographic Projection View for further information.\nQuick Projection\nAllows you to create an orthographic projection view of the objects in an existing 2D view without a preview image of the view. Refer to Create Quick Projection View for further information.\nDetail\nAllows you to create a Detail view, which displays a selected area of an existing view. Refer to Create Detail View for further information.\nSection\nAllows you to create a section view, which is a simple section through an existing view. Refer to Create Section View for further information.\nQuick Section\nAllows you to create a section view, which is a simple section through an existing view, without a preview image of the view. Refer to Create Quick Section View for further information.\nSection Group\nDisplay\nClick to turn the display of section planes on or off. A shaded area indicates an area that is removed from the view.\nFunctionality is available to modify the section planes. Refer to Modify Section Plane using Grip Points for further information.\nCreate\nAllows you to create a section plane, an existing view can be modified to display only specific parts of it. Refer to Create 2D Section Planes for further information\nModify Cutting List\nAllows you to modify the drawlist for the view. Click to display the Drawlist Management window.\nNote:\nThe functionality is not available for hull views.\nRefer to Define View Contents for further information.\nSelect Cutting List\nEach section plane can be associated with a pre-defined cutting list, which is effectively a drawlist. Elements within the cutting list can be removed from the view, allowing for other elements to remain within the view even though a section plane exists. Refer to Apply Cutting List to Section Plane for further information.\nPick Section Plane\nClick to apply a cutting list to a section plane. Refer to Apply Cutting List to Section Plane for further information.\nOpen/Closed\nSelect from the drop-down list to define the shape of a section plane.\nSelect Open to define a section plane as an open ended shape. For example, an L shape consisting of two planes.\nSelect Closed to define a section plane as a closed shape. For example, a rectangle.\nGrid Group\nAnnotation\nAllows you to define the display of reference grid annotations for the view. Refer to Reference Grid Annotations for further information.\nModify Group\nEdit in 3D\nClick to display a view in the 3D window and display the Format 3D tab. Refer to The 3D View and Format 3D Tab for further information.\nView Limits\nAllows you to define the view limits by supplying coordinates that define a 3D box. Refer to Modify View Limits for further information.\nMatchlines\nClick to turn the display of matchlines on or off.\nScale Group\nType\nAllows you to set the type of scale for the view. Click to display a drop-down list with the following options:\nArchitectural\nEngineering\nMetric\nScale\nAllows you to select the scale for the view.\nClick to display a drop-down list with the available options. The available options are determined by the selected scale type.\nSelect Auto to re-center the model geometry contained by the view and select the best-fit predefined scale to display the model within the view frame.\nNote:\nFor limits defined views with the lock view frame to limits functionality enabled, changing the scale also changes the size of the view. Refer to Modify View Limits for further information.\nDirection Group\nDown\nAllows you to set the view direction.\nClick to display a drop-down list with the following options:\nDown\nUp\nEast\nWest\nNorth\nSouth\nIso 1\nIso 2\nIso 3\nIso 4\nDirection\nDisplays coordinates and indicates the current view direction. For example, D for down or E for East, W 45 S 35.26 D for ISO 1. You can input values in the field to specify the view direction. The field can be modified.\nRotation\nDisplays the current view angle. The field can be modified.\nRepresentation Styles Group\nView Type\nAllows you to select the view type. Click to display a drop-down list with the following options:\nGlobal\nLocal\nModel Wireline\nUniversal\nWireline\nWireline Hidden\nStyle\nAllows you to select a discipline specific view style.\nClick to display a drop-down list with the available options.\nFor example, select PIPE+PIPEINSUL-Solid from the drop-down list to display pipe insulation as a solid line. Alternatively, select PIPE+PIPEINSUL-Dashed from the drop-down list to display pipe insulation as a dashed line.\nHatching Rule\nAllows you to select discipline specific view hatching.\nClick to display a drop-down list with the available options.\nFor example, select Hatch-Equip from the drop-down list to display hatching for equipment elements in the view.\nLocal Rules Group\nRepresentation\nAllows you to select and apply local view rules to items in the view's drawlist, overriding the selected discipline specific view style rules for those items. Refer to Create and Apply Local Rules for further information.\nHatching\nAllows you to select and apply local hatching rules to items in the view's drawlist, overriding the selected discipline specific hatching style rules for those items. Refer to Create and Apply Local Hatching Rules for further information.\nDrawlist Group\nManager\nAllows you to create, modify and populate drawlists. Refer to Define View Contents for further information.\nQuick Add\nAllows you to quickly and easily add model elements to selected views. Refer to Quick Add for further information.\nPoint Cloud Group\nDisplay\nClick to display a drop-down list with the following options:\nDisplay\nAllows you to define the display of laser data for the view. Refer to Laser Data for further information.\nLow Density Points\nLow density point laser data is laser survey data that has not been defined as detailed laser data. Refer to Detail Laser Data for further information.\nClick to remove low density point laser data from the view.\nRepeat the command to add low density point laser data to the view\nUpdate Group\nCurrent Owner\nUsed to manually update the current owner with any database or settings changes.\nNote:\nSuch changes are automatically applied if is set on the Status Bar.\nArchitectural\nEngineering\nMetric\nArchitectural\nArchitectural\nEngineering\nEngineering\nMetric\nMetric\nDown\nUp\nEast\nWest\nNorth\nSouth\nIso 1\nIso 2\nIso 3\nIso 4\nDown\nDown\nUp\nUp\nEast\nEast\nWest\nWest\nNorth\nNorth\nSouth\nSouth\nIso 1\nIso 1\nIso 2\nIso 2\nIso 3\nIso 3\nIso 4\nIso 4\nGlobal\nLocal\nModel Wireline\nUniversal\nWireline\nWireline Hidden\nGlobal\nGlobal\nLocal\nLocal\nModel Wireline\nModel Wireline\nUniversal\nUniversal\nWireline\nWireline\nWireline Hidden\nWireline Hidden\nNote:\nThe functionality is not available for hull views.\nNote:\nFor limits defined views with the lock view frame to limits functionality enabled, changing the scale also changes the size of the view. Refer to Modify View Limits for further information.\nNote:\nSuch changes are automatically applied if is set on the Status Bar.\n\n\n\nCreate Orthographic Projection View\nCreate Quick Projection View\nCreate Detail View\nCreate Section View\nCreate Quick Section View\nModify Section Plane using Grip Points\nCreate 2D Section Planes\nDefine View Contents\nApply Cutting List to Section Plane\nApply Cutting List to Section Plane\nReference Grid Annotations\nThe 3D View\nFormat 3D Tab\nModify View Limits\nModify View Limits\nCreate and Apply Local Rules\nCreate and Apply Local Hatching Rules\nDefine View Contents\nQuick Add\nLaser Data\nDetail Laser Data\nStatus Bar\nProjection\nProjection\nCreate Orthographic Projection View\nQuick Projection\nCreate Quick Projection View\nDetail\nCreate Detail View\nSection\nCreate Section View\nQuick Section\nCreate Quick Section View\nSection Group\nDisplay\nModify Section Plane using Grip Points\nCreate\nCreate 2D Section Planes\nModify Cutting List\nDrawlist Management\nNote\n:\nDefine View Contents\nSelect Cutting List\nApply Cutting List to Section Plane\nPick Section Plane\nApply Cutting List to Section Plane\nOpen/Closed\nOpen\nClosed\nGrid Group\nAnnotation\nReference Grid Annotations\nModify Group\nEdit in 3D\nThe 3D View\nFormat 3D Tab\nView Limits\nModify View Limits\nMatchlines\nScale Group\nType\nScale\nAuto\nNote\n:\nModify View Limits\nDirection Group\nDown\nDirection\nRotation\nRepresentation Styles Group\nView Type\nStyle\nPIPE+PIPEINSUL-Solid\nPIPE+PIPEINSUL-Dashed\nHatching Rule\nHatch-Equip\nLocal Rules Group\nRepresentation\nCreate and Apply Local Rules\nHatching\nCreate and Apply Local Hatching Rules\nDrawlist Group\nManager\nDefine View Contents\nQuick Add\nQuick Add\nPoint Cloud Group\nDisplay\nDisplay\nLaser Data\nLow Density Points\nDetail Laser Data\nUpdate Group\nCurrent Owner\nNote\n:\nStatus Bar"}
{"Headers": "Create 2D Section Planes", "Content": "Displays specific parts of an existing view.\nSection planes can also be created using facilities on the Format 3D tab.Refer to Create 3D Section Planes for further information.\n\n\n\nCreate 3D Section Planes\nCreate 3D Section Planes"}
{"Headers": "Apply Cutting List to Section Plane", "Content": "Each section plane can be associated with a pre-defined cutting list. Elements within the cutting list are removed from the view, allowing for other elements to remain in the view even though a section plane exists.\nCutting lists, which are effectively drawlists, are pre-defined by the administrator.\nSelect a cutting list from the Select Cutting List drop-down list.\n\nClick Pick Section Plane to associate a cutting list with a section plane.\nYou are prompted to Select section\nClick to identify the section plane to associate with the cutting list.\nThe prompt is repeated allowing you to associate multiple section planes with the cutting list.\nPress ESC to end the command. The cutting list is associated with the identified section planes.\nWhen the cutting list associations are complete. It may be necessary to manually update the view to display the modifications. Refer to Format 2D View for further information.\nThe example indicates a view that contains piping and equipment elements. The piping elements are contained within the cutting list and removed from the view using a section plane. The equipment elements are ignored by the section plane and remain within the view.\n\n\n\n\nFormat 2D View\nSelect Cutting List\nPick Section Plane\nSelect section\nESC\nFormat 2D View"}
{"Headers": "Reference Grid Annotations", "Content": "Sets the display properties and visual style of reference grid annotations.\nWhen a view is created that contains a reference grid within the drawlist, the view displays the reference grid annotations. The appearance of the reference grid annotations are inherited from the View Visual Style which is pre-defined by the administrator.\nLabels and dimensions are generated automatically for grid planes that are not perpendicular to the plane of the view (these appear as a single line when drawn). If all the grid planes in the view are perpendicular to the view plane, then a sub-set of the annotations is generated.\nReference Grid (REFGRD, GRIDEL, GRIDFA, GRIDPL, GRIDCY) elements may be added to an IDList and can be the sole element, they are added in the same way as other 3D model elements. REFGRD elements may or may not extend to the view boundary. AUTO commands function with REFGRD elements in the same way as other 3D model elements when calculating the VSCA and THPOS attributes of the VIEW.\n\nWhen a grid is rotated with respect to the view, the label text follows the angle of the leader line (rather than being horizontal). For readability, the text is constrained to lie between -89 and 90 degrees (measured clockwise from the horizontal).\n\nReference grid annotations can be added and removed from the view, dependent on the side of the view that the annotations are positioned.\nSelect a view that contains reference grid annotations, on the Format 2D tab, in the Grids group, click Annotations to remove the grid annotations from all sides of the view. Repeat the command to display the grid annotations on all sides of the view.\nThe Annotations drop-down list allows you to individually define the display options for the reference grid annotations on each side of the view.\nLeft\nSelect from the drop-down list to remove the grid annotations from the left side of the view. Repeat the command to display the grid annotations on the left side of the view.\nRight\nSelect from the drop-down list to remove the grid annotations from the right side of the view. Repeat the command to display the grid annotations on the right side of the view.\nTop\nSelect from the drop-down list to remove the grid annotations from the top of the view. Repeat the command to display the grid annotations on the top of the view.\nBottom\nSelect from the drop-down list to remove the grid annotations from the bottom of the view. Repeat the command to display the grid annotations on the bottom of the view.\n\nLeft\nSelect from the drop-down list to remove the grid annotations from the left side of the view. Repeat the command to display the grid annotations on the left side of the view.\n\nRight\nSelect from the drop-down list to remove the grid annotations from the right side of the view. Repeat the command to display the grid annotations on the right side of the view.\n\nTop\nSelect from the drop-down list to remove the grid annotations from the top of the view. Repeat the command to display the grid annotations on the top of the view.\n\nBottom\nSelect from the drop-down list to remove the grid annotations from the bottom of the view. Repeat the command to display the grid annotations on the bottom of the view.\nThe reference grid annotation properties of a view can be modified to alter the display using the Properties window. Refer to Properties for further information.\n\nThe visual style property and grid annotation properties can be modified to define the display of the reference grid annotations.\nVisual Style\nSelect from the drop-down list to modify the visual style for the view.\nGrid annotation\nSelect By Style from the drop-down list to inherit the annotation offset position from the selected visual style.\nSelect Yes from the drop-down list to position the annotation offset from the attached grid line p-point.\nSelect No from the drop-down list to position the annotations offset from the view frame.\nLabel offset\nSelect By Style from the drop-down list to inherit the annotation offset distance from the selected visual style.\nInput a dimensional value in the field or select a distance from the drop-down list to modify the distance between the attached p-point and the annotation.\nDimension offset\nSelect By Style from the drop-down list to inherit the dimension offset distance from the selected visual style.\nInput a dimensional value in the field or select a distance from the drop-down list to modify the distance between the attached p-point and the dimension line.\nClosing dimensions\nSelect By Style from the drop-down list to inherit the annotation closing dimension settings from the selected visual style.\nSelect No from the drop-down list to define that dimension lines from the view frame to the first and last gridline do not display.\nSelect Yes from the drop-down list to display dimension lines from the view frame to the first and last gridline.\nOverall dimensions\nSelect By Style from the drop-down list to inherit the annotation overall dimension settings from the selected visual style.\nSelect No from the drop-down list to define that overall dimension lines from the first to last gridline do not display.\nSelect Yes from the drop-down list to display overall dimension lines from the first to last gridline.\nOverall dimension offset\nSelect By Style from the drop-down list to inherit the overall dimension offset distance from the selected visual style.\nInput a dimensional value in the field or select a distance from the drop-down list to modify the distance between the attached p-point and the overall dimension line.\nVertical dimensions\nSelect By Style from the drop-down list to inherit the vertical dimension settings from the selected visual style.\nSelect No from the drop-down list to define that vertical dimension lines between the elevation gridlines do not display.\nSelect Yes from the drop-down list to display vertical dimension lines between the elevation gridlines\nSides\nAllows you to individually define the display options for the reference grid annotations on each side of the view.\nInput a value in the field to define the display options for the reference grid annotations on each side of the view.\nFor an orthogonal view, you can define the annotation display for Top, Bottom, Left, Right, None, All.\nFor example, input Right Bottom to display reference grid annotations on the right and bottom of the view.\nFor a non-orthogonal view, you can define the annotation display for Left, TopLeft, TopRight, Right, BottomRight, BottomLeft, None, All.\nFor example, input Right Bottom BottomLeft BottomRight to display reference grid annotations on the right, bottom, bottom left and bottom right of the view.\nGrid annotation mode\nAllows you to modify the display of reference grid annotations.\nSelect Off from the drop-down list to define that reference grid annotations do not display.\nSelect Labels from the drop-down list to display only labels.\nSelect Dimensions from the drop-down list to display only dimensions.\nSelect All from the drop-down list to display both labels and dimensions\nSelect By Style from the drop-down list to inherit the reference grid annotation settings from the selected visual style.\nFace label template\nAllows you to modify the template used to define the display of grid reference annotations on the X and Y axis.\nClick to display the Select window.\nYou can browse and select the required template.\nClick Select to apply the selected template.\nClick Cancel to discard any changes and close the Select window.\nElev label template\nAllows you to modify the template used to define the display of grid reference annotations on the Z axis.\nThe functionality of the Elev label template is identical to the Face label template field. Refer to Face label template for further information.\nElev label style\nSelect from the drop down list to modify the visual style used for labels on the Z axis.\nElev label style\nSelect from the drop down list to modify the visual style used for labels on the X and Y axis.\nDimension style\nSelect from the drop down list to modify the visual style used for dimensions.\nVisual Style\nSelect from the drop-down list to modify the visual style for the view.\nGrid annotation\nSelect By Style from the drop-down list to inherit the annotation offset position from the selected visual style.\nSelect Yes from the drop-down list to position the annotation offset from the attached grid line p-point.\n\nSelect No from the drop-down list to position the annotations offset from the view frame.\n\nLabel offset\nSelect By Style from the drop-down list to inherit the annotation offset distance from the selected visual style.\nInput a dimensional value in the field or select a distance from the drop-down list to modify the distance between the attached p-point and the annotation.\nDimension offset\nSelect By Style from the drop-down list to inherit the dimension offset distance from the selected visual style.\nInput a dimensional value in the field or select a distance from the drop-down list to modify the distance between the attached p-point and the dimension line.\nClosing dimensions\nSelect By Style from the drop-down list to inherit the annotation closing dimension settings from the selected visual style.\nSelect No from the drop-down list to define that dimension lines from the view frame to the first and last gridline do not display.\nSelect Yes from the drop-down list to display dimension lines from the view frame to the first and last gridline.\n\nOverall dimensions\nSelect By Style from the drop-down list to inherit the annotation overall dimension settings from the selected visual style.\nSelect No from the drop-down list to define that overall dimension lines from the first to last gridline do not display.\nSelect Yes from the drop-down list to display overall dimension lines from the first to last gridline.\n\nOverall dimension offset\nSelect By Style from the drop-down list to inherit the overall dimension offset distance from the selected visual style.\nInput a dimensional value in the field or select a distance from the drop-down list to modify the distance between the attached p-point and the overall dimension line.\nVertical dimensions\nSelect By Style from the drop-down list to inherit the vertical dimension settings from the selected visual style.\nSelect No from the drop-down list to define that vertical dimension lines between the elevation gridlines do not display.\nSelect Yes from the drop-down list to display vertical dimension lines between the elevation gridlines\n\nSides\nAllows you to individually define the display options for the reference grid annotations on each side of the view.\nInput a value in the field to define the display options for the reference grid annotations on each side of the view.\nFor an orthogonal view, you can define the annotation display for Top, Bottom, Left, Right, None, All.\nFor example, input Right Bottom to display reference grid annotations on the right and bottom of the view.\n\nFor a non-orthogonal view, you can define the annotation display for Left, TopLeft, TopRight, Right, BottomRight, BottomLeft, None, All.\nFor example, input Right Bottom BottomLeft BottomRight to display reference grid annotations on the right, bottom, bottom left and bottom right of the view.\n\nGrid annotation mode\nAllows you to modify the display of reference grid annotations.\nSelect Off from the drop-down list to define that reference grid annotations do not display.\nSelect Labels from the drop-down list to display only labels.\nSelect Dimensions from the drop-down list to display only dimensions.\nSelect All from the drop-down list to display both labels and dimensions\nSelect By Style from the drop-down list to inherit the reference grid annotation settings from the selected visual style.\nFace label template\nAllows you to modify the template used to define the display of grid reference annotations on the X and Y axis.\nClick to display the Select window.\n\nYou can browse and select the required template.\nClick Select to apply the selected template.\nClick Cancel to discard any changes and close the Select window.\nElev label template\nAllows you to modify the template used to define the display of grid reference annotations on the Z axis.\nThe functionality of the Elev label template is identical to the Face label template field. Refer to Face label template for further information.\nElev label style\nSelect from the drop down list to modify the visual style used for labels on the Z axis.\nElev label style\nSelect from the drop down list to modify the visual style used for labels on the X and Y axis.\nDimension style\nSelect from the drop down list to modify the visual style used for dimensions.\nWhen the reference grid annotation modifications are complete. It may be necessary to update the view. Refer to Update and Regenerate Reference Grid Annotations for further information.\nLeft\nSelect from the drop-down list to remove the grid annotations from the left side of the view. Repeat the command to display the grid annotations on the left side of the view.\nRight\nSelect from the drop-down list to remove the grid annotations from the right side of the view. Repeat the command to display the grid annotations on the right side of the view.\nTop\nSelect from the drop-down list to remove the grid annotations from the top of the view. Repeat the command to display the grid annotations on the top of the view.\nBottom\nSelect from the drop-down list to remove the grid annotations from the bottom of the view. Repeat the command to display the grid annotations on the bottom of the view.\nVisual Style\nSelect from the drop-down list to modify the visual style for the view.\nGrid annotation\nSelect By Style from the drop-down list to inherit the annotation offset position from the selected visual style.\nSelect Yes from the drop-down list to position the annotation offset from the attached grid line p-point.\nSelect No from the drop-down list to position the annotations offset from the view frame.\nLabel offset\nSelect By Style from the drop-down list to inherit the annotation offset distance from the selected visual style.\nInput a dimensional value in the field or select a distance from the drop-down list to modify the distance between the attached p-point and the annotation.\nDimension offset\nSelect By Style from the drop-down list to inherit the dimension offset distance from the selected visual style.\nInput a dimensional value in the field or select a distance from the drop-down list to modify the distance between the attached p-point and the dimension line.\nClosing dimensions\nSelect By Style from the drop-down list to inherit the annotation closing dimension settings from the selected visual style.\nSelect No from the drop-down list to define that dimension lines from the view frame to the first and last gridline do not display.\nSelect Yes from the drop-down list to display dimension lines from the view frame to the first and last gridline.\nOverall dimensions\nSelect By Style from the drop-down list to inherit the annotation overall dimension settings from the selected visual style.\nSelect No from the drop-down list to define that overall dimension lines from the first to last gridline do not display.\nSelect Yes from the drop-down list to display overall dimension lines from the first to last gridline.\nOverall dimension offset\nSelect By Style from the drop-down list to inherit the overall dimension offset distance from the selected visual style.\nInput a dimensional value in the field or select a distance from the drop-down list to modify the distance between the attached p-point and the overall dimension line.\nVertical dimensions\nSelect By Style from the drop-down list to inherit the vertical dimension settings from the selected visual style.\nSelect No from the drop-down list to define that vertical dimension lines between the elevation gridlines do not display.\nSelect Yes from the drop-down list to display vertical dimension lines between the elevation gridlines\nSides\nAllows you to individually define the display options for the reference grid annotations on each side of the view.\nInput a value in the field to define the display options for the reference grid annotations on each side of the view.\nFor an orthogonal view, you can define the annotation display for Top, Bottom, Left, Right, None, All.\nFor example, input Right Bottom to display reference grid annotations on the right and bottom of the view.\nFor a non-orthogonal view, you can define the annotation display for Left, TopLeft, TopRight, Right, BottomRight, BottomLeft, None, All.\nFor example, input Right Bottom BottomLeft BottomRight to display reference grid annotations on the right, bottom, bottom left and bottom right of the view.\nGrid annotation mode\nAllows you to modify the display of reference grid annotations.\nSelect Off from the drop-down list to define that reference grid annotations do not display.\nSelect Labels from the drop-down list to display only labels.\nSelect Dimensions from the drop-down list to display only dimensions.\nSelect All from the drop-down list to display both labels and dimensions\nSelect By Style from the drop-down list to inherit the reference grid annotation settings from the selected visual style.\nFace label template\nAllows you to modify the template used to define the display of grid reference annotations on the X and Y axis.\nClick to display the Select window.\nYou can browse and select the required template.\nClick Select to apply the selected template.\nClick Cancel to discard any changes and close the Select window.\nElev label template\nAllows you to modify the template used to define the display of grid reference annotations on the Z axis.\nThe functionality of the Elev label template is identical to the Face label template field. Refer to Face label template for further information.\nElev label style\nSelect from the drop down list to modify the visual style used for labels on the Z axis.\nElev label style\nSelect from the drop down list to modify the visual style used for labels on the X and Y axis.\nDimension style\nSelect from the drop down list to modify the visual style used for dimensions.\n\n\n\nProperties\nUpdate and Regenerate Reference Grid Annotations\nFormat 2D\nGrids\nAnnotations\nAnnotations\nLeft\nRight\nTop\nBottom\nProperties\nProperties\nVisual Style\nGrid annotation\nBy Style\nYes\nNo\nLabel offset\nBy Style\nDimension offset\nBy Style\nClosing dimensions\nBy Style\nNo\nYes\nOverall dimensions\nBy Style\nNo\nYes\nOverall dimension offset\nBy Style\nVertical dimensions\nBy Style\nNo\nYes\nSides\nTop\nBottom\nLeft\nRight\nNone\nAll\nRight Bottom\nLeft, TopLeft, TopRight, Right, BottomRight, BottomLeft, None, All\nRight Bottom BottomLeft BottomRight\nGrid annotation mode\nOff\nLabels\nDimensions\nAll\nBy Style\nFace label template\nSelect\nSelect\nCancel\nSelect\nElev label template\nFace label template\nFace label template\nElev label style\nElev label style\nDimension style\nUpdate and Regenerate Reference Grid Annotations"}
{"Headers": "Modify View Limits", "Content": "Sets the view limits by supplying coordinates that define a 3D box.\nView limits can bet set to draw the contents of a specified volume of the 3D model. The limits are defined as project coordinates, and are represented by the size of the view frame at the selected scale, although view frames and limits boxes can be unlinked. The view frame can include match lines with text that displays the coordinates of the view limits. If not otherwise set, the limits default to 0 0 0 and must be set either manually or using the Set from drop-down list.\n\nInput dimensional values in the From and To position fields to define the limits of the view explicitly. Refer to Coordinates for further information.\nSet from\nThe Set from drop-down list allows you to define the view limits using a specified source.\nDrawlist\nSelect from the drop-down list to set the limits of the view to the extremities of the drawlist members. The From and To fields are populated with the coordinates derived from the drawlist elements.\nElements\nSelect from the drop-down list to set the limits of the view using two picked elements.\nYou are prompted to Identify the first Design Element for the From limits\nClick to identify the first element of the view limits. The From fields are populated with the coordinates of the selected element.\nYou are then prompted to Identify the second Design Element for the To limits\nClick to identify the second element of the view limits. The To fields are populated with the coordinates of the selected element.\nCopy from view\nSelect from the drop-down list to set the limits of the view using a picked view.\nYou are prompted to Identify the VIEW that you wish to copy limits from\nClick to identify the view. The From and To fields are populated with the coordinates derived from the selected view.\nView volume\nSelect from the drop-down list to set the limits of the view using the view bounding volume.\nThe From and To fields are populated with the coordinates of the axis aligned bounding volume.\nView Frame\nClick to lock the view frame to the limits box for a limits-defined view. A blue background indicates that the view frame and limits box have been locked. Changing the view scale adjusts the view frame size accordingly.\nClick again to unlock the view frame from the limits box for a limits-defined view. A white background indicates that the view frame and limits box are independent of each other. Changing the view scale does not adjust the view frame size.\nThe example indicates a view frame and limits box that are independent of each other. The outer line is the view frame and match lines have been turned on to indicate the extent of the limits box.\nClear Limits\nClick to remove the limits from a view.\nSet from\nThe Set from drop-down list allows you to define the view limits using a specified source.\nSelect from the drop-down list to set the limits of the view to the extremities of the drawlist members. The From and To fields are populated with the coordinates derived from the drawlist elements.\nSelect from the drop-down list to set the limits of the view using two picked elements.\nYou are prompted to Identify the first Design Element for the From limits\nClick to identify the first element of the view limits. The From fields are populated with the coordinates of the selected element.\nYou are then prompted to Identify the second Design Element for the To limits\nClick to identify the second element of the view limits. The To fields are populated with the coordinates of the selected element.\nSelect from the drop-down list to set the limits of the view using a picked view.\nYou are prompted to Identify the VIEW that you wish to copy limits from\nClick to identify the view. The From and To fields are populated with the coordinates derived from the selected view.\nSelect from the drop-down list to set the limits of the view using the view bounding volume.\nThe From and To fields are populated with the coordinates of the axis aligned bounding volume.\nView Frame\nClick to lock the view frame to the limits box for a limits-defined view. A blue background indicates that the view frame and limits box have been locked. Changing the view scale adjusts the view frame size accordingly.\nClick again to unlock the view frame from the limits box for a limits-defined view. A white background indicates that the view frame and limits box are independent of each other. Changing the view scale does not adjust the view frame size.\nThe example indicates a view frame and limits box that are independent of each other. The outer line is the view frame and match lines have been turned on to indicate the extent of the limits box.\n\nClear Limits\nClick to remove the limits from a view.\nClick Apply to define the view limits or Cancel to discard any changes and close the Set View Limits window.\nSet from\nThe Set from drop-down list allows you to define the view limits using a specified source.\nDrawlist\nSelect from the drop-down list to set the limits of the view to the extremities of the drawlist members. The From and To fields are populated with the coordinates derived from the drawlist elements.\nElements\nSelect from the drop-down list to set the limits of the view using two picked elements.\nYou are prompted to Identify the first Design Element for the From limits\nClick to identify the first element of the view limits. The From fields are populated with the coordinates of the selected element.\nYou are then prompted to Identify the second Design Element for the To limits\nClick to identify the second element of the view limits. The To fields are populated with the coordinates of the selected element.\nCopy from view\nSelect from the drop-down list to set the limits of the view using a picked view.\nYou are prompted to Identify the VIEW that you wish to copy limits from\nClick to identify the view. The From and To fields are populated with the coordinates derived from the selected view.\nView volume\nSelect from the drop-down list to set the limits of the view using the view bounding volume.\nThe From and To fields are populated with the coordinates of the axis aligned bounding volume.\nView Frame\nClick to lock the view frame to the limits box for a limits-defined view. A blue background indicates that the view frame and limits box have been locked. Changing the view scale adjusts the view frame size accordingly.\nClick again to unlock the view frame from the limits box for a limits-defined view. A white background indicates that the view frame and limits box are independent of each other. Changing the view scale does not adjust the view frame size.\nThe example indicates a view frame and limits box that are independent of each other. The outer line is the view frame and match lines have been turned on to indicate the extent of the limits box.\nClear Limits\nClick to remove the limits from a view.\nNote:\n2D drawing sheets can be populated using the 3D view of the 3D model within Draw. Refer to The 3D View for further information.\n\n\n\nThe 3D View\nCoordinates\nSet from\nNote\nThe 3D View\nFrom\nTo\nCoordinates\nSet from\nSet from\nDrawlist\nFrom\nTo\nElements\nIdentify the first Design Element for the From limits\nFrom\nIdentify the second Design Element for the To limits\nTo\nCopy from view\nIdentify the VIEW that you wish to copy limits from\nFrom\nTo\nView volume\nFrom\nTo\nView Frame\nClear Limits\nApply\nCancel\nSet View Limits"}
{"Headers": "Define View Contents", "Content": "Defines the contents of a view using a drawlist. When a view is created, a new drawlist is automatically created at the same time.\n\nThe Drawlist Management window allows you to define the drawlist contents by compiling a list of selected elements and element rules. You can create, copy and delete drawlists, and associate a drawlist with a view. A drawlist can be modified by dragging and dropping model elements into a list of drawlist members from the Model Explorer or Draw Explorer.\nTo resize the Drawlist Management window, click a corner or side and drag the cursor to create a window of the required size.\nCollapse\nClick to resize the Drawlist Management window to the smallest possible size. Only the window name is visible.\nExpand\nClick to resize the Drawlist Management window to full size.\nClose\nClick to close the Drawlist Management window.\n\nCollapse\nClick to resize the Drawlist Management window to the smallest possible size. Only the window name is visible.\n\nExpand\nClick to resize the Drawlist Management window to full size.\n\nClose\nClick to close the Drawlist Management window.\nWhen the Drawlist Management window opens, the Drawlist Library and Drawlist drop-down lists are auto-populated with the data associated with the currently selected item:\nThe user default DLLB displays alongside any current DLLB.\n\nDrawlist Library\nSelect a drawlist library from the drop-down list.\nDrawlists\nDisplays the drawlists in the selected drawlist library.\nSelect a drawlist from the drop-down list.\nUpdate Form from Current View\nClick to populate the Drawlist Manager window with the drawlist settings for the currently selected view.\nIf a view is not currently selected, a Warning displays summarizing the problem.\nNew Drawlist\nAllows you to create a drawlist. Refer to Create Drawlist for further information.\nCreate Copy\nAllows you to create a copy of the currently selected drawlist within the same drawlist library.\nThe new drawlist is named with a Copy-of- prefix. The copy is then available for selection in the Drawlist drop-down list.\nDelete\nClick to delete the currently selected drawlist. A confirm window displays asking you to OK the deletion. Click Yes to delete the drawlist.\nAssociate to View\nClick to associate the currently selected drawlist with the currently selected view.\n\nDrawlist Library\nSelect a drawlist library from the drop-down list.\n\nDrawlists\nDisplays the drawlists in the selected drawlist library.\nSelect a drawlist from the drop-down list.\n\nUpdate Form from Current View\nClick to populate the Drawlist Manager window with the drawlist settings for the currently selected view.\nIf a view is not currently selected, a Warning displays summarizing the problem.\n\n\nNew Drawlist\nAllows you to create a drawlist. Refer to Create Drawlist for further information.\n\nCreate Copy\nAllows you to create a copy of the currently selected drawlist within the same drawlist library.\nThe new drawlist is named with a Copy-of- prefix. The copy is then available for selection in the Drawlist drop-down list.\n\nDelete\nClick to delete the currently selected drawlist. A confirm window displays asking you to OK the deletion. Click Yes to delete the drawlist.\n\nAssociate to View\nClick to associate the currently selected drawlist with the currently selected view.\nThe Limits Functions & Purpose part of the Drawlist Manager window allows you to set the drawlist limits and define a function and purpose for the drawlist.\n\nInput dimensional values in the From and To position fields to define the limits of the view explicitly. Refer to Coordinates for further information.\nFunction\nInput a value in the field to define the function for the drawlist.\nPurpose\nInput a value in the field to define a special purpose for the drawlist. The purpose value must be fewer than six characters and input using capital letters.\nSet Limits from Drawlist\nClick to set the limits of the view to a volume that encloses all items in the current drawlist.\nSet Limits from CE\nClick to set the limits of the view to the current element in the Model Explorer or IDLE element in the Draw Explorer.\nIf the CE is not a model element or an IDLE element, a Warning displays summarizing the problem.\nClear Limits\nClick to clear the limits defined for the view.\nLimits from View\nClick to set the drawlist limits using a selected view.\nYou are prompted to Select view\nClick to identify the view to create drawlist limits from.\n\nFunction\nInput a value in the field to define the function for the drawlist.\n\nPurpose\nInput a value in the field to define a special purpose for the drawlist. The purpose value must be fewer than six characters and input using capital letters.\n\nSet Limits from Drawlist\nClick to set the limits of the view to a volume that encloses all items in the current drawlist.\n\nSet Limits from CE\nClick to set the limits of the view to the current element in the Model Explorer or IDLE element in the Draw Explorer.\nIf the CE is not a model element or an IDLE element, a Warning displays summarizing the problem.\n\n\nClear Limits\nClick to clear the limits defined for the view.\n\nLimits from View\nClick to set the drawlist limits using a selected view.\nYou are prompted to Select view\nClick to identify the view to create drawlist limits from.\nThe list of drawlist members displays the elements and rules that are included in the drawlist.\n\nEach row represents an element (which may contain child elements) or a rule.\nAction\nIndicates if the element or rule is added or removed from the drawlist.\nMember\nDisplays the element name or the rule criterion to be evaluated.\nType\nIf the Member is an element, the column is populated with the element type. If the Member is a rule, the column is populated with Criteria.\nStatus\nIndicates the validity of the element or rule.\nIndicates that the element or rule is valid for the current drawlist.\nIndicates that the element or rule is not valid for the current drawlist.\nAction\nIndicates if the element or rule is added or removed from the drawlist.\nMember\nDisplays the element name or the rule criterion to be evaluated.\nType\nIf the Member is an element, the column is populated with the element type. If the Member is a rule, the column is populated with Criteria.\nStatus\nIndicates the validity of the element or rule.\nIndicates that the element or rule is valid for the current drawlist.\nIndicates that the element or rule is not valid for the current drawlist.\nThe bottom part of the Drawlist Manager window allows you to define the drawlist contents, update the associated view and save the drawlist.\n\nAdd CE\nClick to append an add action to the list of drawlist members using the currently selected element in the Model Explorer or Draw Explorer.\nAlternatively, drag the CE from the Model Explorer or Draw Explorer to the list of drawlist members.\nNote:\nOnly IDLIST elements can be added from the Draw Explorer.\nAdd Rule\nClick to append an add criterion based rule action to the list of drawlist members.\nInput a valid rule criterion into the Members column to define the selection.\nIf the rule criterion is not valid, a Warning displays summarizing the problem.\nAdd CE Within Limits\nClick to append an add action to the list of drawlist members using all child elements of the CE (in the Model Explorer) that are positioned within the defined drawlist limits.\nIf the drawlist limits are not defined, a Warning displays summarizing the problem.\nRemove CE\nClick to append a remove action to the list of drawlist members using the currently selected element in the Model Explorer or Draw Explorer.\nAlternatively, press SHIFT and drag the CE from the Model Explorer or Draw Explorer to the list of drawlist members.\nNote:\nOnly IDLIST elements can be removed from the Draw Explorer.\nRemove Rule\nClick to append a remove criterion based rule action to the list of drawlist members.\nInput a valid rule into the Members column to define the selection.\nIf the rule is not valid, a Warning displays summarizing the problem.\nCollections\nClick to display the Collections window. Repeat the command to close the Collections window.\nThe selected collection of elements can have an add action or remove action appended to the list of drawlist members using the Add CE or Remove CE options as required. Refer to Collections for further information.\nNote:\nTo prevent a conflict between different sources, all explorers must be closed when adding or removing collections.\nDelete Entry\nClick to delete the selected drawlist entry from the list of drawlist members. A Warning displays asking you to confirm the deletion.\nClean Up\nClick to remove all invalid entries from the list of drawlist members. Clean Up only becomes active if the list of drawlist members contains invalid entries.\nUpdate Design\nClick to clean up and save the drawlist, and update the associated view.\nSave Drawlist\nClick to clean up and save the drawlist.\n\nAdd CE\nClick to append an add action to the list of drawlist members using the currently selected element in the Model Explorer or Draw Explorer.\nAlternatively, drag the CE from the Model Explorer or Draw Explorer to the list of drawlist members.\n\nAdd Rule\nClick to append an add criterion based rule action to the list of drawlist members.\nInput a valid rule criterion into the Members column to define the selection.\nIf the rule criterion is not valid, a Warning displays summarizing the problem.\n\n\nAdd CE Within Limits\nClick to append an add action to the list of drawlist members using all child elements of the CE (in the Model Explorer) that are positioned within the defined drawlist limits.\nIf the drawlist limits are not defined, a Warning displays summarizing the problem.\n\n\nRemove CE\nClick to append a remove action to the list of drawlist members using the currently selected element in the Model Explorer or Draw Explorer.\nAlternatively, press SHIFT and drag the CE from the Model Explorer or Draw Explorer to the list of drawlist members.\n\nRemove Rule\nClick to append a remove criterion based rule action to the list of drawlist members.\nInput a valid rule into the Members column to define the selection.\nIf the rule is not valid, a Warning displays summarizing the problem.\n\n\nCollections\nClick to display the Collections window. Repeat the command to close the Collections window.\nThe selected collection of elements can have an add action or remove action appended to the list of drawlist members using the Add CE or Remove CE options as required. Refer to Collections for further information.\n\nDelete Entry\nClick to delete the selected drawlist entry from the list of drawlist members. A Warning displays asking you to confirm the deletion.\n\n\nClean Up\nClick to remove all invalid entries from the list of drawlist members. Clean Up only becomes active if the list of drawlist members contains invalid entries.\n\nUpdate Design\nClick to clean up and save the drawlist, and update the associated view.\n\nSave Drawlist\nClick to clean up and save the drawlist.\n\nCollapse\nClick to resize the Drawlist Management window to the smallest possible size. Only the window name is visible.\nExpand\nClick to resize the Drawlist Management window to full size.\nClose\nClick to close the Drawlist Management window.\nDrawlist Library\nSelect a drawlist library from the drop-down list.\nDrawlists\nDisplays the drawlists in the selected drawlist library.\nSelect a drawlist from the drop-down list.\nUpdate Form from Current View\nClick to populate the Drawlist Manager window with the drawlist settings for the currently selected view.\nIf a view is not currently selected, a Warning displays summarizing the problem.\nNew Drawlist\nAllows you to create a drawlist. Refer to Create Drawlist for further information.\nCreate Copy\nAllows you to create a copy of the currently selected drawlist within the same drawlist library.\nThe new drawlist is named with a Copy-of- prefix. The copy is then available for selection in the Drawlist drop-down list.\nDelete\nClick to delete the currently selected drawlist. A confirm window displays asking you to OK the deletion. Click Yes to delete the drawlist.\nAssociate to View\nClick to associate the currently selected drawlist with the currently selected view.\nFunction\nInput a value in the field to define the function for the drawlist.\nPurpose\nInput a value in the field to define a special purpose for the drawlist. The purpose value must be fewer than six characters and input using capital letters.\nSet Limits from Drawlist\nClick to set the limits of the view to a volume that encloses all items in the current drawlist.\nSet Limits from CE\nClick to set the limits of the view to the current element in the Model Explorer or IDLE element in the Draw Explorer.\nIf the CE is not a model element or an IDLE element, a Warning displays summarizing the problem.\nClear Limits\nClick to clear the limits defined for the view.\nLimits from View\nClick to set the drawlist limits using a selected view.\nYou are prompted to Select view\nClick to identify the view to create drawlist limits from.\nAction\nIndicates if the element or rule is added or removed from the drawlist.\nMember\nDisplays the element name or the rule criterion to be evaluated.\nType\nIf the Member is an element, the column is populated with the element type. If the Member is a rule, the column is populated with Criteria.\nStatus\nIndicates the validity of the element or rule.\nIndicates that the element or rule is valid for the current drawlist.\nIndicates that the element or rule is not valid for the current drawlist.\nAdd CE\nClick to append an add action to the list of drawlist members using the currently selected element in the Model Explorer or Draw Explorer.\nAlternatively, drag the CE from the Model Explorer or Draw Explorer to the list of drawlist members.\nNote:\nOnly IDLIST elements can be added from the Draw Explorer.\nAdd Rule\nClick to append an add criterion based rule action to the list of drawlist members.\nInput a valid rule criterion into the Members column to define the selection.\nIf the rule criterion is not valid, a Warning displays summarizing the problem.\nAdd CE Within Limits\nClick to append an add action to the list of drawlist members using all child elements of the CE (in the Model Explorer) that are positioned within the defined drawlist limits.\nIf the drawlist limits are not defined, a Warning displays summarizing the problem.\nRemove CE\nClick to append a remove action to the list of drawlist members using the currently selected element in the Model Explorer or Draw Explorer.\nAlternatively, press SHIFT and drag the CE from the Model Explorer or Draw Explorer to the list of drawlist members.\nNote:\nOnly IDLIST elements can be removed from the Draw Explorer.\nRemove Rule\nClick to append a remove criterion based rule action to the list of drawlist members.\nInput a valid rule into the Members column to define the selection.\nIf the rule is not valid, a Warning displays summarizing the problem.\nCollections\nClick to display the Collections window. Repeat the command to close the Collections window.\nThe selected collection of elements can have an add action or remove action appended to the list of drawlist members using the Add CE or Remove CE options as required. Refer to Collections for further information.\nNote:\nTo prevent a conflict between different sources, all explorers must be closed when adding or removing collections.\nDelete Entry\nClick to delete the selected drawlist entry from the list of drawlist members. A Warning displays asking you to confirm the deletion.\nClean Up\nClick to remove all invalid entries from the list of drawlist members. Clean Up only becomes active if the list of drawlist members contains invalid entries.\nUpdate Design\nClick to clean up and save the drawlist, and update the associated view.\nSave Drawlist\nClick to clean up and save the drawlist.\nIf the window is opened with a view currently selected, the information is gathered from the IDLN attribute. This takes precedence over all other selections.\nIf the window is opened with a DLLB element currently selected, the Drawlist Library drop-down list displays the selected DLLB, and the Drawlist drop-down list displays the first IDLI element under the DLLB element.\nIf the window is opened with an IDLI element currently selected, the Drawlist drop-down list displays the selected IDLI, and the Drawlist Library drop-down list displays the owning DLLB element.\nIf the IDLI element value is null in this case, the Drawlist drop-down list is blank. The Drawlist Library drop-down list only displays the user default DLLB (if one has been set up).\nIf the window is opened with a view currently selected, the information is gathered from the IDLN attribute. This takes precedence over all other selections.\nIf the window is opened with a view currently selected, the information is gathered from the IDLN attribute. This takes precedence over all other selections.\nIf the window is opened with a DLLB element currently selected, the Drawlist Library drop-down list displays the selected DLLB, and the Drawlist drop-down list displays the first IDLI element under the DLLB element.\nIf the window is opened with a DLLB element currently selected, the Drawlist Library drop-down list displays the selected DLLB, and the Drawlist drop-down list displays the first IDLI element under the DLLB element.\nIf the window is opened with an IDLI element currently selected, the Drawlist drop-down list displays the selected IDLI, and the Drawlist Library drop-down list displays the owning DLLB element.\nIf the IDLI element value is null in this case, the Drawlist drop-down list is blank. The Drawlist Library drop-down list only displays the user default DLLB (if one has been set up).\nIf the window is opened with an IDLI element currently selected, the Drawlist drop-down list displays the selected IDLI, and the Drawlist Library drop-down list displays the owning DLLB element.\nNote:\nOnly IDLIST elements can be added from the Draw Explorer.\nNote:\nOnly IDLIST elements can be removed from the Draw Explorer.\nNote:\nTo prevent a conflict between different sources, all explorers must be closed when adding or removing collections.\n\n\n\nCreate Drawlist\nCoordinates\nCollections\nDrawlist Management\nDrawlist Management\nDrawlist Management\nDrawlist Management\nDrawlist Management\nDrawlist Management\nDrawlist Library\nDrawlist\nDrawlist Library\nDrawlist\nDrawlist\nDrawlist Library\nDrawlist\nDrawlist Library\nDrawlist Library\nDrawlists\nUpdate Form from Current View\nDrawlist Manager\nNew Drawlist\nCreate Drawlist\nCreate Copy\nCopy-of-\nDrawlist\nDelete\nYes\nAssociate to View\nLimits Functions & Purpose\nDrawlist Manager\nFrom\nTo\nCoordinates\nFunction\nPurpose\nSet Limits from Drawlist\nSet Limits from CE\nClear Limits\nLimits from View\nSelect view\nAction\nMember\nType\nMember\nMember\nStatus\nDrawlist Manager\nAdd CE\nNote\n:\nAdd Rule\nMembers\nAdd CE Within Limits\nRemove CE\nSHIFT\nNote\n:\nRemove Rule\nMembers\nCollections\nCollections\nCollections\nAdd CE\nRemove CE\nCollections\nNote\n:\nDelete Entry\nClean Up\nClean Up\nUpdate Design\nSave Drawlist"}
{"Headers": "Quick Add", "Content": "Adds model elements to selected views.\n\nThe QuickAdd window allows you to highlight the currently selected views and define the model elements that are added to the views.\nThe QuickAdd window is populated using the currently selected views on the drawing canvas when opened.\nUpdate Form from Current Selection\nClick to update the QuickAdd window with the currently selected views on the drawing canvas.\nViews can be selected or deselected using a mouse click on the drawing canvas.\nHighlight Views\nClick and hold the left mouse button to highlight the currently selected views on the drawing canvas. The currently selected views display with a green outline on the drawing canvas.\nViews Selected\nDisplays the number of selected views and the view types. The available view options are:\nLocation Defined\nQuick View\nMulti-Location\nExpansion\nMixed type - more than one view type is selected.\n\nUpdate Form from Current Selection\nClick to update the QuickAdd window with the currently selected views on the drawing canvas.\nViews can be selected or deselected using a mouse click on the drawing canvas.\n\nHighlight Views\nClick and hold the left mouse button to highlight the currently selected views on the drawing canvas. The currently selected views display with a green outline on the drawing canvas.\n\n\nViews Selected\nDisplays the number of selected views and the view types. The available view options are:\nElement Selection\nThe Element Selection tab allows you to define the elements that are added to the views.\nDedicated Owner\nBy default, all elements of the selected element types are added to the drawlist. Select the Select Dedicated Owner check box to only add elements to the views which are member elements of a picked owning element.\nInput an element name in the field or click CE to define the owning element using a selected model element. The model element can be selected using the Model Explorer or the drawing canvas.\nElements\nSelect the required check boxes to define the element types that are added to the views.\nAlternatively, select the All Elements check box to add all element types to the views.\nVolume Criteria\nThe Volume Criteria tab allows you to define the area used to add elements to the views.\n\nGet volume from\nDefines the source volume that is used to add elements to the views.\nDrawlist\nAdds elements to the view using the volume of the current drawlist contents.\nView\nAdds elements to the views using the volume of the current view limits, if set.\nAdds elements to the views using the view contents/view volume, if the view limits are unset.\nModel element\nAdds elements to the views using the volume of a model element (the Current Element).\nUser Input\nInput dimensional values in the From and To position fields to define the limits of the volume box explicitly. Refer to Coordinates for further information.\nThe values are stored in the QuickAdd window until Refresh is clicked.\nDrawlist\nAdds elements to the view using the volume of the current drawlist contents.\nView\nAdds elements to the views using the volume of the current view limits, if set.\nAdds elements to the views using the view contents/view volume, if the view limits are unset.\nModel element\nAdds elements to the views using the volume of a model element (the Current Element).\nUser Input\nInput dimensional values in the From and To position fields to define the limits of the volume box explicitly. Refer to Coordinates for further information.\nThe values are stored in the QuickAdd window until Refresh is clicked.\nWholly and partially within\nSelect the option button to add all elements to the view which are contained wholly and partially within the volume box.\nWholly within\nSelect the option button to add all elements to the view which are contained wholly within the volume box.\nWithin shape\nSelect the option button to add all elements to the view which are contained wholly within the volume of the selected design element.\nUpdate Design\nClick to clean up and save the drawlist, and update the selected views.\nSave Drawlist\nClick to clean up and save the drawlist. The views are not updated but can be manually updated at a later time. Refer to Update for further information.\n\nUpdate Design\nClick to clean up and save the drawlist, and update the selected views.\n\nSave Drawlist\nClick to clean up and save the drawlist. The views are not updated but can be manually updated at a later time. Refer to Update for further information.\n\nUpdate Form from Current Selection\nClick to update the QuickAdd window with the currently selected views on the drawing canvas.\nViews can be selected or deselected using a mouse click on the drawing canvas.\nHighlight Views\nClick and hold the left mouse button to highlight the currently selected views on the drawing canvas. The currently selected views display with a green outline on the drawing canvas.\nViews Selected\nDisplays the number of selected views and the view types. The available view options are:\nLocation Defined\nQuick View\nMulti-Location\nExpansion\nMixed type - more than one view type is selected.\nDrawlist\nAdds elements to the view using the volume of the current drawlist contents.\nView\nAdds elements to the views using the volume of the current view limits, if set.\nAdds elements to the views using the view contents/view volume, if the view limits are unset.\nModel element\nAdds elements to the views using the volume of a model element (the Current Element).\nUser Input\nInput dimensional values in the From and To position fields to define the limits of the volume box explicitly. Refer to Coordinates for further information.\nThe values are stored in the QuickAdd window until Refresh is clicked.\nUpdate Design\nClick to clean up and save the drawlist, and update the selected views.\nSave Drawlist\nClick to clean up and save the drawlist. The views are not updated but can be manually updated at a later time. Refer to Update for further information.\nLocation Defined\nQuick View\nMulti-Location\nExpansion\nMixed type - more than one view type is selected.\nLocation Defined\nLocation Defined\nQuick View\nQuick View\nMulti-Location\nMulti-Location\nExpansion\nExpansion\nMixed type - more than one view type is selected.\nMixed type - more than one view type is selected.\nNote:\nThe functionality does not modify the scale or limits of the selected views. If the added elements are outside of the current view limits, they will not be visible. However, the view drawlist is updated accordingly and if you adjust the view scale or view limits correctly, the added elements become visible.\nNote:\nThe functionality is only available if Model element is the current source volume criteria.\n\n\n\nCoordinates\nUpdate\nNote\n:\nQuickAdd\nQuickAdd\nUpdate Form from Current Selection\nQuickAdd\nHighlight Views\nViews Selected\nElement Selection\nElement Selection\nDedicated Owner\nSelect Dedicated Owner\nCE\nElements\nAll Elements\nVolume Criteria\nVolume Criteria\nGet volume from\nDrawlist\nView\nModel element\nUser Input\nFrom\nTo\nCoordinates\nQuickAdd\nRefresh\nWholly and partially within\nWholly within\nWithin shape\nNote\n:\nModel element\nUpdate Design\nSave Drawlist\nUpdate"}
{"Headers": "Create and Apply Local Rules", "Content": "Creates local view rules and applies them to items in the view drawlist, overriding the selected discipline specific rules for those items.\n\nCE\nClick to identify the currently selected view as the working element.\nViews\nSelect a view for the sheet from the drop-down list.\nRules\nSelect a rule from the list.\nCreate\nAllows you to create a rule. Click to display the Create RRUL window.\nInput a name for the new rule in the Name field.\nClick OK to add the rule to the Rules list or Cancel to discard any changes and close the Create RRUL window.\nDelete\nClick to delete the currently selected rule from the Rules list.\nFor\nAllows you to specify the items that the rule is applied to.\nSelect the All option button and select the elements the rule is applied to from the drop-down list.\nSelect the Names option button and click Modify to display the Names window.\nWith\nTo apply qualifying restrictions to the elements specified in the For section, input an expression in the With field. For example, if the For section specifies Branches, the following can be input:\n(HBOR GT 100) AND (TBOR GT 80)\nmeaning 'Branches with HBOR greater than 100mm and TBOR greater than 80mm'.\nSymbology - Draw as Annotations\nSelect the check box to represent design items symbolically.\nHidden line removal\nSelect the check box to enable hidden line removal.\nStyle\nSelect the check box to associate the local rule with a representation style.\nStyles\nSelect a representation style library from the upper drop-down list.\nSelect a style from the lower list.\nPlease note that the SRLSTY special style type cannot be used with this window. If you attempt to use the SRLSTY style, an error message is displayed.\nThe SRLSTY special style type is used when setting up symbolic representation, refer to Symbolic Representation for further information.\nDisplay\nSelect from the drop-down list to define the display of representation styles in the Styles list.\nCE\nClick to identify the currently selected view as the working element.\nViews\nSelect a view for the sheet from the drop-down list.\nRules\nSelect a rule from the list.\nCreate\nAllows you to create a rule. Click to display the Create RRUL window.\n\nInput a name for the new rule in the Name field.\nClick OK to add the rule to the Rules list or Cancel to discard any changes and close the Create RRUL window.\nDelete\nClick to delete the currently selected rule from the Rules list.\nFor\nAllows you to specify the items that the rule is applied to.\nSelect the All option button and select the elements the rule is applied to from the drop-down list.\nSelect the Names option button and click Modify to display the Names window.\nWith\nTo apply qualifying restrictions to the elements specified in the For section, input an expression in the With field. For example, if the For section specifies Branches, the following can be input:\nmeaning 'Branches with HBOR greater than 100mm and TBOR greater than 80mm'.\nSymbology - Draw as Annotations\nSelect the check box to represent design items symbolically.\nHidden line removal\nSelect the check box to enable hidden line removal.\nStyle\nSelect the check box to associate the local rule with a representation style.\nStyles\nSelect a representation style library from the upper drop-down list.\nSelect a style from the lower list.\nPlease note that the SRLSTY special style type cannot be used with this window. If you attempt to use the SRLSTY style, an error message is displayed.\nThe SRLSTY special style type is used when setting up symbolic representation, refer to Symbolic Representation for further information.\nDisplay\nSelect from the drop-down list to define the display of representation styles in the Styles list.\nClick Apply to apply the local rules or Cancel to discard any changes and close the Local Rules window.\nNames\nSpecifies items by name that a rule is applied to.\n\nThe Names window allows you to select individual elements from the Members list and copy them to the Names list.\nThe Navigation drop-down menu allows you to select elements to display in the Members List.\n\nOwner\nSelect to navigate to the owning element of the currently selected element. The element is selected in the Members List.\nFirst\nSelect Element to navigate to the first element in the currently selected hierarchy. The element is selected in the Members List.\nSelect Member to navigate to the first member of the currently selected element. The element is selected in the Members List.\nLast\nSelect Element to navigate to the last element in the currently selected hierarchy. The element is selected in the Members List.\nSelect Member to navigate to the last member of the currently selected element. The element is selected in the Members List.\nSame\nSelect to navigate to the previously selected element. The element is selected in the Members List.\nClick to navigate to the previous element in the currently selected hierarchy. The element is selected in the Members List.\nClick to navigate to the next element in the currently selected hierarchy. The element is selected in the Members List.\nDesign Members / Drawlists\nThe Members list can display either design member elements or existing drawlists.\nSelect Design Members from the drop-down list to pick design elements explicitly.\nSelect Drawlists from the drop-down list to identify design elements by their presence in other drawlists.\nAdd\nClick to add the currently selected element in the Members List to the Names list.\nDelete Entry\nClick to delete the selected entry from the Names list.\nDelete All\nClick to delete all entries from the Names list.\nOwner\nSelect to navigate to the owning element of the currently selected element. The element is selected in the Members List.\nFirst\nSelect Element to navigate to the first element in the currently selected hierarchy. The element is selected in the Members List.\nSelect Member to navigate to the first member of the currently selected element. The element is selected in the Members List.\nLast\nSelect Element to navigate to the last element in the currently selected hierarchy. The element is selected in the Members List.\nSelect Member to navigate to the last member of the currently selected element. The element is selected in the Members List.\nSame\nSelect to navigate to the previously selected element. The element is selected in the Members List.\n\nClick to navigate to the previous element in the currently selected hierarchy. The element is selected in the Members List.\n\nClick to navigate to the next element in the currently selected hierarchy. The element is selected in the Members List.\nDesign Members / Drawlists\nThe Members list can display either design member elements or existing drawlists.\nSelect Design Members from the drop-down list to pick design elements explicitly.\nSelect Drawlists from the drop-down list to identify design elements by their presence in other drawlists.\nAdd\nClick to add the currently selected element in the Members List to the Names list.\nDelete Entry\nClick to delete the selected entry from the Names list.\nDelete All\nClick to delete all entries from the Names list.\n\nCE\nClick to identify the currently selected view as the working element.\nViews\nSelect a view for the sheet from the drop-down list.\nRules\nSelect a rule from the list.\nCreate\nAllows you to create a rule. Click to display the Create RRUL window.\nInput a name for the new rule in the Name field.\nClick OK to add the rule to the Rules list or Cancel to discard any changes and close the Create RRUL window.\nDelete\nClick to delete the currently selected rule from the Rules list.\nFor\nAllows you to specify the items that the rule is applied to.\nSelect the All option button and select the elements the rule is applied to from the drop-down list.\nSelect the Names option button and click Modify to display the Names window.\nWith\nTo apply qualifying restrictions to the elements specified in the For section, input an expression in the With field. For example, if the For section specifies Branches, the following can be input:\n(HBOR GT 100) AND (TBOR GT 80)\nmeaning 'Branches with HBOR greater than 100mm and TBOR greater than 80mm'.\nSymbology - Draw as Annotations\nSelect the check box to represent design items symbolically.\nHidden line removal\nSelect the check box to enable hidden line removal.\nStyle\nSelect the check box to associate the local rule with a representation style.\nStyles\nSelect a representation style library from the upper drop-down list.\nSelect a style from the lower list.\nPlease note that the SRLSTY special style type cannot be used with this window. If you attempt to use the SRLSTY style, an error message is displayed.\nThe SRLSTY special style type is used when setting up symbolic representation, refer to Symbolic Representation for further information.\nDisplay\nSelect from the drop-down list to define the display of representation styles in the Styles list.\nOwner\nSelect to navigate to the owning element of the currently selected element. The element is selected in the Members List.\nFirst\nSelect Element to navigate to the first element in the currently selected hierarchy. The element is selected in the Members List.\nSelect Member to navigate to the first member of the currently selected element. The element is selected in the Members List.\nLast\nSelect Element to navigate to the last element in the currently selected hierarchy. The element is selected in the Members List.\nSelect Member to navigate to the last member of the currently selected element. The element is selected in the Members List.\nSame\nSelect to navigate to the previously selected element. The element is selected in the Members List.\nClick to navigate to the previous element in the currently selected hierarchy. The element is selected in the Members List.\nClick to navigate to the next element in the currently selected hierarchy. The element is selected in the Members List.\nDesign Members / Drawlists\nThe Members list can display either design member elements or existing drawlists.\nSelect Design Members from the drop-down list to pick design elements explicitly.\nSelect Drawlists from the drop-down list to identify design elements by their presence in other drawlists.\nAdd\nClick to add the currently selected element in the Members List to the Names list.\nDelete Entry\nClick to delete the selected entry from the Names list.\nDelete All\nClick to delete all entries from the Names list.\n\n\n\nSymbolic Representation\nCE\nViews\nRules\nCreate\nCreate RRUL\nName\nOK\nCancel\nCreate RRUL\nDelete\nFor\nAll\nNames\nModify\nNames\nWith\nFor\nWith\nFor\nSymbology - Draw as Annotations\nHidden line removal\nStyle\nStyles\nSymbolic Representation\nDisplay\nStyles\nApply\nCancel\nLocal Rules\nNames\nNames\nMembers\nNames\nNavigation\nMembers List\nOwner\nFirst\nElement\nMember\nLast\nElement\nMember\nSame\nDesign Members / Drawlists\nDesign Members\nDrawlists\nAdd\nDelete Entry\nDelete All"}
{"Headers": "Create and Apply Local Hatching Rules", "Content": "Creates local hatching rules and applies them to items in the view drawlist, overriding the selected discipline specific rules for those items.\n\nCE\nClick to identify the currently selected view as the working element.\nViews\nSelect the view for the sheet from the drop-down list.\nRules\nSelect a hatching rule from the list.\nCreate\nAllows you to create a hatching rule. Click to display the Create HRUL window.\nInput a name for the new rule in the Name field.\nClick OK to add the rule to the Rules list or Cancel to discard any changes and close the Create HRUL window.\nDelete\nClick to delete the currently selected hatching rule from the Rules list.\nFor\nAllows you to specify the items that the rule is applied to.\nSelect the Menus option button and select the elements the rule is applied to from the drop-down list.\nSelect the Names option button and click Modify to display the Names window. Refer to Create and Apply Local Rules for further information.\nWith\nTo apply qualifying restrictions to the elements specified in the For section, input an expression in the With field. For example, if the For section specifies Branches, the following can be input:\n(HBOR GT 100) AND (TBOR GT 80)\nmeaning 'Branches with HBOR greater than 100mm and TBOR greater than 80mm'.\nStyle\nSelect the check box to associate the hatching rule with a representation style.\nStyles\nSelect a representation style library from the upper drop-down list.\nSelect a style from the lower list.\nDisplay\nDisplays a graphical representation of the selected style from the lower Styles list.\nAttributes\nAllows you to define the hatching rule attributes. Refer to Hatching Rule Attributes for further information.\nCE\nClick to identify the currently selected view as the working element.\nViews\nSelect the view for the sheet from the drop-down list.\nRules\nSelect a hatching rule from the list.\nCreate\nAllows you to create a hatching rule. Click to display the Create HRUL window.\n\nInput a name for the new rule in the Name field.\nClick OK to add the rule to the Rules list or Cancel to discard any changes and close the Create HRUL window.\nDelete\nClick to delete the currently selected hatching rule from the Rules list.\nFor\nAllows you to specify the items that the rule is applied to.\nSelect the Menus option button and select the elements the rule is applied to from the drop-down list.\nSelect the Names option button and click Modify to display the Names window. Refer to Create and Apply Local Rules for further information.\nWith\nTo apply qualifying restrictions to the elements specified in the For section, input an expression in the With field. For example, if the For section specifies Branches, the following can be input:\nmeaning 'Branches with HBOR greater than 100mm and TBOR greater than 80mm'.\nStyle\nSelect the check box to associate the hatching rule with a representation style.\nStyles\nSelect a representation style library from the upper drop-down list.\nSelect a style from the lower list.\nDisplay\nDisplays a graphical representation of the selected style from the lower Styles list.\nAttributes\nAllows you to define the hatching rule attributes. Refer to Hatching Rule Attributes for further information.\nClick Apply to apply the hatching rules or Cancel to discard any changes and close the Local Hatching Rules window.\nCE\nClick to identify the currently selected view as the working element.\nViews\nSelect the view for the sheet from the drop-down list.\nRules\nSelect a hatching rule from the list.\nCreate\nAllows you to create a hatching rule. Click to display the Create HRUL window.\nInput a name for the new rule in the Name field.\nClick OK to add the rule to the Rules list or Cancel to discard any changes and close the Create HRUL window.\nDelete\nClick to delete the currently selected hatching rule from the Rules list.\nFor\nAllows you to specify the items that the rule is applied to.\nSelect the Menus option button and select the elements the rule is applied to from the drop-down list.\nSelect the Names option button and click Modify to display the Names window. Refer to Create and Apply Local Rules for further information.\nWith\nTo apply qualifying restrictions to the elements specified in the For section, input an expression in the With field. For example, if the For section specifies Branches, the following can be input:\n(HBOR GT 100) AND (TBOR GT 80)\nmeaning 'Branches with HBOR greater than 100mm and TBOR greater than 80mm'.\nStyle\nSelect the check box to associate the hatching rule with a representation style.\nStyles\nSelect a representation style library from the upper drop-down list.\nSelect a style from the lower list.\nDisplay\nDisplays a graphical representation of the selected style from the lower Styles list.\nAttributes\nAllows you to define the hatching rule attributes. Refer to Hatching Rule Attributes for further information.\n\n\n\nCreate and Apply Local Rules\nHatching Rule Attributes\nCE\nViews\nRules\nCreate\nCreate HRUL\nName\nOK\nCancel\nCreate HRUL\nDelete\nFor\nMenus\nNames\nModify\nNames\nCreate and Apply Local Rules\nWith\nFor\nWith\nFor\nStyle\nStyles\nDisplay\nStyles\nAttributes\nHatching Rule Attributes\nApply\nCancel\nLocal Hatching Rules"}
{"Headers": "Laser Data", "Content": "Displays rendered Laser Survey Data (XGOEM) alongside the modelled data.\nThe appearance of the laser survey is inherited from a Point Cloud Volume Representation Set (LAVOST) element which stores a list of representation style elements. Each representation element references an Area Definition (AREADE) or Demolition Package (DEMOPA) element in which the volume of laser survey is rendered. AREADE and DEMOPA elements are stored in the Design (DESI) database and cannot be modified in the DRAW application.\nThe drawing output containing laser survey is depth buffered with modelled elements. All modelled elements that are in front of the laser survey will obscure the survey, and all elements behind the survey will be obscured by the survey.\n\n\nThe first time the Point Cloud Volumes window displays for a view, the DRAW application checks that the view references a point cloud volume representation set. If the view does not reference a point cloud volume representation set, a confirm window displays asking you to create one.\n\nClick Yes to create a point cloud volume representation set. Click No to define that the view is not associated with a point cloud volume representation set.\nThe Point Cloud Volumes window displays the area definitions and demolition packages that have been defined in Model. When an area definition or demolition package is selected, the selection is highlighted in the 2D or 3D view.\n\nSelect LAVOST\nAllows you to modify the point cloud volume representation set used to define the appearance of the laser survey.\nClick to display the Select Point Cloud Volume Representation Set window.\n\nYou can browse and select the required point cloud volume representation set element.\nClick Select to apply the selected point cloud volume representation set element.\nClick Cancel to discard any changes and close the Select Point Cloud Volume Representation Set window.\n\nDetail Laser Data\nClick to optimise the display resolution of the laser survey within the area definition or demolition package volume.\nRepeat the command to turn off the display optimisation.\n\nHighlight Laser Data\nClick to highlight detailed laser survey data within the area definition or demolition package volume.\nThe default highlight colour is pink and cannot be modified.\nRepeat the command to remove the highlight from the detailed laser survey data volume.\n\nSpecify Highlight Colour\nClick to modify the colour of highlighted laser survey data within the area definition or demolition package volume. Multiple colours can be used to highlight the area definition or demolition package volume.\nSelect a colour from the colour palette. The laser survey data is not highlighted as a solid colour, the colour is applied as a colour ramp to the selected volume. If the highlight was to be displayed as a solid colour, depth cues could be difficult for the user and the laser survey data could appear as a flat representation.\nAs colour ramps are applied to the laser survey data, some colours may not appear to contrast well with the laser survey data or other highlight colours. It is recommended that highlight colours are restricted to a limited discernible palette.\n\nMask Laser Data\nClick to remove detailed laser survey data within the area definition or demolition package volume.\nRepeat the command to remove the mask from the detailed laser survey data volume.\nExport and Print Resolution\nSets the laser survey final output quality.\nThe export/print resolution can be modified to alter the output using the Properties window. Refer to Properties for further information.\n\nPoint Cloud Drawing Resolution (dpi)\nThe dots per inch (dpi) resolution defines the amount of dots that are printed/exported on the output drawing per square inch.\nInput a value in the field to modify the dpi resolution for laser survey.\nFor example, input 50 in the field to print/export at 50 dpi. The laser survey display is less detailed and solid (background model elements are not visible). Input 600 in the field to print/export at 600 dpi. The laser survey display is more detailed and translucent (background model elements are visible).\nPoint Cloud Drawing Resolution (dpi)\nThe dots per inch (dpi) resolution defines the amount of dots that are printed/exported on the output drawing per square inch.\nInput a value in the field to modify the dpi resolution for laser survey.\nFor example, input 50 in the field to print/export at 50 dpi. The laser survey display is less detailed and solid (background model elements are not visible). Input 600 in the field to print/export at 600 dpi. The laser survey display is more detailed and translucent (background model elements are visible).\n\nSelect LAVOST\nAllows you to modify the point cloud volume representation set used to define the appearance of the laser survey.\nClick to display the Select Point Cloud Volume Representation Set window.\nYou can browse and select the required point cloud volume representation set element.\nClick Select to apply the selected point cloud volume representation set element.\nClick Cancel to discard any changes and close the Select Point Cloud Volume Representation Set window.\nDetail Laser Data\nClick to optimise the display resolution of the laser survey within the area definition or demolition package volume.\nRepeat the command to turn off the display optimisation.\nHighlight Laser Data\nClick to highlight detailed laser survey data within the area definition or demolition package volume.\nThe default highlight colour is pink and cannot be modified.\nRepeat the command to remove the highlight from the detailed laser survey data volume.\nSpecify Highlight Colour\nClick to modify the colour of highlighted laser survey data within the area definition or demolition package volume. Multiple colours can be used to highlight the area definition or demolition package volume.\nSelect a colour from the colour palette. The laser survey data is not highlighted as a solid colour, the colour is applied as a colour ramp to the selected volume. If the highlight was to be displayed as a solid colour, depth cues could be difficult for the user and the laser survey data could appear as a flat representation.\nAs colour ramps are applied to the laser survey data, some colours may not appear to contrast well with the laser survey data or other highlight colours. It is recommended that highlight colours are restricted to a limited discernible palette.\nMask Laser Data\nClick to remove detailed laser survey data within the area definition or demolition package volume.\nRepeat the command to remove the mask from the detailed laser survey data volume.\nPoint Cloud Drawing Resolution (dpi)\nThe dots per inch (dpi) resolution defines the amount of dots that are printed/exported on the output drawing per square inch.\nInput a value in the field to modify the dpi resolution for laser survey.\nFor example, input 50 in the field to print/export at 50 dpi. The laser survey display is less detailed and solid (background model elements are not visible). Input 600 in the field to print/export at 600 dpi. The laser survey display is more detailed and translucent (background model elements are visible).\n\n\n\nProperties\nPoint Cloud Volumes\nYes\nNo\nPoint Cloud Volumes\nSelect LAVOST\nSelect Point Cloud Volume Representation Set\nSelect\nCancel\nSelect Point Cloud Volume Representation Set\nDetail Laser Data\nHighlight Laser Data\nSpecify Highlight Colour\nMask Laser Data\nExport and Print Resolution\nProperties\nProperties\nPoint Cloud Drawing Resolution (dpi)"}
{"Headers": "Add Model Element to Selected Views", "Content": "Adds the currently selected element in the Model Explorer to all selected views.\nThe functionality is not available if a view is not selected or the Drawlist Manager is open.\nTo add the currently selected element in the Model Explorer to all selected views, right-click and select Add CE To Selected Views from the drop-down menu.\n\nNote:\nThe functionality does not modify the scale or limits of the selected views. If the added element is outside of the current view limits, it will not be visible. However, the view Drawlist is updated accordingly and if you adjust the view scale or view limits correctly, the added element becomes visible.\nNote:\nThe changes are applied automatically if is set on the Status Bar.\n\n\n\nStatus Bar\nNote\n:\nDrawlist Manager\nAdd CE To Selected Views\nNote\n:\nStatus Bar"}
{"Headers": "Display Model Element Properties", "Content": "Displays model element properties in Draw. Model elements can be selected in a view, the Properties window is populated with the model element properties. Refer to Properties for further information.\nInput the command IN and press Enter to enable model element selection for the currently selected views.\nAlternatively, you can double click on a model element in a view to directly populate the Properties window with the model properties of a selected element.\n\nYou are prompted to Select Objects\nClick to identify design geometry in the view. The Properties window is populated with the model properties of the selected element.\n\nThe Properties window is populated with single model element or multiple model element properties, dependent on the object selection mode (single or multiple).\n\nInput the command OUT and press Enter to exit model element selection.\nAlternatively, you can press ESC to exit model element selection.\n\n\n\nProperties\nProperties\nProperties\nIN\nEnter\nProperties\nSelect Objects\nProperties\nProperties\nOUT\nEnter\nESC"}
{"Headers": "The 3D View", "Content": "Displays a 3D view for the assembly and manipulation of design elements to populate drawing sheets.\nYou can examine the content of the drawings in 3D view, before establishing the view content as a 2D drawing.\nHowever, the 3D view window also offers powerful facilities to enable the manipulation of 2D drawings.\n\nBy default, the Model Explorer and the Format 3D tab (refer to Format 3D Tab for further information) display when a 3D view is opened.\nWhen an element is selected in the 3D view, it is highlighted in the Model Explorer and vice versa.\n\nNote:\nThe display of elements in the 3D view can be modified using the Graphics Settings window. Refer to Graphics Drawlist for further information.\n\n\n\nFormat 3D Tab\nGraphics Drawlist\nFormat 3D\nFormat 3D Tab\nNote\n:\nGraphics Settings\nGraphics Drawlist"}
{"Headers": "Pan, Zoom and Rotate", "Content": "Sets the position and magnification of the model in the 3D environment.\nOther zoom options are available. Refer to Format 3D Tab for further information.\nTo zoom into a drawing, roll the mouse wheel up.\nTo zoom out from a drawing, roll the mouse wheel down.\nTo zoom in or out of a drawing while the view is in zoom mode, hold down the mouse wheel and move the cursor up (to zoom in) or down (to zoom out).\nTo pan, click and hold the mouse wheel and drag the drawing in the required direction.\nTo rotate, either hold the mouse wheel and move the cursor in the required direction to rotate the view in that direction, or press the appropriate arrow key on the keyboard.\nTo zoom into a drawing, roll the mouse wheel up.\nTo zoom into a drawing, roll the mouse wheel up.\nTo zoom out from a drawing, roll the mouse wheel down.\nTo zoom out from a drawing, roll the mouse wheel down.\nTo zoom in or out of a drawing while the view is in zoom mode, hold down the mouse wheel and move the cursor up (to zoom in) or down (to zoom out).\nTo zoom in or out of a drawing while the view is in zoom mode, hold down the mouse wheel and move the cursor up (to zoom in) or down (to zoom out).\nTo pan, click and hold the mouse wheel and drag the drawing in the required direction.\nTo pan, click and hold the mouse wheel and drag the drawing in the required direction.\nTo rotate, either hold the mouse wheel and move the cursor in the required direction to rotate the view in that direction, or press the appropriate arrow key on the keyboard.\nTo rotate, either hold the mouse wheel and move the cursor in the required direction to rotate the view in that direction, or press the appropriate arrow key on the keyboard.\n\n\n\nFormat 3D Tab\nFormat 3D Tab"}
{"Headers": "View Contents", "Content": "Displays the contents of the drawlist.\n\nTo remove the currently selected element, right-click and select Remove Selected from the drop-down menu.\n\n\n\nRemove Selected"}
{"Headers": "Add and Remove Model Items to/from the 3D View", "Content": "Adds an item to the 3D view or removes an item from the 3D view.\nTo add an item to a 3D view, select the item in the Model Explorer and drag it into the 3D view.\nAlternatively, select the item in the Model Explorer, right-click and select 3D View, select Add, Add Connected or Add Within Volume from the drop-down menu.\nAlternatively, an item can be added to the 3D view using the Format 3D tab. Refer to Format 3D Tab for further information.\nTo delete an item from a 3D view, select the item in 3D view, right-click and select Remove from 3D View from the drop-down menu.\nAlternatively, select the item in the Model Explorer, right-click and select 3D View, select Remove from the drop-down menu.\nAlternatively, an item can be removed from the 3D view using the Format 3D tab. Refer to Format 3D Tab Tab for further information.\nAlternatively, an item can be removed form the 3D view using the View Contents window. Refer to View Contents for further information.\nNote:\nAny modifications made to the 3D view using the Command Window (ADD or REM) are not added to the Draw Idlist. Modifications made in this way are lost when the 3D view is closed.\n\n\n\nFormat 3D Tab\nFormat 3D Tab\nView Contents\n3D View\nAdd\nAdd Connected\nAdd Within Volume\nFormat 3D\nFormat 3D Tab\nRemove from 3D View\n3D View\nRemove\nFormat 3D\nFormat 3D Tab\nView Contents\nView Contents\nNote\n:"}
{"Headers": "Format 3D Tab", "Content": "3D views are formatted using the Format 3D tab. The tab displays when a 3D view is open.\n\n\nManage Group\nAdd Element\nAllows you to add elements to the view. Refer to Add and Remove Model Items to/from the 3D View for further information.\nRemove Element\nAllows you to remove selected elements from the view. Refer to Add and Remove Model Items to/from the 3D View for further information.\nView Contents\nAllows you to view a list of the view contents. Refer to View Contents for further information.\nNavigate Group\nZoom\nAllows you to switch the 3D view to zoom mode. Refer to Pan, Zoom and Rotate for further information.\nClick to display a drop-down list with the following options:\nLimits CE\nClick to adjust the scale of the view so that it corresponds to the volume of the selected element(s).\nZoom to Selection\nClick to zoom into the element selected in the Model Explorer.\nGo to Drawlist\nClick to zoom to the limits of all the elements in the drawlist.\nCentre on Selection\nClick to centre the view on the element selected in the Model Explorer.\nParallel\nClick to display a drop-down list with the following options:\nParallel\nClick to set the view to parallel projection mode.\nPerspective\nClick to set the view to perspective projection mode.\nModel\nClick to display a drop-down list with the following options:\nEye\nClick to move the 3D model around the current viewpoint.\nModel\nClick to move the current viewpoint around the 3D model.\nGrid Group\nSet View\nAllows you to modify the view to display a grid plane. Refer to Grid Plane View for further information.\nScale Group\nType\nAllows you to set the type of scale for the view. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nScale\nAllows you to select the scale for the view. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nDirection Group\nDown\nAllows you to set the view direction. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nDirection\nDisplays coordinates to indicate the current view direction. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nRotation\nDisplays the current view angle. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nNote:\nFor a 2D view direction of U (+Z) only, there is a difference in the definition of Rotation between the 2D and 3D views. A rotation of 0 in the 2D view corresponds to a rotation of 180 in the 3D view for this direction only. In this scenario moving between the 2D and 3D view will toggle the Rotation between 0 and 180. This is as designed and the visual orientation of the view is maintained correctly.\nLimits Group\nLimits from Drawlist\nAllows you to set the limits of the 3D view to a volume that encloses all items in the view drawlist.\nClick to populate the limits fields.\nAdd CE Fully Within\nClick to add to the drawlist any elements under the currently selected element in the Model Explorer which are fully contained by the current limits volume. To add all Model elements that are fully contained by the current limits volume, select the WORLD element in the Model Explorer.\nAdd CE Partially Within\nClick to add to the drawlist any elements under the currently selected element in the Model Explorer which are partially contained by the current limits volume. To add all Model elements that are partially contained by the current limits volume, select the WORLD element in the Model Explorer.\nDisplay\nClick to turn the display of the limits box on or off.\nEast/West, North/South, Up/Down\nAllows you to set the limits of the 3D view.\nPopulate these fields initially by selecting Limits from Drawlist.\nThen, if required, input dimensional values in the direction fields to define the limits of the view explicitly.\nClick the view direction icon adjacent to the field to flip the view direction.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down lists.\nClear Limits\nClick to clear all 3D limits defined for the view.\nView Frame\nTurns the view frame lock on or off. If the view frame is unlocked, the frame becomes independent of the view limits and is unaffected by any alteration to the view content or limits via 3D view or update commands.\nMatchlines\nClick to turn the display of match lines on or off.\nRefer to Define Limits for further information.\nSection Group\nCreate\nAllows you to create a section plane, an existing view can be modified to display only specific parts of it. Refer to Create 3D Section Planes for further information\nDisplay\nClick to turn the display of section planes on or off. A hatched area indicates the side of the plane that an area of the view is removed from.\nFunctionality is available to modify the section planes. Refer to Modify Section Plane using Grip Points for further information.\nDelete\nClick to delete the currently selected section plane.\nCutting List\nEach section plane can be associated with a pre-defined cutting list, which is effectively a drawlist. Elements within the cutting list can be removed from the view, allowing for other elements to remain within the view even though a section plane exists.\nSelect from the drop-down list to associate the currently selected section plane with a cutting list.\nDirection\nSelect from the drop-down list to modify the cutting direction of the currently selected section plane.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down list.\nA hatched area indicates the side of the plane that an area of the view is removed from.\nOpen/Closed\nSelect from the drop-down list to define the shape of the currently selected section plane.\nSelect Open to define a section plane as an open ended shape. For example, an L shape consisting of two planes.\nSelect Closed to define a section plane as a closed shape. For example, a rectangle.\nClipping Group\nClip\nClick to turn all clipping on or off for both the limits box (if defined) and any defined section planes.\nWhen the 3D view is entered, clipping is off.\nNote:\nIf any section planes are enabled individually for clipping, the option becomes active.\nClip Plane\nAllows you to turn clipping on or off for individual section planes. Refer to Define Clipping Plane for further information.\nCap\nElements that are intersected by the clipping plane can have a coloured cap added to indicate that they extend beyond the display region.\nClick to turn the capping of clipped elements or off. The default cap settings can be defined. Refer to Current View for further information.\nPoint Cloud Group\nDisplay\nClick to display a drop-down list with the following options:\nDisplay\nAllows you to define the display of laser data for the view. Refer to Laser Data for further information.\nLow Density Points\nLow density point laser data is laser data that has not been defined as detailed laser data. Refer to Detail Laser Data for further information.\nClick to remove low density point laser data from the view.\nRepeat the command to add low density point laser data to the view\nRemember Group\nFreeze\nClick to remember the current scale and view direction.\nRestore\nClick to restore the scale or view direction to when it was last frozen, or to the 3D view entry state.\nComplete Group\nApply\nClick to close the 3D view and save the current scale and view direction. Changes to the view content and section planes are also saved. The view is resized to the limits.\nFinish\nFor a new view, the functionality is the same as clicking Apply.\nFor an existing view, the functionality is equivalent to clicking Restore and then clicking Apply. The current scale and view direction are not saved. Modifications to the view content and section planes are saved. The view is resized to the limits.\nCancel\nClick to close the 3D view without saving any changes.\nNote:\nCreation and modification of user defined section planes is an exception, these are always saved immediately.\nManage Group\nAdd Element\nAllows you to add elements to the view. Refer to Add and Remove Model Items to/from the 3D View for further information.\nRemove Element\nAllows you to remove selected elements from the view. Refer to Add and Remove Model Items to/from the 3D View for further information.\nView Contents\nAllows you to view a list of the view contents. Refer to View Contents for further information.\nNavigate Group\nZoom\nAllows you to switch the 3D view to zoom mode. Refer to Pan, Zoom and Rotate for further information.\nClick to display a drop-down list with the following options:\nClick to adjust the scale of the view so that it corresponds to the volume of the selected element(s).\nClick to zoom into the element selected in the Model Explorer.\nClick to zoom to the limits of all the elements in the drawlist.\nClick to centre the view on the element selected in the Model Explorer.\nParallel\nClick to display a drop-down list with the following options:\nClick to set the view to parallel projection mode.\nClick to set the view to perspective projection mode.\nModel\nClick to display a drop-down list with the following options:\nClick to move the 3D model around the current viewpoint.\nClick to move the current viewpoint around the 3D model.\nGrid Group\nSet View\nAllows you to modify the view to display a grid plane. Refer to Grid Plane View for further information.\nScale Group\nType\nAllows you to set the type of scale for the view. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nScale\nAllows you to select the scale for the view. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nDirection Group\nDown\nAllows you to set the view direction. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nDirection\nDisplays coordinates to indicate the current view direction. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nRotation\nDisplays the current view angle. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nLimits Group\nLimits from Drawlist\nAllows you to set the limits of the 3D view to a volume that encloses all items in the view drawlist.\nClick to populate the limits fields.\nAdd CE Fully Within\nClick to add to the drawlist any elements under the currently selected element in the Model Explorer which are fully contained by the current limits volume. To add all Model elements that are fully contained by the current limits volume, select the WORLD element in the Model Explorer.\nAdd CE Partially Within\nClick to add to the drawlist any elements under the currently selected element in the Model Explorer which are partially contained by the current limits volume. To add all Model elements that are partially contained by the current limits volume, select the WORLD element in the Model Explorer.\nDisplay\nClick to turn the display of the limits box on or off.\nEast/West, North/South, Up/Down\nAllows you to set the limits of the 3D view.\nPopulate these fields initially by selecting Limits from Drawlist.\nThen, if required, input dimensional values in the direction fields to define the limits of the view explicitly.\nClick the view direction icon adjacent to the field to flip the view direction.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down lists.\nClear Limits\nClick to clear all 3D limits defined for the view.\nView Frame\nTurns the view frame lock on or off. If the view frame is unlocked, the frame becomes independent of the view limits and is unaffected by any alteration to the view content or limits via 3D view or update commands.\nMatchlines\nClick to turn the display of match lines on or off.\nRefer to Define Limits for further information.\nSection Group\nCreate\nAllows you to create a section plane, an existing view can be modified to display only specific parts of it. Refer to Create 3D Section Planes for further information\nDisplay\nClick to turn the display of section planes on or off. A hatched area indicates the side of the plane that an area of the view is removed from.\nFunctionality is available to modify the section planes. Refer to Modify Section Plane using Grip Points for further information.\nDelete\nClick to delete the currently selected section plane.\nCutting List\nEach section plane can be associated with a pre-defined cutting list, which is effectively a drawlist. Elements within the cutting list can be removed from the view, allowing for other elements to remain within the view even though a section plane exists.\nSelect from the drop-down list to associate the currently selected section plane with a cutting list.\nDirection\nSelect from the drop-down list to modify the cutting direction of the currently selected section plane.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down list.\nA hatched area indicates the side of the plane that an area of the view is removed from.\nOpen/Closed\nSelect from the drop-down list to define the shape of the currently selected section plane.\nSelect Open to define a section plane as an open ended shape. For example, an L shape consisting of two planes.\nSelect Closed to define a section plane as a closed shape. For example, a rectangle.\nClipping Group\n\nClip\nClick to turn all clipping on or off for both the limits box (if defined) and any defined section planes.\nWhen the 3D view is entered, clipping is off.\nClip Plane\nAllows you to turn clipping on or off for individual section planes. Refer to Define Clipping Plane for further information.\nCap\nElements that are intersected by the clipping plane can have a coloured cap added to indicate that they extend beyond the display region.\nClick to turn the capping of clipped elements or off. The default cap settings can be defined. Refer to Current View for further information.\nPoint Cloud Group\nDisplay\nClick to display a drop-down list with the following options:\nAllows you to define the display of laser data for the view. Refer to Laser Data for further information.\nLow density point laser data is laser data that has not been defined as detailed laser data. Refer to Detail Laser Data for further information.\nClick to remove low density point laser data from the view.\nRepeat the command to add low density point laser data to the view\nRemember Group\nFreeze\nClick to remember the current scale and view direction.\nRestore\nClick to restore the scale or view direction to when it was last frozen, or to the 3D view entry state.\nComplete Group\nApply\nClick to close the 3D view and save the current scale and view direction. Changes to the view content and section planes are also saved. The view is resized to the limits.\nFinish\nFor a new view, the functionality is the same as clicking Apply.\nFor an existing view, the functionality is equivalent to clicking Restore and then clicking Apply. The current scale and view direction are not saved. Modifications to the view content and section planes are saved. The view is resized to the limits.\nCancel\nClick to close the 3D view without saving any changes.\n\nManage Group\nAdd Element\nAllows you to add elements to the view. Refer to Add and Remove Model Items to/from the 3D View for further information.\nRemove Element\nAllows you to remove selected elements from the view. Refer to Add and Remove Model Items to/from the 3D View for further information.\nView Contents\nAllows you to view a list of the view contents. Refer to View Contents for further information.\nNavigate Group\nZoom\nAllows you to switch the 3D view to zoom mode. Refer to Pan, Zoom and Rotate for further information.\nClick to display a drop-down list with the following options:\nLimits CE\nClick to adjust the scale of the view so that it corresponds to the volume of the selected element(s).\nZoom to Selection\nClick to zoom into the element selected in the Model Explorer.\nGo to Drawlist\nClick to zoom to the limits of all the elements in the drawlist.\nCentre on Selection\nClick to centre the view on the element selected in the Model Explorer.\nParallel\nClick to display a drop-down list with the following options:\nParallel\nClick to set the view to parallel projection mode.\nPerspective\nClick to set the view to perspective projection mode.\nModel\nClick to display a drop-down list with the following options:\nEye\nClick to move the 3D model around the current viewpoint.\nModel\nClick to move the current viewpoint around the 3D model.\nGrid Group\nSet View\nAllows you to modify the view to display a grid plane. Refer to Grid Plane View for further information.\nScale Group\nType\nAllows you to set the type of scale for the view. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nScale\nAllows you to select the scale for the view. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nDirection Group\nDown\nAllows you to set the view direction. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nDirection\nDisplays coordinates to indicate the current view direction. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nRotation\nDisplays the current view angle. The functionality is identical to the Format 2D tab. Refer to Format 2D View for further information.\nNote:\nFor a 2D view direction of U (+Z) only, there is a difference in the definition of Rotation between the 2D and 3D views. A rotation of 0 in the 2D view corresponds to a rotation of 180 in the 3D view for this direction only. In this scenario moving between the 2D and 3D view will toggle the Rotation between 0 and 180. This is as designed and the visual orientation of the view is maintained correctly.\nLimits Group\nLimits from Drawlist\nAllows you to set the limits of the 3D view to a volume that encloses all items in the view drawlist.\nClick to populate the limits fields.\nAdd CE Fully Within\nClick to add to the drawlist any elements under the currently selected element in the Model Explorer which are fully contained by the current limits volume. To add all Model elements that are fully contained by the current limits volume, select the WORLD element in the Model Explorer.\nAdd CE Partially Within\nClick to add to the drawlist any elements under the currently selected element in the Model Explorer which are partially contained by the current limits volume. To add all Model elements that are partially contained by the current limits volume, select the WORLD element in the Model Explorer.\nDisplay\nClick to turn the display of the limits box on or off.\nEast/West, North/South, Up/Down\nAllows you to set the limits of the 3D view.\nPopulate these fields initially by selecting Limits from Drawlist.\nThen, if required, input dimensional values in the direction fields to define the limits of the view explicitly.\nClick the view direction icon adjacent to the field to flip the view direction.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down lists.\nClear Limits\nClick to clear all 3D limits defined for the view.\nView Frame\nTurns the view frame lock on or off. If the view frame is unlocked, the frame becomes independent of the view limits and is unaffected by any alteration to the view content or limits via 3D view or update commands.\nMatchlines\nClick to turn the display of match lines on or off.\nRefer to Define Limits for further information.\nSection Group\nCreate\nAllows you to create a section plane, an existing view can be modified to display only specific parts of it. Refer to Create 3D Section Planes for further information\nDisplay\nClick to turn the display of section planes on or off. A hatched area indicates the side of the plane that an area of the view is removed from.\nFunctionality is available to modify the section planes. Refer to Modify Section Plane using Grip Points for further information.\nDelete\nClick to delete the currently selected section plane.\nCutting List\nEach section plane can be associated with a pre-defined cutting list, which is effectively a drawlist. Elements within the cutting list can be removed from the view, allowing for other elements to remain within the view even though a section plane exists.\nSelect from the drop-down list to associate the currently selected section plane with a cutting list.\nDirection\nSelect from the drop-down list to modify the cutting direction of the currently selected section plane.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down list.\nA hatched area indicates the side of the plane that an area of the view is removed from.\nOpen/Closed\nSelect from the drop-down list to define the shape of the currently selected section plane.\nSelect Open to define a section plane as an open ended shape. For example, an L shape consisting of two planes.\nSelect Closed to define a section plane as a closed shape. For example, a rectangle.\nClipping Group\nClip\nClick to turn all clipping on or off for both the limits box (if defined) and any defined section planes.\nWhen the 3D view is entered, clipping is off.\nNote:\nIf any section planes are enabled individually for clipping, the option becomes active.\nClip Plane\nAllows you to turn clipping on or off for individual section planes. Refer to Define Clipping Plane for further information.\nCap\nElements that are intersected by the clipping plane can have a coloured cap added to indicate that they extend beyond the display region.\nClick to turn the capping of clipped elements or off. The default cap settings can be defined. Refer to Current View for further information.\nPoint Cloud Group\nDisplay\nClick to display a drop-down list with the following options:\nDisplay\nAllows you to define the display of laser data for the view. Refer to Laser Data for further information.\nLow Density Points\nLow density point laser data is laser data that has not been defined as detailed laser data. Refer to Detail Laser Data for further information.\nClick to remove low density point laser data from the view.\nRepeat the command to add low density point laser data to the view\nRemember Group\nFreeze\nClick to remember the current scale and view direction.\nRestore\nClick to restore the scale or view direction to when it was last frozen, or to the 3D view entry state.\nComplete Group\nApply\nClick to close the 3D view and save the current scale and view direction. Changes to the view content and section planes are also saved. The view is resized to the limits.\nFinish\nFor a new view, the functionality is the same as clicking Apply.\nFor an existing view, the functionality is equivalent to clicking Restore and then clicking Apply. The current scale and view direction are not saved. Modifications to the view content and section planes are saved. The view is resized to the limits.\nCancel\nClick to close the 3D view without saving any changes.\nNote:\nCreation and modification of user defined section planes is an exception, these are always saved immediately.\nNote:\nFor a 2D view direction of U (+Z) only, there is a difference in the definition of Rotation between the 2D and 3D views. A rotation of 0 in the 2D view corresponds to a rotation of 180 in the 3D view for this direction only. In this scenario moving between the 2D and 3D view will toggle the Rotation between 0 and 180. This is as designed and the visual orientation of the view is maintained correctly.\nNote:\nIf any section planes are enabled individually for clipping, the option becomes active.\nNote:\nCreation and modification of user defined section planes is an exception, these are always saved immediately.\n\n\n\nAdd and Remove Model Items to/from the 3D View\nAdd and Remove Model Items to/from the 3D View\nView Contents\nPan, Zoom and Rotate\nGrid Plane View\nFormat 2D View\nFormat 2D View\nFormat 2D View\nFormat 2D View\nFormat 2D View\nDefine Limits\nCreate 3D Section Planes\nModify Section Plane using Grip Points\nDefine Clipping Plane\nCurrent View\nLaser Data\nDetail Laser Data\nFormat 3D\nManage Group\nAdd Element\nAdd and Remove Model Items to/from the 3D View\nRemove Element\nAdd and Remove Model Items to/from the 3D View\nView Contents\nView Contents\nNavigate Group\nZoom\nPan, Zoom and Rotate\nLimits CE\nZoom to Selection\nGo to Drawlist\nCentre on Selection\nParallel\nParallel\nPerspective\nModel\nEye\nModel\nGrid Group\nSet View\nGrid Plane View\nScale Group\nType\nFormat 2D View\nScale\nFormat 2D\nFormat 2D View\nDirection Group\nDown\nFormat 2D\nFormat 2D View\nDirection\nFormat 2D\nFormat 2D View\nRotation\nFormat 2D View\nNote\n:\nLimits Group\nLimits from Drawlist\nAdd CE Fully Within\nAdd CE Partially Within\nDisplay\nEast/West, North/South, Up/Down\nLimits from Drawlist\nEast\nWest\nNorth\nSouth\nUp\nDown\nClear Limits\nView Frame\nMatchlines\nDefine Limits\nSection Group\nCreate\nCreate 3D Section Planes\nDisplay\nModify Section Plane using Grip Points\nDelete\nCutting List\nDirection\nEast\nWest\nNorth\nSouth\nUp\nDown\nOpen/Closed\nOpen\nClosed\nClipping Group\nClip\nNote\n:\nClip Plane\nDefine Clipping Plane\nCap\nCurrent View\nPoint Cloud Group\nDisplay\nDisplay\nLaser Data\nLow Density Points\nDetail Laser Data\nRemember Group\nFreeze\nRestore\nComplete Group\nApply\nFinish\nApply\nRestore\nApply\nCancel\nNote\n:"}
{"Headers": "Grid Plane View", "Content": "Sets the view to display a specified grid plane and all the 3D model elements that are associated with it.\n\nWith the 3D view displayed, select a grid plane in the Model Explorer. The grid plane is highlighted in the 3D view.\nThe grid plane displays in the view and is scaled to the view limits.\n\nBy default, section planes are created to remove unwanted elements from the view. You can modify the section planes to define the view. Refer to Modify Section Plane using Grip Points for further information.\n\nThe view can be modified to display the grid plane view.\n\n\n\n\nModify Section Plane using Grip Points\nModify Section Plane using Grip Points"}
{"Headers": "Define Limits", "Content": "Defines the limits of a 3D view.\nThe view limits are derived from the elements in the drawlist and display in the view. For example:\n\nThe limits display in the fields in the Define Limits group. For example:\n\nMove Limits Box\nMoves the limits box to a specified position.\nDouble click the limits box to display editor grips and select the cube grip.\nYou are prompted to Specify move point\nInput values in the dimension fields and press Enter or click to identify the limits box position.\nThe limits box is moved and the command ends automatically. By default, the limits fields are updated accordingly.\n\nModify Limits Box\nSets the size of the limits box along a single axis.\nDouble click the limits box to display editor grips and select a cone grip.\nYou are prompted to Specify absolute value or\nInput a dimensional value in the field and press Enter or click to identify the limits box position.\nThe limits box is modified and the command ends automatically. By default, the limits fields are updated accordingly.\nThroughout the limits box modification process you can press ESC to cancel the command. Additional functionality is also available.\nExpand\nPress the down arrow key and select Expand to scale the limits box.\nYou are prompted to Specify expansion or\nInput a dimensional value in the field and press Enter or click to identify the limits box position.\nThe limits box is scaled and the command ends automatically. By default, the limits fields are updated accordingly.\n\nExpand\nPress the down arrow key and select Expand to scale the limits box.\nYou are prompted to Specify expansion or\nInput a dimensional value in the field and press Enter or click to identify the limits box position.\nThe limits box is scaled and the command ends automatically. By default, the limits fields are updated accordingly.\n\nExpand\nPress the down arrow key and select Expand to scale the limits box.\nYou are prompted to Specify expansion or\nInput a dimensional value in the field and press Enter or click to identify the limits box position.\nThe limits box is scaled and the command ends automatically. By default, the limits fields are updated accordingly.\n\n\n\nDefine Limits\nMove Limits Box\nSpecify move point\nEnter\nModify Limits Box\nSpecify absolute value or\nEnter\nESC\nExpand\nExpand\nSpecify expansion or\nEnter"}
{"Headers": "Create 3D Section Planes", "Content": "Displays specific parts of an existing view.\nSection planes can also be created using facilities on the Format 2D tab. Refer to Create 2D Section Planes for further information.\n\n\n\nCreate 2D Section Planes\nFormat 2D\nCreate 2D Section Planes"}
{"Headers": "Define Clipping Plane", "Content": "Turns clipping on or off for individual section planes.\nYou are prompted to Select plane to toggle clipping\nClick to identify one or more section planes. The clipping status of the selected section planes is switched on or off.\n\nNote:\nSection planes must be visible to modify the clipping status. Refer to Format 3D Tab for further information.\n\n\n\nFormat 3D Tab\nNote\n:\nFormat 3D Tab\nSelect plane to toggle clipping"}
{"Headers": "Create Regions", "Content": "Sets an area that can be used for sketching. Unlike other views a region has a pre-defined direction or orientation, and does not have a drawlist.\n\n\n"}
{"Headers": "Add and Modify Drawing Objects", "Content": "You can amend drawing sheets by adding and modifying drawing objects such as lines and circles (primitives).\nWhen a 2D drafting element such as a primitive is added to a Sheet or View that does not own any Sheet Note or View Note elements, a new note is automatically created. The 2D drafting element is automatically placed under the new note.\nIf the Sheet/View owns a single note, the new element is automatically placed under that note.\nIf the Sheet/View owns multiple notes, the new element is added either to the currently selected note (for example, in the Draw Explorer) or to the first note listed in the Draw Explorer if none is selected.\nDrawing commands are initiated by selecting the required command from the Fluent User Interface (typically the Draw tab or Home tab) or inputting the command directly on the drawing canvas to display the Context Editor. Refer to Context Editor for further information.\n\n\n\nContext Editor\nDraw\nHome\nContext Editor"}
{"Headers": "Specify Points", "Content": "Click the required point of a drawing to specify points. The current cartesian coordinates, and where applicable, polar coordinates display.\nIf required, you can input values over the display coordinates to specify cartesian coordinates.\nA number of aids are available to help specify a point.\n\n\n"}
{"Headers": "Object Snaps", "Content": "Aids the positioning of objects by placing them relative to the geometry of existing objects.\nWhen object snapping is on, if a point is being specified and it is close to the snap point of an existing object, a symbol displays to indicate that the snap point is present.\nIn the example, a line is being drawn. The orange symbol indicates that the line endpoint is close to a snap point on an existing object (in this case the endpoint of a diamond, as indicated by a box).\n\nSelect the object snap modes to specify the types of snap points that are available.\n\nP-Point\nSnaps to P-points of objects.\nFunctionality is available to snap to P-points that are located both on the geometry and outside of the geometry of an object.\nWhen hovering over the design geometry, special snap points are displayed as crosses on the drawing canvas indicating the P-point locations on the object.\nTo select P-points outside of the geometry of an object, you must first hover the mouse over the design geometry.\nInformation is displayed for the currently selected P-point. The example displays a selected P-point at the centre arc of a panel element.\nP-Line MidPoint\nSnaps to middle P-line points of objects.\nP-Line EndPoint\nSnaps to start and end P-line points of objects.\nItem\nSnaps to start or end points of object origins.\nOwner\nSnaps to the owning element of the currently selected objects.\nConnection\nSnaps to connection points of objects.\nConnection Create\nSnaps to the nearest connection points of objects.\nEndpoint\nSnaps to endpoints of objects.\nMidpoint\nSnaps to middle points of objects.\nCentre\nSnaps to centre points (for example, for circles arcs or ellipses).\nNearest\nSnaps to the nearest points of objects.\nPerpendicular\nSnaps to perpendicular points of objects.\nQuadrant\nSnaps to points representing quadrants of circles, arcs or ellipses.\nTangent\nSnaps to points of objects where the line connecting the point and the previous point is tangent to the objects.\nExtension\nThe cursor is attracted by virtual extensions of existing objects.\nParallel\nSnaps to points on a virtual line parallel to the indicated objects.\nNode\nSnaps to node points (for example, on text objects).\nIntersection\nSnaps to intersection points of objects.\nInsertion\nSnaps to insertion points of complex objects.\nPoint Cloud\nSnaps to points on laser data.\nClear All\nTurns off all snap points for an area of the window.\nP-Point\nSnaps to P-points of objects.\nFunctionality is available to snap to P-points that are located both on the geometry and outside of the geometry of an object.\nWhen hovering over the design geometry, special snap points are displayed as crosses on the drawing canvas indicating the P-point locations on the object.\nTo select P-points outside of the geometry of an object, you must first hover the mouse over the design geometry.\nInformation is displayed for the currently selected P-point. The example displays a selected P-point at the centre arc of a panel element.\n\nP-Line MidPoint\nSnaps to middle P-line points of objects.\nP-Line EndPoint\nSnaps to start and end P-line points of objects.\nItem\nSnaps to start or end points of object origins.\nOwner\nSnaps to the owning element of the currently selected objects.\nConnection\nSnaps to connection points of objects.\nConnection Create\nSnaps to the nearest connection points of objects.\nEndpoint\nSnaps to endpoints of objects.\nMidpoint\nSnaps to middle points of objects.\nCentre\nSnaps to centre points (for example, for circles arcs or ellipses).\nNearest\nSnaps to the nearest points of objects.\nPerpendicular\nSnaps to perpendicular points of objects.\nQuadrant\nSnaps to points representing quadrants of circles, arcs or ellipses.\nTangent\nSnaps to points of objects where the line connecting the point and the previous point is tangent to the objects.\nExtension\nThe cursor is attracted by virtual extensions of existing objects.\nParallel\nSnaps to points on a virtual line parallel to the indicated objects.\nNode\nSnaps to node points (for example, on text objects).\nIntersection\nSnaps to intersection points of objects.\nInsertion\nSnaps to insertion points of complex objects.\nPoint Cloud\nSnaps to points on laser data.\nClear All\nTurns off all snap points for an area of the window.\nDifferent symbols display for each snap type. Each type of snap point can be turned on or off.\nYou can retain a snap selection between different states of the same operation using the PowerWheel\u2122. For example, it is possible to select a linear dimension that only snaps to end points.\nTo use a single snap type, select the required operation, for example, linear dimension (refer to Add Linear Dimensions for further information). Press Shift and simultaneously Right-click the drawing canvas. The PowerWheel\u2122 displays the snapping options:\n\nSelect the required snapping option. You are only able to snap to the selected option until the point is specified.\nP-Point\nSnaps to P-points of objects.\nFunctionality is available to snap to P-points that are located both on the geometry and outside of the geometry of an object.\nWhen hovering over the design geometry, special snap points are displayed as crosses on the drawing canvas indicating the P-point locations on the object.\nTo select P-points outside of the geometry of an object, you must first hover the mouse over the design geometry.\nInformation is displayed for the currently selected P-point. The example displays a selected P-point at the centre arc of a panel element.\nP-Line MidPoint\nSnaps to middle P-line points of objects.\nP-Line EndPoint\nSnaps to start and end P-line points of objects.\nItem\nSnaps to start or end points of object origins.\nOwner\nSnaps to the owning element of the currently selected objects.\nConnection\nSnaps to connection points of objects.\nConnection Create\nSnaps to the nearest connection points of objects.\nEndpoint\nSnaps to endpoints of objects.\nMidpoint\nSnaps to middle points of objects.\nCentre\nSnaps to centre points (for example, for circles arcs or ellipses).\nNearest\nSnaps to the nearest points of objects.\nPerpendicular\nSnaps to perpendicular points of objects.\nQuadrant\nSnaps to points representing quadrants of circles, arcs or ellipses.\nTangent\nSnaps to points of objects where the line connecting the point and the previous point is tangent to the objects.\nExtension\nThe cursor is attracted by virtual extensions of existing objects.\nParallel\nSnaps to points on a virtual line parallel to the indicated objects.\nNode\nSnaps to node points (for example, on text objects).\nIntersection\nSnaps to intersection points of objects.\nInsertion\nSnaps to insertion points of complex objects.\nPoint Cloud\nSnaps to points on laser data.\nClear All\nTurns off all snap points for an area of the window.\n\n\n\nAdd Linear Dimensions\nP-Point\nP-Line MidPoint\nP-Line EndPoint\nItem\nOwner\nConnection\nConnection Create\nEndpoint\nMidpoint\nCentre\nNearest\nPerpendicular\nQuadrant\nTangent\nExtension\nParallel\nNode\nIntersection\nInsertion\nPoint Cloud\nClear All\nAdd Linear Dimensions\nShift"}
{"Headers": "Set Colours, Line Types and Owners", "Content": "Sets the current colour, line type and owner for new objects.\nThe Current Colour, Current Line Type, Current Owner and Current Layer fields on the Active Properties window define the current colour, line type and owner for new objects. The properties can be modified using the drop-down lists in the Active Properties window. Refer to Active Properties for further information.\nThese properties can subsequently be changed using the Properties window.\n\n\n\nActive Properties\nProperties\nCurrent Colour\nCurrent Line Type\nCurrent Owner\nCurrent Layer\nActive Properties\nActive Properties\nProperties"}
{"Headers": "Add Construction Lines", "Content": "Adds construction lines to a drawing.\nNote:\nConstruction lines are drawn between two points on a drawing sheet. They can only be drawn if a frame is present.\n\n\n\nNote\n:"}
{"Headers": "Add Ray Lines", "Content": "Adds a ray line with two selected points.\nYou are prompted to Specify insertion point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the insertion point for the ray line.\nYou are then prompted to Specify direction point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the direction of the ray line. The ray line is drawn in the specified direction.\nThe prompt is repeated, allowing you to create multiple ray lines from the insertion point.\nInput F at the prompt and press Enter to end the command.\nThroughout the ray line creation process you can press ESC to cancel the command. Additional functionality is also available.\nFinish\nPress the down arrow key and select Finish to end the command.\nUndo\nPress the down arrow key and select Undo to undo the last action.\n\nFinish\nPress the down arrow key and select Finish to end the command.\nUndo\nPress the down arrow key and select Undo to undo the last action.\n\nThe new NOTE element displays in the Draw Explorer containing a STRAI element that represents each ray line.\n\nFinish\nPress the down arrow key and select Finish to end the command.\nUndo\nPress the down arrow key and select Undo to undo the last action.\n\n\n\nSpecify insertion point or <Finish>\nEnter\nSpecify direction point or <Finish>\nEnter\nF\nEnter\nESC\nFinish\nFinish\nUndo\nUndo"}
{"Headers": "Add XLines", "Content": "Adds an XLine to the drawing.\n\nNote:\nConstruction lines are drawn between two points on a drawing sheet. They can only be drawn if a frame is present.\n\n\n\nNote\n:"}
{"Headers": "Add Drawing Objects", "Content": "A number of drawing objects can be added to a drawing.\n\n\n"}
{"Headers": "Draw Lines", "Content": "Adds a line to a drawing.\n\n\n"}
{"Headers": "Draw Clouds and Outlines", "Content": "Adds a cloud or an outline to a drawing.\n\n\n"}
{"Headers": "Draw Circles", "Content": "Adds a circle to a drawing.\n\n\n"}
{"Headers": "Draw Rectangles and Diamonds", "Content": "Adds a rectangle or a diamond to a drawing.\n\n\n"}
{"Headers": "Draw Arcs", "Content": "Adds an arc to a drawing.\n\n\n"}
{"Headers": "Draw Equilateral Triangles", "Content": "Adds an equilateral triangle to a drawing.\n\n\n"}
{"Headers": "Draw Hexagons", "Content": "Adds a hexagon to a drawing.\n\n\n"}
{"Headers": "Draw Ellipses", "Content": "Adds an ellipse to a drawing.\n\n\n"}
{"Headers": "Draw Tangent Lines", "Content": "Adds a tangent line to a drawing.\n\n\n"}
{"Headers": "Draw Connectors", "Content": "Adds a connector to a drawing.\nIntelligent grip points can be used to connect the connector to an object, if the object is moved or modified, the connection is preserved. The connector is drawn using straight line segments.\nConnectors can be drawn using orthogonal connector mode. Refer to Status Bar for further information.\n\n\n\nStatus Bar\nStatus Bar"}
{"Headers": "Modify Drawing Objects", "Content": "Numerous facilities are available to modify drawing objects.\n\n\n"}
{"Headers": "Select Objects", "Content": "Selects multiple objects for modification.\nClick to identify an object for selection.\nAlternatively, a box can be drawn to select multiple objects.\nTo create a box in which all objects completely enclosed are selected, click the draw canvas and move the cursor from left to right. Click to confirm the selection.\nTo create a box in which all objects fully or partially enclosed are selected, click the drawing canvas and move the cursor from right to left. Click to confirm the selection.\nThe Properties window allows you to define multiple selection mode or single selection mode. Refer to Properties for further information.\nSelect an object to display the grip points. Refer to Modify Objects using Grip Points for further information.\n\nTo deselect all selected objects, press ESC.\nTo deselect a single object, hold down Shift and either click it or draw a box round it.\nMove Selected Objects\nMoves a selected object.\nClick to identify the object and drag the object to a new position.\nMultiple objects are moved as a group. The currently selected object is moved to the identified position, the relative position of all other selected objects is maintained.\nFunctionality is available to move objects in other ways. Refer to Modify Objects using Grip Points and Move Objects for further information.\nNote:\nIf required, the application can be configured so that the you must hold down Shift to select additional objects. Refer to Object Selection and Object Snap Settings for further information.\n\n\n\nProperties\nModify Objects using Grip Points\nObject Selection and Object Snap Settings\nModify Objects using Grip Points\nMove Objects\nProperties\nModify Objects using Grip Points\nESC\nShift\nNote\n:\nObject Selection and Object Snap Settings\nMove Selected Objects\nModify Objects using Grip Points\nMove Objects"}
{"Headers": "Modify Objects using Grip Points", "Content": "When an object is selected, the grip points display in blue. There are various types of grip point, for example, squares and diamonds.\nYou can manipulate a grip point to modify the appearance of an object.\n\nWhen a grip point is selected, the display colour changes to red.\n\n\n"}
{"Headers": "Modify Connectors", "Content": "A connector can be modified using grip points (refer to Modify Objects using Grip Points and additional grip points (refer to Additional Grips for further information).\nConnector vertices can be modified using the Vertex Editor window. Refer to Vertex Editor for further information.\nA connector can be modified using the Properties window. Refer to Properties for further information. A number of properties are connector specific.\n\nAlignment\nSelect Base from the drop-down list to align the bottom of the connector text with the connector.\nSelect BBody from the drop-down list to align the connector text above the connector.\nSelect HBody from the drop-down list to align the centre of the connector text with the connector.\nSelect TBody from the drop-down list to align the top of the connector text with the connector.\nChar height\nSelect By Style from the drop-down list to inherit the connector text character height from the visual style.\nInput a value in the field or select from the drop-down list to define the character height for the connector text.\nChar spacing\nSelect By Style from the drop-down list to inherit the connector text character spacing from the visual style.\nInput a value in the field or select from the drop-down list to define the character spacing for the connector text.\nFont\nSelect By Style from the drop-down list to inherit the text font from the visual style.\nSelect from the drop-down list to define the font for the connector text.\nJustification\nSelect Left from the drop-down list to left justify the connector text.\nSelect Right from the drop-down list to right justify the connector text.\nSelect Centre from the drop-down list to centre justify the connector text.\nLine spacing\nSelect By Style from the drop-down list to inherit the connector text line spacing from the visual style.\nInput a value in the field or select from the drop-down list to define the vertical line spacing for the connector text.\nRotation angle\nInput a value in the field to define the rotation angle for the connector text.\nText\nInput a value in the field to define the content for the connector text.\nClick to add intelligent text. Refer to Intelligent Text for further information.\nNote:\nThe connector has a DEXREF attribute which holds a reference to an external element. The intelligent text is evaluated against this external element if it is valid. There are two pseudo attributes on the connector CONSRF and CONERF, these hold the DEXREF of the symbols at the start and end of the connector respectively. The FROM command can be used to extract data about the DEXREF, CONSRF and CONERF (for example, #BORE<FR DEXREF>). There is a limitation on the intelligent text, it is not possible to travel the hierarchy from the DEXREF, CONSRF or CONERF. This means that while it is possible to display the owner of the DEXREF element, it is not possible to display any further information about the OWNER.\nText Colour\nSelect from the drop-down list to define the colour of the connector text.\nText Offset\nInput a value in the field or select from the drop-down list to define the text offset from the centre of the connector along the X axis and the Y axis.\nText segment\nSelect By Style from the drop-down list to inherit the connector text position from the visual style.\nSelect Start from the drop-down list to position connector text adjacent to the first connector segment.\nSelect Centre from the drop-down list to position connector text adjacent to the center connector segment.\nSelect End from the drop-down list to position connector text adjacent to the last connector segment\nIs major\nSelect By Style from the drop-down list to inherit the connector jump settings from the visual style.\nSelect Yes from the drop-down list to define the connector as dominant. A jump is not applied to the connector at connector intersections.\nSelect No from the drop-down list to define the connector as subordinate. A jump is applied to the connector at connector intersections.\nJumping glyph\nSelect By Style from the drop-down list to inherit the connector jump display settings from the visual style. The default jump display is indicated with a gap.\nSelect By Owner from the drop-down list to inherit the connector jump display settings from the owning element.\nSelect an image from the gallery to modify the connector jump display settings.\nJumping size\nSelect By Style from the drop-down list to inherit the connector jump size from the visual style.\nSelect By Owner from the drop-down list to inherit the connector jump size from the owning element.\nInput a value in the field or select a size from the drop-down list to modify the size of the connector jump.\nFlow\nSelect By Style from the drop-down list to inherit the connector flow direction from the visual style.\nSelect None from the drop-down list to modify the connector flow direction to no direction.\nSelect Forward from the drop-down list to modify the connector flow direction to forwards.\nSelect Back from the drop-down list to modify the connector flow direction to backwards.\nThe flow setting is created for use with asymmetric line styles or glyphs\nMarker Colour\nSelect By Style from the drop-down list to inherit the connector marker colour settings from the visual style.\nSelect a colour from the drop-down list to modify the connector marker colour.\nMarker glyph\nSelect By Style from the drop-down list to inherit the connector marker display settings from the visual style.\nSelect an image from the gallery to modify the connector marker display settings. A marker is positioned at each connector vertex point.\nMarker size\nSelect By Style from the drop-down list to inherit the connector marker size from the visual style.\nSelect By Owner from the drop-down list to inherit the connector marker size from the owning element.\nInput a value in the field or select a size from the drop-down list to modify the size of the connector marker.\nShield colour\nSelect By Style from the drop-down list to inherit the connector shield colour settings from the visual style.\nSelect a colour from the drop-down list to modify the connector shield colour.\nShield diameter\nSelect By Style from the drop-down list to inherit the connector shield diameter size from the visual style.\nInput a value in the field or select a size from the drop-down list to modify the diameter of the connector shield.\nShield line type\nSelect By Style from the drop-down list to inherit the connector shield line style from the visual style.\nSelect an image from the gallery to modify the connector shield line style settings.\nAlignment\nSelect Base from the drop-down list to align the bottom of the connector text with the connector.\n\nSelect BBody from the drop-down list to align the connector text above the connector.\n\nSelect HBody from the drop-down list to align the centre of the connector text with the connector.\n\nSelect TBody from the drop-down list to align the top of the connector text with the connector.\n\nChar height\nSelect By Style from the drop-down list to inherit the connector text character height from the visual style.\nInput a value in the field or select from the drop-down list to define the character height for the connector text.\nChar spacing\nSelect By Style from the drop-down list to inherit the connector text character spacing from the visual style.\nInput a value in the field or select from the drop-down list to define the character spacing for the connector text.\nFont\nSelect By Style from the drop-down list to inherit the text font from the visual style.\nSelect from the drop-down list to define the font for the connector text.\nJustification\nSelect Left from the drop-down list to left justify the connector text.\nSelect Right from the drop-down list to right justify the connector text.\nSelect Centre from the drop-down list to centre justify the connector text.\nLine spacing\nSelect By Style from the drop-down list to inherit the connector text line spacing from the visual style.\nInput a value in the field or select from the drop-down list to define the vertical line spacing for the connector text.\nRotation angle\nInput a value in the field to define the rotation angle for the connector text.\nText\nInput a value in the field to define the content for the connector text.\nClick to add intelligent text. Refer to Intelligent Text for further information.\nText Colour\nSelect from the drop-down list to define the colour of the connector text.\nText Offset\nInput a value in the field or select from the drop-down list to define the text offset from the centre of the connector along the X axis and the Y axis.\nText segment\nSelect By Style from the drop-down list to inherit the connector text position from the visual style.\nSelect Start from the drop-down list to position connector text adjacent to the first connector segment.\n\nSelect Centre from the drop-down list to position connector text adjacent to the center connector segment.\n\nSelect End from the drop-down list to position connector text adjacent to the last connector segment\n\nIs major\nSelect By Style from the drop-down list to inherit the connector jump settings from the visual style.\nSelect Yes from the drop-down list to define the connector as dominant. A jump is not applied to the connector at connector intersections.\nSelect No from the drop-down list to define the connector as subordinate. A jump is applied to the connector at connector intersections.\n\nJumping glyph\nSelect By Style from the drop-down list to inherit the connector jump display settings from the visual style. The default jump display is indicated with a gap.\nSelect By Owner from the drop-down list to inherit the connector jump display settings from the owning element.\nSelect an image from the gallery to modify the connector jump display settings.\nJumping size\nSelect By Style from the drop-down list to inherit the connector jump size from the visual style.\nSelect By Owner from the drop-down list to inherit the connector jump size from the owning element.\nInput a value in the field or select a size from the drop-down list to modify the size of the connector jump.\nFlow\nSelect By Style from the drop-down list to inherit the connector flow direction from the visual style.\nSelect None from the drop-down list to modify the connector flow direction to no direction.\nSelect Forward from the drop-down list to modify the connector flow direction to forwards.\nSelect Back from the drop-down list to modify the connector flow direction to backwards.\nThe flow setting is created for use with asymmetric line styles or glyphs\nMarker Colour\nSelect By Style from the drop-down list to inherit the connector marker colour settings from the visual style.\nSelect a colour from the drop-down list to modify the connector marker colour.\nMarker glyph\nSelect By Style from the drop-down list to inherit the connector marker display settings from the visual style.\nSelect an image from the gallery to modify the connector marker display settings. A marker is positioned at each connector vertex point.\n\nMarker size\nSelect By Style from the drop-down list to inherit the connector marker size from the visual style.\nSelect By Owner from the drop-down list to inherit the connector marker size from the owning element.\nInput a value in the field or select a size from the drop-down list to modify the size of the connector marker.\nShield colour\nSelect By Style from the drop-down list to inherit the connector shield colour settings from the visual style.\nSelect a colour from the drop-down list to modify the connector shield colour.\nShield diameter\nSelect By Style from the drop-down list to inherit the connector shield diameter size from the visual style.\nInput a value in the field or select a size from the drop-down list to modify the diameter of the connector shield.\nShield line type\nSelect By Style from the drop-down list to inherit the connector shield line style from the visual style.\nSelect an image from the gallery to modify the connector shield line style settings.\n\nAlignment\nSelect Base from the drop-down list to align the bottom of the connector text with the connector.\nSelect BBody from the drop-down list to align the connector text above the connector.\nSelect HBody from the drop-down list to align the centre of the connector text with the connector.\nSelect TBody from the drop-down list to align the top of the connector text with the connector.\nChar height\nSelect By Style from the drop-down list to inherit the connector text character height from the visual style.\nInput a value in the field or select from the drop-down list to define the character height for the connector text.\nChar spacing\nSelect By Style from the drop-down list to inherit the connector text character spacing from the visual style.\nInput a value in the field or select from the drop-down list to define the character spacing for the connector text.\nFont\nSelect By Style from the drop-down list to inherit the text font from the visual style.\nSelect from the drop-down list to define the font for the connector text.\nJustification\nSelect Left from the drop-down list to left justify the connector text.\nSelect Right from the drop-down list to right justify the connector text.\nSelect Centre from the drop-down list to centre justify the connector text.\nLine spacing\nSelect By Style from the drop-down list to inherit the connector text line spacing from the visual style.\nInput a value in the field or select from the drop-down list to define the vertical line spacing for the connector text.\nRotation angle\nInput a value in the field to define the rotation angle for the connector text.\nText\nInput a value in the field to define the content for the connector text.\nClick to add intelligent text. Refer to Intelligent Text for further information.\nNote:\nThe connector has a DEXREF attribute which holds a reference to an external element. The intelligent text is evaluated against this external element if it is valid. There are two pseudo attributes on the connector CONSRF and CONERF, these hold the DEXREF of the symbols at the start and end of the connector respectively. The FROM command can be used to extract data about the DEXREF, CONSRF and CONERF (for example, #BORE<FR DEXREF>). There is a limitation on the intelligent text, it is not possible to travel the hierarchy from the DEXREF, CONSRF or CONERF. This means that while it is possible to display the owner of the DEXREF element, it is not possible to display any further information about the OWNER.\nText Colour\nSelect from the drop-down list to define the colour of the connector text.\nText Offset\nInput a value in the field or select from the drop-down list to define the text offset from the centre of the connector along the X axis and the Y axis.\nText segment\nSelect By Style from the drop-down list to inherit the connector text position from the visual style.\nSelect Start from the drop-down list to position connector text adjacent to the first connector segment.\nSelect Centre from the drop-down list to position connector text adjacent to the center connector segment.\nSelect End from the drop-down list to position connector text adjacent to the last connector segment\nIs major\nSelect By Style from the drop-down list to inherit the connector jump settings from the visual style.\nSelect Yes from the drop-down list to define the connector as dominant. A jump is not applied to the connector at connector intersections.\nSelect No from the drop-down list to define the connector as subordinate. A jump is applied to the connector at connector intersections.\nJumping glyph\nSelect By Style from the drop-down list to inherit the connector jump display settings from the visual style. The default jump display is indicated with a gap.\nSelect By Owner from the drop-down list to inherit the connector jump display settings from the owning element.\nSelect an image from the gallery to modify the connector jump display settings.\nJumping size\nSelect By Style from the drop-down list to inherit the connector jump size from the visual style.\nSelect By Owner from the drop-down list to inherit the connector jump size from the owning element.\nInput a value in the field or select a size from the drop-down list to modify the size of the connector jump.\nFlow\nSelect By Style from the drop-down list to inherit the connector flow direction from the visual style.\nSelect None from the drop-down list to modify the connector flow direction to no direction.\nSelect Forward from the drop-down list to modify the connector flow direction to forwards.\nSelect Back from the drop-down list to modify the connector flow direction to backwards.\nThe flow setting is created for use with asymmetric line styles or glyphs\nMarker Colour\nSelect By Style from the drop-down list to inherit the connector marker colour settings from the visual style.\nSelect a colour from the drop-down list to modify the connector marker colour.\nMarker glyph\nSelect By Style from the drop-down list to inherit the connector marker display settings from the visual style.\nSelect an image from the gallery to modify the connector marker display settings. A marker is positioned at each connector vertex point.\nMarker size\nSelect By Style from the drop-down list to inherit the connector marker size from the visual style.\nSelect By Owner from the drop-down list to inherit the connector marker size from the owning element.\nInput a value in the field or select a size from the drop-down list to modify the size of the connector marker.\nShield colour\nSelect By Style from the drop-down list to inherit the connector shield colour settings from the visual style.\nSelect a colour from the drop-down list to modify the connector shield colour.\nShield diameter\nSelect By Style from the drop-down list to inherit the connector shield diameter size from the visual style.\nInput a value in the field or select a size from the drop-down list to modify the diameter of the connector shield.\nShield line type\nSelect By Style from the drop-down list to inherit the connector shield line style from the visual style.\nSelect an image from the gallery to modify the connector shield line style settings.\nNote:\nThe connector has a DEXREF attribute which holds a reference to an external element. The intelligent text is evaluated against this external element if it is valid. There are two pseudo attributes on the connector CONSRF and CONERF, these hold the DEXREF of the symbols at the start and end of the connector respectively. The FROM command can be used to extract data about the DEXREF, CONSRF and CONERF (for example, #BORE<FR DEXREF>). There is a limitation on the intelligent text, it is not possible to travel the hierarchy from the DEXREF, CONSRF or CONERF. This means that while it is possible to display the owner of the DEXREF element, it is not possible to display any further information about the OWNER.\n\n\n\nModify Objects using Grip Points\nVertex Editor\nProperties\nIntelligent Text\nModify Objects using Grip Points\nAdditional Grips\nVertex Editor\nVertex Editor\nProperties\nProperties\nAlignment\nBase\nBBody\nHBody\nTBody\nChar height\nBy Style\nChar spacing\nBy Style\nFont\nBy Style\nJustification\nLeft\nRight\nCentre\nLine spacing\nBy Style\nRotation angle\nText\nIntelligent Text\nNote\n:\nText Colour\nText Offset\nText segment\nBy Style\nStart\nCentre\nEnd\nIs major\nBy Style\nYes\nNo\nJumping glyph\nBy Style\nBy Owner\nJumping size\nBy Style\nBy Owner\nFlow\nBy Style\nNone\nForward\nBack\nMarker Colour\nBy Style\nMarker glyph\nBy Style\nMarker size\nBy Style\nBy Owner\nShield colour\nBy Style\nShield diameter\nBy Style\nShield line type\nBy Style"}
{"Headers": "Move Objects", "Content": "Moves a selected object.\nOther methods for moving objects are available. Refer to Select Objects and Move Objects using Grip Points for further information.\n\n\n\nSelect Objects\nMove Objects using Grip Points\nSelect Objects\nMove Objects using Grip Points"}
{"Headers": "Copy Objects", "Content": "Copies a selected object.\n\n\n"}
{"Headers": "Paste Objects", "Content": "Pastes a selected object.\n\n\n"}
{"Headers": "Stretch Objects", "Content": "Stretches objects using a box selection or polygon selection.\nObjects can also be stretched by manipulating grips. Refer to Stretch Objects using Endpoints and Stretch Objects using Midpoints for further information.\n\n\n\nStretch Objects using Endpoints\nStretch Objects using Midpoints\nStretch Objects using Endpoints\nStretch Objects using Midpoints"}
{"Headers": "Rotate Objects", "Content": "Rotates objects using a base point or around a base angle.\nNote:\nObjects can also be rotated by manipulating grips. Refer to Rotate Objects using Grip Points for further information.\n\n\n\nRotate Objects using Grip Points\nNote\n:\nRotate Objects using Grip Points"}
{"Headers": "Mirror Objects", "Content": "Creates a mirrored copy of a selected object.\nYou are prompted to Select objects to mirror\nClick to identify the objects to mirror and press Enter.\nYou are then prompted to Specify the first point or\nInput values in the dimension fields and press Enter or click to identify the point around which the objects are mirrored.\nYou are then prompted to Specify the second point or\nInput values in the dimension fields and press Enter or click to specify the location of the mirrored objects.\nA copy of the object is mirrored at the specified angle and the command ends automatically.\nThroughout the mirroring process you can press ESC to cancel the command. Additional functionality is also available.\nObject\nPress the down arrow key and select Object to re-select the objects to mirror.\nNo-copy\nPress the down arrow key and select No-copy to mirror the selected objects without keeping a copy of the original.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nObject\nPress the down arrow key and select Object to re-select the objects to mirror.\nNo-copy\nPress the down arrow key and select No-copy to mirror the selected objects without keeping a copy of the original.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nObject\nPress the down arrow key and select Object to re-select the objects to mirror.\nNo-copy\nPress the down arrow key and select No-copy to mirror the selected objects without keeping a copy of the original.\nBack\nPress the down arrow key and select Back to undo the last action.\nNote:\nThe prompt does not display if one or more objects are already selected.\n\n\n\nSelect objects to mirror\nNote\n:\nEnter\nSpecify the first point or\nEnter\nSpecify the second point or\nEnter\nESC\nObject\nObject\nNo-copy\nNo-copy\nBack\nBack"}
{"Headers": "Scale Objects", "Content": "Sets the overall size of an object.\n\n\n"}
{"Headers": "Offset Objects", "Content": "Creates objects using an offset position from a specified object.\n\n\n"}
{"Headers": "Create Arrays of Objects", "Content": "Creates a number of copied objects using a specified offset distance.\n\nIf one or more objects are selected before the Array window is opened, the array is created from them.\nIf objects are not selected before the Array window is opened, the OK button is greyed out and becomes active when one or more objects are selected.\nTo select objects, or to select different objects from those selected when the window was opened, click in the Select objects part of the Array window.\nThe Array window is closed and you are prompted to Select objects\nClick to identify the required objects and press Enter.\nYou are returned to the Array window.\nSelect the Rectangular tab to create a Rectangular Array.\nSpecify both offsets of the array on screen\nClick to specify both row and column offsets on the drawing canvas. Refer to Specify Row and Column Offsets on Drawing Canvas for further information.\nColumns\nInput the required number of columns in the field.\nColumn offset\nInput a value in the field to define the amount by which array columns are offset from the selected objects and each other.\nAlternatively, this can be specified on the drawing canvas. Refer to Specify Column Offset on Drawing Canvas for further information.\nRows\nInput the required number of rows.\nRow offset\nInput a value in the field to define the amount by which array rows are offset from the selected objects and each other.\nAlternatively, this can be specified on the drawing canvas. Refer to Specify Row Offset on Drawing Canvas for further information.\nAngle of array\nInput the array angle in the field.\nAlternatively, this can be specified on the drawing canvas. Refer to Specify Angle of Array on Drawing Canvas for further information.\nPreview\nClick to display a preview of the array with the current settings. The Array window is closed and the preview displays on the drawing canvas.\nPress ESC to return to the Array window or Enter to create the array.\n\nSpecify both offsets of the array on screen\nClick to specify both row and column offsets on the drawing canvas. Refer to Specify Row and Column Offsets on Drawing Canvas for further information.\n\nColumns\nInput the required number of columns in the field.\n\nColumn offset\nInput a value in the field to define the amount by which array columns are offset from the selected objects and each other.\nAlternatively, this can be specified on the drawing canvas. Refer to Specify Column Offset on Drawing Canvas for further information.\n\nRows\nInput the required number of rows.\n\nRow offset\nInput a value in the field to define the amount by which array rows are offset from the selected objects and each other.\nAlternatively, this can be specified on the drawing canvas. Refer to Specify Row Offset on Drawing Canvas for further information.\n\nAngle of array\nInput the array angle in the field.\nAlternatively, this can be specified on the drawing canvas. Refer to Specify Angle of Array on Drawing Canvas for further information.\n\nPreview\nClick to display a preview of the array with the current settings. The Array window is closed and the preview displays on the drawing canvas.\nPress ESC to return to the Array window or Enter to create the array.\n\nSpecify both offsets of the array on screen\nClick to specify both row and column offsets on the drawing canvas. Refer to Specify Row and Column Offsets on Drawing Canvas for further information.\nColumns\nInput the required number of columns in the field.\nColumn offset\nInput a value in the field to define the amount by which array columns are offset from the selected objects and each other.\nAlternatively, this can be specified on the drawing canvas. Refer to Specify Column Offset on Drawing Canvas for further information.\nRows\nInput the required number of rows.\nRow offset\nInput a value in the field to define the amount by which array rows are offset from the selected objects and each other.\nAlternatively, this can be specified on the drawing canvas. Refer to Specify Row Offset on Drawing Canvas for further information.\nAngle of array\nInput the array angle in the field.\nAlternatively, this can be specified on the drawing canvas. Refer to Specify Angle of Array on Drawing Canvas for further information.\nPreview\nClick to display a preview of the array with the current settings. The Array window is closed and the preview displays on the drawing canvas.\nPress ESC to return to the Array window or Enter to create the array.\nNote:\nThe objects from which the array is created can be selected before or after the Array window is opened. Refer to Select Objects for further information.\n\n\n\nSelect Objects\nSpecify Row and Column Offsets on Drawing Canvas\nSpecify Column Offset on Drawing Canvas\nSpecify Row Offset on Drawing Canvas\nSpecify Angle of Array on Drawing Canvas\nNote\n:\nArray\nSelect Objects\nArray\nArray\nOK\nSelect objects\nArray\nSelect objects\nEnter\nArray\nRectangular\nSpecify both offsets of the array on screen\nSpecify Row and Column Offsets on Drawing Canvas\nColumns\nColumn offset\nSpecify Column Offset on Drawing Canvas\nRows\nRow offset\nSpecify Row Offset on Drawing Canvas\nAngle of array\nSpecify Angle of Array on Drawing Canvas\nPreview\nArray\nESC\nArray\nEnter"}
{"Headers": "Change Length of Objects", "Content": "Sets the length of an object.\n\n\n"}
{"Headers": "Explode and Merge Objects", "Content": "Explodes multiple objects or outline elements into the primitive components that the objects are composed of or merges multiple elements and forms them into an outline element.\n\n\n"}
{"Headers": "Trim and Extend Objects", "Content": "Trims or extends objects to a specified point.\n\n\n"}
{"Headers": "Fillet Objects", "Content": "Applies a fillet to objects.\n\n\n"}
{"Headers": "Chamfer Objects", "Content": "Applies a chamfer to objects.\n\n\n"}
{"Headers": "Send to Back", "Content": "Moves objects to the back of the drawing canvas, objects are positioned behind overlapping objects.\nYou are prompted to Select entities to send to back\nClick to identify the objects to move and press Enter.\nThe objects are moved and the command ends automatically.\n\nNote:\nThe prompt does not display if one or more objects are already selected.\n\n\n\nSelect entities to send to back\nNote\n:\nEnter"}
{"Headers": "Bring to Front", "Content": "Moves objects to the front of the drawing canvas, objects are positioned in front of overlapping objects.\nYou are prompted to Select entities to bring to front\nClick to identify the objects to move and press Enter.\nThe objects are moved and the command ends automatically.\n\nNote:\nThe prompt does not display if one or more objects are already selected.\n\n\n\nSelect entities to bring to front\nNote\n:\nEnter"}
{"Headers": "Align Views", "Content": "Aligns views on the drawing canvas, views can be aligned horizontally or vertically. The alignment is with respect to the model coordinate system rather than the view frames. Using this function, it is possible, for example, to have Z=0 horizontally aligned to the selected views.\nYou are prompted to Specify alignment mode <Auto>\nPress Enter to select the auto alignment mode.\nYou are then prompted to Select view\nClick to identify the reference view to align other views to.\nYou are then prompted to Select views to align\nClick to identify the views to align and press Enter.\nThe views are aligned and the command ends automatically.\nThroughout the align views process you can press ESC to cancel the command. Additional functionality is also available.\nVertical\nPress the down arrow key and select Vertical to align the views vertically.\nHorizontal\nPress the down arrow key and select Horizontal to align the views horizontally.\nAuto\nPress the down arrow key and select Auto to align the views automatically. The views are aligned horizontally or vertically depending on the original positions of the views on the sheet.\n\nVertical\nPress the down arrow key and select Vertical to align the views vertically.\nHorizontal\nPress the down arrow key and select Horizontal to align the views horizontally.\nAuto\nPress the down arrow key and select Auto to align the views automatically. The views are aligned horizontally or vertically depending on the original positions of the views on the sheet.\n\nExample 1: Horizontal alignment. The Z-axes are aligned, Z=0 is on a horizontal line.\nIt is possible to align a view with different view directions which works well if the views are aligned along a common coordinate axis. The example below displays one view looking down (-Z) and one view looking Y. Both views have the X-axis in a horizontal direction (indicated on the grid ruler). Aligning the views vertically positions the frames (X-coordinate) correctly below each other:\n\nExample 2: Vertical alignment. The X-axes are aligned. For example, the FR160 grid positions are exactly below each other.\nAligning the above views horizontally does not give the obvious coordinate matching since the vertical grid ruler represents different coordinate axes, Y-axis and Z-axis:\n\nVertical\nPress the down arrow key and select Vertical to align the views vertically.\nHorizontal\nPress the down arrow key and select Horizontal to align the views horizontally.\nAuto\nPress the down arrow key and select Auto to align the views automatically. The views are aligned horizontally or vertically depending on the original positions of the views on the sheet.\nNote:\nThe prompt does not display if a view is already selected.\nNote:\nOnly views with the same scale as the reference view can be selected.\n\n\n\nSpecify alignment mode <Auto>\nEnter\nSelect view\nNote\nSelect views to align\nNote\nEnter\nESC\nVertical\nVertical\nHorizontal\nHorizontal\nAuto\nAuto"}
{"Headers": "Determine Distances, Angles and Points", "Content": "Measures the distance or angle between two points or the coordinates of a specified point using different methods.\n\n\n"}
{"Headers": "Measure Distance between Two Points", "Content": "Measures the distance between two points.\nYou are prompted to Specify the first point\nInput values in the dimension fields and press Enter or click to identify the point to measure from.\nYou are then prompted to Specify the second point or\nInput values in the dimension fields and press Enter or click to identify the point to measure to.\nThe context editor displays the distance between the two points.\nInput F at the prompt and press Enter to end the command.\nThroughout the measure process you can press ESC to cancel the command. Additional functionality is also available.\nYou can press the Spacebar to cancel the command. Press the Spacebar again to activate a new measure distance process.\nYou are prompted to Specify the first point\nAlternatively, you can activate the measure distance functionality by using an in canvas command. Type DI and press Enter.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nAxes distance\nPress the down arrow key and select Axes distance to turn the axes display on or off on the drawing canvas.\nChange unit\nPress the down arrow key and select Change unit to display the available units of measure.\nCopy to clipboard\nPress the down arrow key and select Copy to clipboard to copy the position value to the clipboard ready for a later paste operation.\nFinish\nPress the down arrow key and select Finish to end the command.\nCurrent units\nPress the down arrow key and select Current units to display the measured distance in the current default units.\nMm\nPress the down arrow key and select Mm to display the measured distance in millimeters.\nCm\nPress the down arrow key and select Cm to display the measured distance in centimeters.\nMetre\nPress the down arrow key and select Metre to display the measured distance in meters.\nKm\nPress the down arrow key and select Km to display the measured distance in kilometers.\nThou\nPress the down arrow key and select Thou to display the measured distance in thou.\nFinch\nPress the down arrow key and select Finch to display the measured distance in feet and inches.\nInch\nPress the down arrow key and select Inch to display the measured distance in inches.\nFt\nPress the down arrow key and select Ft to display the measured distance in feet.\nYd\nPress the down arrow key and select Yd to display the measured distance in yards.\nMile\nPress the down arrow key and select Mile to display the measured distance in miles.\n\n\nBack\nPress the down arrow key and select Back to undo the last action.\nAxes distance\nPress the down arrow key and select Axes distance to turn the axes display on or off on the drawing canvas.\nChange unit\nPress the down arrow key and select Change unit to display the available units of measure.\nCopy to clipboard\nPress the down arrow key and select Copy to clipboard to copy the position value to the clipboard ready for a later paste operation.\nFinish\nPress the down arrow key and select Finish to end the command.\nCurrent units\nPress the down arrow key and select Current units to display the measured distance in the current default units.\nMm\nPress the down arrow key and select Mm to display the measured distance in millimeters.\nCm\nPress the down arrow key and select Cm to display the measured distance in centimeters.\nMetre\nPress the down arrow key and select Metre to display the measured distance in meters.\nKm\nPress the down arrow key and select Km to display the measured distance in kilometers.\nThou\nPress the down arrow key and select Thou to display the measured distance in thou.\nFinch\nPress the down arrow key and select Finch to display the measured distance in feet and inches.\nInch\nPress the down arrow key and select Inch to display the measured distance in inches.\nFt\nPress the down arrow key and select Ft to display the measured distance in feet.\nYd\nPress the down arrow key and select Yd to display the measured distance in yards.\nMile\nPress the down arrow key and select Mile to display the measured distance in miles.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nAxes distance\nPress the down arrow key and select Axes distance to turn the axes display on or off on the drawing canvas.\nChange unit\nPress the down arrow key and select Change unit to display the available units of measure.\nCopy to clipboard\nPress the down arrow key and select Copy to clipboard to copy the position value to the clipboard ready for a later paste operation.\nFinish\nPress the down arrow key and select Finish to end the command.\nCurrent units\nPress the down arrow key and select Current units to display the measured distance in the current default units.\nMm\nPress the down arrow key and select Mm to display the measured distance in millimeters.\nCm\nPress the down arrow key and select Cm to display the measured distance in centimeters.\nMetre\nPress the down arrow key and select Metre to display the measured distance in meters.\nKm\nPress the down arrow key and select Km to display the measured distance in kilometers.\nThou\nPress the down arrow key and select Thou to display the measured distance in thou.\nFinch\nPress the down arrow key and select Finch to display the measured distance in feet and inches.\nInch\nPress the down arrow key and select Inch to display the measured distance in inches.\nFt\nPress the down arrow key and select Ft to display the measured distance in feet.\nYd\nPress the down arrow key and select Yd to display the measured distance in yards.\nMile\nPress the down arrow key and select Mile to display the measured distance in miles.\n\n\n\nSpecify the first point\nEnter\nSpecify the second point or\nEnter\nF\nEnter\nESC\nSpacebar\n\nSpacebar\n\nSpecify the first point\nDI\nEnter\nBack\nBack\nAxes distance\nAxes distance\nChange unit\nChange unit\nCopy to clipboard\nCopy to clipboard\nFinish\nFinish\nCurrent units\nCurrent units\nMm\nMm\nCm\nCm\nMetre\nMetre\nKm\nKm\nThou\nThou\nFinch\nFinch\nInch\nInch\nFt\nFt\nYd\nYd\nMile\nMile"}
{"Headers": "Measure Cumulative Lengths of Objects", "Content": "Measures the cumulative length of objects.\nYou are then prompted to Select objects\nClick to identify the required objects and press Enter.\n\nThe context editor and message bar display the cumulative length of the currently selected measureable objects.\nInput F at the prompt and press Enter to end the command.\nThroughout the measuring process you can press ESC to cancel the command. Additional functionality is also available.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nSelect objects\nEnter\nF\nEnter\nESC\nBack\nBack\nFinish\nFinish"}
{"Headers": "Display Point Coordinates", "Content": "Displays the coordinates of a specified point.\nYou are prompted to Specify point\nClick to identify the required point.\nThe context editor and message bar display the coordinates of the selected point.\nInput F at the prompt and press Enter to end the command.\nThroughout the display process you can press ESC to cancel the command. Additional functionality is also available.\nYou can activate the query position functionality by using an in canvas command. Type ID and press Enter.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nCopy to clipboard\nPress the down arrow key and select Copy to clipboard to copy the measured value to the clipboard ready for a later paste operation.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nCopy to clipboard\nPress the down arrow key and select Copy to clipboard to copy the measured value to the clipboard ready for a later paste operation.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nBack\nPress the down arrow key and select Back to undo the last action.\nCopy to clipboard\nPress the down arrow key and select Copy to clipboard to copy the measured value to the clipboard ready for a later paste operation.\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nSpecify point\nF\nEnter\nESC\nID\nEnter\nBack\nBack\nCopy to clipboard\nCopy to clipboard\nFinish\nFinish"}
{"Headers": "Add Annotation", "Content": "Draw contains various labelling and annotation facilities.\nWhen a 2D drafting element, for example, an annotation is added to a Sheet or View that does not own any Sheet Note or View Note elements, a new note is automatically created. The 2D drafting element is automatically placed under the new note.\nIf the Sheet/View owns a single note, the new element is automatically placed under that note.\nIf the Sheet/View owns multiple notes, the new element is added either to the currently selected note or if no note is selected, the first note listed in the Draw Explorer.\n\n\n"}
{"Headers": "Dimensions", "Content": "Views can be annotated with the following types of dimensions: Linear (LDIM), Angular (ADIM), Radial (RDIM) and Pitch Circle Diameter (PDIM).\nDimension\nExample\nLinear\nAngular\nRadial\nPitched Circle\nDimension\nExample\nLinear\n\nAngular\n\nRadial\n\nPitched Circle\n\n\nDimension\nExample\nLinear\nAngular\nRadial\nPitched Circle\n\n\n\nDimension\nExample\nLinear\nAngular\nRadial\nPitched Circle"}
{"Headers": "Add Linear Dimensions", "Content": "Adds linear dimensions to a view.\nYou are prompted to Specify the dimension point or <Type>\nInput values in the dimension fields and press Enter or click to identify the point to measure from.\nYou are then prompted to Specify the dimension point or\nInput values in the dimension fields and press Enter or click to identify the first point to measure to.\nYou are then prompted to Specify the dimension line position or\nInput values in the dimension fields and press Enter or click to identify the position of the dimension line.\nYou are then prompted to Specify the dimension point or <Finish>\nThe prompt is repeated, allowing you to create multiple linear dimensions.\nInput F at the prompt and press Enter to end the command.\nThroughout the linear dimension creation process you can press ESC to cancel the command. Additional functionality is also available.\nOrientation\nPress the down arrow key and select Orientation to specify the orientation of the linear dimension.\nYou are prompted to Select option <Orthogonal>\nInput A at the prompt and press Enter to specify the dimension orientation as aligned.\nAlternatively, input O at the prompt and press Enter to specify the dimension orientation as orthogonal.\nType\nPress the down arrow key and select Type to specify the type of linear dimension.\nSelect option <Chained>\nInput B at the prompt and press Enter to specify the dimension type as baseline.\nAlternatively, input C at the prompt and press Enter to specify the dimension type as chained.\nAlternatively, input O at the prompt and press Enter to specify the dimension type as combined.\nDirection\nPress the down arrow key and select Direction to specify the direction of the dimension.\nYou are prompted to Select option <Left>\nInput L at the prompt and press Enter to specify the dimension direction as left.\nAlternatively, input R at the prompt and press Enter to specify the dimension direction as right.\nThe option is only available for Combined Left, Combined Right, Baseline Left, and Baseline Right linear dimension types.\nPosition\nPress the down arrow key and select Position to specify the position of the linear dimension connection point.\nSelect option <Point>\nInput A at the prompt and press Enter to position the linear dimension connection point after a specified snap point.\nAlternatively, input B at the prompt and press Enter to position the linear dimension connection point before a specified snap point.\nAlternatively, input P at the prompt and press Enter to position the linear dimension connection point at a specified snap point.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nOrientation\nPress the down arrow key and select Orientation to specify the orientation of the linear dimension.\nYou are prompted to Select option <Orthogonal>\nInput A at the prompt and press Enter to specify the dimension orientation as aligned.\nAlternatively, input O at the prompt and press Enter to specify the dimension orientation as orthogonal.\nType\nPress the down arrow key and select Type to specify the type of linear dimension.\nSelect option <Chained>\nInput B at the prompt and press Enter to specify the dimension type as baseline.\nAlternatively, input C at the prompt and press Enter to specify the dimension type as chained.\nAlternatively, input O at the prompt and press Enter to specify the dimension type as combined.\nDirection\nPress the down arrow key and select Direction to specify the direction of the dimension.\nYou are prompted to Select option <Left>\nInput L at the prompt and press Enter to specify the dimension direction as left.\nAlternatively, input R at the prompt and press Enter to specify the dimension direction as right.\nThe option is only available for Combined Left, Combined Right, Baseline Left, and Baseline Right linear dimension types.\nPosition\nPress the down arrow key and select Position to specify the position of the linear dimension connection point.\nSelect option <Point>\nInput A at the prompt and press Enter to position the linear dimension connection point after a specified snap point.\nAlternatively, input B at the prompt and press Enter to position the linear dimension connection point before a specified snap point.\nAlternatively, input P at the prompt and press Enter to position the linear dimension connection point at a specified snap point.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nThe new LDIM element displays in the Draw Explorer containing a DPOI element that represents each dimension point.\n\nOrthogonal Chained\n\nAligned Chained\n\nCombined Left\n\nCombined Right\n\nAligned Combined\n\nBaseline Left\n\nBaseline Right\n\nAligned Baseline\n\nOrientation\nPress the down arrow key and select Orientation to specify the orientation of the linear dimension.\nYou are prompted to Select option <Orthogonal>\nInput A at the prompt and press Enter to specify the dimension orientation as aligned.\nAlternatively, input O at the prompt and press Enter to specify the dimension orientation as orthogonal.\nType\nPress the down arrow key and select Type to specify the type of linear dimension.\nSelect option <Chained>\nInput B at the prompt and press Enter to specify the dimension type as baseline.\nAlternatively, input C at the prompt and press Enter to specify the dimension type as chained.\nAlternatively, input O at the prompt and press Enter to specify the dimension type as combined.\nDirection\nPress the down arrow key and select Direction to specify the direction of the dimension.\nYou are prompted to Select option <Left>\nInput L at the prompt and press Enter to specify the dimension direction as left.\nAlternatively, input R at the prompt and press Enter to specify the dimension direction as right.\nThe option is only available for Combined Left, Combined Right, Baseline Left, and Baseline Right linear dimension types.\nPosition\nPress the down arrow key and select Position to specify the position of the linear dimension connection point.\nSelect option <Point>\nInput A at the prompt and press Enter to position the linear dimension connection point after a specified snap point.\nAlternatively, input B at the prompt and press Enter to position the linear dimension connection point before a specified snap point.\nAlternatively, input P at the prompt and press Enter to position the linear dimension connection point at a specified snap point.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nSpecify the dimension point or <Type>\nEnter\nSpecify the dimension point or\nEnter\nSpecify the dimension line position or\nEnter\nSpecify the dimension point or <Finish>\nF\nEnter\nESC\nOrientation\nOrientation\nSelect option <Orthogonal>\nA\nEnter\nO\nEnter\nType\nType\nSelect option <Chained>\nB\nEnter\nC\nEnter\nO\nEnter\nDirection\nDirection\nSelect option <Left>\nL\nEnter\nR\nEnter\nCombined\nLeft\nCombined Right\nBaseline Left\nBaseline Right\nPosition\nPosition\nSelect option <Point>\nA\nEnter\nB\nEnter\nP\nEnter\nBack\nFinish\nFinish\nOrthogonal Chained\nAligned Chained\nCombined Left\nCombined Right\nAligned Combined\nBaseline Left\nBaseline Right\nAligned Baseline"}
{"Headers": "Add Angular Dimensions", "Content": "Adds angular dimensions to a view.\nYou are prompted to Specify the dimension position point or <Type>\nInput values in the dimension fields and press Enter or click to identify the center point of the annotation.\nYou are then prompted to Specify the dimension position point or <Direction>\nInput values in the dimension fields and press Enter or click to identify a point to measure from.\nYou are then prompted to Specify the dimension point or <Direction>\nInput values in the dimension fields and press Enter or click to identify a point to measure to.\nYou are then prompted to Specify the dimension line position or\nInput values in the dimension fields and press Enter or click to identify the position of the dimension line.\nYou are then prompted to Specify the dimension point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the position of an additional angular dimension.\nThe prompt is repeated, allowing you to create multiple angular dimensions.\nInput F at the prompt and press Enter to end the command.\nThroughout the angular dimension creation process you can press ESC to cancel the command. Additional functionality is also available.\nType\nPress the down arrow key and select Type to specify the type of angular dimension.\nSense mode\nPress the down arrow key and select Sense mode to specify the mode of the angular dimension. Refer to Sense Mode for further information.\nDerived\nPress the down arrow key and select Derived to define the origin point of the angular dimension using the intersecting point of two P-lines. Refer Add Angular Dimensions with Derived Intersection to for further information.\nChained\nPress the down arrow key and select Chained to specify the angular dimension type as chained.\nBaseline\nPress the down arrow key and select Baseline to specify the angular dimension type as angular baseline.\nCombined\nPress the down arrow key and select Combined to specify the angular dimension type as combined.\nDirection\nPress the down arrow key and select Direction to add angular dimensions with a specified direction. Refer to Add Angular Dimensions with Specified Direction for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nFree\nPress the down arrow key and select Free to create the angular dimensions in either a clockwise or anti clockwise rotational direction style. The style is defined by the cursor movement direction used to create the dimension points. Refer to Sense Mode for further information.\nBy Style\nPress the down arrow key and select By style to create the angular dimensions using the rotational direction style used to create the previous angular dimension. Refer to Sense Mode for further information.\n\nType\nPress the down arrow key and select Type to specify the type of angular dimension.\nSense mode\nPress the down arrow key and select Sense mode to specify the mode of the angular dimension. Refer to Sense Mode for further information.\nDerived\nPress the down arrow key and select Derived to define the origin point of the angular dimension using the intersecting point of two P-lines. Refer Add Angular Dimensions with Derived Intersection to for further information.\nChained\nPress the down arrow key and select Chained to specify the angular dimension type as chained.\nBaseline\nPress the down arrow key and select Baseline to specify the angular dimension type as angular baseline.\nCombined\nPress the down arrow key and select Combined to specify the angular dimension type as combined.\nDirection\nPress the down arrow key and select Direction to add angular dimensions with a specified direction. Refer to Add Angular Dimensions with Specified Direction for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nFree\nPress the down arrow key and select Free to create the angular dimensions in either a clockwise or anti clockwise rotational direction style. The style is defined by the cursor movement direction used to create the dimension points. Refer to Sense Mode for further information.\nBy Style\nPress the down arrow key and select By style to create the angular dimensions using the rotational direction style used to create the previous angular dimension. Refer to Sense Mode for further information.\nThe new ADIM element displays in the Draw Explorer containing a DPOI element that represents each dimension point.\n\nThe different types of angular dimension are:\nAngular Chained\n\nAngular Baseline\n\nAngular Combined\n\nType\nPress the down arrow key and select Type to specify the type of angular dimension.\nSense mode\nPress the down arrow key and select Sense mode to specify the mode of the angular dimension. Refer to Sense Mode for further information.\nDerived\nPress the down arrow key and select Derived to define the origin point of the angular dimension using the intersecting point of two P-lines. Refer Add Angular Dimensions with Derived Intersection to for further information.\nChained\nPress the down arrow key and select Chained to specify the angular dimension type as chained.\nBaseline\nPress the down arrow key and select Baseline to specify the angular dimension type as angular baseline.\nCombined\nPress the down arrow key and select Combined to specify the angular dimension type as combined.\nDirection\nPress the down arrow key and select Direction to add angular dimensions with a specified direction. Refer to Add Angular Dimensions with Specified Direction for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nFree\nPress the down arrow key and select Free to create the angular dimensions in either a clockwise or anti clockwise rotational direction style. The style is defined by the cursor movement direction used to create the dimension points. Refer to Sense Mode for further information.\nBy Style\nPress the down arrow key and select By style to create the angular dimensions using the rotational direction style used to create the previous angular dimension. Refer to Sense Mode for further information.\n\n\n\nSense Mode\nAdd Angular Dimensions with Derived Intersection\nAdd Angular Dimensions with Specified Direction\nSense Mode\nSense Mode\nSpecify the dimension position point or <Type>\nEnter\nSpecify the dimension position point or <Direction>\nEnter\nSpecify the dimension point or <Direction>\nEnter\nSpecify the dimension line position or\nEnter\nSpecify the dimension point or <Finish>\nEnter\nF\nEnter\nESC\nType\nType\nSense mode\nSense mode\nSense Mode\nDerived\nDerived\nAdd Angular Dimensions with Derived Intersection\nChained\nChained\nBaseline\nBaseline\nCombined\nCombined\nDirection\nDirection\nAdd Angular Dimensions with Specified Direction\nBack\nBack\nFinish\nFinish\nFree\nFree\nSense Mode\nBy Style\nBy style\nSense Mode\nAngular Chained\nAngular Baseline\nAngular Combined"}
{"Headers": "Add Linear Dimensions Using Grip Points", "Content": "Adds additional Linear (LDIM) points for an existing dimension using grip points.\nTo create additional LDIM points for a dimension, click to identify an existing LDIM. The grip points display in blue.\n\nClick the additional grip point. The grip point displays in red.\nYou are prompted to Specify stretch point or\n\nClick to identify the position of the new dimension point. The dimension annotation is added.\nYou are then prompted to Specify stretch point or\nThe prompt is repeated allowing you to add multiple dimension annotations.\nPress ESC to end the command.\nThroughout the linear dimension creation process you can press ESC to cancel or finish the command (created dimension annotations remain when ESC is pressed but the operation ends). Additional functionality is also available.\nBefore\nPress the down arrow key and select Before to add a before dimensional point using a specified owner as the point to measure from.\nNote:\nPpoint snap must be enabled to use this functionality. Refer to Object Snaps for further information.\nYou are prompted to Specify stretch point or\nClick to identify the position of the new dimension point by snapping to a ppoint. The dimension annotation is added before the selected owner.\nThe new DBPA element displays in the Draw Explorer.\nAfter\nPress the down arrow key and select After to add an after dimensional point using a specified owner as the point to measure from.\nNote:\nPpoint snap must be enabled to use this functionality. Refer to Object Snaps for further information.\nYou are prompted to Specify stretch point or\nClick to identify the position of the new dimension point by snapping to a ppoint. The dimension annotation is added after the selected owner.\nThe new DBPA element displays in the Draw Explorer.\nPoint\nPress the down arrow key and select Point to add a standard LDIM point at a specified snap point.\nYou are prompted to Specify stretch point or\nClick to identify the position of the new dimension point. The dimension annotation is added.\n\nBefore\nPress the down arrow key and select Before to add a before dimensional point using a specified owner as the point to measure from.\nYou are prompted to Specify stretch point or\nClick to identify the position of the new dimension point by snapping to a ppoint. The dimension annotation is added before the selected owner.\n\n\nThe new DBPA element displays in the Draw Explorer.\n\nAfter\nPress the down arrow key and select After to add an after dimensional point using a specified owner as the point to measure from.\nYou are prompted to Specify stretch point or\nClick to identify the position of the new dimension point by snapping to a ppoint. The dimension annotation is added after the selected owner.\n\n\nThe new DBPA element displays in the Draw Explorer.\n\nPoint\nPress the down arrow key and select Point to add a standard LDIM point at a specified snap point.\nYou are prompted to Specify stretch point or\nClick to identify the position of the new dimension point. The dimension annotation is added.\nModify linear dimension points using the Vertex Editor window. Refer to Vertex Editor for further information.\n\nBefore\nPress the down arrow key and select Before to add a before dimensional point using a specified owner as the point to measure from.\nNote:\nPpoint snap must be enabled to use this functionality. Refer to Object Snaps for further information.\nYou are prompted to Specify stretch point or\nClick to identify the position of the new dimension point by snapping to a ppoint. The dimension annotation is added before the selected owner.\nThe new DBPA element displays in the Draw Explorer.\nAfter\nPress the down arrow key and select After to add an after dimensional point using a specified owner as the point to measure from.\nNote:\nPpoint snap must be enabled to use this functionality. Refer to Object Snaps for further information.\nYou are prompted to Specify stretch point or\nClick to identify the position of the new dimension point by snapping to a ppoint. The dimension annotation is added after the selected owner.\nThe new DBPA element displays in the Draw Explorer.\nPoint\nPress the down arrow key and select Point to add a standard LDIM point at a specified snap point.\nYou are prompted to Specify stretch point or\nClick to identify the position of the new dimension point. The dimension annotation is added.\nNote:\nPpoint snap must be enabled to use this functionality. Refer to Object Snaps for further information.\nNote:\nPpoint snap must be enabled to use this functionality. Refer to Object Snaps for further information.\n\n\n\nObject Snaps\nObject Snaps\nVertex Editor\nSpecify stretch point or\nSpecify stretch point or\nESC\nESC\nESC\nBefore\nBefore\nNote\n:\nObject Snaps\nSpecify stretch point or\nAfter\nAfter\nNote\n:\nObject Snaps\nSpecify stretch point or\nPoint\nPoint\nSpecify stretch point or\nVertex Editor\nVertex Editor"}
{"Headers": "Add Angular Dimensions Using Grip Points", "Content": "Adds additional Angular (ADIM) points for an existing dimension using grip points.\nTo create additional ADIM points for a dimension, click to identify an existing ADIM. The grip points display in blue.\n\nClick the additional grip point. The grip point displays in red.\nYou are prompted to Specify stretch point\n\nClick to identify the position of the new dimension point. The dimension annotation is added.\nYou are then prompted to Specify stretch point\nThe prompt is repeated allowing you to add multiple dimension annotations.\nPress ESC to end the command.\n\n\n\nSpecify stretch point\nSpecify stretch point\nESC"}
{"Headers": "Define Dimension Project Line Overshoot and Clearance Length using Grip Points", "Content": "Sets the Linear (LDIM) or Angular (ADIM) overshoot and clearance properties using grip points. The grip points display as a double-headed triangle.\nTo display the grip points, make sure that Additional grips on/off is highlighted on the status bar. Refer to Status Bar for further information.\nClick to identify the dimension line.\n\nYou are prompted to Specify stretch point\nInput a dimensional value in the field and press Enter or click to identify the overshoot or clearance length.\n\nThe overshoot property is updated.\nThe overshoot property can also be modified using the Projection line field on the Properties window. Refer to Properties for further information.\n\n\n\nStatus Bar\nProperties\nAdditional grips on/off\nStatus Bar\nSpecify stretch point\nEnter\nProjection line\nProperties\nProperties"}
{"Headers": "Rotate Dimension and Projection Line Text", "Content": "Rotates Dimension/Projection Line text for LDIM, ADIM, PDIM or RDIM dimensions.\n\n\n"}
{"Headers": "Extend Dimension Lines using Grip Points", "Content": "Extends dimension lines for ADIM and LDIM when a dimension annotation is moved using a grip point.\nThe extended dimension line properties of a ADIM or LDIM can be modified using the Properties window. Refer to Properties for further information.\n\nThe functionality is available for dimension lines that have the Dim line text angle property value defined as Extended, Parallel or Standard.\nExtended dimension line\nSelect Yes from the drop down list to extend the dimension line when a dimension annotation is moved using a grip point.\nInput No from the drop down list to define that dimension lines are not extended when a dimension annotation is moved using a grip point.\nExtended dimension line\nSelect Yes from the drop down list to extend the dimension line when a dimension annotation is moved using a grip point.\n\nInput No from the drop down list to define that dimension lines are not extended when a dimension annotation is moved using a grip point.\n\n\nExtended dimension line\nSelect Yes from the drop down list to extend the dimension line when a dimension annotation is moved using a grip point.\nInput No from the drop down list to define that dimension lines are not extended when a dimension annotation is moved using a grip point.\n\n\n\nProperties\nProperties\nProperties\nDim line text angle\nExtended\nParallel\nStandard\nExtended dimension line\nYes\nNo"}
{"Headers": "Define Dimension Line Gaps for Dimension Annotations", "Content": "Adds gaps to dimension lines to allow for dimension annotations.\nThe dim line continuous properties of a ADIM or LDIM can be modified using the Properties window. Refer to Properties for further information.\n\nDim line continuous\nSelect By Style from the drop-down list to inherit the dimension line continuous property from the visual style.\nSelect On from the drop down list to specify a continuous dimension line.\nSelect Off from the drop down list to create a gap on the dimension line to allow for a dimension annotation.\nThe property is ignored if the dimension annotation does not fit between the projection lines.\nDim line continuous\nSelect By Style from the drop-down list to inherit the dimension line continuous property from the visual style.\nSelect On from the drop down list to specify a continuous dimension line.\n\nSelect Off from the drop down list to create a gap on the dimension line to allow for a dimension annotation.\n\nThe property is ignored if the dimension annotation does not fit between the projection lines.\n\n\nDim line continuous\nSelect By Style from the drop-down list to inherit the dimension line continuous property from the visual style.\nSelect On from the drop down list to specify a continuous dimension line.\nSelect Off from the drop down list to create a gap on the dimension line to allow for a dimension annotation.\nThe property is ignored if the dimension annotation does not fit between the projection lines.\n\n\n\nProperties\ndim line continuous\nProperties\nProperties\nDim line continuous\nBy Style\nOn\nOff"}
{"Headers": "Add Leader Lines to Dimensions", "Content": "Adds leader lines to dimensions.\nThe Leader line properties of an LDIM, ADIM, PDIM or RDIM can be modified using the Properties window. Refer to Properties for further information.\n\nLeader line color\nSelect By Style from the drop-down list to inherit the leader line color from the visual style.\nSelect By Layer from the drop-down list to inherit the leader line color from the layer.\nSelect a color from the drop-down list to define the color of the leader line.\nLeader line type\nSelect By Style from the drop-down list to inherit the leader line type from the visual style.\nSelect By Layer to from the drop-down list to inherit the leader line type from the layer.\nSelect a line type from the drop-down list to define the label leader line type.\nLeader line visibility\nSelect By Style from the drop-down list to inherit the leader line visibility from the visual style.\nSelect On from the drop-down list to display the leader line.\nSelect Off from the drop-down list to remove the leader line from the display.\nLeader line shape settings\nSelect By Style from the drop-down list to inherit the leader line shape settings from the visual style.\nSelect from the drop-down list to define the shape of the leader line. For example:\nStraight\nAngled Vertical\nBent\nLeader line color\nSelect By Style from the drop-down list to inherit the leader line color from the visual style.\nSelect By Layer from the drop-down list to inherit the leader line color from the layer.\nSelect a color from the drop-down list to define the color of the leader line.\nLeader line type\nSelect By Style from the drop-down list to inherit the leader line type from the visual style.\nSelect By Layer to from the drop-down list to inherit the leader line type from the layer.\nSelect a line type from the drop-down list to define the label leader line type.\nLeader line visibility\nSelect By Style from the drop-down list to inherit the leader line visibility from the visual style.\nSelect On from the drop-down list to display the leader line.\nSelect Off from the drop-down list to remove the leader line from the display.\nLeader line shape settings\nSelect By Style from the drop-down list to inherit the leader line shape settings from the visual style.\nSelect from the drop-down list to define the shape of the leader line. For example:\nStraight\n\nAngled Vertical\n\nBent\n\nWhen exported to DGN, DWG or DXF, leader lines are exported as separate lines and not as part of the dimensions.\nTo add a leader line to an individual dimension text element, modify the Leader line properties using the Vertex Editor window.\n\nLeader line color\nSelect By Style from the drop-down list to inherit the leader line color from the visual style.\nSelect By Layer from the drop-down list to inherit the leader line color from the layer.\nSelect a color from the drop-down list to define the color of the leader line.\nLeader line type\nSelect By Style from the drop-down list to inherit the leader line type from the visual style.\nSelect By Layer to from the drop-down list to inherit the leader line type from the layer.\nSelect a line type from the drop-down list to define the label leader line type.\nLeader line visibility\nSelect By Style from the drop-down list to inherit the leader line visibility from the visual style.\nSelect On from the drop-down list to display the leader line.\nSelect Off from the drop-down list to remove the leader line from the display.\nLeader line shape settings\nSelect By Style from the drop-down list to inherit the leader line shape settings from the visual style.\nSelect from the drop-down list to define the shape of the leader line. For example:\nStraight\nAngled Vertical\nBent\n\n\n\nProperties\nLeader line\nProperties\nProperties\nLeader line color\nBy Style\nBy Layer\nLeader line type\nBy Style\nBy Layer\nLeader line visibility\nBy Style\nOn from\nOff from\nLeader line shape settings\nBy Style\nStraight\nAngled Vertical\nLeader line\nVertex Editor"}
{"Headers": "Add Text Frame to Dimensions", "Content": "Adds a visible text frame to dimensions. The functionality is available for all dimension types.\nThe Frame properties of dimensions can be modified using the Properties window. Refer to Properties for further information.\n\nDim Text Frame Sides Visibility\nSelect By Style from the drop-down list to inherit the visible text frame from the visual style.\nSelect the visible sides from the drop-down list to define the display of the visible text frame.\nFor example, select Bottom Left to display a visible text frame below and left of the dimension text.\nDim Text Frame Colour\nSelect By Style from the drop-down list to inherit the text frame colour from the visual style.\nSelect the colour from the drop-down list to define the colour of the visible text frame.\nFor example, select Colour 7 Blue to display a blue text frame.\nDim Text Frame Line Style\nSelect By Style from the drop-down list to inherit the text frame line style from the visual style.\nSelect the line style from the drop-down list to define the line style of the visible text frame.\nFor example, select 8002 Dashed [Thin] to display a dashed text frame.\nGbox\nSelect By Style from the drop-down list to inherit the text frame size from the from the visual style.\nInput a dimensional value or select from the drop-down list to define the size of the visible text frame. The text frame distance is measured from the edge of the text.\nFor example, select 3mm to insert a 3mm gap between the edge of the text and the text frame.\nDim Text Frame Sides Visibility\nSelect By Style from the drop-down list to inherit the visible text frame from the visual style.\nSelect the visible sides from the drop-down list to define the display of the visible text frame.\nFor example, select Bottom Left to display a visible text frame below and left of the dimension text.\n\nDim Text Frame Colour\nSelect By Style from the drop-down list to inherit the text frame colour from the visual style.\nSelect the colour from the drop-down list to define the colour of the visible text frame.\nFor example, select Colour 7 Blue to display a blue text frame.\n\nDim Text Frame Line Style\nSelect By Style from the drop-down list to inherit the text frame line style from the visual style.\nSelect the line style from the drop-down list to define the line style of the visible text frame.\nFor example, select 8002 Dashed [Thin] to display a dashed text frame.\n\nGbox\nSelect By Style from the drop-down list to inherit the text frame size from the from the visual style.\nInput a dimensional value or select from the drop-down list to define the size of the visible text frame. The text frame distance is measured from the edge of the text.\nFor example, select 3mm to insert a 3mm gap between the edge of the text and the text frame.\n\nTo add a visible text frame to an individual dimension text element, modify the Frame properties using the Vertex Editor window.\n\nDim Text Frame Sides Visibility\nSelect By Style from the drop-down list to inherit the visible text frame from the visual style.\nSelect the visible sides from the drop-down list to define the display of the visible text frame.\nFor example, select Bottom Left to display a visible text frame below and left of the dimension text.\nDim Text Frame Colour\nSelect By Style from the drop-down list to inherit the text frame colour from the visual style.\nSelect the colour from the drop-down list to define the colour of the visible text frame.\nFor example, select Colour 7 Blue to display a blue text frame.\nDim Text Frame Line Style\nSelect By Style from the drop-down list to inherit the text frame line style from the visual style.\nSelect the line style from the drop-down list to define the line style of the visible text frame.\nFor example, select 8002 Dashed [Thin] to display a dashed text frame.\nGbox\nSelect By Style from the drop-down list to inherit the text frame size from the from the visual style.\nInput a dimensional value or select from the drop-down list to define the size of the visible text frame. The text frame distance is measured from the edge of the text.\nFor example, select 3mm to insert a 3mm gap between the edge of the text and the text frame.\n\n\n\nProperties\nFrame\nProperties\nProperties\nDim Text Frame Sides Visibility\nBy Style\nBottom Left\nDim Text Frame Colour\nBy Style\nColour 7 Blue\nDim Text Frame Line Style\nBy Style\n8002 Dashed [Thin]\nGbox\nBy Style\n3mm\nFrame\nVertex Editor"}
{"Headers": "Add Radial Dimensions", "Content": "Adds radial dimensions to a view.\nYou are prompted to Select design object\nClick to identify a circular design object to add the radial dimension to.\nThe new RDIM element displays in the Draw Explorer.\n\nThe different types of radial dimension are:\nAcross Diameter\n\nAcross Diameter Leaderline\n\nDiameter Leaderline\n\nDiameter Pointer Leaderline\n\nDiameter Internal Leaderline\n\nInternal Radius\n\nInternal Radius Leaderline\n\nExternal Radius Leaderline\n\nExternal Point Leaderline\n\nRadius Internal Leaderline\n\n\n\n\nSelect design object\nAcross Diameter\nAcross Diameter Leaderline\nDiameter Leaderline\nDiameter Pointer Leaderline\nDiameter Internal Leaderline\nInternal Radius\nInternal Radius Leaderline\nExternal Radius Leaderline\nExternal Point Leaderline\nRadius Internal Leaderline"}
{"Headers": "Add Pitch Circle Dimensions", "Content": "Adds pitch circle dimensions to a view.\nYou are prompted to Specify the first point or <Mode>\nInput values in the dimension fields and press Enter or click to identify a point to measure from.\nYou are then prompted to Specify the second point or <Mode>\nInput values in the dimension fields and press Enter or click to identify the point to measure to. The pitch circle dimension is added.\nThroughout the pitch circle dimension creation process you can press ESC to cancel the command. Additional functionality is also available.\nMode\nPress the down arrow key and select Mode to specify the pitch circle dimension mode.\nYou are prompted to Specify dim mode <Diameter>\nInput B at the prompt and press Enter to specify the dimension mode as by style.\nInput D at the prompt and press Enter to specify the dimension mode as by diameter.\nInput R at the prompt and press Enter to specify the dimension mode as by radius.\nStyle\nPress the down arrow key and select Style to specify the pitch circle dimension style.\nYou are prompted to Specify dim style <dim line>\nInput B at the prompt and press Enter to specify the dimension style as by style.\nInput D at the prompt and press Enter to specify the dimension style as dim line.\nInput E at the prompt and press Enter to specify the dimension style as external.\nInput L at the prompt and press Enter to specify the dimension style as leader line.\nAngle mode\nPress the down arrow key and select Angle mode to specify the pitch circle dimension angle mode.\nYou are prompted to Specify angle mode <Free>\nInput B at the prompt and press Enter to specify the angle mode as by style.\nInput F at the prompt and press Enter to specify the angle mode as by free.\nYou can then select Free or By style.\nDesign item\nPress the down arrow key and select Design item to specify a design item to annotate.\nYou are prompted to Select design object.\nClick to identify the design object and press Enter.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nMode\nPress the down arrow key and select Mode to specify the pitch circle dimension mode.\nYou are prompted to Specify dim mode <Diameter>\nInput B at the prompt and press Enter to specify the dimension mode as by style.\nInput D at the prompt and press Enter to specify the dimension mode as by diameter.\nInput R at the prompt and press Enter to specify the dimension mode as by radius.\nStyle\nPress the down arrow key and select Style to specify the pitch circle dimension style.\nYou are prompted to Specify dim style <dim line>\nInput B at the prompt and press Enter to specify the dimension style as by style.\nInput D at the prompt and press Enter to specify the dimension style as dim line.\nInput E at the prompt and press Enter to specify the dimension style as external.\nInput L at the prompt and press Enter to specify the dimension style as leader line.\nAngle mode\nPress the down arrow key and select Angle mode to specify the pitch circle dimension angle mode.\nYou are prompted to Specify angle mode <Free>\nInput B at the prompt and press Enter to specify the angle mode as by style.\nInput F at the prompt and press Enter to specify the angle mode as by free.\nYou can then select Free or By style.\nDesign item\nPress the down arrow key and select Design item to specify a design item to annotate.\nYou are prompted to Select design object.\nClick to identify the design object and press Enter.\nBack\nPress the down arrow key and select Back to undo the last action.\nThe new PDIM element displays in the Draw Explorer containing an RPOI element that represents each dimension point.\n\nThe different types of pitch circle diameter (PCD) and pitch circle radius (PCR) dimension are:\nAcross PCD\n\nAcross PCD Leaderline\n\nPCD Leaderline\n\nPCD Pointer Leaderline\n\nPCD Internal Leaderline\n\nInternal PCR\n\nInternal PCR Leaderline\n\nExternal PCR Leaderline\n\nExternal PCR Pointer Leaderline\n\nPCR Internal Leaderline\n\nMode\nPress the down arrow key and select Mode to specify the pitch circle dimension mode.\nYou are prompted to Specify dim mode <Diameter>\nInput B at the prompt and press Enter to specify the dimension mode as by style.\nInput D at the prompt and press Enter to specify the dimension mode as by diameter.\nInput R at the prompt and press Enter to specify the dimension mode as by radius.\nStyle\nPress the down arrow key and select Style to specify the pitch circle dimension style.\nYou are prompted to Specify dim style <dim line>\nInput B at the prompt and press Enter to specify the dimension style as by style.\nInput D at the prompt and press Enter to specify the dimension style as dim line.\nInput E at the prompt and press Enter to specify the dimension style as external.\nInput L at the prompt and press Enter to specify the dimension style as leader line.\nAngle mode\nPress the down arrow key and select Angle mode to specify the pitch circle dimension angle mode.\nYou are prompted to Specify angle mode <Free>\nInput B at the prompt and press Enter to specify the angle mode as by style.\nInput F at the prompt and press Enter to specify the angle mode as by free.\nYou can then select Free or By style.\nDesign item\nPress the down arrow key and select Design item to specify a design item to annotate.\nYou are prompted to Select design object.\nClick to identify the design object and press Enter.\nBack\nPress the down arrow key and select Back to undo the last action.\n\n\n\nSpecify the first point or <Mode>\nEnter\nSpecify the second point or <Mode>\nEnter\nESC\nMode\nMode\nSpecify dim mode <Diameter>\nB\nEnter\nD\nEnter\nR\nEnter\nStyle\nStyle\nSpecify dim style <dim line>\nB\nEnter\nD\nEnter\nE\nEnter\nL\nEnter\nAngle mode\nAngle mode\nSpecify angle mode <Free>\nB\nEnter\nF\nEnter\nFree\nBy style\nDesign item\nDesign item\nSelect design object\nEnter\nBack\nBack\nAcross PCD\nAcross PCD Leaderline\nPCD Leaderline\nPCD Pointer Leaderline\nPCD Internal Leaderline\nInternal PCR\nInternal PCR Leaderline\nExternal PCR Leaderline\nExternal PCR Pointer Leaderline\nPCR Internal Leaderline"}
{"Headers": "Autolabels", "Content": "Generates annotations for design elements on a view using the Properties window. Refer to Properties for further information.\n\nAutolabels enabled\nSelect Yes from the drop-down list to update the autolabels when the design elements are updated.\nSelect No from the drop-down list to suppress the update of autolabels when the design elements are updated.\nRefer to Update for further information.\nAutolabels rule\nInput a value or select a valid path to define the default Design Annotations Rule Set (DARST) element that contains the autolabels rules.\nAutolabels enabled\nSelect Yes from the drop-down list to update the autolabels when the design elements are updated.\nSelect No from the drop-down list to suppress the update of autolabels when the design elements are updated.\nRefer to Update for further information.\nAutolabels rule\nInput a value or select a valid path to define the default Design Annotations Rule Set (DARST) element that contains the autolabels rules.\nWhen the design elements are updated, the autolabels display on the view.\n\nThe new SLAB elements display in the Draw Explorer.\n\nAutolabels enabled\nSelect Yes from the drop-down list to update the autolabels when the design elements are updated.\nSelect No from the drop-down list to suppress the update of autolabels when the design elements are updated.\nRefer to Update for further information.\nAutolabels rule\nInput a value or select a valid path to define the default Design Annotations Rule Set (DARST) element that contains the autolabels rules.\n\n\n\nProperties\nUpdate\nProperties\nProperties\nAutolabels enabled\nYes\nNo\nUpdate\nAutolabels rule"}
{"Headers": "Label Objects", "Content": "Adds a General Label (GLAB) or Symbolic Label (SLAB) to a view.\nThere are two types of Label, General Labels (GLAB) and Symbolic Labels (SLAB). Their characteristics are as follows:\n\nThe Select window allows you to select the required label template (GLAB) from the GLAB template folder.\nSelect the required template and click Select.\nYou are prompted to Specify attachment point or <Template>\nInput values in the dimension fields and press Enter or click to identify the label leader line attachment point.\nYou are then prompted to Select design element\nClick to identify the design element to be labelled.\nYou are then prompted to Specify connection point or <Template>\nInput values in the dimension fields and press Enter or click to identify the position of the label text.\nIf the label is a symbolic label (SLAB) it is added to the drawing. If the label is a general label (GLAB), the Text Editor window displays. Refer to Add Text to Drawings for further information.\nWhen you have input and formatted the text using the Text Editor window and clicked OK, the label is added to the drawing.\nYou are then prompted to Specify attachment point or <Finish>\nThe process can be repeated, allowing you to add multiple labels.\nInput F at the prompt and press Enter to end the command.\nThroughout the label creation process you can press ESC to cancel the command. Additional functionality is also available.\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to add a copy of a label. Refer to Add Copy of Label for further information.\nGeneral\nPress the down arrow key and select General to add a label that consists of text derived from the 3D model or free text.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to add a copy of a label. Refer to Add Copy of Label for further information.\nGeneral\nPress the down arrow key and select General to add a label that consists of text derived from the 3D model or free text.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new GLAB OR SLAB element displays in the Draw Explorer.\n\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to add a copy of a label. Refer to Add Copy of Label for further information.\nGeneral\nPress the down arrow key and select General to add a label that consists of text derived from the 3D model or free text.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nGeneral Labels consist of text derived from the 3D model or free text.\nSymbolic Labels are generated from templates (which can contain 2D primitives, including text), defined by a reference to a Symbol Template (SYTM).\nGeneral Labels consist of text derived from the 3D model or free text.\nGeneral Labels consist of text derived from the 3D model or free text.\nSymbolic Labels are generated from templates (which can contain 2D primitives, including text), defined by a reference to a Symbol Template (SYTM).\nSymbolic Labels are generated from templates (which can contain 2D primitives, including text), defined by a reference to a Symbol Template (SYTM).\n\n\n\nAdd Text to Drawings\nAdd Copy of Label\nSelect\nSelect\nSpecify attachment point or <Template>\nEnter\nSelect design element\nSpecify connection point or <Template>\nEnter\nText Editor\nAdd Text to Drawings\nText Editor\nOK\nSpecify attachment point or <Finish>\nF\nEnter\nESC\nTemplate\nTemplate\nSame As\nSame As\nAdd Copy of Label\nGeneral\nGeneral\nBack\nBack\nFinish\nFinish"}
{"Headers": "Add Copy of Label", "Content": "Adds a copy of a label to a view.\n\nThe Select window allows you to select the required label template (GLAB) from the GLAB template folder.\nSelect the required template and click Select.\nYou are prompted to Specify attachment point or <Template>\nInput S at the prompt and press Enter.\nYou are then prompted to Select label element\nClick to identify the label to copy.\nYou are then prompted to Specify attachment point or <Template>\nClick the label leader line attachment point.\nYou are then prompted to Select design element\nClick to identify the design element to be labelled. A copy of the label is added to the drawing\nThe process can be repeated, allowing you to add multiple labels.\nPress ESC to end the command.\nThroughout the label copy process you can press ESC to cancel the command. Additional functionality is also available.\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to add a copy of a label.\nGeneral\nPress the down arrow key and select General to add a label that consists of text derived from the 3D model or free text.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to add a copy of a label.\nGeneral\nPress the down arrow key and select General to add a label that consists of text derived from the 3D model or free text.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to add a copy of a label.\nGeneral\nPress the down arrow key and select General to add a label that consists of text derived from the 3D model or free text.\nBack\nPress the down arrow key and select Back to undo the last action.\n\n\n\nSelect\nSelect\nSpecify attachment point or <Template>\nS\nEnter\nSelect label element\nSpecify attachment point or <Template>\nSelect design element\nESC\nESC\nTemplate\nTemplate\nSame As\nSame As\nGeneral\nGeneral\nBack\nBack"}
{"Headers": "Create Advanced Label", "Content": "Adds an advanced label to the view.\n\n\n"}
{"Headers": "Weight and Center of Gravity Label", "Content": "Adds a weight and center of gravity label to a view.\nYou are prompted to Select design element\nClick to identify the design element to be labelled. For example an IPLATE element.\nYou are then prompted to Use element <element name> or\nPress Enter to use the selected design element as the element to be labelled.\nIf the centre of gravity of the selected design element is inside the view frame, the label leader line attachment point is automatically defined.\nIf the centre of gravity of the selected design element is outside the view frame, you are prompted to Specify attachment point\nInput values in the dimension fields and press Enter or click to identify the label leader line attachment point.\nYou are then prompted to Specify connection point or\nInput values in the dimension fields and press Enter or click to identify the position of the label text.\nThe process can be repeated, allowing you to add multiple labels.\nPress ESC to end the command.\nThroughout the label creation process you can press ESC to cancel the command. Additional functionality is also available.\n1 UPANEL\nPress the down arrow key and select 1 UPANEL to add a label with a center of gravity derived from the owning UPANEL element.\n2 ZONE\nPress the down arrow key and select 2 ZONE to add a label with a centre of gravity derived from the owning ZONE element.\n3 ASMBLY\nPress the down arrow key and select 3 ASMBLY to add a label with a center of gravity derived from the owning ASSEMBLY element.\nNote:\nThe functionality is only available if the selected design element is a defined as part of an assembly.\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to select a different label template derived from an existing label on the drawing canvas.\nYou are prompted to Select label element\nClick to identify the label, the template of the selected label is used for the created label.\n\n1 UPANEL\nPress the down arrow key and select 1 UPANEL to add a label with a center of gravity derived from the owning UPANEL element.\n2 ZONE\nPress the down arrow key and select 2 ZONE to add a label with a centre of gravity derived from the owning ZONE element.\n3 ASMBLY\nPress the down arrow key and select 3 ASMBLY to add a label with a center of gravity derived from the owning ASSEMBLY element.\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to select a different label template derived from an existing label on the drawing canvas.\nYou are prompted to Select label element\nClick to identify the label, the template of the selected label is used for the created label.\n\nThe new SLAB element displays in the Draw Explorer.\n\n1 UPANEL\nPress the down arrow key and select 1 UPANEL to add a label with a center of gravity derived from the owning UPANEL element.\n2 ZONE\nPress the down arrow key and select 2 ZONE to add a label with a centre of gravity derived from the owning ZONE element.\n3 ASMBLY\nPress the down arrow key and select 3 ASMBLY to add a label with a center of gravity derived from the owning ASSEMBLY element.\nNote:\nThe functionality is only available if the selected design element is a defined as part of an assembly.\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to select a different label template derived from an existing label on the drawing canvas.\nYou are prompted to Select label element\nClick to identify the label, the template of the selected label is used for the created label.\nNote:\nWeight and centre of gravity labels are generated from a special Symbol Template (SYTM). To setup the default template for this label type:\nNote:\nThe functionality is only available if the selected design element is a defined as part of an assembly.\n\n\n\nSet System Defaults\nNote\n:\nSet System Defaults\nSelect design element\nUse element <element name> or\nEnter\nSpecify attachment point\nEnter\nSpecify connection point or\nEnter\nESC\nESC\n1 UPANEL\n1\nUPANEL\n2 ZONE\n2\nZONE\n3 ASMBLY\n3 ASMBLY\nNote\n:\nTemplate\nTemplate\nSame As\nSame As\nSelect label element"}
{"Headers": "3D Coordinate Label", "Content": "Adds a label containing positional information to a view.\nYou are prompted to Specify attachment point\nClick to identify the Ppoint provided by the design element to be labelled.\n\nYou are then prompted to Specify connection point or\nInput values in the dimension fields and press Enter or click to identify the position of the label text.\nThe process can be repeated, allowing you to add multiple labels.\nPress ESC to end the command.\nThroughout the label creation process you can press ESC to cancel the command. Additional functionality is also available.\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to select a different label template derived from an existing label on the drawing canvas.\nYou are prompted to Select label element\nClick to identify the label, the template of the selected label is used for the created label.\n\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to select a different label template derived from an existing label on the drawing canvas.\nYou are prompted to Select label element\nClick to identify the label, the template of the selected label is used for the created label.\n\nThe new SLAB element displays in the Draw Explorer.\n\nTemplate\nPress the down arrow key and select Template to select a different label template.\nSame As\nPress the down arrow key and select Same As to select a different label template derived from an existing label on the drawing canvas.\nYou are prompted to Select label element\nClick to identify the label, the template of the selected label is used for the created label.\nNote:\n3D Coordinate labels are generated from a special Symbol Template (SYTM). To setup the default template for this label type:\n\n\n\nSet System Defaults\nNote\n:\nSet System Defaults\nSpecify attachment point\nSpecify connection point or\nEnter\nESC\nESC\nTemplate\nTemplate\nSame As\nSame As\nSelect label element"}
{"Headers": "Label Format Tab", "Content": "The attributes of a label are modified using the Label Tools Format tab, which displays when a label is selected.\nLabels reflect the visual layers from the label template as long as the corresponding label properties are set to By Template (or By Style with the style properties set to By Template). Setting the label properties to By Layer overrides the label template and forces the use of the appropriate local sheet layer.\n\n\nVisual Style Group\nLabel Style\nAllows you to select a visual style for the label. Refer to Active Visual Styles for further information.\nText Group\nText Colour\nSelect from the drop-down list to define the colour of the label text.\nLabel Text Justification\nSelect By Template from the drop-down list to justify the label text using the default template setting.\nSelect Left from the drop-down list to left justify the label text.\nSelect Right from the drop-down list to right justify the label text.\nSelect Centre from the drop-down list to centre justify the label text.\nLabel Text Alignment\nSelect By Template from the drop-down list to align the label text using the default template setting.\nSelect Base from the drop-down list to align the label text with the base of the first character (on the first line of text).\nSelect BBody from the drop-down list to align the table text with the bottom of the body.\nSelect HBody from the drop-down list to align the label text halfway up the body.\nSelect TBody from the drop-down list to align he label text with the top of the body.\nLine text spacing\nSelect from the drop-down list to define the spacing factor for the label text.\nLine character spacing\nSelect from the drop-down list to define the character spacing for the label text.\nLabel text font\nSelect from the drop-down list to define the font for the label text.\nText height\nSelect from the drop-down list to define the height for the label text.\nLeader Group\nVisibility\nIf the label leader line is not currently displayed, click to display the label leader line.\nIf the label leader line is currently displayed, click to hide the label leader line.\nLeader Shape\nSelect from the drop-down list to define the shape of the label leader line. For example, straight, bent or angled horizontal.\nLabel Leader Line Colour\nSelect from the drop-down list to define the colour of the label leader line.\nLeader Line Type\nSelect from the drop-down list to define the label leader line type.\nLeader Line Terminator\nSelect from the drop-down list to define the type of terminator symbol used at the attachment point of the label leader line.\nLabel Leader Line Clearance Value\nSelect from the drop-down list to define the gap size between the attachment point and the start of the label leader line.\nLabel Leader Line Angle Value\nAllows you to define the label leader line angle if an angled leader line has been selected from the Leader Shape drop-down menu.\nInput a value in the Label Leader Line Angle Value field to define the angle for the label leader line.\nLabel Leader Line Terminator Size\nAllows you to define the size of the terminator symbol if a Leader Line Terminator has been selected.\nSelect from the drop-down list to define the size of the label leader line terminator symbol.\nFrame Group\nGeneric Label Frame Visibility\nIf the label frame is not currently displayed, click to display the label frame.\nIf the label frame is currently displayed, click to hide the label frame.\nLabel Leader Line Frame Colour\nSelect from the drop-down list to define the colour of the label frame.\nFrame Line Type\nSelect from the drop-down list to define the line type of the label frame.\nLabel Frame Rotation Angle\nInput a value in the Label Frame Rotation Angle field to define the rotation angle of the label frame.\nNote:\nThe text is rotated at the same angle.\nGeneric Label Box Gap\nSelect from the drop-down list to define the gap value between the text and label frame.\nLabel Frame Blanking Margin\nInput a value in the field to define the blanking margin for the frame label.\nFrame Sides Visibility\nSelect from the drop-down list to specify the visible frame sides for the label.\nScale X factor\nAllows you to define the scale along the X axis for symbols used in labels. For example, SLABs.\nInput the scale factor in the field to define the scale for the symbol.\nScale Y factor\nAllows you to define the scale along the Y axis for symbols used in labels. For example SLABs.\nInput the scale factor in the field to define the scale for the symbol.\nLabel Frame Blanking Visibility\nUsed to specify whether blanking is visible or not for the label.\nGaps Group\nCreate Gap\nAllows you to add gaps in leader lines. Refer to Leader Line Gaps for further information.\nRemove Gap\nAllows you to remove gaps from leader lines. You are prompted to Select design element.\nVisual Style Group\n\nLabel Style\nAllows you to select a visual style for the label. Refer to Active Visual Styles for further information.\nText Group\n\nText Colour\nSelect from the drop-down list to define the colour of the label text.\n\nLabel Text Justification\nSelect By Template from the drop-down list to justify the label text using the default template setting.\nSelect Left from the drop-down list to left justify the label text.\nSelect Right from the drop-down list to right justify the label text.\nSelect Centre from the drop-down list to centre justify the label text.\n\nLabel Text Alignment\nSelect By Template from the drop-down list to align the label text using the default template setting.\nSelect Base from the drop-down list to align the label text with the base of the first character (on the first line of text).\nSelect BBody from the drop-down list to align the table text with the bottom of the body.\nSelect HBody from the drop-down list to align the label text halfway up the body.\nSelect TBody from the drop-down list to align he label text with the top of the body.\n\nLine text spacing\nSelect from the drop-down list to define the spacing factor for the label text.\n\nLine character spacing\nSelect from the drop-down list to define the character spacing for the label text.\n\nLabel text font\nSelect from the drop-down list to define the font for the label text.\n\nText height\nSelect from the drop-down list to define the height for the label text.\nLeader Group\n\nVisibility\nIf the label leader line is not currently displayed, click to display the label leader line.\nIf the label leader line is currently displayed, click to hide the label leader line.\n\nLeader Shape\nSelect from the drop-down list to define the shape of the label leader line. For example, straight, bent or angled horizontal.\n\nLabel Leader Line Colour\nSelect from the drop-down list to define the colour of the label leader line.\n\nLeader Line Type\nSelect from the drop-down list to define the label leader line type.\n\nLeader Line Terminator\nSelect from the drop-down list to define the type of terminator symbol used at the attachment point of the label leader line.\n\nLabel Leader Line Clearance Value\nSelect from the drop-down list to define the gap size between the attachment point and the start of the label leader line.\n\nLabel Leader Line Angle Value\nAllows you to define the label leader line angle if an angled leader line has been selected from the Leader Shape drop-down menu.\nInput a value in the Label Leader Line Angle Value field to define the angle for the label leader line.\n\nLabel Leader Line Terminator Size\nAllows you to define the size of the terminator symbol if a Leader Line Terminator has been selected.\nSelect from the drop-down list to define the size of the label leader line terminator symbol.\nFrame Group\n\nGeneric Label Frame Visibility\nIf the label frame is not currently displayed, click to display the label frame.\nIf the label frame is currently displayed, click to hide the label frame.\n\nLabel Leader Line Frame Colour\nSelect from the drop-down list to define the colour of the label frame.\n\nFrame Line Type\nSelect from the drop-down list to define the line type of the label frame.\n\nLabel Frame Rotation Angle\nInput a value in the Label Frame Rotation Angle field to define the rotation angle of the label frame.\n\nGeneric Label Box Gap\nSelect from the drop-down list to define the gap value between the text and label frame.\n\nLabel Frame Blanking Margin\nInput a value in the field to define the blanking margin for the frame label.\n\nFrame Sides Visibility\nSelect from the drop-down list to specify the visible frame sides for the label.\n\nScale X factor\nAllows you to define the scale along the X axis for symbols used in labels. For example, SLABs.\nInput the scale factor in the field to define the scale for the symbol.\n\nScale Y factor\nAllows you to define the scale along the Y axis for symbols used in labels. For example SLABs.\nInput the scale factor in the field to define the scale for the symbol.\n\nLabel Frame Blanking Visibility\nUsed to specify whether blanking is visible or not for the label.\nGaps Group\n\nCreate Gap\nAllows you to add gaps in leader lines. Refer to Leader Line Gaps for further information.\n\nRemove Gap\nAllows you to remove gaps from leader lines. You are prompted to Select design element.\n\nVisual Style Group\nLabel Style\nAllows you to select a visual style for the label. Refer to Active Visual Styles for further information.\nText Group\nText Colour\nSelect from the drop-down list to define the colour of the label text.\nLabel Text Justification\nSelect By Template from the drop-down list to justify the label text using the default template setting.\nSelect Left from the drop-down list to left justify the label text.\nSelect Right from the drop-down list to right justify the label text.\nSelect Centre from the drop-down list to centre justify the label text.\nLabel Text Alignment\nSelect By Template from the drop-down list to align the label text using the default template setting.\nSelect Base from the drop-down list to align the label text with the base of the first character (on the first line of text).\nSelect BBody from the drop-down list to align the table text with the bottom of the body.\nSelect HBody from the drop-down list to align the label text halfway up the body.\nSelect TBody from the drop-down list to align he label text with the top of the body.\nLine text spacing\nSelect from the drop-down list to define the spacing factor for the label text.\nLine character spacing\nSelect from the drop-down list to define the character spacing for the label text.\nLabel text font\nSelect from the drop-down list to define the font for the label text.\nText height\nSelect from the drop-down list to define the height for the label text.\nLeader Group\nVisibility\nIf the label leader line is not currently displayed, click to display the label leader line.\nIf the label leader line is currently displayed, click to hide the label leader line.\nLeader Shape\nSelect from the drop-down list to define the shape of the label leader line. For example, straight, bent or angled horizontal.\nLabel Leader Line Colour\nSelect from the drop-down list to define the colour of the label leader line.\nLeader Line Type\nSelect from the drop-down list to define the label leader line type.\nLeader Line Terminator\nSelect from the drop-down list to define the type of terminator symbol used at the attachment point of the label leader line.\nLabel Leader Line Clearance Value\nSelect from the drop-down list to define the gap size between the attachment point and the start of the label leader line.\nLabel Leader Line Angle Value\nAllows you to define the label leader line angle if an angled leader line has been selected from the Leader Shape drop-down menu.\nInput a value in the Label Leader Line Angle Value field to define the angle for the label leader line.\nLabel Leader Line Terminator Size\nAllows you to define the size of the terminator symbol if a Leader Line Terminator has been selected.\nSelect from the drop-down list to define the size of the label leader line terminator symbol.\nFrame Group\nGeneric Label Frame Visibility\nIf the label frame is not currently displayed, click to display the label frame.\nIf the label frame is currently displayed, click to hide the label frame.\nLabel Leader Line Frame Colour\nSelect from the drop-down list to define the colour of the label frame.\nFrame Line Type\nSelect from the drop-down list to define the line type of the label frame.\nLabel Frame Rotation Angle\nInput a value in the Label Frame Rotation Angle field to define the rotation angle of the label frame.\nNote:\nThe text is rotated at the same angle.\nGeneric Label Box Gap\nSelect from the drop-down list to define the gap value between the text and label frame.\nLabel Frame Blanking Margin\nInput a value in the field to define the blanking margin for the frame label.\nFrame Sides Visibility\nSelect from the drop-down list to specify the visible frame sides for the label.\nScale X factor\nAllows you to define the scale along the X axis for symbols used in labels. For example, SLABs.\nInput the scale factor in the field to define the scale for the symbol.\nScale Y factor\nAllows you to define the scale along the Y axis for symbols used in labels. For example SLABs.\nInput the scale factor in the field to define the scale for the symbol.\nLabel Frame Blanking Visibility\nUsed to specify whether blanking is visible or not for the label.\nGaps Group\nCreate Gap\nAllows you to add gaps in leader lines. Refer to Leader Line Gaps for further information.\nRemove Gap\nAllows you to remove gaps from leader lines. You are prompted to Select design element.\nNote:\nThe text is rotated at the same angle.\n\n\n\nActive Visual Styles\nLeader Line Gaps\nLabel Tools Format\nBy Template\nBy Style\nBy Template\nBy Layer\nVisual Style Group\nLabel Style\nActive Visual Styles\nText Group\nText Colour\nLabel Text Justification\nBy Template\nLeft\nRight\nCentre\nLabel Text Alignment\nBy Template\nBase\nBBody\nHBody\nTBody\nLine text spacing\nLine character spacing\nLabel text font\nText height\nLeader Group\nVisibility\nLeader Shape\nLabel Leader Line Colour\nLeader Line Type\nLeader Line Terminator\nLabel Leader Line Clearance Value\nLabel Leader Line Angle Value\nLabel Leader Line Angle Value\nLabel Leader Line Terminator Size\nLeader Line Terminator\nFrame Group\nGeneric Label Frame Visibility\nLabel Leader Line Frame Colour\nFrame Line Type\nLabel Frame Rotation Angle\nLabel Frame Rotation Angle\nNote\n:\nGeneric Label Box Gap\nLabel Frame Blanking Margin\nFrame Sides Visibility\nScale X factor\nScale Y factor\nLabel Frame Blanking Visibility\nGaps Group\nCreate Gap\nLeader Line Gaps\nRemove Gap\nSelect design element"}
{"Headers": "Label and Dimension Blanking", "Content": "Sets the blanking options for labels and dimensions.\nTo set the blanking margin for every label and dimension on a sheet, input a value in the Blanking Margin field.\nTo turn blanking on or off for every label and dimension on a sheet, click Enable Blanking or Disable Blanking.\nTo turn blanking on or off and set a blanking margin for an individual label, refer to Label Format Tab for further information.\nTo turn blanking on or off and set a blanking margin for an individual dimension, use the settings in the Misc group of the Properties window. Refer to Properties for further information.\nTo set the blanking margin for every label and dimension on a sheet, input a value in the Blanking Margin field.\nTo set the blanking margin for every label and dimension on a sheet, input a value in the Blanking Margin field.\nTo turn blanking on or off for every label and dimension on a sheet, click Enable Blanking or Disable Blanking.\nTo turn blanking on or off for every label and dimension on a sheet, click Enable Blanking or Disable Blanking.\nTo turn blanking on or off and set a blanking margin for an individual label, refer to Label Format Tab for further information.\nTo turn blanking on or off and set a blanking margin for an individual label, refer to Label Format Tab for further information.\nTo turn blanking on or off and set a blanking margin for an individual dimension, use the settings in the Misc group of the Properties window. Refer to Properties for further information.\nTo turn blanking on or off and set a blanking margin for an individual dimension, use the settings in the Misc group of the Properties window. Refer to Properties for further information.\nNote:\nApplying blanking settings at sheet level overrides any settings made at individual level, and vice versa.\n\n\n\nLabel Format Tab\nProperties\nBlanking Margin\nEnable Blanking\nDisable Blanking\nLabel Format Tab\nMisc\nProperties\nProperties\nNote\n:"}
{"Headers": "Leader Line Gaps", "Content": "Adds a leader line gap to a label.\n\n\n"}
{"Headers": "Leader Line Gap with Specified Diameter", "Content": "Adds gaps with a specified diameter to the leader lines of the currently selected labels.\nYou are prompted to Specify first point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the first point of the diameter of a circle to define the gap.\nYou are then prompted to Specify second point or <Finish>\nClick to identify the second point of the diameter of a circle to define the gap.\nThe process can be repeated, allowing you to add multiple gaps to leader lines.\nInput F at the prompt and press Enter to end the command. The gaps in the leader lines are created.\nThroughout the gap creation process you can press ESC to cancel the command. Additional functionality is also available.\nCentre\nPress the down arrow key and select Centre to define a gap with a specified radius. Refer to Leader Line Gap with Specified Radius for further information.\nFinish\nPress the down arrow key and select Finish to end the command.\nBack\nPress the down arrow key and select Back to redefine the most recently created gap.\nYou are prompted to Specify first point or <Finish>\n\nCentre\nPress the down arrow key and select Centre to define a gap with a specified radius. Refer to Leader Line Gap with Specified Radius for further information.\nFinish\nPress the down arrow key and select Finish to end the command.\nBack\nPress the down arrow key and select Back to redefine the most recently created gap.\nYou are prompted to Specify first point or <Finish>\n\n\n\nLeader Line Gap with Specified Radius\nSpecify first point or <Finish>\nEnter\nSpecify second point or <Finish>\nF\nEnter\nESC\nCentre\nCentre\nLeader Line Gap with Specified Radius\nFinish\nFinish\nBack\nBack\nSpecify first point or <Finish>"}
{"Headers": "Leader Line Gap with Specified Radius", "Content": "Adds gaps with a specified radius to the leader lines of the currently selected labels.\nYou are prompted to Specify first point or <Finish>\nInput C at the prompt and press Enter.\nYou are then prompted to Specify centre or <Finish>\nInput values in the dimension fields and press Enter or click to identify the centre point of the diameter of a circle to define the gap.\nYou are then prompted to Specify radius or <#mm>\nInput a dimensional value in the field and press Enter or click to identify the edge of the circle.\nThe process can be repeated, allowing you to add multiple gaps to leader lines.\nInput F at the prompt and press Enter to end the command. The gaps in the leader lines are created.\nThroughout the gap creation process you can press ESC to cancel the command. Additional functionality is also available.\nBy two points\nPress the down arrow key and select by Bytwo points to define a leader line gap with a specified diameter. Refer to Leader Line Gap with Specified Diameter for further information.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nBy two points\nPress the down arrow key and select by Bytwo points to define a leader line gap with a specified diameter. Refer to Leader Line Gap with Specified Diameter for further information.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nBy two points\nPress the down arrow key and select by Bytwo points to define a leader line gap with a specified diameter. Refer to Leader Line Gap with Specified Diameter for further information.\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nLeader Line Gap with Specified Diameter\nSpecify first point or <Finish>\nC\nEnter\nSpecify centre or <Finish>\nEnter\nSpecify radius or <#mm>\nEnter\nF\nEnter\nESC\nBy two points\nBytwo points\nLeader Line Gap with Specified Diameter\nFinish\nFinish"}
{"Headers": "Add Symbols to Drawings", "Content": "Adds a symbol to the drawing using the symbol template (SYTM) or ISODRAFT symbol template (ISOTM) elements which are small drawings that can be created and modified.\nRefer to Create Backing Sheets, Overlays, Symbol Templates, Isodraft Symbol Templates and Sheet Templates for further information.\nSymbols reflect the visual layers from the symbol template as long as the corresponding symbol properties are set to By Template (or By Style with the style properties set to By Template). Setting the symbol properties to By Layer overrides the symbol template and forces the use of the appropriate local sheet layer.\n\n\n\nCreate Backing Sheets, Overlays, Symbol Templates, Isodraft Symbol Templates and Sheet Templates\nCreate Backing Sheets, Overlays, Symbol Templates, Isodraft Symbol Templates and Sheet Templates\nBy Template\nBy Style\nBy Template\nBy Layer"}
{"Headers": "Add Symbol", "Content": "Adds a symbol to a drawing.\n\nThe Select window can be used to select the required SYTM or ISOTM element.\nIf the symbol templates are viewed as thumbnails, the Background Colour option becomes available. Click Background Colour to modify the background colour of all symbols in the currently selected symbol library using the Color palette. The background colour can be modified to prevent the symbol background being non-distinguishable from the symbol content.\nDouble-click the required element, or click the element and click Select. The symbol is used as the default symbol for the session until another symbol is selected.\nYou are prompted to Specify the insertion point or <Finish>\nA preview of the image displays at the cursor.\nInput values in the dimension fields and press Enter or click to identify the position of the symbol. The symbol is added to the drawing.\nYou are again prompted to Specify the insertion point or <Finish>\nThe prompt is repeated allowing you to create multiple copies of the symbol.\nInput F at the prompt and press Enter to end the command.\nThroughout the process of adding symbols to the drawing you can press ESC to cancel the command. Additional functionality is also available.\nTemplate\nPress the down arrow key and select Template to select a different symbol from the template.\nScale\nPress the down arrow key and select Scale to define the size of the symbol. Refer to Add Symbol with Specified Size for further information.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nTemplate\nPress the down arrow key and select Template to select a different symbol from the template.\nScale\nPress the down arrow key and select Scale to define the size of the symbol. Refer to Add Symbol with Specified Size for further information.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new SYMB element displays in the Draw Explorer.\n\nTemplate\nPress the down arrow key and select Template to select a different symbol from the template.\nScale\nPress the down arrow key and select Scale to define the size of the symbol. Refer to Add Symbol with Specified Size for further information.\nFinish\nPress the down arrow key and select Finish to end the command.\nNote:\nThe background change is not permanent. When the Select window is closed and reopened, the background colour reverts to the default colour specified in the project options.\n\n\n\nAdd Symbol with Specified Size\nSelect\nBackground Colour\nBackground Colour\nColor\nNote:\nSelect\nSelect\nSpecify the insertion point or <Finish>\nEnter\nSpecify the insertion point or <Finish>\nF\nEnter\nESC\nTemplate\nTemplate\nScale\nScale\nAdd Symbol with Specified Size\nFinish\nFinish"}
{"Headers": "Add Symbol with Specified Size", "Content": "Add a symbol to a drawing with a specified size.\n\nThe Select window can be used to select the required SYTM or ISOTM element.\nIf the symbol templates are viewed as thumbnails, the Background Colour option becomes available. Click Background Colour to modify the background colour of all symbols in the currently selected symbol library using the Color palette. The background colour can be modified to prevent the symbol background being non-distinguishable from the symbol content.\nDouble-click the required element, or click the element and click Select. The symbol is used as the default symbol for the session until another symbol is selected.\nYou are prompted to Specify the insertion point or <Finish>\nA preview of the image displays at the cursor.\nInput S at the prompt and press Enter.\nYou are then prompted to Specify X scale <1>\nInput a value in the field and press Enter to define the scale factor for the X dimension.\nYou are then prompted to Specify Y scale <1>\nInput a value in the field and press Enter to define the scale factor for the Y dimension.\nYou are then prompted to Specify the Insertion point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the position of the symbol. The symbol is added to the drawing.\nYou are again prompted to Specify the insertion point or <Finish>\nThe prompt is repeated allowing you to create multiple copies of the symbol.\nInput F at the prompt and press Enter to end the command.\nThroughout the process of adding symbols to the drawing you can press ESC to cancel the command. Additional functionality is also available.\nTemplate\nPress the down arrow key and select Template to select a different symbol from the template.\nScale\nPress the down arrow key and select Scale to modify the scale of the symbol.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nTemplate\nPress the down arrow key and select Template to select a different symbol from the template.\nScale\nPress the down arrow key and select Scale to modify the scale of the symbol.\nFinish\nPress the down arrow key and select Finish to end the command.\nThe new SYMB element displays in the Draw Explorer.\n\nTemplate\nPress the down arrow key and select Template to select a different symbol from the template.\nScale\nPress the down arrow key and select Scale to modify the scale of the symbol.\nFinish\nPress the down arrow key and select Finish to end the command.\nNote:\nThe background change is not permanent. When the Select window is closed and reopened, the background colour reverts to the default colour specified in the project options.\nNote:\nA value of less than 1 decreases the width of the symbol. For example, to reduce the width of the symbol by half, input 0.5 at the prompt.\n\n\n\nSelect\nBackground Colour\nBackground Colour\nColor\nNote:\nSelect\nSelect\nSpecify the insertion point or <Finish>\nS\nEnter\nSpecify X scale <1>\nEnter\nNote\n:\n0.5\nSpecify Y scale <1>\nEnter\nSpecify the Insertion point or <Finish>\nEnter\nSpecify the insertion point or <Finish>\nF\nEnter\nESC\nTemplate\nTemplate\nScale\nScale\nFinish\nFinish"}
{"Headers": "Add Images to Drawings", "Content": "Adds an image to a drawing.\nSelect the required image from the window and click Open\nYou are prompted to Specify the centre point or <By corner and scale>\nA preview of the image displays at the cursor.\n\nInput values in the dimension fields and press Enter or click to identify the location for the center of the image.\nYou are then prompted to enter the Scale <1>\nInput a value in the field and press Enter to define the scale factor. Alternatively you can move the cursor away from the insertion point to increase the size of the image or move the cursor closer to the insertion point to decrease the size of the image. Click to define the scale factor.\nYou are then prompted to enter the Rotation angle <0deg>\nInput an angular value in the field and press Enter to define the rotation angle. Alternatively, you can move the cursor around the centre of the image to visually select the required angle. A ghosted preview of the image rotates to reflect the angle. Click to define the rotation angle.\nThe image is added to the drawing.\nThroughout the process of adding the image to a drawing you can press ESC to cancel the command. Additional functionality is also available.\nBy corner and scale\nPress the down arrow key and select By corner and scale to insert an image with a specified corner point.\nYou are prompted to Specify the left down corner or.\nInput values in the dimension fields and press Enter or click to identify the location for the bottom-left of the image.\nThe image can then be scaled, rotated and positioned.\n\nBy corner and scale\nPress the down arrow key and select By corner and scale to insert an image with a specified corner point.\nYou are prompted to Specify the left down corner or.\nInput values in the dimension fields and press Enter or click to identify the location for the bottom-left of the image.\nThe image can then be scaled, rotated and positioned.\nThe new EXTIMG element displays in the Draw Explorer containing an ARCHIV element.\n\nBy corner and scale\nPress the down arrow key and select By corner and scale to insert an image with a specified corner point.\nYou are prompted to Specify the left down corner or.\nInput values in the dimension fields and press Enter or click to identify the location for the bottom-left of the image.\nThe image can then be scaled, rotated and positioned.\n\n\n\nOpen\nSpecify the centre point or <By corner and scale>\nEnter\nenter the Scale <1>\nEnter\nenter the Rotation angle <0deg>\nEnter\nESC\nBy corner and scale\nBy corner and scale\nSpecify the left down corner or\nEnter"}
{"Headers": "Add Overlays to Drawings", "Content": "Adds an overlay to a drawing sheet.\n\n\n"}
{"Headers": "Add Overlay", "Content": "Adds an overlay to a drawing sheet.\nSelect the required overlay sheet from the window and click Open\nYou are prompted to Specify the insertion point or <Finish>\nA preview of the overlay displays at the cursor.\nInput values in the dimension fields and press Enter or click to identify the insertion point for the overlay. The overlay is added to the drawing.\nThe prompt is repeated allowing you to add multiple overlays to the drawing.\nInput F at the prompt and press Enter to end the command.\nThroughout the process of adding overlays to the drawing you can press ESC to cancel the command. Additional functionality is also available.\nOver\nPress the down arrow key and select Over to select a different overlay. The Open Overlay Sheet Window displays.\nScale\nPress the down arrow key and select Scale to add an overlay with a specified scale. Refer to Add Overlay with Specified Scale for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nOver\nPress the down arrow key and select Over to select a different overlay. The Open Overlay Sheet Window displays.\nScale\nPress the down arrow key and select Scale to add an overlay with a specified scale. Refer to Add Overlay with Specified Scale for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new OLAY element displays in the Draw Explorer.\n\nOver\nPress the down arrow key and select Over to select a different overlay. The Open Overlay Sheet Window displays.\nScale\nPress the down arrow key and select Scale to add an overlay with a specified scale. Refer to Add Overlay with Specified Scale for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\n\n\nAdd Overlay with Specified Scale\nOpen\nSpecify the insertion point or <Finish>\nEnter\nF\nEnter\nESC\nOver\nOver\nOpen Overlay Sheet\nScale\nScale\nAdd Overlay with Specified Scale\nBack\nBack\nFinish\nFinish"}
{"Headers": "Add Overlay with Specified Scale", "Content": "Add an overlay to a drawing sheet with a specified scale.\nSelect the required overlay sheet from the window and click Open\nYou are prompted to Specify the insertion point or <Finish>\nInput S at the prompt or press the down arrow key and select Scale\nYou are then prompted to Specify X scale <1>\nInput a value in the field and press Enter to define the scale factor for the X dimension.\nYou are then prompted to Specify Y scale <1>\nInput a value in the field and press Enter to define the scale factor for the Y dimension. The overlay is added to the drawing.\nYou are again prompted to Specify the insertion point or <Finish>\nThe prompt is repeated allowing you to add multiple overlays to the drawing.\nInput F at the prompt and press Enter to end the command.\nThroughout the process of adding overlays to the drawing you press ESC to cancel the command. Additional functionality is also available.\nOver\nPress the down arrow key and select Over to select a different overlay. The Open Overlay Sheet Window displays.\nScale\nPress the down arrow key and select Scale to define a different scale factor for the overlay.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nOver\nPress the down arrow key and select Over to select a different overlay. The Open Overlay Sheet Window displays.\nScale\nPress the down arrow key and select Scale to define a different scale factor for the overlay.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\n\nThe new OLAY element displays in the Draw Explorer.\n\nOver\nPress the down arrow key and select Over to select a different overlay. The Open Overlay Sheet Window displays.\nScale\nPress the down arrow key and select Scale to define a different scale factor for the overlay.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nNote:\nA value of less than 1 decreases the width of the overlay. For example, to reduce the width of the overlay by half, input 0.5 at the prompt.\n\n\n\nOpen\nSpecify the insertion point or <Finish>\nS\nScale\nSpecify X scale <1>\nEnter\nNote\n:\n0.5\nSpecify Y scale <1>\nEnter\nSpecify the insertion point or <Finish>\nF\nEnter\nESC\nOver\nOver\nOpen Overlay Sheet\nScale\nScale\nBack\nBack\nFinish\nFinish"}
{"Headers": "Define Required Layers of Overlay Elements", "Content": "Sets the visible layers of the currently selected Overlay (OLAY) element using the Properties window.\n\nSelect the Layer Visibility drop-down list to display the available OLAY layers.\n\nSelect the required check boxes to define the visible layers.\nThe ALL and DESI check boxes display by default, all other check boxes are added dynamically. If you select the ALL check box, all other check boxes in the drop-down list become inactive.\n\n\n\nProperties\nLayer Visibility\nALL\nDESI\nALL"}
{"Headers": "Intelligent Text", "Content": "Adds intelligent text to the Text Editor window.\n\nSelect a category from the drop-down list. The list of intelligent code words associated with the category displays.\nSelect the intelligent text to add to the annotation and click Insert selected Intelligent Text. The text is added to the Text Editor window at the current cursor position.\n\n\n\nText Editor\nInsert selected Intelligent Text\nText Editor"}
{"Headers": "Modify Intelligent Text Properties", "Content": "Modifies annotations that contain intelligent text using the Properties window.\nOn the Properties window, select the property to be modified (for example, Dim line text or Projection line text).\nDim line text\nIf the By style property is set to Yes, the field displays By Style.\nIf the By style property is set to No, the field displays the annotation text value. Click to add intelligent text fields to the annotation.\nBy Style\nSelect Yes from the drop-down list to inherit the annotation text from the visual style.\nSelect No from the drop-down list to explicitly define the annotation text.\nValue\nAllows you to modify the annotation text explicitly.\nDim line text\nIf the By style property is set to Yes, the field displays By Style.\nIf the By style property is set to No, the field displays the annotation text value. Click to add intelligent text fields to the annotation.\nBy Style\nSelect Yes from the drop-down list to inherit the annotation text from the visual style.\nSelect No from the drop-down list to explicitly define the annotation text.\nValue\nAllows you to modify the annotation text explicitly.\n\nDim line text\nIf the By style property is set to Yes, the field displays By Style.\nIf the By style property is set to No, the field displays the annotation text value. Click to add intelligent text fields to the annotation.\nBy Style\nSelect Yes from the drop-down list to inherit the annotation text from the visual style.\nSelect No from the drop-down list to explicitly define the annotation text.\nValue\nAllows you to modify the annotation text explicitly.\n\n\n\nProperties\nProperties\nDim line text\nProjection line text\nDim line text\nBy style\nYes\nBy Style\nBy style\nNo\n\nBy Style\nYes\nNo\nValue"}
{"Headers": "Add Tables to Drawings", "Content": "Adds a table to a drawing.\nYou are prompted to Specify start point\nInput values in the dimension fields and press Enter or click to identify the first corner of the table.\nYou are then prompted to Specify end point\nInput values in the dimension fields and press Enter or click to identify the opposite corner of the table. The outline of the table is drawn.\n\nYou are then prompted to Specify number of columns <10>\nInput the required number of columns at the prompt and press Enter.\nYou are then prompted to Specify the number or rows <10>\nInput the required number of rows at the prompt and press Enter.\n\nThe table is then added to the drawing.\n\nThe new TEXP element displays in the Draw Explorer.\n\n\n\n\nSpecify start point\nEnter\nSpecify end point\nEnter\nSpecify number of columns <10>\nEnter\nSpecify the number or rows <10>\nEnter"}
{"Headers": "Add Marker Points", "Content": "Adds a marker point to a drawing.\n\n\n"}
{"Headers": "Add Marker Points", "Content": "Adds a marker point to a drawing.\nYou are prompted to Specify the insertion point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the insertion point for the marker. The marker point is added to the drawing.\nThe prompt is repeated, allowing you to create multiple marker points.\nInput F at the prompt and press Enter to end the command.\nThroughout the process of adding marker points to the drawing you can press ESC to cancel the command. Additional functionality is also available.\nGlyph\nPress the down arrow key and select Glyph to select a different symbol for the marker point. Refer to Add Marker Point with Specified Glyph for further information.\nSize\nPress the down arrow key and select Size to specify the size of the marker point. Refer to Add Marker Point with Specified Size for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the marker point to the drawing.\n\nGlyph\nPress the down arrow key and select Glyph to select a different symbol for the marker point. Refer to Add Marker Point with Specified Glyph for further information.\nSize\nPress the down arrow key and select Size to specify the size of the marker point. Refer to Add Marker Point with Specified Size for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the marker point to the drawing.\n\nThe new MRKP element displays in the Draw Explorer.\n\nGlyph\nPress the down arrow key and select Glyph to select a different symbol for the marker point. Refer to Add Marker Point with Specified Glyph for further information.\nSize\nPress the down arrow key and select Size to specify the size of the marker point. Refer to Add Marker Point with Specified Size for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the marker point to the drawing.\n\n\n\nAdd Marker Point with Specified Glyph\nAdd Marker Point with Specified Size\nSpecify the insertion point or <Finish>\nEnter\nF\nEnter\nESC\nGlyph\nGlyph\nAdd Marker Point with Specified Glyph\nSize\nSize\nAdd Marker Point with Specified Size\nBack\nBack\nFinish\nFinish\nInsert\nInsert"}
{"Headers": "Add Marker Point with Specified Glyph", "Content": "Adds a marker point to a drawing with a specified glyph.\nYou are prompted to Specify the insertion point or <Finish>\nInput G at the prompt and press Enter to display the Glyph Selection window.\n\nClick to identify the required marker symbol.\nBy default, the Glyph Selection window closes and you are prompted to Specify the insertion point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the insertion point for the marker. The marker point is added to the drawing.\nThe prompt is repeated, allowing you to create multiple marker points.\nInput F at the prompt and press Enter to end the command.\nThroughout the process of adding marker points to the drawing you can press ESC to cancel the command. Additional functionality is also available.\nGlyph\nPress the down arrow key and select Glyph to select a different symbol for the marker point.\nSize\nPress the down arrow key and select Size to specify the size of the marker point. Refer to Add Marker Point with Specified Size for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the marker point to the drawing. Refer to Add Marker Points for further information.\n\nGlyph\nPress the down arrow key and select Glyph to select a different symbol for the marker point.\nSize\nPress the down arrow key and select Size to specify the size of the marker point. Refer to Add Marker Point with Specified Size for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the marker point to the drawing. Refer to Add Marker Points for further information.\n\nThe new MRKP element displays in the Draw Explorer.\n\nGlyph\nPress the down arrow key and select Glyph to select a different symbol for the marker point.\nSize\nPress the down arrow key and select Size to specify the size of the marker point. Refer to Add Marker Point with Specified Size for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the marker point to the drawing. Refer to Add Marker Points for further information.\n\n\n\nAdd Marker Point with Specified Size\nAdd Marker Points\nSpecify the insertion point or <Finish>\nG\nEnter\nGlyph Selection\nGlyph Selection\nSpecify the insertion point or <Finish>\nEnter\nF\nEnter\nESC\nGlyph\nGlyph\nSize\nSize\nAdd Marker Point with Specified Size\nBack\nBack\nFinish\nFinish\nInsert\nInsert\nAdd Marker Points"}
{"Headers": "Add Marker Point with Specified Size", "Content": "Adds a marker point to a drawing with a specified size.\nYou are prompted to Specify the insertion point or <Finish>\nInput S at the prompt and press Enter.\nYou are then prompted to Specify the glyph size or <#mm>\nInput a dimensional value in the field and press Enter to define the size of the marker point.\nYou are again prompted to Specify the insertion point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the insertion point for the marker. The marker point is added to the drawing.\nThe prompt is repeated, allowing you to create multiple marker points.\nInput F at the prompt and press Enter to end the command.\nThroughout the process of adding marker points to the drawing you can press ESC to cancel the command. Additional functionality is also available.\nGlyph\nPress the down arrow key and select Glyph to select a different symbol for the marker point. Refer to Add Marker Point with Specified Glyph for further information.\nSize\nPress the down arrow key and select Size to specify a different size for the marker point.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the marker point to the drawing. Refer to Add Marker Points for further information.\n\nGlyph\nPress the down arrow key and select Glyph to select a different symbol for the marker point. Refer to Add Marker Point with Specified Glyph for further information.\nSize\nPress the down arrow key and select Size to specify a different size for the marker point.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the marker point to the drawing. Refer to Add Marker Points for further information.\n\nThe new MRKP element displays in the Draw Explorer.\n\nGlyph\nPress the down arrow key and select Glyph to select a different symbol for the marker point. Refer to Add Marker Point with Specified Glyph for further information.\nSize\nPress the down arrow key and select Size to specify a different size for the marker point.\nBack\nPress the down arrow key and select Back to undo the last action.\nFinish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the marker point to the drawing. Refer to Add Marker Points for further information.\n\n\n\nAdd Marker Point with Specified Glyph\nAdd Marker Points\nSpecify the insertion point or <Finish>\nS\nEnter\nSpecify the glyph size or <#mm>\nEnter\nSpecify the insertion point or <Finish>\nEnter\nF\nEnter\nESC\nGlyph\nGlyph\nAdd Marker Point with Specified Glyph\nSize\nSize\nBack\nBack\nFinish\nFinish\nInsert\nInsert\nAdd Marker Points"}
{"Headers": "Add Connection Points", "Content": "Creates intelligent connection points on a symbol (SYMB) or symbol template (SYTM). Connectors or annotation leader lines can be connected to the connection points.\nYou are prompted to Specify the insertion point or <Finish>\nInput values in the dimension fields and press Enter or click to identify the position of the connection point.\nThe prompt is repeated, multiple connection points can be created.\nInput F at the prompt and press Enter to end the command.\nThroughout the connection point creation process you can press ESC to cancel the command. Additional functionality is also available.\nSize\nPress the down arrow key and select Size to specify a different size for the connection point.\nBack\nPress the down arrow key and select Back to undo the last action.\nFInish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the connection point to the symbol.\n\nSize\nPress the down arrow key and select Size to specify a different size for the connection point.\nBack\nPress the down arrow key and select Back to undo the last action.\nFInish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the connection point to the symbol.\n\nThe connection point extended line indicates the connection direction. The associated connector can be connected using the specified direction.Refer to Status Bar for further information.\nUse the rotate grip point to modify the direction of the connection point extended line. Refer to Rotate Objects using Grip Points for further information.\nThe new SYCNPT elements display in the Draw Explorer.\n\nSize\nPress the down arrow key and select Size to specify a different size for the connection point.\nBack\nPress the down arrow key and select Back to undo the last action.\nFInish\nPress the down arrow key and select Finish to end the command.\nInsert\nPress the down arrow key and select Insert to add the connection point to the symbol.\n\n\n\nStatus Bar\nRotate Objects using Grip Points\nSpecify the insertion point or <Finish>\nEnter\nF\nEnter\nESC\nSize\nSize\nBack\nBack\nFInish\nFinish\nInsert\nInsert\nStatus Bar\nRotate Objects using Grip Points"}
{"Headers": "Add Excel Tables", "Content": "Adds a Microsoft Excel table to a drawing.\nSelect the required Excel file from the window and click Open\nYou are prompted to Specify the centre point or <By corner and scale>\nA ghosted preview of the Excel table displays at the cursor.\nInput values in the dimension fields and press Enter or click to identify the location for the center of the Excel table.\nYou are then prompted to enter the Scale <1>\nInput a value in the field and press Enter to define the scale factor. Alternatively you can move the cursor away from the insertion point to increase the size of the Excel table or move the cursor closer to the insertion point to decrease the size of the Excel table. Click to define the scale factor.\nYou are then prompted to enter the Rotation angle <#deg>\nInput an angular value in the field and press Enter to define the rotation angle. Alternatively, you can move the cursor around the center of the Excel table to visually select the required angle. A ghosted preview of the image rotates to reflect the angle. Click to define the rotation angle.\nThe Excel table is added to the drawing.\n\nThroughout the process of adding the Excel table to a drawing you can press ESC to cancel the command. Additional functionality is also available.\nBy corner and scale\nPress the down arrow key and select By corner and scale to insert an Excel table with a specified corner point.\nYou are prompted to Specify the left down corner.\nInput values in the dimension fields and press Enter or click to identify the location for the bottom-left of the Excel table.\nThe Excel table can then be scaled, rotated and positioned.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nBy corner and scale\nPress the down arrow key and select By corner and scale to insert an Excel table with a specified corner point.\nYou are prompted to Specify the left down corner.\nInput values in the dimension fields and press Enter or click to identify the location for the bottom-left of the Excel table.\nThe Excel table can then be scaled, rotated and positioned.\nBack\nPress the down arrow key and select Back to undo the last action.\nThe new EXTIMG element displays in the Draw Explorer containing an ARCHIV element and an EXTDAT element. The EXTDAT element contains an ARCHIV element.\n\nTo modify the Excel table, double-click on the table to open Microsoft Excel.\nYou can make changes to the Excel table and save the file. The table on the drawing canvas is automatically updated.\nBy corner and scale\nPress the down arrow key and select By corner and scale to insert an Excel table with a specified corner point.\nYou are prompted to Specify the left down corner.\nInput values in the dimension fields and press Enter or click to identify the location for the bottom-left of the Excel table.\nThe Excel table can then be scaled, rotated and positioned.\nBack\nPress the down arrow key and select Back to undo the last action.\n\n\n\nOpen\nSpecify the centre point or <By corner and scale>\nEnter\nenter the Scale <1>\nEnter\nenter the Rotation angle <#deg>\nEnter\nESC\nBy corner and scale\nBy corner and scale\nSpecify the left down corner\nEnter\nBack\nBack"}
{"Headers": "Grid Ruler", "Content": "Adds a grid ruler annotation that allows you to visualize the grid plane positions of a reference grid. Grid rulers can be added to orthogonal views, including advanced views.\nBy default, a grid ruler is associated with the main reference grid. Refer to Main Reference Grid for further information. You can select an alternative reference grid during grid ruler creation. Additional functionality is available to create baseline rulers, center line rulers and baseline and center line rulers.\nWhen base line or center line rulers are created using the menu options of the grid ruler function, the rulers are created using the defined active visual style for the grid ruler, refer to Active Visual Styles for further information. When base line or center line rulers are created using the Fluent UI options, the rulers are created using the defined base line ruler and center line ruler visual styles in the system defaults, refer to Visual Styles for further information.\n\n\n\nMain Reference Grid\nActive Visual Styles\nVisual Styles\nMain Reference Grid\nActive Visual Styles\nVisual Styles"}
{"Headers": "Create Grid Ruler", "Content": "Adds a grid ruler to an orthogonal view.\nYou are prompted to Select view\nClick to identify the view, a preview of the ruler displays. Move the cursor from the top of the frame downwards to create a horizontal ruler or from the left of the frame inwards to create a vertical ruler.\nYou are prompted to Specify insertion point or\nInput values in the dimension fields and press Enter or click to identify the position of the ruler. The ruler is created.\nThroughout the ruler creation process you can press ESC to cancel the command. Additional functionality is also available.\nGrid\nPress the down arrow key and select Grid to modify the ruler association with a grid.\nYou are prompted to Enter grid name\nInput the name of the grid in the field to associate with the ruler.\nCentre line\nPress the down arrow key and select Centre line to create a ruler at the center line of the view. Refer to Create Center Line Ruler for further information.\nBase line\nPress the down arrow key and select Base line to create a ruler at the base line of the view. Refer to Create Base Line Ruler for further information.\n\nGrid\nPress the down arrow key and select Grid to modify the ruler association with a grid.\nYou are prompted to Enter grid name\nInput the name of the grid in the field to associate with the ruler.\nCentre line\nPress the down arrow key and select Centre line to create a ruler at the center line of the view. Refer to Create Center Line Ruler for further information.\nBase line\nPress the down arrow key and select Base line to create a ruler at the base line of the view. Refer to Create Base Line Ruler for further information.\n\nThe new GRDRLR element displays in the Draw Explorer.\n\nGrid\nPress the down arrow key and select Grid to modify the ruler association with a grid.\nYou are prompted to Enter grid name\nInput the name of the grid in the field to associate with the ruler.\nCentre line\nPress the down arrow key and select Centre line to create a ruler at the center line of the view. Refer to Create Center Line Ruler for further information.\nBase line\nPress the down arrow key and select Base line to create a ruler at the base line of the view. Refer to Create Base Line Ruler for further information.\nNote:\nThe prompt does not display if a view is already selected.\n\n\n\nCreate Center Line Ruler\nCreate Base Line Ruler\nSelect view\nNote\n:\nSpecify insertion point or\nEnter\nESC\nGrid\nGrid\nEnter grid name\nCentre line\nCentre line\nCreate Center Line Ruler\nBase line\nBase line\nCreate Base Line Ruler"}
{"Headers": "Create Center Line Ruler", "Content": "Adds a centre line ruler to an orthogonal view.\nYou are prompted to Select view\nClick to identify the view, the ruler is created and positioned at the center line of the view.\n\nThe new GRDRLR element displays in the Draw Explorer.\n\nNote:\nThe prompt does not display if a view is already selected.\n\n\n\nSelect view\nNote"}
{"Headers": "Create Center Line and Base Line Ruler", "Content": "Adds a center line and a base line ruler to an orthogonal view.\nYou are prompted to Select view\nClick to identify the view, the rulers are created and positioned at the center line and base line of the view.\n\nThe new GRDRLR element displays in the Draw Explorer.\n\nNote:\nThe prompt does not display if a view is already selected.\n\n\n\nSelect view\nNote\n:"}
{"Headers": "Modify Ruler", "Content": "Sets the ruler properties to alter the display using the Properties window.\n\nThe content and location properties can be modified to define the display of the ruler.\nClosing Ticks\nDisplays grid ruler first and last ticks as long ticks with labels.\nOff - Long ticks with labels are placed on grid ruler main locations indicated by long tick index.\nOn - Long ticks with labels are placed on grid ruler closing ticks and main locations indicated by long tick index.\nAuto - Grid ruler displays at least two long ticks with labels. Closing ticks are added when necessary on short grid rulers.\nBy Style - Closing ticks are defined by the grid ruler style.\nWhen creating grid rulers on narrow views, the ruler length may be automatically extended to include at least two ticks when the closing ticks property is enabled in the grid ruler visual style.\nClosing Ticks\nDisplays grid ruler first and last ticks as long ticks with labels.\nOff - Long ticks with labels are placed on grid ruler main locations indicated by long tick index.\nOn - Long ticks with labels are placed on grid ruler closing ticks and main locations indicated by long tick index.\nAuto - Grid ruler displays at least two long ticks with labels. Closing ticks are added when necessary on short grid rulers.\nBy Style - Closing ticks are defined by the grid ruler style.\nWhen creating grid rulers on narrow views, the ruler length may be automatically extended to include at least two ticks when the closing ticks property is enabled in the grid ruler visual style.\n\nClosing Ticks\nDisplays grid ruler first and last ticks as long ticks with labels.\nOff - Long ticks with labels are placed on grid ruler main locations indicated by long tick index.\nOn - Long ticks with labels are placed on grid ruler closing ticks and main locations indicated by long tick index.\nAuto - Grid ruler displays at least two long ticks with labels. Closing ticks are added when necessary on short grid rulers.\nBy Style - Closing ticks are defined by the grid ruler style.\nWhen creating grid rulers on narrow views, the ruler length may be automatically extended to include at least two ticks when the closing ticks property is enabled in the grid ruler visual style.\n\n\n\nProperties\nClosing Ticks\nOff\nOn\nAuto\nBy Style"}
{"Headers": "Automatic Tagging", "Content": "Automatically generates labels for a set of design items that match a tagging rule (TAGR). Tagging rules are part of tag rule sets (TRSTs), which are part of tagging libraries (TRLBs).\nThe rule sets determine the type of label, and which design items the labels are applied to. For example, all nozzles that have a bore of >100mm and <300mm with a pressure rating of #150. After the labels have been created, they can be automatically updated to reflect any changes to the 3D model. When the labels have been created, their positions can be adjusted graphically.\nYou are prompted to Select element\nClick to identify the element to apply automatic tagging to. The Automatic Tagging window displays.\n\nThe Automatic Tagging window allows you to specify the conditions for automatically generating labels for one or more views in a sheet.\nLayer\nAllows you to define a layer for the current view that can own GLAB and SLAB elements created using auto tagging.\nSelect from the drop-down list to define a layer for the current view.\nClick to create a new automatic tagging layer. Refer to Create Automatic Tagging Layer for further information.\nNote:\nYou can manually replace the Purpose attribute of the LAYE element from TAG[A-Z] to LAY[A-Z]. For example, LAYA, LAYB, LAYC. The LAYE cascade of attribute values is then used for label terminator type (Lterminator) and terminator size (Tsiztx) attributes instead of ByVStyle (because these form too many possible combinations to be reflected by the visual style). Other attributes are unaffected.\nLibrary Tagging\nRef Library\nDisplays the tag rule library. An alternative library can be selected with the User Defaults window. Refer to Modify User Defaults for further information.\nTag Library\nSelect Piping from the drop-down list to define piping as the type of item required for tagging.\nSelect Equipment from the drop-down list to define equipment as type of item required for tagging.\nSelect Structural from the drop-down list to define structural as the type of item required for tagging.\nStyle\nSelect from the drop-down list to define a filtered item type for tagging.\nThe available list varies depending on the option selected from the Tag Library List.\nApply\nClick to apply the Library Tagging settings. The Confirm window displays.\nThe Confirm window informs you that all current tags in the layer will be lost.\nClick Yes to confirm the settings or No to discard any changes.\nLocal Tagging\nCopy Library Style\nAllows you to copy an existing Library Tagging Style and modify the tag rule, defining which elements are to be tagged.\nNote:\nAfter copying a library style, the Style field in Library Tagging is unset. If the Style field is already unset, no style is copied when Copy Library Style is clicked. The following error message displays:\nClick OK.\nTag\nSelect from the drop-down list to define the item type to be tagged.\nRule\nSelect from the drop-down list to define the tagging rule from the local style.\nCreate\nClick to create a new rule name based on the type of equipment to be tagged. For example, EQUIPMENT-1.\nFurther creation of a Local Tagging Rules using the same element type increments the suffix of the rule name. For example, EQUIPMENT-2.\nDelete\nClick to delete the Local Tagging Rule from the Rule list.\nWith\nAllows you to enter selection criteria to filter the selected element types using standard operands.\nFor example, if the selected element type is Valve, an entry of STYPE EQ 'GATE' AND ABBORE GE 80 in the Width field would select only gate valves with a bore greater or equal to 80mm.\nTemplate Type\nSelect Library from the drop-down list to define a library template type.\nSelect Local from the drop-down list to define a local template type.\nAttributes\nIf Library is selected from the Template Type drop-down list:\nClick to display the Select window.\nYou can browse and select the required STYM or TXTM.\nClick Select to apply the selected template.\nClick Cancel to discard any changes and close the Select window.\nIf Local is selected from the Template Type drop-down list:\nSelect Text Settings from the drop-down list to define the label text attributes. Refer to Label Text Attributes for further information.\nSelect Text Contents from the drop-down list to modify the label text. Refer to Modify Label Text for further information.\nSelect Frame from the drop-down list to define the label frame attributes. Refer to Label Frame Attributes for further information.\nSelect Leader Line from the drop-down list to modify the label leader line. Refer to Tagging Template Leader Line Line for further information.\nTemplate Ref\nDisplays the currently selected element.\nApply\nClick to create a tag rule (TGR) element and label master (GLAB) element beneath the LAYE element in the hierarchy based on the selected options.\nPline Name\nSelect from the drop-down list to define the p-line connection point.\nProportional Distance\nThe proportional distance is stored along the p-line from its start (0.0 to 1.0). The default value is 0.5 and can be altered. The initial value of 0.5 is the midpoint of the p-line.\nRegenerate All Tags\nSelect the check box to regenerate tags using the current settings for either Library or Local Tagging.\nRemove Redundant Tags\nClick to remove all redundant tags.\nLayer\nAllows you to define a layer for the current view that can own GLAB and SLAB elements created using auto tagging.\nSelect from the drop-down list to define a layer for the current view.\nClick to create a new automatic tagging layer. Refer to Create Automatic Tagging Layer for further information.\nLibrary Tagging\n\nDisplays the tag rule library. An alternative library can be selected with the User Defaults window. Refer to Modify User Defaults for further information.\nSelect Piping from the drop-down list to define piping as the type of item required for tagging.\nSelect Equipment from the drop-down list to define equipment as type of item required for tagging.\nSelect Structural from the drop-down list to define structural as the type of item required for tagging.\nSelect from the drop-down list to define a filtered item type for tagging.\nThe available list varies depending on the option selected from the Tag Library List.\nClick to apply the Library Tagging settings. The Confirm window displays.\n\nThe Confirm window informs you that all current tags in the layer will be lost.\nClick Yes to confirm the settings or No to discard any changes.\nLocal Tagging\n\nAllows you to copy an existing Library Tagging Style and modify the tag rule, defining which elements are to be tagged.\n\nClick OK.\nSelect from the drop-down list to define the item type to be tagged.\nSelect from the drop-down list to define the tagging rule from the local style.\nClick to create a new rule name based on the type of equipment to be tagged. For example, EQUIPMENT-1.\nFurther creation of a Local Tagging Rules using the same element type increments the suffix of the rule name. For example, EQUIPMENT-2.\nClick to delete the Local Tagging Rule from the Rule list.\nAllows you to enter selection criteria to filter the selected element types using standard operands.\nFor example, if the selected element type is Valve, an entry of STYPE EQ 'GATE' AND ABBORE GE 80 in the Width field would select only gate valves with a bore greater or equal to 80mm.\nSelect Library from the drop-down list to define a library template type.\nSelect Local from the drop-down list to define a local template type.\nIf Library is selected from the Template Type drop-down list:\nClick to display the Select window.\n\nYou can browse and select the required STYM or TXTM.\nClick Select to apply the selected template.\nClick Cancel to discard any changes and close the Select window.\nIf Local is selected from the Template Type drop-down list:\nDisplays the currently selected element.\nClick to create a tag rule (TGR) element and label master (GLAB) element beneath the LAYE element in the hierarchy based on the selected options.\nPline Name\nSelect from the drop-down list to define the p-line connection point.\nProportional Distance\nThe proportional distance is stored along the p-line from its start (0.0 to 1.0). The default value is 0.5 and can be altered. The initial value of 0.5 is the midpoint of the p-line.\nRegenerate All Tags\nSelect the check box to regenerate tags using the current settings for either Library or Local Tagging.\nRemove Redundant Tags\nClick to remove all redundant tags.\nClick Update to generate the tags.\nLayer\nAllows you to define a layer for the current view that can own GLAB and SLAB elements created using auto tagging.\nSelect from the drop-down list to define a layer for the current view.\nClick to create a new automatic tagging layer. Refer to Create Automatic Tagging Layer for further information.\nNote:\nYou can manually replace the Purpose attribute of the LAYE element from TAG[A-Z] to LAY[A-Z]. For example, LAYA, LAYB, LAYC. The LAYE cascade of attribute values is then used for label terminator type (Lterminator) and terminator size (Tsiztx) attributes instead of ByVStyle (because these form too many possible combinations to be reflected by the visual style). Other attributes are unaffected.\nLibrary Tagging\nRef Library\nDisplays the tag rule library. An alternative library can be selected with the User Defaults window. Refer to Modify User Defaults for further information.\nTag Library\nSelect Piping from the drop-down list to define piping as the type of item required for tagging.\nSelect Equipment from the drop-down list to define equipment as type of item required for tagging.\nSelect Structural from the drop-down list to define structural as the type of item required for tagging.\nStyle\nSelect from the drop-down list to define a filtered item type for tagging.\nThe available list varies depending on the option selected from the Tag Library List.\nApply\nClick to apply the Library Tagging settings. The Confirm window displays.\nThe Confirm window informs you that all current tags in the layer will be lost.\nClick Yes to confirm the settings or No to discard any changes.\nLocal Tagging\nCopy Library Style\nAllows you to copy an existing Library Tagging Style and modify the tag rule, defining which elements are to be tagged.\nNote:\nAfter copying a library style, the Style field in Library Tagging is unset. If the Style field is already unset, no style is copied when Copy Library Style is clicked. The following error message displays:\nClick OK.\nTag\nSelect from the drop-down list to define the item type to be tagged.\nRule\nSelect from the drop-down list to define the tagging rule from the local style.\nCreate\nClick to create a new rule name based on the type of equipment to be tagged. For example, EQUIPMENT-1.\nFurther creation of a Local Tagging Rules using the same element type increments the suffix of the rule name. For example, EQUIPMENT-2.\nDelete\nClick to delete the Local Tagging Rule from the Rule list.\nWith\nAllows you to enter selection criteria to filter the selected element types using standard operands.\nFor example, if the selected element type is Valve, an entry of STYPE EQ 'GATE' AND ABBORE GE 80 in the Width field would select only gate valves with a bore greater or equal to 80mm.\nTemplate Type\nSelect Library from the drop-down list to define a library template type.\nSelect Local from the drop-down list to define a local template type.\nAttributes\nIf Library is selected from the Template Type drop-down list:\nClick to display the Select window.\nYou can browse and select the required STYM or TXTM.\nClick Select to apply the selected template.\nClick Cancel to discard any changes and close the Select window.\nIf Local is selected from the Template Type drop-down list:\nSelect Text Settings from the drop-down list to define the label text attributes. Refer to Label Text Attributes for further information.\nSelect Text Contents from the drop-down list to modify the label text. Refer to Modify Label Text for further information.\nSelect Frame from the drop-down list to define the label frame attributes. Refer to Label Frame Attributes for further information.\nSelect Leader Line from the drop-down list to modify the label leader line. Refer to Tagging Template Leader Line Line for further information.\nTemplate Ref\nDisplays the currently selected element.\nApply\nClick to create a tag rule (TGR) element and label master (GLAB) element beneath the LAYE element in the hierarchy based on the selected options.\nPline Name\nSelect from the drop-down list to define the p-line connection point.\nProportional Distance\nThe proportional distance is stored along the p-line from its start (0.0 to 1.0). The default value is 0.5 and can be altered. The initial value of 0.5 is the midpoint of the p-line.\nRegenerate All Tags\nSelect the check box to regenerate tags using the current settings for either Library or Local Tagging.\nRemove Redundant Tags\nClick to remove all redundant tags.\nSelect Text Settings from the drop-down list to define the label text attributes. Refer to Label Text Attributes for further information.\nSelect Text Contents from the drop-down list to modify the label text. Refer to Modify Label Text for further information.\nSelect Frame from the drop-down list to define the label frame attributes. Refer to Label Frame Attributes for further information.\nSelect Leader Line from the drop-down list to modify the label leader line. Refer to Tagging Template Leader Line Line for further information.\nSelect Text Settings from the drop-down list to define the label text attributes. Refer to Label Text Attributes for further information.\nSelect Text Settings from the drop-down list to define the label text attributes. Refer to Label Text Attributes for further information.\nSelect Text Contents from the drop-down list to modify the label text. Refer to Modify Label Text for further information.\nSelect Text Contents from the drop-down list to modify the label text. Refer to Modify Label Text for further information.\nSelect Frame from the drop-down list to define the label frame attributes. Refer to Label Frame Attributes for further information.\nSelect Frame from the drop-down list to define the label frame attributes. Refer to Label Frame Attributes for further information.\nSelect Leader Line from the drop-down list to modify the label leader line. Refer to Tagging Template Leader Line Line for further information.\nSelect Leader Line from the drop-down list to modify the label leader line. Refer to Tagging Template Leader Line Line for further information.\nNote:\nYou can manually replace the Purpose attribute of the LAYE element from TAG[A-Z] to LAY[A-Z]. For example, LAYA, LAYB, LAYC. The LAYE cascade of attribute values is then used for label terminator type (Lterminator) and terminator size (Tsiztx) attributes instead of ByVStyle (because these form too many possible combinations to be reflected by the visual style). Other attributes are unaffected.\nNote:\nAfter copying a library style, the Style field in Library Tagging is unset. If the Style field is already unset, no style is copied when Copy Library Style is clicked. The following error message displays:\n\n\n\nCreate Automatic Tagging Layer\nModify User Defaults\nLabel Text Attributes\nModify Label Text\nLabel Frame Attributes\nTagging Template Leader Line\nSelect element\nAutomatic Tagging\nAutomatic Tagging\nLayer\nCreate Automatic Tagging Layer\nNote\n:\nLibrary Tagging\nRef Library\nUser Defaults\nModify User Defaults\nTag Library\nPiping\nEquipment\nStructural\nStyle\nApply\nConfirm\nConfirm\nYes\nNo\nLocal Tagging\nCopy Library Style\nNote\n:\nOK\nTag\nRule\nCreate\nDelete\nWith\nTemplate Type\nLibrary\nLocal\nAttributes\nLibrary\nTemplate Type\nSelect\nSelect\nCancel\nSelect\nLocal\nTemplate Type\nText Settings\nLabel Text Attributes\nText Contents\nModify Label Text\nFrame\nLabel Frame Attributes\nLeader Line\nTagging Template Leader Line\nTemplate Ref\nApply\nPline Name\nProportional Distance\nRegenerate All Tags\nRemove Redundant Tags\nUpdate"}
{"Headers": "Create Automatic Tagging Layer", "Content": "Creates an automatic tagging layer.\n\nThe Create LAYE window displays a default name for the element. Input a different name if required.\nClick OK to apply the LAYE name or Cancel to discard any changes and close the Create LAYE window.\n\n\n\nCreate LAYE\nOK\nCancel\nCreate LAYE"}
{"Headers": "Label Text Attributes", "Content": "Sets label text attributes.\n\nCE\nClick to identify the currently selected GLAB as the working element.\nText\nSelect from the drop-down list to define the representation colour for text.\nAlternatively, click Pick to display the Pick a colour window. The functionality of the Pick a colour window is explained, refer to Pens for further information.\nFont\nSelect from the drop-down list to define the font.\nIf you select True Type Font the True Type font selection window displays\nSelect the DB ordering option button to order the True Type fonts list by database order.\nSelect the Face name option button to order the True Type fonts list by Face name.\nSelect the Font ID option button to order the True Type fonts list by font ID.\nSelect the Description option button to order the True Type fonts list by description.\nSelect the Bold check box to apply bold formatting to the font style.\nSelect the Italic check box to apply italic formatting to the font style.\nClick OK to confirm the selection or Cancel to discard any changes and close the True Type font selection window.\nJustification\nSelect Left from the drop-down list to left justify the label text.\nSelect Right from the drop-down list to right justify the label text.\nSelect Centre from the drop-down list to centre justify the label text.\nAlignment\nSelect Centre from the drop-down list to align the center of the text with the center of the frame.\nSelect Top from the drop-down list to align the text with the top of the frame.\nSelect Bottom from the drop-down list to align the text with the bottom of the frame.\nSelect Base from the drop-down list to align the text with the base of the first character.\nHeight\nInput a value in the text field to define the height for the label text.\nSpacing\nInput a value in the text field to define the spacing for the label text.\nLine Spacing\nInput a value in the text field to define the line spacing for the label text.\nCE\nClick to identify the currently selected GLAB as the working element.\nText\nSelect from the drop-down list to define the representation colour for text.\nAlternatively, click Pick to display the Pick a colour window. The functionality of the Pick a colour window is explained, refer to Pens for further information.\nFont\nSelect from the drop-down list to define the font.\nIf you select True Type Font the True Type font selection window displays\n\nSelect the DB ordering option button to order the True Type fonts list by database order.\nSelect the Face name option button to order the True Type fonts list by Face name.\nSelect the Font ID option button to order the True Type fonts list by font ID.\nSelect the Description option button to order the True Type fonts list by description.\nSelect the Bold check box to apply bold formatting to the font style.\nSelect the Italic check box to apply italic formatting to the font style.\nClick OK to confirm the selection or Cancel to discard any changes and close the True Type font selection window.\nJustification\nSelect Left from the drop-down list to left justify the label text.\nSelect Right from the drop-down list to right justify the label text.\nSelect Centre from the drop-down list to centre justify the label text.\nAlignment\nSelect Centre from the drop-down list to align the center of the text with the center of the frame.\nSelect Top from the drop-down list to align the text with the top of the frame.\nSelect Bottom from the drop-down list to align the text with the bottom of the frame.\nSelect Base from the drop-down list to align the text with the base of the first character.\nHeight\nInput a value in the text field to define the height for the label text.\nSpacing\nInput a value in the text field to define the spacing for the label text.\nLine Spacing\nInput a value in the text field to define the line spacing for the label text.\nClick Apply to define the text attributes, or Reset to revert to the settings when the Label Text Attributes window was opened. Click Cancel to discard any changes and close the Label Text Attributes window.\nCE\nClick to identify the currently selected GLAB as the working element.\nText\nSelect from the drop-down list to define the representation colour for text.\nAlternatively, click Pick to display the Pick a colour window. The functionality of the Pick a colour window is explained, refer to Pens for further information.\nFont\nSelect from the drop-down list to define the font.\nIf you select True Type Font the True Type font selection window displays\nSelect the DB ordering option button to order the True Type fonts list by database order.\nSelect the Face name option button to order the True Type fonts list by Face name.\nSelect the Font ID option button to order the True Type fonts list by font ID.\nSelect the Description option button to order the True Type fonts list by description.\nSelect the Bold check box to apply bold formatting to the font style.\nSelect the Italic check box to apply italic formatting to the font style.\nClick OK to confirm the selection or Cancel to discard any changes and close the True Type font selection window.\nJustification\nSelect Left from the drop-down list to left justify the label text.\nSelect Right from the drop-down list to right justify the label text.\nSelect Centre from the drop-down list to centre justify the label text.\nAlignment\nSelect Centre from the drop-down list to align the center of the text with the center of the frame.\nSelect Top from the drop-down list to align the text with the top of the frame.\nSelect Bottom from the drop-down list to align the text with the bottom of the frame.\nSelect Base from the drop-down list to align the text with the base of the first character.\nHeight\nInput a value in the text field to define the height for the label text.\nSpacing\nInput a value in the text field to define the spacing for the label text.\nLine Spacing\nInput a value in the text field to define the line spacing for the label text.\n\n\n\nPens\nCE\nText\nPick\nPick a colour\nPick a colour\nPens\nFont\nTrue Type Font\nTrue Type font selection\nDB ordering\nFace name\nTrue Type fonts\nFont ID\nDescription\nBold\nItalic\nOK\nCancel\nTrue Type font selection\nJustification\nLeft\nRight\nCentre\nAlignment\nCentre\nTop\nBottom\nBase\nHeight\nSpacing\nLine Spacing\nApply\nReset\nLabel Text Attributes\nCancel\nLabel Text Attributes"}
{"Headers": "Modify Label Text", "Content": "Sets the label text content.\n\nPosition\nSelect At Cursor from the drop-down list to display the Point Construction Option Form window. Refer to Define View Frame with Cursor for further information.\nYou are prompted to Input 1 point(s) on a sheet\nSelect By Cursor from the drop-down list to display the Point Construction Option Form window. Refer to Define View Frame with Cursor for further information.\nYou are prompted to Input 2 point(s) on a sheet\nAlign\nSelect Centre from the drop-down list to align the center of the text with the center of the frame.\nSelect Top from the drop-down list to align the text with the top of the frame.\nSelect Bottom from the drop-down list to align the text with the bottom of the frame.\nSelect Base from the drop-down list to align the text with the base of the first character.\nJustify\nSelect Left from the drop-down list to left justify the label text.\nSelect Right from the drop-down list to right justify the label text.\nSelect Centre from the drop-down list to center justify the label text.\nIntelligent Texts\nClick to add intelligent text to the label. The Intelligent Text window displays.\nSelect a category from the drop-down list. The list of intelligent code words associated with the category displays.\nClick to identify the intelligent text to add to the Modify Text window.\nClick Append to add the intelligent text to end of the label text in the Modify Text window.\nClick Insert to add the intelligent text to the beginning of the label text in the Modify Text window.\nClick Cancel to discard any changes and close the Intelligent Text window.\nCopy\nAllows you to copy the text attributes of an existing label.\nYou are prompted to Select element\nPosition\nSelect At Cursor from the drop-down list to display the Point Construction Option Form window. Refer to Define View Frame with Cursor for further information.\nYou are prompted to Input 1 point(s) on a sheet\nSelect By Cursor from the drop-down list to display the Point Construction Option Form window. Refer to Define View Frame with Cursor for further information.\nYou are prompted to Input 2 point(s) on a sheet\nAlign\nSelect Centre from the drop-down list to align the center of the text with the center of the frame.\nSelect Top from the drop-down list to align the text with the top of the frame.\nSelect Bottom from the drop-down list to align the text with the bottom of the frame.\nSelect Base from the drop-down list to align the text with the base of the first character.\nJustify\nSelect Left from the drop-down list to left justify the label text.\nSelect Right from the drop-down list to right justify the label text.\nSelect Centre from the drop-down list to center justify the label text.\nIntelligent Texts\nClick to add intelligent text to the label. The Intelligent Text window displays.\n\nSelect a category from the drop-down list. The list of intelligent code words associated with the category displays.\nClick to identify the intelligent text to add to the Modify Text window.\nClick Append to add the intelligent text to end of the label text in the Modify Text window.\nClick Insert to add the intelligent text to the beginning of the label text in the Modify Text window.\nClick Cancel to discard any changes and close the Intelligent Text window.\nCopy\nAllows you to copy the text attributes of an existing label.\nYou are prompted to Select element\nClick Apply to modify the label text or Cancel to discard any changes and close the Modify Text window.\nPosition\nSelect At Cursor from the drop-down list to display the Point Construction Option Form window. Refer to Define View Frame with Cursor for further information.\nYou are prompted to Input 1 point(s) on a sheet\nSelect By Cursor from the drop-down list to display the Point Construction Option Form window. Refer to Define View Frame with Cursor for further information.\nYou are prompted to Input 2 point(s) on a sheet\nAlign\nSelect Centre from the drop-down list to align the center of the text with the center of the frame.\nSelect Top from the drop-down list to align the text with the top of the frame.\nSelect Bottom from the drop-down list to align the text with the bottom of the frame.\nSelect Base from the drop-down list to align the text with the base of the first character.\nJustify\nSelect Left from the drop-down list to left justify the label text.\nSelect Right from the drop-down list to right justify the label text.\nSelect Centre from the drop-down list to center justify the label text.\nIntelligent Texts\nClick to add intelligent text to the label. The Intelligent Text window displays.\nSelect a category from the drop-down list. The list of intelligent code words associated with the category displays.\nClick to identify the intelligent text to add to the Modify Text window.\nClick Append to add the intelligent text to end of the label text in the Modify Text window.\nClick Insert to add the intelligent text to the beginning of the label text in the Modify Text window.\nClick Cancel to discard any changes and close the Intelligent Text window.\nCopy\nAllows you to copy the text attributes of an existing label.\nYou are prompted to Select element\n\n\n\nDefine View Frame with Cursor\nDefine View Frame with Cursor\nPosition\nAt Cursor\nPoint Construction Option Form\nDefine View Frame with Cursor\nInput 1 point(s) on a sheet\nBy Cursor\nPoint Construction Option Form\nDefine View Frame with Cursor\nInput 2 point(s) on a sheet\nAlign\nCentre\nTop\nBottom\nBase\nJustify\nLeft\nRight\nCentre\nIntelligent Texts\nIntelligent Text\nModify Text\nAppend\nModify Text\nInsert\nModify Text\nCancel\nIntelligent Text\nCopy\nSelect element\nApply\nCancel\nModify Text"}
{"Headers": "Label Frame Attributes", "Content": "Sets the label frame attributes.\n\nCE\nClick to identify the currently selected drawing as the working element.\nFrame\nSelect On from the drop-down list to display the frame.\nSelect Off from the drop-down list to hide the frame.\nLabel Frame Pen Colour and Style\nColour\nSelect from the drop-down list to define the representation colour for the frame.\nAlternatively, click Pick to display the Pick a colour window. The functionality of the Pick a colour window is explained, refer to Pens for further information.\nStyle\nSelect from the drop-down lists to define the label frame style.\nAlternatively, click Select to display the User-defined styles window. Refer to User-Defined Linear Styles for further information.\nWhen a style is selected, it populates the Style field and the check box is selected.\nClearance\nInput a value in the field to define the distance between the label text and the frame.\nAngle\nInput a value in the field to define the rotation angle for the frame.\nCE\nClick to identify the currently selected drawing as the working element.\nFrame\nSelect On from the drop-down list to display the frame.\nSelect Off from the drop-down list to hide the frame.\nLabel Frame Pen Colour and Style\nSelect from the drop-down list to define the representation colour for the frame.\nAlternatively, click Pick to display the Pick a colour window. The functionality of the Pick a colour window is explained, refer to Pens for further information.\nSelect from the drop-down lists to define the label frame style.\nAlternatively, click Select to display the User-defined styles window. Refer to User-Defined Linear Styles for further information.\nWhen a style is selected, it populates the Style field and the check box is selected.\nClearance\nInput a value in the field to define the distance between the label text and the frame.\nAngle\nInput a value in the field to define the rotation angle for the frame.\nClick Apply to define the label frame attributes or Reset to revert to the values applied when the Label Frame Attributes window was opened.\nClick Cancel to discard any changes and close the Label Frame Attributes window.\nCE\nClick to identify the currently selected drawing as the working element.\nFrame\nSelect On from the drop-down list to display the frame.\nSelect Off from the drop-down list to hide the frame.\nLabel Frame Pen Colour and Style\nColour\nSelect from the drop-down list to define the representation colour for the frame.\nAlternatively, click Pick to display the Pick a colour window. The functionality of the Pick a colour window is explained, refer to Pens for further information.\nStyle\nSelect from the drop-down lists to define the label frame style.\nAlternatively, click Select to display the User-defined styles window. Refer to User-Defined Linear Styles for further information.\nWhen a style is selected, it populates the Style field and the check box is selected.\nClearance\nInput a value in the field to define the distance between the label text and the frame.\nAngle\nInput a value in the field to define the rotation angle for the frame.\n\n\n\nPens\nUser-Defined Linear Styles\nCE\nFrame\nOn\nOff\nLabel Frame Pen Colour and Style\nColour\nPick\nPick a colour\nPick a colour\nPens\nStyle\nSelect\nUser-defined styles\nUser-Defined Linear Styles\nStyle\nClearance\nAngle\nApply\nReset\nLabel Frame Attributes\nCancel\nLabel Frame Attributes"}
{"Headers": "Delete Automatic Tagging Labels", "Content": "Removes the currently selected auto-tag label. The label is not deleted but hidden from the view. A message displays on the status bar indicating that the auto-tag label is hidden.\nNote:\nIt is not possible to delete an auto-tag label using the Command Window.\n\n\n\nNote\n:"}
{"Headers": "Pipe End Labels", "Content": "Creates pipe end labels that are automatically sized to the pipe diameter.\nNote:\nThe tubing must be normal to the plane of the View.\nNote:\nTubes that have no piping components cannot have a pipe end label attached to them\n\n\n\nNote\n:\nNote\n:"}
{"Headers": "Manually Identified Pipe End Labels", "Content": "Creates pipe end labels for manually identified pipe ends.\nYou are prompted to Select Element\n\nClick to identify the pipe end to be labelled in the active view. The pipe end label is added.\n\nYou are then prompted to Select Element\nThe prompt is repeated, allowing you to add multiple pipe end labels.\nInput F at the prompt and press Enter to end the command.\nNote:\nThe Identified option only becomes active after the VIEW has been made the Current Owner using the Active Properties window. Refer to Active Properties for further information.\n\n\n\nActive Properties\nNote\n:\nActive Properties\nActive Properties\nSelect Element\nSelect Element\nF\nEnter"}
{"Headers": "Automatically Identified Pipe End Labels", "Content": "Creates pipe end labels using a rule to define the pipe ends that are labelled.\n\nLayer\nThe layer name displays at the top of the window.\nLabel\nInput a name for the label in the field.\nWith\nAllows you to modify the rule that determines which elements labelling is applied to.\nInput a new rule in the field and press Enter.\nPurge Existing Labels\nSelect the check box to remove all existing pipe end labels.\nLayer\nThe layer name displays at the top of the window.\nLabel\nInput a name for the label in the field.\nWith\nAllows you to modify the rule that determines which elements labelling is applied to.\nInput a new rule in the field and press Enter.\nPurge Existing Labels\nSelect the check box to remove all existing pipe end labels.\nClick Apply to add labels to all the pipe ends in the active view or Cancel to discard any changes and close the Automatic Pipe End Labels window.\nLayer\nThe layer name displays at the top of the window.\nLabel\nInput a name for the label in the field.\nWith\nAllows you to modify the rule that determines which elements labelling is applied to.\nInput a new rule in the field and press Enter.\nPurge Existing Labels\nSelect the check box to remove all existing pipe end labels.\nNote:\nTo automatically add pipe end labels the selected view must be Limits Defined.\n\n\n\nNote\n:\nLayer\nLabel\nWith\nEnter\nPurge Existing Labels\nApply\nCancel\nAutomatic Pipe End Labels"}
{"Headers": "Label Placement", "Content": "Repositions crowded areas of labelling, minimizing label overlap and leader-line crossing. In addition to changing label positions, label placement may also be used to change label orientations, text justification, alignment, and the definition of leader line shapes.\n\nCE\nClick to identify the currently selected view as the working element.\nSelect\nAdd\nSelect the option button to add labels to the drawing.\nRemove\nSelect the option button to remove labels from the drawing.\nCE's Labels\nClick to select an individual label or all labels in the current layer or view.\nOwner's Labels\nClick to select all labels for the owner of the CE.\nList\nClick to display the Select List window. Refer to Select List for further information.\nClear\nClick to clear the current selection.\nID Label\nClick to select a series of labels.\nYou are prompted to Select Element\nID Design\nClick to select a series of labels attached to the identified design element.\nYou are prompted to Select Element\n2D Window\nAllows you to select all the labels within a cursor defined window.\nClick to display the Point Construction Option Form window.\nYou are prompted to Input 2 point(s) on a sheet\nPosition\nRemote\nAllows you to place labels around the view border.\nSelect the check box and click Definition to display the Remote Label Placement window. Refer to Remote Label Placement for further information.\nLocal\nAllows you to place labels around significant design elements.\nSelect the check box and click Definition to display the Local Label Placement window. Refer to Local Label Placement for further information.\nCE\nClick to identify the currently selected view as the working element.\nSelect\n\nSelect the option button to add labels to the drawing.\nSelect the option button to remove labels from the drawing.\nClick to select an individual label or all labels in the current layer or view.\nClick to select all labels for the owner of the CE.\nClick to display the Select List window. Refer to Select List for further information.\nClick to clear the current selection.\nClick to select a series of labels.\nYou are prompted to Select Element\nClick to select a series of labels attached to the identified design element.\nYou are prompted to Select Element\nAllows you to select all the labels within a cursor defined window.\nClick to display the Point Construction Option Form window.\nYou are prompted to Input 2 point(s) on a sheet\nPosition\n\nAllows you to place labels around the view border.\nSelect the check box and click Definition to display the Remote Label Placement window. Refer to Remote Label Placement for further information.\nAllows you to place labels around significant design elements.\nSelect the check box and click Definition to display the Local Label Placement window. Refer to Local Label Placement for further information.\nClick Apply to confirm the intelligent label placement settings or Cancel to discard any changes and close the Intelligent Label Placement window.\nCE\nClick to identify the currently selected view as the working element.\nSelect\nAdd\nSelect the option button to add labels to the drawing.\nRemove\nSelect the option button to remove labels from the drawing.\nCE's Labels\nClick to select an individual label or all labels in the current layer or view.\nOwner's Labels\nClick to select all labels for the owner of the CE.\nList\nClick to display the Select List window. Refer to Select List for further information.\nClear\nClick to clear the current selection.\nID Label\nClick to select a series of labels.\nYou are prompted to Select Element\nID Design\nClick to select a series of labels attached to the identified design element.\nYou are prompted to Select Element\n2D Window\nAllows you to select all the labels within a cursor defined window.\nClick to display the Point Construction Option Form window.\nYou are prompted to Input 2 point(s) on a sheet\nPosition\nRemote\nAllows you to place labels around the view border.\nSelect the check box and click Definition to display the Remote Label Placement window. Refer to Remote Label Placement for further information.\nLocal\nAllows you to place labels around significant design elements.\nSelect the check box and click Definition to display the Local Label Placement window. Refer to Local Label Placement for further information.\nNote:\nIf no element has been selected, you are prompted to select an element before the Intelligent Label Placement window displays.\n\n\n\nSelect List\nRemote Label Placement\nLocal Label Placement\nNote\n:\nIntelligent Label Placement\nCE\nSelect\nAdd\nRemove\nCE's Labels\nOwner's Labels\nList\nSelect List\nSelect List\nClear\nID Label\nSelect Element\nID Design\nSelect Element\n2D Window\nPoint Construction Option Form\nInput 2 point(s) on a sheet\nPosition\nRemote\nDefinition\nRemote Label Placement\nRemote Label Placement\nLocal\nDefinition\nLocal Label Placement\nLocal Label Placement\nApply\nCancel\nIntelligent Label Placement"}
{"Headers": "Label Alignment", "Content": "Horizontally or vertically aligns labels and text annotations.\nYou are prompted to Specify alignment mode <Vertical>\nInput V at the prompt and press Enter to align the labels vertically.\nYou are then prompted to Select extended mode <Standard>\nInput S at the prompt and press Enter to align the labels using the standard format. The angle of each leader line is not preserved.\nYou are then prompted to Select model label\nClick to identify the label to align others to.\n\nYou are then prompted to Select labels to align\nClick to identify the labels to align and press Enter.\nThe labels are aligned to the model label.\nThroughout the label align process you can press ESC to cancel the command. Additional functionality is also available.\nVertical\nPress the down arrow key and select Vertical to align labels vertically.\nHorizontal\nPress the down arrow key and select Horizontal to align labels horizontally.\nStandard\nPress the down arrow key and select Standard to align labels with the angle of the leader lines preserved.\nExtend\nPress the down arrow key and select Extend to align labels with the angle of the leader lines preserved.\nOnly labels can be aligned in extended mode. The Connection point offset field in the Properties window must be set to Origin. Refer to Properties for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nVertical\nPress the down arrow key and select Vertical to align labels vertically.\nHorizontal\nPress the down arrow key and select Horizontal to align labels horizontally.\nStandard\nPress the down arrow key and select Standard to align labels with the angle of the leader lines preserved.\nExtend\nPress the down arrow key and select Extend to align labels with the angle of the leader lines preserved.\nOnly labels can be aligned in extended mode. The Connection point offset field in the Properties window must be set to Origin. Refer to Properties for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nThe model labels are aligned.\nVertical\nPress the down arrow key and select Vertical to align labels vertically.\nHorizontal\nPress the down arrow key and select Horizontal to align labels horizontally.\nStandard\nPress the down arrow key and select Standard to align labels with the angle of the leader lines preserved.\nExtend\nPress the down arrow key and select Extend to align labels with the angle of the leader lines preserved.\nOnly labels can be aligned in extended mode. The Connection point offset field in the Properties window must be set to Origin. Refer to Properties for further information.\nBack\nPress the down arrow key and select Back to undo the last action.\n\n\n\nProperties\nSpecify alignment mode <Vertical>\nV\nEnter\nSelect extended mode <Standard>\nS\nEnter\nSelect model label\nSelect labels to align\nEnter\nESC\nVertical\nVertical\nHorizontal\nHorizontal\nStandard\nStandard\nExtend\nExtend\nConnection point offset\nProperties\nOrigin\nProperties\nBack\nBack"}
{"Headers": "Modify Labels and Annotations", "Content": "Sets the position and orientation of labels and annotations using grip points.\nLabels and annotations can be modified using grip points in the same way as other drawing objects. Refer to Modify Objects using Grip Points for further information.\n\nLabels and annotations can also be moved, copied, rotated, scaled and deleted in the same way as other drawing objects. Refer to Move Objects, Copy Objects, Rotate Objects, Scale Objects and Delete for further information.\nProperties for labels and annotations can also be changed. Refer to Properties for further information.\nThe annotation leader line connection point can be defined. Refer to Modify Annotation Leader Line Connection for further information.\n\n\n\nModify Objects using Grip Points\nMove Objects\nCopy Objects\nRotate Objects\nScale Objects\nDelete\nProperties\nModify Annotation Leader Line Connection\nModify Objects using Grip Points\nMove Objects\nCopy Objects\nRotate Objects\nScale Objects\nDelete\nProperties\nModify Annotation Leader Line Connection"}
{"Headers": "Modify Labels and Annotations using intelligent grip points", "Content": "Updates labels and annotations that are associated with design items using intelligent grip points.\nTo modify a LDIM using intelligent grip points, click to identify an existing LDIM. The intelligent grip points display in yellow.\n\nSelect the intelligent grip point. The grip point displays in red.\nYou are prompted to Specify stretch point\n\nClick to identify the position of the new intelligent grip point. The dimension annotation is modified.\nTo associate a label with a different design item using intelligent grip points, click to identify an existing label. The intelligent grip points display in yellow.\n\nClick the intelligent grip point. The grip point displays in red.\nYou are prompted to Specify stretch point\n\nClick to identify the position of the new intelligent grip point. The label annotation is modified.\n\n\n\nSpecify stretch point\nSpecify stretch point"}
{"Headers": "Modify Annotation Leader Line Connection", "Content": "Defines the annotation leader line connection position. Refer to Properties for further information.\n\nBy Style\nPress the down arrow key and select By style to inherit the annotation leader line offset position form the visual style.\nOrigin\nPress the down arrow key and select Origin to position the annotation leader line connection to the base point on the General Label (GLAB) or Symbol Label (SLAB).\nStandard\nPress the down arrow key and select Standard to position the annotation leader line connection to the nearest standard position on the GLAB.\nPress the down arrow key and select Standard to position the annotation leader line connection to the nearest connection point on the SLAB.\nNote:\nConnection points are not displayed on the drawing canvas when the SLAB is selected.\nBy Style\nPress the down arrow key and select By style to inherit the annotation leader line offset position form the visual style.\nOrigin\nPress the down arrow key and select Origin to position the annotation leader line connection to the base point on the General Label (GLAB) or Symbol Label (SLAB).\n\nStandard\nPress the down arrow key and select Standard to position the annotation leader line connection to the nearest standard position on the GLAB.\n\nPress the down arrow key and select Standard to position the annotation leader line connection to the nearest connection point on the SLAB.\n\n\nBy Style\nPress the down arrow key and select By style to inherit the annotation leader line offset position form the visual style.\nOrigin\nPress the down arrow key and select Origin to position the annotation leader line connection to the base point on the General Label (GLAB) or Symbol Label (SLAB).\nStandard\nPress the down arrow key and select Standard to position the annotation leader line connection to the nearest standard position on the GLAB.\nPress the down arrow key and select Standard to position the annotation leader line connection to the nearest connection point on the SLAB.\nNote:\nConnection points are not displayed on the drawing canvas when the SLAB is selected.\nNote:\nConnection points are not displayed on the drawing canvas when the SLAB is selected.\n\n\n\nProperties\nProperties\nBy Style\nBy style\nOrigin\nOrigin\nStandard\nStandard\nStandard\nNote\n:"}
{"Headers": "Clean Up Annotations", "Content": "Deletes elements with null or illegal design element reference (DDNM) attributes.\nA message displays, indicating the number of DDNM attributes that have been removed.\n\nClick OK to close the message or Save Support Info to save the alert summary to a file\n\n\n\nOK"}
{"Headers": "Sort Dimensions", "Content": "Dimensions are drawn in the same order as the LDIM\u2019s member list order. If the elements get out of the correct order, the display of the dimensions becomes confused. The situation can be corrected by using Sort Dimensions at dimension or dimension point level. The example indicates the effects of the function.\n\n\n\n\nSort Dimensions"}
{"Headers": "Model Reference Check", "Content": "Checks that objects are properly associated with the model. An object is considered to be properly associated when it has an intelligent position.\nTo use the facility, select the adjacent Primitives, Labels and/or Dimensions toggle options as required to specify the types of objects in the drawing to be checked, then click Model Ref. Check.\nObjects not properly associated with the model are highlighted as invalid (red).\nItems that may require attention, for example, modified automatic dimension annotations, are highlighted as a caution (yellow).\nObjects that are 100% properly associated are highlighted as valid (green).\nOther items display as grey.\n\nClick Model Ref. Check again to turn off checking. All objects display in their normal colours.\nBy default, a notification band is displayed at the top of the drawing canvas when model reference check mode is active.\n\nNote:\nLabels with an unknown reference can display with green coloring, for example, when an associated model element has been deleted. In this case, close and reopen the sheet to display the unknown reference label with red coloring.\nNote:\nModel reference check mode cannot be used if model invalid reference check mode is active.\n\n\n\nPrimitives\nLabels\nDimensions\nModel Ref. Check\nNote\n:\nModel Ref\nNote\n:"}
{"Headers": "Model Invalid Reference Check", "Content": "Checks that objects associated with the model have a valid reference. Objects with non-intelligent positions are always considered valid.\nTo use the facility, select the adjacent Primitives, Labels and/or Dimensions toggle options as required to specify the types of objects in the drawing to be checked, then click Model Invalid Ref. Check.\nObjects with an intelligent position where the reference is unset or not valid are highlighted as invalid (red).\nObjects with an intelligent position where the reference is valid are highlighted as valid (green).\nObjects with non-intelligent positions (for example, 2D sheet or 3D world positions) are highlighted as valid (green).\n\nClick Model Invalid Ref. Check again to turn off checking. All objects display in their normal colors.\nBy default, a notification band is displayed at the top of the drawing canvas when model invalid reference check mode is active.\n\nNote:\nThe DDNM on labels with non-intelligent positions is not checked by this facility.\nNote:\nModel invalid reference check mode cannot be used if model reference check mode is active.\n\n\n\nPrimitives\nLabels\nDimensions\nModel Invalid Ref. Check\nNote\n:\nModel Invalid Ref. Check\nNote\n:"}
{"Headers": "Hidden Annotation", "Content": "Hidden Annotation is used to toggle between showing the Visible and the Invisible annotations respectively in a drawing. When Hidden Annotations is enabled, all annotations with Visibility set to No will become temporarily visible and annotations with Visibility set to Yes will be temporarily hidden. All normal functions can be used on the annotations when Hidden Annotation is enabled.\nIf a new annotation, which by default has Visibility set to Yes, is created when Hidden Annotation is enabled, the annotation will not be displayed. It will become visible once Hidden Annotation is disabled. A message informs the user about this in Messages window, under User tab.\nIt is not allowed to enable or disable Hidden Annotations when one or more annotations are selected in the drawing. They have to be deselected before changing mode. A warning message informs the user about this in Messages window, under User tab.\nBy default, a notification band is displayed at the top of the drawing canvas when hidden annotation mode is active.\n\n\n\n\nHidden Annotation\nHidden Annotations\nNo\nYes\nHidden Annotation\nYes\nHidden Annotation\nHidden Annotation\nHidden Annotations"}
{"Headers": "Fill Objects", "Content": "The fill functionality can be used to fill objects on a drawing. OUTLine elements are created which contain a filled area that is aligned to the boundary of each picked object. The OUTL element can be deleted which allows you to delete the filled area without deleting the original object.\nYou are prompted to Select Objects\nClick to identify the objects to fill and press Enter.\nClick within the boundary of each required object, the fill is added to the drawing.\nThroughout the fill process you can press ESC to cancel the command.\n\nThe new OUTL elements display in the Draw Explorer.\n\nThe fill colour and fill type of the OUTL element can be modified using the Properties window. Refer to Properties for further information.\n\nFill colour\nSelect from the drop-down list to modify the fill color.\nFill type\nSelect from the drop-down list to modify the fill type.\nFill colour\nSelect from the drop-down list to modify the fill color.\nFill type\nSelect from the drop-down list to modify the fill type.\n\nFill colour\nSelect from the drop-down list to modify the fill color.\nFill type\nSelect from the drop-down list to modify the fill type.\n\n\n\nProperties\nSelect Objects\nEnter\nESC\nProperties\nProperties\nFill colour\nFill type"}
{"Headers": "Update", "Content": "Updates elements with database or settings changes.\nIf you attempt to update a drawing that you do not have access rights to, a Confirm window displays indicating that the changes to the drawing cannot be saved.\n\nClick Yes to update the drawing or No to cancel the drawing update.\n\n\n\nConfirm\nYes\nNo"}
{"Headers": "Current Owner", "Content": "Updates the current owner for all design elements, annotations, laser elements or reference grid annotations on the current sheet.\nTo update the current owner for all design elements and laser data on the current sheet, in the Drawing group, click Design and select Current Owner from the drop-down list.\nTo update the current owner for all annotations on the current sheet, in the Drawing group, click Annotation and select Current Owner from the drop-down list.\nTo update the current owner for all design elements and annotations on the current sheet, in the Drawing group, click All and select Current Owner from the drop-down list.\nTo update the current owner for all reference grid annotations on the current sheet, in the Grid Annotations group, click Update and select Current Owner from the drop-down list. Modifications to the reference grid annotations are retained.\nTo update the current owner and regenerate all reference grid annotations on the current sheet, in the Grid Annotations group, click Regenerate and select Current Owner from the drop-down list. The reference grid annotations are regenerated to match the 3D model. Modifications to reference grid annotations are overwritten.\nTo update the current owner for all auto-labels on the current sheet, in the Autolabels group, click Update and select Current Owner from the drop-down list. Modifications to the auto-labels are retained.\nTo update the current owner and regenerate all auto-labels on the current sheet, in the Autolabels group, click Regenerate and select Current Owner from the drop-down list. The auto-labels are regenerated to match the 3D model. Modifications to auto-labels are overwritten.\nNote:\nThe changes are applied automatically if is set on the Status Bar.\nNote:\nIf the design elements are updated on a view with an unset ID list reference, a warning displays in the message log. If the WARNINGS ON command is issued using the Command Window, a warning is issued if the ID list reference is set, but points to an empty ID list.\n\n\n\nStatus Bar\nDrawing\nDesign\nCurrent Owner\nDrawing\nAnnotation\nCurrent Owner\nDrawing\nAll\nCurrent Owner\nGrid Annotations\nUpdate\nCurrent Owner\nGrid Annotations\nRegenerate\nCurrent Owner\nAutolabels\nUpdate\nCurrent Owner\nAutolabels\nRegenerate\nCurrent Owner\nNote\n:\nStatus Bar\nNote\n:"}
{"Headers": "Create and Compare Drawing Revisions", "Content": "Records of drawings, as they are at a particular time, can be saved. These records are known as revisions. Revisions can subsequently be compared with each other or with the drawing in it\u2019s current state.\nDifferences are highlighted on the current drawing, and revision clouds can optionally be added around them if required.\n\n\n"}
{"Headers": "Export to DGN", "Content": "Exports a drawing or drawings to a DGN file.\n\nExport\nClick to export the current sheet. By default, the exported file is named using the sheet name and the current revision number (if a revision is present).\nWhen Export is selected, the current export settings are saved.\nMulti Export\nAllows you to export multiple sheets. Refer to Export Multiple Sheets for further information.\nWhen Multi Export is selected, the current export settings are saved.\nSpecify the export type\nSelect Export to DGN from the drop-down list to define a DGN file as the export format.\nSpecify file type\nAllows you to define the exported file type. Click to display a drop-down list.\nSelect the required export file format from the drop-down list.\nSpecify what to export\nAllows you to define what to export. Click to display a drop-down list.\nSelect either the entire sheet or one of its views from the drop-down list.\nSpecify paper size\nAllows you to define the size of the paper. Click to display a drop-down list.\nSelect a pre-defined scale size for the exported file, for example, ISO A3 or ISO A4, or select Auto size paper to compute a custom paper size using the Paper ScaleUp field and the extents of the exported data.\nCutmarks\nSelect the check box to export the file with cutmarks.\nPaper ScaleUp\nInput a value in the field to define a scale factor for the exported file or select a scale factor from the drop-down list.\nThe Paper ScaleUp field becomes active if Auto size paper is selected when you specify the desired output size.\nPaper Frame\nSelect the check box to export the frame.\nBorder\nInput a value in the field to define the border width. 0mm indicates no border.\nAdvanced\nSelect the check box to display advanced export settings.\nDeselect the check box to suppress the display of advanced export settings. Export white graphics becomes available.\nExport white graphics\nSelect the check box to export all graphics as white, in order for them to be seen in a viewer with a black background. The default is to export all graphics as black.\nThe following options are only available when Advanced is selected:\nAnnotation Mapping\nSelect the check box to map annotation entities to equivalent AutoCAD/Microstation entities, if available. If a good equivalent entity is not available, the export reverts to the basic (exploded) version for that entity.\nBlanking\nSelect the check box to export labels and dimensions with blanking, if blanking is enabled for the DRAW element.\nSeed File\nSelect the check box to associate a seed file with the exported output.\nClick and browse to the required seed file.\nIf enabled, the specified seed file is used to configure the export settings.\nUse Grouping Rules\nSelect the check box to use grouping rules for the export. Edit Grouping rules becomes active.\nEdit grouping rules\nClick to define the grouping rules for the export. Refer to Edit Grouping Rules for further information.\nAssign levels by rule\nSelect the check box to use level rules for the export. Edit level rules becomes active.\nEdit level rules\nClick to define the level rules for the export. Refer to Edit Level Rules for further information.\nUse backing sheet level\nSelect the check box to export the backing sheet to a specified level.\nInput a value in the field to define the level for the exported backing sheet.\nDefault level\nInput a value in the field to define the default level for exported elements.\nLinked external image file\nSelect the radio button to export a DGN file with linked PNG files. Note that if a linked PNG file is moved or deleted, the image is not rendered on the DGN file.\nEmbedded OLE object\nSelect the radio button to export a DGN file with embedded objects. The exported file size is larger than the Linked external image file option.\nEmbedded indexed palette bitmap\nSelect the radio button to export a DGN file with colours modified to use the DGN colour palette. A smaller file size is exported but the quality and colour of the file may be reduced. The example displays the quality and colour differences between an embedded OLE object and an indexed palette bitmap.\nShow View and Region Frames\nSelect the check box to include the frames of all View frame owners (for example, Views and Regions) in the exported output, if they are enabled in Draw.\nAuto Preview\nSelect the check box to update the preview as the export settings are changed, by default.\nPreview\nClick to update the view of what will be exported.\nLoad Settings\nClick to open a file browser to locate and load new export settings from a configuration file (.pmldat) or a legacy LIEXEC configuration macro file (.mac).\nSave Settings\nClick to save the current export settings.\nRestore Defaults\nClick to restore the default export settings.\nExport\nClick to export the current sheet. By default, the exported file is named using the sheet name and the current revision number (if a revision is present).\nWhen Export is selected, the current export settings are saved.\nMulti Export\nAllows you to export multiple sheets. Refer to Export Multiple Sheets for further information.\nWhen Multi Export is selected, the current export settings are saved.\nSpecify the export type\nSelect Export to DGN from the drop-down list to define a DGN file as the export format.\nSpecify file type\nAllows you to define the exported file type. Click to display a drop-down list.\n\nSelect the required export file format from the drop-down list.\nSpecify what to export\nAllows you to define what to export. Click to display a drop-down list.\n\nSelect either the entire sheet or one of its views from the drop-down list.\nSpecify paper size\nAllows you to define the size of the paper. Click to display a drop-down list.\n\nSelect a pre-defined scale size for the exported file, for example, ISO A3 or ISO A4, or select Auto size paper to compute a custom paper size using the Paper ScaleUp field and the extents of the exported data.\nCutmarks\nSelect the check box to export the file with cutmarks.\nPaper ScaleUp\nInput a value in the field to define a scale factor for the exported file or select a scale factor from the drop-down list.\nThe Paper ScaleUp field becomes active if Auto size paper is selected when you specify the desired output size.\nPaper Frame\nSelect the check box to export the frame.\nBorder\nInput a value in the field to define the border width. 0mm indicates no border.\nAdvanced\nSelect the check box to display advanced export settings.\nDeselect the check box to suppress the display of advanced export settings. Export white graphics becomes available.\nSelect the check box to export all graphics as white, in order for them to be seen in a viewer with a black background. The default is to export all graphics as black.\nThe following options are only available when Advanced is selected:\nSelect the check box to map annotation entities to equivalent AutoCAD/Microstation entities, if available. If a good equivalent entity is not available, the export reverts to the basic (exploded) version for that entity.\nSelect the check box to export labels and dimensions with blanking, if blanking is enabled for the DRAW element.\nSelect the check box to associate a seed file with the exported output.\nClick and browse to the required seed file.\nIf enabled, the specified seed file is used to configure the export settings.\nSelect the check box to use grouping rules for the export. Edit Grouping rules becomes active.\nClick to define the grouping rules for the export. Refer to Edit Grouping Rules for further information.\nSelect the check box to use level rules for the export. Edit level rules becomes active.\nClick to define the level rules for the export. Refer to Edit Level Rules for further information.\nSelect the check box to export the backing sheet to a specified level.\nInput a value in the field to define the level for the exported backing sheet.\nInput a value in the field to define the default level for exported elements.\nSelect the radio button to export a DGN file with linked PNG files. Note that if a linked PNG file is moved or deleted, the image is not rendered on the DGN file.\nSelect the radio button to export a DGN file with embedded objects. The exported file size is larger than the Linked external image file option.\nSelect the radio button to export a DGN file with colours modified to use the DGN colour palette. A smaller file size is exported but the quality and colour of the file may be reduced. The example displays the quality and colour differences between an embedded OLE object and an indexed palette bitmap.\n\nShow View and Region Frames\nSelect the check box to include the frames of all View frame owners (for example, Views and Regions) in the exported output, if they are enabled in Draw.\nAuto Preview\nSelect the check box to update the preview as the export settings are changed, by default.\nPreview\nClick to update the view of what will be exported.\nLoad Settings\nClick to open a file browser to locate and load new export settings from a configuration file (.pmldat) or a legacy LIEXEC configuration macro file (.mac).\nSave Settings\nClick to save the current export settings.\nRestore Defaults\nClick to restore the default export settings.\nTo export blanking information with the drawing, select the Advanced check box. Refer to Label and Dimension Blanking for further information.\nExport\nClick to export the current sheet. By default, the exported file is named using the sheet name and the current revision number (if a revision is present).\nWhen Export is selected, the current export settings are saved.\nMulti Export\nAllows you to export multiple sheets. Refer to Export Multiple Sheets for further information.\nWhen Multi Export is selected, the current export settings are saved.\nSpecify the export type\nSelect Export to DGN from the drop-down list to define a DGN file as the export format.\nSpecify file type\nAllows you to define the exported file type. Click to display a drop-down list.\nSelect the required export file format from the drop-down list.\nSpecify what to export\nAllows you to define what to export. Click to display a drop-down list.\nSelect either the entire sheet or one of its views from the drop-down list.\nSpecify paper size\nAllows you to define the size of the paper. Click to display a drop-down list.\nSelect a pre-defined scale size for the exported file, for example, ISO A3 or ISO A4, or select Auto size paper to compute a custom paper size using the Paper ScaleUp field and the extents of the exported data.\nCutmarks\nSelect the check box to export the file with cutmarks.\nPaper ScaleUp\nInput a value in the field to define a scale factor for the exported file or select a scale factor from the drop-down list.\nThe Paper ScaleUp field becomes active if Auto size paper is selected when you specify the desired output size.\nPaper Frame\nSelect the check box to export the frame.\nBorder\nInput a value in the field to define the border width. 0mm indicates no border.\nAdvanced\nSelect the check box to display advanced export settings.\nDeselect the check box to suppress the display of advanced export settings. Export white graphics becomes available.\nExport white graphics\nSelect the check box to export all graphics as white, in order for them to be seen in a viewer with a black background. The default is to export all graphics as black.\nThe following options are only available when Advanced is selected:\nAnnotation Mapping\nSelect the check box to map annotation entities to equivalent AutoCAD/Microstation entities, if available. If a good equivalent entity is not available, the export reverts to the basic (exploded) version for that entity.\nBlanking\nSelect the check box to export labels and dimensions with blanking, if blanking is enabled for the DRAW element.\nSeed File\nSelect the check box to associate a seed file with the exported output.\nClick and browse to the required seed file.\nIf enabled, the specified seed file is used to configure the export settings.\nUse Grouping Rules\nSelect the check box to use grouping rules for the export. Edit Grouping rules becomes active.\nEdit grouping rules\nClick to define the grouping rules for the export. Refer to Edit Grouping Rules for further information.\nAssign levels by rule\nSelect the check box to use level rules for the export. Edit level rules becomes active.\nEdit level rules\nClick to define the level rules for the export. Refer to Edit Level Rules for further information.\nUse backing sheet level\nSelect the check box to export the backing sheet to a specified level.\nInput a value in the field to define the level for the exported backing sheet.\nDefault level\nInput a value in the field to define the default level for exported elements.\nLinked external image file\nSelect the radio button to export a DGN file with linked PNG files. Note that if a linked PNG file is moved or deleted, the image is not rendered on the DGN file.\nEmbedded OLE object\nSelect the radio button to export a DGN file with embedded objects. The exported file size is larger than the Linked external image file option.\nEmbedded indexed palette bitmap\nSelect the radio button to export a DGN file with colours modified to use the DGN colour palette. A smaller file size is exported but the quality and colour of the file may be reduced. The example displays the quality and colour differences between an embedded OLE object and an indexed palette bitmap.\nShow View and Region Frames\nSelect the check box to include the frames of all View frame owners (for example, Views and Regions) in the exported output, if they are enabled in Draw.\nAuto Preview\nSelect the check box to update the preview as the export settings are changed, by default.\nPreview\nClick to update the view of what will be exported.\nLoad Settings\nClick to open a file browser to locate and load new export settings from a configuration file (.pmldat) or a legacy LIEXEC configuration macro file (.mac).\nSave Settings\nClick to save the current export settings.\nRestore Defaults\nClick to restore the default export settings.\n\n\n\nExport Multiple Sheets\nEdit Grouping Rules\nEdit Level Rules\nLabel and Dimension Blanking\nExport\nExport\nMulti Export\nExport Multiple Sheets\nMulti Export\nSpecify the export type\nExport to DGN\nSpecify file type\nSpecify what to export\nSpecify paper size\nISO A3\nISO A4\nAuto size paper\nPaper ScaleUp\nCutmarks\nPaper ScaleUp\nPaper ScaleUp\nAuto size paper\nPaper Frame\nBorder\nAdvanced\nExport white graphics\nExport white graphics\nAdvanced\nAnnotation Mapping\nBlanking\nSeed File\nUse Grouping Rules\nEdit Grouping rules\nEdit grouping rules\nEdit Grouping Rules\nAssign levels by rule\nEdit level rules\nEdit level rules\nEdit Level Rules\nUse backing sheet level\nDefault level\nLinked external image file\nEmbedded OLE object\nLinked external image file\nEmbedded indexed palette bitmap\nShow View and Region Frames\nAuto Preview\nPreview\nLoad Settings\nSave Settings\nRestore Defaults\nAdvanced\nLabel and Dimension Blanking"}
{"Headers": "Export to DWG or DXF", "Content": "Exports a drawing or drawings to a DWG or DXF file.\n\nExport\nClick to export the current sheet. By default, the exported file is named using the sheet name and the current revision number (if a revision is present).\nWhen Export is selected, the current export settings are saved.\nMulti Export\nAllows you to export multiple sheets. Refer to Export Multiple Sheets for further information.\nWhen Multi Export is selected, the current export settings are saved.\nSpecify export type\nSelect Export to DXF/DWG from the drop-down list to define a DXF or a DWG file as the export format.\nSpecify file type\nAllows you to define the exported file type. Click to display a drop-down list.\nSelect the required export file format from the drop-down list.\nSpecify what to export\nAllows you to define what to export. Click to display a drop-down list.\nSelect either the entire sheet or one of its views from the drop-down list.\nSpecify paper size\nAllows you to define the size of the paper. Click to display a drop-down list.\nSelect a pre-defined size for the exported file, for example, ISO A3 or ISO A4, or select Auto size paper to define a custom size for the exported output using the Paper ScaleUp field and the extents of the exported data.\nCutmarks\nSelect the check box to export the file with cut marks.\nPaper ScaleUp\nInput a value in the field to define a scale factor for the exported file or select a scale factor from the drop-down list.\nThe Paper ScaleUp field becomes active if Auto size paper is selected when you specify the desired output size.\nPaper Frame\nSelect the check box to export the frame.\nBorder\nInput a value in the field to define the border width. 0mm indicates no border.\nAdvanced\nSelect the check box to display advanced export settings.\nDeselect the check box to suppress the display of advanced export settings. Export white graphics becomes available.\nExport to Paper Space\nSelect the check box to export the entire drawing to a paper space block. Additionally, all views containing design elements are exported to a model space block.\nExport white graphics\nSelect the check box to export all graphics as white, in order for them to be seen in a viewer with a black background. The default is to export all graphics as black.\nThe following options are only available when Advanced is selected:\nAnnotation Mapping\nSelect the check box to map annotation entities to equivalent AutoCAD/Microstation entities, if available. If a good equivalent entity is not available, the export reverts to the basic (exploded) version for that entity.\nBlanking\nSelect the check box to export labels and dimensions with blanking, if blanking is enabled for the DRAW element.\nHeader File\nSelect the check box to associate a header file with the exported output.\nClick and browse to the required header file.\nBacking sheets\nSelect the check box to form backing sheets into blocks.\nFills\nSelect the check box to form fills into blocks.\nOverlays\nSelect the check box to form overlays into blocks.\nNested Blocks\nSelect the check box to create nested blocks.\nAttributes\nSelect the check box to create attributes in exported blocks for text, labels and backing sheets. The ETEXT attribute value of TEXP or TXTM elements is exported as the attribute name. The text attribute value of the TEXP or TXTM is exported as the attribute value, for example the BTEXT attribute of a TEXP.\nUse Blocking Rules\nSelect the check box to use blocking rules for the export. Edit blocking rules becomes active.\nEdit blocking rules\nClick to define the blocking rules for the export. Refer to Edit Blocking Rules for further information.\nExport\nClick to export the current sheet. By default, the exported file is named using the sheet name and the current revision number (if a revision is present).\nWhen Export is selected, the current export settings are saved.\nMulti Export\nAllows you to export multiple sheets. Refer to Export Multiple Sheets for further information.\nWhen Multi Export is selected, the current export settings are saved.\nSpecify export type\nSelect Export to DXF/DWG from the drop-down list to define a DXF or a DWG file as the export format.\nSpecify file type\nAllows you to define the exported file type. Click to display a drop-down list.\n\nSelect the required export file format from the drop-down list.\nSpecify what to export\nAllows you to define what to export. Click to display a drop-down list.\n\nSelect either the entire sheet or one of its views from the drop-down list.\nSpecify paper size\nAllows you to define the size of the paper. Click to display a drop-down list.\n\nSelect a pre-defined size for the exported file, for example, ISO A3 or ISO A4, or select Auto size paper to define a custom size for the exported output using the Paper ScaleUp field and the extents of the exported data.\nCutmarks\nSelect the check box to export the file with cut marks.\nPaper ScaleUp\nInput a value in the field to define a scale factor for the exported file or select a scale factor from the drop-down list.\nThe Paper ScaleUp field becomes active if Auto size paper is selected when you specify the desired output size.\nPaper Frame\nSelect the check box to export the frame.\nBorder\nInput a value in the field to define the border width. 0mm indicates no border.\nAdvanced\nSelect the check box to display advanced export settings.\nDeselect the check box to suppress the display of advanced export settings. Export white graphics becomes available.\nExport to Paper Space\nSelect the check box to export the entire drawing to a paper space block. Additionally, all views containing design elements are exported to a model space block.\nExport white graphics\nSelect the check box to export all graphics as white, in order for them to be seen in a viewer with a black background. The default is to export all graphics as black.\nThe following options are only available when Advanced is selected:\nSelect the check box to map annotation entities to equivalent AutoCAD/Microstation entities, if available. If a good equivalent entity is not available, the export reverts to the basic (exploded) version for that entity.\nSelect the check box to export labels and dimensions with blanking, if blanking is enabled for the DRAW element.\nSelect the check box to associate a header file with the exported output.\nClick and browse to the required header file.\nSelect the check box to form backing sheets into blocks.\nSelect the check box to form fills into blocks.\nSelect the check box to form overlays into blocks.\nSelect the check box to create nested blocks.\nSelect the check box to create attributes in exported blocks for text, labels and backing sheets. The ETEXT attribute value of TEXP or TXTM elements is exported as the attribute name. The text attribute value of the TEXP or TXTM is exported as the attribute value, for example the BTEXT attribute of a TEXP.\nSelect the check box to use blocking rules for the export. Edit blocking rules becomes active.\nClick to define the blocking rules for the export. Refer to Edit Blocking Rules for further information.\nSelect the check box to use layer rules for the export. Edit layer rules becomes active.\nClick to modify layers for the export. Refer to Edit Layer Definitions for further information.\nSelect the check box to export colours 'ByLayer' when a given (design) element matches a layer rule.\nClick to define the layer rules for the export. Refer to Edit Layer Rules for further information.\nSelect the check box to export line styles and line weights 'ByLayer' when a given (design) element matches a layer rule.\nSelect the check box to create a unique layer for each SITE and place all design information from that site onto the layer.\nSelect the check box to create a unique layer for each ZONE and place all design information from that zone onto the layer.\nSelect the check box to add a unique numeric view prefix value to the beginning of each AutoCAD Layer name created from Draw views.\nThe functionality is only available if the Use layering by site or Use layering by zone check box is selected.\nSelect the radio button to export a DWG or DXF file with linked PNG files. Note that if a linked PNG file is moved or deleted, the image is not rendered on the DWG or DXF file.\nSelect the radio button to export a DWG or DXF file with embedded objects. The exported file size is larger than the Linked external image file option.\nShow View and Region Frames\nSelect the check box to include the frames of all View frame owners (for example, Views and Regions) in the exported output, if they are enabled in Draw.\nAuto Preview\nSelect the check box to update the preview as the export settings are changed, by default.\nPreview\nClick to update the export preview.\nLoad Settings\nClick to open the file browser and load settings from a file.\nSave Settings\nClick to save the current export settings.\nRestore Defaults\nClick to restore the default export settings.\nTo export blanking information with the drawing, select the Advanced check box. Refer to Label and Dimension Blanking for further information.\nExport\nClick to export the current sheet. By default, the exported file is named using the sheet name and the current revision number (if a revision is present).\nWhen Export is selected, the current export settings are saved.\nMulti Export\nAllows you to export multiple sheets. Refer to Export Multiple Sheets for further information.\nWhen Multi Export is selected, the current export settings are saved.\nSpecify export type\nSelect Export to DXF/DWG from the drop-down list to define a DXF or a DWG file as the export format.\nSpecify file type\nAllows you to define the exported file type. Click to display a drop-down list.\nSelect the required export file format from the drop-down list.\nSpecify what to export\nAllows you to define what to export. Click to display a drop-down list.\nSelect either the entire sheet or one of its views from the drop-down list.\nSpecify paper size\nAllows you to define the size of the paper. Click to display a drop-down list.\nSelect a pre-defined size for the exported file, for example, ISO A3 or ISO A4, or select Auto size paper to define a custom size for the exported output using the Paper ScaleUp field and the extents of the exported data.\nCutmarks\nSelect the check box to export the file with cut marks.\nPaper ScaleUp\nInput a value in the field to define a scale factor for the exported file or select a scale factor from the drop-down list.\nThe Paper ScaleUp field becomes active if Auto size paper is selected when you specify the desired output size.\nPaper Frame\nSelect the check box to export the frame.\nBorder\nInput a value in the field to define the border width. 0mm indicates no border.\nAdvanced\nSelect the check box to display advanced export settings.\nDeselect the check box to suppress the display of advanced export settings. Export white graphics becomes available.\nExport to Paper Space\nSelect the check box to export the entire drawing to a paper space block. Additionally, all views containing design elements are exported to a model space block.\nExport white graphics\nSelect the check box to export all graphics as white, in order for them to be seen in a viewer with a black background. The default is to export all graphics as black.\nThe following options are only available when Advanced is selected:\nAnnotation Mapping\nSelect the check box to map annotation entities to equivalent AutoCAD/Microstation entities, if available. If a good equivalent entity is not available, the export reverts to the basic (exploded) version for that entity.\nBlanking\nSelect the check box to export labels and dimensions with blanking, if blanking is enabled for the DRAW element.\nHeader File\nSelect the check box to associate a header file with the exported output.\nClick and browse to the required header file.\nBacking sheets\nSelect the check box to form backing sheets into blocks.\nFills\nSelect the check box to form fills into blocks.\nOverlays\nSelect the check box to form overlays into blocks.\nNested Blocks\nSelect the check box to create nested blocks.\nAttributes\nSelect the check box to create attributes in exported blocks for text, labels and backing sheets. The ETEXT attribute value of TEXP or TXTM elements is exported as the attribute name. The text attribute value of the TEXP or TXTM is exported as the attribute value, for example the BTEXT attribute of a TEXP.\nUse Blocking Rules\nSelect the check box to use blocking rules for the export. Edit blocking rules becomes active.\nEdit blocking rules\nClick to define the blocking rules for the export. Refer to Edit Blocking Rules for further information.\nUse layer rules\nSelect the check box to use layer rules for the export. Edit layer rules becomes active.\nNote:\nThese override Model Visual Layers for any elements they apply to.\nEdit layer definitions\nClick to modify layers for the export. Refer to Edit Layer Definitions for further information.\nColours \u2018ByLayer\u2019 in export\nSelect the check box to export colours 'ByLayer' when a given (design) element matches a layer rule.\nNote:\nThis setting does not affect Model Visual Layers which are always 'ByLayer'.\nEdit layer rules\nClick to define the layer rules for the export. Refer to Edit Layer Rules for further information.\nLines \u2018ByLayer\u2019 in export\nSelect the check box to export line styles and line weights 'ByLayer' when a given (design) element matches a layer rule.\nNote:\nThis setting does not affect Model Visual Layers which are always 'ByLayer'.\nUse layering by site\nSelect the check box to create a unique layer for each SITE and place all design information from that site onto the layer.\nUse layering by zone\nSelect the check box to create a unique layer for each ZONE and place all design information from that zone onto the layer.\nUse view prefixing\nSelect the check box to add a unique numeric view prefix value to the beginning of each AutoCAD Layer name created from Draw views.\nThe functionality is only available if the Use layering by site or Use layering by zone check box is selected.\nLinked external image file\nSelect the radio button to export a DWG or DXF file with linked PNG files. Note that if a linked PNG file is moved or deleted, the image is not rendered on the DWG or DXF file.\nEmbedded OLE object\nSelect the radio button to export a DWG or DXF file with embedded objects. The exported file size is larger than the Linked external image file option.\nShow View and Region Frames\nSelect the check box to include the frames of all View frame owners (for example, Views and Regions) in the exported output, if they are enabled in Draw.\nAuto Preview\nSelect the check box to update the preview as the export settings are changed, by default.\nPreview\nClick to update the export preview.\nLoad Settings\nClick to open the file browser and load settings from a file.\nSave Settings\nClick to save the current export settings.\nRestore Defaults\nClick to restore the default export settings.\nNote:\nBy default, backing sheets are exported to a separate layer. In AutoCAD, the backing sheet is assigned to the layer named backlayer.\nNote:\nIf Model Visual Layers are in use they are exported and the model geometry that references them is exported with Colours and Lines 'ByLayer'. However these are overridden by any export layer rules defined below. Refer to Create and Modify Visual Layers for further information.\nNote:\nThese override Model Visual Layers for any elements they apply to.\nNote:\nThis setting does not affect Model Visual Layers which are always 'ByLayer'.\nNote:\nThis setting does not affect Model Visual Layers which are always 'ByLayer'.\n\n\n\nExport Multiple Sheets\nEdit Blocking Rules\nCreate and Modify Visual Layers\nEdit Layer Definitions\nEdit Layer Rules\nLabel and Dimension Blanking\nNote:\nExport\nExport\nMulti Export\nExport Multiple Sheets\nMulti Export\nSpecify export type\nExport to DXF/DWG\nSpecify file type\nSpecify what to export\nSpecify paper size\nISO A3\nISO A4\nAuto size paper\nPaper ScaleUp\nCutmarks\nPaper ScaleUp\nPaper ScaleUp\nPaper Frame\nBorder\nAdvanced\nExport white graphics\nExport to Paper Space\nExport white graphics\nAdvanced\nAnnotation Mapping\nBlanking\nHeader File\nBacking sheets\nFills\nOverlays\nNested Blocks\nAttributes\nUse Blocking Rules\nEdit blocking rules\nEdit blocking rules\nEdit Blocking Rules\nNote\n:\nCreate and Modify Visual Layers\nUse layer rules\nEdit layer rules\nNote\n:\nEdit layer definitions\nEdit Layer Definitions\nColours \u2018ByLayer\u2019 in export\nNote\n:\nEdit layer rules\nEdit Layer Rules\nLines \u2018ByLayer\u2019 in export\nNote\n:\nUse layering by site\nUse layering by zone\nUse view prefixing\nUse layering by site\nUse layering by zone\nLinked external image file\nEmbedded OLE object\nLinked external image file\nShow View and Region Frames\nAuto Preview\nPreview\nLoad Settings\nSave Settings\nRestore Defaults\nAdvanced\nLabel and Dimension Blanking"}
{"Headers": "Export to PDF", "Content": "Exports a drawing or drawings to a PDF file.\n\nExport\nClick to export the current sheet. By default, the exported file is named using the sheet name and the current revision number (if a revision is present).\nWhen Export is selected, the current export settings are saved.\nMulti Export\nSelect Export to multiple files from the drop-down list to export multiple sheets to individual files. By default, each exported file is named using the sheet name and the current revision number (if a revision is present).\nSelect Export to single file from the drop-down list to export multiple sheets to a single file. By default, the export file is auto named.\nSelect Export each DRWG to separate file from the drop-down list to export multiple drawings to individual files. All selected sheets in a drawing are exported to a single file. By default, the export file is named using the drawing name.\nRefer to Export Multiple Sheets for further information.\nSpecify the export type\nSelect Export to PDF from the drop-down list to define a PDF file as the export format.\nSpecify PDF file version\nAllows you to define the exported PDF file version. Click to display a drop-down list.\nSelect the required export file version from the drop-down list.\nSpecify plot styles\nAllows you to define the colour, fill and line style settings for the export. Click to display a drop-down list.\nSelect Default from the drop-down list, the colour, fill and line style settings are not changed.\nSelect Monochrome from the drop-down list to export all colours as black and white.\nSelect Greyscale from the drop-down list to export all colours as greyscale.\nAs well as the default plot styles provided with the product, additional plot styles can be created. Refer to Plot Style for further information.\nSpecify the object type to be exported\nAllows you to define the export area. Click to display a drop-down list.\nSelect Sheet from the drop-down list to export the currently selected sheet.\nSelect Display from the drop-down list to export the current display area of a sheet.\nSelect Extents from the drop-down list to export the extents of a sheet.\nSelect Window from the drop-down list to export a display area defined by you. Click Specify window to define the display area to be exported.\nSpecify window\nClick to define the area to be exported. The application displays the current sheet.\nYou are prompted to Specify first corner\nClick to identify the first corner of the export area.\nYou are then prompted to Specify opposite corner\nClick to identify the opposite corner of the export area.\nSpecify scale\nAllows you to define the exported drawing scale. Click to display a drop-down list.\nYou can select a preset scale from the drop-down list.\nAlternatively, input scale nominator and denominator values in the adjacent fields\nNote:\nIf a scale of 1:1 is selected from the drop-down list and the Fit to Paper check box is not selected, the exported sheet size for each sheet is identical to the original sheet size when a Multi Export is performed.\nFit to paper\nSelect the check box to scale the exported output to the selected page size, by default.\nSpecify paper orientation\nAllows you to define the exported page orientation. Click to display a drop-down list.\nSelect Landscape Orientation to export the sheet as Landscape.\nSelect Landscape Upside Down Orientation to export the sheet as Landscape Upside Down.\nSelect Portrait Orientation to export the sheet as Portrait.\nSelect Landscape Upside Down Orientation to export the sheet as Landscape Upside Down.\nSpecify paper size\nAllows you to define the exported page size. Click to display a drop-down list, you can select an available page size.\nCentre to Paper\nSelect the check box to centre the exported output on the paper.\nAlternatively, you can de-select the check box and input coordinates in the X and Y fields to define the centre point of the exported area.\nEmbed Font Data\nSelect the check box to include font data in the exported file. This option can greatly increase the size of the exported file. Optimize Fonts becomes available.\nIf the check box is not selected, font data is not embedded in output file. In some cases, the appearance of the exported file may be affected.\nOptimize Fonts\nSelect the check box to remove unused symbols from the font data of the exported file. This option can greatly decrease the size of the exported file, future editing options will be limited.\nBlanking\nSelect the check box to export labels and dimensions with blanking, if blanking is enabled for the Draw element.\nShow View and Region Frames\nSelect the check box to include the frames of all View frame owners (for example, Views and Regions) in the exported output, if they are enabled in Draw.\nAuto Preview\nSelect the check box to update the export preview as the export settings are changed, by default.\nScale Line Weight\nSelect the check box to scale line weights on the exported output.\nPreview\nClick to update the export preview.\nExport\nClick to export the current sheet. By default, the exported file is named using the sheet name and the current revision number (if a revision is present).\nWhen Export is selected, the current export settings are saved.\nMulti Export\nSelect Export to multiple files from the drop-down list to export multiple sheets to individual files. By default, each exported file is named using the sheet name and the current revision number (if a revision is present).\nSelect Export to single file from the drop-down list to export multiple sheets to a single file. By default, the export file is auto named.\nSelect Export each DRWG to separate file from the drop-down list to export multiple drawings to individual files. All selected sheets in a drawing are exported to a single file. By default, the export file is named using the drawing name.\nRefer to Export Multiple Sheets for further information.\nSpecify the export type\nSelect Export to PDF from the drop-down list to define a PDF file as the export format.\nSpecify PDF file version\nAllows you to define the exported PDF file version. Click to display a drop-down list.\n\nSelect the required export file version from the drop-down list.\nSpecify plot styles\nAllows you to define the colour, fill and line style settings for the export. Click to display a drop-down list.\n\nSelect Default from the drop-down list, the colour, fill and line style settings are not changed.\nSelect Monochrome from the drop-down list to export all colours as black and white.\nSelect Greyscale from the drop-down list to export all colours as greyscale.\nAs well as the default plot styles provided with the product, additional plot styles can be created. Refer to Plot Style for further information.\nSpecify the object type to be exported\nAllows you to define the export area. Click to display a drop-down list.\n\nSelect Sheet from the drop-down list to export the currently selected sheet.\nSelect Display from the drop-down list to export the current display area of a sheet.\nSelect Extents from the drop-down list to export the extents of a sheet.\nSelect Window from the drop-down list to export a display area defined by you. Click Specify window to define the display area to be exported.\nSpecify window\nClick to define the area to be exported. The application displays the current sheet.\nYou are prompted to Specify first corner\nClick to identify the first corner of the export area.\nYou are then prompted to Specify opposite corner\nClick to identify the opposite corner of the export area.\nSpecify scale\nAllows you to define the exported drawing scale. Click to display a drop-down list.\n\nYou can select a preset scale from the drop-down list.\nAlternatively, input scale nominator and denominator values in the adjacent fields\nFit to paper\nSelect the check box to scale the exported output to the selected page size, by default.\nSpecify paper orientation\nAllows you to define the exported page orientation. Click to display a drop-down list.\n\nSelect Landscape Orientation to export the sheet as Landscape.\nSelect Landscape Upside Down Orientation to export the sheet as Landscape Upside Down.\nSelect Portrait Orientation to export the sheet as Portrait.\nSelect Landscape Upside Down Orientation to export the sheet as Landscape Upside Down.\nSpecify paper size\nAllows you to define the exported page size. Click to display a drop-down list, you can select an available page size.\n\nCentre to Paper\nSelect the check box to centre the exported output on the paper.\nAlternatively, you can de-select the check box and input coordinates in the X and Y fields to define the centre point of the exported area.\nEmbed Font Data\nSelect the check box to include font data in the exported file. This option can greatly increase the size of the exported file. Optimize Fonts becomes available.\nIf the check box is not selected, font data is not embedded in output file. In some cases, the appearance of the exported file may be affected.\nOptimize Fonts\nSelect the check box to remove unused symbols from the font data of the exported file. This option can greatly decrease the size of the exported file, future editing options will be limited.\nBlanking\nSelect the check box to export labels and dimensions with blanking, if blanking is enabled for the Draw element.\nShow View and Region Frames\nSelect the check box to include the frames of all View frame owners (for example, Views and Regions) in the exported output, if they are enabled in Draw.\nAuto Preview\nSelect the check box to update the export preview as the export settings are changed, by default.\nScale Line Weight\nSelect the check box to scale line weights on the exported output.\nPreview\nClick to update the export preview.\n\nExport\nClick to export the current sheet. By default, the exported file is named using the sheet name and the current revision number (if a revision is present).\nWhen Export is selected, the current export settings are saved.\nMulti Export\nSelect Export to multiple files from the drop-down list to export multiple sheets to individual files. By default, each exported file is named using the sheet name and the current revision number (if a revision is present).\nSelect Export to single file from the drop-down list to export multiple sheets to a single file. By default, the export file is auto named.\nSelect Export each DRWG to separate file from the drop-down list to export multiple drawings to individual files. All selected sheets in a drawing are exported to a single file. By default, the export file is named using the drawing name.\nRefer to Export Multiple Sheets for further information.\nSpecify the export type\nSelect Export to PDF from the drop-down list to define a PDF file as the export format.\nSpecify PDF file version\nAllows you to define the exported PDF file version. Click to display a drop-down list.\nSelect the required export file version from the drop-down list.\nSpecify plot styles\nAllows you to define the colour, fill and line style settings for the export. Click to display a drop-down list.\nSelect Default from the drop-down list, the colour, fill and line style settings are not changed.\nSelect Monochrome from the drop-down list to export all colours as black and white.\nSelect Greyscale from the drop-down list to export all colours as greyscale.\nAs well as the default plot styles provided with the product, additional plot styles can be created. Refer to Plot Style for further information.\nSpecify the object type to be exported\nAllows you to define the export area. Click to display a drop-down list.\nSelect Sheet from the drop-down list to export the currently selected sheet.\nSelect Display from the drop-down list to export the current display area of a sheet.\nSelect Extents from the drop-down list to export the extents of a sheet.\nSelect Window from the drop-down list to export a display area defined by you. Click Specify window to define the display area to be exported.\nSpecify window\nClick to define the area to be exported. The application displays the current sheet.\nYou are prompted to Specify first corner\nClick to identify the first corner of the export area.\nYou are then prompted to Specify opposite corner\nClick to identify the opposite corner of the export area.\nSpecify scale\nAllows you to define the exported drawing scale. Click to display a drop-down list.\nYou can select a preset scale from the drop-down list.\nAlternatively, input scale nominator and denominator values in the adjacent fields\nNote:\nIf a scale of 1:1 is selected from the drop-down list and the Fit to Paper check box is not selected, the exported sheet size for each sheet is identical to the original sheet size when a Multi Export is performed.\nFit to paper\nSelect the check box to scale the exported output to the selected page size, by default.\nSpecify paper orientation\nAllows you to define the exported page orientation. Click to display a drop-down list.\nSelect Landscape Orientation to export the sheet as Landscape.\nSelect Landscape Upside Down Orientation to export the sheet as Landscape Upside Down.\nSelect Portrait Orientation to export the sheet as Portrait.\nSelect Landscape Upside Down Orientation to export the sheet as Landscape Upside Down.\nSpecify paper size\nAllows you to define the exported page size. Click to display a drop-down list, you can select an available page size.\nCentre to Paper\nSelect the check box to centre the exported output on the paper.\nAlternatively, you can de-select the check box and input coordinates in the X and Y fields to define the centre point of the exported area.\nEmbed Font Data\nSelect the check box to include font data in the exported file. This option can greatly increase the size of the exported file. Optimize Fonts becomes available.\nIf the check box is not selected, font data is not embedded in output file. In some cases, the appearance of the exported file may be affected.\nOptimize Fonts\nSelect the check box to remove unused symbols from the font data of the exported file. This option can greatly decrease the size of the exported file, future editing options will be limited.\nBlanking\nSelect the check box to export labels and dimensions with blanking, if blanking is enabled for the Draw element.\nShow View and Region Frames\nSelect the check box to include the frames of all View frame owners (for example, Views and Regions) in the exported output, if they are enabled in Draw.\nAuto Preview\nSelect the check box to update the export preview as the export settings are changed, by default.\nScale Line Weight\nSelect the check box to scale line weights on the exported output.\nPreview\nClick to update the export preview.\nNote:\nIf a scale of 1:1 is selected from the drop-down list and the Fit to Paper check box is not selected, the exported sheet size for each sheet is identical to the original sheet size when a Multi Export is performed.\n\n\n\nExport Multiple Sheets\nExport\nExport\nMulti Export\nExport to multiple files\nExport to single file\nExport each DRWG to separate file\nExport Multiple Sheets\nSpecify the export type\nExport to PDF\nSpecify PDF file version\nSpecify plot styles\nDefault\nMonochrome\nGreyscale\nPlot Style\nSpecify the object type to be exported\nSheet\nDisplay\nExtents\nWindow\nSpecify window\nSpecify window\nSpecify first corner\nSpecify opposite corner\nSpecify scale\nNote\n:\n1:1\nFit to Paper\nMulti Export\nFit to paper\nSpecify paper orientation\nLandscape Orientation\nLandscape Upside Down Orientation\nPortrait Orientation\nLandscape Upside Down Orientation\nSpecify paper size\nCentre to Paper\nX\nY\nEmbed Font Data\nOptimize Fonts\nOptimize Fonts\nBlanking\nShow View and Region Frames\nAuto Preview\nScale Line Weight\nPreview"}
{"Headers": "Create HVAC Sketches", "Content": "Creates HVAC sketches automatically in Draw using HVAC spool data.\nThe sketches include dimensioned, scaled drawings of an HVAC spool with details of the spool and assembly data.\nThe layout of the sketch and associated sheets can be chosen from a database and the location of where the sketches can be stored can be defined in the system hierarchy. To customise the layout, refer to the administrator for further information.\nAfter launching Draw you must display the Model Explorer and select the required spool.\nThe HVAC Spool data, required to create a sketch, must now be selected. The HVAC Sketches window contains all the options to search for HVAC spool data. You can use any or all of the options.\n\nYou can input the name of the design element in the Design Element to search under field.\nAlternatively, select the HVAC element in the Model Explorer and click CE on the HVAC sketches window. The selected CE must be a valid element or an error message displays.\n\nAfter the Design Element to search under field has been populated, the search criteria for the HVAC Spool data can be customised to search for All or part of the spool name, Production Status and the Sketch Status. You can populate any of the three fields or all of the three fields.\n\nAll or part of the spool name\nInput either the complete spool name or part of the spool name.\nProduction Status\nYou can select from the drop-down list, one of three options.\nAny - Matches all spools, both validated and not validated.\nValid - Matches only spools valid for production.\nNot Valid - Matches only spools not valid for production\nSketch Status\nYou can select from the drop-down list, one of three options.\nAny - Matches all spools, both with and without HVAC sketches.\nCreated - Matches only spools with HVAC sketches.\nNot Created - Matches only spools without HVAC sketches.\nAll or part of the spool name\nInput either the complete spool name or part of the spool name.\nProduction Status\nYou can select from the drop-down list, one of three options.\nAny - Matches all spools, both validated and not validated.\nValid - Matches only spools valid for production.\nNot Valid - Matches only spools not valid for production\nSketch Status\nYou can select from the drop-down list, one of three options.\nAny - Matches all spools, both with and without HVAC sketches.\nCreated - Matches only spools with HVAC sketches.\nNot Created - Matches only spools without HVAC sketches.\nClick Search to display the results in the Search Results window.\n\nThe Name column displays the name of the HVAC Spool.\nThe Valid column indicates the validation status of the spool, true indicates a validated spool and false indicates a non-validated spool.\nThe Sketch column indicates the sketch status of the spool. The sketch name displays if a sketch has been created, FALSE displays if a sketch is not created. If the sketch has been created, the sketch creation date displays in the Drawn column.\nRight-click the Search Results part of the HVAC Sketches window to display a drop-down list.\nSelect All\nSelects all the spools in the Search Results list.\nClear Selection\nDeselects all the spools in the Search Results list.\nPrint Sketch\nOpens a print window which allows you to print selected spool sketches.\nNote:\nOnly valid if a spool sketch has been created.\nDelete Sketch\nDeletes all selected spool sketches.\nNote:\nOnly valid if a spool sketch has been created.\nSelect All\nSelects all the spools in the Search Results list.\nClear Selection\nDeselects all the spools in the Search Results list.\nPrint Sketch\nOpens a print window which allows you to print selected spool sketches.\nDelete Sketch\nDeletes all selected spool sketches.\nTo create the HVAC sketches, select rows on the Search Results part of the HVAC Sketches window to identify which HVAC Spools are to be created.\nThe Sketch Creation Options part of the HVAC Sketches window allows you to define the template to be used for the sketch, a storage area for the created sketch and a log filename.\n\nSketch Template\nYou must select an existing DRWG or DRTMPL element that can be used for the sketch.\nNote:\nIf the selected element is not an existing DRWG element then an error message displays.\nSelect the required DRWG element on the Draw Explorer and click CE. The name of the element displays in the field.\nCreate Sketches in Registry\nYou must select a Registry for the storage of the created HVAC sketches.\nNote:\nIf the selected element is not an existing REGI element then an error message displays.\nSelect the required REGI element on the Draw Explorer and click CE. The name of the element displays in the field.\nLog File\nYou must select a location for the storage of a log file (.txt file). The log file contains a record of the sketch creation, and is overwritten if it already exists.\nTo change the file location, click Browse and navigate to the required location to save the log file.\nSketch Template\nYou must select an existing DRWG or DRTMPL element that can be used for the sketch.\nSelect the required DRWG element on the Draw Explorer and click CE. The name of the element displays in the field.\nCreate Sketches in Registry\nYou must select a Registry for the storage of the created HVAC sketches.\nSelect the required REGI element on the Draw Explorer and click CE. The name of the element displays in the field.\nLog File\nYou must select a location for the storage of a log file (.txt file). The log file contains a record of the sketch creation, and is overwritten if it already exists.\nTo change the file location, click Browse and navigate to the required location to save the log file.\nClick Create Sketches to create sketches for the selected rows. The Search Results are refreshed to show the spool sketch that has been created and the date it was drawn.\n\nDisplay\nClick to view the spool sketch and add it to a working list of sheets for display. Only one sheet can display at a time\nBack one Sketch\nClick to move the selection up one position in the Search Results, the spool sketch display is updated with the new selection.\nForward one Sketch\nClick to move the selection down one position in the Search Results, the spool sketch display is updated with the new selection.\n\nDisplay\nClick to view the spool sketch and add it to a working list of sheets for display. Only one sheet can display at a time\n\nBack one Sketch\nClick to move the selection up one position in the Search Results, the spool sketch display is updated with the new selection.\n\nForward one Sketch\nClick to move the selection down one position in the Search Results, the spool sketch display is updated with the new selection.\n\nAll or part of the spool name\nInput either the complete spool name or part of the spool name.\nProduction Status\nYou can select from the drop-down list, one of three options.\nAny - Matches all spools, both validated and not validated.\nValid - Matches only spools valid for production.\nNot Valid - Matches only spools not valid for production\nSketch Status\nYou can select from the drop-down list, one of three options.\nAny - Matches all spools, both with and without HVAC sketches.\nCreated - Matches only spools with HVAC sketches.\nNot Created - Matches only spools without HVAC sketches.\nSelect All\nSelects all the spools in the Search Results list.\nClear Selection\nDeselects all the spools in the Search Results list.\nPrint Sketch\nOpens a print window which allows you to print selected spool sketches.\nNote:\nOnly valid if a spool sketch has been created.\nDelete Sketch\nDeletes all selected spool sketches.\nNote:\nOnly valid if a spool sketch has been created.\nSketch Template\nYou must select an existing DRWG or DRTMPL element that can be used for the sketch.\nNote:\nIf the selected element is not an existing DRWG element then an error message displays.\nSelect the required DRWG element on the Draw Explorer and click CE. The name of the element displays in the field.\nCreate Sketches in Registry\nYou must select a Registry for the storage of the created HVAC sketches.\nNote:\nIf the selected element is not an existing REGI element then an error message displays.\nSelect the required REGI element on the Draw Explorer and click CE. The name of the element displays in the field.\nLog File\nYou must select a location for the storage of a log file (.txt file). The log file contains a record of the sketch creation, and is overwritten if it already exists.\nTo change the file location, click Browse and navigate to the required location to save the log file.\nDisplay\nClick to view the spool sketch and add it to a working list of sheets for display. Only one sheet can display at a time\nBack one Sketch\nClick to move the selection up one position in the Search Results, the spool sketch display is updated with the new selection.\nForward one Sketch\nClick to move the selection down one position in the Search Results, the spool sketch display is updated with the new selection.\nNote:\nOnly valid if a spool sketch has been created.\nNote:\nOnly valid if a spool sketch has been created.\nNote:\nIf the selected element is not an existing DRWG element then an error message displays.\nNote:\nIf the selected element is not an existing REGI element then an error message displays.\n\n\n\nHVAC Sketches\nDesign Element to search under\nModel Explorer\nCE\nHVAC sketches\nCE\nDesign Element to search under\nAll or part of the spool name\nProduction Status\nSketch Status\nAll or part of the spool name\nProduction Status\nAny\nValid\nNot Valid\nSketch Status\nAny\nCreated\nNot Created\nSearch\nSearch Results\nName\nValid\nSketch\nDrawn\nSearch Results\nHVAC Sketches\nSelect All\nClear Selection\nPrint Sketch\nNote\n:\nDelete Sketch\nNote\n:\nSearch Results\nHVAC Sketches\nSketch Creation Options\nHVAC Sketches\nSketch Template\nNote\n:\nCE\nCreate Sketches in Registry\nNote\n:\nCE\nLog File\nBrowse\nCreate Sketches\n\nSearch Results\nDisplay\nOnly one sheet can display at a time\nBack one Sketch\nSearch Results\nForward one Sketch\nSearch Results"}
{"Headers": "General Automatic Drawing Production", "Content": "The General Automatic Drawing Production (ADP) functionality uses special drawing sheets, referred to as Backing Sheets, which enable schedules and lists of reference drawings to be generated and placed on the drawing sheet automatically. It also uses intelligent keyplans (in the form of overlays), which can be used to define the limits of the 3D model display on the drawings.\nADP requires set up rules to define how different types of drawing are created and annotated. A set of default rules are supplied with Draw. Changing the defaults is a system administration task. Refer to Set ADP Defaults for further information.\nADP can be used to create an annotated and dimensioned view on a drawing sheet.\n\n\n\nSet ADP Defaults\nSet ADP Defaults"}
{"Headers": "Create General ADP Drawings", "Content": "Creates a general ADP drawing.\n\nThe Create DRWG window displays a default name for the element followed by the next available number, for example, DR4. Input a different name if required.\nClick OK to apply the DRWG name or Cancel to discard any changes and close the Create DRWG window. By default, the Modify General ADP Drawing window displays which can be used to modify the default drawing attributes and provides access to facilities for creating an ADP sheet. Refer to Modify General ADP Drawings for further information.\nNote:\nThe Drawing is created under the current Registry, assuming that the Current Element is a Registry or lower.\nIf you are at a higher level, and more than one Registry is available, you are prompted to move to the required Registry.\n\n\n\nModify General ADP Drawings\nNote\n:\n\nCreate DRWG\nDR4\nOK\nCancel\nCreate\nDRWG\nModify General ADP Drawing\nModify General ADP Drawings"}
{"Headers": "Modify General ADP Drawings", "Content": "Sets the general ADP drawing backing sheet, title, date and owner.\nADP drawings are modified using the Modify General ADP Drawing window. By default, the Modify General ADP Drawing window displays when an ADP drawing is created (refer to Create General ADP Drawings for further information).\n\nThe Modify General ADP Drawing window allows you to input a title and date for the drawing, and provides access to create an ADP sheet.\nCE\nClick to identify the currently selected drawing as the working element.\nFrame\nSelect from the drop-down list to define a backing sheet for the drawing.\nTitle\nInput a drawing title in the field.\nDate\nBy default, the field is populated with the current date.\nDrn\nBy default, the field is populated with the ID of the current user.\nCreate ADP Sheet\nClick to display the Create SHEE window. Refer to Create General ADP Sheets for further information.\nCE\nClick to identify the currently selected drawing as the working element.\nFrame\nSelect from the drop-down list to define a backing sheet for the drawing.\nTitle\nInput a drawing title in the field.\nDate\nBy default, the field is populated with the current date.\nDrn\nBy default, the field is populated with the ID of the current user.\nCreate ADP Sheet\nClick to display the Create SHEE window. Refer to Create General ADP Sheets for further information.\nClick Apply to modify the drawing or Cancel to discard any changes and close the Modify General ADP Drawing window.\nCE\nClick to identify the currently selected drawing as the working element.\nFrame\nSelect from the drop-down list to define a backing sheet for the drawing.\nTitle\nInput a drawing title in the field.\nDate\nBy default, the field is populated with the current date.\nDrn\nBy default, the field is populated with the ID of the current user.\nCreate ADP Sheet\nClick to display the Create SHEE window. Refer to Create General ADP Sheets for further information.\n\n\n\nCreate General ADP Drawings\nCreate General ADP Sheets\nModify General ADP Drawing\nModify General ADP Drawing\nCreate General ADP Drawings\nModify General ADP Drawing\nCE\nFrame\nTitle\nDate\nDrn\nCreate ADP Sheet\nCreate SHEE\nCreate General ADP Sheets\nApply\nCancel\nModify General ADP Drawin"}
{"Headers": "Create General ADP Sheets", "Content": "Creates a general ADP sheet under the currently selected drawing.\n\nThe Create SHEE window displays a default name for the sheet, taken from the drawing name followed by /S and the next available number, for example, DR4/S2. Input a different name if required.\nClick OK to apply the SHEE name or Cancel to discard any changes and close the Create SHEE window. By default, the Modify General ADP Sheet window displays which can be used to modify the default sheet attributes and provides access to facilities for creating an ADP view. Refer to Modify General ADP Sheets for further information.\nNote:\nThe Sheet is created under the current drawing, assuming that the Current Element is a Drawing or lower.\nIf you are at a higher level, and more than one drawing is available, you are prompted to move to the required drawing.\n\n\n\nModify General ADP Sheets\nNote\n:\nCreate SHEE\n/S\nDR4/S2\nOK\nCancel\nCreate SHEE\nModify General ADP Sheet\nModify General ADP Sheets"}
{"Headers": "Modify General ADP Sheets", "Content": "Sets the general ADP sheet properties.\nADP sheets are modified using the Modify General ADP Sheet window. By default, the Modify General ADP Sheet window displays when an ADP sheet is created (refer to Create General ADP Sheets for further information).\n\nThe Modify General ADP Sheet window allows you to input a title and date for the sheet, and provides access to create an ADP view.\nCE\nClick to identify the currently selected sheet as the working element.\nFrame\nSelect from the drop-down list to define a frame for the sheet.\nTitle\nInput a sheet title in the field.\nKeyplan\nSelect a keyplan from the drop-down list to define the limits of the drawing. You can define the Area of the keyplan to use as the drawing limits.\nSelect unset if a keyplan is not required to define the limits of the drawing.\nArea\nSelect from the drop-down list to define the keyplan area to be used for the drawing limits. The drop-down list becomes available once a key plan is selected.\nFor example, select All from the drop-down list to use the whole key plan as the limits for the drawing.\nReference Drawings\nAllows you to define an area of the sheet to be used as a list of referenced drawings. Refer to Reference Drawings for further information.\nCreate ADP View\nClick to display the Create VIEW window. Refer to Create General ADP Views for further information.\nCE\nClick to identify the currently selected sheet as the working element.\nFrame\nSelect from the drop-down list to define a frame for the sheet.\nTitle\nInput a sheet title in the field.\nKeyplan\nSelect a keyplan from the drop-down list to define the limits of the drawing. You can define the Area of the keyplan to use as the drawing limits.\nSelect unset if a keyplan is not required to define the limits of the drawing.\nArea\nSelect from the drop-down list to define the keyplan area to be used for the drawing limits. The drop-down list becomes available once a key plan is selected.\nFor example, select All from the drop-down list to use the whole key plan as the limits for the drawing.\nReference Drawings\nAllows you to define an area of the sheet to be used as a list of referenced drawings. Refer to Reference Drawings for further information.\nCreate ADP View\nClick to display the Create VIEW window. Refer to Create General ADP Views for further information.\nClick Apply to modify the sheet, the keyplan is highlighted red on the appropriate area of the sheet.\nClick Cancel to discard any changes and close the Modify General ADP Drawing window.\n\nCE\nClick to identify the currently selected sheet as the working element.\nFrame\nSelect from the drop-down list to define a frame for the sheet.\nTitle\nInput a sheet title in the field.\nKeyplan\nSelect a keyplan from the drop-down list to define the limits of the drawing. You can define the Area of the keyplan to use as the drawing limits.\nSelect unset if a keyplan is not required to define the limits of the drawing.\nArea\nSelect from the drop-down list to define the keyplan area to be used for the drawing limits. The drop-down list becomes available once a key plan is selected.\nFor example, select All from the drop-down list to use the whole key plan as the limits for the drawing.\nReference Drawings\nAllows you to define an area of the sheet to be used as a list of referenced drawings. Refer to Reference Drawings for further information.\nCreate ADP View\nClick to display the Create VIEW window. Refer to Create General ADP Views for further information.\n\n\n\nCreate General ADP Sheets\nReference Drawings\nCreate General ADP Views\nModify General ADP Sheet\nModify General ADP Sheet\nCreate General ADP Sheets\nModify General ADP Sheet\nCE\nFrame\nTitle\nKeyplan\nArea\nunset\nArea\nAll\nReference Drawings\nReference Drawings\nCreate ADP View\nCreate VIEW\nCreate General ADP Views\nApply\nCancel\nModify General ADP Drawing"}
{"Headers": "Create General ADP Views", "Content": "Creates a general ADP view under the currently selected sheet.\n\nThe Create View window displays a default name for the view, taken from the drawing name and sheet name followed by /V and the next available number, for example, DR4/S2/V1. Input a different name if required.\nSelect the function of the view from the list of available functions. For example, select dra-genadp-equilocn from the list of functions to create a general ADP equipment location view. The view is created with reference to a corresponding file.\nClick OK to create the new view or Cancel to discard any changes and close the Create VIEW window. By default, the Modify General ADP View window displays which can be used to modify the default view attributes. Refer to Modify General ADP View for further information.\nNote:\nThe view is created under the current sheet, assuming that the Current Element is a sheet or lower.\nIf you are at a higher level, and more than one sheet is available, you are prompted to move to the required sheet.\n\n\n\nModify General ADP View\nNote\n:\nCreate View\n/V\nDR4/S2/V1\nOK\nCancel\nCreate VIEW\nModify General ADP View\nModify General ADP View"}
{"Headers": "Modify General ADP View", "Content": "Sets the general ADP view properties.\nADP views are modified using the Modify General ADP View window. By default, the Modify General ADP View window displays when an ADP view is created (refer to Create General ADP Views for further information).\n\nThe Modify General ADP View window allows you to define the drawing view based on general settings and limits imposed either by the drawlist or keyplan.\nCE\nClick to identify the currently selected view as the working element.\nFunction\nThe currently selected view function displays on the top part of the window.\nModify\nAllows you to select a view function from a list of available view functions. Refer to Modify View Function for further information.\nDefaults\nChanging the defaults is a system administration task, some user defaults can be modified. Refer to Set ADP Defaults for further information.\nGeneral Settings\nDrawlist\nSelect how the Drawlist is defined from the drop-down list. For example select Volume Defined to define the drawing using the values in the direction boxes at the bottom of the window.\nModify\nClick to display the Drawlist Management window. Refer to Define View Contents for further information.\nStyle\nSelect a view style from the drop-down list to define the display of the view.\nType\nSelect a view type from the drop-down list. You can select from:\nUniversal Hidden Line\nGlobal Hidden Line\nLocal Hidden Line\nModelled Wireline\nWireline Hidden Line\nWireline\nDirection\nSelect a direction for the frame position from the drop-down list.\nAutomatic\nClick to set the frame position automatically.\nCursor\nAllows you to define the frame position using a cursor pick in the view. Refer to Define View Frame with Cursor for further information.\nLimits\nFrom Drawlist\nClick to define the limits of the view from the Drawlist setting.\nFrom Keyplan\nClick to define the limits of the view from the selected keyplan.\nUpdate Aids\nClick to update the aids.\nMatchlines\nSelect the check box to display match lines on the drawing view.\nFrom\nInput dimensional values in the From direction fields to define the limits of the view explicitly.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down lists.\nSelect the check box adjacent to the drop-down list to define the required direction.\nTo\nInput dimensional values in the To direction fields to define the limits of the view explicitly.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down lists.\nSelect the check box adjacent to the drop-down list to define the required direction.\nScale\nYou can set the scale of the drawing in the view. The option buttons allow you to either select the scale from a drop-down list or input a scale value.\nSelect Metric from the drop-down list to scale the drawing using metric values. For example, 1/1.\nSelect Architectural from the drop-down list to scale the drawing using architectural values. For example, 1 1/2\" = 1\u2019-0\".\nSelect Engineering from the drop-down list to scale the drawing using engineering values. For example, 1\" = 10\u2019-0\".\nInput a percentage value in the field to scale the drawing using a percentage factor. By default, the decimal field is changed to represent the scale factor.\nNearest\nClick to display the complete drawing in the view. By default, Draw selects the nearest available scale factor.\nSet Scale\nClick to set the drawing scale according to the input values.\nTagging\nAllows you to apply tagging to elements in the view. Refer to Automatic Tagging for further information.\nClick to display the ADP Tagging window. Refer to ADP Tagging. for further information.\nSchedules\nAllows you to include schedules in the view. Refer to ADP Schedules for further information.\nAttributes\nAllows you to define attributes for the view. Refer to General ADP View Attributes for further information.\nUpdate\nAllows you to define the elements of the view to be updated. Refer to Update View for further information.\nCE\nClick to identify the currently selected view as the working element.\nFunction\nThe currently selected view function displays on the top part of the window.\nModify\nAllows you to select a view function from a list of available view functions. Refer to Modify View Function for further information.\nDefaults\nChanging the defaults is a system administration task, some user defaults can be modified. Refer to Set ADP Defaults for further information.\nGeneral Settings\n\nSelect how the Drawlist is defined from the drop-down list. For example select Volume Defined to define the drawing using the values in the direction boxes at the bottom of the window.\nClick to display the Drawlist Management window. Refer to Define View Contents for further information.\nSelect a view style from the drop-down list to define the display of the view.\nSelect a view type from the drop-down list. You can select from:\nSelect a direction for the frame position from the drop-down list.\nClick to set the frame position automatically.\nAllows you to define the frame position using a cursor pick in the view. Refer to Define View Frame with Cursor for further information.\nLimits\n\nClick to define the limits of the view from the Drawlist setting.\nClick to define the limits of the view from the selected keyplan.\nClick to update the aids.\nSelect the check box to display match lines on the drawing view.\nInput dimensional values in the From direction fields to define the limits of the view explicitly.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down lists.\nSelect the check box adjacent to the drop-down list to define the required direction.\nInput dimensional values in the To direction fields to define the limits of the view explicitly.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down lists.\nSelect the check box adjacent to the drop-down list to define the required direction.\nYou can set the scale of the drawing in the view. The option buttons allow you to either select the scale from a drop-down list or input a scale value.\nSelect Metric from the drop-down list to scale the drawing using metric values. For example, 1/1.\nSelect Architectural from the drop-down list to scale the drawing using architectural values. For example, 1 1/2\" = 1\u2019-0\".\nSelect Engineering from the drop-down list to scale the drawing using engineering values. For example, 1\" = 10\u2019-0\".\nInput a percentage value in the field to scale the drawing using a percentage factor. By default, the decimal field is changed to represent the scale factor.\nClick to display the complete drawing in the view. By default, Draw selects the nearest available scale factor.\nClick to set the drawing scale according to the input values.\nTagging\nAllows you to apply tagging to elements in the view. Refer to Automatic Tagging for further information.\nClick to display the ADP Tagging window. Refer to ADP Tagging. for further information.\nSchedules\nAllows you to include schedules in the view. Refer to ADP Schedules for further information.\nAttributes\nAllows you to define attributes for the view. Refer to General ADP View Attributes for further information.\nUpdate\nAllows you to define the elements of the view to be updated. Refer to Update View for further information.\nClick Apply to modify the ADP view or Cancel to discard any inputs and close the Modify General ADP View window. On completion of the creation process, the drawing view displays.\n\nCE\nClick to identify the currently selected view as the working element.\nFunction\nThe currently selected view function displays on the top part of the window.\nModify\nAllows you to select a view function from a list of available view functions. Refer to Modify View Function for further information.\nDefaults\nChanging the defaults is a system administration task, some user defaults can be modified. Refer to Set ADP Defaults for further information.\nGeneral Settings\nDrawlist\nSelect how the Drawlist is defined from the drop-down list. For example select Volume Defined to define the drawing using the values in the direction boxes at the bottom of the window.\nModify\nClick to display the Drawlist Management window. Refer to Define View Contents for further information.\nStyle\nSelect a view style from the drop-down list to define the display of the view.\nType\nSelect a view type from the drop-down list. You can select from:\nUniversal Hidden Line\nGlobal Hidden Line\nLocal Hidden Line\nModelled Wireline\nWireline Hidden Line\nWireline\nDirection\nSelect a direction for the frame position from the drop-down list.\nAutomatic\nClick to set the frame position automatically.\nCursor\nAllows you to define the frame position using a cursor pick in the view. Refer to Define View Frame with Cursor for further information.\nLimits\nFrom Drawlist\nClick to define the limits of the view from the Drawlist setting.\nFrom Keyplan\nClick to define the limits of the view from the selected keyplan.\nUpdate Aids\nClick to update the aids.\nMatchlines\nSelect the check box to display match lines on the drawing view.\nFrom\nInput dimensional values in the From direction fields to define the limits of the view explicitly.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down lists.\nSelect the check box adjacent to the drop-down list to define the required direction.\nTo\nInput dimensional values in the To direction fields to define the limits of the view explicitly.\nThe direction can be defined in East, West, North, South, Up and Down directions using the drop-down lists.\nSelect the check box adjacent to the drop-down list to define the required direction.\nScale\nYou can set the scale of the drawing in the view. The option buttons allow you to either select the scale from a drop-down list or input a scale value.\nSelect Metric from the drop-down list to scale the drawing using metric values. For example, 1/1.\nSelect Architectural from the drop-down list to scale the drawing using architectural values. For example, 1 1/2\" = 1\u2019-0\".\nSelect Engineering from the drop-down list to scale the drawing using engineering values. For example, 1\" = 10\u2019-0\".\nInput a percentage value in the field to scale the drawing using a percentage factor. By default, the decimal field is changed to represent the scale factor.\nNearest\nClick to display the complete drawing in the view. By default, Draw selects the nearest available scale factor.\nSet Scale\nClick to set the drawing scale according to the input values.\nTagging\nAllows you to apply tagging to elements in the view. Refer to Automatic Tagging for further information.\nClick to display the ADP Tagging window. Refer to ADP Tagging. for further information.\nSchedules\nAllows you to include schedules in the view. Refer to ADP Schedules for further information.\nAttributes\nAllows you to define attributes for the view. Refer to General ADP View Attributes for further information.\nUpdate\nAllows you to define the elements of the view to be updated. Refer to Update View for further information.\nUniversal Hidden Line\nGlobal Hidden Line\nLocal Hidden Line\nModelled Wireline\nWireline Hidden Line\nWireline\nUniversal Hidden Line\nUniversal Hidden Line\nGlobal Hidden Line\nGlobal Hidden Line\nLocal Hidden Line\nLocal Hidden Line\nModelled Wireline\nModelled Wireline\nWireline Hidden Line\nWireline Hidden Line\nWireline\nWireline\n\n\n\nCreate General ADP Views\nModify View Function\nSet ADP Defaults\nDefine View Contents\nDefine View Frame with Cursor\nAutomatic Tagging\nADP Tagging\nADP Schedules\nGeneral ADP View Attributes\nUpdate View\nModify General ADP Vie\nModify General ADP View\nCreate General ADP Views\nModify General ADP View\nCE\nFunction\nModify\nModify View Function\nDefaults\nSet ADP Defaults\nGeneral Settings\nDrawlist\nVolume Defined\nModify\nDrawlist Management\nDefine View Contents\nStyle\nType\nDirection\nAutomatic\nCursor\nDefine View Frame with Cursor\nLimits\nFrom Drawlist\nDrawlist\nFrom Keyplan\nUpdate Aids\nMatchlines\nFrom\nFrom\nEast\nWest\nNorth\nSouth\nUp\nDown\nTo\nTo\nEast\nWest\nNorth\nSouth\nUp\nDown\nScale\nMetric\nArchitectural\nEngineering\nNearest\nSet Scale\nTagging\nAutomatic Tagging\nADP Tagging\nADP Tagging\nSchedules\nADP Schedules\nAttributes\nGeneral ADP View Attributes\nUpdate\nUpdate View\nApply\nCancel\nModify General ADP View"}
{"Headers": "Modify View Function", "Content": "Sets the view function to be used for the ADP view.\n\nSelect the function of the view from the list of available functions. For example, select dra-genadp-equilocn from the list of functions to create a general ADP equipment location view. The view is created with reference to the corresponding file.\nClick Edit to display the ADP Defaults File Editor window. Changing the defaults is a system administration task. Refer to Set ADP Defaults for further information.\nClick OK to apply the selected function to the general ADP view or Cancel to discard any changes and close the View Function window.\n\n\n\nSet ADP Defaults\nEdit\nADP Defaults File Editor\nSet ADP Defaults\nOK\nCancel\nView Function"}
{"Headers": "Define View Frame with Cursor", "Content": "Sets the frame position for the ADP view using the cursor.\n\nThe Point Construction Option Form window allows you to position the frame using a cursor pick in the view.\n2D Cursor hit\nSelect from the drop-down list to position the frame using a cursor pick on the drawing view.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nEnd point of\nSelect from the drop-down list to position the centre of the frame using a specified end point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nCentre point of\nSelect from the drop-down list to position the centre of the frame using a specified center point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nMid point of\nSelect from the drop-down list to position the centre of the frame using a specified mid point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nMid pt between\nSelect from the drop-down list to position the centre of the frame using a specified mid point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nIntersection at\nSelect from the drop-down list to position the centre of the frame using a specified intersection.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nInter between\nSelect from the drop-down list to position the centre of the frame using a specified intersection.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nNearest to\nSelect from the drop-down list to position the centre of the frame using a specified nearest to point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\n2D Cursor hit\nSelect from the drop-down list to position the frame using a cursor pick on the drawing view.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nEnd point of\nSelect from the drop-down list to position the centre of the frame using a specified end point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nCentre point of\nSelect from the drop-down list to position the centre of the frame using a specified center point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nMid point of\nSelect from the drop-down list to position the centre of the frame using a specified mid point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nMid pt between\nSelect from the drop-down list to position the centre of the frame using a specified mid point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nIntersection at\nSelect from the drop-down list to position the centre of the frame using a specified intersection.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nInter between\nSelect from the drop-down list to position the centre of the frame using a specified intersection.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nNearest to\nSelect from the drop-down list to position the centre of the frame using a specified nearest to point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nClick Cancel to close the Point Construction Option Form window.\n2D Cursor hit\nSelect from the drop-down list to position the frame using a cursor pick on the drawing view.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nEnd point of\nSelect from the drop-down list to position the centre of the frame using a specified end point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nCentre point of\nSelect from the drop-down list to position the centre of the frame using a specified center point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nMid point of\nSelect from the drop-down list to position the centre of the frame using a specified mid point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nMid pt between\nSelect from the drop-down list to position the centre of the frame using a specified mid point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nIntersection at\nSelect from the drop-down list to position the centre of the frame using a specified intersection.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nInter between\nSelect from the drop-down list to position the centre of the frame using a specified intersection.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\nNearest to\nSelect from the drop-down list to position the centre of the frame using a specified nearest to point.\nYou are prompted to Specify position\nClick to identify the center point of the of the frame.\n\n\n\nPoint Construction Option Form\n2D Cursor hit\nSpecify position\nEnd point of\nSpecify position\nCentre point of\nSpecify position\nMid point of\nSpecify position\nMid pt between\nSpecify position\nIntersection at\nSpecify position\nInter between\nSpecify position\nNearest to\nSpecify position\nCancel\nPoint Construction Option Form"}
{"Headers": "ADP Tagging", "Content": "Applies tagging to elements in the general ADP view.\n\nThe view name displays at the top of the ADP Tagging window.\nSelect the Instruments, Equipment, Valves and Pipe_Supports check boxes to apply tagging to the elements in the drawing.\nClick Update to apply the tagging settings or Cancel to discard any changes and close the ADP Tagging window.\n\n\n\nADP Tagging\nInstruments\nEquipment\nValves\nPipe_Supports\nUpdate\nCancel\nADP Tagging"}
{"Headers": "ADP Schedules", "Content": "Applies schedules to elements in the general ADP view.\n\nThe view name displays at the top of the ADP Schedules window.\nSelect the Nozzle_1, Nozzle_2, Valve and Pipe_Support check boxes to apply schedules to the elements in the drawing.\nYou can modify the position of schedules, click Modify to display the Modify Schedule window. Refer to Modify Schedule Position for further information.\nClick Update to apply the schedules, Re-Build to build the schedules table, or Cancel to discard any changes and close the ADP Schedules window.\n\n\n\nModify Schedule Position\nADP Schedules\nNozzle_1\nNozzle_2\nValve\nPipe_Support\nModify\nModify Schedule\nModify Schedule Position\nUpdate\nRe-Build\nCancel\nADP Schedules"}
{"Headers": "General ADP View Attributes", "Content": "Sets the general ADP view attributes.\n\nThe view name displays at the top of the General ADP View Attributes window.\nView Orientation\nSelect from the drop-down list to define the view orientation.\nThe view orientation can be defined in Up, Down, Left and Right directions.\nSection Mode\nSelect Standard from the drop-down list or Omit Frac. Comp. to remove components from the view that only partially display.\nArc Tolerance\nInput a value in the field to define the tolerance within which arcs must be drawn.\nGraphics Angle\nInput an angular value in the field to define the view graphic angle.\nPerspective\nInput an angular value in the field to define the perspective angle. A value of 0 indicates a parallel view.\nGapping\nInput a dimensional value in the field to define the gap, the default value is 1.50mm.\nView Orientation\nSelect from the drop-down list to define the view orientation.\nThe view orientation can be defined in Up, Down, Left and Right directions.\nSection Mode\nSelect Standard from the drop-down list or Omit Frac. Comp. to remove components from the view that only partially display.\nArc Tolerance\nInput a value in the field to define the tolerance within which arcs must be drawn.\nGraphics Angle\nInput an angular value in the field to define the view graphic angle.\nPerspective\nInput an angular value in the field to define the perspective angle. A value of 0 indicates a parallel view.\nGapping\nInput a dimensional value in the field to define the gap, the default value is 1.50mm.\nClick OK to apply the attribute settings or Cancel to discard any changes and close the Modify General ADP View window.\nView Orientation\nSelect from the drop-down list to define the view orientation.\nThe view orientation can be defined in Up, Down, Left and Right directions.\nSection Mode\nSelect Standard from the drop-down list or Omit Frac. Comp. to remove components from the view that only partially display.\nArc Tolerance\nInput a value in the field to define the tolerance within which arcs must be drawn.\nGraphics Angle\nInput an angular value in the field to define the view graphic angle.\nPerspective\nInput an angular value in the field to define the perspective angle. A value of 0 indicates a parallel view.\nGapping\nInput a dimensional value in the field to define the gap, the default value is 1.50mm.\n\n\n\nGeneral ADP View Attributes\nView Orientation\nUp\nDown\nLeft\nRight\nSection Mode\nStandard\nOmit Frac. Comp.\nArc Tolerance\nGraphics Angle\nPerspective\nGapping\nOK\nCancel\nModify General ADP View"}
{"Headers": "Update View", "Content": "Sets the elements to be updated and specifies the log file settings for the general ADP view.\n\nUpdate\nSelect the check boxes to define the view elements to be updated. The elements available for selection are:\nDesign Graphics\nSchedules\nTagging\nAnnotation\nUnused\nEquipment\nGridline.\nNote:\nReference grids can be used on ADP drawings. By default, gridline functionality is not available.\nNote:\nBy default, the Automatic Savework check box is selected.\nLog File\nDirectory\nInput a value in the field to modify the location of the log file.\nFile Name\nInput the file name or click Browse to navigate to the required folder.\nMessages\nSelect from the drop-down list to define the number of messages to be written to the log file. The options available are Debug, Full, Brief or Summary. Debug is very verbose, and is primarily intended to help developers to investigate any issues with the translation of particular files. If Debug is selected, the On Error drop-down list become active.\nOn Error\nSelect from the drop-down list to define the action to be taken when an error occurs in Debug mode.\nSelect Handle Locally for Draw to log the error and attempt to continue the view update.\nSelect Stop Processing for Draw to end the update process if an update error is found.\nCreate Batch Macro\nAllows you to associate a batch macro file with the drawing view. Refer to Create Batch Macro for further information.\nUpdate\nSelect the check boxes to define the view elements to be updated. The elements available for selection are:\nLog File\n\nInput a value in the field to modify the location of the log file.\nInput the file name or click Browse to navigate to the required folder.\nSelect from the drop-down list to define the number of messages to be written to the log file. The options available are Debug, Full, Brief or Summary. Debug is very verbose, and is primarily intended to help developers to investigate any issues with the translation of particular files. If Debug is selected, the On Error drop-down list become active.\nOn Error\nSelect from the drop-down list to define the action to be taken when an error occurs in Debug mode.\nSelect Handle Locally for Draw to log the error and attempt to continue the view update.\nSelect Stop Processing for Draw to end the update process if an update error is found.\nCreate Batch Macro\nAllows you to associate a batch macro file with the drawing view. Refer to Create Batch Macro for further information.\nClick Update Now to update the ADP view, messages appear on the status bar detailing information about the creation process, which can take a few minutes.\nUpdate\nSelect the check boxes to define the view elements to be updated. The elements available for selection are:\nDesign Graphics\nSchedules\nTagging\nAnnotation\nUnused\nEquipment\nGridline.\nNote:\nReference grids can be used on ADP drawings. By default, gridline functionality is not available.\nNote:\nBy default, the Automatic Savework check box is selected.\nLog File\nDirectory\nInput a value in the field to modify the location of the log file.\nFile Name\nInput the file name or click Browse to navigate to the required folder.\nMessages\nSelect from the drop-down list to define the number of messages to be written to the log file. The options available are Debug, Full, Brief or Summary. Debug is very verbose, and is primarily intended to help developers to investigate any issues with the translation of particular files. If Debug is selected, the On Error drop-down list become active.\nOn Error\nSelect from the drop-down list to define the action to be taken when an error occurs in Debug mode.\nSelect Handle Locally for Draw to log the error and attempt to continue the view update.\nSelect Stop Processing for Draw to end the update process if an update error is found.\nCreate Batch Macro\nAllows you to associate a batch macro file with the drawing view. Refer to Create Batch Macro for further information.\nDesign Graphics\nSchedules\nTagging\nAnnotation\nUnused\nEquipment\nGridline.\nDesign Graphics\nDesign Graphics\nSchedules\nSchedules\nTagging\nTagging\nAnnotation\nAnnotation\nUnused\nUnused\nEquipment\nEquipment\nGridline.\nGridline.\nNote:\nReference grids can be used on ADP drawings. By default, gridline functionality is not available.\nNote:\nBy default, the Automatic Savework check box is selected.\n\n\n\nCreate Batch Macro\nUpdate\nNote\n:\nNote\n:\nAutomatic Savework\nLog File\nDirectory\nFile Name\nBrowse\nMessages\nDebug\nFull\nBrief\nSummary\nDebug\nOn Error\nOn Error\nDebug\nHandle Locally\nStop Processing\nCreate Batch Macro\nCreate Batch Macro\nUpdate Now"}
{"Headers": "Create Batch Macro", "Content": "Associates a batch macro file with the general ADP view.\n\nThe Create Update Batch Macro window allows you to define the location and loading method of the batch macro file. Refer to Macros for further information.\nBatch Macro\nDirectory\nInput a value in the field to modify the location of the batch macro file.\nFile Name\nInput the file name or click Browse to navigate to the required folder.\nGenerate Module Entry Syntax\nSelect the check box to generate syntax for entry to other modules in the batch macro file, by default.\nAppware Loading Method\nSelect the Macros option button to load the Appware from the batch macro file.\nSelect the Binary File option button to load the Appware from a binary file. The Directory and File Name fields become active.\nDirectory\nInput a value in the field to modify the location of the binary file.\nFile Name\nInput the file name or click Browse to navigate to the required folder.\nBatch Macro\n\nInput a value in the field to modify the location of the batch macro file.\nInput the file name or click Browse to navigate to the required folder.\nSelect the check box to generate syntax for entry to other modules in the batch macro file, by default.\nAppware Loading Method\nSelect the Macros option button to load the Appware from the batch macro file.\nSelect the Binary File option button to load the Appware from a binary file. The Directory and File Name fields become active.\nInput a value in the field to modify the location of the binary file.\nInput the file name or click Browse to navigate to the required folder.\nClick OK to associate the batch macro file or Cancel to discard any changes and close the Create Update Batch Macro window.\nBatch Macro\nDirectory\nInput a value in the field to modify the location of the batch macro file.\nFile Name\nInput the file name or click Browse to navigate to the required folder.\nGenerate Module Entry Syntax\nSelect the check box to generate syntax for entry to other modules in the batch macro file, by default.\nAppware Loading Method\nSelect the Macros option button to load the Appware from the batch macro file.\nSelect the Binary File option button to load the Appware from a binary file. The Directory and File Name fields become active.\nDirectory\nInput a value in the field to modify the location of the binary file.\nFile Name\nInput the file name or click Browse to navigate to the required folder.\n\n\n\nMacros\nCreate Update Batch Macro\nMacros\nBatch Macro\nDirectory\nFile Name\nBrowse\nGenerate Module Entry Syntax\nAppware Loading Method\nMacros\nBinary File\nDirectory\nFile Name\nDirectory\nFile Name\nBrowse\nOK\nCancel\nCreate Update Batch Macro"}
{"Headers": "Equipment Centerlines", "Content": "Creates and deletes equipment centerlines on a general ADP view. Functionality is also available to update the equipment centerline display for the view.\nCreate\nAllows you to create an equipment centerline. Refer to Add Equipment Centreline for further information\nDelete\nAllows you to remove an existing equipment centerline. Refer to Delete Equipment Centerline for further information\nUpdate\nClick to update the centerline display for equipment elements in the currently selected view.\nYou are prompted to select element\nClick to identify the equipment element. The equipment centerline display is updated in the view.\nThe prompt is repeated until the command is ended. You can continue to update the centerline display for equipment elements in the currently selected view.\nPress ESC to end the command.\nUpdate all\nClick to update the centerline display for all elements in the currently selected view.\nThe equipment centerline display is updated in the view and the command ends automatically.\nCreate\nAllows you to create an equipment centerline. Refer to Add Equipment Centreline for further information\nDelete\nAllows you to remove an existing equipment centerline. Refer to Delete Equipment Centerline for further information\nUpdate\nClick to update the centerline display for equipment elements in the currently selected view.\nYou are prompted to select element\nClick to identify the equipment element. The equipment centerline display is updated in the view.\nThe prompt is repeated until the command is ended. You can continue to update the centerline display for equipment elements in the currently selected view.\nPress ESC to end the command.\nUpdate all\nClick to update the centerline display for all elements in the currently selected view.\nThe equipment centerline display is updated in the view and the command ends automatically.\n\nCreate\nAllows you to create an equipment centerline. Refer to Add Equipment Centreline for further information\nDelete\nAllows you to remove an existing equipment centerline. Refer to Delete Equipment Centerline for further information\nUpdate\nClick to update the centerline display for equipment elements in the currently selected view.\nYou are prompted to select element\nClick to identify the equipment element. The equipment centerline display is updated in the view.\nThe prompt is repeated until the command is ended. You can continue to update the centerline display for equipment elements in the currently selected view.\nPress ESC to end the command.\nUpdate all\nClick to update the centerline display for all elements in the currently selected view.\nThe equipment centerline display is updated in the view and the command ends automatically.\n\n\n\nAdd Equipment Centreline\nDelete Equipment Centerline\nCreate\nAdd Equipment Centreline\nDelete\nDelete Equipment Centerline\nUpdate\nselect element\nESC\nUpdate all"}
{"Headers": "Create Weld Labels", "Content": "Adds a weld label to a view using a specific weld symbol template.The weld symbol template is automatically added on selection of the STWELD element via a linked attribute between the STWELD and WDET elements.\nYou are prompted to Specify attachment point\nClick to identify the Ppoint of the weld element to be labelled.\nYou are then prompted to Specify connection Point or\nInput values in the dimension fields and press Enter or click to identify the position of the weld label.\nThe weld label is added to the drawing and the command ends automatically.\nThroughout the weld label creation process you can press ESC to cancel the command. Additional functionality is also available.\nLeft\nPress the down arrow key and select Left to specify the weld label direction as left.\nRight\nPress the down arrow key and select Right to specify the weld label direction as right.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nLeft\nPress the down arrow key and select Left to specify the weld label direction as left.\nRight\nPress the down arrow key and select Right to specify the weld label direction as right.\nBack\nPress the down arrow key and select Back to undo the last action.\n\nDynamic text can be used with the weld symbol templates via #PML. A specific PML function has been created which requires a WDET key.\n\nLeft\nPress the down arrow key and select Left to specify the weld label direction as left.\nRight\nPress the down arrow key and select Right to specify the weld label direction as right.\nBack\nPress the down arrow key and select Back to undo the last action.\n\n\n\nSpecify attachment point\nSpecify connection Point\nor\nEnter\nESC\nLeft\nLeft\nRight\nRight\nBack\nBack"}
{"Headers": "Area Based Automatic Drawing Production", "Content": "Area Based Automatic Drawing Production (ABA) functionality is available with Draw.\nABA drawings can be compiled by selecting predefined areas and templates created by the administrator. An area is a physical box volume within the database defined by coordinates, and a template is a drawing layout with set parameters that describes a number of views, graphical representation in the views, and types of labelling.\nYou can produce ABA drawings from the 3D model. A pre-requisite to using ABA is that the administrator has configured ABA functionality.\nABA allows you to produce drawings by selecting predefined physical box volumes (known as areas), these are then matched to a template that describes the format of the drawing to be produced. A typical example of the ABA work process is to update a drawing after a change has been made to the 3D model for a maintenance project.\nFunctionality is available for you to create drawings using the administrative elements defined by an administrator. If any of the functionality covered does not exist, consult the administrator.\n\n\n"}
{"Headers": "ABA Defaults", "Content": "If the project is organised in such a way that different disciplines have different ABA libraries, you can select a different Defaults file to that initially loaded.\nThe ABA Defaults window allows you define the ABA defaults file for DRAW. When re-entering DRAW at the next session, this defaults file is opened initially.\nThe functionality of the ABA Defaults window is explained, refer to ABA Defaults for further information.\n\n\n\nABA Defaults\nABA Defaults\nABA Defaults\nABA Defaults"}
{"Headers": "ABA Drawing Process", "Content": "Sets the options for the creation and modification of ABA drawings.\nAll of the tasks that are associated with the creation or modification of ABA drawings are initiated from a Process Drawings Control window which acts as a task hub.\n\nThe key activities you can perform are:\nSelect combinations of areas and templates to define New Drawings.\nSelect Existing Drawings to be updated or regenerated.\nSelect or define a Drawing Registry Area to store the drawings.\nAdd the required Process Settings to the drawings.\nStart Process drawings (either immediately or as a batch process).\nSelect combinations of areas and templates to define New Drawings.\nSelect combinations of areas and templates to define New Drawings.\nSelect Existing Drawings to be updated or regenerated.\nSelect Existing Drawings to be updated or regenerated.\nSelect or define a Drawing Registry Area to store the drawings.\nSelect or define a Drawing Registry Area to store the drawings.\nAdd the required Process Settings to the drawings.\nAdd the required Process Settings to the drawings.\nStart Process drawings (either immediately or as a batch process).\nStart Process drawings (either immediately or as a batch process).\n\n\n\nNew Drawings\nExisting Drawings\nDrawing Registry Area\nProcess Settings\nStart Process\nProcess Drawings Control\nNew Drawings\nExisting Drawings\nDrawing Registry Area\nProcess Settings\nStart Process"}
{"Headers": "Menu Options", "Content": "The menu options are:\n\nFile\nLoad Log File\nSelect from the drop-down menu to display the File Browser.\nClose\nSelect from the drop-down menu to close the Process Drawings Control window.\nSetting\nGeneral Defaults\nSelect from the drop-down menu to display the ABA Defaults window. Refer to ABA Defaults for further information.\nBrowse\nExisting Drawings\nSelect from the drop-down menu to display the ABA Browse Sheets window, which allows you to view ABA drawings that have already been created. Refer to ABA Browse Sheets for further information. Close the browser to return to the Process Drawings Control window.\nStored LogFiles\nSelect from the drop-down menu to display the File Browser.\nShow Version\nSelect from the drop-down menu to display the currently installed version of ABA.\nFile\n\nSelect from the drop-down menu to display the File Browser.\nSelect from the drop-down menu to close the Process Drawings Control window.\nSetting\n\nSelect from the drop-down menu to display the ABA Defaults window. Refer to ABA Defaults for further information.\nBrowse\n\nSelect from the drop-down menu to display the ABA Browse Sheets window, which allows you to view ABA drawings that have already been created. Refer to ABA Browse Sheets for further information. Close the browser to return to the Process Drawings Control window.\nSelect from the drop-down menu to display the File Browser.\nSelect from the drop-down menu to display the currently installed version of ABA.\n\nFile\nLoad Log File\nSelect from the drop-down menu to display the File Browser.\nClose\nSelect from the drop-down menu to close the Process Drawings Control window.\nSetting\nGeneral Defaults\nSelect from the drop-down menu to display the ABA Defaults window. Refer to ABA Defaults for further information.\nBrowse\nExisting Drawings\nSelect from the drop-down menu to display the ABA Browse Sheets window, which allows you to view ABA drawings that have already been created. Refer to ABA Browse Sheets for further information. Close the browser to return to the Process Drawings Control window.\nStored LogFiles\nSelect from the drop-down menu to display the File Browser.\nShow Version\nSelect from the drop-down menu to display the currently installed version of ABA.\n\n\n\nFile Browser\nABA Defaults\nABA Browse Sheets\nFile Browser\nFile\nLoad Log File\nFile Browser\nClose\nProcess Drawings Control\nSetting\nGeneral Defaults\nABA Defaults\nABA Defaults\nBrowse\nExisting Drawings\nABA Browse Sheets\nABA Browse Sheets\nProcess Drawings Control\nStored LogFiles\nFile Browser\nShow Version"}
{"Headers": "New Drawings", "Content": "The New Drawings part of the Process Drawings Control window allows you to create new drawings for processing.\n\nTo select new drawings, on the New Drawings part of the Process Drawings Control window, click Select to display the ABA New Drawing List window.\n\nYou can select a combination of areas and templates to create drawings from.\nAreas\nSelect from the drop-down list to filter the Design Areas list.\nAreas\nSelect from the drop-down list to filter the Design Areas list.\nClick to select the required combination from the Drawing Templates and Design Areas lists or right-click the current selection to display a drop-down menu. The functionality is available in both lists:\nSelect All\nSelect from the drop-down menu to select all templates or areas in the list.\nClear Selection\nSelect from the drop-down menu to clear all selected templates or in the list.\nSelect All\nSelect from the drop-down menu to select all templates or areas in the list.\nClear Selection\nSelect from the drop-down menu to clear all selected templates or in the list.\nABA areas are defined by the administrator, refer to Create and Modify Area Libraries for further information.\nAdd Selection to List\nSelect from the drop-down menu to include the selected combination of templates and areas in the Process Drawings Control window.\nReplace List with Selection\nSelect from the drop-down menu to replace any existing templates and areas in the Process Drawings Control window with the current selections.\nAdd Selection to List\nSelect from the drop-down menu to include the selected combination of templates and areas in the Process Drawings Control window.\nReplace List with Selection\nSelect from the drop-down menu to replace any existing templates and areas in the Process Drawings Control window with the current selections.\nClick Drawing Names to modify the drawing naming method. Refer to Drawing Names for further information.\nClick Apply to accept the selections or Cancel to discard any changes and close the ABA New Drawing List window.\nWhen the New Drawings part of the Process Drawings Control window is populated, right-click to display a drop-down menu.\n\nSelect All\nSelect from the drop-down menu to select all drawings in the New Drawings list.\nClear Selection\nSelect from the drop-down menu to deselect all currently selected drawings in the New Drawings list.\nRename\nAllows you to rename the currently selected drawing in the New Drawings list. Select from the drop-down menu to display the Rename Drawing window.\nYou can modify the value in the Name field to rename the drawing.\nClick OK to apply the new drawing name or Cancel to discard any changes and close the Rename Drawing window.\nRemove All\nSelect from the drop-down list to remove all drawings from the New Drawings list.\nRemove Selection\nSelect from the drop-down list to remove the currently selected drawing from the New Drawings list.\nSelect All\nSelect from the drop-down menu to select all drawings in the New Drawings list.\nClear Selection\nSelect from the drop-down menu to deselect all currently selected drawings in the New Drawings list.\nRename\nAllows you to rename the currently selected drawing in the New Drawings list. Select from the drop-down menu to display the Rename Drawing window.\n\nYou can modify the value in the Name field to rename the drawing.\nClick OK to apply the new drawing name or Cancel to discard any changes and close the Rename Drawing window.\nRemove All\nSelect from the drop-down list to remove all drawings from the New Drawings list.\nRemove Selection\nSelect from the drop-down list to remove the currently selected drawing from the New Drawings list.\n\nAreas\nSelect from the drop-down list to filter the Design Areas list.\nSelect All\nSelect from the drop-down menu to select all templates or areas in the list.\nClear Selection\nSelect from the drop-down menu to clear all selected templates or in the list.\nAdd Selection to List\nSelect from the drop-down menu to include the selected combination of templates and areas in the Process Drawings Control window.\nReplace List with Selection\nSelect from the drop-down menu to replace any existing templates and areas in the Process Drawings Control window with the current selections.\nSelect All\nSelect from the drop-down menu to select all drawings in the New Drawings list.\nClear Selection\nSelect from the drop-down menu to deselect all currently selected drawings in the New Drawings list.\nRename\nAllows you to rename the currently selected drawing in the New Drawings list. Select from the drop-down menu to display the Rename Drawing window.\nYou can modify the value in the Name field to rename the drawing.\nClick OK to apply the new drawing name or Cancel to discard any changes and close the Rename Drawing window.\nRemove All\nSelect from the drop-down list to remove all drawings from the New Drawings list.\nRemove Selection\nSelect from the drop-down list to remove the currently selected drawing from the New Drawings list.\n\n\n\nCreate and Modify Area Libraries\nDrawing Names\nNew Drawings\nProcess Drawings Control\nNew Drawings\nProcess Drawings Control\nSelect\nABA New Drawing List\nAreas\nSelect All\nClear Selection\nCreate and Modify Area Libraries\nAdd Selection to List\nProcess Drawings Control\nReplace List with Selection\nProcess Drawings Control\nDrawing Names\nDrawing Names\nApply\nCancel\nABA New Drawing List\nNew Drawings\nProcess Drawings Control\nSelect All\nClear Selection\nRename\nRename Drawing\nName\nOK\nCancel\nRename Drawing\nRemove All\nRemove Selection"}
{"Headers": "Existing Drawings", "Content": "The Existing Drawings part of the Process Drawings Control window allows you to select existing drawings for update, regeneration or renumbering.\n\nSelect\nAllows you to populate the Existing Drawings list from a list of existing drawings. Refer to Select Existing Drawing drawings for further information.\nAdd\nAllows you to add an element to the Existing Drawings list.\nSelect CE from the drop-down list and click Add to add the currently selected drawing on the Draw Explorer to the Existing Drawings list.\nSelect Current List from the drop-down list and click Add to add drawings from the currently selected list of drawings. Refer to Lists/Collections for further information.\nSelect\nAllows you to populate the Existing Drawings list from a list of existing drawings. Refer to Select Existing Drawing drawings for further information.\nAdd\nAllows you to add an element to the Existing Drawings list.\nSelect CE from the drop-down list and click Add to add the currently selected drawing on the Draw Explorer to the Existing Drawings list.\nSelect Current List from the drop-down list and click Add to add drawings from the currently selected list of drawings. Refer to Lists/Collections for further information.\n\nSelect\nAllows you to populate the Existing Drawings list from a list of existing drawings. Refer to Select Existing Drawing drawings for further information.\nAdd\nAllows you to add an element to the Existing Drawings list.\nSelect CE from the drop-down list and click Add to add the currently selected drawing on the Draw Explorer to the Existing Drawings list.\nSelect Current List from the drop-down list and click Add to add drawings from the currently selected list of drawings. Refer to Lists/Collections for further information.\n\n\n\nSelect Existing Drawing\nLists/Collections\nExisting Drawings\nProcess Drawings Control\nSelect\nSelect Existing Drawing\nAdd\nCE\nAdd\nCurrent List\nAdd\nLists/Collections"}
{"Headers": "Drawing Registry Area", "Content": "The Drawing Registry Area part of the Process Drawings Control window allows you to place the created or modified drawings in a specific registry (REGI) in the DRAW database. The storage area is defined by selecting an existing registry or by creating one, by default.\n\nCreate One Automatically\nSelect the option button to create a registry. You must input a registry name in the field.\nUse Existing Registry\nSelect the option button to select an existing registry.\nClick Select to display a list of registries, refer to Select Registry for further information.\nAlternatively, input a registry name in the field.\nAlternatively, click CE to populate the field with the name of the currently selected registry element.\nCreate One Automatically\nSelect the option button to create a registry. You must input a registry name in the field.\nUse Existing Registry\nSelect the option button to select an existing registry.\nClick Select to display a list of registries, refer to Select Registry for further information.\nAlternatively, input a registry name in the field.\nAlternatively, click CE to populate the field with the name of the currently selected registry element.\n\nCreate One Automatically\nSelect the option button to create a registry. You must input a registry name in the field.\nUse Existing Registry\nSelect the option button to select an existing registry.\nClick Select to display a list of registries, refer to Select Registry for further information.\nAlternatively, input a registry name in the field.\nAlternatively, click CE to populate the field with the name of the currently selected registry element.\n\n\n\nSelect Registry\nDrawing Registry Area\nProcess Drawings Control\nCreate One Automatically\nUse Existing Registry\nSelect\nSelect Registry\nCE"}
{"Headers": "Process Settings", "Content": "The Process Settings part of the Process Drawings Control window allows you to define and modify process tasks.\n\nTasks which act on the entire 'run', can be added to the drawing process.\nProcess Tasks\nAllows you to define the process tasks used. Refer to Process Tasks for further information.\nAvailable Registries\nAllows you to define the process type. Refer to Process Type for further information.\nAuto Numbering\nSelect the ON option button to apply auto numbering to the process.\nSelect the OFF to omit auto numbering from the process.\nAuto Numbering assigns a specific numbering code to the drawings to generate a Drawing number. The administrator sets up the Drawing number and configuration.\nProcess Tasks\nAllows you to define the process tasks used. Refer to Process Tasks for further information.\nAvailable Registries\nAllows you to define the process type. Refer to Process Type for further information.\nAuto Numbering\nSelect the ON option button to apply auto numbering to the process.\nSelect the OFF to omit auto numbering from the process.\nAuto Numbering assigns a specific numbering code to the drawings to generate a Drawing number. The administrator sets up the Drawing number and configuration.\n\nProcess Tasks\nAllows you to define the process tasks used. Refer to Process Tasks for further information.\nAvailable Registries\nAllows you to define the process type. Refer to Process Type for further information.\nAuto Numbering\nSelect the ON option button to apply auto numbering to the process.\nSelect the OFF to omit auto numbering from the process.\nAuto Numbering assigns a specific numbering code to the drawings to generate a Drawing number. The administrator sets up the Drawing number and configuration.\nNote:\nIf there are no tasks selected this is indicated in Red. If tasks are selected this is indicated in green.\n\n\n\nProcess Tasks\nProcess Type\nProcess Settings\nProcess Drawings Control\nNote\n:\nProcess Tasks\nProcess Tasks\nAvailable Registries\nProcess Type\nAuto Numbering\nON\nOFF"}
{"Headers": "Start Process", "Content": "Defines the start process for the ABA drawings.\n\n\n"}
{"Headers": "Isometric Automatic Drawing Production", "Content": "The Isometric Automatic Drawing Production (IsoADP) functionality allows you to produce automatically annotated and dimensioned HVAC or cableway Isometric drawings with associated parts lists.\n\nIsometric ADP drawing allows you to create, modify and print Isometric drawings.\nTo produce a drawing and associated deliverables, an HVAC or CWAY design element must be selected to be processed. If required, settings can be modified as necessary before processing.\nOnce the drawing is created, it can be modified with the Isometric ADP functionality which has many of the necessary tools without the need to use the Isodraft menus.\n\n\n\n"}
{"Headers": "Isometric Drawings Production", "Content": "Sets the options for the creation and modification of isometric drawings.\nCWAY or HVAC design elements can be selected for Isometric Drawing Production.\nAll of the tasks available to you that are associated with creation of Isometric Drawings are initiated from a central Isometric Production window which acts as a task hub.\nDepending on selections made in the Isometric Production window, you are presented with further windows prompting for input. After inputting information in these windows you are returned to the Isometric Production window allowing the work flow to continue.\nBefore any Isometric drawings are produced the design element in the Model Explorer must be selected and identified as the CE.\n\n\n\n\n\nIsometric Production\nIsometric Production\nIsometric Production\nModel Explorer"}
{"Headers": "Track Current Element", "Content": "Dependant on whether the CE has had drawings produced before, you are presented with different options, on the Isometric Production window.\nBy default, the Track current element check box is not selected.\nTo automatically identify an element in the Model Explorer as the CE, select the Track current element check box. The Isometric Production window is also automatically updated.\nIf the CE has not had drawings produced before, a statement displays in the Existing Drawing part of the Isometric Production window.\n\n\n\n\nIsometric Production\nTrack current element\nIsometric Production\nExisting Drawing\nIsometric Production"}
{"Headers": "Process Types", "Content": "If the CE has had drawings produced and has been searched for with the search filter Those drawn, you are required to update or recreate these drawings.\n\nNote:\nIt is not possible to process a single existing drawing sheet; all drawing sheets must be processed at the same time even if some of them have not been modified.\n\n\n\nThose drawn\nNote\n:"}
{"Headers": "Model Elements Search", "Content": "Searches for Model element drawings using a selected element in the Model Explorer as the Current Element (CE) under which to search. The default is world (*).\nAlternatively, you can input an element name in the Model element to search under: field.\nClick to move up one level in the Model Explorer hierarchy.\nClick to refresh the search results when the search criteria is changed if the Track current element check box is not selected. If required, select the Track current element check box to track element selection in the Model Explorer, refer to Track Current Element for further information.\nAny HVAC or CWAY design elements can be searched for, even of a drawing has not been produced before, the result displays in the Search Results table.\n\n\nThe Search for: drop-down menu allows you to define the element type to search. You can search for CWAY or HVAC design elements.\n\nThe Filter the results for: drop-down list allows you to filter the search results.\nThose not drawn\nSelect from the drop-down list to search for all elements that have yet to be drawn, this is the default.\nThose drawn\nSelect from the drop-down list to search for all elements that have associated drawings.\nThose drawn by me\nSelect from the drop-down list to search for elements that have associated drawings processed by you.\nBad Drawing Reference\nSelect from the drop-down list to search for elements that have bad reference links to drawings.\nAll\nSelect from the drop-down list to search for all elements without being filtered.\nThose not drawn\nSelect from the drop-down list to search for all elements that have yet to be drawn, this is the default.\nThose drawn\nSelect from the drop-down list to search for all elements that have associated drawings.\nThose drawn by me\nSelect from the drop-down list to search for elements that have associated drawings processed by you.\nBad Drawing Reference\nSelect from the drop-down list to search for elements that have bad reference links to drawings.\nAll\nSelect from the drop-down list to search for all elements without being filtered.\nClick Search to update the Search Results table. Refer to Search Results Table for further information.\nThose not drawn\nSelect from the drop-down list to search for all elements that have yet to be drawn, this is the default.\nThose drawn\nSelect from the drop-down list to search for all elements that have associated drawings.\nThose drawn by me\nSelect from the drop-down list to search for elements that have associated drawings processed by you.\nBad Drawing Reference\nSelect from the drop-down list to search for elements that have bad reference links to drawings.\nAll\nSelect from the drop-down list to search for all elements without being filtered.\n\n\n\nTrack Current Element\nSearch Results Table\nModel element to search under:\nTrack current element\nTrack current element\nTrack Current Element\nSearch Results\nSearch for:\nCWAY\nHVAC\nFilter the results for:\nThose not drawn\nThose drawn\nThose drawn by me\nBad Drawing Reference\nAll\nSearch\nSearch Results\nSearch Results Table"}
{"Headers": "Search Results Table", "Content": "Displays the results of the HVAC or CWAY element search.\n\nName\nDisplays the name of the element.\nValid\nReports whether the Design element has any members and whether it has any spatial volume.\nDrawn\nReports whether the CE has a corresponding drawing that exists in the current MDB.\nAccess\nReports if a drawing exists for the CE, and if you have modification access rights.\nMode\nReports the process type available. If a drawing does not exist for the CE, then the type is Create. If a drawing does exist then by default Update displays.\nName\nDisplays the name of the element.\nValid\nReports whether the Design element has any members and whether it has any spatial volume.\nDrawn\nReports whether the CE has a corresponding drawing that exists in the current MDB.\nAccess\nReports if a drawing exists for the CE, and if you have modification access rights.\nMode\nReports the process type available. If a drawing does not exist for the CE, then the type is Create. If a drawing does exist then by default Update displays.\nTo update or recreate select Update or Generate from the drop-down list in the mode column of the grid. Refer to Update or Recreate for further information.\nTo select the Design elements to process, select single or multiple entries in the Search Results Table.\nRight-click the currently selected entry to display a drop-down menu.\n\nSelect All\nSelect from the drop-down menu to select all entries in the table.\nDeselect All\nSelect from the drop-down menu to deselect all currently selected entries in the table.\nRemove Selected\nSelect from the drop-down menu to remove the currently selected entry from the table.\nRemove All\nSelect from the drop-down menu to remove all entries from the table\nGoto Element\nSelect from the drop-down menu to make the currently selected entry the current element in the Design hierarchy.\nGoto Drawing\nIf a drawing exists, select from the drop-down menu to make the currently selected drawing the current element in the hierarchy.\nDisplay Details\nSelect from the drop-down menu to display the Details of the Selected Element window.\nSelect All\nSelect from the drop-down menu to select all entries in the table.\nDeselect All\nSelect from the drop-down menu to deselect all currently selected entries in the table.\nRemove Selected\nSelect from the drop-down menu to remove the currently selected entry from the table.\nRemove All\nSelect from the drop-down menu to remove all entries from the table\nGoto Element\nSelect from the drop-down menu to make the currently selected entry the current element in the Design hierarchy.\nGoto Drawing\nIf a drawing exists, select from the drop-down menu to make the currently selected drawing the current element in the hierarchy.\nDisplay Details\nSelect from the drop-down menu to display the Details of the Selected Element window.\n\nTo switch to single search mode, make sure the Track current element check box is not selected and the currently selected element in the Model Explorer is an HVAC or CWAY element, on the Isometric Production window, click Switch to Single Mode.\nName\nDisplays the name of the element.\nValid\nReports whether the Design element has any members and whether it has any spatial volume.\nDrawn\nReports whether the CE has a corresponding drawing that exists in the current MDB.\nAccess\nReports if a drawing exists for the CE, and if you have modification access rights.\nMode\nReports the process type available. If a drawing does not exist for the CE, then the type is Create. If a drawing does exist then by default Update displays.\nSelect All\nSelect from the drop-down menu to select all entries in the table.\nDeselect All\nSelect from the drop-down menu to deselect all currently selected entries in the table.\nRemove Selected\nSelect from the drop-down menu to remove the currently selected entry from the table.\nRemove All\nSelect from the drop-down menu to remove all entries from the table\nGoto Element\nSelect from the drop-down menu to make the currently selected entry the current element in the Design hierarchy.\nGoto Drawing\nIf a drawing exists, select from the drop-down menu to make the currently selected drawing the current element in the hierarchy.\nDisplay Details\nSelect from the drop-down menu to display the Details of the Selected Element window.\nNote:\nTo select multiple entries in the Search Results table, click and press Ctrl or Shift on the keyboard.\n\n\n\nUpdate\nRecreate\nName\nValid\nDrawn\nAccess\nMode\nCreate\nUpdate\nUpdate\nGenerate\nUpdate\nRecreate\nSearch Results Table\nNote\n:\nSearch Results\nCtrl\nShift\nSelect All\nDeselect All\nRemove Selected\nRemove All\nGoto Element\nGoto Drawing\nDisplay Details\nDetails of the Selected Element\nTrack current element\nIsometric Production\nSwitch to Single Mode"}
{"Headers": "Save Search Results", "Content": "Saves the content of the Search Results table to an Excel file.\n\nYou must input a name and navigate to a location for the file.\nClick Save to save the file or Cancel to discard any inputs and close the Save Drawing Report as Excel window.\n\n\n\nSearch Results\nSave\nCancel\nSave Drawing Report as Excel"}
{"Headers": "Multiple Systems", "Content": "The options are only available when the Current Element (CE) has not already been processed.\nWhen the Isometric Production window displays a single design element, identified as the CE for processing, you can switch to search for multiple design elements. That is the design element that owns the CE in the design hierarchy and all other design elements owned by this element in the hierarchy.\nFrom the Isometric Production window click search for HVAC Mains to search for HVAC elements or click Cableways to search for cableways.\nYou can the search, preview spooling and modify settings.\n\nSearch for HVAC Mains\nSearch for Cableways\nSearch for HVAC Mains\nSearch for HVAC Mains\nSearch for Cableways\nSearch for Cableways\n\n\n\nIsometric Production\nIsometric Production\nsearch for HVAC Mains\nCableways"}
{"Headers": "Spooling", "Content": "Isometric ADP produces Fabrication and Erection isometrics, which means that the drawing is designed to provide fabrication information about spools.\nA Design Branch is broken down into a smaller set of easily managed Design components called spools. These spools are fabricated individually and later connected together to form the Design Branch in situ.\nIsometric ADP allows for two methods of splitting HVAC and CWAY Design Branches into Fabrication Spools.\n\n\n"}
{"Headers": "Preview Spooling", "Content": "The HVAC or CWAY main branch are the design elements to process in order to produce isometric drawings, the drawing contains a subset of components in each side branch, each subset being referred to as a Fabrication Spool. It is possible to control and preview how the Design elements are split into spools. Refer to Spooling for further information.\nAs the selection of a split type or different complexity effects how the branches are split into spools, you can preview the spools before production of the drawings.\nTo preview the spooling, on the Tasks part of the Isometric Production window, select a Design element in the Search Results table, click Preview Spooling.\n\nThe Isometric Splitting tab displays a graphical representation of the CE in the 3D view. All of the manipulation functionality common to all design modules is available. Refer to Editor for further information.\n\nYou can preview the Look Direction, Spool Playback Controls and the Spool Split Control.\n\n\n\n\nSpooling\nEditor\nLook Direction\nSpool Playback Controls\nSpool Split Control\nSpooling\nTasks\nIsometric Production\nSearch Results\nPreview Spooling\nIsometric Splitting\nEditor\nLook Direction\nSpool Playback Controls\nSpool Split Control"}
{"Headers": "Modify Settings", "Content": "Defines the user settings that are available for modification.\nIsometric ADP has many Default Settings, many of which are only able to be changed by the administrator, refer to Isometric Automatic Drawing Production for further information. However, you can modify some of the default settings.\nOn the Tasks part of the Isometric Production window, click Modify User Settings, to populate the Isometric Production window with the user settings.\n\n\n\n\n\nIsometric Automatic Drawing Production\nIsometric Automatic Drawing Production\nTasks\nIsometric Production\nModify User Settings\nIsometric Production"}
{"Headers": "Process Drawings", "Content": "When you have selected the Design elements and made changes to the Settings, from the Process part of the Isometric Production window, click Start. An Isometric ADP drawing is created and each created sheet displays as a separate tab.\n\n\n\nProcess\nIsometric Production\nStart"}
{"Headers": "Log File", "Content": "During the creation, update or regeneration of isometric drawings, the application passes through several stages, any of which can encounter errors. As a result, a Log File is produced.\n\nIf Design elements have not been processed during the current session, a window displays, allowing you to browse for existing Log Files.\n\n\n\n"}
{"Headers": "Drawing Content", "Content": "Isometric ADP drawings contain several components\u00b4.\n\n\n\n"}
{"Headers": "Isometric Detail", "Content": "The drawing contains a single graphical view of the Fabrication Spool, which includes a variety of annotations and can, if required, display the following internal details:\n\nDesign components are tagged to match the entries in the Material Parts Table.\nThe centreline is dimensioned with either a full or overall dimension type dependant on the default choice, this can be modified. Refer to Modify Drawings for further information.\nLabels are provided to indicate continuation to other sheets in this drawing or to other parts of the 3D model system (as long as the connection data is available).\nCertain elements such as Tees, Bends and Elbows are labelled to indicate their coordinate position, while BRCO elements are labelled to provide connection data.\nThe start position of the Spool is marked as the origin, this relates to the nearest reference grid and displays on the Isometric ADP Keyplan.\nDesign components are tagged to match the entries in the Material Parts Table.\nDesign components are tagged to match the entries in the Material Parts Table.\nThe centreline is dimensioned with either a full or overall dimension type dependant on the default choice, this can be modified. Refer to Modify Drawings for further information.\nThe centreline is dimensioned with either a full or overall dimension type dependant on the default choice, this can be modified. Refer to Modify Drawings for further information.\nLabels are provided to indicate continuation to other sheets in this drawing or to other parts of the 3D model system (as long as the connection data is available).\nLabels are provided to indicate continuation to other sheets in this drawing or to other parts of the 3D model system (as long as the connection data is available).\nCertain elements such as Tees, Bends and Elbows are labelled to indicate their coordinate position, while BRCO elements are labelled to provide connection data.\nCertain elements such as Tees, Bends and Elbows are labelled to indicate their coordinate position, while BRCO elements are labelled to provide connection data.\nThe start position of the Spool is marked as the origin, this relates to the nearest reference grid and displays on the Isometric ADP Keyplan.\nThe start position of the Spool is marked as the origin, this relates to the nearest reference grid and displays on the Isometric ADP Keyplan.\n\n\n\nModify Drawings\nModify Drawings"}
{"Headers": "Material Parts Table", "Content": "The Material Parts Table contains information about each Design component in the Spool. The format of the Material Parts Table is defined by the administrator.\n\n\n\n\nMaterial Parts Table"}
{"Headers": "Location Plan", "Content": "The Location Plan indicates the relationship between the currently drawn Spool and the complete HVAC Main or Cableway. It is a standard View so you can manipulate it or annotate it as with any other Draw View.\n\n\n\n"}
{"Headers": "Keyplan", "Content": "The keyplan provides the origin location of the currently drawn Spool within a current reference grid. The administrator configures the reference grid that is used. The nearest grid lines display, the distance to them is indicated with dimensions in the relevant units.\n\nNote:\nBecause the keyplan is not to scale, the dimensions display the grid offset values using the Linear Dimension attribute DMTX, the grid offset values are calculated, not extracted from the 3D model.\n\n\n\nNote\n:"}
{"Headers": "Revision Table", "Content": "The Revision Table contains information about the current Issue of the Isometric Sheet.\nDuring creation or update of the sheet, the Revision value is applied. The administrator configures the revision system used, refer to Revision for further information. The date of creation or update is included as well as the name of the author.\nEach row in the table reflects the settings of each REVI element stored below the sheet, with each cell being a TEXT element. You can change each cell individually, if required, but the complete table can be easily modified, refer to Modify Drawings for further information.\n\n\n\n\nRevision\nModify Drawings\nRevision\nModify Drawings"}
{"Headers": "Title Block", "Content": "The Title Block contains information extracted from the Drawing and Sheet element attributes, this is controlled by the Intelligent Hash Codes used on the Backing Sheet, defined by the administrator. The supplied backing sheet extracts the following data:\nHVAC Isometric\nThe DRWG attribute TITLE\nHTESTHVAC\nThe DRWG user-defined attribute :IdpLineNo\nDuct Class:\nThe SHEE user-definable attribute :IdpLineNo\nDrawing No:\nThe DRWG attribute DrwgNumber\nSheet\nThe SHEE user-defined attributes :IdpSheetNo and :IdpNumberOff\nHVAC Isometric\nThe DRWG attribute TITLE\nHTESTHVAC\nThe DRWG user-defined attribute :IdpLineNo\nDuct Class:\nThe SHEE user-definable attribute :IdpLineNo\nDrawing No:\nThe DRWG attribute DrwgNumber\nSheet\nThe SHEE user-defined attributes :IdpSheetNo and :IdpNumberOff\n\nHVAC Isometric\nThe DRWG attribute TITLE\nHTESTHVAC\nThe DRWG user-defined attribute :IdpLineNo\nDuct Class:\nThe SHEE user-definable attribute :IdpLineNo\nDrawing No:\nThe DRWG attribute DrwgNumber\nSheet\nThe SHEE user-defined attributes :IdpSheetNo and :IdpNumberOff\n\n\n"}
{"Headers": "North Direction", "Content": "The North Direction is a Symbolic label located at a position defined by a setting on the Backing Sheet. You must not make modifications to the label directly as it is linked to the Isometric Detail View look direction.\nYou can modify the North Direction. Refer to Modify Drawings for further information.\n\n\n\n\nModify Drawings\nModify Drawings"}
{"Headers": "Total Weight and Center of Gravity", "Content": "The Total Weight and Center of Gravity display values are calculated by the application. If during the calculation any errors occur or any components are found with zero weight, a warning message is included in the display. The values are extracted from the SHEE user-defined attributes :IdpTotWeight and :IdpCofG.\n\n\n\n"}
{"Headers": "Modify Drawings", "Content": "When Isometric ADP drawings are created or updated, you can modify the drawing using the standard Draw functionality. The Isometric Tools group of the Auto tab provides functionality designed specifically for the modification of Isometric drawings.\n\n\n\nIsometric Tools\nAuto"}
{"Headers": "Search for Isometric ADP Drawings", "Content": "Searches for existing Isometric ADP Drawings.\n\nThe Search part of the Isometric Drawings Search window allows you to define the search criteria for the drawing search.\n\nInput a value in the Search field and select a filter from the Search drop-down list to define the search criteria. For example, Input APS in the field and select Drwg Name from the drop-down list to display all drawings that contain APS in the drawing name.\nAll Dwgs\nSelect from the drop-down list to display all drawings.\nDrwg Name\nSelect from the drop-down list to display all drawings that match the name in the Search field.\nDrwg Number\nSelect from the drop-down list to display all drawings that match the drawing number in the Search field.\nDrwg Date\nSelect from the drop-down list to display all drawings that match the date in the Search field.\nDrwg Author\nSelect from the drop-down list to display all drawings that match the author name in the Search field.\nLine Number\nSelect from the drop-down list to display all drawings that match the line number in the Search field.\nRev Number\nSelect from the drop-down list to display all drawings that match the revision number in the Search field.\nRev Desc\nSelect from the drop-down list to display all drawings that match the revision description in the Search field.\nRev Date\nSelect from the drop-down list to display all drawings that match the revision date in the Search field.\nStatus\nSelect from the drop-down list to display all drawings that match the status in the Search field.\nAll Dwgs\nSelect from the drop-down list to display all drawings.\nDrwg Name\nSelect from the drop-down list to display all drawings that match the name in the Search field.\nDrwg Number\nSelect from the drop-down list to display all drawings that match the drawing number in the Search field.\nDrwg Date\nSelect from the drop-down list to display all drawings that match the date in the Search field.\nDrwg Author\nSelect from the drop-down list to display all drawings that match the author name in the Search field.\nLine Number\nSelect from the drop-down list to display all drawings that match the line number in the Search field.\nRev Number\nSelect from the drop-down list to display all drawings that match the revision number in the Search field.\nRev Desc\nSelect from the drop-down list to display all drawings that match the revision description in the Search field.\nRev Date\nSelect from the drop-down list to display all drawings that match the revision date in the Search field.\nStatus\nSelect from the drop-down list to display all drawings that match the status in the Search field.\nClick Go to populate the Drawings part of the Isometric Drawings Search window with the search results.\nThe Drawings part of the Isometric Drawings Search window displays the results from the drawings search. You can modify the Drawings list display. Functionality is also available to open, print and export drawing sheets.\n\nTo modify the display of the Drawings list, right-click the currently selected drawing to display a drop-down menu.\n\nDisplay\nDraw Name\nSelect from the drop-down menu to display the Drawings list by name.\nDrwg Number\nSelect from the drop-down menu to display the Drawings list by number.\nLine Number\nSelect from the drop-down menu to display the Drawings list by line number.\nDisplay\n\nSelect from the drop-down menu to display the Drawings list by name.\nSelect from the drop-down menu to display the Drawings list by number.\nSelect from the drop-down menu to display the Drawings list by line number.\nTo open, print or export drawing sheets to PDF format, right-click the currently selected sheet to display a drop-down menu.\n\nOpen Sheet\nSelect from the drop-down menu to display the currently selected sheet in the view.\nPrint With Current Settings\nSelect from the drop-down menu to print the currently selected sheet. The sheet is printed using the current printer settings. Refer to Print Sheets for further information.\nExport to PDF\nSelect from the drop-down menu to export the currently selected sheet to a PDF format. The sheet is exported using the current PDF export settings. Refer to Export to PDF for further information.\nOpen Sheet\nSelect from the drop-down menu to display the currently selected sheet in the view.\nPrint With Current Settings\nSelect from the drop-down menu to print the currently selected sheet. The sheet is printed using the current printer settings. Refer to Print Sheets for further information.\nExport to PDF\nSelect from the drop-down menu to export the currently selected sheet to a PDF format. The sheet is exported using the current PDF export settings. Refer to Export to PDF for further information.\n\nAll Dwgs\nSelect from the drop-down list to display all drawings.\nDrwg Name\nSelect from the drop-down list to display all drawings that match the name in the Search field.\nDrwg Number\nSelect from the drop-down list to display all drawings that match the drawing number in the Search field.\nDrwg Date\nSelect from the drop-down list to display all drawings that match the date in the Search field.\nDrwg Author\nSelect from the drop-down list to display all drawings that match the author name in the Search field.\nLine Number\nSelect from the drop-down list to display all drawings that match the line number in the Search field.\nRev Number\nSelect from the drop-down list to display all drawings that match the revision number in the Search field.\nRev Desc\nSelect from the drop-down list to display all drawings that match the revision description in the Search field.\nRev Date\nSelect from the drop-down list to display all drawings that match the revision date in the Search field.\nStatus\nSelect from the drop-down list to display all drawings that match the status in the Search field.\nDisplay\nDraw Name\nSelect from the drop-down menu to display the Drawings list by name.\nDrwg Number\nSelect from the drop-down menu to display the Drawings list by number.\nLine Number\nSelect from the drop-down menu to display the Drawings list by line number.\nOpen Sheet\nSelect from the drop-down menu to display the currently selected sheet in the view.\nPrint With Current Settings\nSelect from the drop-down menu to print the currently selected sheet. The sheet is printed using the current printer settings. Refer to Print Sheets for further information.\nExport to PDF\nSelect from the drop-down menu to export the currently selected sheet to a PDF format. The sheet is exported using the current PDF export settings. Refer to Export to PDF for further information.\n\n\n\nPrint Sheets\nExport to PDF\nSearch\nIsometric Drawings Search\nSearch\nSearch\nAPS\nDrwg Name\nAll Dwgs\nDrwg Name\nSearch\nDrwg Number\nSearch\nDrwg Date\nSearch\nDrwg Author\nSearch\nLine Number\nSearch\nRev Number\nSearch\nRev Desc\nSearch\nRev Date\nSearch\nStatus\nSearch\nGo\nDrawings\nIsometric Drawings Search\nDrawings\nIsometric Drawings Search\nDisplay\nDraw Name\nDrwg Number\nLine Number\nOpen Sheet\nPrint With Current Settings\nPrint Sheets\nExport to PDF\nExport to PDF"}
{"Headers": "Isometric Direction", "Content": "Sets the view direction for individual isometric drawing sheets.\nOnce the Isometric drawings have been produced with a particular direction selected, all associated sheets are created using the same view direction. For some drawings this is not satisfactory as the routing direction can be orthogonal to the paper direction (in or out of the page).\nIso 1\nSelect from the drop-down list to display the currently selected sheet in Iso 1 view direction. The drawing is updated and all annotations recalculated accordingly.\nIso 2\nSelect from the drop-down list to display the currently selected sheet in Iso 2 view direction. The drawing is updated and all annotations recalculated accordingly.\nIso 3\nSelect from the drop-down list to display the currently selected sheet in Iso 3 view direction. The drawing is updated and all annotations recalculated accordingly.\nIso 4\nSelect from the drop-down list to display the currently selected sheet in Iso 4 view direction. The drawing is updated and all annotations recalculated accordingly.\nIso 1\nSelect from the drop-down list to display the currently selected sheet in Iso 1 view direction. The drawing is updated and all annotations recalculated accordingly.\nIso 2\nSelect from the drop-down list to display the currently selected sheet in Iso 2 view direction. The drawing is updated and all annotations recalculated accordingly.\nIso 3\nSelect from the drop-down list to display the currently selected sheet in Iso 3 view direction. The drawing is updated and all annotations recalculated accordingly.\nIso 4\nSelect from the drop-down list to display the currently selected sheet in Iso 4 view direction. The drawing is updated and all annotations recalculated accordingly.\n\nIso 1\nSelect from the drop-down list to display the currently selected sheet in Iso 1 view direction. The drawing is updated and all annotations recalculated accordingly.\nIso 2\nSelect from the drop-down list to display the currently selected sheet in Iso 2 view direction. The drawing is updated and all annotations recalculated accordingly.\nIso 3\nSelect from the drop-down list to display the currently selected sheet in Iso 3 view direction. The drawing is updated and all annotations recalculated accordingly.\nIso 4\nSelect from the drop-down list to display the currently selected sheet in Iso 4 view direction. The drawing is updated and all annotations recalculated accordingly.\n\n\n\nIso 1\nIso 1\nIso 2\nIso 2\nIso 3\nIso 3\nIso 4\nIso 4"}
{"Headers": "Layer Visibility", "Content": "Sets the visibility of individual layers for isometric drawings.\n\nSelect the relevant layer from the drop-down menu. Select the check box to make the layer visible, deselect the check box to make the layer invisible.\nYou can modify visibility for the following layers:\nKeyplan\nLocation\nMTO Tags\nDimensions\nUser labels\nSpecification Breaks\nNamed Elements\nPenetrations\nContinuations\nISO Origin\nSymbols\nElevations\nMTO Table\nKeyplan\nKeyplan\nLocation\nLocation\nMTO Tags\nMTO Tags\nDimensions\nDimensions\nUser labels\nUser labels\nSpecification Breaks\nSpecification Breaks\nNamed Elements\nNamed Elements\nPenetrations\nPenetrations\nContinuations\nContinuations\nISO Origin\nISO Origin\nSymbols\nSymbols\nElevations\nElevations\nMTO Table\nMTO Table\n\n\n"}
{"Headers": "Nudge the View Scale", "Content": "Sets the view scale of the isometric drawing.\nWhen the Isometric drawing is created, the main Isometric Detail view scale is calculated using the Scale and the Look Through Point of the 3D model graphics. In most cases the scale dictates that the graphics almost completely fill the available space, there may not be sufficient room to place, for example, Labels.\nTo increase the view scale by a small amount, click Nudge Up.\nTo decrease the view scale by a small amount, click Nudge Down.\nTo modify the scale factor used for Nudge Up and Nudge Down. Click Nudge Factor, and select a percentage value from the drop-down list. The nudge factor can be set to 1%, 2%, 5% or 10%.\n\n\n\n\nNudge Up\nNudge Down\nNudge Up\nNudge Down\nNudge Factor\n1%\n2%\n5%\n10%"}
{"Headers": "Dimension Style", "Content": "The default dimension style is set by the administrator. You can modify the style to one of four options.\nYou can continue to cycle through the Dimension Styles until the display is satisfactory.\nOverall\nOnly those components with a change in direction, for example, BEND and ELBO types or TEE type are dimensioned.\nAll\nAll components are dimensioned.\nAll Horizontal\nAll components are dimensioned. Any compound dimension is set to provide the distance between the points but projected onto the horizontal plane.\nOverall Horizontal\nOnly those components with a change in direction, for example, BEND and ELBO types or TEE type are dimensioned. Any compound dimension is set to provide the distance between the points but projected onto the horizontal plane.\nOverall\nOnly those components with a change in direction, for example, BEND and ELBO types or TEE type are dimensioned.\n\n\nAll\nAll components are dimensioned.\n\n\nAll Horizontal\nAll components are dimensioned. Any compound dimension is set to provide the distance between the points but projected onto the horizontal plane.\n\n\nOverall Horizontal\nOnly those components with a change in direction, for example, BEND and ELBO types or TEE type are dimensioned. Any compound dimension is set to provide the distance between the points but projected onto the horizontal plane.\n\n\n\nOverall\nOnly those components with a change in direction, for example, BEND and ELBO types or TEE type are dimensioned.\nAll\nAll components are dimensioned.\nAll Horizontal\nAll components are dimensioned. Any compound dimension is set to provide the distance between the points but projected onto the horizontal plane.\nOverall Horizontal\nOnly those components with a change in direction, for example, BEND and ELBO types or TEE type are dimensioned. Any compound dimension is set to provide the distance between the points but projected onto the horizontal plane.\n\n\n\nOverall\nAll\nAll Horizontal\nOverall Horizontal"}
{"Headers": "Revision Details", "Content": "Sets the revision details for the isometric drawing.\nWhen the Isometric drawing is created or updated, the issue number, date and author are set. Other details are not set, for example, the description or approval signatures.\n\nTo add details to the current revision, input the details in the fields as required.\nClick Apply to update the drawing revision table or Cancel to discard any changes and close the Isometric Drawing Revision window.\n\nTo add a new revision, select an issue from the Rev drop-down list, add new details as necessary and click Apply. The drawing revision table updates to display all previous and new revisions.\n\nTo switch an Internal revision to an External revision you can either:\nUpdate a drawing and modify the revision type (refer to Create and Compare Drawing Revisions for further information).\nModify the ADP revision settings, refer to Revision for further information.\nUpdate a drawing and modify the revision type (refer to Create and Compare Drawing Revisions for further information).\nUpdate a drawing and modify the revision type (refer to Create and Compare Drawing Revisions for further information).\nModify the ADP revision settings, refer to Revision for further information.\nModify the ADP revision settings, refer to Revision for further information.\n\n\n\nCreate and Compare Drawing Revisions\nRevision\nApply\nCancel\nIsometric Drawing Revision\nRev\nApply\nCreate and Compare Drawing Revisions\nRevision"}
{"Headers": "Draw the Design", "Content": "At VIEW level point construction methods can be used to:\nThe THPO OF @ syntax (similarly FRPO OF @ allows input of a 2D constructed point, provided the current VIEW is orthogonal, and the 2D position lies in the current VIEW.\nposition the VIEW using the AT command\nset the VIEW size and position using the VREGION command\nset the THPO, FRPO and ONPO positions of the VIEW.\nposition the VIEW using the AT command\nposition the VIEW using the AT command\nset the VIEW size and position using the VREGION command\nset the VIEW size and position using the VREGION command\nset the THPO, FRPO and ONPO positions of the VIEW.\nset the THPO, FRPO and ONPO positions of the VIEW.\n\n\n"}
{"Headers": "Draw Database", "Content": "The top-level graphical elements in the Draw Database hierarchy are:\n\nThe principal element is the Drawing (DRWG), which is the Database equivalent of the traditional paper drawing. All the elements below DRWG in the hierarchy are used to store the information required to completely define the Drawing.\nA Drawing can own one or more Sheet (SHEE) elements, which correspond to the sheets of a paper drawing (\u2018Sheet 1 of 3\u2019, \u2018Sheet 2 of 3\u2019). A Drawing can consist of a single Sheet. A Sheet is the highest-level element that can display within a view.\nA Sheet can own one or more VIEW elements. These are projections of parts of the Design Database. A VIEW element has attributes that:\nThe full Draw database hierarchy is illustrated. Refer to Draw Database Hierarchy for further information.\ndefine the viewing parameters (looking direction, through point or scale)\ndefine the size, position and orientation of the region on the Sheet that the View occupies\nrefer to another Draw database element that contains a list of the Design (or Catalogue) elements that make up the VIEW picture.\ndefine the viewing parameters (looking direction, through point or scale)\ndefine the viewing parameters (looking direction, through point or scale)\ndefine the size, position and orientation of the region on the Sheet that the View occupies\ndefine the size, position and orientation of the region on the Sheet that the View occupies\nrefer to another Draw database element that contains a list of the Design (or Catalogue) elements that make up the VIEW picture.\nrefer to another Draw database element that contains a list of the Design (or Catalogue) elements that make up the VIEW picture.\n\n\n\nDraw Database Hierarchy\nDraw\nDrawing\nSheet\nDraw\nDraw\nDraw Database Hierarchy"}
{"Headers": "Create a Drawing, a Sheet and a View", "Content": "The top-level element in a database is the World. You cannot delete or create the World. Starting with the World as the current element, you can create the hierarchy under the World using a command sequence, for example:\nYou can omit all commands except for NEW DRWG and NEW VIEW if there is only Department, one Registry and one Sheet on the Drawing. If the administrative elements do not exist they are created automatically.\nDepartments (DEPT) and Registries (REGI) are administrative elements. Departments own Registries.\n\nNEW DEPT /PIPES\nNEW REGI /PIPREG\nNEW DRWG /PD101\nNEW SHEET /SHEET1\nNEW VIEW /PLAN\nNote:\nYou can have several VIEWs on a Sheet. Each VIEW can contain a picture of a different part of the 3D model, or different views of the same part of the 3D model. The contents of a view can be manipulated. Refer to Change the VIEW Attributes for further information.\n\n\n\nChange the VIEW Attributes\nWorld\nDepartments\nRegistries\nNote\n:\nChange the VIEW Attributes"}
{"Headers": "Define the Contents of a View", "Content": "There are two methods of specifying the contents of a VIEW:\nSpecifying the contents directly, by referencing a single Design database element. The content can be as small as a BRANCH or a complete SITE.\nSpecifying the contents indirectly, by referencing a Draw IDLIST element that defines a list of Design database elements. Refer to Define VIEW Contents Using Id Lists for further information.\nSpecifying the contents directly, by referencing a single Design database element. The content can be as small as a BRANCH or a complete SITE.\nSpecifying the contents directly, by referencing a single Design database element. The content can be as small as a BRANCH or a complete SITE.\nSpecifying the contents indirectly, by referencing a Draw IDLIST element that defines a list of Design database elements. Refer to Define VIEW Contents Using Id Lists for further information.\nSpecifying the contents indirectly, by referencing a Draw IDLIST element that defines a list of Design database elements. Refer to Define VIEW Contents Using Id Lists for further information.\n\n\n\nDefine VIEW Contents Using Id Lists\ndirectly\nindirectly\nDraw\nDefine VIEW Contents Using Id Lists"}
{"Headers": "Define Views Using the AUTO Commands", "Content": "There are two AUTO commands: AUTOSCALE and AUTOSIZE. (AUTOSCALE can be abbreviated to AUTOS but the full command is generally used here to avoid ambiguity).\n\n\n"}
{"Headers": "AUTOSCALE Command", "Content": "The AUTOSCALE command is typically:\nThe command carries out the various operations:\nAUTOSCALE\nAUTOSCALE /ZONE1\nAUTOSCALE /IDLIST-STEAM-PIPEWORK\nThe VIEW\u2019s IDLN (ID List Name) attribute is set to the name of the Design item or IDList element to be drawn (/ZONE1 or /IDLIST-STEAM-PIPEWORK in our second and third examples).\nThe VIEW's THPO (Through Position) attribute is set to the World coordinates corresponding to the centre of interest of the Design items to be drawn.\nThe VIEW's VSCA (View Scale) attribute is set to a value calculated such that the drawn Design items fit within the View rectangle. The current values of the VIEW's DIR and SIZE attributes are used (these define the 'looking direction' and the size of the rectangle).\nThe VIEW\u2019s IDLN (ID List Name) attribute is set to the name of the Design item or IDList element to be drawn (/ZONE1 or /IDLIST-STEAM-PIPEWORK in our second and third examples).\nThe VIEW\u2019s IDLN (ID List Name) attribute is set to the name of the Design item or IDList element to be drawn (/ZONE1 or /IDLIST-STEAM-PIPEWORK in our second and third examples).\nThe VIEW's THPO (Through Position) attribute is set to the World coordinates corresponding to the centre of interest of the Design items to be drawn.\nThe VIEW's THPO (Through Position) attribute is set to the World coordinates corresponding to the centre of interest of the Design items to be drawn.\nThe VIEW's VSCA (View Scale) attribute is set to a value calculated such that the drawn Design items fit within the View rectangle. The current values of the VIEW's DIR and SIZE attributes are used (these define the 'looking direction' and the size of the rectangle).\nThe VIEW's VSCA (View Scale) attribute is set to a value calculated such that the drawn Design items fit within the View rectangle. The current values of the VIEW's DIR and SIZE attributes are used (these define the 'looking direction' and the size of the rectangle).\nNote:\nThe AUTOSCALE command only sets the IDLN attribute if it has not already been set. A second AUTOSCALE command does not change the IDLN (but the specified Design item or IDList is used in the recalculation of the VSCA and THPO attributes). An AUTOSCALE command by itself uses the existing IDLN setting to recalculate VSCA and THPO.\n\n\n\nNote\n:"}
{"Headers": "AUTOSIZE Command", "Content": "The AUTOSIZE command is typically:\nThe command carries out various operations:\nAUTOSIZE\nAUTOSIZE /150-A-3-Branch1\nAUTOSIZE /Equipment-List\nThe VIEW's IDLN (ID List Name) attribute is set to the name of the Design item or IDList element to be drawn (/150-A-3-Branch1 or /Equipment-List in our second and third examples).\nThe VIEW's THPO (Through Position) attribute is set to the World coordinates corresponding to the centre of interest of the Design items to be drawn.\nThe VIEW's SIZE (View Rectangle Size) attribute is set to a value calculated such that the drawn Design items fit within the View rectangle. The current values of the VIEW's DIR and VSCA attributes are used (these define the 'looking direction' and scale).\nThe VIEW's IDLN (ID List Name) attribute is set to the name of the Design item or IDList element to be drawn (/150-A-3-Branch1 or /Equipment-List in our second and third examples).\nThe VIEW's IDLN (ID List Name) attribute is set to the name of the Design item or IDList element to be drawn (/150-A-3-Branch1 or /Equipment-List in our second and third examples).\nThe VIEW's THPO (Through Position) attribute is set to the World coordinates corresponding to the centre of interest of the Design items to be drawn.\nThe VIEW's THPO (Through Position) attribute is set to the World coordinates corresponding to the centre of interest of the Design items to be drawn.\nThe VIEW's SIZE (View Rectangle Size) attribute is set to a value calculated such that the drawn Design items fit within the View rectangle. The current values of the VIEW's DIR and VSCA attributes are used (these define the 'looking direction' and scale).\nThe VIEW's SIZE (View Rectangle Size) attribute is set to a value calculated such that the drawn Design items fit within the View rectangle. The current values of the VIEW's DIR and VSCA attributes are used (these define the 'looking direction' and scale).\nNote:\nThe AUTOSIZE command only sets the IDLN attribute if it has not already been set. A second AUTOSIZE command does not change the IDLN (but the specified Design item or IDList is used in the recalculation of the SIZE and THPO attributes). An AUTOSIZE command by itself uses the existing IDLN setting to recalculate SIZE and THPO.\n\n\n\nNote\n:"}
{"Headers": "Generate the Graphics", "Content": "Once the critical attributes of a VIEW are set (for example, by an AUTO command) the graphics can be generated by:\nNote:\nThe UPDATE command creates the VIEW graphics in a Central Picture Store (CPS) within the computer's memory.\nThe SAVEWORK command is not necessary but is recommended. It saves the graphics in the CPS to Picture Files in the Picture File directory. In subsequent Draw sessions, the graphics are read from the Picture File without the need for an UPDATE command.\nIf you leave Draw via a QUIT command the graphics in the CPS are not saved and any existing Picture Files are not updated.\nLeaving Draw by switching to another module performs an implicit SAVEWORK, graphics in the CPS are saved to Picture Files.\n\n\n\nNote\n:\nDraw\nDraw\nDraw"}
{"Headers": "Update Reference Grid Annotations", "Content": "The reference grid annotations can be generated by:\nA complete regeneration of the reference grid is carried out and all generated annotations are updated. User created annotations are unchanged.\nA simple update is carried out. All missing annotations are generated. All automatically generated and created annotations remain unchanged.\n\n\n"}
{"Headers": "Define VIEW Contents Using Id Lists", "Content": "You can add many elements to a VIEW by displaying the contents of an Id List (IDLI element). The Id List contains a list of the elements to display. Id Lists are contained within Drawing List Libraries (DLLB elements).\nStarting at World level, the library part of the database is set up as:\nRefer to Create a Drawing, a Sheet and a View for further information.\nThe Id List is constructed by using DRAADD and DRAREMOVE commands:\nDRAADD and DRAREMOVE can be combined on a single line, for example:\nThe DRAADD and DRAREMOVE commands automatically create the Add Entry (ADDE) and Remove Entry (REME) elements, refer to Create a Drawing, a Sheet and a View for further information, also setting those ADDE and REME attributes which refer to (in this example) appropriate elements in the Design database. Other Id Lists can be added or removed in the same way. For example:\nIf an Id List has Remove entries then the member list order is important. For an entry to be removed it must have been (implicitly) added previously. Hence a Remove Entry must never be the first element in an Id List. Consider the command sequences:\nSequence 1\nSequence 2\nDRAADD /ZONE.PIPES\nDRAADD /ZONE.PIPES\nDRAADD /PIPE1-1\nDRAREM /PIPE1\nDRAREM /PIPE1\nDRAADD /PIPE1-1\nSequence 1\nSequence 2\nDRAADD /ZONE.PIPES\nDRAADD /ZONE.PIPES\nDRAADD /PIPE1-1\nDRAREM /PIPE1\nDRAREM /PIPE1\nDRAADD /PIPE1-1\nIn Sequence 1 the final command removes all branches owned by /PIPE1 - including /PIPE1-1 which has been added by the second command (and implicitly by the first). In Sequence 2 these commands have been reordered so that having removed all branches in /PIPE1 (second command) the required Branch (/PIPE1-1) is added by the final command.\nHaving created an Id List it can be used to define the contents of a VIEW by setting the VIEW's IDLN attribute directly:\nor indirectly:\nRefer to Define Views Using the AUTO Commands for further information.\nSequence 1\nSequence 2\nDRAADD /ZONE.PIPES\nDRAADD /ZONE.PIPES\nDRAADD /PIPE1-1\nDRAREM /PIPE1\nDRAREM /PIPE1\nDRAADD /PIPE1-1\nNEW LIBY /LIB1\nNEW DLLB /DLB1\nNEW IDLI /ID1\nDRAADD /ZONE.PIPES2-1\nDRAADD /ZONE.EQUI2-1\nDRAREMOVE /PIPE2-1-12\nDRAREM /PUMP2-1-12\nNEW IDLI /LIST1\nDRAADD /ZONE1\nDRAADD /LIST2\nDRAREM /LIST3\nIDLI /ID1\nAUTO /ID1\nLibrary (LIBY) elements can display at four positions in the hierarchy. Refer to Draw Database Hierarchy for further information. They are administrative elements used to group together several types of sub-library. The type of sub-library of interest here is the Drawing List Library (DLLB) .\nThe DLLB is used to group together Id List (IDLI) elements.\nLibrary (LIBY) elements can display at four positions in the hierarchy. Refer to Draw Database Hierarchy for further information. They are administrative elements used to group together several types of sub-library. The type of sub-library of interest here is the Drawing List Library (DLLB) .\nLibrary (LIBY) elements can display at four positions in the hierarchy. Refer to Draw Database Hierarchy for further information. They are administrative elements used to group together several types of sub-library. The type of sub-library of interest here is the Drawing List Library (DLLB) .\nThe DLLB is used to group together Id List (IDLI) elements.\nThe DLLB is used to group together Id List (IDLI) elements.\nNote:\nWhen evaluated individually both /LIST2 and /LIST3 must define a set of design elements which are then added to/removed from /LIST1, respectively. In particular if /LIST3 is being used to remove a number of Branches (say) from /LIST1 then it must be defined as:\nDRAADD /BRAN1, /BRAN2, /BRAN3\nand NOT as:\nDRAREM /BRAN1, /BRAN2, /BRAN3\nNote:\nGRIDSYstem and GRIDAXis elements can be added to IDLists but cannot be the sole member of the IDList. When drawn their GRIDLNs are considered to be of infinite length and are extended to the VIEW boundary. AUTO commands ignore these elements when calculating the VSCA, THPOS, and SIZE attributes of a VIEW.\n\n\n\nCreate a Drawing, a Sheet and a View\nDraw Database Hierarchy\nCreate a Drawing, a Sheet and a View\nDefine Views Using the AUTO Commands\nId List\nDrawing List\nLibraries\nCreate a Drawing, a Sheet and a View\nLibrary\nDraw Database Hierarchy\nDrawing List Library\nId List\nDRAADD /ZONE1.EQUIP, /ZONE1.PIPES DRAREMOVE /VESS1, BRAN 2 OF /PIPE3\nCreate a Drawing, a Sheet and a View\nNote\n:\nDRAADD /BRAN1, /BRAN2, /BRAN3\nDRAREM /BRAN1, /BRAN2, /BRAN3\nSequence 1\nSequence 2\nDRAADD /ZONE.PIPES\nDRAADD /ZONE.PIPES\nDRAADD /PIPE1-1\nDRAREM /PIPE1\nDRAREM /PIPE1\nDRAADD /PIPE1-1\nDefine Views Using the AUTO Commands\nNote\n:"}
{"Headers": "Add Elements to 3D View", "Content": "The DESADD and DESREMOVE commands allow for the addition and removal of Design elements to a 3D view. The syntax is similar to the DRAADD and DRAREMOVE commands. For example:\nThe sequence of commands adds elements /ZONE.PIPES2-1 and /ZONE.EQUI2-1 to a 3D View, and removes /PIPE2-1-12 and /PUMP2-1-12. The sequence is normally activated by the interface.\nDESADD /ZONE.PIPES2-1\nDESADD /ZONE.EQUI2-1\nDESREMOVE /PIPE2-1-12\nDESREM /PUMP2-1-12\n\n\n\nDESADD /ZONE.PIPES2-1\nDESADD /ZONE.EQUI2-1\nDESREMOVE /PIPE2-1-12\nDESREM /PUMP2-1-12"}
{"Headers": "Selective Additions to the Id List", "Content": "The Selection syntax can be used to generate Id Lists. For example:\nwhere !COLLECTION is a local variable containing a list of Design element references.\nIn the examples, the Selection criteria are not stored in the database but expanded, and the resulting list of elements stored. The result can produce very long Id Lists. You can define criteria, which are stored in the database, and only expanded at the time of an UPDATE Design command using the RULE keyword. For example:\nYou must be sure to use the RULE keyword in these cases, otherwise the criterion is evaluated when the Rule is defined, and very many ADDEs and REMEs can be created.\nThese forms of the DRAADD and DRAREMOVE commands set the CRIT attribute of the ADDE and REME elements. The CRIT attribute can also be set directly, for example:\nIn this case the RULE keyword is not required.\nDRAADD ALL EQUI FOR /SITE/99\nDRAREM ALL BRAN WITH (HBOR LT 25 AND TBOR LT 25) FOR\n/ZONE/PIPES\nDRAADD ALL FROM !COLLECTION\nDRAADD RULE ALL ZONE WITH ( FUNC EQ 'PIPING')\nDRAREM RULE ALL BRAN WITH (HBOR LT 25 AND TBOR LT 25)\nNEW ADDE\nCRIT ALL BRAN WITH (PSPE EQ /RF300)\n\n\n\nDRAADD ALL EQUI FOR /SITE/99\nDRAREM ALL BRAN WITH (HBOR LT 25 AND TBOR LT 25) FOR\n/ZONE/PIPES\nDRAADD ALL FROM !COLLECTION\nDesign"}
{"Headers": "Spatial Map", "Content": "The DRAADD ... WITHIN variation of the DRAADD command uses the AVEVA E3D Design spatial map. The spatial map is a simplified geometric representation of the 3D model. For example:\nThe first example creates a list of DRAADD entries, one for each significant element that is in /ZONE99 and which overlaps the specified volume. The second example generates a list of DRAREMOVE entries, one for each significant element in the current MDB that overlaps the specified volume.\nDRAADD /ZONE99 WITHIN E5000 N5000 U5000 TO W1000 S1000 U0\nDRAREMOVE WITHIN E2500 N1000 U500 TO E0 N0 U0\nNote:\nIf the spatial map is not up-to-date the list of elements generated can be incorrect. The DRAADD ... WITHIN method can produce very long Id Lists. These are liable to become out-of-date as elements are added to, and removed from, the Design databases. Better results can be yielded by setting the IDLI\u2019s LIMI attribute to define the required volume and only DRAADD the relevant SITEs and ZONEs to the Id List.\n\n\n\nAVEVA E3D Design\nspatial map.\nNote\n:"}
{"Headers": "Change the Limits of the View Contents", "Content": "The display of Design elements within a VIEW can be changed without affecting the Id List by changing the LIMI attribute of the IDLI element, using the LIMITS command.\nExample\nLIMITS E1000 N8000 U1000 TO E5000 N1000 U900\nDefine limits explicitly.\nLIMITS @ TO @\nSet limits as 3D coordinates using the cursor.\nLIMITS ID @ ID @\n    Set limits as 3D coordinates via Design elements selected with the cursor.\nLIMITS E1000 N8000 U1000 TO E5000 N1000 U900\nDefine limits explicitly.\nLIMITS @ TO @\nSet limits as 3D coordinates using the cursor.\nLIMITS ID @ ID @\nSet limits as 3D coordinates via Design elements selected with the cursor.\n\nLIMITS E1000 N8000 U1000 TO E5000 N1000 U900\nDefine limits explicitly.\nLIMITS @ TO @\nSet limits as 3D coordinates using the cursor.\nLIMITS ID @ ID @\n    Set limits as 3D coordinates via Design elements selected with the cursor.\n\n\n\nwithout\nExample"}
{"Headers": "Clean Up Id Lists", "Content": "Id Lists can be purged of unknown references by the command:\nThe command scans down the database hierarchy from the current position and deletes all ADDE and REME elements whose IDNM attribute is null or references an unknown element.\n\n\n\nDELETE NULL IDLIstmembers"}
{"Headers": "Query Id Lists", "Content": "Q FOR /design_element_name\nQ IDLN FOR /design_element_name\nThese commands output information on whether the named element is wholly included in the named Id List (for example, in the Id List and no member elements DRAREMOVEd), partially included in the named Id List (for example, in the Id List but some member elements DRAREMOVEd), or absent from the named Id List. The Id List name/VIEW name is not required if the current element is the Id List itself or a related VIEW.\nQ IDLN DESC\nNote that querying the Id List in the usual way lists the ADDE and REME elements; a more comprehensive output can be obtained by:\nQ DESCRIPTION\nOther querying commands relating to Id Lists are:\nQ MAP\nQ VOLUME identifier\nQ WINDOW volume\n\n\n\nQ\n \nFOR \n/design_element_name\nQ IDLN FOR \n/design_element_name\nQ\n \nIDLN DESC\nQ DESCRIPTION\nQ MAP\nQ VOLUME \nidentifie\nQ WINDOW\nvolume"}
{"Headers": "Change the VIEW Attributes", "Content": "VIEW attributes can be set explicitly in the usual way, and the effect on an element\u2019s attributes of giving the various Draw commands can be seen by giving a QUERY ATTRIBUTES command for the element concerned.\n\n\n\nDraw"}
{"Headers": "VIEW Frame", "Content": "LFRA controls the visibility of the VIEW frame. The frame is drawn using the View\u2019s NLSTYLE/NLCOLOUR attributes. Refer to Colours and Styles for further information.\nLFRA TRUE  (or FRAME ON)\nLFRA FALSE  (or FRAME OFF)\n\n\n\nColours and Styles\nLFRA\nColours and Styles\nLFRA TRUE  \nFRAME ON\nLFRA FALSE  \nFRAME OFF"}
{"Headers": "View Size", "Content": "SIZE is the \u2018paper size\u2019 of the VIEW rectangle. Changing the size by a command, for example,\nleaves the scale of the VIEW contents unaffected, but moves the point at the centre of the picture to the centre of the new VIEW frame.\nThe SIZE attribute is also be changed by the VREGION command, which can be used to resize and reposition the VIEW. For example:\nVREGION FROM @ TO @\nOpposite corners of VIEW defined by cursor\nVREG X100 Y100 TO X500 Y500\nOpposite corners of VIEW defined explicitly\nVREG AT @\nCentre of VIEW defined by cursor\nVREG corner AT @\nSpecified corner of VIEW defined by cursor:\nTL top left\nTR top right\nBL bottom left\nBR bottom right\nC centre\nVREGION FROM @ TO @\nOpposite corners of VIEW defined by cursor\nVREG X100 Y100 TO X500 Y500\nOpposite corners of VIEW defined explicitly\nVREG AT @\nCentre of VIEW defined by cursor\nVREG corner AT @\nSpecified corner of VIEW defined by cursor:\nThe default size is that of the owning Sheet. The VREGION command also affects the XYPS attribute. Refer to View Center for further information.\nThe SIZE command can also be used at SHEE level to change the Sheet size.\nVREGION FROM @ TO @\nOpposite corners of VIEW defined by cursor\nVREG X100 Y100 TO X500 Y500\nOpposite corners of VIEW defined explicitly\nVREG AT @\nCentre of VIEW defined by cursor\nVREG corner AT @\nSpecified corner of VIEW defined by cursor:\nTL top left\nTR top right\nBL bottom left\nBR bottom right\nC centre\nSIZE 400 400\n\n\n\nView Center\nSIZE\nExample\nTL\nTR\nBL\nBR\nC\nView Center"}
{"Headers": "View Center", "Content": "XYPS controls the position of the center of the VIEW on its owning Sheet. The attribute takes two numeric values, which are the coordinates of the center of the VIEW relative to the bottom left corner of the Sheet. The attribute can be set directly by commands, for example,\nThe default XYPS is at the center of the Sheet.\n\nONPOS is the position of the centre of the VIEW contents, relative to the centre of the VIEW. VIEW contents are centered within the VIEW by default, so this attribute takes the default values x0 y0. ONPOS is set directly, for example:\nChanging ONPOS makes the existing VIEW graphics out-of-date, so an UPDATE Design command must be given.\n\nONPO 45 -25\n\n\n\nXYPS\nONPOS\ncontents\nDesign"}
{"Headers": "View Limits", "Content": "The VIEW element attribute controlling whether the View limits are locked to the view frame is VFLIIND ('View Frame Limits Independent'). The default is TRUE, in common with historic VIEW behavior. Setting the attribute to FALSE unlocks the frame from the view limits (attribute VWLIMITS) so they can be manipulated independently. To avoid confusion, note that the sense of the VFLIIND attribute is the reverse of the view property \"Limits locked to frame\" in the user interface (ie \"Limits locked to frame\" false is implied by VFLIIND TRUE and vice-versa).\nThe VWLIMITS physical attribute on the VIEW can be set manually using the following example syntax:\nThe VWLIMITS attribute should not be confused with the read-only VLIMITS pseudo attribute.\nQ VLIMITS\nWhen a view frame is larger than the view limits, the expected behavior is for all Model elements within or overlapping the limits box to displayed in their entirety (up to the view frame and of course only as determined by the view's Idlist). Model elements entirely outside the view limits will not be displayed. If the user requires Model elements that overlap the view limits to be clipped to the view limits it is necessary to apply clipping planes, as is normal to achieve any clipping inside the view frame.\nVwlimits From E 1500mm S 2001mm U 1285mm To E 15465mm N 18500mm U 23962mm\nNote:\nThe VWLIMITS attribute is ignored if VFLIIND is FALSE as the view limits are then calculated from the view frame. If VFLIIND is TRUE.\n\n\n\nNote\n:\nQ VLIMITS"}
{"Headers": "View Scale", "Content": "VSCA controls the scale of the VIEW contents. The scale is normally set automatically to a value which makes sure that the VIEW contents fit comfortably within the VIEW boundary (refer to Additional AUTO Commands for further information), but can be changed if necessary, for example,\nThe larger the VSCA value, the larger the display of objects.\nVIEW scale can be expressed in terms of a ratio using the VRAT (VIEW Ratio) attribute, for example:\nTwo positive values must be specified but the TO can be omitted. Setting VRAT recalculates the existing VIEW scale (VSCA attribute). Setting VSCA directly defines VRAT as unset. The AUTO command calculates and sets VSCA directly and defines VRAT as unset.\nCare must be taken when changing VSCA, as it is easy to move the VIEW contents over the VIEW frame. The AUTO command takes the ONPOS value into consideration when it calculates the VSCALE.\nVSCA 0.05\n\n\n\nAdditional AUTO Commands\nVSCA\nAdditional AUTO Commands\nVRAT\nVRAT 1 TO 75\nVRAT 1/16in TO 1ft"}
{"Headers": "Orientation of View Contents", "Content": "ADEG controls the orientation of the VIEW contents. The attribute has a default value of 0, and can be set to any angle. ADEG can be set directly or by using the TURN command, for example:\nA positive value results in an anticlockwise rotation.\n\nNote that the degree of rotation produced is relative to an ADEG value of 0, not to the last value of ADEG.\nVarying RCOD (rotation code) produces a similar effect to varying ADEG, except that the VIEW is rotated as well. RCOD can be set to UP, DOWN, LEFT or RIGHT, corresponding to the direction of the \u2018top\u2019 of the VIEW region relative to the top of the screen. Default is UP.\nTURN 60\nADEG -120\n\n\n\nADEG\nnot\nRCOD"}
{"Headers": "Perspective", "Content": "PERS (perspective) can be used to give a perspective projection, the value taken by the PERS attribute being related to the view angle. The default value of 0 gives a parallel projection, which is the normal setting for drawings. If PERS is changed, an UPDATE Design command must be given to change the picture.\n\n\n\nPERS\nDesign"}
{"Headers": "3D View", "Content": "A 3D View can be generated from a 2D View using the GENERATE MODEL command. The view can be amended using the user interface. Elements can be added using the DESADD command. Refer to Add Elements to 3D View for further information.\n\n\n\nAdd Elements to 3D View\nAdd Elements to 3D View"}
{"Headers": "Look Direction", "Content": "The View\u2019s line of sight is fully defined by any two of:\nwhich are defined by the attributes DIR, THPO and FRPO. Setting one of these unsets one of the other two, assuming they are both already set.\nDIR (Direction) specifies the Looking Direction, down by default. The attribute is set by commands, for example:\nNote that the picture produced by changing the Looking Direction does not necessarily fit into the VIEW frame.\nThe THPO (Through Point) attribute is set to the Design coordinates corresponding to the centre of interest of the view. These are calculated automatically from the VIEW\u2019s related Id List by the AUTO command.\nFRPO (the From Point) is the position (in Design coordinates) at which the observer is deemed to be.\nThe Through Point and From Point can be set explicitly by commands, for example:\nChanging the Direction, Through Point or From Point makes the existing VIEW graphics out of date, so this must be updated by typing\nbefore any change in the picture is seen.\nThe 3D view direction equivalent to 2D Sheet direction can be queried using\nFor example, in a plan VIEW with RCODE UP (the default), then the query\ngives:\nHowever, for a plan VIEW with RCODE LEFT, the result is:\nand for a plan VIEW with ADEG 120 (and RCODE UP) the result is:\nLOOK E\nLOOK N45W\nISO3\nPLAN\nDRAELEVATION N\nIR D\nLOOK THROUGH N53426 W632764 U2125\nLOOK FROM N53426 W632764 U2125\nFRPO N125671 E67342 U11254\nTHPO N125671 E67342 U11254\nUPDATE DESIGN\nQ VIEWDIR LEFT\nViewdirection Left W\nViewdirection Left N\nViewdirection Left E 30 N\nLooking Direction\nFrom Point\nThrough Point\nLooking Direction\nLooking Direction\nFrom Point\nFrom Point\nThrough Point\nThrough Point\n\n\n\nDIR\nTHPO\nFRPO\n3D view direction\nQuery VIEWDIRection \n<sheet-dir>\n<sheet-dir>"}
{"Headers": "Representation Ruleset Reference", "Content": "The RRSF (Representation Ruleset Reference) attribute refers to elements that control the representation style to be used. Refer to Representation Rules for further information.\n\n\n\nRepresentation Rules\nRRSF\nRepresentation Rules"}
{"Headers": "Hatching Ruleset Reference", "Content": "The HRSF (Hatching Ruleset Reference) attribute refers to elements that control the representation style to be used for hatching. Refer to Automatic Hatching for further information.\n\n\n\nAutomatic Hatching\nHRSF\nAutomatic Hatching"}
{"Headers": "Change Ruleset Reference", "Content": "The CRSF (Change Ruleset Reference) attribute refers to elements that control the representation styles to be used for changed design items and annotations. Refer to Change Highlighting for further information.\n\n\n\nChange Highlighting\nCRSF\nChange Highlighting"}
{"Headers": "Arc Tolerance", "Content": "The ATOL attribute controls the Arc Tolerance (the difference between the true and the facetted representation of curves) of the graphical output for the VIEW, being set in units of hundredths of a millimeter on the drawing. (Default value 15.)\n\n\n\nATOL"}
{"Headers": "View Gap Length", "Content": "The VGAP attribute allows you to define the size of the gap that Draw inserts in View lines where they are crossed by non-solid primitives. For example, Plines or centrelines. The default value is 1.5mm.\n\n\n\nVGAP\nDraw"}
{"Headers": "Suppress View Clipping", "Content": "By default the Design graphics are clipped by the View frame. However it is possible to prevent this happening by setting the View's NOCLIP attribute to TRUE. (The default value is FALSE). After changing the NOCLIP attribute an UPDATE DESIGN is required.\n\n\n\nNOCLIP\nNOCLIP"}
{"Headers": "Ignore the DUNION attribute", "Content": "Use of the DUNION attribute on DESIGN elements, for example, FRMW or STRU is described. Refer to Controlling Edge Representation in DRAW for further information. The DUNION values are used during an UPDATE DESIGN process to determine whether common edges between FRMWs are drawn or omitted. However it is possible to ignore all DUNION values by setting the View's IGNDUN attribute (Ignore Dunion) to TRUE. (The default value is FALSE). After changing the IGNDUN attribute an UPDATE DESIGN is required.\n\n\n\nControlling Edge Representation in DRAW\nControlling Edge Representation in DRAW\nIGNDUN\nIGNDUN"}
{"Headers": "Additional AUTO Commands", "Content": "Previous sections have described the use of the two AUTO commands to add Design elements to Views and to define their THPO and VSCA or SIZE. There are two other uses of AUTOSCALE and AUTOSIZE:\nThe VIEW's VSCA and THPO attributes are calculated using only the LIMI attribute of the specified Id List, ignoring any Design items. If the Id List name is omitted the Id List referenced by the VIEW is assumed. Using AUTOSIZE calculates the VIEW's SIZE and THPO attributes.\nThe VIEW's SIZE and THPO attributes are calculated from the box defined by the two 3D coordinates given. The position can be specified using the cursor (3D point or p-point), explicit p-point reference, origin of a named element, or an explicit 3D coordinate. Using AUTOSCALE calculates the VIEW's VSCA and THPO attributes.\nAUTOSCALE LIMITS OF /idlist_name\nAUTOSIZE FROM position TO position\n\n\n"}
{"Headers": "Hidden Line Representation", "Content": "The VTYP (view type) command controls the hidden-line representation of pictures. Six possible VTYP settings are provided. These give progressively greater graphical accuracy at the expense of increasing processing requirements. The facility allows you to produce preliminary and intermediate drawings (where graphical accuracy can be of secondary importance) quickly, leaving only finished drawings to incur the greatest processing overhead. The default VTYP setting is WIRELINE, which gives a conventional wireline picture.\n\nModelled Wireline representation gives slightly greater realism by blending the intersection of primitives, but without incurring the computational overheads of removing hidden lines.\n\nWireline Hidden Line Removed representation produces a View where hidden lines are removed from individual significant elements (EQUI or SUBS) but not from items hidden behind them.\n\nLocal Hidden Line representation gives a picture where hidden lines are removed from individual significant elements (EQUI or SUBS), but not from items hidden behind them.\nThe representation differs from Wireline Hidden Lines Removed because individual significant elements are properly modelled so that intersections between primitives and holes display correctly.\n\nGlobal Hidden Line representation gives a picture where all hidden lines are removed.\n\nUniversal representation gives a picture where all hidden lines are removed (as in Global HLR), but in addition intersection lines between clashing significant elements (for example, EQUI and STRU or SUBS and SUBS) are generated. Whether you need to use this View type depends on the way in which you have created the 3D model. The need for VTYP UNIVERSAL is greater if the 3D model is composed of a large number of significant elements each with a small number of primitives, rather than vice versa. It is also more likely to be needed in non-orthogonal Views, where missing intersection lines are most noticeable.\n\nAlternative methods of setting VTYP are:\nVTYP WIRE\nwireline (default)\nVTYP MWIR\nmodelled wireline\nVTYP WIREHL\nwireline with hidden lines removed\nVTYP LOCAL\nlocal hidden lines removed\nVTYP GLOBAL\nglobal hidden lines removed\nVTYP UNIV\nglobal hidden lines removed and intersection lines generated\nVTYP WIRE\nwireline (default)\nVTYP MWIR\nmodelled wireline\nVTYP WIREHL\nwireline with hidden lines removed\nVTYP LOCAL\nlocal hidden lines removed\nVTYP GLOBAL\nglobal hidden lines removed\nVTYP UNIV\nglobal hidden lines removed and intersection lines generated\n\nVTYP WIRE\nwireline (default)\nVTYP MWIR\nmodelled wireline\nVTYP WIREHL\nwireline with hidden lines removed\nVTYP LOCAL\nlocal hidden lines removed\nVTYP GLOBAL\nglobal hidden lines removed\nVTYP UNIV\nglobal hidden lines removed and intersection lines generated\n\n\n\nVTYP\nWireline Hidden Line Removed\nLocal Hidden Line\nGlobal Hidden Line\nGlobal\nVTYP WIRE\nVTYP MWIR\nVTYP WIREHL\nVTYP LOCAL\nVTYP GLOBAL\nVTYP UNIV"}
{"Headers": "2D Symbolic Representation", "Content": "Draw allows design elements to be represented symbolically in a 2D View when the UPDATE Design command is executed. Symbolic representation can either replace or be in addition to the normal geometric representation of the elements.\nDesign symbols can consist of geometrical elements or text or can be a combination of both, including Draw Intelligent Text hash-codes. Design symbols can be scaled and oriented as required.\nGraphic representation of design elements are controlled by Representation Rules. Refer to Representation Rules for further information.\nThe 2D symbols are generated from templates stored in the Draw database. These are the Symbol Templates (SYTM) and the Text Label Templates (TXTM), used for generation of geometric elements or text elements, respectively. Refer to Basic Hierarchy for a diagram of the Draw database hierarchy.\nThe data defining which templates to use for a given design element, and under which circumstances, is stored in the Catalogue database. Several templates can be associated with a design element so that it can be represented differently in different types of Views. The representation of a light fitting, for example, can depend on both the View direction (for example, plan or elevation) and the View classification (for example, Room Design or Cabling).\nThe design symbols are created as Design Symbol (DESSYM) database elements. DESSYM is a soft-type variant of the Special Label (SLAB) element. The DESSYM elements are added as members of a Design Symbol Layer (DSLAYE) element, which is a soft-type variant of the Layer (LAYE) element, and is therefore a member of a View. Only one occurrence of DSLAYE is created per View during the UPDATE Design process, the DSLAYE is removed if it subsequently ceases to own any child DESSYMs.\n2D symbols are created as part of the annotation of the View, rather than design graphics. DSLAYEs and DESSYMs are created and deleted automatically by Draw, with no user control over these operations.\nDESSYMs are not created for any design item whose origin falls outside the View rectangle or whose origin (or datum point) is excluded by the action of section planes.\nWhere only a symbolic representation is required (for example, when a normal geometric representation is not required in addition to design symbols), Draw does not attempt to determine whether the design items are hidden by the action of the Hidden Line Removal process.\n\n\n\nRepresentation Rules\nBasic Hierarchy\nDraw\nDesign\nDraw\nRepresentation Rules\nRepresentation Rules\nDraw\nBasic Hierarchy\nDraw\nDesign\nDraw\nDraw"}
{"Headers": "Scale Design Symbols", "Content": "2D symbols can be specified as scaled or non-scaled. The size of a scaled symbol depends upon the View Scale (VSCA attribute of the View), and is therefore changed correspondingly when the View Scale changes (and after an UPDATE Design command). Non-scaled symbols are a fixed size, irrespective of View Scale and paper size. The Scaling Flag (SCALFG) of a design element has the value 1 when the design symbol can be scaled within a view and zero it is non-scaled.\nFor non-scaled design symbols which reference a symbol template (SYTM), the array elements of the XY scaling (XYSC) attribute of the design symbol are set equal to the NSIZE attribute of the referenced SYTM.\nFor a scaled design symbol which references an SYTM, the actual size on the sheet depends on the View Scale. The NSIZE attribute is used to scale the symbol to its actual size on the sheet and, by setting the array elements of the XYSC attribute equal to the VSCALE attribute of the View, this adjusts the symbol to the appropriate size for the View (uniform scaling).\nSetting X and Y scaling factors of XYSC independently on the Design Symbol Link (DRSYLK) element enables non-uniform scaling of the design symbol. The design symbol (DESSYM) held in the PADD database can be scaled to the correct size for the design element that it is intended to replace in the Draw View, regardless of the aspect ratio of that design element.\n\n\n\nscaled\nnon-scaled\nDesign\nuniform scaling\nnon-uniform scaling\nDraw"}
{"Headers": "Orientate Design Symbols", "Content": "The correct orientation of a DESSYM in a Draw View is obtained by copying the value of the P-point Direction (PPDI) attribute from the Symbol Template (SYTM) or Text Label Template (TXTM) to the PPDI attribute of the DESSYM. The 2D Symbology functionality to uses the direction of the P-point, which is determined by the P-point direction (PTCD) attribute on the P-point element, to align the X-axis of the SYTM or TXTM.\nSYTMs and TXTMs are created and modified in Draw Administration Mode. In addition the administrator must associate the SYTM and TXTM with orientation of the component in the Catalogue that the DESSYM represents. You can either select an existing P-point on the Catalogue component, or create a new P-point. Then the value of the PPDI attribute on the SYTM or TXTM is set to the value of the P-point Number (%NUM) attribute on the Catalogue component.\n\n\n\nDraw\nDraw"}
{"Headers": "Query View Contents", "Content": "You can query which Design elements are visible in a specified Draw View using the Q VSCAN command. For example:\nThe IN view_id can be omitted if your current database position is at or below a View.\nYou can:\nIn the examples, design_id must refer to a Design significant element, which is EQUI, SUBE, STRU, SUBS, FRMW, SBFR, TMPL, BRAN, or HANG.\nDraw determines whether design items are visible by scanning the data in the picture, not by scanning the IDList. Thus elements hidden by the hidden-line-removal process are not found. The command cannot determine how much of the element is visible.\nQ VSCAN <SIGNIFICANT | design_id> <IN view_id> <FOR selection_criteria>\n   \nRequest a list of all significant elements that are visible in a View.\nQ VSCAN SIGNIFicant IN view_id\nFor example:\nQ VSCAN SIGNIF IN /VIEW-01\nSpecify a significant design element and request a list of all its primitives that are visible in a View.\nQ VSCAN design_id IN view_id\nFor example:\nQ VSCAN /PIPE100-B-1-B1\nSpecify selection criteria to determine matching design elements visible in a View.\nQ VSCAN IN view_id FOR selection_criteria\nFor example:\nQ VSCAN FOR ALL (VALVE VTWAY VFWAY) WITH (ABOR GE 50)\nQ VSCAN FOR SCTN EXCL WITHIN E 800mm N 750mm U 638mm To E 900mm N 850mm U 738mm\nRequest a list of all significant elements that are visible in a View.\nQ VSCAN SIGNIFicant IN view_id\nFor example:\nQ VSCAN SIGNIF IN /VIEW-01\nRequest a list of all significant elements that are visible in a View.\nSpecify a significant design element and request a list of all its primitives that are visible in a View.\nQ VSCAN design_id IN view_id\nFor example:\nQ VSCAN /PIPE100-B-1-B1\nSpecify a significant design element and request a list of all its primitives that are visible in a View.\nSpecify selection criteria to determine matching design elements visible in a View.\nQ VSCAN IN view_id FOR selection_criteria\nFor example:\nQ VSCAN FOR ALL (VALVE VTWAY VFWAY) WITH (ABOR GE 50)\nQ VSCAN FOR SCTN EXCL WITHIN E 800mm N 750mm U 638mm To E 900mm N 850mm U 738mm\nSpecify selection criteria to determine matching design elements visible in a View.\nNote: It is possible but not recommended to enter the syntax:\nQ VSCAN FOR SCTN WITHIN <volume> IN CE\nIn this case the \"IN forms part of the generic selection criteria syntax (equivalent to \"WRT CE\") and is unlikely to be what is intended. The results may be very different from the probable intent of syntax, for example:\nQ VSCAN IN CE FOR SCTN WITHIN <volume>\nNote: A significant Design element is not found in a View if it only owns other significant elements. It must own visible primitives. The EQUI, STRU and FRMW elements are affected; they are not found unless they own visible primitives.\n\n\n\nDraw\nQ VSCAN\n \n \n \n \n \n \n \n \nview_id\nQ VSCAN SIGNIFicant IN \nview_id\nQ VSCAN SIGNIF IN /VIEW-01\nQ VSCAN \ndesign_id\n IN \nview_id\nQ VSCAN /PIPE100-B-1-B1\nQ VSCAN IN \nview_id\n FOR \nselection_criteria\nQ VSCAN FOR ALL (VALVE VTWAY VFWAY) WITH (ABOR GE 50)\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \ndesign_id\nNote\n:\nQ VSCAN FOR SCTN WITHIN <volume> IN CE\nQ VSCAN IN CE FOR SCTN WITHIN <volume>\nDraw\nNote\n:"}
{"Headers": "Query Element Appearance in a View", "Content": "You can query whether low-level design elements and their owners display in a given View using the command:\nwhere gid is the general identifier of the element and view is the view identifier. For example:\nThe view identifier can be omitted if it is the current element. For example:\nPossible answers are:\nQ FIND /BOX99 IN /SH1/V1\nQ FIND /VESS-05 IN VIEW\nQ FIND ILEAVE TUBE OF /VALVE-24 IN /VIEW/02\nQ FIND /BRANCH-01\nFOUND\nMISSING\nINVALID ELEMENT\nNote: A significant Design element is not found in a View if it only owns other significant elements. It must own visible primitives. The EQUI, STRU and FRMW elements are affected; they are not found unless they own visible primitives.\n\n\n\nQ FIND \ngid\n IN \nview\ngid\nview\nNote\n:"}
{"Headers": "Query the Nearest Side to an Item", "Content": "You can query the nearest side of a View to a given P-point, proportional distance along a P-line, or origin of a Design element in the current View using the command:\nFor example:\nThe ROTATED option allows the rotation (for example, the VIEW\u2019s RCOD attribute) to be considered if required.\nThe response is the nearest and next-nearest sides, and also whether the item is inside or outside the View. For example, Point 1 is LEFT UP OUTSIDE.\n\nQ VSIDE OF /VESS-99\nQ VSIDE OF PPO2 OF /VALVE-100\nQ VSIDE OF PPLINE TOS OF /SCTN-101 START\nQ VSIDE OF PPLINE MEML OF /SCTN-101 PROP 0.5\n\n\n\nQ VSIDE [ROTated] OF\n 3d_point_definition"}
{"Headers": "Highlighting Components in the Designs", "Content": "Keywords\nHIGHLIGHT UNHIGHLIGHT SOLELY IN\nDescription\nThis facility lets you highlight elements on a sheet.\nThe SOLELY keyword clears all previous highlighting before highlighting the defined components.\nDesign geometry must be highlighted in a specific view. This defaults to the current owner but can be overridden with the IN keyword.\nHIGHLIGHT CE\nHighlight the current element in the current view.\nHIGHLIGHT IN /VIEW1 EQUI1\nHighlight EQUI1 in VIEW1.\nHIGHLIGHT SOLELY CE ALL STRA\nHighlight only the current element and all STRA components.\nUNHIGHLIGHT\nClear highlight on all elements.\nHIGHLIGHT CE\nHighlight the current element in the current view.\nHIGHLIGHT IN /VIEW1 EQUI1\nHighlight EQUI1 in VIEW1.\nHIGHLIGHT SOLELY CE ALL STRA\nHighlight only the current element and all STRA components.\nUNHIGHLIGHT\nClear highlight on all elements.\nCommand Syntax\nHIGHLIGHT CE\nHighlight the current element in the current view.\nHIGHLIGHT IN /VIEW1 EQUI1\nHighlight EQUI1 in VIEW1.\nHIGHLIGHT SOLELY CE ALL STRA\nHighlight only the current element and all STRA components.\nUNHIGHLIGHT\nClear highlight on all elements.\n\n\n\nKeywords\nDescription\nExamples\nHIGHLIGHT CE\nHIGHLIGHT IN /VIEW1 EQUI1\nHIGHLIGHT SOLELY CE ALL STRA\nUNHIGHLIGHT\nCommand Syntax\n>-- HIGHLIGHT --+- IN <gid> -.\n                |            |\n                \u2018------------+- SOLELY -.              .------<-------.\n                             |          |              |              |\n                             \u2018----------+-- <selatt> --+-- <selatt> --+-->\n>-- UNHIGHLIGHT --+------<-------.\n                  |              |\n                  \u2018-- <selatt> --+-->"}
{"Headers": "Design Templates", "Content": "This chapter explains the concept of Design Templates, which lets the user create and store standard design configurations for subsequent use, and the Design Datasets which hold the parameterized data settings for such templates.\n\n\n"}
{"Headers": "Concepts", "Content": "A design template is a set of design primitives, panels and nozzles that may be grouped together and then referenced from within another part of the Design database as though it were a single item. In many ways, a design template behaves in a similar way to a Catalog component, except that the template items are stored in a special area of the Design DB, rather than in a separate Catalog Database (DB), and they can use the more powerful sets of primitives and parameterization facilities available from within Model. Unlike a Catalog component, a design template can be split down into its constituent parts for selective reporting, dimensioning, MTO, etc.\nA design template is used in a design by creating an instance of the template. When a design template is instanced, the template contents are copied into the Design hierarchy and a reference is set to the original template definition. At this release version, a design template may only be copied under a Panel Fitting, a Section Fitting or a Primary Joint. A design element cannot own more than one design template, nor can one design template own another template.\nDesign templates may be parameterized to allow a single template definition to be used in different circumstances. The parameterization facilities use Design Datasets to store named parameters, which may then be referenced in geometric and p-point definitions. The value assigned to a parameter can be defined in terms of a rule by using any of the standard expression syntax.\nNote:\nThe definition of Design Templates is likely to be done by the person who organizes Catalog and Specification data in a company, while the use of Design Templates for building up a design model will be carried out by a Plant designer. Therefore, although both functions are carried out in Model, this chapter is relevant to two different types of user.\n\n\n\ninstance\nNote\n:"}
{"Headers": "Design Template Hierarchy", "Content": "Design Template (TMPL) elements are usually stored in a separate Design DB under an administrative Template World (TPWL) , which is itself divided into administrative Template Areas (TMAR) .\nEach TMPL is initially created as a copy of an existing set of design elements which have been created in a part of the usual hierarchy below a SITE. The TMPL may then be modified by the addition of positive and/or negative primitives, negative extrusions, etc. For example, a very simple template, consisting of a positive box and a negative box, could be created thus:\n\nWhen this template is instanced in a design model, say under a panel fitting, its constituent elements are copied back and all parameterization rules are executed so that the attributes of the copy are set to suit the local Model requirements, thus:\n\nAll attributes of the copy are locked to prevent unintentional changes.\n\n\n\nDesign Template\nTemplate World\nTemplate Areas"}
{"Headers": "Control of Negative Primitive Application", "Content": "Negatives owned by positive primitives directly under a Template, or deeper in the component hierarchy behave as normal design primitives in that they are removed from their owner's geometry to create holes and notches.\nA Template can also directly own negatives, which, in isolation, have nothing to be applied to. These negatives act in the same way as negatives within Negative Geometry sets in the Catalog database. Together these apply to the template geometry as a whole, or the geometry of other associated items in the context of the element whose geometry is defined by the template. For example a joint can be defined by a Catalog item, or a template, and both need to be able to modify the geometry of an attached section element (SCTN or GENSEC) and/or the geometry of the beam element on which the joint has been welded or bolted.\nTo determine the behaviour of these negative geometry elements each has a Negative Application attribute (NAPP). Refer to Negative Geometry Sets in the Catalog and Specification Reference manual for further information.\nKey values of NAPP are:\n0\nNegative Primitive will not be removed from anything.\n1\nNegative Primitive will be removed from the item Attached to the owner of the Template geometry. The template user will be a joint type element (SJOI,SUBJ,FIXING etc), and the attached elements will be either a SCTN or a GENSEC\n2\nNegative Primitive will be removed from its 'significant' Owner or hierarchical owner. The template user will be a Fitting (FITT, PFIT, FIXING, SBFI etc.) and the hierarchical owner will be a PANEL, SCTN or GENSEC.\n4\nNegative Primitive will be removed from the item using the Template itself. This item could be any type of element. In the case of FIXINGs subsidiary to other fixings, both the subsidiary and owning compound fixing will be operated on as the item itself.\n0\nNegative Primitive will not be removed from anything.\n1\nNegative Primitive will be removed from the item Attached to the owner of the Template geometry. The template user will be a joint type element (SJOI,SUBJ,FIXING etc), and the attached elements will be either a SCTN or a GENSEC\n2\nNegative Primitive will be removed from its 'significant' Owner or hierarchical owner. The template user will be a Fitting (FITT, PFIT, FIXING, SBFI etc.) and the hierarchical owner will be a PANEL, SCTN or GENSEC.\n4\nNegative Primitive will be removed from the item using the Template itself. This item could be any type of element. In the case of FIXINGs subsidiary to other fixings, both the subsidiary and owning compound fixing will be operated on as the item itself.\nOther values of NAPP are allowed and will be additions of 1, 2 and 4 to allow the negative primitive to operate on any combination of attached, owner and itself.\n0\nNegative Primitive will not be removed from anything.\n1\nNegative Primitive will be removed from the item Attached to the owner of the Template geometry. The template user will be a joint type element (SJOI,SUBJ,FIXING etc), and the attached elements will be either a SCTN or a GENSEC\n2\nNegative Primitive will be removed from its 'significant' Owner or hierarchical owner. The template user will be a Fitting (FITT, PFIT, FIXING, SBFI etc.) and the hierarchical owner will be a PANEL, SCTN or GENSEC.\n4\nNegative Primitive will be removed from the item using the Template itself. This item could be any type of element. In the case of FIXINGs subsidiary to other fixings, both the subsidiary and owning compound fixing will be operated on as the item itself.\n\n\n"}
{"Headers": "Application Data Areas", "Content": "Application Data Areas and Elements are a new form of definition in the Design Database that are provided to assist Appware Applications to store model parts for copying and propagation within a design. They have some similarities with Templates, but are more general in content, and more restrictive in behaviour.\nApplication Data Areas and Elements are expected to be used for Piping Assemblies and Platforms Stairs and Ladders (PSL) applications and perhaps others. They are also expected to be used for storing Supports definitions to make the management of these more robust.\nThe Elements available are administrative elements allowing applications to organize 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 etc. They are similar to Catalog definitions and to Template definitions in particular.\nThe top level element in the Model database is Design WORL. This owns a top level application data element\nAPPLDWorld\n- Application Data World\nAPPLDW can own\nAPPDAReas\n- Application Data Areas\nDDAR\n- Design Data Set Areas\nAPPLDWorld\n- Application Data World\n\n\n\nAPPLDW can own\n\nAPPDAReas\n- Application Data Areas\n\nDDAR\n- Design Data Set Areas\nDDARs are existing element types. They own Design Data Sets (DDSE) for storage of data used by Template expressions and Rules, and by Appware. They can be used for Appware to store data, rules, etc for use in data driven instancing of assemblies.\nAPPDAR can own:\nAPPLDAta - Application Data. This is logically similar to a Template Definition.\nAPPLDA is a new element type. It can own\nZONE\nDDSE\n- Design Dataset\nDPSE\n- Design Pointset\nROOM\nAPPDAR can own:\n\n\nAPPLDAta - Application Data. This is logically similar to a Template Definition.\n\n\nAPPLDA is a new element type. It can own\n\nZONE\n\n\nDDSE\n- Design Dataset\n\nDPSE\n- Design Pointset\n\nROOM\n\nThe following diagram illustrates the relative positions of these elements in the Model database hierarchy:\n\nAPPLDWorld\n- Application Data World\nAPPLDW can own\nAPPDAReas\n- Application Data Areas\nDDAR\n- Design Data Set Areas\nAPPDAR can own:\nAPPLDAta - Application Data. This is logically similar to a Template Definition.\nAPPLDA is a new element type. It can own\nZONE\nDDSE\n- Design Dataset\nDPSE\n- Design Pointset\nROOM\n\n\n\nAPPLDWorld\nAPPLDAta"}
{"Headers": "Functional Queries", "Content": "Everything under the Application Data World (APPLDWorld) is treated in the same way that hierarchies under Template Worlds (TMWL) are. In particular, Clash checking on command, spatial mapping and auto clashing will be isolated from normal design data except when specifically queried within the APPLDWorld.\n\n\n"}
{"Headers": "Naming", "Content": "Names in the APPLDWorld are in the same scope as the normal project model and so duplicate names will clash. This is not likely to be an issue as it is expected that application data will be unnamed. It would become an issue if sections of 'real' model data are copied or included (moved) into the APPLDWorld.\nAPPLDA elements have a local name scope so that objects that the APPLDA owns can have local names, allowing any Appware manager that manipulates Application Data to easily identify elements within them in the same way that design templates (TMPLates) are handled. Existing commands and expression functions such as LNAME, LNID etc operate within this scope.\n\n\n"}
{"Headers": "Application Data and Templates", "Content": "A template (TMPLate) can be included in the Application Data World, but only as an instanced template, NOT a template definition. Such templates can be refreshed from their definitions using existing (appware and core) driven functions. However, there is no core supported means to refresh copies of Application Data in the real model.\n\n\n"}
{"Headers": "Extension to Design Data", "Content": "DDAT elements have a new attribute PTOLER that provides a tolerance value as an alternative to the MAXMIN values which determine the range of valid values when set. Applications using the Application Data will use this value to validate its data.\n\n\n"}
{"Headers": "Valid Value Elements Additional Attribute", "Content": "Valid Value elements (VVALUE) owned by a DDAT can have a Valid Rule set stored in the attribute VALRULE. VALRULE is an expression attribute that can store an expression that evaluates to a logical true or false value. If the expression does not evaluate to a logical result, or if there are errors in the evaluation of the expression, then the VALRULE will return FALSE when queried. The VVALUE element owns a Valid Value attribute (VALIDV) that is an expression returning a real, logical, text or reference value which supports the owning DDAT element. If the VALRULE is true, or if it is a null expression, then this VALIDV will be available to the DDAT.\nVALRULEs are used by the system to control the choice of a Valid Value when property queries are made on the owning DDAT.\nFor example a DDAT element might own four VVALUE elements with VALIDV and VALRULE attributes as follows:\nVVALUE 1\n( ID /ANG35x35x15 )\n( LDPR LENG le 1800 )\nVVALUE 2\n( ID /ANG40x40x15 )\n( LDPR LENG gt 1800 and LDPR LENG le 2400 )\nVVALUE 3\n( ID /ANG45x45x18 )\n( LDPR LENG gt 2400 and LDPR LENG le 3000 )\nVVALUE 4\n( ID /ANG50x50x18 )\n( LDPR LENG gt 3000 )\nThe 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 evaluation generate errors.\nVValue\nVALIDValue expression\nVALRULE expression\nVVALUE 1\n( ID /ANG35x35x15 )\n( LDPR LENG le 1800 )\nVVALUE 2\n( ID /ANG40x40x15 )\n( LDPR LENG gt 1800 and LDPR LENG le 2400 )\nVVALUE 3\n( ID /ANG45x45x18 )\n( LDPR LENG gt 2400 and LDPR LENG le 3000 )\nVVALUE 4\n( ID /ANG50x50x18 )\n( LDPR LENG gt 3000 )\n\n\n"}
{"Headers": "Extension to Design Data Associated Pseudo Attributes", "Content": "Local Design Data Set (DDSE) pseudo attributes DEPL, LDPR, DEPR, DEPD and LFDP (which up to release 12 only operated within the scope of the owner of a DDSE) now also operate at the DDSE level and within the scope of a DDSE:\nDEPL\nList of\nProperty keys\nProperties in all\nowned DDSE\nProperties in this\nDDSE\nProperties in owning\nDDSE\nLDPR\nReal value\nProperty in any owned DDSE\nProperty or\nDefault Property\nin any DDSE\nowned by owner\nof DDSE\nProperty in any\nDDSE owned by\nowner of owning\nDDSE\nDEPR\nText value for text and reals\n\n\n\nLFDP\nReference value\n\n\n\nDEPD\nText default\nvalue for text\nand reals\nDefault Property\nin any owned\nDDSE\n\nDefault Property in any DDSE owned by owner of DDSE\nAll attributes fail above the owner of the DDSE.\nAttribute\nReturns\nAt Owner of DDSE\nAt DDSE\nBelow a DDSE\n(DDAT, VVALUE etc)\nDEPL\nList of\nProperty keys\nProperties in all\nowned DDSE\nProperties in this\nDDSE\nProperties in owning\nDDSE\nLDPR\nReal value\nProperty in any owned DDSE\nProperty or\nDefault Property\nin any DDSE\nowned by owner\nof DDSE\nProperty in any\nDDSE owned by\nowner of owning\nDDSE\nDEPR\nText value for text and reals\nLFDP\nReference value\nDEPD\nText default\nvalue for text\nand reals\nDefault Property\nin any owned\nDDSE\nDefault Property in any DDSE owned by owner of DDSE\n\n\n"}
{"Headers": "Special Design Data Property names in scope of a DDSE", "Content": "Each of the Local Design Data pseudo attributes DEPL, LDPR, DEPR, DEPD and LFDP take a qualifier that is the key to a particular design data element (the DKEY of the DDAT). Special values of this key are used to query values within the DDAT and VVALUE elements:\nVALI:\nfor returning evaluation of the VALIDV attribute of a VVALUE\nVALR:\nfor returning the evaluation of a VALRUL attribute of a VVALUE\nVVAL:\nfor returning a VALIDV/ALUE result with a true VALRULE\nDDAT:\nfor returning the value of the local DDAT (either a DPROPerty or else a DDEFAUlt without knowing its DKEY\nVALI:\nfor returning evaluation of the VALIDV attribute of a VVALUE\nVALR:\nfor returning the evaluation of a VALRUL attribute of a VVALUE\nVVAL:\nfor returning a VALIDV/ALUE result with a true VALRULE\nDDAT:\nfor returning the value of the local DDAT (either a DPROPerty or else a DDEFAUlt without knowing its DKEY\nVALR\nERROR, no VALRUL attribute\nresult of evaluated VALRUL attribute\nVALI\nERROR, no VALIDV attribute\nresult of evaluated VALIDV attribute\nVVAL\nreturns VVAL result of first VVALUE element that does not ERROR,\nreturns result of evaluated VALIDV if VALRUL evaluates TRUE, else ERROR\nDDAT\nreturns the same value as would be returned using the DKEY of the DDAT. (Either the DPROPerty or DDEFAUlt value). This is a convenient way of obtaining this value without knowing the DKEY\nReturns the same value as the DDAT property of the owning DDAT without having to know the actual DKEY value to use.\nAll of these properties will error if queried at the DDSE element or above.\nIf the Design Data set actually has a data element that has a property with one of these name keys (they are not reserved in anyway) then the use of the key will operate normally on the DDSE or its owner, and as listed in the table above on a DDAT or VVALUE.\nUse of the VVAL key on a particular DDAT will return the first suitable value from a set of many values. This is similar to choosing from a set of values according to some criteria. It is possible to use this as an alternative to the IFTRUE expression, which can, for example when used iteratively, select a set of possible choices depending on a particular criterion. The IFTRUE expressions will increase the expression length with the possibility of exceeding the maximum length of the text attribute. Use of VVAL key will not do this.\nThe VVALUEs owned by a DDAT DO NOT modify the return values of design data properties when queried by their owners.\nIt should be noted that if the DPROPerty of a DDAT is inconsistent with the set of VVALUEs that it owns, this will NOT raise an exception or error when querying it directly using its DKEY. It is up to the application using these data values to decide whether to accept the value of a DPROPerty whenever it conflicts with valid values, or maximum or minimum values, or a tolerance. To do otherwise would risk the integrity of existing user and system applications.\nVALI:\nfor returning evaluation of the VALIDV attribute of a VVALUE\nVALR:\nfor returning the evaluation of a VALRUL attribute of a VVALUE\nVVAL:\nfor returning a VALIDV/ALUE result with a true VALRULE\nDDAT:\nfor returning the value of the local DDAT (either a DPROPerty or else a DDEFAUlt without knowing its DKEY\nelement special key word\nDDAT\nVVALUE\nVALR\nERROR, no VALRUL attribute\nresult of evaluated VALRUL attribute\nVALI\nERROR, no VALIDV attribute\nresult of evaluated VALIDV attribute\nVVAL\nreturns VVAL result of first VVALUE element that does not ERROR,\nreturns result of evaluated VALIDV if VALRUL evaluates TRUE, else ERROR\nDDAT\nreturns the same value as would be returned using the DKEY of the DDAT. (Either the DPROPerty or DDEFAUlt value). This is a convenient way of obtaining this value without knowing the DKEY\nReturns the same value as the DDAT property of the owning DDAT without having to know the actual DKEY value to use.\n\n\n"}
{"Headers": "Design Datasets", "Content": "Design Datasets (DDSE) are used to store the properties of design template items, which may then be used to define the template\u2019s parameters.\nEach property is stored in a Design Data (DDAT) element under a DDSE, with each DDAT being identified (and subsequently referenced) by a keyword or property name by a keyword held in its DKEY attribute.\nThe property definition can be specified by an expression held in the Design Data Property (DDPR) attribute, while a default value or expression for the property (which is used if the DDPR expression cannot be evaluated for any reason) can be stored in the Design Data Default (DDDF) attribute.\nUnlike a design reference to a Catalog component, which can access only a single Catalog dataset via its DTREF setting, a reference to a design template can access more than one design dataset.\nThe following diagram illustrates the relative positions of these types of dataset for a simple hierarchy:\n\nThe pseudo\u2011attributes available for accessing the properties data in the various types of dataset are as follows:\n\nMost commonly, a design attribute value will be defined in terms of a design property by using the Current Design Dataset Property (CDPR) attribute. The CDPR can also be used to define a property in one dataset in terms of a property in another dataset. When a CDPR is used in a rule for a component whose owner can own datasets, the current datasets will be those at the same level as the component: otherwise, the current datasets will be those under the first dataset-owning element above the component. When a CDPR is used in a property expression within a dataset, it refers to a property in the current dataset for the item at which CDPR is evaluated.\nWhen used in a querying command or in an expression (for example, when defining a parameterization rule), the attributes for a specific property are identified by the DKEY for that property. For example:\nQ CDPL\nLists all DKEYs for properties in current dataset.\nQ CDPR LENG\nGives value of LENG property in current dataset.\nRULE SET XLEN (CDPR LENG)\nSets rule for current element\u2019s XLEN attribute using value from LENG property in current dataset.\nQ CDPL\nLists all DKEYs for properties in current dataset.\nQ CDPR LENG\nGives value of LENG property in current dataset.\nRULE SET XLEN (CDPR LENG)\nSets rule for current element\u2019s XLEN attribute using value from LENG property in current dataset.\nQ CDPL\nLists all DKEYs for properties in current dataset.\nQ CDPR LENG\nGives value of LENG property in current dataset.\nRULE SET XLEN (CDPR LENG)\nSets rule for current element\u2019s XLEN attribute using value from LENG property in current dataset.\nA local design dataset is owned directly by the current element,\nA template design dataset is owned by the first template below the current element, and\nA current design dataset is at the same level as the current element and has the same owner.\nA local design dataset is owned directly by the current element,\nA local design dataset is owned directly by the current element,\nA template design dataset is owned by the first template below the current element, and\nA template design dataset is owned by the first template below the current element, and\nA current design dataset is at the same level as the current element and has the same owner.\nA current design dataset is at the same level as the current element and has the same owner.\nNote:\nThe dataset attributes PRLS, PROP and PRDE are also used to refer to Catalog dataset properties. To query any of these attributes, a search for a Catalog dataset will be made first; if this fails, a search for a design template dataset will be made.\nNote:\nUsually default values are assigned to properties, which are then used to evaluate expressions during the creation of a design template. Which allows the user to see the template geometry in a graphical view, at a practical scale, as defined. Thus a default value for LENG in the last example would allow a sensible XLEN dimension to be evaluated from the rule for display purposes. When instanced in a design, the value of the LENG property would be derived from, say, a design parameter and the rule would be re\u2011executed to give the correct XLEN.\n\n\n\nDesign Datasets\nDesign Data\nDKEY\n\nDDPR\nDDDF\nA local design dataset\nA\ntemplate design dataset\nA current design dataset\nNote\n:\nQ CDPL\nQ CDPR LENG\nRULE SET XLEN (CDPR LENG)\nNote\n:"}
{"Headers": "Type of Property", "Content": "The data property can return\nand the DDPR expression should evaluate to one of these values. So should the DDDF and VALIDV attributes of any owned VVALUE of the property (DDAT).\nWhichever type of value is expected is determined by the pseudo attribute used to access the data property. There are different attributes for each type, and for each of local, template, or current design properties as is described below.\nThe PTYP attribute of the DDAT element can be set to a WORD value (4-6 uppercase alphabetic characters) to signify the type of data stored or evaluated in the property. For text and reference properties this is not essential information but it may be used by applications using the properties. For example it sometimes might have PTYP set to SPRE.\nWhen the property returns a real value its PTYP attribute is important. It should be set to the type of physical quantity being returned. Its common values are:\nNONE\n-\na pure numeric, not a physical property\nDIST\n-\na Distance or Length property\nBORE\n-\na size of BORE property\nDATA or ANY\n-\nany physical property so that any checking for consistency is met and no warning issued.\nNONE\n-\na pure numeric, not a physical property\nDIST\n-\na Distance or Length property\nBORE\n-\na size of BORE property\nDATA or ANY\n-\nany physical property so that any checking for consistency is met and no warning issued.\nIn addition any standard hashcode for a supported physical quantity (dimension) can be used (MASS, ANGL, TEMP etc.) No checks are made for validity since the PTYP can be used by applications for their own needs. Any WORD not recognized is treated as NONE.\nThe PTYP can also be set to a generic dimension by setting the attribute to a compound unit value of such a dimension (a value has to be supplied for syntax purposes).\nThe DDPR and DDDF and VALIDValue expressions should all evaluate to a quantity whose dimension is the same or equivalent to the PTYPE\nis suitable for a DDAT whose PTYP is DIST. If the expression evaluates to a pure numeric with no dimension then it is assumed to be in the current units of the PTYP dimension.\nWarnings are issued if the PTYP does not match the evaluated physical quantity. This will occur when the PTYP is:\nWarnings are suppressed if PTYP is:\nThe Property now is a physical quantity and this is persisted in any expression that the property is used in (including RULE type, Catalog, reverse Polish, and PML2 expressions).\nIt is transferred to any PML2 variable assigned to the property (!a = !!CE.LDPR.HEIG).\nIf the dimensions in the expression or function arguments do not match then further warnings will be generated:\nNONE\n-\na pure numeric, not a physical property\nDIST\n-\na Distance or Length property\nBORE\n-\na size of BORE property\nDATA or ANY\n-\nany physical property so that any checking for consistency is met and no warning issued.\nPTYP 1kg.degC-1.m2\nDDPR ( XLEN of OWNER + 500mm)\na real value, or\na text string value, or\na reference value\na real value, or\na real value, or\na text string value, or\na text string value, or\na reference value\na reference value\nNONE\nnot a valid dimension when it is taken to be NONE\na non matching valid dimension\nNONE\nNONE\nnot a valid dimension when it is taken to be NONE\nnot a valid dimension when it is taken to be NONE\na non matching valid dimension\na non matching valid dimension\nREAL\nDATA\nANY\nREAL\nREAL\nDATA\nDATA\nANY\nANY\nWarning:\nDIMENSION(UNIT) MISMATCH in arithmetic/arguments/assignment or format: ANGL expected but DIST supplied (element DDATA /DDSE2-DDAT2).\n\n\n\nWarning\n:"}
{"Headers": "Assigning Local Names to Template Elements", "Content": "When a design template is copied, confusion can arise in the identification of members of the template instance. If a template rule refers to an element by its hierarchic position (for example, BOX 1 OF TMPL 1 OF), rule execution errors can arise if the template instance is modified in any way which affects the ordering of the members list. Even if the element has an AVEVA E3D Design name under the Template World, this name will be lost when the template is copied because an element name cannot be used more than once in a Design database.\nTo avoid these problems, assign a local name (LNAME) to a template member. Each local name, and the reference of the corresponding element, is stored in an array attribute of the template. Local names are therefore set and queried at member element level, even though they are stored at template level. The local name survives a template copy operation.\n\n\n\nlocal name"}
{"Headers": "Setting Local Names", "Content": "LNAME\nAssign a local name to a template member, or unset an existing local name. A local name can have a maximum of 20 characters; a maximum of 500 local names can be stored on one template. The local name cannot be modified if either the element or its owning template is locked.\nLNAME /ANTHONY\nSets local name for current element\nLNAME UNSET\nUnsets local name for current element\nQ LNAMe\nGives local name for current element\nQ LNLST\nLists all local names for elements under current template\nQ ATT\nNote:\nLocal names are stored in a compressed numeric format.\nQ LNAMe\nGives local name for current element\nQ LNLST\nLists all local names for elements under current template\nQ ATT\n\nExamples\nLNAME /ANTHONY\nSets local name for current element\nLNAME UNSET\nUnsets local name for current element\nQ LNAMe\nGives local name for current element\nQ LNLST\nLists all local names for elements under current template\nQ ATT\nNote:\nLocal names are stored in a compressed numeric format.\n>--- LNAMe ---*--- local_name ---.\n              |                  |\n              \u2018--- UNSET --------+--->\nNote:\nLocal names are stored in a compressed numeric format.\n\n\n\nLNAME /ANTHONY\nLNAME UNSET\n>--- LNAMe ---*--- local_name ---.\n              |                  |\n              \u2018--- UNSET --------+--->\nQ LNAMe\nQ LNLST\nQ ATT\nNote"}
{"Headers": "Using Local Names in Expressions", "Content": "LNID MLNID\nIdentify an element by its local name in a rule or dataset expression.\nLNID /SID\nIdentifies element defined in current template\nMLNID /JOE\nIdentifies element defined in member template (i.e. in template owned by current element)\n(XLEN OF LNID /SID)\nUses dimension of locally named element in expression (XLEN OF MLNID /JOE)\nQ LNID /SID\nFor element in current template\nQ MLNID /JOE\nFor element in member template\nQ LNID /SID\nFor element in current template\nQ MLNID /JOE\nFor element in member template\n\nExample\nLNID /SID\nIdentifies element defined in current template\nMLNID /JOE\nIdentifies element defined in member template (i.e. in template owned by current element)\n(XLEN OF LNID /SID)\nUses dimension of locally named element in expression (XLEN OF MLNID /JOE)\nQ LNID /SID\nFor element in current template\nQ MLNID /JOE\nFor element in member template\n>---+--- LNid ----.\n    |             |\n    \u2018--- MLNid ---+--- local_name --->\n\n\n\nLNID /SID\nMLNID /JOE\n(XLEN OF LNID /SID)\n>---+--- LNid ----.\n    |             |\n    \u2018--- MLNid ---+--- local_name --->\nQ LNID /SID\nQ MLNID /JOE"}
{"Headers": "Setting Priorities for Evaluating Rules", "Content": "By default, the rules for the member elements of a design template are executed in descending hierarchic order. If the rule for one member element includes a reference to the result of a rule for another member, it is important that the latter rule is executed before the former, otherwise an incorrect result will be obtained.\nThe user can control the order in which the rules for a given template will be executed by assigning a rule sequence number to any element which has a local name. When the template rules are re-executed, the rules for such elements will be executed in ascending order of their sequence numbers: the rules for elements with sequence numbers unset (or zero) will then be executed in the default order. Each rule sequence number, and the reference of the corresponding element, is stored in an array attribute of the template. Rule sequence numbers are therefore set and queried at member element level, even though they are stored at template level.\nRSEQNUMBER\nAssign a rule sequence number to any design template member which has a local name. The rule sequence number must be a positive integer (zero is equivalent to unset). The same sequence number may be assigned to more than one element, but this is not recommended.\nRSEQN 3\nSets rule sequence number for current element (which must be a member of a design template and must already have a local name)\nRSEQN UNSET\nUnsets rule sequence number for current element\nQ RSEQN\nGives sequence number for current element\nQ RSEQA\nLists sequence numbers for all elements under current template (in the order in which their local names were set)\nQ RSEQFA\nLists local names for elements under current template, sorted by rule sequence number; that means, in order of rule execution priority\nQ RSEQN\nGives sequence number for current element\nQ RSEQA\nLists sequence numbers for all elements under current template (in the order in which their local names were set)\nQ RSEQFA\nLists local names for elements under current template, sorted by rule sequence number; that means, in order of rule execution priority\n\nExamples\nRSEQN 3\nSets rule sequence number for current element (which must be a member of a design template and must already have a local name)\nRSEQN UNSET\nUnsets rule sequence number for current element\nQ RSEQN\nGives sequence number for current element\nQ RSEQA\nLists sequence numbers for all elements under current template (in the order in which their local names were set)\nQ RSEQFA\nLists local names for elements under current template, sorted by rule sequence number; that means, in order of rule execution priority\n>--- RSEQNumber ---+--- integer ---.\n                   |               |\n                   \u2018--- UNSET -----+--->\n\n\n\nrule sequence number\nRSEQN 3\nRSEQN UNSET\n>--- RSEQNumber ---+--- integer ---.\n                   |               |\n                   \u2018--- UNSET -----+--->\nQ RSEQN\nQ RSEQA\nQ RSEQFA"}
{"Headers": "Adding Design Points to Template Elements", "Content": "The design datasets for a template, as discussed in Design Datasets, approximate to the Geomset data for a Catalog component. In a similar way, design templates can also own Design Pointsets (DPSE), which approximate to the Pointset data for a Catalog component. These let the user assign p-points to design template items, to be used as references for subsequent positioning and orientating operations.\nA design pointset can store three types of p-point (note that these are not the same as those available in Catalog pointsets):\nA Cartesian P-point is specified in terms of its X,Y,Z co-ordinates only, thus:\nA Cylindrical P-point is specified as a position on the surface of a cylinder at a given position and with given dimensions, thus:\nA Spherical P-point is specified as a position on the surface of a sphere at a given position and with given dimensions, thus:\nA Cartesian P-point is specified in terms of its X,Y,Z co-ordinates only, thus:\nA Cartesian P-point is specified in terms of its X,Y,Z co-ordinates only, thus:\nA Cylindrical P-point is specified as a position on the surface of a cylinder at a given position and with given dimensions, thus:\nA Cylindrical P-point is specified as a position on the surface of a cylinder at a given position and with given dimensions, thus:\nA Spherical P-point is specified as a position on the surface of a sphere at a given position and with given dimensions, thus:\nA Spherical P-point is specified as a position on the surface of a sphere at a given position and with given dimensions, thus:\n\n\n\nDesign Datasets\nDesign Datasets\nDesign Pointsets\nCartesian P-point\nCylindrical P-point\nSpherical P-point"}
{"Headers": "Using a Design Template Item in a Design", "Content": "To create an instance of a \u2018source\u2019 design template in a design model, first create a template below the owning design element and then copy into this the details of the source template (which must be in a template world) from which it is to derive its data. The commands (at the design element which is to own the instance) are:\nwhere template_identifier is the name of the source template. The effects are as follows:\nTo change an attribute explicitly, thereby causing it to differ from the design as specified in the source template, the user must first unset the ORRF references which point back to the source and unlock the members. To do so, use the command\nwhere template_instance is the name of the copy TMPL in the design model hierarchy.\nNEW TMPL \n COPY REXEcute template_identifier\nUNTIE template_instance\nAll elements below the original design template are copied below the new TMPL.\nAll template rules are copied and re\u2011executed, thus setting the attributes of the new TMPL members to suit the design data.\nThe Origin Reference (ORRF) attributes for the new TMPL elements are set to point to their equivalents in the source template.\nAll elements below the new TMPL are locked to prevent unintentional changes to any of their attributes.\nAll elements below the original design template are copied below the new TMPL.\nAll elements below the original design template are copied below the new TMPL.\nAll template rules are copied and re\u2011executed, thus setting the attributes of the new TMPL members to suit the design data.\nAll template rules are copied and re\u2011executed, thus setting the attributes of the new TMPL members to suit the design data.\nThe Origin Reference (ORRF) attributes for the new TMPL elements are set to point to their equivalents in the source template.\nThe Origin Reference (ORRF) attributes for the new TMPL elements are set to point to their equivalents in the source template.\nAll elements below the new TMPL are locked to prevent unintentional changes to any of their attributes.\nAll elements below the new TMPL are locked to prevent unintentional changes to any of their attributes.\n\n\n\nNEW TMPL \n COPY REXEcute \ntemplate_identifier\ntemplate_identifier\nUNTIE \ntemplate_instance\ntemplate_instance"}
{"Headers": "Portsets and Linksets", "Content": "If the user lists the possible members of most types of design element, the user will see two elements called Portsets (PORS) and Linksets (LNKS). These are included in the database definitions to permit logical connections to be made to items derived from design templates by the AVEVA applications.\n\n\n"}
{"Headers": "Assumptions", "Content": "The Monitor Reference Manual has been written for users who need to customize their interface or write macros.\nIt is assumed that:\nUsers have a valid license and the software has been installed.\nUsers have completed the AVEVA Basic Training Course.\nUsers have a valid license and the software has been installed.\nUsers have a valid license and the software has been installed.\nUsers have completed the AVEVA Basic Training Course.\nUsers have completed the AVEVA Basic Training Course.\n\n\n\nMonitor\n."}
{"Headers": "Access Rights", "Content": "This chapter describes what is happening at each stage of entering the application. It explains the way access to data and modules is controlled when the System Administrator sets up projects, users, teams and databases. Then it describes how you can use Monitor commands to query information about access rights to databases and modules, and about who is using the application.\n\n\n\nMonitor"}
{"Headers": "Entering the Application", "Content": "When you start up the application, you must first give the name of the project you will be working on using the PROJECT command. You can query the projects available. Then you specify a user name and password by giving the USERNAME command. You can query the users, and the MDBs, available in the Project before they are set.\nWhen you have entered the username and password correctly, you will be in Monitor.\nYou will be able to use the facilities described in this manual, or start up another module.\nNote:\nWhen working in non-graphics mode, it is recommended that you enter the USERNAME command on its own, and you will then be prompted to enter the username and password, which will not be echoed on the screen. Do not follow the command immediately by the username and password, as this may be a security risk.\n\n\n\nNote\n:\nMonitor"}
{"Headers": "Databases", "Content": "All data is stored in databases. To work on design data you must specify the name of a Multiple Database (MDB) before you enter another module. An MDB is a collection of databases with defined access rights. Specifying an MDB sets your access rights to the databases.\nA MDB can contain up to 1000 DBs, and any number of the 1000 DBs can be described as current and accessed at one time. Databases which cannot be accessed are described as non-current or deferred. The status of a DB can be changed to Current or Defer at any time. Refer to Current and Non-current Databases for further information.\nMONITOR checks that an MDB has been selected before it will allow you to enter another module (except ADMIN).\nRefer to Current Working Units Initialization for further information.\nNote:\nWhen you select an MDB and enter a design module, UNITS settings are taken from the first current catalogue DB. Connection compatibility (COCO) tables in all the current catalogue DBs are available to the designer.\n\n\n\nCurrent and Non-current Databases\nCurrent Working Units Initialization\ndatabases\nMultiple Database\ncurrent\nnon-current\ndeferred\nCurrent\nDefer\nCurrent and Non-current Databases\nNote\n:\nfirst\nall\nCurrent Working Units Initialization"}
{"Headers": "Database Types", "Content": "A Plant project can contain the following types of database:\nSystem Databases\nModel Databases\nThe SYSTEM database itself, which holds the access control data for the model data and modules.\nThe COMMS (Communications) database, which stores information about who is using which module and which model databases are available.\nThe MISC database which store inter-user messages, and inter-database macros.\nIn a Global project there will also be the Global database and a transaction database.\nThe SYSTEM database itself, which holds the access control data for the model data and modules.\nThe SYSTEM database itself, which holds the access control data for the model data and modules.\nThe COMMS (Communications) database, which stores information about who is using which module and which model databases are available.\nThe COMMS (Communications) database, which stores information about who is using which module and which model databases are available.\nThe MISC database which store inter-user messages, and inter-database macros.\nThe MISC database which store inter-user messages, and inter-database macros.\nIn a Global project there will also be the Global database and a transaction database.\nIn a Global project there will also be the Global database and a transaction database.\nThe Design database which contains all the design information for the project\nThe CATALOGUE database where the project catalogue and specifications are stored.\nThe PADD database which contains data about drawings produced by Draw.\nThe PROPERTIES database which can contain material properties, and can be referenced by the catalogue\nThe DICTIONARY database which holds the definitions of user-defined attributes (UDAs), as set up in Lexicon.\nThe ISOD database holds spool drawings generated by SPOOL.\nThe Design database which contains all the design information for the project\nThe Design database which contains all the design information for the project\nThe CATALOGUE database where the project catalogue and specifications are stored.\nThe CATALOGUE database where the project catalogue and specifications are stored.\nThe PADD database which contains data about drawings produced by Draw.\nThe PADD database which contains data about drawings produced by Draw.\nThe PROPERTIES database which can contain material properties, and can be referenced by the catalogue\nThe PROPERTIES database which can contain material properties, and can be referenced by the catalogue\nThe DICTIONARY database which holds the definitions of user-defined attributes (UDAs), as set up in Lexicon.\nThe DICTIONARY database which holds the definitions of user-defined attributes (UDAs), as set up in Lexicon.\nThe ISOD database holds spool drawings generated by SPOOL.\nThe ISOD database holds spool drawings generated by SPOOL.\n\n\n\nGlobal\nGlobal\nDesign\nDraw\nLexicon"}
{"Headers": "Database Access Control", "Content": "Users have one of the following types of access to a DB:\nRead/Write\nYou can change the data held in the DB.\nRead-only\nYou can interrogate the contents of the DB (for example, by using Isodraft to produce an isometric), but you cannot alter it.\nNone\nYou have no access to the DB.\nEach database is set up with UPDATE, CONTROLLED or MULTIWRITE access rights, where:\nUPDATE\nThe database can be accessed by many users with Read-only rights, but only one user with Read/Write right\nCONTROLLED\nControlled by an external system.\nMULTIWRITE\nThe database can be accessed by many users with Read/Write rights.\nRead/Write\nYou can change the data held in the DB.\nRead-only\nYou can interrogate the contents of the DB (for example, by using Isodraft to produce an isometric), but you cannot alter it.\nNone\nYou have no access to the DB.\nEach database is set up with UPDATE, CONTROLLED or MULTIWRITE access rights, where:\nUPDATE\nThe database can be accessed by many users with Read-only rights, but only one user with Read/Write right\nCONTROLLED\nControlled by an external system.\nMULTIWRITE\nThe database can be accessed by many users with Read/Write rights.\nYou can see the access rights to a database by using the LIST DB command.\nRead/Write\nYou can change the data held in the DB.\nRead-only\nYou can interrogate the contents of the DB (for example, by using Isodraft to produce an isometric), but you cannot alter it.\nNone\nYou have no access to the DB.\nEach database is set up with UPDATE, CONTROLLED or MULTIWRITE access rights, where:\nUPDATE\nThe database can be accessed by many users with Read-only rights, but only one user with Read/Write right\nCONTROLLED\nControlled by an external system.\nMULTIWRITE\nThe database can be accessed by many users with Read/Write rights.\n\n\n\nRead/Write\nRead-only\nIsodraft\nNone\nUPDATE\nCONTROLLED\nMULTIWRITE\nLIST DB"}
{"Headers": "Foreign Databases", "Content": "Foreign databases are databases which have been included from a different project. This is often used for Catalogue databases, so that many users can have Read access to the same database without needing multiple copies. For example, in the Sample project supplied with the product, there are several databases shared with the Master project. Foreign databases are listed as such when databases are queried. Refer to QUERY.\n\n\n\nQUERY\nQUERY"}
{"Headers": "Teams", "Content": "A team is a user or a group of users who have read-write access to a database (and read access to several other databases). The database must be named as:\nteamid/identifier\nteamid\nis the name of the team which is given full Read/Write access to the DB\nidentifier\nis the name of the DB. This is a normal Plant name beginning with a slash (/).\nteamid\nis the name of the team which is given full Read/Write access to the DB\nidentifier\nis the name of the DB. This is a normal Plant name beginning with a slash (/).\nFor example, the PIPING team would have read-write access to design databases containing piping design, the STRUCTURES team would have read-write access to databases containing steelwork design, but they would both have read-only access to a catalogue database. So, the MDB for the PIPING team could contain the following databases (and normally several others):\nPIPING/PIPING-A\nA Design database PIPING-A, to which the PIPING team will have read/write access.\nMASTER/CATALOGUE-1\nA Catalogue database CATALOGUE-1, to which the PIPING team will have read-only access.\nPIPING/PIPING-A\nA Design database PIPING-A, to which the PIPING team will have read/write access.\nMASTER/CATALOGUE-1\nA Catalogue database CATALOGUE-1, to which the PIPING team will have read-only access.\n\nteamid\nis the name of the team which is given full Read/Write access to the DB\nidentifier\nis the name of the DB. This is a normal Plant name beginning with a slash (/).\nPIPING/PIPING-A\nA Design database PIPING-A, to which the PIPING team will have read/write access.\nMASTER/CATALOGUE-1\nA Catalogue database CATALOGUE-1, to which the PIPING team will have read-only access.\n\n\n\nteam\nteamid/identifier\nteamid\nidentifier"}
{"Headers": "Access Rights of Users to Databases", "Content": "Each user has a level of access assigned by the System Administrator:\nFree users have read-write access to all databases.\nGeneral users have read-write access to databases owned by their team in the current MDB, and read-only access to other copies of databases in the current MDB.\nFree users have read-write access to all databases.\nFree users have read-write access to all databases.\nGeneral users have read-write access to databases owned by their team in the current MDB, and read-only access to other copies of databases in the current MDB.\nGeneral users have read-write access to databases owned by their team in the current MDB, and read-only access to other copies of databases in the current MDB.\n\n\n\nFree\nGeneral"}
{"Headers": "Module Access Control", "Content": "Any module can be classified as Free, or Restricted. Whether a user has access to a module will depend on the user\u2019s access rights and the access classification of the module, as follows:\nIn the system configuration as supplied, only Admin and Lexicon are Restricted. All the other modules are Free.\nOnly a Free user may use a Restricted module\nA General user may use Free modules\nOnly a Free user may use a Restricted module\nOnly a Free user may use a Restricted module\nA General user may use Free modules\nA General user may use Free modules\n\n\n\nAdmin\nLexicon"}
{"Headers": "Using Monitor", "Content": "This chapter is an overview of Monitor commands. They are mainly used to select databases and modules, to query information about the system status, users and databases, and to communicate with other users.\nRefer to Command Summary for further information.\n\n\n\nCommand Summary\nMonitor\nCommand Summary"}
{"Headers": "Changing Your Password", "Content": "You can change your password from that allocated to you by the System Administrator. The command PASS is followed by a slash and then the new password, consisting of up to fifteen characters, excluding I\u2019@$/*\".\n\n\n\nPASS"}
{"Headers": "User Status", "Content": "The STATUS command outputs information about your current status and the databases to which you have access. Refer to STATUS for a detailed description of the status command.\n\n\n\nSTATUS\nSTATUS\nSTATUS"}
{"Headers": "System Status", "Content": "The SYSTAT (System Status) command outputs information about the current active status of the project. It lists all users who are accessing the project at that time, the modules and databases which they are using, and whether they are examining (Read-only status) or modifying (Read/Write status) the database. It also gives the unique identifier of each user. Refer to SYSTAT for a detailed description of the SYSTAT command.\n\n\n\nSYSTAT\nSYSTAT\nactive\nSYSTAT"}
{"Headers": "Setting the Current Team", "Content": "The SET command sets the specified team as the current one. Once a team has been set, DBs owned by that team can be referred to by using the name part only. For example, after the command\nYou could give the command\nInstead of the command\n\n\n\nSET\nSET TEAM SAMPLE\nQ DB /DESI\nQ DB SAMPLE/DESI"}
{"Headers": "Listing and Querying", "Content": "The LIST and QUERY commands can be used to display information about Users, Teams, MDBs and Databases. LIST outputs general information, and QUERY outputs information about a named item. Note that there are many other options in the QUERY command available in other modules; the ones described here are those available in Monitor.\nThe LIST command outputs information about:\n\n\n\nLIST\nQUERY\nLIST\nQUERY\nQUERY\nMonitor\nLIST\nUsers\nMDBs\nDBs\nTeams\nCopies of databases\nModules"}
{"Headers": "LIST USERS", "Content": "An example of typical output from the command LIST USERS is shown below. It lists all the users in the project, with their access level (Free or General), and the teams they belong to:\nList of USERS for project SAM\n ===============================\n SYSTEM   (Free)\n Teams : MASTER   SAMPLE   DEMO   HANGERS  HVAC PIPE\n         DRAFTADMIN   ISOADMIN HSADMIN  ADMIN\n          SAMPLE   (General)\n          Teams : SAMPLE\n          DEMO     (General)\n          Teams : DEMO\n          HANGERS  (General)\n          Teams : HANGERS\n               (General)\n          Teams : HVAC\n          PIPE     (General)\n          Teams : PIPE\n\n\n\nLIST USERS\nList of USERS for project SAM\n ===============================\n SYSTEM   (Free)\n Teams : MASTER   SAMPLE   DEMO   HANGERS  HVAC PIPE\n         DRAFTADMIN   ISOADMIN HSADMIN  ADMIN\n          SAMPLE   (General)\n          Teams : SAMPLE\n          DEMO     (General)\n          Teams : DEMO\n          HANGERS  (General)\n          Teams : HANGERS\n               (General)\n          Teams : HVAC\n          PIPE     (General)\n          Teams : PIPE"}
{"Headers": "LIST TEAMS", "Content": "An example of typical output from the command LIST TEAMS is shown below. It lists all the teams in the project, with the users who are members of the teams and the DBs associated with them.\nList of TEAMS for project SAM\n ===============================\n MASTER\n USERS: SYSTEM\n DBS: /PIPECATA  /PIPEOLD /STLCATA /HVACCATA  /SUPPCATA\n      /PADD    /DICT    /PROP\n   \nSAMPLE\nUSERS: SYSTEM   SAMPLE\nDBS: /DESI    /PADD    /COMP\n   \nDEMO\nUSERS: SYSTEM   DEMO\nDBS: /DESI    /PADD    /COMP\n   \n...\n...\n   \nADMIN\nUSERS: SYSTEM\nDBS: /PADD\n   \n\n\n\nLIST TEAMS"}
{"Headers": "LIST MDB", "Content": "The command LIST MDB lists the MDBs in the project. For each MDB it lists the databases it contains, their types (DESI, CATA, ), access level (for example, UPDATE), and the current and deferred databases. For example:\nList of MDBS for project SAM\n ==============================\n MDB: /SAMPLE\n Current DBS:\n   1  SAMPLE/DESI              DESI Update\n   2  SAMPLE/PADD              PADD Update\n   3  ADMIN/PADD               PADD Update\n   4  SAMPLE/COMP              COMP Update\n   5  MASTER/PIPECATA          CATA Update Foreign\n   6  MASTER/PIPEOLD           CATA Update Foreign\n   7  MASTER/STLCATA           CATA Update Foreign\n   8  MASTER/HVACCATA          CATA Update Foreign\n   9  MASTER/SUPPCATA          CATA Update Foreign\n  10  MASTER/PADD              PADD Update Foreign\n  11  MASTER/DICT              DICT Update Foreign\n  12  MASTER/PROP              PROP Update Foreign\n Deferred DBS:\n **NONE**\nMDB: /DEMO\n Current DBS:\n   1  DEMO/DESI                 DESI Update\n   2  DEMO/PADD                 PADD Update\n   ...\n\n\n\nLIST MDB"}
{"Headers": "LIST DB", "Content": "The command LIST DB lists all the databases in the project, their types (DESI, CATA, ) and the MDBs which contain them. For example:\nList of DBS for project SAM\n =============================\n MASTER/PIPECATA    CATA FOREIGN   Number 8101 Update\n   Size 7623 pages\n MDBS: /SAMPLE  /DEMO    /HANGERS /HVAC    /PIPE\n   \nMASTER/PIPEOLD    CATA FOREIGN   Number 8105 Update\n   Size 4861 pages\n MDBS: /SAMPLE  /DEMO    /HANGERS /HVAC    /PIPE\n   \nADMIN/PADD        PADD   Number 8013 Update\n   Size  51 pages\n MDBS: /SAMPLE  /DEMO\n ...\n ...\n   \n\n\n"}
{"Headers": "LIST COPIES", "Content": "The command LIST COPIES displays the names of all DBs which have been copied from a different project and the names under which the copies are filed. For example:\nList of sets of copied DBS for project ABC\n ============================================\n Database PIPING-A/DESI has copies:\n   PIPING-X/DESI\n   \n\n\n\nLIST COPIES"}
{"Headers": "LIST MODULES", "Content": "The LIST MODULES command lists information about modules in the current project. It may be useful if you are having difficulty accessing a module for some reason, but you will need access to Admin to make any changes.\nList of modules for project SAM\n =================================\n   \nModule 0  MONITOR\n          Security Free\n          Imacro /%PMLUI%/MON/ADMIN/START\n          Open  Attlib /%AVEVA_DESIGN_EXE%/attlib.dat\n          Open  Message /%AVEVA_DESIGN_EXE%/message.dat\n           Resume /%AVEVA_DESIGN_EXE%/mon\n   \nModule 1  ADMIN\n          Security Restricted\n          Buffer 2560000\n           Resume /%AVEVA_DESIGN_EXE%/adm\n   \n...\n\n\n\nLIST MODULES\nAdmin"}
{"Headers": "QUERY", "Content": "The QUERY command outputs information about named administration elements.\nNote that there are many other elements and attributes of elements that can be queried in other modules. This section lists those available in Monitor.\nSome examples of output from querying commands are given below. For a complete specification of the options, see the command syntax.\nCommand\nOutput\nQ USER\nUser: SAMPLE\nQ USER SAMPLE\nSAMPLE   (General)\nTeams : SAMPLE\n                  \nQ USER SYSTEM ACCESS\n(Free)\nQ USER SYSTEM DESCRIPTION\nsystem administrator\nCommand\nOutput\nCurrent DBS:1 SAMPLE/DESI  DESI Update\n            2 SAMPLE/PADD  PADD Update\n               . . .\n          11 MASTER/DICT DICT Update Foreign\n          12 MASTER/PROP PROP Update Foreign\n          Deferred DBS:\n          **NONE**\nLIST\nCommand\nOutput\nQ USER\nUser: SAMPLE\nQ USER SAMPLE\nSAMPLE   (General)\nTeams : SAMPLE\n                  \nQ USER SYSTEM ACCESS\n(Free)\nQ USER SYSTEM DESCRIPTION\nsystem administrator\nQ ACTIVE\nNumber of Active Users is 1\nQ TEAM SAMPLE\nSAMPLE\nUSERS: SYSTEM   SAMPLE\nDBS: /DESI    /PADD    /COMP\nQ TEAM SAMPLE DESCRIPTION\nTeam for Sample Project\nq set team\n** SAMPLE **\nQ MDB /SAMPLE\nMDB: /SAMPLE\nCurrent DBS:1 SAMPLE/DESI  DESI Update\n            2 SAMPLE/PADD  PADD Update\n               . . .\n          11 MASTER/DICT DICT Update Foreign\n          12 MASTER/PROP PROP Update Foreign\n          Deferred DBS:\n          **NONE**\nQ MDB /SAMPLE\nMDB for Sample Project\nQ DB SAMPLE/DESI\nSAMPLE/DESI DESI Number 8010 Update\nSize 664 pages\n                  \nMDBS: /SAMPLE\nQ DB MASTER/PIPEOLD TYPE\nCATA\nQ DB MASTER/PIPECATA FILE\nFilename /%MAS000%/mas005\nQ DB MASTER/PIPECATA NUMBER\nNumber 8101\nQ DB MASTER/PIPECATA SIZE\nSize 623 pages\nQ DB MASTER/PIPECATA FOREIGN\nFOREIGN\nQ DB SAMPLE/DESI FOREIGN\nLocal\nQ DB SAMPLE/DESI ACCESS\nUpdate\nQ COPIES SAMPLE/DESI\nDatabase SAMPLE/DESI has copies: ABC/DESI\nQ MACRO 1\n/%SAMMAC%/sam001.mac TEST/DESI SAMPLE/DESI\nQ MACRO 1 FROM\nTEST/DESI\nQ PROJ\nNumber (01223) 556666\nName Sample Project\nDescription \nSample Released \nProject\nMessage AVEVA Project - Example Only\n                  \n>--- Query ---+--- USer ---+-------------------------------.\n              |            |                               |\n              |            \u2018--- userid --+-- ACCess -------|\n              |                          |                 |\n              |                          |-- DESCription --|\n              |                          |                 |\n              |                          \u2018-- PASS ---------|\n              |                                            |\n              |--- ACTIVE ---------------------------------|\n              |                                            |\n              |--- TEam teamid ----------+-----------------|\n              |                          |                 |\n              |                          \u2018-- DESCription --|\n              |                                            |\n              |--- DB dbname --+---------------------------|\n              |                |                           |\n              |                |-- DESCription ------------|\n              |                |                           |\n              |                |-- TYpe -------------------|\n              |                |                           |\n              |                |-- FIle -------------------|\n              |                |                           |\n              |                |-- NUmber -----------------|\n              |                |                           |\n              |                |-- SIze -------------------|\n              |                |                           |\n              |                |-- FOREign ----------------|\n              |                |                           |\n              |                \u2018-- ACCess -----------------|\n              |                                            |\n              |--- COpies dbname --------------------------|\n              |                                            |\n              |--- MDB mdbname --+-------------------------|\n              |                  |                         |\n              |                  \u2018-- DESCription ----------|\n              |                                            |\n              |--- MACRO integer --+-----------------------|\n              |                    |                       |\n              |                    |-- FILEname -----------|\n              |                    |                       |\n              |                    |-- FROMdb -------------|\n              |                    |                       |\n              |                    \u2018-- TOdb ---------------|\n              |                                            |\n              |--- PASSWORDLOCK ---------------------------|\nNote:\nDescription must have been set.\nNote:\nThis information will only be output if you are a Free user.\nNote:\nA description must have been set.\nNote:\nA description must have been set.\n\n\n\nQUERY\nMonitor\nCommand\nOutput\nNote\n:\nNote\n:\nNote\n:\nNote\n:\n>--- Query ---+--- USer ---+-------------------------------.\n              |            |                               |\n              |            \u2018--- userid --+-- ACCess -------|\n              |                          |                 |\n              |                          |-- DESCription --|\n              |                          |                 |\n              |                          \u2018-- PASS ---------|\n              |                                            |\n              |--- ACTIVE ---------------------------------|\n              |                                            |\n              |--- TEam teamid ----------+-----------------|\n              |                          |                 |\n              |                          \u2018-- DESCription --|\n              |                                            |\n              |--- DB dbname --+---------------------------|\n              |                |                           |\n              |                |-- DESCription ------------|\n              |                |                           |\n              |                |-- TYpe -------------------|\n              |                |                           |\n              |                |-- FIle -------------------|\n              |                |                           |\n              |                |-- NUmber -----------------|\n              |                |                           |\n              |                |-- SIze -------------------|\n              |                |                           |\n              |                |-- FOREign ----------------|\n              |                |                           |\n              |                \u2018-- ACCess -----------------|\n              |                                            |\n              |--- COpies dbname --------------------------|\n              |                                            |\n              |--- MDB mdbname --+-------------------------|\n              |                  |                         |\n              |                  \u2018-- DESCription ----------|\n              |                                            |\n              |--- MACRO integer --+-----------------------|\n              |                    |                       |\n              |                    |-- FILEname -----------|\n              |                    |                       |\n              |                    |-- FROMdb -------------|\n              |                    |                       |\n              |                    \u2018-- TOdb ---------------|\n              |                                            |\n              |--- PASSWORDLOCK ---------------------------|\n              |                                            |\n              |--- SET TEam -------------------------------|\n              |                                            |\n              \u2018--- PROject ---+--- NAMe -------------------|\n                              |                            |\n                              |--- NUMber -----------------|\n                              |                            |\n                              |--- DEScription ------------|\n                              |                            |\n                              \u2018--- MESsage ----------------+-->"}
{"Headers": "Temporarily Changing Access Rights", "Content": "The PROTECT command allows you to alter your access rights to specified DBs for the current session. You can only reduce your access rights from the set state, never increase them. This command can be used on the current MDB. Refer to PROTECT for a detailed description of the PROTECT command.\n\n\n\nPROTECT\nPROTECT\nPROTECT"}
{"Headers": "Current and Non-current Databases", "Content": "A MDB can contain up to 1000 DBs, and any number of the 1000 DBs can be described as current and accessed at one time. Databases which cannot be accessed are described as non-current or deferred.\nEXCHANGE replaces a current DB by a non-current DB. The DB names do not need to be listed in a particular order, since the MDB knows which are current and which are non-current, but they must be paired correctly if more than two names are listed.\nCURRENT includes the specified DB at a given position in the Current list.\nDEFER removes the specified DB from the Current list and makes it non-current.\nFor example, assume that an MDB contains the following DBs as shown by a LIST command:\nThe command\nwould result in the new configuration\nThe effect of the command\nafter the EXCHANGE command is to insert the named DBs at positions 1 and 4 respectively in the Current list, resulting in\nNote that the position specified for each DB to be added to the Current list applies after the previous insertions have been made.\n/DESIGN\nCurrent DBS:   PIPING/PIPING-A    PIPING/PIPINGC\nMASTER/CATA-D\nDeferred DBS:   PIPING/PIPING-B    MASTER/PIPING-\nEXCHANGE PIPING/PIPING-A PIPING/PIPING-B MASTER/PIPING-E MASTER/CATA-D\n/DESIGN\nCurrent DBS:  PIPING/PIPING-B   PIPING/PIPING-C  \nMASTER/PIPING-E\nDeferred DBS: PIPING/PIPING-A   MASTER/CATA-D\nCURRENT PIPING/PIPING-A 1  MASTER/CATA-D 4\n/DESIGN\nCurrent DBS: PIPING/PIPING-A PIPING/PIPING-B PIPING/PIPING-C          MASTER/CATA-D   \nMASTER/PIPING-E\nDeferred DBS:**NONE**\nNote:\nThe current DBs PIPING/PIPING-A and MASTER/CATA-D are replaced by the DBs PIPING/PIPING-B and MASTER/PIPING-E respectively, even though they are listed out of sequence in the EXCHANGE command.\n\n\n\ncurrent\nnon-current\ndeferred.\nEXCHANGE\nCURRENT\nDEFER\nLIST\n/DESIGN\nCurrent DBS:   PIPING/PIPING-A    PIPING/PIPINGC\nMASTER/CATA-D\nDeferred DBS:   PIPING/PIPING-B    MASTER/PIPING-\nEXCHANGE PIPING/PIPING-A PIPING/PIPING-B MASTER/PIPING-E MASTER/CATA-D\n/DESIGN\nCurrent DBS:  PIPING/PIPING-B   PIPING/PIPING-C  \nMASTER/PIPING-E\nDeferred DBS: PIPING/PIPING-A   MASTER/CATA-D\nNote\n:\nEXCHANGE\nCURRENT PIPING/PIPING-A 1  MASTER/CATA-D 4\nEXCHANGE\n/DESIGN\nCurrent DBS: PIPING/PIPING-A PIPING/PIPING-B PIPING/PIPING-C          MASTER/CATA-D   \nMASTER/PIPING-E\nDeferred DBS:**NONE**\nafter"}
{"Headers": "Sending Messages to Other Users", "Content": "You can send messages to other users of the project using the MESSAGE command.\nMessages sent using the MESSAGE command will only be displayed to users already in the project when the command is given, and then only when they next change modules. You can send messages to:\nThe text of the message must be enclosed in quotes. For example:\nMESS TEAM PIPING  \u2019LATEST PIPE ROUTING HAS BEEN APPROVED\u2019\nAn individual user, specified by name or identifier\nAll members of a specified team\nAll active project users\nAll users logged into a given host\nAll users with a given line number\nAn individual user, specified by name or identifier\nAn individual user, specified by name or identifier\nAll members of a specified team\nAll members of a specified team\nAll active project users\nAll active project users\nAll users logged into a given host\nAll users logged into a given host\nAll users with a given line number\nAll users with a given line number\nNote:\nThe message must be enclosed in quotes.\n\n\n\nMESSAGE\nMESSAGE\nMESS TEAM PIPING  \u2019LATEST PIPE ROUTING HAS BEEN APPROVED\u2019\nNote\n:"}
{"Headers": "Output Destination", "Content": "The data output by the commands described in this chapter can be sent to the screen or to a file. By default, the data is sent to the screen, but it can be directed to a file using the ALPHA FILE or FILE command. These commands also specify the number of characters in a line and the number of lines on a page, and whether the file should be overwritten if new data is sent to it.\nIf you have specified that output should be sent to a file using the ALPHA FILE command, you can return to output being sent to the screen by giving the ALPHA FILE END command. If you have specified that output should be sent to a file using the FILE command, you must use the TERMINAL command to send output to the screen. ALPHA FILE is recommended for normal use.\nThe default is TERMINAL WITH 80 CHARACTERS.\n\n\n\nALPHA FILE\nFILE\nALPHA FILE\nALPHA FILE END\nFILE\nTERMINAL\nALPHA FILE\nTERMINAL WITH 80 CHARACTERS"}
{"Headers": "Output Devices", "Content": "You will normally have a default output device set. The default output devices for both text and graphics are shown in a message which is displayed when the application is started up. You can use the DEVICE command to change your output device, for example, if you do not want any graphics to be displayed.\n\n\n\nDEVICE"}
{"Headers": "Changing Modules", "Content": "You can enter any module which is installed on your system and to which you have access by typing its name.\nYou can return to Monitor from any other module by giving the command\nMonitor\n\n\n\nMonitor\nMonitor"}
{"Headers": "Deleting Inter-database Connection Macros", "Content": "The DELETE command is used to delete inter-DB connection macros, which are created in a Design module when connections are made across databases.\n\n\n\nDELETE"}
{"Headers": "Leaving the Application", "Content": "The FINISH command terminates the current session and returns you to the operating system.\n\n\n\nFINISH"}
{"Headers": "Running in Batch Mode", "Content": "To run jobs in batch mode, the application must be started up in batch mode. To set up a batch job, you must create a file containing all the commands which you would normally enter at the keyboard, and possibly add other commands required by the computer\u2019s batch system. Then run the file using the normal command in your operating system. Refer to BATCH.\n\n\n\nBATCH\nBATCH"}
{"Headers": "Command Summary", "Content": "This section lists the Monitor commands, with a brief description of each.\nBATCH\nSpecifies commands for running in batch mode.\nCURRENT\nMakes a database current.\nDEFER\nMakes a database non-current (deferred).\nDELETE\nDeletes inter-DB connection macros.\nDEVICE\nSpecifies a device type.\nEXCHANGE\nReplaces a current database by a deferred one.\nFINISH\nExits the application.\nLIST\nLists information about the project.\nMESSAGE\nSends a message to other users.\nPASSWORD\nChanges your password.\nPROJECT\nSpecifies the current project.\nPROTECT\nChanges your access rights to databases.\nQUERY\nOutputs information about named administration elements (Users, Teams, etc).\nRUN\nRuns modules which are not available through the normal module-changing commands.\nSYSTAT\nOutputs status information about the current project.\nUSERNAME\nSpecifies a username and password.\nBATCH\nSpecifies commands for running in batch mode.\nCURRENT\nMakes a database current.\nDEFER\nMakes a database non-current (deferred).\nDELETE\nDeletes inter-DB connection macros.\nDEVICE\nSpecifies a device type.\nEXCHANGE\nReplaces a current database by a deferred one.\nFINISH\nExits the application.\nLIST\nLists information about the project.\nMESSAGE\nSends a message to other users.\nPASSWORD\nChanges your password.\nPROJECT\nSpecifies the current project.\nPROTECT\nChanges your access rights to databases.\nQUERY\nOutputs information about named administration elements (Users, Teams, etc).\nRUN\nRuns modules which are not available through the normal module-changing commands.\nSYSTAT\nOutputs status information about the current project.\nUSERNAME\nSpecifies a username and password.\n\nBATCH\nSpecifies commands for running in batch mode.\nCURRENT\nMakes a database current.\nDEFER\nMakes a database non-current (deferred).\nDELETE\nDeletes inter-DB connection macros.\nDEVICE\nSpecifies a device type.\nEXCHANGE\nReplaces a current database by a deferred one.\nFINISH\nExits the application.\nLIST\nLists information about the project.\nMESSAGE\nSends a message to other users.\nPASSWORD\nChanges your password.\nPROJECT\nSpecifies the current project.\nPROTECT\nChanges your access rights to databases.\nQUERY\nOutputs information about named administration elements (Users, Teams, etc).\nRUN\nRuns modules which are not available through the normal module-changing commands.\nSYSTAT\nOutputs status information about the current project.\nUSERNAME\nSpecifies a username and password.\n\n\n\nMonitor"}
{"Headers": "Conventions Used in the Syntax Graphs", "Content": "The commands described in this chapter are presented in the form of syntax graphs.\nCommands are shown in a combination of uppercase and lowercase letters, where the capital letters indicate the minimum abbreviation.\nFor example, the command\ncan be input in any of the following forms:\nmeans that to set a password to secret, you enter:\nCommand arguments are just descriptions of what you need to enter, and the description shown should be replaced by the text or value required. The following table shows some examples:\nname\nAn element name\nPIPE-A63\nrefno\nA reference number\n=23/1403\ninteger\nA positive integer\n3\nvalue\nA positive or negative number\n3.142\nword\nA sequence of up to 4 letters\nFLOW\ntext\nAn alphanumeric string\n\u2018Enclose in quotes\u2019\nfilename\nThe pathname of a file\n/c:\\\\testing\nName\nDefinition\nExample\nname\nAn element name\nPIPE-A63\nrefno\nA reference number\n=23/1403\ninteger\nA positive integer\n3\nvalue\nA positive or negative number\n3.142\nword\nA sequence of up to 4 letters\nFLOW\ntext\nAn alphanumeric string\n\u2018Enclose in quotes\u2019\nfilename\nThe pathname of a file\n/c:\\\\testing\nNote:\nWhen a full pathname is given, the first slash is needed because all names in the application must start with a slash.\nQuery\nQ\nQU\nQUE\nQUER\nQUERY\nPASSWORD password\nPASSWORD /SECRET\n >----+--- ABC -----.\n      |             |\n      |--- PQR -----|\n      |             |\n      \u2018-------------+--->\n              .-----<-------.\n             /              |\n        >---*--- option1 ---|\n            |               |\n            |--- option2 ---|\n            |               |\n            \u2018--- option3 ---+--->\n             .----<------.\n            /            |\n       >---*--- name ----+--->\nCommands shown in all uppercase letters cannot be abbreviated.\nCommand arguments are shown in lowercase italic letters. For example:\nPASSWORD password\nCommands shown in all uppercase letters cannot be abbreviated.\nCommands shown in all uppercase letters cannot be abbreviated.\nCommand arguments are shown in lowercase italic letters. For example:\nPASSWORD password\nCommand arguments are shown in lowercase italic letters. For example:\nSyntax graphs are read from top left to bottom right. The start point is shown by >, and you can follow any path through the graph until the exit point, shown by >, is reached.\nPoints marked with a plus sign (+) are option junctions which allow you to input any one of the commands to the right of the junction. For example:\n >----+--- ABC -----.\n      |             |\n      |--- PQR -----|\n      |             |\n      \u2018-------------+--->\nmeans you can type in ABC or PQR or just press Enter to get the default option.\nPoints marked with an asterisk (*) are loop back junctions. Command options following these may be repeated as required.\nFor example:\n              .-----<-------.\n             /              |\n        >---*--- option1 ---|\n            |               |\n            |--- option2 ---|\n            |               |\n            \u2018--- option3 ---+--->\nmeans that you can enter any combination of option1 and/or option2 and/or option3, where the options can be commands, other syntax diagrams, or command arguments.\nThe simplified format:\n             .----<------.\n            /            |\n       >---*--- name ----+--->\nmeans that you may type in a list of names, separated by at least one space.\nSyntax graphs are read from top left to bottom right. The start point is shown by >, and you can follow any path through the graph until the exit point, shown by >, is reached.\nSyntax graphs are read from top left to bottom right. The start point is shown by >, and you can follow any path through the graph until the exit point, shown by >, is reached.\nPoints marked with a plus sign (+) are option junctions which allow you to input any one of the commands to the right of the junction. For example:\n >----+--- ABC -----.\n      |             |\n      |--- PQR -----|\n      |             |\n      \u2018-------------+--->\nmeans you can type in ABC or PQR or just press Enter to get the default option.\nPoints marked with a plus sign (+) are option junctions which allow you to input any one of the commands to the right of the junction. For example:\nPoints marked with an asterisk (*) are loop back junctions. Command options following these may be repeated as required.\nFor example:\n              .-----<-------.\n             /              |\n        >---*--- option1 ---|\n            |               |\n            |--- option2 ---|\n            |               |\n            \u2018--- option3 ---+--->\nmeans that you can enter any combination of option1 and/or option2 and/or option3, where the options can be commands, other syntax diagrams, or command arguments.\nPoints marked with an asterisk (*) are loop back junctions. Command options following these may be repeated as required.\nThe simplified format:\n             .----<------.\n            /            |\n       >---*--- name ----+--->\nmeans that you may type in a list of names, separated by at least one space.\nThe simplified format:\nNote:\nThis convention does not mean that the second part of the command must be typed in lowercase letters; commands may be entered in any combination of uppercase and lowercase letters.\nNote:\nWhen a full pathname is given, the first slash is needed because all names in the application must start with a slash.\n\n\n\nsyntax graphs\nNote\n:\nQuery\nQ\nQU\nQUE\nQUER\nQUERY\nPASSWORD password\nPASSWORD /SECRET\nName\nDefinition\nExample\nname\nrefno\ninteger\nvalue\nword\ntext\nfilename\nNote\n:\noption junctions\n >----+--- ABC -----.\n      |             |\n      |--- PQR -----|\n      |             |\n      \u2018-------------+--->\nor\nor\nloop back junctions\n              .-----<-------.\n             /              |\n        >---*--- option1 ---|\n            |               |\n            |--- option2 ---|\n            |               |\n            \u2018--- option3 ---+--->\nand/or\nand/or\n             .----<------.\n            /            |\n       >---*--- name ----+--->"}
{"Headers": "BATCH", "Content": "The BATCH command enables you to specify how batch jobs will be processed.\nTo run jobs in batch mode, the application must be started up in batch mode.\nWhen you enter the application interactively, you are allowed three attempts at giving your correct username and password. When the application is started up in batch mode, only one attempt is permitted. If either the username or password are incorrect, control will pass back to the operating system and that job will be terminated.\nThe BATCH COPY command allows you to take copies of DBs with Read/Write access, provided you have Read/Write access to the database. The batch job accesses these copies and so allows interactive users to carry on using the normal copies. Write access to copies of DBs is needed to allow functions such as automatic group creation to be carried out.\nBy default, if a COPY command is not given, copies are made of all Design DBs.\nIf copies are not taken of DBs, then the originals are accessed in Read-only mode, irrespective of the normal access rights (which may be Read/Write).\nYou can specify that you want all the databases of a given type to be copied, for example, all the PADD databases, or you can specify named databases, all databases or none. You can specify a group of databases of a given type, and then use the NOCOPY option to stop copies of named databases or specified types of database being made.\nThe copies taken by the BATCH COPY command are temporary. They disappear when the batch job exits from the application (whether successfully completed or not) or when the batch file selects a new MDB. If permanent copies are required, they must be made by the System Administrator using Admin.\nAccess to databases through Admin and RECONFIGURER can only be made in Read-only mode, even if the databases have been copied with Read/Write access. Any attempt to alter the project structure for batch jobs, even temporarily, will result in the message:\nBATCH COPY DESI DRWG\nCopies will be made of all Design and Drawing DBs in the selected MDB.\nBATCH COPY PIPING/DES74A CIVIL/DES13B\nCopies will be made of the two named DBs.\nBATCH COPY ALL\nCopies will be made of all DBs in the MDB.\nBATCH COPY NONE\nNo copies will be made of any DB.\nBATCH NOCOPY PIPING/DES74A\nThe database PIPING/DES74A will not be copied.\nBATCH COPY DESI DRWG\nCopies will be made of all Design and Drawing DBs in the selected MDB.\nBATCH COPY PIPING/DES74A CIVIL/DES13B\nCopies will be made of the two named DBs.\nBATCH COPY ALL\nCopies will be made of all DBs in the MDB.\nBATCH COPY NONE\nNo copies will be made of any DB.\nBATCH NOCOPY PIPING/DES74A\nThe database PIPING/DES74A will not be copied.\nCOPY commands are additive; that is, each new COPY command is added to the result of all previous COPY commands. For example, consider an MDB containing the following DBs:\nIf the batch file contains the commands:\nThe following DBs would be marked as requiring copies:\nFor a batch job to start, the application must be able to access all the databases it needs, either to make copies of them or to access them directly.\nWhen a batch run starts, and the first module change command occurs, Monitor will make copies of any DBs marked for copying.\nAs the batch file could alter the status of databases in an MDB by using the DEFER, CURRENT or EXCHANGE commands, or could change to a different MDB, copies are not taken until immediately after the command to change to another module. If a new MDB is selected, or the same MDB is reselected and copies of DBs exist from the last time the MDB was accessed, then all existing copies are deleted and fresh copies are taken. It is important for batch users to assess the effect of copying DBs on disk space.\nWhen you use the batch facilities, you must put your username and password into a file. This is a potential breach of the security system provided by the application, from two points of view.\nThere is some risk of corruption of the COMMS DB (the only DB written to in Read-only batch operation) if a batch-mode job is interrupted before completion.\nTo reduce the risk of serious corruption of the COMMS DB, you should take the following precautions:\nwhere dbtype is one of the following:\nDESI CATA PROP PADD DICT ISOD\nBATCH COPY DESI DRWG\nCopies will be made of all Design and Drawing DBs in the selected MDB.\nBATCH COPY PIPING/DES74A CIVIL/DES13B\nCopies will be made of the two named DBs.\nBATCH COPY ALL\nCopies will be made of all DBs in the MDB.\nBATCH COPY NONE\nNo copies will be made of any DB.\nBATCH NOCOPY PIPING/DES74A\nThe database PIPING/DES74A will not be copied.\nMASTER/CATA                 CATA\nPIPING/DES74A               DESI\nPIPING/DES75A               DESI\nPIPING/DES37C               DESI\nCIVIL/DES74A                DESI\nCIVIL/DES75A                DESI\nCIVIL/DES37C                DESI\nMATS/PROP2                  PROP\n   \nBATCH  COPY  NONE\nBATCH  COPY  PIPING/DES75A  PIPING/DES37C\nBATCH  COPY  DRWG\n   \nPIPING/DES75A              DESI\nPIPING/DES37C              DESI\n   \n                            .----------<---------.\n                           /                     |\n>-- BAtch ---+--- COpy ---*--- ALL --------------|\n             |            |                      |\n             |            |--- NONE -------------|\n             |            |                      |\n             |            |--- dbtype -----------|\n             |            |                      |\n             |            \u2018--- dbname -----------|\n             |                                   |\n             |                .-----<------.     |\n             |               /             |     |\n             \u2018--- NOCOpy ---*--- dbtype ---|     |\n                            |              |     |\n                            \u2018--- dbname ---+-----+--->\nIf the project name, username or password are incorrectly specified while trying to gain access in batch mode, the application will immediately abort.\nIf any other errors occur, the batch job will immediately be aborted, unless PML error handling has been used. Refer to Variables, Objects, Functions and Methods for information about PML.\nIf the project name, username or password are incorrectly specified while trying to gain access in batch mode, the application will immediately abort.\nIf the project name, username or password are incorrectly specified while trying to gain access in batch mode, the application will immediately abort.\nIf any other errors occur, the batch job will immediately be aborted, unless PML error handling has been used. Refer to Variables, Objects, Functions and Methods for information about PML.\nIf any other errors occur, the batch job will immediately be aborted, unless PML error handling has been used. Refer to Variables, Objects, Functions and Methods for information about PML.\nUnless the batch file is protected from access by other users, they will be able to read it and find out the username and password contained in it. You should make sure that operating system security is used to protect batch files.\nMany batch systems operate by taking a copy of the file submitted for batch execution. If this copy is held somewhere accessible to normal (non-system) users, then even if the user submitting the job has protected his own files, his username and password could still be read from the copy. Project Coordinators should consult their Computer Systems department to make sure that this is not the case on their particular computer.\nUnless the batch file is protected from access by other users, they will be able to read it and find out the username and password contained in it. You should make sure that operating system security is used to protect batch files.\nUnless the batch file is protected from access by other users, they will be able to read it and find out the username and password contained in it. You should make sure that operating system security is used to protect batch files.\nMany batch systems operate by taking a copy of the file submitted for batch execution. If this copy is held somewhere accessible to normal (non-system) users, then even if the user submitting the job has protected his own files, his username and password could still be read from the copy. Project Coordinators should consult their Computer Systems department to make sure that this is not the case on their particular computer.\nMany batch systems operate by taking a copy of the file submitted for batch execution. If this copy is held somewhere accessible to normal (non-system) users, then even if the user submitting the job has protected his own files, his username and password could still be read from the copy. Project Coordinators should consult their Computer Systems department to make sure that this is not the case on their particular computer.\nDo not send remote instructions to abort a batch job. The job interruption could occur while the COMMS DB is being updated.\nDo not use batch queues where CPU or elapsed time restrictions are in force.\nDo not execute batch jobs if there is a risk of running out of disk space.\nDo not send remote instructions to abort a batch job. The job interruption could occur while the COMMS DB is being updated.\nDo not send remote instructions to abort a batch job. The job interruption could occur while the COMMS DB is being updated.\nDo not use batch queues where CPU or elapsed time restrictions are in force.\nDo not use batch queues where CPU or elapsed time restrictions are in force.\nDo not execute batch jobs if there is a risk of running out of disk space.\nDo not execute batch jobs if there is a risk of running out of disk space.\n\n\n\nVariables, Objects, Functions and Methods\nBATCH\nBATCH COPY\nCOPY\nNOCOPY\nBATCH COPY\nAdmin\nAdmin\nCOPY\nCOPY\nCOPY\nMonitor\nMonitor\nDEFER, CURRENT\nEXCHANGE\nVariables, Objects, Functions and Methods\nDo not\nDo not\nDo not\n                            .----------<---------.\n                           /                     |\n>-- BAtch ---+--- COpy ---*--- ALL --------------|\n             |            |                      |\n             |            |--- NONE -------------|\n             |            |                      |\n             |            |--- dbtype -----------|\n             |            |                      |\n             |            \u2018--- dbname -----------|\n             |                                   |\n             |                .-----<------.     |\n             |               /             |     |\n             \u2018--- NOCOpy ---*--- dbtype ---|     |\n                            |              |     |\n                            \u2018--- dbname ---+-----+--->\ndbtype"}
{"Headers": "CURRENT", "Content": "The CURRENT command makes a database current.\nA MDB can contain up to 1000 DBs, and any number of the 1000 DBs can be described as current and accessed at one time. Databases which cannot be accessed are described as non-current or deferred. CURRENT makes the specified DB current and includes it at position n in the current list of the MDB (where n is in the range 1 to 1000 inclusive).\nMakes the databases PIPING/PIPING-A and PIPING/PIPING-C current\nDEFER EXCHANGE\nCURRENT PIPING/PIPING-A PIPING/PIPING-C\n    Makes the databases PIPING/PIPING-A and PIPING/PIPING-C current\nCURRENT PIPING/PIPING-A PIPING/PIPING-C\n    Makes the databases PIPING/PIPING-A and PIPING/PIPING-C current\nCURRENT PIPING/PIPING-A PIPING/PIPING-C\n                  .--------------.\n                 /               |\n>--- CUrrent ---*--- dbname n ---+--->\n\n\n\nCURRENT\ncurrent\nnon-current\ndeferred\nCURRENT\nn\nn\n                  .--------------.\n                 /               |\n>--- CUrrent ---*--- dbname n ---+--->"}
{"Headers": "DEFER", "Content": "The DEFER command makes a database deferred or non-current.\nA MDB can contain up to 1000 DBs, and any number of the 1000 DBs can be described as current and accessed at one time. Databases which cannot be accessed are described as non-current or deferred.\nMakes the databases PIPING/PIPING-A and PIPING/PIPING-C deferred.\nCURRENT EXCHANGE\nDEFER PIPING/PIPING-A PIPING/PIPING-C\n    Makes the databases PIPING/PIPING-A and PIPING/PIPING-C deferred.\nDEFER PIPING/PIPING-A PIPING/PIPING-C\n    Makes the databases PIPING/PIPING-A and PIPING/PIPING-C deferred.\nDEFER PIPING/PIPING-A PIPING/PIPING-C\n                .------------.\n               /             |\n>--- DEfer ---*--- dbname ---+--->\n\n\n\nDEFER\ncurrent\nnon-current\ndeferred\n                .------------.\n               /             |\n>--- DEfer ---*--- dbname ---+--->"}
{"Headers": "DELETE", "Content": "The DELETE command deletes unwanted inter-DB connection macros.\nThe DELETE command deletes inter-DB connection macros, which are created in a Design module when connections are made between elements in different databases. Such macros should normally be executed in Design, and are deleted by the system.\nTo protect against accidental deletion, the DELETE command cannot be abbreviated.\nDeletes macro number 3\nDELETE MACRO 3\nDeletes macro number 3\n>--- DELETE MACro n --->\n   \n\n\n\nDELETE\nDELETE\nDELETE\nn"}
{"Headers": "DEVICE", "Content": "Function:\nThe DEVICE command allows you to specify a different device type.\nDescription:\nA default output device will normally be set when you enter the application. If you want to change this, you should do so in Monitor using the DEVICE command. A message giving the default output devices for text and graphics is displayed when the application is started up.\nYou can also query the device type.\nNo graphics output\nGraphics output as normal.\nDEVICE TTY\nDEVICE NOGRAPHICS\n                  \nNo graphics output\nDEVICE GRAPHICS\nGraphics output as normal.\n>--- DEVice --+--- GRAphics ----.\n              |                 |\n              |--- NOGraphics --|\n              |                 |\n              \u2018--- TTY ---------+--->\n>--- Query DEVice --->\n\n\n\nDEVICE\nMonitor\nDEVICE\n.\n>--- DEVice --+--- GRAphics ----.\n              |                 |\n              |--- NOGraphics --|\n              |                 |\n              \u2018--- TTY ---------+--->"}
{"Headers": "EXCHANGE", "Content": "EXCHANGE replaces a current DB by a non-current DB.\nEXCHANGE replaces a current DB by a non-current DB. The DB names do not need to be listed in a particular order, since the MDB knows which are current and which are non-current, but they must be paired correctly if more than two names are listed.\nAssume that an MDB contains the following DBs as shown by a LIST command:\nThe command\nwould result in the new configuration\n/DESIGN\nCurrent DBS:   PIPING/PIPING-A    PIPING/PIPING-C    MASTER/CATA-D \nDeferred DBS:  PIPING/PIPING-B    MASTER/PIPING-E\n   \nEXCHANGE PIPING/PIPING-A PIPING/PIPING-B MASTER/PIPING-E MASTER/CATA-D\n/DESIGN \nCurrent DBS:    PIPING/PIPING-B   PIPING/PIPING-C    MASTER/PIPING-E \nDeferred DBS:   PIPING/PIPING-A   MASTER/CATA-D\n   \nCURRENT   DEFER\n                    .---------------------.\n                   /                      |\n>--- EXchange ----*--- dbname - dbname ---+--->\n\n\n\nEXCHANGE\nEXCHANGE\nLIST\ndbname\ndbname"}
{"Headers": "FINISH", "Content": "The FINISH command ends the session and returns to the operating system.\nThe abbreviated form of this command, FIN, can only be given in Monitor. To leave other modules, you must give the command in full.\n>--- FINish --->\n\n\n\nFINISH\nFIN\nMonitor"}
{"Headers": "LIST", "Content": "The LIST command lists most of the available project information.\nThe LIST command displays most of the project information held in the System Database.\nLIST USERS\nLists all the users in the project, with their access level (Free or General), and the Teams they belong to.\nLIST TEAMS\nLists all the teams in the project, with the users who are members of the teams and the DBs associated with them.\nLIST MDBS\nLists the MDBs in the project, and the current and deferred databases in each MDB.\nLIST DBS\nLists all the databases in the project, their types (Design, CATALOGUE etc) and the MDBs which contain them.\nLIST EXTERNAL\nLists all the foreign databases in the project.\nLIST TYPES\nLists all the database types (Design, CATALOGUE etc) in the project.\nLIST COPIES\nDisplays the names of all DBs which have been copied and the names under which the copies are filed.\nLIST MODULES\nDisplays information about modules in the current project.\nLIST FILES\nDisplays information about the database files in the current project.\nLIST SIZES\nLists the sizes (in pages and Mbytes) of all the databases in the project.\nLIST MACROS\nLists all the inter-DB macros in the project.\nLIST AREA 20\nDisplays information about databases in area 20. Refer to the Administration User Guide for information about database areas.\nLIST MESSAGES\nLists all the user messages in the project.\nLIST ALL\nDisplays all the above information.\nWORKING EXTRACTS\nList working extracts for specified user name.\nAUTHUSERS\nLists NT authorised users.\nLIST USERS\nLists all the users in the project, with their access level (Free or General), and the Teams they belong to.\nLIST TEAMS\nLists all the teams in the project, with the users who are members of the teams and the DBs associated with them.\nLIST MDBS\nLists the MDBs in the project, and the current and deferred databases in each MDB.\nLIST DBS\nLists all the databases in the project, their types (Design, CATALOGUE etc) and the MDBs which contain them.\nLIST EXTERNAL\nLists all the foreign databases in the project.\nLIST TYPES\nLists all the database types (Design, CATALOGUE etc) in the project.\nLIST COPIES\nDisplays the names of all DBs which have been copied and the names under which the copies are filed.\nLIST MODULES\nDisplays information about modules in the current project.\nLIST FILES\nDisplays information about the database files in the current project.\nLIST SIZES\nLists the sizes (in pages and Mbytes) of all the databases in the project.\nLIST MACROS\nLists all the inter-DB macros in the project.\nLIST AREA 20\nDisplays information about databases in area 20. Refer to the Administration User Guide for information about database areas.\nLIST MESSAGES\nLists all the user messages in the project.\nLIST ALL\nDisplays all the above information.\nWORKING EXTRACTS\nList working extracts for specified user name.\nAUTHUSERS\nLists NT authorised users.\nIf a user has a working extract for a database, then this will be opened instead of the owning database when the user enters a module. for example, if user A has a W.ext, then User A will use it; but User B will use the normal database. Refer to Database and Extracts in the Database Management Reference Manual for further information.\nRefer to Using Monitor for examples of output from some of these commands.\nLIST USERS\nLists all the users in the project, with their access level (Free or General), and the Teams they belong to.\nLIST TEAMS\nLists all the teams in the project, with the users who are members of the teams and the DBs associated with them.\nLIST MDBS\nLists the MDBs in the project, and the current and deferred databases in each MDB.\nLIST DBS\nLists all the databases in the project, their types (Design, CATALOGUE etc) and the MDBs which contain them.\nLIST EXTERNAL\nLists all the foreign databases in the project.\nLIST TYPES\nLists all the database types (Design, CATALOGUE etc) in the project.\nLIST COPIES\nDisplays the names of all DBs which have been copied and the names under which the copies are filed.\nLIST MODULES\nDisplays information about modules in the current project.\nLIST FILES\nDisplays information about the database files in the current project.\nLIST SIZES\nLists the sizes (in pages and Mbytes) of all the databases in the project.\nLIST MACROS\nLists all the inter-DB macros in the project.\nLIST AREA 20\nDisplays information about databases in area 20. Refer to the Administration User Guide for information about database areas.\nLIST MESSAGES\nLists all the user messages in the project.\nLIST ALL\nDisplays all the above information.\nWORKING EXTRACTS\nList working extracts for specified user name.\nAUTHUSERS\nLists NT authorised users.\n                .------<------------------------------.\n               /                                      |\n>--- LIst ----*--- USers -----------------------------|\n              |                                       |\n              |--- TEams -----------------------------|\n              |                                       |\n              |--- MDBs ------------------------------|\n              |                                       |\n              |--- DBs -------------------------------|\n              |                                       |\n              |--- FILES -----------------------------|\n              |                                       |\n              |--- DBs -------------------------------|\n              |                                       |\n              |--- EXTernal --------------------------|\n              |                                       |\n              |--- AREA n ----------------------------|\n              |                                       |\n              |--- TYpes -----------------------------|\n              |                                       |\n              |--- SIZe  -----------------------------|\n              |                                       |\n              |--- COpies ----------------------------|\n              |                                       |\n              |--- MOdules ---------------------------|\n              |                                       |\n              |--- MACRos ----------------------------|\n              |                                       |\n              |--- MESSages --------------------------|\n              |                                       |\n              |--- Authusers -------------------------|\n              |                                       |\n              |--- ALL -------------------------------|\n              |                                       |\n              \u2018--- WORKING EXTRACTS -+- FOR USERNAME--|\n                                     \u2018----------------+--->\n\n\n\nUsing Monitor\nLIST\nLIST\nExamples\nLIST USERS\nLIST TEAMS\nLIST MDBS\nLIST DBS\nLIST EXTERNAL\nLIST TYPES\nLIST COPIES\nLIST MODULES\nLIST FILES\nLIST SIZES\nLIST MACROS\nLIST AREA 20\nAdministration User Guide\nLIST MESSAGES\nLIST ALL\nWORKING EXTRACTS\nAUTHUSERS\nDatabase and Extracts in the\nUsing Monitor\n                .------<------------------------------.\n               /                                      |\n>--- LIst ----*--- USers -----------------------------|\n              |                                       |\n              |--- TEams -----------------------------|\n              |                                       |\n              |--- MDBs ------------------------------|\n              |                                       |\n              |--- DBs -------------------------------|\n              |                                       |\n              |--- FILES -----------------------------|\n              |                                       |\n              |--- DBs -------------------------------|\n              |                                       |\n              |--- EXTernal --------------------------|\n              |                                       |\n              |--- AREA n ----------------------------|\n              |                                       |\n              |--- TYpes -----------------------------|\n              |                                       |\n              |--- SIZe  -----------------------------|\n              |                                       |\n              |--- COpies ----------------------------|\n              |                                       |\n              |--- MOdules ---------------------------|\n              |                                       |\n              |--- MACRos ----------------------------|\n              |                                       |\n              |--- MESSages --------------------------|\n              |                                       |\n              |--- Authusers -------------------------|\n              |                                       |\n              |--- ALL -------------------------------|\n              |                                       |\n              \u2018--- WORKING EXTRACTS -+- FOR USERNAME--|\n                                     \u2018----------------+--->"}
{"Headers": "MESSAGE", "Content": "The MESSAGE command sends a message to other users.\nThe message will be displayed only to users already in the application when the command is given, and then only when they next change modules. A message consists of text enclosed in quotes, and it can contain several lines of text.\nYou can specify the destination in several ways, as shown in the examples.\nMESSAGE ID '64da-36' 'This is a message'\nThis message will be sent to the user with the process/host identifier 64da-ws36\nMESSAGE USER SAMPLE  \u2019This is a message\u2019 \nThis message will be sent to the user SAMPLE\nMESSAGE TEAM CABLE \u2019This is a message\u2019 \nThis message will be sent to all members of the CABLE team\nMESS \u2019THE LATEST PIPE ROUTING HAS BEEN APPROVED\u2019\nThis message will be sent to all users in the project.\nMESSAGE ID '64da-36' 'This is a message'\n\nThis message will be sent to the user with the process/host identifier 64da-ws36\nMESSAGE USER SAMPLE  \u2019This is a message\u2019 \n\nThis message will be sent to the user SAMPLE\nMESSAGE TEAM CABLE \u2019This is a message\u2019 \n\nThis message will be sent to all members of the CABLE team\nMESS \u2019THE LATEST PIPE ROUTING HAS BEEN APPROVED\u2019\n\nThis message will be sent to all users in the project.\nMESSAGE ID '64da-36' 'This is a message'\nThis message will be sent to the user with the process/host identifier 64da-ws36\nMESSAGE USER SAMPLE  \u2019This is a message\u2019 \nThis message will be sent to the user SAMPLE\nMESSAGE TEAM CABLE \u2019This is a message\u2019 \nThis message will be sent to all members of the CABLE team\nMESS \u2019THE LATEST PIPE ROUTING HAS BEEN APPROVED\u2019\nThis message will be sent to all users in the project.\n>--- MEssage ----+--- n ------------------.\n                 |                        |\n                 |--- HOST hostname ------|\n                 |                        |\n                 |--- ID descript --------|\n                 |                        |\n                 |--- LOGIN loginid ------|\n                 |                        |\n                 |--- USer userid --------|\n                 |                        |\n                 |--- TEam teamid --------|\n                 |                        |\n                 \u2018------------------------+-- text -->\n\n\n\nMESSAGE\nExamples\n>--- MEssage ----+--- n ------------------.\n                 |                        |\n                 |--- HOST hostname ------|\n                 |                        |\n                 |--- ID descript --------|\n                 |                        |\n                 |--- LOGIN loginid ------|\n                 |                        |\n                 |--- USer userid --------|\n                 |                        |\n                 |--- TEam teamid --------|\n                 |                        |\n                 \u2018------------------------+-- text -->"}
{"Headers": "PASSWORD", "Content": "The PASSWORD command changes your password.\nYou can change your password at any time. You may wish to do this if you suspect that an unauthorised user has gained access to your DBs.\nwhere password consists of up to six alphabetic characters.\n>--- PASSword password --->\nYou must take care when typing in the new password, because if you do not type what you think you are typing you will not be able to enter the application again. If this happens, ask your System Administrator to tell you what password you have set.\nYou must take care when typing in the new password, because if you do not type what you think you are typing you will not be able to enter the application again. If this happens, ask your System Administrator to tell you what password you have set.\nYou must take care when typing in the new password, because if you do not type what you think you are typing you will not be able to enter the application again. If this happens, ask your System Administrator to tell you what password you have set.\nNote:\nThis command can only be used if your Administrator has granted this capability. You can check this using the command \"Q PASSWORDLOCK\". If the PASSWORDLOCK is ON, ask your Administrator to change your password for you.\n\n\n\nPASSWORD\nNote\n:\npassword"}
{"Headers": "PROJECT", "Content": "The PROJECT command sets the current project.\nPROJECT SAM\n>--- PROJect --- proj_name --->\n\n\n\nFunction\nPROJECT"}
{"Headers": "PROTECT", "Content": "The PROTECT command allows you to change your access rights to DBs.\nYou can temporarily change your access rights to DBs. You can only reduce your access rights from the set state, never increase them. The change will only apply in the current session.\nYou can only change access rights to the current MDB.\nAn example of using the PROTECT command is shown below:\nUser SAMPLE enters Plant and selects the MDB to which he has Read/Write access. This MDB contains two current DBs named PIPING/AREA-A and PIPING/AREA-B. The STATUS command will list the DBs as follows:\nSAMPLE changes his access level to the DB /AREA-B to Read-only status by the command:\nThe STATUS command will now list the DBs as follows:\nDB                                TYPE  MODE \nPIPING/AREA-A                     DESI  RW \nPIPING/AREA-B                     DESI  RW\nPROT  PIPING/AREA-B  READ\nDB                                TYPE  MODE\nPIPING/AREA-A                     DESI  RW \nPIPING/AREA-B                     DESI  R\n   \n                   .--------------<-----------.\n                  /                           |\n>--- PROtect ----*--- dbname ---+--- RW ------|\n                                |             |\n                                |--- Read ----|\n                                |             |\n                                \u2018--- None ----+--->\n\n\n\nPROTECT\nreduce\nSTATUS\ndbname"}
{"Headers": "RUN", "Content": "The RUN command allows you to run modules which are not available through the normal module-changing commands.\nThis command should only be used with the advice of AVEVA. See the copyright page at the front of this manual for access to the addresses and telephone numbers of AVEVA offices.\n>--- RUN module --->\n   \n\n\n\nmodule"}
{"Headers": "SET", "Content": "The SET command sets the current team.\nOnce a team has been set, you can omit the team name when you specify the database name; for example, in a LIST command.\nQueries the database PIPING/AREA-A\nSET TEAM PIPING Q DB /AREA-A\nQueries the database PIPING/AREA-A\nSET TEAM PIPING Q DB /AREA-A\nQueries the database PIPING/AREA-A\nSET TEAM PIPING Q DB /AREA-A\n>--- SET TEam teamid --->\n\n\n\nSET\nLIST\nExamples"}
{"Headers": "STATUS", "Content": "The STATUS command gives information about your current status and the DBs to which you have access.\nThe output from the command is shown in the example:\nThis shows that in the project SAM, a user with identifier SYSTEM is logged in to workstation PC046. Xd0 is a unique identifier based on SAMPLE\u2019s process number. SYSTEM is a member of the 16 teams listed. They have selected an MDB called /SAMPLE. Their current databases are listed.\nProject:  SAM\nUser:     SYSTEM (Xd0-PC046)\nTeams:    MASTER SAMPLE DEMO HANGER HVAC PIPE STRUC\n       DRAFTADMIN ISOADMIN HSADMIN CATADMIN ADMIN CATS EQUI\n       TRAINING PARAGONADMIN\nMDB:      /SAMPLE\n1  SAMPLE/DESI                                    RW PRIMARY\n2  STRUC/ASLTMPL                                  RW PRIMARY\n3  STRUC/TEMPLATE                                 RW PRIMARY\n4  EQUI/EQUITMPL                                  RW PRIMARY\n5  PIPE/ISOD                                      RW PRIMARY\n6  SAMPLE/PADD                                    RW PRIMARY\n7  ADMIN/PADD                                     RW PRIMARY\n8  MASTER/COMP                                     R FOREIGN\n9  MASTER/PIPECATA                                 R FOREIGN\n10  MASTER/PIPEOLD                                 R FOREIGN\n11  MASTER/STLCATA                                 R FOREIGN\n12  MASTER/HVACCATA                                R FOREIGN\n13  MASTER/SUPPCATA                                R FOREIGN\n14  MASTER/EQUICATA                                R FOREIGN\n15  MASTER/ASLCATA                                 R FOREIGN\n16  MASTER/PADD                                    R FOREIGN\n17  MASTER/DICT                                    R FOREIGN\n18  MASTER/PROP                                    R FOREIGN\nDeferred DBS:\n        **NONE**\n>--- STATus --->\n\n\n\nSTATUS"}
{"Headers": "SYSTAT", "Content": "The SYSTAT command gives system status information about the current project.\nThe SYSTAT command lists all users who are accessing the project, the modules and databases which they are using, and whether they are examining (Read-only status) or modifying (Read/Write status) the database. It also gives the unique identifier, login id and host name for each user.\nYou list the system status of a given user, module, MDB or host using the commands shown in the syntax graph.\nThis shows that user SYSTEM is logged in and using the application for work on Project /SAMPLE. The user\u2019s unique identifier is Xd0. The user is using Monitor and not accessing any databases\n  PROJECT SAM\n=============\nUser SYSTEM (Xd0-PC046)\nName user.name (user)\nHost PC046\nEntered 15:27 23 Apr\nModule MONITOR\nMDB /SAMPLE\nDB            MODE\nSAMPLE/DESI   R\nSTRUC/ASLTMPL R\nSTRUC/TEMPLATE               R\nEQUI/EQUITMPL R\nPIPE/ISOD     R\nSAMPLE/PADD   R\nADMIN/PADD    R\nMASTER/COMP   R\nMASTER/PIPECATA              R\nMASTER/PIPEOLD               R\nMASTER/STLCATA               R\nMASTER/HVACCATA              R\nMASTER/SUPPCATA              R\nMASTER/EQUICATA              R\nMASTER/ASLCATA               R\nMASTER/PADD   R\nMASTER/DICT   R\nMASTER/PROP   R\n 1 user(s) listed\n>--- SYStat ---+--- USER _ID     ------.\n               |                       |\n               |--- NAME \u2019login_id\u2019 ---|\n               |                       |\n               |--- HOST \u2019host_id -----|\n               |                       |\n               |--- MODUle module -----|\n               |                       |\n               |--- MDB mdb_name ------|\n               |                       |\n               \u2018-----------------------+--->\n\n\n\nSYSTAT\nSYSTAT\n PROJECT SAM\n=============\nUser SYSTEM (Xd0-PC046)\nName user.name (user)\nHost PC046\nEntered 15:27 23 Apr\nModule MONITOR\nMDB /SAMPLE\nDB            MODE\nSAMPLE/DESI   R\nSTRUC/ASLTMPL R\nSTRUC/TEMPLATE               R\nEQUI/EQUITMPL R\nPIPE/ISOD     R\nSAMPLE/PADD   R\nADMIN/PADD    R\nMASTER/COMP   R\nMASTER/PIPECATA              R\nMASTER/PIPEOLD               R\nMASTER/STLCATA               R\nMASTER/HVACCATA              R\nMASTER/SUPPCATA              R\nMASTER/EQUICATA              R\nMASTER/ASLCATA               R\nMASTER/PADD   R\nMASTER/DICT   R\nMASTER/PROP   R\n 1 user(s) listed\nMonitor\n_ID     \n\u2019login_id\u2019 \n\u2019host_id \nmodule \nmdb_name "}
{"Headers": "USERNAME", "Content": "The USERNAME command specifies a username and password.\nUsers can be queried if no username is set, but the username must be given before an MDB is set.\nUSER \nSYSTEM/XXXXXX\n   \n>--- USERname --- newline --- text --->\nNote:\nWhen working in non-graphics mode, it is recommended that you enter the USERNAME command on its own, and you will then be prompted to enter the username and password, which will not be echoed on the screen. Do not follow the command immediately by the username and password, as this may be a security risk.\n\n\n\nUSERNAME\nNote\n:\nUSERNAME"}
{"Headers": "Error Messages", "Content": "The following is a complete list of those messages specific to the Monitor module that may be output to the terminal (with message number) and message file (with message number suppressed). All such messages will have a message number beginning with 39. Any other messages that may be output are not described here as they are not specific to the Monitor module.\n(39,3)\nMDB not found\nThe MDB name referred to does not exist in the current project.\n(39,4)\nDB not found\nThe DB name referred to does not exist in the current project.\n(39,5)\nTEAM not found\nThe team named does not exist in the current project.\n(39,6)\nInsufficient status to set this mode\nUser\u2019s access rights do not allow him to modify the relevant files.\n(39,7)\nUSER not found\nThe user named is not a member of the specified or current team.\n(39,8)\nMODULE not found\nNo runfile for the specified module can be found in the current Project Database. The runfile must be set by the System Administrator using Admin.\n(39,11)\nDB not current\nThe DB specified in an EXCHANGE or DEFER command is not current within the MDB.\n(39,12)\nUser number not found\nNo user is currently logged in under the specified id number.\n(39,13)\nResume file not found\nNo runfile for the specified module can be found in the current Project Database. The runfile must be set by the System Administrator using Admin.\n(39,14)\nInsufficient status to run module\nYou do not have access rights to the specified module.\n(39,15)\nNo MDB has been specified\nAn MDB must be selected before Monitor will transfer control to most other modules or before individual DBs can be made current.\n(39,16)\nDB is not part of this MDB\nThe DB referred to is not within the specified MDB, or within the current MDB if none was specified.\n(39,17)\nDB already current\n.\nThe DB specified in a CURRENT or EXCHANGE command is already current within the MDB.\n(39,18)\nFiling error - cannot delete macro file\nThe macro identification number given in a DELETE MACRO command is not valid.\n(39,19)\nCannot delete - macro not yet read\nThe DELETE MACRO command cannot be used until the inter-DB connection macro specified has been read by the recipient team.\n(39,20)\nCurrent position out of range\nThe list position for adding a current DB to an MDB must be in the range 1 to 1000.\n(39,21)\nThere are already 1000 current DBs\nA maximum of 1000 DBs are accessible within an MDB at any time. Use the EXCHANGE command to substitute the required DB for one not currently needed.\n(39,22)\nActions turned off\nThe ACTIONS OFF command has been issued.\n(39,23)\nBATCH command ignored for interactive use\nThe BATCH command is only valid if entry was made using the batch option.\n(39,25)\n/* is not a valid MDB\nThe MDB must be fully specified by name; wildcard characters are not allowed in this context.\n(39,36)\nUser password not changed - passwordLock is on. Please contact the system administrator at location =0/0 to change passwords.\nYour Administrator has set the PASSWORDLOCK ON. You may not reset your password in Monitor.\n(39,3)\nMDB not found\n\nThe MDB name referred to does not exist in the current project.\n(39,4)\nDB not found\n\nThe DB name referred to does not exist in the current project.\n(39,5)\nTEAM not found\n\nThe team named does not exist in the current project.\n(39,6)\nInsufficient status to set this mode\n\nUser\u2019s access rights do not allow him to modify the relevant files.\n(39,7)\nUSER not found\n\nThe user named is not a member of the specified or current team.\n(39,8)\nMODULE not found\n\nNo runfile for the specified module can be found in the current Project Database. The runfile must be set by the System Administrator using Admin.\n(39,11)\nDB not current\n\nThe DB specified in an EXCHANGE or DEFER command is not current within the MDB.\n(39,12)\nUser number not found\n\nNo user is currently logged in under the specified id number.\n(39,13)\nResume file not found\n\nNo runfile for the specified module can be found in the current Project Database. The runfile must be set by the System Administrator using Admin.\n(39,14)\nInsufficient status to run module\n\nYou do not have access rights to the specified module.\n(39,15)\nNo MDB has been specified\n\nAn MDB must be selected before Monitor will transfer control to most other modules or before individual DBs can be made current.\n(39,16)\nDB is not part of this MDB\n\nThe DB referred to is not within the specified MDB, or within the current MDB if none was specified.\n(39,17)\nDB already current\n.\nThe DB specified in a CURRENT or EXCHANGE command is already current within the MDB.\n(39,18)\nFiling error - cannot delete macro file\n\nThe macro identification number given in a DELETE MACRO command is not valid.\n(39,19)\nCannot delete - macro not yet read\n\nThe DELETE MACRO command cannot be used until the inter-DB connection macro specified has been read by the recipient team.\n(39,20)\nCurrent position out of range\n\nThe list position for adding a current DB to an MDB must be in the range 1 to 1000.\n(39,21)\nThere are already 1000 current DBs\n\nA maximum of 1000 DBs are accessible within an MDB at any time. Use the EXCHANGE command to substitute the required DB for one not currently needed.\n(39,22)\nActions turned off\n\nThe ACTIONS OFF command has been issued.\n(39,23)\nBATCH command ignored for interactive use\n\nThe BATCH command is only valid if entry was made using the batch option.\n(39,25)\n/* is not a valid MDB\n\nThe MDB must be fully specified by name; wildcard characters are not allowed in this context.\n(39,36)\nUser password not changed - passwordLock is on. Please contact the system administrator at location =0/0 to change passwords.\n\nYour Administrator has set the PASSWORDLOCK ON. You may not reset your password in Monitor.\n\n(39,3)\nMDB not found\nThe MDB name referred to does not exist in the current project.\n(39,4)\nDB not found\nThe DB name referred to does not exist in the current project.\n(39,5)\nTEAM not found\nThe team named does not exist in the current project.\n(39,6)\nInsufficient status to set this mode\nUser\u2019s access rights do not allow him to modify the relevant files.\n(39,7)\nUSER not found\nThe user named is not a member of the specified or current team.\n(39,8)\nMODULE not found\nNo runfile for the specified module can be found in the current Project Database. The runfile must be set by the System Administrator using Admin.\n(39,11)\nDB not current\nThe DB specified in an EXCHANGE or DEFER command is not current within the MDB.\n(39,12)\nUser number not found\nNo user is currently logged in under the specified id number.\n(39,13)\nResume file not found\nNo runfile for the specified module can be found in the current Project Database. The runfile must be set by the System Administrator using Admin.\n(39,14)\nInsufficient status to run module\nYou do not have access rights to the specified module.\n(39,15)\nNo MDB has been specified\nAn MDB must be selected before Monitor will transfer control to most other modules or before individual DBs can be made current.\n(39,16)\nDB is not part of this MDB\nThe DB referred to is not within the specified MDB, or within the current MDB if none was specified.\n(39,17)\nDB already current\n.\nThe DB specified in a CURRENT or EXCHANGE command is already current within the MDB.\n(39,18)\nFiling error - cannot delete macro file\nThe macro identification number given in a DELETE MACRO command is not valid.\n(39,19)\nCannot delete - macro not yet read\nThe DELETE MACRO command cannot be used until the inter-DB connection macro specified has been read by the recipient team.\n(39,20)\nCurrent position out of range\nThe list position for adding a current DB to an MDB must be in the range 1 to 1000.\n(39,21)\nThere are already 1000 current DBs\nA maximum of 1000 DBs are accessible within an MDB at any time. Use the EXCHANGE command to substitute the required DB for one not currently needed.\n(39,22)\nActions turned off\nThe ACTIONS OFF command has been issued.\n(39,23)\nBATCH command ignored for interactive use\nThe BATCH command is only valid if entry was made using the batch option.\n(39,25)\n/* is not a valid MDB\nThe MDB must be fully specified by name; wildcard characters are not allowed in this context.\n(39,36)\nUser password not changed - passwordLock is on. Please contact the system administrator at location =0/0 to change passwords.\nYour Administrator has set the PASSWORDLOCK ON. You may not reset your password in Monitor.\n\n\n\nMonitor\nMonitor\n(39,3)\nMDB not found\n(39,4)\nDB not found\n(39,5)\nTEAM not found\n(39,6)\nInsufficient status to set this mode\n(39,7)\nUSER not found\n(39,8)\nMODULE not found\nAdmin\n(39,11)\nDB not current\nEXCHANGE\nDEFER\n(39,12)\nUser number not found\n(39,13)\nResume file not found\nAdmin\n(39,14)\nInsufficient status to run module\n(39,15)\nNo MDB has been specified\nMonitor\n(39,16)\nDB is not part of this MDB\n(39,17)\nDB already current\nCURRENT\nEXCHANGE\n(39,18)\nFiling error - cannot delete macro file\nDELETE MACRO\n(39,19)\nCannot delete - macro not yet read\nDELETE MACRO\n(39,20)\nCurrent position out of range\n(39,21)\nThere are already 1000 current DBs\nEXCHANGE\n(39,22)\nActions turned off\nACTIONS OFF\n(39,23)\nBATCH command ignored for interactive use\nBATCH\n(39,25)\n/* is not a valid MDB\n(39,36)\nUser password not changed - passwordLock is on. Please contact the system administrator at location =0/0 to change passwords."}
{"Headers": "PDMSLOG", "Content": "The following menu maps shows the options available from the main Monitor menu bar.\nThe environment variable PDMSLOGOPT can be set to any or all of these settings to get more info or recorded into the file pointed at by PDMSL0G. Some of this is available in 10.5Call in 11.1 onwards.\nSLOT - Records which 'slot' each user gets in the Comms DB (This 'slot' info is what comes out in the 'sys' command and the slot is what PDMS uses to try and work out who has things claimed^ in use etcj\nCOMMDB - When queuing for access to Comms Dbito get your slot)\nMISCDB - When queuing for access to Misc Dbifor messagesCinter-db macros)\nMDB - Records selection of an MDB in Monitor or MDB mode\nWRITER] Records if, with write access to an UPDATE db, the db itself thinks there was someone else writing to it, This could be useful info if updates are lost or people suspect 2 writersD. You could probably deliberately cause this with one writer, then 'mv' ing the file irix and going to 2nd writer. The 1st writer may later have a Dab crashI\nMODSW - Records which module going to nextDCould be used to see how often certain modules are used.\nEXPUNGE - Records info of who is being expunged from which slot when\nEXPUNGE command usedCor auto] expunged.\nCORE - More for developers - forces a core to be dumped even if the program would not normally do soDYou also get a core if any TRACE flag is set (can just do $r23+ by itself.)\nSet any combination, no space neededibut are allowed.) for example,,\nset PDMSLOGOPT=SLOTEXPUNGEMODSW\nset PDMSLOGOPT=COMMDB MISCDB WRITER\n\n\n\nMonitor"}
{"Headers": "Symbol Keys", "Content": "The following list of the symbol key (i.e. the SKEY text attribute) and the plotted symbol used to identify each type of component on isometric drawings. There is a section for each generic type. The sections are in alphabetic order of generic type:\nBEND (refer to ELBOw)\nRefer to ELBO or BEND Symbol Keys.\nCAP\nRefer to CAP Symbol Keys.\nCLOSure\nRefer to CLOS Symbol Keys.\nCOUPling\nRefer to COUP Symbol Keys.\nCROSs\nRefer to CROS Symbol Keys.\nELBOw\nRefer to ELBO or BEND Symbol Keys.\nFBLInd (Blind Flange)\nRefer to FBLI Symbol Keys.\nFILTer\nRefer to FILT Symbol Keys.\nFLANge\nRefer to FLAN Symbol Keys.\nFTUBe (Fixed-length\nTube)\nRefer to FTUB Symbol Keys.\nINSTrument\nRefer to INST Symbol Keys.\nLJSEnd (Lap Joint, Stub End)\nRefer to LJSE Symbol Keys.\nOLET (refer to TEE)\nRefer to TEE or OLET Symbol Keys.\nPCOMponent\n(Pipe Component)\nRefer to PCOM Symbol Keys\nREDUcer\nRefer to REDU Symbol Keys.\nSHU\nRefer to SHU Symbol Keys.\nTEE\nRefer to TEE or OLET Symbol Keys.\nTRAP\nRefer to TRAP Symbol Keys.\nUNIOn\nRefer to UNIO Symbol Keys.\nUNIVersal\nRefer to UNIVERSAL Symbol Key.\nVALVe\nRefer to VALV Symbol Keys.\nVENT\nRefer to VENT Symbol Keys.\nVFWAy (Four-way Valve)\nRefer to VFWA Symbol Keys.\nVTWAy (Three-way valve)\nRefer to VTWA Symbol Keys.\nWELD\nRefer to WELD Symbol Keys.\nFLOR (Pipe through floor)\nRefer to Floor Penetration ATTA Symbol.\nBEND (refer to ELBOw)\nRefer to ELBO or BEND Symbol Keys.\nCAP\nRefer to CAP Symbol Keys.\nCLOSure\nRefer to CLOS Symbol Keys.\nCOUPling\nRefer to COUP Symbol Keys.\nCROSs\nRefer to CROS Symbol Keys.\nELBOw\nRefer to ELBO or BEND Symbol Keys.\nFBLInd (Blind Flange)\nRefer to FBLI Symbol Keys.\nFILTer\nRefer to FILT Symbol Keys.\nFLANge\nRefer to FLAN Symbol Keys.\nFTUBe (Fixed-length\nTube)\nRefer to FTUB Symbol Keys.\nINSTrument\nRefer to INST Symbol Keys.\nLJSEnd (Lap Joint, Stub End)\nRefer to LJSE Symbol Keys.\nOLET (refer to TEE)\nRefer to TEE or OLET Symbol Keys.\nPCOMponent\n(Pipe Component)\nRefer to PCOM Symbol Keys\nREDUcer\nRefer to REDU Symbol Keys.\nSHU\nRefer to SHU Symbol Keys.\nTEE\nRefer to TEE or OLET Symbol Keys.\nTRAP\nRefer to TRAP Symbol Keys.\nUNIOn\nRefer to UNIO Symbol Keys.\nUNIVersal\nRefer to UNIVERSAL Symbol Key.\nVALVe\nRefer to VALV Symbol Keys.\nVENT\nRefer to VENT Symbol Keys.\nVFWAy (Four-way Valve)\nRefer to VFWA Symbol Keys.\nVTWAy (Three-way valve)\nRefer to VTWA Symbol Keys.\nWELD\nRefer to WELD Symbol Keys.\nFLOR (Pipe through floor)\nRefer to Floor Penetration ATTA Symbol.\nSymbol Key Reference Index is an alphabetical list of symbol keys cross-referenced to the generic types of the components to which they refer. The following information is given for each SKEY:\nComponent description\nThe actual component description\nSKEY\nA four-letter identifier\nPlotted symbol\nThe symbol plotted on isometrics, plus dimensions (in mm)\nP-points\nThe position and direction of the P-points with respect to the plotted symbol. P-points needed to specify components fully are shown against the symbols. P-points which are optional are not shown, but their effects are explained in the notes when appropriate.\nNotes\nThe numbers in the right-hand column refer to the notes at the end of each section.\nComponent description\nThe actual component description\nSKEY\nA four-letter identifier\nPlotted symbol\nThe symbol plotted on isometrics, plus dimensions (in mm)\nP-points\nThe position and direction of the P-points with respect to the plotted symbol. P-points needed to specify components fully are shown against the symbols. P-points which are optional are not shown, but their effects are explained in the notes when appropriate.\nNotes\nThe numbers in the right-hand column refer to the notes at the end of each section.\nP-points\nWhen defining piping components in PARAGON, the user must remember the following rules so that ISODRAFT can produce isometrics correctly:\nBEND (refer to ELBOw)\nRefer to ELBO or BEND Symbol Keys.\nCAP\nRefer to CAP Symbol Keys.\nCLOSure\nRefer to CLOS Symbol Keys.\nCOUPling\nRefer to COUP Symbol Keys.\nCROSs\nRefer to CROS Symbol Keys.\nELBOw\nRefer to ELBO or BEND Symbol Keys.\nFBLInd (Blind Flange)\nRefer to FBLI Symbol Keys.\nFILTer\nRefer to FILT Symbol Keys.\nFLANge\nRefer to FLAN Symbol Keys.\nFTUBe (Fixed-length\nTube)\nRefer to FTUB Symbol Keys.\nINSTrument\nRefer to INST Symbol Keys.\nLJSEnd (Lap Joint, Stub End)\nRefer to LJSE Symbol Keys.\nOLET (refer to TEE)\nRefer to TEE or OLET Symbol Keys.\nPCOMponent\n(Pipe Component)\nRefer to PCOM Symbol Keys\nREDUcer\nRefer to REDU Symbol Keys.\nSHU\nRefer to SHU Symbol Keys.\nTEE\nRefer to TEE or OLET Symbol Keys.\nTRAP\nRefer to TRAP Symbol Keys.\nUNIOn\nRefer to UNIO Symbol Keys.\nUNIVersal\nRefer to UNIVERSAL Symbol Key.\nVALVe\nRefer to VALV Symbol Keys.\nVENT\nRefer to VENT Symbol Keys.\nVFWAy (Four-way Valve)\nRefer to VFWA Symbol Keys.\nVTWAy (Three-way valve)\nRefer to VTWA Symbol Keys.\nWELD\nRefer to WELD Symbol Keys.\nFLOR (Pipe through floor)\nRefer to Floor Penetration ATTA Symbol.\nComponent description\nThe actual component description\nSKEY\nA four-letter identifier\nPlotted symbol\nThe symbol plotted on isometrics, plus dimensions (in mm)\nP-points\nThe position and direction of the P-points with respect to the plotted symbol. P-points needed to specify components fully are shown against the symbols. P-points which are optional are not shown, but their effects are explained in the notes when appropriate.\nNotes\nThe numbers in the right-hand column refer to the notes at the end of each section.\nP0 is automatically set and defines the origin of the component.\nFor two-way components, the arrive and leave p-points must be numbered P1 and P2 (not necessarily in that order). For two-way valves, the spindle direction must be indicated by P3.\nFor three-way components, the offline leg must be indicated by P3. The spindle direction for three-way valves must be specified by using a p-point greater than P3, which must have its bore unset.\nFor four-way components, the two straight-through flows must have p-points P1/P2 and P3/P4. The spindle direction for four-way valves must be specified by using a p-point greater than P4, which must have its bore unset.\nFor eccentric reducers without a connection point, the flat side must be indicated by P3. Eccentric reducers with a connection point must use P3, with a valid bore set, to indicate the connection point and must use P9, with bore unset, for orientation of the flat side.\nFor U-bends (defined as bends of more than 135 degrees), the p-points must be set as shown for each symbol.\nP0 is automatically set and defines the origin of the component.\nP0 is automatically set and defines the origin of the component.\nFor two-way components, the arrive and leave p-points must be numbered P1 and P2 (not necessarily in that order). For two-way valves, the spindle direction must be indicated by P3.\nFor two-way components, the arrive and leave p-points must be numbered P1 and P2 (not necessarily in that order). For two-way valves, the spindle direction must be indicated by P3.\nFor three-way components, the offline leg must be indicated by P3. The spindle direction for three-way valves must be specified by using a p-point greater than P3, which must have its bore unset.\nFor three-way components, the offline leg must be indicated by P3. The spindle direction for three-way valves must be specified by using a p-point greater than P3, which must have its bore unset.\nFor four-way components, the two straight-through flows must have p-points P1/P2 and P3/P4. The spindle direction for four-way valves must be specified by using a p-point greater than P4, which must have its bore unset.\nFor four-way components, the two straight-through flows must have p-points P1/P2 and P3/P4. The spindle direction for four-way valves must be specified by using a p-point greater than P4, which must have its bore unset.\nFor eccentric reducers without a connection point, the flat side must be indicated by P3. Eccentric reducers with a connection point must use P3, with a valid bore set, to indicate the connection point and must use P9, with bore unset, for orientation of the flat side.\nFor eccentric reducers without a connection point, the flat side must be indicated by P3. Eccentric reducers with a connection point must use P3, with a valid bore set, to indicate the connection point and must use P9, with bore unset, for orientation of the flat side.\nFor U-bends (defined as bends of more than 135 degrees), the p-points must be set as shown for each symbol.\nFor U-bends (defined as bends of more than 135 degrees), the p-points must be set as shown for each symbol.\nNote: How to define symbol keys is described in Symbol Keys, of the ISODRAFT User Guide.\n\n\n\nELBO or BEND Symbol Keys\nCAP Symbol Keys\nCLOS Symbol Keys\nCOUP Symbol Keys\nCROS Symbol Keys\nELBO or BEND Symbol Keys\nFBLI Symbol Keys\nFILT Symbol Keys\nFLAN Symbol Keys\nFTUB Symbol Keys\nINST Symbol Keys\nLJSE Symbol Keys\nTEE or OLET Symbol Keys\nPCOM Symbol Keys\nREDU Symbol Keys\nSHU Symbol Keys\nTEE or OLET Symbol Keys\nTRAP Symbol Keys\nUNIO Symbol Keys\nUNIVERSAL Symbol Key\nVALV Symbol Keys\nVENT Symbol Keys\nVFWA Symbol Keys\nVTWA Symbol Keys\nWELD Symbol Keys\nFloor Penetration ATTA Symbol\nSymbol Key Reference Index\nNote\n:\nSymbol Keys\nsymbol key\nplotted symbol\ngeneric type\nELBO or BEND Symbol Keys\nCAP Symbol Keys\nCLOS Symbol Keys\nCOUP Symbol Keys\nCROS Symbol Keys\nELBO or BEND Symbol Keys\nFBLI Symbol Keys\nFILT Symbol Keys\nFLAN Symbol Keys\nFTUB Symbol Keys\nINST Symbol Keys\nLJSE Symbol Keys\nTEE or OLET Symbol Keys\nPCOM Symbol Keys\nREDU Symbol Keys\nSHU Symbol Keys\nTEE or OLET Symbol Keys\nTRAP Symbol Keys\nUNIO Symbol Keys\nUNIVERSAL Symbol Key\nVALV Symbol Keys\nVENT Symbol Keys\nVFWA Symbol Keys\nVTWA Symbol Keys\nWELD Symbol Keys\nFloor Penetration ATTA Symbol\nSymbol Key Reference Index\noptional\norigin\ntwo-way components\ntwo-way valves\nthree-way components\nthree-way valves\nfour-way components\nfour-way valves\neccentric reducers without a connection point\nEccentric reducers with a connection point\nU-bends"}
{"Headers": "CAP Symbol Keys", "Content": "Cap - Butt Weld\nKABW\n\n\n1\nCap -\nCompression\nKACP\n\n\n1\nCap - Screwed\nKASC\n\n\n1\nCap - Socket Weld\nKASW\n\n\n\nNote:\n1\nThe p-point configurations refer only to Caps used solely for blanking and are positioned on the axis of the appropriate face (depending on type). Caps with different p-point configurations, such as \u2018flipped\u2019 Caps (where P1 is Pleave and P2 is Parrive) or Caps used as Reducers, can result in incorrect output.\n1\nThe p-point configurations refer only to Caps used solely for blanking and are positioned on the axis of the appropriate face (depending on type). Caps with different p-point configurations, such as \u2018flipped\u2019 Caps (where P1 is Pleave and P2 is Parrive) or Caps used as Reducers, can result in incorrect output.\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nCap - Butt Weld\nKABW\n1\nCap -\nCompression\nKACP\n1\nCap - Screwed\nKASC\n1\nCap - Socket Weld\nKASW\n1\nThe p-point configurations refer only to Caps used solely for blanking and are positioned on the axis of the appropriate face (depending on type). Caps with different p-point configurations, such as \u2018flipped\u2019 Caps (where P1 is Pleave and P2 is Parrive) or Caps used as Reducers, can result in incorrect output.\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote"}
{"Headers": "CLOS Symbol Keys", "Content": "Pipe Block\nFixed Length\nPF\n\n\n\nPipe Block\nVariable Length\nPV\n\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nPipe Block\nFixed Length\nPF\nPipe Block\nVariable Length\nPV\n\n\n\nNote"}
{"Headers": "COUP Symbol Keys", "Content": "Nipple - Screwed\nNRSC\n\n\n\nNipple - Screwed\nNBSC\n\n\n\nCoupling -\nCompression\nCOCP\n\n\n\nCoupling - Screwed\nCOSC\n\n\n\nCoupling - Socket\nWeld\nCOSW\n\n\n\nHalf Coupling\n- Screwed\nCFSC\n\n\n\nHalf Coupling\n- Socket Weld\nCFSW\n\n\n\nButt Weld Elbolet\nCEBW\n\n\n1\nSocket Weld Elbolet\nCESW\n\n\n1\nScrewed Elbolet\nCESC\n\n\n1\nCentre Flange\nCPCF\n\n\n\nWatertight bulkhead and deck\nCPWP\n\n\n\nWelded sleeve thru pipe\nCPWT\n\n\n\nWelded sleeve and pipe\nCPWW\n\n\n\nNote:\n1\nThe dimensions of these components depend upon plotted leg length. The default plotted leg length is 9mm, but the user can set this to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n1\nThe dimensions of these components depend upon plotted leg length. The default plotted leg length is 9mm, but the user can set this to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nNipple - Screwed\nNRSC\nNipple - Screwed\nNBSC\nCoupling -\nCompression\nCOCP\nCoupling - Screwed\nCOSC\nCoupling - Socket\nWeld\nCOSW\nHalf Coupling\n- Screwed\nCFSC\nHalf Coupling\n- Socket Weld\nCFSW\nButt Weld Elbolet\nCEBW\n1\nSocket Weld Elbolet\nCESW\n1\nScrewed Elbolet\nCESC\n1\nCentre Flange\nCPCF\nWatertight bulkhead and deck\nCPWP\nWelded sleeve thru pipe\nCPWT\nWelded sleeve and pipe\nCPWW\n1\nThe dimensions of these components depend upon plotted leg length. The default plotted leg length is 9mm, but the user can set this to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n\n\n\nNote"}
{"Headers": "CROS Symbol Keys", "Content": "Cross - Butt Weld\nCRBW\n\n\n2\nCross - Socket Weld\nCRSW\n\n\n2\nCross - Compression\nCRCP\n\n\n2\nCross - Flanged\nCRFL\n\n\n2\nCross - Screwed\nCRSC\n\n\n2\nCross - Set on\nCRSO\n\n\n1, 2\nCross - Set on\nReinforced\nCRRF\n\n\n1,2\nCross - Generic Y-\ntype with variable angle out- and off- legs\nX@**\n\n\n3,4,5\nNote:\n1\nThe positions of P3 and P4 along the vertical axis are important for deriving correct cut pipe lengths. The vertical displacements of P3 and P4 are determined by the points at which the offline legs intersect the main line. P0, P1, P2, P3 and P4 will be coincident when the offline leg has the same bore as the main line.\n2\nThe dimensions of all Cross components depend upon plotted leg length. The default plotted leg length is 9mm, but the user can set this to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n3\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n4\nThe @ character in the symbol key is replaced automatically by an integer in the range 1 to 4, depending on the relative bore size of the connections, with 1 assigned to the largest bore. It is important to note the bore size if redefining the SKEYS for X1**, X2**, X3** or X4**.\n5\nFlanged connections on generic Y-type fittings are represented on the isometric on the tube only. This is due to the fact that the y-type fitting is user-definable and flanged representation on the component cannot be enforced. ELBO or BEND Symbol Keys\n1\nThe positions of P3 and P4 along the vertical axis are important for deriving correct cut pipe lengths. The vertical displacements of P3 and P4 are determined by the points at which the offline legs intersect the main line. P0, P1, P2, P3 and P4 will be coincident when the offline leg has the same bore as the main line.\n2\nThe dimensions of all Cross components depend upon plotted leg length. The default plotted leg length is 9mm, but the user can set this to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n3\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n4\nThe @ character in the symbol key is replaced automatically by an integer in the range 1 to 4, depending on the relative bore size of the connections, with 1 assigned to the largest bore. It is important to note the bore size if redefining the SKEYS for X1**, X2**, X3** or X4**.\n5\nFlanged connections on generic Y-type fittings are represented on the isometric on the tube only. This is due to the fact that the y-type fitting is user-definable and flanged representation on the component cannot be enforced. ELBO or BEND Symbol Keys\n\n\n\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nCross - Butt Weld\nCRBW\n2\nCross - Socket Weld\nCRSW\n2\nCross - Compression\nCRCP\n2\nCross - Flanged\nCRFL\n2\nCross - Screwed\nCRSC\n2\nCross - Set on\nCRSO\n1, 2\nCross - Set on\nReinforced\nCRRF\n1,2\nCross - Generic Y-\ntype with variable angle out- and off- legs\nX@**\n3,4,5\n1\nThe positions of P3 and P4 along the vertical axis are important for deriving correct cut pipe lengths. The vertical displacements of P3 and P4 are determined by the points at which the offline legs intersect the main line. P0, P1, P2, P3 and P4 will be coincident when the offline leg has the same bore as the main line.\n2\nThe dimensions of all Cross components depend upon plotted leg length. The default plotted leg length is 9mm, but the user can set this to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n3\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n4\nThe @ character in the symbol key is replaced automatically by an integer in the range 1 to 4, depending on the relative bore size of the connections, with 1 assigned to the largest bore. It is important to note the bore size if redefining the SKEYS for X1**, X2**, X3** or X4**.\n5\nFlanged connections on generic Y-type fittings are represented on the isometric on the tube only. This is due to the fact that the y-type fitting is user-definable and flanged representation on the component cannot be enforced. ELBO or BEND Symbol Keys\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nNote"}
{"Headers": "ELBO or BEND Symbol Keys", "Content": "Elbow - Butt Weld (90 and 45 degree)\nELBW\n\n\n1,9\nElbow - Butt Weld with a Connection (90 and 45 degree)\nETBW\n\n\n1,5,9\nElbow - Butt Weld 180 degree Return (U Elbow)\nEUBW\n\n\n2,9\nElbow Compression (90 and 45 degree)\nELCP\n\n\n1,9\nElbow Compression with a Connection (90 and 45 degree)\nETCP\n\n\n1,5,9\nElbow - Screwed with Male Ends (90 and 45 degree)\nEBSC\n\n\n1,9\nElbow - Screwed with Female Ends (90 and 45 degrees)\nELSC\n\n\n1,9\nElbow - Screwed - Female with a Connection (90 and 45 degree)\nETSC\n\n\n1,5,9\nElbow - Socket Weld\nELSW\n\n\n1,9\nElbow - Socket Weld with a Connection\nETSW\n\n\n1,5,9\nElbow - Reducing\nER**\n\n\n1,6\nBend - Flanged (all angles)\nBEFL\n\n\n1,9\nBend - Flanged with a Connection (all angles)\nBTFL\n\n\n1,5,9\nBend - Flanged 180 degree Return (U Bend)\nBUFL\n\n\n2,9\nBend - Mitre\nMIFL\n\n\n1,9\nFlanged Bend - Mitre with a Connection Flanged\nMTFL\n\n\n1,5,9\nBend - Mitre\nMIBW\n\n\n1,7,9\nBend - Mitre\nMIPL\n\n\n1,8,9\nButt Weld Bend - Mitre with a Connection\nMTBW\n\n\n1,5, 9\nButt Weld Bend - Mitre with a Connection\nMTPL\n\n\n1,5,9\nBend - Lobster Back Flanged\nL@FL\n\n\n1,3,9\nBend - Lobster Back with a Connection Flanged\nT@FL\n\n\n1,3,5,9\nBend - Lobster Back Butt Weld\nL@BW\n\n\n1,3,9\nLobster Back Bend\nL@PL\n\n\n1,3,8,9\nBend - Lobster Back with a Connection\nT@BW\n\n\n1,3,5,9\nBend - Lobster Back with a Connection\nT@PL\n\n\n1,3,5,9\nBend - Pulled (All Angles)\nPB+D\n\n\n1,4,9\nBend - Pulled 180 degree Return (U Bend)\nBU+D\n\n\n2,4,9\nBend - Pulled with a Connection (All Angles)\nTB+D\n\n\n1,4,5,9\nNote:\n1\nGeneric types ELBO and BEND have a connection reference to facilitate connections to the elbow or bend. ISODRAFT will always treat an elbow or bend as having an offline leg if it has a P3 with a bore greater than zero. Care is needed when selecting a symbol key and point set in order to achieve the required results.\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram and P3 should not have its bore set.\n3\nReplace the @ character in the symbol key with an integer (1 to 9) denoting the number of segments.\n4\nReplace the + character in the symbol key with an integer (1 to 9) denoting the ratio of the bend radius to the pipe bore.\n5\nThe p-point for the offline connection (P3) can be positioned anywhere along the horizontal (P1) axis that suits the specific component design.\n6\nReducing elbows can have any of the end types BW, CP, FL, SC, or SW, but not PL.\n7\nThis type of component is treated as a fitting in the material list.\n8\nThis type of component is treated as tube in the material list.\n9\nThe dimensions of all Elbow and Bend components depend upon plotted leg length. The default plotted leg length is 9mm, but this can be set to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n1\nGeneric types ELBO and BEND have a connection reference to facilitate connections to the elbow or bend. ISODRAFT will always treat an elbow or bend as having an offline leg if it has a P3 with a bore greater than zero. Care is needed when selecting a symbol key and point set in order to achieve the required results.\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram and P3 should not have its bore set.\n\n3\nReplace the @ character in the symbol key with an integer (1 to 9) denoting the number of segments.\n4\nReplace the + character in the symbol key with an integer (1 to 9) denoting the ratio of the bend radius to the pipe bore.\n5\nThe p-point for the offline connection (P3) can be positioned anywhere along the horizontal (P1) axis that suits the specific component design.\n6\nReducing elbows can have any of the end types BW, CP, FL, SC, or SW, but not PL.\n7\nThis type of component is treated as a fitting in the material list.\n8\nThis type of component is treated as tube in the material list.\n9\nThe dimensions of all Elbow and Bend components depend upon plotted leg length. The default plotted leg length is 9mm, but this can be set to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nElbow - Butt Weld (90 and 45 degree)\nELBW\n1,9\nElbow - Butt Weld with a Connection (90 and 45 degree)\nETBW\n1,5,9\nElbow - Butt Weld 180 degree Return (U Elbow)\nEUBW\n2,9\nElbow Compression (90 and 45 degree)\nELCP\n1,9\nElbow Compression with a Connection (90 and 45 degree)\nETCP\n1,5,9\nElbow - Screwed with Male Ends (90 and 45 degree)\nEBSC\n1,9\nElbow - Screwed with Female Ends (90 and 45 degrees)\nELSC\n1,9\nElbow - Screwed - Female with a Connection (90 and 45 degree)\nETSC\n1,5,9\nElbow - Socket Weld\nELSW\n1,9\nElbow - Socket Weld with a Connection\nETSW\n1,5,9\nElbow - Reducing\nER**\n1,6\nBend - Flanged (all angles)\nBEFL\n1,9\nBend - Flanged with a Connection (all angles)\nBTFL\n1,5,9\nBend - Flanged 180 degree Return (U Bend)\nBUFL\n2,9\nBend - Mitre\nMIFL\n1,9\nFlanged Bend - Mitre with a Connection Flanged\nMTFL\n1,5,9\nBend - Mitre\nMIBW\n1,7,9\nBend - Mitre\nMIPL\n1,8,9\nButt Weld Bend - Mitre with a Connection\nMTBW\n1,5, 9\nButt Weld Bend - Mitre with a Connection\nMTPL\n1,5,9\nBend - Lobster Back Flanged\nL@FL\n1,3,9\nBend - Lobster Back with a Connection Flanged\nT@FL\n1,3,5,9\nBend - Lobster Back Butt Weld\nL@BW\n1,3,9\nLobster Back Bend\nL@PL\n1,3,8,9\nBend - Lobster Back with a Connection\nT@BW\n1,3,5,9\nBend - Lobster Back with a Connection\nT@PL\n1,3,5,9\nBend - Pulled (All Angles)\nPB+D\n1,4,9\nBend - Pulled 180 degree Return (U Bend)\nBU+D\n2,4,9\nBend - Pulled with a Connection (All Angles)\nTB+D\n1,4,5,9\n1\nGeneric types ELBO and BEND have a connection reference to facilitate connections to the elbow or bend. ISODRAFT will always treat an elbow or bend as having an offline leg if it has a P3 with a bore greater than zero. Care is needed when selecting a symbol key and point set in order to achieve the required results.\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram and P3 should not have its bore set.\n3\nReplace the @ character in the symbol key with an integer (1 to 9) denoting the number of segments.\n4\nReplace the + character in the symbol key with an integer (1 to 9) denoting the ratio of the bend radius to the pipe bore.\n5\nThe p-point for the offline connection (P3) can be positioned anywhere along the horizontal (P1) axis that suits the specific component design.\n6\nReducing elbows can have any of the end types BW, CP, FL, SC, or SW, but not PL.\n7\nThis type of component is treated as a fitting in the material list.\n8\nThis type of component is treated as tube in the material list.\n9\nThe dimensions of all Elbow and Bend components depend upon plotted leg length. The default plotted leg length is 9mm, but this can be set to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n\n\n\nNote"}
{"Headers": "FBLI Symbol Keys", "Content": "Flange - Blind\nFLBL\n\n\n\nFlange - Reducing Concentric\nFLRC\n\n\n1\nFlange - Reducing Eccentric\nFLRE\n\n\n1,2\nNote:\n1\nReducing flanges will have clarifying text plotted on the isometric drawing to highlight their presence.\n2\nP3 is used only for orientation and will have its bore unset.\n1\nReducing flanges will have clarifying text plotted on the isometric drawing to highlight their presence.\n2\nP3 is used only for orientation and will have its bore unset.\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nFlange - Blind\nFLBL\nFlange - Reducing Concentric\nFLRC\n1\nFlange - Reducing Eccentric\nFLRE\n1,2\n1\nReducing flanges will have clarifying text plotted on the isometric drawing to highlight their presence.\n2\nP3 is used only for orientation and will have its bore unset.\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote"}
{"Headers": "FILT Symbol Keys", "Content": "Filter/Strainer -\nStraight Through\nFI**\n\n\n1\nFilter/Strainer - Angle\nFA**\n\n\n1,2\nFilter/Strainer - Offset\nFO**\n\n\n1,3,5\nFilter/Strainer -\nReturn\nFR**\n\n\n1,4\n'Y'-type Filter/ Strainer\nFY**\n\n\n1\nNotes:\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote:That the horizontal offset may be zero; i.e. P0, P1, P2 and P3 may be coplanar.\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: P3 is used only for orientation purposes and will have its bore unset. The horizontal offset may be zero; i.e. P0 and P1(and similarly P2 and P3) may be coincident\n5\nGeneric type FILT has a connection reference to facilitate connections to reducers. If the connection facility is not being used, then an eccentric reducer will have a p-arrive, a p-leave, and a P3 to orientate the flat side. In this case, the P3 should not have a bore. In this case, the P3 should not have a bore.\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote:That the horizontal offset may be zero; i.e. P0, P1, P2 and P3 may be coplanar.\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n5\nGeneric type FILT has a connection reference to facilitate connections to reducers. If the connection facility is not being used, then an eccentric reducer will have a p-arrive, a p-leave, and a P3 to orientate the flat side. In this case, the P3 should not have a bore. In this case, the P3 should not have a bore.\n\n\n\n\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nFilter/Strainer -\nStraight Through\nFI**\n1\nFilter/Strainer - Angle\nFA**\n1,2\nFilter/Strainer - Offset\nFO**\n1,3,5\nFilter/Strainer -\nReturn\nFR**\n1,4\n'Y'-type Filter/ Strainer\nFY**\n1\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote:That the horizontal offset may be zero; i.e. P0, P1, P2 and P3 may be coplanar.\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: P3 is used only for orientation purposes and will have its bore unset. The horizontal offset may be zero; i.e. P0 and P1(and similarly P2 and P3) may be coincident\n5\nGeneric type FILT has a connection reference to facilitate connections to reducers. If the connection facility is not being used, then an eccentric reducer will have a p-arrive, a p-leave, and a P3 to orientate the flat side. In this case, the P3 should not have a bore. In this case, the P3 should not have a bore.\nNote: P3 is used only for orientation purposes and will have its bore unset. The horizontal offset may be zero; i.e. P0 and P1(and similarly P2 and P3) may be coincident\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNotes\nNote:\nNote\n:"}
{"Headers": "FLAN Symbol Keys", "Content": "Component Description\nSKEY\nPlotted Symbol\nP-points\nNote\nFlange - Blind\nFLBL\nFlange -Flared/Loose Backing\nFLFL\n1\nFlange - Backing\nFLLB\n2\nFlange - Reducing Concentric\nFLRC\n3\nFlange - Reducing Eccentric\nFLRE\n3\nFlange - Screwed\nFLSC\nFlange - Slip On\nFLSO\nFlange - Slip On with \u2018J\u2019 Type Weld\nFLSJ\n1\nFlange - Orifice Slip On\nFOSO\n4\nFlange - Socket Weld\nFLSW\nFlange - Weld Neck\nFLWN\nFlange - Orifice Weld Neck\nFOWN\n4\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nFlange - Blind\nFLBL\n\n\n\nFlange -Flared/Loose Backing\nFLFL\n\n\n1\nFlange - Backing\nFLLB\n\n\n2\nFlange - Reducing Concentric\nFLRC\n\n\n3\nFlange - Reducing Eccentric\nFLRE\n\n\n3\nFlange - Screwed\nFLSC\n\n\n\nFlange - Slip On\nFLSO\n\n\n\nFlange - Slip On with \u2018J\u2019 Type Weld\nFLSJ\n\n\n1\nFlange - Orifice Slip On\nFOSO\n\n\n4\nFlange - Socket Weld\nFLSW\n\n\n\nFlange - Weld Neck\nFLWN\n\n\n\nFlange - Orifice Weld Neck\nFOWN\n\n\n4\nNotes:\n1\nTo allow for the amount of pipe that normally passes through the component before cutting or grinding off, a cutting allowance is included if the LOOSE attribute of the flange is set to TRUE. This allowance is determined by the value of the ALLO attribute, if set. If the ALLO attribute is not set (or set to zero), the allowance will default to 150mm. However, this default value can be altered by the LOOSEFLANGEALLOWANCE command.\n2\nThe system used by previous version of the software (using \u2018intuitive\u2019 P3 points) is still supported.\n3\nTo be used in conjunction with LJSE symbols FLRG or FLSE\n4\nReducing flanges will have clarifying text plotted on the isometric drawing to highlight their presence.\n5\nOrifice flanges will have clarifying text plotted on the isometric drawing to highlight their presence.\n1\nTo allow for the amount of pipe that normally passes through the component before cutting or grinding off, a cutting allowance is included if the LOOSE attribute of the flange is set to TRUE. This allowance is determined by the value of the ALLO attribute, if set. If the ALLO attribute is not set (or set to zero), the allowance will default to 150mm. However, this default value can be altered by the LOOSEFLANGEALLOWANCE command.\n2\nThe system used by previous version of the software (using \u2018intuitive\u2019 P3 points) is still supported.\n3\nTo be used in conjunction with LJSE symbols FLRG or FLSE\n4\nReducing flanges will have clarifying text plotted on the isometric drawing to highlight their presence.\n5\nOrifice flanges will have clarifying text plotted on the isometric drawing to highlight their presence.\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nFlange - Blind\nFLBL\nFlange -Flared/Loose Backing\nFLFL\n1\nFlange - Backing\nFLLB\n2\nFlange - Reducing Concentric\nFLRC\n3\nFlange - Reducing Eccentric\nFLRE\n3\nFlange - Screwed\nFLSC\nFlange - Slip On\nFLSO\nFlange - Slip On with \u2018J\u2019 Type Weld\nFLSJ\n1\nFlange - Orifice Slip On\nFOSO\n4\nFlange - Socket Weld\nFLSW\nFlange - Weld Neck\nFLWN\nFlange - Orifice Weld Neck\nFOWN\n4\n1\nTo allow for the amount of pipe that normally passes through the component before cutting or grinding off, a cutting allowance is included if the LOOSE attribute of the flange is set to TRUE. This allowance is determined by the value of the ALLO attribute, if set. If the ALLO attribute is not set (or set to zero), the allowance will default to 150mm. However, this default value can be altered by the LOOSEFLANGEALLOWANCE command.\n2\nThe system used by previous version of the software (using \u2018intuitive\u2019 P3 points) is still supported.\n3\nTo be used in conjunction with LJSE symbols FLRG or FLSE\n4\nReducing flanges will have clarifying text plotted on the isometric drawing to highlight their presence.\n5\nOrifice flanges will have clarifying text plotted on the isometric drawing to highlight their presence.\n\n\n\nNotes"}
{"Headers": "FTUB Symbol Keys", "Content": "Fixed Length Pipe - With flanged ends\nFPFL\n\n\n1\nFixed Length Pipe - Without flanged ends\nFPPL\n\n\n\n\nFixed Length Pipe - to be displayed and stretched, like implied tube on an isometric\nTUBE\n\n\n\nNote:\n1\nThe dimensions of all piping components depend upon plotted leg length. The default plotted leg length is 9mm, but this can be set to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n1\nThe dimensions of all piping components depend upon plotted leg length. The default plotted leg length is 9mm, but this can be set to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nFixed Length Pipe - With flanged ends\nFPFL\n1\nFixed Length Pipe - Without flanged ends\nFPPL\nFixed Length Pipe - to be displayed and stretched, like implied tube on an isometric\nTUBE\n\n1\nThe dimensions of all piping components depend upon plotted leg length. The default plotted leg length is 9mm, but this can be set to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote"}
{"Headers": "INST Symbol Keys", "Content": "Instrument\nII**\n\n\n1,5\nInstrument - Angle\nIA**\n\n\n1,2,5\nInstrument - Offset\nIO**\n\n\n1,3\nInstrument - Return\nIR**\n\n\n1,4\nInstrument - Dial\nIDPL\n\n\n6\nInstrument - Dial\nFlanged\nIDFL\n\n\n6\nOrifice Plate\nOP\n\n\n\nRestrictor Plate\nRP\n\n\n\nRupture Disk\nDR\n\n\n\nValve - Angle Relief/Vent\nRA**\n\n\n1,5\nValve - Angle Pressure Reducing\nXA**\n\n\n1,5\nValve Control\nCV**\n\n\n1,5\nValve - Angle Control\nCA**\n\n\n1,5\nValve - 3 Way Control\nC3**\n\n\n1,5\nValve - 4 Way Control\nC4**\n\n\n1,5\nValve - Control Square Indicator\nSV**\n\n\n1,5\nValve - Angle Control Square Indicator\nSA**\n\n\n1,3\nValve - 3 Way Control Square Indicator\nS3**\n\n\n1,5\nValve - 4 Way Control Square Indicator\nS4**\n\n\n1,5\nValve - Control Motorised Indicator\nMV**\n\n\n1,5\nValve - Angle Control Motorized Indicator\nMA**\n\n\n1,5\nValve - 3 Way Control Motorized Indicator\nM3**\n\n\n1,5\nValve - 4 Way Control Motorized Indicator\nM4**\n\n\n1,5\nValve - Control Hand Indicator\nHV**\n\n\n1,5\nValve - Angle Control Hand Indicator\nHA**\n\n\n1,5\nValve - 3Way Control Hand Indicator\nH3**\n\n\n1,5\nValve - 4Way Control Hand Indicator\nH4**\n\n\n1,5\nValve - Pressure Reducing\nXV**\n\n\n1,5\nValve - Relief/Vent\nRV**\n\n\n1,5\nLevel Gauge\nLG**\n\n\n1\nOne-Level Multiport\nValve\nJL**\n\n\n1,7\nOne-Level Multiport Valve\nJT**\n\n\n1,7\nTwo-Level Multiport Valve\nJB**\n\n\n1,7\nTwo-Level Multiport Valve\nJK**\n\n\n1,7\nTwo-Level Multiport Valve\nJC**\n\n\n1,7\nTwo-Level Multiport Valve\nJV**\n\n\n1,7\nTwo-Level Multiport Valve\nJA**\n\n\n1,7\nTwo-Level Multiport Valve\nJP**\n\n\n1,7\nTwo-Level Multiport Valve\nJE**\n\n\n1,7\nTwo-Level Multiport Valve\nJO**\n\n\n1,7\nThree-Level Multiport Valve\nJW**\n\n\n1,7\nThree-Level Multiport Valve\nJY**\n\n\n1,7\nThree-Level Multiport Valve\nJU**\n\n\n1,7\nThree-Level Multiport Valve\nJM**\n\n\n1,7\nThree-Level Multiport Valve\nJX**\n\n\n1,7\nThree-Level Multiport Valve\nJN**\n\n\n1,7\nThree-Level Multiport Valve\nJZ**\n\n\n1,7\nThree-Level Multiport Valve\nJG**\n\n\n1,7\nNotes:\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: The horizontal offset may be zero; i.e. P0, P1, P2 and P3 may be coplanar.\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: The horizontal offset may be zero; i.e. P0 and P1 (and similarly P2 and P3) may be coincident.\n5\nIf an orientation p-point (P3) is present in the point set and is oriented away from the XYZ axes, then the orientation of this p-point will be shown on the isometric.\n6\nInstrument dials can have a P3 with an unset bore for orienting the dial. This p-point will normally be positioned perpendicular to the dial face, on the dial axis. A message will be output near the component showing the orientation of P3.\n7\nP-Point 11 is the Spindle attachment point and its PURP attribute should be set to 'SPIN'. These Multiport Valves may have up to two flushing/draining connections:\nThese must be P-Point 9 and P-Point 10.\nThe isometric will only show a symbolic line and a note CONT TO \"name\" for each connection.\nThere will be no materials or isometric representation of the branch connection to these points.\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n\n5\nIf an orientation p-point (P3) is present in the point set and is oriented away from the XYZ axes, then the orientation of this p-point will be shown on the isometric.\n6\nInstrument dials can have a P3 with an unset bore for orienting the dial. This p-point will normally be positioned perpendicular to the dial face, on the dial axis. A message will be output near the component showing the orientation of P3.\n7\nP-Point 11 is the Spindle attachment point and its PURP attribute should be set to 'SPIN'. These Multiport Valves may have up to two flushing/draining connections:\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nInstrument\nII**\n1,5\nInstrument - Angle\nIA**\n1,2,5\nInstrument - Offset\nIO**\n1,3\nInstrument - Return\nIR**\n1,4\nInstrument - Dial\nIDPL\n6\nInstrument - Dial\nFlanged\nIDFL\n6\nOrifice Plate\nOP\nRestrictor Plate\nRP\nRupture Disk\nDR\nValve - Angle Relief/Vent\nRA**\n1,5\nValve - Angle Pressure Reducing\nXA**\n1,5\nValve Control\nCV**\n1,5\nValve - Angle Control\nCA**\n1,5\nValve - 3 Way Control\nC3**\n1,5\nValve - 4 Way Control\nC4**\n1,5\nValve - Control Square Indicator\nSV**\n1,5\nValve - Angle Control Square Indicator\nSA**\n1,3\nValve - 3 Way Control Square Indicator\nS3**\n1,5\nValve - 4 Way Control Square Indicator\nS4**\n1,5\nValve - Control Motorised Indicator\nMV**\n1,5\nValve - Angle Control Motorized Indicator\nMA**\n1,5\nValve - 3 Way Control Motorized Indicator\nM3**\n1,5\nValve - 4 Way Control Motorized Indicator\nM4**\n1,5\nValve - Control Hand Indicator\nHV**\n1,5\nValve - Angle Control Hand Indicator\nHA**\n1,5\nValve - 3Way Control Hand Indicator\nH3**\n1,5\nValve - 4Way Control Hand Indicator\nH4**\n1,5\nValve - Pressure Reducing\nXV**\n1,5\nValve - Relief/Vent\nRV**\n1,5\nLevel Gauge\nLG**\n1\nOne-Level Multiport\nValve\nJL**\n1,7\nOne-Level Multiport Valve\nJT**\n1,7\nTwo-Level Multiport Valve\nJB**\n1,7\nTwo-Level Multiport Valve\nJK**\n1,7\nTwo-Level Multiport Valve\nJC**\n1,7\nTwo-Level Multiport Valve\nJV**\n1,7\nTwo-Level Multiport Valve\nJA**\n1,7\nTwo-Level Multiport Valve\nJP**\n1,7\nTwo-Level Multiport Valve\nJE**\n1,7\nTwo-Level Multiport Valve\nJO**\n1,7\nThree-Level Multiport Valve\nJW**\n1,7\nThree-Level Multiport Valve\nJY**\n1,7\nThree-Level Multiport Valve\nJU**\n1,7\nThree-Level Multiport Valve\nJM**\n1,7\nThree-Level Multiport Valve\nJX**\n1,7\nThree-Level Multiport Valve\nJN**\n1,7\nThree-Level Multiport Valve\nJZ**\n1,7\nThree-Level Multiport Valve\nJG**\n1,7\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: The horizontal offset may be zero; i.e. P0, P1, P2 and P3 may be coplanar.\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: The horizontal offset may be zero; i.e. P0 and P1 (and similarly P2 and P3) may be coincident.\n5\nIf an orientation p-point (P3) is present in the point set and is oriented away from the XYZ axes, then the orientation of this p-point will be shown on the isometric.\n6\nInstrument dials can have a P3 with an unset bore for orienting the dial. This p-point will normally be positioned perpendicular to the dial face, on the dial axis. A message will be output near the component showing the orientation of P3.\n7\nP-Point 11 is the Spindle attachment point and its PURP attribute should be set to 'SPIN'. These Multiport Valves may have up to two flushing/draining connections:\nThese must be P-Point 9 and P-Point 10.\nThe isometric will only show a symbolic line and a note CONT TO \"name\" for each connection.\nThere will be no materials or isometric representation of the branch connection to these points.\nThese must be P-Point 9 and P-Point 10.\nThe isometric will only show a symbolic line and a note CONT TO \"name\" for each connection.\nThere will be no materials or isometric representation of the branch connection to these points.\nThese must be P-Point 9 and P-Point 10.\nThese must be P-Point 9 and P-Point 10.\nThe isometric will only show a symbolic line and a note CONT TO \"name\" for each connection.\nThe isometric will only show a symbolic line and a note CONT TO \"name\" for each connection.\nThere will be no materials or isometric representation of the branch connection to these points.\nThere will be no materials or isometric representation of the branch connection to these points.\nNote: The horizontal offset may be zero; i.e. P0, P1, P2 and P3 may be coplanar.\nNote: The horizontal offset may be zero; i.e. P0 and P1 (and similarly P2 and P3) may be coincident.\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNotes\nNote\nNote"}
{"Headers": "LJSE Symbol Keys", "Content": "Lap Joint Ring Loose\nFLRG\n\n\nLap Joint Stub End Loose\nFLSE\n\n\n1\nNote:\n1\nTo be used in conjunction with FLAN symbol FLLB.\n1\nTo be used in conjunction with FLAN symbol FLLB.\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nLap Joint Ring Loose\nFLRG\n1\nLap Joint Stub End Loose\nFLSE\n1\n1\nTo be used in conjunction with FLAN symbol FLLB.\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote"}
{"Headers": "PCOM Symbol Keys", "Content": "Block - Angle\nBA**\n\n\n1,2\nBlock - Offset\nBO**\n\n\n1,3\nBlock - Return\nBR**\n\n\n1,4\nExpansion Bellows\nEX**\n\n\n1\nFlame Trap\nFT**\n\n\n1\nBlock - Angle\nBA**\n\n\n1,2\nFlexible Hose\nFX**\n\n\n1\nHose Coupling\nCH**\n\n\n1\nNon-category Item\nNC**\n\n\n1\nPlug\nPL\n\n\n\nRestrictor Plate\nRP\n\n\n\nSight Glass\nSG**\n\n\n1,5\nSlip Plate\nSP\n\n\n5,6\nSlip Ring\nSR\n\n\n5,6\nSpectacle Blind\nSB\n\n\n5,6\nTundish (Funnel)\nTU**\n\n\n1\nNotes:\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: Tthe horizontal offset may be zero; for example, P0, P1, P2 and P3 may be coplanar.\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: The horizontal offset may be zero; for example, P0 and P1 (and similarly P2 and P3) may be coincident.\n5\nIf an orientation p-point is present in the point set, the orientation of this p-point will be shown on the isometric.\n6\nThe p-point set shown represents a typical arrangement for positioning and orienting the component, but is not mandatory.\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n\n\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n\n5\nIf an orientation p-point is present in the point set, the orientation of this p-point will be shown on the isometric.\n6\nThe p-point set shown represents a typical arrangement for positioning and orienting the component, but is not mandatory.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nBlock - Angle\nBA**\n1,2\nBlock - Offset\nBO**\n1,3\nBlock - Return\nBR**\n1,4\nExpansion Bellows\nEX**\n1\nFlame Trap\nFT**\n1\nBlock - Angle\nBA**\n1,2\nFlexible Hose\nFX**\n1\nHose Coupling\nCH**\n1\nNon-category Item\nNC**\n1\nPlug\nPL\nRestrictor Plate\nRP\nSight Glass\nSG**\n1,5\nSlip Plate\nSP\n5,6\nSlip Ring\nSR\n5,6\nSpectacle Blind\nSB\n5,6\nTundish (Funnel)\nTU**\n1\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: Tthe horizontal offset may be zero; for example, P0, P1, P2 and P3 may be coplanar.\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: The horizontal offset may be zero; for example, P0 and P1 (and similarly P2 and P3) may be coincident.\n5\nIf an orientation p-point is present in the point set, the orientation of this p-point will be shown on the isometric.\n6\nThe p-point set shown represents a typical arrangement for positioning and orienting the component, but is not mandatory.\nNote: Tthe horizontal offset may be zero; for example, P0, P1, P2 and P3 may be coplanar.\nNote: The horizontal offset may be zero; for example, P0 and P1 (and similarly P2 and P3) may be coincident.\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNotes\nNote\n:\nNote"}
{"Headers": "REDU Symbol Keys", "Content": "The following list of concentric and eccentric reducers symbol keys and plotted symbol.\n\n\n"}
{"Headers": "Concentric Reducers", "Content": "Reducer - Concentric Butt Weld\nRCBW\n\n\n1\nReducer - Concentric Fabricated from Plate\nCPBW\n\n\n1\nReducer - Concentric Swaged from Pipe\nCSBW\n\n\n1\nReducer - Concentric with a Connection Butt Weld\nCTBW\n\n\n1\nReducer - Concentric with a Connection Fabricated from Plate\nCZBW\n\n\n1\nReducer - Concentric with a Connection Swaged from Pipe\nCXBW\n\n\n1\nReducer - Concentric Compression\nRCCP\n\n\n1\nReducer - Concentric Flanged\nRCFL\n\n\n1\nReducer - Concentric Fabricated from Plate Flanged\nCPFL\n\n\n1\nReducer - Concentric Swaged from Pipe Flanged\nCSFL\n\n\n1\nReducer - Concentric with a Connection Flanged\nCTFL\n\n\n1\nReducer - Concentric with a Connection Fabricated from Plate Flanged\nCZFL\n\n\n1\nReducer - Concentric with a Connection Swaged from Pipe Flanged\nCXFL\n\n\n1\nReducer - Concentric Nipple\nRNSC\n\n\n1\nReducer - Concentric Screwed\nRCSC\n\n\n1\nReducer - Concentric with a Screwed Connection\nCTSC\n\n\n1\nReducer - Concentric Socket Weld\nRCSW\n\n\n1\nReducer - Concentric with a Connection Socket Weld\nCTSW\n\n\n1\nReducer - Concentric Socket Weld Bush\nRBSW\n\n\n1\nSpecial Reducing Flange\nRF\n\n\n1\nNote:\n1\nA concentric reducer with a connection point will have an additional p-point, P3, with a valid bore. A concentric reducer without a connection will have only a p-arrive and p-leave, as shown.\n1\nA concentric reducer with a connection point will have an additional p-point, P3, with a valid bore. A concentric reducer without a connection will have only a p-arrive and p-leave, as shown.\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nReducer - Concentric Butt Weld\nRCBW\n1\nReducer - Concentric Fabricated from Plate\nCPBW\n1\nReducer - Concentric Swaged from Pipe\nCSBW\n1\nReducer - Concentric with a Connection Butt Weld\nCTBW\n1\nReducer - Concentric with a Connection Fabricated from Plate\nCZBW\n1\nReducer - Concentric with a Connection Swaged from Pipe\nCXBW\n1\nReducer - Concentric Compression\nRCCP\n1\nReducer - Concentric Flanged\nRCFL\n1\nReducer - Concentric Fabricated from Plate Flanged\nCPFL\n1\nReducer - Concentric Swaged from Pipe Flanged\nCSFL\n1\nReducer - Concentric with a Connection Flanged\nCTFL\n1\nReducer - Concentric with a Connection Fabricated from Plate Flanged\nCZFL\n1\nReducer - Concentric with a Connection Swaged from Pipe Flanged\nCXFL\n1\nReducer - Concentric Nipple\nRNSC\n1\nReducer - Concentric Screwed\nRCSC\n1\nReducer - Concentric with a Screwed Connection\nCTSC\n1\nReducer - Concentric Socket Weld\nRCSW\n1\nReducer - Concentric with a Connection Socket Weld\nCTSW\n1\nReducer - Concentric Socket Weld Bush\nRBSW\n1\nSpecial Reducing Flange\nRF\n1\n1\nA concentric reducer with a connection point will have an additional p-point, P3, with a valid bore. A concentric reducer without a connection will have only a p-arrive and p-leave, as shown.\n\n\n\nNote"}
{"Headers": "Eccentric Reducers", "Content": "Component Description\nSKEY\nPlotted Symbol\nP-points\nNote\nReducer - Eccentric Butt Weld\nREBW\n1,2\nReducer - Eccentric Fabricated from Plate\nEPBW\n1,2\nReducer - Eccentric Swaged from Pipe\nESBW\n1\nReducer - Eccentric with a Connection Butt Weld\nOTBW\n1,2\nReducer - Eccentric with a Connection Fabricated from Plate\nEZBW\n1,2\nReducer - Eccentric with a Connection Swaged from Pipe\nEXBW\n1,2\nReducer - Eccentric Screwed\nRESC\n1\nReducer - Eccentric with a Connection Screwed\nOTSC\n1,2\nReducer - Eccentric Flanged\nREFL\n1,2\nReducer - Eccentric Fabricated from Plate Flanged\nEPFL\n1,2\nReducer - Eccentric Swaged from Pipe Flanged\nESFL\n1,2\nReducer - Eccentric with a Connection Flanged\nOTFL\n1,2\nReducer - Eccentric with a Connection Fabricated from Plate Flanged\nEZFL\n1,2\nReducer - Eccentric with a Connection Swaged from Pipe Flanged\nEXFL\n1,2\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nReducer - Eccentric Butt Weld\nREBW\n\n\n1,2\nReducer - Eccentric Fabricated from Plate\nEPBW\n\n\n1,2\nReducer - Eccentric Swaged from Pipe\nESBW\n\n\n1\nReducer - Eccentric with a Connection Butt Weld\nOTBW\n\n\n1,2\nReducer - Eccentric with a Connection Fabricated from Plate\nEZBW\n\n\n1,2\nReducer - Eccentric with a Connection Swaged from Pipe\nEXBW\n\n\n1,2\nReducer - Eccentric Screwed\nRESC\n\n\n1\nReducer - Eccentric with a Connection Screwed\nOTSC\n\n\n1,2\nReducer - Eccentric Flanged\nREFL\n\n\n1,2\nReducer - Eccentric Fabricated from Plate Flanged\nEPFL\n\n\n1,2\nReducer - Eccentric Swaged from Pipe Flanged\nESFL\n\n\n1,2\nReducer - Eccentric with a Connection Flanged\nOTFL\n\n\n1,2\nReducer - Eccentric with a Connection Fabricated from Plate Flanged\nEZFL\n\n\n1,2\nReducer - Eccentric with a Connection Swaged from Pipe Flanged\nEXFL\n\n\n1,2\nNote:\n1\nGeneric type REDU has a connection reference to facilitate connections to reducers. If the connection facility is not being used, then an eccentric reducer will have a p-arrive, a p-leave, and a P3 to orientate the flat side. If the connection facility is to be used, P3 will be the connection p-point and as such must have valid bore and orientation data for the connection. As the flat side can be either in the same direction as the connection or directly opposite, a P9 p-point must be used to give the orientation of the flat side.\n2\nIf an orientation p-point is present in the point set, the orientation of this p-point will be shown on the isometric.\n1\nGeneric type REDU has a connection reference to facilitate connections to reducers. If the connection facility is not being used, then an eccentric reducer will have a p-arrive, a p-leave, and a P3 to orientate the flat side. If the connection facility is to be used, P3 will be the connection p-point and as such must have valid bore and orientation data for the connection. As the flat side can be either in the same direction as the connection or directly opposite, a P9 p-point must be used to give the orientation of the flat side.\n2\nIf an orientation p-point is present in the point set, the orientation of this p-point will be shown on the isometric.\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nReducer - Eccentric Butt Weld\nREBW\n1,2\nReducer - Eccentric Fabricated from Plate\nEPBW\n1,2\nReducer - Eccentric Swaged from Pipe\nESBW\n1\nReducer - Eccentric with a Connection Butt Weld\nOTBW\n1,2\nReducer - Eccentric with a Connection Fabricated from Plate\nEZBW\n1,2\nReducer - Eccentric with a Connection Swaged from Pipe\nEXBW\n1,2\nReducer - Eccentric Screwed\nRESC\n1\nReducer - Eccentric with a Connection Screwed\nOTSC\n1,2\nReducer - Eccentric Flanged\nREFL\n1,2\nReducer - Eccentric Fabricated from Plate Flanged\nEPFL\n1,2\nReducer - Eccentric Swaged from Pipe Flanged\nESFL\n1,2\nReducer - Eccentric with a Connection Flanged\nOTFL\n1,2\nReducer - Eccentric with a Connection Fabricated from Plate Flanged\nEZFL\n1,2\nReducer - Eccentric with a Connection Swaged from Pipe Flanged\nEXFL\n1,2\n1\nGeneric type REDU has a connection reference to facilitate connections to reducers. If the connection facility is not being used, then an eccentric reducer will have a p-arrive, a p-leave, and a P3 to orientate the flat side. If the connection facility is to be used, P3 will be the connection p-point and as such must have valid bore and orientation data for the connection. As the flat side can be either in the same direction as the connection or directly opposite, a P9 p-point must be used to give the orientation of the flat side.\n2\nIf an orientation p-point is present in the point set, the orientation of this p-point will be shown on the isometric.\n\n\n\nNote"}
{"Headers": "SHU Symbol Keys", "Content": "Non-Category Item\nNC**\n\n\n1,2\nNote:\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nSHU elements have a CRFA attribute allowing up to 10 connection points.\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nSHU elements have a CRFA attribute allowing up to 10 connection points.\n\n\n\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nNon-Category Item\nNC**\n1,2\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nSHU elements have a CRFA attribute allowing up to 10 connection points.\n\n\n\nNote"}
{"Headers": "TEE or OLET Symbol Keys", "Content": "Olet - Half Coupling e.g. Screwed (Picture shows screwed but can be any connection type)\nHC**\n\n\n7\nOlet - Half Coupling e.g. Socket Weld\nHC**\n\n\n7\nOlet - Latrolet e.g. Butt Weld\nLA**\n\n\n\nOlet - Latrolet\ne.g. Screwed\nLA**\n\n\n\nOlet - Latrolet\ne.g. Socket Weld\nLA**\n\n\n\nOlet - Nipolet\ne.g. Screwed\nNI**\n\n\n\nOlet - Nipolet e.g. Plain Ended\nNI**\n\n\n\nOlet - Sockolet\nSK**\n\n\n\nOlet - Sweepolect\nSW**\n\n\n\nOlet - Thredolet\nTH**\n\n\n\nOlet - Weldolet\nWT**\n\n\n\nOlet - Instrument\nFlanged\nITFL\n\n\n\nTee - Butt Weld\nTEBW\n\n\n2,3,7\nTee - Compression\nTECP\n\n\n2,3\nTee - Flanged\nTEFL\n\n\n2,3\nTee - Screwed\nTESC\n\n\n2,3\nReserved for pipe tappings\nTESI\n\n\n1,2,7\nTee - Set-on\nTESO\n\n\n1,2,7\nTee - Set-on\nReinforced\nTERF\n\n\n1,2,7\nTee - Pulled\nTPUL\n\n\n1,2,7\nTee - Socket Weld\nTESW\n\n\n2,3,7\nTee - Swept Branch Butt Weld\nTSBW\n\n\n2,7\nTee - Swept Branch Flanged\nTSFL\n\n\n2,7\nTee - Swept Branch Compression\nTSCP\n\n\n2,7\nTee - Swept Branch Socket Weld\nTSSW\n\n\n2,7\nTee - Generic Y-type with variable angle out- and off- legs\n\nY@**\n\n\n4,5,6,7\nNote:\n1\nThe position of P3 along the perpendicular axis is important for deriving the cut pipe length. The perpendicular displacement of P3 is determined by the point at which the offline leg intersects the main line. For TESO and TERF, the distance P0 to P3 must not exceed half the main bore; P0, P1, P2 and P3 will be coincident when the offline leg has the same bore as the main line. For TPUL, the distance P0 to P3 must exceed half the main bore. If the position of P3 does not follow these rules, any weld shown at the intersection may appear in the wrong place.\n2\nThe dimensions of piping components depend upon plotted leg length. The default plotted leg length is 9mm, but this can be set to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n3\nThe TEBW, TECP, TEFL, TESC and TESW SKEYs can be used for laterals.\n4\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n5\nThe @ character in the symbol key is replaced automatically by an integer in the range 1 to 3, depending on the relative bore size of the connections, with 1 assigned to the largest bore. It is important to note the bore size if redefining the SKEYS for Y1**, Y2** or Y3**.\n6\nFlanged connections on generic Y-type fittings are represented on the isometric on the tube only. This is due to the fact that the y-type fitting is user-definable and flanged representation on the component cannot be enforced.\n7\nThe presence of an offset P3 may be indicated. The P3 connection of the tee/olet must be connected directly to a tube. The default behaviour is that, if an offset P3 configuration is present, a new ATEXT characterising the offset is output upon the drawing. This new ATEXT is number 233 in the list of ATEXTs and its default value is \u2018BRANCH OFFSET BY\u2019 followed by the nonzero relative coordinates of the offset.\n1\nThe position of P3 along the perpendicular axis is important for deriving the cut pipe length. The perpendicular displacement of P3 is determined by the point at which the offline leg intersects the main line. For TESO and TERF, the distance P0 to P3 must not exceed half the main bore; P0, P1, P2 and P3 will be coincident when the offline leg has the same bore as the main line. For TPUL, the distance P0 to P3 must exceed half the main bore. If the position of P3 does not follow these rules, any weld shown at the intersection may appear in the wrong place.\n2\nThe dimensions of piping components depend upon plotted leg length. The default plotted leg length is 9mm, but this can be set to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n3\nThe TEBW, TECP, TEFL, TESC and TESW SKEYs can be used for laterals.\n4\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n5\nThe @ character in the symbol key is replaced automatically by an integer in the range 1 to 3, depending on the relative bore size of the connections, with 1 assigned to the largest bore. It is important to note the bore size if redefining the SKEYS for Y1**, Y2** or Y3**.\n6\nFlanged connections on generic Y-type fittings are represented on the isometric on the tube only. This is due to the fact that the y-type fitting is user-definable and flanged representation on the component cannot be enforced.\n7\nThe presence of an offset P3 may be indicated. The P3 connection of the tee/olet must be connected directly to a tube. The default behaviour is that, if an offset P3 configuration is present, a new ATEXT characterising the offset is output upon the drawing. This new ATEXT is number 233 in the list of ATEXTs and its default value is \u2018BRANCH OFFSET BY\u2019 followed by the nonzero relative coordinates of the offset.\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nOlet - Half Coupling e.g. Screwed (Picture shows screwed but can be any connection type)\nHC**\n7\nOlet - Half Coupling e.g. Socket Weld\nHC**\n7\nOlet - Latrolet e.g. Butt Weld\nLA**\nOlet - Latrolet\ne.g. Screwed\nLA**\nOlet - Latrolet\ne.g. Socket Weld\nLA**\nOlet - Nipolet\ne.g. Screwed\nNI**\nOlet - Nipolet e.g. Plain Ended\nNI**\nOlet - Sockolet\nSK**\nOlet - Sweepolect\nSW**\nOlet - Thredolet\nTH**\nOlet - Weldolet\nWT**\nOlet - Instrument\nFlanged\nITFL\nTee - Butt Weld\nTEBW\n2,3,7\nTee - Compression\nTECP\n2,3\nTee - Flanged\nTEFL\n2,3\nTee - Screwed\nTESC\n2,3\nReserved for pipe tappings\nTESI\n1,2,7\nTee - Set-on\nTESO\n1,2,7\nTee - Set-on\nReinforced\nTERF\n1,2,7\nTee - Pulled\nTPUL\n1,2,7\nTee - Socket Weld\nTESW\n2,3,7\nTee - Swept Branch Butt Weld\nTSBW\n2,7\nTee - Swept Branch Flanged\nTSFL\n2,7\nTee - Swept Branch Compression\nTSCP\n2,7\nTee - Swept Branch Socket Weld\nTSSW\n2,7\nTee - Generic Y-type with variable angle out- and off- legs\nY@**\n4,5,6,7\n1\nThe position of P3 along the perpendicular axis is important for deriving the cut pipe length. The perpendicular displacement of P3 is determined by the point at which the offline leg intersects the main line. For TESO and TERF, the distance P0 to P3 must not exceed half the main bore; P0, P1, P2 and P3 will be coincident when the offline leg has the same bore as the main line. For TPUL, the distance P0 to P3 must exceed half the main bore. If the position of P3 does not follow these rules, any weld shown at the intersection may appear in the wrong place.\n2\nThe dimensions of piping components depend upon plotted leg length. The default plotted leg length is 9mm, but this can be set to a different value using the LEGLENGTH command. The minimum value the user can set is 6mm.\n3\nThe TEBW, TECP, TEFL, TESC and TESW SKEYs can be used for laterals.\n4\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n5\nThe @ character in the symbol key is replaced automatically by an integer in the range 1 to 3, depending on the relative bore size of the connections, with 1 assigned to the largest bore. It is important to note the bore size if redefining the SKEYS for Y1**, Y2** or Y3**.\n6\nFlanged connections on generic Y-type fittings are represented on the isometric on the tube only. This is due to the fact that the y-type fitting is user-definable and flanged representation on the component cannot be enforced.\n7\nThe presence of an offset P3 may be indicated. The P3 connection of the tee/olet must be connected directly to a tube. The default behaviour is that, if an offset P3 configuration is present, a new ATEXT characterising the offset is output upon the drawing. This new ATEXT is number 233 in the list of ATEXTs and its default value is \u2018BRANCH OFFSET BY\u2019 followed by the nonzero relative coordinates of the offset.\n\n\n\nNote"}
{"Headers": "TRAP Symbol Keys", "Content": "Component Description\nSKEY\nPlotted Symbol\nP-points\nNote\nTrap - In Line (Straight Through)\nTI**\n2\nTrap - Angle\nTA**\n1,2\nTrap - Offset\nTO**\n1,3\nTrap - Return\nTR**\n1,4\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nTrap - In Line (Straight Through)\nTI**\n\n\n2\nTrap - Angle\nTA**\n\n\n1,2\nTrap - Offset\nTO**\n\n\n1,3\nTrap - Return\nTR**\n\n\n1,4\nNote:\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nP3 must not have a valid bore. It is used only to obtain correct orientation of the element.\nP3 can be orientated in PARAGON.\nNote: The horizontal offset may be zero; i.e. P0, P1, P2 and P3 may be coplanar.\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: The horizontal offset may be zero; i.e. P0 and P1 (and similarly P2 and P3) may be coincident.\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n\nP3 must not have a valid bore. It is used only to obtain correct orientation of the element.\nP3 can be orientated in PARAGON.\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nTrap - In Line (Straight Through)\nTI**\n2\nTrap - Angle\nTA**\n1,2\nTrap - Offset\nTO**\n1,3\nTrap - Return\nTR**\n1,4\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\n3\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nP3 must not have a valid bore. It is used only to obtain correct orientation of the element.\nP3 can be orientated in PARAGON.\nNote: The horizontal offset may be zero; i.e. P0, P1, P2 and P3 may be coplanar.\n4\nTo use this symbol, the p-points must be arranged as shown in the following diagram:\nNote: The horizontal offset may be zero; i.e. P0 and P1 (and similarly P2 and P3) may be coincident.\nNote: The horizontal offset may be zero; i.e. P0, P1, P2 and P3 may be coplanar.\nNote: The horizontal offset may be zero; i.e. P0 and P1 (and similarly P2 and P3) may be coincident.\n\n\n\nNote\nNote\nNote\n:"}
{"Headers": "UNIO Symbol Keys", "Content": "Union - Screwed\nUNSC\n\n\n\nUnion - Socket Weld\nUNSW\n\n\n\nUnion - Butt Weld\nUNBW\n\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nUnion - Screwed\nUNSC\nUnion - Socket Weld\nUNSW\nUnion - Butt Weld\nUNBW\n\n\n"}
{"Headers": "UNIVERSAL Symbol Key", "Content": "Universal key for generic type PCOM\nUNIV\n\n\n1,2\nNote:\n1\nRadius of circle is controlled by percentage scale factor attribute, SkeyScale, on SDTE element (100% = 10mm). Symbol also has a line from circumference to each connection point.\n2\nUNIV Skey implies no end connection information. To flag end connections, the PSkey on each p-point must be set to one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain (default if unset)\n1\nRadius of circle is controlled by percentage scale factor attribute, SkeyScale, on SDTE element (100% = 10mm). Symbol also has a line from circumference to each connection point.\n2\nUNIV Skey implies no end connection information. To flag end connections, the PSkey on each p-point must be set to one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain (default if unset)\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nUniversal key for generic type PCOM\nUNIV\n1,2\n1\nRadius of circle is controlled by percentage scale factor attribute, SkeyScale, on SDTE element (100% = 10mm). Symbol also has a line from circumference to each connection point.\n2\nUNIV Skey implies no end connection information. To flag end connections, the PSkey on each p-point must be set to one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain (default if unset)\n\n\n\nNote"}
{"Headers": "VALV Symbol Keys", "Content": "Valve - Angle\nAV**\n\n\n1,2\nValve - Angle Pressure Reducing\nAX**\n\n\n1,2\nValve - Angle Relief/Vent\nAR**\n\n\n1,2\nValve - Ball\nVB**\n\n\n1,2\nValve - Basic\nVV**\n\n\n1,2\nValve - Butterfly\nVY**\n\n\n1,2\nValve - Check\nVC**\n\n\n1,2\nValve - Check\nCK**\n\n\n1,2\nValve - Cock\nVK**\n\n\n1,2\nValve - Diaphragm\nVD**\n\n\n1,2\nValve - Gate\nVT**\n\n\n1,2\nValve - Globe\nVG**\n\n\n1,2\nValve - Needle\nVN**\n\n\n1,2\nValve - Plug\nVP**\n\n\n1,2\nValve - Pressure Reducing\nVX**\n\n\n1,2\nValve - Relief/Vent\nVR**\n\n\n1,2\nValve - Slide\nVS**\n\n\n1,2\nNote:\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nIf an orientation p-point is present in the point set, then ISODRAFT will output the orientation of this p-point unless it is oriented in a primary direction (X, Y, Z etc.)\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nIf an orientation p-point is present in the point set, then ISODRAFT will output the orientation of this p-point unless it is oriented in a primary direction (X, Y, Z etc.)\n\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nValve - Angle\nAV**\n1,2\nValve - Angle Pressure Reducing\nAX**\n1,2\nValve - Angle Relief/Vent\nAR**\n1,2\nValve - Ball\nVB**\n1,2\nValve - Basic\nVV**\n1,2\nValve - Butterfly\nVY**\n1,2\nValve - Check\nVC**\n1,2\nValve - Check\nCK**\n1,2\nValve - Cock\nVK**\n1,2\nValve - Diaphragm\nVD**\n1,2\nValve - Gate\nVT**\n1,2\nValve - Globe\nVG**\n1,2\nValve - Needle\nVN**\n1,2\nValve - Plug\nVP**\n1,2\nValve - Pressure Reducing\nVX**\n1,2\nValve - Relief/Vent\nVR**\n1,2\nValve - Slide\nVS**\n1,2\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nIf an orientation p-point is present in the point set, then ISODRAFT will output the orientation of this p-point unless it is oriented in a primary direction (X, Y, Z etc.)\n\n\n\nNote"}
{"Headers": "VENT Symbol Keys", "Content": "Rupture Disk\nRD\n\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nPoints\nNote\nRupture Disk\nRD\n\n\n"}
{"Headers": "VFWA Symbol Keys", "Content": "Valve - 4 Way\nV4**\n\n\n1,2\nNotes:\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nIf an orientation p-point (P5) is present in the point set, the orientation of that p-point will be shown on the isometric.\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nIf an orientation p-point (P5) is present in the point set, the orientation of that p-point will be shown on the isometric.\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nValve - 4 Way\nV4**\n1,2\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nIf an orientation p-point (P5) is present in the point set, the orientation of that p-point will be shown on the isometric.\n\n\n\nNotes"}
{"Headers": "VTWA Symbol Keys", "Content": "Component Description\nSKEY\nPlotted Symbol\nP-points\nNote\nValve - 3 Way\nV3**\n1,2\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nValve - 3 Way\nV3**\n\n\n1,2\nNotes:\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nIf an orientation p-point (P5) is present in the point set, the orientation of that p-point will be shown on the isometric.\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nIf an orientation p-point (P5) is present in the point set, the orientation of that p-point will be shown on the isometric.\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nValve - 3 Way\nV3**\n1,2\n1\nReplace the ** characters in the symbol key with one of the following end condition identifiers:\nBW for butt weld\nCP for compression\nSW for socket weld\nFL for flanged\nSC for screwed\nPL for plain\n2\nIf an orientation p-point (P5) is present in the point set, the orientation of that p-point will be shown on the isometric.\n\n\n\nNotes"}
{"Headers": "WELD Symbol Keys", "Content": "Weld - Site\nWS\n\n\n\nWeld - Field Fitted\nWF\n\n\n\nWeld - Shop\nWW\n\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nWeld - Site\nWS\nWeld - Field Fitted\nWF\nWeld - Shop\nWW\n\n\n"}
{"Headers": "Floor Penetration ATTA Symbol", "Content": "Component Description\nSKEY\nPlotted Symbol\nNote\nPipe passing through floor\nFLOR\n1,2,3\nComponent Description\nSKEY\nPlotted Symbol\n\nNote\nPipe passing through floor\nFLOR\n\n\n1,2,3\nNotes:\n1\nSame rules apply as those used for positioning the FLOW ARROW symbol (refer to In-line Components, Including Straight-through Valves in the ISODRAFT User Guide).\n2\nMust only be positioned in vertical sections of pipeline.\n3\nISODRAFT will automatically orientate the fitting shape to suit the up/down direction of the pipeline.\n1\nSame rules apply as those used for positioning the FLOW ARROW symbol (refer to In-line Components, Including Straight-through Valves in the ISODRAFT User Guide).\n2\nMust only be positioned in vertical sections of pipeline.\n3\nISODRAFT will automatically orientate the fitting shape to suit the up/down direction of the pipeline.\n\nComponent Description\nSKEY\nPlotted Symbol\nNote\nPipe passing through floor\nFLOR\n1,2,3\n1\nSame rules apply as those used for positioning the FLOW ARROW symbol (refer to In-line Components, Including Straight-through Valves in the ISODRAFT User Guide).\n2\nMust only be positioned in vertical sections of pipeline.\n3\nISODRAFT will automatically orientate the fitting shape to suit the up/down direction of the pipeline.\n\n\n\nNotes"}
{"Headers": "Welded Lug Symbol Keys", "Content": "Welded Circular Lug\nWLC\n\n\n\nWelded Rectangular Lug\nWLR\n\n\n\n\nComponent Description\nSKEY\nPlotted Symbol\nP-points\nNote\nWelded Circular Lug\nWLC\nWelded Rectangular Lug\nWLR\n\n\n"}
{"Headers": "Symbol Key Reference Index", "Content": "This section lists all available symbol keys (SKEYs) in alphabetic order. Cross-references are given to the generic component types (GTYPEs) under which the user will find them described in the preceding sections of this appendix (if appropriate).\nEach SKEY has an indication of whether or not it may be redefined, as explained in the ISODRAFT User Guide, Section 11.1, The Basic Principles. For components which include spindles, the standard spindle type associated with the predefined SKEY is indicated, refer to ISODRAFT User Guide Section 11.3, Special Keys, for illustrations of these spindle types.\nSKEY\nGTYPE\nCOMPONENT\nUSER DEFINABLE?\nSPINDLE TYPE\nAR**\nVALV\nAngled Pressure Reducing Valve\nYes\n09SP\nAV**\nVALV\nAngled Valve\nYes\n01SP\nAX**\nVALV\nAngled Relief Valve or Vent\nYes\n02SP\nBA**\nPCOM\nAngle Block\nYes\nBEFL\nBEND\nFlanged Bend\nNo\nBO**\nPCOM\nOffset Block\nYes\nBR**\nPCOM\nReturn Block\nYes\nBTFL\nBEND\nFlanged Bend with Tee\nNo\nBU+D\nBEND\nPulled Return Bend\nNo\nBUFL\nBEND\nFlanged Return Bend\nNo\nC3**\nINST\n3-Way Control Valve\nNo\n13SP\nC4**\nINST\n4-Way Control Valve\nNo\n13SP\nCA**\nINST\nAngled Control Valve\nYes\n13SP\nCEBW\nCOUP\nButt Weld Elbolet\nYes\nCESC\nCOUP\nScrewed Fitting Elbolet\nYes\nCESW\nCOUP\nSocket Weld Elbolet\nYes\nCFSC\nCOUP\nHalf Coupling - Screwed\nYes\nCFSW\nCOUP\nHalf Coupling - Socket Screwed\nYes\nCH**\nPCOM\nHose Coupling\nYes\nCK**\nVALV\nCheck Valve\nYes\nCOCP\nCOUP\nCompression Fitting Coupling\nYes\nCOSC\nCOUP\nScrewed Fitting Coupling\nYes\nCOSW\nCOUP\nSocket Weld Coupling\nYes\nCPBW\nREDU\nButt Weld Concentric Reducer\nYes\nCPCF\nCOUP\nCentre Flange\nYes\nCPFL\nREDU\nFlanged Concentric Reducer\nYes\nCPWP\nCOUP\nWatertight Bulkhead and Deck\nYes\nCPWT\nCOUP\nWelded Sleeve thru Pipe\nYes\nCPWW\nCOUP\nWelded Sleeve thru Pipe\nYes\nCRBW\nCROS\nButt Weld Cross\nNo\nCRCP\nCROS\nCompression Fitting Cross\nNo\nCRFL\nCROS\nFlanged Cross\nNo\nCRRF\nCROS\nSet On Reinforced Cross\nNo\nCRSC\nCROS\nScrewed Fitting Cross\nNo\nCRSO\nCROS\nSet On Cross\nNo\nCRSW\nCROS\nSocket Weld Cross\nNo\nCSBW\nREDU\nButt Weld Concentric Reducer\nYes\nCSFL\nREDU\nFlanged Concentric Reducer\nYes\nCTBW\nREDU\nButt Weld Concentric Reducer with Tee\nYes\nCTFL\nREDU\nFlanged Concentric Reducer with Tee\nYes\nCTSC\nREDU\nScrewed Fitting Concentric with Tee\nYes\nCTSW\nREDU\nSocket Weld Concentric Reducer with Tee\nYes\nCV**\nINST\nControl Valve\nYes\n13SP\nCXBW\nREDU\nButt Weld Concentric Reducer with Tee\nYes\nCXFL\nREDU\nFlanged Concentric Reducer with Tee\nYes\nCZBW\nREDU\nButt Weld Concentric Reducer with Tee\nYes\nCZFL\nREDU\nFlanged Concentric Reducer with Tee\nYes\nDR\nINST\nRupture Disc\nYes\nEBSC\nELBO\nScrewed Fitting (Male) Elbow\nNo\nELBW\nELBO\nButt Weld Elbow\nNo\nELCP\nELBO\nCompression Fitting Elbow\nNo\nELSC\nELBO\nScrewed Fitting Elbow\nNo\nELSW\nELBO\nSocket Weld Elbow\nNo\nEPBW\nREDU\nButt Weld Eccentric Reducer\nYes\nEPFL\nREDU\nFlanged Eccentric Reducer\nYes\nER**\nELBO\nReducing Elbow\nNo\nESBW\nREDU\nButt Weld Eccentric Reducer\nYes\nESFL\nREDU\nFlanged Eccentric Reducer\nYes\nETBW\nELBO\nButt Weld Elbow with Tee\nNo\nETCP\nELBO\nCompression Fitting Elbow with Tee\nNo\nETSC\nELBO\nScrewed Fitting Elbow with Tee\nNo\nETSW\nELBO\nSocket Weld Elbow with Tee\nNo\nEUBW\nELBO\nButt Weld Return Elbow\nNo\nEX**\nPCOM\nExpansion Bellows\nYes\nEXBW\nREDU\nButt Weld Eccentric Reducer with Tee\nYes\nEXFL\nREDU\nFlanged Eccentric Reducer with Tee\nYes\nEZBW\nREDU\nButt Weld Eccentric Reducer with Tee\nYes\nEZFL\nREDU\nFlanged Eccentric Reducer with Tee\nYes\nFA**\nFILT\nAngled Filter\nYes\nFI**\nFILT\nStraight-Through (In-Line) Filter\nYes\nFLBL\nFLAN\nBlind or Blanking Flange\nYes\nFLBL\nFBLI\nBlind or Blanking Flange\nYes\nFLFL\nFLAN\nFlared Flange\nYes\nFLLB\nFLAN\nLoose Backing Flange\nYes\nFLOR\nATTA\nFloor Penetration Type ATTA\nYes\nFLOW\nFlow Arrow\nYes\nFLRC\nFLAN\nReducing Flange\nYes\nFLRC\nFBLI\nReducing Flange\nYes\nFLRE\nFLAN\nEccentric Reducing Flange\nYes\nFLRE\nFBLI\nEccentric Reducing Flange\nYes\nFLRG\nLJSE\nLap Joint Ring\nNo\nFLSC\nFLAN\nScrewed Fitting Flange\nYes\nFLSE\nLJSE\nLap Joint Stub End\nNo\nFLSJ\nFLAN\nSlip-on J-Type Welded Flange\nYes\nFLSO\nFLAN\nSlip-on Flange\nYes\nFLSW\nFLAN\nSocket Weld Flange\nYes\nFLWN\nFLAN\nWeld Neck Flange\nYes\nFO**\nFILT\nOffset Filter\nYes\nFOSO\nFLAN\nSlip-on Flange with Orifice\nYes\nFOWN\nFLAN\nWeld Neck Flange with Orifice\nYes\nFPFL\nFTUB\nFixed Length Pipe with Flanged Ends\nNo\nFPPL\nFTUB\nFixed Length Pipe with Plain Ends\nYes\nFR**\nFILT\nReturn Filter\nNo\nFT**\nPCOM\nFlame Trap\nYes\nFX**\nPCOM\nFlexible Hose\nYes\nFY**\nFILT\n\u2018Y\u2019-type Filter/Strainer\nYes\nH3**\nINST\n3-Way Control Valve\nNo\n12SP\nH4**\nINST\n4-Way Control Valve\nNo\n12SP\nHA**\nINST\nAngled Control Valve\nYes\n12SP\nHC**\nOLET\nScrewed Half Coupling\nYes\nHC**\nOLET\nSocket Weld Half Coupling\nYes\nHV**\nINST\nControl Valve\nYes\n12SP\nIA**\nINST\nAngled Instrument\nYes\nIDFL\nINST\nFlanged Instrument with Dial\nNo\nIDPL\nINST\nInstrument with Dial\nNo\nII**\nINST\nInstrument\nYes\nIO**\nINST\nOffset Instrument\nYes\nIR**\nINST\nReturn Instrument\nNo\nITFL\nOLET\nFlanged Instrument Tee\nNo\nJA**\nINST\nTwo-Level Multiport Valve\nNo\nJB**\nINST\nTwo-Level Multiport Valve\nNo\nJC**\nINST\nTwo-Level Multiport Valve\nNo\nJE**\nINST\nTwo-Level Multiport Valve\nNo\nJG**\nINST\nThree-Level Multiport Valve\nNo\nJK**\nINST\nTwo-Level Multiport Valve\nNo\nJL**\nINST\nOne-Level Multiport Valve\nNo\nJM**\nINST\nThree-Level Multiport Valve\nNo\nJN**\nINST\nThree-Level Multiport Valve\nNo\nJO**\nINST\nTwo-Level Multiport Valve\nNo\nJP**\nINST\nTwo-Level Multiport Valve\nNo\nJT**\nINST\nOne-Level Multiport Valve\nNo\nJU**\nINST\nThree-Level Multiport Valve\nNo\nJV**\nINST\nTwo-Level Multiport Valve\nNo\nJW**\nINST\nThree-Level Multiport Valve\nNo\nJX**\nINST\nThree-Level Multiport Valve\nNo\nJY**\nINST\nThree-Level Multiport Valve\nNo\nJZ**\nINST\nThree-Level Multiport Valve\nNo\nKABW\nCAP\nButt Weld Cap\nYes\nKACP\nCAP\nCompression Fitting Cap\nYes\nKASC\nCAP\nScrewed Fitting Cap\nYes\nKASW\nCAP\nSocket Weld Cap\nYes\nL@BW\nBEND\nButt Weld Lobster Back Bend\nNo\nL@FL\nBEND\nFlanged Lobster Back Bend\nNo\nLA**\nOLET\nButt Weld Latrolet\nYes\nLA**\nOLET\nScrewed Fitting Latrolet\nYes\nLA**\nOLET\nSocket Weld Latrolet\nYes\nLG**\nINST\nLevel Gauge\nNo\nM3**\nINST\n3-Way Motorised Valve\nNo\n11SP\nM4**\nINST\n4-Way Motorised Valve\nNo\nMA**\nINST\nAngled Control Valve\nYes\n11SP\nMIBW\nBEND\nButt Weld Mitred Bend\nNo\nMIFL\nBEND\nFlanged Mitred Bend\nNo\nMTBW\nBEND\nButt Weld Mitred Bend with Tee\nNo\nMTFL\nBEND\nFlanged Mitred Bend with Tee\nNo\nMV**\nINST\nMotorised Valve\nYes\n11SP\nNBSC\nCOUP\nScrewed Nipple\nYes\nNC**\nPCOM\nNon-Category Item\nYes\nNC**\nSHU\nNon-Category Item\nYes\nNI**\nOLET\nPlain End Nipolet\nYes\nNI**\nOLET\nScrewed Fitting Nipolet\nYes\nNRSC\nCOUP\nScrewed Fitting Nipple\nYes\nOP\nINST\nOrifice Plate\nYes\nOTBW\nREDU\nButt Weld Eccentric Reducer with Tee\nYes\nOTFL\nREDU\nFlanged Eccentric Reducer with Tee\nYes\nOTSC\nREDU\nScrewed Fitting Eccentric Reducer with Tee\nYes\nPB+D\nBEND\nPulled Bend\nNo\nPF\nCLOS\nFixed Length Pipe Block\nYes\nPL\nPCOM\nPlug\nYes\nPR\nINST\nRestrictor Plate\nYes\nPV\nCLOS\nVariable Length Pipe Block\nYes\nRA**\nINST\nAngled Relief Valve\nYes\n02SP\nRBSC\nREDU\nScrewed Fitting Concentric Reducing Bush\nYes\nRBSW\nREDU\nSocket Weld Concentric Reducing Bush\nYes\nRCBW\nREDU\nButt Weld Concentric Reducer\nYes\nRCCP\nREDU\nCompression Fitting Concentric Reducer\nYes\nRCFL\nREDU\nFlanged Concentric Reducer\nYes\nRCSC\nREDU\nScrewed Fitting Concentric Reducer\nYes\nRCSW\nREDU\nSocket Weld Concentric Reducer\nYes\nRD\nVENT\nRupture Disc\nYes\nREBW\nREDU\nButt Weld Eccentric Reducer\nYes\nREFL\nREDU\nFlanged Eccentric Reducer\nYes\nRESC\nREDU\nScrewed Fitting Eccentric Reducer\nYes\nRF\nREDU\nSpecial Reducing Flange\nYes\nRNSC\nREDU\nNipple Fitting Concentric Reducer\nYes\nRP\nPCOM\nRestrictor Plate\nYes\nRV**\nINST\nRelief Valve\nYes\nS3**\nINST\n3-Way Control Valve with Square Indicator\nNo\n10SP\nS4**\nINST\n4-Way Control Valve with Square Indicator\nNo\n10SP\nSA**\nINST\nAngled Control Valve with Square Indicator\nYes\n10SP\nSB\nPCOM\nSpectacle Blind\nYes\nSG**\nPCOM\nSight Glass\nYes\nSK**\nOLET\nSocket Weld Sockolet\nYes\nSP\nPCOM\nSlip Plate\nYes\nSR\nPCOM\nSlip Ring\nYes\nSV**\nINST\nControl Valve with Square Indicator\nYes\n10SP\nSW**\nOLET\nButt Weld Sweepolet\nYes\nT@BW\nBEND\nButt Weld Lobster Back Bend with Tee\nNo\nT@FL\nBEND\nFlanged Lobster Back Bend with Tee\nNo\nTA**\nTRAP\nAngled Trap\nYes\nTB+D\nBEND\nPulled Bend with Tee\nNo\nTEBW\nTEE\nButt Weld Tee\nNo\nTECP\nTEE\nCompression Fitting Tee\nNo\nTEFL\nTEE\nFlanged Tee\nNo\nTERF\nTEE\nReinforced Tee\nNo\nTESC\nTEE\nScrewed Fitting Tee\nNo\nTESI\nTEE\nReserved for pipe tappings\nNo\nTESO\nTEE\nSet On Tee\nNo\nTESW\nTEE\nSocket Weld Tee\nNo\nTH**\nOLET\nScrewed Fitting Thredolet\nYes\nTI**\nTRAP\nIn-line Trap\nYes\nTO**\nTRAP\nOffset Trap\nYes\nTPUL\nTEE\nPulled Tee\nNo\nTR**\nTRAP\nReturn Trap\nNo\nTSBW\nTEE\nButt Weld Swept Tee\nNo\nTSCP\nTEE\nCompression Fitting Swept Tee\nNo\nTSFL\nTEE\nFlanged Swept Tee\nNo\nTSSW\nTEE\nSocket Weld Swept Tee\nNo\nTU**\nPCOM\nTundish or Funnel\nYes\nUNBW\nUNIO\nUnion - Butt Weld\nYes\nUNIV\nPCOM\nUniversal Skey for special fittings\nYes Refer to\nISODRAFT User Guide\nUNSC\nUNIO\nScrewed Fitting Union\nYes\nUNSW\nUNIO\nButt or Socket Weld Union\nYes\nV3**\nVTWA\n3-Way Valve\nNo\n01SP\nV4**\nVFWA\n4-Way Valve\nNo\n01SP\nVB**\nVALV\nBall Valve\nYes\n03SP\nVC**\nVALV\nCheck Valve\nYes\nVD**\nVALV\nDiaphragm Valve\nYes\n01SP\nVG**\nVALV\nGlobe Valve\nYes\n01SP\nVK**\nVALV\nCock Valve\nYes\n03SP\nVN**\nVALV\nNeedle Valve\nYes\n06SP\nVP**\nVALV\nPlug Valve\nYes\n07SP\nVR**\nVALV\nRelief Valve\nYes\n02SP\nVS**\nVALV\nSlide Valve\nYes\n08SP\nVT**\nVALV\nGate Valve\nYes\n05SP\nVV**\nVALV\nBasic Valve\nYes\n01SP\nVX**\nVALV\nPressure Reducing Valve\nYes\n09SP\nVY**\nVALV\nButterfly Valve\nYes\n03SP\nWF\nWELD\nField Fitted Weld\nNo\nWLC\nOLET\nWelded Circular Lug\nYes\nWLR\nOLET\nWelded Rectangular Lug\nYes\nWS\nWELD\nSite Weld\nNo\nWTBW\nOLET\nButt Weld Weldolet\nYes\nWW\nWELD\nShop Weld\nNo\nX@**\nCROS\nGeneric Y-type Cross with user-definable out- and off- legs\nYes\nXA**\nINST\nAngled Pressure Reducing Valve\nYes\n09SP\nXV**\nINST\nPressure Reducing Valve\nYes\n09SP\nY@**\nTEE\nGeneric Y-type Tee with user-definable out- and off- legs\nYes\n01HG\nHanger (As a basis for user-defined hangers; refer to ISODRAFT User Guide, Section 10.4, Defining a New Hanger)\nYes\nSKEY\nGTYPE\nCOMPONENT\nUSER DEFINABLE?\nSPINDLE TYPE\nAR**\nVALV\nAngled Pressure Reducing Valve\nYes\n09SP\nAV**\nVALV\nAngled Valve\nYes\n01SP\nAX**\nVALV\nAngled Relief Valve or Vent\nYes\n02SP\nBA**\nPCOM\nAngle Block\nYes\n\nBEFL\nBEND\nFlanged Bend\nNo\n\nBO**\nPCOM\nOffset Block\nYes\n\nBR**\nPCOM\nReturn Block\nYes\n\nBTFL\nBEND\nFlanged Bend with Tee\nNo\n\nBU+D\nBEND\nPulled Return Bend\nNo\n\nBUFL\nBEND\nFlanged Return Bend\nNo\n\nC3**\nINST\n3-Way Control Valve\nNo\n13SP\nC4**\nINST\n4-Way Control Valve\nNo\n13SP\nCA**\nINST\nAngled Control Valve\nYes\n13SP\nCEBW\nCOUP\nButt Weld Elbolet\nYes\n\nCESC\nCOUP\nScrewed Fitting Elbolet\nYes\n\nCESW\nCOUP\nSocket Weld Elbolet\nYes\n\nCFSC\nCOUP\nHalf Coupling - Screwed\nYes\n\nCFSW\nCOUP\nHalf Coupling - Socket Screwed\nYes\n\nCH**\nPCOM\nHose Coupling\nYes\n\nCK**\nVALV\nCheck Valve\nYes\n\nCOCP\nCOUP\nCompression Fitting Coupling\nYes\n\nCOSC\nCOUP\nScrewed Fitting Coupling\nYes\n\nCOSW\nCOUP\nSocket Weld Coupling\nYes\n\nCPBW\nREDU\nButt Weld Concentric Reducer\nYes\n\nCPCF\nCOUP\nCentre Flange\nYes\n\nCPFL\nREDU\nFlanged Concentric Reducer\nYes\n\nCPWP\nCOUP\nWatertight Bulkhead and Deck\nYes\n\nCPWT\nCOUP\nWelded Sleeve thru Pipe\nYes\n\nCPWW\nCOUP\nWelded Sleeve thru Pipe\nYes\n\nCRBW\nCROS\nButt Weld Cross\nNo\n\nCRCP\nCROS\nCompression Fitting Cross\nNo\n\nCRFL\nCROS\nFlanged Cross\nNo\n\nCRRF\nCROS\nSet On Reinforced Cross\nNo\n\nCRSC\nCROS\nScrewed Fitting Cross\nNo\n\nCRSO\nCROS\nSet On Cross\nNo\n\nCRSW\nCROS\nSocket Weld Cross\nNo\n\nCSBW\nREDU\nButt Weld Concentric Reducer\nYes\n\nCSFL\nREDU\nFlanged Concentric Reducer\nYes\n\nCTBW\nREDU\nButt Weld Concentric Reducer with Tee\nYes\n\nCTFL\nREDU\nFlanged Concentric Reducer with Tee\nYes\n\nCTSC\nREDU\nScrewed Fitting Concentric with Tee\nYes\n\nCTSW\nREDU\nSocket Weld Concentric Reducer with Tee\nYes\n\nCV**\nINST\nControl Valve\nYes\n13SP\nCXBW\nREDU\nButt Weld Concentric Reducer with Tee\nYes\n\nCXFL\nREDU\nFlanged Concentric Reducer with Tee\nYes\n\nCZBW\nREDU\nButt Weld Concentric Reducer with Tee\nYes\n\nCZFL\nREDU\nFlanged Concentric Reducer with Tee\nYes\n\nDR\nINST\nRupture Disc\nYes\n\nEBSC\nELBO\nScrewed Fitting (Male) Elbow\nNo\n\nELBW\nELBO\nButt Weld Elbow\nNo\n\nELCP\nELBO\nCompression Fitting Elbow\nNo\n\nELSC\nELBO\nScrewed Fitting Elbow\nNo\n\nELSW\nELBO\nSocket Weld Elbow\nNo\n\nEPBW\nREDU\nButt Weld Eccentric Reducer\nYes\n\nEPFL\nREDU\nFlanged Eccentric Reducer\nYes\n\nER**\nELBO\nReducing Elbow\nNo\n\nESBW\nREDU\nButt Weld Eccentric Reducer\nYes\n\nESFL\nREDU\nFlanged Eccentric Reducer\nYes\n\nETBW\nELBO\nButt Weld Elbow with Tee\nNo\n\nETCP\nELBO\nCompression Fitting Elbow with Tee\nNo\n\nETSC\nELBO\nScrewed Fitting Elbow with Tee\nNo\n\nETSW\nELBO\nSocket Weld Elbow with Tee\nNo\n\nEUBW\nELBO\nButt Weld Return Elbow\nNo\n\nEX**\nPCOM\nExpansion Bellows\nYes\n\nEXBW\nREDU\nButt Weld Eccentric Reducer with Tee\nYes\n\nEXFL\nREDU\nFlanged Eccentric Reducer with Tee\nYes\n\nEZBW\nREDU\nButt Weld Eccentric Reducer with Tee\nYes\n\nEZFL\nREDU\nFlanged Eccentric Reducer with Tee\nYes\n\nFA**\nFILT\nAngled Filter\nYes\n\nFI**\nFILT\nStraight-Through (In-Line) Filter\nYes\n\nFLBL\nFLAN\nBlind or Blanking Flange\nYes\n\nFLBL\nFBLI\nBlind or Blanking Flange\nYes\n\nFLFL\nFLAN\nFlared Flange\nYes\n\nFLLB\nFLAN\nLoose Backing Flange\nYes\n\nFLOR\nATTA\nFloor Penetration Type ATTA\nYes\n\nFLOW\n\nFlow Arrow\nYes\n\nFLRC\nFLAN\nReducing Flange\nYes\n\nFLRC\nFBLI\nReducing Flange\nYes\n\nFLRE\nFLAN\nEccentric Reducing Flange\nYes\n\nFLRE\nFBLI\nEccentric Reducing Flange\nYes\n\nFLRG\nLJSE\nLap Joint Ring\nNo\n\nFLSC\nFLAN\nScrewed Fitting Flange\nYes\n\nFLSE\nLJSE\nLap Joint Stub End\nNo\n\nFLSJ\nFLAN\nSlip-on J-Type Welded Flange\nYes\n\nFLSO\nFLAN\nSlip-on Flange\nYes\n\nFLSW\nFLAN\nSocket Weld Flange\nYes\n\nFLWN\nFLAN\nWeld Neck Flange\nYes\n\nFO**\nFILT\nOffset Filter\nYes\n\nFOSO\nFLAN\nSlip-on Flange with Orifice\nYes\n\nFOWN\nFLAN\nWeld Neck Flange with Orifice\nYes\n\nFPFL\nFTUB\nFixed Length Pipe with Flanged Ends\nNo\n\nFPPL\nFTUB\nFixed Length Pipe with Plain Ends\nYes\n\nFR**\nFILT\nReturn Filter\nNo\n\nFT**\nPCOM\nFlame Trap\nYes\n\nFX**\nPCOM\nFlexible Hose\nYes\n\nFY**\nFILT\n\u2018Y\u2019-type Filter/Strainer\nYes\n\nH3**\nINST\n3-Way Control Valve\nNo\n12SP\nH4**\nINST\n4-Way Control Valve\nNo\n12SP\nHA**\nINST\nAngled Control Valve\nYes\n12SP\nHC**\nOLET\nScrewed Half Coupling\nYes\n\nHC**\nOLET\nSocket Weld Half Coupling\nYes\n\nHV**\nINST\nControl Valve\nYes\n12SP\nIA**\nINST\nAngled Instrument\nYes\n\nIDFL\nINST\nFlanged Instrument with Dial\nNo\n\nIDPL\nINST\nInstrument with Dial\nNo\n\nII**\nINST\nInstrument\nYes\n\nIO**\nINST\nOffset Instrument\nYes\n\nIR**\nINST\nReturn Instrument\nNo\n\nITFL\nOLET\nFlanged Instrument Tee\nNo\n\nJA**\nINST\nTwo-Level Multiport Valve\nNo\n\nJB**\nINST\nTwo-Level Multiport Valve\nNo\n\nJC**\nINST\nTwo-Level Multiport Valve\nNo\n\nJE**\nINST\nTwo-Level Multiport Valve\nNo\n\nJG**\nINST\nThree-Level Multiport Valve\nNo\n\nJK**\nINST\nTwo-Level Multiport Valve\nNo\n\nJL**\nINST\nOne-Level Multiport Valve\nNo\n\nJM**\nINST\nThree-Level Multiport Valve\nNo\n\nJN**\nINST\nThree-Level Multiport Valve\nNo\n\nJO**\nINST\nTwo-Level Multiport Valve\nNo\n\nJP**\nINST\nTwo-Level Multiport Valve\nNo\n\nJT**\nINST\nOne-Level Multiport Valve\nNo\n\nJU**\nINST\nThree-Level Multiport Valve\nNo\n\nJV**\nINST\nTwo-Level Multiport Valve\nNo\n\nJW**\nINST\nThree-Level Multiport Valve\nNo\n\nJX**\nINST\nThree-Level Multiport Valve\nNo\n\nJY**\nINST\nThree-Level Multiport Valve\nNo\n\nJZ**\nINST\nThree-Level Multiport Valve\nNo\n\nKABW\nCAP\nButt Weld Cap\nYes\n\nKACP\nCAP\nCompression Fitting Cap\nYes\n\nKASC\nCAP\nScrewed Fitting Cap\nYes\n\nKASW\nCAP\nSocket Weld Cap\nYes\n\nL@BW\nBEND\nButt Weld Lobster Back Bend\nNo\n\nL@FL\nBEND\nFlanged Lobster Back Bend\nNo\n\nLA**\nOLET\nButt Weld Latrolet\nYes\n\nLA**\nOLET\nScrewed Fitting Latrolet\nYes\n\nLA**\nOLET\nSocket Weld Latrolet\nYes\n\nLG**\nINST\nLevel Gauge\nNo\n\nM3**\nINST\n3-Way Motorised Valve\nNo\n11SP\nM4**\nINST\n4-Way Motorised Valve\nNo\n\nMA**\nINST\nAngled Control Valve\nYes\n11SP\nMIBW\nBEND\nButt Weld Mitred Bend\nNo\n\nMIFL\nBEND\nFlanged Mitred Bend\nNo\n\nMTBW\nBEND\nButt Weld Mitred Bend with Tee\nNo\n\nMTFL\nBEND\nFlanged Mitred Bend with Tee\nNo\n\nMV**\nINST\nMotorised Valve\nYes\n11SP\nNBSC\nCOUP\nScrewed Nipple\nYes\n\nNC**\nPCOM\nNon-Category Item\nYes\n\nNC**\nSHU\nNon-Category Item\nYes\n\nNI**\nOLET\nPlain End Nipolet\nYes\n\nNI**\nOLET\nScrewed Fitting Nipolet\nYes\n\nNRSC\nCOUP\nScrewed Fitting Nipple\nYes\n\nOP\nINST\nOrifice Plate\nYes\n\nOTBW\nREDU\nButt Weld Eccentric Reducer with Tee\nYes\n\nOTFL\nREDU\nFlanged Eccentric Reducer with Tee\nYes\n\nOTSC\nREDU\nScrewed Fitting Eccentric Reducer with Tee\nYes\n\nPB+D\nBEND\nPulled Bend\nNo\n\nPF\nCLOS\nFixed Length Pipe Block\nYes\n\nPL\nPCOM\nPlug\nYes\n\nPR\nINST\nRestrictor Plate\nYes\n\nPV\nCLOS\nVariable Length Pipe Block\nYes\n\nRA**\nINST\nAngled Relief Valve\nYes\n02SP\nRBSC\nREDU\nScrewed Fitting Concentric Reducing Bush\nYes\n\nRBSW\nREDU\nSocket Weld Concentric Reducing Bush\nYes\n\nRCBW\nREDU\nButt Weld Concentric Reducer\nYes\n\nRCCP\nREDU\nCompression Fitting Concentric Reducer\nYes\n\nRCFL\nREDU\nFlanged Concentric Reducer\nYes\n\nRCSC\nREDU\nScrewed Fitting Concentric Reducer\nYes\n\nRCSW\nREDU\nSocket Weld Concentric Reducer\nYes\n\nRD\nVENT\nRupture Disc\nYes\n\nREBW\nREDU\nButt Weld Eccentric Reducer\nYes\n\nREFL\nREDU\nFlanged Eccentric Reducer\nYes\n\nRESC\nREDU\nScrewed Fitting Eccentric Reducer\nYes\n\nRF\nREDU\nSpecial Reducing Flange\nYes\n\nRNSC\nREDU\nNipple Fitting Concentric Reducer\nYes\n\nRP\nPCOM\nRestrictor Plate\nYes\n\nRV**\nINST\nRelief Valve\nYes\n\nS3**\nINST\n3-Way Control Valve with Square Indicator\nNo\n10SP\nS4**\nINST\n4-Way Control Valve with Square Indicator\nNo\n10SP\nSA**\nINST\nAngled Control Valve with Square Indicator\nYes\n10SP\nSB\nPCOM\nSpectacle Blind\nYes\n\nSG**\nPCOM\nSight Glass\nYes\n\nSK**\nOLET\nSocket Weld Sockolet\nYes\n\nSP\nPCOM\nSlip Plate\nYes\n\nSR\nPCOM\nSlip Ring\nYes\n\nSV**\nINST\nControl Valve with Square Indicator\nYes\n10SP\nSW**\nOLET\nButt Weld Sweepolet\nYes\n\nT@BW\nBEND\nButt Weld Lobster Back Bend with Tee\nNo\n\nT@FL\nBEND\nFlanged Lobster Back Bend with Tee\nNo\n\nTA**\nTRAP\nAngled Trap\nYes\n\nTB+D\nBEND\nPulled Bend with Tee\nNo\n\nTEBW\nTEE\nButt Weld Tee\nNo\n\nTECP\nTEE\nCompression Fitting Tee\nNo\n\nTEFL\nTEE\nFlanged Tee\nNo\n\nTERF\nTEE\nReinforced Tee\nNo\n\nTESC\nTEE\nScrewed Fitting Tee\nNo\n\nTESI\nTEE\nReserved for pipe tappings\nNo\n\nTESO\nTEE\nSet On Tee\nNo\n\nTESW\nTEE\nSocket Weld Tee\nNo\n\nTH**\nOLET\nScrewed Fitting Thredolet\nYes\n\nTI**\nTRAP\nIn-line Trap\nYes\n\nTO**\nTRAP\nOffset Trap\nYes\n\nTPUL\nTEE\nPulled Tee\nNo\n\nTR**\nTRAP\nReturn Trap\nNo\n\nTSBW\nTEE\nButt Weld Swept Tee\nNo\n\nTSCP\nTEE\nCompression Fitting Swept Tee\nNo\n\nTSFL\nTEE\nFlanged Swept Tee\nNo\n\nTSSW\nTEE\nSocket Weld Swept Tee\nNo\n\nTU**\nPCOM\nTundish or Funnel\nYes\n\nUNBW\nUNIO\nUnion - Butt Weld\nYes\n\nUNIV\nPCOM\nUniversal Skey for special fittings\nYes Refer to\nISODRAFT User Guide\n\nUNSC\nUNIO\nScrewed Fitting Union\nYes\n\nUNSW\nUNIO\nButt or Socket Weld Union\nYes\n\nV3**\nVTWA\n3-Way Valve\nNo\n01SP\nV4**\nVFWA\n4-Way Valve\nNo\n01SP\nVB**\nVALV\nBall Valve\nYes\n03SP\nVC**\nVALV\nCheck Valve\nYes\n\nVD**\nVALV\nDiaphragm Valve\nYes\n01SP\nVG**\nVALV\nGlobe Valve\nYes\n01SP\nVK**\nVALV\nCock Valve\nYes\n03SP\nVN**\nVALV\nNeedle Valve\nYes\n06SP\nVP**\nVALV\nPlug Valve\nYes\n07SP\nVR**\nVALV\nRelief Valve\nYes\n02SP\nVS**\nVALV\nSlide Valve\nYes\n08SP\nVT**\nVALV\nGate Valve\nYes\n05SP\nVV**\nVALV\nBasic Valve\nYes\n01SP\nVX**\nVALV\nPressure Reducing Valve\nYes\n09SP\nVY**\nVALV\nButterfly Valve\nYes\n03SP\nWF\nWELD\nField Fitted Weld\nNo\n\nWLC\nOLET\nWelded Circular Lug\nYes\n\nWLR\nOLET\nWelded Rectangular Lug\nYes\n\nWS\nWELD\nSite Weld\nNo\n\nWTBW\nOLET\nButt Weld Weldolet\nYes\n\nWW\nWELD\nShop Weld\nNo\n\nX@**\nCROS\nGeneric Y-type Cross with user-definable out- and off- legs\nYes\n\nXA**\nINST\nAngled Pressure Reducing Valve\nYes\n09SP\nXV**\nINST\nPressure Reducing Valve\nYes\n09SP\nY@**\nTEE\nGeneric Y-type Tee with user-definable out- and off- legs\nYes\n\n01HG\n\nHanger (As a basis for user-defined hangers; refer to ISODRAFT User Guide, Section 10.4, Defining a New Hanger)\nYes\n\n@\nin Bends, denotes the number of bend segments (range 1\u20119)\nin X-type and Y-type Crosses/Tees, replaced by an integer in the range 1 to 4, 1\nindicating the largest bore, 4 indicating the smallest bore.\n+\ndenotes the ratio of the bend radius to the pipe bore (range 1\u20119)\n\nSKEY\nGTYPE\nCOMPONENT\nUSER DEFINABLE?\nSPINDLE TYPE\nAR**\nVALV\nAngled Pressure Reducing Valve\nYes\n09SP\nAV**\nVALV\nAngled Valve\nYes\n01SP\nAX**\nVALV\nAngled Relief Valve or Vent\nYes\n02SP\nBA**\nPCOM\nAngle Block\nYes\nBEFL\nBEND\nFlanged Bend\nNo\nBO**\nPCOM\nOffset Block\nYes\nBR**\nPCOM\nReturn Block\nYes\nBTFL\nBEND\nFlanged Bend with Tee\nNo\nBU+D\nBEND\nPulled Return Bend\nNo\nBUFL\nBEND\nFlanged Return Bend\nNo\nC3**\nINST\n3-Way Control Valve\nNo\n13SP\nC4**\nINST\n4-Way Control Valve\nNo\n13SP\nCA**\nINST\nAngled Control Valve\nYes\n13SP\nCEBW\nCOUP\nButt Weld Elbolet\nYes\nCESC\nCOUP\nScrewed Fitting Elbolet\nYes\nCESW\nCOUP\nSocket Weld Elbolet\nYes\nCFSC\nCOUP\nHalf Coupling - Screwed\nYes\nCFSW\nCOUP\nHalf Coupling - Socket Screwed\nYes\nCH**\nPCOM\nHose Coupling\nYes\nCK**\nVALV\nCheck Valve\nYes\nCOCP\nCOUP\nCompression Fitting Coupling\nYes\nCOSC\nCOUP\nScrewed Fitting Coupling\nYes\nCOSW\nCOUP\nSocket Weld Coupling\nYes\nCPBW\nREDU\nButt Weld Concentric Reducer\nYes\nCPCF\nCOUP\nCentre Flange\nYes\nCPFL\nREDU\nFlanged Concentric Reducer\nYes\nCPWP\nCOUP\nWatertight Bulkhead and Deck\nYes\nCPWT\nCOUP\nWelded Sleeve thru Pipe\nYes\nCPWW\nCOUP\nWelded Sleeve thru Pipe\nYes\nCRBW\nCROS\nButt Weld Cross\nNo\nCRCP\nCROS\nCompression Fitting Cross\nNo\nCRFL\nCROS\nFlanged Cross\nNo\nCRRF\nCROS\nSet On Reinforced Cross\nNo\nCRSC\nCROS\nScrewed Fitting Cross\nNo\nCRSO\nCROS\nSet On Cross\nNo\nCRSW\nCROS\nSocket Weld Cross\nNo\nCSBW\nREDU\nButt Weld Concentric Reducer\nYes\nCSFL\nREDU\nFlanged Concentric Reducer\nYes\nCTBW\nREDU\nButt Weld Concentric Reducer with Tee\nYes\nCTFL\nREDU\nFlanged Concentric Reducer with Tee\nYes\nCTSC\nREDU\nScrewed Fitting Concentric with Tee\nYes\nCTSW\nREDU\nSocket Weld Concentric Reducer with Tee\nYes\nCV**\nINST\nControl Valve\nYes\n13SP\nCXBW\nREDU\nButt Weld Concentric Reducer with Tee\nYes\nCXFL\nREDU\nFlanged Concentric Reducer with Tee\nYes\nCZBW\nREDU\nButt Weld Concentric Reducer with Tee\nYes\nCZFL\nREDU\nFlanged Concentric Reducer with Tee\nYes\nDR\nINST\nRupture Disc\nYes\nEBSC\nELBO\nScrewed Fitting (Male) Elbow\nNo\nELBW\nELBO\nButt Weld Elbow\nNo\nELCP\nELBO\nCompression Fitting Elbow\nNo\nELSC\nELBO\nScrewed Fitting Elbow\nNo\nELSW\nELBO\nSocket Weld Elbow\nNo\nEPBW\nREDU\nButt Weld Eccentric Reducer\nYes\nEPFL\nREDU\nFlanged Eccentric Reducer\nYes\nER**\nELBO\nReducing Elbow\nNo\nESBW\nREDU\nButt Weld Eccentric Reducer\nYes\nESFL\nREDU\nFlanged Eccentric Reducer\nYes\nETBW\nELBO\nButt Weld Elbow with Tee\nNo\nETCP\nELBO\nCompression Fitting Elbow with Tee\nNo\nETSC\nELBO\nScrewed Fitting Elbow with Tee\nNo\nETSW\nELBO\nSocket Weld Elbow with Tee\nNo\nEUBW\nELBO\nButt Weld Return Elbow\nNo\nEX**\nPCOM\nExpansion Bellows\nYes\nEXBW\nREDU\nButt Weld Eccentric Reducer with Tee\nYes\nEXFL\nREDU\nFlanged Eccentric Reducer with Tee\nYes\nEZBW\nREDU\nButt Weld Eccentric Reducer with Tee\nYes\nEZFL\nREDU\nFlanged Eccentric Reducer with Tee\nYes\nFA**\nFILT\nAngled Filter\nYes\nFI**\nFILT\nStraight-Through (In-Line) Filter\nYes\nFLBL\nFLAN\nBlind or Blanking Flange\nYes\nFLBL\nFBLI\nBlind or Blanking Flange\nYes\nFLFL\nFLAN\nFlared Flange\nYes\nFLLB\nFLAN\nLoose Backing Flange\nYes\nFLOR\nATTA\nFloor Penetration Type ATTA\nYes\nFLOW\nFlow Arrow\nYes\nFLRC\nFLAN\nReducing Flange\nYes\nFLRC\nFBLI\nReducing Flange\nYes\nFLRE\nFLAN\nEccentric Reducing Flange\nYes\nFLRE\nFBLI\nEccentric Reducing Flange\nYes\nFLRG\nLJSE\nLap Joint Ring\nNo\nFLSC\nFLAN\nScrewed Fitting Flange\nYes\nFLSE\nLJSE\nLap Joint Stub End\nNo\nFLSJ\nFLAN\nSlip-on J-Type Welded Flange\nYes\nFLSO\nFLAN\nSlip-on Flange\nYes\nFLSW\nFLAN\nSocket Weld Flange\nYes\nFLWN\nFLAN\nWeld Neck Flange\nYes\nFO**\nFILT\nOffset Filter\nYes\nFOSO\nFLAN\nSlip-on Flange with Orifice\nYes\nFOWN\nFLAN\nWeld Neck Flange with Orifice\nYes\nFPFL\nFTUB\nFixed Length Pipe with Flanged Ends\nNo\nFPPL\nFTUB\nFixed Length Pipe with Plain Ends\nYes\nFR**\nFILT\nReturn Filter\nNo\nFT**\nPCOM\nFlame Trap\nYes\nFX**\nPCOM\nFlexible Hose\nYes\nFY**\nFILT\n\u2018Y\u2019-type Filter/Strainer\nYes\nH3**\nINST\n3-Way Control Valve\nNo\n12SP\nH4**\nINST\n4-Way Control Valve\nNo\n12SP\nHA**\nINST\nAngled Control Valve\nYes\n12SP\nHC**\nOLET\nScrewed Half Coupling\nYes\nHC**\nOLET\nSocket Weld Half Coupling\nYes\nHV**\nINST\nControl Valve\nYes\n12SP\nIA**\nINST\nAngled Instrument\nYes\nIDFL\nINST\nFlanged Instrument with Dial\nNo\nIDPL\nINST\nInstrument with Dial\nNo\nII**\nINST\nInstrument\nYes\nIO**\nINST\nOffset Instrument\nYes\nIR**\nINST\nReturn Instrument\nNo\nITFL\nOLET\nFlanged Instrument Tee\nNo\nJA**\nINST\nTwo-Level Multiport Valve\nNo\nJB**\nINST\nTwo-Level Multiport Valve\nNo\nJC**\nINST\nTwo-Level Multiport Valve\nNo\nJE**\nINST\nTwo-Level Multiport Valve\nNo\nJG**\nINST\nThree-Level Multiport Valve\nNo\nJK**\nINST\nTwo-Level Multiport Valve\nNo\nJL**\nINST\nOne-Level Multiport Valve\nNo\nJM**\nINST\nThree-Level Multiport Valve\nNo\nJN**\nINST\nThree-Level Multiport Valve\nNo\nJO**\nINST\nTwo-Level Multiport Valve\nNo\nJP**\nINST\nTwo-Level Multiport Valve\nNo\nJT**\nINST\nOne-Level Multiport Valve\nNo\nJU**\nINST\nThree-Level Multiport Valve\nNo\nJV**\nINST\nTwo-Level Multiport Valve\nNo\nJW**\nINST\nThree-Level Multiport Valve\nNo\nJX**\nINST\nThree-Level Multiport Valve\nNo\nJY**\nINST\nThree-Level Multiport Valve\nNo\nJZ**\nINST\nThree-Level Multiport Valve\nNo\nKABW\nCAP\nButt Weld Cap\nYes\nKACP\nCAP\nCompression Fitting Cap\nYes\nKASC\nCAP\nScrewed Fitting Cap\nYes\nKASW\nCAP\nSocket Weld Cap\nYes\nL@BW\nBEND\nButt Weld Lobster Back Bend\nNo\nL@FL\nBEND\nFlanged Lobster Back Bend\nNo\nLA**\nOLET\nButt Weld Latrolet\nYes\nLA**\nOLET\nScrewed Fitting Latrolet\nYes\nLA**\nOLET\nSocket Weld Latrolet\nYes\nLG**\nINST\nLevel Gauge\nNo\nM3**\nINST\n3-Way Motorised Valve\nNo\n11SP\nM4**\nINST\n4-Way Motorised Valve\nNo\nMA**\nINST\nAngled Control Valve\nYes\n11SP\nMIBW\nBEND\nButt Weld Mitred Bend\nNo\nMIFL\nBEND\nFlanged Mitred Bend\nNo\nMTBW\nBEND\nButt Weld Mitred Bend with Tee\nNo\nMTFL\nBEND\nFlanged Mitred Bend with Tee\nNo\nMV**\nINST\nMotorised Valve\nYes\n11SP\nNBSC\nCOUP\nScrewed Nipple\nYes\nNC**\nPCOM\nNon-Category Item\nYes\nNC**\nSHU\nNon-Category Item\nYes\nNI**\nOLET\nPlain End Nipolet\nYes\nNI**\nOLET\nScrewed Fitting Nipolet\nYes\nNRSC\nCOUP\nScrewed Fitting Nipple\nYes\nOP\nINST\nOrifice Plate\nYes\nOTBW\nREDU\nButt Weld Eccentric Reducer with Tee\nYes\nOTFL\nREDU\nFlanged Eccentric Reducer with Tee\nYes\nOTSC\nREDU\nScrewed Fitting Eccentric Reducer with Tee\nYes\nPB+D\nBEND\nPulled Bend\nNo\nPF\nCLOS\nFixed Length Pipe Block\nYes\nPL\nPCOM\nPlug\nYes\nPR\nINST\nRestrictor Plate\nYes\nPV\nCLOS\nVariable Length Pipe Block\nYes\nRA**\nINST\nAngled Relief Valve\nYes\n02SP\nRBSC\nREDU\nScrewed Fitting Concentric Reducing Bush\nYes\nRBSW\nREDU\nSocket Weld Concentric Reducing Bush\nYes\nRCBW\nREDU\nButt Weld Concentric Reducer\nYes\nRCCP\nREDU\nCompression Fitting Concentric Reducer\nYes\nRCFL\nREDU\nFlanged Concentric Reducer\nYes\nRCSC\nREDU\nScrewed Fitting Concentric Reducer\nYes\nRCSW\nREDU\nSocket Weld Concentric Reducer\nYes\nRD\nVENT\nRupture Disc\nYes\nREBW\nREDU\nButt Weld Eccentric Reducer\nYes\nREFL\nREDU\nFlanged Eccentric Reducer\nYes\nRESC\nREDU\nScrewed Fitting Eccentric Reducer\nYes\nRF\nREDU\nSpecial Reducing Flange\nYes\nRNSC\nREDU\nNipple Fitting Concentric Reducer\nYes\nRP\nPCOM\nRestrictor Plate\nYes\nRV**\nINST\nRelief Valve\nYes\nS3**\nINST\n3-Way Control Valve with Square Indicator\nNo\n10SP\nS4**\nINST\n4-Way Control Valve with Square Indicator\nNo\n10SP\nSA**\nINST\nAngled Control Valve with Square Indicator\nYes\n10SP\nSB\nPCOM\nSpectacle Blind\nYes\nSG**\nPCOM\nSight Glass\nYes\nSK**\nOLET\nSocket Weld Sockolet\nYes\nSP\nPCOM\nSlip Plate\nYes\nSR\nPCOM\nSlip Ring\nYes\nSV**\nINST\nControl Valve with Square Indicator\nYes\n10SP\nSW**\nOLET\nButt Weld Sweepolet\nYes\nT@BW\nBEND\nButt Weld Lobster Back Bend with Tee\nNo\nT@FL\nBEND\nFlanged Lobster Back Bend with Tee\nNo\nTA**\nTRAP\nAngled Trap\nYes\nTB+D\nBEND\nPulled Bend with Tee\nNo\nTEBW\nTEE\nButt Weld Tee\nNo\nTECP\nTEE\nCompression Fitting Tee\nNo\nTEFL\nTEE\nFlanged Tee\nNo\nTERF\nTEE\nReinforced Tee\nNo\nTESC\nTEE\nScrewed Fitting Tee\nNo\nTESI\nTEE\nReserved for pipe tappings\nNo\nTESO\nTEE\nSet On Tee\nNo\nTESW\nTEE\nSocket Weld Tee\nNo\nTH**\nOLET\nScrewed Fitting Thredolet\nYes\nTI**\nTRAP\nIn-line Trap\nYes\nTO**\nTRAP\nOffset Trap\nYes\nTPUL\nTEE\nPulled Tee\nNo\nTR**\nTRAP\nReturn Trap\nNo\nTSBW\nTEE\nButt Weld Swept Tee\nNo\nTSCP\nTEE\nCompression Fitting Swept Tee\nNo\nTSFL\nTEE\nFlanged Swept Tee\nNo\nTSSW\nTEE\nSocket Weld Swept Tee\nNo\nTU**\nPCOM\nTundish or Funnel\nYes\nUNBW\nUNIO\nUnion - Butt Weld\nYes\nUNIV\nPCOM\nUniversal Skey for special fittings\nYes Refer to\nISODRAFT User Guide\nUNSC\nUNIO\nScrewed Fitting Union\nYes\nUNSW\nUNIO\nButt or Socket Weld Union\nYes\nV3**\nVTWA\n3-Way Valve\nNo\n01SP\nV4**\nVFWA\n4-Way Valve\nNo\n01SP\nVB**\nVALV\nBall Valve\nYes\n03SP\nVC**\nVALV\nCheck Valve\nYes\nVD**\nVALV\nDiaphragm Valve\nYes\n01SP\nVG**\nVALV\nGlobe Valve\nYes\n01SP\nVK**\nVALV\nCock Valve\nYes\n03SP\nVN**\nVALV\nNeedle Valve\nYes\n06SP\nVP**\nVALV\nPlug Valve\nYes\n07SP\nVR**\nVALV\nRelief Valve\nYes\n02SP\nVS**\nVALV\nSlide Valve\nYes\n08SP\nVT**\nVALV\nGate Valve\nYes\n05SP\nVV**\nVALV\nBasic Valve\nYes\n01SP\nVX**\nVALV\nPressure Reducing Valve\nYes\n09SP\nVY**\nVALV\nButterfly Valve\nYes\n03SP\nWF\nWELD\nField Fitted Weld\nNo\nWLC\nOLET\nWelded Circular Lug\nYes\nWLR\nOLET\nWelded Rectangular Lug\nYes\nWS\nWELD\nSite Weld\nNo\nWTBW\nOLET\nButt Weld Weldolet\nYes\nWW\nWELD\nShop Weld\nNo\nX@**\nCROS\nGeneric Y-type Cross with user-definable out- and off- legs\nYes\nXA**\nINST\nAngled Pressure Reducing Valve\nYes\n09SP\nXV**\nINST\nPressure Reducing Valve\nYes\n09SP\nY@**\nTEE\nGeneric Y-type Tee with user-definable out- and off- legs\nYes\n01HG\nHanger (As a basis for user-defined hangers; refer to ISODRAFT User Guide, Section 10.4, Defining a New Hanger)\nYes\nBW\nButt Weld\nCP\nCompression Fitting\nFL\nFlange\nSC\nScrewed Fitting\nSW\nSocket Weld\nPL\nPlain\n@\nin Bends, denotes the number of bend segments (range 1\u20119)\nin X-type and Y-type Crosses/Tees, replaced by an integer in the range 1 to 4, 1\nindicating the largest bore, 4 indicating the smallest bore.\n+\ndenotes the ratio of the bend radius to the pipe bore (range 1\u20119)\nNote: **   denotes any of the following connection types:\nBW\nButt Weld\nCP\nCompression Fitting\nFL\nFlange\nSC\nScrewed Fitting\nSW\nSocket Weld\nPL\nPlain\n@\nin Bends, denotes the number of bend segments (range 1\u20119)\nin X-type and Y-type Crosses/Tees, replaced by an integer in the range 1 to 4, 1\nindicating the largest bore, 4 indicating the smallest bore.\n+\ndenotes the ratio of the bend radius to the pipe bore (range 1\u20119)\n\n\n\nin alphabetic order.\n,\nThe Basic Principles\nSpecial Keys,\nISODRAFT User Guide\nISODRAFT User Guide,\nDefining a New Hanger\nNote\n:"}
{"Headers": "PML1", "Content": "This appendix explains the PML 1 expressions package. These facilities are needed within AVEVA products, for example, to define report templates in AVEVA E3D Design.\nExpressions have types. For example, you can have numeric expressions, text expressions and logical expressions. All the elements in an expression must be of the correct type. For example, if you have two numbers, x and y, and two text strings text1 and text2, the following expression is meaningless:\nx + text1\n$\nx + text1\n$\nHowever, both of the following expressions are valid:\nx + y\n$ adds the values of the numeric variables.\ntext1 + text2\n$ concatenates the two text strings.\nx + y\n$ adds the values of the numeric variables.\ntext1 + text2\n$ concatenates the two text strings.\nThe following types of expressions are available:\nx + text1\n$\nx + y\n$ adds the values of the numeric variables.\ntext1 + text2\n$ concatenates the two text strings.\nLogical Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nReal Arrays\nText Expressions\nLogical Expressions\nLogical Expressions\nLogical Array Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nNumeric (Real) Expressions\nReal Arrays\nReal Arrays\nText Expressions\nText Expressions\nNote:\nGenerally, all these facilities are compatible with PML 2.\n\n\n\nLogical Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nReal Arrays\nText Expressions\nNote\n:\nx + text1\nx + y\ntext1 + text2\nLogical Expressions\nLogical Array Expressions\nNumeric (Real) Expressions\nReal Arrays\nText Expressions"}
{"Headers": "Format of Expressions", "Content": "The format of an expression, for example the use of brackets, spaces and quotes, is important. If you do not follow the rules given below you will get error messages:\nText must be enclosed in quotes. For example:\n\nThere must be a space between each operator and operand. For example:\n\nUse round brackets to control the order of evaluation of expressions and to enclose the argument of a function. For example:\n\nIn general, you do not need spaces before or after brackets, except when a name is followed by a bracket. If there is no space, the bracket will be read as part of the name. For example:\n\n \u2018This is text\u2019\nx + y\nSIN(30)\n(NAME EQ /VESS1 )\n\n\n"}
{"Headers": "Operator Precedence", "Content": "Operators are evaluated in the order of the following list: the ones at the top of the list are evaluated first.\nOperator\nComments\nBRACKETS\nBrackets can be used to control the order in which operators are evaluated, in the same way as in normal arithmetic.\nFUNCTIONS\n* /\n+ -\nEQ, NEQ, LT, LE, GE, GT\nNOT\nAND\nOR\nOperator\nComments\nBRACKETS\nBrackets can be used to control the order in which operators are evaluated, in the same way as in normal arithmetic.\nFUNCTIONS\n\n* /\n\n+ -\n\nEQ, NEQ, LT, LE, GE, GT\n\nNOT\n\nAND\n\nOR\n\n\nOperator\nComments\nBRACKETS\nBrackets can be used to control the order in which operators are evaluated, in the same way as in normal arithmetic.\nFUNCTIONS\n* /\n+ -\nEQ, NEQ, LT, LE, GE, GT\nNOT\nAND\nOR\n\n\n\nOperator\nComments"}
{"Headers": "Nesting Expressions", "Content": "Expressions can be nested using brackets. For example:\n ( (SIN(!angleA) * 2)  /  SIN(!angleB) )\n ( (SIN(!angleA) * 2)  /  SIN(!angleB) )\n\n ( (SIN(!angleA) * 2)  /  SIN(!angleB) )\n\n\n\n ( (SIN(!angleA) * 2)  /  SIN(!angleB) )"}
{"Headers": "Logical Expressions", "Content": "Logical expressions can contain:\nAttributes of type logical, for example, BUILT.\nLogical constants. The constants available are: TRUE, ON, YES for true, and FALSE, OFF, NO for false.\nLogical operators.\nLogical functions.\nAttributes of type logical, for example, BUILT.\nAttributes of type logical, for example, BUILT.\nLogical constants. The constants available are: TRUE, ON, YES for true, and FALSE, OFF, NO for false.\nLogical constants. The constants available are: TRUE, ON, YES for true, and FALSE, OFF, NO for false.\nLogical operators.\nLogical operators.\nLogical functions.\nLogical functions.\n\n\n\nTRUE\nON\nYES\nFALSE\nOFF\nNO"}
{"Headers": "Logical Operators", "Content": "The logical operators available are:\nOperator\nComments\nAND\nEQ, NE\nThe operators EQ and NE may be applied to any pair of values of the same type.\nGT, GE, LE, LT\nThe operators GE, LE, GT, and LT may only be used with numbers and positions. Refer to Positions, Directions and Orientations in Expressions (AVEVA E3D Design only) for further information.\nNOT\nOR\nOperator\nComments\nAND\n\nEQ, NE\nThe operators EQ and NE may be applied to any pair of values of the same type.\nGT, GE, LE, LT\nThe operators GE, LE, GT, and LT may only be used with numbers and positions. Refer to Positions, Directions and Orientations in Expressions (AVEVA E3D Design only) for further information.\nNOT\n\nOR\n\nAND\nSynopsis\nlog1 AND log2\n-> logical\nDescription\nPerform the logical AND between two logical values. Treats unset values as FALSE.\nSide Effects\nIf one of the values is undefined and the other one is FALSE, the result is FALSE.\nExample\nTRUE and FALSE -> FALSE\nSynopsis\nlog1 AND log2\n-> logical\nDescription\nPerform the logical AND between two logical values. Treats unset values as FALSE.\nSide Effects\nIf one of the values is undefined and the other one is FALSE, the result is FALSE.\nExample\nTRUE and FALSE -> FALSE\nEQ and NE\nSynopsis\n( number1 EQual number2)\n-> logical\n( text1 EQual text2 )\n-> logical\n( log1 EQual log2 )\n-> logical\n( id1 EQual id2 )\n-> logical\n( pos1 EQual pos2 )\n-> logical\n( dir1 EQual dir2 )\n-> logical\n( ori1 EQual ori2 )\n-> logical\n( pp1 EQual pp2 )\n-> logical\n( number1 NEqual number2 )\n-> logical\n( text1 NEqual text2 )\n-> logical\n( log1 NEqual log2 )\n-> logical\n( id1 NEqual id2 )\n-> logical\n( pos1 NEqual pos2 )\n-> logical\n( dir1 NEqual dir2 )\n-> logical\n( ori1 NEqual ori2 )\n-> logical\n( pp1 NEqual pp2 )\n-> logical\nDescription\nCompare two values. A special feature is used for the positions, only the coordinates specified are compared. Refer to Comparing Positions for further information.\nUnset values result in FALSE across EQ, TRUE across NE.\nSide Effects\nIf two positions have no common coordinate, for example, \u2019N 10 ne U 10\u2019, the result is undefined. Units are consolidated across comparisons.\nExample\n( 1.0 eq 2.0) -> FALSE\nErrors\nNone.\nSynopsis\n( number1 EQual number2)\n-> logical\n( text1 EQual text2 )\n-> logical\n( log1 EQual log2 )\n-> logical\n( id1 EQual id2 )\n-> logical\n( pos1 EQual pos2 )\n-> logical\n( dir1 EQual dir2 )\n-> logical\n( ori1 EQual ori2 )\n-> logical\n( pp1 EQual pp2 )\n-> logical\n( number1 NEqual number2 )\n-> logical\n( text1 NEqual text2 )\n-> logical\n( log1 NEqual log2 )\n-> logical\n( id1 NEqual id2 )\n-> logical\n( pos1 NEqual pos2 )\n-> logical\n( dir1 NEqual dir2 )\n-> logical\n( ori1 NEqual ori2 )\n-> logical\n( pp1 NEqual pp2 )\n-> logical\nDescription\nCompare two values. A special feature is used for the positions, only the coordinates specified are compared. Refer to Comparing Positions for further information.\nUnset values result in FALSE across EQ, TRUE across NE.\nSide Effects\nIf two positions have no common coordinate, for example, \u2019N 10 ne U 10\u2019, the result is undefined. Units are consolidated across comparisons.\nExample\n( 1.0 eq 2.0) -> FALSE\nErrors\nNone.\nGT, GE, LE and LT\nSynopsis\n( number1 GT number2 )\n> logical\n( pos1 GT pos2 )\n> logical\n( number1 GE number2 )\n> logical\n( pos1 GE pos2 )\n> logical\n( number1 LE number2 )\n> logical\n( pos1 LE pos2 )\n> logical\n( number1 LT number2 )\n> logical\n( pos1 LT pos2 )\n> logical\nDescription\nCompare two values. A special feature is used for positions: only the coordinates specified are compared. Refer to Comparing Positions for further information.\nFor positions, since comparisons may be performed on more than one value, LT (GT) is not the inverse of GE (LE). Unset values result in false.\nSide Effects\nIf two positions have no common coordinate, the result is undefined. For example, \u2019N 10 gt U 10\u2019.\nUnits are consolidated across comparisons.\nExample\n( 1.0 LT 2.0) -> TRUE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\nErrors\nNone.\nSynopsis\n( number1 GT number2 )\n> logical\n( pos1 GT pos2 )\n> logical\n( number1 GE number2 )\n> logical\n( pos1 GE pos2 )\n> logical\n( number1 LE number2 )\n> logical\n( pos1 LE pos2 )\n> logical\n( number1 LT number2 )\n> logical\n( pos1 LT pos2 )\n> logical\nDescription\nCompare two values. A special feature is used for positions: only the coordinates specified are compared. Refer to Comparing Positions for further information.\nFor positions, since comparisons may be performed on more than one value, LT (GT) is not the inverse of GE (LE). Unset values result in false.\nSide Effects\nIf two positions have no common coordinate, the result is undefined. For example, \u2019N 10 gt U 10\u2019.\nUnits are consolidated across comparisons.\nExample\n( 1.0 LT 2.0) -> TRUE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\nErrors\nNone.\nNOT\nSynopsis\nNOT log1\n-> logical\nDescription\nPerform the logical NOT on a logical value.\nSide Effects\nNone.\nExample\nnot TRUE -> FALSE\nErrors\nNone.\nSynopsis\nNOT log1\n-> logical\nDescription\nPerform the logical NOT on a logical value.\nSide Effects\nNone.\nExample\nnot TRUE -> FALSE\nErrors\nNone.\nOR\nSynopsis\nOR log2\n-> logical\nDescription\nPerform the logical inclusive OR between two logical values. (The exclusive OR is defined by using NE.)\nAllows numbers instead of logical values.\nSide Effects\nIf one of the values is undefined and the other one is TRUE, the result is TRUE.\nExample\nTRUE or FALSE -> TRUE\nErrors\nNone.\nSynopsis\nOR log2\n-> logical\nDescription\nPerform the logical inclusive OR between two logical values. (The exclusive OR is defined by using NE.)\nAllows numbers instead of logical values.\nSide Effects\nIf one of the values is undefined and the other one is TRUE, the result is TRUE.\nExample\nTRUE or FALSE -> TRUE\nErrors\nNone.\n\nOperator\nComments\nAND\nEQ, NE\nThe operators EQ and NE may be applied to any pair of values of the same type.\nGT, GE, LE, LT\nThe operators GE, LE, GT, and LT may only be used with numbers and positions. Refer to Positions, Directions and Orientations in Expressions (AVEVA E3D Design only) for further information.\nNOT\nOR\nSynopsis\nlog1 AND log2\n-> logical\nDescription\nPerform the logical AND between two logical values. Treats unset values as FALSE.\nSide Effects\nIf one of the values is undefined and the other one is FALSE, the result is FALSE.\nExample\nTRUE and FALSE -> FALSE\nSynopsis\n( number1 EQual number2)\n-> logical\n( text1 EQual text2 )\n-> logical\n( log1 EQual log2 )\n-> logical\n( id1 EQual id2 )\n-> logical\n( pos1 EQual pos2 )\n-> logical\n( dir1 EQual dir2 )\n-> logical\n( ori1 EQual ori2 )\n-> logical\n( pp1 EQual pp2 )\n-> logical\n( number1 NEqual number2 )\n-> logical\n( text1 NEqual text2 )\n-> logical\n( log1 NEqual log2 )\n-> logical\n( id1 NEqual id2 )\n-> logical\n( pos1 NEqual pos2 )\n-> logical\n( dir1 NEqual dir2 )\n-> logical\n( ori1 NEqual ori2 )\n-> logical\n( pp1 NEqual pp2 )\n-> logical\nDescription\nCompare two values. A special feature is used for the positions, only the coordinates specified are compared. Refer to Comparing Positions for further information.\nUnset values result in FALSE across EQ, TRUE across NE.\nSide Effects\nIf two positions have no common coordinate, for example, \u2019N 10 ne U 10\u2019, the result is undefined. Units are consolidated across comparisons.\nExample\n( 1.0 eq 2.0) -> FALSE\nErrors\nNone.\nSynopsis\n( number1 GT number2 )\n> logical\n( pos1 GT pos2 )\n> logical\n( number1 GE number2 )\n> logical\n( pos1 GE pos2 )\n> logical\n( number1 LE number2 )\n> logical\n( pos1 LE pos2 )\n> logical\n( number1 LT number2 )\n> logical\n( pos1 LT pos2 )\n> logical\nDescription\nCompare two values. A special feature is used for positions: only the coordinates specified are compared. Refer to Comparing Positions for further information.\nFor positions, since comparisons may be performed on more than one value, LT (GT) is not the inverse of GE (LE). Unset values result in false.\nSide Effects\nIf two positions have no common coordinate, the result is undefined. For example, \u2019N 10 gt U 10\u2019.\nUnits are consolidated across comparisons.\nExample\n( 1.0 LT 2.0) -> TRUE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\nErrors\nNone.\nSynopsis\nNOT log1\n-> logical\nDescription\nPerform the logical NOT on a logical value.\nSide Effects\nNone.\nExample\nnot TRUE -> FALSE\nErrors\nNone.\nSynopsis\nOR log2\n-> logical\nDescription\nPerform the logical inclusive OR between two logical values. (The exclusive OR is defined by using NE.)\nAllows numbers instead of logical values.\nSide Effects\nIf one of the values is undefined and the other one is TRUE, the result is TRUE.\nExample\nTRUE or FALSE -> TRUE\nErrors\nNone.\nNote:\nThe operators EQ, NE, LT, GT, LE, and GE are sometimes referred to as comparator or relational operators; NOT, AND, and OR are sometimes referred to as Boolean operators. Refer to Precision of Comparisons for tolerances in comparing numbers.\n\n\n\nPositions, Directions and Orientations in Expressions (AVEVA E3D Design only)\nPrecision of Comparisons\nComparing Positions\nComparing Positions\nOperator\nComments\nAND\nEQ, NE\nEQ\nNE\nGT, GE, LE, LT\nGE\nLE\nGT\nLT\nPositions, Directions and Orientations in Expressions (AVEVA E3D Design only)\nNOT\nOR\nNote\n:\nEQ\nNE\nLT\nGT\nLE\nGE\nNOT\nAND\nOR\nPrecision of Comparisons\nAND\nSynopsis\nlog1 AND log2\n-> logical\nDescription\nAND\nFALSE\nSide Effects\nFALSE\nFALSE\nExample\nTRUE and FALSE -> FALSE\nEQ and NE\nSynopsis\n( number1 EQual number2)\n-> logical\n( text1 EQual text2 )\n-> logical\n( log1 EQual log2 )\n-> logical\n( id1 EQual id2 )\n-> logical\n( pos1 EQual pos2 )\n-> logical\n( dir1 EQual dir2 )\n-> logical\n( ori1 EQual ori2 )\n-> logical\n( pp1 EQual pp2 )\n-> logical\n( number1 NEqual number2 )\n-> logical\n( text1 NEqual text2 )\n-> logical\n( log1 NEqual log2 )\n-> logical\n( id1 NEqual id2 )\n-> logical\n( pos1 NEqual pos2 )\n-> logical\n( dir1 NEqual dir2 )\n-> logical\n( ori1 NEqual ori2 )\n-> logical\n( pp1 NEqual pp2 )\n-> logical\nDescription\nComparing Positions\nFALSE\nEQ\nTRUE\nNE\nSide Effects\nN 10 ne U 10\nExample\n( 1.0 eq 2.0) -> FALSE\nErrors\nGT, GE, LE and LT\nSynopsis\n( number1 GT number2 )\n> logical\n( pos1 GT pos2 )\n> logical\n( number1 GE number2 )\n> logical\n( pos1 GE pos2 )\n> logical\n( number1 LE number2 )\n> logical\n( pos1 LE pos2 )\n> logical\n( number1 LT number2 )\n> logical\n( pos1 LT pos2 )\n> logical\nDescription\nComparing Positions\nLT\nGT\nGE\nLE\nfalse\nSide Effects\nN 10 gt U 10\nExample\n( 1.0 LT 2.0) -> TRUE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\n( N 0 E 10 GT N 10 E 0 ) -> FALSE\nErrors\nNOT\nSynopsis\nNOT log1\n-> logical\nDescription\nNOT\nSide Effects\nExample\nnot TRUE -> FALSE\nErrors\nOR\nSynopsis\nOR log2\n-> logical\nDescription\nOR\nOR\nNE\nSide Effects\nTRUE\nTRUE\nExample\nTRUE or FALSE -> TRUE\nErrors"}
{"Headers": "Logical Functions", "Content": "The logical functions available are:\nFunction\nComments\nBADREF\nDEFINED,UNDEFINED\nCREATED\nDELETED\nEMPTY\nMATCHWILD\nMODIFIED\nUNSET\nVLOGICAL\nFunction\nComments\nBADREF\n\nDEFINED,UNDEFINED\n\nCREATED\n\nDELETED\n\nEMPTY\n\nMATCHWILD\n\nMODIFIED\n\nUNSET\n\nVLOGICAL\n\nBADREF\nSynopsis\nBADREF (id)\n-> logical\nDescription\nTRUE if id is invalid, otherwise FALSE.\nSide Effects\nNone.\nExample\nBADREF(TREF) -> \u2019true\u2019 if TREF=nulref\nErrors\nNone.\nSynopsis\nBADREF (id)\n-> logical\nDescription\nTRUE if id is invalid, otherwise FALSE.\nSide Effects\nNone.\nExample\nBADREF(TREF) -> \u2019true\u2019 if TREF=nulref\nErrors\nNone.\nDEFINED and UNDEFINED\nSynopsis\nDEFined (variable_name)\n-> logical\nDEFined (variable_name,number)\n-> logical\nUNDEFined (variable_name)\n-> logical\nUNDEFined (variable_name , number)\n-> logical\nDescription\nWith one argument, DEFINED is true only if the scalar variable, the array variable, or the array variable element exists.\nWith two arguments, DEFINED is true only if the first argument is an array variable, which has a value for the index, denoted by the second argument.\nUNDEFINED( !foo ) is equivalent to NOT DEFINED( !foo ).\nSide Effects\nNone.\nExample\nDEFINED ( !var ) -> TRUE\nDEFINED ( !array ) -> TRUE\nDEFINED ( !array[1] )) -> TRUE\nDEFINED ( !array , 1 ) -> TRUE\nDEFINED ( !var) -> FALSE\nUNDEFINED ( !array) -> TRUE\nDEFINED ( !array , 3 ) -> FALSE\nErrors\nNone.\nSynopsis\nDEFined (variable_name)\n-> logical\nDEFined (variable_name,number)\n-> logical\nUNDEFined (variable_name)\n-> logical\nUNDEFined (variable_name , number)\n-> logical\nDescription\nWith one argument, DEFINED is true only if the scalar variable, the array variable, or the array variable element exists.\nWith two arguments, DEFINED is true only if the first argument is an array variable, which has a value for the index, denoted by the second argument.\nUNDEFINED( !foo ) is equivalent to NOT DEFINED( !foo ).\nSide Effects\nNone.\nExample\nErrors\nNone.\nCREATED\nSynopsis\nCREATED\n-> logical\nDescription\nReturns TRUE if the element has been created since the set date.\nSide Effects\nNone.\nExample\nCREATED -> TRUE\nErrors\nNone.\nSynopsis\nCREATED\n-> logical\nDescription\nReturns TRUE if the element has been created since the set date.\nSide Effects\nNone.\nExample\nCREATED -> TRUE\nErrors\nNone.\nDELETED\nSynopsis\nDELETED\n-> logical\nDescription\nReturns TRUE if the element has been deleted since the set date.\nSide Effects\nNone.\nExample\nDELETED -> TRUE\nErrors\nNone.\nSynopsis\nDELETED\n-> logical\nDescription\nReturns TRUE if the element has been deleted since the set date.\nSide Effects\nNone.\nExample\nDELETED -> TRUE\nErrors\nNone.\nEMPTY\nSynopsis\nEMPTY(text)\n-> logical\nDescription\nReturns TRUE if text is a zero length string, otherwise FALSE.\nSide Effects\nNone.\nExample\nEMPTY(\u2018\u2019) -> TRUE\nEMPTY(\u2018not empty\u2019) -> FALSE\nErrors\nNone.\nSynopsis\nEMPTY(text)\n-> logical\nDescription\nReturns TRUE if text is a zero length string, otherwise FALSE.\nSide Effects\nNone.\nExample\nEMPTY(\u2018\u2019) -> TRUE\nEMPTY(\u2018not empty\u2019) -> FALSE\nErrors\nNone.\nMATCHWILD\nSynopsis\nMATCHW/ILD( text1, text2)\n-> logical\nMATCHW/ILD( text1, text2, text3)\n-> logical\nMATCHW/ILD( text1, text2, text3, text4)\n-> logical\nDescription\nMatches string text2 to string text1. If they are the same, then returns TRUE, otherwise FALSE. text2 may contain wildcard characters.\nThe defaults for wildcards are '*' for any number of characters, and '?' for a single character.\nWith three arguments, the multiple wildcard character '*' may be redefined by text3.\nWith four arguments the single wildcard character '?' may be redefined by text4.\nSide Effects\nNone.\nExample\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019??big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019???*big*\u2019) -> FALSE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*beer\u2019) -> TRUE\nMATCHW/ILD(\u2019** text\u2019,\u2019**!\u2019,\u2019!\u2019) -> TRUE\nErrors\nNone.\nSynopsis\nMATCHW/ILD( text1, text2)\n-> logical\nMATCHW/ILD( text1, text2, text3)\n-> logical\nMATCHW/ILD( text1, text2, text3, text4)\n-> logical\nDescription\nMatches string text2 to string text1. If they are the same, then returns TRUE, otherwise FALSE. text2 may contain wildcard characters.\nThe defaults for wildcards are '*' for any number of characters, and '?' for a single character.\nWith three arguments, the multiple wildcard character '*' may be redefined by text3.\nWith four arguments the single wildcard character '?' may be redefined by text4.\nSide Effects\nNone.\nExample\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019??big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019???*big*\u2019) -> FALSE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*beer\u2019) -> TRUE\nMATCHW/ILD(\u2019** text\u2019,\u2019**!\u2019,\u2019!\u2019) -> TRUE\nErrors\nNone.\nMODIFIED\nSynopsis\nDescription\nFor sophisticated queries relating to modifications. Returns TRUE if a modification has taken place.\nEach attribute name may be followed by the following qualifying keywords:\nOFFSPRING, to check this element and members.\nSIGNIF, to check all elements for which this element represents the significant one.\nPRIMARY, check all elements for which this element represents the primary one.\nDESCENDANTS, this element and everything below (descendants).\nThe OF syntax may be used as for attributes.\nThe MODIFIED function or the GEOM, CATTEXT, and CATMOD pseudo-attributes can be used instead of the AFTERDATE function.Refer to Pseudo Attributes for further information.\nThe MODIFIED, DELETED, and CREATED functions may go anywhere within a PML1 expression, as in, after Q/VAR and within collections.\nSide Effects\nNone.\nExample\nQ MODIFIED()\nReturns TRUE if element has changed at all since the comparison date.\nIt will also return TRUE if the element has been created since the comparison date.\nQ MODIFIED(POS,ORI)\nReturns TRUE if POS or ORI modified since the comparison date.\nQ MODIFIED(P1 POS)\nReturns TRUE if the position of P1 has changed.\nQ MODIFIED(GEOM DESCENDANTS\nReturns TRUE if any geometry for item or any descendants has changed.\nQ MODIFIED(PRIMARY)\nReturns TRUE if any element for which this element is primary, has changed.\nQ MODIFIED() OF /PIPE1\nReturns TRUE if /PIPE1 has been modified since the comparison date.\nQ (BUIL OR MODIFIED()OR ELECREC OF NEXT )\nErrors\nNone.\nDescription\nFor sophisticated queries relating to modifications. Returns TRUE if a modification has taken place.\nEach attribute name may be followed by the following qualifying keywords:\nThe OF syntax may be used as for attributes.\nThe MODIFIED function or the GEOM, CATTEXT, and CATMOD pseudo-attributes can be used instead of the AFTERDATE function.Refer to Pseudo Attributes for further information.\n\nThe MODIFIED, DELETED, and CREATED functions may go anywhere within a PML1 expression, as in, after Q/VAR and within collections.\nSide Effects\nNone.\nExample\nQ MODIFIED()\nReturns TRUE if element has changed at all since the comparison date.\nIt will also return TRUE if the element has been created since the comparison date.\nQ MODIFIED(POS,ORI)\nReturns TRUE if POS or ORI modified since the comparison date.\nQ MODIFIED(P1 POS)\nReturns TRUE if the position of P1 has changed.\nQ MODIFIED(GEOM DESCENDANTS\nReturns TRUE if any geometry for item or any descendants has changed.\nQ MODIFIED(PRIMARY)\nReturns TRUE if any element for which this element is primary, has changed.\nQ MODIFIED() OF /PIPE1\nReturns TRUE if /PIPE1 has been modified since the comparison date.\nQ (BUIL OR MODIFIED()OR ELECREC OF NEXT )\n\nErrors\nNone.\nThe MODIFIED, DELETED, and CREATED functions are not implemented within PML2 expressions.\nUNSET\nSynopsis\nUNSET(value)\n-> logical\nDescription\nReturns TRUE if value is unset, otherwise FALSE. The value can be of any data type including ARRAYS. Normally, it will be a attribute.\nSide Effects\nNone.\nExample\nUNSET( DESC )\nTRUE where DESC is an unset text attribute.\nUNSET(CRFA)\nFALSE where CRFA contains unset reference attributes.\nErrors\nNone.\nSynopsis\nUNSET(value)\n-> logical\nDescription\nReturns TRUE if value is unset, otherwise FALSE. The value can be of any data type including ARRAYS. Normally, it will be a attribute.\nSide Effects\nNone.\nExample\nUNSET( DESC )\nTRUE where DESC is an unset text attribute.\nUNSET(CRFA)\nFALSE where CRFA contains unset reference attributes.\nErrors\nNone.\nVLOGICAL\nVLOGICAL is used for the late evaluation of variables.\nSynopsis\nVLOGICAL ( variable_name ))\n-> logical\nVLOGICAL ( variable_name , number)\n-> logical\nDescription\nWith one argument, return the value of the scalar variable or the value of the array variable element as a logical.\nWith two arguments, return the value of the element corresponding to the index number as a logical.\nThe rules of conversion are:\nTRUE for the strings 'T', 'TR', 'TRU' or 'TRUE' (case insensitive) or any numeric value not equal to zero.\nFALSE for the strings 'F', 'FA', 'FAL', 'FALS' or 'FALSE' (case insensitive) or a numeric value equal to zero.\nScalar variables may not be indexed. For example, VTEXT(!var[1]) will return an error.\nArray variables must have an index. For example, VTEXT (!array) will return an error.\nThe value cannot be translated into a logical.\nSee also VTEXT, used for late evaluation when a text result is required, and VVALUE, used for late evaluation when a numeric result is required.\nSide Effects\nIf the scalar variable, the array variable, or the array variable element does not exist, the result is undefined.\nExample\nVLOG ( !array[1] ) -> TRUE\nVLOG ( !array , 2 ) -> FALSE\nErrors\nNone.\nSynopsis\nVLOGICAL ( variable_name ))\n-> logical\nVLOGICAL ( variable_name , number)\n-> logical\nDescription\nWith one argument, return the value of the scalar variable or the value of the array variable element as a logical.\nWith two arguments, return the value of the element corresponding to the index number as a logical.\nThe rules of conversion are:\nThe value cannot be translated into a logical.\nSee also VTEXT, used for late evaluation when a text result is required, and VVALUE, used for late evaluation when a numeric result is required.\nSide Effects\nIf the scalar variable, the array variable, or the array variable element does not exist, the result is undefined.\nExample\nVLOG ( !array[1] ) -> TRUE\nVLOG ( !array , 2 ) -> FALSE\nErrors\nNone.\nFunction\nComments\nBADREF\nDEFINED,UNDEFINED\nCREATED\nDELETED\nEMPTY\nMATCHWILD\nMODIFIED\nUNSET\nVLOGICAL\nSynopsis\nBADREF (id)\n-> logical\nDescription\nTRUE if id is invalid, otherwise FALSE.\nSide Effects\nNone.\nExample\nBADREF(TREF) -> \u2019true\u2019 if TREF=nulref\nErrors\nNone.\nSynopsis\nDEFined (variable_name)\n-> logical\nDEFined (variable_name,number)\n-> logical\nUNDEFined (variable_name)\n-> logical\nUNDEFined (variable_name , number)\n-> logical\nDescription\nWith one argument, DEFINED is true only if the scalar variable, the array variable, or the array variable element exists.\nWith two arguments, DEFINED is true only if the first argument is an array variable, which has a value for the index, denoted by the second argument.\nUNDEFINED( !foo ) is equivalent to NOT DEFINED( !foo ).\nSide Effects\nNone.\nExample\nDEFINED ( !var ) -> TRUE\nDEFINED ( !array ) -> TRUE\nDEFINED ( !array[1] )) -> TRUE\nDEFINED ( !array , 1 ) -> TRUE\nDEFINED ( !var) -> FALSE\nUNDEFINED ( !array) -> TRUE\nDEFINED ( !array , 3 ) -> FALSE\nErrors\nNone.\nSynopsis\nCREATED\n-> logical\nDescription\nReturns TRUE if the element has been created since the set date.\nSide Effects\nNone.\nExample\nCREATED -> TRUE\nErrors\nNone.\nSynopsis\nDELETED\n-> logical\nDescription\nReturns TRUE if the element has been deleted since the set date.\nSide Effects\nNone.\nExample\nDELETED -> TRUE\nErrors\nNone.\nSynopsis\nEMPTY(text)\n-> logical\nDescription\nReturns TRUE if text is a zero length string, otherwise FALSE.\nSide Effects\nNone.\nExample\nEMPTY(\u2018\u2019) -> TRUE\nEMPTY(\u2018not empty\u2019) -> FALSE\nErrors\nNone.\nSynopsis\nMATCHW/ILD( text1, text2)\n-> logical\nMATCHW/ILD( text1, text2, text3)\n-> logical\nMATCHW/ILD( text1, text2, text3, text4)\n-> logical\nDescription\nMatches string text2 to string text1. If they are the same, then returns TRUE, otherwise FALSE. text2 may contain wildcard characters.\nThe defaults for wildcards are '*' for any number of characters, and '?' for a single character.\nWith three arguments, the multiple wildcard character '*' may be redefined by text3.\nWith four arguments the single wildcard character '?' may be redefined by text4.\nSide Effects\nNone.\nExample\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019??big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019???*big*\u2019) -> FALSE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*beer\u2019) -> TRUE\nMATCHW/ILD(\u2019** text\u2019,\u2019**!\u2019,\u2019!\u2019) -> TRUE\nErrors\nNone.\nDescription\nFor sophisticated queries relating to modifications. Returns TRUE if a modification has taken place.\nEach attribute name may be followed by the following qualifying keywords:\nOFFSPRING, to check this element and members.\nSIGNIF, to check all elements for which this element represents the significant one.\nPRIMARY, check all elements for which this element represents the primary one.\nDESCENDANTS, this element and everything below (descendants).\nThe OF syntax may be used as for attributes.\nThe MODIFIED function or the GEOM, CATTEXT, and CATMOD pseudo-attributes can be used instead of the AFTERDATE function.Refer to Pseudo Attributes for further information.\nThe MODIFIED, DELETED, and CREATED functions may go anywhere within a PML1 expression, as in, after Q/VAR and within collections.\nSide Effects\nNone.\nExample\nQ MODIFIED()\nReturns TRUE if element has changed at all since the comparison date.\nIt will also return TRUE if the element has been created since the comparison date.\nQ MODIFIED(POS,ORI)\nReturns TRUE if POS or ORI modified since the comparison date.\nQ MODIFIED(P1 POS)\nReturns TRUE if the position of P1 has changed.\nQ MODIFIED(GEOM DESCENDANTS\nReturns TRUE if any geometry for item or any descendants has changed.\nQ MODIFIED(PRIMARY)\nReturns TRUE if any element for which this element is primary, has changed.\nQ MODIFIED() OF /PIPE1\nReturns TRUE if /PIPE1 has been modified since the comparison date.\nQ (BUIL OR MODIFIED()OR ELECREC OF NEXT )\nErrors\nNone.\nSynopsis\nUNSET(value)\n-> logical\nDescription\nReturns TRUE if value is unset, otherwise FALSE. The value can be of any data type including ARRAYS. Normally, it will be a attribute.\nSide Effects\nNone.\nExample\nUNSET( DESC )\nTRUE where DESC is an unset text attribute.\nUNSET(CRFA)\nFALSE where CRFA contains unset reference attributes.\nErrors\nNone.\nSynopsis\nVLOGICAL ( variable_name ))\n-> logical\nVLOGICAL ( variable_name , number)\n-> logical\nDescription\nWith one argument, return the value of the scalar variable or the value of the array variable element as a logical.\nWith two arguments, return the value of the element corresponding to the index number as a logical.\nThe rules of conversion are:\nTRUE for the strings 'T', 'TR', 'TRU' or 'TRUE' (case insensitive) or any numeric value not equal to zero.\nFALSE for the strings 'F', 'FA', 'FAL', 'FALS' or 'FALSE' (case insensitive) or a numeric value equal to zero.\nScalar variables may not be indexed. For example, VTEXT(!var[1]) will return an error.\nArray variables must have an index. For example, VTEXT (!array) will return an error.\nThe value cannot be translated into a logical.\nSee also VTEXT, used for late evaluation when a text result is required, and VVALUE, used for late evaluation when a numeric result is required.\nSide Effects\nIf the scalar variable, the array variable, or the array variable element does not exist, the result is undefined.\nExample\nVLOG ( !array[1] ) -> TRUE\nVLOG ( !array , 2 ) -> FALSE\nErrors\nNone.\n                                  .-----------------------------------.\n                                 /                                    |\n>- MODIFIED-(-+- attname -------*- DESCENDANTS \u2011-+-+-comma +-attname \u2011\u2019\n              |                 |                | |\n              |- DESCENDANTS -. |- SIGNIFICANT --| |\n              |               | |                | |\n              |- SIGNIFICANT--| |- PRIMARY ----- | |\n              |               | |                | |\n              |- PRIMARY -----| |- OFFSPRING-----| |\n              |               | |                | |\n              |- OFFSPRING ---| \u2018----------------\u2019 |\n              |               |                    |\n              |               |                    |\n              |               |                    |\n              \u2018---------------+--------------------+--+-- ) - OF \u2011 id\n                                                      |\n                                                      \u2018-\nOFFSPRING, to check this element and members.\nSIGNIF, to check all elements for which this element represents the significant one.\nPRIMARY, check all elements for which this element represents the primary one.\nDESCENDANTS, this element and everything below (descendants).\nOFFSPRING, to check this element and members.\nOFFSPRING, to check this element and members.\nSIGNIF, to check all elements for which this element represents the significant one.\nSIGNIF, to check all elements for which this element represents the significant one.\nPRIMARY, check all elements for which this element represents the primary one.\nPRIMARY, check all elements for which this element represents the primary one.\nDESCENDANTS, this element and everything below (descendants).\nDESCENDANTS, this element and everything below (descendants).\nTRUE for the strings 'T', 'TR', 'TRU' or 'TRUE' (case insensitive) or any numeric value not equal to zero.\nFALSE for the strings 'F', 'FA', 'FAL', 'FALS' or 'FALSE' (case insensitive) or a numeric value equal to zero.\nScalar variables may not be indexed. For example, VTEXT(!var[1]) will return an error.\nArray variables must have an index. For example, VTEXT (!array) will return an error.\nTRUE for the strings 'T', 'TR', 'TRU' or 'TRUE' (case insensitive) or any numeric value not equal to zero.\nTRUE for the strings 'T', 'TR', 'TRU' or 'TRUE' (case insensitive) or any numeric value not equal to zero.\nFALSE for the strings 'F', 'FA', 'FAL', 'FALS' or 'FALSE' (case insensitive) or a numeric value equal to zero.\nFALSE for the strings 'F', 'FA', 'FAL', 'FALS' or 'FALSE' (case insensitive) or a numeric value equal to zero.\nScalar variables may not be indexed. For example, VTEXT(!var[1]) will return an error.\nScalar variables may not be indexed. For example, VTEXT(!var[1]) will return an error.\nArray variables must have an index. For example, VTEXT (!array) will return an error.\nArray variables must have an index. For example, VTEXT (!array) will return an error.\n\n\n\nPseudo Attributes\nFunction\nComments\nBADREF\nDEFINED,UNDEFINED\nCREATED\nDELETED\nEMPTY\nMATCHWILD\nMODIFIED\nUNSET\nVLOGICAL\nBADREF\nSynopsis\nBADREF (id)\n-> logical\nDescription\nTRUE\nid\nFALSE\nSide Effects\nExample\nBADREF(TREF) -> \u2019true\u2019 if TREF=nulref\nErrors\nDEFINED and UNDEFINED\nSynopsis\nDEFined (variable_name)\n-> logical\nDEFined (variable_name,number)\n-> logical\nUNDEFined (variable_name)\n-> logical\nUNDEFined (variable_name , number)\n-> logical\nDescription\nDEFINED\ntrue\nDEFINED\ntrue\nUNDEFINED( !foo )\nNOT DEFINED( !foo )\nSide Effects\nExample\nErrors\nCREATED\nSynopsis\nCREATED\n-> logical\nDescription\nTRUE\nSide Effects\nExample\nCREATED -> TRUE\nErrors\nDELETED\nSynopsis\nDELETED\n-> logical\nDescription\nTRUE\nSide Effects\nExample\nDELETED -> TRUE\nErrors\nEMPTY\nSynopsis\nEMPTY(text)\n-> logical\nDescription\nTRUE\nFALSE\nSide Effects\nExample\nEMPTY(\u2018\u2019) -> TRUE\nEMPTY(\u2018not empty\u2019) -> FALSE\nErrors\nMATCHWILD\nSynopsis\nMATCHW/ILD( text1, text2)\n-> logical\nMATCHW/ILD( text1, text2, text3)\n-> logical\nMATCHW/ILD( text1, text2, text3, text4)\n-> logical\nDescription\ntext2\ntext1\nTRUE\nFALSE\ntext2\n*\n?\n*\ntext3\n?\ntext4\nSide Effects\nExample\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019??big*\u2019) -> TRUE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019???*big*\u2019) -> FALSE\nMATCHW/ILD(\u2019A big bottle of beer\u2019,\u2019*big*beer\u2019) -> TRUE\nMATCHW/ILD(\u2019** text\u2019,\u2019**!\u2019,\u2019!\u2019) -> TRUE\nErrors\nMODIFIED\nSynopsis\n                                  .-----------------------------------.\n                                 /                                    |\n>- MODIFIED-(-+- attname -------*- DESCENDANTS \u2011-+-+-comma +-attname \u2011\u2019\n              |                 |                | |\n              |- DESCENDANTS -. |- SIGNIFICANT --| |\n              |               | |                | |\n              |- SIGNIFICANT--| |- PRIMARY ----- | |\n              |               | |                | |\n              |- PRIMARY -----| |- OFFSPRING-----| |\n              |               | |                | |\n              |- OFFSPRING ---| \u2018----------------\u2019 |\n              |               |                    |\n              |               |                    |\n              |               |                    |\n              \u2018---------------+--------------------+--+-- ) - OF \u2011 id\n                                                      |\n                                                      \u2018-\nDescription\nTRUE\nOFFSPRING\nSIGNIF\nPRIMARY\nDESCENDANTS\nOF\nMODIFIED\nGEOM\nCATTEXT\nCATMOD\nAFTERDATE\nPseudo Attributes\nMODIFIED\nDELETED\nCREATED\nQ/VAR\nSide Effects\nExample\nQ MODIFIED()\nTRUE\nTRUE\nQ MODIFIED(POS,ORI)\nTRUE\nPOS\nORI\nQ MODIFIED(P1 POS)\nTRUE\nP1\nQ MODIFIED(GEOM DESCENDANTS\nTRUE\nQ MODIFIED(PRIMARY)\nTRUE\nQ MODIFIED() OF /PIPE1\nTRUE\n/PIPE1\nQ (BUIL OR MODIFIED()OR ELECREC OF NEXT )\nErrors\nMODIFIED\nDELETED\nCREATED\nUNSET\nSynopsis\nUNSET(value)\n-> logical\nDescription\nTRUE\nvalue\nFALSE\nSide Effects\nExample\nUNSET( DESC )\nTRUE\nDESC\nUNSET(CRFA)\nFALSE\nCRFA\nErrors\nVLOGICAL\nVLOGICAL\nSynopsis\nVLOGICAL ( variable_name ))\n-> logical\nVLOGICAL ( variable_name , number)\n-> logical\nDescription\nTRUE\nT\nTR\nTRU\nTRUE\nFALSE\nF\nFA\nFAL\nFALS\nFALSE\nVTEXT(!var[1])\nVTEXT (!array)\nVTEXT\nVVALUE\nSide Effects\nExample\nVLOG ( !array[1] ) -> TRUE\nVLOG ( !array , 2 ) -> FALSE\nErrors"}
{"Headers": "Logical Array Expressions", "Content": "Logical array expressions can contain:\nAVEVA E3D Design attributes of type logical array. For example, LOGARR where 'LOGARR' is a UDA of type logical.\nLogical constants. The constants available are: TRUE, ON, YES for true; and FALSE, OFF, NO for false.\nLogical operators. Refer to Logical Operators for further information.\nLogical functions. Refer to Logical Functions for further information.\nAVEVA E3D Design attributes of type logical array. For example, LOGARR where 'LOGARR' is a UDA of type logical.\nAVEVA E3D Design attributes of type logical array. For example, LOGARR where 'LOGARR' is a UDA of type logical.\nLogical constants. The constants available are: TRUE, ON, YES for true; and FALSE, OFF, NO for false.\nLogical constants. The constants available are: TRUE, ON, YES for true; and FALSE, OFF, NO for false.\nLogical operators. Refer to Logical Operators for further information.\nLogical operators. Refer to Logical Operators for further information.\nLogical functions. Refer to Logical Functions for further information.\nLogical functions. Refer to Logical Functions for further information.\n\n\n\nLogical Operators\nLogical Functions\nLOGARR\nTRUE\nON\nYES\nFALSE\nOFF\nNO\nLogical Operators\n.\nLogical Functions\n."}
{"Headers": "Numeric (Real) Expressions", "Content": "In expressions, integers are treated as reals; they are fully interchangeable. Numeric expressions can contain:\nNumbers, for example, 32, 10.1, and so on.\nNumbers can be given as as integer exponents, for example: 10 exp 5, and 5 E 6.\nNumbers be qualified by unit names.\nAttributes of type number, for example: XLEN.\nPosition, direction and orientation attributes which have a subscript to indicate which part of the array is required. For example, POS[2] means the second element of the POSITION attribute; that is, the northing. Note that position, direction and orientation attributes without subscripts can only be used in number array expressions.\nThe keyword PI (3.142).\nNumeric operators.\nNumeric functions.\nNumbers, for example, 32, 10.1, and so on.\nNumbers, for example, 32, 10.1, and so on.\nNumbers can be given as as integer exponents, for example: 10 exp 5, and 5 E 6.\nNumbers can be given as as integer exponents, for example: 10 exp 5, and 5 E 6.\nNumbers be qualified by unit names.\nNumbers be qualified by unit names.\nAttributes of type number, for example: XLEN.\nAttributes of type number, for example: XLEN.\nPosition, direction and orientation attributes which have a subscript to indicate which part of the array is required. For example, POS[2] means the second element of the POSITION attribute; that is, the northing. Note that position, direction and orientation attributes without subscripts can only be used in number array expressions.\nPosition, direction and orientation attributes which have a subscript to indicate which part of the array is required. For example, POS[2] means the second element of the POSITION attribute; that is, the northing. Note that position, direction and orientation attributes without subscripts can only be used in number array expressions.\nThe keyword PI (3.142).\nThe keyword PI (3.142).\nNumeric operators.\nNumeric operators.\nNumeric functions.\nNumeric functions.\n\n\n\nPOS[2]\nPOSITION"}
{"Headers": "Real Physical Quantities with Units", "Content": "Numbers can be qualified by an appended unit string. Most common are the standard MM, M/etres, IN/ches, FT. However any of the standard units supported by the system (refer to Standard Units) can be used together with most combinations of them in compound unit strings. Feet and inches can also be shown as in 10'6.\nSuch values are always internally converted to internal database units so that any processing, comparison etc., done with these values is always done consistently and in the same units.\nFunction arguments if not purely numeric must be consistent with each other and the function itself. For example trigonometric functions (SIN, COS etc.) must have arguments defined in angle units (in any at all). General functions like MIN, MAX must have all arguments which have units consistent with the same physical quantity (e.g. units of length).\nArithmetic expressions must add and subtract unit consistent quantities.\nMultiplication and division will generate reals of the same physical quantity (but scaled) if only one value has units, or a real of a new physical quantities if both have. For example there is a difference between (5 * 10inch) and (5mm * 10inch) which are 50inch and 1.9685 square inches respectively.\nWhen numbers have units that are not consistent with each other, or the function or expression they are being used then warnings, and sometimes (for serious problems) errors are raised.\n\n\n\nStandard Units\nStandard Units\n)"}
{"Headers": "Numeric (Real) Operators", "Content": "The numeric operators available are:\nOperator\nComments\n+\nAddition.\n-\nSubtraction.\n*\nMultiplication.\n/\nDivision.\nOperator\nComments\n+\nAddition.\n-\nSubtraction.\n*\nMultiplication.\n/\nDivision.\n\nOperator\nComments\n+\nAddition.\n-\nSubtraction.\n*\nMultiplication.\n/\nDivision.\n\n\n\nOperator\nComments"}
{"Headers": "ADD and SUBTRACT (+ and -)", "Content": "Synopsis\nnumber + number\n-> number\nnumber \u2011 number\n-> number\n+ number\n-> number\n- number\n-> number\nDescription\nAdd or subtract two numbers. They can also be used as unary operators at the beginning of a parenthesized sub-expression.\nSide Effects\nUnits are consolidated across add and subtract.\nExample\n1 + 2 -> 3.0\n1 \u2011 2 -> 1.0\n+ 1 -> 1.0\n- 1 -> -1.0\nErrors\nFloating point underflow.\nSynopsis\nnumber + number\n-> number\nnumber \u2011 number\n-> number\n+ number\n-> number\n- number\n-> number\nDescription\nAdd or subtract two numbers. They can also be used as unary operators at the beginning of a parenthesized sub-expression.\nSide Effects\nUnits are consolidated across add and subtract.\nExample\n1 + 2 -> 3.0\n1 \u2011 2 -> 1.0\n+ 1 -> 1.0\n- 1 -> -1.0\nErrors\nFloating point underflow.\n\nSynopsis\nnumber + number\n-> number\nnumber \u2011 number\n-> number\n+ number\n-> number\n- number\n-> number\nDescription\nAdd or subtract two numbers. They can also be used as unary operators at the beginning of a parenthesized sub-expression.\nSide Effects\nUnits are consolidated across add and subtract.\nExample\n1 + 2 -> 3.0\n1 \u2011 2 -> 1.0\n+ 1 -> 1.0\n- 1 -> -1.0\nErrors\nFloating point underflow.\n\n\n\nSynopsis\nnumber + number\n-> number\nnumber \u2011 number\n-> number\n+ number\n-> number\n- number\n-> number\nDescription\nSide Effects\nExample\n1 + 2 -> 3.0\n1 \u2011 2 -> 1.0\n+ 1 -> 1.0\n- 1 -> -1.0\nErrors"}
{"Headers": "MULTIPLY and DIVIDE (* and /)", "Content": "Synopsis\nnumber * number\n-> number\nnumber / number\n-> number\nDescription\nMultiply or divide two numbers.\nThey can also be used as unary operators at the beginning of a parenthesized sub-expression.\nNumeric underflow is not considered to be an error and neither is it flagged as a warning. The result returned is zero.\nSide Effects\nUnits are consolidated across Multiply and Divide.\nThe dimension of the result of the expression is determined from the combination of all the values being combined.\nFor example, '1kg / (1m * 1m *1m )' will give a density of '1kg/m3'.\nExample\n2 * 3 -> 6.0\n2 / 3 -> 0.666666666\nErrors\nDivide by zero.\nSynopsis\nnumber * number\n-> number\nnumber / number\n-> number\nDescription\nMultiply or divide two numbers.\nThey can also be used as unary operators at the beginning of a parenthesized sub-expression.\nNumeric underflow is not considered to be an error and neither is it flagged as a warning. The result returned is zero.\nSide Effects\nUnits are consolidated across Multiply and Divide.\nThe dimension of the result of the expression is determined from the combination of all the values being combined.\nFor example, '1kg / (1m * 1m *1m )' will give a density of '1kg/m3'.\nExample\n2 * 3 -> 6.0\n2 / 3 -> 0.666666666\nErrors\nDivide by zero.\n\nSynopsis\nnumber * number\n-> number\nnumber / number\n-> number\nDescription\nMultiply or divide two numbers.\nThey can also be used as unary operators at the beginning of a parenthesized sub-expression.\nNumeric underflow is not considered to be an error and neither is it flagged as a warning. The result returned is zero.\nSide Effects\nUnits are consolidated across Multiply and Divide.\nThe dimension of the result of the expression is determined from the combination of all the values being combined.\nFor example, '1kg / (1m * 1m *1m )' will give a density of '1kg/m3'.\nExample\n2 * 3 -> 6.0\n2 / 3 -> 0.666666666\nErrors\nDivide by zero.\n\n\n\nSynopsis\nnumber * number\n-> number\nnumber / number\n-> number\nDescription\nzero\nSide Effects\nExample\n2 * 3 -> 6.0\n2 / 3 -> 0.666666666\nErrors"}
{"Headers": "Numeric (Real) Functions", "Content": "The numeric functions available are:\nFunction\nComments\nABS ( number1 )\nGives the absolute value of a number\nACOS ( number1 )\nGives the arc cosine of a number, in degrees.\nASIN ( number1 )\nGives the arc sine of a number, in degrees.\nATAN ( number1 )\nGives the arc tangent of a number, in degrees.\nATANT ( number1, number2 )\nGives the arc tangent of number1/number2, in degrees, with the appropriate sign.\nALOG ( number1 )\nGives the exponential function (natural anti-log) of a number.\nARRAY(pos or dir or ori)\nConverts a position, direction or orientation value or attribute into three numbers.\nARRAYSIZE ( variable-name )\nGives the size of an array variable.\nARRAYWIDTH( variable-name )\nGives the largest display width of any string in array variable-name.\nCOMPONENT dir OF pos2\nGives the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nINT ( number1 )\nGives the truncated integer value of a number.\nSIN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in degrees).\nCOS ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in degrees).\nTAN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in degrees).\nLENGTH ( text1 )\nGives the length of text1.\nLOG ( number1 )\nGives the natural logarithm of a number.\nMATCH ( text1, text2 )\nGives the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nMAX ( number1, number2[ , number3 [. . .]]) )\nGives the maximum value of the arguments.\nMIN ( number1, number2[ , number3 [. . .]]) )\nGives the minimum value of the arguments.\nNEGATE\nMultiply a number by -1.0.\nNINT ( number1 )\nGives the nearest integer to a real.\nNINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nOCCUR ( text1, text2 )\nGives the number of times string text2 occurs in string text1.\nREAL ( text1 )\nTry to read a number at the beginning of text1.\nPOWER ( number1, number2 )\nGives the value of number1 raised to the power number2.\nSQRT ( number1 )\nGives the square root of a number.\nVVALUE ( variable-name )\nUsed for late evaluation of variables. Gives a real value.\nFunction\nComments\nABS ( number1 )\nGives the absolute value of a number\nACOS ( number1 )\nGives the arc cosine of a number, in degrees.\nASIN ( number1 )\nGives the arc sine of a number, in degrees.\nATAN ( number1 )\nGives the arc tangent of a number, in degrees.\nATANT ( number1, number2 )\nGives the arc tangent of number1/number2, in degrees, with the appropriate sign.\nALOG ( number1 )\nGives the exponential function (natural anti-log) of a number.\nARRAY(pos or dir or ori)\nConverts a position, direction or orientation value or attribute into three numbers.\nARRAYSIZE ( variable-name )\nGives the size of an array variable.\nARRAYWIDTH( variable-name )\nGives the largest display width of any string in array variable-name.\nCOMPONENT dir OF pos2\nGives the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nINT ( number1 )\nGives the truncated integer value of a number.\nSIN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in degrees).\nCOS ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in degrees).\nTAN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in degrees).\nLENGTH ( text1 )\nGives the length of text1.\nLOG ( number1 )\nGives the natural logarithm of a number.\nMATCH ( text1, text2 )\nGives the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nMAX ( number1, number2[ , number3 [. . .]]) )\nGives the maximum value of the arguments.\nMIN ( number1, number2[ , number3 [. . .]]) )\nGives the minimum value of the arguments.\nNEGATE\nMultiply a number by -1.0.\nNINT ( number1 )\nGives the nearest integer to a real.\nNINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nOCCUR ( text1, text2 )\nGives the number of times string text2 occurs in string text1.\nREAL ( text1 )\nTry to read a number at the beginning of text1.\nPOWER ( number1, number2 )\nGives the value of number1 raised to the power number2.\nSQRT ( number1 )\nGives the square root of a number.\nVVALUE ( variable-name )\nUsed for late evaluation of variables. Gives a real value.\nABS\nSynopsis\nABS ( number1 )\n-> number\nDescription\nReturns the absolute value of a real.\nSide Effects\nNone.\nExample\nABS ( -3.2 ) -> 3.2\nErrors\nNone.\nSynopsis\nABS ( number1 )\n-> number\nDescription\nReturns the absolute value of a real.\nSide Effects\nNone.\nExample\nABS ( -3.2 ) -> 3.2\nErrors\nNone.\nACOS, ASIN, ATAN and ATANT\nSynopsis\nASIN ( number1 )\n-> number\nACOS ( number1 )\n-> number\nATAN ( number1 )\n-> number\nATANT ( number1, number2 )\n-> number\nDescription\nReturn the arc-cosine, arc-sine or arc-tangent of a number, in degrees.\nATANT returns the arc-tangent of number1/number2 with the appropriate sign. ATANT is useful where the second value is near or equal to zero.\nFor example, (6 0 ATANT) will give the correct result of 90 degrees, but (6 0 D ATAN) will indicate an error when trying to divide by zero.\nSide Effects\nNone.\nExample\nACOS ( 0.8660254 ) -> 30\nErrors\nArgument of ACOS or ASIN out of range [-1.0,+1.0]\nATANT (0.0,0.0) is undefined.\nSynopsis\nASIN ( number1 )\n-> number\n\nACOS ( number1 )\n-> number\n\nATAN ( number1 )\n-> number\n\nATANT ( number1, number2 )\n-> number\nDescription\nReturn the arc-cosine, arc-sine or arc-tangent of a number, in degrees.\nATANT returns the arc-tangent of number1/number2 with the appropriate sign. ATANT is useful where the second value is near or equal to zero.\nFor example, (6 0 ATANT) will give the correct result of 90 degrees, but (6 0 D ATAN) will indicate an error when trying to divide by zero.\nSide Effects\nNone.\nExample\nACOS ( 0.8660254 ) -> 30\nErrors\nArgument of ACOS or ASIN out of range [-1.0,+1.0]\nATANT (0.0,0.0) is undefined.\nALOG\nSynopsis\nALOG ( number1 )\n-> number\nDescription\nReturn the exponential function (natural anti-log) of a number.\nSide Effects\nNumeric underflow causes the result to be set to zero.\nExample\nALOG( -0.7 ) -> 0.4965853\nErrors\nFloating point overflow.\nSynopsis\nALOG ( number1 )\n-> number\nDescription\nReturn the exponential function (natural anti-log) of a number.\nSide Effects\nNumeric underflow causes the result to be set to zero.\nExample\nALOG( -0.7 ) -> 0.4965853\nErrors\nFloating point overflow.\nARRAY\nSynopsis\nARRAY(pos or dir or ori)\n-> number\nDescription\nConverts a position, direction or orientation value or attribute into three numbers.\nSide Effects\nNone\nExample\nARRAY(e100 ) -> 100 0 0\nErrors\nNone.\nSynopsis\nARRAY(pos or dir or ori)\n-> number\nDescription\nConverts a position, direction or orientation value or attribute into three numbers.\nSide Effects\nNone\nExample\nARRAY(e100 ) -> 100 0 0\nErrors\nNone.\nARRAYSIZE\nSynopsis\nARRAYSize ( variable-name )\n-> number\nDescription\nGive the size of an array variable.\nSide Effects\nIf the array variable does not exist, the result is undefined.\nExample\nARRAYSIZE(!array) -> 2.0\nErrors\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nSynopsis\nARRAYSize ( variable-name )\n-> number\nDescription\nGive the size of an array variable.\nSide Effects\nIf the array variable does not exist, the result is undefined.\nExample\nARRAYSIZE(!array) -> 2.0\nErrors\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nARRAYWIDTH\nSynopsis\nARRAYWIDTH ( variable-name )\n-> number\nDescription\nGive the largest display with of any string in array variable_name.\nSide Effects\nNone.\nExample\nIf an array contains the following values:\n!ARRAY[1] \u2019Bread\u2019\n!ARRAY[2] \u2019is\u2019\n!ARRAY[3] \u2019for\u2019\n!ARRAY[4] \u2019life,\u2019\n!ARRAY[5] \u2019not\u2019\n!ARRAY[6] \u2019just\u2019\n!ARRAY[7] \u2019for\u2019\n!ARRAY[8] \u2019breakfast\u2019\nThen\nARRAYWIDTH(!ARRAY -> 9\nas in, the length of \u2019breakfast\u2019.\nErrors\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nSynopsis\nARRAYWIDTH ( variable-name )\n-> number\nDescription\nGive the largest display with of any string in array variable_name.\nSide Effects\nNone.\nExample\nIf an array contains the following values:\n!ARRAY[1] \u2019Bread\u2019\n!ARRAY[2] \u2019is\u2019\n!ARRAY[3] \u2019for\u2019\n!ARRAY[4] \u2019life,\u2019\n!ARRAY[5] \u2019not\u2019\n!ARRAY[6] \u2019just\u2019\n!ARRAY[7] \u2019for\u2019\n!ARRAY[8] \u2019breakfast\u2019\n\nThen\nARRAYWIDTH(!ARRAY -> 9\nas in, the length of \u2019breakfast\u2019.\n\nErrors\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nCOMPONENT ... OF ...\nSynopsis\nCOMPonent dir1 OF pos2\n-> text\nDescription\nReturns the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nSide Effects\nNone.\nExample\nCOMP E 45 N of N 0 E 100 U 50 -> 70.710\nErrors\nNone.\nSynopsis\nCOMPonent dir1 OF pos2\n-> text\nDescription\nReturns the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nSide Effects\nNone.\nExample\nCOMP E 45 N of N 0 E 100 U 50 -> 70.710\nErrors\nNone.\nSINE, COSINE and TANGENT\nSynopsis\nSINe ( number1 )\n-> number\nCOSine ( number1 )\n-> number\nTANgent ( number1 )\n-> number\nDescription\nReturn the sine, cosine or tangent value of a number (considered to be in degrees).\nSide Effects\nNone.\nExample\nCOS ( 0.0 ) -> 1.0\nTAN ( 45.0 ) -> 1.0\nErrors\nDivision by zero for TAN if the SINe is (nearly) equal to zero.\nSynopsis\nSINe ( number1 )\n-> number\nCOSine ( number1 )\n-> number\nTANgent ( number1 )\n-> number\nDescription\nReturn the sine, cosine or tangent value of a number (considered to be in degrees).\nSide Effects\nNone.\nExample\nCOS ( 0.0 ) -> 1.0\nTAN ( 45.0 ) -> 1.0\nErrors\nDivision by zero for TAN if the SINe is (nearly) equal to zero.\nINT\nSynopsis\nINT ( number1 )\n-> number\nDescription\nReturn the truncated integer value of a number.\nSide Effects\nNone.\nExample\nINT ( 1.6 ) -> 1.0\nINT ( -23.7 ) -> -23.0\nErrors\nInteger overflow.\nSynopsis\nINT ( number1 )\n-> number\nDescription\nReturn the truncated integer value of a number.\nSide Effects\nNone.\nExample\nINT ( 1.6 ) -> 1.0\nINT ( -23.7 ) -> -23.0\nErrors\nInteger overflow.\nLENGTH\nSynopsis\nLENgth ( text1 )\n-> number\nDescription\nReturn the length of text1.\nSide Effects\nNone.\nExample\nLENGTH ( \u2019abcdef\u2019 ) -> 6.0\nLENGTH ( \u2019\u2019 ) -> 0.0\nErrors\nNone.\nSynopsis\nLENgth ( text1 )\n-> number\nDescription\nReturn the length of text1.\nSide Effects\nNone.\nExample\nLENGTH ( \u2019abcdef\u2019 ) -> 6.0\nLENGTH ( \u2019\u2019 ) -> 0.0\nErrors\nNone.\nALOG\nSynopsis\nLOG ( number1 )\n-> number\nDescription\nReturn the natural logarithm of a number.\nSide Effects\nNone.\nExample\nLOG( 3 ) -> 1 0986123\nErrors\nNegative arguments.\nSynopsis\nLOG ( number1 )\n-> number\nDescription\nReturn the natural logarithm of a number.\nSide Effects\nNone.\nExample\nLOG( 3 ) -> 1 0986123\nErrors\nNegative arguments.\nMATCH\nSynopsis\nMATch ( text1 , text2)\n-> number\nDescription\nReturn the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nSide Effects\nNone.\nExample\nMATCH ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> 3.0\nMATCH ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> 0.0\nMATCH ( \u2019abcdef\u2019 , \u2019\u2019 ) -> 1.0\nErrors\nNone.\nSynopsis\nMATch ( text1 , text2)\n-> number\nDescription\nReturn the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nSide Effects\nNone.\nExample\nMATCH ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> 3.0\nMATCH ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> 0.0\nMATCH ( \u2019abcdef\u2019 , \u2019\u2019 ) -> 1.0\nErrors\nNone.\nMAX and MIN\nSynopsis\nMAX ( number1 ,\nnumber2 [ , number3\n[ ... ] ] )\n-> number\nMIN ( number1 ,\nnumber2 [ , number3\n[ ... ] ] )\n-> number\nDescription\nReturn the maximum or minimum value of the arguments.\nSide Effects\nNone.\nExample\nMAX ( 1 , 3.4 ) -> 3.4\nMIN ( 7.6 , -12.33 , 2.3 ) -> -12.33\nErrors\nNone.\nSynopsis\nMAX ( number1 ,\nnumber2 [ , number3\n[ ... ] ] )\n-> number\n\nMIN ( number1 ,\nnumber2 [ , number3\n[ ... ] ] )\n-> number\nDescription\nReturn the maximum or minimum value of the arguments.\nSide Effects\nNone.\nExample\nMAX ( 1 , 3.4 ) -> 3.4\nMIN ( 7.6 , -12.33 , 2.3 ) -> -12.33\nErrors\nNone.\nNEGATE\nSynopsis\nNEGate ( number1 )\n-> number\nDescription\nMultiply a real by -1.0.\nSide Effects\nNone.\nExample\nNEG ( 1 ) -> -1.0\nErrors\nNone.\nSynopsis\nNEGate ( number1 )\n-> number\nDescription\nMultiply a real by -1.0.\nSide Effects\nNone.\nExample\nNEG ( 1 ) -> -1.0\nErrors\nNone.\nNINT\nSynopsis\nNINT ( number1 )\n-> number\nDescription\nReturn the nearest integer to a real.\nNINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nSide Effects\nNone.\nExample\nNINT ( 1.1 ) -> 1.0\nNINT ( -23.7 ) -> -24.0\nNINT ( 1.5 ) -> 2.0\nNINT ( -11.5 ) -> -12.0\nErrors\nInteger overflow.\nSynopsis\nNINT ( number1 )\n-> number\nDescription\nReturn the nearest integer to a real.\nNINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nSide Effects\nNone.\nExample\nNINT ( 1.1 ) -> 1.0\nNINT ( -23.7 ) -> -24.0\nNINT ( 1.5 ) -> 2.0\nNINT ( -11.5 ) -> -12.0\nErrors\nInteger overflow.\nOCCUR\nSynopsis\nOCCUR(text1, text2)\n-> integer\nDescription\nCounts the number of times string text2 occurs in string text1.\nSide Effects\nNone.\nExample\nOCCUR (\u2019ABBACCBBBBBAB\u2019, \u2019BB\u2019) -> 3\nOCCUR(\u2019ZZZZZZZZZZZ\u2019, \u2019A\u2019) -> 0\nErrors\nNone.\nSynopsis\nOCCUR(text1, text2)\n-> integer\nDescription\nCounts the number of times string text2 occurs in string text1.\nSide Effects\nNone.\nExample\nOCCUR (\u2019ABBACCBBBBBAB\u2019, \u2019BB\u2019) -> 3\nOCCUR(\u2019ZZZZZZZZZZZ\u2019, \u2019A\u2019) -> 0\nErrors\nNone.\nREAL\nSynopsis\nREAL ( text1 )\n-> number\nDescription\nTry to read a real number at the beginning of text1.\nNote that if text is in the form of an exponent, (-12E-1 in the third example), there must be no spaces in it.\nNote:\nThis function was formerly called NUMBER.\nSide Effects\nNumeric underflow causes the result to be set to zero.\nExample\nREAL ( \u201912.34\u2019) -> 12.34\nREAL ( \u2019 7.23 E 3 meters\u2019 ) -> 7.23\nREAL ( \u2019 -12E-1 meters \u2019 ) -> -1.2\nErrors\nUnable to convert the text into a real number.\nSynopsis\nREAL ( text1 )\n-> number\nDescription\nTry to read a real number at the beginning of text1.\nNote that if text is in the form of an exponent, (-12E-1 in the third example), there must be no spaces in it.\nSide Effects\nNumeric underflow causes the result to be set to zero.\nExample\nREAL ( \u201912.34\u2019) -> 12.34\nREAL ( \u2019 7.23 E 3 meters\u2019 ) -> 7.23\nREAL ( \u2019 -12E-1 meters \u2019 ) -> -1.2\nErrors\nUnable to convert the text into a real number.\nPOWER\nSynopsis\nPOWer ( number1 , number2 )\n-> real\nDescription\nReturn the value of number1 raised to the power number2.\nSide Effects\nUnits are consolidated across POWER. The dimension of the result of the function is determined from the input quantities.\nExample\nPOWER (2inch, 3) = 8cubic inch or 8in3\nErrors\nFloating point overflow.\nZero first argument and non-positive second argument (effectively divide by zero).\nNegative first argument and non-integer second argument.\nSynopsis\nPOWer ( number1 , number2 )\n-> real\nDescription\nReturn the value of number1 raised to the power number2.\nSide Effects\nUnits are consolidated across POWER. The dimension of the result of the function is determined from the input quantities.\nExample\nPOWER (2inch, 3) = 8cubic inch or 8in3\nErrors\nFloating point overflow.\nZero first argument and non-positive second argument (effectively divide by zero).\nNegative first argument and non-integer second argument.\nSQRT\nSynopsis\nSQrt ( number1 )\n-> number\nDescription\nReturn the square root of a real.\nSide Effects\nUnits are consolidated across SQRT. The dimension of the result of the function is determined from the input quantities.\nExample\nSQRT (16METRE2) = 4Metre\nErrors\nNegative argument.\nSynopsis\nSQrt ( number1 )\n-> number\nDescription\nReturn the square root of a real.\nSide Effects\nUnits are consolidated across SQRT. The dimension of the result of the function is determined from the input quantities.\nExample\nSQRT (16METRE2) = 4Metre\nErrors\nNegative argument.\nVVALUE\nREAL(string) and VVAL(!stringvar) functions:\nThese will return the value of the number in the string IGNORING any unit qualifier.\nThe unit qualifier must still be a valid unit qualifier. This is done so that output from '$!' and 'VAR !' combinations of commands can still be accepted by the REAL function and other functions with or without unit qualifiers appended\nVVALUE is used for the late evaluation of variables.\nSynopsis\nVVALue( variable_name )\n-> number\nVVALue( variable_name , number )\n-> number\nDescription\nWith one argument, returns value of the scalar variable or value of the array variable element as a number.\nWith two arguments, returns value of the element corresponding to the index number as a number.\nSee also VLOGICAL, used for late evaluation when a logical result is required, and VTEXT, used for late evaluation when a text result is required.\nSide Effects\nIf the scalar variable, the array variable or the array variable element does not exist, the result is undefined.\nExample\nVVAL ( !array[1] ) -> 1.0\nVVAL ( !array , 2 ) -> 0.0\nErrors\nScalar variable may not be indexed. For example, VTEXT (!var[1]) ) will return an error.\nArray variable must have an index. For example, VTEXT ( !array ) ) will return an error.\nThe string can not be converted to a number.\nSynopsis\nVVALue( variable_name )\n-> number\nVVALue( variable_name , number )\n-> number\nDescription\nWith one argument, returns value of the scalar variable or value of the array variable element as a number.\nWith two arguments, returns value of the element corresponding to the index number as a number.\nSee also VLOGICAL, used for late evaluation when a logical result is required, and VTEXT, used for late evaluation when a text result is required.\nSide Effects\nIf the scalar variable, the array variable or the array variable element does not exist, the result is undefined.\nExample\nVVAL ( !array[1] ) -> 1.0\nVVAL ( !array , 2 ) -> 0.0\nErrors\nScalar variable may not be indexed. For example, VTEXT (!var[1]) ) will return an error.\nArray variable must have an index. For example, VTEXT ( !array ) ) will return an error.\nThe string can not be converted to a number.\n\nFunction\nComments\nABS ( number1 )\nGives the absolute value of a number\nACOS ( number1 )\nGives the arc cosine of a number, in degrees.\nASIN ( number1 )\nGives the arc sine of a number, in degrees.\nATAN ( number1 )\nGives the arc tangent of a number, in degrees.\nATANT ( number1, number2 )\nGives the arc tangent of number1/number2, in degrees, with the appropriate sign.\nALOG ( number1 )\nGives the exponential function (natural anti-log) of a number.\nARRAY(pos or dir or ori)\nConverts a position, direction or orientation value or attribute into three numbers.\nARRAYSIZE ( variable-name )\nGives the size of an array variable.\nARRAYWIDTH( variable-name )\nGives the largest display width of any string in array variable-name.\nCOMPONENT dir OF pos2\nGives the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nINT ( number1 )\nGives the truncated integer value of a number.\nSIN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in degrees).\nCOS ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in degrees).\nTAN ( number1 )\nGives the sine, cosine or tangent value of a number (considered to be in degrees).\nLENGTH ( text1 )\nGives the length of text1.\nLOG ( number1 )\nGives the natural logarithm of a number.\nMATCH ( text1, text2 )\nGives the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nMAX ( number1, number2[ , number3 [. . .]]) )\nGives the maximum value of the arguments.\nMIN ( number1, number2[ , number3 [. . .]]) )\nGives the minimum value of the arguments.\nNEGATE\nMultiply a number by -1.0.\nNINT ( number1 )\nGives the nearest integer to a real.\nNINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nOCCUR ( text1, text2 )\nGives the number of times string text2 occurs in string text1.\nREAL ( text1 )\nTry to read a number at the beginning of text1.\nPOWER ( number1, number2 )\nGives the value of number1 raised to the power number2.\nSQRT ( number1 )\nGives the square root of a number.\nVVALUE ( variable-name )\nUsed for late evaluation of variables. Gives a real value.\nSynopsis\nABS ( number1 )\n-> number\nDescription\nReturns the absolute value of a real.\nSide Effects\nNone.\nExample\nABS ( -3.2 ) -> 3.2\nErrors\nNone.\nSynopsis\nASIN ( number1 )\n-> number\nACOS ( number1 )\n-> number\nATAN ( number1 )\n-> number\nATANT ( number1, number2 )\n-> number\nDescription\nReturn the arc-cosine, arc-sine or arc-tangent of a number, in degrees.\nATANT returns the arc-tangent of number1/number2 with the appropriate sign. ATANT is useful where the second value is near or equal to zero.\nFor example, (6 0 ATANT) will give the correct result of 90 degrees, but (6 0 D ATAN) will indicate an error when trying to divide by zero.\nSide Effects\nNone.\nExample\nACOS ( 0.8660254 ) -> 30\nErrors\nArgument of ACOS or ASIN out of range [-1.0,+1.0]\nATANT (0.0,0.0) is undefined.\nSynopsis\nALOG ( number1 )\n-> number\nDescription\nReturn the exponential function (natural anti-log) of a number.\nSide Effects\nNumeric underflow causes the result to be set to zero.\nExample\nALOG( -0.7 ) -> 0.4965853\nErrors\nFloating point overflow.\nSynopsis\nARRAY(pos or dir or ori)\n-> number\nDescription\nConverts a position, direction or orientation value or attribute into three numbers.\nSide Effects\nNone\nExample\nARRAY(e100 ) -> 100 0 0\nErrors\nNone.\nSynopsis\nARRAYSize ( variable-name )\n-> number\nDescription\nGive the size of an array variable.\nSide Effects\nIf the array variable does not exist, the result is undefined.\nExample\nARRAYSIZE(!array) -> 2.0\nErrors\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nSynopsis\nARRAYWIDTH ( variable-name )\n-> number\nDescription\nGive the largest display with of any string in array variable_name.\nSide Effects\nNone.\nExample\nIf an array contains the following values:\n!ARRAY[1] \u2019Bread\u2019\n!ARRAY[2] \u2019is\u2019\n!ARRAY[3] \u2019for\u2019\n!ARRAY[4] \u2019life,\u2019\n!ARRAY[5] \u2019not\u2019\n!ARRAY[6] \u2019just\u2019\n!ARRAY[7] \u2019for\u2019\n!ARRAY[8] \u2019breakfast\u2019\nThen\nARRAYWIDTH(!ARRAY -> 9\nas in, the length of \u2019breakfast\u2019.\nErrors\nThe variable is a scalar variable and not an array variable.\nThe variable is an array variable element and not an array variable.\nSynopsis\nCOMPonent dir1 OF pos2\n-> text\nDescription\nReturns the magnitude of a vector drawn from E0 N0 U0 to pos2, projected in the direction dir1.\nSide Effects\nNone.\nExample\nCOMP E 45 N of N 0 E 100 U 50 -> 70.710\nErrors\nNone.\nSynopsis\nSINe ( number1 )\n-> number\nCOSine ( number1 )\n-> number\nTANgent ( number1 )\n-> number\nDescription\nReturn the sine, cosine or tangent value of a number (considered to be in degrees).\nSide Effects\nNone.\nExample\nCOS ( 0.0 ) -> 1.0\nTAN ( 45.0 ) -> 1.0\nErrors\nDivision by zero for TAN if the SINe is (nearly) equal to zero.\nSynopsis\nINT ( number1 )\n-> number\nDescription\nReturn the truncated integer value of a number.\nSide Effects\nNone.\nExample\nINT ( 1.6 ) -> 1.0\nINT ( -23.7 ) -> -23.0\nErrors\nInteger overflow.\nSynopsis\nLENgth ( text1 )\n-> number\nDescription\nReturn the length of text1.\nSide Effects\nNone.\nExample\nLENGTH ( \u2019abcdef\u2019 ) -> 6.0\nLENGTH ( \u2019\u2019 ) -> 0.0\nErrors\nNone.\nSynopsis\nLOG ( number1 )\n-> number\nDescription\nReturn the natural logarithm of a number.\nSide Effects\nNone.\nExample\nLOG( 3 ) -> 1 0986123\nErrors\nNegative arguments.\nSynopsis\nMATch ( text1 , text2)\n-> number\nDescription\nReturn the position of the beginning of the leftmost occurrence of text2 in text1. If text2 does not occur in text1, 0 is returned.\nSide Effects\nNone.\nExample\nMATCH ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> 3.0\nMATCH ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> 0.0\nMATCH ( \u2019abcdef\u2019 , \u2019\u2019 ) -> 1.0\nErrors\nNone.\nSynopsis\nMAX ( number1 ,\nnumber2 [ , number3\n[ ... ] ] )\n-> number\nMIN ( number1 ,\nnumber2 [ , number3\n[ ... ] ] )\n-> number\nDescription\nReturn the maximum or minimum value of the arguments.\nSide Effects\nNone.\nExample\nMAX ( 1 , 3.4 ) -> 3.4\nMIN ( 7.6 , -12.33 , 2.3 ) -> -12.33\nErrors\nNone.\nSynopsis\nNEGate ( number1 )\n-> number\nDescription\nMultiply a real by -1.0.\nSide Effects\nNone.\nExample\nNEG ( 1 ) -> -1.0\nErrors\nNone.\nSynopsis\nNINT ( number1 )\n-> number\nDescription\nReturn the nearest integer to a real.\nNINT(N+0.5) is equal to N+1 if N is positive or equal to zero, to N if N is negative.\nSide Effects\nNone.\nExample\nNINT ( 1.1 ) -> 1.0\nNINT ( -23.7 ) -> -24.0\nNINT ( 1.5 ) -> 2.0\nNINT ( -11.5 ) -> -12.0\nErrors\nInteger overflow.\nSynopsis\nOCCUR(text1, text2)\n-> integer\nDescription\nCounts the number of times string text2 occurs in string text1.\nSide Effects\nNone.\nExample\nOCCUR (\u2019ABBACCBBBBBAB\u2019, \u2019BB\u2019) -> 3\nOCCUR(\u2019ZZZZZZZZZZZ\u2019, \u2019A\u2019) -> 0\nErrors\nNone.\nSynopsis\nREAL ( text1 )\n-> number\nDescription\nTry to read a real number at the beginning of text1.\nNote that if text is in the form of an exponent, (-12E-1 in the third example), there must be no spaces in it.\nNote:\nThis function was formerly called NUMBER.\nSide Effects\nNumeric underflow causes the result to be set to zero.\nExample\nREAL ( \u201912.34\u2019) -> 12.34\nREAL ( \u2019 7.23 E 3 meters\u2019 ) -> 7.23\nREAL ( \u2019 -12E-1 meters \u2019 ) -> -1.2\nErrors\nUnable to convert the text into a real number.\nSynopsis\nPOWer ( number1 , number2 )\n-> real\nDescription\nReturn the value of number1 raised to the power number2.\nSide Effects\nUnits are consolidated across POWER. The dimension of the result of the function is determined from the input quantities.\nExample\nPOWER (2inch, 3) = 8cubic inch or 8in3\nErrors\nFloating point overflow.\nZero first argument and non-positive second argument (effectively divide by zero).\nNegative first argument and non-integer second argument.\nSynopsis\nSQrt ( number1 )\n-> number\nDescription\nReturn the square root of a real.\nSide Effects\nUnits are consolidated across SQRT. The dimension of the result of the function is determined from the input quantities.\nExample\nSQRT (16METRE2) = 4Metre\nErrors\nNegative argument.\nSynopsis\nVVALue( variable_name )\n-> number\nVVALue( variable_name , number )\n-> number\nDescription\nWith one argument, returns value of the scalar variable or value of the array variable element as a number.\nWith two arguments, returns value of the element corresponding to the index number as a number.\nSee also VLOGICAL, used for late evaluation when a logical result is required, and VTEXT, used for late evaluation when a text result is required.\nSide Effects\nIf the scalar variable, the array variable or the array variable element does not exist, the result is undefined.\nExample\nVVAL ( !array[1] ) -> 1.0\nVVAL ( !array , 2 ) -> 0.0\nErrors\nScalar variable may not be indexed. For example, VTEXT (!var[1]) ) will return an error.\nArray variable must have an index. For example, VTEXT ( !array ) ) will return an error.\nThe string can not be converted to a number.\nNote:\nThis function was formerly called NUMBER.\n\n\n\nFunction\nComments\nABS ( number1 )\nACOS ( number1 )\nASIN ( number1 )\nATAN ( number1 )\nATANT ( number1, number2 )\nnumber1/number2\nALOG ( number1 )\nARRAY(pos or dir or ori)\nARRAYSIZE ( variable-name )\nARRAYWIDTH( variable-name )\nCOMPONENT dir OF pos2\npos2\ndir1\nINT ( number1 )\nSIN ( number1 )\nCOS ( number1 )\nTAN ( number1 )\nLENGTH ( text1 )\ntext1\nLOG ( number1 )\nMATCH ( text1, text2 )\ntext2\ntext1\ntext2\ntext1\nMAX ( number1, number2[ , number3 [. . .]]) )\nMIN ( number1, number2[ , number3 [. . .]]) )\nNEGATE\nNINT ( number1 )\nOCCUR ( text1, text2 )\ntext2\ntext1\nREAL ( text1 )\ntext1\nPOWER ( number1, number2 )\nnumber1\nnumber2\nSQRT ( number1 )\nVVALUE ( variable-name )\nABS\nSynopsis\nABS ( number1 )\n-> number\nDescription\nSide Effects\nExample\nABS ( -3.2 ) -> 3.2\nErrors\nACOS, ASIN, ATAN and ATANT\nSynopsis\nASIN ( number1 )\n-> number\nACOS ( number1 )\n-> number\nATAN ( number1 )\n-> number\nATANT ( number1, number2 )\n-> number\nDescription\nATANT\nnumber1/number2\nATANT\n(6 0 ATANT)\n(6 0 D ATAN)\nSide Effects\nExample\nACOS ( 0.8660254 ) -> 30\nErrors\nACOS\nASIN\n[-1.0,+1.0]\nATANT (0.0,0.0)\nALOG\nSynopsis\nALOG ( number1 )\n-> number\nDescription\nSide Effects\nExample\nALOG( -0.7 ) -> 0.4965853\nErrors\nARRAY\nSynopsis\nARRAY(pos or dir or ori)\n-> number\nDescription\nSide Effects\nExample\nARRAY(e100 ) -> 100 0 0\nErrors\nARRAYSIZE\nSynopsis\nARRAYSize ( variable-name )\n-> number\nDescription\nSide Effects\nExample\nARRAYSIZE(!array) -> 2.0\nErrors\nARRAYWIDTH\nSynopsis\nARRAYWIDTH ( variable-name )\n-> number\nDescription\nvariable_name\nSide Effects\nExample\n!ARRAY[1] \u2019Bread\u2019\n!ARRAY[2] \u2019is\u2019\n!ARRAY[3] \u2019for\u2019\n!ARRAY[4] \u2019life,\u2019\n!ARRAY[5] \u2019not\u2019\n!ARRAY[6] \u2019just\u2019\n!ARRAY[7] \u2019for\u2019\n!ARRAY[8] \u2019breakfast\u2019\nARRAYWIDTH(!ARRAY -> 9\n\u2019breakfast\u2019\nErrors\nCOMPONENT ... OF ...\nSynopsis\nCOMPonent dir1 OF pos2\n-> text\nDescription\npos2\ndir1\nSide Effects\nExample\nCOMP E 45 N of N 0 E 100 U 50 -> 70.710\nErrors\nSINE, COSINE and TANGENT\nSynopsis\nSINe ( number1 )\n-> number\nCOSine ( number1 )\n-> number\nTANgent ( number1 )\n-> number\nDescription\nSide Effects\nExample\nCOS ( 0.0 ) -> 1.0\nTAN ( 45.0 ) -> 1.0\nErrors\nTAN\nSINe\nINT\nSynopsis\nINT ( number1 )\n-> number\nDescription\nSide Effects\nExample\nINT ( 1.6 ) -> 1.0\nINT ( -23.7 ) -> -23.0\nErrors\nLENGTH\nSynopsis\nLENgth ( text1 )\n-> number\nDescription\ntext1\nSide Effects\nExample\nLENGTH ( \u2019abcdef\u2019 ) -> 6.0\nLENGTH ( \u2019\u2019 ) -> 0.0\nErrors\nALOG\nSynopsis\nLOG ( number1 )\n-> number\nDescription\nSide Effects\nExample\nLOG( 3 ) -> 1 0986123\nErrors\nMATCH\nSynopsis\nMATch ( text1 , text2)\n-> number\nDescription\ntext2\ntext1\ntext2\ntext1\nSide Effects\nExample\nMATCH ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> 3.0\nMATCH ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> 0.0\nMATCH ( \u2019abcdef\u2019 , \u2019\u2019 ) -> 1.0\nErrors\nMAX and MIN\nSynopsis\nMAX ( number1 ,\nnumber2 [ , number3\n[ ... ] ] )\n-> number\nMIN ( number1 ,\nnumber2 [ , number3\n[ ... ] ] )\n-> number\nDescription\nSide Effects\nExample\nMAX ( 1 , 3.4 ) -> 3.4\nMIN ( 7.6 , -12.33 , 2.3 ) -> -12.33\nErrors\nNEGATE\nSynopsis\nNEGate ( number1 )\n-> number\nDescription\nSide Effects\nExample\nNEG ( 1 ) -> -1.0\nErrors\nNINT\nSynopsis\nNINT ( number1 )\n-> number\nDescription\nNINT(N+0.5)\nN+1\nN\nN\nN\nSide Effects\nExample\nNINT ( 1.1 ) -> 1.0\nNINT ( -23.7 ) -> -24.0\nNINT ( 1.5 ) -> 2.0\nNINT ( -11.5 ) -> -12.0\nErrors\nOCCUR\nSynopsis\nOCCUR(text1, text2)\n-> integer\nDescription\ntext2\ntext1\nSide Effects\nExample\nOCCUR (\u2019ABBACCBBBBBAB\u2019, \u2019BB\u2019) -> 3\nOCCUR(\u2019ZZZZZZZZZZZ\u2019, \u2019A\u2019) -> 0\nErrors\nREAL\nSynopsis\nREAL ( text1 )\n-> number\nDescription\ntext1\nNote\n:\nSide Effects\nExample\nREAL ( \u201912.34\u2019) -> 12.34\nREAL ( \u2019 7.23 E 3 meters\u2019 ) -> 7.23\nREAL ( \u2019 -12E-1 meters \u2019 ) -> -1.2\nErrors\nPOWER\nSynopsis\nPOWer ( number1 , number2 )\n-> real\nDescription\nnumber1\nnumber2\nSide Effects\nExample\nPOWER (2inch, 3) = 8cubic inch or 8in3\nErrors\nSQRT\nSynopsis\nSQrt ( number1 )\n-> number\nDescription\nSide Effects\nExample\nSQRT (16METRE2) = 4Metre\nErrors\nVVALUE\nREAL(string)\nVVAL(!stringvar)\n$!\nVAR !\nVVALUE\nSynopsis\nVVALue( variable_name )\n-> number\nVVALue( variable_name , number )\n-> number\nDescription\nVLOGICAL\nVTEXT\nSide Effects\nExample\nVVAL ( !array[1] ) -> 1.0\nVVAL ( !array , 2 ) -> 0.0\nErrors\nVTEXT (!var[1]) )\nVTEXT ( !array ) )"}
{"Headers": "Real Arrays", "Content": "Real array expressions can contain attributes of type real array, for example: DESP.\n\n\n\nDESP"}
{"Headers": "Using IDs in Expressions", "Content": "IDs can be used in expressions. IDs can be any of the following:\nSPEC OF SPREF OF FLAN 1 OF NEXT BRAN\nHEAD TUBE OF /BRAN1\nElement name, for example: /VESS1.\nRefno, for example: =23/456.\nElement type further up the hierarchy, for example: SITE.\nNumber within member list, for example: 3.\nType and number within member list, for example: BOX 3.\nNEXT, PREV for next, previous within current list. Optionally, with a count and/or element type, for example: NEXT 2 BOX, LAST CYL.\nNEXT, PREV MEMBER for next, previous within member list. Optionally with a count and/or element type.\nIf the element type given is only valid as a member then MEMBER is assumed. For example, NEXT BOX at an EQUIPMENT will assume MEMBER.\nFIRST, LAST for first and last in current list. Optionally, with a count and/or element type.\nFIRST, LAST MEMBER for first and last in member list. If the element type given is only valid as a member then MEMBER is assumed.\nEND to navigate up from current list.\nEND is similar to owner but not quite the same. For example, if the current element is a GROUP MEMBER, and it has been reached from the GROUP then END will return to the group but OWNE will go to the true owner.\nAttribute of type ref, for example: CREF.\nSAME to mean last current element.\nNULREF to mean =0/0.\nCE for the current element.\n'OF' may be used to nest the options indefinitely. For example:\nSPEC OF SPREF OF FLAN 1 OF NEXT BRAN\nThis denotes the SPEC element owing the SELE element pointed to by the SPREF attribute on the first FLANGE of the next BRANCH. ILEAVE TUBE, IARRIV TUBE, HEAD TUBE, TAIL TUBE can be added to denote tube. For example:\nHEAD TUBE OF /BRAN1\nAn error will occur if there is no implied tube for the element concerned.\nID arrays can also be used in expressions. For example, CRFA.\nElement name, for example: /VESS1.\nElement name, for example: /VESS1.\nRefno, for example: =23/456.\nRefno, for example: =23/456.\nElement type further up the hierarchy, for example: SITE.\nElement type further up the hierarchy, for example: SITE.\nNumber within member list, for example: 3.\nNumber within member list, for example: 3.\nType and number within member list, for example: BOX 3.\nType and number within member list, for example: BOX 3.\nNEXT, PREV for next, previous within current list. Optionally, with a count and/or element type, for example: NEXT 2 BOX, LAST CYL.\nNEXT, PREV for next, previous within current list. Optionally, with a count and/or element type, for example: NEXT 2 BOX, LAST CYL.\nNEXT, PREV MEMBER for next, previous within member list. Optionally with a count and/or element type.\nNEXT, PREV MEMBER for next, previous within member list. Optionally with a count and/or element type.\nIf the element type given is only valid as a member then MEMBER is assumed. For example, NEXT BOX at an EQUIPMENT will assume MEMBER.\nIf the element type given is only valid as a member then MEMBER is assumed. For example, NEXT BOX at an EQUIPMENT will assume MEMBER.\nFIRST, LAST for first and last in current list. Optionally, with a count and/or element type.\nFIRST, LAST for first and last in current list. Optionally, with a count and/or element type.\nFIRST, LAST MEMBER for first and last in member list. If the element type given is only valid as a member then MEMBER is assumed.\nFIRST, LAST MEMBER for first and last in member list. If the element type given is only valid as a member then MEMBER is assumed.\nEND to navigate up from current list.\nEND to navigate up from current list.\nEND is similar to owner but not quite the same. For example, if the current element is a GROUP MEMBER, and it has been reached from the GROUP then END will return to the group but OWNE will go to the true owner.\nEND is similar to owner but not quite the same. For example, if the current element is a GROUP MEMBER, and it has been reached from the GROUP then END will return to the group but OWNE will go to the true owner.\nAttribute of type ref, for example: CREF.\nAttribute of type ref, for example: CREF.\nSAME to mean last current element.\nSAME to mean last current element.\nNULREF to mean =0/0.\nNULREF to mean =0/0.\nCE for the current element.\nCE for the current element.\n'OF' may be used to nest the options indefinitely. For example:\nSPEC OF SPREF OF FLAN 1 OF NEXT BRAN\n'OF' may be used to nest the options indefinitely. For example:\nThis denotes the SPEC element owing the SELE element pointed to by the SPREF attribute on the first FLANGE of the next BRANCH. ILEAVE TUBE, IARRIV TUBE, HEAD TUBE, TAIL TUBE can be added to denote tube. For example:\nHEAD TUBE OF /BRAN1\nThis denotes the SPEC element owing the SELE element pointed to by the SPREF attribute on the first FLANGE of the next BRANCH. ILEAVE TUBE, IARRIV TUBE, HEAD TUBE, TAIL TUBE can be added to denote tube. For example:\nAn error will occur if there is no implied tube for the element concerned.\nID arrays can also be used in expressions. For example, CRFA.\nAn error will occur if there is no implied tube for the element concerned.\nNote:\nSome of the ID syntax clashes with other types. To allow for this, an id expression may always be preceded with the keyword ID. For example, ID 3 will mean the third member of the current list rather than a number of value 3.\n\n\n\n/VESS1\n=23/456\nSITE\n3\nBOX 3\nNEXT\nPREV\nNEXT 2 BOX\nLAST CYL\nNEXT\nPREV MEMBER\nMEMBER\nNEXT BOX\nEQUIPMENT\nMEMBER\nFIRST\nLAST\nFIRST\nLAST MEMBER\nMEMBER\nEND\nEND\nGROUP MEMBER\nGROUP\nEND\nOWNE\nCREF\nSAME\nNULREF\n=0/0\nCE\nOF\nSPEC OF SPREF OF FLAN 1 OF NEXT BRAN\nSPEC\nSELE\nSPREF\nFLANGE\nBRANCH\nILEAVE TUBE\nIARRIV TUBE\nHEAD TUBE\nTAIL TUBE\nCRFA\nNote\n:\nID 3"}
{"Headers": "Positions, Directions and Orientations in Expressions (AVEVA E3D Design only)", "Content": "Detailed information is provided for positions, directions and orientations in expressions.\n\n\n"}
{"Headers": "Using Positions in Expressions", "Content": "The basic ways of defining a position are:\nThe Cartesian position may optionally be followed by WRT to specify the axis system. Refer to WRT (AVEVA E3D Design Only) for further information.\nPOS OF /VESS1 WRT /* or P1 POS OF /CYL2\nN 45 W 20000 U 1000\nN 1000 FROM /ATEST.\nN 1000 FROM P1 OF /BOX2.\nN 1000 FROM POSS OF /SCTN1\nN (DESP[1] + 10) E\nPosition attribute plus optional WRT. For example:\nPOS OF /VESS1 WRT /* or P1 POS OF /CYL2\nCartesian position. For example:\nN 45 W 20000 U 1000\nCartesian position from an element. For example:\nN 1000 FROM /ATEST.\nCartesian position from a ppoint. For example:\nN 1000 FROM P1 OF /BOX2.\nCartesian position from an attribute. For example:\nN 1000 FROM POSS OF /SCTN1\nAny numeric value within a position may itself be an expression. For example (the following is a valid position expression):\nN (DESP[1] + 10) E\nPosition attribute plus optional WRT. For example:\nPOS OF /VESS1 WRT /* or P1 POS OF /CYL2\nPosition attribute plus optional WRT. For example:\nCartesian position. For example:\nN 45 W 20000 U 1000\nCartesian position. For example:\nCartesian position from an element. For example:\nN 1000 FROM /ATEST.\nCartesian position from an element. For example:\nCartesian position from a ppoint. For example:\nN 1000 FROM P1 OF /BOX2.\nCartesian position from a ppoint. For example:\nCartesian position from an attribute. For example:\nN 1000 FROM POSS OF /SCTN1\nCartesian position from an attribute. For example:\nAny numeric value within a position may itself be an expression. For example (the following is a valid position expression):\nN (DESP[1] + 10) E\nAny numeric value within a position may itself be an expression. For example (the following is a valid position expression):\n\n\n\nWRT (AVEVA E3D Design Only)\nWRT (AVEVA E3D Design Only)"}
{"Headers": "WRT (AVEVA E3D Design Only)", "Content": "The WRT keyword is used to toggle between absolute and relative units.\nWhen we specify an element (or attribute of an element) we are specifying an absolute point in world space. The point can be given in world space or some other axis. Normally the answer is required relative to the owner axis system and this is taken as the default.\nFor example:\nQ POS\n$ will return the position of the current element\n$ relatively to its owner.\nQ POS OF /EQUIP1\n$ will return the position of EQUIP1 relative to its\n$ owner.\nQ POS\n$ will return the position of the current element\n$ relatively to its owner.\nQ POS OF /EQUIP1\n$ will return the position of EQUIP1 relative to its\n$ owner.\nIf we require the result in some other axis system then the WRT keyword is used.\nFor example:\nQ POS WRT /*\n$ for the position in world coordinates.\nQ POS WRT /*\n$ for the position in world coordinates.\nWhen we specify a Cartesian coordinate we are dealing with a relative position.\nFor example, 'N 10' is meaningless until we specify the axis system, or default to an axis system.\nAgain we use WRT to do this, although it is important to note that in this case we are going from a relative position to an absolute position (in the previous example, WRT was used to go from an absolute position to a relative one).\nFor example:\nN 100 WRT /BOX1\n$ specifies an absolute position in world space\n$ which is N100 of /BOX1.\nN 100 WRT /BOX1\n$ specifies an absolute position in world space\n$ which is N100 of /BOX1.\nThe default is that Cartesian coordinates are in the owning element\u2019s axis system. This absolute position can be expressed in different coordinate systems: the default is again the owner\u2019s axis system.\nA SITE at (0,0,0)\nWith default (World) orientation.\nA ZONE at (100,0,0)\nWith default (World) orientation.\nAn EQUIPMENT at (100,0,0)\nWith orientation \u2019N IS E.\nA BOX at (-100,0,0)\nWith default (World) orientation.\n\nThe result of Q (N 100 WRT /BOX1), shown as \u00c4, will depend on the current element.\nWorld\n(300,100,0), in World coordinates.\nSite\n(300,100,0) in World coordinates because the World is the owner of the current element.\nZone\n(300,100,0) in World coordinates, because the Site is the owner of the current element, and the Site coordinates are the same as the World coordinates.\nEquipment\n(200,100,0), which is the position relative to its owner, the Zone.\nBox\n(100,100,0) which is the position relative to its owner, the Equipment.\nWRT can be further qualified by FROM.\nQ POS\n$ will return the position of the current element\n$ relatively to its owner.\nQ POS OF /EQUIP1\n$ will return the position of EQUIP1 relative to its\n$ owner.\nQ POS WRT /*\n$ for the position in world coordinates.\nN 100 WRT /BOX1\n$ specifies an absolute position in world space\n$ which is N100 of /BOX1.\nItem\nComments\nA SITE at (0,0,0)\nWith default (World) orientation.\nA ZONE at (100,0,0)\nWith default (World) orientation.\nAn EQUIPMENT at (100,0,0)\nWith orientation \u2019N IS E.\nA BOX at (-100,0,0)\nWith default (World) orientation.\nLocation\nResult\nWorld\n(300,100,0), in World coordinates.\nSite\n(300,100,0) in World coordinates because the World is the owner of the current element.\nZone\n(300,100,0) in World coordinates, because the Site is the owner of the current element, and the Site coordinates are the same as the World coordinates.\nEquipment\n(200,100,0), which is the position relative to its owner, the Zone.\nBox\n(100,100,0) which is the position relative to its owner, the Equipment.\nNote:\nThe CONSTRUCT syntax uses the world as the default axis.\n\n\n\nWRT\nQ POS\nQ POS OF /EQUIP1\nEQUIP1\nQ POS WRT /*\nN 10\nWRT\nN 100 WRT /BOX1\nN100\n/BOX1\nNote\n:\nCONSTRUCT\nItem\nComments\nQ (N 100 WRT /BOX1)\n\u00c4\nWRT\nFROM"}
{"Headers": "FROM", "Content": "In some cases we require an offset from a fixed point, other than the position of an item. For example, a point or attribute.\nThe FROM syntax is used for this. We may still use WRT in combination with FROM, but in this case the WRT is only used to determine the axis direction and not the offset, since the offset is specified by the FROM part.\nConsider the following:\nA SITE at (0,0,0)\nWith default (World) orientation.\nA ZONE at (100,0,0)\nWith default (World) orientation.\nAn EQUIPMENT at (100,0,0)\nWith orientation \u2019N IS E.\nA BOX at (-100,0,0)\nWith default (World) orientation.\n\nThe result of Q (N 100 WRT /* FROM /BOX1), shown as \u00c4, will depend on the current element.\nWorld, Site, and Zone\n(200,200,0) since the offset of N100 is applied in world axis rather than /BOX1 axis.\nEquipment\n(100,200,0).\nBox\n(200,0,0), because the default axis for the result is the Equipment.\nThe result of \u2019Q (N 100 WRT /BOX1 FROM /* ) is different:\nSite and Zone\n(100,0,0)\nEquipment\n(0,0,0)\nBox\n(0, -100, 0), because the axis for the result is the Equipment.\nThe result of \u2019Q (N 100 FROM /* )\u2019 is different again.\nFor this we cannot mark an absolute point on the diagram since the default WRT will vary with the current element. In fact, for the SITE, ZONE, EQUI the point \u00c4 is marked, and for the BOX the point coincides with the ZONE.\n\nSite and Zone\n(0,100,0)\nEquipment\n(-100,100,0), because the default result axis is the Zone.\nBox\n(0, -100, 0), because the axis for the result is the Equipment.\nItem\nComments\nA SITE at (0,0,0)\nWith default (World) orientation.\nA ZONE at (100,0,0)\nWith default (World) orientation.\nAn EQUIPMENT at (100,0,0)\nWith orientation \u2019N IS E.\nA BOX at (-100,0,0)\nWith default (World) orientation.\nLocation\nResult\nWorld, Site, and Zone\n(200,200,0) since the offset of N100 is applied in world axis rather than /BOX1 axis.\nEquipment\n(100,200,0).\nNote:\nThe default axis for the result is the Zone.\nBox\n(200,0,0), because the default axis for the result is the Equipment.\nLocation\nResult\nSite and Zone\n(100,0,0)\nEquipment\n(0,0,0)\nBox\n(0, -100, 0), because the axis for the result is the Equipment.\nLocation\nResult\nSite and Zone\n(0,100,0)\nEquipment\n(-100,100,0), because the default result axis is the Zone.\nBox\n(0, -100, 0), because the axis for the result is the Equipment.\nNote:\nThe default axis for the result is the Zone.\n\n\n\nFROM\nWRT\nFROM\nWRT\nFROM\nQ (N 100 WRT /* FROM /BOX1),\n\u00c4\n/BOX1\nNote\n:\n\u2019Q (N 100 WRT /BOX1 FROM /* )\n\u2019Q (N 100 FROM /* )\u2019\nWRT\n\u00c4"}
{"Headers": "Comparing Positions", "Content": "Two positions can be compared with EQ, NE, GT, LT, GE or LE. The pairs of coordinates are only compared in the coordinate axes for which the two positions are defined. A position attribute always has all three coordinates defined.\nFor positions entered by you, only those coordinates which are given by you are defined.\nFor example:\n\u2019N10U3\u2019\n$ only the Y and Z coordinates are defined,\n$ while the X coordinate remains undefined.\n\u2019N10U3\u2019\n$ only the Y and Z coordinates are defined,\n$ while the X coordinate remains undefined.\nFor the EQ operator, all the pairs of defined coordinates should be equal. For NE, only one pair of defined coordinates need be different. For GT (LT,GE,LE), all the defined coordinates of the first position should be greater than (less than, greater than or equal to, less than or equal to) the defined coordinates of the second position. This means that GE is not the opposite of LT and LE is not the opposite of GT.\nIf no coordinate of the two positions are defined for a common axis (for example, 'N10' and 'W4D7'), the result of the comparison is undefined.\nExamples:\n\u2019POS EQ W1S2D3\u2019\n$ This evaluates to true only if POS of the current $ element is (-1,-2,-3).\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\n$ Only the second coordinate of POS is compared;\n$ if it is greater than 10, then the result is true.\n\u2019E10N10 GT E0N0\u2019\n$ Is true because the inequality is verified for the X.\n$ and Y axis (both coordinates are undefined for\n$ the Z axis, so it is ignored).\n\u2019E10N0 GT E0N0\u2019\n$ Is false because the Y components are different $ axes.\n\u2019E10N0 GT E0U100\u2019\n$ Is true. Although no comparison can be\n$ performed n either the Y or the Z axis, because\n$ the components are not present in both position\n$ constants, the comparison is true in the X\n$ component.\n\u2019N10 EQ W4D7\u2019\n$ Is undefined (no comparison is possible).\n\u2019POS EQ W1S2D3\u2019\n$ This evaluates to true only if POS of the current $ element is (-1,-2,-3).\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\n$ Only the second coordinate of POS is compared;\n$ if it is greater than 10, then the result is true.\n\u2019E10N10 GT E0N0\u2019\n$ Is true because the inequality is verified for the X.\n$ and Y axis (both coordinates are undefined for\n$ the Z axis, so it is ignored).\n\u2019E10N0 GT E0N0\u2019\n$ Is false because the Y components are different $ axes.\n\u2019E10N0 GT E0U100\u2019\n$ Is true. Although no comparison can be\n$ performed n either the Y or the Z axis, because\n$ the components are not present in both position\n$ constants, the comparison is true in the X\n$ component.\n\u2019N10 EQ W4D7\u2019\n$ Is undefined (no comparison is possible).\nRefer to Precision of Comparisons for tolerances in comparing numbers.\n\u2019N10U3\u2019\n$ only the Y and Z coordinates are defined,\n$ while the X coordinate remains undefined.\n\u2019POS EQ W1S2D3\u2019\n$ This evaluates to true only if POS of the current $ element is (-1,-2,-3).\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\n$ Only the second coordinate of POS is compared;\n$ if it is greater than 10, then the result is true.\n\u2019E10N10 GT E0N0\u2019\n$ Is true because the inequality is verified for the X.\n$ and Y axis (both coordinates are undefined for\n$ the Z axis, so it is ignored).\n\u2019E10N0 GT E0N0\u2019\n$ Is false because the Y components are different $ axes.\n\u2019E10N0 GT E0U100\u2019\n$ Is true. Although no comparison can be\n$ performed n either the Y or the Z axis, because\n$ the components are not present in both position\n$ constants, the comparison is true in the X\n$ component.\n\u2019N10 EQ W4D7\u2019\n$ Is undefined (no comparison is possible).\n\n\n\nPrecision of Comparisons\n\u2019N10U3\u2019\n\u2019POS EQ W1S2D3\u2019\ntrue\nPOS\n(-1,-2,-3)\n\u2019POS GT N10\u2019 or \u2019N10 LE POS\u2019\ntrue\n\u2019E10N10 GT E0N0\u2019\ntrue\n\u2019E10N0 GT E0N0\u2019\nfalse\n\u2019E10N0 GT E0U100\u2019\ntrue\n\u2019N10 EQ W4D7\u2019\nPrecision of Comparisons"}
{"Headers": "POLAR", "Content": "The POLAR keyword allows positions to be defined in terms of a distance in a particular direction from a point.\nThe syntax is:\nIf FROM is not specified the default is the origin of the owner.\nFor example:\nPOLAR N 45 E DIST 20M FROM U 10 M\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V\nPOLAR N 45 E DIST 20M FROM U 10 M\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V\n\nPOLAR dir DISTance expr -+- FROM -+- pos -----.\n                  \n                         |        |           |\n                         |        \u2018- point ---|\n                  \n                         |                    |\n                         \u2018--------------------+--->\nPOLAR N 45 E DIST 20M FROM U 10 M\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V\nPOLAR dir DISTance expr -+- FROM -+- pos -----.\n                  \n                         |        |           |\n                         |        \u2018- point ---|\n                  \n                         |                    |\n                         \u2018--------------------+--->\nPOLAR dir DISTance expr -+- FROM -+- pos -----.\n                  \n                         |        |           |\n                         |        \u2018- point ---|\n                  \n                         |                    |\n                         \u2018--------------------+--->\n\n\n\nPOLAR\ndir\nexpr\npos\npoint\nFROM\nPOLAR N 45 E DIST 20M FROM U 10 M\nPOLAR AXES PL OF PREV DIST ( ABORE * 10 ) FROM PL OF PRE V"}
{"Headers": "Direction", "Content": "The basic ways of defining a direction are:\nIn the above graph, the keywords are:\n>- CLOSEST type -+- WITH exp -.\n                 |            |\n                 \u2018------------+- DIRECTION dir -+- EXTENT val -.\n                                                |              |\n                                                \u2018--------------+--> cont\n                                                    \n         continued >-+- AFTER val -.\n                     |             |\n                     \u2018-------------+- FROM ? -.\n                                   |          |\n                                   \u2018----------+-->\nCLOSEST DIR E\nCLOSEST BOX WITH ( PURP EQ \u2019FLOO\u2019 ) DIR D WRT /* EXTENT 20M\nCLOSEST VALVE DIR N 45 U FROM E100 N200 U300\nCLOSEST BRAN HANG AFTER 2M\nDirection attribute plus optional WRT. For example: HDIR OF /PIPE1 WRT /*.\nCartesian direction. For example: N 45 W.\nCartesian direction WRT to an element.\nAll Cartesian directions are returned in the axis of the owner of the current element. For example: (U WRT CE ). This will return the Z axis of the current element relative to its owner.\nQ ( Z WRT /SCTN ). This will return the Z axis direction of /SCTN relative to the owner of the current element. For example, if the result is required in world coordinates the current element must be the World or a Site.\nFROM pos2 TO pos2. For example: FROM N 50 WRT CE TO N 100.\nKeyword AXES followed by a ppoint or pline.\nThe CLOSEST keyword, which will find the closest element in a particular direction. The syntax is:\n>- CLOSEST type -+- WITH exp -.\n                 |            |\n                 \u2018------------+- DIRECTION dir -+- EXTENT val -.\n                                                |              |\n                                                \u2018--------------+--> cont\n                                                              continued >-+- AFTER val -.\n                     |             |\n                     \u2018-------------+- FROM ? -.\n                                   |          |\n                                   \u2018----------+-->\nDirection attribute plus optional WRT. For example: HDIR OF /PIPE1 WRT /*.\nDirection attribute plus optional WRT. For example: HDIR OF /PIPE1 WRT /*.\nCartesian direction. For example: N 45 W.\nCartesian direction. For example: N 45 W.\nCartesian direction WRT to an element.\nCartesian direction WRT to an element.\nAll Cartesian directions are returned in the axis of the owner of the current element. For example: (U WRT CE ). This will return the Z axis of the current element relative to its owner.\nAll Cartesian directions are returned in the axis of the owner of the current element. For example: (U WRT CE ). This will return the Z axis of the current element relative to its owner.\nQ ( Z WRT /SCTN ). This will return the Z axis direction of /SCTN relative to the owner of the current element. For example, if the result is required in world coordinates the current element must be the World or a Site.\nQ ( Z WRT /SCTN ). This will return the Z axis direction of /SCTN relative to the owner of the current element. For example, if the result is required in world coordinates the current element must be the World or a Site.\nFROM pos2 TO pos2. For example: FROM N 50 WRT CE TO N 100.\nFROM pos2 TO pos2. For example: FROM N 50 WRT CE TO N 100.\nKeyword AXES followed by a ppoint or pline.\nKeyword AXES followed by a ppoint or pline.\nThe CLOSEST keyword, which will find the closest element in a particular direction. The syntax is:\n>- CLOSEST type -+- WITH exp -.\n                 |            |\n                 \u2018------------+- DIRECTION dir -+- EXTENT val -.\n                                                |              |\n                                                \u2018--------------+--> cont\n                                                              continued >-+- AFTER val -.\n                     |             |\n                     \u2018-------------+- FROM ? -.\n                                   |          |\n                                   \u2018----------+-->\nThe CLOSEST keyword, which will find the closest element in a particular direction. The syntax is:\nEXTENT, which is how far to search in the direction specified, default 10M.\nAFTER, or the distance along vector after which to start search, default 0M.\nFROM, which specifies an alternative start point other than current element. This is of particular use for a branch where you might want to specify the HPOS or TPOS.\nExamples are:\nCLOSEST DIR E\nCLOSEST BOX WITH ( PURP EQ \u2019FLOO\u2019 ) DIR D WRT /* EXTENT 20M\nCLOSEST VALVE DIR N 45 U FROM E100 N200 U300\nCLOSEST BRAN HANG AFTER 2M\nEXTENT, which is how far to search in the direction specified, default 10M.\nEXTENT, which is how far to search in the direction specified, default 10M.\nAFTER, or the distance along vector after which to start search, default 0M.\nAFTER, or the distance along vector after which to start search, default 0M.\nFROM, which specifies an alternative start point other than current element. This is of particular use for a branch where you might want to specify the HPOS or TPOS.\nFROM, which specifies an alternative start point other than current element. This is of particular use for a branch where you might want to specify the HPOS or TPOS.\nExamples are:\nCLOSEST DIR E\nCLOSEST BOX WITH ( PURP EQ \u2019FLOO\u2019 ) DIR D WRT /* EXTENT 20M\nCLOSEST VALVE DIR N 45 U FROM E100 N200 U300\nCLOSEST BRAN HANG AFTER 2M\nExamples are:\n\n\n\nDirection\nWRT\nHDIR OF /PIPE1 WRT /*\nN 45 W\nWRT\n(U WRT CE )\nQ ( Z WRT /SCTN )\n/SCTN\nFROM N 50 WRT CE TO N 100\nAXES\nCLOSEST\nEXTENT\nAFTER\nFROM\nHPOS\nTPOS"}
{"Headers": "Orientations", "Content": "The basic ways of defining an orientation are:\n             .----<--------.\n            /              |\n>-- AXES --*--- PArrive ---|\n           |               |\n           |--- PLeave ----|\n           |               |\n           |--- PTail -----|\n           |               |\n           |--- HHead -----|\n           |               |\n           |--- HTail -----|\n           |               |\n           \u2018--- PPOINT n --+-- OF - <gid> ---->\n\n( AXES PLEAVE IS AXES PLEAVE OF PREV AND AXES P3 IS UP )\nOrientation attribute plus optional WRT. For example: ORI OF /BOX1 WRT /*.\nCartesian orientation. For example: dir IS dir AND dir IS dir.\nFor example to set an orientation of an element to that of a section, rotated by 90 degrees use: (E IS U WRT /SCTN1 AND N IS E WRT /SCTN1).\nThe AXES keyword, which will allow you to use ppoints to specify orientations.\nThe syntax is:\n             .----<--------.\n            /              |\n>-- AXES --*--- PArrive ---|\n           |               |\n           |--- PLeave ----|\n           |               |\n           |--- PTail -----|\n           |               |\n           |--- HHead -----|\n           |               |\n           |--- HTail -----|\n           |               |\n           \u2018--- PPOINT n --+-- OF - <gid> ---->\nAn example is:\n( AXES PLEAVE IS AXES PLEAVE OF PREV AND AXES P3 IS UP )\nThis will orient a branch component, such as a valve, so that it is aligned with the previous component and its P3 is up. Refer to Comparing Positions for further information.\nOrientation attribute plus optional WRT. For example: ORI OF /BOX1 WRT /*.\nOrientation attribute plus optional WRT. For example: ORI OF /BOX1 WRT /*.\nCartesian orientation. For example: dir IS dir AND dir IS dir.\nCartesian orientation. For example: dir IS dir AND dir IS dir.\nFor example to set an orientation of an element to that of a section, rotated by 90 degrees use: (E IS U WRT /SCTN1 AND N IS E WRT /SCTN1).\nFor example to set an orientation of an element to that of a section, rotated by 90 degrees use: (E IS U WRT /SCTN1 AND N IS E WRT /SCTN1).\nThe AXES keyword, which will allow you to use ppoints to specify orientations.\nThe AXES keyword, which will allow you to use ppoints to specify orientations.\nThe syntax is:\n             .----<--------.\n            /              |\n>-- AXES --*--- PArrive ---|\n           |               |\n           |--- PLeave ----|\n           |               |\n           |--- PTail -----|\n           |               |\n           |--- HHead -----|\n           |               |\n           |--- HTail -----|\n           |               |\n           \u2018--- PPOINT n --+-- OF - <gid> ---->\nThe syntax is:\nAn example is:\n( AXES PLEAVE IS AXES PLEAVE OF PREV AND AXES P3 IS UP )\nAn example is:\nThis will orient a branch component, such as a valve, so that it is aligned with the previous component and its P3 is up. Refer to Comparing Positions for further information.\nThis will orient a branch component, such as a valve, so that it is aligned with the previous component and its P3 is up. Refer to Comparing Positions for further information.\n\n\n\nComparing Positions\nOrientation\nWRT\nORI OF /BOX1 WRT /*\ndir IS dir AND dir IS dir\n(E IS U WRT /SCTN1 AND N IS E WRT /SCTN1)\nAXES\nComparing Positions"}
{"Headers": "Text Expressions", "Content": "Text expressions can contain the following:\nA text string, which must be enclosed in quotes. For example: 'FRED'.\nAn AVEVA E3D Design attribute of type text or word. For example: FUNC.\nA single element of a word array attribute. For example: ELEL[2].\nText operators.\nText functions.\nA text string, which must be enclosed in quotes. For example: 'FRED'.\nA text string, which must be enclosed in quotes. For example: 'FRED'.\nAn AVEVA E3D Design attribute of type text or word. For example: FUNC.\nAn AVEVA E3D Design attribute of type text or word. For example: FUNC.\nA single element of a word array attribute. For example: ELEL[2].\nA single element of a word array attribute. For example: ELEL[2].\nText operators.\nText operators.\nText functions.\nText functions.\n\n\n\n'FRED'\nFUNC\nELEL[2]"}
{"Headers": "Text Operator", "Content": "The text operator available is +, used for concatenation.\nSynopsis\ntext1 + text2 -> text\n-> text\nDescription\nReturn the concatenation of two text strings.\nSide Effects\nNone.\nExample\n'no' + 'space' -> 'nospace'\nErrors\nText result too long.\nSynopsis\ntext1 + text2 -> text\n-> text\nDescription\nReturn the concatenation of two text strings.\nSide Effects\nNone.\nExample\n'no' + 'space' -> 'nospace'\nErrors\nText result too long.\n\nSynopsis\ntext1 + text2 -> text\n-> text\nDescription\nReturn the concatenation of two text strings.\nSide Effects\nNone.\nExample\n'no' + 'space' -> 'nospace'\nErrors\nText result too long.\n\n\n\n+\nSynopsis\ntext1 + text2 -> text\n-> text\nDescription\nSide Effects\nExample\n'no' + 'space' -> 'nospace'\nErrors"}
{"Headers": "Text Functions", "Content": "The text functions available are:\nAFTER\n\nBEFORE\n\nDISTANCE\n\nLOWCASE, UPCASE\n\nPART\n\nREPLACE\n\nSTRING\n\nSUBS, DSUBS\n\nTRIM\n\nVTEXT\n\nAFTER\nSynopsis\nAFTER ( text1 , text2 )\n-> text\nDescription\nReturn the substring of text1 which is after the leftmost occurrence of text2 in text1.\nIf text2 does not occur in text1, the null string is returned.\nSide Effects\nNone.\nExample\nAFTER ( \u2019abcdef\u2019 , \u2019cd\u2019 ) ->\u2019ef\u2019\nAFTER ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> \u2019\u2019\nAFTER ( \u2019abcdef\u2019 , \u2019\u2019 ) -> \u2019abcdef\u2019\nErrors\nNone.\nSynopsis\nAFTER ( text1 , text2 )\n-> text\nDescription\nReturn the substring of text1 which is after the leftmost occurrence of text2 in text1.\nIf text2 does not occur in text1, the null string is returned.\nSide Effects\nNone.\nExample\nAFTER ( \u2019abcdef\u2019 , \u2019cd\u2019 ) ->\u2019ef\u2019\nAFTER ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> \u2019\u2019\nAFTER ( \u2019abcdef\u2019 , \u2019\u2019 ) -> \u2019abcdef\u2019\nErrors\nNone.\nBEFORE\nSynopsis\nBEFORE ( text1 , text2 )\n-> text\nDescription\nReturn the substring of text1 which is before the leftmost occurrence of text2 in text1. If text2 does not occur in text1, text1 is returned.\nSide Effects\nNone.\nExample\nBEFORE ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> \u2019ab\u2019\nBEFORE ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> \u2019\u2019\nBEFORE ( \u2019abcdef\u2019 , \u2019\u2019 ) -> \u2018\u2019\nErrors\nNone.\nSynopsis\nBEFORE ( text1 , text2 )\n-> text\nDescription\nReturn the substring of text1 which is before the leftmost occurrence of text2 in text1. If text2 does not occur in text1, text1 is returned.\nSide Effects\nNone.\nExample\nBEFORE ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> \u2019ab\u2019\nBEFORE ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> \u2019\u2019\nBEFORE ( \u2019abcdef\u2019 , \u2019\u2019 ) -> \u2018\u2019\nErrors\nNone.\nDISTANCE\nSynopsis\nDISTance ( number1 )\nDISTance( number1, logical1, logical2, logical3, number2, logical4)\n-> text\n-> text\nDescription\nFor the one-argument form, if the current distance units are FINCH, text is the conversion of the decimal inches value number1 into the format 'aa'bb.cc/dd'.\nOtherwise, text is the STRING conversion of number1.\nThe six-argument form is more complex. The format is:\nDIST/ANCE (distance, feet, usformat, fraction, denom_or_dp, zeros)\nWhere:\ndistance is the numeric distance in inches that is to be formatted.\nfeet is a logical flag set to true if output is to be in feet and inches and to false if output is to be in inches.\nusformat is a logical set to true if US format is to be used, or false if AVEVA E3D Design format is to be used.\nfraction is a logical set to true if the fractional component is to be output as a fraction, or false if to be output as a decimal denom_or_dp is a number representing the largest denominator if fraction is TRUE, or representing the number of decimal places if it is FALSE.\nzeros is a logical set to true if zeros are to be shown when that component of the output has no value.\nAVEVA E3D Design\nFor both US and AVEVA E3D Design formats, the following rules are observed:\nIf distance is negative, the first symbol is a minus sign.\nIf feet is true and the distance is at least a foot, then the number of feet is output next, followed by a single quote ('). Only if zeros is true will the number of feet be output as 0 for distances less than a foot. Otherwise, the feet will be omitted.\nIf feet have been output, the inches will be at least two characters wide. Numbers less than ten will be preceded by a space if US format is being used or a zero if AVEVA E3D Design format is used. A zero will be output if there are no whole inches.\nIf no feet have been output and the distance is at least an inch, then the number of inches is displayed but without any preceding spaces. Only if zeros is true will a 0 be output for distances of less than an inch.\nIf inches have been output and fraction is true, these will be followed by a decimal point (.).\nIf fraction is TRUE and the number has a fractional component, then the numerator and the denominator are shown separated by a slash (/). This is then blank padded up to the width that the largest numerator and denominator would take.\nIf fraction is FALSE and the number of decimal places is greater than zero, then the decimal point (.) is displayed followed by the remainder up to the appropriate number of decimal places. If the number of decimal places is 0 then the decimal point is not shown either.\nIf US format has been selected then the following additional rules are observed on output:\nThe (') after the number of feet is followed by a dash (-).\nThe decimal point separating the inches from the fraction is replaced by a space.\nThe inches and fraction of inches are followed by a double quote (\").\nSide Effects\nNone.\nExample\nIf the current distance units are FINCH:\nDISTANCE ( 17.5 ) ->  \u20191\u20195.1/2\u2019\nSome examples, where the current distance units are feet and inches:\nDIST(34.5,TRUE,TRUE,TRUE,100,TRUE) -> 2\u2019-10.1/2.\nDIST(34.5,FALSE,TRUE,FALSE,1,TRUE) -> 34.5\"\nDIST(34.5,FALSE,TRUE,TRUE,4,FALSE) -> 34 1/2\"\nDIST(128.5,TRUE,FALSE,TRUE,2,TRUE) -> 10\u201908.1/2\"\nThe following table shows sets of options that could have been chosen and the format of the output produced for different numbers. Blanks output by the system are represented by underscores (_).\nErrors\nThe value is too big to be converted.\nSynopsis\nDISTance ( number1 )\nDISTance( number1, logical1, logical2, logical3, number2, logical4)\n-> text\n-> text\nDescription\nFor the one-argument form, if the current distance units are FINCH, text is the conversion of the decimal inches value number1 into the format 'aa'bb.cc/dd'.\nOtherwise, text is the STRING conversion of number1.\nThe six-argument form is more complex. The format is:\nDIST/ANCE (distance, feet, usformat, fraction, denom_or_dp, zeros)\n\nWhere:\n\nAVEVA E3D Design\nFor both US and AVEVA E3D Design formats, the following rules are observed:\n\nIf US format has been selected then the following additional rules are observed on output:\n\nSide Effects\nNone.\nExample\nIf the current distance units are FINCH:\nSome examples, where the current distance units are feet and inches:\nDIST(34.5,TRUE,TRUE,TRUE,100,TRUE) -> 2\u2019-10.1/2.\nDIST(34.5,FALSE,TRUE,FALSE,1,TRUE) -> 34.5\"\nDIST(34.5,FALSE,TRUE,TRUE,4,FALSE) -> 34 1/2\"\nDIST(128.5,TRUE,FALSE,TRUE,2,TRUE) -> 10\u201908.1/2\"\nThe following table shows sets of options that could have been chosen and the format of the output produced for different numbers. Blanks output by the system are represented by underscores (_).\n\nErrors\nThe value is too big to be converted.\nLOWCASE and UPCASE\nSynopsis\nUPCase ( text1 )\n-> text\nLOWCase ( text1 )\n-> text\nDescription\nReturn an upper or lower case version of text1.\nSide Effects\nNone.\nExample\nUPCASE ( \u2019False\u2019) -> \u2019FALSE\u2019\nLOWCASE ( \u2019False\u2019) -> \u2019false\u2019\nErrors\nNone.\nSynopsis\nUPCase ( text1 )\n-> text\nLOWCase ( text1 )\n-> text\nDescription\nReturn an upper or lower case version of text1.\nSide Effects\nNone.\nExample\nUPCASE ( \u2019False\u2019) -> \u2019FALSE\u2019\nLOWCASE ( \u2019False\u2019) -> \u2019false\u2019\nErrors\nNone.\nPART\nSynopsis\nPART(text1, number1)\n-> text\nPART(text1, number1\n, text2)\n-> text\nDescription\nWith two arguments, returns the number1 component of text1 assuming that text1 is split on any whitespace characters. If number1 is negative, counting of components starts from the right.\nWith three arguments, as above, but use text2 as the separator on which splitting takes place.\nIf you gives a part number higher than the number of components in the string, the function returns an empty string.\nSide Effects\nNone.\nExample\nPART (\u2019x-y-z\u2019, 1, \u2019-\u2019 -> \u2019x\u2019\nPART (\u2019a b c d e\u2019, 4-> \u2019d\u2019\nPART (\u2019/PIPE45/B9\u2019, -1, \u2019/\u2019) -> \u2019B9\u2019\nPART(\u2019aa bb cc\u2019, 2) -> \u2019bb\u2019\nPART(\u2019aa-bb-cc\u2019,3,\u2019-\u2019) -> \u2019cc\u2019\nErrors\nNone.\nSynopsis\nPART(text1, number1)\n-> text\n\nPART(text1, number1\n, text2)\n-> text\nDescription\nWith two arguments, returns the number1 component of text1 assuming that text1 is split on any whitespace characters. If number1 is negative, counting of components starts from the right.\nWith three arguments, as above, but use text2 as the separator on which splitting takes place.\nIf you gives a part number higher than the number of components in the string, the function returns an empty string.\nSide Effects\nNone.\nExample\nPART (\u2019x-y-z\u2019, 1, \u2019-\u2019 -> \u2019x\u2019\nPART (\u2019a b c d e\u2019, 4-> \u2019d\u2019\nPART (\u2019/PIPE45/B9\u2019, -1, \u2019/\u2019) -> \u2019B9\u2019\nPART(\u2019aa bb cc\u2019, 2) -> \u2019bb\u2019\nPART(\u2019aa-bb-cc\u2019,3,\u2019-\u2019) -> \u2019cc\u2019\nErrors\nNone.\nREPLACE\nSynopsis\nREPLace (text1,text2,text3)\nREPLace(text1,text2,text3,int1)\nREPLace(text1,text2,text2,int1,int2)\n-> text\n-> text\n-> text\nDescription\nReplace search string text2 in input string text1 with replacement string text3.\nIf int1 is given this specifies the first occurrence of text2 at which to start replacement.\nIf int2 is given this specifies the number of replacements to make. int1 and/or int2 may be negative to indicate that the direction is backwards.\nSide Effects\nNone.\nExample\nThree arguments:\nREPLACE (\u2019cat dog cat cat dog \u2019, \u2019cat\u2019, \u2019dog\u2019 ) -> \u2019dog dog dog dog dog\u2019\nAll occurrences of 'cat' are replaced with 'dog'.\nFour arguments: start occurrence given:\nREPLACE (\u2019cat dog cat cat cat dog\u2019, \u2019cat\u2019, \u2019dog\u2019, 2) -> \u2019cat dog dog dog dog dog\nAll occurrence of 'cat' from the second occurrence onwards are replaced with 'dog':\nREPLACE(\u2019cat dog cat cat dog\u2019 ,\u2019cat\u2019, dog\u2019, -2 -> \u2019dog dog dog cat dog\u2019\nAll occurrences starting at the second occurrence from the end of the string and moving backwards are replaced.\nNote:\nA negative fourth argument without a fifth argument implies backwards mode.\nFive arguments: start occurrence and number of replacements given. Replace two occurrences of 'cat' starting at second occurrence:\nREPLACE (\u2019cat dog cat cat cat, \u2019cat\u2019,\u2019dog\u2019, 2,2) -> \u2019cat dog dog dog cat\u2019\nReplace two occurrences in backwards direction starting at the second occurrence:\nREPLACE (\u2019cat dog cat cat cat\u2019, ,\u2019cat\u2019, \u2019dog\u2019, 2, -2) -> \u2019dog dog dog cat cat \u2019\nReplace two occurrences in forwards direction starting at second occurrence from the end of the string:\nREPLACE (\u2019cat cat cat cat dog\u2019, \u2019cat\u2019, \u2019dog\u2019,-2,2) -> \u2019cat cat dog dog dog\u2019\nReplace two occurrences in backwards direction starting at second occurrence from the end of the string.\nREPLACE (\u2019cat cat cat cat dog\u2019,\u2019cat\u2019, \u2019dog\u2019, -2, -2) -> \u2019cat dog dog cat dog\u2019\nThe following examples all give the same result:\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, 4, 2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, 5, -2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019,-6, -2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, -7, 2)\n                  \nIn each case, the output string is:\n\u2019cat1 cat2 cat3 dog4 dog5 cat6 cat7 cat8 cat9 cat10\u2019\nIf the replacement string text3 is a null string, the required number of occurrences of the search string text2 are removed. For example:\nREPLACE (\u2019AAABBABZ\u2019, \u2019B\u2019, \u2019\u2019)   ->  \u2019AAAAZ\u2019\nREPLACE (\u2019AAABBABZ\u2019, \u2019B\u2019, \u2019\u2019, -1, -1) -> \u2019AAABBAZ\u2019\nErrors\nIf the input string text1 is a null string or an unset text attribute, the input string text1 is returned unchanged. For example:\nREPLACE (\u2019\u2019, \u2019A\u2019,\u2019B\u2019)  ->  \u2019\u2019\nIf the search string text2 is longer than the input string text1, the input string text1 is returned unchanged. For example:\nREPLACE(\u2019AA\u2019, \u2019AAAAA\u2019 , \u2019B\u2019)  -> \u2019AA\u2019\nIf no occurrence of the search string text2 is found, the input string text1 is returned unchanged. For example:\nREPLACE( \u2019AAAAAA\u2019,\u2019B\u2019,\u2019C\u2019)      -> \u2019AAAAAA\nIf required occurrence int1 is not found the input string text1 is returned unchanged. For example:\nREPLACE(\u2019AAAAAA\u2019, \u2019A\u2019, \u2019B\u2019, 10 )      -> \u2019AAAAAA\u2019\nIf the number of replacements required int2 is greater than the actual number of occurrence from the specified start occurrence, replacements are made up to the end of the string ( or beginning in backwards mode). For example:\nREPLACE(\u2019AAAAAA\u2019, \u2019A\u2019, \u2019B\u2019, 2, 8)   ->   \u2019ABBBBB\u2019\nREPLACE (\u2019AAAAAA\u2019, \u2019A\u2019, \u2019B\u2019, -3, 8)  ->   \u2019BBBBAA\u2019\nSynopsis\nREPLace (text1,text2,text3)\nREPLace(text1,text2,text3,int1)\nREPLace(text1,text2,text2,int1,int2)\n-> text\n-> text\n-> text\nDescription\nReplace search string text2 in input string text1 with replacement string text3.\nIf int1 is given this specifies the first occurrence of text2 at which to start replacement.\nIf int2 is given this specifies the number of replacements to make. int1 and/or int2 may be negative to indicate that the direction is backwards.\nSide Effects\nNone.\nExample\nThree arguments:\nAll occurrences of 'cat' are replaced with 'dog'.\nFour arguments: start occurrence given:\n\nAll occurrence of 'cat' from the second occurrence onwards are replaced with 'dog':\nAll occurrences starting at the second occurrence from the end of the string and moving backwards are replaced.\n\nFive arguments: start occurrence and number of replacements given. Replace two occurrences of 'cat' starting at second occurrence:\nReplace two occurrences in backwards direction starting at the second occurrence:\n\nReplace two occurrences in forwards direction starting at second occurrence from the end of the string:\nReplace two occurrences in backwards direction starting at second occurrence from the end of the string.\n\nThe following examples all give the same result:\n\nIn each case, the output string is:\nIf the replacement string text3 is a null string, the required number of occurrences of the search string text2 are removed. For example:\nREPLACE (\u2019AAABBABZ\u2019, \u2019B\u2019, \u2019\u2019, -1, -1) -> \u2019AAABBAZ\u2019\nErrors\nIf the input string text1 is a null string or an unset text attribute, the input string text1 is returned unchanged. For example:\nIf the search string text2 is longer than the input string text1, the input string text1 is returned unchanged. For example:\nIf no occurrence of the search string text2 is found, the input string text1 is returned unchanged. For example:\n\nIf required occurrence int1 is not found the input string text1 is returned unchanged. For example:\nIf the number of replacements required int2 is greater than the actual number of occurrence from the specified start occurrence, replacements are made up to the end of the string ( or beginning in backwards mode). For example:\nSTRING\nSynopsis\nSTRing ( any scalar type )\n-> text\nSTRing ( number , text1 )\n-> text\nSTRing ( pos , text1 )\n-> text\nDescription\nTurns a value into a text string.\nWith a single argument the STRING function can be applied to the following scalar data types:\nNumeric\nLogical\nId\nPosition\nDirection\nOrientation\nWith only one argument, decimal places are output to give a maximum of six significant figures. Trailing zeros are always removed in this case.\nWith two arguments the data type may be either numeric (scalar) or position or direction. With two arguments, convert a number or position into a text string using the format described by text1, which may take any of the values between 'D0' and 'D6' (or 'd0' and 'd6'), where the number indicates the number of decimal places.\nFor numbers, STRING always outputs values as millimetres. If unit conversion is needed then the DIST function should be used. For positions, the current distance units are used.\nSide Effects\nNone.\nExample\nSTRING ( 1 ) -> \u20191\u2019\nSTRING ( 1 , \u2019D3\u2019 ) -> \u20191.000\u2019\nSTRING ( 1.23456789 ) -> \u20191.23457\u2019\nSTRING(1.1230000) ->\u20191.123\u2019\nSTRING ( 1.23456789 , \u2019D3\u2019 ) -> \u20191.235\u2019\nSTRING (9*9 LT 100) -> \u2019TRUE\u2019\nSTRING (OWN OF CE) -> \u2019/PIPE1\u2019\nSTRING(POS) -> \u2019W1000 N20000 U18000\u2019\nSTRING(POS, \u2019D4\u2019 ) -> \u2019W10000.1234 N20000.1234 U18000.1234\u2019\nSTRING(HDIR OF /PIPE1-1) -> \u2019D\u2019\nSTRING(E 22.0125 N, \u2019D2\u2019) -> \u2019E 22.01 N\u2019\nSTRING (ORI OF NEXT) -> \u2019Y IS D AND Z IS U\u2019\nErrors\nSynopsis\nSTRing ( any scalar type )\n-> text\nSTRing ( number , text1 )\n-> text\nSTRing ( pos , text1 )\n-> text\nDescription\nTurns a value into a text string.\nWith a single argument the STRING function can be applied to the following scalar data types:\nWith only one argument, decimal places are output to give a maximum of six significant figures. Trailing zeros are always removed in this case.\nWith two arguments the data type may be either numeric (scalar) or position or direction. With two arguments, convert a number or position into a text string using the format described by text1, which may take any of the values between 'D0' and 'D6' (or 'd0' and 'd6'), where the number indicates the number of decimal places.\nFor numbers, STRING always outputs values as millimetres. If unit conversion is needed then the DIST function should be used. For positions, the current distance units are used.\nSide Effects\nNone.\nExample\nSTRING ( 1 ) -> \u20191\u2019\nSTRING ( 1 , \u2019D3\u2019 ) -> \u20191.000\u2019\nSTRING ( 1.23456789 ) -> \u20191.23457\u2019\nSTRING(1.1230000) ->\u20191.123\u2019\nSTRING ( 1.23456789 , \u2019D3\u2019 ) -> \u20191.235\u2019\nSTRING (9*9 LT 100) -> \u2019TRUE\u2019\nSTRING (OWN OF CE) -> \u2019/PIPE1\u2019\nSTRING(POS) -> \u2019W1000 N20000 U18000\u2019\nSTRING(POS, \u2019D4\u2019 ) -> \u2019W10000.1234 N20000.1234 U18000.1234\u2019\nSTRING(HDIR OF /PIPE1-1) -> \u2019D\u2019\nSTRING(E 22.0125 N, \u2019D2\u2019) -> \u2019E 22.01 N\u2019\nSTRING (ORI OF NEXT) -> \u2019Y IS D AND Z IS U\u2019\nErrors\n\nSUBSTRING\nSynopsis\n)SUBString ( text1 , number1 )\n-> text\nSUBString ( text1 , number1 , number2 )\n-> text\nDescription\nWith two arguments, return the substring of text1 beginning at the position number1 to the end of text1.\nWith three arguments, return the substring of text1 beginning at the position number1 and of length number2.\nIf number1 is negative, then counting of characters starts from the RHS of the input string. If number2 is negative, then characters up to and including the start position are returned.\nSide Effects\nNone.\nExample\nSUBSTRING ( \u2019abcdef\u2019 , 3 ) -> \u2019cdef\u2019\nSUBSTRING ( \u2019abcdef\u2019 ,-3 ) -> \u2019abcd\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 3 , 2 ) -> \u2019cd\u2019\nSUBSTRING ( \u2019abcdef\u2019 , -3, 2 ) -> \u2019de\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 3 , -2 ) -> \u2019bc\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 10 ) -> \u2019\u2019\nSUBSTRING ( \u2019abcdef\u2019 , -10 , 2 ) -> \u2019ab\u2019\nErrors\nNone.\nSynopsis\n)SUBString ( text1 , number1 )\n-> text\n\nSUBString ( text1 , number1 , number2 )\n-> text\nDescription\nWith two arguments, return the substring of text1 beginning at the position number1 to the end of text1.\nWith three arguments, return the substring of text1 beginning at the position number1 and of length number2.\nIf number1 is negative, then counting of characters starts from the RHS of the input string. If number2 is negative, then characters up to and including the start position are returned.\nSide Effects\nNone.\nExample\nSUBSTRING ( \u2019abcdef\u2019 , 3 ) -> \u2019cdef\u2019\nSUBSTRING ( \u2019abcdef\u2019 ,-3 ) -> \u2019abcd\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 3 , 2 ) -> \u2019cd\u2019\nSUBSTRING ( \u2019abcdef\u2019 , -3, 2 ) -> \u2019de\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 3 , -2 ) -> \u2019bc\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 10 ) -> \u2019\u2019\nSUBSTRING ( \u2019abcdef\u2019 , -10 , 2 ) -> \u2019ab\u2019\nErrors\nNone.\nTRIM\nSynopsis\nTRIM ( text1 )\n-> text\nTRIM ( text1, text2 )\n-> text\nTRIM ( text1, text2, text3 )\n-> text\nDescription\nWhen only one argument is supplied, TRIM removes all spaces to the left (leading) and right (trailing) of text1 and returns the answer in text.\nWhen two arguments are supplied, text2 specifies where the spaces should be removed from: either 'L' or 'l' for left, 'R' or 'r' for right, and 'M' or 'm' for multiple (where multiple occurrences of blanks are squeezed to a single spaces) or any combination of the three key letters. So the default is 'LR' when this field is omitted.\nWhen the third argument text3 is also supplied, this should only be a single character which overrides the space character as the character being trimmed.\nSide Effects\nNone.\nExample\nTRIM ( \u2019 How now, brown cow \u2019, \u2019LRM\u2019 ) -> \u2019How now, brown cow\u2019\nTRIM ( \u201910.3000\u2019, \u2019R\u2019, \u20190\u2019 ) -> \u201910.3\u2019\nErrors\nNone.\nSynopsis\nTRIM ( text1 )\n-> text\nTRIM ( text1, text2 )\n-> text\nTRIM ( text1, text2, text3 )\n-> text\nDescription\nWhen only one argument is supplied, TRIM removes all spaces to the left (leading) and right (trailing) of text1 and returns the answer in text.\nWhen two arguments are supplied, text2 specifies where the spaces should be removed from: either 'L' or 'l' for left, 'R' or 'r' for right, and 'M' or 'm' for multiple (where multiple occurrences of blanks are squeezed to a single spaces) or any combination of the three key letters. So the default is 'LR' when this field is omitted.\nWhen the third argument text3 is also supplied, this should only be a single character which overrides the space character as the character being trimmed.\nSide Effects\nNone.\nExample\nTRIM ( \u2019 How now, brown cow \u2019, \u2019LRM\u2019 ) -> \u2019How now, brown cow\u2019\nTRIM ( \u201910.3000\u2019, \u2019R\u2019, \u20190\u2019 ) -> \u201910.3\u2019\nErrors\nNone.\nVTEXT\nVTEXT is used for the late evaluation of variables.\nSynopsis\nVTEXT ( variable-name )\n-> text\nVTEXT ( variable-name , number )\n-> text\nDescription\nWith one argument, it gets the value of the scalar variable or the value of the array variable element.\nWith two arguments, it gets the value of the element corresponding to the index number.\nThe value is returned as a text string.\nSee also VLOGICAL used for late evaluation when a logical result is required, and VVALUE used for late evaluation when a numeric result is required.\nSide Effects\nIf the scalar variable, the array variable or the array variable element does not exist, the result is undefined.\nExample\nVTEXT ( !var ) -> \u2019hello\u2019\nVTEXT ( !array[1] ) -> \u20191.00\u2019\nVTEXT ( !array , 2 ) -> \u20190.00\u2019\nErrors\nErrors Scalar variable may not be indexed (for example, VTEXT (!var[1])).\nArray variable must have an index (for example, VTEXT ( !array )).\nSynopsis\nVTEXT ( variable-name )\n-> text\nVTEXT ( variable-name , number )\n-> text\nDescription\nWith one argument, it gets the value of the scalar variable or the value of the array variable element.\nWith two arguments, it gets the value of the element corresponding to the index number.\nThe value is returned as a text string.\nSee also VLOGICAL used for late evaluation when a logical result is required, and VVALUE used for late evaluation when a numeric result is required.\nSide Effects\nIf the scalar variable, the array variable or the array variable element does not exist, the result is undefined.\nExample\nVTEXT ( !var ) -> \u2019hello\u2019\nVTEXT ( !array[1] ) -> \u20191.00\u2019\nVTEXT ( !array , 2 ) -> \u20190.00\u2019\nErrors\nErrors Scalar variable may not be indexed (for example, VTEXT (!var[1])).\nArray variable must have an index (for example, VTEXT ( !array )).\nFunction\nComments\nAFTER\nBEFORE\nDISTANCE\nLOWCASE, UPCASE\nPART\nREPLACE\nSTRING\nSUBS, DSUBS\nTRIM\nVTEXT\nSynopsis\nAFTER ( text1 , text2 )\n-> text\nDescription\nReturn the substring of text1 which is after the leftmost occurrence of text2 in text1.\nIf text2 does not occur in text1, the null string is returned.\nSide Effects\nNone.\nExample\nAFTER ( \u2019abcdef\u2019 , \u2019cd\u2019 ) ->\u2019ef\u2019\nAFTER ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> \u2019\u2019\nAFTER ( \u2019abcdef\u2019 , \u2019\u2019 ) -> \u2019abcdef\u2019\nErrors\nNone.\nSynopsis\nBEFORE ( text1 , text2 )\n-> text\nDescription\nReturn the substring of text1 which is before the leftmost occurrence of text2 in text1. If text2 does not occur in text1, text1 is returned.\nSide Effects\nNone.\nExample\nBEFORE ( \u2019abcdef\u2019 , \u2019cd\u2019 ) -> \u2019ab\u2019\nBEFORE ( \u2019abcdef\u2019 , \u2019x\u2019 ) -> \u2019\u2019\nBEFORE ( \u2019abcdef\u2019 , \u2019\u2019 ) -> \u2018\u2019\nErrors\nNone.\nSynopsis\nDISTance ( number1 )\nDISTance( number1, logical1, logical2, logical3, number2, logical4)\n-> text\n-> text\nDescription\nFor the one-argument form, if the current distance units are FINCH, text is the conversion of the decimal inches value number1 into the format 'aa'bb.cc/dd'.\nOtherwise, text is the STRING conversion of number1.\nThe six-argument form is more complex. The format is:\nDIST/ANCE (distance, feet, usformat, fraction, denom_or_dp, zeros)\nWhere:\ndistance is the numeric distance in inches that is to be formatted.\nfeet is a logical flag set to true if output is to be in feet and inches and to false if output is to be in inches.\nusformat is a logical set to true if US format is to be used, or false if AVEVA E3D Design format is to be used.\nfraction is a logical set to true if the fractional component is to be output as a fraction, or false if to be output as a decimal denom_or_dp is a number representing the largest denominator if fraction is TRUE, or representing the number of decimal places if it is FALSE.\nzeros is a logical set to true if zeros are to be shown when that component of the output has no value.\nAVEVA E3D Design\nFor both US and AVEVA E3D Design formats, the following rules are observed:\nIf distance is negative, the first symbol is a minus sign.\nIf feet is true and the distance is at least a foot, then the number of feet is output next, followed by a single quote ('). Only if zeros is true will the number of feet be output as 0 for distances less than a foot. Otherwise, the feet will be omitted.\nIf feet have been output, the inches will be at least two characters wide. Numbers less than ten will be preceded by a space if US format is being used or a zero if AVEVA E3D Design format is used. A zero will be output if there are no whole inches.\nIf no feet have been output and the distance is at least an inch, then the number of inches is displayed but without any preceding spaces. Only if zeros is true will a 0 be output for distances of less than an inch.\nIf inches have been output and fraction is true, these will be followed by a decimal point (.).\nIf fraction is TRUE and the number has a fractional component, then the numerator and the denominator are shown separated by a slash (/). This is then blank padded up to the width that the largest numerator and denominator would take.\nIf fraction is FALSE and the number of decimal places is greater than zero, then the decimal point (.) is displayed followed by the remainder up to the appropriate number of decimal places. If the number of decimal places is 0 then the decimal point is not shown either.\nIf US format has been selected then the following additional rules are observed on output:\nThe (') after the number of feet is followed by a dash (-).\nThe decimal point separating the inches from the fraction is replaced by a space.\nThe inches and fraction of inches are followed by a double quote (\").\nSide Effects\nNone.\nExample\nIf the current distance units are FINCH:\nDISTANCE ( 17.5 ) ->  \u20191\u20195.1/2\u2019\nSome examples, where the current distance units are feet and inches:\nDIST(34.5,TRUE,TRUE,TRUE,100,TRUE) -> 2\u2019-10.1/2.\nDIST(34.5,FALSE,TRUE,FALSE,1,TRUE) -> 34.5\"\nDIST(34.5,FALSE,TRUE,TRUE,4,FALSE) -> 34 1/2\"\nDIST(128.5,TRUE,FALSE,TRUE,2,TRUE) -> 10\u201908.1/2\"\nThe following table shows sets of options that could have been chosen and the format of the output produced for different numbers. Blanks output by the system are represented by underscores (_).\nErrors\nThe value is too big to be converted.\nSynopsis\nUPCase ( text1 )\n-> text\nLOWCase ( text1 )\n-> text\nDescription\nReturn an upper or lower case version of text1.\nSide Effects\nNone.\nExample\nUPCASE ( \u2019False\u2019) -> \u2019FALSE\u2019\nLOWCASE ( \u2019False\u2019) -> \u2019false\u2019\nErrors\nNone.\nSynopsis\nPART(text1, number1)\n-> text\nPART(text1, number1\n, text2)\n-> text\nDescription\nWith two arguments, returns the number1 component of text1 assuming that text1 is split on any whitespace characters. If number1 is negative, counting of components starts from the right.\nWith three arguments, as above, but use text2 as the separator on which splitting takes place.\nIf you gives a part number higher than the number of components in the string, the function returns an empty string.\nSide Effects\nNone.\nExample\nPART (\u2019x-y-z\u2019, 1, \u2019-\u2019 -> \u2019x\u2019\nPART (\u2019a b c d e\u2019, 4-> \u2019d\u2019\nPART (\u2019/PIPE45/B9\u2019, -1, \u2019/\u2019) -> \u2019B9\u2019\nPART(\u2019aa bb cc\u2019, 2) -> \u2019bb\u2019\nPART(\u2019aa-bb-cc\u2019,3,\u2019-\u2019) -> \u2019cc\u2019\nErrors\nNone.\nSynopsis\nREPLace (text1,text2,text3)\nREPLace(text1,text2,text3,int1)\nREPLace(text1,text2,text2,int1,int2)\n-> text\n-> text\n-> text\nDescription\nReplace search string text2 in input string text1 with replacement string text3.\nIf int1 is given this specifies the first occurrence of text2 at which to start replacement.\nIf int2 is given this specifies the number of replacements to make. int1 and/or int2 may be negative to indicate that the direction is backwards.\nSide Effects\nNone.\nExample\nThree arguments:\nREPLACE (\u2019cat dog cat cat dog \u2019, \u2019cat\u2019, \u2019dog\u2019 ) -> \u2019dog dog dog dog dog\u2019\nAll occurrences of 'cat' are replaced with 'dog'.\nFour arguments: start occurrence given:\nREPLACE (\u2019cat dog cat cat cat dog\u2019, \u2019cat\u2019, \u2019dog\u2019, 2) -> \u2019cat dog dog dog dog dog\nAll occurrence of 'cat' from the second occurrence onwards are replaced with 'dog':\nREPLACE(\u2019cat dog cat cat dog\u2019 ,\u2019cat\u2019, dog\u2019, -2 -> \u2019dog dog dog cat dog\u2019\nAll occurrences starting at the second occurrence from the end of the string and moving backwards are replaced.\nNote:\nA negative fourth argument without a fifth argument implies backwards mode.\nFive arguments: start occurrence and number of replacements given. Replace two occurrences of 'cat' starting at second occurrence:\nREPLACE (\u2019cat dog cat cat cat, \u2019cat\u2019,\u2019dog\u2019, 2,2) -> \u2019cat dog dog dog cat\u2019\nReplace two occurrences in backwards direction starting at the second occurrence:\nREPLACE (\u2019cat dog cat cat cat\u2019, ,\u2019cat\u2019, \u2019dog\u2019, 2, -2) -> \u2019dog dog dog cat cat \u2019\nReplace two occurrences in forwards direction starting at second occurrence from the end of the string:\nREPLACE (\u2019cat cat cat cat dog\u2019, \u2019cat\u2019, \u2019dog\u2019,-2,2) -> \u2019cat cat dog dog dog\u2019\nReplace two occurrences in backwards direction starting at second occurrence from the end of the string.\nREPLACE (\u2019cat cat cat cat dog\u2019,\u2019cat\u2019, \u2019dog\u2019, -2, -2) -> \u2019cat dog dog cat dog\u2019\nThe following examples all give the same result:\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, 4, 2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, 5, -2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019,-6, -2)\nREPLACE(\u2019cat1 cat2 cat3 cat4 cat5 cat6 cat7 cat8 cat9 cat10\u2019, \u2019cat\u2019, \u2019dog\u2019, -7, 2)\n                  \nIn each case, the output string is:\n\u2019cat1 cat2 cat3 dog4 dog5 cat6 cat7 cat8 cat9 cat10\u2019\nIf the replacement string text3 is a null string, the required number of occurrences of the search string text2 are removed. For example:\nREPLACE (\u2019AAABBABZ\u2019, \u2019B\u2019, \u2019\u2019)   ->  \u2019AAAAZ\u2019\nREPLACE (\u2019AAABBABZ\u2019, \u2019B\u2019, \u2019\u2019, -1, -1) -> \u2019AAABBAZ\u2019\nErrors\nIf the input string text1 is a null string or an unset text attribute, the input string text1 is returned unchanged. For example:\nREPLACE (\u2019\u2019, \u2019A\u2019,\u2019B\u2019)  ->  \u2019\u2019\nIf the search string text2 is longer than the input string text1, the input string text1 is returned unchanged. For example:\nREPLACE(\u2019AA\u2019, \u2019AAAAA\u2019 , \u2019B\u2019)  -> \u2019AA\u2019\nIf no occurrence of the search string text2 is found, the input string text1 is returned unchanged. For example:\nREPLACE( \u2019AAAAAA\u2019,\u2019B\u2019,\u2019C\u2019)      -> \u2019AAAAAA\nIf required occurrence int1 is not found the input string text1 is returned unchanged. For example:\nREPLACE(\u2019AAAAAA\u2019, \u2019A\u2019, \u2019B\u2019, 10 )      -> \u2019AAAAAA\u2019\nIf the number of replacements required int2 is greater than the actual number of occurrence from the specified start occurrence, replacements are made up to the end of the string ( or beginning in backwards mode). For example:\nREPLACE(\u2019AAAAAA\u2019, \u2019A\u2019, \u2019B\u2019, 2, 8)   ->   \u2019ABBBBB\u2019\nREPLACE (\u2019AAAAAA\u2019, \u2019A\u2019, \u2019B\u2019, -3, 8)  ->   \u2019BBBBAA\u2019\nSynopsis\nSTRing ( any scalar type )\n-> text\nSTRing ( number , text1 )\n-> text\nSTRing ( pos , text1 )\n-> text\nDescription\nTurns a value into a text string.\nWith a single argument the STRING function can be applied to the following scalar data types:\nNumeric\nLogical\nId\nPosition\nDirection\nOrientation\nWith only one argument, decimal places are output to give a maximum of six significant figures. Trailing zeros are always removed in this case.\nWith two arguments the data type may be either numeric (scalar) or position or direction. With two arguments, convert a number or position into a text string using the format described by text1, which may take any of the values between 'D0' and 'D6' (or 'd0' and 'd6'), where the number indicates the number of decimal places.\nFor numbers, STRING always outputs values as millimetres. If unit conversion is needed then the DIST function should be used. For positions, the current distance units are used.\nSide Effects\nNone.\nExample\nSTRING ( 1 ) -> \u20191\u2019\nSTRING ( 1 , \u2019D3\u2019 ) -> \u20191.000\u2019\nSTRING ( 1.23456789 ) -> \u20191.23457\u2019\nSTRING(1.1230000) ->\u20191.123\u2019\nSTRING ( 1.23456789 , \u2019D3\u2019 ) -> \u20191.235\u2019\nSTRING (9*9 LT 100) -> \u2019TRUE\u2019\nSTRING (OWN OF CE) -> \u2019/PIPE1\u2019\nSTRING(POS) -> \u2019W1000 N20000 U18000\u2019\nSTRING(POS, \u2019D4\u2019 ) -> \u2019W10000.1234 N20000.1234 U18000.1234\u2019\nSTRING(HDIR OF /PIPE1-1) -> \u2019D\u2019\nSTRING(E 22.0125 N, \u2019D2\u2019) -> \u2019E 22.01 N\u2019\nSTRING (ORI OF NEXT) -> \u2019Y IS D AND Z IS U\u2019\nErrors\nSynopsis\n)SUBString ( text1 , number1 )\n-> text\nSUBString ( text1 , number1 , number2 )\n-> text\nDescription\nWith two arguments, return the substring of text1 beginning at the position number1 to the end of text1.\nWith three arguments, return the substring of text1 beginning at the position number1 and of length number2.\nIf number1 is negative, then counting of characters starts from the RHS of the input string. If number2 is negative, then characters up to and including the start position are returned.\nSide Effects\nNone.\nExample\nSUBSTRING ( \u2019abcdef\u2019 , 3 ) -> \u2019cdef\u2019\nSUBSTRING ( \u2019abcdef\u2019 ,-3 ) -> \u2019abcd\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 3 , 2 ) -> \u2019cd\u2019\nSUBSTRING ( \u2019abcdef\u2019 , -3, 2 ) -> \u2019de\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 3 , -2 ) -> \u2019bc\u2019\nSUBSTRING ( \u2019abcdef\u2019 , 10 ) -> \u2019\u2019\nSUBSTRING ( \u2019abcdef\u2019 , -10 , 2 ) -> \u2019ab\u2019\nErrors\nNone.\nSynopsis\nTRIM ( text1 )\n-> text\nTRIM ( text1, text2 )\n-> text\nTRIM ( text1, text2, text3 )\n-> text\nDescription\n"}
{"Headers": "Late Evaluation of Variables in Expressions", "Content": "The functions VVALUE, VLOGICAL, and VTEXT are used for late evaluation of PML variables, that is, they enable you to specify PML variables in expressions which will not be evaluated until the expression is evaluated.\nFor example, when you are creating a report template, you are actually creating a macro which will run when a report is generated. All variables in a report template must therefore be preceded by a suitable late evaluation operator. Otherwise, the system will try to substitute a value for the variable when it is entered on the form.\nThe difference between the operators is the type of output. VVALUE is used to output a numeric value, VLOGICAL to output a logical variable and VTEXT to output a text variable.\n\n\n\nVVALUE\nVLOGICAL\nVTEXT\nVVALUE\nVLOGICAL\nVTEXT"}
{"Headers": "Attributes in Expressions", "Content": "All attributes and pseudo-attributes may be recognized within expressions.\nOptionally, they may be followed by 'OF' to denote a different element to the current one, for example, POS OF /VESS1. Brackets may be used to denote an element of an array, for example, DESP[8 + 1] for the ninth value of DESP. Since syntax clashes are possible, the keyword ATTRIB may be used to denote that an attribute follows. For example, ATTRIB E will denote the pseudo-attribute EAST, as opposed to the start of a position or direction.\nAttributes are described in the Data Model Reference Manual.\n\n\n\nOF\nPOS OF /VESS1\nDESP[8 + 1]\nDESP\nATTRIB\nATTRIB E\nEAST\nData Model Reference Manual"}
{"Headers": "Querying Expressions", "Content": "All expressions may be queried. Arrays are always concatenated into a single variable. Imperial values are always output as inch to variables. This preserves maximum accuracy.\nTo output in FINCH, then the DISTANCE function must be used. In general, expressions do not have to be enclosed in brackets, but to be sure that other queries are not picked up by mistake, then it is advised to do so.\nParticular queries that could lead to confusion are those available both outside and inside expressions. These are:\nThe functionality may vary between outside and inside expression queries. For example, 'Q N 100 FROM /POSS' is not valid. It must be entered as: Q N 100 FROM /POSS ).\nQ PPOINT n\nQ POS or cartesian position\nQ ORI or cartesian orientation\nQ PPOINT n\nQ PPOINT n\nQ POS or cartesian position\nQ POS or cartesian position\nQ ORI or cartesian orientation\nQ ORI or cartesian orientation\n\n\n\nDISTANCE\nQ PPOINT n\nQ POS or cartesian position\nQ ORI or cartesian orientation\n'Q N 100 FROM /POSS'\nQ N 100 FROM /POSS )"}
{"Headers": "Units in Expressions", "Content": "When a user enters a literal value, then the units are not necessarily known. The units for PML variables may not be known if not input initially. Where units are known, then all internal values are set to database units (mm for distances). The value is then converted to the target (local) units on assignment to a variable or on output.\nTo cope with 'unknown' units, each value remembers its original units internally. An attempt is then made to allow for 'unknown' units across operators.\nThe internal settings for units are as follows:\nNONE\nNo units. e.g. attribute OBS.\nUNKN\nUnknown units, e.g. 10.\nMM\nDist/bore attribute if units are MM, or literal e.g. 10 mm.\nINCH\nDist/bore attribute if units are INCH/FINCH, or literal e.g. 10'.\nSQIN\nMultiply two INCH values together, or literal e.g. 10 sq in.\nCUIN\nMultiply SQIN by INCH, or literal e.g. 10 cu in.\nOn comparison, addition or subtraction of two values the following assumptions are made. If one of the units is unknown and the other is anything other than UNKN, then the unknown value is assumed to have the same units as the known units. A suitable conversion is then done if the known units is INCH or SQIN or CUIN.\nFor example:\nIf we are working in distance units of inches, it is known that XLEN is a distance value. Internally, the value is held in mm, but the units are held as INCH. The units for '10' are held as unknown. On doing the comparison, the '10' is assumed to be inches and thus multiplied by 25.4 to make sure that the comparison works as expected.\nSpecial action is also taken to preserve the correct units across multiplication, division, POWER and SQRT, in particular the maintenance of SQIN and CUIN. In these situations, units of %UNKN are treated as none. For example, (10 * XLEN) is assumed to result in INCH rather than SQIN. An exception is made when a reciprocal would result from division. For example: for (10 / XLEN) we assume that the 10 is in inches rather than none.\nSetting\nComments\nNONE\nNo units. e.g. attribute OBS.\nUNKN\nUnknown units, e.g. 10.\nMM\nDist/bore attribute if units are MM, or literal e.g. 10 mm.\nINCH\nDist/bore attribute if units are INCH/FINCH, or literal e.g. 10'.\nSQIN\nMultiply two INCH values together, or literal e.g. 10 sq in.\nCUIN\nMultiply SQIN by INCH, or literal e.g. 10 cu in.\n(XLEN GT 10)\n\n\n\nUNKN\n(10 * XLEN)\n(10 / XLEN)"}
{"Headers": "Precision of Comparisons", "Content": "To allow for small losses of accuracy, the following tolerances are used.\nNumber\nTolerance factor of 0.000001.\nIn other words, if the difference between two reals is not greater than 0.000001* (maximum of the two values) then the values are considered to be equal.\nFor example:\nPosition\nConsidered to be equal if within 0.5 mm of one another.\nDirection or Orientation\nConsidered to be equal if values are within 0.005.\nObject\nTolerance\nNumber\nTolerance factor of 0.000001.\nIn other words, if the difference between two reals is not greater than 0.000001* (maximum of the two values) then the values are considered to be equal.\nFor example:\n(1.000001 GT 1) is FALSE as it considers 1.000001, and 1 to be equal\n(1.000002 GT 1) is TRUE\nPosition\nConsidered to be equal if within 0.5 mm of one another.\nDirection or Orientation\nConsidered to be equal if values are within 0.005.\n(1.000001 GT 1) is FALSE as it considers 1.000001, and 1 to be equal\n(1.000002 GT 1) is TRUE\n(1.000001 GT 1) is FALSE as it considers 1.000001, and 1 to be equal\n(1.000001 GT 1) is FALSE as it considers 1.000001, and 1 to be equal\n(1.000002 GT 1) is TRUE\n(1.000002 GT 1) is TRUE\n\n\n\nFALSE\nTRUE"}
{"Headers": "Undefined Values", "Content": "In order to permit expressions like ((DIAM GT 200.0) OR (TYPE EQ \u2019BOX\u2019)), expressions must be able to cope with undefined values. Generally, applying an operator to one or more undefined arguments has an undefined result.\nTwo exceptions are: the use of the AND operator with a false argument, will result in FALSE, regardless of whether or not the remainder of the arguments are defined; and OR which returns TRUE if any of its arguments is TRUE.\nFor example, consider applying the above expression when the current element is a box. DIAM is undefined, therefore (DIAM GT 200.0) is also undefined. However, (TYPE EQ \u2019BOX\u2019) is certainly true and so the final result of the whole expression evaluates to TRUE.\nAn undefined result occurs when:\nOne of the operands or arguments of a function (except some cases of AND and OR) is undefined.\nAn attribute is unavailable for the corresponding element (for example, \u2019DIAM OF OWNER\u2019 when the current element is a box).\nAn element is undefined (for example, \u2019OWNER\u2019 when the current element is the WORLD).\nAn attribute is unset (for example, text attribute or UDA of length 0).\nA variable is undefined (for example, \u2019VVAL(!ARC6)\u2019 where !ARC6 has never been initialized).\nTwo position constants are compared with GT, GE, LT, or LE and they have no common coordinates (for example, \u2019N10 EQ E5\u2019).\nIf the result of the whole expression is undefined, an error occurs.\nOne of the operands or arguments of a function (except some cases of AND and OR) is undefined.\nOne of the operands or arguments of a function (except some cases of AND and OR) is undefined.\nAn attribute is unavailable for the corresponding element (for example, \u2019DIAM OF OWNER\u2019 when the current element is a box).\nAn attribute is unavailable for the corresponding element (for example, \u2019DIAM OF OWNER\u2019 when the current element is a box).\nAn element is undefined (for example, \u2019OWNER\u2019 when the current element is the WORLD).\nAn element is undefined (for example, \u2019OWNER\u2019 when the current element is the WORLD).\nAn attribute is unset (for example, text attribute or UDA of length 0).\nAn attribute is unset (for example, text attribute or UDA of length 0).\nA variable is undefined (for example, \u2019VVAL(!ARC6)\u2019 where !ARC6 has never been initialized).\nA variable is undefined (for example, \u2019VVAL(!ARC6)\u2019 where !ARC6 has never been initialized).\nTwo position constants are compared with GT, GE, LT, or LE and they have no common coordinates (for example, \u2019N10 EQ E5\u2019).\nTwo position constants are compared with GT, GE, LT, or LE and they have no common coordinates (for example, \u2019N10 EQ E5\u2019).\nIf the result of the whole expression is undefined, an error occurs.\nIf the result of the whole expression is undefined, an error occurs.\n\n\n\n((DIAM GT 200.0) OR (TYPE EQ \u2019BOX\u2019))\nAND\nFALSE\nOR\nTRUE\nTRUE\nDIAM\n(DIAM GT 200.0)\n(TYPE EQ \u2019BOX\u2019)\nTRUE\nAND\nOR\n\u2019DIAM OF OWNER\u2019\n\u2019OWNER\u2019\n\u2019VVAL(!ARC6)\u2019\n!ARC6\nGT\nGE\nLT\nLE\n\u2019N10 EQ E5\u2019"}
{"Headers": "Unset Values", "Content": "A particular class of undefined values are unset values. The concept exists for attributes which are valid for a given element, but for which no value has been assigned. Typically these may be elements of an array, or 'word' attributes. References of value =0/0 are also treated as unset.\nUnset values are propagated as for undefined values (except for Boolean operations- see below). Undefined values take precedence over unset. There is a specific logical function UNSET to test if a values is unset.\nAcross comparisons, unset values are not propagated, but are treated as follows:\nEQ, GT, GE, LT, LE\nResults in FALSE.\nNE\nResults in TRUE.\nOR, AND\nValues are treated as FALSE.\nFor example, if DESP(2) and LVAL(3) are unset then:\nOperator\nWhen Applied to an UNSET\nEQ, GT, GE, LT, LE\nResults in FALSE.\nNE\nResults in TRUE.\nOR, AND\nValues are treated as FALSE.\n(DESP(2) GT 99) -> False\n(DESP(2) NE 33) -> True\n(:LVAL(3) AND TRUE) -> False\n\n\n\nEQ\nGT\nGE\nLT\nLE\nFALSE\nNE\nTRUE\nOR\nAND\nFALSE\nDESP(2)\nLVAL(3)\n(DESP(2) GT 99) -> False\n(DESP(2) NE 33) -> True\n(:LVAL(3) AND TRUE) -> False"}
{"Headers": "BEAMS  COLUMNS  STRUCTURE APPLICATION  Presentation of the module ", "Content": "The Structure Module is splitIn 4 different types of applications: 1 - Beams & Columns... Metal frames from a complete catalog 2 - Panels & Plates... Plates, pebbles, etc... 3 - Walls & Floors... Civil Engineering,... 4 - Stair, Ladder and Handrail Stairs, ladders and railings"}
{"Headers": "BEAMS  COLUMNS  STRUCTURE APPLICATION  Hierarchy ", "Content": "AVEVA E3D allows you to create structural elements according to the following hierarchy model: Section and plates FRMW GENSEC 1,PANE1,SCTN2,GWALL,FLOOR,SCREED Walls and floors CFLOOR CSCREE CWALL FLOOR SCREED STWALLHANDRA STRFLT RLADDR "}
{"Headers": "BEAMS  COLUMNS  SECTIONS  Section Storage ", "Content": "The elements created via the Section discipline can be prioritized in two ways: In automatic via Grid Storage In manual via Manual StorageGrid Storage Structure: The sections will be automatically prioritized in a structure that will be created in relation to The associated \"Grid\" Storage Area (Frmw or Sbfr): Sections will be automatically prioritized in a framework or SubFRamework that will be created in relation to the associated \"Grid\" The elements created via the Section discipline can be prioritized in two ways: In automatic via Grid Storage In manual via Manual Storage Manual storage Structure: The sections will beStored in a Structure that will have been created manually by the user Storage Area (Frmw or Sbfr): The sections will be stored in a Framework or Sub-framework that has been Created manually by the user The Lock allows you to lock orNot the framework or Sub-Framework "}
{"Headers": "BEAMS  COLUMNS  SECTIONS  Specification ", "Content": "Specific menu: Selection of the classDefault selection of materials Selection of the justification Selection of the specification Selection of the type Selection of the profile Use of the current profile by default Profiles: Defined by 2 points and a specification modifiable at any time, the profiles have specific attachment points and Plines that are the edges of the profiles. "}
{"Headers": "BEAMS  COLUMNS  SECTIONS  Fitting ", "Content": "Allows you to create an assembly element (fitting). It can be used to represent any element that is attached to the structure but is not an integral part of it.Create > Fitting Step 1: Click to identify the section where the fitting will be placed Step 2: Select the specification and fitting Step 3: Graphically indicate the Pline where the fitting will be positioned Step 4: Move the fitting to the positionN desired on the previously selected pline "}
{"Headers": "BEAMS  COLUMNS  Modification of a profile  Bracing gaps", "Content": "Once the bracing has been created, it is possible to adjust the interval (Gaps) between the bracing and a reference element.Modify after Gaps Step 1 - Selection of the GENSEC composing the bracing (Yellow elements) Step 2 - Selection of the reference elements ( Cyan Elements) Step 3 - Modification of the Gap Gap: Distance between reference element and an element of the bracing The diDifferent bracing configurations: Diagonal Bracing Knee Bracing Cross Bracing Diamond Bracing K Bracing \u2022 Extend: Allows you to change the length of a Gensec in relation to a plan or panel. \u2022 Mitre Ends: Allows you to make a cut of the extremesIrons so that they are parallel to the bisector angle. \u2022 Daughter: Allows you to merge two irons to create a circular section \u2022 Merge: Allows you to make iron melts \u2022 Split: Allows you to make iron cuts in relation to an element\u2022 Splice: Allows you to make iron cuts compared to a plan \u2022 Fitting: Allows you to modify fitting specifications "}
{"Headers": "BEAMS  COLUMNS  Nodes and connections  Type of Knots ", "Content": "The creation of perm nodesAnd the connection of the elements between them. The installation of these connections makes it possible to quickly modify a frame, model the fasteners between irons and use some Design features. -Node for fixing with the GC (ENDATUM > FIXING)-Node for fixing metal frame / profile (JLDATU > PLDATU > FIXING) "}
{"Headers": "BEAMS  COLUMNS  Nodes and connections  Type of Knots ", "Content": "Fixing knot with the GC Selection of the End DATUM tool then selection of the END of a structural iron\u2022 Metal frame fixing knot profile Use the Connect tool then select the main iron, then the secondary section(s) to connect, then Esc then Complete the action "}
{"Headers": "BEAMS  COLUMNS  Nodes and connections  Representation of joints ", "Content": "Once the connections have been made, it is possible to show the type of fixation/preparation of the profiles by defining a specification at the Joint (Fixing). After selecting modify -> Joint 1-SelectR its section (always the main section). 2-Click on its joint 3-Press enter 4-Select the attached type 5-Make \"Apply\" "}
{"Headers": "BEAMS  COLUMNS  Nodes and connections  Subordinate Node and Dominant Node ", "Content": "By default, the connection nodes between irons are subordinate, i.e. the direction of the connected iron has priority On the position of the connection node. By making a dominant node, its position takes precedence over the direction of the connected iron, so when youRestores the connections, the irons are adapted in length and direction. "}
{"Headers": "DATA CONSISTENCY  VERIFICATION OF DATA CONSISTENCY  Data consistency  DIAGNOSTIC MESSAGES ", "Content": "This action makes it possible to checkIer the consistency of Piping & Structural data. CONSISTENCY CHECK DIAGNOSTIC MESSAGES A230 CONNECTION TYPE HCONN NOT SAME AS TERMINAL CONNECTION TYPE The FBD-FBD connection types in this example must be the same. B230 CONNECTION TYPE TCONN NOT SAME AS TERMINAL CONNECTION TYPE The GBD-GBD connection types in this example must be the same. D430 BAD ARRIVE CONNECTION TYPE The GBD-FBD connection types in this example must be a compatible combination in COCO tables.E730 LEAVE CONNECTION TYPE (of the Flange) NOT COMPATIBLE WITH TCONN The FBD-GBD connection types in this example must be a compatible combination in COCO tables "}
{"Headers": "DATA CONSISTENCY  VERIFICATION OF DATA CONSISTENCY  Data consistency  ERRORS ON THE BRANCH HEAD ", "Content": "A10 HEAD REFERENCE NOT SET The header reference can only be entered (e.g. zero) if the head connection (HCONN) is of type OPEN, CLOSED or DRAN.A200 DIRECTION HDIR NOT SAME AS TERMINAL DIRECTIONIf the head is connected to an object such as a stitch or tee, then the HDIR position should always be identical to that of the p-point Appropriate of the object. A210 POSITION HPOS NOT SAME AS TERMINAL DIRECTION If the head is connected to an object such as aStitching or a tee, then the HPOS position should always be identical to that of the p-point Appropriate of the object. A230 CONNECTION TYPE HCONN NOT SAME AS TERMINAL CONNECTION TYPE If the head is connected to an object such as a stitching or a tee, then the positionItion HCONN should always be identical to that of the p-point Appropriate of the object. A300 REFERENCE HSTUBE UNSET There is more than one mm of tube between the head and the p-arrive of the first component (or tail), but the HSTUBE is not filled in. A310 REFERENCE HSTUBE REFERS TO A NONEXISTENT IS SPCOM This can happen if part of the specification has been deleted. A320 HSTUBE PROBLEM, CATREF IN SPCOM UNSET This indicates an error in the specification. A330 HSTUBE PROBLEM, CATREF IN THE SPCOM REFERS TO NONEXISTENT Catalogue COMPONENTThis can happen if part of the catalog has been deleted or if the CATREF is not filled in. A400 HBORE NOT SAME AS BORE OF HSTUBE The diameter of any component of the head (determined from the catalog) must be identical to the diameter of the HBORE head.A410 HCON NOT COMPATIBLE WITH CONNECTION TYPE OF HSTUBE The connection of any component of the head (determined from the catalog) must be identical to the connection of the head HCON. A420 ISPEC REFERENCE POINTS TO NONEXISTENT ELEMENT This wanderingUr occurs if, for example, the heat retardant specification pointed out by the ISPEC attribute has been deleted A20 HEAD REFERENCE POINTS TO NONEXISTENT ELEMENT This error is the result of a deletion of an element, such as a stitch to which a branch was initially connected.A30 BAD HEAD RETURN REFERENCE The head is connected to an element that does not refer to the branch reciprocally. This can happen when the head of the branch is Connected to another branch, which assumes that a tee must be placed somewhere along the branch.The error can also be Produce when two or more branches are connected to the same object. "}
{"Headers": "DATA CONSISTENCY  VERIFICATION OF DATA CONSISTENCY  Data consistency  ERRORS ON THE TAIL AND BRANCH ", "Content": "B10 TAIL REFERENCE NOT SET The queue reference can be unfilled (e.g. zero) only if the queue connection (TCONN) is of type OPEN, VENT, CLOS or DRAN. "}
{"Headers": "DATA CONSISTENCY  VERIFICATION OF DATA CONSISTENCY  Data consistency  ERRORS ON THE ENTIRE BRANCH ", "Content": "\nC500 TUBE TOO SHORT BETWEEN HEAD AND TAIL\nThe distance between the head position (HPOS) and the tail position (TPOS) is greater than zero and less than the minimum accepted tube length (default: 100mm).\n\nC510 BAD HEAD TO TAIL GEOMETRY\nEither the head position (HPOS) is not at a positive distance along the line passing through TPOS in the direction of TDIR, or the tail position (TPOS) is not at a positive distance along the line passing through HPOS in the direction of HDIR.\n\nC520 HBORE NOT SAME AS TBORE\nWhen there are no components on the branch, the diameter of the head (HBORE) should ideally be identical to the tail diameter (TBORE).\n\nC530 HCONN IS NOT COMPATIBLE WITH TCONN\nThis means that the head is connected to the tail without a tube or pipe component between them, and therefore the head connection type (HCONN) must be compatible with the tail connection type (TCONN).\n\nC540 THIS BRANCH HAS NO COMPONENTS\nThis message does not necessarily indicate an error; it is just a warning.\n\nA410 HCON NOT COMPATIBLE WITH CONNECTION TYPE OF HSTUBE\nThe connection of any head component (determined from the catalog) must match the head connection (HCON).\n\nA420 ISPEC REFERENCE POINTS TO NONEXISTENT ELEMENT\nThis error occurs if, for example, the insulation specification pointed to by the ISPEC attribute has been deleted."}
{"Headers": "DATA CONSISTENCY  VERIFICATION OF DATA CONSISTENCY  Data consistency  DIAGNOSIS FOR ANY COMPONENT", "Content": "D100 REFERENCE SPREF UNSET This means that you probably forgot to choose the piping component correctly. D300 CONN REFERENCE NOT SET Multi-channel components can be left unconnected only if the type of conneXion of the p-point concerned is OPEN, VENT, DRAN or NULL. D310 CONN REFERENCE POINTS TO NON-EXISTENT BRANCH This can happen if the branch that is pointed to by CONN reference has been reconnected to another object. D400 ARRIVE TUBE LESS THAN TUBE MINIMUM. ACTUAL TUBE LENGTH IS...The distance between the arrival p-point of this component and the output p-point of the preceding component (or head) is greater than zero and less than the length of the minimum specified tube (default: 100mm) D410 BAD ARRIVE GEOMETRY The position and diRection of the p-point of arrival of this component is not correct vis-\u00e0-vis the p-point of exit of the previous component (or head). The error can be caused by incorrect positioning of this component, or the preceding component (or head) or both.D420 BAD ARRIVES BORE The diameter of the p-point of arrival of this component is different from the diameter of the preceding tube or, if this component is not preceded by the tube, from the diameter of the output p-point of the preceding component (or HBORE). DIAGNOSIS FOR N'IMPORTE WHICH COMPONENT D430 BAD ARRIVES connection TYPE The connection type of the p-end point of this component is not compatible with the preceding tube, or if this component is not preceded by the tube, with the connection type of the output p-point of the preceding component (or HCONN).D500 REFERENCE LSTUBE UNSET You probably forgot to select the D600 PIPE component LEAVE BORE NOT SAME AS BORE OF LSTUBE The diameter of the output p-point of this component is not the same as the diameter of the tube that follows the component.D610 LEAVE CONNECTION TYPE NOT COMPATIBLE WITH CONNECTION TYPE OF LSTUBE The connection type of the output p-point of this component is not compatible with the tube following the component. "}
{"Headers": "DATA CONSISTENCY  VERIFICATION OF DATA CONSISTENCY  Data consistency  DIAGNOSTICS SPECIFIC TO THE END COMPONENT ", "Content": "E700 LEAVE TUBE LESS THAN TUBE MINIMUM. ACTUAL LENGTH IS ... The distance between the output p-point of the current component and the position of the tail (TPOS), is greater than zero and less than theSpecified minimum tube length (default: 100mm) E710 BAD LEAVE GEOMETRY The position and direction of the p-point of this component is not correct with respect to the TPOS position, and the TDIR direction of the tail. The error can be caused by a positiIncorrect onnement of this component, the tail, or both. E720 LEAVE BORE NOT SAME AS TBORE The diameter of the output p-point of this component is not the same as that of the TBORE tail. DIAGNOSIS FOR ANY COMPONENT (CONTINUED) E730 LEAVE CONNECTION TYPE NOT COMPTAIBLE WITH TCONN The connection type of the output p-point of this component is not compatible with the TCONN queue. "}
{"Headers": "Draw  Introduction  What is draw?  What is draw? ", "Content": "AppealingTo MODEL databases, the DRAW module allows the processing of the elements of the 3D model in order to obtain a 2D plan In addition, this module allows the dressing of the generated plans, including Labels, Quotations, ..... DRAW databases allow the generation of these plans.All the information of the 3D graphic elements resides in the MODEL and CATALOGUE databases and cannot be modified from the DRAW module, These bases are only for reference. "}
{"Headers": "Draw  Draw  PRESENTATION OF THE DRAW ENVIRONMENT  DRAW database ", "Content": "DRAW databases allow the creation, modification and storage of plans. DRAW represents the \"paper space\" of the AVEVA E3D system and allows the processing of the 3D model in hidden lines, as well as the dressing ofGenerated plans (quotes, tracking, annotations,...) Treatment Of Lines Hidden The information, geometries reside in the MODEL (Design) and PARAGON(Catalogue) and cannot be modified under DRAW However, a permanent link eXiste between the 2 types of databases. "}
{"Headers": "Draw  Draw  PRESENTATION OF THE DRAW ENVIRONMENT  Draw explorer ", "Content": "Open: Display the sheet in the 2D view Attributes: Display attributes Rename: Rename the current itemDelete: Delete the current item Delete Members: Delete members of the current element Select Element: Make the current element active New Explorer: Show a new explorer For this element Copy: Copy (eg. Ctrl + C ) Paste: Paste (eg.Ctrl +V ) "}
{"Headers": "Draw  Draw  PRESENTATION OF THE DRAW ENVIRONMENT  Use of the mouse in the graphic view ", "Content": "RIGHT BUTTON: PowerWheel MIDDLE BUTTON: Mollette: Zoom In / OUT Button: Pan SIMPLE LEFT CLICK:-Selection of an element (View,Line, Text...) -Rectangle selection DOUBLE LEFT CLICK: Selection of the work area (View, Region or Sheet) NOTE: When creating view dressing elements, selecting a work area makes navigation unnecessaryTion and positioning in the DRAW Explorer. NOTE: The Navigator menu allows you to navigate between the different work areas of the Sheet NOTE: A second menu is accessible by combining a right click with the Crtl key  "}
{"Headers": "Draw  Draw  PRESENTATION OF THE DRAW ENVIRONMENT  Property Grid & Attributs ", "Content": "The modification of the attributes of an element is done using a window containing the main attributes of it. Type of elements chosen (filter in case of multiple selection)Properties (attributes) of the element(s) Description of the property (attributes) Single / multiple selection Element selection (in the 2D window) "}
{"Headers": "Draw  Draw  CREATION OF A PLAN BOOK  DRAWING (Plan notebook)", "Content": "It is strongly recommended to generate the plan books (DRWG) and folios (SHEE) according to a model predefined by the E3D system administrator. This allows the creation of homogeneous plans, and standardized by profession, here are some examples:It is possible to create a plan book without using a predefined template from the Create Explicitly Drawing menu under the TOOLS tab. In this case, the user must configure the plan book. This method is therefore not recommended."}
{"Headers": "Draw  Draw  CREATION OF A PLAN BOOK  Adding a SHEET (Folio) ", "Content": "From the HOME tab after New This option allows the addition of a SHEET according to the model chosen when creating the DRAWING It isAlso possible to create a SHEET from a predefined model from HOME > New > Drawing Type ( choose Sheet in the subset Drawing Types "}
{"Headers": "Draw  CREATION OF A PLAN BOOK  Modification of a SHEET (Folio)  Attributes and Cartridges ", "Content": "Modifying the attributes of a SHEET is done using the Property Grid: It is possible to change the format, cartridge, name and title of the Sheet, as well as Other attributes that could be usedS for filling the cartridge. "}
{"Headers": "Draw  CREATION OF A PLAN BOOK  Modification of a SHEET (Folio)  Update of the 2D display ", "Content": "From the UPDATE tab > ..., it is possible to update: - l2D display linked to DRAW element attributes or linked to the MODEL database UPDATE > Annotation - The representation of MODEL elements in a VIEW (2D view) UPDATE > Design - Update all elements related to the attributes of DRAW elements And theI\u00e9s to the representation of the elements of MODEL UPDATE > All - The image of the plan generated by DRAW (stored in the projPIC directory) UPDATE > Pictures - The background of the plan in reference UPDATE > Backing Sheet - All links external to the current element UPDATE > InstancesUPDATE > Refs UPDATE > Names "}
{"Headers": "Draw  CREATION OF A 2D VIEW  Tools for creating a VIEW (2D View)  From the Model Explorer", "Content": "From the MODEL Explorer, and via a right mouse click, the Quick View Creation option allows the creation A 2D plan view of the chosen MODEL element. Values can be incremented manually. The tab key on the keyboard PermAnd select the field and space to lock it The choice of the position and dimension of the created 2D view is then available in the 2D view window. By default, the choice of size and position is made by defining the diagonal (Specify the first corner...Then Specify the opposite Corner) It is possible to define this 2D space from the center, then the width and height of the 2D view by the down key on the keyboard and then select \"Center\" "}
{"Headers": "Draw  CREATION OF A 2D VIEW  Tools for creating a VIEW (2D View)  Home design ", "Content": "This option allows the creation of a 2D view from a 3D view inserted into the 2D space. This 2D space is defined in the same way as when creating a Quick View. This view 3D generated in 2D space has the following features: - Drag & Drop from the Model Explorer - Definition of the direction of the view, and the limits of the view, of the center of rotation of the view on a right click - The addition and removal of an eleMent of MODEL in the Drawlist with a right click on the element in the view or from the Model Explorer Once the following elements are defined: - Drawlist (MODEL elements displayed) - Direction of view The finalization of the view is carried out either: -DepuIs the 2D view key on the keyboard and then select From the Ribbon Bar A context menu specific to defining a 2D view from a 3D space is then available Apply........... Validation and update of the VIEW Finish. ........... Validation and update of the VIEW (identical)Cancel......... Cancellation of changes "}
{"Headers": "Draw  CREATION OF A 2D VIEW  Tools for creating a VIEW (2D View)  Projection ", "Content": "It is possible to make projected views from a previous orthogonal VIEWEnt defined, as described below: Plan view (North to bottom) The projection of this view (at Below) will be a view in North elevation of the view Original version N North elevation view (West to the right) The projection of this view (right) Will be a view in west elevation of the viewOriginal version West North elevation view (East on the left) The projection of this view (left) Will be a view in East elevation of the view Original version "}
{"Headers": "Draw  CREATION OF A 2D VIEW  Tools for creating a VIEW (2D View)  Region ", "Content": "A REGION, is a 2D space at a predefined scale in which it is possible to draw a set of elements, representing a detail Not being present in MODEL. The definition of the 2D space of the REGION, is carried out in the same way as the definition of a VIEWThe definition of the scale of this space is achieved by a keyboard input Once the space has been created, it is then possible to draw in 2D all the shapes available under the DRAW tab. DRAW The drawing opposite was drawn on a scale of 1:20 The platiNe (RECTANGLE) drawn is 40mm side (i.e. 40 x 20 = 800mm) The drawn holes (CIRCLE) have a diameter of 4mm (i.e. 4 x 20 = 80 mm) "}
{"Headers": "Draw  MODIFICATION OF A 2D VIEW  MODIFICATION OF A 2D VIEW  Modification of the 2D format", "Content": "When selecting a 2D view (VIEW), the VIEW Menu > 2D FORMAT appears. This menu allows you to modify the selected view. View / Section ) Representation Styles Modification of the type of representation of hidden lines and line processing rulesHidden and hatching Local Rules Management of user rules for processing hidden lines and hatching Drawlist Modification of the content of the lists of displayed items (Drawlist) Management of lists of displayed items (Drawlist) Update Update to jOr 2D view (graphic only) Creation of a projection, a detail view or a cutting plan from the current view Modify Modification of the 2D view from a 3D view (cf. 6.2.2 HOME > Design), Modifying the 2D view from the Limits Defined windowView or User-Defined View (PDMS method) Scale & Direction Adjustment of the 2D view scale Changing the direction and orientation of the 2D view "}
{"Headers": "Draw  MODIFICATION OF A 2D VIEW  MODIFICATION OF A 2D VIEW  Modification of the 3D format ", "Content": "When selecting a 2D view (VIEW), the VIEW Menu > 2D FORMAT appears. By selecting the Edit in 3D option The VIEW Menu > 3D FORMAT appears Manage Management of the Drawlist (list of items displayed) Displaying the Navigate DrawlistChoice of navigation mode and display mode of the 3D Scale & Direction view Adjustment of the 2D view scale Changing the direction and orientation of the 2D View Define Limits Management of 3D and 2D view display limits "}
{"Headers": "Draw  DRESSING OF PLANS DRESSING OF PLANS Status Bar ", "Content": "Graphical hanging options are available at the bottom right of the interface. Enable / disable orthogonal constraint (F8) Show the grid (F7)Enable / disable hanging on the grid (F9) Enable / disable the polar coordinate system (F10) Enable / disable the display of stroke thicknesses Adjust the graphic hook / Drawing grid Enable / disable the automatic update of VIEWEnable / disable the graying of inactive elements Activate / deactivate the degraded background Enable / disable object hanging (F3) Enable / disable advanced modification on dimensions, outlines and cutting planes Activate / disable the affDynamic ichage of length and angle information (F12) "}
{"Headers": "Draw  DRESSING OF PLANS DRESSING OF PLANS Graphic hanging ", "Content": "Grid Settings Grid On: Activation of the grid Insertion: Intersection of 2D surfaces onlyPerpendicular: 2D perpendicular projection only Tangent: Tangent point Nearest: Approached point Parallel: Parallel hook P-point: P-point (MODEL) P-Line End Point: P-Line End(MODEL) P-Line Mid Point: P-Line Mid Point (MODEL) Owner: Origin of the OWNER (MODEL)Grid Spacing: Grid display spacing Grid Snap: Activation of the hooking on the grid Grid Snap On: Hanging space on the grid Style: Grid display style Draw rulers: Display of rulers at the edge of paper spaceObject Snap Object Snaps: Activation of object snapping Project Snaps onto LCS: Activation of projected object hanging Distance snap: Activation of remote hooking View: Hanging assigned to VIEWs Sheet/Region: Hanging assigned to SHEET and REGIONEndpoint: Segment end Midpoint: Middle point of segment Center: Center Node: Nodes (MODEL) Quadrant: Quadrant point Intersection: Intersection of 2 segments Extension: End of 2D objects only "}
{"Headers": "Draw  DRESSING OF PLANS DRESSING OF PLANS Layers (Layer & Visual Layer)", "Content": "AVEVA E3D Draw, uses two types of elements to differentiate elements in different layers, these two types of layers, called LAYER and Visual LAYER (VLAYER), oHave very distinct properties. "}
{"Headers": "Draw  DRESSING OF PLANS Layers (Layer & Visual Layer) LAYER ", "Content": "LAYER-type elements are native to PDMS and not E3D. Allowing you to order 2D elements in aVIEW, they appear in the following form in the hierarchy: Each of these LAYERs has a PURPOSE attribute that allows you to define the function of each of them; for example, the PURPOSE attribute filled in DIMA, allows you to Define a quotation layer (DImensionning), a LAYER whose PURPOSE is entered in LABA, allows you to define an element tracking layer (Labelling) and A LAYER whose PURPOSE is entered at NOTA, allows you to define a layer of annotations (2D Draughting) For more informationNs see ADMIN > System Defaults > Layer Purpose Definitions... in Administrator session LAYERs are defined under the hierarchy of a VIEW and are totally linked to it (position of the elements, dimensions, scale,...) "}
{"Headers": "Draw  DRESSING OF PLANS Layers (Layer & Visual Layer) Visual LAYER ", "Content": "Elements of type VISUAL LAYER, belong to and are linked to the SHEET. Members of a VISUAL LAYER SET, they allow you to \"group\" the dressing of plans by category, and to define a formattingCommon to all the elements attached to this Home Layer The creation of a VISUAL LAYER is carried out from HOME > Visual Layer "}
{"Headers": "Draw  DRESSING OF PLANS Layers (Layer & Visual Layer) Visual STYLE", "Content": "Visual Styles are 2D representation styles that define colors, fonts, text height, line styles, etc., for each type of 2D element. These styles are accessible from ANNOTATE > Active Visual Style. Each Visual Style is predefined by the administrator, ensuring consistent graphical standards across all project plans. Note: The chosen style determines the properties of newly created elements, while modifying an element is done through the Properties window."}
{"Headers": "Draw  DRESSING OF PLANS Layers (Layer & Visual Layer) 2D and Visual LAYER elements ", "Content": "Each 2D element (drawing or annotation) can be assigned to a Visual LAYER. The assignment of an element to a Visual LAYER, allowsTo define its color, its line type as well as its display configuration and Of printing. When created, 2D elements are associated with the active Visual LAYER of the Active Properties window. Selection of the work area Selection of the Visual LAYERSelection of the type of line Color selection Assignment of the Visual LAYER and Properties to one or more 2D element(s) Identification of the Visual LAYER and Properties of a 2D element "}
{"Headers": "Draw  DRESSING OF PLANS Layers (Layer & Visual Layer) Creation ", "Content": "The quotation tools under ANNOTATE > Annotate, allow the realization of quotations under the Chained and Orthogonal Chained tools There are several types of quotations: - Orthogonal (orthogonal) - Aligned (aligned) Chained Orthogonal QuotationChained Aligned Quotation Orthogonal Quotation with Quotation Base on the left Orthogonal quotation with quotation base on the right Aligned Quotation with Quotation Base at the first point Offbeat Quotation with Quotation Base on the left Offbeat Quotation with Quotation Base on the rightOffbeat Quotation with Quotation Base at the first point The quotation can also be generated from 2D Space > Right click > Annotate > Orthogonal Chained "}
{"Headers": "Draw  DRESSING OF PLANS Quotations  Creation ", "Content": "The pointsTs of quotation are automatically generated when selecting a 2D or 3D object, attachments to 3D elements (cotation Associative) are indicated by a blue highlight. The cursor allows you to select several types of attachment: - Challenge pointNor by geographical coordinates (DPOI) Coordinates X Y Coordinates - Point associated with MODEL elements (DPPT) In the image opposite: Attachment to Ppoint 2 of the flange In this case, the element to which the quotation is attached appears in blue highlighted.- Point defined by the end, middle point, intersection, ... of a segment (DPOI) In the image opposite: Attachment to the midpoint of the segment "}
{"Headers": "Draw  DRESSING OF PLANS Quotations  Change ", "Content": "The modiFication of the points of a rib is carried out in 2D. The reallocation of existing points is carried out by selecting them with a left click and validating the New position by another left click. The modification of the textual information is carried out pAr a double click on the displayed text "}
{"Headers": "Draw  DRESSING OF PLANS Label  Label ", "Content": "The identification of MODEL elements is carried out by the creation of Label. These 2D elements attached to the 3D elements, can be under theIn the form of framed texts, or be formatted according to a predefined template by the system administrator. "}
{"Headers": "Draw  DRESSING OF PLANS Label  Type of Labels ", "Content": "General Label These Labels are simple benchmarks to set up entirely.Symbolic Label These Labels are benchmarks according to a model predefined by the system administrator "}
{"Headers": "Draw  DRESSING OF PLANS Label  Modification of a label (FORMAT - LABEL Tools menu) ", "Content": "Visual Style ModifyVisual style operator, this option allows you to change the Style of the selected General Labels and Symbolic Labels (According to the predefined models). Text Text modifier, this option allows you to change the formatting of the text part of the General Labels selected.Leader Reminder line modifier, this option allows you to modify the formatting of the Reminder line of the General Labels and Symbolic Labels selected. Frame Framing modifier, this option allows you to modify the formatting ofThe framework of the selected General Labels. Gaps Manager of the cache elements of the Lines leaders. "}
{"Headers": "Draw  DRESSING OF PLANS Label  Modification of a general label ", "Content": "General Labels During the seleCtion of the Label, it is possible to modify graphically, its position, orientation, attachment, as well as the setting in Form of the text. The formatting of the Leader Line and the Frame are managed from the FORMAT menu (LABELS TOOLS).The formatting of the text is most commonly carried out by a Double click on the General Label, giving access to the Text Editor "}
{"Headers": "Draw  DRESSING OF PLANS Label  Modification of a Smart Texts label ", "Content": "Smart textsGeneral Labels as well as Simple Texts (TEXP - Text Primitive), can use information from databases. Principle of intelligent texts #: key character for the search for an attribute (C2:5): Taking into account the attribute from character 2 to character 5(P1:3): Taking into account parts 1 to 3 of the attribute (name parts are delimited by the \"/\") Ex: Label on an elbow whose PIPE is named /BAT-001/PIPE/50-ERA-001 The code #PIPE(P3:3)(C2:) will give: 50-ERA-001 The code #PIPE(P3:)(C2:3) will give: 50The (C2:) allows you to eliminate the / at the beginning of the name; in the absence of an end character, the character string ends at the end of the name These intelligent texts can also be assigned to the projection text of the quotations (e.g. #SPREF(P2:)(C2:))To retrieve the specification of a profile On a rating between two beams or poles. "}
{"Headers": "Draw  DRESSING OF PLANS Label  Modification of a Symbolic Labels label ", "Content": "When selecting the Label, it is possibleBle to modify graphically, its position, orientation, attachment, as well as the scale of the associated symbol ( Template Reference - TMRF) The formatting of the callback line (Leader Line), is managed from the FORMAT menu (LABELS TOOLS). The betIn the form of the text cannot be modified on Symbolic Labels (managed by the system administrator) "}
{"Headers": "Draw  DRESSING OF PLANS Label  Symbols ", "Content": "Symbols accessible from ANNOTATE > Symbols are created asSymbolic Labels, referring to a 2D drawing model, alone Their position, orientation and size is modifiable. These elements do not have a callback line, but are attached to ELEMENTS of MODEL, and will be automatically replaced during theUpdate of a view for which the MODEL elements have been moved. "}
{"Headers": "Draw  DRESSING OF PLANS Label  Verification of links ", "Content": "When updating a view, it may happen that some elements of the habilLage are linked to model elements that no longer exist. These elements are then no longer visible, or no longer informed. The Clean Up Annotation tool allows you to remove all annotation elements that are no longer linked to 3D elements. ActivationOf the Model Ref Check allows a real-time visualization of the links of the elements Dressing: In green: the dressing elements in connection with the model In red: the dressing elements unrelated to the model "}
{"Headers": "Draw  DRESSING OF PLANS Label  2D drawing ", "Content": "From the DRAW Menu, a 2D interface is accessible to launch queries on the positioning and dimensions of the elements of the 2D space. This menu also allows the 2D drawing plot in the es2D pace to reproduce installation details not present in MODEL. It is also possible thanks to these tools to add 2D dressing to the plans in order to make fully finalized documents under DRAW. Measure Verification of dimensionsWe have 2D and 3D elements in 2D space Querying 3D element information (position, name, etc.) Draw 2D drawing Construct Construction line tools Modify Tools for editing 2D elements Multiple Copy (Array) This tool allows a copyR move to an array, i.e. the multiple copy of an element or a selection of elements with a step Defined. "}
{"Headers": "Draw  MANAGEMENT OF REVISIONS  Revision Control  Revision Control ", "Content": "AVEVA E3D integrates a tool ofE management of revisions, with which it is possible to compare revisions with each other. When creating the revision by clicking on, the system generates a Snapshot of the Sheet. For each revision, it is possible to fill in all the parametersIdentification of the people who have worked or verified the plan. For each revision, a REVI element is created and stored under the SHEET in the Draw Explorer. Depending on the configuration of the cartridge used, the information of the REVI can automaticallyFill in the cartridge revision table. "}
{"Headers": "Draw  EXTRACTION OF PLANS  EXTRACTION OF PLANS  Export ", "Content": "From the PROJECT > Export Menu, all the options defined by the system administrators are accessible."}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  The hierarchy", "Content": "Under the EQUIPMENT module, equipment modeling is conducted. This STOCKAGE entity is classified as an Equipment (EQUI). In AVEVA E3D, it comprises a collection of primitives grouped within the same EQUIPMENT, such as NOZZ, CYLI, and DISH."}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  Stall ", "Content": "Specific attributes: Xlength: Length(mm) on the X axis Ylength: Length(mm) on the Y axis Zlength: Length(mm) on the Z axis Position in the hierarchy: EQUI, SUBE, STRU, SUBSAccepted members: All negative elements "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  CYLINDER ", "Content": "Specific attributes: Height: Height (mm) Diameter: Diameter (mm)Position in the hierarchy: EQUI, SUBE, STRU, SUBS Accepted members: All negative elements "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  NOZZLE ", "Content": "Specific attributes:Height: Height (mm) Catref: Catalogue Reference Position in the hierarchy: EQUI, SUBE, STRU, SUBS Accepted members: No "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  CONE", "Content": "Specific attributes: Height: Height(mm) Dtop: Diameter at P1 Dbottom: Diameter at P2 Position in the hierarchy: EQUI, SUBE, STRU, SUBS Members accepted: All negative elements "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  SNOU ", "Content": "Specific attributes: Height: Height(mm) Dtop: Diameter at P1 Dbottom: Diameter at P2 Xoffset / Yoffset: offset on X/Y Position in the hierarchy: EQUI, SUBE, STRU, SUBSAccepted members: All negative elements "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  PYRAMID ", "Content": "Specific attributes: Height: Height (mm) Xtop/Ytop: Dimension X/YTo P1 Xbot/Ybot: Dimension X/Y to P2 Xoffset / Yoffset: offset on X/Y Position in the hierarchy: EQUI, SUBE, STRU, SUBS Members accepted: All negative elements "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  RTORUS (Rectangular Torus) ", "Content": "Specific attributes: Height: Height(mm) Rinside: Inner radius Routside: Outer radius Angle: Angle Position in the hierarchy: EQUI, SUBE, STRU, SUBS Accepted members: All negative elements "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  CTORUS (Circular Torus) ", "Content": "Specific attributes: Rinside: Interior radius Routside: Outside radius Angle: Angle The diameter is defined byThe difference between ROUT and RINS Position in the hierarchy: EQUI, SUBE, STRU, SUBS Accepted members: All negative elements "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  DISH (Bombed ground)", "Content": "Specific attributes: Diameter: Diameter Height: Height Radius: Radius Position in the hierarchy: EQUI, SUBE, STRU, SUBS Accepted members: All negative elements "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  Sloped Cylinder (SLCY) ", "Content": "Specific attributes: Height: Height (mm) Position in the hierarchy: EQUI, SUBE, STRU, SUBS Accepted members: All negative elements Diameter: Diameter (mm) Angle: Angle"}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  Extrusion (EXTR) ", "Content": "Specific attributes: Height: Height(mm) Position in the hierarchy: EQUI, SUBE, STRU, SUBS Accepted members:All negative elements "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT APPLICATION  PRINCIPLE OF MODELING OF AN EQUIPMENT  Solid of Revolution (REVO) ", "Content": "Specific attributes: Angle: Angle Position in the hierarchy: EQUI, SUBE, STRU, SUBSAccepted members: All negative elements "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT CREATION  EQUIPMENT CREATION  Creation of the EQUI element ", "Content": "Equipment creation after click on OK "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT CREATION  Creation of a primitive Choice of the mode of creation ", "Content": "Once the primitive type has been selected, press the bottom arrow on the keyboard to select a primitive creation mode. TwoPoints: Creation of a primitive with 2 specific points (first and opposite corners) Three points: Creation of a primitive with 3 specific points (First, opposite and height) Four points: Creation of a primitive with 4 specific points (Origin, X, Y and Z)Explicit: Creation of a primitive from the center by defining length, width and height "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT CREATION  Creation of a primitive Example of creation of the primitive ", "Content": "Step1: Choice of the type of primitive Step 2: Definition of the base point Step 3: Definition of the opposite point in the diagonal Step 4: Definition of the height of the box "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT CREATION  Creation of a primitive Sub-Equipment ", "Content": "A Sub-equipment (SUBE), is a sub-assembly of equipment. It is a graphic group whose display can be managed Regardless of the equipment. It is most often used to dissociate several partiesAre of the same equipment (e.g. a motor, feet, a chassis, etc.) "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT CREATION  Sub-Equipment  Change the origin of an Equipment / Sub-Equipment ", "Content": "ID Point: Placement of the oriGine to a P-point designated on the screen (it is possible to create a temporary primitive to place the origin of the equipment or sub-equipment. Explicit...: Displacement of the origin in one or more direction(s) In both cases a confirmation messageAtion/cancellation will be proposed to you (Return to the original origin YES: Cancellation NO: Confirmation of the action) "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT CREATION  Sub-Equipment  Standard equipment ", "Content": "The eqStandard equipment are equipment created using a configurable template. They can be modified after their creation. Note: The Modify Properties window allows you to fill in the configurable dimensions of Standard equipment. We find there atUssi a \"Plotfile\" plan, which informs the dimensions Configurable. "}
{"Headers": "EQUIPMENT APPLICATION  LEVEL OF REPRESENTATION AND OBSTRUCTION  Level of representation  Level of representation ", "Content": "Each primitive of theThe model is defined by a level of representation. It allows you to define the level of detail To which the primitive corresponds. There are several levels of representation: \u2022Level 0-3: Summary representation. \u2022Level 4-6: Detailed representation. \u2022NiCalf 7-10: Very detailed representation. \u2022Level 9-10: Representation of the volumes of obstructions and reservations. The definition of the level of representation of an equipment primitive is carried out when it is created. "}
{"Headers": "EQUIPMENT APPLICATION  LEVEL OF REPRESENTATION AND OBSTRUCTION  Level of obstruction  Level of obstruction ", "Content": "Each primitive of the model is defined by a level of obstruction. There are three levels of obstruction \u2022Level 0: Clash none.Primitives are not taken into account in the Clasher \u2022Level 1: Clash soft. Possibility to choose whether primitives are taken into account or not in the Clasher \u2022Level 2: Hard clash. Primitives are always taken into account in the ClasherTo limit the calculation times of the Clasher it is advisable to create the primitives of an EQUI with an obstruction level 0 (image 1), and to create An obstruction level 2 primitive (image 2), which encompasses the total volume of the pump. "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT ASSOCIATION  Creation of an association  Creation of an association ", "Content": "Rules for the association between equipment can be defined by the user. These rules allow a verification of the positioning of equipment.These rules are defined by a positioning constraint between 2 elements. At the end of the design, the user can check the state of these rules in order to validate the positioning of the elements. Associations are managed in a specific hierarchyThat, Available from the Associate Browser window "}
{"Headers": "EQUIPMENT APPLICATION  EQUIPMENT ASSOCIATION  Verification of associations  Verification of associations ", "Content": "The rules of association can be consulted from the Association Manager.It allows you to check the status of the existing rules (Passed / Failed), and the criteria for them: -Type of association -Distance A summary table of the elements constituting the association is also presented. "}
{"Headers": "ISODRAFT  THE ATTACHMENTS  Their functions Their functions", "Content": "Attachments are created in the same way as a piping component. They are used for various applications. We will detail the main ones.\n\nThe different types of ATTA are defined by setting the ATTY attribute.\n\n\u2022 ATTY Unset: Default type. It is used to mark the position of a support on the piping in the isometric.\n\n\u2022 ATTY CCCC: Allows you to add a note with a leader line on the isometric. The attachment will also be dimensioned (referred to as a dimensioned comment).\n\n\u2022 ATTY CCNN: Allows you to add a note with a leader line on the isometric. In this case, the attachment will not be dimensioned (referred to as an undimensioned comment).\n\n\u2022 ATTY Flow: Adds an arrow to indicate the direction of fluid flow on the isometric.\n\n\u2022 ATTY XXXX: Splits the piping line. This option is used if you want to break your isometric to make it easier to read.\n\n\u2022 ATTY SSSS: Defines the point from which an isometric should be divided on the next sheet. The same considerations apply as for an ATTY SSSS.\n\n\u2022 ATTY INPP: Defines the beginning and end points of insulation on an isometric.\n\nIf you want to add a comment to the attachment (in the case of CCCC or CCNN), you need to fill in the Stext attribute of the attachment."}
{"Headers": "ISODRAFT  THE ATTACHMENTS  Isometric Design  Isometric Design ", "Content": "It is possible to pre-visualize the isometrics of the Piping discipline with the isometric Pipe function "}
{"Headers": "ISODRAFT  THE ATTACHMENTS  The Isodraft module  The Isodraft module ", "Content": "You can access the Isodraft module by selecting Project > Modules > Isodraft... Once in the module, you can display the Model Explorer. CEci allows you to display Design databases. To produce an Isometric, select in the Model Explorer, the line or branch for which you want to create the Isometric. CE button: allows you to re-select a branch or Pipe using the Model Explorer.Option: allows you to choose the rules defined by the administrator, depending on the option chosen, you have several choices in the window Standard iso options, for example in our case, the Project option uses the FTN.MET rule (to take the Iso into a metric unit)Detail: Allows you to select the branches of a line, if you want to exit only part of the selected piping line. Produce: allows you to generate: - Transfer File: transfer file for use with other software - Batch MAcro: allows you to take out a large amount of isometric. - Bolt Report: allows you to take a bolt report out of the piping line "}
{"Headers": "ISODRAFT  THE ATTACHMENTS  Specific configurations  Specific configurations ", "Content": "In order to improve the readability of an isometric or to provide additional clarification, the user can perform several operations on Pipes and pipe components: - Use of attachments - Information on the names of valves, instruments.... - Quotation of an element in relation to irons or rows Dmtype: NORT EAST ELEV POS Dmfarray 1 /Name of the element 2 /... - Exclusion of items from the material list (MTOC, MTOT, MTOH attributes) - ON: Includes the components in the material list and draws them normally- OFF: Excludes components from the material list and draws them normally - DOTD: Excludes the components of the material list, draws them in dotted and dimensions - DOTU: Excludes components from the list of equipment, draws them in poiNtill\u00e9s and do not size them "}
{"Headers": "LASER APPLICATION  Introduction  What is laser application?  What is the laser reading? ", "Content": "Recent developments in computer techniques and tools have made theLasergrammetry (recorded by 3D laser scanner) essential for the realization of TQC models (as built), the industrial installation survey for revamping studies... The advantages of this technology are multiple: time saving, pCircumcision, minimization of the risk of exposure in dangerous environments, 3D modeling... A laser scanner scans the surrounding space and collects millions of points thanks to its laser beam. A device can generate up to 1 million points per secondOf (each point being a measure in space, in 3D). A cloud of points can thus be generated in a few minutes and represent the environment accurately recorded. In order to obtain a complete model, it is necessary to make several stations ofE survey and compile all the point clouds obtained. "}
{"Headers": "LASER APPLICATION  IMPORT UNDER E3D  Preparation of the point cloud  Preparation of the point cloud ", "Content": "Before it can be operated under AVEVA E3D,The data extracted from the 3D laser scanners must be compiled by the AVEVA LFM Server software. "}
{"Headers": "LASER APPLICATION  IMPORT UNDER E3D  Import of the point cloud  Import of the point cloud ", "Content": "You have to be admIllustrator of the E3D2 project to import a point cloud The import of a point cloud is done from the ADMIN tab > LASER ACCESS > CREATE LASER MODEL Following the import, an XGEOM element is then created in the AVEVA E3D2 databases, it is visible in the Model Explorer.In the same way as any element of AVEVA E3D2, the point cloud can be displayed in the 3D view. "}
{"Headers": "LASER APPLICATION  DISPLAY OF A POINT CLOUD  BubbleView  BubbleView ", "Content": "You have to be administeredAtor of the E3D2 project to import a point cloud The import of a point cloud is done from the ADMIN > LASER ACCESS > CREATE LASER MODEL tab Following the import, an XGEOM element is then created in the AVEVA E3D2 databases, it is visible in the Model Explorer.In the same way as any element of AVEVA E3D2, the point cloud can be displayed in the 3D view. From the Available Bubble views window or by graphically identifying a reading station via the Pick option, it is possible to switchThe 3D window in \"Bubble View\" mode The simultaneous display of a cloud of Points and 3D elements can allow A verification of the consistency of the 3D model and laser model. From this mode of viewing, The user can change stations from RelReference eve in order to move In the 3D model. The icon allows you to leave the \"Bubble View\" mode. "}
{"Headers": "LASER APPLICATION  DISPLAY OF A POINT CLOUD  HyperBubble  HyperBubble ", "Content": "The HyperBubble tool allowsTo the user to work in an environment such as built fully immersed. The user is able to walk away from the scanner's position, move freely around the point cloud data in any direction. The HyperBubble is not available by default with the point cloud. To be able to use it, it must be created with the \"LFM Server\" software Once the HyperBubble is activated in Model (View > Laser > HyperBubble), use the \"Walk Mode\" or \"Fly MOde\" to navigate the point cloud. Walk Mode: Navigate the model as if you were walking in the model. Use the \"Space\" key on the keyboard to refocus the Fly Mode view: Navigate the model as in a flight simulator. CUse the \"F2\" key on the keyboard to show/hide the internal E3D windows (Model Explorer, Property grid etc...) "}
{"Headers": "LASER APPLICATION  DISPLAY OF A POINT CLOUD  Density of points  Display Option ", "Content": "By dEfault, point clouds are represented with a low point density so as not to overload the software with data. From the Display Options tool, it is possible to define a volume and act on the density of the point cloud inside it.The volume must be defined via the \"CE Volume\" or \"Pick Volume\" options. Once the volume has been created, it is possible to modify it by double clicking graphically on the volume and using the graphic modification handles. The Display Re optionSet: Allows you to hide the volume The Edge Mode option: Allows you to optimize the edges of the reading to increase visibility (Passage in grayscale) The Low density option: Allows you to hide areas of the point cloud where the density is low "}
{"Headers": "LASER APPLICATION  DISPLAY OF A POINT CLOUD  Density of points  Area ", "Content": "Thanks to an AREA, it is possible to define a volume and act on the density of the point cloud inside it. The volume may be more complex (Circular, pyramidal etc...) that a volume made with the Display Mode option and it will be saved in a project database via an Area Definition. 1 - Creation of an Area WORLD at the same level as a SITE in the Model Explorer ( GENERAL > AREA > WOLRD ) 2 - Creation of aArea SET ( GENERAL > AREA > SET ) 3 - Creation of an Area DEFINITION ( GENERAL > AREA > DEFINITION ) 4 - In the DEFINITION area, model primitives to define the limits of the volume to increase the density of points "}
{"Headers": "LASER APPLICATION  LASER DEMOLITION  Demolition Demolition", "Content": "In AVEVA E3D, it is possible to demolish a part of a point cloud.\n\n1 - Create a Demolition WORLD at the same level as a SITE in the Model Explorer (GENERAL > LASER DEMOLITION > WORLD)\n2 - Create a Demolition SET (GENERAL > LASER DEMOLITION > SET)\n3 - Create a Demolition PACKAGE (GENERAL > LASER DEMOLITION > PACKAGE)\n4 - In the Demolition PACKAGE, model primitives to define the boundaries of the volume of the area to be demolished in the point cloud.\n5 - Once the volume is defined, click on \"READY\" then \"DEMOLITION\" to demolish the desired area in the point cloud. To redisplay the demolished area, click again on \"DEMOLITION\". The BROWER option allows displaying a secondary hierarchy listing all the demolished elements in the point cloud of the project."}
{"Headers": "LASER APPLICATION  MODELING Measuring tool  Measuring tool ", "Content": "The use of the measurement tool requires a graphic selection. The Positioning dialog boxControl allows you to configure the type of hook on the elements of the graphic view. To take measurements in relation to a point cloud, you must select the type of hook \"LASER data\" By default, the measurement is broken down into 3 axial dimensions (East, North and Up).The results are displayed in the Measure window and in the graphic view. It is possible to obtain only a horizontal dimension and a vertical dimension by activating the Perpendicular to option. The Show linear dimension option allows the display of direct measurement in the graphic view.The Unit Type drop-down menu allows you to select the unit in which the result is to be presented. "}
{"Headers": "LASER APPLICATION  MODELING Piping  Piping ", "Content": "When creating a pipe and defining theHEAD and TAIL, it is possible to automatically retrieve a position and a diameter. Select the Pick branch in laser data option, then click on a pipe in the laser reading to retrieve the position and diameter of the pipe. This optIon is valid for the HEAD and TAIL Useful options: Nudge option allows you to move the head or tail along the axis of the pipe Option Opposite Direction allows you to reverse the direction of the head or tail "}
{"Headers": "LASER APPLICATION  MODELING Clasher  Clasher ", "Content": "The clasher tool can be used to check the clashes between the new modeling made in MODEL and the point cloud. To check the clashes with the point cloud, you must add the XGEOM inS the list of elements of obstructions. "}
{"Headers": "LASER APPLICATION  DRAW  Laser in Draw  Display of the point cloud ", "Content": "E3D 2 allows the insertion of a point cloud into a 2D plan in the DRAW To insert aPoint cloud in DRAW, you must add the XGEOM of the point cloud in the drawlist of the view. Once the XGEOM is in the drawlist, a \"Laser Volume Representation Set\" (LAVOST) must be created via the Display tool. This element of Representation will be assOci\u00e9 to Area definition (AREADE) or demolition Package (DEMOPA). First, DRAW checks if the view is linked to a \"laser volume representation set\", if this Is not the case, a window opens to create a new laser volume representation.A laser volume representation is stored in the Library of the sheet and can be used by several Views. Once the laser volume representation is created, it must be linked to it one or more Area Definition or/and one or Several demolition package "}
{"Headers": "LASER APPLICATION  DRAW  Laser in Draw  Quotation and dressing of the plan ", "Content": "After inserting a point cloud in a view it is possible to create quotations and annotations in relation to this point cloud. For this he fAut adjust the graphic hooking on Laser, in order to select laser points. "}
{"Headers": "PANELS  PLATES  PANELS AND PLATES Specification ", "Content": "Specific menu: Thickness of the panels Selection of the type of beam desired Specification of panelsSelection of materials for the panels Representation of the aretes Standard Plate: Smooth sheet metal Chequer Plate: Tear tin Standard Grating: Grating Each of these specifications Has a thickness range Clean Panel (PANE) It is defined by at least 3 vertex (PAVE), aSpecification or a thickness and justification. 1 "}
{"Headers": "PANELS  PLATES  PANELS AND PLATES Creation of panels ", "Content": "Under a FRAMEWORK (FRMW) or a SUBFRAMEWORK (SBFR), if the default hierarchies have not been rTaught: For the creation of a panel, simply select graphically or manually enter the coordinates of the points. There are several options when creating a panel: FILLET: allows you to create a leave at a point of the panel ARC: permAnd create a rounded side JUSTIFICATION: allows you to choose between top, bottom or center for the creation of the BACK panel: return to the previous point FINISH: complete the creation of the panel "}
{"Headers": "PANELS  PLATES  PANELS AND PLATES Modification of panels ", "Content": "After creating a profile, it is possible to edit it at any time: Specification: allows you to change the thickness of a panel with specification - Thickness: allows you to change the thickness of a panel without specification- Justification: allows you to modify the justification of the panel (Top, Center, Bottom) - Panel Origin: allows you to move the origin of the panel - Representation: allows you to modify the representation and level of obstruction of the panel - Drawing Edges: allows you toE modify the representation of the edges - Offset: allows you to modify the dimension of the panel - Split: allows you to section the panel by an element or plane - Merge: allows you to merge several panels "}
{"Headers": "PANELS  PLATES  PANELS AND PLATES Opening creation ", "Content": "The Negative Extrusion creation tool allows you to create specific openings "}
{"Headers": "PANELS  PLATES  PANELS AND PLATES Accessories for Panel ", "Content": "Specification: allows you to choose the desired type of accessory.Fitting group: displays the possible types for the current element (GTYPE) Fitting: allows you to choose the subtype of accessories (for example, a particular style, or a gusset thickness). Design Parameters: Allows you to modify the attributes of the selected fitting."}
{"Headers": "PIPING APPLICATION  Pipe  MODELING OF PIPING LINES  The basics ", "Content": "This module allows you to create all the piping elements. "}
{"Headers": "PIPING APPLICATION  Pipe  MODELING OF PIPING LINES  The branches ", "Content": "The Branches have two functions: 1. Define the start and finish points of a section of piping (Head/Tail) 2. Contain Head/Tail piping components:They define a position, direction and start or end diameter of the Piping. AVEVA E3D allows you to connect these points to elements such as tees, Nozzles, other branches, etc... and automatically retrieve the information NecessaryComponents: They define the passage of the piping, their order must remain the sense of the fluid! Thus, if two components are aligned, correctly oriented, and Of the same diameter, AVEVA E3D will automatically generate the tube between these 2 components "}
{"Headers": "PIPING APPLICATION  Pipe  MODELING OF PIPING LINES  Configuration of Tools ", "Content": "The Piping Settings window allows the configuration of the default values of piping creation tools. Project > Options> Discipline > Piping > Piping Application Defaults "}
{"Headers": "PIPING APPLICATION  Pipe  MODELING OF PIPING LINES  Creation of a Pipe ", "Content": "When creating a piping line, it It is mandatory to specify a line name andA piping specification. Possibly, it is also possible to Fill in the main DN, the specifications Tracing and heat insulation, temperature and The pressure of the line. If the piping line must be modeled With a slope, the value of it can beSpecified. Once the creation of the Pipe has been validated, the window Pipe Editor evolves and allows the creation and Definition of the Head/Tail of a Branch. "}
{"Headers": "PIPING APPLICATION  Pipe  MODELING OF PIPING LINES  Creation of a branch", "Content": "The icon allows you to link the dialog box to your current item. Modification of the pipe attributes Modification of the attributes of the Highway branch branch: Modeling of the pipeline line in automatic. Creation of a new branCh in the current pipe Allows you to open the piping component creation window "}
{"Headers": "PIPING APPLICATION  Pipe  MODELING OF PIPING LINES  Creation of components ", "Content": "Choice of Specifications (Piping/Heating/Tracing)Allows you to choose the specifications of the components to be created (Beware of spec changes they are visible on the Isometric). NOTE: The Auto-Create option allows the automatic creation of the components necessary to mount the created component (e.g. Flange, Gask)Choice of component type Choice and configuration of the component Choosing the type of item to be created, check your position in the Hierarchy, and meaning (forward/backward) Creation/Placement of the component Choose the item to create, check your position in the hierarchy, andThe meaning (forward/backward) The component can be created directly upstream or in Downstream of the current element (CE), or placed on a length Pipe line. "}
{"Headers": "PIPING APPLICATION  Pipe  Installation of a component Use of Piping Component Editor tools ", "Content": "Position Through: Positions the component on the head of the branch Moves the component to align it to the previous Align the component to the previousMove the component to align it to the next Position the component on the tail of the branch Aligns the component to a graphic selection Copy of the current element Connects the current element to the previous element 1.7. Installation of a component 1.MODELING OF PIPING LINES 1.7.1. Use of Piping Component Editor tools: NOTE: Modification tools are dependent on the direction of creation (FORWARDS / BACKWARDS) "}
{"Headers": "PIPING APPLICATION  Pipe  Installation of a component Use of the Model Editor: General ", "Content": "Each piping component can be moved and oriented with the Model Editor: The components connected to each other (excluding elbows) are considered a group. It is possible to move theGroups on sections of blue highlighted piping (the update of the hierarchy is automatic) From the context menu of a component, the options in the Select menu allow a selection ranging from all the components of the Pipe to the current component.A fast path mode is activated by clicking on the elastic of the branch. It makes it possible to create an elbow when changing direction. "}
{"Headers": "PIPING APPLICATION  Pipe  Installation of a component Using the Model Editor: Contextual Menus", "Content": "Enter Offset...: allows you to enter a value of the offset from the current position in the direction of the current path. Enter Distance From: allows you to enter the absolute value between the handle and the connection point, the compo originHealth or the preceding or following change of direction. Align with Feature ...: allows you to align with an edge or point identified on the screen. Offset From Feature...: allows you to align with a offset at an edge or a point identified on the screen. Connect: allows you to connect the selection to the previous or next component. Move Handle: move the handle to one end of the selected group. Distance Feedback: allows you to choose how the routing handle graphically displays the distance. FrOm Arrive/Leave (distance from the connection point of the preceding or next component), From Origin (distance from the handle from the position of the origin of the change of direction), From Direction Change (Distance from the origin of the cha componentDirection), From Current Position (relative distance from the original position). ID PRESENTATION FLOW ARROWS: graphical help for the representation of fluid sense.Enter Offset...: allows you to enter a value of the offset from the current position in theDirection of the ongoing path. Enter Leg Length...: allows you to enter the absolute distance between the handle and the last Direction change component. Distance From Origin...: allows you to enter the absolute value between the handle and the position at The origin of the previous component.Extend Through Feature...: allows you to indicate on the screen an edge or a point on which you Want to align yourself. Offset From Feature...: allows you to align with a offset at an identified edge or point On the screen. No Slope / slope Angle: indication of the slope angleOrient To Point...: allows you to orient the handle towards the indicated point. Align with Direction...: allows you to indicate on the screen an edge or a point with which to align The handle. Explicit Direction...: allows you to explicitly enter the new direction of the handle.Component Choice: allows you to choose the type of component that will be created by the handle of Routing when a change of direction occurs. The component can be either an elbow, Or a bending. Distance Feedback: allows you to choose how the routing handle displaysGraphically the distance. Offset (offset from the previous position of the handle), Leg Length (distance from the handle from the position of the last change of direction), Or From Origin (distance from the handle from the position of the origin of the change ofDirection. Show Rotation Handles: allows you to display or not the rotation handles (hided by default). "}
{"Headers": "PIPING APPLICATION  Pipe  Installation of a component Using the Model Editor: Alignment ", "Content": "By selecting the point...The elbow is placed perpendicular to the axis of travel passing through the point. By selecting the arrow... The elbow aligns with the plane defined by the direction of the arrow. "}
{"Headers": "PIPING APPLICATION  Pipe  Installation of a component Slope management ", "Content": "When creating a pipe, it is possible to specify the value of the slope of the pipe. This menu allows you to apply the slope on all the elements of the branch Allows you to apply on the branch a slope veRs the bottom Allows to apply on the branch a slope upwards Do not apply a slope on the branch NOTE: The slope can be applied only has certain elements of piping "}
{"Headers": "PIPING APPLICATION  Pipe  MODIFICATION OF PIPING LINES Modification of a pipe ", "Content": "The editing of a pipe or branch can be done at any time with the tools in the Modify Pipe dialog box (see 1.4. Creation of Pipe). "}
{"Headers": "PIPING APPLICATION  MODIFICATION OF PIPING LINES MODIFICATION OF PIPING LINES Component modification ", "Content": "All piping components can be moved and redirected with the tools in the Modify Component window (see 1.7. Installation of a component). The Model EditGold can also be used to modify a component. "}
{"Headers": "PIPING APPLICATION  Pipe  MODIFICATION OF PIPING LINES Reselection of components ", "Content": "When a component already created must be replaced by another coMposing of the same type, it is possible to reselect it. The Reconnection function automatically moves the connected elements to the original one, so that they are always connected to the new component. "}
{"Headers": "PIPING APPLICATION  Pipe  MODIFICATION OF PIPING LINES Change of specification ", "Content": "The Modify Components dialog box can be used to change the specifications of piping, heat insulation, tracing and also to change the diameter of the components.To access it: -Modify > Spec / Bore By using the right mouse click in the dialog box you bring up the context menu. Modify Specification: allows you to modify the specification of the selected component(s) Modify BorE: allows you to modify the diameter of the selected component(s) Modify Insulation Spec: allows you to modify the heat retardant specification of the selected component(s) Modify Tracing Spec: allows you to modify the tracing specification ofU or selected component(s) Select Component: allows a re-selection of the Select All component: allows you to select all the components present in the dialog box. Clear New Specification: allows you to clear the new specificationsThat you have given on all the elements or on those you will select. Export to Excel...: exports the table in Excel Print Preview format: allows the table to be printed in PDF or on paper "}
{"Headers": "PIPING APPLICATION  Pipe  MODIFICATION OF PIPING LINES Removal of components ", "Content": "Piping components, like all E3D elements, can be deleted by the Delete tools. This option is also available in the component's context menu in the Model Explorer.In the Piping discipline, the Delete Range tool allows you to remove all the components of a section of piping located between 2 user-defined components: "}
{"Headers": "PIPING APPLICATION  Pipe  MODIFICATION OF PIPING LINES Pipe line cutting ", "Content": "Cutting a line can be useful to make an isometric clearer or to meet a process need. Split Pipes on a Plane: This mode allows the cutting of one or more lines by a user-defined plan.The elements downstream of the section are moved into an identified branch (Existing), into a new pipe (New Pipe) or a new branch (New Branch). From the Assembly tab, the user can choose a typical assembly to insert on the cut.Split Pipes into Segments: This mode allows the cutting of a pipeline line into sections of defined lengths between 2 identified components. Each section can be created in a new branch or a new pipe.Split Pipes by moving Components:This mode allows the cutting of a piping line on a selected component. The elements located downstream of the section are moved into an identified branch (Existing), in a New pipe (New Pipe) or a new branch (New Branch). Merge Branch / pipe:This mode allows the fusion of 2 branches or 2 pipes. NOTE: it is strongly recommended to initiate a data consistency check when you modify a piping. "}
{"Headers": "PIPING APPLICATION  Pipe  MODIFICATION OF PIPING LINES Slope management ", "Content": "When a piping line has been modeled without a slope, it is possible to generate a slope on the entire line or on only one section: Slope management on the entire Pipe Choice of the section ofWork Management of the slope on the current section "}
{"Headers": "PIPING APPLICATION  Pipe  THE ATTACHMENTS  Their functions", "Content": "Attachments are created in the same way as a piping component. They are used for various applications. Let's detail the main ones. The different types of ATTA are defined by setting the attribute ATTY.\n\n- ATTY Unset: default type. It is used to mark the position of a support on the piping in the isometric.\n- ATTY CCCC: allows adding a note with a reference line on the isometric. The attachment will also be sided (called a sided comment).\n- ATTY CCNN: allows adding a note with a reference line on the isometric. In this case, the attachment will not be sided (called a non-sided comment).\n- ATTY Flow: allows adding an arrow to indicate the direction of the fluid on the isometric.\n- ATTY XXXX: allows splitting the piping line. This option is used if you want to cut your isometric to facilitate its reading.\n- ATTY SSSS: allows defining the point from which an isometric should be divided on the next sheet. These are the same considerations as for an ATTY SSSS.\n- ATTY INPP: allows defining the beginning and end points of insulation on an isometric. If you want to add a comment to the attachment (in the case of a CCCC or CCNN), you must fill in the Stext attribute of the attachment."}
{"Headers": "PIPING APPLICATION  Pipe  ISOMETRIC PRODUCTION  Isometric Design ", "Content": "It is possible to pre-visualise the isometrics of the Piping discipline with the foNction Isometric pipe: NOTE: The plot of the isometric is in white, do not pass the background in white. Otherwise you will no longer see your isometric. The context menu has an option to change the background color. "}
{"Headers": "PIPING APPLICATION  Pipe  ISOMETRIC PRODUCTION  The Isodraft module ", "Content": "You can access the Isodraft module by selecting Project > Modules > Isodraft... Once in the module, you can display the Model Explorer. This allows youTo display Design databases. To produce an Isometric, select in the Model Explorer, the line or branch for which you want to create the Isometric. CE button: allows you to re-select a branch or Pipe using the Model Explorer.Option: allows you to choose the rules defined by the administrator, depending on the option chosen, you have several choices in the Standard iso options window, for example in our case, the Project option uses the FTN.MET rule (to exit theEs Iso in metric unit) Detail: Allows you to select the branches of a line, if you want to exit only part of the selected piping line. Produce: allows you to generate: - Transfer File: transfer file for use withOther software - Batch Macro: allows you to take out a large amount of isometric. - Bolt Report: allows you to take out a bolting report from the piping line. "}
{"Headers": "PIPING APPLICATION  Pipe  ISOMETRIC PRODUCTION  Specific configurations ", "Content": "In order to improve the readability of an isometric or to provide additional clarification, the user can carry out several operations on pipes and pipe components: - Use of fastenersMents - Information of the names of valves, instruments .... - Quotation of an element in relation to irons or files Dmtype: NORT EAST ELEV POS Dmfarray 1 / Name of the element 2 /... - Exclusion of elements from the list of equipment (attributes MTOC, MTOT, MTOH)- ON: Includes the components in the material list and draws them normally - OFF: Excludes the components from the material list and draws them normally - DOTD: Excludes the components of the material list, draws them in dotted and dimensionsIons - DOTU: Excludes components from the material list, draws them in dotted and does not size them "}
{"Headers": "PIPING APPLICATION  Pipe  VERIFICATION OF DATA CONSISTENCY  CONSISTENCY CHECK DIAGNOSTIC MESSAGES", "Content": "A230 CONNECTION TYPE HCONN NOT SAME AS TERMINAL CONNECTION TYPE The FBD-FBD connection types in this example must be the same. B230 CONNECTION TYPE TCONN NOT SAME AS TERMINAL CONNECTION TYPE The GBD-GBD connection types in this example must be the same.D430 BAD ARRIVE CONNECTION TYPE The GBD-FBD connection types in this example must be a compatible combination in COCO tables. E730 LEAVE CONNECTION TYPE (of the Flange) NOT COMPATIBLE WITH TCONN The FBD-GBD connection types in this exemPle must be a compatible combination in COCO tables. "}
{"Headers": "PIPING APPLICATION  Pipe  nan ERRORS ON THE BRANCH HEAD ", "Content": "A10 HEAD REFERENCE NOT SET The top reference can only be filled in (e.g. zero) ifThe head connection (HCONN) is of the OPEN, CLOSED or DRAN type. A20 HEAD REFERENCE POINTS TO NONEXISTENT ELEMENT This error is the result of a deletion of an element, such as a stitching to which a branch was initially connected. A30 BAD HEAD RETURN REFERENCE The head is connected to an element that does not refer reciprocally to the branch. This can happen when the head of the branch is connected to another branch, which assumes that a tee must be placed somewhere along the branch. The erreUr can also occur when two or more branches are connected to the same object. "}
{"Headers": "PIPING APPLICATION  Pipe  nan ERRORS ON THE BRANCH HEAD (CONTINUED) ", "Content": "A200 DIRECTION HDIR NOT SAME AS TERMINAL DIRECTION If the headE is connected to an object such as a stitch or tee, so the HDIR position should always be identical to that of the appropriate p-point of the object. A210 POSITION HPOS NOT SAME AS TERMINAL DIRECTION If the head is connected to an object such as a stitchingOr a tee, then the HPOS position should always be identical to that of the appropriate p-point of the object. A230 CONNECTION TYPE HCONN NOT SAME AS TERMINAL CONNECTION TYPE If the head is connected to an object such as a stitch or tee, then the HCO positionNN should always be identical to that of the appropriate p-point of the object. A300 REFERENCE HSTUBE UNSET There is more than one mm of tube between the head and the p-arrive of the first component (or tail), but the HSTUBE is not filled in. A310 REFERENCE HSTUBE REFERS TO A NONEXISTENT IS SPCOM This can happen if part of the specification has been deleted. A320 HSTUBE PROBLEM, CATREF IN SPCOM UNSET This indicates an error in the specification. A330 HSTUBE PROBLEM, CATREF IN THE SPCOM REFERS TO NONEXISTENT Catalogue COMPONENT This can happen if part of the catalog has been deleted or if the CATREF is not filled in. A400 HBORE NOT SAME AS BORE OF HSTUBE The diameter of any head component (determined from the catalog) must be idEntice to the diameter of the HBORE head. A410 HCON NOT COMPATIBLE WITH CONNECTION TYPE OF HSTUBE The connection of any component of the head (determined from the catalog) must be identical to the connection of the HCON head. A420 ISPEC REFERENCE POINTS TO NONEXISTENT ELEMENT This error occurs if, for example, the heat retardant specification pointed out by the ISPEC attribute has been deleted. "}
{"Headers": "PIPING APPLICATION  Pipe  nan ERRORS ON THE TAIL AND BRANCH ", "Content": "B10 TAILREFERENCE NOT SET The queue reference can be unfilled (e.g. zero) only if the queue connection (TCONN) is of type OPEN, VENT, CLOS or DRAN. "}
{"Headers": "PIPING APPLICATION  Pipe  nan ERRORS ON THE ENTIRE BRANCH ", "Content": "C500TUBE TOO SHORT BETWEEN HEAD AND TAIL The distance between the position of the HPOS head, and the position of the TPOS tail, is greater than zero and smaller than the minimum accepted tube length (default: 100mm) C510 BAD HEAD TO TAIL GEOMETRY The poSite of the HPOS head, is not at a positive distance along the line that passes through TPOS in the direction of TDIR or the position of the TPOS tail, is not at a positive distance along the line that passes through HPOS in the direction of HDIR.C520 HBORE NOT SAME AS TBORE When there are no components on the branch, the diameter of the HBORE head must be identical in principle to the TBORE tail diameter. C530 HCONN IS NOT COMPATIBLE WITH TCONN This means that the head is connected to theUe without tube or piping component between the two, and therefore that the type of HCONN head connection must be compatible with the TCONN tail connection type. C540 THIS BRANCH HAS NO COMPONENTS This message does not necessarily indicate an error, it is just a warning.A410 HCON NOT COMPATIBLE WITH CONNECTION TYPE OF HSTUBE The connection of any component of the head (determined from the catalog) must be identical to the connection of the HCON head. A420 ISPEC REFERENCE POINTS TO NONEXISTENT ELEMENT This wanderingUr occurs if, for example, the heat retardant specification pointed out by the ISPEC attribute has been deleted. "}
{"Headers": "PIPING APPLICATION  Pipe  nan DIAGNOSIS FOR ANY COMPONENT", "Content": "D100 REFERENCE SPREF UNSET: This indicates that you likely forgot to select the correct piping component.\nD300 CONN REFERENCE NOT SET: Multi-way components can only be left unconnected if the connection type of the concerned p-point is OPEN, VENT, DRAN, or NULL.\nD310 CONN REFERENCE POINTS TO NON EXISTENT BRANCH: This can happen if the branch pointed to by the CONN reference has been connected to another object.\nD400 ARRIVE TUBE LESS THAN TUBE MINIMUM: The distance between the arrival p-point of this component and the departure p-point of the preceding component (or the head) is greater than zero and less than the specified minimum tube length (default: 100mm).\nD410 BAD ARRIVE GEOMETRY: The position and direction of the arrival p-point of this component are not correct with respect to the departure p-point of the preceding component (or the head). The error may be caused by incorrect positioning of this component, or the preceding component (or the head), or both.\nD420 BAD ARRIVE BORE: The diameter of the arrival p-point of this component is different from the diameter of the preceding tube, or if this component is not preceded by tube, from the diameter of the departure p-point of the preceding component (or HBORE).\nD430 BAD ARRIVE CONNECTION TYPE: The connection type of the arrival p-point of this component is not compatible with the preceding tube, or if this component is not preceded by tube, with the connection type of the departure p-point of the preceding component (or HCONN).\nD500 REFERENCE LSTUBE UNSET: You likely forgot to select the piping component."}
{"Headers": "PIPING APPLICATION  Pipe  nan DIAGNOSIS FOR ANY COMPONENT (CONTINUED) ", "Content": "D600 LEAVE BORE NOT SAME AS BOREOF LSTUBE The diameter of the output p-point of this component is not the same as the diameter of the tube that follows the component. D610 LEAVE CONNECTION TYPE NOT COMPATIBLE WITH CONNECTION TYPE OF LSTUBE The connection type of the output p-point of this componentIs not compatible with the tube following the component. "}
{"Headers": "PIPING APPLICATION  Pipe  nan DIAGNOSTICS SPECIFIC TO THE END COMPONENT ", "Content": "E700 LEAVE TUBE LESS THAN TUBE MINIMUM. ACTUAL LENGTH IS... The distance between the p-point ofOutput of the current component and the position of the tail (TPOS), is greater than zero and less than the specified minimum tube length (default: 100mm) E710 BAD LEAVE GEOMETRY The position and direction of the p-point of this component is not correct screwOpposite the TPOS position, and the TDIR direction of the tail. The error can be caused by incorrect positioning of this component, the tail, or both. E720 LEAVE BORE NOT SAME AS TBORE The diameter of the output p-point of this component is not pHave the same as that of the TBORE tail. DIAGNOSIS FOR ANY COMPONENT (SUITE) E730 LEAVE CONNECTION TYPE NOT COUNTABLE WITH TCONN The connection type of the output p-point of this component is not compatible with the TCONN queue "}
{"Headers": "STAIRS LADDERS  HANDRAILS  Stair Flight  Stair Flight ", "Content": "Representation Mode: Choice of representation mode Layout: simple representation (modeling) Detail: detailed representation (design) General Attributes: Default: choiceX of the standard Name: Name of the element Description: Description of the element Width: Width of the staircase Click on Next to validate the data entered.Reference Points: the user defines the reference points (start and end) of the staircase: FROM Reference Point: Definition of the START reference point by graphic identification of a stop (iron, Panel....) The Modify Position option allows you to specify the coordinates of the START point TO Reference Point: Definition of the START reference point by ideGraphic ntification of a stop (iron, Panel....), or plan identification of a plan (panel, floor...) In Plane mode, after making the graphic selection, it is possible To reverse the direction of the staircase, and to specify between the plan and the point Of reference of the staircase.Click on Next to validate the data entered. Stair Configuration: the user defines the geometric configuration of the staircase: Handrail Configuration: Determination of the Position of the railings. Click on Next to validate the data Seized.Extensions: length of extensions Stringer Option: choice of the attachment of the staircase to a surface (available in Detailed mode) Landing Options: Configuration of the landings of the staircase Extensions and Landings: the user defines the extensions and landings of the staircase:Click on to finish creating a staircase "}
{"Headers": "STAIRS LADDERS  HANDRAILS  Rung Ladder  Rung Ladder ", "Content": "The procedure for creating a ladder is similar to that for creating a staircase. Exit Type: Configuration of the exit type (face, right or left) Width inside stile: Width of the scale Truncate Stile: Foot shortening Omit Cage: PresentThat of the protective cage Omit Top Rung: Presence of the upper step Safety Gate: Safety gate "}
{"Headers": "STAIRS LADDERS  HANDRAILS  Handrail  Handrail ", "Content": "The procedure for creating railings is similar to that of creating stairs. After configuring the types of railings to be created, simply identifyEr the remarkable points of the path of the railing, It is possible to modify the railing, in order to add openings in it: The management of openings is feasible under the OPENINGS menu Creating an opening Deleting an openingDisplacement of an opening Type of opening (single or gate) "}
{"Headers": "STAIRS LADDERS  HANDRAILS  Modification of Handrail  Modification of Handrail ", "Content": "The modification of a railing is possible from the same tool as for its creation.In Layout mode as in Detail mode It is also possible to modify, create or delete components of a railing from the Modify Handrail Component dialog box. This tool allows you to modify a railing locally or in its entirety.- Split Handrail: Railing cutting tool based on selection Of elements at intersection with the railing. - Merge Handrail: Tool for merging 2 railings. -Split Rails: Tool for cutting the rails of a railing compared to aElement or between 2 points. - Material: Tool for associating matter with an STH element. "}
{"Headers": "STRUCTURE APPLICATION  STRUCTURE APPLICATION  Presentation of the module  Presentation of the module ", "Content": "The Structure Module is splitIn 4 different types of applications: 1 - Beams & Columns... Metal frames from a complete catalog 2 - Panels & Plates... Plates, pebbles, etc... 3 - Walls & Floors... Civil Engineering,... 4 - Stair, Ladder and Handrail Stairs, ladders and railings"}
{"Headers": "STRUCTURE APPLICATION  SECTIONS  Section Storage  Section Storage ", "Content": "Grid Storage Structure: The sections will be automatically prioritized in a structure that will be created in relation to The associated \"Grid\"Storage Area (Frmw or Sbfr): Sections will be automatically prioritized in a framework or SubFramework that will be created in relation to the associated \"Grid\" The elements created via the Section discipline can be prioritized in two ways: In automatic via Grid StorageIn manual via Manual Storage Manual storage Structure: The sections will be stored in a Structure that has been created manually by the user Storage Area (Frmw or Sbfr): The sections will be stored in a Framework or Sub-framework that has beenCreated manually by the user The Lock allows you to lock or not to lock the framework or Sub-Framework "}
{"Headers": "STRUCTURE APPLICATION  SECTIONS  Specification  Specification ", "Content": "Specific menu: Selection of the classDefault selection of materials Selection of the justification Selection of the specification Selection of the type Selection of the profile Use of the current profile by default Profiles: Defined by 2 points and a specification modifiable at any time, the profiles have specific attachment points and Plines that are the edges of the profiles. "}
{"Headers": "STRUCTURE APPLICATION  SECTIONS  Creating a profile (GENSEC)  Creating a profile (GENSEC) ", "Content": "Under a FRAMEWORK (FRMW) or a SUBFRAMEWORK(SBFR) (Cf 2.1 Section storage) 1 - Definition of the Start point of the Shift section: move the gensec on a single axis. Option move allows you to easily move an element. Double click opens the model editor. Allows you to work in a plan.Tips 2 - Definition of the End point of the section "}
{"Headers": "STRUCTURE APPLICATION  SECTIONS  Fitting Section  Fitting ", "Content": "Allows you to create an assembly element (fitting). It can be used to represent any elementWhich is fixed to the structure but is not an integral part of it. Create > Fitting Step 1: Click to identify the section where the fitting will be placed Step 2: Select the specification and fitting Step 3: Graphically indicate theA Pliny where the fitting will be positioned Step 4: Move the fitting to the desired position on the previously selected pline "}
{"Headers": "STRUCTURE APPLICATION  SECTIONS  Modification of a profile  Bracing gaps", "Content": "Once the bracing is created, it is possible to adjust the gap between the bracing and a reference element.\n\nAfter selecting Modify > Gaps:\n\nStep 1 \u2013 Select the components (yellow elements) that compose the bracing (GENSEC).\nStep 2 \u2013 Select the reference elements (cyan elements).\nStep 3 \u2013 Adjust the gap.\nGap: Distance between the reference element and a bracing element.\n\nNOTE: During step 2, the number of reference elements to select will vary depending on the bracing configuration."}
{"Headers": "STRUCTURE APPLICATION  SECTIONS  Modification of a profile  Modification of a profile ", "Content": "Extend: Allows you to change the length of a Gensec in relation to a plane or panel. \u2022 Mitre Ends: Allows you to make a cut of the iron endsSo that they are parallel to the bisector angle. \u2022 Fillet: Allows you to merge two irons to create a circular section \u2022 Merge: Allows you to make iron fusions \u2022 Split: Allows you to make iron cuts in relation to an element \u2022 Splice: Allows you to make iron cuts compared to a plane \u2022 Fitting: Allows you to modify specifications of fittings NOTE: The above tools will not all be detailed, because they have already been described previously, or are easy to use.If you want more information, refer to the AVEVA E3D online manual. "}
{"Headers": "STRUCTURE APPLICATION  SECTIONS  Nodes and connections  Type of Knots ", "Content": "The creation of nodes allows the elements to be connected to each other.The installation of these connections makes it possible to quickly modify a frame, model the fasteners between irons and use certain design features. -Node for fixing with the GC (ENDATUM > FIXING) -Node for fixing frame withAllique / profile (JLDATU > PLDATU > FIXING)\u2022 Fixing node with the GC Selection of the End DATUM tool then selection of the END of a structural iron \u2022 Metal frame fixing knot profile Use of the Connect tool then selection of the prin ironCipal, then the secondary section(s) to be connected, then Esc then Complete the action "}
{"Headers": "STRUCTURE APPLICATION  SECTIONS  Nodes and connections  Representation of joints ", "Content": "Once the connections are made, it is poIt is possible to show the type of fixing/preparation of the profiles by defining a specification at the seal (Fixing). After selecting modify -> Joint 1-Select its section (always the main section). 2-Click on its joint 3-PressOn enter 4-Select the joint type 5-Make \"Apply\" "}
{"Headers": "STRUCTURE APPLICATION  SECTIONS  Nodes and connections  Subordinate Node and Dominant Node ", "Content": "By default, the connection nodes between irons are subordinated,That is, the direction of the connected iron has priority over the position of the connection node. By making a dominant node, its position takes precedence over the direction of the connected iron, so when the connections are restored, the irons areAdapted in length and direction. "}
{"Headers": "STRUCTURE APPLICATION  PANELS AND PLATES Specification  Specification ", "Content": "Specific menu: Thickness of the panels Selection of the type of beam desired Specification of panels SelEction of materials for panels Representation of aretes Standard Plate: Smooth sheet Check Plate: Tear metal Standard Grating: Grating Each of these specifications has its own thickness range Panel (PANE) It is defined by at the mInimum 3 vertex (PAVE), a specification or thickness and justification "}
{"Headers": "STRUCTURE APPLICATION  PANELS AND PLATES Creation of panels  Creation of panels ", "Content": "Under a FRAMEWORK (FRMW) or a SUBFRAMEWORK(SBFR), if the default hierarchies have not been filled in: For the creation of a panel, simply select graphically or manually enter the coordinates of the points. There are several options when creating a panel: FILLET: permeT to create a leave at a point of the ARC panel: allows you to create a rounded side JUSTIFICATION: allows you to choose between top, bottom or center for the creation of the BACK panel: return to the previous point FINISH: complete the creation of the panel NOTE: In representationBy default, the panels are represented in transparency. The combination of the \"T\" key and the left click allows you to select the elements under a panel. "}
{"Headers": "STRUCTURE APPLICATION  PANELS AND PLATES Modification of panels  Modification of panels ", "Content": "After creating a profile, it is possible to edit it at any time: Specification: allows you to change the thickness of a panel with specification - Thickness: allows you to change the thickness of a panel without specification- Justification: allows you to modify the justification of the panel (Top, Center, Bottom) - Panel Origin: allows you to move the origin of the panel - Representation: allows you to modify the representation and level of obstruction of the panel - Drawing Edges: allows you toE modify the representation of the edges - Offset: allows you to modify the dimension of the panel - Split: allows you to section the panel by an element or plane - Merge: allows you to merge several panels "}
{"Headers": "STRUCTURE APPLICATION  PANELS AND PLATES Opening creation  Opening creation ", "Content": "The Negative Extrusion creation tool allows you to create specific openings "}
{"Headers": "STRUCTURE APPLICATION  WALLS AND FLOORS  Specification  WALLS ", "Content": "A wall (STWALL), like an iron section, is characterized by: - a line defined by 2 points - a section defined by a specification - a justification of the section on the line It can also include nodes and connections with other walls or sections. It is also possible toModel a wall without using a specification: GWALLs are defined as Floor or Screed. "}
{"Headers": "STRUCTURE APPLICATION  WALLS AND FLOORS  Specification  FLOOR / SCREED ", "Content": "A floor or a screed, like a panel, isCharacterized by: - a sketch defined by vertexes - a thickness defined by a specification - a justification These elements can be connected in the same way as a panel. "}
{"Headers": "STRUCTURE APPLICATION  WALLS AND FLOORS  Creation of wall  Creation of wall ", "Content": "Under a FRAMEWORK (FRMW) or a SUBFRAMEWORK (SBFR), "}
{"Headers": "STRUCTURE APPLICATION  WALLS AND FLOORS  Creation of Floor / Screed  Creation of Floor / Screed ", "Content": "Under a FRAMEWORK (FRMW) or a SUBFRAMEWORK (SBFR), if the default hierarchies have not been filled in: They are defined in the same way as the panels (PANEL). In general, Floors are used to represent GC slabs, and ScreedsFor the GC massifs. Openings can be made in these elements, in the same way as in a Panel. Under a FRAMEWORK (FRMW) or a SUBFRAMEWORK (SBFR), if the default hierarchies have not been filled in: The screeds can be modifiedS in order to be represented with a slope "}
{"Headers": "STRUCTURE APPLICATION  WALLS AND FLOORS  Element modification  Element modification ", "Content": "Definition: allows you to redefine \"Start\" and \"End\" points - Specification: allows you to change the type of wall (thicknessAnd height) - Origin position: allows the displacement of the origin of a GWALL - Justification: allows you to change the justification of the wall (NA,CBOW, ITOW....) - Flip: allows you to change the orientation of the walls by switching their Start and End positions - DefinItion: allows you to redefine the points of the sketch - Justification: allows you to modify the justification of the element (NA,TOS, BOTTOM) - Thickness: allows you to modify the thickness of the element - Negative Extrusion: allows you to redefine the points of theQuisse - Origin Position: allows the displacement of the origin of the element -Specification: allows you to change the specification (thickness) "}
{"Headers": "STRUCTURE APPLICATION  FITTING  Accessories for Iron  Accessories for Iron ", "Content": "Specification: allows you to choose the type of accessories you want. Fitting group: displays the possible types for the current element (GTYPE) Fitting: allows you to choose the subtype of accessories (for example, a stylE particular, or a thickness of gusset). Design Parameters: Allows you to modify the attributes of the selected fitting. See page 20 of the manual for the steps of creating a fitting on Gensec NOTA: The movement of accessories can be carried out withC the Model Editor, by activating the Model Editing tool from the context menu of the element "}
{"Headers": "STRUCTURE APPLICATION  FITTING  Accessories for Panel  Accessories for Panel ", "Content": "Specification: allows you to choose the desired type of accessory.Fitting group: displays the possible types for the current element (GTYPE) Fitting: allows you to choose the subtype of accessories (for example, a particular style, or a gusset thickness). Design Parameters: Allows you to modify the attributes of the selected fitting."}
{"Headers": "STRUCTURE APPLICATION  FITTING  Accessories for Wall Accessories for Wall", "Content": "Specification Data: allows you to choose the type of accessories (Standard Doors, Standard Windows, etc). Current selection: summary of the selected subtypes Type: allows you to select the subtype of accessories, for example a particular type of window or door.Positioning: the drop-down menu allows you to specify the positioning in the thickness, elevation and distance from the origin of the wall. A click on the Pick Position icon displays the Positioning Control and Pick Fitting Position dialog boxes.The Properties icon: allows you to enter the values used in the definition of the accessory. The Plotfile icon: allows you to display a help plan of the accessory, if it is provided. "}
{"Headers": "STRUCTURE APPLICATION  FITTING  Accessories for Floor and Screed  Accessories for Floor and Screed ", "Content": "Specification Data: allows you to choose the type of accessories (Standard Doors, Standard Windows, etc). Current selection: summary of the selected subtypes Type: allows you to select the subtypeAccessories, for example a particular type of window or door. Positioning: the drop-down menu allows you to specify the positioning in the thickness, elevation and distance from the origin of the floor or screed A click on the Pick iconPosition displays the Positioning Control and Pick Fitting Position dialog boxes. The Properties icon: allows you to enter the values used in the definition of the accessory. The Plotfile icon: allows you to display a help plan of the accessory, if it is provided."}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  Stair Flight  Stair Flight ", "Content": "Representation Mode: Choice of representation mode Layout: simple representation (modeling) Detail: det representationAill\u00e9 (design) General Attributes: Default: choice of the standard Name: Element name Description: Description of the element Width: Stair width Click on Next to validate the data entered. Reference Points: the user defines theReference points (beginning and end) of the staircase: FROM Reference Point: Definition of the START reference point by graphic identification of a stop (iron, Panel....) The Modify Position option allows you to specify the coordinates of the START point TO ReferencePoint: Definition of the START reference point by graphical identification of a stop (iron, Panel....), or plan identification of a plan (panel, floor...) In Plane mode, after making the graphic selection, it is possible To reverse the direction of the eScale, and specify between the plane and the point Of reference of the staircase. Click on Next to validate the data entered. "}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  Rung Ladder  Rung Ladder ", "Content": "The procedure for creating a ladder is similar to that for creating a staircase. Exit Type: Configuration of the exit type (face, right or left) Width inside stile: Width of the scale Truncate Stile: Foot shortening Omit Cage: PresentThat of the protective cage Omit Top Rung: Presence of the upper step Safety Gate: Safety gate "}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  Handrail  Handrail ", "Content": "The creation procedureOf railing is similar to that of creating stairs. After configuring the types of railing to be created, simply identify the remarkable points of the railing path, It is possible to modify the guard, It is possible to modifyProud the railing, in order to add openings in it: The management of openings is feasible under the OPENINGS menu Creating an opening Deleting an opening Displacement of an opening Type of opening (single or gate) "}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  Modification of Handrail  Modification of Handrail ", "Content": "The modification of a railing is possible from the same tool as for its creation. In Layout mode as well as in Detail modeIt is also possible to modify, create or delete Components of a railing from the box of Dialogue Modify Handrail Component. This tool allows you to modify locally or in its Overall a railing. - Split Handrail: Slitting toolAge of railing based on selection Of elements at intersection with the railing. - Merge Handrail: Tool for merging 2 railings. -Split Rails: Tool for cutting the rails of a railing compared to a Element or between 2 points. - Mat\u00e9riAl: Tool for associating matter with an STH element. "}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  Clasher  Display of Clashes ", "Content": "There are two solutions to use the Clash: - Auto Clash: which is activated using the iconAll collisions will be displayed as they take place when creating new objects. - Or you can control collisions at the end of a routing of a piping for example. In this case, the clasher opens from the icon"}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  Clasher  Configuration of the clasher ", "Content": "The configuration of the Clasher is feasible with the tools available under the Options tab, Touch Gap: tangent tolerance OVerlap: overlap tolerance Clearance: spacing tolerance Keys are: -Are Included: support of tangents -Are Ignored: tangents ignored Clashes within Branch: -Are included: management of clashes in the same branch -Ignore aDjacent: management of clashes in the same branch, excluding Previous and following elements -Are ignored: interference in the same branch ignored Connections: -Are Included: support for tangents with connections (NOZZLE) -Are Ignored: tangents ignored-With Spec. are ignored: tangents ignored if the specification of Connections is identical to that of the controlled element. -Clashes Ignored Within: Ignores clashes between primitives belonging to the same element "}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  Clasher  Obstruction list ", "Content": "The obstruction list defines all the elements of the special map with which collisions will be defined. By default, the obstruction list contains all the design elements of the MDB.It is possible to modify this list in order to generate an item collision list. The exclusion list contains all the elements that should not be taken into account when calculating collisions. By default, this list is empty. From the onglAnd Limits, a volume can be defined around one or more elements, or a region in order to create an obstruction space. Any element that is partially or entirely in this space will be checked. "}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  Clasher  Visualization ", "Content": "Click on Check CE to check the current item, or enter the name of the item to be checked before clicking on Check. By navigating the list of collisions, a visualization of the collision sSelected is generated in a graphic area similar to the design graphic view. The Navigate to Clash Item option allows you to access the colliding object. The Navigate to Obstruction option provides access to the obstructed object "}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  History of the model  Session Comment ", "Content": "At each Savework, a working session is opened by the user. The user has the possibility to comment on his sessions in order to facilitate theUnderstanding of the history of the elements. "}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  History of the model  Comparison Date ", "Content": "It is possible to compare the state of an element of the model with its state on a defined date.The easiest way is to be able to use a stamp (revision) of the database. After choosing a comparison date and clicking on OK, the user can query the elements of the model on their previous state with the keyword \"OLD\".Ex: Q OLD NAME Q OLD POS "}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  History of the model  Model Changes ", "Content": "The history of element creations and modifications is kept by AVEVA E3D. The Mode toolL Changes allows visibility of the entire history or just that of a particular element. It is therefore possible to know which user has modified an element and on what date. NOTE: The Q LASTMOD and Q USERMOD commands allow you to displayExpensive in the Command Window, the date and author of the last modification. "}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  DB Listing  DB Listing ", "Content": "The DB Listing is the backup of one or more element(s) ofE the database in a text file. This backup is only compatible with AVEVA E3D and AVEVA PDMS, the versions may be different. This file (.txt) can be edited before being reused, it contains all the command lines for recreationR the same element identically (name, position, geometry). Only the hierarchy differs and depends on the hierarchy selected at the time of importing this file. Some elements of PDMS using references in CATALOGUE (Structure, Piping, Nozzle, etc...) are only compatible with a Project containing the same CATALOGUE. It is possible to use this tool to: -Save an element at a time \"t\" -Duplicate an element (requires to modify the text file) -Modify an existing element (requiresIte to modify the text file) "}
{"Headers": "STRUCTURE APPLICATION  STAIRS, LADDERS AND HANDRAILS  Postponement  Postponement ", "Content": "Reporting is the extraction of information about the 3D model into text files, Excel, or to the AVEVA E3D reporting editor. Files (.txt) or (.csv) can be edited.They contain all the information you want to extract from the model (name, position, geometry). This data can be modified and reinjected into the model. Some elements of E3D using references in CATALOGUE (Structure, Piping, Nozzle, etc...) are only compatible with a Project containing the same CATALOGUE. It is possible to use this tool to: -Check one or more existing elements -Edit one or more existing elements (requires to modify the text file) -Emblish a list ofE hardware (data extraction) For simple verification or modification operations, the Simple Report function is preferred: In the example opposite, we query all the EQUI-type elements located under the CE hierarchy. The attributesNAME, OWNER, PURPOSE, AREA and POSITION of each item found will be saved in the report.txt file "}
{"Headers": "WALLS AND FLOORS  WALLS AND FLOORS  Specification  WALLS ", "Content": "A wall (STWALL), like an iron section, is characterized by: - a line defined by 2 points - a section defined by a specification - a justification of the section on the line It can also include nodes and connections with other walls or sections. It is also possible toModel a wall without using a specification: GWALLs are defined as Floor or Screed. "}
{"Headers": "WALLS AND FLOORS  WALLS AND FLOORS  Specification  FLOOR / SCREED ", "Content": "A floor or a screed, like a panel, isCharacterized by: - a sketch defined by vertexes - a thickness defined by a specification - a justification These elements can be connected in the same way as a panel. "}
{"Headers": "WALLS AND FLOORS  WALLS AND FLOORS  Creation of wall  Creation of wall ", "Content": "Under a FRAMEWORK (FRMW) or a SUBFRAMEWORK(SBFR), if the default hierarchies have not been filled in: Single Continuous Radial Position of the points compared to the previous NOTES: Without default specification,The profile appears in dotted Position of the points by coordinates X, Y and Z "}
{"Headers": "WALLS AND FLOORS  WALLS AND FLOORS  Creation of Floor / Screed  Creation of Floor / Screed ", "Content": "Under a FRAMEWORK (FRMW) or a SUBFRAMEWORK(SBFR), if the default hierarchies have not been filled in: They are defined in the same way as the panels (PANEL). In general, Floors are used to represent GC slabs, and Screeds For the GC massifs. OpenUres can be carried out in these elements, in the same way as in a Panel. Under a FRAMEWORK (FRMW) or a SUBFRAMEWORK (SBFR), if the default hierarchies have not been filled in: The screeds can be modified to be represented with a slope"}
{"Headers": "WALLS AND FLOORS  WALLS AND FLOORS  Element modification  Element modification ", "Content": "Definition: allows you to redefine \"Start\" and \"End\" points - Specification: allows you to change the type of wall (thicknessAnd height) - Origin position: allows the displacement of the origin of a GWALL - Justification: allows you to change the justification of the wall (NA,CBOW, ITOW....) - Flip: allows you to change the orientation of the walls by switching their Start and End positions - DefinItion: allows you to redefine the points of the sketch - Justification: allows you to modify the justification of the element (NA,TOS, BOTTOM) - Thickness: allows you to modify the thickness of the element - Negative Extrusion: allows you to redefine the points of theQuisse - Origin Position: allows the displacement of the origin of the element -Specification: allows you to change the specification (thickness) "}
{"Headers": "WALLS AND FLOORS  WALLS AND FLOORS  Accessories for Wall Accessories for Wall", "Content": "Specification Data: allows you to choose the type of accessories (Standard Doors, Standard Windows, etc). Current selection: summary of the selected subtypes Type: allows you to select the subtype of accessories, for example a particular type of window or door.Positioning: the drop-down menu allows you to specify the positioning in the thickness, elevation and distance from the origin of the wall. A click on the Pick Position icon displays the Positioning Control and Pick Fitting Position dialog boxes.The Properties icon: allows you to enter the values used in the definition of the accessory. The Plotfile icon: allows you to display a help plan of the accessory, if it is provided. "}
{"Headers": "Function Keys", "Content": "F2 Clear Canvas "}
{"Headers": "Function Keys", "Content": "F3 Object Snap On/Off "}
{"Headers": "Function Keys", "Content": "F4 Object Snap Projection On/Off "}
{"Headers": "Function Keys", "Content": "F5 Toggle Walk Mode On/Off "}
{"Headers": "Function Keys", "Content": "F6 Toggle Fly Mode On/Off"}
{"Headers": "Function Keys", "Content": "F7 Grid On/Off "}
{"Headers": "Function Keys", "Content": "F8 Orthogonal drawing On/Off "}
{"Headers": "Function Keys", "Content": "F9 Grid Snap On/Off"}
{"Headers": "Function Keys", "Content": "F10 Polar Tracking On/Off "}
{"Headers": "Function Keys", "Content": "F11 Toggle Shaded/Wireline mode "}
{"Headers": "Function Keys", "Content": "F12 Dynamic hints On/Off"}
{"Headers": "Function Keys", "Content": "General Keys "}
{"Headers": "Function Keys", "Content": "Delete Deletes selected elements in 3D View with confirmation "}
{"Headers": "Function Keys", "Content": "Tab Navigates between in-canvas input boxes "}
{"Headers": "Function Keys", "Content": "Space Locks value in the in canvas input boxes / Repeat Command"}
{"Headers": "Function Keys", "Content": "Home or Page Up Navigates to WORL* level in any Explorer "}
{"Headers": "Function Keys", "Content": "End or Page Down Navigates to Bottom Level in any Explorer "}
{"Headers": "Function Keys", "Content": "Esc Exits current CIE Operation / cancels position input/ removes selection/exits edit mode "}
{"Headers": "Function Keys", "Content": "Arrow UP Shows In-Canvas command of last used CIE Operation "}
{"Headers": "Function Keys", "Content": "Arrow Down Shows available Tile Icons during CIE Operation "}
{"Headers": "Function Keys", "Content": "Insert Toggle Feature Highlight function On/Off"}
{"Headers": "Function Keys", "Content": "Backspace Removes selection from 3D view "}
{"Headers": "Function Keys", "Content": "Enter Confirms position, selects default option, executes command, etc. "}
{"Headers": "Function Keys", "Content": "Ctrl + A Select All Elements in the View "}
{"Headers": "Function Keys", "Content": "CTrl + C Copies via Mid Position of all selected element(s)(Clipboard operation) "}
{"Headers": "Function Keys", "Content": "Ctrl + E Toggles  Distance Snap  Mode On/Off"}
{"Headers": "Function Keys", "Content": "Ctrl + F Triggers Find/Search form "}
{"Headers": "Function Keys", "Content": "Ctrl + G GETWORK "}
{"Headers": "Function Keys", "Content": "Ctrl + I Toggles Property Grid On/Off "}
{"Headers": "Function Keys", "Content": "Ctrl + P Print "}
{"Headers": "Function Keys", "Content": "Ctrl + S SAVEWORK "}
{"Headers": "Function Keys", "Content": "Ctrl + T Toggles Pick Through Translucency On/Off "}
{"Headers": "Function Keys", "Content": "Ctrl + V Paste Clipped "}
{"Headers": "Function Keys", "Content": "Ctrl + Y Redo "}
{"Headers": "Function Keys", "Content": "Ctrl + Z Undo "}
{"Headers": "Function Keys", "Content": "Shift + F4 Toggles between Perspective and Parallel modes "}
{"Headers": "Function Keys", "Content": "Shift + F7 Toggles between About Model and About an Eye modes "}
{"Headers": "Function Keys", "Content": "Shift + Insert Paste Clipped "}
{"Headers": "Function Keys", "Content": "Ctrl + Shift+ C Copies element(s) with basepoint(Clipboard operation) "}
{"Headers": "Function Keys", "Content": "Alt + Left Arrow Pans 3D view towards Left"}
{"Headers": "Function Keys", "Content": "Alt + Right Arrow Pans 3D view towards Right "}
{"Headers": "Function Keys", "Content": "Alt + Up Arrow Pans 3D view towards Up "}
{"Headers": "Function Keys", "Content": "Alt + Down Arrow Pans 3D view towards Down "}
{"Headers": "Function Keys", "Content": "Alt + F4 Quit Application"}
{"Headers": "Function Keys", "Content": "In Canvas Commands (Model) "}
{"Headers": "Function Keys", "Content": "Order Description "}
{"Headers": "Function Keys", "Content": "AIDARC Invokes function to create AID type Arc"}
{"Headers": "Function Keys", "Content": "AIDBIS Invokes function to create an AIDLIN bisecting between two non -parallel AIDLINs "}
{"Headers": "Function Keys", "Content": "AIDCIR Invokes function to create AID type Circle "}
{"Headers": "Function Keys", "Content": "AIDFIL Invokes function to create filleting AIDARC connecting two non-parallel AIDLINs "}
{"Headers": "Function Keys", "Content": "AIDLIN or L Invokes function to create AID type Line "}
{"Headers": "Function Keys", "Content": "AIDPOI Invokes function to create AID type Point "}
{"Headers": "Function Keys", "Content": "AIDTAN Invokes function to create an AIDLIN taNgential to two circles which are non- concentric "}
{"Headers": "Function Keys", "Content": "AIDTEXT Invokes function to create AID type Text"}
{"Headers": "Function Keys", "Content": "Command Description "}
{"Headers": "Function Keys", "Content": "ANGLE To calculate angle between any two entities "}
{"Headers": "Function Keys", "Content": "AREA To create area arrangement "}
{"Headers": "Function Keys", "Content": "BRACING To specify bracing gaps for existing diagonal elements or members"}
{"Headers": "Function Keys", "Content": "CAMERA Enables to lock view wrt an object. Also disables 3D orbit mode when it is enabled "}
{"Headers": "Function Keys", "Content": "CANCEL Cancels any current operation in-progress "}
{"Headers": "Function Keys", "Content": "CO or COPY Invokes function to copy selected entities with respect to a base point selected "}
{"Headers": "Function Keys", "Content": "COPYBASE Invokes function to copy selected entities with respect to a base point selected "}
{"Headers": "Function Keys", "Content": "COPYCLIP Invokes function to copy selected entities without any base point "}
{"Headers": "Function Keys", "Content": "CONNECT Enables function to connect any two GENSECs "}
{"Headers": "Function Keys", "Content": "CUTBASE Invokes function to CUT/PASTE selected entities with respect to a base point selected "}
{"Headers": "Function Keys", "Content": "CUTCLIP Invokes function to CUT/PASTE selected entities"}
{"Headers": "Function Keys", "Content": "CURVE To create curve from plane "}
{"Headers": "Function Keys", "Content": "D or LINDIM Invokes function to create db type Linear Dimension "}
{"Headers": "Function Keys", "Content": "DECKS To create decks "}
{"Headers": "Function Keys", "Content": "DELETE To delete selected entities "}
{"Headers": "Function Keys", "Content": "DISCONNECT Enables function to disconnect any two connected GENSECs "}
{"Headers": "Function Keys", "Content": "DIST or DI To calculate distance between any two entities "}
{"Headers": "Function Keys", "Content": "EM or EDITMODE Triggers Edit Mode "}
{"Headers": "Function Keys", "Content": "ENDATUM Create an ENDATU Fixing at selected End of GENSEC."}
{"Headers": "Function Keys", "Content": "EXTEND Enables function to extend the end of a structural element to a reference element. "}
{"Headers": "Function Keys", "Content": "FILLET To create a Fillet between two non-connected structural elements "}
{"Headers": "Function Keys", "Content": "FLY Enable FLY mode operation"}
{"Headers": "Function Keys", "Content": "FORCETRIM To trim an attached GENSEC to selective Pline of Owning GENSEC "}
{"Headers": "Function Keys", "Content": "FOVY Enables option to enter new Vertical field -of-view angle "}
{"Headers": "Function Keys", "Content": "GENSECDEF Triggers function to set default specification wrt. existing GENSEC "}
{"Headers": "Function Keys", "Content": "GFITT_CRE Enable function to create a GENSEC Fitting "}
{"Headers": "Function Keys", "Content": "GFITT_MODEnable function to modify a GENSEC Fitting "}
{"Headers": "Function Keys", "Content": "GRIDCY Invokes function to create a new GRID CYLINCER for Radial Grid only in In -Mode "}
{"Headers": "Function Keys", "Content": "GRIDID Resets IDs of REFGRDs "}
{"Headers": "Function Keys", "Content": "Command Description "}
{"Headers": "Function Keys", "Content": "GRIDPL Invokes function to create a new GRID PLANE for REFGRD in IN-Mode(Currently works for a Single REFGRD) "}
{"Headers": "Function Keys", "Content": "ID Queries Coordinate Positions at snapped position "}
{"Headers": "Function Keys", "Content": "IN Triggers IN or Include mode "}
{"Headers": "Function Keys", "Content": "JMOD Enables user to modify joints on a SECTION "}
{"Headers": "Function Keys", "Content": "LCS Invokes opeRation to change Coordinate system between Local and World "}
{"Headers": "Function Keys", "Content": "LINDIMA Invokes function to create db type Aligned Dimensions"}
{"Headers": "Function Keys", "Content": "LOOKROUND Enables 3D Orbit mode option to look around a locked view in Perspective ProjMode "}
{"Headers": "Function Keys", "Content": "M or MOVE Invokes function to move entities with respect to a base point selected a "}
{"Headers": "Function Keys", "Content": "MERGE To merge two members of the same element type "}
{"Headers": "Function Keys", "Content": "MI or MIRROR To mirror any selected Structural Elements by defining a Mirror Plane "}
{"Headers": "Function Keys", "Content": "MITRE Enables option to Mitre two ends of GENSECs "}
{"Headers": "Function Keys", "Content": "MLABEL InvokesA function that creates a Label in 3D Canvas "}
{"Headers": "Function Keys", "Content": "MREDO Enables user to REDO all previous actions or to desired no.Of actions "}
{"Headers": "Function Keys", "Content": "NEXT To go Forwards through Views "}
{"Headers": "Function Keys", "Content": "OUT Trigger OUT mode by exiting IN mode "}
{"Headers": "Function Keys", "Content": "OUTALL takes user all the way out "}
{"Headers": "Function Keys", "Content": "OSNAPD Triggers Distance Snap Mode function"}
{"Headers": "Function Keys", "Content": "P or PAN Enables REALTIME PAN option "}
{"Headers": "Function Keys", "Content": "PANARC Enables function to Create a ARC PANEL using three point or two point methods "}
{"Headers": "Function Keys", "Content": "PANCIRC Enables function to Create a CIRCULAR PANEL with multiple options "}
{"Headers": "Function Keys", "Content": "PANDIR Pans View towards selected PLAN VIEW directions "}
{"Headers": "Function Keys", "Content": "PANDISC EnablesFunction to Create a DISC PANEL using Centre+ or two point methods "}
{"Headers": "Function Keys", "Content": "PANELSURF To create panel from surface"}
{"Headers": "Function Keys", "Content": "PANELPLANAR To create pane from grid plane "}
{"Headers": "Function Keys", "Content": "PANELNXTRDISC Creates a Negative extrusion of a PANEL in Circular Shape in 3 different Modes "}
{"Headers": "Function Keys", "Content": "PANELNXTRMULT Creates a Negative extrusion of a PANEL in Rectangular Shape using Multiple Points "}
{"Headers": "Function Keys", "Content": "PANELNXTRRECT Creates a Negative extrusion of a PANEL in Rectangular Shape using Two Points "}
{"Headers": "Function Keys", "Content": "PANMULT Enables function to Create a RECTANGULAR PANEL with multiple points "}
{"Headers": "Function Keys", "Content": "PANOFFSET Enables function to Create an Offset Perimeter of PANEL with multiple points "}
{"Headers": "Function Keys", "Content": "PANRECT Enables function to Create a RECTANGULAR PANEL using two points "}
{"Headers": "Function Keys", "Content": "Description "}
{"Headers": "Function Keys", "Content": "PANRING Enables function to Create a RING PANEL using three point to two point methods "}
{"Headers": "Function Keys", "Content": "PASTECLIP To paste any copied or cut elements that are available in current session "}
{"Headers": "Function Keys", "Content": "PFITT_MOD Enable function to modify a PANEL Fitting"}
{"Headers": "Function Keys", "Content": "PL or PLINE Enables function to create a Polyline "}
{"Headers": "Function Keys", "Content": "PLAN Set the current View to Plan View mode "}
{"Headers": "Function Keys", "Content": "PR or PROPERTIES Open Property Window if not opened already in the application "}
{"Headers": "Function Keys", "Content": "PREV To go Back through Views "}
{"Headers": "Function Keys", "Content": "PROJMODE Toggles between Projection modes Orthogonal or Perspective"}
{"Headers": "Function Keys", "Content": "RADIAL Enables option to create a Radial Grid "}
{"Headers": "Function Keys", "Content": "REDO Redo any operation that was previously called back(Performed Undo) "}
{"Headers": "Function Keys", "Content": "REFGRD Enables option to create a Reference Grid "}
{"Headers": "Function Keys", "Content": "RO or ROTATE Invokes function to rotate any object around any defined axis "}
{"Headers": "Function Keys", "Content": "SCALE To Scale a StruCtural Element by selecting a Base Point "}
{"Headers": "Function Keys", "Content": "SECARC Creates an ARC GENSEC and also gives multiple oPtions to choose the way they are created "}
{"Headers": "Function Keys", "Content": "SECCUR Creates a Curved GENSEC and also gives multiplE options to choose the way they are created "}
{"Headers": "Function Keys", "Content": "SECRING Creates a RING GENSEC and also gives multiPle options to choose the way they are created "}
{"Headers": "Function Keys", "Content": "SECTION Creates a Straight GENSEC and gives multIple options to choose the way they are created "}
{"Headers": "Function Keys", "Content": "SELALL To select all the elements in 3D View "}
{"Headers": "Function Keys", "Content": "SPLICE To Splice any Structural Element(s) in multiple ways "}
{"Headers": "Function Keys", "Content": "SPLIT To split any Structural Element(s) in multiple ways "}
{"Headers": "Function Keys", "Content": "STRETCH To Stretch any Structural Element along a defined path "}
{"Headers": "Function Keys", "Content": "SURFACE To create Surface "}
{"Headers": "Function Keys", "Content": "SPACE To create space arrangement "}
{"Headers": "Function Keys", "Content": "TOWER Enables option to create a Rectangular Tower Grid "}
{"Headers": "Function Keys", "Content": "TOWERT Enables option to create a Triangular Tower Grid "}
{"Headers": "Function Keys", "Content": "U To Undo any current operation "}
{"Headers": "Function Keys", "Content": "UNDO Enables user to UNDO all operation or to desired no.Of counts "}
{"Headers": "Function Keys", "Content": "WALK Enables user to WALK around a Model "}
{"Headers": "Function Keys", "Content": "Z or ZOOM Enables Zoom options "}
{"Headers": "Function Keys", "Content": "-VIEW or -V To change any View between Isometric or Orthographic or Plan View "}
{"Headers": "Function Keys", "Content": "-PAN or -P PANs view wrt base point selection "}
{"Headers": "Function Keys", "Content": "In Canvas Commands (Primitives) "}
{"Headers": "Function Keys", "Content": "Command Description "}
{"Headers": "Function Keys", "Content": "BOX Invokes function to create BOX "}
{"Headers": "Function Keys", "Content": "CYLI Invokes function to create CYLINDER "}
{"Headers": "Function Keys", "Content": "CONE Invokes function to create CONE "}
{"Headers": "Function Keys", "Content": "CTOR Invokes function to create CIRCULAR TORUS "}
{"Headers": "Function Keys", "Content": "DISH Invokes function to create DISH "}
{"Headers": "Function Keys", "Content": "EXTR Invokes function to create EXTRUSION "}
{"Headers": "Function Keys", "Content": "PYRA Invokes function to create PYRAMID "}
{"Headers": "Function Keys", "Content": "RTOR Invokes function to create RECTANGULAR TORUS "}
{"Headers": "Function Keys", "Content": "REVO InvokesFunction to create REVOLUTION PRIMITIVE "}
{"Headers": "Function Keys", "Content": "SLCY Invokes function to create SLOPING CYLINDER "}
{"Headers": "Function Keys", "Content": "SNOU Invokes function to create SNOUT "}
{"Headers": "Function Keys", "Content": "NBOX Invokes function to create BOX "}
{"Headers": "Function Keys", "Content": "NCYLInvokes function to create CYLINDER "}
{"Headers": "Function Keys", "Content": "NCON Invokes function to create CONE "}
{"Headers": "Function Keys", "Content": "NCTO Invokes function to create CIRCULAR TORUS "}
{"Headers": "Function Keys", "Content": "NDIS Invokes function to create DISH "}
{"Headers": "Function Keys", "Content": "NPYR Invokes function to create PYRAMID"}
{"Headers": "Function Keys", "Content": "NRTO Invokes function to create RECTANGULAR TORUS"}
{"Headers": "Function Keys", "Content": "NREV Invokes function to create REVOLUTION PRIMITIVE "}
{"Headers": "Function Keys", "Content": "NSLC Invokes function to create SLOPING CYLINDER "}
{"Headers": "Function Keys", "Content": "NSNO Invokes function to create SNOUT "}
{"Headers": "Function Keys", "Content": "NXTR Invokes function to create EXTRUSION"}
{"Headers": "PDMS PML  Objectives PML 1&2 ", "Content": "Programming \u2022Acquire the basics of programming in PML \u2022Know the programming conventions \u2022Understand the cCommunication between DABACON databases and the PML language \u2022Be able to create a user interface \u2022Browsing development possibilities (PML/C# interface) "}
{"Headers": "PDMS PML  Simple macros  ", "Content": "Presentation of macros A macro is a sequence of commands interpreted and executed by PDMS software. These commands can be filled in one at One in the \"command window\" and will give the same result.To launch a macro, simply drag the .pmlmac file into the \"command window\" of PDMS or write the following line: $m Macro path, example: $m C:\\Path \\mySimpleMacro.pmlmac NOTE: A macro does not require a particular extension.A *.txt file can be a macro however, the *.pmlmac extension allows them to differentiate from Other text files. "}
{"Headers": "PDMS PML  Simple macros with parameters ", "Content": "Presentation of macros The parameterized macros allow, when launching them, to fill in arguments that will be used by macros. The arguments are read using the syntax: $1, $2, etc. The arguments are to rTeach following the macro call command and separated by a space. $m C: \\Path \\mySimpleMAcro.pmlmac MYEQUI 200 300 500 $1 $2 $3 $4 If an argument contains a space, we use the syntax: $m C: \\Path \\mySimpleMAcro.pmlmac $<TEXT WITH SPACE$> 200 300 500 (for a description for example) $1 $2 $3 $4  "}
{"Headers": "PDMS PML  Programmable macros  ", "Content": "Presentation of macrosPML1 variables make it possible to program macros to make them intelligent. Variables are memory blocks that will make it possible to store data (numbers, string, etc.). The variables can be compared to Labeled drawers.For example, we can store the number \"32\" in the \"Age\" drawer. To define a variable in PML, the following syntax must be used: VAR! nameVariable value of the variable Or ! nameVariable = value of the variable To retrieve the value of the variable, you must use:$! nameVariable To display the value of the variable in the \"commands window\" you must write: $p $! nameVariable \u2192 Returns the value of the variable Or Q var! nameVariable \u2192 Returns the type and value of the variable \u25baThe variables are defined with one or two \"!\": \"! Variable\": to define a local variable (Usable only by the macro that created it). \u201c!! Variable\": to define a global variable (Usable by all macros during the same PDMS session). \u25baNever start the name of a variable with a digit.\u25baNever use \".\" or \"_\" in a variable name. NOTE: It is important to choose the name of the variables so that the code is as readable as possible. For this, he You must choose names that represent as much as possible the content of the variable.PML 1 PML 2  "}
{"Headers": "PDMS PML  String (string)", "Content": "Type of variables There are different types of variables that do not store data in the same way.NOTE: Lasyntax \"var! myVar \"works only for the definition of STRING variables. String-type variables can contain strings. Declaration of variable of type string: Var! myString 'String of characters' Or Var! myString |Character string|Or ! myString = |String| Real-type variables are used to store numerical values. Declaration of variable of type real: ! myReal = 23 Boolean variables can have values only equal to \"TRUE\" or \"FALSE\", ! myBOolean = TRUENOTA: It is preferable to use \"||\" rather than \"''\" For the definition of a string type variable. In Effect, with this syntax, the use of characters As \"'\", \"\u00e9\", is then possible. 2.2. Real (real) 2.3. Boolean (boul\u00e9ens) "}
{"Headers": "PDMS PML  Array (tables) ", "Content": "Type of variables A table is a set of variables stored in a table. The tables must be defined as follows: ! myTable = array ()! myTable [1] = |Chain| ! myTable [2] = |de| ! myTable [3] = |characters| Or ! myTable.append (|Chaine|) ! myTable.append (|de|) ! myTable.append (|characters|) ! Brand = 1 ! Model = 2 ! Year = 3 ! Garage = array () ! Garage[1][! Brand] = |Citro\u00ebn| ! Garage[1][! Model ] = |Xsara|! Garage[1][! Year ] = |1999| ! Garage[2][! Brand] = |Renault| ! Garage[2][! Model ] = |Clio| ! Garage[2][! Year ] = |2003| ! Garage[3][! Brand] = |Alfa Romeo| ! Garage[3][! Model ] = |159| ! Garage[3][! Year ] = |2005|NOTA: In this case, we define the value of eachLines of the table. 2.5. Array of Array (multidimensional arrays) Citro\u00ebn ! garage[1][brand]Xsara ! Garage[1][ model ]1999 ! Garage[1][ year ] Renault ! garage[2][brand]Clio ! Garage[2][ model ]2003 ! Garage[2][ year ] Alfa Romeo ! Garage[3][brand]159! Garage[3][ model ]2005 ! Garage[3][ year ][brand] [ model ] [ year ] [1] [2] [3]NOTE: In this case, one increments a new Line atlatable with the value between Parentheses.  "}
{"Headers": "PDMS PML  G-string ", "Content": "PML1 Var! nameOfCE NAME The variable! NameOfCE is of type string and will take the value of the NAME attribute of the current element. Var! posOfCE POS wrt/* The variable! posOfCE is of the string type and takes the valEur of the POSITION attribute of the current element. ! Real1 = 3 ! Real2 = 5 ! Sum =! Real1 +! Real2 ! Average = (! Real1 +! Real2 ) / 2 Operations +, -, *, / are possible in the same way.NOTA: This syntax can be used with all the attributes of an element.3.2. RealIt is possible to concatenate string-type variables. ! String1 = |Hello| ! String2 = |world| ! Result = ! String1 & | | & ! String2 Q var! Result <STRING> 'hello world' 3.3. array Var! Listcollect all PIPE for CE ! List is a string arrayS containing the refnos of all PIPEs ('=23584/5442')PML 1 is a language for performing actions and manipulating variables. This version of the language is mainly used When it is necessary to obtain a value in one lIgne of code, otherwise we will prefer the use of PML2.  "}
{"Headers": "PDMS PML  PML2  ", "Content": "PML2 is a so-called object-oriented language. An object has its own functions (Objects will be more detailed later in this manual).When we define a variable as a STRING object, we associate it with all the functions specific to a STRING object. The functions are used as follows: ! Variable.function (Arguments) 4.1. G-string Here are some examples of essential functionsTielles to manipulate string-type variables. Function. PART( Part to be kept, 'Delimiter') returns a STRING type variable ! Identity = 'DUPONT -Fran\u00e7ois -18/08/1964' ! Name = ! Identity.part ( 1 , ' -' ) Q var! Behalf <STRING> 'DUPONT' ! First name = !Identity.part ( 2 , ' -' ) Q var! First name <STRING> 'Fran\u00e7ois' ! Test = ! Identity.part ( 1 , '/' ) Q var! Behalf <STRING> 'DUPONT -Fran\u00e7ois -18' Function. SPLIT( 'Delimiter' ) returns a variable of type ARRAY ! identityArray = ! Identity.split ( '-' ) Q var!identityArray <ARRAY> [1] <STRING> 'DUPONT' [2] <STRING> 'Fran\u00e7ois' [3] <STRING> '18/08/1964 ' NOTE: An exhaustive list of functions that can be applied to each of the object types can be found in the \"Software Customisation Reference Manual \u00bb"}
{"Headers": "PDMS PML  ARRAY", "Content": "Voici quelques exemples de fonctions essentielles pour manipuler les variables de type ARRAY.\nFonction .SIZE() retourne une variable de type REAL qui indique le nombre de lignes dans la table.\nFonction .DELETE( ) retourne une variable de type ARRAY, suppression de la ligne et de l\u2019index.\n!table[3]. delete ()\nQ var !table\n<ARRAY>\n[1] <STRING> 'un'\n[2] <STRING> 'deux'\n[4] <STRING> 'quatre\u2018\nFonction .REMOVE( REAL ) retourne une variable de type ARRAY, suppression de la ligne et d\u00e9calage de l\u2019index.\n!table.remove ( 3 )\nQ var !table\n<ARRAY>\n[1] <STRING> 'un'\n[2] <STRING> 'deux'\n[3] <STRING> ' quatre '\nFonction .FIND( STRING ) Retourne une variable de type ARRAY contenant les index des lignes correspondantes trouv\u00e9es.\nFonction .FINDFIRST( STRING ) Retourne une variable de type REAL contenant l\u2019index de la premi\u00e8re ligne correspondante trouv\u00e9e\nNOTA surlesfoncions FIND etFINDFIRST : Siaucun \u00e9l\u00e9ment n\u2019est trouv\u00e9 alors une variable sera cr\u00e9\u00e9e mais pas renseign\u00e9e, elle\nsera alors en\u00abunset \u00bb.\nFonction .SORT() Retourne une variable de type ARRAY tri\u00e9e par ordre alphab\u00e9tique (si STRING) ou num\u00e9rique (si REAL)."}
{"Headers": "PDMS PML  Real  ", "Content": "Real Variables of REAL types allow us to faIre of mathematical operations. Function. POWER(REAL) returns a variable of type REAL. Function. SQRT() returns a variable of type REAL. Function. SINE( ) returns a variable of type REAL. Function. COSINE( ) returns a variable of type REAL.Function. TANGENT( ) returns a variable of type REAL. Function. ASIN( ) returns a variable of type REAL. Function. ACOS( ) returns a variable of type REAL. Function. ATAN( ) returns a variable of type REAL. Function. LOG( ) returns a variable of type REAL."}
{"Headers": "PDMS PML ", "Content": " It may be that a variable is not of the desired type it is possible to convert them using specific functions:  It may be that a variable is not of the desired type it is possible to convert them using specific functions:  It may be that a variable is not of the desired type it is possible to convert them using specific functions: .Real(), .string(), . boolean (), position(), ... ! ageSTRING = |23| ! ageREAL =! ageSTRING.real () Q var! ageREAL <REAL> 23Var! posSTRING POS WRT /* Q var! posSTRING <STRING> 'E 12490mm N 12280mm U 2150mm' ! posPOSITION = ! posSTRING.position () Q var! posPOSITION <POSITION> E 12490mm N 12280mm U 2150mm WRT /* EAST <REAL> 12490mm NORTH <REAL> 12280mm ORIGIN <DBREF> =15392/0 UP <REAL> 2150mmQ var! posPOSITION.north <REAL> 12280mm 4 . PML2 4.4. Conversions NOTE: The conversion of variable types is applicable all the time when possible, an alpha and/or alphanumeric character chain does not Cannot be converted into REAL.( Ex:! AgeSTRING =|23years|)Pseudo -attribute \"sequen\": Give the order of the element In relation to his parent "}
{"Headers": "PDMS PML  The conditions", "Content": " Yew IF ( condition ) THEN OrdersENDIF Or, also: IF ( condition ) THEN Orders ELSEIF ( condition ORcondition AND condition ) THEN Orders ELSE Orders ENDIF$*IF (condition) THEN $*END $*IF ( condition ) THEN $*IF NOT IF ( condition ) THEN $*The AND has priority over the OR$*IF NOT $*END 5.2. Comparators EQ EQUAL NEQ NON EGAL GT BIGGER LT SMALLER GE BIGGER OR EQUAL THE SMALLEST OR EQUAL IF ( ! Age GE 18 ) THEN ! Major = TRUE ELSE ! Major = FALSE ENDIF NOTE: As soon as it is necessary to write a surplus orderLines (example the \"if\"), it becomes imperative to go through a macro file, the Window command requiring to validate each line a parune. "}
{"Headers": "PDMS PML  The conditions  ", "Content": "Matchwild IF ( MATCHWILD( ! Name, |? ABC*|) ) THEN Orders ENDIF The MATCHWILD function returns the TRUE value if the search is Conclusion, orFALSE silachaine of characters is not present in The variable to test. 5.4. Game IF ( MATCH( ! Name, |? ABC*|) GE 1 ) THENOrders ENDIF The match function returns the number of times the search (|? ABC*|) Is present in the variable to be tested. The number is larger or equal to 1 is that the research is conclusing. NOTE: We use \"?\" ifUNcharacter is anyone. We Use \"*\"sAll a chain of characters is anyone. Condition matchwild "}
{"Headers": "PDMS PML  The loops", "Content": " C Loops allow you to execute the same command several times, TheyAre controlled by a counter. DO! X FROM 4 TO 10 BY 2 Orders ENDDO ! X Variable incremented automatically at each turn of the loop. If no variable is filled in, an unknown variable will be used. FROM Defines the initial value of the variable for the first round.If the initial value is not entered, then it will be equal to 1. TO Sets the final value of the variable for the last round. If the final value is not filled in, then the loop will be infinite. BY Defines the step of the increment. If the paS is not informed so it will be 1. 6.2. DO Index Using this syntax, the variable! X will value the index of each row of the table ! Mytable. DO! X INDEX! myTable Orders ENDDO 6.3. DO Value Using this syntax, the variable!X will hang the value of each row of the table! Mytable. DO! X VALUE! myTable Orders ENDDO  "}
{"Headers": "PDMS PML  The loops ", "Content": "Estate car If no final \"to\" condition isIs defined for the loop, then it will be infinite. It is possible to stop it by using the \"BREAK\" syntax Related to a condition. DO! X IF ( ! X GT 15 ) THEN Estate car ENDIF ENDDO 6.5. SKIP The \"SKIP\" command is used to go directly to the next value of!XDO! X BREAK IF (! X GT 15 ) ENDDO DO! X IF ( ! X GT 15 ) THEN SKIP ENDIF Orders ENDDODO! X SKIP IF ( ! X GT 15 ) Orders ENDDO NOTE: ! Inset variable (value 1, value 2,...) allows you to verify that the variable is part of a set of predefined values. "}
{"Headers": "PDMS PML  Comments  ", "Content": "The comments Since the codes are not always explicit, it is important to comment on each operation carried out by the macro. This allows during a ModificationN of the code, to find the operation of it more quickly. Several methods are available to comment on a macro. --This is a new comment ! X = ! Y +! Z $*! X is equal to the sum of! Y and! Z $( New comment On several lines $)NOTE: By using the \"PML language\" option in notepad ++(c.f.pml_notepadd ++.xml), comments will be automatically displayed envert  "}
{"Headers": "PDMS PML  Handle ", "Content": "Error management \"HANDLE\" PendaNt the progress of a program, it is possible that some lines of code generate errors and block the continuation of the program. It is possible to manage them with the \"HANDLE\" blocks. HANDLE If errors are expected, the \"HANDLE\" syntax makes it possible not to stop theCode and enter specific commands in case of errors. ANY The command block will be read for any error. ERROR CODE (46, 28), the error code is specific to a specific error, the block of Orders will be read only for this errorELSEHANDLE Allows you to manage several errors NONE The command block will be read if there is no error ENDHANDLE Ends the command block HANDLE (46,28) Orders ELSEHANDLE ANY Orders ELSEHANDLE NONE Orders ENDHANDLE The \"HANDLE\" syntax must beFind directly below the line of code that can generate an error. NOTE: The syntax \"old/elementName\" allows you to decemmettre enCEsurl'element. "}
{"Headers": "PDMS PML  Object oriented  ", "Content": "PML2 object-oriented language The strength of PML2 is the use of objects that make it possible to optimize programs. This technology is inspired by other languages such as The C# developed by Microsoft.9.1. Notion of object !! PHONE Fon directory attributeCtion(argument) Call(number) Web(url)! myPhoneVariable Object ! myPhone = OBJECT PHONE() ! myPhone. directory [X] ! myFunction = ! myPhone.function (argument) ! myPhone.call ('0623589xxx') ! myWeb = ! myPhone.Web ('http://www.rg -services.fr/') "}
{"Headers": "PDMS PML  Object oriented", "Content": "PML2 object-oriented language. DBREF object DBREF objects are elements of the database, the object!! It's defined by default, so!! This.name will return the name of the element Running,!! This type, its type, etc. 9.3. Object COLLECTION() ! myCollection = Object COLLECTION() ! myCollection.scope (CE) ! myCollection.addType ('PIPE') ! allPipe = ! myCollection.results () The equivalent syntax in PML1 is as follows: Var! myCollect Collect all PIPE for CEHere is the variable! myCollect is a table of STRING ( Refno ) and not DBREF.Function(Argument) Reference Description Scope(DBREF) Defines the target for the collection AddType (STRING) Defines the type of item to be collected. Results () Array of DBREF RenvoIe the a table containing the search resultNOTA: The name of an element is stored in a variable in String format, it is then Possible to access the element in the database with the function ! nameElement .dbref ()  "}
{"Headers": "PDMS PML  Functional repertoires ", "Content": "Functional Directories\nIt is possible to add dialog boxes, functions, and objects to those already created by AVEVA. These files must be placed under a \"pmllib\" folder declared in the evars. In this folder, there is a file called \"pml.index\" generated by PDMS that lists all these elements. To update it, you must write in the commands window: Pmlrehash all.\nPMLLIB\nDesign\nForms\nFunctions\nObjects\nDraft Paragon\nPml.index\nNOTE: You can consult the PMLLIB folder in the software installation directory to take examples from the forms, functions, and objects developed by AVEVA."}
{"Headers": "PDMS PML  Role  ", "Content": "Functions, Arguments and References The functions are used for coOf tasks frequently used by other developed programs. They are widely used to divide a development project into specific tasks. The file must have, as extension: *.pmlfnc Command to call the function: !! myFunction ()Create the function: Define Function!! myFunction () . . . EndFunction11.1. The functions ( function ) NOTE: Once the function is created in the \"Functions\" folder of dupmllib, it must Run a \"pml rehash all\" to refresh lepml.index. NOTE: The file *.pmLfnc must have the same name as the function.  "}
{"Headers": "PDMS PML  Role ", "Content": "Functions, Arguments and References As with parameterized macros, it is possible to call a function with arguments.Command to call the function: !! myFunction (! Name,! Age,! City) Create the function: Define Function!! myFunction (! Name isstring,! Age isreal,! City isstring) . . . EndFunction11.2. Functions with arguments NOTE: It is not mandatory dedoNner the same name to the arguments in the call and in the definition of the function, only the order and type of the Arguments are important. It is still advisable to keep the names of the arguments used in the definition of the function.  "}
{"Headers": "PDMS PML  Role  ", "Content": "Functions, Arguments and References The functions are also able to return a result to a program that launched it. Command to call the function: ! Result = !! myFunction (! Name,! Age,!City) Create the function: Define Function!! myFunction (! Name isstring,! Age isreal,! City isstring) isarray ! myResult = array () . . . Return! myResult EndFunction11.3. Functions with referral  "}
{"Headers": "PDMS PML  Creation of objects  ", "Content": "Creation of objects Objects are composed of different methods. Methods are functions attached to an object or a \"form\". Methods Work on the same principle as the functions. It's-I.e. they can receive arguments and send values. One Variable defined in a method is unknown to other methods. To use a variable in several methods of an object, it is necessary to Define as a member of this object outIliser global variables (not recommended). Lavariable! This is automatically equal to the object or \"form\" in which it is used. The file containing the object code must be *.pmlobj to be recognized by PDMS. Define object myObject Member .Member1 is string Member .member2 is real endObject Define method . setMember () ! This.member1 = 'Hello' --! This= !! myObject EndMethod Define method .readmember () $p $! This.member1 EndmethodMembers MethodsObject NOTE: In the same object, two methods littleVent have the same name provided that their arguments are different. "}
{"Headers": "PDMS PML  Creation of objects  ", "Content": "Creation of objects Members MethodsDeclaration of a Instance of the objectCalling a method On the object "}
{"Headers": "PDMS PML  Example of creation ", "Content": "Example of c Reation Of a Diff It is possible to customize the main \"form\" by adding toolbars.You must first create a text file without extension in the Addins folder so that when it is opened, PDMS knows how to get the new Toolbar, with the following information: Then, you have to create an object placed in the folder:\\pmllib \\design \\objectsName: DIFFNAME Object: myOBJECT Directory: myOBJECT Synonym: CALL myOBJECT Define object myOBJECT Endobject Define method .modifyForm () ! This.toolbars () Endmethod Define method .toolbars () ! iconSize = !! comSysOpt.iconSize () Frame .myToolBar toolbar 'myFrame Tag' ! Pixmap = !! Pml.getpathname ('image.png') Button .myButton 'myButton Tag' pixmap \"$! <pixmap >\" width $! iconSize height $! iconSize callback | CallbackCommand | Exit !! appTbarCntrl.addToolbar (myToolBar ', 'ALL')endmethodKeywod ! Pixmap = path to an image in the PMLLIB folder Modules in which the new bar will be displayed Tools (ALL, DESIGN, PARAGON,... "}
{"Headers": "PDMS PML  Forms dialog box", "Content": "A dialog box is a set of gadgets (buttons, options, list, etc.) that offers a graphical interface between the user and the Programmed functions. The file containing the delaform code must be *.pmlfrm to be recognized by PDMS. Necessary and sufficient syntax:Setup form!! myForm $*Declaration of the form !! myForm .initCall =|! This.init()| $*Declaration of the initialization method Options: Setup form!! Myform DIALOG /DIALOG RESIZABLE /DIALOG DOCKING (SIZE width height) DIALOG: Fixed form RESIZEABLE: Non-fixed formDOCKING: Built-in and unfrozen shape (to embed the shape at its opening, it is enough to specify where to hang it, L=Left, R=Right, T=Top, B=Bottom, compared to the graphic view) !! myForm .quitcall =|! This.quit()| $*Definition of the closure method  !! myForm .Autocall =|! This.autocall ()| $*Automatic method declaration, when any delaform attribute is Modified. 14.1. Definition "}
{"Headers": "PDMS PML  Forms gadget ", "Content": "METHOD 1:Gadget 1 PATH DOWN $*Slet down HALIGN CENTRE $*Horizontal alignment Compared to the center VDIST $2*Vertical offset Of 2 units Gadget 2 Gadget $3*the information of Gadget 2 are always Valid PATH RIGHT $* Delay to the Right VALIGN BOTTOM $* Vertical alignmentCompared to the bottom HDIST $3* Horizontal offset Of 3 units Gadget 414.2. Position of gadgets Gadget1 Gadget 2 Gad.3Gadget5 "}
{"Headers": "PDMS PML  Forms gadget ", "Content": "METHOD 2: Gadget1 at X3 Y3Gadget2 atXMIN.Gadget1 YMAX.Gadget1+114.2. Position of gadgets Gadget1X YYMINXMIN YMAXXMAX Gadget3 "}
{"Headers": "PDMS PML  Forms  ", "Content": "Gadget2 atX...Y... Anchor Top + Right14.2. Position of gadgetsGadget2 Gadget3 "}
{"Headers": "PDMS PML  Forms", "Content": "The Gadgets BAR: These are menus located under the title of the \"form\". Bar ! this.bar.add('Control', 'control') $*BAR.add('Text displayed', 'MENU Reference ')Menu .control ! This.control .add('CALLBACK', 'Select CE', '! This.init()') $*MENU .add('TYPE', 'Text displayed' ,'Reference' ) ! This.control .add('Separator ') ! This.control .add('MENU', 'Info', 'info' ) ! This.control .add('TOGGLE', 'active', 'this.activeMethod ()')MENU: The Menus can use: \u25baMenus \u25baMethods/functions \u25baDesToggles (boxes to check) POPUP: Including contextual menus called parunclicdroit. Menu .menupopup ! This.menupopup .add('CALLBACK', 'Select CE', '! This.init()') To attach a popup menu toungadget:! myGadget .setpopup (! This.menupopup ) NOTE: The forms of type DOCKING and RESIZEABLE do not netoledeBAR. "}
{"Headers": "PDMS PML  Forms  ", "Content": "The Gadgets BUTTON: Without icon: Button .myButton |BUTTON |atxpos ypos tooltip |description |CALLBACK |Callback Command |dock/ anchor With icon: Button .myButton pixmap width 50height 17atxpos ypos tooltip |desc |CALLBACK |Callback Command |dock/ anchor In the initialization method: ! This.myButton .addPixmap (!! pml.getPathname ('icon .png'))  LinkLabel: Button .myButton LinkLabel|BUTTON |atxpos ypos tooltip |description |CALLBACK |Callback Command |dock/ anchor  Attributes: . Tag: Title / name dugadget (STRING) . Val: Equal to TRUE when the button is clicked (BOOLEAN). Popup: Context menu attached (MENU) . Active: Greyed active (BOOLEAN) . Visible: Visible or not (BOOLEAN) . Callback:Command / Attached method (STRING) . Background:Background color (REAL /STRING)NOTE: The icons must be in the PMLLIB challenge folderNit for them to be filled in in lepml.index.  "}
{"Headers": "PDMS PML  Forms  ", "Content": "The Gadgets  Toggle: The .valgarde attribute the TRUE value after the click Button .myButton TOggle| BUTTON |atxpos ypos tooltip |description |CALLBACK |Callback Command |dock/ anchor "}
{"Headers": "PDMS PML  Forms ", "Content": " - Gadgets\n\nLIST:\nList.myList |ListTitle|atxpos ypos dock/ anchor CALLBACK |Callback Command |multiple width 35 height 15\n\nAttributes:\n.Dtext: Visible field (ARRAY of STRING)\n.Rtext: Invisible field (ARRAY of STRING with the same number of values as Dtext)\n.Val: Number of selected line(s) (REAL or ARRAY for multiple selection)\n.Pickedfield: Last selected line (REAL)\n.Tag: Title of the gadget (STRING)\n.Active: Active or grayed out (BOOLEAN)\n.Visible: Visible or not (BOOLEAN)\n.Popup: Attached context menu (MENU)\n.Callback: Attached command/method (STRING)\nRetrieving values from selected fields:\n!val = !this.myList.val\n!dtext = !this.myList.dtext\n!rtext = !this.myList.rtext\nDO !refvalue !val\n$p$!dtext[$!ref]\n$p$!rtext[$!ref]\nENDDO\nSingle or multiple selection"}
{"Headers": "PDMS PML  Forms ", "Content": " The Gadgets OPTION: Option .myOption |Option Title|atxpos ypos CALLBACK |Callback Command |dock/ anchor width 10\u25baAttributes: . Dtext: Visible field (ARRAY ofSTRING) . Rtext: Invisible field (ARRAY ofSTRING with the same number of values as ledtext) . Val: Selected line number (REAL or ARRAY silalisteesten multiple selection) . Pickedfield: Last line selected (REAL). Tag: Title dugadget (STRING) . Active: Greyed active (BOOLEAN) . Visible: Visible or not (BOOLEAN) . Popup: Context menu attached (MENU) . Callback:Command / Attached method (STRING) \u25baRetrieval of the values of the selected fields: The results are found more simply :$!this.myOption returns the delatable value of substitution (! this.myOption .rtext )of the selected field.  "}
{"Headers": "PDMS PML  Forms ", "Content": "The Gadgets TEXT (The user can enter text):Text .myText dock/ anchor atxpos ypos tooltip |Desciption |CALLBACK |Command |width 20isSTRING \u25baAttributes: . Echo: Display of fields or****(BOOLEAN) . Val:Value entered in the field( =DATATYPE) . Scroll: Max length of characters (REAL) . Tag: Title (STRING). Active: Greyed active (BOOLEAN) . Datatype: 'STRING', 'REAL' or 'BOOLEAN' (STRING) . Popup: Context menu attached (MENU) . Callback:Command / Attached method (STRING) . Editable: Editable or frozen (BOOLEAN) PARAGRAPH (the user of a text is not possible):Paragraph .myPara dock/ anchor atxpos ypos text |Paragraph |width 10height 1 \u25baAttributes: . Val: Value duchamp (SRTING) . Tag: Title (STRING) . Active: Greyed active (BOOLEAN) . Popup: Context menu attached (MENU) . Background:Background color (REAL/STRING) TVariable ype (Isstring or isreal) "}
{"Headers": "PDMS PML  Forms ", "Content": "The Gadgets TOGGLE Checkbox: Toggle .myToggle |TEXTE| atxpos ypos tooltip |Desciption |tagwidth 10\u25baAttributes: .val:Returns TRUE sileTOGGLE is clicked (BOOLEAN) .tag:Title (STRING) COMBOBOX Combines a text and an option: Combobox .myCombo |Title|dock/ anchor atxpos ypos CALLBACK |command |tagwidth 10width 10 \u25baAttributes: . Val: Number of the line of the selected options (REAL). Dtext: Visible field (ARRAY ofSTRING) . Rtext: Invisible field (ARRAY ofSTRING having the same number of value as ledtext) . Editable: Editable or not (BOOLEAN) . Scroll: Max length of characters (REAL) . Count:Number of choices in the list(REAL)Tag lengthLength of the tag Length of the field of Seizure  "}
{"Headers": "PDMS PML  Forms ", "Content": "The Gadgets FRAME: Frame .myFrame |Title|atxpos ypos dock/ anchor width 80height 15 \u25baAttributes:.tag:Title (STRING) .Visible: Visible or not (BOOLEAN) \u25baOption Foldup The foldup option allows you to make a drop-down Frame Frame .myFrame foldup |Title|atxpos ypos dock/ anchor width 80height 15 \u25baOption Tabset Allows you to have several tabs in a frameFrame .myFrame TABSET |Title|atxpos ypos dock/ anchor width 80height 15 Frame .tab 1 Exit Frame .tab 2 Exit Exit  "}
{"Headers": "PDMS PML  Forms ", "Content": "Form structure Setup form!! myForm $*Declaration of the form !! myForm .initCall =|! This.init()| $*Declaration of the initialization method Frame .myFirstFrame Foldup ... $*Definition of theFrame Button .button 1... Button .button 1... Exit $*FindelaFrame Frame .mySecondFrame Foldup ... List.myList .... Toggle .myToggle ... Exit Menu .myMenu ! this.myMenu .add(....) Member .name isstring $*Definition of members of theForm Member .age isREAL EXIT $*End of theForm definition Define Method .myForm () $*Definition of the construction method that will be executed duringOrders $*from theForm download EndMethod Define Method .init() $*Definition of the initialization method that will be executed during Orders $*the delaform display EndMethod "}
{"Headers": "PDMS PML  Forms ", "Content": "ALERT() object ! myAlert =!! Alert .confirm (|Do you want to continue? |) If(! myAlert eq'YES')then Orders Endif NOTE: We see here that the same object can integrate several forms. Function(Argument) Reference Description Confirm (MessageSTRING)'YES' or 'NO' Displays a question with the possibility of answering 'YES' or 'NO' Error (Message STRING) 'YES' Displays an error message Message(Message STRING)'YES' Displays a message Question(Message STRING)'YES', 'NO', 'CANCEL'Post a questionWarning(Message STRING)'YES' Displays a message Input(Message STRING, Default value STRING)STRING Displays a field that the user must fill in, a value by Defect can be filled in.  "}
{"Headers": "PDMS PML  Forms ", "Content": "Syscom The easiest way to communicate with Windows is the integration of simple commands in DOS. --Sil'address! Directory does not exist, so create it ! Directory ='C:\\temp \\logFolder ' SYSCOM 'IFNOT EXIST \"$!Directory\" mkdir \"$! Directory\"' --File deletion! Line SYSCOM 'DEL \"$! File\"' --Opening a *.txt file SYSCOM 'Explorer .exe''C:\\temp \\test.txt'' ' NOTE: No referral is available with Syscom commands.  "}
{"Headers": "PDMS PML  Communicate with the Windows environment ", "Content": "LeC#is a recommended language for programming on Windows, it is inspired by JAVA and C++. LeC#estassoci\u00e9 auneFramework . NET is a DLL library, a file format of software libraries files. NOTE: Libraries must be imported only once, otherwise an error message appears. It's for That it is wise to use the codeFollowing after importing the DLL: \"Handle any Endhandle \u00bb15.2. Introduction of the C# and the Framework. Net 15.3. Dynamic Link Librairy (DLL) or Assembly A DLL is a library containing ready-to-use function classes and data that can be used at the same time bySeveral programs. PDMS uses an uncertain number of DLLs that we find in the PDMS installation folder. We can, from macros programmed in PML, use these libraries provided that they are [PMLNetCallable ]. The PMLNet assembly.Dllestlapasserelle that allows you to integrate the DLLentant as reference in PDMS. It's only if DLLs use This gateway that they are [PMLNetCallable ], To use a DLL in a PML program, you must first load the library with the commAnde: import 'library name'. "}
{"Headers": "PDMS PML  Communicate with the Windows environment ", "Content": "Then you have to indicate the spaceNames used with the code:using namespace 'space name'. They bring together slots of variables, objects, Functions, this allows the program to know where to get its variables. A frequently used name space is 'Aveva. Pdms . Presentation '. LesbiLibraries that can contain several classes containing several functions themselves, we must define which one we want to use. It's necessary So define a PML object in this way:! Myvar =object nomobject () Once the object is defined, we can know ifMethods entering the command \"QMETH! myVar\" in the \"command window\". Recommended software: JetBrains dotPeek, Freeware It allows you to open and decompile the content of DLLUsingNameSpace1 \u2022! Name = Jacques \u2022! Age = 32 \u2022Function split()UsingNameSpace2 \u2022! Name = Francois\u2022Function create () Name of the DLL Namespace Object "}
{"Headers": "PDMS PML  Communicate with the Windows environment with PMLFileBrowser", "Content": "DLL: 'PMLFileBrowser'\nNamespace: 'Aveva.Pdms.Presentation'\n\nOBJECT PMLFILEBROWSER:\nAllows displaying the Windows navigation window to save and open files.\nOur object must be defined with an argument ('SAVE' or 'LOAD') to indicate whether we want to save or open a file.\nThen, to display the file search window, we need to call the 'show' method of our Object with several arguments:\nstring path: Default path\nstring seedFile: Default file name\nstring title: Title of the window\nbool existFlag: Allows or disallows the creation of a new file\nstring filter: Type of file to save or open\ndouble filterIndex: If multiple filters are defined, the filterIndex indicates the default one.\n\nOnce the file is selected, its path must be retrieved using the 'file' method:\n!myFile = !browser.file()"}
{"Headers": "PDMS PML  Communicate with the Windows environment", "Content": "OBJECT PMLFOLDERBROWSER: Allows you to display the Windows navigation window to select a folder. For this object, there is no argument to enter when defining. To display the file search window, you must call the method'sHow' denotre Object with two arguments: String description: description text intended for the user Bool showNewFolderButton: the user right to create a new folder15.4. PMLFILEBROWSER.DLL Once the file is selected, it is necessary to recover itsNpath using the 'SelectedPath' method: ! myPath =! Browser . SelectedPath ()  "}
{"Headers": "Form Concepts Overview  ", "Content": "A type of object represented by a global variable  Owns a set of predefined member variables and built -in Methods \uf0a8It can also have user -defined members Form variables, form gadgets It can also have user -defined methods Form members are always accessed using the dotNotation Example: !! MyForm.Textfield Form name Form member "}
{"Headers": "Form Concepts Overview  ", "Content": "GadgetS own a set of predefined member variables and Built-in methods and can be accessed using the dot Notation Example: !! MyForm.Textfield.Val \uf06eCallbacks are user -defined actions assigned to a form And its gadgets and that are executed when the Operator interacts with the formVantage Plant Design Software Customization Reference Manual con tains A list of all the members and methods of forms and gadget typesGadget as a member Member variable "}
{"Headers": "Naming Forms ", "Content": "Their Members Format: !! MyForm $* name of the form !! MyForm.GadgetName $* name of a gadget on a form !! MyForm.GadgetName.Val $* data value held by that Gadget Within the forM definition, the members should be referred to by Using! Thisto replace the form name part of the gadget name. From the above example: ! This.GadgetName $* just equal to !! Myform.GadgetName ! This.GadgetName.Val $* just equal to!! Myform.GadgetName.Val PML1 (obsolete method but still supported): _GadgetName $* just equal to !! Myform.GadgetName "}
{"Headers": "Forms  ", "Content": "Syntax: Setup form!! Formname............ Exit Example: Setup form!! Hello Paragraph . Message text 'Hello world ' Button . Bye 'Goodbye 'OK Exit paragraph command adds a paragraph gadget Message is the name of the gadget and the dot( .) indicates that the gadget is a Member of the form \uf0a8buttOncommand adds a button gadget named . Bye.The text on the button will be'Goodbye ' The keyword OKis aform control attribute that specifies that the action of this button is to Remove the form from the screen "}
{"Headers": "Form Attributes  ", "Content": "Form Types: MAIN DOCUMENT DIALOG BLOCKINGDIALOG Examples: Setup form!! MyFormdialog dock left -creates a resizable docking dialogSetup form!! MyFormdialogresizeable -creates a resizable floating dialog Setup form!! MyFormdialog -creates a non -resizable floating dialog Setup form!! MyForm -creates a non -resizable floating dialog Setup form!! MyFormdocument -creates a resizable MDI child documentSetup form!! MyFormblock -creates a non -resizable blocking dialog Setup form!! MyFormblockresizeable -creates a resizable blocking dialog "}
{"Headers": "Form Attributes ", "Content": "Minimum Size and Resizability A form will automatically stretch to fit the gadgets you Add to it You can use the SIZEkeyword to give minimum size in Multiples of the character width and line height Setup form!! MyFormsize 25.5 10 \uf0a8TheRESIZEABLE command means that the form will be Displayed with re -sizing controls at its corners Setup form!! MyFormresizeable Setup form!! MyFormsize 25.5 10resizeable "}
{"Headers": "Form Title and Icon Title ", "Content": "TheTITLEsub-command is used to supply a string that is displayed in Its banner at the top of the form 's window TheICONTITLE sub-commandIs used to supply a string that is used When a form is iconized Setup form!! MyForm ............ TITLE 'My Form Title ' ICONTITLE 'Short Title ' ............ Exit Gold Setup form!! MyForm ............ ! This.FormTitle = 'My Form Title ' ! This.IconTitle = 'Short Title ' ............ Exit "}
{"Headers": "Form Callbacks ( Initcall) ", "Content": "The form 's initialization callback allows the form 's gadgets to beInitialized to reflect the current state of the application You can set the callback by assigning to the form 'sinitcallmember: Setup form!! MyForm ............ INITCALL '! This.init() ' ............ Exit Gold Setup form!! MyForm ............ !! Myform.InitCall = '! This.init() ' ............ Exit "}
{"Headers": "Form Callbacks ( OK) ", "Content": "TheOKCALL callback allows the operator to Approve the current gadget settings You can assign to the form 'sOKCALL member by: Setup form!! MyForm ............ OKCALL '! this.approveData1() ' ............ Exit You can modify the OK callback at any time using, ! this.OKCall= '! this.approveData2() ' "}
{"Headers": "Form Callbacks ( Cancel) ", "Content": "TheCANCELCALL callback allows the operator Not to proceed with the function of the form You can assign to the form 'sCANCELCALL Member by:Setup form!! MyForm ............ CANCELCALL '! this.cancelForm1() ' ............ Exit \uf06eYou can modify the Cancel callback at any time using, ! this.CancelCall = '! this.cancelForm2() ' "}
{"Headers": "Form Callbacks ( Quitcall ) ", "Content": "TheQUITCALL callback is executed whenever the user Presses the QUIT/CLOSE icon (X) on the title bar of forms You can assign to the form 'sQUITCALL member by:Setup form!! MyForm ............ QUITCALL '! this.quitForm1() ' ............ Exit \uf06eYou can modify the Quit callback at any time using, ! this.QuitCall= '! this.quitForm2() ' "}
{"Headers": "Form Control Attributes ", "Content": "A button may optionally have a form control Attribute which takes effect after the callback Command is invoked Control Attributes: OK APPLY CANCEL RESET HELP "}
{"Headers": "Form Control Attributes ", "Content": "Examples: Button . Ok 'OK 'callback'!! MyOKFunction 'OK Button . Apply 'Apply 'callback $'!! MyApplyFunction 'APPLY Button . Cancel 'Cancel 'callback $ '!! MyCancelFunction 'CANCEL Button . Reset 'Reset 'RESET Button . Help 'Help 'HELP You can only have one of each type of control Attribute on any form except for APPLY which may Be used on several buttons"}
{"Headers": "A Simple Form ", "Content": "Example ( simpleForm.pmlfrm ): Setup form!! simpleForm Title 'My Form ' Icontitle 'Myform'Paragraph .message text 'Hello world! ' Button .bye 'Goodbye 'ok Exit "}
{"Headers": "The Form Definition File", "Content": "Should be held one per file.\nThe file should be stored in a directory pointed to by the PMLLIB environment variable.\nFilename must have suffix .pmlfrm.\n!!MYFORM or!!MyForm or!!myform all correspond to myform.pmlfrm.\nBegins with setup form and ends with exit.\nAny method definitions should follow the exit command.\nEach method begins with define method and ends with end method.\nIn particular, it will contain the form's default constructor method.\nThis method has the same name as the form and no arguments.\nThe only method called automatically when the form is loaded.\nUsed to set default values for the gadgets of the form.\nThe form may be given an initialization method.\nWhich is run whenever the form is shown.\nNo executable statements should appear in the file outside the form\ndefinition or form methods.\nBut comments can be put anywhere in the file."}
{"Headers": "Loading and Displaying ", "Content": "Forms PML will automatically load an object or form from file When first used To display a form (can either be free -standing or as a member of A form family): Show!! Formname $* default is a child form Show!! Formnamefree \uf0a8Removing or hiding from the screen:Hide!! Formname Redefining a form once loaded: Pmlreload form!! Formname Loading a form: Loadform!! Formname "}
{"Headers": "Loading and Displaying ", "Content": "Forms Note: If you show the form again, it will appear on The screen but its definition is already known so it Will not be loaded again Removing a form definition: Kill!! Formname "}
{"Headers": "Some Built -in Methods ", "Content": "For Forms A variety of useful method calls have been Provided: To show a form: !! MyForm.Show() !! MyForm.Show( 'FREE ') !! MyForm.Show( 'At ',0.3,0.5) $* automatically FREE To hide a form: !! MyForm.Hide() To query whether a form is currently shown: If (!! MyForm.Shown()) then ......... Endif "}
{"Headers": "Form Member Variables ", "Content": "Used to store additional information on a form which will Not be displayed to the user \uf0a8These are variables which can be any of the PMLdata types, Including ARRAYS and OBJECTSSetup form!! MyForm ............ Member . MyNumberis REAL Member . MyStringis STRING Member . MyArrayis ARRAY ............ Exit The value of a form member can be set and used in just the Same way as an object member ! this.MyNumber= 42 ! this.MyString= 'Gadz ' ! Num = ! this.MyNumber"}
{"Headers": "Form Gadgets ", "Content": "There are many kinds of form gadgets Two common aims in defining gadgets on the Form Define tHe area to be taken up on the form Define the action to be taken if the gadget is Selected Each gadget size and position determines the Area taken up The action is defined by the gadget 'sCALLBACK "}
{"Headers": "Callbacks ", "Content": "Any selectable gadget has a callback which Is defined at the time the gadget is created The callback can do one of the three things: Show a form Execute a command directly Run a function or method"}
{"Headers": "Callbacks ", "Content": "Example: Setup form!! MyForm Paragraph . Message text 'Hello world ' Button . Change 'Change Message 'callback $|! this.Message.Val = 'Modified '| Button . Bye 'Goodbye 'OK Exit \uf0a8a gadget callback is defined by the callback command followed by a Command or PML functions enclosed in text delimiters \uf0a8for defining complicated callback, it is recommended to use a form Method"}
{"Headers": "Callback Example ", "Content": "For a callback to call a function Setup form!! MyForm ............ Button . Query 'Query 'callback'!! queryCatalogueDetails () ' ............ Exit For a callback to call a method Setup form!! MyForm ............ Button . Query 'Query 'callback'! this.queryDetails () ' ............ Exit "}
{"Headers": "Callback Example ", "Content": "Showing another form from a form gadget Setup form!! MyForm ............ Button . Gadz 'Show Gadz Form 'callback 'show!! gdzMainForm ' ............ Exit Gold Setup form!! MyForm ............ Button . Gadz 'Show Gadz Form 'form!! gdzMainForm ............ Exit "}
{"Headers": "Callbacks: Form Methods ", "Content": "Most callbacks require more than a singThe command, so invoking a method Or function or macro is an essential requirement \uf0a8Example: Setup form!! MyForm Title 'Display Your Message ' Paragraph . Message width 15 height 1 Text. Capture 'Enter message: 'width 15 is STRING Button . Bye 'Goodbye 'OK ExitDefine method. MyForm() $* default constructor \u2013set gadget default values ! this.Message.Val = 'Hello world! ' ! this.Capture.Callback = '! this.Message.Val = ! this.Capture.Val ' ! this.OKcall= '! this.Success() ' Endmethod Define method. Success() ! this.Message.Val = 'Hello again! ' ! this.Capture.Val = '' Endmethod "}
{"Headers": "Callbacks: Form Methods ", "Content": "The greAt advantage of methods is that you can pass Variables as arguments to the method and it can also Return a result just like a PML function Example: Define method. Success(! Output is GADGET, ! Input is GADGET) ! output.Val= 'Hello again! ' ! input.SetFocus()Endmethod Define method . setGadget(! Output is GADGET) is BOOLEAN ! output.Val= 'Gadget initialized! ' Handle any Return FALSE Endhandle Return TRUE Endmethod "}
{"Headers": "PML Open Callbacks ", "Content": "When the operator interacts with a GUI, an event occurs Example: Types something into a field on a form Moves the cursor into a window Presses down a mouse button Etc. Application sOftware defines a set of meta-eventsfor Forms and gadgets \uf06eWhen a meta -event occurs, the application software Checks for user -defined callbacks and execute them "}
{"Headers": "PML Open Callbacks ", "Content": "Simple assigned callback is insufficient to fully exploit the Gadget's possible behaviors To overcome this shortcoming, we can use OPEN CALLBACKS to Allow the AppWare to be informed whenever a meta event isEncountered Open Callback: Define method. Control(! Object is GADGET, ! Action is STRING) Object is aForms and Menus object (i.e. a form, gadget, or Menu)! Action is the meta -event that occurred on the object and Represents the action to be carried out by the method"}
{"Headers": "PML Open Callbacks ", "Content": "The open callback is a string of the form: '! this.MethodName(' Note the open bracket '('(no arguments andNo closing bracket). The callback is to an openmethod or function "}
{"Headers": "PML Open Callbacks Example", "Content": "An open callback to a multi -choice list gadget: Setup form!! Open Title 'Test Open Callbacks ' List . Choose callback '! this.Control('multi width 15 height 8 Exit Define method. Open() Do! I from 1 to 10 ! Fields[! I] = 'list field $! I ' Enddo ! This.Choose.Dtext = ! Fields Endmethod Define method. Control(! Object is GADGET, ! Action is STRING) If (! Actioneq 'SELECT ') then --Find out all about our gadget object ! Form = ! object.Owner() ! Type = ! object.Type() ! Name = ! object.Name() ! Field = ! object.PickedField! Fieldtext= ! object.Dtext[! Field ] $P Selected $! Form$n. $! Name$! Type Field $! Field Dtext{$! Fieldtext } Elseif(! Actioneq 'UNSELECT ') then ! Field = ! object.PickedField $P Unselect field $! Field Endif Endmethod "}
{"Headers": "PML Open Callbacks ", "Content": "It is also be essential if we use PML functions as Open callbacks Define function!! Control(! Object is GADGET, ! Action is STRING)............... Endfunction List of objects that can have open callbacks is Found Vantage Plant Design Software Customisation Guide Section,"}
{"Headers": "Gadget Definition Commands", "Content": "Types of Gadgets:\nFRAME\nPARAGRAPH\nBUTTON\nTOGGLE\nRGROUP\nOPTION\nLIST\nDATABASE SELECTOR\nTEXT\nTEXTPANE\nVIEW\nSLIDER\nRTOGGLE"}
{"Headers": "Gadget Size Management ", "Content": "User Specifiable Tagwidth for TEXT, TOGGLE, OPTION And RGROUP Gadgets TEXT, TOGGLE, OPTION andRGROUP gadgets support theTagwidth syntax Tagwidth specifies the size of the gadget 's tag field in grid Width units Option. ELLISTtagwid7 |Element Id| width 4 \uf06eThe actual tag may have more characters than the Declared Tagwidth and still fit in the tag field  "}
{"Headers": "Gadget Size Management ", "Content": "Specifying Gadget Size Relative to Other Gadgets Example: Frame .fr1 'Frame 1 'at x0 y0 width 10 height 10............... Exit Frame .fr2 'Frame 2 'atxminyminwidth.fr1 height 15 ............... Exit "}
{"Headers": "Gadget that Support Pixmaps", "Content": "some gadgets support pixmaps as content as an alternative to text e.g.Buttons,Toggles, andParagraphs Pixmaps arepixelated pictures held in files of type .png Default size for pixmaps is assumed to be 32x32 pixels Whenpixmaps are required, you will need to specify pathnames to the pixmap file \uf0a8Maximum required size of the image Button . But1pixmap/C:\\pic.pngwidth 26 height 26 \uf06eUsingAddPixmap ()Method: Button . But1pixmapwidth 26 height 26 \uf0a8In the constructor method: ! This.but1. AddPixmap( 'C:\\pic.png ') "}
{"Headers": "Gadget Members ", "Content": "Members Contained by All Gadgets Visible Active Callback Tag \uf0a8Making gadgets visible and invisible !! MyForm.List1. Visible = FALSE $* Invisible !! MyForm.List1. Visible = TRUE $* Visible Activating and de -activating gadgets !! MyForm.List1. Active = FALSE $* From -activate !! MyForm.List1. Active = TRUE $* Activate "}
{"Headers": "Gadget Members ", "Content": "Setting Keyboard Focus Thekeyboard focus defines which gadget will receive keystrokes !! MyForm.KeyboardFocus = !! MyForm.Gadget This can be moved at any time to another gadget using the SetFocus ()method !! MyForm.Textfield.SetFocus () "}
{"Headers": "Frame Gadgets ", "Content": "Frame gadgets provide visual grouping of gadgets on a Form \uf0a8Frame Definition: Frame . MyFrameat x0 y3 'My Frame' ..................... Exit Frame Size: Automatically expands downwards and to the right when gadget is Added but you can specify default sizeFrame . MyFrameat x0 y3 'My Frame 'width 25 height 5 ..................... Exit  "}
{"Headers": "TabsetFrames ", "Content": "A frame with tab pages TabsetFrame Definition:Frame . MyFrametabsetwidth 25 height 5 Frame . Tab1 'Tab 1 ' ............... Exit Frame . Tab2 'Tab 2 ' ............... Exit Exit  "}
{"Headers": "Paragraph Gadgets", "Content": "Paragraph gadgets are simple named gadgets which Allow piece of text or a pixmap to be displayed on the Form Textual Paragraph Gadgets: Paragraph . Message text 'Text String ' Paragraph . Message at ......text 'Text String 'width 16 lines 7 Paragraph .Message at ......background 2 width 20 lines 2 Pixmap Paragraph Gadgets: Paragraph . Picture at ......pixmap/C:\\pic.png Paragraph . Picture at ......pixmap/C:\\pic.pngwidth 30 height 30 \uf06ePixmap may be changed any time by assigning a new value to the . Valmember: !! MyForm.Picture.Val = /C:\\newpic.png  "}
{"Headers": "Button Gadgets ", "Content": "Also called control button , usually displays a child form or invoke aCallback (typically a PML Form method) Tag,pixmap, callback, and child form are all optional Button . SubForm 'More ...'form!! ChildForm Button . SubFormpixmap/C:\\pic.pngform!! ChildForm Button . Calculate 'Calculate 'callback '! this.Calculate() ' Button . But1 'More ...'At......width 10 height 1 Toggle Mode Buttons: Button . But1 toggle pixmap/C:\\unselectpic.png /C:\\selectpic.png/C:\\inactivepic.png width 16 height 16 Tooltip 'This is a toggle button '  "}
{"Headers": "Toggle Gadgets ", "Content": "Are used for independent on/offsettings Opposed to a radio group Example: Toggle . Bold 'Bold ' Toggle . Italic 'Italic' Toggle . Underline 'Underline ' \uf06eUsingPixmap: Toggle .GridOnpixmap/C:\\gridon.pngcallback '! this.enableGrid() '  "}
{"Headers": "RGroup Gadgets ", "Content": "Used to allow selection of oneOf a small fixed number of choice s Example: rgroup.MyRGroup 'Choices: 'horizontal callback '! this.Select() ' Add tag 'Red 'select 'RED ' Add tag 'Blue 'select 'BLUE ' Add tag 'Green 'select 'GREEN 'callback '! this.RadAction() ' Exit TheSELECTkeyword inThe addcommand defines its replacement Text string (RTEXT) \uf06eWhen querying current selection using Selection() method, it will Return the RTEXTstring of the selected button If (!! MyForm.MyRGroup.Selection ()eq 'RED ') then ......... Endif  "}
{"Headers": "RToggle Gadgets ", "Content": "Very similar to TOGGLE gadget, but is allowed only in FRAMES, where they operate together to form a set of RaDio buttons similar to RGROUP gadget \uf06eExample: Frame . MyFrame 'Frame 'atxminymin rtoggle.Rad1 'Radio Button 1 'callback '! this.Control(' rtoggle.Rad2 'Radio Button 2 'callback '! this.Control(' rtoggle.Rad3 'Radio Button 3 'callback '! this.Control(' Exit  "}
{"Headers": "Option Gadgets ", "Content": "Offers a single choice from a list of items The items on the list can be either pixmaps or Text strings but not a mixture Contains two parallel lists of the same length in ARRAY format Display values (DTEXT) \uf0a8Replacement values (RTEXT) "}
{"Headers": "Textual Option Gadgets ", "Content": "Width of a textual option gadget must be Specified Example: Option. Colour 'Colours 'at......callback '!! MyFunc() 'width 10 ! ColourDtext[1] = 'Color Black ' ! ColourDtext[2] = 'Color White ' ! ColourDtext[3] = 'Color Red '! ColourRtext[1] = 'Black ' ! ColourRtext[2] = 'White ' ! ColourRtext[3] = 'Red ' ! this.Colour.Dtext = ! ColourDtext ! this.Colour.Rtext = ! ColourRtext  "}
{"Headers": "Pixmap Option Gadgets ", "Content": "Gadget shape must be specified using WIDTH Keyword and either HEIGHTorASPECT \uf0a8DTEXTmember will be the pixmap'sfilename Example: Option. Circle 'Circles 'at......callback '!! MyFunc() 'pixmapWidth 256 height 128 ! CircleDtext[1] = 'C:\\circle1.png ' ! CircleDtext[2] = 'C:\\circle2.png ' ! CircleRtext[1] = 'Circle 1 ' ! CircleRtext[2] = 'Circle 2 ' ! this.Circle.Dtext = ! CircleDtext ! this.Circle.Rtext = ! CircleRtext  "}
{"Headers": "Option Gadgets ", "Content": "Setting and Getting the Current Selection Setting selection using Select() Method: !! MyForm.Colour.Select( 'Dtext ','ColorBlack ')!! MyForm.Colour.Select( 'Rtext ','Black ') !! MyForm.Circle.Select( 'Dtext ','C:\\circle1.png ') \uf0a8Reading the selection using Selection() Method: ! Selected = ! this.Colour.Selection () ! Selected = ! this.Colour.Selection( 'Dtext ') ! Selected = ! this.Colour.Selection( 'Rtext ')"}
{"Headers": "Slider Gadgets ", "Content": "Allows you to interactively to Generate values in a specified Range, at specified steps Supports vertical andhorizontalFrame .fr1 'Slider 'atxminymaxwidth 10 Text .txt width 3 is REAL Slider .sldhorizontal callback '! this.ControlSlide (' Range-50 +50 step 5val0 width 5 Exit Responds to left -mouseSLIDER START, MOVE, andSTOP Events  "}
{"Headers": "List Gadgets ", "Content": "Allows you to interactively to\ngenerate values in a specified\nrange, at specified steps\nSupports vertical andhorizontal\nframe .fr1 \u2018Slider \u2019atxminymaxwidth 10\ntext .txt width 3 is REAL\nslider .sldhorizontal callback \u2018!this.ControlSlide (\u2019\nrange-50 +50 step 5val0 width 5\nexit\nResponds to left -mouseSLIDER START, MOVE, andSTOPevents"}
{"Headers": "List Gadgets ", "Content": "Multiple Choice List Gadgets List . Components 'List 'multiple width 25 lines 15 ! ComponentDtext[1] = 'ELBO1 '! ComponentDtext[2] = 'FLAN1 ' ! ComponentRtext[1] = '=1565/1543 ' ! ComponentRtext[2] = '=1565/1544 ' ! this.Components.Dtext = ! ComponentDtext ! this.Components.Rtext = ! ComponentRtext Querying selected values Single choice list gadget returns a STRING MulTiple choice list gadget returns an ARRAY of STRINGS  "}
{"Headers": "Form Exercise 1 ", "Content": "Create the following form. Upon the form is initialized;Default value in textbox: 0 Default frame tag: 'Sequence Frame ' Upon choosing 'Fibonacci ' Button; Frame tag: 'Fibonacci Sequence ' The sequence is shown inside the Frame. Upon choosing 'Hailstone ' Button; Frame tag: 'Hailstone Sequence' The sequence is shown inside theFrame.  "}
{"Headers": "Form Exercise 1 ", "Content": "Use the functions you created in the previous exercises 3 & 4 Found in Part 1.Handle invalid input ( 0 and string ). Input should be a REAL Object. Define a constructor method. "}
{"Headers": "Multi-Column List Gadgets ", "Content": "A list gadget with a COLUMNS keyword Column Oriented -SETCOLUMNS() List . Components columns single zeroselectionwidth 25 lines 15 ! Head[1] = 'Name ' ! Head[2] = 'Type ' ! Col[1][1] = 'Flange_B1 ' ! Col[1][2] = 'Elbow_B2 '! Col[2][1] = 'Type is Flange ' ! Col[2][2] = 'Type is Elbow ' ! Rtext[1] = '=156/256 ' ! Rtext[2] = '=157/257 ' ! this.Components.SetHeadings(! Head ) ! this.Components.SetColumns(! Col ) ! this.Components.Rtext = ! Rtext \uf06eCan be apply to Multiple Choice List gadget also"}
{"Headers": "Multi-Column List Gadgets ", "Content": "Row Oriented -SETROWS() List . Components columns single zeroselectionwidth 25 lines 15! Head[1] = 'Name ' ! Head[2] = 'Type ' ! Row[1][1] = 'Flange_B1 ' ! Row[1][2] = 'Type is Flange ' ! Row[2][1] = 'Elbow_B2 ' ! Row[2][2] = 'Type is Elbow ' ! Rtext[1] = '=156/256 ' ! Rtext[2] = '=157/257 ' ! this.Components.SetHeadings(! Head ) ! this.Components.SetRows(!Row ) ! this.Components.Rtext = ! Rtext DTEXTstring is held as a 'horizontal tab 'character separated String of column data "}
{"Headers": "Database Selector Gadgets ", "Content": "A special kind of list gadget Provides a mechanism for Displaying the current database Element along with its owner And members User can interact with a selector To change the current element Selector. Salt 'Selector: 'single width 12 height 5 DATABASE Selector. Selmultiple width 12 height 5 DATABASE OWNERS Selector. Selmultiple width 12 height 5 DATABASE MEMBERS Selector. Selsingle width 12 height 5 DATABASE AUTO Selector. Selcallback '! this.Mylist('single width 12Height 5 DATABASE  "}
{"Headers": "Database Selector Gadgets ", "Content": "DATABASE keyword is mandatory OWNERS andMEMBERS are optional AUTOandMULTIPLE cannot be used together To get and set values for a selector: Selection() \u2013get value Select() \u2013set value ! Element = ! this.Sel.Selection () RTEXTandDTEXTare always the same as one Another AUTOmeans the selector gadget is updated when YOu do action to the design explorer form "}
{"Headers": "Text Gadgets ", "Content": "A box that can display a Value and into which the User may type a value,Or edit an existing value Text. Number at ........width 10 is REAL Text. Str 'Username: 'callback '!! MyFunction 'width 10 Scroll 100 is STRING Text. Bore 'Bore: 'width 10 is BORE format!! FormatBore Text. Passwd 'Password: 'at......width 10 NOECHO is STRING Specify data type using ISSupply a FORMAT object Password type using NOECHO keyword  "}
{"Headers": "Text Gadgets ", "Content": "Validating Input to Text Fields HAs an optional validation callback member which The user can specify ! textField.ValidateCall = <callback string> Example: !! MyForm.Txt1. ValidateCall = '! this.Validate() ' VALIDATECALL is used to apply any checks if an error is encountered then the callback raises the errorAnd returns "}
{"Headers": "Textpane Gadgets ", "Content": "Provides a box on a form into which a user may type And edit multiple lines of texttextpane.Txt 'Text: 'at......width 10 height 20 textpane.Txt 'Text: 'at......height 20 aspect 0.5 Its contents is an array of strings \uf06eEach element of the array corresponds to a line of text in the Gadget Setting contents: ! Lines[1] = 'Hello World ' ! Lines[2] = ''! Lines[3] = '' ! Lines[4] = 'Goodbye World' ! this.Txt.Val=! Lines  "}
{"Headers": "Fast Access to Lists and Selectors", "Content": "Textpanes using Do Loops To aLISTgadget: Do! Field list!! FormA.ListA ............ Enddo To aSELECTOR gadget: Do! Field selector!! FormA.SelectorA ............ Enddo To aTEXTPANE gadget: Do! Line pane!! FormA.TextpaneA ............ Enddo "}
{"Headers": "View Gadgets ", "Content": "Used to display and interact with alphanumeric or graphical view s Types of View Gadgets: ALPHA PLOT 2D Graphical Views3D Graphical Views Example (using multiple lines): View . MyViewat......PLOT Height 10 width 20 Cursortypepick Border on Setcolour15 Exit Example (using one line): View . MyViewat......PLOT height 10 width 20 bordonsetc15 exit "}
{"Headers": "View Gadgets ", "Content": "Defining ALPHA Views Views for displaying text output and/or allowing command input View . Input at ......ALPHA Height 10 width 20 Channel COMMANDSExit View . InputOutputat......ALPHA Height 10 width 20 Channel REQUESTS Channel COMMANDS Exit channel COMMANDS \u2013causes alpha view to have a command input Field and displays command lines and error messages in the messa ges In the scrollable output region chaNnel REQUESTS \u2013displays the output resulting from commands, in Particular, queries in the scrollable output region  "}
{"Headers": "View Gadgets ", "Content": "Defining PLOT Views Views for displaying non -interactive 2Dplotfiles Setup!! MyForm ...... ...... View . Diagram at ......PLOT height 10 width 20 ......exit ! this.Diagram.Borders = false ! this.Diagram.Add( 'C:\\plot1.plt ') ...... Exit To define the content of thePlot view, specify the PLOTFILE pat h with theAdd()method  "}
{"Headers": "View Gadgets ", "Content": "Defining DRAFT'sArea (2D) Views CoNtents of the view may be any valid 2D graphical element, such as Drat sheet, VIEW, LIBRARY, etc. To define the content of the view, use the PUTcommand \uf06eput CE -draws the current element put /SITE/SHEET -draws the named Sheet element Example: View . Drawing at ......AREA Height 10 width 20 Put /MDS-ABA-3-VIEWS(METRIC)-PS00001-AREA Limits 200 100 to 600 500 Exit ! this.Drawing.Background = 'beige' For DRAFT Module only "}
{"Headers": "View Gadgets ", "Content": "Defining DESIGN'sComparator (2D) Views Contents of the view may be any valid Process and Instrument Diagram sheet reference Example: View . Pidat......COMPARE Height 20 width 40 Put /SHEET CursortypepointerExit ! this.Pid.Background = 'darkslate ' "}
{"Headers": "View Gadgets ", "Content": "Defining DESIGN'sVolume (3D) Views Example: Setup form!! MyForm ...... View . Model at ......VOLUME Height 10 width 30 Auto limits Iso3 Exit ...... Exit Define method. MyForm() ...... ! this.Model.Borders = false ! this.Model.Shaded = true ...... Endmethod Full list of members and methods is found in VANTAGE Plant Desig n Software Customisation Reference Manual"}
{"Headers": "Form Layout", "Content": "Defining DESIGN\u2019sVolume (3D) Views\nExample:\nsetup form !!MyForm\n\u2026\u2026\nview .Model at \u2026\u2026VOLUME\nheight 10 width 30\nlimits auto\niso3\nexit\n\u2026\u2026\nexit\ndefine method .MyForm()\n\u2026\u2026\n!this.Model.Borders = false\n!this.Model.Shaded = true\n\u2026\u2026\nendmethod\nFull list of members and methods is found in VANTAGE Plant Desig n Software\nCustomisation Reference Manual"}
{"Headers": "Gadget Positioning ", "Content": "Form Coordinate System Gadgets are positioned on a form from top Left 0 0123456789 X 1 2 3 4 5 6 7 8 9 Y1 character width per unit 1 line height per unit "}
{"Headers": " Auto Gadget - Placement ", "Content": "ThePATHcommand can be used to define the logical Position of subsequent gadgets PATH DOWN means that the next gadget will be below The current one, PATH RIGHT means that the next gadget Will be to the right of the current one The spacing between gadgets is controlled by VDIST andHDISTfor vertical and horizontal spacing If desperation calls!!! There are settings of HALIGN and VALIGN which can set the alignment LEFT,RIGHT,TOP, CENTRE, andBOTTOM "}
{"Headers": "Auto Gadget - Placement ", "Content": "Example: Button . But1 $* default placement PATH DOWN HALIGN CENTRE VDIST 4.0 para.Par2 width 4 height 2 $* auto-placed Toggle . Tog3 $* auto-placed PATH RIGHT HDIST 6.0 VALIGN BOTTOM List . Lis4 width 5 height 4 $* auto-placedPATH UP HALIGN RIGHT para.Par5 width 6 height 5 $* auto-placed.But1 . Par2 . Tog3. Lis4. Par6 "}
{"Headers": "Relative Gadget Placement ", "Content": "\uf06eEach gadget has four label points \uf0a8XMIN \uf0a8XMAX \uf0a8YMIN \uf0a8YMAX \uf06eThese can be used for positioning using theATkeyword Paragraph .message at xminymaxtext 'Hello world! 'gadgetYMIN YMAX XMAXXMIN "}
{"Headers": "Relative Gadget Placement ", "Content": "Relative to the last gadget 0 0123456789 X 1 2 3 4 5 6 7 8 9 Y XMINYMAX YMAX + 2 Paragraph . Msg 'Hello! 'Atxminymax+2previously created gadget used asReference New paragraph gadget.Msg "}
{"Headers": "Relative Gadget Placement ", "Content": "Relative to the last gadget0 0123456789 X 1 2 3 4 5 6 7 8 9 Y XMIN.Para -5YMAX.Para YMAX.Para+5 Paragraph . Msg 'Hello! 'At xmin.Para-5 ymax.Para+5existing paragraph gadget New paragraph gadget.Para . Frm existing frame gadget . Msg "}
{"Headers": "Mixing Auto and Relative ", "Content": "Investment Example: Toggle .t1 atxminymin Toggle .t2 atxmaxymax.t1+0.25 PATH DOWN VDIST 2.0 Toggle .t3 at xmin.t1 \uf0a8places.t3with respect to XMINof gadget .T2, whilstYcoordinate For.t3is auto-placed at current VDISTvalue (which is 2.0) below the Last placed gadget (which is .t2) "}
{"Headers": "Absolute Gadget Positioning ", "Content": "Example: Toggle . OnOffat 4 3.5 Toggle . OnOffat x 4 y 3.5 0 0123456789X 1 2 3 4 5 6 7 8 9 Y Note: Absolute positioning is not recommended way to define your ga dget positions, Use relative positioning "}
{"Headers": "Intelligent Positioning and Resizing ", "Content": "So far, we have considered the static layout ofThe form Defining intelligent positioning and resizing Behavior of gadgets is considered as Complex Form Layout \uf0a8These describes gadgets with DOCKandANCHOR Attributes "}
{"Headers": "Complex Form Layout ", "Content": "Defines form with intelligent positioning and Resizingbehaviour of gadgets using the DOCK andANCHOR attributes DOCKAttribute: Allows you to dock a gadget to the left, right, top, orBottom edge of its container, typically a form or a Frame: or you can cause the gadget to dock to all Edges, or to no edges ANCHOR Attribute: Allows you to control the position of an edge of the Gadget relative to the corresponding edge of its Container"}
{"Headers": "Complex Form Layout ", "Content": "DOCKAttribute Examples: For forms: Setup form!! MyFormdialog dock bottom For gadgets: Frame . MyFrameat......width 50heigth10 Button . But1 'This is a button 'dock fill Path down Frame . Fr1 'A Frame 'width 5 height 10 dock right Exit Exit "}
{"Headers": "Complex Form Layout ", "Content": "ANCHOR Attribute Examples: Only applicable to gadgets Frame . MyFrame 'My Frame 'at......anchor all textpane.Txt anchor all width 5 height 5 Button . Apply 'Apply 'anchor bottom + right at Xmax-size ymax+0.5 Path left Button . Cancel 'Cancel 'anchor bottom + right Exit "}
{"Headers": "Menus ", "Content": "Menus are always members of forms but can Be employedIn various ways by the form and Its gadgets Two types of menus: Main menu Popup menu "}
{"Headers": "Defining a Bar Menu Gadget", "Content": "Defined within a form definition Created with barsubcommand Use the bar 'sAdd()method to Add options Example: Setup form!! MyFormdialog size 25 1 Bar ! this.bar.Add( 'Choose ','Menu1 ') ! this.bar.Add( 'Window ','Window ') ! this.bar.Add( 'Help ','Help ')Exit  "}
{"Headers": "Defining a Menu Object ", "Content": "A Menu is a set of menu fields, each Representing an action that is invokedWhen the field is selected A menu field can do one of three things: Execute a callback \uf0a8Display a form Display a sub -menu "}
{"Headers": "Defining a Menu Object ", "Content": "Example of a complete Menu definition: --Menu1 definition ! Menu1 = ! this.newMenu( 'MENU1 ','Main ') ! Menu1. Add( 'CALLBACK ','QueryElbows ','!! queryElbows() ') ! Menu1. Add( 'SEPARATOR ') ! Menu1. Add( 'MENU ','Pull-right ','PULLR ')--PULLR menu definition ! Pullr=! this.newMenu( 'PULLR ','Main ') ! pullr.Add( 'CALLBACK ','Menu1','show!! MyForm ') ! pullr.Add( 'FORM ','GadzMenu ','gdzMainForm ')  "}
{"Headers": "Defining a Menu Object ", "Content": "General Syntax: ! menu.Add ('<Fieldtype >','<Dtext>','<Rtext>',{'<Fieldname >'}) <Fieldtype > CALLBACK ,TOGGLE ,MENU,FORM <Dtext> Display text <Rtext> CALLBACK \u2013callback string TOGGLE \u2013callback string MENU -menuname string (cannot be blank) FORM \u2013formname string without '!!'( Cannot be blank) <Fieldname> Optional argument (unique field name) "}
{"Headers": "Popup Menus ", "Content": "You can use any of your defined menus as popup menus For most interactive gadgets and for the form background As long as you have specified them as belonging to the Popup menu system Triggered using Right-clickA popup is added to a gadget or form using its SetPopup () Method Example (Using MENUkeyword): Button . But1 'A Button 'at...... Menu .pop1 popup ! This.pop1. Add( 'TOGGLE ','Active/Inactive ','') ! This.pop1. Add( 'CALLBACK ','Clear ','ALPHA REQUEST Clear ') ! This.But1. SetPopup(! This.pop1)  "}
{"Headers": "Popup Menus ", "Content": "Another Way: Button . But1 'A Button 'at...... ! Popit=! this.newMenu( 'POPIT ','Popup ')! popit.Add( 'TOGGLE ','Active/Inactive ','! this.Control(') ! this.But1. SetPopup(! Popit) "}
{"Headers": "Toggle Menus ", "Content": "A menu fIeld with a callback action and a tick -box to show that the Field has been selected or unselected \uf0a8By default, the field is unselected Example: Setup form!! MyformDialog size 30 5 ...... ! Menu = ! this.newMenu( 'Test ','popup ') ! Menu.add( 'TOGGLE ','Active/Inactive ','!This.toggle( ','OnOff ') ...... Exit Define method .toggle(! Menuis MENU, ! Action is STRING ) ! Name = ! menu.Fullname() ! Field = ! menu.PickedFieldName $P menu $! Name $! Action field: $! Field Endmethod  "}
{"Headers": " ALERT Objects ", "Content": "A menu field with a callback action and a tick -box to show that the field has been selected or unselected\nBy default, the field is unselected\nExample:\nsetup form !!MyformDialog size 30 5\n\u2026\u2026\n!menu = !this.newMenu( \u2018Test \u2019,\u2018popup \u2019)\n!menu.add( \u2018TOGGLE ',\u2019Active/Inactive \u2019,'!this.toggle( \u2018,'OnOff ')\n\u2026\u2026\nexit\ndefine method .toggle(!menuis MENU, !action is STRING )\n!name = !menu.Fullname()\n!field = !menu.PickedFieldName\n$P menu $!name $!action field: $!field\nendmethod"}
{"Headers": "ALERT Objects ", "Content": "INPUT Alerts allows the useR to obtain textual input from the operator via a Blocking alert which overrides all other interactive activities. The alert can be summoned by the alert methods: !! Alert.Input (! Prompt is STRING, ! Default is STRING) is STRING Examples: !! Alert.Error( 'Youcannot do this!') !! Alert.Message( 'Savingyour data now ') !! Alert.Warning( 'Donot press this button again! ') ! Answer = !! Alert.Confirm( 'Areyou sure? ') ! Answer = !! Alert.Question( 'OKto delete component? ') Confirm Alert returns: 'YES'or'NO'Strings Question Alert returns:'YES'or'NO'or'CANCEL 'Strings "}
{"Headers": "Form Exercise 2 ", "Content": "Create the following form. When stretched;"}
{"Headers": "Form Exercise 2 ", "Content": "The'Choose Template 'list gadget: It's contents is based in an option file; FirstRow means the Nameof the template Next row is for the description Third row is the plot files Forth row is the macro file of the template Last row means how many arguments are needed of the template The list only shows the name and the description of the templateUpon choosing each item on the list; The plot file will change based on the plot file defined in the option file The tag of the frame in the parameters frame will also change ba se on the name Disabling and enabling of the parameter fields are also handled Example (If the selected template 's required arguments are only 2, then parameter field 3 will be Disabled and parameter 1 and 2 will be enabled. Same concepts ap ply to all.)  "}
{"Headers": "Form Exercise 2 ", "Content": "The'Create'button: Upon clicking this button; Check validity of the name supplied (If already exists, etc.) Check validity of the hierarchy Check if all required fiElds of the chosen template are supplied by the user If successful to all checking, create the equipment and revert t he form's Mode to initialization mode. Form as initialized: The first item is the default selection of the form This means, the plot fiLe, parameter frame tag and enabled/disab led Parameter fields are also based on the default item selected Supplied files: \uf0a8The option file, plot files, and macro files will be supplied. It is delivered together with this manual under Form Exercise 2 folder"}
{"Headers": "That's All Folks! ", "Content": "DISCLAIMER: This guide is for information purpose only. It is Recommended that users following this guide haveUndergone training first. You may use this manual at your own risk. In no Event shall the writer be liable for any direct, Indirect, incidental, exemplary or consequential Damages."}
{"Headers": "Customizing a Graphical User Interface ", "Content": "The main features of PML2 are:  \u2022 Available Variable Types - STRING, REAL, BOOLEAN, ARRAY \u2022 Built in Methods for commonly used actions \u2022 Global Functions supersede old style macros \u2022 User Defined Object Types \u2022 PML Search Path (PMLLIB)\u2022 Dynamic Loading of Forms, Functions and Objects \u2022 Aid objects for geometric modeling  PML is now more consistent with other programming languages and more structured in Form. The new data types are now OBJECTS which can be operated by running METHODS .The old $ based variables are still valid, but are always treated as strings. Global functions Are macros which can be called more like subroutine s than traditional macros. e.g. a function Can be called between the brackets of an IF stateme nt and return a BOOLEAN result User-Defined object types enable a group of mixed variab les to be combined into packages. The Resulting object can then be used as a simple varia ble and the separate parts set or used as Attributes of the variable. Search paths and dynami c loading mean that it is no longerNecessary to pre load forms or have synonyms for ca lling macros. A large number of new Aid objects have been created so that users can do more graphical construction. Most AVEVA products make use of a Graphical User Interface (GUI) to drive the Software.PML 2 has been specifically designed for writing and customizing the Forms and Menus for AVEVA products. Almost all the facilities avail able in PML 1 and the older Forms And Menus facilities continue to function as before even if they are not documented here.Before you begin customizing a GUI, you must have a good working knowledge of the Command syntax for the AVEVA product you are working g with. PML2 is almost an object-oriented language. Its ma in deficiency is that it lacks Inheritance. However, itDoes provide for classes o f built-in, system-defined and user-defined Object types. Objects have members (their own variables) and methods (their own Functions ). All PML Variables are an instance of a built-in, system-defined or user-defined Object type.Operators and methods are polymorphic - what they do (their behavior) Depends on the type of the variable. Overloading of functions and operators is supported for All variable types. There is no concept of private members or methods, everything is public .There are only two levels of scope for variables: Global and Local . Arguments to PML Functions are passed-by-reference with Read/Write a ccess so any argument can potentially Be used as an output argument.  Note: From PDMS12.1, all textual informatiOn in PDMS is represented as Unicode. Unicode Is a computing industry standard for the consistent encoding, representation and handling of Text expressed in most of the world's writing system ms. Developed in conjunction with the Universal Character SetStandard and published in b ook form as The Unicode Standard, the Latest version of Unicode consists of a repertoire of more than 109,000 characters covering All PML string variables support Unicode values. Yo u can use Unicode characters in PML VariabLe names, PML object form and gadget names, P ML method and function names. All PML language files should either be UTF8 format wit h a BOM present or else strictly ASCII  "}
{"Headers": "PML2 variables", "Content": "AVEVA PDMS Programmable Macro Language manual \n\u2022 Available Variable Types - STRING, REAL, BOOLEAN, ARRAY \n\u2022 Built in Methods for commonly used actions \n\u2022 Global Functions supersede old style macros \n\u2022 User Defined Object Types \n\u2022 PML Search Path (PMLLIB) \n\u2022 Dynamic Loading of Forms, Functions and Objects \n\u2022 Aid objects for geometric modeling \n \n PML is now more consistent with other programming languages and more structured in form. The new data types are now OBJECTS which can be operated by running METHODS . \nThe old $ based variables are still valid, but are always treated as strings. Global functions are macros which can be called more like subroutine s than traditional macros. e.g. a function can be called between the brackets of an IF stateme nt and return a BOOLEAN result User-defined object types enable a group of mixed variab les to be combined into packages. The resulting object can then be used as a simple varia ble and the separate parts set or used as attributes of the variable. Search paths and dynami c loading mean that it is no longer necessary to pre load forms or have synonyms for ca lling macros. A large number of new aid objects have been created so that users can do more graphical construction. \n Most AVEVA products make use of a Graphical User Interface (GUI) to drive the software. PML 2 has been specifically designed for writing and customizing the Forms and Menus for AVEVA products. Almost all the facilities avail able in PML 1 and the older Forms \nand Menus facilities continue to function as before  even if they are not documented here. \nBefore you begin customizing a GUI, you must have a  good working knowledge of the command syntax for the AVEVA product you are workin g with. \n PML2 is almost an object-oriented language. Its ma in deficiency is that it lacks inheritance. However, it does provide for classes o f built-in, system-defined and user-defined object types. Objects have members (their own variables) and methods (their own \nfunctions ). All PML Variables are an instance of a built-in,  system-defined or user-defined object type. Operators and methods are polymorphic - what they do (their behavior) depends on the type of the variable. Overloading of functions and operators is supported for \nall variable types. There is no concept of private members or methods, everything is public . \nThere are only two levels of scope for variables: Global and Local . Arguments to PML Functions are passed-by-reference with Read/Write a ccess so any argument can potentially be used as an output argument. \n \nNote: From PDMS12.1, all textual information in PDMS is represented as Unicode. Unicode is a computing industry standard for the consistent  encoding, representation and handling of text expressed in most of the world's writing syste ms. Developed in conjunction with the \nUniversal Character Set standard and published in b ook form as The Unicode Standard, the latest version of Unicode consists of a repertoire of more than 109,000 characters covering all PML string variables support Unicode values. Yo u can use Unicode characters in PML \nvariable names, PML object form and gadget names, P ML method and function names. All PML language files should either be UTF8 format wit h a BOM present or else strictly ASCII \n  "}
{"Headers": "Kupdf.net_pdms-pml-manual", "Content": "\u2022 ARRAY holds many values of any type. An ARRAY variable c an contain many values, Each of which is called an array element. An Array is created automatically by Creating one of its array elements.The system-defined object types 2.1.2. \u2022 Position, Orientation, DirE, P0, P1... \u2022 Bore, Hbore, Href ... \u2022 Dbref, Dbname, Dbfile...  Examples: BLOCK blocks are used to store commands for a special fo rm of working on arrays. The Block contains a listOf commands and \"block Evalua tion\" is used to perform the actions on An array FILE file is in principle a file name, but the file obj ect contains built in methods for working on The file. DATETIME returns current Date and Time information DB a DB object is an object representing a database. Can be used to interrogate information About type, team, access, claim type DBREF a dbref object a ref to a database it has members (access, file, name, number, Foreign, type, description, claim (string) and team (team))DIRECTION a Direction object has members (direction, origin (dbref), up, east, north (real)) MDB MDB object has members (name and description, both strings) ORIENTATION an orientation object has members (alpha (real), o rigin (dbref), Gamma and Beta(reals))POSITION a position object has members (origin (dbref) up, east, north (reals) PROJECT a project object has one member (evar (string)) TEAM a team object has members (name and description (r eals)) USER a user object has members (access, name, descripti on (strings))FORMAT is a way of formatting data for example metric or imperial] The user-defined object types 2.1.3. You may find that the object types supplied with P ML 2 are enough. However, you can Define new object types if you need to. In any case, the following example may help youUnderstand objects, their members and how they are used. It is a good idea to use upper Case for object-type names, and mixed upper and low er case for variable names, the objects Themselves. For example, a type might be Employee, and a variable name might beNumberOfEmployees.  Define object COMPANY Member . Name is STRING Member . Address is STRING Member . Employees is REAL Member . NumberOfEmpliyees is REAL Endobject  The user-defined object type should by normally st ored in a file with a lowercase nameMatching the name of the object type and a .pmlobj suffix in PMLLIB directory. PML will Load a definition automatically when it is needed. Example above should have name Company.pmlobj .  "}
{"Headers": "PML1 variables creation ", "Content": "Creation of variables For creating variable is used VAR command. As value in variable could be used text orSome attribute. As you may see there are used text delimiters to define any text as value. These delimiters could be used '' or vertical bars || as well. The most important fact is that Using the VAR command always create variable as str ing() object. Even if you use numbersOr Booleans. Of course that you can create an array by VAR command but array itself Contain array members. Through command VAR you just fill an array by string elements. REMEMBER THAT VAR COMMAND ALWAYS CREATES STRING OBJ ECT TYPE!!!  Text - as string in PML2:VAR! PML1text 'THISisTEXT' VAR! PML1attribute1 NAME VAR! PML1attribute2 POS WRT /*  Numbers - as real in PML2:  VAR! X (32) VAR! Y (52) VAR! Z1 (! X + ! Y) VAR! Z2 ('! X' + '! Y') VAR! Z3 ('$! X' + '$! Y') VAR! Z4 (23 * 1.8 + 32)  Boolean - as Boolean in PML2:VAR! T1 TRUE VAR! F1 FALSE VAR! T2 T VAR! F2 F VAR! T3 YES VAR! F3 NO VAR! T4 Y VAR! F4 N  There are no BOOLEAN () object variables in PML1. V AR command always creates the STRING () object type.  Array - as array in PML2:  VAR! ARRAY[1] 'AVEVA'VAR! ARRAY[10] NAME VAR! ARRAY[20] (12)  Using the PML2 syntax you will create not only the value for variable but you Automatically assign the object type according to d efined data. If it is simply text, then results As string object but some dataAs position are alre ady defined as some other object type. In This case the position is system defined object typ e therefore results as POSITION. This is The most important difference between PML1 and PML2 because PML2 is object oriented Language."}
{"Headers": "Members and Attributes ", "Content": "! PML2string = 'THISisTEXT'! PML2attribute1 = NAME ! PML2attribute2 = POS WRT /* (in PML1 will be stri ng in PML2 position object type)  Real:  ! X = 32 ! Y = 52 ! Z1 = (! X + ! Y) ! Z2 = ('! X' + '! Y') ! Z3 = ('$! X' + '$! Y') ! Z4 = (23 * 1.8 + 32)  Boolean:  ! T1 = TRUE! F1 = FALSE ! T2 = T ! F2 = F ! T3 = YES ! F3 = NO ! T4 = Y ! F4 = N  Array:  ! ARRAY = ARRAY() ! ARRAY[1] = 'AVEVA' ! ARRAY[2] = NAME ! ARRAY[3] = 12 ! ARRAY[4] = N ! ARRAY[5] = TRUE An object can contain one or more items of data re ferRed to as its members or attributes. Each member has a name.  \u2022 STRING, REAL and BOOLEAN variables just have a val ue - no members. \u2022 ARRAY variables have numbered elements, not member s.  User Defined Objects can contain any variable or o bject type as attributes or members.Information is grouped with an object for ease of reference and standard reference. User- Defined objects can also contain user-defined metho ds that will use the information stored Within the object. These methods may represent a ca lculation, or information retrieval.After An object has been declared as a variable, the meth ods can be applied to the variable. For Example:  Define object ELEMENT Member . Type is STRING Member . Material is STRING Endobject  Define method. FullDesc() is STRING Return! This.Type & ' ' &! this.Material Endmethod "}
{"Headers": "Naming conventions ", "Content": "String: \n \n!PML2string = 'THISisTEXT' \n !PML2attribute1 = NAME \n !PML2attribute2 = POS WRT /* (in PML1 will be stri ng in PML2 position object type) \n \nReal: \n \n !x = 32 \n !y = 52 \n !z1 = (!x + !y) \n !z2 = ('!x' + '!y') \n !z3 = ('$!x' + '$!y') \n !z4 = (23 * 1.8 + 32) \n \nBoolean: \n \n !T1 = TRUE \n !F1 = FALSE \n !T2 = T \n !F2 = F \n !T3 = YES \n !F3 = NO \n !T4 = Y \n !F4 = N \n \nArray: \n \n !ARRAY = ARRAY() \n !ARRAY[1] = 'AVEVA' \n !ARRAY[2] = NAME \n !ARRAY[3] = 12 \n !ARRAY[4] = N \n !ARRAY[5] = TRUE \n An object can contain one or more items of data re ferred to as its members or attributes. \nEach member has a name. \n \n\u2022 STRING, REAL and BOOLEAN variables just have a val ue - no members. \n\u2022 ARRAY variables have numbered elements, not member s. \n \n User Defined Objects can contain any variable or o bject type as attributes or members. \nInformation is grouped with an object for ease of r eference and standard reference. User-defined objects can also contain user-defined metho ds that will use the information stored within the object. These methods may represent a ca lculation, or information retrieval. After \nan object has been declared as a variable, the meth ods can be applied to the variable. For example: \n \ndefine object ELEMENT \n  member .Type is STRING \n  member .Material is STRING \nendobject \n \ndefine method .FullDesc() is STRING \n  return !this.Type & \u2018 \u2018 & !this.Material \nendmethod "}
{"Headers": "Naming conventions ", "Content": "Application Prefix Comments Area BasedADP!! ABA Add-in application Administration!! ADM Plus!! CDA Application Switching !! App Batch Handling!! BAT CADCentre!! CADC Draft!! CDR Draft Icon Location!! CD2D Icon pathnames Defaults!! DFLTS General!! CDC Plus!! CDD, E, F, G, H, I, L, M, N, P, S, U, V, W Specialized!! CE Plus!! ERROR, !! FMSYS  The majority of the existing PML2 code has been giv en a 3or4 letter prefix to the full name.  Application Prefix Comments Accommodation ACC ADM Administration Access, Stairs & Ladders ASL Area Based ADP ABA Add-in application Assembly ASSYAssociations ASSOC None apparent Common COMM Mixed Design DES Mixed Draft DRA Plus ADP, DGN, DXF Global GLB Hull Design HULL Hull Drafting HDRA None Integrator INT  Application Prefix Comments Isometric ADP ISO Add-in application Marine DiagramsDIAG No appware except main form Monitor MON Paragon CAT Review Interface REVI None - Single file Spooler SPL Vantage Marine VMAR No appware except start-up  Icons are named without regard to any rules, except on odd occasions.  Application Prefix CommentsDesign DES Various Profile PRFL Various Schematic Model Viewer SMV Various Styles STY Plus FSTY  "}
{"Headers": "PML 1 expressions ", "Content": "\u2022 Text values VAR! CEname NAME takes the current element's (ce) name attribute as string VAR! BRhbore HBORE takes bran bore on hbore, even if its number varia ble is stringVAR! X 'NAME' or VAR! X |NAME| sets the variable to the text string 'NAME'  Note: Quotes ' ' or vertical bars | | may be used as tex t delimiters.  \u2022 Number values VAR! X (32) VAR! Y (52) Expression VAR! Z (! X + ! Y) results as STRING 84!!! Expression VAR!Z ('! X' + '! Y') results as STRING! X! Y!!! Expression VAR! Z ('$! X' + '$! Y' ) results as STRING 3252!!! VAR! Temp (23 * 1.8 + 32) calculate a value and result is STRING 73.4 !!!  Note: VAR always obtain STRING (text) value even if expr ession calculate numbers!!!  \u2022 Boolean values VAR! X TRUE  Note: This expression set variable! X as true. But this i s string text. This is not as PML2 Boolean where condition is TRUE or FALSE or 0 or 1. Booleans could be used as parameter In IF statement but from VAR evaluate STRING!!!  \u2022 ARRAY (array is variable with many values in rows) VAR! ARRAY[1] 'AVEVA' VAR! ARRAY[10] NAME  Note: VAR always obtain STRING (text) value even if coll ecting DB elements. The result is String value. \u2022 STRING ! Name = 'Fred' create STRING variable\u2022 REAL !! Answer = 42 create REAL variable: Expression! Z = ! X + ! Y where! X=32! Y=52 results as REAL 84!!!  \u2022 BOOLEAN !! Flag = TRUE create BOOLEAN variable. If false than is Boolean 0.  \u2022 ARRAY ! Newarray = ARRAY() create an empty ARRAY ! Newarray[1] = |xxx| or!Newarray[1] = 'xxx ' add first value to the empty ARRAY  "}
{"Headers": "Deleting PML Variables ", "Content": "Creating Unset and undefined variable Each new data type supports a String() method that returns a string representing the Value of the variable. For example:  ! X = 2.5 $* defines a variable X of type REAL wit h 2.5 as its numeric value! S = ! X.String() $* will be a variable of type STR ING, with the value \u201c2.5\u201d ! X = REAL()! $* yields the string '(the empty stri ng) ! S = ! X.String() ! X = BOOLEAN() $* yields the string '' (the empty s tring) ! S = ! X.String() ! X = STRING() $* yields the string 'Unset'! S = ! X.String() ! X = ARRAY() $* yields the string 'ARRAY ! S = ! X.String()  Other variable types are system-defined variables. Most of these have adopted the unset String 'Unset'. User-defined data types can also pr ovide a String() method. These alsoSupport an UNSET representation, and usually adopt the UNSET representation 'Unset'. For example:  ! X = DIRECTION() $* yields the string 'Unset' ! S = ! X.String()  All data types can have the value UNSET which indi cates that a variable does not have aValue. A variable created without giving it an init ial value in fact has the value UNSET:  !! Answer = REAL()! Name = STRING() ! Grid = BOOLEAN()! Lengths = ARRAY()  Variables with an UNSET value can be passed around and assigned, but use of anUNSET value where a valid item of data is required will always result in a PML error. The Presence of an UNSET value may be tested either wit h functions or methods:  If ( Unset(! X) ) then if ( ! X.Unset() ) then If ( Set(! X) ) then if ( ! X.Set() ) thenAn UNDEFINED variable is one that does not exist. T he existence of a variable may be Tested with these functions:  If ( Undefined(!! Y) ) then If ( Defined(!! Y) ) then  There is no equivalent method call. If the variable does not exist, attempting to call a methodWould result in an error. A variable that exists can be explicitly made UNDE FINED with the Delete() method:  !! Y.Delete() Warning: You must not attempt to delete members of objects or forms. Mixing PML1 and PML2 expressions could cause mixin g the variables types.Mixing the Variables types give error for example: \u201eCannot ass ign variable to result - incompatible types (REAL=STRING)\". With VAR you will always obtain a S TRING. You could have defined Variable type before you assign any value to the variable: "}
{"Headers": "Expression operators", "Content": "Creating Unset and undefined variable \n Each new data type supports a String() method that  returns a string representing the value of the variable. For example: \n \n!X = 2.5   $* defines a variable X of type REAL wit h 2.5 as its numeric value \n!S = !X.String()  $* will be a variable of type STR ING, with the value \u201c2.5\u201d \n!X = REAL()!  $* yields the string \u2019(the empty stri ng) \n!S = !X.String() \n!X = BOOLEAN() $* yields the string \u2018\u2019 (the empty s tring) \n!S = !X.String() \n!X = STRING()  $* yields the string \u2018Unset\u2019 \n!S = !X.String() \n!X = ARRAY()  $* yields the string \u2018ARRAY \n!S = !X.String() \n \n Other variable types are system-defined variables.  Most of these have adopted the unset string \u2018Unset\u2019. User-defined data types can also pr ovide a String() method. These also support an UNSET representation, and usually adopt the UNSET representation \u2018Unset\u2019.  \nFor example: \n \n!X = DIRECTION() $* yields the string \u2018Unset\u2019 \n!S = !X.String() \n \n All data types can have the value UNSET which indi cates that a variable does not have a value. A variable created without giving it an init ial value in fact has the value UNSET: \n \n!!Answer  = REAL()  !Name   = STRING() \n!Grid   = BOOLEAN()  !Lengths  = ARRAY() \n \n Variables with an UNSET value can be passed around  and assigned, but use of an UNSET value where a valid item of data is required will always result in a PML error. The presence of an UNSET value may be tested either wit h functions or methods: \n \nif ( Unset(!X) ) then if ( !X.Unset() ) then \nif ( Set(!X) ) then if ( !X.Set() ) then \n \nAn UNDEFINED variable is one that does not exist. T he existence of a variable may be tested with these functions: \n \nif ( Undefined(!!Y) ) then  \nif ( Defined(!!Y) ) then \n \nThere is no equivalent method call. If the variable  does not exist, attempting to call a method would result in an error. \n A variable that exists can be explicitly made UNDE FINED with the Delete() method : \n \n!!Y.Delete()  Warning: You must not attempt to delete members of  objects or forms. \n Mixing PML1 and PML2 expressions could cause mixin g the variables types. Mixing the \nvariables types give error for example: \u201eCannot ass ign variable to result - incompatible types \n(REAL=STRING)\u201d. With VAR you will always obtain a S TRING. You could have defined \nvariable type before you assign any value to the va riable: "}
{"Headers": "Boolean Operators ", "Content": "! S = 30 * sin(45) ! T = pow(20,2) (raise 20 to the power 2 (=400)) ! F = (match (name of owner, |LPX|) GT 0) The Boolean, sometimes called Logical, operators h ave the following meanings:  \u2022 EQ TRUE if two expressions have the same value.\u2022 NE TRUE if two expressions have different values. \u2022 LT TRUE if the first expression is less than the s econd. \u2022 GT TRUE if the first expression is greater than th e second. \u2022 LE OR LEQ TRUE if the first expression is less than n or equal to the second.\u2022 GE OR GEQ TRUE if the first expression is greater than or equal to the second. \u2022 NOT TRUE if the expression is FALSE. \u2022 AND TRUE if both expressions are TRUE \u2022 OR TRUE if either or both expressions are TRUE.  Note: The operators EQ, NE, LT, GT, LE and GE are someti mes referred to as comparator Or relational operators; NOT, AND, and OR are somet imes referred to as Boolean operators. Refer to Precisions of Comparisons for tolerances i n comparing numbers.  Several different types of expressions examples:Logical expressions - PDMS attributes Logical constants TRUE, ON, YES for true / FALSE, OFF, NO for false Logical Operators Comparator operators (EQ, NEQ, LT, GT, LEQ, GEQ) Boolean operators (NOT, AND, OR) Logical functions BADREF, DEFINED, UNDEFINED, CREATE, DELETED, EMPTY, MATCHWILD, MODIFIED, UNSET, VLOGICAL.... Logical array expressions PDMS attributes e.g. XLEN YLEN POHE POSITION ORIENT ATION Numeric operator -- + Add, - Subtract, * Multiply, / Divide Numeric function ABS, ACOS, ASIN, ATAN, SIN, COS, TAN, MATCH, MAX, S QRT.. Real expressions - See numeric functions Text expressions - A text string, PDMS attributes, Text operators, Text functions Values to be concatenated are automatically conver ted to STRING by the '&' operator.Type the following onto the command line:  ! A = 64! B = 32! M = 'mm' ! C = ! A & ! B & ! M Q var! C  Compare this against the results of typing ! D = ! A +! B Q var! D  "}
{"Headers": "Parameterized Macros ", "Content": "Communicating with AVEVA Products in PML All commands need to be supplied to the command pr ocessor as STRINGS. This is ImportantT when working with element creation (using the NEW syntax) to expand the Contents of a PML variable into a string - put a $ in front of it!  ! CompType = |ELBO| ! Dist = 5600 NEW $! CompType DIST $! Dist Macros can be parameterized. This means insteadOf hard coding the values through the Macro, the values can be referenced, allowing them to be varied. Simplemac.mac can be Parameterized as follows:  NEW EQUIP /$1 NEW BOX XLEN $2 YLEN $3 ZLEN $4 NEW CYL DIA $3 HEI $4 CONN P1 TO P2 OF PREV  IF no parameters are specified, the macro will fai l. To avoid this, default values can be put Inside the macro. This is done by specified $d1= at the top of the macro. For example: $d1=ABCDEF $d2=300 $d3=400 $d4=600 Synonyms are abbreviations of longer commands.The y are created by assigning the Command to a synonym variable:  E.g. $SNewBox=NEW BOX XLEN 100 YLEN 200 ZLEN 300 E.g. $SNewBox=NEW BOX XLEN $S1 YLEN $S2 ZLEN $S3 (A parameterized synonym)  To call the first version, type NewBox. For the secondVersion, type NewBox 100 200 300  If all synonyms are killed, the synonyms needed to run PDMS will be removed. This Means PDMS will no longer work properly and will re quire restarting. If synonyms are turned Off, some PDMS functionality will also be removed.The return this functionality, the Synonyms should be turned back on.  To kill a synonym, type $SXXX= & all synonyms $sk To switch synonyms off and on $S- and $S+  Note: If all synonyms are killed, the synonyms needed to run PDMS will be removed.This Means PDMS will no longer work properly and will re quire restarting. If synonyms are turned Off, some PDMS functionality will also be removed. The return this functionality, the Synonyms should be turned back on.  $S - defines a local synonym$G - defines a global synonym $U - prevents the deletion of a global synonym whic h has already been defined Global synonym ($G) works inside pml functions/meth ods while local ($S) does not.  "}
{"Headers": "Using the Member Values of an Object", "Content": "Communicating with AVEVA Products in PML \n All commands need to be supplied to the command pr ocessor as STRINGS. This is important when working with element creation (using  the NEW syntax) to expand the contents of a PML variable into a string - put a $ in front of it! \n \n!CompType = |ELBO| !dist = 5600 \nNEW $!CompType \nDIST $!dist \n Macros can be parameterized. This means instead of  hard coding the values through the macro, the values can be referenced, allowing them to be varied. Simplemac.mac can be parameterized as follows: \n \nNEW EQUIP /$1 \nNEW BOX \nXLEN $2 YLEN $3 ZLEN $4 \nNEW CYL DIA $3 HEI $4 \nCONN P1 TO P2 OF PREV \n \n If no parameters are specified, the macro will fai l. To avoid this, default values can be put inside the macro. This is done by specified $d1= at  the top of the macro. For example: \n$d1=ABCDEF $d2=300 $d3=400 $d4=600  \n Synonyms are abbreviations of longer commands. The y are created by assigning the command to a synonym variable: \n \ne.g. $SNewBox=NEW BOX XLEN 100 YLEN 200 ZLEN 300  \ne.g. $SNewBox=NEW BOX XLEN $S1 YLEN $S2 ZLEN $S3  (A parameterized synonym) \n \nTo call the first version, type NewBox. For the second version, type NewBox 100 200 300 \n \n If all synonyms are killed, the synonyms needed to  run PDMS will be removed. This means PDMS will no longer work properly and will re quire restarting. If synonyms are turned off, some PDMS functionality will also be removed. The return this functionality, the \nsynonyms should be turned back on. \n \nTo kill a synonym, type $SXXX= & all synonyms $sk \nTo switch synonyms off and on $S- and $S+  \n \nNote:  If all synonyms are killed, the synonyms needed to  run PDMS will be removed. This means PDMS will no longer work properly and will re quire restarting. If synonyms are turned off, some PDMS functionality will also be removed. The return this functionality, the \nsynonyms should be turned back on. \n \n$S - defines a local synonym \n$G - defines a global synonym \n$U - prevents the deletion of a global synonym whic h has already been defined \nGlobal synonym ($G) works inside pml functions/meth ods while local ($S) does not. \n  "}
{"Headers": "Storing and Loading PML Functions", "Content": "define function!! LengthAndTrim(! Name is STRING, ! L ength is REAL) ! Name = ! Name.Trim() ! Length = ! Name.Length() Endfunction  Arguments used for output must exist prIor to the c all and one that is also used as an input Argument must also have a value:  ! Name = 'FRED'! Length = REAL()  The function is called to set the value of a variab le! Length as follows:  !! LengthAndTrim(' FRED ', ! Length)  When an argUment value is changed within a PML Func tion its value outside the function is Also changed. The following call is incorrect, as t he function cannot modify a constant:  !! LengthAndTrim(' FRED ' ,4 ) $* WRONG  A PML Function returning a value may beUsed wherev er an expression or PML Variable Can be used, for example, this call to the! Area fu nction defined above:  ! PartLength = 7! PartWidth = 6 ! SurfaceArea = !! Area(! PartLength, ! PartWidth) When a PML Function is called it is loaded automat iCally from its source file in a directory Located via the environment variable PMLLIB. The na me of the external file must be Lowercase and must have the .pmlfnc suffix. The sou rce of a PML Function invoked as !! AREA or !! Area or!! Area all correspond to the fi le named area.Pmlfnc.  Note: The!! Means that the function is user-defined and that it is global - but!! Does not Form part of the external filename. All user-define d functions are global and only one may be Defined per file. The define function must be theF first line in the file and that its name and the File name must correspond. You may specify ANY as the type of an argument (an d even as the type of the function Return value).  Note: The use of ANY should be the exception rather than the rule as it switches offArgument type checking - an important feature of PM L Functions to help ensure correct Functioning of your PML.  In the case an argument of type ANY, a value of any type may be passed as the argument to The function:  Define function!! Print(! Argument is ANY)$P $! Argument Endfunction  Where an argument of type ANY is used, you may need to find out its actual type before you Can do anything with it. The ObjectType() method ca n be used for this purpose:  "}
{"Headers": "PML Procedures ", "Content": "define function!! AnyType(! Argument is ANY) Type = ! Argument.pmlobjectType() If (! Type EQ 'STRING' ) then- - do something with a STRING Elseif (! Type EQ 'REAL' ) then - - do something with a REAL Elseif (! Type EQ 'DBREF' ) then - - do something with a DB Reference Else - - do something with all other types or give a n error EndifEndfunction A PML Procedure is a PML Function that does not re turn a result. A function is defined as A procedure by omitting the data type at the end of the define function statement:  Define function!! Area( ! Length is REAL, ! Width is REAL, ! Result is REAL)! Result = ! Length * ! Width Endfunction  Here we are using an output argument, ! Result, to r eturn the result rather than using a Function return value. The arguments to the!! Area procedure can be set as follows, and then The procedure invoked with the call command.! SurfaceArea = REAL() ! Partlength = 7 ! PartWidth = 6 Call!! Area(! PartLength, ! PartWidth, ! SurfaceArea)  There will be an error if you attempt to assign the result of a PML Procedure because there Is no return value to assign. So, for example you c an say:Call!! Area(! PartLength, ! PartWidth, ! SurfaceArea) ! Answer = ! SurfaceArea  But you cannot say:  ! Answer = !! Area(! PartLength, ! PartWidth, ! SurfaceA rea) $* WRONG  The ( ) parentheses after the name of a procedure o r function must always be present evenFor procedures that do not need arguments:  Define function!! Initialize() ! TotalWeight = 0 !! MaxWeight = 0 Endfunction Call!! Initialize()  Although the call keyword is strictly speaking opti onal, its use is recommended with Procedures.  NOte: As well as procedures, you can invoke a PML Functi on that has a return value using Call, in which case the function result value is di scarded. "}
{"Headers": "Methods on User-Defined Object Types", "Content": " define function !!AnyType(!Argument is ANY) \n  Type = !Argument.pmlobjectType() \n  if ( !Type EQ 'STRING' ) then \n    - - do something with a STRING \n  elseif ( !Type EQ 'REAL' ) then \n    - - do something with a REAL \n  elseif ( !Type EQ 'DBREF' ) then \n    - - do something with a DB Reference \n  else \n    - - do something with all other types or give a n error \n  endif \nendfunction \n A PML Procedure is a PML Function that does not re turn a result. A function is defined as a procedure by omitting the data type at the end of  the define function statement: \n \ndefine function !!Area( !Length is REAL, !Width is REAL, !Result is REAL) \n  !Result = !Length * !Width \nendfunction \n \nHere we are using an output argument, !Result, to r eturn the result rather than using a function return value. The arguments to the !!Area procedure can be set as follows, and then the procedure invoked with the call command. \n \n!SurfaceArea = REAL() \n!Partlength = 7 \n!PartWidth = 6 \ncall !!Area(!PartLength, !PartWidth, !SurfaceArea) \n \nThere will be an error if you attempt to assign the  result of a PML Procedure because there is no return value to assign. So, for example you can say: \n \ncall !!Area(!PartLength, !PartWidth, !SurfaceArea) \n!Answer = !SurfaceArea \n \nBut you cannot say: \n \n!Answer = !!Area(!PartLength, !PartWidth, !SurfaceA rea) \n$* WRONG \n \nThe ( ) parentheses after the name of a procedure o r function must always be present even for procedures that do not need arguments: \n \ndefine function !!Initialize() \n  !TotalWeight = 0 \n  !!MaxWeight = 0 \nendfunction \ncall !!Initialize() \n \nAlthough the call keyword is strictly speaking opti onal, its use is recommended with procedures. \n \nNote:  As well as procedures, you can invoke a PML Functi on that has a return value using call, in which case the function result value is discarded. "}
{"Headers": "Method Overloading ", "Content": "define method . Life() ! This.Answer = 42 Endmethod  A method may return a result in just the same way a s a PML Function using the returnCommand. Set a member of the object using! This.mem bername.  Define method. Answer() IS REAL Return! This.Answer Endmethod  Define method. Answer( ! Value Is REAL) ! This.Answer =! Value Endmethod  These methods might be used in the following way:! Marvin = object LIFE() -- The method . Life() was called automatically ! Number = ! Marvin.Answer() --! Number is set to the value 42 ! Marvin.Answer(40) ! Number = ! Marvin.Answer() --! Number now has the value 40  Warning: When you create a new objeCt type, or chan ge an existing definition, you Must load the definition by giving the command:  Pml reload object _name_ Two or more methods on an object may share the sam e name providing they have Different arguments. This is called method overload ing.PML will invoke the method with the Arguments which match the method call. It is common practice:  \u2022 To use a method with the same name as a member and one argument of the same Type to set the member's value. For example:  ! Marvin.Answer(65)  \u2022To use a method of the same name as a member retur ning a value of the same type But with no arguments to get the member's value. Fo r example:  ! Number = ! Marvin.Answer() When an object is created, it is possible to suppl y arguments that are passed by PML to aConstructor method with matching arguments instead of the default constructor method:  ! Marvin = object LIFE(40)  This would invoke a method:  Define method. Life(! Value IS REAL) "}
{"Headers": "Invoking a Method from Another Method ", "Content": " Overloading with ANY As with PML Functions, the type of a methOd argume nt may be specified as ANY. Yew Method overloading is being used, PML will invoke t he method with a matching set of Explicitly typed arguments in preference to calling a method with arguments of type ANY, Irrespective of the order the methodsAppeared in t he object definition file:  Define method. SetValue(! Argument Is ANY) Define method. SetValue(! Argument Is REAL)  Then: ! SomeObject.SetValue(100) will invoke the method with the REAL argument, but ! SomeObject.SetValue('Priceless' )Will invoke the method with the ANY argument. Within a method! This.Methodname() refers to anoth er method on the same object. So Our second LIFE constructor method, the one with an argument, could be defined as:  Define method. Life(! Value IS REAL)! This.Answer(! Value) Endmethod Whenever you add a new method to an object, you ne ed to tell PML to re-read the object Definition, by giving the command:  Pml reload object life  It is not necessary to use this command if you are simply editing an existing method(Although you will have to use it if you edit a for m definition file, and change the default Constructor method, described in Form Definition Fi le.) In PML 2, forms are a type of global variable. Thi s means that a form cannot have the Same name as aNy other global variable or any other form. Note that a form definition is also The definition of an object, so a form cannot have the same name as any other object type.   "}
{"Headers": "Kupdf.net_pdms-pml-manual", "Content": "in PML An ARRAY variable can contain many values, each of which is called an array element. YearArray is created automatically by creating one o f its array elements.  ! Array = Array()  This is an empty variable but it has been defined a s an array. Adding elements to the array:  Type 1 ! Array[1] = 'BOB'! Array[2] = 45! Array[10] = !! C E Type 2! Array.Append('BOB')! Array.Append(45)! Array.Appe nd(!! CE)  Type 1 adds string values into exact position of a rray element (1,2 and 10). Type2 add String values to the end of lists (11,12,13). To ch eck array list query:  Q var! Array <ARRAY> [1] <STRING> 'BOB'[2] <REAL> 45 [10] <DBREF> 'KELLY' [11] <STRING> 'BOB' [12] <REAL> 'GEORGE' [13] <DBREF> 'KELLY'  To check exact array member query:  Q var! Array[1] <STRING> 'BOB'  Note: How array elements are referred to by means of a s ubscript expression in [ ] squareBrackets and that there must be no space between th e end of the array name and the Subscript. Array elements are accessed in the same way when using the value in an Expression:  ! Average = ( ! Sample[1] +! Sample[2] +! Sample[3] ) / 3 )  The individualUal elements of an array variable can be set independently and in any order. Thus You can set! X[1] and ! X[10] without setting any of the intervening elements! X[2] to! X[9]. In Other words PML arrays are allowed to be 'sparse' a nd to have gaps between the subscriptNumbers which have values set. Negative subscripts are no longer permitted. An array Subscript of zero is allowed but you are advised ag ainst using it as many of the array Facilities ignore array element zero. An array subs cript may be an expression of anyComplexity provided it evaluates to a positive REAL result and may even include a call to a PML Function:  ! Value = ! MyArray[! A + (! B * !! MyFunction() ) + ! C ]  PML Arrays may be heterogeneous. That is to say the elements of a PML array do not haveTo be all of the same type. Array elements may even be user-defined objects. Values to be Concatenated are automatically converted to STRING by the '&' operator. Type the following Onto the command line: Non-existent array elements - after the last set element of the arrayAnd the non-existent elements in the gaps of a spar se array - are all UNDEFINED: the Function Undefined() will return TRUE and the funct ion Defined() will return FALSE for all These subscripts. "}
{"Headers": "Kupdf.net_pdms-pml-manual-1 ", "Content": "Array methods \n Array methods are built-in functions for performin g a variety of operations on the array. \nThese methods are invoked with a dot following the array name. The method name must be followed by ( ) parentheses - even if the function has no arguments. Array methods :  \n\u2022 !Array.Size() \n\u2022 !Array.Clear() \n\u2022 !Array.RemoveFrom(x,y) \n\u2022 !Array.Append() \n\u2022 !Array.Delete() or !Array[N].Delete() \n\u2022 !Array.Split() \n\u2022 !Array.Width() \n\u2022 !Array.Sort() \n\u2022 !Array.Inver() \n\u2022 !Array.SortUnique() \n\u2022 !Array.Unique() \n \nNote:  Always use an array method, if one is available, i n preference to constructing a do loop as it is far more efficient. \n \n!Nelements = !MyArray.Size() \nThis method sets !Nelements to the number of elemen ts currently in the array. Its returns a REAL result which can be assigned to another variable. \n \n!MyArray.Clear() \nThis is an example of a method which modifies the a rray by deleting all the array elements but produces no-result value, so there is nothing t o assign to another variable. \n \n!NewArray = !OldArray.RemoveFrom(5,10) \nThis is an example of a method result which modifie s the array by removing 10 elements, starting at element 5. NewArray value is a new arra y containing the 10 removed elements. If not required, the result can be simply discarded by  invoking the method as a command and \nnot assigning the result to a variable: !OldArray.RemoveFrom(5,10)  \n \n!Result.Append(!NewValue) \nTo set a new element at the end of an existing arra y without needing to know which elements are already set, use the Append() method. The new array element to be created is determined automatically by adding 1 to the highest  existing index for the array !Result. The \ndata are stored in !Result[1] if the array does not  yet contain any elements. The array !Result must exist before you can call this method. If nece ssary you can create an empty array (with no elements) beforehand: !Result = ARRAY() .If !Res ult exists already as a simple variable, you will get an error and the command is ignored. \n \n!MyArray[N].Delete() \nTo destroy an array element use the Delete() method . The deleted array element would test \nas UNDEFINED. Note that the array continues to exis t even when you have deleted all its \nelements. Deleting the entire array, together with any existing array elements, use the Delete \nmethod on the array itself: !MyArray.Delete()  \n \n!ArrayOfFields = !Line.split() \nYou can split a text string into its component fiel ds and store each field in a separate array element using a text string\u2019s Split() method. This can be useful after reading a record from a file into a variable. By default, the delimiter is any white-space character (tab, space or "}
{"Headers": "Kupdf.net_pdms-pml-manual-1", "Content": "(newline): ! Line = '123 456 789' The white-space is treated as a special case since Consecutive white-spaces are treated as a single deLimit and white-spaces at the start or Finish of the string are ignored. The result is to create the array-variable! ArrayOfFields (if it Does not already exist) with the element! FIELDS[1] set to '123', ! FIELDS[2] set to '456', and ! FIELDS[3] set to '789'.To specify a different del imiter, specify the required (single) Character as the argument to the Split() method:  ! Line = '123 ,456 ,,789' ! ArrayOfFields = ! Line.split(',') In this example, comma is used as the delimiter. ! A rrayOfFields is created if it does notAlready exist with the element! FIELDS[1] set to '1 23', ! FIELDS[2] set to '456', ! FIELDS[3] Created but set to zero length, and! FIELDS[4] set to '789'. Note that in this case, unlike the White-space delimiter, consecutive occurrences of t he comma define empty elements.Note: The only way to set the special white-space delimit er is by default; that is, by not specifying Any delimiter as an argument to the Split() method. If a space is specified explicitly as the Delimiter (as ' '), it will behave in the same way as comma in this example.You can combine An array-append method with a text-string Split() m ethod in a single command to append the Fields of a text string to the end of an existing a rray variable, thus: ! ArrayOfFields.AppendArray(! Line.Split())  ! Width = ! List.width() ThE length of the longest element in an array can b e a useful thing to know, for example When you are outputting the values in table form. Y ou can do this using the Width() method. For example, in the array! LIST: ! LIST[1]'One'! LIST[2]'Two'! LIST[3]'Three'The command: ! Width = ! List.width() would set to! Width to the v alue 5, the length of the longest element in ! LIST, which is 'Three'. Note: If the array contain ed elements that were not strings, these are Ignored when calculating the maximum width. ! MyArray.Sort() & ! MyArray.Sort(). Invert() The simplest way of sorting an array is to use the Sort() method: ! MyArray.Sort() This is a No-result method that modifies the array by perform ing a sort in-situ. The sort is into Ascending order and will be aN ASCII sort on an arr ay of STRING elements and a NUMERIC Sort on an array of REAL values. The Sort() method returns the array itself as a list result, so It is possible to follow the call to the Sort() met hod immediately with a call to the Invert() MEthod, which will return a descending sort: ! MyArr ay.Sort(). Invert(). An alternative Approach is an indirect sort using the method Sorte dIndices() which returns a REAL array Representing new index positions for the array elem ents in their sorted positions:! NewPositions = ! MyArray.SortedIndices() The array can be sorted by applying the new Index values using the ReIndex() method: ! MyArray.R eIndex(! NewPositions) More important, The index values in! NewPositions can be used to so rt other arrays as well. To use some simple examples, imagine we had the arr ay! Animals that contained: [1] Wombat [2] Kangaroo [3] Gnu [4] Aardvark [5] An telope  The command: ! Animals.Sort ()  Would move the array elements so that they now appe ared in the following order:[1] Aardvark [2] Antelope [3] Gnu [4] Kangaroo [5] Wombat  The command: ! Animals.Invert () invert the sort to the following order: [1] Antelope [2] Aardvark [3] Gnu [4] Kangaroo [5] Wombat  "}
{"Headers": "Subtotaling Arrays with the VAR Command ", "Content": "Sorting Arrays using the VAR Command These facilities were dSigned to work with arrays of STRINGS. Where a multi-level sort Is required it is still necessary to use the older facilities of the VAR command to perform the Comes out. Using a different example, look at the arrays! Because,! Colour and! Year:  VAR! Index SORT!Because CIASCII! Colour! Year NUMERIC  Sorting Option Effect CIASCII Sorts in ascending case-independent alphabe tic order. DESCENDING Sorts in alphabetic in reverse order CIASCII DESCENDING Sorts in descending case-indepen dent alphabetic order. NUMERIC Forces an ascending numerical sort on numbe rs held as strings. NUMERIC DESCENDING Forces a descending numerical so rt on numbers held as strings.  You can also modify the array to eliminate empty or repeated elements:  UNIQUE - Eliminates instances of duplicated data.For exa mple:  VAR! Unique SORT Index! Because CIASCII! Colour! Year N UMERIC  NOUNSET NOEMPTY - Eliminates rows that contain only UNSET values.  VAR! Index SORT NOUNSET! Because CIASCII! Colour! Year NUMERIC  To sort these arrays and identify the last oCcurren ce of each group of the same car type, use The LASTINGROUP option:  VAR! Index SORT! Because LASTINGROUP! Group Suppose we had sorted the array! Car and another ar ray! Value using the command:  VAR! Index SORT! Because! Value LASTINGROUP! Group We can then generate an array of subtotals for each type of car with the following command:  VAR! Totals SUBTOTAL! Values! Index! Group  VAR! Variable SUBTOTAL - This will sum value strings that contain values with or without Unit qualifiers. Unit qUalifiers within the strings will be ignored. This is to allow REPORTER to Still operate with unit qualified value strings tha t may have been introduced by other VAR or $! Variable commands.  VAR! Variable EVALUATE - Will return string variables andArrays of unit qualified values if The evaluation generates quantities with physical d imensions. VAR! D EVAL (DIAM) for all CYLI - sets! D to a set of strings such as '90cm' ' 60cm' etc. - when cm are the current length Units). The unit will be the current working unit.VAR! Variable ATTRIBUTE This sets the variable to a string that contains t he value AND The unit qualifier for attributes with of a physica l quantity VAR! X XLEN sets! X to '46cm' if Current units are cm) The unit will be the current working unit."}
{"Headers": "The Collection Syntax PML 1 ", "Content": "Sorting Arrays using the VAR Command \n These facilities were designed to work with arrays  of STRINGS. Where a multi-level sort is required it is still necessary to use the older facilities of the VAR command to perform the sort. Using a different example, look at the arrays  !Car, !Colour and !Year: \n \nVAR !Index SORT !Car CIASCII !Colour !Year NUMERIC \n \n Sorting   Option Effect  \nCIASCII Sorts in ascending case-independent alphabe tic order. \nDESCENDING Sorts in alphabetic in reverse order \nCIASCII DESCENDING Sorts in descending case-indepen dent alphabetic order. \nNUMERIC Forces an ascending numerical sort on numbe rs held as strings. \nNUMERIC DESCENDING Forces a descending numerical so rt on numbers held as strings. \n \nYou can also modify the array to eliminate empty or  repeated elements: \n \nUNIQUE  - Eliminates instances of duplicated data. For example: \n \nVAR !Index SORT UNIQUE !Car CIASCII !Colour !Year N UMERIC \n \nNOUNSET NOEMPTY  - Eliminates rows that contain only UNSET values. \n \nVAR !Index SORT NOUNSET !Car CIASCII !Colour !Year NUMERIC \n \nTo sort these arrays and identify the last occurren ce of each group of the same car type, use the LASTINGROUP  option: \n \nVAR !Index SORT !Car LASTINGROUP !Group \nSuppose we had sorted the array !Car and another ar ray !Value using the command: \n \nVAR !Index SORT !Car !Value LASTINGROUP !Group \n \nWe can then generate an array of subtotals for each  type of car with the following command: \n \nVAR !Totals SUBTOTAL !Values !Index !Group \n \nVAR !variable SUBTOTAL  - This will sum value strings that contain values with or without unit qualifiers. Unit qualifiers within the strings  will be ignored. This is to allow REPORTER to still operate with unit qualified value strings tha t may have been introduced by other VAR or \n$!variable commands. \n \nVAR !variable EVALUATE  - Will return string variables and arrays of unit qualified values if the evaluation generates quantities with physical d imensions. VAR !D EVAL (DIAM) for all CYLI - sets !D to a set of strings such as '90cm' ' 60cm' etc. - when cm are the current length \nunits). The unit will be the current working unit. \n \nVAR !variable ATTRIBUTE  This sets the variable to a string that contains t he value AND the unit qualifier for attributes with of a physica l quantity VAR !X XLEN sets !X to '46cm' if current units are cm) The unit will be the current working unit. \n  "}
{"Headers": "The Collection Syntax PML 1 ", "Content": "Expression search criteria applied to collection eq uates to \"with (GTYP eq 'BEAM')\" ! Expression = object EXPRESSION() ! expression.expression('GTYP eq ''BEAM''') Define Collection ! Collection = object COLLECTION() ! Collection.scope(! Scope)! collection.addType(! elementType) ! Collection.filter(! Expression) !! sectionPML2 = ! Collection.results()  Example 2:  PML 1 collection  Var! myColl collect ALL (VALV INST) WITH (spec of s pref eq /INST ) FOR /TUB_PRUEBA /Tuberias_para_aplicacionesPML 2 Collection  ! myColl = !! CollectAllFor('VALV INST', 'spec of spr ef eq /INST', /TUB_PRUEBA /Tuberias_para_aplicaciones ! Coll = object COLLECTION() ! Coll.type('<gtype>') ! Coll.scope(<dbref>) ! Coll.filter(<expression>) ! Coll.initialize() ! ListOfItems = !Coll.results()  Note: Remember that this returns an array of DBREFS and not STRINGS  Example 3:  PML 1 collection  Var! Test coll all pipe with matchw (purp,'*yourpur pose*') within vol ce 1000 Var! Test1 eval name for all from! Test ! Dat = 'c:/temp/excel.Csv' ! Output = object file (! Dat) ! Output.writefile ('WRITE',! Test1) ! Output.close() Syscom 'c:/temp/excel.csv&'  Example 4:  PML 2 collection  ! Coll = object COLLECTION() ! coll.type('TRFAIL') ! Coll.scope(! Trinco) ! Coll.filter( object EXPRESSION('OWNER eq TRMLST') )! Coll.initialize() ! Scope = ! Coll.results()  -- Create an array of list names (for the dropdown) ! listNames = object ARRAY() ! listNames.append('ExampleList') ! listNames.append('AnotherList') -- Create a corresponding list of numbers (the RTEX T in the dropdown)"}
{"Headers": "The Collection Syntax PML 1 ", "Content": "! listNumbers = object ARRAY()! listNumbers.append('1') ! listNumbers.append('2')  -- Create an array of strings for contents of the f irst list (names or refnos) ! listContents = object ARRAY() ! listContents.append('/P-MA') ! listContents.append('/P-GA') ! listContents.append('/P-16B')-- Add the array of contents to a global variable !! Cdlist1 = object ARRAY() !! Cdlist1.appendarray(! listContents)  -- Repeat for a second list (optional) ! listContents = object ARRAY() ! listContents.append('/E-13') ! listContents.append('/S-13') !listContents.append('/P-16B') !! Cdlist2 = object ARRAY() !! Cdlist2.appendarray(! listContents)  -- Update the form with the DTEXT and RTEXT !! cdcList.name.dText = ! listNames !! cdcList.name.rText = ! listNumbers  -- Store the names in a global variable!! cdList = ! listNames  Example 5:  PML 2 collection  ! E = !! CollectAllFor('SCTN','', !! This ) ! E = !! CollectAllFor('PIPE','Pspec eq |/A3|', world ) ! E = object COLLECT() ! E.classes = 'ALL' ! E.types = 'sctn' ! Tmp = !! Collect(! E)  Note: There are more options, like!E.expression - this lets you add an expression to the Object, etc. The easiest way to see the options I t hink is to create the object then query it.  ! E = object COLLECT() Q var! E ! A = Object Collection() ! a.scope(/VALIDELY) ! a.type('TYPE') Example 6:  Conditions:  Type: TEE Stype: RDTE (reducing tee in our DB) Bore: DN100 Cbore: DN50 (bore of tee connection) Spec: /SOME_SPEC "}
{"Headers": "Array sorting", "Content": "PML 1 collection  Var! Tees coll all SPCO with ((GTYPE of catref eq ' TEE') and (STYPE eq 'RDTE' and PARAM1 of Catref eq 100)) for /SOME_SPEC  Note: What you get is anArray of specifications matchin g criteria. In this case this would be All reducing tees in catalog. You still don't know how to select the tee with correct reduced DN.  PML 2 collection  ! Elbows = !! collectallfor(|ELBO|,|gtype of catref i nset('ELBO') AND stype inset('PPBA') AND P1BORE eq 50mm|,!! This)  ! Directory = object file (|C:\\FOLDER|) ! dirFiles = ! Directory.files() -- Query! dirFiles: Q var! dirFiles  -- If you want to get only the filenames: ! fileList = object array() Do! I clues!dirFiles ! File = ! dirFiles[! I].entry() ! fileList.append(! File) Enddo  Q var! fileList ! Project = CURRENT PROJECT ! MyProj = ! Project.code() $p $p Project: $! MyProj $p ! xTab = | |  Var! Pipes collect all (PIPE) ! Asz = ArraySize(! Pipes) $P Array size: $!Asz  ! Output = object ARRAY() ! xRec = |'PIPE| & |$! xTab| & |ZONE| & |$! xTab| & |P SPEC| & |$! xTab| & |ISPEC| & |$! xTab| & |:STATUS'| ! Output.append($! xRec) Var! Names evaluate (name) for all from! Pipes ! NewPositions = ! names.SortedIndices() ! Names.Sort()  Var! Zones evaluate (name of zone) for all from! Pi pes Var! Pspes evaluate (pspe) for all from! Pipes Var! Ispes evaluate (ispe) for all from! Pipes Var! Stats evaluate (:status) for all from! Pipes  ! zones.ReIndex(! NewPositions) ! pspes.ReIndex(!NewPositions) ! ispes.ReIndex(! NewPositions) ! stats.ReIndex(! NewPositions) "}
{"Headers": "Kupdf.net_pdms-pml-manual-1 ", "Content": "do! Pipe index! Pipes ! Record =! Names[! Pipe] & |$! xTab| & ! Zones[! Pipe ] & |$! xTab| & ! Pspes[! Pipe] & |$! xTab| & ! Ispes[! Pipe] & |$! xTab| & ! Stats[! Pip e] ! Output.append(! Record) Enddo  ! File = object FILE('%PDMSuser%\\$!MyProj_PipeList.t xt') ! file.writefile('OVERWRITE',! Output) $p $p Macro finished  Resulting sample output of PML report (623 records): PIPE ZONE PSPEC ISPEC :STATUS /1\"-D173015-11180-H4-0001 /PIP-17000-71 /11180-H4 = 0/0 1 /1\"-R172002-11085-R /PIP-17000-FLARE /11180-H4 =0/0 1/1\"-R17200X-11085-R /PIP-17000-FLARE /11180-H4 =0/0 1 /10\"-B172001-11380-H1-0001-1 /PIP-17000-FLARE /1138 0-H1 =0/0 1 /10\"-B172002-11380-H1-0001-1 /PIP-17000-FLARE /1138 0-H1 =0/0 1 /10\"-B172035-11380-H1-0001 /PIP-17000-FLARE /11380- H1 =0/0 1 /10\"-B172036-11380-H1-0001 /PIP-17000-FLARE /11380- H1 =0/0 1 PML 2 array sorting ! Project = CURRENT PROJECT ! MyProj = ! Project.code()  $p $p Project: $! MyProj $p  ! TwldX = |*| ! xTab = | | ! Output = object ARRAY() ! xRec = |'PIPE| & |$! xTab| & |ZONE| & |$!xTab| & |P SPEC| & |$! xTab| & |ISPEC| & |$! xTab| & |:STATUS'| ! Output.append($! xRec)  ! Collect = object COLLECTION() ! Collect.scope(WORLD) ! Collect.type('PIPE') ! Collect.expression(object EXPRESSION('SUBSTR(NAME, 1,1) eq |/|') )  ! Pipes = ! Collect.Results() ! Names = object ARRAY() Do! Pipe values! Pipes ! Names.append(! Pipe.name) Enddo  ! Clues = ! Names.sortedindices() ! Pipes.reindex(! Indices)  ! Zones = ARRAY() ! PSpecs = ARRAY() ! ISpecs = ARRAY() ! udaSTATUS = ARRAY()  ! I = 1 Do! Pipe values!Pipes -- $p $! Pipe.name ! Zones.append(! Pipe.owner.name) -- q var! Zones ! PSpecs.append(! Pipe.pspec.name) "}
{"Headers": "Kupdf.net_pdms-pml-manual-1 ", "Content": "do !Pipe index !Pipes \n  !record = !names[!Pipe] & |$!xTab| & !zones[!Pipe ] & |$!xTab| & !pspes[!Pipe] & \n  |$!xTab| & !ispes[!Pipe] & |$!xTab| & !stats[!Pip e] \n  !output.append(!record) \nEnddo \n \n!file = object FILE('%PDMSuser%\\$!MyProj_PipeList.t xt') \n!file.writefile('OVERWRITE',!output) \n$p \n$p Macro finished \n \nResulting sample output of PML report (623 records) : \nPIPE ZONE PSPEC ISPEC :STATUS \n/1\"-D173015-11180-H4-0001 /PIP-17000-71 /11180-H4 = 0/0 1 \n/1\"-R172002-11085-R /PIP-17000-FLARE /11180-H4 =0/0  1 \n/1\"-R17200X-11085-R /PIP-17000-FLARE /11180-H4 =0/0  1 \n/10\"-B172001-11380-H1-0001-1 /PIP-17000-FLARE /1138 0-H1 =0/0 1 \n/10\"-B172002-11380-H1-0001-1 /PIP-17000-FLARE /1138 0-H1 =0/0 1 \n/10\"-B172035-11380-H1-0001 /PIP-17000-FLARE /11380- H1 =0/0 1 \n/10\"-B172036-11380-H1-0001 /PIP-17000-FLARE /11380- H1 =0/0 1 \nPML 2 array sorting \n!Project = CURRENT PROJECT \n!MyProj = !Project.code() \n \n$p \n$p Project: $!MyProj \n$p \n \n!TwldX = |*| \n!xTab = | | \n!output = object ARRAY() \n!xRec = |'PIPE| & |$!xTab| & |ZONE| & |$!xTab| & |P SPEC| & |$!xTab| & |ISPEC| & |$!xTab| & \n|:STATUS'| \n!output.append($!xRec) \n \n!Collect = object COLLECTION() \n!Collect.scope(WORLD) \n!Collect.type('PIPE') \n!Collect.expression(object EXPRESSION('SUBSTR(NAME, 1,1) eq |/|') ) \n \n!Pipes = !Collect.results() \n!Names = object ARRAY() \ndo !Pipe values !Pipes \n  !Names.append(!Pipe.name) \nEnddo \n \n!Indices = !Names.sortedindices() \n!Pipes.reindex(!Indices) \n \n!Zones = ARRAY() \n!PSpecs = ARRAY() \n!ISpecs = ARRAY() \n!udaSTATUS = ARRAY() \n \n!i = 1 \ndo !Pipe values !Pipes \n  -- $p $!Pipe.name \n  !Zones.append(!Pipe.owner.name) \n  -- q var !Zones \n  !PSpecs.append(!Pipe.pspec.name) "}
{"Headers": "Functions, Macros and Object Definitions ", "Content": "PML general futures Functions and Macros are PML Files that contain st ored sequences of commands. The PML FileIs invoked whenever this sequence of comma nds is required. The PML file may Also include control logic which alters the order i n which the commands are carried out and Special commands for handling errors. PML Files are normally created using a text editor.PML Functions and methods on objects (including for ms) are the recommended way of Storing command sequences because:  \u2022 There is a check that they have been called with t he right type of arguments. \u2022 Arguments can return values. \u2022 A PML Function oR method can return a result of an y type.  Most new AppWare code is written as methods on obj ects. PML Macros are explained in Macros as they are the basis of the older AppWare c ode. PML Macros are normally stored in A directory under the PDMSUI search-path.PML Funct ions are automatically loaded from a Directory under the PMLLIB search-path. Comments are additional text included in a PML Fil e for the benefit of someone reading The PML code. The PML processor ignores comments an d so they do not affect the way theCode executes. For a simple one line comment, begin the line with - - (two dashes) or $* (Dollar and asterisk).  - - This is a new-style PML comment - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $* The following lines calculate the new angleYou can also use $* to add an inline comment to any line of PML. A comment may extend Over several lines provided it is enclosed in the e scape sequences: $( and $) $( A comment containing Skip if (! X EQ! Y) More than one line $) At any point wiThin a PML File a return command wi ll stop further execution of the file and Return to the calling PML File, if there is one:  If ( count EQ 0 ) then Return Endif  For clarity, return can be used as the final line o f a PML Macro. However, the use of thisCommand is not essential and there will be no error if it is not used. Note: This is a different Use of return from the command used to set return v alues of variables. Everything written in PML, including keywords such as if, do and else means the sameThing in upper or lower case. The exception is text enclosed between quotes or vertical bars, Which is used exactly as it is typed. Throughout th is document you will see examples of PML Code using a mixture of upper and lower case for re adability. "}
{"Headers": "Special Character $ ", "Content": "Abbreviations Many commands have a minimumAbbreviation which ca n be used in place of the full Command. For readability it is recommended that you use the full form of the command \u2014 Note that it is not less efficient than using the a bbreviation. PML keywords such as if, else And do have no abbreviations.The $ character has a special meaning in PML. It i s an escape character, which means That together with the character which follows it a re treated as a special instruction to PML. The pair of characters beginning with $ is known as an escape sequence.$P is a commonly Encountered example, which is used to output a mess age to the screen: $P This text will be output to the screen  A number of other escape sequences will be described ed later in this manual. The important Point to note here that if yOr need the dollar char acter itself as part of a command, you will Need to double it ($$). As the last character on a line, $ means that the next line is a Continuation line. For example: $P This is an example of a much longer message that will be $ output to the screen$! The PML variable following the! (Gold!!) Is expa nded as a string by using its own . STRING() Method.  Note: Real values are automatically expanded with any un it qualify appended if the value is A physical quantity. This is useful on $P lines oR converting real values to strings in Commands. $newline command continues on next line w ithout being automatically closed.  $M/filename execute a text file as a sequence of co mmands or an input macro. Named Using its filename or pathname.  The Dollar $ symbol and its meanings$M = Runs a macro in pdms $! = Evaluate a variable $. = Terminates a macro $S = Defines a synonym $G = Defines a global synonym $S- = Turns synonyms off $S+ = Turns synonyms On $QS = Query's the synonyms $H = Help $Q = Another syntax help $P = PRints a line to your command line $$ = Adds a $ symbol $D = Default argument value  To turn the pml trace on and off I use  $R<n> $R0 = Turn trace Off $R6 = Turn trace On $R1 = Tracing to shell window (default) $R2 = Tracing to requests window $R4 = Tracing of only input lines executed $R8 = Tracing of all input lines $R16 = Tracing without $ expression (Default off) $R32 = Tracing includes line numbers $R64 = Tracing of macro/function changes $R100 = General Debugging $R102 = capture trace in ALPHA LOGText strings must be enclosed in either single quo tes, or apostrophes, or vertical bars: ('Apostrophes' or |vertical bars| ). The apostrophe s and vertical bars are known as delimiters. Take great care to avoid unmatched delimiters as th is can lead to many lines of PML codeBeing included as part of the text string, and so l ost. "}
{"Headers": "Storing and Loading PML Files", "Content": "Abbreviations \n Many commands have a minimum abbreviation which ca n be used in place of the full command. For readability it is recommended that you  use the full form of the command \u2014 note that it is not less efficient than using the a bbreviation. PML keywords such as if, else \nand do have no abbreviations. \n The $ character has a special meaning in PML. It i s an escape character, which means that together with the character which follows it a re treated as a special instruction to PML. \nThe pair of characters beginning with $ is known as  an escape sequence. $P is a commonly encountered example, which is used to output a mess age to the screen: \n$P This text will be output to the screen \n \n A number of other escape sequences will be describ ed later in this manual. The important point to note here that if you need the dollar char acter itself as part of a command, you will need to double it ($$). As the last character on a line, $ means that the next line is a \ncontinuation line. For example: \n$P This is an example of a much longer message that  will be $ output to the screen \n \n$! The PML variable following the ! (or !!) is expa nded as a string by using its own .STRING() method. \n \nNote:  Real values are automatically expanded with any un it qualifier appended if the value is a physical quantity. This is useful on $P lines or converting real values to strings in commands. $newline command continues on next line w ithout being automatically closed. \n \n$M/filename execute a text file as a sequence of co mmands or an input macro. Named using its filename or pathname. \n \nThe Dollar $ symbol and its meanings \n \n$M = Runs a macro in pdms \n$! = Evaluate a variable \n$. = Terminates a macro \n$S = Defines a synonym \n$G = Defines a global synonym \n$S- = Turns synonyms off \n$S+ = Turns synonyms On $QS = Query\u2019s the synonyms \n$H = Help \n$Q = Another syntax help \n$P = Prints a line to your command line \n$$ = Adds a $ symbol \n$D = Default argument value \n \nTo turn the pml trace on and off I use \n \n$R<n> \n$R0 = Turn trace Off \n$R6 = Turn trace On \n$R1 = Tracing to shell window (default) \n$R2 = Tracing to requests window \n$R4 = Tracing of only input lines executed \n$R8 = Tracing of all input lines $R16 = Tracing without $ expression \n(default off) \n$R32 = Tracing includes line numbers \n$R64 = Tracing of macro/function changes \n$R100 = General Debugging \n$R102 = capture trace in ALPHA LOG \n Text strings must be enclosed in either single quo tes, or apostrophes, or vertical bars: \n('apostrophes' or |vertical bars| ). The apostrophe s and vertical bars are known as delimiters. \nTake great care to avoid unmatched delimiters as th is can lead to many lines of PML code being included as part of the text string, and so lost. "}
{"Headers": "IF Construct ", "Content": "PML Control logicThere are four types of construct for implementing control logic within a PML Function or Macro. These are: \u2022 The if construct for conditional execution of comm ands. \u2022 The do command for looping and the associated brea k and skip. \u2022 The golabel for jumping to a line with a label.\u2022 The handle construct for dealing with errors. The full form of an if-construct is as follows:  If (! Word EQ 'Peanuts' OR! Word EQ 'Crisps') then ! Snacks = ! Snacks + 1 ! Meal = FALSE Elseif (! Word EQ 'Soup') then ! Starters = ! Starters + 1! Meal = TRUE Elseif (! Word EQ 'Fruit' Gold! Word EQ 'IceCream' ) t hen ! Puddings = ! Puddings + 1 ! Meal = TRUE Else ! MainCourse =! MainCourse + 1 ! Meal = TRUE Endif  Each BOOLEAN expression, such as (! Word EQ 'Soup') , is examined in turn to seeWhether it is TRUE or FALSE. As soon as an expressi on that is TRUE is encountered, the Following block of commands is executed. Once a blo ck of commands has been executed, Everything else up to the endif is ignored. The els e command is optional. If it is included, youCan be sure that exactly one command block within t he if-construct will be executed. The Elseif commands are also optional. Once one of the elseif expressions has been found to be TRUE, any remaining elseif commands are ignored. Th us the simplest form of the if-Construct is:  If (! Number LT 0 ) then ! Negative = TRUE Endif  You may not concatenate the commands into one line, so the following expressions are not If (! TrueValue OR! UnsetValue) If (! FalseValue AND! UnsetValue) Don't know! UnsetValue if thE value is not required to determine the outcome of the expression. The same is true for PML Functions which have retur ned an error.  Any if-construct may contain further if ... elseif ... endif constructs:  If (! Number LT 0) then ! Negative = TRUEIf (! Number EQ -1 ) then ! OnlyJustNegative = TRUE Endif Endif It is particularly helpful with nested if construct s to indent the code so that the logic is clear. "}
{"Headers": "BOOLEAN Expressions and if Statements ", "Content": "IF, THEN, ELSEIF and ELSE Statements An IF construct can beExtended by adding addition al conditions. This is done by adding Either ELSEIF or ELSE to it. When an IF construct i s encountered, PML will evaluate its Condition. If the condition is FALSE, PDMS will loo k to the next ELSEIF condition. Once a ConditiOn is found to be TRUE, that code will be ru n that proportional of the code and the IF Construct is complete. If an ELSE condition is adde d, this portion of code will only be run if The other conditions are never met. This is a way o f ensuring some code is always run.If ($1 EQ 0) THEN $p Your value is zero Elseif ($1 LT 0) THEN $p Your value is less than zero Else $p Your value is Greater than zero Endif  The ELSEIF and ELSE commands are optional, but ther e can only be one ELSE command In an IF construct.New expressions based on the operators such as EQ and GT give a BOOLEAN result That can be used directly in a PML2 if test: If (! NewValue - 1 GT 0) then  The expression can be a simple variable provided it is a BOOLEAN type variable: ! Success =! NewValue GT 0If (! Success) then The expression could be a user-defined PML Function provided it returns a BOOLEAN Result: if (!! MyFunction() ) then  Note: The BOOLEAN constants TRUE, FALSE, YES and NO and t heir single-letter abbreviations Not enclosed in quoTes return BOOLEAN results and s o can be used directly in expressions. For example:  Code Result Type If ( TRUE ) BOOLEAN If ( FALSE ) If ( T ) BOOLEAN If ( F ) If ( YES ) BOOLEAN If ( NO ) If ( Y ) BOOLEAN If ( N )  The following do not retUrn BOOLEAN values and are therefore invalid:  Code Result Type If ( 1 ) REAL If ( 0 ) If ( 'TRUE' ) STRING If ( 'FALSE' ) If ( 'T' ) STRING If ( 'F' ) Variable = 1 REAL If ($Variable) "}
{"Headers": "IF TRUE Expression ", "Content": "For upward compatibility with PML1, STRING variable s set to 'TRUE', 'FALSE', 'YES' or 'NO' or their singlE-letter abbreviations can be us ed in an if-test as long as they are Evaluated with a preceding $. For example:  Code Result Type Variable = 'TRUE' STRING If ($Variable)  There is a built-in PML Method and a function for c onverting a value to BOOLEAN:! MyString = 'TRUE' If (! MyString.Boolean() ) then  The Boolean conversion is as follows:  Code Result REAL zero FALSE $* All other positive and negative REAL values TRUE STRING 'FALSE, 'F', 'NO' and 'N' FALSE STRING 'false, 'f', 'no' and 'n' FALSESTRING 'TRUE', 'T', 'YES' AND 'Y' TRUE STRING 'true', 't', 'yes' and 'y' TRUE IF TRUE will return a value of the type defined by the second and third arguments. If the Initial Boolean expression is true, the result of t he first expression is returned.If false, the Result of the second expression is returned. Both t he second and third arguments are fully Evaluated regardless of the value of the Boolean. T his is because the function is evaluated Using reverse polish procedure (as is the case of t he expression design).This allows the IF Statement to be nest able with any of the arguments to IF capable of including other IF Functions.  If logical1 expression is set to true, then value o f typeX1expression is returned If logical1 Expression is set to false, then vAlue of typeX1 ex pression is returned typeX1 and typeX2 Are two arguments of the same type which may be:  Logical Logical Array Real Real Array ID ID Array Text Position Direction For upward compatibility with PML1, STRING variable es set to 'TRUE', 'FALSE', 'YES' or'NO' or their single letter abbreviations can be us ed in an if test as long as they are Evaluated with a preceding $. For example:  If ($Variable) where Variable = 'TRUE' STRING OK   "}
{"Headers": "Stopping a DO loop: break and breakif", "Content": "For upward compatibility with PML1, STRING variable s set to \u2018TRUE\u2019, \u2018FALSE\u2019, \u2018YES\u2019 or \u2018NO\u2019 or their single-letter abbreviations can be us ed in an if-test as long as they are evaluated with a preceding $. For example: \n \nCode Result Type \nVariable = \u2018TRUE\u2018 STRING \nif ($Variable) \n \nThere is a built-in PML Method and a function for c onverting a value to BOOLEAN: \n \n!MyString = \u2018TRUE\u2019 \nif (!MyString.Boolean() ) then \n \nThe Boolean conversion is as follows: \n \nCode Result \nREAL zero FALSE \n$* All other positive and negative REAL values TRUE  \nSTRING \u2018FALSE, \u2018F\u2019, \u2018NO\u2019 and \u2018N\u2019 FALSE \nSTRING \u2018false, \u2018f\u2019, \u2018no\u2019 and \u2018n\u2019 FALSE \nSTRING \u2018TRUE\u2019, \u2018T\u2019, \u2018YES\u2019 AND \u2018Y\u2019 TRUE \nSTRING \u2018true\u2019, \u2018t\u2019, \u2018yes\u2019 and \u2018y\u2019 TRUE \n IF TRUE will return a value of the type defined by  the second and third arguments. If the initial Boolean expression is true, the result of t he first expression is returned. If false, the result of the second expression is returned. Both t he second and third arguments are fully \nevaluated regardless of the value of the Boolean. T his is because the function is evaluated using reverse polish procedure (as is the case of t he expression design). This allows the IF statement to be nest able with any of the arguments  to IF capable of including other IF \nfunctions. \n \nIf logical1 expression is set to true, then value o f typeX1expression is returned  If logical1 expression is set to false, then value of typeX1 ex pression is returned typeX1 and typeX2 are two arguments of the same type which may be: \n \nLogical \nLogical Array \nReal \nReal Array \nID \nID Array \nText \nPosition \nDirection \n For upward compatibility with PML1, STRING variabl es set to \u2018TRUE\u2019, \u2018FALSE\u2019, \u2018YES\u2019 or \u2018NO\u2019 or their single letter abbreviations can be us ed in an if test as long as they are evaluated with a preceding $. For example: \n \nif ($Variable) where Variable = \u2018TRUE\u2019 STRING OK \n \n  "}
{"Headers": "Nested DO Loops ", "Content": "do! X ! Number = ! Sample[! X] If ((INT(!Number/2) NE (! Number/2)) then Skip Endif ! Result = ! Result +! Number Enddo  The skip if command can sometimes be more convenien t:  Do! X ! Number = ! Sample[! X] Skip if (INT(! Number/2) NE (! Number/2)) ! Result = ! Result +! Number EnddoYou can nest do-loops one inside the other. The co unter for each loop must have a Different name.  Do! X to 10 Do! Y ! Z = ! X +! Y Break if (! Y GT 5) Enddo Enddo  The inner-most loop goes through all the values of! Y before the outer loop moves on to theSecond value of! X. Note that the break (or skip) c ommand acts just on the loop containing it - in this case the inner-most loop. DO Index and DO Values are ways of looping through arrays. This is an effective method For controlling the values used for the loops.Typi cally values are collected into an ARRAY Variable then looped through using the following:  Do! X values! ARRAY ! X takes each ARRAY element (! X is an element!!!) Enddo  Do! X index! ARRAY ! X takes a number from 1 to! ARRAY size (! X is a number!!!) Enddo Type out the following as an example of looping thr ough an ARRAY of values.  VAR! Zones COLL ALL ZONES FOR SITE VAR! Names EVAL NAME FOR ALL FROM! Zones Q var! Names  Do! X VALUES! Names Q var! X Enddo  Do! X INDEX! Names Q var!Names[! X] Enddo "}
{"Headers": "Jumping to a Labelled Line ", "Content": "DO Values with Arrays of Objects Imagine that we have already defined an object typ e EMPLOYEE which contains a Member of type STRING. We create an array of EMPLOY EE objects and set the Name Member of each of each object.  ! MyEmployees[1] = object EMPLOYEE()! MyEmployees[2] = object EMPLOYEE() ! MyEmployees[3] = object EMPLOYEE() ! MyEmployees[1]. Name = 'James' ! MyEmployees[2]. Name = 'Joe' ! MyEmployees[3]. Name = 'Mike'  We then wish to create a new array containing just the employees' names.  ! Names = ARRAY()Do! Person VALUES! MyEmployees ! Names.Append(! Person.Name) Enddo  Each time round the do-loop, the do-variable become s an object of the appropriate type, Even if the array is a heterogeneous mixture of obj ects. The golabel command in PML allowYou to jump to a line with a matching label name  LABEL /FRED : : GOLABEL /FRED  The label name /FRED has a maximum length of 16 characters , excluding the / slash Which must be present. The next line to be executed will be the line following LABEL /FRED,Which could be before or after the GOLABEL command. Do! A Do! B to 3 ! C = ! A * ! B Golabel /finished if (! C GT 100) ! Total = ! Total +! C Enddo Enddo Label /finished $P Total is $! Total  If the expression! C GT 100 is TRUE there wIll be a jump to LABEL /FINISHED and PML Execution will continue with the line  $P Total is $! Total  If the expression is FALSE , PML execution will continue with the line:  ! Total = ! Total +! C "}
{"Headers": "Errors and Error Handling ", "Content": "Illegal Jumping The following is an illegal jump into a nested do b lock. It is however allowed to jump out ofA nested block to a line in an enclosing block.  Golabel /illegaL Do! Count to 5 ! Total = ! Total +! Count Label /illegal Enddo An error condition can occur because a command cou ld not complete successfully or Because of a mistake in a PML Macro or function.Th e presence of an error normally has Three effects:  \u2022 An Alert box appears which the user must acknowled ge \u2022 An error message is output together with a trace b ack of any calling macros or Functions. \u2022 Any currently running PML Macros and functions are abandoned.This example of an error is caused by an attempt to use a PML Variable that does not exist:  (46,28) ERROR - Variable FRED not defined  The 46 is the module or program section which identified the error and is the error code itself Is 28 . If thE input line had been typed interactively th at is the end of the story. However, if the Input line was part of a PML Macro or function the error may optionally be handled. An error arising during the processing of a PML Ma cro or function does not immediatelyGive rise to an error message - this depends on the next line of input. Provided the next Command processed by PML is a matching handle comma nd, the error is not output and the Commands within the matching handleblock are proces sed instead. Elsehandle blocks mayOptionally also be present - if the handle block do es not match the error one elsehandle will Be processed - if it matches the error:  $* a command causes Error(46, 28) Handle (46, 27) $* handle block - not processed this time Elsehandle (46, 28)$* The commands in this matching handle block are processed Next Elsehandle ANY $* An ANY Handle Block is processed for any error s. In this position it would handle errors Other than (46, 27) and (46,28) Elsehandle NONE $* A NONE Handle BloCk is processed only if there were no errors Endhandle  $* This line is processed after the handle block.  If (46,27) matches the error, PML processes the com mands in that handle block instead of Outputting an error. Processing of the current PML MAcro or function continues at the line After the endhandle command. "}
{"Headers": "Setting the ONERROR Behavior", "Content": "Illegal Jumping \nThe following is an illegal jump into a nested do b lock. It is however permitted to jump out of a nested block to a line in an enclosing block. \n \ngolabel /illegaL \ndo !Count to 5 \n  !Total = !Total + !Count \n  label /illegal \nenddo \n An error condition can occur because a command cou ld not complete successfully or because of a mistake in a PML Macro or function. Th e presence of an error normally has three effects:  \n\u2022 An Alert box appears which the user must acknowled ge \n\u2022 An error message is output together with a trace b ack of any calling macros or functions. \n\u2022 Any currently running PML Macros and functions are  abandoned. \n \nThis example of an error is caused by an attempt to  use a PML Variable that does not exist: \n \n(46,28) ERROR - Variable FRED not defined \n \nThe 46  is the module or program section which identified the error and is the error code itself is 28 . If the input line had been typed interactively th at is the end of the story. However, if the input line was part of a PML Macro or function the error may optionally be handled. \n An error arising during the processing of a PML Ma cro or function does not immediately give rise to an error message - this depends on the  next line of input. Provided the next command processed by PML is a matching handle comma nd, the error is not output and the \ncommands within the matching handleblock are proces sed instead. Elsehandle blocks may optionally also be present - if the handle block do es not match the error one elsehandle will be processed - if it matches the error: \n \n$* a command causes Error(46, 28) \nhandle (46, 27) \n  $* handle block - not processed this time \nelsehandle (46, 28) \n  $* The commands in this matching handle block are  processed \n  next \nelsehandle ANY \n  $* An ANY Handle Block is processed for any error s. In this position it would handle errors \nother than (46, 27) and (46,28) \nelsehandle NONE \n  $* A NONE Handle Block is processed only if there  were no errors \nEndhandle \n \n$* This line is processed after the handle block. \n \nIf (46,27) matches the error, PML processes the com mands in that handle block instead of \noutputting an error. Processing of the current PML Macro or function continues at the line \nafter the endhandle command. "}
{"Headers": "Handling Files and Directories ", "Content": "return error  You can also re-instate the error but suppress the alert using the command: Return error noalert  To generate a new error (or replace an error with y our own error) plus an optional message, Use one of the followingReturn error 1 Return error 1 'Your error message' Return error 1 NOALERT  To handle such an error there is a special form of the handle command:  Handle 1 PML code to handle a user-defined error number Endhandle Reading and writing files isGreatly simplified by using the FILE object. This chapter Describes the methods most frequently used for read ing and writing. Methods are also Provided for moving, copying and deleting files and extracting information such as the Pathname of a file,Its size data and time last mod ified. A FILE object may refer to a directory Rather than a file and methods are provided for nav igating around the directory structure. For A complete list of the methods available, refer to the Software Customization ReferenceManual. A file object is created by invoking the FILE cons tructor with the name of the file as its Argument. For example:  ! MyFile = object FILE ('c:\\users\\bob\\list.txt') ! MyFile = object FILE (/net/usr/bob/list') ! MyFile = object FILE ('%PDMSUSER%\\bob\\list.Txt')  At this stage, the file may or may not exist \u2014 cre ating the FILE object does not open or Access the file in any way. This example reads pair s of numbers from file data, adds them Together and writes the answers to file RESULTS.  ! Input = object FILE('DATA')! Input.Open('READ') ! Output = object FILE('RESULTS') ! Output.Open('WRITE') C ! Line = ! Input.ReadRecord() If (! Line.set()) then ! Array = ! Line.Split() ! Total = ! Array[1]. Real() +! Array[2]. Real() ! Output.WriteRecord( ! Total.String() )Else Estate car Endif Enddo ! Output.Close() ! Input.Close() "}
{"Headers": "Writing to Files ", "Content": "Reading from Files When reading a file one line at a time using the R eadRecord() method you must open the File first with the Open('READ') method and close i t afterwards with the Close() method. Each line read from the file wilL be returned as a STRING until the end of the file is reached, When you will get an UNSET STRING returned. The UNS ET string can be detected using The STRING object's Set() method (or Unset()) When you open a file for writing, the file will be created if it does not already exist.If you Use Open('WRITE') and the file already exists, the user will be shown an alert asking Whether the file can be overwritten. Alternatively you may specify OVERWRITE, to force Overwriting of a file if it already exists or APPEN D if you want to add to the end of a file if itAlready exists. You will obtain much quicker performance if you re ad or write an entire array in a single Operation. In particular you are recommended to use the ReadFile() method which returns The whole file as an array of strings, opening and closing the file automatically:! Input = object FILE('DATA') ! Output = object FILE('RESULTS') ! Lines = ! Input.ReadFile() ! ResultArray = ARRAY() Do! Line VALUES! Lines ! Numbers = ! Line.Split() ! Total = ! Numbers[1]. Real() +! Numbers[2]. Real() ! ResultArray.Append( ! Total.String() )Enddo ! Output.WriteFile('WRITE', ! ResultArray)  Note: With the ReadFile() method you may optionally specify the maximum number r of Lines you are prepared to read and an error is rais ed if this number is exceeded. If not Specified, a limit of 10000 is imposed.Errors will mainly be encountered when an attempt is made to open a file that does not Exist, has been mistyped or to which you do not hav e access. Anticipated errors may be Dealt with in a handle command following use of the Open() method. The errors mostCommonly encountered include the following:  (160,7) Argument to method is incorrect (160,9) File does not exist (160,36) Unable to read file record, file is not op en (160,37) Unable to write file record, file is not o pen (160,44) File exists, userDoes not want to overwri te it (160,47) File length has exceeded N lines (41,319) Cannot access file (Privileges insufficien t)  "}
{"Headers": "PML Macros ", "Content": "Macros are command sequences that are stored in te xt files. To access a macro file and Input the command sequence to your program, you run the macro. The file is scanned line-By-line, with exactly the same effect as if you wer e typing the lines in from a keyboard. Macro files may include synonyms and user-defined v ariables. They may also act on data Which you define when you give the command to run t he macro (parameterized macros).Macros are permanent records which may be called fr om within any working session of a Program. A macro file can be given any name that conforms t o the naming conventions of the Operating system. The suffix .mac is often used to indicate that the filename is that of aMacro, but this is optional. The process of reading the contents of a macro file as program Input is known as running the macro . The program does not discriminate between input From the GUI, the keyboard, or a macro file. To run a macro, enter: $M filenameWhere filename is the pathname of the macro file. The filename may optionally be preceded By a slash (/) character. If you give only the name of the file, the program will look for it in the Directory from which you executed the program. An e rror meSsage will be output if the file Cannot be found and opened for reading. It is often convenient to write a macro in a gener alized form, using parameters to Represent dimensions, part numbers etc., and to ass ign specific values to those parameters Only when the macro is to be run.In the simplest c ase, parameters are allocated positions in The command lines as macro arguments by inserting e scape codes of the form $n where n is An integer in the range 1 to 9. These arguments are then specified as part of the command To run the macro.They follow the macro name, with spaces separating the individual Arguments. For example, if a macro named beam.mac i ncludes the command line  NEW BOX XLEN $1 YLEN $2 ZLEN $3  Then the macro call $M/BEAM.MAC 5000 200 300 will run the macro and will set the lengthsDefined as $1, $2, $3 to 5000, 200 and 300 respecti vely. Arguments may be either values or Text, but note that a space in a text string will b e interpreted as a separator between two Different arguments. Apostrophes in text arguments are treated as parts of the arguments,Not as separators between them. For example, if a d demonstration macro arg.mac includes The lines: $P First Argument is $1 $P Second Argument is $2 $P Third Argument is $3  And is called by the command $M arg.mac 'Arg1a Arg1b' 'Arg2' 'Arg3'  The resulting output will beFirst Argument is 'Arg1a' Second Argument is 'Arg1b' Third Argument is 'Arg2'  Whereas the intended output was First Argument is 'Arg1a Arg1b' Second Argument is 'Arg2' Third Argument is 'Arg3' "}
{"Headers": "Using Macros and Functions Together", "Content": "Macros \n Macros are command sequences that are stored in te xt files. To access a macro file and input the command sequence to your program, you run the macro. The file is scanned line-by-line, with exactly the same effect as if you wer e typing the lines in from a keyboard. \nMacro files may include synonyms and user-defined v ariables. They may also act on data which you define when you give the command to run t he macro (parameterized macros). \nMacros are permanent records which may be called fr om within any working session of a program. \n A macro file can be given any name that conforms t o the naming conventions of the operating system. The suffix .mac is often used to indicate that the filename is that  of a macro, but this is optional. The process of reading  the contents of a macro file as program \ninput is known as running the macro . The program does not discriminate between input from the GUI, the keyboard, or a macro file. To run  a macro, enter: $M filename  \n \nwhere filename is the pathname of the macro file. The filename may  optionally be preceded by a slash (/) character. If you give only the name  of the file, the program will look for it in the directory from which you executed the program. An e rror message will be output if the file cannot be found and opened for reading. \n It is often convenient to write a macro in a gener alized form, using parameters to represent dimensions, part numbers etc., and to ass ign specific values to those parameters only when the macro is to be run. In the simplest c ase, parameters are allocated positions in \nthe command lines as macro arguments by inserting e scape codes of the form $n where n is an integer in the range 1 to 9. These arguments are  then specified as part of the command to run the macro. They follow the macro name, with spaces separating the individual \narguments. For example, if a macro named beam.mac includes the command line  \n \nNEW BOX XLEN $1 YLEN $2 ZLEN $3 \n \nthen the macro call $M/BEAM.MAC 5000 200 300 will run the macro and will set the lengths defined as $1, $2, $3 to 5000, 200 and 300 respecti vely. Arguments may be either values or text, but note that a space in a text string will b e interpreted as a separator between two \ndifferent arguments. Apostrophes in text arguments are treated as parts of the arguments, not as separators between them. For example, if a d emonstration macro arg.mac includes the lines: \n$P First Argument is $1 \n$P Second Argument is $2 \n$P Third Argument is $3 \n \nand is called by the command $M arg.mac \u2019Arg1a Arg1b\u2019 \u2019Arg2\u2019 \u2019Arg3\u2019 \n \nthe resulting output will be \nFirst Argument is \u2019Arg1a\u2019 \nSecond Argument is \u2019Arg1b\u2019 \nThird Argument is \u2019Arg2\u2019 \n \nwhereas the intended output was \nFirst Argument is \u2019Arg1a Arg1b\u2019 \nSecond Argument is \u2019Arg2\u2019 \nThird Argument is \u2019Arg3\u2019 "}
{"Headers": "PML2 Functions and Objects ", "Content": "PML 1 Hierarchy All PML1 Macros are in a directory structure point ed at by the variable PDMSUI. The PDMSUI environment variable Set PDMSUI=C:\\AVEVA\\plant\\PDMS12.0.2\\pdmsui  Picture Nr.2. - PML1 File hierarchy Standard AVEVA environment variable are set in a b at files called EVAR.bat in the Executable directory. All PML1 macros and forms ar e called using synonyms For example The macros and forms associated with piping are cal led using the synonym CALLP:$S CALLP=$M/%PDMSUI%/DES/PIPE/$s1 CALLP MPIPE  Note: This is why if all synonyms are killed that PDMS w ill no longer work properly.  It is normal practice to create a parallel hierarch y to contain any new or modified PML. These modifications canThen be called by modifying the PDMSUI variable to point at a multi Path. This can be done by putting a new file path i n front of the %PDMSUI% definition. This Will update the PDMSUI environment variable to incl ude the specified file path. Set PDMSUI=c:\\pmltraining\\PDMSUI %pdmsui%  The new file path should go in front of %PDMSUI% so this area is checked first for content. Once content is found, other locations will not be searched. This modification should be Done after the PDMSUI environment variable has been defined.This can be done at the Bottom of the EVAR.bat file or in the PDMS.bat file (after the line which calls evar.bat). The Environment variables can be checked with PDMS by u sing the q evar syntax q evar PDMSUI Or q evar 'SAM000' . The PMLLIB environmentNt variable points to a PML2 di rectory structure. Set PMLLIB= C:\\AVEVA\\plant\\PDMS12.0.2\\pmllib  Picture Nr.3. - PML2 File hierarchy There are 3 new file extensions .pmlfnc for Functi ons, .pmlfrm for Forms and .pmlobj for Objects, with these extensiOns the files will be lo aded by PDMS automatically when the Program is started. Functions are loaded by PDMS an d are run by typing the following !! Mymac(). This runs file mymac.pmlfnc. Forms are d isplayed by typing Show!! Myform or !! Myform.show()ObjEcts have to be assigned to a var iable before they can be used i.e.! X = Object MyObject() It is normal practice to create a parallel hierarc hy to contain any new or modified PML. These modifications can then be called by modifying the PMLLIB variable to point at a multi"}
{"Headers": "Updating PDMSUI and PMLLIB ", "Content": "path. This canBe done by putting a new file path i n front of the %PMLLIB% definition. This Will update the PMLLIB environment variable to incl ude the specified file path.  Set pmllib=c:\\pmltraining\\PMLLIB %pmllib%  The new file path should go in front of %PMLLIB% s o this area is checked first for Happy. Once content is found, other locations wil l not be searched. This modification should Be done after the PMLLIB environment variable has b een defined. This can be done at the Bottom of the EVAR.bat file or in the PDMS.Bat file (after the line which calls evar.bat). In AVEVA products environment variables can be checked using the q evar syntax i.e. q evar Pmllib. Edit the Evar.bat file to include multi paths for PDMSUI and PMLLIB. These settings Should be made at the bottom of the evar.Bat file  Set pdmsui=c:\\pmltraining\\pdmsui %pdmsui% Set pmllib=c:\\pmltraining\\pmllib %pmllib%  The setting of the variable can be checked in AVEV A Plant Design (PDMS) using the Following commands: q evar pdmsui and q evar pmllib . If a pmllib file is c once items haveBeen loaded by PDMS, it needs to be reloaded. This can be done by typing either pml Reload form!! NAME or pml reload object NAME If a new file is to pmllib, the files can be Remapped so PDMS knows where it is located. This is done by typing pml rehash onto theCommand line. This will update the first file locat ion in the search path. To update all search Paths, type pml rehash all . An object is a PML grouping of information. It may have MEMBERS (used to hold data) And METHODS (used to complete an action).Once assi gned to a variable, that variable Becomes an instance of that object. This means that variable will behave as the object Definition. While it is possible to create user-def ined objects (discussed later), PDMS is Supplied with a large number of built-in objects.A full list of these can be found in the PDMS Software Customization Reference Manual. For exampl e, type! Pos = object position() onto The command line. Query the variable and check the results against the members of a Position object listed in the reference manual.When working with built-in objects, there may also be BUILT-IN METHODS (object Dependents). These methods have been defined to com plete certain actions applicable to Object. For example, type the following into the co mmand line:  ! Value = |56| !Result = ! Value * 2  This example will have caused an error as a string cannot be used in an expression like This. To avoid the error, refer to the STRING objec t in the Reference Manual and find the .Real() method. This method translates the variableE from a STRING to a REAL so that it can Be used in the expression. The! Value remains a str ing, but! Results now becomes a REAL E.g.  ! Value = |56| ! Result = ! Value.real() * 2  "}
{"Headers": "Method Concatenation", "Content": "path. This can be done by putting a new file path i n front of the %PMLLIB% definition. This will update the PMLLIB environment variable to incl ude the specified file path. \n \nSet pmllib=c:\\pmltraining\\PMLLIB %pmllib% \n \n The new file path should go in front of %PMLLIB% s o this area is checked first for content. Once content is found, other locations wil l not be searched. This modification should be done after the PMLLIB environment variable has b een defined. This can be done at the \nbottom of the EVAR.bat file or in the PDMS.bat file  (after the line which calls evar.bat). In AVEVA products environment variables can be checked  using the q evar syntax i.e. q evar pmllib. \n Edit the Evar.bat file to include multi paths for PDMSUI and PMLLIB. These settings should be made at the bottom of the evar.bat file \n \nSet pdmsui=c:\\pmltraining\\pdmsui %pdmsui% \nSet pmllib=c:\\pmltraining\\pmllib %pmllib% \n \n The setting of the variable can be checked in AVEV A Plant Design (PDMS) using the following commands: q evar pdmsui and q evar pmllib . If a pmllib file is c once items have been loaded by PDMS, it needs to be reloaded. This can be done by typing either pml \nreload form !!NAME  or pml reload object NAME  If a new file is to pmllib, the files can be remapped so PDMS knows where it is located. This is  done by typing pml rehash  onto the command line. This will update the first file locat ion in the search path. To update all search \npaths, type pml rehash all . \n An object is a PML grouping of information. It may  have MEMBERS (used to hold data) and METHODS (used to complete an action). Once assi gned to a variable, that variable becomes an instance of that object. This means that  variable will behave as the object \ndefinition. While it is possible to create user-def ined objects (discussed later), PDMS is supplied with a large number of built-in objects. A  full list of these can be found in the PDMS Software Customization Reference Manual. For exampl e, type !pos = object position() onto \nthe command line. Query the variable and check the results against the members of a position object listed in the reference manual. \n When working with built-in objects, there may also  be BUILT-IN METHODS (object dependents). These methods have been defined to com plete certain actions applicable to object. For example, type the following into the co mmand line: \n \n!value = |56| \n!result = !value * 2 \n \n This example will have caused an error as a string  cannot be used in an expression like this. To avoid the error, refer to the STRING objec t in the Reference Manual and find the .real() method. This method translates the variable  from a STRING to a REAL so that it can \nbe used in the expression. The !value remains a str ing, but !results now becomes a REAL e.g. \n \n!value = |56| \n!result = !value.real() * 2 \n "}
{"Headers": "PML2 Functions ", "Content": "! Easting = !! CE.Href.Cpar[1] Cata parameter member (attribute) of a DBREF objec t. If the!! CE object member is an object with built-in metho ds, these methods can also be called:  ! PosWRTValve = !! CE.Hpos.WRT(ZONE) POSITION object w.r.t the owning ZONE  This process can also be reversed allowing the sett ing of attributes for the CE. This meansThat it is possible to record the current value of an attribute, modify and reassign back to the CE. For example, type out the following onto the co mmand line:  ! Pos = !! CE.Pos Q POS ! Pos.Up = 2000 !! CE.Pos = ! Pos Q POS  These lines will have moved the CE up by 2000.Try this example again with some other Attributes. Functions are new style macros which are pre-loade d by PDMS and can be called Directly. For example, to call the function called FuncName.pmlfnc, type!! FuncName() onto The command line. A function is defined within a .P mlfnc file stored within the PMLLIB file Path. For an example of a function, type the follow ing into a new file and save it as  c:\\pmltraining\\pmllib\\functions\\NameCE.pmlfnc. Define function!! NameCE() ! This = !! CE.fullname $p $! This EndfunctionTo run this function, type!! NameCE() onto the comm and line. You will notice the full name is Printed below it. This is an example of a NON-RETUR N function with NO ARGUMENTS. Yew The function can be given arguments which are then assigned to variables with the function.If a variable is returned, this means that the func tion can be assigned to another variable or As part of a calculation. Type out the following, a nd save it as  c:\\pmltraining\\pmllib\\functions\\Area.pmlfnc: Define function!! Area(! Radius is REAL) is REAL! CircleArea = ! Radius.Power(2) * 3.142 Return! CircleArea Endfunction  As this function is an example of a RETURN function with an ARGUEMENT, it can be used As part of an expression. The returned value is bas ed the functions argument and its type(REAL in this case ).   ! Height = 64 ! CylinderVolume = !! Area(2.3) *! Height Q var! CylinderVolume  As indicated by the !!, functions are global. This means that once defined, they can be called By any form or method within PDMS minimizing repeti tive code."}
{"Headers": "Composing Text ", "Content": "Using PML in AVEVA Products Most of this maNual describes how to use PML 2 to create and customize Forms and Menus. This chapter describes how to use PML within AVEVA products. Note that for tasks Such as defining Rules and Report Templates, you ar e restricted to the PML 1 expressions PackageDescribed in the Software Customization Reference Manual, and it is also Sometimes necessary to use the VAR command. It is sometimes necessary to arrange text in multi ple columns. The COMPOSE facility of The VAR command will help you do this. For examPle, if we create the following text string:  ! A = 'The quick brown fox jumped over the lazy dogs'  To compose the text we might use the following comm and:  VAR! Table COMPOSE |$! A| WIDTH 11 C SPACES 2 |$! A| WIDTH 15 R  This would give the following output:Index Value [1] The quick The quick brown' [2] brown fox jumped over' [3] jumped over the lazy dogs' [4] the lazy ' [5] dogs '  COMPOSE always returns an array with at least one element. The number of array Elements depends on the length ofThe text strings supplied and the width of each column. Notice that all of the STRING array elements are sp ace-padded to the same length. Following the COMPOSE keyword is a list of column d definitions. For each column, there is a Text string, such as |$!A| which evaluates to a tex t string, followed by the column layout Keywords in any order: Keyword Effect WIDTH n Specifies the space-padded width of this column. If not specified the width Of the column will be the length of the input strin g. SPACES n Specifies the number spaces between this and the ne xt column. L LEFT Specifies text is to be aligned along the left edge of the column. R RIGHT Specifies text aligned along the right edge of the column C CENTRE Specifies justification in the center of the column .DELIMITER ' ' This can optionally be used to specify an alternati ve delimiter at which to Break the input. By default the text will be split at a white-space character such as space Which may be removed from the output text. If the d elimiter is specified as an empty string,The text will be split at the column edge whatever the content. The following are used to pass the name of a varia ble into PDMS as part of a stored Expression so that the value is taken when PDMS pro cesses the stored expression rather Than PML extracTing the value at the time the line is read:  VVALUE( ! X ) VTEXT(! AString ) VLOGICAL( ! Boolean) "}
{"Headers": "Accessing DB Elements As Objects", "Content": "Using PML in PDMS The following facilities are only applicable to PDM S. A special global variable!! CE has been provided w hich always refers to the current Element in the database.!! CE can be used to obtain the DB reference of the current Element:  ! Item = !! THIS  !! CE is of type DBREF so the new variable! Item wil l also be of type DBREF. The dot Notation can be used to access attributes and pseud o-attributes of a database element:! Bore = ! Item.bore  This form of access can also be used directly on th e !! CE variable:  ! Owner = !! CE.owner  It is also possible to follow references between DB elements using this mechanism:  ! Rating = !! CE.cref.pspec.rating  Assigning a new reference to the!! CE variable make s the new reference the current element By navigating to it in the database:  !! THIS =!! CE.owner  P-points are accessed using the P-point number like an array subscript. For example, to Access the direction of P-point[1]:  ! Dir = !! CE.Pdirection[1] $*! Dir is a DIRECTION ob ject  To access the position of P-point[3]:  ! Pos = !! CE.Pposition[3] $*! Pos is a POSITION obje ct  A NULREF is treated as UNSET, so a NULREF can be te sted for in two ways:  If (! MyDBRef EQ NULREF ) thenIf ( UNSET( ! MyDBRef ) ) then  There is also the function BADREF which will detect whether a database reference is unset Or invalid (i.e. impossible to navigate to):  If (BADREF(! MyDBRef ) ) then . . .  Note: Use full-length names for attributesAs listed in the Appendix for compatibility with Future releases. You can assign a new value to aDBREF attribute, en suring that the type of the new value Matches the type of the attribute  !! CE.Built = TRUE"}
{"Headers": "Accessing Information About a Session ", "Content": "You can still assign an attribute value in this way even if the PML DBREF is not the current Element':  ! A = !! THIS !! THIS =!! CE.Owner ! A.Built = TRUE  You can even assign a PML object, such as POSITION, where this corresponds to the typeOf the attribute:  Note that where the type of an attribute is a PML o bject, it is not possible to set an object Member value, such as the up value of a POSITION, d irectly - this must be done in two Internships:  ! Pos = !! CE.Position ! Pos.Up = 2000 !!CE.Position =! Pos A number of special commands have been provided to set a PML Variable with Information about the current session. The commands are:  Current Session, Sessions, Projects, Teams, Users, MDBs, DBs  These commands can be used as in the following exam ple.The SESSION object has a Method that returns name of the MDB in the current session. Hence:  ! C = current session ! CurrentMDB = ! C.MDB()  This will set! CurrentMDB to the name of the curren t MDB. Using the facilities described here you can createAn expression and have it evaluated for all Elements which satisfy particular selection criteri a. The results of the expression are then Placed in a named array. The command syntax is:  VAR! Array EVALUATE (Expression) FOR select COUNTVA R! Counter Where: ! Array is the name of the array that will be created to c ontain the results of (expression) for All the elements selected within select. (Expression) is the expression that will be carried out for all the elements that match the Select criteria.Select is the selection criteria (see above, and the rele vant Reference Manual for your Product for details of selection criteria) COUNTVAR is an optional command which allows you to record how often the expression is Calculated in Counter , whichIs increased by one e ach time the expression is evaluated.  You can append the results of such an evaluation to an existing array using the APPEND Keyword. For example: VAR! BOXES APPEND EVALUATE ( XLEN*YLEN ) FOR ALL BOXES will add the values calculationAted from the express ssion for all BOXES to the (already Existing) array BOXES. You can also overwrite eleme nts in the array by specifying the first Index in the array which you want to be overwritten . The specified index, and the indexes Following it,Will be overwritten by the results of the evaluation. For example:  "}
{"Headers": "RAW keyword When setting Variables with VAR", "Content": "VAR! BOXES[99] EVALUATE ( XLEN*YLEN ) FOR ALL BOXES  Will place the result of the first evaluation for t he selected elements at index 99, overwriting Any existing item,And the following results in the subsequent array elements. Programs that use the Forms and Menus interface (e .g. the DESIGN, DRAFT and ISODRAFT modules) strip out line feeds and compress consecutive spaces to a single Space before text strings are assigned to array var iables.If this is not the effect you want, You can suppress this automatic editing by includin g the RAW keyword into the variable- Setting command line for these programs. The syntax for setting array variable elements to Unedited text strings is  VAR! VarName RAW ...  Where ... represents any of the standard VAR syntax f or setting variables. The Undo and Redo functionality has been exposed t o PML so you can create your own Set of undoable events. There are several ways PDMS adds entries to the undo system: \u2022 Using the MARKDB / ENDMARKDB commands. The syntax is as follows: MARKDB 'Text' \u2022 where text is an optional description to be includ ed with the mark. This causes a mark To be made in the database and an entry made in the undo stack. You should makeYour database changes, and then use the command END MARKDB \u2022 By creating a PML undoable object and adding it to the undo stack. See the Software Customization Reference Manual for a fuller descript tion of this object. You should Create an undoable objeCt, set up the undo and redo execution strings, and then Call the method add() to mark the database and add the undoable to the undo Stack. Make your database changes, and then call th e method end Undoable(). \u2022 Automatically whenever a model element iS moved us ing graphical interaction Techniques in Model Editor. Additionally you may re gister to be informed whenever An undo or redo operation has taken place, using th e PML PostEvents object. See The Software Customization Reference Manual for a fUller description of this object.  After an undoable has been removed from the stack a nd its state recovered then the user Supplied method on the PostEvents object is called, and will be passed the description text That was associated with the undoable object."}
{"Headers": "Assignment ", "Content": "Copies and References Assignment using = , the assignMent operator, usua lly does what you would expect, but a Detailed explanation of how the different data type s are handled may be helpful. Assignment always makes a copy of the right-hand-s ide to replace what is on the left- Hand side. The following command copies!Y into! X:  ! X = ! Y  If, for example, ! Y is an array, this command will duplicate the entire array making a copy of Each of the array elements. The same is true if! Y is an OBJECT. The technical term for this Is deep copy. Following this copy! X[1] = 'New Value'Will change! X[1] but leave the original array! Y u nchanged. !! Form and!! Form.Gadget are both PML references. A fter the command:  ! X = !! Form.Gadget  ! X is now a new reference, but the gadget itself ha s not been copied. Both PML Variables Now refer to the same gadget.! X.val = 'New Value' !! Form.Gadget = 'New Value'  Will both have the same effect and will assign a ne w value original gadget. You can think of a Reference as another name for the same object or va riable. !! CE is a DB reference. Following the command:! X = !! THIS  ! X is now a new reference to the same DB element, b ut the element itself has not been Copied.  ! Value = ! X.Attribute  Will now return an attribute of the current element . When the current element changes, !! THIS Will point to a new DB element.In this example, ! X will not be changed but remains as a Reference to the previous current element. Because!! CE is special,  !! THIS =! X  Will navigate to a new current element provided! X is another DB reference. In this example The command would nAvigate to the previous current element.  Where! Y is an array or object: ! X = ! Y "}
{"Headers": "Function Arguments ", "Content": "will make a deep copy of! Y. However, if any of the array elements is a reference (e.g. to a Gadget or DB element), a copy is made of the reference, but not of the object it refers to. In Other words a deep copy stops copying when it reach ed a reference.A function argument is a PML reference to a value or object outside the function. In effect The argument is another name for the original PML V ariable. If we define a PML Function Such as the following:  Define function!! ChangeIt (! Argument is STRING)! Argument = 'New Value' $P! Argument $P!! Global Var Endfunction  Then invoke the function like this:  !! GlobalVar = 'Old Value' !! ChangeIt (!! GlobalVar)  The values printed for! Argument and!! GlobalVar wi ll both be 'NewValue'. Warning: Be veryCareful about changing function arguments. It is a powerful feature capable of causing Unexpected results. Passing a constant as a function argument, such as a STRING in quotes, means the Argument is read only and cannot be assigned a new value. So if we define a functionDefine function!! ChangeString( ! Argument is STRING ) ! Argument = 'New Value' Endfunction  The following will change the value of ! S:  ! S = 'Old Value' !! ChangeString ( ! S )  However, the following will result in a PML error m essage because the value passed to theFunction as an argument is a CONSTANT STRING value which cannot be modified.  !! ChangeString ( 'OldValue' ) $* WRONG A form or gadget value passed as a function argume nt is read only so cannot be Assigned a new value. If you wish to change the val ueOf a gadget passed as an argument, Pass the gadget itself as an argument, not its value:  Define function!! ChangeValue( ! Argument is GADGET) ! Argument.val = 'NewValue' Endfunction PDMS Database Attribute are read only, and so they cannot be given new values byAssigning to them.  "}
{"Headers": "Using Unicode Text", "Content": "will make a deep copy of !Y. However, if any of the  array elements is a reference (e.g. to a gadget or DB element), a copy is made of the refere nce, but not of the object it refers to. In other words a deep copy stops copying when it reach ed a reference. \n A function argument is a PML reference to a value or object outside the function. In effect the argument is another name for the original PML V ariable. If we define a PML Function such as the following: \n \ndefine function !!ChangeIt ( !Argument is STRING) \n  !Argument = 'New Value' \n  $P !Argument \n  $P !!Global Var \nEndfunction \n \nThen invoke the function like this: \n \n!!GlobalVar = \u2018Old Value\u2019 \n!!ChangeIt (!!GlobalVar) \n \nThe values printed for !Argument and !!GlobalVar wi ll both be 'NewValue'. Warning: Be very careful about changing function arguments. It is a powerful feature capable of causing unexpected results. \nPassing a constant as a function argument, such as a STRING in quotes, means the argument is read only and cannot be assigned a new value. So if we define a function \n \ndefine function !!ChangeString( !Argument is STRING ) \n  !Argument = 'New Value' \nEndfunction \n \nThe following will change the value of !S: \n \n!S = \u2018Old Value\u2019 \n!!ChangeString ( !S ) \n \nHowever, the following will result in a PML error m essage because the value passed to the function as an argument is a CONSTANT STRING value which cannot be modified. \n \n!!ChangeString ( 'OldValue' ) $* WRONG \n A form or gadget value passed as a function argume nt is read only so cannot be \nassigned a new value. If you wish to change the val ue of a gadget passed as an argument, \npass the gadget itself as an argument, not its valu e: \n \ndefine function !!ChangeValue( !Argument is GADGET)  \n  !Argument.val = 'NewValue' \nendfunction \n PDMS Database Attribute are read only, and so they  cannot be given new values by assigning to them. \n  "}
{"Headers": "File Transcoding Utility ", "Content": "\u2022 UTF32BE UTF32 big-endian \u2022 ISO \u2022 LATIN1 ISO8859-1 \u2022 LATIN2 ISO8859-2\u2022 LATIN5 ISO8859-5 Cyrillic \u2022 Windows code page \u2022 CP932 Japanese shift-JIS \u2022 CP936 Simplified Chinese GBK \u2022 CP949 Korean \u2022 CP950 Traditional Chinese Big5 \u2022 CP1250 Central European \u2022 CP1251 Cyrillic \u2022 CP1252 LATIN1 + some extras (beware) \u2022 For backWards compatibility with legacy PDMS Proje cts \u2022 JAPANESE Japanese shift-JIS \u2022 CHINESE Simplified Chinese (EUC) \u2022 KOREAN Korean (EUC) \u2022 TCHINESE Traditional Chinese (used in Taiwan for e example) (EUC) PDMS provides a file transcoding utility transc.exE which users may find useful, particularly For moving files between PDMS12.1 and previous PDMS versions. Transc is a command line Application to transcode files from one encoding to another, and can also be used to add or Remove the BOM from existing UTF8 (or UTF16) files.The basic syntax is:  Transc -encoding> <input-file> -encoding> <output-f ile>  See Transc - text file transcoding utility.doc for more details. The major design decision for the Unicode conversi on of PDMS was to use (32bit) Unicode Scalar (US) iNstead of ASCII codes as it's integer character representation (holding Strings, with up to 4 bytes to represent 1 characte r. The section below describes a few Important properties of Unicode Scalars and the UTF 8 format.  Character. Unicode assumes tHat the 32 bit range wi ll cope uniquely with all the world's Character sets. Codes. To be able to clearly distinguish the number of cha racters held and the number of bytes Needed to represent them - as they cannot be assume d to be the same. Either direction.Search in either direction, and every first byte yi elds the number of bytes in the character. /, &, space, ~ etc.) then subsequent bytes of the c haracter are never ASCII bytes. So when You've found an ASCII byte it is a genuine characte r and not part of another character."}
{"Headers": "Diagnostic Messages From Within PML Files ", "Content": "PML Tracing If a PML File does not appear to be running in the way you expect the easiest thing to do Is to turn on PML Tracing with the command:  PML TRACE ON  With PML Tracing switched on, each of the PML lines executed is output to the parentWindow together with its line number. Additional tr acing messages tell you when you have Begun to process a new PML File and when it has fin ished. To turn off tracing type:  PML TRACE OFF  These commands can also be put into a PML File on a temporary basis.You can also turn PML tracing on by setting the Environment Variable PMLTRACE to ON before you start the Program. For more precise control of PML tracing yo u can use the $R command. $R100 is The equivalent of PML TRACE ON and $R0 is the same as PML TRACE OFF.Type the Command $HR for online help on how to use the $R command. It is often useful to output a line to the screen from within a running PML File to indicate That the execution of the program has reached a par ticular stage. Use the $P command: $P! Total is: $! Total and! Maximum is: $! Maximum  Note: The use of $ to convert the value of a variable to a STRING. The alpha-log is a file containing a record of all the commands processed together with Any text output and error messages. To startRecord ing use one of the following commands:  Alpha log /filename $* to open a new file Alpha log /filename OVERWRITE $* to replace an exis ting file Alpha log /filename APPEND $* to add to an existing file  To finish recording and close the file use:Alpha log END The alpha-log does not include standard PML tracin g from the command PML TRACE ON. For PML tracing to be included in the alpha-log , PML tracing should be directed to the Alpha-window. For example, to obtain standard PML t racing in the alpha-log use theCommand:  $R102  Refer to the online help given by $HR for other opt ions. If you cannot find out what is going wrong by mean s of PML trace output or writing out the Values of PML Variables, you may suspend a running PML File at a particular point byIncluding the command: "}
{"Headers": "Querying PML ", "Content": "$M You  Can then query the valuesOf any PML Variables of i nterest and even change the values of Some PML Variables. To resume processing of the sus pended PML File type into the Command line:  $M+  Use these facilities only for debugging and do not leave these commands in a finished PMLFile.  Note: These facilities do not apply to PML Functions or m ethods. A variety of queries are available to help diagnos e problems. Typically you might type These queries into the command line while a PML File is suspended. Alternatively you could Include any of these commands temporarily within a PML File. If you are interested in the name of the currently running PML File and the other PML Files from which the current file was invoked use t he command:  $QM The table below gives some usefuL commands for que rying PML Variables.  Command Effect Q var! LocalName Queries the value of a specific local variable, u se the command. Q var LOCAL Queries the values of all local variables. Q var!! GlobalName Queries the value of a specific global variable.Q var GLOBAL Queries the values of all global variables Q var! MyArray[1] Queries the value of a specific element of an arr ay. Q var! MyArray Queries the values of all elements of an array. Q var! MyArray.Size() Queries the number of elements currently in an ar ray.When you are typing commands into a macro or into a command line, you may not Remember exactly what arguments are available or wh at other commands are related. You Will find full details in the appropriate Reference Manuals to the module, but you can also askThe command processor what sort of command or comma nds it is expecting next by typing: $Q  This will produce a list of every valid command wor d or argument type that you may enter Next. The list may be long and could include every valid command for the module that youAre in. The $Q facility is also useful to establish what is allowed as the next component of a Command. Type the beginning of the command sequence followed by $Q.  "}
{"Headers": "Querying PML ", "Content": "$M You can then query the values of any PML Variables of i nterest and even change the values of some PML Variables. To resume processing of the sus pended PML File type into the command line: $M+ \n \nUse these facilities only for debugging and do not leave these commands in a finished PML File. \n \nNote: \nThese facilities do not apply to PML Functions or m ethods. \n A variety of queries are available to help diagnos e problems. Typically you might type these queries into the command line whilst a PML Fi le is suspended. Alternatively you could include any of these commands temporarily within a PML File. \n If you are interested in the name of the currently  running PML File and the other PML Files from which the current file was invoked use the command: $QM \n The table below gives some useful commands for que rying PML Variables. \n \nCommand   Effect  \nq var !LocalName   Queries the value of a specific local variable, u se the command. \nq var LOCAL   Queries the values of all local variables. \nq var !!GlobalName   Queries the value of a specific global variable. \nq var GLOBAL   Queries the values of all global variables \nq var !MyArray[1]   Queries the value of a specific element of an arr ay. \nq var !MyArray   Queries the values of all elements of an array. \nq var !MyArray.Size()   Queries the number of elements currently in an ar ray. \n When you are typing commands into a macro or into a command line, you may not remember exactly what arguments are available or wh at other commands are related. You will find full details in the appropriate Reference  Manuals to the module, but you can also ask \nthe command processor what sort of command or comma nds it is expecting next by typing: $Q \n \nThis will produce a list of every valid command wor d or argument type that you may enter next. The list may be long and could include every valid command for the module that you are in. The $Q facility is also useful to establish  what is allowed as the next component of a \ncommand. Type the beginning of the command sequence  followed by $Q. \n  "}
{"Headers": "Difference between PML 1 and PML2", "Content": "Upgrading from PML1 to PML2 \n\u2022 PML 1-First version of PML including loops, if sta tements, string handling , labels. \n\u2022 Is faster with simple single line definition and s ingle execution, \n\u2022 Returns array of strings of the references, \n\u2022 The scope can include volumetric limits (within \u2026) , \n\u2022 To obtain a value in PML 1 must be preceded with $ , var !value ($!number), \n\u2022 PML1 must be still used when an expression is used  as an argument to a command and must be enclosed in () brackets, \n\u2022 PML 1 macros are in PDMSUI folder, \n\u2022 PML 2-Object oriented language builds on PML 1 and  extends the facilities to be like other object based languages (VB, Smalltalk) \n\u2022 Is slower and initially more lines of code to set up the collection is necessary, \n\u2022 Returns array of database references and  \n\u2022 Collection can be used as the scope of a collectio n, \n\u2022 Can be used with the TABLE object, \n\u2022 Can\u2019t use volumes to limit the scope, \n\u2022 To obtain a value in PML 2 is used =, !value = !nu mber, \n\u2022 PML2 may be of any complexity, may contain PML fun ctions and methods and form gadget values, !value = !!MyFunction(!arg) * !!Form .Gadget.Val / !MyArray.Method(), \n\u2022 PML2 may consist operators and operands (+,-,*,/,G T,AND,OR,&,EQ\u2026), \n\u2022 PML 2 macros are in PMLLIB, \n\u2022 Variable Types - STRING, REAL, BOOLEAN and ARRAY, \n\u2022 Built in methods for commonly used actions, \n\u2022 User Defined Object Types, \n\u2022 PML Search PATH (%PMLLIB%), \n\u2022 Dynamic Loading of Forms, Functions and Objects, \n\u2022 New Aid objects for geometric modelling, \n\u2022 $Wn - Will Break the GUI Software \n\u2022 Numbered Variables - Are no longer available \n\u2022 Macros - Avoid Mixing with PML Functions \n\u2022 Global Variables for results - Use Function \u201cRetur n\u201d \n\u2022 $M- $M+ $MK - Only for debugging, not LIVE code \n\u2022 $R+ $R- - Withdrawn, (PML TRACE ON/OFF) \n\u2022 Synonyms - Not permitted in PML Functions but work s in macros, \n\u2022 VAR Syntax - Use \u201c=\u201c Where possible \n\u2022 VAR Name READ - Use ALERT object or Form \n\u2022 Expressions in () - Brackets not needed after \u201c=\u201c \n\u2022 !VALUE = NAME - Use !VALUE = !!CE \n\u2022 $ - Use variables without $ \n\u2022 Don\u2019t Quote variables - With no $, quotes not need ed \n\u2022 @ cursor functions - Use Event Driven Graphics \n\u2022 !ARRAY[-ve] - Not allowed in PML2 \n\u2022 !ARRAY[0] - Not advised to use at PML2 \n\u2022 Dots \u201c.\u201d In Names - New meaning at PML2 \n\u2022 Form EDIT  - syntax Use direct setting  "}
{"Headers": "Important difference between PML1 and PML2", "Content": "Important differences \nOnly Algebraic expressions are allowed, (No reverse -polish notations after \u201c=\u201c sign) \n \nCreating numeric variable with \u201c=\u201c creates a REAL \n \nSome PML1 macros using the \u201c=\u201c will now create vari ables of the wrong type. \n \nVAR !name value will now create a STRING value. \n \nDO variables are now REAL rather than STRING \n \nIf \u201c=\u201c has been used in existing PML code and probl ems are found, re-write the code using PML2 technology, or revert to PML1 VAR technology. \n \nConversion utility \u201ceq2var\u201d (Currently runs through  an \u201cawk\u201d script) \n \nDO variables in PML2 are automatically deleted to e nsure that they can be created, This can upset other variables if of the same name. \n \nOn exit DO variables remain REAL; previously they w ould have been STRING +1 if loop ran to completion. \n \nVariable in \u201cdo values\u201d is deleted on exit. \n \nDO from to are required to be REAL, Existing macros  are unaffected by this ($) \n \nChange variable names to avoid DO variables \n \nCheck DO expressions, re-write as necessary \n \nResults of an expression in IF must be TRUE or FALS E. \n \nAn error will occur where ZERO=FALSE \n \ne.g.                                     if ($value) then - - (PML1)  \nwill have to be either       if ($value EQ 1) then  \n                                  or if ( BOOLEAN($value)) then  \n \nMost common occurrence  \nPML1  if ( match ($!String1,$!String2)) then  \nPML2  if ( match ($!String1,$!String2) GT 0 ) then  \n \nCheck Form and Global Variable Names \n \nForms are now GLOBAL variables, and cannot have the  same names as a Global Variable. \n \nForm and Gadget Names Must be Unique and Start with  a Letter \n \nForms & Menus enforces the rule that gadget names m ust start with a letter, and must be \nunique, (Gadget names can be re-used in different f orms). \n \nNew Forms & Menus Error Messages. \n \nNo longer possible to use setup form from within .I NIT macro. "}
{"Headers": "Gadgets that are outside the form are now ERRORS", "Content": "Gadgets that are outside the form are now ERRORS. \n \nMore than one OK,CANCEL or HELP will generate an error. \n \nVar list & do list are restricted to LIST gadgets, for TEXTPANES & SELECTOR gadgets use var pane,selector & do selector \n \nDOT in variable, Form and Gadget Names Is now used as separator between a Form or Object name and the name of one of its members or f unctions. \n \n!Array.size() \nvar !String \u2018comment\u2019 \n!Old.Name = \u2018!String\u2019 \n \ncould now use: \n!Size = $!<Old.name>.length() \nor \n!Size = $!Old.name$N.length() \n \nNegative Array Subscript is now an Error. \nArray subscripts MUST now be positive or zero, Zero  is permitted but many of the array methods ignore the zero\u2019th element. Macros which ma ke use of negative array subscripts will need to be revised. \n \n$MKn & $MK-n Withdrawn. \n \nThese commands may have had a role when macros were  run directly from a terminal, but are incompatible with form-driven software. \n \nMacros will have to be re-written. \n \nSynonyms are NOT Available in PML Functions but are  still available in Macros. \n \n= in PDMS10 is not compatible with = in PDMS11 \n \nComponents in Function to the Right of \u201c=\u201c \n \nExisting \u201cvar\u201d code is not affected. \n \nAdd brackets if PML1 code has none. \n \nTo convert to \u201ctext\u201d add \u201c$\u201d \n \n!X = 32 , !Y = 52 \n!Z = !X + !Y Result = REAL  \u2026..84 \n!Z = \u2018$!X\u2019 + \u2018$!Y\u2019 Result = STRING  \u2026..3252 \n \n  "}
{"Headers": "Overview ", "Content": "PML Form concepts \n The AVEVA software module which provides the abili ty for users to customize the PDMS graphical user interface using the PML is referred to as PML Forms & Menus (or just F&M). \nThe default \u2018system font\u2019 used by Forms and Menus t o display character data is Arial Unicode MS which contains a large number of the wor ld\u2019s alphabets. Internally F&M uses full Unicode, but can only display the characters access ible in its current \u2018system font\u2019. You will \nbe able to copy and paste Unicode characters from a nd to textual fields of F&M gadgets. \n \n In PML 2, forms are a type of object represented b y a global variable \u2014 the form\u2019s name, for example !!EntryForm . This means that a form cannot have the same name as any other object type, global variable, or any other form. Th e form object owns a set of predefined \nmember variables and built-in methods. In addition,  you can define your own members \u2014 form variables and form gadgets \u2014 and your own form  methods. All these will determine the content and functionality of the form. Gadget objec ts are user-defined members of the form object. Form members are always accessed using the dot notation, for example !!EntryForm.TextField \n \nGadgets own a set of predefined member variables an d built-in methods which determine the content and functionality of the gadget. For ex ample, the value of a text field gadget is accessed by: !!EntryForm.TextField.val.  \n \nNote that gadgets do not support user-defined membe r variables or user-defined gadget methods. \n \nCallbacks  are user-defined actions assigned to a form and it s gadgets and that are executed when the operator interacts with the form,  for example, by clicking a mouse button on a gadget. The callbacks are supplied as text str ings and may be any valid PML \nexpression, PML Function or method call, including any form, gadget or user defined object method. Effectively, these callbacks determine the intelligence of the form. \n The following are examples of the format of form a nd member names: \n \n!!EntryForm  The name of a form \n!!EntryForm .GadgetName The name of a gadget on a form \n!!EntryForm .GadgetName.val The data value held by that gadget \n \nNote: \nThat total length of the name is limited to 1024 ch aracters even though the length each individual components is limited to 64 characters. Within the form definition, the members of the form should be referred to by using !This to re place the form name part of the gadget \nname. For example: \n \n!This.GadgetName \n!This.GadgetName.val \n \nNote: The obsolete convention of using an underscore to r eplace the form name has been retained for compatibility with earlier versions.   "}
{"Headers": "Adding a Gadget Callback ", "Content": "Simple Form \n You define a form using a command sequence that st arts with: \n \nsetup form !!formname \n \nand ending with: \n \nexit \n \n Between these two commands come a number of option al subcommands which define the gadgets on the form. The following example defi nes a small form, containing the text \u2018Hello  World\u2019, and a button labelled \u2018 Goodbye\u2019 , which removes the form when pressed: \n \nsetup form !!hello \n  paragraph .Message text 'Hello world' \n  button .bye 'Goodbye' OK \nexit \n \n- A simple form \n Some points to note about the above definition and  the form it creates are: \n \n\u2022 there are no user-defined methods on this form, an d so the setup form . . . exit sequence is the complete form definition; \n\u2022 the paragraph command adds a paragraph gadget to t he form (a paragraph gadget is just a piece of text displayed on the form). The na me of the gadget is Message, and the dot before the name indicates that the gadget i s a member of the form. The text itself is specified after the keyword TEXT. \n\u2022 the button subcommand adds a button gadget named . bye. The text on the button will be \u2018Goodbye\u2019. The keyword OK is a form control attr ibute that specifies that the action of this button is to remove the form from th e screen. \n \nTo display the form in this example, you can use th e command: show !!Hello \n To perform intelligent actions a form or gadget mu st invoke a callback.We will now add a simple gadget callback to the hello form. We will a dd a second button, change message, which will execute a callback to modify the Message  paragraph gadget. \n \nsetup form !!hello \n  paragraph .Message text 'Hello world' \n  button .change \u2018Change message\u2019 callback |!this.m essage.val = \u2018Modified\u2019| \n  button .bye 'Goodbye' OK \nexit \n"}
{"Headers": "Form Definition File ", "Content": "A gadget callback is defined by the callback comma nd followed by a command or PML Function enclosed in text delimiters. As we are giv ing a text string as part of the command which is itself supplied as a text string, we have had to use two kinds of delimiter: the \napostrophe, (\u2018) and the (|) vertical bar. \n \nNote: The use of this to mean the current form. When the callback is executed, \n \n!this.message.val = \u2018Modified\u2019 \n \nwill set the value member of the gadget Message on this form to read Modified rather than Hello world. \n \nNote: The gadget callback could have been \n \n|!!OtherForm.Para.val = \u2018Modified\u2019| \n \nto change the value of a paragraph gadget on anothe r form named !!OtherForm. Typically a callback will involve many commands and could be a complex piece of code in its own right. \nIn practice, the recommended way of defining a comp licated callback is to use a form method. \n Form definitions must be held one per file. The fi le name must be the form\u2019s name in lowercase with the file extension .pmlfrm.  For example, our form !!Hello would be captured in a file called hello.pmlfrm. This definition file should be stored in a director y pointed to by \nthe PMLLIB  environment variable. It will then be loaded autom atically on execution of the show !!Hello  command. The form definition file contains: \n \n\u2022 The form definition between setup form and exit. T his includes the commands which create the form itself, and set its attributes, suc h as its size and title, the commands which create the gadgets on the form and specify ho w they are arranged, and the definitions of any variables which are to be member s of the form. \n\u2022 Any method definitions should follow the exit comm and, each method beginning with the define method command and ending with endmethod . Methods on forms are just like methods on any other kind of object. \n\u2022 In particular, it will contain the form's default constructor method. This is a method with the same name as the form, and no arguments. It is the only method called automatically when the form is loaded, and so it ca n be used, among other things, to set default values for the gadgets on the form. \n\u2022 The form may be given an initialization method, wh ich is run whenever the form is shown (as opposed to when it is loaded). \n\u2022 No executable statements should appear in the file  outside of the form definition or form methods. The effect of misplaced executable st atements is indeterminate. You can put comments anywhere in the file. \n A form definition must be loaded before the form c an be displayed. If you have stored the definition in a . pmlfrm  file then loading will be automatic when the form is displayed for the first time. Normally, a form is displayed as a resu lt of the operator making a menu selection \nor pressing a button on a form. This is achieved ei ther by using the Form Directive in the \nmenu or button definition (see next section) or by means of the command show !!formname  \nused in the gadget\u2019s callback. However, to display forms when you are developing them, you \nmay find it convenient to type the command: \nshow !!formname  "}
{"Headers": "PML Directives ", "Content": "Sometimes it is useful to force the loading of a f orm\u2019s definition file before the form is actually displayed, so that you can edit the form or gadget attributes from another form\u2019s callbacks before the form is actually displayed. Us ing the command loadform !!formname \n \nfrom a callback will force load the definition if t he form is unknown to PML, but do nothing if the form has already been loaded. Once a form has b een displayed you can remove it from the screen using the command \n \nhide !!formname \n \nNote that if you show it again it will appear on th e screen, but its definition is already known to PML and so it will not be loaded. It is possible  to remove a form definition from PML using the command kill !!formname \n \nThe form is then no longer known to PML until a new  definition is loaded. \n \nNote:  Earlier AppWare used form definitions in macro fil es which had to be loaded explicitly via $M path-name-to-file. This mechanism still oper ates for backwards compatibility, but is strongly discouraged when writing new AppWare. \n PML directives are commands used to control PML it self. For example, you use a PML directive to instruct PML to re-make its index when  you have added a new file. Some of these directives have been described in Storing and  Loading PML Files: the information is \nrepeated here, with additional directives for loadi ng forms. Note: Unlike the PML commands described in How Forms are Loaded and Displayed, PM L directives should not be included in callbacks, but are generally for command line us e. You will need to use PML directives \nwhen you are developing new form definitions or mod ifying existing ones. PML directives are commands of the form pml . . . The table below give s some useful PML directives. \n \nCommand Effect: \n \npml rehash  When you create a new PML Form while an AVEVA prod uct is running, you must link in the file storing the form by giving th is command. It causes PML to scan all the directories under the PMLLIB path, and to create a file pml.index, which contains a list of all \nthe .pmlfrm files in the directories. pml index  This command re-reads all the pml.index files in y our search path without rebuilding them. If other users have added PML File s and updated the appropriate pml.index files, you can access the new files by giving this command. \npml reload form !!formname  When you edit an existing form while an AVEVA prod uct is running, you must use this directive to reload the form definition file. \nkill !!formname  If you experience problems of an edited form defin ition not being re-loaded, you can use this directive followed by the pml relo ad directive. \npmlscan directory_name  This command runs a utility supplied with AVEVA pr oducts. \nWhen you are not running an AVEVA product, you can use this command to update the pml.index file in a given directory. \n  "}
{"Headers": "PML Directives ", "Content": "Revisiting our Simple Form \nOur simple form !!Hello , which we constructed earlier in this chapter, is not very intelligent. \nOnce we have pressed the Change button the .Message  paragraph will read \u2018Modified\u2019 for ever more, even if we hide the form and re-show it.  The extended version of form !!Hello below: \n \n\u2022 illustrates the use of the form definition file; \n\u2022 illustrates form methods as callbacks; \n\u2022 introduces some important predefined form members.  \n \nFirst save the definition in a file called hello.pm lfrm and ensure that its directory is in your PMLLIB search-path. \n \nsetup form !!hello \n  title \u2018Display Your Message\u2019 \n  paragraph .Message width 15 height 1 \n  text .capture \u2018Enter message\u2019 width 15 is STRING \n  button .bye 'Goodbye' OK \nexit \n \ndefine method .hello() \n  -- default constructor - set gadget load-time def ault \n  values \n  !this.message.val = \u2018Hello world\u2019 \n  !this.capture.callback = \u2018!this.message.val = !th is.capture.val\u2019 \n  !this.Okcall = \u2018!this.success()\u2019 \nEndmethod \n \ndefine method .success() \n  -- action when OK button is pressed \n  !this.message.val = \u2018Hello again\u2019 \n  !this.capture.val = \u2018\u2019 \nEndmethod \n \n \n- A Smarter Form \n \nIn the form definition: \n \n\u2022 title sets the form title member and hence display s a title; \n\u2022 para adds a PARAGRAPH gadget size 15 chars by 1 li ne with no content; \n\u2022 text adds a TEXT field gadget with tag \u2018Enter mess age\u2019, width 15 chars, to hold data of type STRING. \n \nThe constructor method .hello() does the following:  \n \n\u2022 initializes the paragraph\u2019s default value to \u2018Hell o world\u2019; \n\u2022 defines the callback on the text input field: to i nsert its value into the paragraph; \n\u2022 sets the form member Okcall (in the line beginning  !this.Okcall). This is a callback that gets executed when a button with control-type OK is  pressed. \n  \n"}
{"Headers": "PML Directives ", "Content": "The definition of method .success() does the following: \n \n\u2022 Sets the paragraph\u2019s value to \u2018Hello again\u2019. \n\u2022 Resets the text field\u2019s value to empty. \n \nNow load and show the form by typing: \n \nPML rehash \nshow !!Hello \n \n This will auto-load the form definition and execut e the default constructor method (which will set the message paragraph to \u2018Hello world\u2019 and  define the gadget and form callbacks). It will also display the form. Type your message into the Enter message field and press the \nEnter key. This will execute the field\u2019s callback, which will write your typed text into the message paragraph. Type a new message and press Ent er. The paragraph updates to reflect what you typed. Click the Goodbye button. T his executes the form\u2019s Okcall action \nwhich calls the success() method. The success() met hod sets the paragraph to \u2018Hello again\u2019 and blanks out the text field. Finally, the OK cont rol action hides the form. \n \nShow the form again and observe that the paragraph reads \u2018Hello again\u2019 and not \u2018Hello world\u2019. This demonstrates that when you re-show the  form the form\u2019s constructor is not run, because the form is already loaded. If you want to reset the form every time it is shown, you \nmust define a form initialization callback. \n  "}
{"Headers": "Callbacks: Expressions ", "Content": "Forms and Gadget callbacks \nA callback may be any valid expression, including a ny AVEVA product commands. For example, the following is a PDMS command: \u2018new box xlen 10 ylen 20 zlen 50\u2019 \n \nIt can also include PML general commands like \u2018$m %pathname%/MyMacro\u2019 \n \nto execute a given command macro, or \u2018q var !!form\u2019 \u2018q var !!form.gadget\u2019 \n \nwhich will write out details of the form or gadget and its members. You might like to try it on the form !!Hello.Typical expressions for a ca llback are \n \n\u2018!this.gadget.val = !MyObject.count\u2019 \n\u2018!MyObject.count = !this.gadget.val\u2019 \n \nwhich get or set the value of a gadget on the form from or to a user-defined object. \n Most callbacks require more than a single command,  so invoking a method or function (or macro) is an essential requirement. The advantage o f using form methods as callbacks is that this keeps the whole form definition in a sing le file. Forms defined in early versions of \nPML 2 used PML Functions as callbacks. This is stil l valid and is sometimes even essential as you may need to manage a group of forms; but mos tly the callbacks on a form are specific to that form. \n \nsetup form !!hello \n  title \u2018Display Your Message\u2019 \n  paragraph .Message width 15 height 1 \n  text .capture \u2018Enter message\u2019 width 15 is STRING \n  button .bye 'Goodbye' OK \nexit \n \ndefine method .hello() \n  !this.message.val = \u2018Hello world\u2019 \n  !this.capture.callback = \u2018!this.message.val = !th is.capture.val\u2019 \n  !this.Okcall = \u2018!this.success()\u2019 \nEndmethod \n \ndefine method .success() \n  !this.capture.val = \u2018\u2019 \nendmethod \n \n The .success() method above could only deliver a f ixed string \u2018Hello again\u2019 to the message PARAGRAPH gadget. The great advantage of me thods is that you can pass variables as arguments to the method, so it can be used more generally, for example as the callback to several gadgets. \n \ndefine method .success( !output is GADGET, !message  is STRING, !input is GADGET ) \n  output.val = !message \n  input.val = \u2018\u2019 \nendmethod "}
{"Headers": "PML Open Callbacks ", "Content": "We have added three arguments, an output gadget, an  input gadget and a message string variable. This has made the method very general. We  can still use it as the Okcall callback: \n \n!this.Okcall = |!this.success( !this.message, \u2018Hell o again\u2019,!this.capture )| \n \n When the OK button is pressed the Okcall action wi ll invoke the success() method, passing to it the message paragraph gadget as !outp ut, the message text \u2018Hello again\u2019 as !message and the text input field gadget capture as  !input. The method will do just what it did \nbefore. However, we could use it differently. We co uld add another button gadget, Restart, to the form: \n \nbutton .restore 'Restart' callback |!this.success( !this.message,\u2018Hello world\u2019, !this.capture )| \n \n When clicked, the Restart button\u2018s callback will e xecute and set the message paragraph gadget to read \u2018Hello world\u2019 and clear the capture text field, thus restoring the form to its state when it was displayed for the very first time . If we invoked the success() method as: \n \n!this.success( !this.capture, \u2018Hello world\u2019, !this. message ) \n \nit would set the value \u2018Hello world\u2019 into the captu re text input field and clear the contents of the message PARAGRAPH gadget. Not what you need her e perhaps, but you can see how versatile methods can be! \n \nNote:  The arguments to methods can be any valid PML obje ct types, built in or user defined. \nWhen the operator interacts with a GUI, an event oc curs. For example, when the operator: \n \n\u2022 types something into a field on a form; \n\u2022 moves the cursor into a window; \n\u2022 presses down a mouse button; \n\u2022 moves the mouse with button down; \n\u2022 let\u2019s the button up. \n \n The events are queued in a time-ordered queue. The  application software services this queue: it gets the next event, determines the objec t of the event (for example, form, gadget, menu) and the event type (for example, enter, leave , select, unselect, popup etc.), deduces \nappropriate actions and carries them out. When one event is completed, the software looks for the next event. \n There are a very large number of possible events, and most of them are very low level and have to be serviced very quickly to produce a u sable GUI. It would be inappropriate to allow the (interpreted) PML AppWare access to them all. However, the application software \ndefines a set of meta-events for forms and gadgets. When a meta-event occurs, the application software checks for user-defined callba cks and executes them. Hence callbacks are the AppWare\u2019s way of providing actions to be ca rried out at these meta-events. \n \n Callbacks provide a simple yet versatile mechanism  for the AppWare to create and manage the GUI. Sometimes there is more than one me ta-event associated with a gadget. In this case, the simple assigned callback is insuf ficient to fully exploit the gadget's possible \nbehaviors. To overcome this shortcoming we can use open callbacks to allow the AppWare "}
{"Headers": "Using a PML Function in an Open Callback ", "Content": "to be informed whenever a meta-event is encountered . Open callbacks can be used wherever callbacks can be used. They always involve  methods or PML Functions with a fixed argument list as follows: \n \ndefine method .Control( !object is FormsAndMenusObj ect, !action is STRING) \n \n\u2022 !object is a Forms and Menus object, for example, a form, gadget or menu. \n\u2022 !action is the meta-event that occurred on the obj ect and represents the action to be carried out by the method. \n \nThe open callback is a string of the form: \n'!this.MethodName(' \n \nNote:  The open bracket '(', no arguments and no closing b racket. The callback is to an open method or function. \n \nWe might assign an open callback to a multi-choice list gadget as follows: \n \nsetup form !!Open \n  title 'Test Open Callbacks' \n  list .choose callback '!this.control(' multi widt h 15 height 8 \nexit \ndefine method .open() \n  do !i from 1 to 10 \n    !fields[!i] = 'list field $!i' \n  enddo \n  !this.choose.dtext = !fields \nendmethod \ndefine method .Control( !object is GADGET, !action is STRING) \n  if ( !action eq 'SELECT' ) then \n   --find out all about our gadget object \n    !form = !object.owner() $*get object\u2019s owner \n    !type = !object.type() $*get object type \n    !name = !object.name() $*get object name \n    !field = !object.PickedField $*get picked field  number \n    !s = !object.DTEXT[!field] $*get DTEXT \n    -- do something with the data \n    $p selected $!form$n.$!name $!type field $!fiel d, D text{$!s} \n  elseif (!action eq 'UNSELECT' ) then \n    !n = !object.PickedField $*get picked field num ber \n     $p unselected field $!n $*do something with     data \n  endif \nendmethod \n \nNote  in the constructor method open() we have initializ ed the list so that field n will display list field n. DTEXT is a shorthand for display-text , that is the text displayed in the list field. \n\u2022 Control is the method which manages interaction wi th the list. Note the open callback \n\u2022 defined in list choose. \n\u2022 Note the use of $* for in-line comments \n\u2022 Note the use of the printing command $p to print i nformation to the system Request channel. $!form replaces the variable !form with it s current value as a string - this only works for PML simple in-built scalars types RE AL, STRING, BOOLEAN. $n in $!form$n.$!name is a separator needed to separate $ !form from the following \u2018.\u2019 which would otherwise be thought of as part of the variable name. When a list field is clicked, the list\u2019s callback will be examined an d if it is an open method or function, then the Forms and Menus software will supply the a rguments required to complete the function. "}
{"Headers": "Using a PML Function in an Open Callback ", "Content": "Thus in this case the actual callback string execut ed will be \n \n|!this.control( !!Open.choose, \u2018SELECT\u2019 )| \n \n Inside the control() method we branch on the value  of !action and access the data of !object (in this case our list). Finally we perform  our application\u2019s resultant action - in this case just printing out all we know about the operat or interaction using the $p command, \nwhich for a selection of an un-highlighted list fie ld will write: Selected OPEN.CHOOSE LIST field 5, Dtext{list field  5} \n \nNotice that the same method could be used to manage  several or even all gadgets on our form since the variable !object is a reference to a  gadget object and is supplied as !!Open.choose, the full name of the gadget includin g its form. This allows us to find \neverything about that object from its in-built meth ods, including its gadget type (LIST, TOGGLE, etc) and its owning form: \n \n!type = !object.type() \n!form = !object.owner() \nAll the examples so far have used form methods as o pen callbacks. The code would be essentially the same if we used PML Functions. The PML Function must be in a file of its own called control.pmlfnc. The body of the definiti on would be identical but must be \nbracketed by: \n \ndefine function !!Control( !object is GADGET, !acti on isSTRING) \nendfunction \n \nNote that the function has a global name !!control,  that is, it is not a member of any form or object and thus cannot use the !this variable The o pen callback on the choose list gadget would become list .choose callback '!!control(' multi width 15 h eight 8 \n \nThe rest of the story remains the same. \n Object  Object Callback \nLIST multichoice Gadget SELECT,UNSELECT,START,STOP \nLIST singlechoice Gadget SELECT, UNSELECT \nOPTION Gadget SELECT, UNSELECT \nALPHA VIEW Gadget SELECT \nBUTTON Gadget SELECT, UNSELECT \nTOGGLE and RTOGGLE Gadget SELECT, UNSELECT \nMENU (command fields) Menu SELECT, INIT \nMENU (toggle fields) Menu SELECT, UNSELECT, INIT \nFORM Form INIT, QUIT, CANCEL, OK,KILLING, FIRSTSHOW N \nTEXT Gadget SELECT, MODIFIED, VALIDATE \nSLIDER Gadget START, STOP, MOVE \nFRAME Gadget SELECT, UNSELECT,SHOWN, HIDDEN \nNUMERICINPUT Gadget SELECT, MODIFIED \nCOMBOBOX Gadget SELECT, UNSELECT, VALIDATE \n \n  "}
{"Headers": "Modules and Applications ", "Content": "Forms \n A PDMS GUI module consists of a set of co-operatin g applications running within the Application Window. Each module has:  \n\u2022 A Main form to present the default application and  to control access to the other applications. \n\u2022 One or more document forms usually displaying the application model. \n\u2022 Transient floating dialog forms that relate to spe cific tasks. \n\u2022 A small number of docking dialog forms to provide frequently required services. The Main form has a menu bar that provides access to al l the functionality of the current application of the module, from its pull-down menus  (the main menu system), and a set of toolbars, each containing gadgets (usually i con buttons, icon toggles and pull-down lists) designed to give fast access to frequen tly used functions. The Main form is not displayed directly, but supplies all its men us and toolbars to be displayed in the Application Window. \nThe form definition is a command sequence starting with: \n \nsetup form !!formname \n \nand ending with: \n \nexit \n \nThe sequence includes: \n \n\u2022 The commands which create the form itself and set its attributes, such as its minimum \nsize and title. \n\u2022 The commands which create the gadgets on the form,  and specify how they are \narranged. \n\u2022 The definitions of any variables which are to be m embers of the form. \nAll the form attributes are optional and have sensi ble defaults. Those which can only be set once must be specified on the setup form line. Thes e are: \n \n\u2022 Form type. \n\u2022 Layout mode. \n\u2022 Minimum size. \n\u2022 Resize. \n\u2022 Docking. \n\u2022 Form position. \n\u2022 NOQUIT \n\u2022 NOALIGN \n \nOther attributes are specified as sub-commands in t he setup form . . . exit sequence. They can be edited after the form has been created by me ans of the form\u2019s in-built members and methods. \n  "}
{"Headers": "Layout Modes ", "Content": "Form Type \n The appearance and behaviour of a form is determin ed by its Type attribute: \n \nMAIN  The form that will be swapped to as a Main form. T hese forms are not usually displayed directly, but serve to provide gadgets fo r the application\u2019s toolbar and menus for the application\u2019s main menus. \nDOCUMENT  Resizable form usually with a view gadget, but no menu bar. All document forms can be floated or un-floated using the right- mouse popup menu in the form\u2019s top border. When it is floating, you can drag the form away from the MDI frame and position it \nand resize it without constraint. This allows you t o drag the document form away to another screen of a multiscreen configuration. \nDIALOG  This is the default type the form will assume if y ou give no type when you set up the form. The default DIALOG form will be non-resiz able, floating, and non-docking. You can specify the DOCKING  attribute to allow the form to be docked within th e application frame. By default, a docking dialog is displayed floating, and you can i nteractively dock it. When a dialog is docked it will be resized to match the application frame edge to which it is docked, and so is resizable by default. The qualifiers LEFT, RIGHT, T OP, and BOTTOM, specify the edge of the application frame to which the dialog form will  be docked when first displayed. \nBLOCKING DIALOG  Normal form layout and content, but will block acc ess to all other forms while it is displayed. \n \nHere are some examples of ways you can set up forms  of different types: \n \nsetup form !!myform dialog dock left - Creates a re sizable docking dialog; \nsetup form !!myform dialog resizable - Creates a re sizable floating dialog; \nsetup form !!myform dialog - Creates a non-resizabl e floating dialog; \nsetup form !!myform - Creates a non-resizable float ing dialog; \nsetup form !!myform document - Creates a resizable MDI child document; \nsetup form !!myform document Float - Creates a floa ting resizable non-MDI document. \n Two layout modes are supported, namely VarChars an d FixChars. VarChars is a new layout mode, based on measuring precise string widt hs. It is better suited to the use of variably spaced fonts, and tends to produce smaller , more pleasing forms, without unwanted \nspace. The benefits of using VarChars are: \n \n\u2022 It tends to produce smaller, more pleasing forms, without unwanted space. \n\u2022 No text wrap-around, except possibly in conjunctio n with TagWidth. \n\u2022 No truncation of explicitly defined text except po ssibly in conjunction with TagWidth. \n \nThe recommended layout mode for all new forms is: \nsetup form !!formname . . . VarChars \n \n FixChars is the old layout mode (prior to PDMS12.1 ), which is based on the use of notional character width to calculate the approxima te sizes of textual gadgets and gadget tags. Because the calculated sizes are only approxi mate, the user has to make frequent use \nof the gadget's Width specifier and TagWidth specif ier and considerable trial and error to achieve a desired layout. \n The default layout mode for setup form is FixChars, because this will be th e least disruptive for existing user Appware, so FixChars m ode will currently result from either of \n \nsetup form !!formname . . . \nsetup form !!formname . . . FixChars "}
{"Headers": "Intelligent Resizable Forms ", "Content": "Minimum Size and Resizability \n A form will automatically stretch to fit the gadge ts you add to it. You can use the SIZE keyword to give a minimum size in multiples of the character width and line height . For example: \n \nsetup form !!New1 size 25.5 10 \n \n\u2022 Character width is the notional character width for the selected ch aracter font. \n\u2022 Line height is the height of the tallest single line gadget, th at is a TOGGLE , BUTTON , \n \nRADIO BUTTON, OPTION  gadget or single-line PARAGRAPH  for the selected character font. The RESIZABLE command means that the form wil l be displayed with re-sizing controls at its corners. This will allow the user to change the size of the form. Docking forms and all \ndocument forms are resizable by default; but for ot her types, if you do not include the RESIZABLE command, the size of the form is fixed. \n \nsetup form !!New1 RESIZABLE \nsetup form !!New2 size 25 10 RESIZABLE \n All gadgets except ALPHA and VIEW gadgets have DOCK and ANCHOR attributes that allow you to define gadgets that have intelligent p ositioning and resizing behaviour when their container gadget resizes. \n \n This allows you to have more than one resizable ga dget on a form and still have predictable and potentially complex resize behaviou r. However, the DOCK and ANCHOR attributes are mutually exclusive: setting the DOCK  attribute resets the ANCHOR to the \ndefault; setting the ANCHOR attribute resets DOCK t o none. \n \n ALPHA and VIEW gadgets do not support DOCK or ANCH OR attributes. They do, however, expand to fill their containers, so you ca n put them in a frame and set the frame\u2019s DOCK or ANCHOR attributes to get the behaviour you desire. \nCertain gadgets, known as the linear gadgets, have their centres auto-aligned approximately to aid simple layout without the user  having to know about PATH and ALIGN concepts. \n \n This pseudo-alignment gives sensible layout for si mple forms, but introduces small errors in all other circumstances and prevents accurate co ntrolled layout because the user doesn\u2019t know the offsets applied. The NOALIGN keyword allow s you to switch off this pseudo \nalignment. \n The gadgets BUTTON, TOGGLE, TEXT, OPTION, single l ine PARGRAPH fit within 1 vertical grid unit and are by default drawn with th eir Y-coordinate adjusted so that they would approximately centre-align with an adjacent BUTTON.  This pseudo-alignment introduces \nsmall errors in all but a few circumstances and pre vents accurate controlled layout. \nNOALIGN prevents this (historical) gadget auto-alig nment. Use NOALIGN in conjunction with PATH RIGHT (the default path) and HALIGN CENTR E, as it gives a better layout, with fewer surprises. \nNote:  It is bad practice to place one gadget on top of a nother. This may lead to gadgets being obscured. The commands to set modifiable attr ibutes are described after the syntax graph.  "}
{"Headers": "Form Title and Icon Title ", "Content": "Form Members \n The title sub-command is used to supply a string t hat is displayed in its banner at the top of the form's window. To set the title: title 'Quite a Long Title for a Form' \n \nYou can modify the title at any time using the Form Title member: !!MyForm.FormTitle = 'Modified Title' \n \nThe icontitle sub-command is used to supply a strin g that is used when a form is iconized. \nTo set the icon title: icontitle 'Short Title' \n \nYou can also modify the icon title at any time usin g the IconTitle member: \n \n!!MyForm.IconTitle = \u2018New Icon\u2019 \n The form\u2019s initialisation callback allows the form \u2019s gadgets to be initialised every time it is shown to reflect the current state of the applicati on and possibly to validate whether the form can be displayed in the current context. You can se t the callback by assigning to the form\u2019s initcall member. This can be done with the INITCALL  command: \n \nINITCALL \u2018!This.InitCallBack()\u2019 \n \nor directly by \n \n!!MyForm.initcall = \u2018This.InitCallBack()\u2019 \n \nNote:  The form initialisation callback must not attempt to display another form. You may invoke an ALERT object but not otherwise seek any i nput from the user. If the callback discovers an error so serious that the form cannot be displayed it can abort the display of the \nform by returning an error. You can supply the text  of an error message that is to be presented in an error alert in place of the form: \n \ndefine method .initcallback() \n  return error 1 'You do not have write access to t his \n  database' \nendmethod \n \nIf the initialisation callback has already caused a n alert to be raised then you can prevent the raising of a new error alert by using the NOALERT k eyword: \n \ndefine method .initcallback() \n  return error 1 NOALERT \nendmethod \nThe form supports the concepts of OK and CANCEL actions: \n \nThe OKCALL callback is executed when a form\u2019s OK bu tton is pressed or when the OK button of a form\u2019s ancestor has been pressed It all ows operators to approve the current gadget settings and carry out the function of the f orm. The form is then removed from the \nscreen. Typically this callback will gather all the  data from the form\u2019s gadgets and perform "}
{"Headers": "Quit/Close Callback ", "Content": "the form\u2019s major task. If you do anything of signif icance in callbacks on other gadgets you may have a hard time undoing everything if the user  presses the CANCEL button. You can assign to the form\u2019s OKCALL member using the comman d OKCALL \u2018CallbackString\u2019 . You \ncan modify the Okcallback at any time using !this.Okcall = \u2018CallbackString\u2019 . \n \nThe CANCELCALL callback is executed when a form\u2019s C ANCEL button is pressed, when the CANCEL button of a form\u2019s ancestor is pressed ( see section on Form Families) or when the window\u2019s CLOSE gadget is used. It allows the op erator not to proceed with the functions \nof the form. The form is then removed from the scre en and all gadgets are automatically reset to the values they had when the form was disp layed or when any APPLY button was last pressed. Typically this callback allows you, t he PML programmer, to undo any actions \nalready carried out on the form that ought to be un done in the light of the CANCEL request You can assign to the form\u2019s CANCELCALL member usin g the command CANCELCALL \u2018CallbackString\u2019 . \n \nYou can modify the CANCELcallback at any time using  \n \n!this.Cancelcall = \u2018CallbackString \n All Forms have a QUITCALL member that you can pass  a standard callback string. This is executed whenever the user presses the Quit/Clos e icon (X) on the title bar of forms and the main application window. If an open callback is  used then it is called with the FORM \nobject as its first parameter and \u2018QUIT\u2019 as its act ion string. QUITCALL for MAIN Forms For forms of type MAIN, the QUITCALL callback is execut ed, if present. This permits the user to terminate the application, and so the associated PM L callback should prompt the user for \nconfirmation. If the user confirms the quit, then t he callback should close down the application, and not return. If the user decides no t to quit, then the callback should return an error to indicate the decision to F&M. \n \n Use return error\u2026noalert if you want to avoid disp laying an error alert. If the form has no QUIT callback, then the QUIT event will be ignored.  The following example shows a (global) PML function, that you could be use from all forms of type MAIN: \n \ndefine function !!quitMain( ) \n  -- Sharable method Quit the application \n  !str = !!Alert.Confirm('Are you sure you want to quit the application?') \n  if( !str eq 'YES' ) then \n    -- execute application termination command, whi ch should not return \n    finish \n  else \n    return error 3 |user chose not to QUIT| noalert  \n  endif \nendfunction \n \nThis would be called from the form definition funct ion body or from its constructor method as shown below: \n \nSetup form !!myApplication MAIN \n  quitCall \u2018!!quitMain( )\u2019 \nexit \ndefine method .myApplication( ) \n-- Constructor \n  !this.quitCall = \u2018!!quitMain( )\u2019 \nendmethod \n "}
{"Headers": "FIRSTSHOWN callback ", "Content": "Essentially, if no QUIT callback is present, then t he form is cancelled (hidden with reset of gadget values). If a QUIT callback is provided then  you can prevent the default Cancel action by returning a PML error, but you must hide the form from your callback method (It is \nmore efficient the use \u2018!this.hide()\u2019, rather than \u2018hide !!myform\u2018 from your form methods). \n \nNote:  F&M does not display an alert for the returned err or, it is merely for communication. \nYou don\u2019t need a QUIT callback if you just want to allow the form to be hidden. For DOCUMENT forms (MDI children) only, the callback must not display an alert as this will cause some gadgets to malfunction afterwards. \nTypically assigned in the Constructor by \n \n!this.FirstShownCall = '!this.<form_method>' \n \n The purpose is to allow the user to carry out any form actions which can only be completed when the form is actually displayed. Ther e are a variety of circumstances where this arises and it is often difficult to find a rel iable solution. A couple of examples are given \nbelow. Commands which manipulate form, menu or gadg et visual properties, executed from a PML macro, function or callback may not happen un til control is returned to the window manager's event loop. For example, in the applicati on's start-up macro the command \nsequence show !!myForm \u2026 hide !!myform will result in the form not being displayed, but also not becoming known at all to the window manage r. Attempts to communicate with this form via the External callback mechanism (possibly from another process) will not work. \n \nThis can be rectified by doing the '!this.hide()' w ithin the FIRSTSHOWN callback, because the form will be guaranteed to be actually displaye d (and hence known to the window manager), before it is hidden It is sometimes diffi cult to achieve the correct gadget \nbackground colour setting the first time the form i s displayed. This can be resolved by setting the required colour in the FIRSTSHOWN callback. \nTypically assigned in the Constructor by \n \n!this.KillingCall = '!this.<form_method>' \n \nThe purpose is to notify the form that it is being destroyed and allow the assigned callback method to destroy any associated resources, e.g. gl obal PML objects which would otherwise not be destroyed. This may be necessary because PML  global objects will survive an \napplication module switch, but may not be valid in the new module. \n \nNotes: \nthe form or to the Form itself (e.g. don't show or hide the form). Attempts to edit the form or its gadgets may cause unwanted side effects or possible system errors. killing callbacks. \n It is often convenient to store additional informa tion on a form which will not be displayed to the user. This is achieved by defining form vari ables. These are variables which can be any of the PML data types, including ARRAYS and OBJ ECTS. These variables have the same lifetime as the form and are deleted when the form itself is killed. \n "}
{"Headers": "Querying Form Members ", "Content": "Form members are defined in just the same way as ob ject members: \n \nsetup form !!MyForm... \n  member .MyNumber is REAL \n  member .MyString is STRING \n  member .MyArray is ARRAY \nexit \n \nThe value of a form member can be set and used in j ust the same way as an object \nmember: \n \n!!MyForm.MyNumber = 42 \n!Text = !This.MyNumber \n!ThirdValue = !This.MyArray[3] \n \nIn a callback function you can use !this. to repres ent 'this form': \n \n!ThirdValue = !This.MyArray[3] \nYou can query the members of a form using the command: \n \nq var !!formname \n \nThis will list all the attributes of the form, and all the gadgets defined on it. This is a useful debugging aid. To query all the gadgets of a form ( excludes USERDATA gadget) use: \n \n!!gadgetsarray = !!MyForm.gadgets() \n \nReturns array of GADGET. \n Forms are displayed on the screen either as free-s tanding forms or as a member of a form family. A form can be displayed as a free stan ding form, for example by show !!form free. It then has no parent so it will not disappea r when the form which caused it to be \ndisplayed is hidden. \n \n When one form causes another form to be displayed,  such as when a button with the FORM keyword is pressed or a gadget callback execut es a show !!form command the result is a child form. A form can have many child forms ( and grand-children\u2026) but a child form \nhas only one parent - the form which caused the chi ld form to be displayed. The nest of related forms is called a Form Family. \n \n The Form Family exists just as long as the forms a re displayed. If a form is already on the screen when it is shown, it is brought to the front  of the display. If the child form is already in a Form Family it is transferred to the new parent. If the user presses the OK button of a \nparent form, the system in effect presses the OK bu ttons on each of the child forms, 'youngest' first, invoking their OKCALL callbacks. The parent form and all child-forms are hidden and the Form Family then ceases to exist. If  the user presses the CANCEL button or \nuses the window's CLOSE controls, the system in effect presses the CANCEL buttons of each of the child forms, 'youngest' first, invoking  their CANCELALL callbacks, and all the forms in the Form Family are hidden. The action of RESET and APPLY buttons does not affect family members. "}
{"Headers": "Position of Forms on the Screen ", "Content": "Loading and Showing Forms \n A form definition must be loaded before the form c an be displayed. If you have saved the definition in a .pmlfrm file then loading will be a utomatic when the form is displayed for the first time. Note: Earlier AppWare used form definit ions in macro files which had to be loaded explicitly via $m path-name. \n \nThis mechanism still operates for backwards compati bility, but is strongly discouraged when writing new AppWare. Normally, a form is displayed as a result of the operator making a menu selection or pressing a button on a form. This  is achieved either by using the Form \ndirective in the menu or button definition or by me ans of the command: \n \nshow !!formname \n \nused in the gadget\u2019s callback. In either case the f orm becomes a child of the menu\u2019s or gadget\u2019s owning form. A form may be displayed free- standing, i.e. not as a child, by: \n \nshow !!formname free \n \nSometimes it is useful to force the loading of a fo rm\u2019s definition file before the form is actually displayed, so that you can edit the form or gadget attributes from another form\u2019s callbacks before the form is actually displayed. Using the co mmand: \n \nloadform !!formname \n \nfrom a callback will force load the definition if t he form is unknown to PML, but do nothing if the form has already been loaded. If you are sure t hat a form\u2019s definition has been loaded hen you can show the form as a child or free-stand ing respectively using the form methods: \n \n!!formname.show( ) \n!!formname.show( \u2018free\u2019 ) \n \nbut note that this will not dynamically load the fo rm definition. \n Mostly forms are automatically positioned by the s ystem according to their type and the way they are shown. The origin of a form is its top  left hand corner. When a form is displayed as a child form then it is always positioned with r espect to its parent. For a form shown from a MENU, its origin is at the origin of the parent. If the form is displayed from a BUTTON or any other gadget, its origin is at the centre of th e gadget. When a form is shown as a free form for the first time then its default position i s at the top left-hand corner of the screen. We strongly recommend that you allow the system to pos ition forms whenever possible. \n \nYou can force the screen position of free-standing forms using the following commands or \nmethods: \n \nshow !!MyForm Free At xr 0.3 yr 0.5 \nshow !!MyForm Free Centred xr 0.5 yr 0.5 \n!!MyForm.show( 'At', 0.3, 0.5 ) \n!!MyForm.show( 'Cen', 0.5, 0.5 ) \n "}
{"Headers": "Hiding Forms ", "Content": "The At option puts the origin of the form at the specified position; alternatively the Cen option puts the centre of the form at the given position. The co-ordinate values are fractions of the screen width or height respectively and are referre d to as screen co-ordinates. For example : \n \nshow !!MyForm free At xr 0.25 yr 0.1 \n \npositions the origin of !!MyForm one quarter of the way across from the left edge of  the screen, and one tenth of the way down from the top.  \n \n!!MyForm.show( 'Cen', 0.5, 0.5 ) \n \ncentres !!MyForm at the middle of the screen.  \n The recommended way for a form to be removed from the screen is for the user to press a button with the OK or CANCEL attribute. Forms may  also be cancelled by using the window\u2019s close controls. Both these mechanisms will  remove the form and any of its children \nexecuting their OK or CANCEL \ncallbacks appropriately. \n \n Sometimes it is required to hide a form and other forms which are functionally associated but not part of the form family or as a result of a  button press on a form you may want to hide other associated forms but not the form whose butto n was pressed. The hide command or method allows this: \n \nhide !!MyForm \n!!MyForm.hide() \n \nNote: When you explicitly hide a form in this way i ts gadgets will be reset to their values at display or at the last APPLY, just like a CANCEL ac tion, but the CANCELCALL callbacks for the form and its nest will not be applied. This mea ns that before youexecute the hide you \nshould use any pertinent data  from the forms to be  hidden. You can destroy a loaded form definition using the command kill !!MyForm \n \nThe form is hidden and then its definition is destr oyed so that it is then no longer known to PML. You cannot then access the form or its gadgets , members or methods (including its .show() method. Normally you will not need to inclu de the kill command within your \nAppWare. If you re-show the form using the show com mand then the system will attempt to demand load the definition again. This is slow and expensive if you haven\u2019t modified the definition so avoid it: use loadform !!MyForm and ! !MyForm.show() instead. If you execute a \nsetup form !!MyForm... while the form !!MyForm alre ady exists then it is killed and a new definition is started. This mechanism may be useful  because it makes it possible to generate a form definition interactively from within your Ap pWare. This can be very powerful but \nshould be used with great care. \n You can stop forms from being hidden from the bord er close/quit pull-down menu by setting the NOQUIT attribute: \n \nSetup form !!MyForm . . . NOQUIT \n \nBy default, you can quit from any user-defined form , except for the current system Main \nform. \n  "}
{"Headers": "Menu Types and Rules ", "Content": "Menus \n Menus are always members of forms but can be emplo yed in various ways by the form and its gadgets. Menus come in two types: main menu s and popup menus. You determine what type a menu is when you create it. If you do n ot specify the type, then the system will \ntry to infer its type from the context of its first  use. \n \nFor example, if the first action in a form definiti on is to define the menubar, then the system will infer any menus referenced in the bar\u2026e xit sequence to be of type MAIN. Or, as a second example, if a menu is assigned as the popu p for the form or a gadget of the form, \nthen the system will infer the menu to be of type P OPUP. \n Forms may have a bar menu gadget or main menu, whi ch appears as a row of options across the top of the form. When you select one of the menu options, a pull-down menu is temporarily displayed. Fields on a menu may have pu ll-right arrows (>) that open a pulldown \nsub-menu when selected. Forms and gadgets can have popup menus assigned to them. \nWhen you move the cursor onto them and press the mo use popup button, the menu pops-up at the cursor and you can then select from the disp layed options. The following rules determine how you can use menus: \n \n\u2022 Each menu belongs either to the Main menu system or to the Popup menu system, but cannot belong to both . \n\u2022 A menu in the Main system can appear only once. i. e. it cannot be a sub-menu of several menus. \n\u2022 A menu in the Popup system may appear only once in a given popup tree, but may be used in any number of popup trees. \n\u2022 A menu cannot reference itself , either directly as a pullright of one of its own fields or be a pullright of another menu in its own menu tree . \n\u2022 Any pullright field of a menu references a sub-men u that will be inferred to be of the same type as the referencing menu. \n A bar menu is defined within a form definition. Th e menu bar is created with the bar subcommand. Note that its name is \u2018bar\u2019: there can be only one bar menu on a form. Then you can use the bar\u2019s Add() method to add the optio ns. For example: \n \nsetup form !!MyForm Dialog size 30 5 \nbar \n!this.bar.add ( 'Choose', 'Menu1') \n!this.bar.add ( 'Window', ' ' ) \n!this.bar.add ( 'Help', ' ' ) \nexit \n \nThis code specifies the text of three options label led Choose, Window, and Help. \n"}
{"Headers": "Defining a Menu Object ", "Content": "\u2022 The Choose option when picked will open Menu1 as a  pull-down \n\u2022 The Window and Help options will open the Window a nd Help system menus \n \nNote:  That Menu1 need not exist when the bar is defined,  it can be defined later in the form definition, but it must exist before the Choose opt ion is selected or an error alert will be raised. \n A menu is a set of menu fields, each representing an action that is invoked when the field is selected. The fields\u2019 display text indicates to the user what the actions are, and the fields\u2019 replacement text defines what the actions are. With in the form definition a menu object can \nbe created using the form\u2019s NewMenu method or the m enu sub-command. You can then use the menu\u2019s Add(), InsertAfter(), and InsertBefore()  methods to add or insert named menu fields. A menu field can do one of three things: \n \n\u2022 Execute a callback. \n\u2022 Display a form. \n\u2022 Display a sub-menu. \n \nYou can also add a visual separator between fields.  Below is an example of a complete menu definition: \n \n!menu = !this.newmenu( 'file', \u2018main\u2019 ) \n!menu.add( 'MENU', 'Send to', 'SendList', 'SendTo' ) \n!menu.add( 'SEPARATOR', 'saveGroup' ) \n!menu.add( 'CALLBACK', 'Save', '!this.SaveFile()', 'Save' ) \n!menu.add( 'FORM', 'Save as...', 'SaveFile', 'SaveA s' ) \n!menu.add( 'SEPARATOR' ) \n--core-code managed field for Explorer Addin, ticke d. \n--Note no Rtext needed \n!menu.add( 'CORETOGGLE', 'Explorer', '', 'Expl' ) \n!menu.add( 'MENU', 'Pull-right1', 'Pull1') \n--initialise toggle field as ticked (typically in t he \nconstructor) \n!menu.SetField( 'Expl', 'Selected', true ) \n \nThis creates a new main menu called Menu with six f ields and two separators between them. For example: \n \n\u2022 The SAVE field when picked will execute the callba ck command this.SaveFile(). \n\u2022 The Save as... field when picked will load and dis play the form !!SaveFile. By convention, the text on a menu field leading to a f orm ends with three dots, which you must include with the text displayed for the fi eld. \n\u2022 The SEPARATOR, usually a line, will appear after t he previous field. \n\u2022 The Pull-right1 field when picked will display the  sub-menu !this.Pull1 to its right. A \n\u2022 menu field leading to a sub-menu ends with a > sym bol: this is added automatically. \n\u2022 Named Menu Fields \n \nYou can add menu fields with an optional fieldname that you can later refer to when editing the menufield or modifying its attributes\u2019. If you do not specify a field name then you will not be able to refer to the field again. You can also a ssign a name to separator fields, which \nallows separator group editing. The general syntax is: \n \n!menu.Add( \u2018<FieldType>\u2019,\u2019 <Dtext>\u2019, \u2018<Rtext>\u2019, { \u2018 <FieldName>\u2019 } ) \n!menu.Add( \u2018SEPARATOR\u2019, { \u2018<FieldName>\u2019 })  "}
{"Headers": "Window Menu ", "Content": "Where the fields have the following meanings: \n \n<FieldType>  has allowable values: \u2018CALLBACK\u2019, \u2018TOGGLE\u2019, \u2018MENU\u2019 , and \u2018FORM\u2019. \n<Dtext>  is the display-text for the field (cannot be null or blank). May contain multi-byte characters. \n<Rtext>  is the replacement-text for the field. A null stri ng indicates no replacement-text. The allowable values for RTEXT for the different field types are: \n \n\u2022 CALLBACK\u2019 - callback string \n\u2022 TOGGLE\u2019 - callback string \n\u2022 MENU\u2019 - menu name string (without preceding \u2018.\u2019). \n\u2022 It cannot be blank. \n\u2022 FORM\u2019 - form name string (without preceding \u2018!!\u2019).  It \n\u2022 cannot be blank. \n \n<FieldName>  is an optional argument, which, if present, is the  unique field name within the menu. \nYou can add the system Window menu to a bar menu using: \n \n!this.bar.add (\u2018<Dtext>\u2019, \u2018window\u2019) \n \nThis menu is dynamically created on use with a list  of the titles of the windows currently displayed as its fields. Selecting a field will pop  that window to the front. This can be very useful on a cluttered screen. \nYou can add the system Help menu with the specified  display text to a bar menu using \n \n!this.bar.add (\u2018Dtext\u2019, \u2018Help') \n!this.bar.InsertAfter(\u2018window\u2019, \u2018<Dtext>\u2019, \u2018Help\u2019) \n \nWhen selected, this Help option displays a system-h elp pull-down menu that gives Access to the application help system. The fields are: \n \nContents  This displays the Help window so that you can find  the required topic from the hierarchical contents list. \nIndex  This displays the Help window with the Index tab s elected, so that you can browse for the topic you want to read about from the alphabeti cally-arranged list. You can locate topics quickly by typing in the first few letters of their  title. \nSearch  This displays the Help window with the Search tab at the front so that you can find all topics containing the keywords you specify. \nAbout  To see the product version information. \n \nYou can access On Window help by pressing the F1 ke y while the form has keyboard focus, or by including a Help button in the form\u2019s definition. \n \nNote:  By convention, the help menu should be the last on e defined for the menu bar, which will ensure that it appears at the right-hand end o f the menu bar. \n You can use any of your defined menus as popup men us for most interactive gadgets and for the form background as long as you have spe cified them as belonging to the popup menu system. When the cursor is moved over it with the popup mouse button pressed down, "}
{"Headers": "Finding Who Popped up a Menu ", "Content": "and then released, the menu will be displayed, and you can select from it in the normal way. \nA popup is added to a gadget or form using its Setp opup() method, with the popup menu as the argument to the method. Note that the menu pop1  must exist when the Setpopup() method is executed. For example: \n \nsetup form !!MyForm resizable \n  menu .pop1 popup \n  !this.pop1.add( 'MENU', 'Options', 'optionmenu' )  \n  !this.pop1.add( 'MENU', 'More', 'moremenu' ) \n  !this.pop1.add( 'MENU', 'Last', 'Lastmenu' \n  button .b1 ... \n  !this.b1.setpopup( !this.pop1 ) \nexit \n You can find out whether a menu was popped up from  a gadget, and if so, the gadget\u2019s name. The method is: \n \n!menu.popupGadget() is GADGET \n \nIf the menu was a popup on a gadget then the return ed GADGET variable is a reference to the gadget. If the menu was popped up from a pulldo wn-menu or from a popup on the form itself, the value is UNSET. Example: \n \n!g = !menu.popupGadget() \nif !g.set() then \n  !n = !g.name() \n  $p menu popped up by gadget $!n \nelse \n  !n = menu.owner().name() \n  $p menu popped up by form $!n \nendif \n A menu TOGGLE field is a menu field with a callbac k action and a tick-box to show that the field has been selected or unselected. By defau lt the field will be unselected so the box will not be ticked. When picked the fields callback  action will be executed and the tick-box \nticked. If you pick the field again the callback ac tion will again be executed and the tick removed. Note that the open callback is an obvious candidate for toggle menus as the SELECT or UNSELECT action is returned as the second  argument to the callback method. \nFor example, in your form definition you can add a toggle field as follows: \n \nsetup form !!Myform Dialog size 30 5 \n  !menu = !this.newmenu(\u2018Test\u2019, \u2018popup\u2019) \n  !menu.add( 'Toggle' ,\u2019Active/Inactive\u2019, '!this.to ggle(\u2018,'OnOff' ) \nExit \n \ndefine method .toggle( !menu IS MENU, !action IS ST RING ) \n  !name = !menu.fullname() \n  !field = !menu.PickedFieldName \n  $P menu $!name $!action field: $!field \nEndmethod \n \nNote: How we use the PickedFieldName member of the menu object to obtain the last picked field. If you pick this menu field the callb ack method will print: \n \nmenu !!MyForm.Menu1 SELECT field: OnOff  "}
{"Headers": "Inserting Menus into a Bar ", "Content": "Editing Bars and Menus \n The contents of menu bars and menus can be modifie d at any time using the members and methods of the bar menu gadget object and the menu object. \n You can insert new fields into a menu bar using th e InsertBefore() and InsertAfter() methods, which insert the new fields relative to ex isting named menus. The methods use named menus to determine the point where they shoul d insert the new menu. The general syntax is: \n \nInsertBefore(<TargetMenuName>, <Dtext>, <MenuName>)  \nInsertAfter(<TargetMenuName>, <Dtext>, <MenuName>) \n \nWhere the fields have the following meanings: \n \n<TargetMenuName>  is the name of the menu immediately before or afte r where you want the new menu to go. \n<Dtext>  is the display-text for the menu. \n<FieldName>  is the unique name for the menu within the bar. \n \nFor example: \n \nsetup form !!MyForm Dialog size 30 5 \n  bar \n  -- adds a pulldown for menu1 labelled with <dtext > \n  !this.bar.Add( \u2018<dtext>\u2019, \u2018menu1\u2019 ) \n  -- adds a window pulldown labelled with <dtext> \n  !this.bar.Add( \u2018<dtext>\u2019, \u2018Window\u2019 ) \n  -- adds a help pulldown labelled with <dtext> \n  !bar.InsertAfter( \u2018Window\u2019, \u2018<dtext>\u2019, \u2018Help\u2019 ) \nExit \n \n If you use the identifier \u2018Window\u2019 or \u2018Help\u2019 as th e name of the menu, the system will interpret them as system Window and Help menus, alt hough they will still be displayed with the string given in <dtext>. Named menus and the me thods that create them are discussed in more detail in the rest of this section. \nYou can insert new fields into a menu using the Ins ertBefore() and InsertAfter() methods, which insert the new fields relative to existing na med menu fields. The methods use named menu fields to determine the point where they shoul d insert the new field. The general \nsyntax is: \n \nInsertBefore(<TargetFieldName>,<FieldType>,<Dtext>, <Rtext >,{<FieldName>}) \nInsertBefore(\u2018SEPARATOR\u2019,{<FieldName>}) \nInsertAfter(<TargetFieldName>,<FieldType>,<Dtext>,< Rtext> ,{<FieldName>}) \nInsertAfter(\u2018SEPARATOR\u2019,{<FieldName>}) \n \nWhere the fields have the following meanings: \n \n<TargetFieldName>  is the name of the field immediately before or aft er where you want the \nnew field to go. \n<FieldType>  has allowable values: \u2018CALLBACK\u2019, \u2018TOGGLE\u2019, \u2018MENU\u2019 , and \u2018FORM\u2019. \n<Dtext>  is the display-text for the field (cannot be null or blank). May contain multi-byte characters. "}
{"Headers": "Changing the State of Menufields ", "Content": "<Rtext>  is the replacement-text for the field. A null stri ng indicates no replacement-text. The allowable values for RTEXT for the different field types are: \n \n\u2022 CALLBACK\u2019 - callback string \n\u2022 TOGGLE\u2019 - callback string \n\u2022 MENU\u2019 - menu name string (without preceding \u2018.\u2019). It cann ot be blank. \n\u2022 FORM\u2019 - form name string (without preceding \u2018!!\u2019). It can not be blank. \n \n<FieldName>  is an optional argument, which, if present, is the  unique field name within the menu. \n There are two methods you can use to set and read the status of menu- and menu-field properties. Setting Menu-Options\u2019 Status You can de -activate a menufield on a menu bar and a field in a menu with the SetFieldProperty() s o that it cannot be selected. Similarly, you \ncan make them invisible so the user cannot see them . You can also use SetFieldProperty() to hide a menu field and to select or unselect togg le-type fields. The general syntax is: \n \n!menu.SetFieldProperty (<FieldName>, <PropertyName> , Boolean) \n \nWhere the fields have the following meanings: \n \n<FieldName>  The name of the field you want to change. \n<PropertyName>  The name of the property you want to change in the  named field. The allowed values are: \n \n\u2022 ACTIVE\u2019 - greyed in or out \n\u2022 VISIBLE\u2019 - visible or invisible \n\u2022 SELECTED\u2019 - selected or unselected (toggle type fi elds, only. Specifically, this value cannot be used with bars). \n \nBoolean  The value, TRUE or FALSE, for the property. \n \nNote:  The property names may optionally be truncated to the first three characters \u2018ACT\u2019, \u2018VIS\u2019, and \u2018SEL\u2019. For example: \n \n!bar = !!MyForm.bar \n!menu = !!MyForm.Menu1 \n \nsets local variables !bar and !menu to be reference s to the bar gadget and Menu1 of form \n!!MyForm. \n \nThen \n \n!bar.SetFieldProperty( 'Foo', \u2018ACTive\u2019, false) \n \nwill grey-out the menufield on bar that has the fie ld-name \u201cFoo\u201d. And \n \n!menu.SetFieldProperty ( 'Bar', \u2018ACTive\u2019, true) \n \nwill activate the menufield on Menu1 that has the f ield-name \u201cBar\u201d. \n \nYou can use the same method to change the selected status of a toggle menu field. \n  "}
{"Headers": "Implied Menu-field Groups ", "Content": "Reading the Status of Menus and Menus\u2019 Fields \nTo read the status of a menu or of a menu-field pro perty, you can use the FieldProperty() method. The general syntax is: \n \nBoolean = !menu.FieldProperty (<FieldName>, <Proper tyName>) \n \nWhere the fields have the following meanings: \n \n<FieldName>  is the name of the field you want to change. \n<PropertyName>  is the name of the property you want to change in the named field. The \nallowed values are: \n \n\u2022 \u2018ACTIVE\u2019 - greyed in or out \n\u2022 VISIBLE\u2019 - visible or invisible \n\u2022 \u2018SELECTED\u2019 - selected or unselected (toggle type f ields, only. Specifically, this value \ncannot be used with bars) \n \nNote:  The property names may optionally be truncated to the first three characters \u2018ACT\u2019, \u2018VIS\u2019, and \u2018SEL\u2019. For example: \n \n!bar = !!MyForm.bar \n \nsets local variable !bar to be a reference to the b ar gadget of form !!MyForm. \n \nThen \n \n!isSet = !bar.FieldProperty( 'Foo', \u2018ACT\u2019) \n \nwill get the greyed-out status of the menufield on bar that has the field-name \u201cFoo\u201d. You can \nuse the same method to change the selected status o f a toggle menu field. \n A separator field and all following fields up to b ut not including the next separator field \nimplies a menu-field group. You can modify the ACTI VE and VISIBLE properties of all fields \nin the group, by reference to its separator name. F or example, for the menu: \n \n!menu = !this.newmenu( 'file', 'Main' ) \n!menu.add( 'MENU', 'Send to', 'SendList', 'SendTo' ) \n!menu.add( 'SEPARATOR', 'SaveGroup' ) \n!menu.add( 'CALLBACK', 'Save', '!this.SaveFile()',' Save' ) \nmenu.add( 'FORM', 'Save as...', 'SaveFile', 'SaveAs ' ) \n!menu.add( 'SEPARATOR', 'explGroup' ) \n!menu.add( 'FORM', 'Explorer...', 'ExplFile', 'Expl ' ) \n \n<FieldName>  is the name of the field you want to change. \n<PropertyName>  is the name of the property you want to change in the named field. The \nallowed values are: \n \n\u2022 ACTIVE\u2019 - greyed in or out \n\u2022 VISIBLE\u2019 - visible or invisible \n\u2022 SELECTED\u2019 - selected or unselected (toggle type fi elds, only. Specifically, this value cannot be used with bars) \n  "}
{"Headers": "Creating Menus Dynamically ", "Content": "Executing the method \n \n!menu.SetField( 'saveGroup', 'visible', false ) \n \nwill make the all the fields invisible for the grou p currently implied by the separator field \u2018SaveGroup\u2019, i.e. the fields SaveGroup, Save and SaveAs. \n \nThe combination of named SEPARATOR fields, insertio n and field group visibility will be useful for managing the sharing of menus between co -operating sub-applications. This facility should be used with great care. \n You can create new menus from within your appware dynamically using the form method NewMenu(). For example, you could equip your form w ith the methods popupCreate() and popupAction() which would allow you create and serv ice a popup menu from an array of \nstrings. Executing !this.popupCreate(\u2018NewPopup\u2019, !f ieldArray) will create a new popup menu and assign it to the form. \n \ndefine method .popupCreate( !name is STRING, !field s is ARRAY ) \n  --!fields is an array of field name strings \n  !menu = !this.newmenu( !name, \u2018popup\u2019 ) \n  --add all the fields with same open callback \n  do !n from 1 to !fields.size() \n    !menu.add( 'Callback', !fields[!n], '!this.menu Action(' ) \n  enddo \n  -- assign the new menu as the form\u2019s popup menu \n  !this.setpopup( !menu ) \nendmethod \n \ndefine method .popupAction( !menu is MENU, !action is STRING ) \n  -- General popup menu action routine \n  if ( !action eq \u2018SELECT\u2019 ) then \n    !name = !menu.fullname() \n    !field = !menu.pickedField \n    -- execute application actions according to the  field selected \n    $P selected field $!field of menu $!name \n  else \n    -- execute applications for unselected field (t oggle) \n  endif \nendmethod \n  "}
{"Headers": "System Font and Unicode characters ", "Content": "Form layout \nThe Form Layout section explains how to lay gadgets  out on a form. \n F&M supports a system font which provides the character representations used w ithin any forms, gadgets and menus which you define. This  system font has variable width characters (referred to as VarChars ), so different characters may have different widths. \nA notional character width for the font is also supported. This is a sort of a verage width (usually the width of upper-case X), and provides a  rough guide to the width of a text string as (number of characters X notional width). The rec ommended system font also supports \nmany of the World's character sets, so forms can be  designed to use non-English characters, and even to mix different languages on the same form. In order to achieve this PML and F&M now use the Unicode standard as their internal character format. \n Two layout modes are supported, namely VarChars an d FixChars. VarChars is a new layout mode, based on measuring precise string widt hs. It is better suited to the use of variably spaced fonts, and removes the need for mos t uses of the TagWidth specifier. The \nbenefits of using VarChars are: \n \n\u2022 It tends to produce smaller, more pleasing forms, without unwanted space. \n\u2022 No text wrap-around, except possibly in conjunctio n with TagWidth. \n\u2022 No truncation of explicitly defined text except po ssibly in conjunction with TagWidth. \n \nThe recommended layout mode for all new forms is: \n \nsetup form !!formname . . . VarChars \n \n FixChars is the old layout mode (prior to PDMS12.1 ), which is based on the use of notional character width to calculate the (approx.)  sizes of textual gadgets and gadget tags. \nBecause the calculated sizes are only approximate t he user has to make frequent use of the gadget's Width specifier and TagWidth specifier and  considerable trial and error to achieve a desired layout. The default layout mode for setup f orm is FixChars, because this will be the least disruptive for existing user Appware, so FixC hars mode will currently result from either of \n \nsetup form !!formname . . . \nsetup form !!formname . . . FixChars \n \nSee the FMSYS object method \n \n!!FMSYS.SetDefaultFormLayout(layout is STRING) \n \nthat allows users to change the default layout mode  for Setup form. This can be used to help est any existing appware which is using setup form  !!formname . . ., in either mode to determine which forms need layout adjustment. \n \nFuture Change to VarChars as Default Layout Mode \nThe intention is to change the recommended layout m ode to be VarChars at a subsequent \nPDMS release. It is probable that this will be achi eved by introducing the alternative, \noptional, form definition Syntax \nLayout form !!<form_name> . . . exit \nThis will ensure VarChars mode (and NoAlign) by def ault.  "}
{"Headers": "System Font and Unicode characters ", "Content": "Containers, Grid Co-ordinates and Gadget Boxes \n The Form and its Frame gadgets act as containers for holding gadgets. Typically gadgets are laid out in their containers from left to right and from top to bottom. Each container has a rectangular co-ordinate grid with origin (0, 0) at the top at the top left-hand corner. Each gadget has an origin at its top left-hand corner and a width and height , which together define a notional gadget box , which contains the gadget including its tag-text if defined. Layout involves positioning each gadget, b y its origin, at a specified position within the grid of its container and indicating its width and height. \n \n\u2022 The grid horizontal pitch is the notional characte r width for the system font. Because this font is variably spaced, n horizontal grid units do not equate to n characters. \nGenerally, it is more than n unless the string has a high proportion of wide characters e.g. capitals, numerals, w's, m's etc. I t is important that you understand this concept when you specify gadget sizes. \n\u2022 The grid vertical pitch is the line-height , which is the height of the tallest of the textual gadgets: TOGGLE, BUTTON, OPTION, TEXT or single-lin e PARAGRAPH. \n \nFor the Form container its extremities are referred to as XMIN form , YMIN form , XMAX form and YMAX form . \n \nThe extremities of a gadget box are referred to as XMIN.gadget , YMIN.gadget , XMAX.gadget an YMAX.gadget . \n \nWhen new gadgets are added to a container, the XMAX and YMAX extremities grow to include the gadget boxes.  \n"}
{"Headers": "System Font and Unicode characters ", "Content": "Positioning, Alignment and Size of Gadgets \n We strongly recommend that you lay out your form u sing auto-placement in combination with relative placement and use the NoAlign keyword. \n \nNote: This is vital because it allows gadgets to be added , removed, and repositioned, \nwithout having to adjust the geometry of all the ot her gadgets on the form. \n \nAuto-placement chooses a gadget's position coordinate automaticall y relative to the last placed gadget. \nRelative placement uses the AT syntax to specify a gadget's position c oordinate relative to a previously placed gadget. \nNoAlign switches off the default approximate centre-alignme nt of the gadgets TEXT, OPTION, COMBO, TOGGLE and single line PARAGRAPH for  path right and path left, which interferes with Auto-placement. \n \nA gadget's size component , width or height, is either a literal value, or a previous gadget's size component, or an extension to a previous gadge t's co-ordinate limit, i.e. min or max. \nThe last option, referred to as sizing to Positional Extent , uses the width to\u2026 and height to\u2026 syntax. This makes it much simpler to lay out compl ex and resizable forms. \n \nThe following example form demonstrates layout of a  simple, fixed size dialog form using the VarChars layout mode. Each gadget's position is set within t he gadget definition either, implicitly using auto-placement , or using the AT syntax. Gadget sizes are set implicitly, or \nrelative to the size of other gadgets or to the pos itional extents of other gadgets. \n \nNote:  No actual co-ordinate positions are required to sp ecify this form. It is mostly undesirable and unnecessary to specify a gadget's p osition as absolute grid coordinates, e.g. at x 12, y 5; we recommend defining the layout  of each gadget relative to a predecessor. \nThis allows simple editing of the layout, without h aving to calculate new positions. There are exceptions, for example, for the first gadget in a form or frame, where you may want to establish an initial x or y co-ordinate that is not  at the default position. \n \nHere is the corresponding PML code for the form: us ingVarChars.pmlfrm. The 'layout' keywords are emboldened and explained later in the chapter. "}
{"Headers": "Auto-placement ", "Content": "setup form !!usingVarChars dialog Varchars NoAlign \n  $*-- layout form !!usingVarChars dialog \n  title |Form !!usingVarChars| \n  path down \n  paragraph .para1 text 'Simple form layout using V arChars' \n  frame .frame1 |frame1: See my gadgets| \n    paragraph .para2 text 'text positioned implicit ly in frame1' \n    frame .frame2 |frame2: path right| \n      toggle .tog1 |BBC news 24| \n      path right \n      toggle .tog2 |BBC 1| \n      toggle .tog3 |BBC 2| \n      path down \n      vdist 0 \n      frame .frame3 |frame3: path down, vdist 0| at  xmin.frame2 width to max.frame2 \n        -- path down, vdist 0 gives minimum vertica l spacing \n        rtoggle .rad1 |ClassicFM| at xcen.frame3 - 0.5 * size \n        rtoggle .rad2 |Caroline| \n        rtoggle .rad3 |BBC Radio 2| \n      exit \n    exit \n  exit \n  button .cancel |CANCEL| at xmin form CANCEL \n  path right \n  button .ok |OK| at xmax form-size OK \nexit \n Auto-placement uses the PATH , DISTANCE and ALIGNMENT commands, which have the following meanings: \n \n\u2022 PATH The direction in which the next gadget origin will be placed relative to the previous gadget. \n\u2022 DISTANCE The distance increment between gadgets along the cu rrent path. \n\u2022 ALIGNMENT Specifies how the next gadget aligns to the previou s one for the current path. \nRelative placement means specifying the new gadget position by reference to the extremities of a previously defined gadget. It is a lso possible to position gadgets using explicit form coordinates, but this is rarely neces sary. \n The path along which gadgets are to be added, is s et using a PATH attribute: Usually PATH right or PATH up, occasionally PATH left or PA TH down. The default direction is PATH right. The current path direction is set until  you give a different PATH command. \n To specify the horizontal and vertical displacemen t between adjacent gadgets, use the \nHDISTANCE and VDISTANCE keywords, respectively. The  default displacements are \nHDIST 0.2 grid units, VDIST 1.0 grid units. Note th at these specify clearance distances \nbetween gadgets (for example, the distance between the XMAX of one gadget and the XMIN \nof the next), not the distance between gadget origins, thus:  "}
{"Headers": "CABLE TRAY APPLICATION Configuration of tools ", "Content": "The Choose Options dialog box allows the configuration of component choices, as well as connection rules when they are created. It is possible to define a default component specification.The selected specification will then be recommended automatically when creating Cable Tray, Branch and Components. "}
{"Headers": "CABLE TRAY APPLICATION Creation of cable path ", "Content": "CrCable Tray eation: Name of the cable path Specification Attributes Branch creation: Branch name Specification Attributes Attribute information window: Name Design Code Inspection Schedule Paint Schedule Tray Duty Material Reference FlUid Reference Case Reference Temperature Pressure etc... "}
{"Headers": "CABLE TRAY APPLICATION Connections of the ends of branches ", "Content": "When creating a branch, it is possible to configureRer the Head and Tail connection points of this one These connections are managed manually, because unlike Piping, cable trays cannot be connected to nozzles Once one of the connections is configured, the branch appears dotted between the Head and the TailIt is also possible to connect the Head and Tail of a branch to cable tray components "}
{"Headers": "CABLE TRAY APPLICATION Creation of components ", "Content": "Cable Tray Specicfication ChOix of Specifications Allows you to choose the specifications of the components to be created Creation/Re-selection mode of a component Choosing the type of elements to be created, Configuration of the direction of creation forward backward Position Modifications/position of a componentCreate Creating a component In the same way as in the Piping module it is possible to change the orientation and position of the components with the Model Editor Change Exit and Route Component allow the modification of inputs and outputs for multi-channel componentsThe Swap Branch function allows you to reverse multi-channel components The straight lengths of cable trays are automatically managed by AVEVA E3D In the majority of cases, the straight lengths are represented by a simple cylindrical volume representedFeeling the axis of the cable path The Fill With Straights and Remove Straights functions allow the automatic generation and deletion of straight sections whose maximum lengths are specified in the catalog Unlike cylindrical volumesBy default, whose length automatically adapts between 2 components, the sections are considered components in their own right and must be modified manually or regenerated "}
{"Headers": "CABLE TRAY APPLICATION Nomenclatures and Isometrics ", "Content": "Piping pipe Isometrics The nomenclature of a cable path can be generated by a deferral From the bar ribbon, in the Piping discipline it is possible to edit an isometry and the nomenclature of a cable tray"}
{"Headers": "HVAC DESIGNER APPLICATION  The basics ", "Content": "This module allows the creation of HVAC parts AVEVA E3D allows you to create ventilation elements according to the following hierarchy model: HVAC BRANCH HVAC Components BEND STRAIGHT TRANSFORMATION... NOTE: The HVAC module is close to the Piping module. An HVAC element must contain a branch, it then has at least 2 ends, which are the Head and Tail of the branch. However, if he hasOf several branches, it can have more than 2 ends. "}
{"Headers": "HVAC DESIGNER APPLICATION  Tool configurations ", "Content": "Create HVAC Create an HVAC System Element HVAC Main Branch Create a Main BRanch Element Choice of Specifications and name. Selection of the direction and dimensions of the Head Choice of the specification and thickness of heat insulation. Head Start: defined where the head will be positioned. NOTE: To define the dimensions of the HeAd, use the Picture icon... "}
{"Headers": "HVAC DESIGNER APPLICATION  Creation of components ", "Content": "Categories Choose the category of components you want See chapter 2 4 for more informationAvailable Types Choose the type of components available in this category See chapter 2 4 for more information Once the category and type of elements have been selected A dialog box appears Fill in the dimensions (Attention this boIte differs depending on the category and type of element chosen) "}
{"Headers": "HVAC DESIGNER APPLICATION  Library of available items ", "Content": "Here is the library of items available in the HVAC moduleHVAC rectangular HVAC Circular HVAC Shape Transformation HVAC Extra Equipment HVAC Nozzle Items HVAC Inline Plant Equipment HVAC Branch Connectors "}
{"Headers": "AVEVA E3D   Introduction ", "Content": "AVEVA E3D is a software that uses databases Indeed, work on AVEVA E3D does not use a so-called \"drawing\" file such as AutoCAD Microstation or SolidWorks To better understand, AVEVA E3D organizes the elements created in baIts of data that are prioritized in the following way PROJECT (ex: FTN) MDB Multiple Data Base (ex: FTN ALL) DB(Database) MODEL in writing DB(Database) CATALOGUE in read-only DB(Database) DRAW in writing NOTE: There is pOther types of DB (Database), the same database can be attached to several MDBs (Multiple Database), and can be read-only or write-only for the user. "}
{"Headers": "PRESENTATION OF AVEVA E3D   Starting the software ", "Content": "List and choice of project User name Password Choice of the MDB Stamp: Project backup choice Choice of E3D Model Draw Isodraft Spool Paragon module "}
{"Headers": "PRESENTATION OF AVEVA E3D  User Interface ", "Content": "Quick Access Toolbar Ribbon Model Explorer 3D graphic view view Properties "}
{"Headers": "AVEVA E3D THE HIERARCHY   Common hierarchy ", "Content": "Elements common to allAll the hierarchies (PIPES, STRUCTURES, EQUIPMENT,...) WORL Site Zone "}
{"Headers": "AVEVA E3D THE HIERARCHY  Specific hierarchy (examples) ", "Content": "Zone EQUI SUBE Primitives ( BOX, CYLI, NOZZ ) PIPE BRAN Piping Components(VALV,ELBO,...) STRU FRMW SBFR STRUCTURAL Elements "}
{"Headers": "AVEVA E3D THE INTERFACE Model Explorer ", "Content": "This dialog box allows you to view the elements of the database, and to position yourselfR also in this one The blue highlighted current element, corresponds to the active element It is called by the initials CE Current Element Drag and drop Drag and drop allows you to take an object from the Model Explorer and display it in the 3D view Right click menuAtttibutes display the attributes Rename rename the current element Delete delete the current item Add CE To Current Collection add to Active collection Add CE Members to Current Collection add members of the current item to the active collectionNew Explorer display a new explorer for this item Copy copy eg Ctrl C Paste paste eg Ctrl +V  Add display in the graphic view Add Only display the item without its group Add Connected show the connected elements Add Supports show mediaAdd Supported Element display supported elements Add Within Volume display the elements in the volume Add Laser Within Volume display the laser in the volume Remove undisplay Remove Only Remove the item without its group Remove linked media Remove linked mediaHightlight highlight Unhightlight remove the highlight  Command Window Add this: adds the object in the 3D view Rem ce: remove the object in the 3D view Rem all: remove all objects in the 3D view  NOTE: It is essential to know how toEp\u00e9rer in the database thanks to this browser. It allows you to position yourself well to create the elements. "}
{"Headers": "AVEVA E3D Using the mouse in a view ", "Content": "LEFT CLICK Selection of an itemMIDDLE BUTTON Mollette Front/Rear: Zoom IN / OUT Button: Refocus view RIGHT CLICK Power Wheel NOTE: The right-click menu is only accessible in the background of the view. "}
{"Headers": "AVEVA E3D Graphic view", "Content": "Automatic representation: Enable by default this option allows the automatic management of the representation of the elements (transparency, edges) at their display Temporary representation: Allows you to manage the representation of future elementsDisplayed, these colors are only temporary, the undisplay of an element resets its representation "}
{"Headers": "AVEVA E3D Setting the graphic view ", "Content": "View Setting: CuRrent View Allows the configuration of 3D window options. Projection adjustment of the view perspective Rotate adjustment of the rotation mode Effects Choice of visual effects (Disable Shadows to optimize performance) Tools Display of graphic orientation aidsBackground Choice of the background color of the view Capping Choice of the color of the cutting sections Lighting Brightness adjustment Anti-alias Enable or disable anti aliasing The level allows you to determine the fineness of the trace of a diagonal line PRead the level is higher, the more powerful the computer's processor must be Point cloud Enable or disable the display of a point cloud NOTE: The Background color allows you to change the background color of the 3D view, it is important to put it inWhite when printing screens. \"Graphics Drawlists\" Allows the configuration of the graphical representation of the elements in the 3D window. Tube representation of pipes Centreline representation of piping axes Holes Drawn representation of holes (negative)Flange Bolts representation of flange holes Tracing representation of tracing (pipes) Insulation representation of heat retardants (pipes) Hvac Tube Translucendy HVAC 3D Display Management Obstruction representation of the volumes of obstructionsArc Tolerance precision of the representation of the arcs Level :(see the Equipment Application manual) "}
{"Headers": "AVEVA E3D THE INTERFACE  Management of views ", "Content": "By default, only one graphic windowUe is active when the software is opened The items displayed in this window are listed in a drawlist collection It is possible to open several graphical windows, with drawlists that may be different Separate View CreatedEr an independent view with a drawlist different from that of the main view Cloned View Create a view identical to the main view but allowing a different orientation Local View Create a view whose drawlist content is the selection on the main viewNew Create an empty view with an independent drawlist Grid plane Create a grid "}
{"Headers": "AVEVA E3D THE INTERFACE Selection of elements in the graphic view ", "Content": "Navigate to The Navig functionAte To Element allows the choice of primitives in the General Discipline, it does not work with the Model Editor. This function allows the selection of only one element (CE). Multiple selection: A multiple selection can be made with theA Ctrl key or by a selection rectangle with a left click The CE is not necessarily included in the selected elements Selection with left click It allows you to choose two selection options depending on the direction in which you create your selection rectangleSelection of the elements included entirely in the rectangle. Selection of all objects passing through the rectangle. "}
{"Headers": "AVEVA E3D Keyboard shortcuts ", "Content": "F1 Help F2 Left windowF3 Object snaping F4 Project Snap onto LCS F5 Walk mode F6 Fly mode F7 Show grid F8 Orthogonal lock F9 Grid snap F10 Polar tracking F11 Wired mode F12 Dynamic hints "}
{"Headers": "AVEVA E3D Quick Access Toolbar ", "Content": "Savework backup Getwork: recovery of the latest bases Undo / Redo: Cancel / Redo eq Ctrl + Z / Ctrl + Y) Discipline: Choice of discipline and associated tools NOTE: To add launch iconsNt quick function in the Quick Access Toolbar, just right-click on the tool to add and select Add to Quick Access Toolbar. "}
{"Headers": "AVEVA E3D Tooltip", "Content": "When hovering the mouse over the elements of the graphic view, it is possible to display a table of information relating to the element by pressing \"shift\" "}
{"Headers": "AVEVA E3D Positioning of windows ", "Content": "When moving a window on the edges of the screen a location appears on the edges of the screen, to lock this position just let go of the left click "}
{"Headers": "AVEVA E3D Rules and conventions ", "Content": "AVEVA E3D is a CAD software, based on a database The user acts on this database and E 3 D makes it a graphic interpretationThis implies a few simple rules 1 Each element is identified in the database thanks to a n called the Refno reference number 2 Each Name name given to an element must be unique 3 In the same hierarchy, the name of the parent owner is transmitted toThe child member Ex Equipment /EQUI 01 Under equipment /EQUI 01 /CHASSIS 4 All names begin with \" / \" (not visible in the Model Explorer) 5 \" / \" is used as the default separator (of a parent/child hierarchy) 6 The current element CE isUnique, there can only be one element chosen in the explorer 7 AVEVA E3D uses a graphical interface that allows the selection of several elements These elements then become a graphic selection neg \u00c0 CE 8 A graphic group is a setWhich can be displayed or undisplayed independently The most common are the following EQUI Equipment Under Equipment SUBE Branch BRAN 9 The creation of SITES and generally ZONES are managed by the administrator "}
{"Headers": "AVEVA E3D DATABASES  Attributes ", "Content": "Home Attributes Each element of the database is determined by different attributes These attributes can be filled in directly by the user from the windowBe attribute, or through the creation and modification tools For example, a cylinder is determined by a Diameter attribute and a Height attribute Track CE Allows an automatic update of attributes on the CE It is possible to activateFilters on the attributes to facilitate reading in the Attributes window NOTE: The Q ATT command allows the display of the attributes of the current element in the command window Right-click menu in the dialog box Navigate To Navigate toThe target of the link that becomes CE Set Attribute Value to CE Fills the attribute by the name of the CE WRT Element Choice of repository Display P-Points Display of P-Points attributes (Primitive) Track CE Automatic window update Categorised/Alphabetical Sort attributes by category and alphabetical order Expand / Collapse Nodes Display of node attributes Modify / Category Filters Modify the display filters Manage Category Filters Management of filters by item Display standardD Attributes Displaying the main attributes Display UDAs Display of UDA (User Defined Attribtuts) attributes Display Pseudo attributes Display of pseudo attributes Columns Display of Columns Description and Data Type Settings Display of undefined attribute valuesExport to Excel Export attributes to Excel Print Preview Visualization before printing NOTE: UDAs are attributes created by the administrator. Some features are not usable with the Track CE function. "}
{"Headers": "AVEVA E3D DATABASES  Claimlist ", "Content": "MANAGE So that an element of the database is not modified by 2 users at the same time, each user has his own Claimlist The Claimlist regrUpe all the elements whose write access is reserved for the user It updates automatically according to the elements created or modified by the user In the event that an item cannot be added to the user's claimlistEur, this one will appear highlighted in red during its selection "}
{"Headers": "AVEVA E3D GENERAL APPLICATION  Rotation ", "Content": "HOME Rotate The Rotate option allows you to rotate according to any point First of all, simply choose your rotation point and then enter the desired rotation, the left click validates the rotation The Advanced option allows you to make more precise rotations than via the rotate option "}
{"Headers": "AVEVA E3D GENERAL APPLICATION  Orientation ", "Content": "HOME Rotate Each elementT E3D is oriented, i.e. it has a definition of its axes. These axes are defined as follows Y is N = Y axis in the North direction Z is U = Z axis in the Up direction This results in the third axis, which is rarely filled in X is EModification The modification of the orientation of these axes is not recommended. The use of rotation tools is preferable, or the use of the Model Editor Ex: If a ZONE has an orientation Y is E and Z is U, then any element created under this ZONE will be oriented Y is N and Z is U in relation to the ZONE and therefore Y is E and Z is U in relation to the World /* It is possible to retrieve the orientation attribute with the Q ORI command in the Command Line NOTE: Orientations Y is N and Z is U must beConsidered as a standard, and thus make it possible to preserve the compatibility of one element from one hierarchy to another. "}
{"Headers": "AVEVA E3D GENERAL APPLICATION  Investment tools ", "Content": "HOME Move or cGraphic order Type \"Move\" or \"M\" The Move option allows you to move according to any point First of all, simply choose your reference point and then enter the desired movement values, the left click validates the movement The Position optionDatum Selection of the reference point Designate Position allows you to define a reference position with the Positioning Control hooking tool Position Position of the chosen reference point in relation to the reference framework WRT referential The Posi Offset OptionTion By This tool can be associated with Positioning Control, which allows you to take a rib between 2 points to fill in the displacement values. NOTE: If your movement is only in 1 or 2 axis(s), lock the directions not concerned.The Advanced option Distance Allows the movement of an element in a direction at a specified distance, In relation to its current position or in relation to an identified element Through Allows the alignment of an element with an element identified in a specified planeClearance Allows the movement of an element until its obstruction volume is a game with an identified element Toward Allows the positioning of the element at a specified distance and direction of an identified element "}
{"Headers": "AVEVA E3D GENERAL APPLICATION  Graphic hook ", "Content": "The use of certain features requires a graphic selection The Positioning Control dialog box allows you to configure the type of hook on the elements of the graphic viewType of hook: Element: Origin of the element Ppoint: Key points of the elements Pliny: Edges of frame irons Graphics: Faces, Edges, vertices Aids Graphic help element Screen Point in the view (not recommended) Laser data: Laser reading pointsAny: Element, Ppoint or Pliny Hang-up mode: Snap: Particular point of the element Distance: Distance from a particular point of the element Midpoint: Middle of the element Explicit Position: Point coordinates Intersection: Intersection between 2 elementsCursor: Point clicked on the element Working Plane: Activates a work plane where the positions of the hanging points are projected. "}
{"Headers": "AVEVA E3D  Measure ", "Content": "HOME Measure One myUre is made between 2 points identified by the user in the graphic view The selection of points is made thanks to the \"Object snaps\" object hooks option By default the measurement is broken down into 3 axial dimensions (East North and Up) The resultsAre displayed in at the mouse pointer level and in the graphic view Activation of the poster on 3 axes After selecting the points and clicking on the arrow at the bottom of your keyboard, it is possible to activate the \"Distance axes\" option as below"}
{"Headers": "AVEVA E3D Copy an item ", "Content": "Copy Offset This tool allows single or multiple copying of an element or more elements Element to copy Location of the copy Move RepositoryThe Object menu allows you to choose the item or elements to copy CE copy of the current element Collection copy of the elements of a collection Pick copy of a group of elements selected on the screen 1 by 1 The To menu allows you to choose the destination hierarchyTion of the copy CE copy in a specific hierarchy (place on the destination hierarchy and select CE in this menu) Rel Copy in the same hierarchy (following) Copy rotate This tool allows the single or multiple copying of an element orSeveral elements Item to be copied Location of the copy Number of copies Rotation angle Displacement Direction of the rotation axis Position of the rotation axis Repository The Offset menu allows you to define a movement vector between 2 elements (defined by 2 points on the screen)The Cursor menu allows you to place the axis of rotation on a point, an element, ... designated on the screen The Intersection menu allows you to place the axis of rotation at the intersection between 2 elements, points... These options can also redefine the direction of the axis of rotation.It should then be locked NOTE: This tool allows the rotation and movement of an element, it is advisable not to use the 2 options simultaneously when making multiple copies Copy Mirror Element to copy Location of the copy NumberCopying Angle of rotation Displacement Direction of the axis of rotation Position of the axis of rotation Repository The Cursor menu allows you to place the plane of symmetry on a point, an element, ... designated on the screen The Intersection menu allows you to place the planOf symmetry at the intersection between 2 elements, points... NOTE: Copies created with the Copy > Offset, Copy > Rotate and Copy > Mirror tools lose all information about the names of the elements. Copy rename (Name conversion) AVEVA E3DAllows you to copy an element while keeping the structure of names within the same hierarchy This type of copy requires that the copied hierarchy be named conventionally The hierarchy must keep the name of the parent to the child Example TeamMent: /1PRO10 BB002 Under Equipment: /1PRO10 BB002 /NOZZLES Primitive: /1PRO10 BB002/ PEN001 Once this condition is met, there are 2 ways to create a so-called \"rename\" copy \u2022 From the Design Explorer Copy Paste from the context menu The coPie of 1 PRO 10 BB 002 is renamed /Copy of 1 PRO 10 BB 002 \u2022 From the Window command Type the following command NEW EQUI /TEC PMP 02 COPY /TEC PMP 01 RENAME /TEC PMP 01 /TEC PMP 02 NOTE: The BY E 2500 command can be added afterwards to moveThe copy of 2500mm to the East at the same time "}
{"Headers": "AVEVA E3D Modification of the hierarchy ", "Content": "Hierarchy Include Destination Hierarchy Element(s) present in the hierarchyIe of destination Insertion position Navigator (eq. DesignNavigator) CE Include the current element (in the destination hierarchy CE Members Include all elements of the current element ( in the destination hierarchy Identified IncludeElements selected on the Pick screen in the destination hierarchy NOTE: The destination hierarchy must be similar to the original hierarchy Reverse hierarchy The reverse hierarchy function allows you to reverse the order of the elements of the parent or dU owner This option is very used to reverse the head and tail of a branch Hierarchy Reorder Original hierarchy Insertion position Desired hierarchy Blocking the Modify Lock hierarchy allows you to block elements so that it is not pPossible to move them in the hierarchy As well as their members Evaluate the rules This function allows you to evaluate whether the rules are respected thanks to the attributes of the elements Break the link with the Template This function allows you to remove an elementOf the Template to which it is attached "}
{"Headers": "AVEVA E3D Modify by macros ", "Content": "Inter DB Macros allows you to activate macros to modify elements in the model or in the hierarchy"}
{"Headers": "AVEVA E3D Clipping Box ", "Content": "VIEW Add Within A Clipping Box allows you to see that the elements included within a defined volume, without being bothered by other elementsThis volume can be defined by From This the obstruction volume of the current element From Selected Element the obstruction volume of a selected element The Clip button allows you to display all the elements in the model or make them disappearTo see only the clipping box. The Cap button allows you to fill the cut elements The Modify button allows you to display the box in order to resize it To change the size of the clipping box simply use the model editor and then agrAndir or move the box as desired NOTE: Capping allows the filling of volumes cut by the Clipping Box"}
{"Headers": "AVEVA E3D SEARCH TOOLS   Search ", "Content": "The Search tool allows the user to search for model elements in the different types of DB and list the search results In a tableName Contains Search for elements whose name contains a specific string Element Type Type of items to search for Search Within Allows you to define the search field The results are stored in a Search Results collection He isIt is possible to add additional criteria to refine the search Attribute Filter Added criteria on the attributes of the elements Free Filter Adding criteria per PML order Search Scope Adding a position criterion Manage Searches PerPuts to save the search Template "}
{"Headers": "AVEVA E3D Collection ", "Content": "The Collection tool allows the user to create lists of items to query or modify themThere are 3 types of System Collections Shared Collections My Collection To be able to work on a collection or on these elements, it must be made active by a double left click The user The user can add elements toThe active collection from the context menu of the model explorer The elements of the collection can be modified directly from the command line or from the Copy, Move tools It is also possible to add columns of atTributes to the array of items On the top right-click, then click on Column Setup A window opens, then just click on Add Column and enter the attribute(s) you want The table obtained can be exported directlyIn Excel, printed or processed by a Quick Report To delete content from a collection, click on Clear Grid on the context menu. "}
{"Headers": "AVEVA E3D FOLLOW-UP AND VERIFICATION  Clasher ", "Content": "Display of ClashesHOME Clashes There are two solutions to use the Clash Auto Clash which is activated using the All collisions icon will be displayed as they take place when creating new objects Or you can control the collisiWe at the end of a routing of a piping for example In this case, the clasher opens from the icon NOTE: The levels of obstructions are taken into account in the calculation of the Clasher. It is therefore important to adjust them correctly Configuration of the clasherThe configuration of the Clasher is feasible with the tools available on the Options tab Touch Gap tangent tolerance Overlap overlap tolerance Clearance spacing tolerance Keys are included support for tangents are Ignored ignored tangentsClashes within Branch are included management of clashes in the same branch ignores adjacent management of clashes in the same branch, excluding previous and subsequent elements are ignored interferences in the same branch ignored Connections are Included pRise in charge of tangents with connections are Ignored ignored tangents With Spec are ignored ignored tangents if the specification of connections is identical to that of the controlled element Clashes Ignored Within Ignore the clashes between primitIves belonging to the same element Obstruction list The obstruction list defines all the elements of the special map with which collisions will be defined By default, the block list contains all the design elements of the MDBIt is possible to modify this list to generate an element collision list The exclusion list contains all the elements that should not be taken into account when calculating collisions By default, this list is empty From the L tabImitates a volume can be defined around one or more elements, or a region in order to create an obstruction space Any element that is partially or entirely in this space will be checked Visualization Click on Check CE to check the elementCurrent, or enter the name of the item to be checked before clicking on Check. By navigating the list of collisions, a visualization of the selected collision is generated in a graphic area similar to the design graphic view. LThe Navigate to Clash Item option allows you to access the colliding object. The Navigate to Obstruction option provides access to the obstructed object "}
{"Headers": "AVEVA E3 History of the model", "Content": "MANAGE History Comment Session At each Savework, a working session is opened by the user. The user has the opportunity to comment on his sessions in order to facilitate the understanding of the history of the elements. Comparison DateIt is possible to compare the state of an element of the model with its state on a defined date. The easiest way is to be able to use a stamp (revision) of the database. After choosing a comparison date and clicking OK, the userYou can question the elements of the model about their previous state with the keyword \"OLD\". NOTE: All attributes and a number of pseudo attributes can be used for comparisons. Model Changes The history of creations and moDifications of elements is kept by AVEVA E3D. The Model Changes tool allows visibility of this entire history or just that of a particular element. It is therefore possible to know which user has modified an element and on what date.NOTE: The Q LASTMOD and Q USERMOD commands allow you to display in the Command Window, the date and author of the last modification "}
{"Headers": "AVEVA E3D FOLLOW-UP AND VERIFICATION  DB Listing ", "Content": "The DB LIsting is the backup of one or more element(s) of the database as a text file This backup is only compatible with AVEVA E3D and AVEVA PDMS, the versions may be different This file (.txt) can be edited before being reused, it contains all the command lines to recreate the same element identically (name, position, geometry). Only the hierarchy differs and depends on the hierarchy selected at the time of importing this file. Some elements of PDMS using dHe references in CATALOGUE (Structure, Piping, Nozzle, etc...) are only compatible with a Project containing the same CATALOGUE It is possible to use this tool to: - Save an item at a moment \"t\" - Duplicate an element (requires to modify the text file)- Modify an existing element (needs to modify the text file) "}
{"Headers": "AVEVA E3D FOLLOW-UP AND VERIFICATION  Postponement ", "Content": "Reporting is the extraction of information about the 3D model toS text files, Excel, or to the AVEVA E3D reporting editor. Files (.txt) or (.csv) can be edited. They contain all the information you want to extract from the model (name, position, geometry). This data can be modifiedAre and reinjected into the model. Some elements of E3D using references in CATALOGUE (Structure, Piping, Nozzle, etc...) are only compatible with a Project containing the same CATALOGUE It is possible to use this tool to: - Check one or more existing elements- Modify one or more existing elements (requires to modify the text file) - Establish a list of equipment (data extraction) For simple verification operations or modifications, the Simple Report function is preferred: In the exOn the other hand, we question all the elements of the EQUI type located under the CE hierarchy. The NAME, OWNER, PURPOSE, AREA and POSITION attributes of each item found will be saved in the report.txt file"}
{"Headers": "CABLE TRAY APPLICATION Introduction", "Content": "This module allow to create Cable trays\nAVEVA E3D enables users to create cable trays using the following hierarchy model :\nPIPE BRANCH Cable Tray Component BEND RISER TEE \u2026\nNOTE : The Cable Tray module is similar to piping module. A PIPE must contain a branch, meaning it must have two extremities, loca ted at the Head and Tail of the\nbranch. If the PIPE contains multiple branches, it may have more than two extremities.\n"}